Skip to main content
Back to documentation homeShared serial reference

AT commands,
consolidated.

Browse the complete command set for RockREMOTE Mini, RockBLOCK Pro and RockFLEET Assured, then filter it by category, device or service.

38 command tables

Using the AT interface

The AT command set provides local device control, configuration, firmware maintenance, positioning and Mobile Originated (MO) and Mobile Terminated (MT) Iridium Messaging Transport (IMT) messaging.

Iridium Provisioning

Many commands require valid provisioning and may return an error until provisioning has been acquired. Position the Iridium antenna with a good view of the sky and leave the unit powered for at least 10 minutes so it can register and collect its provisioning information, including available IMT topics.

important

The serial interface supports several independent functions, including AT commands, C-Kermit file updates and NMEA streaming. Use one function at a time. For example, always turn NMEA streaming off before using AT commands or a serial firmware update.

Definitions

MO = Mobile Originated — a message sent from the device to the Iridium network.

MT = Mobile Terminated — a message received at the device from the Iridium network.

IMT = Iridium Messaging Transport Protocol — medium-sized messaging supporting up to 100 KB per message.

Serial settings

Default Baud speed 115200, 8 data bits, no parity and no flow control. RS232.

(Can be reconfigured following the User Configuration Guide for the appropriate device locally or remotely.)
For example:
Change mode from RS232 to RS4XX_FULL

info

Not applicable to RockFLEET Assured, please contact Ground Control Support

General behaviour

There is no response to strings or characters that are not defined in this reference. Every command must be prefixed with AT to be recognised.

important

Characters are not echoed back.

When the device is powered up or following a reboot, the AT interface displays a message of the day containing identificatory information, and sends the same to Cloudloop Device Manager.

tip

This can be toggled in the user configuration. As Cloudloop Startup Messages cost plan balance, however it is important to note that many Cloudloop Device Manager functionalities will not work until either a Startup Message has been received or the device's information has been requested and received.
Applicable from FWv0.18 onwards only.

Buffer limitations

The combined size of the MO and MT message buffers must be less than 3 MB. The maximum number of messages shared between both directions is approximately 6,000.

AT syntax and line termination

All commands use the following structure:

AT+CMD<CR>

AT is the command prefix, +CMD represents the proprietary command and <CR> is the carriage return that ends the line.

A contextual response uses this structure and always ends with OK<CR>:

+CMD: <Response Context><CR>
OK<CR>

A contextual error uses:

+CMD ERROR: <Error Num><CR>

An unsolicited response uses +CMD: <Unsolicited Context><CR>. Use AT+UNS to enable or disable unsolicited messages; they are enabled by default.

The maximum value for a TopicID or MessageID is 65535.

Typical IMT sequences

The following sequences show how a host normally sends an MO message and receives an MT message.

Typical IMT Mobile Originated sequence
Typical IMT MO sequence
Typical IMT Mobile Terminated sequence
Typical IMT MT sequence
Command catalogue

All AT commands

38 of 38 command tables shown

Refine the catalogue

Filter commands

Select more than one tag to combine filters. Results update immediately.

category
device
service

AT+CGMI

Get manufacturer string

  • Device information
  • RockREMOTE Mini
  • RockBLOCK Pro
  • RockFLEET Assured
  • Device
+CGMI
AT+CGMIReturns the device manufacturer string.
ExampleAT+CGMI
+CGMI: Ground Control
OK

AT+CGMM

Get model string

  • Device information
  • RockREMOTE Mini
  • RockBLOCK Pro
  • RockFLEET Assured
  • Device
+CGMM
AT+CGMMReturns the model string.
ExampleAT+CGMM
+CGMM: "RockREMOTE Mini"
OK
NotesReturns the “Variant” key from the device.cfg file

AT+CRTW

Get Rock 3 Words

  • Device information
  • RockREMOTE Mini
  • RockBLOCK Pro
  • RockFLEET Assured
  • Device
+CRTW
AT+CRTWReturns the Rock 3 Words - device serial number.
ExampleAT+CRTW
+CRTW: "mini.mini.me"
OK
Notes

AT+CPOW

Get power consumption

  • Device information
  • RockREMOTE Mini
  • RockBLOCK Pro
  • RockFLEET Assured
  • Device
CommandDescription
+CPOW
AT+CPOWReturns the average device power consumption in mW over the last second.
ExampleAT+CPOW
+CPOW: 285
OK
Notes

AT+CGCV

Get the application firmware version

  • Device information
  • RockREMOTE Mini
  • RockBLOCK Pro
  • RockFLEET Assured
  • Device
