tmc-210 pei-ext - tetramodem · 2021. 2. 4. · funk-electronic piciorgros gmbh tmc-210 / tam-200...

TMC-210

TAM-200

TETRA Modem Core

V1.22, July 2021

Funk-Electronic Piciorgros GmbH

Claudiastrasse 5

51149 Cologne

Germany

Funk-Electronic Piciorgros GmbH TMC-210 / TAM-200

V1.22 - of 49

Content

1 INTRODUCTION ............................................................................................................... 4

1.1 Overview ....................................................................................................................... 4

1.2 Safety Precautions ......................................................................................................... 4

1.3 Disclaimer ..................................................................................................................... 4

1.4 Document Versions ....................................................................................................... 5

1.5 Functions and Features .................................................................................................. 6

1.6 TMC-210 versions ......................................................................................................... 6

1.7 Usage restrictions .......................................................................................................... 7

2 HARDWARE INFORMATION ........................................................................................ 9

2.1 Mechanical Details ........................................................................................................ 9

2.2 Power supply ................................................................................................................. 9

2.3 Main connector and layout considerations .................................................................. 10

2.4 Main connector - Connection table ............................................................................ 12

2.5 Antenna connections ................................................................................................... 13

2.6 LED Functions ............................................................................................................ 13

3 INTERFACES ................................................................................................................... 14

3.1 PEI interface (UART 1) .............................................................................................. 14

3.2 PPP interface (UART 3) .............................................................................................. 14

3.3 Service interface (UART 2) ........................................................................................ 14

3.4 User modes .................................................................................................................. 15

4 TMC-210 EVALUATION BOARD ................................................................................. 16

5 SPECIFICATIONS TMC-210 ......................................................................................... 17

6 TAM-200 MODEM ........................................................................................................... 19

6.1 Overview ..................................................................................................................... 19

6.2 LED Functions ............................................................................................................ 19

6.3 6 Pin connector assignment ......................................................................................... 20

6.3.1 Connection diagram to a PC ................................................................................ 21

6.4 Mechanical Drawing ................................................................................................... 22

6.5 Specifications TAM-200 ............................................................................................. 23

7 CONFIGURATION EXAMPLES ................................................................................... 24

7.1 Basic TETRA configuration ........................................................................................ 25

7.2 Sending and receiving an SDS message ..................................................................... 27

7.3 Packet data connections .............................................................................................. 29

8 UPDATING THE TMC-210 / TAM-200 ......................................................................... 36

8.1 Preparations ................................................................................................................. 36

8.2 Software versions and TEA version ............................................................................ 39

8.3 Updating the firmware ................................................................................................ 40

8.3.1 Initiate the update sequence ................................................................................ 40

8.3.2 Deletion of the Flash areas .................................................................................. 41

8.3.3 Programming the new software versions ............................................................ 45

8.3.4 Finishing the software update ............................................................................. 48

9 APPENDIX – PEI COMMANDS AND EKIT DRAWINGS ........................................ 49


V1.22 - of 49


V1.22 - of 49

1 Introduction

1.1 Overview

This document contains information about installation, settings and operation of the

TMC-210 TETRA Modem Core and the TAM-200 TETRA modem. Additional

information is also available on the Internet, at the website www.TetraModem.com.

1.2 Safety Precautions

This equipment transmits radio waves in the frequency range 380 to 470 MHz or -800

MHz. Under certain circumstances, these radio waves could be harmful to any living

being or electronic equipment near it. Care should be taken to ensure that the radio and

antenna systems are installed and commissioned only by trained personnel.

This radio equipment should not be used in life-support systems or in safety systems

without our prior written permission.

1.3 Disclaimer

We have carefully checked the contents of this document, and the hardware and

software described in it, for compatibility. However, we cannot exclude possibilities of

deviations and cannot guarantee complete conformity of the document with the


V1.22 - of 49

equipment it describes. If any corrections or improvements are to be made, they will be

taken into consideration in the next version of this document.

Important instructions are marked by the expressions "Important", "Note" or

“Caution!”. These should be carefully observed. Explanations regarding these

precautions can be found in the website www.TetraModem.com, in the login area.

1.4 Document Versions

The software (firmware) versions and document editions history is listed below:

Firmware

Version

Document

Version

Comments / Changes

Stack: 4.51

DSP: 4.53

1.20 Documentation Update for TMC-210

Stack: 4.54

DSP: 4.56

1.21 Added connection example between TAM-200 and PC

1.22 Changed type of the 50 pin connector in 2.3 due to obsolescence /

replacement of the original part.


V1.22 - of 49

1.5 Functions and Features

The TMC-210 is a TETRA Core device for PCB-mounting that can be used for Data

and Voice applications in TETRA infrastructures. Its small size (of approx. 87 x 56 x 10

mm, aluminum enclosure) and the interface design allow an easy and time saving

integration and provide a platform to adopt almost any application for Voice, Serial

Data and IP Communication - and the six multi-function LED’s provide Power Supply,

Network and Interface Information during operation.

A wide range of powerful AT-Commands are used to control the device. And with the

embedded user application interface (optional) the unit can be customized for example

to control external events via its serial ports, to perform data compression or to act as a

responder for SDS or status messages reporting events or just the RF-Field strength,

neighborhood cells or the complete TETRA SysInfo Message.

Two serial ports are available in the basic setup: the AT-Command Port and the

PPP/ACELP Port. That makes it possible to still use all AT-Commands on the first port

during IP-Data Communication or while receiving or sending an ACELP (TETRA

digital voice) data stream on the second port.

For voice applications a microphone and speaker can directly be connected to the TMC-

210. The AF output power is about 150 mW at 8 Ohm and can directly drive a speaker

or an external Power Amplifier.

The TMC-210 is available for 370 – 470 MHz and for the 800 MHz frequency band and

provides different TETRA options (not all included in the basic setup) as AIE, AUTH,

SDS, PD, MSPD, and when connecting an external card reader also E2EE.

1.6 TMC-210 versions

The standard version of the TMC-210 has no built-in GPS module, and 4 pins of the

main connector are used to make the signals of the 3 LED’s “OK”, “PPP” and “RF”

available to the customer application.

The version TMC-210/E2EE (future option / available on request) includes the ability

for End-to-End encryption, on this type the 4 pins which are providing the LED

functions on the connector are used for the SIM-card connections instead. The E2EE

version is available on request.

In general there are two frequency types of the TMC-210: One for the frequency range

370-470 MHz, and one for the 800 MHz band. The frequency version must be provided

with the order.


V1.22 - of 49

1.7 Usage restrictions

In DMO mode the TMC-210 TETRA radio can transmit without being controlled by a

licensed trunked mode radio network.

Therefore it must be ensured by the controlling application that the TMC-210 is not

configured to frequencies which are not allowed or licensed to the user in the country

where the TMC-210 is operated. In any case the authorities should be contacted

regarding approved frequency use before operating the radio in DMO mode.

In the EU, restrictions are valid for the following countries:

United Kingdom (UK), Greece (EL), Ireland (IE), Belgium (BE), Croatia (HR),

Portugal (PT), Luxemburg (LU), Bulgaria (BG), Latvia (LV), Denmark (DK), Poland

(PL), Slovakia (SK), Finland (FI) and Sweden (SE).

Country Frequency Range(MHz) Max. transmit power

(W)

Germany (DE) no no

France (FR) no no

United Kingdom (UK

) 380- 385,390-395 3

Italy(IT) no no

Greece(EL) 380- 385,390-395,410-430,450-470 3

Spain(ES) no no

Ireland (IE) 335.4- 387,390-399.9 3

Belgium (BE) 415-419,425-429 3

Croatia (HR) 380-399.9 3

Cyprus (CY) no no

Portugal (PT) 410-430,440-455 3

Malta(MT) no no

Luxembourg (LU)

410-430, 450-470 3

Bulgaria (BG)

380-385,390-395 3

Latvia (LV) 387-399.9 3

Slovenia(SI) no no

Czech Republic (CZ)

no no

Denmark (DK)

380-385,390-395,452.5-457.5,462.5-467.5 3

Estonia(EE) 380-389.9,390-399.9 3

Lithuania (LT)

no no

Hungary (HU)

no no

Netherlands (NL)

no no

Austria(AT) no no

Poland(PL) 380-382.5,390-392.5 3

Romania (RO)

no no

Slovakia (SK)

410-430 3

Finland(FI) 385.0125-389.9875,395.0125- 399.8875,414.0125-416.3375,

417.925-419.125,424.0125-426.3375,427.925-429.125 3

Sweden (SE)

380-385,390-395,410-430 3


V1.22 - of 49

TETRA parameters

Operation Frequency Range 370 – 430 MHz

450 – 470 MHz

806 – 869 MHz

Rated Output Power 3 Watts (34.77 dBm) for 370 – 470 MHz range

1.8 Watt (32.55 dBm) for 806 – 869 MHz range

Modulation Type π/4 DQPSK

Channel Separation 25 kHz

Operating Mode V+D & DMO


V1.22 - of 49

2 Hardware Information

2.1 Mechanical Details

The TMC-210 is packed into a tiny aluminum enclosure. The connection to the

application PCB is done by a 50 pin Hirose DF-12-series connector. The part number of

the connector for the user application PCB is: DF12(5.0)-50DP-0.5V(86)

The connector provides all signals and the power supply to the TMC-210 except the

antenna connections, which are available via a MMCX connectors.

The total size of the TMC-210 is 87mm x 56mm x 10mm (excluding mounting straps).

2.2 Power supply

The TMC-210 needs two power supplies: A 9.0V rail (+/-0.2V) which should be able to

deliver short peak currents of up to 3A, and a 5V logic power rail (must be able to serve

up to 0.5A). A 1000µF capacitor should be placed close to the connector on the

application PCB, connected to the 9.0V rail, to ensure that sufficient energy for the fast

transmitter keying is available.

An application note for a simple power supply with a possible input voltage of 12-24V

can be provided on request.


V1.22 - of 49

2.3 Main connector and layout considerations

The main connector is a 50 pin Hirose type DF-12, the connector for the customer

application PCB has the Hirose part number DF12NC(5.0)-50DP-0.5V(51).

The TMC-210 is fixed on the application board by 3 mounting straps. For easy fixing,

the insert nut "Multisert 0006M2,5" is recommended (Manufacturer: KVT Fastening,

www.kvt-fastening.de). For these insert nuts, the diameter of the mounting holes in the

application PCB should be 4.1mm.

The drawing below shows the positions of the mounting holes against the middle point

of the DF12 connector along with the pinout of the connector.


V1.22 - of 49


V1.22 - of 49

2.4 Main connector - Connection table

Pin Name Remark

1-8 VCC_PA 9.0V DC power supply, 3A, +/- 0.2V

All pins must be connected!

A 1000µF capacitor must block these pins to ground close to the connector.

10,18, 25-29, 35,39, 45,46

GND Ground. All pins must be connected

32 UART 1 Rx Data receive (input), UART 1 (PEI)

31 UART 1 Tx Data transmit (output), UART 1 (PEI)

42 UART 1 RTS Handshake output, UART 1 (PEI)

33 UART 1 CTS Handshake input, UART 1 (PEI)

21 UART 3 Rx Data receive (input), UART 3 (PPP/ACELP)

24 UART 3 Tx Data transmit (output), UART 3 (PPP/ACELP)

22 UART 3 RTS Handshake output, UART 3 (PPP/ACELP)

23 UART 3 CTS Handshake input, UART 3 (PPP/ACELP)

13 UART 2 Rx Data receive (input), UART 2 (Service port)

12 UART 2 Tx Data transmit (output), UART 2 (Service port)

43 Microphone + Microphone, positive line

40 Microphone - Microphone, negative line

47 Speaker + Speaker, positive line (8 Ohm, max. 120mW)

48 Speaker - Speaker, negative line (8 Ohm, max. 120mW)

49,50 VCC_5V 5V logic power supply, 0.5A

41 NC currently not used

11 3V3D 3.3V output, max. 100mA Active when module is switched on.

30 ON_OFF Activation input, tie to ground

38 PTT input Push-to-talk for standalone voice operation Tied to ground: PTT active

34 ALARM Alarm call PTT for standalone voice operation Tied to ground: Alarm call PTT active

9 PPP LED Connection for external PPP-LED

Optional: SIM-SUPPLY for E2EE version

36 RF LED gn Connection for the green part of the RF-LED

Optional: SIM-DATA for E2EE version

37 RF LED rd Connection for the red part of the RF-LED

Optional: SIM-CLK for E2EE version


V1.22 - of 49

Pin Name Remark

44 OK LED Connection for the OK-LED

Optional: SIM-RST for E2EE version

14 RESET Reset input

Tie to ground to perform reset

15-17, 19,20

Test pins Pins for internal testing.

Must be left unconnected

Note: All logical lines and UART interfaces are operating at a 3.3V level. Do not

provide voltages higher than 3.3V on any of these lines!

Note: If RTS/CTS is not connected to the application on UART1 or UART3, these

pins must be connected together on the target PCB (RTS to CTS)!

2.5 Antenna connections

The connection to the antenna is provided by MMCX connectors. There is at least one

connector for the TETRA antenna at the TMC-210.

Both connectors are of the same type, the function of the antenna connector is printed

on the label close to it.

2.6 LED Functions

6 LED’s are giving the most important status information to the user. The functions of

these LED are listed below.

LED Color Function

PWR Green On: Power supply is provided to the module

OK Green Once the OK-LED is lit, the TMC-210 has booted up and is ready for use

RF Green / Yellow / Red RF condition of the TETRA network.

Off: Not registered to a TETRA network

Red flashing: TMC-210 is scanning for a network

Red: Registered, but the field strength is bad. Communication drops may be expected.

Yellow: Registered with a fair fieldstregth

Green: Registered with a good fieldstrength

PPP Blue On: Indicates that a Packet Data connection is active

TxD Red Transmission indicator for the serial PEI interface

RxD Green Reception indicator for the serial PEI interface


V1.22 - of 49

3 Interfaces

3.1 PEI interface (UART 1)

The UART 1 is the main interface where all the AT commands are running on. The

interface operates at a speed of 38400 bps which 8 data bits, no parity and 1 stop bit.

Hardware handshake via RTS/CTS line is active.

In the normal mode the UART1 provides the standardized TETRA commands and any

PPP connections are done also on the same UART. In this mode, during an active PPP

connection, no further commands can be given (like checking the field strength, send

and receive SDS etc.).

3.2 PPP interface (UART 3)

The UART3 is an extended interface for running the Packet Data connection in

extended mode. This interface also operates at a speed of 38400 bps which 8 data bits,

no parity and 1 stop bit. Hardware handshake via RTS/CTS line is active.

As soon as the extended mode is activated, the PPP connection is using UART3. In this

mode, the UART1 PEI interface can be used also during an active packet data

connection which gives the user the ability to continue using any commands and to send

and receive status and SDS messages.

3.3 Service interface (UART 2)

This interface is used for updating the firmware of the TMC-210 and for service

purposes. It is highly recommended to integrate this interface in the customer designs in

a way that the serial interface can be accessed by a computer (i.e. using a service

connector).


V1.22 - of 49

3.4 User modes

The TMC-210 supports two user modes:

The normal mode makes only the standardized TETRA AT commands available on

UART 1. UART 3 is not used in this mode, a PPP connection is using the PEI interface

which makes it useless for AT commands during an active packet data session.

Also no special commands for setting the TETRA network parameters are supported in

this mode (for the setup of the TETRA parameters the extended mode must be active at

least temporary).

The extended mode is the recommended operating mode, making a lot of special

commands available (like setting the TETRA parameters, use the TMC-210 as a voice

gateway to an application etc.).

In this mode the packet data connection is routed to UART3, allowing the parallel use

of the PPP connection and the PEI commands.

The extended mode is activated by the command “AT+PIMODE=1” and will stay

active until the next modem restart.

A detailed command documentation for the standard mode and the enhanced mode is

attached in the appendix of this document.


V1.22 - of 49

4 TMC-210 Evaluation Board

The TMC-210 Evaluation Board (EKit) provides a fast and easy way to make the first

steps in software development for the TMC-210.

The Board comes with a wall-plug power supply and generates the needed voltages for

the TMC-210. It has also all 3 UARTS ready for plug into a computer on DB9

connectors.

The schematics of the TMC-210 EKit is provided as an appendix to this document. You

can also use this as a reference for the power supply design.


V1.22 - of 49

5 Specifications TMC-210

Functions: TETRA AT-modem for serial and IP communication

Alarm device for SDS and status messages

TETRA voice terminal

Available frequency

ranges:

370 MHz - 470 MHz

806 MHz - 869 MHz

Serial Interfaces UART 1: AT command port

UART 3: Packet data port (in enhanced mode)

UART 2: Service and update port

Indications: 6 LED providing information about operating status and RSSI

field strength

TETRA features: SDS, Status, SCCH, Packet Data, Multi Slot Packet Data,

SDS size up to 2047 bit, Air Interface Encryption (Class 2/3),

Authentication, Voice Interface

Transmission Power: Up to 3 Watts (Class 3)

Static Receiver sensitivity: Min. -112dBm (Typ. -115 dBm)

Dynamic Receiver

sensitivity:

Min. -103 dBm (Typ: -107 dBm)

RF Conformance EN 300 394-1

EMC Conformance EN 301 489-1 and -18

ESD Conformance 61000-4-2

Special options: Embedded GPS-Receiver

End-to-End-Encryption

Stand-alone voice mode

User applications

Power supply voltage: 9.0V DC (800MHz type), max. 3A and 5 V DC (max. 500mA)

All voltages +/- 0.2V

Current in receive mode: ~ 300mA

Current in transmit mode: ~ 800mA in average at 1-slot operation

Peaks may go up to 3 A on the 9.0V supply rail

Operating Temperature: -20 °C to +65 °C

Enclosure: Anodized aluminum

Dimensions: 87mm x 56mm x 10mm (excluding antenna connectors and

mechanical installation straps)


V1.22 - of 49

TAM-200

TETRA AT modem


Claudiastrasse 5

51149 Cologne

Germany


V1.22 - of 49

6 TAM-200 Modem

6.1 Overview

The TAM-200 packs the TMC-210 into a metal enclosure with a wide range power

supply for 12-24 V DC operation and V.24 level drivers for the UARTs, allowing the

direct connection to any equipment using RS-232 interfaces.

The status LED of the TMC-210 are also available on the TAM-200, giving the user the

needed status information.

The use of the interfaces and the commands are identical with the TMC-210.

6.2 LED Functions

6 LED’s are giving the most important status information to the user. The functions of

these LED are listed below.

LED Color Function

PWR Green On: Power supply is provided to the module

OK Green Once the OK-LED is lit, the TMC-210 has booted up and is ready for use

RF Green / Yellow / Red RF condition of the TETRA network.

Off: Not registered to a TETRA network

Red flashing: The TMC-210 is scanning for the configured TETRA network

Red: Registered, but the field strength is bad. Communication drops may be expected.

Yellow: Registered with a fair fieldstregth

Green: Registered with a good fieldstrength

PPP Blue Flashing: PPP connection is about to be established

On: Indicates that a Packet Data connection is active

TxD Red Transmission indicator for the serial PEI interface

RxD Green Reception indicator for the serial PEI interface


V1.22 - of 49

6.3 6 Pin connector assignment

The TAM-200 has a removable 6-pin screw connector block where the power supply

and data connections are provided. Please note that the screw connector is faced

downside!


V1.22 - of 49

Connection table:

Pin Name Remark

1 GND Negative Supply

2 RTS Hardware handshake input, V.24 / RS-232

3 CTS Hardware handshake output, V.24 / RS-232

4 RxD Data input, V.24 / RS-232, 38400bps 8N1

5 TxD Data output, V.24 / RS-232, 38400bps, 8N1

6 VCC Power supply, 12-24V DC +/- 20% min. 1.5A @12V / 1A @24V

All serial interfaces are using RS-232 levels and can directly be connected to a

computer!

If the hardware handshake signals are not used, a wired connection between RTS

and CTS should be made.

6.3.1 Connection diagram to a PC

To connect the TAM-200 to a PC via a serial RS-232 interface the connections below

must be made. In this example the hardware handshake is not used, therefore it's

bridged at the TAM-200 connector.


V1.22 - of 49

6.4 Mechanical Drawing


V1.22 - of 49

6.5 Specifications TAM-200

Functions: TETRA AT-modem for serial and IP communication

Alarm device for SDS and status messages

TETRA voice terminal

Available frequency

ranges:

370 MHz - 470 MHz

806 MHz - 869 MHz

Serial Interfaces UART 1: AT command port (RS-232 level)

UART 2: Service and update port (4pin inside the TAM,

TAM-200 programming cable needed)

Indications: 6 LED providing information about operating status and RSSI

field strength

TETRA features: SDS, Status, SCCH, Packet Data, Multi Slot Packet Data,

SDS size up to 2047 bit, Air Interface Encryption (Class 2/3),

Authentication, Voice Interface

Transmission Power: Up to 3 Watts (Class 3) @400MHz, 1W @800MHz

Static Receiver sensitivity: Min. -112dBm (Typ. -115 dBm)

Dynamic Receiver

sensitivity:

