Hi,
I am experiencing very strange behaviour after bootup sometime when Geolink is connected, it is so strange I recorded a video to show it happening, in the video https://youtu.be/Ly15sg8f-I0 you can see the following happen:
- Power the heli, the ESC / motor beeps ok
- Tx receives telemetry from Spirit ok, GPS pos 0,0 (no position acquired yet)
- I test move Tx sticks, and heli responds as expected on all movements (inc pitch)
- Geolink acquires position (blue led on, GPS coordinates seen on Tx telemetry)
- Pitch repeatedly and randomly changes from one extreme to the other with no input from me.
- I can still control rudder and cyclic from Tx sticks as normal, but most of the time I don't have any control of pitch. When I do it is briefly between the pitch still randomly jumping from one extreme to the other.
- Logs don't show anything unusual (only cyclic and rudder limits reached which I believe is normal if you test movement end to end?), shows health ok, doesn't show any loss of signal.
During that process I have not tried to perform any Geolink actions such as set home position, I have not spun up motor, I have only moved the sticks whilst the heli remained still.
If I disconnect the Geolink (v1) then I never experience this issue, pitch does not move by itself and all channels respond ok every time I power up.
I have swapped to a spare Geolink and Geolink cable, and still see exact same issues.
Failsafe is configured for negative pitch, and TX is also at negative pitch, so it is not jumping to failsafe position and back.
Sometime this behaviour will not occur. If it does not occur and I can successfully go on to set home position from Tx (with the pitch slowly going one way then the other to confirm), then after that it will fly ok including geolink functions such as return to home for the rest of the flight, so does not appear to be a loose connection.
So it seems to be around the time of GPS position acquiring that this behaviour can occur, and once it starts I have to power of / on and try again, until I get a time when it does not occur (although clearly I don't want to continue to fly it with a known issue).
Any ideas what it could be or what else to try?
Spirit unit and Geolink (V1) are running latest firmware versions, but I have experienced this issue on previous Spirit firmware versions so not version specific.
(Backup of the settings attached in case it helps Thomas)
| Attachments: |
after tweaking rudder - Bank 0.4ds [255 Bytes]
Downloaded 24 times |
