-
Notifications
You must be signed in to change notification settings - Fork 17.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't set 100Hz for MAVLINK_MSG_ID_HIGHRES_IMU on Rover #28101
Comments
Just a guess, but the loop rate in Rover |
I successfully set 10Hz(actually 9Hz), 25Hz(actually 24Hz), 50Hz(actually 49~50Hz), but I can't set 40Hz, 100Hz, 200Hz. But it works for copter code 4.6-dev(same git commit code). It might be copter handles this command different from rover. I'm NOT digging into the code right now. Just post this question here, maybe someone can take care of it when have time. --- EDIT: BTW, I can test if there is any debug version. |
Ok, I've done some digging and created a patch in #28144. I've confirmed by initial guess that Ardupilot is indeed capping the message rate at |
I'll do the test tomorrow and get back to you soon. --- EDIT Yes, change loop rate helps. Is there any api for changing "SCHEDULER_LOOP_RATE"?
Does this mean we can remove this part in ardupilot/libraries/GCS_MAVLink/GCS_Common.cpp Lines 1654 to 1660 in 075a5c3
|
That's just an Ardupilot parameter that you can set via your GCS. |
Setup:
same code from setting MAV_CMD_SET_MESSAGE_INTERVAL,MAVLINK_MSG_ID_HIGHRES_IMU to 100Hz, which is 10000 us.
Result:
PS: Previous discussion hereCan't set 100Hz for MAVLINK_MSG_ID_HIGHRES_IMU?
#4.
The text was updated successfully, but these errors were encountered: