Siemens TC65 Terminal. Manual (Version: 02.000)

Document Name:

Version:

02.000

Date:

June 2, 2006

DocId:

Status

General Notes

Product is deemed accepted by recipient and is provided without interface to recipient’s products. The documen-

tation and/or product are provided for testing, evaluation, integration and information purposes. The documen-

tation and/or product are provided on an “as is” basis only and may contain deficiencies or inadequacies. The

documentation and/or product are provided without warranty of any kind, express or implied. To the maximum

extent permitted by applicable law, Siemens further disclaims all warranties, including without limitation any im-

plied warranties of merchantability, completeness, fitness for a particular purpose and non-infringement of third-

party rights. The entire risk arising out of the use or performance of the product and documentation remains with

recipient. This product is not intended for use in life support appliances, devices or systems where a malfunction

of the product can reasonably be expected to result in personal injury. Applications incorporating the described

product must be designed to be in accordance with the technical specifications provided in these guidelines. Fail-

ure to comply with any of the required procedures can result in malfunctions or serious discrepancies in results.

Furthermore, all safety instructions regarding the use of mobile technical systems, including GSM products,

which also apply to cellular phones must be followed. Siemens or its suppliers shall, regardless of any legal the-

ory upon which the claim is based, not be liable for any consequential, incidental, direct, indirect, punitive or other

damages whatsoever (including, without limitation, damages for loss of business profits, business interruption,

loss of business information or data, or other pecuniary loss) arising out the use of or inability to use the docu-

mentation and/or product, even if Siemens has been advised of the possibility of such damages. The foregoing

limitations of liability shall not apply in case of mandatory liability, e.g. under the German Product Liability Act, in

case of intent, gross negligence, injury of life, body or health, or breach of a condition which goes to the root of

the contract. However, claims for damages arising from a breach of a condition, which goes to the root of the

contract, shall be limited to the foreseeable damage, which is intrinsic to the contract, unless caused by intent or

gross negligence or based on liability for injury of life, body or health. The above provision does not imply a

change on the burden of proof to the detriment of the recipient. Subject to change without notice at any time. The

interpretation of this general note shall be governed and construed according to German law without reference

to any other substantive 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 re-

served.

Trademark notice

Bluetooth™ is a registered trademark of Bluetooth SIG Inc.

Page 2 of 567

Contents

Introduction

1.1

Scope of the document

1.2

Related documents

[1]

TC65 Release Notes, Version 02.000

[2]

TC65 Hardware Interface Description, Version 02.000

[3]

TC65 Terminal Hardware Interface Description, Version 02.000

[4]

TC65 Java User's Guide

[5]

GPRS Startup User's Guide

[6]

Remote-SAT User's Guide

[7]

Multiplexer User's Guide

[8]

Multiplex Driver Developer's Guide for Windows 2000 and Windows XP

[9]

Multiplex Driver Installation Guide for Windows 2000 and Windows XP

[10]

Application Note 02: Audio Interface Design

[11]

Application Note 16: Updating TC65 Firmware

[12]

Application Note 17: Over-The-Air Firmware Update

[13]

Application Note 24: Application Developer's Guide

[14]

Application Note 22: Using TTY / CTM equipment with TC65

[15]

SIM Access Profile Interoperability Specification (Revision 1.0), issued by the Bluetooth Special Interest

Group

[16]

ISO/IEC10646: "Universal Multiple-Octet Coded Character Set (UCS)"; UCS2, 16 bit coding

[17]

ITU-T Recommendation V.24: List of definitions for interchange circuits between data terminal equipment

(DTE) and data circuit-terminating equipment (DCE)

[18]

ITU-T Recommendation V.250: Serial asynchronous automatic dialling and control

[19]

3GPP TS 100 918/EN 300 918 (GSM 02.04): General on supplementary services

[20]

3GPP TS 100 907 (GSM 02.30): Man-Machine Interface (MMI) of the Mobile Station (MS)

[21]

3GPP TS 23.038 (GSM 03.38): Alphabets and language specific information

[22]

3GPP TS 27.005 (GSM 07.05): Use of Data Terminal Equipment - Data Circuit terminating Equipment (DTE

- DCE) interface for Short Message Service (SMS) and Cell Broadcast Service (CBS)

[23]

3GPP TS 27.007 (GSM 07.07): AT command set for User Equipment (UE)

[24]

3GPP TS 27.060 (GSM 07.60): Mobile Station (MS) supporting Packet Switched Services

[25]

3GPP TS 51.011 (GSM 11.11): Specification of the Subscriber Identity Module - Mobile Equipment (SIM -

ME) interface

[26]

3GPP TS 11.14 (GSM 11.14): Specification of the SIM Application Toolkit for the Subscriber Identity Module

- Mobile Equipment (SIM - ME) interface

[27]

3GPP TS 22.101 (GSM 22.101): Service principles

[28]

Common PCN Handset Specification (CPHS) v4.2

Page 15 of 567

1.3 Document conventions

1.3

Document conventions

Throughout the document, the GSM engines are referred to as ME (Mobile Equipment), MS (Mobile Station), TA

(Terminal Adapter), DCE (Data Communication Equipment) or facsimile DCE (FAX modem, FAX board). When

the Siemens product names are required to distinguish the two models, TC65 is short for the engine type and

TC65T for the terminal.

To control your GSM engine you can simply send AT Commands via its serial interface. The controlling device

