Tait TM8100 mobiles User manual

TM8100 mobiles
TM8200 mobiles
Computer-Controlled
Data Interface (CCDI)
Protocol Manual
MMA-00038-02
Issue 2
April 2007

2TM8100/TM8200 Computer-Controlled Data Interface (CCDI) Protocol Manual
© Tait Electronics Limited April 2007
Contact Information
Tait Radio Communications
Corporate Head Office
Tait Electronics Limited
P.O. Box 1645
Christchurch
New Zealand
For the address and telephone number of regional
offices, refer to the TaitWorld website:
We b s i t e : http://www.taitworld.com
Technical Support
For assistance with specific technical issues, contact
Technical Support:
E-mail: [email protected]
We b s i t e : http://support.taitworld.com
Copyright and Trademarks
All information contained in this manual is the property
of Tait Electronics Limited. All rights reserved.
This manual may not, in whole or in part, be copied,
photocopied, reproduced, translated, stored, or reduced
to any electronic medium or machine-readable form,
without prior written permission from Tait Electronics
Limited.
The word TAIT and the TAIT logo are trademarks of
Tait Electronics Limited.
All trade names referenced are the service mark,
trademark or registered trademark of the respective
manufacturers.
Disclaimer
There are no warranties extended or granted by this
manual. Tait Electronics Limited accepts no
responsibility for damage arising from use of the
information contained in the manual or of the
equipment and software it describes. It is the
responsibility of the user to ensure that use of such
information, equipment and software complies with the
laws, rules and regulations of the applicable
jurisdictions.
Enquiries and Comments
In the interests of improving the performance, reliability
or servicing of the equipment, Tait Electronics Limited
reserves the right to update the equipment or this
manual or both without prior notice.
Updates of Manual and Equipment
In the interests of improving the performance, reliability
or servicing of the equipment, Tait Electronics Limited
reserves the right to update the equipment or this
manual or both without prior notice.
Intellectual Property Rights
This product may be protected by one or more patents
of Tait Electronics Limited together with their
international equivalents, pending patent applications
and registered trade marks: NZ338097, NZ508054,
NZ508340, NZ508806, NZ508807, NZ509242,
NZ509640, NZ509959, NZ510496, NZ511155,
NZ511421, NZ516280/519742, NZ519118,
NZ519344, NZ520650/537902, NZ522236,
NZ524369, NZ524378, NZ524509, NZ524537,
NZ524630, NZ530819, NZ534475, NZ534692,
NZ535471, NZ536945, NZ537434, NZ546295,
NZ547713, NZ521450, AU2003281447,
AU2002235062, AU2004216984, AU2005207405,
CA2439018, CA2554213, EU03784706.8,
EU02701829.0, EU04714053.8, EU05704655.9,
GB23865476, GB2386010, GB2413249,
GB0516092.4, US11,232716, US10/597339, US10/
520827, US10/468740, US5,745,840, US10/547653,
US10/546696, US10/547964, US10/523952, US11/
572700.
To Our European Customers
Tait Electronics Limited is an
environmentally responsible company
which supports waste minimization and
material recovery. The European Union’s
Waste Electrical and Electronic Equipment
Directive requires that this product be disposed of
separately from the general waste stream when its
service life is over. Please be environmentally
responsible and dispose through the original supplier,
your local municipal waste “separate collection” service,
or contact Tait Electronics Limited.

TM8100/TM8200 Computer-Controlled Data Interface (CCDI) Protocol Manual 3
© Tait Electronics Limited April 2007
Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Scope of Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Associated Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Publication Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Alert Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1 CCDI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.1 Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
1.2 Serial Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
1.2.1 Data Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
1.2.2 Logic Level Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1.2.3 GPS Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1.2.4 MAP27 Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1.3 Before Operating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
1.4 Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
1.5 Programming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
1.6 CCDI Flow Control. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
1.6.1 XON/XOFF Software Flow Control. . . . . . . . . . . . . . . . . . . . . . . . . 15
1.6.2 Hardware Flow Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
1.7 CCDI Transparent Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
1.7.1 Entering Transparent Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
1.7.2 Exiting Transparent Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
1.7.3 Transparent Mode Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
1.8 Command Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
1.8.1 Entering Command Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
1.8.2 CCDI Command Prompt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
1.8.3 CCDI Command Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
1.8.4 Restrictions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
1.8.5 Calculating the CCDI [CHECKSUM]. . . . . . . . . . . . . . . . . . . . . . . . 20
1.9 Commands to the Radio. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
1.9.1 CANCEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
1.9.2 DIAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
1.9.3 FUNCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
1.9.4 GO_TO_CHANNEL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
1.9.5 QUERY. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
1.9.6 SEND_ADAPTABLE_SDM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
1.9.7 SEND_SDM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
1.9.8 TDMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
1.9.9 TRANSPARENT (FFSK and THSD) . . . . . . . . . . . . . . . . . . . . . . . . 38
1.10 Messages from the Radio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
1.10.1 CCTM_QUERY_RESULTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
1.10.2 ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

