Using STorM32 with ArduPilot

The information on this page refers to firmware v2.48e and BetaPilot 4.0 v002, and higher.

The STorM32 gimbal controller can communicate with an ArduPilot flight controller via a serial UART data line. The serial communication allows for a much richer data transmission and accordingly richer set of features than possible with the traditional PWM connections. Examples are advanced control functions, the STorM32-Link or the NT Camera features. It also can lead to a much cleaner wiring.

If you just need the range of functionality possible with the standard tilt & pan control, then you don't need anything of the following, and you may stop reading here. Also, some of the features discussed below can be accomplished by workarounds. Decide yourself which approach fits your needs best. :)

STorM32 - ArduPilot Support

ArduPilot offers two mount types, which can be used with the STorM32 controller, the SToRM32 MAVLink (MNT_TYPE = 4) and SToRM32 Serial (MNT_TYPE = 5) mounts. For further details please visit ArduPilot Docs > Copter > Optional Hardware > Camera&Gimbals > SToRM32 Gimbal Controller.

Comment: Unfortunately, ArduPilot's gimbal support is partially flawed. That is, many features you will find to work great, but some you will find to not work well. STorM32 can't do anything about it, it's ArduPilot. Please also note that the STorM32 firmware author is not responsible for the implementation of the above mounts; again, it's ArduPilot.

The BetaPilot fork of ArduPilot additionally offers the STorM32 MAVLink2 (MNT_TYPE = 83) mount type, which provides the best range of functions.

A comparison of the different techniques to connect the STorM32 controller with the flight controller is given in the following feature matrix.

Feature Matrix

(to the best of the authors knowledge)

Feature	PWM	SToRM32 MAVLink	SToRM32 Serial	STorM32 MAVLink2
Gimbal Angle Control	x	x (?)	x	x
Solo Smart Shots	x	-	-	x
MAV_MOUNT_STATUS message	-	x (1)	x (2)	x
Camera Trigger	x	x	-	x
Gimbal Point in MP	-	x	x (2)	x
Camera Manager in QGC	-	x (3)	-	x
MAVLink Parameters	-	x	-	x
Video on/off	-	-	-	x
360° Gimbal with Free Look	-	-	-	x
STorM32 Functions	-	-	-	x
STorM32 Scripts	-	-	-	x
STorM32-Link: Horizon Drift Comp.	-	-	-	x (4)
STorM32-Link: Yaw Drift Comp.	-	-	-	x (4)
Passthrough Configuration	-	-	-	x
MAVLink Camera Micro Service	-	-	-	x
MAVLink Advanced Features	-	-	-	x

(?) May or may not work properly in the latest ArduPilot releases. Please check with the ArduPilot community.

(1) The message reports the last set point, not the actual gimbal/camera orientation.

(2) Works only for deprecated v0.xx firmwares.

(3) Only elementary features work.

(4) Works only for T-STorM32 gimbals.

BetaPilot

Some modifications to the ArduPilot firmware were made and the result called BetaPilot, which provides simply the best support of STorM32 gimbals.

Comments:

• If you are satisfied with ArduPilot's gimbal support then there is really no need to use BetaPilot. However, if you want to make best use of STorM32 and want 2019-ish capabilities then you seriously want to chose BetaPilot.
• Before using BetaPilot it is strongly recommended to first install the original ArduPilot firmware and get the copter/plane flying flawlessly with it, and only then to install BetaPilot.

In order to establish a working communication between the STorM32 controller and the flight controller, parameters on both sides, BetaPilot and STorM32, need to be adjusted, as described in the following.

The BetaCopter fork implements the STorM32 MAVLink2 mount type, which handles all of the following features. If the STorM32 MAVLink2 mount is not activated, then the BetaPilot firmware will behave exactly like the original ArduPilot firmware, with no side effects.

STorM32 MAVLink2

---

The STorM32 controller needs to be connected via one of its UART ports to one of the UART ports on the flight controller, and these settings be made:

Settings in BetaPilot:

• MNT_TYPE = 83
• SERIALx_PROTOCOL = 2
• SERIALx_BAUD = 115

Settings in STorM32:

• Mavlink Gimbal = “Gimbal1” or higher
• Mavlink Gimbal Stream = “attitude” or higher
• Mavlink Uart Port = “uart” if the UART port is used (is default)

