AeroComm PKLR2400 Mounting instructions

PKLR2400 Radio
Hardware and Software
Interface Specification
Version 3.1
13256 W. 98th Street
Lenexa, KS 66215
[phone]
www.aerocomm.com
[e-mail]
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Copyright Information/FCC User’s Notice
Copyright Copyright © 1999 AEROCOMM, Inc. All rights reserved.
Information The information contained in this manual and the accompanying
software programs are copyrighted and all rights are reserved by
AEROCOMM, Inc. AEROCOMM, Inc. reserves the right to make
periodic modifications of this product without obligation to notify
any person or entity of such revision. Copying, duplicating, selling,
or otherwise distributing any part of this product without the prior
consent of an authorized representative of AEROCOMM, Inc. is
prohibited.
All brands and product names in this publication are registered
trademarks or trademarks of their respective holders.
FCC USER'S
Notice
WARNING: This equipment has been tested and found to comply with the limits for a
Class B digital device, pursuant to Part 15 of the FCC Rules. These limits
are designed to provide reasonable protection against harmful
interference when the equipment is operated in a residential environment.
This equipment generates, uses, and can radiate radio frequency energy
and, if not installed and used in accordance with the instruction manual,
may cause harmful interference to radio communications. However, there
is no guarantee that interference will not occur in a particular installation.
If this equipment does cause harmful interference to radio or television
reception, which can be determined by turning the equipment off and on,
the user is encouraged to try to correct the interference by one or more of
the following measures:
•Reorient or relocate the receiving antenna
•Increase the separation between the equipment and receiver.
•Connect the equipment into an outlet on a circuit different from the
one the receiver is connected.

Revisions Description
Version 1.0 Initial Release Version - 2/4/99
Version 1.1 page 24 - System ID Address corrected from 30h to 34h
Version 2.0 Add transparent serial modes – 5/25/1999
Added EEPROM Write Protect
Changed Pin 27 Definition to Forced API Mode 03
Version 3.0 Add broadcast packet attempts – 6/10/1999
Broadcast Packet size increased from 256Bytes to 2KBytes
Version 3.1 Correct number of channels from 75 to 77 – 7/22/1999
Change nomenclature for Serial Packet Mode 03 to Serial API Mode 03
Copyright © 1999
AeroComm, Inc.
This material is preliminary.
Information furnished by AeroComm in this specification is believed to be accurate. Devices sold by
AeroComm are covered by the warranty and patent indemnification provisions appearing in its Terms of
Sale only. AeroComm makes no warranty, express, statutory, implied or by description, regarding the
information set forth herein. AeroComm reserves the right to change specifications at any time and without
notice.
AeroComm’s products are intended for use in normal commercial applications. Applications requiring
extended temperature range or unusual environmental requirements such as military, medical life-support or
life-sustaining equipment, are specifically not recommended without additional testing for such application.