CommandDescription
+CGCV
AT+CGCVReturns the version number of the application firmware running on the device.
ExampleAT+CGCV
+CGCV: "0.6.1"
OK
Notes

AT+CMEM

Get available heap memory

  • Device information
  • RockREMOTE Mini
  • RockBLOCK Pro
  • RockFLEET Assured
  • Device
CommandDescription
AT+CMEMReturns the current amount of available heap memory reported by the device firmware.
Response+CMEM: <Available heap memory>
OK
ExampleAT+CMEM
+CMEM: 123456
OK
NotesThe reported value is intended for diagnostics and may vary during normal operation and between firmware versions.

AT+CIRV

Get the Iridium transceiver firmware version

  • Device information
  • RockREMOTE Mini
  • RockBLOCK Pro
  • RockFLEET Assured
  • Iridium
CommandDescription
+CIRV
AT+CIRVReturns the firmware version running on the Iridium transceiver.
ExampleAT+CIRV
+CIRV: "1.3.4"
OK
Notes

AT+CGSN

Get the Iridium 9770 transceiver IMEI

  • Device information
  • RockREMOTE Mini
  • RockBLOCK Pro
  • RockFLEET Assured
  • Iridium
+CGSN
AT+CGSNReturns the Iridium 9770 IMEI
ExampleAT+CGSN
+CGSN: "300058060009380"
OK
Notes

AT+CCID

Get the SIM ICCID string

  • Device information
  • RockREMOTE Mini
  • RockBLOCK Pro
  • RockFLEET Assured
  • Iridium
+CCID
AT+CCIDReturns the Iridium SIM ICCID
ExampleAT+CCID
+CCID: "8988169771000172669"
OK
NotesIf no SIM is present the response will be empty +CCID: ""

AT+CSQ

Get the signal level

  • Device information
  • RockREMOTE Mini
  • RockBLOCK Pro
  • RockFLEET Assured
  • Iridium

Iridium signal ranges from -100dBm (Excellent) to -120dBm (Worst)

+CSQ
AT+CSQReturns the Iridium Signal Level.
ExampleReturn signal in dBm and Signal Bars (0-5).
+CSQ: <dBm>,<Signal Bars>
AT+CSQ
+CSQ: -125,0
OK
NotesResponse of +CSQ: 0,0 is given when the modem has not provided a signal_level - i.e when constellation_visible is false

This usually means that at that time there was no satellite in view long enough to acquire a signal reading. More importantly the transceiver reports signal level of any current satellite in view not necessarily the satellite that would ultimately be used to transmit to. View Signal Strength FAQ

AT+APNTGS

Get the A-PNT module serial number

  • Device information
  • RockBLOCK Pro
  • RockFLEET Assured
  • A-PNT
A-PNT hardware only
+APNTGS
ExampleRetrieving the module serial number:
AT+APNTGS
+APNTGS: JL-03127
OK
Errors+APNTGS ERROR: <Error Num>

Error Numbers:
1 Serial Number not found (APNT Module not fitted or disabled)

Example:
AT+APNTGS
+APNTGS ERROR: 1
OK
Notes

AT+CETH

Configure Ethernet

  • Configuration
  • RockREMOTE Mini
  • Ethernet
CommandDescription
+CETH
AT+CETH
AT+CETH=0|1		Returns whether the Ethernet interface is currently enabled in the configuration.

Disables or enables the Ethernet interface in the configuration. Returns the configured state. Takes effect at next device restart.
ExampleAT+CETH
+CETH: 0
OK
AT+CETH=1
+CETH: 1
OK
Notes
Errors+CETH ERROR: 1

Incorrect option, 1 = On, 0 = Off

AT+CSUM

Configure startup messages

  • Configuration
  • RockREMOTE Mini
  • RockBLOCK Pro
  • RockFLEET Assured
  • Cloudloop
CommandDescription
+CSUM
AT+CSUM
AT+CSUM=0|1		Returns whether the Startup Messages are currently enabled in the configuration.

Disables or enables the Startup Messages to Cloudloop Device Manager in the configuration. Returns the configured state. Takes effect at next device restart.
ExampleAT+CSUM
+CSUM: 0
OK
AT+CSUM=1
+CSUM: 1
OK
Notes
Errors+CSUM ERROR: 1

Incorrect option, 1 = On, 0 = Off

AT+CFGR

Read user configuration

  • Configuration
  • RockREMOTE Mini
  • RockBLOCK Pro
  • RockFLEET Assured
  • Device
CommandDescription
+CFGR
AT+CFGRReturns current contents of the user configuration
ExampleAT+CFGR
{<JSON>}
OK
Errors+CFGR ERROR: <Error Num>

Error Numbers:
1 Unable to produce a valid configuration response.
Notes

