Mavlink command SET_MESSAGE_INTERVAL does not respect disabling of LOCAL_POSITION_NED messages

arduouspilot · February 6, 2023, 11:38am

Posting here before I do a Github bug report in case I got it wrong…

If you use MAV_CMD_SET_MESSAGE_INTERVAL with:

com.param1 = (float) MAVLINK_MSG_ID_LOCAL_POSITION_NED;
com.param2 = (float) -1;

Then Arducopter ignores the -1 and sends MAVLINK_MSG_ID_LOCAL_POSITION_NED every 100-200ms.

Anyone else seen this bug?

Thanks.

amilcarlucas · February 6, 2023, 11:44pm

This is not a bug. Please post all your SR* parameters.
One of the SR*_position is not set to zero.

arduouspilot · February 8, 2023, 4:19pm

Please see below for the non 0Hz params:

I set SR0_POSITION to zero Hz and I no longer see MAVLINK_MSG_ID_LOCAL_POSITION_NED.

Thanks very much, I had no idea these params could override the ones set with MESSAGE_INTERVAL.