Hi all,
When performing automated flights I always receive the following vehicle error per waypoint: “Rejecting mission request command, component or system ID mismatch”. Although the error is there the drone still completes the mission. As QGC operator it is annoying to receive these errors.
I traced the error down in the source code of the PX4 firmware, it relates to the mavlink_mission.cpp file (located at: \src\modules\mavlink). However I do not understand the check that is executed to trigger this error. It seems to me that the QGC is requesting something via MAVLink which is not available.
Hi @Quincy. Are you sending the mission plan from QGC or you uploading the plan by using mavlink middleware like MAVSDK,MAVROS etc. ? Have you checked the MAV_SYS_ID ?
Hi @Alp_Ucan , many thanks to reach out. I make the flightplans, geofence etc. directly in QGC. I do not use any middleware. I checked MAV_SYS_ID in my parameter file and it is equal to “1” (default value).
Because QGC sending seperate mavlink packet (MISSION_ITEM_INT) to vehicle for each mission item and due to ID mismatch each time it is throwing warning.
As far as I know QGC using MAV_SYS_ID and MAV_COMP_ID values while filling out these sections in the message default (1,1). You can check more detail about sys_id and comp_id from this link: https://mavlink.io/en/services/mavlink_id_assignment.html
Interesting part is I’m using 1.14.3 too and I tried to send mavlink command and mission both from QGC and middleware app. but there is no warning. Did you try different QGC version ? I’m using 4.3.0.
The MAV_SYS_ID and MAV_COMP_ID need to be same. In my parameter file they are both equal to 1 (default value). I only use one Autopilot and one QGC station.
I do not use gimballs, cameras etc. via MAVLink.
I did not try another QGC version yet, I use QGC 4.4.1, do you recommend going higher or lower in versions? I will try your version anyway. On the QGC MAVLink setting page I have 255 as MAVLink system ID (default).
How did you test the mission command? Did you perform a flight? Indoor I can upload the flight path and geofence without errors. In simulation the errors are not there. However the error appeared when performing outdoor flight tests, when the machine was going toward it first way point. I’m now looking how I can reproduce these errors with a machine without propellors for debugging purposes.
While uploading mission we were using some different way. QGC was uploading coming waypoints from a uORB topic instead of appearing ones on plan screen. This change was made in source code. And we performed many flights.
I’m not sure but actually your setup is quite clear it should work without any error so I suspected new version of QGC If older version of QGC works please share it. Good luck.
I was able to retrieve the same errors while simulating an outdoor flight, without props on the machine. I uploaded the geofence + flight plan via QGC and launched the flight via QGC.
I tested first with the latest QGC version, 4.4.2, and retrieved the errors when going (manually moving the drone) for the first way point. I then installed version 4.3.0 and performed the same test and the errors did not pop up! @Alp_Ucan , thanks for the support! Maybe something to look into for a new release of QGC?
I examind the mavlink mission part in source code actually I would expect mission would not uploaded succesfuly while observing this warning. If I can debug to understand more detailed I will share. I don’t have enough info about QGC side but it’s look like there is an issue about mavlink packet generation. May be someone more experienced can make more accurate comment. If you can create an issue under QGC project it would be great. Have a nice day.
If older version of QGC works please share it. Good luck.