Developer’s Guide98-08901C39-B

© Motorola Communications Ltd., 2002A subsidiary of Motorola Inc.All rights reserved.

g18 GSM/GPRSOEM Embedded Module

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 commandsUpdate 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 ConsiderationsAdd 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.7Add 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.11Change 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 5Update 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.19Update Response/Action and Remarks columnsAdd to AT+CBST command noteUpdate 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.25Update Remarks in AT+CMGD command tableUpdate noteReplace 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.33Update command example

Update AT+CSMS command table, section 8.2.34

Change AT+CSQ command table with new table and example, section 8.2.35Update 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.37Update 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.44Update 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.53Add note to AT+CBAUD command, section 8.2.53Add 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.67Update example

Update At+CMSS command table, section 8.2.73Update example

Update note in AT+MMGR command, section 8.2.75

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

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

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

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

Add new AT command: AT+CSCB, Select Cell Broadcast Message Types, section 8.2.81Add exampleUpdate AT+CSCB command note (+CSCB Parameters)

Add new AT command: AT+MCSAT, Motorola Control SMS Alert Tone, section 8.2.82Add exampleUpdate AT+MCSAT command table, note and example

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

Add new AT command: AT+CSCR, SIM Card Reader, section 8.2.84Add 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.86Update AT+IPR command table

Add new chapter, g18 PC Loader Application, section 10Update g18 PC Loader Application chapter

g18 GSM/GPRSOEM 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......................................................................................................................................................xvi7. g18 Type Certification Identifications .........................................................................................................................xvii7. Safety............................................................................................................................................................................xvii

THE INTEGRATOR'S TASK1.1 GENERAL..............................................................................................................................................................................11.2 INTRODUCTION ..................................................................................................................................................................11.3 PLANNING THE PRODUCT AND CREATING THE DESIGN ........................................................................................1

1.3.1 Developing a Usage Model .........................................................................................................................................11.3.2 Developing a Message Model .....................................................................................................................................21.3.3 Defining a Service Strategy.........................................................................................................................................21.3.4 Defining Remote Diagnostic Functionality.................................................................................................................21.3.5 Investigating and Obtaining Regulatory Approval .....................................................................................................3

1.4 DEVELOPING AND VALIDATING THE HARDWARE...................................................................................................31.4.1 Designing the Hardware Platform...............................................................................................................................31.4.2 Considering Power Supply Options ............................................................................................................................31.4.3 Selecting the Source Antenna .....................................................................................................................................31.4.4 Setting Up a Development Test Environment.............................................................................................................3

March 2002© Motorola Inc., 2002 98-08901C39-B

1.5 DEVELOPING SUPPORTING APPLICATION SOFTWARE ........................................................................................... 31.6 TESTING AND APPROVING THE PRODUCT ................................................................................................................. 4

1.6.1 Setting Up a Final Test Environment ......................................................................................................................... 41.6.2 Installing and Field-Testing the Product .................................................................................................................... 4

1.7 RESOURCE ASSISTANCE.................................................................................................................................................. 41.7.1 Integrating Engineering Support ................................................................................................................................ 4

1.8 ENVIRONMENTAL ISSUES............................................................................................................................................... 51.8.1 General Precautions .................................................................................................................................................... 51.8.2 ESD Handling Precautions ......................................................................................................................................... 5

MODEL DESCRIPTION2.1 GENERAL ............................................................................................................................................................................. 72.2 INTRODUCTION.................................................................................................................................................................. 72.3 BASIC MODEL OVERVIEW............................................................................................................................................... 7

2.3.1 g18 DV Slim............................................................................................................................................................... 72.3.2 g18 DV Board Only – Horizontal............................................................................................................................... 82.3.3 g18 DVG/Slim............................................................................................................................................................ 8

2.4 D15 AND G18 DIFFERENCES............................................................................................................................................ 9

DESIGN CONSIDERATIONS3.1 GENERAL ........................................................................................................................................................................... 133.2 POWER SUPPLY CONSIDERATIONS ............................................................................................................................ 13

3.2.1 Power Supply Losses................................................................................................................................................ 133.2.2 g18 Current Consumption ........................................................................................................................................ 133.2.3 How/When to Wake Up the Unit ............................................................................................................................. 16

3.3 AUDIO CIRCUIT CONSIDERATIONS ............................................................................................................................ 173.3.1 Digital Audio ............................................................................................................................................................ 173.3.2 Analog Audio Without Hands Free .......................................................................................................................... 183.3.3 Analog Audio - Levels ............................................................................................................................................. 183.3.4 Analog Audio With Hands Free ............................................................................................................................... 20

3.4 DATA PORT CONSIDERATIONS.................................................................................................................................... 213.4.1 Data Levels ............................................................................................................................................................... 213.4.2 DTR Line and DCD Line ......................................................................................................................................... 223.4.3 Setting the Baud Rate ............................................................................................................................................... 22

3.5 SIM CARD CONSIDERATIONS....................................................................................................................................... 233.5.1 SIM Card Support..................................................................................................................................................... 23

3.6 ESD CONSIDERATIONS................................................................................................................................................... 233.7 ANTENNA CONSIDERATIONS....................................................................................................................................... 24

3.7.1 Antenna Systems ...................................................................................................................................................... 243.7.2 Antenna Safety ......................................................................................................................................................... 243.7.3 Antenna Performance ............................................................................................................................................... 243.7.4 Portable Devices ....................................................................................................................................................... 243.7.5 Fixed Devices ........................................................................................................................................................... 253.7.6 Antenna Test Methods.............................................................................................................................................. 25

3.8 MECHANICS - MOUNTING THE G18............................................................................................................................. 253.8.1 Fixed-Mount Usage .................................................................................................................................................. 253.8.2 Fastening Units with Housing .................................................................................................................................. 26

ii 98-08901C39-B

3.8.3 Fastening DIN Units..................................................................................................................................................263.9 CONNECTING THE M8989 HANDSET TO THE G18 ....................................................................................................263.10 GPS CONSIDERATIONS .................................................................................................................................................26

SOFTWARE INTERFACE4.1 GENERAL............................................................................................................................................................................274.2 MODEM COMMUNICATION MODES ............................................................................................................................27

4.2.1 Voice Communication...............................................................................................................................................274.2.2 Data Communication.................................................................................................................................................284.2.3 SMS Communication ................................................................................................................................................294.2.4 Fax Communication ..................................................................................................................................................29

4.3 BASIC OPERATIONS.........................................................................................................................................................294.3.1 Making a Voice Call .................................................................................................................................................294.3.2 Receiving a Voice Call..............................................................................................................................................294.3.3 Commencing Voice Communication .......................................................................................................................304.3.4 Making a CSD - Data Call ........................................................................................................................................304.3.5 Receiving a Data Call................................................................................................................................................304.3.6 Enabling Cell Broadcast (CB) Reception..................................................................................................................304.3.7 Setting Up the g18 in CSD Mode..............................................................................................................................31

4.4 SENDING AND RECEIVING DATA IN DIFFERENT FLOW CONTROLS ..................................................................314.4.1 Flow Control Set to Hardware Flow Control (FC) ...................................................................................................314.4.2 Flow Control - Flow Control Set to Xon/Xoff..........................................................................................................314.4.3 Flow Control Set to None..........................................................................................................................................32

4.5 CALL WAITING, CALL FORWARDING, AND CONFERENCE CALLS .....................................................................324.6 SENDING AN SMS .............................................................................................................................................................32

4.6.1 Sending an SMS in PDU Mode.................................................................................................................................324.6.2 Sending an SMS in PDU Mode - Wave Forms.........................................................................................................344.6.3 Sending an SMS in CSD Mode.................................................................................................................................344.6.4 Receiving an SMS.....................................................................................................................................................344.6.5 Sending and Receiving Binary Data Via SMS..........................................................................................................354.6.6 Receiving an SMS in CSD Mode - Wave Forms......................................................................................................354.6.7 Sending a Fax ............................................................................................................................................................434.6.8 Establishing GPRS PDP Context ..............................................................................................................................434.6.9 Changing the PIN Code Number ..............................................................................................................................444.6.10 Writing into the Fix Dialing (FD) Phone Book.......................................................................................................44

4.7 BASIC AT COMMANDS....................................................................................................................................................454.8 ERROR CORRECTION AND COMPRESSION (ECC) COMMANDS............................................................................494.9 FAX CLASS 1 COMMANDS .............................................................................................................................................494.10 ETSI 07.07 STANDARD ...................................................................................................................................................494.11 V.25TER COMMANDS USED WITH GSM....................................................................................................................534.12 ETSI 07.05 STANDARD (SMS)........................................................................................................................................55

4.12.1 Block Mode .............................................................................................................................................................554.12.2 Text Mode ...............................................................................................................................................................564.12.3 PDU Mode...............................................................................................................................................................57

MUX INTEGRATION5.1 GENERAL............................................................................................................................................................................59

98-08901C39-B iii

5.2 MUX INTEGRATION REQUIREMENTS......................................................................................................................... 595.3 MUX OPEN SERVICE ....................................................................................................................................................... 595.4 MUX CLOSE SERVICE ..................................................................................................................................................... 595.5 DATA TRANSFER ............................................................................................................................................................. 595.6 TWO CHANNEL LIMITATION ........................................................................................................................................ 595.7 SYSTEM BEHAVIOR ........................................................................................................................................................ 605.8 SUPPORTED PROTOCOL SERVICES ............................................................................................................................. 605.9 USER INTEGRATION........................................................................................................................................................ 61

5.9.1 Introduction .............................................................................................................................................................. 61

HARDWARE6.1 GENERAL ........................................................................................................................................................................... 636.2 HOST INTERFACE ............................................................................................................................................................ 63

6.2.1 Modem I/O Connector.............................................................................................................................................. 636.2.2 Interface Cable.......................................................................................................................................................... 63

6.3 ANTENNAS ........................................................................................................................................................................ 636.3.1 GSM Antenna ........................................................................................................................................................... 636.3.2 GPS Antenna (Recommendation) ............................................................................................................................ 646.3.3 Antenna Connector ................................................................................................................................................... 646.3.4 Antenna Cable Assembly ......................................................................................................................................... 64

6.4 DEVELOPER’S KIT ........................................................................................................................................................... 646.5 VENDOR CONTACTS ....................................................................................................................................................... 64

TESTING7.1 GENERAL ........................................................................................................................................................................... 697.2 TESTING STAGES ............................................................................................................................................................. 69

7.2.1 Hardware Integration ................................................................................................................................................ 697.2.2 Desense and EMI...................................................................................................................................................... 707.2.3 Regulatory Compliance ............................................................................................................................................ 707.2.4 Application Software ................................................................................................................................................ 707.2.5 Final Assembly ......................................................................................................................................................... 717.2.6 End User Problem Resolution .................................................................................................................................. 717.2.7 OEM Service Depot Repair ...................................................................................................................................... 71

7.3 DIAGNOSTIC UTILITY..................................................................................................................................................... 717.3.1 Quality Assurance Testing........................................................................................................................................ 717.3.2 Equipment Test Set-up ............................................................................................................................................. 72

AT COMMANDS8.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 BOARD9.1 GENERAL ......................................................................................................................................................................... 1739.2 EV BOARD ISSUE P4 ...................................................................................................................................................... 173

9.2.1 Connector Description ............................................................................................................................................ 1749.2.2 Jumper Description................................................................................................................................................. 175

9.3 EV BOARD ISSUE P5 ...................................................................................................................................................... 176

vi 98-08901C39-B

9.3.1 Connector Description.............................................................................................................................................1779.3.2 S3 Dip Switch Description......................................................................................................................................179

G18 PC LOADER APPLICATION10.1 GENERAL........................................................................................................................................................................18110.2 APPLICATION OPTIONS ..............................................................................................................................................181

10.2.1 Setting....................................................................................................................................................................18110.2.2 Programming.........................................................................................................................................................183

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

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

DESENSEC.1 GENERAL .........................................................................................................................................................................199C.2 DESENSE DEFINED ........................................................................................................................................................199

C.2.1 Noise Sources .........................................................................................................................................................199C.2.2 Receiver Susceptibilities.........................................................................................................................................200

C.3 MEASUREMENT TECHNIQUES ...................................................................................................................................200C.3.1 Packet Modem Integration Tester (PMIT) .............................................................................................................200C.3.2 Alternate Measurement Method .............................................................................................................................201C.3.3 Preparing the Device Under Test............................................................................................................................201

C.4 PERFORMANCE GOALS................................................................................................................................................201C.4.1 Radio Performance Capabilities .............................................................................................................................201C.4.2 Determine Emission Level Goals ...........................................................................................................................202

C.5 ACCEPTANCE ANALYSIS ON A SAMPLE DATA SET .............................................................................................202C.6 PREDICTION OF SOURCES...........................................................................................................................................202

C.6.1 Probability of Channel Interference .......................................................................................................................203C.6.2 Desense Scenarios ..................................................................................................................................................203

98-08901C39-B vii

C.7 METHODS OF CONTROLLING EMISSIONS .............................................................................................................. 203C.7.1 Shielding Approach ............................................................................................................................................... 203C.7.2 Alternate EMI Reduction Methods ........................................................................................................................ 204

C.8 RF NETWORK ISSUES................................................................................................................................................... 204C.9 ANTENNA........................................................................................................................................................................ 205

C.9.1 Field Strengths from the Antenna .......................................................................................................................... 205C.9.2 Antenna Interactions .............................................................................................................................................. 205C.9.3 Antenna Cable Routing.......................................................................................................................................... 205

C.10 DESENSE SUMMARY .................................................................................................................................................. 205

IP OVER AT COMMANDS LISTD.1 GENERAL ........................................................................................................................................................................ 207D.2 ENABLE IP OVER AT SERVICES +CIPE..................................................................................................................... 207D.3 DSC BUS IP PRIMITIVE OVER AT SERVICES +CIP ................................................................................................. 207D.4 IP PRIMITIVES SUPPORTED BY CIP .......................................................................................................................... 209D.5 REQUEST/CONFIRM PRIMITIVES .............................................................................................................................. 209D.6 UNSOLICITED PRIMITIVES ......................................................................................................................................... 209D.7 IP PRIMITIVES CIP SPECIFICATIONS ........................................................................................................................ 210

D.7.1 Class Indicator Primitives...................................................................................................................................... 210D.7.2 Power Down Primitives ......................................................................................................................................... 213D.7.3 Phone Book Related Primitives ............................................................................................................................. 213D.7.4 Display Indicator Primitives .................................................................................................................................. 215D.7.5 Call Control Interface Primitives........................................................................................................................... 216D.7.6 Call Status Indication Primitives ........................................................................................................................... 216D.7.7 Generate DTMF Signalling Primitives .................................................................................................................. 218D.7.8 Hook-switch Status Indicator Primitives ............................................................................................................... 219D.7.9 Microphone Mute Primitives ................................................................................................................................ 221D.7.10 SEEM Interface Primitives .................................................................................................................................. 221D.7.11 Idle SIM Card Notification Primitives ................................................................................................................ 223D.7.12 SIM Card Deactivation Notification.................................................................................................................... 223D.7.13 SIM Card Activation Notification Primitives...................................................................................................... 224D.7.14 SIM Card Security Notifications ......................................................................................................................... 224D.7.15 Attached Peripherals Primitives .......................................................................................................................... 228D.7.16 IP_HF_AUDIO_STATUS_IND.......................................................................................................................... 229D.7.17 IP_SET_RING_LEVEL_REQ ............................................................................................................................ 230D.7.18 IP_SET_RING_LEVEL_CNF ............................................................................................................................ 230D.7.19 IP_LOW_VOLTAGE_IND................................................................................................................................. 231D.7.20 IP_GET_HF_VOLUME_REQ........................................................................................................................... 231D.7.21 IP_GET_HF_VOLUME_CNF ............................................................................................................................ 231D.7.22 IP_LTC_ERASED_IND...................................................................................................................................... 232

D.8 IP PRIMITIVES CIP EXAMPLES................................................................................................................................... 232

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

INDEX

viii 98-08901C39-B

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

98-08901C39-B ix

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

x 98-08901C39-B

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

98-08901C39-B xi

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

xii 98-08901C39-B

USING THIS GUIDEThis guide presents critical research and development issuesaffecting the design and development of productsincorporating the Motorola g18 900/1800/1900MHz GSM/GPRS Integrated Wireless Modem, used in NorthAmerica, Asia, Africa and Europe.

The purpose of this document is to describe the technicaldetails needed to integrate g18 Tri-band 900, 1800 and 1900MHz Data Module into a host device. The g18 Data Moduleis the next generation that replaces the current d15 DataModule. There are several configurations of this product thatprovide flexibility in meeting full system integrationrequirements, as described in this manual.

PURPOSEData terminal equipment (DTE) OEM teams are often pulledtogether quickly from other work groups. For this reason,OEM team members often need advice about how to bestsustain a concerted design and development effort. Thepurpose of this guide is to assist your team to successfullyproduce a wireless product that integrates the Motorola g18wireless modem.

This guide strives to bridge the gap between the variousengineering and business disciplines that make up OEMteams. Our approach is to provide a practical disclosure ofuseful information that can offer a common understanding ofthe problems you may encounter and examples of probablesolutions.

We at Motorola want to make this guide as helpful aspossible. Keep us informed of your comments andsuggestions for improvements. You can reach us by email at: GSM support-BSH015@email.mot.com

INTENDED AUDIENCEThe intended audience of this manual are data terminalequipment (DTE) OEM integration team members. Teamshistorically consist of representatives from the disciplines ofhardware, software and RF engineering. These readers willprobably find the entire document useful, if not enlightening.Other readers include marketing, business, and programmanagers. These readers might find the first chapter, whichdiscusses the integrator’s task, to be sufficiently informativefor their needs. The remaining chapters go into more detail.

DISCLAIMERThis guide provides advice and guidelines to OEM teams.Responsibility regarding how the information is used liesentirely with the OEM. Statements indicating supportprovided by, or offered by, Motorola are subject to change atany time.

Motorola reserves the right to make any changes to thismanual.

REFERENCE DOCUMENTSElectromagnetic Compatibility: Principles and Applicationsby David A Weston, published by Marcel Dekker, Inc., 270Madison Avenue, New York, NY 10016 USA.

GSM 07.07 - prETS 300 916, Digital cellulartelecommunication system (Phase 2+); AT command set forGSM 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 Circuitterminating; Equipment (DTE-DCE) interface for ShortMessage Service (SMS) and Cell Broadcast Service (CBS),Version 5.3.0, August, 1997, ReferenceTS/SMG-040705QR2.

GSM 03.40, Digital cellular telecommunication system(Phase 2+); Technical realization of the Short MessageService (SMS) Point-to-Point (PP), Version 5.3.0, July1996, 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 EngineeringDocuments, 15 Inverness Way East, Englewood, Colorado80112-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

Note

A product that incorporates the modem isreferred to as the Original EquipmentManufacturer (OEM) host or simply the host.

98-08901C39-B xiii

GSM Data Adapter for Motorola Handsets, AT commandreference, Rev 2, June 9 1997.

ETSI standard SMG31.

GSM 05.02.

ETSI 07.60.

ETSI 0.7.07 Ver. 7.5.0.

CUSTOMER ASSISTANCEThis page is to be used as a source of contact information forany possible queries that may arise.

• Have questions? • Trouble getting the evaluation board set up?• Technical questions?• Configuration questions/problems?• Technical operating problems?• Need documentation?The GSM Data Module Customer Support Center is ready toassist you on integration issues.

• The help desk phone number is: +972 (0) 3 568-4040• Email: BSH015@email.mot.comAt Motorola, total customer satisfaction is a top priority. Ifyou have a question, a suggestion or a concern about yourMotorola g18 product, we would like to hear from you.

Please contact the Motorola Cellular Response Center by faxon +44 (0) 131 458-6732 or use one of the local phonenumbers in the following countries for general productinquiries.

Austria 0800 297-246

Belgium 0800 72-370

Canada 1 (800) 461-4575

Denmark 4348-8005

Finland 0800 117-036

France 0 803 303-302

Hong Kong 2506-3888

Ireland (01) 402-6887

Italy (02) 696-333-16

Luxembourg 0800 21 99

Netherlands 0800 022 27 43

Norway 22 55 10 04

People’s Republic of China (10) 6846-6060

Portugal (21) 318-0051

Singapore 485-5333

Sweden (08) 445-1210

Switzerland 0800 553-109

UK 0500 55 55 55

United States of America 1 (800) 331-6456

Accessory Items Available to Aid the Developer

Developer Kit S9002x

Handset with SIM CR SCN50011x

Handset without SIM CR SCN50012x

Headset SYN6962

Headset SYN4937

Microphone SMN4097

Speaker SNN4018

GPRS Manager SVN4503

Short Flex Cable 50mm 3086229J10

Long Flex Cable 300mm 3086229J09

Coax Cable 200mm (MMCX/SMA) 3085720G01

If you wish to place an order, please contact your AccountManager. A list of Motorola Account Managers is availableat www.motorola.com/automotive/telematics/. ClickProducts > Data Modules > Contact Us.

REGULATORY REQUIREMENTS

Investigate and Obtain Regulatory Approval

Most countries where the final product will be sold currentlyrequire approval from the local government regulatory body.It is your responsibility to investigate and obtain the properregulatory approval and certification for each country inwhich the product is sold. Motorola can provide the contactnames and phone numbers of the regulatory bodies in eachcountry.

You are required to obtain regulatory approval of productsthat integrate a g18 integrated wireless modem. The specificdetails for achieving regulatory approval may vary fromcountry to country.

xiv98-08901C39-B

Worldwide, government regulatory agencies forcommunications have established standards andrequirements for products that incorporate fixed, mobile,and portable radio transmitters. To this end, Motorolaprovides g18 modems as certified in specific regionalmarkets to levels of compliance appropriate for an integrateddevice. Approval is required for two interrelated reasons, toguard public safety and to ensure electrical non-interference.

UL, CSA, and other safety approvals are not required. InAustralia, AUSTEL safety approval is required of networkoperators, meaning that the network operators might passAUSTEL safety requirements through to the deviceintegrators.

Full-Product Certification

As the integrator, you must determine what additionalspecific regulatory requirements are required of the countryin which your product is marketed. This means that yourproduct must be individually certified, even though the g18modems are already approved. The certification processincludes submittal of prototype products and acceptable testresults.

The certification process for your product can take from afew weeks to several months. Its duration can be affected bysafety requirements, the type of product, and the country inwhich you are seeking approval.

Country Requirements

These country requirements are provided as a generalorientation to the certification processes in specific regionsand countries. You are strongly encouraged to use theservices of a consultant or a full-service test house if youhave limited expertise in meeting the regulatoryrequirements of a specific country.

Countries of the European Union and EFTA

Since April 8th 2000, radio and telecommunicationequipment are regulated under directive 1999/5/EC of theEuropean Union. This directive is referred to as the R&TTE.

For equipment within its scope, the R&TTE supersedes theTelecommunication Terminal Equipment directive (TTE98/13/EC), the Electromagnetic Compatibility Directive(EMC 89/336/EC) and the Low Voltage Directive (LVD 73/23/EC).

The R&TTE and important information about it, ispublished by the European Commission under the followingweb 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 demonstratecompliance 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 terminalequipment.

The implication of the R&TTE is that integrators of the g18will need to raise their own Declaration of Conformity underthe R&TTE using Annex III, IV or V.

Motorola recommends that integrators of the g18 documenttheir compliance activities in a technical construction file.The Motorola test report for the g18 can be used todemonstrate compliance with article 3.2 of the R&TTEunder 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 willbe available upon request from Motorola. Requests shouldbe made to your contact person within Motorola. Careshould be taken as a product might fall under the scope ofother directives or standards depending on the type ofproduct.

The g18 is not approved under the automotive directive(95/54/EC), as it cannot be connected directly to the powersupply or other systems of a vehicle without havingadditional electronic interfacing.

Host Device Requirements

The host device requirements for the EU and EFTAcountries are:

• If the host device controls the g18 and technically doesnot change it, no additional g18 test is required for the(R&TTE) directive for FTA.

98-08901C39-B xv

• EN 301 489-1 and EN 301 489-7 for EMC on the hostdevice. Ensure that there is no technical differences toETS300 342-1. If the host device is a portable or fixedapplication, the CE mark is required. If the host device isin 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 TypeCertification scheme as setup by the PCS 1900 TypeCertification Review Board (PTCRB) and is listed as PCS1900 Type Certified product. This certification will beinvalidated 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.

United States of America

The Federal Communications Commission (FCC) requiresapplication for certification of digital devices in accordancewith CFR Title 47, Part 2 and Part 15. This includesElectromagnetic Energy Exposure (EME) testing. As theg18 modem is not a standalone transceiver but is anintegrated module, the g18 cannot be tested by itself forEME certification. It is, however, your responsibility to haveyour completed device tested for EME certification.

Host Device Requirements

The host device requirements are:

• If the host device controls the g18 and technically doesnot change it, FCC CFR 47 part 24 is not required as it iscovered by the g18 approval.

• FCC CFR part 15 needs to be completed as this applies tothe end product, including EME (Electromagnetic EnergyExposure) for a portable application.

• The FCC ID label must be easily visible from the outsideof the equipment enclosure. However, it does not have tobe visible at all times, such as when a battery covers thelabel or is embedded in a host device. In any case, thelabel must not be removed from the g18. It isrecommended to add a label to the outside of the host withthe following information: “FCC ID: ID IHDT6AC1 iscontained within.”

Canada

This class B device also complies with all requirements ofthe Canadian Interference-Causing Equipment Regulations(ICES-003).

Cet appareil numérique de la classe B respecte toutes lesexigences du Règlement sur le matériel brouilleur duCanada.

Regulatory Statement

The following regulatory statement for the E.E.A applies tothe g18 type MG1-4F21 only:

1. The g18 must be operated at the voltages described inthe technical documentation.

2. The g18 must not be mechanically nor electricallychanged. Usage of connectors should follow theguidance of the technical documentation.

The g18 is type approved under CTR 5 ed.2 and CTR 9ed.2. Using different external card readers or handsetsother than those approved by Motorola will invalidatethe type approval and require retesting and re-approvalby the British Approval Board – Telecommunications(BABT). Such testing can only be carried out with priorapproval of Motorola. It must be noted that CTR 5 ed.2and CTR 9 ed.2 are expected to be repealed by October24th. 1998, but changes approved prior to that date canbe marketed after October 24.

3. The g18 has been designed the meet the EMCrequirements of ETS 300 342.

4. When integrating the g18 into a system, Motorolarecommends testing the system to ETS300342-1.

5. The g18 meets the safety requirements of EN60950.

6. Systems using the g18 will be subject to mandatoryEMC testing under directive 89/336/EEC and onlyoptional (see 3.) GSM type approval testing underdirective 98/13/EEC. Other directives like the LVDdirective 73/23/EEC might also be applicable to asystem using g18.

Note

Host device PTCRB approval is required.

xvi98-08901C39-B

7. The g18 is type approved at BABT. Changes subject totype approval should be communicated to Motorola andBABT, and are not subject for discussion with otherNotified Bodies.

The above statement has been made on the basis ofMotorola’s long experience in GSM type approvals for theE.E.A. and reviews with BABT of the UK. Motorolarecommends that integrators of the g18 consult Motorola inthe design phase to clarify any regulatory questions.

g18 Type Certification Identifications

Europe MT3-411A21

US FCC ID IHDT6AC1

Canada CANADA 109331257A TYPE ACPA or CAN109331257A TYPE

PTCRB g18

Safety

User OperationDo not operate your telephone when a person is within 8 inches (20 centimeters) of the antenna. A person or objectwithin 8 inches (20 centimeters) of the antenna could impaircall quality and may cause the phone to operate at a higherpower level than necessary.

IMPORTANT: The telephone must be installed in amanner that provides a minimum separation distance of 20 cm or more between the antenna and persons to satisfyFCC RF exposure requirements for mobile transmittingdevices.

IMPORTANT: To comply with the FCC RF exposurelimits and satisfy the categorical exclusion requirements formobile transmitters, the following requirements must bemet:

Antenna Installation• A minimum separation distance of 20 cm needs to be

maintained between the antenna and all persons,otherwise a SAR test will be required.

• The transmitter effective radiated power must be less than3.0 Watts ERP (4.9 Watts or 36.9 dBm EIRP). Thisrequires that the combination of antenna gain and feedline loss does not exceed 16 dBi.

98-08901C39-B xvii

xviii98-08901C39-B

98-08901C39-B

1. THE INTEGRATOR'S TASK

1.1 GENERALThis chapter provides background information and indicatesthe objectives and tasks required to achieve a successfulimplementation.

Figure 1. Integrator’s Tasks

1.2 INTRODUCTIONAs an OEM integrator, you must accurately choose whereand how wireless technology will facilitate communicationfor your customers. You will also have to evaluate whichtechnical considerations will give your product an edge overthe competition.

To successfully integrate g18 wireless modems into theirhost 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

As you review these tasks, allow sufficient time for requiredactivities, such as the regulatory approval process, (see“Regulatory Requirements”, page xiv) to identify criticalpath activities ahead of time.

1.3 PLANNING THE PRODUCT AND CREATING THE DESIGN

To plan the product and create the design, perform thefollowing 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 endproduct be used - will it be portable or mobile, how manyhours a day will it be used, how many days a week?” and soon.

Perhaps the most important factor for success is a clearunderstanding and decision regarding how the final productis to be used. This guides the development process, since alldesign considerations drive toward meeting the needs of theend user. For example, design issues related to a mobiledevice, such as alternator noise and vibration, are completelydifferent from considerations required for a fixed-pointtelemetry application powered by a solar panel. Definingwhat is and is not important to the end user helps to make thecritical engineering trade-off decisions that are inevitable inevery product design.

As the integrator, it is your responsibility to develop theusage model. Motorola is available to provide assistance andanswer questions, but is not directly involved in this phase ofthe 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 messagemodel, determine the quantity and frequency of data sent ineach of the uplink (terminal to network) and downlink(network to terminal) directions.

Answer the question, “Is there a requirement for the terminalto be powered on and ready to receive eight hours a day, ordoes the user turn the unit on only when making a query tothe host system?” The answer has a direct bearing on thebattery size and capacity requirement for powering thedevice. The amount of data sent and received is relevant incalculating the cost of airtime and deciding which type ofnetwork connection to use. In short, the message model isessential for making many engineering design decisions,especially in calculating values such as sleep time versuswake time and in determining battery capacity requirements.

You are responsible for developing the message model. Thetypical approach to creating the model is to define the peakand average network throughput requirements based oninput from the user. Motorola can provide currentconsumption figures for each of the various modes ofoperation, for example, receive and transmit.

The network throughput of the host device depends onvarious factors, in addition to the raw throughput of the radiochannel. For example, in addition to the overhead involvedin forward error correction and support for packet headers,the number of active users on the network can directly affectnetwork throughput.

1.3.3 Defining a Service Strategy

The service strategy determines whether the integratedmodem is the cause of a user’s problem and sets a policy forkeeping the end user operational during repair. The servicestrategy must consider all potential service situations andevaluate them in light of the usage model. You can create theservice strategy jointly with Motorola. Contact your Motorola OEM sales representative for details.

To ensure that a final product can be efficiently serviced, itis recommended that you design for serviceability early inthe R&D process. At a minimum, you could develop afunctional service strategy that contains a well-consideredprocedure for performing unit-level screening. The test mayprimarily determine whether a fault lies with the modem orwith the product. The test must also screen for networkproblems and human error.

Motorola supplies an evaluation board (a standalone testfixture) that provides a mounting platform and electricalinterface to the modem. (Refer to Chapter 9, “g18 Evaluation

Board”, page 173, for further information.) Testing isperformed much more efficiently when the modem isintegrated within the OEM host, whether for a factoryend-of-line test or while at the user’s site. (Refer toAppendix B, “Quick Start”, page 197, for furtherinformation.)

In order for your product to allow integrated testing of themodem, you may decide to provide a modem pass-throughmode.

A thoroughly developed OEM serviceability plan typicallyincludes a needs assessment for developing software utilitiesthat can assist in identifying communication problemsbetween the product and the modem and between the modemand the RF network.

These utilities must be able to send commands to themodem, evaluate the modem responses, perform networkconnectivity testing, and verify data communication with thenetwork.

Such a software utility is essential for field service engineersand shop technicians to diagnose problems with the productand to troubleshoot a problem to a failed assembly ormismanaged communication link.

1.3.4 Defining Remote Diagnostic Functionality

When customer problems are reported from the field, youmust isolate the source of the problem remotely. You willneed to determine which part of the overall system is notfunctioning correctly. The following items need to beconsidered 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 ofhow to use the product correctly. Regardless, remotetroubleshooting is essential in reducing the number ofreturned products and lowering service costs, particularly ifthe host must be disassembled in order for the modem to beremoved.

Motorola recommends that your product application (both atthe terminal and host ends) incorporates sufficient problemdiagnostic software to determine the cause of the problemremotely. Often, the best approach is to incorporateprogressively deeper loopback tests to determine the point atwhich the communication link fails.

This remote diagnostic functionality should be an integralpart of your standard software load.

2 98-08901C39-B

The Integrator's Task

1.3.5 Investigating and Obtaining Regulatory Approval

It is your responsibility to obtain regulatory approval ofproducts that integrate a g18 Integrated Wireless Modem.The specific details for achieving regulatory approval varyfrom 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 thefollowing 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 designrequires many steps. Here again, the usage and messagemodels are necessary to calculate issues such as battery size,heat dissipation, isolation from EMI, and physical mountingof the unit to ensure proper grounding. Refer to Chapter 3,“Design Considerations”, page 13, for further information.

Hardware design is your responsibility. Motorola canprovide recommendations where applicable, and can alsoprovide a one-time verification of EMI-caused desense withthe modem integrated into the host. To clarify, the hostdevice can introduce electromagnetic interference, whichwill interfere with the performance of the modem. This EMIcan be conducted into the modem via the serial and powerlines, or radiated into the antenna and antenna cable. It isyour task to minimize the generation of EMI by your deviceso 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 andmessage models. In addition to accounting for the currentdrain of the modem in its various operating modes, youshould also consider ripple and noise on the power lines andthe ability to supply sufficient instantaneous current toenable correct operation of the transmitter. You should alsoensure that your power supply can accommodate the highest

power consumption for the g18 modem that you want tointegrate.

Together, these requirements define the type and size ofpower supply (for example, linear versus switched) to usewith the wireless modem. Refer to Chapter 3, “DesignConsiderations”, 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 considerthese network requirements when you select an antennasystem. Refer to “Antenna Considerations”, page 24, forfurther information.

You are responsible for selecting a suitable antenna andsubmitting the final product to the network operator forcertification.

1.4.4 Setting Up a Development Test Environment

A number of development test aids are available to assist inhardware and application development. Modem hardwareand an evaluation board can be purchased from Motorola.The evaluation board is a specially developed circuit boardwith test points and jumper switches, which allows formaximum flexibility in accessing and controllingconnections 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 canhelp 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 environmentsupported by Motorola. This development network, onwhich you can develop and test your application, is separatefrom the production network. You must negotiate directlywith the network operator for airtime and for building andmaintaining a development test environment at their facility.

1.5 DEVELOPING SUPPORTING APPLICATION SOFTWARE

To develop supporting application software, perform thefollowing steps:• Select a communications model• Develop end-to-end application software

98-08901C39-B 3

The Integrator's Task

1.6 TESTING AND APPROVING THE PRODUCT

To test and approve the product, perform the followingsteps:• Perform EMI and desense testing (Refer to Appendix C,

“Desense”, page 199, for further information.)• Set up a final test environment• Install and field-test the product

1.6.1 Setting Up a Final Test Environment

To ensure correct assembly of the final product (that theantenna is properly connected, the serial port is operational,and so on), perform an end-to-end test that proves that thefinal product can receive and transmit at the required signallevels. In locations where the final assembly test isperformed within network coverage area, this test isrelatively simple. However, in locations where networkcoverage is not available, or for products being shipped toother countries, it is necessary to test by secondary means.

The final assembly test must verify that all connections tothe modem are made correctly. Testing on a network is notrequired.

1.6.2 Installing and Field-Testing the Product

When the product is shipped to a site, it is installed ormounted in a location that may restrict RF communications.It must be verified whether the behavior of a dysfunctionalproduct is caused by poor coverage or is due to the fact that

the network service provider is down. To guarantee that themodem is located in an area with good coverage, and that anend-to-end loopback message is possible, your productneeds a software application to perform the test.

The most effective approach to field-testing is to include aninstallation test procedure as part of your standard softwareload. Motorola can recommend specific network informa-tion that you can obtain from the modem describing how toimplement an end-to-end loopback test. Refer to Chapter 7,“Testing”, page 69, for further information.

1.7 RESOURCE ASSISTANCEDeveloping and testing a wireless integrated productrequires a well-equipped development lab and access toresources and outside information. Table 1, “Parts and ToolsRequirements”, below, identifies the required developmentand service tools. Information is also provided regardingwhere to obtain the tools and how to obtain furtherassistance.

1.7.1 Integrating Engineering Support

Questions on this manual and the integration process arehandled by Motorola’s integration engineering teamslocated in Europe and North America.

Send an email to BSH015@email.mot.com, with yourname, phone number, company name, description of theproject and your question. An engineer will be assigned toyour project and will contact you by phone or by email toassist you in resolving any issues.

Table 1. Parts and Tools Requirements

Related Documentation

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

www.etsi.org

Unique Development and Service Aids

Host Evaluation Board Kit P/N S9002This 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

1.8 ENVIRONMENTAL ISSUESg18 Integrated Wireless Modems are designed for acombination of easy serviceability and general robustness.These integrated modems are designed to be housed in anOEM host product. The modem is tested to conform to theenvironmental levels (for example, industrial usespecifications and PC card standards) that meet the intendedapplications of most integrators. If you need additionalrobustness and safety in your products, you must engineerthe environmental characteristics of your host product toachieve a special safety rating.

1.8.1 General Precautions

Follow these precautions when working with wirelessmodems:• 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.

1.8.2 ESD Handling Precautions

All electronic devices contain components that are sensitiveto ESD (electrostatic discharge). For example, peopletypically experience up to 35 kV ESD, while walking on acarpet in low humidity environments. In the same manner,many electronic components can be damaged by less than1000 V of ESD. For this reason, you must observe thefollowing handling precautions when servicing thisequipment:• 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 inESD-protective containers.

• Disconnect all power from the unit before ESD-sensitivecomponents are removed or inserted, unless instructedotherwise.

• Use a static safe-guarded workstation, which can be setup by using an anti-static kit (Motorola part number0180386A82). This kit includes a wrist strap, two groundcords, a static control table mat, and a static control floormat. The Motorola part number for a replacement wriststrap that connects to the tablemat is 4280385A59.

Modem Test Equipment

GSM Test SetGPS Test Set

Rohde and Schwarz CMU 200 with GPRS optionHewlett Packard 8960 with GPRS optionWelnavigate GS700 or GS1010

www.rsd.dewww.hp.com

Wireless Verification Equipment

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

Traditional Shop Equipment

Power Supply

OscilloscopeDigital Volt Meter

Dual Power Supply with 3-6V/2A and 12V/2A output supplies(12V for optional hands-free only – g18 EV board)900Mhz, digital storageFluke 77 multimeter or equivalent

Commercial Items

Commercial ItemCommercial Item

Table 1. Parts and Tools Requirements (Continued)

98-08901C39-B 5

The Integrator's Task

When anti-static facilities are unavailable, use the followingtechnique to minimize the chance of damaging theequipment:• 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

surface first and maintain this contact while handling thecomponent.

• If possible, maintain relative humidity of 70-75% indevelopment labs and service shops.

Note

g18 was tested for ESD according to EN 61000-4-2.

6 98-08901C39-B

98-08901C39-B

2. MODEL DESCRIPTION

2.1 GENERALThis chapter provides an overview of the different g18integrated wireless modem models, including accessories,physical and electrical characteristics, features andfunctional capabilities, and the data-exchange network overwhich they communicate.

For model numbers, supported languages and specifications,Refer to “Specifications”, on page 187.

2.2 INTRODUCTIONThe g18 modem supports the following modes of operation:1. A Phase II + GSM class 4 embedded module package

with voice, data, fax, and short message service (SMS)support.

2. GPRS module supporting packed data communicationin 900/1800/1900 MHz bands.

The g18 GPRS features include full over-the-air Class Bfeatures using a handset with multi-slot Class 1, 2 and 4. Inaddition, CS1-CS4 GPRS coding schemes are supported(coding schemes are used to manage the error rate in thetransmission of data to the mobile).

If you have both RS232 and DSC bus interfacing g18, youhave GPRS class B ability, meaning that you can answer avoice call, while in GPRS mode. It provides the samefunctionality as if a handset is connected, since this is alsoDSC bus.

The g18 is designed to support a range of subsidiary servicesassociated with navigation, emergency services, road tolls,security systems (such as car alarms and fire alarms), as wellas integrated standard voice/data/GPRS communication.Applications where data modules can provide these benefitsinclude automotive telematics, mobile computing, assetmanagement, remote utility meter reading, street lightcontrol, home security, vending and copy machinemanagement, fleet management, ATM security, POSconnectivity, household appliance monitoring and control,

display systems, load management and more. To support thisflexibility, the same functionality is offered in severaldifferent configurations. GPS capability is also provided inan additional configuration.

The g18 modem relies on system software for basicoperational instructions and on configuration parametervalues to meet modem and network interface requirements.

The g18 is designed for use in a system environmentcomprising a GSM mobile radio network with one or moreradio operators per country. There is a basic requirement ofa corresponding infrastructure of a configuration levelsuitable for the use of terminal devices with 2 Wtransmission power.

2.3 BASIC MODEL OVERVIEW

2.3.1 g18 DV Slim

This configuration is the smallest packaged module, whichmeasures 44.28 mm x 88.45 mm x 10.4 mm.

Figure 2. g18 DV Slim Data Module

7

Model Description

2.3.2 g18 DV Board Only – Horizontal

The Horizontal Board Only product provides the smallestvolume with a horizontal connection.

Figure 3. g18 DV Board Only – Horizontal Connection

2.3.3 g18 DVG/Slim

The DVG Slim configuration provides GPS (GlobalPositioning System) capability housed on the same packageas the GSM data module. This allows developers to saveintegration space when location information is required.

Figure 4. g18 DV GPS Data Module

8 98-08901C39-B

Model Description

2.4 d15 AND g18 DIFFERENCESThe 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 10 in DIN connector. "Port-out" - Not used.

Pin 15 in ZIF connectorPin 10 in DIN connector "wake up line" (awake g18, Awake DTE, GPRS coverage). Refer to “Data Communication”, on page 28.

Pin 2,3 in ZIF connector - Not used.Pin 16,15 in DIN connector - Not used.

Pin 2,3 in ZIF connector.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 Mode

<10mA @ DRX2.<8mA @ DRX 9.

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

On/Off Pulse Duration

<500mS. <700mS. Refer to “Configuration Setup and 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 Sleep Mode

Special sequence is needed in the application.

Different sequence than d15. Refer to “How/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

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 returned.

0,1 are supported.

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 detect

Not supported. Supported.

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,012,014,065,066,068,070,071,075),(000),(001).

(006,007,070,071),(000),(000-001)The g18 supports baud rates of 4800 and 9600 bps.

AT+CGSN Not supported. Supported.

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

Function d15 g18

10 98-08901C39-B

Model Description

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.

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

Function d15 g18

98-08901C39-B 11

Model Description

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.

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

Function d15 g18

12 98-08901C39-B

98-08901C39-B

3. DESIGN CONSIDERATIONS

3.1 GENERALWhen integrating a wireless modem, internal connectionsand placements are critical for a successful implementation.Specific attention must be paid to the following supportmechanisms:• Power supply considerations• Audio circuit considerations• Data port considerations• SIM card considerations• ESD considerations• Antenna considerations• Mechanical mounting• Desense control (Refer to Appendix C, “Desense”,

page 199, for further information.)• Connecting the 3788 handset to the g18• GPS considerations

3.2 POWER SUPPLY CONSIDERATIONS

3.2.1 Power Supply Losses

The g18 is specified to operate between 3.0 V and 6.0 V onthe g18 input (after the flat cable losses). In order to be ableto function in the lowest battery values, it is important toverify the losses in the power supply lines, flat cable and userPCB.

The g18 is a GSM phone that transmits in pulses ofapproximately 0.5 mS every 4.6 mS. The peak current isapproximately 1.5 A, while the worst cast peak current is 2.2 A at 3 VCC.

The VCC line drops down during TX periods:

Figure 5. The VCC Signal During TX Periods

In order to minimize the ∆ it is recommended to use as shorta flat cable as possible and to put a 1000 uF capacitor (ormaximum possible) in the g18 VCC input.

3.2.2 g18 Current Consumption

In order to design the power supply correctly, you need totake into account the current consumption of the g18 in itsdifferent modes.

Note

In addition to the losses recommendation, it isrecommended to have a current limit in thepower supply (2.5-3 A), in order to avoiddamage if a short occurs.

Table 3. g18 Current Consumption

Mode Current Consumption

g18 without accessories and no call in process(Sleep mode)

<4mA @ DRX9< 7.5mA @ DRX2

g18 without accessories but TS ON

< 50mA

g18 during searching time <180mA typical average 80mA

g18 with DSC bus accessory (such as a handset) and no call in process

Typical 45 mA

g18 during a call and using maximum power level

<1.8A Peak, Average 300mA @5V

g18 during a call in GSM power level #10 (for example)

<0.7A Peak, Average 175mA @ 5V

Note

DRX is the rate at which the base stationinterrogates the mobile station. The networkoperator sets this parameter.

13

Design Considerations

3.2.2.1 Turning the Unit On or OffThe g18 is powered from a single power supply in the rangeof 3.0 to 6.0 V DC.

The unit will not power up automatically by connecting thepower. There are two ways to turn on the unit, using the ON/OFF pin and using the TS pin, as described in thefollowing sections.

The ON/OFF line is the recommended way to power off theg18, since it detaches the g18 from the network anddisasserts the SIM card contacts in the correct order. Whenthe g18 is powered off by disconnecting the power to theunit, the SIM card might be damaged, and units containingthe g18 that need to pass SIM card type approval tests willfail 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 #18on the DIN connector) is used as a toggle input to turn theunit on or off. Any drop to low in this pin will change thestatus.

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.

Figure 6. Turning On the Unit Using the On/Off Pin

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

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 mobiledevice where the current consumption is not the mainconcern.

The TS line is used to turn on the unit. This line cannot turnoff 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 isconnected to the unit (for example, the ignition line in a carkit).

Figure 8. Turning the Unit On Using the TS Line

T1 minimum = 12ms T2 minimum = 630ms T3 typical = 850ms T4 typical = 240ms T3+T4 max =1300ms T5 typical = 1725ms

T2 min = 630ms (T1 min = 12ms) T3 min = 1550ms T4 min = 630ms T5 = 620ms T6 = 800ms T7 = 240ms T8 = 5400ms T9 = 4840ms

Note

The TS line should be returned to low in orderto be able to work in sleep mode.

It is recommended to pull the unit high for650 ms in order to wake the unit using the TSline.

The 650ms pulse can be without any delay fromthe VCC.

The actual turn ON process using the TS line isdone by sampling the line at 2 points. Whenpowering ON the g18, there is a spike on theVCC that is considered as sample number one.After 600ms, the next TS will be sampled. Thissituation changes, however, if the unit was notpowered off using the ON_OFF signal.

T1=600ms (on is sent after thepower was supplied for a longtime 600ms)

T2=12ms (The TS signal issampled on the rising edge,therefore its size does not matter)

T3= 820ms

T4= 25ms

T5= 250ms

14 98-08901C39-B

Design Considerations

The following pictures show the behavior of the RS232 lineswhile turning on the g18. (Low level on RS232 indicates an active state).

Figure 9. DTR/DSR During Ton

The CTS becomes active before the DSC_EN becomesactive.

Figure 10. RTS/CTS During Ton

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

Figure 11. DCD/RI During Ton

Figure 12. TXD/RXD During Ton

T1 max = 3.5 sec T2 max = 5.5 sec

T1

T2

T1 max = 1.7 sec

T1

T1 max = 1.7 sec

T1

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 logicsection is reduced from 13 MHz to 32 KHz.

The unit senses activity by periodically exiting this mode. Inthe case of an incoming call, the unit will exit Sleep mode.Entering Sleep mode will not terminate a GPRS section andwill not deactivate a context.

During Sleep mode, the RS232 does not respond to anycommands from the DTE device (UART is disabled and noresponse will be received via the RXD line). In order to wakethe unit, the host needs to communicate with the g18 usingone of the following options:

Option 1

Sleep mode works as follows:

Activate Sleep mode by sending ATS24=n (n=1,2,3,4seconds). (To disable Sleep mode send ATS24=0).

This causes the g18 to drop the CTS whenever the unit is inSleep mode.

When TXD is present, the g18 will not enter Sleep mode. Atthe end of the TXD (TXD buffer empty), the g18 waits nseconds (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 inthe 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 startsending the data.

While sending data, the wake up line should remain low, andthe g18 will not enter Sleep mode.

.

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 theunit exited and returned to a GPRS coverage area. This isdone using the bi-directional wake up line (pin #15 in the FC36 pin or pin #10 in the DIN 28 pin).

When the g18 wants to send data to the DTE, it activates thewake up line to interrupt the DTE, followed by datatransmission (assuming RTS is active). When data is presentin the UART, the g18 sends a pulse with a duration of2*y ms. The value of y is determined by ATS99= (defaultvalue is 30; 0 value is not allowed), where t = pulse duration.

Note

1 The ATS24 factory default value is "0". Thisvalue is saved in the EEPROM. To changethe default value, save the new value to theEEPROM. After recycling the power, thevalue of ATS24 will be the value saved in theEEPROM. The value of ATS24 can also bechanged without saving in the EEPROM, butwill be lost after power recycling.

2 The TS line should be low in order to enterSleep mode.

3 The DTE should look for the active CTSbefore sending data (HW flow control).

4 The DTE’s UART should not send anycharacter to g18 if the CTS is inactive,otherwise that character might be lost. If theDTE’s processor handles the flow control,and not its UART, and there is a gapbetween checking the CTS state andsending the start bit, g18 may set CTS toinactive during this gap, and the charactersent to g18 might be lost.

16 98-08901C39-B

Design Considerations

In order to limit the number of interrupts, g18 sendsinterrupts when the distance between one burst of data to theother 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 onthe 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:

Figure 17. Wake Up Internal Connections

Pay attention to the following points:1. When the wake up line is used to wake the g18 (wake

up line is pulled down), no wake up indication to theDTE will be available.

2. When the DTE enters Sleep mode, the DTE should notload the wake up line (3 state).

3.3 AUDIO CIRCUIT CONSIDERATIONSThe g18 can make voice calls as well as data calls. Withvoice 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

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.

There are two DSC bus accessories for audio defined for theg18:1. External Handset.

2. DHFA - Car Kit for Hands Free.

Note

1 The g18 gives a wake up pulse for data sent to the DTE in GPRS mode and in CSD mode.

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.

98-08901C39-B 17

Design Considerations

3.3.2 Analog Audio Without Hands Free

The g18 drives the audio in/out in order to allow a voice call.In order to connect a headset, the speaker and microphonechannels must be amplified.

For an example of these drivers, refer to Chapter 8,“g18Evaluation Board”, page 173.

Another point to be taken into consideration is the buzzexisting in GSM phones due to the transmission rate (217 Hz). In order to minimize this noise, the g18 has aseparate ground for the analog circuits.

Figure 18. Ground Connections

The main reason for the buzz is the drop in the ground/Vcclines because of the peak current during TX mode. In orderto minimize the buzz, the following should be done:• Use a short flat cable.• Connect the analog ground from the g18 to all the analog

circuits in the customer application without connectingthem to the power supply ground.

• Connect all the capacitors to the audio circuits ground tothe analog ground.

• Any reference voltage that may be used should have theexternal capacitor connected to the analog ground.

• The maximal audio in/out levels from/to the g18 can beseen in “Analog Audio - Levels”, below.

• Connect the digital ground to the antenna ground. (Thiscan also help if there is sensitivity desense due to digitalsignals from the customer’s board.)

• Connect the digital ground of the g18 with the digitalground of the application.

• Verify that none of the analog lines are referenced to thedigital ground.

3.3.3 Analog Audio - Levels

Audio Uplink (MIC)

The maximum signal level that the g18 can receive in theAudio In pin, before the signal is saturated, is 260 mv, seeFigure 19.

Figure 19. g18 Input Maximum Level

The maximum level that the g18 can accept before the signalat the network becomes distorted is approximately500 mvP-P.

The following picture shows this maximum signal:

Figure 20. Input Maximum Level and BS Detected Signal

18 98-08901C39-B

98-0

Design Considerations

The CODEC 0 dbm0 = 375 mvrms = 1058 mvP-P. Betweenthe EX_AUDIO_IN pin and the CODEC there is anamplifier with an amplification of 3.3 and the followingfrequency response:

Figure 21. Gcap Amplifier Gain Response

Therefore the odbm0 of the uplink path is 375/3.3 = 113.63 mVRMS. The headroom is 20*LOG (500/(1058/3.3))= +3.86 dbm0.

Audio Downlink (Speaker)

The 0dbm0 is 548 mV RMS. Max output is 2.6 V p-p.

The maximum signal from the network before distortionsoccur was measured at 1180 mv RMS. Therefore, theheadroom is 20*LOG (1180/548)= 6.66 dbm0.

The following graph shows the frequency response of theanalog section:

Figure 22. g18 Analog Audio Frequency Response (Audio Out Pin)

Voice

A 500mv RMS sin signal with a frequency of 1khz was sentfrom a base station to the g18.

The following amplitudes were measured on the audio outpin of the g18:

Varying levels were sent from the network and the signalwas measured at the audio out.

The input is presented both in RMS and in dbm0. The outputis at level 7.

Tones

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

Table 4. g18 Rx Audio Levels

Handset Volume Amplitude (mV RMS)0 271 372 513 694 1005 1376 1967 277

Table 5. Rx Audio Levels vs. Different Signals in the BS

dBm0 mV RMS g18 Out (mV RMS)

3.14 1111.9 580

0 774.6 420

-5 435.6 237

-10 244.9 135

-15.5(Phone: -4.7 dBPa)

130 70

-16 122.8 68

-17 109.4 61

-20 (Dispatch: -94 dBSP)

77.5 43

-25 43.6 24

-30 24.5 17

8901C39-B 19

Design Considerations

The same amplitude was measured during a call, and off call.All the measurements are with ATS96=0.

With the ATS96=1 command, the amplitude was 1043 mVP-P.

3.3.4 Analog Audio With Hands Free

The audio in/out from the g18 for analog hands free is thesame as for non-hands free. All the considerations fromSection 3.3.2 are applicable for this mode also.

The additional consideration in this case is to switch the g18DSP to Echo Cancelling mode.

In order to switch to Hands Free mode, use the RS232 portby sending a switch command at the start up.

ATS96=1 Echo canceller is activated (Hands free).

ATS96=0 Echo canceller is disabled (Headset - Default).

The block diagram for the required drivers is shown below.For a detailed example of the driver designs, refer toChapter 8,“g18 Evaluation Board”, page 173.

Figure 23. EV Audio Block Diagram

The requirements from the external drivers and audiodevices are as follows:

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

Note

From version E6.13.24 and later, the EchoCanceller feature can be activated or disabledduring an active call.

Table 7. External Drivers and Audio Device Requirements

Requirement Value

Microphone Impedance Typical 700 ohm

S/N Ratio Minimum 35dB

Gain from Headset to g18 (A2) 45 – 49 dB

Frequency Response(including microphone)

11 to +1 dB 300 to 3400 Hz

g18 Input Impedance 10KΩ

TX Distortion Maximum 5%

Speakerphone Load 25 to 39 ohm

S/N Minimum 35dB

Gain from g18 to Headset (A1) 13 to –9 dB

Frequency Response(including SPKR)

10 to +1 dB 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. AnMC74LCX244 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 maxVil 0.8 V maxVoh 2.5 V min @100 uAVol 0.2 V max @ 100 uA

The port configuration is:

1 start bit1 stop bit8 data bitsNo parity

The default Baud rate is 9600bps with auto baud detectactivated. The specific baud rate can be set usingAT+CBAUD=<Baud>

.

Figure 24. DTE Connection to g18 (DCE Device) (User Connector 36 Pin ZIF)

Figure 25. DTE Connection to g18 (User Connector 28 Pin DIN)

Figure 26. DCE Connection to g18 (DCE Device) (User Connector 36 Pin ZIF)

98-08901C39-B 21

Design Considerations

Figure 27. DCE Connection to g18 (User Connector 28 Pin DIN)

3.4.2 DTR Line and DCD Line

The DTR line must be active (0V) in order for the g18 torecognize the DTE.

If the DTR is not used by the application, connect this line toground (DTR Active).

The DCD line indicates the following:

• In CSD Indicates Carrier Detect Low during the call highin idle mode.

• In GPRS mode Indicates PDP context status - Active low,Inactive high.

DCD is activated only when PDP context is achieved. DCDis de-activated when PDP context is off.

3.4.3 Setting the Baud Rate

The power up default baud rate is 9600, with enable autobaud rate detection feature. The baud rate can be switched to4800, 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 representsauto baud rate detection. For example, AT+CBAUD=8 is equivalent toAT+CBAUD=57600. Using AT+CBAUD=<baud> with<baud> value other than 9 will disable the auto baud ratedetection feature.

After power up, the g18 UART is programmed to 9600, withautomatic baud rate detection. To switch to 57600 BPS useAT+CBAUD=57600. g18 will replay with“OK<CR><LF>”. After flushing these characters out of theUART, g18 will re-program the UART to the new baud rate.

To verify this process, DTE’s UART should switch to thenew baud rate after receiving “OK<CR><LF>”, and sendAT+CBAUD? to get the new baud rate. The answer“OK<CR><LF>” is not dependent on ATVx setting (verbalor numeric response).

The g18 supports auto baud rate detection for low baud rates4800 - 19200. To switch to this mode, the AT+CBAUD=9command should be sent to the g18. The g18 will processthis command as described above, except that it willprogram UART to 9600 with auto baud rate detection. Aftergetting the “OK<CR><LF>”, the DTE can program itsUART to a baud rate between 4800 - 19200, and verify thenew setup using AT+CBAUD?.

Auto-baud detection mode in g18 will be reinitiated, asfollows:

• On power up. • After AT+CBAUD=9.• When DTR changes mode from LOW to HIGH. Once the baud rate is detected and set, g18 will continue towork at the same baud rate until it is reinitiated as describedabove.

Note

When the g18 is in Sleep mode, the RS232output lines maintain the last stage.

There are no level changes due to the sleepstage of the unit.

Note

The DTR indicates that the DTE is ready.The DSR indicates that the DCE is ready. Thereis no connection between the two.

Do no use DTR for releasing a CSD call.

22 98-08901C39-B

Design Considerations

3.5 SIM CARD CONSIDERATIONS

3.5.1 SIM Card Support

The g18 module has a built-in SIM card reader within themodule itself. The SIM card is inserted into the slot providedon the side of the sheet plastic cover. When inserted to thecorrect depth, the card should be flush with the cover. Toextract the card, insert a non-conductive tuning tool into theslot on the top of the unit at the back end of the card, and thenpush the card out of the slot so that it can be removed byhand.

For some installations, this built-in slot will not beaccessible, so an external card reader is needed. If a digitalhandset is going to be used, the card reader can be part of thehandset and is connected to the modem via the DSCinterface. Other installations require the SIM card slot to beinstalled into the OEM device and circuitry to be installed toconnect the card reader to the g18.

The SIM card interface contains six lines plus two lines forpresence detection, (lines 1 and 2) as shown in Figure 28,below.

Figure 28. The SIM Card Interface

The g18 supports 3 types of SIM connections:

• Internal SIM: Internal socket in the g18. Supports 3/5 Vcards.

• External SIM: The SIM lines are routed in parallel to theSIM socket and to the user connector. The user canconnect the SIM externally. Supports 3/5 V cards.

IMPORTANT!

When connecting externally, Full Type Approval should berequired. This may require submission for testing if theSIM lines are longer than 10 cm.

• Remote SIM: This is a standard connection. The SIM isconnected to an external SIM socket, which is connectedto the radio via the DSC bus. Two accessories areavailable: M3788 handset and external SIM card reader.Supports 5V cards only.

3.6 ESD CONSIDERATIONS Generally, the ESD can be protected up to 8KV by usingceramic 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 isperformed inside the g18, however, it is recommended toadd protection inside the user PCB, especially if the flatcable is long.

Note

Auto baud detect requires careful handling,since the g18 has numerous asynchronousmessages that arrive while the UART is in autobaud detect mode, and generally are displayedas garbage characters.

• It is recommended to set the baud rateusing the at+cbaud=x (x not equal to 9)command. This means that the UART isnever in auto detect mode, and there is noproblem sending commands and receivingasynchronous messages.

• The inter byte delay issue: Work within thespeed defined for your UART. It is theUART’s job to handle inter byte delay, withthe exception of handling CTS.

• After setting the baud rate to fixed baud,you can issue another AT command onceyou receive the entire OK response,including the CR/LF appended to it.

• If you are working in auto baud detectmode, you should allow another charactertime after the OK, before starting anotherAT command.

Pin Description1 Gnd2 SIM_PD3 SIM_CLK4 *SIM_RST5 SIM VCC6 SIM_I_O7 SIM VPP8 Gnd

Note

For GPRS functionality, your SIM card mustsupport this service.

A SIM card should be replaced either when theunit is powered off or when a power cycle isapplied after a change.

98-08901C39-B 23

Design Considerations

For lines with high signal rates, it is recommended to useTransguard with low capacitance. There are Transguards of3 pF or less.

It is recommended to ground the antenna ground contact andthe power supply ground contact in order to prevent ESDfrom entering the g18 or the user equipment.

3.7 ANTENNA CONSIDERATIONSThe antenna must be mounted like any other cellular or landmobile radio antenna. The best position for the antenna isusually the center of the vehicle roof, which provides a fairlysymmetric ground plane on metal cars. For vehicles ofnon-metallic material, such as fiberglass, mount the antennawhere it will not be obstructed by items, such as mirrors.

3.7.1 Antenna Systems

Use this information to assist you in selecting the appropriateantenna to incorporate into your product package. Forspecific detailed information, Motorola recommends thatyou use the expertise of an antenna design engineer to solveindividual application concerns.

3.7.2 Antenna Safety

The following statement from the American NationalStandards Institute (ANSI) specifies the safety criteria thatintegrators must use when designing the antenna for aproduct integrating the g18 modem.

“The design of the integrated product must be such that thelocation used and other particulars of the antenna complywith the then current American National Standards Institute(ANSI) Guidelines concerning Radio Frequency EnergyExposure and with any other nationally recognized radiofrequency standards that may be applicable thereto.”

3.7.2.1 User OperationDo not operate your telephone when a person is within 8inches (20 centimeters) of the antenna. A person or objectwithin 8 inches (20 centimeters) of the antenna could impaircall quality and may cause the phone to operate at a higherpower level than necessary and expose that person to RFenergy in excess of that established by the FCC RF ExposureGuidelines.

3.7.3 Antenna Performance

The network operator usually sets the antenna networkrequirements.

3.7.4 Portable Devices

In an environment where portable devices are in use, manyvariables exist that can affect the transmission path. In thiscase, it is preferable to use a vertically-polarized, omni-directional antenna.

Antennas for portable devices include the followingdesigns:• 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. Despitegreater physical constraints, an internal antenna must stillprovide a gain sufficient to meet network specifications.Metal-cased products cannot have internal antennas sincethe metal acts as a shield around the antenna and prevents RFsignals from reaching the antenna. (A metal case acts like aFaraday cage.) The antenna should be positioned so that it isvertically oriented when the device is carried normally. Thiswill ensure that the optimal antenna performance is availablethe majority of the time.

Cable routing from the modem to the antenna needs to avoidRF-sensitive circuits and high-level, high-speed clockcircuits. The following points should be considered:

• The location of the antenna to avoid RFI to a computingdevice.

• Good shielding of the display and other RF-sensitivecomponents.

• The most efficient method of cable routing. !

Caution

The telephone must be installed in a mannerthat provides a minimum separation distance of20 cm or more between the antenna and allpersons to satisfy FCC RF exposure require-ments for mobile transmitting devices.

Note

To comply with the FCC RF exposure limits andsatisfy the categorical exclusion requirementsfor mobile transmitters, the followingrequirement must be met:

The transmitter effective radiated power (ERP)must be less than 3.0 W ERP (4.9 W or 36.9dBm EIRP). This requires that the combinationof antenna gain and feed line loss does notexceed 16 dBi.

24 98-08901C39-B

Design Considerations

If the above points are not considered, antenna gain can beoffset by cable loss. A typical coaxial cable is very thin, suchas the RG178B used in portable devices, and cable loss canbe as high as 0.5 dB per foot. Some coaxial cablemanufacturers market relatively thin double-braid coaxialcables. These cables show much better isolation thansingle-braid cables, typically by 30 to 40 dB. Double-braidcables reduce radiation and RF pick-up when routed inside aportable device.

3.7.4.2 External Antenna, Removable and Directly Connected to the Device

You can design a portable device that can use anoff-the-shelf, plug-in antenna, such as a 1/4 wave monopoleor 1/2 wave dipole antenna. The typical gain of theseomni-directional antennas is 0 dBi and 2.14 dBi,respectively. Like the internal antenna, these antennasshould be oriented vertically when the device is carriednormally to ensure the best antenna performance.

Cabling in this case demands the same consideration as aninternal antenna application. In a typical laptop application,the antenna must be placed as far as possible from thedisplay to avoid deflection. This usually causes a deep nullin radiation patterns.

3.7.4.3 External, Remote AntennaFor remote antenna applications, use the same designapproach as internal designs, including the RF cable routingof the external connector. You can choose an off-the-shelfmobile antenna of omni-directional 1/2 wave length. Theantenna should have a gain of 2.14 dBi. Higher gain than thismay not be appropriate for portable applications.

A double-braid coaxial cable, (such as RG223) from thedevice to the antenna is recommended, if the cable length ismore than a few feet long. The difference in cable lossbetween low-cost RG58 cable and the more expensiveRG223 cable is approximately 4.5 dB per 100 feet. If thecable must be routed through noisy EMI/RFI environments,a double-braid cable such as RG223 can reduce radiation andpick-up by 30 to 40 dB.

3.7.5 Fixed Devices

Fixed data device applications use the same designrecommendations as a portable device with a remoteantenna.

The most economical and practical choice for the RFconnector of an external antenna is a TNC threadedconnector, whether it is a plug-in type or a remote type. TNChas a good frequency response to 7 GHz, and leakage is low.A mini UHF threaded connector provides adequateperformance and is an economical choice. If the size of theTNC and mini UHF connectors becomes critical, consideran SMA threaded connector or an SMB snap fit connector.(The SMB connector does not accept RG58 or RG223cables).

3.7.6 Antenna Test Methods

Whether portable or fixed, the device antenna is the criticallink to the network. A poorly performing antenna reducesthe coverage of the device within the network footprint. Theantenna performance must meet the impedance and matchthe criteria of the modem (refer toChapter 8,“Specifications”, page 187.), and have theappropriate amount of gain to meet the network ERPrequirements.

Two tests must be performed on the antenna to ensure that itmeets the requirements. For both tests, the antenna must beintegrated in its final form. That is, the antenna must bemounted on a representative housing that includes all metalobjects forming the ground plane or counterpoise.

Antenna testing requires an experienced operator and ananechoic chamber, a GTEM cell, or approved open field site.Your Motorola OEM support representative can provideadvice on this type of testing.

3.8 MECHANICS - MOUNTING THE G18

3.8.1 Fixed-Mount Usage

Fixed-mount usage eliminates most of the mechanicalconstraints of handheld designs, although the requirementsstill apply. Fixed-mount units are sometimes AC-linepowered and require filtering to eliminate the 60 Hz noisethat can impair modem operation.

Proper mounting of the modem requires it to be securelyfastened within the host housing.

To ensure ease of access for installation and troubleshooting,locate the modem within the product in such a way that serialI/O and antenna connections are readily accessible.

Quick access to the modem allows it to be efficientlyremoved, probed and functionally tested.

98-08901C39-B 25

Design Considerations

3.8.2 Fastening Units with Housing

Mount the modem to the rigid OEM product housing, usingfour #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 30. Mounting the Modem (Rear View)

3.8.3 Fastening DIN Units

Secure the DIN board to the host device using three M1.8screws.

3.9 CONNECTING THE M8989 HANDSET TO THE G18

In order to connect the handset (M8989) to the g18 thefollowing connections are required in the user board.

You can see the circuits used in the g18 Evaluation board forthis purpose as an example, in Figure 31, below.

Figure 31. Handset Connections / Hardware Required

3.10GPS CONSIDERATIONSThe g18 DV with a GPS model includes an internal M12GPS 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 userconnector (ZIF 36 pin). The GPS lines in the g18 userconnector 36 pin ZIF socket are as follows:

The GPS receiver is a standalone unit in the g18.

More details about the M12 module can be viewed on theweb at:

http://www.synergy-gps.com/M12_Oncore.html

!Caution

Do not mount a g18 integrated wireless modemin PC Card Type III rails. Forcing the modeminto a PC Card header can damage theconnector pins in the header and leave themodem loose and poorly grounded.

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

g18 User Connector Pin # Function

2 GPS RXD receives data in 3V logic.

3 GPS TXD transmits data in 3V logic.

34 Antenna voltage input 3 or 5 V DC. (active antennas)

35 RTCM input in 3V logic.

36 1pps output in 3V logic.

26 98-08901C39-B

98-08901C39-B

4. SOFTWARE INTERFACE

4.1 GENERALThe operating functions of the g18 modem are implementedin the base unit into which the g18 is integrated. The g18 isa GSM900/1800/1900 Phase II+ device with GPRScapabilities.

The corresponding functions are implemented conformingto V.25ter, GSM07.07, and GSM07.05.

AT+C commands conforming to GSM07.07 and GSM07.05and a number of manufacturer-specific AT commands areavailable via the serial interface of the g18 for functionalityimplementation.

Commands are input via the operating functions of the baseunit. The base unit translates the operating functions into ATcommands and the g18 executes the requested action.

The V.25ter modem guidelines apply to the time sequence ofinterference commands. In accordance with theseguidelines, commands start with the string AT and end witha carriage return (<CR> or 0x0D). Commands areacknowledged with OK or ERROR. A command currentlybeing processed will be interrupted by each subsequentincoming character, so the next command must not be sentuntil the acknowledgement has been received that thecommand has been processed. If this does happen, thecurrent command will be cancelled.

4.2 MODEM COMMUNICATION MODESThe g18 modem supports the following communicationsmodes: voice, data, SMS and fax.

4.2.1 Voice Communication

• Analog Audio: Analog audio communication is providedvia a standard analog headset such as the headset usedwith the StarTAC cellular phone. In this case, the controlsfor answering calls, dialing, and hanging up are providedby the AT command set interface. This mode is used if themodem is integrated into a handheld terminal thatsupports voice communications.

• Digital Audio: Digital audio is provided by the MotorolaProprietary DSC interface. This interface is used when anexternal handset, like that used in an automotiveinstallation, is used. In this case, the call controls areprovided on the handset. DSC handsets that support thisinterface are manufactured by and available fromMotorola. The AT command set can also be used tocontrol calls. The DSC interface is a Motorola proprietaryfeature that requires licensing from Motorola. Pleasecontact your Motorola representative for moreinformation.

4.2.1.1 Configuration Setup and Audio Routing in g18

Voice Connectivity

The g18 is an OEM data and voice module. Voiceconnectivity can be performed using two main channels:analog voice and digital voice.

Note

The standards bodies regularly update thesestandards, therefore there is no guarantee thatthe commands supported by the g18 exactlyconform to the latest versions of thesespecifications. Some commands listed in thesestandards do not apply in the GSMenvironment.

Note

You should wait to receive OK before sendinga new AT command.

27

Software Interface

The audio route for the different devices is described in thefollowing table, where HF refers to the connected externalspeaker and microphone, and DHFA refers to the externalcar kit.

• Sidetone - Reduces the microphone audio input that isrouted to the selected speaker so that the people speakingwill hear themselves talking. This also creates a slightecho because the speaker sound then gets picked up againby the microphone and again output to the speaker, and soon. Echo suppress is designed to take care of this echo.

• Echo Suppress - Cancels a small amount of the outputsound picked up by the input device (suppresses theecho). It is designed to be used where there will be littleor no echo (for example, in a handset) rather than wherethere will be a lot of echo (for example, in a hands-freedevice).

• Echo Cancel - Suppresses a large amount of the outputsound picked up by the input device (cancels all echo).

• Noise Suppress - Improves audio quality in all modes.There are two AT commands that support enabling/disablingthe Echo Cancellation and Sidetone characteristics, asfollows:

• ATS96=1 enables the Echo Cancellation, which is themain HF mode characteristic.

• ATS94=1 enables Sidetone (default). ATS94=0 mutessidetone.

The following table shows the relationship between theATS94, the ATS96 and the g18 analog audio behavior whenthe digital handset is omitted or ONHOOK.

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 aninitialization of a PDP context the data sent from the DTEwill be over PPP. A GPRS wizard is available to do thePDP connectivity (for PC applications). This is a veryeffective tool for transferring data at a high rate and onlywhen data is available, without the need to dial again.

Table 9. Voice Connectivity

Configuration Setup Audio Route to…

Off hook handset (overrides all other conditions)

Handset

On hook handset, or absence of handset:•HF + HF was selected byATS96 command

•HF + HF was not selectedby ATS96 command

•DHFA

•Headset + HF was selectedby ATS96 command

•Headset + HF was notselected by AT command

•HF external speakerwith echo cancelling

•HF external speaker, without echo cancelling

•DHFA speaker

•Headset with echocancelling

•Headset without echocancelling

Table 10. Regular (HS) and HF Mode using RS232

Characteristics Regular Mode (Handset) HF mode

Echo Cancelling (EC)

-Disable

+Enable

Sidetone + -Mute

Echo Suppression (ES)

+Enable

-Disable

Full Duplex Half Duplex

Note

Both AT commands are not allowed when theCar kit is attached.

Hands-free

Mode ATS96 ATS94

Echo Cancella-

tions

Noise Suppres-

sionST

Off 0 0 Disabled Disabled Mute

0 1 Disabled Disabled Unmute

On 1 1 Enabled Enabled Mute

1 1 Enabled Enabled Mute

Note

ATS94 is affected only when ATS96=0.

The HF setting (ATS96) is kept in flex, evenafter power cycling the g18.

28 98-08901C39-B

Software Interface

• CSD - Circuit Switch Data: The default setting for theg18 is RS232 full flow control. In this mode, data, SMSand 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 GPRSmode is the need to dial the desired number wheneverdata needs to be transferred.

4.2.3 SMS Communication

• Block mode: This is a binary SMS presentation. Anapplication SMS build is required for this mode.

• Text mode: This mode is not supported by the g18.• PDU mode: This is the recommended mode for SMS

communications. Note that the PDU packet has acomplex structure, so careful examination of GSM 04.11and GSM 03.40 is required.

4.2.4 Fax Communication

Class 1: This is the basic set of fax commands that issupported by all types of fax machines. To support faxcommunication with g18, use WinFax in your computer.

Class 2: This mode is not supported by the g18.

4.3 BASIC OPERATIONS

4.3.1 Making a Voice Call

4.3.2 Receiving a Voice Call

Note

The g18 supports both transparent andnon-transparent modes.

Table 11. Features Supported using CSD/GPRS

CSD Supports

Flow Control

HWXon/XoffNone

Data Type TransparentNon transparent

SMS SMS PDU modeSMS Block mode

Fax Class 1

GPRS Supports

Flow Control

HWXon/XoffNone

Data Type Data over PPP

Multi Slot Class 1, 2 and 4 1 uplink 1,2 or 3 downlinks

Coding Schemes

CS1, CS2, CS3, CS4

AT+CPIN=”nnnn”, if required

Enter the PIN number which enables the SIM card (4-8 digits).

ATDnnnnnn OR

AT*Dnnnnn OR

ATD><index> OR

ATD>”name” OR

ATDS=n (n=0 to 3) ORATDS=n (n=0 to 3) ORATD><mem><index>

Initiates the voice call to the remote phone. The voice communications commence.Phone book storage should first be selected at+cpbs=”sm”.Phone number corresponding to the name entered.Phone number from register #1 after setting at&z1=035658452.Phone number from register #0 after setting at&z1=035658452.Phone number from SIM card #101, for example, ATD>SM101.Note: Only the second OK for the voice call notifies the user that the call is established.

ATH Hangs up the voice call.Note: In multi-party calls, ATH does not end the last call, only AT+CHLD=1 does.

AT+CPIN=”nnnn”, if required

Enter the PIN number that enables the SIM Card (4 -8 digits).

AT+CRC=1 Enables cellular result codes extended format. A remote phone dials the g18 voice number.

98-08901C39-B 29

Software Interface

4.3.3 Commencing Voice Communication

4.3.4 Making a CSD - Data Call

4.3.5 Receiving a Data Call

4.3.6 Enabling Cell Broadcast (CB) Reception

Send AT+CKPD=”M>>S>>>>>S<SCC”

In order to receive the CB message on the TE, use theAT+CNMI command.

For example:

AT+CNMI=0,2,2,0,0

+CRING:VOICEor+RING

If AT+CRC=1, VOICE indicates an incoming voice call. If AT+CRC=0 then +RING indicates an incoming call.Note: To retrieve the call type, use the CMER command.

ATA Answers the call

ATH orAT+CHUP

Hangs up. Call ends.Note: In multi-party calls, ATH does not end the last call, only AT+CHLD=1 does.

If the remote phone hangs up first, the modem will stay online, (AT+CPAS returns +CPAS:004) for approximately 60 seconds, at which point it will time out and the call will be cleared (AT+CPAS returns +CPAS: 000). At any time during this period, the modem can execute an ATH command.

ATDnnnnnnn Dials the remote modem.

CONNECT xxxx

Indicates that the connection is made. Proceeds with data communications.

+++ Escapes to Command mode.

ATO Returns to Online mode.

+++ Escapes to Command mode.

ATH or AT+CHUP

Hangs up the connection.

The remote modem dials the g18 data number.

AT+CRC=1 Enables cellular result codes extended format. The remote phone dials the g18 voice number.

+CRING: REL ASYNCor+RING

If AT+CRC=1, DATA indicates an incoming data call.

If AT+CRC=0, then +RING indicates an incoming call.Note: To retrieve the call type, use the CMER command.

ATA Answers manually.ATS0=1 enables an automatic answer after one ring.

+++ Escapes from Online mode.

ATH or AT+CHUP

Hangs up call.Note: In multi-party calls, ATH does not end the last call, only AT+CHLD=1 does.

If the remote phone hangs up first, the modem will stay online (+CPAS:004) for approximately 60 seconds, at which point it will time out and the call will be cleared (+CPAS: 000). At any time during this period, the modem can execute an ATH command.

Note

When using different SIM cards, the abovesequence might be changed, accordingly.

30 98-08901C39-B

Software Interface

4.3.7 Setting Up the g18 in CSD Mode

When a data call is received, the RI signal goes to ActiveLow for one second and then to Inactive High for fourseconds repeatedly, as shown below.

Figure 32. RI Waveform

When a data carrier is detected by the g18, it sets the DCDsignal to Active Low.

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 DataWhen data is sent by the g18, the only dynamic signalsthrough the data transfer are TXD and CTS. The DTE deviceshould be kept at DTR ON.

TXD is used in order to transmit the data from the terminalto the g18, and CTS is used in order to control the data flow.When data is transferred too rapidly to the modem, at a ratewhich is greater than its transfer rate, and its buffers becomefull, the modem sets CTS to Inactive High, until it completesthe transfer.

When the modem is ready to accept more data, it sets theCTS signal to Active Low again.

Figure 34. g18 Sending Data Hardware Flow Control

4.4.1.2 Receiving DataWhen data is received by the g18, the only dynamic signalduring the data transfer is RXD, with which the data is sentto the terminal. The DTE device should keep DTR ON. RTScan 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 DataWhen data is sent in this mode, it is transferred on the TXDline. The DTE device should keep DTR ON.

When data is transferred too rapidly to the modem, itsbuffers may become full, and the transmission cannotsucceed. In this case, it sends an Xoff signal to the terminalon the RXD line.

When the modem has sent the data in the buffer and is readyto receive more data, it sends an Xon signal on the RXD line.

Note

The g18 does not support non-transparent CSDwith a baud rate of less than 4800 bps.

98-08901C39-B 31

Software Interface

.

Figure 36. Sending Data Xon/Xoff

4.4.2.2 Receiving DataWhen data is received in Xon/Xoff flow control, the data istransferred from the g18 to the terminal on the RXD line.The DTE device should keep DTR ON.

Figure 37. g18 Receiving Data Xon/Xoff

4.4.3 Flow Control Set to None

The g18 should be configured to Xon/Xoff, using AT&K0.

To return to the hardware flow control, use AT&K3.

4.4.3.1 Sending DataWhen data is sent in this mode, it is transferred on the TXDline, and there is no flow control. The DTE device shouldkeep DTR ON.

When the modem cannot keep up with the rate of datatransmission from the terminal, an error occurs.

Figure 38. Sending Data in None FC

4.4.3.2 Receiving DataWhen data is received by the g18, the only dynamic signalduring the data transfer is RXD, with which the data is sentto the terminal. The DTE device should keep DTR ON.

Figure 39. g18 Receiving Data in None FC

4.5 CALL WAITING, CALL FORWARD-ING, AND CONFERENCE CALLS

4.6 SENDING AN SMS

4.6.1 Sending an SMS in PDU ModeNote

In the figure above, the Z Modem transferprotocol was used, with crash recovery setup.When an error is encountered, the terminalsends a message to the sending side, asking itto resend the specific block.

Note

These operations are network dependent, andare not supported by some networks. Somenetworks behave unexpectedly, such asroaming or call dropout.

AT+CPIN=”nnnn” Enter the PIN number that enables the SIM card (4 - 8 digits).

AT+CSMS=0 Select message service response. The response will be +CSMS:001,001,001.

AT+CPMS=”SM” Select preferred message storage. The response will be similar to +CPMS:001,0015,001,015, depending on your SIM card.

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

32 98-08901C39-B

Software Interface

For example:

AT+CMGS=19

>07914483056100F511000B914410927856F40000000541E1905804<0x1A>

will return +CMGS:000 after sending “ABCDE” to phonenumber 44-012-987-654 via the SMS center at 44-385-016-005.

The following ASCII string is the ASCII representation ofthe hexadecimal values that will be transmitted as a binarystring.

‘F’’4’ below means that the hexadecimal values 0xF and 0x4will be transmitted over the air. CMGS=19 is the length ofthe TPDU in octets, see below.

AT+CMGS=19

>07914483056100F511000B914410927856F40000000541E190F804<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 hexadecimaldigit 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 toform a semi-octet. So, the phone digits 3, 8 will become 0x3,0x8, then 0x38, and then reversed to become 0x83. TheASCII characters ‘8’ and ‘3’, the string ‘83’ are then insertedinto the full ASCII string above. Since there is an oddnumber of digits, the last digit, 5, is placed in the lowernibble of the last octet and then its top nibble is filled with1s. This means that ‘5’ becomes 0x5, then 0x05, then 0xf5,and then ‘f5’, which are the last two characters in the ServiceCenter address.

Refer to ETSI 04.11 for more details.

Looking at the remainder of the message after the SCA, wefind the Transport Protocol Data Unit (TPDU). The TPDUcontains the destination device address (phone number), andthe user data or message. There are 38 characters, whichrepresent 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 DestinationAddress

0B = Number of digits (11) in phone number

91=TON/NPI (as above)

4410927856F4 = Destination phone number 44-012-987-654

The user data control information and the user data followthe 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 isencoded as GSM characters. The GSM character set is amethod of encoding 7 bit ASCII characters into 8 bitnumbers. GSM only supports 128 characters with ASCIIvalues 0x00 to 0x7f. Since these only need 7 bits to definethem, and the SMS message is transmitted as a series of 8-bitvalues, GSM uses a method of packing the series of 7 bitvalues into 8 bit octets. For example:

ABCDE is encoded as 41E190F804 as follows.

A B C D Ein ASCII hexadecimal is:0x41 0x42 0x43 0x44 0x45in 8 bit binary is:01000001 01000010 01000011 01000100 01000101

Note

This is an example only. This particular SMScenter is a UK number.

Note

The message is terminated with a Control-Zcharacter (0x1A).

Note

The destination phone number is converted toan ASCII string in the same manner as theSCA.

98-08901C39-B 33

Software Interface

The most significant bit is truncated, resulting in a series ofseven bit values. The now unused most significant bit(s) arepacked with enough least significant bits from the followingvalue to make up eight bits.

This results in the string of eight-bit hexadecimal numbers0x41, 0xE1, 0x90, 0x58, 0x04. By continuing this process, astring of 160 ASCII characters can be stored as a string of140 bytes (octets).

The Service Center Address is described in ETSI GSM 04.11.

The Transport Protocol Data Unit is described in ETS GSM03.40.

4.6.2 Sending an SMS in PDU Mode - Wave Forms

4.6.3 Sending an SMS in CSD Mode

When sending an SMS in PDU mode, after executing theat+cmgs=n command, the DCD line goes to Active Low,and the data is transferred on the TXD line.

After executing the <Ctrl+Z> command, the DCD linereturns to Active High, and the message is sent via thephone.

Figure 40. Sending an SMS

4.6.4 Receiving an SMS

Once the message has been received, the next step is todecode it into something comprehensible. This particularmessage is generated by a Rohde and Schwarz CMD55GSM Test station. In the first line of data, we see theinformation about the service center, followed by the TPDU.

038021430402802100006990502100000064D2279258049940D321F21A946A4

03 = Length of service center address

80 = Type of number = unknown, number plan identifier =unknown

2143 = Service center address = 1234

04 = MTI = SMS-DELIVER, MMS = no moremessages, SRI = no status report UDHI = no UDheader, RP = reply path not set

Note

Sending and receiving of SMS messagesinterfere with each other when the time intervalbetween them is too short, or when bothoperations take place simultaneously.

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.

AT+CNMI=0,1 Allows buffering of unsolicited result codes in the TA. Indication of memory location is routed to TE.

+CMTI: "SM",001 Is displayed (001 message location).

To display incoming messages:

AT+CMGL=4 Lists all the stored messages.

AT+CMGR=1 Reads the message at location 001.

+CMGR: 000,,102038021430402802100006990502100000064D2279258049940D321F21A946A4153F45B4E0735CBF379F85C064DCB727B7A5C0651CB73BA0B44459741D17A7ABC0609E5EFBB1B647CE341CA7A1B3E073DED6539888A2E8398617D1E447C9F5DA0986C46ABD96EB81C4C01.OK.

34 98-08901C39-B

Software Interface

02 = OA length

80 =TON = unknown, NPI = unknown

21 = OA = 12

00 = PID =Protocol ID

00 = DCS = Data Coding Scheme

69905021000000=SCTS ServiceCenter Time Stamp = 5th Sept. 1996 12:00:00 GMT

64=UDL=UserData Length=100octets

Following is the user data:

D2279258049940D321F21A946A4153F45B4E0735CBF379F85C064DCB727B7A5C0651CB73BA0B44459741D17A7ABC0609E5EFBB1B647CE341CA7A1B3E073DED6539888A2E8398617D1E447C9F5DA0986C46ABD96EB81C4C01

This is a string of GSM characters, which must be translatedback into ASCII. The process is the reverse of the codingprocess described previously. This converts the charactersback from a series of octets to a series of 7 bit ASCIInumbers.

Looking at the first 6 octets:

This decoding process continues for the entire user datastring. Translating the entire string comes up with ROHDE

& SCHWARZ THE QUICK BROWN FOX JUMPEDOVER 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 cansimply insert your raw data as the user data, instead of usingthe GSM character coding process. This limits you to 140octets of data. So long as your application controls theencoding and decoding of the SMS PDUs at either end of thesolution, you can use the 140 octets of user data as you seefit.

4.6.6 Receiving an SMS in CSD Mode - Wave Forms

When an SMS is received, it is stored on the SIM card.

Figure 41 shows a reading command sent on the TXD line,and the message transferred from the SIM card to theterminal.

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

#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

Message Types

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

#define MMISMS_SUCCESS 512

Text Mode and PDU Mode Error Values (Continued)

#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

4.6.7 Sending a Fax

4.6.7.1 Installing the Modem DriverFrom the Control Panel, select Modems > Add modem> Next > (Windows finds "standard modem" on one of theCOM ports) > Change > Have Disk > Enter the path tomodem driver (for example, D:\motorola\modem) and selectL-series > Next > Finish. (You may have to restart beforeusing the modem.)

4.6.7.2 Configuring the Modem in WinFax1. Run WinFax.

2. Select Tools > Program Setup > Modemsand Communications Devices > Properties.

3. Set Motorola L Series to Active (WinFax beginstesting the modem and the result is Failed. This resultis acceptable).

4. Click Next and select CLASS 1 (Hardware FlowControl) > 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 portto which the modem is connected and initialize it at57600 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 activatingPDP context.

Connection may be performed in one of the following twoways:• Automatically after powering up your MS. The GPRS

logo is displayed on your screen.

• Using the AT+CGATT=1 command. You can check yourconnection status by using the AT+CGATT? commandAT+CGDCONT=1,"IP","RTY","123.32.45.9

Following are the three main ways in which to activate PDPcontext:1. If the GPRS Wizard application is used, double-click

the button predefined as the dialer for this provider toautomatically establish PDP context. If the g18 was notpreviously attached to GPRS, it will be attachedautomatically.

Setup Configuration

1. Enter into the wizard parameters provided by youroperator.

2. Set definitions to allow your http\ftp browser to usethe g18 as a port to the Internet.

Usage

1. Open the GPRS Manager.

2. Double-click the dialer icon to select and activate theprovider of your choice (multiple providers may bedisplayed in the list).

3. After dialing, your temporary IP address and then theGPRS DATA session message will be displayed onthe handset.

4. Minimize the GPRS wizard window and use yourhttp\ftp browser (Internet Explorer, Netscape).

2. If you use AT commands to activate PDP context, youmust 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=1command.

#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)

SMS TIMERS

98-08901C39-B 43

Software Interface

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#

3. Using the ATD* command set: The GSM 07.07 version7.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 thiscommand can be used in the following format:

ATD*99***(CID)#

The CID includes the APN (defined by theAT+CGDCONT command) to which you want to beconnected. (This depends on the ability of the SIM cardto be attached to the different networks)

The format ATD*99# may also be used. In this case, theg18 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 PINnumber and recheck whether the status is READY.

2 Check that AT+CLCK="SC",2 returns +CLCK: 1,7. Ifnot, send AT+CLCK="SC",1, your PIN# command.

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 FDarea.

If the response is: +CLCK: 0,7enter AT+CLCK="FD",1,"PIN2", OK, then enter AT+CLCK="FD",0,"PIN2".

Note

Bear in mind that the AT command AT+CGACTis not supported in all countries with GPRS. AGPRS connection is also possible withATD*99#. See the following section for moreinformation.

Note

The above list is only for the AT command level.PPP information (DNSs) is not shown here.

Note

When buffering the DTE message data in theg18 (both inbound and outbound data), thefollowing apply:

•Turning off the g18 clears any buffered data.

•Removing power from the g18 clears anybuffered data.

•Whenever the DTE drops the PPP connectionwith the g18, via LCP terminate, the buffereddata is cleared.

•Whenever the g18 drops the PPP connectionwith the DTE, with LCP terminate, the buffereddata is cleared. LCP termination triggers thetermination of the data in the g18 buffer.

•Whenever the g18 drops the PPP connectionwith the DTE, without an LCP terminate, thebuffered data is cleared. Dropping the DTRalso clears the buffer.

•When the network sends a deactivationmessage or a detached message, the g18buffer is cleared.

•When the g18 transfers data in the uplink andGPRS coverage is lost, the data may flow-off.If the mobile has lost coverage and is unable tosend the packets from the DTE to the network,the buffers will continue to store the packetsuntil the buffers are full. The DTE will then beflowed off and the packets will be stored untilthey can be sent to the GPRS network.

•The amount of time that takes before the useris notified is specified in the T3312 timer that islocated in the mobile side. The default delaytime of T3312 is 54 minutes, as per the GSM0408 specification. After 54 minutes, the g18deactivates the PDP session.

44 98-08901C39-B

Software Interface

After receiving OK, write operations are allowed in the FDarea.

at+cpbs="fd"

OK

at+cpbw=10,"123",,"time"

ERROR

at+clck="fd",2

+CLCK: 0,7

OK

at+clck="fd",0,"7391"

OK

at+clck="fd",2

+CLCK: 0,7

OK

at+cpbw=10,"123",,"time"

OK

The following is an example of a SIM card that is configuredwith the Fixed Dial number phonebook of 0 possible entries:

at+cmee=2

OK

at+clck=?

+CLCK:("CS","SC","AO","OI","OX","AI","IR","AB","AG","AC","FD")

OK

at+clck="FD",2

+CLCK: 3,7

OK

at+cpbs=?

+CPBS: ("FD","LD","ME","MT","SM","DD","RC")

OK

at+clck="FD",0,"8625"

OK

at+clck="FD",2

+CLCK: 0,7

OK

at+cpbs="FD"

+CME ERROR: "operation not allowed"

Possible explanations could be “Fixed Dial Phonebook notavailable” or “No memory space available on the SIM cardfor the fixed Dial Phonebook”.

4.7 BASIC AT COMMANDSTable 12 lists the basic AT commands for the g18 modem.Most of the basic commands are from the V.25ter reference.Commands shown in bold are factory defaults.

The format of the command is:

AT<command>

For example: ATE0 will turn off the echo command.

Note

To repeat the command, use the command A/which will repeat the previous command. This isnot prefixed with AT.

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

Command Function

A Goes off-hook and attempts to answer a call.

Dn Dial modifier. For voice calls useATDxxx; or AT*Dxxxx or ATD>102or ATD>"DAN" or ATDS=1 or ATDS=0 or ATD>SM101.

E0 Turns off command echo.

E1 Turns on command echo.

F No action, compatibility only.

H Initiates a hang-up sequence.

I0 Reports product code.

I1 Reports pre-computed checksum.

I2 Reports processor name.

I3 Reports firmware revision.

I4 Reports product name.

98-08901C39-B 45

Software Interface

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.

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

Command Function

Sn for n equal to 14, 21, 22, 31, 36, 39, 40, 41

Bit map registers.

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.

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

Command Function

46 98-08901C39-B

Software Interface

S101 Sets the wakeup line forever when x=1, and resets it when x=0. ATS101? returns the current state. These operations are allowed only when the factory bit is set. When the parameters are wrong, or the factory bit is not set, it returns an error.

T No action, compatibility only.

V0 Reports short form (terse) result codes.ATV0 result code information: OK 0CONNECT 1RING 2NO_CARRIER 3ERROR 4BUSY 7NO_ANSWER 8OK without sending any response 9

V1 Reports long form (verbose) result codes.

W0 Reports DTE in Error Correction (EC) mode.

X0 Reports basic call progress result codes:OK, CONNECT, RING, NO CARRIER(also for busy, if enabled, and dial tone not detected), NO ANSWER, and ERROR.

X1 Reports basic call progress result codes and connection baud rates:OK, CONNECT, RING, NO CARRIER(also for busy, if enabled, and dial tone not detected), NO ANSWER, CONNECT XXXX, and ERROR.

X4 Reports all calls progress result codes and connection rates:OK, CONNECT, RING, NO CARRIER,NO ANSWER, CONNECT XXXX and ERROR.

Y No action, compatibility only.

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

Command Function

Z Resets to default configuration.

&C0 DCD is forced ON at all times.

&C1 DCD is set to ON when the CSD carrier is detected or when the GPRS session is started.

&C2 DCD is set to ON when the PDP is active and the IP address is received from the network. This command should not be used with a computer dial-up networking program.

&D0 Interprets the DTR on-to-off transition. The modem ignores DTR.

&D1 Interprets the DTR on-to-off transition. The modem performs as asynchronous to command mode.

&D2 Interprets the DTR on-to-off transition. The modem hangs up.

&D3 Interprets the DTR on-to-off transition. The modem hangs up.

&F0 Restores the factory configuration 0.

&F1 Restores the factory configuration 1.

&G No action, compatibility only.

&J No action, compatibility only.

&K0 Disables all DTE/DCE flow controls.

&K3 Enables RTS/CTS DTE/DCE flow controls.

&K4 Enables XON/XOFF DTE/DCE flow controls.

&K6 Enables RTS/CTS DTE/DCE flow controls.

&L No action, compatibility only.

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

Command Function

98-08901C39-B 47

Software Interface

&M No action, compatibility only.

&P No action, compatibility only.

&Q0 Selects a direct asynchronous mode. (This has no effect on the g1,8 since it only has a non-transparent mode.)

&Q5 Modem negotiates an error corrected link (default). (This has no effect on the g18, since it only has a non-transparent mode.)

&Q6 Selects an asynchronous operation in normal mode. (This has no effect on the g18, since it only has a non-transparent mode.)

&R No action, compatibility only.

&S Defines the DSR's behavior. (This is always active).

&T No action, compatibility only.

&V Displays the current configuration and stores the profiles.

&W0 Stores the active profile in NVRAM profile 0.

&W1 Stores the active profile in NVRAM profile 1.

&Y0 Recalls the stored profile 0 upon power up.

&Y1 Recalls the stored profile 1 upon power up.

&Zn=x Stores the dial string x (up to 35 characters) into location n = (0 to 3).

\N1 Selects the direct mode. (This has no effect on the g18, since it only has a non-transparent mode.)

\N2 Selects the reliable link mode. (This has no effect on the g18, since it only has a non-transparent mode.)

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

Command Function

AT*A Same as ATA.

AT*D Dials voice call numbers.

AT*P No action, compatibility only.

AT*V No action, compatibility only.

A/ Repeats last command.

AT? Returns the value of the last updated S-Register.

AT$ Lists the supported AT commands.

Table 13. Advanced AT Commands List

Command Function

+CRTT Selects ring tone.

+CIPE Enables/disables CIP command.

+CIP Sends IP primitives over RS232 (IP primitives are messages used by the DSC bus).

+CBAUD Selects the baud rate.

+CGPRS Indicates the GPRS coverage.

+MTDTR Supported for DTR line test command.

+MTCTS Supported for CTS line test command.

+MCWAKE

Supported for DTE wake line control command.

+MMGL Lists the messages without changing their attributes.

+MMGR Reads the message without changing its attributes.

+MMGA Changes the message attributes.

+CMSS Sends the message from storage.

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

Command Function

48 98-08901C39-B

Software Interface

4.8 ERROR CORRECTION AND COMPRESSION (ECC) COMMANDS

The g18 modem supports the commands listed in Table 14.

4.9 FAX CLASS 1 COMMANDS

4.10 ETSI 07.07 STANDARDThe following tables list the commands defined by ETSIstandard 07.07 Phase 1, which are supported by the g18modem.

For a more detailed description of ETSI commands, refer toETSI document GSM 07.07 — prETS 300 916, GSM 07.05,GSM 03.40 Sections 9.1 and 9.2, GSM 04.11 Sections8.2.5.1 and 8.2.5.2, and GSM 03.38.

For each command it is recommended that you use the ?option to query the modem for the particular details of eachcommand. For example, use AT+CR? to get the full detailson the +CR command.

Table 14. Supported ECC Commands List

Command Function

%C0 Disables data compression. (This has no effect on the g18, since it does not have compression.)

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

%C2 Enables V.42 bis data compression. (This has no effect on the g18, since it does not have compression.)

%C3 Enables both V.42 bis and MNP 5 compression. (This has no effect on the g18, since it does not have compression.)

\A0 Sets the maximum block size in MNP to 64.

\A1 Sets the maximum block size in MNP to 128.

\A2 Sets the maximum block size in MNP to 192.

\A3 Sets the maximum block size in MNP to 256.

\G Uses XON/XOFF flow controls. Not supported by the g18.

\S Shows the status of the commands and S-Registers in effect.

Table 15. FAX Class Commands

Command Function Remark

"FCLASS" Selects mode 0 – data1 – fax

Class 1

"FAE" fax_auto_answer Class 1

"FRH" fax_receive_hdlc_data Class 1

"FRM" fax_receive_data Class 1

"FRS" fax_receive_silence Class 1

"FTH" fax_transmit_hdlc_data Class 1

"FTM" fax_transmit_data Class 1

"FTS" fax_transmit_silence Class 1

Table 16. General ETSI 07.07 Commands

Command Description Reference

+CGMI Requests manufacturer identification

5.1

+CGMM Requests model identification

5.2

+CGMR Requests revision identification

5.3

+CGSN Requests product serial number identification

5.4

+CSCS Selects TE character set

5.5

Table 15. FAX Class Commands

Command Function Remark

98-08901C39-B 49

Software Interface

+CIMI Requests international mobile subscriber identity

5.6

+GCAP Requests overall capabilities of TA

V25ter section 6.1.9

Table 17. ETSI 07.07 Call Control Commands and Methods

Command Description Reference

+CSTA Selects type of address and selects dial characters allowed in dial string

6.1

D Dial modesDial modifiers for V.25ter dialing

6.2

D>X V.25ter: Direct dialing from phone books where x is the location

6.3

+CMOD Call mode 6.4

+CHUP Hangs-up call (similar to ATH)

6.5

+CBST Selects bearer service type (baud rate, V110/RLP, and so on.)

6.7

+CRLP Radio link protocol parameters

6.8

+CR Service reporting control (result codes)

6.9

+CEER Extended error report (report failure reason of last call)

6.10

+CRC Cellular result codes 6.11

Table 16. General ETSI 07.07 Commands (Continued)

Command Description Reference

Table 18. ETSI 07.07 Mobile Extended Error Report

Command Description

+CEER Extended error report

+CEER ERROR

1 Unassigned or unallocated number3 No route to destination6 Channel unacceptable8 Operator determined barring16 Normal call clearing17 User busy18 No user responding19 User alerting, no answer21 Call rejected22 Number changed26 Non selected user clearing27 Destination out of order28 Invalid number format (incomplete

number)29 Facility rejected30 Response to STATUS ENQUIRY31 Normal, unspecified33 Command aborted34 No circuit/channel available38 Network out of order41 Temporary failure42 Switching equipment congestion43 Access information discarded44 Requested circuit/channel

unavailable47 Resources unavailable, unspecified49 Quality of Service unavailable50 Requested facility not subscribed55 Incoming calls barred within the

CUG57 Bearer capability not authorized58 Bearer capability not presently

available63 Service or option not available,

unspecified65 Bearer service not implemented69 Requested facility not implemented70 Only restricted digital information

bearer capability is available79 Service or option not implemented,

unspecified81 Invalid transaction identifier value87 User not member of CUG88 Incompatible destination

50 98-08901C39-B

Software Interface

+CEER ERROR

91 Invalid transit network selection95 Semantically incorrect message96 Invalid mandatory information97 Message type non-existent or not

implemented98 Message type not compatible with

protocol state99 Information element non-existent or

not implemented100 Conditional IE error101 Message not compatible with

protocol state102 Recovery on timer expiry111 Protocol error, unspecified127 Inter-working, unspecified

Table 19. ETSI 07.07 Network Service Related Commands

Command Description Reference

+CNUM Subscriber number 7.1

+CREG Network registration 7.2

+COPS GSM network operator selection

7.3

+CLCK Facility lock 7.4

+CPWD Changes password 7.5

+CLIP Calling line identification presentation

7.6

+CLIR Calling line identification restriction

7.7

+CCFC Call forwarding number and conditions

7.10

+CCWA Call waiting 7.11

+CHLD Call-related supplementary services

7.12

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

Command Description

+CTFR1* Reject an incoming call, and divert it to the voice mail (not to another number)

7.13

+CAOC Advice of charge 7.15

+CLCC Lists current calls and asynchronous answers

7.17

+CPOL Preferred operator list 7.18

*This command is based on the +CTFR standards.

Table 20. ETSI 07.07 Mobile Equipment Control and Status Commands

Command Description Reference

+CPAS Phone activity status (off, on, online)

Return Code - Meaning+CPAS:000 - Ready+CPAS:001 - Unavailable+CPAS:002 - Unknown+CPAS:003 - Ringing+CPAS:004 - Call in process+CPAS:005 - Asleep

8.1

+CPIN Enter/change PIN (4 - 8 digits)

8.3

+CSQ Signal quality 8.5

+CMEC Mobile equipment control mode (optional if keypad and display not supported)

8.6

+CKPD Keypad control 8.7

+CDEV Display Control - upon sending AT+CMER=0,0,1 current text display report is received

8.8

Table 19. ETSI 07.07 Network Service Related Commands (Continued)

Command Description Reference

98-08901C39-B 51

Software Interface

+CIEV Indicator Control - upon sending AT+CMER=0,0,0,1 current indicator report is received

8.9

+CMER Mobile equipment event reporting

8.10

+CPBS Selects phone book memory storage (optional if phone book not supported)

8.11

+CPBR Reads phone book entries

8.12

+CPBF Finds phone book entries

8.13

+CPBW Writes phone book entry

8.14

+CRSM Restricts SIM access 8.18

+CMUT* Mute control – use AT+CIP with IP_MUTE_REQ command for mute toggling

8.24

*This command is not supported by the g18. To obtain +CMUT functionality, use +CIP AT command, and follow the instructions above.

Table 21. ETSI 07.07 Mobile Equipment Errors and Status Reports

Command Description Reference

+CMEE Report mobile equipment error

9.1

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

Command Description Reference

+CME ERROR

0 Phone failure1 No connection to

phone2 Phone-adaptor link

reserved3 Operation not

allowed4 Operation not

supported5 PH-SIM PIN

required6 PH-FSIM PIN

required7 PH-FSIM PUK

required10 SIM not inserted11 SIM PIN required12 SIM PUK required13 SIM failure14 SIM busy15 SIM wrong16 Incorrect

password17 SIM PIN2

required18 SIM PUK2

required20 Memory full21 Invalid index22 Not found23 Memory failure24 Text string too

long25 Invalid characters

in text string26 Dial string too

long27 Invalid characters

in dial string30 No network

service31 Network time-out32 Network not

allowed - emergency calls only

9.2

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

Command Description Reference

52 98-08901C39-B

Software Interface

4.11 V.25TER COMMANDS USED WITH GSM

The following are the V.25ter commands that can be usedwith GSM.

Table 22. V.25ter Commands Used with GSM

Command Description V.25ter Reference

&C DCD (received line signal detector) behavior.

6.2.8

&D DTR (data terminal ready) behavior.

6.2.9

&F Set to factory-defined configuration.

6.1.2

+GCAP Request complete capabilities list.

6.1.9

+CGMI Request manufacturer identification.

6.1.4

+CGMM Request model identification.

6.1.5

+CGMR Request revision identification.

6.1.6

+CGSN Request product serial number ID (IMEI).

6.1.7

A Answer. 6.3.5

D Dial. 6.3.1

E Command echo. 6.2.4

H Hook control. 6.3.6

I Request identification information.

6.1.3

O Return to online data state.

6.3.7

S0 Automatic answer. 6.3.8

S2 Read/set escape code character.

S3 Command line termination character.

6.2.1

S4 Response formatting character.

6.2.2

S5 Command line editing character.

6.2.3

S7 Connection completion time-out.

6.3.10

S24 Sleep mode.

Sn for n equals to 14, 21, 22, 31, 36, 39, 40, 41

Bit map registers.Note: S14 is a read only register. When trying to type it will return OK but value is not changed.

S94 Sidetone enable/disable (unmute/mute) feature for analog audio devices. When ATS94=1, sidetone is enabled (default).

S95 Bitmap register for extended result code.

S96 Echo cancelling feature for audio analog devices by ATS96=1.

S97 Antenna diagnostic feature: ATS97? will respond with 000 or 001. 000 means that either the antenna is not connected or the hardware does not support this feature.

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

Command Description V.25ter Reference

98-08901C39-B 53

Software Interface

S98 ATS98=1 allows the handset’s backlight to behave as if the unit was not powered by using the TS line. It turns off the backlight immediately, for the first time after powering up.Note: ATS98=x is allowed only for x=1.

S99 ATS99=x, where x defines the length in ms of the hardware pulse given when GPRS coverage is changed from no coverage to coverage. The pulse length is 2x when 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.

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 time the last character was sent 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.

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

Command Description V.25ter Reference

S101 Sets wakeup line forever when x=1, and resets it when x=0. ATS101? returns the current state. These operations are allowed only when the factory bit is set. When the parameters are incorrect, or the factory bit is not set, returns an error.

V DCE response format. 6.2.6

X Result code selection and call progressmonitoring control.

6.2.7

Z0 Restores stored profile 0 6.1.1

Z1 Restores stored profile 1 6.1.1

Table 23. V.25ter Voice Commands

Command Description

*A Voice answer.

*D Voice dial.

; Dial modifier

Modifier for voice dial.

A Voice answer.

H Voice hang-up.

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

Command Description V.25ter Reference

54 98-08901C39-B

Software Interface

4.12 ETSI 07.05 STANDARD (SMS)The following tables list the complete set of commands asdescribed in ETSI standard 07.05. For each command it isrecommended that you use the ? option to query the modemfor the particular details of each command. For example, useAT+CR? to get the full details on the +CR command.

Block mode is a stand-alone mode that makes use of full textcommands and responses to send and receive SMSmessages. This is an older mode that is provided forcompatibility reasons. It is recommended that PDU mode beused instead of block mode. Text mode is not supported bythe modem. PDU mode is the preferred method since it is thesimplest and easiest to use.

4.12.1 Block Mode

SMS block mode is described fully in GSM 07.05, section 2.

Table 24. ETSI 0705 TE Commands Sent from Host to Phone

Command Description ETSI 07.05Reference

ACKNOWLEDGE MESSAGE

Acknowledges receipt of INC MESSAGE or MESSAGE ARRIVED

2.4.1.12

DELETE MESSAGE

Deletes SMS message

2.4.1.9

END SMS MODE Terminates SMS/CBS mode of the DTE/DCE interface

2.4.1.11

GET FIRST MESSAGE

Retrieves the first message stored on the phone

2.4.1.3

GET MESSAGE Retrieves a specific message stored on the phone

2.4.1.2

GET NEXT MESSAGE

Retrieves the next message stored on the phone

2.4.1.4

INDICATE INC SMS

Requests notification of any incoming SMS messages

2.4.1.6

INSERT SMS Sends an SMS message

2.4.1.8

LIST REQUEST Requests list of messages stored on the phone

2.4.1.1

TRANSFER INC CBS

Requests direct transfer of broadcast messages directly to host computer

2.4.1.7

TRANSFER INC SMS

Requests direct transfer of incoming SMS messages from the air directly to host computer

2.4.1.5

UNABLE TO PROCESS

Indicates that a phone message could not be processed

2.4.1.10

Table 25. ETSI07.05 MT Responses Sent from Phone to Host

Response Description ETSI 07.05Reference

DELETE MESSAGE COMPLETE

Host’s request to delete a message has been completed

2.4.2.8

DELETE MESSAGE FAILURE

Host’s request to delete a message has failed

2.4.2.9

END SMS MODE

Phone is exiting SMS mode

2.4.2.11

Table 24. ETSI 0705 TE Commands Sent from Host to Phone (Continued)

Command Description ETSI 07.05Reference

98-08901C39-B 55

Software Interface

4.12.2 Text Mode

Text mode is fully described in GSM 07.05, section 3.

The g18 module does not support text mode, however thefollowing commands are supported, since they are useful forPDU mode.GET

MESSAGE FAILURE

Request for a message cannot be fulfilled

2.4.2.3

INC MESSAGE

Incoming message transfer to host has been requested

2.4.2.4

INSERT SMS COMPLETE

Host’s request to insert a message has been completed

2.4.2.6

INSERT SMS FAILURE

Host’s request to insert a message has failed

2.4.2.7

MESSAGE Indicates a message has been requested

2.4.2.2

MESSAGE ARRIVED

Indication of incoming messages has been requested

2.4.2.5

MESSAGE LIST

Indicates receipt of LIST REQUEST

2.4.2.1

REQUEST CONFIRMED

Request received and will be performed

2.4.2.12

UNABLE TO PROCESS

Host’s request could not be processed

2.4.2.10

Table 25. ETSI07.05 MT Responses Sent from Phone to Host (Continued)

Response Description ETSI 07.05Reference

Table 26. ETSI 07.05 Text Mode

Command Description ETSI 07.05Reference

+CSMS Select message service (phase 2, phase 2+, and so on)

3.2.1

+CPMS Preferred message storage

3.2.2

+CMGF Message format: PDU or text mode selection, PDU = default

3.2.3

+CESP Enter SMS block mode protocol

3.2.4

+CMS Message service failure result code:0 - 127 GSM 04.11 Appendix E-2 values128 - 255 GSM 03.40 sub-clause 9.2.3.22 values300 ME failure301 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

3.2.5

56 98-08901C39-B

Software Interface

4.12.3 PDU Mode

PDU mode is described fully in GSM 07.05 Section 4. PDUmode uses the same commands and responses as the Textmode described above. However, PDU mode uses differentformats for the following commands and responses.

In addition, refer to GSM 04.11 and GSM 03.40 for detailson formatting the Service Center Address and TransportData Protocol Unit of the SMS PDU.

+CMS 311 SIM PIN required

312 PH-SIM PIN required

313 SIM failure314 SIM busy315 SIM incorrect316 SIM PUK

required317 SIM PIN2

required318 SIM PUK2

required320 Memory failure321 Invalid

memory index322 Memory full330 SMSC

address unknown

331 No network service

332 Network time-out

340 No +CNMA acknowledge-ment expected

500 Unknown error

3.2.5

+CMGD Deletes message 3.5.4

+CSCA Service centre address

3.3.1

+CNMI Indicates new message

3.4.1

+CMGL Lists messages 3.4.2

+CMGR Reads message 3.4.3

+CNMA Acknowledges new message to ME/TA

3.4.4

+CMSS Sends message from storage

3.5.2

Table 26. ETSI 07.05 Text Mode (Continued)

Command Description ETSI 07.05Reference

Table 27. ETSI 0705 PDU Mode

Command Description ETSI 07.05Reference

+CMGL Lists messages 4.1

+CMGR Reads message 4.2

+CMGS Sends message 4.3

+CMGW Writes message 4.4

+CNMA Acknowledges new message to ME/TA

4.6

+CMSS Sends message from storage

4.7

98-08901C39-B 57

Software Interface

GPRS COMMANDS

Table 28. ETSI 07.07 Commands for GPRS

Command Function Reference

+CGDCONT Defines, modifies or removes a PDP context

10.1.1

+CGQREQ Defines, modifies or removes a requested Quality of Service profile

10.1.2

+CGQMIN Defines, modifies or removes a minimum required Quality of Service profile

10.1.3

+CGATT Attaches/detaches GPRS requests

10.1.4

+CGACT Activates/deactivates PDP context request

10.1.5

+CGPADDR Shows PDP address 10.1.8

+CGCLASS Interfacing mobile station class parameters (stores, manages, retrieves)

10.1.11

58 98-08901C39-B

98-08901C39-B

5. MUX INTEGRATION

5.1 GENERALThe g18 is supplied with an internal GSM 07.10 protocolstack, also referred to as a multiplexer or MUX.

This software utility provides the user with two virtualchannels on one physical connection (an RS232 line).

The g18 with multiplexer support allows data (CSD/GPRS)and command (AT commands set) services simultaneously.

In this way, a user can make network and phone serviceinquiries and maintain data communication at the same time.

5.2 MUX INTEGRATION REQUIREMENTS

• g18 version E6.12.24 or higher (with MUX support)• MUX software implementation within your product

(terminal, and so on)• Hardware flow control implementation

5.3 MUX OPEN SERVICEThe following procedure describes how to open the MUXservice:

1. Send the AT+CMUX=0 command to g18 (for initiationof the GSM 07.10 protocol).

2. Wait for the OK response.

3. Open the MUX within ten seconds, as described insection 5.9.2.2.1 (otherwise, the g18 will exit MUXmode and revert back to one channel in 0705/0707mode).

4. Three channels must be opened; one for control and theother two for information.

5. Use Channel 1 for CSD or GPRS.

6. Use Channel 2 for the AT COMMAND set.

5.4 MUX CLOSE SERVICEThe following procedure describes how to close the MUXservice:

1. Close any CSD/Voice/GPRS connections.

2. Close MUX, as described in section 5.9.2.2.2, or togglethe hardware DTR signal.

3. The MUX remains open as one channel in 0707/0705mode.

5.5 DATA TRANSFERAfter the MUX is open the user can send and receive data inthe two virtual channels, channel 1 and channel 2.

The user can also send and receive MUX command data onthe control channel (channel 0).

5.6 TWO CHANNEL LIMITATIONUsing two channels has the following limitations:

1. Use Channel 1 for CSD/GPRS. AT COMMAND usageon this channel is only allowed for establishing orreleasing a connection.

2. Use Channel 2 for AT COMMANDS, VOICE CALLand SMS.

3. The g18 profile setup (S(x)-register) will be the samefor all channels (one modem). For example, when theatsx command is sent from either Channel 1 or Channel2, the modem S(x)-register changes and affects bothchannels.

4. When the g18 is in CSD negotiation mode, meaningfrom ATD until the CONNECT/NO CARRIERmessage appears, the user must not send any commandson Channel 2.

59

MUX Integration

5.7 SYSTEM BEHAVIORThe following are system behavior guidelines while in MUXmode:

1. Using the AT+CBAUD command is prohibited inMUX mode.

2. Channels 1 and 2 have the same baud-rate and the samehardware flow control.

3. Both AT+CMUX=0 and MUX services can beactivated without a SIM card.

4. When Channel 1 is in CSD data mode, the connectionshould be released by sending the +++ sequence, andthen sending the ATH command.

5. When Channel 1 is in GPRS data mode, the connectioncan be released by sending either the +++ sequence,LCP_TERMINATE or ATH command, or by using thevirtual DTR toggle.

6. In MUX mode, use virtual V24 signals since the DTRand DCD hardware signals are not relevant in the MUX.

7. AT commands that create unsolicited reports should beset in the MUX mode in order to receive the correctunsolicited AT commands indications (CLCC, CSCB,and so on). Only the CIPE command should remain inPREMUX mode.

8. Activate the +CIPE command before the +MUXcomand in order to receive the correct CIP confirmationin the MUX mode.

9. When in CSD data call mode, close the call beforeexiting the MUX.

10. Do not use the ATZ command on a channel on which aCSD call is not released.

11. When using the A/ command on two virtual channels,the A/ command repeats the last entered commandaccording to the time and not per channel.

12. When both a GPRS call and Voice calls are establishedon the virtual channels, the Voice call should bereleased first and then the GPRS call. If the GPRS callis released first, the Voice call can only be releasedfrom the HandSet and not by the ATH command.

13. When any Data call is established on the first channel,RING cannot be released by the ATH command on thesecond channel. Use AT+CTFR1 instead to release theRING.

14. Do not use the +IPR command in the MUX mode.

5.8 SUPPORTED PROTOCOL SERVICESThe following is a list of supported protocol services:

1. The g18 Support Multiplexer ETSI 07.10 - Non ErrorRecovery Mode - Basic Option.

2. The Multiplexer Flow Control Service (5.1.8.1.4 in thespecifications).

3. Channel Establishment:

• Purpose: Used to add a new channel.• Usage: Permitted channel ID numbers are 0–2.

4. Channel Release Services:

• Purpose: Used to disconnect the existing channel.• Usage: On existing channel.

5. Data Service:

• Purpose: Used for data transmissions.• Usage: For data transfer between the g18 and the

terminal. 6. 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 forthis purpose.

7. 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 linkquality between the two 07.10 entities (g18and terminal).

• Usage: To send test frame and to check replyframe (must be equal).

8. MSC ( Modem Status Command)

9. 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 havethe MUX entity installed with the product. The followingtwo MUX Integration options are available to the user:

• MIP (Mux Integration Packet): The user receives thesource code, which is provided by Motorola, with knownAPIs for the MUX.

• MUI (Mux User Implementation): The GSM 07.10protocol is implemented by the user.

5.9.1.1 ArchitectureThe Mux 0710 packet architecture is shown below.

Figure 42. Mux Architecture

The MIP (Mux Integration Packet) is a Motorola opensource code packet for GSM 07.10 protocol with APIfunctions provided for the user.

The MUI (Mux User Implementation) is the userimplemenetation device for the GSM 07.10 protocol.

Each of the following points represents an API userinterface, as shown in Figure 42, above:

• Point 1: The RX data is generated by the user ISR. At thispoint the data is unpacked and dispatched to the correctAPI TS0710_rx_handler_api channel.

• Point 2: The MIP either generates or triggers an APIfunction 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 APITS0710_application_send_data channel.

• Point 4: The MIP either generates or triggers an APIfunction for sending the API USER_tx_service() frameTX.

• Point 5: The Mgr is used to close the MUX, open theMUX and for testing (echo, ping).

5.9.1.2 APIsThere are five API user integrations, as follows:

• Open service• Close service• Sending Data service• Receiving Data service• MUX service test, msc, fc and so on (all to control

channel)

5.9.1.2.1 Open ServiceThe API Open Service MIP and MUI procedures are as follows:

MIP: Use API TS0710_open_all_MUX_channels().

MUI:

1. Send establish for control channel (07.10 SABMcommand frame for Channel 0).

2. Wait for ACK (07.10 UA command frame).

3. Send establish for the first channel (07.10 SABMcommand frame for Channel 1).

4. Wait for ACK (07.10 UA command frame).

5. Send establish for the second channel (07.10 SABMcommand frame for Channel 2).

6. Wait for ACK (07.10 UA command frame).

5.9.1.3 Close ServiceThe API Close Service MIP and MUI procedures are as follows:

MIP:

1. Use API TS0710_close_all_MUX_channels().

2. Wait for third ACK (07.10 UA command frame).

MUI:

1. Send release for second channel (07.10 DISC commandframe for Channel 2).

2. Wait for ACK (07.10 UA command frame).

3. Send release for first channel (07.10 DISC commandframe for Channel 1).

4. Wait for ACK (07.10 UA command frame).

5. Send release for control channel (07.10 DISC commandframe for Channel 0) or 07.10 CLD command frame.

6. Wait for ACK (07.10 UA command frame).

5.9.1.4 Sending Data ServiceThe API Sending Data Service MIP and MUI procedures are as follows:

MIP: Use API TS0710_application_send_data (MUX_CHANNEL dlc,BYTE data_length, BYTE *data_body).

MUI:

• Use UIH frame with the data encapsulated for sendingChannel 1 data.

• Use UIH frame with the data encapsulated for sendingChannel 2 data.

5.9.1.5 Receiving Data ServiceThe API Receiving Data Service MIP and MUI procedures are as follows:

MIP:

1. Use API BYTE TS0710_rx_handler_api(BYTE* rx_string, WORD len_rx_string)for unpack frames.

2. Use TS0710_DLC_APP_rx_handler_api (MUX_CHANNEL dlc,BYTE bytes_in_queue) for reading the arrival data from the channel buffer void.

MUI: Create data unpack.

5.9.1.6 MUX Service Test, MSC, FC, and so on (all to control channel)

MIP:

1. Void ts_0710_send_CLD_cmd (DLC_CMD_OR_RESP type )

2. Void ts_0710_send_test_req (BYTE* test_DATA, WORD test_DATA_length)

3. Void ts_0710_send_Channel_DTR_status (BYTE DTR_Signal, BYTE dlc)

4. Void ts_0710_send_test_req (BYTE* test_DATA, WORD test_DATA_length)

62 98-08901C39-B

98-08901C39-B

6. HARDWARE

6.1 GENERALThe following vendor and parts information is provided as arecommended solution for acquiring host interface, modemantenna and evaluation board components. You may alsosearch for and find your own solution for acquiring therequired components.

6.2 HOST INTERFACE

6.2.1 Modem I/O Connector

For the modem-to-host interface, use the 36-pin ZIF-styleserial connector. Use the following description to orderconnectors from ELCO:• Part number 04 6240 036 003 800Motorola recommends that you use the same connector forthe host-to-modem interface connection.

6.2.2 Interface Cable

The serial interface cable is a 36-pin 0.5 mm pitch flexibleprinted circuit (FPC). Use the following descriptions toorder 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 “mateswith ELCO 6240 series connector” indicates that the FPC isto be connected to an ELCO connector.

6.3 ANTENNAS

6.3.1 GSM Antenna

The g18 is supplied without an antenna and the customermust choose which antenna will be used. The style of theantenna is highly dependent on the particular projectrequirements.

Recommended values:Frequencies GSM 900: TX band: 880 - 915 MHz

RX band: 925 - 960 MHzDCS: TX band: 710 - 1785 MHz

RX band: 1805 - 1880 MHzPCS: TX band: 1850 - 1910 MHz

RX band: 1930 - 1990 MHzGain 0 dBi (Unity) gain or greaterImpedance 50 OhmVSWR 1.5:1 typical

63

Hardware

6.3.2 GPS Antenna (Recommendation)

6.3.3 Antenna Connector

The antenna connector on the g18 for the GSM and GPS portis a 82MMCX-S50-0-3 (female). Mating connectors to the82MMCX include the following two options only:

11MMCX Straight connector (male)

16MMCX Right-angle connector (male)

Use the preceding descriptions to order antenna connectorsfrom Huber-Suhner.

6.3.4 Antenna Cable Assembly

The antenna cable assembly, as supplied in the MotorolaDeveloper’s Kit, uses a SMA (female) with an 8-inchRG316 cable to a male MMCX connector.

The following options can be ordered as antenna cableassemblies from Huber-Suhner:

RG316/16MMCX/21SMA/.203M Straight jack

RG316/16MMCX/24SMA/.203M Bulkhead jack

An alternate supplier, Conectec, can also provide long 90°MMCX connectors and RF cable assemblies.

Huber-Suhner and Conectec also provide assemblies withother connector types.

6.4 DEVELOPER’S KITThe Motorola Developer’s Kit, part number S9002, includesthe following parts and part numbers:

Handset with SIM CR SCN5011x

Handset without SIM CR SCN5012x

Headset SYN6962

Headset SYN4937

Microphone SMN4097

Speaker SNN4018

GPRS Manager SVN4503

Short Flex Cable 50mm 3086229J10

Long Flex Cable 300mm 3086229J09

Coax Cable 200mm (MMCX/SMA) 3085720G01

6.5 VENDOR CONTACTSAllgon Antenna AB

Box 500, SE-18425 Akersberga, Sweden

Cap-XX

1709 Crooked Pine DriveMyrtle Beach, SC 29575U.S.A.

Frequency 1575.42 MHz (L1)Bandwidth ± 1.023 MHzPolarization Right-hand circularImpedance 50 OhmGain requirement 10 to 26 dB (at receiver input)Gain pattern +0 dBic minimum at zenith

-10 dBic minimum at 0° elevationNoise figure 1.8 dB typical

2.2 dB maximumVSWR 1.5:1 typical

2.5:1 maximumAxial ratio 3 dB typical at zenith

6 dB maximum at zenith1 dB compression point

-14 dBm typical (at antenna output)

3 dB frequency bandwidth

45 MHz maximum

25 dB frequency rejection

± 95 MHz

Ground plane 15 x 15 cm (recommended)

Phone: +46 (0) 8 540-601-20Fax: +46 (0) 8 540-676-16Website: www.allgon.seEmail: info@allgon.seProduct: Antennas

Phone: +1 (843) 215-2584Fax: +1 (843) 215-4419Website: www.cap-xx.comEmail: jmr@peoplepc.comProduct: Super capacitors

64 98-08901C39-B

Hardware

Centurion

44th StreetLincoln, Nebraska 68504U.S.A..

Conectec RF, Inc.

2155 Stonington Way, Suite 108Hoffman Estates, IL 60195U.S.A.

ELCO ZIF Connector

AVX Ltd.

Admiral HouseHarlington WayFleet, HampshireEngland GU13 8BB

Africa

Europe

Middle East

AVX/Kyocera (Singapore) Pte Ltd.

39A Jalan Pemimpin#07-00 TAL BuildingSingapore 577183

AVX Corporation

801 17th Avenue SouthMyrtle Beach, SC 29578-0867U.S.A.

South America

Electro Mech, Inc.

2 Cordier Street Irvington, NJ 07111U.S.A.

Galtronics LTD

P.O. Box 1569Tiberias 14115Israel

Bogart, Georgia

Phone: +1 (402) 474-0706Fax: +1 (402) 423-3358Website: www.centurion.comEmail: bobb@centurion.comProduct: Antennas

Phone: +1 (847) 519-0100Fax: +1 (847) 519-1515Website: noneEmail: ctecrf@ix.netcom.comProduct: Antenna cable assemblies

Phone: +44 (0) 1252 770-062Fax: +44 (0) 1252 770-104

Phone: +44 (0) 1252 770-130Fax: +44 (0) 1217 057-145

Phone: +44 (0) 1252 770-062Fax: +44 (0) 1252 770-104

Phone: +65 350-4892Fax: +65 258-1756

Phone: +1 (843) 946-0585Fax: +1 (843) 626-5292

Phone: +1 (843) 946-0392Fax: +1 (843) 626-2396

Phone: +1 (201) 318-7999Fax: +1 (201) 318-7995Website: noneEmail: noneProduct: Power supplies, Framatome connectors,

SIM connector supplier

Phone: +972 (0) 6 673-9777Fax: +972 (0) 6 673-3000Website: http://www.galtronics.com/Email: noneProduct: Antennas

Phone: +1 (706) 546-0087Fax: +1 (706) 546-1298

98-08901C39-B 65

Hardware

San Diego, California

Chicago, Illinois

Tianjin, China

Japan

Livingston, UK

Huber+Suhner

1014 East Algonquin RoadSuite 104, Schaumburg, IL 60173U.S.A.

Huber+Suhner Hong Kong Ltd.

Suite 902, 9/F Jubilee Centre18 Fenwick St,Wanchai, Hong Kong

Huber+Suhner (Singapore) Pte. Ltd.

1 Tuas Basin CloseSingapore 638803

Larsen Electronics

3611 N.E. 112th Ave.Vancouver, WA 98682U.S.A.

Parlex Corporation

7 Industrial WaySalem, NH 03079U.S.A.

Santac Connectors

North AmericaMVP Sales820 South Bartlett RoadSuite 108Streamwood, IL 60107U.S.A.

Phone: +1 (858) 451-3730Fax: +1 (858) 451-3571

Phone: +1 (262) 942-7259Fax: +1 (262) 942-7260

Phone: +86 22 26517176/7Fax: +86 22 26517178

Phone: +81 (0) 47 394-8227Fax: +81 (0) 47 394-8244

Phone: +44 (0) 1506 460-430 Fax: +44 (0) 1506 461-007

Phone: +1 (847) 397-2800Fax: +1 (847) 397-2882Website: www.hubersuhnerinc.comEmail: sschweizer@hubersuhnerinc.com

bburress@hubersuhnerinc.comProduct: Antenna cables and connectors

Phone: +852 2866-6600Fax: +852 2866-6313Product: Antenna cables and connectors

Phone: +65 861-8186Fax: +65 861-3316Product: Antenna cables and connectors

Phone: +1 (800) 778-7854, ext 711, 742Fax: +1 (360) 944-7556Website: www.larsenet.comEmail: pstorm@larsenet.comProduct: Antennas

Phone: +1 (603) 893-0040Fax: +1 (603) 894-5684Website: www.parlex.comEmail: jholdeman@parlex.comProduct: Serial interface cables

Phone: +1 (630) 483-8766 Fax: +1 (630) 483-1993Website: mvpsales@msn.com

66 98-08901C39-B

Hardware

Africa

Arrow Altech Distribution Ltd. 53-57 Yaldwyn Road Hughes Ext. Jet Park 1459 Johannesburg Post Office Johannesburg, South Africa

Asia

Samtec Asia Pacific Pte Ltd. 1 Kallang Sector #05-01 Kolam Ayer Industrial Park Singapore 349276

Europe

Samtec Europe Ltd. 117 Deerdykes View Westfield Industrial Estate Cumbernauld, Scotland UK G68 9HN

Middle East

Dimtec Adiel Ltd.

7 Propes St P.O. Box 7637 Ramat Gan Israel 52176

Phone: +27 (0) 11 923-9713Fax: +27 (0) 11 974-9683Email: djrodger@arrow.altech.co.za

Phone: +65 745-5955Fax: +65 841-1502Email: yvonne.tang@samtec.com

Phone: +44 (0) 1236 739-292Fax: +44 (0) 1236 727-113Email: julie.campbell@samtec.com

Phone: +972 (0) 3 678-1758Fax: +972 (0) 3 678-1738Email: oferdim@zahav.net.il

98-08901C39-B 67

Hardware

68 98-08901C39-B

98-08901C39-B

7. TESTING

7.1 GENERALThis section contains a product development checklist ofparameters to check, requirements to meet, and standards ofperformance to evaluate. You can use these process checksand functional test procedures to ensure that the g18Integrated Wireless Modem is well integrated into your hostproduct.

7.2 TESTING STAGESProper testing throughout the development and integrationcycle ensures that the final product works in both normaland exceptional situations. These tests are provided inseveral stages, as follows:1. Hardware integration

2. Desense and EMI

3. Regulatory compliance

4. Application software

5. Final assembly

6. End user problem resolution

7. OEM service depot repair

7.2.1 Hardware Integration

To ensure that the integration effort is carried out properly,monitor all relevant engineering standards, requirements,and specifications. In addition, perform functional testsduring product development to validate that the integratedpackage performs as intended.

7.2.1.1 Enabler FunctionsTo test the interaction between the modem and the host, yourproduct must be able to perform the following tests:

• Turn the various hardware components on and off. Thiscapability helps to isolate possible desense and otheremission problems.

• Pass data through the host between the modem and thetest platform. This allows external programming andconfiguration software to communicate with the modemwhile it is integrated within the host. For microprocessor-based products, the pass-through modeuses software emulation involving the host processor,which passes full-duplex serial port data to, and from, theintegrated modem.

7.2.1.2 Specific TestsIn addition to the various tests that exercise your owncircuitry (such as the power-on self test), design tests thatensure proper interaction between the modem and host.Ensure that the following hardware integration issues areevaluated:

RF Immunity RF transmissions of the modem donot interfere with operation of thehost.

Electrical Signaling Power sources and interface arefunctionally compatible betweenthe host and the modem.

Physical Parameters Physical configuration of themodem inside the host providesadequate ventilation, mounting,shielding and grounding.

Antenna Performance Integrated antenna system meets therequired ERP specifications,VSWR specifications and antennapropagation patterns.

ESD Requirements Host design protects the modemfrom ESD.

RF Re-radiation Host does not allow spuriousemissions in excess of 60 dBc, ascaused by carrier re-radiation.

69

Testing

7.2.2 Desense and EMI

Any host in which the modem is integrated generates someEMI (electromagnetic interference), which tends todesensitize the modem’s ability to receive at certainfrequencies. You should verify that the host equipment doesnot influence the g18 performance. (Refer to “Desense” onpage 199, for more information).

If desense was detected, one or more of the following can beperformed:1. Connect the antenna cable shield to the main ground

(PS ground).

2. Shield the logic section in the user application. (Most ofthe radiation can come from clocks and data linesaround the logic section due to the high rise/fall time ofthe 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 currentlyrequire approval from the local government regulatory body.In the U.S., the FCC requires that two individualrequirements be met before the final product can be certified.The first test, (FCC Part 15 Qualification), requires you toprove that the product electronics hardware does not yieldlocal radiation capable of affecting other equipment, such astelevisions, computer monitors, and so on.

The second test (FCC Part 24) requires you to prove thatwhen the modem transmits, it remains properly in itsallocated channel spacing and does not produce spikes orsplatter in other frequencies. Motorola undergoes FCCtesting with the modem integrated into a dummy OEM hostto ensure compatibility with these requirements. However,since the eventual transmit capability of the modem is highlyintegrated with the power supply and antenna system of thefuture host, the fully integrated product must be submittedfor final regulatory approval.

In addition, regulatory bodies can require the wirelessmodem to transmit random data patterns on specificfrequencies while incorporated in the host platform. Themodem incorporates special debug modes to allow this kindof testing, provided the host application can issue therequired commands to the modem.

The entire regulatory process can take many months tocomplete and should start early in the development cycle.The exact regulatory requirements of each country change

from time to time. For efficient regulatory processing, usethe services of specialized regulatory consultants todetermine the specific requirements at the time ofmanufacture.

To prepare for regulatory testing, you need to integrate thepass-through mode into the product design. For moreinformation, refer to “Enabler Functions” on page 69. The pass-through mode passes the RS-232 levels from anexternal computer to and from the modem. Motorolaprovides the ability to key and dekey the radio at the requiredfrequencies and modulation levels from an externalcomputer via the pass-through mode.

Nothing further is required for regulatory requirements forthe g18, which is approved for Part 24 when used in yourhost device. The product is approved by FCC and DOC. Thehost device will still require approval for Part 15.

For further information about regulatory compliance, referto “Regulatory Requirements” on page xiv.

7.2.4 Application Software

The following tests need to be performed to verify thecommunications links between the host and the modem andbetween the modem and the network, as follows:

Software Driver Configuration

Ensure that the host product can enable the modem serialport to permit the host and modem to communicate. This testverifies that the driver software functions well and isconfigured properly.

Network Configuration

Determine whether the host can use the modem tocommunicate with a GSM network. This test uses existingnetwork software in an attempt to communicate with aspecific network.

The final application must be able to respond correctly underall adverse network conditions, not only under idealconditions. To achieve this, the application software must besystematically tested against all possible failure andexception conditions. Situations such as low battery, out ofrange, host down, unexpected data, maximum message size,maximum peak/sustained throughput and other conditionsmust not cause the host application to fail. Each conditionmust have a specific remedial action to alleviate it.

Note

Ensure the g18 is set to the correct band.

70 98-08901C39-B

Testing

7.2.5 Final Assembly

A final assembly test is performed before shipment to ensurethat all components are working properly and issues such ascrimped antenna cables, loose connections, and impropersoftware load are resolved. During final assembly, themodem sends and receives a loopback message of maximumsize. The successful return of the sent message proves thatthe 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, testingmust quickly isolate the cause of the problem in the field. Forexample, is the problem caused by the terminal, the modem,the network, the configuration, or a user error? Can theproblem be fixed locally or does the unit need to be sent to aservice center?

It is time consuming and expensive to send products to aservice center, particularly if the problem is caused by atemporary network or host outage. For this reason, youshould design the application to enable the cause of theend-user problem to be established. Often this functionalitycan be designed together with the Help Desk, which supportsthe user by telephone and without access to the user’s screen.The application must enable the end user to relate the mostlikely cause of the problem to the Help Desk for a quicksolution.

Effective tests provide a systematic, positiveacknowledgment from each of the network components. Forexample:

Test 1 Is the OEM module able to pass its own self test?

Test 2 Is the OEM module able to communicate withperipherals?

Test 3 Is the OEM module able to communicate with theintegrated modem?

Test 4 Is the modem able to hear the network?

Test 5 Is the modem registered and allowed to operate onthe 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 firstrequirement is to determine whether the modem must be senton to Motorola for repair. A screening test must beperformed. In the screening test, the modem is mounted onto

the Motorola evaluation board and a loopback message issent to qualify the specific problem.

To set up this test, you need an evaluation board, aknown-good g18 modem (for comparison), and a powersupply. The end-to-end test can employ either a live networkor an over-the-air test involving a communications monitorthat can transmit and receive at the appropriate frequencies.The objective is to test the suspect modem in a known-goodenvironment, where all other components are known to beoperational.

7.3 DIAGNOSTIC UTILITYThis section describes how to develop a script to perform afactory end-of-line test of a g18 modem integrated in anOEM platform. This test provides a high degree ofconfidence that the modem is properly configured andintegrated, and is ready for shipment.

7.3.1 Quality Assurance Testing

Efficient, automated testing can ensure that the product isfunctional when delivered to the end user, especially whenOEM product manufacturing occurs in a region or countrythat is distant from the intended network.

Use the following checklist to verify that a product is readyfor shipment:1. The OEM host platform (without modem) is

operational.

2. The OEM host platform contains the correct softwareload.

3. The OEM host platform provides sufficient power tooperate 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 andnetwork registration information.

7. The OEM host communicates with the modem logicboard.

8. The OEM host is able to key up the radio with sufficientoutput at the antenna.

9. The modem can receive with sufficient signal strengthfrom the antenna port.

Note

OEM service operations are encouraged tomodify the following QA test procedure todevelop a test for the diagnostic screening ofrepair products.

98-08901C39-B 71

Testing

An automated test script provides more than diagnosticsupport. When you set up an automated test process, youensure that only those products that pass the test are labeledfor release. For example, since regulatory agencies requireproduct labeling for certification and approval, you candevelop an automated script to read the modem ID anddestination network from the modem and generate a labelwith the proper inscription.

7.3.2 Equipment Test Set-up

7.3.2.1 Calibration Tools and EquipmentThe following tools and equipment are required:

• For RF testing, use GSM simulators such as HP8960 orRohde & Schwarz CMU200 (or equivalent).

• For data testing, use a standard computer connecting theg18 to the serial port via Motorola Evaluation BoardS9002, or use the user’s equipment.

• Line modem.• Use the local network to make the communication.

7.3.2.2 Modem Test Setup

Figure 43. g18 Setup for Testing

7.3.2.3 Loop-back Test

Use any known file to transfer from COM1 to COM2 orfrom COM2 to COM1.

Getting Started• 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

for COM2.• Verify that each terminal receives a response from the

DCE device (send AT and verify OK response).• Start the test by sending a file from COM1 to COM2.

Measuring Additional Parameters• ATI3 g18 Software version.• ATI4 Product name.• AT+CSQ Reception signal quality (does not

support BER information).• AT+CMER=0,0,1 Shows data on the handset display.For additional information, consult the Motorola g18Customer Support Center:

• Help Desk phone number: +972 (0)3-5684040• Email: BSH015@email.mot.com

Note

Requirements for testing items 1 and 2 arespecific to each OEM product. A specificdescription of these items is beyond the scopeof this document.

Note

All communication between the DTE (thecomputer) and the DCE (g18 modem) occurs at57600 bps, no parity, 8 data bits, one stop bit.

Set the baud rate to 57600 bps usingAT+CBAUD=57600.

72 98-08901C39-B

98-08901C39-B

H. AT COMMANDS

8.1 BASIC FUNCTIONALITYMake 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+CME ERROR: <err>Enables the SIM card.

nnnn = PIN number (4 - 8 digits).If PIN is correct, “OK” is shown. 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>+CME ERROR: <err>Responds with information about the SIM and the PIN.

When no SIM is available: +CME ERROR: <err>

When PIN is not needed:+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

73

AT Commands

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

8.1.2 Feedback from the System

SIM/PIN Status Allowed Commands

AT Command Result for Non-allowed Commands +CPIN? Result

+CPIN? Code

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

Note

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.

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

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+cops? Provides the name of the network operator.

+COPS: 000, 000, “IL ORANGE”.

at+csq Provides the signal strength indication, for example +CSQ: 031,099.

+CSQ: 030, 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 the IP.

For example,AT+CMER=0,0,1,1,0.

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); orAT*D (phone number) orATD> <index>; orATD> <“name”> orATDS=n (n=0 to 3) orATD><mem><index>;

Dials the phone number (voice call). For example,ATD123456;ATD>102; ORATD>“DAN” ORATDS=1; ORATDS=0 ORATD>SM101;

OKNO CARRIER

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.

AT Command Action Examples

98-08901C39-B 75

AT Commands

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.

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.

Note

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.

AT Command Response/Action Remarks

ata Answers the call.

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+cpbf=“Name” The g18 shows the number on that position +CPBF: xxx, “phone number”, yyy, “Name of the entry”.

The “NAME” is a string up to first 3 characters. <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

8.1.7 Reading a Phone Book Entry

8.1.8 Phone Book Function

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, “Name of the entry”

The g18 writes the number on that position.

<xxx> Position in the memory. 0-100 Phone memory. 101-220 SIM card memory.<yyy> 129 Normal number.145 International number.

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 position +CPBR: xxx, “phone number”, yyy, “Name”.

<xxx> Position in the memory0–100 Phone memory101–260 SIM card memory<yyy> 129 Normal number145 International number

AT Command Response/Action Remarks

at+cpbs=“NN” This AT should be the first one to be used to select the phone book.

“FD” SIM fix dialing 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

8.1.9 Sending an SMS in PDU Mode

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 ofPDP 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.

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

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

List of supported memory.

at+cpbr=xxx For example:at+cpbr=101+CPBR: 101,“123456”,129,“AVI”

<xxx> is a number from 0 to 100, used to read from ME phone books; 101 to 220 is used to read from SIM phone books.

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 response: +CSMS: <mt>,<mo>,<bm>

<Service>0 For phase 2

+CSMS: 001,001,001 OK.

<mt>,<mo>,<bm>1 Supported2 Not supported

at+cpms=“sm” Preferred message storage response: +CPMS:<used1>,<total1>,<used2>,<total2>+CPMS: 001,0015,001,015 OK.

at+cmgs=160>0791947122720 00011000c91947 1628128430000a 704f4f29c0e ctrl-z

Sends an SMS in PDU mode return:+CMGS: 000.

Sends “TEST”:To phone # 49 -172 - 6188234 To SMS center 49 -172 - 2720000.For SMS coding, refer to “SMS Error Messages”, page 36.

AT Command Response/Action Remarks

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 inthe 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.

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#

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 toattach to their GPRS service.

Note

Bear in mind that the AT command AT+CGACT is not supported in all countries with GPRS. A GPRS connectionis also possible with ATD*99#. See the following section for more information.

Note

The above list is only for the AT command level. PPP information (DNSs) is not shown here.

98-08901C39-B 79

AT Commands

8.2 AT COMMAND LISTINGFor basic AT commands information, refer to “Basic AT Commands” on page 45.

8.2.1 ATD, Dialing

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

AT Command Response/Action Remarks

atd<number> OK

BUSY

NO CARRIER

<number> Data/Fax number

Called party is not available

No connection to the number

ATD (phone number); orAT*D (phone number) orATD> <index>; orATD> <“name”> orATDS=n (n=0 to 3) orATD><mem><index>;ATDLATD*99

ATDL: “<number>”

For voice calls only

Use without “;” for Data Call

Requests GPRS service “D”.Manual acceptance of a network request.

at*d xxxxxx Dials a voice call.

Note

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

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

Example

at+caoc=?

+CAOC: 0

OK

at+caoc=0

+CAOC: 000000

OK

AT Command Response/Action Remarks

at+caoc[=<mode>] +CAOC: <xxxx>OK+CME ERROR: <err>

<mode> 0 Query CCM value

<xxxx> The actual price of the current call (hex).at+caoc? +CAOC: <mode>

OK+CME ERROR: <err>

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

Note

Only available if the local network supports this command.

98-08901C39-B 81

AT Commands

8.2.3 AT+CCFC, Call Forwarding Number and Conditions

AT Command Response/Action Remarks

at+ccfc= <reason>,<mode>[,<number>[,<type>[,<class>[,<subaddr>[,<satype>[,<time>]]]]]]

When <mode>=2 and command is successful:+CCFC: <status>,<class1>[,<number>,<type>[,<subaddr>,<satype>[,<time>]]][<CR><LF>+CCFC: <status>,<class2>[,<number>,<type>[,<subaddr>,<satype>[,<time>]]] [...]]OKWhen <mode> is 0,1OK+CME ERROR: <err>

<reason> 0 Unconditional1 Mobile busy2 No reply3 Not reachable4 All calls forwarded5 All conditional calls forwarded

<Mode>0 Disable1 Enable2 Query status3 Registration4 Erasure

<Type> 145 International number 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 Voice2 Data4 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

at+ccfc? +CME ERROR: <err>

at+ccfc=? +CCFC: (list of supported <reason>s)

OK+CME ERROR: <err>

Note

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.

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. When <mode>=2 and command are successful:+CCWA: <status>,<class1> [<CR><LF>+CCWA: <status>,<class2> [...]]OKWhen <mode> is 0,1OK+CME ERROR: <err>

<n> Shows the result code in TA 0 Disable 1 Enable

<mode> 0 Disable 1 Enable 2 Query<status> 0 Not active 1 Active

<class>Sum of integers representing information for call blocking services 1 Voice2 Data4 Fax

at+ccwa? +CCWA: <n>OK+CME ERROR: <err>

at+ccwa=? +CCWA: (list of supported <n>s)OK+CME ERROR: <err>

Note

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

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 OK+CME ERROR: <err>

<mode> 0 Releases all held calls or sets

the User Determined User Busy (UDUB) for a waiting call.

1 Releases all active calls (if any exist) and accepts the other (held or waiting) call.

1X Releases a specific active call X.

2 Places all active calls (if any 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.

at+chld? +CME ERROR: <err>

at+chld=? +CHLD: (supported <mode>s)OK+CME ERROR: <err>

84 98-08901C39-B

AT Commands

CALL STATE (+CLCC)

+CHLD modes

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

IDLE Error 3. Error 3. Error 3. Error 3. Error 3. If there is no such call, returns error 22.

Error 3.

SINGLE ACTIVE

Error 3. Releases active.

When X = 1, release is active. If not, returns error 22.

Puts call on hold.

Error 3. If there is no such call, returns error 22.

Error 3.

MPTY ACTIVE

Error 3. Releases mpty call. Returns 2 "no carrier" when there are 2 outgoing calls.

Releases a specific call x. If there is no such call, returns error 22.

Puts mpty on hold.

Split. If there is no such call, returns error 22.

Error 3.

INCOMING CALL

Releases incoming call.

Error 3. Error 3. Error 3. Error 3. If there is no such call, returns error 22.

Error 3.

ACTIVE + WAITING

Releases waiting call.

Releases active call and accepts waiting call.

Releases a specific call x. If there is no such call, returns error 22.

Puts active call on hold and accepts the waiting call.

Error 3. If there is no such call, returns error 22.

Error 3.

MPTY ACTIVE + WAITING

Releases waiting call.

Releases mpty, accepts waiting.

Releases a specific call x. If there is no such call, returns error 22.

Puts mpty on hold, accepts the waiting call.

Splits. If there is no such call, returns error 22.

Error 3.

SINGLE HELD

Releases held call.

Accepts held call.

Error 3. Accepts held call.

Error 3. If there is no such call, returns error 22.

Error 3.

98-08901C39-B 85

AT Commands

HELD MPTY Releases held call.

Accepts mpty call.

Error 3. Accepts mpty call.

Error 3. If there is no such call, returns error 22.

Error 3.

DUAL Releases held call.

Releases active, accepts the other call.

Releases a specific call x. If there is no such call, returns error 22.

Switches. Error 3. If there is no such call, returns error 22.

Makes a conference call.

HELD + MPTY ACTIVE

Releases held call.

Releases mpty, accepts the other call.

Releases a specific call x. If there is no such call, returns error 22.

Switches. Error 3. If there is no such call, returns error 22.

Makes a conference call.

ACTIVE + MPTY HELD

Releases held call.

Releases active, accepts the mpty.

Releases a specific call x. If there is no such call, returns error 22.

Switches. Error 3. If there is no such call, returns error 22.

Makes a conference call.

HELD + WAITING

Releases waiting call.

Accepts the waiting call.

Error 3. Accepts the waiting call.

Error 3. If there is no such call, returns error 22.

Error 3.

HELD + MPTY ACTIVE + WAITING

Releases waiting call.

Accepts the waiting call.

Error 3. Accepts the waiting call.

Error 3. If there is no such call, returns error 22.

Error 3.

DUAL + WAITING

Releases waiting call.

Releases active, accepts waiting call.

Releases a specific call x. If there is no such call, returns error 22.

Error 3 (too many calls on hold).

Error 3. If there is no such call, returns error 22.

Joins the dual calls.

CALL STATE (+CLCC)

+CHLD modes (Continued)

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

86 98-08901C39-B

AT Commands

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

ACTIVE + MPTYHELD + WAITING

Releases waiting call.

Releases mpty active, accepts waiting call.

Releases a specific call x. If there is no such call, returns error 22.

Error 3 (too many calls on hold).

Error 3. If there is no such call, returns error 22.

Joins the dual and the mpty calls.

ACTIVE + MPTY HELD + WAITING

Releases waiting call.

Releases active, accepts waiting call.

Releases a specific call x. If there is no such call, returns error 22.

Error 3 (too many calls on hold).

Error 3. If there is no such call, returns error 22.

Joins the dual and the mpty calls.

Note

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

Switch: Puts the active call on hold and accepts the held call.

Error 3: "operation not allowed"

Error 22: "not found"

CALL STATE (+CLCC)

+CHLD modes (Continued)

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

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

+CME ERROR: <err>

<state>0 Enable clcc unsolicited

indication.1 Disable clcc unsolicited

indication.

<Direction> 0 Mobile originated call. 1 Mobile terminated call.

<Call State> 0 Active. 1 Held. 2 Dialing. 3 Alerting. 4 Incoming. 5 Waiting. 6 Released.

<Mode> 0 Voice Call. 1 Data. 2 Fax.

<Multiparty> 0 Call is not part of a conference

call. 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.

at+clcc +CLCC: <id1>,<direction>,<call state>,<mode>,<mpty>[,<number>,<type>,<alpha>

OK

+CME ERROR: <err>

at+clcc=? OK

+CME ERROR: <err>

at+clcc? +CLCC: <state>OK

+CME ERROR: <err>

Note

Add non-standard "released" state.Asynchronous answers are also allowed, by using at+clcc=1.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

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

AT Command Response/Action Remarks

at+clck=<facility>,<mode>[,<password>[,<class>]]

When <mode>=2, command is successful and <class> is relevant:+CLCK: <status>, <class1> [<CR><LF>+CLCK: <status>,<class2> [...]]OKWhen <mode>=0,1 and command successful:OK

+CME ERROR: <err>

<facility>CS Key padSC SIM CardAO Block all outgoing callsOI Block all outgoing international

callsOX Block outgoing international

calls except to home countryAI Block all incoming callsIR Block incoming calls when

roaming outside home countryAB All blocking servicesAG All outgoing blocking servicesAC All incoming blocking ServicesFD SIM fixed dialing feature

<mode>0 Unlock1 Lock2 Query status

<password>Call Block password or PIN1 to Lock/ Unlock SIM or PIN2 for SIM Fixed Dialing Feature

<class>Sum of integers representing of information for call blocking services 1 Voice2 Data4 Fax

<status>0 Not active1 Active

at+clck? +CME ERROR: <err>

at+clck=? +CLCK: (list of supported <facilitie>s)OK

+CME ERROR: <err>

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

Example

at+clip=1

OK

RING

+CLIP: “+496113611404”,145

RING

+CLIP: “+496113611404”,145

at+clip=?

+CLIP: (000,001)

OK

AT Command Response/Action Remarks

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

+CME ERROR: <err>

<n>0 Disable (default)1 Enable

<m>0 Clip not provisioned1 Clip provisioned2 Unknown

at+clip? +CLIP: <n>,<m>OK+CME ERROR: <err>

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

92 98-08901C39-B

AT Commands

at+clip=0

OK

RING

8.2.9 AT+CLIR, Calling Line Identification Restriction

Example

at+clir=?

+CLIR: (0,1,2)

OK

at+clir?

AT Command Response/Action Remarks

at+clir =<n> OK+CME ERROR: <err>

<n> 0 Used according to the clir service

subscription1 Enable 2 CLIR suppression in permanent

mode

<m> 0 Clir not provisioned 1 Clir provisioned 2 Unknown 3 Clir temporarily restricted4 Clir temporarily allowed

at+clir? +CLIR: <n>,<m>OK+CME ERROR: <err>

at+clir=? +CLIR: (list of supported <n>s)OK

+CME ERROR: <err>

Note

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

Order of Actions First Call behavior Other Calls behavior

CLIR via RS232 According to the action performed by RS232.

According to the action performed by RS232.

CLIR by HS According to the action performed by HS.

Default behavior.

CLIR by HS and then CLIR via RS232

According to the action performed by RS232.

According to the action performed by RS232.

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

According to the action performed by RS232.

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

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?

AT Command Response/Action Remarks

at+cmee=<n> Shows a description of the error OK+CME ERROR: <err>

<n> 0 Disable 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>

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)at+cmgs=<length> <CR> >PDU is given <ctrl-z/ESC>

Sends the SMS message.

The message is terminated with control-Z character (0x1A).

The command is aborted with <esc>. If the message is sent successfully: +CMGS: 000. OKIf the message is not sent successfully:+CMS ERROR: <err>

<length> Number of octets coded in the TP.

<cr> After terminating with <cr>, g18 returns with “>” and then, the PDU can be given from the TE.

<crtl-z> Indicates the end of the PDU.

at+cmgs? +CME ERROR: <err>

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

Note

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 viaAT+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

Example

at+CNUM=?

OK

at+CNUM

+CNUM: “voice”, “054556426”, 129

+CNUM: “data”, “054667739”, 129

+CNUM: “fax”, “054422417”, 129

OK

AT Command Response/Action Remarks

at+cnum +CNUM: <alpha1>,<number1>,<type1> [<CR><LF> +CNUM: <alpha2>,<number2>,<type2>[...]]OK+CME ERROR: <err>

Shows the numbers that were entered into “My Phone Numbers” from the Handset menu.

<alpha>Alphanumeric string, associated with <number>.

<number>String type, phone type.

<type>129 Normal number.145 International number with

access character +.

at+cnum?

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

Note

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

96 98-08901C39-B

AT Commands

8.2.13 AT+COPS, Operator Selection

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

AT Command Response/Action Remarks

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

Selects the operator OK+CME ERROR: <err>

<mode> 0 Automatic 1 Manual 2 De-register from network3 Set only <format>4 Manual/automatic

<format> 0 Long alphanumeric1 Short alphanumeric2 Numeric

<Operator status> 0 Unknown 1 Available 2 Current 3 Forbidden

at+cops=? +COPS:[list of supported (<stat>, long alpha numeric <oper>, short alphanumeric <oper>, numeric <oper>)][,, list of supported <mode>s), (list of supported <format>s)OK+CME ERROR: <err>

at+cops? +COPS: <mode>[,<format>,<oper>]OK+CME ERROR: <err>

Note

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

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

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

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

AT Command Response/Action Remarks

at+cpbs=<storage> OK+CME ERROR: <err>

<storage> FD SIM fix dialing phone book LD Last dialing phone book ME ME phone book MT ME and SIM phone bookSM SIM phone bookDD Direct Dial phone bookRC ME received calls listMC ME missed calls list

at+cpbs? +CPBS: <storage>[,<used>,<total>] OK+CME ERROR: <err>

at+cpbs=? +CPBS: (list of supported <storage>s)OK+CME ERROR: <err>

Note

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.

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

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

Example,

at+cpbs=“sm”;+cpbw=?

+CPBW: (101-220),020,(255,129,145),014 // SM phone book definitions: number length limited to 20, text length limitedto 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 limitedto 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 21digits 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 SMphone book

OK

at+cpbr=110

AT Command Response/Action Remarks

at+cpbw=[<index>], [,<number> [<type> [,<text>]]]

OK+CME ERROR: <err>

<index> Location number of the phone book

<number> Phone number in format <type>

<type> type of address: 129 Normal format 145 International format

<text> String type field of maximum <tlength> length.

<tlength> Maximum length of <text>

<nlength>Maximum length of <number>

at+cpbw? +CME ERROR: <err>

at+cpbw=? +CPBW: (list of supported <index>s),[<nlength>], (list of supported <type>s), [<tlength>] OK+CME ERROR: <err>

Note

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(ME or SM) instead of to the MT phone book. When writing to the SM or ME phone book, the g18 validates the stringlength for phone number and label, as defined for the specific phone book. When writing to the MT phone book, theg18 is unable to detect errors with a string length less than that allowed in MT phone book, but more than what isdefined in the specific phone book. In this case, the write action is not rejected, but the number and text will betruncated to the limit allowed for the specific phone book.

98-08901C39-B 101

AT Commands

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

OK

at+cpbs=“mt”

OK

at+cpbw=?

+CPBW: (001-200),32,(255,129,145),18

OK

at+cmee=2OK

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

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

AT Command Response/Action Remarks

at+cpin=<pin>[,<newpin>] OK+CME ERROR: <err>Enters or changes pin number. When entering the pin, a new pin is not required.

<pin> String type 4-8 digits.To enable SIM card or change PIN, insert the current PIN. When phone is blocked, insert the puk number.

<newpin> String type 4-8 digits. Used when changing PIN or unblocking phone.

<code>When PIN is not needed:READY

When PIN is needed: SIM PIN

When PUK number is needed:SIM PUK

When PIN2 is blocked:SIM PUK2

at+cpin? +CPIN: <code>OK+CME ERROR: <err>Responds with information about the SIM and the PIN.

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

Note

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.

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

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

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

AT Command Response/Action Remarks

at+creg=[<n>] OK+CME ERROR: <err>Controls the presentation of an unsolicited result code +CREG: <stat>

<n> 0 Disables network registration,

unsolicited result code (default)1 Enables network registration,

unsolicited result code2 Enables network registration

and location information, unsolicited result code

<stat> 0 Not registered 1 Registered (home network) 2 Not registered, but ME searches

for a network 3 Registration denied 4 Unknown 5 Registered roaming

<lac> 2-byte location code (hex)

<ci> 2-byte cell ID (hex)

at+creg? +CREG: <n>,<stat>[,<lac>,<ci>].OK+CME ERROR: <err>

at+creg=? +CREG: (list of supported <n>s)OK+CME ERROR: <err>

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

Example

at+csta?

+CSTA: 129

OK

at+csta=145

OK

AT Command Response/Action Remarks

at+csta=[<type>] OK+CME ERROR: <err>

<type> Number format129 Local phone number145 With international access code

character ‘+’Use default 145 when dialing string includes international access code character ‘+’, otherwise 129

at+csta? +CSTA: <type>OK+CME ERROR: <err>

at+csta=? +CSTA: (list of supported <type>s)OK+CME ERROR: <err>

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

Example

at+cbst=?

+CBST: (006,007,070,071),(000),(000-001)

OK

at+cbst?

+CBST: 007,000,001

OK

at+cbst=1,0,1

AT Command Response/Action Remarks

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

Sets the valueOK+CME ERROR: <err>

<speed>6 4800 bps (V.32)7 9600 bps (V.32)70 4800 bps (V.110)71 9600 bps (V.110)

<name>0 data circuit asynchronous

<ce> connection element0 transparent1 non-transparent

AT+CBST? +CBST: <speed>,<name>,<ce>OK+CME ERROR: <err>

AT+CBST=? +CBST: (list of supported <speed>s),(list of supported <name>s),(list of supported <ce>s)OK+CME ERROR: <err>

Note

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.

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

Example

at+cgmi

+CGMI: “Motorola”

OK

at+cgmi?

ERROR

AT Command Response/Action Remarks

at+cmgi +CGMI: <manufacture> OK+CME ERROR: <err>

<manufacture> Name of the manufacturer.

at+cmgi? +CME ERROR: <err>

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

108 98-08901C39-B

AT Commands

8.2.21 AT+CGMM, Requesting Model Identification

Example

at+cgmm?

ERROR

at+cgmm=?

OK

at+cgmm

+CGMM: “L Series”

OK

8.2.22 AT+CGMR, Requesting Revision Identification

Example

at+cgmr?

ERROR

at+cgmr=?

OK

at+cgmr

+CGMR: g18_vE6.02.07

AT Command Response/Action Remarks

at+cgmm +CGMM: <model>OK+CME ERROR: <err>

<model> Model identification

at+cgmm? +CME ERROR: <err>

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

AT Command Response/Action Remarks

at+cgmr +CGMR: <revision> OK+CME ERROR: <err>

<revision> Software revision number.Requests revision identification.

at+cgmr? +CME ERROR: <err>

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

98-08901C39-B 109

AT Commands

OK

8.2.23 AT+CGSN, Requesting Product Serial Number Identification

Example

at+cgsn?

ERROR

at+cgsn=?

OK

at+cgsn

+CGSN: “447764074608839”

OK

8.2.24 AT+CHUP, Hanging Up Calls

Example

at+chup=?

OK

RING

at+chup

AT Command Response/Action Remarks

at+cgsn +CGSN: <sn> OK+CME ERROR: <err>

<sn> IMEI number

at+cgsn? +CME ERROR: <err>

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

AT Command Response/Action Remarks

at+chup NO CARRIEROK

If there is an active call, hangs up.

at+chup? +CME ERROR: <err>

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

110 98-08901C39-B

AT Commands

NO CARRIER

OK

at+chup?

ERROR

8.2.25 AT+CMGD, Deleting SMS Messages

Example

at+mmgl

+MMGL: 004,001,,041

07917952140230F2040B917952545600F10000208080418245001965B339DD080147A492D7A432A152DF15DFDFEA71C10D

+MMGL: 005,001,,023

07917952140230F2040B917952545600F10000208011213182000465B3390D

+MMGL: 006,001,,009

0001FF00800000024122

+MMGL: 007,000,,023

07917952140230F2040B917952545600F100002080112151340004E131D90C

+MMGL: 008,002,,010

AT Command Response/Action Remarks

AT+CMGD=<index> [,<delflag>] Deletes SMS or group of SMSsOK+CME ERROR: <err>

<index> The location of the SMS in the memory.

<delflag>0 or omitted Delete message.1 Delete all messages,

except unread or stored messages.

2 Delete all messages, except unread or unsent messages.

3 Delete all messages, except unread messages.

4 Delete all messages.

AT+CMGD? +CME ERROR: <err>

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

Note

Delete SMS with ID=0 is not allowed.

Delete SMS with ID=75 is allowed.

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 therange of SMS storage memory (1–75), even though the message with this index might not exist.

98-08901C39-B 111

AT Commands

0001FF0080000003416213

OK

at+cmgd=6

OK

at+mmgl

+MMGL: 004,001,,041

07917952140230F2040B917952545600F10000208080418245001965B339DD080147A492D7A432A152DF15DFDFEA71C10D

+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

Example

at+cmgf?

+CMGF: 000

OK

at+cmgf=?

+CMGF: (000)

OK

at+cmgf=1

+CME ERROR: operation not allowed

AT Command Response/Action Remarks

at+cmgf= <mode> OK+CME ERROR: <err>

<mode> 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>

98-08901C39-B 113

AT Commands

8.2.27 AT+CMGL, Listing Messages

Example

at+cmgl=?

+CMGL: (000-004)

OK

at+cmgl?

ERROR

at+cmgl

+CMGL: 001,000,023

0791947122723033040B831027492204F000009930926145148004C2A2F308

OK.

AT Command Response/Action Remarks

at+cmgl[=<stat>] If PDU mode (+CMGF=0) and command successful:+CMGL: <index>,<stat>,[<alpha>],<length><CR><LF><pdu>[<CR><LF>+CMGL:<index>,<stat>,[<alpha>],<length><CR><LF><pdu>[...]]OK+CMS ERROR: <err>

<stat> 0 "REC UNREAD", received unread

message (for example, new message).

1 "REC READ", received read message.

2 "STO UNSENT", stored unsent message.

3 "STO SENT", stored sent message.

4 "ALL", all messages (default).

<index>

The value of the message location in the range of location numbers is supported by the associated memory.

<alpha>

Not supported.

at+cmgl? +CME ERROR: <err>

at+cmgl=? +CMGL: (list of supported <stat>s)OK+CME ERROR: <err>

Note

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

Wait for OK before sending new AT commands.

114 98-08901C39-B

AT Commands

8.2.28 AT+CMGR, Reading Messages

Example

at+cmgr=2

+CMGR: 001,,023

0791947122723033040B831027492204F000009930927190948004C2A2F308

OK

8.2.29 AT+CPAS, Phone Activity Status

Example

at+CPAS

+CPAS: 000

AT Command Response/Action Remarks

at+cmgr=<index> If PDU mode (+CMGF=0) and command are successful:+CMGR: <stat>,[<alpha>],<length><CR><LF><pdu>OK+CMS ERROR: <err>

<stat> 0 "REC UNREAD", received unread

message (for example, new message).

1 "REC READ", received read message.

2 "STO UNSENT", stored unsent message.

3 "STO SENT", stored sent message.

4 "ALL", all messages (default).

<index>

The value of the message location in the range of location numbers is supported by the associated memory.

<alpha>Not supported.

at+cmgr? +CME ERROR: <err>

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

AT Command Response/Action Remarks

AT+CPAS +CPAS: <pas> OK+CME ERROR: <err>

<pas>0 Ready1 Unavailable2 Unknown3 Ringing (MT calls)4 Call in progress5 Asleep

AT+CPAS? +CME ERROR: <err>

AT+CPAS=? +CPAS: (list of supported <pas>s)OK+CME ERROR: <err>

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

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

AT Command Response/Action Remarks

at+cpbr=<index> +CPBR: <index>,<number>,<type>,<text> OK+CME ERROR: <err>

<index> Location number in the storage

<number> Phone number in the <type> format

<type> 129 Local number145 International number with

access character +

<text> Name of the entry

<tlength> Maximum length of <text>

<nlength>Maximum length of <number>

at+cpbr? +CME ERROR: <err>

at+cpbr=? +CPBR: (list of supported <index>s),<nlength>,<tlength>OK+CME ERROR: <err>

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

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?

AT Command Response/Action Remarks

at+cpms=<mem1>[,<mem2>] +CPMS: <used1>,<total1>,<used2>,<total2>OK+CMS ERROR: <err>

<mem1> <mem2>“SM” Memory storage

<used> Used memory storage

<total> Total memory storage

at+cpms? +CPMS:<mem1>,<used1>,<total1>,<mem2>,<used2>,<total2>OK+CMS ERROR: <err>

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

98-08901C39-B 117

AT Commands

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

OK

8.2.32 AT+CSCA, Service Center Address

Example

at+csca?

+CMS ERROR: SMSC address unknown

at+csca=?

OK

at+csca=“491722270333”,145

OK

at+csca?

+CSCA: “+491722270333”,145

OK

AT Command Response/Action Remarks

at+csca=<sca>,<type> OK+CMS ERROR: <err>

<sca> Service center number + International, allowed at start

only0,9,*,# Digits and instruction/,-,(,blank,),A,B,C,D Allowed,

ignored, not saved

, Pause control; 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 +

at+csca? +CSCA: <sca>,<type>OK+CMS ERROR: <err>

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

118 98-08901C39-B

AT Commands

8.2.33 AT+CSCS, Selecting TE Character Set

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

AT Command Response/Action Remarks

at+cscs=<chset> OK+CME ERROR: <err>

<chset>GSM GSM alphabetIRA International alphabetUCS2 16-bit universal multiple-octet

coded character setat+cscs? +CSCS: <chest>

OK+CME ERROR: <err>

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

98-08901C39-B 119

AT Commands

8.2.34 AT+CSMS, Selecting the Message Service

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

AT Command Response/Action Remarks

at+csms=<service> +CSMS: <mt>, <mo>, <bm>OK+CMS ERROR: <err>

<service>0 GSM 03.40 and 03.41. The

syntax of SMS AT commands is compatible with GSM 07.05 Phase 2 version 4.7.0. Phase 2+ features that do not require new command syntax may be supported.

<mt>,< mo>,< bm>0 Type not supported1 Type supported<mt> Mobile terminated message<mo> Mobile originate message<bm> Broadcast type message

at+csms? +CSMS: <service>, <mt>, <mo>, <bm>OK+CMS ERROR: <err>

at+csms=? +CSMS: (list of supported <service>s)OK+CMS ERROR: <err>

120 98-08901C39-B

AT Commands

8.2.35 AT+CSQ, Signal Quality

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+CSQ +CSQ: <rssi>,<ber>OK+CME ERROR: <err>

<rssi>0 0 Bars < -108 dBm1 1 Bar -102 to -108 dBm10 2 Bars -93 to -101 dBm20 3 Bars -87 to -92 dBm30 4 Bars -77 to -86 dBm31 5 Bars > -76 dBm99 Unknown or not detectable

<ber> channel bit error rate (in percent)0–7 RXQUAL values in the GSM

05.08 table99 Unknown or not detectable

AT+CSQ? +CME ERROR: <err>

AT+CSQ=? +CSQ: (list of supported <rssi>s),(list of supported <ber>s)OK+CME ERROR: <err>

Note

BER information is not supported.

AT Command Response/Action Remarks

at+CEER +CEER: <report>OK+CME ERROR: <err>

<report>Refer to Table 18, “ETSI 07.07 Mobile Extended Error Report,” on page 50.

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

At+CEER? +CME ERROR: <err>

98-08901C39-B 121

AT Commands

Example

at+ceer=?

OK

at+ceer?

ERROR

at+ceer

+CEER: “No information available”

OK

Note

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

122 98-08901C39-B

AT Commands

8.2.37 AT+CKPD, Keypad Control

Example

at+ckpd=?

OK

at+ckpd=M

ERROR

at+ckpd=“M>>S”

OK

AT Command Response/Action Remarks

AT+CKPD=<Keys>[,<time>[,<pause>]] OK+CME ERROR: <err>

<Keys> # Hash (number sign) * Star (*) 09 Number keys: Escape character for

manufacturer specific keys; Escape character for string

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).

AT+CKPD? +CME ERROR: <err>

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

98-08901C39-B 123

AT Commands

8.2.38 AT+FCLASS, Selecting a Mode

Example

AT+FCLASS=?

0,1

OK

AT+FCLASS?

+FCLASS: 0

OK

8.2.39 AT+GCAP, Requesting Complete Capabilities List

Example

AT+GCAP

+GCAP: +FCLASS

OK

AT+GCAP=?

AT Command Response/Action Remarks

AT+FCLASS=<n> OKPuts the TA into a particular mode of operation. +CME ERROR: <err>

<n>0 Data1 Fax

AT+FCLASS? +FCLASS: <n>OK+CME ERROR: <err>

AT+FCLASS=? (list of supported <n>s)OK+CME ERROR: <err>

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>

124 98-08901C39-B

AT Commands

ERROR

AT+GCAP?

ERROR

8.2.40 AT+CMOD, Calling Mode

Example

AT+CMOD =?

+CMOD: (000, 001)

OK

AT+CMOD?

+CMOD: 000

OK

AT+CMOD=1

OK

AT Command Response/Action Remarks

AT+CMOD=[<mode>] OK+CME ERROR: <err>

<mode> 0 Single mode1 Alternating voice/fax

(teleservice 61)AT+CMOD? +CMOD: <mode>OK+CME ERROR: <err>

AT+CMOD=? +CMOD: (list of supported <mode>s)OK+CME ERROR: <err>

98-08901C39-B 125

AT Commands

8.2.41 AT+CRLP, Radio Link Protocol

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

+CRLP= [<iws>[,<mws>[,<T1>[,<N2>]]]]

OK+CME ERROR: <err>

<iws>, <mws>, <T1>, <N2>:

IWF to MS window size (default 61),

MS to IWF window size (default 61),

Acknowledgement timer T1 (default 48),Retransmission attempts N2 (default 6) in integer format (refer to GSM 04.22 [18] subclause 5.4.3)

+CRLP? +CRLP= <iws>,<mws>,<T1>,<N2>OK+CME ERROR: <err>

+CRLP=? +CRLP= (list of supported <iws>s), (list of supported <mws>s), (list of supported <T1>s), (list of supported <N2>s)OK+CME ERROR: <err>

AT Command Response/Action Remarks

AT+CR= [<mode>] OK+CME ERROR: <err>

<mode>0 Disables reporting1 Enables reporting

<serv>REL ASYNC Asynchronous

non-transparentREL SYNC Synchronous

non-transparent

AT+CR? +CR: <mode>OK+CME ERROR: <err>

AT+CR=? +CR: (list of supported<mode>s)OK+CME ERROR: <err>

Note

Set command controls whether or not intermediate result code +CR: <serv> is returned from the TA to the TE. Ifenabled, the intermediate result code is transmitted at the point during connect negotiation at which the TA hasdetermined which speed and quality of service will be used, before any error control or data compression reportsare 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

Example

AT+CRC?

+CRC:000

OK

AT+CRC=1

OK

AT+CRC=?

+CRC: (000,001)

AT Command Response/Action Remarks

AT+CRC= [<mode>] OK+CME ERROR: <err>

<mode> 0 Disables extended format1 Enables extended format<type>REL ASYNC Asynchronous

non-transparentFAX Facsimile (TS 62)VOICE Normal voice (TS 11)

AT+CRC? +CRC: <mode>OK+CME ERROR: <err>

AT+CRC=? +CRC: (list of supported <modes>s)OK+CME ERROR: <err>

Note

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

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>[,<ds>[,<bfr>]]]]]

OK+CMS ERROR: <err>

<mode> 0 Buffer unsolicited result codes in

the TA. If TA result code buffer is full, indications can be buffered elsewhere or the oldest indications may be discarded and replaced with the new received indications.

<mt>0 No SMS DELIVER indications are

routed to the TE route message to TE.

1 Indication of memory location is routed to the TE.

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).

AT+CNMI? +CNMI: <mode>,<mt>,<bm>,<ds>,<bfr>OK+CMS ERROR: <err>

AT+CNMI=? +CNMI: (list of supported <mode>s), (list of supported <mt>s), (list of supported <bm>s), (list of supported <ds>s), (list of supported <bfr>s)OK+CMS ERROR: <err>

Note

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

After automatically transferring a SMS/CBM message to the DTE (mt=2 and/or bm=2), the g18 waits for a +CNMAresponse from the DTE (within one minute). If DTE does not respond within this time, or if another message arrivesfrom 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 cellbroadcast 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 thedata 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

Example

AT+CMEC?

+CMEC: 02, 00, 00

OK

AT+CMEC=?

+CMEC: (00,02), (00), (00)

OK

AT+CMEC=2, 0, 0

OK

AT Command Response/Action Remarks

AT+CMEC= [<keyp>[,<disp>[,<ind>]]] OK+CME ERROR: <err>

<keyp> 0 ME can be operated only through

its keypad2 ME can be operated from both ME

keypad and TE

<disp>0 Only ME can write to its display

<ind>0 Only ME can set the status of its

indications

AT+CMEC? +CMEC: <keyp>,<disp>,<ind>OK+CME ERROR: <err>

AT+CMEC=? +CMEC: (list of supported <keyp>s), (list of supported <disp>s), (list of supported <ind>s)OK+CME ERROR: <err>

Note

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

130 98-08901C39-B

AT Commands

8.2.46 AT+CMER, Mobile Equipment Event Reporting

AT Command Response/Action Remarks

AT+CMER= [<mode>[,<keyp>[, <disp>[,<ind>[,<bfr>]]]]]

OK+CME ERROR: <err>

<mode>0 Buffer unsolicited result codes in

the TA. If TA result code buffer is full, codes can be buffered elsewhere or the oldest ones can be discarded.

<keyp>0 No keypad event reporting.

<disp>0 No display event reporting.1 Display event reporting +CDEV:

<Upper corner>, <text>, <Lower corner>.The display height is 54 pixels: 0–53.

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.

AT+CMER? +CMER: <mode>, <keyp>, <disp>, <ind>, <bfr>OK+CME ERROR: <err>

AT+CMER=? +CMER: (list of supported <mode>s), (list of supported <keyp>s), (list of supported <disp>s), (list of supported <ind>s), (list of supported <bfr>s)OK+CME ERROR: <err>

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>, <type>, <text>[<CR><LF>+CBPF: <index2>, <number>, <type>, <text>[..]]OK+CME ERROR: <err>

<index1>, <index2> 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

AT+CPBF? +CME ERROR: <err>

AT+CPBF=? +CPBF: <nlength>, <tlength>OK+CME ERROR: <err>

132 98-08901C39-B

AT Commands

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

Note

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

For example:

The name “RONEN” is in PB.

at+cpbf=“RON” +CPBF: 106, “054567432”, 129, “RONEN”

whereas,

at+cpbf=“ONE” Will yield no result

98-08901C39-B 133

AT Commands

8.2.48 AT+CESP, Entering SMS Block Mode

Example

at+cesp

OK

8.2.49 AT+CMGW, Writing Messages in PDU Mode

Example

at+cmgw=24

>07917952140230F2040B917952545630F200000070528141630005A060B10902

<ctrl/Z>

+CMGW: 001

AT Command Response/Action Remarks

at+cesp OK +CME ERROR: <err>

Sets the TA in SMS block protocol mode.

at+cesp? +CME ERROR: <err>

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

Note

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

AT Command Response/Action Remarks

(cmgf=0)at+cmgw=<length><CR>>PDU is given <ctrl-z/ESC>

Stores the SMS messageIf storage succeeds:+CMGW: <index>OKIf storage fails:+CMS: <err>

The message is terminated with control-Z character (0x1A)

The command is aborted with <esc>

<length>Number of octets coded in the TP

<cr>After terminating with<cr>, the PDU can be given from the TE

<crtl-z>Indicates the end of the PDU

<index>Index of stored messages

at+cmgw? +CME ERROR: <err>

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

134 98-08901C39-B

AT Commands

OK

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

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+CTFR1 OK+CME ERROR: <err>

If there is no waiting call in progress, returns error.

AT+CTFR1? +CME ERROR: <err>

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

AT Command Response/Action Remarks

AT+CNMA OK+CME ERROR: <err>

Must be sent within 60 seconds from the arrival of the message to the DTE. If not, the message will be stored on the SIM card and all the parameters of the CNMI command except <bm> will be set to zero.

AT+CNMA? +CME ERROR: <err>

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

Note

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

98-08901C39-B 135

AT Commands

8.2.52 AT+CBAND, Changing Band

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”

AT Command Response/Action Remarks

AT+CBAND = N OK+CME ERROR: <err>

Wait for power cycle to apply the change.<N>3 For 1900Mhz4 For 900/1800Mhz

AT+CBAND? +CBAND: <N>OK

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

136 98-08901C39-B

AT Commands

8.2.53 AT+CBAUD, Setting the Baud Rate

Example

at+cbaud=?

+CBAUD: (0–9,300,600,1200,2400,4800,9600,19200,38400,57600)

OK

at+cbaud?

+CBAUD: 57600

OK

AT Command Response/Action Remarks

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

OK+CME ERROR: <err>

<n> <rate>0 3001 6002 12003 24004 48005 96006 192007 384008 576009 Auto baud rate detection

AT+CBAUD? + CBAUD: <rate>OK+CME ERROR: <err>

AT+CBAUD=? +CBAUD: (list of supported <n>s, <rate>s)OK+CME ERROR: <err>

Note

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.

The g18 supports up to 57600 auto baud within the accuracy limitations of the application’s baud (g18 meets theRS232 specifications).

If you call MO CSD at 4800 bps (on the air), then do not use 57600 bps on your RS232 port.

98-08901C39-B 137

AT Commands

8.2.54 AT+CGPRS, GPRS Coverage

Example

AT+CGPRS

+CGPRS: 0

OK

AT+CGPRS?

+CGPRS: 0

OK

AT+CGPRS=1

+CME ERROR: “operation not allowed”

AT Command Response/Action Remarks

AT+CGPRS +CGPRS: <mode>OK+CME ERROR: <err>

<mode>0 No GPRS coverage1 GPRS coverage

AT+CGPRS? +CGPRS: <mode>OK+CME ERROR: <err>

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

Note

This command without an attachment will always return zero.

138 98-08901C39-B

AT Commands

8.2.55 AT+CGPADDR, Showing the PDP Address

Example

AT+CGPADDR=?

+CGPADDR: (1,2,3)

OK

at+cgpaddr=1

+CGPADDR: 1, 0.0.0.0

OK

AT Command Response/Action Remarks

AT+CGPADDR=[<cid> [,<cid> [,]]]

+CGPADDR: <cid>,<PDP_addr>[<CR><LF>+CGPADDR: <cid>,<PDP_addr>[...]]OK+CME ERROR: <err>

<cid>A numeric parameter that specifies a particular PDP context definition.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>

Note

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

98-08901C39-B 139

AT Commands

8.2.56 AT+CGCLASS, GPRS MS Class

Example

AT+CGCLASS=?

+CGCLASS: (B)

OK

AT+CGCLASS=“B”

OK

AT+CGCLASS=“A”

ERROR

AT Command Response/Action Remarks

AT+CGCLASS= [<class>] OK+CME ERROR: <err>

<class>String parameter that indicates the GPRS mobile classB Class BAT +CGCLASS? +CGCLASS: <class>

OK+CME ERROR: <err>

AT +CGCLASS=? +CGCLASS: (list of supported <class>s)OK+CME ERROR: <err>

140 98-08901C39-B

AT Commands

8.2.57 AT+CGDCONT, Defining the PDP Context

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

AT Command Response/Action Remarks

+CGDCONT=[<cid> [,<PDP_type> [,<APN> [,<PDP_addr> [,<d_comp> [,<h_comp> [,<pd1> [,[,pdN]]]]]]]]]

OK+CME ERROR: <err>

<cid>A numeric parameter that specifies a particular PDP context definition.

<PDP_type>IP Internet Protocol

<d_comp> Data compression0 Off (default)1 On<h_comp> Header

compression0 Off (default)1 On

AT+CGDCONT? +CGDCONT: <cid>, <PDP_type>,<APN>,<PDP_addr>, <data_comp>,<head_comp>[,<pd1>[,[,pdN]]][<CR><LF>+CGDCONT: <cid>, <PDP_type>,<APN>,<PDP_addr>, <data_comp>,<head_comp>[,<pd1>[,[,pdN]]][...]]OK+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>

Note

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

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

Example

AT+CGQMIN=?

+CGQMIN: (1-3),(0-3),(0-4),(0-5),(0-9),(0-18,31)

OK

AT Command Response/Action Remarks

AT+CGQMIN=[<cid> [,<precedence> [,<delay> [,<reliability.> [,<peak> [,<mean>]]]]]]

OK+CME ERROR: <err>

<cid> A numeric parameter that specifies a particular PDP context definition.

<precedence> A numeric parameter that specifies the precedence class.

<delay> A numeric parameter that specifies the delay class.

<reliability> 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.

AT+CGQMIN? +CGQMIN: <cid>, <precedence >, <delay>,<reliability>, <peak>, <mean>[<CR><LF>+CGQMIN: <cid>, <precedence >,<delay>, <reliability.>, <peak>, <mean>[...]]OK+CME ERROR: <err>

AT+CGQMIN=? +CGQMIN: <PDP_type>, (list of supported<precedence>s), (list of supported<delay>s), (list of supported<reliability>s), (list of supported<peak>s), (list of supported <mean>s)[<CR><LF>+CGQMIN: <PDP_type>, (list ofsupported <precedence>s), (list ofsupported <delay>s), (list of supported<reliability>s), (list of supported<peak>s), (list of supported <mean>s)OK+CME ERROR: <err>

Note

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

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

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.

AT Command Response/Action Remarks

AT+CGACT=[<state> [,<cid>[,<cid>[,]]]]

OK+CME ERROR: <err>

<state>: Indicates the state of GPRS attachment.0 Detached. 1 Attached.

<cid> A numeric parameter that specifies a particular PDP context definition.

AT+CGACT? +CGACT: <cid>, <state>[<CR><LF>+CGACT: <cid>, <state>OK+CME ERROR: <err>

AT+CGACT=? +CGACT: (list of supported <state>s)OK+CME ERROR: <err>

Note

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

98-08901C39-B 143

AT Commands

8.2.60 AT+CGATT, GPRS Attach/Detach Request

Example

AT+CGATT=?

+CGATT: (0, 1)

OK

AT+CGATT?

+CGATT: 0

OK

AT+CGATT=1

ERROR

AT+CGATT=0

OK

AT Command Response/Action Remarks

AT+CGATT= [<state>] OK+CME ERROR: <err>

<state>Indicates the state of the GPRS attachment:0 Detached.1 Attached.If no <state> is given, the default state is the current state and nothing needs to be done.

AT+CGATT? +CGATT: <state>OK+CME ERROR: <err>

AT+CGATT=? +CGATT: (list of supported <state>s)OK+CME ERROR: <err>

144 98-08901C39-B

AT Commands

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

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,10OK

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

AT Command Response/Action Remarks

AT+CGQREQ=[<cid> [,<precedence> [,<delay>[,<reliability.> [,<peak> [,<mean>]]]]]]

OK+CME ERROR: <err>

<cid>A numeric parameter that specifies a particular PDP context definition.

<precedence> A numeric parameter that specifies the precedence class.

<delay> A numeric parameter that specifies the delay class.

<reliability> 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.

AT+CGQREQ? +CGQREQ: <cid>, <precedence >, <delay>,<reliability>, <peak>, <mean>OK+CME ERROR: <err>

AT+CGQREQ=? +CGQREQ: <PDP_type>, (list of supported<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>

98-08901C39-B 145

AT Commands

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

Example

AT+CIMI=?

OK

AT+CIMI

+CIMI: 425010100420457

OK

AT Command Response/Action Remarks

AT+CIMI +CIMI: <IMSI>OK+CME ERROR: <err>

<IMSI>International Mobile Subscriber Identity (string without double quotes)

AT+CIMI? +CME ERROR: <err>

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

146 98-08901C39-B

AT Commands

8.2.63 AT+CRSM, Restricting SIM Access

Example

AT+CRSM=?

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

CRSM: 0,0,FFFFFFFFFFFFFFFFFF00 0000000000000000

OK

AT Command Response/Action Remarks

AT+CRSM=<command>,<fileid> +CRSM: <sw1>,<sw2>[,<response>]OK+CME ERROR: <err>

<command>Only command 176 is supported.

<fileid>1 Flex-ID2 Factory Info #13 Factory Info #2197 IMSI214 GID1242 ICC ID243 GID2

<sw1>, <sw2>:Reason0 0 Success0 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.

AT+CRSM? +CME ERROR: <err>

AT+CRSM=? +CRSM: (list of supported <command>s),(list of supported <fileid>s)OK+CME ERROR: <err>

98-08901C39-B 147

AT Commands

8.2.64 AT+CPOL, Preferred Operator List

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

AT Command Response/Action Remarks

AT+CPOL=[<index>][,<format>[,<oper>]]

OK+CME ERROR: <err>

<index>Integer type; the order number of the operator in the SIM preferred operator list

<format> of <oper>0 Long format alphanumeric 1 Short format alphanumeric 2 Numeric

<oper> String type; <format> indicates whether the format is alphanumeric or numeric

AT+CPOL? +CPOL: <index1>,<format>,<oper1>[<CR><LF>+CPOL: <index2>,<format>,<oper2>[...]]OK+CME ERROR: <err>

AT+CPOL=? +CPOL: (list of supported <index>es),(list of supported <format>s)OK+CME ERROR: <err>

148 98-08901C39-B

AT Commands

8.2.65 AT+CIPE, ENABLE +CIP AT Command

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

Example

at+cip=8,a842,0020,00010001

AT Command Response/Action Remarks

AT+CIPE=<mode> OK+CME ERROR: <err>

<mode>0 Disable +CIP command1 Enable +CIP command

AT+CIPE? +CIPE: <mode>OK+CME ERROR: <err>

AT+CIPE=? +CIPE: <list of supported modes>OK+CME ERROR: <err>

AT Command Response/Action Remarks

AT+CIP=<Data length> ,<Prim_Id>,<Sub_addr>,<Data>

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

OK

+CME ERROR: <err>

Data length(characters) In decimalPrim_Id In hex (2 bytes)Sub_addr(Destination) In hex (2 bytes)Data In hexNote: 2 characters in 1 byte

AT+CIP? +CME ERROR: <err>

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

98-08901C39-B 149

AT Commands

+CIP: 38,a844,0001093033353638343133318105726F6E6974

OK

8.2.67 AT+CRTT, Selecting the Ring Tone

Example

AT+CRTT=?

+CRTT: (0–10), (0–1)

OK

AT+CRTT=4, 1

OK

AT+CRTT?

+CRTT: 4

OK

AT Command Response/Action Remarks

AT+CRTT= <RingTypeNumber>,<operation>

OK+CME ERROR: <err>

<RingTypeNumber> 0 Standard 1 British 2 French 3 German 4 Bravo 5 3 Tone 6 Siren 7 Quick 8 1 Ring 9 High 10 Music

<operation>0 Play1 Set

AT+CRTT? +CRTT: <RingTypeNumber>OK+CME ERROR: <err>

AT+CRTT=? +CRTT: (<list of supported <RingTypeNumber>s), (<list of supported <operation>s)OK

+CME ERROR: <err>

150 98-08901C39-B

AT Commands

8.2.68 AT+CPWD, Changing the Password

8.2.69 Fax AT Commands

AT Command Response/Action Remarks

AT+CPWD=<fac>,<oldpwd>,<newpwd>

OK+CME ERROR: <err>

<fac> string type; facility (upper/lower case acceptable)

CS Control surface (keypad)SC SIM cardAO Block all outgoing callsOI Block outgoing international

callsOX Block outgoing international

calls except to home countryAI Block all incoming callsIR Block incoming calls when roaming

outside home countryAB All blocking servicesAG All outgoing blocking servicesAC All Incoming blocking servicesFD 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.

AT+CPWD? +CME ERROR: <err>

AT+CPWD=? +CPWD: list of supported (<fac>,<pwdlength>s)OK+CME ERROR: <err>

AT Command Function Remarks

AT+FCLASS Select mode 0 Data1 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

8.2.70 AT+MTDTR, DTR Line Test Command

8.2.71 AT+MTCTS, CTS Line Test Command

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

AT Command Response/Action Remarks

AT+MTDTR +MTDTR: <n>OK+CME ERROR: <err>

<n>1 DTR is active 0 DTR is not active

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

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

Note

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

AT Command Response/Action Remarks

AT+MTCTS OK+CME ERROR: <err>

Deactivates CTS. Wait approximately 1 second and then activate CTS.

AT+MTCTS? +CME ERROR: <err>

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

AT Command Function Remarks

152 98-08901C39-B

AT Commands

8.2.72 AT+MCWAKE, DTE Wake Line Control Command

8.2.73 AT+CMSS, Send Message from Storage

Example

AT+CMSS=1, “054511511”

+CMSS: 002

AT Command Response/Action Remarks

AT+MCWAKE= <mode> OK+CME ERROR: <err>

<mode>0 Send no indication1 Send indication when GPRS

coverage goes off 2 Send indication when GPRS

coverage goes on (default)

AT+MCWAKE=? +MCWAKE: (list of supported <mode>s)OK+CME ERROR: <err>

AT+MCWAKE? +MCWAKE: <Mode>OK+CME ERROR: <err>

AT Command Response/Action Remarks

AT+CMSS=<index>[,<da>[,<toda>]] If PDU mode (+CMGF=0) and send are successful:+CMSS: <mr>OKIf send fails:+CMS ERROR: <err>

<mr> Message reference<da> Destination address<toda> Type of destination address

129145

AT+CMSS? +CME ERROR: <err>

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

98-08901C39-B 153

AT Commands

8.2.74 AT+MMGL, Message List

8.2.75 AT+MMGR, Read Message

AT Command Response/Action Remarks

AT+MMGL[=<stat>] If PDU mode (+CMGF=0) and command are successful:+MMGL: <index>,<stat>,[<alpha>],<length><CR><LF><pdu>[<CR><LF>+MMGL:<index>,<stat>,[<alpha>],<length><CR><LF><pdu>[...]]OKIf not:+CMS ERROR: <err>

<stat>0 “REC UNREAD”, received

unread message1 “REC READ”, received read

message2 “STO UNSENT”, stored unsent

message3 “STO SENT”, stored sent

message4 “ALL”, all messages (default)

AT+MMGL? +CMS ERROR: <err>

AT+MMGL=? +MMGL: (list of supported <stat>s)OK+CME ERROR: <err>

Note

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

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

AT Command Response/Action Remarks

AT+MMGR=<index> If PDU mode (+CMGF=0) and command are successful:+MMGR: <stat>,[<alpha>],<length><CR><LF><pdu>OKIf not:+CMS ERROR: <err>

<stat> 0 "REC UNREAD", received unread

message (for example, new message).

1 "REC READ", received read message.

2 "STO UNSENT", stored unsent message.

3 "STO SENT", stored sent message. 4 "ALL", all messages (default).

<index>

Value of message location in the range of location numbers, supported by the associated memory.

<alpha>Not supported.

AT+MMGR? +CME ERROR: <err>

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

154 98-08901C39-B

AT Commands

8.2.76 AT+MMGA, Changing the Message Attributes

8.2.77 AT+MSCTS, Motorola Sleep CTS Control

Note

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

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

AT Command Response/Action Remarks

AT+MMGA = <index>, <attribute> OK +CME ERROR: <err>

<index>An integer between 1 and 75

<attribute>0 <received-unread>1 <received-read>

AT+MMGA? +CME ERROR: <err>

AT+MMGA =? +MMGA: (001 – 075), (000-001)OK+CME ERROR: <err>

Note

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:MMGR & MMGL that return the message without changing its attribute from received-unread to received-read, thisset command can be used to change the specific message attribute from received-unread to received-read andvice versa.

The test command returns the entire available <index>es and <attribute>s supported by this command.

AT Command Response/Action Remarks

AT+MSCTS=<control> OK+CME ERROR: <err>

<control>0 Default. Ignores the wakeup

line state.1 When g18 is awakened and the

DTE wakeup line is high, CTS will not be activated.

AT+MSCTS? +MSCTS: <control>OK+CME ERROR: <err>

AT+MSCTS=? +MSCTS: (list of supported <control>s)OK+CME ERROR: <err>

Note

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

When sending data, use the wakeup line, either pin #15 at the FC 36 pin, or pin #10 at the DIN 28 pin, to awakenthe g18.

This command is supported in software versions E6.13.24 and above.

98-08901C39-B 155

AT Commands

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

!Warning

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

Using At+MSCTS=1 will deactivate the CTS after g18 has entered sleep mode, and the DTE will be unableto 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.

156 98-08901C39-B

AT Commands

8.2.78 AT+CSMP, Set SMS SIM Parameters

Example

at+csmp=?

OK

at+csmp?

+CSMP: 17,119,0,0

OK

AT Command Response/Action Remarks

AT+CSMP=[<fo>[,<vp>[,<pid>[,<dcs>]]]]

OK+CME ERROR: <err>

<fo> First OctetDefault, and after power up = 17This parameter is saved on the g18 NVM.

<vp> Validity PeriodUses a relative formatRange: 0 – 225Default value = 167000 – 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 day197 – 255: (<vp> - 192) x 1 weekThis parameter is saved on SIM.

<pid> Protocol IdentifierRange: 0 – 225Default value = 0Support values:0 Text34 Fax36 Voice37 ERMES38 Paging49 X40050 eMailThis parameter is saved on SIM.

<dcs> Data Coding SchemeDefault, and after power up = 0. This parameter is ignored, not verified, and stored in the g18 NVM.

AT+CSMP? +CSMP: <fo>,<vp>,<pid>,<dcs>OK+CME ERROR: <err>

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

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

Example

at+csvm=?

+CSVM: (0,1),(129,145)

OK

at+csvm?

+CSVM: 1,"*155",129

OK

at+csvm=0 // Number cleared from eeprom

OK

AT Command Response/Action Remarks

AT+ CSVM= <mode>[,<number>[,<type>]]

Sets or clears the voicemail number in the EEPROM or SIM, depending on the type of SIM card.OK+CME ERROR: <err>

<mode>0 Disable. Clears the number in

the EEprom.1 Enable. Must be followed by a

number.

<number> String format up to 35 characters+ International, allowed at start

only.0,9,*,# Digits and instruction/,-,(,blank,),A,B,C,D Allowed,

ignored, not saved

, Pause control.; Allowed at end of number.

May be omitted or ignored, but not saved.

<type> Type of number

Range: 0 – 255129 International or unknown

international 145 International numberIf <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.

AT+ CSVM? For mode=1:+CSVM:1, <number>, <type>OKFor mode=0:+CSVM: 0 OK+CME ERROR: <err>

AT+ CSVM=? +CSVM: (list of supported mode>s), (list of supported <type>s)OK+CME ERROR: <err>

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

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?

AT Command Response/Action Remarks

AT+MFS = <freq>[,<mode>] OK+CME ERROR: <err>

<freq> Frequency of Search0 Continous1 Medium2 Slow3 Fast

<mode> Search mode0 Automatic1 Manual

AT+MFS? +MFS: <freq>,<mode>OK+CME ERROR: <err>

AT+MFS=? +MFS:(list of supported <freq>s), (list of supported <mode>s)OK+CME ERROR: <err>

Note

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

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 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>

<mode>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–65354String type: Default is an empty string

<dcss>Data Coding Scheme: 0–255String 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

Note

+CSCB Parameters:

• The default value for missing <mode> is 0.

• 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 toTCU, 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 theaccumulated 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 errorwill 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 samenumber 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

Note

Cell Broadcast Support in g18:

• The g18 allows selection of the SMS service for cell broadcast. The AT command for selecting the service is:

• +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 theDTE 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 anindividual 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. Thepage could be a duplicate, or unorganized and multiplexed with other pages. TCU should reconstructmessages and remove duplicates. These messages should be shown to the user only after a successfulbuild.

• 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 notempty 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

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

Note

Incoming Cell Broadcast Messages:

In releases up to E6.11.23, the handset is set to receive accumulated messages. This means that if the messageexceeds 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 intendedmessage is sent.

Using AT+CSCB, DTE is set to receive page-by-page messages, meaning that a message with several pages isreported to DTE page by page.

There will be two behavior methods: One that keeps the previous release’s behavior (backward compatible), andanother 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 ofAT 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 isdone 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 notreceive 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.

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 SMS alert tone for all arriving messages, or for some messages, as defined in <dcs mask>.OK+CME ERROR: <err>

<mode>0 Suppress alert tone1 Enable alert tone (default)2 Exercise alert tone

<dcs mask>SMS Data Coding Scheme mask, which either suppresses or activates the alert tone.AT+MCSAT? +MCSAT:

<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

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

Note

This command suppresses the SMS alert tone for a specific SMS type whenever the SMS alert tone is generated(receiving, storing or sending SMS).

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 (asciicharacter):

• 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.

98-08901C39-B 167

AT Commands

8.2.83 AT+MECC, Motorola Extended Characters Check

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 WindowsHyper Terminal.

OK

at+cpbf=“ ”

+CPBF: 001, “030303”, 129, “abc”

AT Command Response/Action Remarks

AT+MECC =<mode> Enables or disables standard checking of ASCII characters with values less than 32 on parsing AT commands.OK+CME ERROR: <err>

<mode> checking mode0 Disable standard checking, or

do not eliminate ASCII characters with values less than 32.

1 Enable standard checking (default).

Returns the supported modes.AT+MECC? +MECC: <mode>OK+CME ERROR: <err>

AT+MECC=? +MECC: (list of supported <mode>s)OK+CME ERROR: <err>

Note

This command prevents the standard check of ASCII characters, and allows all characters to be entered in thephone book, for example @. Indications that are affected by this command are: +CCWA, +CLCC, +CLIP.

168 98-08901C39-B

AT Commands

+CPBF: 002, “0303030”, 129, “abc” // The “Ω” character can be seen on the handset display, but not in Windows HyperTerminal.

OK

8.2.84 AT+CSCR, SIM Card Reader

Example

at+cscr=?

ERROR

at+cscr?

+CSCR: 2 // Internal sim card.

8.2.85 AT+MCELL, Motorola Cell Description

AT Command Response/Action Remarks

AT+CSCR +CME ERROR: <err> <sim_type>1 External SIM card2 Internal SIM cardAT+CSCR? +CSCR: <sim_type>

OK+CME ERROR: <err>

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

Note

This command tells which SIM card reader is being used, either the internal one on the g18 board, or an externalcard reader via the DSC bus.

AT Command Response/Action Remarks

+MCELL = <mode>, <screen_num> +MCELL: <screen_num> <screen_info>

OK

+CME ERROR: <err>

<mode>0 One shot requested

<screen_num>An integer number between 1-20

<screen_info>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

* N1—N6 information concerning Neighbor Cell 1—6 appears on screens 5—10 respectively.

** When the information is not available, an * is displayed instead.

Item Description Screen

Main Cell mcc

Mobile Country Code. Screen 1, position 19-21

Main Cell mnc

Mobile Network Code. Screen 1, position 22-24

Main Cell lac

Location Area Code. Screen 1, position 58-62

Main Cell bsic

Base Station Identity Code. Screen 1, position 11-12

Main Cell BCCH Freq (absolute)

Basic Control Channel. Screen 1, 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 the serving cell.

Screen 1 in dedicate mode, position 35-39

Main Cell RxLev Sub Signal strength of the active dedicated channel.

Screen 1 in dedicate mode, position 51-55

Main Cell RxQual Full Received signal quality in the base channel (carrying the BCCH).

Screen 1 in dedicate mode, position 41-42

Main Cell RxQual Sub Received signal quality in the dedicated active channel.

Screen 1 in dedicate mode, position 57-58

Neighbor Cell bsic

Base Station Identity Code. Screen *, position 11-12

Neighbor Cell BCCH Freq

Basic Control Channel. Screen *, position 6-9

Timing Advance Timing Advance quarter of bits. Screen 1 in dedicate mode, position 45-49

170 98-08901C39-B

AT Commands

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

Note

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.

Read command returns OK.

Test command returns the whole <mode> and <screen> options, supported by this command.

AT Command Response/Action Remarks

AT+IPR = [<baud_rate>]ORAT+IPR = [n]

OK+CME ERROR: <err>

<n> <baud_rate>0 3001 6002 12003 24004 48005 96006 192007 384008 576009 Auto baud rate detection

AT+IPR? +IPR: <baud_rate>OK+CME ERROR: <err>

AT+IPR=? +IPR: (list of supported <n>s, <baud_rate>s)OK+CME ERROR: <err>

98-08901C39-B 171

AT Commands

8.2.87 AT+PT42

8.2.88 AT+CMUX, Multiplexing Mode

Note

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. Theentered 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 orits 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 are4-8, 9 or 4800, 9600, 19200, 38400, 57600. Value represents 4800 to 57600. Value 9 represents auto baud ratedetection.

AT+IPR is similar to AT+CBAUD with the ability to save.

AT Command Response/Action Remarks

AT+PT42 OK+CME ERROR: <err>

AT+PT42? +CME ERROR: <err>

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

Note

This command disables echo suppression and echo cancellation processing in normal mode untilthe MS is turned off, which affects the handset screen. Registration starts when the command iscompleted.

AT Command Response/Action Remarks

AT+CMUX=0 OKor+CME ERROR: “Operation not allowed”

When sending the command outside the MuxWhen sending the command from the Mux

AT+CMUX? +CMUX:0,0,1,31,10,3,30,10,2,0,1,0,0or+CME ERROR: “Operation not allowed”

When sending the command from the MuxWhen sending the command outside the Mux

AT+CMUX=? +MECC: (0)

172 98-08901C39-B

98-08901C39-B

9. g18 EVALUATION BOARD

9.1 GENERALThe EV board is designed to be a tool used to operate the g18and to provide an example of the different drivers/connections available. It also provides an idea of how towork with the g18 in different situations.

Two versions of the EV board have been released, Issue P4and Issue P5. These boards have the same functionality,however the Issue P5 board contains an additional D-subconnector for GPS connectivity.

Additional information regarding the evaluation boards canbe found in “Schematic Diagrams, Layouts and Parts Lists”.

9.2 EV BOARD ISSUE P4To view the connectivity options, refer to Figures 44 and 45.

Note

The EV boards can be used as a test tool for thed10, d15 and g18. The g18 requires a retrofit kit(FTN8105A) in order to make the LEDs operatein 3V logic (d10/d15 operate in 5V logic).

10 Indicator LEDs

DB-9 RS-232 J5

36 Pin ZIF J121

30 Pin ZIF J4

ON/OFF ToggleSW2HeadsetJ118

SpeakerJ111

MicrophoneJ122

Handset andHands FreeCircuits

30 PinZIFJ12

Capacitor

Fuses 2.5 AMPFast Blow

Board ON/OFFS2

15 Pin Butt ConnectorJ2 J1

12 Pin Butt ConnectorJ13

RJ-45 (Handset)J110 J115

SMA ConnectorJ124

GPS J127

28 Pin DINAntenna Contact

28 Pin DIN

Test PointsJ114

OnBoardSIM S1

Ex SIM Connector36 Pin ZIFJ120

Soft GSM

GPS Select

Hands Free

IRDA EN

GPS Ant Power

MuteTS

LED EN

GNDIRDA

Ground

Vcc 3 to 6 Vdc

12Vdc forHF only

ConnectorHorizontal J126

ConnectorVertical J125

173

g18 Evaluation Board

Figure 44. EV Board P4 - Front

Figure 45. EV Board P4 - Back

9.2.1 Connector Description

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 RS232connector 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 thed15/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-freeapplications.

J122 - MIC Connector: Used for hands-free applications.

J3 - Power Inputs:

• 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 standardaccessories (for example, EMMI, charger for power input,and so on.)

J10, J115 - Handset Connectors: Used to connect thehandset and/or the remote SIM card reader.

J124 - Internal Antenna Connector: SMA connection forantenna.

J120: Connection to the d15/g18 under test - 36 pin. This isa 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.

Ex Sim ConnectorS1 On

12Vdcfor HF only

Vcc 3 to6 Vdc

GroundAudio Drivers

15 Pin Butt ConnectorJ1 J2

12 Pin Butt ConnectorJ13

RJ-45 (Handset)J110 J115

Fuses

Fast Blow

Board ON/OFFS2

2.5 AMP

DB-9 RS-232 J5

36 Pin ZIF J229

HeadsetJ118SpeakerJ111MicrophoneJ122

Board SimIndicator LEDs

SMA ConnectorJ124

AntennaContact

!Caution

Misalignment of the 28 pin DIN connector whileinserting it into the EV board or host device maycause irreversible damage to the d15/g18.

174 98-08901C39-B

g18 Evaluation Board

J126: d15/g18 DIN horizontal connector for unit under test- 28 pin.

S1: SIM connector.

Figure 46. SIM Card Interface

SIM: Additional SIM connectors for extended SIM sockets.

J127: GPS connector for Motorola M12 GPS module.

J114: Test points of the main functions from the d15 userconnector.

9.2.2 Jumper Description

TS Used to turn on the unit whenever power issupplied.

Led EN Enables the LED operation.

GND Ground pins.

IrDA Future option, which is not currentlyavailable.

Mute Test point used for hands-free operations,which is an input to mute the audio.

Pin Description1 Gnd2 SIM_PD3 SIM_CLK4 *SIM_RST5 SIM VCC6 SIM_I_O7 SIM VPP8 Gnd

Table 30. SIM Card Pin Functions

Pin Function

1 SIMPD

2 SIM VCC

3 *SIM_RST

4 DGND

5 N.C.

6 DGND

7 SIMCLK

8 DGND

9 N.C.

10 N.C.

Table 31. J114 Functions

Pin Function

1 CTS

2 TXD

3 DCD

4 DSR

5 RXD

6 RTS

7 SIM I_O

8 DTR

9 SIM_PD

10 SIM VCC

11 RI

12 SIM CLK

13 DCS_EN

14 DSC Downlink

15 DSC Uplink

16 2.7V for Audio Circuits

98-08901C39-B 175

g18 Evaluation Board

SoftGsm When the jumper is connected to the d15, itswitches to SoftGsm mode. In the g18, thisjumper should be always open.

GPS ant Pwr: Future option, which will connect the powerto a GPS mounted in the EV board.

HF: Jumper not in use. HF selection must beperformed using the software.

GPS select Future option, which will connect the GPS tothe RS232 output.

9.3 EV BOARD ISSUE P5To view the connectivity options, refer to Figures 47 and 48, below.

Figure 47. EV Board P5 - Front

DB-9 RS-232 J5

36 Pin ZIF J129

30 Pin ZIF J4

ON/OFF ToggleSW2HeadsetJ118

SpeakerJ111

MicrophoneJ122

Handset andHands FreeCircuits

30 PinZIFJ12

CapacitorFuses 2.5 AMPFast Blow

Board ON/OFFS2

15 Pin Butt ConnectorJ2 J1

12 Pin Butt ConnectorJ13

RJ-45 (Handset)J110 J115

SMA ConnectorJ124

GPS J9

28 Pin DINAntenna Contact

28 Pin DIN

10 Indicator LEDs36 Pin ZIFJ128

P6

Test PointsP11

DipSwitchS3

OnBoardSIM S1

P10

DB 9 GPS J9

Ex SIM ConnectorConnectorVertical J125

ConnectorHorizontal J126

GroundVcc 3 to 6 Vdc

12Vdc forHF only

176 98-08901C39-B

g18 Evaluation Board

Figure 48. EV Board P5 - Back

9.3.1 Connector Description

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.

J9 - GPS Connector for Debugging:• This connector has the GPS TXD and RXD lines in

RS232 levels.• GPS 1pps and RTCM lines are routed directly to the g18

user connector.

J4 - d15/g18 Output: Connection to the host device.

J129 - g18 Output: Connection to the host device.

SW2 - On/Off Button: Push button switch connected to theg18/d15 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-freeapplications.

J122 - MIC Connector: Used for hands-free applications.

J3 - Power Inputs:• 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 standardaccessories (for example, EMMI, charger for power input,and so on.)

J10, J115 – Handset Connectors: Used to connect thehandset and/or remote SIM card reader.

J124 – Internal Antenna Connector: SMA connector foran antenna.

J128: Connection to the g18 under test - 36 pin. This is amirror image connector to the g18.

J12: Connection to the d15/g18 under test - 30 pin.

J125: g18 DIN Vertical connector under test - 28 pin.

J126: g18 DIN horizontal connector under test - 28 pin.

S1: SIM connector. See Figure 46 for connector details.

Vcc 3 to6 Vdc

12Vdc

Indicator LEDsS1OnBoardSIM

DB 9 GPS J9

DB-9 RS-232 J5

36 Pin ZIF J229

HeadsetJ118SpeakerJ111MicrophoneJ122

Audio DriversBoard ON/OFFS2

15 Pin Butt ConnectorJ1 J2

12 Pin Butt ConnectorJ13

RJ-45 (Handset)J110 J115

SMA ConnectorJ124

Fuses 2.5 AMPFast Blow

AntennaContact

for HF only

Ground

98-08901C39-B 177

g18 Evaluation Board

SIM: Additional SIM connectors for extended SIM sockets.

J127: GPS connector for Motorola M12 GPS module.

P6 GND: Ground pins.

P10 GPS ant Pwr: Future option, which will connect powerto a GPS mounted in the EV board.

P11: Test points of main functions from the g18 userconnector.

Table 32. SIM Card Pin Functions

Pin Function

1 SIMPD

2 SIM VCC

3 *SIM_RST

4 DGND

5 N.C.

6 DGND

7 SIM_CLK

8 DGND

9 N.C.

10 N.C.

Table 33. P11 Functions

Pin Function

1 CTS

2 TXD (input to g18)

3 DCD

4 DSR

5 RXD (Output from g18)

6 RTS

7 SIM I_O

8 DTR

9 SIM_PD

10 SIM VCC

11 RI

12 SIM CLK

13 DCS_EN

14 DSC Downlink

15 DSC Uplink

16 2.7V for audio circuits

17 GPS - RTCM

18 GPS 1PPS

19 TX_EN

20 HF Mute input (for customer application)

21 GPS TXD (output from g18)

22 GPS RXD (input to g18)

Table 33. P11 Functions (Continued)

Pin Function

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 HFwhen a call is active, and mute it if there isno active call. When S3-1 is open, the HFaudio channel is always active.

S3-2 Led EN: Enables the LED operation.

S3-3 SoftGsm: When the dip switch is closed, the d15switches to SoftGsm mode. In the g18, thisdip switch should always be open.

S3-4 TS: Used to turn on the unit whenever power issupplied.

98-08901C39-B 179

g18 Evaluation Board

180 98-08901C39-B

98-08901C39-B

10. g18 PC LOADER APPLICATION

10.1GENERALThe g18 PC Loader Application is a tool that downloads newprogram codes into g18 via RS232.

Configuration Requirements:

• PC with 16 MB of RAM, available serial port supportingTX, RX, RTS, CTS, and Windows 2000 or NT.

• g18 software version E6.02.10 and above.• g18 connected to the PC communication port either

through the EV board or through the externalcommunication port on the host device.

10.2APPLICATION OPTIONS

10.2.1 Setting

The Setting tab, shown below, enables you to specify theapplication parameters that are used in the programmingprocedure.

Figure 50. Setting Page

The PCLoader.exe application must be run from thedirectory 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.

Note

Contact GSM Support atBSH015@email.mot.com, or your accountmanager for the CP software and PC Loaderapplication and specify the required languagepack as all CP software and PC Loader files areprovided in one zipped file.

181

g18 PC Loader Application

Baud Rate The active baud rate of the interface between the g18 and the PC on RS232. This is used as the initial handshake between them.

Maximal Baud Rate The maximum baud rate value that will be used after the initial 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 51. Applying Pop-up Approval Message

Set default Sets the default application parameters specified in the Setting tab.

Figure 52. Set Default Pop-up Approval Message

Note

The specified port name must be between COM1 – COM9.

The Baud Rate value can be 9600, 19200,38400, 57600 or 115200.

182 98-08901C39-B

g18 PC Loader Application

10.2.2 Programming

10.2.2.1 Warnings and RulesBefore pressing Start in the Programming tab, the user mustcheck that the following conditions have been met:• The g18 is connected to the PC serial port.• The g18 is powered on.• The g18 baud rate is the same as set in the Setting tab.The PC Loader application must not be interrupted while itis flashing the g18. Any interrupt such as, disconnecting theg18, powering off the g18, or powering off the PC, willdamage the g18.

During the programming process, the application retrievesdata from the flash.hex file (image file) and transfers it to theg18.

The Programming tab, shown below, enables you to specifythe image file from which data is retrieved and downloadedto the g18.

Figure 53. Programming Page

The following parameters are available in the Programmingtab:

g18 Image File

Browse Enables you to set the input flash.hex file by opening the standard Windows Browse for Folder dialog box. From there you can browse to the location of the required file. Browse to g18 flash, hex file, or enter the name of the file in the File field.

Start Initiates the flashing/program download to g18.

Test Tests the current g18 version and baud rate.

Figure 54. Image File Selection via Browse Button

Note

Test can also be used to ensure that all thepre-start conditions specified in the followingWarning and Rules section are met. In theSetting tab, the Baud Rate will be set as theactive baud rate.

98-08901C39-B 183

g18 PC Loader Application

After activating the test, a Test Report log is displayed, asshown in the example below.

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 messages appear in the window in red.

The sequence of the operations during the programmingprocess 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.

Figure 56. Start Programming Pop-up Approval Message

Note

By pressing Test after the g18 is programmed,the user can check the software version in theconnected g18 to verify that it has beenprogrammed correctly. A message is displayedprompting the user to ensure that the g18 ispowered on before pressing Test.

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. Ifthe prior g18 version is installed on the computer, thefollowing message is displayed prompting the user to poweron the g18 after the first stage is completed.

Figure 57. Programming Message in Earlier g18 Versions

During the programming process, the user can view thecurrent programming phase in the program log. ,

Figure 58. Programming Log in Programming Status Report

Note

The user cannot stop the programming processafter it has been started.

98-08901C39-B 185

g18 PC Loader Application

When the programming process is completed, the followingmessage is displayed. Click OK to close the messagewindow.

Figure 59. Programming Complete Message

186 98-08901C39-B

98-08901C39-B

11. SPECIFICATIONS

A.1 GENERAL

Figure 60. Slim Version

Figure 61. Slim with GPS Version

Figure 62. DIN Version

187

Specifications

A.2 MODEL SPECIFICATIONS

PhysicalForm factor: PCMCIA type III, no PCMCIA connector, for Slim with GPS modelSize: g18 (GPRS) DV Slim: 44.29 x 88.45x10.4 mm

g18 (GPRS) DVG with GPS: 44.54 x 88.45 x 17.6 mmg18 (GPRS) DV DIN: 40 x 80.2 x 7.5 mm

Mounting: Four 2.43mm Ø holes provided on non-DIN modelsWeight: g18 (GPRS) DV Slim: 35.5 g

g18 (GPRS) DVG with GPS: 49 gg18 (GPRS) DV DIN: 22 g

Volume: g18 (GPRS) DV Slim: 36.8 ccg18 (GPRS) DVG with GPS: 57.0 ccg18 (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-800g18 (GPRS) DV Horizontal Board only:

28 pin dual in-line pin socket @1.27 pitch (SAMTEC # CLP-114-02-L-D)

RF output connector: MMCX Jack (female) 50Ω GSM and GPS mating connector plug (male)Coax Huber-Shuhner Johnson ComponentsRG178 11-MMCX-50-1-1 135-3302-001RG316 11-MMCX-50-2-3 135-3403-001

EnvironmentalOperational temperature: -30 to +60° C Storage temperature: -40 to +85° CShock: 20 g’s with 11 millisecond duration

20 impacts in three mutually perpendicular planesVibration: IS-19: 1.5g acceleration

5 to 500 Hz @ 0.1 octave/minute in three mutually perpendicular planesPerformance

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 current300mA 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 ETSIDCS – Power levels # 15 to 0, 0 dBm to 30 dBm per ETSIPCS – Power levels # 15 to 0, 0 dBm to 30 dBm per ETSI

SIM card reader:2 Options: 1. Internal - SIM CR 3/5V SIM2. External - Local interface 3/5 SIM3. 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 maxVil 0.8 V maxVoh 2.5 V min @100 uAVol 0.2 V max @ 100 uAWizard application for running on a PC for running IP over a PPP application. Motorola Proprietary DSC BusGPS 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 maxCircuit 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 channelsL1 1574,42 MHzCode 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

.

Table 34. Interface Connector, 36 Pin Description Stan-dard, Slim, Slim with GPS and DIN Horizontal

Pin # Function1 TX Enable2 RXD UART 2 (GPS RXD on GPS models)1

1 Functionality for these pins is provided only on units with GPS. For more information on wake-up line functionality, refer to Section 3.2.3, “How/When to Wake Up the Unit”.

3 TXD UART 2 (GPS TXD on GPS models)1

4 RS232 – TXD2 5 RS232 – RXD3

6 RS232 – DTR7 RS232 – DCD for CSD call/PDP context

indicator in GPRS4

8 RS232 – RTS9 RS232 – CTS10 RS232 – DSR11 RS232 – RI12 Man test13 Analog Audio In14 Analog Audio Out and Power On/Off5

15 Wake up/GPRS coverage indicator6

16 SIM CR DET17 SIM CR Vcc (3/5Vdc)18 SIM CR Reset (RST)19 SIM CR I/O Data20 SIM CR Clock21 TS (Turn on/stand by)7 22 DSC - Enable23 DSC - Downlink24 DSC - Uplink25 Analog Audio GND26 GND27 GND28 GND29 GND30 Vcc (3.0 – 6 Vdc)31 Vcc (3.0 – 6 Vdc)32 Vcc (3.0 – 6 Vdc)33 Vcc (3.0 – 6 Vdc)34 GPS Ant. PWR (3/5 Vdc)1

35 RX for differential GPS RTCM1

36 GPS 1 pps1

2 Data received by g18 (DCE flow).

3 Data sent from g18 (DCE flow).

4 GPRS PDP context active – DCD line will be active (low). GPRS PDP context not active – DCD line will be inactive (high).

5 The Audio Out line is used to send out the detected audio and as a toggle On/Off pin.

6 The wake up line is bi-directional. When going from non-GPRS coverage to GPRS coverage, a negative pulse will be generated on 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 to the g18.

7 Logic high turns the unit on, logic low places the unit into standby 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.

Table 35. Interface Connector, 28 Pin Description DIN Models

Pin # Function1 Vcc (3.0 – 6) Vdc2 Vcc (3.0 – 6)Vdc3 SIM CR I/O Data4 SIM CR Reset (RST)5 SIM CR Vcc (3/5Vdc)6 SIM CR DET 7 RS232 – DTR8 TS (Turn on/stand by)1 9 Man test10 Wake up/GPRS coverage indicator2 11 GND12 GND13 RS232 – RI14 RS232 – DCD for CSD call/PDP context

indicator in GPRS3

15 TXD UART 216 RXD UART 217 Analog audio GND18 Analog audio out and power on/off 19 Analog audio in20 DSC - Enable21 RS232 - DSR22 DSC - Downlink23 DSC - Uplink24 SIM CR Clock25 RS232 – TXD4

190 98-08901C39-B

Specifications

A.4 SLIM CONNECTIVITY OPTIONS

Figure 63. Data and Voice (Slim) - Connections

26 RS232 - RXD5 27 RS232 - CTS28 RS232 - RTS

1 Logic high turns the unit on, logic low places the unit into standby 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 coverage to GPRS coverage, a negative pulse will be generated on 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 to the g18.

3 GPRS PDP context active – DCD line will be active (low). GPRS PDP context not active – DCD line will be inactive (high).

4 Data received by g18 (DCE flow).

5 Data sent from g18 (DCE flow).

Table 36. Standard, Slim, Slim with GPS and DIN Horizontal Model Functions Available on 36 Pin ZIF

VCC input 3.0 to 6Vdc.

Full RS232 - 9 pins TXD, RXD, RTS, CTS, DSR, DTR, DCD RI at 3V levels.

External SIM Connections

SIM Clock, SIM reset, SIM I/O, SIM VCC, SIM PD.

DSC BUS DSC_EN, Downlink, Uplink Motorola proprietary BUS.

Audio In/Out Audio Out and On/Off in the same pin.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.

Table 35. Interface Connector, 28 Pin Description DIN Models (Continued)

Pin # Function

GPS (GPS option only)

TXD & RXD in 3V levels, 1PPS, RTCM, Antenna power. RXD and TXD lines are at 3V levels. The GPS receiver is the Motorola M12.

Table 37. DIN and Horizontal Model Functions Available on 28 Pin ZIF

VCC Input 3.0 to 6Vdc.

Full RS232 - 9 Pins

TXD, RXD, RTS,CTS, DSR, DTR, DCD RI at 3V levels.

External SIM Connections

SIM Clock, SIM reset, SIM I/O, SIM VCC,SIM PD.

DSC BUS DSC_EN, Downlink, Uplink Motorola proprietary BUS

Audio In/Out Audio Out and On/Off in the same pin. 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 Not available in DIN connectors.

Table 36. Standard, Slim, Slim with GPS and DIN Horizontal Model Functions Available on 36 Pin ZIF

(Continued)

98-08901C39-B 191

Specifications

A.5 SLIM AND GPS CONNECTIVITY OPTIONS

Figure 64. Data and Voice and GPS Model Connections

A.6 DIN CONNECTIVITY OPTIONS

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

Figure 68. g18 DV DIN Horizontal

A.8 LANGUAGE SUPPORT

MIN9.69

40.50

80.20

40.00

3.70

2.80

7.97

11.24

65.505.00

35.00

2.50

6.0923.77

2.9715.20

ø HOLE2.00ø 4.000

2

1

28

27 MIN9.69

40.50

80.20

40.00

3.70

2.80

7.97

11.24

65.505.00

35.00

2.50

6.0923.77

2.9715.20

ø HOLE2.00ø 4.000

2

1

28

27 MIN9.69

40.50

80.20

40.00

3.70

2.80

7.97

11.24

65.505.00

35.00

2.50

6.0923.77

2.9715.20

ø HOLE2.00ø 4.000

2

1

28

27

Language PackDescription

Language 01Western Europe

Language 03 GSM 1900 NA

Language 06 Nordic

Language 07East Europe

Language 08Mid East

Language 08Mid 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

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

Language PackDescription

Language 01Western Europe

Language 03 GSM 1900 NA

Language 06 Nordic

Language 07East Europe

Language 08Mid East

Language 08Mid East Arabic

98-08901C39-B 195

Specifications

Slovenian X

Spanish X

Spanish-American X

Swedish X X

Thai

Turkish X X X

Ukrainian X

Vietnamese with tonal marks

Language PackDescription

Language 01Western Europe

Language 03 GSM 1900 NA

Language 06 Nordic

Language 07East Europe

Language 08Mid East

Language 08Mid East Arabic

196 98-08901C39-B

98-08901C39-B

B. QUICK START

B.1 POWER CONNECTIONSBasic operation requires a single power supply of 3 to 6 Vconnected to the EV board J3 connector.

When an external speaker and microphone are used(hands-free operation), an additional 12V power supply isneeded.

Use switch S2 to power the EV board.

B.2 g18 CONNECTIONSFor all models with a 36 pin ZIF socket, connect the g18 viaa 36 pin FC to connector J120.

For the g18 in DIN Horizontal, connect the g18 to the EVboard using connector J126 or by using a flex cable betweenthe 36 pin ZIF socket and connector J120.

For the g18 in DIN Horizontal, connect the g18 to the EVboard using connector J125.

B.3 CUSTOMER CONNECTIONSFor computer evaluations, connect to a 9-pin D-subconnector J5.

For a customer application, connect the host device toconnector J121 using a flex cable.

B.4 AUDIO CONNECTIONSHeadset - 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.5 SIM CONNECTIONSThe 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.6 BAND SELECTIONSThe default setting of the g18 is 900/1800 MHz band (GSM/DCS).

For PCS operation, you need to change the band using oneof the following options:

• Using the handset: Select Menu/Network/Change Bandand select 1900 Band.

• Using AT commands: Send AT+CBAND=3 (for GSM/DCS=4).

B.7 RS232 CONNECTIONSThe g18 is a DCE device. Connect the RS232 linesaccording to the host device type.

For more details regarding DCE or DTE, refer to “DataLevels” on page 21.

B.8 ANTENNA CONNECTIONSWhen a long 90° MMCX connector is necessary, you canpurchase it through Conectec. For more information, refer to“Vendor Contacts” on page 64.

Note

Pinout of J120/J128 is a mirror image of the ZIFin the g18.

Note

The g18 must undergo a power cycle for theband change to take effect.

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

Note

The SoftGsm function must be disabled in orderto communicate using RS232. (In EV_P4, theSoftGsm jumper is open. In EV_P5, the S3-3dip switch is open.)

198 98-08901C39-B

98-08901C39-B

C. DESENSE

C.1 GENERALWhen wireless data radio technology is integrated intocomputing and telemetry devices, hardware issues related toRF emissions must be considered. For example, thetechnical aspects of enabling a wireless RF device as anintegrated peripheral in a host device, such as RFperformance and inter-operability with the host must beaddressed. 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 actionscan be performed:

• Connect the antenna cable shield to the main ground (PSground).

• Shield the logic section in the user application. (Most ofthe radiation comes from clocks and data lines around thelogic 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.

C.2 DESENSE DEFINEDReceiver desensitization occurs when an unwanted signal ispresent at the radio receive frequency. The signal is usuallythe result of harmonic energy emanating from a highfrequency, non-sinusoidal source. This noise desensitizes orlowers the sensitivity threshold of the receiver.

The radio cannot differentiate between wanted andunwanted signals. In frequency modulated systems, theradio receiver can capture the strongest signal present. Ifwanted and unwanted signals are present and there is not a

significant difference in level, the unwanted signal canovertake the receiver, effectively blocking the wanted signal(see Figure 58).

Consistent and reliable reception occurs when a safetymargin dictated by co-channel rejection is maintained. Forexample, if the co-channel rejection is 10 dB, all unwantedsignals 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. Thismeans an interference signal that is more than 10 dB belowthe wanted signal has little impact on the data receiver’s datarecovery. Any interfering source above this level createsdesense, reducing the radio’s sensitivity for data reception.For each dB above the threshold level, one dB of desense iscreated.

Figure 58. Wanted and Unwanted Signal Levels

C.2.1 Noise Sources

CPU clocks, address and data buses, LCD refresh, switchingpower supplies, and peripheral drivers are the primarycontributors of EMI (see Figure 59). The frequency of theseemissions is often unstable. One reason for this instability isthat high stability clock sources are not a requirement in hostcomputer designs.

The frequency of sources move as a function of temperature,time, and aging. Other sources by nature move within thefrequency spectrum as a function of time. The edges of clocksignals create detectable harmonics well into the 1 GHz

Note

This chapter considers, but does not attempt toresolve, these technical issues since they arebeyond the scope of this guide.

199

Desense

band. This presents a challenge in measuring the effects ofthe emission, since one must first determine where theemission exists in the frequency spectrum.

Noise from the host can conduct through the electrical/mechanical interface or radiate electromagnetic fields thatare received by the modem antenna and impact the modem.Motorola modems are specifically designed to minimizeconducted noise.

Radiated electromagnetic fields emanating from the internalcircuitry are incident on the modem antenna. These fields arethen converted to noise power by the antenna and areincident on the receiver. The physical interface signalingconnection has less impact on the receiver performance andcan be electrically decoupled using passive components.

Figure 59. EMI in a Portable Computer Platform

C.2.2 Receiver Susceptibilities

The receiver is susceptible to being desensed within thechannel bandwidth and at intermediate frequencies used fordown conversion. Consult the particular receiverspecifications for IF frequencies. Excessive noise on powersupply pins can also create sensitivity problems.

C.3 MEASUREMENT TECHNIQUESDesense 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 asystem test.

The test must be non-intrusive. Peripheral test cables orapparatus must not be connected to the unit under test, sincethey can have a significant effect on the receiver sensitivityresults.

Indirect testing is essentially the FCC Part 15 EMI testingthat is currently being performed. Bear in mind that some

assumptions have to be made to extrapolate the results andconvert them to desense figures. Of course, theseassumptions can create a certain level of error in theprediction.

C.3.1 Packet Modem Integration Tester (PMIT)

To enable non-intrusive, labor-saving testing of desense, aPMIT session measures and records the sensitivity of everychannel in the receive band. PMIT produces an RF levelversus channel frequency data set that helps determinesystem coverage. Figure 60 illustrates the PMIT hardwarefacility. 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 60. PMIT Hardware Facility

C.3.1.1 PMIT Data PresentationPMIT produces two columns of data that can be ported toany two-axis linear plotting program. A typical PMIT plot isshown in Figure 61. The plot provides the RF level requiredto produce 1% BER at any channel within the test range.

Figure 61. Typical PMIT Plot

Note

PMIT for the g18 module is not yet available.The following section provides an overviewonly.

200 98-08901C39-B

Desense

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 notdeveloped, use a portable dipole antenna as a measurementantenna.

The measurement apparatus is capable of measuring signalsas low as –120 dBm. A preamplifier is required to allow thespectrum analyzer to achieve these levels. Use the analyzer’ssmallest possible bandwidth resolution, typically 1 kHz, toimprove the dynamic range of the measurement.

If the input impedance of the analyzer is the same as that ofthe radio receiver and the antenna, you can measure the noiseto which the receiver will be subjected. The gain on the lownoise amplifier (LNA) will make low level noise morevisible. Ensure that the spectrum analyzer’s input is notoverridden by other RF signals, such as FM radio stations.Any spikes that appear may cause desense problems.

The indirect method cannot account for data protocolcharacteristics and is less effective. Also, the bandwidth ofthe noise source is important. If the source is narrow band, ithas less effect than a source occupying the entire channelbandwidth. The method is not effective in determiningdesensitization at IF frequencies or from less obvioussources such as mixed products. The method providesinformation on how much effort, if any, needs to occur toresolve desense problems.

This method is useful when connection of the wireless cardis not yet facilitated by the platform, since it can beperformed without the wireless card being present. Thismethod determines the magnitude of the emissions withoutextensive test facility requirements.

Figure 62. Spectrum Analyzer Setup

C.3.3 Preparing the Device Under Test

All battery-operated portable devices implement powermanagement. This means devices are shut down in stages astime elapses. To provide an effective test condition, eachproduct should include a software test mode that powers upall non-passive circuitry. In addition, you are advised to

deploy a pseudo-random-based routine that utilizes allcircuit blocks and peripherals. This ensures that desensetesting considers the worst-case scenario.

PMIT testing can take up to three hours to complete. Thedevice under test (DUT) must remain powered during theentire test cycle. For this reason, use external power sourcesto maintain operation during testing when possible. Typicalcircuit 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. Somedevices generate the bulk of their emissions during userinteraction.

C.4 PERFORMANCE GOALSNetwork coverage is the ultimate goal of emissions control.The allowable emission levels are a function of the radiosensitivity and the required network coverage.

C.4.1 Radio Performance Capabilities

Each radio technology demands certain sensitivityrequirements. Wide area networks require the subscriberdevice to be very sensitive, while local area networksoperate with higher receiver-signal levels.

Highly sensitive radios are more susceptible to noise fromthe host platform. For example, assuming a 10 dBco-channel rejection, a less sensitive receiver tolerates ahigher 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 ofthree meters from the device.

As a reference, the theoretical noise level that the host devicemay emit without desensitizing the most sensitive receiver is~ 40 dB below the FCC limits.

Note

This calculation assumes the host device andthe modem card antenna are isotropic sources.

98-08901C39-B 201

Desense

C.4.2 Determine Emission Level Goals

To determine the allowable emissions levels from the hostdevice, 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 acost-sensitive commercial product. The following is one setof 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 airprotocol reacts in a unique way, and each network performsdifferently under the same levels of unwanted ambient noise.However, noise from the host above the desense thresholdlevel degrades the ultimate potential performance.

Narrow band interference sources have a low probability ofcreating customer problems. Wide band sources have ahigher probability of occurring at a channel frequency andthus have a greater potential for causing problems. For thisdocument, any emission that occupies less than 50 kHz ofthe 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

The measured sensitivity is a function of receiverperformance, 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. Theupper dashed line represents the equivalent FCC Part 15Class B emission level. The lower dashed line is themaximum sensitivity capability of the radio receiver. Thedata set plot (solid line) is the actual performance of the radioreceiver as used with the host platform.

If the host unit met FCC limits from 851 to 870 MHz, theeffective 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 highin this frequency range. Most host devices are well below thelimit in the majority of frequencies.

The worst-case desense from this platform is ~25dB at anarrow spike near 856.5 MHz. The noise floor of the deviceis in the 3 dB range, which is good. There are a number ofspikes that have a 10 dB impact on narrow band channels.

The most notable emission response is at 855.5 MHz wherea wide band emission is present. This response poses aconcern due to the number of channels it impacts and theprobability of a user wanting to operate within that range.The level of desense is a considerable 15dB.

C.6 PREDICTION OF SOURCESDetermining the exact nature and source of each emission isbeyond the scope of this guide, with the exception of somecommon scenarios. Common problems are evident in thesample data set. The large narrow band spikes are usually theresult of harmonics from a clock source. You can determinewhich clock is creating the problem by checking whether theemission is a direct product of the clock frequency or asub-harmonic of it.

For example, if your system runs a 16.8 MHz clock, and a1.23 MHz clock and a strong narrow band emission is foundat 865.2000 MHz, it is reasonable to deduce that theemission is created by the 16.8 MHz clock as a product of865.2/16.8 = 51.5. The 51st harmonic plus a sub-harmonicof 8.4 MHz.

The wide band emissions are normally a switching powersupply. These emissions are created by the low frequency ofthe switcher modulating onto a higher harmonic of anothersource. Switching power supplies creates a lot of magneticenergy due to the need for inductive coils. In fact, any circuitusing large inductors that are not toroidal is usually a sourceof noise.

202 98-08901C39-B

Desense

Some emissions are tricky to pin down. They may resultfrom multiple order mixing of any number of sources. Thebest way to discover these is to shut down sources one by oneand see if the emission disappears. Near field probing allowsa geographical fix on the emission once the source circuitryis identified.

Noise floor problems, where the entire receive band isdesensed, preclude all methods of tracking down individualsources.

A loop probe is a useful measurement tool for confirmingemissions sources. This probe must be small enough topinpoint an area from which the emission is radiating butlarge enough to provide adequate sensitivity.

C.6.1 Probability of Channel Interference

The probability of a strong interference source landing on achannel of interest is actually quite low. The possibility doesexist, especially in single-channel systems, rather thanmulti-channel systems. A multi-channel system provides anumber of frequencies at which to operate.

Using probability to desense a channel only works withnarrow band sources. A wide band emission increases theprobability of desensing a channel proportional to thebandwidth it occupies.

You can calculate the probability of an interference sourcecoinciding with a channel frequency. To do this, considerthat the source usually drifts over a range of frequencies,increasing the possibility that the two will coincide. Providestable clock sources within the host to allow for betterprediction and control of which channels will be affected bythe noise.

C.6.2 Desense Scenarios

The target of 40 dB below FCC Class B guarantees nodesensitization. The typical scenarios that work in favor ofthe 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 wirelesscommunications.

• In most systems, multiple channels are usually availablefor operation. If one channel is desensitized, the radio canchoose to operate on another. This greatly reducespotential coverage problems, and channel switching istransparent to the user.

• The system continues to function even after beinginterfered with, however, coverage range is reduced. In

some applications, this is not a problem. This could betrue for users who do not stray into network fringecoverage areas.

• Two-way protocols can retry unsent messages.

Each platform, network operating model, and user profile isdifferent. As such, each application requires a unique levelof EMI reduction effort.

C.7 METHODS OF CONTROLLING EMISSIONS

Preferred methods of controlling emissions observe that theemissions must be contained to a level 40 dB less than theFCC Part 15 requirements. For WAN products, the acceptedmethod of achieving this is to shield.

Through past experience, it has become evident thatstandard techniques used to achieve FCC certification arenot enough to satisfy wireless communications. Engineeringteams logically attempt an array of decoupling, partialshielding, and PCB layout methods, which produceincremental improvements, but do not achieve the emissioncontrol requirements. Hybrid methods of shielding andsource reduction are often a good approach.

IMPORTANT: Unless the host platform is already close toachieving the goals set out in this chapter, source reductionefforts may only increase the direct materials cost of theproduct without increasing the return on investment.

If a compromise is chosen where the target levels are not thegoal, standard EMI techniques can be of value. For narrowband emissions, some form of clock frequency “pulling” orcontrol can be implemented.

C.7.1 Shielding Approach

The mechanical design of the host product must allow theEMC engineers to create a Faraday Box shield design. Thisis an electrically continuous shielded enclosure. If designedproperly, such an enclosure easily attenuates radiated signalsfrom the host device.

The shield approach initially appears to be a big step. Theadvantage is that the shield minimizes the possible redesignrequired of the host PCB platform and circuitry.

For a thorough discussion of shielded enclosure design, anexcellent reference is Electromagnetic Compatibility:Principles and Applications, by David A Weston. Thepublisher is Marcel Dekker, Inc. 270 Madison Avenue, NewYork, NY 10016. Any well-written text on EMI controlprobably also covers the design of shielded enclosures.

98-08901C39-B 203

Desense

C.7.1.1 Components of the Shield DesignTo be effective, the shield design must incorporate:• A highly conductive shielded enclosure that encapsulates

all of the active circuitry. This can be constructed of sheetmetal 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 keyboardand display apertures in the enclosure. Testing of apertureradiation at the frequencies of interest may prove thatlarger apertures are acceptable to the particular scenario.

C.7.1.2 Benefits of the Shielding ApproachEmission reduction can be achieved using shielding sourcereduction techniques, such as decoupling, or PCB layout andgrounding, or a combination of the two. Once a shield is inplace, any revisions to product circuitry have no effect onemissions levels. If a circuit level approach is used to controlthe emissions, a change in circuitry can bring a newunknown to the emission performance.

In addition, perfecting shielding designs now will provide ajump on future requirements for emission reduction. Withthe proliferation of wireless communications, emissionlevels need to be reduced. It is also likely that the FCC willtighten up the Part 15 regulations.

C.7.2 Alternate EMI Reduction Methods

Although shielding is the “brute-force” method of reducingemission 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 PullingClock pulling is effective when the emission sources arenarrow band (Figure 64). To implement clock pulling, amethod must be devised for the modem to tell the host it ishaving difficulty receiving. Devising such a method isadmittedly very difficult. The host provides pulling of itsinternal emission source, which is identified as a potentialproblem.

If this source is the cause of the interference, the pulling orslight shift of the source frequency moves the harmonicenergy out of the receive channel. This is an inexpensive

way of solving the problem, since no special shielding ordecoupling 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 ISSUESEach RF network has its own requirements for the subscriberdevice. Most networks implement a coverage equalizationscheme. This consists of configuring the infrastructure sitesso that their RF power output is equal to that of thesubscriber device.

Since most portable devices are battery operated, thetransmitter power of the portable units is relatively low. Tocompensate for this, the base site transmitter power isdecreased to a level equal to that of the portable. The basesite has a much larger and more reliable power source, and iscapable of putting out more power. This helps overcomedesense problems that the portable unit incurs. Most networkoperators prefer not to increase their site power because ofERP licence limitations and cell overlap issues.

Network operators must consider ambient noise levels whendesigning their coverage plans. Once the wireless modemand host unit are engineered not to self-desense, a host ofother machines in the user’s environment can still impactradio performance. These machines are not usually withinclose proximity of the wireless modem antenna and have lesseffect. An FCC Class B radiator can impact the wirelessdevice if it is within 30 meters of the device, assuming thatan emission exists at the channel frequency of the radio.

Networks can assist in the desense problem by offering morethan one channel frequency at which to operate. If the radioencounters interference on a channel, it can then roam toanother.

204 98-08901C39-B

Desense

WAN protocols include retry mechanisms that resendmessages not acknowledged from the subscriber device.These protocols can correct problems from intermittentnoise sources by retrying during a time slot that does notcoincide with noise source interference.

At a certain point, desensitizing a wireless modem receivercreates unacceptable coverage in the network. This usuallyis in the 10 dB range, though it can vary with networks.

C.9 ANTENNAThe Motorola g18 wireless modem is not equipped with anon-board antenna. You must provide one within the hostdevice.

C.9.1 Field Strengths from the Antenna

Field strengths from the wireless modem transmitter canreach as high as 100 V/M for WAN products. The hostdevice should be hardened to withstand these levels. LCDdisplays and switching power supplies are particularlysusceptible to RF. Capacitive decoupling of sensitive areasis required. Decouple the reference voltage points on powersupplies, reset lines on processors and keyboard scanningcircuitry.

C.9.2 Antenna Interactions

There are two interactions that can impact the performanceof the antenna.

• By placing a hand near the antenna, a user can detune theantenna and absorb energy. Accordingly, the antennamust be positioned such that interaction between the userand the card is minimized.

• The host device might also interact with the antenna. Thisis particularly true for WAN modems, which have higheroutput power. An imaginary sphere of real estate shouldbe provided for the antenna to function. Cabling for otherperipherals must not interfere with this area.

C.9.3 Antenna Cable Routing

The coaxial cable used to connect the modem to the antennamust be routed away from noise sources such as oscillators,bus lines, or noisy CPUs. These noise sources generate broadband noise that will radiate and be picked up by the antennacable. In addition, this cable should be kept as short aspossible. Avoiding noise sources is the primary goal, sowithin reasonable limits, length can be added to allowrouting away from noise sources.

When a long 90° MMCX connector needs to be used, it canbe purchased through Conectec. For more information, referto “Vendor Contacts” on page 64.

C.10 DESENSE SUMMARYDesense considerations fall into two categories when usinga 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 devicetransmitter on computer operation

The latter consideration is not a significant problem. If RFIis assessed properly, it can usually be corrected withminimal effort and cost.

Because of the need for system coverage, the host EMIinteraction with the radio receiver can be a significant andoften elusive problem to characterize and correct. Mostcomputers are very fast and include numerous highfrequency radiators. These can interfere with the radioreception of the wireless modem.

The theoretical levels at which the receiver might beimpacted are derived from system coverage requirementsand the sensitivity of the radio. These goals are not setarbitrarily to improve product performance but to maintainthe RF performance that the networks demand and that theradios are designed to deliver.

Since each product is unique, the level of noise is verydifficult to predict, as is the amount of effort needed tocontrol it. Measuring the product in an early engineeringphase is key to managing the situation.

98-08901C39-B 205

Desense

206 98-08901C39-B

98-08901C39-B

4. IP OVER AT COMMANDS LIST.

D.1 GENERALThis appendix describes the AT commands set and the newIP over AT service.

The old DSC bus IP primitives set provides radio internalinformation via commands on request, in addition tounsolicited indications.

Since the AT commands set does not provide complete radiointernal indications, a new AT interface is provided, in orderto supply these complementary IP primitives via the RS232serial port in a standard interface (AT). This service is calledCIP.

The AT commands are generally an atomic operation, inwhich only one command at a time is executed. The usermay enable or disable unsolicited AT indications, on acommand level.

The CIP service can be enabled or disabled by the user, butonce the user enables the CIP service, he or she will receiveunsolicited IP primitives based on internal radio events. TheCIP service enables the user to send IP primitive requestsand receive indications.

D.2 ENABLE IP OVER AT SERVICES +CIPE

Defined Values

<cipen>

0 IP over AT services (+CIP) is disabled

1 IP over AT services (+CIP) is enabled

Example

at+cipe?

+CIPE: 1

OK

at+cipe=?

+CIPE:(0-1)

OK

at+cipe=1

OK

D.3 DSC BUS IP PRIMITIVE OVER AT SERVICES +CIP

Defined Values

<len> The length (number of characters) of the field<primdata>.

The value of the length is in decimal.

If the field <primdata> does not exist, then<len> is 00.

<primid> The IP primitive ID (For the list of supportedIPs, refer to “IP Primitives Supported by CIP”,page 209.)

Command Possible Response(s)

+CIPE=<cipen>

+CIPE? +CIPE: <cipen>

+CIPE=? +CIPE: list of supported <cipen>s

Command Possible Response(s)

+CIP=<len>,<primid>,<subadd>[,<primdata>]

+CIP:<len>,<primid>[,<primdata>]+CME ERROR: <err>

+CIP? +CME ERROR: <err>

+CIP=? +CME ERROR: <err>

207

IP Over AT Commands List

The value is two hexadecimal bytes,represented in 4 (ASCII) characters.

<subadd> The sub address within the XCVR, for routingthis IP primitive. (Refer to “IP PrimitivesSupported by CIP”, page 209 for the list of theIPs sub addresses).

<primdata> The data of the specific IP primitive. (Refer to“IP Primitives Supported by CIP”, page 209for the list of the supported IPs). This data willhave padding bytes at the end of the primitivestructure due to the ARM 32 bit alignment.

The number of padding bytes is deferred from0 to 3*N (N > = 0). The padding bytes shouldbe counted in the <len> field. The terminal/TCU should ignore these bytes.

Example

CIP Request (IP_ERROR)

AT+CIP=10,A87E,0020,0003000000

+CIP: 24,a87f,0003FFFF434900000000FFFF

OK

The IP_ERROR_REQ primitive ID is: A87E (hexadecimal).

The sub address is 0020.

The data field is: 0003000000, 10 characters, whichrepresent 5 Hexadecimal bytes: 0x00, 0x03, 0x00, 0x00,0x00

The IP_ERROR_CNF primitive ID is: A87F (hexadecimal).

The data field is: 0003FFFF434900000000FFFF, 24characters, which represent 12 hexadecimal bytes.

Decimal bytes:

0x00, 0x03, 0xFF, 0xFF, 0x43, 0x49, 0x00, 0x00, 0x00,0x00, 0xFF, 0xFF

Example

CIP unsolicited indication

+CIP: 8,1406,00010004

+CIP: 16,a827,000000000000FFFF

AT+CIP=10,A87E,0020,0003000000

ERROR

at+cmee=2

OK

AT+CIP=10,A87E,0020,0003000000

+CME ERROR: "operation not allowed"

208 98-08901C39-B

IP Over AT Commands List

D.4 IP PRIMITIVES SUPPORTED BY CIP

D.5 REQUEST/CONFIRM PRIMITIVESREQ

IP_MUTE_REQ_ID (no_cnf)

IP_CALL_DTMF_REQ_ID (no_cnf)

IP_ERROR_REQ_IDIP_GET_HF_VOLUME_REQ_IDIP_SET_RING_LEVEL_REQ_ID

CNF

IP_ERROR_CNF_ID IP_GET_HF_VOLUME_CNF_ID IP_SET_RING_LEVEL_CNF_ID

SIM Card Information

SEEM_ACTIVATE_CNF_ID: SEEM_STATUS_CNF_ID: SEEM_PIN_VERIFY_CNF_ID: SEEM_PIN_CHANGE_CNF_ID: SEEM_PIN_DISABLE_CNF_ID: SEEM_PIN_ENABLE_CNF_ID: SEEM_UNBLOCKING_CNF_ID:

D.6 UNSOLICITED PRIMITIVESIND IP_ABBR_DIAL_TBL_IND_ID IP_CALL_STATUS_IND_IDIP_CLASS_IND_IDIP_LOW_VOLTAGE_IND_ID IP_MUTE_IND_IDIP_PD_USAGE_IND_IDIP_HOOKSWITCH_IND_ID

IP_CALL_DTMF_REQ 0xA835 0x0017

IP_CALL_STATUS_IND 0xA827 ind->IP

IP_CLASS_IND 0xA829 ind->IP

IP_HOOKSWITCH_IND 0xA809 ind->IP

IP_INDR_CTRL_STATE_IND 0xA825 ind->IP

IP_MUTE_REQ 0xA822 0x0017

IP_MUTE_IND 0xA808 ind->IP

IP_PD_USAGE_IND 0xA826 ind->IP

IP_STOP_REQ 0xA82F req->IP

SEEM_ACTIVATE_CNF 0x1402 cnf->IP

SEEM_ACTIVATE_IND 0x1403 ind->IP

SEEM_CARD_STATUS_IND 0x142B ind->IP

SEEM_DEACTIVATE_IND 0x1406 ind->IP

SEEM_PIN_CHANGE_CNF 0x1411 cnf->IP

SEEM_PIN_DISABLE_CNF 0x1413 cnf->IP

SEEM_PIN_ENABLE_CNF 0x1415 cnf->IP

SEEM_PIN_VERIFY_CNF 0x1417 cnf->IP

SEEM_STATUS_CNF 0x140f cnf->IP

SEEM_UNBLOCKING_CNF 0x1419 Cnf->IP

IP_ERROR_REQ 0xA87E 0x0020

IP_ERROR_CNF 0xA87F Cnf->IP

IP_LOW_VOLTAGE_IND* 0xA884 ind->IP

IP_NUM_OF_ATTACHED_PERIPHERALS_IND

0xA890 ind->IP

IP_ATTACHED_PERIPHERALS_INFO IND

0xA88F ind->IP

IP_GET_HF_VOLUME_REQ 0xA886 0x0017

IP_GET_HF_VOLUME_CNF 0xA887 Cnf->IP

IP_HF_AUDIO_STATUS_IND 0xA888 ind->IP

IP_LTC_ERASED_IND 0xA88A ind->IP

IP_SET_RING_LEVEL_REQ 0xA88B 0x0017

IP_SET_RING_LEVEL_CNF 0xA88C

Cnf->IP

IP_ABBR_DIAL_TBL_IND 0xA831 ind->IP

*IP_LOW_VOLTAGE_IND - Not supported by g18.

98-08901C39-B 209

IP Over AT Commands List

IP_INDR_CTRL_STATE_IND_ID IP_STOP_REQ_ID(txvr->periph)

IP_NUM_OF_ATTACHED_PERIPHERALS_IND

IP_ATTACHED_PERIPHERALS_INFO_IND

IP_HF_AUDIO_STATUS_IND

IP_LTC_ERASED_IND

SEEM_DEACTIVATE_IND_ID SEEM_ACTIVATE_IND_ID

D.7 IP PRIMITIVES CIP SPECIFICATIONS

D.7.1 Class Indicator Primitives

The transceiver sends an ip_class_ind primitive to indicatethe current state of the phone. It is sent shortly after powerup to all the peripherals. It is also sent following a warm plugattachment and whenever the current state of the phonechanges.

The primitive contains several pieces of information that arevery useful to peripherals at power up. The primitive is

specifically designed to "get the ball rolling" in theperipheral and it indicates that the transceiver is ready toperform high level communication with the IP. Intelligentperipherals must wait for the first ip_class_ind primitivebefore sending a primitive to the transceiver (with theexception of the bic_init_intelligent_cnf). Any primitivessent to the peripheral before the ip_class_ind primitivecontain valid data and can be used by the peripheral.

The initial ip_class_ind primitives may not contain theactual number of abbreviated dialing phone book locationsin the SIM card or EEPROM. The transceiver needs to scanand sort the phone book locations before it can indicate thenumber of locations. In addition, the SIM card may be PINprotected. If it is, the SIM card phone book is not accessibleuntil a valid PIN is entered. Currently, this interface supportsa maximum of 255 locations in EEPROM and SIMcombined.

For the restrict phone book start and restrict phone book endfields, the phone book location numbering scheme for theEEPROM and SIM phone book locations is defined by thenumbering scheme field in the ip_abbr_dial_tbl_ind primitive.

BROADCAST GROUP: MMI Statistics

Table 39. IP_CLASS_IND Parameters

Name Format Valid Values Description

Reserved WORD 0 Reserved for future use. Peripherals should ignore it.

Restrict Phone Book Start

WORD

0-2550

Start of phone book location range for the protected (1) and recall only (2) Restrict Phone Book Access modes.Valid for ui1 products only.Obsolete for ui2 products and successors.

Restrict Phone Book End

WORD

0-255254

End of phone book location range for the protected (1) and recall only (2) Restrict Phone Book Access modes.Valid for ui1 products only.Obsolete for ui2 products and successors.

Number of SIM Locations

BYTE 0-155255

Number of SIM card abbreviated dialing locations.Number of locations unknown, initialization in progress.

Number of E2 Locations

BYTE 0-100255

Number of EEPROM abbreviated dialing locations.Number of locations unknown, initialization in progress.

210 98-08901C39-B

IP Over AT Commands List

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.

012345678910111213141516171819202122

EnglishGermanDanishFrenchItalianSpanishSwedishDutchPortugueseFinnishNorwegianGreekHungarianTurkishPolishThaiVietnameseMalayIndonesianTagalogChineseCzechComplex Chinese

Bad Device BYTE01-255

Indicates whether a bad device condition is present.No_bad_device.Bad_device.

Manual Test BYTE01

Indicates whether the TXVR is in manual test mode.In normal mode (not manual test).In manual test mode.

Lock State BYTE01

Indicates whether the TXVR is locked.Unlocked.Locked.

Table 39. IP_CLASS_IND Parameters (Continued)

Name Format Valid Values Description

98-08901C39-B 211

IP Over AT Commands List

Example

+CIP:40,a829,0090000000FE786400000000000014000100FFFF-----ip_class_ind

+CIP: 40,a829,0090-0000-00FE-78-64-00-00-00-00-00-00-14-00-01-00FFFF----

254--120-100 20

Reserved 0090

RestrictPhone Book AccessMode

BYTE

012345

Indicates the Restrict Phone Book Access mode. The protected and recall only modes are an alternate, older restriction scheme that only apply to ui1 phones (BMW Phase IV). For these modes, access to the phone book locations outside the range defined by the restrict phone book start and end fields is restricted.No restrictions, all locations can be read/dialed.Protected, storing/recalling is not allowed outside range (ui1).Recall only, only recalling is allowed outside range (ui1).Phone only, EEPROM locations can be read/dialed.SIM only, SIM locations can be read/dialed.No access, no locations can be read/dialed.

RestrictKeypadDialing

BYTE

01

Indicates whether keypad dialing is restricted. If keypad dialing is restricted, all keypad dialing except for emergency dialing is restricted. Note: Phone book locations, which have not been restricted by the Restrict Phone Book Access mode, may be dialed but not programmed.Keypad dialing allowed.Keypad dialing restricted.

Restrict Phone Number Length

BYTE

1-201-32

Indicates the maximum phone number length allowed for call origination. Only phone numbers less than or equal to this value may be called. Note that emergency dialing is still possible irrespective of this length.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 BYTE01

01

01

0

>> Warm plug capable (bit 0)Not capable of warm plug.Capable of warm plug.

>> Charge only mode (bit 1)Not in charge only mode.In charge only mode.

>> warm plug active (bit 2) bInactive mode.Active mode.

>> reserved for future use (bits 3-7)Reserved bits are zeroed.

Unused BYTE 0 Available for future use.

Table 39. IP_CLASS_IND Parameters (Continued)

Name Format Valid Values Description

212 98-08901C39-B

IP Over AT Commands List

RestrictPhonebook Start 0000

RestrictPhonebook End 00FE - 254

Number of SIM Locations 78 - 120

Number ofE2 Locations 64 - 100

Language 00- English

Bad Device 00

Manual Test 00

Lock State 00- Unlocked

Restrict Phone Book Access Mode 00

Restrict Keypad Dialing 00

Restrict Phone Number Length 14 -20

Unused 1 00

Current State 01

Unused 21 00

D.7.2 Power Down Primitives

At power down, the transceiver informs peripherals via theip_stop_req primitive that the transceiver is powering down.A peripheral that receives an ip_stop_req should perform itsown shutdown procedure, which may include saving someinformation from the transceiver. After this procedure iscomplete, the peripheral should inform the transceiver viathe ip_stop_cnf primitive that it is ready for the power down.

Since peripherals may not function correctly, the transceiverwill eventually time out waiting for ip_stop_cnf primitivesfrom the peripherals. However, in error recovery, significantadditional time is added to the power down process whichmay cause user dissatisfaction. The peripheral must respondwith an ip_stop_cnf primitive in normal situations.

BROADCAST GROUP: Power Down

Example

+CIP: 0,a82f,-----------IP_STOP_REQ (transc->periph.)

D.7.3 Phone Book Related Primitives

The transceiver provides the peripheral with information onphone book locations via the ip_class_ind, ip_pd_usage_indand ip_abbr_dial_tbl_ind primitives. Peripherals canimplement a phone book browsing interface using theinformation available with these primitives and theip_get_info_element_req and ip_get_info_element_cnf

primitives. The primitives support phone book browsing bylocation number and are sorted alphabetically by alpha-tag.Please note that GSM Recommendation 07.07 defines astandards-based phone book interface. This alternateinterface is the preferred interface for future applications.

The transceiver sends an ip_pd_usage_ind primitive toinform peripherals that a phone book location (personaldirectory location) is being used to originate a call.

BROADCAST GROUP: Personal Directory Statistics

Table 40. IP_STOP_REQ Parameters

Name Format Valid Values Description

None None None

Table 41. IP_PD_USAGE_IND Parameters

Name Format Valid Values Description

Memory Type WORD 75Other

Abbreviated dialing memory location.Reserved and should be ignored by the peripheral.

Device Type WORD 01Other

Memory location residing in EEPROM.Memory location residing in the SIM.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

Example

--CALLING_FROM_PB_ABRA_DIAL--NO1--EPROM---ENTER_SMART_BUTTON

+CIP:16,a826,004B-0000-01-FFFFFF-IP_PB_USAGE_IND

Memory Type 004B 75

Device Type 0000 EEPROM

Location 01

Reserve FF-FF-FF

+CIP:16,a826,004B-0001-01-FFFFFF-IP_PB_USAGE_IND

75 SIM LOCATION 1

The transceiver sends an ip_abbr_dial_tbl_ind primitive toprovide peripherals with information on abbreviated dialinglocations in EEPROM and the SIM card.

BROADCAST GROUP: Personal Directory Statistics

Reserved 3 BYTES Padding added by compiler. Should be ignored by the peripheral.

Table 41. IP_PD_USAGE_IND Parameters (Continued)

Name Format Valid Values Description

Table 42. IP_ABBR_DIAL_TBL_IND Parameters

Name Format Valid Values Description

Reserved WORD Reserved for future use, peripherals should ignore.

Numbering Scheme

BYTE

0

The Numbering Scheme indicates how the transceiver interprets 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 equivalent to the `MT' storage type defined in [4].EEPROM locations followed by SIM locations.

Table ID BYTE 01

Usage Table.Alpha Sort Table.

Reserved WORD Reserved for future use, peripherals should ignore.

Usage TableorAlpha Sort Table

32-255BYTES

The Usage Table is a bitmap that indicates the abbreviated dialing locations that contain a number or alpha-tag. When a bit is set to one, the location contains a number or alpha-tag. The 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

+CIP:32,a831,0090-00-01-FFFF-9669676F01666ECB6500

01-alpha_sort_table

Reserved 0090

Numbering Scheme 00

Table ID 01-alpha_sort_table

Reserved FFFF

Usage Table or Alpha Sort Table 96-69-67-6F-01-66-6E-CB-65-00

+CIP:102,a831,0101-00-00-DFF7-010000000000000000000000F06100000000200000000000000400000000000000000000000000000000000000

00-usage_table

Reserved 0101

Numbering Scheme 00

Table ID 00-Usage_table

Reserved DFF7

Usage Table or Alpha Sort Table010000000000000000000000F06100000000200000000000000400000000000000000000000000000000000000

D.7.4 Display Indicator Primitives

The transceiver sends an ip_indr_ctrl_state_ind primitive toinform peripherals of display indicator state changes in thetransceiver's display. At power-up, all indicators areassumed to be off. No ip_indr_ctrl_state_ind primitives aresupplied to indicate this initial state. Following a warm-plugattachment, ip_indr_ctrl_state_ind primitives are sent toprovide the current state of the indicators.

BROADCAST GROUP: Indicator

For the IN USE indicator:

Off (0). Phone not in use. No call in progress.

On (1). Phone in use. A call is in progress.

Flashing (2). Not applicable.

For the NO SERVICE indicator:

Off (0). The phone is registered with a system.

On (1). The phone is outside any system coverage.

Flashing (2). The phone is in an area with coverage, but isnot registered with the system. Only emergency calls (112)are allowed.

The ROAM indicator is meaningful only if the NOSERVICE indicator is off.

Off (0) The phone is registered with its home network.

On (1) The phone is registered with a preferred system otherthan home.

Flashing (2) The phone is registered with a non-preferredsystem.

+CIP: 8,a825,00-01-0000 --ip_indr_ctrl_state_ind--in call

00 - In_use

01- Calling

Indicator ID - 00 in_use

Indicator State 01- calling

Reserved 00-00

Table 43. IP_INDR_CTRL_STATE_IND Parameters

Name Format Valid Values Description

Indicator ID BYTE 012

IN USE indicator.ROAM indicator.NO SERVICE indicator.

Indicator State BYTE 012

Off.On.Flashing.

Reserved 3 BYTEs Padding added by compiler. Should be ignored by the peripheral.

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 ofvoice calls.

D.7.5.1 BackgroundThe transceiver's voice calls are always under parallel callcontrol. This means that any peripheral or handset connectedto the transceiver may act on a voice call regardless of thedevice that actually established the call.

When a peripheral wants to originate a call, it should use theip_call_start_req primitive. The peripheral can use thisprimitive 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 isannounced via the ip_call_status_ind primitive. A peripheralcan direct the transceiver to answer the call via theip_call_accept_req primitive. If the peripheral is interestedin the outcome of call establishment, it will need to monitorsubsequent ip_call_status_ind primitives.

When a peripheral wants to release a call, it can send anip_call_release_req primitive. The transceiver will supplysubsequent call status information via the ip_call_status_indprimitive.

D.7.5.2 Call RestrictionsCall restriction settings in the transceiver's EEPROM andSIM card can affect the call control interface.

Restrict keypad dialing is a flex option. It can preventkeypad dialing except for emergency dialing. Memorydialing from phone book locations is allowed per additionallimitations which may be imposed by restrict phone bookaccess options. The restrict keypad dialing field in theip_class_ind primitive indicates when keypad dialing isrestricted.

Restrict phone book access is a flex option. It can preventvarious types of phone book dialing (memory dialing). TheRestrict Phone Book Access mode, Restrict Phone BookStart, and Restrict Phone Book End fields in the ip_class_indprimitive indicate the transceiver's restricted phone bookaccess settings.

Restrict phone number length is a flex option. It controls themaximum phone number length for mobile-originated calls.For example, the maximum phone number length can be setto prevent international dialing. Emergency dialing isalways allowed regardless of the maximum phone numberlength. The restrict phone number length field in the

ip_class_ind primitive indicates the transceiver's maximumphone number length.

Newer SIM cards support the fixed dialing feature. A specialSIM card phone book contains a list of phone numberprefixes that can be used for outgoing calls. When fixeddialing is enabled, the leading digits in an outgoing call mustmatch a number in the fixed dialing phone book. The fixeddialing status can be determined via primitives in [4].

Restrict incoming calls is a flex option. This restrictionprevents peripherals from being informed of mobileterminated call establishing events via the ip_call_status_indprimitive. This restriction is not communicated to theperipheral directly.

D.7.6 Call Status Indication Primitives

The transceiver sends an ip_call_status_ind primitive toannounce a change in the status of a voice call that itcontrols.

• <Idle>: The CC has returned to the fully Idle state. Nocommunication with the network is in progress. Note thatthe CC may go to the Idle state from any other state.

• <MO Establishment>: The CC is attempting to establisha mobile-originated call.

• <Waiting to Answer MT Call>: The network is attempt-ing to establish a call. The CC is waiting for an entity toinstruct it to answer the call.

• <Completing MT Establishment>: An entity hasinstructed the CC to answer the call. The CC iscompleting the process of establishing the call.

• <Fully Active>: Call establishment is completed. Thecurrent call is now fully active.

• <Releasing>: The current call has started releasing. Notethat the CC may go to the Releasing state from any stateexcept Idle.

The ip_call_status_ind contains a local tone status bit, whichindicates the phone is generating tones locally after a callattempt has failed. The local tone status bit is only validwhen the current call state is idle. In all other call states, theperipheral should ignore the local tone status bit.

BROADCAST GROUP: Call

Note

An IP may receive what it considers to beduplicate call status indications, that is,primitives with the same information more thanonce. IPs must not be affected by receivingduplicate call status indications.

216 98-08901C39-B

IP Over AT Commands List

Table 44. IP_CALL_STATUS_IND Parameters

Name Format Valid Values Description

Local Tone BYTE0 1

>> local tones generated by transceiver (bit 7)Local tones off.Local tones on.

>> bits 0-6 are reservedPeripheral must ignore these bits.

Extended Call States

BYTE

1000010000100001

1000010000100001

Bits indicate current and previous extended call states related to waiting calls, held calls, and multiparty calls.

>> Previous Call State (high nibble)Multiparty call present.Held call present.Active call present.Incoming / Waiting call present.

>> Current Call State (low nibble)Multiparty call present.Held call present.Active call present.Incoming / Waiting call present.

Reserved BYTE Reserved for future use, peripherals must ignore.

Current Call State

BYTE

012345678

>> upper nibble is reservedperipheral must ignore these bits.>> lower nibble

Idle.MO Establishment.Waiting to Answer MT Call.Completing MT Establishment.Fully Active (includes call on hold).Releasing.Redial.Call Pending.MO Alerting.

98-08901C39-B 217

IP Over AT Commands List

Example+CIP: 6,a827,0000000700FF42D1 MO PENDING

+CIP:16,a827,0011000200FFFFFF11-INCOMING CALL

02-WAITING TO

+CIP:16,a827,001000030053FFFF-03-COMPLETINGMT ESTA.

+CIP: 16,a827,0010000300C0FFFF

+CIP:16,a827,002200040008FFFF-04 -ACTIVE CALL

+CIP:16,a827,002200040008FFFF 04 -ACTIVE CALL

Local Tone 00

Extended3Call States 22 - Active/previous_call_present

Reserved 00

Current Call State 04 - Mo establishment

PreviousCall State 00

Reserved 08-FF-FF

D.7.7 Generate DTMF Signalling Primitives

A peripheral can send ip_call_dtmf_req primitives so thatDTMF signalling will be sent to the network. The network

generates the tones to the called party. The ip_call_dtmf_reqprimitive does not generate keypress feedback tones. Theip_key_feedback_ind primitive can be used for this purpose.

Currently, DTMF signaling can only be sent during a callwhen the current state is Fully Active, (see“IP_CALL_STATUS_IND Parameters,” page 217). If thetransceiver receives an ip_call_DTMF_REQ when it is notallowed, the request is ignored. If DTMF signaling is notallowed, the transceiver simply ignores the primitive.

In future, DTMF signalling may be allowed in other callstates. DTMF signaling will never be allowed in the Idlestate. This will prevent nuisance primitives every time theuser presses a key on the peripheral.

The peripheral should send two ip_call_dtmf_req primitivesfor each DTMF digit. The first is normally sent as a result ofa user's key press. It should indicate Start DTMF Signaling.The second is normally sent as a result of a user's key release.It should indicate Stop DTMF Signaling. For the secondaction, the timestamp field indicates the amount of time inmilliseconds that the signaling lasts. This is usually theamount of time that the user has held down the key. Thetransceiver uses the timestamp to produce DTMF signalingfor the correct amount of time in case of network delays orother problems.

PreviousCall State

BYTE

012345678

>> upper nibble is reserved peripheral must ignore these bits.>> lower nibble

Idle.MO Establishment.Waiting to Answer MT Call.Completing MT Establishment.Fully Active (includes call on hold).Releasing.Redial.Call Pending.MO Alerting.

Reserved 3 BYTE Padding added by compiler. Should be ignored by the peripheral.

Table 44. IP_CALL_STATUS_IND Parameters (Continued)

Name Format Valid Values Description

218 98-08901C39-B

IP Over AT Commands List

Example

at+cip=14,A835,0017,00000000010031-START-ip_call_dtmf_req

OK

Time Stamp 00 00 00 00

Start 01

Character Set 00

DTMF Digit 31 (‘1’)

at+cip=14,A835,0017,00000020000031-END-ip_call_dtmf_req

OK

D.7.8 Hook-switch Status Indicator Primitives

The transceiver sends an ip_hookswitch_ind primitive toinform peripherals of the status of portable/externalhandset(s), analog/digital hands-free device(s), and theboom headset (hearing aid adaptor) device.

BROADCAST GROUP: Indicator

Table 45. IP_CALL_DTMF_REQ Parameters

Name Format Valid Values Description

Time Stamp LWORD 0non-zero

When DTMF signaling starts, it should be set to zero.Otherwise, it should be set to time in milliseconds since starting.

Start/Stop BYTE 01

Stop DTMF Signaling.Start DTMF Signaling.

Character Set BYTE0

The character set defines how the DTMF digit is formatted. Motorola GSM Character Set (ASCII).

DTMF Digit BYTE `0'-'9','*','#'ASCII

DTMF digit to start/stop per Character Set.

Table 46. IP_HOOKSWITCH_IND Parameters

Name Format Valid Values Description

Update Reason BYTE 0123456789101112

Flip State Change.Boom Headset Add/Remove.Analog Hands-free Add/Remove.Digital Hands-free Add/Remove.Analog Handset Add/Remove.Digital Handset Add/Remove.Portable Cradle State Change.External Digital Handset Lifted.External Digital Handset Hung-Up.Handset/Hands-free Toggle.Call State Begin/End.Exit Manual Test.Invalid Reason.

Reserved BYTE Reserved for future use, peripheral must ignore.

98-08901C39-B 219

IP Over AT Commands List

Example

PICK_UP_HS

+CIP:16,a809,07-00-00-05-04-0E-FFFF-IP_HOOKSWITCH_IND

07-handset_lifted

Update Reason 07 - External Digital Hand-set Lifted

Reserved 00

Info Mask 00

Hands-free Present Mask 05 - analog hands-freespeakers present and hands- free digital devicespresent (DSC addressnumber 2)

Handset Present Mask 04-->> external digital hand-set present

HandsetActive Mask4 0E

Info Mask BYTE01

01

>> Flip state (bit 0)Closed.Open, or no flip.

>> Boom headset device (bit 1)Not present.Present.

>> Bits 2-7 are reserved for future use, peripheral must ignore.

Hands-free Present Mask

BYTE01

01

>> Analog hands-free speakers (bit 0)Not present.Present.

>> Hands-free digital devices (bits 1-7)Not present.Present.>> If Hands-free Present Mask byte is 0, there are no hands-free devices.

HandsetPresent Mask

BYTE01

01

>> Portable handset (bit 0)Not present (mobile/transportable).Present (portable phone).

>> External digital handset (bits 1-7)Not present.Present.

>> If Handset Present Mask byte is 0, there are no handsets.

HandsetActive Mask

BYTE01

01

>> Portable cradle state (bit 0)In cradle, or not a portable.Not in cradle, or not supported.>> External digital handset (bits 1-7)On hook (in cup).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.

Table 46. IP_HOOKSWITCH_IND Parameters (Continued)

Name Format Valid Values Description

220 98-08901C39-B

IP Over AT Commands List

Reserved FFFF

HS_HUNG_UP

+CIP:16,a809,08-00-00-05-00-00-FFFF-IP_HOOKSWITCH_IND

D.7.9 Microphone Mute Primitives

A peripheral can send an ip_mute_req primitive to instructthe Audio Manager to update the microphone mute state.There is no confirmation to this primitive but there is anip_mute_ind primitive.

The transceiver sends an ip_mute_ind primitive to indicate achange in the microphone mute state. The microphone mutestate can be changed by an intelligent peripheral via theip_mute_req primitive. It can also be changed via thephone's man-machine interface.

BROADCAST GROUP: Indicator

Example

+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 cardreaders present on the DSC bus, it will choose a card readerand SIM card to activate. The transceiver gives a SIM cardin an external card reader priority over a SIM card in theinternal card reader. For details on individual card reader

procedures at power up, power down, SIM carddeactivation, and SIM card insertion, refer to the GSMSubscriber SIM Card Reader Interface Specification,version 1.2.

The primitives listed in the following sections can be used todetermine SIM card status. In general, there are two servicecategories: limited service and ready for full service. Withlimited service, no SIM data fields can be accessed and onlyemergency calls can be placed. Table 49 documents how todetermine the service status category but does not documentall possible return status values for each of the primitivesinvolved. Only primitives with a documented return statusshould be used to determine the SIM card status. Primitive/return status pairs not shown should be ignored.

Table 47. IP_MUTE_REQ Parameters

Name Format Valid Values Description

Type BYTE 0 Toggle microphone mute state, off->on or on->off

Table 48. IP_MUTE_IND Parameters

Name Format Valid Values Description

Mute State BYTE 01

Microphone muting is OFF.Microphone muting is ON.

Reserved 3 BYTEs Padding added by compiler. Should be ignored by the peripheral.

98-08901C39-B 221

IP Over AT Commands List

Table 49. SIM Card Status

SIM Card Status Primitive Return

Status Description

Insert Card(Emergency Only)

SEEM_ACTIVATE_CNF No SIM No card in any card reader at power up.

SEEM_DEACTIVATE_IND No SIM The active card was removed.

Check Card(Emergency Only)

SEEM_DEACTIVATE_IND Bad SIM Bad card, error in communications, or card is backwards.

SEEM_ACTIVATE_INDSEEM_ACTIVATE_CNF

Bad SIM Bad card detected at power up or when activating a new card.

Enter PIN(Emergency Only)

SEEM_STATUS_CNF PIN Enabled

A PIN enabled card has been inserted.

SEEM_PIN_VERIFY_CNF Bad Code Incorrect PIN entered. `Wrong PIN' will blink.

Blocked(Emergency Only)

SEEM_STATUS_CNF PIN Blocked A PIN blocked card has been inserted.

SEEM_PIN_CHANGE_CNFSEEM_PIN_DISABLE_CNFSEEM_PIN_ENABLE_CNFSEEM_PIN_VERIFY_CNF

PIN Blocked Incorrect PIN entered more than 3 times, card is blocked.

SEEM_UNBLOCKING_CNF PIN Blocked An incorrect unblock code was entered.

Bad Cardsee Supplier(Emergency Only)

SEEM_STATUS_CNFSEEM_PIN_CHANGE_CNFSEEM_PIN_DISABLE_CNFSEEM_PIN_ENABLE_CNFSEEM_PIN_VERIFY_CNFSEEM_UNBLOCKING_CNF

No SecretCodeorOtherTechnicalProblem

The SIM card is defective.

Blocked,see Supplier(Emergency Only)

SEEM_STATUS_CNFSEEM_UNBLOCKING_CNF

Permanently Blocked

The SIM card is permanently blocked.

Transition to New Status in Process(Emergency Only)

SEEM_ACTIVATE_CNF SIM Available

SIM card is activated.

222 98-08901C39-B

IP Over AT Commands List

D.7.11 Idle SIM Card Notification Primitives

The transceiver sends a seem_activate_ind primitive toindicate that an idle, non-active SIM card has been insertedor removed. This primitive does not indicate anything aboutthe status of the active SIM card.

BROADCAST GROUP: SIM Availability

Example

+CIP: 8,1403,0004-007F 04_idle_sim-SEEM_ACTIVATE_IND

SIM Status 0004 › Idle SIM, idle SIMinserted.

Reserved 007F

+CIP: 8,1403,0001-0381 01_no_sim_==remove_sim-SEEM_ACTIVATE_IND

SIM Status- -- 0001 › No SIM, idle SIMremoved or no alternate SIMpresent

Reserved 007F

D.7.12 SIM Card Deactivation Notification

The transceiver sends a seem_deactivate_ind primitive toindicate that the active SIM card has been removed or is nolonger usable because of a SIM card communication failure.This primitive always indicates that the active SIM card is nolonger usable.

BROADCAST GROUP: SIM Availability

Ready forFull Services

SEEM_STATUS_CNF PIN Disabled

PIN code is disabled.

SEEM_PIN_VERIFY_CNF Successful PIN entry has unlocked the SIM card.

SEEM_UNBLOCKING_CNF Successful PUK entry has unblocked the SIM card.

Table 49. SIM Card Status (Continued)

SIM Card Status Primitive Return

Status Description

Table 50. SEEM_ACTIVATE_IND Parameters

Name Format Valid Values Description

SIM Status WORD 124

No SIM, idle SIM was removed or no alternate SIM is present. Bad SIM.Idle SIM, idle SIM inserted.

Reserved WORD Padding added by compiler. Should be ignored by the peripheral.

Table 51. SEEM_DEACTIVATE_IND Parameters

Name Format Valid Values Description

SIM Status WORD 12

No SIM, active SIM card has been removed.Bad SIM, phone can no longer talk to the active SIM card.

98-08901C39-B 223

IP Over AT Commands List

Example

+CIP: 8,1406,0001-0381 01-no_sim-SEEM_DEACTIVATE_IND

SIM Status 0001 › No SIM, active SIM card has been removed

Reserved 0381

D.7.13 SIM Card Activation Notification Primitives

The transceiver is responsible for deciding when to initiate aSIM card activation. It will forward a copy of theseem_activate_cnf primitive to subscribing peripherals.Therefore, a peripheral can use the seem_activate_cnf todetermine the state of the active SIM card.

BROADCAST GROUP: SIM Availability

Example

+CIP: 8,1402,0001-0200 01_no_sim-SEEM_ACTIVATE_CNF

SIM Status 0001 › No SIM, active SIM card has been removed

Reserved 0200

D.7.14 SIM Card Security Notifications

Shortly after the transceiver activates a SIM card it willcheck the PIN status of the SIM card. When provided, the

transceiver will subsequently coordinate the submission ofcodes such as the PIN and PUK to the SIM card. Thetransceiver forwards a copy of the confirmation primitivesassociated with these procedures to peripherals. This allowsperipherals to track the security status of the active SIM card.Peripherals may also check the active SIM card's securitystatus via the newer MMI primitives ip_gen_pin_status_reqand ip_gen_pin_status_cnf.

Immediately after SIM card activation, the transceiverforwards a seem_status_cnf primitive to peripherals.

BROADCAST GROUP: SIM Security/Access

Reserved WORD Padding added by compiler. Should be ignored by the peripheral.

Table 51. SEEM_DEACTIVATE_IND Parameters (Continued)

Name Format Valid Values Description

Table 52. SEEM_ACTIVATE_CNF Parameters

Name Format Valid Values Description

SIM Status WORD 012

SIM Available, active SIM has answered to reset correctly.No SIM, there is no active SIM card.Bad SIM, phone cannot talk to the active SIM card.

Reserved WORD Padding added by compiler. Should be ignored by the peripheral.

Table 53. SEEM_STATUS_CNF Parameters

Name Format Valid Values Description

PIN Result WORD 235678

PIN enabled, PIN entry required.PIN disabled, no PIN entry required.PIN blocked, user must enter PUK to unblock.Permanently blocked.No secret code.Other technical problem.

224 98-08901C39-B

IP Over AT Commands List

Example

+CIP:8,140f,0003-0300 03_pin_disable-SEEM_STATUS_CNF

PIN Result 0003 › PIN Disabled, no PINentry required

Reserved 0300

Following a PIN entry attempt, the transceiver forwards aseem_pin_verify_cnf primitive to peripherals.

BROADCAST GROUP: SIM Security/Access

Example

+CIP: 8,1417,0005-0300 05_PIN_BLOCKED---SEEM_PIN_VERIFY_CNF

PIN Result 0005 › PIN Blocked, from 3rdPIN verification failure

Reserved 0300

Following a PUK entry attempt, the transceiver forwards aseem_unblocking_cnf primitive to peripherals.BROADCAST GROUP: SIM Security/Access

Example

+CIP: 8,1419,0000-0300 00_SUCCESS_PUK(PUK2)SEEM_UNBLOCKED_CNF

PIN Result 0000 › Success, PUK verificationsuccessful

Reserved 0300

Reserved WORD Padding added by compiler. Should be ignored by the peripheral.

Table 53. SEEM_STATUS_CNF Parameters (Continued)

Name Format Valid Values Description

Table 54. SEEM_PIN_VERIFY_CNF Parameters

Name Format Valid Values Description

PIN Result WORD 01578

Success, PIN verification successful.Bad Code, PIN verification failure, not PIN blocked.PIN Blocked, from 3rd PIN verification failure.No Secret Code.Other Technical Problem.

Reserved WORD Padding added by compiler. Should be ignored by the peripheral.

Table 55. SEEM_UNBLOCKING_CNF Parameters

Name Format Valid Values Description

PIN Result WORD 01678

Success, PUK verification successful.Bad code, PUK verification failure, not permanent blocked.Permanently blocked, from 3rd PUK verification failure.No secret code.Other technical problem.

Reserved WORD Padding added by compiler. Should be ignored by the peripheral.

98-08901C39-B 225

IP Over AT Commands List

Following a PIN disable attempt, the transceiver forwards aseem_pin_disable_cnf primitive to peripherals.

BROADCAST GROUP: SIM Security/Access

Example

+CIP:8,1413,0000-0300-----_SUCCESS_DISABLE--SEEM_PIN_DISABLE_CNF

PIN Result 0000 › Success, PUK verification successful

Reserved 0300

Following a PIN enable attempt, the transceiver forwards aseem_pin_enable_cnf primitive to peripherals.

BROADCAST GROUP: SIM Security/Access

Example

+CIP:8,1415,0000-0300 00_SUCCESS_ENABLE--SEEM_PIN_ENABLE_CNF

PIN Result 0000 › Success, PIN entryrequired at power-up.

Reserved 0300

Following a PIN change attempt, the transceiver forwards aseem_pin_change_cnf primitive to peripherals.

BROADCAST GROUP: SIM Security/Access

Table 56. SEEM_PIN_DISABLE_CNF Parameters

Name Format Valid Values Description

PIN Result WORD 013578

Success, no PIN entry required at power-up.Bad code, PIN does not match, PIN not disabled.PIN disabled, PIN entry was already disabled.PIN blocked, from 3rd bad PIN code.No secret code.Other technical problem.

Reserved WORD Padding added by compiler. Should be ignored by the peripheral.

Table 57. SEEM_PIN_ENABLE_CNF Parameters

Name Format Valid Values Description

PIN Result WORD 012578

Success, PIN entry required at power-up.Bad code, PIN does not match, PIN not enabled.PIN enabled, PIN entry was already enabled.PIN blocked, from 3rd bad PIN code.No secret code.Other technical problem.

Reserved WORD Padding added by compiler. Should be ignored by the peripheral.

226 98-08901C39-B

IP Over AT Commands List

Example

+CIP:8,1411,0000-0300->00_SUCCESS_PIN_CHANGE---SEEM_PIN_CHANGE_CNF

PIN Result 0000 › Success. PIN code was changed

Reserved 0300

Following a warm plug attach, the transceiver sends aseem_card_status_ind primitive with current SIM cardsecurity information. Peripherals should be careful using the

PIN result field. This field contains the status of the lastsecurity operation. Its meaning is largely dependent on thelast security operation attempted. The ip_gen_pin_stat_reqand ip_gen_pin_stat_cnf primitives are a more reliablemechanism for determining the PIN status of the active SIMcard following a warm plug attach.

BROADCAST GROUP: SIM Security/Access

Table 58. SEEM_PIN_CHANGE_CNF Parameters

Name Format Valid Values Description

PIN Result WORD 014578

Success, PIN code was changed.Bad code, old PIN does not match, not changed.Not allowed, PIN entry is not enabled, cannot change.PIN blocked, from 3rd bad PIN code.No secret code.Other technical problem.

Reserved WORD Padding added by compiler. Should be ignored by the peripheral.

Table 59. SEEM_CARD_STATUS_IND Parameters

Name Format Valid Values Description

PIN Result WORD 0123456789

Success, last operation successfulBad code, last operation not successfulPIN enabled, PIN entry was already enabledPIN disabled, PIN entry was already disabledNot allowed, last operation is not allowedPIN Blocked, from 3rd bad PIN codePermanently blocked, from 3rd pad PUK codeNo secret codeOther technical problemSwitch band

SIM Status WORD 0123456789

SIM available, active SIM has answered to reset properlyNo SIM, there is no active SIM cardBad SIM, phone cannot talk to the active SIM cardGood SIM, after test cardIdle SIM, new card just insertedUninitialized SIM, no secret code and perm blockedActive SIM, current working card in for tableClone SIM, clone card indication to MMIGood clone, after test clone cardActive clone, current working clone card for table

98-08901C39-B 227

IP Over AT Commands List

Example

+CIP: 8,142b,0004-0004------------------------SEEM_CARD_STATUS_IND

PIN Result 0004 › Success, last operationsuccessful

SIM Status 0004-> Not Allowed, last operation isnot allowed

D.7.15 Attached Peripherals Primitives

The IP_ATTACHED_PERIPHERALS_IND primitive’spurpose is to inform the IP of the mobile's peripherals status.It will inform all DSC addresses held by peripherals, theirtypes and specific information, as well as unregistered orfailed peripherals.

The IP_ATTACHED_PERIPHERALS_IND primitiveconsists of the following fields:

• DSC_ADDR: The DSC address that the radio has allo-cated to the peripheral.

• PRODUCT_ID: The type of peripheral that is present (forexample, card reader, DHFA, eject box, and so on.)

• BIC_SERIAL_NUM: Serial number of peripheraldevice, programmed into BIC EEPROM.

• SW_VERSION_NUM: Peripheral’s software versionnumber.

• STATUS: The status of the peripherals: either ALIVE orDEAD. With "dead" status, the peripherals either do notexist on the DSC bus or do exist but have failed toinitialize.

• FAILED_TO_INITIALIZE: If this field is "true", theperipherals are actually attached to the DSC bus but havefailed during the initialization process. If this field is"false", then there are no peripherals attached to the DSCbus.

• DEVICE_TYPE_BMAP: This bit-mapped field holds allthe Call Processor events, which this peripheral isinterested in receiving.

These seven fields are held for each peripheral attached tothe radio. In addition, there are two fields that hold thenumber of ALIVE peripherals on the bus and the number ofperipherals, which have failed during the initializationprocess.

NUM_OF_ALIVE - Number of ALIVE peripherals.

NUM_OF_FAILED - Number of peripherals that havefailed to initialize.

BROADCAST GROUP: Intelligent peripherals can useprimitive broadcasting groups to select the primitives theyreceive from the transceiver. This allows peripherals toreduce the overhead associated with primitives that are notnecessary for a specific intelligent peripheral application.

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

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

228 98-08901C39-B

IP Over AT Commands List

Example

HS LIVE

+CIP: 36,a88f,02-000A-000A017402A8-0000-00-0000-00000000

DSC_ADDR 02

PRODUCT_ID 000A › 0000-0fff Dumb / HS

BIC_SERIAL NUM 00-0A-01-74-02-A8

SW_VERSION 0000

STATUS 00 › 0 - live (registered)peripheral

FAILED_TO INITIALIZE 0000

DEVICE_TYPE BMAP 00-00-00-00

+CIP: 36,a88f,01-8011-8011017402A0-3309-00-0000-00000020

LIVE SIM

D.7.16 IP_HF_AUDIO_STATUS_IND

Indication whenever any type of audio is starting or ending.

The purpose of this primitive is to let the TCU know aboutpending audio, in order to synchronize other audio relatedmachines like entertainment radio etc.

Table 61. IP_ATTACHED_PERIPHERALS_INFO_IND Parameters

Name Format Valid Values Description

DSC_ADDR BYTE 1-7

PRODUCT_ID WORD0000-0ffff8000-80108011803480318032

Shows the product type (TCU,EMMI,SIM etc)Dumb / HSEmmi E. SIM C/RACP TCU JaguarTeleAid DCTeleAid DC

BIC_SERIAL NUM

6 BYTES If it exists and status is dead, it means this peripheral failed to register

SW_VERSION WORD

STATUS BYTE 02

Live (registered) peripheralDead (no peripheral or failed to register)

FAILED_TO INITIALIZE

WORD

DEVICE_TYPE BMAP

LWORD 0001 0010 0020 00400080

Emmi Data SIM BMW TCUGen. TCU

98-08901C39-B 229

IP Over AT Commands List

Example

+CIP:8,a888,01-9F17DEIP_HF_AUDIO_STATUS_IND

Audio_status 01

Reserved 9F-17-DE

+CIP:8,a888,00-9F17DEIP_HF_AUDIO_STATUS_IND

Audio_status 00

Reserved 9F-17-DE

D.7.17 IP_SET_RING_LEVEL_REQ

Allows the TCU to control the ringer gain level.

Example

at+cip=6,a88b,0017,00-05-00 ip_set_ring_level_req

Ring_type 00

Ring_level 05- Req ring gain

Addressing_info 00

D.7.18 IP_SET_RING_LEVEL_CNF

Provides a confirmation regarding the ringer gain levelrequest.

The reply contains the gain level adjusted and the statusresults.

The status results indicate whether the gain requested wasout of limits or a valid result.

Table 62. IP_HF_AUDIO_STATUS_IND Parameters

Name Format Valid Values Description

Audio_status BYTE 10

Audio startedAudio ended

Reserved 3 BYTE Padding added by compiler. Should be ignored by the peripheral.

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

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

Example

+CIP:8,a88c,00-05-00-03 ip_set_ring_level_cnf

Ring_type 00 Ring_level 05 Ring gainAddressing_info 00 Req_status 03 level_is_changed

D.7.19 IP_LOW_VOLTAGE_IND

Indicates any movement from one voltage level to another.

Due to hardware defense circuitry, the XCVR may not arriveat the points that are under voltage and over voltage.

.

D.7.20 IP_GET_HF_VOLUME_REQ

Request for HF voice and ringer gain levels.

Example

at+cip=2,A886,0017,00 ip_get_hf_volume_req

addressing_info 00

D.7.21 IP_GET_HF_VOLUME_CNF

Returns the HF voice and ringer gain levels.

Req_status BYTE 0123

less_than_min same_levelmore_than_maxlevel_is_changed

Table 64. IP_SET_RING_LEVEL_CNF Parameters (Continued)

Name Format Valid Values Description

Table 65. IP_LOW_VOLTAGE_IND Parameters

Name Format Valid Values Description

Low_voltage_state BYTE 1 2

Low voltage - Battery with "low batt active" Normal volt - FULL battery - out of low batt

Table 66. IP_GET_HF_VOLUME_REQ Parameters

Name Format Valid Values Description

Addressing_info BYTE N/A Unused

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

+CIP:8,a887,07--04--01-00 ip_get_hf_volume_cnf

VOICE RING

Voice_gain_level 07 - Voice - HF gain level

Ring_gain_level 04 - Ringer - HF gain level

Success 01

Addressing_info 00

D.7.22 IP_LTC_ERASED_IND

Indicates to the TCU that there are no phone numbers in theLTC (last ten call) list, meaning, the last dialed number waserased.

Example

+CIP:8,a88a,01-00004D ip_ltc_erased_ind

01-ltc_erased

Erased 01 ltc_erased

Reserved 00-00-4D

D.8 IP PRIMITIVES CIP EXAMPLES

Table 68. IP_LTC_ERASED_IND Parameters

Name Format Valid Values Description

Erased BYTE 01

Not erasedErased

Reserved 3 BYTEs Padding added by compiler. Should be ignored by the peripheral.

Table 69. IP_CALL_STATUS_IND Ref. GSM-IP 7.3

Action Reaction Remark

Power up MS. Wait response:+CIP: 12,a827,000000000000

Verify the response is correct.

The transceiver sends an ip_call_status_ind primitive to announce a change in the status of a 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. Dial number. Wait response: +CIP: 12,a827,000000010000

Verify the response is correct.

01 MO established.

MO voice call. Call is alerted. Wait response: +CIP: 12,a827,000000020003

Verify the response is correct.

02 Waiting to answer MO call.

MO voice call. Call is answered. Wait response: +CIP: 12,a827,002200040043

Verify the response is correct.

04 Fully active. 22 Active call present.

MO voice call. Releasing. Wait response: +CIP: 12,a827,002000050006

Verify the response is correct.

05 Releasing. 20 Active call state - previous call state.

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. No +CIP:4,A825,XXXX should be send.

Verify the response is correct.

The transceiver sends an ip_indr_ctrl_state_ind primitive to inform peripherals of display indicator 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. Remove antenna Wait response: +CIP:4,A825,0201 Insert antenna Wait response +CIP:4,A825,0200

Verify the response is correct.

Power up MS. Make call Wait response +CIP:4,A825,0001 Release call Wait response +CIP:4,A825,0000

Verify the response is correct.

Table 71. IP_STOP_REQ Ref. GSM-IP 6.6.

Action Reaction Remark

Power down MS. Wait response: +CIP: 0,A82F

Verify the response is correct.

At power down the transceiver will inform peripherals via the ip_stop_req primitive that the 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 Wait response: +CIP,XX, A88f,M1...Mn

Verify the response is correct.

CIP with ID=A88F replaces CIP with ID=A885. This is a TCG solution. The +CIP report should be 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. Wait response: +CIP: 2,A888,01 +CIP:2,A888,00

Verify the response is correct:2 "+CIP " indicators for every button.01 audio started02 audio endedVerify Side Tone in SPKR.

Indication whenever any type of hands-free audio is starting or ending.The purpose of this primitive is to let the TCU know about pending HF audio, in order to synchronize other audio related machines, such as entertainment radio and so on.

Table 74. LTC_ERASED_IND Ref. GSM-IP10.11.

Action Reaction Remark

Make MO call.Empty LTC memory area via HS. Wait response: +CIP: 2,A88A,01

Verify the response is correct.00 Not erased01 Erased

Indicates to the TCU that there are no phone numbers in the LTC (last ten call) list, meaning, the last dialed number was erased.

Table 75. SEEM_CARD_STATUS_IND Ref. GSM-IP 10.3.

Action Reaction Remark

Power-Up MS, wait response: +CIP: 8,142B,(0-9)(0-9)

Verify the response is correct.0 SUCCESS1 BAD_CODE2 PIN_ENABLED3 PIN_DISABLED4 NOT_ALLOWED5 BLOCKED6 PERM_BLOCKED7 NO_SECRET_CODE8 OTHER_TECHNICAL_PROBLEM9 SWITCH_BAND

This primitive is sent to the IP whenever it receives an update from the SIM manager in the mobile.

234 98-08901C39-B

IP Over AT Commands List

Table 76. SEEM_ACTIVATE_IND Ref. GSM-IP 9.1.

Action Reaction Remark

Power-Up MS with normal SIM, Wait response: +CIP: 4,1403,0004

Verify the response is correct. This primitive is sent to the IP whenever it received an update from the SIM manager in the mobile.

Power-Up MS without SIM, Wait response: +CIP:4,1403,0001

Verify the response is correct.

Power-Up MS with BAD SIM, Wait response: +CIP: 4,1403,0002

Verify the response is correct.

Table 77. SEEM_ACTIVATE_IND Ref. GSM-IP 9.3.

Action Reaction Remark

Power-Up MS with normal SIM, Wait response: +CIP: 4,1402,0000

Verify the response is correct. 0 SIM Available, active SIM has answered to reset properly

Power-Up MS without SIM, Wait response: +CIP: 4,1402,0001

Verify the response is correct. 1 No SIM, there is no active SIM card

Power-Up MS with BAD SIM, Wait response: +CIP: 4,1402,0002

Verify the response is correct. 2 Bad SIM, phone cannot talk to the active SIM

Table 78. SEEM_DEACTIVATE_IND Ref. GSM-IP 9.2.

Action Reaction Remark

Power-Up MS with normal SIM, Remove SIM. Wait response: +CIP: 4,1406,0001

Verify the response is correct.1 No SIM, active SIM card has been removed.

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.

Power-Up MS with BAD SIM, Wait response: +CIP: 4,1406,0002

Verify the response is correct.2 Bad SIM, phone can no longer talk to the active SIM card.

98-08901C39-B 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. Use correct PIN1 code. Wait response: +CIP: 8,1411,0000yyyy

Verify the response is correct.0 Success, PIN code was changed.

Following a PIN change attempt, the transceiver forwards a seem_pin_change_cnf primitive to peripherals.

Change PIN via HS menu. Use wrong PIN1 code. Wait response: +CIP: 8,1411,0001yyyy

Verify the response is correct.1 Bad Code, old PIN does not match, not changed.

Change PIN via HS menu. Use wrong PIN1 code three times. Wait response: +CIP:8,1411,0005yyyy

Verify the response is correct.5 PIN Blocked, from third bad PIN code.

Table 80. SEEM_PIN_DISABLE_CNF Ref. GSM-IP 9.4.

Action Reaction Remark

Power-Up MS with PIN requested. Set "PIN disabled" via HS menu. Use correct PIN1 code. Wait response: +CIP: 8,1413,0000yyyy

Verify the response is correct.0 Success, no PIN entry required at power-up.

Following a PIN disable attempt, the transceiver forwards a seem_pin_disable_cnf primitive to peripherals.

Power-Up MS with PIN requested. Set "PIN disabled" via HS menu. Use wrong PIN1 code. Wait response: +CIP: 8,1413,0001yyyy

Verify the response is correct.1 Bad Code, PIN does not match, PIN not disabled.

Power-Up MS with PIN requested. Set "PIN disabled" via HS menu. Use correct PIN1. Set "PIN disabled" via HS menu again. Wait no response.

Verify the response is correct.3 PIN disabled, PIN entry was already disabled.

Power-Up MS with PIN requested. Set “PIN disabled” via HS menu. Use wrong PIN1 code three times. Wait response: +CIP: 8,1413,0005yyyy

Verify the response is correct.5 PIN Blocked, from third bad PIN code.

236 98-08901C39-B

IP Over AT Commands List

Table 81. SEEM_PIN_ENABLE_CNF Ref. GSM-IP 9.4.

Action Reaction Remark

Power-Up MS. Set "PIN enabled" via HS menu.Use correct PIN1 code. Wait response: +CIP:8,1415,0000yyyy

Verify the response is correct.0 Success, PIN entry required at power-up.

Following a PIN enable attempt, the transceiver forwards a seem_pin_enable_cnf primitive to peripherals.

Power-Up MS. Set "PIN enabled" via HS menu.Use wrong PIN1 code. wait response: +CIP: 8,1415,0001yyyy

Verify the response is correct.1 Bad Code, PIN does not match, PIN not enabled.

Power-Up MS. Set "PIN enabled" via HS menu.Use correct PIN1 code. Try again to set "PIN enabled" . Wait no response:

Verify the response is correct.2 PIN Enabled, PIN entry was already enabled.

Power-Up MS. Set "PIN enabled" via HS menu. Use wrong PIN1 code three times. Wait response: +CIP: 8,1415,0005yyyy

Verify the response is correct.5 PIN Blocked, from 3rd bad PIN code.

Table 82. SEEM_PIN_VERIFY_CNF Ref. GSM-IP 9.4.

Action Reaction Remark

Power-Up MS with PIN1 required. Enter correct PIN1. Wait response: +CIP: 8,1417,0000yyyy

Verify the response is correct.0 Success, PIN verification successful.

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.

Power-Up MS with PIN required. Enter wrong PIN. Wait response: +CIP: 8,1417,0001yyyy

Verify the response is correct.1 Bad Code, PIN verification failure, not PIN blocked.

Power-Up MS with PIN required. Enter wrong PIN 3 times. Wait response: +CIP:8,1417,0002yyyy

Verify the response is correct.5 PIN Blocked, from 3rd PIN verification failure.

98-08901C39-B 237

IP Over AT Commands List

Table 83. SEEM_STATUS_CNF Ref. GSM-IP 9.4.

Action Reaction Remark

Power-Up MS without PIN required.Wait response: +CIP: 8,140F,0003yyyy

Verify the response is correct.3 PIN Disabled, no PIN entry required.

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.

Power-Up MS with PIN required Wait response: +CIP:8,140F,0002yyyy

Verify the response is correct.2 PIN Enabled, PIN entry required.

Power-Up MS with PUK1 required Wait response: +CIP: 8,140F,0005yyyy

Verify the response is correct.5 PIN Blocked, user must enter PUK to unblock.

Table 84. SEEM_UNBLOCKING_CNF Ref. GSM-IP 9.4.

Action Reaction Remark

Power-Up MS with PUK1 required. Enter wrong PUK1. Wait response: +CIP: 8,1419,0001yyyy

Verify the response is correct.1 Bad Code, PUK verification failure, not permanently blocked.

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.

Power-Up MS with PUK1 required. Enter correct PUK1. Wait response: +CIP: 8,1419,0000yyyy

Verify the response is correct.0 Success, PUK verification successful.

Table 85. IP MUTE Ref. GSM-PCN.8.3.

Action Reaction Remark

MS is in conversation. AT+CIP=2,A822,0017,00 Wait response: +CIP: 4,A808,0100

Verify the response is correct.Check Mic muting before (off) and after (on) AT command.

01 means microphone muting is "on".

MS is in conversation. AT+CIP=2,A822,0017,00 Wait response: +CIP: 4,A808,0000

Verify the response is correct.Check Mic muting before (on) and after (off) AT command.

00 means microphone muting is "off".

238 98-08901C39-B

IP Over AT Commands List

Table 86. IP CALL DTMF Ref. GSM-PCN.7.7

Action Reaction Remark

Dial *054. Enter AT+CIP=14,A835,0017,00000000010031;

+CIP=14,A835,0017,000001f4000031 No response.

Verify no response. Check the stepping into menu. Check "1" displayed on HS screen.

1 Digit 1 will be sent as DTMF signal.

Dial *054. Enter AT+CIP=14,A835,0017,00000000010023;

+CIP=14,A835,0017,000001f4000023 No response.

Verify no response. Check the stepping into menu. Check "*" displayed on HS screen.

* Char. "#" will be send as DTMF signal.

Dial *054. Enter AT+CIP=14,A835,0017,0000000001002B;

+CIP=14,A835,0017,000001f400002B No response.

Verify no response. Check no stepping into menu. Check no "+" displayed on HS screen.

"B" is incorrect value. Nothing will be sent as DTMF signal.

Table 87. IP ERROR Ref. GSM 07.07.7.10.

Action Reaction Remark

Enter: AT+CIP=10,A87E,0020,0003000000 Wait response: +CIP: 16,A87F,0003FFFF0000ZZZZ

00 Read error codes stored in EEPROM. FFFF Indicates success. ZZZZ Code of the stored Error.

Enter: AT+CIP=10,A87E,0003000001 Wait response: +CIP:8,A87F,0003FFFF00000000

01 Clear error codes stored in 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) Enter: AT+CIP=2,A886,17,FF Wait response: +CIP:8,A887,070401FF

Verify the response is correct. XX Voice - HF gain level YY Ringer - HF gain level 01 PASS (phone is in hands-free mode).

(The phone is in hands-free mode) Enter: AT+CIP=6,A88B,0017,FF05FF Enter: AT+CIP=2,A886,FF Wait response: +CIP:8,A887,XXYY05FF

Verify the response is correct. XX Voice - HF gain level YY Ringer - HF gain level 00 FAIL (if the phone is not in hands-free mode).

98-08901C39-B 239

IP Over AT Commands List

(The phone is not in hands-free mode) Enter: AT+CIP=2,A886,FF Wait response: +CIP:8,A887,XXYY00FF

Verify the response is correct. XX Voice - HF gain level YY Ringer - HF gain level 00 FAIL (if the phone is not in hands-free mode).

Table 88. IP GET HF VOLUME Ref. GSM-IP 10.8. (Continued)

Action Reaction Remark

240 98-08901C39-B

98-08901C39-B

5. GLOSSARY

E.1 GENERALThis appendix provides definitions for terms and acronymsused in this document.

Abbreviation DescriptionACK AcknowledgementADC Analog-to-digital converterALC Automatic level controlANSI American National Standards InstituteAOC Automatic output controlASIC Application-specific integrated circuitATE Automatic test equipmentBABT British Approval Board –

TelecommunicationsBGA Ball grid arrayBER Bit error rateBNC A type of connector used with coaxial

cablebps Bits per secondBSC Base station controller (for a network)C/R Card readerCCR Type of miniature RF connectorChebyshev filter A filter with very sharp cutoffCHRONOS Enhanced pendulum ICCLA Cigarette lighter adapterCLK ClockCMOS Complementary metal oxide siliconCNTL ControlCOM Communications (port)CPU Central processing unitCQA Customer quality assuranceCNTL Control (key)CSA California Safety AuthorityCSD Circuit switch dataDAC Digital-to-analog converter

DataTAC A type of Motorola data communications system

DB DecibelDBc Decibels relative to carrierdBm Decibels mean; levels relative to 1 mWDCD Detailed circuit descriptionDCS Digital cellular system (GSM in the

1800MHz band)DDFTM Digital data fast, a technique that

combines an industry-standard error-correction protocol with two compression algorithms (V.42bis and MNP5) to provide data transfer rates up to 33,600bps over a fixed 9,600bps channel

Debounce Protection against feedback voltageDesense Loss of sensitivity from high ambient

noiseDHFA Digital hands free adapterDIN Deutsches Institut Für NormungDISC DiscriminatorDOS Disc operating systemDSC Digital speech controlDTE Data terminal equipment, the user

deviceDTR Data terminal readyDUT Device under testDVM Digital volt meterECC Error correction and compressionEEPROM Electronically erasable, programmable,

read-only memoryEIA Electronic Industries Association (U.S.)EMA Embedded memory access (mode)EMI Electromagnetic interferenceEMMI Electrical man machine interfaceEPC File name suffix for modem

configuration files

Abbreviation Description

241

Glossary

EPROM Erasable, programmable, read-only memory

ERP Effective radiated powerESD Electrostatic dischargeESN Electronic serial numberEV EvaluationEVB Evaluation boardFCC Federal Communications Commission

(U.S.)FET Field effect transistorFIFO First in, first outFNE Fixed network equipmentFPC Flexible printed circuitFracN Fractional division synthesizer ICFRU Field-replaceable unitFSK Frequency shift keyingGaAs Gallium arsenide, a semi-conducting

materialGND GroundGPIB A type of ATE interfaceGPRS General packet radio serviceGSM Global system for mobile

communicationsGTEM Gigahertz transverse electromagneticHCT High-speed CMOS technologyHost The computer platform, or DTEHP Hewlett PackardI/O Input/OutputIB InboundIC Integrated circuit or Industry Canada or

inductor-capacitorInbound Direction of wireless data originating

from the host and/or modem to the fixed network equipment

IP Internet protocolIR InfraredLED Light-emitting diodeLi-ion Lithium ion (battery technology)LLI Logical link identifier; unit IDLNA Low noise amplifierMDC Mobile data communications protocol

(Motorola)ME Mobile equipment, for example, g18MFR Multiple-frequency reuseMNP Microcom networking protocol

Abbreviation DescriptionMPS Maintenance programming softwareNAK Negative acknowledgmentNatSim Native mode simulation (software utility)NCL Native control language (Motorola)NiCad / NiCd Nickel-cadmium (battery technology)NiMH Nickel-metal-hydride (battery

technology)NPN Type of bipolar transistorNSI Network systems integrationNVRAM Non-volatile RAMOB OutboundOEM Original equipment manufacturerop-amp Operational amplifierOSMT Type of miniature RF connectorOutbound Direction of wireless data originating

from the fixed network destined for either the host application(s) or the modem itself

Palmtop A class of small, personal computing devices

PCA Printed circuit assembly (populated board)

PCB Printed circuit board (bare board)PC Card A PCMCIA productPCMCIA Personal Computer Memory Card

International AssociationPCS Personal communication service (GSM

in the 1900MHz band used in North America)

PDA Personal data assistantPDU Packet data unitPIC Personal information communicatorPLL Phase-locked loopp/n Part numberPMIT Packet modem integration testPOST Power-on self testPpm Parts per millionPPP Point to point protocolQFP Quad flat packR&D Research and developmentRAM Random-access memoryRayleigh A measure of multi-path fading depth of

a signalRC Resistor-capacitorRF Radio frequency

Abbreviation Description

242 98-08901C39-B

Glossary

E.2 SHORT MESSAGE SERVICE ABBRE-VIATIONS

The relevant specifications are given in parentheses.(*) indicates a common GSM abbreviation and (-) indicatesa general abbreviation. These abbreviations are oftenprefixed with “TP-”, which refers to “Transport Protocol”.

RFI Radio-frequency interferenceRGxxx Cabling designation numberRLP Radio link protocol, a sophisticated

error-correcting systemRMA Return material authorizationRNC Radio network controllerRPM Radio packet modemRS-232 The EIA standard for a serial data

interfaceRSSI Received signal strength indicatorRTU Radio training utilityRx Receive or receptionSAP0 A specific service access pointSchottky diode A diode with low forward voltage drop

and fast switchingSCR Standard context routingSDK Software developers kitSDU Service data unitSFR Single-frequency reuseSINAD Ratio (measured in dB) of signal to

noise-plus-distortionSMA Sub-miniature connectorSMB Sub-miniature connectorSMS Short message serviceSNR Signal-to-noise ratioSPDT Single pole, double throw (switch)SPI Serial peripheral interfaceSRAM Static random-access memory (static

RAM)TA Terminal adapter, equivalent to DCE, for

example, the g18.TBD To be determinedTE Terminal equipment, equivalent to DTE,

for example, a laptop computer or OEM device.

TNC Industry standard connector typeTransorb Transient absorberTTO Transmitter turn-on timeTuple An element of a database relation,

consisting of an identifier of an entity and its attributes

Tx Transmit or transmissionType III Reference to a PC card form factorUART Universal asynchronous receiver /

transmitterUL Underwriters Laboratories

Abbreviation DescriptionVCC Voltage common collectorVCO Voltage controlled oscillatorVDD Voltage direct drainVpp Voltage peak to peakVSRAM Battery backup voltage for SRAMVSWR Voltage standing-wave ratioWireline Communications over a direct, physical

linkXIP Execute in placeZIF Zero insertion force

Abbreviation DescriptionCM Call Management (*)CS CauSe (-)DA Destination Address (-)DCS Data Coding Scheme (03.40)DI Dialogue Identifier TCAPGMSCA Gateway MSC AddressHLR Home Location Register (*)IMSI International Mobile Subscriber

Identity (*)MAL MSIsdn-ALert (03.40)MMS More Messages to Send (03.40)MR Message Reference (03.40)MS Mobile Station (*)MSC Mobile services Switching Centre (*)MSI Mobile waiting Set Indication (03.40)MSIsdn Mobile Station ISDN number (*)MSM More Short Messages (09.02)MSRN Mobile Station Roaming Number (*)MT Message Type (04.11)MTI Message Type Indicator (04.11)MWS Message Waiting Set (03.40)OA Originating Address (-)OC Operation Code (09.02)PCI Protocol Control Information (-)PDI Protocol DIscriminator (*)

Abbreviation Description

98-08901C39-B 243

Glossary

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)

Abbreviation Description

244 98-08901C39-B

98-08901C39-B

6. INDEX

AAcceptance Analysis on a Sample Data Set 202Address

Selecting Type 106Alternate EMI Reduction Methods

Clock Pulling 204Analog Audio

Audio Downlink (Speaker) 19Audio Uplink (MIC) 18Levels 18Tones 19Voice 19With Hands Free 20Without Hands Free 18

AnsweringVoice Call 76

Antenna 205Cable Assembly 64Cable Routing 205Connections 197Connector 64Considerations 24External Remote 25External Removable 25Field Strengths from the Antenna 205Fixed Devices 25GPS Antenna 64GSM Antenna 63Hardware 63Installation Safety xviiInteractions 205Internal 24Performance 24Portable Devices 24Safety 24Systems 24Test Methods 25

Application SoftwareNetwork Configuration 70Software Driver Configuration 70Testing 70

AT Command Listing 80AT+CAOC, Charge Advice 81AT+CBAND, Changing Band 136AT+CBAUD, Setting the Baud Rate 137AT+CBST, Selecting Bearer Service Type 107AT+CCFC, Call Forwarding Number Conditions 82AT+CCWA, Call Waiting 83AT+CEER, Extended Error Report 121AT+CESP, Entering SMS Block Mode 134AT+CGACT, PDP Context Activation/Deactivation

Request 143AT+CGATT, GPRS Attach/Detach Request 144AT+CGCLASS, GPRS MS Class 140AT+CGDCONT, Defining the PDP Content 141AT+CGMI, Requesting Manufacturer Identification 108AT+CGMM, Requesting Model Identification 109AT+CGMR, Requesting Revision Identification 109AT+CGPADDR, Showing the PDP Address 139AT+CGPRS, GPRS Coverage 138AT+CGQMIN, Quality of Service Provider 142AT+CGQREQ, Defining a Requested Quality of Service

Profile 145AT+CGQREQ, Modifying a Requested Quality of

Service Profile 145AT+CGQREQ, Removing a Requested Quality of

Service Profile 145AT+CGSN, Requesting Product Serial Number Identifi-

cation 110AT+CHLD, Call Related Supplementary Services 84AT+CHUP, Hanging Up Calls 110AT+CIMI, Requesting International Mobile Subscriber

Identity (IMEI) 146AT+CIP, IP Primitive Over AT Command 149AT+CIPE, ENABLE+CIP AT Command 149AT+CKPD, Keypad Control 123AT+CLCC, List Current Calls 89AT+CLCK, Facility Lock 91AT+CLIP, Calling Line Identification Presentation 92AT+CLIR, Call Line Identification Restriction 93AT+CMEC, Mobile Equipment Control Mode 130AT+CMEE, Report Mobile Equipment 94AT+CMER, Mobile Equipment Event Reporting 131AT+CMGD, Deleting SMS Message 111AT+CMGF, Message Format 113

245

Index

AT+CMGL, Listing Messages 114AT+CMGR, Reading Messages 115AT+CMGS, Sending an SMS Message 95AT+CMGW, Writing Messages 134AT+CMOD, Calling Mode 125AT+CMSS, Send Message from Storage 153AT+CMUX, Multiplexing Mode 172AT+CNMA, DTE Confirming the Previous Message 135AT+CNMI, New Message Indications to TE+CNMI 128AT+CNUM, Subscriber Number 96AT+COPS, Operator Selection 97AT+CPAS, Phone Activity Status 115AT+CPBF, Finding Phone Book Entries 132AT+CPBR, Reading Phone Book Entries 116AT+CPBS, Selected Phone Book Memory Storage 99AT+CPBW, Writing Phone Book Entries 101AT+CPIN, Enter Pin 103AT+CPMS, Preferred Message Storage 117AT+CPOL, Preferred Operator List 148AT+CPWD, Changing the Password 151AT+CR, Service Reporting Control 126AT+CRC, Cellular Result Codes 127AT+CREG, Network Registration 105AT+CRLP, Radio Link Protocol 126AT+CRSM, Restricting SIM Access 147AT+CRTT, Selecting the Ring Tone 150AT+CSCA, Service Center Address 118AT+CSCB, Select Cell Broadcast Message Types 162AT+CSCR, SIM Card Reader 169AT+CSCS, Selecting TE Character Set 119AT+CSMP, Set SMS SIM Parameters 157AT+CSMS, Selecting the Message Service 120AT+CSQ, Signal Quality 121AT+CSTA, Selecting Type of Address 106AT+CSVM, Set VoiceMail Parameters 159AT+CTFR1, Diverting an Incoming Call to the Voice

Mail 135AT+FCLASS, Selecting a Mode 124AT+GCAP, Requesting Complete Capabilities List 124AT+IPR, Setting and Saving the Baud Rate 171AT+MCELL, Motorola Cell Description 169AT+MCSAT, Motorola Control SMS Alert Tone 166AT+MCWAKE, DTE Wake Line Control Command 153AT+MECC, Motorola Extended Characters Check 168AT+MFS, Motorola Frequency of Search 161AT+MMGA, Changing the Message Attributes 155AT+MMGL, Message List 154AT+MMGR, Read Message 154AT+MSCTS, Motorola Sleep CTS Control 155AT+MTCTS, CTS Line Test Command 152AT+MTDTR, DTR Line Test Command 152AT+PT42 172ATD, Dialing 80Fax AT Commands 151

AT Commands 73Answering a Voice Call 76AT Command Listing 80Basic 45Establishing a Voice Call 75Establishing GPRS PDP Context 78Feedback from the System 74Finding a Phone Book Entry 76Phone Book Function 77PIN and PUK Code Entry 73Reading a Phone Book Entry 77Sending an SMS in PDU Mode 78Writing a Phone Book Entry 77

AT+CAOC, Charge Advice 81AT+CBAND, Changing Band 136AT+CBAUD, Setting the Baud Rate 137AT+CBPF, Finding Phone Book Entries 132AT+CBST, Selecting Bearer Service Type 107AT+CCFC, Call Forwarding Number and Conditions 82AT+CCWA, Call Waiting 83AT+CEER, Extended Error Report 121AT+CESP, Entering SMS Block Mode 134AT+CGACT, PDP Context Activation/Deactivation

Request 143AT+CGCLASS, GPRS MS Class 140AT+CGDCONT, Defining the PDP Content 141AT+CGMI, Requesting Manufacturer Identification 108AT+CGMM, Requesting Model Identification 109AT+CGMR, Requesting Revision Identification 109AT+CGPADDR, Showing the PDP Address 139AT+CGPRS, GPRS Coverage 138AT+CGQMIN, Quality of Service Provider 142AT+CGSN, Requesting Product Serial Number

Identification 110AT+CHLD, Call Related Supplementary Services 84AT+CHUP, Hanging Up Calls 110AT+CIMI, Requesting International Mobile Subscriber

Identity (IMEI) 146AT+CIP, IP Primitive Over AT Command 149AT+CIPE, ENABLE+CIP AT Command 149AT+CKPD, Keypad Control 123AT+CLCC, List Current Calls 89AT+CLCK, Facility Lock 91AT+CLIP, Calling Line Identification Presentation 92AT+CLIR, Calling Line Identification Restriction 93AT+CMEC, Mobile Equipment Control Mode 130AT+CMEE, Report Mobile Equipment 94AT+CMER, Mobile Equipment Event Reporting 131AT+CMGD, Deleting SMS Message 111AT+CMGF, Message Format 113AT+CMGL, Listing Messages 114AT+CMGR, Reading Messages 115AT+CMGS, Sending an SMS Message 95AT+CMGW, Writing Messages 134AT+CMOD, Calling Mode 125

246 98-08901C39-B

Index

AT+CMSS, Send Message from Storage 153AT+CMUX, Multiplexing Mode 172AT+CNMA, DTE Confirming the Previous Message 135AT+CNMI, New Message Indications to TE+CNMI 128AT+CNUM, Subscriber Number 96AT+COPS, Operator Selection 97AT+CPAS, Phone Activity Status 115AT+CPBR, Reading Phone Book Entries 116AT+CPBS, Selected Phone Book Memory Storage 99AT+CPBW, Writing Phone Book Entries 101AT+CPIN, Enter Pin 103AT+CPMS, Preferred Message Storage 117AT+CPOL, Preferred Operator List 148AT+CPWD, Changing the Password 151AT+CR, Service Reporting Control 126AT+CRC, Cellular Result Codes 127AT+CREG, Network Registration 105AT+CRLP, Radio Link Protocol 126AT+CRSM, Restricting SIM Access 147AT+CRTT, Selecting the Ring Tone 150AT+CSCA, Service Center Address 118AT+CSCB, Select Cell Broadcast Message Types 162AT+CSCR, SIM Card Reader 169AT+CSCS, Selecting TE Character Set 119AT+CSMP, Set SMS SIM Parameters 157AT+CSMS, Selecting the Message Service 120AT+CSQ, Signal Quality 121AT+CSTA, Selecting Type of Address 106AT+CSVM, Set VoiceMail Parameters 159AT+CTFR1, Diverting an Incoming Call to the Voice Mail

135AT+FCLASS, Selecting a Mode 124AT+GCAP, Requesting Complete Capabilities List 124AT+IPR, Setting and Saving the Baud Rate 171AT+MCELL, Motorola Cell Description 169AT+MCSAT, Motorola Control SMS Alert Tone 166AT+MCWAKE, DTE Wake Line Control Command 153AT+MECC, Motorola Extended Characters Check 168AT+MFS, Motorola Frequency of Search 161AT+MMGA, Changing the Message Attributes 155AT+MMGL, Message List 154AT+MMGR, Read Message 154AT+MSCTS, Motorola Sleep CTS Control 155AT+MTCTS, CTS Line Test Command 152AT+MTDTR, DTR Line Test Command 152AT+PT42 172ATD, Dialing 80Attached Peripherals Primitives 228Audio Circuit Considerations 17

Analog Audio Levels 18Analog Audio With Hands Free 20Analog Audio Without Hands Free 18Digital Audio 17

Audio Connections 197Audio Downlink (Speaker) 19

Audio Uplink (MIC) 18

BBand Changing 136Band Selections 197Basic AT Commands 45Basic Model Overview 7

g18 Board Only - Horizontal 8g18 DV Slim 7g18 DVG Slim 8

Basic Operations 29Commencing Voice Communication 30Enabling Cell Broadcast (CB) Reception 30Making a CSD - Data Call 30Making a Voice Call 29Receiving a Data Call 30Receiving a Voice Call 29Setting Up the g18 in CSD Mode 31

Baud RateSaving 171Setting 171

Baud Rate Setting 137Bearer Service Type

Selecting 107Binary Data

Receiving via SMS 35Sending via SMS 35

CCable Assembly

Antenna 64Cable Routing

Antenna 205Calibration Tools and Equipment 72Call Control Interface Primitives 216

Background 216Call Restrictions 216

Call Forwarding 32Conditions 82Number 82

Call Related Supplementary Services 84Call Status Indication Primitives 216Call Waiting 32, 83Calling Line Identification Presentation 92Calling Line Identification Restriction 93Calling Mode 125Capabilities List 124Card Reader

SIM 169Cellular Result Codes 127Channel Interference

Probability of 203

98-08901C39-B 247

Index

Characters CheckExtended 168

Charge Advice 81Class Indicator Primitives 210Clock Pulling 204Commands

AT 73Basic AT 45CTS Line Test 152DTE Wake Line Control 153DTR Line Test 152, 172ENABLE +CIP AT 149Error Correction and Compression 49Fax AT 151Fax Class 1 49GPRS 58IP Primitive Over AT 149V.25TER Used With GSM 53

Conference Calls 32Configuration Setup and Audio Routing in g18 27Configuring

Modem in WinFax 43Connecting

3788 Handset to the g18 26Connections

Antenna 197Audio 197Customer 197Power 197RS232 197SIM 197

ConnectorAntenna 64

Connector DescriptionEV Board Issue P4 174EV Board Issue P5 177

Country Requirements xvCSD - Data Call

Making 30CTS Line Test Command 152Customer Connections 197

Dd15 Differences from g18 9

AT Commands 10Data Options 9General 9GPRS ST Commands 12Mechanical 9Power 9

Data CallReceiving 30

Data Communication 28CSD 29GPRS 28

Data Levels 21Data Port Considerations 21

Data Levels 21DTR Line and DCD Line 22Setting the Baud Rate 22

DescriptionCell 169

Desense 199Acceptance Analysis on a Sample Data Set 202Antenna 205Definition 199Measurement Techniques 200Methods of Controlling Emissions 203Noise Sources 199Performance Goals 201Prediction of Sources 202Receiver Susceptibilities 200RF Network Issues 204Scenarios 203Summary 205Testing 70

Design Considerations 13Antenna Considerations 24Audio Circuit Considerations 17Connecting the 3788 Handset to the g18 26Data Port Considerations 21ESD Considerations 23GPS Considerations 26Mechanics - Mounting the g18 25Power Supply Considerations 13SIM Card Considerations 23

Developer’s Kit 64Development and Service Aids 4Development Test Environment 3Diagnostic Utility

Equipment Test Setup 72Quality Assurance Testing 71Testing 71

Digital Audio 17DIP Switch Settings 198Display Indicator Primitives 215DSC BUS IP Primitive Over AT Services +CIP 207DTE Wake Line Control Command 153DTR Line and DCD Line 22DTR Line Test 152, 172

EEMI

Reduction Methods 204Testing 70

248 98-08901C39-B

Index

EmissionsMethods of Controlling 203

Enable IP Over AT Services +CIPE 207Enabler Functions

Testing 69Enabling Cell Broadcast (CB) Reception 30Engineering Support

Integrating 4Enter Pin 103Environmental

Issues 5Specifications 188

EquipmentModem Test 5Traditional Shop 5Wireless Verification Equipment 5

Equipment Test Setup 72Calibration Tools and Equipment 72Loop-back Test 72Modem Test Setup 72

Error Correction and Compression Commands 49Error Messages

SMS 36Error Report

Extended 121ESD

Considerations 23Handling Precautions 5

ETSI 07.05 Standard (SMS) 55ETSI 07.07 Standard 49European Union and EFTA xvEV Board Issue P4 173

Connector Description 174Jumper Description 175

EV Board Issue P5 176Connector Description 177S3 Dip Switch Description 179

Extended Error Report 121External Antenna 25External Remote Antenna 25

FFacility Lock 91Fastening

DIN Units 26Units with Housing 26

FaxAT Commands 151Class 1 Commands 49Communication 29Sending 43

FeedbackSystem 74

Field Strengths from the Antenna 205Field-Testing 4Final Assembly Test 71Final Test Environment 4Fix Dialing Phone Book 44Fixed Devices 25Fixed-Mount Usage 25Flow Control Set to Hardware Flow Control 31

Receiving Data 31Sending Data 31

Flow Control Set to None 32Receiving Data 32Sending Data 32

Flow Control Set to Xon/Xoff 31Receiving Data 32Sending Data 31

Gg18

PC Loader Application 181Setting Up in CSD Mode 31

g18 Current Consumption 13Turning the Unit On or Off 14Turning the Unit On or Off Using the ON/OFF Pin 14Turning the Unit On Using the TS Pin 14

g18 Differences from d15 9AT Commands 10Data Options 9General 9GPRS ST Commands 12Mechanical 9Power 9

g18 DV Board Only - Horizontal 8g18 DV Slim 7g18 DVG/Slim 8g18 Evaluation Board 173

EV Board Issue P4 173EV Board Issue P5 176

g18 PC Loader Application 181Options 181

g18 Type Certification Identifications xviiGeneral Precautions 5Generate DTMF Signalling Primitives 218GPRS

Attach/Detach Request 144Commands 58Coverage 138MS Class 140PDP Context 43, 78

GPSAntenna 64Considerations 26

GSM Antenna 63

98-08901C39-B 249

Index

HHanging Up Calls 110Hardware 63

Antennas 63Designing Platform 3Developer’s Kit 64Developing and Validating 3Host Interface 63Vendor Contacts 64

Hardware IntegrationSpecific Tests 69Testing 69Testing Enabler Functions 69

Hook-switch Status Indicator Primitives 219Host Interface 63

Interface Cable 63Modem I/O Connector 63

IIdle SIM Card Notification Primitives 223Installing

Modem Driver 43Integration

MUX 59MUX Requirements 59

Interface Cable 63International Mobile Subscriber Identity 146IP Over AT Commands List 207IP Primitives CIP Specifications 210

Attached Peripherals Primitives 228Call Control Interface Primitives 216Call Status Indication Primitives 216Class Indicator Primitives 210Display Indicator Primitives 215Generate DTMF Signalling Primitives 218Hook-switch Status Indicator Primitives 219Idle SIM Card Notification Primitives 223IP_HF_AUDIO_STATUS_IND 229IP_LOW_VOLTAGE_IND 231IP_SET_RING_LEVEL_CNF 230IP_SET_RING_LEVEL_REQ 230Microphone Mute Primitives 221Phone Book Related Primitives 213Power Down Primitives 213SEEM Interface Primitives 221SIM Card Activation Notification Primitives 224SIM Card Deactivation Notification 223SIM Card Security Notifications 224

IP Primitives Supported by CIP 209IP_HF_AUDIO_STATUS_IND 229IP_LOW_VOLTAGE_IND 231IP_SET_RING_LEVEL_CNF 230

IP_SET_RING_LEVEL_REQ 230

JJumper Description

EV Board Issue P4 175Jumper Settings 198

LLanguage Packs 194List Current Calls 89Loop-back Test 72

Getting Started 72Measuring Additional Parameters 72

MManufacturer Identification, Requesting 108Measurement Techniques 200

Alternate Measurement Method 201Packet Modem Integration Tester (PMIT) 200Preparing the Device Under Test 201

MechanicsFastening DIN Units 26Fastening Units with Housing 26Fixed-Mount Usage 25

MessageAttributes 155Confirming Previous 135Format 113List 154Listing 114Model 2Read 154Reading 115Send from Storage 153Writing 134

Message ServiceSelecting 120

Message TypesCell Broadcast 162

Methods of Controlling EmissionsAlternate EMI Reduction Methods 204Shielding Approach 203

MIC 18Microphone Mute Primitives 221Mobile Equipment Control Mode 130Mobile Equipment Event Reporting 131Mode

Selecting 124Model Description

Basic Overview 7d15 and g18 Differences 9

250 98-08901C39-B

Index

General 7Introduction 7

Model Identification, Requesting 109Modem

Configuring in WinFax 43I/O Connector 63Installing Drivers 43Test Equipment 5Test Setup 72

Modem Communication Modes 27Data Communication 28Fax Communication 29SMS Communication 29Voice Communication 27

MUX Integration 59Architecture 61Close Service 59Data Transfer 59Open Service 59Requirements 59Supported Protocol Services 60System Behavior 60Two Channel Limitation 59

Mux IntegrationUser APIs 62

MUX ServiceClose 59Open 59

NNetwork

Configuration 70Registration 105

Noise SourcesDesense 199

North American GSM Type Certification xvi

OOEM Service Depot Repair 71Operator Selection 97

PP4 Evaluation Board

Connector Description 174Jumper Description 175

P5 Evaluation BoardConnector Description 177Dip Switch Description 179

Packet Modem Integration Tester (PMIT) 200Data Presentation 200

ParametersSet SMS SIM 157Set VoiceMail 159

PartsRequirements 4

PasswordChanging 151

PDPAddress 139Content 141Context Activation/Deactivation Request 143

PerformanceSpecifications 188

Performance Goals 201Emission Level Goals 202Radio Performance Capabilities 201

Phone Activity Status 115Phone Book

Finding an Entry 76, 132Function 77Reading an Entry 77, 116Related Primitives 213Writing an Entry 77, 101

Physical Specifications 188PIN Code

Entry 73Number 44

PMIT Data Presentation 200Portable Antenna

External Antenna 25Portable Devices 24

External Remote Antenna 25Internal Antenna 24

Power Connections 197Power Down Primitives 213Power Supply

Losses 13Options 3

Power Supply Considerations 13g18 Current Consumption 13How and When to Wake Up the Unit 16Power Supply Losses 13

PrecautionsESD Handling 5General 5

Prediction of Sources 202Desense Scenarios 203Probability of Channel Interference 203

Preferred Message Storage 117Preferred Operator List 148Preparing the Device Under Test 201Primitives

Attached Peripherals 228Call Control Interface 216Call Status Indication 216

98-08901C39-B 251

Index

Class Indicator 210Display Indicator 215Generate DTMF Signalling 218Hook-switch Status Indicator 219Idle SIM Card Notification 223IP Supported by CIP 209Microphone Mute 221Phone Book Related 213Power Down 213Request/Confirm 209SEEM Interface 221SIM Card Deactivation Notification 223SIM Card Security Notifications 224Unsolicited 209

Problem Resolution 71Product

Approving 4Field-Testing 4Installing 4Planning 1Testing 4

Product Serial Number Identification 110Protocol Services

Supported 60PUK Code Entry 73

QQuality Assurance Testing 71Quality of Service Profile

Defining 145Modifying 145Removing 145

RRadio

Link Protocol 126Performance Capabilities 201

Receiver Susceptibilities 200Receiving

Binary Data via SMS 35SMS 34SMS CSD Mode Wave Forms 35

Receiving DataFlow Control Set to Hardware Flow Control 31Flow Control Set to None 32Flow Control Set to Xon/Xoff 32

Regulatory ApprovalObtaining 3

Regulatory ComplianceTesting 70

Regulatory Requirements xivCountry Requirements xvEuropean Union and EFTA xvFull-Product Certification xvg18 Type Certification Identifications xviiNorth America GSM Type Certification xviSafety xvii

Remote Diagnostic FunctionalityDefining 2

Report Mobile Equipment 94Request/Confirm Primitives 209Requirements

Parts and Tools 4Resource Assistance 4Result Codes

Cellular 127Revision Identification

Requesting 109RF Network Issues 204Ring Tone

Selecting 150

SS3 Dip Switch Description

EV Board Issue P5 179Safety xvii

Antenna Installation xviiUser Operation xvii

Sample Data SetAcceptance Analysis 202

SearchFrequency 161

SEEM Interface Primitives 221Sending

Binary Data via SMS 35Fax 43SMS 32, 95SMS Fax 43SMS in CSD Mode 34SMS in PDU Mode 32, 78SMS PDU-Mode Waveforms 34

Sending DataFlow Control Set to Hardware Flow Control 31Flow Control Set to None 32Flow Control Set to Xon/Xoff 31

Service Center Address 118Service Provider Quality 142Service Reporting Control 126Service Strategy

Defining 2Shielding Approach 203

Benefits 204Components of Shield Design 204

Signal Quality 121

252 98-08901C39-B

Index

SIMConnections 197Restricting Access 147

SIM CardActivation Notification Primitives 224Deactivation Notification 223Security Notifications 224Support 23

Sleep ControlCTS 155

SMSBlock Mode 134Deleting a Message 111Error Messages 36Sending in PDU Mode 78

SMS Alert ToneControl 166

SMS Communication 29Block Mode 29PDU Mode 29Text Mode 29

Software Driver Configuration 70Software Interface 27

Basic AT Commands 45Basic Operations 29Call Forwarding 32Call Waiting 32Conference Calls 32Error Correction and Compression Commands 49ETSI 07.05 Standard (SMS) 55ETSI 07.07 Standard 49Fax Class 1 Commands 49GPRS Commands 58Modem Communication Modes 27Sending an SMS 32Sending and Receiving Data in Different Flow Controls

31V.25TER Commands Used with GSM 53

Source Antenna 3Speaker 19Specific Tests

Hardware Integration 69Specifications 187

Environmental 188Performance 188Physical 188

Subscriber Number 96Supporting Application Software 3System Feedback 74

TTE Character Set

Selecting 119

Testing 69Desense 70Diagnostic Utility 71EMI 70Hardware Integration 69Product 4Stages 69

Testing StagesApplication Software 70Desense and EMI 70End User Problem Resolution 71Final Assembly 71Hardware Integration 69OEM Service Depot Repair 71Regulatory Compliance 70

Tones 19Tools

Requirements 4Traditional Shop Equipment 5Turning the Unit On or Off 14

Using the ON/OFF Pin 14Using the TS Pin 14

UUnsolicited Primitives 209Usage Model

Developing 1

VV.25TER Commands Used With GSM 53Vendor Contacts 64Voice 19

Call Answering 76Call Establishing 75

Voice CallMaking 29Receiving 29

Voice Communication 27Commencing 30Configuration Setup and Audio Routing in g18 27Voice Connectivity 27

Voice MailDiverting an Incoming Call 135

WWaking Up the Unit 16WinFax

Configuring Modem 43Wireless Verification Equipment 5Writing 77

98-08901C39-B 253

Index

254 98-08901C39-B

SCHEMATIC DIAGRAMS,

LAYOUTS AND

PARTS LISTS

ContentsEach 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.

OL 79B02965C18-O

J124

J123

8486452t01_p4

SHOWN FROM SIDE 1OL 79B02965C16-O

C1

C2

C3

C4

C5

C6

C8

C9

C11

C12

C13

C14

C15

C24

C25C

26

C27

C28

C29

C30

C32

C33

C34

C35

C36

C37

C38

C39

C40

C41

C42

C43

C44

C45

C46

C47

C48

C49

C50

C51

C52

C60

C62

C68

C71C72

C73

C74

C75

C76

C77

C78

C79

C80

C81

C82

C83

C84

C85

C86

C87

C88

C89

C90

C91

C92

C93

C94

C95

C96

C97

C98

C99

C10

0

C10

1

C10

2

C103C10

4

C10

5

C11

0

C112

C11

4

C11

5

C11

6

C11

7

C9192 C9206

C93

65

C93

78

C9386

C94

09

C95

36

C9537

C95

38

C9539

C9540

C95

42

C9543

C95

44

C95

45

C9546

C95

49

C95

50

C95

51C95

52

C9553

C95

54

C95

55

C9556

C9559

C9560

C9561

C9563

C9564

C9565

C95

67

C9569

C95

70

C9573

C95

74

C95

75

CR1 CR2CR3CR4CR5CR6CR7CR8CR9 CR10CR11

D1

D3

F1

J1J2

1 J3

J4

51

69

J5

8

1

J10

J12

J13

J111

15

16 2

1

J114

8

1

J115

J118

J120

J121

J122

J125

J126

J127

L1

L2

L3

L4

L5L6

L7

L10

L12

L14

L15

L16

LE

D

P1

P2

P3 P5

P6

P7

P8

P9

P10

P12

Q38

R2

R3

R4

R15

R17

R18

R19

R21

R22R23

R24

R25R26

R27

R28

R29

R30

R31

R32

R33

R35

R38

R50

R52

R53

R55

R56

R57

R58R59

R60

R63

R77

R78

R83

R84

R10

56

R10

57

R10

68

R1069

R11

04

R24

73

R2518

R25

19

R25

21R

2527 R2550

R2551R2552

R25

53

R2564

R2565

R2569

R2575

R25

87

R25

88

R2595

S1

S2

SH1

1

2

SIM

SW2

U3

U4

U5

U978

U979

U980

U98

1

U985

U986

U98

7

U988

R25

72

OL 79B02965C17-OSHOWN FROM SIDE 2

OL 79B02965C19-O

8486452t01_p4

R25

89

U983

R25

71

C7

C59

C61

C70

C106

C111

C113

C9185

C91

90

C92

01

C9204

C92

05

C92

08

C92

15

C9219

C92

28C

9241

C9541

C95

47

C95

48

C9558

C9562

C9566

C9568

C9571

C9572

C95

76

C9577

C95

78

C9579

C95

80

C95

81

D2

D4

D5

L8

L11

L13

L17

Q3

Q4 Q11Q14

Q15

Q16

Q17

Q18Q19Q20Q21Q22Q23

Q25

Q26

Q27

Q28

Q29

Q30 Q32

Q34 Q35

Q36Q37

R20

R36

R61

R62

R64

R65

R66

R67

R68

R69R70

R79

R82

R85

R1098

R24

68

R24

69R

2470

R24

71

R2554

R2556

R2557

R25

58

R25

59

R2560

R25

61

R2563

R25

66 R2568

R25

70

R2573

R2574

R2576

R2577

R25

78

R2579

R2580

R2582

R2583

R25

85

R25

86

R2590

R25

93

R25

94

R2596

R2597

R25

98

U982

U984

U98

9

U990

U991

U992

VR2

VR3

VR4

VR5 VR6

VR7

VR8

VR9

VR

10

RS232_RTS

RXD_UART_2

SPKR_OUT

SPK_GND

STNDBY

TXD_UART_2

VCC

Interface Connectors

Audio & Voltage REGs

79B02963C87-O

SHEET 1 OF 6

5V_Data

AUDIO_PA_12V

Analog_Audio_In

Analog_Audio_Out&Power_On_Off

DC_to_DC_12V

DHFA_MIC_IN

DHFA_SPKR_OUT

DSC_Enable

GPS_1PPS_LED

GPS_PWR

MIC_In

RS232_CTS

RS232_DCD

RS232_DSR

RS232_DTR

RS232_RI

GPS_1PPS_STANDALONE

GPS_PWR MIC_In

RS232_CTS

RS232_DCD

RS232_DSR

RS232_DTR

RS232_RI

RS232_RTS

RXD_UART_2

SPKR_OUT

STNDBY

TXD_UART_2

VCC

2.7V

2.7V_IN_SHEELD

DSC_Enable

DSC_Enable

DHFA_MIC_IN

DHFA_SPKR_OUT

DHFA_MIC_IN

DHFA_SPKR_OUT

2.7V_IN_SHEELD

2.7V

2.7V_IN_SHEELD

5V_Data

AUDIO_PA_12V

Analog_Audio_In

Analog_Audio_Out&Power_On_Off

DC_to_DC_12V

DHFA_MIC_IN

DHFA_SPKR_OUT

DSC_Enable

Dc_to_Dc_12V

Analog_Audio_In

GPS_PWR

VCC

2.7V

5V_Data

AUDIO_PA_12V

SPKR_OUT

2.7V

AUDIO_PA_12V

SPKR_OUT

GPS_PWR

Dc_to_Dc_12V5V_Data

VCC

Analog_Audio_In

2.7V_IN_SHEELD

R30

180K

100NF

C12

R38

C47

1K

1uF

2

3

1

8

4

2.7Vdc REG

Must be SHEELDED

SHEET 2 OF 6

79B02963C87-O

AGND

U3

MC33202DR2

10n

C11

C14

2.2nR29 560

560

R28

R27

560

R26

560R25

560

51KR2

C13 2.2n

R24 560

15K

R19

120n

L6

120n

L5

RES_10KR33

RES_1000

R50

120n

L4

120n

L2

R18

15K

C15 2.2NF

C52 680PF

R21

2.4K

C1

0

R4

18.2KR52

22u

C8

10n

C2

1uF

33p

C32

33p

C34

33p

C35

33p

C33

1uF

C44

C3

33p

C38 33p

33pC39

33p

C40

33p

C41

33p

C46

33p

C45

C43

33p

C25

33p

C42

33p

33pC24

33p

C36

33p

C37

33p

C27

33p

C26

33p

C29C30

C28

33p

33p

7

8

4

33p

C68

6

5

7

8

4

U4

MC33202DR2

6

5

DGND

AGND

U3MC33202DR2

C9553

33p

C111

33p

AGND DGND

33p

120n

C110

100n

C77

L10

C105

AGND

33p

120n

U987

C4

AGND

AGND

AGND AGND

22u

1u

C9

1uF

C6

1uF

C5

C49

33p

C48

33p

33p

C50 33p

C51

VCC

10u

C62

R77

47K

39K

R78

GN

D3

6

GN

D4

7

IN1

OFF_4

OUT8

SET5

MAX603ESA

U5

GN

D1

2

GN

D2

3

U4

MC33202DR2

2

3

1

8

4

22K

R23

22K

R22

5V_DataR3

51K

1.8K

R2564

1u

C9540

C9550

33.p

C9549

33.p

SH1SHIELD

1

DGND

AGND

MIC_BAIS

VAG

VAG2

VAG2

VAG

VAG

MIC_BAIS

AGND

1.u

C9561

C9567

33p

AGND

vcc=8V_AUDIO,vee=AGND6

5

7

8

4

C9554

33p

MC33072

U988

100n

C9208

5.6K

R1104

R1056

15K

R1068

39.KC9185

3.3u

47.u

C9190 C9205

0.1u

100n

C9204

R2588

3.9K

DGND

1.u

C9560

R2587

2.4K

1.uC9555

AGND120n

AGND AGND

AGND

AGND

AGND

AGND

L15

0.

R2473

100p

C9228

R1057

15K

39.K

R1069

C9206

100n

R2553

15K

R2470

0. 0.

R2468

R2471

0.0.

R2469

C9219

1n

8.2K

R1098

RR1

VP10

C9201

330n

NC59

NC618

NC717

NC816

15NC9

NINV19

OUT13

OUT28

INV12

M_SS11

NC12

NC1014

NC1113

NC24

NC36

NC47

TDA1519CTD

U982

GN

D1

20

GN

D2

5

GN

D3

21

880_1800MHZ

C9535

1IN

2

OUT

R2550

15K

15K

R2552

15K

R2551

C9192

330n

8V_AUDIO

C9409

330n

AUDIO_PA_12V

C9378

100n

100p

C9241

C9215

0.

R2590

10n

15K

R2575

AGND

AGND

AGND

8V_AUDIO

R2563

8.2K

21

AGND AGND

AGND

AGND

AGND

AGNDDGND

RES_47K

R32

C117

33p

C116

33p

120n

470K

L12

AGND

AGND

AGND

AGND

R15

C76

100n

C104

33p

100n

C75 C103

AGND

AGND

AGND

AGND

AGND

AGND

AGND

AGND

33p

R84 33.K

AGND

560K

470K

R31

Analog_Audio_Out&Power_On_Off

2.7V_IN_SHEELD

SPKR_Out

MIC_In

R17

INV

NINV

SPK_GNDSPK_GND

SPK_GND

DHFA_MIC_IN

DHFA_SPKR_OUTDHFA_SPKR_OUT

STNDBY

RR

2.7V_IN_SHEELD

MIC_BAIS

2.7V_IN_SHEELD

Analog_Audio_Out&Power_On_Off

2.7V_IN_SHEELD

2.7V_IN_SHEELD

2.7V_IN_SHEELD

2.7V

VAG

VAG2

Analog_Audio_In

R62

CR11

Q11

270

R2570

Q25

270

DSC_Enable

RXD_UART_2

TXD_UART_2

8.2K

270

1PPS

CR9

5V_Data

5V_Data

GPS RXD on GPS models

GPS TXD on GPS models

GPS 3Volts REG

Voltage to MIC & AMP

5V regulator for

RS-232 Driver

13mmx13mm PCB

Heatsink is needed

Must be SHEELDED

To be Placed

In the SHEELED

79B02963C87-O

SHEET 3 OF 6

Voltage to MIC & AMP

DSC_EN

5V_Data

Q18

Q4

Q19

Q20

Q21

Q22

Q23

LED-2

2

LED-1

1

4.7K

R79

U984

470K

R66

DGND

RES_10K

R68 3904L

Q16

22.u

L14

3

D1

DGND

VCC

S2

1

2

3

F1

AMPVOLTAGE

J3-2

2

J3-3

J3-1

1

33pC106

4.7uC70

R85 0

L8

120n

1

IN

2

OUT

AGND

AGND DGND

C9536

880_1800MHZ

100.K

R2527

20.K

R2521

0.

R2519

2SHUTDOWN

3

R2518

110.K

LP2951C

U978

5V_TAP6

ERROR5

FEEDBACK7

GN

D4

INPUT8

OUTPUT1

SENSE

AUDIO_PA_12V8V_AUDIO

C9365

3.3u

C9386

C9542

DGND

100n

4NC

3ON_OFF*

1VIN

5VOUT

DGND

47.u

DGND

LP2981

U981

2

GND

R2589

221K

VR10

2.

MC33072

U992

2

3

1

8

4

100.u

C9564

100.u

C9563

GN

D7

REF5

SHDN4

V+2

5V_Data

MAX771ESA

U983

AG

ND

6

CS8

EXT1

FB3

D2

33p

C115

AGND DGND

C114

33p

C9538

100.u

U980

LP2957IS

ERROR5

GND

3

INPUT1

OUTPUT2

SHUTDOWN4

DGND

DGND

DGND

100.n

C9548

0.1

R2554 C9547

100.n

DGND

100.u

DGND

DGND

C9537

C9539

68u

Q27

C9579

VCC

DGND

DGND

100.n

DGND

220.n

C9569

D5

D4

R2594

0.

R2593

470.K

Q38

2.4K

R2596

R2598

R2597

22.K

3904L

Q15

R63

270

Q3

CR10

GPS_RXD

270

R60

R61

DCD

CR8 CR7

DTR

270

R59

270

DSR

CR6

R58

270

R57

270

RTS

CR5

CTS

CR4

R56

270

R55

RI

CR3

CR2

GPS_TXD

270

R53

DGND

VCC

CR1

R64

470K

R65

470K

2.4K

R67

Q14

3906L

AUDIO_PA_12V

VCC

DC_to_DC_12V

SENSE

5V_Data

RS232_DCD

RS232_DTR

RS232_DSR

RS232_RTS

RS232_CTS

RS232_RI

GPS_1PPS_LED

VCC

GPS_PWR

DIN Connector F.

GPS Connector

DIN Connector M.

DNP

Jumper ON = SoftGSM Mode

d-10 To HOSTd-15 To HOST

GPS RXD on GPS models

GPS TXD on GPS models

for CSD call/PDP context indicator

Custom Definition

VCC(3.0-6Vdc)

To HOST

79B02963C87-O

SHEET 4 OF 6

J121-24

24

DGND

J121-33

33

J121-36

36

J121-31

31

J121-34

34

J121-29

29

J121-32

32

J121-28

28

J121-30

30

EXT_B+ VCC

J121-26

26

D3

J4-30

30

AGND

VCC

AUDIO_PA_12V

2.7V

J4-28

28

J4-29

29

J4-26

26

J4-27

27

J4-24

24

J4-25

25

22

J4-23

23

J4-21

21

J4-22

J4-19

19

J4-20

20

J4-17

17

J4-18

18

J4-15

15J4-16

16

J4-13

13

J4-14

14

J4-11

11

J4-12

12

J4-9

9

J4-10

10

J4-7

7

J4-8

8

22

J121-25

25

21

J121-23

23

J121-22

20

J121-19

19

J121-21

18

J121-17

17

J121-20

2

3

4

J121-15

15

J121-18

Jack_4pin

J122

1

DGND

HandsFree_Select

470u

C9559

R2572

56.K56.K

Q35

R2571

DGND

HandsFree_Select

Q34

2

R2557

100.K

1

P10-2

13

J121-16

16

P10-1

J121-12

12

J121-14

14

J121-13

11

J121-10

10

9

J121-8

8

J121-11

7

J121-6

6

J121-9

J121-1

1

J121-5

5

J121-7

J121-3

3

J121-4

4

AGND

VCC

J121-2

2

J125

-26

J125

-24

J125

-28

J125

-20

27

J125

-18

J125

-22

25

J126

-1 1

J126

-27

J126

-23 23

J126

-2519

J126

-21 21

J126

-17 17

J126

-19

1

P2-

2

2

1

J121-35

35

P2-

1

2

P3-1

P3-3

3

P3-2

C9541

3.3u

DGND

22.uL16

2

5V_Data

GPS_PWR

P1-1

1

DGND

P1-2

R2566

1.K

5V_Data

10.K

P5-2

2

DGND

R2561

AGND

P5-1

1

1

P6-2

2

AUDIO_PA_12V

P6-1

100.K

R2556

2

3

DGND

100

R35

J126

-15 15

MOMENT_SWITCH

SW2

13

J126

-11 11

J126

-9 9

J126

-13

4

J126

-2 2 8

J126

-6 6

J126

-4

J126

-10 10

J126

-8 14

J126

-12 12

J126

-16 16

J126

-14

J126

-20 20

J126

-18 18 24

J126

-22 22

J126

-26 26

J126

-24

GPS_PWR

J126

-28 28

0.

R2595

5V_Data

J125

-14

TX_EN

TX_EN

J125

-12

J125

-16

J125

-8

J125

-1

J125

-10

J125

-3

J125

-7

J125

-5

J125

-11

J125

-9

J125

-13

J125

-17

J125

-15

J125

-19

J125

-23

J125

-21

J125

-27

J125

-25

J126

-7 73

J126

-5 5

J125

-6

AGNDDGND

DGND

J126

-3

J4-2

2 J125

-4

DGND

J4-1

1 J127

-6 6

J127

-8 8

9

J127

-4 4

J127

-5 5

J127

-93

J127

-7 7

J127

-1 1

J127

-3

DGND

DGND

DGND

J127

-2 2

27

J4-4

4

AGNDDGND

J127

-10 10

J121-27

J4-3

3

J125

-2

GPS_PWR

J4-5

5

J4-6

6

DGND

Inp

ut_

I_O

&S

im_c

r_d

et

SIM

_CR

_Res

et_R

ST

5

RS

232_

RT

S

RS

232_

RX

D

SIM

_CR

_Clo

ck

DS

C_D

ow

nlin

k

DS

C_E

nab

le

An

alo

g_A

ud

io_O

ut&

Po

wer

_On

_Off

RS

232_

DC

D

IrD

A_S

elec

t

TS

_Tu

rn_o

n_s

tan

d_b

y

Inp

ut_

I_O

&S

im_c

r_d

et

SIM

_CR

_Res

et_R

ST

RS232_RI

RS232_DSR

RS232_CTS

RS232_RTS

RS232_DCD

RS232_DTR

RS232_RXD

RS232_TXD

TX_EN

RXD_UART_2

TXD_UART_2

GPS_ANTTENNA_VOLTAGE

GP

S_1

PP

S

RX

_fo

r_d

iffe

ren

tial

_GP

S_R

TC

M

RS

232_

RT

S

RS

232_

RX

D

SIM

_CR

_Clo

ck

DS

C_D

ow

nlin

k

DS

C_E

nab

le

An

alo

g_A

ud

io_O

ut&

Po

wer

_On

_Off

5

RS

232_

DC

D

IrD

A_S

elec

t

TS

_Tu

rn_o

n_s

tan

d_b

y

AGND

GPS_1PPS

RX_for_differential_GPS_RTCM

GPS_Ant_PWR_3_TO_5Vdc

VCC

VCC

VCC

VCC

DGND

DGND

DGND

DGND

AGND

DSC_Uplink

DSC_Downlink

DSC_Enable

TS_Turn_on_stand_by

SIM_CR_Clock

SIM_CR_I_O_Data

SIM_CR_Reset_RST

SIM_CR_VCC_3.0_TO_5Vdc

Input_I_O&Sim_cr_det

Wake_up_gprs_coverage_indicator

Analog_Audio_Out&Power_On_Off

Analog_Audio_In

MAN_TEST

MAN_TEST DSC_Downlink

RS232_TXD

RS232_RXD

RS232_DTR

RS232_DCD

RS232_RTS

RS232_CTS

RS232_DSR

RS232_RI

MAN_TEST

Analog_Audio_In

Analog_Audio_Out&Power_On_Off

Wake_up_gprs_coverage_indicator

Input_I_O&Sim_cr_det

SIM_CR_VCC_3.0_TO_5Vdc

SIM_CR_Reset_RST

SIM_CR_I_O_Data

SIM_CR_Clock

TS_Turn_on_stand_by

DSC_Enable

DSC_Downlink

DSC_Uplink

DSC_Enable

Analog_Audio_Out&Power_On_Off

SoftGSM_EN

IrDA_Select

DHFA_SPKR_OUT

5

MA

N_T

ES

T

RS

232_

RI

TX

D_U

AR

T_2

An

alo

g_A

ud

io_I

n

RS

232_

DS

R

DS

C_U

plin

k

RS

232_

TX

D

RS

232_

CT

S

SIM

_CR

_VC

C_3

.0_T

O_5

Vd

c

5V_Data

GPS_PWR

GPS_1PPS_STANDALONE

AUDIO_PA_12V

2.7V

RXD_UART_2

TXD_UART_2

RS232_DTR

RS232_DCD

RS232_RTS

RS232_CTS

RS232_RI

RS232_DSR

VCC

SIM

_CR

_I_O

_Dat

a

RS

232_

DT

R

MA

N_T

ES

T

RS

232_

RI

TX

D_U

AR

T_2

An

alo

g_A

ud

io_I

n

RS

232_

DS

R

DS

C_U

plin

k

RS

232_

TX

D

RS

232_

CT

S

SIM

_CR

_VC

C_3

.0_T

O_5

Vd

c

GP

S_R

TC

M_S

TA

ND

AL

ON

E

GP

S_1

PP

S_S

TA

ND

AL

ON

E

RX

D_U

AR

T_2

GP

S_A

NT

TE

NN

A_V

OL

TA

GE

TX

D_U

AR

T_2

VCC

SIM

_CR

_I_O

_Dat

a

RS

232_

DT

R

6

AGND

VCC

J12-6

BUTT-I 15 PINs BUTT-I I 15 PINs BUTT 12 PINs

RF SMA Connector

MUTE

AUDIO PA ON Const

Diagnostic

To d-10

To the UUT

To D-15

NOTE:MIRROR TO G18/D15

GPS RXD on GPS models

GPS TXD on GPS models

for CSD call/PDP context indicator

Custom Definition

VCC(3.0-6Vdc)

SHEET 5 OF 6

79B02963C87-O

DGND

C9572

220.n 220.n

C9571

C9581

470.p

AGND AGND

C9556

470.p

C9580

33

2.2m

31

J120-32

32

J120-33

29

J120-30

30

J120-31

27

J120-28

28

J120-29

25

J120-26

26

J120-27

23

J120-24

24

J120-25

21

J120-22

22

J120-23

19

J120-20

20

J120-21

17

J120-18

18

J120-19

15

J120-16

16

J120-17

13

J120-14

14

J120-15

11

J120-12

12

J120-13

J12-22

22

J120-10

10

J120-11

11

J12-23

23

4

J114

-11 3

J114

-4

J114

-6 6

J114

-3

J114

-1 1

J114

-2 2

J114

-5 5

J114

-8 8

33p

AGNDDGND

33p

C113

120n

C112

16

L11

9

j114

-16

J114

-10 10

J114

-9

J114

-7 7

J114

-12 12

J114

-13 13

J114

-14 14

2

J114

-15 15

1

DGND

P1-2

J12-20

20

5V_Data

P1-1

J12-19

19

J12-21

21

18

J12-17

17

DGND

J12-15

15

J12-18

L13

120n

4

J120-5

5

VCC

AGND

120nDGND

J120-4

34

DGNDU989

36

J120-35

35

J120-34

2

J120-3

3

J120-36

9

J120-8

8

J120-2

6

J120-1

1

J120-9

16

J120-7

7

J120-6

12

J12-14

14

J12-16

10

J12-13

13

J12-12

J12-9

9

J12-11

11

J12-10

8

J12-7

7

J12-5

5

J12-8

J12-2

2

J13-

6 6

1

J12-3

3

J2-1

5 15

DGND

DGND

J12-1

J2-1

4 14

J2-1

3 1311

J2-1

2 1210

J2-1

1

J2-9

9

J2-1

0

87

J2-8

J2-6

6

J2-7

J2-5

53

J2-4

42

J2-3

J2-1

1

J2-2

J12-4

4

J1-1 1

DGND

J1-2 2

J1-4 4

J1-3 3

J1-5 5 6

P9-

2

2

J1-6

DGND

P9-

1

1

Q37

DGND

DGND

10u

C9558

AUDIO_PA_12V

Q36

R2574

100K

R2573

560.K

R2579

10K

R2578

100.K

10K

10K

R25770.5p

DGND

R2576

DGND

C9566

4.7p

C9562

0.5p

R2583

0.5p

R2582 L17

0.

DGND J123

ANT1

NC02 3

NC1

2

J124

P8-

1

1

P8-

2

J13-

3 3 4

C101

33p

J13-

4

DGND

C97

33p

33p

C96

C95

33p

C94

33p

C93

33p

33p

C92

DGND

33p

33p

C91

C90

33p

C89

33p

C88

C74

100n

33p

DGNDC73

C87

100n

J13-

5 5

100n

C72

DGND

C85 C86

33p33p

C100

33p

20

33p

C98

19

J2-2

0

17

J2-1

9

J13-

16 16

J13-

17

C102

33p

DGND

C84

DGND

100n

C71

J13-

15 15

33p

C99

33p

13

J13-

8 8

J13-

14 14

J13-

13

2

J13-

1 1

30

J12-29

29

J13-

2

J12-27

27

J12-30

25

J12-28

28

J12-24

24

J12-26

26

J12-25

DGND

220.n

DGND

220.n

C9578

DGND

C9577

DGND

220.n

C9576

C9575

220.n

C9574

DGND

9

DGND

220.n

12

J13-

10 10

J13-

9

J13-

11 11

J13-

12

J2-1

8 18

J13-

7 7

J2-1

7 1716

J1-2

0 20

J2-1

6

J1-1

9 1917

J1-1

8 1816

J1-1

7

DGND

DGND

DGND

J1-1

6

J1-1

5 15

DGND

DGND

J1-1

4 1412

J1-1

3 1311

J1-1

210

J1-1

1

J1-9 9

J1-1

0

J1-8 8

J1-7 7

DS

C_D

ow

nlin

k

DS

C_U

plin

k

MA

N_T

ES

T

An

alo

g_A

ud

io_I

n

An

alo

g_A

ud

io_O

ut&

Po

wer

_On

_Off

EX

T_B

+

Inp

ut_

I_O

&S

im_c

r_d

et

DS

C_U

plin

k

DS

C_D

ow

nlin

k

DS

C_E

nab

le

SIM

_CR

_Clo

ck

SIM

_CR

_I_O

_Dat

a

SIM

_CR

_VC

C_3

.0_T

O_5

Vd

c

GPS_1PPS

RS232_RXD

RS232_TXD

TXD_UART_2

SIM_CR_VCC_3.0_TO_5Vdc

DS

C_E

nab

le

RS232_DTR

RS232_DCD

RS232_RTS

RS232_CTS

RS232_DSR

RS232_RI

MAN_TEST

Analog_Audio_Out&Power_On_Off

Wake_up_gprs_coverage_indicator

SIM_CR_VCC_3.0_TO_5Vdc

SIM_CR_Reset_RST

SIM_CR_I_O_Data

DSC_Enable

DSC_Downlink

DSC_Uplink

AGND_IN

TS_Turn_on_stand_by

Input_I_O&Sim_cr_det

Analog_Audio_In

RXD_UART_2

TX_EN

GPS_Ant_PWR_3_TO_5Vdc

RX_for_differential_GPS_RTCM

RS232_TXD

RS232_DTR

RS232_DCD

RS232_RTS

RS232_CTS

RS232_DSR

RS232_RI

MAN_TEST

Analog_Audio_Out&Power_On_Off

Wake_up_gprs_coverage_indicator

SIM_CR_Reset_RST

SIM_CR_I_O_Data

DSC_Enable

DSC_Downlink

DSC_Uplink

AGND_IN

TS_Turn_on_stand_by

Input_I_O&Sim_cr_det

Analog_Audio_In

VCC

VCC

VCC

DGND

DGND

DGND

DGND

SIM_CR_Clock

STNDBY

TX_Enable

IrDA_Select

2.7V_IN_SHEELD

RS

232_

RX

D

RS

232_

TX

D

RS

232_

DT

R

RS

232_

DC

D

RS

232_

RT

S

RS

232_

CT

S

RS

232_

DS

R

RS

232_

RI

SIM_CR_Clock

RS232_RXD

An

alo

g_A

ud

io_I

n

An

alo

g_A

ud

io_O

ut&

Po

wer

_On

_Off

2.7V

An

alo

g_A

ud

io_O

ut&

Po

wer

_On

_Off

5

EX

T_B

+

An

alo

g_A

ud

io_I

n

DS

C_U

plin

k

DS

C_E

nab

le

MA

N_T

ES

T

MA

N_T

ES

T

DS

C_U

plin

k

DS

C_E

nab

le

DS

C_D

ow

nlin

k

DS

C_D

ow

nlin

k

DS

C_D

ow

nlin

k

2.7V

EX

T_B

+

J5-1

1

DGND

DS

C_D

ow

nlin

k

12V_SW

An

alo

g_A

ud

io_I

n

An

alo

g_A

ud

io_O

ut&

Po

wer

_On

_Off

DHFA_MIC_IN

SIM

_CR

_I_O

_Dat

a

Inp

ut_

I_O

&S

im_c

r_d

et

SIM

_CR

_VC

C_3

.0_T

O_5

Vd

c

SIM

_CR

_Res

et_R

ST

SIM

_CR

_Clo

ck

Modem/GPS Select

Connector SHEELD

D9 FEMALE

EXT SIM ConnectionsHandSet adapter

RJ-45 Connector

HeadSet Connctor.

RJ-45 Connector

DHFA MIC

SHEET 6 OF 6

79B02963C87-O

2

DGND

VR7

MMBZ15VD

3

12

DTE Orintation

SoftGSM Switching circuit

3

12

DGND

MMBZ15VD

VR8

3

1

3

12

DGND

MMBZ15VD

VR6

MMBZ15VD

3

12

DGND

DGND

MMBZ15VD

VR5

VR4

V-4

VCC

26

DGND

12K

R2585

T2OUT6

T3IN22

T3OUT7

T4IN19

T4OUT10

T5IN17

T5OUT12

V+27

R1OUTB16

R2IN9

R2OUT20

R3IN11

R3OUT18

T1IN24

T1OUT5

T2IN23

C2+1

C2-3

FORCEOFF14

FORCEON13

2

GND

INVALID15

R1IN8

R1OUT21

DGND

MAX3238E

U979

C1+28

C1-25

3

12

J5-2

2

5V_Data

DGND

DGND

VR9

MMBZ15VD

Q28

100.n

C9546

C9545

330.n

DGNDDGND

330.n

C9543C9544

5V_Data

330.n

R2559

22.K

Q32U99122.K

R2558

3.9K

Q30

100.

R2565

R2568

DGND

Q29

Z1

R2580

100K

X012

13X1

Y15

Y02

Y11

Z4

Z05

3

MC14053B

A11

B10

C9

EN6

GN

D8

VCC

16

VE

E7

X14

5V_Data

DGND

U990

R2560

DGND

SIM

-8 8

DGND

22.K

6

SIM

-4 4

SIM

-6

SIM

-2 25

SIM

-3 37

SIM

-5

33.u

SIM

-7

DGND

C9565

11

J5-10

10

9.1K

DGND

J5-11

2

DGND

R2586

P12-1

1

P12-2

33p

DGND

5V_Data

DGND

DGND

DGND

C9568

DGND

C9573

220.n

C9570

220.n

R83

0

2

J115

-1 1

DGND

J115

-4 4

J115

-3 3

J115

-26

J115

-5 5

J115

-7 7

J115

-6

DGND

VCC

J115

-8 8

680p

C79

DGND

DGND

C83

C9551

680p

33p

33p

C82C81

33p

33p

C9552

120n

0

R2569

U986

4.7K

DGND

3

J10-

2 2

R69

5

J10-

4 4

J10-

3

J10-

6 6

J10-

5

J10-

8 8

J10-

7 7

2.2u

C7

R82

100

Q26

4.7K

DGND

Q17

D

G

S

R70

J10-

1 1

7002

C60

10u

DGND

DGND

10UF

C59

DGND

10UF

C61

34

AGND

DGND

VCC

J118

12

GN

D1

8G

ND

2

S_RESET4

5S

_VC

C1

7S

_VC

C2

3S_CLK

6S_I|O

2S_PD

DGND

DGND

S1

SWITCH

1

120n

U985

120n

L1

R20

4.7K

SIM

-1 1

J111

12 34

120n

L7

DGND

AGND

680p

C78

C80

33p

120n

VR3

MMBZ15VD

3

12

DGND

L3

8

VR2

MMBZ15VD

3

12

J5-5

5

J5-8

9

J5-7

7

J5-6

6

J5-9

J5-3

3

J5-4

4

SIM_CR_I_O_Data

Input_I_O&Sim_cr_det

An

alo

g_A

ud

io_I

n

An

alo

g_A

ud

io_O

ut&

Po

wer

_On

_Off

DS

C_U

plin

k

TxD

CTS

RTS

DSR

DTR

RI

DSC_Enable

DC_to_DC_12V

SPKR_Out

MIC_In

DS

C_U

plin

k

DS

C_D

ow

nlin

k

12V_SW

SIM_CR_Reset_RST

SIM_CR_VCC_3.0_TO_5Vdc

SIM_CR_Clock

CTS

RxD

DTR

TxD

DCD

RxD

DSC_EnableDSC_Downlink

SoftGSM_EN

SoftGSM_EN

SoftGSM_EN

RTS

Analog_Audio_Out&Power_On_Off

RTS

RI

DCD

DSR

TXD_UART_2

RXD_UART_2

Modem_GPS_RxD

Modem_GPS_TxD

RS232_RI

RS232_DSR

RS232_CTS

RS232_RTS

RS232_DCD

RS232_DTR

RS232_TXD

RS232_RXD

1

Parts ListEvaluation BoardModel FTN8071A P4

REFERENCE SYMBOL

MOTOROLA PART NO. DESCRIPTION

CapacitorsC1-6 2311049A07 ECAP_1UFC7 2311049A09 CAPP_2.2uC8-9 2311049J35 CAPP_22uC11 2113741F49 CAP_10nC12 2113743A19 CAP_100NFC14-15 2113741F33 CAP_2.2NFC24-30 2113740F39 CAP_33pC32-46 2113740F39 CAP_33pC47 2113741F49 CAP_10nC48-51 2113740F39 CAP_33pC52 2113741F21 CAP_680PFC60 2380090M24 CAPP_10uC62 2380090M24 CAPP_10uC68 2113740F39 CAP_33pC70 2113743G26 CAP_4.7uC71-77 2113743A19 CAP_100nC78-79 2113741F21 CAP_680PFC80-106 2113740F39 CAP_33pC110-117 2113740F39 CAP_33pC9185 2311049A57 ECAP_10UFC9190 2311049C05 CAPP_47uC9192 2113743K17 CAP_330nC9201 2113743K17 CAP_330nC9204 2113743E20 CAP_100nC9205 2311049A01 CAPP_0.1uC9215 2113741F49 CAP_10nC9219 2113741F25 CAP_1nC9228 2113740F51 CAP_100pC9241 2113740F51 CAP_100pC9365 2311049A57 ECAP_10UFC9378 2113743E20 CAP_100nC9386 2113743E20 CAP_100nC9409 2113743K17 CAP_330nC9535-9536 9186929J01 880_1800MHZC9537-9538 2311049C13 CAPP_100u

C9539 2311049A24 CAPP_68uC9540 2311049A07 CAPP_1UFC9541 2113743G25 CAP_3.3uC9542 2186201J02 CAP_22uC9543-9545 2113743K17 CAP_330nC9546 2113743K15 CAP_100nC9547-9548 2113743E20 CAP_100nC9549-9550 2113740F39 CAP_33pC9551 2113741F21 CAP_680PFC9552-9554 2113740F39 CAP_33pC9555 2311049A07 CAPP_1UFC9556 2313748E31 CAPP_2.2mC9558 2311049A19 CAPP_10uC9559 2380090M39 CAPP_470uC9560 2311049A07 CAPP_1UFC9561 2113928A01 CAP_1uC9562 2113740F19 CAP_4.7pC9563-9564 2311049C13 CAPP_100uC9565 2311049C08 CAPP_33uC9566 2113740F01 CAP_0.5pC9567-9568 2113740F39 CAP_33pC9569-9578 2113743A23 CAP_220nC9579 2113743A19 CAP_100nC9580-9581 2113740F67 CAP_470pCR1 4880304L02 LED_GRNCR2-11 4880304L01 LED_RED

DiodesD1 4813833B01 MBRS140D2 4813833A06 MBRD360D3 4813833B01 MBRS140D4-5 4813833A02 MBRD640

FusesF1 0904923K01 SMD_FUSE_HOLD

ConnectorsJ1-2 0909449B04 CONN_JJ3 3102151C30 CONN_PJ4 2804989M01 EDGEJ5 0909672B03 CONN_JJ10 0983365N01 EDGEJ12 2804989M01 EDGEJ13 0909467R02 CONN_JJ111 0909399T02 CONN_J

REFERENCE SYMBOL

MOTOROLA PART NO. DESCRIPTION

2

J114 2802935S08 CONN_PJ115 0983365N01 EDGEJ118 0909399T02 CONN_JJ120-121 0988716K01 CONNJ122 0909032K01 JACK_4PINJ123 3903920K01 ANTENNA_3P2NCJ125 0908606Y06 CONN_JJ126 2880471L02 CONN_PJ127 0908606Y05 CONN_J

CoilsL1-8 2462587T16 IDCTR_120nL10-13 2462587T16 IDCTR_120nL14 2503788S09 IDCTR_22uL15 2462587T16 IDCTR_120nL16 2462587P28 IDCTR_22uL17 249646M43 NO_DESC

ConnectorsLED 2880001R02 CONN_PP1-2 2880001R02 CONN_PP3 2880001R03 CONN_PP5-10 2880001R02 CONN_PP12 2880001R02 CONN_P

TransistorsQ3 4803676A04 BSS123Q4 4802393L34 FDV302PQ11 4802393L34 FDV302PQ14 4813824A17 PNP_3906LQ15-16 4813824A10 NPN_3904LQ17 4813823A07 TMOSFETN_7002Q18-23 4802393L34 FDV302PQ25 4803676A04 BSS123Q26 4802393L04 BSS84Q27 4813821A21 MTD20N03HDQ28-30 4803676A04 BSS123Q32 4803676A04 BSS123Q35-37 4803676A04 BSS123Q38 4809807C24 SI4463

ResistorsR2-3 0662057D17 RES_51KR4 0662057B47 RES_0R15 0662057B14 RES_470KR17 0662057B14 RES_470K

REFERENCE SYMBOL

MOTOROLA PART NO. DESCRIPTION

R18-19 0662057A77 RES_15KR20 0662057A65 RES_4.7KR21 0662057A58 RES_2.4KR22-23 0662057A81 RES_22KR24-29 0662057A43 RES_560R30 0662057D30 RES_180KR31 0662057B16 RES_560KR32 0662057A89 RES_47KR33 0662057A73 RES_10KR35 0611077D97 RES_100R36 0662057A97 RES_100KR38 0662057C75 RES_1KR50 0662057C75 RES_1000_1KR52 0662057R68 RES_18.2KR53 0662057C61 RES_270R55-63 0662057C61 RES_270R64-66 0662057B14 RES_470KR67 0662057A58 RES_2.4KR68 0662057A73 RES_10KR69-70 0662057A65 RES_4.7KR77 0662057A89 RES_47KR78 0662057A87 RES_39KR79 0662057A65 RES_4.7KR82 0611077D97 RES_100R83 0662057B47 RES_0R84 0662057A85 RES_33KR85 0662057B47 RES_0R1056 0662057P02 RES_15KR1068 0662057A87 RES_39KR1098 0662057A71 RES_8.2KR1104 0662057A67 RES_5.6KR2468-2469 0662057B47 RES_0R2518 0611079E05 RES_110KR2519 0662057B47 RES_0R2521 0662057P20 RES_20KR2527 0662057P95 RES_100KR2550-2552 0662057P02 RES_15KR2553 0662057A77 RES_15KR2554 0604648P05 RES_0.1R2556-2557 0662057A97 RES_100KR2558-2560 0662057A81 RES_22KR2561 0662057A73 RES_10K

REFERENCE SYMBOL

MOTOROLA PART NO. DESCRIPTION

3

R2564 0662057A55 RES_1.8KR2565 0662057A63 RES_3.9KR2566 0662057A49 RES_1KR2568 0662057A25 RES_100R2569 0662057B47 RES_0R2570 0662057C61 RES_270R2572 0662057D18 RES_56KR2573 0662057B16 RES_560KR2574 0662057A97 RES_100KR2575 0662057A77 RES_15KR2576-2577 0662057A73 RES_10KR2578 0662057A97 RES_100KR2579 0662057A73 RES_10KR2580 0662057A97 RES_100KR2582-2583 2113740F01 CAP_0.5pR2585 0662057A75 RES_12KR2586 0662057A72 RES_9.1KR2587 0662057A58 RES_2.4KR2588 0662057A63 RES_3.9KR2589 0662057G31 RES_221KR2590 0662057B47 RES_0R2593 0662057B14 RES_470KR2596 0662057A81 RES_22KR2597 0662057A71 RES_8.2KR2598 0662057A58 RES_2.4K

SwitchesS1 4009060S01 SWITCH

REFERENCE SYMBOL

MOTOROLA PART NO. DESCRIPTION

S2 4008241G06 SWIT_ET01SW2 4004929K01 MOMENT_SWITCH

ShieldsSH1 2604044K01 SHIELD

SIMSIM 2808044H12 CONN_P

Integrated CircuitsU3-4 5113818A14 MC33202DR2U5 5104187K08 MAX603ESAU978 5105469E65 LP2951CU979 5109781E76 MAX3238EU980 5104187K46 LP2957ISU981 5185963A04 LP2981U982 5144751U01 TDA1519CTDU983 5108858K58 MAX771ESAU984 4803676A04 BSS123U985-987 2462587T16 IDCTR_120nU988 5113818A03 MC33072U989 2462587T16 IDCTR_120nU990 5113806A20 MC14053BU991 4803676A04 BSS123U992 5113818A03 MC33072

Voltage SuppressorsVR2-9 4813832C28 ZENER_MMBZ15VDVR10 4813830G02 MMSZ4679T

REFERENCE SYMBOL

MOTOROLA PART NO. DESCRIPTION

1

Parts ListEvaluation BoardModel FTN8071B P4

REFERENCE SYMBOL

MOTOROLA PART NO. DESCRIPTION

CapacitorsC1-6 2311049A07 ECAP_1UFC7 2311049A09 CAPP_2.2uC8-9 2311049J35 CAPP_22uC11 2113741F49 CAP_10nC12 2113743A19 CAP_100NFC14 2113741F33 CAP_2.2NFC15 2113743F49 10nfC24-30 2113740F39 CAP_33pC32-46 2113740F39 CAP_33pC47 2113741F49 CAP_10nC48-51 2113740F39 CAP_33pC52 2113741F21 CAP_680PFC60 2380090M24 CAPP_10uC68 2113740F39 CAP_33pC75-77 2113743A19 CAP_100PFC78-79 2113741F21 CAP_680PFC80-C83 2113740F39 CAP_33pC103-C105 2113740F39 CAP_33pC110-117 2113740F39 CAP_33pC9185 2311049A57 10uC9192 2113743K17 CAP_330nC9201 2113743K17 CAP_330nC9204 2113743E20 CAP_100nC9205 2311049A01 CAPP_0.1uC9215 2113741F49 CAP_10nC9219 2113741F25 CAP_1nC9228 2113740F51 CAP_100pC9241 2113740F51 CAP_100pC9365 2311049A57 10uC9378 2113743E20 CAP_100nC9386 2113743E20 CAP_100nC9409 2113743K17 CAP_330nC9535-9536 9186929J01 880_1800MHZC9537-9538 2311049C13 CAPP_100uC9539 2311049A24 CAPP_68u

C9540 2311049A07 CAPP_1uC9541 2113743G25 CAP_3.3uC9542 2186201J02 22uC9543-9545 2113743K17 CAP_330nC9546 2113743K15 CAP_100nC9547-9548 2113743E20 CAP_100nC9549-9550 2113740F39 CAP_33pC9551 2113741F21 CAP_680PFC9552 2113740F39 CAP_33pC9554 2113740F39 CAP_33pC9555 2311049A07 CAPP_1uC9556 2313748E31 CAPP_2.2mC9558 2311049A19 CAPP_10UFC9559 2380090M39 CAPP_470uC9560 2311049A07 CAPP_1UFC9561 2113928A01 CAP_1uC9562 2113740F19 CAP_4.7pC9563-9564 2311049C13 CAPP_100uC9565 2311049C08 CAPP_33uC9566 2113740F01 CAP_0.5pC9567-9568 2113740F39 CAP_33pC9569-9573 2113743A23 CAP_220nC9578 2113743A23 CAP_220nC9579 2113743A19 CAP_100PFC9580-9581 2113740F67 CAP_470pC9582 2311049C08 CAPP_33uC9583-9585 2113743K17 CAP_330nC9586 2113743K15 CAP_100nC9587-9590 2113740F51 CAP_100pCR1 4880304L02 LED_GRNCR2-11 4880304L01 LED_RED

DiodesD1 4813833B01 MBRS140D2 4813833A06 MBRD360D3 4813833B01 MBRS140D4-5 4813833A02 MBRD640

FusesF1 0904923K01 SMD_FUSE_HOLD

ConnectorsJ1-2 0909449B04 CONN_JJ3 3102151C30 CONN_P

REFERENCE SYMBOL

MOTOROLA PART NO. DESCRIPTION

2

J4 2804989M01 EDGEJ5 0909672B03 CONN_JJ10 0983365N01 EDGEJ12 2804989M01 EDGEJ111 0909399T02 CONN_JJ115 0983365N01 EDGEJ118 0909399T02 CONN_JJ124 2886156U01 CONN_PJ125 0908606Y06 CONN_JJ126 2880471L02 CONN_J127 0908606Y05 CONN_JJ128-129 0988716K01 CONN_JJ130 0909032K01 CONN_J

CoilsL1-7 2462587T16 IDCTR_120nL10-13 2462587T16 IDCTR_120nL14 2503788S09 IDCTR_22uL15 2462587T16 IDCTR_120nL16 2462587P28 IDCTR_22uL17 2485930A01 3.3nh

ContactM1 3903920K01 CONTACT

ConnectorsP6 2880001R02 CONN_PP9 2802837C03 CONN_PP10 2880001R03 CONN_PP11 2802935S09 CONN_P

TransistorsQ3 4803676A04 BSS123Q4 4809579E18 FDV302PQ11 4809579E18 FDV302PQ14 4813824A17 PNP_3906LQ15-16 4813824A10 NPN_3904LQ17 4813823A07 TMOSFETN_7002Q18-23 4809579E18 FDV302PQ25 4803676A04 BSS123Q26 4802393L35 BSS84Q27 4813821A21 MTD20N03HDQ28-30 4803676A04 BSS123Q32 4803676A04 BSS123Q36-37 4803676A04 BSS123Q38 4809807C24 SI4463

REFERENCE SYMBOL

MOTOROLA PART NO. DESCRIPTION

ResistorsR2-3 0662057D17 RES_51KR4 0662057B47 RES_0R15 0662057B14 RES_470KR17 0662057B14 RES_470KR18-19 0662057A77 RES_15KR20 0662057A65 RES_4.7KR21 0662057A71 8.2KR22-23 0662057A81 RES_22KR24-29 0662057A43 RES_560R30 0662057D30 RES_180KR31 0662057B16 RES_560KR32 0662057A89 RES_47KR33 0662057A57 2.2KR35 0611077D97 RES_100R38 0662057C75 RES_1KR50 0662057C75 RES_1000_1KR52 0662057R68 RES_18.2KR53 0662057C61 RES_270R55-63 0662057C61 RES_270R64-66 0662057B14 RES_470KR67 0662057A58 RES_2.4KR68 0662057A73 RES_10KR69-70 0662057A65 RES_4.7KR77 0662057A89 RES_47KR78 0662057A87 RES_39KR79 0662057A65 RES_4.7KR82 0611077D97 RES_100R83 0662057B47 RES_0R84 0662057A85 RES_33KR1056 0662057P02 RES_15KR1068 0662057A87 RES_39KR1098 0662057A71 RES_8.2KR1104 0662057A67 RES_5.6KR2468-2469 0662057B47 RES_0R2518 0611079E05 RES_110KR2519 0662057B47 RES_0R2521 0662057P20 RES_20KR2527 0662057P95 RES_100KR2550-2552 0662057P02 RES_15KR2553 0662057A77 RES_15KR2554 0604648P05 RES_0.1

REFERENCE SYMBOL

MOTOROLA PART NO. DESCRIPTION

3

R2558-2560 0662057A81 RES_22KR2564 0662057A55 RES_1.8KR2565 0662057A63 RES_3.9KR2568 0662057A25 RES_100R2569 0662057B47 RES_0R2570 0662057C61 RES_270R2573 0662057B16 RES_560KR2574 0662057A97 RES_100KR2575 0662057A77 RES_15KR2576-2577 0662057A73 RES_10KR2578 0662057A97 RES_100KR2579 0662057A73 RES_10KR2580 0662057A97 RES_100KR2583 2113740F01 CAP_0.5pR2587 0662057A58 RES_2.4KR2588 0662057A63 RES_3.9KR2589 0662057G31 RES_221KR2590 0662057B47 RES_0R2593 0662057B14 RES_470KR2596 0662057A81 RES_22KR2597 0662057A71 RES_8.2KR2598 0662057A58 RES_2.4KR2599-2601 0662057C61 RES_270R2602 0662057A97 RES_100KR2603 0662057A89 RES_47KR2605-2606 0662057A75 RES_12KR2607 0662057A73 RES_10KR2608-2609 0662057A71 RES_8.2KR2611 0662057A49 RES_1KR2612-2613 0662057C61 RES_270R2614-2615 0662057B47 RES_0

SwitchesS1 4009060S01 SWITCHS2 4008241G06 SWIT_ET01S3 4083849F04 SWITCHSW2 4004929K01 MOMENT_SWITCH

ShieldsSH1 2604044K01 SHIELD

SIMSIM 2808044H04 CONN_P

REFERENCE SYMBOL

MOTOROLA PART NO. DESCRIPTION

Integrated CircuitsU3-4 5113818A14 MC33202DR2U5 5104187K08 MAX603ESAU978 5105469E65 LP2951CU979 5109781E76 MAX3238EU980 5104187K46 LP2957ISU981 5185963A04 LP2981U982 5144751U01 TDA1519CTDU983 5108858K58 MAX771ESAU984 4803676A04 BSS123U985-987 2462587T16 IDCTR_120nU988 5113818A03 MC33072U989 2462587T16 IDCTR_120nU990 5113806A20 MC14053BU991 4803676A04 BSS123U992 5113818A03 MC33072U993 5109781E76 MAX3238E

Voltage SuppressorsVR2-9 4813832C28 ZENER_MMBZ15VDVR10 4813830G02 MMSZ4679TVR11-12 4813832C28 MMBZ15VDVR14 4813832C28 MMBZ15VDVR16 4813832C28 MMBZ15VDVR18 4813832C28 MMBZ15VD

REFERENCE SYMBOL

MOTOROLA PART NO. DESCRIPTION

O1 79B02965C23-0

J126

8486452t01_p5

SHOWN FROM SIDE 1O1 79B02965C21-0

C1

C2

C3

C4

C5

C6

C8

C9

C11

C12

C13

C14

C15

C24

C25

C26

C27

C28

C29 C30

C32

C33

C34

C35

C36

C37

C38

C39

C40

C41

C42

C43

C44

C45

C46

C47

C48

C49

C50

C51

C52

C60

C62

C68

C71C72

C73

C74

C75

C76

C77

C78

C79

C80

C81

C82

C83

C84

C85

C86

C87

C88

C89

C90

C91

C92

C93

C94

C95

C96

C97

C98

C99

C10

0

C10

1

C10

2

C103C10

4

C10

5

C11

0C112

C11

4

C11

5

C11

6

C11

7

C9192 C9206

C9365

C93

78

C9386

C94

09

C95

36

C9537

C9538

C9539

C9540

C95

42

C95

49

C95

50

C95

51C95

52

C9553

C95

54

C95

55

C9556

C9559

C9560

C9561

C9563

C9564

C95

67

C9569

C9570

C9573

C9582

C9583

C95

84

C9585

C95

86

C95

87C

9588

C95

89

C95

90

CR1 CR2CR3CR4CR5CR6CR7CR8CR9 CR10CR11

D1

D3

D6D7 D8

F1

J1J2

1 J3

J4

51

69

J5

8

1

J10

J12

J13

J111

8

1

J115

J118

J124

J125

J127

J128

J129

J130

L1

L2

L3

L4

L5L6

L7

L10

L12

L14

L15

L16

M1

P6

1

6

5

9

P9

P10

P11

Q38

R2

R3

R4

R15

R17

R18

R19

R21

R22R23

R24

R25R26

R27

R28

R29

R30

R31

R32

R33

R35R

38

R50

R52

R53

R63

R77

R78

R83

R84

R10

56

R10

57

R10

68

R1069

R11

04

R24

73

R2518

R25

19

R25

21R

2527 R2550

R2551R2552

R25

53

R2564

R2569

R2575

R25

87

R25

88

R25

95

R2602

R26

05

R26

06

R2607

R26

08

R26

09

R26

11

R2612R2613

R2614

R2615

R2616

R2617

S1

S2

S3

SH1

SIM

SW2

SW2

U3

U4

U5

U978

U980

U98

1

U985

U986

U98

7

U988

U993

VR11VR12VR14VR16VR18

OL 79B02965C24-0

OL 79B02965C22-0SHOWN FROM SIDE 2

8486452t01_p5

C7

C59

C61

C70

C106

C111

C113

C91

85

C91

90

C92

01

C9204

C92

05

C92

08

C92

15

C9219

C92

28C

9241

C95

35

C9541

C9543

C95

44

C95

45

C9546

C95

47

C95

48

C95

58

C9562

C95

65

C9566

C9568

C95

71

C95

72C

9578

C9579

C95

80C95

81

D2

D4 D5

L8

L11

L13

L17

Q3

Q4 Q11Q14

Q15

Q16

Q17

Q18Q19Q20Q21Q22Q23

Q25

Q26

Q27

Q28Q29

Q30Q32

Q36

Q37

Q39

Q40 Q41

R20

R55

R56

R57

R58

R59

R60

R61 R62

R64

R65

R66

R67 R68

R69R70

R79

R82

R85

R1098

R24

68

R24

69R

2470

R24

71

R2554

R25

58

R25

59

R2560

R2563

R25

65

R2568

R25

70

R25

73

R2574

R2576

R2577

R2578

R2579

R2580

R2582

R2583

R25

89 R2590

R25

93

R25

94

R2596

R2597

R25

98

R2599R26

00R26

01

R2603

U979

U982

U983

U984

U989

U990

U991

U992

VR2

VR3

VR4

VR5VR6

VR7

VR8

VR9

VR

10

RS232_TXD

RXD_UART_2

RX_for_differential_gps_rtcm

SPKR_Out

SPK_GND

STNDBY

TXD_UART_2

VCCDC_to_DC_12V

DHFA_MIC_IN

2.7V

2.7V_IN_SHEELD

5V_Data

AUDIO_PA_12V

Analog_Audio_In

Analog_Audio_OUT&POWER_On_Off

SPKR_OUT

STNDBY

TXD_UART_2

VCC

Audio & Voltage REGs

Interface Connectors

SHEET 1 OF 6

79B02963C88-O

DHFA_SPKR_OUT

DSC_Enable

GPS_1PPS

GPS_PWR

LEDS_Enable

MIC_In

RS232_CTS

RS232_DCD

RS232_DSR

RS232_DTR

RS232_RI

RS232_RTS

RS232_RXD

RS232_TXD

RXD_UART_2

RX_for_differential_gps_rtcm

Analog_Audio_OUT&POWER_On_Off

DC_to_DC_12V

DHFA_MIC_IN

DHFA_SPKR_OUT

DSC_Enable

GPS_1PPS_LED

GPS_PWR

LEDS

MIC_In

RS232_CTS

RS232_DCD

RS232_DSR

RS232_DTR

RS232_RI

RS232_RTS

RS232_RXD

DSC_Enable

2.7V_IN_SHEELD

Analog_Audio_In

VCC

5V_Data Dc_to_Dc_12V

GPS_PWR

SPKR_OUT

AUDIO_PA_12V

2.7V

SPKR_OUT

AUDIO_PA_12V

5V_Data

2.7V

VCC

GPS_PWR

Analog_Audio_In

Dc_to_Dc_12V

2.7V

2.7V_IN_SHEELD

5V_Data

AUDIO_PA_12V

Analog_Audio_In

TXD_UART_2

RXD_UART_2

RX_for_differential_gps_rtcm

TXD_UART_2

RXD_UART_2

RX_for_differential_gps_rtcm

2.7V_IN_SHEELD

DHFA_SPKR_OUT

DHFA_MIC_IN

DHFA_SPKR_OUT

DHFA_MIC_IN

DSC_Enable

C9204

100n

AUDIO_PA_12V

8V_AUDIO

C9409

330n

33p

C68

R2471

0.

R2587 change to 8.2k

79B02963C88-O

SHEET 2 OF 6

2.7Vdc REG

Must be SHEELDED

R33 change to 2.2k

R21 change to 8.2k

0.

R2469

R2468

0.

2

3

1

8

4

C9554

33p

U4

MC33202DR2

C9549

DGNDAGND

R3

51K

AGND DGND

33.p

C111

33p

C110

33p

L10

120n

100n

C77 C105

U987

33p

120n

AGND

C9550

33.p

22u

AGND

AGND

C9C5

1uF

C6

1uF

1.8K

R2564

1uC9540

R2550

AGND

AGND

15K

C9192

330n

MIC_BAIS

AGND

C4

1u

33p

C48

VAG

15NC9

NINV19

OUT13

OUT28

RR1

VP10

13NC11

NC24

NC36

7NC4

NC59

NC618

NC717

NC816

TDA1519CTD

GN

D1

20

GN

D2

5 21G

ND

3

INV12

M_SS11

NC12

NC1014

U982

C9378

100n

C9219

1n

8.2K

R1098

C9201

330n

880_1800MHZ

C9535

1IN

2

OUT

15K

R2552

R2551

33p

C49

15K

100p

C9241

10n

C9215

MC33072

U988

vcc=8V_AUDIO,vee=AGND

6

5

7

8

4

C9208

100n

5.6K

R1104

R1056

15K

R1068

39.K3.3u

C9185

47.u

C9190

AGND

C9205

0.1u

1.u

C9555

120n

L15

AGND

5V_Data

21

OFF_4

OUT8

SET5

AGND

RES_47K

R32

MAX603ESA

U5

GN

D1

2G

ND

23

GN

D3

6G

ND

47

IN1

C62

R23

10u

22K

R22

22K

470K

47K

AGND

R15

R78

R77

AGNDDGND

39K

C117

33p

C116

33p

120n

AGND

VCC

L12

C76

100n

C104

33p

100n

C75 C103AGND AGND

AGND

AGND

AGND

AGND

33p

0.

R2473

C9228

15K

100p

R1057

39.K

R1069

15K

C9206

100n

R2553

R2470

0.

33p

C27

33p

C26

33p

C28

R2588

3.9K1.u

C9560

DGND

VAG2

VAG2

VAG

VAG

33pC24

C956733p

R2587

2.4K

C9561

1

DGND

AGND

AGND

1.u

SH1SHIELD

R2

560R25

2.2n

51K

R24 560

C13

15K

R19

120n

L6

120n

L5

VALUE

3.9KR33

33p

C29

RES_1000

R50

C30

6

5

7

8

4

33p

R30

180K

U4MC33202DR2

R18

15K

C15 2.2NF

C52 680PF

0

R4

1uF

C1

0.

R2590

15K

R2575

AGND

AGND

AGND

8V_AUDIO

R2563

8.2K

AGND AGND

AGND

AGND

AGND

C2

1uF

33p

C32

33p

C34

33p

C35

33p

C33

1uF

C44

C3

33p

C38 33p

33pC39

33p

C40

33p

C41

33p

C46

33p

C45

C43

33p

AGND AGND

33p

C42

33p

C36

33p

C37

L2

100NF

C12120n

R21

2.4K

MC33202DR2

6

5

7

8

4

U3MC33202DR22

31

8

4

AGND

U3

C11

AGND

2.2n

10n

C14R29

560

560

R28

R27 560

560R26

33pC51

C50 33p

33p

C9553

R38

AGND

MIC_BAIS

AGND AGND

AGND

1K

33pC25120n

AGND

L4

R84 33.K

R31

560K

R17

470K

18.2K

R52

C47

AGND

22uC8

10n

MIC_BAIS

MIC_In

2.7V_IN_SHEELD

2.7V_IN_SHEELD

2.7V_IN_SHEELD

2.7V

DHFA_MIC_IN

VAG2

Analog_Audio_In

2.7V_IN_SHEELD

2.7V_IN_SHEELD

2.7V_IN_SHEELD

Analog_Audio_OUT&POWER_On_Off

NINV

SPK_GNDSPK_GND

Analog_Audio_OUT&POWER_On_Off

VAG

SPKR_Out

DHFA_SPKR_OUTDHFA_SPKR_OUT

STNDBY

RR

INV

C9542

47.u

DGND

R62

Q25

CR11 CR1

VCC

Modem_TXD

CR2

1PPS

Must be SHEELDED

To be Placed

In the SHEELED

DNP

DNP

DNP

DNP

79B02963C88-O

SHEET 3 OF 6

270

470K

R65

GPS 3Volts REG

Voltage to MIC & AMP

5V regulator for

13mmx13mm PCB

Heatsink is needed

DGND

3906L

Q14

470K

R64

R67

2.4K

Q15

3904L

270

R63

Modem_RXD

CR10

270

Q3

R2570

270

R61

DSC_EN

CR9

R60

270

CR8

DCD

R59

270

R58

CR7

DTR

CR6

DSR

270

R57

270

RTS

CR5

CTS

R56

270

R55

270

CR4

RI

CR3

R53

270

ON_OFF*3

VIN1

VOUT5

DGND

U981LP2981

GN

D

2

NC4

Q11

Q4

Q18

Q19

Q20

Q21

Q22

Q23

4.7K

U984

R79

DGND

R66

470K

Q16

3904L

R68

RES_10K

J3-2

2

100.u

C9564

100.u

C9563

100.u

C9537

C9569

220.n

DGND

D5

R2594

D4

0.

470.K

R2593

R2598

Q38

22.K

2.4K

8.2K

R2596

DGND

R2597

221K

R2589

3

1

8

4

2.

VR10

DGND

U992

MC33072

2

C9579

100.n

AG

ND

8CS

1EXT

3FB

7G

ND

5REF

4SHDN

2V+

5V_Data

AGND

U983

MAX771ESA

6

D2

C114

J3-3

3

33p

DGND

100.u

C9538

5ERROR

3

GND

1INPUT

2OUTPUT

4SHUTDOWN

DGND

DGND

LP2957IS

U980

C9548

100.n

R2554

0.1 C9547

DGND

DGND

AGND

DGND

100.n

68u

C9539

Q27

L1422.u

VCC

DGND

S2

1

2

3

D1

DGND

VCC

VOLTAGE

AMP

F1

1

DGND

C115

33p

880_1800MHZ

C9536

IN

1

OUT

2

J3-1

R2527

100.K

R2521

20.K

R2519

0.

R2518

1OUTPUT

2SENSE

3SHUTDOWN

110.K

65V_TAP

5ERROR

7FEEDBACK

4

GND

8INPUT

C9365

AUDIO_PA_12V8V_AUDIO

U978

LP2951C

3.3u

C9386

100n

C106 33p

C70 4.7u

0R85

120nL8

AGND DGND

R2601

270 270

R2600

270R2599

D8

LED_RED

D7

LED_RED

D6

LED_RED

Q41

Q40

Q39

DC_to_DC_12V5V_Data

5V_Data

AUDIO_PA_12V

VCC

SENSE

5V_Data

RS232_DCD

RS232_DTR

RS232_DSR

RS232_RTS

RS232_CTS

RS232_RI

VCC

GPS_PWR

GPS_1PPS_LED

RX_for_differential_gps_rtcm

TXD_UART_2

RXD_UART_2

DSC_Enable

RS232_RXD

RS232_TXD

LEDS

25

d-10 To HOST

To HOST

d-15 To HOST

(GPS RXD on GPS modeles)

(GPS TXD on GPS modeles)

for CSD call

3.0-6Vdc

AUDIO PA ON Const - For D10

Speaker Jack

5Volts

3Volts

DIN Connector F.

GPS Connector

DIN Connector M.

DNP

PDP context indicator

79B02963C88-O

SHEET 4 OF 6

DGND

J4-11

26

J129-24

24

J129-25

J129-22

22

J129-23

23

20

J129-21

21

J129-19

19

J129-20

17

J129-18

18

J129-16

16

J129-17

J129-14

14

J129-15

15

12

J129-13

13

J129-11

11

J129-12

9

J129-10

10

J129-8

8

J129-9

J129-6

6

J129-7

7

4

J129-5

5

J129-3

3

J129-4

J4-3030

AGND

VCC

DGND AGND

VCC

J4-2828

J4-2929

8

J4-2727

DGND

S3

SWITCH

1

3.3u

C9541

22.u

L16

R2607

5V_Data

GPS_PWR

R2602

10K

5V_Data

5V_Data

DGND

100K

1K

R2611

1

2

3

4

VCC

C9559

J130

AGND

470u

DGND

100

R35

J129-1

J129-2

J129-35

35

J129-36

36

33

J129-34

34

J129-32

32

J129-33

30

J129-31

31

J129-29

29

J129-30

J129-27

27

J129-28

28

3

J129-26

26

J4-2525

MOMENT_SWITCH

SW2

2

J4-2323

J4-2424

J4-2121

J4-2222

J4-1919

J4-2020

J4-1717

J4-1818

J4-1515

J4-1616

J4-1313

J4-1414

11J4-12

12

J4-1010

J4-11

J4-88

J4-99

J4-66

J4-77

J4-44

J4-55

J4-22

J4-33

J126

-17 17

J4-26

13

J126

-15 15

J126

-11 11

J126

-137

J126

-9 9

J126

-5 5

J126

-71

J126

-3 3

AGNDDGND

DGND

J126

-1

J125

-3

J125

-1

J125

-7

J125

-5

J125

-9

J125

-13

J125

-11

J125

-15

J125

-19

J125

-17

J125

-23

J125

-21

J125

-25

J125

-28

J125

-27

J125

-26

J125

-22

J125

-24

18

J125

-20

J126

-16

16

J126

-18

24

J126

-20

20

J126

-22

22

J126

-24

J126

-28

28

J126

-26

26

5V_Data

GPS_PWR

AUDIO_PA_12V

2.7V

0.

R2595

J126

-27 27

TX_EN

TX_EN

23

J126

-25 25

J126

-21 21

J126

-23

10

J126

-19 19

2

J126

-4

4

J127

-10

J126

-6

6

J126

-2

8

J126

-10

10

J126

-12

12

J126

-8

J126

-14

14 D3

EXT_B+

VCC

6

J127

-4

4

J127

-6

J125

-8

J127

-2

2

J125

-6

J125

-2

J125

-4

J125

-18

GPS_PWR

J125

-14

J125

-16

J127

-9 9

J125

-12

7

J127

-5 5

J127

-3 3

J127

-7

J127

-1 1

DGND

DGND

DGND

DGND

J125

-10

P10-2

P10-3

AGND

P10-1

S3

SWITCH

4 5

S3

SWITCH

3 6

S3

SWITCH

2 7

Inp

ut_

I_O

_cu

sto

m_d

efin

itio

n&

sim

_cr_

det

RX

_fo

r_d

iffe

ren

tial

_gp

s_rt

cm

GP

S_1

PP

S

RX

D_U

AR

T_2

J127

-8

8

RS232_CTS

RS232_RI

RS232_DSR

DSC_Enable

LEDS_Enable

TXD_UART_2 RX_for_differential_gps_rtcm

RXD_UART_2

Analog_Audio_In

Input_I_O_custom_definition&sim_cr_det

SIM_CR_Vcc3_TO_5Vdc

TS_Turn_on_stand_by

DSC_Uplink

DSC_Downlink

DSC_Enable

SIM_CR_I_O_Data

SIM_CR_Reset_RST

Wake_up_gprs_coverage_indicator

Analog_Audio_OUT&POWER_On_Off

MAN_TEST

RS232_RI

RS232_DSR

RS232_CTS

RS232_RTS

RS232_DCD

RS232_DTR

RS232_TXD

RS232_RXD

SIM_CR_Clock

TS

_Tu

rn_o

n_s

tan

d_b

y

IrD

A_S

elec

t

RS

232_

DC

D

An

alo

g_A

ud

io_O

UT

&P

OW

ER

_On

_Off

DS

C_E

nab

le

DS

C_D

ow

nlin

k

SIM

_CR

_Clo

ck

RS

232_

RX

D

RS

232_

RT

S

5

5V_Data

GPS_PWR

GPS_1PPS

AUDIO_PA_12V

2.7V

RS232_RXD

RS232_TXD

RS232_DTR

RS232_DCD

RS232_RTS

SIM

_CR

_Clo

ck

RS

232_

RX

D

RS

232_

RT

S

GP

S_A

nt_

Pw

r3_t

o_5

Vd

c

TX

D_U

AR

T_2

5

VCC

SIM

_CR

_I_O

_Dat

a

RS

232_

DT

R

MA

N_T

ES

T

RS

232_

RI

TX

D_U

AR

T_2

An

alo

g_A

ud

io_I

n

RS

232_

DS

R

DS

C_U

plin

k

RS

232_

TX

D

RS

232_

CT

S

SIM

_CR

_Vcc

3_T

O_5

Vd

c

SIM

_CR

_Res

et_R

ST

GPS_Ant_Pwr3_to_5Vdc

VCC

SIM

_CR

_I_O

_Dat

a

RS

232_

DT

R

MA

N_T

ES

T

RS

232_

RI

TX

D_U

AR

T_2

An

alo

g_A

ud

io_I

n

RS

232_

DS

R

DS

C_U

plin

k

RS

232_

TX

D

RS

232_

CT

S

SIM

_CR

_Vcc

3_T

O_5

Vd

c

SIM

_CR

_Res

et_R

ST

Inp

ut_

I_O

_cu

sto

m_d

efin

itio

n&

sim

_cr_

det

TS

_Tu

rn_o

n_s

tan

d_b

y

IrD

A_S

elec

t

RS

232_

DC

D

An

alo

g_A

ud

io_O

UT

&P

OW

ER

_On

_Off

DS

C_E

nab

le

DS

C_D

ow

nlin

k

AGND

TS_Turn_on_stand_by

SIM_CR_Vcc3_TO_5Vdc

Input_I_O_custom_definition&sim_cr_det

Analog_Audio_In

TX_EN

RS232_RXD

GPS_Ant_Pwr3_to_5Vdc

RX_for_differential_gps_rtcm

GPS_1PPS

RXD_UART_2

TXD_UART_2

Analog_Audio_OUT&POWER_On_Off

DHFA_SPKR_OUT

TX_EN

TS_Turn_on_stand_by

SoftGSM_EN

LEDS_Enable

AGND

DGND

DGND

DGND

DGND

VCC

VCC

VCC

VCC

SIM_CR_Clock

RS232_TXD

RS232_DTR

RS232_DCD

RS232_RTS

RS232_CTS

RS232_DSR

RS232_RI

MAN_TEST

Analog_Audio_OUT&POWER_On_Off

Wake_up_gprs_coverage_indicator

SIM_CR_Reset_RST

SIM_CR_I_O_Data

DSC_Enable

DSC_Downlink

DSC_Uplink

J12-1

SIM

_CR

_Clo

ck

Inp

ut_

I_O

_cu

sto

m_d

efin

itio

n&

sim

_cr_

det

DS

C_U

plin

k

DS

C_D

ow

nlin

k

DS

C_E

nab

le

SIM

_CR

_I_O

_Dat

a

13

J12-13

DGND

To d-10

To the UUT

To D-15

RF SMA Connector

ANT

DNP

(GPS RXD on GPS modeles)

(GPS TXD on GPS modeles)

for CSD call/PDP context indicator

3.0-6Vdc

NOTE:MIRROR TO G18/D15

MUTE

Diagnostic

BUTT-I I 15 PINs BUTT 12 PINsBUTT-I 15 PINs

79B02963C88-O

SHEET 5 OF 6

C9581

470.p

C9580

470.p

AGND

C9566

0.5p

AGND

DGND

R2583

DGND

4.7p

C9562

0.5p 0.5p

R2582

0.

L17

2.2m

120n

DGND

C9556

VCC

DGND

DGND

L13

U989

AGND

J12-30

30

DGND

120n

J12-27

27

J12-29

29

AGND

VCC

28

P6-1

1

26

J12-25

25

J12-28

J12-23

23

J12-26

J12-22

22

J12-24

24

21

J12-20

20

19

J12-18

18

J12-21

15

J12-17

17

J12-19

DGND

J12-16

16

J12-15

11

J128-13

13

12

J128-11

8

J128-10

10

J128-12

7

J128-9

9

J128-8

5

J128-7

4

J128-6

6

J128-5

2

J128-4

J128-1

1

J128-3

3

J128-2

M1

PIN

11

PIN

22

PIN

33

27

J128-29

29

CONTACT

28

J128-27

24

J128-26

26

J128-28

25

J128-24

21

J128-23

23

J128-25

20

J128-22

22

J128-21

18

J128-20

17

J128-19

19

J128-18

16

J128-17

15

J128-14

14

J128-16

10K

J128-15

10K

R2577

2

R2576

4

J124

-5 5

P6-2

J124

-3 3

J124

-4 2

J124

-1 1

J128-36

36

J124

-2

35

J128-34

34

J128-33

33

J128-35

30

J128-32

32

J128-31

31

J128-30

47K

R2603

Q37

5V_Data

DGND

DGND

10u

C9558

AUDIO_PA_12V

Q36

R2574100K

R2573

560.K

10K

R2579R2578

P11

-9 9

100.K

6

P11

-8 8 5

P11

-7 7

P11

-6 3

P11

-5 2

P11

-4 4

P11

-3

P11

-1 1

P11

-2

33p

C113

DGND AGND

120n

33p

C112

DGND

L11

220.n

C9571

100.p

C9589

100.p

C9588C9587

100.p

C9578

C9572

DGND

220.n

DGND

220.n

100.p

DGND

DGND

DGND

P11

-22 22

C9590

21

P11

-20 20

P11

-19

19

P11

-21

18

P11

-17

17

P11

-16 16

P11

-1813

P11

-15 15 14

P11

-13 10

P11

-12 12

P11

-14

11

P11

-10

4

J2-1 1

P11

-11

6

J13-

4

J13-

7 7

J13-

5 5

J13-

6

J13-

10 10

J13-

11 11

J13-

9 9

J13-

12 12

33p

C97

C96

33p33p

DGND

33p

C95

2

C94

J2-1

7

17

J13-

2

J2-1

6

16

J2-1

5

15

DGND

DGND

DGND

J2-1

4

1412

J2-1

3

13

J2-1

1

11

J2-1

2

J2-1

0

10

J2-9 98

J2-7 7

J2-8

J2-6 64

J2-5 5

J2-3 3

J2-4

J2-2 2

33p

J2-1

9

19

C92

J2-1

8

18

DGND

20

C91

J2-2

0

20

33p

18

J1-2

019

J1-1

8 17

J1-1

915

J1-1

6 16

J1-1

7

J1-1

5

C86 33p

C72 100n

C90

33p

C93

33p

C88

33p100n

DGND

33p

C89

DGND

C74

100n

C73

C87

33p

C85

DGND

J1-1

1 11

33p

J1-1

0 10

J1-9 97

J1-8 86

J1-7

J1-5 5

J1-6

J1-4 432

J1-3

J1-1

3 13

J1-2 12

J1-1

4 141

J1-1

2

DGND

DGND

J1-1

C102

33p

C101

16

J13-

17 17

DGND

33p

J13-

16

C99 C100

33p33p

C71

100n 33p

C8433p

15

J13-

8 8

DGND

C98

J13-

14 14

J13-

15

J13-

1 1

J13-

13 133

DGND

DGND

J12-12

12

J12-14

14

J13-

3

11

J12-10

10

9

J12-8

8

J12-11

J12-7

7

J12-9

6

J12-5

5

4

J12-3

3

J12-6

1

J12-2

2

J12-4 An

alo

g_A

ud

io_O

UT

&P

OW

ER

_On

_Off

An

alo

g_A

ud

io_I

n

DS

C_E

nab

le

EX

T_B

+

MA

N_T

ES

T

DS

C_U

plin

k

DS

C_D

ow

nlin

k

An

alo

g_A

ud

io_O

UT

&P

OW

ER

_On

_Off

An

alo

g_A

ud

io_I

n

2.7V

DS

C_D

ow

nlin

k

DS

C_D

ow

nlin

k

MA

N_T

ES

T

DS

C_E

nab

le

DS

C_U

plin

k2.7V

An

alo

g_A

ud

io_O

UT

&P

OW

ER

_On

_Off

DS

C_D

ow

nlin

k

DS

C_E

nab

le

DS

C_U

plin

k

MA

N_T

ES

T

An

alo

g_A

ud

io_I

n

EX

T_B

+

GP

S_1

PP

S

RX

D_U

AR

T_2

Mu

te

SIM

_CR

_Vcc

3_T

O_5

Vd

c

Analog_Audio_In

Input_I_O_custom_definition&sim_cr_det

Wake_up_gprs_coverage_indicator

Analog_Audio_OUT&POWER_On_Off

MAN_TEST

RS232_RI

RS232_DSR

RS232_CTS

rs232_rt

RS232_DCD

RS232_DTR

RS232_TXD

RS232_RXD

TS_Turn_on_stand_by

AGND_IN

DSC_Uplink

DSC_Downlink

DSC_Enable

SIM_CR_I_O_Data

SIM_CR_Reset_RST

SIM_CR_Vcc3_TO_5Vdc

SIM_CR_Clock

Analog_Audio_In

Input_I_O_custom_definition&sim_cr_det

TS_Turn_on_stand_by

AGND_IN

DSC_Uplink

DSC_Downlink

DSC_Enable

SIM_CR_I_O_Data

SIM_CR_Reset_RST

SIM_CR_Vcc3_TO_5Vdc

Wake_up_gprs_coverage_indicator

Analog_Audio_OUT&POWER_On_Off

MAN_TEST

RS232_RI

RS232_DSR

RS232_CTS

RS232_RTS

RS232_DCD

RS232_DTR

SIM_CR_Clock

DGND

DGND

DGND

DGND

VCC

VCC

VCC

TX

_EN

RX

_fo

r_d

iffe

ren

tial

_gp

s_rt

cm

RS

232_

RI

RS

232_

DS

R

RS

232_

CT

S

RS

232_

RT

S

RS

232_

DC

D

RS

232_

DT

R

RS

232_

TX

D

RS

232_

RX

D

2.7V_IN_SHEELD

TX_EN

Mute

STNDBY

5

TXD_UART_2

RS232_TXD

RS232_RXD

GPS_1PPS

RX_for_differential_gps_rtcm

GPS_Ant_Pwr3_to_5Vdc

TX_EN

RXD_UART_2

EX

T_B

+

TX

D_U

AR

T_2

RI

TxD

DTR

RxD

CTS

DSR

DCD 3

12

DGND DGND

DGND

MMBZ15VD

VR6

2 1

3

DGND

DTR

VR5

PC_TX

PC_RX

1PPS

RI

DSR

RTS

CTS

TxD

RxD

DCD

680p

C78

DGND

AGND

EXT SIM ConnectionsHandSet adapter

RJ-45 Connector

HeadSet Connctor.

DHFA MIC

RJ-45 Connector

D9 MALE

GPS

3Volt_VPP(NC)

Ext_Backup_batt(NC)

3Volt(NC)

1PPS_RTN (GND)

GND

DNP DNP

D9 FEMALE

DTE Orintation

SoftGSM Switching circuit

Connector SHEELD

79B02963C88-O

SHEET 6 OF 6

G

S

R70

4.7K

7002

Q17

D

DGND 4.7K

R69

C60

10u

10UF

C61

DGND

10UF

C59

DGND

12 34

AGND

DGND

VCC

S_CLK6

S_I|O2

S_PD

J118

S1

SWITCH

1G

ND

1

8G

ND

2

S_RESET4

5S

_VC

C1

7S

_VC

C2

3

U985

DGND

DGND

L1

120n

120n

1

R20

4.7K

SIM

-8 8

SIM

-14

SIM

-6 6

SIM

-2 2

SIM

-45

SIM

-3 3

SIM

-7 7

SIM

-5

120n

C80

33p

L3

680p

C79

DGND

DGND

C9551

680p

33pC83

33p

C82

C81 33p

33pC9552

120n

0

R2569

U986

J10-

1 1

DGND

J10-

3 3

J10-

2 25

J10-

4 47

J10-

6 6

J10-

5

J10-

8 8

J10-

7

2.2u

C7R82

100

Q26

5V_Data

DGND

DGND

330.n

C9585

DGND

C9586

100.n

330.n

C9584

DGND

330.n

C9583

5V_Data

DGND

V-4

VCC

26

C9582

33.u

T2OUT6

T3IN22

T3OUT7

T4IN19

T4OUT10

T5IN17

T5OUT12

V+27

R1OUTB16

R2IN9

R2OUT20

R3IN11

R3OUT18

T1IN24

T1OUT5

T2IN23

C2+1

C2-3

FORCEOFF14

FORCEON13

2G

ND

INVALID15

R1IN8

R1OUT21

DGND

MAX3238E

U993

C1+28

C1-25

C9568

33p

C9573

220.n

DGND

220.n

DGND

C9570

DGND

R83

0

J115

-2 2

J115

-1 1

J115

-4 4

J115

-3 3

J115

-6 6

J115

-5 58

J115

-7 7

12 34

DGND

VCC

J115

-8

J111

120n

L7

R2613

270.

R2612 270.

DGND

DGND

DGND

DGND

DGND

DGND

VR1815

DGND DGND

VR16 15

VR14

15

VR12

1515

11

VR11

P9-10

10

P9-11

8

P9-9

9

P9-77

P9-8

5

P9-6

6

P9-4

4

P9-5

2

P9-3

3

P9-1

1

P9-2

R2609

8.2K

DGNDDGND

8.2K

12K

R2608

12K

R2606

VCC

26

DGND

R2605

T3IN22

T3OUT7

T4IN19

T4OUT10

T5IN17

T5OUT12

V+27

V-4

9R2OUT

20

R3IN11

R3OUT18

T1IN24

T1OUT5

T2IN23

T2OUT6

C2-3

FORCEOFF14

FORCEON13

2G

ND

INVALID15

R1IN8

R1OUT21

R1OUTB16

R2IN

MAX3238E

U979

C1+28

C1-25

C2+1

DGND

DGND

J5-2

2

12

DGND

MMBZ15VD

VR9

3

12

MMBZ15VD

3

12

DGND

MMBZ15VD

VR7

3

MMBZ15VD

3

12

DGND

VR8

VR3

MMBZ15VD

3

12

VR4

MMBZ15VD

5

VR2

MMBZ15VD

3

12

J5-8

8

J5-5

6

J5-7

7

9

J5-6

3

J5-4

4

J5-9

1

J5-3

0.

R2617

J5-1

0.R2616

0.R2615

R2614 0.

11

DGND

C9565

33.u

J5-10

10

J5-11

100K

DGND

DGND

DGND

Z1

DGND

5V_Data

DGND

R2580

14X0

12

13X1

Y15

Y02

Y11

Z4

Z05

3

11A

B10

C9

EN6

GN

D8

VCC

16

VE

E7

X

DGND

5V_Data

U990

MC14053B

22.K

R2560

22.K

R2559

Q32U991

R2558

22.K

Q30

R2565

3.9K

DGND

R2568

100.

Q29

Q28

C9545

DGND DGND

100.n

C9546

330.n 330.n

C9544330.n

C9543

RS232_RI

TXD_MUX

RS

232_

Pre

sen

t

RS232_DTR

RS232_RXD

RS232_RTS

RS232_TXD

RS232_Present

DGND

5V_Data

RTS

Analog_Audio_OUT&POWER_On_Off

RTS

SoftGSM_EN

SoftGSM_EN

SoftGSM_EN

DSC_Downlink DSC_Enable

DTR_MUX

RS232_DCD

RTS_MUX

RS232_CTS

RS232_DSR

GPS_1PPS

1PPS

RX_for_differential_gps_rtcm RXD_UART_2

RTCM_IN

DS

C_U

plin

k

DS

C_D

ow

nlin

k

12V_SW

An

alo

g_A

ud

io_I

n

An

alo

g_A

ud

io_O

UT

&P

OW

ER

_On

_Off

RTCM_IN

PC_TX

TXD_UART_2

PC_RX

An

alo

g_A

ud

io_I

n

An

alo

g_A

ud

io_O

UT

&P

OW

ER

_On

_Off

SIM

_CR

_I_O

_Dat

a

DHFA_MIC_IN

DSC_Enable

DC_to_DC_12V

SPKR_Out

MIC_In

DS

C_U

plin

k

DS

C_D

ow

nlin

k

12V_SW

SIM

_CR

_Clo

ck

SIM

_CR

_Res

et_R

ST

SIM

_CR

_Vcc

3_T

O_5

Vd

c

Inp

ut_

I_O

_cu

sto

m_d

efin

itio

n&

sim

_cr_

det

SIM_CR_Reset_RST

SIM_CR_Vcc3_TO_5Vdc

SIM_CR_Clock SIM_CR_I_O_Data

Input_I_O_custom_definition&sim_cr_det

1

Parts ListEvaluation BoardModel FTN8071A P5

REFERENCE SYMBOL

MOTOROLA PART NO. DESCRIPTION

CapacitorsC1-6 2311049A07 ECAP_1UFC7 2311049A09 CAPP_2.2uC8-9 2311049J35 CAPP_22uC11 2113741F49 CAP_10nC12 2113743A19 CAP_100NFC14-15 2113741F33 CAP_2.2NFC24-30 2113740F39 CAP_33pC32-46 2113740F39 CAP_33pC47 2113741F49 CAP_10nC48-51 2113740F39 CAP_33pC52 2113741F21 CAP_680PFC60 2380090M24 CAPP_10uC62 2380090M24 CAPP_10uC68 2113740F39 CAP_33pC71-77 2113743A19 CAP_100NFC78-79 2113741F21 CAP680PFC80-105 2113740F39 CAP_33pC110-117 2113740F39 CAP_33pC9185 2311049A57 ECAP_10UFC9190 2311049C05 CAPP_47uC9192 2113743K17 CAP_330nC9201 2113743K17 CAP_330nC9204 2113743E20 CAP_100nC9205 2311049A01 CAPP_0.1uC9215 2113741F49 CAP_10nC9219 2113741F25 CAP_1nC9228 2113740F51 CAP_100pC9241 2113740F51 CAP_100pC9365 2311049A57 ECAP_10UFC9378 2113743E20 CAP_100nC9386 2113743E20 CAP_100nC9409 2113743K17 CAP_330nC9535-9536 9186929J01 880_1800MHZC9537-9538 2311049C13 CAPP_100uC9539 2311049A24 CAPP_68u

C9540 2311049A07 CAPP_1uC9541 2113743G25 CAP_3.3uC9542 2186201J02 CAP_22uC9543-9545 2113743K17 CAP_330nC9546 2113743K15 CAP_100nC9547-9548 2113743E20 CAP_100nC9549-9550 2113740F39 CAP_33pC9551 2113741F21 CAP_680PFC9552-9554 2113740F39 CAP_33pC9555 2311049A07 CAPP_1uC9556 2313748E31 CAPP_2.2mC9558 2311049A19 CAPP_10uC9559 2380090M39 CAPP_470uC9560 2311049A07 CAPP_1uC9561 2113928A01 CAP_1uC9562 2113740F19 CAP_4.7pC9563-9564 2311049C13 CAPP_100uC9565 2311049C08 CAPP_33uC9566 2113740F01 CAP_0.5pC9567-9568 2113740F39 CAP_33pC9569-9573 2113743A23 CAP_220nC9578 2113743A23 CAP_220nC9579 2113743A19 CAP_100NFC9580-9581 2113740F67 CAP_470pC9582 2311049C08 CAPP_33uC9583-9585 2113743K17 CAP_330nC9586 2113743K15 CAP_100nC9587-9590 2113740F51 CAP_100pCR1 4880304L02 LED_GRNCR2-11 4880304L01 LED_RED

DiodesD1 4813833B01 MBRS140D2 4813833A06 MBRD360D3 4813833B01 MBRS140D4-5 4813833A02 MBRD640D6-8 4880304L01 LED_RED

FusesF1 0904923K01 SMD_FUSE_HOLD

ConnectorsJ1-2 0909449B04 CONN_JJ3 3102151C30 CONN_PJ4 2804989M01 EDGE

REFERENCE SYMBOL

MOTOROLA PART NO. DESCRIPTION

2

J5 0909672B03 CONN_JJ10 0983365N01 EDGEJ12 2804989M01 EDGEJ13 0909467R02 CONN_JJ111 0909399T02 CONN_JJ115 0983365N01 EDGEJ118 0909399T02 CONN_JJ124 2886156U01 CONN_PJ125 0908606Y06 CONN_JJ126 2880471L02 CONN_PJ127 0908606Y05 CONN_JJ128-129 0988716K01 CONN_JJ130 0909032K01 CONN_J

CoilsL1-7 2462587T16 IDCTR_120nL10-13 2462587T16 IDCTR_120nL14 2503788S09 IDCTR_22uL15 2462587T16 IDCTR_120nL16 2462587P28 IDCTR_22uL17 249646M43 NO_DESC

ContactM1 3903920K01 CONTACT

ConnectorsP6 2880001R02 CONN_PP9 2802837C03 CONN_PP10 2880001R03 CONN_PP11 2802935S09 CONN_P

TransistorsQ3 4803676A04 BSS123Q4 4802393L34 FDV302PQ11 4802393L34 FDV302PQ14 4813824A17 PNP_3906LQ15-16 4813824A10 NPN_3904LQ17 4813823A07 TMOSFETN_7002Q18-23 4802393L34 FDV302PQ25 4803676A04 BSS123Q26 4802393L04 BSS84Q27 4813821A21 MTD20N03HDQ28-30 4803676A04 BSS123Q32 4803676A04 BSS123Q36-37 4803676A04 BSS123Q38 4809807C24 SI4463

REFERENCE SYMBOL

MOTOROLA PART NO. DESCRIPTION

Q39-41 4802393L34 FDV302PResistors

R2-3 0662057D17 RES_51KR4 0662057B47 RES_0R15 0662057B14 RES_470KR17 0662057B14 RES_470KR18-19 0662057A77 RES_15KR20 0662057A65 RES_4.7KR21 0662057A58 RES_2.4KR22-23 0662057A81 RES_22KR24-29 0662057A43 RES_560R30 0662057D30 RES_180KR31 0662057B16 RES_560KR32 0662057A89 RES_47KR33 0662057A63 RES_3.9KR35 0611077D97 RES_100R38 0662057C75 RES_1KR50 0662057C75 RES_1000_1KR52 0662057R68 RES_18.2KR53 0662057C61 RES_270R55-63 0662057C61 RES_270R64-66 0662057B14 RES_470KR67 0662057A58 RES_2.4KR68 0662057A73 RES_10KR69-70 0662057A65 RES_4.7KR77 0662057A89 RES_47KR78 0662057A87 RES_39KR79 0662057A65 RES_4.7KR82 0611077D97 RES_100R83 0662057B47 RES_0R84 0662057A85 RES_33KR1056 0662057P02 RES_15KR1068 0662057A87 RES_39KR1098 0662057A71 RES_8.2KR1104 0662057A67 RES_5.6KR2468-2469 0662057B47 RES_0R2518 0611079E05 RES_110KR2519 0662057B47 RES_0R2521 0662057P20 RES_20KR2527 0662057P95 RES_100KR2550-2552 0662057P02 RES_15KR2553 0662057A77 RES_15K

REFERENCE SYMBOL

MOTOROLA PART NO. DESCRIPTION

3

R2554 0604648P05 RES_0.1R2558-2560 0662057A81 RES_22KR2564 0662057A55 RES_1.8KR2565 0662057A63 RES_3.9KR2568 0662057A25 RES_100R2569 0662057B47 RES_0R2570 0662057C61 RES_270R2573 0662057B16 RES_560KR2574 0662057A97 RES_100KR2575 0662057A77 RES_15KR2576-2577 0662057A73 RES_10KR2578 0662057A97 RES_100KR2579 0662057A73 RES_10KR2580 0662057A97 RES_100KR2583 2113740F01 CAP_0.5pR2587 0662057A58 RES_2.4KR2588 0662057A63 RES_3.9KR2589 0662057G31 RES_221KR2590 0662057B47 RES_0R2593 0662057B14 RES_470KR2596 0662057A81 RES_22KR2597 0662057A71 RES_8.2KR2598 0662057A58 RES_2.4KR2599-2601 0662057C61 RES_270R2602 0662057A97 RES_100KR2603 0662057A89 RES_47KR2605-2606 0662057A75 RES_12KR2607 0662057A73 RES_10KR2608-2609 0662057A71 RES_8.2KR2611 0662057A49 RES_1KR2612-2613 0662057C61 RES_270R2614-2615 0662057B47 RES_0

SwitchesS1 4009060S01 SWITCH

REFERENCE SYMBOL

MOTOROLA PART NO. DESCRIPTION

S2 4008241G06 SWIT_ET01S3 4083849F04 SWITCHSW2 4004929K01 MOMENT_SWITCH

ShieldsSH1 2604044K01 SHIELD

SIMSIM 2808044H04 CONN_P

Integrated CircuitsU3-4 5113818A14 MC33202DR2U5 5104187K08 MAX603ESAU978 5105469E65 LP2951CU979 5109781E76 MAX3238EU980 5104187K46 LP2957ISU981 5185963A04 LP2981U982 5144751U01 TDA1519CTDU983 5108858K58 MAX771ESAU984 4803676A04 BSS123U985-987 2462587T16 IDCTR_120nU988 5113818A03 MC33072U989 2462587T16 IDCTR_120nU990 5113806A20 MC14053BU991 4803676A04 BSS123U992 5113818A03 MC33072U993 5109781E76 MAX3238E

Voltage SuppresorsVR2-9 4813832C28 ZENER_MMBZ15VDVR10 4813830G02 MMSZ4679TVR11-12 4813832C28 MMBZ15VDVR14 4813832C28 MMBZ15VDVR16 4813832C28 MMBZ15VDVR18 4813832C28 MMBZ15VD

REFERENCE SYMBOL

MOTOROLA PART NO. DESCRIPTION