at the other end of the serial line is referred to as TE (Terminal Equipment), DTE (Data Terminal Equipment) or

plainly 'the application' (probably running on an embedded system).

All abbreviations and acronyms used throughout this document are based on the GSM specifications. For defi-

nitions please refer to TR 100 350 V7.0.0 (1999-08), (GSM 01.04, version 7.0.0 release 1998).

1.3.1

Quick reference table

Each AT command description includes a table similar to the example shown below. The table is intended as a

quick reference to indicate the following functions:

PIN:

Is the AT command PIN protected?

% Yes

! No

§ Usage is dependent on conditions specified for the command, or not all command types are PIN

protected (for example write command PIN protected, read command not).

Note: The table provided in Section 23.3, Available AT Commands and Dependency on SIM

PIN uses the same symbols.

ASC0:

Is the AT command supported on the first physical serial interface ASC0?

% Yes

! No

ASC1:

Is the AT command supported on the second physical serial interface ASC1?

% Yes

! No

USB:

Is the AT command supported on the USB interface?

% Yes

! No

MUXn:

Is the AT command usable on the Multiplexer channels MUX1, MUX2, MUX3?

% Yes

! No

§ AT command is usable, but under the restrictions specified in the section related to the command.

Note: The columns MUX1, MUX2 and MUX3 are relevant only when the GSM engine operates in Mul-

tiplexer mode, that is, when the first physical serial interface is partitioned into 3 virtual channels

by using the Multiplexer protocol. Usage is the same on ASC0 and MUX1.

Is the AT command supported in AIRPLANE mode?

% Yes

! No

§ In AIRPLANE mode, not all described functions are available. For example, the test or read com-

mand is usable, the write or execute command is not. Furthermore, only some of the listed

parameters can be changed in AIRPLANE mode. A typical example is AT^SCFG that controls dif-

ferent features.

Charge: Is the AT command supported in CHARGE ONLY mode?

% Yes

! No

§ AT command is usable, but under the restrictions specified in the section related to the command.

Last:

If commands are concatenated, this AT command must be the last one.

% Yes

! No

Note: See also Section 1.4, AT Command Syntax for details on concatenated AT commands.

Page 16 of 567

1.3 Document conventions

1.3.2

Superscript notation for parameters and values

Table 1.2: Symbols used to mark the type of parameters

Parameter type

Meaning

<param>^(num)

Parameter value must be numeric type

<param>^(str)

Parameter value must be string type

Table 1.3: Symbols used to indicate the correlations with other commands

Parameter option

Meaning

<param>^(&W)

Parameter value will be stored with AT&W

<param>^(&V)

Parameter value will be displayed with AT&V

<param>^(ˆSNFW)

Parameter value will be stored with AT^SNFW

<param>^(+CSCS)

Parameter value has to be (is) coded according to current setting of <chset> (see

AT+CSCS for details)

Table 1.4: Symbols used to mark different types of default values of parameters

Value option

Meaning

[x]

Default value: if the parameter is omitted, the value 'x' will be assumed

x^(&F)

Factory default value, will be restored to 'x' with AT&F

x^(P)

Powerup default value of a parameter which is not stored at power down

x^(D)

Delivery default value of a parameter which cannot be restored automatically

Page 18 of 567

1.4 AT Command Syntax

1.4

AT Command Syntax

The "AT" or "at" prefix must be set at the beginning of each command line. To terminate a command line enter

<CR>. Commands are usually followed by a response that includes "<CR><LF><response><CR><LF>". Through-

out this document, only the responses are presented, <CR><LF> are omitted intentionally.

Table 1.5: Types of AT commands and responses

AT command type

Syntax

Function

Test command

AT+CXXX=?

The mobile equipment returns the list of parameters and value

ranges set with the corresponding Write command or by internal

processes.

Read command

AT+CXXX?

This command returns the currently set value of the parameter or

parameters.

Write command

AT+CXXX=<...>

This command sets user-definable parameter values.

Exec(ution) command

AT+CXXX

The execution command reads non-variable parameters deter-

mined by internal processes in the GSM engine.

1.4.1

Using Parameters

• Optional parameters are enclosed in square brackets. If optional parameters are omitted, the current settings

are used until you change them.

• Optional parameters or subparameters can be omitted unless they are followed by other parameters. If you

want to omit a parameter in the middle of a string it must be replaced by a comma. See also example 1.

• A parameter value enclosed in square brackets represents the value that will be used if an optional parameter

is omitted. See also example 2.

• When the parameter is a character string, e.g. <text> or <number>, the string must be enclosed in quotation

marks, e.g. "Charlie Brown" or "+49030xxxx". Symbols in quotation marks will be recognized as strings.

• All spaces will be ignored when using strings without quotaton marks.

• It is possible to omit the leading zeros of strings which represent numbers.

• If an optional parameter of a V.250 command is omitted, its value is assumed to be 0.

Example 1: Omitting parameters in the middle of a string

AT+CCUG?

Query current setting

+CCUG: 1,10,1

AT+CCUG=,9

Set only the middle parameter

AT+CCUG?

Query new setting

+CCUG: 1,9,1

Example 2: Using default parameter values for optional parameters

AT+CFUN=7,0

Activate CYCLIC SLEEP mode, don't reset ME

AT+CFUN?

Query ME mode

+CFUN: 7

AT+CFUN=