4TM8100/TM8200 Computer-Controlled Data Interface (CCDI) Protocol Manual
© Tait Electronics Limited April 2007
1.10.3 GET_SDM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
1.10.4 MODEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
1.10.5 PROGRESS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
1.10.6 QUERY_DISPLAY_RESPONSE . . . . . . . . . . . . . . . . . . . . . . . . . . 47
1.10.7 RADIO_SERIAL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
1.10.8 RADIO_VERSIONS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
1.10.9 RING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
1.10.10TDMA_DATA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
1.10.11TRANSACTION OK. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
2 CCR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
2.1 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
2.1.1 Configurable Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
2.1.2 Potential Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
2.2 Programmable Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
2.2.1 Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
2.3 Command Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
2.4 Command Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
2.4.1 Message Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
2.4.2 Calculating [CHECKSUM]. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
2.5 CCR Mode Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
2.5.1 Entering CCR Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
2.5.2 CCR/CCDI Mode Independence. . . . . . . . . . . . . . . . . . . . . . . . . . . 57
2.5.3 CCR Mode Activated. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
2.5.4 CCR Mode Busy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
2.5.5 Blocked Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
2.5.6 CCR Persistence. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
2.5.7 CCR Response Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
2.5.8 Exiting CCR Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
2.6 CCR Positive Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
2.7 CCR Negative Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
2.7.1 Invalid CCR Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
2.7.2 Validation Checksum Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
2.7.3 Invalid Validation Command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
2.7.4 Validation Parameter Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
2.7.5 Radio Busy Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
2.7.6 Command Not Accepted Message . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
2.8 CCR Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
2.8.1 Summary and Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
2.8.2 Go to Receive Frequency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
2.8.3 Load Transmit Frequency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
2.8.4 Set Volume Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
2.8.5 Receive CTCSS Value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
2.8.6 Transmit CTCSS Value. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
2.8.7 Receive DCS Value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
2.8.8 Transmit DCS Value. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
2.8.9 Encode Selcall Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
2.8.10 Set Selcall Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
2.8.11 Set ANI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

TM8100/TM8200 Computer-Controlled Data Interface (CCDI) Protocol Manual 5
© Tait Electronics Limited April 2007
2.8.12 Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
2.8.13 Transmitter Output Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
2.8.14 Set Bandwidth. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
2.8.15 Query Radio Pulse . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
2.8.16 Exit CCR Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
2.9 Unsolicited Messages from the Radio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
2.9.1 Summary and Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
2.9.2 PTT exceeds max transmit limit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
2.9.3 Selcall Decode Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
2.9.4 Notify Buffer Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Tait General Software Licence Agreement . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

6TM8100/TM8200 Computer-Controlled Data Interface (CCDI) Protocol Manual
© Tait Electronics Limited April 2007

