Telit Wireless Solutions GE863-GPS Software User's Manual

Download

GE863-GPS Software User Guide

GE863-GPS Software User Guide 1vv0300724 Rev. 2 - 24/01/07

GE863-GPS Software User Guide

1vv0300724 Rev. 2 - 24/01/07

Contents:

1 Overview .......................................................................................................4

2 Basic Operations..........................................................................................5

2.1 Command Syntax ...................................................................................................................................5

2.1.1 Interface Style...................................................................................................................................5

2.2 Command Response Timeout ................................................................................................................6

2.3 Turning ON the GE863-GPS.................................................................................................................9

2.4 Turning OFF the GE863-GPS ............................................................................................................. 10

2.5 Checking GSM device functionality ...................................................................................................12

2.5.1 Autobauding...................................................................................................................................12

2.5.2 SIM presence checking...................................................................................................................13

2.5.3 Network checking...........................................................................................................................15

2.6 Placing a Voice call...............................................................................................................................21

2.6.1 Voice call device set up..................................................................................................................21

2.6.2 Phone number dialing.....................................................................................................................23

2.6.3 Closing the voice call .....................................................................................................................24

2.7 Placing a CSD Data call (not GPRS) ..................................................................................................25

2.7.1 Data call device set up....................................................................................................................25

2.7.2 Phone number dialing (data call)....................................................................................................26

2.7.3 Closing the Data call.......................................................................................................................27

2.8 Answer an incoming Call.....................................................................................................................28

3 Advanced Operations ................................................................................30

3.1 Accessing the phonebook .....................................................................................................................30

3.1.1 Preliminary phonebook set up........................................................................................................30

3.1.2 Phonebook entry search by Name..................................................................................................33

3.1.3 Phonebook entry read by Index......................................................................................................34

3.1.4 Phonebook entry Write...................................................................................................................35

3.1.5 Phonebook entry Delete..................................................................................................................37

3.1.6 Phonebook entry Dial.....................................................................................................................38

3.2 Distinguish Calls................................................................................................................................... 40

3.2.1 Identify the Call type......................................................................................................................40

3.2.2 Identify the Caller...........................................................................................................................41

3.2.3 Restricting Calling Line Indication ................................................................................................42

3.2.4 Call Barring Control.......................................................................................................................44

3.3 DTMF tones ..........................................................................................................................................51

3.4 GSM Power Saving function ...............................................................................................................52

3.5 SMS handling........................................................................................................................................54

3.5.1 SMS device setup ...........................................................................................................................54

GE863-GPS Software User Guide

1vv0300724 Rev. 2 - 24/01/07

3.5.2 IRA character set............................................................................................................................64

3.5.3 Writing a New SMS to storage.......................................................................................................66

3.5.4 Sending an SMS previously stored.................................................................................................67

3.5.5 Sending a new SMS without storing it...........................................................................................68

3.5.6 Deleting an SMS.............................................................................................................................69

3.5.7 Reading an SMS.............................................................................................................................70

3.5.8 Listing a group of SMSs.................................................................................................................72

3.6 Using General Purpose Input/Output pins.........................................................................................74

3.6.1 GPIO pin setup ...............................................................................................................................74

3.6.2 GPIO pin use ..................................................................................................................................76

3.7 Clock/Alarm function...........................................................................................................................81

3.7.1 Clock date/time...............................................................................................................................81

3.7.2 Alarm function................................................................................................................................83

4 GPRS operations........................................................................................88

4.1 Introduction ..........................................................................................................................................88

5 GPS operations ..........................................................................................91

5.1 Introduction ..........................................................................................................................................91

5.2 GE863-GPS Serial Ports......................................................................................................................91

5.2.1 GPS SERIAL PORT A (SIRF BINARY) ......................................................................................91

5.2.2 GPS SERIAL PORT B (NMEA)....................................................................................................91

5.3 WGS 84..................................................................................................................................................92

5.4 NMEA 0183...........................................................................................................................................93

5.4.1 GGA - Global Positioning System Fixed Data...............................................................................94

5.4.2 GLL - Geographic Position - Latitude/Longitude..........................................................................95

5.4.3 GSA - GNSS DOP and Active Satellites........................................................................................96

5.4.4 GSV - GNSS Satellites in View .....................................................................................................97

5.4.5 RMC - Recommended Minimum Specific GNSS Data .................................................................98

5.4.6 VTG - Course Over Ground and Ground Speed ............................................................................99

5.5 Checking GPS device functionality...................................................................................................100

5.5.1 Controlled mode...........................................................................................................................100

5.6 CONTROLLING GPS RECEIVER.................................................................................................101

5.6.1 POWER CONTROL OF GPS RECEIVER .................................................................................101

5.6.2 GPS RESET..................................................................................................................................102

5.6.3 GPS ANTENNA MANAGEMENT.............................................................................................103

5.6.4 GPS PARAMETERS SAVE........................................................................................................104

5.6.5 RESTORE GPS PARAMETERS.................................................................................................104

5.6.6 READ ACQUIRED GPS POSITION..........................................................................................104

6 Service and firmware update ..................................................................106

6.1 Step-by-Step upgrade procedure ......................................................................................................106

7 Document Change Log............................................................................109

GE863-GPS Software User Guide

1vv0300724 Rev. 2 - 24/01/07

1 Overview

The purpose of this document is the description of some common AT command procedures that may be used with the Telit GE863-GPS module. In this document, all the basic functions of a mobile phone will be taken into account and for each one of them, a proper command sequence will be suggested. In the Advanced operation section the more useful services and features of the GSM network supported by the Telit GE863-GPS module is taken into account and some command sequence and usage are provided for each one of them. This document and its suggested command sequences shall not be considered mandatory; instead, the information given shall be used as a guide for properly using the Telit module. For further commands and features that may not be explained in this document refer to the GE863-GPS Product Description document where all the supported AT commands are reported.

NOTE

The information presented in this document is believed to be accurate and reliable. However, Telit Communications S.p.A. assumes no responsibility for its use, nor any infringement of patents or other rights of third parties, which may result from its use. No license is granted by implication or othe rwise under any patent rights of Telit Communications S.p.A. other than for circuitry embodied in Telit products. This document is subject to change without notice.

GE863-GPS Software User Guide

1vv0300724 Rev. 2 - 24/01/07

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 GE863-GPS 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 GE863QUAD, 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 GE863-GPS product is 2. The switch between the different interfaces could also be performed with the #SELINT AT command.

Refer to the AT Commands Reference Guide for the full command description. All the AT commands described in this specification is related to SELINT 2

GE863-GPS Software User Guide

1vv0300724 Rev. 2 - 24/01/07

2.2 Command Response Timeout

Every command issued to the Telit GE863-GPS returns a result response if response codes are enabled (default) (see command ATQn). The time needed to process the given command and return the response varies from command to command and may depend also from the network on which the command may interact. As a result every command is provided with a proper timeout time, if this time elapses without any result from the operation, then the ERROR response is reported as if the operation was not successful. The timeout time is quite short for commands that imply only internal set up commands, but may be very long for command that interact with the network (or even Networks).

NOTE: In case no response is received after the timeout time has been elapsed, then try repeating the last command and if still no response is received until the timeout time, then an Unconditional Shutdown MUST be issued and then the device shall be powered ON again.

In the table below are listed all the commands whose timeout differs from the default 100 ms and their effective timeout is reported:

Command Time-Out (Seconds)

+CBST 0.2 +CR 0.2 +CRC 0.2 +CRLP 0.2 +CSCS 0.2 +CEER 5 +CGMI 5 +CGMM 5 +CGMR 5 +CGSN 20 +CIMI 20 +CNUM 20 +CREG 5 +COPS 180 +CLCK 180 @CLCK 180 +CPWD 180 +CLIP 180 +CLIR 180 +CCFC 180 +CCWA 20 +CHLD 20 +CUSD 180 +CAOC 20 +CSSN 20

GE863-GPS Software User Guide

1vv0300724 Rev. 2 - 24/01/07

Command Time-Out (Seconds)

+CLCC 20 +CPAS 5 +CPIN 20 +CSQ 5 +CPBS 5 +CPBR 20 +CPBF 20 +CPBW 20 +CALM 5 +CRSL 5 +CLVL 5 +CMUT 5 +CACM 20 +CAMM 20 +CPUC 20 +CMEE 5 +VTS 20 +GMI 5 +GMM 5 +GMR 5 +GSN 20 I3 5 I4 5 I5 5 +CSMS 5 +CPMS 5 +CMGF 5 +CSCA 20 +CSMP 5 +CSDH 5 +CSAS 5 +CRES 5 +CNMI 5 +CMGS 180 / 5 for prompt”>” +CMSS 180 +CMGW 5 / 5 for prompt”>” +CMGD 5 +CMGR 5 +CMGL 5 #CAP 10 #SRS 10 #SRP 10 #STM 10 #PCT 10

GE863-GPS Software User Guide

1vv0300724 Rev. 2 - 24/01/07

Command Time-Out (Seconds)

#SHDN 10 #QTEMP 10 #SGPO 10 #GGPI 10 #MONI 10 #CGMI 5 #CGMM 5 #CGMR 5 #CGSN 20 #CIMI 5 +CGACT 180 +CGATT 180 +CGDATA 20 +CGDCONT 20 +CGPADDR 20 +CGQMIN 20 +CGQREQ 20

GE863-GPS Software User Guide

1vv0300724 Rev. 2 - 24/01/07

2.3 Turning ON the GE863-GPS

To turn on the GE863-GPS the pin ON# must be tied low for at least 1 second and then released. A simple circuit to do it is:

ON#

Power ON impulse

GND

NOTE: don't use any pull up resistor on the ON# line. Using pull up resistor may bring to latch up problems on the GE863-GPS power regulator and improper power off of the module. The line ON# must be connected only in open collector configuration.

TIP: To check if power has raised it is possible to monitor the PWRMON line, when this line goes high the module is powered on, but before it remains on the device needs other 900 ms for software startup. Hence check the PWRMON line and 900 ms after its transition to high it is possible to release the ON# pin.

When turning on the module, both devices (GSM and GPS) will be started. The GPS antenna will be supplied and the receiver will start the scanning activity to achieve the Fix.

GE863-GPS Software User Guide

1vv0300724 Rev. 2 - 24/01/07

2.4 Turning OFF the GE863-GPS

The turning off of the device can be done in two ways:

• • by software command by hardware shutdown

When the device is shut down by software command or by hardware shutdown, it issues to the network a detach request that informs the network that the device will not be reachable any more.

2.4.1.1 Software shutdown

• Send command

AT#SHDN<cr>

• wait for

OK response

The device shuts down with the following sequence of activities:

• Detach from the network

• Module Shutdown

In the case of Network unavailability the detach will be attempted few seconds (typical 6secs). After this timeout the module will be shut down.

2.4.1.2 Hardware shutdown

To turn OFF the GE863-GPS the pin ON# must be tied low for at least 2 second and then released. The same circuitry for the power on can be used. The device shuts down after the release of the ON# pin.

TIP: To check if the device has powered off, the hardware line PWRMON should be monitored. When it goes low, the device has powered off.

GE863-GPS Software User Guide

1vv0300724 Rev. 2 - 24/01/07

2.4.1.3 Hardware Unconditional SHUTDOWN

To unconditionally SHUTDOWN the GE863-GPS the pin RESET# must be tied low for at least 200 milliseconds and then released. A simple circuit to do it is:

RESET#

Unconditional Power OFF impulse

GND

NOTE: don't use any pull up resistor on the RESET# line nor any totem pole digital output. Using pull up resistor may bring to latch up problems on the GE863-GPS power regulator and improper functioning of the module. The line RESET# must be connected only in open collector configuration.

TIP: The unconditional hardware RESET should be always implemented on the boards and software should use it as an emergency exit procedure.

GE863-GPS Software User Guide

1vv0300724 Rev. 2 - 24/01/07

2.5 Checking GSM device functionality

After a proper power on the device is ready to receive AT commands on the serial port. Several things have to be checked in order to be sure that the device is ready to send and receive calls and SMS:

2.5.1 Autobauding

At startup it is necessary to send an AT command to make the device set the right speed and character format of the serial port. When this is done the device responds with OK. If no response is received within the timeout period of 200 ms retry.

• Send command

AT<cr>

• wait for

OK response

after this initial command, it is advisable to fix the port rate, in order to eliminate possible errors in detecting the serial speed rate:

• Send command

AT+IPR=<rate><cr>

• wait for

OK response

where rate is the port speed and can be 0, 300,1200,2400,4800,9600,19200,38400,57600,115200 bps.

If <rate> is set to 0, then automatic speed detection is enabled and also character format (see +ICF) is set to auto-detect. (default) If <rate> is specified and not 0, DTE-DCE speed is fixed at that speed, hence no speed auto-detection (autobauding) is enabled.

TIP: The serial port suggested setting is: port speed 38400, character format 8N1 (8 bit per char, No parity bit, 1 stop bit).

GE863-GPS Software User Guide

1vv0300724 Rev. 2 - 24/01/07

2.5.2 SIM presence checking

After autobauding the first thing to check is the SIM presence and PIN code insertion, this can be done with the following commands:

2.5.2.1 Enable the Extended error result codes

• send command AT+CMEE=1<cr>

• wait for

OK response

or if you prefer the verbose format instead of the numerical format then:

• send command

AT+CMEE=2<cr>

• wait for

OK response

2.5.2.2 Query SIM presence and status

•

send command AT+CPIN?<cr>

•

wait for response:

Response Reason Action

+CPIN: SIM PIN SIM is present and PIN is

required to continue operations

Proceed to par. 2.5.2.3

+CPIN: SIM PUK SIM is present and 3 attempts

to give SIM PIN have failed, so SIM PUK is required

Send command AT+CPIN=<SIM PUK>

+CPIN: READY SIM is present and no PIN code

is required to proceed

Proceed ahead

+CME ERROR: 10 SIM not present Insert SIM or require SIM

insertion and repeat from par.

2.5.2.2

+CME ERROR: 13 SIM defect Check SIM insertion or require

a new SIM not defected and

repeat from par. 2.5.2.2 +CME ERROR: 14 SIM is busy retry later +CME ERROR: 15 SIM is wrong type Check SIM, it must be a GSM

SIM.

GE863-GPS Software User Guide

1vv0300724 Rev. 2 - 24/01/07

2.5.2.3 Provide SIM PIN (only if required see point 2.5.2.2)

•

send command AT+CPIN=****<cr>

where **** stands for the SIM PIN code (e.g. 1234)

• wait for response:

Response Reason Action

OK SIM PIN was correct Proceed ahead ERROR the PIN code inserted is not

correct

Retry from par. 2.5.2.2

NOTE: When receiving the ERROR message, repeat

Query SIM presence and status since after 3 failed attempts SIM PIN is not anymore requested, but SIM PUK is requested instead, hence you may need to go through procedure

2.5.2.4

2.5.2.4 Provide SIM PUK (only if required see par. 2.5.2.2)

•

send command AT+CPIN=*******,<newpin><cr>

where ******* stands for the SIM PUK code (e.g. 12345678) and <newpin> (e.g. 1234) will replace the old pin in the SIM.

• wait for response:

Response Reason Action

OK SIM PUK was correct Proceed ahead ERROR the SIM PUK code inserted is

not correct

Retry from par. 2.5.2.4

TIP: When receiving the ERROR message, be careful to check if the SIM PUK is correct before retrying, since after 10 failed attempts to provide the SIM PUK the SIM Card will lock and will not be usable anymore.

GE863-GPS Software User Guide

1vv0300724 Rev. 2 - 24/01/07

2.5.3 Network checking

2.5.3.1 Query network status

•

send command AT+CREG?<cr>

•

wait for response:

Response Reason Action

+CME ERROR: 10 SIM not present or damaged Check SIM or require SIM

insertion and repeat from par.

2.5.2.2

+CME ERROR: 11 SIM is present and PIN is

required to continue operations

Repeat par. 2.5.2.3

+CREG: 0,0 or +CREG: 1,0

No GSM/DCS network is found Check for antenna cable

