TMC-200 TAM-200 TETRA Modem Core V1.10, June 2016

Transcription

1 TMC-200 TAM-200 TETRA Modem Core V1.10, June 2016 Funk-Electronic Piciorgros GmbH Claudiastrasse Cologne Germany

2 Funk-Electronic Piciorgros GmbH TMC-200 / TAM-200 Content 1 INTRODUCTION Overview Safety Precautions Disclaimer Software Versions Functions and Features TMC-200 versions HARDWARE INFORMATION Mechanical Details Power supply Main connector and layout considerations Main connector - Connection table Antenna connections LED Functions INTERFACES PEI interface (UART 1) PPP interface (UART 3) Service interface (UART 2) User modes TMC-200 EVALUATION BOARD SPECIFICATIONS TMC TAM-200 MODEM Overview LED Functions Pin connector assignment Mechanical Drawing Specifications TAM CONFIGURATION EXAMPLES Basic TETRA configuration Sending and receiving an SDS message Packet data connections UPDATING THE TMC-200 / TAM Preparations Software versions and TEA version Updating the firmware Initiate the update sequence Deletion of the Flash areas Programming the new software versions Finishing the software update APPENDIX PEI COMMANDS AND EKIT DRAWINGS V Page 2 of 45

3 Funk-Electronic Piciorgros GmbH TMC-200 / TAM Introduction 1.1 Overview This document contains information about installation, settings and operation of the TMC-200 TETRA Modem Core and the TAM-200 TETRA modem. Additional information is also available on the Internet, at the website 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 V Page 3 of 45

4 Funk-Electronic Piciorgros GmbH TMC-200 / TAM-200 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 in the login area. 1.4 Software and Document Versions The software (firmware) versions and document editions history is listed below: Firmware Version Stack: 3.23 DSP: 3.23 MMI: 3.07 Stack: 3.35 DSP: 3.29 MMI: 3.11 Document Version Comments / Changes 1.0 First Release 1.10 Firmware: Improvements in AIE / Authentication handling Combined PPP mode on one UART supported in PIMODE (AT+PPPSPLIT=0) Escape Sequence "+++" for PPP mode added Documentation: Final description of the TAM-200 of the TMC-200 EKit added Corrections in the TMC-200 area Configuration examples and software update instructions added Reference schematics of the TMC-200 EKit added PEI documentation updated TMC-200 UART1 & UART3 RTS/CTS direction corrected V Page 4 of 45

5 Funk-Electronic Piciorgros GmbH TMC-200 / TAM Functions and Features The TMC-200 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 The AF output power is about 150 mw at 8 Ohm and can directly drive a speaker or an external Power Amplifier. The TMC-200 is available for 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-200 versions The standard version of the TMC-200 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-200/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-200: One for the frequency range MHz, and one for the 800 MHz band. The frequency version must be provided with the order. V Page 5 of 45

6 Funk-Electronic Piciorgros GmbH TMC-200 / TAM Hardware Information 2.1 Mechanical Details The TMC-200 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-200 except the antenna connections, which are available via a MMCX connectors. The total size of the TMC-200 is 87mm x 56mm x 10mm (excluding mounting straps). 2.2 Power supply The TMC-200 needs two power supplies: A 9.6V rail (-0.1/+0.4V) 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.6V 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. V Page 6 of 45

7 Funk-Electronic Piciorgros GmbH TMC-200 / TAM 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 DF12(5.0)-50DP-0.5V(86). The TMC-200 is fixed on the application board by 3 mounting straps. For easy fixing, the insert nut "Multisert 0006M2,5" is recommended (Manufacturer: KVT Fastening, 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. V Page 7 of 45

8 Funk-Electronic Piciorgros GmbH TMC-200 / TAM Main connector - Connection table Pin Name Remark 1-8 VCC_PA 9.6V 9.6V power supply, 3A. 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 44 OK LED Connection for the OK-LED Optional: SIM-RST for E2EE version V Page 8 of 45

9 Funk-Electronic Piciorgros GmbH TMC-200 / TAM-200 Pin Name Remark 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-200. 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-200 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-200 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 V Page 9 of 45

10 Funk-Electronic Piciorgros GmbH TMC-200 / TAM 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 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 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-200 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). V Page 10 of 45