The other settings can normally be left at their default (a complete description of the configuration parameters is provided in the article MAVLink Communication);

With the mount activated, you should notice:

• In MissonPlanner or any other ground control station an additional MAVLink component named GIMBAL will be present.
• In the STorM32 [GUI:Dashboard], the MAVLINK field will show PRESENT.
• In the STorM32[GUI:Dashboard], the STorM32-Link, providing horizon drift and yaw drift compensation, and additional features, is present.

Comment: The default baudrate of the STorM32 serial ports is 115200 bps, hence in ArduPilot SERIALx_BAUD has to be set to 115. However, other baudrates can be configured; for e.g. 230400 bps one sets the STorM32 parameter Uart Baudrate to “230400” and the ArduPilot parameter SERIALx_BAUD to 230.

STorM32 via UAVCAN

---

The STorM32 can also be connected via CAN bus to the ArduPilot flight controller. This option is mentioned here solely for completeness (details of the STorM32's UAVCAN support are described in the article UAVCAN).

STorM32-Link

---

Settings in STorM32:

• STorM32Link Configuration = “v1”

With setting MNT_TYPE = 83 also the STorM32-Link is activated (for details see STorM32-Link). That is, in addition to the 'conventional' data also the data required for the functioning of the STorM32-Link are emitted by the flight controller. The setting STorM32Link Configuration = “v1” makes the STorM32 using them. In the STorM32 GUI, specifically the [GUI:Dashboard] and/or the [GUI:Data Display], you should note that the STorM32-Link field goes to INUSE and OK.

Comment: If only the 'conventional' data but not the STorM32-Link data are received by the STorM32 controller, then an ISPRESENT and/or OK will be displayed to indicate that a working link has been established between STorM32 and BetaCopter, and that the 'conventional' control functions are all working. The INUSE flag will not appear, which indicates that the STorM32-Link, i.e., the horizon and yaw drift compensation feature, is not active.

Comment: The STorM32-Link is available only for T-STorM32 gimbals, but not the conventional STorM32 NT gimbals.

Virtual Channel Configuration

---

Settings in STorM32:

• Virtual Channel Configuration = “serial”

With this setting, all STorM32 functions can be invoked by selecting any of the “Virtual-1” - “Virtual-16” input channels, exactly as one would do it if the STorM32 controller would be directly connected to a receiver.

This allows us to do many useful things, such as activating a script or triggering video on/off from the transmitter. It however also allows us to do nonsense, and it is in the user's responsibility to avoid that. For instance, if ArduPilot is in Rc Targeting mode, and e.g. Rc Pitch Control is set to a virtual input channel, then the gimbal may move in funny ways since it may receive the transmitter stick information from both ArduPilot and the receiver. In contrast, if ArduPilot in GPS or ROI Targeting mode, then one gets "free look", which is useful and quite cool actually. As said, all this is exactly as if the receiver would be directly connected to the STorM32 controller on its RC ports.

Passthrough Configuration

---

This feature allows you to connect the STorM32 GUI to the USB or any serial (MAVLink enabled) port of the flight controller, and to directly communicate with the STorM32 gimbal.

This is extremely convenient for configuring STorM32 gimbals when they are e.g. installed permanently in the vehicle. This also works via a wireless telemetry link, and thus opens the option of e.g. tuning the gimbal during flight, and further unheard of possibilities for controlling the gimbal during flight.

This preliminary demo video demonstrates the pass-through feature:

Testing the Connection

The serial MAVLink connection can be tested in several ways. The following tests do not require that the vehicle is completely built and/or set up, and do not require that the vehicle is armed.

• MAVLINK field in the STorM32 GUI: The [GUI:Dashboard] haa a field named NAMVLINK. It should display PRESENT.

• STorM32-LINK field in the STorM32 GUI: The [GUI:Dashboard] and [GUI:Data Display] each have a field which is related to the STorM32-Link. They should display OK, PRESENT or a similar positive message.

• MissonPlanner or QGroundControl: An additional MAVLink component named GIMBAL should be present.

• Message box in MissonPlanner: With the GIMBAL component selected, in the message box several text messages related to the STorM32 should appear. In particular, a message like "STorM32 v2.40 nt v1.30 F103RC" informing about the STorM32 firmware version should be visible.