connection (antenna may be disconnected or damaged) or change position if the antenna is OK. Repeat par. 2.5.3.1 until

a network is found. +CREG: 0,1 or +CREG: 1,1

Mobile is registered on its home network.

Proceed ahead. Ready to call

+CREG: 0,2 or +CREG: 1,2

Mobile is currently not registered on any network but is looking for a suitable one to register.

Repeat procedure at par.

2.5.3.1 to see if it has found a

suitable network to register in. +CREG: 0,3

or +CREG: 1,3

Mobile has found some networks but it is not allowed to register on any of them, no roaming was allowed.

Try in another place, and repeat

procedure at par.2.5.3.1

+CREG: 0,4 or +CREG: 1,4

Mobile is in an unknown network status

Repeat procedure at par.2.5.3.1

to see if it has found a suitable

network to register in +CREG: 0,5 or +CREG: 1,5

Mobile has found some networks and is currently registered in roaming on one of them

Proceed ahead. Ready to call

TIP: When a response +CREG: x,1 or +CREG: x,5 is received, then the device is ready to place and receive a call or SMS. It is possible to jump directly to call setup procedures or SMS sending procedures.

GE863-GPS Software User Guide

1vv0300724 Rev. 2 - 24/01/07

2.5.3.2 Network operator identification

Once the mobile has registered on some network (or even if it has returned +CREG:x,3), it is possible to query the mobile for network identifications codes an names:

• send command AT+COPS=?<cr>

•

wait for response in the format:

+COPS: [list of supported (<stat> ,<oper (in <format>=0)>,, <oper (in <format>=2)>)s][,,(list of supported <mode>s), (list of supported<format>s)]

where: <stat> - operator availability 0 - unknown 1 - available 2 - current 3 - forbidden

<format> 0 - alphanumeric long form (max length 16 digits) 2 - numeric 5 digits [country code (3) + network code (2)]

<oper>: network operator in format defined by <format> parameter. NOTE: since with this command a network scan is done, this command may require some seconds

before the output is given.

For example:

command:

AT+COPS=?<cr> Answer: +COPS: (2,"I WIND",,"22288"),(1,"SI MOBITEL GSM",,"29341"),(1,"vodafone IT",,"22 210"),(1,"SI.MOBIL",,"29340"),(3,"I TIM",,"22201"),,(0-4),(0,2)

OK In this case the mobile is registered on the network "I TIM" which is a network from Italy Nation code

:222 and Network ID: 01. There is also another network available for registration: "SI.MOBIL" which is a network from Slovenia Nation Code:293 and Network ID: 40. The other networks are not available for registration and are: "I-OMNITEL" from Italy Nation code :222 and Network ID: 10 - FORBIDDEN "SI-GSM " from Slovenia Nation Code:293 and Network ID: 41 - UNKNOWN

TIP: In this case a "I TIM" logo might be reproduced on the MMI to give the user the information that is registered on that network.

NOTE: this command issues a network request and it may require a quite long time to respond, since the device has to wait the answer from the network (it can be as long as 60 seconds). Hence don't use it if not needed.

GE863-GPS Software User Guide

1vv0300724 Rev. 2 - 24/01/07

2.5.3.3 Check for received signal strength & quality

Once the mobile has registered on one network, it may be useful to know the received signal strength & quality to give the user an indication of the reliability of the network.

• send command AT+CSQ<cr>

•

wait for response in the format:

+CSQ: <rssi>,<ber> OK where:

<rssi> is an integer from 0 to 99 that indicates the received signal strength:

<rssi> value Signal strength Indication

0 -113 dBm or less Signal is VERY low: at the extreme sensibility limit 1 -111 dBm MMI may indicate only 1 antenna bar 2 -109 dBm MMI may indicate only 1 antenna bar 3 -107 dBm MMI may indicate only 1 antenna bar 4 -105 dBm MMI may indicate only 1 antenna bar 5 -103 dBm MMI may indicate only 1 antenna bar 6 -101 dBm MMI may indicate 2 antenna bars 7 -99 dBm MMI may indicate 2 antenna bars 8 -97 dBm MMI may indicate 2 antenna bars

9 -95 dBm MMI may indicate 2 antenna bars 10 -93 dBm MMI may indicate 3 antenna bars 11 -91 dBm MMI may indicate 3 antenna bars 12 -89 dBm MMI may indicate 3 antenna bars 13 -87 dBm MMI may indicate 3 antenna bars 14 -85 dBm MMI may indicate 3 antenna bars 15 -83 dBm MMI may indicate 4 antenna bars 16 -81 dBm MMI may indicate 4 antenna bars 17 -79 dBm MMI may indicate 4 antenna bars 18 -77 dBm MMI may indicate 4 antenna bars 19 -75 dBm MMI may indicate 4 antenna bars 20 -73 dBm MMI may indicate 4 antenna bars 21 -71 dBm MMI may indicate 4 antenna bars 22 -69 dBm MMI may indicate 4 antenna bars 23 -67 dBm MMI may indicate 4 antenna bars 24 -65 dBm MMI may indicate 4 antenna bars 25 -63 dBm MMI may indicate 4 antenna bars 26 -61 dBm MMI may indicate 4 antenna bars 27 -59 dBm MMI may indicate 4 antenna bars 28 -57 dBm MMI may indicate 4 antenna bars

GE863-GPS Software User Guide

1vv0300724 Rev. 2 - 24/01/07

29 -55 dBm MMI may indicate 4 antenna bars 30 -53 dBm MMI may indicate 4 antenna bars 31 -51 dBm or more MMI may indicate 4 antenna bars 99 not detected MMI may indicate flashing antenna bars

NOTE: when <rssi> is less than 6, only 1 MMI antenna bar, the quality of a call will be poor and the call may even drop.

<ber> is an integer from 0 to 7 and 99 that reports the received signal quality measured on the radio

traffic channel.

NOTE: The quality is measured on the traffic channel, hence it is available only during a

conversation, in Idle the reported value must not be considered. In conversation the quality decreases with the increase of the <ber> number.

NOTE: The <ber> value refers strictly to the GSM radio channel and is a very technical parameter, it can be used to monitor the voice call quality since the voice quality is inversely proportional to the <ber> number.

NOTE: For Data calls the signal quality reported is not directly connected to the connection quality. The reported signal quality refers only to the GSM radio channel link and not to the whole path from the caller to the receiver, so it may happen that the quality on the GSM radio link is very good and hence the reported <ber> is 0 (good quality) but the quality of the remaining path to the other party is very bad and hence the final data connection quality is very poor. For this reason the signal quality indicator <ber> should not be taken into account to monitor data calls quality.

2.5.3.4 Quick Network Status Checking

Once the mobile has registered on one network, it may be useful to know the received signal strength and the network on which the mobile is registered. These information can be gathered with the commands +CREG, +COPS and +CSQ, which are part of the standard ETSI GSM 07.07 commands as seen before, unfortunately these commands are not so fast in the response due to network response time, especially the +COPS command. If You want to keep your software as general as possible you can follow the indications given before and forget this part; instead if you need or want a faster way to check at the mobile network information, the GE863-GPS provides a special command #MONI which can be used to gather all the information needed in a faster and simpler way:

send command AT#MONI=0<cr> •

•

wait for OK response

• send command AT#MONI?<cr>

• wait for response in the format:

GE863-GPS Software User Guide

1vv0300724 Rev. 2 - 24/01/07

#MONI: <netname> BSIC:<bsic> RxQual:<qual> LAC:<lac> Id:<id> ARFCN:<arfcn> PWR:<dBm> dBmTA: <timadv>

or in the case the network name is not known:

#MONI: Cc:<cc> Nc:<nc> BSIC:<bsic> RxQual:<qual> LAC:<lac> Id:<id> ARFCN:<arfcn> PWR:<dBm> dBm TA: <timadv>

OK where:

<netname> = name of network operator <cc> = country code <nc> = network operator code <n> = progressive number of adjacent cell <bsic> = base station identification code <qual> = quality of reception (0-7) (same as <ber> of +CSQ command) <lac> = localization area code <id> = cell identifier <arfcn> = assigned radio frequency channel <dBm> = received signal strength in dBm (same as "decoded" rssi value) <timadv> = timing advance

For example:

command:

AT#MONI=0<cr>

Answer:

command:

AT#MONI?<cr>

Answer:

#MONI: I TIM BSIC:23 RxQual:7 LAC:AEAD Id:5265 ARFCN: 59 PWR: -80 dBm TA:0 OK In this case the mobile is registered on the network "I TIM", the signal strength is -80dBm (MMI may

indicate 4 antenna bars as reported on the table 5). The other information received is strictly technical and should not be given to the user.

For example2:

command:

AT#MONI=0<cr>

Answer:

GE863-GPS Software User Guide

1vv0300724 Rev. 2 - 24/01/07

command:

AT#MONI?<cr>

Answer:

#MONI: Cc: 010 Nc: 03 BSIC:23 RxQual:7 LAC:0001 Id:0001 ARFCN: 60 PWR: -83 dBm TA:0 OK In this case the mobile is registered on the network whose Country code is 010 and Network operator

code is 03, the signal strength is -83dBm (MMI may indicate 4 antenna bars as reported on the table

5). The other information received is strictly technical and should not be given to the user. The values reported are random and have no meaning they are used only to explain command usage.

NOTE: This command should be used only to gather information on network name and signal strength, to check if mobile is registered or is looking for a suitable network to register to, use always the +CREG command. This is due to the fact that if the network signal is too weak and mobile looses the registration, until a new network is found the #MONI command reports the last measured valid values and not the real ones. The TA (timing advance parameter) is valid only during a call.

TIP: To properly use this feature, check network registration with command +CREG as seen on par. 2.5.3.1 and when mobile is registered query the mobile for network operator name and signal strength with #MONI command.

GE863-GPS Software User Guide

1vv0300724 Rev. 2 - 24/01/07

2.6 Placing a Voice call

Before a voice call can be placed, it is recommended to check if the mobile is registered on a network (see par.

2.5.3.1) and if the signal strength is enough to ensure a call can be made.

2.6.1 Voice call device set up

2.6.1.1 Set the device in voice mode

• Send command AT+FCLASS=8<cr>

• wait for

OK response

NOTE: This command may be omitted if the modifier ";" is added at the end of the ATD command

after the number to be dialed.

2.6.1.2 Set the desired audio path active

The GE863-GPS has two different audio paths:

• internal microphone/ear (MT)

• external microphone/ear (HF)

Usually the internal path is used for a handset function, while the external is used for handsfree function. There are two way to switch between these two paths:

• SOFTWARE: by using the command AT#CAP= <n> (with n=1 OR n=2)

• HARDWARE: by setting AT#CAP=0 and setting the AXE input high (internal MT) or low

(external HF).

If only one path is needed, then it is preferable to use the internal one (MT).

TIP: when Hardware control is not needed AXE pin can be left unconnected.

TIP: the audio paths can be switched also during a call in both ways.

• Send command

AT#CAP=<n><cr>

where:

<n> = 0 for HARDWARE control with AXE input <n> = 1 for external HF path (regardless of the AXE input status) <n> = 2 for internal MT path (regardless of the AXE input status)

• wait for

OK response

GE863-GPS Software User Guide

1vv0300724 Rev. 2 - 24/01/07

For example: 1 - Let's assume that the desired audio path is always the internal MT

Command:

AT#CAP=2<cr>

Answer:

2 - Let's assume that the desired audio path has to be determined by HARDWARE pin AXE

Command:

AT#CAP=0<cr>

Answer:

Now set the hardware pin AXE in the desired status.

2.6.1.3 Set the desired volume on the active audio path speaker output

This setting is not strictly necessary; it is also possible to keep the default volume setting.

• Send command

AT+CLVL=<vol><cr>

where: <vol> is a number between 0 and 10 representing the volume setting:

0 – minimum volume

10 - maximum volume

• wait for

OK response

NOTE: The volume setting refers to the ACTIVE path ear line and is stored each time. When changing audio path the volume setting will be reset to the previously stored value for that audio path.

2.6.1.4 Check for microphone mute setting

The microphone of the active path can be muted with an AT command; to be sure that it is not muted, it is suggested to check it with this command:

• Send command

AT+CMUT?<cr>

• wait for response in the format:

+CMUT: <mute> OK where:

<mute> is the muting setting for the microphone: 0 - microphone active

GE863-GPS Software User Guide

1vv0300724 Rev. 2 - 24/01/07

1 - microphone muted

NOTE: The mute setting is different from Volume setting: it refers to both the audio paths, the mute setting will remain even when changing audio path.

2.6.2 Phone number dialing

2.6.2.1 Dial a given phone number

• Send command ATD <PhoneNumber><cr>

where: <PhoneNumber> is the phone number to be dialed

• wait for response:

Response Reason Action

OK The call has been placed Wait for the other party to lift

the receiver.. BUSY The line called is busy retry later NO ANSWER The receiver did not answer the

call

retry later NO CARRIER Call placing has not been

successful

check for mobile registration

and signal strength

For example: 1- Let's assume you have to call the national number 040 - 4192111,

command:

ATD 0404192111<cr>

response

OK 2- Let's assume you have to call the national number but in international format +39-40-4192111,

command:

ATD +39404192111<cr>

response

OK 3- Let's assume you have to call the international number +386-40-4192111 without previously setting

the +FCLASS=8 (voice),

command:

ATD +386404192111;<cr>

response

GE863-GPS Software User Guide

1vv0300724 Rev. 2 - 24/01/07

2.6.3 Closing the voice call

2.6.3.1 Hang up the voice call

• Send command

ATH<cr>

• wait for response

TIP: during the voice call the device remains in command mode, so the escape sequence (+++) must not be issued before sending commands.

GE863-GPS Software User Guide

1vv0300724 Rev. 2 - 24/01/07

2.7 Placing a CSD Data call (not GPRS)

Before a data call can be placed, it is recommended to check if the mobile is registered on a network (see par.

2.5.3.1) and if the signal strength is enough to ensure that a call can be made.

2.7.1 Data call device set up

2.7.1.1 Set the device in data mode

• Send command AT+FCLASS=0<cr>

• wait for

OK response

TIP: The +FCLASS setting is maintained in memory, so there's no need to repeat this command if +FCLASS setting is not changed.

2.7.1.2 Set the desired modulation and speed for the connection

The data connection can be made using different modulations at different speeds. This connection mode can be selected with the command +CBST. The syntax for the command is: AT+CBST=<mod>,0,<ce> These parameters can be selected as seen in the table:

Command Modulation Speed

[bps]

Connection

Element

AT+CBST==0, 0, 1 Autobauding ---- non transparent AT+CBST==1, 0, 1 V.21 300 non transparent AT+CBST==2, 0, 1 V.22 1200 non transparent AT+CBST==3, 0, 1 V.23 1200/75 non transparent AT+CBST==4, 0, 1 V.22Bis 2400 non transparent AT+CBST==6, 0, 1 V.32 4800 non transparent AT+CBST==7, 0, 1 V.32 9600 non transparent AT+CBST==14, 0, 1 V.34 14400 non transparent AT+CBST==65, 0, 1 V.110 300 non transparent AT+CBST==66, 0, 1 V.110 1200 non transparent AT+CBST==68, 0, 1 V.110 / X.31 2400 non transparent AT+CBST==70, 0, 1 V.110 / X.31 4800 non transparent AT+CBST==71, 0, 1 V.110 / X.31 9600 non transparent AT+CBST==75, 0, 1 V.110 / X.31 14400 non transparent AT+CBST==1, 0, 0 V.21 300 transparent

GE863-GPS Software User Guide

1vv0300724 Rev. 2 - 24/01/07

AT+CBST==2, 0, 0 V.22 1200 transparent AT+CBST==3, 0, 0 V.23 1200/75 transparent AT+CBST==4, 0, 0 V.22Bis 2400 transparent AT+CBST==6, 0, 0 V.32 4800 transparent AT+CBST==7, 0, 0 V.32 9600 transparent AT+CBST==65, 0, 0 V.110 300 transparent AT+CBST==66, 0, 0 V.110 1200 transparent AT+CBST==68, 0, 0 V.110 / X.31 2400 transparent AT+CBST==70, 0, 0 V.110 / X.31 4800 transparent AT+CBST==71, 0, 0 V.110 / X.31 9600 transparent