Set ME back to normal (default parameters: 1,0)

+CFUN: 1

Page 19 of 567

1.4 AT Command Syntax

1.4.2

Combining AT commands on the same command line

You may enter several AT commands on the same line. This eliminates the need to type the "AT" or "at" prefix

before each command. Instead, it is only needed once at the beginning of the command line. Use a semicolon

as command delimiter.

The table below lists the AT commands you cannot enter together with other commands on the same line. Oth-

erwise, the responses may not be in the expected order.

AT command type

Comment

V.250 commands

with FAX commands (Prefix AT+F)

GSM 7.07 commands

with Siemens commands, Prefix AT^S)

GSM 7.05 commands (SMS)

To be used standalone

Commands starting with AT&

To be used standalone

AT+IPR

To be used standalone

Note: When concatenating AT commands please keep in mind that the sequence of processing may be different

from the sequential order of command input. Therefore, if the consecutive order of the issued commands and

the associated responses is your concern, avoid concatenating commands on the same line.

Page 20 of 567

1.5 Supported character sets

1.5

Supported character sets

The ME supports two character sets: GSM 03.38 (7 bit, also referred to as GSM alphabet or SMS alphabet) and

UCS2 (16 bit, refer to ISO/IEC 10646). See AT+CSCS for information about selecting the character set. Character

tables can be found below.

Explanation of terms

• International Reference Alphabet (IRA)

IRA means that one byte is displayed as two characters in hexadecimal format. For example, the byte 0x36

(decimal 54) is displayed as "36" (two characters). IRA is used here for input 8-bit or 16-bit data via terminal

devices using text mode. This means only characters 'A'..F','a'..'f' and '0'..'9' are valid.

• Escape sequences

The escape sequence used within a text coded in the GSM default alphabet (0x1B) must be correctly inter-

preted by the TE, both for character input and output. To the module, an escape sequence appears like any

other byte received or sent.

• Terminal Adapter (TA)

TA is an equivalent to Mobile Equipment (ME) which stands for the GSM module described here. It uses GSM

default alphabet as its character set.

• Terminal Equipment (TE)

TE is the device connected to the TA via serial interface. In most cases TE is an ANSI/ASCII terminal that

does not fully support the GSM default alphabet, for example MS Hyperterminal.

• TE Character Set

The character set currently used by Terminal Equipment is selected with AT+CSCS.

• Data Coding Scheme (dcs)

DCS is part of a short message and is saved on the SIM. When writing a short message to the SIM in text

mode, the dcs stored with AT+CSMP is used and determines the coded character set.

The behavior when encountering characters that are not valid characters of the supported alphabets is unde-

fined.

Due to the constraints described below it is recommended to prefer the USC2 alphabet in any external applica-

tion.

If the GSM alphabet is selected all characters sent over the serial line (between TE and TA) are in the range from

0 to 127 (7 Bit range). CAUTION: ASCII alphabet (TE) is not GSM alphabet (TA/ME) !

Several problems resulting from the use of GSM alphabet with ASCII terminal equipment:

• "@" character with GSM alphabet value 0 is not printable by an ASCII terminal program (e.g. Microsoft©

Hyperterminal®).

• "@" character with GSM alphabet value 0 will terminate any C string! This is because the 0 is defined as C

string end tag. Therefore, the GSM Null character may cause problems on application level when using a 'C'-

function as "strlen()". This can be avoided if it is represented by an escape sequence as shown in the table

below.

By the way, this may be the reason why even network providers often replace "@"with "@=*" in their SIM

application.

• Other characters of the GSM alphabet are misinterpreted by an ASCII terminal program. For example, GSM

"ö" (as in "Börse") is assumed to be "|" in ASCII, thus resulting in "B|rse". This is because both alphabets mean

different characters with values hex. 7C or 00 and so on.

• In addition, decimal 17 and 19 which are used as XON/XOFF control characters when software flow control

is activated, are interpreted as normal characters in the GSM alphabet.

When you write characters differently coded in ASCII and GSM (e.g. Ä, Ö, Ü), you need to enter escape

sequences. Such a character is translated into the corresponding GSM character value and, when output later,

the GSM character value can be presented. Any ASCII terminal then will show wrong responses.

Page 21 of 567

1.5 Supported character sets

1.5.1

GSM alphabet tables and UCS2 character values

This section provides tables for the GSM 03.38 alphabet supported by the ME. Below any GSM character find

the corresponding two byte character value of the UCS2 alphabet.

(For related mapping definition see: http://www.unicode.org/Public/MAPPINGS/ETSI/GSM0338.TXT)

Figure 1.1: Main character table of GSM 03.38 alphabet

1) This code is an escape to the following extension of the 7 bit default alphabet table.

2) This code is not a printable character and therefore not defined for the UCS2 alphabet. It shall be treated as the accom-

panying control character.

3) As the standard GSM alphabet does not provide a backspace functionality the TC65 is designed to use the GSM character

08 (hex 0x08) as backspace. This allows the user to easily erase the last character when using an ASCII terminal. On the

other hand, this solution requires entering the escape sequence \08 for writing the "ò" character in GSM alphabet.

Page 23 of 567

1.5 Supported character sets

In the event that an MS receives a code where a symbol is not represented in Figure 1.2, Extension character

table of GSM 03.38 alphabet the MS shall display the character shown in the main default 7 bit alphabet table

