A message was asked for more often than ArduPilot can send it
What ArduPilot says:
- Requested rate for message ID N too fast. Increase SCHED_LOOP_RATE
A ground station or companion computer asked for one MAVLink message (the ID is in the line) at a rate above 0.8 of the main loop rate: more than 40 times a second with SCHED_LOOP_RATE 50, more than 250 with 400. ArduPilot sends messages from the main loop, so it cannot go faster. The request is refused and the message keeps its previous rate.
What to do, most likely first
A program asks for more than it needs.
CheckWhich program sets message rates: the ground station's telemetry-rate settings, or a companion computer's start-up script?
FixAsk for a lower rate: a display needs 4 to 10 a second, and few uses need more than 50.
The line suggests raising SCHED_LOOP_RATE. That changes how often the whole flight code runs and how loaded the processor is; do not change it for the sake of telemetry.
Parameters to look at
| Parameter | What it is |
|---|---|
SCHED_LOOP_RATE | Scheduling main loop rate |
Where to do it:Setup & Tuning Guide
The code that sends it
Requested rate for message ID N too fast. Increase SCHED_LOOP_RATE
libraries/GCS_MAVLink/GCS_Common.cpp GCS_MAVLINK::set_message_interval() · Open in ArduPilot Copter-4.7.1