AT+CFGW

Write user configuration

  • Configuration
  • RockREMOTE Mini
  • RockBLOCK Pro
  • RockFLEET Assured
  • Device
CommandDescription
+CFGW
AT+CFGW=<JSON>Writes a JSON string into user.cfg.
ExampleAT+CFGW={<SingleLineJSON>}
+CFGW:
OK
NotesJSON has to be formatted as a single line and contain the full configuration file
Errors+CFGW ERROR: <Error Num>

Error Nums:
1: Invalid Command format
2: Illegal message length
3: Bad JSON

AT+UNS

Configure unsolicited messages

  • Configuration
  • RockREMOTE Mini
  • RockBLOCK Pro
  • RockFLEET Assured
  • IMT

When unsolicited messages are disabled, the device will store only two IMT MT messages at any time, irrespective of their size.

If a new IMT MT message arrives when the buffer already contains two messages, the oldest stored message will be replaced with the newly arrived message.

+UNS=<Enable/Disable>
AT+UNS=Enable and disable unsolicited messages. When unsolicited messages are enabled, the AT interface will send unsolicited AT messages defined in the document. When disabled, it will not send any AT messages unsolicited.

<Enable>: 1 (Default)

<Disabled>: 0
ExampleAT+UNS=1
OK
NotesState is not persisted across power cycle.

AT+UNS with a payload that evaluates to 0 or 1 responds with OK and state is changed - additional input is ignored.
AT+UNS with a payload that evaluates to a number other than 0 or 1 responds with ERROR - additional input is ignored.
AT+UNS with a non-numeric value will disable unsolicited messages.

AT+UNS without a value will respond with current state:
AT+UNS
Response:
+UNS:1
OK
or
+UNS:0
OK

Correctly interprets values that start 0x and 0X.
Treats values in quotes as invalid.

AT+APNTCFG

Get the A-PNT module configuration

  • Configuration
  • RockBLOCK Pro
  • RockFLEET Assured
  • A-PNT
A-PNT hardware only
CommandDescription
AT+APNTCFGReturns the complete configuration and status information reported by the fitted A-PNT module.
Response+APNTCFG: <Module configuration and status>
OK
Errors+APNTCFG ERROR: <Error Num>

Error Numbers:
1 The A-PNT module is not fitted, disabled or unavailable.
2 The A-PNT module did not return its configuration.
NotesThe returned fields depend on the configuration and status reported by the fitted A-PNT module.

AT+APNTWK

Write a new A-PNT license key

  • Configuration
  • RockBLOCK Pro
  • RockFLEET Assured
  • A-PNT
A-PNT hardware only
+APNTWK=<key>
ExampleWriting a License Key:
AT+APNTWK=C5EXX2511RRR69W2ZMIT274V3111
+APNTWK:
OK
Errors+APNTWK ERROR: <Error Num>

Error Numbers:
1 Invalid APNT License Key
2 APNT License Key not provided

Example:
AT+APNTWK=7194
+APNTWK ERROR: 1
OK

AT+APNTWK=
+APNTWK ERROR: 2
OK
NotesWarning! This command will overwrite the existing License Key, +APNTUK can be used to revert back.

AT+APNTUK

Restore the previous A-PNT license key

  • Configuration
  • RockBLOCK Pro
  • RockFLEET Assured
  • A-PNT
A-PNT hardware only
+APNTUK
ExampleFallback to previous APNT License Key:
AT+APNTUK
+APNTUK:
OK
Errors+APNTUK ERROR: <Error Num>

Error Numbers:
1 APNT License Key not found (APNT Module not fitted or no existing key stored)

Example:
AT+APNTUK
+APNTUK ERROR: 1
OK
NotesWarning! +APNTUK will erase the current APNT License Key and fallback to the previous one, in a case where there is only one APNT License Key loaded, running this command may result in losing the only License Key.
+APNTWK can be used to write a new License Key.

AT+CTOK / AT+CRBT

Reboot

  • Firmware and maintenance
  • RockREMOTE Mini
  • RockBLOCK Pro
  • RockFLEET Assured
  • Device
CommandDescription
+CTOK and +CRBT
AT+CTOK
AT+CRBT=<TOK>		Returns a token number that is used to validate a subsequent reboot request.
Request reboot
ExampleAT+CTOK
+CTOK: 123456
OK

AT+CRBT=123456
NotesA successful reboot command (AT+CRBT=<TOK>) is executed immediately; there is no feedback.
Errors+CRBT ERROR: <Error Num>

Error Nums:
1: Invalid token

AT+CTOK / AT+CDFU

