Modem commands

Hi everyone, I would like to know if it is possible to do AT Commands through the Octave application example through Edge Actions.

Thank you

Hi henrikflog,

You could try to configure Universal Serial Parser (USP) at the link below:

Universal Serial Parser (USP) Guide (


How could I do at command via uart serial? I used putty and connected to the modem when I do it physically

Hi henrikflog,

Please follow these step:

  1. Install driver for your Octave device here:

  2. Connect your PC to the FX30/FX30S via the USB port.

  3. On your PC, open Computer Management, find Sierra Wireless WWAN Modem as the picture below to get COM port and port speed for the next step:

  4. Open your putty and configure the correct com port and speed.

Thank you for your reply, indeed I know how to do it with PuTTy, I was just asking how can I do it via Octave (remotely)


Unfortunately, we do not support AT commands through the existing Octave applications. You could write your own application to forward commands from the Datahub to the AT parser, if you are comfortable doing so. This would give you AT access from the cloud or from edge actions. Such an application would need to use the Datahub io.api and the Legato le_atClient.api.

The AT port is also available when logged into the device locally, via ssh. To access it, use:
microcom /dev/ttyAT. Echo is not enabled by default so it helps to issue “ATE” as the first command


Hi, thank you for your reply.

So if I understand correctly:

  1. I create a Legato APP
  2. I define an AT Command that I want to be prompted on the modem and create it with le_atClient API on the Legato APP

at this point I am not sure if it’s correct:

  1. I create an INPUT on the dataHub with a boolean that trigger the AT Command
  2. I create a virtual resource on Octave that link the previous INPUT created

Is this these steps right?

Thank you


Yes, that’s right. You want to create a Legato app that uses the le_atClient API - and the /dev/ttyAT device.

As for sending the command from the Datahub:

  • The resource which causes the command to be sent must be an OUTPUT. This means that an edge action or the Octave server can push data TO the resource
  • Your application should register a push handler on this resource. When resource is updated, your app will receive the data via the handler and call the appropriate le_atClient APIs
  • The data type of the OUTPUT can be trigger however, for flexibility you may want to use a string which contains the actual command to be sent
  • The response from the AT command can be pushed to another resource. This resource should be an INPUT


Hi Henrik,

Please see the attached sample application code.

Ian (4.5 KB)