Skip to content

Commit e0c355c

Browse files
committed
Common: Update Rockblock usage
1 parent c9bd945 commit e0c355c

File tree

1 file changed

+48
-24
lines changed

1 file changed

+48
-24
lines changed

common/source/docs/common-telemetry-rockblock.rst

Lines changed: 48 additions & 24 deletions
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ Due to the very low datarate of the RockBLOCK, there are a few key limitations:
1919

2020
- A single `HIGH_LATENCY2 <https://mavlink.io/en/messages/common.html#HIGH_LATENCY2>`__ packet will be sent every ``RCK_PERIOD`` sec. This will give basic position and status information.
2121
- No heartbeats, statustexts, parameters and waypoints will be sent from the vehicle to the GCS.
22-
- The RockBLOCK only sends a subset of command MAVlink messages (see below list) from the GCS to Vehicle. Parameters and waypoints will not be sent.
22+
- The RockBLOCK only sends a subset of MAVlink messages (see below list) from the GCS to Vehicle. Parameters and waypoints will not be sent.
2323
- Only 1 command message can be sent per ``RCK_PERIOD`` from the GCS to vehicle. Any additional commands will overwrite the previous command
2424

2525
In practice, this means the RockBLOCK can only be used whilst monitoring a vehicle during automated flight modes. Any sort
@@ -28,36 +28,59 @@ of manual control (outside of low-rate GUIDED mode "fly to" locations) is not po
2828
The RockBLOCK has a latency of 20-60 seconds and is only able to send 1 message per 30 second period (or greater). This period is
2929
configurable via the ``RCK_PERIOD`` parameter.
3030

31+
If desired, the RockBlock can automatically activate on loss-of-GCS-telemetry. This is done by setting the ``RCK_FORCEHL`` parameter to 2.
32+
The RockBLOCK will then automatically activate when telemetry is lost for ``RCK_TIMEOUT`` seconds. When telemetry is restored,
33+
the RockBLOCK will deactivate.
34+
3135
.. note:: Any modem using the Iridium 9602 or 9603 chipset *should* work, though only the RockBLOCK 9603N modem has been tested.
3236

33-
Supported MAVLink command messages
34-
==================================
37+
Supported MAVLink messages
38+
==========================
3539

36-
- CMD_NAV_RETURN_TO_LAUNCH
37-
- CMD_NAV_LAND
38-
- CMD_NAV_TAKEOFF
39-
- CMD_NAV_VTOL_TAKEOFF
40-
- CMD_NAV_VTOL_LAND
41-
- CMD_DO_SET_MODE
42-
- CMD_MISSION_START
43-
- CMD_COMPONENT_ARM_DISARM
44-
- CMD_CONTROL_HIGH_LATENCY
40+
The following MAVLink messages are supported from the GCS to the vehicle:
4541

46-
Setup
47-
=====
42+
- COMMAND_LONG
43+
- COMMAND_INT
44+
- MISSION_ITEM_INT
45+
- MISSION_SET_CURRENT
46+
47+
Within the COMMAND_LONG and COMMAND_INT messages, the following commands are supported:
4848

49-
Due to limitations of the RockBLOCK web service, all packets in the Vehicle to GCS direction need to go via a public-facing web service.
50-
See `here <https://docs.rockblock.rock7.com/docs/integration-with-application>`__ for details.
51-
For the purposes of this configuration, the free `adafruit.io <https://io.adafruit.com/>`__ service is used.
49+
- MAV_CMD_NAV_RETURN_TO_LAUNCH
50+
- MAV_CMD_NAV_LAND
51+
- MAV_CMD_NAV_TAKEOFF
52+
- MAV_CMD_NAV_VTOL_TAKEOFF
53+
- MAV_CMD_NAV_VTOL_LAND
54+
- MAV_CMD_DO_SET_MODE
55+
- MAV_CMD_DO_CHANGE_SPEED
56+
- MAV_CMD_DO_SET_SERVO
57+
- MAV_CMD_DO_PARACHUTE
58+
- MAV_CMD_MISSION_START
59+
- MAV_CMD_COMPONENT_ARM_DISARM
60+
- MAV_CMD_DO_REPOSITION
61+
- MAV_CMD_CONTROL_HIGH_LATENCY
62+
63+
Vehicle Setup
64+
============
5265

5366
#. Connect the RockBLOCK modem to a spare UART on the flight controller. Only the +5V, RX, TX and GND lines need to be connected
5467
#. Ensure the modem is activated in your RockBLOCK account
55-
#. Create a `new feed on adafuit.io <https://learn.adafruit.com/using-the-rockblock-iridium-modem/forwarding-messages>`__. Ensure the Feed History is OFF and a webhook is active. Connect this feed to your RockBLOCK account.
5668
#. Copy the `Ardupilot RockBLOCK Lua script <https://github.com/ArduPilot/ardupilot/blob/master/libraries/AP_Scripting/applets/RockBlock.lua>`__ to the flight controller's SD card.
5769
#. Ensure :ref:`LUA Scripts<common-lua-scripts>` are enabled and the RockBLOCK UART is set as a scripting UART.
58-
#. Run the RockBLOCK gateway `rockblock2mav.py <https://github.com/stephendade/rockblock2mav>`__ on the GCS to send/receive telemetry on 127.0.0.1:16000. Ensure the GCS software is connected to this ip/port.
5970

60-
.. note:: QGroundControl and Mission Planner have very limited support for RockBLOCK MAVLink telemetry. It is highly recommended to use MAVProxy, which fully supports this telemetry.
71+
72+
Ground Setup
73+
============
74+
75+
The RockBLOCK messages are sent and received via the Rock7 gateway. It has an API that allows for
76+
sending and receiving messages via a web service.
77+
78+
The `Rockblock2MAV <https://github.com/stephendade/rockblock2mav>`__ software is a companion to the RockBlock Lua
79+
script. Use this software on the GCS to send and receive MAVLink messages from the RockBLOCK modem via the Rock7 gateway.
80+
81+
See the `Rockblock2MAV documentation <https://github.com/stephendade/rockblock2mav>`__ for installation and usage instructions.
82+
83+
.. note:: QGroundControl and Mission Planner have limited support for RockBLOCK MAVLink telemetry. It is recommended to use MAVProxy, which fully supports this telemetry.
6184

6285

6386
Usage
@@ -87,12 +110,13 @@ Parameters
87110

88111
The following parameters are available to control the script:
89112

90-
======================== ==========================================================================
113+
======================== ============================================================================================
91114
Name Description
92-
======================== ==========================================================================
93-
RCK_FORCEHL Automatically enables High Latency mode if not already enabled
115+
======================== ============================================================================================
116+
RCK_FORCEHL Mode of operation. 0 = start disabled, 1 = start enabled, 2 = enabled on loss of telemetry
94117
RCK_PERIOD When in High Latency mode, send RockBLOCK updates every RCK_PERIOD seconds
95118
RCK_DEBUG Sends RockBLOCK debug text to GCS via statustexts
96119
RCK_ENABLE Enables the modem transmission
97-
======================== ==========================================================================
120+
RCK_TIMEOUT When RCK_FORCEHL=2, the number of seconds of no telemetry until High Latency mode is enabled
121+
======================== ============================================================================================
98122

0 commit comments

Comments
 (0)