Update device firmware

  • Firmware and maintenance
  • RockREMOTE Mini
  • RockBLOCK Pro
  • RockFLEET Assured
  • Device
CommandDescription
+CTOK and +CDFU
AT+CTOK

AT+CDFU = <TOK>		Returns a token number that is used to validate a subsequent reboot request.

Start kermit session to transfer the new device firmware file.
ExampleAT+CTOK
+CTOK: 123456
OK
AT+CDFU = 123456
NotesA successful reboot command is executed immediately - there is no feedback.

The firmware update file must be re-named “H7-App.new” (case-sensitive)

As of FWv0.5.5 the transfer works, but the required reboot may need to be manual.
Errors+CDFU ERROR: <Error Num>

Error Numbers:
1: Invalid token

AT+GNSS

Get the current GNSS location

  • Positioning
  • RockREMOTE Mini
  • RockBLOCK Pro
  • RockFLEET Assured
  • GNSS
+GNSS
AT+GNSSGets the current location of the device.
Returns a comma-separated string of the following:
Source:
0: None
1: GPS
2: Galileo
3: Glonass
4: GNSS
5: BeiDou
6: NavIC
Epoch: A UNIX timestamp of when the fix was achieved.
Latitude
Longitude
Fix:
0: None
1: Standard
2: DGPS
Number of Satellites: Number of satellites used for the fix.
HDOP: Horizontal Dilution of Precision
Altitude: In metres
Geoidal Separation: In metres
DGPS Age: In seconds
DGPS ID: DGPS station ID
Speed: Speed in knots
Heading: Heading/track made good in degrees true
ExampleAT+GNSS
+GNSS: 1,1713445252,51.864400,-2.486030,1,6,0.9,140.0,47.0,,,0.0,0.0
OK
AT+GNSS=\<EPOCH>,\<LATITUDE>,\<LONGITUDE>,\<ALTITUDE>Sets the current location and time from the host on the device.
This function is only available when the internal GNSS is disabled. Positive values for latitude are north. Positive values for longitude are east.
ExampleAT+GNSS=1713445252,51.8644,-2.48603,140.5
OK
Errors+GNSS ERROR: <Error Num>

Error Numbers:
1 Can't set GNSS with internal GNSS enabled
2 Invalid parameters
3 Invalid position
NotesIf there is no location fix, zero values and empty DGPS fields are returned.
AT+GNSS
+GNSS: 0,0,0.000000,0.000000,0,0,0.0,0.0,0.0,,,0.0,0.0
OK
The response contains the stored value, even if the timestamp was acquired some time ago; it therefore reports the last good fix.
This command can also be used to read the current A-PNT position.

AT+APNT

Get or set the current A-PNT position

  • Positioning
  • RockBLOCK Pro
  • RockFLEET Assured
  • A-PNT
A-PNT hardware only
CommandDescription
AT+APNTReturns the current A-PNT position and fix information.
Response+APNT: <Source>,<Epoch>,<Latitude>,<Longitude>,<Fix Quality>,<Number of Satellites>,<HDOP>,<Altitude>,<Geoidal Separation>,<DGPS Age>,<DGPS ID>,<Speed>,<Heading>
AT+APNT=<Epoch>,<Latitude>,<Longitude>,<Altitude>Sets the current position and time from the host. This form is only accepted when an internal A-PNT module is not fitted. Positive latitude values are north and positive longitude values are east.
Errors+APNT ERROR: <Error Num>

Error Numbers:
1 Manual position injection is not permitted when the device has an internal A-PNT module fitted.
2 Incorrect or incomplete parameters.
3 Invalid epoch, latitude, longitude or altitude.
NotesThe response uses the same field order as AT+GNSS.

If there is no location fix, zero values and empty strings are returned. The response contains the last stored fix, which may have been acquired some time ago.

AT+IMTT

List provisioned IMT topics

  • IMT messaging
  • RockREMOTE Mini
  • RockBLOCK Pro
  • RockFLEET Assured
  • IMT
+IMTT
AT+IMTTLists all provisioned raw IMT topics known to the device.
ExampleAT+IMTT
+IMTT: 244,"RAW"
OK
NotesIf no IMT topics are provisioned then no topics will be listed as follows:
AT+IMTT
OK

AT+IMTWT

Send MO IMT in text mode without CRC

  • IMT messaging
  • RockREMOTE Mini
  • RockBLOCK Pro
  • RockFLEET Assured
  • IMT
+IMTWT=<Topic ID>,<Text>
AT+IMTWT=<Topic ID>:
The IMT Topic ID. This is optional; if a Topic ID is not specified, the configured default Topic ID will be used.

