TC65i AT-Commands Set. Manual

TC65i

Version:

01.100

DocId:

01.100

Date:

November 10, 2008

DocId:

THE USE OF THE PRODUCT INCLUDING THE SOFTWARE AND DOCUMENTATION (THE "PRODUCT") IS

SUBJECT TO THE RELEASE NOTE PROVIDED TOGETHER WITH PRODUCT. IN ANY EVENT THE PROVI-

SIONS OF THE RELEASE NOTE SHALL PREVAIL. THIS DOCUMENT CONTAINS INFORMATION ON CIN-

TERION PRODUCTS. THE SPECIFICATIONS IN THIS DOCUMENT ARE SUBJECT TO CHANGE AT

CINTERION'S DISCRETION. CINTERION WIRELESS MODULES GMBH GRANTS A NON-EXCLUSIVE

RIGHT TO USE THE PRODUCT. THE RECIPIENT SHALL NOT TRANSFER, COPY, MODIFY, TRANSLATE,

REVERSE ENGINEER, CREATE DERIVATIVE WORKS; DISASSEMBLE OR DECOMPILE THE PRODUCT

OR OTHERWISE USE THE PRODUCT EXCEPT AS SPECIFICALLY AUTHORIZED. THE PRODUCT AND

THIS DOCUMENT ARE PROVIDED ON AN "AS IS" BASIS ONLY AND MAY CONTAIN DEFICIENCIES OR

INADEQUACIES. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, CINTERION WIRELESS

MODULES GMBH DISCLAIMS ALL WARRANTIES AND LIABILITIES. THE RECIPIENT UNDERTAKES FOR

AN UNLIMITED PERIOD OF TIME TO OBSERVE SECRECY REGARDING ANY INFORMATION AND DATA

PROVIDED TO HIM IN THE CONTEXT OF THE DELIVERY OF THE PRODUCT. THIS GENERAL NOTE

SHALL BE GOVERNED AND CONSTRUED ACCORDING TO GERMAN LAW.

Transmittal, reproduction, dissemination and/or editing of this document as well as utilization of its contents and

communication thereof to others without express authorization are prohibited. Offenders will be held liable for

payment of damages. All rights created by patent grant or registration of a utility model or design patent are

reserved.

Trademark Notice

Bluetooth^TM is a registered trademark of Bluetooth SIG Inc.

Microsoft and Windows are either registered trademarks or trademarks of Microsoft Corporation in the United

States and/or other countries. All other registered trademarks or trademarks mentioned in this document are

property of their respective owners.

Contents

Introduction

1.1

Scope of the document

1.2

See also:

• Section 2.12.1, CME/CMS Error Code Overview

• Section 2.5.1, Verbose and numeric result codes

• Section 3.4, AT+CEER

1.9

Auxiliary Serial Interface

The second serial interface (ASC1) is designed as an additional interface for applications which need multiple

parallel access to the TC65i, e.g. to query status information while a data connection is in progress on ASC0.

However, the auxiliary interface provides only limited functionality:

• Multiplex mode via AT+CMUX is not supported.

• DTR, DSR, DCD, RING hardware lines do not exist. AT commands for controlling the behavior of these lines

(AT&D, AT&C, AT&S) can be used but will have no effect.

• CSD calls are not supported.

• Fax calls are not supported.

• When you set up packet switched connections take care that your application uses only AT commands,

parameters and signal lines supported on the ASC1 interface. For example, keep in mind that Microsoft Dial-

up connections are typically trying to request the DCD line status and that common modem drivers use to

send commands such as AT+CBST or ATS7, which may not be supported.

• No Autobauding. The hardware is not capable of automatically detecting the baudrate on this interface, so

the AT command which selects autobauding (AT+IPR=0) is not allowed and returns ERROR.

ASC1 is disabled when the multiplexer is enabled on the first serial interface ASC0. Yet, both ASC1 and the mul-

tiplexer channel 2 are using the same parameters, and thus, the same user defined profile (if any). As a result,

a user profile stored on multiplexer channel 2 takes effect on ASC1 after closing the multiplexer and starting up

ASC1. Likewise, a user profile stored on ASC1 will be loaded on multiplexer channel 2.

This may be a problem when ASC1 is not connected, but flow control (for example AT\Q1 or AT\Q3) is stored to

the user profile on the multiplexer channel 2. In this case, flow control takes effect on ASC1, when the multiplexer

is switched off. If then for example a large amount of URCs is generated, their transmission might be stopped

due to the flow control. To avoid this problem we recommend that you do not activate flow control on multiplexer

channel 2 when you set up a user profile with AT&W.

1.10

Serial Interface Flow Control

Flow control is essential to prevent loss of data or avoid errors when, in a data or fax call, the sending device is

transferring data faster than the receiving side is ready to accept. When the receiving buffer reaches its capacity,

the receiving device should be capable to cause the sending device to pause until it catches up.

There are basically two approaches to regulate data flow: Software flow control and hardware flow control. The

High Watermark (HWM) of the input/output buffer should be set to approximately 60% of the total buffer size, the

Low Watermark (LWM) is recommended to be about 30%. The data flow should be stopped when the buffer

capacity rises close to the High Watermark and resumed when it drops below the Low Watermark. The time

required to cause stop and go results in a hysteresis between the High and Low Watermarks.

1.10.1

Software Flow Control (XON/OFF Handshake)

Software flow control can be used to control the data flow in both directions from DTE to TC65i and from TC65i

to DTE. Software flow control uses different characters to stop (XOFF, decimal 19) and resume (XON, decimal

17) data flow. Hence, all data that represent XON or XOFF characters will be interpreted as control characters.

This applies also to characters included within the data stream to be transmitted (usually plain ASCII text files do

not inlude such characters). The only advantage of software flow control is that three wires would be sufficient

on the serial interface.

1.10.2

Hardware Flow Control (RTS/CTS Handshake)

Hardware flow control sets or resets the RTS/CTS wires. This approach is faster and more reliable, and there-

fore, the better choice. When the HWM is reached, CTS is set inactive. When the LWM is passed, CTS goes

active again. To achieve smooth data flow, ensure that the RTS/CTS lines are present on your application plat-

form.

Configuring hardware flow control

• Hardware flow control must be set on both sides: with AT\Q3 or AT+IFC in the ME and an equivalent RTS/

CTS handshake option in the host application.

• The default setting of the ME is AT\Q0 (no flow control) which must be altered to AT\Q3 (RTS/CTS hardware

handshake on). The setting is stored volatile and must be restored each time after rebooting the ME.

• AT\Q has no read command. To verify the current setting of AT\Q, simply check the settings of the active

profile with AT&V.

• Often, fax programs run an intialization procedure when started up. The intialization commonly includes

enabling RTS/CTS hardware handshake, eliminating the need to set AT\Q3 once again. However, before set-

ting up a CSD call, you are advised to check that RTS/CTS handshake is set.

Buffer design considerations

• Each serial interface (ASC0 and ASC1) of the TC65i uses two buffers, one for the uplink and one for the

downlink. Each buffer has a capacity of minimum 1024 bytes.

• Uplink direction (where ME is receiving data from host application):

CTS control is based on the filling level of the ME's receive buffer. When the application detects that CTS is

being deactivated it must instantly stop sending data to the ME's receive buffer. But still, after deactivation of

CTS, the receive buffer of the ME can accept another 512 bytes.

• Downlink direction (where ME is sending data to host application):

The transmit buffer of the ME can hold at least 1024 bytes. After deactivation of RTS the ME sends max. 2

more bytes and then stops transferring data to the application.

The maximum time RTS can be kept inactive without losing data is determined by the buffer size and the max-

imum possible over-the-air data rate. In any case, the local data rate between DCE and DTE (AT+IPR) should

be set to a value higher than the maximum possible over-the-air data rate.

• Buffer size recommended for the host application:

Just like the ME, the host application should include send and receive buffers for each serial interface. To

handle large amounts of data at high speed a buffer capacity of 1024 bytes is recommended. If the host appli-

cation is designed mainly for one direction (uplink or downlink) a lower buffer size will do for the direction

where less data is transferred.

In fact, the optimal size of the host application buffers is a matter of finding the balance between the amount

of data, data throughput, reaction time of the application when handling the buffer, processor performance

and available memory. To give an example, a small buffer size (such as 256 bytes) increases the frequency

of deactivating RTS/CTS and the frequency of flushing the buffer, thus diminishing the efficiency of the appli-

cation.

Also, please consider that RTS/CTS flow control cannot stop the data stream coming from the network, e.g.

in a GPRS or fax connection. So the lack of appropriate hardware flow control increases the risk of losing data

packets if, like in the case of UDP, the connection protocol has no or only minimum error handling functions.

Other network protocols are using high level flow control mechanisms. For example, to prevent loss of data

the TCP protocol uses retransmission algorithms, fax applications usually repeat the transfer of faulty pages.

1.11

Common PCN Handset Specification (CPHS)

The ME provides features to implement a device following the prerequisites of the Common PCN Handset Spec-

ification (CPHS) Phase 2.

CPHS Feature

Description/Remarks

AT command

Alternate Line Service

Using two phone numbers with one SIM card.

AT^SALS

Voice Message Waiting

Indicate the receipt of a short message coded as Voice Mes-

AT^SIND,

Indication

sage Waiting Indicator as defined by the CPHS Phase 2

AT+CMER, indicators

standard.

"vmwait1" and

"vmwait2"

Operator (Service pro-

Read specific Elementary Files (6F14h, 6F18h) from SIM.

AT+CRSM

vider) name from SIM

Network and Service Pro-

Lock/Unlock an ME to specific HPLMN and service provider.

AT+CLCK,

vider Lock

(AT+CPIN)

Call Forwarding

Get and set diverted call status. Access specific Elementary

AT+CCFC, AT+CRSM

File (6F13h) from SIM.

Customer Service Profile

Setting services and their menu entries depending on cus-

AT+CRSM

(CSP)

tomer profiles.

Information numbers

Hierarchically structured service numbers phonebook on

AT+CRSM

SIM according to CPHS 4.2 (mandatory).

Configuration Commands

The AT Commands described in this chapter allow the external application to determine the TC65i's behaviour

under various conditions.

2.1

AT&F Set all current parameters to manufacturer defaults

AT&F sets all current parameters to the manufacturer defined profile. All defined GPRS contexts which are not

activated or not online will be undefined if the non volatile storage of CGDCONT settings is not activated by the

AT^SCFG parameter "GPRS/PersistentContexts" (see AT+CGDCONT).

Syntax

Exec Command

AT&F[<value>]

Response(s)

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

Reference(s)

V.250

Parameter Description

<value>^(num)

[0]

Set all TA parameters to manufacturer defaults

Notes

• List of parameters reset to manufacturer default can be found in Section 23.6, Factory Default Set-

tings Restorable with AT&F.

• In addition to the default profile, you can store an individual one with AT&W. To alternate between the two pro-

files enter either ATZ (loads user profile) or AT&F (restores factory profile).

• Every ongoing or incoming call will be terminated.

2.2

AT&V Display current configuration

AT&V returns the current parameter setting. The configuration varies depending on whether or not PIN authen-

tication has been done and whether or not Multiplex mode is enabled (see AT+CMUX).

Syntax

Exec Command

AT&V[<value>]

Response(s)

ACTIVE PROFILE:

... (see Section 2.2.1, AT&V responses)

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

Reference(s)

V.250

Parameter Description

<value>^(num)

[0]

Profile number

Notes

• The value of \Q (flow control) is also determined by the AT+IFC command. In case the value set by AT+IFC

cannot be represented by a \Q equivalent, \Q255 will be displayed.

• The parameters of AT^SMGO can only be displayed after the SMS data from the SIM have been read success-

fully for the first time. Reading starts after successful SIM authentication has been performed, and may take

up to 30 seconds depending on the SIM used. While the read process is in progress, an attempt to read the

parameter will result in empty values.

• The parameter of AT+CSDH will only be displayed in SMS PDU mode, see AT+CMGF.

2.2.1

AT&V responses

The following tables show four different kinds of responses depending on whether or not the PIN is entered and

whether or not the Multiplex mode is enabled (see AT+CMUX).

Table 2.1: Current configuration on ASC0 / MUX channel 1 / USB (example)

PIN authentication done

No PIN authentication

ACTIVE PROFILE:

E1 Q0 V1 X4 &C1 &D2 &S0 \Q0 \V1

S0:000 S3:013 S4:010 S5:008 S6:000 S7:060 S8:000

S10:002 S18:000

+CBST: 7,0,1

+CRLP: 61,61,78,6

+CR: 0

+FCLASS: 0

+CRC: 0

+ICF: 3

+CMGF: 1

+IFC: 0,0

+CSDH: 0

+ILRR: 0

+CNMI: 0,0,0,0,1

+IPR: 115200

+ICF: 3

+CMEE: 2

+IFC: 0,0

^SCKS: 0,1

+ILRR: 0

^SSET: 0

+IPR: 115200

+CMEE: 2

^SMGO: 0,0

+CSMS: 0,1,1,1

^SACM: 0,"000000","000000"

^SLCC: 0

^SCKS: 0,1

^SSET: 0

+CREG: 0,1

+CLIP: 0,2

+CAOC: 0

+COPS: 0,0,"operator"

+CGSMS: 3

2.5

ATV Result code format mode

This command determines the contents of header and trailer transmitted with AT command result codes and

information responses. Possible responses are described in Section 2.5.1, Verbose and numeric result codes.

Syntax

Exec Command

ATV[<value>]

Response(s)

ERROR

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

Reference(s)

V.250

Parameter Description

<value>^{(num)(&W)(&V)}

[0]

Information response: <text><CR><LF>

Short result code format: <numeric code><CR>

1^(&F)

Information response: <CR><LF><text><CR><LF>

Long result code format: <CR><LF><verbose code><CR>

2.5.1

Verbose and numeric result codes

Verbose format

Numeric format

Meaning

command executed, no errors

CONNECT

link established

RING

ring detected

NO CARRIER

link not established or disconnected

ERROR

invalid command or command line too long

NO DIALTONE

no dial tone, dialling impossible, wrong mode

BUSY

remote station busy

CONNECT 2400/RLP