Table of Contents
Preliminary 4
1. OVERVIEW.......................................................................................................................................... 6
2. PKLR2400 SPECIFICATIONS........................................................................................................... 7
3. THEORY OF OPERATION................................................................................................................ 8
3.1 DEFINITIONS .................................................................................................................................... 8
3.2 SERIAL INTERFACE MODES.............................................................................................................. 8
3.2.1 Serial Interface Mode 01 – Transparent, Fixed Length, with Timeout................................... 8
3.2.2 Serial Interface Mode 02 – Transparent, End Character....................................................... 8
3.2.3 Serial Interface Mode 03 – API .............................................................................................. 9
3.2.4 Serial Interface Mode 04 – Transparent, Fixed Length, No Timeout..................................... 9
3.2.5 Serial Interface Buffer............................................................................................................. 9
3.3 INITIALIZATION SEQUENCE ............................................................................................................ 10
4. HARDWARE INTERFACE.............................................................................................................. 11
4.1 MECHANICAL OVERVIEW............................................................................................................... 11
4.2 PIN DEFINITIONS FOR CONNECTOR J1............................................................................................ 12
4.3 PIN DESCRIPTIONS FOR CONNECTOR J1 ......................................................................................... 13
4.3.1 No Connect............................................................................................................................ 13
4.3.2 Vcc ........................................................................................................................................ 13
4.3.3 Clear To Send (CTS)............................................................................................................. 13
4.3.4 Reserved................................................................................................................................ 13
4.3.5 Baud Rate Selector (BDSEL)................................................................................................ 13
4.3.6 Forced API Mode 03 (PKTMODE) ...................................................................................... 13
4.3.7 Microprocessor Reset (uP RESET)....................................................................................... 14
4.3.8 EEPROM Write Protect (E2WP) .......................................................................................... 14
5. DEVELOPERS KIT........................................................................................................................... 15
5.1 SERIAL ADAPTER BOARD............................................................................................................... 16
NOTE: The pins on the 40 pin header strip match up 1 to 1 with the pin-out of the OEM Connector J1.16
J3-J9 Level Translator Settings ................................................................................................................ 17
5.1.1 Serial Adapter Board Pin Definitions................................................................................... 17
5.2 SOFTWARE UTILITIES..................................................................................................................... 17
5.2.1 OEM.EXE.............................................................................................................................. 18
5.2.2 *.RTC.................................................................................................................................... 19
5.2.3 PORTS.CFG.......................................................................................................................... 20
5.2.4 Setup Scripts.......................................................................................................................... 20
5.3 ANTENNA BOARD .......................................................................................................................... 22
5.4 POWER SUPPLY SPECIFICATION...................................................................................................... 22
6. COMMAND SET................................................................................................................................23
6.1 SYSTEM COMMAND SET SUMMARY............................................................................................... 23
6.1.1 Reset*.................................................................................................................................... 23
6.1.2 Control*................................................................................................................................ 24
6.1.3 Diagnostic result*................................................................................................................. 24
6.1.4 Standby* (THIS COMMAND NOT YET SUPPORTED)...................................................... 25
6.1.5 Reset EEPROM*................................................................................................................... 25
6.1.6 Status Request*..................................................................................................................... 25
6.1.7 Status Reply*......................................................................................................................... 26
6.1.8 Update EEPROM Checksum*............................................................................................... 27
6.1.9 Check EEPROM Checksum* ................................................................................................ 27
6.1.10 EEPROM Checksum Status*.................................................................................................27
6.1.11 Acknowledge*....................................................................................................................... 27
6.2 RADIO COMMAND SET SUMMARY ................................................................................................. 28
6.2.1 RF enable*............................................................................................................................ 28

PKLR
Preliminary 5
6.2.2 Send data*............................................................................................................................. 28
6.2.3 Send data complete*............................................................................................................. 29
6.2.4 Received data*...................................................................................................................... 29
6.2.5 In range*............................................................................................................................... 29
6.2.6 Out of range*........................................................................................................................ 30
7. CONFIGURING THE PKLR2400 RADIO...................................................................................... 31
7.1 SYSTEM EEPROM PARAMETERS .................................................................................................. 31
7.1.1 Product Identifier String/Version Information...................................................................... 31
7.1.2 IEEE assigned MAC Address................................................................................................ 31
7.1.3 Channel Number................................................................................................................... 32
7.1.4 Client/Server Mode............................................................................................................... 32
7.1.5 System ID.............................................................................................................................. 32
7.1.6 Baud High (BH) and Baud Low (BL).................................................................................... 33
7.2 PROTOCOL EEPROM PARAMETERS.............................................................................................. 34
7.2.1 Transmit Data Link Attempts................................................................................................35
7.2.2 Receive mode ........................................................................................................................ 35
7.2.3 In-Range, Out-of-Range Refresh...........................................................................................35
7.2.4 End Character Definition...................................................................................................... 36
7.2.5 Fixed Packet Length High Byte/Low Byte............................................................................. 36
7.2.6 Serial Interface Modes.......................................................................................................... 36
7.2.7 Destination Address Control................................................................................................. 37
7.2.8 Interface Timeout Control..................................................................................................... 37
7.2.9 Broadcast Attempts............................................................................................................... 38
7.3 EEPROM PARAMETER SUMMARY................................................................................................ 38
8. INITIALIZING THE PKLR2400 RADIO........................................................................................ 39

Overview
Preliminary 6
1. Overview
This document contains information about the hardware and software interface between an
AeroComm PKLR2400 Radio and an OEM host. Information includes the theory of operation, system
issues, and a basic command set for operational control of the system and radio.
The Radio is designed to allow flexibility at the hardware interface level with a minimum number
of actual hardware pins connecting the radio and the OEM Product. The radio is controlled by a Dallas
87C520 microcontroller providing program storage. A separate EEPROM provides user definable
parameter storage.
The RF system is a Client/Server (Slave/Master) architecture. Data can be transmitted from client
to server or server to client, but not from client to client, or server to server. Clients can only hear servers
and servers can only hear clients.
The Serial Interface Modes provide four main serial user interfaces. This protocol provides
significant flexibility to the OEM allowing them to provide data in many forms including packet, end
character and fixed-length with and without timeouts.