TM8100/TM8200 Computer-Controlled Data Interface (CCDI) Protocol Manual 7
© Tait Electronics Limited April 2007
Preface
Scope of Manual
This manual contains reference information about the CCDI and CCR
protocols for the TM8100 and TM8200 mobiles. It applies to CCDI version
3.00 and later and CCR version 2.00.
Associated Documentation
Technical notes are published from time to time to describe applications for
Tait products, to provide technical details not included in manuals, and to
offer solutions for any problems that arise.1
■Technical Note TN-855-AN: TM8000 and TB7100 Data Modem
Facilities
■Technical Note TN-919-AN: Configuring the TM8100 for Data
Operation
■Technical Note TN-1075-AN: MAP27 Implementation Form
(Appendix A7)
Publication Record
1. Technical notes are available in PDF format from the Tait support website. Consult your nearest
Tait Dealer or Customer Service Organization for more information.
Issue Publication Date Description
1 March 2006 First issue
2 April 2007 ■Description of CCDI command prompt
(TIMS 38465)
■QUERY command 7 (display) added
(TIMS 59393)
■FUNCTION command 0 (functions),
subfunction 4, qualifiers 2 and 3 (keypress
progress message) added (TIMS 59393)
■FUNCTION command 0 (functions),
subfunction 5, qualifiers 0, 1, and 2 (channel
progress message) added (TIMS 59393)
■TDMA command added (TIMS 59393)
■PROGRESS message types 22 and 23 added
(TIMS 59393)
■QUERY_DISPLAY_RESOPNSE message added
(TIMS 59393)
■TDMA_DATA message added (TIMS 59393)
■CCR section added (TIMS 57777)

8TM8100/TM8200 Computer-Controlled Data Interface (CCDI) Protocol Manual
© Tait Electronics Limited April 2007
Alert Notices
Within this manual, four types of alerts are given to the reader: warning,
caution, important and note. The following paragraphs illustrate each type
of alert and its associated symbol.
Warning!! This alert is used when there is a potential risk
of death or serious injury.
Caution This alert is used when there is the risk of minor or
moderate injury to people.
Important This alert is used to warn about the risk of equipment dam-
age or malfunction.
Note This alert is used to highlight information that is required to
ensure that procedures are performed correctly.
Abbreviations
Abbreviation Description
ASCII American Standard Code for Information Interchange
AVL Automatic Vehicle Location
CCDI Computer Controlled Data Interface
CCR Computer Controlled Radio
CDP Conventional Data Protocol. A Tait over-air protocol.
CRC Cyclic Redundancy Check
CTCSS Continuous Tone Coded Squelch System
CTS Clear to Send
DCE Data Circuit-Terminating Equipment
DCS Data Carrier System
DTE Data Terminal Equipment
DTMF Dual Tone Multi-Frequency
FFSK Fast Frequency Shift Keying
GFI General Format Information for an SDM
GPIO General Purpose Input/Output
IPN Internal Part Number
LED Light-Emitting Diode
MSD Most Significant Digit
NMEA National Marine Electronics Association standard. Combined
electrical and data specification for communication between
marine electronics and GPS receivers.
PC Personal Computer
PTT Press To Talk

TM8100/TM8200 Computer-Controlled Data Interface (CCDI) Protocol Manual 9
© Tait Electronics Limited April 2007
RMC Recommended Minimum sentence C. NMEA GPS message
type for the minimum recommended transmit/GPS data.
RTS Request to Send (ready to receive)
Rx Receive
RXD Receive Data
SDM Short Data Message
SFI Specific Format Information for an SDM
THSD Tait High Speed Data
TIA Telecommunications Industry Association
TOP Tait Orca Portable
Tx Transmit
TXD Transmit Data
UART Universal Asynchronous Receiver-Transmitter
XON Transmitter On
XOFF Transmitter Off
Abbreviation Description

10 TM8100/TM8200 Computer-Controlled Data Interface (CCDI) Protocol Manual
© Tait Electronics Limited April 2007

TM8100/TM8200 Computer-Controlled Data Interface (CCDI) Protocol Manual CCDI 11
© Tait Electronics Limited April 2007
1CCDI
The Computer Controlled Data Interface (CCDI) protocol is a Tait
proprietary command protocol embedded in the TM8100 and TM8200
radios, and used for communicating with the radio via asynchronous serial
ports and over-air.
The radio is the DCE and is connected directly to the DTE, usually a PC,
via the serial port.
Two modes of operation are available:
■Command mode
■Transparent mode
When in Command mode, commands and response messages are passed
between the PC and the radio using the CCDI protocol. CCDI commands
can also be used to obtain GPS data and NMEA messages from the radio.
Refer to “QUERY” and “SEND_ADAPTABLE_SDM”. The baud rate is
set to 1200, 2400, 4800, 9600, 14400, 19200, 28800 or 115200 (TM8200
only) baud, using the programming application.
When in Transparent mode, communication between the PC and the radio
is set to 1200, 2400, 4800, 9600, 14400, 19200, 28800 or 115200 (TM8200
only) baud, using the programming application.
The over-air data rate is 1200 or 2400 bit/s for FFSK data,
12 kbit/s for Tait High Speed Data (THSD) narrow band and wide band,
and can be set to 19200 bit/s for THSD wide band.
Figure 1.1 Modes of operation
PC Serial Port
PC running
terminal application
PC running
terminal application
PC Serial Port

