g18 GSM/GPRS

OEM Embedded Module

© Motorola Communications Ltd., 2002

A subsidiary of Motorola Inc.
All rights reserved.

Developer’s Guide
98-08901C39-B
REVISION HISTORY

Revision Date Purpose

1.0 7 April 01 G18 Developer Guide first version

2.0 15 Oct 01 Update VII Customer Assistance

Update table 2 "g18 compatibility with d15" Ch. 2

"Turn On/Off timings" Ch. 3.1.2

Update "How/When to make the unit to wakeup" Ch. 3.1.3

Update "Audio levels" Ch. 3.1.6

Update "Port Configuration" at Ch. 3.1.8

Update DTR & DCD lines - Ch 3.1.9

New Chapter "Setting Baud Rate" - Ch. 3.1.10

Update "Sending Fax" Ch. 4.1.17

New Chapter "How to establish GPRS context" Ch 4.1.18

New Chapter "How to change Pin code number" Ch 4.1.19

New Chapter "How to write into the fix dialling (FD) phone book" Ch. 4.1.20

Update table 13 in "Basic AT Command list"

Update table 16 in "Advance AT command list"

Update table 23 in "ETSI 07.07 mobile equipment Control and status commands"

Update table 25 in "V.25ter commands used with GSM"

Update table 29 in "ETSI 07.05 text mode"

Update table 30 in "ETSI 07.05 PDU mode"

Update Spec. Annex B

Update Annex C. Ch. 1.1, 1.2, 1.3, 1.4, 1.8, 2.1, 2.5, 2.6, 2.7, 2.13, 2.14, 2.15, 2.16,
2.17, 2.22, 2.27, 2.37, 2.46, 2.54, 2.57, 2.58, 2.59, 2.70, 2.71, 2.72

Add in Annex E "Default Dip switch/Jumpers setting"

New Annex G "IPs over AT commands list"

98-08901C39-A 6 Mar 02 Major revision to language and format throughout

98-08901C39-B 15 Aug 02 Update book version

Update table 2 in "Differences Between the d15 and g18" with new AT commands
Update table 2 in "Differences Between the d15 and g18"

Add to section 3.2.2.1, Turning the Unit On or Off, in Design Considerations

Add note in Design Considerations, section 3.2.2.3, Turning the Unit On Using the TS
Pin
Replace sentence in Design Considerations, section 3.3.4, Analog Audio with Hands
Free

Update section 3.4.2, DTR Line and DCD LIne, in Design Considerations
Add to note in section 3.4.2, DTR Line and DCD LIne, in Design Considerations

Update section 3.4.3, Setting the Baud Rate, in Design Considerations

Add to note in section 3.5.1, SIM Card Support, in Design Considerations

Update section 4.2.1.1, Configuring Setup and Audio Routing in g18, in Software
Interface

Update note in Software Interface, section 4.2.2, Data Communication

Update table in section 4.3.1, Making a Voice Call, in Software Interface

Update table in section 4.3.2, Receiving a Voice Call, in Software Interface

Add note to section 4.3.6, Enabling Cell Broadcast (CB) Reception

Update section 4.6.8, Establishing GPRS PDP Context, in Software Interface

Add quotes in section 4.6.9, Changing the PIN Code Number, in Software Interface

Add quotes to Dn command in table 12 "Basic Call Control Commands", section 4.7
Add to S2 command in table 12 "Basic Call Control Commands"
Add to V0 command in table 12 "Basic Call Control Commands"

Update table 17 in "ETSI 07.07 Call Control Commands and Methods", section 4.10

Add error code in table 18 "ETSI 07.07 Mobile Extended Error Report", section 4.10

Update table 20 in "ETSI 07.07 Mobile Equipment Control and Status Commands",
section 4.10

Add command S94 in table 22 "V.25ter Commands Used with GSM", section 4.11
Change description of S96 command in table 22 "V.25ter Commands Used with GSM"

Update table 23 in "V.25ter Voice Commands", section 4.11

Add new chapter, MUX Integration, section 5

Update MUX Integration chapter

Update all AT Commands tables with Response/Action instead of Reaction, section 8

Update table in 8.1.2, Feedback from the System

Update table in 8.1.4, Answering a Voice Call

Update table in 8.1.7, Reading a Pone Book Entry

Update table in 8.1.9, Sending an SMS in PDU Mode

Add Read and Test commands to AT+CAOC command table, section 8.2.2

Update AT+CCFC command table and example, section 8.2.3

Update AT+CCWA Response/Action column (Execute mode description), section 8.2.4

Update +CHLD modes table in AT+CHLD command, section 8.2.5

Update AT+CLCC command table and example, section 8.2.6

Add note to AT+CLIR command, section 8.2.9

Update AT+CMGS Response/Action column in command table and add note, section
8.2.11

Add note to AT+CNUM command, and update example, section 8.2.12

Update Response/Action column in AT+COPS command table, section 8.2.13

Update AT+CPBW command example, section 8.2.15

Add AT to CSTA command table, section 8.2.18

Replace AT+CBST command table with new table and example, section 8.2.19
Update Response/Action and Remarks columns
Add to AT+CBST command note
Update At+CBST command example

Update AT+CGMI command table and example, section 8.2.20

Update AT+CGMM command table and example, section 8.2.21

Update AT+CGMR command table and example, section 8.2.22

Update AT+CGSN command table, section 8.2.23

Update AT+CHUP command table, section 8.2.24

Change AT+CMGD command table with new table, and add to note, section 8.2.25
Update Remarks in AT+CMGD command table
Update note
Replace example with new example

Update AT+CMGL command table, section 8.2.27

UPdate AT+CMGR command table, section 8.2.28

Update AT+CPMS command table and example, section 8.2.31

Update AT+CSCA command table, section 8.2.32

Change At+CSCS command table with new table, section 8.2.33

Update command example

Update AT+CSMS command table, section 8.2.34

Change AT+CSQ command table with new table and example, section 8.2.35
Update Remarks column in command table

Add note to At+CEER command, section 8.2.36

Change parameter description in Remarks column of AT+CKPD command table, section

8.2.37
Update At+CKPD command table with Test command, section 8.2.37

Update Remarks column in AT+CRC command table, and add note, section 8.2.43
Add note to AT+CNMI command, section 8.2.44
Update AT+CNMI command note and example

Update AT+CMER command table, section 8.2.46

Add note to AT+CPBF command, section 8.2.47

Add note to AT+CESP command, section 8.2.48

Replace AT+CMGW command table with new table, section 8.2.49

Update Remarks in AT+CNMA, DTE command table and fix note, section 8.2.51

Update AT+CBAUD command table, and add example, section 8.2.53

Add note to AT+CBAUD command, section 8.2.53
Add to AT+CBAUD command note, section 8.2.53

Update note in AT+CGPRS, GPRS command, section 8.2.54

Update AT+CGPADDR command (includes table, note and example), section 8.2.55

Update Response/Action column in AT+CGDCONT command, section 8.2.57

Add Remarks column to AT+CGATT, GPRS command table, section 8.2.60

Update title of AT+CIMI command, section 8.2.62

Update AT+CRSM command table, section 8.2.63

Update AT+CRTT command table, section 8.2.67

Update example

Update At+CMSS command table, section 8.2.73

Update example

Update note in AT+MMGR command, section 8.2.75

Add new AT command: At+MSCTS, Motorola Sleep CTS Control, section 8.2.77
Add example

Add new AT command: AT+CSMP, Set SMS SIM Parameters, section 8.2.78
Add example
Update AT+CSMP command table

Add new AT command: At+CSVM, Set VoiceMail Parameters, section 8.2.79

Add example
Update AT+CSVM command table

Add new AT command: AT+MFS, Motorola Frequency of Search, section 8.2.80

Add example
Update At+MFS command table

Add new AT command: AT+CSCB, Select Cell Broadcast Message Types, section
8.2.81
Add example
Update AT+CSCB command note (+CSCB Parameters)
Add new AT command: AT+MCSAT, Motorola Control SMS Alert Tone, section 8.2.82
Add example
Update AT+MCSAT command table, note and example

Add new AT command: AT+MECC, Motorola Extended Characters Check, section

8.2.83
Add example
Update example

Add new AT command: AT+CSCR, SIM Card Reader, section 8.2.84

Add example

Add new AT command: AT+MCELL, Motorola Cell Description, section 8.2.85

Add new AT command: AT+IPR, Setting and Saving the Baud Rate, section 8.2.86
Update AT+IPR command table

Add new chapter, g18 PC Loader Application, section 10

Update g18 PC Loader Application chapter
 g18 GSM/GPRS
OEM Embedded Module
Developer’s Guide

CONTENTS
REVISION HISTORY ................................................................................................................................................................ii
USING THIS GUIDE .............................................................................................................................................................. xiii
PURPOSE ................................................................................................................................................................................ xiii
INTENDED AUDIENCE........................................................................................................................................................ xiii
DISCLAIMER ......................................................................................................................................................................... xiii
REFERENCE DOCUMENTS................................................................................................................................................. xiii
CUSTOMER ASSISTANCE ...................................................................................................................................................xiv
• REGULATORY REQUIREMENTS ......................................................................................................................................xiv
• Investigate and Obtain Regulatory Approval .................................................................................................................xiv
• Full-Product Certification ................................................................................................................................................xv
• Country Requirements .....................................................................................................................................................xv
• Countries of the European Union and EFTA...................................................................................................................xv
• North American GSM Type Certification ......................................................................................................................xvi
• United States of America ................................................................................................................................................xvi
• Canada ............................................................................................................................................................................xvi
• Regulatory Statement......................................................................................................................................................xvi
7. g18 Type Certification Identifications .........................................................................................................................xvii
7. Safety............................................................................................................................................................................xvii

THE INTEGRATOR'S TASK

1.1 GENERAL..............................................................................................................................................................................1
1.2 INTRODUCTION ..................................................................................................................................................................1
1.3 PLANNING THE PRODUCT AND CREATING THE DESIGN ........................................................................................1
1.3.1 Developing a Usage Model .........................................................................................................................................1
1.3.2 Developing a Message Model .....................................................................................................................................2
1.3.3 Defining a Service Strategy.........................................................................................................................................2
1.3.4 Defining Remote Diagnostic Functionality.................................................................................................................2
1.3.5 Investigating and Obtaining Regulatory Approval .....................................................................................................3
1.4 DEVELOPING AND VALIDATING THE HARDWARE...................................................................................................3
1.4.1 Designing the Hardware Platform...............................................................................................................................3
1.4.2 Considering Power Supply Options ............................................................................................................................3
1.4.3 Selecting the Source Antenna .....................................................................................................................................3
1.4.4 Setting Up a Development Test Environment.............................................................................................................3

March 2002
© Motorola Inc., 2002 98-08901C39-B
1.5 DEVELOPING SUPPORTING APPLICATION SOFTWARE ........................................................................................... 3
1.6 TESTING AND APPROVING THE PRODUCT ................................................................................................................. 4
1.6.1 Setting Up a Final Test Environment ......................................................................................................................... 4
1.6.2 Installing and Field-Testing the Product .................................................................................................................... 4
1.7 RESOURCE ASSISTANCE.................................................................................................................................................. 4
1.7.1 Integrating Engineering Support ................................................................................................................................ 4
1.8 ENVIRONMENTAL ISSUES............................................................................................................................................... 5
1.8.1 General Precautions .................................................................................................................................................... 5
1.8.2 ESD Handling Precautions ......................................................................................................................................... 5

MODEL DESCRIPTION
2.1 GENERAL ............................................................................................................................................................................. 7
2.2 INTRODUCTION.................................................................................................................................................................. 7
2.3 BASIC MODEL OVERVIEW............................................................................................................................................... 7
2.3.1 g18 DV Slim ............................................................................................................................................................... 7
2.3.2 g18 DV Board Only – Horizontal............................................................................................................................... 8
2.3.3 g18 DVG/Slim ............................................................................................................................................................ 8
2.4 D15 AND G18 DIFFERENCES ............................................................................................................................................ 9

DESIGN CONSIDERATIONS
3.1 GENERAL ........................................................................................................................................................................... 13
3.2 POWER SUPPLY CONSIDERATIONS ............................................................................................................................ 13
3.2.1 Power Supply Losses................................................................................................................................................ 13
3.2.2 g18 Current Consumption ........................................................................................................................................ 13
3.2.3 How/When to Wake Up the Unit ............................................................................................................................. 16
3.3 AUDIO CIRCUIT CONSIDERATIONS ............................................................................................................................ 17
3.3.1 Digital Audio ............................................................................................................................................................ 17
3.3.2 Analog Audio Without Hands Free .......................................................................................................................... 18
3.3.3 Analog Audio - Levels ............................................................................................................................................. 18
3.3.4 Analog Audio With Hands Free ............................................................................................................................... 20
3.4 DATA PORT CONSIDERATIONS .................................................................................................................................... 21
3.4.1 Data Levels ............................................................................................................................................................... 21
3.4.2 DTR Line and DCD Line ......................................................................................................................................... 22
3.4.3 Setting the Baud Rate ............................................................................................................................................... 22
3.5 SIM CARD CONSIDERATIONS ....................................................................................................................................... 23
3.5.1 SIM Card Support..................................................................................................................................................... 23
3.6 ESD CONSIDERATIONS................................................................................................................................................... 23
3.7 ANTENNA CONSIDERATIONS ....................................................................................................................................... 24
3.7.1 Antenna Systems ...................................................................................................................................................... 24
3.7.2 Antenna Safety ......................................................................................................................................................... 24
3.7.3 Antenna Performance ............................................................................................................................................... 24
3.7.4 Portable Devices ....................................................................................................................................................... 24
3.7.5 Fixed Devices ........................................................................................................................................................... 25
3.7.6 Antenna Test Methods.............................................................................................................................................. 25
3.8 MECHANICS - MOUNTING THE G18............................................................................................................................. 25
3.8.1 Fixed-Mount Usage .................................................................................................................................................. 25
3.8.2 Fastening Units with Housing .................................................................................................................................. 26

ii 98-08901C39-B
 3.8.3 Fastening DIN Units..................................................................................................................................................26
3.9 CONNECTING THE M8989 HANDSET TO THE G18 ....................................................................................................26
3.10 GPS CONSIDERATIONS .................................................................................................................................................26

SOFTWARE INTERFACE
4.1 GENERAL............................................................................................................................................................................27
4.2 MODEM COMMUNICATION MODES ............................................................................................................................27
4.2.1 Voice Communication...............................................................................................................................................27
4.2.2 Data Communication.................................................................................................................................................28
4.2.3 SMS Communication ................................................................................................................................................29
4.2.4 Fax Communication ..................................................................................................................................................29
4.3 BASIC OPERATIONS.........................................................................................................................................................29
4.3.1 Making a Voice Call .................................................................................................................................................29
4.3.2 Receiving a Voice Call..............................................................................................................................................29
4.3.3 Commencing Voice Communication .......................................................................................................................30
4.3.4 Making a CSD - Data Call ........................................................................................................................................30
4.3.5 Receiving a Data Call................................................................................................................................................30
4.3.6 Enabling Cell Broadcast (CB) Reception..................................................................................................................30
4.3.7 Setting Up the g18 in CSD Mode..............................................................................................................................31
4.4 SENDING AND RECEIVING DATA IN DIFFERENT FLOW CONTROLS ..................................................................31
4.4.1 Flow Control Set to Hardware Flow Control (FC) ...................................................................................................31
4.4.2 Flow Control - Flow Control Set to Xon/Xoff..........................................................................................................31
4.4.3 Flow Control Set to None..........................................................................................................................................32
4.5 CALL WAITING, CALL FORWARDING, AND CONFERENCE CALLS .....................................................................32
4.6 SENDING AN SMS .............................................................................................................................................................32
4.6.1 Sending an SMS in PDU Mode.................................................................................................................................32
4.6.2 Sending an SMS in PDU Mode - Wave Forms.........................................................................................................34
4.6.3 Sending an SMS in CSD Mode.................................................................................................................................34
4.6.4 Receiving an SMS.....................................................................................................................................................34
4.6.5 Sending and Receiving Binary Data Via SMS..........................................................................................................35
4.6.6 Receiving an SMS in CSD Mode - Wave Forms......................................................................................................35
4.6.7 Sending a Fax ............................................................................................................................................................43
4.6.8 Establishing GPRS PDP Context ..............................................................................................................................43
4.6.9 Changing the PIN Code Number ..............................................................................................................................44
4.6.10 Writing into the Fix Dialing (FD) Phone Book.......................................................................................................44
4.7 BASIC AT COMMANDS....................................................................................................................................................45
4.8 ERROR CORRECTION AND COMPRESSION (ECC) COMMANDS ............................................................................49
4.9 FAX CLASS 1 COMMANDS .............................................................................................................................................49
4.10 ETSI 07.07 STANDARD ...................................................................................................................................................49
4.11 V.25TER COMMANDS USED WITH GSM ....................................................................................................................53
4.12 ETSI 07.05 STANDARD (SMS)........................................................................................................................................55
4.12.1 Block Mode .............................................................................................................................................................55
4.12.2 Text Mode ...............................................................................................................................................................56
4.12.3 PDU Mode...............................................................................................................................................................57

MUX INTEGRATION
5.1 GENERAL............................................................................................................................................................................59

98-08901C39-B iii
5.2 MUX INTEGRATION REQUIREMENTS......................................................................................................................... 59
5.3 MUX OPEN SERVICE ....................................................................................................................................................... 59
5.4 MUX CLOSE SERVICE ..................................................................................................................................................... 59
5.5 DATA TRANSFER ............................................................................................................................................................. 59
5.6 TWO CHANNEL LIMITATION ........................................................................................................................................ 59
5.7 SYSTEM BEHAVIOR ........................................................................................................................................................ 60
5.8 SUPPORTED PROTOCOL SERVICES ............................................................................................................................. 60
5.9 USER INTEGRATION........................................................................................................................................................ 61
5.9.1 Introduction .............................................................................................................................................................. 61

HARDWARE
6.1 GENERAL ........................................................................................................................................................................... 63
6.2 HOST INTERFACE ............................................................................................................................................................ 63
6.2.1 Modem I/O Connector.............................................................................................................................................. 63
6.2.2 Interface Cable.......................................................................................................................................................... 63
6.3 ANTENNAS ........................................................................................................................................................................ 63
6.3.1 GSM Antenna ........................................................................................................................................................... 63
6.3.2 GPS Antenna (Recommendation) ............................................................................................................................ 64
6.3.3 Antenna Connector ................................................................................................................................................... 64
6.3.4 Antenna Cable Assembly ......................................................................................................................................... 64
6.4 DEVELOPER’S KIT ........................................................................................................................................................... 64
6.5 VENDOR CONTACTS ....................................................................................................................................................... 64

TESTING
7.1 GENERAL ........................................................................................................................................................................... 69
7.2 TESTING STAGES ............................................................................................................................................................. 69
7.2.1 Hardware Integration ................................................................................................................................................ 69
7.2.2 Desense and EMI...................................................................................................................................................... 70
7.2.3 Regulatory Compliance ............................................................................................................................................ 70
7.2.4 Application Software ................................................................................................................................................ 70
7.2.5 Final Assembly ......................................................................................................................................................... 71
7.2.6 End User Problem Resolution .................................................................................................................................. 71
7.2.7 OEM Service Depot Repair ...................................................................................................................................... 71
7.3 DIAGNOSTIC UTILITY..................................................................................................................................................... 71
7.3.1 Quality Assurance Testing........................................................................................................................................ 71
7.3.2 Equipment Test Set-up ............................................................................................................................................. 72

AT COMMANDS
8.1 BASIC FUNCTIONALITY ................................................................................................................................................. 73
8.1.1 PIN and PUK Code Entry........................................................................................................................................ 73
8.1.2 Feedback from the System ...................................................................................................................................... 74
8.1.3 Establishing a Voice Call ........................................................................................................................................ 75
8.1.4 Answering a Voice Call........................................................................................................................................... 76
8.1.5 Finding a Phone Book Entry ................................................................................................................................... 76
8.1.6 Writing a Phone Book Entry ................................................................................................................................... 77
8.1.7 Reading a Phone Book Entry................................................................................................................................... 77
8.1.8 Phone Book Function .............................................................................................................................................. 77

iv 98-08901C39-B
 8.1.9 Sending an SMS in PDU Mode................................................................................................................................78
8.1.10 Establishing GPRS PDP Context ...........................................................................................................................78
8.2 AT COMMAND LISTING ..................................................................................................................................................80
8.2.1 ATD, Dialing............................................................................................................................................................80
8.2.2 AT+CAOC, Charge Advice ....................................................................................................................................81
8.2.3 AT+CCFC, Call Forwarding Number and Conditions ............................................................................................82
8.2.4 AT+CCWA, Call Waiting........................................................................................................................................83
8.2.5 AT+CHLD, Call Related Supplementary Services..................................................................................................84
8.2.6 AT+CLCC, List Current Calls .................................................................................................................................89
8.2.7 AT+CLCK, Facility Lock ........................................................................................................................................91
8.2.8 AT+CLIP, Calling Line Identification Presentation ................................................................................................92
8.2.9 AT+CLIR, Calling Line Identification Restriction ..................................................................................................93
8.2.10 AT+CMEE, Report Mobile Equipment ................................................................................................................94
8.2.11 AT+CMGS, Sending an SMS Message .................................................................................................................95
8.2.12 AT+CNUM, Subscriber Number ...........................................................................................................................96
8.2.13 AT+COPS, Operator Selection ..............................................................................................................................97
8.2.14 AT+CPBS, Selected Phone Book Memory Storage ..............................................................................................99
8.2.15 AT+CPBW, Writing Phone Book Entries ...........................................................................................................101
8.2.16 AT+CPIN, Enter Pin ............................................................................................................................................103
8.2.17 AT+CREG, Network Registration .......................................................................................................................105
8.2.18 AT+CSTA, Selecting Type of Address ...............................................................................................................106
8.2.19 AT+CBST, Selecting Bearer Service Type .........................................................................................................107
8.2.20 AT+CGMI, Requesting Manufacturer Identification ..........................................................................................108
8.2.21 AT+CGMM, Requesting Model Identification....................................................................................................109
8.2.22 AT+CGMR, Requesting Revision Identification.................................................................................................109
8.2.23 AT+CGSN, Requesting Product Serial Number Identification ...........................................................................110
8.2.24 AT+CHUP, Hanging Up Calls.............................................................................................................................110
8.2.25 AT+CMGD, Deleting SMS Messages .................................................................................................................111
8.2.26 AT+CMGF, Message Format ..............................................................................................................................113
8.2.27 AT+CMGL, Listing Messages.............................................................................................................................114
8.2.28 AT+CMGR, Reading Messages...........................................................................................................................115
8.2.29 AT+CPAS, Phone Activity Status .......................................................................................................................115
8.2.30 AT+CPBR, Reading Phone Book Entries............................................................................................................116
8.2.31 AT+CPMS, Preferred Message Storage ..............................................................................................................117
8.2.32 AT+CSCA, Service Center Address ....................................................................................................................118
8.2.33 AT+CSCS, Selecting TE Character Set ...............................................................................................................119
8.2.34 AT+CSMS, Selecting the Message Service.........................................................................................................120
8.2.35 AT+CSQ, Signal Quality .....................................................................................................................................121
8.2.36 AT+CEER, Extended Error Report......................................................................................................................121
8.2.37 AT+CKPD, Keypad Control ................................................................................................................................123
8.2.38 AT+FCLASS, Selecting a Mode..........................................................................................................................124
8.2.39 AT+GCAP, Requesting Complete Capabilities List............................................................................................124
8.2.40 AT+CMOD, Calling Mode .................................................................................................................................125
8.2.41 AT+CRLP, Radio Link Protocol .........................................................................................................................126
8.2.42 AT+CR, Service Reporting Control ....................................................................................................................126
8.2.43 AT+CRC, Cellular Result Codes .........................................................................................................................127
8.2.44 AT+CNMI, New Message Indications to TE+CNMI..........................................................................................128
8.2.45 AT+CMEC, Mobile Equipment Control Mode ..................................................................................................130
8.2.46 AT+CMER, Mobile Equipment Event Reporting ..............................................................................................131

98-08901C39-B v
 8.2.47 AT+CPBF, Finding Phone Book Entries ............................................................................................................ 132
8.2.48 AT+CESP, Entering SMS Block Mode .............................................................................................................. 134
8.2.49 AT+CMGW, Writing Messages in PDU Mode .................................................................................................. 134
8.2.50 AT+CTFR1, Diverting an Incoming Call to the Voice Mail .............................................................................. 135
8.2.51 AT+CNMA, DTE Confirming the Previous Message ........................................................................................ 135
8.2.52 AT+CBAND, Changing Band............................................................................................................................. 136
8.2.53 AT+CBAUD, Setting the Baud Rate................................................................................................................... 137
8.2.54 AT+CGPRS, GPRS Coverage............................................................................................................................. 138
8.2.55 AT+CGPADDR, Showing the PDP Address ...................................................................................................... 139
8.2.56 AT+CGCLASS, GPRS MS Class ....................................................................................................................... 140
8.2.57 AT+CGDCONT, Defining the PDP Context ...................................................................................................... 141
8.2.58 AT+CGQMIN, Quality of Service Provider ....................................................................................................... 142
8.2.59 AT+CGACT, PDP Context Activation/Deactivation Request............................................................................ 143
8.2.60 AT+CGATT, GPRS Attach/Detach Request ...................................................................................................... 144
8.2.61 AT+CGQREQ, Defining/Modifying/Removing a Requested Quality of Service Profile .................................. 145
8.2.62 AT+CIMI, Requesting International Mobile Subscriber Identity (IMSI) ........................................................... 146
8.2.63 AT+CRSM, Restricting SIM Access................................................................................................................... 147
8.2.64 AT+CPOL, Preferred Operator List .................................................................................................................... 148
8.2.65 AT+CIPE, ENABLE +CIP AT Command.......................................................................................................... 149
8.2.66 AT+CIP, IP Primitive Over AT Command ......................................................................................................... 149
8.2.67 AT+CRTT, Selecting the Ring Tone .................................................................................................................. 150
8.2.68 AT+CPWD, Changing the Password ................................................................................................................. 151
8.2.69 Fax AT Commands.............................................................................................................................................. 151
8.2.70 AT+MTDTR, DTR Line Test Command............................................................................................................ 152
8.2.71 AT+MTCTS, CTS Line Test Command ............................................................................................................. 152
8.2.72 AT+MCWAKE, DTE Wake Line Control Command ....................................................................................... 153
8.2.73 AT+CMSS, Send Message from Storage ............................................................................................................ 153
8.2.74 AT+MMGL, Message List ................................................................................................................................. 154
8.2.75 AT+MMGR, Read Message................................................................................................................................ 154
8.2.76 AT+MMGA, Changing the Message Attributes ................................................................................................. 155
8.2.77 AT+MSCTS, Motorola Sleep CTS Control ........................................................................................................ 155
8.2.78 AT+CSMP, Set SMS SIM Parameters ................................................................................................................ 157
8.2.79 AT+CSVM, Set VoiceMail Parameters .............................................................................................................. 159
8.2.80 AT+MFS, Motorola Frequency of Search........................................................................................................... 161
8.2.81 AT+CSCB, Select Cell Broadcast Message Types ............................................................................................. 162
8.2.82 AT+MCSAT, Motorola Control SMS Alert Tone .............................................................................................. 166
8.2.83 AT+MECC, Motorola Extended Characters Check ............................................................................................ 168
8.2.84 AT+CSCR, SIM Card Reader ............................................................................................................................. 169
8.2.85 AT+MCELL, Motorola Cell Description ............................................................................................................ 169
8.2.86 AT+IPR, Setting and Saving the Baud Rate........................................................................................................ 171
8.2.87 AT+PT42 ............................................................................................................................................................. 172
8.2.88 AT+CMUX, Multiplexing Mode ........................................................................................................................ 172

G18 EVALUATION BOARD

9.1 GENERAL ......................................................................................................................................................................... 173
9.2 EV BOARD ISSUE P4 ...................................................................................................................................................... 173
9.2.1 Connector Description ............................................................................................................................................ 174
9.2.2 Jumper Description................................................................................................................................................. 175
9.3 EV BOARD ISSUE P5 ...................................................................................................................................................... 176

vi 98-08901C39-B
 9.3.1 Connector Description.............................................................................................................................................177
9.3.2 S3 Dip Switch Description......................................................................................................................................179

G18 PC LOADER APPLICATION

10.1 GENERAL........................................................................................................................................................................181
10.2 APPLICATION OPTIONS ..............................................................................................................................................181
10.2.1 Setting....................................................................................................................................................................181
10.2.2 Programming.........................................................................................................................................................183

SPECIFICATIONS
A.1 GENERAL .........................................................................................................................................................................187
A.2 MODEL SPECIFICATIONS.............................................................................................................................................188
A.3 PIN DESCRIPTIONS ........................................................................................................................................................190
A.4 SLIM CONNECTIVITY OPTIONS .................................................................................................................................191
A.5 SLIM AND GPS CONNECTIVITY OPTIONS ...............................................................................................................192
A.6 DIN CONNECTIVITY OPTIONS....................................................................................................................................192
A.7 MECHANICAL SPECIFICATION DIAGRAMS ............................................................................................................192
A.8 LANGUAGE SUPPORT...................................................................................................................................................194

QUICK START
B.1 POWER CONNECTIONS.................................................................................................................................................197
B.2 G18 CONNECTIONS........................................................................................................................................................197
B.3 CUSTOMER CONNECTIONS.........................................................................................................................................197
B.4 AUDIO CONNECTIONS..................................................................................................................................................197
B.5 SIM CONNECTIONS .......................................................................................................................................................197
B.6 BAND SELECTIONS .......................................................................................................................................................197
B.7 RS232 CONNECTIONS....................................................................................................................................................197
B.8 ANTENNA CONNECTIONS ...........................................................................................................................................197
B.9 DEFAULT DIP SWITCH/JUMPER SETTINGS .............................................................................................................198

DESENSE
C.1 GENERAL .........................................................................................................................................................................199
C.2 DESENSE DEFINED ........................................................................................................................................................199
C.2.1 Noise Sources .........................................................................................................................................................199
C.2.2 Receiver Susceptibilities.........................................................................................................................................200
C.3 MEASUREMENT TECHNIQUES ...................................................................................................................................200
C.3.1 Packet Modem Integration Tester (PMIT) .............................................................................................................200
C.3.2 Alternate Measurement Method .............................................................................................................................201
C.3.3 Preparing the Device Under Test............................................................................................................................201
C.4 PERFORMANCE GOALS ................................................................................................................................................201
C.4.1 Radio Performance Capabilities .............................................................................................................................201
C.4.2 Determine Emission Level Goals ...........................................................................................................................202
C.5 ACCEPTANCE ANALYSIS ON A SAMPLE DATA SET .............................................................................................202
C.6 PREDICTION OF SOURCES ...........................................................................................................................................202
C.6.1 Probability of Channel Interference .......................................................................................................................203
C.6.2 Desense Scenarios ..................................................................................................................................................203

98-08901C39-B vii
C.7 METHODS OF CONTROLLING EMISSIONS .............................................................................................................. 203
C.7.1 Shielding Approach ............................................................................................................................................... 203
C.7.2 Alternate EMI Reduction Methods ........................................................................................................................ 204
C.8 RF NETWORK ISSUES ................................................................................................................................................... 204
C.9 ANTENNA........................................................................................................................................................................ 205
C.9.1 Field Strengths from the Antenna .......................................................................................................................... 205
C.9.2 Antenna Interactions .............................................................................................................................................. 205
C.9.3 Antenna Cable Routing.......................................................................................................................................... 205
C.10 DESENSE SUMMARY .................................................................................................................................................. 205

IP OVER AT COMMANDS LIST

D.1 GENERAL ........................................................................................................................................................................ 207
D.2 ENABLE IP OVER AT SERVICES +CIPE..................................................................................................................... 207
D.3 DSC BUS IP PRIMITIVE OVER AT SERVICES +CIP ................................................................................................. 207
D.4 IP PRIMITIVES SUPPORTED BY CIP .......................................................................................................................... 209
D.5 REQUEST/CONFIRM PRIMITIVES .............................................................................................................................. 209
D.6 UNSOLICITED PRIMITIVES ......................................................................................................................................... 209
D.7 IP PRIMITIVES CIP SPECIFICATIONS ........................................................................................................................ 210
D.7.1 Class Indicator Primitives...................................................................................................................................... 210
D.7.2 Power Down Primitives ......................................................................................................................................... 213
D.7.3 Phone Book Related Primitives ............................................................................................................................. 213
D.7.4 Display Indicator Primitives .................................................................................................................................. 215
D.7.5 Call Control Interface Primitives........................................................................................................................... 216
D.7.6 Call Status Indication Primitives ........................................................................................................................... 216
D.7.7 Generate DTMF Signalling Primitives .................................................................................................................. 218
D.7.8 Hook-switch Status Indicator Primitives ............................................................................................................... 219
D.7.9 Microphone Mute Primitives ................................................................................................................................ 221
D.7.10 SEEM Interface Primitives .................................................................................................................................. 221
D.7.11 Idle SIM Card Notification Primitives ................................................................................................................ 223
D.7.12 SIM Card Deactivation Notification.................................................................................................................... 223
D.7.13 SIM Card Activation Notification Primitives...................................................................................................... 224
D.7.14 SIM Card Security Notifications ......................................................................................................................... 224
D.7.15 Attached Peripherals Primitives .......................................................................................................................... 228
D.7.16 IP_HF_AUDIO_STATUS_IND.......................................................................................................................... 229
D.7.17 IP_SET_RING_LEVEL_REQ ............................................................................................................................ 230
D.7.18 IP_SET_RING_LEVEL_CNF ............................................................................................................................ 230
D.7.19 IP_LOW_VOLTAGE_IND................................................................................................................................. 231
D.7.20 IP_GET_HF_VOLUME_REQ........................................................................................................................... 231
D.7.21 IP_GET_HF_VOLUME_CNF ............................................................................................................................ 231
D.7.22 IP_LTC_ERASED_IND...................................................................................................................................... 232
D.8 IP PRIMITIVES CIP EXAMPLES................................................................................................................................... 232

GLOSSARY
E.1 GENERAL......................................................................................................................................................................... 241
E.2 SHORT MESSAGE SERVICE ABBREVIATIONS........................................................................................................ 243

INDEX

viii 98-08901C39-B
 LIST OF FIGURES
Figure 1. Integrator’s Tasks ..........................................................................................................................................................1
Figure 2. g18 DV Slim Data Module............................................................................................................................................7
Figure 3. g18 DV Board Only – Horizontal Connection ..............................................................................................................8
Figure 4. g18 DV GPS Data Module ............................................................................................................................................8
Figure 5. The VCC Signal During TX Periods...........................................................................................................................13
Figure 6. Turning On the Unit Using the On/Off Pin .................................................................................................................14
Figure 7. Turning On and Off the Unit Using the ON/OFF Pin .................................................................................................14
Figure 8. Turning the Unit On Using the TS Line......................................................................................................................14
Figure 9. DTR/DSR During Ton ................................................................................................................................................15
Figure 10. RTS/CTS During Ton ...............................................................................................................................................15
Figure 11. DCD/RI During Ton..................................................................................................................................................15
Figure 12. TXD/RXD During Ton .............................................................................................................................................15
Figure 13. Sleep Mode Timing ...................................................................................................................................................16
Figure 14. Wake the g18 When the DTE Wants to Send Data...................................................................................................16
Figure 15. Wake the DTE When Data is Present Using the Wake up Line ...............................................................................17
Figure 16. Wake Up the DTE when the Unit Goes from a State of Non-GPRS Coverage to GPRS Coverage ........................17
Figure 17. Wake Up Internal Connections .................................................................................................................................17
Figure 18. Ground Connections..................................................................................................................................................18
Figure 19. g18 Input Maximum Level........................................................................................................................................18
Figure 20. Input Maximum Level and BS Detected Signal........................................................................................................18
Figure 21. Gcap Amplifier Gain Response.................................................................................................................................19
Figure 22. g18 Analog Audio Frequency Response (Audio Out Pin) ........................................................................................19
Figure 23. EV Audio Block Diagram .........................................................................................................................................20
Figure 24. DTE Connection to g18 (DCE Device) (User Connector 36 Pin ZIF)......................................................................21
Figure 25. DTE Connection to g18 (User Connector 28 Pin DIN) ............................................................................................21
Figure 26. DCE Connection to g18 (DCE Device) (User Connector 36 Pin ZIF) .....................................................................21
Figure 27. DCE Connection to g18 (User Connector 28 Pin DIN) ............................................................................................22
Figure 28. The SIM Card Interface.............................................................................................................................................23
Figure 29. Mounting the Modem (Front View) ..........................................................................................................................26
Figure 30. Mounting the Modem (Rear View) ...........................................................................................................................26
Figure 31. Handset Connections / Hardware Required ..............................................................................................................26
Figure 32. RI Waveform .............................................................................................................................................................31
Figure 33. g18 Receiving a Data Call.........................................................................................................................................31
Figure 34. g18 Sending Data Hardware Flow Control ...............................................................................................................31
Figure 35. g18 Receiving Data Hardware Flow Control ............................................................................................................31
Figure 36. Sending Data Xon/Xoff.............................................................................................................................................32
Figure 37. g18 Receiving Data Xon/Xoff...................................................................................................................................32
Figure 38. Sending Data in None FC..........................................................................................................................................32
Figure 39. g18 Receiving Data in None FC................................................................................................................................32
Figure 40. Sending an SMS ........................................................................................................................................................34
Figure 41. Receiving an SMS .....................................................................................................................................................35
Figure 42. Mux Architecture ......................................................................................................................................................61
Figure 43. g18 Setup for Testing ................................................................................................................................................72
Figure 44. EV Board P4 - Front................................................................................................................................................174
Figure 45. EV Board P4 - Back ................................................................................................................................................174
Figure 46. SIM Card Interface ..................................................................................................................................................175

98-08901C39-B ix
Figure 47. EV Board P5 - Front ............................................................................................................................................... 176
Figure 48. EV Board P5 - Back................................................................................................................................................ 177
Figure 49. Dip Switch Description........................................................................................................................................... 179
Figure 50. Setting Page ............................................................................................................................................................ 181
Figure 51. Applying Pop-up Approval Message...................................................................................................................... 182
Figure 52. Set Default Pop-up Approval Message................................................................................................................... 182
Figure 53. Programming Page.................................................................................................................................................. 183
Figure 54. Image File Selection via Browse Button ................................................................................................................ 183
Figure 55. Testing Report Log Activated via Test Button ....................................................................................................... 184
Figure 56. Start Programming Pop-up Approval Message ...................................................................................................... 184
Figure 57. Programming Message in Earlier g18 Versions ..................................................................................................... 185
Figure 58. Programming Log in Programming Status Report ................................................................................................. 185
Figure 59. Programming Complete Message........................................................................................................................... 186
Figure 60. Slim Version .......................................................................................................................................................... 187
Figure 61. Slim with GPS Version........................................................................................................................................... 187
Figure 62. DIN Version............................................................................................................................................................ 187
Figure 63. Data and Voice (Slim) - Connections ..................................................................................................................... 191
Figure 64. Data and Voice and GPS Model Connections ........................................................................................................ 192
Figure 65. Data and Voice in DIN Configuration Connections ............................................................................................... 192
Figure 66. g18 DV Slim ........................................................................................................................................................... 192
Figure 67. g18 DV Slim with GPS........................................................................................................................................... 193
Figure 68. g18 DV DIN Horizontal ......................................................................................................................................... 194
Figure 58. Wanted and Unwanted Signal Levels ..................................................................................................................... 199
Figure 59. EMI in a Portable Computer Platform .................................................................................................................... 200
Figure 60. PMIT Hardware Facility ......................................................................................................................................... 200
Figure 61. Typical PMIT Plot .................................................................................................................................................. 200
Figure 62. Spectrum Analyzer Setup ....................................................................................................................................... 201
Figure 63. Sample Data Set...................................................................................................................................................... 202
Figure 64. Clock Pulling .......................................................................................................................................................... 204

x 98-08901C39-B
 LIST OF TABLES
Table 1. Parts and Tools Requirements ........................................................................................................................................4
Table 2. Differences Between the d15 and g18 ............................................................................................................................9
Table 3. g18 Current Consumption.............................................................................................................................................13
Table 4. g18 Rx Audio Levels ....................................................................................................................................................19
Table 5. Rx Audio Levels vs. Different Signals in the BS .........................................................................................................19
Table 6. g18 Rx Audio Levels with ATS96=1 ...........................................................................................................................20
Table 7. External Drivers and Audio Device Requirements.......................................................................................................20
Table 8. The GPS Lines in the g18 (User Connector 36 Pin Zif Socket) ...................................................................................26
Table 9. Voice Connectivity .......................................................................................................................................................28
Table 10. Regular (HS) and HF Mode using RS232 ..................................................................................................................28
Table 11. Features Supported using CSD/GPRS........................................................................................................................29
Table 12. Basic Call Control Commands (Including V.25ter) ...................................................................................................45
Table 13. Advanced AT Commands List ...................................................................................................................................48
Table 14. Supported ECC Commands List................................................................................................................................49
Table 15. FAX Class Commands ...............................................................................................................................................49
Table 16. General ETSI 07.07 Commands .................................................................................................................................49
Table 17. ETSI 07.07 Call Control Commands and Methods ....................................................................................................50
Table 18. ETSI 07.07 Mobile Extended Error Report ................................................................................................................50
Table 19. ETSI 07.07 Network Service Related Commands .....................................................................................................51
Table 20. ETSI 07.07 Mobile Equipment Control and Status Commands................................................................................51
Table 21. ETSI 07.07 Mobile Equipment Errors and Status Reports.........................................................................................52
Table 22. V.25ter Commands Used with GSM ..........................................................................................................................53
Table 23. V.25ter Voice Commands ..........................................................................................................................................54
Table 24. ETSI 0705 TE Commands Sent from Host to Phone .................................................................................................55
Table 25. ETSI07.05 MT Responses Sent from Phone to Host .................................................................................................55
Table 26. ETSI 07.05 Text Mode ...............................................................................................................................................56
Table 27. ETSI 0705 PDU Mode................................................................................................................................................57
Table 28. ETSI 07.07 Commands for GPRS ..............................................................................................................................58
Table 29. External Screen Information.....................................................................................................................................170
Table 30. SIM Card Pin Functions ...........................................................................................................................................175
Table 31. J114 Functions ..........................................................................................................................................................175
Table 32. SIM Card Pin Functions ...........................................................................................................................................178
Table 33. P11 Functions ...........................................................................................................................................................178
Table 34. Interface Connector, 36 Pin Description Standard, Slim, Slim with GPS and DIN Horizontal...............................190
Table 35. Interface Connector, 28 Pin Description DIN Models .............................................................................................190
Table 36. Standard, Slim, Slim with GPS and DIN Horizontal Model Functions Available on 36 Pin ZIF ...........................191
Table 37. DIN and Horizontal Model Functions Available on 28 Pin ZIF ..............................................................................191
Table 39. IP_CLASS_IND Parameters ....................................................................................................................................210
Table 40. IP_STOP_REQ Parameters ......................................................................................................................................213
Table 41. IP_PD_USAGE_IND Parameters ............................................................................................................................213
Table 42. IP_ABBR_DIAL_TBL_IND Parameters .................................................................................................................214
Table 43. IP_INDR_CTRL_STATE_IND Parameters ............................................................................................................215
Table 44. IP_CALL_STATUS_IND Parameters .....................................................................................................................217
Table 45. IP_CALL_DTMF_REQ Parameters ........................................................................................................................219
Table 46. IP_HOOKSWITCH_IND Parameters ......................................................................................................................219
Table 47. IP_MUTE_REQ Parameters.....................................................................................................................................221

98-08901C39-B xi
Table 48. IP_MUTE_IND Parameters ..................................................................................................................................... 221
Table 49. SIM Card Status ....................................................................................................................................................... 222
Table 50. SEEM_ACTIVATE_IND Parameters ..................................................................................................................... 223
Table 51. SEEM_DEACTIVATE_IND Parameters ................................................................................................................ 223
Table 52. SEEM_ACTIVATE_CNF Parameters..................................................................................................................... 224
Table 53. SEEM_STATUS_CNF Parameters ......................................................................................................................... 224
Table 54. SEEM_PIN_VERIFY_CNF Parameters.................................................................................................................. 225
Table 55. SEEM_UNBLOCKING_CNF Parameters .............................................................................................................. 225
Table 56. SEEM_PIN_DISABLE_CNF Parameters ............................................................................................................... 226
Table 57. SEEM_PIN_ENABLE_CNF Parameters ................................................................................................................ 226
Table 58. SEEM_PIN_CHANGE_CNF Parameters ............................................................................................................... 227
Table 59. SEEM_CARD_STATUS_IND Parameters ............................................................................................................. 227
Table 60. IP_NUM_OF_ATTACHED_PERIPHERALS_IND Parameters............................................................................ 228
Table 61. IP_ATTACHED_PERIPHERALS_INFO_IND Parameters ................................................................................... 229
Table 62. IP_HF_AUDIO_STATUS_IND Parameters ........................................................................................................... 230
Table 63. IP_SET_RING_LEVEL_REQ Parameters.............................................................................................................. 230
Table 64. IP_SET_RING_LEVEL_CNF Parameters .............................................................................................................. 230
Table 65. IP_LOW_VOLTAGE_IND Parameters .................................................................................................................. 231
Table 66. IP_GET_HF_VOLUME_REQ Parameters ............................................................................................................. 231
Table 67. IP_GET_HF_VOLUME_CNF Parameters.............................................................................................................. 231
Table 68. IP_LTC_ERASED_IND Parameters ....................................................................................................................... 232
Table 69. IP_CALL_STATUS_IND Ref. GSM-IP 7.3 ........................................................................................................... 232
Table 70. INDR_CTRL_STATE_IND Ref. GSM-IP 6.14...................................................................................................... 233
Table 71. IP_STOP_REQ Ref. GSM-IP 6.6. ........................................................................................................................... 233
Table 72. ATTACHED_PERIPHERALS_IND Ref. GSM-IP 10.2. ....................................................................................... 233
Table 73. HF_AUDIO_STATUS_IND Ref. GSM-IP 10.4. .................................................................................................... 234
Table 74. LTC_ERASED_IND Ref. GSM-IP10.11. ............................................................................................................... 234
Table 75. SEEM_CARD_STATUS_IND Ref. GSM-IP 10.3. ................................................................................................ 234
Table 76. SEEM_ACTIVATE_IND Ref. GSM-IP 9.1............................................................................................................ 235
Table 77. SEEM_ACTIVATE_IND Ref. GSM-IP 9.3............................................................................................................ 235
Table 78. SEEM_DEACTIVATE_IND Ref. GSM-IP 9.2. ..................................................................................................... 235
Table 79. SEEM_PIN_CHANGE_CNF Ref. GSM-IP 9.4...................................................................................................... 236
Table 80. SEEM_PIN_DISABLE_CNF Ref. GSM-IP 9.4...................................................................................................... 236
Table 81. SEEM_PIN_ENABLE_CNF Ref. GSM-IP 9.4....................................................................................................... 237
Table 82. SEEM_PIN_VERIFY_CNF Ref. GSM-IP 9.4. ....................................................................................................... 237
Table 83. SEEM_STATUS_CNF Ref. GSM-IP 9.4................................................................................................................ 238
Table 84. SEEM_UNBLOCKING_CNF Ref. GSM-IP 9.4..................................................................................................... 238
Table 85. IP MUTE Ref. GSM-PCN.8.3. ................................................................................................................................ 238
Table 86. IP CALL DTMF Ref. GSM-PCN.7.7 ...................................................................................................................... 239
Table 87. IP ERROR Ref. GSM 07.07.7.10. ......................................................................................................................... 239
Table 88. IP GET HF VOLUME Ref. GSM-IP 10.8............................................................................................................... 239

xii 98-08901C39-B
USING THIS GUIDE
This guide presents critical research and development issues
affecting the design and development of products
incorporating the Motorola g18 900/1800/1900MHz
GSM/GPRS Integrated Wireless Modem, used in North
America, Asia, Africa and Europe.
The purpose of this document is to describe the technical
details needed to integrate g18 Tri-band 900, 1800 and 1900
MHz Data Module into a host device. The g18 Data Module
is the next generation that replaces the current d15 Data
Module. There are several configurations of this product that
provide flexibility in meeting full system integration
requirements, as described in this manual.
A product that incorporates the modem is
referred to as the Original Equipment
Manufacturer (OEM) host or simply the host.
Note
PURPOSE
Data terminal equipment (DTE) OEM teams are often pulled
together quickly from other work groups. For this reason,
OEM team members often need advice about how to best
sustain a concerted design and development effort. The
purpose of this guide is to assist your team to successfully
produce a wireless product that integrates the Motorola g18
wireless modem.
This guide strives to bridge the gap between the various
engineering and business disciplines that make up OEM
teams. Our approach is to provide a practical disclosure of
useful information that can offer a common understanding of
the problems you may encounter and examples of probable
solutions.
We at Motorola want to make this guide as helpful as
possible. Keep us informed of your comments and
suggestions for improvements. You can reach us by email at:
GSM support-BSH015@email.mot.com
INTENDED AUDIENCE
The intended audience of this manual are data terminal
equipment (DTE) OEM integration team members. Teams
historically consist of representatives from the disciplines of
hardware, software and RF engineering. These readers will
probably find the entire document useful, if not enlightening.
Other readers include marketing, business, and program
managers. These readers might find the first chapter, which
discusses the integrator’s task, to be sufficiently informative
for their needs. The remaining chapters go into more detail.
98-08901C39-B
DISCLAIMER
This guide provides advice and guidelines to OEM teams.
Responsibility regarding how the information is used lies
entirely with the OEM. Statements indicating support
provided by, or offered by, Motorola are subject to change at
any time.
Motorola reserves the right to make any changes to this
manual.
REFERENCE DOCUMENTS
Electromagnetic Compatibility: Principles and Applications
by David A Weston, published by Marcel Dekker, Inc., 270
Madison Avenue, New York, NY 10016 USA.
GSM 07.07 - prETS 300 916, Digital cellular
telecommunication system (Phase 2+); AT command set for
GSM Mobile Equipment (ME), Version 5.2.0 or higher,
Reference RE/SMG-040707QR1.
GSM 07.05, Digital cellular telecommunication system
(Phase 2+); Use of Data Terminal Equipment - Data Circuit
terminating; Equipment (DTE-DCE) interface for Short
Message Service (SMS) and Cell Broadcast Service (CBS),
Version 5.3.0, August, 1997, Reference
TS/SMG-040705QR2.
GSM 03.40, Digital cellular telecommunication system
(Phase 2+); Technical realization of the Short Message
Service (SMS) Point-to-Point (PP), Version 5.3.0, July
1996, Reference TS/SMG-040340QR2.
GSM 04.11 Digital cellular telecommunication system
(Phase 2+); Point-to-Point (PP) Short Message Service
(SMS) support on mobile radio interface, Version 5.1.0,
March 1996, Reference TS/SMG-030411QR.
GSM 03.38, Digital cellular telecommunication system
(Phase 2+); Alphabets and language-specific information,
Version 5.3.0, July 1996, Reference TS/SMG-040338QR2.
GSM 11.10-1, Digital cellular telecommunication system
(Phase 2); Mobile Station (MS) Conformance specification;
Part 1: Conformance specification. Draft pr ETS 300 607-1,
March 1998, Reference RE/SMG-071110PR6-1.
GSM Specifications are orderable from Global Engineering
Documents, 15 Inverness Way East, Englewood, Colorado
80112-5704 USA 303-792-2181 800-624-3974.
ETSI Standard PCS - 11.10-1.
GSM 02.30 Supplementary services.
GSM 03.90 USSD stage 2.
GSM 11.14 SIM toolkit.
ITU-T V.25ter
xiii
GSM Data Adapter for Motorola Handsets, AT command People’s Republic of China (10) 6846-6060
reference, Rev 2, June 9 1997.
Portugal (21) 318-0051
ETSI standard SMG31.
Singapore 485-5333
GSM 05.02.
Sweden (08) 445-1210
ETSI 07.60.
Switzerland 0800 553-109
ETSI 0.7.07 Ver. 7.5.0.
UK 0500 55 55 55
United States of America 1 (800) 331-6456
CUSTOMER ASSISTANCE Accessory Items Available to Aid the Developer
This page is to be used as a source of contact information for Developer Kit S9002x
any possible queries that may arise.
Handset with SIM CR SCN50011x
• Have questions?
Handset without SIM CR SCN50012x
• Trouble getting the evaluation board set up?
• Technical questions? Headset SYN6962
• Configuration questions/problems? Headset SYN4937
• Technical operating problems? Microphone SMN4097
• Need documentation?
Speaker SNN4018
The GSM Data Module Customer Support Center is ready to
assist you on integration issues. GPRS Manager SVN4503

• The help desk phone number is: +972 (0) 3 568-4040 Short Flex Cable 50mm 3086229J10
• Email: BSH015@email.mot.com Long Flex Cable 300mm 3086229J09
At Motorola, total customer satisfaction is a top priority. If Coax Cable 200mm (MMCX/SMA) 3085720G01
you have a question, a suggestion or a concern about your
Motorola g18 product, we would like to hear from you. If you wish to place an order, please contact your Account
Manager. A list of Motorola Account Managers is available
Please contact the Motorola Cellular Response Center by fax at www.motorola.com/automotive/telematics/. Click
on +44 (0) 131 458-6732 or use one of the local phone Products > Data Modules > Contact Us.
numbers in the following countries for general product
inquiries.
Austria 0800 297-246 REGULATORY REQUIREMENTS
Belgium 0800 72-370
Canada 1 (800) 461-4575 Investigate and Obtain Regulatory Approval
Denmark 4348-8005
Most countries where the final product will be sold currently
Finland 0800 117-036 require approval from the local government regulatory body.
France 0 803 303-302 It is your responsibility to investigate and obtain the proper
regulatory approval and certification for each country in
Hong Kong 2506-3888 which the product is sold. Motorola can provide the contact
Ireland (01) 402-6887 names and phone numbers of the regulatory bodies in each
country.
Italy (02) 696-333-16
You are required to obtain regulatory approval of products
Luxembourg 0800 21 99 that integrate a g18 integrated wireless modem. The specific
Netherlands 0800 022 27 43 details for achieving regulatory approval may vary from
country to country.
Norway 22 55 10 04

xiv
98-08901C39-B
Worldwide, government regulatory agencies for
communications have established standards and
requirements for products that incorporate fixed, mobile,
and portable radio transmitters. To this end, Motorola
provides g18 modems as certified in specific regional
markets to levels of compliance appropriate for an integrated
device. Approval is required for two interrelated reasons, to
guard public safety and to ensure electrical non-interference.
UL, CSA, and other safety approvals are not required. In
Australia, AUSTEL safety approval is required of network
operators, meaning that the network operators might pass
AUSTEL safety requirements through to the device
integrators.
Full-Product Certification
As the integrator, you must determine what additional
specific regulatory requirements are required of the country
in which your product is marketed. This means that your
product must be individually certified, even though the g18
modems are already approved. The certification process
includes submittal of prototype products and acceptable test
results.
The certification process for your product can take from a
few weeks to several months. Its duration can be affected by
safety requirements, the type of product, and the country in
which you are seeking approval.
Country Requirements
These country requirements are provided as a general
orientation to the certification processes in specific regions
and countries. You are strongly encouraged to use the
services of a consultant or a full-service test house if you
have limited expertise in meeting the regulatory
requirements of a specific country.
Countries of the European Union and EFTA
Since April 8th 2000, radio and telecommunication
equipment are regulated under directive 1999/5/EC of the
European Union. This directive is referred to as the R&TTE.
For equipment within its scope, the R&TTE supersedes the
Telecommunication Terminal Equipment directive (TTE
98/13/EC), the Electromagnetic Compatibility Directive
(EMC 89/336/EC) and the Low Voltage Directive
(LVD 73/23/EC).
98-08901C39-B
The R&TTE and important information about it, is
published by the European Commission under the following
web address:
http://www.europa.eu.int/comm/enterprise/rtte/infor.htm
The requirements of the R&TTE are given in article 3:
• Health and Safety in Article 3.1(a),
• EMC in Article 3.1 (b),
• Radio in Article 3.2,
• Optional requirements in article 3.3.
The harmonized standards used for the g18 to demonstrate
compliance with the R&TTE directive are:
• EN60950 for Health and Safety,
• ETS 300 342 –1 for EMC in Article 3.1 (b),
• CTR 19 and 31 as relevant parts of TBR 19 and TBR 31
for Radio.
No optional requirements are applicable to GSM terminal
equipment.
The implication of the R&TTE is that integrators of the g18
will need to raise their own Declaration of Conformity under
the R&TTE using Annex III, IV or V.
Motorola recommends that integrators of the g18 document
their compliance activities in a technical construction file.
The Motorola test report for the g18 can be used to
demonstrate compliance with article 3.2 of the R&TTE
under the following circumstances:
• The g18 must be operated at the voltages described in the
technical documentation.
• The g18 must not be mechanically or electrically
changed.
• Usage of connectors should follow the guidance of the
technical documentation.
A Declaration of Conformity and test reports for the g18 will
be available upon request from Motorola. Requests should
be made to your contact person within Motorola. Care
should be taken as a product might fall under the scope of
other directives or standards depending on the type of
product.
The g18 is not approved under the automotive directive
(95/54/EC), as it cannot be connected directly to the power
supply or other systems of a vehicle without having
additional electronic interfacing.
Host Device Requirements
The host device requirements for the EU and EFTA
countries are:
• If the host device controls the g18 and technically does
not change it, no additional g18 test is required for the
(R&TTE) directive for FTA.
xv
• EN 301 489-1 and EN 301 489-7 for EMC on the host
device. Ensure that there is no technical differences to
ETS300 342-1. If the host device is a portable or fixed
application, the CE mark is required. If the host device is
in a mobile application, the E mark should be used.
• EN60950 Health and Safety for the host device.
• EN50360 for SAR portable device applications (when the
application can be used on or near the head).
North American GSM Type Certification
The g18 complies with the requirements of PCS 1900 Type
Certification scheme as setup by the PCS 1900 Type
Certification Review Board (PTCRB) and is listed as PCS
1900 Type Certified product. This certification will be
invalidated if the following conditions are not met:
• The g18 must be operated at the voltages described in the
technical documentation.
• The g18 must not be mechanically or electrically
changed.
• Usage of connectors should follow the guidance of the
technical documentation.
• Handsets or external card readers must be certified.
Host device PTCRB approval is required.
Note
United States of America
The Federal Communications Commission (FCC) requires
application for certification of digital devices in accordance
with CFR Title 47, Part 2 and Part 15. This includes
Electromagnetic Energy Exposure (EME) testing. As the
g18 modem is not a standalone transceiver but is an
integrated module, the g18 cannot be tested by itself for
EME certification. It is, however, your responsibility to have
your completed device tested for EME certification.
Host Device Requirements
The host device requirements are:
• If the host device controls the g18 and technically does
not change it, FCC CFR 47 part 24 is not required as it is
covered by the g18 approval.
• FCC CFR part 15 needs to be completed as this applies to
the end product, including EME (Electromagnetic Energy
Exposure) for a portable application.
xvi
98-08901C39-B
• The FCC ID label must be easily visible from the outside
of the equipment enclosure. However, it does not have to
be visible at all times, such as when a battery covers the
label or is embedded in a host device. In any case, the
label must not be removed from the g18. It is
recommended to add a label to the outside of the host with
the following information: “FCC ID: ID IHDT6AC1 is
contained within.”
Canada
This class B device also complies with all requirements of
the Canadian Interference-Causing Equipment Regulations
(ICES-003).
Cet appareil numérique de la classe B respecte toutes les
exigences du Règlement sur le matériel brouilleur du
Canada.
Regulatory Statement
The following regulatory statement for the E.E.A applies to
the g18 type MG1-4F21 only:
1. The g18 must be operated at the voltages described in
the technical documentation.
2. The g18 must not be mechanically nor electrically
changed. Usage of connectors should follow the
guidance of the technical documentation.
The g18 is type approved under CTR 5 ed.2 and CTR 9
ed.2. Using different external card readers or handsets
other than those approved by Motorola will invalidate
the type approval and require retesting and re-approval
by the British Approval Board – Telecommunications
(BABT). Such testing can only be carried out with prior
approval of Motorola. It must be noted that CTR 5 ed.2
and CTR 9 ed.2 are expected to be repealed by October
24th. 1998, but changes approved prior to that date can
be marketed after October 24.
3. The g18 has been designed the meet the EMC
requirements of ETS 300 342.
4. When integrating the g18 into a system, Motorola
recommends testing the system to ETS300342-1.
5. The g18 meets the safety requirements of EN60950.
6. Systems using the g18 will be subject to mandatory
EMC testing under directive 89/336/EEC and only
optional (see 3.) GSM type approval testing under
directive 98/13/EEC. Other directives like the LVD
directive 73/23/EEC might also be applicable to a
system using g18.
7. The g18 is type approved at BABT. Changes subject to
type approval should be communicated to Motorola and
BABT, and are not subject for discussion with other
Notified Bodies.
The above statement has been made on the basis of
Motorola’s long experience in GSM type approvals for the
E.E.A. and reviews with BABT of the UK. Motorola
recommends that integrators of the g18 consult Motorola in
the design phase to clarify any regulatory questions.
IMPORTANT: The telephone must be installed in a
manner that provides a minimum separation distance of
20 cm or more between the antenna and persons to satisfy
FCC RF exposure requirements for mobile transmitting
devices.
IMPORTANT: To comply with the FCC RF exposure
limits and satisfy the categorical exclusion requirements for
mobile transmitters, the following requirements must be
met:

Antenna Installation
g18 Type Certification Identifications
• A minimum separation distance of 20 cm needs to be
maintained between the antenna and all persons,
Europe MT3-411A21
otherwise a SAR test will be required.
US FCC ID IHDT6AC1 • The transmitter effective radiated power must be less than
Canada CANADA 109331257A TYPE ACPA or CAN 3.0 Watts ERP (4.9 Watts or 36.9 dBm EIRP). This
109331257A TYPE requires that the combination of antenna gain and feed
line loss does not exceed 16 dBi.
PTCRB g18

Safety

User Operation
Do not operate your telephone when a person is within
8 inches (20 centimeters) of the antenna. A person or object
within 8 inches (20 centimeters) of the antenna could impair
call quality and may cause the phone to operate at a higher
power level than necessary.

98-08901C39-B xvii
xviii
98-08901C39-B

1.1 GENERAL
This chapter provides background information and indicates
the objectives and tasks required to achieve a successful
implementation.
Figure 1. Integrator’s Tasks
1.2 INTRODUCTION
As an OEM integrator, you must accurately choose where
and how wireless technology will facilitate communication
for your customers. You will also have to evaluate which
technical considerations will give your product an edge over
the competition.
To successfully integrate g18 wireless modems into their
host platforms, you must perform the following tasks:
• Plan the product and create the design
• Develop and validate the hardware
• Develop supporting applications software
• Test and approve the product
98-08901C39-B
1. THE INTEGRATOR'S TASK
As you review these tasks, allow sufficient time for required
activities, such as the regulatory approval process, (see
“Regulatory Requirements”, page xiv) to identify critical
path activities ahead of time.
1.3 PLANNING THE PRODUCT AND
CREATING THE DESIGN
To plan the product and create the design, perform the
following steps:
• Develop a usage model
• Develop a message model
• Define a service strategy
• Define remote diagnostic functionality
• Investigate and obtain regulatory approval
1.3.1 Developing a Usage Model
The usage model answers the question, “How will the end
product be used - will it be portable or mobile, how many
hours a day will it be used, how many days a week?” and so
on.
Perhaps the most important factor for success is a clear
understanding and decision regarding how the final product
is to be used. This guides the development process, since all
design considerations drive toward meeting the needs of the
end user. For example, design issues related to a mobile
device, such as alternator noise and vibration, are completely
different from considerations required for a fixed-point
telemetry application powered by a solar panel. Defining
what is and is not important to the end user helps to make the
critical engineering trade-off decisions that are inevitable in
every product design.
As the integrator, it is your responsibility to develop the
usage model. Motorola is available to provide assistance and
answer questions, but is not directly involved in this phase of
the project.
1
The Integrator's Task
1.3.2 Developing a Message Model
The message model defines the number of messages that are
sent and received and their frequency. To create the message
model, determine the quantity and frequency of data sent in
each of the uplink (terminal to network) and downlink
(network to terminal) directions.
Answer the question, “Is there a requirement for the terminal
to be powered on and ready to receive eight hours a day, or
does the user turn the unit on only when making a query to
the host system?” The answer has a direct bearing on the
battery size and capacity requirement for powering the
device. The amount of data sent and received is relevant in
calculating the cost of airtime and deciding which type of
network connection to use. In short, the message model is
essential for making many engineering design decisions,
especially in calculating values such as sleep time versus
wake time and in determining battery capacity requirements.
You are responsible for developing the message model. The
typical approach to creating the model is to define the peak
and average network throughput requirements based on
input from the user. Motorola can provide current
consumption figures for each of the various modes of
operation, for example, receive and transmit.
The network throughput of the host device depends on
various factors, in addition to the raw throughput of the radio
channel. For example, in addition to the overhead involved
in forward error correction and support for packet headers,
the number of active users on the network can directly affect
network throughput.
1.3.3 Defining a Service Strategy
The service strategy determines whether the integrated
modem is the cause of a user’s problem and sets a policy for
keeping the end user operational during repair. The service
strategy must consider all potential service situations and
evaluate them in light of the usage model. You can create the
service strategy jointly with Motorola. Contact your
Motorola OEM sales representative for details.
To ensure that a final product can be efficiently serviced, it
is recommended that you design for serviceability early in
the R&D process. At a minimum, you could develop a
functional service strategy that contains a well-considered
procedure for performing unit-level screening. The test may
primarily determine whether a fault lies with the modem or
with the product. The test must also screen for network
problems and human error.
Motorola supplies an evaluation board (a standalone test
fixture) that provides a mounting platform and electrical
interface to the modem. (Refer to Chapter 9, “g18 Evaluation
2 98-08901C39-B
Board”, page 173, for further information.) Testing is
performed much more efficiently when the modem is
integrated within the OEM host, whether for a factory
end-of-line test or while at the user’s site. (Refer to
Appendix B, “Quick Start”, page 197, for further
information.)
In order for your product to allow integrated testing of the
modem, you may decide to provide a modem pass-through
mode.
A thoroughly developed OEM serviceability plan typically
includes a needs assessment for developing software utilities
that can assist in identifying communication problems
between the product and the modem and between the modem
and the RF network.
These utilities must be able to send commands to the
modem, evaluate the modem responses, perform network
connectivity testing, and verify data communication with the
network.
Such a software utility is essential for field service engineers
and shop technicians to diagnose problems with the product
and to troubleshoot a problem to a failed assembly or
mismanaged communication link.
1.3.4 Defining Remote Diagnostic
Functionality
When customer problems are reported from the field, you
must isolate the source of the problem remotely. You will
need to determine which part of the overall system is not
functioning correctly. The following items need to be
considered as a possible source of the problem:
• Network
• g18 wireless modem
• Host product
Often a problem is caused by a user’s lack of knowledge of
how to use the product correctly. Regardless, remote
troubleshooting is essential in reducing the number of
returned products and lowering service costs, particularly if
the host must be disassembled in order for the modem to be
removed.
Motorola recommends that your product application (both at
the terminal and host ends) incorporates sufficient problem
diagnostic software to determine the cause of the problem
remotely. Often, the best approach is to incorporate
progressively deeper loopback tests to determine the point at
which the communication link fails.
This remote diagnostic functionality should be an integral
part of your standard software load.

1.3.5 Investigating and Obtaining
Regulatory Approval
It is your responsibility to obtain regulatory approval of
products that integrate a g18 Integrated Wireless Modem.
The specific details for achieving regulatory approval vary
from country to country. Refer to “Regulatory Require-
ments”, page xiv, for further information.
1.4 DEVELOPING AND VALIDATING
THE HARDWARE
To develop and validate the hardware, perform the
following steps:
• Design the hardware platform
• Consider power supply options
• Select the source antenna
• Set up a development test environment
1.4.1 Designing the Hardware Platform
Integrating a wireless modem into a hardware design
requires many steps. Here again, the usage and message
models are necessary to calculate issues such as battery size,
heat dissipation, isolation from EMI, and physical mounting
of the unit to ensure proper grounding. Refer to Chapter 3,
“Design Considerations”, page 13, for further information.
Hardware design is your responsibility. Motorola can
provide recommendations where applicable, and can also
provide a one-time verification of EMI-caused desense with
the modem integrated into the host. To clarify, the host
device can introduce electromagnetic interference, which
will interfere with the performance of the modem. This EMI
can be conducted into the modem via the serial and power
lines, or radiated into the antenna and antenna cable. It is
your task to minimize the generation of EMI by your device
so that the modem’s RF performance is minimally affected.
Contact your Motorola OEM representative for details.
1.4.2 Considering Power Supply Options
Power supply requirements vary according to the usage and
message models. In addition to accounting for the current
drain of the modem in its various operating modes, you
should also consider ripple and noise on the power lines and
the ability to supply sufficient instantaneous current to
enable correct operation of the transmitter. You should also
ensure that your power supply can accommodate the highest
98-08901C39-B
The Integrator's Task
power consumption for the g18 modem that you want to
integrate.
Together, these requirements define the type and size of
power supply (for example, linear versus switched) to use
with the wireless modem. Refer to Chapter 3, “Design
Considerations”, page 13, for further information.
1.4.3 Selecting the Source Antenna
The g18 is terminated by 50Ω; therefore, any antenna termi-
nated by 50Ω will work with the g18. You should consider
these network requirements when you select an antenna
system. Refer to “Antenna Considerations”, page 24, for
further information.
You are responsible for selecting a suitable antenna and
submitting the final product to the network operator for
certification.
1.4.4 Setting Up a Development Test
Environment
A number of development test aids are available to assist in
hardware and application development. Modem hardware
and an evaluation board can be purchased from Motorola.
The evaluation board is a specially developed circuit board
with test points and jumper switches, which allows for
maximum flexibility in accessing and controlling
connections into and out of the modem. Refer to Chapter 9,
“g18 Evaluation Board”, page 173, for further information.
Motorola also provides various software utilities that can
help in performing development tests. Refer to Chapter 7,
“Testing”, page 69, for further information.
The network operator may sometimes provide a live devel-
opment network, supplementing the test environment
supported by Motorola. This development network, on
which you can develop and test your application, is separate
from the production network. You must negotiate directly
with the network operator for airtime and for building and
maintaining a development test environment at their facility.
1.5 DEVELOPING SUPPORTING
APPLICATION SOFTWARE
To develop supporting application software, perform the
following steps:
• Select a communications model
• Develop end-to-end application software
3
The Integrator's Task

1.6 TESTING AND APPROVING THE the network service provider is down. To guarantee that the
PRODUCT modem is located in an area with good coverage, and that an
end-to-end loopback message is possible, your product
To test and approve the product, perform the following needs a software application to perform the test.
steps:
The most effective approach to field-testing is to include an
• Perform EMI and desense testing (Refer to Appendix C, installation test procedure as part of your standard software
“Desense”, page 199, for further information.) load. Motorola can recommend specific network informa-
• Set up a final test environment tion that you can obtain from the modem describing how to
• Install and field-test the product implement an end-to-end loopback test. Refer to Chapter 7,
“Testing”, page 69, for further information.

1.6.1 Setting Up a Final Test Environment

1.7 RESOURCE ASSISTANCE
To ensure correct assembly of the final product (that the
Developing and testing a wireless integrated product
antenna is properly connected, the serial port is operational,
requires a well-equipped development lab and access to
and so on), perform an end-to-end test that proves that the
resources and outside information. Table 1, “Parts and Tools
final product can receive and transmit at the required signal
Requirements”, below, identifies the required development
levels. In locations where the final assembly test is
and service tools. Information is also provided regarding
performed within network coverage area, this test is
where to obtain the tools and how to obtain further
relatively simple. However, in locations where network
assistance.
coverage is not available, or for products being shipped to
other countries, it is necessary to test by secondary means.
The final assembly test must verify that all connections to 1.7.1 Integrating Engineering Support
the modem are made correctly. Testing on a network is not
required. Questions on this manual and the integration process are
handled by Motorola’s integration engineering teams
located in Europe and North America.
1.6.2 Installing and Field-Testing the Send an email to BSH015@email.mot.com, with your
Product name, phone number, company name, description of the
project and your question. An engineer will be assigned to
When the product is shipped to a site, it is installed or your project and will contact you by phone or by email to
mounted in a location that may restrict RF communications. assist you in resolving any issues.
It must be verified whether the behavior of a dysfunctional
product is caused by poor coverage or is due to the fact that

Table 1. Parts and Tools Requirements

Related Documentation

GSM Specifications Refer to “Reference Documents”, page xiii, for further www.etsi.org
information.

Unique Development and Service Aids

Host Evaluation Board Kit P/N S9002

This board provides interface connectors and circuitry
that allow the modem to be powered and interfaced to
a host device (PC) via a serial port and cable.
Includes instructions, interface ribbon cable, jumpers,
mounting hardware, antenna and antenna cable.
For evaluation board problems, contact:
+972-3-5684040

4 98-08901C39-B
 The Integrator's Task

Table 1. Parts and Tools Requirements (Continued)

Modem Test Equipment

GSM Test Set Rohde and Schwarz CMU 200 with GPRS option www.rsd.de
GPS Test Set Hewlett Packard 8960 with GPRS option www.hp.com
Welnavigate GS700 or GS1010

Wireless Verification Equipment

Live Network When available, a live network can be used Network Operator

Traditional Shop Equipment

Power Supply Dual Power Supply with 3-6V/2A and 12V/2A output Commercial Items
supplies
(12V for optional hands-free only – g18 EV board)
Oscilloscope 900Mhz, digital storage Commercial Item
Digital Volt Meter Fluke 77 multimeter or equivalent Commercial Item

1.8 ENVIRONMENTAL ISSUES 1.8.2 ESD Handling Precautions

g18 Integrated Wireless Modems are designed for a
combination of easy serviceability and general robustness.
These integrated modems are designed to be housed in an
OEM host product. The modem is tested to conform to the
environmental levels (for example, industrial use
specifications and PC card standards) that meet the intended
applications of most integrators. If you need additional
robustness and safety in your products, you must engineer
the environmental characteristics of your host product to
achieve a special safety rating.
1.8.1 General Precautions
Follow these precautions when working with wireless
modems:
• Minimize the handling of static-sensitive modules and
components.
• Wear a grounded anti-static wrist strap while handling
static-sensitive components.
• Do not bend or stress the modem in any way.
• Reinsert connectors straightly and evenly to avoid
causing short and open circuits.
All electronic devices contain components that are sensitive
to ESD (electrostatic discharge). For example, people
typically experience up to 35 kV ESD, while walking on a
carpet in low humidity environments. In the same manner,
many electronic components can be damaged by less than
1000 V of ESD. For this reason, you must observe the
following handling precautions when servicing this
equipment:
• Always wear a conductive wrist strap.
• Eliminate static generators (plastics, styrofoam, and so
on) in the work area.
• Remove nylon or polyester jackets, roll up long sleeves,
and remove or tie back loose hanging neckties, jewelry,
and long hair.
• Store and transport all static sensitive components in
ESD-protective containers.
• Disconnect all power from the unit before ESD-sensitive
components are removed or inserted, unless instructed
otherwise.
• Use a static safe-guarded workstation, which can be set
up by using an anti-static kit (Motorola part number
0180386A82). This kit includes a wrist strap, two ground
cords, a static control table mat, and a static control floor
mat. The Motorola part number for a replacement wrist
strap that connects to the tablemat is 4280385A59.

98-08901C39-B 5
The Integrator's Task
When anti-static facilities are unavailable, use the following
technique to minimize the chance of damaging the
equipment:
• Rest the static-sensitive component on a conductive
surface when you are not holding it.
• When setting down or picking up the static-sensitive
component, make skin contact with a conductive work
6 98-08901C39-B
surface first and maintain this contact while handling the
component.
• If possible, maintain relative humidity of 70-75% in
development labs and service shops.
g18 was tested for ESD according to
EN 61000-4-2.
Note
 2. MODEL DESCRIPTION

2.1 GENERAL display systems, load management and more. To support this
flexibility, the same functionality is offered in several
This chapter provides an overview of the different g18 different configurations. GPS capability is also provided in
integrated wireless modem models, including accessories, an additional configuration.
physical and electrical characteristics, features and
functional capabilities, and the data-exchange network over The g18 modem relies on system software for basic
which they communicate. operational instructions and on configuration parameter
values to meet modem and network interface requirements.
For model numbers, supported languages and specifications,
Refer to “Specifications”, on page 187. The g18 is designed for use in a system environment
comprising a GSM mobile radio network with one or more
radio operators per country. There is a basic requirement of
2.2 INTRODUCTION a corresponding infrastructure of a configuration level
suitable for the use of terminal devices with 2 W
The g18 modem supports the following modes of operation: transmission power.
1. A Phase II + GSM class 4 embedded module package
with voice, data, fax, and short message service (SMS)
support. 2.3 BASIC MODEL OVERVIEW
2. GPRS module supporting packed data communication
in 900/1800/1900 MHz bands.
The g18 GPRS features include full over-the-air Class B
2.3.1 g18 DV Slim
features using a handset with multi-slot Class 1, 2 and 4. In
This configuration is the smallest packaged module, which
addition, CS1-CS4 GPRS coding schemes are supported
measures 44.28 mm x 88.45 mm x 10.4 mm.
(coding schemes are used to manage the error rate in the
transmission of data to the mobile).
If you have both RS232 and DSC bus interfacing g18, you
have GPRS class B ability, meaning that you can answer a
voice call, while in GPRS mode. It provides the same
functionality as if a handset is connected, since this is also
DSC bus.
The g18 is designed to support a range of subsidiary services
associated with navigation, emergency services, road tolls,
security systems (such as car alarms and fire alarms), as well
as integrated standard voice/data/GPRS communication.
Applications where data modules can provide these benefits
include automotive telematics, mobile computing, asset
management, remote utility meter reading, street light
control, home security, vending and copy machine Figure 2. g18 DV Slim Data Module
management, fleet management, ATM security, POS
connectivity, household appliance monitoring and control,

98-08901C39-B 7
Model Description

2.3.2 g18 DV Board Only – 2.3.3 g18 DVG/Slim

Horizontal
The Horizontal Board Only product provides the smallest
volume with a horizontal connection.
The DVG Slim configuration provides GPS (Global
Positioning System) capability housed on the same package
as the GSM data module. This allows developers to save
integration space when location information is required.

Figure 3. g18 DV Board Only – Horizontal Connection

Figure 4. g18 DV GPS Data Module

8 98-08901C39-B
 Model Description

2.4 d15 AND g18 DIFFERENCES

The g18 is based on the d15, with added GPRS functionality.
Table 2 summarizes the differences between the g18 and the d15.

Table 2. Differences Between the d15 and g18

Function d15 g18

General

GSM Type GSM Phase II+. GSM Phase II+ + GPRS.

Data Levels Data signals at 5V. Data signals at 3V. Refer to “Data Levels”, on
page 21.

Pin-out Pin 15 in ZIF connector. Pin 15 in ZIF connector

Pin 10 in DIN connector. Pin 10 in DIN connector "wake up line" (awake
"Port-out" - Not used. g18, Awake DTE, GPRS coverage). Refer to
“Data Communication”, on page 28.

Pin 2,3 in ZIF connector - Not used. Pin 2,3 in ZIF connector.
Pin 16,15 in DIN connector - Not used. Pin 16,15 in DIN used for 2nd UART TXD & RXD
lines.

Mechanical

Mechanical Models Standard, Slim, DIN-Hor, DIN-Ver, GPS. Slim, DIN-Hor, GPS.

Power

Current in Sleep <10mA @ DRX2. <7.5mA @ DRX2.

Mode <8mA @ DRX 9. <4mA @ DRX 9. Refer to “g18 Current
Consumption”, on page 13.

On/Off Pulse <500mS. <700mS. Refer to “Configuration Setup and

Duration Audio Routing in g18”, on page 27.

Data Options

V42 Bis Supported only in SoftGsm mode. Not supported.

Transparent Mode Supported only in SoftGsm mode. Supported.

Fax Class 1 & 2 Supported only in SoftGsm mode. Fax class 1 using Winfax.

Wake Unit from Special sequence is needed in the Different sequence than d15. Refer to “How/
Sleep Mode application. When to Wake Up the Unit”, on page 16.

Baud Rate Setting Not supported. Enabled from 4800 to 57600 bps. See
AT+CBAUD.
(Auto baud rate is available between 4800 to
19200 bps).

98-08901C39-B 9
Model Description

Table 2. Differences Between the d15 and g18 (Continued)

Function d15 g18

DTR/DSR Lines DSR set ON after the DTE asserted DTR. There is no dependency between the two lines.

AT Commands

AT+FCLASS=? Not used, but can be entered and an OK 0,1 are supported.
returned.

ATD*99 Not Supported. Request GPRS service "D ". Refer to “AT
Command Listing”, on page 80.

ATD*100 Not Supported. Manual acceptance of a network request. Refer

to “AT Command Listing”, on page 80.

AT$ Not Supported. Supported (List of Supported Commands).

AT+CPOL Not Supported. Supported (Preferred Operator List).

AT+CIMI Not Supported. IMSI Request.

AT+CIP Not Supported. AT command for IP primitives simulation.

See Ph. 4.15.

AT+CRSM Not Supported. Supported (Restricted SIM access).

AT+CPBS +CPBS:("FD","LD","ME","MT","SM","DD"). +CPBS:("FD","LD",“ME”,"MT","SM","DD", “RC”,

“MC”).

ATS97 Antenna Not supported. Supported.

detect

ATS99 Not supported. Supported. Is not saved in profile, and needs to

be re-established after power-up.

ATS100 Not supported. Supported. Is not saved in profile, and needs to

be re-established after power-up.

ATS101 Not supported. Will set wake up line forever when x=1, and reset
it when x=0.
ats101? will return current state. These
operations are allowed only when factory bit is
set.
When parameters are incorrect, or factory bit is
not set, returns an error.

AT+CBST (000-002,004-007, (006,007,070,071),(000),(000-001)

012,014,065,066,068,070,071,075), The g18 supports baud rates of 4800 and 9600
(000),(001). bps.

AT+CGSN Not supported. Supported.

10 98-08901C39-B
 Model Description

Table 2. Differences Between the d15 and g18 (Continued)

Function d15 g18

AT+CPWD Not supported. Supported.

AT+CRTT Not supported. Select ring tone - Supported.

CIEV: 8, 10, 11 Not supported. Supported.

AT&C2 Not supported. Supported.

AT+GMI Not supported. Supported.

AT+GMM Not supported. Supported.

AT+GMR Not supported. Supported.

AT+CLCC Supported. Add "dialing" state, and non standard "released"

state. Asynchronous answers are also allowed,
by using at+clcc=1.

AT +MTDTR Not supported. Supported for DTR line test command.

AT +MTCTS Not supported. Supported for CTS line test command.

AT +MCWAKE Not supported. Supported for DTE Wake line control command.

MMGL Not supported. Supported from software version above

E6.01.10.

MMGR Not supported. Supported from software version above

E6.01.10.

MMGA Not supported. Supported from software version above

E6.01.10.

CMSS Not supported. Supported from software version above

E6.01.10.

CMGL Supports list of all messages only. From software version above E6.01.10, supports
list of messages for each status according to
ETSI 07.05.

AT+MSCTS Not supported. Supported.

AT+CSMP Not Supported. Supported.

AT+CSVM Not Supported. Supported.

AT+MFS Not Supported. Supported.

AT+CSCB Not Supported. Supported.

98-08901C39-B 11
Model Description

Table 2. Differences Between the d15 and g18 (Continued)

Function d15 g18

AT+MCSAT Not Supported. Supported.

AT+MECC Not Supported. Supported.

AT+CSCR Not Supported. Supported.

AT+MCELL Not Supported. Supported.

AT+IPR Not Supported. Supported.

GPRS AT Commands

AT+CGDCONT Not supported. Supported.

AT+CGQREQ Not supported. Supported.

AT+CGQMIN Not supported. Supported.

AT+CGATT Not supported. Supported.

AT+CGACT Not supported. Supported.

AT+CGCLASS Not supported. Supported.

12 98-08901C39-B
 3. DESIGN CONSIDERATIONS

3.1 GENERAL In order to minimize the ∆ it is recommended to use as short

a flat cable as possible and to put a 1000 uF capacitor (or
When integrating a wireless modem, internal connections maximum possible) in the g18 VCC input.
and placements are critical for a successful implementation.
Specific attention must be paid to the following support In addition to the losses recommendation, it is
mechanisms: recommended to have a current limit in the
power supply (2.5-3 A), in order to avoid
• Power supply considerations Note damage if a short occurs.
• Audio circuit considerations
• Data port considerations
• SIM card considerations 3.2.2 g18 Current Consumption
• ESD considerations
In order to design the power supply correctly, you need to
• Antenna considerations take into account the current consumption of the g18 in its
• Mechanical mounting different modes.
• Desense control (Refer to Appendix C, “Desense”,
page 199, for further information.) Table 3. g18 Current Consumption
• Connecting the 3788 handset to the g18 Mode Current Consumption
• GPS considerations
g18 without accessories and <4mA @ DRX9
no call in process < 7.5mA @ DRX2
(Sleep mode)
3.2 POWER SUPPLY CONSIDERATIONS
g18 without accessories but < 50mA
TS ON
3.2.1 Power Supply Losses g18 during searching time <180mA
typical average 80mA
The g18 is specified to operate between 3.0 V and 6.0 V on
g18 with DSC bus accessory Typical 45 mA
the g18 input (after the flat cable losses). In order to be able
(such as a handset) and no
to function in the lowest battery values, it is important to
call in process
verify the losses in the power supply lines, flat cable and user
PCB. g18 during a call and using <1.8A Peak, Average
maximum power level 300mA @5V
The g18 is a GSM phone that transmits in pulses of
approximately 0.5 mS every 4.6 mS. The peak current is g18 during a call in GSM <0.7A Peak, Average
approximately 1.5 A, while the worst cast peak current is power level #10 (for example) 175mA @ 5V
2.2 A at 3 VCC.
The VCC line drops down during TX periods:
DRX is the rate at which the base station
interrogates the mobile station. The network
operator sets this parameter.
Note

Figure 5. The VCC Signal During TX Periods

98-08901C39-B 13
Design Considerations

3.2.2.1 Turning the Unit On or Off
The g18 is powered from a single power supply in the range
of 3.0 to 6.0 V DC.
The unit will not power up automatically by connecting the
power. There are two ways to turn on the unit, using the
ON/OFF pin and using the TS pin, as described in the
following sections.
The ON/OFF line is the recommended way to power off the
g18, since it detaches the g18 from the network and
disasserts the SIM card contacts in the correct order. When
the g18 is powered off by disconnecting the power to the
unit, the SIM card might be damaged, and units containing
the g18 that need to pass SIM card type approval tests will
fail due to the SIM’s incorrect power off sequence.
3.2.2.2 Turning the Unit On or Off Using the
ON/OFF Pin
The ON/OFF pin (pin #14 on the ZIF connector and pin #18
on the DIN connector) is used as a toggle input to turn the
unit on or off. Any drop to low in this pin will change the
status.
To verify that the unit is on or off, check the DSC_EN line.
If it is high, the unit is on; if it is low, the unit is off.
The timing for this process is shown in Figures 6 and 7.
T1 minimum = 12ms
T2 minimum = 630ms
T3 typical = 850ms
T4 typical = 240ms
T3+T4 max =1300ms
T5 typical = 1725ms
3.2.2.3 Turning the Unit On Using the TS
Pin
The main use of the TS line is for units connected to a mobile
device where the current consumption is not the main
concern.
The TS line is used to turn on the unit. This line cannot turn
off the unit. When the TS line rises, it will turn on the unit.
The TS line is used to turn the unit on when power is
connected to the unit (for example, the ignition line in a car
kit).
The TS line should be returned to low in order
to be able to work in sleep mode.
Note It is recommended to pull the unit high for
650 ms in order to wake the unit using the TS
line.
The 650ms pulse can be without any delay from
the VCC.
The actual turn ON process using the TS line is
done by sampling the line at 2 points. When
powering ON the g18, there is a spike on the
VCC that is considered as sample number one.
After 600ms, the next TS will be sampled. This
situation changes, however, if the unit was not
powered off using the ON_OFF signal.
T1=600ms (on is sent after the
power was supplied for a long
time 600ms)
T2=12ms (The TS signal is
sampled on the rising edge,
therefore its size does not matter)

T3= 820ms

T4= 25ms

T5= 250ms

Figure 6. Turning On the Unit Using the On/Off Pin Figure 8. Turning the Unit On Using the TS Line

T2 min = 630ms (T1 min = 12ms)

T3 min = 1550ms
T4 min = 630ms
T5 = 620ms
T6 = 800ms
T7 = 240ms
T8 = 5400ms
T9 = 4840ms

Figure 7. Turning On and Off the Unit Using the ON/OFF

Pin

14 98-08901C39-B
 Design Considerations

The following pictures show the behavior of the RS232 lines

while turning on the g18.
(Low level on RS232 indicates an active state).

T1 max = 3.5 sec

T2 max = 5.5 sec

T1

T2

Figure 11. DCD/RI During Ton

Figure 9. DTR/DSR During Ton

T1 max = 1.7 sec

The CTS becomes active before the DSC_EN becomes
active.
T1 max = 1.7 sec

T1

T1

Figure 12. TXD/RXD During Ton

Figure 10. RTS/CTS During Ton

The DCD and RI are inactive during the On/Off process.

98-08901C39-B 15
Design Considerations
3.2.3 How/When to Wake Up the Unit
If the g18 has no accessories, it can enter Sleep mode
(current save mode).
In Sleep mode, the radio is switched to minimum activity.
The clock is removed from the RF section and the logic
section is reduced from 13 MHz to 32 KHz.
The unit senses activity by periodically exiting this mode. In
the case of an incoming call, the unit will exit Sleep mode.
Entering Sleep mode will not terminate a GPRS section and
will not deactivate a context.
During Sleep mode, the RS232 does not respond to any
commands from the DTE device (UART is disabled and no
response will be received via the RXD line). In order to wake
the unit, the host needs to communicate with the g18 using
one of the following options:
Option 1
Sleep mode works as follows:
Activate Sleep mode by sending ATS24=n (n=1,2,3,4
seconds). (To disable Sleep mode send ATS24=0).
This causes the g18 to drop the CTS whenever the unit is in
Sleep mode.
When TXD is present, the g18 will not enter Sleep mode. At
the end of the TXD (TXD buffer empty), the g18 waits n
seconds (as defined in ATS24=n) and then enter Sleep mode.
Figure 13. Sleep Mode Timing
Option 2
Activate Sleep mode by sending ATS24=n
(n = 1, 2, 3, 4 seconds).
Use the wake up line (pin #15 in the FC 36 pin or pin #10 in
the DIN 28 pin) to wake the g18 when you want to send data.
When the DTE needs to send data, it will pull this line to low,
wait 30 ms (wake time required for the g18) and then start
sending the data.
While sending data, the wake up line should remain low, and
the g18 will not enter Sleep mode.
16
1 The ATS24 factory default value is "0". This
value is saved in the EEPROM. To change
the default value, save the new value to the
Note EEPROM. After recycling the power, the
value of ATS24 will be the value saved in the
EEPROM. The value of ATS24 can also be
changed without saving in the EEPROM, but
will be lost after power recycling.
2 The TS line should be low in order to enter
Sleep mode.
3 The DTE should look for the active CTS
before sending data (HW flow control).
4 The DTE’s UART should not send any
character to g18 if the CTS is inactive,
otherwise that character might be lost. If the
DTE’s processor handles the flow control,
and not its UART, and there is a gap
between checking the CTS state and
sending the start bit, g18 may set CTS to
inactive during this gap, and the character
sent to g18 might be lost.
.
Figure 14. Wake the g18 When the DTE Wants to Send
Data
Wake up the DTE
The g18 indicates to the DTE that data is present or that the
unit exited and returned to a GPRS coverage area. This is
done using the bi-directional wake up line (pin #15 in the FC
36 pin or pin #10 in the DIN 28 pin).
When the g18 wants to send data to the DTE, it activates the
wake up line to interrupt the DTE, followed by data
transmission (assuming RTS is active). When data is present
in the UART, the g18 sends a pulse with a duration of
2*y ms. The value of y is determined by ATS99= (default
value is 30; 0 value is not allowed), where t = pulse duration.
98-08901C39-B
 Design Considerations

In order to limit the number of interrupts, g18 sends

interrupts when the distance between one burst of data to the
other is bigger than specified in ATS100 (default value is 1;
0 value is not allowed).
Figure 15. Wake the DTE When Data is Present Using the
Wake up Line
Figure 16. Wake Up the DTE when the Unit Goes from a State of
Non-GPRS Coverage to GPRS Coverage
Wake Up Line Architecture
The wake up line is a bi-directional line. It is used to turn on
the g18 as described in “Option 2” , page 16, (input to g18)
and to wake the DTE (output from g18).
The configuration of the line is as follows:
1 The g18 gives a wake up pulse for data
sent to the DTE in GPRS mode and in
CSD mode.
Note
2 The g18 generates a wake up pulse
whenever asynchronous data is sent to
the DTE.
(+CIEV, +CLCC, +CCWA, +CMT, +CMTI,
+CBM, +CDS, +CDEV, +CLIP, +CR,
+CREG, +CIP, 2 / RING …)
3 The g18 gives a wake up pulse whenever
a change in GPRS coverage occurs,
depending on the dynamic setting of the
AT+CWAKE=N command:
• N = 0: Changes in GPRS coverage
will not generate a wake up pulse.
• N = 1: When GPRS coverage is lost,
the g18 will generate a wake up
pulse.
• N = 2: When GPRS coverage is
achieved, the g18 will generate a
wake up pulse. This is the default
value after power-up.
4 S99 responds with an error if the value is
greater than 2,147,483,647. Value of 0 is
changed to 1, with no error.
5 S100 responds with an error if the value
is greater than 32,767. Value of 0 is
changed to 1, with no error.
2. When the DTE enters Sleep mode, the DTE should not
load the wake up line (3 state).
3.3 AUDIO CIRCUIT CONSIDERATIONS
The g18 can make voice calls as well as data calls. With
voice calls, the audio can be routed via several channels:
• Digital audio channel: Audio is sent via the DSC bus.
• Analog audio channel: Audio is sent via external drivers
to audio devices.
• Analog audio channel in hands free mode: the g18 sends
the audio out with the Echo Cancelling on in the DSP.
External drivers are required.

3.3.1 Digital Audio

Figure 17. Wake Up Internal Connections In the case of a digital audio channel, a DSC driver is used.
The user should be aware of the presence of the hook switch,
which will determine whether the handset is in/out of use.
Pay attention to the following points: There are two DSC bus accessories for audio defined for the
1. When the wake up line is used to wake the g18 (wake g18:
up line is pulled down), no wake up indication to the 1. External Handset.
DTE will be available.
2. DHFA - Car Kit for Hands Free.

98-08901C39-B 17
Design Considerations

3.3.2 Analog Audio Without Hands Free 3.3.3 Analog Audio - Levels

The g18 drives the audio in/out in order to allow a voice call. Audio Uplink (MIC)
In order to connect a headset, the speaker and microphone
The maximum signal level that the g18 can receive in the
channels must be amplified.
Audio In pin, before the signal is saturated, is 260 mv, see
For an example of these drivers, refer to Chapter 8,“g18 Figure 19.
Evaluation Board”, page 173.
Another point to be taken into consideration is the buzz
existing in GSM phones due to the transmission
rate (217 Hz). In order to minimize this noise, the g18 has a
separate ground for the analog circuits.

Figure 18. Ground Connections Figure 19. g18 Input Maximum Level

The main reason for the buzz is the drop in the ground/Vcc The maximum level that the g18 can accept before the signal
lines because of the peak current during TX mode. In order at the network becomes distorted is approximately
to minimize the buzz, the following should be done: 500 mvP-P.
• Use a short flat cable. The following picture shows this maximum signal:
• Connect the analog ground from the g18 to all the analog
circuits in the customer application without connecting
them to the power supply ground.
• Connect all the capacitors to the audio circuits ground to
the analog ground.
• Any reference voltage that may be used should have the
external capacitor connected to the analog ground.
• The maximal audio in/out levels from/to the g18 can be
seen in “Analog Audio - Levels”, below.
• Connect the digital ground to the antenna ground. (This
can also help if there is sensitivity desense due to digital
signals from the customer’s board.)
• Connect the digital ground of the g18 with the digital
ground of the application. Figure 20. Input Maximum Level and BS Detected Signal
• Verify that none of the analog lines are referenced to the
digital ground.

18 98-08901C39-B
 Design Considerations

The CODEC 0 dbm0 = 375 mvrms = 1058 mvP-P. Between Voice

the EX_AUDIO_IN pin and the CODEC there is an
A 500mv RMS sin signal with a frequency of 1khz was sent
amplifier with an amplification of 3.3 and the following
from a base station to the g18.
frequency response:
The following amplitudes were measured on the audio out
pin of the g18:
Table 4. g18 Rx Audio Levels
Handset Volume Amplitude (mV RMS)
0 27
1 37
2 51
3 69
4 100
5 137
6 196
7 277

Varying levels were sent from the network and the signal
Figure 21. Gcap Amplifier Gain Response was measured at the audio out.
The input is presented both in RMS and in dbm0. The output
Therefore the odbm0 of the uplink path is 375/3.3 = 113.63 mV is at level 7.
RMS. The headroom is
Table 5. Rx Audio Levels vs. Different Signals in the BS
20*LOG (500/(1058/3.3))= +3.86 dbm0.
Audio Downlink (Speaker)
g18 Out
The 0dbm0 is 548 mV RMS. Max output is 2.6 V p-p. dBm0 mV RMS
(mV RMS)
The maximum signal from the network before distortions 3.14 1111.9 580
occur was measured at 1180 mv RMS. Therefore, the
0 774.6 420
headroom is 20*LOG (1180/548)= 6.66 dbm0.
-5 435.6 237
The following graph shows the frequency response of the
analog section: -10 244.9 135
-15.5 130 70
(Phone: -4.7 dBPa)
-16 122.8 68
-17 109.4 61
-20 77.5 43
(Dispatch: -94 dBSP)
-25 43.6 24
-30 24.5 17

Tones
The OK key was pressed and the tones were measured on the
audio out pin of the g18.

Figure 22. g18 Analog Audio Frequency Response (Audio

Out Pin)

98-08901C39-B 19
Design Considerations

The same amplitude was measured during a call, and off call. The block diagram for the required drivers is shown below.
All the measurements are with ATS96=0. For a detailed example of the driver designs, refer to
Chapter 8,“g18 Evaluation Board”, page 173.
Table 6. g18 Rx Audio Levels with ATS96=1

Handset volume Amplitude (mV P-P)

0 43
1 75
2 107
3 150
4 215
4 215
5 295
6 420
7 583

With the ATS96=1 command, the amplitude was 1043 mV

P-P.
Figure 23. EV Audio Block Diagram

3.3.4 Analog Audio With Hands Free The requirements from the external drivers and audio
devices are as follows:
The audio in/out from the g18 for analog hands free is the
same as for non-hands free. All the considerations from Table 7. External Drivers and Audio Device Requirements
Section 3.3.2 are applicable for this mode also.
Requirement Value
The additional consideration in this case is to switch the g18
Microphone Impedance Typical 700 ohm
DSP to Echo Cancelling mode.
S/N Ratio Minimum 35dB
In order to switch to Hands Free mode, use the RS232 port
by sending a switch command at the start up. Gain from Headset to g18 (A2) 45 – 49 dB

ATS96=1 Echo canceller is activated (Hands free). Frequency Response 11 to +1 dB

(including microphone) 300 to 3400 Hz
ATS96=0 Echo canceller is disabled (Headset - Default).
g18 Input Impedance 10KΩ
From version E6.13.24 and later, the Echo
Canceller feature can be activated or disabled TX Distortion Maximum 5%
during an active call. Speakerphone Load 25 to 39 ohm
Note
S/N Minimum 35dB
Gain from g18 to Headset (A1) 13 to –9 dB
Frequency Response 10 to +1 dB
(including SPKR) 300 to 3400Hz
g18 Output Impedance <1KΩ

20 98-08901C39-B
 Design Considerations

3.4 DATA PORT CONSIDERATIONS

3.4.1 Data Levels

The g18 is a DCE device operating on 0 to 3V logic. An

MC74LCX244 buffer buffers all the in/out signals.
The DTR, DSR, RTS, CTS, DCD lines are "1" (active) in
0 V and "0" (inactive) in 3 V. The RXD and TXD lines are
"1" in 0V and "0" in 3V.
The signal thresholds are:
Vih 2.0 V min, 5.5 V max
Vil 0.8 V max
Voh 2.5 V min @100 uA
Vol 0.2 V max @ 100 uA
Figure 25. DTE Connection to g18 (User Connector 28 Pin
The port configuration is: DIN)
1 start bit
1 stop bit
8 data bits
No parity
The default Baud rate is 9600bps with auto baud detect
activated. The specific baud rate can be set using
AT+CBAUD=<Baud>
.

Figure 26. DCE Connection to g18 (DCE Device) (User

Connector 36 Pin ZIF)

Figure 24. DTE Connection to g18 (DCE Device) (User

Connector 36 Pin ZIF)

98-08901C39-B 21
Design Considerations

3.4.3 Setting the Baud Rate

The power up default baud rate is 9600, with enable auto

baud rate detection feature. The baud rate can be switched to
4800, 9600, 19200, 38400 or 57600 using AT+CBAUD =
<baud>.
<baud> values are 4-8, 9 or 4800, 9600, 19200, 38400,
57600. Value represents 4800 to 57600. Value 9 represents
auto baud rate detection.
For example, AT+CBAUD=8 is equivalent to
AT+CBAUD=57600. Using AT+CBAUD=<baud> with
<baud> value other than 9 will disable the auto baud rate
detection feature.
After power up, the g18 UART is programmed to 9600, with
automatic baud rate detection. To switch to 57600 BPS use
Figure 27. DCE Connection to g18 (User Connector 28 Pin AT+CBAUD=57600. g18 will replay with
DIN) “OK<CR><LF>”. After flushing these characters out of the
UART, g18 will re-program the UART to the new baud rate.
To verify this process, DTE’s UART should switch to the
When the g18 is in Sleep mode, the RS232 new baud rate after receiving “OK<CR><LF>”, and send
output lines maintain the last stage. AT+CBAUD? to get the new baud rate. The answer
Note There are no level changes due to the sleep “OK<CR><LF>” is not dependent on ATVx setting (verbal
stage of the unit. or numeric response).
The g18 supports auto baud rate detection for low baud rates
4800 - 19200. To switch to this mode, the AT+CBAUD=9
3.4.2 DTR Line and DCD Line command should be sent to the g18. The g18 will process
this command as described above, except that it will
The DTR line must be active (0V) in order for the g18 to program UART to 9600 with auto baud rate detection. After
recognize the DTE. getting the “OK<CR><LF>”, the DTE can program its
If the DTR is not used by the application, connect this line to UART to a baud rate between 4800 - 19200, and verify the
ground (DTR Active). new setup using AT+CBAUD?.

The DCD line indicates the following: Auto-baud detection mode in g18 will be reinitiated, as
follows:
• In CSD Indicates Carrier Detect Low during the call high
in idle mode. • On power up.
• In GPRS mode Indicates PDP context status - Active low, • After AT+CBAUD=9.
Inactive high. • When DTR changes mode from LOW to HIGH.
DCD is activated only when PDP context is achieved. DCD Once the baud rate is detected and set, g18 will continue to
is de-activated when PDP context is off. work at the same baud rate until it is reinitiated as described
above.
The DTR indicates that the DTE is ready.
The DSR indicates that the DCE is ready. There
is no connection between the two.
Note
Do no use DTR for releasing a CSD call.

22 98-08901C39-B

Auto baud detect requires careful handling,
since the g18 has numerous asynchronous
messages that arrive while the UART is in auto
Note baud detect mode, and generally are displayed
as garbage characters.
• It is recommended to set the baud rate
using the at+cbaud=x (x not equal to 9)
command. This means that the UART is
never in auto detect mode, and there is no
problem sending commands and receiving
asynchronous messages.
• The inter byte delay issue: Work within the
speed defined for your UART. It is the
UART’s job to handle inter byte delay, with
the exception of handling CTS.
• After setting the baud rate to fixed baud,
you can issue another AT command once
you receive the entire OK response,
including the CR/LF appended to it.
• If you are working in auto baud detect
mode, you should allow another character
time after the OK, before starting another
AT command.
3.5 SIM CARD CONSIDERATIONS
3.5.1 SIM Card Support
The g18 module has a built-in SIM card reader within the
module itself. The SIM card is inserted into the slot provided
on the side of the sheet plastic cover. When inserted to the
correct depth, the card should be flush with the cover. To
extract the card, insert a non-conductive tuning tool into the
slot on the top of the unit at the back end of the card, and then
push the card out of the slot so that it can be removed by
hand.
For some installations, this built-in slot will not be
accessible, so an external card reader is needed. If a digital
handset is going to be used, the card reader can be part of the
handset and is connected to the modem via the DSC
interface. Other installations require the SIM card slot to be
installed into the OEM device and circuitry to be installed to
connect the card reader to the g18.
98-08901C39-B
Design Considerations
The SIM card interface contains six lines plus two lines for
presence detection, (lines 1 and 2) as shown in Figure 28,
below.
Pin Description
1 Gnd
2 SIM_PD
3 SIM_CLK
4 *SIM_RST
5 SIM VCC
6 SIM_I_O
7 SIM VPP
8 Gnd
Figure 28. The SIM Card Interface
The g18 supports 3 types of SIM connections:
• Internal SIM: Internal socket in the g18. Supports 3/5 V
cards.
• External SIM: The SIM lines are routed in parallel to the
SIM socket and to the user connector. The user can
connect the SIM externally. Supports 3/5 V cards.
IMPORTANT!
When connecting externally, Full Type Approval should be
required. This may require submission for testing if the
SIM lines are longer than 10 cm.
• Remote SIM: This is a standard connection. The SIM is
connected to an external SIM socket, which is connected
to the radio via the DSC bus. Two accessories are
available: M3788 handset and external SIM card reader.
Supports 5V cards only.
For GPRS functionality, your SIM card must
support this service.
Note A SIM card should be replaced either when the
unit is powered off or when a power cycle is
applied after a change.
3.6 ESD CONSIDERATIONS
Generally, the ESD can be protected up to 8KV by using
ceramic capacitors of 0.1uF or higher.
The capacitor protects against ESD for all the static lines,
power, SIM PD, SIM VCC, and so on. The protection is
performed inside the g18, however, it is recommended to
add protection inside the user PCB, especially if the flat
cable is long.
23
Design Considerations
For lines with high signal rates, it is recommended to use
Transguard with low capacitance. There are Transguards of
3 pF or less.
It is recommended to ground the antenna ground contact and
the power supply ground contact in order to prevent ESD
from entering the g18 or the user equipment.
3.7 ANTENNA CONSIDERATIONS
The antenna must be mounted like any other cellular or land
mobile radio antenna. The best position for the antenna is
usually the center of the vehicle roof, which provides a fairly
symmetric ground plane on metal cars. For vehicles of
non-metallic material, such as fiberglass, mount the antenna
where it will not be obstructed by items, such as mirrors.
3.7.1 Antenna Systems
Use this information to assist you in selecting the appropriate
antenna to incorporate into your product package. For
specific detailed information, Motorola recommends that
you use the expertise of an antenna design engineer to solve
individual application concerns.
3.7.2 Antenna Safety
The following statement from the American National
Standards Institute (ANSI) specifies the safety criteria that
integrators must use when designing the antenna for a
product integrating the g18 modem.
“The design of the integrated product must be such that the
location used and other particulars of the antenna comply
with the then current American National Standards Institute
(ANSI) Guidelines concerning Radio Frequency Energy
Exposure and with any other nationally recognized radio
frequency standards that may be applicable thereto.”
3.7.2.1 User Operation
Do not operate your telephone when a person is within 8
inches (20 centimeters) of the antenna. A person or object
within 8 inches (20 centimeters) of the antenna could impair
call quality and may cause the phone to operate at a higher
power level than necessary and expose that person to RF
energy in excess of that established by the FCC RF Exposure
Guidelines.
The telephone must be installed in a manner
!
that provides a minimum separation distance of
20 cm or more between the antenna and all
Caution persons to satisfy FCC RF exposure require-
ments for mobile transmitting devices.
24
To comply with the FCC RF exposure limits and
satisfy the categorical exclusion requirements
for mobile transmitters, the following
Note requirement must be met:
The transmitter effective radiated power (ERP)
must be less than 3.0 W ERP (4.9 W or 36.9
dBm EIRP). This requires that the combination
of antenna gain and feed line loss does not
exceed 16 dBi.
3.7.3 Antenna Performance
The network operator usually sets the antenna network
requirements.
3.7.4 Portable Devices
In an environment where portable devices are in use, many
variables exist that can affect the transmission path. In this
case, it is preferable to use a vertically-polarized,
omni-directional antenna.
Antennas for portable devices include the following
designs:
• Internal antenna (invisible or pull-up)
• External antenna, removable and directly connected to
the device
• External, remote antenna
3.7.4.1 Internal Antenna (Invisible or Pull-
up)
This is the most difficult antenna design scenario. Despite
greater physical constraints, an internal antenna must still
provide a gain sufficient to meet network specifications.
Metal-cased products cannot have internal antennas since
the metal acts as a shield around the antenna and prevents RF
signals from reaching the antenna. (A metal case acts like a
Faraday cage.) The antenna should be positioned so that it is
vertically oriented when the device is carried normally. This
will ensure that the optimal antenna performance is available
the majority of the time.
Cable routing from the modem to the antenna needs to avoid
RF-sensitive circuits and high-level, high-speed clock
circuits. The following points should be considered:
• The location of the antenna to avoid RFI to a computing
device.
• Good shielding of the display and other RF-sensitive
components.
• The most efficient method of cable routing.
98-08901C39-B

If the above points are not considered, antenna gain can be
offset by cable loss. A typical coaxial cable is very thin, such
as the RG178B used in portable devices, and cable loss can
be as high as 0.5 dB per foot. Some coaxial cable
manufacturers market relatively thin double-braid coaxial
cables. These cables show much better isolation than
single-braid cables, typically by 30 to 40 dB. Double-braid
cables reduce radiation and RF pick-up when routed inside a
portable device.
3.7.4.2 External Antenna, Removable and
Directly Connected to the Device
You can design a portable device that can use an
off-the-shelf, plug-in antenna, such as a 1/4 wave monopole
or 1/2 wave dipole antenna. The typical gain of these
omni-directional antennas is 0 dBi and 2.14 dBi,
respectively. Like the internal antenna, these antennas
should be oriented vertically when the device is carried
normally to ensure the best antenna performance.
Cabling in this case demands the same consideration as an
internal antenna application. In a typical laptop application,
the antenna must be placed as far as possible from the
display to avoid deflection. This usually causes a deep null
in radiation patterns.
3.7.4.3 External, Remote Antenna
For remote antenna applications, use the same design
approach as internal designs, including the RF cable routing
of the external connector. You can choose an off-the-shelf
mobile antenna of omni-directional 1/2 wave length. The
antenna should have a gain of 2.14 dBi. Higher gain than this
may not be appropriate for portable applications.
A double-braid coaxial cable, (such as RG223) from the
device to the antenna is recommended, if the cable length is
more than a few feet long. The difference in cable loss
between low-cost RG58 cable and the more expensive
RG223 cable is approximately 4.5 dB per 100 feet. If the
cable must be routed through noisy EMI/RFI environments,
a double-braid cable such as RG223 can reduce radiation and
pick-up by 30 to 40 dB.
3.7.5 Fixed Devices
Fixed data device applications use the same design
recommendations as a portable device with a remote
antenna.
98-08901C39-B
Design Considerations
The most economical and practical choice for the RF
connector of an external antenna is a TNC threaded
connector, whether it is a plug-in type or a remote type. TNC
has a good frequency response to 7 GHz, and leakage is low.
A mini UHF threaded connector provides adequate
performance and is an economical choice. If the size of the
TNC and mini UHF connectors becomes critical, consider
an SMA threaded connector or an SMB snap fit connector.
(The SMB connector does not accept RG58 or RG223
cables).
3.7.6 Antenna Test Methods
Whether portable or fixed, the device antenna is the critical
link to the network. A poorly performing antenna reduces
the coverage of the device within the network footprint. The
antenna performance must meet the impedance and match
the criteria of the modem (refer to
Chapter 8,“Specifications”, page 187.), and have the
appropriate amount of gain to meet the network ERP
requirements.
Two tests must be performed on the antenna to ensure that it
meets the requirements. For both tests, the antenna must be
integrated in its final form. That is, the antenna must be
mounted on a representative housing that includes all metal
objects forming the ground plane or counterpoise.
Antenna testing requires an experienced operator and an
anechoic chamber, a GTEM cell, or approved open field site.
Your Motorola OEM support representative can provide
advice on this type of testing.
3.8 MECHANICS - MOUNTING THE G18
3.8.1 Fixed-Mount Usage
Fixed-mount usage eliminates most of the mechanical
constraints of handheld designs, although the requirements
still apply. Fixed-mount units are sometimes AC-line
powered and require filtering to eliminate the 60 Hz noise
that can impair modem operation.
Proper mounting of the modem requires it to be securely
fastened within the host housing.
To ensure ease of access for installation and troubleshooting,
locate the modem within the product in such a way that serial
I/O and antenna connections are readily accessible.
Quick access to the modem allows it to be efficiently
removed, probed and functionally tested.
25
Design Considerations

3.8.2 Fastening Units with Housing You can see the circuits used in the g18 Evaluation board for
this purpose as an example, in Figure 31, below.
Mount the modem to the rigid OEM product housing, using
four #2-56 UNC 2A machine screws, torqued to 2 in.-lbs.
Position the screws as shown in Figure 29 and Figure 30.

Figure 29. Mounting the Modem (Front View)

Figure 31. Handset Connections / Hardware Required

3.10 GPS CONSIDERATIONS

The g18 DV with a GPS model includes an internal M12
GPS receiver from Motorola.
The GPS receiver is powered internally from the g18 with
3 V DC. All the other lines of the GPS are routed to the user
connector (ZIF 36 pin). The GPS lines in the g18 user
connector 36 pin ZIF socket are as follows:

Table 8. The GPS Lines in the g18 (User Connector 36 Pin

Zif Socket)
Figure 30. Mounting the Modem (Rear View)
g18 User
Function
Connector Pin #

3.8.3 Fastening DIN Units 2 GPS RXD receives data in 3V logic.

3 GPS TXD transmits data in 3V logic.

Secure the DIN board to the host device using three M1.8
screws. 34 Antenna voltage input 3 or 5 V DC.
(active antennas)
Do not mount a g18 integrated wireless modem

!
Caution
in PC Card Type III rails. Forcing the modem
into a PC Card header can damage the
connector pins in the header and leave the
35

36
RTCM input in 3V logic.

1pps output in 3V logic.

modem loose and poorly grounded.
The GPS receiver is a standalone unit in the g18.
More details about the M12 module can be viewed on the
3.9 CONNECTING THE M8989 HANDSET
web at:
TO THE G18
http://www.synergy-gps.com/M12_Oncore.html
In order to connect the handset (M8989) to the g18 the
following connections are required in the user board.

26 98-08901C39-B

4.1 GENERAL
The operating functions of the g18 modem are implemented
in the base unit into which the g18 is integrated. The g18 is
a GSM900/1800/1900 Phase II+ device with GPRS
capabilities.
The corresponding functions are implemented conforming
to V.25ter, GSM07.07, and GSM07.05.
The standards bodies regularly update these
standards, therefore there is no guarantee that
the commands supported by the g18 exactly
Note
conform to the latest versions of these
specifications. Some commands listed in these
standards do not apply in the GSM
environment.
AT+C commands conforming to GSM07.07 and GSM07.05
and a number of manufacturer-specific AT commands are
available via the serial interface of the g18 for functionality
implementation.
Commands are input via the operating functions of the base
unit. The base unit translates the operating functions into AT
commands and the g18 executes the requested action.
You should wait to receive OK before sending
a new AT command.
Note
The V.25ter modem guidelines apply to the time sequence of
interference commands. In accordance with these
guidelines, commands start with the string AT and end with
a carriage return (<CR> or 0x0D). Commands are
acknowledged with OK or ERROR. A command currently
being processed will be interrupted by each subsequent
incoming character, so the next command must not be sent
until the acknowledgement has been received that the
command has been processed. If this does happen, the
current command will be cancelled.
98-08901C39-B
4. SOFTWARE INTERFACE
4.2 MODEM COMMUNICATION MODES
The g18 modem supports the following communications
modes: voice, data, SMS and fax.
4.2.1 Voice Communication
• Analog Audio: Analog audio communication is provided
via a standard analog headset such as the headset used
with the StarTAC cellular phone. In this case, the controls
for answering calls, dialing, and hanging up are provided
by the AT command set interface. This mode is used if the
modem is integrated into a handheld terminal that
supports voice communications.
• Digital Audio: Digital audio is provided by the Motorola
Proprietary DSC interface. This interface is used when an
external handset, like that used in an automotive
installation, is used. In this case, the call controls are
provided on the handset. DSC handsets that support this
interface are manufactured by and available from
Motorola. The AT command set can also be used to
control calls. The DSC interface is a Motorola proprietary
feature that requires licensing from Motorola. Please
contact your Motorola representative for more
information.
4.2.1.1 Configuration Setup and Audio
Routing in g18
Voice Connectivity
The g18 is an OEM data and voice module. Voice
connectivity can be performed using two main channels:
analog voice and digital voice.
27
Software Interface

The audio route for the different devices is described in the • Echo Suppress - Cancels a small amount of the output
following table, where HF refers to the connected external sound picked up by the input device (suppresses the
speaker and microphone, and DHFA refers to the external echo). It is designed to be used where there will be little
car kit. or no echo (for example, in a handset) rather than where
there will be a lot of echo (for example, in a hands-free
Table 9. Voice Connectivity device).
• Echo Cancel - Suppresses a large amount of the output
Configuration Setup Audio Route to…
sound picked up by the input device (cancels all echo).
Off hook handset (overrides Handset • Noise Suppress - Improves audio quality in all modes.
all other conditions) There are two AT commands that support enabling/disabling
the Echo Cancellation and Sidetone characteristics, as
On hook handset, or follows:
absence of handset:
• ATS96=1 enables the Echo Cancellation, which is the
•HF + HF was selected by •HF external speaker main HF mode characteristic.
ATS96 command with echo cancelling
• ATS94=1 enables Sidetone (default). ATS94=0 mutes
•HF + HF was not selected •HF external speaker, sidetone.
by ATS96 command without echo
cancelling Both AT commands are not allowed when the
Car kit is attached.
•DHFA •DHFA speaker
•Headset + HF was selected •Headset with echo Note
by ATS96 command cancelling The following table shows the relationship between the
•Headset + HF was not •Headset without echo ATS94, the ATS96 and the g18 analog audio behavior when
selected by AT command cancelling the digital handset is omitted or ONHOOK.

Table 10. Regular (HS) and HF Mode using RS232 Hands- Echo Noise
free ATS96 ATS94 Cancella- Suppres- ST
Regular Mode Mode tions sion
Characteristics HF mode
(Handset)
Off 0 0 Disabled Disabled Mute
Echo Cancelling - +
(EC) Disable Enable 0 1 Disabled Disabled Unmute

Sidetone + - On 1 1 Enabled Enabled Mute

Mute
1 1 Enabled Enabled Mute
Echo Suppression + -
(ES) Enable Disable
ATS94 is affected only when ATS96=0.

Full Duplex Half The HF setting (ATS96) is kept in flex, even

Duplex Note after power cycling the g18.

• Sidetone - Reduces the microphone audio input that is

routed to the selected speaker so that the people speaking
will hear themselves talking. This also creates a slight
echo because the speaker sound then gets picked up again
by the microphone and again output to the speaker, and so
on. Echo suppress is designed to take care of this echo.
4.2.2 Data Communication
There are two modes in which to use the data port:
• GPRS: This mode is for package data communication.
This mode starts from the command mode and after an
initialization of a PDP context the data sent from the DTE
will be over PPP. A GPRS wizard is available to do the
PDP connectivity (for PC applications). This is a very
effective tool for transferring data at a high rate and only
when data is available, without the need to dial again.

28 98-08901C39-B
 Software Interface

• CSD - Circuit Switch Data: The default setting for the
g18 is RS232 full flow control. In this mode, data, SMS
and Fax class 1 are transferred using a full flow control
(hardware flow control), Xon/Xoff or non-flow control.
The main difference between this mode and the GPRS
mode is the need to dial the desired number whenever
data needs to be transferred.
4.2.4 Fax Communication
Class 1: This is the basic set of fax commands that is
supported by all types of fax machines. To support fax
communication with g18, use WinFax in your computer.
Class 2: This mode is not supported by the g18.

The g18 supports both transparent and

non-transparent modes.
4.3 BASIC OPERATIONS
Note

4.3.1 Making a Voice Call

4.2.3 SMS Communication
AT+CPIN=”nnnn”, Enter the PIN number which
Table 11. Features Supported using CSD/GPRS if required enables the SIM card (4-8
digits).
CSD Supports
ATDnnnnnn OR Initiates the voice call to the
Flow HW remote phone. The voice
Control Xon/Xoff communications commence.
None AT*Dnnnnn OR Phone book storage should first
be selected at+cpbs=”sm”.
Data Type Transparent ATD><index> OR Phone number corresponding to
Non transparent the name entered.
ATD>”name” OR Phone number from register #1
SMS SMS PDU mode after setting at&z1=035658452.
SMS Block mode ATDS=n (n=0 to Phone number from register #0
3) OR after setting at&z1=035658452.
ATDS=n (n=0 to Phone number from SIM card
Fax Class 1
3) OR #101, for example, ATD>SM101.
ATD><mem><ind Note: Only the second OK for
GPRS Supports
ex> the voice call notifies the user
that the call is established.
Flow HW
Control Xon/Xoff ATH Hangs up the voice call.
None Note: In multi-party calls, ATH
does not end the last call, only
Data Type Data over PPP AT+CHLD=1 does.

Multi Slot Class 1, 2 and 4

1 uplink
4.3.2 Receiving a Voice Call
1,2 or 3 downlinks

Coding CS1, CS2, CS3, CS4 AT+CPIN=”nnnn”, Enter the PIN number that
Schemes if required enables the SIM Card (4 -8
digits).

• Block mode: This is a binary SMS presentation. An

AT+CRC=1 Enables cellular result codes
application SMS build is required for this mode.
extended format. A remote
• Text mode: This mode is not supported by the g18. phone dials the g18 voice
• PDU mode: This is the recommended mode for SMS number.
communications. Note that the PDU packet has a
complex structure, so careful examination of GSM 04.11
and GSM 03.40 is required.

98-08901C39-B 29
Software Interface

4.3.5 Receiving a Data Call

+CRING:VOICE If AT+CRC=1, VOICE indicates
or an incoming voice call.
+RING If AT+CRC=0 then +RING The remote modem dials the g18 data number.
indicates an incoming call.
Note: To retrieve the call type, AT+CRC=1 Enables cellular result codes extended
use the CMER command. format. The remote phone dials the
g18 voice number.
ATA Answers the call
+CRING: If AT+CRC=1, DATA indicates an
REL incoming data call.
ASYNC
4.3.3 Commencing Voice Communication or
+RING If AT+CRC=0, then +RING indicates
ATH Hangs up. Call ends. an incoming call.
or Note: In multi-party calls, ATH does Note: To retrieve the call type, use the
not end the last call, only AT+CHLD=1 CMER command.
AT+CHUP
does.
ATA Answers manually.
If the remote phone hangs up first, the modem will stay ATS0=1 enables an automatic answer
online, (AT+CPAS returns +CPAS:004) for after one ring.
approximately 60 seconds, at which point it will time out
and the call will be cleared (AT+CPAS returns +CPAS: +++ Escapes from Online mode.
000). At any time during this period, the modem can
execute an ATH command. ATH or Hangs up call.
AT+CHUP Note: In multi-party calls, ATH does
not end the last call, only AT+CHLD=1
4.3.4 Making a CSD - Data Call does.

If the remote phone hangs up first, the modem will stay

ATDnnnnnnn Dials the remote modem. online (+CPAS:004) for approximately 60 seconds, at
which point it will time out and the call will be cleared
CONNECT Indicates that the connection is (+CPAS: 000). At any time during this period, the
xxxx made. Proceeds with data modem can execute an ATH command.
communications.

+++ Escapes to Command mode.

4.3.6 Enabling Cell Broadcast (CB)
ATO Returns to Online mode. Reception
+++ Escapes to Command mode. Send AT+CKPD=”M>>S>>>>>S<SCC”

ATH or Hangs up the connection. In order to receive the CB message on the TE, use the
AT+CHUP AT+CNMI command.
For example:
AT+CNMI=0,2,2,0,0
When using different SIM cards, the above
sequence might be changed, accordingly.

Note

30 98-08901C39-B

4.3.7 Setting Up the g18 in CSD Mode
When a data call is received, the RI signal goes to Active
Low for one second and then to Inactive High for four
seconds repeatedly, as shown below.
Figure 32. RI Waveform
When a data carrier is detected by the g18, it sets the DCD
signal to Active Low.
The g18 does not support non-transparent CSD
with a baud rate of less than 4800 bps.
Note
Figure 33. g18 Receiving a Data Call
4.4 SENDING AND RECEIVING DATA IN
DIFFERENT FLOW CONTROLS
4.4.1 Flow Control Set to Hardware Flow
Control (FC)
4.4.1.1 Sending Data
When data is sent by the g18, the only dynamic signals
through the data transfer are TXD and CTS. The DTE device
should be kept at DTR ON.
TXD is used in order to transmit the data from the terminal
to the g18, and CTS is used in order to control the data flow.
When data is transferred too rapidly to the modem, at a rate
which is greater than its transfer rate, and its buffers become
full, the modem sets CTS to Inactive High, until it completes
the transfer.
98-08901C39-B
Software Interface
When the modem is ready to accept more data, it sets the
CTS signal to Active Low again.
Figure 34. g18 Sending Data Hardware Flow Control
4.4.1.2 Receiving Data
When data is received by the g18, the only dynamic signal
during the data transfer is RXD, with which the data is sent
to the terminal. The DTE device should keep DTR ON. RTS
can be used to alert the g18 that the DTE buffer is full.
Figure 35. g18 Receiving Data Hardware Flow Control
4.4.2 Flow Control - Flow Control Set to
Xon/Xoff
The g18 should be configured to Xon/Xoff flow control,
using AT&K4.
To return to the hardware flow control, use AT&K3.
4.4.2.1 Sending Data
When data is sent in this mode, it is transferred on the TXD
line. The DTE device should keep DTR ON.
When data is transferred too rapidly to the modem, its
buffers may become full, and the transmission cannot
succeed. In this case, it sends an Xoff signal to the terminal
on the RXD line.
When the modem has sent the data in the buffer and is ready
to receive more data, it sends an Xon signal on the RXD line.
31
Software Interface

4.4.3.2 Receiving Data

.

When data is received by the g18, the only dynamic signal

during the data transfer is RXD, with which the data is sent
to the terminal. The DTE device should keep DTR ON.

Figure 36. Sending Data Xon/Xoff

4.4.2.2 Receiving Data

Figure 39. g18 Receiving Data in None FC
When data is received in Xon/Xoff flow control, the data is
transferred from the g18 to the terminal on the RXD line.
The DTE device should keep DTR ON.
4.5 CALL WAITING, CALL FORWARD-
ING, AND CONFERENCE CALLS
These operations are network dependent, and
are not supported by some networks. Some
networks behave unexpectedly, such as
Note roaming or call dropout.

Figure 37. g18 Receiving Data Xon/Xoff

4.6 SENDING AN SMS

In the figure above, the Z Modem transfer

protocol was used, with crash recovery setup. 4.6.1 Sending an SMS in PDU Mode
When an error is encountered, the terminal
Note sends a message to the sending side, asking it
to resend the specific block. AT+CPIN=”nnnn” Enter the PIN number that
enables the SIM card
(4 - 8 digits).

4.4.3 Flow Control Set to None AT+CSMS=0 Select message service

response. The response
The g18 should be configured to Xon/Xoff, using AT&K0. will be
+CSMS:001,001,001.
To return to the hardware flow control, use AT&K3.
AT+CPMS=”SM” Select preferred message
4.4.3.1 Sending Data storage. The response
When data is sent in this mode, it is transferred on the TXD will be similar to
line, and there is no flow control. The DTE device should +CPMS:001,0015,001,01
keep DTR ON. 5, depending on your SIM
card.
When the modem cannot keep up with the rate of data
transmission from the terminal, an error occurs. AT+CMGS=
<length of TPDU><cr>

<SCA><TPDU><ctrl-Z> <SCA>: Service Center

Address, refer to GSM
04.11
<TPDU>: Transport
Protocol Data Unit, refer
to GSM 03.40
Figure 38. Sending Data in None FC

32 98-08901C39-B

For example:
AT+CMGS=19
>07914483056100F511000B914410927856F40000000541
E1905804<0x1A>
will return +CMGS:000 after sending “ABCDE” to phone
number 44-012-987-654 via the SMS center at
44-385-016-005.
This is an example only. This particular SMS
center is a UK number.
Note
The following ASCII string is the ASCII representation of
the hexadecimal values that will be transmitted as a binary
string.
‘F’’4’ below means that the hexadecimal values 0xF and 0x4
will be transmitted over the air. CMGS=19 is the length of
the TPDU in octets, see below.
The message is terminated with a Control-Z
character (0x1A).
Note
AT+CMGS=19
>07914483056100F511000B914410927856F40000000541
E190F804<CTRL-Z>
07 = LENGTH OF SCA element including the TON/NPI
91 = TON/NPI,TON=9=Type of number, NPI=1=Number-
ing Plan Identifier
4483056100F5 SCA =SERVICE CENTER ADDRESS
(This means that the real phone number for the SCA is
44-385-016-005).
Explanation of phone number coding: One hexadecimal
digit for each phone number digit is used. Each pair of hexa-
decimal digits is considered an octet (8 bit binary number).
Then, the two hexadecimal digits are reversed in order to
form a semi-octet. So, the phone digits 3, 8 will become 0x3,
0x8, then 0x38, and then reversed to become 0x83. The
ASCII characters ‘8’ and ‘3’, the string ‘83’ are then inserted
into the full ASCII string above. Since there is an odd
number of digits, the last digit, 5, is placed in the lower
nibble of the last octet and then its top nibble is filled with
1s. This means that ‘5’ becomes 0x5, then 0x05, then 0xf5,
and then ‘f5’, which are the last two characters in the Service
Center address.
Refer to ETSI 04.11 for more details.
98-08901C39-B
Software Interface
Looking at the remainder of the message after the SCA, we
find the Transport Protocol Data Unit (TPDU). The TPDU
contains the destination device address (phone number), and
the user data or message. There are 38 characters, which
represent 19 octets, this being the length of the TPDU.
11000B914410927856F40000000541E190F804 = TPDU
11 = 8 bits MTI,RD,VPF,SRR,UDHI,RP,MMS,SRI
00 = MR Message Reference
0B914410927856F4 = DA Transport Destination
Address
0B = Number of digits (11) in phone number
91=TON/NPI (as above)
4410927856F4 = Destination phone number
44-012-987-654
The destination phone number is converted to
an ASCII string in the same manner as the
SCA.
Note
The user data control information and the user data follow
the phone number:
0000000541e190f804
00 = PID Protocol ID
00 = DCS Data Coding Scheme
00 = VP Validity Period
05 = UDL User Data Length
41E190F804 = The user data ‘ABCDE’
Description of encoding the user data: The user data is
encoded as GSM characters. The GSM character set is a
method of encoding 7 bit ASCII characters into 8 bit
numbers. GSM only supports 128 characters with ASCII
values 0x00 to 0x7f. Since these only need 7 bits to define
them, and the SMS message is transmitted as a series of 8-bit
values, GSM uses a method of packing the series of 7 bit
values into 8 bit octets. For example:
ABCDE is encoded as 41E190F804 as follows.
A B C D E
in ASCII hexadecimal is:
0x41 0x42 0x43 0x44 0x45
in 8 bit binary is:
01000001 01000010 01000011 01000100 01000101
33
Software Interface

The most significant bit is truncated, resulting in a series of 4.6.4 Receiving an SMS
seven bit values. The now unused most significant bit(s) are
packed with enough least significant bits from the following
value to make up eight bits. AT+CPIN="nnnn" Enter the PIN which enables
the SIM card (4 -8 digits).

AT+CSMS=0 Selects the message service.

AT+CPMS="SM" Selects the preferred message

storage.

This results in the string of eight-bit hexadecimal numbers AT+CNMI=0,1 Allows buffering of unsolicited
0x41, 0xE1, 0x90, 0x58, 0x04. By continuing this process, a result codes in the TA.
string of 160 ASCII characters can be stored as a string of Indication of memory location is
140 bytes (octets). routed to TE.

The Service Center Address is described in +CMTI: "SM",001 Is displayed (001 message
ETSI GSM 04.11. location).
The Transport Protocol Data Unit is described in ETS GSM
03.40. To display incoming messages:

Sending and receiving of SMS messages

AT+CMGL=4 Lists all the stored messages.
interfere with each other when the time interval
between them is too short, or when both
Note operations take place simultaneously. AT+CMGR=1 Reads the message at location
001.

+CMGR: 000,,102
4.6.2 Sending an SMS in PDU Mode -
0380214304028021000069905
Wave Forms 02100000064D227925804994
0D321F21A946A4153F45B4E
0735CBF379F85C064DCB727
4.6.3 Sending an SMS in CSD Mode B7A5C0651CB73BA0B444597
41D17A7ABC0609E5EFBB1B
When sending an SMS in PDU mode, after executing the 647CE341CA7A1B3E073DED
at+cmgs=n command, the DCD line goes to Active Low, 6539888A2E8398617D1E447C
9F5DA0986C46ABD96EB81C
and the data is transferred on the TXD line.
4C01.
After executing the <Ctrl+Z> command, the DCD line OK.
returns to Active High, and the message is sent via the
phone.
Once the message has been received, the next step is to
decode it into something comprehensible. This particular
message is generated by a Rohde and Schwarz CMD55
GSM Test station. In the first line of data, we see the
information about the service center, followed by the TPDU.
038021430402802100006990502100000064D2279258049
940D321F21A946A4
03 = Length of service center address
80 = Type of number = unknown, number plan identifier =
unknown
2143 = Service center address = 1234
Figure 40. Sending an SMS
04 = MTI = SMS-DELIVER, MMS = no more
messages, SRI = no status report UDHI = no UD
header, RP = reply path not set

34 98-08901C39-B
 Software Interface

02 = OA length & SCHWARZ THE QUICK BROWN FOX JUMPED

80 =TON = unknown, NPI = unknown
21 = OA = 12
00 = PID =Protocol ID
00 = DCS = Data Coding Scheme
69905021000000=SCTS Service
Center Time Stamp =
5th Sept. 1996 12:00:00 GMT
64=UDL=User
Data Length=100
octets
Following is the user data:
OVER THE LAZY DOG.
4.6.5 Sending and Receiving Binary Data
Via SMS
Your specific application may require binary data to be sent,
instead of an ASCII text message. In this case, you can
simply insert your raw data as the user data, instead of using
the GSM character coding process. This limits you to 140
octets of data. So long as your application controls the
encoding and decoding of the SMS PDUs at either end of the
solution, you can use the 140 octets of user data as you see
fit.

D2279258049940D321F21A946A4153F45B4E0735CBF3
79F85C064DCB727B7A5C0651CB73BA0B44459741D1
4.6.6 Receiving an SMS in CSD Mode -
7A7ABC0609E5EFBB1B647CE341CA7A1B3E073DED6
539888A2E8398617D1E447C9F5DA0986C46ABD96EB Wave Forms
81C4C01
When an SMS is received, it is stored on the SIM card.
This is a string of GSM characters, which must be translated
back into ASCII. The process is the reverse of the coding Figure 41 shows a reading command sent on the TXD line,
process described previously. This converts the characters and the message transferred from the SIM card to the
back from a series of octets to a series of 7 bit ASCII terminal.
numbers.
Looking at the first 6 octets:

This decoding process continues for the entire user data

string. Translating the entire string comes up with ROHDE Figure 41. Receiving an SMS

98-08901C39-B 35
Software Interface

4.6.6.1 SMS Error Messages

Message Types

#define MMISMS_MSG_TYPE_LIST_REQUEST 0x00

#define MMISMS_MSG_TYPE_GET_MESSAGE 0x01

#define MMISMS_MSG_TYPE_GET_FIRST_MESSAGE 0x02

#define MMISMS_MSG_TYPE_GET_NEXT_MESSGAE 0x03

#define MMISMS_MSG_TYPE_TRANSFER_INC_SMS 0x04

#define MMISMS_MSG_TYPE_INDICATE_INC_SMS 0x05

#define MMISMS_MSG_TYPE_TRANSFER_INC_CBS 0x06

#define MMISMS_MSG_TYPE_INSERT_SMS 0x07

#define MMISMS_MSG_TYPE_DELETE_MESSAGE 0x08

#define MMISMS_MSG_TYPE_TE_UNABLE_TO_PROCESS 0x09

#define MMISMS_MSG_TYPE_TE_SET_MESSAGE_REQUEST 0x0A

#define MMISMS_MSG_TYPE_TE_BEGIN_SMS_MODE 0x1d Added to support 07.05

#define MMISMS_MSG_TYPE_TE_END_SMS_MODE 0x1e

#define MMISMS_MSG_TYPE_ACKNOWLEDGE_MESSAGE 0x1f

#define MMISMS_MSG_TYPE_MESSAGE_LIST 0x20

#define MMISMS_MSG_TYPE_MESSAGE 0x21

#define MMISMS_MSG_TYPE_GET_MESSAGE_FAILURE 0x22

#define MMISMS_MSG_TYPE_INC_MESSAGE 0x23

#define MMISMS_MSG_TYPE_MESSAGE_ARRIVED 0x24

#define MMISMS_MSG_TYPE_INSERT_SMS_COMPLETE 0x25

#define MMISMS_MSG_TYPE_INSERT_SMS_FAILURE 0x26 38

#define MMISMS_MSG_TYPE_DELETE_MESSAGE_COMPLETE 0x27

#define MMISMS_MSG_TYPE_DELETE_MESSAGE_FAILURE 0x28

#define MMISMS_MSG_TYPE_MT_UNABLE_TO_PROCESS 0x29

36 98-08901C39-B
 Software Interface

Message Types

#define MMISMS_MSG_TYPE_REQUEST_CONFIRMED 0x2a

#define MMISMS_MSG_TYPE_SET_MESSAGE_CONFIRMED 0x2b

#define MMISMS_MSG_TYPE_SET_MESSAGE_FAIL_CONFIRMED 0x2c

#define MMISMS_MSG_TYPE_MT_END_SMS_MODE 0x3f

Information Element Identifier

#define MMISMS_IEI_SHORT_MSG_REF 0x00

#define MMISMS_IEI_TRANSFER_TYPE 0x01

#define MMISMS_IEI_INDICATE_TYPE 0x02

#define MMISMS_IEI_INSERT_TYPE 0x03

#define MMISMS_IEI_SHORT_MSG_INDEX 0x04

#define MMISMS_IEI_CBS_SHORT_MSG_INDEX 0x05

#define MMISMS_IEI_SHORT_MSG_DATA 0x06

#define MMISMS_IEI_CBS_SHORT_MSG_DATA 0x07

#define MMISMS_IEI_CAUSE 0x08

#define MMISMS_IEI_INDEX_COUNT 0x09

#define MMISMS_IEI_CBS_TRANSFER_TYPE 0x0A

#define MMISMS_IEI_PAGE_INDEX 0x0B

#define MMISMS_IEI_LAST_SHORT_MSG 0x0C

#define MMISMS_IEI_CONFIRM_TYPE 0x0D

#define MMISMS_IEI_TP_FAILURE_CAUSE 0x0E

98-08901C39-B 37
Software Interface

Transfer CBS Types

#define MMISMS_CBS_TRANSFER_TYPE_NO_CBS 0x00

#define MMISMS_CBS_TRANSFER_TYPE_TE_SPECIFIC 0x01

#define MMISMS_CBS_TRANSFER_TYPE_RESERVED 0x02

#define MMISMS_CBS_TRANSFER_TYPE_ALL_CBS 0x03

#define MMISMS_CBS_TRANSFER_TYPE_BIT_MASK 0x03 first two bits

#define MMISMS_CBS_TRANSFER_TYPE_RESERVED_BIT_MASK 0xFC bits 3 to 8

Indicate Types

#define MMISMS_INDICATE_TYPE_NO_MSG 0x00

#define MMISMS_INDICATE_TYPE_RESERVED 0x01

#define MMISMS_INDICATE_TYPE_ALL_SMS 0x02

#define MMISMS_INDICATE_TYPE_TE_SPECIFIC_SMS 0x03

#define MMISMS_INDICATE_TYPE_ALL_CBS 0x04

#define MMISMS_INDICATE_TYPE_TE_SPECIFIC_CBS 0x05

#define MMISMS_INDICATE_TYPE_ALL_CBS_SMS 0x06

#define MMISMS_INDICATE_TYPE_ALL_TE_SPECIFIC_MSG 0x07

#define MMISMS_INDICATE_TYPE_REPORT 0x08

#define MMISMS_INDICATE_TYPE_BIT_MASK 0x07 first three bits

#define MMISMS_INDICATE_TYPE_REPORT_BIT_MASK 0x08 fourth bit

#define MMISMS_INDICATE_TYPE_RESERVED_BIT_MASK 0xF0 bits 5 to 8

38 98-08901C39-B
 Software Interface

Cause Values

#define MMISMS_CAUSE_NO_SUCH_MESSAGE 0x00

#define MMISMS_CAUSE_NO_MEMORY 0x01

#define MMISMS_CAUSE_NO_AIR_INTERFACE 0x02

#define MMISMS_CAUSE_RECEIVING_ENTITY_BUSY 0x03

#define MMISMS_CAUSE_COMMAND_NOT_UNDERSTOOD 0x04

#define MMISMS_CAUSE_INCOMING_DATA_CALL 0x05

#define MMISMS_CAUSE_USER_INVOKED_EXIT 0x06

#define MMISMS_CAUSE_MESSAGE_TRANSFER_FAILED 0x87

Short Message Statuses

#define MMISMS_STATUS_NOT_READ 0x00

#define MMISMS_STATUS_NOT_SENT 0x00

#define MMISMS_STATUS_NOT_READ_SENT 0x00

#define MMISMS_STATUS_READ 0x01

#define MMISMS_STATUS_SENT 0x01

#define MMISMS_STATUS_READ_SENT 0x01

Confirm Types

#define MMISMS_CONFIRM_TYPE_BEGIN_SMS_REQ_CNF 0x00 Added to support 07.05

#define MMISMS_CONFIRM_TYPE_TRANSFER_INC_SMS_REQ_CNF 0x01

#define MMISMS_CONFIRM_TYPE_TRANSFER_INC_CBS_REQ_CNF 0x02

#define MMISMS_CONFIRM_TYPE_INDICATE_INC_SMS_REQ_CNF 0x03

#define MMISMS_CONFIRM_TYPE_ATTEMPT_SEND_SMS_REQ_CNF 0x04

98-08901C39-B 39
Software Interface

Number of SMS Message Headers per Page

#define MMISMS_NUM_HEADERS_PER_PAGE 5

#define MMISMS_MIN_PAGE_INDEX 1

#define MMISMS_MAX_PAGE_INDEX 51

Text Mode and PDU Mode Error Values

#define MMISMS_ERROR_ME_FAILURE 300

#define MMISMS_ERROR_ME_SMS_SERVICE_RESERVED 301

#define MMISMS_ERROR_OPERATION_NOT_ALLOWED 302

#define MMISMS_ERROR_OPERATION_NOT_SUPPORTED 303

#define MMISMS_ERROR_INVALID_PDU_MODE_PARAMETER 304

#define MMISMS_ERROR_INVALID_TEXT_MODE_PARAMETER 305

#define MMISMS_ERROR_SIM_NOT_INSERTED 310

#define MMISMS_ERROR_SIM_PIN_NECESSARY 311

#define MMISMS_ERROR_PH_SIM_PIN_NECESSARY 312

#define MMISMS_ERROR_SIM_FAILURE 313

#define MMISMS_ERROR_SIM_BUSY 314

#define MMISMS_ERROR_SIM_WRONG 315

#define MMISMS_ERROR_MEMORY_FAILURE 320

#define MMISMS_ERROR_INVALID_MEMORY_INDEX 321

#define MMISMS_ERROR_MEMORY_FULL 322

#define MMISMS_ERROR_SMSC_ADDRESS_UNKNOWN 330

#define MMISMS_ERROR_NO_NETWORK_SERVICE 331

#define MMISMS_ERROR_NETWORK_TIMEOUT 332

#define MMISMS_ERROR_UNKNOWN_ERROR 500

40 98-08901C39-B
 Software Interface

Text Mode and PDU Mode Error Values (Continued)

#define MMISMS_SUCCESS 512

#define TD_SMS_RP_CAUSE_MASK 127 0x7F (MSB of RP-Cause

is an ext bit)

#define TD_SMS_RP_CAUSE_NUM_MO_RP_CAUSES 22

#define TD_SMS_RP_CAUSE_NUM_MT_RP_CAUSES 8

#define TD_SMS_RP_CAUSE_UNASSIGNED_NUMBER 1

#define TD_SMS_RP_CAUSE_OPERATOR_BARRING 8

#define TD_SMS_RP_CAUSE_CALL_BARRED 10

#define TD_SMS_RP_CAUSE_SM_TRANSFER_REJECTED 21

#define TD_SMS_RP_CAUSE_MEMORY_CAPACITY_EXCEEDED 22 (MT specific)

#define TD_SMS_RP_CAUSE_DESTINATION_OUT_OF_ORDER 27

#define TD_SMS_RP_CAUSE_UNIDENTIFIED_SUBSCRIBER 28

#define TD_SMS_RP_CAUSE_FACILITY_REJECTED 29

#define TD_SMS_RP_CAUSE_UNKNOWN_SUBSCRIBER 30

#define TD_SMS_RP_CAUSE_NETWORK_OUT_OF_ORDER 38

#define TD_SMS_RP_CAUSE_TEMPORARY_FAILURE 41

#define TD_SMS_RP_CAUSE_CONGESTION 42

#define TD_SMS_RP_CAUSE_NO_RESOURCES 47

#define TD_SMS_RP_CAUSE_FACILITY_NOT_SUBSCRIBED 50

#define TD_SMS_RP_CAUSE_FACILITY_NOT_IMPLEMENTED 69

#define TD_SMS_RP_CAUSE_INVALID_RP_MR 81 Bad RP-MR

#define TD_SMS_RP_CAUSE_SEMANTICAL_ERROR 95 Error in an IE

#define TD_SMS_RP_CAUSE_MANDATORY_IE_ERROR 96 Mandatory IE missing/

has error

98-08901C39-B 41
Software Interface

#define TD_SMS_RP_CAUSE_RP_MT_NOT_IMPLEMENTED 97 Specific message type

not supported

#define TD_SMS_RP_CAUSE_BAD_STATE 98 RP-MT not compatible

with SM-RL state

#define TD_SMS_RP_CAUSE_IE_NOT_IMPLEMENTED 99 IE missing or

nonexistent

#define TD_SMS_RP_CAUSE_UNSPECIFIED_ERROR 111 Protocol error

unspecified

#define TD_SMS_RP_CAUSE_INTERWORKING_ERROR 127

#define TD_SMS_RP_CAUSE_SUCCESS 128 INTERNAL MOTOROLA

DEFINITION

#define TD_SMS_RP_CAUSE_SUCCESS_ACK 129 INTERNAL MOTOROLA

DEFINITION

#define TD_SMS_RP_CAUSE_NO_TRANSACTION_ID 253 INTERNAL MOTOROLA

DEFINITION

#define TD_SMS_RP_CAUSE_CM_INTERNAL_ERROR 254 INTERNAL MOTOROLA

DEFINITION

#define TD_SMS_RP_CAUSE_RL_TIMEOUT 255 INTERNAL MOTOROLA

DEFINITION

SMS TIMERS

#define TD_TIMER_LENGTHS_CMSMS_TC1M 20000 20 sec for both mob.

orig. and mob. term.
SMS CM

#define TD_TIMER_LENGTHS_MMISMS_TR1M 45000 45 sec for SMS mobile

originated relay layer
TR1M timeout

#define TD_TIMER_LENGTHS_MMISMS_TRAM 35000 35 sec for SMS memory

available relay layer
TRAM timeout

#define TD_TIMER_LENGTHS_MMISMS_SHORTCUT_MSG_TIMEOUT 60000 60 sec for "Message -

Read Now?" message
window timeout

#define TD_TIMER_LENGTHS_MMISMS_TL_IP_ACK 60000 msec

#define TD_TIMER_LENGTHS_MMIIPS_IP_RING_IND_VALUE 5000 msec

42 98-08901C39-B
 Software Interface

SMS TIMERS

#define TD_TIMER_LENGTHS_MMISMS_VIAG_SCAN 60000 60 sec timer in msec

#define MMISMS_SET_TR1M_TIMER (1) Used by send_timer

method to determine
which timer task port a
timer primitive is sent to.

#define MMISMS_RESET_TR1M_TIMER (0)

4.6.7 Sending a Fax
4.6.7.1 Installing the Modem Driver
From the Control Panel, select Modems > Add modem
> Next > (Windows finds "standard modem" on one of the
COM ports) > Change > Have Disk > Enter the path to
modem driver (for example, D:\motorola\modem) and select
L-series > Next > Finish. (You may have to restart before
using the modem.)
4.6.7.2 Configuring the Modem in WinFax
• Using the AT+CGATT=1 command. You can check your
connection status by using the AT+CGATT? command
AT+CGDCONT=1,"IP","RTY","123.32.45.9
Following are the three main ways in which to activate PDP
context:
1. If the GPRS Wizard application is used, double-click
the button predefined as the dialer for this provider to
automatically establish PDP context. If the g18 was not
previously attached to GPRS, it will be attached
automatically.
Setup Configuration

1. Run WinFax. 1. Enter into the wizard parameters provided by your

2. Select Tools > Program Setup > Modems
and Communications Devices > Properties.
3. Set Motorola L Series to Active (WinFax begins
testing the modem and the result is Failed. This result
is acceptable).
4. Click Next and select CLASS 1 (Hardware Flow
Control) > Next > Finish, set Default (or other) > OK .
5. In the Modem and Communications Devices Proper-
ties window, click Properties.
6. In General > Communications port, set the COM port
to which the modem is connected and initialize it at
57600 bps.
4.6.8 Establishing GPRS PDP Context
When using the GPRS Network for HTTP/FTP browsing,
you must be attached to the GPRS Network before activating
PDP context.
Connection may be performed in one of the following two
ways:
• Automatically after powering up your MS. The GPRS
logo is displayed on your screen.
operator.
2. Set definitions to allow your http\ftp browser to use
the g18 as a port to the Internet.
Usage
1. Open the GPRS Manager.
2. Double-click the dialer icon to select and activate the
provider of your choice (multiple providers may be
displayed in the list).
3. After dialing, your temporary IP address and then the
GPRS DATA session message will be displayed on
the handset.
4. Minimize the GPRS wizard window and use your
http\ftp browser (Internet Explorer, Netscape).
2. If you use AT commands to activate PDP context, you
must perform the following steps:
1. Define the PDP contact (profile).
For example: AT+CGDCONT=1,"IP","RTY","
2. Define Quality of Service.
For example: At+CGQREQ=3,2,4,5,8,12
3. Define minimum acceptable Quality of Service.
For example: At+CGQMIN=1,0,0,0,0
4. Activate PDP context using the AT+CGACT=1
command.

98-08901C39-B 43
Software Interface
Bear in mind that the AT command AT+CGACT
is not supported in all countries with GPRS. A
GPRS connection is also possible with
Note ATD*99#. See the following section for more
information.
Setup Configuration
AT+CGQMIN=1,0,0,0,0,0
AT+CGQREQ=1,0,0,0,0,0
AT+CGCONT=1,"IP","APN","0.0.0.0",0,0 // APN –
replace it with the provider name
AT
AT &F0 &D2 &C1 E0
AT V1 W1 S95=47
AT&K3
ATD*99#
The above list is only for the AT command level.
PPP information (DNSs) is not shown here.
Note
3. Using the ATD* command set: The GSM 07.07 version
7.5.0, Chapter 10.2.1.1 states:
Request GPRS service 'D':
D*<GPRS_SC>[*[called_address>][*[L2P][*<cid>]]]
]#
The g18 supports TCP/IP protocol only, and this
command can be used in the following format:
ATD*99***(CID)#
The CID includes the APN (defined by the
AT+CGDCONT command) to which you want to be
connected. (This depends on the ability of the SIM card
to be attached to the different networks)
The format ATD*99# may also be used. In this case, the
g18 will first try to activate a non-empty (predefined)
CID. If the attempt fails, the g18 will try the next CID,
and so on.
4.6.9 Changing the PIN Code Number
1 Check your CPIN status. If AT+CPIN? returns +CPIN:
READY then proceed to the next step.
If AT+CPIN? returns +CPIN: SIM PIN, enter the PIN
number and recheck whether the status is READY.
2 Check that AT+CLCK="SC",2 returns +CLCK: 1,7. If
not, send AT+CLCK="SC",1, your PIN# command.
44
When buffering the DTE message data in the
g18 (both inbound and outbound data), the
following apply:
Note
•Turning off the g18 clears any buffered data.
•Removing power from the g18 clears any
buffered data.
•Whenever the DTE drops the PPP connection
with the g18, via LCP terminate, the buffered
data is cleared.
•Whenever the g18 drops the PPP connection
with the DTE, with LCP terminate, the buffered
data is cleared. LCP termination triggers the
termination of the data in the g18 buffer.
•Whenever the g18 drops the PPP connection
with the DTE, without an LCP terminate, the
buffered data is cleared. Dropping the DTR
also clears the buffer.
•When the network sends a deactivation
message or a detached message, the g18
buffer is cleared.
•When the g18 transfers data in the uplink and
GPRS coverage is lost, the data may flow-off.
If the mobile has lost coverage and is unable to
send the packets from the DTE to the network,
the buffers will continue to store the packets
until the buffers are full. The DTE will then be
flowed off and the packets will be stored until
they can be sent to the GPRS network.
•The amount of time that takes before the user
is notified is specified in the T3312 timer that is
located in the mobile side. The default delay
time of T3312 is 54 minutes, as per the GSM
0408 specification. After 54 minutes, the g18
deactivates the PDP session.
3 You can now change the PIN number by using the
+CPIN command as follows:
AT+CPIN=Old PIN#, New PIN#
4.6.10 Writing into the Fix Dialing (FD)
Phone Book
Send AT+CLCK="FD",2 (Query Status)
If the response is: +CLCK: 1,7-
Enter AT+CLCK="FD",0,"PIN2".
After receiving OK, write operations are allowed in the FD
area.
If the response is: +CLCK: 0,7
enter AT+CLCK="FD",1,"PIN2",
OK,
then enter AT+CLCK="FD",0,"PIN2".
98-08901C39-B
 Software Interface

After receiving OK, write operations are allowed in the FD Possible explanations could be “Fixed Dial Phonebook not
area. available” or “No memory space available on the SIM card
for the fixed Dial Phonebook”.
at+cpbs="fd"
OK
at+cpbw=10,"123",,"time" 4.7 BASIC AT COMMANDS
ERROR Table 12 lists the basic AT commands for the g18 modem.
Most of the basic commands are from the V.25ter reference.
at+clck="fd",2 Commands shown in bold are factory defaults.
+CLCK: 0,7 The format of the command is:
OK AT<command>
at+clck="fd",0,"7391" For example: ATE0 will turn off the echo command.
OK To repeat the command, use the command A/
which will repeat the previous command. This is
at+clck="fd",2
not prefixed with AT.
Note
+CLCK: 0,7
OK
at+cpbw=10,"123",,"time" Table 12. Basic Call Control Commands (Including
OK V.25ter)

The following is an example of a SIM card that is configured Command Function

with the Fixed Dial number phonebook of 0 possible entries:
at+cmee=2 A Goes off-hook and attempts to answer
a call.
OK
at+clck=? Dn Dial modifier. For voice calls use
ATDxxx;
+CLCK: or AT*Dxxxx or ATD>102
("CS","SC","AO","OI","OX","AI","IR","AB","AG","AC", or ATD>"DAN" or ATDS=1
"FD") or ATDS=0
or ATD>SM101.
OK
at+clck="FD",2 E0 Turns off command echo.

+CLCK: 3,7
E1 Turns on command echo.
OK
at+cpbs=? F No action, compatibility only.

+CPBS: ("FD","LD","ME","MT","SM","DD","RC") H Initiates a hang-up sequence.

OK
I0 Reports product code.
at+clck="FD",0,"8625"
OK I1 Reports pre-computed checksum.

at+clck="FD",2
I2 Reports processor name.
+CLCK: 0,7
I3 Reports firmware revision.
OK
at+cpbs="FD" I4 Reports product name.
+CME ERROR: "operation not allowed"

98-08901C39-B 45
Software Interface
Table 12. Basic Call Control Commands (Including
V.25ter) (Continued)
Command Function
I6 Reports processor name.
L No action, compatibility only.
M No action, compatibility only.
N No action, compatibility only.
P No action, compatibility only.
O Goes on-line.
Q0 Allows result codes to the DTE.
Q1 Inhibits result codes to the DTE.
Sn=x Sets value x for S-register n.
Sn? Returns the value of S-register n.
S0 Reads/sets the number of rings before
Automatic Answer.
S2 Reads/sets Escape code character.
When Escape characters equals 255
(ats2=255), Escape characters are
ignored while in data transfer mode.
S3 Reads/sets Carriage return code
character.
S4 Line feed code character.
S5 Command line editing character.
Note: In command line editing, all
characters with a hexadecimal value of
0 to $1F, except for Backspace, Line
Feed and Carriage Return, are ignored.
S7 Wait time for data call carrier.
S24 ATS24=0 The g18 is not in sleep mode.
ATS24=# The g18 is in sleep mode and
will enter sleep mode after # seconds.
Refer to “How/When to Wake Up the
Unit”, page 16.
46
Table 12. Basic Call Control Commands (Including
V.25ter) (Continued)
Command Function
Sn for n Bit map registers.
equal to
14, 21, 22,
31, 36, 39,
40, 41
S95 Bitmap register for extended result
code.
S96 Echo cancelling feature for audio
devices by ATS96=1.
S97 Antenna diagnostic feature: ATS97?
responds with 000 or 001.
000 means that either the antenna is
not connected or the hardware does not
support this feature.
S98 ATS98=1 allows the handset’s backlight
to behave as if the unit was not
powered by using the TS line. It will turn
off the backlight immediately, for the
first time after powering up.
Note: ATS98=x is allowed only for x=1.
S99 ATS99=x to define the length in ms of
the hardware pulse given when the
GPRS coverage is changed from no
coverage to coverage. The pulse length
is 2x when the data indication is sent.
The default value is 30 ms; 0 value is
not allowed.
S99 responds with an error if the value
is greater than 2,147,483,647 or equal
to zero.
S100 ATS100=x, where x defines the number
of seconds. To avoid frequent hardware
interrupts, the g18 uses hardware
indication for data only after x seconds
from the last sent character to the DTE.
The default value of x is 1 second; 0
value is not allowed.
S100 responds with an error if the value
is greater than 32,767 or equal to zero.
98-08901C39-B
 Software Interface

Table 12. Basic Call Control Commands (Including Table 12. Basic Call Control Commands (Including
V.25ter) (Continued) V.25ter) (Continued)

Command Function Command Function

S101 Sets the wakeup line forever when x=1, Z Resets to default configuration.
and resets it when x=0.
ATS101? returns the current state. &C0 DCD is forced ON at all times.
These operations are allowed only
when the factory bit is set. When the
&C1 DCD is set to ON when the CSD carrier
parameters are wrong, or the factory bit
is detected or when the GPRS session
is not set, it returns an error.
is started.

T No action, compatibility only.

&C2 DCD is set to ON when the PDP is
active and the IP address is received
V0 Reports short form (terse) result codes. from the network.
ATV0 result code information: This command should not be used with
OK 0 a computer dial-up networking
CONNECT 1 program.
RING 2
NO_CARRIER 3 &D0 Interprets the DTR on-to-off transition.
The modem ignores DTR.
ERROR 4
BUSY 7
&D1 Interprets the DTR on-to-off transition.
NO_ANSWER 8 The modem performs as asynchronous
OK without sending any response 9 to command mode.

V1 Reports long form (verbose) result &D2 Interprets the DTR on-to-off transition.
codes. The modem hangs up.

W0 Reports DTE in Error Correction (EC) &D3 Interprets the DTR on-to-off transition.
mode. The modem hangs up.

X0 Reports basic call progress result &F0 Restores the factory configuration 0.
codes:
OK, CONNECT, RING, NO CARRIER &F1 Restores the factory configuration 1.
(also for busy, if enabled, and dial tone
not detected), NO ANSWER, and &G No action, compatibility only.
ERROR.
&J No action, compatibility only.
X1 Reports basic call progress result
codes and connection baud rates:
&K0 Disables all DTE/DCE flow controls.
OK, CONNECT, RING, NO CARRIER
(also for busy, if enabled, and dial tone
&K3 Enables RTS/CTS DTE/DCE flow
not detected), NO ANSWER,
controls.
CONNECT XXXX, and ERROR.

&K4 Enables XON/XOFF DTE/DCE flow

X4 Reports all calls progress result codes
controls.
and connection rates:
OK, CONNECT, RING, NO CARRIER,
&K6 Enables RTS/CTS DTE/DCE flow
NO ANSWER, CONNECT XXXX and
controls.
ERROR.

&L No action, compatibility only.

Y No action, compatibility only.

98-08901C39-B 47
Software Interface

Table 12. Basic Call Control Commands (Including Table 12. Basic Call Control Commands (Including
V.25ter) (Continued) V.25ter) (Continued)

Command Function Command Function

&M No action, compatibility only. AT*A Same as ATA.

&P No action, compatibility only. AT*D Dials voice call numbers.

&Q0 Selects a direct asynchronous mode. AT*P No action, compatibility only.

(This has no effect on the g1,8 since it
only has a non-transparent mode.) AT*V No action, compatibility only.

&Q5 Modem negotiates an error corrected A/ Repeats last command.

link (default). (This has no effect on the
g18, since it only has a non-transparent
AT? Returns the value of the last updated
mode.)
S-Register.

&Q6 Selects an asynchronous operation in

AT$ Lists the supported AT commands.
normal mode. (This has no effect on the
g18, since it only has a non-transparent
mode.)
Table 13. Advanced AT Commands List
&R No action, compatibility only.
Command Function
&S Defines the DSR's behavior. (This is
always active).
+CRTT Selects ring tone.

&T No action, compatibility only.

+CIPE Enables/disables CIP command.

&V Displays the current configuration and

+CIP Sends IP primitives over RS232 (IP
stores the profiles.
primitives are messages used by the
DSC bus).
&W0 Stores the active profile in NVRAM
profile 0.
+CBAUD Selects the baud rate.

&W1 Stores the active profile in NVRAM

+CGPRS Indicates the GPRS coverage.
profile 1.

+MTDTR Supported for DTR line test command.

&Y0 Recalls the stored profile 0 upon power
up.
+MTCTS Supported for CTS line test command.
&Y1 Recalls the stored profile 1 upon power
up. +MCWAK Supported for DTE wake line control
E command.
&Zn=x Stores the dial string x (up to 35
characters) into location n = (0 to 3). +MMGL Lists the messages without changing
their attributes.
\N1 Selects the direct mode. (This has no
effect on the g18, since it only has a +MMGR Reads the message without changing
non-transparent mode.) its attributes.

\N2 Selects the reliable link mode. (This has +MMGA Changes the message attributes.
no effect on the g18, since it only has a
non-transparent mode.) +CMSS Sends the message from storage.

48 98-08901C39-B
 Software Interface

4.8 ERROR CORRECTION AND Table 15. FAX Class Commands

COMPRESSION (ECC) COMMANDS
Command Function Remark
The g18 modem supports the commands listed in Table 14.
"FAE" fax_auto_answer Class 1
Table 14. Supported ECC Commands List
"FRH" fax_receive_hdlc_data Class 1
Command Function
"FRM" fax_receive_data Class 1
%C0 Disables data compression. (This has
no effect on the g18, since it does not
"FRS" fax_receive_silence Class 1
have compression.)

"FTH" fax_transmit_hdlc_data Class 1

%C1 Enables MNP 5 data compression.
(This has no effect on the g18, since it
does not have compression.) "FTM" fax_transmit_data Class 1

%C2 Enables V.42 bis data compression. "FTS" fax_transmit_silence Class 1

(This has no effect on the g18, since it
does not have compression.)
4.10 ETSI 07.07 STANDARD
%C3 Enables both V.42 bis and MNP 5
compression. (This has no effect on the The following tables list the commands defined by ETSI
g18, since it does not have standard 07.07 Phase 1, which are supported by the g18
compression.) modem.
For a more detailed description of ETSI commands, refer to
\A0 Sets the maximum block size in MNP to
64. ETSI document GSM 07.07 — prETS 300 916, GSM 07.05,
GSM 03.40 Sections 9.1 and 9.2, GSM 04.11 Sections
8.2.5.1 and 8.2.5.2, and GSM 03.38.
\A1 Sets the maximum block size in MNP to
128. For each command it is recommended that you use the ?
option to query the modem for the particular details of each
\A2 Sets the maximum block size in MNP to command. For example, use AT+CR? to get the full details
192. on the +CR command.

\A3 Sets the maximum block size in MNP to

256. Table 16. General ETSI 07.07 Commands

\G Uses XON/XOFF flow controls. Not Command Description Reference

supported by the g18.
+CGMI Requests manufacturer 5.1
\S Shows the status of the commands and identification
S-Registers in effect.
+CGMM Requests model 5.2
identification
4.9 FAX CLASS 1 COMMANDS
+CGMR Requests revision 5.3
Table 15. FAX Class Commands identification

Command Function Remark +CGSN Requests product serial 5.4

number identification
"FCLASS" Selects mode 0 – data
1 – fax +CSCS Selects TE character 5.5
Class 1 set

98-08901C39-B 49
Software Interface

Table 16. General ETSI 07.07 Commands (Continued) Table 18. ETSI 07.07 Mobile Extended Error Report

Command Description Reference

Command Description
+CIMI Requests international 5.6
mobile subscriber +CEER Extended error report
identity
+CEER 1 Unassigned or unallocated number
+GCAP Requests overall V25ter ERROR 3 No route to destination
capabilities of TA section
6 Channel unacceptable
6.1.9
8 Operator determined barring
16 Normal call clearing
Table 17. ETSI 07.07 Call Control Commands
17 User busy
and Methods
18 No user responding
19 User alerting, no answer
Command Description Reference
21 Call rejected
22 Number changed
+CSTA Selects type of address 6.1
and selects dial 26 Non selected user clearing
characters allowed in 27 Destination out of order
dial string 28 Invalid number format (incomplete
number)
D Dial modes 6.2 29 Facility rejected
Dial modifiers for 30 Response to STATUS ENQUIRY
V.25ter dialing 31 Normal, unspecified
33 Command aborted
D>X V.25ter: Direct dialing 6.3 34 No circuit/channel available
from phone books
38 Network out of order
where x is the location
41 Temporary failure
42 Switching equipment congestion
+CMOD Call mode 6.4
43 Access information discarded
+CHUP Hangs-up call (similar 6.5 44 Requested circuit/channel
to ATH) unavailable
47 Resources unavailable, unspecified
+CBST Selects bearer service 6.7 49 Quality of Service unavailable
type (baud rate, V110/ 50 Requested facility not subscribed
RLP, and so on.) 55 Incoming calls barred within the
CUG
+CRLP Radio link protocol 6.8 57 Bearer capability not authorized
parameters 58 Bearer capability not presently
available
+CR Service reporting 6.9 63 Service or option not available,
control (result codes) unspecified
65 Bearer service not implemented
+CEER Extended error report 6.10 69 Requested facility not implemented
(report failure reason of 70 Only restricted digital information
last call) bearer capability is available
79 Service or option not implemented,
+CRC Cellular result codes 6.11 unspecified
81 Invalid transaction identifier value
87 User not member of CUG
88 Incompatible destination

50 98-08901C39-B
 Software Interface

Table 18. ETSI 07.07 Mobile Extended Error Report Table 19. ETSI 07.07 Network Service Related
(Continued) Commands (Continued)

Command Description Command Description Reference

+CEER 91 Invalid transit network selection +CTFR1* Reject an incoming call, 7.13
ERROR 95 Semantically incorrect message and divert it to the voice
96 Invalid mandatory information mail (not to another
number)
97 Message type non-existent or not
implemented
+CAOC Advice of charge 7.15
98 Message type not compatible with
protocol state
99 Information element non-existent or +CLCC Lists current calls and 7.17
not implemented asynchronous answers
100 Conditional IE error
+CPOL Preferred operator list 7.18
101 Message not compatible with
protocol state *This command is based on the +CTFR standards.
102 Recovery on timer expiry
111 Protocol error, unspecified
Table 20. ETSI 07.07 Mobile Equipment Control and
127 Inter-working, unspecified Status Commands

Command Description Reference

Table 19. ETSI 07.07 Network Service Related
Commands
+CPAS Phone activity status 8.1
(off, on, online)
Command Description Reference

Return Code - Meaning

+CNUM Subscriber number 7.1
+CPAS:000 - Ready
+CREG Network registration 7.2 +CPAS:001 -
Unavailable
+CPAS:002 - Unknown
+COPS GSM network operator 7.3
selection +CPAS:003 - Ringing
+CPAS:004 - Call in
+CLCK Facility lock 7.4 process
+CPAS:005 - Asleep
+CPWD Changes password 7.5
+CPIN Enter/change PIN 8.3
+CLIP Calling line 7.6 (4 - 8 digits)
identification
presentation +CSQ Signal quality 8.5

+CLIR Calling line 7.7 +CMEC Mobile equipment 8.6

identification restriction control mode (optional
if keypad and display
not supported)
+CCFC Call forwarding number 7.10
and conditions
+CKPD Keypad control 8.7
+CCWA Call waiting 7.11
+CDEV Display Control - upon 8.8
+CHLD Call-related 7.12 sending
AT+CMER=0,0,1
supplementary services
current text display
report is received

98-08901C39-B 51
Software Interface

Table 20. ETSI 07.07 Mobile Equipment Control and Table 21. ETSI 07.07 Mobile Equipment Errors and Status
Status Commands (Continued) Reports (Continued)

Command Description Reference Command Description Reference

+CIEV Indicator Control - upon 8.9 +CME 0 Phone failure 9.2

sending ERROR 1 No connection to
AT+CMER=0,0,0,1 phone
current indicator report
2 Phone-adaptor link
is received
reserved
3 Operation not
+CMER Mobile equipment 8.10
allowed
event reporting
4 Operation not
supported
+CPBS Selects phone book 8.11
5 PH-SIM PIN
memory storage
required
(optional if phone book
not supported) 6 PH-FSIM PIN
required
+CPBR Reads phone book 8.12 7 PH-FSIM PUK
entries required
10 SIM not inserted
+CPBF Finds phone book 8.13 11 SIM PIN required
entries 12 SIM PUK required
13 SIM failure
+CPBW Writes phone book 8.14 14 SIM busy
entry 15 SIM wrong
16 Incorrect
+CRSM Restricts SIM access 8.18 password
17 SIM PIN2
+CMUT* Mute control – use 8.24 required
AT+CIP with 18 SIM PUK2
IP_MUTE_REQ required
command for mute 20 Memory full
toggling
21 Invalid index
*This command is not supported by the g18. To obtain +CMUT 22 Not found
functionality, use +CIP AT command, and follow the instructions 23 Memory failure
above.
24 Text string too
long
Table 21. ETSI 07.07 Mobile Equipment Errors and Status 25 Invalid characters
Reports in text string
26 Dial string too
Command Description Reference long
27 Invalid characters
+CMEE Report mobile 9.1 in dial string
equipment error 30 No network
service
31 Network time-out
32 Network not
allowed -
emergency calls
only

52 98-08901C39-B
 Software Interface

4.11 V.25TER COMMANDS USED WITH Table 22. V.25ter Commands Used with GSM (Continued)
GSM
V.25ter
The following are the V.25ter commands that can be used Command Description
Reference
with GSM.
S3 Command line 6.2.1
Table 22. V.25ter Commands Used with GSM termination character.

V.25ter S4 Response formatting 6.2.2

Command Description
Reference character.

&C DCD (received line 6.2.8 S5 Command line editing 6.2.3

signal detector) character.
behavior.

S7 Connection completion 6.3.10

&D DTR (data terminal 6.2.9 time-out.
ready) behavior.

S24 Sleep mode.

&F Set to factory-defined 6.1.2
configuration.
Sn for n Bit map registers.
equals to Note: S14 is a read only
+GCAP Request complete 6.1.9 14, 21, 22, register. When trying to
capabilities list. 31, 36, 39, type it will return OK but
40, 41 value is not changed.
+CGMI Request manufacturer 6.1.4
identification.
S94 Sidetone enable/disable
(unmute/mute) feature
+CGMM Request model 6.1.5 for analog audio
identification. devices. When
ATS94=1, sidetone is
+CGMR Request revision 6.1.6 enabled (default).
identification.
S95 Bitmap register for
+CGSN Request product serial 6.1.7 extended result code.
number ID (IMEI).
S96 Echo cancelling feature
A Answer. 6.3.5 for audio analog devices
by ATS96=1.
D Dial. 6.3.1
S97 Antenna diagnostic
E Command echo. 6.2.4 feature: ATS97? will
respond with 000 or 001.
000 means that either
H Hook control. 6.3.6
the antenna is not
connected or the
I Request identification 6.1.3 hardware does not
information. support this feature.

O Return to online data 6.3.7

state.

S0 Automatic answer. 6.3.8

S2 Read/set escape code

character.

98-08901C39-B 53
Software Interface

Table 22. V.25ter Commands Used with GSM (Continued) Table 22. V.25ter Commands Used with GSM (Continued)

V.25ter V.25ter
Command Description Command Description
Reference Reference

S98 ATS98=1 allows the S101 Sets wakeup line forever

handset’s backlight to when x=1, and resets it
behave as if the unit was when x=0. ATS101?
not powered by using returns the current state.
the TS line. It turns off These operations are
the backlight allowed only when the
immediately, for the first factory bit is set. When
time after powering up. the parameters are
Note: ATS98=x is incorrect, or the factory
allowed only for x=1. bit is not set, returns an
error.
S99 ATS99=x, where x
defines the length in ms V DCE response format. 6.2.6
of the hardware pulse
given when GPRS X Result code selection 6.2.7
coverage is changed and call progress
from no coverage to monitoring control.
coverage. The pulse
length is 2x when data
Z0 Restores stored profile 0 6.1.1
indication is sent. The
default value is 30 ms; 0
value is not allowed. Z1 Restores stored profile 1 6.1.1
S99 responds with an
error if the value is
greater than
Table 23. V.25ter Voice Commands
2,147,483,647.

Command Description
S100 ATS100=x, where x
defines the number of
seconds. To avoid *A Voice answer.
frequent hardware
interrupts, the g18 uses *D Voice dial.
hardware indication for
data only after x seconds ; Dial Modifier for voice dial.
from the time the last modifier
character was sent to
the DTE. The default
A Voice answer.
value of x is 1 second; 0
value is not allowed.
S100 responds with an H Voice hang-up.
error if the value is
greater than 32,767.

54 98-08901C39-B
 Software Interface

4.12 ETSI 07.05 STANDARD (SMS) Table 24. ETSI 0705 TE Commands Sent from Host to
Phone (Continued)
The following tables list the complete set of commands as
described in ETSI standard 07.05. For each command it is
ETSI 07.05
recommended that you use the ? option to query the modem Command Description
Reference
for the particular details of each command. For example, use
AT+CR? to get the full details on the +CR command.
INDICATE INC Requests 2.4.1.6
Block mode is a stand-alone mode that makes use of full text SMS notification of
commands and responses to send and receive SMS any incoming
messages. This is an older mode that is provided for SMS messages
compatibility reasons. It is recommended that PDU mode be
used instead of block mode. Text mode is not supported by INSERT SMS Sends an SMS 2.4.1.8
the modem. PDU mode is the preferred method since it is the message
simplest and easiest to use.
LIST REQUEST Requests list of 2.4.1.1
messages
stored on the
4.12.1 Block Mode phone

SMS block mode is described fully in GSM 07.05,

TRANSFER INC Requests direct 2.4.1.7
section 2. CBS transfer of
broadcast
Table 24. ETSI 0705 TE Commands Sent from Host to messages
Phone directly to host
computer
ETSI 07.05
Command Description
Reference TRANSFER INC Requests direct 2.4.1.5
SMS transfer of
ACKNOWLEDGE Acknowledges 2.4.1.12 incoming SMS
MESSAGE receipt of INC messages from
MESSAGE or the air directly to
MESSAGE host computer
ARRIVED
UNABLE TO Indicates that a 2.4.1.10
DELETE Deletes SMS 2.4.1.9 PROCESS phone message
MESSAGE message could not be
processed
END SMS MODE Terminates 2.4.1.11
SMS/CBS mode
of the DTE/DCE
Table 25. ETSI07.05 MT Responses Sent from Phone to
interface
Host
GET FIRST Retrieves the 2.4.1.3
MESSAGE first message ETSI 07.05
Response Description
stored on the Reference
phone
DELETE Host’s request to 2.4.2.8
GET MESSAGE Retrieves a 2.4.1.2 MESSAGE delete a message
specific COMPLETE has been completed
message stored
on the phone DELETE Host’s request to 2.4.2.9
MESSAGE delete a message
GET NEXT Retrieves the 2.4.1.4 FAILURE has failed
MESSAGE next message
stored on the END SMS Phone is exiting 2.4.2.11
phone MODE SMS mode

98-08901C39-B 55
Software Interface

Table 25. ETSI07.05 MT Responses Sent from Phone to 4.12.2 Text Mode
Host (Continued)
Text mode is fully described in GSM 07.05, section 3.
ETSI 07.05
Response Description The g18 module does not support text mode, however the
Reference
following commands are supported, since they are useful for
PDU mode.
GET Request for a 2.4.2.3
MESSAGE message cannot be
Table 26. ETSI 07.05 Text Mode
FAILURE fulfilled

ETSI 07.05
INC Incoming message 2.4.2.4 Command Description
Reference
MESSAGE transfer to host has
been requested
+CSMS Select message 3.2.1
service (phase 2,
INSERT SMS Host’s request to 2.4.2.6
phase 2+, and so
COMPLETE insert a message
on)
has been completed

+CPMS Preferred message 3.2.2

INSERT SMS Host’s request to 2.4.2.7
storage
FAILURE insert a message
has failed
+CMGF Message format: 3.2.3
PDU or text mode
MESSAGE Indicates a 2.4.2.2
selection, PDU =
message has been
default
requested

+CESP Enter SMS block 3.2.4

MESSAGE Indication of 2.4.2.5
mode protocol
ARRIVED incoming messages
has been requested
+CMS Message service 3.2.5
failure result code:
MESSAGE Indicates receipt of 2.4.2.1
LIST LIST REQUEST 0 - 127 GSM 04.11
Appendix E-2
values
REQUEST Request received 2.4.2.12
CONFIRMED and will be 128 - 255 GSM
performed 03.40 sub-clause
9.2.3.22 values
300 ME failure
UNABLE TO Host’s request could 2.4.2.10
PROCESS not be processed 301 SMS service
of ME
reserved
302 Operation not
allowed
303 Operation not
supported
304 Invalid PDU
mode
parameter
305 Invalid text
mode
parameter
310 SIM not
inserted

56 98-08901C39-B
 Software Interface

Table 26. ETSI 07.05 Text Mode (Continued) 4.12.3 PDU Mode

Command Description
ETSI 07.05 PDU mode is described fully in GSM 07.05 Section 4. PDU
Reference mode uses the same commands and responses as the Text
mode described above. However, PDU mode uses different
+CMS 311 SIM PIN 3.2.5 formats for the following commands and responses.
required
In addition, refer to GSM 04.11 and GSM 03.40 for details
312 PH-SIM PIN
required on formatting the Service Center Address and Transport
Data Protocol Unit of the SMS PDU.
313 SIM failure
314 SIM busy Table 27. ETSI 0705 PDU Mode
315 SIM incorrect
316 SIM PUK ETSI 07.05
required Command Description
Reference
317 SIM PIN2
required +CMGL Lists messages 4.1
318 SIM PUK2
required
+CMGR Reads message 4.2
320 Memory failure
321 Invalid +CMGS Sends message 4.3
memory index
322 Memory full
+CMGW Writes message 4.4
330 SMSC
address
+CNMA Acknowledges new 4.6
unknown
message to ME/TA
331 No network
service
+CMSS Sends message from 4.7
332 Network time-
storage
out
340 No +CNMA
acknowledge-
ment
expected
500 Unknown error

+CMGD Deletes message 3.5.4

+CSCA Service centre 3.3.1

address

+CNMI Indicates new 3.4.1

message

+CMGL Lists messages 3.4.2

+CMGR Reads message 3.4.3

+CNMA Acknowledges 3.4.4

new message to
ME/TA

+CMSS Sends message 3.5.2

from storage

98-08901C39-B 57
Software Interface

GPRS COMMANDS
Table 28. ETSI 07.07 Commands for GPRS

Command Function Reference

+CGDCONT Defines, modifies or 10.1.1

removes a PDP
context

+CGQREQ Defines, modifies or 10.1.2

removes a requested
Quality of Service
profile

+CGQMIN Defines, modifies or 10.1.3

removes a minimum
required Quality of
Service profile

+CGATT Attaches/detaches 10.1.4

GPRS requests

+CGACT Activates/deactivates 10.1.5

PDP context request

+CGPADDR Shows PDP address 10.1.8

+CGCLASS Interfacing mobile 10.1.11

station class
parameters (stores,
manages, retrieves)

58 98-08901C39-B
 5. MUX INTEGRATION

5.1 GENERAL 5.4 MUX CLOSE SERVICE

The g18 is supplied with an internal GSM 07.10 protocol The following procedure describes how to close the MUX
stack, also referred to as a multiplexer or MUX. service:
This software utility provides the user with two virtual 1. Close any CSD/Voice/GPRS connections.
channels on one physical connection (an RS232 line).
2. Close MUX, as described in section 5.9.2.2.2, or toggle
The g18 with multiplexer support allows data (CSD/GPRS) the hardware DTR signal.
and command (AT commands set) services simultaneously. 3. The MUX remains open as one channel in 0707/0705
In this way, a user can make network and phone service mode.
inquiries and maintain data communication at the same time.

5.5 DATA TRANSFER

5.2 MUX INTEGRATION After the MUX is open the user can send and receive data in
REQUIREMENTS the two virtual channels, channel 1 and channel 2.
• g18 version E6.12.24 or higher (with MUX support) The user can also send and receive MUX command data on
• MUX software implementation within your product the control channel (channel 0).
(terminal, and so on)
• Hardware flow control implementation
5.6 TWO CHANNEL LIMITATION
Using two channels has the following limitations:
5.3 MUX OPEN SERVICE
1. Use Channel 1 for CSD/GPRS. AT COMMAND usage
The following procedure describes how to open the MUX on this channel is only allowed for establishing or
service: releasing a connection.
1. Send the AT+CMUX=0 command to g18 (for initiation 2. Use Channel 2 for AT COMMANDS, VOICE CALL
of the GSM 07.10 protocol). and SMS.
2. Wait for the OK response. 3. The g18 profile setup (S(x)-register) will be the same
3. Open the MUX within ten seconds, as described in for all channels (one modem). For example, when the
section 5.9.2.2.1 (otherwise, the g18 will exit MUX atsx command is sent from either Channel 1 or Channel
mode and revert back to one channel in 0705/0707 2, the modem S(x)-register changes and affects both
mode). channels.

4. Three channels must be opened; one for control and the 4. When the g18 is in CSD negotiation mode, meaning
other two for information. from ATD until the CONNECT/NO CARRIER
message appears, the user must not send any commands
5. Use Channel 1 for CSD or GPRS. on Channel 2.
6. Use Channel 2 for the AT COMMAND set.

98-08901C39-B 59
MUX Integration

5.7 SYSTEM BEHAVIOR 5.8 SUPPORTED PROTOCOL SERVICES

The following are system behavior guidelines while in MUX The following is a list of supported protocol services:
mode:
1.
1. Using the AT+CBAUD command is prohibited in
MUX mode.
2.
2. Channels 1 and 2 have the same baud-rate and the same
hardware flow control. 3.
3. Both AT+CMUX=0 and MUX services can be
activated without a SIM card.
4. When Channel 1 is in CSD data mode, the connection
4.
should be released by sending the +++ sequence, and
then sending the ATH command.
5. When Channel 1 is in GPRS data mode, the connection
can be released by sending either the +++ sequence, 5.
LCP_TERMINATE or ATH command, or by using the
virtual DTR toggle.
6. In MUX mode, use virtual V24 signals since the DTR
and DCD hardware signals are not relevant in the MUX.
6.
7. AT commands that create unsolicited reports should be
set in the MUX mode in order to receive the correct
unsolicited AT commands indications (CLCC, CSCB,
and so on). Only the CIPE command should remain in
PREMUX mode.
8. Activate the +CIPE command before the +MUX
comand in order to receive the correct CIP confirmation 7.
in the MUX mode.
9. When in CSD data call mode, close the call before
exiting the MUX.
10. Do not use the ATZ command on a channel on which a
CSD call is not released.
11. When using the A/ command on two virtual channels,
the A/ command repeats the last entered command
according to the time and not per channel.
12. When both a GPRS call and Voice calls are established
on the virtual channels, the Voice call should be
released first and then the GPRS call. If the GPRS call
is released first, the Voice call can only be released 8.
from the HandSet and not by the ATH command. 9.
13. When any Data call is established on the first channel,
RING cannot be released by the ATH command on the
second channel. Use AT+CTFR1 instead to release the
RING.
14. Do not use the +IPR command in the MUX mode.
The g18 Support Multiplexer ETSI 07.10 - Non Error
Recovery Mode - Basic Option.
The Multiplexer Flow Control Service (5.1.8.1.4 in the
specifications).
Channel Establishment:
• Purpose: Used to add a new channel.
• Usage: Permitted channel ID numbers are 0–2.
Channel Release Services:
• Purpose: Used to disconnect the existing channel.
• Usage: On existing channel.
Data Service:
• Purpose: Used for data transmissions.
• Usage: For data transfer between the g18 and the
terminal.
Close Down Service:
• Purpose: Used to terminate multiplexer 07.10.
• Usage: This command can be used if the last
existing channel is the control channel (channel 0).
The DISC or CLD command frame can be used for
this purpose.
Control Services:
• Flow Control Service
• Purpose: To avoid virtual channels buffers
overflow.
• Usage: To send to Radio MSC frame with
virtual CTS/RTS ON/OFF.
• Test Service
• Purpose: To test the communication link
quality between the two 07.10 entities (g18
and terminal).
• Usage: To send test frame and to check reply
frame (must be equal).
MSC ( Modem Status Command)
Other GSM 07.10 services are not supported.

60 98-08901C39-B
 MUX Integration

5.9 USER INTEGRATION

5.9.1 Introduction

When implementing the MUX feature, the user should have

the MUX entity installed with the product. The following
two MUX Integration options are available to the user:
• MIP (Mux Integration Packet): The user receives the
source code, which is provided by Motorola, with known
APIs for the MUX.
• MUI (Mux User Implementation): The GSM 07.10
protocol is implemented by the user.

5.9.1.1 Architecture
The Mux 0710 packet architecture is shown below.

Figure 42. Mux Architecture

The MIP (Mux Integration Packet) is a Motorola open
source code packet for GSM 07.10 protocol with API
functions provided for the user.
The MUI (Mux User Implementation) is the user
implemenetation device for the GSM 07.10 protocol.
Each of the following points represents an API user
interface, as shown in Figure 42, above:
• Point 1: The RX data is generated by the user ISR. At this
point the data is unpacked and dispatched to the correct
API TS0710_rx_handler_api channel.
• Point 2: The MIP either generates or triggers an API
function for each TS0710_DLC_APP_rx_handler_api()
channel.

98-08901C39-B 61
MUX Integration

• Point 3: The user wants to send data from the API
TS0710_application_send_data channel.
• Point 4: The MIP either generates or triggers an API
function for sending the API USER_tx_service() frame
TX.
• Point 5: The Mgr is used to close the MUX, open the
MUX and for testing (echo, ping).
3. Send release for first channel (07.10 DISC command
frame for Channel 1).
4. Wait for ACK (07.10 UA command frame).
5. Send release for control channel (07.10 DISC command
frame for Channel 0) or 07.10 CLD command frame.
6. Wait for ACK (07.10 UA command frame).

5.9.1.2 APIs 5.9.1.4 Sending Data Service

The API Sending Data Service MIP and MUI procedures are
There are five API user integrations, as follows:
as follows:
• Open service
MIP: Use API TS0710_application_send_data
• Close service (MUX_CHANNEL dlc,BYTE data_length,
• Sending Data service BYTE *data_body).
• Receiving Data service MUI:
• MUX service test, msc, fc and so on (all to control
• Use UIH frame with the data encapsulated for sending
channel)
Channel 1 data.
5.9.1.2.1 Open Service • Use UIH frame with the data encapsulated for sending
Channel 2 data.
The API Open Service MIP and MUI procedures are as
follows: 5.9.1.5 Receiving Data Service
MIP: Use API The API Receiving Data Service MIP and MUI procedures
TS0710_open_all_MUX_channels(). are as follows:
MUI: MIP:
1. Send establish for control channel (07.10 SABM 1. Use API BYTE TS0710_rx_handler_api
command frame for Channel 0). (BYTE* rx_string, WORD len_rx_string)
2. Wait for ACK (07.10 UA command frame). for unpack frames.
3. Send establish for the first channel (07.10 SABM 2. Use TS0710_DLC_APP_rx_handler_api
command frame for Channel 1). (MUX_CHANNEL dlc,BYTE bytes_in_queue)
for reading the arrival data from the channel buffer
4. Wait for ACK (07.10 UA command frame).
void.
5. Send establish for the second channel (07.10 SABM
MUI: Create data unpack.
command frame for Channel 2).
6. Wait for ACK (07.10 UA command frame). 5.9.1.6 MUX Service Test, MSC, FC, and so on
(all to control channel)
5.9.1.3 Close Service
MIP:
The API Close Service MIP and MUI procedures are as
1. Void ts_0710_send_CLD_cmd
follows:
(DLC_CMD_OR_RESP type )
MIP:
2. Void ts_0710_send_test_req (BYTE*
1. Use API test_DATA, WORD test_DATA_length)
TS0710_close_all_MUX_channels().
3. Void ts_0710_send_Channel_DTR_status
2. Wait for third ACK (07.10 UA command frame). (BYTE DTR_Signal, BYTE dlc)
MUI: 4. Void ts_0710_send_test_req (BYTE*
test_DATA, WORD test_DATA_length)
1. Send release for second channel (07.10 DISC command
frame for Channel 2).
2. Wait for ACK (07.10 UA command frame).

62 98-08901C39-B
 6. HARDWARE

6.1 GENERAL 6.3 ANTENNAS

The following vendor and parts information is provided as a
recommended solution for acquiring host interface, modem
antenna and evaluation board components. You may also 6.3.1 GSM Antenna
search for and find your own solution for acquiring the
required components. The g18 is supplied without an antenna and the customer
must choose which antenna will be used. The style of the
antenna is highly dependent on the particular project
requirements.
6.2 HOST INTERFACE
Recommended values:
Frequencies GSM 900: TX band: 880 - 915 MHz
6.2.1 Modem I/O Connector
RX band: 925 - 960 MHz
For the modem-to-host interface, use the 36-pin ZIF-style DCS: TX band: 710 - 1785 MHz
serial connector. Use the following description to order
RX band: 1805 - 1880 MHz
connectors from ELCO:
PCS: TX band: 1850 - 1910 MHz
• Part number 04 6240 036 003 800
Motorola recommends that you use the same connector for RX band: 1930 - 1990 MHz
the host-to-modem interface connection. Gain 0 dBi (Unity) gain or greater
Impedance 50 Ohm
VSWR 1.5:1 typical
6.2.2 Interface Cable

The serial interface cable is a 36-pin 0.5 mm pitch flexible

printed circuit (FPC). Use the following descriptions to
order interface cables from the Parlex Corporation:
0.5MM-36-xx-B, mates with ELCO 6240 series connector,
where xx indicates the length in inches. The term “mates
with ELCO 6240 series connector” indicates that the FPC is
to be connected to an ELCO connector.

98-08901C39-B 63
Hardware

6.3.2 GPS Antenna (Recommendation) An alternate supplier, Conectec, can also provide long 90°
MMCX connectors and RF cable assemblies.
Frequency 1575.42 MHz (L1) Huber-Suhner and Conectec also provide assemblies with
Bandwidth ± 1.023 MHz other connector types.
Polarization Right-hand circular
Impedance 50 Ohm 6.4 DEVELOPER’S KIT
Gain requirement 10 to 26 dB (at receiver input)
The Motorola Developer’s Kit, part number S9002, includes
Gain pattern +0 dBic minimum at zenith the following parts and part numbers:
-10 dBic minimum at 0° elevation
Handset with SIM CR SCN5011x
Noise figure 1.8 dB typical
2.2 dB maximum Handset without SIM CR SCN5012x
VSWR 1.5:1 typical Headset SYN6962
2.5:1 maximum
Headset SYN4937
Axial ratio 3 dB typical at zenith
6 dB maximum at zenith Microphone SMN4097

1 dB compression -14 dBm typical (at antenna output) Speaker SNN4018

point GPRS Manager SVN4503
3 dB frequency 45 MHz maximum
Short Flex Cable 50mm 3086229J10
bandwidth
25 dB frequency ± 95 MHz Long Flex Cable 300mm 3086229J09
rejection Coax Cable 200mm (MMCX/SMA) 3085720G01
Ground plane 15 x 15 cm (recommended)

6.5 VENDOR CONTACTS

6.3.3 Antenna Connector Allgon Antenna AB

The antenna connector on the g18 for the GSM and GPS port Box 500, SE-184
is a 82MMCX-S50-0-3 (female). Mating connectors to the 25 Akersberga,
82MMCX include the following two options only: Sweden

11MMCX Straight connector (male) Phone: +46 (0) 8 540-601-20

16MMCX Right-angle connector (male) Fax: +46 (0) 8 540-676-16

Website: www.allgon.se
Use the preceding descriptions to order antenna connectors
from Huber-Suhner. Email: info@allgon.se
Product: Antennas

6.3.4 Antenna Cable Assembly Cap-XX

The antenna cable assembly, as supplied in the Motorola 1709 Crooked Pine Drive
Developer’s Kit, uses a SMA (female) with an 8-inch Myrtle Beach, SC 29575
RG316 cable to a male MMCX connector. U.S.A.

The following options can be ordered as antenna cable Phone: +1 (843) 215-2584
assemblies from Huber-Suhner: Fax: +1 (843) 215-4419
RG316/16MMCX/21SMA/.203M Straight jack Website: www.cap-xx.com
RG316/16MMCX/24SMA/.203M Bulkhead jack Email: jmr@peoplepc.com
Product: Super capacitors

64 98-08901C39-B
 Hardware

Centurion AVX/Kyocera (Singapore) Pte Ltd.

44th Street 39A Jalan Pemimpin
Lincoln, Nebraska 68504 #07-00 TAL Building
U.S.A.. Singapore 577183

Phone: +1 (402) 474-0706 Phone: +65 350-4892

Fax: +1 (402) 423-3358 Fax: +65 258-1756
Website: www.centurion.com
AVX Corporation
Email: bobb@centurion.com
Product: Antennas 801 17th Avenue South
Myrtle Beach, SC 29578-0867
U.S.A.
Conectec RF, Inc.
2155 Stonington Way, Suite 108 Phone: +1 (843) 946-0585
Hoffman Estates, IL 60195 Fax: +1 (843) 626-5292
U.S.A.
South America
Phone: +1 (847) 519-0100
Fax: +1 (847) 519-1515 Phone: +1 (843) 946-0392
Website: none Fax: +1 (843) 626-2396
Email: ctecrf@ix.netcom.com
Electro Mech, Inc.
Product: Antenna cable assemblies
2 Cordier Street
ELCO ZIF Connector Irvington, NJ 07111
U.S.A.
AVX Ltd.
Phone: +1 (201) 318-7999
Admiral House
Harlington Way Fax: +1 (201) 318-7995
Fleet, Hampshire Website: none
England GU13 8BB Email: none
Product: Power supplies, Framatome connectors,
Africa SIM connector supplier
Phone: +44 (0) 1252 770-062
Galtronics LTD
Fax: +44 (0) 1252 770-104
P.O. Box 1569
Europe Tiberias 14115
Israel
Phone: +44 (0) 1252 770-130
Phone: +972 (0) 6 673-9777
Fax: +44 (0) 1217 057-145
Fax: +972 (0) 6 673-3000
Middle East Website: http://www.galtronics.com/
Email: none
Phone: +44 (0) 1252 770-062
Product: Antennas
Fax: +44 (0) 1252 770-104

Bogart, Georgia

Phone: +1 (706) 546-0087

Fax: +1 (706) 546-1298

98-08901C39-B 65
Hardware

San Diego, California Huber+Suhner (Singapore) Pte. Ltd.

Phone: +1 (858) 451-3730 1 Tuas Basin Close

Singapore 638803
Fax: +1 (858) 451-3571
Phone: +65 861-8186
Chicago, Illinois Fax: +65 861-3316
Phone: +1 (262) 942-7259 Product: Antenna cables and connectors
Fax: +1 (262) 942-7260
Larsen Electronics
Tianjin, China 3611 N.E. 112th Ave.
Vancouver, WA 98682
Phone: +86 22 26517176/7
U.S.A.
Fax: +86 22 26517178
Phone: +1 (800) 778-7854, ext 711, 742
Japan Fax: +1 (360) 944-7556

Phone: +81 (0) 47 394-8227 Website: www.larsenet.com

Fax: +81 (0) 47 394-8244 Email: pstorm@larsenet.com

Product: Antennas
Livingston, UK
Parlex Corporation
Phone: +44 (0) 1506 460-430
7 Industrial Way
Fax: +44 (0) 1506 461-007
Salem, NH 03079
U.S.A.
Huber+Suhner
Phone: +1 (603) 893-0040
1014 East Algonquin Road
Suite 104, Schaumburg, IL 60173 Fax: +1 (603) 894-5684
U.S.A. Website: www.parlex.com
Phone: +1 (847) 397-2800 Email: jholdeman@parlex.com
Fax: +1 (847) 397-2882 Product: Serial interface cables
Website: www.hubersuhnerinc.com
Santac Connectors
Email: sschweizer@hubersuhnerinc.com
bburress@hubersuhnerinc.com North America
MVP Sales
Product: Antenna cables and connectors 820 South Bartlett Road
Suite 108
Huber+Suhner Hong Kong Ltd. Streamwood, IL 60107
Suite 902, 9/F Jubilee Centre U.S.A.
18 Fenwick St, Phone: +1 (630) 483-8766
Wanchai, Hong Kong
Fax: +1 (630) 483-1993
Phone: +852 2866-6600 Website: mvpsales@msn.com
Fax: +852 2866-6313
Product: Antenna cables and connectors

66 98-08901C39-B
 Hardware

Africa Europe
Arrow Altech Distribution Ltd. Samtec Europe Ltd.
53-57 Yaldwyn Road 117 Deerdykes View
Hughes Ext. Jet Park 1459 Westfield Industrial Estate
Johannesburg Post Office Cumbernauld, Scotland
Johannesburg, South Africa UK G68 9HN

Phone: +27 (0) 11 923-9713 Phone: +44 (0) 1236 739-292

Fax: +27 (0) 11 974-9683 Fax: +44 (0) 1236 727-113
Email: djrodger@arrow.altech.co.za Email: julie.campbell@samtec.com

Asia Middle East

Samtec Asia Pacific Pte Ltd. Dimtec Adiel Ltd.
1 Kallang Sector #05-01
7 Propes St
Kolam Ayer Industrial Park
P.O. Box 7637
Singapore 349276
Ramat Gan
Israel 52176
Phone: +65 745-5955
Phone: +972 (0) 3 678-1758
Fax: +65 841-1502
Fax: +972 (0) 3 678-1738
Email: yvonne.tang@samtec.com
Email: oferdim@zahav.net.il

98-08901C39-B 67
Hardware

68 98-08901C39-B
 7. TESTING

7.1 GENERAL
This section contains a product development checklist of
parameters to check, requirements to meet, and standards of
performance to evaluate. You can use these process checks
and functional test procedures to ensure that the g18
Integrated Wireless Modem is well integrated into your host
product.
• Pass data through the host between the modem and the
test platform. This allows external programming and
configuration software to communicate with the modem
while it is integrated within the host. For
microprocessor-based products, the pass-through mode
uses software emulation involving the host processor,
which passes full-duplex serial port data to, and from, the
integrated modem.

7.2.1.2 Specific Tests

7.2 TESTING STAGES
In addition to the various tests that exercise your own
Proper testing throughout the development and integration circuitry (such as the power-on self test), design tests that
cycle ensures that the final product works in both normal ensure proper interaction between the modem and host.
and exceptional situations. These tests are provided in Ensure that the following hardware integration issues are
several stages, as follows: evaluated:
1. Hardware integration
RF Immunity RF transmissions of the modem do
2. Desense and EMI not interfere with operation of the
3. Regulatory compliance host.

4. Application software Electrical Signaling Power sources and interface are

functionally compatible between
5. Final assembly
the host and the modem.
6. End user problem resolution
Physical Parameters Physical configuration of the
7. OEM service depot repair modem inside the host provides
adequate ventilation, mounting,
shielding and grounding.
7.2.1 Hardware Integration Antenna Performance Integrated antenna system meets the
required ERP specifications,
To ensure that the integration effort is carried out properly,
VSWR specifications and antenna
monitor all relevant engineering standards, requirements,
propagation patterns.
and specifications. In addition, perform functional tests
during product development to validate that the integrated ESD Requirements Host design protects the modem
package performs as intended. from ESD.
RF Re-radiation Host does not allow spurious
7.2.1.1 Enabler Functions emissions in excess of 60 dBc, as
To test the interaction between the modem and the host, your caused by carrier re-radiation.
product must be able to perform the following tests:
• Turn the various hardware components on and off. This
capability helps to isolate possible desense and other
emission problems.

98-08901C39-B 69
Testing
7.2.2 Desense and EMI
Any host in which the modem is integrated generates some
EMI (electromagnetic interference), which tends to
desensitize the modem’s ability to receive at certain
frequencies. You should verify that the host equipment does
not influence the g18 performance. (Refer to “Desense” on
page 199, for more information).
If desense was detected, one or more of the following can be
performed:
1. Connect the antenna cable shield to the main ground
(PS ground).
2. Shield the logic section in the user application. (Most of
the radiation can come from clocks and data lines
around the logic section due to the high rise/fall time of
the pulses).
3. A ferrite can be wrapped around the antenna cable.
Recommended ferrite: Fair Rate (company name)
# 2643023002 or # 0431173951.
7.2.3 Regulatory Compliance
Most countries where the final product will be sold currently
require approval from the local government regulatory body.
In the U.S., the FCC requires that two individual
requirements be met before the final product can be certified.
The first test, (FCC Part 15 Qualification), requires you to
prove that the product electronics hardware does not yield
local radiation capable of affecting other equipment, such as
televisions, computer monitors, and so on.
The second test (FCC Part 24) requires you to prove that
when the modem transmits, it remains properly in its
allocated channel spacing and does not produce spikes or
splatter in other frequencies. Motorola undergoes FCC
testing with the modem integrated into a dummy OEM host
to ensure compatibility with these requirements. However,
since the eventual transmit capability of the modem is highly
integrated with the power supply and antenna system of the
future host, the fully integrated product must be submitted
for final regulatory approval.
In addition, regulatory bodies can require the wireless
modem to transmit random data patterns on specific
frequencies while incorporated in the host platform. The
modem incorporates special debug modes to allow this kind
of testing, provided the host application can issue the
required commands to the modem.
The entire regulatory process can take many months to
complete and should start early in the development cycle.
The exact regulatory requirements of each country change
70
from time to time. For efficient regulatory processing, use
the services of specialized regulatory consultants to
determine the specific requirements at the time of
manufacture.
To prepare for regulatory testing, you need to integrate the
pass-through mode into the product design. For more
information, refer to “Enabler Functions” on page 69. The
pass-through mode passes the RS-232 levels from an
external computer to and from the modem. Motorola
provides the ability to key and dekey the radio at the required
frequencies and modulation levels from an external
computer via the pass-through mode.
Nothing further is required for regulatory requirements for
the g18, which is approved for Part 24 when used in your
host device. The product is approved by FCC and DOC. The
host device will still require approval for Part 15.
For further information about regulatory compliance, refer
to “Regulatory Requirements” on page xiv.
7.2.4 Application Software
The following tests need to be performed to verify the
communications links between the host and the modem and
between the modem and the network, as follows:
Software Driver Configuration
Ensure that the host product can enable the modem serial
port to permit the host and modem to communicate. This test
verifies that the driver software functions well and is
configured properly.
Network Configuration
Determine whether the host can use the modem to
communicate with a GSM network. This test uses existing
network software in an attempt to communicate with a
specific network.
Ensure the g18 is set to the correct band.
Note
The final application must be able to respond correctly under
all adverse network conditions, not only under ideal
conditions. To achieve this, the application software must be
systematically tested against all possible failure and
exception conditions. Situations such as low battery, out of
range, host down, unexpected data, maximum message size,
maximum peak/sustained throughput and other conditions
must not cause the host application to fail. Each condition
must have a specific remedial action to alleviate it.
98-08901C39-B

7.2.5 Final Assembly
A final assembly test is performed before shipment to ensure
that all components are working properly and issues such as
crimped antenna cables, loose connections, and improper
software load are resolved. During final assembly, the
modem sends and receives a loopback message of maximum
size. The successful return of the sent message proves that
the product can transmit and receive correctly.
7.2.6 End User Problem Resolution
When the final product is in the hands of the end user, testing
must quickly isolate the cause of the problem in the field. For
example, is the problem caused by the terminal, the modem,
the network, the configuration, or a user error? Can the
problem be fixed locally or does the unit need to be sent to a
service center?
It is time consuming and expensive to send products to a
service center, particularly if the problem is caused by a
temporary network or host outage. For this reason, you
should design the application to enable the cause of the
end-user problem to be established. Often this functionality
can be designed together with the Help Desk, which supports
the user by telephone and without access to the user’s screen.
The application must enable the end user to relate the most
likely cause of the problem to the Help Desk for a quick
solution.
Effective tests provide a systematic, positive
acknowledgment from each of the network components. For
example:
Test 1 Is the OEM module able to pass its own self test?
Test 2 Is the OEM module able to communicate with
peripherals?
Test 3 Is the OEM module able to communicate with the
integrated modem?
Test 4 Is the modem able to hear the network?
Test 5 Is the modem registered and allowed to operate on
the network?
Test 6 Is the gateway (if present) up and running?
Test 7 Is the host up and running?
7.2.7 OEM Service Depot Repair
When a unit comes in to the OEM for service, the first
requirement is to determine whether the modem must be sent
on to Motorola for repair. A screening test must be
performed. In the screening test, the modem is mounted onto
98-08901C39-B
Testing
the Motorola evaluation board and a loopback message is
sent to qualify the specific problem.
To set up this test, you need an evaluation board, a
known-good g18 modem (for comparison), and a power
supply. The end-to-end test can employ either a live network
or an over-the-air test involving a communications monitor
that can transmit and receive at the appropriate frequencies.
The objective is to test the suspect modem in a known-good
environment, where all other components are known to be
operational.
7.3 DIAGNOSTIC UTILITY
This section describes how to develop a script to perform a
factory end-of-line test of a g18 modem integrated in an
OEM platform. This test provides a high degree of
confidence that the modem is properly configured and
integrated, and is ready for shipment.
OEM service operations are encouraged to
modify the following QA test procedure to
develop a test for the diagnostic screening of
Note repair products.
7.3.1 Quality Assurance Testing
Efficient, automated testing can ensure that the product is
functional when delivered to the end user, especially when
OEM product manufacturing occurs in a region or country
that is distant from the intended network.
Use the following checklist to verify that a product is ready
for shipment:
1. The OEM host platform (without modem) is
operational.
2. The OEM host platform contains the correct software
load.
3. The OEM host platform provides sufficient power to
operate the modem.
4. The modem is loaded with the correct software version.
5. The modem is loaded with the correct frequencies.
6. The modem is configured for the correct ID and
network registration information.
7. The OEM host communicates with the modem logic
board.
8. The OEM host is able to key up the radio with sufficient
output at the antenna.
9. The modem can receive with sufficient signal strength
from the antenna port.
71
Testing

Requirements for testing items 1 and 2 are 7.3.2.3 Loop-back Test

specific to each OEM product. A specific
description of these items is beyond the scope All communication between the DTE (the
Note of this document. computer) and the DCE (g18 modem) occurs at
57600 bps, no parity, 8 data bits, one stop bit.
An automated test script provides more than diagnostic Note
support. When you set up an automated test process, you Set the baud rate to 57600 bps using
ensure that only those products that pass the test are labeled AT+CBAUD=57600.
for release. For example, since regulatory agencies require Use any known file to transfer from COM1 to COM2 or
product labeling for certification and approval, you can from COM2 to COM1.
develop an automated script to read the modem ID and
destination network from the modem and generate a label Getting Started
with the proper inscription. • Verify that the g18 is on (DSC_EN LED in the EV board
will be on).
• Activate two terminal programs, one for COM1 and one
7.3.2 Equipment Test Set-up for COM2.
• Verify that each terminal receives a response from the
7.3.2.1 Calibration Tools and Equipment DCE device (send AT and verify OK response).
The following tools and equipment are required: • Start the test by sending a file from COM1 to COM2.
• For RF testing, use GSM simulators such as HP8960 or Measuring Additional Parameters
Rohde & Schwarz CMU200 (or equivalent). • ATI3 g18 Software version.
• For data testing, use a standard computer connecting the • ATI4 Product name.
g18 to the serial port via Motorola Evaluation Board
• AT+CSQ Reception signal quality (does not
S9002, or use the user’s equipment.
support BER information).
• Line modem.
• AT+CMER=0,0,1 Shows data on the handset display.
• Use the local network to make the communication.
For additional information, consult the Motorola g18
Customer Support Center:
7.3.2.2 Modem Test Setup
• Help Desk phone number: +972 (0)3-5684040
• Email: BSH015@email.mot.com

Figure 43. g18 Setup for Testing

72 98-08901C39-B
 H. AT COMMANDS

8.1 BASIC FUNCTIONALITY

Make sure that the g18 is mounted and linked correctly to the developer board. The power supply must provide 3-6 V DC with-
out any voltage spikes.
Use Telix or any other terminal program on your computer and set it to a normal RS232 connection, using a one-to-one connec-
tion cable.
After all the links have been established correctly, use the power switch to power up the board.

8.1.1 PIN and PUK Code Entry

If your SIM card requests a PIN number, do the following:

AT Command Response/Action Remarks

at+cpin=”nnnn” OK nnnn = PIN number (4 - 8 digits).

+CME ERROR: <err> If PIN is correct, “OK” is shown.
Enables the SIM card. If PIN is incorrect, “+CME ERROR:
<err>” is shown.
When incorrect PIN is entered:
ERROR
When correct PIN is entered:
OK

at+cpin? +CPIN: <code> When no SIM is available:

+CME ERROR: <err> +CME ERROR: <err>
Responds with information about the When PIN is not needed:
SIM and the PIN. +CPIN: READY
When PIN is needed:
+CPIN: SIM PIN
When PUK number is needed:
+CPIN: SIM PUK
When PIN2 is blocked:
+cpin: SIM PUK2

at+cpin=? OK

98-08901C39-B 73
AT Commands

+CPIN?
Allowed AT Command Result for
SIM/PIN Status +CPIN? Result Code
Commands Non-allowed Commands
Output

No SIM G1 SIM not inserted SIM not inserted -

Bad SIM G1 SIM failure SIM failure -

Required SIM Card PIN G1, G2 SIM PIN required OK SIM PIN

PIN1 Blocked G1, G2 SIM PUK required OK SIM PUK

Permanent Blocked (PUK) G1 SIM failure SIM failure -

PIN2 Required All Depends on AT command OK

PIN2 Blocked All Depends on AT command OK SIM PUK2

Permanent Blocked (PUK2) G1 SIM failure SIM failure -

Other All Depends on AT command OK READY

G1 is the group containing the following AT commands:

• Basic AT commands (includes ATD, ATA, ATH).
• AT+CKPD (to simulate handset key strokes).
• AT+CMER (to obtain handset screen output).
G2 is the group containing the AT commands which interacts with the ME. The following commands are accepted when the
ME is pending SIM PIN, SIM PUK or PH-SIM (GSM 7.07 section 8.3): +CGMI, +CGMM, +CGMR, +CGSN, +CPAS,
+CPIN

The following AT commands are enabled without a valid SIM: GCAP, GMI, GMR, IFC, CEER, CGMI, CGMM,
CGMR, CGSN, CHUP, CIPE, CKPD, CMEE, CMER, CIP, CRC, CSQ, CR, MTDTR.

Note

8.1.2 Feedback from the System

AT Command Action Examples

ati3 Provides the software version. E6.02.07.

at+cgmr Provides hardware information. +CGMR: g18_v_E6_02_07 (PC card)

at+cgmi Provides hardware information. CGMI: “MOTOROLA”.

at+cnum Provides the subscriber number. +CNUM: “VOICE”,”054445561”,129.

+CNUM: “DATA”,”054626515”,129.
+CNUM: “FAX”,”054562511”,129.

74 98-08901C39-B
 AT Commands

AT Command Action Examples

at+cops? Provides the name of the network +COPS: 000, 000, “IL ORANGE”.
operator.

at+csq Provides the signal strength +CSQ: 030, 099.

indication, for example
+CSQ: 031,099.

at+cmee=<n> Reports mobile equipment error. <n>

0 Disabled. (“ERROR”)
1 Enabled. (numeric, +CME
ERROR: 3)
2 Enabled. (string, +CME
ERROR: “operation not
allowed”)

at+cmer Reports mobile equipment events to For example,

the IP. AT+CMER=0,0,1,1,0.

8.1.3 Establishing a Voice Call

The following procedure shows the basic commands to be sent to the g18 to establish a voice call.

AT Command Response/Action Remarks

Power on the g18.

at+cpin=“xxxx” Enables the SIM card. DSC LED lights up.

xxxx PIN number (4 - 8 digits)

ATD (phone number); or Dials the phone number (voice call). OK

AT*D (phone number) or For example, NO CARRIER
ATD> <index>; or ATD123456;
ATD> <“name”> or ATD>102; OR
ATDS=n (n=0 to 3) or ATD>“DAN” OR
ATD><mem><index>; ATDS=1; OR
ATDS=0 OR
ATD>SM101;

Atdl Redials the last number.

at*dxxxx Dials a voice call.

Ath Hangs up. Note: In Multi-party calls, ATH does

not end the last call, only
AT+CHLD=1 does.

98-08901C39-B 75
AT Commands

In a voice call, when the other side hangs up, DTE receives a “NO CARRIER" message.
Only the second OK in a voice call notifies the user that the call was established.
Note

8.1.4 Answering a Voice Call

The following procedure shows the basic commands to be sent to the g18 to answer a voice call.

AT Command Response/Action Remarks

ata Answers the call.

8.1.5 Finding a Phone Book Entry

The following procedure shows the basic commands to be sent to the g18 to find a phone book entry.

Remarks
AT Command Response/Action

Power up the g18.

at+cpin=“nnnn” Enables the SIM card. nnnn PIN number (4 - 8 digits).

at+cpbs=“mt” Enables the phone and SIM memory.

at+cpbf=“Name” The g18 shows the number on that The “NAME” is a string up to first 3
position +CPBF: xxx, “phone characters.
number”, yyy, “Name of the entry”. <xxx> Position in the memory.
0-100 Phone memory.
101-220 SIM card memory.
<yyy>
129 Normal number.
145 International number.

76 98-08901C39-B
 AT Commands

8.1.6 Writing a Phone Book Entry

AT Command Response/Action Remarks

Power up the g18.

at+cpin=“nnnn” Enables the SIM card. nnnn = PIN number (4 - 8 digits).

at+cpbs=“mt” Enables the phone and SIM memory.

at+cpbw=xxx,“Phone number“, yyy, The g18 writes the number on that <xxx> Position in the memory.
“Name of the entry” position. 0-100 Phone memory.
101-220 SIM card memory.
<yyy>
129 Normal number.
145 International number.

8.1.7 Reading a Phone Book Entry

AT Command Response/Action Remarks

Power up the g18.

at+cpin= “nnnn” Enables the SIM card. nnnn PIN number (4 - 8 digits)

at+cpbs= “mt” Enables the phone and SIM memory.

at+cpbr= xxx The g18 shows the number on that <xxx> Position in the memory
position 0–100 Phone memory
+CPBR: xxx, “phone number”, yyy, 101–260 SIM card memory
“Name”. <yyy>
129 Normal number
145 International number

8.1.8 Phone Book Function

AT Command Response/Action Remarks

at+cpbs=“NN” This AT should be the first one to be “FD” SIM fix dialing phone book
used to select the phone book. “LD” Last dialing phone book
“ME” ME phone book
“MT” ME and SIM phone book
“SM” SIM phone book
“DD” Direct-dial phone book
“RC” ME received calls list
“MC” ME missed calls list

98-08901C39-B 77
AT Commands

AT Command Response/Action Remarks

at+cpbs? For example, +CPBS: “SM”,45, 100

at+cpbs=? +CPBS: (“FD”,”LD”,“ME”,“MT”, List of supported memory.

“SM”,“DD”,“RC”,“MC”)

at+cpbr=xxx For example: <xxx> is a number from 0 to 100,

at+cpbr=101 used to read from ME phone books;
+CPBR: 101,“123456”,129,“AVI” 101 to 220 is used to read from SIM
phone books.

8.1.9 Sending an SMS in PDU Mode

AT Command Response/Action Remarks

Power on the g18.

at+cpin=“nnnn” Enables the SIM card. nnnn PIN number (4 - 8 digits)

at+csms=<service> Selects the message service <Service>

response: 0 For phase 2
+CSMS: <mt>,<mo>,<bm>

+CSMS: 001,001,001 <mt>,<mo>,<bm>

OK. 1 Supported
2 Not supported

at+cpms=“sm” Preferred message storage

response:
+CPMS:<used1>,<total1>,<used2>,<
total2>
+CPMS: 001,0015,001,015
OK.

at+cmgs=160 Sends an SMS in PDU mode return: Sends “TEST”:

>0791947122720 00011000c91947 +CMGS: 000. To phone # 49 -172 - 6188234
1628128430000a 704f4f29c0e ctrl-z To SMS center 49 -172 - 2720000.
For SMS coding, refer to “SMS Error
Messages”, page 36.

8.1.10 Establishing GPRS PDP Context

When using the GPRS network for HTTP/FTP browsing, you must be connected to the GPRS network before the activation of
PDP context.
Connection may be performed in one of two ways:
• Automatically, after powering up of your MS. On the screen, the “GPRS” logo is displayed.
• Using the AT+CGATT=1 command.

78 98-08901C39-B
 AT Commands

You can check your connection status by using the AT+CGATT? command:
AT+CGDCONT=1, “IP”,“RTY”,“123.32.45.9”
Following are the three main ways in which to activate PDP context:
1. If the GPRS Wizard application is used, double-click the button predefined as the dialer for this provider to automatically
establish PDP context. If the g18 was not previously attached to GPRS, it will be attached automatically.
Setup Configuration
1. Enter into the wizard parameters provided by your operator.
2. Set definitions to allow your http\ftp browser to use the g18 as a port to the Internet.
Usage
1. Open the GPRS wizard.
2. Double-click the dialer icon to select and activate the provider of your choice (multiple providers may be displayed in
the list).
3. After dialing, your temporary IP address and then the GPRS DATA session message will be displayed on the handset.
4. Minimize the GPRS wizard window and use your http\ftp browser (Internet Explorer, Netscape).
2. If you use AT commands to activate PDP context, you must perform the following steps:
1. Define the PDP contact (profile).
For example: AT+CGDCONT=1,“IP”,“RTY”,“
2. Define Quality of Service.
For example: At+CGQREQ=3,2,4,5,8,12
3. Define minimum acceptable Quality of Service.
For example: At+CGQMIN=1,0,0,0,0
4. Activate PDP context using the AT+CGACT=1 command.
Bear in mind that the AT command AT+CGACT is not supported in all countries with GPRS. A GPRS connection
is also possible with ATD*99#. See the following section for more information.

Note

Setup Configuration
AT+CGQMIN=1,0,0,0,0,0
AT+CGQREQ=1,0,0,0,0,0
AT+CGCONT=1,“IP”,“APN”,“0.0.0.0”,0,0 // APN – replace it with the provider name
AT
AT &F0 &D2 &C1 E0
AT V1 W1 S95=47
AT&K3
ATD*99#
The above list is only for the AT command level. PPP information (DNSs) is not shown here.

Note

3. Using the ATD* command set:

To select the provider, protocol and the profile, use ATD*99***(CID)#. In fact, providers use the ATD*99# command to
attach to their GPRS service.

98-08901C39-B 79
AT Commands

8.2 AT COMMAND LISTING

For basic AT commands information, refer to “Basic AT Commands” on page 45.

8.2.1 ATD, Dialing

AT Command Response/Action Remarks

atd<number> OK <number>
Data/Fax number

BUSY Called party is not available

NO CARRIER No connection to the number

ATD (phone number); or For voice calls only

AT*D (phone number) or
ATD> <index>; or
ATD> <“name”> or Use without “;” for Data Call
ATDS=n (n=0 to 3) or
ATD><mem><index>;
ATDL ATDL: “<number>”
ATD*99 Requests GPRS service “D”.
Manual acceptance of a network
request.

at*d xxxxxx Dials a voice call.

Only the second OK for the voice call notifies the user that the call was established.

Note

Example
at*d06113611404
OK

OK // When the call is connected

atd06512467; //Another format for a voice call

atdl //Dial last number
ATDL: “06512467;”
OK

OK // When the call is connected

80 98-08901C39-B
 AT Commands

ath
NO CARRIER

OK
atd06113611404 // Data call
OK

BUSY
NO CARRIER

atd06113611404 // Data call - success

CONNECT

8.2.2 AT+CAOC, Charge Advice

AT Command Response/Action Remarks

at+caoc[=<mode>] +CAOC: <xxxx> <mode>

OK 0 Query CCM value
+CME ERROR: <err> <xxxx>
The actual price of the current call
at+caoc? +CAOC: <mode> (hex).
OK
+CME ERROR: <err>

at+caoc=? +CAOC: (list of supported <mode>s)

OK
+CME ERROR: <err>

Only available if the local network supports this command.

Note

Example
at+caoc=?
+CAOC: 0
OK

at+caoc=0
+CAOC: 000000
OK

98-08901C39-B 81
AT Commands

8.2.3 AT+CCFC, Call Forwarding Number and Conditions

AT Command Response/Action Remarks

at+ccfc= When <mode>=2 and command is <reason>

<reason>,<mode>[,<number>[,<type successful:
0 Unconditional
>[,<class>[,<subaddr>[,<satype>[,<ti +CCFC:
<status>,<class1>[,<number>,<type>[, 1 Mobile busy
me>]]]]]]
<subaddr>,<satype>[,<time>]]][<CR>< 2 No reply
LF>+CCFC: 3 Not reachable
<status>,<class2>[,<number>,<type>[, 4 All calls forwarded
<subaddr>,<satype>[,<time>]]] [...]]
5 All conditional calls forwarded
OK
When <mode> is 0,1 <Mode>
OK 0 Disable
+CME ERROR: <err> 1 Enable
2 Query status
at+ccfc? +CME ERROR: <err> 3 Registration
4 Erasure
at+ccfc=? +CCFC: (list of supported <reason>s)
<Type>
OK 145 International number
+CME ERROR: <err> 129 Regular number
<Time>
1-30 Time to wait before the call is
forwarded when there is no
reply (default)
<class>
Sum of integers representing
information for call blocking services
1 Voice
2 Data
4 Fax
<number>
String type phone number of
forwarding address in format
specified by <type>.
<subaddr>
String type subaddress of format
specified by <satype>
<satype>
Type of subaddress octet in integer
format (refer GSM 04.08 [8]
subclause 10.5.4.8); default 128
<status>
0 Not active
1 Active

The third parameter must be a multiple of 5 (0,5,10,...).

at+ccfc=5,2 and at+ccfc=4,2 are not supported by the network.
Note The first registration mode also enables the call forward.

82 98-08901C39-B
 AT Commands

Example
AT+CCFC=?
+CCFC: (0,1,2,3,4,5)

OK
AT+CCFC?
+CME ERROR: “Operation not allowed”

AT+CCFC=0,3,“01256316830”,129,1
OK
AT+CCFC=0,2
+CCFC: 1,1,“+441256316830”,1
+CCFC: 0,2
+CCFC: 0,4

OK

8.2.4 AT+CCWA, Call Waiting

AT Command Response/Action Remarks

at+ccwa=<n>, <mode>, <class x> Enables the call waiting feature. <n> Shows the result code in TA
When <mode>=2 and command are 0 Disable
successful: 1 Enable
+CCWA: <status>,<class1> <mode>
[<CR><LF>+CCWA: 0 Disable
<status>,<class2> [...]] 1 Enable
OK 2 Query
When <mode> is 0,1 <status>
OK 0 Not active
+CME ERROR: <err>
1 Active

at+ccwa? +CCWA: <n> <class>

OK Sum of integers representing
information for call blocking services
+CME ERROR: <err>
1 Voice
2 Data
at+ccwa=? +CCWA: (list of supported <n>s)
4 Fax
OK
+CME ERROR: <err>

The unsolicited result code does not include the alpha tag within the double-quote.

Note

98-08901C39-B 83
AT Commands

Example
At+ccwa=?
+CCWA: 00,01
OK
at+ccwa=0,0
OK
at+ccwa=0,2 //status query
+CCWA: 0,1
+CCWA: 0,2
+CCWA: 0,4
OK

at+ccwa=1,1 //Enable call waiting for voice call

OK

at+ccwa=1,2
+CCWA: 1,1
+CCWA: 1,2
+CCWA: 1,4
OK

8.2.5 AT+CHLD, Call Related Supplementary Services

AT Command Response/Action Remarks

at+chld=<mode> Switches between the active calls <mode>

OK 0 Releases all held calls or sets
+CME ERROR: <err> the User Determined User Busy
(UDUB) for a waiting call.
1 Releases all active calls (if any
exist) and accepts the other
at+chld? +CME ERROR: <err>
(held or waiting) call.
1X Releases a specific active call
at+chld=? +CHLD: (supported <mode>s)
X.
OK
2 Places all active calls (if any
+CME ERROR: <err> exist) on hold and accepts the
other (held or waiting) call.
2X Places all active calls on hold
except call X with which
communication will be
supported. If there is no such
call, returns error 22.
3 Adds a held call to the
conversation.

84 98-08901C39-B
 AT Commands

CALL STATE +CHLD modes

(+CLCC)

CHLD = 0 CHLD = 1 CHLD = 1X CHLD = 2 CHLD = 2X CHLD = 3

IDLE Error 3. Error 3. Error 3. Error 3. Error 3. If Error 3.

there is no
such call,
returns error
22.

SINGLE Error 3. Releases When X = 1, Puts call on Error 3. If Error 3.

ACTIVE active. release is hold. there is no
active. If not, such call,
returns error returns error
22. 22.

MPTY Error 3. Releases Releases a Puts mpty on Split. If there Error 3.

ACTIVE mpty call. specific call hold. is no such
Returns 2 x. If there is call, returns
"no carrier" no such call, error 22.
when there returns error
are 2 22.
outgoing
calls.

INCOMING Releases Error 3. Error 3. Error 3. Error 3. If Error 3.

CALL incoming there is no
call. such call,
returns error
22.

ACTIVE + Releases Releases Releases a Puts active Error 3. If Error 3.

WAITING waiting call. active call specific call call on hold there is no
and accepts x. If there is and accepts such call,
waiting call. no such call, the waiting returns error
returns error call. 22.
22.

MPTY Releases Releases Releases a Puts mpty on Splits. If Error 3.

ACTIVE + waiting call. mpty, specific call hold, accepts there is no
WAITING accepts x. If there is the waiting such call,
waiting. no such call, call. returns error
returns error 22.
22.

SINGLE Releases Accepts held Error 3. Accepts held Error 3. If Error 3.

HELD held call. call. call. there is no
such call,
returns error
22.

98-08901C39-B 85
AT Commands

CALL STATE +CHLD modes (Continued)

(+CLCC)

CHLD = 0 CHLD = 1 CHLD = 1X CHLD = 2 CHLD = 2X CHLD = 3

HELD MPTY Releases Accepts mpty Error 3. Accepts mpty Error 3. If Error 3.
held call. call. call. there is no
such call,
returns error
22.

DUAL Releases Releases Releases a Switches. Error 3. If Makes a

held call. active, specific call there is no conference
accepts the x. If there is such call, call.
other call. no such call, returns error
returns error 22.
22.

HELD + Releases Releases Releases a Switches. Error 3. If Makes a

MPTY held call. mpty, specific call there is no conference
ACTIVE accepts the x. If there is such call, call.
other call. no such call, returns error
returns error 22.
22.

ACTIVE + Releases Releases Releases a Switches. Error 3. If Makes a

MPTY HELD held call. active, specific call there is no conference
accepts the x. If there is such call, call.
mpty. no such call, returns error
returns error 22.
22.

HELD + Releases Accepts the Error 3. Accepts the Error 3. If Error 3.

WAITING waiting call. waiting call. waiting call. there is no
such call,
returns error
22.

HELD + Releases Accepts the Error 3. Accepts the Error 3. If Error 3.

MPTY waiting call. waiting call. waiting call. there is no
ACTIVE + such call,
WAITING returns error
22.

DUAL + Releases Releases Releases a Error 3 (too Error 3. If Joins the

WAITING waiting call. active, specific call many calls there is no dual calls.
accepts x. If there is on hold). such call,
waiting call. no such call, returns error
returns error 22.
22.

86 98-08901C39-B
 AT Commands

CALL STATE +CHLD modes (Continued)

(+CLCC)

CHLD = 0 CHLD = 1 CHLD = 1X CHLD = 2 CHLD = 2X CHLD = 3

ACTIVE + Releases Releases Releases a Error 3 (too Error 3. If Joins the

MPTY waiting call. mpty active, specific call many calls there is no dual and the
HELD + accepts x. If there is on hold). such call, mpty calls.
WAITING waiting call. no such call, returns error
returns error 22.
22.

ACTIVE + Releases Releases Releases a Error 3 (too Error 3. If Joins the

MPTY HELD waiting call. active, specific call many calls there is no dual and the
+ WAITING accepts x. If there is on hold). such call, mpty calls.
waiting call. no such call, returns error
returns error 22.
22.

Split: Places all active calls on hold except a specific call.

Switch: Puts the active call on hold and accepts the held call.
Note Error 3: "operation not allowed"
Error 22: "not found"

Example
at+chld=? //list of supported <n>s
+CHLD: (0,1,1X,2,2X,3)
OK

at+chld =1 //ME is not in conversation

+CME ERROR: operation not allowed

RING
ata
OK

at+chld
NO CARRIER

at+chld=2 //Call goes to hold

OK

at+chld=2 //Call is reconnected

OK

98-08901C39-B 87
AT Commands

at+chld=2 //Incoming intruder call

OK //First call goes to hold and second call is received

at+chld=2 //Second call goes to hold and first call becomes active
OK
at+chld=3 //Add the held call to the conversation

at+chld=21 //Second call goes to hold

OK

88 98-08901C39-B
 AT Commands

8.2.6 AT+CLCC, List Current Calls

AT Command Response/Action Remarks

at+clcc = <state> OK <state>

0 Enable clcc unsolicited
+CME ERROR: <err> indication.
1 Disable clcc unsolicited
indication.
at+clcc +CLCC: <id1>,<direction>,<call <Direction>
state>,<mode>,<mpty>[, 0 Mobile originated call.
<number>,<type>,<alpha> 1 Mobile terminated call.
<Call State>
OK
0 Active.
1 Held.
+CME ERROR: <err>
2 Dialing.
3 Alerting.
4 Incoming.
5 Waiting.
at+clcc=? OK
6 Released.

+CME ERROR: <err> <Mode>

0 Voice Call.
at+clcc? +CLCC: <state> 1 Data.
OK 2 Fax.
<Multiparty>
0 Call is not part of a conference
call.
+CME ERROR: <err> 1 Call is one of multiparty call
parties.
<Phone Number>
<Type>
129 Normal number.
145 International number with
access character +.
<alpha>
The Alpha string from phone book, if
this phone number exists in any
phone book.
<id>
Integer type call identification number,
as described in GSM 02.30 [19]
subclause 4.5.5.1. This number can
be used in +CHLD command
operations.

Add non-standard "released" state.

Asynchronous answers are also allowed, by using at+clcc=1.
Note In Release state, the call mode will always be zero.

98-08901C39-B 89
AT Commands

Example
AT+CLCC=?
OK

AT+CLCC?
+CLCC: 0
OK

at*d01256316830
OK

OK
AT+CLCC
+CLCC: 1,0,0,0,0,“01256316830”,129,“Shmuel”

OK
AT+CHUP
NO CARRIER

90 98-08901C39-B
 AT Commands

8.2.7 AT+CLCK, Facility Lock

AT Command Response/Action Remarks

at+clck=<facility>, When <mode>=2, command is <facility>

<mode>[,<password>[,<class>]] successful and <class> is relevant: CS Key pad
+CLCK: <status>, <class1> SC SIM Card
[<CR><LF>+CLCK: AO Block all outgoing calls
<status>,<class2> [...]]
OI Block all outgoing international
OK calls
When <mode>=0,1 and command OX Block outgoing international
successful: calls except to home country
OK AI Block all incoming calls
IR Block incoming calls when
+CME ERROR: <err> roaming outside home country
AB All blocking services
AG All outgoing blocking services
AC All incoming blocking Services
FD SIM fixed dialing feature
<mode>
at+clck? +CME ERROR: <err>
0 Unlock
1 Lock
2 Query status
<password>
Call Block password or PIN1 to
Lock/ Unlock SIM or PIN2 for SIM
at+clck=? +CLCK: (list of supported <facilitie>s)
Fixed Dialing Feature
OK
<class>
+CME ERROR: <err> Sum of integers representing of
information for call blocking services
1 Voice
2 Data
4 Fax
<status>
0 Not active
1 Active

Example
AT+CLCK=?
+CLCK: (“CS”,“SC”,“AO”,“OI”,“OX”,“AI”,“IR”,“AB”,“AG”, “AC”,“FD”)

OK
AT+CLCK?

+CME ERROR: “operation not allowed”

AT+CLCK=“OX”,2

98-08901C39-B 91
AT Commands

+CLCK: 0,1
+CLCK: 0,2
+CLCK: 0,4

OK

AT+CLCK=FD,2

+CLCK: 0,7 // Means that write operations into FD area are possible if PIN2 was entered at least once after power up.

OK

8.2.8 AT+CLIP, Calling Line Identification Presentation

AT Command Response/Action Remarks

at+clip=[<n>] Shows the number of the calling party <n>

OK 0 Disable (default)
1 Enable
+CME ERROR: <err> <m>
0 Clip not provisioned
1 Clip provisioned
2 Unknown
at+clip? +CLIP: <n>,<m>
OK
+CME ERROR: <err>

at+clip=? +CLIP: (list of supported <n>s)

OK
+CME ERROR: <err>

Example
at+clip=1
OK
RING
+CLIP: “+496113611404”,145
RING
+CLIP: “+496113611404”,145

at+clip=?
+CLIP: (000,001)
OK

92 98-08901C39-B
 AT Commands

at+clip=0
OK
RING

8.2.9 AT+CLIR, Calling Line Identification Restriction

AT Command Response/Action Remarks

at+clir =<n> OK <n>

+CME ERROR: <err> 0 Used according to the clir service
subscription
at+clir? +CLIR: <n>,<m> 1 Enable
OK 2 CLIR suppression in permanent
+CME ERROR: <err> mode
<m>
at+clir=? +CLIR: (list of supported <n>s) 0 Clir not provisioned
OK 1 Clir provisioned
2 Unknown
+CME ERROR: <err> 3 Clir temporarily restricted
4 Clir temporarily allowed

This command enables or disables the presentation of the CLI to the called party when originating a call. The
behavior is according to the last action performed by HS or RS232. (For information about When HS affects only
the next call and +CLIR command is affected until phone power off, refer to the following table.)
Note

Order of Actions First Call behavior Other Calls behavior

CLIR via RS232 According to the action performed by According to the action performed by
RS232. RS232.

CLIR by HS According to the action performed by Default behavior.

HS.

CLIR by HS and then CLIR via According to the action performed by According to the action performed by
RS232 RS232. RS232.

CLIR via RS232 and then by HS According to the action performed by According to the action performed by
HS. RS232.

Example
at+clir=?
+CLIR: (0,1,2)
OK
at+clir?

98-08901C39-B 93
AT Commands

+clir: 000,004
at+clir=2
OK
at+clir?
+clir: 002,004

8.2.10 AT+CMEE, Report Mobile Equipment

AT Command Response/Action Remarks

at+cmee=<n> Shows a description of the error <n>

OK 0 Disable
+CME ERROR: <err> 1 Enable (numeric)
2 Enable (verbose)
at+cmee? +CMEE: <n>
OK
+CME ERROR: <err>

at+cmee=? +CMEE: (list of supported <n>s)

OK
+CME ERROR: <err>

Example
at+cmee?
+CMEE: 000
OK

at+cmee=?
+CMEE: (0-2)
OK.

at+cmee=1
OK

at+cmee?
+CMEE: 1
OK

at+cmee=2
OK

at+cmee?

94 98-08901C39-B
 AT Commands

+CMEE: 2
OK

8.2.11 AT+CMGS, Sending an SMS Message

AT Command Response/Action Remarks

(cmgf=0) Sends the SMS message. <length>

at+cmgs=<length> <CR> Number of octets coded in the TP.
>PDU is given <cr>
<ctrl-z/ESC> The message is terminated with After terminating with <cr>, g18
control-Z character (0x1A). returns with “>” and then, the PDU
can be given from the TE.
The command is aborted with <esc>. <crtl-z>
If the message is sent successfully:
Indicates the end of the PDU.
+CMGS: 000.
OK
If the message is not sent
successfully:
+CMS ERROR: <err>

at+cmgs? +CME ERROR: <err>

at+cmgs=? OK
+CME ERROR: <err>

When an SMS is sent using AT+CMGS, the DTE receives the status. Sent messages are not stored in the SIM.
After an SMS is sent and stored in the SIM (using block mode commands), it can be filtered or displayed via
Note AT+CMGL=3. A similar message cannot be sent later using the AT+CMSS command.

98-08901C39-B 95
AT Commands

8.2.12 AT+CNUM, Subscriber Number

AT Command Response/Action Remarks

at+cnum +CNUM: Shows the numbers that were

<alpha1>,<number1>,<type1> entered into “My Phone Numbers”
[<CR><LF> +CNUM: from the Handset menu.
<alpha2>,<number2>,<type2>[...]]
<alpha>
OK
Alphanumeric string, associated with
+CME ERROR: <err> <number>.
<number>
at+cnum?
String type, phone type.

at+cnum=? OK <type>
+CME ERROR: <err> 129 Normal number.
145 International number with
access character +.

If you write a name that includes non-standard characters in “My Phone Number”, +CNUM will read that name
incorrectly.

Note

Example
at+CNUM=?
OK

at+CNUM
+CNUM: “voice”, “054556426”, 129
+CNUM: “data”, “054667739”, 129
+CNUM: “fax”, “054422417”, 129
OK

96 98-08901C39-B
 AT Commands

8.2.13 AT+COPS, Operator Selection

AT Command Response/Action Remarks

at+cops=[<mode>[,<format>[,<oper>] Selects the operator <mode>

]] OK 0 Automatic
+CME ERROR: <err> 1 Manual
2 De-register from network
at+cops=? +COPS:[list of supported (<stat>, 3 Set only <format>
long alpha numeric <oper>, short 4 Manual/automatic
alphanumeric <oper>, numeric
<oper>)][,, list of supported <format>
<mode>s), (list of supported 0 Long alphanumeric
<format>s)} 1 Short alphanumeric
OK 2 Numeric
+CME ERROR: <err> <Operator status>
0 Unknown
at+cops? +COPS: <mode>[,<format>,<oper>]
1 Available
OK
2 Current
+CME ERROR: <err>
3 Forbidden

When set command (=) is used without entering <oper>, the response is OK, but no action will be
performed (at+cops=<mode>,<format><cr>, the response is OK).

Note When manually de-registering from the network using AT+COPS=2,1, the phone automatically
searches for a new network and logs in.

Example
at+cops=?
+COPS: (2,“”,“D2 PRIVAT”,“26202”),(0,“”,“A1”,“23201”),(0,“”,“F SFR”,“20810”),(0,“”,“GR PANAFON”,“20205”),(0,“”,
“S EURO”,“24008”),(0,“”,“EUROTEL-CZ”,“23002”),(0,“”,“NL LIBERTEL”,“20404”),(0,“”,“I OMNI”,“22210”),(3,“”,
“D1-TELEKOM”,“26201”),,( 0,1,2,3,4),(0,1,2)

OK

at+cops?
+COPS: 0,0,“D2 PRIVAT”
OK

at+cops=0
OK

at+cops=1
OK

at+cops=1,0,d1-telekom

98-08901C39-B 97
AT Commands

ERROR

at+cops=1,1,d02
OK

at+cops=1,1,d01
ERROR

at+cops=2
OK

at+cops=3
OK

at+cops=4
OK

at+cops=4,2,d01
OK

at+cops=4,2,26201
ERROR

at+cops=4,0,“D1-Telekom”
ERROR

at+cops=4,0,d1-telekom
ERROR
at+cops=4,2,d
OK

at+cops=4,2,d02
OK

98 98-08901C39-B
 AT Commands

8.2.14 AT+CPBS, Selected Phone Book Memory Storage

AT Command Response/Action Remarks

at+cpbs=<storage> OK <storage>
+CME ERROR: <err> FD SIM fix dialing phone book
LD Last dialing phone book
at+cpbs? +CPBS: <storage>[,<used>,<total>] ME ME phone book
OK MT ME and SIM phone book
+CME ERROR: <err> SM SIM phone book
DD Direct Dial phone book
at+cpbs=? +CPBS: (list of supported RC ME received calls list
<storage>s) MC ME missed calls list
OK
+CME ERROR: <err>

The g18 responds to at+cpbs=? with the current initialized phone books:
+CPBS:("FD","LD","ME","MT","SM","DD","RC","MC"). It may take up to 45 seconds to see all the phone books.

Note MC (missed calls) and RC (received calls) share the same area. They are both limited to a total of 10 records, and
they are both sorted by their time stamps, where the first record in phone book is the latest call received or not
answered.

Example
at+cpbs=?
+CPBS: (“FD”,“LD”,“ME”,“MT”,“SM”,DD,“RC”,“MC”)
OK

at+cpbs?
+CPBS: 0,0
OK

at+cpbs=“fd”
OK

at+cpbs?
+CPBS: “FD”,1,10
OK

at+cpbs=“DC”
+CME ERROR: “operation not allowed”

at+cpbs=“LD”
OK

98-08901C39-B 99
AT Commands

at+cpbs?
+CPBS: “LD”,10,10
OK

at+cpbs=“me”
OK

at+cpbs?
+CPBS: “ME”,0,100
OK

at+cpbs=“MT”
OK

at+cpbs?
+CPBS: “MT”,14,200
OK

at+cpbs=“SM”
OK

at+cpbs?
+CPBS: “SM”,14,100
OK

100 98-08901C39-B
 AT Commands

8.2.15 AT+CPBW, Writing Phone Book Entries

AT Command Response/Action Remarks

at+cpbw=[<index>], [,<number> OK <index>

[<type> [,<text>]]] +CME ERROR: <err> Location number of the phone book
<number>
at+cpbw? +CME ERROR: <err> Phone number in format <type>
<type> type of address:
at+cpbw=? +CPBW: (list of supported
<index>s),[<nlength>], (list of 129 Normal format
supported <type>s), [<tlength>] 145 International format
OK <text>
+CME ERROR: <err> String type field of maximum
<tlength> length.
<tlength>
Maximum length of <text>
<nlength>
Maximum length of <number>

When creating a new entry without a name, the response is OK, but no action takes place.
The telephone book "MT" is a combination of "ME" and "SM". Entries should be written to a specific phone book
Note (ME or SM) instead of to the MT phone book. When writing to the SM or ME phone book, the g18 validates the string
length for phone number and label, as defined for the specific phone book. When writing to the MT phone book, the
g18 is unable to detect errors with a string length less than that allowed in MT phone book, but more than what is
defined in the specific phone book. In this case, the write action is not rejected, but the number and text will be
truncated to the limit allowed for the specific phone book.

Example,
at+cpbs=“sm”;+cpbw=?
+CPBW: (101-220),020,(255,129,145),014 // SM phone book definitions: number length limited to 20, text length limited
to 14.
OK
at+cpbs=“mt”;+cpbw=?
+CPBW: (001-220),032,(255,129,145),016 // MT phone book definitions: number length limited to 32, text length limited
to 16.
OK
The following statement attempts to write a record to the SM area in the MT phone book (record 110 is in this area), with 21
digits for the phone number, and 15 digits for text. This is valid for the MT phone book, and therefore no error is expected.
However, since it is written to the SM area, the phone number is truncated to 20 digits, and the text is truncated to 14 digits.

at+cpbw=110,“123456789012345678901”,,“123456789012345” // No error when writing to MT, to a slot defined in the SM

phone book
OK
at+cpbr=110

98-08901C39-B 101
AT Commands

+CPBR: 110,“12345678901234567890”,129,“12345678901234” // Record written to phone book as defined in the definition

limitation.
OK

at+cpbs=“mt”
OK

at+cpbw=?
+CPBW: (001-200),32,(255,129,145),18
OK

at+cmee=2
OK

at+cpbw=140,“+496113611404”,145,“Raum 1004”
OK

at+cpbs=“SM”
OK

at+cpbw=140,“496113611404”,145,“Raum1004”
OK

at+cpbs=“ME”
OK

at+cpbw=73,“491726706014”,145,“eigene number”
OK

at+cpbw=190,“491728788793”,145,“Freundin”
+CME ERROR: “invalid index”

at+cpbs?
+CPBS: “ME”,002,100
OK

102 98-08901C39-B
 AT Commands

8.2.16 AT+CPIN, Enter Pin

AT Command Response/Action Remarks

at+cpin=<pin>[,<newpin>] OK <pin>
+CME ERROR: <err> String type 4-8 digits.
Enters or changes pin number. When To enable SIM card or change PIN,
entering the pin, a new pin is not insert the current PIN. When phone is
required. blocked, insert the puk number.
<newpin>
at+cpin? +CPIN: <code> String type 4-8 digits.
OK Used when changing PIN or
+CME ERROR: <err> unblocking phone.
Responds with information about the
<code>
SIM and the PIN.
When PIN is not needed:
READY
at+cpin=? OK
+CME ERROR: <err> When PIN is needed:
SIM PIN
When PUK number is needed:
SIM PUK
When PIN2 is blocked:
SIM PUK2

The following AT commands are enabled without a valid SIM: GCAP, GMI,GMR, IFC, CEER, CGMI, CGMM,
CGMR, CGSN, CHUP, CIPE, CKPD, CMEE, CMER, CIP, CRC, CSQ, CR.

Note When PUK is required, and only one parameter is given in +CPIN, error "PUK is required" is returned.

Example
at+cpin=“3011” // The current PIN
OK

at+cpin=?
OK

at+cpin?
+CPIN: READY
OK

at+cpin=“3011”,“2811” // Change PIN to 2811

OK

at+cpin“1111” // Wrong PIN

ERROR

98-08901C39-B 103
AT Commands

at+cpin“1111” // Wrong PIN

ERROR

at+cpin“1111” // Wrong PIN

ERROR

at+cpin?
+CPIN: SIM PUK // After 3 times, phone is blocked.
OK

at+cpin=“71388330”,“3011” // When phone is blocked, release it with PUK1 and new PIN.
OK

AT+CLCK=“FD”,2 // Checking the status of Fix Dialing phone book

+CLCK: 0,7 // Enable dialing of all numbers
OK
AT+CLCK=“FD”,1,“2035” // Closing FD phone book for changes, and allowed to originate calls
// only to the numbers from the FD phone book
OK
AT+CLCK=“FD”,2
+CLCK: 1,7
OK
AT+CPBS=“FD” // Select FD phone book
OK
AT+CPBW=1,“343434”,129 // Try to change entry in the phone book
+CME ERROR: “SIM PIN2 required”
AT+CPIN?
+CPIN: READY
OK
AT+CLCK=“FD”,0,“1234” // Wrong PIN2 is inserted
+CME ERROR: “incorrect password”
A/ // Wrong PIN2 is inserted
+CME ERROR: “incorrect password”
A/ // Wrong PIN2 is inserted
+CME ERROR: “SIM PUK2 required”
AT+CPIN?
+CPIN: SIM PUK2 // PIN2 is blocked. Need PUK2 to release it.

OK

104 98-08901C39-B
 AT Commands

AT+CPIN=“61356375”,“2035” // Enter PUK2 and new PIN2

OK
AT+CPIN?
+CPIN: READY

OK

8.2.17 AT+CREG, Network Registration

AT Command Response/Action Remarks

at+creg=[<n>] OK <n>
+CME ERROR: <err> 0 Disables network registration,
Controls the presentation of an unsolicited result code (default)
unsolicited result code +CREG: 1 Enables network registration,
<stat> unsolicited result code
2 Enables network registration
at+creg? +CREG: <n>,<stat>[,<lac>,<ci>]. and location information,
OK unsolicited result code
+CME ERROR: <err> <stat>
0 Not registered
at+creg=? +CREG: (list of supported <n>s) 1 Registered (home network)
OK 2 Not registered, but ME searches
+CME ERROR: <err> for a network
3 Registration denied
4 Unknown
5 Registered roaming
<lac>
2-byte location code (hex)
<ci>
2-byte cell ID (hex)

Example
at+creg=?
+CREG: (000,001,002)
OK
at+creg?
+CREG: 000,001
OK
at+creg=2
OK
at+creg?
+CREG: 002,001,“6202”,“6113”
OK

98-08901C39-B 105
AT Commands

at+creg=1
OK
at+creg?
+CREG: 001,001
OK
at+creg=0
OK
at+creg=2,5
ERROR

at+creg?
+CREG: 002,001,“6202”,“6113”
OK

at+creg=1
OK
at+creg?
+CREG: 001,001
OK

8.2.18 AT+CSTA, Selecting Type of Address

AT Command Response/Action Remarks

at+csta=[<type>] OK <type> Number format

+CME ERROR: <err> 129 Local phone number
145 With international access code
at+csta? +CSTA: <type> character ‘+’
OK Use default 145 when dialing string
+CME ERROR: <err> includes international access code
character ‘+’, otherwise 129
at+csta=? +CSTA: (list of supported <type>s)
OK
+CME ERROR: <err>

Example
at+csta?
+CSTA: 129

OK
at+csta=145
OK

106 98-08901C39-B
 AT Commands

at+csta?
+CSTA: 145

OK
at+csta=129
OK
at+csta?
+CSTA: 129

OK

8.2.19 AT+CBST, Selecting Bearer Service Type

AT Command Response/Action Remarks

AT+CBST=[<speed>[,<name>[,<ce>] Sets the value <speed>

]] OK 6 4800 bps (V.32)
+CME ERROR: <err> 7 9600 bps (V.32)
70 4800 bps (V.110)
AT+CBST? +CBST: <speed>,<name>,<ce> 71 9600 bps (V.110)
OK <name>
+CME ERROR: <err> 0 data circuit asynchronous
<ce> connection element
AT+CBST=? +CBST: (list of supported
<speed>s),(list of supported 0 transparent
<name>s),(list of supported <ce>s) 1 non-transparent
OK
+CME ERROR: <err>

The g18 supports baud rates of 4800 to 9600 bps.

If you work at 4800 bps, do not use 57600 bps for your RS232 port.
Note

Example
at+cbst=?
+CBST: (006,007,070,071),(000),(000-001)
OK

at+cbst?
+CBST: 007,000,001
OK

at+cbst=1,0,1

98-08901C39-B 107
AT Commands

+CME ERROR: operation not supported

at+cbst=6
OK

at+cbst?
+CBST: 006,000,001
OK

at+cbst=7
OK

at+cbst?
+CBST: 007,000,001
OK

8.2.20 AT+CGMI, Requesting Manufacturer Identification

AT Command Response/Action Remarks

at+cmgi +CGMI: <manufacture> <manufacture>

OK Name of the manufacturer.
+CME ERROR: <err>

at+cmgi? +CME ERROR: <err>

at+cmgi=? OK
+CME ERROR: <err>

Example
at+cgmi
+CGMI: “Motorola”

OK

at+cgmi?
ERROR

108 98-08901C39-B
 AT Commands

8.2.21 AT+CGMM, Requesting Model Identification

AT Command Response/Action Remarks

at+cgmm +CGMM: <model> <model>

OK Model identification
+CME ERROR: <err>

at+cgmm? +CME ERROR: <err>

at+cgmm=? OK
+CME ERROR: <err>

Example
at+cgmm?
ERROR

at+cgmm=?
OK

at+cgmm
+CGMM: “L Series”

OK

8.2.22 AT+CGMR, Requesting Revision Identification

AT Command Response/Action Remarks

at+cgmr +CGMR: <revision> <revision>

OK Software revision number.
+CME ERROR: <err> Requests revision identification.

at+cgmr? +CME ERROR: <err>

at+cgmr=? OK
+CME ERROR: <err>

Example
at+cgmr?
ERROR

at+cgmr=?
OK
at+cgmr
+CGMR: g18_vE6.02.07

98-08901C39-B 109
AT Commands

OK

8.2.23 AT+CGSN, Requesting Product Serial Number Identification

AT Command Response/Action Remarks

at+cgsn +CGSN: <sn> <sn>

OK IMEI number
+CME ERROR: <err>

at+cgsn? +CME ERROR: <err>

at+cgsn=? OK
+CME ERROR: <err>

Example
at+cgsn?
ERROR
at+cgsn=?
OK
at+cgsn
+CGSN: “447764074608839”

OK

8.2.24 AT+CHUP, Hanging Up Calls

AT Command Response/Action Remarks

at+chup NO CARRIER If there is an active call, hangs up.

OK

at+chup? +CME ERROR: <err>

at+chup=? OK
+CME ERROR: <err>

Example
at+chup=?
OK

RING

at+chup

110 98-08901C39-B
 AT Commands

NO CARRIER

OK

at+chup?
ERROR

8.2.25 AT+CMGD, Deleting SMS Messages

AT Command Response/Action Remarks

AT+CMGD=<index> [,<delflag>] Deletes SMS or group of SMSs <index>

OK The location of the SMS in the
+CME ERROR: <err> memory.
<delflag>
AT+CMGD? +CME ERROR: <err> 0 or omitted Delete message.
1 Delete all messages,
AT+CMGD=? OK except unread or
+CME ERROR: <err> stored messages.
2 Delete all messages,
except unread or
unsent messages.
3 Delete all messages,
except unread
messages.
4 Delete all messages.

Delete SMS with ID=0 is not allowed.

Delete SMS with ID=75 is allowed.
Note Delete SMS with illegal ID or with non-existent SMS, ends with "Invalid index"
For 1-4 above, <index> should be a valid number, for <delflag> = 1/2/3/4, <index> should be in the
range of SMS storage memory (1–75), even though the message with this index might not exist.

Example
at+mmgl
+MMGL: 004,001,,041
07917952140230F2040B917952545600F10000208080418245001965B339DD080147A492D7A432A152DF15DFDFEA71
C10D
+MMGL: 005,001,,023
07917952140230F2040B917952545600F10000208011213182000465B3390D
+MMGL: 006,001,,009
0001FF00800000024122
+MMGL: 007,000,,023
07917952140230F2040B917952545600F100002080112151340004E131D90C
+MMGL: 008,002,,010

98-08901C39-B 111
AT Commands

0001FF0080000003416213
OK

at+cmgd=6
OK

at+mmgl
+MMGL: 004,001,,041
07917952140230F2040B917952545600F10000208080418245001965B339DD080147A492D7A432A152DF15DFDFEA71
C10D
+MMGL: 005,001,,023
07917952140230F2040B917952545600F10000208011213182000465B3390D
+MMGL: 007,000,,023
07917952140230F2040B917952545600F100002080112151340004E131D90C
+MMGL: 008,002,,010
0001FF0080000003416213
OK

at+cmgd=30,1
OK

at+mmgl
+MMGL: 007,000,,023
07917952140230F2040B917952545600F100002080112151340004E131D90C
+MMGL: 008,002,,010
0001FF0080000003416213
OK

at+cmgd=1,3
OK

at+mmgl
+MMGL: 007,000,,023
07917952140230F2040B917952545600F100002080112151340004E131D90C
OK

at+cmgd=1,4
OK

112 98-08901C39-B
 AT Commands

at+mmgl
OK

8.2.26 AT+CMGF, Message Format

AT Command Response/Action Remarks

at+cmgf= <mode> OK <mode>

+CME ERROR: <err> 0 PDU mode
1 Text mode (not supported)
at+cmgf? +CMGF: <mode>
OK
+CME ERROR: <err>

at+cmgf=? +CMGF: <list of supported <mode>s)

OK
+CME ERROR: <err>

Example
at+cmgf?
+CMGF: 000

OK
at+cmgf=?
+CMGF: (000)

OK
at+cmgf=1
+CME ERROR: operation not allowed

98-08901C39-B 113
AT Commands

8.2.27 AT+CMGL, Listing Messages

AT Command Response/Action Remarks

at+cmgl[=<stat>] If PDU mode (+CMGF=0) and <stat>

command successful: 0 "REC UNREAD", received unread
+CMGL: message (for example, new
<index>,<stat>,[<alpha>],<length> message).
<CR><LF><pdu> 1 "REC READ", received read
[<CR><LF>+CMGL:<index>,<stat>, message.
[<alpha>],<length><CR><LF><pdu> 2 "STO UNSENT", stored unsent
[...]] message.
OK 3 "STO SENT", stored sent
+CMS ERROR: <err> message.
4 "ALL", all messages (default).
at+cmgl? +CME ERROR: <err> <index>
The value of the message location in
at+cmgl=? +CMGL: (list of supported <stat>s) the range of location numbers is
OK supported by the associated memory.
+CME ERROR: <err>
<alpha>
Not supported.

Use of any valid value of +CMGL parameter (0-4) lists of all messages.
The selection list of messages is valid only in software versions above E6.01.10
Note

Example
at+cmgl=?
+CMGL: (000-004)

OK
at+cmgl?
ERROR

at+cmgl
+CMGL: 001,000,023
0791947122723033040B831027492204F000009930926145148004C2A2F308
OK.
Wait for OK before sending new AT commands.

Note

114 98-08901C39-B
 AT Commands

8.2.28 AT+CMGR, Reading Messages

AT Command Response/Action Remarks

at+cmgr=<index> If PDU mode (+CMGF=0) and <stat>

command are successful: 0 "REC UNREAD", received unread
+CMGR: message (for example, new
<stat>,[<alpha>],<length><CR><LF> message).
<pdu> 1 "REC READ", received read
OK message.
+CMS ERROR: <err> 2 "STO UNSENT", stored unsent
message.
at+cmgr? +CME ERROR: <err> 3 "STO SENT", stored sent
message.
at+cmgr=? OK 4 "ALL", all messages (default).
+CME ERROR: <err> <index>
The value of the message location in
the range of location numbers is
supported by the associated memory.
<alpha>
Not supported.

Example
at+cmgr=2
+CMGR: 001,,023
0791947122723033040B831027492204F000009930927190948004C2A2F308
OK

8.2.29 AT+CPAS, Phone Activity Status

AT Command Response/Action Remarks

AT+CPAS +CPAS: <pas> <pas>

OK 0 Ready
+CME ERROR: <err> 1 Unavailable
2 Unknown
AT+CPAS? +CME ERROR: <err> 3 Ringing (MT calls)
4 Call in progress
AT+CPAS=? +CPAS: (list of supported <pas>s) 5 Asleep
OK
+CME ERROR: <err>

Example
at+CPAS
+CPAS: 000

98-08901C39-B 115
AT Commands

OK
at+CPAS=?
+CPAS: (000-005)

OK
at+cpas?
ERROR

8.2.30 AT+CPBR, Reading Phone Book Entries

AT Command Response/Action Remarks

at+cpbr=<index> +CPBR: <index>

<index>,<number>,<type>,<text>
OK
+CME ERROR: <err>
Location number in the storage
<number>
Phone number in the <type> format

at+cpbr? +CME ERROR: <err> <type>

at+cpbr=? +CPBR: (list of supported
<index>s),<nlength>,<tlength>
OK
+CME ERROR: <err>
129 Local number
145 International number with
access character +
<text>
Name of the entry
<tlength>
Maximum length of <text>
<nlength>
Maximum length of <number>

Example
at+cpbr=?
+CPBR: (1-200),32,18

OK
at+cpbr=73
+CPBR: 73, “+496128970912”,145, “Eigene Number”

OK
at+cpbr=10 // Empty entry
OK
at+cpbr=101
+CPBR: 101,“+491721212”,145,“D2-Kundenbetreuung”

OK

116 98-08901C39-B
 AT Commands

at+cpbr=74
+CPBR: 74,“+496113611400”,145,“test”

OK
at+cpbr=124
+CPBR: 124,“+4917222333”,145,“D2-Hotelservice”

OK

8.2.31 AT+CPMS, Preferred Message Storage

AT Command Response/Action Remarks

at+cpms=<mem1>[,<mem2>] +CPMS: <mem1> <mem2>

<used1>,<total1>,<used2>,<total2> “SM” Memory storage
OK
<used>
+CMS ERROR: <err>
Used memory storage

at+cpms? +CPMS: <total>

<mem1>,<used1>,<total1>,<mem2>, Total memory storage
<used2>,<total2>
OK
+CMS ERROR: <err>

at+cpms=? +CPMS:
(list of support <mem1>s),
(list of support <mem2>s)
OK
+CMS ERROR: <err>

Example
at+cpms=?
+CPMS: (“SM”),(“SM”)

OK
at+cpms?
+CPMS: “SM”,005,020,“SM”,005,020

OK
at+cpms=“SM”
+CPMS: 005,020,005,020

OK
at+cpms?

98-08901C39-B 117
AT Commands

+CPMS: “SM”,005,020,“SM”,005,020

OK

8.2.32 AT+CSCA, Service Center Address

AT Command Response/Action Remarks

at+csca=<sca>,<type> OK <sca> Service center number

+CMS ERROR: <err> + International, allowed at start
only
at+csca? +CSCA: <sca>,<type> 0,9,*,# Digits and instruction
OK /,-,(,blank,),A,B,C,D Allowed,
+CMS ERROR: <err> ignored, not
saved
at+csca=? OK , Pause control
+CME ERROR: <err> ; Allowed at end of number
May be omitted or ignored,
but not saved
<type> Format of the number
129 Local number
145 International number with
access character +

Example
at+csca?
+CMS ERROR: SMSC address unknown

at+csca=?
OK
at+csca=“491722270333”,145
OK
at+csca?
+CSCA: “+491722270333”,145

OK

118 98-08901C39-B
 AT Commands

8.2.33 AT+CSCS, Selecting TE Character Set

AT Command Response/Action Remarks

at+cscs=<chset> OK <chset>
+CME ERROR: <err> GSM GSM alphabet
IRA International alphabet
at+cscs? +CSCS: <chest> UCS2 16-bit universal multiple-octet
OK coded character set
+CME ERROR: <err>

at+cscs=? +CSCS: (list of supported <chset>s)

OK
+CME ERROR: <err>

Example
at+cscs=?
+CSCS: (“GSM”,“IRA”, “UCS2”)

OK
at+cscs?
+CSCS: “IRA”

OK
at+cscs=“gsm”
OK
at+cscs?
+CSCS: “GSM”

OK
at+cscs=“IRA”
OK
at+cscs?
+CSCS: “IRA”

OK

98-08901C39-B 119
AT Commands

8.2.34 AT+CSMS, Selecting the Message Service

AT Command Response/Action Remarks

at+csms=<service> +CSMS: <mt>, <mo>, <bm> <service>

OK 0 GSM 03.40 and 03.41. The
+CMS ERROR: <err> syntax of SMS AT commands is
compatible with GSM 07.05
Phase 2 version 4.7.0. Phase
at+csms? +CSMS: <service>, <mt>, <mo>,
2+ features that do not require
<bm>
new command syntax may be
OK supported.
+CMS ERROR: <err>
<mt>,< mo>,< bm>
0 Type not supported
at+csms=? +CSMS: (list of supported
<service>s) 1 Type supported
OK <mt> Mobile terminated message
+CMS ERROR: <err> <mo> Mobile originate message
<bm> Broadcast type message

Example
at+csms
ERROR
at+csms=?
+CSMS: (000)

OK
at+csms?
+CSMS: 000,001,001,001

OK
at+csms=0
+CSMS: 001,001,001

OK

120 98-08901C39-B
 AT Commands

8.2.35 AT+CSQ, Signal Quality

AT Command Response/Action Remarks

AT+CSQ +CSQ: <rssi>,<ber> <rssi>

OK 0 0 Bars < -108 dBm
+CME ERROR: <err> 1 1 Bar -102 to -108 dBm
10 2 Bars -93 to -101 dBm
AT+CSQ? +CME ERROR: <err> 20 3 Bars -87 to -92 dBm
30 4 Bars -77 to -86 dBm
AT+CSQ=? +CSQ: (list of supported <rssi>s),(list 31 5 Bars > -76 dBm
of supported <ber>s) 99 Unknown or not detectable
OK
<ber> channel bit error rate (in
+CME ERROR: <err>
percent)
0–7 RXQUAL values in the GSM
05.08 table
99 Unknown or not detectable

BER information is not supported.

Note

Example
at+csq
+CSQ: 031, 099
OK

at+csq=?
+CSQ: (000-031,099),(000-007,099)
OK

8.2.36 AT+CEER, Extended Error Report

AT Command Response/Action Remarks

at+CEER +CEER: <report> <report>

OK Refer to Table 18, “ETSI 07.07
+CME ERROR: <err> Mobile Extended Error Report,” on
page 50.
at+CEER=? OK
+CME ERROR: <err>

At+CEER? +CME ERROR: <err>

98-08901C39-B 121
AT Commands

At the beginning of a call the ceer value is reset to "No information available". When the call is released by the
network, the network message is saved by the ceer value until the next call is started. When the user hangs up, no
information is saved. For information about ceer values, refer to Table 19, “ETSI 07.07 Network Service Related
Note Commands,” on page 51. The GPRS error values are not supported by this command.

Example
at+ceer=?
OK
at+ceer?
ERROR
at+ceer
+CEER: “No information available”

OK

122 98-08901C39-B
 AT Commands

8.2.37 AT+CKPD, Keypad Control

AT Command Response/Action Remarks

AT+CKPD=<Keys>[,<time>[,<pause>]] OK <Keys>
+CME ERROR: <err> # Hash (number sign)
* Star (*)
09 Number keys
AT+CKPD? +CME ERROR: <err> : Escape character for
manufacturer specific keys
AT+CKPD=? OK ; Escape character for string
+CME ERROR: <err> entering
< Left arrow
> Right arrow
C/c Clear display (C/CLR)
D/d Volume down
E/e Connection end (END)
L/l Phone lock (LOCK)
M/m Menu (MENU)
Q/q Quiet/mute (MUTE)
S/s Connection start (SEND)
T/t Store/memory (STO/M/M+)
U/u Volume up
V/v Forward in menu
Y/y Delete last character (C)
:0 Smart button (Colon followed
by zero)
:a VA Voice annotator (Colon
followed by A/a)
^ Up arrow
<time>, <pause>:
0..255 0 - 25.5 seconds (default
values are manufacturer
specific, but should be long
enough that a normal ME can
handle key strokes correctly).

Example
at+ckpd=?
OK
at+ckpd=M
ERROR

at+ckpd=“M>>S”
OK

98-08901C39-B 123
AT Commands

8.2.38 AT+FCLASS, Selecting a Mode

AT Command Response/Action Remarks

AT+FCLASS=<n> OK <n>
Puts the TA into a particular mode of 0 Data
operation. 1 Fax
+CME ERROR: <err>

AT+FCLASS? +FCLASS: <n>

OK
+CME ERROR: <err>

AT+FCLASS=? (list of supported <n>s)

OK
+CME ERROR: <err>

Example
AT+FCLASS=?
0,1

OK
AT+FCLASS?
+FCLASS: 0

OK

8.2.39 AT+GCAP, Requesting Complete Capabilities List

AT Command Response/Action Remarks

AT+GCAP GCAP: (list of <capabilitie>s)

OK
+CME ERROR: <err>

AT+GCAP? +CME ERROR: <err>

AT+GCAP=? +CME ERROR: <err>

Example
AT+GCAP
+GCAP: +FCLASS

OK
AT+GCAP=?

124 98-08901C39-B
 AT Commands

ERROR

AT+GCAP?
ERROR

8.2.40 AT+CMOD, Calling Mode

AT Command Response/Action Remarks

AT+CMOD=[<mode>] OK <mode>
+CME ERROR: <err> 0 Single mode
1 Alternating voice/fax
AT+CMOD? +CMOD: <mode> (teleservice 61)
OK
+CME ERROR: <err>

AT+CMOD=? +CMOD: (list of supported <mode>s)

OK
+CME ERROR: <err>

Example
AT+CMOD =?
+CMOD: (000, 001)

OK
AT+CMOD?
+CMOD: 000

OK
AT+CMOD=1
OK

98-08901C39-B 125
AT Commands

8.2.41 AT+CRLP, Radio Link Protocol

AT Command Response/Action Remarks

+CRLP= OK <iws>, <mws>, <T1>, <N2>:

[<iws>[,<mws>[,<T1>[,<N2>]]]] +CME ERROR: <err> IWF to MS window size (default 61),
MS to IWF window size (default 61),
+CRLP? +CRLP= <iws>,<mws>,<T1>,<N2>
OK Acknowledgement timer T1 (default
48),
+CME ERROR: <err>
Retransmission attempts N2
(default 6) in integer format (refer to
+CRLP=? +CRLP= (list of supported <iws>s),
GSM 04.22 [18] subclause 5.4.3)
(list of supported <mws>s), (list of
supported <T1>s), (list of supported
<N2>s)
OK
+CME ERROR: <err>

Example
AT+CRLP=?
+CRLP: (010-061),(010-061),(048-255),(006-010)
OK
AT+CRLP?
+CRLP: 061, 061, 048, 006

OK

8.2.42 AT+CR, Service Reporting Control

AT Command Response/Action Remarks

AT+CR= [<mode>] OK <mode>

+CME ERROR: <err> 0 Disables reporting
1 Enables reporting
AT+CR? +CR: <mode> <serv>
OK REL ASYNC Asynchronous
+CME ERROR: <err> non-transparent
REL SYNC Synchronous
AT+CR=? +CR: (list of supported<mode>s) non-transparent
OK
+CME ERROR: <err>

Set command controls whether or not intermediate result code +CR: <serv> is returned from the TA to the TE. If
enabled, the intermediate result code is transmitted at the point during connect negotiation at which the TA has
determined which speed and quality of service will be used, before any error control or data compression reports
Note are transmitted, and before the intermediate result code CONNECT is transmitted.

126 98-08901C39-B
 AT Commands

Example
AT+CR
ERROR

AT+CR=?
+CR: (000,001)

OK
AT+CR?
+CR: 000

OK

8.2.43 AT+CRC, Cellular Result Codes

AT Command Response/Action Remarks

AT+CRC= [<mode>] OK <mode>

+CME ERROR: <err> 0 Disables extended format
1 Enables extended format
AT+CRC? +CRC: <mode> <type>
OK REL ASYNC Asynchronous
+CME ERROR: <err> non-transparent
FAX Facsimile (TS 62)
AT+CRC=? +CRC: (list of supported VOICE Normal voice (TS 11)
<modes>s)
OK
+CME ERROR: <err>

This command controls whether or not the extended format of incoming call indication is used. When enabled, an
incoming call is indicated to the TE with unsolicited result code +CRING: <type> instead of the normal RING.

Note

Example
AT+CRC?
+CRC:000

OK
AT+CRC=1
OK

AT+CRC=?
+CRC: (000,001)

98-08901C39-B 127
AT Commands

OK
+CRING: VOICE // Incoming voice call

8.2.44 AT+CNMI, New Message Indications to TE+CNMI

AT Command Response/Action Remarks

AT+CNMI=[<mode>[,<mt>[,<bm>[,<d OK <mode>
s>[,<bfr>]]]]] +CMS ERROR: <err> 0 Buffer unsolicited result codes in
the TA. If TA result code buffer is
AT+CNMI? +CNMI: full, indications can be buffered
<mode>,<mt>,<bm>,<ds>,<bfr> elsewhere or the oldest
indications may be discarded and
OK
replaced with the new received
+CMS ERROR: <err> indications.
<mt>
AT+CNMI=? +CNMI: (list of supported <mode>s),
0 No SMS DELIVER indications are
(list of supported <mt>s), (list of
routed to the TE route message to
supported <bm>s), (list of supported
TE.
<ds>s), (list of supported <bfr>s)
1 Indication of memory location is
OK
routed to the TE.
+CMS ERROR: <err>
2 SMS DELIVER indications are
routed directly to TE.
<bm>
0 No CBM indications are routed to
TE.
2 New CBMs are routed directly to
TE.
<ds>
0 No SMS-STATUS-REPORTs are
routed to the TE.
1 SMS-STATUS-REPORTs are
routed to the TE using unsolicited
result code: +cds:
<length><cr><lf><pdu>.
<bfr>
0 TA buffer of unsolicited result
codes defined within this
command is flushed to TE when
<mode> 13 is entered (OK
response is given before flushing
the codes).

While conducting a g18 data call, the arrival of an SMS resets the +CNMI setting, thereby notifying that something
unexpected has occurred.

Note After automatically transferring a SMS/CBM message to the DTE (mt=2 and/or bm=2), the g18 waits for a +CNMA
response from the DTE (within one minute). If DTE does not respond within this time, or if another message arrives
from the network, the g18 saves the message in SIM, exits from SMS mode, and sets all CNMI parameters except
<bm> to zero.
When DTE does not respond on time for other SMS indications (E6.13.24 and above), the CNMI indication for cell
broadcast messages is not cleared automatically.

128 98-08901C39-B
 AT Commands

In the following scenario:

1 AT CNMI=0,1,0,1,0 or CNMI=0,2,0,1,0
2 MO DATA call, connected state.
3 SM received.
The g18 will end SMS mode and reset the CNMI parameters.This will indicate to the user that something occurred during the
data call.

Example
at+cmgl
OK // No messages on SIM
at+cnmi=0,2,2,1
OK
at+cnmi?
+CNMI: 000,002,002,001,000

OK

+CMT: 026 // First message indication

07917952140230F2040B917952545608F500001010034171700007B12915D49C1E01
at+cnma // Response of the DTE
OK

+CMT: 036 // Second message indication

07917952140230F2040B917952545608F500001010034183800013C7E793086A3EA5CEA4F308A23E
41D96715
at+cnma // Response of the DTE
OK
+CMT: 026 // Third message indication
07917952140230F2040B917952545608F500001010034102030007332911D49C1E01
at+cnmi?
+CNMI: 000,000,002,000,000 // CNMI parameters changed since the DTE did not response with +CNMA
OK
at+cmgl
+CMGL: 001,000,,026 // The third message stored in the SIM
07917952140230F2040B917952545608F500001010034102030007332911D49C1E01
OK
at+cmgl
+CMGL: 001,001,,026
07917952140230F2040B917952545608F500001010034102030007332911D49C1E01
+CMGL: 002,000,,029 // New message also stored in the SIM

98-08901C39-B 129
AT Commands

07917952140230F2040B917952545608F50000101003414240000BCEE215D42C4EA7C16311
OK
at+cnmi=0,2,2,1 // Setting CNMI parameters to receive new messages again on DTE
OK

at+cnmi=?
+CNMI: (000),(000-002),(000,002),(000,001),(000)

OK

8.2.45 AT+CMEC, Mobile Equipment Control Mode

AT Command Response/Action Remarks

AT+CMEC= [<keyp>[,<disp>[,<ind>]]] OK <keyp>

+CME ERROR: <err> 0 ME can be operated only through
its keypad
AT+CMEC? +CMEC: <keyp>,<disp>,<ind> 2 ME can be operated from both ME
OK keypad and TE
+CME ERROR: <err> <disp>
0 Only ME can write to its display
AT+CMEC=? +CMEC: (list of supported <keyp>s), <ind>
(list of supported <disp>s), (list of
0 Only ME can set the status of its
supported <ind>s)
indications
OK
+CME ERROR: <err>

Set command selects the equipment that operates the ME keypad, writes to the ME display and sets the ME
indications.

Note

Example
AT+CMEC?
+CMEC: 02, 00, 00

OK
AT+CMEC=?
+CMEC: (00,02), (00), (00)

OK
AT+CMEC=2, 0, 0
OK

130 98-08901C39-B
 AT Commands

8.2.46 AT+CMER, Mobile Equipment Event Reporting

AT Command Response/Action Remarks

AT+CMER= [<mode>[,<keyp>[, OK <mode>

<disp>[,<ind>[,<bfr>]]]]] +CME ERROR: <err> 0 Buffer unsolicited result codes in
the TA. If TA result code buffer is
AT+CMER? +CMER: <mode>, <keyp>, <disp>, full, codes can be buffered
<ind>, <bfr> elsewhere or the oldest ones can
be discarded.
OK
+CME ERROR: <err> <keyp>
0 No keypad event reporting.
AT+CMER=? +CMER: <disp>
(list of supported <mode>s), 0 No display event reporting.
(list of supported <keyp>s), (list of 1 Display event reporting +CDEV:
supported <disp>s), <Upper corner>, <text>, <Lower
(list of supported <ind>s), corner>.
(list of supported <bfr>s) The display height is 54 pixels:
OK 0–53.
+CME ERROR: <err> The upper corner refers to the
starting high point and the lower
corner refers to the bottom right
ending point.
<ind>
0 No indicator event reporting.
1 Indicator event +CIEV: <ind>,
<value>. <ind> indicates the
indicator order number and
<value> is the new value of
indicator.
+CIEV:00, 00 Battery indicator (0–3).
+CIEV:01, xx Signal bars # (xx=1–5).
+CIEV:02, xx Service availability 0/1.
+CIEV:03, xx SMS envelope ind
(0/1).
+CIEV:04, xx Call in progress (0/1).
+CIEV:05, xx Roaming indicator
(0/1).
+CIEV:06, xx Sim pin1 requested
(0/1).
+CIEV:07, x Sim SMS full (0/1).
+CIEV:08, x GPRS coverage (0/1).
+CIEV:10, xx Voice volume level
(xx=00–07).
+CIEV:11, xxRinger volume level
(xx=00–07).
<bfr>
0 TA buffer of unsolicited result
codes defined within this
command is cleared when
<mode> 13 is entered.

98-08901C39-B 131
AT Commands

Example
AT+CMER=?
+CMER: (00), (00), (00,01), (00,01), (00)

OK
AT+CMER?
+CMER: 00, 00, 00, 00, 00

OK
AT+CMER=0, 0, 1, 0, 0
OK

+CDEV: 19, “orange”, 35

8.2.47 AT+CPBF, Finding Phone Book Entries

AT Command Response/Action Remarks

AT+CPBF=<findtext> +CPBF: <index1>, <number>, <index1>, <index2>

<type>, <text>[<CR><LF>+CBPF:
<index2>, <number>, <type>,
<text>[..]]
OK
+CME ERROR: <err>
AT+CPBF? +CME ERROR: <err>
AT+CPBF=? +CPBF: <nlength>, <tlength>
OK
+CME ERROR: <err>
Integer type values in the range of
location numbers of phone book
memory
<number>
String type phone number of
format <type>
<type>
Type of address octet in integer
format (refer GSM 04.08 [8]
subclause 10.5.4.7)
<find text>, <text>
String type field of maximum length
<tlength>
Character set as specified by
command Select TE Character Set
+CSCS
<nlength>
Integer type value indicating the
maximum length of field <number> in
the current phone book
<tlength>
Integer type value indicating the
maximum length of field <text> in the
current phone book

132 98-08901C39-B
 AT Commands

Set command returns phone book entries (from the current phone book memory storage, selected with +CPBS)
when the alphanumeric field starts with <findtext>.

Note For example:

The name “RONEN” is in PB.
at+cpbf=“RON” +CPBF: 106, “054567432”, 129, “RONEN”
whereas,
at+cpbf=“ONE” Will yield no result
Example
at+cpbs =SM
OK

at+cpbf =?
+CPBF: 020, 014

OK
at+cpbf =“RON”
+CPBF: 105, “035655555”, 129, “RON”

+CPBF: 106, “054564254”, 129, “RONEN”

OK
at+cpbf =“ron”
OK
at + cpbf = /List of all entries
+CPBF: 101, “6251455”, 129, “AVI”
+CPBF: 102, “052646651”, 129, “DAVID”
+CPBF: 103, “04621515”, 129, “BEN”
+CPBF: 104, “02665111”, 129, “CHRIS”
+CPBF: 105, “03565555”, 129, “RON”
+CPBF: 106, “054564254”, 129, “RONEN”

OK

98-08901C39-B 133
AT Commands

8.2.48 AT+CESP, Entering SMS Block Mode

AT Command Response/Action Remarks

at+cesp OK Sets the TA in SMS block protocol

+CME ERROR: <err> mode.

at+cesp? +CME ERROR: <err>

at+cesp=? OK
+CME ERROR: <err>

To exit SMS Block mode, use block mode command: “exit SMS block mode” or disconnect the DTR.

Note

Example
at+cesp
OK

8.2.49 AT+CMGW, Writing Messages in PDU Mode

AT Command Response/Action Remarks

(cmgf=0) Stores the SMS message <length>

at+cmgw=<length><CR>
>PDU is given <ctrl-z/ESC>
If storage succeeds: Number of octets coded in the TP
+CMGW: <index> <cr>
OK After terminating with<cr>, the PDU
If storage fails: can be given from the TE
+CMS: <err> <crtl-z>
Indicates the end of the PDU
The message is terminated with
control-Z character (0x1A) <index>
Index of stored messages
The command is aborted with <esc>

at+cmgw? +CME ERROR: <err>

at+cmgw=? OK
+CME ERROR: <err>

Example
at+cmgw=24
>07917952140230F2040B917952545630F200000070528141630005A060B10902
<ctrl/Z>
+CMGW: 001

134 98-08901C39-B
 AT Commands

OK

8.2.50 AT+CTFR1, Diverting an Incoming Call to the Voice Mail

AT Command Response/Action Remarks

AT+CTFR1 OK If there is no waiting call in progress,

+CME ERROR: <err> returns error.

AT+CTFR1? +CME ERROR: <err>

AT+CTFR1=? +CME ERROR: <err>

Example
RING
at+ctfr1
OK

at+ctfr1 // When a call is not received

+CME ERROR: “operation not allowed”

8.2.51 AT+CNMA, DTE Confirming the Previous Message

AT Command Response/Action Remarks

AT+CNMA OK Must be sent within 60 seconds from

+CME ERROR: <err> the arrival of the message to the DTE.
If not, the message will be stored on
the SIM card and all the parameters
AT+CNMA? +CME ERROR: <err>
of the CNMI command except <bm>
will be set to zero.
AT+CNMA=? +CME ERROR: <err>

Refer to “AT+CNMI, New Message Indications to TE+CNMI”, page 128 for examples.

Note

98-08901C39-B 135
AT Commands

8.2.52 AT+CBAND, Changing Band

AT Command Response/Action Remarks

AT+CBAND = N OK Wait for power cycle to apply the

+CME ERROR: <err> change.
<N>
3 For 1900Mhz
4 For 900/1800Mhz

AT+CBAND? +CBAND: <N>

OK

AT+CBAND=? +CBAND: (list of supported <N>s)

OK

Example
at+cmee=2
OK
at+cband?
+CBAND: 4

OK
at+cpin?
+CPIN: READY

OK
at+cband=3
OK // g18 waits for power cycle
at+cpin?
+CME ERROR: “no network service”

136 98-08901C39-B
 AT Commands

8.2.53 AT+CBAUD, Setting the Baud Rate

AT Command Response/Action Remarks

AT+CBAUD=<n> OK <n> <rate>

OR +CME ERROR: <err> 0 300
AT+CBAUD=<rate> 1 600
2 1200
AT+CBAUD? + CBAUD: <rate> 3 2400
OK 4 4800
+CME ERROR: <err> 5 9600
6 19200
AT+CBAUD=? +CBAUD: (list of supported <n>s, 7 38400
<rate>s) 8 57600
OK 9 Auto baud rate detection
+CME ERROR: <err>

For example, AT+CBAUD=8 is equivalent to AT+CBAUD=57600.

Using AT+CBAUD=<baud> with <baud> value other than 9 will disable the auto baud rate detection feature.
Note The g18 supports up to 57600 auto baud within the accuracy limitations of the application’s baud (g18 meets the
RS232 specifications).
If you call MO CSD at 4800 bps (on the air), then do not use 57600 bps on your RS232 port.

Example
at+cbaud=?
+CBAUD: (0–9,300,600,1200,2400,4800,9600,19200,38400,57600)

OK

at+cbaud?
+CBAUD: 57600

OK

98-08901C39-B 137
AT Commands

8.2.54 AT+CGPRS, GPRS Coverage

AT Command Response/Action Remarks

AT+CGPRS +CGPRS: <mode> <mode>

OK 0 No GPRS coverage
+CME ERROR: <err> 1 GPRS coverage

AT+CGPRS? +CGPRS: <mode>

OK
+CME ERROR: <err>

AT+CGPRS=? +CME ERROR: <err>

Example
AT+CGPRS
+CGPRS: 0

OK
AT+CGPRS?
+CGPRS: 0

OK
AT+CGPRS=1
+CME ERROR: “operation not allowed”
This command without an attachment will always return zero.

Note

138 98-08901C39-B
 AT Commands

8.2.55 AT+CGPADDR, Showing the PDP Address

AT Command Response/Action Remarks

AT+CGPADDR=[<cid> [,<cid> +CGPADDR: <cid>,<PDP_addr> <cid>

[,]]] [<CR><LF>+CGPADDR: <cid>,<PDP_addr> A numeric parameter that
[...]] specifies a particular PDP context
OK definition.
+CME ERROR: <err> If no <cid> is specified, the
addresses for all defined context
are returned.
AT+CGPADDR? +CME ERROR: <err>

AT+CGPADDR=? +CGPADDR:(list of defined <cid>s)

OK
+CME ERROR: <err>

The execution command returns a list of PDP addresses for the specified context identifiers. The test command
returns a list of defined <cid>s.

Note

Example
AT+CGPADDR=?
+CGPADDR: (1,2,3)

OK

at+cgpaddr=1
+CGPADDR: 1, 0.0.0.0

OK

98-08901C39-B 139
AT Commands

8.2.56 AT+CGCLASS, GPRS MS Class

AT Command Response/Action Remarks

AT+CGCLASS= [<class>] OK <class>

+CME ERROR: <err> String parameter that indicates the
GPRS mobile class
AT +CGCLASS? +CGCLASS: <class> B Class B
OK
+CME ERROR: <err>

AT +CGCLASS=? +CGCLASS: (list of supported <class>s)

OK
+CME ERROR: <err>

Example
AT+CGCLASS=?

+CGCLASS: (B)

OK
AT+CGCLASS=“B”
OK
AT+CGCLASS=“A”
ERROR

140 98-08901C39-B
 AT Commands

8.2.57 AT+CGDCONT, Defining the PDP Context

AT Command Response/Action Remarks

+CGDCONT=[<cid>
[,<PDP_type> [,<APN>
[,<PDP_addr> [,<d_comp>
[,<h_comp> [,<pd1>
[,[,pdN]]]]]]]]]
AT+CGDCONT?
OK <cid>
+CME ERROR: <err> A numeric parameter that
specifies a particular PDP
context definition.
<PDP_type>
IP Internet Protocol
+CGDCONT: <cid>, <PDP_type>,
<APN>,<PDP_addr>, <data_comp>, <d_comp> Data compression
<head_comp>[,<pd1>[,[,pdN]]] 0 Off (default)
[<CR><LF>+CGDCONT: <cid>, <PDP_type>, 1 On
<APN>,<PDP_addr>, <data_comp>, <h_comp> Header
<head_comp>[,<pd1>[,[,pdN]]] compression
[...]] 0 Off (default)
OK 1 On
+CME ERROR: <err>

AT+CGDCONT=? +CGDCONT: (range of supported <cid>s),

<PDP_type>,,,(list of supported <d_comp>s),
(list of supported <h_comp>s)[,(list of supported
<pd1>s)[,[,(list of supported <pdN>s)]]]
[<CR><LF>+CGDCONT: (range of supported
<cid>s),
<PDP_type>,,,(list of supported <d_comp>s),
(list of supported <h_comp>s)[,(list of supported
<pd1>s)[,[,(list of supported <pdN>s)]]]
[...]]
OK
+CME ERROR: <err>

Read command returns the current settings for each defined context.
Test command returns the parameter value ranges for each <PDP_type>.
Note

Example
AT+CGDCONT=?

+CGDCONT: (1-3),(“IP”),,,(0,1),(0,1)

OK

AT+CGDCONT?

+CGDCONT: 1,“IP”,“”,“0.0.0.0”,0,0
+CGDCONT: 2,“IP”,“”,“0.0.0.0”,0,0

98-08901C39-B 141
AT Commands

+CGDCONT: 3,“IP”,“”,“0.0.0.0”,0,0

OK
AT+CGDCONT=1,“IP”,“RTY”,“123.32.45.9”
OK
AT+CGDCONT=4 / / Only allowed to set up to 3 PDP contexts
ERROR

8.2.58 AT+CGQMIN, Quality of Service Provider

AT Command Response/Action Remarks

AT+CGQMIN=[<cid> OK <cid>
[,<precedence> [,<delay> +CME ERROR: <err> A numeric parameter that specifies
[,<reliability.> [,<peak> a particular PDP context definition.
[,<mean>]]]]]]
<precedence>
A numeric parameter that specifies
AT+CGQMIN? +CGQMIN: <cid>, <precedence >, <delay>,
the precedence class.
<reliability>, <peak>, <mean>
[<CR><LF>+CGQMIN: <cid>, <precedence >, <delay>
<delay>, <reliability.>, <peak>, <mean>[...]] A numeric parameter that specifies
the delay class.
OK
+CME ERROR: <err> <reliability>
A numeric parameter that specifies
AT+CGQMIN=? +CGQMIN: <PDP_type>, (list of supported the reliability class.
<precedence>s), (list of supported <peak>
<delay>s), (list of supported A numeric parameter that specifies
<reliability>s), (list of supported the peak throughput class.
<peak>s), (list of supported <mean>s) <mean>
[<CR><LF>+CGQMIN: <PDP_type>, (list of A numeric parameter that specifies
supported <precedence>s), (list of the mean throughput class.
supported <delay>s), (list of supported
<reliability>s), (list of supported
<peak>s), (list of supported <mean>s)
OK
+CME ERROR: <err>

Read command returns the current settings for each defined context.
Test command returns the parameter value ranges for each <PDP_type>.
Note For more details about Quality of Service, refer to ETSI specification GSM 03.60.

Example
AT+CGQMIN=?
+CGQMIN: (1-3),(0-3),(0-4),(0-5),(0-9),(0-18,31)

OK

142 98-08901C39-B
 AT Commands

AT+CGQMIN?

+CGQMIN: 1,2,4,3,9,10
+CGQMIN: 2,2,4,3,9,10
+CGQMIN: 3,2,4,3,9,10

OK

8.2.59 AT+CGACT, PDP Context Activation/Deactivation Request

AT Command Response/Action Remarks

AT+CGACT=[<state> [,<cid> OK <state>: Indicates the state of

[,<cid>[,]]]] +CME ERROR: <err> GPRS attachment.
0 Detached.
AT+CGACT? +CGACT: <cid>, <state> 1 Attached.
[<CR><LF>+CGACT: <cid>, <state> <cid>
OK A numeric parameter that
+CME ERROR: <err> specifies a particular PDP context
definition.
AT+CGACT=? +CGACT: (list of supported <state>s)
OK
+CME ERROR: <err>

Example
AT+CGACT=?
+CGATT: (0, 1)
OK
AT+CGACT?

+CGACT: 1,0
+CGACT: 2,0
+CGACT: 3,0

OK

AT+CGACT=1

ERROR // GPRS network not present.

In some GPRS networks, for example Germany, +CGACT is not supported. The ATD*99# command can be used
to make a connection.

Note

98-08901C39-B 143
AT Commands

8.2.60 AT+CGATT, GPRS Attach/Detach Request

AT Command Response/Action Remarks

AT+CGATT= [<state>] OK <state>

+CME ERROR: <err> Indicates the state of the GPRS
attachment:
AT+CGATT? +CGATT: <state> 0 Detached.
OK 1 Attached.
+CME ERROR: <err> If no <state> is given, the default
state is the current state and nothing
AT+CGATT=? +CGATT: (list of supported <state>s) needs to be done.
OK
+CME ERROR: <err>

Example
AT+CGATT=?

+CGATT: (0, 1)

OK
AT+CGATT?

+CGATT: 0

OK
AT+CGATT=1
ERROR
AT+CGATT=0

OK

144 98-08901C39-B
 AT Commands

8.2.61 AT+CGQREQ, Defining/Modifying/Removing a Requested Quality of Service Profile

AT Command Response/Action Remarks

AT+CGQREQ=[<cid> OK <cid>
[,<precedence> +CME ERROR: <err> A numeric parameter that specifies a
[,<delay>[,<reliability.> [,<peak> particular PDP context definition.
[,<mean>]]]]]]
<precedence>
A numeric parameter that specifies the
AT+CGQREQ? +CGQREQ: <cid>, <precedence >, <delay>,
precedence class.
<reliability>, <peak>, <mean>
OK <delay>
+CME ERROR: <err> A numeric parameter that specifies the
delay class.

AT+CGQREQ=? +CGQREQ: <PDP_type>, (list of supported <reliability>

<precedence>s), (list of supported
<delay>s), (list of supported
<reliability>s), (list of supported
<peak>s), (list of supported <mean>s)
OK
+CME ERROR: <err>
A numeric parameter that specifies the
reliability class.
<peak>
A numeric parameter that specifies the
peak throughput class.
<mean>
A numeric parameter that specifies the
mean throughput class.

Example
AT+CGQREQ=?
+ CGQREQ: (1-3),(0-3),(0-4),(0-5),(0-9),(0-18,31)

OK
AT+CGQREQ?
+CGQREQ: 1,2,4,3,9,10
+CGQREQ: 2,2,4,3,9,10
+CGQREQ: 3,2,4,3,9,10
OK

AT+CGQREQ=1,0,,0,0,0
OK

AT+CGQREQ?
+CGQREQ: 1,0,4,0,0,0
+CGQREQ: 2,2,4,3,9,10
+CGQREQ: 3,2,4,3,9,10

OK

98-08901C39-B 145
AT Commands

8.2.62 AT+CIMI, Requesting International Mobile Subscriber Identity (IMSI)

AT Command Response/Action Remarks

AT+CIMI +CIMI: <IMSI> <IMSI>

OK International Mobile Subscriber
+CME ERROR: <err> Identity (string without double quotes)

AT+CIMI? +CME ERROR: <err>

AT+CIMI=? OK
+CME ERROR: <err>

Example
AT+CIMI=?
OK

AT+CIMI

+CIMI: 425010100420457

OK

146 98-08901C39-B
 AT Commands

8.2.63 AT+CRSM, Restricting SIM Access

AT Command Response/Action Remarks

AT+CRSM=<command>,<fileid> +CRSM: <command>

<sw1>,<sw2>[,<response>]
OK
+CME ERROR: <err>
AT+CRSM? +CME ERROR: <err>
AT+CRSM=? +CRSM:
(list of supported <command>s),
(list of supported <fileid>s)
OK
+CME ERROR: <err>
Only command 176 is supported.
<fileid>
1 Flex-ID
2 Factory Info #1
3 Factory Info #2
197 IMSI
214 GID1
242 ICC ID
243 GID2
<sw1>, <sw2>:Reason
0 0 Success
0 1 SEEM not allowed: SIM card has
been removed or no such
element.
0 2 Bad record number: Record
number is out of valid range
0 3 Bad PIN: User has entered an
incorrect PIN code
0 4 Other technical problem: SIM
card malfunction
0 5 Unavailable: Data is temporarily
unavailable (initializing)
255 253 Not Allowed: Call processor is
still initializing
255 254 Bad Device: Call processor has
an internal error
255 255 Locked: Phone is locked by user
<response>
Response of a successful completion of
the command previously issued
(hexadecimal character uppercase format).
The requested data will be returned.

Example
AT+CRSM=?

CRSM: (176),(1-3,197,214,242,243)
OK
AT+CRSM=176,214

CRSM: 0,0,FFFFFFFFFFFFFFFFFF00 0000000000000000

OK

98-08901C39-B 147
AT Commands

8.2.64 AT+CPOL, Preferred Operator List

AT Command Response/Action Remarks

AT+CPOL=[<index>][,<format> OK <index>
[,<oper>]] +CME ERROR: <err> Integer type; the order number of the
operator in the SIM preferred
AT+CPOL? +CPOL: <index1>,<format>,<oper1> operator list
[<CR><LF>+CPOL: <format> of <oper>
<index2>,<format>,<oper2> 0 Long format alphanumeric
[...]] 1 Short format alphanumeric
OK 2 Numeric
+CME ERROR: <err>
<oper>
String type; <format> indicates
AT+CPOL=? +CPOL: (list of supported whether the format is alphanumeric or
<index>es),(list of supported numeric
<format>s)
OK
+CME ERROR: <err>

Example
AT+CPOL =?

+CPOL: (1-32),(0-2)

OK
AT+CPOL?

+CPOL: 001, 002, “425-01”

+CPOL:00 2, 002, “250-99”

OK
AT+CPOL =1

OK
AT+CPOL =1

+CME ERROR: Not found // Index “1” is emptied before test

148 98-08901C39-B
 AT Commands

8.2.65 AT+CIPE, ENABLE +CIP AT Command

AT Command Response/Action Remarks

AT+CIPE=<mode> OK <mode>
+CME ERROR: <err> 0 Disable +CIP command
1 Enable +CIP command
AT+CIPE? +CIPE: <mode>
OK
+CME ERROR: <err>

AT+CIPE=? +CIPE: <list of supported modes>

OK
+CME ERROR: <err>

Example
AT+CIPE=1
OK
AT+CIPE?
+CIPE: 1

OK
AT+CIPE=?
+CIPE: (0, 1)

OK

8.2.66 AT+CIP, IP Primitive Over AT Command

AT Command Response/Action Remarks

AT+CIP=<Data length> +CIP: <Data length>, <Prim id Cnf/ Data length

,<Prim_Id>,<Sub_addr>,<Data> Ind>, <Data> (characters) In decimal
Prim_Id In hex (2 bytes)
OK Sub_addr
(Destination) In hex (2 bytes)
Data In hex
+CME ERROR: <err> Note: 2 characters in 1 byte

AT+CIP? +CME ERROR: <err>

AT+CIP=? +CME ERROR: <err>

Example
at+cip=8,a842,0020,00010001

98-08901C39-B 149
AT Commands

+CIP: 38,a844,0001093033353638343133318105726F6E6974
OK

8.2.67 AT+CRTT, Selecting the Ring Tone

AT Command Response/Action Remarks

AT+CRTT= OK <RingTypeNumber>
<RingTypeNumber>,<operation> +CME ERROR: <err> 0 Standard
1 British
AT+CRTT? +CRTT: <RingTypeNumber> 2 French
OK 3 German
+CME ERROR: <err> 4 Bravo
5 3 Tone
AT+CRTT=? +CRTT: (<list of supported 6 Siren
<RingTypeNumber>s), (<list of 7 Quick
supported <operation>s)
8 1 Ring
OK
9 High
+CME ERROR: <err> 10 Music
<operation>
0 Play
1 Set

Example
AT+CRTT=?
+CRTT: (0–10), (0–1)

OK
AT+CRTT=4, 1

OK
AT+CRTT?
+CRTT: 4

OK

150 98-08901C39-B
 AT Commands

8.2.68 AT+CPWD, Changing the Password

AT Command Response/Action Remarks

AT+CPWD=<fac>,<oldpwd>, OK <fac> string type; facility (upper/lower

<newpwd> +CME ERROR: <err> case acceptable)
CS Control surface (keypad)
AT+CPWD? +CME ERROR: <err> SC SIM card
AO Block all outgoing calls
AT+CPWD=? +CPWD: list of supported OI Block outgoing international
(<fac>,<pwdlength>s) calls
OK OX Block outgoing international
+CME ERROR: <err> calls except to home country
AI Block all incoming calls
IR Block incoming calls when roaming
outside home country
AB All blocking services
AG All outgoing blocking services
AC All Incoming blocking services
FD SIM fixed dialing feature (not
supported)
P2 SIM PIN2
<oldpwd>, <newpwd>
string type
<oldpwd>
The same as the password specified for
the facility from the ME user interface or
using the command Change Password
+CPWD.
<newpwd>
The new password; maximum length of
password can be determined with
<pwdlength>.
<pwdlength>
Integer type; maximum length of the
password for the facility.

8.2.69 Fax AT Commands

AT Command Function Remarks

AT+FCLASS Select mode 0 Data

1 Fax

AT+FAE Fax auto answer Class 1

AT+FRH Fax receive hdlc data Class 1

AT+FRM Fax receive data Class 1

98-08901C39-B 151
AT Commands

AT Command Function Remarks

AT+FRS Fax receive silence Class 1

AT+FTH Fax transmit hdlc data Class 1

AT+FTM Fax transmit data Class 1

AT+FTS Fax transmit silence Class 1

8.2.70 AT+MTDTR, DTR Line Test Command

AT Command Response/Action Remarks

AT+MTDTR +MTDTR: <n> <n>

OK 1 DTR is active
+CME ERROR: <err> 0 DTR is not active

AT+MTDTR=? OK
+CME ERROR: <err>

AT+MTDTR? +MTDTR: <n>

OK
+CME ERROR: <err>

The command is accepted even when the SIM card is missing.

Note

8.2.71 AT+MTCTS, CTS Line Test Command

AT Command Response/Action Remarks

AT+MTCTS OK Deactivates CTS. Wait approximately

+CME ERROR: <err> 1 second and then activate CTS.

AT+MTCTS? +CME ERROR: <err>

AT+MTCTS=? OK
+CME ERROR: <err>

152 98-08901C39-B
 AT Commands

8.2.72 AT+MCWAKE, DTE Wake Line Control Command

AT Command Response/Action Remarks

AT+MCWAKE= <mode> OK <mode>

+CME ERROR: <err> 0 Send no indication
1 Send indication when GPRS
AT+MCWAKE=? +MCWAKE: (list of supported coverage goes off
<mode>s) 2 Send indication when GPRS
OK coverage goes on (default)
+CME ERROR: <err>

AT+MCWAKE? +MCWAKE: <Mode>

OK
+CME ERROR: <err>

8.2.73 AT+CMSS, Send Message from Storage

AT Command Response/Action Remarks

AT+CMSS=<index>[,<da>[,<toda>]] If PDU mode (+CMGF=0) and send <mr> Message reference

are successful: <da> Destination address
+CMSS: <mr> <toda> Type of destination address
OK 129
If send fails: 145
+CMS ERROR: <err>

AT+CMSS? +CME ERROR: <err>

AT+CMSS=? OK
+CME ERROR: <err>

Example
AT+CMSS=1, “054511511”
+CMSS: 002

98-08901C39-B 153
AT Commands

8.2.74 AT+MMGL, Message List

AT Command Response/Action Remarks

AT+MMGL[=<stat>] If PDU mode (+CMGF=0) and <stat>

command are successful: 0 “REC UNREAD”, received
+MMGL: unread message
<index>,<stat>,[<alpha>],<length> 1 “REC READ”, received read
<CR><LF><pdu> message
[<CR><LF>+MMGL:<index>,<stat>, 2 “STO UNSENT”, stored unsent
[<alpha>],<length><CR><LF><pdu> message
[...]] 3 “STO SENT”, stored sent
OK message
If not: 4 “ALL”, all messages (default)
+CMS ERROR: <err>

AT+MMGL? +CMS ERROR: <err>

AT+MMGL=? +MMGL: (list of supported <stat>s)

OK
+CME ERROR: <err>

This new AT command returns the SMS message list without changing the message status from unread to read. It
is used in the same way as +CMGL.

Note This command is supported in software versions above E6.01.10.

8.2.75 AT+MMGR, Read Message

AT Command Response/Action Remarks

AT+MMGR=<index> If PDU mode (+CMGF=0) and command are <stat>

successful: 0 "REC UNREAD", received unread
+MMGR: message (for example, new
<stat>,[<alpha>],<length><CR><LF><pdu> message).
OK 1 "REC READ", received read
If not: message.
+CMS ERROR: <err> 2 "STO UNSENT", stored unsent
message.
AT+MMGR? +CME ERROR: <err> 3 "STO SENT", stored sent message.
4 "ALL", all messages (default).
AT+MMGR=? OK <index>
+CME ERROR: <err> Value of message location in the range
of location numbers, supported by the
associated memory.
<alpha>
Not supported.

154 98-08901C39-B
 AT Commands

This new AT command returns the SMS message list without change the message status from unread to read. It is
used in the same way as +CMGR.

Note This command is supported in software versions above E6.01.10.

8.2.76 AT+MMGA, Changing the Message Attributes

AT Command Response/Action Remarks

AT+MMGA = <index>, <attribute> OK <index>

+CME ERROR: <err> An integer between 1 and 75
<attribute>
AT+MMGA? +CME ERROR: <err> 0 <received-unread>
1 <received-read>
AT+MMGA =? +MMGA: (001 – 075), (000-001)
OK
+CME ERROR: <err>

This command is supported in software versions above E6.01.10.

SMS attributes can be one of the following: received-unread or received-read. Since there are new AT commands:
Note MMGR & MMGL that return the message without changing its attribute from received-unread to received-read, this
set command can be used to change the specific message attribute from received-unread to received-read and
vice versa.
The test command returns the entire available <index>es and <attribute>s supported by this command.

8.2.77 AT+MSCTS, Motorola Sleep CTS Control

AT Command Response/Action Remarks

AT+MSCTS=<control> OK <control>
+CME ERROR: <err> 0 Default. Ignores the wakeup
line state.
AT+MSCTS? +MSCTS: <control> 1 When g18 is awakened and the
OK DTE wakeup line is high, CTS
will not be activated.
+CME ERROR: <err>

AT+MSCTS=? +MSCTS: (list of supported

<control>s)
OK
+CME ERROR: <err>

This new AT command controls CTS behavior and will deactivate it when the unit is in sleep mode. When there is
no activity, g18 may enter the sleep-awake sequence, which can occur every 30-40 milliseconds.

Note When sending data, use the wakeup line, either pin #15 at the FC 36 pin, or pin #10 at the DIN 28 pin, to awaken
the g18.
This command is supported in software versions E6.13.24 and above.

98-08901C39-B 155
AT Commands

When the DTE is not connected to the wakeup line, do not use this command.

!
Warning
Using At+MSCTS=1 will deactivate the CTS after g18 has entered sleep mode, and the DTE will be unable
to communicate with g18 until powered on.
To enable communication between the DTE and g18 when the DTE is powered off:
1 Change the DTE flow control to none, and then send AT&K0; +MSCTS=0.
2 Wait for OK, and then send At&K3.
3 Wait for OK, and then change the DTE flow control to HW.

Example
at+mscts=1 // feature ON
OK

at+mscts?
+MSCTS: 1

OK

at+mscts=?
+MSCTS: (0,1)

OK

at+mscts=0
OK

at+mscts?
+MSCTS: 0

OK

156 98-08901C39-B
 AT Commands

8.2.78 AT+CSMP, Set SMS SIM Parameters

AT Command Response/Action Remarks

AT+CSMP=[<fo>[,<vp>[,<pid>[,<dcs OK <fo> First Octet

>]]]] +CME ERROR: <err> Default, and after power up = 17
This parameter is saved on the g18
AT+CSMP? +CSMP: <fo>,<vp>,<pid>,<dcs> NVM.
OK <vp> Validity Period
+CME ERROR: <err> Uses a relative format
Range: 0 – 225
AT+CSMP=? OK Default value = 167
+CME ERROR: <err> 000 – 143:
(<vp>+1) x 5 minutes, meaning
five-minute intervals for up to 12
hours.
144 – 167:
12 hours + ((<vp> - 143) x 30
minutes)
168 – 196:
(<vp> - 166) x 1 day
197 – 255:
(<vp> - 192) x 1 week
This parameter is saved on SIM.
<pid> Protocol Identifier
Range: 0 – 225
Default value = 0
Support values:
0 Text
34 Fax
36 Voice
37 ERMES
38 Paging
49 X400
50 eMail
This parameter is saved on SIM.
<dcs> Data Coding Scheme
Default, and after power up = 0. This
parameter is ignored, not verified,
and stored in the g18 NVM.

Example
at+csmp=?
OK
at+csmp?
+CSMP: 17,119,0,0

OK

98-08901C39-B 157
AT Commands

at+csmp= // Set default parameters

OK
at+csmp?
+CSMP: 17,167,0,0

OK
at+csmp=20
OK
at+csmp?
+CSMP: 20,167,0,0

OK
at+csmp=19,119,36,1
OK
at+csmp?
+CSMP: 19,119,36,1

OK

// POWER CYCLE

at+csmp?
+CSMP: 17,119,36,0 // Only <vp> and <pid> are saved. Other parameters are ignored and not saved.
OK

158 98-08901C39-B
 AT Commands

8.2.79 AT+CSVM, Set VoiceMail Parameters

AT Command Response/Action Remarks

AT+ CSVM= Sets or clears the voicemail number <mode>

<mode>[,<number>[,<type>]] in the EEPROM or SIM, depending 0 Disable. Clears the number in
on the type of SIM card. the EEprom.
OK 1 Enable. Must be followed by a
+CME ERROR: <err> number.
<number> String format up to 35
AT+ CSVM? For mode=1: characters
+CSVM: + International, allowed at start
1, <number>, <type> only.
OK 0,9,*,# Digits and instruction
For mode=0: /,-,(,blank,),A,B,C,D Allowed,
+CSVM: 0 ignored, not
OK saved
+CME ERROR: <err> , Pause control.
; Allowed at end of number.
May be omitted or ignored,
AT+ CSVM=? +CSVM: (list of supported mode>s),
but not saved.
(list of supported <type>s)
OK <type> Type of number
+CME ERROR: <err> Range: 0 – 255
129 International or unknown
international
145 International number
If <number> starts with +, then
<type> must be 145 or omitted.
If <type> is 145 and <number> does
not start with +, then add + to the start
of <number> (length of new
<number> should not exceed 35).
<number> must include at least one
digit.
The updated <number> is saved on
either the EEPROM or SIM,
depending on the type of SIM card.

Example
at+csvm=?
+CSVM: (0,1),(129,145)

OK
at+csvm?
+CSVM: 1,"*155",129

OK
at+csvm=0 // Number cleared from eeprom
OK

98-08901C39-B 159
AT Commands

at+csvm?
+CSVM: 0

OK
at+csvm=1
ERROR // Must be followed by a number
at+csvm=1,"+155",129
ERROR // If <number> starts with '+' then <type> must be 145 or omitted.
at+csvm=1,"+155",145
OK
at+csvm=1,"+155"
OK
at+csvm?
+CSVM: 1,"+155",145
at+csvm=1,"*155AB "// (/,-,(,blank,),A,B,C,D) : allowed, ignored, not saved.
OK
at+csvm?
+CSVM: 1,"*155",129

OK
at+csvm=1,"bcd" // Characters not allowed.
ERROR
at+csvm=1,"" // <number> must be with at least one digit.
ERROR

160 98-08901C39-B
 AT Commands

8.2.80 AT+MFS, Motorola Frequency of Search

AT Command Response/Action Remarks

AT+MFS = <freq>[,<mode>] OK <freq> Frequency of Search

+CME ERROR: <err> 0 Continous
1 Medium
AT+MFS? +MFS: <freq>,<mode> 2 Slow
OK 3 Fast
+CME ERROR: <err> <mode> Search mode
0 Automatic
AT+MFS=? +MFS:(list of supported <freq>s), (list
1 Manual
of supported <mode>s)
OK
+CME ERROR: <err>

This command will set or read the EEPROM Frequency of Search.

Note

Example
at+mfs=?
+MFS: (0-3),(0,1)

OK
at+mfs?
+MFS: 1,0

OK
at+mfs=3
OK
at+mfs?
+MFS: 3,0

OK
at+mfs=2,1
OK
at+mfs?
+MFS: 2,1

////////////////////// POWER CYCLE

at+mfs?

98-08901C39-B 161
AT Commands

+MFS: 2,1

OK
at+mfs=0
OK
at+mfs?
+MFS: 0,1

OK

8.2.81 AT+CSCB, Select Cell Broadcast Message Types

AT Command Response/Action Remarks

+CSCB=[<mode>[,<mids>[,<dcss>]]] If mode=0 and <mids> is not <mode>

specified or is an empty string, then
no channels are accepted, and the
g18 channel/mid list is cleared.
If mode=0 and <mids> is specified,
but <dcss> is not specified or is an
empty string, then accept all coding
formats.
If mode=1 and <mids> is not
specified or is an empty string, then
the g18 channel list will stay as is.
If mode=1 and <mids> is specified,
but <dcss> is not specified or is an
empty string, then accept all coding
formats.
OK
+CME ERROR: <err>
0 Message types specified in
<mids> and <dcss> are
accepted.
1 Message types specified in
<mids> and <dcss> are not
accepted.
<mids>
Message ID/Channel: 0–65354
String type: Default is an empty string
<dcss>
Data Coding Scheme: 0–255
String type: Default is an empty
string.

AT+CSCB? +CSCB: <mode>,<mids>,<dcss>

OK
+CME ERROR: <err>

AT+CSCB=? +CSCB: (list of supported <mode>s)

OK
+CME ERROR: <err>

162 98-08901C39-B
 AT Commands

+CSCB Parameters:
• The default value for missing <mode> is 0.
Note • A comma must be followed with a value.
• When using <dcs> GSM 3.38, only non compressed messages with default alphabet or UCS2 are transferred to
TCU, and 8-bit data support is required.
• No more than 16 channels will be submitted in <mids>.
• The string type lists <mids> and <dcss> may include only numbers (0–9), blanks, comma and minus (-)
characters.
• <mids> = 1–5 is equivalent to five channels.
• When <mode> is 0, and <mids> is a non empty list, the list will be added to the current g18 list, as long as the
accumulated g18 list does not exceed the maximum allowed.
• When <mode> is 1, and <mids> is a non empty list, items from the list will be deleted from the g18 list. An error
will not be issued if an item does not exist in the g18 list.
• The <dcss> list can include schemes that are not handled by g18, without error notification.
• AT+CSCB=0,"x,x","y,y"
When specifying a mid or a dcs several times in the same AT+CSCB request, the mid/dcs will be added the same
number of times to the g18 internal lists.
• AT+CSCB does not affect or represent SIM cell broadcast channel/language lists.
• The dcss specified refers to all incoming messages, and not only to mids specified in the same AT command.
For example, AT+CSCB=0,"1–5","1–7" followed by AT+CSCB=0,"6–10","8" will update the g18 mids list to
1–10, and the dcs list to 1–8. Any CB message that arrives with mid value of 1–10 and a dcs value between
1–8, will be accepted by g18.

98-08901C39-B 163
AT Commands

Cell Broadcast Support in g18:

• The g18 allows selection of the SMS service for cell broadcast. The AT command for selecting the service is:
Note • +CSMS=<service>
• +CSMS?
<service> 0 is allowed
• The g18 supports text and binary data coding schemes for cell broadcast messages.
• The number of concurrent cell broadcast channels from which the g18 forwards cell broadcast messages to the
DTE is not less than 21. (Five of the channels are user-defined lists through SIM and menu handling).
• The g18 NAD delivers multiple pages of a cell broadcast messages to the DTE. Each page is sent as an
individual message, even though the pages will be delivered in page number based sequence.
• AT+CNMA is not requested for cell broadcast.
• g18 is unable to save all pages being processed in its memory. g18 will send each page as it arrives. The
page could be a duplicate, or unorganized and multiplexed with other pages. TCU should reconstruct
messages and remove duplicates. These messages should be shown to the user only after a successful
build.
• The g18 supports up to 15 pages in a message.
• The g18 NAD does not store CBM messages in SIM or NVM.
• +CNMI's <bm> value is not converted to 0 by g18, unless requested to do so.
• Messages are sent to the TCU only when CNMI's <bm> value is 2, and either +CSCB's channel list is not
empty or SIM user's list is not empty.
• The following two entities may be required to handle or listen to cell broadcasts:
• DTE using AT+CSCB command
• User predefined SIM list, where the user controls the list using the handset menu.
These entities will be referred to later as requesters.

164 98-08901C39-B
 AT Commands

Incoming Cell Broadcast Messages:

In releases up to E6.11.23, the handset is set to receive accumulated messages. This means that if the message
Note exceeds one page then the message is not sent to the handset until the whole message is accumulated in a buffer.
The maximum number of accumulated pages is three, which means that sometimes only part of the intended
message is sent.
Using AT+CSCB, DTE is set to receive page-by-page messages, meaning that a message with several pages is
reported to DTE page by page.
There will be two behavior methods: One that keeps the previous release’s behavior (backward compatible), and
another for those who will use AT+CSCB.
• Previous version — SIM/handset is the sole requester (by default, after AT+CSCB=0 or any other sequence of
AT commands that leads to an empty g18 CSCB's mid list):
• CB control (on/off) is via Menu → Messages → Cell_Broadcast → On/Off
• mid control is via Menu → Cell Broadcast → Channel index
• dcs control is via Menu → Messages → Cell Broadcast → Languages
• Messages received accumulated.
• Maximum number of pages received in a message is three.
• Handset does not support 8-bit data and compressed data. Additional screening by data coding scheme is
done via the SIM language list.
• AT+CNMI=0,0,2 is required to transfer data to DTE.
• g18 mid list assigned by AT+CSCB is not empty:
• DTE gets all messages page by page (maximum of 15 pages per message). Messages are not sent to hand-
set.
• g18 tracks incoming cell broadcast messages. After receiving a CB message with a specific mid, g18 will not
receive CB messages with that same mid unless its update number is different. For example, CB mid = 1,
update = 1→ CB is accepted; CB mid = 1, update = 1 → the CB is not accepted; CB mid = 1, update = 2 →
CB is accepted; CB mid = 1, update = 1 → CB is accepted.
Example
Testing the modes supported:
at+cscb=?
+CSCB: (0,1)
OK

Reading the current mid and dcs lists:

at+cscb?
+CSCB: 0,“”,“”
OK

Adding channels 3, 4,5,6,22 to mid list and language 1 to dcs list:

at+cscb=0,“3-6,22”,“1”
OK

Removing channels 4 and 6 from channel list, and removing the default dcs(0) from the dcs list:
at+cscb=1,“4,6”,“”
OK

98-08901C39-B 165
AT Commands

Reading the current mid and dcs lists:

at+cscb?
+CSCB: 0,“3,5,22”,“1”
OK

Adding channel 4 to mid list, and language 2 to dcs list:

at+cscb=0,“4”,“2”
OK

Reading the current mid and dcs lists:

at+cscb?
+CSCB: 0,“3,5,22,4”,“1,2”
OK

Clearing both lists:

at+cscb=0
OK

8.2.82 AT+MCSAT, Motorola Control SMS Alert Tone

AT Command Response/Action Remarks

AT+MCSAT=<mode>[,<dcs mask>, Suppresses or removes suppressed <mode>

[…]] SMS alert tone for all arriving 0 Suppress alert tone
messages, or for some messages, as 1 Enable alert tone (default)
defined in <dcs mask>.
2 Exercise alert tone
OK
+CME ERROR: <err> <dcs mask>
SMS Data Coding Scheme mask,
which either suppresses or activates
AT+MCSAT? +MCSAT:
the alert tone.
<mode>, [<current dcs mask >,[..]]
OK
+CME ERROR: <err>

AT+MCSAT=? +MCSAT: (list of supported <mode>s)

OK
+CME ERROR: <err>

166 98-08901C39-B
 AT Commands

This command suppresses the SMS alert tone for a specific SMS type whenever the SMS alert tone is generated
(receiving, storing or sending SMS).

Note When the <dcs mask> parameter is omitted, the alert tone is suppressed for all SMS arrivals.
Up to ten <dcs mask> are allowed.
<dcs mask> format is an 8-bit information K7K6K5K4K3K2K1K0 parameter. Each Kn contains 0, 1, or X (ascii
character):
• 0: Condition is met if arrival SMS includes dcs with 0 in this position.
• 1: Condition is met if arrival SMS includes dcs with 1 in this position.
• x or X: This bit in an arrival dcs is ignored.
Example
On power up, the alert tone is not suppressed.
AT+MCSAT= 0 will suppress the alert tone for all SMS messages.
AT+MCSAT= 0, 11110111 will suppress the alert tone for dcs = $F7.
AT+MCSAT= 0, 00xx01xx,111101xx will suppress the alert tone for 8-bit data.
AT+MCSAT=1 will delete all suppressed conditions.
AT+MCSAT=2 will exercise the alert tone.

at+mcsat=?
+MCSAT: (0-2)

OK

at+mcsat?
+MCSAT: 1

OK

at+mcsat=2
OK

at+mcsat=1

OK

at+mcsat=0,00000001 // Disable SMS alert tone for DCS value 1.

OK

98-08901C39-B 167
AT Commands

8.2.83 AT+MECC, Motorola Extended Characters Check

AT Command Response/Action Remarks

AT+MECC =<mode> Enables or disables standard <mode> checking mode

checking of ASCII characters with 0 Disable standard checking, or
values less than 32 on parsing AT do not eliminate ASCII
commands. characters with values less
OK than 32.
+CME ERROR: <err> 1 Enable standard checking
(default).
AT+MECC? +MECC: <mode> Returns the supported modes.
OK
+CME ERROR: <err>

AT+MECC=? +MECC: (list of supported <mode>s)

OK
+CME ERROR: <err>

This command prevents the standard check of ASCII characters, and allows all characters to be entered in the
phone book, for example @. Indications that are affected by this command are: +CCWA, +CLCC, +CLIP.

Note

Example
at+mecc=?
+MECC: (0-1)

OK
at+mecc?
+MECC: 1

OK
at+cpbs=“me”
OK
at+cpbw=, “030303”, 129, “abc” // Cannot display and include the alpha tag “Ω” in the phone book entry.
OK
at+mecc=0
OK
at+cpbw=, “0303030”, 129, “abc” // The “Ω” character was added to the end of the string, but it cannot be seen in Windows
Hyper Terminal.
OK
at+cpbf=“ ”
+CPBF: 001, “030303”, 129, “abc”

168 98-08901C39-B
 AT Commands

+CPBF: 002, “0303030”, 129, “abc” // The “Ω” character can be seen on the handset display, but not in Windows Hyper
Terminal.
OK

8.2.84 AT+CSCR, SIM Card Reader

AT Command Response/Action Remarks

AT+CSCR +CME ERROR: <err> <sim_type>

1 External SIM card
AT+CSCR? +CSCR: <sim_type> 2 Internal SIM card
OK
+CME ERROR: <err>

AT+CSCR=? +CME ERROR: <err>

This command tells which SIM card reader is being used, either the internal one on the g18 board, or an external
card reader via the DSC bus.

Note

Example
at+cscr=?
ERROR
at+cscr?
+CSCR: 2 // Internal sim card.

8.2.85 AT+MCELL, Motorola Cell Description

AT Command Response/Action Remarks

+MCELL = <mode>, <screen_num> +MCELL: <screen_num> <mode>

<screen_info> 0 One shot requested
<screen_num>
OK
An integer number between 1-20
<screen_info>
+CME ERROR: <err>
Refer to Table 29, “External Screen
Information,” on page 170.
+MCELL? OK

+MCELL =? +MCELL: (000), (list of supported

<screen>s)

OK

+CME ERROR: <err>

98-08901C39-B 169
AT Commands

Table 29. External Screen Information

Item Description Screen

Main Cell Mobile Country Code. Screen 1,

mcc position 19-21

Main Cell Mobile Network Code. Screen 1,

mnc position 22-24

Main Cell Location Area Code. Screen 1,

lac position 58-62

Main Cell Base Station Identity Code. Screen 1,

bsic position 11-12

Main Cell Basic Control Channel. Screen 1,

BCCH Freq (absolute) position 6-9

Main Cell RxLev Signal strength of the cell being viewed. Screen 1,
position 13-16

Main Cell RxLev Full Signal strength of the beacon channel of Screen 1 in dedicate mode,
the serving cell. position 35-39

Main Cell RxLev Sub Signal strength of the active dedicated Screen 1 in dedicate mode,
channel. position 51-55

Main Cell RxQual Full Received signal quality in the base Screen 1 in dedicate mode,
channel (carrying the BCCH). position 41-42

Main Cell RxQual Sub Received signal quality in the dedicated Screen 1 in dedicate mode,
active channel. position 57-58

Neighbor Cell Base Station Identity Code. Screen *,

bsic position 11-12

Neighbor Cell Basic Control Channel. Screen *,

BCCH Freq position 6-9

Timing Advance Timing Advance quarter of bits. Screen 1 in dedicate mode,

position 45-49

* N1—N6 information concerning Neighbor Cell 1—6 appears on screens 5—10 respectively.
** When the information is not available, an * is displayed instead.

170 98-08901C39-B
 AT Commands

The information in screens 1–20 is for internal use, except for those listed in Table 29, above.
Set command can be used to retrieve the specific cell parameters.
Note Read command returns OK.
Test command returns the whole <mode> and <screen> options, supported by this command.
Example
1. To find MCC value:
+MCELL = 0,1
MCELL: 1 BC 0095 51-057B<LF>425001 39051 33<LF>047 047 *** ***<LF>0 A1aN 09800 20
<LF>7 *** 4 1 32 04<LF>-104 GPI1 ****

OK
MCC is at position 19-21: 425
2. To find Neighbor 5 (N5) BSIC value: (N5 appears at screen 9)
+MCELL = 0,9
+MCELL: 9 BC 0095 51-059B<LF>045 045 *** ***<LF>N5 0638 51-097B<LF>-01 -01 *** ***
<LF>-095C000 T00M30<LF>CA0 CQ0 GP1 RA

OK
N5 BSIC is at position 11-12: 51

8.2.86 AT+IPR, Setting and Saving the Baud Rate

AT Command Response/Action Remarks

AT+IPR = [<baud_rate>] OK <n> <baud_rate>

OR +CME ERROR: <err> 0 300
AT+IPR = [n] 1 600
2 1200
3 2400
AT+IPR? +IPR: <baud_rate> 4 4800
OK 5 9600
+CME ERROR: <err> 6 19200
7 38400
AT+IPR=? +IPR: (list of supported <n>s, 8 57600
<baud_rate>s) 9 Auto baud rate detection
OK
+CME ERROR: <err>

98-08901C39-B 171
AT Commands

For example, AT+IPR=8 is equivalent to AT+IPR=57600.

Using AT+IPR=<baud> with a <baud> value other than 9 will disable the auto baud rate detection feature. The
Note entered baud rate is stored in the unit and restored after power up.
The power up default baud rate is 9600, with enabled auto baud rate detection feature. If AT+IPR was not used or
its last use was AT+IPR=9, the baud rate at power up will be the default.
The baud rate can be switched to 4800, 9600, 19200, 38400 or 57600 using AT+IPR = <baud>. <baud> values are
4-8, 9 or 4800, 9600, 19200, 38400, 57600. Value represents 4800 to 57600. Value 9 represents auto baud rate
detection.
AT+IPR is similar to AT+CBAUD with the ability to save.

8.2.87 AT+PT42

AT Command Response/Action Remarks

AT+PT42 OK
+CME ERROR: <err>

AT+PT42? +CME ERROR: <err>

AT+PT42=? +CME ERROR: <err>

This command disables echo suppression and echo cancellation processing in normal mode until
the MS is turned off, which affects the handset screen. Registration starts when the command is
completed.
Note

8.2.88 AT+CMUX, Multiplexing Mode

AT Command Response/Action Remarks

AT+CMUX=0 OK When sending the command

or outside the Mux
+CME ERROR: “Operation not allowed” When sending the command from
the Mux

AT+CMUX? +CMUX:0,0,1,31,10,3,30,10,2,0,1,0,0 When sending the command from

or the Mux
+CME ERROR: “Operation not allowed” When sending the command
outside the Mux

AT+CMUX=? +MECC: (0)

172 98-08901C39-B
 9. g18 EVALUATION BOARD

9.1 GENERAL
The EV board is designed to be a tool used to operate the g18
and to provide an example of the different drivers/
connections available. It also provides an idea of how to
work with the g18 in different situations.
Two versions of the EV board have been released, Issue P4
and Issue P5. These boards have the same functionality,
however the Issue P5 board contains an additional D-sub
connector for GPS connectivity.
Additional information regarding the evaluation boards can
be found in “Schematic Diagrams, Layouts and Parts Lists”.
The EV boards can be used as a test tool for the
d10, d15 and g18. The g18 requires a retrofit kit
(FTN8105A) in order to make the LEDs operate
Note in 3V logic (d10/d15 operate in 5V logic).

9.2 EV BOARD ISSUE P4

To view the connectivity options, refer to Figures 44 and 45.
On Test Points
Board J114
SIM S1
LED EN
GPS Ant Power
GND Soft GSM
Hands Free TS IRDA
36 Pin ZIF 10 Indicator LEDs
Mute
Ex SIM Connector J120

GPS Select 28 Pin DIN

Connector
DB-9 RS-232 J5 Horizontal J126
IRDA EN Antenna Contact
28 Pin DIN
36 Pin ZIF J121 Connector
Vertical J125
30 Pin ZIF J4
GPS J127
ON/OFF Toggle
SMA Connector
SW2
J124
Headset
J118

Speaker
J111

30 Pin Ground
Microphone ZIF Board ON/OFF 12 Pin Butt Connector
J122 J12 S2 J13
Handset and
Vcc 3 to
Hands Free
6 Vdc
Circuits
Fuses 2.5 AMP 15 Pin Butt Connector RJ-45 (Handset)
12Vdc for Fast Blow J2 J1 J110 J115
HF only

Capacitor

98-08901C39-B 173
g18 Evaluation Board

Figure 44. EV Board P4 - Front

Ex Sim Connector
S1 On
Indicator LEDs Board Sim

DB-9 RS-232 J5
Antenna
Contact

36 Pin ZIF J229

SMA Connector
J124 Headset
J118
Speaker
J111
Microphone
J122

Fuses Vcc 3 to
12 Pin Butt Connector 2.5 AMP 6 Vdc
J13 Fast Blow
Audio Drivers
Ground
RJ-45 (Handset) 15 Pin Butt Connector
J110 J115 J1 J2
Board ON/OFF 12Vdc
S2 for HF only

Figure 45. EV Board P4 - Back

9.2.1 Connector Description J3 - Power Inputs:

J5 - RS232 Connector:
• This connector has eight RS232 lines (DTR, DSR, RTS,
CTS, TXD, RXD, DCD, RI).
• These lines are the RS232 lines from the g18 output,
converted to RS232 levels.
• The D-type connector can be used to drive the GPS TXD
and RXD lines.
• When the GPS_Select jumper is inserted, the TXD/RXD
lines from the GPS connector are driven to the RS232
connector instead of the d15 signals.
J4 - d10 Output: Flex connection to the host device.
J121 - d15/g18 Output: Flex connection to the host device.
SW2 - On/Off Button: Push button switch connected to the
d15/d10 On/Off line, used to turn the unit on and off.
J118 - Headset Connector: Used to connect a headset.
J111 - Speaker Connector: Used for hands-free
applications.
J122 - MIC Connector: Used for hands-free applications.
• 3V to 6Vdc for the g18 and audio drivers in the EV board.
• 12Vdc for the hands-free drivers.
S2 - Power Switch: Turns on the 3 - 6V to the EV board.
J1, J2, J13 - Butt Connectors: Used to connect standard
accessories (for example, EMMI, charger for power input,
and so on.)
J10, J115 - Handset Connectors: Used to connect the
handset and/or the remote SIM card reader.
J124 - Internal Antenna Connector: SMA connection for
antenna.
J120: Connection to the d15/g18 under test - 36 pin. This is
a mirror image connector to the g18.
J12: Connection to the d10 under test - 30 pin.
J125: d15 DIN Vertical connector for unit under
test - 28 pin.
Misalignment of the 28 pin DIN connector while
!
Caution
inserting it into the EV board or host device may
cause irreversible damage to the d15/g18.

174 98-08901C39-B
 g18 Evaluation Board

J126: d15/g18 DIN horizontal connector for unit under test J114: Test points of the main functions from the d15 user
- 28 pin. connector.
S1: SIM connector. Table 31. J114 Functions

Pin Description Pin Function

1 Gnd
2 SIM_PD 1 CTS
3 SIM_CLK
2 TXD
4 *SIM_RST
5 SIM VCC 3 DCD
6 SIM_I_O
7 SIM VPP 4 DSR
8 Gnd
5 RXD
Figure 46. SIM Card Interface
6 RTS

SIM: Additional SIM connectors for extended SIM sockets. 7 SIM I_O

Table 30. SIM Card Pin Functions 8 DTR

Pin Function 9 SIM_PD

1 SIMPD 10 SIM VCC

2 SIM VCC 11 RI

3 *SIM_RST 12 SIM CLK

4 DGND 13 DCS_EN

5 N.C. 14 DSC Downlink

6 DGND 15 DSC Uplink

7 SIMCLK 16 2.7V for Audio Circuits

8 DGND

9.2.2 Jumper Description

9 N.C.
TS Used to turn on the unit whenever power is
10 N.C.
supplied.
Led EN Enables the LED operation.
J127: GPS connector for Motorola M12 GPS module.
GND Ground pins.
IrDA Future option, which is not currently
available.
Mute Test point used for hands-free operations,
which is an input to mute the audio.

98-08901C39-B 175
g18 Evaluation Board

SoftGsm When the jumper is connected to the d15, it HF: Jumper not in use. HF selection must be
switches to SoftGsm mode. In the g18, this performed using the software.
jumper should be always open.
GPS select Future option, which will connect the GPS to
GPS ant Pwr: Future option, which will connect the power the RS232 output.
to a GPS mounted in the EV board.

9.3 EV BOARD ISSUE P5

To view the connectivity options, refer to Figures 47 and 48, below.
DipSwitch P6
S3

P10 On
Board Test Points 36 Pin ZIF 10 Indicator LEDs
DB 9 GPS J9 SIM S1 P11 J128

28 Pin DIN
DB-9 RS-232 J5 Connector
Horizontal J126
Antenna Contact
Ex SIM Connector 28 Pin DIN
Connector
36 Pin ZIF J129 Vertical J125
30 Pin ZIF J4 GPS J9
ON/OFF Toggle SMA Connector
SW2 J124
Headset
J118
Speaker
J111

Ground
Microphone 30 Pin Board ON/OFF 12 Pin Butt Connector
Vcc 3 to
J122 ZIF S2 J13
6 Vdc
J12
12Vdc for
Handset and HF only Fuses 2.5 AMP 15 Pin Butt Connector RJ-45 (Handset)
Hands Free Capacitor Fast Blow J2 J1 J110 J115
Circuits

Figure 47. EV Board P5 - Front

176 98-08901C39-B
 g18 Evaluation Board

S1On DB 9 GPS J9
Indicator LEDs Board
SIM

DB-9 RS-232 J5
Antenna
Contact

36 Pin ZIF J229

SMA Connector
J124 Headset
J118
Speaker
J111
Microphone
J122

Fuses 2.5 AMP 12Vdc

Fast Blow for HF only
12 Pin Butt Connector
J13 Vcc 3 to Audio Drivers
Board ON/OFF 6 Vdc
RJ-45 (Handset) S2
J110 J115 15 Pin Butt Connector Ground
J1 J2

Figure 48. EV Board P5 - Back

9.3.1 Connector Description J122 - MIC Connector: Used for hands-free applications.
J3 - Power Inputs:
J5 - RS232 Connector:
• 6Vdc for the g18 and audio drivers in the EV board.
• This connector has eight RS232 lines (DTR, DSR, RTS,
• 12Vdc for the hands-free drivers.
CTS, TXD, RXD, DCD, RI).
• These lines are the RS232 lines from the g18 output, S2 - Power Switch: Turns on the 3 - 6V to the EV board.
converted to RS232 levels.
J1, J2, J13 – Butt Connectors: Used to connect standard
J9 - GPS Connector for Debugging: accessories (for example, EMMI, charger for power input,
and so on.)
• This connector has the GPS TXD and RXD lines in
RS232 levels. J10, J115 – Handset Connectors: Used to connect the
• GPS 1pps and RTCM lines are routed directly to the g18 handset and/or remote SIM card reader.
user connector. J124 – Internal Antenna Connector: SMA connector for
an antenna.
J4 - d15/g18 Output: Connection to the host device.
J128: Connection to the g18 under test - 36 pin. This is a
J129 - g18 Output: Connection to the host device. mirror image connector to the g18.
SW2 - On/Off Button: Push button switch connected to the J12: Connection to the d15/g18 under test - 30 pin.
g18/d15 On/Off line, used to turn the unit on and off.
J125: g18 DIN Vertical connector under test - 28 pin.
J118 - Headset Connector: Used to connect a headset.
J126: g18 DIN horizontal connector under test - 28 pin.
J111 Speaker Connector: Used for hands-free
applications. S1: SIM connector. See Figure 46 for connector details.

98-08901C39-B 177
g18 Evaluation Board

SIM: Additional SIM connectors for extended SIM sockets. Table 33. P11 Functions (Continued)

Table 32. SIM Card Pin Functions Pin Function

Pin Function 4 DSR

1 SIMPD 5 RXD (Output from g18)

2 SIM VCC 6 RTS

3 *SIM_RST 7 SIM I_O

4 DGND 8 DTR

5 N.C. 9 SIM_PD

6 DGND 10 SIM VCC

7 SIM_CLK 11 RI

8 DGND 12 SIM CLK

9 N.C. 13 DCS_EN

10 N.C. 14 DSC Downlink

J127: GPS connector for Motorola M12 GPS module. 15 DSC Uplink

P6 GND: Ground pins.

16 2.7V for audio circuits
P10 GPS ant Pwr: Future option, which will connect power
to a GPS mounted in the EV board. 17 GPS - RTCM
P11: Test points of main functions from the g18 user
18 GPS 1PPS
connector.

Table 33. P11 Functions 19 TX_EN

Pin Function 20 HF Mute input (for customer application)

1 CTS 21 GPS TXD (output from g18)

2 TXD (input to g18) 22 GPS RXD (input to g18)

3 DCD

178 98-08901C39-B
 g18 Evaluation Board

9.3.2 S3 Dip Switch Description
Figure 49. Dip Switch Description
S3-1 TX_EN: Used to open the audio channel for the HF
when a call is active, and mute it if there is
no active call. When S3-1 is open, the HF
audio channel is always active.
S3-2 Led EN: Enables the LED operation.
S3-3 SoftGsm: When the dip switch is closed, the d15
switches to SoftGsm mode. In the g18, this
dip switch should always be open.
S3-4 TS: Used to turn on the unit whenever power is
supplied.

98-08901C39-B 179
g18 Evaluation Board

180 98-08901C39-B
 10. g18 PC LOADER APPLICATION

10.1 GENERAL
The g18 PC Loader Application is a tool that downloads new 10.2 APPLICATION OPTIONS
program codes into g18 via RS232.
Configuration Requirements:
10.2.1 Setting
• PC with 16 MB of RAM, available serial port supporting
TX, RX, RTS, CTS, and Windows 2000 or NT. The Setting tab, shown below, enables you to specify the
• g18 software version E6.02.10 and above. application parameters that are used in the programming
• g18 connected to the PC communication port either procedure.
through the EV board or through the external
communication port on the host device.
Contact GSM Support at
BSH015@email.mot.com, or your account
manager for the CP software and PC Loader
Note application and specify the required language
pack as all CP software and PC Loader files are
provided in one zipped file.

Figure 50. Setting Page

The PCLoader.exe application must be run from the

directory in which it is installed.
The following parameters are available in the Setting tab:
Serial Port Settings
Serial Port The name of the communication
port to which the g18 is connected.

98-08901C39-B 181
g18 PC Loader Application

Baud Rate The active baud rate of the interface The specified port name must be between
between the g18 and the PC on COM1 – COM9.
RS232. This is used as the initial The Baud Rate value can be 9600, 19200,
Note
handshake between them. 38400, 57600 or 115200.
Maximal Baud Rate The maximum baud rate value that Set default Sets the default application parameters
will be used after the initial specified in the Setting tab.
handshake is completed. The PC
should support this baud rate. If
RS232 is being bridged to the g18
through the host device, the
maximum setting must reflect the
host device UART/bridge
capability.
Programming Status Report
Writing to File When checked, saves the PC Loader
Application progress status.
File Name The name of the Status Report file.
Browse Opens the standard Windows
Browse for Folder dialog box,
which enables you to browse to the
location of a required file.
Apply Checks the parameters specified in the Serial Port
Settings area, writes them into the Windows
registry and tries to open the communication port.

Figure 52. Set Default Pop-up Approval Message

Figure 51. Applying Pop-up Approval Message

182 98-08901C39-B
 g18 PC Loader Application

10.2.2 Programming The following parameters are available in the Programming

tab:
10.2.2.1 Warnings and Rules g18 Image File
Before pressing Start in the Programming tab, the user must Browse Enables you to set the input flash.hex file by
check that the following conditions have been met: opening the standard Windows Browse for
• The g18 is connected to the PC serial port. Folder dialog box. From there you can browse
• The g18 is powered on. to the location of the required file. Browse to
g18 flash, hex file, or enter the name of the file
• The g18 baud rate is the same as set in the Setting tab. in the File field.
The PC Loader application must not be interrupted while it
is flashing the g18. Any interrupt such as, disconnecting the Start Initiates the flashing/program download to
g18, powering off the g18, or powering off the PC, will g18.
damage the g18. Test Tests the current g18 version and baud rate.
During the programming process, the application retrieves
data from the flash.hex file (image file) and transfers it to the
g18.
The Programming tab, shown below, enables you to specify
the image file from which data is retrieved and downloaded
to the g18.

Figure 54. Image File Selection via Browse Button

Test can also be used to ensure that all the

pre-start conditions specified in the following
Warning and Rules section are met. In the
Note Setting tab, the Baud Rate will be set as the
active baud rate.

Figure 53. Programming Page

98-08901C39-B 183
g18 PC Loader Application

After activating the test, a Test Report log is displayed, as
shown in the example below.
The sequence of the operations during the programming
process is as follows:
1. Loads the image file and checks its validity.
2. Checks that the g18 is connected to the PC.
3. Sends the code from the image file to the g18.
By pressing Test after the g18 is programmed,
the user can check the software version in the
connected g18 to verify that it has been
Note programmed correctly. A message is displayed
prompting the user to ensure that the g18 is
powered on before pressing Test.

Figure 55. Testing Report Log Activated via Test Button

The following information is displayed:

Complete Displays the programming
progress graphically.
Programming Status Report This is a text message
window. When Start is
pressed, all the actions
performed by the
application are displayed in
this window. Error Figure 56. Start Programming Pop-up Approval Message
messages appear in the
window in red.

184 98-08901C39-B
 g18 PC Loader Application

The programming process can be performed in two stages,
depending on the g18 version installed in the computer. If
the prior g18 version is installed on the computer, the
following message is displayed prompting the user to power
on the g18 after the first stage is completed.
During the programming process, the user can view the
current programming phase in the program log. ,
The user cannot stop the programming process
after it has been started.
Note

Figure 57. Programming Message in Earlier g18 Versions

Figure 58. Programming Log in Programming Status

Report

98-08901C39-B 185
g18 PC Loader Application

When the programming process is completed, the following

message is displayed. Click OK to close the message
window.

Figure 59. Programming Complete Message

186 98-08901C39-B
 11. SPECIFICATIONS

A.1 GENERAL

Figure 62. DIN Version

Figure 60. Slim Version

Figure 61. Slim with GPS Version

98-08901C39-B 187
Specifications

A.2 MODEL SPECIFICATIONS

Physical
Form factor: PCMCIA type III, no PCMCIA connector, for Slim with GPS model
Size: g18 (GPRS) DV Slim: 44.29 x 88.45x10.4 mm
g18 (GPRS) DVG with GPS: 44.54 x 88.45 x 17.6 mm
g18 (GPRS) DV DIN: 40 x 80.2 x 7.5 mm
Mounting: Four 2.43mm Ø holes provided on non-DIN models
Weight: g18 (GPRS) DV Slim: 35.5 g
g18 (GPRS) DVG with GPS: 49 g
g18 (GPRS) DV DIN: 22 g
Volume: g18 (GPRS) DV Slim: 36.8 cc
g18 (GPRS) DVG with GPS: 57.0 cc
g18 (GPRS) DV DIN: 24.1 cc
Housing material: Plastic housing PC/ABS
Interface connector: g18 (GPRS) DV Slim/DVG: 36 pin ZIF socket @ 0.5 mm pitch
ELCO #04-6240-036-800
g18 (GPRS) DV Horizontal Board 28 pin dual in-line pin socket @1.27 pitch
only: (SAMTEC # CLP-114-02-L-D)
RF output connector: MMCX Jack (female) 50Ω GSM and GPS mating connector plug (male)
Coax Huber-Shuhner Johnson Components
RG178 11-MMCX-50-1-1 135-3302-001
RG316 11-MMCX-50-2-3 135-3403-001
Environmental
Operational temperature: -30 to +60° C
Storage temperature: -40 to +85° C
Shock: 20 g’s with 11 millisecond duration
20 impacts in three mutually perpendicular planes
Vibration: IS-19: 1.5g acceleration
5 to 500 Hz @ 0.1 octave/minute in three mutually perpendicular planes
Performance
Operating systems GSM: 900 MHz
DCS: 1800 MHz
PCS: 1900 MHz
Voltage:1 3.0 to 6V measured at the I/O connector during the transmit slot (576µs out of 4.6ms)
Current: =7.2 +/- 0.5 mA @ DRX 2 standby (sleep)
=3.5 +/- 0.5 mA @ DRX 9 standby (sleep)
< 150uA off current
300mA avg. in call at power level 5 (max. 350 mA)
1.2 A peak @ 217 Hz at power level 5 (max. 1.8 A)
Power out: GSM – Power levels #19 to 5, 5 dBm to 33 dBm per ETSI
DCS – Power levels # 15 to 0, 0 dBm to 30 dBm per ETSI
PCS – Power levels # 15 to 0, 0 dBm to 30 dBm per ETSI
SIM card reader:2 Options: 1. Internal - SIM CR 3/5V SIM
2. External - Local interface 3/5 SIM
3. External - Remote interface (DSC interface) 5V only

188 98-08901C39-B
 Specifications

Interface options: 9 line RS232 Serial Asynchronous full flow control, 3V logic level (DCE flow direction).
Vih 2.0 V min, 5.5 V max
Vil 0.8 V max
Voh 2.5 V min @100 uA
Vol 0.2 V max @ 100 uA
Wizard application for running on a PC for running IP over a PPP application.
Motorola Proprietary DSC Bus
GPS interface (TxD, RxD, 1PPS, RTCM, Antenna Voltage), on Slim GPS model.
Host protocol: CSD mode: AT commands including GSM 07.07, GSM 07. 05
(Appendix H, “AT Commands,” for specific AT commands
that are supported).
GPRS mode: AT commands as per standard for GSM 07.60 and 07.07
ver 7.5.0. (Appendix H, “AT Commands,” for specific AT
commands that are supported.)
Data: RS232: RS232 port up to 57.6 kbps. The default is set at 9.6 kbps
with auto-baud detection active up to 19.2 kbps. For rates
above 19.2 kbps, the baud rate can be set by the AT
command up to 57.6 kbps, which needs to be reset after
each power cycle.
CSD mode: Over the air rate depending on network, 9.6 kbps max
Circuit Switched Data.
Note: The g18 does not support non-transparent CSD with
speed less than 4800 bps.
GPRS mode: Over the air data rate depends on coding schemes
(CS1-CS4).
GPRS packet data (SMG31) Class B (only when a handset
is used), multi slot class 1, 2 and 4, 1X (uplink)/1X
(downlink) or 1X (uplink)/2X (downlink) or 1X (uplink)/3X
(downlink) coding schemes CS1 to CS4.
PC FAX: Class 1 using Winfax, alternates between fax and voice (TS61).
SMS: Send and receive (PDU and block mode per GSM 07.05).
Voice call: Supported I/O with external H/SET.
Audio: Analog - Full duplex I/O on interface connector.
Digital - Motorola proprietary DSC bus.
Echo cancelling activated by AT or IP for hands-free audio applications.
GPS: Independent GPS receiver on GPS model only.
GPS (TXD, RXD, 1PPS, RTCM, antenna voltage) functions are available on the ZIF and DIN
header/socket connector at 3V logic levels.
12 parallel channels
L1 1574,42 MHz
Code plus carrier tracking (carrier aided tracking)
Positional accuracy: 100 meters 2dRMS with SA as per DoD specifications, less than 25 meters
SEP without SA.
Additional specifications are available on request.

1 It is recommended that a 1000 uF capacitor be placed across the GND and VCC as close as possible to the flex cable on versions with a housing or
the 28-way connector on the DIN version. This will prevent a Vcc drop during peak current, which has a 543 ms duration every 4.3 ms due to
GSM power pulses. Voltage must not drop below 3.0 vdc to prevent degradation of module performance.
2 One SIM card can be used with option 1 and 2. With option 3, two SIM cards can be in the system. When connecting the remote card reader to
evaluation board, use the handset connector.

98-08901C39-B 189
Specifications

A.3 PIN DESCRIPTIONS 2 Data received by g18 (DCE flow).

3 Data sent from g18 (DCE flow).
Table 34. Interface Connector, 36 Pin Description Stan-
4 GPRS PDP context active – DCD line will be active (low). GPRS
dard, Slim, Slim with GPS and DIN Horizontal PDP context not active – DCD line will be inactive (high).
Pin # Function 5 The Audio Out line is used to send out the detected audio and as a
1 TX Enable toggle On/Off pin.

2 RXD UART 2 (GPS RXD on GPS models)1 6 The wake up line is bi-directional. When going from non-GPRS
coverage to GPRS coverage, a negative pulse will be generated on
3 TXD UART 2 (GPS TXD on GPS models)1 this line. When the g18 sends data to the DTE (host), a negative
4 RS232 – TXD2 pulse will be generated on this line. When the DTE (host) sends
data (while the g18 is in sleep mode), it sends a wake up command
5 RS232 – RXD3 to the g18.
6 RS232 – DTR
7 Logic high turns the unit on, logic low places the unit into standby
7 RS232 – DCD for CSD call/PDP context mode. The unit must be turned on before it is placed in standby
indicator in GPRS4 mode. An alternate way to power on the radio is by using the On/
Off pin.
8 RS232 – RTS
9 RS232 – CTS
.
10 RS232 – DSR
11 RS232 – RI Table 35. Interface Connector, 28 Pin Description DIN
12 Man test Models
13 Analog Audio In Pin # Function
14 Analog Audio Out and Power On/Off5 1 Vcc (3.0 – 6) Vdc
15 Wake up/GPRS coverage indicator6 2 Vcc (3.0 – 6)Vdc
16 SIM CR DET 3 SIM CR I/O Data
17 SIM CR Vcc (3/5Vdc) 4 SIM CR Reset (RST)
18 SIM CR Reset (RST) 5 SIM CR Vcc (3/5Vdc)
19 SIM CR I/O Data 6 SIM CR DET
20 SIM CR Clock 7 RS232 – DTR
21 TS (Turn on/stand by)7 8 TS (Turn on/stand by)1
22 DSC - Enable 9 Man test
23 DSC - Downlink 10 Wake up/GPRS coverage indicator2
24 DSC - Uplink 11 GND
25 Analog Audio GND 12 GND
26 GND 13 RS232 – RI
27 GND 14 RS232 – DCD for CSD call/PDP context
28 GND indicator in GPRS3
29 GND 15 TXD UART 2
30 Vcc (3.0 – 6 Vdc) 16 RXD UART 2
31 Vcc (3.0 – 6 Vdc) 17 Analog audio GND
32 Vcc (3.0 – 6 Vdc) 18 Analog audio out and power on/off
33 Vcc (3.0 – 6 Vdc) 19 Analog audio in
1 20 DSC - Enable
34 GPS Ant. PWR (3/5 Vdc)
35 RX for differential GPS RTCM1 21 RS232 - DSR
36 GPS 1 pps1 22 DSC - Downlink
23 DSC - Uplink
1 Functionality for these pins is provided only on units with GPS. For
more information on wake-up line functionality, refer to Section 24 SIM CR Clock
3.2.3, “How/When to Wake Up the Unit”. 25 RS232 – TXD4

190 98-08901C39-B
 Specifications

Table 35. Interface Connector, 28 Pin Description DIN Table 36. Standard, Slim, Slim with GPS and DIN
Models (Continued) Horizontal Model Functions Available on 36 Pin ZIF
(Continued)
Pin # Function
26 RS232 - RXD5 GPS (GPS option TXD & RXD in 3V levels, 1PPS,
27 RS232 - CTS only) RTCM, Antenna power. RXD
and TXD lines are at 3V levels.
28 RS232 - RTS
The GPS receiver is the
1 Logic high turns the unit on, logic low places the unit into standby Motorola M12.
mode. The unit must be turned on before it is placed in standby
mode. An alternate way to power on the radio is by using the On/
Off pin.
2 The wake up line is bi-directional. When going from non-GPRS Table 37. DIN and Horizontal Model Functions Available
coverage to GPRS coverage, a negative pulse will be generated on on 28 Pin ZIF
this line. When the g18 sends data to the DTE (host), a negative
pulse will be generated on this line. When the DTE (host) sends
data (while the g18 is in sleep mode), it sends a wake up command VCC Input 3.0 to 6Vdc.
to the g18.
Full RS232 - 9 TXD, RXD, RTS,CTS, DSR, DTR,
3 GPRS PDP context active – DCD line will be active (low). GPRS
PDP context not active – DCD line will be inactive (high). Pins DCD RI at 3V levels.

4 Data received by g18 (DCE flow).

External SIM SIM Clock, SIM reset, SIM I/O,
5 Data sent from g18 (DCE flow). Connections SIM VCC,SIM PD.

Table 36. Standard, Slim, Slim with GPS and DIN DSC BUS DSC_EN, Downlink, Uplink
Horizontal Model Functions Available on 36 Pin ZIF Motorola proprietary BUS

Audio In/Out Audio Out and On/Off in the same

pin.
VCC input 3.0 to 6Vdc.
Audio In signal and analog ground.

Full RS232 - 9 pins TXD, RXD, RTS, CTS, DSR,

Man_Test Line Used to detect standard Motorola
DTR, DCD RI at 3V levels.
accessories.

External SIM SIM Clock, SIM reset, SIM I/O,

TS Line Used to turn on the radio when Vcc
Connections SIM VCC, SIM PD.
(mobport) is applied.

DSC BUS DSC_EN, Downlink, Uplink

TX_EN Line Not available in DIN connectors.
Motorola proprietary BUS.

Audio In/Out Audio Out and On/Off in the

same pin. A.4 SLIM CONNECTIVITY OPTIONS
Audio In signal and analog
ground.

Man_Test Line Used to detect standard

Motorola accessories.

TS line (mobport) Used to turn on the radio when

Vcc is applied.

TX_EN Line This line indicates when the

radio is transmitting - Open
Drain.

Figure 63. Data and Voice (Slim) - Connections

98-08901C39-B 191
Specifications

A.5 SLIM AND GPS CONNECTIVITY A.6 DIN CONNECTIVITY OPTIONS

OPTIONS

Figure 64. Data and Voice and GPS Model Connections Figure 65. Data and Voice in DIN Configuration
Connections

A.7 MECHANICAL SPECIFICATION DIAGRAMS

Figure 66. g18 DV Slim

192 98-08901C39-B
 Specifications

Figure 67. g18 DV Slim with GPS

98-08901C39-B 193
Specifications

80.20
2.50 15.20
ø 4.000
2.97
ø 2.00 HOLE

40.00 35.00 40.50

2 28
11.24
1 27 9.69 MIN
6.09 65.50
23.77 5.00
3.70
7.97

2.80
Figure 68. g18 DV DIN Horizontal

A.8 LANGUAGE SUPPORT

Language Pack Language 01 Language 03 Language 06 Language 07 Language 08 Language 08

Description Western Europe GSM 1900 NA Nordic East Europe Mid East Mid East Arabic

g18 DV slim SE2836xF5Z8 SE2836xF5Z6 SE2836xF5Y5 SE2836xF5Y6 SE2836xF5Z5 SE2841xF5Z5

g18 DV slim w/GPS SE2837xF5Z8 SE2837xF5Z6 SE2837xF5Y5 SE2837xF5Y6 SE2837xF5Z5 SE2842xF5Z5

g18 DV DIN Horz SE2838xF5Z8 SE2838xF5Z6 SE2838xF5Y5 SE2838xF5Y6 SE2838xF5Z5 SE2843xF5Z5

Languages

Arabic X X

Bulgarian X

Chinese-Complex

194 98-08901C39-B
 Specifications

Language Pack Language 01 Language 03 Language 06 Language 07 Language 08 Language 08

Description Western Europe GSM 1900 NA Nordic East Europe Mid East Mid East Arabic

Chinese-Simplified

Croatian X

Czech X

Danish X X

Dutch X X X

English X X X X X

English-American X

Estonian X

Finnish X X

French X X X

French-Canadian X

German X X X X X

Greek X X X

Hebrew X X

Hungarian X

Indonesian-Bahasa

Italian X X X X

Latvian X

Lithuanian X

Norwegian X X

Polish X

Portuguese X X

Romanian X

Russian X X X

Serbian X

Slovak X

98-08901C39-B 195
Specifications

Language Pack Language 01 Language 03 Language 06 Language 07 Language 08 Language 08

Description Western Europe GSM 1900 NA Nordic East Europe Mid East Mid East Arabic

Slovenian X

Spanish X

Spanish-American X

Swedish X X

Thai

Turkish X X X

Ukrainian X

Vietnamese with
tonal marks

196 98-08901C39-B
 B. QUICK START

B.1 POWER CONNECTIONS B.5 SIM CONNECTIONS

Basic operation requires a single power supply of 3 to 6 V
connected to the EV board J3 connector.
When an external speaker and microphone are used
(hands-free operation), an additional 12V power supply is
needed.
Use switch S2 to power the EV board.
The SIM can be connected in one of four ways:
• Internally in the g18.
• In the SIM socket using the EV board S1 connector.
• Externally, using the connector marked SIM.
• The remote SIM can be connected using the DSC bus (in
the handset).

B.2 g18 CONNECTIONS B.6 BAND SELECTIONS

For all models with a 36 pin ZIF socket, connect the g18 via
a 36 pin FC to connector J120.
For the g18 in DIN Horizontal, connect the g18 to the EV
board using connector J126 or by using a flex cable between
the 36 pin ZIF socket and connector J120.
For the g18 in DIN Horizontal, connect the g18 to the EV
board using connector J125.
Pinout of J120/J128 is a mirror image of the ZIF
in the g18.
Note
The default setting of the g18 is 900/1800 MHz band (GSM/
DCS).
For PCS operation, you need to change the band using one
of the following options:
• Using the handset: Select Menu/Network/Change Band
and select 1900 Band.
• Using AT commands: Send AT+CBAND=3
(for GSM/DCS=4).
The g18 must undergo a power cycle for the
band change to take effect.

Note

B.3 CUSTOMER CONNECTIONS

For computer evaluations, connect to a 9-pin D-sub
connector J5.
For a customer application, connect the host device to
connector J121 using a flex cable.
B.4 AUDIO CONNECTIONS
Headset - Connect to J118 (labelled HEAD SET).
For hands-free:
Microphone - Connect to J122 (labelled MIC).
Speaker phone - Connect to J111 (labelled SPKR).
Handset - Connect to J10 or J115 (both in parallel).
B.7 RS232 CONNECTIONS
The g18 is a DCE device. Connect the RS232 lines
according to the host device type.
For more details regarding DCE or DTE, refer to “Data
Levels” on page 21.
B.8 ANTENNA CONNECTIONS
When a long 90° MMCX connector is necessary, you can
purchase it through Conectec. For more information, refer to
“Vendor Contacts” on page 64.

98-08901C39-B 197
Quick Start

B.9 DEFAULT DIP SWITCH/JUMPER

SETTINGS
In EV_P4
TS Open
Led EN Closed
GND Open (Test point)
IrDA Open (Not used)
Mute Open
SoftGsm Open
GPS ant Pwr 3V
HF Open
GPS select Open
In EV_P5
S3-1 Open
S3-2 Closed
S3-3 Open
S3-4 Open
The SoftGsm function must be disabled in order
to communicate using RS232. (In EV_P4, the
SoftGsm jumper is open. In EV_P5, the S3-3
Note dip switch is open.)

198 98-08901C39-B

C.1 GENERAL
When wireless data radio technology is integrated into
computing and telemetry devices, hardware issues related to
RF emissions must be considered. For example, the
technical aspects of enabling a wireless RF device as an
integrated peripheral in a host device, such as RF
performance and inter-operability with the host must be
addressed. Specifically, this chapter describes the following:
• The term desense
• Preferred test procedures
• Acceptable levels of electromagnetic interference (EMI)
• Approaches to solving desense problems
• Pertinent radio and antenna issues
If desense is detected, one or more of the following actions
can be performed:
• Connect the antenna cable shield to the main ground (PS
ground).
• Shield the logic section in the user application. (Most of
the radiation comes from clocks and data lines around the
logic section due to the high rise/fall time of the pulses.)
• A Ferrite can be wrapped around the antenna cable.
Recommended ferrite: Fair Rate # 2643023002 or #
0431173951.
This chapter considers, but does not attempt to
resolve, these technical issues since they are
beyond the scope of this guide.
Note
C.2 DESENSE DEFINED
Receiver desensitization occurs when an unwanted signal is
present at the radio receive frequency. The signal is usually
the result of harmonic energy emanating from a high
frequency, non-sinusoidal source. This noise desensitizes or
lowers the sensitivity threshold of the receiver.
The radio cannot differentiate between wanted and
unwanted signals. In frequency modulated systems, the
radio receiver can capture the strongest signal present. If
wanted and unwanted signals are present and there is not a
98-08901C39-B
C. DESENSE
significant difference in level, the unwanted signal can
overtake the receiver, effectively blocking the wanted signal
(see Figure 58).
Consistent and reliable reception occurs when a safety
margin dictated by co-channel rejection is maintained. For
example, if the co-channel rejection is 10 dB, all unwanted
signals must be 10 dB below the receiver’s sensitivity level.
Some modems and networks have different rejection levels.
Use the rejection level appropriate for your modem. This
means an interference signal that is more than 10 dB below
the wanted signal has little impact on the data receiver’s data
recovery. Any interfering source above this level creates
desense, reducing the radio’s sensitivity for data reception.
For each dB above the threshold level, one dB of desense is
created.
Figure 58. Wanted and Unwanted Signal Levels
C.2.1 Noise Sources
CPU clocks, address and data buses, LCD refresh, switching
power supplies, and peripheral drivers are the primary
contributors of EMI (see Figure 59). The frequency of these
emissions is often unstable. One reason for this instability is
that high stability clock sources are not a requirement in host
computer designs.
The frequency of sources move as a function of temperature,
time, and aging. Other sources by nature move within the
frequency spectrum as a function of time. The edges of clock
signals create detectable harmonics well into the 1 GHz
199
Desense

band. This presents a challenge in measuring the effects of
the emission, since one must first determine where the
emission exists in the frequency spectrum.
Noise from the host can conduct through the electrical/
mechanical interface or radiate electromagnetic fields that
are received by the modem antenna and impact the modem.
Motorola modems are specifically designed to minimize
conducted noise.
Radiated electromagnetic fields emanating from the internal
circuitry are incident on the modem antenna. These fields are
then converted to noise power by the antenna and are
incident on the receiver. The physical interface signaling
connection has less impact on the receiver performance and
can be electrically decoupled using passive components.
assumptions have to be made to extrapolate the results and
convert them to desense figures. Of course, these
assumptions can create a certain level of error in the
prediction.
C.3.1 Packet Modem Integration Tester
(PMIT)
PMIT for the g18 module is not yet available.
The following section provides an overview
only.
Note
To enable non-intrusive, labor-saving testing of desense, a
PMIT session measures and records the sensitivity of every
channel in the receive band. PMIT produces an RF level
versus channel frequency data set that helps determine
system coverage. Figure 60 illustrates the PMIT hardware
facility. For more information on testing using PMIT,
consult your Motorola OEM representative for details.
Special conditions apply to receipt and usage of the utility.

Figure 59. EMI in a Portable Computer Platform

C.2.2 Receiver Susceptibilities

The receiver is susceptible to being desensed within the
channel bandwidth and at intermediate frequencies used for
down conversion. Consult the particular receiver
specifications for IF frequencies. Excessive noise on power
supply pins can also create sensitivity problems.
C.3 MEASUREMENT TECHNIQUES
Figure 60. PMIT Hardware Facility
C.3.1.1 PMIT Data Presentation
PMIT produces two columns of data that can be ported to
any two-axis linear plotting program. A typical PMIT plot is
shown in Figure 61. The plot provides the RF level required
to produce 1% BER at any channel within the test range.

Desense can be measured in one of the following ways:

• Indirectly, by recording the emission level from the host
and then calculating the effect on the modem.
• Directly, by using packet error rate testing off air.
Direct testing is the preferred method since it is more of a
system test.
The test must be non-intrusive. Peripheral test cables or
apparatus must not be connected to the unit under test, since
they can have a significant effect on the receiver sensitivity
results.
Indirect testing is essentially the FCC Part 15 EMI testing
that is currently being performed. Bear in mind that some Figure 61. Typical PMIT Plot

200 98-08901C39-B

C.3.2 Alternate Measurement Method
Using a spectrum analyzer with input impedance of 50 W,
connect the antenna of the product under test to the analyzer,
as shown in Figure 62. If an antenna is currently not
developed, use a portable dipole antenna as a measurement
antenna.
The measurement apparatus is capable of measuring signals
as low as –120 dBm. A preamplifier is required to allow the
spectrum analyzer to achieve these levels. Use the analyzer’s
smallest possible bandwidth resolution, typically 1 kHz, to
improve the dynamic range of the measurement.
If the input impedance of the analyzer is the same as that of
the radio receiver and the antenna, you can measure the noise
to which the receiver will be subjected. The gain on the low
noise amplifier (LNA) will make low level noise more
visible. Ensure that the spectrum analyzer’s input is not
overridden by other RF signals, such as FM radio stations.
Any spikes that appear may cause desense problems.
The indirect method cannot account for data protocol
characteristics and is less effective. Also, the bandwidth of
the noise source is important. If the source is narrow band, it
has less effect than a source occupying the entire channel
bandwidth. The method is not effective in determining
desensitization at IF frequencies or from less obvious
sources such as mixed products. The method provides
information on how much effort, if any, needs to occur to
resolve desense problems.
This method is useful when connection of the wireless card
is not yet facilitated by the platform, since it can be
performed without the wireless card being present. This
method determines the magnitude of the emissions without
extensive test facility requirements.
Figure 62. Spectrum Analyzer Setup
C.3.3 Preparing the Device Under Test
All battery-operated portable devices implement power
management. This means devices are shut down in stages as
time elapses. To provide an effective test condition, each
product should include a software test mode that powers up
all non-passive circuitry. In addition, you are advised to
98-08901C39-B
Desense
deploy a pseudo-random-based routine that utilizes all
circuit blocks and peripherals. This ensures that desense
testing considers the worst-case scenario.
PMIT testing can take up to three hours to complete. The
device under test (DUT) must remain powered during the
entire test cycle. For this reason, use external power sources
to maintain operation during testing when possible. Typical
circuit blocks to power on and utilize include:
• Display characters and backlighting
• Interface drivers and power supplies
• Keyboard scanning
• Peripheral silicon
• Mass storage devices and controllers
You can also emulate keyboard or tablet activity. Some
devices generate the bulk of their emissions during user
interaction.
C.4 PERFORMANCE GOALS
Network coverage is the ultimate goal of emissions control.
The allowable emission levels are a function of the radio
sensitivity and the required network coverage.
C.4.1 Radio Performance Capabilities
Each radio technology demands certain sensitivity
requirements. Wide area networks require the subscriber
device to be very sensitive, while local area networks
operate with higher receiver-signal levels.
Highly sensitive radios are more susceptible to noise from
the host platform. For example, assuming a 10 dB
co-channel rejection, a less sensitive receiver tolerates a
higher level of noise.
FCC Part 15 Level Comparison
The FCC emissions limits for unintentional radiators are:
• 200 µV/M between 216 MHz and 960 MHz
• 500 µV/M above 960 MHz
These limits are for measurements conducted at a distance of
three meters from the device.
As a reference, the theoretical noise level that the host device
may emit without desensitizing the most sensitive receiver is
~ 40 dB below the FCC limits.
This calculation assumes the host device and
the modem card antenna are isotropic sources.
Note
201
Desense
C.4.2 Determine Emission Level Goals
To determine the allowable emissions levels from the host
device, consider the following:
• The sensitivity of the wireless modem in use
• The targeted network coverage requirements
• The expected proximity of the wireless device to the host
platform
Achieving zero desense is not a realistic goal with a
cost-sensitive commercial product. The following is one set
of subjective levels based on industry experience:
• Channels desensitized by less than 9 dB are acceptable.
• Channels desensitized by more than 10 dB create a
noticeable problem within the network.
• Channels desensitized by more than 20 dB are
unacceptable.
It should be noted that each case is different, each air
protocol reacts in a unique way, and each network performs
differently under the same levels of unwanted ambient noise.
However, noise from the host above the desense threshold
level degrades the ultimate potential performance.
Narrow band interference sources have a low probability of
creating customer problems. Wide band sources have a
higher probability of occurring at a channel frequency and
thus have a greater potential for causing problems. For this
document, any emission that occupies less than 50 kHz of
the frequency spectrum is considered narrow band.
C.5 ACCEPTANCE ANALYSIS ON A
SAMPLE DATA SET
Consider the data set shown in Figure 63.
Figure 63. Sample Data Set
202
The measured sensitivity is a function of receiver
performance, path loss in the test facility and emissions,
creating desense on certain channels.
The data set in Figure 63 is typical of a host system. The
upper dashed line represents the equivalent FCC Part 15
Class B emission level. The lower dashed line is the
maximum sensitivity capability of the radio receiver. The
data set plot (solid line) is the actual performance of the radio
receiver as used with the host platform.
If the host unit met FCC limits from 851 to 870 MHz, the
effective sensitivity of the receiver would be reduced to
-55 dBm in this test site. The capability of the receiver is
-95 dBm, a 40 dB difference. The FCC limits are quite high
in this frequency range. Most host devices are well below the
limit in the majority of frequencies.
The worst-case desense from this platform is ~25dB at a
narrow spike near 856.5 MHz. The noise floor of the device
is in the 3 dB range, which is good. There are a number of
spikes that have a 10 dB impact on narrow band channels.
The most notable emission response is at 855.5 MHz where
a wide band emission is present. This response poses a
concern due to the number of channels it impacts and the
probability of a user wanting to operate within that range.
The level of desense is a considerable 15dB.
C.6 PREDICTION OF SOURCES
Determining the exact nature and source of each emission is
beyond the scope of this guide, with the exception of some
common scenarios. Common problems are evident in the
sample data set. The large narrow band spikes are usually the
result of harmonics from a clock source. You can determine
which clock is creating the problem by checking whether the
emission is a direct product of the clock frequency or a
sub-harmonic of it.
For example, if your system runs a 16.8 MHz clock, and a
1.23 MHz clock and a strong narrow band emission is found
at 865.2000 MHz, it is reasonable to deduce that the
emission is created by the 16.8 MHz clock as a product of
865.2/16.8 = 51.5. The 51st harmonic plus a sub-harmonic
of 8.4 MHz.
The wide band emissions are normally a switching power
supply. These emissions are created by the low frequency of
the switcher modulating onto a higher harmonic of another
source. Switching power supplies creates a lot of magnetic
energy due to the need for inductive coils. In fact, any circuit
using large inductors that are not toroidal is usually a source
of noise.
98-08901C39-B

Some emissions are tricky to pin down. They may result
from multiple order mixing of any number of sources. The
best way to discover these is to shut down sources one by one
and see if the emission disappears. Near field probing allows
a geographical fix on the emission once the source circuitry
is identified.
Noise floor problems, where the entire receive band is
desensed, preclude all methods of tracking down individual
sources.
A loop probe is a useful measurement tool for confirming
emissions sources. This probe must be small enough to
pinpoint an area from which the emission is radiating but
large enough to provide adequate sensitivity.
C.6.1 Probability of Channel Interference
The probability of a strong interference source landing on a
channel of interest is actually quite low. The possibility does
exist, especially in single-channel systems, rather than
multi-channel systems. A multi-channel system provides a
number of frequencies at which to operate.
Using probability to desense a channel only works with
narrow band sources. A wide band emission increases the
probability of desensing a channel proportional to the
bandwidth it occupies.
You can calculate the probability of an interference source
coinciding with a channel frequency. To do this, consider
that the source usually drifts over a range of frequencies,
increasing the possibility that the two will coincide. Provide
stable clock sources within the host to allow for better
prediction and control of which channels will be affected by
the noise.
C.6.2 Desense Scenarios
The target of 40 dB below FCC Class B guarantees no
desensitization. The typical scenarios that work in favor of
the system are as follows:
• The host unit is usually in a power management state,
either completely asleep or in a reduced functional state.
This reduces the EMI and allows for improved wireless
communications.
• In most systems, multiple channels are usually available
for operation. If one channel is desensitized, the radio can
choose to operate on another. This greatly reduces
potential coverage problems, and channel switching is
transparent to the user.
• The system continues to function even after being
interfered with, however, coverage range is reduced. In
98-08901C39-B
Desense
some applications, this is not a problem. This could be
true for users who do not stray into network fringe
coverage areas.
• Two-way protocols can retry unsent messages.
Each platform, network operating model, and user profile is
different. As such, each application requires a unique level
of EMI reduction effort.
C.7 METHODS OF CONTROLLING
EMISSIONS
Preferred methods of controlling emissions observe that the
emissions must be contained to a level 40 dB less than the
FCC Part 15 requirements. For WAN products, the accepted
method of achieving this is to shield.
Through past experience, it has become evident that
standard techniques used to achieve FCC certification are
not enough to satisfy wireless communications. Engineering
teams logically attempt an array of decoupling, partial
shielding, and PCB layout methods, which produce
incremental improvements, but do not achieve the emission
control requirements. Hybrid methods of shielding and
source reduction are often a good approach.
IMPORTANT: Unless the host platform is already close to
achieving the goals set out in this chapter, source reduction
efforts may only increase the direct materials cost of the
product without increasing the return on investment.
If a compromise is chosen where the target levels are not the
goal, standard EMI techniques can be of value. For narrow
band emissions, some form of clock frequency “pulling” or
control can be implemented.
C.7.1 Shielding Approach
The mechanical design of the host product must allow the
EMC engineers to create a Faraday Box shield design. This
is an electrically continuous shielded enclosure. If designed
properly, such an enclosure easily attenuates radiated signals
from the host device.
The shield approach initially appears to be a big step. The
advantage is that the shield minimizes the possible redesign
required of the host PCB platform and circuitry.
For a thorough discussion of shielded enclosure design, an
excellent reference is Electromagnetic Compatibility:
Principles and Applications, by David A Weston. The
publisher is Marcel Dekker, Inc. 270 Madison Avenue, New
York, NY 10016. Any well-written text on EMI control
probably also covers the design of shielded enclosures.
203
Desense
C.7.1.1 Components of the Shield Design
To be effective, the shield design must incorporate:
• A highly conductive shielded enclosure that encapsulates
all of the active circuitry. This can be constructed of sheet
metal or plated/sprayed plastic.
• Decoupling on all signals exiting the enclosure.
• Control of aperture sizes in the shield to less than l/10 of
the frequency of interest. This would apply to keyboard
and display apertures in the enclosure. Testing of aperture
radiation at the frequencies of interest may prove that
larger apertures are acceptable to the particular scenario.
C.7.1.2 Benefits of the Shielding Approach
Emission reduction can be achieved using shielding source
reduction techniques, such as decoupling, or PCB layout and
grounding, or a combination of the two. Once a shield is in
place, any revisions to product circuitry have no effect on
emissions levels. If a circuit level approach is used to control
the emissions, a change in circuitry can bring a new
unknown to the emission performance.
In addition, perfecting shielding designs now will provide a
jump on future requirements for emission reduction. With
the proliferation of wireless communications, emission
levels need to be reduced. It is also likely that the FCC will
tighten up the Part 15 regulations.
C.7.2 Alternate EMI Reduction Methods
Although shielding is the “brute-force” method of reducing
emission levels, other methods are available, such as:
• PCB layout modification using ground layers adjacent to
high speed layers
• Capacitive or filter decoupling
• Redistribution of module interconnects
• Clock pulling
C.7.2.1 Clock Pulling
Clock pulling is effective when the emission sources are
narrow band (Figure 64). To implement clock pulling, a
method must be devised for the modem to tell the host it is
having difficulty receiving. Devising such a method is
admittedly very difficult. The host provides pulling of its
internal emission source, which is identified as a potential
problem.
If this source is the cause of the interference, the pulling or
slight shift of the source frequency moves the harmonic
energy out of the receive channel. This is an inexpensive
204
way of solving the problem, since no special shielding or
decoupling is required.
The limitations of the clock pulling method are:
• Computing devices have multiple sources.
• Each source must be identified and controlled. This
identification is at times difficult.
• The host and modem must communicate the problem at
hand to attempt to correct it.
Figure 64. Clock Pulling
C.8 RF NETWORK ISSUES
Each RF network has its own requirements for the subscriber
device. Most networks implement a coverage equalization
scheme. This consists of configuring the infrastructure sites
so that their RF power output is equal to that of the
subscriber device.
Since most portable devices are battery operated, the
transmitter power of the portable units is relatively low. To
compensate for this, the base site transmitter power is
decreased to a level equal to that of the portable. The base
site has a much larger and more reliable power source, and is
capable of putting out more power. This helps overcome
desense problems that the portable unit incurs. Most network
operators prefer not to increase their site power because of
ERP licence limitations and cell overlap issues.
Network operators must consider ambient noise levels when
designing their coverage plans. Once the wireless modem
and host unit are engineered not to self-desense, a host of
other machines in the user’s environment can still impact
radio performance. These machines are not usually within
close proximity of the wireless modem antenna and have less
effect. An FCC Class B radiator can impact the wireless
device if it is within 30 meters of the device, assuming that
an emission exists at the channel frequency of the radio.
Networks can assist in the desense problem by offering more
than one channel frequency at which to operate. If the radio
encounters interference on a channel, it can then roam to
another.
98-08901C39-B

WAN protocols include retry mechanisms that resend
messages not acknowledged from the subscriber device.
These protocols can correct problems from intermittent
noise sources by retrying during a time slot that does not
coincide with noise source interference.
At a certain point, desensitizing a wireless modem receiver
creates unacceptable coverage in the network. This usually
is in the 10 dB range, though it can vary with networks.
C.9 ANTENNA
The Motorola g18 wireless modem is not equipped with an
on-board antenna. You must provide one within the host
device.
C.9.1 Field Strengths from the Antenna
Field strengths from the wireless modem transmitter can
reach as high as 100 V/M for WAN products. The host
device should be hardened to withstand these levels. LCD
displays and switching power supplies are particularly
susceptible to RF. Capacitive decoupling of sensitive areas
is required. Decouple the reference voltage points on power
supplies, reset lines on processors and keyboard scanning
circuitry.
C.9.2 Antenna Interactions
There are two interactions that can impact the performance
of the antenna.
• By placing a hand near the antenna, a user can detune the
antenna and absorb energy. Accordingly, the antenna
must be positioned such that interaction between the user
and the card is minimized.
• The host device might also interact with the antenna. This
is particularly true for WAN modems, which have higher
output power. An imaginary sphere of real estate should
be provided for the antenna to function. Cabling for other
peripherals must not interfere with this area.
98-08901C39-B
Desense
C.9.3 Antenna Cable Routing
The coaxial cable used to connect the modem to the antenna
must be routed away from noise sources such as oscillators,
bus lines, or noisy CPUs. These noise sources generate broad
band noise that will radiate and be picked up by the antenna
cable. In addition, this cable should be kept as short as
possible. Avoiding noise sources is the primary goal, so
within reasonable limits, length can be added to allow
routing away from noise sources.
When a long 90° MMCX connector needs to be used, it can
be purchased through Conectec. For more information, refer
to “Vendor Contacts” on page 64.
C.10 DESENSE SUMMARY
Desense considerations fall into two categories when using
a wireless device and computer as a system:
• The impact of the computer’s EMI on system perfor-
mance
• The impact of the RF fields from the wireless device
transmitter on computer operation
The latter consideration is not a significant problem. If RFI
is assessed properly, it can usually be corrected with
minimal effort and cost.
Because of the need for system coverage, the host EMI
interaction with the radio receiver can be a significant and
often elusive problem to characterize and correct. Most
computers are very fast and include numerous high
frequency radiators. These can interfere with the radio
reception of the wireless modem.
The theoretical levels at which the receiver might be
impacted are derived from system coverage requirements
and the sensitivity of the radio. These goals are not set
arbitrarily to improve product performance but to maintain
the RF performance that the networks demand and that the
radios are designed to deliver.
Since each product is unique, the level of noise is very
difficult to predict, as is the amount of effort needed to
control it. Measuring the product in an early engineering
phase is key to managing the situation.
205
Desense

206 98-08901C39-B
 4. IP OVER AT COMMANDS LIST
.

D.1 GENERAL Example

This appendix describes the AT commands set and the new at+cipe?
IP over AT service. +CIPE: 1
The old DSC bus IP primitives set provides radio internal
information via commands on request, in addition to OK
unsolicited indications.
at+cipe=?
Since the AT commands set does not provide complete radio
internal indications, a new AT interface is provided, in order +CIPE:(0-1)
to supply these complementary IP primitives via the RS232
serial port in a standard interface (AT). This service is called
OK
CIP.
at+cipe=1
The AT commands are generally an atomic operation, in
which only one command at a time is executed. The user OK
may enable or disable unsolicited AT indications, on a
command level.
The CIP service can be enabled or disabled by the user, but D.3 DSC BUS IP PRIMITIVE OVER AT
once the user enables the CIP service, he or she will receive SERVICES +CIP
unsolicited IP primitives based on internal radio events. The
CIP service enables the user to send IP primitive requests
Command Possible Response(s)
and receive indications.
+CIP=<len>,<primid>,< +CIP:<len>,<primid>
subadd>[,<primdata>] [,<primdata>]
D.2 ENABLE IP OVER AT SERVICES +CME ERROR: <err>
+CIPE
+CIP? +CME ERROR: <err>
Command Possible Response(s)
+CIP=? +CME ERROR: <err>
+CIPE=<cipen>
Defined Values
+CIPE? +CIPE: <cipen>
<len> The length (number of characters) of the field
<primdata>.
+CIPE=? +CIPE: {list of supported
<cipen>s} The value of the length is in decimal.
If the field <primdata> does not exist, then
Defined Values <len> is 00.
<cipen> <primid> The IP primitive ID (For the list of supported
IPs, refer to “IP Primitives Supported by CIP”,
0 IP over AT services (+CIP) is disabled
page 209.)
1 IP over AT services (+CIP) is enabled

98-08901C39-B 207
IP Over AT Commands List

The value is two hexadecimal bytes, The sub address is 0020.

represented in 4 (ASCII) characters.
The data field is: 0003000000, 10 characters, which
<subadd> The sub address within the XCVR, for routing represent 5 Hexadecimal bytes: 0x00, 0x03, 0x00, 0x00,
this IP primitive. (Refer to “IP Primitives 0x00
Supported by CIP”, page 209 for the list of the
The IP_ERROR_CNF primitive ID is: A87F (hexadecimal).
IPs sub addresses).
The data field is: 0003FFFF434900000000FFFF, 24
<primdata> The data of the specific IP primitive. (Refer to
characters, which represent 12 hexadecimal bytes.
“IP Primitives Supported by CIP”, page 209
for the list of the supported IPs). This data will Decimal bytes:
have padding bytes at the end of the primitive
0x00, 0x03, 0xFF, 0xFF, 0x43, 0x49, 0x00, 0x00, 0x00,
structure due to the ARM 32 bit alignment.
0x00, 0xFF, 0xFF
The number of padding bytes is deferred from
Example
0 to 3*N (N > = 0). The padding bytes should
be counted in the <len> field. The terminal/ CIP unsolicited indication
TCU should ignore these bytes.
+CIP: 8,1406,00010004
Example
+CIP: 16,a827,000000000000FFFF
CIP Request (IP_ERROR)
AT+CIP=10,A87E,0020,0003000000
AT+CIP=10,A87E,0020,0003000000
ERROR
+CIP: 24,a87f,0003FFFF434900000000FFFF
at+cmee=2
OK
OK
AT+CIP=10,A87E,0020,0003000000
The IP_ERROR_REQ primitive ID is: A87E (hexadecimal).
+CME ERROR: "operation not allowed"

208 98-08901C39-B
 IP Over AT Commands List

D.4 IP PRIMITIVES SUPPORTED BY CIP

IP_GET_HF_VOLUME_REQ 0xA886 0x0017

IP_CALL_DTMF_REQ 0xA835 0x0017 IP_GET_HF_VOLUME_CNF 0xA887 Cnf->IP

IP_CALL_STATUS_IND 0xA827 ind->IP IP_HF_AUDIO_STATUS_IND 0xA888 ind->IP

IP_CLASS_IND 0xA829 ind->IP IP_LTC_ERASED_IND 0xA88A ind->IP

IP_HOOKSWITCH_IND 0xA809 ind->IP IP_SET_RING_LEVEL_REQ 0xA88B 0x0017

IP_INDR_CTRL_STATE_IND 0xA825 ind->IP IP_SET_RING_LEVEL_CNF 0xA88 Cnf->IP

C
IP_MUTE_REQ 0xA822 0x0017
IP_ABBR_DIAL_TBL_IND 0xA831 ind->IP
IP_MUTE_IND 0xA808 ind->IP

*IP_LOW_VOLTAGE_IND - Not supported by g18.

IP_PD_USAGE_IND 0xA826 ind->IP

IP_STOP_REQ 0xA82F req->IP

D.5 REQUEST/CONFIRM PRIMITIVES
SEEM_ACTIVATE_CNF 0x1402 cnf->IP REQ

SEEM_ACTIVATE_IND 0x1403 ind->IP IP_MUTE_REQ_ID (no_cnf)

IP_CALL_DTMF_REQ_ID (no_cnf)
SEEM_CARD_STATUS_IND 0x142B ind->IP
IP_ERROR_REQ_ID
IP_GET_HF_VOLUME_REQ_ID
SEEM_DEACTIVATE_IND 0x1406 ind->IP
IP_SET_RING_LEVEL_REQ_ID
SEEM_PIN_CHANGE_CNF 0x1411 cnf->IP CNF
IP_ERROR_CNF_ID
SEEM_PIN_DISABLE_CNF 0x1413 cnf->IP
IP_GET_HF_VOLUME_CNF_ID
IP_SET_RING_LEVEL_CNF_ID
SEEM_PIN_ENABLE_CNF 0x1415 cnf->IP
SIM Card Information
SEEM_PIN_VERIFY_CNF 0x1417 cnf->IP SEEM_ACTIVATE_CNF_ID:
SEEM_STATUS_CNF_ID:
SEEM_STATUS_CNF 0x140f cnf->IP SEEM_PIN_VERIFY_CNF_ID:
SEEM_PIN_CHANGE_CNF_ID:
SEEM_UNBLOCKING_CNF 0x1419 Cnf->IP SEEM_PIN_DISABLE_CNF_ID:
SEEM_PIN_ENABLE_CNF_ID:
IP_ERROR_REQ 0xA87E 0x0020 SEEM_UNBLOCKING_CNF_ID:

IP_ERROR_CNF 0xA87F Cnf->IP

D.6 UNSOLICITED PRIMITIVES
IP_LOW_VOLTAGE_IND* 0xA884 ind->IP
IND
IP_ABBR_DIAL_TBL_IND_ID
IP_NUM_OF_ATTACHED 0xA890 ind->IP
IP_CALL_STATUS_IND_ID
_PERIPHERALS_IND
IP_CLASS_IND_ID
IP_LOW_VOLTAGE_IND_ID
IP_ATTACHED 0xA88F ind->IP
IP_MUTE_IND_ID
_PERIPHERALS_INFO IND
IP_PD_USAGE_IND_ID
IP_HOOKSWITCH_IND_ID

98-08901C39-B 209
IP Over AT Commands List

IP_INDR_CTRL_STATE_IND_ID specifically designed to "get the ball rolling" in the

IP_STOP_REQ_ID(txvr->periph) peripheral and it indicates that the transceiver is ready to
perform high level communication with the IP. Intelligent
IP_NUM_OF_ATTACHED_PERIPHERALS_IND
peripherals must wait for the first ip_class_ind primitive
IP_ATTACHED_PERIPHERALS_INFO_IND before sending a primitive to the transceiver (with the
exception of the bic_init_intelligent_cnf). Any primitives
IP_HF_AUDIO_STATUS_IND
sent to the peripheral before the ip_class_ind primitive
IP_LTC_ERASED_IND contain valid data and can be used by the peripheral.
SEEM_DEACTIVATE_IND_ID The initial ip_class_ind primitives may not contain the
SEEM_ACTIVATE_IND_ID actual number of abbreviated dialing phone book locations
in the SIM card or EEPROM. The transceiver needs to scan
and sort the phone book locations before it can indicate the
D.7 IP PRIMITIVES CIP SPECIFICATIONS number of locations. In addition, the SIM card may be PIN
protected. If it is, the SIM card phone book is not accessible
until a valid PIN is entered. Currently, this interface supports
D.7.1 Class Indicator Primitives a maximum of 255 locations in EEPROM and SIM
combined.
The transceiver sends an ip_class_ind primitive to indicate For the restrict phone book start and restrict phone book end
the current state of the phone. It is sent shortly after power fields, the phone book location numbering scheme for the
up to all the peripherals. It is also sent following a warm plug EEPROM and SIM phone book locations is defined by the
attachment and whenever the current state of the phone numbering scheme field in the ip_abbr_dial_tbl_ind
changes. primitive.
The primitive contains several pieces of information that are BROADCAST GROUP: MMI Statistics
very useful to peripherals at power up. The primitive is

Table 39. IP_CLASS_IND Parameters

Name Format Valid Values Description

Reserved WORD 0 Reserved for future use. Peripherals should ignore it.

Restrict Phone WORD Start of phone book location range for the protected (1) and
Book Start recall only (2) Restrict Phone Book Access modes.
0-255 Valid for ui1 products only.
0 Obsolete for ui2 products and successors.

Restrict Phone WORD End of phone book location range for the protected (1) and
Book End recall only (2) Restrict Phone Book Access modes.
0-255 Valid for ui1 products only.
254 Obsolete for ui2 products and successors.

Number of SIM BYTE 0-155 Number of SIM card abbreviated dialing locations.
Locations 255 Number of locations unknown, initialization in progress.

Number of E2 BYTE 0-100 Number of EEPROM abbreviated dialing locations.

Locations 255 Number of locations unknown, initialization in progress.

210 98-08901C39-B
 IP Over AT Commands List

Table 39. IP_CLASS_IND Parameters (Continued)

Name Format Valid Values Description

Language BYTE Language used for textual information is presented to user via
the TXVR's man-machine interface. Any values not listed
indicate a new language and it is up to the peripheral to decide
what language it will use.

0 English
1 German
2 Danish
3 French
4 Italian
5 Spanish
6 Swedish
7 Dutch
8 Portuguese
9 Finnish
10 Norwegian
11 Greek
12 Hungarian
13 Turkish
14 Polish
15 Thai
16 Vietnamese
17 Malay
18 Indonesian
19 Tagalog
20 Chinese
21 Czech
22 Complex Chinese

Bad Device BYTE Indicates whether a bad device condition is present.

0 No_bad_device.
1-255 Bad_device.

Manual Test BYTE Indicates whether the TXVR is in manual test mode.
0 In normal mode (not manual test).
1 In manual test mode.

Lock State BYTE Indicates whether the TXVR is locked.

0 Unlocked.
1 Locked.

98-08901C39-B 211
IP Over AT Commands List

Table 39. IP_CLASS_IND Parameters (Continued)

Name Format Valid Values Description

Restrict BYTE Indicates the Restrict Phone Book Access mode. The protected
Phone Book and recall only modes are an alternate, older restriction scheme
Access that only apply to ui1 phones (BMW Phase IV). For these
Mode modes, access to the phone book locations outside the range
defined by the restrict phone book start and end fields is
0 restricted.
1 No restrictions, all locations can be read/dialed.
2 Protected, storing/recalling is not allowed outside range (ui1).
3 Recall only, only recalling is allowed outside range (ui1).
4 Phone only, EEPROM locations can be read/dialed.
5 SIM only, SIM locations can be read/dialed.
No access, no locations can be read/dialed.

Restrict BYTE Indicates whether keypad dialing is restricted. If keypad dialing

Keypad is restricted, all keypad dialing except for emergency dialing is
Dialing restricted. Note: Phone book locations, which have not been
restricted by the Restrict Phone Book Access mode, may be
0 dialed but not programmed.
1 Keypad dialing allowed.
Keypad dialing restricted.

Restrict Phone BYTE Indicates the maximum phone number length allowed for call
Number Length origination. Only phone numbers less than or equal to this value
may be called. Note that emergency dialing is still possible
1-20 irrespective of this length.
1-32 Valid values for GSM (900 Mhz) and DCS (1800 Mhz).
Valid values for PCS (1900 Mhz) phones.

Unused 1 BYTE 0 Available for future use.

Current State BYTE >> Warm plug capable (bit 0)

0 Not capable of warm plug.
1 Capable of warm plug.
>> Charge only mode (bit 1)
0 Not in charge only mode.
1 In charge only mode.
>> warm plug active (bit 2) b
0 Inactive mode.
1 Active mode.
>> reserved for future use (bits 3-7)
0 Reserved bits are zeroed.

Unused BYTE 0 Available for future use.

Example +CIP: 40,a829,0090-0000-00FE-78-64-00-00-00-00-00-00-

14-00-01-00FFFF----
+CIP:
40,a829,0090000000FE786400000000000014000100FFFF 254--120-100 20
-----ip_class_ind
Reserved 0090

212 98-08901C39-B
 IP Over AT Commands List

RestrictPhonebook Start 0000 D.7.2 Power Down Primitives

RestrictPhonebook End 00FE - 254
At power down, the transceiver informs peripherals via the
Number of SIM Locations 78 - 120 ip_stop_req primitive that the transceiver is powering down.
Number ofE2 Locations 64 - 100 A peripheral that receives an ip_stop_req should perform its
own shutdown procedure, which may include saving some
Language 00- English
information from the transceiver. After this procedure is
Bad Device 00 complete, the peripheral should inform the transceiver via
Manual Test 00 the ip_stop_cnf primitive that it is ready for the power down.

Lock State 00- Unlocked Since peripherals may not function correctly, the transceiver
will eventually time out waiting for ip_stop_cnf primitives
Restrict Phone Book from the peripherals. However, in error recovery, significant
Access Mode 00 additional time is added to the power down process which
Restrict Keypad Dialing 00 may cause user dissatisfaction. The peripheral must respond
with an ip_stop_cnf primitive in normal situations.
Restrict Phone Number
Length 14 -20 BROADCAST GROUP: Power Down
Unused 1 00
Current State 01
Unused 21 00

Table 40. IP_STOP_REQ Parameters

Name Format Valid Values Description

None None None

Example primitives. The primitives support phone book browsing by

location number and are sorted alphabetically by alpha-tag.
+CIP: 0,a82f,-----------IP_STOP_REQ (transc->periph.)
Please note that GSM Recommendation 07.07 defines a
standards-based phone book interface. This alternate
interface is the preferred interface for future applications.
D.7.3 Phone Book Related Primitives
The transceiver sends an ip_pd_usage_ind primitive to
The transceiver provides the peripheral with information on inform peripherals that a phone book location (personal
phone book locations via the ip_class_ind, ip_pd_usage_ind directory location) is being used to originate a call.
and ip_abbr_dial_tbl_ind primitives. Peripherals can
BROADCAST GROUP: Personal Directory Statistics
implement a phone book browsing interface using the
information available with these primitives and the
ip_get_info_element_req and ip_get_info_element_cnf

Table 41. IP_PD_USAGE_IND Parameters

Name Format Valid Values Description

Memory Type WORD 75 Abbreviated dialing memory location.

Other Reserved and should be ignored by the peripheral.

Device Type WORD 0 Memory location residing in EEPROM.

1 Memory location residing in the SIM.
Other Reserved and should be ignored by the peripheral.

Location BYTE 1-255 Abbreviated dialing location used per device type.

98-08901C39-B 213
IP Over AT Commands List

Table 41. IP_PD_USAGE_IND Parameters (Continued)

Name Format Valid Values Description

Reserved 3 BYTES Padding added by compiler. Should be ignored by the

peripheral.

Example Reserve FF-FF-FF

--CALLING_FROM_PB_ABRA_DIAL--NO1-- +CIP:16,a826,004B-0001-01-FFFFFF-
EPROM---ENTER_SMART_BUTTON IP_PB_USAGE_IND
+CIP:16,a826,004B-0000-01-FFFFFF- 75 SIM LOCATION 1
IP_PB_USAGE_IND
The transceiver sends an ip_abbr_dial_tbl_ind primitive to
Memory Type 004B 75 provide peripherals with information on abbreviated dialing
locations in EEPROM and the SIM card.
Device Type 0000 EEPROM
BROADCAST GROUP: Personal Directory Statistics
Location 01

Table 42. IP_ABBR_DIAL_TBL_IND Parameters

Name Format Valid Values Description

Reserved WORD Reserved for future use, peripherals should ignore.

Numbering BYTE The Numbering Scheme indicates how the transceiver interprets
Scheme abbreviated dialing location numbers. For example, EEPROM
locations followed by SIM locations. This information is
necessary so that a peripheral can assign the same meaning to
location references and provide MMI consistency.
Note that EEPROM locations followed by SIM locations are
0 equivalent to the `MT' storage type defined in [4].
EEPROM locations followed by SIM locations.

Table ID BYTE 0 Usage Table.

1 Alpha Sort Table.

Reserved WORD Reserved for future use, peripherals should ignore.

Usage Table 32-255 The Usage Table is a bitmap that indicates the abbreviated
or BYTES dialing locations that contain a number or alpha-tag. When a bit
Alpha Sort is set to one, the location contains a number or alpha-tag. The
Table first byte contains information on locations 1 through 8, LSB is
location 1. The second byte contains information on locations 9
through 16, LSB is location 9. And so on.
The Alpha Sort Table is a table containing all abbreviated dialing
locations that have an alpha-tag defined. Each byte contains a
location number. The table is sorted alphabetically. The end of
the table is indicated when a byte has a value of zero, or the
255th byte has a valid location number. Since the transceiver
supports a maximum of 255 locations, this field can contain a
maximum of 255 bytes.

214 98-08901C39-B
 IP Over AT Commands List

Example Table ID 00-Usage_table

+CIP:32,a831,0090-00-01-FFFF- Reserved DFF7
9669676F01666ECB6500
Usage Table or Alpha Sort Table
01-alpha_sort_table 010000000000000000000000F0610000000020000000000
0000400000000000000000000000000000000000000
Reserved 0090
Numbering Scheme 00
Table ID 01-alpha_sort_table D.7.4 Display Indicator Primitives
Reserved FFFF The transceiver sends an ip_indr_ctrl_state_ind primitive to
Usage Table or Alpha Sort Table 96-69-67-6F-01-66-6E- inform peripherals of display indicator state changes in the
CB-65-00 transceiver's display. At power-up, all indicators are
assumed to be off. No ip_indr_ctrl_state_ind primitives are
+CIP:102,a831,0101-00-00-DFF7- supplied to indicate this initial state. Following a warm-plug
010000000000000000000000F0610000000020000000000 attachment, ip_indr_ctrl_state_ind primitives are sent to
0000400000000000000000000000000000000000000 provide the current state of the indicators.
00-usage_table BROADCAST GROUP: Indicator
Reserved 0101
Numbering Scheme 00

Table 43. IP_INDR_CTRL_STATE_IND Parameters

Name Format Valid Values Description

Indicator ID BYTE 0 IN USE indicator.

1 ROAM indicator.
2 NO SERVICE indicator.

Indicator State BYTE 0 Off.

1 On.
2 Flashing.

Reserved 3 BYTEs Padding added by compiler. Should be ignored by the

peripheral.

For the IN USE indicator: Off (0) The phone is registered with its home network.
Off (0). Phone not in use. No call in progress. On (1) The phone is registered with a preferred system other
than home.
On (1). Phone in use. A call is in progress.
Flashing (2) The phone is registered with a non-preferred
Flashing (2). Not applicable.
system.
For the NO SERVICE indicator:
+CIP: 8,a825,00-01-0000 --ip_indr_ctrl_state_ind--in call
Off (0). The phone is registered with a system.
00 - In_use
On (1). The phone is outside any system coverage.
01- Calling
Flashing (2). The phone is in an area with coverage, but is
Indicator ID - 00 in_use
not registered with the system. Only emergency calls (112)
are allowed. Indicator State 01- calling
The ROAM indicator is meaningful only if the NO Reserved 00-00
SERVICE indicator is off.

98-08901C39-B 215
IP Over AT Commands List
D.7.5 Call Control Interface Primitives
The call control interface primitives deal with the control of
voice calls.
D.7.5.1 Background
The transceiver's voice calls are always under parallel call
control. This means that any peripheral or handset connected
to the transceiver may act on a voice call regardless of the
device that actually established the call.
When a peripheral wants to originate a call, it should use the
ip_call_start_req primitive. The peripheral can use this
primitive to specify the digits to dial (keypad dialing format)
or specify a phone book location (memory dialing format).
Automatic redial from a peripheral is not supported.
The presence of a ringing, mobile-terminated call is
announced via the ip_call_status_ind primitive. A peripheral
can direct the transceiver to answer the call via the
ip_call_accept_req primitive. If the peripheral is interested
in the outcome of call establishment, it will need to monitor
subsequent ip_call_status_ind primitives.
When a peripheral wants to release a call, it can send an
ip_call_release_req primitive. The transceiver will supply
subsequent call status information via the ip_call_status_ind
primitive.
D.7.5.2 Call Restrictions
Call restriction settings in the transceiver's EEPROM and
SIM card can affect the call control interface.
Restrict keypad dialing is a flex option. It can prevent
keypad dialing except for emergency dialing. Memory
dialing from phone book locations is allowed per additional
limitations which may be imposed by restrict phone book
access options. The restrict keypad dialing field in the
ip_class_ind primitive indicates when keypad dialing is
restricted.
Restrict phone book access is a flex option. It can prevent
various types of phone book dialing (memory dialing). The
Restrict Phone Book Access mode, Restrict Phone Book
Start, and Restrict Phone Book End fields in the ip_class_ind
primitive indicate the transceiver's restricted phone book
access settings.
Restrict phone number length is a flex option. It controls the
maximum phone number length for mobile-originated calls.
For example, the maximum phone number length can be set
to prevent international dialing. Emergency dialing is
always allowed regardless of the maximum phone number
length. The restrict phone number length field in the
216
ip_class_ind primitive indicates the transceiver's maximum
phone number length.
Newer SIM cards support the fixed dialing feature. A special
SIM card phone book contains a list of phone number
prefixes that can be used for outgoing calls. When fixed
dialing is enabled, the leading digits in an outgoing call must
match a number in the fixed dialing phone book. The fixed
dialing status can be determined via primitives in [4].
Restrict incoming calls is a flex option. This restriction
prevents peripherals from being informed of mobile
terminated call establishing events via the ip_call_status_ind
primitive. This restriction is not communicated to the
peripheral directly.
D.7.6 Call Status Indication Primitives
The transceiver sends an ip_call_status_ind primitive to
announce a change in the status of a voice call that it
controls.
An IP may receive what it considers to be
duplicate call status indications, that is,
primitives with the same information more than
Note once. IPs must not be affected by receiving
duplicate call status indications.
• <Idle>: The CC has returned to the fully Idle state. No
communication with the network is in progress. Note that
the CC may go to the Idle state from any other state.
• <MO Establishment>: The CC is attempting to establish
a mobile-originated call.
• <Waiting to Answer MT Call>: The network is attempt-
ing to establish a call. The CC is waiting for an entity to
instruct it to answer the call.
• <Completing MT Establishment>: An entity has
instructed the CC to answer the call. The CC is
completing the process of establishing the call.
• <Fully Active>: Call establishment is completed. The
current call is now fully active.
• <Releasing>: The current call has started releasing. Note
that the CC may go to the Releasing state from any state
except Idle.
The ip_call_status_ind contains a local tone status bit, which
indicates the phone is generating tones locally after a call
attempt has failed. The local tone status bit is only valid
when the current call state is idle. In all other call states, the
peripheral should ignore the local tone status bit.
BROADCAST GROUP: Call
98-08901C39-B
 IP Over AT Commands List

Table 44. IP_CALL_STATUS_IND Parameters

Name Format Valid Values Description

Local Tone BYTE >> local tones generated by transceiver (bit 7)

0 Local tones off.
1 Local tones on.
>> bits 0-6 are reserved
Peripheral must ignore these bits.

Extended Call BYTE Bits indicate current and previous extended call states related to
States waiting calls, held calls, and multiparty calls.
>> Previous Call State (high nibble)
1000 Multiparty call present.
0100 Held call present.
0010 Active call present.
0001 Incoming / Waiting call present.
>> Current Call State (low nibble)
1000 Multiparty call present.
0100 Held call present.
0010 Active call present.
0001 Incoming / Waiting call present.

Reserved BYTE Reserved for future use, peripherals must ignore.

Current Call BYTE >> upper nibble is reserved

State peripheral must ignore these bits.
>> lower nibble
0 Idle.
1 MO Establishment.
2 Waiting to Answer MT Call.
3 Completing MT Establishment.
4 Fully Active (includes call on hold).
5 Releasing.
6 Redial.
7 Call Pending.
8 MO Alerting.

98-08901C39-B 217
IP Over AT Commands List

Table 44. IP_CALL_STATUS_IND Parameters (Continued)

Name Format Valid Values Description

Previous BYTE >> upper nibble is reserved

Call State peripheral must ignore these bits.
>> lower nibble
0 Idle.
1 MO Establishment.
2 Waiting to Answer MT Call.
3 Completing MT Establishment.
4 Fully Active (includes call on hold).
5 Releasing.
6 Redial.
7 Call Pending.
8 MO Alerting.

Reserved 3 BYTE Padding added by compiler. Should be ignored by the

peripheral.

Example generates the tones to the called party. The ip_call_dtmf_req

+CIP: 6,a827,0000000700FF42D1 MO PENDING
+CIP:16,a827,0011000200FFFFFF11-INCOMING CALL
02-WAITING TO
+CIP:16,a827,001000030053FFFF-03-COMPLETING
MT ESTA.
+CIP: 16,a827,0010000300C0FFFF
+CIP:16,a827,002200040008FFFF-04 -ACTIVE CALL
+CIP:16,a827,002200040008FFFF 04 -ACTIVE CALL
primitive does not generate keypress feedback tones. The
ip_key_feedback_ind primitive can be used for this purpose.
Currently, DTMF signaling can only be sent during a call
when the current state is Fully Active, (see
“IP_CALL_STATUS_IND Parameters,” page 217). If the
transceiver receives an ip_call_DTMF_REQ when it is not
allowed, the request is ignored. If DTMF signaling is not
allowed, the transceiver simply ignores the primitive.
In future, DTMF signalling may be allowed in other call
states. DTMF signaling will never be allowed in the Idle
state. This will prevent nuisance primitives every time the
user presses a key on the peripheral.

Local Tone 00 The peripheral should send two ip_call_dtmf_req primitives

for each DTMF digit. The first is normally sent as a result of
Extended3Call States 22 - Active/previous_call_present a user's key press. It should indicate Start DTMF Signaling.
Reserved 00 The second is normally sent as a result of a user's key release.
It should indicate Stop DTMF Signaling. For the second
Current Call State 04 - Mo establishment action, the timestamp field indicates the amount of time in
PreviousCall State 00 milliseconds that the signaling lasts. This is usually the
amount of time that the user has held down the key. The
Reserved 08-FF-FF transceiver uses the timestamp to produce DTMF signaling
for the correct amount of time in case of network delays or
other problems.
D.7.7 Generate DTMF Signalling
Primitives

A peripheral can send ip_call_dtmf_req primitives so that

DTMF signalling will be sent to the network. The network

218 98-08901C39-B
 IP Over AT Commands List

Table 45. IP_CALL_DTMF_REQ Parameters

Name Format Valid Values Description

Time Stamp LWORD 0 When DTMF signaling starts, it should be set to zero.
non-zero Otherwise, it should be set to time in milliseconds since starting.

Start/Stop BYTE 0 Stop DTMF Signaling.

1 Start DTMF Signaling.

Character Set BYTE The character set defines how the DTMF digit is formatted.
0 Motorola GSM Character Set (ASCII).

DTMF Digit BYTE `0'-'9','*','#' DTMF digit to start/stop per Character Set.
ASCII

Example D.7.8 Hook-switch Status Indicator

at+cip=14,A835,0017,00000000010031-START- Primitives
ip_call_dtmf_req
The transceiver sends an ip_hookswitch_ind primitive to
OK inform peripherals of the status of portable/external
Time Stamp 00 00 00 00 handset(s), analog/digital hands-free device(s), and the
boom headset (hearing aid adaptor) device.
Start 01
BROADCAST GROUP: Indicator
Character Set 00
DTMF Digit 31 (‘1’)
at+cip=14,A835,0017,00000020000031-END-
ip_call_dtmf_req
OK

Table 46. IP_HOOKSWITCH_IND Parameters

Name Format Valid Values Description

Update Reason BYTE 0 Flip State Change.

1 Boom Headset Add/Remove.
2 Analog Hands-free Add/Remove.
3 Digital Hands-free Add/Remove.
4 Analog Handset Add/Remove.
5 Digital Handset Add/Remove.
6 Portable Cradle State Change.
7 External Digital Handset Lifted.
8 External Digital Handset Hung-Up.
9 Handset/Hands-free Toggle.
10 Call State Begin/End.
11 Exit Manual Test.
12 Invalid Reason.

Reserved BYTE Reserved for future use, peripheral must ignore.

98-08901C39-B 219
IP Over AT Commands List

Table 46. IP_HOOKSWITCH_IND Parameters (Continued)

Name Format Valid Values Description

Info Mask BYTE >> Flip state (bit 0)

0 Closed.
1 Open, or no flip.
>> Boom headset device (bit 1)
0 Not present.
1 Present.
>> Bits 2-7 are reserved for future use, peripheral must ignore.

Hands-free BYTE >> Analog hands-free speakers (bit 0)

Present Mask 0 Not present.
1 Present.
>> Hands-free digital devices (bits 1-7)
0 Not present.
1 Present.
>> If Hands-free Present Mask byte is 0, there are no hands-
free devices.

Handset BYTE >> Portable handset (bit 0)

Present Mask 0 Not present (mobile/transportable).
1 Present (portable phone).
>> External digital handset (bits 1-7)
0 Not present.
1 Present.
>> If Handset Present Mask byte is 0, there are no handsets.

Handset BYTE >> Portable cradle state (bit 0)

Active Mask 0 In cradle, or not a portable.
1 Not in cradle, or not supported.
>> External digital handset (bits 1-7)
0 On hook (in cup).
1 Off hook (out of cup).
>> If Handset Active Mask byte is 0, all handsets are on hook

Reserved WORD Padding added by compiler. Should be ignored by the

peripheral.

Example Info Mask 00

PICK_UP_HS Hands-free Present Mask 05 - analog hands-free
speakers present and
+CIP:16,a809,07-00-00-05-04-0E-FFFF-
hands- free digital devices
IP_HOOKSWITCH_IND
present (DSC address
07-handset_lifted number 2)
Update Reason 07 - External Digital Hand- Handset Present Mask 04-->> external digital hand-
set Lifted set present
Reserved 00 HandsetActive Mask4 0E

220 98-08901C39-B
 IP Over AT Commands List

Reserved FFFF D.7.9 Microphone Mute Primitives

HS_HUNG_UP
A peripheral can send an ip_mute_req primitive to instruct
+CIP:16,a809,08-00-00-05-00-00-FFFF- the Audio Manager to update the microphone mute state.
IP_HOOKSWITCH_IND There is no confirmation to this primitive but there is an
ip_mute_ind primitive.

Table 47. IP_MUTE_REQ Parameters

Name Format Valid Values Description

Type BYTE 0 Toggle microphone mute state, off->on or on->off

The transceiver sends an ip_mute_ind primitive to indicate a BROADCAST GROUP: Indicator

change in the microphone mute state. The microphone mute
state can be changed by an intelligent peripheral via the
ip_mute_req primitive. It can also be changed via the
phone's man-machine interface.

Table 48. IP_MUTE_IND Parameters

Name Format Valid Values Description

Mute State BYTE 0 Microphone muting is OFF.

1 Microphone muting is ON.

Reserved 3 BYTEs Padding added by compiler. Should be ignored by the

peripheral.

Example procedures at power up, power down, SIM card

+CIP: 8,a808,01460000 - ip_mute_ind--01-mute_on
+CIP: 8,a808,00060401-ip_mute_ind--00-mute_off
Mute state 00
Padd 06 04 01
D.7.10 SEEM Interface Primitives
At power up, after the transceiver has determined the card
readers present on the DSC bus, it will choose a card reader
and SIM card to activate. The transceiver gives a SIM card
in an external card reader priority over a SIM card in the
internal card reader. For details on individual card reader
deactivation, and SIM card insertion, refer to the GSM
Subscriber SIM Card Reader Interface Specification,
version 1.2.
The primitives listed in the following sections can be used to
determine SIM card status. In general, there are two service
categories: limited service and ready for full service. With
limited service, no SIM data fields can be accessed and only
emergency calls can be placed. Table 49 documents how to
determine the service status category but does not document
all possible return status values for each of the primitives
involved. Only primitives with a documented return status
should be used to determine the SIM card status. Primitive/
return status pairs not shown should be ignored.

98-08901C39-B 221
IP Over AT Commands List

Table 49. SIM Card Status

SIM Card Return

Primitive Description
Status Status

Insert Card SEEM_ACTIVATE_CNF No SIM No card in any card reader at power up.
(Emergency
Only) SEEM_DEACTIVATE_IND No SIM The active card was removed.

Check Card SEEM_DEACTIVATE_IND Bad SIM Bad card, error in communications, or card is
(Emergency backwards.
Only)
SEEM_ACTIVATE_IND Bad SIM Bad card detected at power up or when activating a
SEEM_ACTIVATE_CNF new card.

Enter PIN SEEM_STATUS_CNF PIN A PIN enabled card has been inserted.
(Emergency Enabled
Only)
SEEM_PIN_VERIFY_CNF Bad Code Incorrect PIN entered. `Wrong PIN' will blink.

Blocked SEEM_STATUS_CNF PIN Blocked A PIN blocked card has been inserted.
(Emergency
Only) SEEM_PIN_CHANGE_CNF PIN Blocked Incorrect PIN entered more than 3 times, card is
SEEM_PIN_DISABLE_CNF blocked.
SEEM_PIN_ENABLE_CNF
SEEM_PIN_VERIFY_CNF

SEEM_UNBLOCKING_CNF PIN Blocked An incorrect unblock code was entered.

Bad Card SEEM_STATUS_CNF No Secret The SIM card is defective.

see Supplier SEEM_PIN_CHANGE_CNF Code
(Emergency SEEM_PIN_DISABLE_CNF or
Only) SEEM_PIN_ENABLE_CNF Other
SEEM_PIN_VERIFY_CNF Technical
SEEM_UNBLOCKING_CNF Problem

Blocked, SEEM_STATUS_CNF Permanentl The SIM card is permanently blocked.

see Supplier SEEM_UNBLOCKING_CNF y Blocked
(Emergency
Only)

Transition to SEEM_ACTIVATE_CNF SIM SIM card is activated.

New Status in Available
Process
(Emergency
Only)

222 98-08901C39-B
 IP Over AT Commands List

Table 49. SIM Card Status (Continued)

SIM Card Return

Primitive Description
Status Status

Ready for SEEM_STATUS_CNF PIN PIN code is disabled.

Full Services Disabled

SEEM_PIN_VERIFY_CNF Successful PIN entry has unlocked the SIM card.

SEEM_UNBLOCKING_CNF Successful PUK entry has unblocked the SIM card.

D.7.11 Idle SIM Card Notification BROADCAST GROUP: SIM Availability

Primitives

The transceiver sends a seem_activate_ind primitive to

indicate that an idle, non-active SIM card has been inserted
or removed. This primitive does not indicate anything about
the status of the active SIM card.

Table 50. SEEM_ACTIVATE_IND Parameters

Name Format Valid Values Description

SIM Status WORD 1 No SIM, idle SIM was removed or no alternate SIM is present.
2 Bad SIM.
4 Idle SIM, idle SIM inserted.

Reserved WORD Padding added by compiler. Should be ignored by the

peripheral.

Example Reserved 007F

+CIP: 8,1403,0004-007F 04_idle_sim-
SEEM_ACTIVATE_IND
D.7.12 SIM Card Deactivation Notification
SIM Status 0004 › Idle SIM, idle SIM
inserted. The transceiver sends a seem_deactivate_ind primitive to
Reserved 007F indicate that the active SIM card has been removed or is no
longer usable because of a SIM card communication failure.
+CIP: 8,1403,0001-0381 01_no_sim_==remove_sim- This primitive always indicates that the active SIM card is no
SEEM_ACTIVATE_IND longer usable.
SIM Status- -- 0001 › No SIM, idle SIM BROADCAST GROUP: SIM Availability
removed or no alternate SIM
present

Table 51. SEEM_DEACTIVATE_IND Parameters

Name Format Valid Values Description

SIM Status WORD 1 No SIM, active SIM card has been removed.
2 Bad SIM, phone can no longer talk to the active SIM card.

98-08901C39-B 223
IP Over AT Commands List

Table 51. SEEM_DEACTIVATE_IND Parameters (Continued)

Name Format Valid Values Description

Reserved WORD Padding added by compiler. Should be ignored by the

peripheral.

Example D.7.13 SIM Card Activation Notification

+CIP: 8,1406,0001-0381 01-no_sim- Primitives
SEEM_DEACTIVATE_IND
The transceiver is responsible for deciding when to initiate a
SIM Status 0001 › No SIM, active SIM card SIM card activation. It will forward a copy of the
has been removed seem_activate_cnf primitive to subscribing peripherals.
Reserved 0381 Therefore, a peripheral can use the seem_activate_cnf to
determine the state of the active SIM card.
BROADCAST GROUP: SIM Availability

Table 52. SEEM_ACTIVATE_CNF Parameters

Name Format Valid Values Description

SIM Status WORD 0 SIM Available, active SIM has answered to reset correctly.
1 No SIM, there is no active SIM card.
2 Bad SIM, phone cannot talk to the active SIM card.

Reserved WORD Padding added by compiler. Should be ignored by the

peripheral.

Example transceiver will subsequently coordinate the submission of

codes such as the PIN and PUK to the SIM card. The
+CIP: 8,1402,0001-0200 01_no_sim-
transceiver forwards a copy of the confirmation primitives
SEEM_ACTIVATE_CNF
associated with these procedures to peripherals. This allows
SIM Status 0001 › No SIM, active SIM card peripherals to track the security status of the active SIM card.
has been removed Peripherals may also check the active SIM card's security
Reserved 0200 status via the newer MMI primitives ip_gen_pin_status_req
and ip_gen_pin_status_cnf.
Immediately after SIM card activation, the transceiver
D.7.14 SIM Card Security Notifications forwards a seem_status_cnf primitive to peripherals.

Shortly after the transceiver activates a SIM card it will BROADCAST GROUP: SIM Security/Access
check the PIN status of the SIM card. When provided, the

Table 53. SEEM_STATUS_CNF Parameters

Name Format Valid Values Description

PIN Result WORD 2 PIN enabled, PIN entry required.

3 PIN disabled, no PIN entry required.
5 PIN blocked, user must enter PUK to unblock.
6 Permanently blocked.
7 No secret code.
8 Other technical problem.

224 98-08901C39-B
 IP Over AT Commands List

Table 53. SEEM_STATUS_CNF Parameters (Continued)

Name Format Valid Values Description

Reserved WORD Padding added by compiler. Should be ignored by the

peripheral.

Example Following a PIN entry attempt, the transceiver forwards a

seem_pin_verify_cnf primitive to peripherals.
+CIP:8,140f,0003-0300 03_pin_disable-
SEEM_STATUS_CNF BROADCAST GROUP: SIM Security/Access
PIN Result 0003 › PIN Disabled, no PIN
entry required
Reserved 0300

Table 54. SEEM_PIN_VERIFY_CNF Parameters

Name Format Valid Values Description

PIN Result WORD 0 Success, PIN verification successful.

1 Bad Code, PIN verification failure, not PIN blocked.
5 PIN Blocked, from 3rd PIN verification failure.
7 No Secret Code.
8 Other Technical Problem.

Reserved WORD Padding added by compiler. Should be ignored by the

peripheral.

Example Reserved 0300

+CIP: 8,1417,0005-0300 05_PIN_BLOCKED--- Following a PUK entry attempt, the transceiver forwards a
SEEM_PIN_VERIFY_CNF seem_unblocking_cnf primitive to peripherals.
PIN Result 0005 › PIN Blocked, from 3rd BROADCAST GROUP: SIM Security/Access
PIN verification failure

Table 55. SEEM_UNBLOCKING_CNF Parameters

Name Format Valid Values Description

PIN Result WORD 0 Success, PUK verification successful.

1 Bad code, PUK verification failure, not permanent blocked.
6 Permanently blocked, from 3rd PUK verification failure.
7 No secret code.
8 Other technical problem.

Reserved WORD Padding added by compiler. Should be ignored by the

peripheral.

Example PIN Result 0000 › Success, PUK verification

successful
+CIP: 8,1419,0000-0300 00_SUCCESS_PUK(PUK2)
SEEM_UNBLOCKED_CNF Reserved 0300

98-08901C39-B 225
IP Over AT Commands List

Following a PIN disable attempt, the transceiver forwards a BROADCAST GROUP: SIM Security/Access
seem_pin_disable_cnf primitive to peripherals.

Table 56. SEEM_PIN_DISABLE_CNF Parameters

Name Format Valid Values Description

PIN Result WORD 0 Success, no PIN entry required at power-up.

1 Bad code, PIN does not match, PIN not disabled.
3 PIN disabled, PIN entry was already disabled.
5 PIN blocked, from 3rd bad PIN code.
7 No secret code.
8 Other technical problem.

Reserved WORD Padding added by compiler. Should be ignored by the

peripheral.

Example Following a PIN enable attempt, the transceiver forwards a

seem_pin_enable_cnf primitive to peripherals.
+CIP:8,1413,0000-0300-----_SUCCESS_DISABLE--
SEEM_PIN_DISABLE_CNF BROADCAST GROUP: SIM Security/Access
PIN Result 0000 › Success, PUK verification successful
Reserved 0300

Table 57. SEEM_PIN_ENABLE_CNF Parameters

Name Format Valid Values Description

PIN Result WORD 0 Success, PIN entry required at power-up.

1 Bad code, PIN does not match, PIN not enabled.
2 PIN enabled, PIN entry was already enabled.
5 PIN blocked, from 3rd bad PIN code.
7 No secret code.
8 Other technical problem.

Reserved WORD Padding added by compiler. Should be ignored by the

peripheral.

Example Following a PIN change attempt, the transceiver forwards a

seem_pin_change_cnf primitive to peripherals.
+CIP:8,1415,0000-0300 00_SUCCESS_ENABLE--
SEEM_PIN_ENABLE_CNF BROADCAST GROUP: SIM Security/Access
PIN Result 0000 › Success, PIN entry
required at power-up.
Reserved 0300

226 98-08901C39-B
 IP Over AT Commands List

Table 58. SEEM_PIN_CHANGE_CNF Parameters

Name Format Valid Values Description

PIN Result WORD 0 Success, PIN code was changed.

1 Bad code, old PIN does not match, not changed.
4 Not allowed, PIN entry is not enabled, cannot change.
5 PIN blocked, from 3rd bad PIN code.
7 No secret code.
8 Other technical problem.

Reserved WORD Padding added by compiler. Should be ignored by the

peripheral.

Example PIN result field. This field contains the status of the last
security operation. Its meaning is largely dependent on the
+CIP:8,1411,0000-0300->00_SUCCESS_PIN_CHANGE-
last security operation attempted. The ip_gen_pin_stat_req
--SEEM_PIN_CHANGE_CNF
and ip_gen_pin_stat_cnf primitives are a more reliable
PIN Result 0000 › Success. PIN code was changed mechanism for determining the PIN status of the active SIM
card following a warm plug attach.
Reserved 0300
BROADCAST GROUP: SIM Security/Access
Following a warm plug attach, the transceiver sends a
seem_card_status_ind primitive with current SIM card
security information. Peripherals should be careful using the

Table 59. SEEM_CARD_STATUS_IND Parameters

Name Format Valid Values Description

PIN Result WORD 0 Success, last operation successful

1 Bad code, last operation not successful
2 PIN enabled, PIN entry was already enabled
3 PIN disabled, PIN entry was already disabled
4 Not allowed, last operation is not allowed
5 PIN Blocked, from 3rd bad PIN code
6 Permanently blocked, from 3rd pad PUK code
7 No secret code
8 Other technical problem
9 Switch band

SIM Status WORD 0 SIM available, active SIM has answered to reset properly
1 No SIM, there is no active SIM card
2 Bad SIM, phone cannot talk to the active SIM card
3 Good SIM, after test card
4 Idle SIM, new card just inserted
5 Uninitialized SIM, no secret code and perm blocked
6 Active SIM, current working card in for table
7 Clone SIM, clone card indication to MMI
8 Good clone, after test clone card
9 Active clone, current working clone card for table

98-08901C39-B 227
IP Over AT Commands List

Example • SW_VERSION_NUM: Peripheral’s software version

number.
+CIP: 8,142b,0004-0004------------------------
SEEM_CARD_STATUS_IND • STATUS: The status of the peripherals: either ALIVE or
DEAD. With "dead" status, the peripherals either do not
PIN Result 0004 › Success, last operation exist on the DSC bus or do exist but have failed to
successful initialize.
SIM Status 0004-> Not Allowed, last operation is • FAILED_TO_INITIALIZE: If this field is "true", the
not allowed peripherals are actually attached to the DSC bus but have
failed during the initialization process. If this field is
"false", then there are no peripherals attached to the DSC
D.7.15 Attached Peripherals Primitives bus.
• DEVICE_TYPE_BMAP: This bit-mapped field holds all
The IP_ATTACHED_PERIPHERALS_IND primitive’s the Call Processor events, which this peripheral is
purpose is to inform the IP of the mobile's peripherals status. interested in receiving.
It will inform all DSC addresses held by peripherals, their These seven fields are held for each peripheral attached to
types and specific information, as well as unregistered or the radio. In addition, there are two fields that hold the
failed peripherals. number of ALIVE peripherals on the bus and the number of
The IP_ATTACHED_PERIPHERALS_IND primitive peripherals, which have failed during the initialization
consists of the following fields: process.

• DSC_ADDR: The DSC address that the radio has allo-
cated to the peripheral.
• PRODUCT_ID: The type of peripheral that is present (for
example, card reader, DHFA, eject box, and so on.)
• BIC_SERIAL_NUM: Serial number of peripheral
device, programmed into BIC EEPROM.
NUM_OF_ALIVE - Number of ALIVE peripherals.
NUM_OF_FAILED - Number of peripherals that have
failed to initialize.
BROADCAST GROUP: Intelligent peripherals can use
primitive broadcasting groups to select the primitives they
receive from the transceiver. This allows peripherals to
reduce the overhead associated with primitives that are not
necessary for a specific intelligent peripheral application.

Table 60. IP_NUM_OF_ATTACHED_PERIPHERALS_IND Parameters

Name Format Valid Values Description

NUM_OF_ALIVE 0-7 Total number of alive (registered) peripherals

NUM_OF_FAILED 0-7 Total number of failed (unregistered) peripherals

Example
+CIP: 4,a890,02-00
NUM_OF_ALIVE 02 › Total number of alive (registered)
peripherals
NUM_OF_FAILED 00 › Total number of failed (unregis-
tered) peripherals

228 98-08901C39-B
 IP Over AT Commands List

Table 61. IP_ATTACHED_PERIPHERALS_INFO_IND Parameters

Name Format Valid Values Description

DSC_ADDR BYTE 1-7

PRODUCT_ID WORD Shows the product type (TCU,EMMI,SIM etc)

0000-0ffff Dumb / HS
8000-8010 Emmi
8011 E. SIM C/R
8034 ACP TCU Jaguar
8031 TeleAid DC
8032 TeleAid DC

BIC_SERIAL 6 BYTES If it exists and status is dead, it means this peripheral failed to
NUM register

SW_VERSION WORD

STATUS BYTE 0 Live (registered) peripheral

2 Dead (no peripheral or failed to register)

FAILED_TO WORD
INITIALIZE

DEVICE_TYPE LWORD 0001 Emmi

BMAP 0010 Data
0020 SIM
0040 BMW TCU
0080 Gen. TCU

Example FAILED_TO INITIALIZE 0000

HS LIVE DEVICE_TYPE BMAP 00-00-00-00
+CIP: 36,a88f,02-000A-000A017402A8-0000-00-0000- +CIP: 36,a88f,01-8011-8011017402A0-3309-00-0000-
00000000 00000020
DSC_ADDR 02 LIVE SIM
PRODUCT_ID 000A › 0000-0fff Dumb / HS
BIC_SERIAL NUM 00-0A-01-74-02-A8 D.7.16 IP_HF_AUDIO_STATUS_IND
SW_VERSION 0000
Indication whenever any type of audio is starting or ending.
STATUS 00 › 0 - live (registered)
peripheral The purpose of this primitive is to let the TCU know about
pending audio, in order to synchronize other audio related
machines like entertainment radio etc.

98-08901C39-B 229
IP Over AT Commands List

Table 62. IP_HF_AUDIO_STATUS_IND Parameters

Name Format Valid Values Description

Audio_status BYTE 1 Audio started

0 Audio ended

Reserved 3 BYTE Padding added by compiler. Should be ignored by the

peripheral.

Example Audio_status 00
+CIP:8,a888,01-9F17DEIP_HF_AUDIO_STATUS_IND Reserved 9F-17-DE
Audio_status 01
Reserved 9F-17-DE D.7.17 IP_SET_RING_LEVEL_REQ

Allows the TCU to control the ringer gain level.

+CIP:8,a888,00-9F17DEIP_HF_AUDIO_STATUS_IND

Table 63. IP_SET_RING_LEVEL_REQ Parameters

Name Format Valid Values Description

Ring_type BYTE N/A Unused

Ring_level BYTE 0-7 Ring gain

Addressing_info BYTE N/A Unused

Example D.7.18 IP_SET_RING_LEVEL_CNF

at+cip=6,a88b,0017,00-05-00 ip_set_ring_level_req
Provides a confirmation regarding the ringer gain level
Ring_type 00 request.
Ring_level 05- Req ring gain The reply contains the gain level adjusted and the status
Addressing_info 00 results.
The status results indicate whether the gain requested was
out of limits or a valid result.

Table 64. IP_SET_RING_LEVEL_CNF Parameters

Name Format Valid Values Description

Ring_type BYTE N/A Unused

Ring_level BYTE 0-7 Ring gain

Addressing_info BYTE N/A Unused

230 98-08901C39-B
 IP Over AT Commands List

Table 64. IP_SET_RING_LEVEL_CNF Parameters (Continued)

Name Format Valid Values Description

Req_status BYTE 0 less_than_min

1 same_level
2 more_than_max
3 level_is_changed

Example D.7.19 IP_LOW_VOLTAGE_IND

+CIP:8,a88c,00-05-00-03 ip_set_ring_level_cnf
Indicates any movement from one voltage level to another.
Ring_type 00
Due to hardware defense circuitry, the XCVR may not arrive
Ring_level 05 Ring gain at the points that are under voltage and over voltage.
Addressing_info 00
Req_status 03 level_is_changed .

Table 65. IP_LOW_VOLTAGE_IND Parameters

Name Format Valid Values Description

Low_voltage_state BYTE 1 Low voltage - Battery with "low batt active"

2 Normal volt - FULL battery - out of low batt

D.7.20 IP_GET_HF_VOLUME_REQ

Request for HF voice and ringer gain levels.

Table 66. IP_GET_HF_VOLUME_REQ Parameters

Name Format Valid Values Description

Addressing_info BYTE N/A Unused

Example D.7.21 IP_GET_HF_VOLUME_CNF

at+cip=2,A886,0017,00 ip_get_hf_volume_req
Returns the HF voice and ringer gain levels.
addressing_info 00

Table 67. IP_GET_HF_VOLUME_CNF Parameters

Name Format Valid Values Description

Voice_gain_level BYTE 0-7 Voice - HF gain level

Ring_gain_level BYTE 0-7 Ringer - HF gain level

Success BYTE 1 PASS

Addressing_info BYTE N/A Unused

98-08901C39-B 231
IP Over AT Commands List

Example D.7.22 IP_LTC_ERASED_IND

+CIP:8,a887,07--04--01-00 ip_get_hf_volume_cnf
Indicates to the TCU that there are no phone numbers in the
VOICE RING LTC (last ten call) list, meaning, the last dialed number was
Voice_gain_level 07 - Voice - HF gain level erased.

Ring_gain_level 04 - Ringer - HF gain level

Success 01
Addressing_info 00

Table 68. IP_LTC_ERASED_IND Parameters

Name Format Valid Values Description

Erased BYTE 0 Not erased

1 Erased

Reserved 3 BYTEs Padding added by compiler. Should be ignored by the

peripheral.

Example Reserved 00-00-4D

+CIP:8,a88a,01-00004D ip_ltc_erased_ind
01-ltc_erased D.8 IP PRIMITIVES CIP EXAMPLES
Erased 01 ltc_erased

Table 69. IP_CALL_STATUS_IND Ref. GSM-IP 7.3

Action Reaction Remark

Power up MS. Verify the The transceiver sends an ip_call_status_ind

Wait response:+CIP: 12,a827,000000000000
response is primitive to announce a change in the status of a
correct. voice calls that it controls.
Note that an IP may receive what it considers
duplicate call status indications, that is, primitives
with the same information.

MO voice call. Verify the 01 MO established.

Dial number. response is
Wait response: +CIP: 12,a827,000000010000 correct.

MO voice call. Verify the 02 Waiting to answer MO call.

Call is alerted. response is
Wait response: +CIP: 12,a827,000000020003 correct.

MO voice call. Call is answered. Verify the 04 Fully active.

Wait response: +CIP: 12,a827,002200040043 response is 22 Active call present.
correct.

MO voice call. Verify the 05 Releasing.

Releasing. response is 20 Active call state - previous call state.
Wait response: +CIP: 12,a827,002000050006 correct.

232 98-08901C39-B
 IP Over AT Commands List

Table 70. INDR_CTRL_STATE_IND Ref. GSM-IP 6.14

Action Reaction Remark

Power up MS. Verify the The transceiver sends an ip_indr_ctrl_state_ind

No +CIP:4,A825,XXXX should be send.
response is primitive to inform peripherals of display indicator
correct. state changes in the transceiver’s display. At
power-up all indicators are assumed to be off. No
ip_indr_ctrl_state_ind primitives are supplied to
indicate this initial state.

Power up MS. Verify the

Remove antenna response is
Wait response: +CIP:4,A825,0201 correct.
Insert antenna
Wait response +CIP:4,A825,0200

Power up MS. Verify the

Make call response is
Wait response +CIP:4,A825,0001 correct.
Release call
Wait response +CIP:4,A825,0000

Table 71. IP_STOP_REQ Ref. GSM-IP 6.6.

Action Reaction Remark

Power down MS. Verify the At power down the transceiver will inform
Wait response: +CIP: 0,A82F response is peripherals via the ip_stop_req primitive that the
correct. transceiver is powering down. A peripheral that
receives an ip_stop_req should perform its own
shut down procedure which may include saving
some information from the transceiver. After this
procedure is complete, the peripheral should
inform the transceiver via the ip_stop_cns
primitive that it is ready for the power down.

Table 72. ATTACHED_PERIPHERALS_IND Ref. GSM-IP 10.2.

Action Reaction Remark

Power UP MS Verify the CIP with ID=A88F replaces CIP with ID=A885.
Wait response: +CIP,XX, A88f,M1...Mn response is This is a TCG solution. The +CIP report should be
correct. produced for every attached peripheral.

98-08901C39-B 233
IP Over AT Commands List

Table 73. HF_AUDIO_STATUS_IND Ref. GSM-IP 10.4.

Action Reaction Remark

In HF mode press /release any buttons. Verify the Indication whenever any type of hands-free
Wait response: +CIP: 2,A888,01 response is audio is starting or ending.
+CIP:2,A888,00 correct: The purpose of this primitive is to let the TCU
2 "+CIP " know about pending HF audio, in order to
indicators for synchronize other audio related machines,
every button. such as entertainment radio and so on.
01 audio started
02 audio ended
Verify Side Tone
in SPKR.

Table 74. LTC_ERASED_IND Ref. GSM-IP10.11.

Action Reaction Remark

Make MO call. Verify the Indicates to the TCU that there are no phone
Empty LTC memory area via HS. response is numbers in the LTC (last ten call) list, meaning,
Wait response: +CIP: 2,A88A,01 correct. the last dialed number was erased.
00 Not erased
01 Erased

Table 75. SEEM_CARD_STATUS_IND Ref. GSM-IP 10.3.

Action Reaction Remark

Power-Up MS, wait response: Verify the response is correct. This primitive is sent to the IP
+CIP: 8,142B,(0-9)(0-9) 0 SUCCESS whenever it receives an update from
1 BAD_CODE the SIM manager in the mobile.
2 PIN_ENABLED
3 PIN_DISABLED
4 NOT_ALLOWED
5 BLOCKED
6 PERM_BLOCKED
7 NO_SECRET_CODE
8 OTHER_TECHNICAL_PROBLEM
9 SWITCH_BAND

234 98-08901C39-B

Table 76. SEEM_ACTIVATE_IND Ref. GSM-IP 9.1.
Action
Power-Up MS with normal SIM,
Wait response: +CIP: 4,1403,0004
Power-Up MS without SIM,
Wait response: +CIP:4,1403,0001
Power-Up MS with BAD SIM,
Wait response: +CIP: 4,1403,0002
Table 77. SEEM_ACTIVATE_IND Ref. GSM-IP 9.3.
Action
Power-Up MS with normal SIM, Wait
response: +CIP: 4,1402,0000
Power-Up MS without SIM, Wait
response: +CIP: 4,1402,0001
Power-Up MS with BAD SIM,
Wait response: +CIP: 4,1402,0002
Table 78. SEEM_DEACTIVATE_IND Ref. GSM-IP 9.2.
Action
Power-Up MS with normal SIM,
Remove SIM. Wait
response: +CIP: 4,1406,0001
Power-Up MS with BAD SIM,
Wait response: +CIP: 4,1406,0002
98-08901C39-B
Reaction
Verify the response is correct.
Verify the response is correct.
Verify the response is correct.
Reaction
Verify the response is correct.
Verify the response is correct.
Verify the response is correct.
Reaction
Verify the response is correct.
1 No SIM, active SIM card has
been removed.
Verify the response is correct.
2 Bad SIM, phone can no longer
talk to the active SIM card.
IP Over AT Commands List
Remark
This primitive is sent to the IP
whenever it received an update
from the SIM manager in the mobile.
Remark
0 SIM Available, active SIM has
answered to reset properly
1 No SIM, there is no active SIM
card
2 Bad SIM, phone cannot talk to the
active SIM
Remark
The transceiver sends a
seem_deactivate_ind primitive to
indicate that the active SIM card
has been removed or is no longer
usable because of a SIM card
communication failure. This
primitive always indicates that the
active SIM card is no longer usable.
235
IP Over AT Commands List

Table 79. SEEM_PIN_CHANGE_CNF Ref. GSM-IP 9.4.

Action Reaction Remark

Change PIN via HS menu. Verify the response is correct. Following a PIN change attempt,
Use correct PIN1 code. 0 Success, PIN code was changed. the transceiver forwards a
Wait response: +CIP: 8,1411,0000yyyy seem_pin_change_cnf primitive to
peripherals.

Change PIN via HS menu. Verify the response is correct.

Use wrong PIN1 code. 1 Bad Code, old PIN does not
Wait response: +CIP: 8,1411,0001yyyy match, not changed.

Change PIN via HS menu. Verify the response is correct.

Use wrong PIN1 code three times. 5 PIN Blocked, from third bad PIN
Wait response: +CIP:8,1411,0005yyyy code.

Table 80. SEEM_PIN_DISABLE_CNF Ref. GSM-IP 9.4.

Action Reaction Remark

Power-Up MS with PIN requested. Verify the response is correct. Following a PIN disable attempt, the
Set "PIN disabled" via HS menu. 0 Success, no PIN entry required at transceiver forwards a
Use correct PIN1 code. power-up. seem_pin_disable_cnf primitive to
Wait response: +CIP: 8,1413,0000yyyy peripherals.

Power-Up MS with PIN requested. Verify the response is correct.

Set "PIN disabled" via HS menu. 1 Bad Code, PIN does not match,
Use wrong PIN1 code. PIN not disabled.
Wait response: +CIP: 8,1413,0001yyyy

Power-Up MS with PIN requested. Verify the response is correct.

Set "PIN disabled" via HS menu. 3 PIN disabled, PIN entry was
Use correct PIN1. already disabled.
Set "PIN disabled" via HS menu again.
Wait no response.

Power-Up MS with PIN requested. Verify the response is correct.

Set “PIN disabled” via HS menu. 5 PIN Blocked, from third bad PIN
Use wrong PIN1 code three times. code.
Wait response: +CIP: 8,1413,0005yyyy

236 98-08901C39-B

Table 81. SEEM_PIN_ENABLE_CNF Ref. GSM-IP 9.4.
Action
Power-Up MS. Set "PIN enabled" via
HS menu.
Use correct PIN1 code.
Wait response: +CIP:8,1415,0000yyyy
Power-Up MS. Set "PIN enabled" via
HS menu.
Use wrong PIN1 code.
wait response: +CIP: 8,1415,0001yyyy
Power-Up MS.
Set "PIN enabled" via HS menu.
Use correct PIN1 code.
Try again to set "PIN enabled" .
Wait no response:
Power-Up MS.
Set "PIN enabled" via HS menu.
Use wrong PIN1 code three times.
Wait response: +CIP: 8,1415,0005yyyy
Table 82. SEEM_PIN_VERIFY_CNF Ref. GSM-IP 9.4.
Action
Power-Up MS with PIN1 required.
Enter correct PIN1.
Wait response: +CIP: 8,1417,0000yyyy
Power-Up MS with PIN required.
Enter wrong PIN.
Wait response: +CIP: 8,1417,0001yyyy
Power-Up MS with PIN required.
Enter wrong PIN 3 times.
Wait response: +CIP:8,1417,0002yyyy
98-08901C39-B
IP Over AT Commands List
Reaction Remark
Verify the response is correct. Following a PIN enable attempt, the
0 Success, PIN entry required at transceiver forwards a
power-up. seem_pin_enable_cnf primitive to
peripherals.
Verify the response is correct.
1 Bad Code, PIN does not match,
PIN not enabled.
Verify the response is correct.
2 PIN Enabled, PIN entry was
already enabled.
Verify the response is correct.
5 PIN Blocked, from 3rd bad PIN
code.
Reaction Remark
Verify the response is correct. Shortly after the transceiver
0 Success, PIN verification activates a SIM card it will check the
successful. PIN status of the SIM card. When
provided, the transceiver will
subsequently coordinate the
submission of the PIN, PUK, etc.
codes to the SIM card.
Verify the response is correct.
1 Bad Code, PIN verification failure,
not PIN blocked.
Verify the response is correct.
5 PIN Blocked, from 3rd PIN
verification failure.
237
IP Over AT Commands List
Table 83. SEEM_STATUS_CNF Ref. GSM-IP 9.4.
Action
Power-Up MS without PIN required.
Wait response: +CIP: 8,140F,0003yyyy
Power-Up MS with PIN required
Wait response: +CIP:8,140F,0002yyyy
Power-Up MS with PUK1 required
Wait response: +CIP: 8,140F,0005yyyy
Table 84. SEEM_UNBLOCKING_CNF Ref. GSM-IP 9.4.
Action
Power-Up MS with PUK1 required.
Enter wrong PUK1.
Wait response: +CIP: 8,1419,0001yyyy
Power-Up MS with PUK1 required.
Enter correct PUK1.
Wait response: +CIP: 8,1419,0000yyyy
Table 85. IP MUTE Ref. GSM-PCN.8.3.
Action
MS is in conversation.
AT+CIP=2,A822,0017,00
Wait response: +CIP: 4,A808,0100
MS is in conversation.
AT+CIP=2,A822,0017,00
Wait response: +CIP: 4,A808,0000
238
Reaction
Verify the response is correct.
3 PIN Disabled, no PIN entry
required.
Verify the response is correct.
2 PIN Enabled, PIN entry required.
Verify the response is correct.
5 PIN Blocked, user must enter
PUK to unblock.
Reaction
Verify the response is correct.
1 Bad Code, PUK verification failure,
not permanently blocked.
Verify the response is correct.
0 Success, PUK verification
successful.
Reaction
Verify the response is correct.
Check Mic muting before (off) and
after (on) AT command.
Verify the response is correct.
Check Mic muting before (on) and
after (off) AT command.
Remark
Shortly after the transceiver
activates a SIM card it will check the
PIN status of the SIM card. When
provided, the transceiver will
subsequently coordinate the
submission of the PIN, PUK, etc.
codes to the SIM card.
Remark
Shortly after the transceiver
activates a SIM card it will check the
PIN status of the SIM card. When
provided, the transceiver will
subsequently coordinate the
submission of the PIN, PUK, and so
on codes to the SIM card.
Remark
01 means microphone muting is
"on".
00 means microphone muting is
"off".
98-08901C39-B
 IP Over AT Commands List

Table 86. IP CALL DTMF Ref. GSM-PCN.7.7

Action Reaction Remark

Dial *054. Verify no response. Check the 1 Digit 1 will be sent as DTMF
Enter AT+CIP=14,A835,0017,00000000010031; stepping into menu. Check "1" signal.
+CIP=14,A835,0017,000001f4000031 displayed on HS screen.
No response.

Dial *054. Verify no response. Check the * Char. "#" will be send as DTMF
Enter AT+CIP=14,A835,0017,00000000010023; stepping into menu. Check "*" signal.
+CIP=14,A835,0017,000001f4000023 displayed on HS screen.
No response.

Dial *054. Verify no response. Check no "B" is incorrect value. Nothing

Enter AT+CIP=14,A835,0017,0000000001002B; stepping into menu. Check no will be sent as DTMF signal.
+CIP=14,A835,0017,000001f400002B "+" displayed on HS screen.
No response.

Table 87. IP ERROR Ref. GSM 07.07.7.10.

Action Reaction Remark

Enter: AT+CIP=10,A87E,0020,0003000000 00 Read error codes stored in

Wait response: +CIP: EEPROM.
16,A87F,0003FFFF0000ZZZZ FFFF Indicates success.
ZZZZ Code of the stored Error.

Enter: AT+CIP=10,A87E,0003000001 01 Clear error codes stored in

Waitresponse:+CIP:8,A87F,0003FFFF00000000 EEPROM.
FFFF Indicates success.
0000 No Error.

Table 88. IP GET HF VOLUME Ref. GSM-IP 10.8.

Action Reaction Remark

(The phone is in hands-free mode) Verify the response is correct. XX Voice - HF gain level
Enter: AT+CIP=2,A886,17,FF YY Ringer - HF gain level
Wait response: +CIP:8,A887,070401FF 01 PASS (phone is in hands-free
mode).

(The phone is in hands-free mode) Verify the response is correct. XX Voice - HF gain level
Enter: AT+CIP=6,A88B,0017,FF05FF YY Ringer - HF gain level
Enter: AT+CIP=2,A886,FF 00 FAIL (if the phone is not in
Wait response: +CIP:8,A887,XXYY05FF hands-free mode).

98-08901C39-B 239
IP Over AT Commands List

Table 88. IP GET HF VOLUME Ref. GSM-IP 10.8. (Continued)

Action Reaction Remark

(The phone is not in hands-free mode) Verify the response is correct. XX Voice - HF gain level
Enter: AT+CIP=2,A886,FF YY Ringer - HF gain level
Wait response: +CIP:8,A887,XXYY00FF 00 FAIL (if the phone is not in
hands-free mode).

240 98-08901C39-B
 5. GLOSSARY

E.1 GENERAL Abbreviation Description

This appendix provides definitions for terms and acronyms DataTAC A type of Motorola data communications
used in this document. system
DB Decibel
Abbreviation Description DBc Decibels relative to carrier
ACK Acknowledgement dBm Decibels mean; levels relative to 1 mW
ADC Analog-to-digital converter DCD Detailed circuit description
ALC Automatic level control DCS Digital cellular system (GSM in the
ANSI American National Standards Institute 1800MHz band)
AOC Automatic output control DDFTM Digital data fast, a technique that
combines an industry-standard error-
ASIC Application-specific integrated circuit
correction protocol with two
ATE Automatic test equipment compression algorithms (V.42bis and
BABT British Approval Board – MNP5) to provide data transfer rates up
Telecommunications to 33,600bps over a fixed 9,600bps
channel
BGA Ball grid array
Debounce Protection against feedback voltage
BER Bit error rate
Desense Loss of sensitivity from high ambient
BNC A type of connector used with coaxial noise
cable
DHFA Digital hands free adapter
bps Bits per second
DIN Deutsches Institut Für Normung
BSC Base station controller (for a network)
DISC Discriminator
C/R Card reader
DOS Disc operating system
CCR Type of miniature RF connector
DSC Digital speech control
Chebyshev filter A filter with very sharp cutoff
DTE Data terminal equipment, the user
CHRONOS Enhanced pendulum IC device
CLA Cigarette lighter adapter DTR Data terminal ready
CLK Clock DUT Device under test
CMOS Complementary metal oxide silicon DVM Digital volt meter
CNTL Control ECC Error correction and compression
COM Communications (port) EEPROM Electronically erasable, programmable,
CPU Central processing unit read-only memory
CQA Customer quality assurance EIA Electronic Industries Association (U.S.)
CNTL Control (key) EMA Embedded memory access (mode)
CSA California Safety Authority EMI Electromagnetic interference
CSD Circuit switch data EMMI Electrical man machine interface
DAC Digital-to-analog converter EPC File name suffix for modem
configuration files

98-08901C39-B 241
Glossary

Abbreviation Description Abbreviation Description

EPROM Erasable, programmable, read-only MPS Maintenance programming software
memory NAK Negative acknowledgment
ERP Effective radiated power NatSim Native mode simulation (software utility)
ESD Electrostatic discharge NCL Native control language (Motorola)
ESN Electronic serial number NiCad / NiCd Nickel-cadmium (battery technology)
EV Evaluation NiMH Nickel-metal-hydride (battery
EVB Evaluation board technology)
FCC Federal Communications Commission NPN Type of bipolar transistor
(U.S.) NSI Network systems integration
FET Field effect transistor NVRAM Non-volatile RAM
FIFO First in, first out OB Outbound
FNE Fixed network equipment OEM Original equipment manufacturer
FPC Flexible printed circuit op-amp Operational amplifier
FracN Fractional division synthesizer IC OSMT Type of miniature RF connector
FRU Field-replaceable unit Outbound Direction of wireless data originating
FSK Frequency shift keying from the fixed network destined for
GaAs Gallium arsenide, a semi-conducting either the host application(s) or the
material modem itself

GND Ground Palmtop A class of small, personal computing

devices
GPIB A type of ATE interface
PCA Printed circuit assembly (populated
GPRS General packet radio service board)
GSM Global system for mobile PCB Printed circuit board (bare board)
communications
PC Card A PCMCIA product
GTEM Gigahertz transverse electromagnetic
PCMCIA Personal Computer Memory Card
HCT High-speed CMOS technology International Association
Host The computer platform, or DTE PCS Personal communication service (GSM
HP Hewlett Packard in the 1900MHz band used in North
America)
I/O Input/Output
PDA Personal data assistant
IB Inbound
PDU Packet data unit
IC Integrated circuit or Industry Canada or
inductor-capacitor PIC Personal information communicator
Inbound Direction of wireless data originating PLL Phase-locked loop
from the host and/or modem to the fixed p/n Part number
network equipment
PMIT Packet modem integration test
IP Internet protocol
POST Power-on self test
IR Infrared
Ppm Parts per million
LED Light-emitting diode
PPP Point to point protocol
Li-ion Lithium ion (battery technology)
QFP Quad flat pack
LLI Logical link identifier; unit ID
R&D Research and development
LNA Low noise amplifier
RAM Random-access memory
MDC Mobile data communications protocol
(Motorola) Rayleigh A measure of multi-path fading depth of
a signal
ME Mobile equipment, for example, g18
RC Resistor-capacitor
MFR Multiple-frequency reuse
RF Radio frequency
MNP Microcom networking protocol

242 98-08901C39-B
 Glossary

Abbreviation Description Abbreviation Description

RFI Radio-frequency interference VCC Voltage common collector
RGxxx Cabling designation number VCO Voltage controlled oscillator
RLP Radio link protocol, a sophisticated VDD Voltage direct drain
error-correcting system Vpp Voltage peak to peak
RMA Return material authorization VSRAM Battery backup voltage for SRAM
RNC Radio network controller VSWR Voltage standing-wave ratio
RPM Radio packet modem Wireline Communications over a direct, physical
RS-232 The EIA standard for a serial data link
interface XIP Execute in place
RSSI Received signal strength indicator ZIF Zero insertion force
RTU Radio training utility
Rx Receive or reception
SAP0 A specific service access point E.2 SHORT MESSAGE SERVICE ABBRE-
Schottky diode A diode with low forward voltage drop
VIATIONS
and fast switching The relevant specifications are given in parentheses.
SCR Standard context routing (*) indicates a common GSM abbreviation and (-) indicates
SDK Software developers kit a general abbreviation. These abbreviations are often
prefixed with “TP-”, which refers to “Transport Protocol”.
SDU Service data unit
SFR Single-frequency reuse Abbreviation Description
SINAD Ratio (measured in dB) of signal to CM Call Management (*)
noise-plus-distortion
CS CauSe (-)
SMA Sub-miniature connector
DA Destination Address (-)
SMB Sub-miniature connector
DCS Data Coding Scheme (03.40)
SMS Short message service
DI Dialogue Identifier TCAP
SNR Signal-to-noise ratio
GMSCA Gateway MSC Address
SPDT Single pole, double throw (switch)
HLR Home Location Register (*)
SPI Serial peripheral interface
IMSI International Mobile Subscriber
SRAM Static random-access memory (static Identity (*)
RAM)
MAL MSIsdn-ALert (03.40)
TA Terminal adapter, equivalent to DCE, for
example, the g18. MMS More Messages to Send (03.40)

TBD To be determined MR Message Reference (03.40)

TE Terminal equipment, equivalent to DTE, MS Mobile Station (*)

for example, a laptop computer or OEM MSC Mobile services Switching Centre (*)
device.
MSI Mobile waiting Set Indication (03.40)
TNC Industry standard connector type
MSIsdn Mobile Station ISDN number (*)
Transorb Transient absorber
MSM More Short Messages (09.02)
TTO Transmitter turn-on time
MSRN Mobile Station Roaming Number (*)
Tuple An element of a database relation,
MT Message Type (04.11)
consisting of an identifier of an entity
and its attributes MTI Message Type Indicator (04.11)
Tx Transmit or transmission MWS Message Waiting Set (03.40)
Type III Reference to a PC card form factor OA Originating Address (-)
UART Universal asynchronous receiver / OC Operation Code (09.02)
transmitter PCI Protocol Control Information (-)
UL Underwriters Laboratories PDI Protocol DIscriminator (*)

98-08901C39-B 243
Glossary

Abbreviation Description
PRI PRIority (03.40)
RCT ReCeption Time (03.40)
REA REcipient Address (03.40)
RL ReLay function (04.11)
RP Reply Path (03.40)
SC Service Centre (03.40)
SCA Service Centre Address (03.40)
SCTS Service Centre Time Stamp (03.40)
SM Short Message (03.40)
SM-AL Short Message Application Layer
(03.40)
SME Short Message Entity (03.40)
SMI Short Message Identifier (03.40)
SM-RL Short Message Relay Layer (03.40,
04.11)
SMS-GMSC Short Message Service Gateway MSC
(03.40)
SMS-IWMSC Short Message Service InterWorking
MSC (03.40)
SoR Status of Report (03.40)
SM-TL Short Message Transfer Layer (03.40)
SRI Status Report Indication (03.40)
SRR Status Report Request (03.40)
ST STatus (03.40)
TCAP Transaction Capabilities Application
Part (-)
TID Transaction IDentifier (*)
TPDU Transport Protocol Data Unit (-)
UD User Data (-)
UDL User Data Length (03.40)
VLR Visitor Location Register (*)
VP Validity Period (03.40)
VPF Validity Period Format (03.40)

244 98-08901C39-B
 6. INDEX

AT Command Listing 80
A AT+CAOC, Charge Advice 81
AT+CBAND, Changing Band 136
Acceptance Analysis on a Sample Data Set 202
AT+CBAUD, Setting the Baud Rate 137
Address
AT+CBST, Selecting Bearer Service Type 107
Selecting Type 106
AT+CCFC, Call Forwarding Number Conditions 82
Alternate EMI Reduction Methods
AT+CCWA, Call Waiting 83
Clock Pulling 204
AT+CEER, Extended Error Report 121
Analog Audio
AT+CESP, Entering SMS Block Mode 134
Audio Downlink (Speaker) 19
AT+CGACT, PDP Context Activation/Deactivation
Audio Uplink (MIC) 18
Request 143
Levels 18
AT+CGATT, GPRS Attach/Detach Request 144
Tones 19
AT+CGCLASS, GPRS MS Class 140
Voice 19
AT+CGDCONT, Defining the PDP Content 141
With Hands Free 20
AT+CGMI, Requesting Manufacturer Identification 108
Without Hands Free 18
AT+CGMM, Requesting Model Identification 109
Answering
AT+CGMR, Requesting Revision Identification 109
Voice Call 76
AT+CGPADDR, Showing the PDP Address 139
Antenna 205
AT+CGPRS, GPRS Coverage 138
Cable Assembly 64
AT+CGQMIN, Quality of Service Provider 142
Cable Routing 205
AT+CGQREQ, Defining a Requested Quality of Service
Connections 197
Profile 145
Connector 64
AT+CGQREQ, Modifying a Requested Quality of
Considerations 24
Service Profile 145
External Remote 25
AT+CGQREQ, Removing a Requested Quality of
External Removable 25
Service Profile 145
Field Strengths from the Antenna 205
AT+CGSN, Requesting Product Serial Number Identifi-
Fixed Devices 25
cation 110
GPS Antenna 64
AT+CHLD, Call Related Supplementary Services 84
GSM Antenna 63
AT+CHUP, Hanging Up Calls 110
Hardware 63
AT+CIMI, Requesting International Mobile Subscriber
Installation Safety xvii
Identity (IMEI) 146
Interactions 205
AT+CIP, IP Primitive Over AT Command 149
Internal 24
AT+CIPE, ENABLE+CIP AT Command 149
Performance 24
AT+CKPD, Keypad Control 123
Portable Devices 24
AT+CLCC, List Current Calls 89
Safety 24
AT+CLCK, Facility Lock 91
Systems 24
AT+CLIP, Calling Line Identification Presentation 92
Test Methods 25
AT+CLIR, Call Line Identification Restriction 93
Application Software
AT+CMEC, Mobile Equipment Control Mode 130
Network Configuration 70
AT+CMEE, Report Mobile Equipment 94
Software Driver Configuration 70
AT+CMER, Mobile Equipment Event Reporting 131
Testing 70
AT+CMGD, Deleting SMS Message 111
AT+CMGF, Message Format 113

98-08901C39-B 245
Index
AT+CMGL, Listing Messages 114
AT+CMGR, Reading Messages 115
AT+CMGS, Sending an SMS Message 95
AT+CMGW, Writing Messages 134
AT+CMOD, Calling Mode 125
AT+CMSS, Send Message from Storage 153
AT+CMUX, Multiplexing Mode 172
AT+CNMA, DTE Confirming the Previous Message 135
AT+CNMI, New Message Indications to TE+CNMI 128
AT+CNUM, Subscriber Number 96
AT+COPS, Operator Selection 97
AT+CPAS, Phone Activity Status 115
AT+CPBF, Finding Phone Book Entries 132
AT+CPBR, Reading Phone Book Entries 116
AT+CPBS, Selected Phone Book Memory Storage 99
AT+CPBW, Writing Phone Book Entries 101
AT+CPIN, Enter Pin 103
AT+CPMS, Preferred Message Storage 117
AT+CPOL, Preferred Operator List 148
AT+CPWD, Changing the Password 151
AT+CR, Service Reporting Control 126
AT+CRC, Cellular Result Codes 127
AT+CREG, Network Registration 105
AT+CRLP, Radio Link Protocol 126
AT+CRSM, Restricting SIM Access 147
AT+CRTT, Selecting the Ring Tone 150
AT+CSCA, Service Center Address 118
AT+CSCB, Select Cell Broadcast Message Types 162
AT+CSCR, SIM Card Reader 169
AT+CSCS, Selecting TE Character Set 119
AT+CSMP, Set SMS SIM Parameters 157
AT+CSMS, Selecting the Message Service 120
AT+CSQ, Signal Quality 121
AT+CSTA, Selecting Type of Address 106
AT+CSVM, Set VoiceMail Parameters 159
AT+CTFR1, Diverting an Incoming Call to the Voice
Mail 135
AT+FCLASS, Selecting a Mode 124
AT+GCAP, Requesting Complete Capabilities List 124
AT+IPR, Setting and Saving the Baud Rate 171
AT+MCELL, Motorola Cell Description 169
AT+MCSAT, Motorola Control SMS Alert Tone 166
AT+MCWAKE, DTE Wake Line Control Command 153
AT+MECC, Motorola Extended Characters Check 168
AT+MFS, Motorola Frequency of Search 161
AT+MMGA, Changing the Message Attributes 155
AT+MMGL, Message List 154
AT+MMGR, Read Message 154
AT+MSCTS, Motorola Sleep CTS Control 155
AT+MTCTS, CTS Line Test Command 152
AT+MTDTR, DTR Line Test Command 152
AT+PT42 172
ATD, Dialing 80
Fax AT Commands 151
246
AT Commands 73
Answering a Voice Call 76
AT Command Listing 80
Basic 45
Establishing a Voice Call 75
Establishing GPRS PDP Context 78
Feedback from the System 74
Finding a Phone Book Entry 76
Phone Book Function 77
PIN and PUK Code Entry 73
Reading a Phone Book Entry 77
Sending an SMS in PDU Mode 78
Writing a Phone Book Entry 77
AT+CAOC, Charge Advice 81
AT+CBAND, Changing Band 136
AT+CBAUD, Setting the Baud Rate 137
AT+CBPF, Finding Phone Book Entries 132
AT+CBST, Selecting Bearer Service Type 107
AT+CCFC, Call Forwarding Number and Conditions 82
AT+CCWA, Call Waiting 83
AT+CEER, Extended Error Report 121
AT+CESP, Entering SMS Block Mode 134
AT+CGACT, PDP Context Activation/Deactivation
Request 143
AT+CGCLASS, GPRS MS Class 140
AT+CGDCONT, Defining the PDP Content 141
AT+CGMI, Requesting Manufacturer Identification 108
AT+CGMM, Requesting Model Identification 109
AT+CGMR, Requesting Revision Identification 109
AT+CGPADDR, Showing the PDP Address 139
AT+CGPRS, GPRS Coverage 138
AT+CGQMIN, Quality of Service Provider 142
AT+CGSN, Requesting Product Serial Number
Identification 110
AT+CHLD, Call Related Supplementary Services 84
AT+CHUP, Hanging Up Calls 110
AT+CIMI, Requesting International Mobile Subscriber
Identity (IMEI) 146
AT+CIP, IP Primitive Over AT Command 149
AT+CIPE, ENABLE+CIP AT Command 149
AT+CKPD, Keypad Control 123
AT+CLCC, List Current Calls 89
AT+CLCK, Facility Lock 91
AT+CLIP, Calling Line Identification Presentation 92
AT+CLIR, Calling Line Identification Restriction 93
AT+CMEC, Mobile Equipment Control Mode 130
AT+CMEE, Report Mobile Equipment 94
AT+CMER, Mobile Equipment Event Reporting 131
AT+CMGD, Deleting SMS Message 111
AT+CMGF, Message Format 113
AT+CMGL, Listing Messages 114
AT+CMGR, Reading Messages 115
AT+CMGS, Sending an SMS Message 95
AT+CMGW, Writing Messages 134
AT+CMOD, Calling Mode 125
98-08901C39-B
 Index

AT+CMSS, Send Message from Storage 153 Audio Uplink (MIC) 18

AT+CMUX, Multiplexing Mode 172
AT+CNMA, DTE Confirming the Previous Message 135
AT+CNMI, New Message Indications to TE+CNMI 128 B
AT+CNUM, Subscriber Number 96
Band Changing 136
AT+COPS, Operator Selection 97
Band Selections 197
AT+CPAS, Phone Activity Status 115
Basic AT Commands 45
AT+CPBR, Reading Phone Book Entries 116
Basic Model Overview 7
AT+CPBS, Selected Phone Book Memory Storage 99
g18 Board Only - Horizontal 8
AT+CPBW, Writing Phone Book Entries 101
g18 DV Slim 7
AT+CPIN, Enter Pin 103
g18 DVG Slim 8
AT+CPMS, Preferred Message Storage 117
Basic Operations 29
AT+CPOL, Preferred Operator List 148
Commencing Voice Communication 30
AT+CPWD, Changing the Password 151
Enabling Cell Broadcast (CB) Reception 30
AT+CR, Service Reporting Control 126
Making a CSD - Data Call 30
AT+CRC, Cellular Result Codes 127
Making a Voice Call 29
AT+CREG, Network Registration 105
Receiving a Data Call 30
AT+CRLP, Radio Link Protocol 126
Receiving a Voice Call 29
AT+CRSM, Restricting SIM Access 147
Setting Up the g18 in CSD Mode 31
AT+CRTT, Selecting the Ring Tone 150
Baud Rate
AT+CSCA, Service Center Address 118
Saving 171
AT+CSCB, Select Cell Broadcast Message Types 162
Setting 171
AT+CSCR, SIM Card Reader 169
Baud Rate Setting 137
AT+CSCS, Selecting TE Character Set 119
Bearer Service Type
AT+CSMP, Set SMS SIM Parameters 157
Selecting 107
AT+CSMS, Selecting the Message Service 120
Binary Data
AT+CSQ, Signal Quality 121
Receiving via SMS 35
AT+CSTA, Selecting Type of Address 106
Sending via SMS 35
AT+CSVM, Set VoiceMail Parameters 159
AT+CTFR1, Diverting an Incoming Call to the Voice Mail
135
AT+FCLASS, Selecting a Mode 124
C
AT+GCAP, Requesting Complete Capabilities List 124 Cable Assembly
AT+IPR, Setting and Saving the Baud Rate 171 Antenna 64
AT+MCELL, Motorola Cell Description 169 Cable Routing
AT+MCSAT, Motorola Control SMS Alert Tone 166 Antenna 205
AT+MCWAKE, DTE Wake Line Control Command 153 Calibration Tools and Equipment 72
AT+MECC, Motorola Extended Characters Check 168 Call Control Interface Primitives 216
AT+MFS, Motorola Frequency of Search 161 Background 216
AT+MMGA, Changing the Message Attributes 155 Call Restrictions 216
AT+MMGL, Message List 154 Call Forwarding 32
AT+MMGR, Read Message 154 Conditions 82
AT+MSCTS, Motorola Sleep CTS Control 155 Number 82
AT+MTCTS, CTS Line Test Command 152 Call Related Supplementary Services 84
AT+MTDTR, DTR Line Test Command 152 Call Status Indication Primitives 216
AT+PT42 172 Call Waiting 32, 83
ATD, Dialing 80 Calling Line Identification Presentation 92
Attached Peripherals Primitives 228 Calling Line Identification Restriction 93
Audio Circuit Considerations 17 Calling Mode 125
Analog Audio Levels 18 Capabilities List 124
Analog Audio With Hands Free 20 Card Reader
Analog Audio Without Hands Free 18 SIM 169
Digital Audio 17 Cellular Result Codes 127
Audio Connections 197 Channel Interference
Audio Downlink (Speaker) 19 Probability of 203

98-08901C39-B 247
Index

Characters Check Data Communication 28

Extended 168 CSD 29
Charge Advice 81 GPRS 28
Class Indicator Primitives 210 Data Levels 21
Clock Pulling 204 Data Port Considerations 21
Commands Data Levels 21
AT 73 DTR Line and DCD Line 22
Basic AT 45 Setting the Baud Rate 22
CTS Line Test 152 Description
DTE Wake Line Control 153 Cell 169
DTR Line Test 152, 172 Desense 199
ENABLE +CIP AT 149 Acceptance Analysis on a Sample Data Set 202
Error Correction and Compression 49 Antenna 205
Fax AT 151 Definition 199
Fax Class 1 49 Measurement Techniques 200
GPRS 58 Methods of Controlling Emissions 203
IP Primitive Over AT 149 Noise Sources 199
V.25TER Used With GSM 53 Performance Goals 201
Conference Calls 32 Prediction of Sources 202
Configuration Setup and Audio Routing in g18 27 Receiver Susceptibilities 200
Configuring RF Network Issues 204
Modem in WinFax 43 Scenarios 203
Connecting Summary 205
3788 Handset to the g18 26 Testing 70
Connections Design Considerations 13
Antenna 197 Antenna Considerations 24
Audio 197 Audio Circuit Considerations 17
Customer 197 Connecting the 3788 Handset to the g18 26
Power 197 Data Port Considerations 21
RS232 197 ESD Considerations 23
SIM 197 GPS Considerations 26
Connector Mechanics - Mounting the g18 25
Antenna 64 Power Supply Considerations 13
Connector Description SIM Card Considerations 23
EV Board Issue P4 174 Developer’s Kit 64
EV Board Issue P5 177 Development and Service Aids 4
Country Requirements xv Development Test Environment 3
CSD - Data Call Diagnostic Utility
Making 30 Equipment Test Setup 72
CTS Line Test Command 152 Quality Assurance Testing 71
Customer Connections 197 Testing 71
Digital Audio 17
DIP Switch Settings 198
D Display Indicator Primitives 215
DSC BUS IP Primitive Over AT Services +CIP 207
d15 Differences from g18 9
DTE Wake Line Control Command 153
AT Commands 10
DTR Line and DCD Line 22
Data Options 9
DTR Line Test 152, 172
General 9
GPRS ST Commands 12
Mechanical 9
Power 9
E
Data Call EMI
Receiving 30 Reduction Methods 204
Testing 70

248 98-08901C39-B
 Index

Emissions Field Strengths from the Antenna 205

Methods of Controlling 203 Field-Testing 4
Enable IP Over AT Services +CIPE 207 Final Assembly Test 71
Enabler Functions Final Test Environment 4
Testing 69 Fix Dialing Phone Book 44
Enabling Cell Broadcast (CB) Reception 30 Fixed Devices 25
Engineering Support Fixed-Mount Usage 25
Integrating 4 Flow Control Set to Hardware Flow Control 31
Enter Pin 103 Receiving Data 31
Environmental Sending Data 31
Issues 5 Flow Control Set to None 32
Specifications 188 Receiving Data 32
Equipment Sending Data 32
Modem Test 5 Flow Control Set to Xon/Xoff 31
Traditional Shop 5 Receiving Data 32
Wireless Verification Equipment 5 Sending Data 31
Equipment Test Setup 72
Calibration Tools and Equipment 72
Loop-back Test 72 G
Modem Test Setup 72
g18
Error Correction and Compression Commands 49
PC Loader Application 181
Error Messages
Setting Up in CSD Mode 31
SMS 36
g18 Current Consumption 13
Error Report
Turning the Unit On or Off 14
Extended 121
Turning the Unit On or Off Using the ON/OFF Pin 14
ESD
Turning the Unit On Using the TS Pin 14
Considerations 23
g18 Differences from d15 9
Handling Precautions 5
AT Commands 10
ETSI 07.05 Standard (SMS) 55
Data Options 9
ETSI 07.07 Standard 49
General 9
European Union and EFTA xv
GPRS ST Commands 12
EV Board Issue P4 173
Mechanical 9
Connector Description 174
Power 9
Jumper Description 175
g18 DV Board Only - Horizontal 8
EV Board Issue P5 176
g18 DV Slim 7
Connector Description 177
g18 DVG/Slim 8
S3 Dip Switch Description 179
g18 Evaluation Board 173
Extended Error Report 121
EV Board Issue P4 173
External Antenna 25
EV Board Issue P5 176
External Remote Antenna 25
g18 PC Loader Application 181
Options 181
g18 Type Certification Identifications xvii
F General Precautions 5
Facility Lock 91 Generate DTMF Signalling Primitives 218
Fastening GPRS
DIN Units 26 Attach/Detach Request 144
Units with Housing 26 Commands 58
Fax Coverage 138
AT Commands 151 MS Class 140
Class 1 Commands 49 PDP Context 43, 78
Communication 29 GPS
Sending 43 Antenna 64
Feedback Considerations 26
System 74 GSM Antenna 63

98-08901C39-B 249
Index

IP_SET_RING_LEVEL_REQ 230
H
Hanging Up Calls 110
Hardware 63
J
Antennas 63 Jumper Description
Designing Platform 3 EV Board Issue P4 175
Developer’s Kit 64 Jumper Settings 198
Developing and Validating 3
Host Interface 63
Vendor Contacts 64 L
Hardware Integration
Language Packs 194
Specific Tests 69
List Current Calls 89
Testing 69
Loop-back Test 72
Testing Enabler Functions 69
Getting Started 72
Hook-switch Status Indicator Primitives 219
Measuring Additional Parameters 72
Host Interface 63
Interface Cable 63
Modem I/O Connector 63
M
Manufacturer Identification, Requesting 108
I Measurement Techniques 200
Alternate Measurement Method 201
Idle SIM Card Notification Primitives 223
Packet Modem Integration Tester (PMIT) 200
Installing
Preparing the Device Under Test 201
Modem Driver 43
Mechanics
Integration
Fastening DIN Units 26
MUX 59
Fastening Units with Housing 26
MUX Requirements 59
Fixed-Mount Usage 25
Interface Cable 63
Message
International Mobile Subscriber Identity 146
Attributes 155
IP Over AT Commands List 207
Confirming Previous 135
IP Primitives CIP Specifications 210
Format 113
Attached Peripherals Primitives 228
List 154
Call Control Interface Primitives 216
Listing 114
Call Status Indication Primitives 216
Model 2
Class Indicator Primitives 210
Read 154
Display Indicator Primitives 215
Reading 115
Generate DTMF Signalling Primitives 218
Send from Storage 153
Hook-switch Status Indicator Primitives 219
Writing 134
Idle SIM Card Notification Primitives 223
Message Service
IP_HF_AUDIO_STATUS_IND 229
Selecting 120
IP_LOW_VOLTAGE_IND 231
Message Types
IP_SET_RING_LEVEL_CNF 230
Cell Broadcast 162
IP_SET_RING_LEVEL_REQ 230
Methods of Controlling Emissions
Microphone Mute Primitives 221
Alternate EMI Reduction Methods 204
Phone Book Related Primitives 213
Shielding Approach 203
Power Down Primitives 213
MIC 18
SEEM Interface Primitives 221
Microphone Mute Primitives 221
SIM Card Activation Notification Primitives 224
Mobile Equipment Control Mode 130
SIM Card Deactivation Notification 223
Mobile Equipment Event Reporting 131
SIM Card Security Notifications 224
Mode
IP Primitives Supported by CIP 209
Selecting 124
IP_HF_AUDIO_STATUS_IND 229
Model Description
IP_LOW_VOLTAGE_IND 231
Basic Overview 7
IP_SET_RING_LEVEL_CNF 230
d15 and g18 Differences 9

250 98-08901C39-B
 Index

General 7 Parameters
Introduction 7 Set SMS SIM 157
Model Identification, Requesting 109 Set VoiceMail 159
Modem Parts
Configuring in WinFax 43 Requirements 4
I/O Connector 63 Password
Installing Drivers 43 Changing 151
Test Equipment 5 PDP
Test Setup 72 Address 139
Modem Communication Modes 27 Content 141
Data Communication 28 Context Activation/Deactivation Request 143
Fax Communication 29 Performance
SMS Communication 29 Specifications 188
Voice Communication 27 Performance Goals 201
MUX Integration 59 Emission Level Goals 202
Architecture 61 Radio Performance Capabilities 201
Close Service 59 Phone Activity Status 115
Data Transfer 59 Phone Book
Open Service 59 Finding an Entry 76, 132
Requirements 59 Function 77
Supported Protocol Services 60 Reading an Entry 77, 116
System Behavior 60 Related Primitives 213
Two Channel Limitation 59 Writing an Entry 77, 101
Mux Integration Physical Specifications 188
User APIs 62 PIN Code
MUX Service Entry 73
Close 59 Number 44
Open 59 PMIT Data Presentation 200
Portable Antenna
External Antenna 25
N Portable Devices 24
External Remote Antenna 25
Network
Internal Antenna 24
Configuration 70
Power Connections 197
Registration 105
Power Down Primitives 213
Noise Sources
Power Supply
Desense 199
Losses 13
North American GSM Type Certification xvi
Options 3
Power Supply Considerations 13
g18 Current Consumption 13
O How and When to Wake Up the Unit 16
OEM Service Depot Repair 71 Power Supply Losses 13
Operator Selection 97 Precautions
ESD Handling 5
General 5
P Prediction of Sources 202
Desense Scenarios 203
P4 Evaluation Board
Probability of Channel Interference 203
Connector Description 174
Preferred Message Storage 117
Jumper Description 175
Preferred Operator List 148
P5 Evaluation Board
Preparing the Device Under Test 201
Connector Description 177
Primitives
Dip Switch Description 179
Attached Peripherals 228
Packet Modem Integration Tester (PMIT) 200
Call Control Interface 216
Data Presentation 200
Call Status Indication 216

98-08901C39-B 251
Index

Class Indicator 210 Regulatory Requirements xiv

Display Indicator 215 Country Requirements xv
Generate DTMF Signalling 218 European Union and EFTA xv
Hook-switch Status Indicator 219 Full-Product Certification xv
Idle SIM Card Notification 223 g18 Type Certification Identifications xvii
IP Supported by CIP 209 North America GSM Type Certification xvi
Microphone Mute 221 Safety xvii
Phone Book Related 213 Remote Diagnostic Functionality
Power Down 213 Defining 2
Request/Confirm 209 Report Mobile Equipment 94
SEEM Interface 221 Request/Confirm Primitives 209
SIM Card Deactivation Notification 223 Requirements
SIM Card Security Notifications 224 Parts and Tools 4
Unsolicited 209 Resource Assistance 4
Problem Resolution 71 Result Codes
Product Cellular 127
Approving 4 Revision Identification
Field-Testing 4 Requesting 109
Installing 4 RF Network Issues 204
Planning 1 Ring Tone
Testing 4 Selecting 150
Product Serial Number Identification 110
Protocol Services
Supported 60 S
PUK Code Entry 73
S3 Dip Switch Description
EV Board Issue P5 179
Safety xvii
Q Antenna Installation xvii
Quality Assurance Testing 71 User Operation xvii
Quality of Service Profile Sample Data Set
Defining 145 Acceptance Analysis 202
Modifying 145 Search
Removing 145 Frequency 161
SEEM Interface Primitives 221
Sending
R Binary Data via SMS 35
Fax 43
Radio
SMS 32, 95
Link Protocol 126
SMS Fax 43
Performance Capabilities 201
SMS in CSD Mode 34
Receiver Susceptibilities 200
SMS in PDU Mode 32, 78
Receiving
SMS PDU-Mode Waveforms 34
Binary Data via SMS 35
Sending Data
SMS 34
Flow Control Set to Hardware Flow Control 31
SMS CSD Mode Wave Forms 35
Flow Control Set to None 32
Receiving Data
Flow Control Set to Xon/Xoff 31
Flow Control Set to Hardware Flow Control 31
Service Center Address 118
Flow Control Set to None 32
Service Provider Quality 142
Flow Control Set to Xon/Xoff 32
Service Reporting Control 126
Regulatory Approval
Service Strategy
Obtaining 3
Defining 2
Regulatory Compliance
Shielding Approach 203
Testing 70
Benefits 204
Components of Shield Design 204
Signal Quality 121

252 98-08901C39-B
 Index

SIM Testing 69
Connections 197 Desense 70
Restricting Access 147 Diagnostic Utility 71
SIM Card EMI 70
Activation Notification Primitives 224 Hardware Integration 69
Deactivation Notification 223 Product 4
Security Notifications 224 Stages 69
Support 23 Testing Stages
Sleep Control Application Software 70
CTS 155 Desense and EMI 70
SMS End User Problem Resolution 71
Block Mode 134 Final Assembly 71
Deleting a Message 111 Hardware Integration 69
Error Messages 36 OEM Service Depot Repair 71
Sending in PDU Mode 78 Regulatory Compliance 70
SMS Alert Tone Tones 19
Control 166 Tools
SMS Communication 29 Requirements 4
Block Mode 29 Traditional Shop Equipment 5
PDU Mode 29 Turning the Unit On or Off 14
Text Mode 29 Using the ON/OFF Pin 14
Software Driver Configuration 70 Using the TS Pin 14
Software Interface 27
Basic AT Commands 45
Basic Operations 29 U
Call Forwarding 32
Unsolicited Primitives 209
Call Waiting 32
Usage Model
Conference Calls 32
Developing 1
Error Correction and Compression Commands 49
ETSI 07.05 Standard (SMS) 55
ETSI 07.07 Standard 49
Fax Class 1 Commands 49
V
GPRS Commands 58 V.25TER Commands Used With GSM 53
Modem Communication Modes 27 Vendor Contacts 64
Sending an SMS 32 Voice 19
Sending and Receiving Data in Different Flow Controls Call Answering 76
31 Call Establishing 75
V.25TER Commands Used with GSM 53 Voice Call
Source Antenna 3 Making 29
Speaker 19 Receiving 29
Specific Tests Voice Communication 27
Hardware Integration 69 Commencing 30
Specifications 187 Configuration Setup and Audio Routing in g18 27
Environmental 188 Voice Connectivity 27
Performance 188 Voice Mail
Physical 188 Diverting an Incoming Call 135
Subscriber Number 96
Supporting Application Software 3
System Feedback 74 W
Waking Up the Unit 16
WinFax
T Configuring Modem 43
TE Character Set Wireless Verification Equipment 5
Selecting 119 Writing 77

98-08901C39-B 253
Index

254 98-08901C39-B
 SCHEMATIC DIAGRAMS,
LAYOUTS AND
PARTS LISTS
Contents
Each of the schematics shown below is accompanied by its layout and parts list:

P4 Evaluation Board - Model FTN8071A GO>

Top Hierarchy GO>
Audio GO>
Interface GO>

P5 Evaluation Board - Model FTN8071A/B GO>

Top Hierarchy GO>
Audio GO>
Interface GO>

Each diagram and layout contains two Print buttons: one of them will print the entire diagram or
schematic on a plotter, and the other will split it so it can be printed on a standard office printer.
P4 EVALUATION BOARD - TOP VIEW 8486452t01_p4 Model FTN8071A Print
SIM 16 2
2 CR9 CR1 CR11 CR8 CR7 CR6 CR5 CR4 CR3 CR2 CR10
P8

R59
P2

J114
R63
R55

R53
R60

R58

R56
R57
5

1
9

1 15

S1
J5 P12
LED

P6
P7

P9
P1
C9545

R2565 C9543

C9565
6

U979 P10 J123

1

C9544

P5
C9570

P3 J126
C9575
C9574

C9546

C9560 L16

R2595

J125

J12 J120
SH1
J121
C112
L10
C110

J4
C9550

C9549

C2 R31
R2588
C9555

R38
C35
C34

R17 C24
C30
C37
C36
C29

L15
R4

R2564 C25
R27 C8
C32
C33

C38
R26 R25
C28
C68

C27

U3 R24 C9540 C12 C39

L2
C15
R33

R2587

C3 C52
L4 R21 C75 C40
C26
C104

C1 C41 R30
C9553 C76 R2 C103
C9561

R50 C4 R32 R84 C45

C13
R3 C48 U4
C46 J124
R29 R52
C9567

C43
R35

C9
C116

C51 C49 R28

C42
SW2 C9563
C62 C77 C50 R18
R15
R22

R23 C5 L6 L5
C44

C9556 C9537
C105
R77

C6 C14
C47

C79
U5
L12 R19
C9564
U987

C117
R78
C81

C82

C11
C9554

R1069 C9539
R2473

R1057

J118
C9552

C9206
C60
R2527

C9192 R2550
C9378

U985
R2519
C9551

C9542

R2551
R2552
L14
U978
U981
C9365

R1056

R2575 R83
R2521

C9409

U988
J127
C9536

R1104

C83 U986
R2569
C9573
C9538

U980
R2553
R1068

C9386 R2518
C9569
Q38
J122
8 8
C73
C74

C72

D3
L1
C101

C100
C86
C88
C93

C95
C94

C91

C84

C99
C96
C90

C102
C92

C97

C98
C87
C89

1 1
C71
C85
L7 J10
C115

C114

C9559 F1 J115
J111 D1
1 J3 S2
C78
J13
C80

L3 J2 J1

OL 79B02965C16-O
SHOWN FROM SIDE 1
OL 79B02965C18-O
 8486452t01_p4

P4 EVALUATION BOARD - BOTTOM VIEW

Q15
Q4 Q11 Q22 Q21 Q20 Q19
R67
R64

Q23 Q18
R68 Q14
R79
R66

Q16 R65 C59

R2570
R61
R62

C9568
VR5 VR6
Q3
C61
Q25 U984 VR2 VR9
R2572

R82 Q34 Q35

R36 VR3 VR7
R2571

R2574
R2558

Q28
VR4 VR8
R2561
R2566

R2568
R2578

R2577
Q37 U991 Q29
R2559

R2557
R2579

R2582
Q36 R2573
R2556
R2576
R2560
L17
Q30 Q32
R2583 C9562
R2580

C9558 U990
R2585

R2586

C9571
C9581

C9580

C111
C9566 C9572

L13
U989

L11
C9578

C9577
C113
C9576

C106
R85

C70
L8
R2554
C9547

C9548

U983 Q27 D2

R70 R69 Q17

C9579

C7
Q26 C9541
R2597
R2594
R2593
R20

R2596

D5
C9201
R2598

C9241

R2590
R2589

D4
C9185 R1098 R2563

U992
VR10

C9208

C9219
R2471

R2469

C9204
C9215

U982
C9190

C9228
C9205

R2468

R2470

SHOWN FROM SIDE 2

Model FTN8071A Print OL 79B02965C17-O

OL 79B02965C19-O
 P4 EVALUATION BOARD - TOP HIERARCHY

Model FTN8071A

Print
Interface Connectors

RS232_DTR

RS232_DSR Audio & Voltage REGs

RS232_DCD
DHFA_MIC_IN DHFA_SPKR_OUT
DHFA_MIC_IN DHFA_SPKR_OUT
RS232_RI RS232_DTR
DHFA_SPKR_OUT Analog_Audio_In
DHFA_SPKR_OUT Analog_Audio_In
RS232_RTS RS232_DSR
DSC_Enable 5V_Data
DSC_Enable 5V_Data
RS232_CTS RS232_DCD
5V_Data Dc_to_Dc_12V
5V_Data DC_to_DC_12V
RXD_UART_2 RS232_RI
VCC GPS_PWR
VCC GPS_PWR
TXD_UART_2 STNDBY
2.7V_IN_SHEELD DSC_Enable
2.7V_IN_SHEELD DSC_Enable

Dc_to_Dc_12V RS232_RTS
VCC
DC_to_DC_12V VCC
RS232_CTS
STNDBY SPK_GND
RXD_UART_2
GPS_PWR SPKR_OUT
GPS_PWR MIC_In SPKR_OUT
TXD_UART_2
SPKR_OUT 2.7V
SPKR_OUT Analog_Audio_In Analog_Audio_In 2.7V

AUDIO_PA_12V AUDIO_PA_12V
Analog_Audio_Out&Power_On_Off MIC_In

2.7V
2.7V GPS_1PPS_STANDALONE GPS_1PPS_LED

Analog_Audio_Out&Power_On_Off

AUDIO_PA_12V
AUDIO_PA_12V

2.7V_IN_SHEELD
DHFA_MIC_IN DHFA_MIC_IN 2.7V_IN_SHEELD

79B02963C87-O
SHEET 1 OF 6
 U5 U987 VCC
MAX603ESA 120n
8 1
OUT IN

GND4
GND3
GND2
GND1
5 4
SET OFF_

7
6
3
2
R77
47K
C9554 C9553
C62
33p 33p
10u
C77 C105
100n 33p
R78 AGND AGND DGND AGND
2.7V_IN_SHEELD

P4 EVALUATION BOARD - AUDIO 39K

2.7Vdc REG
AGND AGND L10
MIC_BAIS 2.7V_IN_SHEELD 120n
2.7V
VAG

Model FTN8071A C50 33p

C110 C111
33p 33p
C51 33p
R32

RES_47K 8 2
VAG2

Print Split 1 2
1

4
3
C48 C49
AGND AGND DGND

33p 33p R22 R23

U4
AUDIO_PA_12V C4 R3
5V_Data MC33202DR2 22K 22K
1u 51K

Print
2.7V_IN_SHEELD

C9560
R2588 C5
R15 C6 C9
1.u 3.9K
1uF 470K 1uF 22u
C9535 DGND
2 880_1800MHZ

OUT AGND
C9555
1.u AGND
C9190 C9205 R2564 AGND
C9204 47.u 0.1u 1.8K

100n L15 C9540 Analog_Audio_In

IN 120n AGND
R2470 R2468 1 1u
C9215 C3
0. DHFA_MIC_IN C52 680PF
0.
10n 1uF
R2587
C9549 C9550 2.4K
C15 2.2NF

33.p 33.p R2 51K

AGND
AGND R33 RES_10K

AGND U982
R2469 R2471 TDA1519CTD
0. 0. INV 12 10 R26 560 6 8
R1098 INV VP 2.7V_IN_SHEELD
U3 7
8.2K DHFA_SPKR_OUT AGND MIC_BAIS C1
NINV 19 3 DHFA_SPKR_OUT MC33202DR2 5
Analog_Audio_Out&Power_On_Off NINV OUT1 1uF R50
8 SPK_GND 2 8 4
R24 560 RES_1000
R2590 OUT2 SPK_GND MIC_In
C9201 1 1
C9219 R2563 0. RR SPK_GND R38
11 18 C9228 3 R27 U3
330n
M_SS NC6 C24 33p 1K 4 MC33202DR2
1n 8.2K 17 MIC_BAIS R25 560 560
NC7 C9208
2 16
NC1 NC8 C32 C33
4 15 100n 100p
NC2 NC9 33p 33p
6 14 C25 33p
RR 2.7V_IN_SHEELD
NC3 NC10 VAG2
7 13
AGND NC4 NC11 L2 R21 L4 AGND
9 C12 R17
NC5 2.4K 120n
120n C27 C28 C68
GND1
GND2
GND3

R1068 C76 C104 470K

STNDBY 100NF C26
C9241 C9185 VAG2
39.K AGND AGND AGND 33p 33p 33p 100n 33p
100p 3.3u 33p
20
5
21

C2
AGND C34 C35 R31
VAG
C38 33p 1uF 560K
AGND 33p 33p
AGND C30 C29
C8
AGND 33p 33p AGND
8V_AUDIO C39 33p 22u
R4
SPKR_Out SH1
0 SHIELD
C36 C37
R1056 33p 33p AGND AGND
15K

C40 C41 C9561 AGND

1.u C13 2.2n L6 1
L5 R18
33p 33p
R2575 C9409 R2553 120n 120n
15K
15K 330n 15K AGND
8 6 AGND R84 33.K R52 18.2K
vcc=8V_AUDIO,vee=AGND 7 Must be SHEELDED
C14
5 C44 C47
4 2.7V_IN_SHEELD 2.2n
R1104 8 6 R29 560
U988 33p 10n
7 DGND
5.6K MC33072 AGND
C75 5
R2473 R1069 C103 U4 4
100n 33p C11
0. 39.K MC33202DR2
AGND R19 10n
R2551 15K
C42 C43 AGND
C9567
15K VAG AGND
33p 33p 33p
R1057

8V_AUDIO 15K L12

VAG 120n
R2552
AGND R28
15K R30
560
C9206 180K

100n C45 C46

33p 33p C116 C117

C9378 R2550 C9192 33p 33p

Analog_Audio_Out&Power_On_Off
100n 15K 330n
AGND
AGND DGND AGND

79B02963C87-O
AGND AGND SHEET 2 OF 6
 Must be SHEELDED

Voltage to MIC & AMP

VCC

CR11 CR9 CR1

1PPS DSC_EN VCC

R62 R2570 R61 5V regulator for L14

22.u
C9539
68u
C9569
220.n
C70 4.7u

270 270 270

RS-232 Driver R85 0

DGND DGND
C106 33p

DC_to_DC_12V
Q25 U980 D2
C9548
GPS_1PPS_LED 5V_Data LP2957IS
100.n L8
Q27 120n
2 1
5V_Data 5V_Data OUTPUT INPUT DGND
5 4 J3-1
U984 ERROR SHUTDOWN AUDIO_PA_12V
AGND DGND 1
DSC_Enable D1
C9538 GND U983
MAX771ESA To be Placed D5
3 C115 C114
100.u
1 4 33p 33p
R65 EXT SHDN
SENSE 8 5 In the SHEELED
470K 5V_Data Q3 CS REF
2 3
V+ FB

AGND
R79

GND
Q14 DGND
4.7K DGND R2554 C9547 VCC AGND DGND
3906L C9564 C9563 C9537

6
Q16 0.1 100.n
3904L 100.u 100.u 100.u
R68
DGND
RES_10K VCC Q38

DGND 2 F1
DGND

R66 DGND 3 1 J3-2

470K 13mmx13mm PCB S2

2

RS232_RI VOLTAGE
R2598 J3-3
Q23 Heatsink is needed 2.4K
AMP
3

R2593
470.K

R2596
RS232_CTS R2589 79B02963C87-O
DGND U992 22.K
Q22
MC33072
221K DGND SHEET 3 OF 6

8 2
1 D4
3
5V_Data RS232_RTS 4
Q21

R2594 C9579 R2597

VR10
LED-2 Voltage to MIC & AMP 0.
100.n 8.2K 2.
2
LED-1
RS232_DSR
1
Q20

DGND

R2527

RS232_DTR 100.K

Q19

AUDIO_PA_12V
8V_AUDIO

U978
RS232_DCD LP2951C
Q18 8
7
INPUT OUTPUT
1
5
P4 EVALUATION BOARD - AUDIO
FEEDBACK ERROR GPS 3Volts REG
3 2
SHUTDOWN SENSE
6 C9536
5V_TAP R2518

GND
880_1800MHZ
RXD_UART_2

GPS RXD on GPS models Q4

110.K U981
LP2981
Model FTN8071A

4
2
OUT
3
C9386 ON_OFF* VCC
C9365 5 1
100n GPS_PWR VOUT VIN
3.3u
TXD_UART_2

GPS TXD on GPS models Q11 IN GND

NC
4
Print Split
1 2
C9542
R2519 R2521
47.u
0. 20.K

Q15 CR2 CR10 CR8 CR7 CR6 CR5 CR4 RI

Print
DGND DGND
3904L
GPS_TXD GPS_RXD DCD DTR DSR RTS CTS CR3
R67
2.4K R64
470K
R53 R63 R60 R59 R58 R57 R56 R55

270 270 270 270 270 270 270 270 AGND

DGND
 P6-2
2
P6-1
DIN Connector F.
1
TX_EN
GPS Connector
P4 EVALUATION BOARD - INTERFACE
5

To HOST 5V_Data
DGND Model FTN8071A

GPS_RTCM_STANDALONE
GPS_1PPS_STANDALONE
RS232_RI TXD_UART_2

Analog_Audio_Out&Power_On_Off
DGND

R2566 DGND

RXD_UART_2
d-15 To HOST 1.K

TS_Turn_on_stand_by
Input_I_O&Sim_cr_det
SIM_CR_Reset_RST
d-10 To HOST P5-1 DNP

DSC_Downlink

SIM_CR_Clock
RS232_CTS RXD_UART_2
1

DSC_Enable
RS232_DCD

RS232_RXD

RS232_RTS
IrDA_Select
P5-2
2 R2595
SoftGSM_EN 0.
J121-1 TX_EN

J127-2

J127-4

J127-6

J127-8
J4-1 RS232_TXD 1

10
J127-10
2

8
1 J121-2 RXD_UART_2 R2561

J125-2

J125-4

J125-6

J125-8

J125-10

J125-12

J125-14

J125-16

J125-18

J125-20

J125-22

J125-24

J125-26

J125-28
GPS RXD on GPS models 2.7V
J4-2 RS232_RXD 2
10.K
2 J121-3 TXD_UART_2
GPS TXD on GPS models
J4-3 RS232_DTR 3
RS232_RTS 2.7V
3 J121-4 RS232_TXD
J4-4 RS232_DCD 4 DGND
VCC
4 J121-5 RS232_RXD
J4-5 RS232_RTS
5
RS232_DTR
5 J121-6
AUDIO_PA_12V
J4-6 RS232_CTS 6

J125-11

J125-13

J125-15

J125-17

J125-19

J125-21

J125-23

J125-25

J125-27
J125-1

J125-3

J125-5

J125-7

J125-9
6 J121-7 RS232_DCD
for CSD call/PDP context indicator Jumper ON = SoftGSM Mode
J4-7 RS232_DSR 7
AUDIO_PA_12V
7 J121-8 RS232_RTS
RS232_DCD

J127-1

J127-3

J127-5
5

J127-7
7

J127-9
9
J4-8 RS232_RI 8
8 J121-9 RS232_CTS

RS232_DSR

DSC_Uplink
SIM_CR_I_O_Data

SIM_CR_VCC_3.0_TO_5Vdc

RS232_DTR

MAN_TEST

TXD_UART_2

RS232_TXD

RS232_CTS
Analog_Audio_In
RS232_RI
J4-9 9 SW2
MAN_TEST
9 J121-10 RS232_DSR MOMENT_SWITCH

TXD_UART_2

GPS_ANTTENNA_VOLTAGE
J4-10 Analog_Audio_In 10 2
RS232_DTR GPS_1PPS_STANDALONE
10 J121-11 RS232_RI
Analog_Audio_Out&Power_On_Off R35
J4-11 11
11 J121-12 MAN_TEST 100

J4-12 Wake_up_gprs_coverage_indicator 12 3 DGND

12 J121-13 Analog_Audio_In DGND
AGND GPS_PWR
J4-13 Input_I_O&Sim_cr_det 13
13 J121-14 Analog_Audio_Out&Power_On_Off DGND
SIM_CR_VCC_3.0_TO_5Vdc GPS_PWR
J4-14 14
RS232_DSR GPS_PWR
14 J121-15 Wake_up_gprs_coverage_indicator
J4-15 SIM_CR_Reset_RST 15
Analog_Audio_Out&Power_On_Off
15 J121-16 Input_I_O&Sim_cr_det Custom Definition
J4-16 SIM_CR_I_O_Data
16
16 J121-17 SIM_CR_VCC_3.0_TO_5Vdc
DSC_Enable 5V_Data
J4-17
17
SIM_CR_Clock 17
J121-18 SIM_CR_Reset_RST
DIN Connector M.
5V_Data
J4-18 TS_Turn_on_stand_by 18
5V_Data
18 J121-19 SIM_CR_I_O_Data
J4-19 DSC_Enable 19 P3-1
19 J121-20 SIM_CR_Clock 1
L16
J4-20 DSC_Downlink 20 22.u TX_EN MAN_TEST DSC_Downlink EXT_B+ VCC
20 J121-21 TS_Turn_on_stand_by P3-2
GPS_PWR GPS_ANTTENNA_VOLTAGE
J4-21 DSC_Uplink 21 2
D3
DSC_Enable 5
21 J121-22 DGND
J4-22 AGND 22 P3-3
C9541
22 J121-23 DSC_Downlink 3 R2571 R2572
3.3u

Analog_Audio_Out&Power_On_Off
J4-23 23 56.K 56.K
23 J121-24 DSC_Uplink
AGND HandsFree_Select
J4-24 24
AUDIO_PA_12V
AGND

Input_I_O&Sim_cr_det

TS_Turn_on_stand_by
24 J121-25

SIM_CR_Reset_RST
J4-25 25 DGND
25 J121-26 DGND 5

DSC_Downlink

SIM_CR_Clock
Q34 Q35

DSC_Enable
RS232_DCD

RS232_RXD

RS232_RTS
IrDA_Select
J4-26 26
26 DGND J121-27 DGND P1-2
IrDA_Select
J4-27 27 2
VCC
27 J121-28 DGND P1-1
J4-28 28 DGND 1
AGND R2556

J126-1
1

J126-3
3

J126-5
5

J126-7
7

J126-9

J126-11

11

J126-13
13

J126-15

15

J126-17

17

J126-19
19

J126-21

21

J126-23

23

J126-25

25

J126-27
27
28 J121-29 DGND
100.K
J4-29 29
29 J121-30 VCC
VCC VCC
J4-30 30 DGND
30 J121-31 VCC
31
P10-2
J121-32 VCC DGND
HandsFree_Select
32 VCC(3.0-6Vdc) 2
J121-33 VCC J122

10

12

14

16

18

20

22

24

26

28
J126-10

J126-12

J126-14

J126-16

J126-18

J126-20

J126-22

J126-24

J126-26

J126-28
2

8
J126-2

J126-4

J126-6

J126-8
Jack_4pin

1
33 P10-1

P2-1
P2-2
J121-34 GPS_Ant_PWR_3_TO_5Vdc 1 1
34 3
DHFA_SPKR_OUT
J121-35 RX_for_differential_GPS_RTCM 4
35 2

SIM_CR_I_O_Data

SIM_CR_VCC_3.0_TO_5Vdc

RS232_DTR

MAN_TEST

TXD_UART_2

RS232_DSR

RS232_TXD

RS232_CTS
J121-36 GPS_1PPS

RS232_RI
Print Split

DSC_Uplink
R2557
36

Analog_Audio_In
GPS_1PPS

RX_for_differential_GPS_RTCM
100.K

C9559

470u
DGND DGND
AGND

Print 79B02963C87-O
SHEET 4 OF 6
AGND
 To the UUT BUTT-I 15 PINs BUTT-I I 15 PINs BUTT 12 PINs

To D-15

Analog_Audio_Out&Power_On_Off
Analog_Audio_Out&Power_On_Off

Analog_Audio_Out&Power_On_Off
To d-10
Print Split

Analog_Audio_In
GPS_1PPS J120-1

Analog_Audio_In
1

Analog_Audio_In

DSC_Downlink
DSC_Uplink

DSC_Enable
RX_for_differential_GPS_RTCM J120-2

DSC_Downlink
DSC_Downlink

DSC_Enable
VCC

DSC_Uplink

MAN_TEST
MAN_TEST
DSC_Enable
DSC_Uplink
2

MAN_TEST

EXT_B+
EXT_B+
GPS_Ant_PWR_3_TO_5Vdc J120-3
3

2.7V

2.7V
VCC VCC(3.0-6Vdc)

Print J12-1
1
J12-2 VCC
J120-4
4
J120-5

J13-1

10

11

12

13

14

15

17

16
1

J13-10

J13-11

J13-12

J13-13

J13-14

J13-15

J13-17

J13-16
J13-2

J13-3

J13-4

J13-5

J13-6

J13-7

J13-8

J13-9
J1-1
1

10

11

12

13

14

15

16

17

18

19

20

10

11

12

13

14

15

16

18

17

19

20
J1-10

J1-11

J1-12

J1-13

J1-14

J1-15

J1-16

J1-18

J1-17

J1-19

J1-20
2 5

J1-2

J1-3

J1-4

J1-5

J1-6

J1-7

J1-8

J1-9
J2-1

J2-11
J2-2

J2-3

J2-4

J2-5

J2-6

J2-7

J2-8

J2-9

J2-10

J2-12

J2-13

J2-14

J2-15

J2-16

J2-17

J2-18

J2-19

J2-20
J12-3 VCC J120-6
C9576 C9577 C9578
3 C9556 6
220.n 220.n 220.n 2.2m
J12-4 VCC J120-7
4 7
DGND C74

DSC_Downlink
J12-5 J120-8
C90 100n
5 DGND DGND DGND DGND 8 C72
33p C89 C87 C93 C88 C96
J12-6 DGND J120-9 100n
33p 33p 33p 33p DGND 33p
6 9
J12-7 DGND J120-10 DGND DGND
C91 DGND C98
7 10
DGND 33p C99 C100 C101 C102 C71 C84
J12-8 DGND J120-11 DGND
U989 L13 C85 C73 33p 33p 33p 33p 33p 100n 33p
C86
DGND 8 DGND 11 DGND
120n 120n 33p 100n C97 C92 C94 C95
AGND_IN J12-9 AGND_IN J120-12 33p

EXT_B+
9 12 33p 33p 33p 33p DGND
DSC_Uplink J12-10 DSC_Uplink J120-13
10 13 DGND DGND
DSC_Downlink J12-11 DSC_Downlink J120-14 DGND DGND DGND DGND
AGND AGND
11 14
DSC_Enable J12-12 DSC_Enable J120-15
12 15
TS_Turn_on_stand_by J12-13 TS_Turn_on_stand_by J120-16
13 16
SIM_CR_Clock J12-14 SIM_CR_Clock J120-17
14 17
SIM_CR_I_O_Data J12-15 SIM_CR_I_O_Data J120-18
15 18

RF SMA Connector SIM_CR_Reset_RST J12-16 SIM_CR_Reset_RST J120-19

5V_Data AUDIO_PA_12V
Diagnostic
16 19 5
SIM_CR_VCC_3.0_TO_5Vdc J12-17 SIM_CR_VCC_3.0_TO_5Vdc J120-20
17 20
Input_I_O&Sim_cr_det J12-18 Custom Definition Input_I_O&Sim_cr_det J120-21 R2578 R2576
J124 18 21 10K
AUDIO PA ON Const 100.K
Wake_up_gprs_coverage_indicator J12-19 Wake_up_gprs_coverage_indicator J120-22
19 22
STNDBY
Analog_Audio_Out&Power_On_Off J12-20 Analog_Audio_Out&Power_On_Off J120-23
R2579

1
20 23

2
P8-2

P8-1
Analog_Audio_In J12-21 Analog_Audio_In J120-24 10K

SIM_CR_VCC_3.0_TO_5Vdc
C9566 21 24
Q36
0.5p
MAN_TEST J12-22 MAN_TEST J120-25 TX_Enable R2577

Input_I_O&Sim_cr_det
22 25

SIM_CR_I_O_Data
10K
J12-23 RS232_RI J120-26

DSC_Downlink

SIM_CR_Clock
RS232_RI C9581 C9580 C9558

DSC_Enable
R2573

DSC_Uplink
DGND J123 23 26

16
C9572 C9571 10u
DGND J12-24 470.p 470.p J120-27

j114-16
RS232_DSR RS232_DSR 560.K
NC0 NC1 24 220.n 220.n 27
2 1 3 RS232_CTS J12-25 RS232_CTS J120-28
ANT L11
25 AGND AGND DGND DGND 28 Q37 120n
RS232_RTS J12-26 RS232_RTS J120-29 2.7V_IN_SHEELD
C9562 26 29 DGND

15

14

13

12

10
J114-15

J114-14

J114-13

J114-12

J114-10
7

9
J114-7

J114-9
4.7p RS232_DCD J12-27 for CSD call/PDP context indicator RS232_DCD J120-30
R2583 R2582 L17 R2574

1
27 30 C113 C112

P9-2
0.5p 0.5p 0. 100K
RS232_DTR J12-28 RS232_DTR J120-31
33p 33p
28 31
MUTE
RS232_RXD J12-29 RS232_RXD J120-32
DGND 29 32

2
P9-1
RS232_TXD J12-30 RS232_TXD J120-33 DGND AGND
30 33 DGND
GPS TXD on GPS models

11
J114-11

2
J114-4

J114-1

J114-6

J114-3

J114-8

J114-5

J114-2
TXD_UART_2 J120-34
34 DGND
GPS RXD on GPS models RXD_UART_2 J120-35
35
TX_EN J120-36

C9575 C9574 36 P1-2

IrDA_Select
220.n 220.n
P1-1
1
2
P4 EVALUATION BOARD - INTERFACE

RS232_RI

RS232_DSR

RS232_RTS

RS232_DCD

RS232_RXD
RS232_DTR
RS232_CTS

RS232_TXD
DGND DGND

NOTE:MIRROR TO G18/D15
Model FTN8071A
DGND

79B02963C87-O
SHEET 5 OF 6
 5V_Data
5V_Data

Modem/GPS Select

P12-2
2

C9565 D9 FEMALE
P12-1 DTE Orintation
33.u
1
DCD J5-1
DGND 1

P4 EVALUATION BOARD - INTERFACE RxD J5-2

26 2 1
2
VCC TxD J5-3
C9546 28 27 VR4 3
5V_Data C1+ V+
100.n MMBZ15VD DTR J5-4
25 4 4
C1- U979 V-

Model FTN8071A U990

MC14053B 1
C2+
MAX3238E 3
DGND
2 1
RI

DSR
J5-9
9
16 C9543 5 J5-6
330.n T1OUT RxD C9545 C9544
VCC 6 3 6
EN C2- 330.n 330.n VR3 RTS
12 6 J5-7
DHFA MIC RS232_RXD X0
X
14 Modem_GPS_RxD
DGND
24
T1IN
T2OUT CTS MMBZ15VD 7

Print Split RXD_UART_2

RS232_TXD
13
2
X1
Y0
A
11

15
RS232_CTS
RS232_DSR
RS232_DCD
23
22
19
T2IN
T3IN
T3OUT
7

10
DSR
DGND DGND
3

DGND
2 1
CTS J5-8
8
J5-5
Y T4IN T4OUT DCD
1 10 RS232_RI 17 5
TXD_UART_2 Y1 B T5IN VR2
5 12
R2586 Z0 5V_Data 14 T5OUT RI MMBZ15VD
4
J111 9.1K Z FORCEOFF
R2585 3 9
Z1 C

Print
3
12K 13 15 DGND

GND

VEE
FORCEON INVALID DGND
R2580

7
16
100K R1OUTB 2 1
VR5
Modem_GPS_TxD 21 8 R2565
R1OUT R1IN TxD MMBZ15VD
C80 DGND J5-10
3.9K
33p RS232_RTS 20 9 10
2 4 3 1 R2OUT R2IN RTS
DGND DGND
2 1 J5-11
RS232_DTR 18 11 DGND
R3OUT R3IN DTR 3
11
GND
DHFA_MIC_IN VR6
2
L3 MMBZ15VD
C78
L7 120n R2568
680p 3
120n 100. DGND DGND
DGND
Connector SHEELD
2 1

DGND

AGND VR8

MMBZ15VD

VR7 2 1
3 MMBZ15VD

DGND

3
2 1
DGND

HeadSet Connctor. VR9

MMBZ15VD

HandSet adapter EXT SIM Connections J118

Q29
3
SoftGSM_EN
DGND
Q26

DC_to_DC_12V 12V_SW
C61
DGND
SIM_CR_VCC_3.0_TO_5Vdc 10UF DGND C9552
2 4 3 1
RJ-45 Connector R82 33p
R70
RJ-45 Connector DGND 100 Analog_Audio_Out&Power_On_Off
C9573 4.7K
SoftGSM_EN

SIM_CR_VCC_3.0_TO_5Vdc
220.n C60
J115-8
8

J115-7
7

J115-6
6

J115-5
5

J115-4
4

J115-3
3

J115-2
2

J115-1
1
10u

Input_I_O&Sim_cr_det
U985
J10-8
8

J10-7
7

J10-6
6

J10-5
5

J10-4
4

J10-3
3

J10-2
2

J10-1
1

DSC_Downlink DSC_Enable

SIM_CR_Reset_RST
SIM_CR_I_O_Data
R69 120n SoftGSM Switching circuit
C7 Q28

SIM_CR_Clock
DGND C59 MIC_In
DGND 4.7K S1

Analog_Audio_In
Analog_Audio_Out&Power_On_Off
DSC_Downlink

DSC_Uplink
2.2u R2559 R2560 RTS
10UF C81
SWITCH

7
C82 22.K
Analog_Audio_Out&Power_On_Off
DSC_Downlink

DSC_Uplink

Analog_Audio_In

L1 22.K

S_VCC1

S_VCC2
D 33p 33p
R20 120n
DGND C9551
4.7K G 3 6 SIM_CR_I_O_Data
R83 SIM_CR_Clock S_CLK S_I|O 680p U991 Q32 R2558
2 4
22.K

SIM-7

SIM-5

SIM-3

SIM-2

SIM-4

SIM-6

SIM-8

SIM-1

1
DSC_Enable 0 S_PD S_RESET
Q17 DGND C83 33p
S DGND Input_I_O&Sim_cr_det
R2569

GND1

GND2
7002 SIM_CR_Reset_RST C9568
DGND 0 12V_SW 33p
DGND DGND DGND

8
VCC C9570 Q30
U986 C79
VCC SoftGSM_EN
220.n
120n 680p

SPKR_Out

DGND DGND DGND DGND

AGND DGND DGND

DGND

79B02963C87-O
SHEET 6 OF 6
Parts List REFERENCE MOTOROLA
DESCRIPTION
SYMBOL PART NO.
Evaluation Board
C9539 2311049A24 CAPP_68u
Model FTN8071A P4 C9540 2311049A07 CAPP_1UF
C9541 2113743G25 CAP_3.3u
C9542 2186201J02 CAP_22u
REFERENCE MOTOROLA C9543-9545 2113743K17 CAP_330n
DESCRIPTION
SYMBOL PART NO.
C9546 2113743K15 CAP_100n
Capacitors C9547-9548 2113743E20 CAP_100n
C1-6 2311049A07 ECAP_1UF C9549-9550 2113740F39 CAP_33p
C7 2311049A09 CAPP_2.2u C9551 2113741F21 CAP_680PF
C8-9 2311049J35 CAPP_22u C9552-9554 2113740F39 CAP_33p
C11 2113741F49 CAP_10n C9555 2311049A07 CAPP_1UF
C12 2113743A19 CAP_100NF C9556 2313748E31 CAPP_2.2m
C14-15 2113741F33 CAP_2.2NF C9558 2311049A19 CAPP_10u
C24-30 2113740F39 CAP_33p C9559 2380090M39 CAPP_470u
C32-46 2113740F39 CAP_33p C9560 2311049A07 CAPP_1UF
C47 2113741F49 CAP_10n C9561 2113928A01 CAP_1u
C48-51 2113740F39 CAP_33p C9562 2113740F19 CAP_4.7p
C52 2113741F21 CAP_680PF C9563-9564 2311049C13 CAPP_100u
C60 2380090M24 CAPP_10u C9565 2311049C08 CAPP_33u
C62 2380090M24 CAPP_10u C9566 2113740F01 CAP_0.5p
C68 2113740F39 CAP_33p C9567-9568 2113740F39 CAP_33p
C70 2113743G26 CAP_4.7u C9569-9578 2113743A23 CAP_220n
C71-77 2113743A19 CAP_100n C9579 2113743A19 CAP_100n
C78-79 2113741F21 CAP_680PF C9580-9581 2113740F67 CAP_470p
C80-106 2113740F39 CAP_33p CR1 4880304L02 LED_GRN
C110-117 2113740F39 CAP_33p CR2-11 4880304L01 LED_RED
C9185 2311049A57 ECAP_10UF Diodes
C9190 2311049C05 CAPP_47u D1 4813833B01 MBRS140
C9192 2113743K17 CAP_330n D2 4813833A06 MBRD360
C9201 2113743K17 CAP_330n D3 4813833B01 MBRS140
C9204 2113743E20 CAP_100n D4-5 4813833A02 MBRD640
C9205 2311049A01 CAPP_0.1u Fuses
C9215 2113741F49 CAP_10n F1 0904923K01 SMD_FUSE_HOLD
C9219 2113741F25 CAP_1n Connectors
C9228 2113740F51 CAP_100p J1-2 0909449B04 CONN_J
C9241 2113740F51 CAP_100p J3 3102151C30 CONN_P
C9365 2311049A57 ECAP_10UF J4 2804989M01 EDGE
C9378 2113743E20 CAP_100n J5 0909672B03 CONN_J
C9386 2113743E20 CAP_100n J10 0983365N01 EDGE
C9409 2113743K17 CAP_330n J12 2804989M01 EDGE
C9535-9536 9186929J01 880_1800MHZ J13 0909467R02 CONN_J
C9537-9538 2311049C13 CAPP_100u J111 0909399T02 CONN_J

1
REFERENCE MOTOROLA REFERENCE MOTOROLA
DESCRIPTION DESCRIPTION
SYMBOL PART NO. SYMBOL PART NO.

J114 2802935S08 CONN_P R18-19 0662057A77 RES_15K

J115 0983365N01 EDGE R20 0662057A65 RES_4.7K
J118 0909399T02 CONN_J R21 0662057A58 RES_2.4K
J120-121 0988716K01 CONN R22-23 0662057A81 RES_22K
J122 0909032K01 JACK_4PIN R24-29 0662057A43 RES_560
J123 3903920K01 ANTENNA_3P2NC R30 0662057D30 RES_180K
J125 0908606Y06 CONN_J R31 0662057B16 RES_560K
J126 2880471L02 CONN_P R32 0662057A89 RES_47K
J127 0908606Y05 CONN_J R33 0662057A73 RES_10K
Coils R35 0611077D97 RES_100
L1-8 2462587T16 IDCTR_120n R36 0662057A97 RES_100K
L10-13 2462587T16 IDCTR_120n R38 0662057C75 RES_1K
L14 2503788S09 IDCTR_22u R50 0662057C75 RES_1000_1K
L15 2462587T16 IDCTR_120n R52 0662057R68 RES_18.2K
L16 2462587P28 IDCTR_22u R53 0662057C61 RES_270
L17 249646M43 NO_DESC R55-63 0662057C61 RES_270
Connectors R64-66 0662057B14 RES_470K
LED 2880001R02 CONN_P R67 0662057A58 RES_2.4K
P1-2 2880001R02 CONN_P R68 0662057A73 RES_10K
P3 2880001R03 CONN_P R69-70 0662057A65 RES_4.7K
P5-10 2880001R02 CONN_P R77 0662057A89 RES_47K
P12 2880001R02 CONN_P R78 0662057A87 RES_39K
Transistors R79 0662057A65 RES_4.7K
Q3 4803676A04 BSS123 R82 0611077D97 RES_100
Q4 4802393L34 FDV302P R83 0662057B47 RES_0
Q11 4802393L34 FDV302P R84 0662057A85 RES_33K
Q14 4813824A17 PNP_3906L R85 0662057B47 RES_0
Q15-16 4813824A10 NPN_3904L R1056 0662057P02 RES_15K
Q17 4813823A07 TMOSFETN_7002 R1068 0662057A87 RES_39K
Q18-23 4802393L34 FDV302P R1098 0662057A71 RES_8.2K
Q25 4803676A04 BSS123 R1104 0662057A67 RES_5.6K
Q26 4802393L04 BSS84 R2468-2469 0662057B47 RES_0
Q27 4813821A21 MTD20N03HD R2518 0611079E05 RES_110K
Q28-30 4803676A04 BSS123 R2519 0662057B47 RES_0
Q32 4803676A04 BSS123 R2521 0662057P20 RES_20K
Q35-37 4803676A04 BSS123 R2527 0662057P95 RES_100K
Q38 4809807C24 SI4463 R2550-2552 0662057P02 RES_15K
Resistors R2553 0662057A77 RES_15K
R2-3 0662057D17 RES_51K R2554 0604648P05 RES_0.1
R4 0662057B47 RES_0 R2556-2557 0662057A97 RES_100K
R15 0662057B14 RES_470K R2558-2560 0662057A81 RES_22K
R17 0662057B14 RES_470K R2561 0662057A73 RES_10K

2
REFERENCE MOTOROLA REFERENCE MOTOROLA
DESCRIPTION DESCRIPTION
SYMBOL PART NO. SYMBOL PART NO.

R2564 0662057A55 RES_1.8K S2 4008241G06 SWIT_ET01

R2565 0662057A63 RES_3.9K SW2 4004929K01 MOMENT_SWITCH
R2566 0662057A49 RES_1K Shields
R2568 0662057A25 RES_100 SH1 2604044K01 SHIELD
R2569 0662057B47 RES_0 SIM
R2570 0662057C61 RES_270 SIM 2808044H12 CONN_P
R2572 0662057D18 RES_56K Integrated Circuits
R2573 0662057B16 RES_560K U3-4 5113818A14 MC33202DR2
R2574 0662057A97 RES_100K U5 5104187K08 MAX603ESA
R2575 0662057A77 RES_15K U978 5105469E65 LP2951C
R2576-2577 0662057A73 RES_10K U979 5109781E76 MAX3238E
R2578 0662057A97 RES_100K U980 5104187K46 LP2957IS
R2579 0662057A73 RES_10K U981 5185963A04 LP2981
R2580 0662057A97 RES_100K U982 5144751U01 TDA1519CTD
R2582-2583 2113740F01 CAP_0.5p U983 5108858K58 MAX771ESA
R2585 0662057A75 RES_12K U984 4803676A04 BSS123
R2586 0662057A72 RES_9.1K U985-987 2462587T16 IDCTR_120n
R2587 0662057A58 RES_2.4K U988 5113818A03 MC33072
R2588 0662057A63 RES_3.9K U989 2462587T16 IDCTR_120n
R2589 0662057G31 RES_221K U990 5113806A20 MC14053B
R2590 0662057B47 RES_0 U991 4803676A04 BSS123
R2593 0662057B14 RES_470K U992 5113818A03 MC33072
R2596 0662057A81 RES_22K Voltage Suppressors
R2597 0662057A71 RES_8.2K VR2-9 4813832C28 ZENER_MMBZ15VD
R2598 0662057A58 RES_2.4K VR10 4813830G02 MMSZ4679T
Switches
S1 4009060S01 SWITCH

3
Parts List REFERENCE MOTOROLA
DESCRIPTION
SYMBOL PART NO.
Evaluation Board
C9540 2311049A07 CAPP_1u
Model FTN8071B P4 C9541 2113743G25 CAP_3.3u
C9542 2186201J02 22u
C9543-9545 2113743K17 CAP_330n
REFERENCE MOTOROLA C9546 2113743K15 CAP_100n
DESCRIPTION
SYMBOL PART NO.
C9547-9548 2113743E20 CAP_100n
Capacitors C9549-9550 2113740F39 CAP_33p
C1-6 2311049A07 ECAP_1UF C9551 2113741F21 CAP_680PF
C7 2311049A09 CAPP_2.2u C9552 2113740F39 CAP_33p
C8-9 2311049J35 CAPP_22u C9554 2113740F39 CAP_33p
C11 2113741F49 CAP_10n C9555 2311049A07 CAPP_1u
C12 2113743A19 CAP_100NF C9556 2313748E31 CAPP_2.2m
C14 2113741F33 CAP_2.2NF C9558 2311049A19 CAPP_10UF
C15 2113743F49 10nf C9559 2380090M39 CAPP_470u
C24-30 2113740F39 CAP_33p C9560 2311049A07 CAPP_1UF
C32-46 2113740F39 CAP_33p C9561 2113928A01 CAP_1u
C47 2113741F49 CAP_10n C9562 2113740F19 CAP_4.7p
C48-51 2113740F39 CAP_33p C9563-9564 2311049C13 CAPP_100u
C52 2113741F21 CAP_680PF C9565 2311049C08 CAPP_33u
C60 2380090M24 CAPP_10u C9566 2113740F01 CAP_0.5p
C68 2113740F39 CAP_33p C9567-9568 2113740F39 CAP_33p
C75-77 2113743A19 CAP_100PF C9569-9573 2113743A23 CAP_220n
C78-79 2113741F21 CAP_680PF C9578 2113743A23 CAP_220n
C80-C83 2113740F39 CAP_33p C9579 2113743A19 CAP_100PF
C103-C105 2113740F39 CAP_33p C9580-9581 2113740F67 CAP_470p
C110-117 2113740F39 CAP_33p C9582 2311049C08 CAPP_33u
C9185 2311049A57 10u C9583-9585 2113743K17 CAP_330n
C9192 2113743K17 CAP_330n C9586 2113743K15 CAP_100n
C9201 2113743K17 CAP_330n C9587-9590 2113740F51 CAP_100p
C9204 2113743E20 CAP_100n CR1 4880304L02 LED_GRN
C9205 2311049A01 CAPP_0.1u CR2-11 4880304L01 LED_RED
C9215 2113741F49 CAP_10n Diodes
C9219 2113741F25 CAP_1n D1 4813833B01 MBRS140
C9228 2113740F51 CAP_100p D2 4813833A06 MBRD360
C9241 2113740F51 CAP_100p D3 4813833B01 MBRS140
C9365 2311049A57 10u D4-5 4813833A02 MBRD640
C9378 2113743E20 CAP_100n
C9386 2113743E20 CAP_100n Fuses
C9409 2113743K17 CAP_330n F1 0904923K01 SMD_FUSE_HOLD
C9535-9536 9186929J01 880_1800MHZ Connectors
C9537-9538 2311049C13 CAPP_100u J1-2 0909449B04 CONN_J
C9539 2311049A24 CAPP_68u J3 3102151C30 CONN_P

1
REFERENCE MOTOROLA REFERENCE MOTOROLA
DESCRIPTION DESCRIPTION
SYMBOL PART NO. SYMBOL PART NO.

J4 2804989M01 EDGE Resistors

J5 0909672B03 CONN_J R2-3 0662057D17 RES_51K
J10 0983365N01 EDGE R4 0662057B47 RES_0
J12 2804989M01 EDGE R15 0662057B14 RES_470K
J111 0909399T02 CONN_J R17 0662057B14 RES_470K
J115 0983365N01 EDGE R18-19 0662057A77 RES_15K
J118 0909399T02 CONN_J R20 0662057A65 RES_4.7K
J124 2886156U01 CONN_P R21 0662057A71 8.2K
J125 0908606Y06 CONN_J R22-23 0662057A81 RES_22K
J126 2880471L02 CONN_ R24-29 0662057A43 RES_560
J127 0908606Y05 CONN_J R30 0662057D30 RES_180K
J128-129 0988716K01 CONN_J R31 0662057B16 RES_560K
J130 0909032K01 CONN_J R32 0662057A89 RES_47K
Coils R33 0662057A57 2.2K
L1-7 2462587T16 IDCTR_120n R35 0611077D97 RES_100
L10-13 2462587T16 IDCTR_120n R38 0662057C75 RES_1K
L14 2503788S09 IDCTR_22u R50 0662057C75 RES_1000_1K
L15 2462587T16 IDCTR_120n R52 0662057R68 RES_18.2K
L16 2462587P28 IDCTR_22u R53 0662057C61 RES_270
L17 2485930A01 3.3nh R55-63 0662057C61 RES_270
Contact R64-66 0662057B14 RES_470K
M1 3903920K01 CONTACT R67 0662057A58 RES_2.4K
Connectors R68 0662057A73 RES_10K
P6 2880001R02 CONN_P R69-70 0662057A65 RES_4.7K
P9 2802837C03 CONN_P R77 0662057A89 RES_47K
P10 2880001R03 CONN_P R78 0662057A87 RES_39K
P11 2802935S09 CONN_P R79 0662057A65 RES_4.7K
Transistors R82 0611077D97 RES_100
Q3 4803676A04 BSS123 R83 0662057B47 RES_0
Q4 4809579E18 FDV302P R84 0662057A85 RES_33K
Q11 4809579E18 FDV302P R1056 0662057P02 RES_15K
Q14 4813824A17 PNP_3906L R1068 0662057A87 RES_39K
Q15-16 4813824A10 NPN_3904L R1098 0662057A71 RES_8.2K
Q17 4813823A07 TMOSFETN_7002 R1104 0662057A67 RES_5.6K
Q18-23 4809579E18 FDV302P R2468-2469 0662057B47 RES_0
Q25 4803676A04 BSS123 R2518 0611079E05 RES_110K
Q26 4802393L35 BSS84 R2519 0662057B47 RES_0
Q27 4813821A21 MTD20N03HD R2521 0662057P20 RES_20K
Q28-30 4803676A04 BSS123 R2527 0662057P95 RES_100K
Q32 4803676A04 BSS123 R2550-2552 0662057P02 RES_15K
Q36-37 4803676A04 BSS123 R2553 0662057A77 RES_15K
Q38 4809807C24 SI4463 R2554 0604648P05 RES_0.1

2
REFERENCE MOTOROLA REFERENCE MOTOROLA
DESCRIPTION DESCRIPTION
SYMBOL PART NO. SYMBOL PART NO.

R2558-2560 0662057A81 RES_22K Integrated Circuits

R2564 0662057A55 RES_1.8K U3-4 5113818A14 MC33202DR2
R2565 0662057A63 RES_3.9K U5 5104187K08 MAX603ESA
R2568 0662057A25 RES_100 U978 5105469E65 LP2951C
R2569 0662057B47 RES_0 U979 5109781E76 MAX3238E
R2570 0662057C61 RES_270 U980 5104187K46 LP2957IS
R2573 0662057B16 RES_560K U981 5185963A04 LP2981
R2574 0662057A97 RES_100K U982 5144751U01 TDA1519CTD
R2575 0662057A77 RES_15K U983 5108858K58 MAX771ESA
R2576-2577 0662057A73 RES_10K U984 4803676A04 BSS123
R2578 0662057A97 RES_100K U985-987 2462587T16 IDCTR_120n
R2579 0662057A73 RES_10K U988 5113818A03 MC33072
R2580 0662057A97 RES_100K U989 2462587T16 IDCTR_120n
R2583 2113740F01 CAP_0.5p U990 5113806A20 MC14053B
R2587 0662057A58 RES_2.4K U991 4803676A04 BSS123
R2588 0662057A63 RES_3.9K U992 5113818A03 MC33072
R2589 0662057G31 RES_221K U993 5109781E76 MAX3238E
R2590 0662057B47 RES_0 Voltage Suppressors
R2593 0662057B14 RES_470K VR2-9 4813832C28 ZENER_MMBZ15VD
R2596 0662057A81 RES_22K VR10 4813830G02 MMSZ4679T
R2597 0662057A71 RES_8.2K VR11-12 4813832C28 MMBZ15VD
R2598 0662057A58 RES_2.4K VR14 4813832C28 MMBZ15VD
R2599-2601 0662057C61 RES_270 VR16 4813832C28 MMBZ15VD
R2602 0662057A97 RES_100K VR18 4813832C28 MMBZ15VD
R2603 0662057A89 RES_47K
R2605-2606 0662057A75 RES_12K
R2607 0662057A73 RES_10K
R2608-2609 0662057A71 RES_8.2K
R2611 0662057A49 RES_1K
R2612-2613 0662057C61 RES_270
R2614-2615 0662057B47 RES_0
Switches
S1 4009060S01 SWITCH
S2 4008241G06 SWIT_ET01
S3 4083849F04 SWITCH
SW2 4004929K01 MOMENT_SWITCH
Shields
SH1 2604044K01 SHIELD
SIM
SIM 2808044H04 CONN_P

3
 8486452t01_p5

P9
P11 D7 D6 D8 CR11 CR1 CR9 CR8 CR7 CR6 CR5 CR4 CR3 CR2 CR10
5

9 6
9

5 1
R53

R63

R2616 R2614 S1
J5 R2613 R2615 R2617 R2612 R2602 R2607

S3
VR18 VR16 VR14 VR12 VR11 P6
C9583 C9585

P10
6

C9582 M1
R2611
1

U993
C9560 L16
C9570 J126
C9584
R2605
R2595

R2606

C9587

C9589

C9586

SIM
R2608

C9588
R2609

C9590

J125

J12 J128
SH1
J4 J129 C112
L10
C110

C9550

C9549
C2

R31
C9555
R2588

R38
C34
C35

R17 C24
C30

C36
C37
C29

L15
R4

R27
R2564 C25 C8
C32
C33

C38
R25
R26 U3
C27
C68
C28

R24 C9540 C12 C39

R33
C15

L2
C3

R2587

C52
L4 R21 C75 C40
C26
C104
C76

C1 C41 R30
C9553
R2 C103
C9561

SW2 R50 C4 R32 R84 C45

C13
C46 J124
R52

R3 C48 U4 R29
C9
C9567

C43
C116

C51 C49 R28

SW2 R35 C42
C62 C77 C50 R18 C9563
R15
C5
R22

L6 L5
C44

R23
C9537
C105

R77

C6 C14
C47

C79
U5 L12 R19
U987

C9564
C117
R78
C81

C82

C11
C9556
C9554

C9539
R2473

R1069
R1057

J118
C9552

C9206
R2527

C9192 R2550
C60
C9378

U985
R2519
C9551

C9542

R2551
U978
R2552
L14
U981
R1056

R2575
C9409

R83
R2521

U988
J127
C9536

R1104

C9365 R2569
C9573
C83 U986
R1068

R2553

C9386 R2518 U980

C9538 C9569
Q38
J130
8 8
D3
C72
C73
C74

L1
C88

C90

C102
C93

C89

C96
C86

C101
C87

C94
C92

C100
C95

C97

C84

C98
C91

C99

1 1
C71
L7 C85
C114
C115

C9559
D1 F1 S2
J111 J10 J115
C78
1 J3
C80

L3 J2 J1 J13

SHOWN FROM SIDE 1

O1 79B02965C21-0

Print P5 EVALUATION BOARD - TOP VIEW Model FTN8071A/B O1 79B02965C23-0

 8486452t01_p5
P5 EVALUATION BOARD - BOTTOM VIEW
Q4 Q11 Q23 Q22 Q21 Q20 Q19 Q18
R64 R67 R68 Q14 Q39
R79
Q25
R66
R2601

Q16
R62
R61

R65
R2600

Q15
C61

C59

C9568
R59

R2599
R60
R58
R56

R57
R55

Q3 U984 Q40 Q41 VR6

VR5
R82
R2570

VR9
R2565

C9545

C9543 VR2

VR7
C9565

R2574
VR3
U979 VR8
R2577
Q37 VR4
U991
R2559

R2579 Q28
Q36
C9544
R2558

R2568
Q29
R2573

R2582 R2576

L17 C9546

R2583 C9562
R2578 Q30
R2560 R2580
Q32
C9558

R2603

U990
C9581

C9571
C9580

C111
C9572

C9566

U989
L13

L11
C9578

C113

C106

R85

C70
L8
R2554
C9547

C9548

U983 Q27 D2

R70 R69
Q17
C9579
C7 R2597
R2593

R2594

Q26 C9541
R20

R2596
D4
C9201

D5
R2598
R2589

C9185

R2590
C9241

R1098 R2563
VR10

U992
C9208

C9219
R2471

R2469

U982 C9204
C9215
C9190

C9228
C9205

R2470
R2468
C9535

SHOWN FROM SIDE 2 OL 79B02965C22-0

Model FTN8071A/B Print OL 79B02965C24-0
 P5 EVALUATION BOARD - TOP HIERARCHY
Model FTN8071A/B

Print
Interface Connectors

RS232_DTR
RXD_UART_2
RXD_UART_2
RS232_DSR
TXD_UART_2
TXD_UART_2 Audio & Voltage REGs
RS232_DCD DHFA_SPKR_OUT
DHFA_MIC_IN
DHFA_MIC_IN DHFA_SPKR_OUT
RS232_RI RS232_DTR Analog_Audio_In
DHFA_SPKR_OUT
DHFA_SPKR_OUT Analog_Audio_In
RS232_RTS RS232_DSR 5V_Data
DSC_Enable
DSC_Enable 5V_Data
RS232_CTS RS232_DCD
5V_Data Dc_to_Dc_12V
5V_Data DC_to_DC_12V
RS232_RXD RS232_RI
VCC GPS_PWR
VCC GPS_PWR
RS232_TXD STNDBY
2.7V_IN_SHEELD DSC_Enable
2.7V_IN_SHEELD DSC_Enable

Dc_to_Dc_12V LEDS_Enable RS232_RTS

VCC
DC_to_DC_12V VCC
RS232_CTS
RX_for_differential_gps_rtcm
STNDBY SPK_GND
RX_for_differential_gps_rtcm
RS232_RXD
GPS_PWR SPKR_OUT
GPS_PWR MIC_In SPKR_Out
RS232_TXD
SPKR_OUT 2.7V
SPKR_OUT Analog_Audio_In Analog_Audio_In 2.7V
RX_for_differential_gps_rtcm
AUDIO_PA_12V RX_for_differential_gps_rtcm
AUDIO_PA_12V Analog_Audio_OUT&POWER_On_Off MIC_In

2.7V TXD_UART_2
2.7V GPS_1PPS GPS_1PPS_LED TXD_UART_2

RXD_UART_2
Analog_Audio_OUT&POWER_On_Off RXD_UART_2

AUDIO_PA_12V
LEDS AUDIO_PA_12V

DHFA_MIC_IN 2.7V_IN_SHEELD
DHFA_MIC_IN 2.7V_IN_SHEELD

79B02963C88-O
SHEET 1 OF 6
 VCC
U5
U987
MAX603ESA
8 1 120n
OUT IN

GND4
GND3
GND2
GND1
5 4
SET OFF_

R77

7
6
3
2
C9554

P5 EVALUATION BOARD - AUDIO 47K

33p
33p
C9553 C62
10u

C77 C105
R78 AGND AGND DGND AGND
2.7V_IN_SHEELD 100n 33p

Model FTN8071A/B
39K

2.7Vdc REG

AGND AGND
2.7V_IN_SHEELD

Print Split
L10
MIC_BAIS
120n
C50 33p
VAG 2.7V
C9204 AUDIO_PA_12V
100n
Print C51 33p
C110 C111
C9535
33p 33p
2 880_1800MHZ R32
OUT RES_47K 8 2
VAG2
1 2 1
AGND
R2470 R2468 C9190 C9205 3 DGND
C9215 AGND
0. 0. 4
10n 47.u 0.1u C48 C49
33p 33p R22 R23
IN R3 U4
C4 22K 22K
1
51K MC33202DR2
AGND 1u 2.7V_IN_SHEELD
U982

TDA1519CTD 5V_Data
R2469 R2471 AGND C5 C6
R15 C9
0. INV 12 10
AGND R1098 0. INV VP 1uF 1uF 22u
C9560 470K
8.2K R2588
NINV 19 3 DHFA_SPKR_OUT 1.u
Analog_Audio_OUT&POWER_On_Off NINV OUT1 DHFA_SPKR_OUT 3.9K
8 SPK_GND
OUT2 SPK_GND DGND AGND
C9201 R2590 1
RR C9555
C9219 R2563 0. 11 18
330n 1.u
M_SS NC6
1n 8.2K 17
NC7 AGND AGND
2 16 C9208 C9228
NC1 NC8
4 15
NC2 NC9 100n 100p
RR 6 14
NC3 NC10 Analog_Audio_In
7 13
AGND NC4 NC11 R2564
9 AGND
NC5 C3
1.8K

GND1
GND2
GND3
R1068 L15 R2587 1uF
C9241 C9185 STNDBY
39.K DHFA_MIC_IN 2.4K
AGND AGND 120n
100p 3.3u

20
5
21
C9540 1u C15 2.2NF
C52 680PF
8V_AUDIO R2587 change to 8.2k
R33 change to 2.2k
MIC_BAIS
C9549 C9550 R33 3.9K
AGND
33.p 33.p R2 51K
AGND VALUE
R38
R1056 MIC_In
15K 1K 2.7V_IN_SHEELD
R2575 R2553 C24 33p MIC_BAIS
C9409 R21 change to 8.2k
15K 15K L4 U3 R26 560 6 8
R1104 330n R21
8 6 2 8 MC33202DR2 7
AGND 2.4K R24 560
5.6K 120n
vcc=8V_AUDIO,vee=AGND 7 C25 33p 1 5
5 3 R27 560 4
L2
U988 4 C12 R25 560
4
C1 R50
120n
MC33072 C38 33p 100NF 1uF RES_1000 U3
AGND C26 C27 C32 C33
R2551 MC33202DR2
R2473 R1069 AGND 33p 33p 33p
15K 33p
0. 39.K AGND VAG2
AGND C39 33p
2.7V_IN_SHEELD
AGND AGND R17
VAG C28 C68
470K
R1057 C8 22u 33p 33p C34 C35 VAG2
SPKR_Out
15K
C76 C104 33p 33p
C9561 1.u
8V_AUDIO R4 100n 33p
C2 R31
0
R2552 C40 C41 C36 C37 C30 C29 1uF
560K
15K 33p 33p 33p 33p 33p 33p
C9206
AGND
100n 2.2n
C13 AGND

C9378 R2550 R52

C9192
18.2K L5 R18 L6
100n 15K 330n R84 33.K
AGND AGND AGND 120n 15K 120n AGND
AGND U4
MC33202DR2

2.7V_IN_SHEELD
8 6
R29
560 C44 C47
C14

2.2n
Must be SHEELDED
7 33p 10n

5
AGND AGND C75 C103 4
100n 33p
C9567 SH1
C42 C43
33p C11 SHIELD
33p 33p
10n
VAG
R19
AGND R30 AGND AGND
15K
180K L12
VAG 1
120n
R28 Analog_Audio_OUT&POWER_On_Off
560
C45 C46
33p 33p C116 C117
33p 33p

DGND
AGND
DGND AGND

79B02963C88-O
SHEET 2 OF 6
 P5 EVALUATION BOARD - AUDIO
CR11 CR9 CR1

1PPS DSC_EN VCC

Model FTN8071A/B Must be SHEELDED

R62 R2570 R61
DNP
270 270 270
C70 4.7u

5V_Data
Q25 Print Split VCC
R85
DNP
0

GPS_1PPS_LED
DNP
C106 33p

C9539 C9569
R65
470K
DSC_Enable
U984
Print 5V regulator for L14
68u 220.n
L8
DNP
120n
22.u
R79 DGND DGND
Q14
4.7K
Q16 3906L
5V_Data
3904L Q3
5V_Data
DC_to_DC_12V DGND
D2 AGND
U980
LP2957IS
C9548
R68
100.n AUDIO_PA_12V
RES_10K 2 1
R66
5V_Data 5
OUTPUT INPUT
4 DGND J3-1
470K ERROR SHUTDOWN Q27
1
RS232_RI D1
GND U983
Q23 C9538 3 MAX771ESA To be Placed C115 C114
D5

100.u 1 4 33p 33p

EXT SHDN
SENSE 8 5 In the SHEELED
CS REF
2 3
V+ FB

AGND
GND
RS232_CTS R2554
C9564 C9563 C9537
DGND DGND DGND AGND DGND
Q22 0.1 C9547 VCC

6
100.u 100.u 100.u
100.n

DGND
VCC Q38

DGND 2 F1
RS232_RTS
DGND DGND
Q21
3 1 J3-2

LEDS
13mmx13mm PCB 2
S2 J3-3
R2598 VOLTAGE
Heatsink is needed 2.4K AMP
3

RS232_DSR
R2593
Q20
470.K

R2596
R2589 DGND
U992 22.K

RS232_DTR MC33072 221K

79B02963C88-O
Q19 8 2
1 D4 SHEET 3 OF 6

Voltage to MIC & AMP 4

3

RS232_DCD
R2594 R2597
VR10
Q18
0. C9579 8.2K 2.
100.n

R2527
100.K
RS232_RXD
DGND
Q4 AUDIO_PA_12V
8V_AUDIO

U978

LP2951C
RS232_TXD
8 1
Q11 GPS 3Volts REG 7
INPUT
FEEDBACK
OUTPUT
ERROR
5
3 2
SHUTDOWN SENSE
6
5V_TAP R2518

110.K C9536
U981 GND
LP2981 3 2 880_1800MHZ
RX_for_differential_gps_rtcm ON_OFF* 4
VCC
5 1 OUT
Q41 GPS_PWR VOUT VIN
C9386
4

GND
NC C9365
100n
3.3u
2
C9542
IN
CR2 CR10 CR8 CR7 CR6 CR5 CR4 CR3 47.u
1
TXD_UART_2
Modem_TXD Modem_RXD DCD DTR DSR RTS CTS RI R2519 R2521
Q39
0. 20.K
DGND DGND

RXD_UART_2

Q40 D6
LED_RED
Q15
3904L D7
R67 LED_RED
D8
2.4K
R64 LED_RED AGND
470K
R2600 R53 R63 R60 R59 R58 R57 R56 R55
R2601 R2599
270 270 270 270 270 270 270 270 270
270 270
DGND
 GPS Connector
DIN Connector F.
TX_EN DGND

RX_for_differential_gps_rtcm
DNP
5

SW2 R2595
To HOST

Input_I_O_custom_definition&sim_cr_det
MOMENT_SWITCH 0.

RXD_UART_2
Analog_Audio_OUT&POWER_On_Off

GPS_1PPS
2
DGND
R35
100

TS_Turn_on_stand_by
SIM_CR_Reset_RST

J127-10

10
J127-2

J127-4

J127-6

J127-8
DSC_Downlink

SIM_CR_Clock
DSC_Enable
RS232_DCD

RS232_RXD

RS232_RTS
IrDA_Select
DGND
d-10 To HOST d-15 To HOST
Analog_Audio_OUT&POWER_On_Off
RXD_UART_2

J125-2

J125-4

J125-6

J125-8

J125-10

J125-12

J125-14

J125-16

J125-18

J125-20

J125-22

J125-24

J125-26

J125-28
J129-1 TX_EN
J4-1 RS232_TXD
1 (GPS RXD on GPS modeles)

J127-1
1

J127-3

J127-5
5

J127-7
7

J127-9
9
J129-2 RXD_UART_2
J4-2 RS232_RXD
VCC
2 J129-3 TXD_UART_2 (GPS TXD on GPS modeles) S3 RX_for_differential_gps_rtcm
J4-3 RS232_DTR 3 SWITCH
VCC TXD_UART_2

3 J129-4 RS232_TXD 1 8 TS_Turn_on_stand_by

J4-4 RS232_DCD 4
5V_Data
4 J129-5 RS232_RXD S3 R2607 R2602

TXD_UART_2

GPS_Ant_Pwr3_to_5Vdc
J4-5 RS232_RTS 5 SWITCH 10K 100K
5 J129-6 RS232_DTR 2 7 SoftGSM_EN DGND

J125-11

J125-21
J125-1

J125-3

J125-5

J125-7

J125-9

J125-13

J125-15

J125-17

J125-19

J125-23

J125-25

J125-27
J4-6 RS232_CTS 6
for CSD call 5V_Data R2611 RS232_RI RS232_TXD
6 J129-7 RS232_DCD S3
1K
J4-7 RS232_DSR 7 SWITCH
PDP context indicator GPS_PWR
7 J129-8 RS232_RTS 3 6 LEDS_Enable
J4-8 RS232_RI 8

RS232_TXD
RS232_RI
SIM_CR_I_O_Data

SIM_CR_Vcc3_TO_5Vdc

RS232_DTR

MAN_TEST

TXD_UART_2

Analog_Audio_In

RS232_DSR

DSC_Uplink

RS232_CTS
8 J129-9 RS232_CTS S3
J4-9 MAN_TEST 9 SWITCH
TX_EN RS232_CTS RS232_RXD
9 J129-10 RS232_DSR 4 5
J4-10 Analog_Audio_In 10
10 J129-11 RS232_RI
J4-11 Analog_Audio_OUT&POWER_On_Off 11 DGND AGND
11 J129-12 MAN_TEST AUDIO PA ON Const - For D10 DGND
J4-12 Wake_up_gprs_coverage_indicator 12
2.7V
12 J129-13 Analog_Audio_In
J4-13 Input_I_O_custom_definition&sim_cr_det 13
13 J129-14 Analog_Audio_OUT&POWER_On_Off
RS232_RTS
J4-14 SIM_CR_Vcc3_TO_5Vdc 14
2.7V
14 J129-15 Wake_up_gprs_coverage_indicator
J4-15 SIM_CR_Reset_RST 15
15
SIM_CR_I_O_Data
J129-16 Input_I_O_custom_definition&sim_cr_det DIN Connector M.
J4-16 16
AUDIO_PA_12V
16 J129-17 SIM_CR_Vcc3_TO_5Vdc
J4-17 SIM_CR_Clock 17
17 J129-18 SIM_CR_Reset_RST
J4-18 TS_Turn_on_stand_by 18
RS232_DCD AUDIO_PA_12V
18 J129-19 SIM_CR_I_O_Data
J4-19 DSC_Enable 19 TX_EN
5V_Data
19 SIM_CR_Clock

Input_I_O_custom_definition&sim_cr_det
J129-20 5
J4-20 DSC_Downlink 20 DGND

Analog_Audio_OUT&POWER_On_Off
20 J129-21 TS_Turn_on_stand_by 5Volts P10-1
RS232_DTR GPS_1PPS
J4-21 DSC_Uplink 21
21
J4-22 AGND
J129-22
22
DSC_Enable
GPS_PWR
P10-3

L16
GPS_Ant_Pwr3_to_5Vdc P5 EVALUATION BOARD - INTERFACE

TS_Turn_on_stand_by
22 J129-23 DSC_Downlink 3Volts P10-2

SIM_CR_Reset_RST
22.u
J4-23 23
C9541 GPS_PWR

DSC_Downlink

SIM_CR_Clock
23 AGND J129-24 DSC_Uplink

RS232_DCD

DSC_Enable

RS232_RXD

RS232_RTS
IrDA_Select
3.3u
J4-24
24
J4-25
24
J129-25
25
AGND Model FTN8071A/B RS232_DSR

GPS_PWR
25 J129-26 DGND
J4-26 26 DGND

J126-1
1

J126-3
3

J126-5
5

J126-7
7

J126-9

J126-11

11

J126-13
13

J126-15

15

J126-17

17

J126-19
19

J126-21

21

J126-23

23

J126-25

25

J126-27
27
26 DGND J129-27 DGND
J4-27
Print Split
27 Speaker Jack
VCC DSC_Enable 5V_Data
27 J129-28 DGND
J4-28 28 DGND AGND J130
28 J129-29 DGND 1
J4-29 29
VCC LEDS_Enable 5V_Data
29 J129-30 VCC 3
VCC DHFA_SPKR_OUT
J4-30
Print
30
30 J129-31 VCC 4
EXT_B+
31 2
J129-32 VCC
3.0-6Vdc VCC
32

8
D3

10

12

14

16

18

20

22

24

26

28
J126-2

J126-4

J126-6

J126-8
J129-33 VCC

J126-10

J126-12

J126-14

J126-16

J126-18

J126-20

J126-22

J126-24

J126-26

J126-28
33
C9559
J129-34 GPS_Ant_Pwr3_to_5Vdc
34 470u

RS232_TXD
RS232_RI
SIM_CR_I_O_Data

SIM_CR_Vcc3_TO_5Vdc

RS232_DTR

MAN_TEST

TXD_UART_2
J129-35 RX_for_differential_gps_rtcm

Analog_Audio_In

RS232_DSR

DSC_Uplink

RS232_CTS
79B02963C88-O
35
J129-36 GPS_1PPS SHEET 4 OF 6
36 AGND

DGND AGND
 To the UUT BUTT-I 15 PINs BUTT-I I 15 PINs BUTT 12 PINs

To D-15
To d-10

Analog_Audio_OUT&POWER_On_Off
GPS_1PPS J128-1

Analog_Audio_OUT&POWER_On_Off
1
VCC

Analog_Audio_OUT&POWER_On_Off
RX_for_differential_gps_rtcm J128-2
2

Analog_Audio_In
GPS_Ant_Pwr3_to_5Vdc J128-3

DSC_Downlink

DSC_Enable
DSC_Uplink
J12-1 3

MAN_TEST
VCC 3.0-6Vdc

Analog_Audio_In
1 VCC J128-4

EXT_B+

Analog_Audio_In

DSC_Downlink
DSC_Downlink
J12-2 4

2.7V

DSC_Enable
C9578

DSC_Uplink
C9587 C9588

DSC_Uplink

DSC_Enable

MAN_TEST
MAN_TEST
2 VCC J128-5
100.p 100.p

EXT_B+
J12-3 220.n 5

2.7V
3 VCC J128-6

J2-10

J2-11

J2-12

J2-13

J2-14

J2-15

J2-16

J2-17

J2-18

J2-19

J2-20
C9556

J2-1

J2-2

J2-3

J2-4

J2-5

J2-6

J2-7

J2-8

J2-9
1

10

11

12

13

14

15

16

17

18

19

20
J12-4 6
4 2.2m J128-7
J12-5 7

J1-1
1

10

11

12

13

14

15

16

18

17

19

20
J1-10

J1-11

J1-12

J1-13

J1-14

J1-15

J1-16

J1-18

J1-17

J1-19

J1-20
5 DGND J128-8

J1-2

J1-3

J1-4

J1-5

J1-6

J1-7

J1-8

J1-9
J12-6 DGND DGND DGND DGND 8
6 DGND J128-9
C90 C89 C87 C93 C88

10

11

12

13

14

15

17

16
4

9
1

J13-10

J13-11

J13-12

J13-13

J13-14

J13-15

J13-17

J13-16
J13-4

J13-5

J13-6

J13-7

J13-9
J13-1

J13-2

J13-3

J13-8
J12-7 9 C74
33p 33p 33p 33p 33p
7 DGND J128-10 100n
J12-8 10
DGND 8 DGND J128-11
C91

DSC_Downlink
AGND_IN J12-9 DGND 11
33p C97 C92 C94 C95
U989 9 AGND_IN J128-12 DGND
33p 33p 33p 33p C96
J12-10 12 C72 100n
120n DSC_Uplink L13 33p
10 DSC_Uplink J128-13 DGND DGND
J12-11 120n 13 DGND
AGND DSC_Downlink DGND C98
DGND C86 33p
11 AGND DSC_Downlink J128-14
C85 C73 DGND 33p C99 C100 C101 C102 C71 C84
J12-12 14 DGND
DSC_Enable 33p 33p 33p 33p 100n 33p
12 DSC_Enable J128-15 33p 100n DGND

EXT_B+
TS_Turn_on_stand_by J12-13 15
13 TS_Turn_on_stand_by J128-16 DGND
J12-14 16 DGND
SIM_CR_Clock
14 SIM_CR_Clock J128-17 DGND DGND DGND

SIM_CR_I_O_Data J12-15 17
15 SIM_CR_I_O_Data J128-18
J12-16 18
SIM_CR_Reset_RST
16 SIM_CR_Reset_RST J128-19
SIM_CR_Vcc3_TO_5Vdc J12-17 19
17 SIM_CR_Vcc3_TO_5Vdc J128-20
Input_I_O_custom_definition&sim_cr_det
J12-18 20
18 Input_I_O_custom_definition&sim_cr_det J128-21
Wake_up_gprs_coverage_indicator
J12-19 21
19 Wake_up_gprs_coverage_indicator J128-22
Analog_Audio_OUT&POWER_On_Off J12-20 22 Diagnostic
20 Analog_Audio_OUT&POWER_On_Off J128-23
5V_Data AUDIO_PA_12V
Analog_Audio_In J12-21 23
21 Analog_Audio_In J128-24 5
J12-22 24
MAN_TEST
22 MAN_TEST J128-25

Input_I_O_custom_definition&sim_cr_det
J12-23 25
RS232_RI 23 RS232_RI J128-26 R2578 R2576 R2579
J12-24 26 10K
RS232_DSR C9581 C9580 C9572 C9571 100.K 10K
24 RS232_DSR J128-27
470.p 220.n STNDBY
J12-25 470.p 220.n 27

SIM_CR_Vcc3_TO_5Vdc
RS232_CTS
25 RS232_CTS J128-28

SIM_CR_I_O_Data
J12-26 DGND DGND 28 R2603
rs232_rt AGND AGND

DSC_Downlink

SIM_CR_Clock

RXD_UART_2
26 RS232_RTS J128-29 47K Q36 R2577
RF SMA Connector

DSC_Uplink

DSC_Enable

GPS_1PPS
J12-27 29
RS232_DCD TX_EN 10K
27 for CSD call/PDP context indicator RS232_DCD J128-30

Mute
J12-28 30
RS232_DTR
28 RS232_DTR J128-31 C9558 R2573
J12-29 31 10u 560.K
RS232_RXD
29 RS232_RXD J128-32
J12-30 32 MUTE

16

15

14

13

12

10

18

20

22
P11-16

P11-15

P11-14

P11-13

P11-12

P11-10

P11-18

P11-20

P11-22
7

9
P11-7

P11-9
M1 RS232_TXD
J124-5
5

1
J124-4

J124-3

J124-2

J124-1

30 RS232_TXD J128-33
Q37
CONTACT 33 Mute
3

L11
PIN3

(GPS TXD on GPS modeles) TXD_UART_2 J128-34 DGND

120n
34 R2574
C9566 2.7V_IN_SHEELD
(GPS RXD on GPS modeles) RXD_UART_2 J128-35 100K
0.5p C9589
35
100.p
TX_EN J128-36 C113 C112
PIN1
PIN2

C9590
36
100.p 33p 33p

11

21
P11-11

P11-17

P11-19

P11-21
4

2
P11-4

P11-1

P11-6

P11-3

P11-8

P11-5

P11-2
1
2

DGND

17

19
DGND DGND
ANT
DGND

NOTE:MIRROR TO G18/D15 DGND DGND AGND

P6-2

TXD_UART_2
TX_EN
RS232_RI

RS232_DSR

RS232_RTS

RS232_DCD

RS232_RXD

RX_for_differential_gps_rtcm
RS232_DTR
RS232_CTS

RS232_TXD
2

R2583
C9562 DNP
R2582 L17
P6-1
1
P5 EVALUATION BOARD - INTERFACE
4.7p
0.5p 0.5p 0.

DGND Model FTN8071A/B

DGND

Print Split Print

79B02963C88-O

SHEET 5 OF 6
 5V_Data

P5 EVALUATION BOARD - INTERFACE

5V_Data C9565

33.u

Model FTN8071A/B DGND

26
C9582

RS232_Present
VCC

Print
33.u
D9 MALE
GPS
Print Split 5V_Data C9546
100.n
28

25
C1+ V+
27

4
D9 FEMALE

DTE Orintation
C1- U979 V-
DGND U990 DCD J5-1
26 1 MAX3238E 1
MC14053B 16 C2+

28
VCC
27
R2612 270. P9-1
1
DHFA MIC VCC 6
C9543
330.n 3
T1OUT
5
RxD C9545 C9544 2 1 2 1
RxD J5-2
2
C1+ V+ RTCM_IN PC_TX EN C2- 330.n 330.n
R2614 0. P9-2 12 6 TxD J5-3
C9586 X0 T2OUT CTS VR4 VR3 2 1
100.n 25 4 R2617 DNP DNP R2616 0. 2 14 RS232_RXD 24 3
C1- U993 V- X T1IN MMBZ15VD
15 15 PC_RX 0. R2615 0. P9-3 13 11 DGND RS232_CTS 23 7 MMBZ15VD DTR J5-4
MAX3238E J111 RS232_RTS X1 A T2IN T3OUT DSR
1 3 2 RS232_DSR 22 DGND DGND VR2 4
C2+ DGND Y0 T3IN
C9585 5 PC_RX VR11 VR12 DGND 3Volt_VPP(NC) P9-4 15 RS232_DCD 19 10 MMBZ15VD RI J5-9
T1OUT C9583 C9584 Y T4IN T4OUT DCD 3 3
330.n 3 4 1 10 RS232_RI 17 9
C2- 330.n 330.n RS232_TXD Y1 B T5IN
6 1PPS 1PPS_RTN (GND) P9-5 5 12 DGND DGND DSR J5-6
T2OUT Z0 5V_Data T5OUT RI 3
TXD_UART_2 24 5 4 14 6
T1IN Z FORCEOFF RTS
GPS_1PPS 23 7 Ext_Backup_batt(NC) P9-6 3 9 J5-7
T2IN T3OUT RS232_DTR Z1 C DGND
22 15 DGND 6 C80 13 15 7

GND

VEE
T3IN FORCEON INVALID RS232_Present CTS
19 10 DGND DGND GND P9-7 33p J5-8
5V_Data T4IN T4OUT 2 4 3 1 R2580

7
17 VR14 DGND 7 16 8
T5IN 100K R1OUTB 2 1
12 3Volt(NC) P9-8 J5-5
T5OUT TXD_MUX
14 DGND 8 21 8 5
FORCEOFF DHFA_MIC_IN R1OUT R1IN TxD VR5 2 1
P9-9 L3
13 15 9 RTS_MUX 20 9 MMBZ15VD
FORCEON INVALID 120n R2OUT R2IN RTS
DGND DGND VR6
L7 C78 DTR_MUX R2565
16 18 11 DGND J5-10
R1OUTB 680p R3OUT R3IN DTR 3 MMBZ15VD
R2613 120n 3.9K 10

GND
21 8 RTCM_IN DGND
R1OUT R1IN 270.
3 2 1

2
J5-11
R2605 20 9 PC_TX 1PPS DGND 11
R2OUT R2IN VR16
12K 15 DGND VR9
18 11 P9-10
R2606 R3OUT R3IN DGND AGND MMBZ15VD
10 DGND
GND

12K
VR18
15 P9-11
RX_for_differential_gps_rtcm RXD_UART_2 2 1 3
2

11 DGND Connector SHEELD

2 1
DGND DGND
R2608 R2609
8.2K 8.2K VR8
DGND MMBZ15VD VR7
R2568 MMBZ15VD
100.
3
DGND DGND DGND
3
DGND

DGND

HeadSet Connctor.
Q29

EXT SIM Connections J118

SoftGSM_EN

HandSet adapter

DC_to_DC_12V Q26
12V_SW
DGND
RJ-45 Connector

SIM_CR_I_O_Data
2 4 3 1

Input_I_O_custom_definition&sim_cr_det
R70 C61 C9552 33p
SIM_CR_Vcc3_TO_5Vdc SoftGSM_EN
4.7K RJ-45 Connector DGND Analog_Audio_OUT&POWER_On_Off
C9573 10UF
C60 SoftGSM Switching circuit
220.n 10u DSC_Downlink DSC_Enable

J115-8

J115-7

J115-6

J115-5

J115-4

J115-3

J115-2

J115-1

1
U985
J10-8
8

J10-7
7

J10-6
6

J10-5
5

J10-4
4

J10-3
3

J10-2
2

J10-1
1

SIM_CR_Vcc3_TO_5Vdc
120n
DGND R69 C7 DGND C81 33p
R2559 R2560 Q28

SIM_CR_Reset_RST
R82 MIC_In
DGND 4.7K 2.2u

DSC_Downlink

DSC_Uplink

Analog_Audio_OUT&POWER_On_Off

Analog_Audio_In
100 22.K 22.K RTS

SIM_CR_Clock
Q17 C59 C82
S1
DSC_Downlink

DSC_Uplink

R20 7002 D SWITCH 10UF 33p R2558

C9551

7
Analog_Audio_In

4.7K G 22.K

S_VCC1

S_VCC2
Analog_Audio_OUT&POWER_On_Off

680p DGND
R83 DGND
DGND R2569 L1
DSC_Enable 0 0 SIM_CR_Clock 3 6 SIM_CR_I_O_Data
S S_CLK S_I|O 120n U991 Q32 Q30
2 4
S_PD S_RESET SoftGSM_EN
C83 33p

SIM-7
7

SIM-5
5

SIM-3
3

SIM-2
2

SIM-4
4

SIM-6
6

SIM-8
8

SIM-1
1
DGND Input_I_O_custom_definition&sim_cr_det

GND1

GND2
DGND 12V_SW DGND SIM_CR_Reset_RST DGND
C9568
VCC VCC 33p
U986 C79

8
C9570
DGND
220.n 120n 680p SPKR_Out

DGND
DGND DGND DGND DGND
DGND
AGND

79B02963C88-O
SHEET 6 OF 6
Parts List REFERENCE MOTOROLA
DESCRIPTION
SYMBOL PART NO.
Evaluation Board
C9540 2311049A07 CAPP_1u
Model FTN8071A P5 C9541 2113743G25 CAP_3.3u
C9542 2186201J02 CAP_22u
C9543-9545 2113743K17 CAP_330n
REFERENCE MOTOROLA C9546 2113743K15 CAP_100n
DESCRIPTION
SYMBOL PART NO.
C9547-9548 2113743E20 CAP_100n
Capacitors C9549-9550 2113740F39 CAP_33p
C1-6 2311049A07 ECAP_1UF C9551 2113741F21 CAP_680PF
C7 2311049A09 CAPP_2.2u C9552-9554 2113740F39 CAP_33p
C8-9 2311049J35 CAPP_22u C9555 2311049A07 CAPP_1u
C11 2113741F49 CAP_10n C9556 2313748E31 CAPP_2.2m
C12 2113743A19 CAP_100NF C9558 2311049A19 CAPP_10u
C14-15 2113741F33 CAP_2.2NF C9559 2380090M39 CAPP_470u
C24-30 2113740F39 CAP_33p C9560 2311049A07 CAPP_1u
C32-46 2113740F39 CAP_33p C9561 2113928A01 CAP_1u
C47 2113741F49 CAP_10n C9562 2113740F19 CAP_4.7p
C48-51 2113740F39 CAP_33p C9563-9564 2311049C13 CAPP_100u
C52 2113741F21 CAP_680PF C9565 2311049C08 CAPP_33u
C60 2380090M24 CAPP_10u C9566 2113740F01 CAP_0.5p
C62 2380090M24 CAPP_10u C9567-9568 2113740F39 CAP_33p
C68 2113740F39 CAP_33p C9569-9573 2113743A23 CAP_220n
C71-77 2113743A19 CAP_100NF C9578 2113743A23 CAP_220n
C78-79 2113741F21 CAP680PF C9579 2113743A19 CAP_100NF
C80-105 2113740F39 CAP_33p C9580-9581 2113740F67 CAP_470p
C110-117 2113740F39 CAP_33p C9582 2311049C08 CAPP_33u
C9185 2311049A57 ECAP_10UF C9583-9585 2113743K17 CAP_330n
C9190 2311049C05 CAPP_47u C9586 2113743K15 CAP_100n
C9192 2113743K17 CAP_330n C9587-9590 2113740F51 CAP_100p
C9201 2113743K17 CAP_330n CR1 4880304L02 LED_GRN
C9204 2113743E20 CAP_100n CR2-11 4880304L01 LED_RED
C9205 2311049A01 CAPP_0.1u Diodes
C9215 2113741F49 CAP_10n D1 4813833B01 MBRS140
C9219 2113741F25 CAP_1n D2 4813833A06 MBRD360
C9228 2113740F51 CAP_100p D3 4813833B01 MBRS140
C9241 2113740F51 CAP_100p D4-5 4813833A02 MBRD640
C9365 2311049A57 ECAP_10UF D6-8 4880304L01 LED_RED
C9378 2113743E20 CAP_100n Fuses
C9386 2113743E20 CAP_100n F1 0904923K01 SMD_FUSE_HOLD
C9409 2113743K17 CAP_330n Connectors
C9535-9536 9186929J01 880_1800MHZ J1-2 0909449B04 CONN_J
C9537-9538 2311049C13 CAPP_100u J3 3102151C30 CONN_P
C9539 2311049A24 CAPP_68u J4 2804989M01 EDGE

1
REFERENCE MOTOROLA REFERENCE MOTOROLA
DESCRIPTION DESCRIPTION
SYMBOL PART NO. SYMBOL PART NO.

J5 0909672B03 CONN_J Q39-41 4802393L34 FDV302P

J10 0983365N01 EDGE Resistors
J12 2804989M01 EDGE R2-3 0662057D17 RES_51K
J13 0909467R02 CONN_J R4 0662057B47 RES_0
J111 0909399T02 CONN_J R15 0662057B14 RES_470K
J115 0983365N01 EDGE R17 0662057B14 RES_470K
J118 0909399T02 CONN_J R18-19 0662057A77 RES_15K
J124 2886156U01 CONN_P R20 0662057A65 RES_4.7K
J125 0908606Y06 CONN_J R21 0662057A58 RES_2.4K
J126 2880471L02 CONN_P R22-23 0662057A81 RES_22K
J127 0908606Y05 CONN_J R24-29 0662057A43 RES_560
J128-129 0988716K01 CONN_J R30 0662057D30 RES_180K
J130 0909032K01 CONN_J R31 0662057B16 RES_560K
Coils R32 0662057A89 RES_47K
L1-7 2462587T16 IDCTR_120n R33 0662057A63 RES_3.9K
L10-13 2462587T16 IDCTR_120n R35 0611077D97 RES_100
L14 2503788S09 IDCTR_22u R38 0662057C75 RES_1K
L15 2462587T16 IDCTR_120n R50 0662057C75 RES_1000_1K
L16 2462587P28 IDCTR_22u R52 0662057R68 RES_18.2K
L17 249646M43 NO_DESC R53 0662057C61 RES_270
Contact R55-63 0662057C61 RES_270
M1 3903920K01 CONTACT R64-66 0662057B14 RES_470K
Connectors R67 0662057A58 RES_2.4K
P6 2880001R02 CONN_P R68 0662057A73 RES_10K
P9 2802837C03 CONN_P R69-70 0662057A65 RES_4.7K
P10 2880001R03 CONN_P R77 0662057A89 RES_47K
P11 2802935S09 CONN_P R78 0662057A87 RES_39K
Transistors R79 0662057A65 RES_4.7K
Q3 4803676A04 BSS123 R82 0611077D97 RES_100
Q4 4802393L34 FDV302P R83 0662057B47 RES_0
Q11 4802393L34 FDV302P R84 0662057A85 RES_33K
Q14 4813824A17 PNP_3906L R1056 0662057P02 RES_15K
Q15-16 4813824A10 NPN_3904L R1068 0662057A87 RES_39K
Q17 4813823A07 TMOSFETN_7002 R1098 0662057A71 RES_8.2K
Q18-23 4802393L34 FDV302P R1104 0662057A67 RES_5.6K
Q25 4803676A04 BSS123 R2468-2469 0662057B47 RES_0
Q26 4802393L04 BSS84 R2518 0611079E05 RES_110K
Q27 4813821A21 MTD20N03HD R2519 0662057B47 RES_0
Q28-30 4803676A04 BSS123 R2521 0662057P20 RES_20K
Q32 4803676A04 BSS123 R2527 0662057P95 RES_100K
Q36-37 4803676A04 BSS123 R2550-2552 0662057P02 RES_15K
Q38 4809807C24 SI4463 R2553 0662057A77 RES_15K

2
REFERENCE MOTOROLA REFERENCE MOTOROLA
DESCRIPTION DESCRIPTION
SYMBOL PART NO. SYMBOL PART NO.

R2554 0604648P05 RES_0.1 S2 4008241G06 SWIT_ET01

R2558-2560 0662057A81 RES_22K S3 4083849F04 SWITCH
R2564 0662057A55 RES_1.8K SW2 4004929K01 MOMENT_SWITCH
R2565 0662057A63 RES_3.9K Shields
R2568 0662057A25 RES_100 SH1 2604044K01 SHIELD
R2569 0662057B47 RES_0 SIM
R2570 0662057C61 RES_270 SIM 2808044H04 CONN_P
R2573 0662057B16 RES_560K Integrated Circuits
R2574 0662057A97 RES_100K U3-4 5113818A14 MC33202DR2
R2575 0662057A77 RES_15K U5 5104187K08 MAX603ESA
R2576-2577 0662057A73 RES_10K U978 5105469E65 LP2951C
R2578 0662057A97 RES_100K U979 5109781E76 MAX3238E
R2579 0662057A73 RES_10K U980 5104187K46 LP2957IS
R2580 0662057A97 RES_100K U981 5185963A04 LP2981
R2583 2113740F01 CAP_0.5p U982 5144751U01 TDA1519CTD
R2587 0662057A58 RES_2.4K U983 5108858K58 MAX771ESA
R2588 0662057A63 RES_3.9K U984 4803676A04 BSS123
R2589 0662057G31 RES_221K U985-987 2462587T16 IDCTR_120n
R2590 0662057B47 RES_0 U988 5113818A03 MC33072
R2593 0662057B14 RES_470K U989 2462587T16 IDCTR_120n
R2596 0662057A81 RES_22K U990 5113806A20 MC14053B
R2597 0662057A71 RES_8.2K U991 4803676A04 BSS123
R2598 0662057A58 RES_2.4K U992 5113818A03 MC33072
R2599-2601 0662057C61 RES_270 U993 5109781E76 MAX3238E
R2602 0662057A97 RES_100K Voltage Suppresors
R2603 0662057A89 RES_47K VR2-9 4813832C28 ZENER_MMBZ15VD
R2605-2606 0662057A75 RES_12K VR10 4813830G02 MMSZ4679T
R2607 0662057A73 RES_10K VR11-12 4813832C28 MMBZ15VD
R2608-2609 0662057A71 RES_8.2K VR14 4813832C28 MMBZ15VD
R2611 0662057A49 RES_1K VR16 4813832C28 MMBZ15VD
R2612-2613 0662057C61 RES_270 VR18 4813832C28 MMBZ15VD
R2614-2615 0662057B47 RES_0
Switches
S1 4009060S01 SWITCH