11 Funk-Electronic Piciorgros GmbH TMC-200 / TAM User modes The TMC-200 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-200 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. V Page 11 of 45

12 Funk-Electronic Piciorgros GmbH TMC-200 / TAM TMC-200 Evaluation Board The TMC-200 Evaluation Board (EKit) provides a fast and easy way to make the first steps in software development for the TMC-200. The Board comes with a wall-plug power supply and generates the needed voltages for the TMC-200. It has also all 3 UARTS ready for plug into a computer on DB9 connectors. The schematics of the TMC-200 EKit is provided as an appendix to this document. You can also use this as a reference for the power supply design. V Page 12 of 45

13 Funk-Electronic Piciorgros GmbH TMC-200 / TAM Specifications TMC-200 Functions: TETRA AT-modem for serial and IP communication Alarm device for SDS and status messages TETRA voice terminal Available frequency ranges: Serial Interfaces Indications: 370 MHz MHz 806 MHz MHz UART 1: AT command port UART 3: Packet data port (in enhanced mode) UART 2: Service and update port 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 dbm) Dynamic Receiver sensitivity: Min dbm (Typ: -107 dbm) RF Conformance EN EMC Conformance EN and -18 ESD Conformance Special options: Embedded GPS-Receiver End-to-End-Encryption Stand-alone voice mode User applications Power supply voltage: Current in receive mode: Current in transmit mode: 9.6 V DC (max. 3A) and 5 V DC (max. 500mA) ~ 300mA ~ 800mA in average at 1-slot operation Peaks may go up to 3 A on the 9.6V supply rail Operating Temperature: -20 C to +65 C Enclosure: Dimensions: Anodized aluminum 87mm x 56mm x 10mm (excluding antenna connectors and mechanical installation straps) V Page 13 of 45

14 Funk-Electronic Piciorgros GmbH TMC-200 / TAM-200 TAM-200 TETRA AT modem Funk-Electronic Piciorgros GmbH Claudiastrasse Cologne Germany V Page 14 of 45

15 Funk-Electronic Piciorgros GmbH TMC-200 / TAM TAM-200 Modem 6.1 Overview The TAM-200 packs the TMC-200 into a metal enclosure with a wide range power supply for 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-200 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 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-200 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-200 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 V Page 15 of 45

16 Funk-Electronic Piciorgros GmbH TMC-200 / TAM 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! V Page 16 of 45

17 Funk-Electronic Piciorgros GmbH TMC-200 / TAM-200 Connection table: Pin Name Remark 1 GND Negative Supply 2 RTS Hardware handshake input, V.24 / RS CTS Hardware handshake output, V.24 / RS 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. / 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. V Page 17 of 45

18 Funk-Electronic Piciorgros GmbH TMC-200 / TAM Mechanical Drawing V Page 18 of 45

19 Funk-Electronic Piciorgros GmbH TMC-200 / TAM 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: Serial Interfaces Indications: 370 MHz MHz 806 MHz MHz UART 1: AT command port (RS-232 level) UART 2: Service and update port (4pin inside the TAM, TAM-200 programming cable needed) 6 LED providing information about operating status and RSSI field strength TETRA features: Transmission Power: Static Receiver sensitivity: Dynamic Receiver sensitivity: SDS, Status, SCCH, Packet Data, Multi Slot Packet Data, SDS size up to 2047 bit, Air Interface Encryption (Class 2/3), Authentication, Voice Interface Up to 3 Watts (Class Min. -112dBm (Typ dbm) Min dbm (Typ: -107 dbm) RF Conformance EN EMC Conformance EN and -18 ESD Conformance Special options: Connectors: User applications Removable screw connector, 6pin Antenna: BNC Power supply voltage: 9-24 V DC, +- 20% Consumption in receive mode: ~ 1W Consumption in transmit ~ 3W in average at 1-slot operation mode: Peaks may go up to 15W! Operating Temperature: -20 C to +65 C Enclosure: Dimensions: Metal enclosure 162mm x 65mm x 31mm (excluding connectors) V Page 19 of 45

20 Funk-Electronic Piciorgros GmbH TMC-200 / TAM Configuration examples All configuration of the TMC-200/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). V Page 20 of 45

