I launched a Nimbus 550 with Spirit GTR (V4.0.4) and GeoLink. While on the ground, the helicopter took a very long time to establish a connection to the satellites. After a short time, the number of satellites dropped back to 0. The helicopter was still on the ground. When Sat=0, the altitude display briefly showed 555.2 m. A few seconds later, it showed -100 m. Later, it showed 555.2 m again. I restarted the helicopter several times, but the problems persisted all day.
I then flew the helicopter despite the unstable GeoLink. The altitude display was normal. I activated RTH as a test. As expected, the helicopter flew off in some direction but also dropped rapidly, so I had to turn off RTH immediately.
I checked the GeoLink cable: OK. BEC voltage is absolutely stable and stabilized via SafetyCap. Antenna signals are OK. Vibrations are within the normal range.
It looks like a defect in the GeoLink. The strange thing, however, is that the next day everything works as usual. It might be a temperature issue.
I suspect that the sensor fusion of the altitude sensors causes problems when the connection to the GeoLink is unstable. That could also be the reason why some issues didn’t occur in earlier firmware versions.
Does it make sense to send the GeoLink in for inspection?
Konrad
GeoLink behaving erratically
-
Dr.Fleming
- Posts: 240
- Joined: Sun 18. Apr 2021 16:54:57
Hi Konrad, you wrote few days ago here that your system works ??? 
All five of my helicopter systems with Spirit and Geolink were already working properly after the update to V4.0.4, including RTH testing. It’s strange that on Saturday, June 6, 2026, my Nimbus went haywire—that is, it exhibited erratic behavior, documentet in my log files. Today I had two flights with the same system without any problems at all. Everything was back to normal, just like before. I'm starting to feel confident again.
It’s hard to speculate on what caused the repeated and prolonged malfunctions last Saturday.
The bottom line is: If there are malfunctions, the entire system exhibits erratic behavior.
I test the RTH function repeatedly so that I can take the right actions in an emergency. Everything is okay today. I am absolutely certain that everything is fine with the current V4.0.4. However, I am also certain that the Spirit system tends to exhibit unstable, erratic behavior in the event of disrupted communication with the GeoLink—regardless of the source of the disruptions.
First of all, kudos to the developer of Spirit and GeoLink, but I’d also like to request that the system be made more reliable in the event of disruptions. I’d suggest taking a look at the aforementioned sensor fusion of the altitude sensors and investigating ways to achieve more stable behavior there. Also, there should be no RTH when Sat=0.
Konrad
It’s hard to speculate on what caused the repeated and prolonged malfunctions last Saturday.
The bottom line is: If there are malfunctions, the entire system exhibits erratic behavior.
I test the RTH function repeatedly so that I can take the right actions in an emergency. Everything is okay today. I am absolutely certain that everything is fine with the current V4.0.4. However, I am also certain that the Spirit system tends to exhibit unstable, erratic behavior in the event of disrupted communication with the GeoLink—regardless of the source of the disruptions.
First of all, kudos to the developer of Spirit and GeoLink, but I’d also like to request that the system be made more reliable in the event of disruptions. I’d suggest taking a look at the aforementioned sensor fusion of the altitude sensors and investigating ways to achieve more stable behavior there. Also, there should be no RTH when Sat=0.
Konrad
-
Dr.Fleming
- Posts: 240
- Joined: Sun 18. Apr 2021 16:54:57
Hi Konrad, sound's like Vibration, make a Vibration test without Blades connected to de Spirit Software and see the value, if the vibratin is to high, than there is the problem, fine weight the Main and the tail Blades. I experience also that the GeoLink takes a lot of times to get satellites even with clear sky and on the following Fly's, very curious.
I wrote "The helicopter was still on the ground." That is why there were no vibrations. The RTH was, of course, in flight. Since I had expected the advice to pay attention to vibrations, I had written: "Vibrations are within the normal range."
My only request is that Tomas checks whether there might be issues with RTH or sensor fusion for the altitude sensors if the connection to GeoLink and/or sattelites is unstable.
As the error on my Nimbus 550 no longer occurs, I don't need any further help. Thank you.
Konrad
My only request is that Tomas checks whether there might be issues with RTH or sensor fusion for the altitude sensors if the connection to GeoLink and/or sattelites is unstable.
As the error on my Nimbus 550 no longer occurs, I don't need any further help. Thank you.
Konrad
-
Dr.Fleming
- Posts: 240
- Joined: Sun 18. Apr 2021 16:54:57
Strange thinks happens, hope Tomas bring the next FW fixed.
-
Dr.Fleming
- Posts: 240
- Joined: Sun 18. Apr 2021 16:54:57
I test today again, and I notice because it was windy today ,that the Coming Home Function makes a similar like Position Hold, and the Position Hold Function not Hold the Position. 
Tomas if you see that is to complicate, tell me wich way to sent you the Serial number of the two Spirit units to downgrade around FW 3.72, because I don't know if you receive my private message weeks ago I sent you the setup file, and still not receive a answer from your side.
Tomas if you see that is to complicate, tell me wich way to sent you the Serial number of the two Spirit units to downgrade around FW 3.72, because I don't know if you receive my private message weeks ago I sent you the setup file, and still not receive a answer from your side.