Table of Contents
Summary of Contents for AeroComm PKLR2400
- Page 1 PKLR2400 Radio Hardware and Software Interface Specification Version 3.1 13256 W. 98 Street Lenexa, KS 66215 (800) 492-2320 www.aerocomm.com wireless@aerocomm.com !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
- Page 2 Copyright Information/FCC User’s Notice Copyright Copyright © 1999 A , Inc. All rights reserved. Information The information contained in this manual and the accompanying software programs are copyrighted and all rights are reserved by , Inc. A , Inc. reserves the right to make periodic modifications of this product without obligation to notify any person or entity of such revision.
- Page 3 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.
-
Page 4: Table Of Contents
Table of Contents OVERVIEW............................6 PKLR2400 SPECIFICATIONS......................7 THEORY OF OPERATION........................ 8 ............................ 8 EFINITIONS ......................8 ERIAL NTERFACE ODES 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... - Page 5 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 CONFIGURING THE PKLR2400 RADIO..................31 EEPROM P ....................31 YSTEM ARAMETERS 7.1.1 Product Identifier String/Version Information..............31 7.1.2 IEEE assigned MAC Address....................31 7.1.3...
-
Page 6: 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. -
Page 7: Pklr2400 Specifications
PKLR2400 Specifications 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 Prog to 800 kbps. Supports PC rates to 57.6 Kbps Parallel 4 Mbps... -
Page 8: Theory Of Operation
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. -
Page 9: Serial Interface Mode 03 - Api
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. -
Page 10: 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. -
Page 11: Hardware Interface
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 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”... -
Page 12: Pin Definitions For Connector J1
E2WP EEPROM Write Protect uP_RESET uP_RESET Microprocessor Reset 5V + 5% 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. Preliminary... -
Page 13: Pin Descriptions For Connector J1
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. -
Page 14: Microprocessor Reset (Up Reset)
Developers Kit 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. -
Page 15: Developers Kit
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: •... -
Page 16: Serial Adapter Board
Developers Kit 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. -
Page 17: J3-J9 Level Translator Settings
Developers Kit 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. -
Page 18: Oem.exe
OEM.CFG – Configuration file for OEM.EXE • OEMRWSP.INI – AeroComm Use Only These files are located in each of three directories as follows: OnePC – This directory contains all the files required to run the Client and Server radios on a single PC. -
Page 19: Rtc
Developers Kit 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. -
Page 20: Ports.cfg
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 –... - Page 21 Developers Kit S4NS.RTC– Setup server radio to Mode 4 Non-Addressed SP3CS.RTC –This file is used to configure both the client and server radio into Mode 3 Receive mode 1 (Unicast/Broadcast). SP3CS02.RTC – This file is used to configure both the client and server radio into Mode 3, receive mode 2 (unicast only) SP3CS03.RTC –...
-
Page 22: Antenna Board
Developers Kit 5.3 Antenna Board The developer kits are provided with (2) patch antennae mounted on a ground plane. In addition, (2) SMA male to MMCX plug, cables are provided to interface the antenna boards to the radio. Optional antennae are available for testing. Antenna selection is instrumental to and will impact overall system performance. -
Page 23: Command Set
This command is issued from the Host processor to the Radio. This command provides a software reset to the PKLR2400 Radio initializing the code at the same location as a hardware reset. This must be followed by an RF Enable. -
Page 24: Control
Command Set 6.1.2 Control* The Host processor will issue this command to Write and Read EEPROM as well as for NOP. Sub Command one byte Description Read EEPROM. Additional data: first two bytes specify starting address. Second two bytes specify ending address. -
Page 25: Standby* (This Command Not Yet Supported)
Command Set 6.1.4 Standby* (THIS COMMAND NOT YET SUPPORTED) This command is issued by the Host processor to put the Radio in one of two low power modes. For mode 0, the Radio should disable the radio and enter a low power state. The hop synching is the only allowed operation in this mode. -
Page 26: Status Reply
Command Set 6.1.7 Status Reply* This command will be sent by the Radio to the OEM Host in response to a Status Request command. All the different parameters pertain to the data link layer and are cumulative totals. Once this command has been sent back to the OEM Product, depending on whether the OEM Product desired an error counter variable reset, the reset operation is carried out. -
Page 27: Update Eeprom Checksum
6.1.8 Update EEPROM Checksum* This command is sent by the Host to the AeroComm module to tell it to recalculate the checksum. This is typically done by the Host CPU after it has completed writing data to the EEPROM on the AeroComm module. -
Page 28: Radio Command Set Summary
(6)Bytes for the IEEE 802.3 standard destination address and (6)Bytes for the IEEE 802.3 standard source address. These unique IEEE addresses are provided by AeroComm. See Section 4 for EEPROM location Note: The Length must include the IEEE 802.3 Header... -
Page 29: Send Data Complete
Command Set 6.2.3 Send data complete* The Radio will issue this command upon completion of the data transmission process, as indicated by a RF-layer Acknowledgment from the destination RF-device. An additional byte of data indicates a success or a failure code. This command must be returned for every send data command unless the device power fails. -
Page 30: Out Of Range
Command Set 6.2.6 Out of range* The Radio will issue this command upon detecting that it is out of range of a Server Radio. This command is only valid after reset or after an in range command has been issued to the Host processor. This command should have some hysterisis so that the Host processor isn’t flooded with these commands in a fringe coverage area. -
Page 31: Configuring The Pklr2400 Radio
AeroComm as AeroComm defaults or customer defaults. These parameters can also be configured by the customer using a PC and an AeroComm provided adapter. If the customer is writing to the EEPROM, they must use the Write EEPROM Command and enable E2WP, pin 37, or switch 2 on the serial adapter board included with the developer kit. -
Page 32: Channel Number
Configuring the PKLR2400 7.1.3 Channel Number EEPROM Address: 2EH Size: 1 byte Default: 00 Range: 01-75 This provides 75 unique and non-interfering pseudorandom hopping sequences or channels. This allows for up-to 75 independent, co-located data networks. Default shipped at 00. It is highly recommended that this be changed to a channel number other than 00. -
Page 33: Baud High (Bh) And Baud Low (Bl)
Configuring the PKLR2400 7.1.6 Baud High (BH) and Baud Low (BL) EEPROM Address: 40H and 41H respectively Size: 1 bytes Default: FF for BH and F1 for BL Range: 00-FF for BH and BL Baud High (BH) along with Baud Low (BL) is used to establish the data rate over the interface... -
Page 34: Protocol Eeprom Parameters
Configuring the PKLR2400 7.2 Protocol EEPROM Parameters The protocol EEPROM parameters are related to the Serial Mode interface selection. A summary of the required EEPROM settings is illustrated in Section 7.3. Note: These parameters can only be changed when the API Serial Interface Mode 03 is active. -
Page 35: Transmit Data Link Attempts
Server beacon that includes the Server IEEE source address. This parameter is very useful when operating in a fringe condition to minimize the In-Range and Out-of-Range commands that may flood the host. AeroComm has established a default value of 5 seconds through extensive testing. Preliminary... -
Page 36: End Character Definition
Configuring the PKLR2400 7.2.4 End Character Definition EEPROM Address: 3EH Size: 1 bytes Default: 0D Range: 00-FF This parameter is used only when the radio is operated in Serial Interface Mode 02 specified by EEPROM address 4AH. Otherwise, this parameter is ignored by the system. The parameter specified by the user will indicate the last character in a data packet. -
Page 37: Destination Address Control
Configuring the PKLR2400 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. -
Page 38: Broadcast Attempts
Configuring the PKLR2400 7.2.9 Broadcast Attempts EEPROM Address: 4EH Size: 1 bytes Default: 04H Range: 01-FF The Broadcast Attempt parameter applies only to the Broadcast modes for all four serial packet modes and specifies the number of times that the RF will broadcast every packet. The receiving radio will discard duplicate packets. -
Page 39: Initializing The Pklr2400 Radio
8. Initializing the PKLR2400 Radio Following is an example of the initialization sequence for both the Client and Server Radios following AeroComm or customer configuration of the EEPROM configuration parameters. This occurs only in the API Serial Interface Mode 03.
Need help?
Do you have a question about the PKLR2400 and is the answer not in the manual?
Questions and answers