Hello,
I had some flights with the V3.0.1 and everything was good.
But on the weekend my Trex 550 crashed. It was almost impossible to steer. I switched off the engine 3 meters above the ground.
After I plugged the power back on, everything ran fine again, only the helicopter is of course broken for now.
I would like to know now only what it was due.
Was it the receiver, was it the Spirit, was it the software?
Here the log of the Spirit in the attachment.
Best Regards
Gerald
crashed Trex 550 V3.0.1
Hello,
unfortunately without additional details it is hard to tell what could be wrong.
But we always recommend to use official latest firmware that is available at the web page.
I can only say from the flight log it was likely not issue of the receiver.
Do you have any connected peripherals such as RPM cable or Governor?
How long the model was flying previusly without any problem?
unfortunately without additional details it is hard to tell what could be wrong.
But we always recommend to use official latest firmware that is available at the web page.
I can only say from the flight log it was likely not issue of the receiver.
Do you have any connected peripherals such as RPM cable or Governor?
How long the model was flying previusly without any problem?
Spirit System developer
Hello,
It is clear that this is difficult.
The problems started when I turned on the minimum height. He kept climbing and climbing and... until I flipped the switch again. After that he hardly reacted at all and felt he had to do something on his own. Stick movements did not matter at all.
Currently I am back to 2.8.0.
So you think its more of a software problem with Spirit with V3?
Or should I have the Spirit tested?
No, no RPM or controls.
About 6 batteries/flight.
Best Regards
Gerald
It is clear that this is difficult.
The problems started when I turned on the minimum height. He kept climbing and climbing and... until I flipped the switch again. After that he hardly reacted at all and felt he had to do something on his own. Stick movements did not matter at all.
Currently I am back to 2.8.0.
So you think its more of a software problem with Spirit with V3?
Or should I have the Spirit tested?
No, no RPM or controls.
About 6 batteries/flight.
Best Regards
Gerald
-
bert_stadler
- Posts: 7
- Joined: Fri 20. Dec 2019 21:30:54
Hallo, ich hatte das gleiche Problem und musste auch den Motor ausschalten. Das Spirit ist komplett ausgestiegen und zahlreiche Einträge mit Hauptprogrammschleife verzögert !
Bin geheilt von der Firmware 3.0.x ! Bin zurück auf 2.8 und da werde ich auch lange Zeit bleiben....
Bin geheilt von der Firmware 3.0.x ! Bin zurück auf 2.8 und da werde ich auch lange Zeit bleiben....
Hi,
last weekend i had a crash with the Goblin Fireball after the update: Koniguration: Spirit 2, Geolink, ESC telemetry, wireless module, SPM4651T
Yesterday I had misfires with the Goblin 700 and was just able to save it. Configuration: Spirit Pro, Geolink, ESC telemetry, SPM4651T, also the latest update from Spirit and Geolink.
I had the same errors in the LOG and an additional error from the Geolink, then I deactivated the Geolink and pulled the plug, then everything worked.
In the Goblin 570, Spirit2, without Geolink I had no failures so far.
So better back to software version 2.8 ??
last weekend i had a crash with the Goblin Fireball after the update: Koniguration: Spirit 2, Geolink, ESC telemetry, wireless module, SPM4651T
Yesterday I had misfires with the Goblin 700 and was just able to save it. Configuration: Spirit Pro, Geolink, ESC telemetry, SPM4651T, also the latest update from Spirit and Geolink.
I had the same errors in the LOG and an additional error from the Geolink, then I deactivated the Geolink and pulled the plug, then everything worked.
In the Goblin 570, Spirit2, without Geolink I had no failures so far.
So better back to software version 2.8 ??