Once selected the appropriate <mod > and <ce> parameters from the table:

• Send command

AT+CBST=<mod>,0,<ce><cr>

• wait for

OK response

2.7.2 Phone number dialing (data call)

2.7.2.1 Dial a given phone number

• Send command ATD <PhoneNumber><cr>

where: <PhoneNumber> is the phone number to be dialed

• wait for response:

Response Reason Action

CONNECT 9600 The called modem is now on

line.

exchange data..

BUSY The line called is busy retry later NO ANSWER The receiver did not answer the

call

retry later

NO CARRIER The modem handshaking has

not been successful

check for mobile registration and signal strength and eventually retry.

TIP: The response to the ATD command is returned after the modem handshaking, this takes about 30 seconds, so allow this time before doing anything.

TIP: When the device is doing the handshake the issue of any character closes the handshake and aborts the call.

GE863-GPS Software User Guide

1vv0300724 Rev. 2 - 24/01/07

For example: 1- Let's assume you have to call the national number 040 - 4192111,

command:

ATD 0404192111<cr>

response

CONNECT 9600 2- Let's assume you have to call the national number but in international format +39-40-4192111,

command:

ATD +39404192111<cr>

response

CONNECT 9600 3- Let's assume you have to call the international number +386-40-4192111,

command:

ATD +386404192111<cr>

response

CONNECT 9600

2.7.3 Closing the Data call

2.7.3.1 Exit the data mode and enter the command mode

• Send escape sequence +++

• wait the escape sequence pause time ( see S12 parameter)

• wait for response

NOTE: After the Escape sequence and during the call the only command that is accepted by the GE863-GPS is the ATH. All the other commands are not supported during a call.

TIP: during the escape sequence pause time S12 no further characters should be sent to the device in order to enter the command mode.

GE863-GPS Software User Guide

1vv0300724 Rev. 2 - 24/01/07

2.7.3.2 Hang up the data call

• Send command

ATH<cr>

• wait for response

NO CARRIER

TIP: during the data call the device remains in data (on line) mode, so the escape sequence (+++) must be issued before sending AT commands to the device.

2.8 Answer an incoming Call

When an incoming call is detected the device reports an unsolicited code which may be:

Unsolicited code Reason

RING The extended format of incoming call indication is

disabled and a call (voice or data) is incoming.

+CRING: VOICE The extended format of incoming call indication is

enabled and a voice call is incoming.

+CRING: ASYNC The extended format of incoming call indication is

enabled and an asynchronous transparent data call is incoming.

+CRING: REL ASYNC The extended format of incoming call indication is

enabled and an asynchronous reliable (not transparent) data call is incoming.

+CRING: SYNC The extended format of incoming call indication is

enabled and a synchronous transparent data call is incoming.

+CRING: REL SYNC The extended format of incoming call indication is

enabled and a synchronous reliable (not transparent) data call is incoming.

+CRING: FAX The extended format of incoming call indication is

enabled and a fax call is incoming.

GE863-GPS Software User Guide

1vv0300724 Rev. 2 - 24/01/07

To answer the call:

• Send command

ATA<cr>

• wait for response:

Response Reason Action

CONNECT 9600 The incoming call was a DATA

one and called modem is now on line.

exchange data..

ERROR No incoming call is found, call

may have been lost

call lost

NO CARRIER The incoming call was a DATA

one and the modem handshaking has not been successful

check for mobile registration and signal strength and modem settings.

OK The incoming call was a VOICE

call and is now active.

proceed ahead

TIP: The call is answered with the appropriate type (VOICE or DATA) regardless of the +FCLASS setting active. To distinguish between Data and Voice see the command response or the extended format incoming call indication.

GE863-GPS Software User Guide

1vv0300724 Rev. 2 - 24/01/07

3 Advanced Operations

3.1 Accessing the phonebook

The GE863-GPS can access the phonebook storage of the SIM card inserted, by using specific AT commands it is possible to store and recall phone numbers and their associated name.

3.1.1 Preliminary phonebook set up

The GE863-GPS supports several SIM phonebook storages:

•

"SM" - SIM phonebook

This is the PB used to store and recall numbers during the normal operation of the device.

"FD" - SIM fixed dialing-phonebook (only phase 2/2+ SIM) This PB has several restrictions; to set it you need the PIN2 code and after having activated the FD only the calls to the numbers stored in the FD or their children are allowed, all the other calls are forbidden.

"LD" - SIM last-dialing-list (+CPBW and +CPBF are not applicable for this storage) This is the list of the last dialed numbers, it is updated automatically at each call originated and insertion or search on it is not possible, the only operations allowed are recall, read and delete.

"MC" - SIM missed-calls-list (+CPBW and +CPBF are not applicable for this storage) This is the list of the missed calls calling numbers, it is updated automatically at each call missed and insertion or search on it is not possible, the only operations allowed are recall, read and delete.

"RC" - SIM received-calls-list (+CPBW and +CPBF are not applicable for this storage) This is the list of the received calls calling numbers, it is updated automatically at each call received and insertion or search on it is not possible, the only operations allowed are recall, read and delete.

In order to access the storage you have to choose which one will be active. This must be the first PB operation always. Once selected storage, it is not anymore needed to select it again until the desired storage remains the one active and the device is not turned off.

GE863-GPS Software User Guide

1vv0300724 Rev. 2 - 24/01/07

3.1.1.1 Selecting PB storage active

• Send command

AT+CPBS=<PB><cr>

where: <PB> is the desired PB storage:

SM – SIM phonebook FD – fixed dialing phonebook LD – last dialed calls list MC – missed calls list RC – received calls list

• wait for response:

Response Reason Action

OK selected PB is now active Proceed ahead ERROR some error occurred Enable extended result codes

(see par. 2.5.2.1) and retry.

+CME ERROR: 10 SIM not present Check SIM or require SIM

insertion and repeat from par.

2.5.2.2

+CMS ERROR: 310 SIM not present Check SIM or require SIM

insertion and repeat from par.

2.5.2.2

+CME ERROR: 11 SIM is present and PIN is

required to continue operations

insert SIM PIN (see par.

2.5.2.3)

+CMS ERROR: 311 SIM is present and PIN is

required to continue operations

insert SIM PIN (see par.

2.5.2.3)

+CME ERROR: 12 SIM is present and PUK is

required to continue operations

insert SIM PUK (see par.2.5.2.4)

+CMS ERROR: 316 SIM is present and PUK is

required to continue operations

insert SIM PUK (see par.2.5.2.4)

+CME ERROR: 13 SIM defect Check SIM insertion or require

a new SIM not defected and repeat from par. 2.5.2.2

+CMS ERROR: 313 SIM defect Check SIM insertion or require

a new SIM not defected and

repeat from par. 2.5.2.2 +CME ERROR: 14 SIM is busy retry later +CMS ERROR: 314 SIM is busy retry later +CME ERROR: 15 SIM is wrong type Check SIM, it must be a GSM

SIM. +CMS ERROR: 315

SIM is wrong type

Check SIM, it must be a GSM

GE863-GPS Software User Guide

1vv0300724 Rev. 2 - 24/01/07

SIM. +CME ERROR: 17 PIN2 is required to continue

operations, since FD facility is not enabled.

Enable FD facility with +CLCK

(see par.3.1.1.2)

and retry.

NOTE: After power up & PIN authentication the device reads all the SIM for a backup, hence SIM access is inhibited (SIM is busy after the issue of the PIN or after power up if PIN request is disabled) for a time varying from few seconds to about a minute, depending on the percentage of written records in the SIM phonebook. If Phonebook commands are issued during this time the device returns an error message. If this happens, retry the operations later.

NOTE: Due to the particular features of the FD storage, when selecting the FD storage, the PIN2 must have been inserted or the FD facility must have been enabled. If +CPBS command reports +CME ERROR: 17 then enable the facility with command +CLCK (see par.

3.1.1.2)

For example: 1- Let's assume you want to select the "SM" normal phonebook for operations,

command:

AT+CPBS="SM"<cr>

response

OK 2- Let's assume you want to select the "MC" missed calls list for operations,

command:

AT+CPBS="MC"<cr>

response

3.1.1.2 Enable Fixed Dialing Phonebook facility (only for FD PB)

• Send command

AT+CLCK=FD,1,<PIN2><cr>

where: <PIN2> is the PIN2 code of the SIM.

• wait for response:

Response Reason Action

OK FD facility is now enabled Return to select PB (see par.

3.1.1.1)

ERROR some error occurred Enable extended result codes

(see par. 2.5.2.1), check if the

PIN2 is correct

GE863-GPS Software User Guide

1vv0300724 Rev. 2 - 24/01/07

and retry. +CME ERROR: 16 the inserted PIN2 is wrong Check PIN2 code and retry.

NOTE: When receiving the ERROR or +CME ERROR message, repeat

Query SIM presence and status since after 3 failed attempts SIM PIN2 is not anymore requested, but SIM PUK2 is requested instead, hence you may need to go through procedure

2.5.2.4 (but insert PUK2

instead of PUK1)

3.1.2 Phonebook entry search by Name

As first thing, you must select the "SM" storage as active (see par.

3.1.1.1).

• send command AT+CPBF=<Name><cr>

where: <Name> is the desired string to be found in the name field of the PB record.

•

wait for response in the format:

+CPBF= <index>,"<number>",<type>,"<name>" OK

where: <index> is the record number on the PB; <Number> is the phone number; <type> is the type of number:

145 – international numbering scheme 129 – national numbering scheme

<Name> is the alphanumeric name associated with the number.

or in the case no corresponding entries are found: +CME ERROR: 22 or simply ERROR.

NOTE: The search for <name> string is not case sensitive and the string may or may not be included in double brackets.

For example: 1- Let's assume you want to select the "SM" normal phonebook for operations,

command:

AT+CPBS="SM"<cr>

response

- Now you might want to look for the entries with the name starting with: "FA"

GE863-GPS Software User Guide

1vv0300724 Rev. 2 - 24/01/07

command:

AT+CPBF="FA"<cr>

the response may look like:

+CPBF= 7,"+39404192369",145,"Fabio" +CPBF= 9,"0404192111",129,"Fabrizio" OK

- Now you might want to look for the entries with the name starting with: "FAUSTO" but no record contains this name:

command:

AT+CPBF="FAUSTO"<cr>

response:

+CME ERROR: 22 or if extended error codes are disabled simply

response:

ERROR

3.1.3 Phonebook entry read by Index

As first thing, you must select the desired storage as active (see par.

3.1.1.1). Then:

• send command AT+CPBR=<index><cr>

where: <index> is the index number of the desired PB record to be read.

•

wait for response in the format:

+CPBR= <index>,"<number>",<type>,"<name>" OK

where: <index> is the record number on the PB; <Number> is the phone number; <type> is the type of number:

145 – international numbering scheme 129 – national numbering scheme

<Name> is the alphanumeric name associated with the number.

or in the case the index number does not correspond to a written record: +CME ERROR: 22 or simply ERROR.

GE863-GPS Software User Guide

1vv0300724 Rev. 2 - 24/01/07

For example: 1- Let's assume you want to select the "SM" normal phonebook for operations,

command:

AT+CPBS="SM"<cr>

response

- Now you might want to look for the entry at the position index = 7

command:

AT+CPBR=7<cr>

the response may look like:

+CPBR= 7,"+39404192369",145,"Fabio" OK

- Now you might want to look for the entries at the positions from 7 to 9 and for example the position at index 8 is empty

command:

AT+CPBR=7,9<cr>

the response may look like:

+CPBR= 7,"+39404192369",145,"Fabio" +CPBR= 9,"0404192111",129,"Fabrizio" OK

3.1.4 Phonebook entry Write

As first thing, you must select the desired storage as active (see par.

3.1.1.1). Then:

• send command AT+CPBW=<index>,<number>,<type>,<name><cr>

where: <index> is the index number of the desired PB record to be written (may be omitted if any empty record number can be used). <Number> is the phone number; <type> is the type of number:

145 – international numbering scheme (contains the character "+") 129 – national numbering scheme

<Name> is the alphanumeric name associated with the number.

• wait for response:

Response Reason Action

OK Record has been successfully

written

Proceed ahead

GE863-GPS Software User Guide

1vv0300724 Rev. 2 - 24/01/07

ERROR some error occurred Enable extended result codes

(see par. 2.5.2.1), and retry.

+CME ERROR: 10 SIM not present Check SIM or require SIM

insertion and repeat from par.

2.5.2.2

+CMS ERROR: 310 SIM not present Check SIM or require SIM

insertion and repeat from par.

2.5.2.2

+CME ERROR: 11 SIM is present and PIN is

required to continue operations

insert SIM PIN (see par.

2.5.2.3)

+CMS ERROR: 311 SIM is present and PIN is

required to continue operations

insert SIM PIN (see par.

2.5.2.3)

+CME ERROR: 12 SIM is present and PUK is

required to continue operations

insert SIM PUK (see par.2.5.2.4)

+CMS ERROR: 316 SIM is present and PUK is

required to continue operations

insert SIM PUK (see par.2.5.2.4)

+CME ERROR: 13 SIM defect Check SIM insertion or require

a new SIM not defected and repeat from par. 2.5.2.2

+CMS ERROR: 313 SIM defect Check SIM insertion or require

a new SIM not defected and

repeat from par. 2.5.2.2 +CME ERROR: 14 SIM is busy retry later +CMS ERROR: 314 SIM is busy retry later +CME ERROR: 15 SIM is wrong type Check SIM, it must be a GSM

SIM. +CMS ERROR: 315 SIM is wrong type Check SIM, it must be a GSM

SIM. +CME ERROR: 21 invalid index Change index number or leave

it empty and retry. +CME ERROR: 20 memory full PB storage is full. +CMS ERROR: 322 memory full PB storage is full.

For example: 1- Let's assume you want to select the "SM" normal phonebook for operations,

command:

AT+CPBS="SM"<cr>

response

- Now you might want to write a new record on the PB:

command:

AT+CPBW=,"0404192123",129,"NewRecord"<cr>

response:

GE863-GPS Software User Guide

1vv0300724 Rev. 2 - 24/01/07

-Now you may want to check if operation has really succeeded and where the new record has been written. (obviously operation was successful, since the device returned OK)

command:

AT+CPBF="NEW"<cr>

response:

+CPBF= 8,"0404192123",129,"NewRecord" OK The new record was written at the position index 8. (The first free record index found).

3.1.5 Phonebook entry Delete

As first thing, the desired storage must be active (see par.3.1.1.1). Then:

• send command AT+CPBW=<index><cr>

where: <index> is the index number of the desired PB record to be deleted.

• wait for response:

Response Reason Action

OK Record has been successfully

deleted

proceed ahead ERROR some error occurred Enable extended result codes

(see par. 2.5.2.1), and retry. +CME ERROR: 21 invalid index, out of PB storage

limits

check index number and retry. +CME ERROR: 10 SIM not present Check SIM or require SIM

insertion and repeat from par.

2.5.2.2

+CMS ERROR: 310 SIM not present Check SIM or require SIM

insertion and repeat from par.

2.5.2.2

+CME ERROR: 11 SIM is present and PIN is

required to continue operations

insert SIM PIN (see par.

2.5.2.3)

+CMS ERROR: 311 SIM is present and PIN is

required to continue operations

insert SIM PIN (see par.

2.5.2.3)

+CME ERROR: 12 SIM is present and PUK is

required to continue operations

insert SIM PUK (see

par.2.5.2.4) +CMS ERROR: 316 SIM is present and PUK is

required to continue operations

insert SIM PUK (see

par.2.5.2.4) +CME ERROR: 13 SIM defect Check SIM insertion or require

a new SIM not defected and

repeat from par. 2.5.2.2 +CMS ERROR: 313 SIM defect Check SIM insertion or require

a new SIM not defected and

GE863-GPS Software User Guide

1vv0300724 Rev. 2 - 24/01/07

