http://www.wavecom.com/forum

Open AT ®  Release version:
4.10

Sample - Telemetry

Changes

Dependencies

This sample depends on the following libraries :

Application Description

As this application uses the MultiApp library, the following start/stop command has to be used to control the application execution.

 

  AT+TELESTART (Telemetry start/stop command)
CommandAnswers
AT+TELESTART?+TELESTART: <state>
OK
AT+TELESTART=?+TELESTART: (0-1)
OK
AT+TELESTART= <state> +CME ERROR: 3
or
OK
 
ParameterValues rangeDescriptionDefault value
state0-1The current application running state. This parameter is stored in non-volatile memory.0

The init entry point sent to the MultiApp library is the tele_init() function. The start/stop entry points linked to the +TELESTART command are the tele_start() and tele_stop() functions.

This application checks some GPIO states every 3 seconds. On a state change, it sends a SMS report to the number set by the application (via the +TEL command) :

 

  AT+TEL (Phone number set command)
CommandAnswers
AT+TEL=?+TEL: (20)
OK
AT+TEL?+TEL: <number>
OK
AT+TEL= <number> WRONG PARAMETER
or
OK
 
ParameterValues rangeDescriptionDefault value
number20Destination phone number for GPIO SMS reportmandatory

This command is always available. When number is set in IDLE state, the SMS report is sent. When it is set out of IDLE state, the SMS will be sent as soon as the Application returns to IDLE state.
The read GPIO are set by the +IOSET command :

 

  AT+IOSET (GPIO settings command)
CommandAnswers
AT+IOSET=?+IOSET: (dynamic list...)
OK
AT+IOSET?+IOSET: <settings>
OK
AT+IOSET= <settings> WRONG PARAMETER
or
OK
 
ParameterValues rangeDescriptionDefault value
settingsdynamic list...Up to 15 GPIO identifiers to monitor.
The available GPIO list is dynamically built according to the currently enabled features on the module.
On any programmed input state change, the SMS report is sent.
NA

Updated: Tue Sep 19 17:17:35 CEST 2006;