(see Figure 1.1, Main character table of GSM 03.38 alphabet).

1.5.2

UCS2 and GSM data coding and conversion for SMS text mode

This section provides basic information on how to handle input and output character conversion for SMS text

mode and Remote-SAT if internal (TA) and external (TE) character representation differ, i.e. if the Data Coding

Scheme and the TE character use different coding.

1.5.2.1

Implementing output of SIM data to Terminal (direction TA to

TE)

Used character set

DCS = 7 bit

DCS = 8 bit

DCS = 16 bit

GSM

Data

UCS2

GSM

Case 1

Case 2

Case 3

GSM (1:1)

8 bit to IRA (1:2)

UCS2 to IRA (2:4)

UCS2

Case 4

Case 5

Case 6

GSM to IRA (1:4)

8 bit to IRA (1:4)

UCS2 to IRA (2:4)

Note: The ratio of SIM bytes to output bytes is given in parentheses.

Case 1

Every GSM character is sent to the TE as it is (8-bit value with highest bit set to zero).

Example: 47'H, 53'H, 4D'H → 47'H, 53'H, 4D'H, displayed as "GSM"

Case 2

Every data byte is sent to the TE as 2 IRA characters each representing a halfbyte.

Example: B8'H (184 decimal) → 42'H, 38'H, displayed as "B8"

Case 3

Every 16-bit UCS2 value is sent to the TE as 4 IRA characters.

Example: C4xA7'H (50343 decimal) → 43'H, 34'H, 41'H, 37'H, displayed as "C4A7"

Problem: An odd number of bytes leads to an error because there are always two bytes needed for each USC2

character

Case 4

Every GSM character is sent to the TE as 4 IRA characters to show UCS2 in text mode.

Example: 41'H ("A") → 30'H, 30'H, 34'H, 31'H, displayed as "0041"

Case 5

Every data byte is sent to the TE as IRA representation of UCS2 (similar to case 4).

Example: B2'H → 30'H, 30'H, 42'H, 32'H, displayed as "00B2"

Case 6

Every 16-bit value is sent to the TE as IRA representation of it. It is assumed that number of bytes is even.

Example: C3x46'H → 43'H, 33'H, 34'H, 36'H, displayed as "C346"

Page 25 of 567

1.5 Supported character sets

1.5.2.2

Implementing input of Terminal data to SIM (direction TE to TA)

Used character set

DCS = 7 bit

DCS = 8 bit

DCS = 16 bit

GSM

Data

UCS2

GSM

Case 1

Case 2

Case 3

GSM (1:1)

IRA to 8 bit (2:1)

IRA to 16 bit (4:2)

UCS2

Case 4

Case 5

Case 6

UCS2 to GSM (4:1)

UCS2 to 8 bit (4:1)

UCS2 to 16 bit (4:2)

Note: The ratio between the number of input characters and bytes stored on the SIM is given in parentheses.

Case 1

Every character is sent from TE to TA as GSM character (or ASCII with standard terminal emulation, e.g. Hyper-

terminal).

Character value must be in range from 0 to 127 because of 7-bit GSM alphabet.

To reach maximum SMS text length of 160 characters in 140 bytes space characters will be compressed on SIM.

This must be set using the parameter <dcs> of AT+CSMP (add 64).

Example: "ABCDEFGH" typed is sent and stored uncompressed as → 4142434445464748'H (stored com-

pressed as 41E19058341E91'H)

Case 2

Every data byte is sent as 2 IRA characters.

Maximum text length is 280 IRA characters which will be converted into 140 bytes SMS binary user data

Example: "C8" typed is sent as 43'H, 38'H → stored as C8'H

Case 3

Every 16-bit value is sent as 4 IRA characters.

Maximum text length is 280 IRA characters which will be converted into 70 UCS2 characters (16-bit each)

Number of IRA characters must be a multiple of four because always 4 half bytes are needed for a 16-bit value

Example: "D2C8" typed is sent as 44'H, 32'H, 43'H, 38'H → stored as D2C8'H

Case 4

Every GSM character is sent as 4 IRA characters representing one UCS2 character.

Example: To store text "ABC" using UCS2 character set you have to type "004100420043".

This is sent as 30'H,30'H,34'H,31'H, 30'H,30'H,34'H,32'H, 30'H,30'H,34'H,33'H → detected as IRA representa-

tion of 3 UCS2 characters, converted to GSM character set and stored as 41'H, 42'H, 43'H.

Maximum input is 640 IRA characters repesenting 160 UCS2 characters when compression is active. These are

converted to 160 GSM 7-bit characters.

Without compression only 140 GSM characters can be stored which are put in as 560 IRA characters.

Values of UCS2 characters must be smaller than 80'H (128 decimal) to be valid GSM characters.

Number of IRA characters must be a multiple of four. Problems:

• "41"

→ Error, there are four IRA characters (two bytes) needed

• "0000" → Error, not an UCS2 character

• "4142" → Error, value of UCS2 character > 7F'H

• "008B" → Error, value of UCS2 character > 7F'H

This affects the maximum input length of a string)

Case 5

Every UCS2 character is sent as 4 IRA characters and is converted into two 8-bit values. This means that the

first two characters have to be '00'.

Example: UCS2 character 009F'H typed as "009F" is sent as 30'H,30'H,39'H,46'H → converted into 8-bit value

9F'H.

