Rainbow Electronics GM862-QUAD-PY - Manual (Page 7)

GM862-QUAD / PY Software User Guide
1vv0300747 Rev. 3 - 10/07/07
Reproduction forbidden w ithout Telit Communications S.p.A. w ritten authorization - All Rights Reserved page 7 of 96
2 Basic Operations
2.1 Command Syntax
In the next paragraphs the following notations are used:
<cr> represents the Carriage Return Character (13)
<lf> represents the Line Feed Character (10)
<xx>
represents a parameter whatever name is in place of the xx. (< and > characters are
only for delimiting the parameter and must not be issued to the terminal).
[<xx>] represents an optional parameter whatever name is in place of the xx. ([ and ]
characters are only for delimiting the optional parameter and must not be issued to the
terminal).
2.1.1 Interface Style
The GM862-QUAD / PY module is using an AT interface that is defined in the document
80000ST10025a
(AT Commands Reference Guide). The specification defines 3 possible AT
interfaces:
0 - AT command interface of the products, to the GM862-GSM and GM862-GPRS interface style
1 – AT interface of the products, to the GM862-PCS, PYTHON, QUAD-PY, TRIZIUM and GE863-
QUAD, PY interface style
2 - switches the AT command interface style of the product, to the new products like GE864, GC864
and the GPS products
The default interface for the GM862-QUAD -PY product is 1.
The default interface for the GM862-QUAD product is 0.
The syntax rules followed by Telit implementation of either Hayes AT commands, GSM commands
and FAX commands are very similar to those of standard basic and extended AT commands. A
special command (#SELINT) has been introduced in order to have an AT interface very close to the
standard one. With the command AT#SELINT is possible to switch to the preferred AT interface.
Refer to the AT Commands reference guide for the full command description.
There are two types of extended command:
- Parameter type commands. This type of commands may be “set” (to store a value or values
for later use), “read” (to determine the current value or values stored), or “tested” (to determine
ranges of values supported). Each of them has a test command (trailing =?) to give information
about the type of its subparameters; they also have a Read command (trailing ?) to check the
current values of subparameters.