Using STorM32 with ArduPilot: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 8: | Line 8: | ||
* SERIAL_PROTOCOL = 1 | * SERIAL_PROTOCOL = 1 | ||
* MOUNT_TYPE = 4 | * MOUNT_TYPE = 4 | ||
* STorM32 heartbeat must be activated | * STorM32 heartbeat must be activated, {{PARAMNAME|Mavlink Configuration}} = {{PARAMVALUE|emit heartbeat}} or higher | ||
* available in ArduPilot and | * available in ArduPilot and BetaCopter | ||
=== STorM32 serial === | === STorM32 serial === | ||
| Line 15: | Line 15: | ||
* SERIAL_PROTOCOL = 8 | * SERIAL_PROTOCOL = 8 | ||
* MOUNT_TYPE = 5 (the arducopter docu is wrong here) | * MOUNT_TYPE = 5 (the arducopter docu is wrong here) | ||
* STorM32 heartbeat must be | * STorM32 heartbeat must be deactivated, {{PARAMNAME|Mavlink Configuration}} = {{PARAMVALUE|no heartbeat}} | ||
* available in ArduPilot and | * available in ArduPilot and BetaCopter | ||
=== STorM32 native === | === STorM32 native === | ||
| Line 22: | Line 22: | ||
* SERIAL_PROTOCOL = 83 | * SERIAL_PROTOCOL = 83 | ||
* MOUNT_TYPE = 83 | * MOUNT_TYPE = 83 | ||
* STorM32 heartbeat must be | * STorM32 heartbeat must be deactivated, {{PARAMNAME|Mavlink Configuration}} = {{PARAMVALUE|no heartbeat}} | ||
* available only in | * available only in BetaCopter | ||
== BetaCopter 3.4 | == BetaCopter 3.4 == | ||
I made some modification to ArduCopter AC3.4 | I made some modification to ArduCopter AC3.4 (dev of 3. Aug. 2016). However, unless the STorM32-specific features are not activated by a "secret key" 83, ArduCopter will - to the best of my knowledge - behave exactly like the original code. This means that - to the best of my knowledge - there is no additional risk in using BetaCopter instead of ArduCopter. | ||
For the following you need betacopter 3.4-dev v013 and o323bgc v2.09e. You can download them here: | For the following you need betacopter 3.4-dev v013 and o323bgc v2.09e. You can download them here: | ||
* o323bgc v2.09e: | * o323bgc v2.09e: | ||
* | * betacopter 3.4-dev v013: | ||
On the STorM32, the {{PARAMNAME|Mavlink Configuration}} parameter must be set to {{PARAMVALUE|no heartbeat}}. | On the STorM32, the {{PARAMNAME|Mavlink Configuration}} parameter must be set to {{PARAMVALUE|no heartbeat}}. | ||
| Line 39: | Line 39: | ||
=== ArduCopter SERIALx_PROTOCOL = 83 === | === ArduCopter SERIALx_PROTOCOL = 83 === | ||
As serial protocol you may choose 83, which activates | As serial protocol you may choose 83, which activates BetaCopter's native STorM32 protocol. SERIALx_BAUD must be set to 115. You should then notice this: | ||
* All ArduCopter | * All ArduCopter camera features are working. That is, whenever a certain path of actions (Mavlink, receiver, mission,...) lets ArduCopter think it wants to take a picture, the STorM32 will know and act. | ||
* In the Message box of MissonPlanner a "STorM32 ..." message will appear. This so-to-say tells you that the serial ArduCopter-STorM32 connection is working. | * In the Message box of MissonPlanner a "STorM32 ..." message will appear. This so-to-say tells you that the serial ArduCopter-STorM32 connection is working. | ||
Setting SERIALx_PROTOCOL = 83 is mandatory for any of the STorM32-specific features to work. That is, also the following features would not work without that setting. | |||
=== ArduCopter MNT_TYPE = 83 === | === ArduCopter MNT_TYPE = 83 === | ||
As mount type you may choose 83, which activates | As mount type you may choose 83, which activates BetaCopter's native STorM32 mount. In addition to the above you should then also notice this: | ||
* All ArduCopter | * All ArduCopter mount features are working. Well, that's mostly exactly what you get also with the other modes of operation, e.g. when using the Mavlink connection with ArduPilot. One enhancement of the 83 mode is however that also the Mavlink MAV_MOUNT_STATUS message is emitted, so that in e.g. MissionPlaner the camera orientation can be read off. Furthermore, see the next parameters. | ||
=== ArduCopter STORM_RC_TRGT === | === ArduCopter STORM_RC_TRGT === | ||
This is a new parameter. It allows to modify the behavior of the native STorM32 mount in the RC Targeting mode. A value of 0 sets it to the standard ArduPilot behavior, as you know it. In this setting, the camera motion is determined by the various MNT parameters. When set to 1, in contrast, the standard STorM32 behavior is obtained. Here, the camera motion is determined by STorM32's Rc Input parameter fields. That is, the camera responds to transmitter inputs in exactly the same way as you know it for the STorM32. I guess, after having gotten used to it, most will prefer this operation | This is a new parameter. It allows to modify the behavior of the native STorM32 mount in the RC Targeting mode. | ||
A value of 0 sets it to the standard ArduPilot behavior, as you know it. In this setting, the camera motion is determined by the various MNT parameters. When set to 1, in contrast, the standard STorM32 behavior is obtained. Here, the camera motion is determined by the STorM32's {{PARAMNAME|Rc Input}} parameter fields. That is, the camera responds to transmitter inputs in exactly the same way as you know it for the STorM32. I guess, after having gotten used to it, most will prefer this operation mode. It is also somewhat more robust against rc failsafes. | |||
=== ArduCopter STORM_HAS_PAN === | === ArduCopter STORM_HAS_PAN === | ||
This is a new parameter. It allows to set the has_pan_control flag of the native STorM32 mount to 0:false or 1:true. It is not clear to me what this flag does (for the other mounts it is set to false). From the code I speculate that when false the copter will yaw along with a yaw command to the gimbal, while when true the copter isn't affected by a yawing mount. If so, the latter would enable a free 360° panning independent on the copter as expected for 360° gimbals (see e.g. digaus' tracking work). Anyway, whatever this flag does, it will be interesting to figure it out. | |||
This is a new parameter. It allows to set the has_pan_control flag of the native STorM32 mount to 0:false or 1:true. | |||
It is not totally clear to me what this flag does (for the other mounts it is set to false). From the code I speculate that when false the copter will yaw along with a yaw command to the gimbal, while when true the copter isn't affected by a yawing mount. If so, the latter would enable a free 360° panning independent on the copter as expected for 360° gimbals (see e.g. digaus' tracking work). Anyway, whatever this flag does, it will be interesting to figure it out. | |||
=== STorM32 Virtual Channel Configuration = serial === | === STorM32 Virtual Channel Configuration = serial === | ||
The STorM32's {{PARAMNAME|Virtual Channel Configuration}} parameter can be set to {{PARAMVALUE|serial}}. | The STorM32's {{PARAMNAME|Virtual Channel Configuration}} parameter can be set to {{PARAMVALUE|serial}}. This enables this feature: | ||
* All STorM32 Functions can be invoked by selecting a | * All STorM32 [[Inputs and Functions|functions]] can be invoked by selecting a {{PARAMVALUE|Virtual-1}} - {{PARAMVALUE|Virtual-16}} input channel, as if the STorM32 would be directly connected to the receiver. This allows doing many useful things, such as activating a script or triggering video on/off from the transmitter. It however also allows doing nonsense, e.g. if the ArduCopter mount is activated and is in Rc Targeting mode, and a RC input control, e.g. {{PARAMNAME|Rc Pitch}}, is set to a virtual input channel, then the gimbal will move in funny ways since it receives the transmitter stick information from two different sides. In contrast, if the ArduCopter mount is in GPS or ROI Targeting mode, when one gets "free look", which is useful and quite cool actually. As said, all that is exactly as if the receiver would be directly connected to the STorM32 on its RC ports. | ||
=== STorM32-Link === | === STorM32-Link === | ||
With SERIALx_PROTOCOL = 83 you should also note that in the STorM32 GUI, specifically the Dashboard and/or DataDisplay, the STorM32-Link field goes ON (if you want to know what STorM32-Link is about, see http://www.rcgroups.com/forums/showthread.php?t=2395475). The STorM32-Link functionality is actually not yet implemented in v2.09e, but this enabled field means that the STorM32-Link is working, and the crucial basis is established. From a practical perspective, you may use that field to check if the connection from your flight controller to the | With SERIALx_PROTOCOL = 83 you should also note that in the STorM32 GUI, specifically the Dashboard and/or DataDisplay, the STorM32-Link field goes ON (if you want to know what STorM32-Link is about, see http://www.rcgroups.com/forums/showthread.php?t=2395475). The STorM32-Link functionality is actually not yet implemented in v2.09e, but this enabled field means that the STorM32-Link is working, and the crucial basis is established. From a practical perspective, you may use that field to check if the connection from your flight controller to the STorM32 is working. | ||
Revision as of 08:42, 4 August 2016
STorM32 - ArduPilot Support
Three modes of operation are currently available:
STorM32 Mavlink
- SERIAL_PROTOCOL = 1
- MOUNT_TYPE = 4
- STorM32 heartbeat must be activated, Mavlink Configuration = “emit heartbeat” or higher
- available in ArduPilot and BetaCopter
STorM32 serial
- SERIAL_PROTOCOL = 8
- MOUNT_TYPE = 5 (the arducopter docu is wrong here)
- STorM32 heartbeat must be deactivated, Mavlink Configuration = “no heartbeat”
- available in ArduPilot and BetaCopter
STorM32 native
- SERIAL_PROTOCOL = 83
- MOUNT_TYPE = 83
- STorM32 heartbeat must be deactivated, Mavlink Configuration = “no heartbeat”
- available only in BetaCopter
BetaCopter 3.4
I made some modification to ArduCopter AC3.4 (dev of 3. Aug. 2016). However, unless the STorM32-specific features are not activated by a "secret key" 83, ArduCopter will - to the best of my knowledge - behave exactly like the original code. This means that - to the best of my knowledge - there is no additional risk in using BetaCopter instead of ArduCopter.
For the following you need betacopter 3.4-dev v013 and o323bgc v2.09e. You can download them here:
- o323bgc v2.09e:
- betacopter 3.4-dev v013:
On the STorM32, the Mavlink Configuration parameter must be set to “no heartbeat”.
These settings to parameter fields are available.
ArduCopter SERIALx_PROTOCOL = 83
As serial protocol you may choose 83, which activates BetaCopter's native STorM32 protocol. SERIALx_BAUD must be set to 115. You should then notice this:
- All ArduCopter camera features are working. That is, whenever a certain path of actions (Mavlink, receiver, mission,...) lets ArduCopter think it wants to take a picture, the STorM32 will know and act.
- In the Message box of MissonPlanner a "STorM32 ..." message will appear. This so-to-say tells you that the serial ArduCopter-STorM32 connection is working.
Setting SERIALx_PROTOCOL = 83 is mandatory for any of the STorM32-specific features to work. That is, also the following features would not work without that setting.
ArduCopter MNT_TYPE = 83
As mount type you may choose 83, which activates BetaCopter's native STorM32 mount. In addition to the above you should then also notice this:
- All ArduCopter mount features are working. Well, that's mostly exactly what you get also with the other modes of operation, e.g. when using the Mavlink connection with ArduPilot. One enhancement of the 83 mode is however that also the Mavlink MAV_MOUNT_STATUS message is emitted, so that in e.g. MissionPlaner the camera orientation can be read off. Furthermore, see the next parameters.
ArduCopter STORM_RC_TRGT
This is a new parameter. It allows to modify the behavior of the native STorM32 mount in the RC Targeting mode.
A value of 0 sets it to the standard ArduPilot behavior, as you know it. In this setting, the camera motion is determined by the various MNT parameters. When set to 1, in contrast, the standard STorM32 behavior is obtained. Here, the camera motion is determined by the STorM32's Rc Input parameter fields. That is, the camera responds to transmitter inputs in exactly the same way as you know it for the STorM32. I guess, after having gotten used to it, most will prefer this operation mode. It is also somewhat more robust against rc failsafes.
ArduCopter STORM_HAS_PAN
This is a new parameter. It allows to set the has_pan_control flag of the native STorM32 mount to 0:false or 1:true.
It is not totally clear to me what this flag does (for the other mounts it is set to false). From the code I speculate that when false the copter will yaw along with a yaw command to the gimbal, while when true the copter isn't affected by a yawing mount. If so, the latter would enable a free 360° panning independent on the copter as expected for 360° gimbals (see e.g. digaus' tracking work). Anyway, whatever this flag does, it will be interesting to figure it out.
STorM32 Virtual Channel Configuration = serial
The STorM32's Virtual Channel Configuration parameter can be set to “serial”. This enables this feature:
- All STorM32 functions can be invoked by selecting a “Virtual-1” - “Virtual-16” input channel, as if the STorM32 would be directly connected to the receiver. This allows doing many useful things, such as activating a script or triggering video on/off from the transmitter. It however also allows doing nonsense, e.g. if the ArduCopter mount is activated and is in Rc Targeting mode, and a RC input control, e.g. Rc Pitch, is set to a virtual input channel, then the gimbal will move in funny ways since it receives the transmitter stick information from two different sides. In contrast, if the ArduCopter mount is in GPS or ROI Targeting mode, when one gets "free look", which is useful and quite cool actually. As said, all that is exactly as if the receiver would be directly connected to the STorM32 on its RC ports.
STorM32-Link
With SERIALx_PROTOCOL = 83 you should also note that in the STorM32 GUI, specifically the Dashboard and/or DataDisplay, the STorM32-Link field goes ON (if you want to know what STorM32-Link is about, see http://www.rcgroups.com/forums/showthread.php?t=2395475). The STorM32-Link functionality is actually not yet implemented in v2.09e, but this enabled field means that the STorM32-Link is working, and the crucial basis is established. From a practical perspective, you may use that field to check if the connection from your flight controller to the STorM32 is working.