21 Funk-Electronic Piciorgros GmbH TMC-200 / TAM 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-200 after power up: +BOOTSTART +SWVER:0334,0311,0329 +CREG:0 +CREG:0 +CSLOT:1 +CREG:0,0,0 The "+SWVER:" message reports the software versions of the TMC-200 in the oder Stack, MMI, DSP. This TMC-200 has these versions: Stack: MMI: DSP: 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 V Page 21 of 45

22 Funk-Electronic Piciorgros GmbH TMC-200 / TAM-200 at+pimode=1 OK at+cnetcon=262,1,1005 OK at+cchan=0, ,50 OK at+cfun=1,1 MS Rebooting +BOOTSTART +SWVER:0334,0311,0329 +CREG:0 +CSLOT:1 +CREG: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 V Page 22 of 45

23 Funk-Electronic Piciorgros GmbH TMC-200 / TAM 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 We need to submit these command to the modem: at+cmgs=1001,128 (There is a CRLF after this line) C6C6F20776F726C6421 (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 The second line is the data including the TL-4 header: " " 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) V Page 23 of 45

24 Funk-Electronic Piciorgros GmbH TMC-200 / TAM-200 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, C6C6F B 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 (" ") and the text payload "Hello back" ("48656C6C6F B"). V Page 24 of 45

25 Funk-Electronic Piciorgros GmbH TMC-200 / TAM 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: V Page 25 of 45

26 Funk-Electronic Piciorgros GmbH TMC-200 / TAM-200 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#". V Page 26 of 45

27 Funk-Electronic Piciorgros GmbH TMC-200 / TAM-200 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 V Page 27 of 45

28 Funk-Electronic Piciorgros GmbH TMC-200 / TAM-200 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. V Page 28 of 45

29 Funk-Electronic Piciorgros GmbH TMC-200 / TAM-200 Close all windows with "OK", the connections are prepared on the PC. The TMC-200/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 hardand 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-200/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" V Page 29 of 45

30 Funk-Electronic Piciorgros GmbH TMC-200 / TAM-200 If the TETRA infrastructure needs a PAP/CHAP username and password for the PPP connection, enter these credentials here. Then click "dial". V Page 30 of 45

31 Funk-Electronic Piciorgros GmbH TMC-200 / TAM-200 And finally the PPP connection is established: On the TAM-200 and the TMC-200 this is indicated by a solid blue "PPP" LED: V Page 31 of 45

32 Funk-Electronic Piciorgros GmbH TMC-200 / TAM Updating the TMC-200 / 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-200 firmware package folder "TETRA V3." A TAM-200 programming cable if the update should be performed on the TAM Preparations The serial interface of the computer must be connected to the UART2 service port of the TMC-200. 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-200 evaluation board, connect the serial interface to the UART2 DB9- connector. V Page 32 of 45

33 Funk-Electronic Piciorgros GmbH TMC-200 / TAM-200 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 bps, No flow control: Connect the serial interface by clicking on the green triangle: Select View Terminal V Page 33 of 45

34 Funk-Electronic Piciorgros GmbH TMC-200 / TAM-200 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: V Page 34 of 45

35 Funk-Electronic Piciorgros GmbH TMC-200 / TAM 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: 0329 Version 3.29 Stack Version: F334 Version F3.34 MMI version: 0311 Version 3.11 AIE version: b002ae1 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! V Page 35 of 45

36 Funk-Electronic Piciorgros GmbH TMC-200 / TAM 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 V3 S0334-M0311-D0329" contains these versions: Stack: 3.34 MMI: 3.11 DSP: 3.29 In case a new software is released, you can compare the software versions of the firmware folder with the versions in the TMC-200/TAM-200. Only changed versions must be updated! Initiate the update sequence To start the update sequence power down the TMC-200/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! V Page 36 of 45