Min. -103 dBm (Typ: -107 dBm)

RF Conformance EN 300 394-1

EMC Conformance EN 301 489-1 and -18

ESD Conformance 61000-4-2

Special options: User applications

Connectors: Removable screw connector, 6pin

Antenna: BNC

Power supply voltage: 12-24 V DC, +- 20%

Consumption in receive

mode:

~ 1W

Consumption in transmit

mode:

~ 3W in average at 1-slot operation

Peaks may go up to 15W!

Operating Temperature: -20 °C to +65 °C

Enclosure: Metal enclosure

Dimensions: 162mm x 65mm x 31mm (excluding connectors)


V1.22 - of 49

7 Configuration examples

All configuration of the TMC-210/TAM-200 can be done via the serial PEI interface,

this includes the configuration of the TETRA parameters!

If Authentication or Air Interface encryption is used, the Piciorgros Key Loader

software is needed along with a TAM-200 programming cable!

Please also note that all devices are TEA1 types by default. If TEA2 or TEA3 is

needed, this needs to be specified on any order! A TEA change is only possible at the

factory, to change the TEA type afterwards the equipment needs to be sent to Piciorgros

and a service fee will apply per device.

In this chapter some basic examples will be shown:

Bring the device into the (unencrypted) TETRA network

Send and receive an SDS

Establish a packet data (PPP) connection

All examples are using the common PuTTY software (Freeware). The serial parameters

must be configured with 38400bps, 8 databit, no parity and 1 stop bit.

All examples are using the extended AT command set enabled (AT+PIMODE=1).


V1.22 - of 49

7.1 Basic TETRA configuration

The TETRA configuration commands are in the extended AT command set which must

be enabled with the AT+PIMODE=1 command.

In this example we configure the modem with the ISSI 1005, MCC 262 and MNC 1.

The frequency scan range will be 50 channels starting with 425 MHz.

We need to use the commands AT+CNETCON to configure MCC, MNC and ISSI and

the AT+CCHAN command to set the scan range.

This is the boot sequence of the TMC-210 after power up:

+BOOTSTART

+SWVER:0451,f444,0453

+CREG:0,0

+CREG:0,0

The "+SWVER:" message reports the software versions of the TMC-210 in the oder

Stack, F444, DSP. This TMC-210 has these versions:

Stack: 04.51

DSP: 04.53

First we need to enable the extended AT commands with AT+PIMODE=1.

Then we need to set the MCC, MNC and ISSI with the command

AT+CNETCON=MCC, MNC, ISSI.

The Scan range will be configured with

AT+CCHAN=0,StartFrequency/100Hz,NumberOfScanChannels

Finally the device must be rebooted with AT+CFUN=1,1


V1.22 - of 49

at+pimode=1

OK

at+cnetcon=262,1,1005

OK

at+cchan=0,4250000,50

OK

at+cfun=1,1

MS Rebooting

+BOOTSTART

+SWVER:0334,0311,0329

+CREG:0,0

+CREG:0,,0

+CREG:2,0,0

+CREG:1,0,0

The "+CREG:1" status announces that the modem is registered to the TETRA network.

The RSSI fieldstrength can be queried with the command "AT+CSQ?". In the extended

PEI mode (PIMODE=1) this gives you also information about the field strength in –

dBm (Here: -47 dBm).

at+csq?

+CSQ:31,0,47,99,38

OK


V1.22 - of 49

7.2 Sending and receiving an SDS message

To send out an SDS message these steps are needed:

Set the message type to SDS

Send the message

To set the message type, the command "AT+CTSDS" must be used. The following

command sets the message type to TL-4 (AI service type 12), the "Called party ident

type" to SSI (0),

at+ctsds=12,0

OK

We now want to send the text "Hello world!" to the ISSI 1001. We need to submit these

command to the modem:

at+cmgs=1001,128 (There is a CRLF after this line)

8202010148656C6C6F20776F726C6421 (This line ends with a CTRL-Z!)

OK

+CMGS:2,3,1,20

The first line "at+cmgs=1001,128" tells the modem that we want to send an SDS of 128

bit (=16 bytes) to the subscriber 1001.

The second line is the data including the TL-4 header:

"82020101" is the 4-byte TL-4 header:

0x82: Protocol Identifier

0x02: Message type: SDS-TRANSFER, Delivery report request: No DR

requested, Service selection: Group or individual service, Store/forward control:

No storage/forward

0x01: Message reference number (should be upcounting with each new message,

value from 0x00-0xff)

0x01: Validity period: No validity period, Forward address type: SSI

"48656C6C6F20776F726C6421" is the text "Hello world!"

The confirmation message "+CMGS:2,3,1,20" gives these information:

SDS-Instance: 2

SDS-Status: 3 (Outgoing message stored and sent)

Message Reference: 1

Transmit Power: 20dBm (this is an extended parameter given in PIMODE=1 to

determine the transmit power the radio current uses based on the parameters of

the network and received RSSI)


V1.22 - of 49

Received SDS are reported unsolicited by the +CTSDSR message. This is the message

from terminal #1001 replying with the text "Hello back"

+CTSDSR:12,1001,0,1005,0,112

8206490148656C6C6F206261636B

It is a message type 12 (SDS-TL4) from ISSI 1001 to ISSI 1005 with 112 bit (14 bytes)

payload.

The payload is the TL-4 header ("82064901") and the text payload "Hello back"

("48656C6C6F206261636B").


V1.22 - of 49

7.3 Packet data connections

To establish a packet data connection, some preparations must be taken on the computer

first.

Go to the Windows Control Panel Telephone and Modem and add a 9600bps

standard modem.

Then go to "Properties"

Click on "Change settings" here:


V1.22 - of 49

Go to "Modem" and change the data rate to "38400":

In the Windows Networking add a new RAS Dialup connection. Choose the Standard

9600 bps Modem and add the dialup number "*99#".


V1.22 - of 49

In "Security" choose either PAP or CHAP protocol, depending on the settings of the

TETRA infrastructure. If you are in doubt, choose PAP first.

In Network IPv4 choose to obtain the IP address automatically


V1.22 - of 49

Click on "Extended" …

… and then unselect to use the PPP connection as a Standard Gateway if your computer

has an internet connection via Ethernet or WiFi.


V1.22 - of 49

Close all windows with "OK", the connections are prepared on the PC.

The TMC-210/TAS-200 uses two separate serial UARTs by default once it's switched

to the extended command set (PIMODE=1). Using two separate ports, one for the AT

commands and the other just for the PPP data, gives many advantages if the target hard-

and software supports the use of separated interfaces.

Windows does NOT support this, here the AT command interface and the PPP data is

using the same serial interface.

Therefore the operating mode for the PPP connection must be switched back to a single

interface on the TMC-210/TAM-200 with the command "AT+PPPSPLIT=0":

at+pppsplit=0

OK

Close the PuTTY terminal window after this to allow Windows to access the serial port

for the dialup connection.

Then click on the network icon in the taskbar:

Choose your RAS dialup connection and click "Connect"


V1.22 - of 49

If the TETRA infrastructure needs a PAP/CHAP username and password for the PPP

connection, enter these credentials here.

Then click "dial".


V1.22 - of 49

And finally the PPP connection is established:

On the TAM-200 and the TMC-210 this is indicated by a solid blue "PPP" LED:


V1.22 - of 49

8 Updating the TMC-210 / TAM-200

To perform software updates these components are needed:

The software "Piciorgros Logger" must be installed on the PC. The PC must

have a serial interface (can be a USB-to-serial cable).

The TMC-210 firmware package folder "TETRA V4 …."

A TAM-200 programming cable if the update should be performed on the TAM-

200

8.1 Preparations

The serial interface of the computer must be connected to the UART2 service port of

the TMC-210.

If the TAM-200 is used, it must be opened to access the UART2. Open the 4 screws and

divide the two enclosure parts.

The UART2 connector is located right from the antenna connector:

On the TMC-210 evaluation board, connect the serial interface to the UART2 DB9-

connector.


V1.22 - of 49

The Piciorgros Logger software must be started now. Go to Target Serial settings

Serial Port

Select the COM port which is used for the connection and set it to 115200 bps, No flow

control:

Connect the serial interface by clicking on the green triangle:

Select View Terminal


V1.22 - of 49

The Terminal Windows must be visible now with the word "(Active)" in the top bar:

If "(Active)" is not visible, it must be switched on by clicking on the red circle button:


V1.22 - of 49

8.2 Software versions and TEA version

To see the software version which are loaded in the module, it needs to be powered up

with the connected UART 2 and the Piciorgros Logger active as described before.

These startup messages will appear in this case:

Important are these lines:

DSP Version: 0453 Version 4.253

Stack Version: 0451 Version 4.51

AIE version: 0B004ae1 The last digit defines the TEA type. 1=TEA1,

2=TEA2 and 3=TEA3.

If a new stack is loaded, the TEA type of the stack must match the TEA version

of the radio!


V1.22 - of 49

8.3 Updating the firmware

First, only new firmware versions must be updated. A firmware folder always has the

versions of Stack, MMI and DSP in the folder name.

The folder "TETRA V4 S0451-D0453" contains these versions:

Stack: 4.51

DSP: 4.53

In case a new software is released, you can compare the software versions of the

firmware folder with the versions in the TMC-210/TAM-200. Only changed versions

must be updated!

8.3.1 Initiate the update sequence

To start the update sequence power down the TMC-210/TAM-200. Then power it up

again and keep the "f" key pressed while the Piciorgros Logger is the active window on

your PC.

If the programming mode is successfully started, you'll see the Flash Programmer

message, followed by "+FLSHRDY":

Remark: The messages "Unidentified record marker …" can appear periodically,

depending on the serial port / cable of the PC. These can be ignored!


V1.22 - of 49

8.3.2 Deletion of the Flash areas

All software areas which should be updated must be erased first.


V1.22 - of 49

Stack:

Choose Target Flash Erase Protocol Stack and OS


V1.22 - of 49

If you're not getting these messages, ending with "+FLSHRDY: ARM Core 0 Erased"

you need to repeat the sequence.


V1.22 - of 49

DSP:

Choose Target Flash Erase DSP Stack Mode

If you're not getting these messages, ending with "+FLSHRDY: ARM Core 1 (DSP)

Erased" you need to repeat the sequence.

IMPORTANT: Do NEVER erase any other areas than these three

mentioned ones! This will render the module unusable and is

must be sent to Piciorgros to recover it!


V1.22 - of 49

8.3.3 Programming the new software versions

After all needed flash areas are erased, the new firmware can be transferred to the

modem.

Make sure to select the subfolder in the firmware package which matches the TEA

type of the modem. If a non matching stack version is programmed, the modem will

not work. In this case you can however start the modem in the Flash Programmer mode

again and erase and reprogram the correct matching stack version!

The programming of each firmware file is started by the "Send file to target" button:


V1.22 - of 49

Stack:

Select the file "firmware_stack.i0" from the firmware folder:

The file will be transferred to the modem:

You should see a pattern like "->->->->->->->->->->->->->" scrolling in the terminal

window in the background. If this does not happen, press "Cancel" and send the file

again to the radio.

Once the programming was successful you should see the message "+FLSHRDY: ARM

Core0 code sector checksum OK"


V1.22 - of 49

DSP:

Select the file "firmware_DSP.i00" from the firmware folder:

The file will be transferred to the modem:

You should see a pattern like "->->->->->->->->->->->->->" scrolling in the terminal

window in the background. If this does not happen, press "Cancel" and send the file

again to the radio.

Once the programming was successful you should see the message "+FLSHRDY: ARM

Core1 (DSP) code sector checksum OK"


V1.22 - of 49

8.3.4 Finishing the software update

Once all needed firmware areas are reprogrammed, power cycle the radio. Make sure

the startup messages are appearing again, ending with the line "MMI READY".

You might compare the reported firmware versions to ensure the update was successful.


V1.22 - of 49

9 Appendix – PEI commands and EKit drawings

On the following pages the AT commands for the standard and extended mode are

listed.

TMC-210

Tetra Modem Core

PEI User Guide

Funk-Electronic Piciorgros

GmbH Claudiastr. 5 51149 Köln

PEI Users Guide

March 2020 Page 2 of 84

1. Disclaimer The information contained within this document is the copyright of Funk-Electronic Piciorgros GmbH.

No part of this document may be disclosed, reproduced or transmitted in any form, or by any means

without the written permission of Funk-Electronic Piciorgros GmbH. The term document extends to all

forms of media in which information may be embodied.

PEI Users Guide


2. Contents

3.1. Purpose 6

3.2. Scope 6

3.3. References 6

3.4. Glossary 6

7.1. Command Mode 10

7.2. Circuit Mode Data State 10

9.1. Reception and Connection 12

9.2. Transmission control in a half-duplex call 12

9.3. Call Termination 12

10.1. Reception and Connection 13

10.2. Call Termination 13

10.3. Switching Between a Call and Command Mode 14

11.1. Commands 16 11.1.1. A/ – Repeat Last Command 16 11.1.2. AT – Attention Command 16 11.1.3. ATA – Answer Call 16 11.1.4. ATD- Dial 17 11.1.5. ATE- Echo 18 11.1.6. <cr><lf>OK<cr><lf>ATH- Hook 19 11.1.7. <cr><lf>ERROR<cr><lf>ATO- Return to online data state 20 11.1.8. ATQ- Result Code 21 11.1.9. ATS0 - Automatic answer 22 11.1.10. ATS2 - Escape character 23 11.1.11. ATS3 - Command line termination character 24 11.1.12. ATS4 - Command line termination character 25 11.1.13. ATS5 - Command line editing character 26 11.1.14. ATV-Command : Response format 27 11.1.15. ATZ-Command : Reset to default configuration 28 11.1.16. +CBC : Return Battery information 29 11.1.17. +CEER : Return the Reason for failure 30 11.1.18. +CME: MT Error result Code 31 11.1.19. +CMEE: Report MT error 33 11.1.20. +CMGD: Delete message 34 11.1.21. +CMGF: Set Message Format 35 11.1.22. +CMGL:List messages 36 11.1.23. +CMGR: Read message 38 11.1.24. +CMGS: Send message 40 11.1.24.1. SDS Examples 42 11.1.24.1.1. Status Message Transmission Example 42

PEI Users Guide


11.1.24.1.2. Status Message Reception Example 42 11.1.24.1.3. Simple SDS-TL protocol transmission example 43 11.1.24.1.4. Simple SDS-TL protocol reception example 43 11.1.25. +CNUM: Get MT TETRA Identities 44 11.1.26. +CREG: Network Registration 45 11.1.27. +CTOM : Set Operating Mode 47 11.1.28. + CTGS: Group Set Up 48 11.1.29. +CSQ: Signal quality 49 11.1.30. +CTSDC: Tetra Service Definition 50 11.1.31. +CTSDS: Tetra Service Definition for SDS Service 53 11.1.32. +CTSTR: Tetra Status Text Read. 55 11.1.33. +CTXD: Transmit Demand 56 11.1.34. +CUTXC: Up Transmit Ceased. 57 11.1.35. +GCAP: Request complete capabilities list 58 11.1.36. +GMI : Request manufacturer identification 59 11.1.37. +GMM : Request model identification 60 11.1.38. +GMR : Request revision identification 61 11.1.39. +CMCC : Mobile Network Code 62 11.1.40. +CMNC : Mobile Network Code 63 11.1.41. +CCHN: Main Control Channel 63 11.1.42. +CLAI: Serving Cell Location Area ID 64 11.1.43. +CNLA: Neighbour Cell Location Area ID 64

11.2. Unsolicited Responses 65 11.2.1. +CMTI: New message indication 65 11.2.2. +CTICN: Tetra Incoming call progress. 66 11.2.3. +CTSDSR: Unsolicited SDS indication 68 11.2.4. +CTOCP: Tetra Outgoing Call Progress. 69 11.2.5. +CTCR: Tetra Call Release. 70 11.2.6. +CTXG: Transmission Grant. 71 11.2.7. +CDTXC: Down Transmission Ceased 82

11.3. Errors Within Tetra PEI 84 11.3.1. Responses to commands 84

PEI Users Guide


3. Introduction

3.1. Purpose

This document gives the functional specification for the Peripheral Equipment Interface (PEI) provided as part of the OMAP radio software. The PEI system consists of a command line interpreter for the ASCII character string originating from the Terminal Equipment (typically a lap top computer) connected to the MT over its serial interface. This document is useful for developers of external applications utilising the Peripheral Equipment Interface (PEI) of TETRA portables utilizing the Osiris software platform.

3.2. Scope

The software described herein is intended to provide the PEI capability of transmission and reception of circuit data (including setting of circuit data parameters) for the MT, operating in V+D mode. Included within this document are details regarding the commands required to send and receive Status and Short Data Service (SDS) Messages over a TETRA (TErrestrial Trunked RAdio) network. The proposed system supports DMO SDS mode. The system does provide the Hays AT and extended command interface between the TE and the MT. It can be used for all the commonly used facilities like file transfer in the environment of a laptop computer (or any other TE), connected to the MT.

3.3. References

1. Extended AT Command Set 2. ITU V.250 3. ETSI specification ETS 300 392-5 (v2.1.1) - http://www.etsi.org/

3.4. Glossary

· ASCII American Standard Code for Information Interchange

· AT Attention

· CR Carriage Return

· DMO Direct Mode Operation

· DSP Digital Signal Processor

· GUI Graphical User Interface

· ITU International Telecommunications Union

· LF Line Feed

· LSB Least Significant Bit

· MMI Man Machine Interface

· MT Mobile Terminal

· OS Operating System

· PABX Private Automatic Branch Exchange

· PEI Peripheral Equipment Interface

· PSTN Public Switched Telephone Network

· SwMI Switching and Management Infrastructure

· TBD To be defined

· TE Terminal Equipment

PEI Users Guide


PEI Users Guide


4. Overview The main functionality behind this document gives the functional specification for the PEI

interface provided as part of the OMAP radio software. The radio software contains a command line interpreter, which parses all the commands received from terminal equipment connected to the MT. The PEI software responds with the correct response code for each command. The commands and the responses are given in detail at section STANDARD PEI AT COMMAND SET OVERVIEW

5. Serial Protocol Serial data transmission between the MT and Terminal Equipment devices operate with the following parameters.

Parameter Setting Rate (bps) 38400 Start Bits 1 Data Bits 8 Stop Bits 1 Parity None Flow Control Hardware Control used.

6. Command syntax The AT Command Mode is activated when the radio is switched into ‘Data Mode’. This is usually done by selection from a menu item in the MMI. In this mode, commands sent from the TE

application to the PEI of the MT should always start with a two character AT prefix, in upper or

lower case, however the ‘A’ and the ‘T’ must always be of the same case. Commands should be

terminated with a <CR> (Carriage Return – ASCII code 13) character. Note that the terminal will

also accept and ignore the <LF> (Line Feed – ASCII code 10) character following a <CR> but

this is not required. In Execute and Set commands, any parameter may be omitted. When a parameter is omitted, it will take the default value as specified for each command.

PEI Users Guide


7. Different Modes of Operation of PEIs

State Diagram for AT Command Implementation is as above. There are two modes of operation in PEI. One is Command mode and other is Circuit mode data mode. In command mode, PEI accepts ASCII characters from serial port and treats them as commands. Each command is parsed and its response is sent to TE. Both TE and MT enter this state on initialization or PEI link establishment. It is always entered from on line data state when any ongoing call is cleared or when the TE sends a recognized Escape sequence. A Circuit Mode Data call is in progress whilst in the Circuit mode data mode state. In this state all AT commands are ignored.

PEI Users Guide


7.1. Command Mode

There are two types of responses that may be issued by the MT: information text and result codes. Information text responses consist of three parts: a header, text, and a trailer. The characters transmitted for the header are determined by a user setting. The trailer consists of two characters, being the character having the ordinal value of parameter S3 followed by the character having the ordinal value of parameter S4. Information text normally consists of a single line; information text returned in response to +GCM commands contain multiple lines, and the text therefore include CR, LF, and other formatting characters to improve readability. Result codes consist of three parts: a header, the result text, and a trailer. The characters transmitted for the header and trailer are determined by a user setting. The result text may be transmitted as a number or as a string, depending on a user-selectable setting . There are three types of result codes: final, intermediate, and unsolicited. A final result code indicates the completion of a full MT action and a willingness to accept new commands from the TE. An intermediate result code is a report of the progress of a MT action. The CONNECT result code is an intermediate result code. In the case of a dialling or answering command, the MT moves from command state to online data state, and issues a CONNECT result code. This is an intermediate result code for the MT because it is not prepared to accept commands from the TE while in online data state. When the MT moves back to the command state, it will then issue a final result code (such as OK or NO CARRIER). Unsolicited result codes (such as RING) indicate the occurrence of an event not directly associated with the issuance of a command from the TE.

7.2. Circuit Mode Data State

When a Circuit Mode Data call is successfully established via the ATD or ATA commands, the PEI will switch from AT Command Mode to Transparent Data Mode. In Transparent Data Mode, the terminal receives and sends free form binary data. Flow control is applied to the PEI as per ITU V.250. The framing of this data is done by a proprietary architecture and so this data transmission may not be compatible with another manufacturer’s radio. When the Data call is cleared down, the interface will return to AT Command Mode.

