Robot_localization diagnostic question #2
I'm still underway attempting to fine-tune an instance of (ekf) robot_localization using gps and single imu devices. The diagnostic message for the ekf filter "appears to be functioning properly." However the next message states "odometry/filtered topic status message: Frequency too low." The value is less than 5Hz with the frequency of both the ekf and the navsat transform are at 60 Hz. The imu delivers at around 55 Hz (set at 16ms ~ 62.5 Hz) using the ImuFilterNodelet of imu_filter_madgwick; so there is some latency.
My goal is to get as close as possible to 60 Hz to enable the gps/filtered topic to deliver a data set that allows around this frequency for post processing sync with dynamic images. How can I rectify the filtered topic status with this latency?
Thank you as always, B2256
Can you please post sample inputs and config files? The EKF can run at hundreds of Hz even with multiple inputs, so I suspect that something else is amiss.
Thanks Tom. Here is the dropbox link: https://www.dropbox.com/sh/u3kznp4oiy...
Still getting low output when initiate bag recording; bandwidth on the Beaglebone Black perhaps.
The link only appears to have launch files. Do you have sample input messages?
Input messages are now on the above dropbox link as "TRIAL007_INPUT.odt". Still suspecting bandwidth issue with the Beaglebone Black, but hopefully some launch file or configurations can be identified for the source of error? Thank you Tom.