← VBar NEO for external transmitters

Vbar Neo and Futaba Sbus Crash My Trex 550X Log RC Input Packet Lost translated

VBar › VBar NEO for external transmitters · Started by thallescsantiago on 3 April 2017 00:4903.04.2017 00:49
thallescsantiago 3 April 2017 00:4903.04.2017 00:49
Hi guys,

Vbar neo is my first fbl mikado unit.
I installed on my trex 550x. Yesterday I only made two flights.
Today, on the third flight, after takeoff, I activated bank switch 3 for speed 3 of my esc castle. I made a punch up and the heli went uncontrolled, flipped involuntarily and very hard, then the engine shut down, landed the heli on the back without much damage.
By analyzing the vbar log, I saw two "RC INPUT PACKE LOST" events, and then an "RC FAILl HAS BEEN ACTIVATED" event.

My setup is:


Futaba 14SG
RX R6303SB in high speed mode with sbus 1
Connection cable between Rx and Vbar is the original of the vbar.

What happened?
I'm very insecure.
It was a big scare.



OK 0:00 Reset Reason: Power On
Info 0:05 Calibration Finished
OK 0:15 Good Health Message (10sec)
OK 0:25 Good Health Message (10sec)
OK 0:35 Good Health Message (10sec)
OK 0:45 Good Health Message (10sec)
OK 0:55 Good Health Message (10sec)
OK 1:05 Good Health Message (10sec)
OK 1:15 Good Health Message (10sec)
OK 1:25 Good Health Message (10sec)
Info 1:29 Motor Switch operated to Idle bailout
Info 1:29 Motor Switch operated to ON
Info 1:30 Motor Switch operated to Idle bailout
Info 1:34 Motor Switch operated to OFF
Info 1:34 Motor Switch operated to Idle bailout
Info 1:38 Motor Switch operated to ON
Info 1:39 Motor Switch operated to Idle bailout
Info 1:41 Motor Switch operated to ON
OK 1:51 Good Health Message (10sec)
Info 1:52 Bank 2 Loaded
Info 1:55 Bank 3 Loaded
Warn 1:55 RC Input Packet lost
Info 1:55 Raised Vibration Level
Warn 2:04 High Vibration Level
Warn 2:07 RC Input Packet lost
Critical 2:07 RC Failsafe has been activated
Info 2:08 Motor Switch operated to OFF
Info 2:08 Motor Switch operated to Idle bailout
Warn 2:10 The Cyclic Ring is active
Critical 2:10 Aileron Sensor Value out of Range
Critical 2:10 Elevator Sensor Value out of Range
Critical 2:13 Extreme Vibration Level
OK 2:23 Good Health Message (10sec)
OK 2:33 Good Health Message (10sec)
OK 2:43 Good Health Message (10sec)
OK 2:53 Good Health Message (10sec)
OK 3:03 Good Health Message (10sec)
OK 3:13 Good Health Message (10sec)
OK 3:23 Good Health Message (10sec)
OK 3:33 Good Health Message (10sec)
OK 3:43 Good Health Message (10sec)
OK 3:53 Good Health Message (10sec)
OK 4:03 Good Health Message (10sec)
OK 4:13 Good Health Message (10sec)
OK 4:23 Good Health Message (10sec)
OK 4:33 Good Health Message (10sec)



3 mal bearbeitet. Zuletzt am 03.04.2017 17:57 von thallescsantiago.

RV 3 April 2017 05:5603.04.2017 05:56
Uhhh!!!!

This seem to be a RX failure - maybe due bad reception. Please keep the antennas (last 6cm) 2-3 cm away from shielding carbon parts as always recommended - never stick them directly to carbon !

Also check the cable from RX to NEO and check motor isolation (bad isolation could cause sparks to antennas, cables are way too close - more distance here too).

I would place the RX on the upper tray in front of the NEO.

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.




1 mal bearbeitet. Zuletzt am 03.04.2017 05:57 von RV.
Eddi E. aus G. 3 April 2017 10:1203.04.2017 10:12
Hi,

one more thing: i find it questionable to mount sensitive electronics that close to the motor in any case.
In the past, when electrics were on the rise, people found out quickly that glitches occurred, caused by the huge electric and electromagnetic fields.
The solution was to place the receiver and other electronic stuff behind the mast, as far away from high power electrics as possible.
The Rex has the gyro mount there, in front, which is also not the best spot, but the gyro (as an external gyro from a full size VBar, for example, or from a GYxxx classic tail gyro) itself is not that sensitive after all, and if you have a glitch it's mostly only a twitch but does not cause permanent damage at worst.

