update: for test purposes I flashed the Geolink with old version V1 1.2.1 [19.12.2020]
The problem disapeared. Initial value is 0kmh.
Flashing again the latest version V1 1.4.1 [6.6.2024] the problem is back. Initial value 379.1kmh.
In other words it seems to be a firmware bug.
I'm using quite a standard equipment, Spirit GTR with Geolink V1 controlled by Jeti DS-16 II. Therfor I wonder if there is anybody out there with the similar issue?
Dear heli community,
I use a GTR with Geolink V1 in my heli. Transmitter: Jeti DS-16 II.
Originally after power on, the Jeti display shows 0 in min and max speed value.
But since a while the initial value is 379.1kmh.
During flight speed is tracked correctly. However the max value remains at 379.1kmh.
Has anybody experienced a similar issue? Any proposal to get it back to 0?
Thanks in advance for feedback
GeRoi
Geolink speed telemetry wrong initial value
Hello,
the problem could be that immediately after speed is available it is calculated based on imprecise data. Few seconds later the data are much more precise.
So for GeoLink it is identical as if model is really moving.
It could be fixed by not updating the value until HDOP is precise enough.
the problem could be that immediately after speed is available it is calculated based on imprecise data. Few seconds later the data are much more precise.
So for GeoLink it is identical as if model is really moving.
It could be fixed by not updating the value until HDOP is precise enough.
Spirit System developer
Thanks for your comment. Unfortunately as a user I have no influence on the timing and hence I have no possibility to fix it myself.
I tested the same Geolink with a Spirit pro and Jeti receiver. The same problem; initial value is 379,1kmh.
A Geolink V2 version (with latest Firmware) has no problem. Initial value is 0kmh.
To summarize my findings:
- Geolink v1 with Firmware 1.2.1 works correct
- with Firmware 1.4.1 it shows 379,1kmh. It is always 379,1kmh (not a random number)
- My Geolink v2 with latest Firmware works correct.
Any chance to get a Firmware update fixing this issue?
I tested the same Geolink with a Spirit pro and Jeti receiver. The same problem; initial value is 379,1kmh.
A Geolink V2 version (with latest Firmware) has no problem. Initial value is 0kmh.
To summarize my findings:
- Geolink v1 with Firmware 1.2.1 works correct
- with Firmware 1.4.1 it shows 379,1kmh. It is always 379,1kmh (not a random number)
- My Geolink v2 with latest Firmware works correct.
Any chance to get a Firmware update fixing this issue?
I'd like to come back to the issue posted a year ago, since no solution found yet.
I appreciate checking max speed value after landing. I can imagine many of you do the same.
Unfortunately the max value is always 379.1 km/h since this value is erroneousely transmitted by Geolink V1 after power up.
The original FW 1.2.1 was ok. Only 1.4.0 and 1.4.1 is having the issue.
I could go back to FW 1.2.1, but this gives me bad feeling, assuming good reasoning for the updates.
I have another workaround: after powering the heli, I wait until Geoling transmits correct data. Then I manually reset the telemtry data on my Jeti DS-16 transmitter. The only drawback: I often fortget to do so
So, ideally a FW update could fix the problem.
Or is there any other idear to automatically reset the telemetry min/max data. Or any idea how the value 379.1 km/h can be filtered out?
Any idea or hint is appreciated, thanks indeed
GeRoi
I appreciate checking max speed value after landing. I can imagine many of you do the same.
Unfortunately the max value is always 379.1 km/h since this value is erroneousely transmitted by Geolink V1 after power up.
The original FW 1.2.1 was ok. Only 1.4.0 and 1.4.1 is having the issue.
I could go back to FW 1.2.1, but this gives me bad feeling, assuming good reasoning for the updates.
I have another workaround: after powering the heli, I wait until Geoling transmits correct data. Then I manually reset the telemtry data on my Jeti DS-16 transmitter. The only drawback: I often fortget to do so
So, ideally a FW update could fix the problem.
Or is there any other idear to automatically reset the telemetry min/max data. Or any idea how the value 379.1 km/h can be filtered out?
Any idea or hint is appreciated, thanks indeed
GeRoi