tb
5 September 2018 07:3905.09.2018 07:39
After working fine for about 10 fligts, my vbar neo will not initialize and keeps blinking red and the swash jumps up and down, but when I connect it to my PC, I got it to initialize and when I download the log I find this: "Critical IMU Sensor failure "
I also found this on the forum page:
https://www.vstabi.info/forum/read.php?53,144972
Regards
Torbjørn Mundal
Eddi E. aus G.
5 September 2018 08:4905.09.2018 08:49
Hi Torbjørn,
can you please save and attach the log file here?
What heli, radio, receiver, power supply, other components like servos etc. are you using?
There are several IMU sensor related messages, and some come up e.g. if the power supply is not stable at power on, so the VBar refuses to initialize on ambiguous data. A good test for that is to power on the model from a suitable and charged receiver battery (4/5s NiXX, 2s LiPo). If it initializes then 10/10 times, it's pretty much a proof that the power supply (e.g. BEC) is struggling to supply stable voltage in time, for all the sensitive electronics to initialize.
If you find z-axis related messages in the log, the cause is probably vibration related, and you can most probably (and safely) circumvent this if you select Standard Initialization over Precision, in the Rescue Setup.
Kind regards
Eddi
Born to fly ...
forced to work.
tb
5 September 2018 10:0905.09.2018 10:09
Hi Eddi, thanks for your reply
Heli: Synergy N556 (Nitro)
7.4 lipo receiver batt
Futaba T16SZ radio with R7003SB receiver (SBUS)
I saved my log but it will be saved as text so the error codes will be lost
I tested the whole now and checked the log and there I find a couple of code 60 raised vibration level and 1 code 61 high vibration level
I also get a couple of code 130 governor full throttle, which is usually normal with nitro I suppose ??
tb
5 September 2018 13:1305.09.2018 13:13
Now I have tried with the external sensor
Flying well just like with the embedded sensor, but after the flight, I go to analyze the log, but now it will not initialize either with or without usb cable, I have tried with another receiver battery, but no difference, just flashing red and Swash jumps up and down 20-30 times
Eddi E. aus G.
5 September 2018 13:2505.09.2018 13:25
Hi again,
well, the log would tell more. The text file is good enough unless there are error codes which are not translated into human-readable.
The external sensor is gyro-only, so it makes no real difference. What raises the error messages is the IMU sensor (accelerometer for Rescue).
The vibration entries are written if certain thresholds are crossed, for information. But it does not necessarily tell you how hard the vibrations are on the sensors, and at which frequencies they happen. If there is no drift in flight, or indifferent feeling, model not feeling locked in, all is well from that side.
Full throttle means the VBar can not open the carb any further and the head speed can not be maintained, helps with tuning an engine, a model, to a head speed where the governor has enough headroom to govern.
Kind regards
Eddi
Born to fly ...
forced to work.
tb
5 September 2018 13:3505.09.2018 13:35
But now it will not initialize either with or without usb cable, so it's not possible to download the log, but I'll add the two logs I've managed to download
Well, I can not get this message: This file is not an allowed file type. Allowed file extensions: gif, jpg, png, zip, bmp, pdf, vbr
Eddi E. aus G.
5 September 2018 15:5305.09.2018 15:53
Hi again,
even if it does not initialize, you can go Info/Event Log.
If you tap the VBar not too soft, not too hard, with a dull tool (non-business end of a screwdriver for example, or a lighter), does it initialize then?
This would release the mechanically sticking sensor element eventually.
.zip is allowed, so please zip (compress, add to zip file) the files you want to send, or send as an e-mail-attachment to service (at) mikado-heli (dot) de.
Kind regards
Eddi
Born to fly ...
forced to work.
tb
5 September 2018 16:2705.09.2018 16:27
hi again Eddi,
I got it to initialize by tapping vbar
Downloaded the log
Heli flies very smoothly without any drifting it's brand new, new engine, etc.
The Governor Full Throttle warning in the log is when I'm at full stick climbing
I have sent the logs by email and tagged it with logs from torbjørn
Eddi E. aus G.
6 September 2018 10:2206.09.2018 10:22
Hi Torbjørn,
according to the logs, you may have two issues. First, the vibration influence on the z-axis-sensor of the IMU.
This can be remedied (and safely) by selecting Standard Initialization instead of Precision, in Rescue Setup.
Then, you may also have a power supply issue, but I would doubt that if you use a (charged and in good working order) 2s LiPo.
Try Standard Initialization (and leave it at that), and see if you run into initialization issues again. Check the log frequently. If you don't have critical log file entries any more, all should be well.
Nitro running smooth is an oxymoron :-) even if the mechanics are running smooth, the 1 cylinder engine hammering away is always a good cause for troubles, as would be a drive train not balanced properly (clutch liners/clutch bell etc.).
With VBar Control, you would be able to check the vibration levels and the Rescue status in flight, the latter without having to actuate Rescue to see.
Without, you have to try ... if the model does not drift in flight, all is well for the gyros. Be prepared to switch banks/head speeds and/or auto during the first shakedown flight(s), and if Rescue works properly, same. But you have to test in real life, to see. Would mean, for Rescue, do it up high (higher than the 4 second timeout), so you can take over again should rescue go anywhere but up.
Of course you can also run the vibration analysis in the PC Setup Software, on the bench, and put the engine and mechanics through it's paces briefly, it won't take damage.
In general, all works well even on nitros or gassers, but there can be exceptions ...
Kind regards
Eddi
Born to fly ...
forced to work.
1 mal bearbeitet. Zuletzt am 06.09.2018 10:23 von Eddi E. aus G..
tb
6 September 2018 12:4006.09.2018 12:40
Hi Eddi,
What in the log suggests the power supply issue? "Critical 0:00 Hotstart"?
I see in my last log that I only have vibration warning at the spool up and down
Thanks for the help so far Eddi :-) I will check the log after each flight, but if I choose Standard Initialization instead of Precision and my Initialization issues are gone then is everything ok?
Eddi E. aus G.
6 September 2018 13:4606.09.2018 13:46
Hi again,
said warm start, and the IMU Sensor entries seemingly only at the time of power-up, where it's critical to have a stable voltage, so the sensors settle properly. Of course I can not tell the time as to when what did happen, was logged, but by experience I would interpret it that way.
If Standard, the VBar will decide: IMU z-axis sticks or hangs, init with a mathematical workaround and under the assumption 'up is up' (the model must stand on it's skids, rotor shaft pointing up, not necessarily upright), or no issues found, init with all sensor elements.
If Standard, the VBar will inform by a triple pitch twitch, if Precision with the known single twitch.
Kind regards
Eddi
Born to fly ...
forced to work.
tb
6 September 2018 14:0506.09.2018 14:05
Hi Eddi,
Ok the hot start was because of me restarted vbar too fast ..
Ok so that's the difference between standing and precise
Thanks again :-)
Torbjørn
tb
7 September 2018 10:4407.09.2018 10:44
It does not matter if I put Precision or Standard, I only get single twitch during initialize..
Eddi E. aus G.
7 September 2018 12:2407.09.2018 12:24
Hi,
do a couple of flights, and see at each power on. You only get the triple if the sensor element is sticking, if it's good you can power cycle as often as you want to, and only get the single twitch, because all is well already ;-)
My text above should say, that in Standard, the VBar will still initialize with Precision _if possible_ an only fall back to Standard _if necessary_, then inform with a triple twitch, but only then.
Kind regards
Eddi
Born to fly ...
forced to work.