PEI Users Guide


8. STANDARD PEI TEXT MESSAGING There are several types of Data Messages and Data Call Types available to the application developer. These include: 1. Status Messaging. This type of message transfer sends a pre coded status value (number) over the air, which corresponds to a particular pre-programmed message in the TETRA Terminal’s customisation. 2. Short Data Service Messaging. This type of Data Message transfers a short message of typically up to 120 characters. 1) A +CTOM command is used to set the operating mode. 2) A +CTSDS command is used to set parameters for subsequent CMGW or CMGS commands. 3) A CMGW or CMGS command is used to send the message (Message stack or direct) using the predefined parameters. Subsequent calls of the same type need a new +CTSDS command. So a new set of parameters is to be set for every call. Implementers should take care that no calls overlap if they have different CTSDS parameters.

9. Circuit-mode Voice Calls The Funk-Electronic Piciorgros GmbH Radio supports the following call types. • full-duplex individual voice calls with hook signalling (not available in DMO) • half-duplex individual voice calls with hook signalling (not available in DMO) • half-duplex group voice calls with direct setup A minimal set of functionalities is implemented for controlling the MT from TE in voice calls though the PEI is designed primarily for circuit mode data transfer. The initiation of an outgoing voice call takes two commands. 1) A +CTSDC command is used to set parameters for subsequent dial commands. 2) ATD command is used to initiate a call set up using the predefined parameters. Subsequent calls of the same type need a new +CTSDS command. So a new set of parameters can be set for every call. Implementers should take care that no calls overlap if they have different CTSDC parameters. A voice call is set up on an "ATD" command if the <AI service> parameter has been set to voice. 1) If the <called party ident type> is PABX the MT will put the PABX gateway into the called party field on the air interface and the dialled string into the ESN field. 2) If the <called party ident type> is PSTN the MT will put the PSTN gateway into the called party field on the air interface and the dialled string into the ESN field. 3) In all other cases the MT will perform computations on the dialled string to generate the called party address field used on the air interface. The computations will depend on the value of <called party ident type>. AT+CTSDC=0,0,0,1,1,0,1,1 (group call) AT+CTSDC=0,0,0,0,0,0,0,1 (duplex call to another Tetra identity) AT+CTSDC=0,0,0,0,1,0,0,1 (half-duplex call to another individual Tetra identity) AT+CTSDC=0,3,0,0,0,0,0,1 (duplex call to a PABX identity) AT+CTSDC=0,4,0,0,0,0,0,1 (duplex call to a PSTN identity)

PEI Users Guide


9.1. Reception and Connection

The unsolicited response (+CTICN) informs the TE that a voice call request has been made to the TE/MT station. The parameters are used to determine further TE actions. For example the parameters <hook> and <simplex> values will determine whether the TE starts a ring tone or goes straight to the call maintenance phase and whether to use the PTT in speech calls. In the event of hook signalling the TE will send the standard command "A" when the TE MMI (or application) goes "off hook" to continue the call set up process. The incoming call progress may be updated by further optional messages (+CTICN) to inform the TE of the call set up progress and for example will be used by the TE to indicate a resource queue. In the event of a voice call with direct signalling the TE MMI will indicate open voice paths to selected speakers and microphones. When the call is ready for completion the TE sends a connect message to the MT and both enter the call maintenance phase.

9.2. Transmission control in a half-duplex call

During a half-duplex voice call, which has been initiated from, or routed, to, the external data application, transmissions are controlled using the following commands: AT+CTXD Transmission Demand. AT+CUTXC Transmission Ceased. +CTXG Transmission Grant Status. +CDTXC Transmission Ceased. +CTXI Transmission Interrupt (not implemented in the current PEI). +CTXW Transmission Wait (not implemented in the current PEI). +CTXN Transmission Continue(not implemented in the current PEI). In order to use these commands the TE and MT shall change into the AT command state (using hardware or escape signalling) the Transmit arbitration commands can be used. Once the transmit direction has been established the TE shall send an ATO command which (when acknowledged) will put both back into AT circuit data mode.

9.3. Call Termination

A voice call which has been initiated from, or routed to, the external data application, may be terminated by the SwMI or by the remote terminal, in which case this will be reported to the external application using a +CTCR response. A voice call can be cleared from the TE, by sending the standard command "H".

PEI Users Guide


10. Circuit-mode Data Calls The Funk-Electronic Piciorgros GmbH radios support full-duplex individual circuit-mode data calls. The initiation of an outgoing circuit mode data call takes two commands. 1) A +CTSDC command is used to set parameters for subsequent dial commands. 2) ATD command is used to initiate a call set up using the predefined parameters. Subsequent calls of the same type do not need a new +CTSDC command but it is recommended that a new set of parameters be set for every call. Implementers should take care that no calls overlap if they have different CTSDC parameters. The MT interprets the "D" command in different ways depending on the <AI service> and <called party ident type> parameters set by the +CTSDC command. The dialled string is normally used as the called party address and the call is set up using the parameters set by the previous +CTSDC command. The MT should check the dialled string for valid numbering. Illegal numbers or combinations of the dialled string and the +CTSDC parameters shall cause an error result code. A circuit mode data call is set up on a "ATD" command if the <AI service> parameter has been set to one of the circuit mode data selections (values 1-7). The MT will generate the called party address field used on the air interface from the dialled string in the "ATD" command. The computations will depend on the value of <called party ident type>. Note PSTN and PABX are not valid <called party ident types>. When the final result code indicates successful execution of the "ATD" command the MT and TE change to AT circuit mode data state. The outgoing call progress responses (+CTOP) inform the TE of the call set up progress The use of call progress signalling is implementation dependant, but for example will be used by the TE to indicate a resource queue. In order to set up a data call, the data application needs to set the parameters for the call using AT+CTSDC, Parameters appropriate for data calls are: AT+CTSDC=1,0,0,0,0,0,0,0 (7.2kb/s unprotected duplex hooking individual call) AT+CTSDC=2,0,0,0,0,0,0,0 (4.8kb/s low protection duplex hooking individual call) AT+CTSDC=1,0,0,0,1,0,0,0 (7.2kb/s unprotected half-duplex hooking individual call) AT+CTSDC=2,0,0,0,1,0,0,0 (4.8kb/s low protection half-duplex hooking individual call)

10.1. Reception and Connection

The unsolicited response (+CTICN) with the right parameters informs the TE that a circuit mode data call request has been made to the TE/MT station. The parameters are used to determine further TE actions. For example the parameters <hook> and <slots/codec> values will determine whether the TE starts a ring tone or goes straight to the call maintenance phase and whether it needs to change the baud rate of the PEI. In the event of hook signalling the TE will send the standard command "A" when the TE MMI goes "off hook" to continue the call set up process. The incoming call progress may be updated by further optional messages (+CTICN) to inform the TE of the call set up progress and for example will be used by the TE to indicate a resource queue. In the event of a circuit mode data call with direct signalling the TE MMI will indicate connection and connect the data device to the circuit. When the call is ready for completion the TE sends a connect message to the MT and both will change state to AT circuit mode data.

10.2. Call Termination

A data call may be terminated by the SwMI or by the remote terminal, in which case this will be reported to the external application using a +CTCR response. The local Data Application may also terminate a Data call by switching into command mode, and then sending an ATH command.

PEI Users Guide


10.3. Switching Between a Call and Command Mode

For an ongoing circuit mode data call that has been interrupted by the TE Escape sequence (+++) the TE can send the ATO command to resume the interrupted call.

PEI Users Guide


Example of Message Flow for a Half-Duplex Data/Voice Call

TE MT SWMI MT TE

AT+CTSDC

OK

ATD

OK

+CTOCP

+CTXG

+CDTXC

AT+CTXD

OK

+CTXG

AT+CUTXC

OK

+CDTXC

ATH

+CTCR

OK

U-SETUP

D-ALERT

D-CONNECT

D-TX-CEASED

D-CALL-PROC

U-TX-DEMAND

D-TX-GRANTED

U-TX-CEASED

D-TX-CEASED

U-DISCONNECT

D-RELEASE

D-SETUP

U-CONNECT

D-CONNECT-ACK

U-TX-CEASED

D-TX-CEASED

D-TX-GRANTED

D-TX-CEASED

D-RELEASE

+CTICN

ATA

+CTCC

+CTXG

OK

AT+CUTXC OK

+CDTXC

+CTXG

+CDTXC

+CTCR

SetUp

End Tx

Next Tx

Clear

PEI Users Guide


11. STANDARD PEI AT COMMAND SET OVERVIEW

11.1. Commands

11.1.1. A/ – Repeat Last Command

Description This command instructs the MT to execute the last command. A trailing <cr> is not required. Any additional commands that appear after A on the same command line are ignored. Execution Syntax

A/

11.1.2. AT – Attention Command

Description This command Checks whether PEI is in Command mode or not. Execution Syntax

AT

11.1.3. ATA – Answer Call

Description This command instructs the MT to immediately connect to the line and start the answer sequence. Any additional commands that appear after A on the same command line are ignored. ExecutionSyntax ATA Set Syntax N/A Test Syntax ATA=? Read Syntax N/A Responses

State Response

Incoming call ringing +CTCC: <params>

no new incoming call for any reason +CME ERROR: 3 (command out of context)

Test Response <cr><lf>OK<cr><lf> Example <cr><lf>+CTICN: 456,0,0,0,20550,0,0,0,0,1<cr><lf> ATA<cr> <cr><lf>+CTCC: 456,0,0,0,0,0,1<cr><lf>

PEI Users Guide


11.1.4. ATD- Dial

Description This command instructs the MT to originate a call. All characters appearing on the same command line after the "D" are considered part of the call addressing information to be signalled to the network up to the end of the command line. Any characters appearing in the dial string that the MT does not recognize as a valid part of the call addressing information or as a valid modifier will not be ignored and results in an error report Valid characters are 0,1,2,3,4,5,6,7,8,9, *, #, +. The dial string type is set either to the default settings, or to the last + CTSDC command. ExecutionSyntax D[<dial_string>][;] Set Syntax N/A Test Syntax ATD=? Read Syntax N/A Responses

Alphabetic

(ATV1)

Numeric

(ATV0) Description

CONNECT 1 If connection is successfully established. This result code is

transmitted immediately before circuit 109 is turned on

NO

CARRIER

3 If a connection cannot be established, or was aborted by reception

of an additional character from the TE

ERROR 4 If issued while in online command state

NO

ANSWER

8 If connection could not be established due to called system is not

ready

+CTCR Release cause of call disconnection.

Test Response <cr><lf>OK<cr><lf> Example ATD20550<cr> <cr><lf>CONNECT<cr><lf>

PEI Users Guide


11.1.5. ATE- Echo

Description The setting of this parameter determines whether or not the MT echoes characters received from the TE during command state and online command state. ExecutionSyntax N/A Set Syntax ATE[<value>] Read Syntax ATE? Test Syntax ATE=? Defined values 0 Switch echo off 1 Switch echo on Any other value returns : +ERROR (parameter out of range) Default 1 Echo is on Test Response <cr><lf>OK<cr><lf> Example : ATE1<cr>

PEI Users Guide


11.1.6. <cr><lf>OK<cr><lf>ATH- Hook

Description If the value is zero, this command instructs the MT to disconnect from the line, terminating any call in progress. All of the functions of the command shall be completed before the MT issues any result code. Any other value is equivalent to “Off Hook”, that is equivalent to the “A” command. Execution SyntaxATH[<value>] Set Syntax N/A Read Syntax N/A Test Syntax ATH=? Defined values 0 – go back on hook (disconnect call) Any other value returns ERROR

State Response

In call on PEI +CTCR: <Params>

Not in a call controlled by PEI ERROR

Test Response <cr><lf>OK<cr><lf> Example : ATH0<cr> <cr><lf>+CTCR: 123,0<cr><lf> ATH1<cr>

PEI Users Guide


11.1.7. <cr><lf>ERROR<cr><lf>ATO- Return to online data state

Description

Causes the MT to return to online data state and issue a CONNECT or CONNECT <text> result code. To get to this state, a data call must have been either initiated, or answered, then the escape sequence sent to switch from online mode to command mode. This command is only appropriate to the command during a data call. Voice calls do not have online data mode. Execution Syntax ATO[<value>] Set Syntax N/A Read Syntax N/A Test Syntax ATO=? Defined values 0 Return to online data state from online command state Response

State Response

Data Call active, but interface in command mode. Call successfully resumed

CONNECT

Not in a data call on this PEI which has been escaped

ERROR

Test Response <cr><lf>OK<cr><lf> Example : ATO<cr> <cr><lf>CONNECT<cr><lf>

PEI Users Guide


11.1.8. ATQ- Result Code

Description The setting of this parameter determines whether or not the MT transmits result codes to the TE. When result codes are being suppressed, no portion of any intermediate, final, or unsolicited result code – header, result text, line terminator, or trailer – is transmitted. Information text transmitted in response to commands is not affected by the setting of this parameter. Execution Syntax

ATQ [<value>] Set Syntax N/A Read Syntax ATQ? Test Syntax ATQ=? Defined values 0 Terminal transmits result codes 1 Terminal does not transmit result codes. (there is no response to this command) Any other value gives a response: ERROR Default 0 Terminal transmits result codes Test Response <cr><lf>OK<cr><lf> Example : ATQ0<cr> <cr><lf>OK<cr><lf> ATQ1<cr>

PEI Users Guide


11.1.9. ATS0 - Automatic answer

Description This S-parameter controls the automatic answering feature of the MT. If set to 0,, automatic answering is disabled. If set to a non-zero value, MT will answer when the incoming call indication (ring) has occurred the number of times indicated by the value. For example, setting this parameter to 1 will cause the MT to answer an incoming call on the first ring. Execution Syntax N/A Set Syntax ATS0 =[<value>] Read Syntax ATS0? Test Syntax ATS0=? Defined values

0 Automatic answering is disabled.

1 to 255 Enable automatic answering on the ring number specified.

Default 0 Test Response <cr><lf>OK<cr><lf> Example ATS0=1<cr> <cr><lf>OK<cr><lf> ATS0?<cr> <cr><lf>001<cr><lf>

<cr><lf>OK<cr><lf>

PEI Users Guide


11.1.10. ATS2 - Escape character

Description Defines the escape character to be used Execution Syntax N/A Set Syntax ATS2=[<value>] Read Syntax ATS2? Test Syntax ATS2=?

Defined values

The value is the decimal value of a character to be used for the escape sequence. Values 0 to 127 are

valid Default + Return Values Value = 0 – 127 OK Any other value gives a response: ERROR Test Response <cr><lf>OK<cr><lf> Example : ATS2=37<cr> <cr><lf>OK<cr><lf> <cr><lf>+CTICN: 123,0,0,0,123456,0,0,0,0,1<cr><lf> <cr><lf>OK<cr><lf> ATA<cr> <cr><lf>+CTCC: 123,0,0,0,0,0,1<cr><lf> <cr><lf>+Hello World<cr><lf> %%%

<cr><lf>OK<cr><lf>

PEI Users Guide


11.1.11. ATS3 - Command line termination character

Description Defines the command line termination character. The previous value of S3 is used to determine the command line termination character for entry of the command line containing the S3 setting command. However, the result code issued will use the value of S3 as set during the processing of the command line. For example, if

S3 was previously set to 13 and the command line "ATS3=30" is issued, the command line will be terminated with a CR character, but the result code issued will use the character with the ordinal value 30 in place of the CR. Execution Syntax N/A Set Syntax ATS3=[<value>] Read Syntax ATS3? Test Syntax ATS3=? Defined values

0 to 127 Set command line termination character to this value.

Default 13 Carriage Return Character Return value If value = 0 – 127 OK Any other value gives a response: ERROR (parameter out of range) Test Response <cr><lf>OK<cr><lf> Example : ATS3=10<cr> <cr><lf>OK<cr><lf> AT<LF> <cr><lf>OK<cr><lf>

AT<CR>

PEI Users Guide


11.1.12. ATS4 - Command line termination character

Description This S-parameter represents the decimal value of the character generated by the MT as part of the header, trailer, and terminator for result codes and information text, along with the S3 parameter. If the value of S4 is changed in a command line, the result code issued in response to that command line will use the new value of S4. For instance, the defaults for S3 and S4 would give a response of <cr><lf>OK<cr><lf> Execution Syntax N/A Set Syntax ATS4=[<value>] Read Syntax ATS4? Test Syntax ATS4=? Defined values

0 to 127 Set command line termination character to this value.. Default 10 Line Feed Character Return value If value = 0 – 127 OK Any other value gives a response: ERROR Test Response <cr><lf>OK<cr><lf> Example : ATS4=36<cr> <cr><lf>OK<cr><lf> AT% <cr><lf>OK<cr><lf>

PEI Users Guide


11.1.13. ATS5 - Command line editing character

Description This S-parameter represents the decimal value of the character recognized by the MT as a request to delete from the command line the immediately preceding character. This character is also known as the backspace character. Set Syntax ATS5=[<value>] Read Syntax ATS5? Test Syntax ATS5=? Defined values

0 to 127 .Set command line termination character to this value. 8 is the default value.

Return value If value = 0 – 127 OK Any other value gives a response: ERROR Default 8 Backspace Character Test Response <cr><lf>OK<cr><lf> Example : ATS5=38<cr> <cr><lf>OK<cr><lf> Typed: helll&o Echo: helll& &o <cr><lf>ERROR<cr><lf>

PEI Users Guide


11.1.14. ATV-Command : Response format

Description The setting of this parameter determines the contents of the header and trailer transmitted with result codes and information responses. It also determines whether result codes are transmitted in a numeric form or an alphabetic (or "verbose") form. The text portion of information responses is not affected by this setting. Execution Syntax ATV[<value>] Set Syntax N/A Read Syntax ATV? Test Syntax ATV=? Defined values 0 MT transmits limited headers and trailers and numeric text. 1 MT transmits full headers and trailers and verbose response text. Return Values If value = 0 – 1 OK Any other value gives a response: ERROR Responses

Value = 0 Value = 1

Information responses <text><cr><lf> <cr><lf>

<text><cr><lf>

Result codes <numeric code><cr> <cr><lf>

<verbose code><cr><lf>

Default

0

Test Response <cr><lf>OK<cr><lf>

Example ATV1 <cr><lf>OK<cr><lf>

PEI Users Guide


11.1.15. ATZ-Command : Reset to default configuration

Description This command instructs the MT to set all parameters to their factory defaults. This may include taking into consideration the settings of hardware configuration switches or non-volatile parameter storage. All of the functions of the command will be completed before the MT issues the result code. Execution Syntax ATZ Set Syntax N/A Read Syntax N/A Test Syntax ATZ=? Return Values

OK If <value> is recognized.

ERROR If <value> is not recognized or supported.

Example :

ATZ<CR>

<cr><lf>OK<cr><lf> Default Configuration Table

Echo E 1 = Echo on

Quiet Mode Q 0=Quiet mode off

Auto answer S0 0 = Disabled

Escape Character S2 +

Command line terminator S3 13 = CR

Response formatting S4 10 = LF

Command line editing S5 8 = BS

Verbose errors V 1 = Full headers and trailers

Final error reporting CMEE 1 = Extended numeric errors

Parameters for SDS services CTSDS AI service = 12 (SDS type 4) Called Party ID type = 0 (SSI) Area = 0 Access Priority = 0 End-to-end Encryption = 0

Parameters for Circuit mode services (data or voice)

CTSDC AI service = 0 (Tetra Speech) Called Party ID type = 0 (SSI) Area = 0 Hook = 0 Simplex = 0 End-to-end Encryption = 0

PEI Users Guide


11.1.16. +CBC : Return Battery information

Description Inform the TE on the battery connection state <bcs> and the battery charge level <bcl> of the MT battery. This is an Funk-Electronic Piciorgros GmbH proprietary command

Execution Syntax AT+CBC Set Syntax N/A Read Syntax N/A Test Syntax AT+CBC=? Return Values +CBC: <bcs>,<bcl> <CR><LF> +CBC: ERROR <CR><LF> Defined values <bcs>: 0 MT is powered by the battery 1 MT has a battery connected, but is not powered by it 2 MT does not have a battery connected 3 Recognized power fault, calls inhibited <bcl>: 0 battery is exhausted, or MT does not have a battery connected 1 battery has 1 to 100 percent capacity remaining Example AT+CBC<cr> +CBC: 0, 25<cr><lf>

PEI Users Guide


11.1.17. +CEER : Return the Reason for failure

Description Causes the MT to return one or more line of information text on the reason for failure in the last unsuccessful call setup, call modification or the reason for the last call release based on the information provided on the TETRA network. If there was no such previous cases, the text <CR>NONE<LF>, followed by the result code OK will be returned. Execution Syntax AT+CEER Set Syntax N/A Read Syntax N/A Test Syntax N/A

Responses +CEER:<CR>Reason for failure<LF> followed by OK. Examples AT+CEER<cr> <cr>NONE<lf> <cr><lf>OK<cr><lf>

PEI Users Guide


11.1.18. +CME: MT Error result Code

