Myriota HyperPulse™ Library 1.0
Loading...
Searching...
No Matches
Myriota HyperPulse™ - AT Command Reference Manual

Overview

This document describes the AT commands supported by Myriota HyperPulse™ library. It provides a summary of the supported commands, their usage, expected responses, and examples. This interface is intended for use with Myriota HyperPulse™ library.


References

  • 3GPP 27.007 Ch 7
  • 3GPP 27.007 Ch 9

Change Log

  • v1.0 Initial release

Command Syntax

All AT commands follow this format:

AT#M<Command><CR>
  • <Command>: Command body including parameters
  • <CR>: Carriage return (\r)

Responses typically end with OK or ERROR.


Supported AT Commands

AT#MSWVERSION

This set command requests the Myriota HyperPulse™ library software version.

AT#MSWVERSION\r

Response Format

HyperPulse library: v<version-string>
Network Info: <network info string>
OK

Example Response

HyperPulse library: v1.0.0-g4b11e08
Network Info: 118f3083, config-clean, 2025-12-03T10:21:55Z, 1.0.2
OK

AT#MMODE

This command sets the operating mode of the Myriota HyperPulse™ library.

Get Command

AT#MMODE?

Query the current mode,

  • 0 : disabled
  • 1 : enabled

Set Command

AT#MMODE=<mode>
  • <mode>
    • 0 : disabled
    • 1 : enabled
AT#MMODE=1

Expected Response:

On success:

OK

AT#MSEND

This command sends a user specified uplink message. If the UE is detached or a satellite link is not available, the message is queued up until the UE is ready to send it.

Set Command

AT#MSEND=<length><data>
  • <length>: Length of payload in Bytes
  • <data>: Payload in HEX string format
AT#MSEND=20,"01968ed71ec1060708090a0b0c0d0e0f10111213"\r

Expected Response:

On success:

OK

Get Command

This command checks the status of the uplink message queue, returning the number of user messages waiting to be sent.

AT#MSEND?
  • <pending_count>: The number of user messages currently in the uplink queue.

Expected Response:

If there are 3 messages waiting in the queue:

AT#MSEND?
AT#MSEND: 3
OK

AT#MRECV

This set command enables/disables unsolicited notifications for received downlink messages.

Set Command

AT#MRECV=<enable>
  • <enable> 1: Enable URC notification , 0: Diasble URC notification

Example URC Notification Enable

AT#MRECV=1\r

Example URC Notification

#MRECV: 20,"01968ed71ec1060708090a0b0c0d0e0f10111213"\r

AT#MCLAC

This command requests a list of all Myriota AT commands supported by the Myriota HyperPulse™ library.

Set Command

AT#MCLAC\r

Expected Response:

AT#MSWVERSION
AT#MSEND
AT#MRECV
AT#MCLAC
AT#M...
OK

AT#MLOCATION

This command requests a new location fix or sets a location for the device. When requesting a fix, the location will be returned as a URC notification. Setting a location allows the device to optimise power consumption by assuming the device will not move, minimising internal location checks.

Set Command

AT#MLOCATION=<latitude>,<longitude>,<elevation>
  • <latitude> : In 0.1 micro-degrees.
  • <longitude> : In 0.1 micro-degrees.
  • <elevation> : In milli-meters.

Expected Response:

OK

Get Command

AT#MLOCATION?<method>,<accuracy>,<max_age_s>,<timeout_s>
  • <method> :
    • 0 : Use GNSS (currently the only supported location method).
  • <accuracy> :
    • 0 : LOW - Approximate fix only, used to save power at the expense of accuracy
    • 1 : BALANCED - Optimise both power and accuracy constraints.
    • 2 : HIGH - High accuracy prioritising accuracy over any power constraints.
  • <max_age_s> : Maximum age in seconds for the last update of specified method and accuracy to be considered valid.
  • <timeout_s> : Fix timeout in seconds.

Expected Notification Format

AT#MLOCATION=<accuracy>,[<latitude>,<longitude>,<elevation>,<timestamp_s>],[<next_fix_s>]
  • <accuracy> : Same as Get command, with additional state of timeout:
    • 0 : LOW - Approximate fix only, used to save power at the expense of accuracy.
    • 1 : BALANCED - Optimise both power and accuracy constraints.
    • 2 : HIGH - High accuracy prioritising accuracy over any power constraints.
    • -1 : TIMEOUT - Fix has timed out. see <timeout_s> for when a fix retry will be attempted.
  • <latitude> : In 0.1 micro-degrees.
  • <longitude> : In 0.1 micro-degrees.
  • <elevation> : In milli-meters.
  • <timestamp_s> : UTC timestamp in seconds of when the fix was obtained.
  • <next_fix_s> : If timeout occurs, specifies time until next retry.

Example URC Notification

Notification containing valid location:

#MLOCATION: 1,-349000000,1380000000,50000,1740000000,\r

Notification containing location fix that has timed-out and the next retry will be in 120s:

#MLOCATION: -1,,,,,120\r

AT#MTIME

Get Command

This command requests the current system time as UTC epoch in milliseconds.

AT#MTIME?

Expected Response :

<current_time_ms> \r
OK
  • <current_time_ms> : Current UTC time in ms.

Example Response

1740000000000 \r
OK

Set Command

This command subscribes to URC notifications whenever the system updates the time.

AT#MTIME=<enable_updates>
  • <enable_updates> :
    • 1 : Subscribe to MTIME URC notifications
    • 0 : Disable MTIME URC notifications

Expected URC notification:

#MTIME: <current_time_ms> \r
OK
  • <current_time_ms> : Current UTC time in ms.

Example URC notification:

#MTIME: 1740000000000 \r
OK

Error Codes