Siemens TC65 Terminal. Manual (Version: 02.000)

19.3 AT^SBC

Notes

• If multiplex mode (AT+CMUX) is active, any virtual channel can be used for entering the read or write com-

mand. The undervoltage URC will be issued simultaneously on all three channels.

• Another URC type required for battery powered applications is the URC "^SYSSTART CHARGE ONLY MODE".

It is indicated automatically when the module enters this mode (except when autobauding is active). See

AT+CFUN for details.

19.3.1

Responses returned by read command

Responses returned by the AT^SBC read command vary with the operating mode of the TC65:

• Normal mode: TC65 is switched on by Ignition pin and running in SLEEP, IDLE, TALK or DATA mode.

Charger is not connected. The AT^SBC read command indicates the battery capacity and the current con-

sumption of the application (if value of application was specified before as <current>).

• Normal mode + charging: Allows charging while TC65 is switched on by Ignition pin and running in SLEEP,

IDLE, TALK or DATA mode. The AT^SBC read command returns only charger status and current consump-

tion of the application. Percentage of battery capacity is not available.

• CHARGE ONLY mode: Allows charging while TC65 is detached from GSM network. When started, the mode

is indicated by the URC "^SYSSTART CHARGE ONLY MODE". The AT^SBC read command returns only the

charger status and current consumption of the application. Percentage of battery capacity is not available. In

CHARGE ONLY mode a limited number of AT commands is accessible (see Appendix). There are several

ways to activate the CHARGE ONLY mode:

- from POWER DOWN mode: Connect charger while the TC65 was powered down with AT^SMSO

- from Normal mode: Connect charger, then enter AT^SMSO.

Page 480 of 567

19.4 AT^SBV

19.4

AT^SBV Battery/Supply Voltage

The AT^SBV execute command allows to monitor the supply (or battery) voltage of the module. The voltage is

continuously measured at intervals depending on the operating mode of the RF interface. The duration of a mea-

surement period ranges from 0.5s in TALK / DATA mode up to 50s when TC65 is in IDLE mode or Limited Ser-

vice (deregistered). The displayed value is averaged over the last measuring period before the AT^SBV

command was executed.

The measurement is related to the reference points of BATT+ and GND, both accessible on a capacitor located

close to the module's board-to-board connector. For details please refer to the Hardware Interface Description

[2].

Syntax

Test Command

AT^SBV=?

Response(s)

ERROR

+CME ERROR:

Exec Command

AT^SBV

Response(s)

^SBV: <value>

ERROR

+CME ERROR:

Reference(s)

ASC0

ASC1

USB

MUX1

MUX2

MUX3

Charge

Last

SIEMENS

Parameter Description

<value>^(num)

Supply (or battery) voltage in mV

Page 481 of 567

19.5 AT^SCTM

19.5

AT^SCTM Set critical operating temperature presentation mode

or query temperature

Use this command to monitor the temperature range of the module and the battery. The write command enables

or disables the presentation of URCs to report critical temperature limits.

CAUTION: During the first 15 seconds after start-up, the module operates in an automatic report mode: URCs

can be always displayed regardless of the selected mode <n>.

Syntax

Test Command

AT^SCTM=?

Response(s)

^SCTM:(list of supported <n>s)

Read Command

AT^SCTM?

Response(s)

^SCTM: <n>, <m>

ERROR

+CME ERROR

Write Command

AT^SCTM=<n>

Response(s)

ERROR

+CME ERROR

Reference(s)

ASC0

ASC1

USB

MUX1

MUX2

MUX3

Charge

Last

SIEMENS

Unsolicited Result Codes

URC 1

URCs will be automatically sent to the TA when the temperature reaches or exceeds the critical level, or when

it is back to normal.

^SCTM_A: <m>

for battery temperature

URC 2

^SCTM_B: <m>

for module (board) temperature

Page 482 of 567

19.5 AT^SCTM

Command Description

The read command returns:

• the URC presentation mode

• information about the current temperature range of the module

Please note that the Read command does not indicate the temperature range of the battery. The battery temper-

ature can only be reported by an Unsolicited Result Code.

Select <n> to enable or disable the presentation of the URCs. Please note that the setting will not be stored upon

Power Down, i.e. after restart or reset, the default <n>=0 will be restored. To benefit from the URCs <n>=1 needs

to be selected every time you reboot the GSM engine.

Parameter Description

<n>^(num)

0^(&F)(P)

Presentation of URCs is disabled (except for <m> equal to -2 or +2).

Presentation of URCs is enabled.

<m>^(num)

-2

Below lowest temperature limit (causes immediate switch-off)

-1

Below low temperature alert limit

Normal operating temperature

Above upper temperature alert limit

Above uppermost temperature limit (causes immediate switch-off)

Notes

• Please refer to the "Hardware Interface Description" for specifications on critical temperature ranges.

• To avoid damage the module will shut down once the critical temperature is exceeded.

The procedure is equivalent to the power-down initiated with AT^SMSO.

• URCs indicating the alert level "1" or "-1" are intended to enable the user to take appropriate precautions,

such as protect the module and the battery from exposure to extreme conditions, or save or back up data etc.

The presentation of "1" or "-1" URCs depends on the settings selected with the write command:

If <n>=0: Presentation is enabled for 15 s time after the module was switched on. After 15 s operation, the

presentation will be disabled, i.e. no URCs will be generated.

If <n>= 1: Presentation of "1" or "-1" URCs is always enabled.

• Level "2" or "-2" URCs are followed by immediate shutdown. The presentation of these URCs is always

enabled, i.e. they will be output even though the factory setting AT^SCTM=0 was never changed.

• If the temperature limit is exceeded while an emergency call is in progress the engine continues to measure

the temperature and to deliver alert messages, but deactivates the shutdown functionality. Once the call is

terminated full temperature control will be resumed. If the temperature is still out of range ME switches off

immediately.

Examples

EXAMPLE 1

URCs issued when the operating temperature is out of range:

^SCTM_A: 1

Caution: Battery close to overtemperature limit.

^SCTM_A: 2

Alert: Battery above overtemperature limit. Engine switches off.

^SCTM_B: 1

Caution: Module close to overtemperature limit.

^SCTM_B: 2

Alert: Module is above overtemperature limit and switches off.

^SCTM_A: -1

Caution: Battery close to undertemperature limit.

^SCTM_A: -2

Alert: Battery below undertemperature limit. Engine switches off.

^SCTM_B: -1

Caution: Module close to undertemperature limit.

^SCTM_B: -2

Alert: Module is below undertemperature limit and switches off.

Page 483 of 567

19.6 AT^SSYNC

19.6

AT^SSYNC Configure SYNC Pin

The AT^SSYNC command serves to configure the SYNC pin of the application interface. The applicability of the

different types of <mode> is product dependent:

• If you have a TC65 module you may select either mode, depending on whether your application is designed

to use the SYNC mode (indicates the current consumption in a transmit burst) or the LED mode (drives a

status LED connected to the pin). See [2] for further details on both modes.

• In the case of the TC65 Terminal the AT^SSYNC command is intended only to control the status LED placed

on the front panel. Therefore, the SYNC mode (<mode>=0) is not applicable. Further details on the LED can

be found in [3].

Syntax

Test Command

AT^SSYNC=?

Response(s)

^SSYNC:list of supported <mode>s

Read Command

AT^SSYNC?

Response(s)

^SSYNC:<mode>

Write Command

AT^SSYNC=<mode>

Response(s)

Reference(s)

ASC0

ASC1

USB

MUX1

MUX2

MUX3

Charge

Last

SIEMENS

Parameter Description

<mode>^(num)

Operation mode of the SYNC pin. Setting is stored non-volatile.

0^(D)

SYNC mode:

Enables the SYNC pin to indicate growing power consumption during a trans-

mit burst. You can make use of the signal generated by the SYNC pin, if power

consumption is your concern. To do so, ensure that your application is capable

of processing the signal. Your platform design must be such that the incoming

signal causes other components to draw less current. In short, this allows your

application to accommodate current drain and thus, supply sufficient current to

the GSM engine if required.

Note: <mode>=0 is the factory default of the TC65 module. In the case of the

TC65 Terminal this mode is not applicable and should not be selected.

LED mode:

Enables the SYNC pin to drive a status LED installed in your application

according to the specifications provided in [2].

The coding of the LED is described in Section 19.6.1, ME status indicated by

status LED patterns.

Page 485 of 567

19.6 AT^SSYNC

LED mode:

Like <mode>=1, but, additionally, enables different LED signalization in SLEEP

mode depending on the status of PIN authentication and network registration.

Please see AT+CFUN for details on SLEEP mode.

Note: <mode>=2 is the factory default of the TC65 Terminal.

19.6.1

ME status indicated by status LED patterns

The following table lists the possible patterns of status LED behavior, and describes the ME operating status indi-

cated by each pattern if AT^SSYNC parameter <mode>=1 and <mode>=2. To better monitor the operating states

while power saving is enabled, we recommend that priority be given to <mode>=2.

During the transition from one LED pattern to another the "on" and/or "off" periods of the LED may vary in length.

This is because an event that triggers the change may occur any time and, thus, truncate the current LED pattern

at any point.

The statements on LED behavior during SLEEP mode are not applicable if the USB cable is plugged. This is

because power saving with connected USB host does not take effect if set with AT+CFUN only. For details see

notes provided with AT+CFUN. Therefore, while the USB cable is plugged, the LED is always on and flashes as

if the module works at AT+CFUN=1, no matter whether AT^SSYNC=1 or AT^SSYNC=2 is enabled.

Table 19.1: Modes of the LED and indicated ME functions

LED behavior

ME operating status if AT^SSYNC=1

ME operating status if AT^SSYNC=2

Permanently off

ME is in one of the following modes:

- POWER DOWN mode

- AIRPLANE mode

- CHARGE ONLY mode

- NON-CYCLIC SLEEP mode

- CYCLIC SLEEP mode with no tempo-

rary wake-up event in progress ¹⁾

600 ms on / 600ms off

Limited Network Service: No SIM card

Same as for AT^SSYNC=1

inserted or no PIN entered, or network

search in progress, or ongoing user

authentication, or network login in

progress.

75 ms on / 3 s off

IDLE mode: The mobile is registered to

Same as for AT^SSYNC=1

the GSM network (monitoring control

channels and user interactions). No call

is in progress.

75 ms on / 75 ms off /

One or more GPRS PDP contexts acti-

Same as for AT^SSYNC=1

75 ms on / 3 s off

vated.

500 ms on / 50 ms off

Packet switched data transfer is in

Same as for AT^SSYNC=1

progress.

Permanently on

Depending on type of call:

Same as for AT^SSYNC=1

Voice call: Connected to remote party.

Data call: Connected to remote party or

exchange of parameters while setting

up or disconnecting a call.

<n> ms on / <n> ms off ²⁾

Not possible: With AT^SSYNC=1, LED

SLEEP mode is activated (AT+CFUN

signalization is disabled in SLEEP

parameter <fun> ≠ 1), but the ME is not

mode.

registered to the GSM network (e.g. SIM

not inserted or PIN not entered, and

therefore, either no network service or

only Limited Network Service is avail-

able.

Page 486 of 567

19.6 AT^SSYNC

LED behavior

ME operating status if AT^SSYNC=1

ME operating status if AT^SSYNC=2

25 ms on / 4 * <n> ms off ²⁾

Not possible: With AT^SSYNC=1, LED

SLEEP mode is activated (AT+CFUN

signalization is disabled in SLEEP

parameter <fun> ≠ 1) while the ME is

mode.

registered to the GSM network and in

IDLE mode.

25 ms on / <m> ms off /

Not possible: With AT^SSYNC=1, LED

SLEEP mode is activated (AT+CFUN

25 ms on / 3 * <m> ms off

signalization is disabled in SLEEP

parameter <fun> ≠ 1) while the ME is

mode.

registered to the GSM network. Addi-

tionally, PDP context is activated.

1) When a temporary wake-up event (for example a call, a URC, a packet switched transfer) occurs in CYCLIC SLEEP mode

the LED flashes according to the patterns listed above. See Section 2.9.1, Wake up the ME from SLEEP mode for details

on the various SLEEP modes and wake-up events.