PKLR2400 Specifications
Preliminary 7
2. PKLR2400 Specifications
GENERAL
Bus Interface Serial (TTL Level Asynchronous) or Parallel through 40
pin mini connector. Amp P/N 177986-1 or Berg
Interface Data Rate
Serial
Parallel Prog to 800 kbps. Supports PC rates to 57.6 Kbps 4 Mbps
Compliance Certifiable under:
US - FCC15.247
Canada - DOC
Europe - ETSI
Japan - MKK
Power Consumption
TX/RX Active (All Modes)
Interface ON/RF OFF (API Mode Only)
Sleepwalk (All Modes)
Standby (API Mode Only)
115mA typical
45mA typical
35mA typical
30mA typical
Channels Supports 77 non-interfering channels
Security User assigned System ID. Unique IEEE address on each
radio.
RADIO
Frequency Band 2.402 – 2.478 GHz
Radio Type Spread Spectrum Frequency Hopping
Output Power 10mW
Voltage 5V nominal +5%, + 50mV ripple
Sensitivity -90dBm
Data Rate 1Mbps
Range Indoors up to 300ft, Outdoors up to 3000ft
Can be extended with directional antenna
ENVIRONMENTAL
Temperature (Operating) 0 to +60 C
Temperature (Storage) -50 to +85 C
Humidity (non-condensing) 10% to 90%
PHYSICAL
Dimensions 1.65” x 2.65” x 0.20”
Antenna Connector Standard MMCX jack
Weight Less than 0.5 ounce
SOFTWARE
User Configurable Options
Host Interface Data Rate Up to 800Kbps
Variable Packet Length Up to 2Kbyte
Serial Interface Modes (3) Transparent and (1) API
Diagnostic Error Counters
User Programmable Attempts Up to 255

PKLR2400 Specifications
Preliminary 8
3. Theory of Operation
3.1 Definitions
Server Host: The server host is the OEM device controlling the server radio
Client Host: The client host is the OEM device controlling the client radio
Host: Host refers to both the server host and the client host
Server Radio: The server radio is the “master” radio. It is the hub of communications
Client Radio: The client radio is a “slave” radio. It is controlled by it’s own Host, but is a slave to the
server radio
Authentication: The acquisition of the IEEE 802.3 address of the Server Radio by the Client Radio and the
subsequent issuance of an In-Range* command by the Client Radio to the Client Host.
Unicast Address: A frame that is directed to a single recipient as specified in IEEE 802.3.
Broadcast Address: A frame that is directed to multiple recipients as specified in IEEE 802.3.
3.2 Serial Interface Modes
The PKLR2400 provides four Serial Interface Modes with programmability within each mode
allowing maximum system flexibility. These four Serial Interface Modes include three transparent modes
and one API mode. The radio-to-radio protocol is identical on all three Transparent Serial Interface Modes.
This allows all three Transparent Serial Interface Modes to coexist within the same network. The API
Serial Interface Mode 03 is not interoperable with the Transparent Serial Interface Modes 01, 02 and 04.
3.2.1 Serial Interface Mode 01 – Transparent, Fixed Length, with Timeout
Mode 01 specifies Transparent mode with fixed length packets and active timeout. Packets will be
transmitted over the RF interface when one of the following conditions occurs:
•The number of data bytes received over the interface is equal to the buffer specified by
the user in EEPROM address locations 43H and 44H.
•A byte gap larger the timeout specified by the user in EEPROM location 4DH occurs.
3.2.2 Serial Interface Mode 02 – Transparent, End Character
Mode 02 specifies Transparent mode with End Character. Packets will be transmitted over the RF
interface when the user-defined End Character is received by the radio over the interface. The End
Character is defined by the user at EEPROM location 3EH.