Maximum number of UCS2 characters is 140 which are represented by 560 IRA characters. Number of IRA char-

acters must be a multiple of four.

Case 6

Every UCS2 character is sent as 4 IRA characters each and is converted into a 16-bit value again.

Example: UCS2 character 9F3A'H typed as "9F3A" is sent as 39'H,46'H,33'H,41'H → converted into 9F3A'H.

Maximum number of UCS2 characters is 70 which are represented by 280 IRA characters. Number of IRA char-

acters must be a multiple of four.

Invalid UCS2 values must be prevented.

Page 26 of 567

1.6 Serial Interface Flow Control

1.6

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

Software Flow Control (XON/OFF Handshake)

Software flow control sends different characters to stop (XOFF, decimal 19) and resume (XON, decimal 17) data

flow. The only advantage of software flow control is that three wires would be sufficient on the serial interface.

1.6.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 TC65 uses two buffers, one for the uplink and one for the down-

link. 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 a maximum of 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 instantly stops

transferring data to the application. Nevertheless, the application must still be able to receive another 2 bytes.

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. The local data rate between DCE and DTE (AT+IPR) should be set to

a higher value than the 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

Page 27 of 567

1.6 Serial Interface Flow Control

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.

Page 28 of 567

1.7 Communication between Customer Application and TC65

1.7

Communication between Customer Application and TC65

Leaving hardware flow control unconsidered the Customer Application (TE) is coupled with the TC65 (ME) via a

receive and a transmit line.

Since both lines are driven by independent devices collisions may (and will) happen. For example, if the TE

issues an AT command the TC65 starts sending a URC. This will probably cause the TE to misinterpret of the

URC being part of the AT command's response.

To avoid this conflict the following measures must be taken:

• If an AT command is finished (with "OK" or "ERROR") the TE shall always wait at least 100 milliseconds

before sending the next one.

This gives the TC65 the opportunity to transmit pending URCs and get necessary service.

Note that some AT commands may require more delay after "OK" or "ERROR" response, refer to the following

command specifications for details.

• The TE shall communicate with the TC65 using activated echo (ATE1), i.e. the TC65 echoes characters

received from the TE.

Hence, when the TE receives the echo of the first character "A" of the AT command just sent by itself it has

control both over the receive and the transmit paths.

Page 29 of 567

1.8 Unsolicited Result Code Presentation

1.8

Unsolicited Result Code Presentation

URC stands for Unsolicited Result Code and is a report message issued by the ME without being requested by

the TE, i.e. a URC is issued automatically when a certain event occurs. Hence, a URC is not issued as part of

the response related to an executed AT command.

Typical events leading to URCs are incoming calls ("RING"), waiting calls, received short messages, changes in

temperature, network registration etc.

A list of all URCs can be found in Section 23.7, Summary of Unsolicited Result Codes (URC).

To announce a pending URC transmission the ME will do the following:

• The ME activates its RING line (logic "1") for 1 second, i.e. the RING line changes to the physical "Low" level.

This allows the TE to stay in power saving mode until an ME related event requests service.

If several URCs occur coincidently or in quick succession each URC triggers the RING line independently,

although the line will not be deactivated between each URC. As a result, the RING line may stay low for more

than 1 second.

If an incoming call is answered within less than 1 second (with ATA or if autoanswering is set to ATS0=1) than

the RING line will be deactivated earlier.

The "^SHUTDOWN" URC will not activate the RING line.

• If the AT command interface is busy a "BREAK" will be sent immediately but the URC will not be issued until

the line is free. This may happen if the URC is pending in the following cases:

- During the processing of an AT command (i.e. the time after the TE echoes back the first character "A" of

an AT command just sent by itself until the ME responds with "OK" or "ERROR").

- During a data call.

Please note that AT command settings may be necessary to enable in-band signaling, e.g. refer to AT+CMER

or AT+CNMI.

It is strongly recommended to use the multiplex mode to map logical communication channels onto the serial line

of the TC65, for details refer to [7] and AT command AT+CMUX. Doing so it is possible to use one channel to still

process URCs while having a data call active on another.

For most of these messages, the ME needs to be configured whether or not to send a URC. Depending on the

AT command, the URC presentation mode can be saved to the user defined profile (see AT&W), or needs to be

activated every time you reboot the ME. Several URCs are not user definable, such as "^SYSSTART",

"^SYSSTART <text>", "^SHUTDOWN"

If autobauding is enabled (as factory default mode or set with AT+IPR=0), URCs generated after restart will be

output with 57600 bps until the ME has detected the current bit rate. The URCs "^SYSSTART", "^SYSSTART

<text>", however, are not presented at all. For details please refer to Section 4.9.1, Autobauding. To avoid prob-

lems we recommend to configure a fixed bit rate rather than using autobauding.

Page 30 of 567

1.9 Common PCN Handset Specification (CPHS)

1.9

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

Page 31 of 567

1.10 Errors and Messages

1.10

Errors and Messages

The command result codes "+CME ERROR: <err>" and "+CMS ERROR: <err>" indicate errors related to mobile

equipment or network functionality.

The format of <err> can be either numeric or verbose and is selectable via AT+CMEE.

A result error code terminates the execution of the command and prevents the execution of all remaining com-

mands that may follow on the same command line. If so, neither "ERROR" nor "OK" result codes are returned

for these commands. A 30 seconds timeout will deliver "ERROR" when the input of a command is not complete.