2) The duration of <n> and <m> depends on the network: In SLEEP mode, the module can only change its LED status during

intermittent wake-up periods when listening to paging information from the base station. Therefore the values of <n> and

<m> vary as follows:

<n> = value from 471 ms to 2118 ms

<m> = 3000 ms

Page 487 of 567

19.7 AT^SSPI

19.7

AT^SSPI Serial Protocol Interface

The AT^SSPI command enables the module to be connected to external I²C or SPI devices.

The I²C/SPI datastream is mapped through an internal I²C/SPI driver to and from an ASCII hex protocol which

can be exchanged with an internal application (JAVA) or an external application via V24.

The AT^SSPI write command configures and activates the I²C/SPI interface and changes from command mode

into data mode. All values must be given in hexadecimal format (0 - 9, A - F) without "0x". For details on data

mode please refer to Section 19.7.3, Transmitting Data over AT Interface.

Caution:

If I²C or SPI data mode is active the DCD line of the connected serial port goes high.

If I²C or SPI are opened from a Java application be sure to close the I²C or SPI channels before Java terminates.

Syntax

Test Command

AT^SSPI=?

Response(s)

^SSPI:(list of supported <basicConfiguration>s), (list of supported <delayOne>s), (list of supported

<delayTwo>s), (list of supported <wordLength>s), (list of supported <extendedSpiConfiguration>s)

Read Command

AT^SSPI?

Response(s)

^SSPI: <connectionState>, <basicConfiguration>, <delayOne>, <delayTwo>, <wordLength>,

ERROR

+CME ERROR: <err>

Write Command

AT^SSPI=[<basicConfiguration>[, <delayOne>[, <delayTwo>[, <wordLength>[,

<extendedSpiConfiguration>]]]]]

Response(s)

CONNECT

(indicates that ME has entered data mode)

ERROR

+CME ERROR: <err>

Reference(s)

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

SIEMENS

Page 488 of 567

19.7 AT^SSPI

Parameter Description

<connectionState>^(num)

Parameter returned by the AT^SSPI? read command.

Indicates whether or not the I²C or SPI channel is used. When the channel is open and the ME is in data mode,

the read command can only be used if one of the remaining interfaces is available. For example, when the chan-

nel was opened on ASC0, you can use ASC1 or the MUX channels to check the status.

[0]^(&F)

Not connected (channel closed). All following parameters are the factory set-

tings AT^SSPI=0,0010,0000,0000,0000,0000.

Connected (channel open, ME in data mode). All following parameters are the

values currently used, for example AT^SSPI=1,0010,FFFF,FFFF,0000,0000.

<basicConfiguration>^(num)

Parameter <basicConfiguration> is a 16 bit word which contains four subparameters to control the follow-

ing functions:

Subparameter

Bit

Hexadecimal

Selected function

Interface type

D15 - D12

I²C bus (default)

SPI device

Port

D11 - D8

Internal port

Data transfer rate

D7 - D4

I²C at 100 kbps

I²C at 400 kbps (default)

SPI at 100 kbps

SPI at 250 kbps

SPI at 500 kbps

SPI at 1.083 Mbps

SPI at 3.25 Mbps

SPI at 6.5 Mbps

Protocol

D3 - D0

ASCII (hex coding)

<delayOne>^(num)

I²C: This parameter specifies a delay after each written byte. See Section 19.7.1, Specifying Delay Time for I²C

for further details.

SPI: 0000 only.

[0]^(&F)...FFFF

Unsigned 16 bit value

<delayTwo>^(num)

I²C: This parameter specifies the delay after a each read byte. See Section 19.7.1, Specifying Delay Time for

I²C for further details.

SPI: 0000 only.

[0]^(&F)...FFFF

Unsigned 16 bit value

<wordLength>^(num)

For SPI only:

Length of SPI word = 8 bits

<extendedSpiConfiguration>^(num)

For SPI only: Parameter <extendedSpiConfiguration> is a 16 bit word which contains four subparameters

to control the following functions:

Page 489 of 567

19.7 AT^SSPI

Subparameter

Bit

Hexadecimal

Selected function

SPI mode

D15 - D12

Four different SPI modes. Phase and

polarity of all SPI modes are illustrated in

Section 19.7.2, Selecting SPI Mode.

Chip Select (CS) mode

D11 - D8

One Chip Select per Transfer Frame.

Arrangement of bytes

D7 - D4

Big endian

Bit sequence

D3 - D0

MSB first

(arrangement of bits on the SPI)

19.7.1

Specifying Delay Time for I²C

The following figures are provided to assist you in specifying appropriate values for the parameters <delayOne>

and <delayTwo>. All delays are relative to the data transfer rate. To calculate the delay use the formula and the

values given below.

Figure 19.1: Formula for calculating the delay

Table 19.2: Values for calculating the delay

Parameter

Values

Delay value

Value set with parameter <delayOne> or <delayTwo>

Master clock

13 MHz

Default data transfer rate

400 bps

User data transfer rate

Value selected with subparameter data transfer rate within <basicConfigura-

tion>, for example 100 kbps or 400 kbps

Delay_min for Write

7.4 µs at 100 kbps

2.0 µs at 400 kbps

Delay_min for Read

9.9 µs at 100 kbps

2.6 µs at 400 kbps

Figure 19.2: Delay time on I²C after Write

Page 490 of 567

19.7 AT^SSPI

19.7.3

Transmitting Data over AT Interface

This section provides information on the protocol used for data transmission to or from I²C/SPI devices and

explains the data mode. It is assumed that you are familiar with the I²C specification.

Throughout this section the following document conventions are used to mark the direction of send and receive:

Transfer Message: AT → I²C or SPI device driver

Response Message: AT ← I²C or SPI device driver

Channel Open / Close:

To change from command mode to data mode use the AT^SSPI write command. To close down the channel

and return to command mode send the ASCII code # (0x23).

ASCII Protocol for I²C or SPI communication over AT interface:

The protocol allows using a Terminal program for the communication between the module and the I²C slave

device/SPI device. To visualize transferred characters and response data it is recommended to run the Terminal

program in chat mode or to switch on local echo.

For transfer and response, special characters are defined, such as Start and Stop to mark a single message and

Close to disconnect the data channel. All valid special characters are listed below:

Table 19.3: Special characters for ASCII coding

Direction

Function in protocol

Special

Hex value

Description

AT - Driver

character

→

Start Transfer Message

0x3C

Special character sent to the I²C/SPI

driver to start sending.

→

Stop Transfer Message

0x3E

Special character sent to the I²C/SPI

driver to stop sending.

→

Channel Close

0x23

For signalling.

Channel Close can be sent any time inside

or outside a transmit or receive message.

Causes the transfer to be aborted and

takes the ME back to AT command mode.

←

Start Response Message

{

0x7B

Special character sent to the I²C/SPI

driver to mark the beginning of a Response

Message.

←

Stop Response Message

}

0x7D

Special character sent to the I²C/SPI

driver to mark the end of a Response Mes-

sage.

←

Protocol error

0x21

For signalling.

Reports to the AT interface that the Trans-

fer Frame does not comply with the proto-

col definition (syntax error).

←

Transmission OK

0x2B

Notifies the AT interface that data were

(in I²C protocol referred to

successfully transmitted or, on the I²C bus,

as ACK)

the I²C Slave Address was recognized.

On I²C bus only:

←

Transmission error

0x2D

Notifies the AT interface that data transmis-

(in I²C protocol referred to

sion failed or the I²C Slave Address was

as NAK)

not recognized. On the I²C bus, the faulty

data byte (16 bit byte counter) is identified

as well.

Page 492 of 567

19.7 AT^SSPI

Message syntax:

Each Message consists of a Start and Stop character, a Message-ID, further protocol data and user data. The

notation of all elements is explained below:

Notation of Message-ID:

• All ASCII characters between 0x00...0x7F. It is recommended to use only the characters 0...9, A...Z, a...z.

• Length of the Message-ID: only one character

Notation of protocol data (except Message-ID) and user data:

• Hex (0...9, a...f, A...F)

• Without "0x" (0x01 →01)

• Each hex value consists of 2 characters (1 →01)

• Without delimiters such as comma, semicolon, space etc. (0xAE 0x01 0xA5 →AE01A5)

• In a Transfer Message, the number of all characters after the Message ID shall be even. If it is odd, a protocol

error will be reported. On the I²C bus, this applies to the I²C Slave Address and all subsequent written user

data. On the SPI this applies to the Read Offset Byte and the Read Length and, if available, all written user

data. (Keep in mind that the number of all characters transmitted between Start "<" and Stop ">" of the Trans-

fer Frame shall always be odd because the ID is one character only.)

• Length of I²C Slave Address and user data: ≤ 2048 bytes

The first element of each message is the Start character ("<" for Transfer, "{" for the Response). Accordingly, the

last character of a message is the Stop character (">" for Transfer, "}" for the Response).

The second element of each message is the Message ID (1 character). The Message ID serves the user to dis-

tinguish between different messages. It is only relevant on protocol level (between AT interface and I²C device

driver), i.e. it is not sent to the I²C slave device.

Each transfer to the device is followed by a Response Message sent from the driver to the AT interface. The

response includes the Message ID and either OK ("+") or error characters ("-" or "!"). A successful response to

a Read Message contains the OK character and the read data. If an error occurs on the I²C bus, the response

consists of an error character followed by a 16 bit code specifying the faulty byte.

After each Transfer Message, wait for the Response Message before sending the next Transfer Message.

All characters entered outside a valid message (i.e. not input between Start character "<" and Stop character ">")

are ignored.

19.7.3.1

Structure of Messages on the I²C Bus

Table 19.4: Structure of Transfer and Response Messages on the I²C bus

Frame

Format

Write Transfer Message

< ID SlaveAddress Data >

Maximum length: 2048 bytes for I²C Slave Address

and written data. LSB of I²C Slave Address = "0".

Read Transfer Message

< ID SlaveAddress ReadLength >

Read Length ≤ 2048 bytes. LSB I²C of Slave Address

= "1".

Response Message

Write OK

{ID + }

Read of x bytes OK

{ID + Data }

NAK for x^th byte if Read or Write

{ID - xxxx }

Protocol error in x^th byte

{ID ! xxxx }

On the I²C bus, read and write data are handled in two separate frames transmitted one after the other. This is

because the I²C bus has only two bus lines, I2CDAT (I2CDAT_SPIDO) for the serial data and I2CCLK

(I2CCLK_SPICLK) for the serial clock. Write data are packed into a Transfer Frame. Read data are packed into

Page 493 of 567

19.7 AT^SSPI

a Response Frame. The Transfer Frame contains a Receive or Transmit Request (R/W Request) for the I²C mas-

ter.

In a Transfer Message (Read or Write), the third element is the 7-bit I²C Slave Address (2 characters) that iden-

tifies each single device connected to the bus. The 8^th bit of this byte is the LSB that determines the direction of

the message. If the LSB is "0" the master will write information to the selected slave. If the LSB is "1" the master

will read information sent from the slave.

In a Read Transfer Message on the I²C bus, the size of the expected data must be specified explicitly. This is an

element of 4 characters stating the number of bytes to be read. It must be placed after the I²C Slave Address.

19.7.3.2

Structure of Messages on the SPI

Table 19.5: Structure of Transfer and Response Messages for SPI

Message

Format

Transfer Message

< ID ReadOffset ReadLength Data >

Read Offset = 8 bits

Read Length = 16 bits

Read Offset + Read Length ≤ 2048 bytes

Max. length of read data: 2048 bytes

Response Message

Write OK

{ID +}

Reading x bytes was OK

{ID + Data }

Protocol error in x^th byte

{ID ! xxxx }

The SPI has two serial data lines, DO (I2CDAT_SPIDO) for sending data from the master to the slave, and DI

(SPIDI) for receiving data sent from the slave to the master. Both data lines are controlled by one serial clock

line CLK (I2CCLK_SPICLK). TC65 acts as master providing the clock. Write and read data are handled in the

same Transfer Messages and Response Messages. In a Transfer Message, the next two elements after the ID

are the Read Offset and the Read Length, both required to enable reading data from the slave. The Read Offset

specifies where to start reading, i.e. which byte is the first to start reading from. If the Read Offset is zero then