Theory of Operation
Preliminary 9
3.2.3 Serial Interface Mode 03 – API
Mode 03 specifies API Mode. In this mode, the OEM has control of the radio command set
detailed in Section 6.2. Packets are transmitted upon completion of the Send_Data command.
In API Serial Interface Mode 03, the OEM host may utilize a set of basic commands to control the
radio and system. These commands allow the customer to establish system parameters through the
programming of variables in EEPROM as well as monitoring system performance. These commands can
only be exercised when the radio is in API Serial Interface Mode 03. It is important to understand two
aspects of the software commands.
1. There are only three commands that are issued from the client radio to the Client Host. These
three commands are Out_of_range*, In_range* and Receive_data*. The Receive_data*
command is the only command issued from the Server radio to the Server Host. It is
important to note that these commands will NOT get an acknowledgement, they are signals to
the Host to alert it to incoming data, or a change of status.
2. All remaining commands initiated by the Host MUST receive an acknowledge from the radio
to signal completion of the assigned task. This works as flow control for the information
going to the radio.
The server radio can receive data from a total of 75 different clients, but from only 8 different
clients in any 30 millisecond interval. It is possible that there will be multiple Receive_data* commands at
the same time. Since there is no reply command at the completion of Receive_data*, the Host must be
capable of handling up to 8 Receive_data* commands at one time.
Note: This means that whenever a command is initiated by the radio to the Host, the Host must be
ready to accept the command and any data following the command.
Note: A full list of commands, definitions, and implementation can be found in Section 6.
3.2.4 Serial Interface Mode 04 – Transparent, Fixed Length, No Timeout
Mode 04 specifies Transparent mode with fixed length packets and no timeout. Packets will be
transmitted over the RF interface when the number of data bytes received over the interface is equal to the
buffer specified by the user in EEPROM address locations 43H and 44H.
3.2.5 Serial Interface Buffer
The serial interface buffer provides 8Kbytes of memory broken into four dynamic regions. In the
API Serial Interface Mode 03, only one region is utilized. In the Transparent Serial Interface Modes 01, 02
and 04, a buffer region is used each time a packet release condition is met. As an example, in End
Character Mode 02, if 500 bytes are transmitted followed by the specified end character, 500 bytes will be
stored in the first region and the remianing 7.5Kbytes will be dynamically allocated for the next three
packets. It is strongly recommended that CTS or upper layer protocol with acknowledgements be used by
the OEM when operating in Transparent Serial Interface Control Modes to eliminate the following system
issues:
Note: If all four buffers are filled and the OEM host continues to send data over the interface, it will
be discarded by the radio. This can be eliminated if the OEM utilizes CTS.

Theory of Operation
Preliminary 10
3.3 Initialization Sequence
When operating in the three Transparent Serial Interface Modes, the initilization sequence is
managed by the AeroComm protocol. In-Range commands are not issued and there is no acknowledge from
the radio on data delivery unless the OEM protocol has built-in acknowledgement.
When operating in the API Serial Interface Mode 03, the following initialization sequence
occurs. During the power up sequence or upon a Reset* command, the Clear to Send (CTS) line is set high
(5V TTL logic levels). While CTS is high, initialization occurs, and when finished, CTS is put low
indicating successful initialization is complete.
Note: At this point, the only command that can not be issued is the Send_data* command. This
command can only be issued after the RF_enable* and In_range* commands have been issued.
Before data communications can begin, a client radio needs to be authenticated. The client host
must issue an RF_enable* command to activate the client radio and receive an acknowledgement from the
client radio. The server radio transmits a beacon containing it’s IEEE 802.3 address. Once the client radio
has been activated by use of the RF_enable* command, it will receive the server radio IEEE 802.3 address
once it is in range. Upon receiving the IEEE 802.3 server radio address, the client radio will issue an
In_range* command to the Client Host containing the IEEE 802.3 server radio address.
The client host must receive the In_range* command from the client radio before the Send_data*
command is invoked. Broadcast mode, as defined by IEEE 802.3, is supported and can be used to send
data to all radios that are within range but its use should be limited because reception of the message is not
guaranteed.
When the last bit of data is transferred from the Host to the radio, the Host must wait for the CTS
line to transition high (meaning that the radio has found the end of the data packet) and then transition back
low (meaning that the radio is ready for the next command).
Clear To Send minimum delay of 40µ
µµ
µs between (1) and (2) after end of data packet
Note: All serial data must be transmitted LSB first.
Note: These radios are designed to be single threaded, meaning that for every command issued, there
is a reply command that signifies the completion of the command issued. There can be no
interleaving of commands.
CTS
from
Radio
Delay for reply command
*Note: If level translators are
used the CTS signal will be
inverted coming from the radio.
TXD
LSB First
From Host Command Length ChecksumData
(1) (2)