link with 2400 bps and Radio Link Protocol

CONNECT 4800/RLP

link with 4800 bps and Radio Link Protocol

CONNECT 9600/RLP

link with 9600 bps and Radio Link Protocol

CONNECT 14400/RLP

link with 14400 bps and Radio Link Protocol

ALERTING

alerting at called phone

DIALING

mobile phone is dialing

2.8

ATZ Set all current parameters to user defined profile

ATZ sets all current parameters to the user profile stored with AT&W. If a connection is in progress, it will be ter-

minated.

All defined GPRS contexts which are not activated or not online will be undefined if the non volatile storage of

CGDCONT settings is not activated by the AT^SCFG parameter "GPRS/PersistentContexts" (see AT+CGDCONT).

The user defined profile is stored to the non-volatile memory.

Syntax

Exec Command

ATZ[<value>]

Response(s)

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

Reference(s)

V.250

Parameter Description

<value>^(num)

[0]

Reset to user profile

Notes

• First the profile will be set to factory default (see AT&F). If there is a valid user profile (stored with AT&W), this

profile will be loaded afterwards.

• Any additional commands on the same command line may be ignored. A delay of 300 ms is required before

next command is sent, otherwise "OK" response may be corrupted.

2.9

AT+CFUN Set phone functionality

The AT+CFUN command serves to control the functionality level of the ME. It can be used to reset the ME, to

choose one of the SLEEP modes or to return to full functionality.

Intended for power saving, SLEEP mode reduces the functionality of the ME to a minimum and thus minimizes

the current consumption. Further information, particularly power supply ratings during the various operating

modes and the timing of hardware signals in SLEEP mode can be found in the "TC65i Hardware Interface

Description, Version 01.100".

SLEEP mode falls in two categories:

• NON-CYCLIC SLEEP mode <fun>=0

• and CYCLIC SLEEP modes, selectable as <fun>= 7 or 9.

NON-CYCLIC SLEEP mode permanently blocks the serial interface. The benefit of the CYCLIC SLEEP mode is

that the serial interface remains accessible and that, in intermittent wake-up periods, characters can be sent or

received without terminating the selected mode. This allows the ME to wake up for the duration of an event and,

afterwards, to resume power saving. Please refer to Section 2.9.1, Wake up the ME from SLEEP mode for a

summary of all SLEEP modes and the different ways of waking up the module.

For CYCLIC SLEEP mode both the ME and the application must be configured to use hardware flow control.

This is necessary since the CTS signal is set/reset every 0.9-2.7 seconds in order to indicate to the application

when the UART is active. The default setting of hardware flow control is AT\Q0 which must be altered to AT\Q3.

For use after restart you are advised to add it to the user profile saved with AT&W.

If both interfaces ASC0 and ASC1 are connected, hardware flow control must be set in either application. See

notes below for further detail.

SLEEP mode management if Java is started: The Java Virtual Machine remains active, but also enters the

SLEEP mode. AT commands can be sent from the Java application to the serial interface, no matter which

SLEEP mode was selected. This allows you to control the ME even if it is in NON-CYCLIC SLEEP mode.

The AT+CFUN test command returns the values of the supported parameters.

The AT+CFUN read command returns the current functionality value.

The AT+CFUN write command can be used to reset the ME, to choose one of the SLEEP modes or to return to

full functionality.

Syntax

Test Command

AT+CFUN=?

Response(s)

+CFUN: (list of supported <fun>s) , (list of supported <rst>s)

Read Command

AT+CFUN?

Response(s)

+CFUN: <fun>

Write Command

AT+CFUN=[<fun>[, <rst>]]

Response(s)

ERROR

+CME ERROR: <err>

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

Reference(s)

GSM 07.07

Unsolicited Result Codes

URC 1

^SYSSTART

Indicates that the ME has been started and is ready to operate. If autobauding is active (AT+IPR=0) the URC

is not generated.

If the ME is configured to enter the Airplane mode after restart or reset the following URC is received on boot-

up: "^SYSSTART AIRPLANE MODE". In this mode, only the AT commands listed in Section 23.4, Avail-

ability of AT Commands Depending on Operating Mode of ME can be used. For details please

refer to the AT^SCFG command, parameter <mapos>.

URC 2

^SYSSTART CHARGE ONLY MODE

Indicates that the ME has entered the CHARGE ONLY mode. This occurs if the charger is connected while

the ME is in POWER DOWN mode. If autobauding is active (AT+IPR=0) the URC is not generated. In

CHARGE ONLY mode the ME is neither registered to the GSM network nor are the serial interfaces fully

accessible. Only the AT commands listed in Section 23.4, Availability of AT Commands Depending

on Operating Mode of ME can be used. For further details on charging refer to the Hardware Interface

Description [2].

Parameter Description

<fun>^(num)

NON-CYCLIC SLEEP mode:

In this mode, the AT interface is not accessible. Consequently, after setting

<fun>=0, do not send further characters. Otherwise these characters remain

in the input buffer and may delay the output of an unsolicited result code.

The first wake-up event stops power saving and takes the ME back to full func-

tionality level <fun>=1.

[1]^(&F)(P)

Full functionality (no power saving).

If the ME is in one of the CYCLIC SLEEP modes you can issue AT+CFUN=1

to stop power saving and return to full functionality. If the ME is NON-CYCLIC

SLEEP mode, <fun>=1 can also be sent by the Java application.

Keep in mind that, unlike the reset command described below, this action does

not restart the ME but only changes the level of functionality. See parameter

<rst> for details on the reset.

CYCLIC SLEEP mode:

In this mode, the serial interface is shortly enabled while CTS is active. If char-

acters are recognized on the serial interface, the ME stays active for 2 seconds

after the last character was sent or received.

The ME exits SLEEP mode only, if AT+CFUN=1 is entered.

CYCLIC SLEEP mode:

In this mode, the serial interface is shortly enabled while CTS is active. If char-

acters are recognized on the serial interface, the ME stays active after the last

character was sent or received for at least the time, which can be configured

by AT^SCFG="PowerSaver/Mode9/Timeout",<psm9to> (temporary wakeup).

In contrast to SLEEP mode 7 assertion of RTS can also be used to temporarily

wake up the ME. In this case too, activity time is at least the time set with

AT^SCFG="PowerSaver/Mode9/Timeout",<psm9to>. RTS can be activated

either from ASC0 or ASC1.

The ME exits SLEEP mode only, if AT+CFUN=1 is entered.

<rst>^(num)

The parameter can only be used if the serial interface is enabled.

Due to the command syntax, you need to enter parameter <fun>, followed by <rst>, where <fun> is only a

placeholder and has no effect. See examples below.

[0]

Placeholder for <fun> as stated above.

ME resets and restarts to full functionality. After reset and restart, PIN 1

authentication is necessary (AT+CPIN). If autobauding is enabled, it is recom-

mended to wait 3 to 5 seconds before entering the first AT command. For

details on autobauding refer to Section 4.9.1, Autobauding.

Notes

•

The settings made with AT+CFUN apply to both serial interfaces ASC0 and ASC1.

•

CYCLIC SLEEP mode cannot be activated or resumed as long as data are buffered in one of the output buff-

ers of the ME (ASC0 or ASC1). This should be taken into account, because RTS may be unintentionally

asserted if, for example, one of the following scenarios occurs:

a) Hardware flow control is set in the ME (AT\Q3), but not in the host application (RTS/CTS handshake).

b) The two serial interfaces ASC0 and ASC1 are connected, but one of them is released, e.g. after closing or

deactivating the application connected to this interface.

In cases a) and b) data sent by the ME, such as URCs or outstanding AT command responses, will be buff-

ered in the output buffer of this interface, signalized by the active RTS line until the buffer is emptied.

Therefore, for CYCLIC SLEEP mode to work properly take care that the following requirements be met: Be

sure that data sent by the ME are collected on both interfaces. Activate hardware flow control on ME (TA) and

application side (TE). Avoid releasing one of the interfaces if any URCs are likely to occur on this interface.

•

CYCLIC SLEEP mode cannot be activated or resumed as long as data is buffered in one of the output buffers

of the ME (ASC0 or ASC1). Therefore, ensure that the following requirements be met:

a) If hardware flow control is set in the ME (AT\Q3), the host must also use hardware flow control.

b) Remember that AT\Q3 takes effect only on the interface where the command was set. Therefore, if both

interfaces ASC0 and ASC1 are connected ensure to set AT\Q3 on each interface. However, if only one inter-

face shall be operated ensure that, on the unused interface, AT\Q3 is neither enabled and nor stored to the

AT&W user profile. This is necessary to avoid that URCs, outstanding AT command responses or, after restart

even the "^SYSSTART" URC might be buffered on the unused interface without being collected by the host

application.

•

In Multiplex mode, the CFUN profile is shared by all multiplexer channels.

•

If the ME is in Multiplexer mode, it is not recommended to activate SLEEP mode with AT+CFUN=<fun>. The

best approach to properly control SLEEP mode in this case is to issue the PSC messages described in [6],

Section "Power saving control".

•

If the host application uses the USB interface, power saving must be configured both on the TC65i module

and on the USB host, i.e. the USB host must be set to Suspend mode (usually Selective or Global Suspend).

Otherwise, if you change only the AT+CFUN parameters, the selected <fun> level will be accepted but the

active USB keeps the module alive and thus prevents power saving until the USB plug is disconnected. Vice

versa, if the module is in SLEEP mode restarting the USB will cause the module to stop power saving

although the selected CFUN level does not change.

•

When a circuit-switched call is in progress, <fun>=7 or 9 can be activated without terminating the call. How-

ever, setting <fun>=0 during a circuit-switched call immediately disconnects this call.

•

To check whether power saving is on, you can query the status with the read command AT+CFUN? only if

the module is in full functionality mode or in CYCLIC SLEEP mode. If available, you can also take advantage

of the status LED controlled by the SYNC pin (see AT^SSYNC and [2]). With AT^SSYNC you can select differ-

ent modes of LED signalization during SLEEP modes (see Section 19.6.1, ME status indicated by status LED

patterns for details). However, the module can wake up temporarily from power saving without leaving its

CYCLIC SLEEP mode (without changing +CFUN "<fun>"), e.g. for a network scan after a loss of radio cov-

erage, or after receipt of serial data during CYCLIC SLEEP mode. During this "temporary wakeup state" the

LED will operate as if the ME was in full functionality mode.

•

Recommendation: In NON-CYCLIC SLEEP mode, you can set an RTC alarm to wake up the ME and return

to full functionality. This is a useful approach because, in this mode, the AT interface is not accessible.

2.9.1

Wake up the ME from SLEEP mode

A wake-up event is any event that causes the ME to draw more current. Depending on the selected mode, the

wake-up event either switches the SLEEP mode off and takes the ME back to full functionality AT+CFUN=1, or

activates the ME temporarily without terminating the selected SLEEP mode.

Definitions of the state transitions described in Table 2.3:

• Quit: ME exits SLEEP mode.

• Temporary: ME becomes active temporarily for the duration of the event and the mode-specific follow-up time

after the last character was sent or received on the serial interface.

• No effect: Event is not relevant in the selected SLEEP mode. The ME does not wake up.

Table 2.3: Wake-up events in NON-CYCLIC and CYCLIC SLEEP modes

Event

Selected mode:

<fun>=0

<fun>=7 or 9

Ignition line

No effect

RTS0 or RTS1 activation

Quit

Mode 7: No effect (RTS is only

used for flow control)

Mode 9: Temporary

Unsolicited Result Code (URC)

Quit

Temporary

Incoming voice or data call

Quit

Temporary

Any AT command (incl. outgoing

Not possible (UART disabled)

Temporary

SMS, voice or data call)

