| Download: |  |
| Mirror Download [FCC.gov] | |
| Document ID | 233185 |
| Application ID | +YArYGvTMgzwOI7JN+Ui2A== |
| Document Description | User manual |
| Short Term Confidential | No |
| Permanent Confidential | No |
| Supercede | No |
| Document Type | User Manual |
| Display Format | Adobe Acrobat PDF - pdf |
| Filesize | 124.06kB (1550688 bits) |
| Date Submitted | 2002-03-26 00:00:00 |
| Date Available | 2002-07-18 00:00:00 |
| Creation Date | 2002-03-05 09:36:22 |
| Producing Software | Acrobat Distiller 4.0 for Windows |
| Document Lastmod | 2002-03-05 11:04:26 |
| Document Title | Reference.book |
| Document Creator | FrameMaker 6.0 |
GM40x GSM/GPRS Module
Reference Manual
UNDOC00048rF
March 2002
Copyright © 2001, 2002 UbiNetics (Cayman Islands) Limited. All rights reserved.
UbiNetics Limited, Cambridge Technology Centre, Melbourn, Herts SG8 6DP, United Kingdom.
www.ubinetics.com
No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or
by any means, electronic, mechanical, photocopying, recording, or otherwise, without the prior written
permission of UbiNetics Limited.
To the fullest extent permitted by law, UbiNetics Limited assumes no responsibility or liability for errors or
omissions in this publication.
UbiNetics™ is a trademark of UbiNetics (Cayman Islands) Limited. This trademark is registered in
Australia, New Zealand, Singapore, the United Kingdom and the European Community, with registrations
pending in other jurisdictions. The information in this guide is believed to be correct as of the date of
publication. However, our policy is one of continuous development and so the information in this guide is
subject to change without notice, and does not represent a commitment on the part of UbiNetics Limited.
Note on Revision F
This version (Revision F) of the GM40x GSM/GPRS Module Reference Manual documents software version
1.3.1.
ii of v
GM40x GSM/GPRS Module Reference: UNDOC00048rF
Table of Contents
1.0
1.1
1.2
1.3
1.4
2.0
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Summary Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2
Functional Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2
Module Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4
Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4
Hardware Specification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.1 Mechanical Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6
2.1.1
2.1.2
2.1.3
Physical & Environmental Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Mechanical Drawings: GM400/401 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Mechanical Drawing: GM404/405 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.2 Hardware Interface Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9
2.2.1
2.2.2
2.2.3
2.2.4
2.2.5
2.2.6
2.2.7
2.2.8
2.2.9
2.2.10
2.2.11
2.2.12
2.2.13
2.2.14
2.2.15
2.2.16
2.2.17
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Pin out diagram and connector orientation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Interface connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Typical application circuit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Main power supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Backup power supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
SIM Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Audio Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Auxiliary speaker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Digital I/O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Interrupt Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Keyboard Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Asynchronous Serial Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
General Purpose I/O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Synchronous Serial Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
RF Interface Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Termination of unused lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
2.3 Electrical Specification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26
2.3.1
3.0
Standard CMOS logic levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Multiplexer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
3.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27
3.2 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27
3.2.1
Software Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
3.3 Supported Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28
3.4 Implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28
3.4.1
3.4.2
3.4.3
3.4.4
3.4.5
3.4.6
4.0
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Multiplexer Start-up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Multiplexer closedown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Data channel establishment and release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Data transmission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Control channel commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
29
29
30
30
30
31
Host suspend procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
4.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33
4.2 Multiplexer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33
GM40x GSM/GPRS Module Reference: UNDOC00048rF
iii of v
4.3 Module power modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
4.4 Host wake-up events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
4.5 Host suspend operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
4.5.1
4.5.2
4.5.3
4.5.4
5.0
Host suspend procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Module wake-up behaviour . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Host wake-up behaviour . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Timing diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
34
34
35
35
Integration Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37
5.1 RF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
5.1.1
5.1.2
5.1.3
Receiver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Transmitter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Sourcing antennae . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
5.2 EMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
5.2.1
5.2.2
5.3
5.4
5.5
5.6
6.0
7.0
Ground plane connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Power supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Mechanical . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Firmware upgrading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Regulatory Approval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41
Definitions and Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
7.0.1
7.0.2
7.0.3
8.0
Radiation by the application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
RF interference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Syntactical Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
AT Commands: Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47
8.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
8.2 Format of the AT Command String and Result Code . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
8.2.1
8.2.2
8.2.3
8.2.4
8.2.5
8.2.6
8.2.7
8.2.8
8.2.9
8.2.10
8.2.11
9.0
9.1
9.2
9.3
9.4
9.5
9.6
Types of Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Command Line Editing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Command Line Termination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Command Formatting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Command Line Echo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Concatenation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Response Code Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Response Code Suppression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Final Result Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Intermediate Result Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Unsolicited Result Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
47
48
48
48
48
48
48
48
48
49
49
Commands Specified by GSM 07.07 . . . . . . . . . . . . . . . . . . . . . . . 50
General Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Call Control Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Network Service Related Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Mobile Equipment Control and Status Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Mobile Equipment Errors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Commands from TIA IS-101 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
10.0 Commands Specified by GSM 07.05 . . . . . . . . . . . . . . . . . . . . . . . 84
iv of v
GM40x GSM/GPRS Module Reference: UNDOC00048rF
10.1 SMS Parameter Definitions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .84
10.1.1 Message Storage Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
10.1.2 Message Data Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
10.2 General Configuration Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .87
10.3 Message Configuration Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .88
10.4 Message Receiving and Reading Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .90
10.5 Message Sending and Writing Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94
11.0 Commands specified within V.25ter Referenced by GSM 07.07 . 97
11.1 Generic DCE Control Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .97
11.2 Call Control Commands and Responses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .104
12.0 Commands Specified by ITU-T Rec. T.32 . . . . . . . . . . . . . . . . . . 109
12.1 Action commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .109
12.2 DCE responses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .110
12.3 Services commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .121
13.0 Condat-specific commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
13.1 CME and CMS Result Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .145
14.0 Additional AT Commands for GPRS. . . . . . . . . . . . . . . . . . . . . . . 149
14.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .149
14.2 Commands specified by GSM Rec. 07.07. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .149
14.3 UbiNetics General Purpose Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .159
15.0 References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
16.0 Alphabetical List of AT Commands . . . . . . . . . . . . . . . . . . . . . . . 172
GM40x GSM/GPRS Module Reference: UNDOC00048rF
v of v
Introduction
1.0
Introduction
This document specifies the functionality of the UbiNetics GM40x dual-band GSM/GPRS modules:
● GM400 is a 900 E-GSM and 1800 GSM dual-band module
● GM401 is a 900 E-GSM and 1900 GSM dual-band module
● GM404 is a low- profile 900 E-GSM and 1800 GSM dual-band module
● GM405 is a low-profile 900 E-GSM and 1900 GSM dual-band module.
Both modules provide multislot GPRS operation to MS8 specification.
The products provide GSM/GPRS mobile communication capability, suitable for embedding in PDAs and
other devices.
1 of 176
GM40x GSM/GPRS Module Reference: UNDOC00048rF
Introduction
1.1
Summary Specification
1.2
Functional Specification
Parameter
Qualifier
Specification
Class
Dual band
GM400
E-GSM 900 Power Class 4 (2W)
GSM1800 Power Class 1 (1W)
Dual band
GM401
E-GSM 900 Power Class 4 (2W)
GSM1900 Power Class 1 (1W)
Dual band
GM404
E-GSM 900 Power Class 4 (2W)
GSM1800 Power Class 1 (1W)
Dual band
GM405
E-GSM 900 Power Class 4 (2W)
GSM1900 Power Class 1 (1W)
Multislot Class
The product provides multislot operation to
MS 8
Mobile station class
The product provides a Mobile Station of
class B (Non-concurrent dual-mode GSM/
GPRS)
RF bands
E-GSM 900:
Tx: 880 – 915 Rx: 925 – 960 MHz
GSM 1800:
Tx: 1710 – 1785, Rx: 1805 – 1880 MHz
GSM 1900:
Tx: 1850 – 1910, Rx: 1930 – 1990 MHz
Receiver sensitivity
Better than -104 dBm at 900 GSM
Better than -102 dBm at 1800/1900 GSM
Selectivity
Better than 9dB at 200KHz
Better than 41dB at 400KHz
Dynamic range
~89dB typical for 900 GSM
~87dB typical for 1800 GSM
Electrical
performance
Conforms to ETSI 11.10
RF connection
Signal and ground PCB pads for
attachment of appropriate RF
GPRS class
RF
GM40x GSM/GPRS Module Reference: UNDOC00048rF
Notes
Maximum total number of
slots is 5
Maximum number of
receive slots is 4
Maximum number of
transmit slots is 1
2 of 176
Introduction
Approvals
Audio
Safety
Radio
Protocol
EMC
SAR
Network
Environmental
EN60950
3GPP 51.010
3GPP 51.010
EN 301 489
ES59005
GCF PTCRB
ETS 300 019
Europe
Safety
Radio
Protocol
EMC
SAR
Network
Environmental
UL60950 edition 3
FCC part 24
USA
Voice
2 Microphone and 2 ear-piece interfaces
Alert
Sounder output
Echo
Cancellation
FCC part 15
ANSI C95.1
PTCRB
Customer specific
Sufficient for small handset enclosures and
desktop use
GSM Data
Asynchronous
transparent and nontransparent
9.6kbps / 14.4kbps
GPRS Data
Asynchronous
9.05, 13.4, 15.6 and 21.4kbps per slot
GSM Fax
Transparent
9.6kbps and 14.4kbps
SMS
Memory
32m second maximum
delay; attenuation
approximately 40 dB
Full ETSI SMS compliant, including cell
broadcast
RAM
6Mbit
Flash
16Mbit
SIM
The module supports the following SIM
card types:
Plug-in SIM card 3V
Plug-in SIM card 3V/5V
Only SIM cards conforming to ETS 300
607-1 are supported, tested against UK
and other European Network Provider SIM
cards
Temperature
monitoring
On-board over-temperature protection
(+80ºC)1
Power supply
Voltage
3.6V nominal
3.3V minimum
3.2V minimum during
(2A) TX burst
Power
consumption
(average)
Shutdown current
70µA
nominal
Stand-by current
3.2mA
nominal
Talk current
See table on page 13
1.Calls are ended if the internal temperature reaches +80ºC. In worst case conditions, the internal temperature of the
module can be up to 20ºC higher than ambient, so temperature protection may trigger at 60ºC ambient temperature.
3 of 176
GM40x GSM/GPRS Module Reference: UNDOC00048rF
Introduction
1.3
Module Interfaces
Parameter
Qualifier
Display interface
SPI (5 wire)
Keyboard
5 x 5 matrix
5 x inputs (rows)
5 x outputs (columns)
2.9 V logic levels
Serial interface
4 lines (TXD, RXD,
RTS, CTS)
Compatible with UART 16C750
device
2.9 V logic levels.
General Purpose I/O
1.4
Specification
Notes
2.9 V logic levels
3 x GPIO
Software
Parameter
Qualifier
Specification
Protocol stack
Layer 1 / 2 / 3
GSM/GPRS Dual Band Protocol Stack
Layer 2 / 3 Supplementary
Services
Caller line identification
Call forwarding
Call waiting / call hold
Layer 1 Codec Support
Firmware providing support for:
FR, HR, EFR (Dual band)
Subsidy protection
Network personalisation according to GSM 02.22
for:
Network Operator Lock
Service Provider Lock
Lock to First SIM
Device drivers
Drivers for all hardware
devices in the core design
RF
SIM
UART
Audio control
Power Supply control
External interfaces
Serial interface with data rate
of 56Kbps (57600bps)
Serial interface supporting AT commands, with
software multiplexer for use in GPRS Class B mode,
or for multiple AT command streams.
Multiplexer supports a subset of ETSI 07.10
specification
AT command interpreter supports a subset of ETSI
07.05 and 07.07 specifications, including V.25
Application software
Diallers
AT Exerciser
Flash Upgrader
Multiplexer
For PC and other operating systems
For driving the module using AT commands
For upgrading module firmware
GM40x GSM/GPRS Module Reference: UNDOC00048rF
4 of 176
Introduction
4 SIM Tool kit (release 98
. compliant, ETSI standard
4 11.14, Version 7.3.1)
MMI
5 of 176
Functions supported
Call Control
Cell Broadcast Download
Event Download
MO Short Message Control
More Time
Polling Off
Poll Interval
Provide Local Information
Refresh
Send DTMF
Send Short Message
Send SS
Send USSD
Set Up Call
Set Up Event List
SMS-PP Download
Timer Management
Timer Expiration
Run AT Command
MMI functions supported
Support available for small or full MMI: details of API
available upon request
Drivers
Keypad
SPI
GPI/O
GM40x GSM/GPRS Module Reference: UNDOC00048rF
Hardware Specification
2.0
Hardware Specification
2.1
Mechanical Characteristics
2.1.1
Physical & Environmental Characteristics
Parameter
Qualifier
Form
Size & weight
PCB, components on both sides, with screening can on both sides
Dual band
Weight
Temperature
& Humidity
Vibration
Specification
Overall size:
50.6 X 31 X 5.25 mm nominal
15 grams
Storage
-20ºC to +70ºC at 93% relative humidity
-40ºC to +70ºC at 30% relative humidity
Operational
-20ºC to +55ºC at a relative humidity of 93%
(no damage)
Random vibration test compliant with IEC60068-2-64 standard
Marking
Type and model number
Serial number and IMEI number (alphanumeric and bar code)
Ubinetics logo
Hardware
interface
Characteristics
As described in the “Hardware Interface Specification” on page 9.
Shock
Shock test
450cm/s impact (impact time 2 - 2.8ms)
Drop test
1 metre drop test
GM40x GSM/GPRS Module Reference: UNDOC00048rF
6 of 176
Hardware Specification
4.15 ±0.10
0.50
35.20 ±0.15
MOUNTING PIN CENTRES
50.60
±0.25
5:1
MAX
MAX
2.10 MAX
(FENCE)
0.20
(LID THICKNESS)
1.60
0.10
(LID ASSEMBLY TOL.)
2.50
1.60
7.80 ±0.30
0.05 MAX
(SOLDER ALLOWANCE)
2.50
DETAIL
SCALE
6.50 ±0.10
DETAIL
SCALE
5:1
ANTENNA PAD DETAIL
3.00
SEE DETAIL
0.50
1.70
2.00
3.40
3.80
2.75
0.20 MAX
(LID THICKNESS)
5.95
5.55
4.15
2.10 MAX
(FENCE)
THIS PIN MUST BE
CONNECTED TO GROUND
ON HOST PCB
0.10 MAX
(LID ASSEMBLY TOL.)
Mechanical Drawings: GM400/401
0.05 MAX
(SOLDER ALLOWANCE)
2.1.2
NOTES:
1. THIS DRAWING SUPERCSEDES AND REPLACES
DRAWING UNASM00126.
SEE DETAIL
2. MODULE REQUIRES A THERMAL RESISTANCE
WHEN MOUNTED TO THE HOST PCB. SPECIFIC
REQUIREMENTS SHOWN BELOW:
-MS8 26 °C/W
-MS10 19 °C/W
-MS12 12 °C/W
5.55 MAX
MODULE HEIGHT
0.30
5.70
REF
44.90
3. MOUNTING HOLE DETAILS SHOWN ON SHEET 2
31.25 ±0.15
MOUNTING PINS
±0.25
31.00
23.80
7.20 ±0.25
±0.25
2. MODULE PCB DIMENSIONS ±0.25MM.
PLACEMENT TOLERANCES ±0.1MM
±0.25
r 1
r 1
VERSION
08-Oct-01
SJW
DATE
CHANGE
SIG
TTED OR REPRODUCED
UBINETICS LTD
Group
Company
DRAWN
SCALE
2:1
DIMS
DATE
mm
7 of 176
25-Sep-01
TITLE
CHECKED
SJW
N/A
AUTHORISED
FINISH
N/A
DRAWING No.
-D r
GM40x GSM/GPRS Module Reference: UNDOC00048rF
SHT
OF
Hardware Specification
UNCON00200
MATING CONNECTOR
15.48
15.50
±0.35
15.50
±0.35
SEE DETAIL
3.00 REF BOARD TO BOARD HEIGHT
(DEFINED BY CONNECTOR SYSTEM)
7.80
3.10 ±0.35
15.48
6.3 MAX
DETAIL
SCALE
10:1
47.50
±0.35
43.00
2.00
1.00
THIS PIN
TO BE
CONNECTED
TO GROUND
ANTENNA PAD
MOUNTING DETAIL
EXAMPLE
NOTES:
1. MOUNTING HOLE DIMENSIONS INCLUDE AN ALLOWANCE FOR
TOLERANCES ON PLACEMENT OF CONNECTOR,MOUNTING
PINS AND MODULE.
2. CUSTOMER TO MAKE ALLOWANCE FOR DRILL HOLE
PLACEMENT TOLERANCE ON THEIR MOTHERBOARD.
3. TOLERANCE ON PLACEMENT OF MATING CONNECTOR ASSUMED
TO BE ±0.1mm. CUSTOMER TO MAKE ALLOWANCE IF TOLERANCE
IS DIFFERENT.
GM40x GSM/GPRS Module Reference: UNDOC00048rF
8 of 176
Hardware Specification
Mechanical Drawing: GM404/405
SUGGESTED MOUNTING
DETAIL
SCALE
1:1
REF
3.0
5.0 SQR. TYP 4 PLACES
39.8
(50.9 MAX)
SCALE
ANTENNA
CONNECTION
PAD
5.1 MAX
36.8
2:1
REF
REF
50.6
2:1
31.0
34.2
13.4
SCALE
(31.3 MAX)
13.4
13.7
43.4
RELATIVE POSITION OF
OF ANTENNA
REF
2.1.3
1.5 REF
1.5 MM BOARD TO BOARD
CONNECTOR
2.2
Hardware Interface Specification
2.2.1
Introduction
This section describes the hardware interface specification for the dual-band GSM/GPRS Module. A 50way board-to-board connector is used to interface with the host hardware platform. The specification of
this connector is given on “Pin out diagram and connector orientation” on page 10. An antenna pad is
provided for the RF interface.
Note:
● The module must be power grounded by the mounting point shown in “Pin out diagram and connector
orientation” on page 10.
● The circuit diagrams in this section show circuits internal to the module. Exceptions to this are the diagrams in “Backup power supply” on page 17, “Auxiliary microphone” on page 20, “Auxiliary speaker”
on page 21 (3-wire headset) and “Sounder output” on page 22, where components may be required in
the host.
9 of 176
GM40x GSM/GPRS Module Reference: UNDOC00048rF
Hardware Specification
2.2.2
Pin out diagram and connector orientation
RF
Connection
Pads
ATE test
points
TOP VIEW
(RF)
RF Screening
can
Mechanical
mounting point
PIN 50
ATE test
points
BOTTOM
VIEW
(BASEBAND)
Mechanical mounting
and electrical
grounding point
50 way board to
board conector
(see DETAIL 1)
PIN 1
DETAIL 1
10
12
14
16
18
20
22
24
26
28
30
32
34
36
38
40
42
44
46
48
50
PWR
PWR
PWR
PWR
PWR
PWR
GND
PWR_RTC
MIC1P
SPK1P
MIC1N
SPK1N
AUXI
SPK2P
GND
SPK2N
SPI_DATA
AUXV0
SPI_CLK
GPIO3
SPI_CS
SIM_VDD
SPI_D/C
SIM_I/O
SPI_RST
SIM_CLK
GPIO1
SIM_RST
GPIO2
KBC0
ON/OFF
KBC1
RESET
KBC2
HOST_WAKEUP
KBC3
SOUNDER
KBC4
CTS
KBR0
TXD
KBR1
HOST_STATUS
KBR2
INT_OUT
KBR3
RTS
KBR4
VDDS
RXD
11
13
15
17
19
21
23
25
27
29
31
33
35
37
39
41
43
45
47
49
GM40x GSM/GPRS Module Reference: UNDOC00048rF
10 of 176
Hardware Specification
2.2.3
Interface connector
The board-to-board connectors required in the host, to provide the interface with the modules are as
follows:
GM400/401
Type
Pins
Pitch
Type
Manufacturer
Part number
Plug1
50-way
0.5mm
Vertical ‘M’ type
SMK (http://www.smk.co.jp)
CPB7250-6211
1.Although catalogued as a plug, this is a ‘female’ receptacle
This plug is available to special order only, and you should allow a lead time of 12 to 14 weeks for delivery
from the manufacturer.
GM404/405
Type
Pins
Pitch
Type
Manufacturer
Part number
Socket
50-way
0.5mm
Vertical SMT
Hirose
DF23C-50DS-0.5V(51)
This is a comparatively new part, and may not yet be in all Hirose catalogues.
2.2.4
Typical application circuit
This is a circuit for a typical application incorporating the GSM/GPRS module, using the following
interfaces:
● LCD
● Serial port
● Keyboard
● SIM
● GPI/O
● 2 speakers
● 2 microphones
● Main battery
● Backup battery
11 of 176
GM40x GSM/GPRS Module Reference: UNDOC00048rF
Hardware Specification
V_BAT
LEGEND
TYPICAL MODULE APPLICATION
TZ
LS
SG
TZ
LEVEL SHIFTER
MAIN
BATTERY
SPARK GAP
TRANZORB
10
12
MIC (MAIN)
14
MIC (AUX)
16
18
LCD
20
22
24
26
PWR
PWR
PWR
GND
PWR_RTC
MIC1P
SPK1P
MIC1N
SPK1N
MIC2P
SPK2P
GND
SPK2N
SPI_DATA
AUXVO
SPI_CLK
SPI_CS
SPI_D/C
GPIO3
SIM_VDD
SIM_I/O
SIM_CLK
GPIO1
SIM_RST
30 GPIO2
KBC0/GPO0
32
34
36
LS
38
BUF
40
LS
42
44
46
LS
48
SERIAL
PORT
INTERFACE
PWR
PWR
SPI_RST
28
HOST
INTERFACE
PWR
50
ON/~OFF
KBC1/GPO1
~RESET
KBC2/GPO2
HOST-WAKEUP KBC3/GPO3
SOUNDER
KBC4/GPO4
CTS
KBR0/GPI0
TXD
KBR1/GPI1
HOST_STATUS
KBR2/GPI2
INT_OUT
KBR3/GPI3
RTS
KBR4/GPI4
VDDS
RXD
SG
SUPERCAP
SPEAKER (MAIN)
11
13
SPEAKER (AUX)
15
17
V_BAT (monitor)
19
21
100n
23
TZ
25
TZ
27
TZ
29
TZ
31
VPP
VCC
SIM
I/O
GND
CLK
RST
Use low capacitance
tranzorbs on SIM
connections
33
35
37
39
41
43
45
47
49
LS
GM40x GSM/GPRS Module Reference: UNDOC00048rF
12 of 176
Hardware Specification
2.2.5
Main power supply
Note that Default State is the pin state on power up.
Pin out
PIN
Pin Name
Description
DIR
Default
State
Electrical Specification
PWR
Main power supply to
the module. Multiple
pins are used for
heavy current capacity
SUPPLY
N/A
Normal operating range:
3.3V to 4.5V (3.6V nominal)1 Minimum
3.0V (typical)2
Absolute maximum rating:
Input Voltage: 5.1 V
Peak current: 2.0A3
See the table below for current
consumption under various power
modes
PWR GND
Power Ground
Uses screening can
fixing point
16
GND
N/A
Heavy ground current is returned
through screening can: one leg only
1.Over full operating temperature range. Note that the input voltage must exceed 3.2V for power-on (undervoltage lockout)
2.Typical figure, in-call at full power at 25ºC ambient: not guaranteed
3.Antenna VSWR <4:1
Bead
PWR
BLM21P300S
100n
33p
1n
33p
4u7
RF PA
4u7
RF GND connection via screening can
Power input circuit
Average Power Consumption
All power consumption specifications are given at the nominal voltage of 3.6V and 25ºC.
State
Description
Activity
Shutdown
Power on VBAT_IN, and
PWR_RTC.
Module not powered up
Only power up circuits (UPR)
and Real Time Clock (RTC)
active
70µA
Stand-by
Power on VBAT_IN, and
PWR_RTC.
Module powered up
Registered on GSM, GPRS
attached
Baseband active
13MHz (5%) / 32KHz (95%)
clock
RF Receive intermittent (5%)
Occasional Tx (LU)
3.2mA
13 of 176
Conditions
Power cons.
GM40x GSM/GPRS Module Reference: UNDOC00048rF
Hardware Specification
GSM in call:
EGSM mode
GSM in call:
DCS mode
GPRS Active
Power on VBAT_IN, and
PWR_RTC.
Module powered up
1 TX slot, 1 RX slot
Power on VBAT_IN, and
PWR_RTC.
Module powered up
1 TX slot, 1 RX slot
Power on VBAT_IN, and
PWR_RTC.
Module powered up
1 TX slot, up to 4 RX slots
Baseband active
13MHz clock
RF active
Average
@Pcl5
Average
@Pcl8
Baseband active
13MHz clock
RF active
300mA
220mA
During RX
bursts
55mA
During TX
bursts @Pcl5
1.8A
Average
225mA
@Pcl03
Average
155mA
@Pcl34
Baseband active
13MHz clock
RF Rx/Tx active
During RX
bursts
55mA
During TX
bursts @ Pcl0
1.4A
<500mA
1.2W
2.0.5W
3.1W
4.0.25W
Power mode specification (average values)
Power supply considerations
The input voltage is expected to be a Lithium-ion cell, or a Ni-MH battery. The cell impedance should be
low enough for the output voltage to remain above 3.3V under a GSM/GPRS load.
GM40x GSM/GPRS Module Reference: UNDOC00048rF
14 of 176
Hardware Specification
talk time usage of Li-ion battery capacity, with respect to cell internal resistance
40.0%
250mR
35.0%
battery capacity remaining when call dropped
225mR
30.0%
200mR
25.0%
175mR
150mR
20.0%
15.0%
10.0%
5.0%
0.0%
2.90
2.95
3.00
3.05
3.10
3.15
3.20
3.25
3.30
minimum operating voltage of module in full power call
The relationship between cell ESR, usable battery capacity and minimum operating voltage
Power Sequencing
When the power is first applied, the module is held in reset until the input voltage rises above the
undervoltage lockout threshold of 3.2V.
At this point, the module enters Power-on state (as opposed to Switch-on state): only the UPR
(uninterrupted power) internal rail is powered. Current consumption is less than 150µA.
The On/Off pin is monitored by a small hardware state machine, which will commence the switch-on
sequence when a falling edge is detected on the power On/Off pin. If the power On/Off pin is not held low
for at least 50ms, the switch-on sequence is aborted.
If the On/Off pin is driven low for more than 50ms, the module enters Switch-on state, the main processor
resets, boots up and runs. After network registration, the current consumption will fall to 3.2mA, averaged
over 60 seconds. The RTC (real-time clock) will be reset only the first time this state is entered. Toggling
between Switch-on and Switch-off states will not clear the RTC.
If the On/Off pin is driven low for more than 50ms again, the module enters Switch-off state, with only the
RTC and alarm timer running. Current consumption in this mode is less than 150µA. Wake-up interrupts
may be programmed using the RTC if required.
If at any time, the main input voltage falls below 2.8V (nominal), and the main input voltage is below the
backup battery voltage, then the module enters backup mode. This is identical to switch-off state except
that any attempt to switch on will be blocked. The module will exit backup mode if either of the two defining
conditions (above) are lifted.
Power ON/OFF line
PIN
Pin Name
Description
DIR
Electrical Specification
32
ON/OFF
External PSU Enable
IN
VIH = Vbatt ±200mV
VIL = 0V ±300mV
15 of 176
GM40x GSM/GPRS Module Reference: UNDOC00048rF
Hardware Specification
Vbatt
10k
ON/OFF
On/Off Input Circuit
The power On/Off pin should be used to power up the module. This is achieved by pulling the line low for
more than 50ms (typically 60ms), then high again.
To power down the module, pull the line low for >600ms (typically 700ms). In order to avoid confusion, it is
recommended that the module be switched off using the AT+POWER_DOWN command. The VDDS line
may be used to monitor the power state of the module: it is high if the module is powered up, and low
otherwise.
RESET line
PIN
Pin Name
Description
DIR
Reset active
Reset not active
34
RESET
External reset pin
IN
Vin >1.5V
Vin <0.5V
2.8V
100k
RESET
PWRONRST
10k
47k
When the hardware RESET line is asserted the digital baseband chip is immediately reset, including the
background functions such as Real Time Clock.
Deasserting RESET causes low-level initialisation of this chip to occur. If the module was in the Switch-ON
state (see “Power Sequencing” on page 15) prior to the reset it will return to the Switch-ON state (but not in
call). If it was previously in the Switch-OFF state it will remain so.
Note however that the immediate nature of hardware RESET may potentially confuse the network if there is
an active GPRS PDP context at that time (because this is only cleared when deactivated or with a GPRS
detach). Also, data corruption could occur if it is asserted while writing to the SIM card or to the memory
chip. Hence, hardware RESET should only be used if absolutely necessary—the "AT+POWER_DOWN"
command (see “+POWER_DOWN Power Down Module” on page 168) or the ON/OFF line should be used
to power off if at all possible.
If the motherboard PCB is not shielded from the Antenna RF radiation, it is advisable to add a 33pF
decoupler to the Reset and ON/OFF lines as close as possible to the module connector.
GM40x GSM/GPRS Module Reference: UNDOC00048rF
16 of 176
Hardware Specification
VDDS rail
Electrical
specification
PIN
Pin Name
Description
DIR
50
VDDS
Power supply for external level shifter
OUT
2.9V nominal
2.7V minimum
3.1V maximum
<3R
Vext
<10mA to be drawn
2V8
100k
100k
100n
Note
Vext-en
This rail is intended to power external level-shifters, if these are required. It also gives a reliable indication
of whether the module is powered up or not. The output is high only if the module is in the "Switch-on"
state, as defined above.
2.2.6
Backup power supply
PIN
Pin Name
Description
DIR
Electrical
Specification
PWR_RTC
Back up power for RTC
SUPPLY
3.0V - 5.5V
charge
Vbackup
0.047F
supercapacitor
e.g. Tokin FC0H473ZTBR24
Note
3.2V
1k
The module has provision for a backup supply, to power the RTC (real-time clock) when the module is
powered down. This is principally intended to be a double layer supercapacitor. Power is drawn from the
backup battery when the main supply voltage is both below 2.8V (nominal) and below the backup voltage.
There is a simple charging facility within the module, whereby a 3.2V (nominal) regulator may be
connected to Vbackup by setting a control register bit. Charging current is kept low, and the capacitor will
be fully charged within a few minutes. Hold-up time with the part shown is at least ten minutes.
Additional specifications for Vbackup:
Min
Typical
Max
Notes
Charge voltage
3.0V
3.2V
3.6V
Icharge = 10µA
Charge current (µA)
250
500
800
Vbackup = 2.8V
Voltage at which module enters
backup mode
2.6
2.8
2.9
Backup current consumption
(µA)
50
150
Minimum back-up voltage
2.3
17 of 176
GM40x GSM/GPRS Module Reference: UNDOC00048rF
Hardware Specification
1.Main supply must also be below backup supply before switchover will occur
2.This figure may be revised; it cannot exceed 150µA. Backup mode = 1 (lowest power mode)
3.This figure is not explicitly specified, so may be revised. Backup mode = 1 (lowest power mode)
2.2.7
SIM Interface
The SIM interface conforms to ISO 7816-3 Class B (3V SIM interface).
PIN
Pin Name
Description
DIR
Default
State
Min
Max
@ IO
21
SIM_VDD
SIM power
supply
OUT
2.7
3.3
6mA
PIN
Pin Name
Description
DIR
Default
State
VOH min.
VOL max
@ IO
23
SIM_I/O
SIM Data
I/O
See
0.4V
1mA
footnote1
25
SIM_CLK
SIM Clock
OUT
0.7 SVDD
0.2 SVDD
20µA
27
SIM_RST
SIM Reset
OUT
0.8 SVDD
0.2 SVDD
200µA
1.Output high voltage VOH is determined by 6k8 pull-up and leakage, ≅SVDD
On host PCB
10
SIM_VDD
100n
reqd
SIM contacts
VPP
VDD
I/O
RST
CLK
GND
3V
6k8
400
SIM_I/O
SIM_RST
2700
50
SIM_CLK
33p
main processor
33p
all reqd
The SIM Interface circuit
Capacitance on SIM interface lines
The SIM interface specification demands fast rise times for the clock, data and reset signals. This
precludes the use of ordinary-type varistors for ESD protection, as the typical capacitance of these parts
is 90-200pF. Several low-capacitance ESD protection devices are available from different manufacturers,
and these should be used.
SIMCLK
SIMRST
SIM_I/O
Unit
Measured module capacitance
15.4
45
7.7
pF
Typical driver output impedance
52
2634
6800
Ω
GM40x GSM/GPRS Module Reference: UNDOC00048rF
18 of 176
Hardware Specification
Required risetime
50
1000
1000
ns
Margin by which specs are to be met
20%
20%
20%
Allowable gross capacitance
350
138
53
pF
Allowable SIM line capacitances (typical)
2.2.8
Audio Interface
Main microphone
DIR
DC
condition1
Digital clipping
level
Input impedance
Microphone 1 Positive3
IN
2.0V
32.5mV RMS
1.2kΩ
Microphone 1 Negative4
IN
0.5V
32.5mV RMS
1.2kΩ
PIN
Pin Name
Description
AGND
Microphone 1 Ground 2
10
MIC1P
12
MIC1N
1.DC conditions assume an electret microphone capsule with a DC resistance of ~4kΩ when biased at 1.5V across the
terminals, and a micbias supply of 2.5V. There is DC on these pins.
2.Cable screening, if used, should be grounded at this point.
3.Clipping level is shown with programmable gain trim amplifier set to 0dB. Available range is -12dB to +12dB in 1dB steps
4.Differential input impedance is 1.2kΩ.
2.5V
1k
47p
1k2
33p
MIC1P
33p
2.0V
MICBIAS supply
2u2
1k
100n
1k
100n
MIC AMP
MIC1N
33p
1k2
10n
10n
CODEC chip
Main microphone input circuit
19 of 176
GM40x GSM/GPRS Module Reference: UNDOC00048rF
Hardware Specification
Main speaker
PIN
Pin Name
Description
DIR
DC
condition
Clipping level
Output
impedance
Notes
SPK1P
Earphone 1
Positive
OUT
1.25V
2Vpp
5Ω typical
123
11
SPK1N
Earphone 1
Negative
OUT
1.25V
2Vpp
5Ω typical
9&
11
SPK1N/P
As Bridge-tied
load
OUT
0V
4Vpp
10Ω typical
1.Differential Maximum capacitive load at EARP-EARN = 100pF max
2.Common Mode Minimum resistive load at EARP or EARN = 200kΩ typical
3.Clipping level is equivalent to two rail-to-rail outputs each driven 3.6Vpp, in antiphase
3.6V
4R7
EARP
0.3
32
CODEC chip
4R7
0.3
33p
EARN
33p
Main speaker driver circuit
Auxiliary microphone
PIN
Pin Name
Description
DIR
DC
condition
Digital clipping
level
Input
impedance
Notes
14
AUXI
Auxiliary Microphone
IN
N/A
365mV RMS
220kΩ
123
24mV RMS
220kΩ
4 23
16
AGND
For use with AUXI
input
1.AUXI programmable gain amplifier set to minimum (4.6dB gain)
2.Clipping level is shown with programmable gain trim amplifier set to 0dB, available range is -12dB to +12dB in 1dB step
3.Input impedance is normally defined by the external bias resistor, typically 2kΩ.
4.AUXI programmable gain amplifier set to maximum (28.2dB gain)
The auxiliary microphone input is primarily intended for an external headset. Great care must be taken to
ensure that the unbalanced signal input is not corrupted with TDMA noise. The grounding of the external
bias generator must be as shown below. The bias voltage and resistance will vary according to the
microphone capsule specification: indicative values are shown.
GM40x GSM/GPRS Module Reference: UNDOC00048rF
20 of 176
Hardware Specification
Note that ESD protection will be required if these lines are accessible to the user.
+ 2V
mic bias
2k
MODULE
codec
100n
AUXin
MIC
33p
AGND
Auxiliary microphone input showing external biasing requirement
2.2.9
Auxiliary speaker
PIN
Pin Name
Description
DIR
DC
condition
Clipping level
Output
impedance
Notes
13
SPK2P
AUXOP
Auxiliary Earphone
positive
OUT
1.25V
1Vpp
50Ω typical
1234
SPK2N
AUXON
Auxiliary Earphone
negative
OUT
1.25V
1Vpp
50Ω typical
Wired as bridge-tied load
OUT
0V
2Vpp
10Ω typical
15
1.Clipping level is equivalent to two rail-to-rail outputs each driven 1Vpp, in antiphase
2.Differential Maximum capacitive load at SPK2P - SPK2N = 100pF maximum
3.Common Mode Minimum resistive load at SPK2P or SPK2N = 200kΩ typical
4.Minimum output resistive load at AUXO-AUXON = 1.2k Ω typical, 1.0kΩ minimum, i.e. auxiliary speaker must be greater
than 1k Ω impedance - to be confirmed
5.Maximum output swing at AUXOP-AUXON: 5% distortion maximum. Load = 1kΩ = 1.96Vpp typical, 1.6Vpp minimum
CODEC chip
3.6V
4R7
SPK2P
0.3
1k
4R7
0.3
33p
SPK2N
33p
Auxiliary output circuit - bridge-tied load
21 of 176
GM40x GSM/GPRS Module Reference: UNDOC00048rF
Hardware Specification
CODEC chip
3.6V
22uF
4R7
SPK2P
0.3
1k
4R7
0.3
33p
32
SPK2N
33p
AGND
AUX output using 3-wire headset
Note the inclusion of a 1kΩ resistor to avoid loud "pops" in the earphone when the headset is plugged in.
The value of the 22µF capacitor is chosen to pass 300Hz, and may be Tantalum or ceramic type.
The codec is designed for both differential and single ended use; however we recommend differential,
rather than single-ended mode, to keep TDMA noise to a minimum. It can be difficult to screen out the
TDMA noise using the analogue ground as the return.
Sounder output
PIN
Pin Name
Description
DIR
Output
level
Min
38
SOUNDER
To drive buzzer
OUT
VOH
0.8*VDDS
VOL
Max
@ IO
2mA
0.22*VDDS
Vbatt
100n
22
470
SOUNDER
47k
Sounder implementation circuit
The sounder output generates a modulated frequency, programmable between 349Hz and 5276Hz with
12 semitones per octave. The output amplitude is also programmable.
Analogue input
PIN
Pin Name
Description
DIR
Internal name
17
AUXV0
Analog Input1 2
IN
VBAT_MEAS
1.The ADC will output all “1”s for an input voltage of 7V nominal.
2.The input pin is not designed to take more than 5.5V.
GM40x GSM/GPRS Module Reference: UNDOC00048rF
22 of 176
Hardware Specification
This input is intended to be used for battery voltage measurement, which in the case of Lithium-ion
batteries, can form a reasonably accurate remaining capacity estimate. Each discrete step in the A/D
reading represents approximately 1.5% of the capacity of a typical Lithium-ion battery.
Parameter
Condition
Min
Nom
AUXV0 input
voltage range
Max
Unit
5.5
24.5
µs
Sampling Rate
2.17
Samples/s
Resolution
10
Bit
Sample acquisition time
16.5µs delay
8µs acquisition
Battery Voltage
Measurement Step size
Tolerance indicates
ADC Linearity, and is
not cumulative
-5%
Reference Voltage
Tolerance
Temperature drift is
50ppm/°C
-0.5%
6.8
+5%
mV
+0.5%
AUXV0 input impedance
10
MΩ
AUXV0 to ADC input
attenuation
0.25
V/V
Integral non linearity
Best fitting
Differential non linearity
-1
+1
LSB
-1
+1
LSB
Battery measurement ADC Electrical Specification
2.2.10
Digital I/O
Host Status
PIN
Pin Name
Description
DIR
Notes
44
HOST_STAT
Host Status
IN
See “Standard CMOS logic levels” on page 26
This pin allows the host to be asleep whilst the module is still attached to the network. The host indicates
that it is entering suspend mode by taking HOST_STATUS low. The module then inhibits data transfer until
HOST_STATUS goes high.
In order to ensure no data is lost in the entry to suspend mode, a specific sequence of checks is required:
these are detailed in the software specification.
If this pin is not used, connect a 10kΩ resistor between this pin and VDDS (pin 50).
23 of 176
GM40x GSM/GPRS Module Reference: UNDOC00048rF
Hardware Specification
Host Wakeup
PIN
Pin Name
Description
DIR
Notes
36
HOST_WAKEUP
Alert host of
incoming call/data
OUT
See “Standard CMOS logic levels” on page 26.
2mA rated
Active high output. If the host is asleep, and an incoming call is received, or data, or SMS, then the host
wakeup pin is driven high for 20µs in order to wake up the host.
2.2.11
Interrupt Output
PIN
Pin Name
Description
DIR
Notes
46
INT_OUT
Interrupt Output
OUT
See “Standard CMOS logic levels” on page 26
Because the AT command interface is host driven, there is no way for the module to output unsolicited
data. This interrupt indicates that the module has some message to convey, and would like to be
questioned. This is not used by the standard AT command set, only by additional functions programmed
into the module by the customer.
2.2.12
Keyboard Interface
PIN
Pin Name
Description
DIR
29
KBC0/GPO0
Keyboard Column 0
OUT
COLUMN (A6)
31
KBC1/GPO1
Keyboard Column 1
OUT
COLUMN (A5)
33
KBC2/GPO2
Keyboard Column 2
OUT
COLUMN (B5)
35
KBC3/GPO3
Keyboard Column 3
OUT
COLUMN (D5)
37
KBC4/GPO4
Keyboard Column 4
OUT
COLUMN (E5)
39
KBR0
Keyboard Row 0
IN
ROW(A4)
41
KBR1
Keyboard Row 1
IN
ROW(B4)
43
KBR2
Keyboard Row 2
IN
ROW(D5)
45
KBR3
Keyboard Row 3
IN
ROW(B3)
47
KBR4
Keyboard Row 4
IN
ROW(A2)
2.2.13
Notes
See “Standard CMOS logic
levels” on page 26.
2mA rated.
All row inputs have a 27kΩ
(nominal) pull-up resistor
integrated within the IC.
Every key can generate a
keyboard interrupt.
Asynchronous Serial Interface
Pin names used are those for DCE device:
PIN
Pin Name
Description
DIR
Notes
40
CTS
Clear to send (to host)
OUT
42
TXD
Transmit Data (from host)
IN
48
RTS
Request to send (from host)
IN
See “Standard CMOS logic levels” on page 26.
4mA rated.
CTS and RTS active LOW.
Serial data rate 56Kbps (57600bps)
49
RXD
Receive Data (to host)
OUT
GM40x GSM/GPRS Module Reference: UNDOC00048rF
24 of 176
Hardware Specification
2.2.14
General Purpose I/O
PIN
Pin Name
Description
DIR
Notes
28
GPIO1
General purpose I/O
I/O
See “Standard CMOS logic levels” on page 26.
30
GPIO2
General purpose I/O
I/O
19
GPIO3
General purpose I/O
I/O
2.2.15
Synchronous Serial Interface
PIN
Pin Name
Description
DIR
Notes
18
SPI_DATA
Serial Data
OUT
See “Standard CMOS logic levels” on page 26.
20
SPI_CLK
Serial Clock
OUT
22
SPI_CS
Chip Select
OUT
24
SPI_D/C
Data / Command
OUT
26
SPI_RST
Reset
OUT
2.2.16
RF Interface Specification
The RF Connection Pads incorporate a signal and ground PCB pad for soldering a semi-rigid coaxial
cable as an interface to the host platform. The pads are also used for RF probing during production test.
Parameter
Specification
Conditions
Output Impedance
50Ω
Across GSM900, DCS1800 & PCS 1900
bands
Output Load Upper Limit
15:1 VSWR1, but Ipeak increases.
Ipeak meets specification at <5:1
VSWR
To maintain PA stability
Output Power
GSM 900: 33dBm ±2dBm (full power)
GSM1800: 30dBm ±2dBm (full power)
These and other power control levels
are compliant with ETSI 11.10 Section
13.3
Units are calibrated to allow for a fixed
attenuation from the RF output of the module
to the antenna port.
The loss should not exceed 0.4dB and is
specified to within ±0.1dB.
1.See “RF” on page 37 for the affects on performance of different VSWRs.
2.2.17
Termination of unused lines
If the host design does not require them, unused lines can be terminated as follows:
● SPI bus (pins 18, 20, 22, 24 and 26): leave unconnected
● GPIO1, 2 and 3 (pins 19, 28 and 30): leave unconnected
● Host_wakeup (pin 36): leave unconnected
● Host_status (pin 44) and VDDS (pin 50): connect 10KΩ resistor between the two pins
● Keyboard matrix (pins 29, 31, 33, 35, 37, 39, 41, 43, 45, 47): leave unconnected.
25 of 176
GM40x GSM/GPRS Module Reference: UNDOC00048rF
Hardware Specification
2.3
Electrical Specification
2.3.1
Standard CMOS logic levels
Parameter
Description
Min
Nom
Max
Unit
VDDS
I/O supply voltage
2.7
2.9
3.1
VIH
High level input voltage
0.7*VDDS
VDDS+0.5
VIL
Low level input voltage
-0.5
0.3*VDDS
VOH
High-level output voltage
0.8*VDDS
VOL
Low-level output voltage
IOL/LOH
Rated output current
0.22*VDDS
GM40x GSM/GPRS Module Reference: UNDOC00048rF
mA
26 of 176
Multiplexer
3.0
Multiplexer
3.1
Introduction
The multiplexer serial interface used by the UbiNetics GPRS module supports a number of different data
streams (GPRS data, circuit switched data / fax, AT command interface, control / status information etc.).
Some of these can potentially be in operation simultaneously and may be communicating with different
host applications and/or drivers. The UbiNetics Multiplexer provides the means of accessing these
different data streams on the various host systems.
The implementation provides a single multiplexed serial link based on GSM 07.10 / 3G TS 27.0101. This
supports operation on a wide range of hosts. Depending on the host platform and / or application, it may
be necessary to implement the multiplexer within a driver and expose standard interfaces (virtual serial
ports) for each of the data channels. Alternatively, in some cases where the GPRS module is used for a
dedicated application, it may be desirable to build the serial multiplexer into the application software.
3.2
Overview
The Multiplexer provides a means to transmit and receive multiple data streams over a single
asynchronous serial connection. It supports a number of virtual connections between software entities in
the host platform and the corresponding entities in the GPRS module. Communication across the
multiplexed link uses 8-bit characters arranged into frames delimited by flag bytes.
3.2.1
Software Structure
Possible Host Software Structure
Modem Driver (DUN,
Fax etc)
TCP/IP / PPP
(GPRS)
AT commands for
control / status etc
Serial Port Emulation
Serial Port Emulation
(or network driver)
Serial Port Emulation
(or private API)
Multiplexer
Serial port driver
UART
1.ETSI TS 127 010 V3.3.0 (2000-03) Terminal Equipment to Mobile Station (TE-MS) multiplexer protocol (3G TS 27.010
version 3.3.0 Release 1999)
27 of 176
GM40x GSM/GPRS Module Reference: UNDOC00048rF
Multiplexer
Each of the top-level entities shown above is connected to a corresponding entity in the GPRS unit via one
of the multiplexer data channels (Data Link Connections / DLCs). These are set up one at a time, normally
on demand when a particular function is required.
GPRS Card / Module Software Structure
Initially each new DLC will connect to an instance of the AT command interpreter. The data channels are
connected to the other stack entities either by issuing the appropriate AT commands (e.g. dialling) or
explicitly using the multiplexer service negotiation command.
AT Command Interpreter
Trace / Debug (Test)
PPP
Multiplexer
GSM Stack
GPRS Stack
UART / Driver
3.3
Supported Functions
The following functions of 3G TS 27.0101 are supported. Additional functionality may be added at a later
stage.
● Multiplexer Advanced option (flag byte transparency) without error recovery
● Multiplexer Start-up / Closedown
● Data Link Connection (DLC) Establish / Release
● Up to 6 user DLCs
● UIH frames for user data (Unnumbered Information with Header check only)
● Flow Control command
● Modem Status command
● Service Negotiation command
● Null convergence layer (unformatted data streams).
3.4
Implementation
For more information on the implementation details, see footnote 1. In particular, control field values and
bit allocations are not discussed here.
1.ETSI TS 127 010 V3.3.0 (2000-03) Terminal Equipment to Mobile Station (TE-MS) multiplexer protocol (3G TS 27.010
version 3.3.0 Release 1999)
GM40x GSM/GPRS Module Reference: UNDOC00048rF
28 of 176
Multiplexer
3.4.1
General
Multiplexer Mode
The multiplexer operates using the advanced option without error recovery. This uses a flag transparency
mechanism to allow rapid resynchronisation in the event of any data loss.
Frame Structure
The frame used for the advanced option consists of an opening flag byte, address field byte, control field
byte, information field (variable or omitted depending on the frame type), frame check byte, and a closing
flag. The closing flag of one frame can be the opening flag of the following frame, so the minimum
overhead is 4 bytes per frame.
4.1.3 Supported Frame Types
Frame Type
Use
SABM (Set Asynchronous Balanced Mode)
Establishing a control or data channel.
UA (Unnumbered Acknowledgement)
'OK' Acknowledgement to SABM or DISC frame.
DISC (Disconnect)
Closing a data channel or closing down the multiplexer.
DM (Disconnected Mode)
'Already disconnected' response to DISC or UIH frame.
UIH (Unnumbered Information with Header Check)
User data or multiplexer control command. Frame
check applied to header only.
Any other frame types are not currently supported.
Acknowledgements, Timeouts and Retries
Where a frame type has an associated acknowledgement, if the expected response frame is not received
within time T1 (default of 100ms) then the sender can retry up to a maximum of N2 times (default of 3).
Frame Check Sequence (FCS)
The frame check sequence uses an 8-bit CRC algorithm. This allows a simple look-up table based
implementation to be used (see1 for algorithm and examples).
3.4.2
Multiplexer Start-up
The GPRS module / card will always start up in non-multiplexed mode. Before the multiplexer is initialised
the serial data stream to / from the UART connects directly to the AT command interpreter. The system can
be operated exclusively in non-multiplexed mode but use of some functions may be restricted. Multiplexed
mode is started with the following sequence:
● Host issues the AT+CMUX command (see the referenced documentation2 for command syntax). If the
GPRS unit supports multiplexed operation and accepts the parameters issued with the command then
it will return an "OK" response.
● At this point both the host and the GPRS unit should switch baud rate to that specified in the issued
AT+CMUX command and also set any other parameters as per the command (see table below for
1.ETSI TS 127 010 V3.3.0 (2000-03) Terminal Equipment to Mobile Station (TE-MS) multiplexer protocol (3G TS 27.010
version 3.3.0 Release 1999)
2.ETSI TS 127 007 V3.6.0 (2000-10), AT command set for User Equipment (UE) (3GPP TS 27.007 version 3.6.0 Release
1999)
29 of 176
GM40x GSM/GPRS Module Reference: UNDOC00048rF
Multiplexer
allowable parameter values). The default values will be used for any parameters which are not
included.
● The host should then send a SABM frame on DLC0. The GPRS module / PC card will respond with a UA
frame. Multiplexed mode is now active.
● Either end can now send commands on the control channel, or establish new user data channels. In
practice the establishment of new data channels will only be initiated by the host.
AT+CMUX Command parameters
Parameter
Allowable values
Operation mode
1 (advanced option)
Subset (Frame Type)
0 (UIH frames only)
Port Speed
1-5 (9600 to 115200 baud) (default = current rate)
N1 (Maximum frame size)
31-64 (default = 64)
T1 (Acknowledgement Timer)
10-100 (default 10 = 100ms)
N2 (Maximum Retransmissions)
3-10 (default 3)
T2 (Response Timer)
30-120 (default 30 = 300ms)
T3 (Wakeup Timer)
3-20 (default 10s)
k (Window Size)
Not supported - applies to error recovery mode only
3.4.3
Multiplexer closedown
The multiplexer is closed down by sending either a DISC frame on DLC0, or by using the closedown
command (see below). This can be sent from either end of the connection but would normally be sent by
the host. Whichever command type is used, any open data channels will be closed and the link will revert
to non-multiplexed AT command mode.
3.4.4
Data channel establishment and release
A data channel (Data Link Connection / DLC) is established by sending a SABM frame with the specified
DLCI. This will only be initiated by the host. If the DLC can be established then the GPRS unit will respond
by sending a UA frame with the same DLCI. If the DLC cannot be established then the response will be a
DM frame.
Once the data channel is established it is connected to one instance of the AT command interpreter in the
GPRS unit. All newly created data channels are equivalent until dedicated in some way. This can be done
in two ways - either by using the service negotiation command to explicitly define what the channel will be
used for, or implicitly by establishing a call, GPRS session etc.
The DLC is closed down by sending a DISC frame with the appropriate DLCI. If the DLC can be
disconnected then the GPRS unit will respond by sending a UA frame with the same DLCI. If the DLC is
already disconnected then the response will be a DM frame.
3.4.5
Data transmission
User data is transferred with UIH frames with the appropriate DLCI. The error recovery mode is not used,
so there is no acknowledgement of data receipt, and lost or bad frames are not retransmitted. In addition,
due to the use of UIH frames, there is no error check on the information payload, so if the connection is
GM40x GSM/GPRS Module Reference: UNDOC00048rF
30 of 176
Multiplexer
expected to be prone to errors then error checking (and correction if required) should be performed by
the higher layers.
Currently only type 1 (null) convergence layer is supported, so no structure is conveyed or implied in the
data. Any additional packet framing etc. required must be implemented with a higher-layer protocol.
Each data channel has an associated priority. The priority of a particular channel is based on the DLCI,
with lower DLCI values having higher priority. See the referenced documentation1 for the priority
assignments given to particular DLCI values. The multiplexer will attempt to transmit higher priority data
before that of lower priority. Frames already being transmitted will not be interrupted by higher-priority
frames. The multiplexer will interleave high and low priority data so as to prevent complete blocking of lowpriority data channels, while giving precedence to higher-priority data.
3.4.6
Control channel commands
The multiplexer control channel provides for various control commands and responses to be sent. These
are transferred using information frames (UIH) on DLC 0. Each control command frame consists of the
standard frame header etc. The information part of the frame contains a type byte which specifies the
command type and whether it is a command (C/R bit = 1) or a response (C/R bit = 0), a length byte, and a
variable number (may be zero) of value bytes containing the command parameters.
Each command has a corresponding response which has the same format as the command except for
the C/R bit mentioned above. The response should be sent as soon as possible after receiving the
command. If an unrecognised or unsupported command is received then a 'Non Supported Command
Response' should be sent.
If the expected response frame is not received within time T2 (default of 300ms) then the sender can retry
up to a maximum of N2 times (default of 3).
Multiplexer Closedown Command
The multiplexer closedown command is used to reset the link into normal AT command mode. This would
normally only be sent by the host. The GPRS unit will send the appropriate response and then return to
non-multiplexed mode.
Flow Control On / Off Command
The flow control commands are used to handle aggregate flow. Either end of the link can send a flow
control off command when it is unable to receive any new data. It should then send a flow control on
command when it is again ready to receive.
If a flow control off command is received then the multiplexer should not transmit any more user data. Any
new user data requests should be queued or failed. Command frames can still be transmitted as normal.
Modem Status Command
The modem status command is used to transfer virtual V.24 control signals associated with a data stream.
The following signals are supported:
Modem Status Command Bit
DTE >DCE
DCE >DTE
RTC (Ready to communicate)
DTR
DSR
1.ETSI TS 127 010 V3.3.0 (2000-03) Terminal Equipment to Mobile Station (TE-MS) multiplexer protocol (3G TS 27.010
version 3.3.0 Release 1999)
31 of 176
GM40x GSM/GPRS Module Reference: UNDOC00048rF
Multiplexer
RTR (Ready to receive)
RFR(RTS)
CTS
IC (Incoming call)
RI
DV (Data valid)
DCD
The exact mapping of these signals is detailed in the referenced documentation1, section 5.4.6.3.7.
The break signal is not supported. The EA bit of the control signal octet should always be set to 1 and the
command length should always be 2.
Service Negotiation Command
The service negotiation command is used to specify what a particular data channel will be used for. This
allows the GPRS unit to direct incoming call notifications etc. to the appropriate channel. The command
frame contains two value bytes — the first defines the general service type (voice or data) and the second
defines the specific service.
Service Value Byte
Specific Service Byte
Data type
03 (S2=0, S1=1, EA=1)
01 (V1-V7=0, EA=1)
Normal AT command mode (unspecified data type)
03
03 (V=1)
Circuit-switched data
03
05 (V=2)
GPRS data
03
07 (V=3)
Trace / Debug output
05 (S2=1, S1=0, EA=1)
Any
Voice (not supported)
Further data types may be added. These will continue as above using sequential values in the V1-V7 bits.
If the service negotiation command is not sent, the data channel will default to the normal AT command
mode. If there is no data channel specified for a particular service type, it is intended that incoming call
notifications for that service be sent on all open data channels which are in the AT mode. Contact
UbiNetics for more information about this.
1.ETSI TS 127 010 V3.3.0 (2000-03) Terminal Equipment to Mobile Station (TE-MS) multiplexer protocol (3G TS 27.010
version 3.3.0 Release 1999)
GM40x GSM/GPRS Module Reference: UNDOC00048rF
32 of 176
Host suspend procedure
4.0
Host suspend procedure
4.1
Introduction
When the GPRS module is used with a PDA host, it is necessary for the host to be able to suspend
operations due to user command or inactivity timeout, while keeping the module active. It is also
necessary for the module to be able to bring the host out of suspend mode on certain events. This section
describes the procedure that is used to enter and exit host suspend mode.
4.2
Multiplexer
The module contains a serial multiplexer based on the GSM 07.10 specification. However, the module
starts in non-multiplexed mode and so it is necessary to have procedures for entering and exiting
suspend mode which do not depend on the multiplexer.
The multiplexer specification includes a sleep mode which can be entered into by one party sending a
sleep mode request to the other. Also it defines a wake-up procedure of sending flag bytes until a
response is received. In theory these could be used to handle the host suspend mode, but since these
would only work if the multiplexer were active, another method has been defined which works in nonmultiplexed mode also.
4.3
Module power modes
One feature of the module is its ability to conserve power by turning off the 13MHz system clock (deep
sleep mode). The deep sleep manager in the module always tries to put the module into deep sleep mode
by regularly checking if deep sleep can be enabled.
The conditions for entering deep sleep mode are:
● There is no activity required on the air interface for a number of frames
● There are no timers about to expire
● There are no tasks ready to run
● There has been no activity on the UART Rx, Tx and flow control lines for 30 seconds
● There is no SIM activity
● The backlight is not active.
Deep sleep mode will be exited when:
● The defined sleep period has expired (e.g. for air interface or timer)
● There is an interrupt
● The UART exits sleep mode due to a transition on the Rx or CTS line.
The UART exiting sleep mode and the 13MHz clock starting takes some time. The host does not know
when the module is in deep sleep mode, so it is possible that the first character sent to the module (which
causes it to exit deep sleep mode) after some time could be lost.
To avoid this, the CTS flow control line is toggled prior to sending an AT command or multiplexer packet if
no characters have been sent for some time.
33 of 176
GM40x GSM/GPRS Module Reference: UNDOC00048rF
Host suspend procedure
4.4
Host wake-up events
The module provides the following wake-up events that will cause the HOST_WAKEUP output to be
toggled:
● Incoming circuit switched call
● SMS received
● GPRS data received
● UART Tx buffer >half full.
The MMI API allows for the first three of these events to be selectively enabled or disabled. The default
state is that all events are enabled.
The events will only generate a pulse on the HOST_WAKEUP line if they happen while the host is
suspended, or within a fixed time window before the host is suspended. This latter case is to guard
against the possibility of losing an event that happens after a suspend operation has been committed to
but before the host is suspended.
4.5
Host suspend operation
The host indicates that it is entering suspend mode by taking HOST_STATUS low. The module then inhibits
data transfer until HOST_STATUS goes high. In order to ensure no data is lost in the entry to suspend
mode, a specific sequence of checks is required.
Host suspend is normally disabled. It can be enabled by the AT command AT+HOST_STATUS (or from the
MMI API).
4.5.1
Host suspend procedure
The following procedure should be adopted by the host when suspending:
● Turn off all unsolicited responses (e.g. +CREG etc.)
● Terminate any circuit switched data calls
● Mask the HOST_WAKEUP interrupt within the PDA
● Take the HOST_STATUS output low
● Continue to read serial characters from the UART into a buffer for at least one character period after
HOST_STATUS is taken low
● Suspend (unmasking HOST_WAKEUP interrupt).
4.5.2
Module wake-up behaviour
The module acts as follows:
● If HOST_STATUS is low, no characters are sent to the UART (equivalent of CTS flow control, but
inverted)
● If a wake-up event is detected and HOST_STATUS is low, the HOST_WAKEUP output is toggled high
then low for approximately 20µs
● If a wake-up event is detected and HOST_STATUS is high, a timer is started (or re-started if already
running)
● When the timer expires, if HOST_STATUS is high, no action is performed. If HOST_STATUS is low the
HOST_WAKEUP output is toggled high then low approximately 20µs. This ensures that a wake-up
event that occurred just before or during the suspend operation is correctly serviced.
GM40x GSM/GPRS Module Reference: UNDOC00048rF
34 of 176
Host suspend procedure
4.5.3
Host wake-up behaviour
The host acts as follows:
● The HOST_WAKEUP pulse causes the host to exit the suspend state
● When it is ready to receive serial characters from the module, the host sets HOST_STATUS high
● Toggle CTS high and low briefly to force module to wake-up and check HOST_STATUS.
4.5.4
Timing diagram
The following diagram shows the behaviour in the worst-case scenario of a wake-up event occurring
during the suspend procedure:
Suspend
committed
MODULE
Timer
Event
Data ->UART
driver
UART TxD
HOST_WAKEUP
HOST
IRQ MASK
HOST_STATUS
!SUSPEND
CTS
The wake-up event happens after the host has committed to the suspend procedure and cannot abort it.
Since HOST_STATUS is high, the module starts a timer. It also starts to output the serial string
corresponding to the event (e.g. “RING”). The diagram show the case where the first character is
35 of 176
GM40x GSM/GPRS Module Reference: UNDOC00048rF
Host suspend procedure
transmitted before HOST_STATUS goes low, and the remainder of the string is transmitted after the host is
woken again. The HOST_WAKEUP pulse is generated after the timeout as HOST_STATUS is low at that
point. This causes the host to wake up again and receive the rest of the string corresponding to the wakeup event.
This procedure ensures that a wake-up event always causes the host to wake up, but does have the
possibility of generating a wake-up when the host has already accepted the event just prior to
suspending.
GM40x GSM/GPRS Module Reference: UNDOC00048rF
36 of 176
Integration Guidelines
5.0
Integration Guidelines
The following notes are designed to provide general help to those considering integrating the GM400 or
GM401 modules into their product.
When designing a product incorporating a GM400 or GM401 module, the main issues to consider are:
● RF
● EMC
● Ground plane connection
● Power supply
● Mechanical
● Firmware upgrading.
5.1
RF
Receiver sensitivity and transmitter output are greatly affected by the design of the RF connection. Great
care should be taken with the RF connection in the final product, as the VSWR and insertion losses in the
connection to the terminals can reduce transmitter and receiver performance, and increase current
consumption.
5.1.1
Receiver
VSWR
The input impedance of the receiver is 50Ω. In order to obtain the maximum power transfer and therefore
highest sensitivity, the antenna and any connecting cables should present an impedance as near to 50Ω
as possible.
The table below shows how the VSWR effects sensitivity:
VSWR
Reduction in Sensitivity
1:1
0 dB
1.5:1
0.18dB
2:1
0.51 dB
3:1
1.25 dB
Any reduction in sensitivity can be minimised by careful selection of an antenna suitable for the
application. A list of suppliers who may be able to help you with this is provided at the end of the section.
It may be necessary to add an external (to the module) matching network in order to ‘tune’ the antenna to
50Ω.
Insertion Loss
The insertion loss of any cables and matching circuit will cause dB for dB a loss in the sensitivity of the
completed product. It is therefore important to minimise this as much as possible by
● using high-Q components
37 of 176
GM40x GSM/GPRS Module Reference: UNDOC00048rF
Integration Guidelines
● keeping any connecting cables as short as possible.
5.1.2
Transmitter
Power out and current consumption are both affected by the match presented to the RF connection. As
with the receiver, the VSWR and insertion loss can adversely affect transmitter performance.
VSWR
Transmitter performance is specified by measuring the power into a 50Ω load at the RF pads on the
module. It is important that the module is presented with a 50Ω load, so that the transmitted power is
maximised and that current consumption is minimised.
By presenting a load impedance other than 50Ω to the module, some of the power generated by the PA is
reflected back into the module. This power is therefore not emitted (reducing product performance) but
instead is absorbed by the module, heating it up. If it can, the PA tries to compensate by generating more
power, hence drawing more current.
Below is a table showing typical transmitter power reduction and current consumption for different VSWRs
at 900MHz and 1800MHz:
VSWR
Peak Current Consumption
Reduction in Power
1:1
1.8 A
0 dB
12:1
3.1 A
-2.1 dB
GSM 900 Channel 62, PCL 5, Vsupply = 3.3 Volts
VSWR
Peak Current Consumption
Reduction in Power
1:1
1.42 A
0 dB
12:1
1.42 A
-1.7dB
GSM 1800 Channel 740, PCL 0, Vsupply = 3.3 Volts
Insertion Loss
As with the Receiver, the insertion loss of any cables and matching circuit will cause dB for dB a loss in the
power emitted. It is therefore important to minimise this by using high-Q components and keeping any
connecting cables as short as possible.
5.1.3
Sourcing antennae
Companies that provide support for the development of both internal and external antennas include:
● Allgon (www.allgon.com)
● Amphenol (http://www.amphenol.com/)
● Centurion (http://www.centurion.com/antennas.htm)
● Filtronic LK (http://www.lkproducts.com/mobile/index.html)
● Galtronics (http://www.galtronics.com/)
● Moteco (http://www.moteco.com/)
● Panorama (http://www.panorama.co.uk)
● Rangestar (http://www.rangestar.com/search.asp)
GM40x GSM/GPRS Module Reference: UNDOC00048rF
38 of 176
Integration Guidelines
This information is provided for your information only and does not represent a recommendation by
UbiNetics Ltd. of these companies or their products.
5.2
EMC
Unwanted radiation from a poorly-designed or incorrectly-sited antenna, or from the host application, can
adversely affect the performance of the module and of the host application. It is therefore essential that
EMC testing be carried out on the application with the module installed as soon as possible during
development, to ensure that RF radiation or interference from the application does not cause any
problems.
5.2.1
Radiation by the application
The metal screening can surrounding the module shields it from most spurious emissions which may be
radiated by the application.
Attention must nevertheless be paid to sources of RF interference within the application — typically
processor clocks and buses, and switch-mode power supplies. The supply to these from the battery
should be filtered using low-value capacitors (whose self-resonant frequency is in the rejection band
required) and lossy ferrite beads, such as the Murata BLM series.
Early EMC tests should be made to pick up any potential problems of this type.
5.2.2
RF interference
(See also “RF” on page 37.)
Apart from ensuring optimum transmit and receive performance, a well-designed and located antenna
can also ensure that RF radiation does not adversely affect the performance of the module.
The GSM specification demands extremely high sensitivity from the GSM receiver: an input signal of
-100dBm must be recovered with a low bit error rate. This represents only 15pW (15 x 10-12 W) of input
signal power. Any sources of RF noise must generate less than a tenth of this power in any given receive
band, otherwise receiver desensing will occur. This limit is some 40dB below the allowed EMC limits,
which themselves are measured at 10 metres. It is therefore possible that equipment that passes EMC
testing may render the GSM radio unusable.
Audio circuits (especially microphone inputs) are particularly susceptible to RF interference. Care should
be taken to keep RF radiation away from the module interface connector, from which it can find its way
onto module tracks.
As much as possible of the RF circuitry should be shielded, and the RF connection and antenna should
be separated from the module and the application by a metallic or metallised-plastic case.
Because of the very high data rates on SIM interface lines, these should be kept as short as possible
(preferably <8cm), and care should taken to shield them from interference.
Ripple
The module has been tested with a ripple of 250mV P-P sine wave 100Hz to 10KHz on the centre channel
of 900 and 1800 bands with the nominal 3.6v supply, with no degradation in performance. It should be
noted, however, that half the peak-to-peak ripple on the power supply must be greater than the minimum
operating voltage.
39 of 176
GM40x GSM/GPRS Module Reference: UNDOC00048rF
Integration Guidelines
5.3
Ground plane connection
The module PCB ground plane is connected to the metal RF screening can which completely encloses
the module.
The screening can itself has four legs which provide the mechanical mounting points for the module in the
application. Only one of these, however, should be used as the electrical grounding point for the module in
the application: this is the leg shown in the drawing in “Pin out diagram and connector orientation” on
page 10. Using only this leg for grounding localises the current flow from the PA to ground and minimises
radiation accordingly.
5.4
Power supply
The power supply should be adequate to meet the specifications outlined in “Main power supply” on
page 13 and “Backup power supply” on page 17.
5.5
Mechanical
“Mechanical Drawings: GM400/401” on page 7 provides the physical dimensions of the module.
The section “Pin out diagram and connector orientation” on page 10 details the type of connector required
to interface with the GM400/401 module, and shows the position of the RF connection pads and the
mechanical mounting points.
5.6
Firmware upgrading
A flash upgrader program, which runs on a PC, is available for upgrading the firmware on the module. To
use this program, the integrator must provide a connection between a PC-compatible device and the
module’s serial interface, which is accessible via the module interface connector (see “Asynchronous
Serial Interface” on page 24).
GM40x GSM/GPRS Module Reference: UNDOC00048rF
40 of 176
Regulatory Approval
6.0
41 of 176
Regulatory Approval
GM40x GSM/GPRS Module Reference: UNDOC00048rF
Regulatory Approval
UbiNetics GM40x modules have been designed to meet the most demanding Safety, Radio, Protocol,
EMC, Network and Environmental performance standards.
They are tested and approved against the following European and US standards:
Standard
Europe
US
EN60950
Safety
UL60950 edition 3
3GPP 51.010
Radio
FCC part 24
3GPP 51.010
Protocol
3GPP 51.010
EMC (Electromagnetic Compatibility)
FCC part 15
EN 301 489
GCF
ETS 300 019
Network
Environmental
PTCRB
Customer specific
UbiNetics hereby declares that GM40x modules are in compliance with the essential requirements and
other relevant provisions of Directive 1999/5/EC.
Because the modules themselves have already obtained Regulatory Approvals under the RTTE Directive,
any product that contains a UbiNetics module does not have to undergo such stringent testing as it
otherwise would.
For example, your product will not normally have to undergo Protocol or SIM testing, as Protocol and SIM
performance is already covered by module approval.
Regulatory Testing of the finished product will normally be limited to Safety, EMC and Environmental
standards (which apply to most electronic products in any case), plus Radio, SAR and Network testing.
However, the approvals already obtained by the module in these areas mean that the amount of testing of
the finished product will normally be less than would otherwise be required.
European and US Regulatory Approvals are accepted in many other countries. UbiNetics can provide an
outline of the approvals required for other world markets that have their own specific requirements, or even
help you obtain these approvals if you wish.
How UbiNetics can help
As a world leader in GSM, GPRS and UMTS technology, and with offices in the UK, Hong Kong, India and
the United States, UbiNetics Ltd. has wide experience of designing and selling compliant wireless
telecommunications products in global markets.
We are now able to offer our Interoperability Test and Approval expertise to other companies that have not
yet developed their own, or who merely wish to concentrate on what they do best.
These are some of the services we offer:
● Interoperability testing
● Regulatory approvals
● Network approvals
● Product Design Validation
● EMC and safety testing
● EMC consultancy.
GM40x GSM/GPRS Module Reference: UNDOC00048rF
42 of 176
Regulatory Approval
Interoperability Testing
Regulation and test requirements are now struggling to keep pace with the speed of technological
development. Interoperability testing is now crucial for demonstrating that products actually work in the
varied environments presented by different network infrastructures.
With our detailed knowledge of the infrastructure of major networks, and access to their test beds, we are
in a unique position to offer an effective interoperability testing service.
Regulatory Approvals
We have compiled an extensive database on a large number of country requirements, both current and
future. We are therefore able to advise on requirements in your target markets during the design phase,
and obtain timely approvals for finished products. With this we can offer the following services:
● Product approvals under the R&TTE directive
● World-wide testing, application and management
● In-house Anite protocol testing
● RF and SIM Protocol testing
● Compiling Technical Construction Files
● EMC testing
● Safety/SAR testing.
Network approvals
UbiNetics have established close working relationships with network operators in the UK, Europe and the
United States. This enables us to obtain crucial network approvals on target networks with the minimum
delay.
Through the relationships we have built up with network operators, we have acquired a depth of
knowledge of their network infrastructure and network-specific test requirements. This has enabled us to
plan out field trial test routes to cover a comprehensive range of operating situations. All of this allows us to
offer the following services:
● Fully-automated field trials testing
● Functional testing against network operator requirements
● Drive testing.
All of these services can be performed for any market in the world.
Product Design Validation
Based at our main test laboratories in Melbourn, near Cambridge in the UK, our engineers have vast
experience in product validation. They are able to carry out a wide range of product testing in our
laboratories. Our offices in Hong Kong, India and North America co-ordinate testing for those markets.
Through our close working relationship with BABT, we have achieved partner status, so we are also able to
call upon the global resources of BABT.
We can ensure that your product meets its physical design specification in all areas, using the following
services:
● Environmental and mechanical testing
● Accelerated Life Testing (ALT)
● AT command testing
● Supplementary Services testing
● Testing the product against product specifications; this may include compatibility with different opera-
tion systems, MMI and compliance with documentation.
43 of 176
GM40x GSM/GPRS Module Reference: UNDOC00048rF
Regulatory Approval
EMC and Safety
EMC performance is crucial both for obtaining regulatory approval and for determining product
acceptability. We can advise on EMC implications during the design phase, then, with our partners in the
UK, carry out the necessary test procedures and evaluate the results. In cases where EMC performance
needs to be improved, we are able to suggest product modifications.
Other Services
Our extensive experience of selling wireless products into world markets also enables us to advise clients
on many other aspects of doing business around the world, such as
● importing / exporting requirements
● country-specific labelling requirements.
Memberships
Our memberships of the following bodies allows us to keep up to date and even ahead of the game in
world regulation and test requirements:
● GSM Association (MoU)
● ETSI
● GCF.
GM40x GSM/GPRS Module Reference: UNDOC00048rF
44 of 176
Definitions and Abbreviations
7.0
Definitions and Abbreviations
This section contains a list of common definitions and abbreviations used in this document.
7.0.1
Definitions
Off-line Command State
The modem enters this state after power up i.e. the modem is not in a data call (offline) and ready to accept AT commands.
On-line Data State
The modem will change from off-line command state to on-line data state after
successfully setting up a data call. This allows the mobile station to exchange data
with the remote station.
On-line Command State
To change from on-line data state to on-line command state the DTE sends the escape
sequence +++. This allows AT commands to be sent to the modem whilst still retaining
the data connection to the remote station. The command ATH will end the data call
and ATO will return to on-line data state.
Remote Station
This is the term given to describe the equipment or modem at the other end of the link,
when making a mobile originated or mobile terminated call.
Mobile Station
Throughout this document this term refers to the UbiNetics modem.
Mobile Originated (MO)
This means a voice call, data call or SMS has initiated by the modem.
Mobile Terminated (MT)
This means a voice call, data call or SMS has been received by the modem.
7.0.2
Syntactical Definitions
The following syntactical definitions are used in this document:
Carriage Return character.
Line Feed character.
<...>
a sub-parameter enclosed within angle brackets, is a syntactical element. The brackets themselves
do not appear in the command line.
[...]
Optional sub-parameter, is enclosed within square brackets. This indicates the element may or may
not be present within a result code or can be omitted from the command string. The square
brackets themselves do not appear in the command line.
underline
Indicates a default setting of a sub-parameter value after a factory reset.
7.0.3
Abbreviations
The following abbreviations are used in this document:
AT
ATtention, used to start a command line
CBM
Cell Broadcast Message
CCITT
Consultative Committee on International Telegraphy and Telephony
DCE
Data Connection Equipment, refers to the modem which is controlled by the computer and application
software. Also see TA
45 of 176
GM40x GSM/GPRS Module Reference: UNDOC00048rF
Definitions and Abbreviations
DTE
Data Terminal Equipment, refers to the computer which is used to control the modem via the serial
interface.
EMC
Electromagnetic Compatibility
ETSI
European Telecommunications Standards Institute
GPRS
General Packet Radio Service
GSM
Global System for Mobile communications
IMEI
International Mobile station Equipment Identity
ITU-T
International Telecommunication Union = Telecommunication Standardisation Sector
ME
Mobile Equipment; refers to the modem
MO
Mobile Originated, when a call is made from the mobile station
MT
Mobile Terminated, when an incoming call is answered by the mobile station
PA
Power Amplifier (transmitter)
PAD
Packet Assembler/Disassembler
PDU
Protocol Data Unit
PIN
Personal Identification Number: a 4-digit code used to protect the SIM
PPP
Point-to-Point Protocol
PUK
Unblocking Key. An 8-digit code used to unblock SIM PIN
RF
Radio Frequency
RLP
Radio Link Protocol
SAR
Specific Absorption Rate
SIM
Subscriber Identity Module
SMS
Short Message Service
TE
Terminal Equipment. Refers to the computer and application software which is controlling the modem,
via the AT command interface
TA
Terminal Adapter. Within this text the TA refers to the modem which is controlled by the application
software, via the AT command interface
TAPI
Telephone APplication Interface.
TCP
Transmission Control Protocol
ME
Mobile Equipment. Within this text the ME refers to the UbiNetics modem, which is controlled by the
application software. As seen from the AT command interface, the TA and ME have been implemented
as a single entity
TIA
Telecommunications Industry Association
UDP
User Datagram Protocol
VSWR
Voltage Standing Wave Ratio
GM40x GSM/GPRS Module Reference: UNDOC00048rF
46 of 176
AT Commands: Introduction
8.0
AT Commands: Introduction
8.1
Overview
UbiNetics Ltd. produces a range of dual-band GSM/GPRS modules, which give compatible mobile
devices wireless connectivity using the GSM900/1800/1900 cellular networks.
The modules are controlled by industry-standard AT commands which are defined by ETSI in GSM 07.07,
GSM 07.05, V.25ter and T.32. These may be downloaded from http://www.etsi.org or http://www.3gpp.org
This manual lists the AT command set currently supported by the UbiNetics GPRS module. It is not
intended to be a full specification of each AT command, but a quick reference to the syntax which
includes any details specific to the implementation. For a full specification of each command, please see
the original ETSI and ITU documentation.
All other commands not included within this document, whether recognised or not, are not supported and
their use is not guaranteed.
8.2
Format of the AT Command String and Result Code
In general AT commands comprise three parts, which start with AT, followed by a command and ended
with the line termination character . The exceptions to this are A/ and +++, which are sent without AT
and carriage return.
The response from each command varies and is documented within the following text. In general, a
successful command will respond with OK, whilst an unrecognised command will fail with an error. If the
command is recognised but fails due to an invalid sub-parameter, equipment error or network error, a
more informative result code may be obtained by using the command AT+CMEE=2, to display extended
verbose result codes.
8.2.1
Types of Commands
AT commands have three basic structures, some of which are not applicable to all command types. For
further information, see the individual commands.
Test Commands
Test Commands (ATxxx=?) test the existence of a command and checks its range of sub-parameter(s).
UbiNetics may not support the full range of values returned by this command.
Read Commands
Read Commands (ATxxx?) read the current value of the sub-parameter(s).
Set Commands
Set Commands (ATxxx=a,b) will attempt to set a new subparameter value(s). If the command is
successful the AT command interpreter will return OK (if ATV1, ATQ0), otherwise an error or informative
result code will be returned.
47 of 176
GM40x GSM/GPRS Module Reference: UNDOC00048rF
AT Commands: Introduction
8.2.2
Command Line Editing
When using a terminal screen to talk directly to the modem, the Back Space character is useful for
deleting previous character(s) sent in error. However Back Space cannot delete the initial AT or the line
termination character .
8.2.3
Command Line Termination
The line termination character Carriage Return tells the modem to accept and process the
command.
8.2.4
Command Formatting
Result code(s) that are sent from the modem use the Line Feed character appended to a Carriage
Return , to format the text correctly on different lines.
8.2.5
Command Line Echo
In command mode, characters that are sent to the modem are echoed back to the DTE. This can be
disabled by using the AT Command ATE0.
8.2.6
Concatenation
Several commands may be joined together to form a single command string, that must be no longer than
350 characters (including the line termination character ).
When concatenating commands, only one AT is required at the beginning of the string and one carriage
return at the end. In the middle, commands are joined together in the order to be processed.
Extended commands, i.e. ones which start AT+ also require an additional semi-colon (;). If an error occurs
while processing the string, the following commands will not be processed and an error returned. See the
examples below:
ATE0V1D123456;
AT+CMGR=1,2;+CMGR=3,4
Some AT commands are not suitable for concatenation and careful thought is required before stringing
together many AT commands.
8.2.7
Response Code Format
The format of the result code is controlled by ATV. The default setting is verbose OK.
8.2.8
Response Code Suppression
Response code suppression is controlled by ATQ. By default response codes are shown.
8.2.9
Final Result Code
This is the last result code returned by the command being processed. In the case of the Dial command
this could be OK, NO CARRIER, NO DIALTONE, NO ANSWER, BUSY, ERROR.
GM40x GSM/GPRS Module Reference: UNDOC00048rF
48 of 176
AT Commands: Introduction
8.2.10
Intermediate Result Code
This is a result code which is displayed before the final result code. In the case of the Dial command this
could be CONNECT or CONNECT.
8.2.11
Unsolicited Result Code
These are result codes generated by an event not directly linked to the command which is being
processed. A good example is an incoming voice call will generate RING or +CRING: VOICE when
AT+CRC=1.
49 of 176
GM40x GSM/GPRS Module Reference: UNDOC00048rF
Commands Specified by GSM 07.07
9.0
Commands Specified by GSM 07.07
This section covers the AT commands specified within GSM 07.07 and supported by UbiNetics devices.
9.1
General Commands
9.1.1
+CGMI
Request Manufacturer Identification
Description
This command causes the modem to return the manufacturer-specific identity.
Command
Possible Response
AT+CGMI=?
AT+CGMI
Ubinetics Ltd.
Parameters
None.
9.1.2
+CGMM
Request Model Identification
Description
This command causes the modem to return the manufacturer-specific model identity.
Command
Possible Response
AT+CGMM=?
AT+CGMM
Parameters
None.
9.1.3
+CGMR
Request Revision Identification
Description
This command causes the modem to return the manufacturer-specific model revision identity.
Command
Possible Response
AT+CGMR=?
AT+CGMR
Parameters
None.
GM40x GSM/GPRS Module Reference: UNDOC00048rF
50 of 176
Commands Specified by GSM 07.07
9.1.4
+CGSN
Request Product Serial Number Identification
Description
This command causes the modem to return the product serial number.
Command
Possible Response
AT+CGSN=?
AT+CGSN
Parameters
None.
9.1.5
+CSCS
Select DTE Character Set
Description
This command selects the character set used by the modem, to allow correct conversion of the character
strings between the DTE and the modem.
Command
Possible Response
AT+CSCS=?
+CSCS: (list of supported s)
AT+CSCS?
+CSCS:
AT+CSCS=
Parameters
9.1.6
GSM
GSM alphabet
“IRA”
International Reference Alphabet
HEX
Hexadecimal numbers from 00 to FF
+CIMI
Request International Mobile Subscriber Identity
Description
Execution command causes the modem to return the International Mobile Subscriber Identity Number
(IMSI), when IMSI attached to a network.
Command
Possible Response
AT+CIMI
Parameters
51 of 176
International Mobile Subscriber Identity number
GM40x GSM/GPRS Module Reference: UNDOC00048rF
Commands Specified by GSM 07.07
9.1.7
+WS46
Select Wireless Network
Description
Selects the cellular network Wireless Data Service (WDS) to operate with the modem.
Command
Possible Response
AT+WS46=?
(list of supported s)
AT+WS46?
AT+WS46=[]
Parameters
9.1.8
12
GSM digital cellular
+CSTA
Select type of address
Description
Selects the type of number for further dialling commands according to GSM specifications.
Command
Possible Response
+CSTA=?
+CSTA: (list of supported s)
+CSTA?
+CSTA:
+CSTA=[]
Parameters
9.2
type of address octet in integer format
129
default
145
default when dialling string includes the international access code character ‘+’
Call Control Commands
9.2.1
Description
Dial Command
Initiates a mobile-originated call to the destination number .
Command
Possible Response
ATD[][;]
see the table below
Parameters
destination number containing the following characters 0-9,*,#,+,A,B,C,D
pause during dialling, ignored
GM40x GSM/GPRS Module Reference: UNDOC00048rF
52 of 176
Commands Specified by GSM 07.07
tone dialling, ignored
pulse dialling, ignored
register recall/hook flash, ignored
wait for dial tone, ignored
wait for quiet answer, ignored
restrict CLI presentation, overriding AT+CLIR setting
originate a voice call
Note: ATD112; is reserved for emergency calls only.
Verbose Result Code
Numeric Result
Code
Description
OK
Command executed, no error
CONNECT
Connection set up (ATX=0)
CONNECT
Connection set up (ATX=n) where n>0
RING
Ringing tone is present (AT+CRC=0)
NO CARRIER
Call failed to connect or disconnected
ERROR
Invalid command or too long
BUSY
The called party is currently in another call
NO ANSWER
Connection failed up to time out
9.2.2
D>
Dial Selected Phone Book
Description
This command initiates a Mobile Originated call, from the specified phone book and location.
Command
Possible Response
ATD>[I][;]
see the table within Dial Command
Parameters
EN
Emergency Number
AD
SIM phone book
Memory location of number to dial
Restrict CLI presentation, overriding AT+CLIR setting
Originate a voice call
9.2.3
D>
Dial Current Phone Book
Description
Initiates a mobile originated call, from the currently selected phone book, location .
Command
Possible Response
ATD>[I][;]
see the table within Dial Command
53 of 176
GM40x GSM/GPRS Module Reference: UNDOC00048rF
Commands Specified by GSM 07.07
Parameters
9.2.4
number of memory location to dial
restrict CLI presentation, overriding AT+CLIR setting
originate a voice call
+CHMOD
Call mode
Description
Selects the call mode for dialling commands or for next answering command. The mode can be either
single or alternating (for example, voice/data, voice/fax).
Command
Possible Response
+CMOD=?
+CMOD: (list of supported s)
+CMOD?
+CMOD:
+CMOD=[]
Parameters
9.2.5
single mode
alternating voice/fax
alternating voice/data
voice followed by data
+CHUP
Hangup Call
Description
Execution command hangs up all active calls, giving an assured procedure to terminate an alternating
mode call.
Command
Possible Response
AT+CHUP
Parameters
None.
9.2.6
+CBST
Select Bearer Service Type
Description
Set command selects the bearer service for Mobile Originated calls. Values may also be used during
mobile terminated data call setup.
GM40x GSM/GPRS Module Reference: UNDOC00048rF
54 of 176
Commands Specified by GSM 07.07
Command
Possible Response
AT+CBST=?
+CBST: (list of supported s),(list of supported
s),(list of supported s)
AT+CBST?
+CBST: ,,
AT+CBST=[[,[,]]]
Parameters
9600 bps (V.32)
12
9600 bps (V.34)
14
14400 bps (V.34)
71
9600 bps (V.110)
75
14400 bps (V.110)
data circuit asynchronous (UDI or 3.1 kHz modem)
9.2.7
Sets whether error correction is performed by RLP, or by other means
transparent
non-transparent
+CRLP
Radio Link Protocol
Description
Radio link protocol (RLP) parameters used for non-transparent data calls.
Command
Possible Response
AT+CRLP=?
+CRLP: (list of supported s),(list of supported s),(list of
supported s),(list of supported s)]
[+CRLP: (list of supported s),(list of supported s),(list of
supported s),(list of supported s)][...]]
AT+CRLP?
+CRLP: ,,,][
+CRLP:,,,][...]]
AT+CRLP=[[,[,[,]]]]
Parameters
0-61
IWF to MS window size
0-61
MS to IWF window size
39-48-255
acknowledgement timer t1, in 10ms units
1-100-255
retransmission attempts n2 (the default subject to change)
Notes
● Only version 1 is supported.
● and are not implemented.
● Not all of the combinations of parameters have not been tested.
55 of 176
GM40x GSM/GPRS Module Reference: UNDOC00048rF
Commands Specified by GSM 07.07
9.2.8
+CR
Service Reporting Control
Description
Set command controls whether or not intermediate result code is returned from the modem to the DTE. If
enabled, the intermediate result code is transmitted when the modem has established the speed, which is
before the final result code connect.
Command
Possible Response
AT+CR=?
+CR: (list of supported s)
AT+CR?
+CR:
AT+CR=[]
intermediate result code
+CR:
Parameters
disables reporting
enables reporting
9.2.9
service supported, displayed after connect message
ASYNC
asynchronous transparent
REL ASYNC
asynchronous non-transparent
+CEER
Extended Error Report
Description
This command returns information text, which offers the user an extended report for the reason of the
failure of the last unsuccessful call set up (originating or answering) or in-call modification.
Command
Possible Response
AT+CEER
+CEER:
Parameters
no error
unassigned number
no route to destination
channel unacceptable
operator determined barring
normal call clearing
user busy
no user responding
user alerting no answer
call rejected
number changed
GM40x GSM/GPRS Module Reference: UNDOC00048rF
56 of 176
Commands Specified by GSM 07.07
non selected user clearing
destination out of order
invalid number format
facility rejected
response to status enquiry
normal unspecified
no channel available
network out of order
temporary failure
switching equipment congestion
access information discarded
requested channel unavailable
resources unavailable
quality of service unavailable
requested facility unsubscribed
incoming calls barred within CUG
bearer capability not authorized
bearer capability not available
service not available
bearer service not implemented
ACM reached ACM maximum
facility not implemented
only restricted bearer cap. avail.
service not implemented
invalid TI
no member of CUG
incompatible destination
invalid transit network selection
incorrect message
invalid mandatory information
message type not implemented
message type incompatible
info element not implemented
conditional info element error
message incompatible
recovery on time expiry
57 of 176
GM40x GSM/GPRS Module Reference: UNDOC00048rF
Commands Specified by GSM 07.07
protocol error
interworking error
bearer service not available
no TI available
timer 303 expiry
establishment failure
no error
operation failed
timeout
bearer service not compatible
9.2.10
+CRC
Cellular Result Codes
Description
Set command controls the use of extended format reporting during a MT call set up.
Command
Possible Response
AT+CRC=?
+CRC: (list of supported s)
AT+CRC?
+CRC:
AT+CRC=[]
unsolicited result code
+CRING:
Parameters
9.2.11
disables extended format (i.e. +RING)
enables extended format (i.e. +CRING: VOICE)
ASYNC
asynchronous transparent
REL ASYNC
asynchronous non-transparent
VOICE
normal voice
FAX
Facsimile
+CRING
Result code
Description
Result code only generated when AT+CRC=1. See See “+CRC Cellular Result Codes” on page 58.
GM40x GSM/GPRS Module Reference: UNDOC00048rF
58 of 176
Commands Specified by GSM 07.07
9.3
Network Service Related Commands
9.3.1
+CSNS
Single Numbering Scheme
Description
Selects the bearer or teleservice to be used when a single numbering scheme call is established.
Command
Possible Response
AT+CSNS=?
+CSNS: (list of supported s)
AT+CSNS?
+CSNS:
AT+CSNS=[]
Parameters
9.3.2
voice
alternating voice/fax; fax first (TS61)
fax (TS 62)
alternating voice/data, voice first (BS61)
data
alternating voice/fax, fax first (TS61)
alternating voice/data, data first (BS61)
voice followed by data (BS81)
+CNUM
Subscriber Number
Description
Action command returns the MSISDNs related to the subscriber. If subscriber has different MSISDN for
different services, each MSISDN is returned in a separate line.
Command
Possible Response
AT+CNUM=?
AT+CNUM
+CNUM: [],,
[,,[,]][
+CNUM: [],,
[,,[,]][...]]
Parameters
optional alphanumeric string associated with
string type phone number of format specified by
type of address octet in integer format
as defined in AT+CBST
service related to the phone number
59 of 176
asynchronous modem
GM40x GSM/GPRS Module Reference: UNDOC00048rF
Commands Specified by GSM 07.07
9.3.3
synchronous modem
PAD access (asynchronous)
packet access (synchronous)
voice
fax
information transfer capability
3.1 kHz
UDI
+CREG
Network Registration
Description
Displays network registration status.
Command
Possible Response
AT+CREG=?
+CREG: (list of supported s)
AT+CREG?
+CREG: ,
AT+CREG=[]
unsolicited result code
+CREG:
Parameters
disable network registration unsolicited result code
enable network registration unsolicited result code
not registered new operator to registered and not searching
registered, home network
not registered, currently searching a new operator to register with
registration denied
unknown
registered, roaming
GM40x GSM/GPRS Module Reference: UNDOC00048rF
60 of 176
Commands Specified by GSM 07.07
9.3.4
+COPS
Operator Selection
Description
Registers/displays network operators available.
Command
Possible Response
AT+COPS=?
+COPS: ([list of supported ,long alphanumeric
,short alphanumeric ,numeric
)s][,,(list of supported s),(list of
supported s)]
AT+COPS?
+COPS: [,,]
AT+COPS=[[,[,]]]
e.g.
AT+COPS=1,2,"23410"
Parameters
availability of operator
unknown
available
current
forbidden
61 of 176
shows the operator identity, within speech marks, in the format set by
registration mode
automatic ( field is ignored)
manual ( field shall be present)
de-register from network
set only (for read command AT+COPS?). Do not attempt registration /
de-registration ( field is ignored); this value is not applicable in read
command response
manual/automatic ( field shall be present); if manual selection fails,
automatic mode =0) is entered
format of reports
long format alphanumeric
short format alphanumeric
numeric
GM40x GSM/GPRS Module Reference: UNDOC00048rF
Commands Specified by GSM 07.07
9.3.5
+CLCK
Facility Lock
Description
This command is used to lock, unlock or interrogate the modem or a network facility. A password is
required for some actions.
Command
Possible Response
AT+CLCK=?
+CLCK: (list of supported s)
AT+CLCK=,[,],]]
e.g.
AT+CLCK="SC",0,"1111"
when =2 and command successful;
+CLCK: [,[
+CLCK: ,[...]]
Parameters
(within speech marks)
SC
SIM (lock SIM card) SIM asks password in modem power-up and
when this lock command issued
AO
BAOC (Bar All Outgoing Calls)
OI
BOIC (Bar Outgoing International Calls)
OX
BOIC-exHC (Bar Outgoing International Calls except to Home Country)
AI
BAIC (Bar All Incoming Calls)
IR
BIC-Roam (Bar Incoming Calls when Roaming outside the home country)
AB
All Barring services
AG
All outGoing barring services
AC
All inComing barring services
FD
SIM fixed dialling memory feature, if PIN2 authentication has not been
done during the current session, PIN2 is required as
unlock
lock
query status
not active (when mode=2, indicates no services are active)
active
the same password used by AT+CPWD, within speech marks
a sum of integers each representing a class of information
voice (telephony)
data (refers to all bearer services; with =2 this may refer only to
some bearer service if TA does not support values 16, 32, 64 and 128)
fax (facsimile services)
all classes
GM40x GSM/GPRS Module Reference: UNDOC00048rF
62 of 176
Commands Specified by GSM 07.07
9.3.6
+CPWD
Change Password
Description
Action command sets a new password for the facility lock function defined by command facility lock
(AT+CLCK).
Command
Possible Response
AT+CPWD=?
+CPWD: list of supported (,)s
AT+CPWD=,,
e.g.
AT+CPWD=”SC”,”1234”,”4321”
Parameters
(within speech marks)
SC
lock SIM card, asks password in modem power-up and when this loc
command issued (SIM PIN1)
AO
bar All Outgoing Calls (BAOC)
OI
bar Outgoing International Calls (BOIC)
OX
bar Outgoing International Calls except to Home Country (BOIC-exHC)
AI
bar All Incoming Calls (BAIC)
IR
bar Incoming Calls when Roaming outside the home country (BIC-Roam)
AB
all Barring services
AG
all outGoing barring services
AC
all inComing barring services
P2
SIM PIN2
integer type, maximum length of the password for the facility (see AT+CPWD=?)
string type; shall be the same as password specified for the facility from the modem AT
command interface or with command Change Password AT+CPWD
string type; shall be the new password for the facility from the modem AT command
interface or with command Change Password AT+CPWD
9.3.7
+CLIP
Calling Line Identification Presentation
Description
This command allows the called subscriber to get the Calling Line Identity (CLI) of the calling party, in a
mobile terminated call.
Command
Possible Response
AT+CLIP=?
+CLIP: (list of supported s)
AT+CLIP?
+CLIP: ,
AT+CLIP=[]
unsolicited result code, displayed when CLI is enabled
for the first two rings
63 of 176
+CLIP: ,
GM40x GSM/GPRS Module Reference: UNDOC00048rF
Commands Specified by GSM 07.07
Parameters
sets/shows the result code presentation status in the modem
disable
enable
CLIP not provisioned (parameter shows the subscriber CLIP service status in the net
work)
CLIP provisioned
unknown (e.g. no network, etc.)
String type phone number in "quotes", in the format specified by
9.3.8
type of number
129
dial string without the international access character
145
dial string which includes the international access character "+"
+CLIR
Calling Line Identification Restriction
Description
This command enables/disables CLI to the called party, when originating a call.
Command
Possible Response
AT+CLIR=?
+CLIR: (list of supported s)
AT+CLIR?
+CLIR: ,
AT+CLIR=[]
Parameters
sets CLI status for following calls.
presentation indicator is used according to the subscription of the CLIR service.
CLIR invocation (hide)
CLIR suppression (show)
Shows the subscriber CLIR service status in the network
CLIR not provisioned
CLIR provisioned in permanent mode
unknown (e.g. no network, etc.)
CLIR temporary mode presentation restricted
CLIR temporary mode presentation allowed
GM40x GSM/GPRS Module Reference: UNDOC00048rF
64 of 176
Commands Specified by GSM 07.07
9.3.9
+COLP
Connected Line Identification Presentation
Description
COLP enables a calling subscriber to get the connected line identity (COL) of the called party after setting
up a mobile originated call.
Command
Possible Response
AT+COLP=?
+COLP: (list of supported s)
AT+COLP?
+COLP: ,
AT+COLP=[]
Intermediate result code
+COLP:,[,,
[,]]
Parameters
Sets/shows the result code presentation status in the TA
disable
enable
Shows the subscriber COLP service status in the network
COLP not provisioned
COLP provisioned
unknown (e.g. no network, etc.)
String type phone number in "brackets" of format specified by
9.3.10
Type of address octet in integer format. 145 when the dial string contains +, otherwise 129.
+CCUG
Closed User Group
Description
Allows control of the Closed User Group supplementary service.
Command
Possible Response
AT+CCUG=?
AT+CCUG?
+CCUG: ,,
AT+CCUG=[[,[,]]]
Parameters
65 of 176
disable CUG temporary mode
enable CUG temporary mode
0...9
CUG index
10
no index
no information
suppress OA
suppress preferential CUG
GM40x GSM/GPRS Module Reference: UNDOC00048rF
Commands Specified by GSM 07.07
9.3.11
suppress OA and preferential CUG
+CCFC
Call Forwarding Number and Conditions
Description
This command allows control over the call forwarding supplementary service providing, registration,
erasure, activation, deactivation and status query.
Command
Possible Response
AT+CCFC=?
+CCFC: (list of supported s)
AT+CCFC=,[,[,[,[,[,[,