Hardware Interface
Preliminary 11
4. Hardware Interface
4.1 Mechanical Overview
The PKLR2400 measures 1.65” x 2.65”. Critical parameters are as follows:
J1 – 40 pin OEM interface connector (Amp P/N 177986-1) mates with Amp P/N
177985-1
J2 – High frequency MMCX style antenna connector (Huber + Suhner P/N 85-MMCX-
S50-0-51) mates with any manufacturer MMCX plug
(4) Mounting holes are 0.100” diameter.
Figure 1. Mechanical Overview of PKLR2400

Developers Kit
Preliminary 12
4.2 Pin Definitions for Connector J1
The following pinout summary is achieved through a 40 pin mini connector J1 (Amp P/N 177986-1).
Pin Serial Parallel* Definition
1 GND GND Ground
2NC NC No Connect
3VCC VCC 5V + 5%
4NC NC No Connect
5VCC VCC 5V + 5%
6NC NC No Connect
7NC NC No Connect
8NC NC No Connect
9NC NC No Connect
10 NC NC No Connect
11 NC NC No Connect
12 NC NC No Connect
13 NC D7 No Connect/Data 7
14 TXD NC Transmit/No Connect
15 NC D6 Data 6
16 RXD NC Receive/No Connect
17 NC D5 Data 5
18 NC NC No Connect
19 NC D4 Data 4
20 GND GND Ground
21 GND GND Ground
22 NC D3 No Connect/Data 3
23 CTS DIR1 Clear To Send/Bidir Handshake 1
24 Reserved Reserved Reserved Processor
25 Reserved Reserved Reserved Crystal
26 BDSEL STROBE’ Baud Select/Strobe Not
27 PKTMODE DIR2 Force API Mode 03/Bidir Handshake 2
28 NC BUSY No Connect /BUSY
29 NC NC No Connect
30 NC NC No Connect
31 NC NC No Connect
32 NC D0 No Connect/Data 0
33 NC NC No Connect
34 NC D1 No Connect/Data 1
35 NC NC No Connect
36 DCD D2 Data Carrier Detect/Data 2
37 E2WP E2WP EEPROM Write Protect
38 uP_RESET uP_RESET Microprocessor Reset
39 VCC VCC 5V + 5%
40 GND GND Ground
Note: The AeroComm radio provides 5Volt logic levels at the interface connector, J1
Note: DCD is not utilized.
Note: * Parallel interface not implemented at this time.

Developers Kit
Preliminary 13
4.3 Pin Descriptions for Connector J1
Special considerations for the hardware interface at connector, J1, are described in this section.
All remaining pin descriptions are standard for serial hardware interfaces.
4.3.1 No Connect
All No Connect pins 2, 4, 6-19, 22, 28-35 and 37 must not be connected to logic high or low
levels, but must be left floating.
4.3.2 Vcc
All Vcc pins 3, 5 and 39 require power of 5Vdc + 5% with ripple of less than 50mv p-p.
4.3.3 Clear To Send (CTS)
Clear To Send (CTS), pin 23, requires a minimum delay of 40µs between (1) and (2) after end of
each data packet.
Figure 1. Timing Note for CTS Pin
4.3.4 Reserved
The reserved pins 24 and 25 are used by AeroComm for internal testing and/or future radio
enhancements. These pins should be treated as No Connect pins and must not be connected to logic high or
low levels, but must be left floating.
4.3.5 Baud Rate Selector (BDSEL)
The Baud Rate Selector (BDSEL), pin 26, provides the user a default method of communicating
with the radio in the event the EEPROM baud rate parameters become corrupted. If pin 26 is logic high
level or not connected, the baud rate will default to the variables specified in EEPROM. If pin 26 is logic
low level, the baud rate will default to 9600 baud.
4.3.6 Forced API Mode 03 (PKTMODE)
Forced API Mode 03 (PKTMODE), pin 27, provides the user a method of programming the radio
from any of the Transparent Serial Interface Modes to the API Serial Interface Mode. It is required that
CTS
from
Radio
Delay for reply command
*Note: If level translators are
used the CTS signal will be
inverted coming from the radio.
TXD
MSB First
From Host Command Length ChecksumData
(1) (2)

