Today, I updated my Spirit 'Red' and My Geolink to the latest 3.1 version.
When the Geolink is powered up, the blue led lights up, then goes off, then after 5-10 secs, it turns permanently on blue. This afaik indicates that it has sat lock.
Then I set the home position:
I flicked the switch to "on 2". The swash moves slowly from low to high, then jerks back to low, indicating the home position is set.
After doing this, I have no control input, nothing, cannot arm, cannot move swash, cannot move rudder. All inputs seem to be ignored by the spirit.
I have to unplug the battery and reconnect it to regain control, then set home position again. This time, it responded to control inputs as expected, so i set home again, and then it stopped responding to all inputs again.
I can reproduce this issue every time.
Power up, wait for solid blue led.
Set home position.
if control inputs work, set home again, and after its done, there will be no response to control inputs.
--- 2nd Issue ---
After landing, the elevator is twitching. Random movements. All other servos are perfectly still, but the elevator is randomly flicking up and down every few seconds.
Before the update, i was using v2.8. I have not had any of these issues with v2.8. After setting RTH position exactly as described above, the unit responded to all control inputs exactly as expected.
GeoLink set home position problem
Hello,
are your settings identical as with version 2.8?
There are no differences in 3.1 in that area so it should behave identically
Maybe you set up bank switching? Possibly programming could be for all banks instead of just one bank.
are your settings identical as with version 2.8?
There are no differences in 3.1 in that area so it should behave identically
Maybe you set up bank switching? Possibly programming could be for all banks instead of just one bank.
Spirit System developer
Hello,
no, we were unable to reproduce this issue.
Can you let me know what receiver, radio and protocol you are using?
no, we were unable to reproduce this issue.
Can you let me know what receiver, radio and protocol you are using?
Spirit System developer
Hello,
I hope we have found the problem. It look like it could happen only when settings is saved for all banks.
We will send you link for firmware where you can verify if it will help.
I hope we have found the problem. It look like it could happen only when settings is saved for all banks.
We will send you link for firmware where you can verify if it will help.
Spirit System developer
The build you sent me didn't fix the issue.
I've just updated to 3.2.0, the issue remains, however, its different.
Once I set RTH, the controls locked-out as they did previously, however, this time, after a reboot, the controls remain locked out. The spirit responds to movement (keeps swash level) but does not respond to TX stick movements.
The only way to regain control is to either unplug the geolink and power cycle, or to connect the PC USB software.
Doing either of these allows the unit to respond to control inputs again, but once the power is cycled and the geolink is plugged back in, it stops responding to control inputs again.
So, for now, I cannot use the geolink.
I've just updated to 3.2.0, the issue remains, however, its different.
Once I set RTH, the controls locked-out as they did previously, however, this time, after a reboot, the controls remain locked out. The spirit responds to movement (keeps swash level) but does not respond to TX stick movements.
The only way to regain control is to either unplug the geolink and power cycle, or to connect the PC USB software.
Doing either of these allows the unit to respond to control inputs again, but once the power is cycled and the geolink is plugged back in, it stops responding to control inputs again.
So, for now, I cannot use the geolink.
I am afraid but something in your setup is behaving differently than for the rest.
For a try I recommend to set very clear radio profile - especially with default frame rates and channel layout.
And then to try it again. Hopefully we will find the reason why it is happening for you.
I guess some of your channel is out of range. This can cause such strange issues. Are all channels limited for +/-100% not go beyond? I mean in the Diagnostic tab are they not exceeding 100%? By default OpenTX is sending around +/- 125% for each channel which is not good.
Am I right you are saving new RTH position each power up?
For a try I recommend to set very clear radio profile - especially with default frame rates and channel layout.
And then to try it again. Hopefully we will find the reason why it is happening for you.
I guess some of your channel is out of range. This can cause such strange issues. Are all channels limited for +/-100% not go beyond? I mean in the Diagnostic tab are they not exceeding 100%? By default OpenTX is sending around +/- 125% for each channel which is not good.
Am I right you are saving new RTH position each power up?
Spirit System developer
