dronekit.APIException: mode (0, 0) not available on mavlink definition

Hacky · 16 August 2022 07:34

Sounds like the problem with ADSB crosstalk, see also:

dronekit.APIException: mode (0, 4) not available on mavlink definition

opened 08:37PM - 24 Apr 20 UTC

Hello all, I am running arduplane 4.1.X with dronekit 2.9.2 and pymavlin…k 2.4.4. When I run the SITL sim_vehicle.py and connect the vehicle_state.py example code every thing works as it should. Now when I run the vehicle_state.py on an RPI connected to a cube orange I get the following error message: ERROR:dronekit:Exception in message handler for HEARTBEAT Traceback (most recent call last): File "/usr/local/lib/python3.5/dist-packages/dronekit/__init__.py", line 1531, in notify_message_listeners fn(self, name, msg) File "/usr/local/lib/python3.5/dist-packages/dronekit/__init__.py", line 1223, in listener raise APIException("mode (%s, %s) not available on mavlink definition" % (m.custom_mode, m.base_mode)) dronekit.APIException: mode (0, 4) not available on mavlink definition From this error I see that from the real pixhawk m.custom_mode =0 and m.base_mode=4 Since the SITL is working I went into the dronekit __init__.py file and added some print statements to tell me what m.custom_mode and m.base_mode is when running with the SITL. When running dronekit connected to SITL: m.custom_mode = 2 m.base_mode = 81 I am not sure why custom and base mode values are different when I run connected to a pixhawk cube orange. I have tried building dronekit from source based on similar issues that are already on github but this did not make a difference. I know @peterbarker mentioned this might be a problem with multiple connections in this link https://github.com/dronekit/dronekit-python/issues/677 but I think this error is something different. Any help would be greatly appreciated

But you seemed to have reconfigured serial5 already, so I have also no additional hints.