reading starts from the first byte. The Read Length specifies the number of expected bytes. If the Read Offset is

zero and the Read Length does not equal zero, the master reads the specified number of bytes, starting from the

first byte. If the Read Length is zero, the Read Offset is ignored, meaning that the master will not read data from

the slave. To transmit data from the master to the slave all data can be entered after the Read Length.

In a Response Message the ID is followed by a special character to indicate the result of reading. If successful,

"+" is given, followed by the read data. If reading fails only "!" is received.

19.7.4

Error Handling on the I²C Bus

Protocol error:

If a protocol error is detected the ASCII value "!" is sent to the AT interface. Also, a Stop Condition is sent to the

I²C device.

A protocol error occurs if

• any data / address characters do not equal 0...9, a...f and A...F

• the length of a read word is smaller or greater than 16 bits

• the number of ASCII data is odd (e.g. "af1" instead of "af01")

• the Read or Write request is greater than 2 KB (0x0800).

Acknowledge:

Once a transmission has completed successfully (Write or Read), the special character "+" (ACK) is included in

the Response sent to the AT interface.

During a Write Transfer, the I²C driver acknowledges each transferred byte, but the Response contains only one

ACK which is transmitted only if all bytes are successfully transferred. During a Read Transfer, an ACK is sent

Page 494 of 567

19.7 AT^SSPI

19.7.5

Example: Using I²C Bus

As stated above, it is recommended to run the Terminal program in chat mode or to use the local echo. First,

activate the I²C interface:

AT^SSPI=0010,0000,0000,0000,0000

The first group of characters forms the <basicCon-

CONNECT

figuration>, where the first "0" sets I²C, the sec-

ond "0" is the internal port, the digit "1" sets 400 kbps

bit rate on the I²C bus, and the next "0" selects ASCII

coding. This is followed by a comma and the value

"0000" = no delay time after Write and Read.

Note: If omitted all above parameters are assumed

default.

Therefore,

instead

AT^SSPI=0010,0000,0000 it is sufficient to enter

only AT^SSPI=

The module is in data mode now. This allows you to send a Write Transfer Message:

Write Transfer Frame, where a = ID, AE = Slave

Address and write request.

{a+}

Write Response Message, where a = ID.

Read Transfer Message, where b = ID, AF = Slave

Address and read request,

0010

= number of

expected bytes.

{b+000102030405060708090A0B0C0D0E0F}

Read Response Message, where b = ID.

To quit data mode and return to command mode enter the Close character "#":

The response OK confirms that the ME is back to

command mode and ready to accept any AT com-

mands.

If the ME is in command mode, the response to the read command contains the factory settings.

AT^SSPI?

AT^SSPI=0,0010,0000,0000

The read command returns the connection state "not

connected" (Channel closed) and the factory set-

tings for I²C.

If the ME is in data mode, the response to the read command contains the current settings.

AT^SSPI?

AT^SSPI=1,0010,0012,00FF,0000,0000

The read command returns the connection state

"connected" (Channel open) and the current settings

for I²C.

Page 496 of 567

19.7 AT^SSPI

19.7.6

Example: Transfer and Response Messages on SPI

The following examples shall illustrate the message structure and write/read procedures explained in Section

19.7.3.2, Structure of Messages on the SPI. Blanks are inserted only to better visualize frame elements. In prac-

tice no blanks are allowed.

<0 00 0000 11 22 33>

Transfer Message: The master writes 3 bytes.

{0 +}

Response Message: Transmission successful.

<1 00 0010>

Transfer Message: The master requests to read 16

bytes from the slave. Read Offset is zero, therefore,

reading starts from the first byte.

{1 + 11 22 33 44 ... FF 00}

Response Message: Reading data successful.

<2 03 0008>

Transfer Message: The master requests to read 8

bytes from the slave. Read Offset is 3, therefore,

reading starts from the fourth byte.

{2 + 44 55 66 77 88 99 AA BB}

Response Message: Reading data successful.

<3 03 0004 11 22 33 44 55 66>

Transfer Message: The master writes 6 bytes and

requests to read 4 bytes from the slave. Read Offset

is 3, therefore, reading starts from the fourth byte.

{3 + AA BB CC DD}

Response Message: Reading and writing data suc-

cessful.

Page 497 of 567

19.8 AT^SAADC

19.8

AT^SAADC Show ADC Adjustment Values

The AT^SAADC command is intended only for the TC65 Terminal. It returns TC65 Terminal specific values

needed to recalculate the raw values captured with AT^SRADC in order to obtain the actual voltage applied at the

ADCx_IN input of the Terminal. The recalculation is necessary to account for the effect of component tolerances,

mainly caused by the measurement amplifier inside the TC65 Terminal. The amplifier is used to scale down the

ADCx_IN input voltage of the TC65 Terminal (5V) to the ADCx_IN input voltage of the in-built TC65 Module

(2.4V).

To recalculate the exact voltages measured at the ADC1_IN input use the following equation:

Value = (<value> from AT^SRADC - <ofs1>) * <amp1> / 4096

where the divisor 4096 is constant. For ADC2_IN use the equivalent parameters <ofs2> and <amp2>.

The voltage offset and the amplification factor are specific to each TC65 Terminal. The values are stored in the

device and are not changeable. Therefore, it is necessary to read the values only once in the lifetime of the TC65

Terminal. ADC1_IN and ADC2_IN may have different offset values and amplification factors.

Syntax

Read Command

AT^SAADC?

Response(s)

^SAADC: <ofs1>, <amp1>, <ofs2>, <amp2>

ERROR

+CME ERROR: <err>

Reference(s)

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

SIEMENS

Parameter Description

<ofs1>^(num)

Offset in mV to be deducted from the measurement <value> captured with AT^SRADC at ADC1_IN.

-32768...+32767

<amp1>^(num)

Amplification factor for ADC1_IN

0...65535

The amplification factor is given as 16 bit unsigned integer. An amplification

factor of 1 equals 4096, an amplification factor of 2 equals 8192 etc. The TC65

Terminal has typically an amplification factor around 2. See example below.

<ofs2>^(num)

Offset in mV to be deducted from the measurement <value> captured with AT^SRADC at ADC2_IN.

-32768...+32767

<amp2>^(num)

Amplification factor for ADC2_IN

0...65535

See <amp1> for further detail.

Page 498 of 567

19.8 AT^SAADC

Example

The example shows how to determine the voltage actually measured at ADC1_IN of the TC65 Terminal. First,

find out the voltage offset and the amplification factor required for the recalculation of all later measurements

done with AT^SRADC:

AT^SAADC?

Query voltage offsets and amplification factors.

^SRADC: 3,8533,2,8000

The ADC1_IN line of the TC65 Terminal has the fol-

lowing values: voltage offset

<ofs1>= 3mV and

<amp1>= 8533 which equals an amplification factor

of 2.083251953125. The values of ADC2_IN are not

relevant for this example.

Measure the voltage applied at ADC1_IN:

AT^SRADC=0

Open the ADC1_IN channel and query the voltage

^SRADC: 0,1,433

applied.

The voltage measured at ADC1_IN is 433mV.

Now recalculate the value captured with AT^SRADC:

Value = (433 - 3) * 8533 / 4096 = 895.8mV

The actual voltage measured at ADC1_IN is

895.8mV.

Page 499 of 567

19.9 AT^SRADC

19.9

AT^SRADC Configure and Read ADC Measurement

The AT^SRADC configures the parameters required for ADC measurement (Analog-to-Digital Converter) and

returns the measurement result(s). The value(s) can be delivered once on request by using the single measure-

ment mode, or periodically by specifying the measurement interval.

Note that the TC65 Module uses an unbalanced input with two pins, while the TC65 Terminal has a balanced

input with four pins. This requires different pin names as listed below. See also [2] and [3].

First ADC channel of TC65 Module: ADC1_IN.

Second ADC channel of TC65 Module: ADC2_IN.

First ADC channel of TC65 Terminal: ADC1_IN_P and ADC1_IN_N

Second ADC channel of TC65 Terminal: ADC2_IN_P and ADC2_IN_N

Another major difference btween both products is that the TC65 Terminal requires the measured ADC voltages

to be recalculated. For detail see parameter <value> below as well as the AT^SAADC command.

Syntax

Test Command

AT^SRADC=?

Response(s)

^SRADC:(list of supported <ch>s), (list of supported <oc>s), (list of supported <it>s)

Read Command

AT^SRADC?

Response(s)

Current settings of first and second ADC channel:

^SRADC: <ch>, <oc>, <it>

Write Command

Single measurement. Implies automatic channel open and close (<oc>=1 and 0) and no interval (<it>=0).

AT^SRADC=<ch>

Response(s)

^SRADC: <ch>, <count>, <value>

ERROR

+CME ERROR: <err>

Write Command

Periodic measurement. Requires <oc>=1 and <it>=100ms...30000ms

AT^SRADC=<ch>, <oc>, <it>

Response(s)

ERROR

+CME ERROR: <err>

Reference(s)

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

SIEMENS

Page 500 of 567

19.9 AT^SRADC

Unsolicited Result Code

URC indicating the used channel, the number of measured samples and the voltage. Applies only if periodic

measurement mode is enabled.

^SRADC: <ch>, <count>, <value>[, <value>[, <value>[, <value>[, <value>[, <value>[,

<value>[, <value>[, <value>[, <value>[, <value>]]]]]]]]]]

Parameter Description

<ch>^(num)

Select ADC channel

First ADC channel

(ADC1_IN at TC65 Module. ADC1_IN_P and ADC1_IN_N at TC65 Terminal.)

Second ADC channel

(ADC2_IN at TC65 Module. ADC2_IN_P and ADC2_IN_N at TC65 Terminal.)

<oc>^(num)

Open or close ADC channel

[0]

Close ADC channel specified with <ch>

Open ADC channel specified with <ch>

<it>^(num)

Measurement interval

[0]

Single measurement mode

100...30,000

Output interval in ms at steps of 60/13 ms to enable periodic measurement

mode.

<value>^(num)

Measurement value

-25...+2425

Measured voltage in mV

The measurement accuracy is ±5mV (typically ±2mV).

In the case of the TC65 Module, the captured value is the actual voltage

applied at the ADCx_IN input. No further calculation is required.

In the case of the TC65 Terminal, the captured value is a raw value. The exact

voltage measured at the ADCx_IN_P and ADCx_IN_N inputs needs to be

recalculated using the values obtained with AT^SAADC. See AT^SAADC for

detail.

<count>^(num)

1...11

Number of measured samples

In single measurement mode: <count> is always 1.

In periodic measurement mode: <count> is number of <value>s indicated by

each URC "^SRADC". The higher the sample rate set with <it>, the more mea-

sured values are reported within the URC "^SRADC".

Page 501 of 567

19.9 AT^SRADC

Notes

• If power saving is enabled with AT+CFUN, take into account that the periodic mode lets the ME consume cur-

rent each time the measurement is performed. This reduces the effect of power saving and thus decreases

the operation time.

• If an AT command is input on the same interface where the periodic measurement mode is on, up to 5

"^SRADC" URCs are queued up and sent after AT command completion.

If more than 5 URCs occur before the AT command is completed their measurement values are lost. In this

case, one additional URC with a negative <count> and the single value "32767" is sent along with the first

5 buffered URCs. The negative <count> indicates the number of lost measurement values (not the number

of URCs). See example below.

Examples

EXAMPLE 1

Single measurement

AT^SRADC=0

Open the first ADC channel for single measurement.

^SRADC: 0,1,2375

EXAMPLE 2

Periodic measurement at low sample rate (5s):

AT^SRADC=0,1,5000

Start periodic measurement mode on the first ADC

^SRADC: 0,1,2375

channel. Samples are taken every 5s. Every 5s the

^SRADC: 0,1,2375

URC "^SRADC" appears to report the measured volt-

ages. The second parameter represents the number

^SRADC: 0,1,2375.

of measured samples, in this case only one.

^SRADC: 0,1,2375AT^SRADC=0,0

Stop the periodic measurement.

EXAMPLE 3

Periodic measurement at high sample rate (250ms):

AT^SRADC=0,1,250

Start periodic measurement on the first ADC chan-

^SRADC: 0,4,2375,2375,2375,2375