37 Funk-Electronic Piciorgros GmbH TMC-200 / TAM Deletion of the Flash areas All software areas which should be updated must be erased first. MMI: Choose Target Flash Erase MMI MMI Code If you're not getting these messages, ending with "+FLSHRDY: MMI Erased" you need to repeat the sequence. V Page 37 of 45

38 Funk-Electronic Piciorgros GmbH TMC-200 / TAM-200 Stack: Choose Target Flash Erase Protocol Stack and OS If you're not getting these messages, ending with "+FLSHRDY: Stack Erased" you need to repeat the sequence. V Page 38 of 45

39 Funk-Electronic Piciorgros GmbH TMC-200 / TAM-200 DSP: Choose Target Flash Erase DSP Stack Mode If you're not getting these messages, ending with "+FLSHRDY: 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! V Page 39 of 45

40 Funk-Electronic Piciorgros GmbH TMC-200 / TAM 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: V Page 40 of 45

41 Funk-Electronic Piciorgros GmbH TMC-200 / TAM-200 MMI: Select the file "firmware_mmi.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: MMI code sector checksum OK" V Page 41 of 45

42 Funk-Electronic Piciorgros GmbH TMC-200 / TAM-200 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: Stack_OS code sector checksum OK" V Page 42 of 45

43 Funk-Electronic Piciorgros GmbH TMC-200 / TAM-200 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: DSP code sector checksum OK" V Page 43 of 45

44 Funk-Electronic Piciorgros GmbH TMC-200 / TAM 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. V Page 44 of 45

45 Funk-Electronic Piciorgros GmbH TMC-200 / TAM Appendix PEI commands and EKit drawings On the following pages the AT commands for the standard and extended mode are listed. V Page 45 of 45

46 TM-one Tetra Modem PEI User Guide Funk-Electronic Piciorgros GmbH Claudiastr Köln

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

48 PEI Users Guide 2. Contents 3.1. Purpose Scope References Glossary Command Mode Circuit Mode Data State Reception and Connection Transmission control in a half-duplex call Call Termination Reception and Connection Call Termination Switching Between a Call and Command Mode Commands A/ Repeat Last Command AT Attention Command ATA Answer Call ATD- Dial ATE- Echo <cr><lf>ok<cr><lf>ath- Hook <cr><lf>error<cr><lf>ato- Return to online data state ATQ- Result Code ATS0 - Automatic answer ATS2 - Escape character ATS3 - Command line termination character ATS4 - Command line termination character ATS5 - Command line editing character ATV-Command : Response format ATZ-Command : Reset to default configuration CBC : Return Battery information CEER : Return the Reason for failure CME: MT Error result Code CMEE: Report MT error CMGD: Delete message CMGF: Set Message Format CMGL:List messages CMGR: Read message CMGS: Send message SDS Examples Status Message Transmission Example 40 June 2016 Page 3 of 70

49 PEI Users Guide Status Message Reception Example Simple SDS-TL protocol transmission example Simple SDS-TL protocol reception example CNUM: Get MT TETRA Identities CREG: Network Registration CTOM : Set Operating Mode CTGS: Group Set Up CSQ: Signal quality CTSDC: Tetra Service Definition CTSDS: Tetra Service Definition for SDS Service CTSTR: Tetra Status Text Read CTXD: Transmit Demand CUTXC: Up Transmit Ceased GCAP: Request complete capabilities list GMI : Request manufacturer identification GMM : Request model identification GMR : Request revision identification CMCC : Mobile Network Code CMNC : Mobile Network Code CCHN: Main Control Channel CLAI: Serving Cell Location Area ID CNLA: Neighbour Cell Location Area ID Unsolicited Responses CMTI: New message indication CTICN: Tetra Incoming call progress CTSDSR: Unsolicited SDS indication CTOCP: Tetra Outgoing Call Progress CTCR: Tetra Call Release CTXG: Transmission Grant CDTXC: Down Transmission Ceased Errors Within Tetra PEI Responses to commands 70 June 2016 Page 4 of 70