Using the wrong command syntax may result in errors: For example, using the execute command syntax

although the command has no execute format, causes "ERROR" to be returned. Likewise, using the write com-

mand syntax although the command has no write format causes "+CME ERROR: <err>" to be returned.

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

Page 32 of 567

2. Configuration Commands

Configuration Commands

The AT Commands described in this chapter allow the external application to determine the TC65'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)

Reference(s)

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

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.

Page 33 of 567

2.2 AT&V

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)

Reference(s)

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

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.

Page 34 of 567

2.2 AT&V

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

Page 35 of 567

2.3 AT&W

2.3

AT&W Stores current configuration to user defined profile

AT&W stores the currently set parameters to a user defined profile in the non-volatile memory.

Syntax

Exec Command

AT&W[<value>]

Response(s)

ERROR/+CME ERROR <err>

Reference(s)

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

V.250

Parameter Description

<value>^(num)

[0]

Number of profile

Notes

• The user defined profile will be restored automatically after power-up. Use ATZ to restore user profile and

AT&F to restore factory settings. Until the first use of AT&W, ATZ works as AT&F.

• AT&W stores all global settings and the current local settings of the interface, on which the command is exe-

cuted.

• A list of parameters stored to the user profile can be found in Section 23.5, AT Command Settings stor-

able with AT&W.

Page 37 of 567

2.5 ATV

2.5

ATV Set 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

Reference(s)

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

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

Page 39 of 567

2.6 ATX

2.6

ATX Set CONNECT result code format and call monitoring

ATX determines whether or not the TA detects the presence of dial tone and busy signal and whether or not TA

transmits particular result codes.

Syntax

Exec Command

ATX[<value>]

Response(s)

ERROR

Reference(s)

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

V.250

Parameter Description

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

[0]

CONNECT result code only returned, dial tone and busy detection are both dis-

abled.

CONNECT <text> result code only returned, dial tone and busy detection are

both disabled.

CONNECT <text> result code returned, dial tone detection is enabled, busy

detection is disabled.

CONNECT <text> result code returned, dial tone detection is disabled, busy

detection is enabled.

4^(&F)

CONNECT <text> result code returned, dial tone and busy detection are both

enabled.

Page 40 of 567

2.8 ATZ

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)

Reference(s)

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

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.

Page 42 of 567

2.9 AT+CFUN

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

Reference(s)

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

GSM 07.07

Page 43 of 567

2.9 AT+CFUN

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.

Due to the fact that the serial interface is disabled, this mode cannot be used

if a Remote SIM Access (RSA) connection is ongoing (reason: during RSA

connections the SIM communication is routed via a serial channel).

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.

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

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

Page 44 of 567

2.9 AT+CFUN

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

•

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 [7],

Section "Power saving control".

•

If the host application uses the USB interface, power saving must be configured both on the TC65 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:

Page 45 of 567

2.9 AT+CFUN

• 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

From Java: Yes

Temporary

SMS, voice or data call)

Without Java: Not possible (UART

disabled)

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

From Java: Yes

Temporary

Without Java: Not possible (UART

disabled)

RTC alarm line

Quit

Temporary

AT+CFUN=1

From Java: Yes

Quit

Without Java: Not possible (UART

disabled)

Java terminates

Quit

Temporary

Page 46 of 567

2.10 AT^SMSO

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 "^SHUTDOWN"

notify that the procedure has completed and the module has entered the POWER DOWN mode. Therefore, 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

Reference(s)

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

SIEMENS

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

Page 47 of 567

2.12 AT+CMEE

2.12

AT+CMEE Mobile Equipment Error Message Format

AT+CMEE controls the format of the error result codes that indicates errors related to TC65 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 (SIEMENS)Table 2.6, GPRS related "CME ERROR" Codes (GSM 07.07) 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>

Reference(s)

ASC0

ASC1

USB

MUX1

MUX2

MUX3

Charge

Last

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

Page 49 of 567

2.12 AT+CMEE

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 pe sonalization PIN required

Corporate personalization PUK required

Master Phone Code required

100

unknown

132

service option not supported

Page 50 of 567

2.12 AT+CMEE

<err> Code

Text (if AT+CMEE=2)

133

requested service option not subscribed

134

service option temporarily 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 (SIEMENS)

<err> Code

Text (if AT+CMEE=2)

615

network failure

616

network is down

639

service type not yet available

640

operation of service temporary not allowed

764

missing input value

765

invalid input value

767

operation failed

769

unable to get control of required module

770

SIM invalid - network reject

771

call setup in progress

772

SIM powered down

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 (SIEMENS)

<err> Code

Text (if AT+CMEE=2)

578

GPRS - unspecified activation rejection

588

GPRS - feature not supported

594

GPRS - invalid address length

595

GPRS - invalid character in address string

Page 51 of 567

2.12 AT+CMEE

<err> Code

Text (if AT+CMEE=2)

596

GPRS - invalid cid value

607

GPRS - missing or unknown APN

625

GPRS - pdp type not supported

630

GPRS - profile (cid) not defined

632

GPRS - QOS not accepted

633

GPRS - QOS validation fail

643

GPRS - unknown PDP address or type

644

GPRS - unknown PDP context

646

GPRS - QOS invalid parameter

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

159

Unspecified TP-DCS error

160

Command cannot be actioned

Page 52 of 567

2.12 AT+CMEE

<err> Code