nel. Samples are taken every 250ms. Every second

^SRADC: 0,4,2375,2375,2375,2375

a URC "^SRADC" appears to report the measured

voltage. The number of samples is 4 or 5.

^SRADC: 0,5,2375,2375,2375,2375,2375

^SRADC: 0,4,2375,2375,2375,2375AT^SRADC=0,0

Stop the periodic measurement.

EXAMPLE 4

Handling of "^SRADC" URCs and AT command execution on the same interface:

AT^SRADC=0,1,250

Start periodic measurement mode on the first ADC

^SRADC: 0,4,2375,2375,2375,2375

channel. Samples are taken every 250ms.

^SRADC: 0,5,2375,2375,2375,2375,2375

^SRADC: 0,4,2375,2375,2375,2375

^SRADC: 0,4,2375,2375,2375,2375AT^SRADC? Input of AT command and <CR> takes 4s.

^SRADC: 0,1,250

^SRADC: 1,0,0

^SRADC: 0,4,2375,2375,2375,2375

4 URCs were buffered during command input and

^SRADC: 0,4,2375,2375,2375,2375

sent after completion.

^SRADC: 0,4,2375,2375,2375,2375

More URCs are delivered.

^SRADC: 0,4,2375,2375,2375,2375

^SRADC: 0,4,2375,2375,2375,2375AT^SRADC? Input of AT command and <CR> takes 7s.

Page 502 of 567

19.10 AT^SWDAC

19.10

AT^SWDAC Configure and Read PWM Signal for DAC

The AT^SWDAC controls the PWM (Pulse Width Modulation) signals generated by means of the DAC_OUT pin

of the TC65 Module. The DAC_OUT pin is not available on the the TC65 Terminal, therefore AT^SWDAC applies

only to the TC65 Module.

Syntax

Test Command

AT^SWDAC=?

Response(s)

^SWDAC:(list of supported <dc>s), (list of supported <oc>s), (list of supported <fq>s)

Read Command

AT^SWDAC?

Response(s)

^SWDAC: <dc>, <oc>, <fq>

ERROR

+CME ERROR: <err>

Write Command

AT^SWDAC=<dc>[, <oc>[, <fq>]]

Response(s)

ERROR

+CME ERROR: <err>

Reference(s)

ASC0

ASC1

USB

MUX1

MUX2

MUX3

Charge

Last

SIEMENS

Parameter Description

<dc>^(num)

Duty cycle in percentage steps

0...100

<oc>^(num)

Open or close DAC

Close DAC

Open DAC

<fq>^(num)

PWM frequency

320 Hz (accuracy of 1 percentage step)

970 Hz (accuracy of 3 percentage steps)

8,125 Hz (accuracy of 1 percentage step)

16,250 Hz (accuracy of 1 percentage step)

Page 504 of 567

20. GPIO Commands

20.

GPIO Commands

This chapter describes the AT commands needed to access and configure the GPIO pins of the TC65.

Please also refer to [2] for electrical specifications of the GPIOs and their signal states after startup and during

application.

Except for the pulse counter commands, usage of all GPIO commands is restricted to the same interface where

the GPIO driver was openend with AT^SPIO. Any attempt to access GPIOs from another interface will be denied

with an error message.

When the TC65 starts up, all GPIO pins are set to high-impedance state after initializing. Therefore, it is recom-

mended to connect pull-up or pull-down resistors to all GPIO pins you want to use as output. This is necessary

to keep these pins from floating or driving any external devices before all settings are done by AT command (at

least AT^SPIO, AT^SCPIN), and after closing the GPIOs again.

20.1

AT^SPIO General Purpose IO Driver Open/Close

The AT^SPIO write command opens and closes the general purpose IO driver. The command must be executed

before any other GPIO command can be used. After closing the driver, all pins used (i.e. opened) will be put into

high impedance state (inputs) with no internal pull up or down.

The command does not reserve any general purpose IO pin, only the drivers required for GPIO pin management

will be loaded.

Syntax

Test Command

AT^SPIO=?

Response(s)

^SPIO:(list of supported <mode>s)

Write Command

AT^SPIO=<mode>

Response(s)

ERROR

+CME ERROR: <err>

Reference(s)

PIN ASC0 ASC1

USB

MUX1

MUX2

MUX3

Charge

Last

SIEMENS

Parameter Description

<mode>^(num)

Close General purpose IO driver

Open General purpose IO driver

Page 506 of 567

20.2 AT^SCPIN

20.2

AT^SCPIN Pin Configuration

The AT^SCPIN write command serves to add (or remove) and configure pins.

Syntax

Test Command

AT^SCPIN=?

Response(s)

^SCPIN:(list of supported <mode>s), (list of supported <pin_id>s), (list of supported <direction>s), (list

of supported <startValue>s)

Write Command

AT^SCPIN=<mode>, <pin_id>, <direction>[, <startValue>]

Response(s)

ERROR

+CME ERROR: <err>

Reference(s)

ASC0

ASC1

USB

MUX1

MUX2

MUX3

Charge

Last

SIEMENS

Parameter Description

<mode>^(num)

Close pin

Open pin

<pin_id>^(num)

Pin identifier

GPIO1

GPIO2

GPIO3

GPIO4

GPIO5

GPIO6

GPIO7

GPIO8

GPIO9

GPIO10 - The GPIO10 pin can be used either as GPIO or as pulse counter. If

configured as GPIO, the pulse counter option cannot be enabled. Vice versa,

if configured as pulse counter the GPIO option is not available. See AT^SCCNT

and AT^SSCNT for further details on the pulse counter.

<direction>^(num)

Parameter <direction> is mandatory when opening a pin, but can be omitted when closing a pin

Input

Output

Page 507 of 567

20.3 AT^SCPOL

20.3

AT^SCPOL Polling Configuration

The AT^SCPOL write command serves to start and stop polling a pin or port specified with <io_id>. The pin or

port must already be configured via AT^SCPIN or AT^SCPORT. Polling is only applicable to input pins.

After polling has been activated on a specified pin or port, all new values related to this pin or port will be reported

via the "^SCPOL" URC.

Syntax

Test Command

AT^SCPOL=?

Response(s)

^SCPOL:(list of supported <mode>s), (list of supported <io_id>s)

Write Command

AT^SCPOL=<mode>, <io_id>

Response(s)

ERROR

+CME ERROR: <err>

Reference(s)

PIN ASC0 ASC1

USB

MUX1

MUX2

MUX3

Charge

Last

SIEMENS

Unsolicited Result Code

^SCPOL: <io_id>, <value>

Parameter Description

<mode>^(num)

Suppress polling

Activate polling

<io_id>^(num)

This can be either a <pin_id> already configured or a <port_id> already opened.

<value>^(num)

New value on this <io_id>.

Low for <pin_id>

High for <pin_id>

0...1023

For <port_id>

Page 509 of 567

20.3 AT^SCPOL

Notes

• The pins will be polled at every TDMA frame interrupt, i.e. every 4.616ms. In SLEEP mode, the frequency of

polling is reduced, as polling will be done only when the module shortly suspends power saving when CTS is

activated. So in SLEEP mode polling intervals are extended to a range from 0.9s to 2.7s.

After a state change has been detected the "^SCPOL" URC is issued if the state of the pin remains stable for

8 TDMA frames (= 36.93ms) in Normal mode, or accordingly, 0.9s to 2.7s in SLEEP mode.

• If the <value> of one or more of the polled pins has changed since polling has been performed last time, or

since a particular pin or its entire port have last been queried with AT^SGIO, polling will be suspended to send

a URC. There will be one URC reported for each polled pin whose <value> has changed, and one for each

polled port with one or more changed pins.

Page 510 of 567

20.4 AT^SCPORT

20.4

AT^SCPORT Port Configuration

With AT^SCPORT a group of maximum 10 pins can be configured to act as a parallel port, which can be controlled

with a single AT command. A pin can only be added once to a port, and only to a port. The first, i.e. left most

parameter, corresponds to the port's LSB.

All pins of a port must be set to the same direction (input or output). See AT^SCPIN.

Syntax

Test Command

AT^SCPORT=?

Response(s)

Write Command

AT^SCPORT=<pin_id>₁[, <pin_id>₂[, <pin_id>₃[, <pin_id>₄[, <pin_id>₅[, <pin_id>₆[, <pin_id>₇[,

<pin_id>₈[, <pin_id>₉[, <pin_id>₁₀]]]]]]]]]

Response(s)

^SCPORT: <port_id>

ERROR

+CME ERROR: <err>

Reference(s)

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

SIEMENS

Parameter Description

<port_id>^(num)

Assigned port

<pin_id>^(num)

Pin ID of the xth pin of this port

See AT^SCPIN for possible pin value.

Page 511 of 567

20.6 AT^SGIO

20.6

AT^SGIO Get IO state of a specified pin or port

Syntax

Test Command

AT^SGIO=?

Response(s)

^SGIO:(list of supported <io_id>s)

Write Command

AT^SGIO=<io_id>

Response(s)

^SGIO: <value>

ERROR

+CME ERROR: <err>

Reference(s)

PIN ASC0 ASC1

USB MUX1 MUX2

MUX3

Charge

Last

SIEMENS

Parameter Description

<io_id>^(num)

This can be either an already configured <pin_id> or an already opened <port_id>.

<value>^(num)

State read on this <io_id>.

Low for <pin_id>

High for <pin_id>

0...1023

For <port_id>

Note

• If one gets the state of a port whose width is less than 10 bits, the bits of <value> that are more significant

than the MSB of the port are set to zero.

Page 513 of 567

20.7 AT^SSIO

20.7

AT^SSIO Set IO state of a specified pin or port

Syntax

Test Command

AT^SSIO=?

Response(s)

^SSIO:(list of supported <io_id>s), (list of supported <value>s)

Write Command

AT^SSIO=<io_id>, <value>

Response(s)

ERROR

+CME ERROR: <err>

Reference(s)

PIN ASC0 ASC1

USB MUX1 MUX2

MUX3

Charge

Last

SIEMENS

Parameter Description

<io_id>^(num)

This can be either an already configured <pin_id> or an already opened <port_id>.

<value>^(num)

State to be set for this <io_id>.

Low for <pin_id>

High for <pin_id>

0...1023

For <port_id>

Notes

• If you set a state on a port whose width is less than 10 bits, the bits of <value> that are more significant than

the MSB of the port are ignored.

• The write command is only applicable to <pin_id>s or <port_id>s which are configured as output.

Page 514 of 567

20.8 AT^SCCNT

20.8

AT^SCCNT Configure Pulse Counter

The AT^SCCNT write command serves to configure the GPIO10 pin as pulse counter. The pulse counter is

designed to measure signals from 0 to 1000 pulses per second.

Remember that if the GPIO10 line is configured as GPIO (see AT^SCPIN) any attempt to activate the pulse

counter will be rejected. Vice versa, if the pulse counter is opened the GPIO10 line cannot be configured as

GPIO.

See also [2] for further detail on the pulse counter.

Syntax

Test Command

AT^SCCNT=?

Response(s)

^SCCNT:(list of supported <action>s), (list of supported <mode>s), (list of supported <limit>s)

Read Command

AT^SCCNT?

Response(s)

^SCCNT: <action>, <mode>[, <limit>]

ERROR

+CME ERROR: <err>

Write Command

AT^SCCNT=<action>, <mode>[, <limit>]

Response(s)

ERROR

+CME ERROR: <err>

Reference(s)

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

SIEMENS

Unsolicited Result Code

^SCCNT: <time>

The URC applies only to the Limit counter mode set with parameter <mode>=1. It is delivered once the pulse

counter has completed counting the number of pulses requested with parameter <limit>.

Parameter Description

<action>^(num)

Close pulse counter

Open pulse counter

Page 515 of 567

20.8 AT^SCCNT

<mode>^(num)

Activates the Start-Stop counter mode.

After setting this mode, use AT^SSCNT and the <action> parameter to start

or stop the pulse counter or to read out the measured pulses.

Activates the Limit counter mode and immediately starts the pulse counter.

Parameter <limit> is mandatory for this mode.

<limit>^(num)

1...65534

Number of pulses to be counted.

Parameter <limit> applies only to the Limit counter mode and is mandatory

