Page 1 of 1

Avian ESC with telemetry and Spirit GT

Posted: Mon 09. Jun 2025 17:05:29
by Crackers
I enabled Spektrum Avian Telemetry on the Spirit Advanced Tab, ESC Telemetry. I moved the Avian ESC throttle cable from AUX1 to CH0 as noted in the Avian Telemetry section of the manual. All telemetry is working as described. However, the first time I spool up after powering the heli, the ESC slow spool up feature does not work and the heli does a very fast spool up and rotates to the left. When I wait for the blades to stop and spool up again, it spools up slowly and takes about 15 seconds to reach full speed. I am not using the Spirit govenor. Each time I plug in a battery pack, the first spool up is fast and then subsequent spool ups are very slow.

Next I reverted to Disable Telemetry and switched the Avian ESC throttle cable back to AUX1 from CH0. Each time I powered up the heli it did a slow spool up.

I believe that something is wrong with the Avian Telemetry and/or with CH0. Is this a known issue or did I miss a Spirit setting when I changed from AUX1 to CH0?

Thanks for reading and any help or suggestions.

Equipment used: Blade 360 and Blade 330, both with Spirit GT, Avian 45 AMP ESC and 4651T SRXL2 Rx. Avian ESCs are set to Store Gov and Very soft start.

Re: Avian ESC with telemetry and Spirit GT

Posted: Mon 07. Jul 2025 20:54:15
by Crackers
My solution is not eligant but it is effective. With Throttle hold on, I advance the throttle until it indicates 17 out of a possible 100 (on the Dashboard screen of an ix14 or -17 on the Monitor screenof an ix14) . I flip the throttle hold off and imediately back on. The main blades usually do not move at all. I then lower the throttle to zero and spin up normally. The spin up is very slow every time. Problem solved. Hope this can help someone. Thanks

Re: Avian ESC with telemetry and Spirit GT

Posted: Wed 09. Jul 2025 13:06:14
by ZeXx86
Hello,

the problem could happen if some changes were made to the Spirit settings.
Try to repeat without saving anything/launching the software.

We will look at this issue and try to find a proper solution.