Incoming SMS (AT+CNMI is set to

No effect

0,0 (this is the default setting)

Incoming SMS (AT+CNMI is set to

Quit

Temporary

1,1)

GPRS data transfer

Not possible (UART disabled)

Temporary

RTC alarm (AT+CALA)

Quit

Temporary

AT+CFUN=1

Not possible (UART disabled)

Quit

In case of Java, the following events will cause the ME to quit NON-CYCLIC SLEEP mode <fun>=0:

- Toggling the RTS line

- Sending data on the serial interface

- Voice or data call (incoming and outgoing)

- AT+CFUN=1

- Terminating Java

2.10

AT^SMSO Switch off mobile station

AT^SMSO initiates the power-off procedure. High level of the module's PWR_IND pin and the URC "^SHUT-

DOWN" notify that the procedure has completed and the module has entered the POWER DOWN mode. There-

fore, be sure not to disconnect the operating voltage until PWR_IND is high or until the URC "^SHUTDOWN" is

displayed. Otherwise, you run the risk of losing data. For further details on how to turn off the module see the [2].

Syntax

Test Command

AT^SMSO=?

Response(s)

Exec Command

AT^SMSO

Response(s)

^SMSO: MS OFF

ERROR

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

Unsolicited Result Code

^SHUTDOWN

Indicates that the power-off procedure is finished and the module will be switched off in less than 1 second.

Notes

• Do not send any other AT command after AT^SMSO.

• If AT^SMSO is entered on one of the Multiplexer channels the ME closes the Multiplexer channels, terminates

the Multiplexer and deactivates all other functions. Then, the URC "^SHUTDOWN" will be issued on the phys-

ical serial interface (ASC0). The URC will be transmitted at the bit rate last activated on ASC0 for use with

the Multiplex driver.

• If both interfaces ASC0 and ASC1 are connected the URC appears on both of them.

• If the module is in NORMAL mode and the charger is connected to the VCHARGE line, the AT^SMSO com-

mand causes the module to shut down shortly and then start into the CHARGE ONLY mode. If the module is

in CHARGE ONLY mode the AT^SMSO command is not supported at all. In both cases, the module can only

be switched off by disconnecting the charger. See also [2].

2.12

AT+CMEE Mobile Equipment Error Message Format

AT+CMEE controls the format of the error result codes that indicates errors related to TC65i functionality. Format

can be selected between plain "ERROR" output, error numbers or verbose "+CME ERROR: <err>" and "+CMS

ERROR: <err>" messages.

Possible error result codes are listed in Table 2.4, General "CME ERROR" Codes (GSM 07.07)Table 2.5, Gen-

eral "CME ERROR" Codes (proprietary)Table 2.6, GPRS related "CME ERROR" Codes (GSM 07.07)Table 2.9,

Java related "CME ERROR" Codes (proprietary) and Table 2.8, SMS related "CMS ERROR" Codes (GSM

07.05).

In multiplex mode (refer AT+CMUX) the setting applies only to the logical channel where selected. The setting on

the other channels may differ.

Syntax

Test Command

AT+CMEE=?

Response(s)

+CMEE: (list of supported<errMode>s)

Read Command

AT+CMEE?

Response(s)

+CMEE: <errMode>

Write Command

AT+CMEE=<errMode>

Response(s)

ERROR

+CME ERROR: <err>

PIN ASC0 ASC1

USB MUX1

MUX2 MUX3

Charge

Last

Reference(s)

GSM 07.07

Parameter Description

<errMode>^{(num)(&W)(&V)}

0^(&F)(D)

Disable result code, i.e. only "ERROR" will be displayed.

Enable error result code with numeric values.

Enable error result code with verbose (string) values.

Example

To obtain enhanced error messages it is recommended to choose <errMode>=2.

AT+CMEE=2

2.12.1

CME/CMS Error Code Overview

Table 2.4: General "CME ERROR" Codes (GSM 07.07)

<err> Code

Text (if AT+CMEE=2)

phone failure

no connection to phone

phone adapter link reserved

operation not allowed

operation not supported

PH-SIM PIN required

PH-FSIM PIN required

PH-FSIM PUK required

SIM not inserted

SIM PIN required

SIM PUK required

SIM failure

SIM busy

SIM wrong

incorrect password

SIM PIN2 required

SIM PUK2 required

memory full

invalid index

not found

memory failure

text string too long

invalid characters in text string

dial string too long

invalid characters in dial string

no network service

network timeout

network not allowed - emergency calls only

network personalization PIN required

network personalization PUK required

network subset personalization PIN required

network subset personalization PUK required

service provider personalization PIN required

service provider personalization PUK required

corporate personalization PIN required

corporate personalization PUK required

PH-SIM PUK (master phone code) required

100

unknown

132

service option not supported

<err> Code

Text (if AT+CMEE=2)

133

requested service option not subscribed

134

service option temporary out of order

256

operation temporary not allowed

257

call barred

258

phone busy

259

user abort

260

invalid dial string

261

SS not executed

262

SIM blocked

263

invalid block

Table 2.5: General "CME ERROR" Codes (proprietary)

<err> Code

Text (if AT+CMEE=2)

673

audio manager not ready

674

audio format cannot be configured

705

SIM toolkit menu has not been configured

706

SIM toolkit already in use

707

SIM toolkit not enabled

737

+CSCS type not supported

738

+CSCS type not found

741

must include <format> with <oper>

742

incorrect <oper> format

743

<oper> length too long

744

SIM full

745

unable to change PLMN list

746

network operator not recognised

749

invalid command length

750

invalid input string

753

missing required cmd parameter

754

invalid SIM command

755

invalid file Id

756

missing required P1/2/3 parameter

757

invalid P1/2/3 parameter

758

missing required command data

759

invalid characters in command data

761

CTM call is not setup

764

missing input value

765

invalid input value

766

unsupported value or mode

767

operation failed

768

multiplexer already active

769

unable to get control of required module

<err> Code

Text (if AT+CMEE=2)

770

SIM invalid - network reject

771

call setup in progress

772

SIM powered down

773

SIM file not present

Table 2.6: GPRS related "CME ERROR" Codes (GSM 07.07)

<err> Code

Text (if AT+CMEE=2)

103

illegal MS

106

illegal ME

107

GPRS services not allowed

111

PLMN not allowed

112

location area not allowed

113

roaming not allowed in this location area

148

unspecified GPRS error

149

PDP authentication failure

150

invalid mobile class

Table 2.7: GPRS related "CME ERROR" Codes (proprietary)

<err> Code

Text (if AT+CMEE=2)

577

GPRS - activation rejected by GGSN

578

GPRS - unspecified activation rejection

579

GPRS - bad code or protocol rejection

580

GPRS - can't modify address

581

GPRS - no echo replyGPRS - CHAP close

582

GPRS - profile (CID) currently unavailable

583

GPRS - a profile (CID) is currently active

584

GPRS - combined services not allowed

585

GPRS - conditional IE error

586

GPRS - context activation rejected

587

GPRS - duplicate TI received

588

GPRS - feature not supported

589

GPRS - service not available

590

GPRS - unknown IE from network

591

GPRS - implicitly detached

592

GPRS - insufficient resources

593

GPRS - invalid activation state (0-1)

594

GPRS - invalid address length

595

GPRS - invalid character in address string

596

GPRS - invalid CID value

597

GPRS - invalid dialstring length

598

GPRS - mode value not in range

599

GPRS - invalid MAND information

<err> Code

Text (if AT+CMEE=2)

600

GPRS - SMS service preference out of range

601

GPRS - invalid TI value

602

GPRS - IPCP negotiation timeout

603

GPRS - LCP negotiation timeout

604

GPRS - LLC error

605

GPRS - LLC or SNDCP failure

606

GPRS - lower layer failure

607

GPRS - missing or unknown APN

608

GPRS - mobile not ready

609

GPRS - MS identity not in network

610

GPRS - MSC temporary not reachable

611

GPRS - message incompatible with state

612

GPRS - message type incompatible with state

613

GPRS - unknown message from network

614

GPRS - NCP close

615

GPRS - network failure

616

GPRS - no echo reply

617

GPRS - no free NSAPIs

618

GPRS - processing of multiple CIDs not supported

619

GPRS - no PDP context activated

620

GPRS - normal termination

621

GPRS - NSAPI already used

622

GPRS - address element out of range

623

GPRS - PAP close

624

GPRS - PDP context w/o TFT already activated

625

GPRS - PDP type not supported

626

GPRS - peer refuses our ACCM

627

GPRS - peer refuses our IP address

628

GPRS - peer refuses our MRU

629

GPRS - peer rerequested CHAP

630

GPRS - profile (CID) not defined

631

GPRS - unspecified protocol error

632

GPRS - QOS not accepted

633

GPRS - QOS validation fail

634

GPRS - reactivation required

635

GPRS - regular deactivation

636

GPRS - semantic error in TFT operation

637

GPRS - semantic errors in packet filter

638

GPRS - semantically incorrect message

639

GPRS - service type not yet available

640

GPRS - syntactical error in TFT operation

641

GPRS - syntactical errors in packet filter

<err> Code

Text (if AT+CMEE=2)

642

GPRS - too many RXJs

643

GPRS - unknown PDP address or type

644

GPRS - unknown PDP context

645

GPRS - user authorisation failed

646

GPRS - QOS invalid parameter

647

GPRS - FDN failure

648

GPRS - bad default PDP context parameters

649

GPRS - bad PDP context parameters

650

GPRS - PDP context already active

660

GPRS - no echo reply

661

GPRS - syntactical error in TFT operation

Table 2.8: SMS related "CMS ERROR" Codes (GSM 07.05)

<err> Code

Text (if AT+CMEE=2)

unassigned (unallocated) number

operator determined barring

call barred

short message transfer rejected

destination out of service

unidentified subscriber

facility rejected

unknown subscriber

network out of order

temporary failure

congestion

resources unavailable, unspecified

requested facility not subscribed

requested facility not implemented

invalid short message transfer reference value

invalid message, unspecified

invalid mandatory information

message type non-existent or not implemented

message not compatible with short message protocol state

information element non-existent or not implemented

111

protocol error, unspecified

127

interworking, unspecified

128

telematic interworking not supported

129

short message type 0 not supported

130

cannot replace short message

143

unspecified TP-PID error

144

data coding scheme (alphabet) not supported

145

message class not supported

<err> Code

Text (if AT+CMEE=2)

159

unspecified TP-DCS error

160

command cannot be actioned

161

command unsupported

175

unspecified TP-command error

176

TPDU not supported

192

SC busy

193

no SC subscription

194

SC system failure

195

invalid SME address

196

destination SME barred

197

SM rejected-duplicate SM

198

TP-VPF not supported

199

TP-VP not supported

208

do SIM SMS storage full

209

no SMS storage capability in SIM

210

error in MS

211

memory capacity exceeded

212

SIM application toolkit busy

213

SIM data download error

255

unspecified error cause

300

ME failure

301

SMS service of ME reserved

302

operation not allowed

303

operation not supported

304

invalid PDU mode parameter

305

invalid text mode parameter

310

SIM not inserted

311

SIM PIN required

312

PH-SIM PIN required

313

SIM failure

314

SIM busy

315

SIM wrong

316

SIM PUK required

317

SIM PIN2 required

318

SIM PUK2 required

320

memory failure

321

invalid memory index

322

memory full

330

SMSC address unknown

331

no network service

332

network timeout

340

no +CNMA acknowledgement expected

<err> Code

Text (if AT+CMEE=2)

500

unknown error

516

invalid length

519

invalid length or character

520

invalid character in text

532

SIM not ready

533

unread records on SIM

534

CB error unknown

535

PS busy

536

couldn't read SMS parameters from SIM

537

SM BL not ready

538

invalid parameter

539

ME temporary not available

548

invalid (non-hex) chars in PDU

549

incorrect PDU length

550

invalid MTI (message type indication)

551

invalid (non-hex) chars in address

552

invalid address (no digits read)

553

incorrect PDU length (UDL)

554

incorrect SCA length

556

invalid first octet (should be 2 or 34)

557

invalid command type

558

SRR bit not set

559

SRR bit set

560

invalid user data header IE

Table 2.9:

Java related "CME ERROR" Codes (proprietary)

<err> Code

Text (if AT+CMEE=2)

800

Java - unspecified error

801

Java - VM failure

802

Java - midlet not found

803

Java - midlet authentication failed

804

Java - midlet invalid descriptor

805

Java - midlet wrong configuration or profile

806

Java - liblet not found

807

Java - liblet authentication failed

808

Java - liblet invalid descriptor

2.13

AT+CSCS Select TE character set

The AT+CSCS write command informs the TA which character set <chset> is used by the TE. This enables the

TA to convert character strings correctly between TE and ME character sets. See also Section 1.6, Supported

character sets.

Note that when the TA-TE interface is set to 8-bit operation and the used TE alphabet is 7-bit, the highest bit will

be set to zero.

Syntax

Test Command

AT+CSCS=?

Response(s)

+CSCS: (list of supported<chset>s)

Read Command

AT+CSCS?

Response(s)

+CSCS: <chset>

Write Command

AT+CSCS=[<chset>]

Response(s)

ERROR

+CME ERROR: <err>

PIN ASC0 ASC1

USB MUX1

MUX2 MUX3

Charge

Last

Reference(s)

GSM 07.07, GSM

11.11

Parameter Description

<chset>^(str)

“GSM“^(&F)(P)

GSM default alphabet (GSM 03.38 subclause 6.2.1);

Note: This setting may cause software flow control problems since the codes

used to stop and resume data flow (XOFF = decimal 19, XON = decimal 17)

are interpreted as normal characters.

“UCS2“

16-bit universal multiple-octet coded character set (ISO/IEC10646 [32]); UCS2

character strings are converted to hexadecimal numbers from 0000 to FFFF;

e.g. "004100620063" equals three 16-bit characters with decimal values 65, 98

and 99.

2.14

AT^SCFG Extended Configuration Settings

AT^SCFG can be used to query and configure various settings of the TC65i.

AT^SCFG read command returns a list of all supported parameters and their current values.

AT^SCFG write command queries a configuration parameter (if no value is entered) or sets its value(s).

Input of parameter names is always coded in GSM character set, parameter values are expected to be given as

specified via AT+CSCS.

Syntax

Test Command

AT^SCFG=?

Response(s)

^SCFG: "AutoExec" , (list of supported <AutoExecCmd>), (list of supported <AutoExecType>), (list of

supported <AutoExecIndex>), (list of supported <AutoExecMode>), (max. string length of

<AutoExecATC>), (time range of <AutoExecPeriod>)

^SCFG: "Call/ECC", (list of supported <ecc>s)

^SCFG: "GPRS/ATS0/withAttach", (list of supported <gs0aa>s)

^SCFG: "GPRS/AutoAttach", (list of supported <gaa>s)

^SCFG: "GPRS/PersistentContexts", (list of supported <gpc>s)

^SCFG: "GPRS/RingOnIncomingData", (list of supported <groid>s)

^SCFG: "MEopMode/Airplane", (list of supported <map>s)

^SCFG: "MEopMode/Airplane/OnStart", (list of supported <mapos>s)

^SCFG: "MEShutdown/OnIgnition", (list of supported <msi>s)

^SCFG: "PowerSaver/Mode9/Timeout", (list of supported <psm9to>s)

^SCFG: "Radio/Band", (list of supported <rbp>s), (list of supported <rba>s)

^SCFG: "Radio/CNS", (list of supported <cns>s)

^SCFG: "Radio/OutputPowerReduction", (list of supported <ropr>s)

^SCFG: "Serial/USB/DDD" , (list of supported <deviceDescr>s) , (list of supported <descrIndex>s) ,

(max. string length of <langId>) , (max. string length of <vendorId>) , (max. string length of

<productId>) , (max. string length of <manufacturer>) , (max. string length of <product>) , (max. string

length of <serialNo>)

^SCFG: "Tcp/BufSize", (list of supported <tcpBufSize>)

^SCFG: "Tcp/IRT", (list of supported <tcpIrt>)

^SCFG: "Tcp/MR", (list of supported <tcpMr>)

^SCFG: "Tcp/OT", (list of supported <tcpOt>)

^SCFG: "Tcp/SAck", (list of supported <tcpSack>)

^SCFG: "Tcp/TTcp", (list of supported <tcpTtcp>)

^SCFG: "Tcp/WithURCs", (list of supported <tcpWithUrc>)

^SCFG: "Trace/Syslog/OTAP", (list of supported <otapTracer>)

^SCFG: "URC/CallStatus/CIEV", (list of supported <succ>s)

^SCFG: "URC/CallStatus/SLCC", (list of supported <sucs>s)

^SCFG: "URC/Datamode/Ringline", (list of supported <udri>s)

^SCFG: "URC/Ringline", (list of supported <uri>s)

^SCFG: "URC/Ringline/ActiveTime", (list of supported <urat>s)

^SCFG: "Userware/Autostart/AppName", (max. string lengths of <uaa>)

^SCFG: "Userware/DebugInterface", (<udbgif1>), (<udbgif2>), (<udbgif3>)

^SCFG: "Userware/Mode", (list of supported <umode>), (length of <uurl>), (range of supported

<uport>values)

^SCFG: "Userware/Stdout", (list of supported <if>), (list of supported <intvalue>), (<filename>), (list of

supported <logmode>)

Read Command

AT^SCFG?

Response(s)

^SCFG: "AutoExec" , <AutoExecCmd>, <AutoExecType>, <AutoExecIndex>, <AutoExecMode>,

<AutoExecATC>[, <AutoExecPeriod>, <AutoExecPeriodTimeLeft>]

^SCFG: "Call/ECC", <ecc>

^SCFG: "GPRS/ATS0/withAttach", <gs0aa>

^SCFG: "GPRS/AutoAttach", <gaa>

^SCFG: "GPRS/PersistentContexts", <gpc>

^SCFG: "GPRS/RingOnIncomingData", <groid>

^SCFG: "MEopMode/Airplane", <map>

^SCFG: "MEopMode/Airplane/OnStart", <mapos>

^SCFG: "MEShutdown/OnIgnition", <msi>

^SCFG: "PowerSaver/Mode9/Timeout", <psm9to>

^SCFG: "Radio/Band", <rbc>, <rba>

^SCFG: "Radio/CNS", <cns>

^SCFG: "Radio/OutputPowerReduction", <ropr>

^SCFG: "Serial/USB/DDD" , <deviceDescr>, <descrIndex>, <langId>, <vendorId>, <productId>,

^SCFG: "Tcp/BufSize", <tcpBufSize>

^SCFG: "Tcp/IRT", <tcpIrt>

^SCFG: "Tcp/MR", <tcpMr>

^SCFG: "Tcp/OT", <tcpOt>

^SCFG: "Tcp/SAck", <tcpSack>

^SCFG: "Tcp/TTcp", <tcpTtcp>

^SCFG: "Tcp/WithURCs", <tcpWithUrc>

^SCFG: "Trace/Syslog/OTAP", <otapTracer>

^SCFG: "URC/CallStatus/CIEV", <succ>

^SCFG: "URC/CallStatus/SLCC", <sucs>

^SCFG: "URC/Datamode/Ringline", <udri>

^SCFG: "URC/Ringline", <uri>

^SCFG: "URC/Ringline/ActiveTime", <urat>

^SCFG: "Userware/Autostart/AppName", <uaa>

^SCFG: "Userware/DebugInterface", <udbgif1>, <udbgif2>, <udbgif3>

^SCFG: "Userware/Mode"

^SCFG: "Userware/Stdout", <if>[, <intvalue>[, <filename>[, <logmode>]]]

Write Command

Automatic AT command execution

AT^SCFG="AutoExec" , <AutoExecCmd>, <AutoExecType>, <AutoExecIndex>[, <AutoExecMode>,

<AutoExecATC>[, <AutoExecPeriod>]]

Response(s)

^SCFG: "AutoExec" , <AutoExecCmd>, <AutoExecType>, <AutoExecIndex>, <AutoExecMode>,

<AutoExecATC>[, <AutoExecPeriod>, <AutoExecPeriodTimeLeft>]

ERROR

+CME ERROR: <err>

Write Command

Query/Configure Emergency numbers for SIM without ECC field

AT^SCFG="Call/ECC"[, <ecc>]

Response(s)

^SCFG: "Call/ECC", <ecc>

Write Command

(Continued)

Query/Configure Emergency numbers for SIM without ECC field

AT^SCFG="Call/ECC"[, <ecc>]

Response(s)

ERROR

+CME ERROR: <err>

Write Command

GPRS ATS0 with automatic attach

AT^SCFG="GPRS/ATS0/withAttach"[, <gs0aa>]

Response(s)

^SCFG: "GPRS/ATS0/withAttach", <gs0aa>

ERROR

+CME ERROR: <err>

Write Command

Automatic GPRS attach

AT^SCFG="GPRS/AutoAttach"[, <gaa>]

Response(s)

^SCFG: "GPRS/AutoAttach", <gaa>

ERROR

+CME ERROR: <err>

Write Command

Persistent GPRS contexts

AT^SCFG="GPRS/PersistentContexts"[, <gpc>]

Response(s)

^SCFG: "GPRS/PersistentContexts", <gpc>

ERROR

+CME ERROR: <err>

Write Command

Ring on incoming GPRS IP data packets

AT^SCFG="GPRS/RingOnIncomingData"[, <groid>]

Response(s)

^SCFG: "GPRS/RingOnIncomingData", <groid>

ERROR

+CME ERROR: <err>

Write Command

Enable/disable Airplane mode during operation

AT^SCFG="MEopMode/Airplane"[, <map>]

Response(s)

^SCFG: "MEopMode/Airplane", <map>

ERROR

+CME ERROR: <err>

Write Command

Airplane mode upon ME restart

AT^SCFG="MEopMode/Airplane/OnStart"[, <mapos>]

Response(s)

^SCFG: "MEopMode/Airplane/OnStart", <mapos>

ERROR

+CME ERROR: <err>

Write Command

Enable/disable shutdown by ignition line

AT^SCFG="MEShutdown/OnIgnition"[, <msi>]

Response(s)

^SCFG: "MEShutdown/OnIgnition", <msi>

ERROR

+CME ERROR: <err>

Write Command

Query/Set timeout value for power saving mode 9

AT^SCFG="PowerSaver/Mode9/Timeout"[, <psm9to>]

Response(s)

^SCFG: "PowerSaver/Mode9/Timeout", <psm9to>

ERROR

+CME ERROR: <err>

Write Command

Radio band selection

AT^SCFG="Radio/Band"[, <rbp>][, <rba>]

Response(s)

^SCFG: "Radio/Band", <rbp>, <rba>

ERROR

+CME ERROR: <err>

Write Command

Query/Enable/Disable Continuous Network Search

AT^SCFG="Radio/CNS"[, <cns>]

Response(s)

^SCFG: "Radio/CNS", <cns>

ERROR

+CME ERROR: <err>

Write Command

Radio output power reduction

AT^SCFG="Radio/OutputPowerReduction"[, <ropr>]

Response(s)

^SCFG: "Radio/OutputPowerReduction", <ropr>

ERROR

+CME ERROR: <err>

Write Command

Configuration of TCP parameter 'BufSize':

AT^SCFG="Tcp/BufSize"[, <tcpBufSize>]

Response(s)

^SCFG: "Tcp/BufSize", <tcpBufSize>

ERROR

+CME ERROR: <err>

Write Command

Configuration of TCP parameter 'InitialRetransmissionTimeout':

AT^SCFG="Tcp/IRT"[, <tcpIrt>]

Response(s)

^SCFG: "Tcp/IRT", <tcpIrt>

ERROR

+CME ERROR: <err>

Write Command

Configuration of TCP parameter 'MaxRetransmissions':

AT^SCFG="Tcp/MR"[, <tcpMr>]

Response(s)

^SCFG: "Tcp/MR", <tcpMr>

ERROR

+CME ERROR: <err>

Write Command

Configuration of TCP parameter 'OverallTimeout':

AT^SCFG="Tcp/OT"[, <tcpOt>]

Response(s)

^SCFG: "Tcp/OT", <tcpOt>

ERROR

+CME ERROR: <err>

Write Command

Configuration of TCP parameter 'Selective Acknowledge':

AT^SCFG="Tcp/SAck"[, <tcpSack>]

Response(s)

^SCFG: "Tcp/SAck", <tcpSack>

ERROR

+CME ERROR: <err>

Write Command

Configuration of Internet Service URCs:

AT^SCFG="Tcp/WithURCs"[, <tcpWithUrc>]

Response(s)

^SCFG: "Tcp/WithURCs", <tcpWithUrc>

ERROR

+CME ERROR: <err>

Write Command

Tracing:

AT^SCFG="Trace/Syslog/OTAP"[, <otapTracer>]

Response(s)

^SCFG: "Trace/Syslog/OTAP", <otapTracer>

SYSLOG ENABLED

ERROR

+CME ERROR: <err>

Write Command

USB Device Descriptor:

AT^SCFG="Serial/USB/DDD" [, <deviceDescr>, [<descrIndex>], [<langId>], <vendorId>,

<productId>, [<manufacturer>], [<product>], [<serialNo>]]

Response(s)

^SCFG: "Serial/USB/DDD" , <deviceDescr>, <descrIndex>, <langId>, <vendorId>, <productId>,

ERROR

+CME ERROR: <err>

Write Command

Configuration of URC "+CIEV: call" Call Status Indication

AT^SCFG="URC/CallStatus/CIEV"[, <succ>]

Response(s)

^SCFG: "URC/CallStatus/CIEV", <succ>

ERROR

+CME ERROR: <err>

Write Command

Configuration of URC "^SLCC" Call Status Indication

AT^SCFG="URC/CallStatus/SLCC"[, <sucs>]

Response(s)

^SCFG: "URC/CallStatus/SLCC", <sucs>

ERROR

+CME ERROR: <err>

Write Command

URC indication in datamode via Ring line:

AT^SCFG="URC/Datamode/Ringline"[, <udri>]

Response(s)

^SCFG: "URC/Datamode/Ringline", <udri>

ERROR

+CME ERROR: <err>

Write Command

URC indication via Ring line:

AT^SCFG="URC/Ringline"[, <uri>]

Response(s)

^SCFG: "URC/Ringline", <uri>

Write Command

(Continued)

URC indication via Ring line:

AT^SCFG="URC/Ringline"[, <uri>]

Response(s)

ERROR

+CME ERROR: <err>

Write Command

Duration of active RING line for URC indications:

AT^SCFG="URC/Ringline/ActiveTime"[, <urat>]

Response(s)

^SCFG: "URC/Ringline/ActiveTime", <urat>

ERROR

+CME ERROR: <err>

Write Command

Userware autostart status:

AT^SCFG="Userware/Autostart"[, <upwd>, <ua>]

Response(s)

^SCFG: "Userware/Autostart"[, <ua>]

ERROR

+CME ERROR: <err>

Write Command

Userware autostart application:

AT^SCFG="Userware/Autostart/AppName"[, <upwd>, <uaa>]

Response(s)

^SCFG: "Userware/Autostart/AppName"[, <uaa>]

ERROR

+CME ERROR: <err>

Write Command

Userware autostart delay:

AT^SCFG="Userware/Autostart/Delay"[, <upwd>, <uad>]

Response(s)

^SCFG: "Userware/Autostart/Delay"[, <uad>]

ERROR

+CME ERROR: <err>

Write Command

Userware configuration password:

AT^SCFG="Userware/Passwd"[, <upwd>_old, <upwd>_new, <upwd>_new]

Response(s)

^SCFG: "Userware/Passwd"

ERROR

+CME ERROR: <err>

Write Command

Userware debug interface:

AT^SCFG="Userware/DebugInterface"[, <udbgif1>, <udbgif2>[, <udbgif3>]]

Response(s)

^SCFG: "Userware/DebugInterface", <udbgif1>, <udbgif2>, <udbgif3>

ERROR

+CME ERROR: <err>

Write Command

Userware mode:

AT^SCFG="Userware/Mode"[, <umode>, <uurl>, <uport>]

Response(s)

^SCFG: "Userware/Mode", <umode>, <uurl>, <uport>

ERROR

+CME ERROR: <err>

Write Command

Standard output of userware:

AT^SCFG="Userware/Stdout"[, <if>[, <intvalue>][, <filename>][, <logmode>]]

Response(s)

^SCFG: "Stdout" , <if>[, <intvalue>[, <filename>[, <logmode>]]]

ERROR

+CME ERROR: <err>

Write Command

Watchdog configuration and control:

AT^SCFG="Userware/Watchdog"[, <wd>]

Response(s)

^SCFG: "Watchdog", <wd>

ERROR

+CME ERROR: <err>

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

Unsolicited Result Codes

URC 1

^SCFG: "AutoExec", <AutoExecState>, <AutoExecType>, <AutoExecIndex>,

If the event specified with <AutoExecType> occurs and the related AT command line is executed this URC

is issued.

URC 2

^SYSSTART AIRPLANE MODE

This URC is issued each time the Airplane mode is activated, no matter whether Airplane mode is set with

parameter <map>="on" or <mapos>="on". The URC notifies the user that only the AT commands supported

in Airplane mode are accessible. After leaving the Airplane mode the URC "^SYSSTART" indicates that the

ME has returned to Normal mode and the full set of AT commands is accessible again.

Parameter Description

<AutoExecCmd>^(str)(+CSCS)

AutoExec Command

This parameter serves to switch the Autoexec function on or off.

If it is switched off (<AutoExecCmd>=0), parameters following <AutoExecIndex> are ignored and all settings

at the given index are restored to their default values.

Value will be saved while switching off the TC65i via AT commands (e.g. AT+CFUN or AT^SMSO) and restored

on next power up.

“0“

Disable automatic execution of the AT command(s) specified with <AutoEx-

ecATC> at a given <AutoExecIndex>.

“1“

Enable automatic execution of the AT command(s) specified with <AutoExe-

cATC> at a given <AutoExecIndex>. Not allowed for <AutoExecType>=0

(DTR line activation) while multiplex mode is active, refer to AT+CMUX.

<AutoExecType>^(str)(+CSCS)

AutoExec Event Type

This parameter selects the kind of event used to automatically launch the AT command(s) specified with

<AutoExecATC>.

Value will be saved while switching off the TC65i via AT commands (e.g. AT+CFUN or AT^SMSO) and restored

on next power up.

“0“

Autoexec activity is driven by ASC0 DTR line activation (OFF-ON transition).

“1“

Autoexec activity is timer driven. To specify the time span use <AutoExecPe-

riod>.

<AutoExecIndex>^(str)(+CSCS)

AutoExec Command Index

This parameter specifies the command storage index. The following table shows the index ranges supported for

each variant of <AutoExecType>.

Value will be saved while switching off the TC65i via AT commands (e.g. AT+CFUN or AT^SMSO) and restored

on next power up.

<AutoExecType> value

<AutoExecType> event

Valid Indices

Autoexec activity is driven by ASC0 DTR

line activation

Autoexec activity is timer driven.

0-2

<AutoExecMode>^(str)(+CSCS)

AutoExec Command Mode

0...255

This parameter specifies details regarding the behavior of the TC65i when the AT command starts to be exe-

cuted.

Value is interpreted as a bit field, unused bits are reserved for future use (RFU) and shall be set to 0.

When a call is released by an Autoexec activity, no release indication may be issued on the first logical channel.

Value will be saved while switching off the TC65i via AT commands (e.g. AT+CFUN or AT^SMSO) and restored

on next power up.

Bit

Mask_hex

Mask_dec

Control

D₀

0x00

00: Ignore ongoing calls

D₁

0x01

01: Wait until all calls have ended

0x02

10: Dismiss any ongoing call

0x03

11: RFU

D₂

0x04

0: One shot action

1: Periodic action (for "AutoExec/Period" only)

D₃

0x08

RFU

D₄

0x10

RFU

D₅

0x20

RFU

D₆

0x40

RFU

D₇

0x80

128

RFU

<AutoExecATC>^(str)(+CSCS)

AutoExec AT command String

This parameter specifies the AT command(s) to be launched automatically. Each AT command is executed in

the same way as if it were entered online, this means that command concatenation is possible if supported by

the given commands. If serial multiplex mode is activated (AT+CMUX) the first logical channel is used, i.e. CSD

calls (data or fax) could be set up. If the TC65i is busy on the serial channel command execution will be delayed

until ongoing action is finished.

The first two characters of the automatically launched AT command shall be "at".

Please refer to examples below.

Value will be saved while switching off the TC65i via AT commands (e.g. AT+CFUN or AT^SMSO) and restored

on next power up.

<AutoExecPeriod>^(str)(+CSCS)

AutoExec Command Period

Parameter specifies the period after which <AutoExecATC> will be executed. Format is "hhh:mm:ss", where

characters indicate hours, minutes and seconds. This parameter applies to <AutoExecType>=1 only.

Value will be saved while switching off the TC65i via AT commands (e.g. AT+CFUN or AT^SMSO) and restored

on next power up.

When using this feature with running java applications, please consider the minimum time for the execution of

AT+CFUN or AT^SMSO is 15 seconds.

000:00:05...240:00:00

<AutoExecPeriodTimeLeft>^(str)(+CSCS)

AutoExec Command Period Left

This parameter shows the amount of time left until <AutoExecATC> will be executed. Format is "hhh:mm:ss",

where characters indicate hours, minutes and seconds. This parameter applies to <AutoExecType>=1 only.

Due to the internal activity and network signaling an execution delay of several seconds may occur for the overall

procedure.

000:00:00...240:00:00

<AutoExecState>^(str)(+CSCS)

AutoExec Command Status

This parameter is part of the Autoexec URC which is presented when a scheduled Autoexec activity is being

performed.

“1“

The value 1 indicates that the Autoexec activity specified with <AutoExec-

ATC> is currently executed.

<ecc>^(str)(+CSCS)

Emergency call numbers on non-ECC SIM

This parameter specifies emergency call numbers on SIM cards without ECC field. The parameter has no influ-

ence on the commonly used emergency numbers 112 and 911 which are always supported.

Please refer also to Section 7.3, ATD where you can find a list of emergency call numbers supported if no SIM

is inserted.

The value range of <ecc> is "0"..."255". To select or deselect an emergency number calculate the sum of the

values of all desired numbers and use the resulting value. For example, for "08" (2) and "118" (8) please enter

the value (10).

Parameter is global for the ME, non-volatile and will not be reset by AT&F.

“ 0“

No additional emergency numbers

“ 1“

000

“ 2“

“ 4“

110

“ 8“

118

“16“

119

“32“

999

“64“

Reserved

“128“

Reserved

“255“^(D)

All additional emergency call numbers are supported.

<gs0aa>^(str)(+CSCS)

GPRS ATS0 with Attach

This parameter can be used to control the behaviour of ATS0.

Parameter is global for all interfaces, volatile and will not be reset by AT&F.

“on“^(P)

When the ATS0=<n> (<n>>0) command is received, the MT will attempt to per-

form a GPRS attach.

“off“

When the ATS0=<n> (<n>>0) command is received, the MT will not attempt to

perform a GPRS attach.

<gaa>^(str)(+CSCS)

GPRS with AutoAttach

This parameter can be used to control whether the ME will perform a GPRS attach immediately after power-up

and registering to the network or not. If the setting is changed to "enabled" and the ME is not attached yet, it will

not initiate an attach immediately but after the next power-up and registration to the network.

Parameter is global for all interfaces, non volatile and will not be reset by AT&F.

“disabled“^(D)

GPRS auto attach is disabled

“enabled“

GPRS auto attach is enabled

<gpc>^(str)(+CSCS)

GPRS with persistent contexts

This parameter can be used to control whether the ME will store the GPRS context information defined by the

AT+CGDCONT volatile or non volatile.

Parameter is global for all interfaces, non volatile and will not be reset by AT&F.

“0“^(D)

GPRS context definitions are volatile.

“1“

GPRS context definitions are non-volatile and will not be reset by AT&F.

<groid>^(str)(+CSCS)

Ring on incoming GPRS IP data packets

This parameter can be used to control the behaviour of the RING line for incoming IP packets in GPRS online

mode.

Parameter is local for the interface, volatile and will not be reset by AT&F.

“on“

If the ME is in power saving mode 7 or 9 (see AT+CFUN) and hardware flow

control is in use (AT\Q3) and the RTS line is inactive and there are incoming

IP packets for a GPRS context which is online, then the RING line will be acti-

vated once, for a time which is configured by the parameter "URC/Ringline/

ActiveTime" (<urat>). The RING line to be used can be configured with the

parameter "URC/Ringline" (<uri>).

“off“^(P)

RING line is not activated for incoming IP packets.

<map>^(str)(+CSCS)

MEopMode/Airplane: Enable/disable Airplane mode during operation

The two parameters <map> and <mapos> can be used to enable/disable the Airplane mode. Airplane mode

shuts down the radio part of the ME (PA and receiver), causes the ME to log off from the GSM/GPRS network

and disables all AT commands whose execution requires a radio connection. A list of AT commands supported

during Airplane mode can be found in Section 23.4, Availability of AT Commands Depending on

Operating Mode of ME. The benefit of Airplane mode is that, at locations where no RF emission is allowed

(typically airplanes, hospitals etc.), the subscriber can continue using network-independent features rather than

powering off the entire device (e.g. a PDA or smartphone).

If the subscriber tries to use an AT command not available in Airplane mode the response "+CME ERROR:

unsupported AT command" is returned.

Parameter <map> allows entering or leaving the Airplane mode any time during operation, eliminating the need

to enter the SIM PIN again. It can be used no matter whether the parameter <mapos> is "on" or "off".

Parameter <map> is global for all interfaces, volatile and will not be reset by AT&F.

“on“

Activates Airplane mode and shuts down the radio part of the ME. The URC

"^SYSSTART AIRPLANE MODE" appears.

“off“^(P)

Deactivates Airplane mode, wakes up the radio part of the ME and restores

access to network-dependent AT commands. The URC "^SYSSTART"

appears.

<mapos>^(str)(+CSCS)

MEopMode/Airplane: Airplane mode upon ME restart

There are two ways to enter Airplane mode upon restart: One is using AT^SCFG with <mapos> as described

below.

Another approach is configuring the ME to restart into Airplane mode at a scheduled time. In this case, use the

AT+CALA command, set an alarm time and then switch the ME off. When the alarm time is reached the ME

wakes up to Airplane mode, no matter whether <mapos> was set "on" or "off".

Parameter <mapos> is global for all interfaces, non volatile and will not be reset by AT&F.

“on“

Causes the ME to enter the Airplane mode each time the ME is restarted or

reset.

After restart or reset, the URC "^SYSSTART AIRPLANE MODE" appears and

parameter <map> is "on". The SIM PIN can be entered using the AT+CPIN

command. This enables the ME to read data from the SIM and give access to

SIM PIN dependent AT commands which are available in Airplane mode, such

as phonebook commands or several SMS commands. To notify the user when

SIM data are accessible it is recommended to activate the "^SSIM READY"

URC and store its presentation mode to the user profile with AT&W.

To return from Airplane mode to Normal mode set the parameter <map> to "off"

as described above. If PIN authentication was already done, the ME will try

now to register to the GSM network.

“off“^(P)

Airplane mode will not be activated after ME restart or reset.

<msi>^(str)(+CSCS)

MEShutdown/OnIgnition: Enable/disable shutdown by IGT line

The parameter specifies two different switching modes of the ignition line IGT: The line may either be used only

to switch on the ME, or to switch it on and off.

By factory default the module's IGT line is configured only for switching on the ME. We recommend that great

care be taken before changing the switch mode of IGT. It is of vital importance that the following conditions are

met to ensure that IGT works properly as ON/OFF switch:

Switch-on condition: If the ME is off the IGT line must be asserted for at least 400 ms and then released.

Switch-off condition: If the ME is on the IGT line must be asserted for at least 1 s and then released. The switch-

off routine is identical with the shutdown procedure initiated by the AT^SMSO command, i.e. the ME performs an

orderly shutdown and issues the "^SHUTDOWN" URC.

Before switching off the ME wait at least 2 seconds after startup.

Furthermore, particular attention shall be given to the USB interface and the DTR signal: The USB interface and

the DTR line shall either be decoupled from IGT to avoid unintentional shutdown of the ME, or require special

precautions if you wish to restart the ME by plugging the USB cable or to toggle IGT from DTR. For further details

please refer to [2].

Parameter <msi> is global for all interfaces, non-volatile and will not be reset by AT&F.

“on“

Ignition line (IGT) can be used to switch on and off the ME.

“off“

Ignition line (IGT) can be used to switch on the ME.

<psm9to>^(str)(+CSCS)

Power saving mode 9 timeout

This parameter can be used to query or configure the wake up time for power saving mode 9 (see AT+CFUN with

parameter <fun>=9).

Parameter is global for the ME, volatile and will not be reset by AT&F.

5...20^(P)...36000

The granularity of the timeout value is 100ms (i.e. a value of 10 equal 1 sec-

ond). The minimum timeout value that can be applied is 5, but accuracy is only

guaranteed for timeout values greater than 20.

<rba>^(str)(+CSCS)

Allowed radio band(s)

The feature "Radio/Band" with its parameters <rba>, <rbp> and <rbc> can be used to set and query prefer-

ences for selecting frequency bands.

The TC65i normally uses an automode algorithm designed to recognize automatically the radio bands of the

current country, typically a combination of two bands. Commonly used dual-band combinations are, for exam-

ple, 900/1800 MHz in European countries or 850/1900 MHz in North America. The standard radio band combi-

nation of a country depends on the ARFCNs (Absolute Frequency Channel Number) and the MCCs (Mobile

Country Code) visible at the air interface. This enables the ME to easily find the standard band or band combi-

nation of a country every time after power-up and, thus, usually eliminates the need for the subscriber to make

any changes. So, if automode is used and the allowed bands are not restricted with <rba> the response param-

eter <rbc> shows the standard band(s) of the current area.

As an alternative, if any bands other than those automatically selected by the ME are needed, the automode

can be influenced using the AT^SCFG command. This may be necessary, for example, when running tests of

GSM applications, when access to specific radio bands shall be restricted or when the final product is not

intended for operation in certain countries.

Before changing the parameters <rba> or <rbp> ensure that no network activity occurs. The write command

cannot be executed when making a call, or sending / receiving short messages.

Execution of the write command causes the ME to deregister from and re-register to the network, no matter

whether the selected <rbp> or <rba> setting really changes. Therefore, it is useful to have the URC "+CREG"

enabled. The status of the SIM PIN authentication remains unchanged, eliminating the need to enter the SIM

PIN again after the change.

The parameter <rba> is intended to restrict the allowed bands to less than four bands. By default, all four bands

are allowed. Each band not contained in <rba> is generally disabled.

All bands of <rbp> must be contained in the range set with <rba>. The response parameter <rbc> will never

show a value outside the <rba> range. <rba> has precedence over <rbp> and <rbc>.

The <rba> value to select resp. deselect radio bands can be either a single band value or a multiple band value

as listed below.

Parameter <rba> is global for the ME, non-volatile and will not be reset by AT&F.

“1“

GSM 900 MHz

“2“

GSM 1800 MHz

“4“

GSM 1900 MHz

“8“

GSM 850 MHz

“3“

GSM 900 MHz + GSM 1800 MHz

“5“

GSM 900 MHz + GSM 1900 MHz

“10“

GSM 850 MHz + GSM 1800 MHz

“12“

GSM 850 MHz + GSM 1900 MHz

“15“

GSM 900 MHz + GSM 1800 MHz + GSM 850 MHz + GSM 1900 MHz

<rbp>^(str)(+CSCS)

Preferred radio band(s)

The write command will trigger the band selection, starting with the user preference specified by <rbp>. This

means bands contained in <rbp> will be searched first, regardless of the standard band combination of the cur-

rent country. The final result of the band selection can be read from <rbc>.

If <rbp> was a band or band combination which differs from the standard band(s) and the requested band(s)

are not visible at the air interface the ME reverts to the standard band(s) of this country. Please note that the

band selection procedure is independent of the registration procedure, i.e. the ME selects a band no matter

whether or not there is a PLMN (Public Land Mobile Network) the ME can register to. So, if the <rbp> was a

band or band combination supported by the country, but currently no PLMN can be found, the ME will select the

"preferred" band (indicated by <rbc>) without registering to the network. To avoid registration problems, for

example when the settings are configured for testing the GSM application it is recommended that the tester first

activates the desired band(s) on the test equipment and then executes the AT^SCFG write command. Besides

remember that the network registration also depends on the settings made with AT+COPS.

The <rbp> is volatile and cannot be read back with the AT^SCFG read command. This is because the value is

used only for triggering one single search operation.

The parameter <rbp> may be one of the single bands or band combinations listed below. All preferred bands

must be contained in the range of allowed bands set with <rba>, invalid combinations are not accepted. To give

priority to a certain single band or band combination and suppress all others simply select the same value both

for <rbp> and <rba>.

“1“

GSM 900 MHz

“2“

GSM 1800 MHz

“4“

GSM 1900 MHz

“8“

GSM 850 MHz

“3“

GSM 900 MHz + GSM 1800 MHz

“5“

GSM 900 MHz + GSM 1900 MHz

“10“

GSM 850 MHz + GSM 1800 MHz

“12“

GSM 850 MHz + GSM 1900 MHz

“15“

GSM 900 MHz + GSM 1800 MHz + GSM 850 MHz + GSM 1900 MHz

<rbc>^(str)(+CSCS)

Currently selected radio band(s)

<rbc> is the single band or band combination currently used by the ME, found either by the automode algorithm

or after the network search was triggered with <rbp>. The <rbc> value is saved on power down. When

restarted next time the ME tries to select the same band(s) if these are visible. If the band(s) stored with <rbc>

are not visible the ME uses the standard band(s) of the current country and consequently updates the <rbc>

value.

<rbc> is only a response parameter returned either after sending the read command AT^SCFG? or writing

AT^SCFG="Radio/Band".

In addition to <rbc> and to allow the subscriber to be notified whenever the selected band changes it is recom-

mended to activate the "+CIEV: band" (see Section 3.3, AT^SIND).

“1“

GSM 900 MHz

“2“

GSM 1800 MHz

“4“

GSM 1900 MHz

“8“

GSM 850 MHz

“3“

GSM 900 MHz + GSM 1800 MHz

“5“

GSM 900 MHz + GSM 1900 MHz

“10“

GSM 850 MHz + GSM 1800 MHz

“12“

GSM 850 MHz + GSM 1900 MHz

“15“

GSM 900 MHz + GSM 1800 MHz + GSM 850 MHz + GSM 1900 MHz

<cns>^(str)(+CSCS)

Continuous Network Search Mode

This parameter can be used to influence the time the ME takes to register to the network.

Parameter is global for the ME, volatile and will not be reset by AT&F.

“0“^(P)

Normal

When trying to register to a network the ME sleeps longer than in "Fast mode"

before restarting a network scan.

“1“

Fast

"Fast mode" reduces the time the ME sleeps before restarting a network scan

when trying to register.

Advantage: If the ME is out of network service it may take less time to find a

network.

Disadvantage: Higher current consumption while the ME is out of network ser-

vice.

Note: To monitor the search process it may be useful to have the "+CREG" URC enabled. Each time the network

search starts, the URC "+CREG" equals "2" (searching). When the network search stops, the URC is issued

again, indicating either "0" (not registered), or "1" (registered) or "5" (registered, roaming). As long as no network

can be found, the URC will be toggling between "2" and "0".

<ropr>^(str)(+CSCS)

Radio Output Power Reduction

According to 3GPP Rel99, output power reduction for multiple TX slots is a mandatory feature. The amount of

power reduction is configurable up to 3.0dB for 2TX, 4.8dB for 3Tx to 6dB for 4TX. To optimize heat dissipation,

power consumption and SAR values it is recommended to use full power reduction (value "3").

Parameter is global for all interfaces, volatile and will not be reset by AT&F.

“1“

Medium Reduction at GMSK (0dB reduction for 1TX and 2TX, 1.8dB for 3TX

and 3dB for 4TX)

“2“

Maximal Reduction at GMSK (0dB reduction for 1TX, 3dB for 2TX, 4.8dB for

3TX and 6dB for 4TX)

“3“^(P)

Maximal Reduction at GMSK (0dB reduction for 1TX, 3dB for 2TX, 4.8dB for

3TX and 6dB for 4TX)

<tcpBufSize>^(str)(+CSCS)

BufferSize

This value defines the default size of the TCP receive queue in bytes. Higher values allow higher throughput but

less number of parallel connections. The total throughput is limited by the GPRS/EDGE network resources and

cannot exceed the theoretical maximum gross throughput of 230Kbit.

Parameter is global for the ME and non-volatile. Use of default value is recommended. If changed the new value

takes effect the next time you start an Internet service with AT^SISO.

3000...5200^(&F)(D)...20000

Size of TCP receive buffer in bytes.

Possible number of parallel socket connections depending on buffer size:

- 5200 bytes (default): max. 8 connections

- 10000 bytes (medium): max. 4 connections

- 20000 bytes (high): max. 2 connections

<tcpIrt>^(str)(+CSCS)

Initial Retransmission Timeout (IRT)

1...3^(&F)(D)...60

This parameter determines the time (in seconds) the TCP/IP stack will wait

before starting the first retransmission of packets during the initial connection

establishment phase.

The TCP protocol ensures the retransmission of packets several times at

increasing intervals until some upper limit is reached.

This mechanism prevents packet loss and serious congestion problems.

Parameter is global for the ME and non-volatile. Use of default value is recom-

mended. If changed the new value takes effect the next time you start an Inter-

net service with AT^SISO.

<tcpMr>^(str)(+CSCS)

Maximum Number of Retransmissions (MR)

1...10^(&F)(D)...30

This parameter determines the maximum number of times to retransmit TCP

packets while the service is in connected state. If the service is still connecting

(connection setup) another algorithm applies.

The value set with <tcpMr> will be assumed as default for the <srv-

ParmTag> "tcpMR" when a new service profile is created with AT^SISS. In

each service profile, you can set another "tcpMR" value which has precedence

over the global value set with AT^SCFG. Existing service profiles are not

affected when you change the global value via AT^SCFG.

Parameter is global for the ME and non-volatile. Use of default value is recom-

mended.

<tcpOt>^(str)(+CSCS)

Overall TCP Timer for outstanding connections (tcpOT)

1...6000^(&F)(D)

This parameter specifies the number of seconds to wait before closing a con-

nection if TCP/IP packets are not acknowledged.

Setting the maximum value is practically equivalent to deactivating the tcpOT

mechanism because the maximum time would never be reached by the TCP/

IP stack.

The value set with <tcpOt> will be assumed as default for the <srv-

ParmTag> "tcpOT" when a new service profile is created with AT^SISS. How-

ever, in each service profile, you can set another "tcpOT" value which has

precedence over the global value set with AT^SCFG. Existing service profiles

are not affected when you change the global value via AT^SCFG.

Parameter is non-volatile. Use of default value is recommended.

<tcpSack>^(str)(+CSCS)

Selective Acknowledge (SAck)

This parameter concerns a set of TCP extensions to improve performance and to provide reliable operation. It

defines new TCP options for scaled windows and timestamps, which are designed to provide compatible inter-

working with TCPs that do not implement the extensions.

The set of TCP extensions to improve performance is described in RFC 1323. The value set with <tcpSack>

enables or disables the set of TCP extensions.

Parameter is global for the ME. Use of powerup value is recommended.

“0“

Disable set of TCP extensions.

“1“^(P)

Enable set of TCP extensions.

<tcpTtcp>^(str)(+CSCS)

Transaction/TCP (T/TCP)

This parameter concerns T/TCP, an extension of TCP to provide a transaction-oriented service.

T/TCP is described in RFC 1644. The value set with <tcpTtcp> enables or disables T/TCP.

Parameter is global for the ME. Use of powerup value is recommended.

“0“^(P)

Disable T/TCP extension.

“1“

Enable T/TCP extension.

<tcpWithUrc>^(str)(+CSCS)

URC mode or polling mode for Internet service commands

This parameter enables or disables the presentation of the following URCs related to Internet service com-

mands: "^SISR" URC, "^SISW" URC and "^SIS" URC for parameter <urcCause>=0 (Internet service events).

"^SIS" URCs with <urcCause>=1 or 2 used to indicate incoming Socket connections are always enabled.

Parameter is global for the ME and non-volatile.

“on“^(&F)(D)

Enable URCs related to Internet service commands.

Throughout the Chapter "Internet Service AT Commands" the mode is also

referred to as URC mode.

“off“

Disable URCs related to Internet service commands.

This requires the host application to employ polling techniques when using the

Internet service AT commands: The host application is responsible to retrieve

all status information needed to control an Internet session. The method is

referred to as polling mode.

<otapTracer>^(str)(+CSCS)

OTAP tracer

This parameter enables a trace output of the Over The Air procedure. The tracer is useful for obtaining additional

information when setting up an OTAP scenario. The output is provided on the interface on which the command

was entered. While the tracer is enabled the interface is used for trace output only, meaning that no AT com-

mands can be entered. The tracer will be switched off only by a reset of the module, e.g. after a completed OTAP

procedure.

“1“

Enable OTAP tracer.

<deviceDescr>^(str)(+CSCS)

Device Descriptor

This parameter determines whether to use the ME's standard USB Device Descriptor configuration (default) or

a Device Descriptor configuration customized by the application manufacturer.

Parameter is global, stored non-volatile in ME and not reset by AT&F. Setting will be active after TC65i restart.

“0“^(D)

Standard USB Device Descriptor of the ME.

If <deviceDescr>=0 is set all other parameters related to "Serial/USB/DDD"

cannot be changed. For use in a Windows environment, the "usbmodem.inf"

file delivered with TC65i shall be present.

Note that whenever the TC65i firmware is updated over the USB interface the

ME's standard configuration must be present. Therefore, before starting a

TC65i firmware download be sure that <deviceDescr>=0 is activated and,

under Windows, the ME's "usbmodem.inf" file can be found. Remember to

restart the ME after reverting to <deviceDescr>=0 and before starting the

firmware download.

“1“

Customer specific USB Device Descriptor.

If <deviceDescr>=1 is set all other parameters related to "Serial/USB/DDD"

can be changed.

Customizing the USB Device Descriptor configuration requires a unique Ven-

dor ID obtained from the USB Implementers Forum. For information please

refer to http://www.usb.org.

For use under Windows a customized INF file for the USB modem must be

present. An easy way to create this file is copying the ME's "usbmodem.inf" file

and overwriting the equivalent values changed with AT^SCFG, usually at least

the Vendor ID, Product ID and, optionally, the manufacturer string. This is

because the strings given for the customized "Serial/USB/DDD" parameters

must be identical with those contained in the INF file.

<descrIndex>^(str)(+CSCS)

Descriptor Index

As the TC65i shall be capable of holding 0 - 3 customized Device Desciptor configurations, the <descrIndex>

allows to create and select different parameter sets consisting of the parameters listed below.

Please note that TC65i Release 01.100 supports only one parameter set associated to value 0.

Parameter is global, stored non-volatile in ME and not reset by AT&F. Setting will be active after TC65i restart.

Please note that this parameter is effective only if the customized Device Descriptor <deviceDescr>=1 is

enabled.

“0“^(D)

Index for the first descriptor definition.

“1“

Future use.

“2“

Future use.

“3“

Future use.

<langId>^(str)(+CSCS)

Language ID

Please refer to USB.ORG [29] to find the language IDs currently defined for USB devices. If parameter

<langId> is not specified, the default value of the ME's standard USB Device Descriptor configuration applies

(US English).

Parameter is global, stored non-volatile in ME and not reset by AT&F. Setting will be active after TC65i restart.

Parameter length: maximum 4 characters.

Please note that this parameter is effective only if the customized Device Descriptor <deviceDescr>=1 is

enabled.

<vendorId>^(str)(+CSCS)

Vendor ID

This parameter represents the Vendor ID obtained from the USB Implementers Forum. The Vendor ID will,

together with the Product ID, be transmitted to the host during initialization. The given Vendor ID must be

included in the INF file needed for Windows.

Parameter is global, stored non-volatile in ME and not reset by AT&F. Setting will be active after TC65i restart.

Parameter length: maximum 4 characters.

Please note that this parameter is effective only if the customized Device Descriptor <deviceDescr>=1 is

enabled.

<productId>^(str)(+CSCS)

Product ID

Product ID (PID) defined by the application manufacturer to identify the USB device.

The Product ID will, together with the Vendor ID, be transmitted to the host during initialization. The given Prod-

uct ID must be included in the INF file needed for Windows.

Parameter is global, stored non-volatile in ME and not reset by AT&F. Setting will be active after TC65i restart.

Parameter length: maximum 4 characters.

Please note that this parameter is effective only if the customized Device Descriptor <deviceDescr>=1 is

enabled.

<manufacturer>^(str)(+CSCS)

Manufacturer name

Optional manufacturer string defined by the application manufacturer. If specified with <manufacturer> the

same string shall be included in the INF file needed for Windows.

Parameter is global, stored non-volatile in ME and not reset by AT&F. Setting will be active after TC65i restart.

Parameter length: maximum 63 characters.

Please note that this parameter is effective only if the customized Device Descriptor <deviceDescr>=1 is

enabled.

<product>^(str)(+CSCS)

Product string

Optional product name defined by the application manufacturer. If specified with <product> it is recommended

to include the same string into the INF file.

Parameter is global, stored non-volatile in ME and not reset by AT&F. Setting will be active after TC65i restart.

Parameter length: maximum 63 characters.

Please note that this parameter is effective only if the customized Device Descriptor <deviceDescr>=1 is

enabled.

<serialNo>^(str)(+CSCS)

Device's serial number

Optional serial number. Empty string if not used, like in the case of the ME'S standard USB Device Descriptor

configuration.

A serial number has several advantages. For example, it enables the host to assign the same virtual COM port

to same USB device even though the device is connected to another USB port. This eliminates the need for the

host to load the driver again.

Parameter is global, stored non-volatile in ME and not reset by AT&F. Setting will be active after TC65i restart.

If parameter <serialNo> is not specified, the default value of ME's standard USB Device Descriptor applies.

Parameter length: maximum 63 characters.

Please note that this parameter is effective only if the customized Device Descriptor <deviceDescr>=1 is

enabled.

<succ>^(str)(+CSCS)

CIEV Call Status Indication

This parameter can be used to control the behaviour of URC "+CIEV: call". See also AT+CIND, AT+CMER and

Section 7.1, Call Status Information.

Parameter is global for all interfaces and will not be reset by AT&F.

“restricted“^(P)

URC "+CIEV: call" will be issued only when a Call Status transition ends in

state "active" or "unknown" (see Section 7.1, Call Status Information) for a call

in the list of active calls.

“verbose“

URC "+CIEV: call" will be issued when any state transition (including transi-

tions beginning or ending in state "unknown") occurs in the list of active calls,

or when a traffic channel is established.

<sucs>^(str)(+CSCS)

SLCC Call Status Indication

This parameter can be used to control the behaviour of URC "^SLCC". See also AT^SLCC and Section 7.1, Call

Status Information.

Parameter is global for all interfaces and will not be reset by AT&F.

“restricted“

URC "^SLCC" will be issued only when a Call Status transition ends in state

"active" or "unknown" (see Section 7.1, Call Status Information) for a call in the

list of active calls

“verbose“^(P)

URC "^SLCC" will be issued when any state transition (including transitions

beginning or ending in state "unknown") occurs in the list of active calls, or

when a traffic channel is established.

<uri>^(str)(+CSCS)

URC RING line

This parameter can be used to control the behaviour of the RING line to indicate URCs (both for idle interfaces

and, if configured by the parameter "URC/Datamode/Ringline", if link is reserved) and, if configured, the indicator

for incoming IP packets (see parameter "GPRS/RingOnIncomingData" (<groid>).

Parameter is local for the interface, volatile and will not be reset by AT&F.

“off“

URC is not indicated by RING.

“local“^(P)

URC will be indicated by an activated RING line of the interface on which the

URC appears

“asc0“

URC is indicated by an activated RING0 line.

<udri>^(str)(+CSCS)

URC Datamode RING line

This parameter specifies whether RING or BREAK is used for the signaling of URCs when the TA-TE link is

reserved (e.g. during circuit-switched data calls, fax connections, in GPRS data mode or during the execution

of an AT command).

Parameter is global for all interfaces, volatile and will not be reset by AT&F.

“off“^(P)

URC will be indicated by BREAK

“on“

URC is indicated by an active RING line for a time which is configured by the

parameter "URC/Ringline/ActiveTime" (<urat>). The RING line which will be

used, can be configured by the parameter "URC/Ringline" (<uri>).

<urat>^(str)(+CSCS)

URC RING line Active Time

This parameter can be used to control how long the RING line is activated to indicate URCs (both for idle inter-

faces and, if configured by the parameter "URC/Datamode/Ringline" (<udri>), if link is reserved) and, if con-

figured by the parameter "GPRS/RingOnIncomingData", to indicate incoming GPRS IP data packets

(<groid>).

Parameter is global for all interfaces, volatile and will not be reset by AT&F.

“0“

RING line will be activated for a time between 4.6 and 9.2 ms.

“1“

RING line will be activated for about 100ms.

“2“^(P)

RING line will be activated for about 1s.

<ua>^(str)(+CSCS)

Userware Autostart

Specifies if the userware is started automatically on power-up.

If autostart is enabled, it is no longer possible to use the multiplexer (see AT+CMUX).

If the Java application starts, all current calls will be terminated.

The Userware/Autostart mechanism takes effect also in Airplane modeand CHARGE-ONLY-MODE.

Parameter is global, stored non-volatile in ME and not reset by AT&F.

“0“^(D)

Userware autostart disabled

“1“

Userware autostart enabled

<uaa>^(str)(+CSCS)

Userware Autostart AppName

Specifies the absolute path of the userware (the jar/jad file containing the desired application) to be started auto-

matically on power-up. The local flash file system is identified by: "A:", directory separator is "/" (002Fh). The

underline character "_" (005Fh) will not be supported.

Parameter is global, stored non-volatile in ME and not reset by AT&F.

Parameter length: maximum 100 characters.

<uad>^(str)(+CSCS)

Userware Autostart Delay

0^(D)...10000

Specifies the delay time (in 100ms) when the userware is started automatically

after power-up.

Parameter is global, stored non-volatile in ME and not reset by AT&F.

<upwd>^(str)(+CSCS)

Userware Password

Password used to change values of userware parameters.

Parameter is global, stored non-volatile in ME and not reset by AT&F.

The maximum length of a given password is 8 characters. It is allowed to have an empty password (this is the

value on delivery of the module).

CAUTION: Be careful not to lose the password. There is no way to reset or recover a forgotten password or to

obtain a new password from the manufacturer.

<udbgif1>^(str)(+CSCS)

Userware Debug Interface Local IP address

Local IP address of the module used by the userware debugger.

Parameter is global, volatile and not reset by AT&F.

<udbgif2>^(str)(+CSCS)

Userware Debug Interface Remote IP address

IP address of the host running the userware debugger.

Parameter is global, volatile and not reset by AT&F.

<udbgif3>^(str)(+CSCS)

Default interface flag for IP connections

Flag to select if the userware debug interface is the default interface for IP connections. Parameter is global,

volatile and not reset by AT&F.

[“0“]

Debug interface is not the default.

“1“

Debug interface is default for IP connections.

<umode>^(str)(+CSCS)

Userware Mode

Parameter is global, volatile and not reset by AT&F.

[“normal“]

Userware is started by AT command or autostart option.

“debug“

Userware is started by debugger on host side.

“test“

Userware is loaded from test server.

<uurl>^(str)(+CSCS)

Userware Mode: Location

Use of parameter depends on selected userware mode.

Parameter is global, volatile and not reset by AT&F.

If <umode>= "normal": Parameter is ignored.

If <umode>= "debug": File name of application stored on module. Maximum length: 126 characters.

If <umode>= "test": URL of the test server. Maximum length: 126 characters.

<uport>^(str)(+CSCS)

Userware Mode: Port

Use of parameter depends on selected userware mode.

Parameter is global, volatile and not reset by AT&F.

0...65535

If <umode>= "normal": Parameter is ignored.

If <umode>= "debug": Port number used by debugger.

If <umode>= "test": Port number of the test server.

<if>^(str)(+CSCS)

Interface for Java System.out

This parameter specifies the interface to be used for the Java standard output System.out. The selected inter-

face must be supported by the hardware.

“ASC0“

System.out is routed to the first serial interface.

The interface is shared between Java CommConnection and System.out. The

baud rate set for CommConnection applies also to System.out.

The value is global, stored non-volatile in ME and is not reset by AT&F.

“ASC1“^(D)

System.out is routed to the second serial interface.

The interface is shared between Java CommConnection and System.out. The

baud rate set for CommConnection applies also to System.out.

The value is global, stored non-volatile in ME and is not reset by AT&F.

“USB“

System.out is routed to the Universal Serial Bus interface.

“NULL“

Discard data.

The value is global, stored non-volatile in ME and is not reset by AT&F.

“UDP“

System.out is routed to a UDP socket. The parameter requires that the port

number be given with <intvalue>.

"UDP" is intended only for use with the Java IDE and will be set automatically

each time you start the debugging emulator of the TC65i (on-device debug-

ging). Closing the debugger causes the ME to reboot and automatically resets

the <if> value last selected. This eliminates any need for manually setting

"UDP" with AT^SCFG, and, besides, allows you to select another System.out

target to be used when not debugging. Due to this, the value "UDP" is volatile

unlike all other <if> values, and switching to "UDP" is not supported while

Java is running.

“FILE“

System.out is written into a file. Requires additional parameters <intvalue>,

<filename> and <logmode>. Because excessive writing to the ME's flash

file system decreases the life time of the flash memory, we recommend using

the "FILE" interface only during development phases.

The value is global, stored non-volatile in ME and is not reset by AT&F.

<intvalue>^(str)(+CSCS)

This parameter is required only if parameter <if> for the Java System.out is set to "UDP" or "FILE". Parameter

is global, stored non-volatile in ME and not reset by AT&F.

1...65535

If <if>= "UDP": UDP port number. It is recommended to use a number greater

than 1023.

If <if>= "FILE": Size of the log file in bytes, values less then 1024 are not sup-

ported.

<filename>^(str)(+CSCS)

This parameter is required only if parameter <if> for the Java System.out is set to "FILE". It specifies the abso-

lute path and the file name of the log. The local Flash File system is identified by: "A:", directory separator is "/"

(002Fh).

The underline character "_" (005Fh) is not supported.

The log is split into two concatenated files, each using half of the entire log size set with parameter

<intvalue>. Each file name consists of the name specified with parameter <filename> and the numeric

extension "0" or "1" automatically appended, for example "a:/java/log.txt.0" for the first part of the log and "a:/

java/log.txt.1" for the second part. When the first log file reaches half of the log size, the System.out is written to

the second file. When the second file is used up, the ME starts to overwrite the first one.

Parameter is global, stored non-volatile in ME and not reset by AT&F.

Parameter length: maximum 125 characters.

<logmode>^(str)(+CSCS)

This parameter is required only if parameter <if> for the Java System.out is set to "FILE". The parameter

selects the mode of writing System.out data to file.

Parameter is global, stored non-volatile in ME and not reset by AT&F.

“buffered“^(D)

Uses a buffer and a timer and acts like a write cache.

“secure“

Writes all output data byte by byte to the file.

<wd>^(str)(+CSCS)

Watchdog configuration and control

This parameter is used to configure the watchdog behaviour.

The use of the watchdog setting does not take care about network registration, file system operation and other

ongoing actions (hard reset).

Parameter is global for all interfaces, non volatile and will not be reset by AT&F.

“0“^(D)

Watchdog "do nothing". The watchdog has no affect.

“1“

Watchdog "re-start". The watchdog reboot the system.

“2“

Watchdog "shutdown". The watchdog switch off the system.

Notes

• Any changes to parameters of the Autoexec function will be saved and restored on next power-up only when

the ME is switched off via AT commands (e.g. AT+CFUN or AT^SMSO).

• Please keep in mind, that each time the ME is restarted the timers of all autoexec actions configured with

<AutoExecType>=1 and <AutoExecPeriod> will be reinitialized and restarted. As a result, an autoexec

action configured at a time later then a scheduled automatic restart would never be executed.

• Be careful using <AutoExecType>=1 with small period values and shutdown or reset AT commands, since

only little time remains to change these settings again after TC65i restart.

• If

<AutoExecATC> uses AT commands containing secret data, this information may be retrieved with

AT^SCFG?. For instance, this applies if using AT+CPIN.

• Parameters "GPRS/ATS0/withAttach" (<gs0aa>) and "GPRS/RingOnIncomingData" (<groid>) are avail-

able only for modules supporting GPRS.

Examples

EXAMPLE 1

Usage of "AutoExec":

Enable sending of a short message (SMS) on next DTR activation (OFF-ON transition). Sent SMS is

assumed to be stored at first location of storage selected with AT+CPMS and AT^SSMSS, i.e. SMS may be

sent either from SIM or ME storage.

Also refer to AT+CMSS and AT+CMGW. Since SMS transmission and ongoing calls are possible at the same

time there is no need to wait until all calls have ended (<AutoExecMode>=0).

AT+CMGF=1

Enable SMS text mode.

AT+CNMI=1,1

Enable "+CMTI:" URC to be indicated when a short

message is received.

AT+CMGD=1

Delete first SMS location.

AT+CMGW="01522400045",145

Start writing a short message.

>Test-SMS to be sent from storage!

Enter the text of the message. Finish with CTRL-Z.

+CMGW: 1

Confirms that message is stored to first location.

AT^SCFG="AutoExec",1,0,0,0,"AT+CMSS=1"

Enable execution on next DTR activation.

^SCFG: "AutoExec","1","0","0","0","at+cmss=1"

^SCFG: "AutoExec","0","1","0","0","","000:00:00","000:00:00"

^SCFG: "AutoExec","0","1","1","0","","000:00:00","000:00:00"

^SCFG: "AutoExec","0","1","2","0","","000:00:00","000:00:00"

If a DTR activation has occured the ME issues the URC "^SCFG: " followed by the response of the executed

command; the message reference in this case:

^SCFG:"AutoExec",0,0,1,0,"AT+CMSS=1"

Confirms that AT+CMSS=1 has been issued.

+CMSS: 16

EXAMPLE 2

Usage of "AutoExec":

Configure TC65i to perform a reset every 10 hours. The execution of the reset command shall be deferred

until after any calls have ended.

For details regarding software controlled power down refer to AT+CFUN and AT^SMSO.

AT^SCFG="AutoExec",1,1,2,5,"AT+CFUN=0,1","010:00:00"

After ten hours:

^SCFG:"AutoExec",1,1,2,5,"AT+CFUN=0,1"

Confirms that AT+CFUN=0,1 has been issued.

SYSSTART

TC65i has restarted. Remember that the

"^SYSSTART" URC will not appear if autobauding is

enabled.

EXAMPLE 3

Usage of "AutoExec":

Switch off the ME after three minutes without restarting it.

For details regarding software controlled power down refer to AT+CFUN and AT^SMSO.

Please keep in mind that if the GSM alphabet is enabled special characters within the executed AT command

shall be issued as escape sequences. A list of typical escape sequences can be found in Section 1.6.1, GSM

alphabet tables and UCS2 character values. For example, the caret character "^" included in all proprietary

AT commands shall be given as "\1B\14".

AT^SCFG="AutoExec",1,1,0,0,"AT\1B\14SMSO","000:03:00"

^SCFG: "AutoExec","0","0","0","0",""

^SCFG:

Please note that the indication of the escape

"AutoExec","1","1","0","0","ATSMSO","000:

sequence in the write command response depends

03:00","000:02:59"

on the used program.

^SCFG: "AutoExec","0","1","1","0","","000:00:00","000:00:00"

^SCFG: "AutoExec","0","1","2","0","","000:00:00","000:00:00"

After three minutes:

^SCFG:"AutoExec",0,1,1,0,"AT^SMSO"

^SMSO: MS OFF

^SHUTDOWN

Indicates that AT^SMSO was successfully executed.

The ME enters the POWER DOWN mode.

EXAMPLE 4

Usage of "AutoExec":

Deactivate a timer-driven Autoexec function configured at <AutoExecIndex> 2 (such as the periodic auto-

matic reset or the automatic switch-off functions configured in the preceding examples):

AT^SCFG="AutoExec",0,1,2

EXAMPLE 5

Usage of "URC/Ringline" and "URC/Datamode/Ringline":

AT+CSCS="GSM"

Switch to GSM character set.

AT^SCFG?

Query all parameters.

^SCFG:"URC/Datamode/Ringline","off"

While the TA-TE link is reserved URCs will be indi-

cated by BREAK.

^SCFG:"URC/Ringline","local"

URCs on this interface will be indicated by Ring line

associated to the interface (e.g. RING0 for ASC0).

AT^SCFG="URC/Datamode/Ringline","on"

^SCFG:"URC/Datamode/Ringline","on"

While the TA-TE link is reserved URCs will be indi-

cated by an activated "local" Ring line.

AT^SCFG="URC/Ringline","asc0"

2.15

AT^SM20

Set M20 compatibility mode

M20 is an earlier, widely used GSM engine. The AT^SM20 command selects different modes of responses

returned upon execution of the commands ATD and sms commands like e.g. AT+CMGW. Please note that the

AT^SM20 command has no effect on any other features and is not intended to adjust other differences between

M20 and TC65i.

Syntax

Test Command

AT^SM20=?

Response(s)

Read Command

AT^SM20?

Response(s)

^SM20:<CallMode>, <CmgwMode>

Write Command

AT^SM20=<CallMode>[, <CmgwMode>]

Response(s)

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3

Charge

Last

Parameter Description

<CallMode>^(num)

Call setup response mode

Applies only to voice calls.

Set compatibility to Cinterion Wireless Modules.

ME will return "OK" immediately after attempting a call with the ATD command.

In case of failure, additional call release indications, such as "NO DIAL TONE,

"NO CARRIER", "BUSY" will follow.

1^(&F)

Default call setup mode, compatible to M20.

ME will return "OK" in case of a successful connection, otherwise one of the

call release indications "NO DIAL TONE, "NO CARRIER", "BUSY" are indi-

cated.

<CmgwMode>^(num)

Response mode for sending and writing short messages

Applies to the sms commands like e.g. AT+CMGS and AT+CMGW command.

Set compatibility to Cinterion Wireless Modules.

ME will return +CMS ERROR: <err> when writing or sending of short mes-

sages fails.

1^(&F)

Default mode for sending and writing short messages, compatible to M20.

ME will return "OK", no matter whether or not sms command was successfully

executed.

Status Control Commands

The AT Commands described in this chapter allow the external application to obtain various status information

from the TC65i.

3.1

AT+CMER Mobile Equipment Event Reporting

This command controls details of the "+CIEV" URC presentation related to AT^SIND and AT+CIND. If registered

via these commands the URCs are sent whenever a value of the related indicator changes.

In addition, AT+CMER controls "^SLCC" URCs related to AT^SLCC. For details refer to Call Status Infor-

mation, AT^SLCC and AT^SCFG, parameter <sucs>.

The read command returns the URC presentation mode <mode> and among others, the indicator event reporting

status <ind>.

The write command enables and disables the presentation of "+CIEV: <indDescr>, <indValue>₁[, <ind-

Value>₂]" URCs. <indDescr> refers to the name of a "+CIEV" indicator and <indValue> is the new value of

this indicator. After AT+CMER has been switched on, URCs for all registered indicators will be issued. See exam-

ples provided in Section 3.2, AT+CIND and Section 3.3, AT^SIND.

Syntax

Test Command

AT+CMER=?

Response(s)

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

Read Command

AT+CMER?

Response(s)

+CMER: <mode>, <keyp>, <disp>, <ind>, <bfr>

Write Command

AT+CMER=[<mode>[, <keyp>[, <disp>[, <ind>[, <bfr>]]]]]

Response(s)

ERROR

+CME ERROR: <err>

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

Reference(s)

GSM 07.07

Unsolicited Result Code

+CIEV: <indDescr>, <indValue>₁[, <indValue>₂]

A value of an indicator has changed.

Parameter Description

<mode>^(num)

0^(&F)

Discard "+CIEV" and "^SLCC" URCs.

Discard "+CIEV" and "^SLCC" URCs when TA-TE link is reserved, e.g. in

online data mode. Otherwise they are forwarded directly to the TE.

Buffer "+CIEV" and "^SLCC" URCs in the TA while TA-TE link is reserved, e.g.

in online data mode, and flush them to the TE afterwards. Otherwise they are

forwarded directly to the TE.

Forward "+CIEV" and "^SLCC" URCs directly to the TE. If TC65i is in online

data mode, URCs are signaled via sending BREAK and stored in a buffer.

Once it is back in command mode e.g. after +++ was entered, all URCs stored

in the buffer will be output.

<keyp>^(num)

0^(&F)

Keypad event reporting is not supported by TC65i.

<disp>^(num)

0^(&F)

Display event reporting is not supported by TC65i.

<ind>^(num)

0^(&F)

Disable indicator event reporting.

Enable indicator event reporting.

<bfr>^(num)

0^(&F)

TA buffer of URCs defined within this command is cleared when <mode> 1..3

is entered.

(str)

Name of indicator; for a list of all supported indicators please refer to AT+CIND and AT^SIND.

<indValue>^(num)

Value of indicator; for a list of all values for the supported indicators please refer to AT+CIND and AT^SIND.

Notes

• If the ME operates on different instances (MUX channels 1, 2, 3 or ASC0/ASC1) avoid different settings for

routing and indicating SMS. For example, if messages shall be routed directly to one instance of the TE (set

with AT+CNMI, AT^SSDA), it is not possible to activate the presentation of URCs with AT+CMER or AT+CNMI

on another instance. Any attempt to activate settings that conflict with existing settings on another interface,

will result in "+CME ERROR", or accordingly "+CMS ERROR".

• It is recommended that priority be given to AT+CMER=<mode> 2 or 3. Otherwise, if <mode> equals 1, URCs

will be discarded in case of long running AT commands or an active data connection.

• If <mode> equals 3, URCs are signaled via sending BREAK only on ASC0 or ASC1.

3.2

AT+CIND Indicator control

The AT+CIND command controls the presentation of Indicator Event Reports related to various functions such

as battery charge level, signal quality, service availability, sound generation, indication of unread short mes-

sages, full SMS storage, call in progress or roaming activities.

Use of AT+CIND has become outdated. Rather we recommend the more powerful AT^SIND command which is

easier to use and provides additional indicators. All indicators provided by AT+CIND can be handled with

AT^SIND as well.

AT+CIND supports two ways to get the values related to indicators:

• One approach is to query the current status of each indicator by using the read command AT+CIND?. It

returns the status no matter whether the indicator has been registered with the write command

AT+CIND=[<mode>[,<mode>[,...]]].

• The other way is an event-driven notification based on the "+CIEV" URCs. In this case, the ME will automat-

ically send a message to the application, whenever the value of an indicator changes. The application should

be designed to react adequately when receiving a URC.

The presentation of these URCs depends on two settings:

- The indicators must be registered with the write command AT+CIND=[<mode>[,<mode>[,...]]]. When the

ME is switched on all of them are in registered mode. Any indicator can be excluded if deregistered with

<mode>=0. To register or deregister an indicator the AT+CIND write command requires to type the value

<mode>=1 or 0 exactly at the position where the indicator is located in the list. This is not necessary with

AT^SIND which allows to specify indicators by name. See examples below.

- The presentation of the registered indicators must be enabled with AT+CMER.

Syntax

Test Command

AT+CIND=?

Response(s)

+CIND: (<indDescr>, list of supported <indValue>s)[, (<indDescr>, list of supported <indValue>s)[,

...]]

Read Command

AT+CIND?

Response(s)

+CIND: <indValue>[, <indValue>[, ...]]

ERROR

+CME ERROR: <err>

Write Command

AT+CIND=<mode>[, <mode>[, ...]]

Response(s)

ERROR

+CME ERROR: <err>

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

Reference(s)

GSM 07.07

Parameter Description

<indValue>^(num)

Integer type value, which shall be in range of corresponding <indDescr>

<indDescr>^(str)

String values and their <indValue> ranges.

More indications are available via AT^SIND. Therefore use of AT^SIND for control of all indications is recom-

mended.

The following indications are accessible via AT+CIND:

“battchg“

Battery charge level 0..4 or 5 if no measuring is performed, e.g because no bat-

tery is connected. Also refer to AT^SBC.

“signal“

Signal quality (0..7) or (99) if not measurable

The indicated value is the bit error rate of the signal received. Bit errors are esti-

mated values. See also AT+CSQ.

“service“

Service availability (0-1)

0: Not registered to any network

1: Registered to home network or, if "roam"=1 then registered to another net-

work

“sounder“

Sounder activity (0-1)

Reports every event that causes the ME to generate a tone.

Value 1 means for example:

Incoming call - ME is ringing. Note that the URC "+CIEV: sounder" will be out-

put only if ringing tones are activated with AT^SRTC.

Waiting call - ME generates waiting call tone (if call waiting is enabled).

Outgoing call - ME generates Call Progress tone.

Outgoing call - ME generates BUSY tone.

The value changes to 0 when the tone stops.

“message“

Unread short message at memory location <mem1> (0-1); refer to AT+CPMS

“call“

Call in progress (0-1). Indicator value is "1" if at least one call is in state "active"

or "held".

Depending on the parameter <succ> selected with AT^SCFG the indicator

"call" will be issued

• when a state transition ends in state "active" or state "unknown", if

<succ>="restricted",

• when any state transition (including transitions beginning or ending in state

"unknown") occurs in the list of active calls or when a traffic channel is

established, if <succ>="verbose".

Also refer to Section 7.1, Call Status Information.

“roam“

Roaming indicator (0-1)

0: Registered to home network or not registered

1: Registered to other network

“smsfull“

A short message memory storage in the MT has become full (1) or memory

locations are available (0), i.e. range is (0-1)

“rssi“

Received signal (field) strength (0..5)

0: signal strength ≤ -112 dBm

1-4: signal strength in 15 dB steps

5: signal strength ≥ -51 dBm

99: not known or not detectable

Received signal (field) strength can also be obtained with AT+CSQ. However,

the signal strength is scaled to value range 0..31 by this command.

<mode>^(num)

Indicator is deregistered. The indicator will not be presented as "+CIEV" URC,

but can be queried with AT+CIND?.

[1]^(&F)(P)

Indicator is registered, indicator event report allowed.

Notes

• Due to its restrictive value range, indicator "call" does not clearly reflect specific call states (such as alerting,

active, held etc.), but rather serves to trigger the application to retrieve the new call status from the list of cur-

rent calls with the AT commands AT^SLCC, AT+CLCC or AT^SCNI.

• If AT^SCFG setting <succ>="verbose", indicator "call" will be issued also when a traffic channel is estab-

lished, or when a call enters states "terminating" or "dropped" (see Call Status Information).

In these cases, the relevant information about the cause of the display is available only from AT command

AT^SLCC.

Examples

EXAMPLE 1

^SYSSTART

AT+CPIN=9999

AT+CIND?

+CIND: 5,0,1,0,0,0,0,0

The battery is either full or no battery is connected to the ME. The bit

error rate of the signal quality is not available (since there is no call in

progress). The ME is registered to its home network.

AT+CMER=2,0,0,2

Now activate the Indicator Event Report with AT+CMER.

+CIEV: battchg,5

+CIEV: signal,0

+CIEV: service,1

+CIEV: sounder,0

+CIEV: message,0

+CIEV: call,0

+CIEV: roam,0

+CIEV: smsfull,0

+CIEV: rssi,5

Full receive signal strength.

ATD0123456;

Make a call.

+CIEV: sounder,1

A set of "+CIEV" URCs is received.

+CIEV: call,1

+CIEV: sounder,0

+CIEV: call,0

Called party hangs up.

NO CARRIER

AT+CIND=,,,0,,0

Deregister the indicators "sounder" and "call".

ATD0123456;

Dial the same call.

This time, no URCs are displayed.

NO CARRIER

Called party hangs up.

EXAMPLE 2

Deactivation of indicator "sounder" via AT+CIND

AT+CIND?

Query the current status of indicators.

+CIND: 5,0,1,0,1,0,0,0,4

AT+CIND=,,,0

To deactivate indicator "sounder" (= fourth item in list of indicators).

EXAMPLE 3

Deactivation of indicator "sounder" via AT^SIND

AT^SIND="sounder",0

To deactivate indicator "sounder".

^SIND: sounder,0,0

3.3

AT^SIND Extended Indicator Control

Designed for extended event indicator control AT^SIND

• offers greater flexibility than the standard command AT+CIND,

• offers several extra indicators,

• can show the current status of all indicators supported by AT+CIND and AT^SIND,

• can be used to register or deregister the indicators of both commands,

• displays all indicator event reports via "+CIEV" URCs.

Presentation mode of the generated URCs is controlled via AT+CMER.

The AT^SIND read command provides a list of all indicators supported by AT+CIND and AT^SIND. Each indica-

tor is represented with its registration mode and current value.

The AT^SIND write command can be used to select a single indicator in order to modify its registration and to

view the current value.

Syntax

Test Command

AT^SIND=?

Response(s)

^SIND: (<indDescr>, list of supported <indValue>s)[, (<indDescr>, list of supported <indValue>s)[,

...]], (list of supported <mode>s)

Read Command

AT^SIND?

Response(s)

^SIND: <indDescr>, <mode>, <indValue>

[^SIND: <indDescr>, <mode>, <indValue>]

In case of <indDescr>="eons"

^SIND: "eons", <mode>, <eonsOperator>, <servProvider>

In case of <indDescr>="nitz"

^SIND: "nitz", <mode>, <nitzUT>, <nitzTZ>, <nitzDST>

In case of <indDescr>="lsta"

^SIND: "lsta", <mode>, <lstaLevel>

ERROR

+CME ERROR: <err>

Write Command

AT^SIND=<indDescr>, <mode>

Response(s)

^SIND: <indDescr>, <mode>, <indValue>

In case of: <indDescr>="eons" and <mode>=2

^SIND: "eons", <mode>, <indValue>, <eonsOperator>, <servProvider>

In case of: <indDescr>="nitz" and <mode>=2

^SIND: "nitz", <mode>, <nitzUT>, <nitzTZ>, <nitzDST>

TC65i AT-Commands Set. Manual - part 1