Spirit System

The AI assistant guided me through a fault analysis and finally reported:
In my opinion, this exhausts all reasonable checks that can be performed via the software:
- Logging parameters are correctly configured and confirmed with “Set Logging”
- The firmware (4.0.5) matches the software version
- The motor ran for 30 seconds at actual RPM (1850) with 5–7% vibration—according to the specifications, this should have triggered automatic recording
- Restarting the software, resetting the connection, and reconnecting the USB cable had no effect
- The Event Log shows no errors or anomalies related to motor operation
- Advanced Flight Viewer continues to show 0 logs throughout

This is no longer an operator error that I can resolve for you here. I would report this to Spirit Support as follows:

Summary for Support:
- Spirit GTR, Serial 68-7f-87-71-78-b1, Firmware 4.0.5 (Heli)
- After factory reset + firmware flash: automatic flight log recording does not start
- Logging configuration confirmed as correct (Parameters > Set Logging)
- Test run: Main rotor 30 s at 1850 RPM, 5–7% vibration, no blades mounted
- Advanced Flight Viewer consistently shows 0 logs
- Event log shows no abnormalities (only health messages)
- Software restart, reconnect, and USB cable reset had no effect

The Background:
I had filled 99 percent of the memory with 16 old log files. I deleted all the log files using “Clear Logfiles.” The “Memory Usage” display remained at 99 percent. Something must have gone wrong during the deletion. Maybe the USB connection was interrupted. Right now, I can’t record any log files, probably because the memory isn’t considered cleared yet. If there are no log files, I can’t access the menu to clear the memory again. It’s a deadlock.

I followed the exact same steps for updating and deleting old log files on another helicopter with GTR. Everything worked fine there. I was able to generate a test log with the rotor blades removed.

Konrad

Additional observation: When all log files are deleted, the memory usage display remains the same for the time being. Only after the application is restarted—which is possible only after a log file has been generated—can you see the current memory usage.

Memory usage and a warning, when logging can't be recordetd, should be displayed on a higher level of the diagnostic menue.

Hello,

it seems you are sending report but I am missing information about the issue itself. From the report I understand you can't remove logs, is this correct?
You were asking something AI, but we dont know anything about what you asked.

If your memory is fully used, you will need to wait around 2 minutes until all logs are completely erased - after clicking clear memory button.
If you are using 500Hz logging then memory could be fully used with long flight especially if all variables are checked for recording.
Is throttle channel assigned?

My problem is stated in the heading. Despite my best efforts, I am unable to record log files. The THR channel is assigned on the Spirit GTR. The Clear Logs button in the Spirit Setting software is not accessible, as there is no log file in the memory. See attached screenshot. The memory therefore appears to be empty. I suspect that an internal error is causing the memory to be marked as full due to an incomplete deletion process.

Everything works fine with another Spirit GTR with an identical configuration.

Do I need to send the Spirit in for repair, or is there any other way to resolve this?

Attached is the screenshot of what I see when I open the Advanced Flight Viewer.

Hello Tomas,
I’ve managed to solve the problem, but could you please take a few seconds to read my feedback:
The solution was a bit tricky. The problem was that I couldn’t access the ‘Clear Logs’ button without a .4dr file and I didn’t have one. I generated a .4dr file using another helicopter, saved it to my PC, and then opened it on my PC whilst connected to the faulty Spirit unit. Memory Usage showed 0. I clicked ‘Clear Logs’ again anyway. That solved the problem and I was able to record log files.
Two conclusions:
1) The ‘Clear Logs’ button should always be accessible even without a .4dr file, e.g. in ‘Configure Logging’.
2) Error in the display of "memory usage": after clicking ‘Clear Logs’, the memory usage bar does not change. Only when the window is closed and reopened does the memory usage display 0. This is confusing.

Konrad