Developers Kit
Preliminary 14
the radio be in API Serial Interface Mode to execute the Command Set or to configure any of the
EEPROM parameters. To force the radio into API Serial Interface Mode 03, pin 27 must be held at logic
low level and the radio reset. The radio can not be placed into any of the Transparent Serial Interface
Modes 01, 02 or 04 until pin 27 is held at logic high level and reset.
4.3.7 Microprocessor Reset (uP RESET)
Microprocessor Reset (uP RESET) is achieved by holding pin 38 at logic high level for a
minimum of 2ms. If uP RESET is performed after power has been applied to the radio and is stable, the
reset time will be significantly less. At all other times, pin 38 should be logic low level. If pin 38 is not
connected, the microprocessor will hold pin 38 at logic low level.
4.3.8 EEPROM Write Protect (E2WP)
EEPROM Write Protect (EEWP) is enabled when pin 37 is at logic high level or left floating. Pin
37 must be logic low level to Write to the EEPROM.

Developers Kit
Preliminary 15
5. Developers Kit
SDK-PKLR2400P (Parallel) and SDK-PKLR2400S (Serial) Developer Kits help system designers
implement radio designs quickly. The kit offers all the cables, power supplies, circuit schematics, documentation
and accessories needed to begin using the PKLR2400 quickly.
The kit includes:
•(2) PKLR2400 Data Radios either serial or parallel
•(2) Serial Adapter Boards with 40 pin interface, 40 pin header, LED indicators, power connector and DB9
connector. (SDK-PKLR2400S includes RS232 transceivers)
•(2) AC Power Adapters
•(2) DB9 to DB9 or (2) DB9 to DB25 for the SDK-PKLR2400S and SDK-PKLR2400P respectively
•Hardware and software interface specification
•(2) Antenna cables with patch antenna (monopole or dipole antenna optional)
•Software utilities
•Technical Support

Developers Kit
Preliminary 16
5.1 Serial Adapter Board
The Serial Adapter Board allows the use of different forms of communication with the OEM
radios. The user must choose between using RS-232 levels or 5 Volt TTL logic levels for interfacing with
the OEM radio when using the adapter board.
Figure 2. Serial Adapter Board Assembly Drawing
Item Qty Reference Description
11 J1 Amp 40 Pin Connector (177985-1) mates directly with J1 on Radio
2 1 J2 DB9 Male connector mates with provided cable to PC or OEM Host
3 1 P1 Power Connector provides power to entire kit with provided 5Vdc PS
4 2 J10 Generic 40 Pin Dip Header 0.100 Centers for test points
5 7 J3-9 Generic 3 Pin Sip Header 0.100 Centers for level translator selection
6 2 U1-2 Max202 Voltage Level Conversion Chips
7 1 SW1 SPST Switch for Reset
8 1 SW2 EEPROM Write Enable when Depressed
NOTE: The pins on the 40 pin header strip match up 1 to 1 with the pin-out of the OEM Connector
J1.

Developers Kit
Preliminary 17
J3-J9 Level Translator Settings
If a PC will be used as the OEM server or client host, then level conversion must be enabled to
convert from the RS-232 levels at the PC to the 5 Volt TTL logic levels used on the radio. To enable level
conversion, place jumpers J3-J9 on pins 2 and 3, see Figure 3. If another device (0-5 volt TTL logic levels)
is to act as the Host for the radio then the user must disable level conversion. To disable level conversion,
place jumpers J3-J9 on pins 1 and 2 see figure 4. If running under Windows, jumper J6
(PKTMODE/RTS) must be removed.
Figure 3. Level Translation Enabled Figure 4. Level Translation Disabled
Note: If level translation is enabled it is important to note that the signal level will be inverted at the
interface connector, J1, between the OEM radio and the Serial Adapter Board.
Figure 5. Jumper Definitions.
5.1.1 Serial Adapter Board Pin Definitions
DB-9 Signal Name Associated 40-pin connector 40-Pin Header Strip
(RS-232C) Level Translation to radio Test Points
Pin # At DB-9 Connector Jumper Pin # Pin #
1 DCD not used J9 NC 35
2 RX Data J3 14 14
3 TX Data J4 16 16
4NC
5 Ground 1,20,21,40 1,20,21,40
6NC
7 PKTMODE/RTS J6 27 27
8 Clear to Send J5 23 23
9NC NC NC
5.2 Software Utilities
Jumper Associated Serial Signal
From DB-9
J3 RX Data
J4 TX Data
J5 Clear to Send
J6 PKTMODE/RTS
J7 NA
J8 NA
J9 DCD not used