for this mode. Once the given number of pulses is reached, the ME sends one

single URC "^SCCNT" which indicates the parameter <time>.

<time>^(num)

1...65534

Time (in milliseconds) taken to count the number of pulses specified with

<limit>.

Note

• Measurement accuracy: In Limit counter mode, the parameter <time> implies an inaccuracy <5ms.

20.8.1

Using the Pulse Counter in Limit Counter Mode

This example assumes that a 1 kHz frequency is applied at the GPIO10 pin. Limit counter mode is enabled to

request the time the pulse counter needs to count a specified number of pulses.

at^sccnt=1,1,1000

Open pulse counter, enable Limit counter mode, request the time

needed to count 1000 pulses.

^SCCNT: 0000001047

"^SCCNT" URC indicates the time taken to count 1000 pulses.

at^sccnt=1,1,2000

Open pulse counter, enable Limit counter mode, request the time

needed to count 2000 pulses.

^SCCNT: 0000002040

"^SCCNT" URC indicates the time taken to count 2000 pulses.

at^sccnt=1,1,10000

Open pulse counter, enable Limit counter mode, request the time

needed to count 10000 pulses.

^SCCNT: 0000010043

"^SCCNT" URC indicates the time taken to count 10000 pulses.

at^sccnt=1,1,20000

Open pulse counter, enable Limit counter mode, request the time

needed to count 20000 pulses.

^SCCNT: 0000020040

"^SCCNT" URC indicates the time taken to count 20000 pulses.

This example shows how to stop the Limit counter mode and close the pulse counter without waiting for the

"^SCCNT" URC. Both methods have the same effect, it is up to you which one to use.

at^sccnt=0,0

Stop and close the pulse counter immediately, without "^SCCNT" URC

being indicated.

at^sscnt=3

Stop and close the pulse counter immediately, without "^SCCNT" URC

being indicated.

Page 516 of 567

20.9 AT^SSCNT

20.9

AT^SSCNT Start and Stop Pulse Counter

The AT^SSCNT write command serves to read, start, restart and stop the pulse counter.

Syntax

Test Command

AT^SSCNT=?

Response(s)

^SSCNT:(list of supported <action>s)

Read Command

AT^SSCNT?

Response(s)

^SSCNT: <action>

If an error occurs:

ERROR

+CME ERROR: <err>

Write Command

AT^SSCNT=<action>

Response(s)

If <action>=0 or 1:

If <action>=2 or 3:

"^SSCNT" URC with parameter <pulse>

If an error occurs:

ERROR

+CME ERROR: <err>

Reference(s)

ASC0

ASC1

USB

MUX1

MUX2

MUX3

Charge

Last

SIEMENS

Unsolicited Result Code

^SSCNT: <pulse>

The URC applies only to the Start-Stop mode set with AT^SCCNT, parameter <mode>=0. It is delivered once the

pulse counter result was requested with <action>=2 or the pulse counter was stopped with <action>=3. The

URC indicates the number of pulses counted.

Parameter Description

<action>^(num)

This parameter can only be used after configuring the pulse counter with AT^SCCNT. The <action> types 0, 1

and 2 apply only to the Start-Stop counter mode set with AT^SCCNT.

Reset and start pulse counter from 0.

Restart pulse counter and continue counting from the <pulse> value of the

last run.

Read out current <pulse> value.

Page 517 of 567

20.9 AT^SSCNT

The effect of value 3 depends on the selected counter mode:

If AT^SCCNT, parameter

<mode>=

(Start-Stop counter mode), then

<action> type 3 stops the pulse counter and displays, as "^SSCNT" URC, the

number of pulses counted until this time.

If AT^SCCNT, parameter <mode>= 1 (Limit counter mode), then <action>

type 3 immediately stops the pulse counter without indicating the "^SCCNT"

URC. This action has the same effect as the command AT^SCCNT=0,0.

<pulse>^(num)

Measurement result of the pulse counter in Start-Stop mode, indicated within the "^SSCNT" URC, if AT^SCCNT,

parameter <action>=2 or 3. The value range of <pulse> is 32 bits (2³²-1).

0...4294967295

Number of pulses counted.

Note

• Measurement accuracy: In Start-Stop mode, you can achieve 100% accuracy if you take care that pulse trans-

mission begins after the start command (AT^SSCNT=0 or 1) has returned OK and ends before the stop com-

mand (AT^SSCNT=3) is issued.

20.9.1

Using the Pulse Counter in Start-Stop Counter Mode

at^sccnt=1,0

Open pulse counter and enable Start-Stop counter mode.

at^sscnt=0

Reset and start pulse counter from 0.

at^sscnt=2

Request value.

^SSCNT: 0000003254

"^SSCNT" URC indicates number of pulses counted.

at^sscnt=2

Request value.

^SSCNT: 0000010024

"^SSCNT" URC indicates number of pulses counted.

at^sscnt=2

Request value.

^SSCNT: 0000015134

"^SSCNT" URC indicates number of pulses counted.

at^sscnt=3

Request value and stop pulse counter.

^SSCNT: 0000021020

"^SSCNT" URC indicates number of pulses counted until this time.

at^sscnt=2

Request value.

^SSCNT: 0000021020

"^SSCNT" URC still indicates the count of the last run.

at^sscnt=1

Restart pulse counter at the value of the last run.

at^sscnt=2

Request value.

^SSCNT: 0000022123

"^SSCNT" URC indicates number of pulses incremented from the last

run.

Page 518 of 567

21. Java related Commands

21.

Java related Commands

This chapter describes the AT commands related to Java applications processed by the TC65.

21.1

AT^SJRA Run Java Application

The AT^SJRA write command launches the Java application.

Syntax

Test Command

AT^SJRA=?

Response(s)

("IMlet path")

Write Command

AT^SJRA=<appName>

Response(s)

^SJRA:

If not successful:

ERROR

+CME ERROR: <err>

Reference(s)

PIN ASC0

ASC1

USB

MUX1

MUX2

MUX3

Charge

Last

SIEMENS

Parameter Description

<appName>^(str)

Path of the Java application

The application name must be given as a fully qualified pathname (a:/.../...) to the jar/jad file containing the

desired application.

The local flash file system is identified by: A:. Directory separator is ''/'' (002Fh).

Example: A:/java/jam/example/helloworld/helloworld.jar

Notes

• As an alternative, the Java application can be enabled to start up automatically whenever TC65 is getting

started. Use the AT^SCFG command to make all the settings need for the Java autostart mode.

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

Page 519 of 567

21.2 AT^SJNET

21.2

AT^SJNET Set Dialup Network Access Parameters

The AT^SJNET write command allows to create a profile which contains all parameters needed for automated

network access through a dialup connection.

Syntax

Test Command

AT^SJNET=?

Response(s)

^SJNET:("csd"|"gprs"), ("Tel. num."|"access point name"), ("login"), ("password"), ("dns"), (list of supported

<timeout>s)

Read Command

AT^SJNET?

Response(s)

^SJNET: <bearer service>, <entry point>, <login>, <password>, <dns>, <timeout>

ERROR

+CME ERROR: <err>

Write Command

AT^SJNET=<bearer service>, <entry point>, <login>, <password>[<dns>][, <timeout>]

Response(s)

^SJNET: <bearer service>, <entry point>, <login>, <password>, <dns>, <timeout>

ERROR

+CME ERROR: <err>

Reference(s)

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

SIEMENS

Page 520 of 567

21.2 AT^SJNET

Parameter Description

<bearer service>^(str)(+CSCS)

"none"^(P)

No bearer specified

"csd"

Dialup access uses Circuit Switched Data connection

"gprs"

Dialup access via GPRS

<entry point>^(str)(+CSCS)

""^(P)

The content of parameter <entry point> depends on <bearer service>.

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

• If <bearer service> is "csd", then parameter specifies the dialup phone

number. The phone number can be modified to select between ISDN and

anlaog call and to choose a bitrate. See also examples below.

- The first character added to the phone number selects the mode: i =

ISDN call, a = analog call (default). If omitted the default setting "analog"

applies.

- The last character appended to the phone number determines the

bitrate. If omitted the default setting "9600 bps" applies.

h = 14400 bps

m = 9600 bps (default)

= 4800 bps

s = 2400 bps

• If

<bearer service> is "gprs", then parameter specifies the GPRS

access point name.

<login>^(str)(+CSCS)

""^(P)

Specifies the login name for access to the dialup network.

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

<password>^(str)(+CSCS)

""^(P)

Specifies the password for access to the dialup network.

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

<dns>^(str)(+CSCS)

""^(P)

Specifies the Primary DNS server (Nameserver) for the dialup network. The

server address has to be specified in dotted IP address format

(e.g.

145.146.147.148). If the parameter is omitted, the DNS assigned by the net-

work is used.

It is recommended to set manual DNS server addresses rather than using

automatic DNS assignment. This avoids problems in case the network is

unable to properly handle the automatic DNS service.

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

<timeout>^(num)

Idle Timeout in seconds

0^(P)...[30]...21600

Specifies the Java network idle timeout, which is the number of seconds to wait

before the network connection is terminated automatically when no data trans-

fer or other network activities take place. The value 0 means no timeout at all

(you have to terminate a Circuit Switched Data connection using ATH and a

GPRS connection using AT+CGATT=0).

We recommend to use values greater than 10 seconds because otherwise you

may get unintentional timeouts for slow network connections.

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

Page 521 of 567

21.2 AT^SJNET

Note

• The authentication mode for CSD and GPRS is always PAP.

Examples

EXAMPLE 1

This example illustrates how to configure a profile for circuit switched network access: The dialup phone num-

ber is +49800654321, user name is "user1", password is "dialup123", and the primary DNS has IP address

"145.146.147.148". The phone number does not contain additional characters, therefore the destination is an

analog device (default) and the bitrate is 9600 bps (default).

AT^SJNET="CSD", "+49800654321", "user1", "dialup123", "145.146.147.148"

^SJNET: "csd","+49800654321","user1","dialup123","145.146.147.148",30

EXAMPLE 2

Same example as above, but the phone number contains additional characters for ISDN and 14400bps.

AT^SJNET="CSD", "i+49800654321h", "user1", "dialup123", "145.146.147.148"

^SJNET: "csd","i+49800654321h","user1","dialup123","145.146.147.148",30

Page 522 of 567

21.3 AT^SJOTAP

21.3

AT^SJOTAP Over The Air Application Provisioning

The AT^SJOTAP command serves to control and start OTAP operations for installing and updating Java appli-

cations over the air. Detailed explanations can be found in [4].

The AT^SJOTAP write command sets the password and all parameters required to install / delete a Java Appli-

cation.

The AT^SJOTAP execute command starts the OTAP install process.

Syntax

Test Command

AT^SJOTAP=?

Response(s)

^SJOTAP:<SMS_pwd>, <Jad_URL>, <Appl_Dir>, <HTTP_User>, <HTTP_Pwd>, <BS>, <Dest>,

<Net_user>, <Net_pwd>, <DNS>, <NotifyURL>

Read Command

AT^SJOTAP?

Response(s)

^SJOTAP: <SMS_pwd>, <Jad_URL>, <Appl_Dir>, <HTTP_User>, <HTTP_Pwd>, <BS>, <Dest>,

<Net_user>, <Net_pwd>, <DNS>, <NotifyURL>

ERROR

+CME ERROR: <err>

Exec Command

AT^SJOTAP

Response(s)

ERROR

+CME ERROR: <err>

Write Command

AT^SJOTAP=[<SMS_pwd>][, <Jad_URL>][, <Appl_Dir>][, <HTTP_User>][, <HTTP_Pwd>][, <BS>][,

<Dest>][, <Net_user>][, <Net_pwd>][, <DNS>][, <NotifyURL>]

Response(s)

ERROR

+CME ERROR: <err>

Reference(s)

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

SIEMENS

Parameter Description

<SMS_pwd>^(str)

Password for OTAP SMS authentification

<Jad_URL>^(str)

URL of update file

Page 523 of 567

21.3 AT^SJOTAP

<Appl_Dir>^(str)

Directory of Java application

Directory on the ME where a new application (JAD and JAR file) is installed. When entering the application direc-

tory with the AT^SJOTAP write command be sure that the path name is not terminated with a slash. For example,

