I noticed the last days some very huge spikes in my vibration logs. When I had a closer look I discovered the RAW line with spikes had the same high number as the next ATT line in the logs.
Look at RAW line 5540 and you see -225, 0, 20531 for X,Y,Z Accel. Three lines later 5543 you see exactly the same values in the ATT line but now for Pitch, Yaw In and Yaw.
This must be a software issue isn't it? Who has an idea? Can I solve this myself?
The logs are downloaded over a direct USB connection.
Replies
I did a test after your suggestion about the problems in the download process. I think it is true. I downloaded the same log and noticed the spikes were on different places. So the spikes are not in the original log in the APM.
I work on a Windows XP laptop without any VM. Some time ago, with the same APM and laptop, it was working fine. I think the only thing wat has changes are some updates to Mission Planner. Has there been a change what can cause this?
Its almost certainly an artefact of the log download process as there is no flow control. Most often seen if you're using a VM on a Mac/Linux, but seen on other machines at times too.
On my mac, I resorted to using 'script' to capture the output and 'screen' to talk to the serial port, rather than using missionplanner in a VM - its fixed the problem completely.