Developers Kit
Preliminary 18
The developer kit includes a 3.5” diskette of software utilities allowing the customer to exercise
the radios upon receipt. The software utilities are written for a DOS environment. The software
utilities will not operate properly under a DOS shell in Windows or Windows. The software includes
several files as follows:
•OEM.EXE – Interactive Command/EE Edit Software/Transmit Receive Emulator.
•*.RTC – Script files that automate radio mode setup and demonstrates operation.
•PORTS.CFG – Com port address and baud rate information
•README.TXT – Further utility software documentation and latest release notes
•OEM.CFG – Configuration file for OEM.EXE
•OEMRWSP.INI – AeroComm Use Only
These files are located in each of three directories as follows:
1. OnePC – This directory contains all the files required to run the Client and Server radios on a single
PC. The Client Radio must be connected to Com1 (3F8) and the Server Radio must be connected to
Com 2 (2F8)
2. ClientPC- This directory contains the Client Radio files that are required to run the Client Radio on
one PC and the Server Radio on a separate PC. The Client Radio should be connected to Com 1 (3F8)
3. ServerPC- This directory contains Server Radio files that are required to run the Client Radio on one
PC and the Server Radio on a separate PC. The Server Radio should be connected to Com 1 (3F8)
5.2.1 OEM.EXE
This software contains three unique utilities to exercise, monitor and setup modes in the radios.
These utilities are: Transmit/Receive Emulator, Single Line Command Interface, and EEPROM
Viewer/Editor.
5.2.1.1 Transmit/Receive Emulator
This software allows (1) Server and (1) Client radio to communicate with each other. The
software comes pre-configured for the two radios in the development kit.
When connecting the Client and Server Radios to the same PC, connect the Server Radio to
Com 2 (2F8), then connect the Client Radio to Com 1 (3F8). Copy the OnePC directory and contents to the
PC.
When connecting the Client and Server Radios to separate PCs, connect the Server Radio to
Com 1 (3F8) on one PC, then connect the Client Radio to Com 1 (3F8) on a separate PC. Copy the
ClientPC directory and contents to the PC with the Client Radio attached. Copy the ServerPC directory and
contents to the PC with the Server Radio attached.
Note: The factory default for the Client Radio and Server Radio is API Serial Interface Mode 03.
Run OEM.EXE on one or both PCs as dictated by your setup. Press the 'F3' key to perform a
RESET and RF_Enable on all PCs. Press the 'F9' key to run the script files and demonstrate continuous
data transfers between radios. Press the 'Esc' key to stop. Pressing the 'Esc' key again will exit from the
program.
Note: The “F3” key should be used only when the radios are in API Serial Mode 03. Use “Alt R” to
perform a RESET of the radios in Transparent Serial Modes 01, 02 and 04.
While running, the screen will display transmit timeouts, receive timeouts, and run number. The
Emulator program is controlled by script files. The script files can be edited by the user and detailed