type "a:" or "a:/otap" rather than "a:/" or "a:/otap/".

<HTTP_User>^(str)

HTTP user name

<HTTP_Pwd>^(str)

HTTP password

<BS>^(str)

Bearer Service

"csd"

Use Bearer service "Circuit Switched".

"gprs"

Use Bearer service "GPRS".

<Dest>^(str)

Destination

Phone number if <BS>="csd" or Access point name (APN)if <BS>="gprs".

The phone number can be modified to select between ISDN or analog and to choose the bitrate. The format of

the phone number and the default settings are the same as in the case of AT^SJNET (see parameter <entry

point> for instructions). Please note that if no additional characters are used to modify the phone number then

the default settings a = analog call and m = 9600 bps are assumed.

<Net_user>^(str)

User name for accessing the network

<Net_pwd>^(str)

Password for accessing the network

<DNS>^(str)

Domain Name Server

<NotifyURL>^(str)

URL to which result codes are posted

Notes

• The authentication mode for CSD and GPRS is always PAP.

• All parameters which are left out in the write command are set to "not configured", while parameters which

are entered as "" will be stored as an empty string.

• Parameters that have not been configured via AT command, can be configured via SMS (see [4]).

• Parameters that have been configured via AT command cannot be reconfigured / overwritten via SMS.

• If the execute command ends up with an error, one or more mandatory parameters have not been specified

(see [4]).

Page 524 of 567

21.4 AT^SJSEC

21.4

AT^SJSEC Write Binary Java Security Data

To configure the Java security environment special Java security commands and a mobile-specific security cer-

tificate must be transferred to the module in binary format. This is done with the help of AT^SJSEC. The

AT^SJSEC execute command activates the binary data mode which allows to send binary data from the host

application to the ME. The AT^SJSEC read command requests the current status of the Java security environ-

ment.

A detailed description of how to create the binary files and configure the Java security environment can be found

in [4].

Syntax

Read Command

AT^SJSEC?

Response(s)

^SJSEC:<mode>, <HTTPS state>, <OBEX state>, <untrusted domain>[, <Certificate

content>]

Exec Command

AT^SJSEC

Response(s)

CONNECT

JSEC READY: SEND COMMAND ...

(Indicates that the ME entered the binary data mode. The host application can start to send the binary data.)

Reference(s)

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

SIEMENS

Parameter Description

<mode>^(num)

Java security mode

0^(D)

Unsecured mode, i.e. security mode not active.

Secured mode, i.e. security mode active.

<HTTPS state>^(num)

0^(D)

HTTPS connection or Secure Connection is possible if the server certificate (or

the certificate chain) is valid.

HTTPS connection or Secure Connection is possible only if the server certifi-

cate is signed by the customer (owner of the root certificate in device).

<OBEX state>^(num)

Start of Module Exchange Suite is not permitted.

1^(D)

Start of Module Exchange Suite is permitted.

Page 525 of 567

22. Miscellaneous Commands

22.

Miscellaneous Commands

The AT Commands described in this chapter are related to various areas.

22.1

A/ Repeat previous command line

Syntax

Exec Command

Response(s)

Reference(s)

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

V.250

Command Description

Repeat previous command line.

Notes

• Line does not need to end with terminating character.

• After beginning with the character "a" or "A" a second character "t", "T" or "/" has to follow. In case of using a

wrong second character, it is necessary to start again with character "a" or "A".

• If autobauding is active, the command A/ cannot be used (see AT+IPR).

Page 527 of 567

22.2 ATS3

22.2

ATS3

Set command line termination character

The ATS3 command determines the character recognized by the TA to terminate an incoming command line.

Syntax

Read Command

ATS3?

Response(s)

<n>

Write Command

ATS3=<n>

Response(s)

ERROR

Reference(s)

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3

Charge

Last

V.250

Parameter Description

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

command line termination character

000...13^(&F)...127

Notes

• Using a value other than the default 13 may cause problems when entering commands.

• Whenever you change the setting take into account that the new value has no effect on the URC "^SHUT-

DOWN".

Page 528 of 567

22.5 AT^SFDL

22.5

AT^SFDL Enter Firmware Download Mode

The AT^SFDL command allows the application manufacturer to download TC65 firmware into the module by

starting the download process from the host application or a customer-designed download program. The down-

load can be done over the serial interfaces ASC0 or ASC1 or the USB interface.

For this purpose, the TC65 firmware update file must be available in the format *.USF. The file can be requested

from Siemens. The firmware file consists of records to be transferred one by one from the host application to the

module.

This manual only describes the handling of the AT^SFDL command. All technical requirements and steps to pre-

pare the host application for this download solution can be found in the Application Note "Updating Firmware".

An example for developing an appropriate download program is included.

The AT^SFDL write command causes the module to reset and enter the firmware update mode. This will be used

to read previous downloaded firmware data.

The AT^SFDL execute command causes the module to reset and enter the firmware download mode (this may

take some milliseconds). After entering the download mode the module sends the start pattern HEX 0x01

("ANSWER_OK") to the application to indicate its ready state. Next, the application shall start to send the records

of the firmware file. Each record received on the module is acknowledged to the host application. Once all

records are successfully received, the module shuts down automatically.

If the module is switched on although it has no valid firmware installed, it waits 60s for the AT^SFDL command

(or for another download method to be started). If neither the AT^SFDL command nor equivalent characters from

another download method are received the module switches off after a 60s timeout.

If a valid firmware is still installed, but the AT^SFDL command is issued without sending any firmware afterwards

the module will stay in ready state. In this case it must be switched off.

Syntax

Test Command

AT^SFDL=?

Response(s)

^SFDL:(list of supported <mode>s)

Exec Command

AT^SFDL

Response(s)

0x01

Write Command

AT^SFDL=<mode>

Response(s)

ERROR

+CME ERROR: <err>

Reference(s)

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

SIEMENS

Page 531 of 567

23. Appendix

23.

Appendix

23.1

Restricted access to SIM data after SIM PIN authentication

Users should be aware that when using a phonebook, SMS or Remote SAT command quickly after SIM PIN

authentication the SIM data may not yet be accessible, resulting in a short delay before the requested AT com-

mand response is returned. This delay is due to the initial process of loading SIM data once after SIM PIN authen-

tication. The duration of loading SIM data is dependent on the SIM card used and may take a couple of seconds.

The "^SSIM READY" URC enabled with AT^SSET can be used to notify the user when the ME has finished read-

ing the SIM card and SIM data are accessible after SIM PIN authentication. Of course, all phonebook and SMS

commands may be issued before the URC is delivered. In this case the AT command response (for example the

complete phonebook) will appear after the delay mentioned above, but before the "^SSIM READY" URC is dis-

played. See example below.

After the "+CREG: 1" (or "+CREG: 5") URC and before the "^SSIM READY" URC it is not sure that outgoing and

incoming calls can be made and short message functions executed. Emergency calls are possible. Outgoing and

incoming calls are always possible AFTER having received the "+CREG: 1" (or "+CREG: 5") and "^SSIM READY"

URCs. See also Section 8.4, Network registration.

Example:

AT^SSET=1

Activate the "^SSIM READY" URC.

AT&W

Store the presentation mode of the "^SSIM READY"

URC to the user profile.

AT+CFUN=1,1

Restart the ME.

^SYSSTART

The ME was restarted.

AT+CPIN

Enter the SIM PIN.

AT+CPBW=50,"+4030123456789",145,"Paul"

Write a new phonebook record.

^SSIM READY

The URC nowconfirms that the ME has finished

reading data from the SIM.

AT+CPBR=50,50

Read the phonebook entered before.

+CPBR: 50,"+4030123456789",145,"Paul"

The phonebook entry was properly saved.

Page 533 of 567

