Hello ArduPilot community,
I’m new to ArduPilot and this is my first post. I’m running ArduRover V4.5.5 in SITL on WSL2 (Windows 10). Everything is working well—I can connect to the rover and execute missions without issues. I primarily use MAVProxy for interaction but also connect via Mission Planner.
However, I’m encountering a minor annoyance: the console is continuously flooded with the message “Field Elevation Set: 0m” appearing every second. This makes it difficult to see other important messages.
I’ve tried searching the documentation and forums for a solution but haven’t had any luck. The only related thread I found is this one which also includes a screenshot showing a flooded message console, like mine, but it doesn’t have a resolution.
Is there a MAVProxy command or boot argument that can suppress this specific message or reduce its frequency? Why does it occur every second—is it related to an altimeter or some other sensor trying to correct itself?
My setup:
- ArduRover V4.5.5 (frame_class=2)
- SITL on WSL2 (Windows 10)
- Connecting via Mission Planner
I’m running this SITL simulation to familiarize myself with ArduPilot before deploying on a small sea vessel equipped with a CUAV V5 and a Raspberry Pi 5.
Any guidance on managing this message would be greatly appreciated. Thanks in advance for your help!
— UPDATE —
Upon researching this further, I think I might have identified the source of the repetitive “Field Elevation Set: 0m” message.
It turns out that this behavior is linked to the BARO_FIELD_ELV parameter in the ArduPilot firmware. By default, this parameter is set to 0.0, which causes the system to continuously reset the field elevation to zero every second while the vehicle is disarmed. I confirmed this, if I arm the vehicle, the message stops. If i disarm, it starts sending it again every second. This issue is particularly prevalent in surface vehicles like mine (a sea vessel simulation), but it’s also been observed in submarines and a relevant issue (and fix) was posted in github.
I understand it’s not disrupting the operation of the rover in any way, but still, I find it clutters messages without an apparent reason? I am thinking of experimenting with setting BARO_FIELD_ELV to a small positive value, but I am not sure if this will have any other consequences. Does anyone have any recommendations? I am not sure why this fix was not applied to other ArduPilot - Rover types, but since I am very new to this, there 's definitely things I don’t understand…
Thanks …