12 CCDI TM8100/TM8200 Computer-Controlled Data Interface (CCDI) Protocol Manual
© Tait Electronics Limited April 2007
1.1 Compatibility
This manual describes CCDI version 3.00 and later.
The radio programming application used should be the latest released
version for both the TM8100 and TM8200 radios. Refer to the
Ta i t Wo r ld we b s i t e http://www.taitworld.com for the latest versions of
programming application.
1.2 Serial Ports
Three ports are available for CCDI asynchronous serial communication
with the radio. The microphone and auxiliary ports are accessed externally,
and the internal options connector is internal to the radio.
Only one of these ports can be used for CCDI transmission and reception
at any time. The port is selected in the Data form of the programming
application, Serial Communications tab. Select “Mic”, “Aux” or “Internal
Connector”.
■Mic: The radio will transmit and receive data via the MIC_TXD and
MIC_RXD lines on the microphone connector.
■Aux: The radio will transmit and receive data via the AUX_TXD and
AUX_RXD lines on the auxiliary connector.
■Internal Connector: The radio will transmit and receive data via the
IOP_TXD and IOP_RXD lines on the internal options connector.
This connector is used to fit an internal options board into the radio.
For more information on these connectors, refer to the service manual.
1.2.1 Data Characteristics
Parameter
Standard
Comments
min. typ. max. units
Serial port
Baud rate: 1200, 2400, 4800, 9600,
14400, 19200, 28800, 115200
bit/s All UART parameters are
fixed and common to all
UARTs except for the
baud rate which is
configurable and
different for different
modes/applications
Data bits: 8
Start bit: 1
Stop bit: 1
Parity: None
Flow control:
Software
Hardware
XON/XOFF
RTS/CTS Requires two GPIO lines
to be programmed as
flow control

TM8100/TM8200 Computer-Controlled Data Interface (CCDI) Protocol Manual CCDI 13
© Tait Electronics Limited April 2007
1.2.2 Logic Level Compatibility
The following table show the compatibility of the radio’s digital I/O used
for CCDI with common industry logic standards.
Digital Input
Compatibility and
Toler a n ce
Digital Output
Compatibility
1.2.3 GPS Port
The GPS receiver/antenna is also connected to an asynchronous serial port
and must be different to the CCDI UART Port. The GPS receiver/antenna
is set in the Data form of the programming application, GPS tab, and can be
set to Mic, Aux or Internal Options.
If set to Aux, the GPS receiver will send NMEA messages to the radio via
the AUX_RXD line on the auxiliary connector.
If set to Internal Options, the GPS receiver will send NMEA messages to
the radio via the IOP_RXD line on the internal options connector.
1.2.4 MAP27 Port
MAP27 data transmission and reception also requires an asynchronous serial
port and must be different to the CCDI UART Port. The MAP27 port is
set in the Data form of the programming application, MAP27 tab, and can
be set to Mic, Aux or Internal Options.
If set to Mic, the radio will use the MIC_TXD and MIC_RXD lines on the
microphone connector.
Digital Input
Line
Logic standard input compatibility and tolerance
3.3V CMOS 5V CMOS 5V TTL RS-232
AUX_RXD Yes Yes Yes Yes
IOP_RXD Yes Yes Yes Noa
a. Level compatible but not tolerant. Inputs can be made RS-232 tolerant by using 3.3kΩseries
resistance inserted at the radio end.
CH_RXD
MIC_RXD
PRG_RXD
Yes Yes Yes Yes
Digital Output
Line
Logic standard input compatibility and tolerance
3.3V CMOS 5V CMOS 5V TTL RS-232
AUX_TXD Yes No Yes No
IOP_TXD Yes Noa
a. These outputs can be made 5V CMOS compatible using a 3.3kΩpull-up resistor to 5V that is
provided by the device being driven.
Yes No
CH_TXD
MIC_TXD
PRG_TXD
Yes No Yes No