<Text>:
ASCII String to send, limited to 5 KB. The text can be but doesn't have to be encapsulated in quotations.
ExampleThis example will send “Hello World!” on Topic 244; once accepted, a message ID of 1 was returned.
AT+IMTWT=244,"Hello World!"
+IMTWT: 1
OK

This example will send “Hello World!” on the default topic; once accepted, a message ID of 2 was returned.
AT+IMTWT="Hello World!"
+IMTWT: 2
OK
Errors+IMTWT ERROR: <Error Num>

Error Numbers:
1 Topic not provisioned.
2 Payload is too large.
3 Buffer is full.
4 Topic is reserved and does not permit MO messages.

Example of an invalid Topic ID:
AT+IMTWT=55,"An invalid topic"
+IMTWT ERROR: 1
OK
NotesWhen the command returns a message ID, it does not mean the IMT message has been sent; it means the message has been accepted and queued by the device. Use AT+IMTMOS with the returned message ID to query the message's actual transmission status.

AT+IMTWB

Send MO IMT in binary mode with CRC

  • IMT messaging
  • RockREMOTE Mini
  • RockBLOCK Pro
  • RockFLEET Assured
  • IMT
+IMTWB=<Topic ID>,<Length>,<Priority>,<TTL>
AT+IMTWB=<Topic ID>:
The IMT Topic ID. This is optional; if a Topic ID is not specified, the configured default Topic ID will be used.

<Length>:
The length of the binary data to be sent in binary mode minus the CRC, but the CRC should be included in the transmission. Currently, the maximum length for a single transfer is 100KB.

Once in binary mode, the connected device must send binary data equal to the length specified plus the CRC within 60 seconds.

The CRC is a 16-bit and is appended MSB. The CRC definition is:
width=16
poly=0x1021
init=0x0000
refin=false
refout=false
xorout=0x0000
check=0x31c3
residue=0x0000

<Priority>:
The Priority of the current message. This is optional but requires a TopicID; if a priority is not specified the default "Normal" priority will be used.
Priority can either be 0 = "Normal" or 1 = "High".

If a high-priority message is sent while normal-priority messages are still in the queue, the high-priority message should bypass the queue and be transmitted first.

<TTL>:
The TTL (Time to Live) of the current message. This is optional but requires both TopicID and Priority to be specified. If omitted or set to 0, the configured default is used. An explicitly supplied non-zero TTL must be 61 seconds or greater.
ExampleExample of writing 9 bytes on topic 244; once 9 bytes have been received by the device and accepted, a message ID is returned.

The data has to be sent in binary and each character represents one byte.
AT+IMTWB=244,9
+IMTWB: READY
b'123456700)c
+IMTWB: 1
OK

… denotes the binary mode of the connected device sending binary data.

Example of writing 200 bytes on the default topic; once 200 bytes have been received by the device and accepted, a message ID of 2 is returned.
AT+IMTWB=200
+IMTWB: READY
…
+IMTWB: 2
OK

Example of writing 700 bytes on TopicID 244 with a High Priority and a TTL of 450 seconds. Once the message has been accepted, a MessageID of 3 is returned.
AT+IMTWB=244,700,1,450
+IMTWB: READY
…
+IMTWB: 3
OK

… denotes the binary mode of the connected device sending binary data.
Errors+IMTWB ERROR: <Error Num>

Error Numbers:
1 Topic not provisioned (immediately reported after CR).
2 Payload too large (immediately reported after CR).
3 Insufficient space in buffer (immediately reported after CR).
4 Timeout after 60 seconds (asynchronously during binary transmission).
5 CRC failed (after reception of binary data).
6 Illegal priority; must be 0 or 1.
7 Illegal TTL; omit for the configured default or specify 61 seconds or greater.
8 Topic is reserved and does not permit MO messages.

Example of a timeout of receiving binary data:
AT+IMTWB=55,10
+IMTWB ERROR: 4
OK
NotesWhen the command returns a message ID, it does not mean the IMT message has been sent; it means the message has been accepted and queued by the device. Use AT+IMTMOS with the returned message ID to query the message's actual transmission status.

The sending device must send binary data within 60 seconds. There currently is a 2 byte CRC limit. Priority and TTL are only supported from FWv0.14.

AT+IMTWU

Send MO IMT in binary mode without CRC

  • IMT messaging
  • RockREMOTE Mini
  • RockBLOCK Pro
  • RockFLEET Assured
  • IMT
+IMTWU=<Topic ID>,<Length>
AT+IMTWU=<Topic ID>:
The IMT Topic ID. This is optional; if a Topic ID is not specified, the configured default Topic ID will be used.

<Length>:
The length of the binary data to be sent in binary mode.

Once in binary mode, the connected device must send binary data equal to the length specified.