50 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 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 References 1. Extended AT Command Set 2. ITU V ETSI specification ETS (v2.1.1) Glossary ASCII AT CR DMO DSP GUI ITU LF LSB MMI MT OS PABX PEI PSTN SwMI TBD TE American Standard Code for Information Interchange Attention Carriage Return Direct Mode Operation Digital Signal Processor Graphical User Interface International Telecommunications Union Line Feed Least Significant Bit Man Machine Interface Mobile Terminal Operating System Private Automatic Branch Exchange Peripheral Equipment Interface Public Switched Telephone Network Switching and Management Infrastructure To be defined Terminal Equipment June 2016 Page 5 of 70

51 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) 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. June 2016 Page 6 of 70

52 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. June 2016 Page 7 of 70

53 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 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. June 2016 Page 8 of 70

54 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) June 2016 Page 9 of 70

55 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 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 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". June 2016 Page 10 of 70

56 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) 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 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. June 2016 Page 11 of 70

57 PEI Users Guide 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. June 2016 Page 12 of 70

58 PEI Users Guide Example of Message Flow for a Half-Duplex Data/Voice Call TE MT SWMI MT TE AT+CTSDC SetUp OK ATD U-SETUP D-CALL-PROC D-ALERT D-SETUP +CTICN ATA U-CONNECT +CTOCP D-CONNECT D-CONNECT-ACK +CTCC +CTXG OK +CTXG OK End Tx +CDTXC D-TX-CEASED U-TX-CEASED D-TX-CEASED AT+CUTXC OK +CDTXC AT+CTXD Next Tx OK U-TX-DEMAND D-TX-GRANTED D-TX-GRANTED +CTXG +CTXG AT+CUTXC OK U-TX-CEASED +CDTXC D-TX-CEASED D-TX-CEASED +CDTXC ATH U-DISCONNECT Clear +CTCR D-RELEASE D-RELEASE +CTCR OK June 2016 Page 13 of 70

59 PEI Users Guide 11. STANDARD PEI AT COMMAND SET OVERVIEW Commands A/ Repeat Last Command 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/ AT Attention Command This command Checks whether PEI is in Command mode or not. Execution Syntax AT ATA Answer Call 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> June 2016 Page 14 of 70

60 PEI Users Guide ATD- Dial 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) 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 +CTCR Test Response <cr><lf>ok<cr><lf> Example ATD20550<cr> <cr><lf>connect<cr><lf> 8 If connection could not be established due to called system is not ready Release cause of call disconnection. June 2016 Page 15 of 70

61 PEI Users Guide ATE- Echo 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> June 2016 Page 16 of 70

62 PEI Users Guide <cr><lf>ok<cr><lf>ath- Hook 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 In call on PEI Not in a call controlled by PEI Response +CTCR: <Params> ERROR Test Response <cr><lf>ok<cr><lf> Example : ATH0<cr> <cr><lf>+ctcr: 123,0<cr><lf> ATH1<cr> June 2016 Page 17 of 70

63 PEI Users Guide <cr><lf>error<cr><lf>ato- Return to online data state 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 Data Call active, but interface in command mode. Call successfully resumed Not in a data call on this PEI which has been escaped Response CONNECT ERROR Test Response <cr><lf>ok<cr><lf> Example : ATO<cr> <cr><lf>connect<cr><lf> June 2016 Page 18 of 70

64 PEI Users Guide ATQ- Result Code 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> June 2016 Page 19 of 70

65 PEI Users Guide ATS0 - Automatic answer 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> June 2016 Page 20 of 70

66 PEI Users Guide ATS2 - Escape character 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 = 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> June 2016 Page 21 of 70

67 PEI Users Guide ATS3 - Command line termination character 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 = 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> June 2016 Page 22 of 70

68 PEI Users Guide ATS4 - Command line termination character 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 = 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> June 2016 Page 23 of 70

69 PEI Users Guide ATS5 - Command line editing character 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 = 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> June 2016 Page 24 of 70