14 CCDI TM8100/TM8200 Computer-Controlled Data Interface (CCDI) Protocol Manual
© Tait Electronics Limited April 2007
If set to Aux, the radio will use the AUX_TXD and AUX_RXD lines on
the auxiliary connector.
If set to Internal Options, the radio will use the IOP_TXD and IOP_RXD
lines on the internal options connector.
For more information on MAP27 data transmission, refer to Technical Note
TN-1075-AN, MAP27 Implementation Form (Appendix A7).
1.3 Before Operating
Before using CCDI, the following is useful to check.
■The radio must be correctly programmed for use with the CCDI
protocol. See “Programming” on page 14 for configuration information.
■At power on, the radio will select its default channel. To change the
channel, select the channel using the normal radio interface or using the
CCDI Go_To_Channel command. Refer to “GO_TO_CHANNEL”
on page 29.
■The radio will power on into the mode selected in the ‘Powerup State’
field in the Data form.
■Power, Tx and Rx LED indicators are helpful for establishing proper
operation. The radio speaker can be used to listen to data coming in.
■Data flow is controlled either by the customer’s embedded computer
system or by a PC running a data-sending application such as
Hyperterminal.
1.4 Limitations
Important Some data applications require extended transmission
times. This may be for larger file transfers or for real-time
telemetry information. This may put undue stress on the
radio transmitter and care must be taken to control trans-
mission times using flow control. Refer to “Hardware Flow
Control” on page 15.
1.5 Programming
For information on the parameters in the Data form of the programming
application, refer to:
■the Help of the programming application
■Technical Note TN-919-AN Configuring the TM8100 for Data
Operation.

TM8100/TM8200 Computer-Controlled Data Interface (CCDI) Protocol Manual CCDI 15
© Tait Electronics Limited April 2007
1.6 CCDI Flow Control
Flow control is a method of controlling the data so that a faster DTE-DCE
baud rate can be used to that of the over the air baud rate. This allows the
radio (DCE) to inform the DTE that its buffer is becoming full and that the
DTE needs to wait before sending more data to the radio.
Flow control should only be needed when the amount of data to send is
larger than the radios buffer (512 bytes for TM8100, 600 bytes for
TM8200).
Note Some older versions of the firmware have a buffer size of 128
bytes.
Available options: None, Hardware Software
1.6.1 XON/XOFF Software Flow Control
When the serial communications are set-up for software flow control, the
radio will use pre-programmed bytes for XOFF and XON.
Important When using XON/XOFF software handshaking, the data
stream (or the data file) must not include the programmed
XON and XOFF characters. It is recommended that only
ASCII text be used with software flow control.
The XOFF character is sent when there is less than 35 bytes of empty space
in the buffer.
The XON character is sent when XOFF had previously been sent and there
is now less than 10 bytes of data in the buffer.
1.6.2 Hardware Flow Control
When the serial communications are set-up for hardware flow control, two
of the programmable I/O lines are enabled for RTS and CTS. Hardware
flow control is not available for the mic port.
RTS Important The RTS line has been implemented as a “Ready to
Receive” line as per RS-232-E.
When the RTS line is inactive the radio will not output any serial data.
It will buffer any data and output it when the line is activated.
Important The RTS line does not stop the radio from receiving data
across the air so leaving this line inactive for any length of