repeat from par. 2.5.2.2 +CME ERROR: 14 SIM is busy retry later +CMS ERROR: 314 SIM is busy retry later +CME ERROR: 15 SIM is wrong type Check SIM, it must be a GSM

SIM. +CMS ERROR: 315 SIM is wrong type Check SIM, it must be a GSM

SIM.

TIP: The delete operation simply overwrites the record number <index> with an empty record. If the record to be deleted was already empty, no error messages will be shown, but it will be only filled again with empty values.

3.1.6 Phonebook entry Dial

You may want to dial a number previously stored in the phonebook. As first thing, you must find the desired phone number index position, to do it use the +CPBF command. Once the <index> number is known set up the device for the type of call you want to dial. Then:

• send command ATD> <index><cr>

where: <index> is the index number of the desired PB record to be dialed.

wait for response according to the call type you issued.

For example: 1- Let's assume you want to make a Voice call on the internal audio path MT to "Fabio" whose number is stored on the SIM PB:

- Select the PB as active storage

command:

AT+CPBS="SM"<cr>

response

- Now find the index number where "Fabio" is recorded:

command:

AT+CPBF="Fabio"<cr>

the response may look like:

+CPBF= 7,"+39404192369",145,"Fabio" OK

- the first field is the index position: 7 in this case.

- Now set up Voice call:

command:

GE863-GPS Software User Guide

1vv0300724 Rev. 2 - 24/01/07

AT+FCLASS=8<cr>

response:

OK AT#CAP=2 <cr>

OK AT+CLVL=8<cr>

OK AT+CMUT? <cr>

+CMUT: 0

- and Dial: ATD> 7<cr> OK

GE863-GPS Software User Guide

1vv0300724 Rev. 2 - 24/01/07

3.2 Distinguish Calls

3.2.1 Identify the Call type

The GE863-GPS is able to identify the call type before answering it, it is so possible to have different ring indications (unsolicited codes) depending on the call type:

Unsolicited code Reason

RING The extended format of incoming call indication is

disabled and a call (voice or data) is incoming.

+CRING: VOICE The extended format of incoming call indication is

enabled and a voice call is incoming.

+CRING: ASYNC The extended format of incoming call indication is

enabled and an asynchronous transparent data call is incoming.

+CRING: SYNC The extended format of incoming call indication is

enabled and a synchronous transparent data call is incoming.

+CRING: REL ASYNC The extended format of incoming call indication is

enabled and an asynchronous not transparent data call is incoming.

+CRING: REL SYNC The extended format of incoming call indication is

enabled and a synchronous not transparent data call is incoming.

+CRING: FAX The extended format of incoming call indication is

enabled and a fax call is incoming.

In order to use this feature you must enable the extended format of incoming calls

GE863-GPS Software User Guide

1vv0300724 Rev. 2 - 24/01/07

3.2.1.1 Set the extended incoming call indication

• Send command AT+CRC=<n><cr>

where: <n> is the operation mode selected:

0 – extended results Disabled (device reports RING only) 1 – extended results Enabled (device reports +CRING: <type> indication)

• wait for

OK response

3.2.2 Identify the Caller

The GE863-GPS is able to identify the caller number and give indication of it before the call is answered. The calling number is presented after each RING or +CRING indication in the format:

+CLIP: "<number>",<type>[,"<subaddress>",<satype>[,"<alpha>"[,<CLI validity>]]] OK where:

<Number> is the phone number; <type> is the type of number:

145 – international numbering scheme 129 – national numbering scheme

<subaddress> is the subaddress of the calling party <satype> is the type of subaddress <alpha> is an optional string type alphanumeric representation of <number> corresponding to the entry found in phonebook; <CLI validity> is the validity status of CLI presentation:

0 CLI valid. 1 CLI has been withheld by the originator. 2 CLI is not available due to interworking problems or limitation or originating network.

In order to use this feature you must enable the caller ID indication presentation, if feature is disabled then no CLI indication is given after the RING or +CRING code.

GE863-GPS Software User Guide

1vv0300724 Rev. 2 - 24/01/07

3.2.2.1 Set Caller line ID indication presentation

• Send command AT+CLIP=<n><cr>

where: <n> is the operation mode selected:

0 – Calling Line Indication Presentation Disabled 1 – Calling Line Indication Presentation Enabled

• wait for

OK response

For example: 1- Let's assume you receive a call from the national number 1234567890 and extended incoming calls indication is disabled while CLIP is enabled, you'll see:

ring indication:

RING +CLIP: "1234567890",129

2- Let's assume you receive a call from the international number +391234567890 and extended incoming calls indication is disabled while CLIP is enabled, you'll see:

ring indication:

RING +CLIP: "+391234567890",145 NOTE: this does not mean that the incoming call is an international one, it simply means that the

numbering scheme used to identify the caller is the international one.

3.2.3 Restricting Calling Line Indication

The GE863-GPS is able to send the calling line indication (CLI) to the other party through the network when an outgoing call is made. This indication can be restricted (CLIR) in various ways:

•

CLI sent always CLI never sent CLI temporary sent (normally not sent) CLI temporary not sent (normally sent)

GE863-GPS Software User Guide

1vv0300724 Rev. 2 - 24/01/07

3.2.3.1 CLIR Service status query

• send command AT+CLIR?<cr>

•

wait for response in the format:

+CLIR: <n>,<m> OK

where: <n> is the facility status on the Mobile

0 – CLIR facility according to CLIR service network status 1 – CLIR facility active (CLI not sent) 2 – CLIR facility not active (CLI sent)

<m> is the facility status on the Network

0 - CLIR service not provisioned (service unavailable) 1 - CLIR service provisioned (service available) 2 - unknown (e.g. no network present, etc.) 3 - CLI temporary mode presentation restricted 4 - CLI temporary mode presentation allowed

NOTE: The <m> parameter reports the status of the service at network level. If the CLIR service is not provisioned, then it is not possible to use this service and changing the first parameter <n> will not change the CLI presentation to the other party behavior of the network.

For example: 1- Let's assume you want to check your CLIR settings:

command:

AT+CLIR? <cr>

response:

+CLIR: 2,4 In this case the CLIR service is temporary mode allowed on the network and the mobile sends the CLI when calling. (CLI Restriction not active).

GE863-GPS Software User Guide

1vv0300724 Rev. 2 - 24/01/07

3.2.3.2 Restrict/Allow Caller line ID indication

• Send command

AT+CLIR=<n><cr>

where: <n> is the operation mode selected:

0 – Calling Line Indication to the other party According to Network service status. 1 – Calling Line Indication Restriction Enabled (CLI not sent) 2 – Calling Line Indication Restriction Disabled (CLI sent)

• wait for

OK response

For example: 1- Let's assume you want to disable the CLI presentation to the other party permanently:

command:

AT+CLIR=1<cr>

response:

3.2.4 Call Barring Control

The call Barring is a GSM service that allows the user to block certain types of calls:

•

Barring All Outgoing Calls Barring Outgoing International Calls Barring Outgoing International Calls except to Home Country Barring All Incoming Calls Barring Incoming Calls when Roaming outside the home country All Barring services (applicable only for disabling command) All Outgoing barring services (applicable only for disabling command) All Incoming barring services (applicable only for disabling command)

The service can be queried, enabled and disabled.

NOTE: The call Barring service is handled by the network, hence all the relative commands issue a network request and it may take several seconds to have the response from the network. Furthermore, all the Call Barring service commands must be issued when the mobile is Registered on some Network, else an error code is returned ( no network service ).

GE863-GPS Software User Guide

1vv0300724 Rev. 2 - 24/01/07

3.2.4.1 Call Barring Service status query

• send command AT+CLCK=<fac>,2<cr>

where: <fac> is the facility to be queried:

AO - Barring All Outgoing Calls OI - Barring Outgoing International Calls OX- Barring Outgoing International Calls except to Home Country AI - Barring All Incoming Calls IR - Barring Incoming Calls when Roaming outside the home country AB - All Barring services (applicable only for disabling command) AG - All Outgoing barring services (applicable only for disabling command) AC - All Incoming barring services (applicable only for disabling command)

•

wait for response:

Response Reason Action

+CLCK: 0 facility is disabled calls are allowed +CLCK: 1 facility is enabled calls are barred +CME ERROR: 4 operation not supported, the

service required is not available

Check command syntax and

service code +CME ERROR: 30 no network service Check for registration (see par.

2.5.3.1) and signal strength.

NOTE: The call Barring service is handled by the network, hence all the relative commands issue a network request and it may take several seconds to have the response from the network. Furthermore all the Barring service commands must be issued when the mobile is Registered on some Network, else an error code is returned ( no network service ).

For example: 1- Let's assume you want to check whether the incoming calls when roaming outside Home Country are barred or not:

command:

AT+CLCK=IR,2<cr>

response:

+CLCK: 0 In this case, the incoming (received) calls ARE NOT BARRED when in Roaming outside the Home

Country.

GE863-GPS Software User Guide

1vv0300724 Rev. 2 - 24/01/07

2- Let's assume you want to check whether the Outgoing (originated) international calls are barred or not:

command:

AT+CLCK=OI,2<cr>

response:

+CLCK: 1 In this case, the outgoing international calls ARE BARRED.

3.2.4.2 Barring/Unbarring All Incoming Calls

• Send command AT+CLCK=AI,<en>,<pwd><cr>

where: <en> is the operation selected:

0 – Call Barring Disable (Unbarring) 1 – Call Barring Enable (Barring)

<pwd> is the network password required to change facility status

• wait for response:

Response Reason Action

OK Barring is now enabled/disabled all incoming calls will be

barred/unbarred ERROR some error occurred Enable the extended error

codes report (see par.2.5.2.1)

and retry. +CME ERROR: 4 operation not supported, the

service required is not available

Check command syntax +CME ERROR: 30 no network service Check for registration (see par.

2.5.3.1) and signal strength.

+CME ERROR: 16 wrong network password check network password and

retry

For example: 1- Let's assume you want to bar all the incoming calls and the network password of your operator is 0000:

command:

AT+CLCK=AI,1,0000<cr>

response:

GE863-GPS Software User Guide

1vv0300724 Rev. 2 - 24/01/07

3.2.4.3 Barring/Unbarring Incoming Calls when in International Roaming

• Send command AT+CLCK=IR,<en>,<pwd><cr>

where: <en> is the operation selected:

0 – Call Barring Disable (Unbarring) 1 – Call Barring Enable (Barring)

<pwd> is the network password required to change facility status

• wait for response:

Response Reason Action

OK Barring is now enabled/disabled all incoming calls when is

international Roaming will be

barred/unbarred ERROR some error occurred Enable the extended error

codes report (see par.2.5.2.1)

and retry. +CME ERROR: 4 operation not supported, the

service required is not available

Check command syntax +CME ERROR: 30 no network service Check for registration (see par.

2.5.3.1) and signal strength.

+CME ERROR: 16 wrong network password check network password and

retry

For example: 1- Let's assume you want to bar all the incoming calls when the mobile is roaming outside its home country and the network password of your operator is 0000:

command:

AT+CLCK=IR,1,0000<cr>

response:

3.2.4.4 Barring/Unbarring All Outgoing Calls

• Send command AT+CLCK=AO,<en>,<pwd><cr>

where: <en> is the operation selected:

0 – Call Barring Disable (Unbarring) 1 – Call Barring Enable (Barring)

<pwd> is the network password required to change facility status

GE863-GPS Software User Guide

1vv0300724 Rev. 2 - 24/01/07

• wait for response:

Response Reason Action

OK Barring is now enabled/disabled all outgoing calls will be

barred/unbarred ERROR some error occurred Enable the extended error

codes report (see par.2.5.2.1)

and retry. +CME ERROR: 4 operation not supported, the

service required is not available

Check command syntax +CME ERROR: 30 no network service Check for registration (see par.

2.5.3.1) and signal strength.

+CME ERROR: 16 wrong network password check network password and

retry

For example: 1- Let's assume you want to bar all the outgoing calls (originated by mobile) and the network password of your operator is 0000:

command:

AT+CLCK=AO,1,0000<cr>

response:

3.2.4.5 Barring/Unbarring All Outgoing International Calls

• Send command

AT+CLCK=OI,<en>,<pwd><cr>

where: <en> is the operation selected:

0 – Call Barring Disable (Unbarring) 1 – Call Barring Enable (Barring)

<pwd> is the network password required to change facility status

• wait for response:

Response Reason Action

OK Barring is now enabled/disabled all outgoing international calls

will be barred/unbarred ERROR some error occurred Enable the extended error

codes report (see par.2.5.2.1)

and retry. +CME ERROR: 4 operation not supported, the

service required is not available

Check command syntax

GE863-GPS Software User Guide

1vv0300724 Rev. 2 - 24/01/07

+CME ERROR: 30 no network service Check for registration (see par.

2.5.3.1) and signal strength.

+CME ERROR: 16 wrong network password check network password and

retry

For example: 1- Let's assume you want to bar all the outgoing international calls (originated by mobile and to a number outside the home country of the mobile) and the network password of your operator is 1234:

command:

AT+CLCK=OI,1,1234<cr>

response:

3.2.4.6 Barring/Unbarring All Outgoing International Calls except to Home

Country

• Send command AT+CLCK=OX,<en>,<pwd><cr>

where: <en> is the operation selected:

0 – Call Barring Disable (Unbarring) 1 – Call Barring Enable (Barring)

<pwd> is the network password required to change facility status

• wait for response:

Response Reason Action

OK Barring is now enabled/disabled all outgoing international calls

except to Home Country will be

barred/unbarred ERROR some error occurred Enable the extended error

codes report (see par.2.5.2.1)

and retry. +CME ERROR: 4 operation not supported, the

service required is not available

Check command syntax +CME ERROR: 30 no network service Check for registration (see par.

2.5.3.1) and signal strength.

+CME ERROR: 16 wrong network password check network password and

retry

For example: 1- Let's assume you want to bar all the outgoing international calls except the ones towards the Home Country and the network password of your operator is 1234:

command:

GE863-GPS Software User Guide

1vv0300724 Rev. 2 - 24/01/07

AT+CLCK=OX,1,1234<cr>

response:

3.2.4.7 Unbarring all the Calls

• Send command AT+CLCK=AB,0,<pwd><cr>

where: <pwd> is the network password required to change facility status

• wait for response:

Response Reason Action

OK Barring is now disabled all calls will be allowed

(unbarred) ERROR some error occurred Enable the extended error

codes report (see par.2.5.2.1)

and retry. +CME ERROR: 4 operation not supported, the

service required is not available

Check command syntax +CME ERROR: 30 no network service Check for registration (see par.

2.5.3.1) and signal strength.

+CME ERROR: 16 wrong network password check network password and

retry

For example: 1- Let's assume you want to disable all the barring services you might have previously activated and the network password of your operator is 0000:

command:

AT+CLCK=AB,0,0000<cr>

response:

GE863-GPS Software User Guide

1vv0300724 Rev. 2 - 24/01/07

3.3 DTMF tones

DTMF tones are managed by specific AT commands. These tones are generated with AT commands only during voice calls. The minimum duration of a DTMF tone can be set on 10 ms but it should be considered that this value can vary with the limitations on network.

Group high Group low

1209 Hz 1336 Hz 1477 Hz 697 Hz 1 2 3 770 Hz 4 5 6 852 Hz 7 8 9 941 Hz * 0 #

NOTE: The GSM system architecture defines that the audio signal of the DTMF tones is inserted by the network switches on commands sent by the Mobile Station (MS). Thus, the default duration parameters may vary from network to network. In case that the devices to be controlled by DTMF are sensitive related to the duration of the tones and timing of the sequences, dedicated investigations on the parameter settings have to be made.

GE863-GPS Software User Guide

1vv0300724 Rev. 2 - 24/01/07

3.4 GSM Power Saving function

