Page 3 of 3
Re: Altitude Limit was activated far above configured altitude
Posted: Tue 05. Aug 2025 20:04:44
by heli_tom
Sorry, I'm not sure what you mean. Shall I connect the ESC by using an Y-Cable to both, Receiver and Spirit GT Channel 1
Re: Altitude Limit was activated far above configured altitude
Posted: Wed 06. Aug 2025 5:16:05
by ZeXx86
No.
Open the software, then in General - Channels assign Throttle to Channel 1.
Save the settings.
This should resolve your problem.
Re: Altitude Limit was activated far above configured altitude
Posted: Thu 07. Aug 2025 11:11:44
by heli_tom
Connected to CH1 is Pitch/Aileron servo.
Regarding "manual.spirit-system.com" the port AUX1 shall be used for BEC/ESC and AUX2 for second BEC line.
Is this correcht? Do you mean this?
Spirit GT with Graupner Hott receiver.
Re: Altitude Limit was activated far above configured altitude
Posted: Thu 07. Aug 2025 11:17:09
by ZeXx86
Unfortunately no, I dont meant this.
I only meant to do these steps:
- Open the software
- Go to General - Channels page
- Assign Throttle to Channel 1.
- Save the settings.
Nothing else is required, no wiring changes are needed. There is no relation to wiring. only channels.
Re: Altitude Limit was activated far above configured altitude
Posted: Thu 07. Aug 2025 11:29:10
by heli_tom
OK, then the ESC line stays connected to Receiver?
Re: Altitude Limit was activated far above configured altitude
Posted: Thu 07. Aug 2025 11:33:08
by ZeXx86
Yes.
Re: Altitude Limit was activated far above configured altitude
Posted: Thu 07. Aug 2025 11:34:16
by heli_tom
OK, I will try. Thank you

Re: Altitude Limit was activated far above configured altitude
Posted: Thu 21. Aug 2025 7:49:36
by heli_tom
Hello,
Unfortunately, setting channel 1 to throttle didn't make a difference. I flew once yesterday, and the altitude limit was triggered again.
I'm attaching the flight log.
Re: Altitude Limit was activated far above configured altitude
Posted: Sun 31. Aug 2025 20:09:48
by heli_tom
Hello,
I updated the Spirit GT today from version 3.7.2 to version 4.0.0. I set the recommended rotation speed and rudder delay values from the update description.
I also reinstalled version 1.4.1 on the GeoLink v2, which took about 10 minutes, not 75 seconds.
After that, I flew twice without the altitude limit being triggered uncontrollably.
When the minimum altitude was exceeded, it was triggered as intended.
I don't know the reason now, but I hope it stays that way!