To enable IMU logging, you will need to configure you eLogger, but first you need to ensure that you are running an eLogger firmware version that is *older than 1.21* as this latest version has IMU logging disabled to save space. In your firmware update dialog, please confirm that the version is *not* 1.21. If it is, I recommend using this old version of the app to temporarily downgrade the eLogger for this test.
Next, in the app navigate to “Advanced” -> “Custom Hardware Options”. In that dialog, set the option “I want to log data from the Guardian Stabilizer.”
Once you’ve done this, clear your eLogger and do a quick test on your bench with your plane configured for flight and powered on. Let it sit stationary in the orientation of level flight for around 30 seconds or so before unpowering the eLogger and downloading the new dataset. In the UI, select “File” -> “Save Recorder File” and choose a safe location to put the log. Next, after the file is saved, open that folder and find the .FDR file. Next to it, you should find a .IMU file with the same name. If you open this in Notepad, you should see a bunch of non-zero numbers in columns.
If you could, it would be great if you sent that bench-test file to me for analysis. Next, continue to fly with this version until you can find a good example of the AHI having troubles. Take the same steps to save the .IMU file and please send it to me for analysis.