The Telit GE863-GPS has a special function that reduces the power consumption during the idle time, thus allowing a longer standby time with a given battery capacity. This function monitors the DTR line indicating that the OEM application is ready to send commands, when it goes high (3V on UART) then the OEM application is not going to send any commands and the GE863-GPS module can save energy by shutting down its internal serial port. When the OEM application becomes again ready, then the line DTR is tied low (0V on UART); the GE863-GPS detects this condition and powers up the serial port. If the power saving function is activated, then the serial port must support the DTR line since when this line is high (Data Terminal is NOT ready) the device goes into a sleep condition and will not respond to commands until the DTR is tied low (Data Terminal is ready).

NOTE: The power saving function does not affect the network behavior of the GE863-GPS, even during the power save condition the module remains registered on the network and reachable for incoming calls or SMS. If a call income during the power save, then the module will wake up and proceed normally with the unsolicited incoming call code. The DTR functionality is usable only when +CFUN=5 is selected.

TIP: When the GE863-GPS wakes up from the sleep mode, it takes a maximum of 150 milliseconds before it can exchange commands on the serial port. Hence place a delay of at least 150 ms between the port opening (DTR lowering) and command sending. According to the V24 standard, when the module is not ready to receive commands it will tie up the CTS line, while it will pull it down when it's ready to receive commands; hence you can monitor the CTS line to ensure the GE863-GPS is ready for commands.

3.4.1.1 Enabling/Disabling the power saving function

• send command AT+CFUN=<fun><cr>

where: <fun> is the power saving function mode, the supported values are:

0 - minimum functionality, NON-CYCLIC SLEEP mode: in this mode, the AT interface is not accessible. 1 - mobile full functionality with power saving disabled (factory default) 2 - disable TX 4 - disable either TX and RX 5 - mobile full functionality with power saving enabled

• wait for response:

GE863-GPS Software User Guide

1vv0300724 Rev. 2 - 24/01/07

Response Reason Action

OK The power save is now active ERROR some error occurred Enable extended result codes

(see par. 2.5.2.1), and retry.

+CME ERROR: 4 operation not supported Check command syntax and

<fun> value.

TIP: The power saving function is disabled by default when the device starts up, in order to guarantee that even without the DTR line support it is possible to exchange commands with the module; for this reason the power saving setting command shall be issued after every power up.

NOTE: The power saving for GSM part will not be activated if the GPS part is switched on. The DTR functionality is usable only when +CFUN=5 is selected.

GE863-GPS Software User Guide

1vv0300724 Rev. 2 - 24/01/07

3.5 SMS handling

The Telit GE863-GPS supports the Short Message Service, it is possible to store, delete, write, send and receive a SMS, which is a short text message up to 160 characters long.

3.5.1 SMS device setup

Before accessing the Short Message Service, the device has to be properly set up.

3.5.1.1 Select SMS format type.

The GE863-GPS supports SMS in two different formats:

• PDU

• Text

The difference is that in the PDU mode the device returns and receives SMS encoded in the format ready to be sent to the network; in TEXT mode the device converts automatically the read PDU into text and viceversa. By using TEXT mode the PDU data encoding knowledge is not needed and operations are easier. For this reason, we will use the TEXT mode to explain how to operate with SMS. If you are familiar with PDU encoding then you can operate with PDU by selecting that format and using appropriate command syntax.

• Send command

AT+CMGF=<mode><cr>

where: <mode> is the SMS format type:

0 – PDU 1 – Text

• wait for response

TIP: This setting is stored and remains until the device is turned off. Hence, there's no need to issue it more than one time. For TEXT mode use <mode>=1.

For example: 1- Let's assume you want to set TEXT format for the SMS:

command:

AT+CMGF=1<cr>

response:

GE863-GPS Software User Guide

1vv0300724 Rev. 2 - 24/01/07

3.5.1.2 Check SMS Service Centre number

The SMS are sent by the GE863-GPS to a service centre (SMSC) where the message is dispatched towards its final destination or is kept until the delivery is possible. To ensure a correct behavior of this service the number of the service centre must be the one your network operator supports. To check which number is stored as the SMSC:

• send command AT+CSCA?<cr>

•

wait for response in the format:

+CSCA: <number>,<type> OK

where: <number> is the SMSC number <type> is the SMSC number type:

145 – international numbering scheme (number begins with "+") 129 – national numbering scheme

TIP: This settings remains stored in the SIM card until it is changed or deleted, so this operation may be done only once if the SIM Card is not changed. The setting is maintained even after power down.

For example: 1- Let's assume you want to check your SMSC number:

command:

AT+CSCA? <cr>

response:

+CSCA: +393359609600 OK

3.5.1.3 Add SMS Service Centre number (only if required)

If your previously check for SMSC returned an empty field: +CSCA: ,129 or if the SMSC number stored does not correspond to the desired one, then the new number has to be stored. In this way the previously stored number will be overwritten.

• send command AT+CSCA=<number>,<type><cr>

where: <number> is the desired SMSC number <type> is the SMSC number type:

145 – international numbering scheme (number begins with "+") 129 – national numbering scheme

wait for

•

GE863-GPS Software User Guide

1vv0300724 Rev. 2 - 24/01/07

For example: 1- Let's assume your desired SMSC number is +39335123456 (stored in international format):

command:

AT+CSCA=+39335123456,145<cr>

response:

3.5.1.4 Select New Messages indication behavior

When the device receives a new message a unsolicited indication is generated, this indication may be sent to the DTE, buffered if the DTE is busy (for example during a data call) or discarded. To set the desired behavior:

• send command AT+CNMI=<mode>,<mt>,<bm>,<ds>,<bfr><cr>

where:

Set command selects the behaviour of the device on how the receiving of new messages from the network is indicated to the DTE.

Parameter: <mode> - unsolicited result codes buffering option 0 - Buffer unsolicited result codes in the TA. If TA result code buffer is full, indications can be

buffered in some other place or the oldest indications may be discarded and replaced with the new received indications.

1 - Discard indication and reject new received message unsolicited result codes when TA-TE link is

reserved, otherwise forward them directly to the TE.

2 - Buffer unsolicited result codes in the TA in case the DTE is busy and flush them to the TE after

reservation. Otherwise forward them directly to the TE.

3 - if <mt> is set to 1 an indication via 100 ms break is issued when a SMS is received while the

module is in GPRS online mode. It enables the hardware ring line for 1 s. too. <mt> - result code indication reporting for SMS-DELIVER 0 - No SMS-DELIVER indications are routed to the TE. 1 - If SMS-DELIVER is stored into ME/TA, indication of the memory location is routed to the TE using

the following unsolicited result code:

+CMTI: <memr>,<index>

where: <memr> - memory storage where the new message is stored "SM" "ME" <index> - location on the memory where SM is stored.

2 - SMS-DELIVERs (except class 2 messages and messages in the message waiting indication

group) are routed directly to the TE using the following unsolicited result code:

(PDU Mode)

+CMT: <alpha>,<length><CR><LF><pdu>

where:

GE863-GPS Software User Guide

1vv0300724 Rev. 2 - 24/01/07

<alpha> - alphanumeric representation of originator/destination number corresponding to the

entry found in MT phonebook <length> - PDU length <pdu> - PDU message

(TEXT Mode)

+CMT:<oa>,<alpha>,<scts>[,<tooa>,<fo>,<pid>,<dcs>,

<sca>,<tosca>,<length>]<CR><LF><data> (the information written in italics will be present depending on +CSDH last setting) where: <oa> - originating address, string type converted in the currently selected character set (see

+CSCS)

<alpha> - alphanumeric representation of <oa>; used character set should be the one selected

with either command +CSCS or @CSCS. <scts> - arrival time of the message to the SC <tooa>, <tosca> - type of number <oa> or <sca>: 129 - number in national format 145 - number in international format (contains the "+") <fo> - first octet of GSM 03.40 <pid> - Protocol Identifier <dcs> - Data Coding Scheme <sca> - Service Centre address, string type, converted in the currently selected character set

(see +CSCS) <length> - text length <data> - TP-User-Data

Class 2 messages and messages in the message waiting indication group (stored message) result in indication as defined in <mt>=1.

3 - Class 3 SMS-DELIVERs are routed directly to TE using unsolicited result codes defined in

<mt>=2. Messages of other data coding schemes result in indication as defined in <mt>=1.

<bm> - broadcast reporting option

0 - Cell Broadcast Messages are not sent to the DTE 2 - New Cell Broadcast Messages are sent to the DTE with the unsolicited result code:

(PDU Mode)

+CBM: <length><CR><LF><PDU>

where: <length> - PDU length <PDU> - message PDU

(TEXT Mode)

+CBM:<sn>,<mid>,<dcs>,<pag>,<pags><CR><LF><data>

where: <sn> - message serial number <mid> - message ID <dcs> - Data Coding Scheme

GE863-GPS Software User Guide

1vv0300724 Rev. 2 - 24/01/07

<pag> - page number <pags> - total number of pages of the message <data> - CBM Content of Message

<ds> - SMS-STATUS-REPORTs reporting option 0 - status report receiving is not reported to the DTE 1 - the status report is sent to the DTE with the following unsolicited result code:

(PDU Mode)

+CDS: <length><CR><LF><PDU>

where: <length> - PDU length <PDU> - message PDU

(TEXT Mode)

+CDS: <fo>,<mr>,,,<scts>,<dt>,<st>

where: <fo> - first octet of the message PDU <mr> - message reference number <scts> - arrival time of the message to the SC <dt> - sending time of the message <st> - message status as coded in the PDU

2 - if a status report is stored, then the following unsolicited result code is sent:

+CDSI: <memr>,<index>

where: <memr> - memory storage where the new message is stored "SM" <index> - location on the memory where SM is stored

<bfr> - buffered result codes handling method: 0 - TA buffer of unsolicited result codes defined within this command is flushed to the TE when

<mode>=1..3 is entered (OK response shall be given before flushing the codes)

1 - TA buffer of unsolicited result codes defined within this command is cleared when <mode>=1..3

is entered.

NOTE: issuing AT+CNMI<CR> is the same as issuing the Read command.

NOTE: issuing AT+CNMI=<CR> is the same as issuing the command AT+CNMI=0<CR>.

• wait for

TIP: In this command description the values that are always 0 are parameter reserved for future use, in the current software revision the only value supported is 0.

GE863-GPS Software User Guide

1vv0300724 Rev. 2 - 24/01/07

For example: 1- Let's assume you want to eliminate all the unsolicited codes that may be sent when receiving SMS & Status Report:

command:

AT+CNMI= 0,0,0,0,0<cr>

response:

OK For example about a new message indication:

1- Let's assume you receive a new SMS delivery (AT+CNMI=1,1,0,0,0) and this new message is stored on the SIM "SM" storage at the location number 7; the unsolicited code you will receive (if code is enabled) is:

unsolicited code:

+CMTI: "SM",7 2- Let's assume you receive a new SMS Status Report delivery (AT+CNMI=1,0,0,2,0) and this new

message is stored on the SIM "SM" storage at the location number 8; the unsolicited code you will receive is:

unsolicited code:

+CDSI: "SM",8

3.5.1.5 Set Text Mode Parameters (only in TEXT mode)

When the device is set to operate with Text SMS not with PDU, the SMS parameters that usually reside on the header of the PDU must be set apart with the command +CSMP. The parameters to be set are:

•

Message Format Validity Period Protocol Identifier Data Coding Scheme

The meaning and format of the parameters is:

- Message format, like defined for the first octet of message according to GSM 3.40: The format is an 8-bit parameter divided into 6 fields and then reported as an integer:

b7 b6 b5 b4 b3 b2 b1 b0

RP UDHI SRR VPF RD MTI

where

MTI message type parameter:

0 1 - SMS Submit (only value supported)

RD reject duplicates parameter

0 - don't reject duplicates SMS in SC 1 - reject duplicates on SC

GE863-GPS Software User Guide

1vv0300724 Rev. 2 - 24/01/07

VPF validity period format

0 0 - Validity period NOT present 1 0 - VP integer represented (relative) 1 1 - VP semi octet represented (absolute) 0 1 - reserved

SRR status report request

0 - status report not requested 1 - status report requested

UDHI user data Header Information

0 - No Header on PDU 1 - Header present on PDU

RP reply path

0 - RP not set 1 - RP set

- Validity Period numerical if in relative format or string if in absolute format

This parameter represents the validity period for the SMS after which the message should be disregarded instead of being delivered. If in relative format (see VPF parameter) it is an integer:

0 to 143 – corresponding to (VP + 1) x 5 minutes 144 to 167 – corresponding to 12 hours + ((VP -143) x 30 minutes) 168 to 196 – corresponding to (VP - 166) x 1 day 197 to 255 – corresponding to (VP - 192) x 1 week

If in absolute format it is a string in the format:

"gg/MM/YY,hh:mm:ss±tz"

where

gg day of expiration (2 characters) MM month of expiration (2 characters) YY year of expiration (2 characters) hh hour of expiration (2 characters) mm minute of expiration (2 characters) ss second of expiration (2 characters) ± sign of the time zone ( + or - ) tz time zone (2 characters)

- Protocol Identifier in numerical format:

This parameter identifies the protocol used by the receiver entity and informs the SC that the conversion from SMS to that protocol should be done while delivering the message.

Protocol ID Conversion towards..

0 Implicit (default)

33 telex (or teletex reduced to telex

format)

34 group 3 telefax

GE863-GPS Software User Guide

1vv0300724 Rev. 2 - 24/01/07

35 group 4 telefax 36 voice telephone (i.e. conversion to

speech)

37 ERMES (European Radio Messaging

System)

38 National Paging system (known to the

SC) 39 Videotex (T.100/T.101) 40 teletex, carrier unspecified 41 teletex, in PSPDN 42 teletex, in CSPDN 43 teletex, in analog PSTN 44 teletex, in digital ISDN 45 UCI (Universal Computer Interface,

ETSI DE/PS 3 01-3)

46-47 (reserved, 2 combinations)

48 a message handling facility (known to

the SC) 49 any public X.400-based message

handling system 50 Internet Electronic Mail

51-55 (reserved, 5 combinations) 56-62 values specific to each SC, usage

based on mutual agreement between

the SME and the SC (7 combinations

available for each SC) 63 A GSM mobile station. The SC

converts the SM from the received TP-

Data-Coding-Scheme to any data

coding scheme supported by that MS

(e.g. the default). 64 Short Message Type 0 65 Replace Short Message Type 1 66 Replace Short Message Type 2 67 Replace Short Message Type 3 68 Replace Short Message Type 4 69 Replace Short Message Type 5 70 Replace Short Message Type 6 71 Replace Short Message Type 7

72..94 Reserved 95 Return Call Message

96..126 Reserved 127 SIM Data download

GE863-GPS Software User Guide

1vv0300724 Rev. 2 - 24/01/07

- Data coding Scheme as defined by GSM 3.38 – in numerical format The DCS is an 8-bit parameter reported as an integer, the default value is 0, otherwise for simplicity, we report only the most useful DCS, for further Schemes refer to GSM 3.38

b7 b6 b5 b4 b3 b2 b1 b0

1 1 1 1 0 Alpha

bet

Class

where

Alphabet

0 - default Alphabet 1 - 8 bit

Class

0 0 - Class 0 0 1 - Class 1 1 0 - Class 2 1 1 - Class 3

TIP: The default value for DCS = 0 represents the default SMS sent by a mobile. If you don't need any particular data coding scheme use DCS=0.

NOTE: Not all the DCS combinations described in the GSM 3.38 are supported, both by the network and by the Telit GE863-GPS. Some features may be not implemented at network level or at device level, resulting in a +CMS ERROR: 303 (operation not supported) result code. If this happens then use a different DCS.

• send command AT+CSMP=<fo>,<vp>,<pid>,<dcs><cr>

where:

<fo>: Message format <vp>: Validity Period <pid>: Protocol Identifier <dcs>: Data coding Scheme

wait for

•

For example: 1- Let's assume you want to set the SMS parameters to the values:

- Message Format:

- SMS submit

- don't reject duplicates

- VP Format integer (relative)

- status report not requested

- No Header on PDU

- Reply path not set

GE863-GPS Software User Guide

1vv0300724 Rev. 2 - 24/01/07

Hence, the message format is the binary number 00010001 corresponding to the integer 17.