70 PEI Users Guide ATV-Command : Response format 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> June 2016 Page 25 of 70

71 PEI Users Guide ATZ-Command : Reset to default configuration 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 ERROR If value is recognized. 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 June 2016 Page 26 of 70

72 PEI Users Guide CBC : Return Battery information 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> June 2016 Page 27 of 70

73 PEI Users Guide CEER : Return the Reason for failure 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> June 2016 Page 28 of 70

74 PEI Users Guide CME: MT Error result Code 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 June 2016 Page 29 of 70

75 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> June 2016 Page 30 of 70

76 PEI Users Guide CMEE: Report MT error 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 June 2016 Page 31 of 70

77 PEI Users Guide CMGD: Delete message 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 = Low protection 4,8 kbit/s medium interleaving depth = Low protection 4,8 kbit/s long interleaving depth = High protection 2,4 kbit/s short interleaving depth = High protection 2,4 kbit/s medium interleaving depth = High protection 2,4 kbit/s high interleaving depth = Packet Data 9 - SDS type 1 (16 bits) 10 - SDS type 2 (32 bits) 11 - SDS type 3 (64 bits) 12 - SDS type 4 ( bits) 13 - Status (16 bits, some values are reserved in EN [2]) <message index> It has the range 0-65,535. Example : AT+CMGD=0,1,<cr> <cr><lf>ok<cr><lf> June 2016 Page 32 of 70

78 PEI Users Guide CMGF: Set Message Format 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. June 2016 Page 33 of 70