16 CCDI TM8100/TM8200 Computer-Controlled Data Interface (CCDI) Protocol Manual
© Tait Electronics Limited April 2007
time could cause the buffer to overflow and for data to be
lost.
CTS The CTS line is deactivated when there is less than 35 bytes of empty space
in the buffer.
The CTS line is activated when the CTS line had previously been
deactivated and there is now less than 10 bytes of data in the buffer.
1.7 CCDI Transparent Mode
In Transparent mode, the radio acts as a modem, automatically transmitting
in FFSK or THSD format the serial data received from the PC. In this mode,
the baud rate between the PC (DTE) and the radio (DCE) can be set to
either 1200, 2400, 4800, 9600, 14400, 19200, 28800 or 115200 (TM8200
only) baud using the programming application. The over-air data rate is
1200 or 2400 bps for FFSK data, 12 kbit/s for Tait High Speed Data
(THSD) narrow band and 19200 bit/s for THSD wide band. The serial data
input buffer is 512 bytes for the TM8100 and 600 bytes for the TM8200, to
adequately cope with the data flow.
Communication in Transparent mode is free-format, with the protocol
determined entirely by the PC and the modem. It is transparent to the
CCDI, allowing the PC to send and receive data without passing through
the CCDI. CTCSS and DCS subaudible signalling is available in FFSK
Tra ns parent mod e on ly.
1.7.1 Entering Transparent Mode
Transparent mode can be set as the default mode at power on by selecting
FFSK or THSD Transparent Mode in the ‘Powerup State’ field in the
programming application. Refer to “Programming” on page 14.
You can change to Transparent mode while operating in Command mode
by sending a TRANSPARENT command to the radio or using a
programmable I/O line programmed for THSD. Example: t01zB1 sends a
TRANSPARENT command, requesting that the radio be put into
Transparent mode. The escape character specified here is “z” (ASCII code
= $7A). Once acknowledged, any further data is linked directly to the radio
in Transparent mode.
If the radio default is set to Transparent mode at power on, the default escape
character is “+”.

TM8100/TM8200 Computer-Controlled Data Interface (CCDI) Protocol Manual CCDI 17
© Tait Electronics Limited April 2007
1.7.2 Exiting Transparent Mode
To change to Command mode while operating in Transparent mode, you
can:
■send the escape sequence consisting of a 2 second idle time, followed by
three escape characters (sent within 2 seconds), followed by a further 2
second idle time.
Example: If the escape character is “+” (default), send
[2 second idle] +++ [2 second idle].
■exit via the I/O line programmed for THSD, if Transparent Mode was
entered using this line.
1.7.3 Transparent Mode Format
Transparent Mode
Packetisation
Transparent mode data is packetised into data blocks before it is sent over-
air. The start and stop bits are removed and a header is sent at the start of
each data block.
FFSK Transmission
Format The Transparent Mode transmission format is as follows:
Singe Data Block:
Multiple Data Blocks:
Lead-In
Delay
Lead-Out
Delay
time...
data block 1 data block n
over-air
PC data
RS232
data
RS232
PC
air-interface data out
serial data out
air-interface data in
serial data in
processing...
radio
Flow
Control
Flow
Control
no Flow Control
air-interface data out
serial data out
air-interface data in
serial data in
processing...
radio
Lead-In
Delay
preamble
2 bytes
sync
2 bytes
size
2 bytes
FFSK data block
max 46 bytes
CRC
2 bytes
Lead-Out
Delay
HEADER
Lead-In
Delay
HEADER
6 bytes
FFSK data block . . . .
max 46 bytes
CRC
2 bytes
HEADER
6 bytes
FFSK data block
max 46 bytes
CRC
2 bytes
Lead-Out
Delay

18 CCDI TM8100/TM8200 Computer-Controlled Data Interface (CCDI) Protocol Manual
© Tait Electronics Limited April 2007
THSD Transmission
Format For more information, refer to Technical Note TN-855-AN TM8000 and
TB7100 Data Modem Facilities.
Effective Over-Air
Data Rate The effective over-the-air data rate is lower than the set data rate.
For more information, refer to Technical Note TN-855-AN TM8000 and
TB7100 Data Modem Facilities.
Lead-In Delay The lead-in delay begins after the transmitter key-up time. It gives the
receiver(s) at the other end time to open before data is sent.
When data is detected at the radio’s input buffer, the following occurs:
■The transmitter keys up.
■A carrier is sent from the transmitter. When the carrier reaches its full
potential, the lead-in delay begins.
■If the receiving base station is set to Repeater mode, the carrier is
detected and Rx Gate becomes active (opens), which in turn makes the
PTT line active.
■The active PTT line keys up the transmitter.
This sequence is repeated with as many base stations as are in the chain.
The optimum length of the lead-in delay should be set keeping in mind the
number of base stations that need to be activated before any data is sent.
The lead-in delay must also allow for subaudible signalling decoding, if it is
enabled, when used in conjunction with FFSK data.
1.8 Command Mode
Command mode uses the Tait proprietary Computer Controlled Data
Interface (CCDI), a command protocol embedded in the radio firmware.
It is accessed using the serial port lines from the PC. In this mode, the baud
rate between the computer equipment (DTE) and the radio (DCE) can be
set to either 1200, 2400, 4800, 9600, 14400, 19200, 28800 or 115200
(TM82000 only) baud using the programming application
Tx
key-up
time
Lead In
Delay data
Lead Out
Delay Tx
key-down
Tx