- Validity period 24 hours corresponding to an integer value 167.

12 hours + ((167 -143) x 30 min) = 24 hours

- Protocol ID implicit (SMS sent to a mobile terminal) corresponding to a value 0.

- DCS default value 0.

command:

AT+CSMP= 17,167,0,0

response:

OK 2- Let's assume you want to set the SMS parameters to the values:

- Message Format:

- SMS submit

- don't reject duplicates

- VP Format semi octet (absolute)

- status report requested

- No Header on PDU

- Reply path not set

Hence, the message format is the binary number 00111001 corresponding to the integer 57.

- Validity period format is absolute, hence it represents the expiration date of the message and the

desired expiration date is for example 29/06/02 at 02:20 in the time zone of Italy (+1). "29/06/02,02:20:00+1"

- Protocol ID implicit (SMS sent to a mobile terminal) corresponding to a value 0.

- Data Coding Scheme:

- Default Alphabet

- Class 0 (e.g. immediate display SMS)

Corresponding to the binary number 11110000 corresponding to the integer 240.

command:

AT+CSMP= 57,29/06/02,02:20:00+1,0,240

response:

3.5.1.6 Select SMS Memory and check for memory space

There are various types of storage where the SMS can be stored, the Telit GE863-GPS provides two different storage:

"ME" - mobile equipment memory

"SM" - SIM Card memory The SMS are usually stored (this is true for both the originated and the received SMS) in the SM storage, the "ME" storage is a read only one where the Class 0 messages received are stored (regardless of the selected active storage which may be "SM"). For this reason the "ME" storage can be selected to read the Class 0 messages.

GE863-GPS Software User Guide

1vv0300724 Rev. 2 - 24/01/07

The GE863-GPS allows the user to select a different storage for the read-delete, write-send, and reception-saving SMS operations.

• send command AT+CPMS=<memr>,<memw>,<mems><cr>

where:

<memr>: memory storage for Read and Delete commands

- "SM"

- "ME" (No Delete operations allowed) <memw>: memory storage for Write and Send commands <mems>: memory storage for new incoming message saving

- "SM" only

• wait for response in the format:

+CPMS:<usedr>,<totalr>,<usedw>,<totalw>,<useds>,<totals> OK where

<usedr> - number of SMS stored into <memr> <totalr> - max number of SMS that <memr> can contain <usedw> - number of SMS stored into <memw> <totalw> max number of SMS that <memw> can contain <useds> - number of SMS stored into <mems> <totals> max number of SMS that <mems> can contain

From this response you can check if the selected storage has room for new SMSs, the free positions in the storage X (where X can be r,w,s ) are <totalX> -<usedX>.

3.5.2 IRA character set

The character set used in SMS text mode is the IRA. This set defines each char as a 7-bit value, hence from 0x00 to 0x7F. The table below reports all the chars supported and their hexadecimal code. To obtain the code for a char in the table remember that in the row it is reported the least significant nibble (4 bits) and in the column the most significant nibble. The empty cells correspond to reserved combinations.

Most Significant Nibble 0x 1x 2x 3x 4x 5x 6x 7x

x0 SP10 @ P p x1 ! 1 A Q a q x2 " 2 B R b r x3 # 3 C S c s x4 $ 4 D T d t x5 % 5 E U e u

Least Significant

Nibble

x6 & 6 F V f v

GE863-GPS Software User Guide

1vv0300724 Rev. 2 - 24/01/07

x7 ' 7 G W g w x8 ( 8 H X h x x9 ) 9 I Y i y xA LF

* : J Z j z

xB + ; K k xC , < L l xD CR3 - = M m xE . > N n xF / ? O £ o

- SP stands for space character

- LF stands for Line Feed character

- CR stands for Carriage Return character

For example: 1- Let's assume you want to find the IRA code for the character '&': From the table you find:

- most significant Nibble: 2

- least significant Nibble: 6 Hence the IRA code for the '&' character is the hexadecimal 0x26.

2- Let's assume you have the IRA code 0x6B and you want to find the corresponding character: From the table you find at the position

- most significant Nibble: 6

- least significant Nibble: B Hence, the character corresponding to the 0x6B IRA code is 'k'.

TIP: With the command AT+CSCS is possible to select the character set; the available types are:

“IRA” - ITU-T.50 ”8859-1” - ISO 8859 Latin 1 ”PCCP437” - PC character set Code Page 437. ”UCS2” - 16-bit universal multiple-octet coded character set (ISO/IEC10646)

Please refer to the AT command specification for the full command description

GE863-GPS Software User Guide

1vv0300724 Rev. 2 - 24/01/07

3.5.3 Writing a New SMS to storage

A new SMS can be written in the selected storage <memw> (in the current SW version only "SM" is supported) and then can be sent to the desired destination. To write the new SMS:

• send command AT+CMGW="<da>"<cr>

where:

<da>: destination address

wait for prompt "

•

send SMS text (MAX 160 characters) end command with CTRL-Z character (0x1A hexadecimal) or abort command with ESC character (0x1B hexadecimal) wait for response:

Response Reason Action

+CMGW: <index> OK

Message has been successfully written in position number <index>

proceed ahead

ERROR some error occurred Enable the extended error

codes report (see par.2.5.2.1) and retry.

+CMS ERROR: 330 SMSC address unknown Insert SMSC address (see par.

3.5.1.3)

+CMS ERROR: 322 Memory Full memory is full, hence delete

some records and retry.

NOTE: if command is aborted with ESC character, then only the OK result code is returned.

For example: 1- Let's assume you want to write a new SMS to the storage and the destination address is the number +39338123456789. We suppose you already have set up the device for text SMS mode as described on the previous paragraphs:

command:

AT+CMGW="+39338123456789"

response:

now you can insert the message text in IRA format (note that the IRA format and ASCII format coincide for the alphabet characters but not for the other).

…. here will be inserted the SMS message text….

conclude text with the character CTRL-Z response:

GE863-GPS Software User Guide

1vv0300724 Rev. 2 - 24/01/07

+CMGW: 3 OK In this case, the new SMS was successfully written to the location index 3 of the selected write

memory (always "SM" SIM Card memory).

3.5.4 Sending an SMS previously stored

An already written SMS can be sent from the selected storage <memw> (in the current SW version only "SM" is supported). To send the written SMS its location index is needed:

• send command AT+CMSS=<index><cr>

where:

<index>: SMS location index

• wait for response:

Response Reason Action

+CMSS: <mr> OK

Message has been successfully sent. <mr> represents the message reference number.

proceed ahead

ERROR some error occurred Enable the extended error

codes report (see par.2.5.2.1) and retry.

+CMS ERROR: 330 SMSC address unknown Insert SMSC address (see par.

3.5.1.3)

+CMS ERROR: 41 "Temporary Failure", may be

that the device is not registered on any network

Check for signal strength and network registration

+CMS ERROR: 331 No network service Check for signal strength and

network registration

+CMS ERROR: 1 Unassigned number The destination address

number does not exist. Check it

and repeat command. +CMS ERROR: 42 network congestion Retry later +CMS ERROR: 96 Mandatory information missing Check for destination address

in the SMS, overwrite it and

retry.

GE863-GPS Software User Guide

1vv0300724 Rev. 2 - 24/01/07

For example: 1- Let's assume you want to send a SMS that was written to the storage index position number 3. We suppose you already have set up the device for text SMS mode as described on the previous paragraphs:

command:

AT+CMSS=3

response:

+CMSS: 1 OK In this case, the SMS was successfully sent to the destination and its network message reference

number is 1.

3.5.5 Sending a new SMS without storing it

A new SMS can be sent directly to the network without storing it.

• send command AT+CMGS="<da>"<cr>

where:

<da>: destination address

wait for prompt "

•

send SMS text (MAX 160 characters) end command with CTRL-Z character (0x1A hexadecimal) or abort command with ESC character (0x1B hexadecimal)

• wait for response:

Response Reason Action

+CMGS: <mr> OK

Message has been successfully sent. <mr> represents the message reference number.

proceed ahead

ERROR some error occurred Enable the extended error

codes report (see par.2.5.2.1) and retry.

+CMS ERROR: 330 SMSC address unknown Insert SMSC address (see par.

3.5.1.3)

+CMS ERROR: 41 "Temporary Failure", may be

that the device is not registered on any network

Check for signal strength and network registration

+CMS ERROR: 331 No network service Check for signal strength and

network registration

+CMS ERROR: 1 Unassigned number The destination address

number does not exist. Check it and repeat command.

GE863-GPS Software User Guide

1vv0300724 Rev. 2 - 24/01/07

+CMS ERROR: 42 network congestion Retry later +CMS ERROR: 96 Mandatory information missing Check for destination address

in the SMS, overwrite it and retry.

OK command aborted by user you issued a ESC char

For example: 1- Let's assume you want to directly send a new SMS to the destination address number +39338123456789. We suppose you already have set up the device for text SMS mode as described on the previous paragraphs:

command:

AT+CMGS="+39338123456789"

response:

now you can insert the message text in IRA format (note that the IRA format and ASCII format coincide for the alphabet characters but not for the other).

…. here will be inserted the SMS message text to be sent….

conclude text with the character CTRL-Z response:

+CMGW: 4 OK In this case, the new SMS was successfully sent to the SC and its network reference number is 4.

Do not confuse message reference with message index position, the first indicates the network reference for identifying the sent message (the eventually requested status report will have the same reference) while the second indicates the position where the message has eventually been stored in memory.

3.5.6 Deleting an SMS

An already written/received SMS can be deleted from the selected storage (in the current SW version only "SM" is supported). To delete the SMS its location index is needed:

• send command AT+CMGD=<index><cr>

where:

<index>: SMS location index

• wait for response:

GE863-GPS Software User Guide

1vv0300724 Rev. 2 - 24/01/07

Response Reason Action

OK Message has been successfully

deleted.

proceed ahead

ERROR some error occurred Enable the extended error

codes report (see par.2.5.2.1) and retry.

+CMS ERROR: 321 Invalid memory index

e.g. the given record was already empty

Check the <index> number and retry.

For example: 1- Let's assume you want to delete a previously written SMS that was written to the storage index position number 3. We suppose you already have set up the device for text SMS mode as described on the previous paragraphs:

command:

AT+CMGD=3

response:

OK In this case, the SMS was successfully deleted. 2- Let's assume you want to delete a received SMS that was stored to the index position number 7:

command:

AT+CMGD=7

response:

3.5.7 Reading an SMS

A new SMS can be read with the command:

• send command AT+CMGR=<index><cr>

where:

<index>: SMS location index

• wait for response in the format:

Output format for received messages (the information written in italics will be present depending on

+CSDH last setting): +CMGR: <stat>,<oa>,<alpha>,<scts>[,<tooa>,<fo>,<pid>, <dcs>,<sca>,<tosca>,<length>]<CR><LF><data>

Output format for sent messages:

GE863-GPS Software User Guide

1vv0300724 Rev. 2 - 24/01/07

+CMGR: <stat>,<da>,<alpha>[,<toda>,<fo>,<pid>,<dcs>,, <sca>,<tosca>,<length>]<CR><LF><data>

Output format for message delivery confirm:

+CMGR: <stat>,<fo>,<mr>,,,<scts>,<dt>,<st> where:

<stat> - status of the message "REC UNREAD" - new received message unread "REC READ" - received message read "STO UNSENT" - message stored not yet sent "STO SENT" - message stored already sent <fo> - first octet of the message PDU

<mr> - message reference number <scts> - arrival time of the message to the SC <dt> - sending time of the message <st> - message status as coded in the PDU

<pid> - Protocol Identifier <dcs> - Data Coding Scheme

<oa> - Originator address, string type represented in the currently selected character set (see

+CSCS)

<da> - Destination address, string type represented in the currently selected character set (see

+CSCS)

<alpha> - string type alphanumeric representation of <da> or <oa>, corresponding to an entry found

in the phonebook; used character set is the one selected with command +CSCS. NB: this optional field is currently not supported.

<sca> - Service Centre number <tooa>,<toda >,<tosca> - type of number <oa>,<da>,<sca>

129 - number in national format 145 - number in international format (contains the "+") <length> - text length <data> - TP-User_data

• If <dcs> indicates that GSM03.38 default alphabet is used , each character of GSM alphabet will be converted into current TE character set (see +CSCS)

• If <dcs> indicates that 8-bit or UCS2 data coding scheme is used, each 8-bit octet will be converted into two IRA character long hexadecimal number (e.g. octet 0x2A will be converted as two characters 0x32 0x41)

NOTE: in both cases if status of the message is 'received unread', status in the storage changes to 'received read'.

NOTE: an error result code is sent on empty record <index>.

For example: 1- Let's assume you want to read the SMS that is stored at the position index 4. We suppose you already have set up the device for text SMS mode as described on the previous paragraphs:

GE863-GPS Software User Guide

1vv0300724 Rev. 2 - 24/01/07

command:

AT+CMGR=4

response:

+CMGR: "STO UNSENT","+393351234565" Telit Test Message for Text Mode SMS. OK

In this case the SMS was successfully read, the text contained was: " Telit Test Message for Text Mode SMS." The message was written to the storage by user (STO) but still not sent (UNSENT) to the destination address that's the number +393351234565

2- Let's assume you want now to read the SMS that is stored at the position index 5:

command:

AT+CMGR=5

response:

+CMGR: "REC UNREAD","+393381234567890", ,"29/06/01,12:30:04+01" Telit Test Message for Text Mode SMS RECEIVING. OK

In this case the SMS was successfully read, the text contained was: " Telit Test Message for Text Mode SMS RECEIVING." The message was received (REC) from the number +393381234567890 at 12:30:04 the day 29/06/01 in the European time zone +1.

After this read command the message at index 5 becomes REC READ.

3.5.8 Listing a group of SMSs

The SMS can be grouped into 5 different groups depending on their status:

 REC UNREAD - received messages still not read  REC READ - received messages already read  STO UNSENT - written messages not yet sent  STO SENT - written messages already sent  ALL - all types of messages

It is possible to have the list of all the messages in one group:

• send command AT+CMGL=<stat><cr>

where:

<stat> - status group of the message

"REC UNREAD" - new message "REC READ" - read message "STO UNSENT" - stored message not yet sent "STO SENT" - stored message already sent

GE863-GPS Software User Guide

1vv0300724 Rev. 2 - 24/01/07

"ALL" - all messages

• wait for response in the format:

For every message in the group: +CMGL: <index>,<stat>,<oa/da> [,,,<tooa/toda>,<length>] <CR><LF><text>

where:

<index> - message index position on the storage <stat> - status of the message

"REC UNREAD" - new message "REC READ" - read message "STO UNSENT" - stored message not yet sent

"STO SENT" - stored message already sent <oa/da> - sender number/destination number < tooa/toda > - type of number <oa/da>

145 - international number (contains "+" character)

129 - national number <length> - length of the message text in characters <text> - message text

NOTE: If status of the message is 'received unread', status in the storage changes to 'received read'.

For example: 1- Let's assume you want to list all the SMS received read that are stored. We suppose you already have set up the device for text SMS mode as described on the previous paragraphs:

command:

AT+CMGL="REC READ"

response:

+CMGL: 5, "REC READ","+393381234567890" Telit Test Message for Text Mode SMS RECEIVING. +CMGL: 8, "REC READ","+393381234567890" Telit Second Test Message for Text Mode SMS RECEIVING. OK

In this case the SMS group was successfully read, the messages Received UNREAD were two in the position indexes 5 & 8. The optional parameters <tooa/toda> and <length> were not shown.

GE863-GPS Software User Guide

1vv0300724 Rev. 2 - 24/01/07

3.6 Using General Purpose Input/Output pins

The Telit GE863-GPS provides various General Purpose Input/Output pins, these pins can be configured via AT commands as Inputs, Outputs and two of them as "alternate function". The "alternate function" are supported by pins GPIO5, which can be configured to become a RF Transmission monitor output pin that reflects the RF transmission activation, GPIO6, which can be configured to become an alarm output pin that reflects the alarm status, and GPIO7 which can be configured to become a buzzer output pin. With these pins your application can control external hardware directly using the Telit GE863-GPS pins, with little or even no hardware added.