Now the NEO and other all-in-one flybarless (or together with an external receiver) are more sensitive, and especially the receivers can take permanent damage if spark-overs or (in case of belt driven systems) ESD hit the sensitive transistors. There's hardly anything you can do but put distance between sensitive electronics and high power electric drives, and make sure you have continuity between tail rotor housing and chassis/motor plate, to prevent static charge from building up on a belt driven tail (not applicable if you have a torque tube like on the 550x, though).

That being said, please consider mounting the VBar on the rear, above the tail boom, and the receiver also there on the back.

I can not imagine why a manufacturer should recommend that mounting position, common knowledge and common sense should advise differently :-)

Cheers

Eddi

Born to fly ...
forced to work.
thallescsantiago 3 April 2017 13:2603.04.2017 13:26
I do not believe it is signal failure tx or rx because the vbar does not understand what a loss of signal is between radio and receiver. I say this because I tested on the bench, turning off the radio, in the vbar log I only see "Motor Switch operated to OFF" because it is the TX fail safe setting.

I also flew futaba for years with ikon, both antennas in the carbon frame, no problems.

I was able to reproduce the same error on the bench, I had to pull the cable from the sbus, then obitive an "RC Input Packet lost" and then a "RC Failsafe has been activated" in the event log of the vbar.

It is worth mentioning that I also have many flights on this same heli using ikon, without any problem. So I ask, is Vbar NEO more sensitive to noise in SBUS communication?

Realize that this installation practice is due to already using another system following exactly these installation procedures and successfully.

Eddi E. aus G. 3 April 2017 14:4403.04.2017 14:44
Hi,

well, it depends. SBus outputs a digital data packet with the channel information, and a checksum.
If afaik two packets in a row are missing, the VBar will log

Warn 2:07 RC Input Packet lost
If the signal is completely lost or packets are garbage for a longer time, the VBar will log

Critical 2:07 RC Failsafe has been activated
and output hold to the servos and off to the motor.

Depending on the fail safe setting, the receiver will output it's stored fail safe settings, right, so the VBar won't notice a loss of radio link.
If a receiver does no longer output signals in case of a lost radio link, the VBar will act as mentioned above.

You have tested and confirmed both.

So following your test results, the data packets between the receiver and the radio must have been scrambled and/or the receiver connection was shaky or came loose, so the VBar did the thing it was programmed for in case of no more sensible input: it went into fail safe.

I can not imagine that the input signal processing of both devices is much different, so I would assume the VBar or VBar NEO is not more or less sensitive compared to other devices, if the data packets are OK and the electrical signal is OK, it should be the same.

I'm not familiar with the IKON, does it log?

Kind regards

Eddi

Born to fly ...
forced to work.
thallescsantiago 3 April 2017 15:5103.04.2017 15:51
Hi Eddi, thanks for the reply.

Perfect! It was clear that there was a loss of signal between rx and vbar and not between tx and rx. The big question is, what disrupted the communication to sbus? Electrical or electromagnetic noise? What intrigues me is that I never went through this in another system following the same physical installation. As a flight with Rex, the fbl and rx always stay close to the engine, esc and batteries. I've never had problems.

Ikon generates logs equally to vbar. Vibrations and flight events. It also generates more specific logs, for example, rotation speed of aileorn, elevator and tail. Among other things.
Eddi E. aus G. 3 April 2017 17:0503.04.2017 17:05
Hi,

well, it's hard to tell. A slight difference might make the difference, electric and electromagnetic (less probable) influence decrease non-linear, so a couple of mm can be crucial. Or a bad soldering joint. Or a bad motor (they eat metal parts from time to time, RB1 even offers motor savers now as I saw recently ;-) or a bad ESC or whatever.

This is one of the reasons why I would try and place my sensitive electronics as far away as possible, so it's less likely that issues occur.

Since we don't know what caused it, I'd better be cautious :-/

There's always a time bad things happen, and we can only be as foresightful as possible.

Kind regards

Eddi

Born to fly ...
forced to work.
thallescsantiago 3 April 2017 17:5503.04.2017 17:55
This time of bad things came now when I was motivated to experiment and test the Vbar. This totally broke my confidence with the vbar.

The feeling I have is that if I do not move the vbar and rx to the support boom, I will not be happy. This does not make much sense to me.

I think I'll give time to time. It's not time to change the system yet. Perhaps when it is possible to acquire a vcontrol to guarantee full compatibility.

I am immensely satisfied with all the support that has been given to me. That made a good impression.

Kind regards

Thalles.
VStabi VStabi Pioneer of Flybarless