TM8100/TM8200 Computer-Controlled Data Interface (CCDI) Protocol Manual CCDI 19
© Tait Electronics Limited April 2007
In Command mode, the PC sends command sequences to the radio and
waits for a prompt before beginning the next transaction. Some commands
require the radio to send a CCDI message in response. Messages sent to the
radio will always be responded to by the prompt.
Unsolicited messages such as PROGRESS or ERROR messages are sent by
the radio if there is a significant change in its state that the PC should be
aware of. When errors are detected, an unsolicited ERROR message is sent
by the radio to the PC. The radio cannot send messages that require a reply.
The SEND_SDM, SEND_ADAPTABLE_SDM and GET_SDM
commands require that SDMs are sent and received as over-the-air FFSK
data by the radio while in Command mode. If an SDM is received from the
over-air interface while the radio is in Command mode, the SDM data is
buffered and a ‘SDM Received’ RING messages are generated by the radio
to indicate that SDM data has been received. When using FFSK, an ‘FFSK
Data Received’ PROGRESS message will also be generated.
1.8.1 Entering Command Mode
Command mode can be set as the default mode at power on by selecting
‘Command Mode’ in the ‘Powerup State’ field in the programming
application. Refer to “Programming” on page 14.
To change to Command mode while operating in Transparent mode, you
can:
■send the escape sequence consisting of a 2 second idle time, followed by
three escape characters (sent within 2 seconds), followed by a further 2
second idle time.
Example: If the escape character is “+” (default), send
[2 second idle] +++ [2 second idle].
■exit via the I/O line programmed for THSD, if Transparent Mode was
entered using this line.
1.8.2 CCDI Command Prompt
After entering Command mode, the radio sends a “.” character to the PC
which is displayed as a command prompt. The command prompt indicates
that the radio is ready for another command. The prompt is also sent after
the radio has sent a message.
Note In early CCDI versions, the command prompt after messages was
not sent for all messages.

20 CCDI TM8100/TM8200 Computer-Controlled Data Interface (CCDI) Protocol Manual
© Tait Electronics Limited April 2007
1.8.3 CCDI Command Format
All CCDI message packets take the general form:
[IDENT] [SIZE] [PARAMETERS] [CHECKSUM] <CR>
■[IDENT] = The message identifier. Identifiers are single ASCII
characters (lower-case alphabetical) which categorise the message type.
■[SIZE] = The number of characters which make up the
[PARAMETERS] field. [SIZE] is an 8-bit number expressed in ASCII
hex notation (two characters).
■[PARAMETERS] = An optional field, depending upon the command.
Parameter values are generally character strings unless explicitly stated
otherwise. Parameter type is dependent upon the command, and often
has multiple parts.
■[CHECKSUM] = An 8-bit checksum of the [IDENT], [SIZE] and
[PARAMETERS] fields. Expressed in two character ASCII hex
notation.
■<CR> = The carriage return (0Dh) packet terminator.
1.8.4 Restrictions
■All characters in a message are printable ASCII.
■Where numeric values are represented in ASCII hex notation (two
characters per byte), characters A to F are upper case.
■The minimum length of a command packet is 5 characters. For example
q002F is the QUERY command where [SIZE] = 00 as there is no
[PARAMETERS] field required.
■The maximum length of the [PARAMETERS] field is 255 characters.
The maximum length of the command packet is therefore 260
characters.
1.8.5 Calculating the CCDI [CHECKSUM]
[CHECKSUM] is calculated by applying the following algorithm:
1. Take the modulo-2 sum of all message bytes preceding
[CHECKSUM].
2. Retain bits 0 to 7, discarding any higher order bits resulting from the
summation.
3. Form the two’s complement of the remainder.
4. Convert the binary number into two ASCII hex digits, MSD first.
Example s0D050800TESTHi!DA
1. Take the modulo-2 sum of all message bytes preceding
[CHECKSUM].