You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Excception in message for Heartbeat each time i connect the Gimal #985
Hello, I'm having an error each time i connect the gimbal (STorM32), to the pixhawk :
raise APIException: mode (6, 0) not available on mavlink definition
ERROR:dronekit:Exception in message handler for HEARTBEAT
raise APIException("mode (%s, %s) not available on mavlink definition" % (m.custom_mode, m.base_mode))
APIException: mode (6, 0) not available on mavlink definition
CRITICAL:autopilot:STorM32 v0.96 v1.30 F103RC
CRITICAL:autopilot:OlliW 323BGC
It sure does seem like this project was abandoned. The last update to master was in November and I submitted the PR to fix this issue back then. Who knows what's happening.
Hi, I'm having this same problem. Pixhawk 2.1 with Storm32 gimbal, using latest dronekit and ardupilot versions, followed the steps here and verified that the gimbal does respond to RC's ch7 and moves accordingly, however, when trying it out with python it doesn't move (it does read the gimbal position correctly though), and it raises this exception:
**raise APIException("mode (%s, %s) not available on mavlink definition" % (m.custom_mode, m.base_mode))
dronekit.APIException: mode (6, 128) not available on mavlink definition**
Activity
Guohao91 commentedon Nov 14, 2019
same problem
activexray commentedon Jan 16, 2020
It sure does seem like this project was abandoned. The last update to master was in November and I submitted the PR to fix this issue back then. Who knows what's happening.
bobn3 commentedon Feb 14, 2020
Hi, I'm having this same problem. Pixhawk 2.1 with Storm32 gimbal, using latest dronekit and ardupilot versions, followed the steps here and verified that the gimbal does respond to RC's ch7 and moves accordingly, however, when trying it out with python it doesn't move (it does read the gimbal position correctly though), and it raises this exception:
dronekit.APIException: mode (6, 128) not available on mavlink definition**