79 PEI Users Guide CMGL:List messages 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 = Low protection 4,8 kbit/s medium interleaving depth = Low protection 4,8 kbit/s long interleaving depth = High protection 2,4 kbit/s short interleaving depth = High protection 2,4 kbit/s medium interleaving depth = High protection 2,4 kbit/s high interleaving depth = Packet Data 9 - SDS type 1 (16 bits) 10 - SDS type 2 (32 bits) 11 - SDS type 3 (64 bits) 12 - SDS type 4 ( bits) 13 - Status (16 bits, some values are reserved in EN [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 June 2016 Page 34 of 70

80 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> June 2016 Page 35 of 70

81 PEI Users Guide CMGR: Read message 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 = Low protection 4,8 kbit/s medium interleaving depth = Low protection 4,8 kbit/s long interleaving depth = High protection 2,4 kbit/s short interleaving depth = High protection 2,4 kbit/s medium interleaving depth = High protection 2,4 kbit/s high interleaving depth = Packet Data 9 - SDS type 1 (16 bits) 10 - SDS type 2 (32 bits) 11 - SDS type 3 (64 bits) 12 - SDS type 4 ( bits) 13 - Status (16 bits, some values are reserved in EN [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> June 2016 Page 36 of 70

82 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 Area Area Area Area Area Area Area Area Area Area Area Area Area 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 " ": - 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>. June 2016 Page 37 of 70

83 PEI Users Guide CMGS: Send message The command will send a data message to the MT over the PEI. The SDS type (<AI service>, <area>, <e-toe 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". June 2016 Page 38 of 70

84 PEI Users Guide For example, for a data field of " ": - 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> June 2016 Page 39 of 70

85 PEI Users Guide 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 AI Service Called Party Area Access Priority End to end Message Identity Type encryption Parameters Command AT+CTSDS Send Message Destination Data Length Status Number Command Identity 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 (7BFF Hex) are reserved by the TETRA standard, to (7C00 to 7FFF Hex) are for use by SDS-TL and to (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 FE00 FE01 Meaning Status Message Delivered 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 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, Status Message Reception Example The following shows how a Status message is received +CMTI:13,1,0 80E8 June 2016 Page 40 of 70

86 PEI Users Guide 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 : AT+CTSDS=12,0,0,0,0<CR><LF> <CR><LF> OK<CR><LF> AT+CMGS=607501,56<CR><LF> C6C6F<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 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> C6C6F <CR><LF> June 2016 Page 41 of 70

87 PEI Users Guide CNUM: Get MT TETRA Identities 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, ,<cr><lf> 1, ,<cr><lf> 1, ,<cr><lf> 2, <cr><lf> 3, <cr><lf> <cr><lf>ok<cr><lf> June 2016 Page 42 of 70

88 PEI Users Guide CREG: Network Registration 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. 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> 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 <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) Example AT+CREG?<CR> <cr><lf>+creg: 1,0,0<cr><lf> <cr><lf>ok<cr><lf> June 2016 Page 43 of 70

89 PEI Users Guide CTOM : Set Operating Mode 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> June 2016 Page 44 of 70

90 PEI Users Guide CTGS: Group Set Up 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 Scan priority Scan priority Scan priority Scan priority 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> June 2016 Page 45 of 70

91 PEI Users Guide CSQ: Signal quality 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 3 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> and the current internal temperature of the RF power amplifier <PA Temp>. 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> Example : AT+CSQ<CR> <cr><lf>+csq: 89,7<cr><lf> <cr><lf>ok<cr><lf> June 2016 Page 46 of 70

92 PEI Users Guide CTSDC: Tetra Service Definition 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 = Low protection 4,8 kbit/s medium interleaving depth = Low protection 4,8 kbit/s long interleaving depth = High protection 2,4 kbit/s short interleaving depth = High protection 2,4 kbit/s medium interleaving depth = High protection 2,4 kbit/s high interleaving depth = Packet Data 9 - SDS type 1 (16 bits) 10 - SDS type 2 (32 bits) 11 - SDS type 3 (64 bits) 12 - SDS type 4 ( bits) 13 - Status (16 bits, some values are reserved in EN [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 Area Area Area 4 June 2016 Page 47 of 70

93 PEI Users Guide 5 - Area Area Area Area Area Area Area Area Area Area 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 Priority Priority Priority Priority Priority Priority Priority Priority Priority 10 (Default) 11 - Priority Priority Priority Priority Priority 15 June 2016 Page 48 of 70

94 PEI Users Guide <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> June 2016 Page 49 of 70

95 PEI Users Guide CTSDS: Tetra Service Definition for SDS Service 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 = Low protection 4,8 kbit/s medium interleaving depth = Low protection 4,8 kbit/s long interleaving depth = High protection 2,4 kbit/s short interleaving depth = High protection 2,4 kbit/s medium interleaving depth = High protection 2,4 kbit/s high interleaving depth = Packet Data 9 - SDS type 1 (16 bits) 10 - SDS type 2 (32 bits) 11 - SDS type 3 (64 bits) 12 - SDS type 4 ( bits) 13 - Status (16 bits, some values are reserved in EN [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 Area Area Area Area Area Area Area Area Area Area 11 June 2016 Page 50 of 70

96 PEI Users Guide 12 - Area Area Area 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> June 2016 Page 51 of 70

97 PEI Users Guide CTSTR: Tetra Status Text Read. 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 = Low protection 4,8 kbit/s medium interleaving depth = Low protection 4,8 kbit/s long interleaving depth = High protection 2,4 kbit/s short interleaving depth = High protection 2,4 kbit/s medium interleaving depth = High protection 2,4 kbit/s high interleaving depth = Packet Data 9 - SDS type 1 (16 bits) 10 - SDS type 2 (32 bits) 11 - SDS type 3 (64 bits) 12 - SDS type 4 ( bits) 13 - Status (16 bits, some values are reserved in EN [2]) June 2016 Page 52 of 70

98 PEI Users Guide CTXD: Transmit Demand 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> June 2016 Page 53 of 70

99 PEI Users Guide CUTXC: Up Transmit Ceased. 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> June 2016 Page 54 of 70

100 PEI Users Guide GCAP: Request complete capabilities list 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 Reserved 20 - Status 21 - SDS type SDS type SDS type SDS type 4 (not SDS-TL) Reserved 30 - PV IPV Reserved June 2016 Page 55 of 70

101 PEI Users Guide GMI : Request manufacturer identification 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. June 2016 Page 56 of 70

102 PEI Users Guide GMM : Request model identification 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 The response from the terminal depends on the terminal type. The options are: +GMM: T-one(TETRA Module) +GMM: TM-ONE(TETRA Modem) Implementation The result string is presently set as T-one (TETRA Module) or TM-ONE (TETRA Modem) Test Response <cr><lf>ok<cr><lf> Example : AT+GMM<cr> <cr><lf>+gmm: TM100<cr><lf> <cr><lf>ok<cr><lf> June 2016 Page 57 of 70

103 PEI Users Guide GMR : Request revision identification 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> June 2016 Page 58 of 70

104 PEI Users Guide CMCC : Mobile Network Code 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> June 2016 Page 59 of 70

105 PEI Users Guide CMNC : Mobile Network Code 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> CCHN: Main Control Channel 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> June 2016 Page 60 of 70

106 PEI Users Guide CLAI: Serving Cell Location Area ID 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> CNLA: Neighbour Cell Location Area ID 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> June 2016 Page 61 of 70

107 PEI Users Guide Unsolicited Responses CMTI: New message indication 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 = Low protection 4,8 kbit/s medium interleaving depth = Low protection 4,8 kbit/s long interleaving depth = High protection 2,4 kbit/s short interleaving depth = High protection 2,4 kbit/s medium interleaving depth = High protection 2,4 kbit/s high interleaving depth = Packet Data 9 - SDS type 1 (16 bits) 10 - SDS type 2 (32 bits) 11 - SDS type 3 (64 bits) 12 - SDS type 4 ( bits) 13 - Status (16 bits, some values are reserved in EN [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 " ": - 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>. June 2016 Page 62 of 70

108 PEI Users Guide CTICN: Tetra Incoming call progress. 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 = Low protection 4,8 kbit/s medium interleaving depth = Low protection 4,8 kbit/s long interleaving depth = High protection 2,4 kbit/s short interleaving depth = High protection 2,4 kbit/s medium interleaving depth = High protection 2,4 kbit/s high interleaving depth = Packet Data 9 - SDS type 1 (16 bits) 10 - SDS type 2 (32 bits) 11 - SDS type 3 (64 bits) 12 - SDS type 4 ( bits) 13 - Status (16 bits, some values are reserved in EN [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. June 2016 Page 63 of 70

109 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 June 2016 Page 64 of 70

110 PEI Users Guide 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 = Low protection 4,8 kbit/s medium interleaving depth = Low protection 4,8 kbit/s long interleaving depth = High protection 2,4 kbit/s short interleaving depth = High protection 2,4 kbit/s medium interleaving depth = High protection 2,4 kbit/s high interleaving depth = Packet Data 9 - SDS type 1 (16 bits) 10 - SDS type 2 (32 bits) 11 - SDS type 3 (64 bits) 12 - SDS type 4 ( bits) 13 - Status (16 bits, some values are reserved in EN [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. June 2016 Page 65 of 70

111 PEI Users Guide CTOCP: Tetra Outgoing Call Progress. 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 = Low protection 4,8 kbit/s medium interleaving depth = Low protection 4,8 kbit/s long interleaving depth = High protection 2,4 kbit/s short interleaving depth = High protection 2,4 kbit/s medium interleaving depth = High protection 2,4 kbit/s high interleaving depth = Packet Data 9 - SDS type 1 (16 bits) 10 - SDS type 2 (32 bits) 11 - SDS type 3 (64 bits) 12 - SDS type 4 ( bits) 13 - Status (16 bits, some values are reserved in EN [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 2 - Point to multipoint (acknowledged) June 2016 Page 66 of 70

112 PEI Users Guide 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 CTCR: Tetra Call Release. 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 June 2016 Page 67 of 70

113 PEI Users Guide CTXG: Transmission Grant. 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>. June 2016 Page 68 of 70

114 PEI Users Guide CDTXC: Down Transmission Ceased 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. June 2016 Page 69 of 70

115 PEI Users Guide Errors Within Tetra PEI 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 June 2016 Page 70 of 70

116 TM-one Tetra Modem Extended AT Command Set Funk-Electronic Piciorgros GmbH Claudiastr Köln