I’m getting the following error in Ardurover messages in the CPP app.
Anyone know how to fix it?
got MISSION_ITEM; GCS should send MISSION_ITEM_INT
Thx
Be specific. What app are you using?
Sorry, the app is Carp Pilot Pro.
It’s when I send a mission from the app to the pix, nothing happens and looking at the messages I see the above.
Hi @sbbrs,
This is a warning that AP is sending out because we prefer to receive the MISSION_ITEM_INT message because it has slightly better accuracy than the MISSION_ITEM message. This is something that the app developer should fix.
This is a warning though so I don’t think it should stop the mission from being loaded or used. FYI @peterbarker.
The exact line of code producing the warning is here but that’s unlikely to help anybody actually.
As a side note (perhaps to myself) we should improve this mavlink interface wiki page to make it easier for app developers.
Hi, thanks for the reply, I’ve emailed the developer of the CPP app, notifying him of the error.
Do you know what version of Ardurover first had the change to the code?
I’ve tried 4.7.0 and 4.5.0 and both give the same error, I’m possibly going to try 4.3.x, 4.2.x even 4.1.x if the previous 2 also produce the error.
Thanks
commit 65b5e0455b58461e6597b3032b3a33925bd7b0b5
Author: Peter Barker <pbarker@barker.dropbear.id.au>
Date: Thu Dec 12 12:57:48 2019 +1100
GCS_MAVLink: warn if GCS send MISSION_ITEM rather than MISSION_ITEM_INT
I’m a touch concerned about that mission not working. Can you upload a textual copy of the mission here somehow?
I’ll upload everything I can in the morning, it’s 1.30am here now, and the missus would kill me if I start messing with it now.
I’ll grab screenshots of the mission, error messages in the app, log files if there’s any, and anything else that I can find.
Is there anything in particular that would be more helpful?
Hi @sbbrs,
Not sure how new you are to ArduPilot but of course, after the mission upload the vehicle needs to be put into Auto mode and it also needs a good GPS lock.
An onboard log would be best if possible.
I’m fairly new to ArduPilot, the vehicle was in Auto mode via a 3 position switch on the handset (Auto/Manual/RTL), and I had around 20 sats and a GPS Fix according to the CPP app.
The log files from both the Pixhawk and the Carp Pilot Pro app are here
Hi @sbbrs,
Txs for the logs. A few things I’ve noticed:
- Autopilot is using ArduPilot-4.5.0 (ArduRover V4.5.0 (53ad2c2a)). This is quite old so you might as well upgrade to 4.7.0. At least upgrading to 4.5.7 which was the last minor update to 4.5.
- The fmuv2 firmware is loaded but the vehicle has 2MB of RAM so the fmuv3 firmware will fit and will provide more features. To upgrade to the fmuv3 firmware you’ll need to specify the board using Mission Planner’s “all options” link or use the custom build server
For some of the logs the vehicle remains in Manual mode but the one starting with 122 the vehicle does switch to Auto mode and it looks like its motor outputs move so I think it’s trying to execute the mission. To me this means that the warning is perhaps being printed but it’s just a warning.
What Flight Controller is this?
Indeed, we actually prefer if users use the firmware specifically built for their autopilot instead of using the generic fmuv2 and fmuv3 firmwares.