← VBar NEO for external transmitters

Neo Flashing Red translated

VBar › VBar NEO for external transmitters · Started by Mike14755 on 26 November 2017 22:2826.11.2017 22:28
Mike14755 26 November 2017 22:2826.11.2017 22:28
After a few flights today the Neo would not initialise it flashed red and the cyclic jumped up and down both the satellite receivers were locked to the transmitter after re powering it a few times it initialised ok the helicopter flew ok but the governor (Nitro Mode) would not provide any power and I noticed the remote sensor changes colour some time red when you move the helicopter around is this ok or has Neo developed a fault.
RV 26 November 2017 23:2026.11.2017 23:20
Can you please read the event log (all entries) and attach it here?

regards (EN) / Gruss (DE)

Rainer Vetter

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Posting and answering - please use a PC and a standard keyboard. Answer all questions fully, take the needed time, don't forget probably requested attachments.

Für Posts und Antworten bitte einen PC und eine richtige Taststaur benutzen sowie alle Fragen vollständig abarbeiten. Nehmt Euch Zeit, beantwortet Rückfragen in Ruhe und vollständig.
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Für Einzelkommunikation bitte ausschließlich Email verwenden! - PN, Messenger, Chat usw. werden nicht bearbeitet.
For single user communication please send a email only! PM, Messenger, Chat etc. won't be read.
Mike14755 27 November 2017 10:3127.11.2017 10:31
Hi Rainer
I am not using a V Bar transmitter so the log file you need is that the file I save in the PC interface setup window if not how to I get the log file from the Neo ?
Eddi E. aus G. 27 November 2017 12:1027.11.2017 12:10
Hi,

in the PC Software there is Info/Event Log, Get All Entries, Save.

Kind regards

Eddi

Born to fly ...
forced to work.
Mike14755 27 November 2017 12:2727.11.2017 12:27
Hi
Ok I found that I was using a mac and its in a different place but now when I attach file its not a valid type.
Eddi E. aus G. 27 November 2017 12:3827.11.2017 12:38
Hi,

OK, then please zip-compress it (right click, ...) and attach the compressed file, that should be allowed.

Kind regards

Eddi

Born to fly ...
forced to work.
Mike14755 27 November 2017 13:0027.11.2017 13:00
Hi
I have managed to attach the file. Dateianhänge:
öffnen | Download - log-20010023-27-Nov-2017-11-53-50.zip (1.6 KB)
Eddi E. aus G. 27 November 2017 13:4027.11.2017 13:40
Hi,

there seem to be no warning entries, so let's see if we can narrow it down.

You are using an external sensor, can you please try without? The external sensor should rotate through red-green-blue (at rest) and show a particular color (depending on which direction you rotate it). Red would mean it has an aileron motion detected. If it was lighting up constantly, it would indicate an issue with the respective sensor element.

If the external sensor had a fault, I would expect an error message, though, but if there are none and the VBar works properly without, we could pretty much pin it down to the sensor.

The problem with the governor / Nitro is probably something different, if the Governor does not provide power, probably the RPM sensor is not/properly connected (any more), but there are no tell tale entries in the log any more, either, so first thing would be to get the VBar to work again so you can do another test flight and read the event log again.

Best,

Eddi

Born to fly ...
forced to work.



1 mal bearbeitet. Zuletzt am 27.11.2017 13:41 von Eddi E. aus G..
Mike14755 27 November 2017 16:4727.11.2017 16:47
Hi Eddi
Thanks for the info I will try it out again as you suggested and see what happens.I did think the governor was a different issue but just wanted to check really that you thought the Neo was fine to continue flying with. Now I know about the log then I can have a look at them myself. One last question the Cyclic jumping up and down what is that warning about.
Thanks again
Mike
Eddi E. aus G. 28 November 2017 08:5228.11.2017 08:52
Hi Mike,

this usually happens either if a sensor issue is detected, like sensors off center, not coming to rest, the IMU sensor z axis sticking temporarily for example, at the power on self test, or if the input signals from the radio are not at center and idle (control inputs but pitch, e.g. a trim too high (on third party radios) or a stick movement where there should be none, during the p.o.s.t., because we read the stick center positions at power on and take them for what they are.

There should be an error message entry in the log, though, but since the VBar seems to have been turned on for a prolonged time in the meantime, these entries could have been overwritten already. That's why I would do a test, on the ground, without the external sensor, if possible a test run with the engine running (no blades) to see if there are any tell tales for vibration messing with the sensors (like uncommanded swash plate movements, drift, also on the tail), then check the logs again, then do a test flight, check the logs again.

Kind regards

Eddi

Born to fly ...
forced to work.
VStabi VStabi Pioneer of Flybarless