<Priority>:
The Priority of the current message. This is optional but requires a TopicID; if a priority is not specified the default "Normal" priority will be used.
Priority can either be 0 = "Normal" or 1 = "High".

If a high-priority message is sent while normal-priority messages are still in the queue, the high-priority message should bypass the queue and be transmitted first.

<TTL>:
The TTL (Time to Live) of the current message. This is optional but requires both TopicID and Priority to be specified. If omitted or set to 0, the configured default is used. An explicitly supplied non-zero TTL must be 61 seconds or greater.
ExampleExample of writing 10 bytes on topic 244; once 10 bytes have been received by the device and accepted, a message ID of 1 is returned.
AT+IMTWU=244,10
+IMTWU: READY
…
+IMTWU: 1
OK

… denotes the binary mode of the connected device sending binary data.

Example of writing 200 bytes on the default topic; once 200 bytes have been received by the device and accepted, a message ID of 2 is returned.
AT+IMTWU=200
+IMTWU: READY
…
+IMTWU: 2
OK

Example of writing 700 bytes on TopicID 244 with a High Priority and a TTL of 450 seconds. Once the message has been accepted, a MessageID of 3 is returned.
AT+IMTWU=244,700,1,450
+IMTWU: READY
…
+IMTWU: 3
OK

… denotes the binary mode of the connected device sending binary data.
Errors+IMTWU ERROR: <Error Num>

Error Numbers:
1 Topic not provisioned (immediately reported after CR).
2 Payload too large (immediately reported after CR).
3 Insufficient space in buffer (immediately reported after CR).
4 Timeout after 60 seconds (asynchronously during binary transmission).
6 Illegal priority; must be 0 or 1.
7 Illegal TTL; omit for the configured default or specify 61 seconds or greater.
8 Topic is reserved and does not permit MO messages.

Example of a timeout of receiving binary data:
AT+IMTWU=55,10
+IMTWU ERROR: 4
OK
NotesWhen the command returns a message ID, it does not mean the IMT message has been sent; it means the message has been accepted and queued by the device. Use AT+IMTMOS with the returned message ID to query the message's actual transmission status.

The sending device must send binary data within 60 seconds. Priority and TTL are only supported from FWv0.14.

AT+IMTWJ

Send an MO IMT JSON object without CRC

  • IMT messaging
  • RockREMOTE Mini
  • RockBLOCK Pro
  • RockFLEET Assured
  • IMT
+IMTWJ=<Topic ID>,<JSON>
AT+IMTWJ=<Topic ID>:
The IMT topic ID. This is optional; if a topic ID is not specified, the configured default topic ID will be used.

<JSON>:
A JSON object formatted as a string with no carriage returns. Other whitespace is accepted. The current limit is 5 KB.
ExampleThis example sends a JSON object that contains a 'key' of type boolean called status with a value of false on topic 244, once accepted a message ID of 1 was returned.
AT+IMTWJ=244,{"status":false}
+IMTWJ: 1
OK
Errors+IMTWJ ERROR: <Error Num>

Error Numbers:
1 Topic not provisioned.
2 Payload too large.
3 Buffer is full.
4 The JSON object is invalid, or the topic is reserved and does not permit MO messages.

Example of an invalid Topic ID:
AT+IMTWJ=55,{"status":false}
+IMTWJ ERROR: 1
OK
NotesWhen the command returns a message ID, it does not mean the IMT message has been sent; it means the message has been accepted and queued by the device. Use AT+IMTMOS with the returned message ID to query the message's actual transmission status.

AT+IMTRJ

Receive an MT IMT message containing JSON using text mode without CRC

  • IMT messaging
  • RockREMOTE Mini
  • RockBLOCK Pro
  • RockFLEET Assured
  • IMT
+IMTRJ=<Topic ID>
AT+IMTRJ=Receives an available MT IMT payload expected to contain JSON, using text mode without CRC. The command does not parse or validate the JSON. An available message is indicated by +IMTMTRING.

<Topic ID> is optional. If omitted, the configured default Topic ID is used. Non-printable characters in the returned copy are represented by a . character.
ExampleRequesting an MT IMT message on topic 55 after +IMTMTRING:

+IMTMTRING=55,2,100
AT+IMTRJ=55
...
OK

... denotes the JSON-encoded message.

Requesting an MT IMT message on the default topic:

AT+IMTRJ
...
OK
Errors+IMTRJ ERROR: <Error Num>

Error Numbers:
1 No MT IMT message is available.
2 The queued message does not match the requested Topic ID.

