Hello,
I’m Chu, Working as firmware developer at the R&D department.
I was charged of developing the gimbal to be compatible with Flight Stack PX4 & Ardupilot.
After releasing beta firmware which supported gimbal interface with Flight Stack. I have been getting a lot of glitch.
We would like to make the gimbal becomes a component in drone’s ecosystem. Anyone has been using the Gimbal, please give us some suggestions to expand message support gimbal beside messages in advance. [http://ardupilot.org/dev/docs/code-overview-adding-support-for-a-new-mavlink-gimbal.html](http://)
Currently we have been supporting some message
- Gimbal receives messages:
- MAVLINK_MSG_ID_HEARTBEAT
- MAVLINK_MSG_ID_ATTITUDE
- MAVLINK_MSG_ID_COMMAND_LONG (command: MAV_CMD_DO_MOUNT_CONTROL)
- Gimbal sends messages:
- MAVLINK_MSG_ID_HEARTBEAT (1Hz)
- MAVLINK_MSG_ID_MOUNT_ORIENTATION (50Hz: Attitude gimbal)
We would like to associate to develop the rich messages support gimbal to interface with Flight Stack (Plug & play) through Mavlink2 protocol?
Drone is an indispensable part of the Gimbal in industrial application.
We really appreciate this cooperation and your business. we will be willing any organisation or developers want to associate with us. Please contact to me.