Text (if AT+CMEE=2)

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

D0 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 ACK EXPECTED

500

Unknown error

512

User abort

Page 53 of 567

2.13 AT+CSCS

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.5, 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)

Reference(s)

ASC0

ASC1

USB

MUX1

MUX2

MUX3

Charge

Last

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.

Page 55 of 567

2.14 AT^SCFG

2.14

AT^SCFG Extended Configuration Settings

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

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

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

The following error messages may be returned by the AT^SCFG write commands:

• "+CME ERROR: operation temporary not allowed"

Change of parameter value(s) temporarily not allowed.

• "+CME ERROR: invalid index"

Invalid parameter name or value(s).

• "+CME ERROR: invalid characters in text string"

Character set conversion of parameter value(s) failed.

• "+CME ERROR: incorrect password"

A given password was not correct.

• "+CME ERROR: memory failure"

Could not allocate necessary memory or storing a parameter failed.

• "+CME ERROR: operation not allowed"

Change of parameter value(s) not allowed

• "+CME ERROR: unknown"

Other error

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: "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/OutputPowerReduction", (list of supported <ropr>s)

^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", (list of supported <ua>s)

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

Page 56 of 567

2.14 AT^SCFG

Test Command

(Continued)

AT^SCFG=?

Response(s)

^SCFG: "Userware/Autostart/Delay", (list of supported <uad>s)

^SCFG: "Userware/Passwd", (max. string length of <upwd>)

^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: "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/OutputPowerReduction", <ropr>

^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", <ua>

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

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

^SCFG: "Userware/Passwd"

^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>]

Page 57 of 567

2.14 AT^SCFG

Write Command

(Continued)

Automatic AT command execution

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

<AutoExecATC>[, <AutoExecPeriod>]]

Response(s)

ERROR

+CME ERROR

Write Command

GPRS ATS0 with automatic attach

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

Response(s)

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

ERROR

+CME ERROR

Write Command

Automatic GPRS attach

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

Response(s)

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

ERROR

+CME ERROR

Write Command

Persistent GPRS contexts

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

Response(s)

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

ERROR

+CME ERROR

Write Command

Ring on incoming GPRS IP data packets

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

Response(s)

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

ERROR

+CME ERROR

Write Command

Enable/disable Airplane mode during operation

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

Response(s)

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

ERROR

+CME ERROR

Page 58 of 567

2.14 AT^SCFG

Write Command

Airplane mode upon ME restart

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

Response(s)

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

ERROR

+CME ERROR

Write Command

Enable/disable shutdown by ignition line

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

Response(s)

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

ERROR

+CME ERROR

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

Write Command

Radio output power reduction

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

Response(s)

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

ERROR

+CME ERROR

Write Command

Radio band selection

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

Response(s)

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

ERROR

+CME ERROR

Write Command

Configuration of TCP parameter 'InitialRetransmissionTimeout':

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

Response(s)

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

ERROR

+CME ERROR

Page 59 of 567

2.14 AT^SCFG

Write Command

Configuration of TCP parameter 'MaxRetransmissions':

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

Response(s)

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

ERROR

+CME ERROR

Write Command

Configuration of TCP parameter 'OverallTimeout':

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

Response(s)

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

ERROR

+CME ERROR

Write Command

Configuration of TCP parameter 'Selective Acknowledge':

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

Response(s)

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

ERROR

+CME ERROR

Write Command

Configuration of Internet Service URCs:

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

Response(s)

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

ERROR

+CME ERROR

Write Command

Tracing:

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

Response(s)

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

SYSLOG ENABLED

ERROR

+CME ERROR

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

Page 60 of 567

2.14 AT^SCFG

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

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

Write Command

URC indication via Ring line:

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

Response(s)

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

ERROR

+CME ERROR

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

Write Command

Userware autostart status:

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

Response(s)

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

ERROR

+CME ERROR

Write Command

Userware autostart application:

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

Response(s)

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

ERROR

+CME ERROR

Page 61 of 567

2.14 AT^SCFG

Write Command

Userware autostart delay:

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

Response(s)

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

ERROR

+CME ERROR

Write Command

Userware configuration password:

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

Response(s)

^SCFG: "Userware/Passwd"

ERROR

+CME ERROR

Write Command

Userware debug interface:

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

Response(s)

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

ERROR

+CME ERROR

Write Command

Userware mode:

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

Response(s)

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

ERROR

+CME ERROR

Write Command

Standard output of userware

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

Response(s)

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

ERROR

+CME ERROR

PIN ASC0 ASC1

USB MUX1

MUX2

MUX3

Charge

Last

Page 62 of 567

2.14 AT^SCFG

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 TC65 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 TC65 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 TC65 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

Page 63 of 567

2.14 AT^SCFG

<AutoExecMode>^(str)(+CSCS)

AutoExec Command Mode

0...255

This parameter specifies details regarding the behavior of the TC65 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 TC65 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 TC65 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 TC65 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 TC65 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

Page 64 of 567

2.14 AT^SCFG

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

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

Page 65 of 567

2.14 AT^SCFG

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

Page 66 of 567

2.14 AT^SCFG

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

Please note that the factory default is different depending on the product type.

Designed as a ready-to-use solution the TC65 Terminal is delivered with <msi>="on". Changing the delivery

default of the TC65 Terminal disables the switch-off function of its ON/OFF push button and its ONOFF line on

