Hi,
I had my first flight with my new Logo 600SX yesterday and about 2 minutes into the flight it suddenly jumped up and right with no tx inputs , I landed straight away with no other problems
A log was stored with the following

00:00 Calibration Finished
Received Frame was Corrupted
00:10 Received Frame was Corrupted
00:20 Received Frame was Corrupted
00:30 Receiver Signal Lost
Power Voltage is low

I have the anti static kit fitted but when I checked it there was intermittent contact with the tail boom to motor mount wire
Optiguard did not activate
BEC test is fine
I am going to fly it again tomorrow but wanted to be sure this was a static problem and nothing else
Thanks
Andy

Hi,

Yes, this is the static issue with 99% certainty. Unfortunately even with grounding it might be not enough in some cases.
Belt is probably not too tight in the boom.

It can be dangerous because the unit lost signal from receiver so it can be uncontrollable, but this is typical behavior of the static discharges.
It can loose the signal randomly so the failsafe can be activated.

_________________
Spirit System developer

Thanks for your fast response
I have checked belt tension and redone the earth lead so will try again tomorrow
Regards
Andy

Couldn't wait so had 2 flights today just hovering low level
There were no glitches like yesterday but coming in to land on the first flight it suddenly dropped the last 50cm, climbed again then landed normally
Second flight no problems apart from a contant rocking front to back but this is probably too low a head speed
First flight everything connected normal , second flight BEC and optiguard diconnected from Rx so only Spirit had pwer to it

I downloaded the logs after both flights which showed numerous failures that I don't understand
Could someone please tell me if there is anything to worry about , I know some of it will be caused by the low head speed, batteries were at 35% after both flights

Setup is Futaba sbus, standard spirit, 1 bec output to spirit , 1 bec output and optiguard into Rx , (hobbywing 10a bec)

Regards
Andy

If you connect BEC to RX and BEC to Spirit with RX connected to Spirit you create a ground loop in your RX power system. If you got static discharges with belts driven systems this might cause big issues.
Future more you got your OptiGuard in RX, power draw is caused by servos and not RX, RX just uses a view mA while Servos draw A, so plug it to Spirit into any free Port or use Y Cable with Servo. Think of connecting power in a STAR topology, whereas you Spirit sits in the center to avoid ground loops. Connect both BEC leads into Spirit as well as the OptiGuard, use Y Cable with Servos if required. On top I do also recommend use of RX capacitor in range of mF on Spirit to kill any spikes caused by Servos or static. Caps respond great to any noise due to low ESR.
Hope this helps, Adrian

_________________
Oxy4max SpiritPro + HW // SOXOS 550, SpiritPro, HW120A V4, 920KV // SOXOS 600, SpiritPro, HW160A, Pyro650 // SOXOS Strike7, SpiritPro, HW160A, Pyro750 // Skywing Spirit Aero // FrSky Horus X10S + Taranis X7 /

Thank you for the logs.

Unfortunately there you can find there are many warnings .. If everything is OK, there should be absolutely no corrupted packet.
I recommend to try to spoolup the motor without a blades until logs will be completely clean.

Maybe the cables are close to the boom and/or grounding wire?

_________________
Spirit System developer

Thanks for the advice
I think Ineed to unplug everything and start again . I might swap it over with a pro unit off my nitro 600 which doesn't use all the ports

Had the same problem again today
First test flight was close in hovering with a few piro's and was perfect
Second flight as soon as I flew 30m away the heli jumped violently up and right and sounded like it had put full pitch on for a split second, I landed straight away and downloaded the log which didn't have any red warnings but loads of received frame corrupted and tail limit warnings although the tail was fine
Back home I have changed the rx and reset the rudder end points as it was binding slightly and now the logs are all green so it looks like the rx is faulty
I have attached the log from the 2nd flight and the one from when I was setting the rudder to show the difference
I also did a 2 minute motor run without blades and it was all green

hopefully now the next flight will be perfect

Oh, thats great you have figured it out.

So it was bad RX? Maybe some connection was not perfect or antenna is damaged.
Definitively there is some issue so that nearly all packets are corrupted (so for example 1/100 are usable), so it was really not good.

_________________
Spirit System developer