3.6.1 GPIO pin setup

Before using the GPIO pin, you must configure them to select their direction or alternate function

3.6.1.1 Setting GPIO pin as OUTPUT

When you set a GPIO as output, you must specify also the value that the pin output must take:

• Send command

AT#GPIO=<pin>,<value>,1<cr>

where: <pin> is the GPIO pin number at which the command applies:

1 – GPIO1 10 – GPIO10 2 – GPIO2 11 – GPIO11 3 – GPIO3 12 – GPIO12 4 – GPIO4 13 – GPIO13 5 – GPIO5 14 – GPIO14 6 – GPIO6 15 – GPIO15 7 – GPIO7 16 – GPIO16 8 – GPIO8 17 – GPIO17 9 – GPIO9 18 – GPIO18

<value> is the GPIO pin value that the pin will assume:

0 – LOW 1 – HIGH

• wait for response

NOTE: The #GPIO setting is not saved and will be lost on power off, so at start-up repeat pin initialization commands. At start-up the setting for GPIO6 and GPIO7 instead is maintained even after a shutdown to permit alarm & buzzer feature to work always.

GE863-GPS Software User Guide

1vv0300724 Rev. 2 - 24/01/07

For example: 1- Let's assume you want to set GPIO3 pin as Output and you want it to be in LOW status:

command:

AT#GPIO=3,0,1<cr>

response:

OK In this case, the GPIO3 pin was successfully put in output direction and its status has been set to

LOW.

3.6.1.2 Setting GPIO pin as INPUT

When you set a GPIO as input, you must specify also a dummy value for the pin state:

• Send command

AT#GPIO=<pin>,<dummy_value>,0<cr>

where: <pin> is the GPIO pin number at which the command applies:

<value> is a dummy value can be either:

0 – dummy value 1 – dummy value

• wait for response

NOTE: The #GPIO setting for all GPIO except from GPIO6, GPIO7, is not saved and will be lost on power off, so at start-up repeat pin initialization commands. At start-up all the GPIOs except from GPIO6 & GPIO7 are configured by default as INPUT, but the setting for GPIO6 and GPIO7 instead is maintained even after a shutdown to permit alarm & buzzer feature to work always.

For example: 1- Let's assume you want to set GPIO4 pin as Input:

command:

AT#GPIO=4,0,0<cr>

response:

GE863-GPS Software User Guide

1vv0300724 Rev. 2 - 24/01/07

In this case, the GPIO4 pin was successfully put in input direction.

3.6.2 GPIO pin use

After having set-up the GPIO pin direction you can query the input status of an INPUT pin or set the output status of an OUTPUT pin.

3.6.2.1 Querying GPIO pin status

To query for the pin status:

• Send command

AT#GPIO=<pin>,2<cr>

where: <pin> is the GPIO pin number at which the command applies:

• wait for response in the format:

#GPIO: <dir>,<stat> OK

where:

<dir> - GPIO<pin> direction setting <stat> - status of the pin 0 - LOW 1 - HIGH

NOTE: In case the GPIO pin direction is set to ALTERNATE FUNCTION (2), then the reported <stat> has no meaning and shall not kept as valid, but shall be threaten as a dummy value.

TIP: The query reports depending on the pin direction:

- the read pin status in case the direction is input;

- the previously set pin status in case the direction is output.

In any case, you can know if the pin at the query moment is high or low and the pin direction.

For example: 1- Let's assume you want to query the GPIO3 pin for its status:

command:

GE863-GPS Software User Guide

1vv0300724 Rev. 2 - 24/01/07

AT#GPIO=3,2<cr>

response:

#GPIO: 0,1 OK In this case, the GPIO3 pin was set in input direction and its status has been measured to be HIGH.

2- Let's assume you want to query the GPIO4 pin for its status:

command:

AT#GPIO=4,2<cr>

response:

#GPIO: 1,0 OK In this case, the GPIO4 pin was set in output direction and its status is LOW.

3- Let's assume you want to query the GPIO6 pin for its status:

command:

AT#GPIO=6,2<cr>

response:

#GPIO: 2,0 OK In this case, the GPIO6 pin was set in "alternate function" direction and therefore works as alarm output. The reported status = LOW has no meaning.

3.6.2.2 Setting GPIO pin output status

To set the pin status (when pin is set as OUTPUT):

• Send command AT#GPIO=<pin>,<value>,1<cr>

where: <pin> is the GPIO pin number at which the command applies:

<value> is the pin value to be set and can be:

0 – LOW 1 – HIGH

• wait for response

GE863-GPS Software User Guide

1vv0300724 Rev. 2 - 24/01/07

For example: 1- Let's assume you want to set the GPIO3 pin HIGH:

command:

AT#GPIO=3,1,1<cr>

response:

OK In this case, the GPIO3 pin was set in output direction and its status has been set to HIGH.

3.6.2.3 Using GPIO5 pin as RFTXMON OUTPUT (alternate function)

When you set the GPIO5 pin as RFTXMON output function, the pin reports the Transmitter active status. To set the pin in alternate function you must specify also a dummy value for the pin state:

• Send command

AT#GPIO=5,<dummy_value>,2<cr>

where: <value> is a dummy value can be either:

0 – dummy value 1 – dummy value

• wait for response

TIP: Remember that the alternate function places the GPIO5 pin always in OUTPUT direction.

NOTE: The #GPIO5 direction setting is saved and will be kept after a power off. The saving can be applied only for the alternate mode.

For example: 1- Let's assume you want to set GPIO5 pin as RFTXMON OUTPUT:

command:

AT#GPIO=5,0,2<cr>

response:

OK In this case, the GPIO5 pin was successfully put in RFTXMON output direction.

3.6.2.4 Using GPIO6 pin as ALARM OUTPUT (alternate function)

When you set the GPIO6 pin as alarm output function, the pin reports the alarm state following the +CALA settings. To set the pin in alternate function you must specify also a dummy value for the pin state:

• Send command

AT#GPIO=6,<dummy_value>,2<cr>

where:

GE863-GPS Software User Guide

1vv0300724 Rev. 2 - 24/01/07

<value> is a dummy value can be either:

0 – dummy value 1 – dummy value

• wait for response

TIP: Remember that the alternate function places the GPIO6 pin always in OUTPUT direction and since the GPIO6 pin value is controlled by the internal software, the corresponding function (+CALA) must be setup properly.

NOTE: The #GPIO6 direction setting is saved and will be kept after a power off.

For example: 1- Let's assume you want to set GPIO6 pin as ALARM OUTPUT:

command:

AT#GPIO=6,0,2<cr>

response:

OK In this case, the GPIO6 pin was successfully put in alarm output direction.

3.6.2.5 Using GPIO7 pin as BUZZER OUTPUT (alternate function)

When you set the GPIO7 pin as buzzer output function, the pin will output a waveform suitable to drive a Buzzer, provided a simple external mosfet driver is developed and that the #SRP settings are adequate. To set the pin in alternate function you must specify also a dummy value for the pin state:

• Send command

AT#GPIO=7,<dummy_value>,2<cr>

where: <value> is a dummy value can be either:

0 – dummy value 1 – dummy value

• wait for response OK