the GPIO connector, and therefore, is not allowed.

TC65 Modules are factory set to <msi>="off". It is only in the case of modules that the application manufacturer

may decide to change the default setting. 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] and [3].

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 parameters <rba>, <rbp> and <rbc> allow the subscriber to set and query preferences for selecting fre-

quency bands.

Before changing <rba> or <rbp> ensure that no network activity occurs. The write command cannot be exe-

cuted 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> determines the maximum range of the bands allowed. The value may be one of the single

bands listed below or all valid combinations from the values 1, 2, 4 and 8. Thus, the value range of <rba> is

"1".."15". To select or deselect a band calculate the sum of the values of all desired bands and enter the resulting

value. For example, for 1800 MHz (2) and 850 MHz (8) please enter the value (10).

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

Page 67 of 567

2.14 AT^SCFG

"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"

all bands

<rbp>^(str)(+CSCS)

Preferred radio band(s)

The parameter <rbp> may be one of the single bands or one of the four dualband combinations listed below.

All preferred bands must be contained in the range of allowed bands (see <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>.

<rbp> primarily serves to trigger the network search, i.e. it is only used one time for searching and selecting a

network. As the currently used band depends on the availability of the allowed networks the value indicated by

<rbc> may be different from <rbp>. Also, next time a network search is necessary, for example after restart,

the ME will first try to reselect the network last used, which may be different from the value of <rbp> last given.

Therefore, the setting of <rbp> will not be saved.

The value range of <rbp> is "1...12", but only the bands or band selections listed below are allowed. Trying to

set an unsupported value will be denied with "ERROR". To select or deselect a band calculate the sum of the

values of all desired bands and enter the resulting value. For example, for GSM 1800 MHz (2) and GSM 850

MHz (8) please enter the value (10).

"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

<rbc>^(str)(+CSCS)

Currently selected radio band(s)

The band(s) indicated with <rbc> are all allowed bands found at a location area. This means, if prompted to

select a network the ME will search for these networks only. The value can be either a single band or a dualband

combination.

<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" (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

Page 68 of 567

2.14 AT^SCFG

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

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

Page 69 of 567

2.14 AT^SCFG

<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 Java 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 commands can be entered. The tracer will be switched off only by a reset of the module, e.g. after a com-

pleted OTAP procedure.

"1"

Enable OTAP tracer.

Page 70 of 567

2.14 AT^SCFG

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

Page 71 of 567

2.14 AT^SCFG

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

Page 72 of 567

2.14 AT^SCFG

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

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

"ASC0"

System.out shall be 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.

"ASC1"^(D)

System.out shall be 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.

"USB"

System.out shall be routed to the Universal Serial Bus.

"NULL"

Discard data.

Page 73 of 567

2.14 AT^SCFG

"UDP"

Intended for IDE usage. Requires additional parameter <intvalue>.

"FILE"

System.out shall be written to file. Requires additional parameters

<intvalue>, <filename> and <logmode>.

<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, usually 1024 to 65535.

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

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 TC65 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).

Page 74 of 567

2.14 AT^SCFG

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 TC65 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

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

AT^SCFG="AutoExec",1,1,2,0,"AT^SMSO","000:03:00"

After three minutes:

^SCFG:"AutoExec",0,1,2,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):

Page 75 of 567

2.14 AT^SCFG

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"

^SCFG:"URC/Ringline","asc0"

URCs on this interface will be indicated by an acti-

vated RING0 no matter whether or not the TA-TE link

is reserved.

AT^SCFG="URC/Datamode/Ringline","off"

^SCFG:"URC/Datamode/Ringline","off"

URCs on this interface will be indicated by an acti-

vated RING0 if the TA-TE link is not reserved and by

BREAK if the TA-TE link is reserved.

AT^SCFG="URC/Ringline"

Disable any Ring line indication for URCs on this

interface.

^SCFG:"URC/Ringline","off"

Page 76 of 567

2.15 AT^SM20

2.15

AT^SM20

Set M20 compatibility mode

M20 is an earlier, widely used SIEMENS 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 TC65.

Syntax

Test Command

AT^SM20=?

Response(s)

Read Command

AT^SM20?

Response(s)

^SM20:<CallMode>, <CmgwMode>

Write Command

AT^SM20=<CallMode>[, <CmgwMode>]

Response(s)

Reference(s)

ASC0

ASC1

USB

MUX1

MUX2

MUX3

Charge

Last

SIEMENS

Parameter Description

<CallMode>^(num)

Call setup response mode

Applies only to voice calls.

Set compatibility to Siemens mobile phones.

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 Siemens mobile phones.

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.

Page 77 of 567

3. Status Control Commands

Status Control Commands

The AT Commands described in this chapter allow the external application to obtain various status information

from the TC65.

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>₂][, <indValue>[,...]]" 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 examples 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

Reference(s)

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

GSM 07.07

Unsolicited Result Code

+CIEV: <indDescr>, <indValue>₁[, <indValue>₂][, <indValue>[,...]]

A value of an indicator has changed. For more details see AT^SIND.

Page 78 of 567

3.1 AT+CMER

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 TC65 is in online

data mode, URCs are signaled via sending BREAK (100ms) 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 TC65.

<disp>^(num)

0^(&F)

Display event reporting is not supported by TC65.

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

Page 79 of 567

Siemens TC65 Terminal. Manual (Version: 02.000) - part 1