23.2 Star-Hash (*#) Network Commands

23.2

Star-Hash (*#) Network Commands

The following command strings can be sent to the network via ATD and have to be terminated with a semicolon.

The command strings are defined with GSM 2.30 [20].

Table 23.1: Star-Hash (*#) Command Overview

Star-Hash Code

Functionality

Response, also refer to Table 23.3

Phone Security

*#06#

Query IMEI

<IMEI> OK

**04[2]*oldPin[2]*newPin[2]*new-

Change SIM pwd

+CME ERROR: <err> / OK

Pin[2]#

**05[2]*unblKey[2]*newPin[2]*new-

Change/Unblocking SIM pwd

+CME ERROR: <err> / OK

Pin[2]#

*#0003*MasterPhoneCode#

Unlock ''PS'' lock with Master

+CME ERROR: <err> / OK

Phone Code

*[*]03*[ZZ]*oldPw*newPw*newPw#

Registration of net password

+CME ERROR: <err> / OK

Phone number presentation

*#30#

Check status of CLIP (Calling Line

+CLIP : <n>,<m> OK (see

Identification Presentation)

AT+CLIP)

*#31#

Check status of CLIR (Calling Line

+CLIR : <n>,<m> OK (see

Identification Restriction)

AT+CLIR)

*31#<Phonenumber>[;]

Suppress CLIR

(see AT+CLIR)

#31#<Phonenumber>[;]

Activate CLIR

(see AT+CLIR)

*#76#

Check status of COLP (Connected

+COLP : <n>,<m> OK (see:

Line Identification Presentation)

AT+COLP)

*#77#

Check status of COLR (Connected

+COLR : 0,<m> OK (where <m> =

Line Identification Restriction)

active or not active)

Call forwarding

(choice of *,#,*#,**,##)21*DN*BS#

Act/deact/int/reg/eras CFU

^SCCFC : <reason>, <status>,

<class> [,...] like +CCFC ^*) (see:

AT+CCFC)

(choice of *,#,*#,**,##)67*DN*BS#

Act/deact/int/reg/eras CF busy

see above

(choice of

Act/deact/int/reg/eras CF no reply

see above

*,#,*#,**,##)61*DN*BS*T#

(choice of *,#,*#,**,##)62*DN*BS#

Act/deact/int/reg/eras CF no reach

see above

(choice of

Act/deact/int/reg/eras CF all

see above

*,#,*#,**,##)002*DN*BS*T#

(choice of

Act/deact/int/reg/eras CF all cond.

see above

*,#,*#,**,##)004*DN*BS*T#

Call waiting

(choice of *,#,*#)43*BS#

Activation/deactivation/int WAIT

+CCWA : <status>, <class> [,...]

like +CCWA ^*) (see: AT+CCWA)

Page 534 of 567

23.2 Star-Hash (*#) Network Commands

Star-Hash Code

Functionality

Response, also refer to Table 23.3

Call barring

(choice of *,#,*#)33*Pw*BS#

Act/deact/int BAOC

^SCLCK : <fac>, <status>, <class>

[, ...] like +CLCK ^*) (Refer to

AT+CLCK)

(choice of *,#,*#)331*Pw*BS#

Act/deact/int BAOIC

see above

(choice of *,#,*#)332*Pw*BS#

Act/deact/int BAOIC exc.home

see above

(choice of *,#,*#)35*Pw*BS#

Act/deact/int. BAIC

see above

(choice of *,#,*#)351*Pw*BS#

Act/deact/int BAIC roaming

see above

#330*Pw*BS#

Deact. All Barring Services

see above

#333*Pw*BS#

Deact. All Outg.Barring Services

see above

#353*Pw*BS#

Deact. All Inc.Barring Services

see above

Call Hold / Multiparty

C[C] in call

Call hold and multiparty

+CME ERROR: <err> / OK

USSD messages

[C]...[C]#

Send USSD message

+CME ERROR: <err> / OK

C[C] (excluded 1[C])

Send USSD message

+CME ERROR: <err> / OK

*) Notes on ^SCCFC, +CCWA, ^SCLCK: The output depends on the affected basic service of the Star-Hash code. One line

will be output for every tele- or bearer service coded in basic service code BS.

^SCCFC and ^SCLCK are modified by giving an additional <reason> or <fac> in front of the regular output string gener-

ated by the standard commands +CCFC and +CLCK.

Table 23.2: Abbreviations of Codes and Parameters used in Table 23.1

Abbreviation

Meaning

Value

Type of supplementary services:

Barring services

330

All services

Not specified

Dialing number

String of digits 0-9

Basic service equivalent to parameter class:

Voice

FAX

SMS

SMS+FAX

Data circuit asynchron

Data circuit synchron

dedicated PAD access

dedicated Packet access

Data circuit asynchron+PAD

Data circuit synchron+Packet

Data circuit asynchron+synchron+Packet+PAD

All Services

Time in seconds

In contrast to AT+CCFC, parameter

T has no default value. If T is not

specified, an operator defined

default or the last known value may

be used, depending on the network

operator.

Page 535 of 567

23.2 Star-Hash (*#) Network Commands

Abbreviation

Meaning

Value

Password

Character of TE character set (e.g. asterics, hash

or digit in case of USSD, or digits in case of held

calls or multiparty calls)

Table 23.3: Star-Hash Command Response Parameters

Parameter

Meaning

<m>

Mode: 0 = not active, 1 = active

<n>

Unsolicited result code: 0 = presentation disabled, 1 = presentation enabled

Status: 0 = not active, 1 = active

<class>

Represents BS = basic service, refer to AT+CCFC, AT+CLCK

<fac>

Facility lock, refer to AT+CLCK

Call forwarding reason

For exact specification of format and parameters for Star-Hash commands refer to GSM 02.04, Table 3.2 [19]

and GSM 02.30, Annex C [20].

Table 23.4: Star-Hash Commands for Supplementary Services

Star-Hash Code

Abbreviations in Table 23.1

Functionality

act

Activate (except for CLIR, see list above)

reg

int

Check status (interrogate)

deact

Deactivate (except for CLIR, see list above)

eras

Unregister and deactivate

Page 536 of 567

23.3 Available AT Commands and Dependency on SIM PIN

23.3

Available AT Commands and Dependency on SIM PIN

; ... Command not available

! ... Command does not require PIN1

% ... Command requires PIN1

§ ... Command sometimes requires PIN1

Table 23.5: Available AT Commands and Dependency on SIM PIN

AT Command

Exec

Test

Read

Write

Configuration Commands

AT&F

;

AT&V

;

AT&W

;

ATQ

;

ATV

;

ATX

;

AT\V

;

ATZ

;

AT+CFUN

;

AT^SMSO

;

AT+GCAP

;

AT+CMEE

;

AT+CSCS

;

AT^SCFG

;

AT^SM20

;

Status Control Commands

AT+CMER

;

AT+CIND

;

AT^SIND

;

AT+CEER

;

ATS18

;

AT+CPAS

;

AT+WS46

;

Serial Interface Control Commands

AT\Q

;

AT&C

;

AT&D

;

AT&S

;

ATE

;

AT+ICF

;

AT+IFC

;

Page 537 of 567

23.3 Available AT Commands and Dependency on SIM PIN

AT Command

Exec

Test

Read

Write

AT+ILRR

;

AT+IPR

;

AT+CMUX

;

AT^STPB

;

Security Commands

AT+CPIN

;

AT+CPIN2

;

AT^SPIC

AT+CLCK

;

AT^SLCK

;

AT+CPWD

;

AT^SPWD

;

AT^SCSL

;

Identification Commands

ATI

;

AT+CGMI

;

AT+GMI

;

AT+CGMM

;

AT+GMM

;

AT+CGMR

;

AT+GMR

;

AT+CGSN

;

AT+GSN

;

AT+CIMI

;

Call related Commands

ATA

;

ATD

;

ATD><mem><n>

;

ATD><n>

;

ATD><str>

;

ATDI

;

ATDL

;

ATH

;

AT+CHUP

;

AT^SHUP

;

ATS0

;

ATS6

;

ATS7

;

ATS8

;

ATS10

;

Page 538 of 567

23.3 Available AT Commands and Dependency on SIM PIN

AT Command

Exec

Test

Read

Write

ATO

;

+++

;

AT+CBST

;

AT+CRLP

;

AT+CLCC

;

AT^SLCC

AT+CR

;

AT+CRC

;

AT+CSNS

;

AT^SCNI

;

AT^SLCD

;

AT^STCD

;

ATP

;

ATT

;

Network Service Commands

AT+COPN

;

AT+COPS

;

AT^SOPS

;

AT+CREG

;

AT+CSQ

;

AT^SMONC

;

AT^SMOND

;

AT^SFNUR

;

AT^MONI

;

AT^MONP

;

AT^SMONG

;

AT^SALS

;

AT^SHOM

;

AT^SPLM

AT+CPOL

;

AT^SPLR

;

AT^SPLW

;

Supplementary Service Commands

AT+CACM

;

AT^SACM

;

AT+CAMM

;

AT+CAOC

AT+CCUG

;

AT+CCFC

;

AT+CCWA

;

Page 539 of 567

23.3 Available AT Commands and Dependency on SIM PIN

AT Command

Exec

Test

Read

Write

AT+CHLD

;

AT+CLIP

;

AT+CLIR

;

AT+COLP

;

AT+CPUC

;

AT+CSSN

;

AT+CUSD

;

Internet Service Commands

AT^SICS

;

AT^SICI

;

AT^SISS

;

AT^SISI

;

AT^SISO

;

AT^SISC

;

AT^SISR

;

AT^SISW

;

AT^SICO

;

AT^SICC

;

AT^SISX

;

AT^SISE

;

GPRS Commands

AT+CGACT

;

AT+CGANS

;

AT+CGATT

;

AT+CGAUTO

;

AT+CGDATA

;

AT+CGDCONT

;

AT+CGEQMIN

;

AT+CGEQREQ

;

AT+CGPADDR

;

AT+CGQMIN

;

AT+CGQREQ

;

AT+CGREG

;

AT+CGSMS

;

AT^SGACT

;

AT^SGAUTH

;

AT^SGCONF

;

ATA

;

ATD*99#

;

ATD*98#

;

Page 540 of 567

23.3 Available AT Commands and Dependency on SIM PIN

AT Command

Exec

Test

Read

Write

ATH

;

ATS0

;

FAX Commands

AT+FCLASS

;

AT+FRH

;

AT+FRM

;

AT+FRS

;

AT+FTH

;

AT+FTM

;

AT+FTS

;

Short Message Service (SMS) Commands

AT+CMGC

;

AT+CMGD

;

AT+CMGF

;

AT+CMGL

;

AT+CMGR

;

AT+CMGS

;

AT+CMGW

;

AT+CMSS

;

AT+CNMA

;

AT+CNMI

;

AT+CPMS

;

AT+CSCA

;

AT+CSCB

;

AT+CSDH

;

AT+CSMP

;

AT+CSMS

;

AT^SCML

;

AT^SCMR

;

AT^SCMS

;

AT^SCMW

;

AT^SLMS

;

AT^SMGL

;

AT^SMGO

;

AT^SMGR

;

AT^SSCONF

;

AT^SSDA

;

AT^SSMSS

;

SIM related Commands

AT+CRSM

;

Page 541 of 567

23.3 Available AT Commands and Dependency on SIM PIN

AT Command

Exec

Test

Read

Write

AT^SXSM

;

AT^SCKS

;

AT^SSET

;

AT^SCID

;

AT+CXXCID

;

Remote SIM Access (RSA) Commands

AT^SRSA

;

AT^SRSM

;

SIM Application Toolkit (SAT) Commands

AT^SSTA

;

^SSTN

;

AT^SSTGI

;

AT^SSTR

;

Phonebook Commands

AT+CNUM

;

AT+CPBR

;

AT+CPBS

;

AT+CPBW

;

AT^SDLD

;

AT^SPBC

;

AT^SPBD

;

AT^SPBG

;

AT^SPBS

;

Audio Commands

ATL

;

ATM

;

AT+CLVL

;

AT+CMUT

;

AT+VTD

;

AT+VTS

;

AT^SAIC

;

AT^SNFA

;

AT^SNFD

;

AT^SNFI

;

AT^SNFM

;

AT^SNFO

;

AT^SNFPT

;

AT^SNFS

;

AT^SNFTTY

;

Page 542 of 567

23.3 Available AT Commands and Dependency on SIM PIN

AT Command

Exec

Test

Read

Write

AT^SNFV

;

AT^SNFW

;

AT^SRTC

Hardware related Commands

AT+CCLK

;

AT+CALA

;

AT^SBC

;

AT^SBV

;

AT^SCTM

;

AT^SSYNC

;

AT^SSPI

;

AT^SAADC

;

AT^SRADC

;

AT^SWDAC

;

GPIO Commands

AT^SPIO

;

AT^SCPIN

;

AT^SCPOL

;

AT^SCPORT

;

AT^SDPORT

;

AT^SGIO

;

AT^SSIO

;

AT^SCCNT

;

AT^SSCNT

;

Java related Commands

AT^SJRA

;

AT^SJNET

;

AT^SJOTAP

AT^SJSEC

;

Miscellaneous Commands

;

ATS3

;

ATS4

;

ATS5

;

AT^SFDL

;

Page 543 of 567

23.4 Availability of AT Commands Depending on Operating Mode of ME

23.4

Availability of AT Commands Depending on Operating Mode of ME

! ... Command not supported

% ... Command supported

§ ... Use in Airplane and Charge-only mode depends on command type (test, read, execute, write).

See description of AT command for details.

Table 23.6: Availability of AT Commands Depending on Operating Mode of ME

AT Command

Normal Mode

Charge

Configuration Commands

AT&F

AT&V

AT&W

ATQ

ATV

ATX

AT\V

ATZ

AT+CFUN

AT^SMSO

AT+GCAP

AT+CMEE

AT+CSCS

AT^SCFG

AT^SM20

Status Control Commands

AT+CMER

AT+CIND

AT^SIND

AT+CEER

ATS18

AT+CPAS

AT+WS46

Serial Interface Control Commands

AT\Q

AT&C

AT&D

AT&S

ATE

AT+ICF

AT+IFC

Page 544 of 567

23.4 Availability of AT Commands Depending on Operating Mode of ME

AT Command

Normal Mode

Charge

AT+ILRR

AT+IPR

AT+CMUX

AT^STPB

Security Commands

AT+CPIN

AT+CPIN2

AT^SPIC

AT+CLCK

AT^SLCK

AT+CPWD

AT^SPWD

AT^SCSL

Identification Commands

ATI

AT+CGMI

AT+GMI

AT+CGMM

AT+GMM

AT+CGMR

AT+GMR

AT+CGSN

AT+GSN

AT+CIMI

Call related Commands

ATA

ATD

ATD><mem><n>

ATD><n>

ATD><str>

ATDI

ATDL

ATH

AT+CHUP

AT^SHUP

ATS0

ATS6

ATS7

ATS8

Page 545 of 567

23.4 Availability of AT Commands Depending on Operating Mode of ME

AT Command

Normal Mode

Charge

ATS10

ATO

+++

AT+CBST

AT+CRLP

AT+CLCC

AT^SLCC

AT+CR

AT+CRC

AT+CSNS

AT^SCNI

AT^SLCD

AT^STCD

ATP

ATT

Network Service Commands

AT+COPN

AT+COPS

AT^SOPS

AT+CREG

AT+CSQ

AT^SMONC

AT^SMOND

AT^SFNUR

AT^MONI

AT^MONP

AT^SMONG

AT^SALS

AT^SHOM

AT^SPLM

AT+CPOL

AT^SPLR

AT^SPLW

Supplementary Service Commands

AT+CACM

AT^SACM

AT+CAMM

AT+CAOC

AT+CCUG

AT+CCFC

Page 546 of 567

23.4 Availability of AT Commands Depending on Operating Mode of ME

AT Command

Normal Mode

Charge

AT+CCWA

AT+CHLD

AT+CLIP

AT+CLIR

AT+COLP

AT+CPUC

AT+CSSN

AT+CUSD

Internet Service Commands

AT^SICS

AT^SICI

AT^SISS

AT^SISI

AT^SISO

AT^SISC

AT^SISR

AT^SISW

AT^SICO

AT^SICC

AT^SISX

AT^SISE

GPRS Commands

AT+CGACT

AT+CGANS

AT+CGATT

AT+CGAUTO

AT+CGDATA

AT+CGDCONT

AT+CGEQMIN

AT+CGEQREQ

AT+CGPADDR

AT+CGQMIN

AT+CGQREQ

AT+CGREG

AT+CGSMS

AT^SGACT

AT^SGAUTH

AT^SGCONF

ATA

ATD*99#

Page 547 of 567

23.4 Availability of AT Commands Depending on Operating Mode of ME

AT Command

Normal Mode

Charge

ATD*98#

ATH

ATS0

FAX Commands

AT+FCLASS

AT+FRH

AT+FRM

AT+FRS

AT+FTH

AT+FTM

AT+FTS

Short Message Service (SMS) Commands

AT+CMGC

AT+CMGD

AT+CMGF

AT+CMGL

AT+CMGR

AT+CMGS

AT+CMGW

AT+CMSS

AT+CNMA

AT+CNMI

AT+CPMS

AT+CSCA

AT+CSCB

AT+CSDH

AT+CSMP

AT+CSMS

AT^SCML

AT^SCMR

AT^SCMS

AT^SCMW

AT^SLMS

AT^SMGL

AT^SMGO

AT^SMGR

AT^SSCONF

AT^SSDA

AT^SSMSS

Page 548 of 567

23.4 Availability of AT Commands Depending on Operating Mode of ME

AT Command

Normal Mode

Charge

SIM related Commands

AT+CRSM

AT^SXSM

AT^SCKS

AT^SSET

AT^SCID

AT+CXXCID

Remote SIM Access (RSA) Commands

AT^SRSA

AT^SRSM

SIM Application Toolkit (SAT) Commands

AT^SSTA

^SSTN

AT^SSTGI

AT^SSTR

Phonebook Commands

AT+CNUM

AT+CPBR

AT+CPBS

AT+CPBW

AT^SDLD

AT^SPBC

AT^SPBD

AT^SPBG

AT^SPBS

Audio Commands

ATL

ATM

AT+CLVL

AT+CMUT

AT+VTD

AT+VTS

AT^SAIC

AT^SNFA

AT^SNFD

AT^SNFI

AT^SNFM

AT^SNFO

Page 549 of 567

23.4 Availability of AT Commands Depending on Operating Mode of ME

AT Command

Normal Mode

Charge

AT^SNFPT

AT^SNFS

AT^SNFTTY

AT^SNFV

AT^SNFW

AT^SRTC

Hardware related Commands

AT+CCLK

AT+CALA

AT^SBC

AT^SBV

AT^SCTM

AT^SSYNC

AT^SSPI

AT^SAADC

AT^SRADC

AT^SWDAC

GPIO Commands

AT^SPIO

AT^SCPIN

AT^SCPOL

AT^SCPORT

AT^SDPORT

AT^SGIO

AT^SSIO

AT^SCCNT

AT^SSCNT

Java related Commands

AT^SJRA

AT^SJNET

AT^SJOTAP

AT^SJSEC

Miscellaneous Commands

ATS3

ATS4

ATS5

AT^SFDL

Page 550 of 567

23.5 AT Command Settings storable with AT&W

23.5

AT Command Settings storable with AT&W

Table 23.7: Settings Stored to User Profile on ASC0 / MUX Channel 1

AT Command

Stored Parameters

Configuration Commands

ATQ

<n>

ATV

<value>

ATX

<value>

AT\V

<value>

AT+CMEE

Status Control Commands

ATS18

<n>

Serial Interface Control Commands

AT\Q

<n>

AT&C

<value>

AT&D

<value>

AT&S

<value>

ATE

<value>

AT+ICF

AT+IFC

AT+ILRR

<value>

AT^STPB

<n>

Call related Commands

ATS0

<n>

ATS6

<n>

ATS7

<n>

ATS8

<n>

ATS10

<n>

AT+CBST

AT+CRLP

AT^SLCC

<n>

AT+CR

<mode>

AT+CRC

<mode>

Network Service Commands

AT+COPS

AT+CREG

<n>

Supplementary Service Commands

AT^SACM

<n>

Page 551 of 567

23.5 AT Command Settings storable with AT&W

AT Command

Stored Parameters

AT+CLIP

<n>

GPRS Commands

ATS0

<n>

FAX Commands

AT+FCLASS

<n>

Short Message Service (SMS) Commands

AT+CMGF

<mode>

AT+CNMI

AT+CSDH

<show>

AT+CSMS

AT^SMGO

<n>

SIM related Commands

AT^SCKS

<mode>

AT^SSET

<n>

Miscellaneous Commands

ATS3

<n>

ATS4

<n>

ATS5

<n>

Table 23.8: Settings Stored to User Profile on ASC1 / MUX Channels 2 and 3

AT Command

Stored Parameters

Configuration Commands

ATQ

<n>

ATV

<value>

ATX

<value>

AT+CMEE

Serial Interface Control Commands

AT\Q

<n>

AT&C

<value>

AT&D

<value>

AT&S

<value>

ATE

<value>

AT+ICF

AT+IFC

AT^STPB

<n>

Page 552 of 567

23.6 Factory Default Settings Restorable with AT&F

23.6

Factory Default Settings Restorable with AT&F

Table 23.9: Factory Default Settings Restorable with AT&F

AT Command

Factory Defaults

Configuration Commands

ATQ

<n>=0

ATV

<value>=1

ATX

<value>=4

AT\V

<value>=1

AT+CFUN

<fun>=1

AT+CMEE

<errMode>=0

AT+CSCS

<chset>="GSM"

AT^SM20

<CallMode>=1, <CmgwMode>=1

AT^SCFG

<tcpIrt>="3", <tcpMr>="10", <tcpOt>="6000", <tcpWith-

Urc>="on"

Status Control Commands

AT+CMER

<mode>=0, <keyp>=0, <disp>=0, <ind>=0, <bfr>=0

AT+CIND

<mode>=1

ATS18

<n>=0

Serial Interface Control Commands

AT\Q

<n>=0

AT&C

<value>=1

AT&D

<value>=2

AT&S

<value>=0

ATE

<value>=1

AT+IFC

<TEflowcontrol>=0, <TAflowcontrol>=0

AT+ILRR

<value>=0

AT^STPB

<n>=0

Call related Commands

ATS0

<n>=000

ATS6

<n>=000

ATS7

<n>=060

ATS8

<n>=0

ATS10

<n>=002

AT+CBST

<speed>=7, <name>=0, <ce>=1

AT+CRLP

<iws>=61, <mws>=61, <T1>=78, <N2>=6

AT^SLCC

<n>=0

AT+CR

<mode>=0

AT+CRC

<mode>=0

Page 554 of 567

23.6 Factory Default Settings Restorable with AT&F

AT Command

Factory Defaults

Network Service Commands

AT+COPS

<format>=0

AT+CREG

<n>=0

AT^SALS

<view>=0, <line>=1

Supplementary Service Commands

AT^SACM

<n>=0

AT+CLIP

<n>=0

AT+CSSN

<n>=0, <m>=0

AT+CUSD

<n>=0

GPRS Commands

AT+CGAUTO

<n>=3

AT+CGREG

<n>=0

AT+CGSMS

<service>=3

AT^SGAUTH

<auth>=3

ATS0

<n>=000

FAX Commands

AT+FCLASS

<n>=0

Short Message Service (SMS) Commands

AT+CMGF

<mode>=0

AT+CNMI

<mode>=0, <mt>=0, <bm>=0, <ds>=0, <bfr>=1

AT+CSCB

<mode>=0

AT+CSDH

<show>=0

AT+CSMP

<fo>=17, <vp>=167, <dcs>=0, <pid>=0

AT+CSMS

<service>=0

AT^SMGO

<n>=0

AT^SSCONF

<ra>=0

AT^SSDA

<da>=0

AT^SSMSS

<seq>=0

SIM related Commands

AT^SCKS

<mode>=0

AT^SSET

<n>=0

Phonebook Commands

AT+CPBS

<storage>="SM"

AT^SPBS

<internal-counter>=0

Audio Commands

AT+VTD

<duration>=1

Page 555 of 567

23.7 Summary of Unsolicited Result Codes (URC)

23.7

Summary of Unsolicited Result Codes (URC)

Table 23.10: Summary of Unsolicited Result Codes (URC)

AT Command

URC

Configuration Commands

AT+CFUN

^SYSSTART

AT+CFUN

^SYSSTART CHARGE ONLY MODE

AT^SMSO

^SHUTDOWN

AT^SCFG

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

AT^SCFG

^SYSSTART AIRPLANE MODE

Status Control Commands

AT+CMER

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

AT^SIND

+CIEV: <indDescr>, <indValue>

AT^SIND

+CIEV: <indDescr>, <adnEntry>, <adnNumber>, <adnType>, <adnText>

+CIEV: <indDescr>, "READY"

AT^SIND

+CIEV: <indDescr>, <indValue>, <vmCounter>

AT^SIND

+CIEV: <indDescr>, <indValue>, <eonsOperator>, <servProvider>

AT^SIND

+CIEV: <indDescr>, <nitzUT>, <nitzTZ>, <nitzDST>

Call related Commands

AT^SLCC

if the list of current calls is empty:

^SLCC:

if one or more calls are currently in the list:

^SLCC: <idx>, <dir>, <stat>, <mode>, <mpty>, <traffic channel

assigned>[, <number>, <type>[, <alpha>]]

[^SLCC: <idx>, <dir>, <stat>, <mode>, <mpty>, <traffic channel

assigned>[, <number>, <type>[, <alpha>]]]

[... ]

^SLCC:

AT+CRC

RING

AT+CRC

+CRING: <type>

Network Service Commands

AT+CREG

+CREG: <stat>

AT+CREG

+CREG: <stat>[, <lac>, <ci>]

AT^SALS

^SALS: <line>

Supplementary Service Commands

AT^SACM

+CCCM: <ccm>

AT+CCWA

+CCWA: <calling number>, <type of number>, <class>, , <CLI validity>

AT+CCWA

^SCWA

AT+CLIP

+CLIP: <number>, <type>, , [, <alpha>][, <CLI validity>]

AT+COLP

+COLP: <number>, <type>

AT+CSSN

+CSSI: <code 1>

Page 557 of 567

23.7 Summary of Unsolicited Result Codes (URC)

AT Command

URC

AT+CSSN

+CSSU: <code 2>

AT+CUSD

+CUSD: <m>[<str_urc>[<dcs>]]

Internet Service Commands

AT^SISR

^SISR: <srvProfileId>, <urcCauseId>

AT^SISW

^SISW: <srvProfileId>, <urcCauseId>

Internet Ser-

^SIS: <srvProfileId>, <urcCause>[, [<urcInfoId>][, <urcInfoText>]]

vice URC "^SIS"

GPRS Commands

AT+CGREG

+CGREG: <stat>

AT+CGREG

+CGREG: <stat>, <lac>, <ci>

Short Message Service (SMS) Commands

AT+CNMI

+CMTI: <mem3>, <index>

AT+CNMI

+CMT: <length><CR><LF><pdu>

AT+CNMI

+CMT: <oa>, <scts>[, <tooa>, <fo>, <pid>, <dcs>, <sca>, <tosca>,

AT+CNMI

+CBM: <length><CR><LF><pdu>

AT+CNMI

+CBM: <sn>, <mid>, <dcs>, <page>, <pages><CR><LF><data>

AT+CNMI

+CDS: <length><CR><LF><pdu>

AT+CNMI

+CDS: <fo>, <mr>[, <ra>][, <tora>], <scts>, <dt>, <st>

AT+CNMI

+CDSI: <mem3>, <index>

AT^SMGO

^SMGO: <mode>

SIM related Commands

AT^SCKS

^SCKS: <SimStatus>

AT^SSET

^SSIM READY

Remote SIM Access (RSA) Commands

AT^SRSA

^SRSA: <devId>, <sapRole>, <connState>

AT^SRSM

^SRSM: <RsaDevId>, <RsaMsgId>[, <RsaMsgData>[, <RsaMsgLen>[, <RsaMs-

gRc>]]]

SIM Application Toolkit (SAT) Commands

^SSTN

^SSTN: <cmdType>

^SSTN

^SSTN: <cmdTerminateValue>

^SSTN

^SSTN: 254

^SSTN

^SSTN: 255

Hardware related Commands

AT+CALA

+CALA: [<text>]

AT^SBC

^SBC: Undervoltage

AT^SBC

^SBC: Overvoltage warning

AT^SBC

^SBC: Overvoltage shutdown

Page 558 of 567

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