Telit xE910 AT Interface

The Telit family of 910 modules have been updated to include native support for interfacing applications to the IoT Portal. This API lets you use a new set of AT commands to easily expand the capabilities of any device built upon a Telit 910 family module.

The ME910 does not support AT Commands

Supported modules:

  • LE910
  • HE910
  • UE910
  • GE910

Supports most TR50 commands.

Can only authenticate using application tokens, you cannot connect using user credentials.

Simple Example
// set the APN for the modem.
AT+CGDCONT=1,"IP","internetm2m.air.com"
// start the PDP context (IP connection)
AT#SGACT=1,1

// configure the connection to the IoT Portal
// settings are saved in NVM, so this needs to be set only once.
AT#DWCFG=open-api.devicewise.com,0,b2Z4JLWY3d8K8Ome
// connect to the IoT Portal
AT#DWCONN=1
// send a property.publish API call to submit "temp" property data.
AT#DWSEND=0,property.publish,key,temp,value,22.5

API Reference

Configuring the API

Before you can connect to the platform, it is important to configure the API so that it connects to the correct instance of the IoT Portal, and has the correct security credentials to connect to your account.  To configure the API, there are two AT commands (AT#DWCFG & AT#DWEN) that must be set prior to issuing a connect (AT#DWCONN).  Calling of the configuration APIs only needs to occur once, as the settings are persisted in NVM (non-volatile memory), so any settings will persist across loss of power to the module.  You should always call both of these APIs prior to establishing a connection.  When in doubt, do not specify optional parameters.

Remote AT Support

One special feature of the API is the ability to enable remote AT command support in the IoT Portal.  Using the Remote AT support, you can execute AT commands via the IoT Portal to diagnose connection issues or perform remote configuration changes with ease.  To enable this function, you need to call "AT#DWEN=0,1" to enable this support.  Enabling or disabling the feature only takes effect when the connection is established.

There is no limit on the length of the single <param_i>, but there is a limit in the total length of the AT command string, that cannot exceed 400 characters. If this threshold is exceeded, then an ERROR is raised.

There is also a limit of 20 messages on the receive queue. If the queue is full, the consequent send will still succeed but the response for that particular request will be dropped until an item is removed from this queue (See command AT#DWRCV and AT#DWRCVR).