Feedback using AI Assistant
Posted: Wed 07. Oct 2026 12:19:57
It was extremely tedious with version 4.0.5, but I managed to improve the parameters of some of my helicopters by carrying out more than 20 analysis flights, each lasting about 1 minute and at a rate of 500 Hz.
The Spirit GTR’s 4.0.5 firmware still has issues when handling log files. I’ve described this before.
The main bottleneck is downloading the log files to the PC via USB. Ist takes several minutes.
The AI Assistant’s calculations of correlation, frequency and lag are useful because they represent the only objective assessments.
The AI Assistant’s advice is almost always poor and does not lead to the desired result. Here, I had to rely on my own knowledge.
I believe that AI support will become the norm in the future. We’re not quite there yet.
Useful steps:
The option to switch logging on and off from the transmitter. This would allow the log files to be made smaller and more accurate.
The truly useful insights from logging are correlation, frequency and lag. These parameters should be calculated on the PC in the Spirit settings or in the Wave transmitter without the AI Assistant.
It would be even better if at least the correlation were calculated in Spirit and made available as a telemetry value. This would enable real-time tuning, whereby a parameter could be optimised in flight, for example via a rotary control.
An example of advice from the AI Assistant:
After analysing the rudder data, the AI recommended increasing ‘Piruette Consistency (Rudder I)’, even though this value was already set to 190. On the next flight, performance deteriorated and I was told to increase it again. Then it got worse again, and the recommendation was to set it back from 245 to 190. The correct advice would actually have been to reduce the gyro gain. Almost all the AI advice was that nonsensical.
Konrad
The Spirit GTR’s 4.0.5 firmware still has issues when handling log files. I’ve described this before.
The main bottleneck is downloading the log files to the PC via USB. Ist takes several minutes.
The AI Assistant’s calculations of correlation, frequency and lag are useful because they represent the only objective assessments.
The AI Assistant’s advice is almost always poor and does not lead to the desired result. Here, I had to rely on my own knowledge.
I believe that AI support will become the norm in the future. We’re not quite there yet.
Useful steps:
The option to switch logging on and off from the transmitter. This would allow the log files to be made smaller and more accurate.
The truly useful insights from logging are correlation, frequency and lag. These parameters should be calculated on the PC in the Spirit settings or in the Wave transmitter without the AI Assistant.
It would be even better if at least the correlation were calculated in Spirit and made available as a telemetry value. This would enable real-time tuning, whereby a parameter could be optimised in flight, for example via a rotary control.
An example of advice from the AI Assistant:
After analysing the rudder data, the AI recommended increasing ‘Piruette Consistency (Rudder I)’, even though this value was already set to 190. On the next flight, performance deteriorated and I was told to increase it again. Then it got worse again, and the recommendation was to set it back from 245 to 190. The correct advice would actually have been to reduce the gyro gain. Almost all the AI advice was that nonsensical.
Konrad