Tell me exactly which details you need. Once more, the loss of control occured under Spirit Firmware V4.0.4-r2 and Jeti integration V4.0.4r2. Any more info required?
And to clarify the issue last discussed on RC-Heli: do you think it’s possible that the downgrade from 4.0.5 to 4.0.4-r2 with the logging function set to 500Hz could have been responsible for the loss of control?
And as for so-called conspiracies, none of that – just a touch of desperation!
Regards Philipp
I am already writing it third time in this thread to provide at least settings file and anything about your model. This include wiring, any sensor connection, any uncommon peripherals, photos.
For now we were unable to replicate any issue when using 500Hz settings with 4.0.4 but I can't also exclude this possibility. At the same time I can't recommend to enable features of new firmware and then downgrade. Without checking the behavior we recommend to not try it, especially without prior bench testing with blades off. This is simply because we can't know what features we will add in the future and retrospectively test them with old software and have fix to exclude any issue from happening when doing this downgrade with settings from the future.
I will provide you with further information later this day.
As for now: Do you still see any potential issues after re-updating back to 4.0.5? In other words, can a downgrade to 4.0.4 cause issues that can't be resolved by just a further update?
Both versions 4.0.4 and 4.0.5 are used daily by people around the world. Nobody else until this post contacted us with any similar issue. Downgrading to 4.0.4 with settings made with PC software 4.0.5 and options available since 4.0.5 is not recommended. I hope it is clear now. Reflashing firmwares back and forth is not helpful. You can use both, but with settings made with corresponding PC software/JETI Integration files.
Just to be perfectly clear:
Being back to V5.0.5 on Spirit together with Spirit integration V4.0.4r2 cannot bear any hidden issues, even after the ill-advised downgrade?
In other words again: Is there anything I should do in addition, factory reset and a complete new setup from scratch e.g.?
Regards Philipp
The best would be to return to everything when the problem appeared and replicate it. If it is replicable, then we can easily find what was also the issue and if it was really resolved.
We would do this long time ago instead of you, but with zero detail except versions you provided we can do nothing. This is exact same setup that works for everybody else.
I can't say it will be OK when we have no idea what was source of the problem.
The heli is a Logo 600 SE, motor a Xnova 4025-830KV, ESC a YGE Saphir 125, servos are all Savöx Brushless, 3x SB-2271SG at the swashplate, tail is SB-2291SG. RC power runs at 7V, from YGE's BEC, buffered with a 300mAh LiFe battery via Spirit's AUX . There are no external sensors connected, just ESC telemetry is fed via Spirit's E1. Equipotential bonding is installed, resistance between tail casing screws and motor mounting plate measures around 3.0Ω.
Αttached three settings backup files, one for each bank, plus three pictures uploaded with the next posting.
Regards Philipp
Piro consistency seems very high. Tail servo endpoints seem uneven as well. What ball link distance do you have at the tail servo?
I assume the BEC Tester gave good results, the wires seem a little thin, but i can be wrong here.
Do you have the log from when you had no control?