TIP: Remember that the alternate function places the GPIO7 pin always in OUTPUT direction and since the GPIO7 pin value is controlled by the internal software, the corresponding function (#SRP) must be setup properly.

NOTE: The #GPIO7 direction setting is saved and will be kept after a power off.

For example: 1- Let's assume you want to set GPIO7 pin as BUZZER OUTPUT:

command:

GE863-GPS Software User Guide

1vv0300724 Rev. 2 - 24/01/07

AT#GPIO=7,0,2<cr>

response:

OK In this case, the GPIO7 pin was successfully put in buzzer output direction.

GE863-GPS Software User Guide

1vv0300724 Rev. 2 - 24/01/07

3.7 Clock/Alarm function

The Telit GE863-GPS provides a Real Time Clock and Alarm embedded in the product; it is therefore possible to set-up the proper time, check the actual time, set-up an alarm time at which the alarm will be triggered with various behavior depending on the +CALA setting. The only requirement is that the power input to the Telit GE863-GPS has to be guaranteed without interruptions, the Telit GE863-GPS has no backup battery; therefore it will lose the time setting if its power supply is interrupted.

On Alarm trigger the Telit GE863-GPS can:

• automatically Wake-up fully operative from shutdown as if the ON/OFF

• automatically Wake-up from shutdown in a special status namely "alarm status" where it will not

look for or try to register into any network, as if it would be off, except from the fact that it proceeds with the alarm action and it can receive commands to return completely operative or shutdown immediately.

• If already ON at alarm trigger time, simply proceed with the Alarm action Once Woken-up the Telit GE863-GPS proceeds with the chosen action that can be

• issue an unsolicited code "+ALARM: <user_text>" on the serial port until a 90s timeout expires or a

special Wake-up command is received

• play an Alarm tone until a 90s timeout expires or a special Wake-up command is received

• rise the pin GPIO6 until a 90s timeout expires or a special Wake-up command is received

• any combination of these actions

With these features, the Telit GE863-GPS for example can:

• Wake-up itself and its controlling hardware by using the GPIO6 pin at the desired time, so timely

surveys can be programmed without the need to keep the any hardware on and therefore reducing power consumption to a minimum.

• Activate some special hardware on time trigger event with the GPIO6 pin.

• Alert the controlling application that the alarm time has come with the unsolicited code

"+ALARM:<user_text>"

• Alert the user with the alarm tone played

3.7.1 Clock date/time

Before using the Alarm feature, you must regulate the internal clock.

GE863-GPS Software User Guide

1vv0300724 Rev. 2 - 24/01/07

3.7.1.1 Regulate the Clock

• Send command

AT+CCLK="<time>"<cr>

where: <time> - current time as quoted string in the format : "yy/MM/dd,hh:mm:ss±zz"

yy - year (two last digits are mandatory), range is 00..99 MM - month (two last digits are mandatory), range is 01..12 dd - day (two last digits are mandatory), range is 01..31 (if the month MM has less than 31 days, the

clock will be set for the next month) hh - hour (two last digits are mandatory), range is 00..23 mm - minute (two last digits are mandatory), range is 00..59 ss - seconds (two last digits are mandatory), range is 00..59 ±zz - time zone (indicates the difference, expressed in quarter of an hour, between the local time and

GMT; two last digits are mandatory), range is -47..+48

NOTE: If the parameter is omitted the behavior of Set command is the same as Read command.

• wait for response

TIP: Remember that the string time has to be encapsulated in double brackets.

NOTE: The time will start immediately after the time setting command.

For example: 1- Let's assume you want to regulate your clock to 7 November 2002 at 12h 24m 30s for the time zone +01h central Europe:

command:

AT+CCLK="02/11/07,12:24:30+04"<cr>

response:

OK In this case, the time was successfully set.

3.7.1.2 Read the current date/time

• Send command AT+CCLK?<cr>

• wait for response in the format:

+CCLK: <time> OK

NOTE: the three last characters of <time> are not returned by +CCLK? because the ME doesn’t

support time zone information.

GE863-GPS Software User Guide

1vv0300724 Rev. 2 - 24/01/07

For example: 1- Let's assume you want now to read the current time:

command:

AT+CCLK?<cr>

response:

+CCLK="02/11/07,12:26:47"<cr> OK In this case the current date/time is: 7 November 2002 12h 26m 47s

3.7.2 Alarm function

Once the current time has been set, the alarm function can be setup.

3.7.2.1 Regulate the Alarm time & behavior

• Send command AT+CALA="<time>",0,<type>,"<text>"<cr>

where: <time> is the Alarm time string in the same format of the clock setting command:

yy/MM/dd,hh:mm:ss±zz where: yy : two digits year (00-99) MM : two digits month (01-12) dd : two digits day (01-31) hh : two digits hour (00-24) mm : two digits minute (00-60) ss : two digits seconds (00-60) ±zz: signed two digits timezone (-11 - +11)

<type> is the Alarm behavior: 0 - reserved for other equipment use. 1 - the MODULE simply wakes up fully operative as if the ON/OFF button had been pressed. If the

device is already ON at the alarm time, then it does nothing.

2 - the MODULE wakes up in "alarm mode" if at the alarm time it was off, otherwise it remains fully

operative. In both cases the MODULE issues an unsolicited code every 3s:

+ALARM: <text>

where <text> is the +CALA optional parameter previously set.

The device keeps on sending the unsolicited code every 3s until a #WAKE or #SHDN command is received or a 90s timeout occurs. If the device is in "alarm mode" and it does not receive the #WAKE command within 90s then it shuts down. (default)

GE863-GPS Software User Guide

1vv0300724 Rev. 2 - 24/01/07

3 - the MODULE wakes up in "alarm mode" if at the alarm time it was off, otherwise it remains fully

operative. In both cases the MODULE starts playing the alarm tone on the selected path for the ringer (see command #SRP) The device keeps on playing the alarm tone until a #WAKE or #SHDN command is received or a 90s timeout occurs. If the device is in "alarm mode" and it does not receive the #WAKE command within 90s then it shuts down.

4 - the MODULE wakes up in "alarm mode" if at the alarm time it was off, otherwise it remains fully

operative. In both cases the MODULE brings the pin GPIO6 high, provided its <direction> has been set to alarm output, and keeps it in this state until a #WAKE or #SHDN command is received or a 90s timeout occurs. If the device is in "alarm mode" and it does not receive the #WAKE

command within 90s then it shuts down. 5 - the MODULE will make both the actions as for <type>=2 and <type>=3. 6 - the MODULE will make both the actions as for <type>=2 and <type>=4. 7 - the MODULE will make both the actions as for <type>=3 and <type>=4.

<text> - unsolicited alarm code text string. It has meaning only if <type> is equal to 2 or 5 or 6.

• wait for response

TIP: Remember that the string time has to be encapsulated in double brackets, furthermore the Alarm time will not be computed for different timezone, therefore the alarm time will always refer to the same timezone as the clock setting regardless the timezone set in the +CALA command. NOTE: if you use the GPIO6 pin as ALARM OUTPUT, then you MUST set its direction to "alternate function" (see par.

3.6.2.4) otherwise the pin will not respond to the alarm settings.

In case the alarm mode is equal to 1,3,7 then a dummy empty text shall be inserted "".

NOTE: if you use the unsolicited codes +ALARM: <text>, then you must fix the port speed rate (see par. 2.5.1) and store it in the active profile (see command &W), in order to make the Telit GE863-GPS boot with the desired port speed, otherwise at the alarm wakeup, the module will start with the default port speed that may differ from yours.

3.7.2.2 Stop the Alarm activity

When the alarm time expires, the module starts the alarm activity according to the alarm behavior parameter <type> selected. To stop the Alarm activity there are three ways, you can either decide to exit from alarm and shutdown the device or exit from alarm and entering the normal operational status; otherwise you can leave the alarm go on until the 90s timeout is reached.

GE863-GPS Software User Guide

1vv0300724 Rev. 2 - 24/01/07

3.7.2.2.1 Exit from the alarm status and shutdown

• Send command AT#SHDN<cr>

• wait for response

At the OK result code, the device will end alarm activity and shutdown.

3.7.2.2.2 Exit from the alarm status and enter the normal operating mode

• Send command

AT#WAKE=0<cr>

• wait for response

At the OK result code, the device will end alarm activity and enter normal operating mode. If the device was already in normal operating mode (alarm has started when the module was already ON), then with the command only the alarm activity is terminated.

3.7.2.3 Querying the Alarm status

When the device awakes by means of an alarm time expire, the module starts the alarm activity but not the network activity, permitting some operations to be done by the controlling application without registering the mobile in the network. To check if the mobile is in the "alarm status" and therefore no network activity is done or if the device is in the normal operating status:

• Send command

AT#WAKE?<cr>

• wait for response in the format:

+WAKE: <status> OK

where: <status> is the operating mode:

0 - normal operating mode 1 - alarm mode

NOTE: if the device is in the alarm mode no network activity is done, therefore the only commands that are accepted are the #WAKE and #SHDN ones. When in the alarm mode, no operation is allowed towards the network, therefore it is not possible to receive or send calls, SMS and whatever GSM/GPRS services.

GE863-GPS Software User Guide

1vv0300724 Rev. 2 - 24/01/07

3.7.2.3.1 Alarm operation example

For example: 1- Let's assume you have a battery powered device, a meteorological unit that measures every hour the conditions and therefore needs to send a new SMS every hour to the central server, for example indicating the whether status just measured. Let say your application shall consume the absolute minimum power to achieve the job, since it will be placed in a remote position where its battery shall last as long as possible and therefore it should shutdown completely and wake up every hour for just the time needed to measure & send the whether, successively shutdown.

- set up the time in the internal clock (only the first time..)

command:

AT+CCLK="02/11/07,12:24:30+01"<cr>

response:

- set up the next alarm in order to raise the GPIO6 pin to power up the controlling application too.

command:

AT+CALA="02/11/07,13:24:30+01",0,6,"TIME TO MEASURE & SMS…!"<cr>

response:

- shutdown the GE863-GPS and successively the controlling application.

command:

AT#SHDN<cr>

response:

OK … after an hour..

The GE863-GPS will turn itself ON in "Alarm Mode" and contemporarily both rise the GPIO6 pin which turns on the power to the controlling application and issue every 3s an unsolicited code +ALARM: TIME TO MEASURE & SMS…!

- turn on the keep alive line in the controlling application that keeps itself ON.

- stop the alarm activity in the GE863-GPS (recognized by the +ALARM unsolicited code) and bring the GE863-GPS in operating mode

command:

AT#WAKE=0<cr>

response:

- take the whether measure

- send the SMS with the whether data (see

Sending a new SMS without storing it par. 3.5.5).

- read the current time.

command:

AT+CCLK?<cr>

GE863-GPS Software User Guide

1vv0300724 Rev. 2 - 24/01/07

response:

+CCLK="02/11/07,13:24:47"<cr> OK

- calculate & set up the next alarm in order to raise the GPIO6 pin to power up the controlling application too.

command:

AT+CALA="02/11/07,14:24:47+01",0,6,"TIME TO MEASURE & SMS…!"<cr>

response:

- shutdown the GE863-GPS and successively the controlling application.

command:

AT#SHDN<cr>

response:

GE863-GPS Software User Guide

1vv0300724 Rev. 2 - 24/01/07

4 GPRS operations

4.1 Introduction

The General Packet Radio Services (GPRS) standard permits DATA transfers in a completely different way with respect to previous point to point communications made with Circuit Switch Data (CSD) GSM modems. In CSD operations the modem establishes a connection with the other party (another modem) in such a way that all the Network devices in between are transparent to the data exchanged, simulating a real point to point connection, just as if the other party is directly connected with the controlling application of the modem. The other party can be either an Internet Service Provider (ISP) or a private server, but in any case, the arrival point must have a modem to connect to (Landline, ISDN or GSM CSD). The connection establishment procedure defines a particular path where all the information exchanged between the two peers flows and this path is reserved for exclusive use of these 2 peers for all the time the connection is active. This approach has the drawbacks of a long time to set-up the link between the two peers (up to a minute) and a time counting bill which proceeds even if no data is exchanged because the path resources are reserved anyway; furthermore the speed of the data transfer is limited to 14400 bps. An example of this kind of operation is shown in the following picture, where the point to point connection is between the two peers as if all the devices inside the dashed line are not present:

GE863-GPS Software User Guide

1vv0300724 Rev. 2 - 24/01/07

CSD interconnectivity

In GPRS operations instead, the connection is made directly towards internet as if the GPRS modem was a network IP socket interface. There's no data path reserved for the data exchange between the two peers, instead the resources are allocated dynamically on demand and the data exchanged is organized into packets typically TCP/IP, furthermore the maximum transfer speed can be much faster than GSM CSD. An example of GPRS connection is shown in the following picture, where the GPRS connection is between the GPRS modem and the internet as if all the devices inside the dashed line are not present:

GPRS interconnectivity

GE863-GPS Software User Guide

1vv0300724 Rev. 2 - 24/01/07

Due to this kind of connection, when activating the GPRS connection you must provide the network parameters to enter through the internet point of the GPRS network ISP (Internet Service Provider) and not the phone number to be dialed; therefore it is not possible to establish a direct point to point GPRS connection between two modems as in CSD case, instead an internet tunneling must be done to achieve a point to point connection between two peers. This approach as the immediate advantage of projecting the controlling application of the GPRS modem directly on the internet, ready to be accessed virtually from anywhere in the world at the same cost on the GPRS; actually the billing of the GPRS connection is based on the amount of data exchanged (number of packets transferred) independently from the time the connection is active or where these packet must be delivered. Therefore, it is possible to leave the controlling application always connected and ready to receive/send data on demand, while paying only for the data really exchanged. The drawback of the GPRS connection is that the controlling application must have its own TCP/IP protocol stack embedded to decode the packets that arrive from GPRS and encode the ones to be sent through the internet. There are few considerations than must be done on the GPRS connections:

• the GPRS connection speed with a GPRS class 10 multislot device is asymmetrical, 3 time slots in reception (43200 bps max) and 2 time slot in sending (28800 bps max) or 4 time slots in reception (57600 bps max) and 1 time slot in sending (14400 bps max).

• The controlling application of the module must have a TCP/IP - PPP software stack to interface with the GPRS modems.

• The controlling application must relay on some ISP that may be the Network Operator of the SIM to gain access to the internet through the GPRS connection.

• Because of the point before, the receiving application must have internet access either.

• Since the communication is based upon TCP/IP packets, then it is possible to talk

contemporarily with more than one peer.

• When required, the data security in internet shall be guaranteed by security protocols over the TCP/IP that must be managed by the controlling application.

NOTE: For more detailed information about GPRS connections and practical examples please refer to the Easy GPRS User Guide

GE863-GPS Software User Guide

1vv0300724 Rev. 2 - 24/01/07

5 GPS operations

5.1 Introduction

The GE863-GPS module is equipped with a SiRFStar III GPS receiver that is controllable by the GSM modem using a setof AT commands or dedicated NMEA sentences.

5.2 GE863-GPS Serial Ports

4 serial ports are available on the module:

•

MODEM SERIAL PORT MODEM SERIAL PORT 2 (GPS CONTROL PORT) GPS SERIAL PORT A (SIRF BINARY) GPS SERIAL PORT B (NMEA)

5.2.1 GPS SERIAL PORT A (SIRF BINARY)

This port is carrying out the GPS navigation data in SIRF BINARY format. The default configuration is 57600 bps, 8, n, 1 It is available on the following pins:

PIN # NAME DESCRIPTION TYPE

78 RX_GPS_BIN GPS RX Data (Sirf Binary) CMOS 2.8V 80 TX_GPS_BIN GPS T X Data (Sirf Binary) CMOS 2.8V

The typical integration requires connecting this pins to MODEM serial port 2.

5.2.2 GPS SERIAL PORT B (NMEA)

This port is carrying out the GPS navigation data in NMEA 0183 format. The default configuration is 4800 bps, 8, n, 1 It is available on the following pins:

PIN # NAME DESCRIPTION TYPE

68 TX_GPS GPS TX Data (NMEA) CMOS 2.8V 73 RX_GPS GPS RX Data (NMEA) CMOS 2.8V

GE863-GPS Software User Guide

1vv0300724 Rev. 2 - 24/01/07

The typical application that permits also to control the GPS part by the GSM modem is the following:

PIN # NAME NAME PIN#

TX_TRACE RX_GPS_BIN

RX_TRACE TX_GPS_BIN

This configuration is also settable on the EVK board. This configuration is defined as “Controlled Mode".

5.3 WGS 84

GPS receivers perform initial position and velocity calculations using an earth-centered earth-fixed (ECEF) coordinate system. Results may be converted to an earth model (geoid) defined by the selected datum. For GE863-GPS the default datum is WGS 84 (World Geodetic System 1984) which provides a worldwide common grid system that may be translated into local coordinate systems or map datums. (Local map datums are a best fit to the local shape of the earth and not valid worldwide).

GE863-GPS Software User Guide

1vv0300724 Rev. 2 - 24/01/07

5.4 NMEA 0183

The NMEA 0183 is a specification created by the National Marine Electronics Association (NMEA) that defines the interface between other marine electronic equipment. The standard permits marine electronics to send information to computers and to other marine equipment. GPS receiver communication is defined within this specification. The actually supported version is 2.2

The provided NMEA sentences are :

GGA

Time, position and fix type data.

GLL

Latitude, longitude, UTC time of position fix and status.

GSA

GPS receiver operating mode, satellites used in the position solution, and DOP values.

GSV

The number of GPS satellites in view satellite ID numbers, elevation, azimuth, and SNR values.

VTG

Course and speed information relative to the ground.

RMC

Time, date, position, course and speed data.

GE863-GPS Software User Guide

1vv0300724 Rev. 2 - 24/01/07

5.4.1 GGA - Global Positioning System Fixed Data

This sentence provides Time, position, and fix related data for a GPS Receiver Table A contains the values for the following example:

$GPGGA,161229.487,3723.2475,N,12158.3416,W,1,07,1.0,9.0,M, , , ,0000*18

Table A

Name Example Units Description Message ID $GPGGA GGA protocol header UTC Time 161229.487 hhmmss.sss Latitude 3723.2475 ddmm.mmmm N/S Indicator N N=north or S=south Longitude 12158.3416 dddmm.mmmm E/W Indicator W E=east or W=west Position Fix Indicator

1 See Table B

Satellites Used

07 Range 0 to 12

HDOP 1.0 Horizontal Dilution of Precision MSL Altitude 9.0 meters Units M meters Geoid Separation

meters

Units M meters Age of Diff. Corr.

second Null fields when DGPS is not used

Diff. Ref. Station ID

0000

Checksum *18 <CR> <LF> End of message termination

Table B

Value Description

0 Fix not available or invalid 1 GPS SPS Mode, fix valid 2 Differential GPS, SPS Mode, fix valid

3-5 Not supported

6 Dead Reckoning Mode, fix valid

GE863-GPS Software User Guide

1vv0300724 Rev. 2 - 24/01/07

5.4.2 GLL - Geographic Position - Latitude/Longitude

This sentence provides latitude and longitude of vessel position, time of position fix and status

Table C contains the values for the following example: $GPGLL,3723.2475,N,12158.3416,W,161229.487,A,A*41

Table C

Name Example Units Description Message ID $GPGLL GLL protocol header Latitude 3723.2475 ddmm.mmmm N/S Indicator N N=north or S=south Longitude 12158.3416 dddmm.mmmm E/W Indicator W E=east or W=west UTC Time 161229.487 hhmmss.sss Status A A=data valid or V=data not valid

Mode A

A=Autonomous, D=DGPS, E=DR (Only present in NMEA version 3.00)

Checksum *41 <CR> <LF> End of message termination

GE863-GPS Software User Guide

1vv0300724 Rev. 2 - 24/01/07

5.4.3 GSA - GNSS DOP and Active Satellites

This sentence reports the GPS receiver’s operating mode, satellites used in the navigation solution reported by the GGA sentence and DOP values.

Table D contains the values for the following example: $GPGSA,A,3,07,02,26,27,09,04,15, , , , , ,1.8,1.0,1.5*33

Table D: GSA Data Format

Name Example Units Description

Message ID $GPGSA GSA protocol header Mode 1 A See Table E Mode 2 3 See Table F Satellite Used1. Satellite used in solution.1

07 Sv on Channel 1

Satellite Used1

02 Sv on Channel 2

....

Satellite Used1 PDOP 1.8 HDOP 1.0 VDOP 1.5 Checksum *33 <CR> <LF> End of message termination

Table E: Mode 1

Value Description

M Manual—forced to operate in 2D or 3D

mode

A 2D Automatic—allowed to automatically

switch 2D/3D

Table F: Mode 2

Value Description

1 Fix not available 2 2D (<4 SVs used) 3 3D (>3 SVs used)

GE863-GPS Software User Guide

1vv0300724 Rev. 2 - 24/01/07

5.4.4 GSV - GNSS Satellites in View

This sentence reports the number of satellites (SV) in view, satellite ID numbers, elevation, azimuth and SNR value. There could be four satellites information per transmission so, if the number of satellites in view is bigger, separated GSV sentences will be generated. The number of sentence in transmission and the total to be transmitted is shown in the first 2 fields of the sentence.

Table G contains the values for the following example:

$GPGSV,2,1,07,07,79,048,42,02,51,062,43,26,36,256,42,27,27,138,42*71 $GPGSV,2,2,07,09,23,313,42,04,19,159,41,15,12,041,42*41

Table G: GSV Data Format

Name Example Units Description

Message ID $GPGSV GSV protocol header Number of Messages

2 Range 1 to 3

Message Number1

1 Range 1 to 3

Satellites in View

Satellite ID 07 Channel 1 (Range 1 to 32) Elevation 79 degrees Azimuth 048 degrees SNR (C/No) 42 dBHz

.... .... ....

Satellite ID 27 Channel 4 (Range 1 to 32) Elevation 27 degrees Channel 4 (Maximum 90) Azimuth 138 degrees Channel 4 (True, Range 0 to 359) SNR (C/No) 42 dBHz Range 0 to 99, null when not tracking Checksum *71 <CR> <LF> End of message termination

GE863-GPS Software User Guide

1vv0300724 Rev. 2 - 24/01/07

5.4.5 RMC - Recommended Minimum Specific GNSS Data

This sentence reports Time , date, position, course and speed data. Table H contains the values for the following example:

$GPRMC,161229.487,A,3723.2475,N,12158.3416,W,0.13,309.62,120598, ,*10

Table H: RMC Data Format

Name Example Units Description

Message ID $GPRMC RMC protocol header UTC Time 161229.487 hhmmss.sss Status A A=data valid or V=data not valid Latitude 3723.2475 ddmm.mmmm N/S Indicator N N=north or S=south Longitude 12158.3416 dddmm.mmmm E/W Indicator W E=east or W=west Speed Over Ground

0.13 knots

Course Over Ground

309.62 degrees True

Date 120598 ddmmyy Magnetic Variation

degrees E=east or W=west

Mode A A=Autonomous, D=DGPS, E=DR Checksum *10 <CR> <LF> End of message termination

NOTE: SiRF Technology Inc. does not support magnetic declination. All “course over ground” data are geodetic WGS84 directions.

GE863-GPS Software User Guide

1vv0300724 Rev. 2 - 24/01/07

5.4.6 VTG - Course Over Ground and Ground Speed

This sentence reports the actual course and speed relative to the ground. Table I contains the values for the following example:

$GPVTG,309.62,T, ,M,0.13,N,0.2,K,A*23

Table I: VTG Data Format

Name Example Units Description

Message ID $GPVTG VTG protocol header Course 309.62 Measured heading Reference T True Course degrees Measured heading Reference M Magnetic Speed 0.13 knots Measured horizontal speed Units N Knots Speed 0.2 km/hr Measured horizontal speed Units K Kilometers per hour

Mode A

A=Autonomous, D=DGPS, E=DR

Checksum *23 <CR> <LF> End of message termination

NOTE: SiRF Technology Inc. does not support magnetic declination. All “course over ground” data are geodetic WGS84 directions.

GE863-GPS Software User Guide

1vv0300724 Rev. 2 - 24/01/07

5.5 Checking GPS device functionality

After a proper power on the device is ready to receive AT commands on the MODEM serial port. The GPS receiver also will be automatically powered on and it will start the scan of the available GPS signals.

On the NMEA serial port (default 4800 bps, 8, n, 1) there must be presence of the NMEA sentences.

5.5.1 Controlled mode

The GE863-GPS is by factory default set to controlled mode. With the command AT$GPSD=<device type> is possible to set this configuration. Parameter:

0 - none; the serial port is not connected to GPS device 2 - serial port connected to GPS serial port: controlled mode (default)

Telit Wireless Solutions GE863-GPS Software User's Manual

Specifications and Main Features

Frequently Asked Questions

User Manual