Description The response +CME ERROR: <extended error report code> result code is similar to the regular ERROR result code but gives the TE more detailed information on the command error. The format of <extended error report code> can be either numeric or verbose. This is set with the command +CMEE. Response is unsolicited .

Responses +CME: ERROR <extended error report code> Execution Syntax N/A Set Syntax AT +CMEE=<value> Read Syntax AT +CMEE? Test Syntax AT +CMEE=? Defined values The terminal returns extended code CME error and numeric result code. 0 MT_FAILURE 1 NO_CONNECTION_TO_MT 2 MT_ADAPTER_LINK_RESERVED 3 OPERATION_NOT_ALLOWED 4 OPERATION_NOT_SUPPORTED 5 PH_SIM_PIN_REQUIRED 10 SIM_NOT_INSERTED 11 SIM_CHV1_REQUIRED 12 SIM_UNBLOCKING_CHV1_REQUIRED 13 SIM_FAILURE 14 SIM_BUSY 15 SIM_WRONG 16 INCORRECT_PASSWORD 17 SIM_CHV2_REQUIRED 18 SIM_UNBLOCKING_CHV2_REQUIRED 19 MEMORY_FULL 20 INVALID_INDEX 21 NOT_FOUND 22 MEMORY_FAILURE 24 TEXT_STRING_TOO_LONG 25 INVALID_CHARACTERS_IN_TEXT_STRING 26 DIAL_STRING_TOO_LONG 27 INVALID_CHARACTERS_INDIAL_STRING 30 NO_NETWORK_SERVICE 31 NETWORK_TIMEOUT 32 ERROR_DECODING_DATA 33 PARAMETER_WRONG_TYPE 34 PARAMETER_VALUE_OUT_OF_RANFGE 35 SYNTAX_ERROR 36 DATA_RECEIVED_WITHOUT_COMMAND 37 TIMEOUT_WAITING_FOR_DATA 38 PROTOCOL_IDETIFIER_ALREADY_REGISTERED 39 REGISTRATION_TABLE_FULL 330 SMSC_ADDRESS_UNKNOWN 331 UNKNOWN

PEI Users Guide


Test Response Syntax +CMEE: (list of extended error report types)<cr><lf> <cr><lf>OK<cr><lf> Test Response +CMEE: (1)<cr><lf> <cr><lf>OK<cr><lf>

Example : AT+CMEE=1<cr> <cr><lf>OK<cr><lf> AT+CMEE?<cr> <cr><lf>+CMEE: 1<cr><lf>

PEI Users Guide


11.1.19. +CMEE: Report MT error

Description Set command disables or enables the use of the final result code +CME ERROR : <extended error report code>. When enabled, MT related errors cause +CME ERROR : <extended error report code> instead of the regular ERROR final result code. ERROR is returned when the error is related to syntax, invalid parameters or MT functionality. Responses +CMEE: <extend error report> Syntax AT+CMEE=<extend error report> AT+CMEE? AT+CMEE=? Execution Syntax N/A Set Syntax AT +CMEE=<value> Read Syntax AT +CMEE? Test Syntax AT +CMEE=? Defined Values <extend error report> 0 - Disable +CME ERROR: <extended error report code> and use "ERROR"(default) 1 - Enable +CME ERROR: <extended error report code> result code and use numeric <extended error reportcode> values 2 - Enable +CME ERROR: <extended error report code> result code and use verbose <extended error report code> values Test Response Syntax +CMEE: (list of extended error report types)<cr><lf> <cr><lf>OK<cr><lf> Test Response +CMEE: (1)<cr><lf> <cr><lf>OK<cr><lf> Example : AT+CMEE=1<cr> <cr><lf>OK<cr><lf> AT+CMEE?<cr> <cr><lf>+CMEE: 1<cr><lf

PEI Users Guide


11.1.20. +CMGD: Delete message

Description The set command deletes the message from the message stack <AI service> at all given storage locations <message index>. If no index is given then all messages of the defined SDS type will be deleted. Responses OK Execution Syntax AT+CMGD=<AI service>, [<message index>] [, <message index>] Set Syntax N/A Read Syntax N/A Test Syntax AT+CMGD =? Defined Values <AI service> 0 - TETRA speech(default) 1 - 7,2 kbit/s unprotected data 2 - Low protection 4,8 kbit/s short interleaving depth = 1 3 - Low protection 4,8 kbit/s medium interleaving depth = 4 4 - Low protection 4,8 kbit/s long interleaving depth = 8 5 - High protection 2,4 kbit/s short interleaving depth = 1 6 - High protection 2,4 kbit/s medium interleaving depth = 4 7 - High protection 2,4 kbit/s high interleaving depth = 8 8 - Packet Data 9 - SDS type 1 (16 bits) 10 - SDS type 2 (32 bits) 11 - SDS type 3 (64 bits) 12 - SDS type 4 (0 - 2 047 bits) 13 - Status (16 bits, some values are reserved in EN 300 392-2 [2]) <message index> It has the range 0 - 65,535. Example : AT+CMGD=0,1,<cr> <cr><lf>OK<cr><lf>

PEI Users Guide


11.1.21. +CMGF: Set Message Format

Description This command is used to set the message format to either PDU mode or TEXT mode. Responses OK Execution Syntax N/A Set Syntax AT+CMGF=<message format> Read Syntax N/A Test Syntax AT+CMGF =? Defined Values <message format> 0 – PDU mode 1 – TEXT mode. Default is TEXT mode.

PEI Users Guide


11.1.22. +CMGL:List messages

Description The set command returns a list of messages stored in the MT message stack. Defined by <AI service>.The data message itself is retrieved using a CMGR command. If <SDS status> is present then only indices to messages with status value <SDS status> are returned. If not then all active message indices of SDS type defined by <AI service> are returned. The result code text contains details of any messages in the stack that meet the set criteria. The read message command +CMGR is used in conjunction with the <message index> to return the actual data. Responses +CMGL: <AI service>, <message index>, <SDS status>, [<calling party ident>, <calling party ident type>], [<calledparty ident>, <called party type>] Execution Syntax AT+CMGL=<AI service> [, <SDS status>] Set Syntax N/A Read Syntax N/A Test Syntax AT+CMGL =? Defined Values <AI service> 0 - TETRA speech(default) 1 - 7,2 kbit/s unprotected data 2 - Low protection 4,8 kbit/s short interleaving depth = 1 3 - Low protection 4,8 kbit/s medium interleaving depth = 4 4 - Low protection 4,8 kbit/s long interleaving depth = 8 5 - High protection 2,4 kbit/s short interleaving depth = 1 6 - High protection 2,4 kbit/s medium interleaving depth = 4 7 - High protection 2,4 kbit/s high interleaving depth = 8 8 - Packet Data 9 - SDS type 1 (16 bits) 10 - SDS type 2 (32 bits) 11 - SDS type 3 (64 bits) 12 - SDS type 4 (0 - 2 047 bits) 13 - Status (16 bits, some values are reserved in EN 300 392-2 [2]) <message index> It has the range 0 - 65,535. <SDS status > 0 - Incoming message stored and unread 1 - Incoming message stored and read 2 - Outgoing message stored and unsent 3 - Outgoing message stored and sent <calling party ident> A digit stream to be interpreted dependant on the value of <calling party type>.The presentation shall be in ASCII. <calling party ident type> 0 - SSI(default) 1 - TSI 2 - Reserved 3 - PABX external subscriber number

PEI Users Guide


4 - PSTN external subscriber number <called party ident> A digit stream to be interpreted dependant on the value of <called party type>.The presentation shall be in ASCII. <called party ident type> 0 - SSI(default) 1 - TSI 2 - Reserved 3 - PABX external subscriber number 4 - PSTN external subscriber number Example : AT+CMGL=0,1,0,1,,0,1,1234,0,<cr> <cr><lf>OK<cr><lf>

PEI Users Guide


11.1.23. +CMGR: Read message

Description The set command reads the message from the message stack <AI service> at all given storage locations <message index>. If no message index is given then all messages of the defined SDS type will be read. If <AI service> is "status" or SDS type 1 then the TE may associate the value read with a text string downloaded from the MT previously with a "CSTR" command. Responses +CMGR: <AI service>, <message index>, <SDS status>, <stack full>[, <calling party ident>] [, <calling party identtype>] [, [<called party ident>], [<calling party ident type>] [, <area> [, <SwMI time>]]]], <length><CR><LF>userdata. ExecutionSyntax +CMGR=<AI service>, [<message index>,] [<message index>] Set Syntax N/A Read Syntax N/A Test Syntax AT+CMGR=? Defined Values <AI service> 0 - TETRA speech(default) 1 - 7,2 kbit/s unprotected data 2 - Low protection 4,8 kbit/s short interleaving depth = 1 3 - Low protection 4,8 kbit/s medium interleaving depth = 4 4 - Low protection 4,8 kbit/s long interleaving depth = 8 5 - High protection 2,4 kbit/s short interleaving depth = 1 6 - High protection 2,4 kbit/s medium interleaving depth = 4 7 - High protection 2,4 kbit/s high interleaving depth = 8 8 - Packet Data 9 - SDS type 1 (16 bits) 10 - SDS type 2 (32 bits) 11 - SDS type 3 (64 bits) 12 - SDS type 4 (0 - 2 047 bits) 13 - Status (16 bits, some values are reserved in EN 300 392-2 [2]) <message index> It has the range 0 - 65,535. <SDS status > 0 - Incoming message stored and unread 1 - Incoming message stored and read 2 - Outgoing message stored and unsent 3 - Outgoing message stored and sent <stack full> 0 - Stack not full(default) 1 - Stack full. <calling party ident> A digit stream to be interpreted dependant on the value of <calling party type>.The presentation shall be in ASCII. <calling party ident type>

PEI Users Guide


0 - SSI(default) 1 - TSI 2 - Reserved 3 - PABX external subscriber number 4 - PSTN external subscriber number <called party ident> A digit stream to be interpreted dependant on the value of <called party type>.The presentation shall be in ASCII. <called party ident type> 0 - SSI(default) 1 - TSI 2 - Reserved 3 - PABX external subscriber number 4 - PSTN external subscriber number <Area> 0 - Area not defined 1 - Area 1 2 - Area 2 3 - Area 3 4 - Area 4 5 - Area 5 6 - Area 6 7 - Area 7 8 - Area 8 9 - Area 9 10 - Area 10 11 - Area 11 12 - Area 12 13 - Area 13 14 - Area 14 15 - All areas <length> This parameter indicates the length of the "user data" field in SDS related commands. The length is given in ASCII decimal. <user data> In AT commands the user data is defined by a combination of two parameters: A "length" parameter and the user data itself. The length parameter can be identified as the one before the <CR><LF> characters (useful in the event of optional parameters not present on the command line). The user data is after the <CR><LF> characters and before either a <CtrlZ> or <ESC> character. The <CtrlZ> character is used to "send" the data; the <ESC> character may be used to cancel the command. The cancel functionality is included to enable cancellation of sending in the event of manual entering of commands, where the operator may have made a typing mistake. The length parameter gives the length of the user data in bits (excluding the <CR>, <LF> and <CtrlZ> characters) represented as ASCII Decimal. Whilst the length parameter is not strictly necessary for all except SDS type 4 it is made mandatory for consistency and MT sanity checking of the other data types (status, SDS types 1-3). The user data itself is represented as ASCII Hex characters. Coding starts at the MS bit; each block of four bits is represented by one character; the characters are presented in the same order as the bits themselves. If the number of bits is not divisible by four, then the least significant bits of the least significant Hex digit are packed with "0". For example, for a data field of "1010 0101 1011 1": - The length will be "13". - The user data will be "A5B8". -The relevant part of a command line to send this data will be 13<CR><LF>A5B8<CtrlZ>.

PEI Users Guide


11.1.24. +CMGS: Send message

