AeroComm PKLR2400 Users Manual
PKLR2400 Radio
Hardware and Software
Interface Specification
Version 3.2
13256 W. 98th Street
Lenexa, KS 66215
(800) 492-2320
www.aerocomm.com
wireless@aerocomm.com
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Copyright Information/FCC User’s Notice
Copyright
Information
FCC U
SER'S NOTICE
WARNING: This equipment has been tested and found to comply with the limits for a
Copyright © 1999 A
EROCOMM
, Inc. All rights reserved.
The information contained in this manual and the accompanying
software programs are copyrighted and all rights are reserved by
EROCOMM
A
, Inc. A
EROCOMM
, 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 A
EROCOMM
, Inc. is
prohibited.
All brands and product names in this publication are registered
trademarks or trademarks of their respective holders.
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:
FCC N
• 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.
OTICE
WARNING: This device complies with Part 15 of the FCC Rules. Operation is subject to the
following two conditions: (1) this device may not cause harmful interfe rence and
(2) this device must accept any interference received, including interference that
may cause undesire d operation.
Revision s 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
Version 3.2 Updated FCC Statement – 9/8/1999
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 r ange or unusual environmental requir ements such as military, medical life-support or
life-sustaining equipment, are specifically not recommended without additional testing for such application.
Table of Contents
1. OVERVIEW
.......................................................................................................................................... 6
2. PKLR2400 SPECIFICATIONS...........................................................................................................7
3. THEORY OF OPERATION................................................................................................................ 8
3.1 D
3.2 S
EFINITIONS
ERIAL INTERFACE MODES
.................................................................................................................................... 8
.............................................................................................................. 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 I
NITIALIZATION SEQUENCE
............................................................................................................ 10
4. HARDWARE INTERFACE.............................................................................................................. 11
4.1 M
4.2 P
4.3 P
ECHANICAL OVERVIEW
IN DEFINITIONS FOR CONNECTOR
IN DESCRIPTIONS FOR CONNECTOR
............................................................................................................... 11
J1............................................................................................12
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
5.1 S
ERIAL ADAPTER BOARD
........................................................................................................................... 15
............................................................................................................... 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 S
OFTWARE 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 A
5.4 P
NTENNA BOARD
OWER SUPPLY SPECIFICATION
.......................................................................................................................... 22
...................................................................................................... 22
6. COMMAND SET ................................................................................................................................23
6.1 S
YSTEM 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 R
ADIO COMMAND SET SUMMARY
................................................................................................. 28
6.2.1 RF enable*............................................................................................................................ 28
Preliminary 4
PKLR
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
7.1 S
YSTEM
EEPROM P
ARAMETERS
...................................................................................... 31
.................................................................................................. 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 P
ROTOCOL
EEPROM P
ARAMETERS
.............................................................................................. 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 P
ARAMETER SUMMARY
................................................................................................ 38
8. INITIALIZING THE PKLR2400 RADIO........................................................................................ 39
Preliminary 5
Overview
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.
Preliminary 6
PKLR2400 Specifications
2. PKLR2400 Specifications
GENERAL
Bus Interface Serial (TTL Level Asynchronous) or Parallel through 40
pin mini con nect or. Amp P/N 177986-1 or Berg
Interface Data Rate
Serial
Parallel
Compliance Certifiable under:
Power Consumption
TX/RX Active (All Modes)
Interface ON/RF OFF (API Mode Only)
Sleepwalk (All Modes)
Standby (API Mode Only)
Channels Supports 77 non-in terf ering chan nel s
Security User assigned Syst em ID. Unique IEEE addres s on each
Prog to 800 kbps. Supports PC rate s to 57.6 Kbps
4 Mbps
US - FCC15.247
Canada - DOC
Europe - ETSI
Japan - MKK
115mA ty pical
45mA typi cal
35mA typi cal
30mA typi cal
radio.
RADIO
Frequency Ban d 2.402 – 2.478 GHz
Radio Type Spread Spectrum Freque ncy Hoppi ng
Output Pow er 10mW
Voltage 5V nominal +5%, +
Sensitivity -90dBm
Data Rate 1Mbps
Range Indoors up to 300ft, Ou tdoors u p to 3000f t
Can be extended with directional antenna
50mV ripple
ENVIRONMENTAL
Temperature (Operating) 0 to +60 C
Temperature (Storage) -50 to +85 C
Humidity (n on- conden si ng ) 10% to 90%
PHYSICAL
Dimension s 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 Attem pts Up to 255
Preliminary 7
PKLR2400 Specifications
3. Theory of Operation
3.1 Definitions
Server Host:
Client Host:
Host refers to both the server host and the client host
Host:
Server Radio:
Client Radio:
server radio
Authentication:
subsequent issuance of an In-Range* command by the Client Radio to the Client Host.
Unicast Address:
Broadcast Address:
The server host is the OEM device controlling the server radio
The client host is the OEM device controlling the client radio
The server radio is the “master” radio. It is the hub of communications
The client radio is a “slave” radio. It is controlled by it’s own Host, but is a slave to the
The acquisition of the IEEE 802.3 address of the Server Radio by the Client Radio and the
A frame that is directed to a single recipient as specified in IEEE 802.3.
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.
Preliminary 8
Theory of Operation
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.
only be exercised when the radio is in API Serial Interface Mode 03
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
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.
get an acknowledgement, they are signals to
NOT
. It is important to understand two
These commands can
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.
Preliminary 9
Theory of Operation
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
. During the power up sequence or upon a Reset* command, the Clear to Send (CTS) line is set high
occurs
(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
command can only be issued after the
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).
*Note:
CTS
from
Radio
TXD
LSB First
From Host
used the CTS signal will be
inverted coming from the radio .
Command Length ChecksumData
RF_enable*
If level translators are
and
In_range*
Send_data*
commands have been issued.
command . Th is
Delay for reply command
(1) (2)
Clear To Send minimum delay of 40
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.
Preliminary 10
µµµµ
s between (1) and (2) after end of data packet
Hardware Interface
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 fre quency 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
Preliminary 11
Developers Kit
4.2 Pin Definitions for Connector J1
The following pi nout summary is achieved through a 40 pin mini connector J1 (Amp P/N 177986-1).
Pin Serial
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
Parallel* Definition
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.
Preliminary 12
Loading...