diff --git a/libraries/GCS_MAVLink/message_definitions/ardupilotmega.xml b/libraries/GCS_MAVLink/message_definitions/ardupilotmega.xml index acd8381c8a..036d294f82 100644 --- a/libraries/GCS_MAVLink/message_definitions/ardupilotmega.xml +++ b/libraries/GCS_MAVLink/message_definitions/ardupilotmega.xml @@ -244,152 +244,6 @@ - - - - Gimbal is powered on but has not started initializing yet - - - - Gimbal is currently running calibration on the pitch axis - - - - Gimbal is currently running calibration on the roll axis - - - - Gimbal is currently running calibration on the yaw axis - - - - Gimbal has finished calibrating and initializing, but is relaxed pending reception of first rate command from copter - - - - Gimbal is actively stabilizing - - - - Gimbal is relaxed because it missed more than 10 expected rate command messages in a row. Gimbal will move back to active mode when it receives a new rate command - - - - - - Gimbal yaw axis - - - - Gimbal pitch axis - - - - Gimbal roll axis - - - - - - Axis calibration is in progress - - - - Axis calibration succeeded - - - - Axis calibration failed - - - - - - Tests to make sure each axis can move to its mechanical limits - - - - - - Whether or not this axis requires calibration is unknown at this time - - - - This axis requires calibration - - - - This axis does not require calibration - - - - - - - No GoPro connected - - - - The detected GoPro is not HeroBus compatible - - - - A HeroBus compatible GoPro is connected - - - - A HeroBus compatible GoPro is connected - - - - A HeroBus compatible GoPro is connected and recording - - - - A HeroBus compatible GoPro is connected and overtemperature - - - - A HeroBus compatible GoPro is connected and storage is missing or full - - - - - - The write message with ID indicated failed - - - - The write message with ID indicated succeeded - - - - - - (Get/Set) - - - - (Get/Set) - - - - (___/Set) - - - - (Get/___) - - - - (Get/___) - - - - (Get/___) - - - @@ -932,153 +786,8 @@ D component - - 3 axis gimbal mesuraments - System ID - Component ID - Time since last update (seconds) - Delta angle X (radians) - Delta angle Y (radians) - Delta angle X (radians) - Delta velocity X (m/s) - Delta velocity Y (m/s) - Delta velocity Z (m/s) - Joint ROLL (radians) - Joint EL (radians) - Joint AZ (radians) - + - - Control message for rate gimbal - System ID - Component ID - Demanded angular rate X (rad/s) - Demanded angular rate Y (rad/s) - Demanded angular rate Z (rad/s) - - - - Causes the gimbal to reset and boot as if it was just powered on - System ID - Component ID - - - - Reports progress and success or failure of gimbal axis calibration procedure - Which gimbal axis we're reporting calibration progress for - The current calibration progress for this axis, 0x64=100% - The status of the running calibration - - - - Instructs the gimbal to set its current position as its new home position. Will primarily be used for factory calibration - System ID - Component ID - - - - Sent by the gimbal after it receives a SET_HOME_OFFSETS message to indicate the result of the home offset calibration - The result of the home offset calibration - - - - Set factory configuration parameters (such as assembly date and time, and serial number). This is only intended to be used during manufacture, not by end users, so it is protected by a simple checksum of sorts (this won't stop anybody determined, it's mostly just to keep the average user from trying to modify these values. This will need to be revisited if that isn't adequate. - System ID - Component ID - Magic number 1 for validation - Magic number 2 for validation - Magic number 3 for validation - Assembly Date Year - Assembly Date Month - Assembly Date Day - Assembly Time Hour - Assembly Time Minute - Assembly Time Second - Unit Serial Number Part 1 (part code, design, language/country) - Unit Serial Number Part 2 (option, year, month) - Unit Serial Number Part 3 (incrementing serial number per month) - - - - Sent by the gimbal after the factory parameters are successfully loaded, to inform the factory software that the load is complete - Dummy field because mavgen doesn't allow messages with no fields - - - - Commands the gimbal to erase its firmware image and flash configuration, leaving only the bootloader. The gimbal will then reboot into the bootloader, ready for the load of a new application firmware image. Erasing the flash configuration will cause the gimbal to re-perform axis calibration when a new firmware image is loaded, and will cause all tuning parameters to return to their factory defaults. WARNING: sending this command will render a gimbal inoperable until a new firmware image is loaded onto it. For this reason, a particular "knock" value must be sent for the command to take effect. Use this command at your own risk - System ID - Component ID - Knock value to confirm this is a valid request - - - - Command the gimbal to perform a series of factory tests. Should not be needed by end users - System ID - Component ID - - - - Reports the current status of a section of a running factory test - Which factory test is currently running - Which section of the test is currently running. The meaning of this is test-dependent - The progress of the current test section, 0x64=100% - The status of the currently executing test section. The meaning of this is test and section-dependent - - - - Requests the calibration status for all gimbal axes. Should result in a GIMBAL_REPORT_AXIS_CALIBRATION_STATUS message being generated by the gimbal - System ID - Component ID - - - - Reports the calibration status for each gimbal axis (whether the axis requires calibration or not) - Whether or not the yaw axis requires calibration, see GIMBAL_AXIS_CALIBRATION_REQUIRED enumeration - Whether or not the pitch axis requires calibration, see GIMBAL_AXIS_CALIBRATION_REQUIRED enumeration - Whether or not the roll axis requires calibration, see GIMBAL_AXIS_CALIBRATION_REQUIRED enumeration - - - - Requests any currently uncalibrated gimbal axes to run the axis calibration procedure. An axis is considered uncalibrated if its commutation calibration slope and intercept are 0 - System ID - Component ID - - - - - - Heartbeat from a HeroBus attached GoPro - Status - - - - Request a GOPRO_COMMAND response from the GoPro - System ID - Component ID - Command ID - - - - Response from a GOPRO_COMMAND get request - Command ID - Value - - - - Request to set a GOPRO_COMMAND with a desired - System ID - Component ID - Command ID - Value - - - - Response from a GOPRO_COMMAND set request - Command ID - Result - - - RPM sensor output RPM Sensor1