Developers Kit
Preliminary 19
instructions on how to write a script file can be found in the section below describing *.RTC. While in the
Emulator, pressing the ‘Alt’ key will bring up a window with 7 choices: File, Settings, Window, Reset,
Enable, Help and About. The File option allows the user to load a script file or execute a mode setup script
to ports 1 or 2. The Settings option allows the user to change baud rate and other settings. The Window
option allows the user to view the trace buffer or a list of the script commands. The Reset command issues a
Reset command to all ports configured in PORTS.CFG. The Enable command sends a RF_Enable to all
ports configured in PORTS.CFG.
Note: The factory default for the Client Radio and Server Radio is API Serial Interface Mode 03.
Therefore, both radios must receive an RF_enable before scripts can be run.
Note: Receive commands expecting more than 16 bytes will fail in 'F10' single-step mode.
The Transmit/Receive Emulator can also be used to execute the setup scripts provided with the
program. For a full list of the scripts, see the readme.txt file in the directory labeled ‘Scripts’ on the disk.
To execute a script, press ‘alt-F’ and then ‘Enter’ to bring up a selection window. You can enter the name
of the setup script to be run, or hit ‘Enter’ to see a list of all the available script files. It is important to note
that when you hit ‘Enter’ it will show all the script files that are in the same directory as the executable
oem.exe. Once you have a script file loaded, then you will need to depress the write protect tab on the
serial adapter board while you single step (‘F10’) through the commands in the script. Once you have
executed all the commands in the set-up script you must press the reset button on the serial adapter board
before any of the changes will be implemented.
5.2.1.2 Single Line Command Interface
While in the Transmit/Receive Emulator press the ‘F5’ key to enter into the One Line Command
Interface. The one line Command Interface allows the user to command the radios into various operation
modes. The command set has already been entered. To invoke a command, scroll to the appropriate
command, using the up/down arrows on the keyboard, until the appropriate command is highlighted. Press
the 'F10' key to send the command to the radio. Press the 'F9' key to continuously retransmit the same
command until the 'Esc' key is pressed. Press the 'F8' key to toggle between ports 1 and 2 (com1 and
com2). You will see the active port and address displayed at the top of the screen
Upon successfully receiving and executing the command, the radio will send back a acknowledge
displayed in the "Receive Data" window. At the end of each command sequence line, a highlighted
checksum is displayed. When entering a new command, it is not necessary to enter a checksum. The
program automatically calculates and enters the checksum. On exit, changes to the command interface can
either be saved or ignored. Press the 'Esc' key to exit.
5.2.1.3 EEPROM Viewer/Editor
Press the 'F2' key to enter the EEPROM viewer/editor screen. To edit a value on this screen,
simply move the cursor to highlight the appropriate value, type in the new value and press the 'Enter' key.
To undo an edit, either press the 'Esc' key to return to the Command Interface, or press any arrow key. To
update the radio with the new EEPROM values, press the 'F10' key. An EEPROM read can be performed
on this page by pressing the 'F9' key.
5.2.2 *.RTC

Developers Kit
Preliminary 20
*.RTC files contain all of the configuration information for OEM.EXE. *.RTC files can be
modified to change timeouts, ports, and commands. *.RTC files require very specific format as detailed
below:
* -- begins and ends each command sequence
T -- invoke transmit sequence over serial host/radio interface (API Mode 3)
R -- invoke receive sequence over serial host/radio interface (API Mode 3)
C -- invoke transmit sequence over serial host/radio interface (Transparent Modes 1,2,4)
S -- invoke receive sequence over serial host/radio interface (Transparent Modes 1,2,4)
D -- invoke delay
Note: Any line beginning with a "space" character is interpreted as a comment
Note: The first line in PING.RTC is always interpreted as a comment
Example Command Format
*T[transmit port number] [timeout]
[transmit port number] is either "1" or "2" as designated in PORTS.CFG
[timeout] is between "0000" and "9999" and is measured in milliseconds
[Command] [Length Low] [Length High] [Data] [Checksum automatically provided]
*
5.2.3 PORTS.CFG
Before attempting to run the executables, the user must ensure the development kit radios are
attached to the two ports specified in PORTS.CFG. The default configuration for PORTS.CFG assumes
that both developer kit radios are connected to the same computer.
The default baud rate in PORTS.CFG is 57600. This should not be changed unless the
EEPROM has been corrupted. In the event of corrupted EEPROM, hit “AltS” in the OEM.EXE program
to change the baud rate to 9600 and pin 26 on the interface connector, J1, of the radio must be logic low
level to communicate.
Note: If the EEPROM parameters for baud rate are changed, and the radio is reset, these utilities
will not communicate with the radio until pin 26 is held at logic low level and the third line of
PORTS.CFG is changed to 9600.
5.2.4 Setup Scripts
AeroComm provides several scripts to allow easy setup and configuration for different modes. These setup
scripts are as follows:
S1AC.RTC – Setup client radio to Mode 1 Addressed
S1AS.RTC – Setup server radio to Mode 1 Addressed
S1NC.RTC– Setup client radio to Mode 1 Non-Addressed
S1NS.RTC– Setup server radio to Mode 1 Non-Addressed
S2AC.RTC– Setup client radio to Mode 2 Addressed
S2AS.RTC– Setup server radio to Mode 2 Addressed
S2NC.RTC– Setup client radio to Mode 2 Non-Addressed
S2NS.RTC– Setup server radio to Mode 2 Non-Addressed
S4AC.RTC– Setup client radio to Mode 4 Addressed
S4AS.RTC– Setup server radio to Mode 4 Addressed
S4NC.RTC– Setup client radio to Mode 4 Non-Addressed