Example:
AT+IMTRJ=55
+IMTRJ ERROR: 1
OK
NotesThe final two CRC bytes are omitted from the returned text. Only the returned copy is converted for display; the stored message is not modified and remains available for binary retrieval. Retrieving a message does not remove it from the queue. Use AT+IMTA to acknowledge it.

AT+IMTRB

Receive an MT IMT message in binary mode with CRC

  • IMT messaging
  • RockREMOTE Mini
  • RockBLOCK Pro
  • RockFLEET Assured
  • IMT
+IMTRB=<Topic ID>
AT+IMTRB=When an IMT MT is available indicated by the +IMTMTRING.

It can be requested in binary mode.

<Topic ID>:
The IMT Topic ID, this is optional; if a Topic ID is not specified, the configured default Topic ID will be used.
ExampleRequesting IMT MT on topic 55 after +IMTMTRING:
+IMTMTRING=55,1,100
AT+IMTRB=55
…
OK

… denotes binary reception of the 100 bytes plus 2 bytes for the CRC.

Request IMT MT on the default topic:
AT+IMTRB
…
OK
Errors+IMTRB ERROR: <Error Num>

Error Numbers:
1 No MT in queue
2 Incorrect Topic ID

Example:
No IMT MT when requesting binary data:
AT+IMTRB=55
+IMTRB ERROR: 1
OK
NotesTo clear this MT IMT message so that more can be received it must be acknowledged with +IMTA.

AT+IMTRT

Receive an MT IMT message in text mode without CRC

  • IMT messaging
  • RockREMOTE Mini
  • RockBLOCK Pro
  • RockFLEET Assured
  • IMT
+IMTRT=<Topic ID>
AT+IMTRT=When an IMT MT is available indicated by the +IMTMTRING.

It can be requested in text mode, non-printable characters will be denoted with a . character.

<Message ID>:
A unique Message ID for this MT. This ID should be used to acknowledge the message.
ExampleRequesting IMT MT on topic 55 after +IMTMTRING:
+IMTMTRING=55,2,100
AT+IMTRT=55
…
OK

… denotes text encoded message.

Request IMT MT on the default topic:
AT+IMTRT
…
OK
Errors+IMTRT ERROR: <Error Num>

Error Numbers:
1 No MT in queue
2 Incorrect Topic ID

Example:
No IMT MT when requesting text data:
AT+IMTRT=55
+IMTRT ERROR: 1
OK
NotesThe final two CRC bytes are omitted from the returned text. Non-printable characters in the returned copy are replaced with . characters. The stored message is not modified and remains available for binary retrieval.

Retrieving a message does not remove it from the queue. Use AT+IMTA to acknowledge it.

ERROR 2 means the queued message does not match the requested Topic ID.

AT+IMTA

Acknowledge an MT IMT message

  • IMT messaging
  • RockREMOTE Mini
  • RockBLOCK Pro
  • RockFLEET Assured
  • IMT
+IMTA=<Message ID>
AT+IMTA=When an IMT MT is available indicated by the +IMTMTRING.

<Message ID>:
A unique Message ID for this MT. This ID should be used to acknowledge the message. This is returned in the +IMTMTRING command.
ExampleAcknowledging an IMT MT with Message ID 1:
AT+IMTA=1
OK
Errors+IMTA ERROR: <Error Num>

Error Numbers:
1 Message ID unknown.

Example:
An invalid or unknown message ID:
AT+IMTA=5
+IMTA ERROR: 1
OK
NotesAT+IMTA can be used without <Message ID> and will clear the Head of MT Queue following FIFO

AT+IMTC

Manage IMT message queues

  • IMT queue management
  • RockREMOTE Mini
  • RockBLOCK Pro
  • RockFLEET Assured
  • IMT
+IMTC<n>
CommandsAT+IMTC1[=<Topic ID>] Clear the MT queue.
AT+IMTC2[=<Topic ID>] Clear the MO queue.
AT+IMTC3=<Message ID> Cancel an MO message.
AT+IMTC4 Clear the sent-message log.
AT+IMTC5 Clear all MO and MT message history.
ParametersTopic ID is optional for operations 1 and 2. Omitting it or supplying 0 clears the entire relevant queue. Supplying a non-zero Topic ID clears messages only for that topic.

Message ID is required for operation 3.
ExamplesClear the MO queue for Topic ID 244:
AT+IMTC2=244
+IMTC2
OK

Clear the complete MT queue:
AT+IMTC1
+IMTC1
OK

Cancel MO Message ID 26:
AT+IMTC3=26
+IMTC3
OK
Errors+IMTC<n> ERROR: <Error Num>

Error Numbers:
1 Failed to cancel the selected message.
2 Invalid Message ID.
4 Illegal operation number.