Description The command will send a data message to the MT over the PEI. The SDS type (<AI service>, <area> , <e-to-e encryption>, <access priority> and <called party ident type> relating to the message shall have been set with a previous +CTSDS command. If necessary, the required operating mode, V+D or DMO, shall have been set with a previous +CTOM command. Although only SDS type 4 has variable length the length field is mandatory for consistency and gives the MT a means for checking the current <AI service> field. Responses +CMGS: <SDS Instance>[, <SDS status> [, <transmit attempts>, <transmit power>]] Syntax +CMGS= <called party ident >, <length><CR> <LF>user data<CtrlZ>/<ESC> +CMGS= ? Defined Values <SDS Instance> A two-digit number identifying a particular SDS message in sending of Status and SDS messages without using the stack. The originating MT assigns this number. The number will be assigned at the beginning of any particular message sending and used to relate all PEI signalling related to that message sending. <SDS status> 0 - Incoming message stored and unread 1 - Incoming message stored and read 2 - Outgoing message stored and unsent 3 - Outgoing message stored and sent <transmit attempts> Reports the number of times the SDS was transmitted before success (or failure). <transmit power> The Rf power in dB used to transmit the SDS (during the final transmission of <transmit attempts> is greater than 1 <called party ident > A digit stream to be interpreted dependant on the value of <called party type>.The presentation shall be in ASCII. <length> This parameter indicates the length of the "user data" field in SDS related commands. The length is given in ASCII decimal. <user data> In AT commands the user data is defined by a combination of two parameters: A "length" parameter and the user data itself. The length parameter can be identified as the one before the <CR><LF> characters (useful in the event of optional parameters not present on the command line). The user data is after the <CR><LF> characters and before either a <CtrlZ> or <ESC> character. The <CtrlZ> character is used to "send" the data; the <ESC> character may be used to cancel the command. The cancel functionality is included to enable cancellation of sending in the event of manual entering of commands, where the operator may have made a typing mistake. The length parameter gives the length of the user data in bits (excluding the <CR>, <LF> and <CtrlZ> characters) represented as ASCII Decimal. Whilst the length parameter is not strictly necessary for all except SDS type 4 it is made mandatory for consistency and MT sanity checking of the other data types (status, SDS types 1-3). The user data itself is represented as ASCII Hex characters. Coding starts at the MS bit; each block of four bits is represented by one character; the characters are presented in the same order as the bits themselves. If the number of bits is not divisible by four, then the least significant bits of the least significant Hex digit are packed with "0".

PEI Users Guide


For example, for a data field of "1010 0101 1011 1": - The length will be "13". - The user data will be "A5B8".

- The relevant part of a command line to send this data will be 13<CR><LF>A5B8<CtrlZ>.

- Example : <cr><lf>AT+CMGS: 1,9,1<cr><lf>

PEI Users Guide


11.1.24.1. SDS Examples

The AT+CMGS command allows either a Status Message or a Short Data Message to be sent from PEI. The parameters for the sending of the messages over the TETRA air interface are set up using the command AT+CTSDS

Set Data Message Parameters Command

AI Service Called Party Identity Type

Area Access Priority End to end encryption

AT+CTSDS 13 0 0 0 0

Send Message Command

Destination Identity

Data Length Status Number

AT+CMGS XXXXXXXX NNN<CRLF> SSSS

Where, The identity can be 1 to 8 digits in length The data length is the number of bits of user data and is always 16 for a Status Message. The Status Number is exactly 4 ASCII Hexadecimal digits, with a valid range from 0000 to FFFF. Note that the status values 1 to 32743 (7BFF Hex) are reserved by the TETRA standard, 31744 to 32767 (7C00 to 7FFF Hex) are for use by SDS-TL and 32768 to 65535 (8000 to FFFF Hex) are available for TETRA network and user specific definitions. After sending a Status Message, some TETRA Infrastructures will send a Status Message Acknowledgement. The most common Infrastructure status messages you might see are in the table below-

Status Meaning

FE00 Status Message Delivered

FE01 Status Negative Acknowledgement (Most likely the Message has failed)

Please refer to your TETRA Infrastructure supplier for exact operation details of these status message acknowledgements.

11.1.24.1.1. Status Message Transmission Example

The following sequence shows how a status message is transmitted at+ctsds=13,0,0,0,0,0 OK at+cmgs=607501,16 80e8 OK +CMGS:2,3

11.1.24.1.2. Status Message Reception Example

The following shows how a Status message is received +CMTI:13,1,0 80E8

PEI Users Guide


11.1.24.1.3. Simple SDS-TL protocol transmission example

The following example demonstrates how to send a SDS Message of “Hello” using the simple text PID to SSI address 607502: AT+CTSDS=12,0,0,0,0<CR><LF> <CR><LF> OK<CR><LF> AT+CMGS=607501,56<CR><LF> 020148656C6C6F<cntlZ> <CR><LF> OK<CR><LF> +CMGS:3,3 The user data in this message is constructed as follows: 02 = PID (2 decimal) 01 = Latin-1 alphabet 48 = ‘H’ 65 = ‘e’ 6C = ‘l’ 6C = ‘l’ 6F = ‘o’ <cntlZ> terminates the user data

11.1.24.1.4. Simple SDS-TL protocol reception example

Using the example above when an SDS-TL transfer message is received by the terminal, it will be presented at the PEI as follows: +CMTI:12,2,0 <CR><LF> 020148656C6C6F <CR><LF>

PEI Users Guide


11.1.25. +CNUM: Get MT TETRA Identities

Description The response to this command returns the TETRA subscriber identity number programmed in the MT. If there is more than one number stored in the MT then each number will be returned on a separate line. Their will always be an individual number returned but additional address such as group will very. The number type variable is different from the “called party type” as it can distinguish groups, gateways, external subscriber numbers. Execution Syntax N/A Set Syntax N/A Read Syntax AT +CNUM? Test Syntax AT +CNUM=? Responses +CNUM: <Num type>,<Called Party Identity>[,<alpha>]<CR><LF> [<Num type>[,<Called Party Identity>[,<alpha>]]] Defined Values <Num type> 0 - Individual 1 - Group 2 - PSTN Gateway 3 - PABX Gateway 4 - Service Centre (ITSI) 5 - Service Centre (E 164 number) <Called Party Identity> A digit stream to be interpreted dependant on the value of <called party type>.The presentation shall be in ASCII. <alpha> Optional alphanumeric string used to help MMI for TETRA identities returned with the CNUM command. Not used in current application. Test Response <cr><lf>OK<cr><lf> Example : AT+CNUM?<cr> <cr><lf>+CNUM: 0,234710000020550,<cr><lf> 1,234710000080001,<cr><lf> 1,234710000080002,<cr><lf> 2,234710000010001<cr><lf> 3,234710000010000<cr><lf> <cr><lf>OK<cr><lf>

PEI Users Guide


11.1.26. +CREG: Network Registration

Description The set command controls the sending of an unsolicited result code by the value of <reg unsolic>, typically reported when there is a change in the MT network Registration status or location area. If a state of CREG:999 is reported this is a special case to indicate that the radio has been programmed with incorrect software. A radio will only support one encryption algorithm (TEA1, TEA2 or TEA3) if the software for the wrong algorithm is programmed in to a radio if will not function but will report CREG:999. The correct software needs to be re-programmed before the radio will function again. Execution Syntax N/A Set Syntax

AT +CREG =<Reg unsolic> Read Syntax AT +CREG? Test Syntax AT +CREG=? Responses +CREG: <Reg stat>,<Reason>,<Enable State> +CREG: 88,<Scan State>,<Registration Reject Cause> +CREG :999 Defined Values < Reg unsolic > 0 Disable network registration unsolicited result codes 1 Enable network registration unsolicited result codes on status change 2 Enable network registration unsolicited result codes on every location area change <Reg stat> 0 Not registered or searching 1 Registered home network 2 In service waiting for first registration 88 Used during first registration to report the scanning state and any registration failure reason <Cell Reselection Reason> 0 Normal cell reselection 1 Radio downlink counter (RDC) timeout 2 Lost synchronisation on downlink channel 3 Pathloss went below zero 4 Maximum path length exceeded <Enable/Disable State> 0 Radio currently enabled in the TETRA network 1 Radio has been temporarily disabled by the TETRA network 2 Radio has been permanently disabled by the TETRA network (can only be re-enabled by

returning to Piciorgros) <Scan State> 0 Channel scan starting 1 RF Carrier found 2 Synchronised with and RF carrier 3 Subscriber class match with cell on a carrier 4 MCC/MNC checked 5 Registration Rejected (check the rejected cause in next parameter)

PEI Users Guide


<Registration Reject Cause> (only valid with a CREG:88,5, <Registration Reject Cause> message) 0 ITSI Unknown 1 Illegal MS 2 Location area ot allowed 3 Location area ot known 4 Network failure 5 Congestion 6 Forward registration failure 7 Service not allowed 8 Mandatory element error 9 Message consistency error 10 Roaming not supported 11 Migration not supported 12 No cipher KSG 13 Identified cipher KSG not supported 14 Requested cipher key not available 15 Identified cipher key not available 16 Ciphering required 17 Authentication failure Example AT+CREG?<CR> <cr><lf>+CREG: 1,0,0<cr><lf> <cr><lf>OK<cr><lf>

PEI Users Guide


11.1.27. +CTOM : Set Operating Mode

Description It is specific to TETRA and is used in conjunction with (before) other commands that perform configuration, outgoing TETRA call set up, and sending of both TETRA STATUS and SDS messages. The command operates in test, set and read modes. The default dor this command is V+D mode. Execution Syntax N/A Set Syntax AT +CTOM=<AI mode> Read Syntax AT +CTOM=? Test Syntax AT +CTOM? Defined Values < AI mode >

� 0 - V+D (trunked mode operation);

� 1 - DMO;

� 2 - V+D with dual watch of DMO; ( Not supported)

� 3 - DMO with dual watch of V+D; ( Not supported)

� 4 - V+D and DMO ( Not supported)

Example AT+CTOM?<CR> <cr><lf>+CTOM: 1<cr><lf> <cr><lf>OK<cr><lf>

PEI Users Guide


11.1.28. + CTGS: Group Set Up

Description Configures groups in the terminal to be selected or scanned. When this command is set, all existing group attachments in the terminal are removed. Execution Syntax N/A Set Syntax AT +CTGS=<group type>,<GSSI>[,<group type>,<GSSI>] Read Syntax AT +CTGS=? Test Syntax AT +CTGS=? Responses +CTGS: <group type>, < Called Party Identity><CR><LF>… [, <group type>, < Called Party Identity>] Defined Values <group type> 0 - None 1 - Select 2 - Scan priority 1 3 - Scan priority 2 4 - Scan priority 3 5 - Scan priority 4 6 - Scan priority 5 7 - Scan priority 6 < Called Party Identity> A digit stream to be interpreted dependant on the value of <called party type>.The presentation shall be in ASCII. Test Response <cr><lf>OK<cr><lf> Example : AT+CTGS?<cr> <cr><lf>+CTGS: 2,40411<cr><lf> 2,40432<cr><lf> <cr><lf>OK<cr><lf>

PEI Users Guide


11.1.29. +CSQ: Signal quality

Description This command returns the received signal strength indication <rssi> and channel bit error ratio <ber> from the MT. The RSSI is reported as a C1 pathloss value calculated using the minimum access level allowed reported by the current serving cell. If the modem has been switched into Piciorgros Extended Command mode using the AT+PIMODE=1 command +CSQ will report 4 additional parameters. The raw RSSI of the serving cell in dB <rssi raw>, the reverse power measured in the transmitter during the last transmit made by the modem <Rev Power>, the current internal temperature of the RF power amplifier <PA Temp> and the state of the PDP Context if the modem is being used for Packet Data communications <PDP State>. Execution Syntax N/A Set Syntax N/A Read Syntax AT +CSQ? Test Syntax AT +CSQ=? AT +CSQ? AT +CSQ=? Test Response <cr><lf>OK<cr><lf> Responses +CSQ: <rssi> , <ber> In extended mode (see above) +CSQ: <rssi>, <ber>, <rssi raw>, <rev power>, <PA temp>, <PDP State> Example : AT+CSQ<CR> <cr><lf>+CSQ: 89,7<cr><lf> <cr><lf>OK<cr><lf>

PEI Users Guide


11.1.30. +CTSDC: Tetra Service Definition

Description This command sets all parameters to be used on the TETRA air interface in outgoing call setup. A MT uses the parameters set with this command in subsequent call setup, after reception of subsequent dial command. Some commands are conditional on others and need not be specified. The MT should check for validity of the parameters and their combination before accepting the command. Execution Syntax N/A Set Syntax AT +CTSDC=<AI service>,<called party ident type>[,<area>,<hook>,<simplex>[,<end-to-end encryption> [,<comms_type>[,<slots/codec>[,<RqTx>[,<priority>[,<CLIR control>]]]]]]] Read Syntax AT +CTSDC? Test Syntax AT +CTSDC=? Responses AT+CTSDC=<AI service>, <called party ident type>, [<area>, <hook>, <simplex>, [<e to e encryption>, [<comms type>,[<slots/codec>, [<RqTx>, [<priority>, [<CLIR control>]]]]]]] Defined Values <AIService> 0 - TETRA speech(default) 1 - 7,2 kbit/s unprotected data 2 - Low protection 4,8 kbit/s short interleaving depth = 1 3 - Low protection 4,8 kbit/s medium interleaving depth = 4 4 - Low protection 4,8 kbit/s long interleaving depth = 8 5 - High protection 2,4 kbit/s short interleaving depth = 1 6 - High protection 2,4 kbit/s medium interleaving depth = 4 7 - High protection 2,4 kbit/s high interleaving depth = 8 8 - Packet Data 9 - SDS type 1 (16 bits) 10 - SDS type 2 (32 bits) 11 - SDS type 3 (64 bits) 12 - SDS type 4 (0 - 2 047 bits) 13 - Status (16 bits, some values are reserved in EN 300 392-2 [2]) <calling party ident type> 0 - SSI(default) 1 - TSI 2 - Reserved 3 - PABX external subscriber number 4 - PSTN external subscriber number <Area> 0 - Area not defined 1 - Area 1 2 - Area 2 3 - Area 3 4 - Area 4

PEI Users Guide


5 - Area 5 6 - Area 6 7 - Area 7 8 - Area 8 9 - Area 9 10 - Area 10 11 - Area 11 12 - Area 12 13 - Area 13 14 - Area 14 15 - All areas <hook> 0 - Hook signaling (Default) 1 - Direct. <simplex> 0 - Duplex(Default) 1 - Simplex. <e_to_e_encryption> 0 - Clear (default) 1 - Encrypted. <comms type> 0 - Point to Point (default) 1 - Point to multipoint 2 - Point to multipoint (acknowledged) 3 - Broadcast. <slots/codec> Data 0 - 1 slot 1 - 2 slots 2 - 3 slots 3 - 4 slots Speech 1 - TETRA encoded speech(default) 2 - Reserved 3 - Reserved 4 - Proprietary encoded speech <RqTx> 0 - Request to Tx(default) 1 - No Request to Tx. <priority> 0 - Priority not defined by this parameter 1 - Priority 1 2 - Priority 2 3 - Priority 3 4 - Priority 4 5 - Priority 5 6 - Priority 6 7 - Priority 7 8 - Priority 8 9 - Priority 9 10 - Priority 10 (Default) 11 - Priority 11 12 - Priority 12 13 - Priority 13

PEI Users Guide


14 - Priority 14 15 - Priority 15 <CLIR control> Not used in the current implementation Defaults <AI service> 0 Tetra Speech <Called party identity type> 0 SSI <Area> 0 Area not defined <hook> 0 hook signalling <simplex> 0 Duplex <End to end encryption> 0 Clear <comms type> 0 Point to point <slots/codec> 1 Tetra encoded speech <RqTx> 0 Request to Transmit with simplex call setup <priority> 0 Priority not defined Test Response Syntax +CTSDC: (list of AI services),(list of called party ident types),(list of areas),(list of hook values),(list of simplex values),(list of e-e encryption values),(list of comms type values),(list of slots/codec values),(List of RqTx values),(list of priority values),(list of CLIR control values)<cr><lf> <cr><lf>OK<cr><lf> Test Response +CTSDC: (0-2,5),(0,3-4),(0),(0-1),(0-1),(0),(0-1),(0-1),(0-1),(0-15),()<cr><lf> <cr><lf>OK<cr><lf> Example : AT+CTSDC=1,0,0,0,0,0,0,0<cr> <cr><lf>OK<cr><lf>

PEI Users Guide


11.1.31. +CTSDS: Tetra Service Definition for SDS Service

Description This command sets parameters to be used on the TETRA air interface in outgoing Status and SDS messaging. The MT uses the parameters set with this command in subsequent SDS sending commands, either directly or via a message stack. The MT should check for validity of the parameters and their combination before accepting the command. Execution Syntax N/A Set Syntax AT+CTSDS=<AI service>, <called party ident type>[, <area>[, <access priority> [, <e-to-e encryption>]]] Read Syntax

AT+CTSDS? Test Syntax AT+CTSDS=? Response +CTSDS: <AI service>,<called party ident type>[,<area>[,<access priority>[,<end-to-end encryption>]]] Defined Values <AIService> 0 - TETRA speech(default) 1 - 7,2 kbit/s unprotected data 2 - Low protection 4,8 kbit/s short interleaving depth = 1 3 - Low protection 4,8 kbit/s medium interleaving depth = 4 4 - Low protection 4,8 kbit/s long interleaving depth = 8 5 - High protection 2,4 kbit/s short interleaving depth = 1 6 - High protection 2,4 kbit/s medium interleaving depth = 4 7 - High protection 2,4 kbit/s high interleaving depth = 8 8 - Packet Data 9 - SDS type 1 (16 bits) 10 - SDS type 2 (32 bits) 11 - SDS type 3 (64 bits) 12 - SDS type 4 (0 - 2 047 bits) 13 - Status (16 bits, some values are reserved in EN 300 392-2 [2]) <called party ident type> 0 - SSI(default) 1 - TSI 2 - Reserved 3 - PABX external subscriber number 4 - PSTN external subscriber number <Area> 0 - Area not defined 1 - Area 1 2 - Area 2 3 - Area 3 4 - Area 4 5 - Area 5 6 - Area 6 7 - Area 7 8 - Area 8 9 - Area 9 10 - Area 10 11 - Area 11

PEI Users Guide


12 - Area 12 13 - Area 13 14 - Area 14 15 - All areas <access priority> 0 - Low

1 - High

2 - Emergency

<e_to_e_encryption> 0 - Clear (default) 1 - Encrypted. Test Response Syntax +CTSDS: (list of AI services),(list of called party ident types),(list of areas),(list of access priorities), (list of e-e encryption values)<cr><lf> <cr><lf>OK<cr><lf> Test Response +CTSDS: (12-13),(0),(0),(0-2),(0)<cr><lf> <cr><lf>OK<cr><lf> Example : AT+CTSDS=12,0,0,0,0<cr> <cr><lf>+CTSDS: <cr><lf> <cr><lf>OK<cr><lf>

PEI Users Guide


11.1.32. +CTSTR: Tetra Status Text Read.

Description The TE uses this command to retrieve text string stored in the MT memories. Status and SDS type 1 in particular have text String associate with them, which have meaning to a particular user or application. The TE would typically use this command at link recovery. Then the text string looked up by the TE when reading SDS messages would be used in preference to the numeric value indicated in the <index> field. Execution Syntax N/A Set Syntax AT+CTSDS=<AI service>, <called party ident type>[, <area>[, <access priority> [, <e-to-e encryption>]]] Read Syntax

AT+CTSDS? Test Syntax N/A Read Syntax AT+CTSTR=<AI Service> Responses +CTSTR:<AI service>,<index>,<text><CR><LF> <index>,<text><CR><LF> Defined Values <AIService> 0 - TETRA speech(default) 1 - 7,2 kbit/s unprotected data 2 - Low protection 4,8 kbit/s short interleaving depth = 1 3 - Low protection 4,8 kbit/s medium interleaving depth = 4 4 - Low protection 4,8 kbit/s long interleaving depth = 8 5 - High protection 2,4 kbit/s short interleaving depth = 1 6 - High protection 2,4 kbit/s medium interleaving depth = 4 7 - High protection 2,4 kbit/s high interleaving depth = 8 8 - Packet Data 9 - SDS type 1 (16 bits) 10 - SDS type 2 (32 bits) 11 - SDS type 3 (64 bits) 12 - SDS type 4 (0 - 2 047 bits) 13 - Status (16 bits, some values are reserved in EN 300 392-2 [2])

PEI Users Guide


11.1.33. +CTXD: Transmit Demand

Description This command is specific to TETRA and is based on the U-TxDemand message. In a simplex call this command is used in conjunction with the transmission grant response to control the transmissions of the MT. The TE will generate this command on pressing of the MMI representing the PTT. Execution Syntax N/A Set Syntax AT+CTXD= <CC instance > [,<e to e encryption>] Read Syntax N/A Test Syntax AT+CTXD=? Responses OK

Defined Values <CC instance> A three-digit number used to identify an ongoing call. The originating MT assigns it. The number will be assigned at the beginning of any particular call (incoming or outgoing) and used to relate all PEI signalling related to that call. <e_to_e_encryption> 0 - Clear (default) 1 - Encrypted. Test Response Syntax +CTXD: (list of CC instance values), (list of e-e encryption values)<cr><lf> <cr><lf>OK<cr><lf> Test Response +CTXD: (0-999),(0)<cr><lf> <cr><lf>OK<cr><lf> Example : AT+CTXD=112,1<cr> <cr><lf>OK<cr><lf>

PEI Users Guide


11.1.34. +CUTXC: Up Transmit Ceased.

Description This command is specific to TETRA and is based on the U-TxCeased message. In a simplex call this command is used in conjunction with the transmission grant response to control the transmissions. The TE will generate this command on release of the MMI representing the PTT. Execution Syntax N/A Set Syntax AT+CUTXC= <CC instance > Read Syntax N/A Test Syntax AT+CUTXC= ? Responses +CUTXC: (list of CC instance values)<cr><lf> <cr><lf>OK<cr><lf> Defined Values <CC instance> A three-digit number used to identify an ongoing call. The originating MT assigns it. The number will be assigned at the beginning of any particular call (incoming or outgoing) and used to relate all PEI signalling related to that call. Test Response Syntax +CUTXC: (list of CC instance values)<cr><lf> <cr><lf>OK<cr><lf> Test Response +CUTXC: (0-999)<cr><lf> <cr><lf>OK<cr><lf> Example : AT+CTXD=112,1<cr> <cr><lf>OK<cr><lf> AT+CUTXC=112 <cr><lf>OK<cr><lf> AT+CUTXC=112 <cr><lf>CME ERROR: 3<cr><lf>

PEI Users Guide


11.1.35. +GCAP: Request complete capabilities list

Description The different services and MS capabilities related to TETRA are added to the response. Execution Syntax N/A Set Syntax N/A Read Syntax +GCAP? Responses +GCAP: TETRA [, <class of MS>[, <stack present> [<CR><LF>[, <service layer1>[, <service layer2>[, PID<CR><LF>]]]]]]] <class of MS> This parameter is used to indicate to the TE the capabilities of the MS regarding air interface characteristics. The value sent in the command line string will be the HEX equivalent of the total bit array. For example a MS capable of all services except security will have the parameter value "FFFF00". <stack present> 0 - SDS Stack present (default) 1 - SDS Stack not present. <service layer1> This parameter is used to indicate the MS capabilities and to set profiles directing services to and from the TE and/or MT. Each one is split into "layer2" sub-parameters. 0 - CC 1 - MM 2 - SDS 3 - SDS-TL 4 - Packet Data. <service layer2> This parameter is used (in conjunction with "service layer1" to indicate the MS capabilities and to set profiles directing services to and from the TE and/or MT. 0 - Voice 1 - Data 2 - 9 Reserved 10 - Registration 11 - Group Management 12 - Security 13 - Enable 14 - Energy saving 15 - 19 Reserved 20 - Status 21 - SDS type 1 22 - SDS type 2 23 - SDS type 3 24 - SDS type 4 (not SDS-TL) 25 - 29 Reserved 30 - PV4 31 - IPV6 32 - 39 Reserved

PEI Users Guide


11.1.36. +GMI : Request manufacturer identification

Description This command causes the MT to transmit one or more lines of information text, which is intended to permit the user of the MT to identify the manufacturer. Typically, the text will consist of a single line containing the name of the manufacturer, and information like address, telephone number for customer service, etc. The total number of characters, including line terminators, in the information text returned in response to this

command will not exceed 2048 characters. The information text will not contain the sequence "0 <CR>or

"OK<CR>" so that TE can avoid false detection of the end of this information text. Execution Syntax AT+GMI Set Syntax N/A Read Syntax N/A Test Syntax AT +GMI=? Response +GMI: Piciorgros GmbH Test Response <cr><lf>OK<cr><lf> Implementation The result string is presently set as “Piciorgros GmbH”.

PEI Users Guide


11.1.37. +GMM : Request model identification

Description This command causes the MT to transmit one or more lines of information text, which is intended to permit the user of the MT to identify the specific model of device. Typically, the text will consist of a single line containing the name of the product. The total number of characters, including line terminators, in the information text returned in response to this command will not exceed 2048 characters. Note that the information text will not contain the sequence "0

<CR>" or "OK<CR>" , so that TE can avoid false detection of the end of this information text. Execution Syntax AT+GMM Set Syntax N/A Read Syntax N/A Test Syntax AT +GMM=? Response +GMM: TMC-210 Implementation The result string is set as “TMC-210” Test Response <cr><lf>OK<cr><lf> Example : AT+GMM<cr> <cr><lf>+GMM: TMC-210<cr><lf> <cr><lf>OK<cr><lf>

PEI Users Guide


11.1.38. +GMR : Request revision identification

Description This command causes the MT to transmit one or more lines of information text, which is intended to permit the user of the MT to identify the version, revision level or date, or other pertinent information of the device. Typically, the text will consist of a single line containing the version of the product, The total number of characters, including line terminators, in the information text returned in response to this command will not

exceed 2048 characters. Note that the information text will not contain the sequence "0 <CR>" or "OK<CR>" , so that TE can avoid false detection of the end of this information text. Execution Syntax AT+GMR Set Syntax N/A Read Syntax N/A Test Syntax AT+GMR=? Responses Returns revision identification followed by OK. Implementation The result string is presently set as the version string of the MicroC_OS image”. Test Response <cr><lf>OK<cr><lf> Example : AT+GMR<cr> <cr><lf>B097<cr><lf> <cr><lf>OK<cr><lf>

PEI Users Guide


11.1.39. +CMCC : Mobile Network Code

Description This command from the TE returns the Mobile Country Code (MCC). This command supports test and read modes. The MNC is returned as a value of 10 bits Execution Syntax AT+CMCC Set Syntax N/A Read Syntax N/A Test Syntax AT+CMCC=? Responses Returns MCC followed by OK. Implementation The result string is presently read from the flashed value of MCC Test Response <cr><lf>OK<cr><lf> Example : AT+CMCC<cr> <cr><lf>234<cr><lf> <cr><lf>OK<cr><lf>

PEI Users Guide


11.1.40. +CMNC : Mobile Network Code

Description This command from the TE returns the Mobile Network Code (MNC). This command supports test and read modes. The MNC is returned as a value of 14 bits. Execution Syntax AT+CMNC Set Syntax N/A Read Syntax N/A Test Syntax AT+CMNC=? Responses Returns MNC followed by OK. Implementation The result string is presently read from the flashed value of MNC Test Response <cr><lf>OK<cr><lf> Example : AT+CMNC<cr> <cr><lf>77<cr><lf> <cr><lf>OK<cr><lf>

11.1.41. +CCHN: Main Control Channel

Description This command from the TE returns the identity of the Main Control Channel (MCCH).This command supports test and read modes. The MNC is returned as a value of 3 digits. Execution Syntax AT+CMNC Set Syntax N/A Read Syntax N/A Test Syntax AT+CCHN=? Responses Returns CHN followed by OK. Test Response <cr><lf>OK<cr><lf> Example : AT+CCHN<cr> <cr><lf>77<cr><lf> <cr><lf>OK<cr><lf>

PEI Users Guide


11.1.42. +CLAI: Serving Cell Location Area ID

Description This command from the TE returns the serving cell location area (LA) ID. The LAis returned as a value of 14 bits Execution Syntax AT+CLAI Set Syntax N/A Read Syntax N/A Test Syntax AT+CLAI=? Responses Returns LA followed by OK. Test Response <cr><lf>OK<cr><lf> Example : AT+CLAI<cr> <cr><lf>2<cr><lf> <cr><lf>OK<cr><lf>

11.1.43. +CNLA: Neighbour Cell Location Area ID

Description This command from the TE returns the neighbour cell location area (LA) ID. The LA is returned as a value of 14 bits Execution Syntax AT+CNLA Set Syntax N/A Read Syntax N/A Test Syntax AT+CNLA=? Responses Returns LA followed by OK. Test Response <cr><lf>OK<cr><lf> Example : AT+CNLA<cr> <cr><lf>2<cr><lf> <cr><lf>OK<cr><lf>

PEI Users Guide


11.2. Unsolicited Responses

11.2.1. +CMTI: New message indication

Description An unsolicited result code to indicate a new message has been put on the message stack. The parameters indicate the

type of SDS and the location on the stack.

Syntax An unsolicited result code. So no Set Syntax.

Responses +CMTI <AI service>, <message index>[, <stack full>], <CR> <LF>user data.

Defined Values <AI service> 0 - TETRA speech(default) 1 - 7,2 kbit/s unprotected data 2 - Low protection 4,8 kbit/s short interleaving depth = 1 3 - Low protection 4,8 kbit/s medium interleaving depth = 4 4 - Low protection 4,8 kbit/s long interleaving depth = 8 5 - High protection 2,4 kbit/s short interleaving depth = 1 6 - High protection 2,4 kbit/s medium interleaving depth = 4 7 - High protection 2,4 kbit/s high interleaving depth = 8 8 - Packet Data 9 - SDS type 1 (16 bits) 10 - SDS type 2 (32 bits) 11 - SDS type 3 (64 bits) 12 - SDS type 4 (0 - 2 047 bits) 13 - Status (16 bits, some values are reserved in EN 300 392-2 [2]) <message index> It has the range 0 - 65,535. <stack full> 0 - Stack not full(default) 1 - Stack full. <user data> In AT commands the user data is defined by a combination of two parameters: A "length" parameter and the user data itself. The length parameter can be identified as the one before the <CR><LF> characters (useful in the event of optional parameters not present on the command line). The user data is after the <CR><LF> characters and before either a <CtrlZ> or <ESC> character. The <CtrlZ> character is used to "send" the data; the <ESC> character may be used to cancel the command. The cancel functionality is included to enable cancellation of sending in the event of manual entering of commands, where the operator may have made a typing mistake. The length parameter gives the length of the user data in bits (excluding the <CR>, <LF> and <CtrlZ> characters) represented as ASCII Decimal. Whilst the length parameter is not strictly necessary for all except SDS type 4 it is made mandatory for consistency and MT sanity checking of the other data types (status, SDS types 1-3). The user data itself is represented as ASCII Hex characters. Coding starts at the MS bit; each block of four bits is represented by one character; the characters are presented in the same order as the bits themselves. If the number of bits is not divisible by four, then the least significant bits of the least significant Hex digit are packed with "0". For example, for a data field of "1010 0101 1011 1": - The length will be "13". - The user data will be "A5B8".

- The relevant part of a command line to send this data will be 13<CR><LF>A5B8<CtrlZ>.

PEI Users Guide


11.2.2. +CTICN: Tetra Incoming call progress.

Description This unsolicited response is specified to TETRA and is based on the TETRA set-up, Connect Ack and D_Info Messages. it indicates an incoming call and its progress to the TE. The TE uses the parameters set with this command to interpret how to handle the call. Responses +CTICN:<CC instance>,<call status>,<AI Service>,[,<calling party ident type>[,<ident>[,<hook>[,<simplex>[,<e_to_e_encryption>[<comms type>,[,<slots/codec>]]]]]]

Syntax It is an unsolicited response from MT. Defined Values <CC instance> A three-digit number used to identify an ongoing call. The originating MT assigns it. The number will be assigned at the beginning of any particular call (incoming or outgoing) and used to relate all PEI signalling related to that call. <call_status> 0 - Call progressing(default) 1 - Call queued 2 - Called party paged 3 - Call continue 4 - Hang time expired <AIService> 0 - TETRA speech(default) 1 - 7,2 kbit/s unprotected data 2 - Low protection 4,8 kbit/s short interleaving depth = 1 3 - Low protection 4,8 kbit/s medium interleaving depth = 4 4 - Low protection 4,8 kbit/s long interleaving depth = 8 5 - High protection 2,4 kbit/s short interleaving depth = 1 6 - High protection 2,4 kbit/s medium interleaving depth = 4 7 - High protection 2,4 kbit/s high interleaving depth = 8 8 - Packet Data 9 - SDS type 1 (16 bits) 10 - SDS type 2 (32 bits) 11 - SDS type 3 (64 bits) 12 - SDS type 4 (0 - 2 047 bits) 13 - Status (16 bits, some values are reserved in EN 300 392-2 [2]) <calling party ident type> 0 - SSI(default) 1 - TSI 2 - Reserved 3 - PABX external subscriber number 4 - PSTN external subscriber number <calling party ident> A digit stream to be interpreted dependant on <calling party type>. The presentation shall be in ASCII. <hook> 0 - Hook signaling (Default) 1 - Direct. <simplex> 0 - Duplex(Default) 1 - Simplex.

PEI Users Guide


<e_to_e_encryption> 0 - Clear (default) 1 - Encrypted. <comms type> 0 - Point to Point (default) 1 - Point to multipoint 2 - Point to multipoint (acknowledged) 3 - Broadcast. <slots/codec> Data 0 - 1 slot 1 - 2 slots 2 - 3 slots 3 - 4 slots Speech 1 - TETRA encoded speech(default) 2 - Reserved 3 - Reserved 4 - Proprietary encoded speech

PEI Users Guide


11.2.3. +CTSDSR: Unsolicited SDS indication

This is an unsolicited message that carries an incoming SDS message from a MT. The command operates in test and read modes. Syntax +CTSDSR: <AI service>, [<calling party identity>], [<calling party identity type>], <called party identity>, <called party identity type>, <length>, [<end to end encryption>]<CR><LF>user data Defined Values <AIService> 0 - TETRA speech(default) 1 - 7,2 kbit/s unprotected data 2 - Low protection 4,8 kbit/s short interleaving depth = 1 3 - Low protection 4,8 kbit/s medium interleaving depth = 4 4 - Low protection 4,8 kbit/s long interleaving depth = 8 5 - High protection 2,4 kbit/s short interleaving depth = 1 6 - High protection 2,4 kbit/s medium interleaving depth = 4 7 - High protection 2,4 kbit/s high interleaving depth = 8 8 - Packet Data 9 - SDS type 1 (16 bits) 10 - SDS type 2 (32 bits) 11 - SDS type 3 (64 bits) 12 - SDS type 4 (0 - 2 047 bits) 13 - Status (16 bits, some values are reserved in EN 300 392-2 [2]) <calling party ident> A digit stream to be interpreted dependant on the value of <calling party type>.The presentation shall be in ASCII. <calling party ident type> 0 - SSI(default) 1 - TSI 2 - Reserved 3 - PABX external subscriber number 4 - PSTN external subscriber number <called party ident> A digit stream to be interpreted dependant on the value of <called party type>.The presentation shall be in ASCII. <called party ident type> 0 - SSI(default) 1 - TSI 2 - Reserved 3 - PABX external subscriber number 4 - PSTN <length> This parameter indicates the length of the "user data" field in SDS related commands. The length is given in ASCII decimal. < end to end encryption > 0 - Clear (default) 1 - Encrypted.

PEI Users Guide


11.2.4. +CTOCP: Tetra Outgoing Call Progress.

Description This response gives an indication to the TE as to the progress of an outgoing call. It is specific to TETRA and is based on the Call-Proceeding, D-Alert, D-Connect, D-Connect Ack and D-Info messages. The reception by the MT of one of these air interface messages will result in this PEI message. All parameters are subject to change by the SwMI in the course of a call set up so the TE should check their values even though it set them in the CTSD command. Responses +CTOCP: <CC instance >, <call status>, <AI service>, [<hook> [,<simplex> [,<e to e encryption> [,<comms type> [,<slots/codec> ]]]] Syntax It is an Unsolicited response from MT. Defined Values <CC instance> A three-digit number used to identify an ongoing call. The originating MT assigns it. The number will be assigned at the beginning of any particular call (incoming or outgoing) and used to relate all PEI signalling related to that call. <call_status> 0 - Call progressing(default) 1 - Call queued 2 - Called party paged 3 - Call continue 4 - Hang time expired <AIService> 0 - TETRA speech(default) 1 - 7,2 kbit/s unprotected data 2 - Low protection 4,8 kbit/s short interleaving depth = 1 3 - Low protection 4,8 kbit/s medium interleaving depth = 4 4 - Low protection 4,8 kbit/s long interleaving depth = 8 5 - High protection 2,4 kbit/s short interleaving depth = 1 6 - High protection 2,4 kbit/s medium interleaving depth = 4 7 - High protection 2,4 kbit/s high interleaving depth = 8 8 - Packet Data 9 - SDS type 1 (16 bits) 10 - SDS type 2 (32 bits) 11 - SDS type 3 (64 bits) 12 - SDS type 4 (0 - 2 047 bits) 13 - Status (16 bits, some values are reserved in EN 300 392-2 [2]) <hook> 0 - Hook signalling (Default) 1 - Direct. <simplex> 0 - Duplex(Default) 1 - Simplex. <e_to_e_encryption> 0 - Clear (default) 1 - Encrypted. <comms type> 0 - Point to Point (default) 1 - Point to multipoint

PEI Users Guide


2 - Point to multipoint (acknowledged) 3 - Broadcast. <slots/codec> Data 0 - 1 slot 1 - 2 slots 2 - 3 slots 3 - 4 slots Speech 1 - TETRA encoded speech(default) 2 - Reserved 3 - Reserved 4 - Proprietary encoded speech

11.2.5. +CTCR: Tetra Call Release.

Description This response is specific to TETRA and is based on the D-Release message. It indicates to the TE that either the other party or the network has cleared an ongoing call. Responses +CTCR: <CC instance >, <disconnect cause> Syntax It is an unsolicited response from MT. Defined Values <CC instance > A three-digit number used to identify an ongoing call. The originating MT assigns it. The number will be assigned at the beginning of any particular call (incoming or outgoing) and used to relate all PEI signalling related to that call. <disconnect cause> 0 - Not defined or unknown 1 - User request 2 - Called party busy 3 - Called party not reachable 4 - Called party does not support encryption 5 - Network congestion 6 - Not allowed traffic 7 - Incompatible traffic 8 - Service not available 9 - Pre-emption 10 - Invalid call identifier 11 - Called party rejection 12 - No CC entity 13 - Timer expiry 14 - SwMI disconnect 15 - No acknowledgement 16 - Unknown TETRA identity 17 - Sublementary Service dependent 18 - Unknown external subscriber number 19 - Call restoration failed

PEI Users Guide


11.2.6. +CTXG: Transmission Grant.

Description This unsolicited response is specific to TETRA and is based on the D-TxGrant message. It indicates to the TE who is allowed to transmit in a simplex call. The TE uses the parameters set with this response to drive the MMI. Typically to display the identity of the transmitting party. Syntax It is an unsolicited response code from MT. Responses +CTXG: <CC instance >, <TxGrant>, <TxRqPrrmsn>, <e to e encryption> [,<TPI type> [,<TPI>]] Defined Values <CC instance> A three-digit number used to identify an ongoing call. The originating MT assigns it. The number will be assigned at the beginning of any particular call (incoming or outgoing) and used to relate all PEI signalling related to that call. <TxGrant> 0 - Transmission granted 1 - Transmission not granted(default) 2 - Transmission queued 3 - Transmission granted to another <TxRqPrrmsn> 0 - Allowed to request 1 - Not allowed to request <e_to_e_encryption> 0 - Clear (default) 1 - Encrypted. <TPI type> 0 - SSI 1 - TSI 2 - External subscriber number <TPI> A digit stream to be interpreted dependant on <TPI type>.

PEI Users Guide


11.2.7. +DMREP_ENABLE: Enable DMO Repeater Type1B

Description This command used to enable or disable DMO Repeater Type 1B mode in the radio. NOTE: The radio will restart/reboot when the DMO Repeater Type 1B mode is disabled (set to 0) Execution Syntax N/A Set Syntax AT+DMREP_ENABLE=(0-1) Read Syntax AT +DMPREP_ENABLE? Test Syntax AT +DMPREP_ENABLE=? Response + DMREP_ENABLE: (0-1)<cr><lf> <cr><lf>OK<cr><lf> Example : AT+DMREP_ENABLE?<cr> <cr><lf>+DMREP_ENABLE:1<cr><lf> <cr><lf>OK<cr><lf>

PEI Users Guide


11.2.8. DMREP_TIMERS: Configure timers used in DMO Repeater Type 1B mode

Description This command sets the values of various protocol timer values used in DMO Repeater Type 1B mode. The command AT+DMREP_TIMERS=0,0 can be used to set all timers to their default values. Execution Syntax N/A Set Syntax AT+DMREP_TIMERS=<DT253>[, <DT254>[, <DT255>[, <DT256>[, <DT257>[, <DT258>[, <DT259>]]]]]] Read Syntax

AT+DMREP_TIMERS? Test Syntax AT+DMREP_TIMERS=? Response +DMREP_TIMERS=<DT253>,<DT254>,<DT255>,<DT256>,<DT257>,<DT258><DT259><cr><lf> <cr><lf>OK<cr><lf> Defined Values <DT253> DM-REP Minimum interval between transmissions of DM-REP presence signal on a free carrier Default value = 2 multi-frame durations, Maximum = 60 multi-frame durations (See table below for correct syntax to set values) <DT254> DM-REP Maximum interval between transmissions of DM-REP presence signal on a free carrier Default value = 5 multi-frame durations, Maximum = 60 multi-frame durations. A value of 0 means no presence signal is sent. (See table below for correct syntax to set values) Valid values for DT253 and DT254 are defined as follows, Command Value Actual DT253/254 timer value 0 0 1 2 multi-frames 2 5 multi-frames 3 10 multi-frames 4 15 multi-frames 5 20 multi-frames 6 30 multi-frames 7 60 multi-frames <DT255> Time when randomization is required for transmission by DM-REP of a presence signal after channel becomes free Default value = 18 frame durations, Maximum = 72 frame durations <DT256> Inactivity time-out for active DM-REP in channel occupation Default value = 120 frame durations, Maximum = 360 frame durations <DT257> Inactivity time-out for idle DM-REP in channel occupation or reservation Default value = 90 frame durations, Maximum = 180 frame durations <DT258> Inactivity time-out for active DM-REP in channel reservation Default value = 120 frame durations, Maximum = 360 frame durations

PEI Users Guide


<DT259> Time when longer randomization is required for transmission after new call pre-emption acceptance. Default value = 9 frame durations, Maximum 36 frame durations Test Response Syntax +DMREP_TIMERS=<DT253>,<DT254>,<DT255>,<DT256>,<DT257>,<DT258><DT259><cr><lf> <cr><lf>OK<cr><lf> Test Response +DMREP_TIMERS=<DT253>,<DT254>,<DT255>,<DT256>,<DT257>,<DT258><DT259><cr><lf> <cr><lf>OK<cr><lf> Example : AT+DMREP_TIMERS=1,2,18,120,90,120<cr> <cr><lf>OK<cr><lf>

PEI Users Guide


11.2.1. +DMREP_CONSTS Configure constants used in DMO Repeater Type 1B mode

Description This command sets the values of various protocol constant values used in DMO Repeater Type 1B mode. The command AT+DMREP_CONSTANTS=0,0 can be used to set all constants to their default values. Execution Syntax N/A Set Syntax AT+DMREP_CONSTS=<DN232>[, <DN233>[, <DN253>[, <DN254>[, <DN255>]]]] Read Syntax

AT+DMREP_CONSTS? Test Syntax AT+DMREP_CONSTS=? Response +DMREP_CONSTS=<DN232>,<DN233>,<DN253>,<DN255>,<DN255><cr><lf> <cr><lf>OK<cr><lf> Defined Values <DN232> The number of consecutive frames in which the DM-REP transmit a DM-MS’s DM-SETUP or DM-SETUP PRES message on the slave link. Default value = 4 frame durations, Minimum = 2 frame durations, Maximum = 4 frame durations <DN233> The number of consecutive frames in which the DM-REP transmit a DM-MS’s DM-SDS UDATA or DM-SDS DATA message on the slave link. Default value = 4 frame durations, Minimum = 2 frame durations, Maximum = 4 frame durations <DN253> The number of consecutive frames in which the DM-REP transmits the free-channel presence signal Default value = 3 frame durations, Minimum = 2 frame durations, Maximum = 4 frame durations <DN254> Minimum randomization by DM-REP before it transmits the free-channel presence signal after channel becomes free. Default value = 1 frame durations, Minimum = 1 frame durations, Maximum = 8 frame durations <DN255> Maximum randomization by DM-REP before it transmits the free-channel presence signal after channel becomes free. Default value = 8 frame durations, Minimum = 4 frame durations, Maximum = 32 frame durations Test Response Syntax +DMREP_CONSTS=<DN232>,<DN233>,<DN253>,<DN254>,<DN255><cr><lf> <cr><lf>OK<cr><lf> Test Response +DMREP_CONSTS=<DN232>,<DN233>,<DN253>,<DN254>,<DN255><cr><lf> <cr><lf>OK<cr><lf> Example : AT+DMREP_CONSTS=4,4,3,1,8<cr> <cr><lf>OK<cr><lf>

PEI Users Guide


11.2.2. +DMREP_CNETCON Configure network parameters used in DMO Repeater Type1B mode

Description This command sets the MCC, MNC and Repeater Address used in DMO Repeater Type 1B mode. Execution Syntax N/A Set Syntax AT+DMREP_CNETCON=<MCC>, <MNC>, <Repeater Address> Read Syntax

AT+DMREP_CNETCON? Test Syntax AT+DMREP_CNETCON=? Response +DMREP_CNETCON=<MCC>,<MNC>,<Repeater Address><cr><lf> <cr><lf>OK<cr><lf> Defined Values <MCC> The Mobile Country Code <MNC> The Mobile Network Code <Repeater Address> The Repeater Address for this repeater (10 bits, 0-1023) Test Response Syntax +DMREP_CNETCON=<MCC>,<MNC>,<Repeater Address><cr><lf> <cr><lf>OK<cr><lf> Test Response +DMREP_CNETCON=<MCC>,<MNC>,<Repeater Address><cr><lf> <cr><lf>OK<cr><lf> Example : AT+DMREP_CNETCON=262,1000,0<cr> <cr><lf>OK<cr><lf>

PEI Users Guide


11.2.3. +DMREP_CCHAN Configure RF parameters used in DMO Repeater Type1B mode

Description This command sets the RF parameters used in DMO Repeater Type 1B mode. (e.g. RF Frequency, Duplex Spacing, etc.) Execution Syntax N/A Set Syntax AT+DMREP_CCHAN=<TX_FREQUENCY>[,<DUPLEX SPACING>[, <REVERSE>[,MAX_MSPOWER_CLASS]]] Read Syntax

AT+DMREP_CCHAN? Test Syntax AT+DMREP_CCHAN=? Response +DMREP_CCHAN=<TX_FREQUENCY>,<DUPLEX SPACING>, <REVERSE>,<MAX_MSPOWER_CLASS> <cr><lf> <cr><lf>OK<cr><lf> Defined Values <TX_FREQUECY> The transmit frequency of the DMO Repeater Type 1B (F2) <DUPLEX SPACING> The duplex spacing between the transmit frequency F1 and the receive frequency F1, defined as follows, 0 - Invalid value 1 - 1.6MHz 2 - 4.5MHz 3 - 8MHz 4 - 10MHz 5 - 18MHz 6 - 30MHz 7 - 39MHz 8 - 45MHz <REVERSE> Reverse operation, defines whether F1 is above or below F2 by the duplex spacing amount, defined as follows, 0 - Rx Frequency F1 = Transmit Frequency F2 + Duplex Spacing 1 - Rx Frequency F1 = Transmit Frequency F2 – Duplex Spacing <MAX MSPOWER CLASS> Defines maximum power class MS’s should use to access this repeater, defined as follows, 0 - Invalid value 1 - Class 1 2 - Class 2 3 - Class 3 4 - Class 4 5 - Class 5 6 - Invalid value 7 - Invalid value Test Response Syntax +DMREP_CCHAN=<TX_FREQUENCY>,<DUPLEX SPACING>, <REVERSE>,<MAX_MSPOWER_CLASS> <cr><lf> <cr><lf>OK<cr><lf>

PEI Users Guide


Test Response +DMREP_CCHAN=<TX_FREQUENCY>,<DUPLEX SPACING>, <REVERSE>,<MAX_MSPOWER_CLASS> <cr><lf> <cr><lf>OK<cr><lf> Example : AT+DMREP_CCHAN=392987500,4,1,1<cr> <cr><lf>OK<cr><lf>

PEI Users Guide


11.2.1. +DMREP_USAGE Configure Usage parameters used in DMO Repeater Type1B mode

Description This command configures various usage parameters in DMO Repeater Type 1B mode. (e.g. like usage restrictions or additional MCC/MNC’s which are allowed to use the repeater) Execution Syntax N/A Set Syntax AT+DMREP_USAGE=<RESTRICTION TYPE>[, <USAGE_MCC>[, <USAGE_MNC>[, <VAL UNIT>[, <NO OF VAL TIME UNITS>[,USAGE_SSI1[,USAGE_SSI2[,USAGE_SSI3]]]]]]] Read Syntax

AT+DMREP_USAGE? Test Syntax AT+DMREP_USAGE=? Response +DMREP_USAGE=<RESTRICTION TYPE>, <USAGE_MCC>, <USAGE_MNC>, <VAL UNIT>, <NO OF VAL TIME UNITS>,<USAGE_SSI1>,<USAGE_SSI2>,<USAGE_SSI3> <cr><lf> <cr><lf>OK<cr><lf> Defined Values < RESTRICTION TYPE > The restrictions on which DM-MS’s are permitted to attempt to use the DM-REP, defined as follows 0 - No restrictions (default value) 1 - Restricted by prior arrangement 2 - Restricted to single MNI 3 - Restricted to single address (TSI) 4 - Restricted to 2 addresses (TSI + SSI) 5 - Restricted to 2 addresses (TSI + SSI) 6 - Restricted to 3 addresses (SSI + SSI + SSI) <USAGE_MCC> Used for all restriction types requiring an MNI (MCC+MNC) <USAGE_MNC> Used for all restriction types requiring an MNI (MCC+MNC) <VAL UNIT> Defines Validity Time Unit being used as defined as follows, 0 - Multi-frame 1 - 60 Multi-frames (default value) 2 - 3600 Multi-frames 3 - Unit not restricted <NO OF VAL TIME UNITS> Defines the validity time expressed as the number of validity time units Default value = 3, Maximum value = 63 <USAGE_SSI1> Used for restriction types 3, 4, 5 and 6. Default value = 0 <USAGE_SSI2> Used for restriction types 4, 5 and 6. Default value = 0 <USAGE_SSI3> Used for restriction type 6. Default value = 0 Test Response Syntax +DMREP_USAGE=<RESTRICTION TYPE>, <USAGE_MCC>, <USAGE_MNC>, <VAL UNIT>, <NO OF VAL TIME UNITS>,<USAGE_SSI1>,<USAGE_SSI2>,<USAGE_SSI3> <cr><lf> <cr><lf>OK<cr><lf>

PEI Users Guide


Test Response +DMREP_USAGE=<RESTRICTION TYPE>, <USAGE_MCC>, <USAGE_MNC>, <VAL UNIT>, <NO OF VAL TIME UNITS>,<USAGE_SSI1>,<USAGE_SSI2>,<USAGE_SSI3> <cr><lf> <cr><lf>OK<cr><lf> Example : AT+DMREP_USAGE=2,262,1001,1, 3,8280460,8280461,8280462<cr> <cr><lf>OK<cr><lf>

PEI Users Guide


11.2.2. +DMREP_STATE Reports the current state of the DMO Repeater Type 1B

Description This command allows the user to interrogate the current state of the DMO Repeater Type 1B. The +DMREP_STATE is also output as an unsolicited message when the state changes. Execution Syntax +DMREP_STATE:<STATE> Set Syntax N/A Read Syntax

AT+DMREP_STATE? Test Syntax N/A Response +DMREP_STATE=<STATE> <cr><lf> <cr><lf>OK<cr><lf> Defined Values < STATE > The current call state of the Repeater, defined as follows 0 - Channel Free and DM-REP is Idle 1 - Channel Occupied DM-REP is Idle 2 - Channel Reserved DM-REP is Idle 3 - Channel Occupied DM-REP is Active 4 - Channel Reserved DM-REP is Active Test Response Syntax N/A Test Response N/A Example : AT+DMREP_STATE?<cr> +DMREP_STATE:0 <cr><lf>OK<cr><lf>

PEI Users Guide


11.2.3. +DMREP_MUTE allows repeater unsolicited output to be muted

Description This command allows the user to mute the DMO Repeater Type 1B unsolicited output which can be useful when using the PEI interface to make configuration changes. Execution Syntax +DMREP_MUTE:<MUTE_STATE> Set Syntax N/A Read Syntax

AT+DMREP_MUTE? Test Syntax N/A Response +DMREP_MUTE=<0 or 1> <cr><lf> <cr><lf>OK<cr><lf> Defined Values < MUTE_STATE > 0 - Unsolicited output is enabled 1 - Unsolicited output is disabled (muted) Test Response Syntax N/A Test Response N/A Example : AT+DMREP_MUTE?<cr> +DMREP_MUTE:0 <cr><lf>OK<cr><lf>

PEI Users Guide


11.2.4. +CDTXC: Down Transmission Ceased

Description This response is specific to TETRA and is based on the D-TxCeased message. In simplex calls it indicates to the TE that the talking party has ceased its transmission so it can update its MMI. The TE may request permission to transmit depending on the value of RqTx. This is an unsolicited response

Responses +CDTXC: <CC instance >, <RqTx> <CR><LF> Defined values <CC instance > A three-digit number used to identify an ongoing call. The originating MT assigns it. The number will be assigned at the beginning of any particular call (incoming or outgoing) and used to relate all PEI signalling related to that call.

<RqTx> 0 - Request to Tx(default) 1 - No Request to Tx.

PEI Users Guide


11.3. Errors Within Tetra PEI

11.3.1. Responses to commands

There are two types of response, informational text (such as baud rate) and result codes. Result codes can be either final (e.g. OK) or unsolicited (e.g. +CTICN). AT+CMD=?<cr> // a fictitious AT command requesting a response <cr><lf>+CMD: data<cr><lf> // information response <cr><lf>OK<cr><lf> // final result code The format of these can generally be set with the following commands, although many of these have restricted values within the Funk-Electronic Piciorgros GmbH products: ATS3 ATS4 ATV AT+CMEE The effects of these individual commands have already been detailed. However, the interaction is studied here. The +CMEE command sets the level of CME error reporting. The error reporting can be either numeric or alphabetic. The CME errors supported by the Funk-Electronic Piciorgros GmbH PEI are shown below. 0 MT_FAILURE 1 NO_CONNECTION_TO_MT 2 MT_ADAPTER_LINK_RESERVED 3 OPERATION_NOT_ALLOWED 4 OPERATION_NOT_SUPPORTED 5 PH_SIM_PIN_REQUIRED 10 SIM_NOT_INSERTED 11 SIM_CHV1_REQUIRED 12 SIM_UNBLOCKING_CHV1_REQUIRED 13 SIM_FAILURE 14 SIM_BUSY 15 SIM_WRONG 16 INCORRECT_PASSWORD 17 SIM_CHV2_REQUIRED 18 SIM_UNBLOCKING_CHV2_REQUIRED 19 MEMORY_FULL 20 INVALID_INDEX 21 NOT_FOUND 22 MEMORY_FAILURE 24 TEXT_STRING_TOO_LONG 25 INVALID_CHARACTERS_IN_TEXT_STRING 26 DIAL_STRING_TOO_LONG 27 INVALID_CHARACTERS_INDIAL_STRING 30 NO_NETWORK_SERVICE 31 NETWORK_TIMEOUT 32 ERROR_DECODING_DATA 33 PARAMETER_WRONG_TYPE 34 PARAMETER_VALUE_OUT_OF_RANFGE 35 SYNTAX_ERROR 36 DATA_RECEIVED_WITHOUT_COMMAND 37 TIMEOUT_WAITING_FOR_DATA 38 PROTOCOL_IDETIFIER_ALREADY_REGISTERED 39 REGISTRATION_TABLE_FULL 330 SMSC_ADDRESS_UNKNOWN 331 UNKNOWN

TMC-210

Tetra Modem Core

Extended AT Command Set


Claudiastr. 5

51149 Köln



The information contained within this document is the copyright of Funk-Electronic Piciorgros GmbH.

No part of this document may be transmitted, reproduced or disclosed in any form, or by any means, physical or electronic, without the written permission of Funk-Electronic Piciorgros GmbH. The term document extends to all forms of media in which this information may be

embodied.

1 HISTORY Issue Date Author Review No. Details

A 19/08/09 James Hall Initial draft

B 15/12/11 Neil Turner Update command list

C 18/06/12 Neil Turner Updated with new commands

D 05/05/14 Neil Turner Updated with latest commands

E 11/06/15 Neil Turner Updated with new commands including TTS output descriptions

F 30/06/16 Neil Turner Add PPPSPLIT and AIEALG commands plus assorted fixes

G 29/05/17 Neil Turner Add FLASHPROG and SDSTLRPT commands



TMC-210 .................................................................................................................................... 1

Tetra Modem Core ..................................................................................................................... 1

1 History ................................................................................................................................ 2

2 Introduction ......................................................................................................................... 5

2.1 Purpose ....................................................................................................................... 5

2.2 Scope .......................................................................................................................... 5

2.3 Guide to Document ..................................................................................................... 5

2.4 References .................................................................................................................. 5

2.5 Glossary ...................................................................................................................... 5

2.6 Definition of Terms ...................................................................................................... 5

3 Additional AT commands ................................................................................................... 6

3.1 AT+PIMODE ............................................................................................................... 6

3.2 Network Configuration AT+CNETCON ....................................................................... 7

3.3 Channel Configuration AT+CCHAN ............................................................................ 8

3.4 Group Configuration AT+CGSSI ................................................................................. 9

3.5 Get or Set Output Power AT+CMAXP ..................................................................... 10

3.6 Report Reflected Power AT+CREFP ........................................................................ 11

3.7 Neighbour Cell Information AT+CNCL ...................................................................... 12

3.8 Data Link Status AT+CDLSTAT ................................................................................ 13

3.9 Supported Frequencies AT+CFREQR ...................................................................... 14

3.10 Speaker Volume AT+CSPKVOL ......................................................................... 15

3.11 Microphone Gain AT+CMICGAIN ........................................................................ 16

3.12 Play Ringtone AT+CTONE .................................................................................. 17

3.13 Cell Information AT+SYSINFO ............................................................................ 18

3.14 Digital Voice AT+DVMODE ................................................................................. 19

3.15 Digital Voice AT+DVMODER ............................................................................... 20

3.16 Software Versions AT+SWVER ........................................................................... 21

3.17 Modem Air Trace AT+AIRLOG ............................................................................ 22

3.18 Terminal Equipment Identification AT+CTEI ....................................................... 23

3.19 Packet Data QoS Parameters AT+PDQOS ........................................................ 24

3.20 Authentication/Encryption AT+CENC .................................................................. 25

3.21 Neighbour Cells AT+CNEIG ................................................................................ 26

3.22 Transmit Power AT+CPOW ................................................................................. 27

3.23 Flash Neighbour Cells AT+FLASHNC ................................................................. 28

3.24 DMO Group Attach AT+CTGSD .......................................................................... 29

3.25 Neighbour Cell Priority List AT+LACP ................................................................. 30

3.26 Neighbour Cell Black List AT+BLIST ................................................................... 31

3.27 Neighbour Cell Forbidden List AT+FLIST ........................................................... 32



3.28 Modem Log Output AT+MODLOG ...................................................................... 33

3.29 Packet Data Transmit Request AT+PDTXR ........................................................ 34

3.30 Tetra Test Set Mode AT+TTSMODE................................................................... 35

3.31 Tetra Test Set Scan Mode AT+TTSSCAN .......................................................... 36

3.32 Tetra Test Set Mute AT+TTSMUTE .................................................................... 37

3.33 Tetra Test Set Mute AT+ALGWMODE ................................................................ 38

3.34 Power Off AT+POWOFF ..................................................................................... 39

3.35 PPP Split AT+PPPSPLIT ..................................................................................... 40

3.36 Air Interface Encryption Algorithm AT+AIEALG ................................................. 41

3.37 Subscription Subscriber class AT+SUBSCR ...................................................... 42

3.38 Report Battery Status AT+BATT ......................................................................... 43

4 Voice Enabled Modem ..................................................................................................... 46

4.1.1 Implementation .................................................................................................... 46

5 AT Interface On UART 1 And UART 3 ............................................................................. 47

5.1.1 Implementation .................................................................................................... 47

6 TETRA Test Set OUTPUT ............................................................................................... 48

6.1.1 TTSSCAN=1 Mode .............................................................................................. 48

6.1.2 TTSSCAN=2 Mode .............................................................................................. 49

6.1.2.1 +BATT:Voltage,Charger .............................................................................. 49

6.1.2.2 +NBLAC: Count, RecordNo, LAC, LAC, LAC, LAC…. ................................ 49

6.1.2.3 +NBRSSI: Count, RecordNo, RSSI, RSSI, RSSI ........................................ 50

6.1.2.4 +NBCHAN: Count, RecordNo, Channel, Channel, Channel…. .................. 50

6.1.2.5 +NBC1: Count, RecordNo, C1, C2, C2…. ................................................... 50

6.1.2.6 +NBBER: Count, RecordNo, BER, RDC ..................................................... 50

6.1.2.7 +NPARAMS: : Count, RecordNo,Param1, Param2….. ............................... 51



2 INTRODUCTION

2.1 PURPOSE This document describes the extended AT command set implemented for the Funk-Electronic Piciorgros GmbH modem software. These commands are described in this document, rather than in Ref [1] as they are not intended for release to, or use by, the end customer.

2.2 SCOPE This document is intended for use by users of the modem.

2.3 GUIDE TO DOCUMENT This document should be read alongside Ref[1], in order to give the full AT command set of the modem.

2.4 REFERENCES 1. PEI User Guide

2.5 GLOSSARY

2.6 DEFINITION OF TERMS



3 ADDITIONAL AT COMMANDS

3.1 AT+PIMODE Description

This command configures the modem to use the Piciorgros extended mode commands. By enabling PI mode, the extended AT commands listed in this document become available. If PI mode is disabled, attempting to use any of the extended Piciorgros commands will result in an ERROR return.

Set Syntax

AT+PIMODE=<PI status>

Read Syntax

AT+PIMODE?

Test Syntax

AT+PIMODE=?

Responses

+PIMODE:<PIstatus>

Defined Values

<PI mode>

0 PI mode disabled 1 PI mode enabled



3.2 NETWORK CONFIGURATION AT+CNETCON Description

This command allows the network configuration (MCC, MNC and ISSI) to be read, or changed by the user. After using this command, the modem must be re-booted for the configuration change to take effect.

Set Syntax

AT+CNETCON=<MCC>,<MNC>,<ISSI>

Read Syntax

AT+CNETCON?

Shall return a string of the format:

+CNETCON=<MCC>,<MNC>,<ISSI>

Test Syntax

AT+CNETCON=?

Defined Values

MCC - The Mobile Country Code

MNC - The Mobile Network Code

ISSI - The International Subscriber Identity



3.3 CHANNEL CONFIGURATION AT+CCHAN Description

This command allows the channel scan range to be defined on the radio.

If NUM_CHANS is not specified, then a single channel will be defined with the value CHANSTART.

If CHANSTART and NUM_CHANS are set to 0, the specified range RANGE_ID will be deleted.

If either CHANSTART or NUM_CHANS are out of the valid channel range for the frequency band of the radio (other than being set to 0, then ERROR shall be returned, and no changes made to the channel range RANGE_ID.

After using this command, the modem must be re-booted for the configuration change to take effect.

Set Syntax

AT+CCHAN=<RANGE_ID>,<CHANSTART>,[<NUM_CHANS>]

Read Syntax

AT+CCHAN?

Shall return a string of the format:

+CCHAN:<RANGE_ID>,<CHANSTART>,<CHANEND>,[<RANGE_ID>,<CHANSTART>,<CHANEND>],[<RANGE_ID>,<CHANSTART>,<CHANEND>]

Test Syntax

AT+CCHAN=?

Defined Values

RANGE_ID - is a value in the range 0-1, indicating which of up to 2 channel ranges are to be set by the command.

CHANSTART - is the actual frequency in Hz divided by 100 of the channel, rather than the channel number (i.e. 4255000 for 425.500 MHz).

NUM_CHANS - is the number of channel in the range.



3.4 GROUP CONFIGURATION AT+CGSSI Description

This command will add a new group to the radio.

After using this command, the modem must be re-booted for the configuration change to take effect.

To attach to groups already set in the radio, use the command AT+CTGS command.

Set Syntax

AT+CGSSI=<GSSI>,[<GSSI>],[<GSSI>],[<GSSI>],[<GSSI>]

Read Syntax

AT+CGSSI?

Shall return a string in the format:

+CGSSI=<GSSI>,[<GSSI>],[<GSSI>],[<GSSI>],[<GSSI>]

Test Syntax

AT+CGSSI=?

Defined Values

GSSI – The Group Subscriber Identity.



3.5 GET OR SET OUTPUT POWER AT+CMAXP Description

This command allows the maximum power at which the radio will transmit to be set or displayed.

Set Syntax

AT+CMAXP=<MAX_POWER>.

Read Syntax

AT+CMAXP?


+CMAXP:<MAXP>

Test Syntax

AT+CMAXP=?

Defined Values

MAX_POWER - is the value (in mW) that the modem can output.



3.6 REPORT REFLECTED POWER AT+CREFP Description

This command will enable or disable the unsolicited reporting of the reflected power measured by the DSP.

When enabled, the unsolicited response shall periodically be generated, when a measurement of reflected power is made by the DSP:

+CREFPOWER:<STATUS>,<REF_OWER>

Set Syntax

AT+CREFP=<STATUS>

Read Syntax

AT+CREFP?

Test Syntax

AT+CREFP=?


+CREFP:(0-1)

Defined Values

STATUS

0 – Reporting disabled.

1 – Reporting enabled.

REF_POWER – The reflected power measured (in mW).



3.7 NEIGHBOUR CELL INFORMATION AT+CNCL Description

This command enables or disables the unsolicited reporting of neighbour cell information, for up to 4 neighbouring cells.

When enabled, the unsolicited response:

+CNCL:<MCN>,<PATHLOSS>,[<MCN>,<PATHLOSS>,][<MCN>,<PATHLOSS>,][<MCN>,<PATHLOSS>,]

Shall be returned whenever the stack receives neighbour cell monitoring indications.

Set Syntax

AT+CNCL=<STATUS>

Read Syntax

AT+CNCL?

Test Syntax

AT+CNCL=?


+CNCL:<NCELLS>,<MCN>,<PATHLOSS>,[<MCN>,<PATHLOSS>,][<MCN>,<PATHLOSS>,][<MCN>,<PATHLOSS>,]

Defined Values

NCELLS – The number of neighbour cells.

MCN – Main Carrier Number.

PATHLOSS – The signal strength measured on MCN.



3.8 DATA LINK STATUS AT+CDLSTAT Description

This command will return the on line status of the radio.

Set Syntax

There is no set command

Read Syntax

AT+CDLSTAT?

The response will be:

+CDLSTAT:<DLSTATUS>

Test Syntax

There is no test command

Defined Values

DLSTATUS

ONLINE – There is an active data connection.

IDLE – The data connection is idle.



3.9 SUPPORTED FREQUENCIES AT+CFREQR Description

This command will return the minimum and maximum supported TETRA frequencies of the modem.

Set Syntax


Read Syntax

AT+CFREQR?


+CFREQR:<MIN_FREQUENCY>,<MAX_FREQUENCY>

Test Syntax


Defined Values

MIN_FREQUENCY – The minimum frequency in the TETRA band of this modem

MAX_FREQUENCY – The maxmum frequency in the TETRA band of this modem



3.10 SPEAKER VOLUME AT+CSPKVOL Description

This command will set or return the current speaker volume used during voice calls and for making tones

Set Syntax

AT+CSPKVOL=<0-10>

Read Syntax

AT+CSPKVOL?


+CSPKVOL:<VOLUME>

Test Syntax

AT+CSPKVOL=?


+CSPKVOL=<0-10>

Defined Values

VOLUME – The speaker volume in units 0-10



3.11 MICROPHONE GAIN AT+CMICGAIN Description

This command will set or return the current microphone gain used during voice calls.

Set Syntax

AT+CMICGAIN=<0-10>

Read Syntax

AT+CMICGAIN?


+CMICGAIN:<MIC_GAIN>

Test Syntax

AT+CMICGAIN=?


+CMICGAIN=<0-10>

Defined Values

MIC_GAIN – The microphone gain in units 0-10



3.12 PLAY RINGTONE AT+CTONE Description

This command will cause the modem to play a tone through the speaker, or stop playing a tone.

Set Syntax

AT+CTONE=<0-9>

Read Syntax

There is no read command

Test Syntax

AT+CTONE=?


+CTONE=<0-9>

Defined Values

TONE=0 – Stop playing tone

TONE=<1-9> – Play tones 1 though 9, each tone is different



3.13 CELL INFORMATION AT+SYSINFO Description

This command will return information received in the SYSINFO message from the attached TETRA network

Set Syntax


Read Syntax

AT+SYSINFO?


+SYSINFO:<REGISTRATION_MANDATORY>,<DEREG_MANDATORY>,<PRIORITY_CELL>,<NEVER_USES_MIN_MODE>,<MIGRATION_UPPORTED>,<SYSTEM_WIDE_SERVICES>,<TETRA_VOICE_SERVICE>,<CIRCUIT_MODE_DATA_SVC>,<SNDCP_SERVICE>,<AI_ENCRIPTION>,<ADVANCED_LINK>

Test Syntax

AT+SYSINFO=?


+SYSINFO:REGISTRATION_MANDATORY, DEREG_MANDATORY, PRIORITY_CELL, NEVER_USES_MIN_MODE, MIGRATION_SUPPORTED, SYSTEM_WIDE_SERVICES, TETRA_VOICE_SERVICE, CIRCUIT_MODE_DATA_SVC, SNDCP_SERVICE, AI_ENCRYPTION, ADVANCED_LINK

Defined Values

All values are true if returned as 1 and false if returned as 0.

REGISTRATION_MANDATORY – Registration on the network is mandatory

DEREG_MANDATORY – De-registration on the network is mandatory

PRIORITY_CELL – This cell is a Priority Cell

NEVER_USES_MIN_MODE – The cell does not use Minimum Mode

MIGRATION_SUPPORTED – This network supports Migration

SYSTEM_WIDE_SERVICES – This cell is connected to the rest of the TETRA network

TETRA_VOICE_SERVICE – This cell supports voice calls

CIRCUIT_MODE_DATA_SVC – This cell supports Circuit Mode Data calls

SNDCP_SERVICE – This cell supports SNDCP services (Packet Data)

AI_ENCRYPTION – This cell supports Air Interface Encryption

ADVANCED_LINK – This cell supports Advanced Link services (Packet Data)



3.14 DIGITAL VOICE AT+DVMODE Description

This command enables or disables Digital Voice Mode

Set Syntax

AT+DVMODE=<0-1>

Read Syntax

AT+DVMODE?

+DVMODE:<0-1>

Test Syntax

AT+DVMODE=?


+DVMODE=<0-1>

Defined Values

0 – Digital Voice Mode is disabled

1 – Digital Voice Mode is enabled



3.15 DIGITAL VOICE AT+DVMODER Description

This command enables or disables Digital Voice Mode. It differs from the above command in that the change in mode is only temporary and is not committed to flash. When the modem is rebooted the mode reverts to whatever has been set by the AT+DVMODE command above.

Set Syntax

AT+DVMODER=<0-1>

Read Syntax

AT+DVMODER?

+DVMODE:<0-1>

Test Syntax

AT+DVMODER=?


+DVMODER=<0-1>

Defined Values

0 – Digital Voice Mode is disabled

1 – Digital Voice Mode is enabled



3.16 SOFTWARE VERSIONS AT+SWVER Description

This command display the current versions of the radio software

Set Syntax


Read Syntax

AT+SWVER?


+SWVER:<Stack Version>,<MMI Version>,<DSP Version>

Test Syntax

AT+SWVER=?


+SWVER:<Stack Version>,<MMI Version>,<DSP Version>

Defined Values

Stack Version – The version number of the Protocol Stack firmware

MMI Version – The version number of the MMI firmware

DSP Version – The version number of the DSP firmware



3.17 MODEM AIR TRACE AT+AIRLOG Description

This command display the current versions of the radio software

Set Syntax

AT+AIRLOG=<0-1>

Read Syntax

There is no read syntax

Test Syntax

AT+AIRLOG=?


+AIRLOG:<0-1>

Defined Values

0 – Disable Air tracing on debug port

1 – Enable Air tracing on debug port



3.18 TERMINAL EQUIPMENT IDENTIFICATION AT+CTEI Description

This command displays the TEI number

Set Syntax


Read Syntax

AT+CTEI?

+CTEI:<TAC>,<FAC>,<ESN>

Test Syntax

AT+CTEI=?


+CTEI:<TAC>,<FAC>,<ESN>

Defined Values

TAC – TAC identifier

FAC – Manufacturer FAC code

ESN – Electronic Serial Number



3.19 PACKET DATA QOS PARAMETERS AT+PDQOS Description

This command sets or displays the Quality of Service (QoS) parameters used in negotiating packet data sessions.

Set Syntax

AT+PDQOS= <Slots(1-4)>,<Throughput (0-5,7)>,<N273 (0-7)>,<N274 (1-15)>

Read Syntax

AT+PDQOS?

+PDQOS: <Slots(1-4)>,<Throughput (0-5,7)>,<N273 (0-7)>,<N274 (1-15)>

Test Syntax

AT+CTEI=?


+PDQOS: <Slots(1-4)>,<Throughput (0-5,7)>,<N273 (0-7)>,<N274 (1-15)>

Defined Values

Slots – The number of packet data slots to request (MSPD)

Throughput – The required Throughput (as defined by TETRA)

N273 – N273 TETRA retransmit parameter

N274 – N274 TETRA retransmit parameter



3.20 AUTHENTICATION/ENCRYPTION AT+CENC Description

This command enables and disables Authentication and Air Interface Encryption

Set Syntax

AT+CENC=<0-2>,<0-2>

Read Syntax

AT+CENC?

+CENC:<AUTHENTICATION_MODE>,<AEI_CLASS>

Test Syntax

AT+CENC=?


+CENC:<0-2>,<0-2>

Defined Values

AUTHENTICATION_MODE – 0=None, 1=Enabled, 2=Mutual Authentication

AEI_CLASS – 0=Class1 (Clear), 1=Encryption Class 2, 2=Encryption Class 3



3.21 NEIGHBOUR CELLS AT+CNEIG Description

This command enables and disables processing Neighbour Cell Broadcasts

Set Syntax

AT+CNEIG=<0-1>

Read Syntax

AT+CNEIG?

+CNEIG:<0-1>

Test Syntax

AT+CNEIG=?


+CNEIG:<0-1>

Defined Values

0 – Neighbour Cell Broadcast processing is disabled

1 – Neighbour Cell Broadcast processing is enabled



3.22 TRANSMIT POWER AT+CPOW Description

This command displays the current transmit power in mW

Set Syntax


Read Syntax

AT+CPOW?

+CPOW:<mW>

Test Syntax


Defined Values

None



3.23 FLASH NEIGHBOUR CELLS AT+FLASHNC Description

This command causes the modem to program the current neighbour list into flash memory so it can be used as a fast channel scan during the next boot up The neighbour list is only written to flash if it is found to be different to the one already stored.

Set Syntax

AT+FLASHNC=<0-1>

Read Syntax


Test Syntax

AT+FLASHNC=?


+FLASHNC:<0,1>

Defined Values

0 – Clear the neighbour list currently stored in flash

1 – Write the current neighbour cell list in flash memory



3.24 DMO GROUP ATTACH AT+CTGSD Description

This command creates or displays DMO groups.

Set Syntax

AT+CTGSD=<group type>, <called party identity>,<channel number>,<offset>,….

These parameters can be repeated in the command to add several groups in one command

AT+CTGSD=0,0

This command will remove ALL DMO groups.

Read Syntax


Test Syntax

AT+CTGSD=?


+CTGSD(0-2),("CALLED PARTY IDENTITY"),("CHANNEL NUMBER"),("0-3")

Defined Values

<group type> – 0 = special mean (see above), 1 = Selected, 2 = Scanned

<called party identity> – the GSSI of the group being defined, (0 has special meaning)

<channel number> – the TETRA channel number of the frequency used by this group

<offset> – the frequency offset,

0=0KHz, 1=+6.25KHz, 2=-6.25KHz, 3=12.5KHZ



3.25 NEIGHBOUR CELL PRIORITY LIST AT+LACP Description

This command adds entries to the Neighbour Cell Priority list based on cell LA number. There can be up to 3 priority neighbour cells. Cells in this list are preferred over other neighbours even if their current field strength is lower. However the field strength of a priority neighbour cell must be above the <MinFS> value before it is will be considered as a priority cell.

Set Syntax

AT+LACP=<Priority 1 LAC>,<MinFS>,<Priority2 LAC>,<MinFS>,<Priority 3 LAC>,<MinFS>

The command can be given with either 1, 2 or all 3 cells in the priority list

Read Syntax

AT+LACP?

Test Syntax

AT+LACP=?


+LACP:<Priority 1 LAC>,<MinFS>,<Priority 2 LAC>,<MinFS>,<Priority 3 LAC>,<MinFS>

Defined Values

<Priority 1 LAC> – the LA number of the cell which be given the highest priority

<MinFS> – the minimum field strength the cell must have before being considered

<Priority 2 LAC> – the LA number of the cell which be given the next highest priority


<Priority 3 LAC> – the LA number of the cell which be given the next highest priority




3.26 NEIGHBOUR CELL BLACK LIST AT+BLIST Description

This command adds entries to the Neighbour Cell Black list based on cell LA number. Cells in this list will only be used if there are no other cells available. Up to 3 cells can be black listed.

Set Syntax

AT+BLIST=<LAC>,<LAC>,<LAC>

The command can be given with either 1, 2 or all 3 cells in the list

Read Syntax

AT+BLIST?

Test Syntax

AT+BLIST=?


+BLIST:<LAC>,<LAC>,<LAC>

Defined Values

< LAC> – the LA number of the cell which will be added to the Black List



3.27 NEIGHBOUR CELL FORBIDDEN LIST AT+FLIST Description

This command adds entries to the Neighbour Cell Forbidden list based on cell LA number. Cells in this list will NEVER be used by the modem. Up to 3 cells can be added to the Forbidden List.

Set Syntax

AT+FLIST=<LAC>,<LAC>,<LAC>

The command can be given with either 1, 2 or all 3 cells in the list

Read Syntax

AT+FLIST?

Test Syntax

AT+FLIST=?


+FLIST:<LAC>,<LAC>,<LAC>

Defined Values

< LAC> – the LA number of the cell which will be added to the Forbidden List



3.28 MODEM LOG OUTPUT AT+MODLOG Description

This command enables or disables modem logging output. This output consists of meaningful text messages about events occurring in the TETRA protocol stack, e.g.

MODLOG:Registered Successfully on LA 1

MODLOG:Registration Rejected Cause: ITSIUnknown

Set Syntax

AT+MODLOG=<0-1>

Read Syntax

AT+MODLOG?

Test Syntax

AT+MODLOG=?


+MODLOG:<0-1>

Defined Values

0 – Disables modem logging output

1 – Enables modem logging output



3.29 PACKET DATA TRANSMIT REQUEST AT+PDTXR Description

This command is only valid when the modem has an active packet data connection. It forces the modem to send a packet data transmit request to the network (even if it has no data to send). This should only be used as a debugging tool.

Set Syntax

AT+PDTXR=1

Defined Values

1 – Forces a Packet Data Transmit Request to be sent to the network



3.30 TETRA TEST SET MODE AT+TTSMODE Description

This command enables or disables Tetra Test Set Mode in the modem. When enabled this mode will periodically output information about the attached Tetra network. . For full details of the output in this mode see Chapter 6

Set Syntax

AT+TTSMODE=<0-1>

Read Syntax

AT+TTSMODE?

Test Syntax

AT+TTSMODE=?


+TTSMODE:<0-1>

Defined Values

0 – Disables Tetra Test Set mode

1 – Enables Tetra Test Set mode



3.31 TETRA TEST SET SCAN MODE AT+TTSSCAN Description

This command enables or disables Tetra Test Set Scan Mode in the modem. It only takes effect when TTSMODE itself is enabled. When enabled to mode will periodically output information about TETRA networks found during a scan. For full details of the output in this mode see Chapter 6

Set Syntax

AT+TTSSCAN=<0-2>

Read Syntax

AT+TTSSCAN?

Test Syntax

AT+TTSSCAN=?


+TTSSCAN:<0-2>

Defined Values

0 – Disables Tetra Test Set Scan mode

1 – Enables Tetra Test Set Scan mode 1. In this mode the radio continuously scans the air looking for valid Tetra channels on any network (whatever the MCC/MNC)

2 – Enabled Tetra Test Set Scan mode 2. In this mode the radio connects to the strongest Tetra cell on the configured network (matching MCC/MNC) but does not register. It reports cell neighbours and continues to reselect without registering as the radio moves.



3.32 TETRA TEST SET MUTE AT+TTSMUTE Description

This command enables or disables the periodic output when the device is in one of the Tetra Test Modes. The device remains in its current mode all the time only the output is disabled

Set Syntax

AT+TTSMUTE=<0-1>

Read Syntax

AT+TTSMUTE?

Test Syntax

AT+TTSMUTE=?


+TTSMUTE:<0-1>

Defined Values

0 – Enables Tetra Test Set output

1 – Disables Tetra Test Set Scan output



3.33 TETRA TEST SET MUTE AT+ALGWMODE Description

This command enables or disables a special Analogue Gateway mode in the radio. This disables all normal TETRA operations and is not intended for use by customers.

Set Syntax

AT+ALGWMODE=<0-1>

Read Syntax

AT+ALGWMODE?

Test Syntax

AT+ALGWMODE=?


+ALGWMODE:<0-1>

Defined Values

0 – Enables Analogue Gateway Mode

1 – Disables Analogue Gateway Mode (the radio will restart)



3.34 POWER OFF AT+POWOFF Description

This command causes the radio to de-register and power off

Set Syntax

AT+POWOFF=<0-1>

Test Syntax

AT+POWOFF=?


+POWOFF:<0-1>

Defined Values

0 – No action

1 – Begin de-registration and power off the radio



3.35 PPP SPLIT AT+PPPSPLIT Description

This command allows control over which UART PPP data is sent during a packet data session when PIMODE=1. When PIMODE=0 packet data is sent over UART2 the AT command UART. When PIMODE is entered packet data is split and sent over UART 3, UART 1 remains the AT command port during the packet data session. If it is required that packet data be send over UART 1 in PIMODE=1 then this command (AT+PPPSPLIT=0) will restore the data to UART1, the AT command UART.

Set Syntax

AT+PPPSPLIT=<0-1>

Test Syntax

AT+PPPSPLIT=?


+PPPSPLIT:<0-1>

Defined Values

0 – PPP Packet data will be sent on UART1 the AT command UART

1 – PPP Packet data will be sent on UART3 the AT command prompt will remain active on UART1



3.36 AIR INTERFACE ENCRYPTION ALGORITHM AT+AIEALG Description

This command can be used to report the supported Air Interface Encryption algorithm loaded in the radio. It reports both the algorithm supported by the loaded Protocol Stack image and the algorithm supported by the internal AIE Co-processor. These should always report with the same number. If they are different the radio will not function and must be re-programmed with the correct Protocol Stack image to match the AIE Co-processor algorithm.

Test Syntax

AT+AIEALG=?


+AIEALG:<Protocol Stack TEA Algorithm>,<Encryption Co-processor TEA Algorithm>

Defined Values

1 – TEA1 algorithm loaded





3.37 SUBSCRIPTION SUBSCRIBER CLASS AT+SUBSCR Description

This command allows the radio to be configured with a Subscriber Class. This will become the default subscriber class used by the radio unless a new one is assigned during registration with the TETRA network.

Set Syntax

AT+SUBSCR=<Subscriber Class>

Test Syntax

AT+SUBSCR=?


+SUBSCR:<1-65535>

Defined Values

Subscriber Class – This is the decimal value of the 16 bit subscriber class bitmap defined in TETRA



3.38 REPORT BATTERY STATUS AT+BATT Description

This command reports the current battery voltage.

Read Syntax

AT+BATT?

Test Syntax

AT+BATT=?


+BATT(V*10), (0-1)

Defined Values

V*10 – Current battery voltage multiplied by 10

0-1 – Returns 1 if charger is connected.



3.39 FLASH PROGRAMMER AT+FLASHPROG Description

This command can be used to directly enter the flash programmer from the AT interface. All protocol operation on the radio will stop. To resume normal operation the radio must be powered down and up.

Set Syntax

AT+FLASHPROG



3.40 SDS-TL DELIVERY REPORTS AT+SDSTLRPT Description

This command allows the user to choose whether the radio will process received SDS-TL messages and automatically send a delivery report if one has been requested by the sender. The default behaviour is for the radio to automatically send reports

Set Syntax

AT+SDSTLRPT=<State>

Test Syntax

AT+SDSTLRPT=?


+SDSTLRPT:<0-1>

Defined Values

0 The radio will ignore the contents of an SDS-TL message

1 The radio will decode the contents of an SDS-TL message and send Delivery reports automatically (Default behaviour)



4 VOICE ENABLED MODEM

4.1.1 Implementation The PEI call control mechanism includes a call control state machine which enables and disables the appropriate voice pathways (microphone and speaker) depending upon the call state.

The voice call is set up in the normal manner, and TX grant demand and TX ceased requests generated on the AT interface by the AT+CTXD and AT+CUTXC AT commands.



5 AT INTERFACE ON UART 1 AND UART 3

5.1.1 Implementation By default when the extended command set has been enabled (using AT+PIMODE=1) upon data call setup, the traffic will automatically be routed to UART3, rather than remaining on UART1.

During the data call, any received AT command will be validated to ensure that it does not interfere with the data connection. Any AT commands that fall into this category will be rejected during this mode of operation. If a command is inhibited, then all modes of operation of that command are inhibited.

If it is required that the data traffic is sent on UART 1 (the AT command port) then the AT+PPPSPLIT command should be used. AT+PPPSPLIT=0 will cause the data traffic to appear on UART 1. All AT commands are not available whilst data is flowing. When the data session is finished and closed down AT commands can be issued once more.



6 TETRA TEST SET OUTPUT

When TETRA Test Set Mode is enabled the device will periodically output information regarding the connected TETRA network or scanning information if the device is scanning for a network. The format of the output generated depends on which TTSSCAN mode the radio is configured to use.

6.1.1 TTSSCAN=1 Mode When in this mode the radio will continuously scan the configured channel range looking for valid TETRA networks. When it finds a network it outputs some details from the SYSINFO message being broadcast by that network.

+MODLOG:Initial Cell Select: Trying channel 3680

+MODLOG:Cell Attach: Starting...

+MODLOG:Cell Attach: Got SYSINFO wait RSSI...

+MODLOG:Cell Attach: Attach successful!

+MODLOG:SYSINFO: LA:3737 Chan:3680 RSSI:79 MCC/MNC:234/78 Service Level:0:1,1,0,1,0,1,1,0,1,1,1



+MODLOG:Cell Attach: Failed no good Rx bursts



+MODLOG:Cell Attach: Got SYSINFO wait RSSI...

+MODLOG:Cell Attach: Attach successful!

+MODLOG:SYSINFO: LA:3737 TrafficChan:3763 MCCHChan:3680 RSSI:83 MCC/MNC:234/78 Service Level:0:1,1,0,1,0,1,1,0,1,1,1

In the above output TTSSCAN=1 has found two different channels from the same TETRA network. The first being the MCCH channel of a cell with a Location Area address of 3737. The measured signal strength is reported in this case it is -79dB.

The second channel found is reported slightly differently as this is a ‘Traffic Channel’ where all 4 TETRA slots are being used for either voice calls or Packet Switched Data. It can be seen that the SYSINFO message on this channel reports the channel number of the MCCH channel with which it is associated (which happens to be the MCCH found above).

In each case the Cells Service Level is reported. Most of these details are taken from the BS Service Details being reported by the SYSINFO message received from the cell. It breaks down as follows,

Service Level:a:b,c,d,e,f,g,h,i,j,k,l

a = Cell Service Level

b = Registration Required

c = De-registration Required

d = Priority Cell

e = Minimum mode service



f = Migration

g = System wide services

h = TETRA voice service

i = Circuit mode data service

j = SNDCP service

k = Air interface encryption service

l = Advanced link supported

6.1.2 TTSSCAN=2 Mode

When in this mode the radio scans and connect to a TETRA network which matches its configured MCC/MNC. It does not register and makes no uplink transmissions whatsoever. However in all other respects it behaves as if it is registered on the network. It performs neighbour cell monitoring and moves from cell to cell using the announced cell reselection parameters of the network. Periodically it reports information regarding the cell it is currently attached to and its neighbours.

+BATT:85,0

+NBLAC:11,6,3737,3822,3728,3812,683,6094,6021,3784,3780,3750,710

+NBRSSI:11,6,83,90,96,100,102,102,103,105,106,107,107

+NBCHAN:11,6,3680,3695,3692,3718,3710,3622,3630,3731,3738,3689,3762

+NBC1:11,6,27,20,14,10,8,8,7,5,4,3,3

+NBBER:6,0,432

+NBPARAMS:11,6,40,6,30,8,35,-110,432,3,3,0,0

6.1.2.1 +BATT:Voltage,Charger

This status is output every 5 seconds to indicate the condition of the device battery

Voltage = Battery voltage (x 10)

Charger = Charger connected

6.1.2.2 +NBLAC: Count, RecordNo, LAC, LAC, LAC, LAC….

This status is output every second. It announces the list of neighbour cell local area codes. The first entry in the list reports the current serving cell.



Count = Number of neighbour cells the radio is currently monitoring

RecordNo = A number which identifies the record, increments from 1-255 then wraps

LAC,LAC… = List of Local Area Codes of all current neighbour cells

6.1.2.3 +NBRSSI: Count, RecordNo, RSSI, RSSI, RSSI

This status is output every second. It announces the list of RSSIs for the serving cell and each of the neighbour cells.



RSSI,RSSI… = List of RSSI measurements from the serving cell followed by each neighbour cell (in the same order as the LAC list above)

6.1.2.4 +NBCHAN: Count, RecordNo, Channel, Channel, Channel….

This status is output every second. It announces the TETRA channel number of the serving cell followed by a list of channels for each of the neighbour cells.



Channel,Channel… = List of channel numbers, the serving cell followed by each neighbour cell (in the same order as the LAC list above)

6.1.2.5 +NBC1: Count, RecordNo, C1, C2, C2….

This status is output every second. It announces the C1 Pathloss calculated for the serving cell and each of the neighbour cells.



C1,C2,C2… = Pathloss C1 of the serving cell followed by the pathloss C2 value for each neighbour cell (in the same order as the LAC list above)

6.1.2.6 +NBBER: Count, RecordNo, BER, RDC

This status is output every second. It announces the current Block Error Rate calculated for downlink received bursts from the serving cell.



BER = Current BER averaged over the last 10 seconds

RDC = Current Radio Downlink Counter in the radio. This counter is defined in TETRA and is used to force a cell reselection if the downlink error rate is too high (when the counter reaches 0)



6.1.2.7 +NPARAMS: : Count, RecordNo,Param1, Param2…..

This status is output every second. It announces various cell reselection parameters which are being broadcast from the current serving cell. Full details of these parameters and there meaning is available in the TETRA Air Interface specification.



Param1 = Slow Reselect Threshold

Param2 = Slow Reselect Hysteresis

Param3 = Fast Reselect Threshold

Param4 = Fast Reselect Hysteresis

Param5 = Tx Power Max Cell

Param6 = Rx Minimum Access Level

Param7 = Radio Downlink Timeout

Param8 = Frequency Band

Param9 = Frequency Offset

Param10 = Reverse Operation

Param11 = Number of Secondary Control Channels

tmc-210 pei-ext - tetramodem · 2021. 2. 4. · funk-electronic piciorgros gmbh tmc-210 / tam-200...

Documents