Example of an invalid Message ID:
AT+IMTC3=13232
+IMTC3 ERROR: 2
OK
NotesAT+IMTC1 deletes MT messages destined for the serial port and cancels associated RING events. Cloudloop Device Manager MT messages are unaffected.

AT+IMTC2 deletes user-prompted MO messages.

AT+IMTC5 deletes all messages, including Cloudloop Device Manager responses.

ERROR 1 can occur when a message has already been sent to the modem and can no longer be cancelled.

AT+IMTQ

Get IMT queue status

  • IMT queue management
  • RockREMOTE Mini
  • RockBLOCK Pro
  • RockFLEET Assured
  • IMT
+IMTQ
AT+IMTQReturns the queue status of IMT MO and MT. This is broken down into MO and MT:

+IMTQ: MO,<Count>,<Total Bytes>
+IMTQ: MT,<Count>,<Total Bytes>
ExampleAT+IMTQ
+IMTQ: MO,2,200
+IMTQ: MT,5,600
OK
ErrorsNone
Notes

AT+IMTS

Get IMT statistics

  • IMT queue management
  • RockREMOTE Mini
  • RockBLOCK Pro
  • RockFLEET Assured
  • IMT
+IMTS
AT+IMTSReturns the IMT statistics:

+IMTS: <Topic ID>,<Topic Name>,<MO Count>,<MT Count>,<MO Drop Count>,<MT Drop Count>

Topic ID: The numeric ID of the IMT topic.

MO Count: The number of MO IMT messages sent.

MT Count: The number of MT IMT messages received.

MT/MO Drop Count: Messages dropped because of a reception or transmission error, transmission retry, or exceeded TTL.
ExampleAT+IMTS
+IMTS: 244,"Reflector_400465",1,2,0,0
OK
ErrorsNone
Notes

AT+IMTMOS

Get MO IMT message status

  • IMT queue management
  • RockREMOTE Mini
  • RockBLOCK Pro
  • RockFLEET Assured
  • IMT
+IMTMOS=<Message ID>
AT+IMTMOS=<Message ID>:
The message ID of the IMT MO message which was returned by +IMTWT or +IMTWB.
ExampleAT+IMTMOS=1
+IMTMOS: <Topic ID>,<State>,<Epoch>
OK

<Topic ID>:
The topic ID associated with the message.

<State>:
1: Queued, waiting to be sent.
2: Sending, being sent to the Iridium transceiver
3: Dropped, failed to send
4: Cancelled (using +IMTC3)
5: Sent

<Epoch>:
A UNIX timestamp of when the state last changed. This timestamp may be inaccurate if the device has not synchronised with a reliable time source such as GNSS.

Example:
AT+IMTMOS=57
+IMTMOS: 244,1,0
OK
Errors+IMTMOS ERROR: <Error Num>

Error Numbers:
1 Invalid message ID

Example of an invalid or unknown MO Message ID:
AT+IMTMOS=1106
+IMTMOS ERROR: 1
OK
Notes

AT+IMTMTS

Get MT IMT status

  • IMT queue management
  • RockREMOTE Mini
  • RockBLOCK Pro
  • RockFLEET Assured
  • IMT
+IMTMTS
AT+IMTMTSThis command will return the head of the MT queue similar to the +IMTMTRING unsolicited message.

+IMTMTS: <Topic ID>,<Message ID>,<Message Length>
ExampleAT+IMTMTS
+IMTMTS: <Topic ID>,<Message ID>,<Message Length>

<Topic ID>:
The IMT Topic ID, this will be the Topic ID of received MT IMT.

<Message ID>:
A unique Message ID for this MT. This ID should be used to acknowledge the message.

<Message Length>:
This will be the message length of the MT IMT. This will be from 1 to 100 KB. This doesn’t include the CRC.
ErrorsNone
NotesIf the MT queue is empty, the device returns only OK.

+IMTMTRING

MT IMT ring notification

  • IMT queue management
  • RockREMOTE Mini
  • RockBLOCK Pro
  • RockFLEET Assured
  • IMT
NotificationDescription
+IMTMTRING: <Topic ID>,<Message ID>,<Message Length>An unsolicited notification indicating that an MT IMT message has arrived. If the message is not acknowledged within five minutes, the notification is repeated.
<Topic ID>The IMT topic ID of the received message.
<Message ID>The unique ID used to retrieve and acknowledge this MT message.
<Message Length>The message length, excluding the CRC. This can be from 1 byte to 100 KB.
Manual queryUse AT+IMTMTS to query the message currently at the head of the MT queue.
NotesThis is an unsolicited notification, not an AT command. Use AT+UNS to enable or disable unsolicited messages.