Laird Connectivity PKLR2400-200 PKLR2400-200 User Manual exb22

AeroComm Corporation PKLR2400-200 exb22

Contents

revised users manual please remove the other

PKLR2400S-200200mW OEM TransceiverHardware and SoftwareInterface SpecificationVersion 1.113256 W. 98th StreetLenexa, KS 66215(800) 492-2320www.aerocomm.comwireless@aerocomm.com§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§
Copyright Information/FCC User’s NoticeCopyright Copyright © 2000 AEROCOMM, Inc. All rights reserved.Information The information contained in this manual and the accompanyingsoftware programs are copyrighted and all rights are reserved byAEROCOMM, Inc. AEROCOMM, Inc. reserves the right to makeperiodic modifications of this product without obligation to notifyany person or entity of such revision. Copying, duplicating, selling,or otherwise distributing any part of this product without the priorconsent of an authorized representative of AEROCOMM, Inc. isprohibited.All brands and product names in this publication are registeredtrademarks or trademarks of their respective holders.AGENCY APPROVAL OVERVIEWUS/FCC CAN/IC EUR/EN Portable Mobile FixedPKLR2400-200 X X Not Approved Not Approved X-32cm X-32cmNote: The product approval above is with antennas specified below.FCC NOTICE WARNING: This device complies with Part 15 of the FCC Rules. Operation is subject to the following twoconditions: (1) this device may not cause harmful interference and (2) this device must accept anyinterference received, including interference that may cause undesired operation.
ANTENNA WARNINGAPPROVED ANTENNA LISTManufacturer Part Number Type Gain Application*Centurion WCP-2400-MMCX ¼ Wave Dipole 2dBi M/FMaxrad Z986 Patch 2.5dBi M/FAeroComm NZH2400-MMCX (External) Microstrip 1dBi M/FNearson S131CL-5-RMM-2450S ¼ Wave Dipole 2dBi M/FNearson S181FL-5-RMM-2450S ¼ Wave Dipole 2dBi M/FNearson S191FL-5-RMM-2450S ¾ Wave Dipole 3dBi M/F*M=Mobile, F=Fixed/Basestation LABELING REQUIREMENTSRF EXPOSURE WARNING: The Original Equipment Manufacturer (OEM) must ensure that FCC labeling requirements aremet. This includes a clearly visible label on the outside of the OEM enclosure specifying theAeroComm FCC identifier, KQL-PKLR2400-200, for this product as well as the FCC Noticeabove. WARNING: This device has been tested with an MMCX connector with the antennas listed below. Whenintegrated in the OEMs product, these fixed antennas require installation preventing end-users fromreplacing them with non-approved antennas. Any antenna not in the following table must be testedto comply with FCC Section 15.203 for unique antenna connectors and Section 15.247 foremissions. WARNING: To satisfy FCC RF exposure requirements for mobile and base station transmitting devices, aseparation distance of 32cm or more should be maintained between the antenna of this deviceand persons during operation. To ensure compliance, operations at closer than this distance isnot recommended.The preceding statement must be included as a CAUTION statement in manualsfor OEM products to alert users on FCC RF Exposure compliance.
Preliminary 4DOC: 504JDSR2Revision DescriptionVersion 1.0 Initial Release Version – 8/18/00Version 1.1 Updated FCC requirements – 9/16/00Copyright © 2000AeroComm, Inc.This material is preliminary.Information furnished by AeroComm in this specification is believed to be accurate. Devices sold byAeroComm are covered by the warranty and patent indemnification provisions appearing in its Terms ofSale only. AeroComm makes no warranty, express, statutory, implied or by description, regarding theinformation set forth herein. AeroComm reserves the right to change specifications at any time and withoutnotice.AeroComm’s products are intended for use in normal commercial applications. Applications requiringextended temperature range or unusual environmental requirements such as military, medical life-support orlife-sustaining equipment, are specifically not recommended without additional testing for such application.
Table of Contents Preliminary 5DOC: 504JDSR21.OVERVIEW .............................................................................................................................................................72. PKLR2400 SPECIFICATIONS ...........................................................................................................................83. THEORY OF OPERATION..................................................................................................................................93.1 DEFINITIONS....................................................................................................................................................93.2 INTERFACE SIGNAL DEFINITIONS..............................................................................................................103.3 HOST SOFTWARE/HARDWARE INTERFACE DEFINITION.......................................................................113.3.1 Clear To Send (CTS)..........................................................................................................................113.3.2 Reserved................................................................................................................................................113.3.3 Baud Rate Selector (BDSEL)............................................................................................................113.3.4 In Range................................................................................................................................................113.3.5 Received Signal Strength Indicator................................................................................................123.3.6 Request To Send (RTS) ......................................................................................................................123.3.7 Microprocessor Reset (uP_RESET) ................................................................................................123.3.8 EEPROM Write Enable (WR_ENA) .................................................................................................124. SERIAL INTERFACE MODES...........................................................................................................................134.1 SERIAL INTERFACE MODE 01 – TRANSPARENT, FIXED LENGTH, WITH TIMEOUT..........................134.2 SERIAL INTERFACE MODE 02 – TRANSPARENT, END CHARACTER.....................................................134.3 SERIAL INTERFACE MODE 03 – API..........................................................................................................134.4 SERIAL INTERFACE MODE 04 – TRANSPARENT, FIXED LENGTH, NO TIMEOUT ..............................144.5 SERIAL INTERFACE BUFFER........................................................................................................................144.6 INITIALIZATION SEQUENCE .......................................................................................................................145. CONFIGURING THE PKLR2400......................................................................................................................165.1 SYSTEM EEPROM PARAMETERS................................................................................................................165.1.1 Product Identifier String/Version Information..............................................................................165.1.2 IEEE assigned MAC Address............................................................................................................165.1.3 Channel Number.................................................................................................................................175.1.4 Client/Server Mode ............................................................................................................................175.1.5 System ID ..............................................................................................................................................175.1.6 Baud High (BH) and Baud Low (BL)..............................................................................................185.2 PROTOCOL EEPROM PARAMETERS...........................................................................................................195.2.1 Transmit Data Link Attempts............................................................................................................205.2.2 Receive mode .......................................................................................................................................205.2.3 In-Range, Out-of-Range Refresh.......................................................................................................205.2.4 End Character Definition..................................................................................................................215.2.5 Fixed Packet Length High Byte/Low Byte .....................................................................................215.2.6 Serial Interface/Power Down Modes ..............................................................................................225.2.7 Destination Address Control............................................................................................................245.2.8 Interface Timeout Control.................................................................................................................245.2.9 Broadcast Attempts.............................................................................................................................245.2.10 RF Mode ...............................................................................................................................................255.3 EEPROM PARAMETER SUMMARY.............................................................................................................266. API COMMAND SET (SERIAL INTERFACE MODE 03 ONLY)................................................................276.1 SYSTEM COMMAND SET SUMMARY .........................................................................................................276.1.1 Reset*....................................................................................................................................................276.1.2 Control* ...............................................................................................................................................286.1.3 Diagnostic result* ..............................................................................................................................286.1.4 Reset EEPROM*..................................................................................................................................29
Table of Contents Preliminary 6DOC: 504JDSR26.1.5 Status Request*...................................................................................................................................296.1.6 Status Reply*.......................................................................................................................................296.1.7 Update EEPROM Checksum* ..........................................................................................................306.1.8 Check EEPROM Checksum* ............................................................................................................306.1.9 EEPROM Checksum Status* ............................................................................................................306.1.10 Acknowledge*.....................................................................................................................................306.2 TRANSCEIVER COMMAND SET SUMMARY ...............................................................................................316.2.1 RF enable*...........................................................................................................................................316.2.2 Send data* ...........................................................................................................................................316.2.3 Send data complete*..........................................................................................................................326.2.4 Received data*....................................................................................................................................326.2.5 In range* ..............................................................................................................................................326.2.6 Out of range*.......................................................................................................................................336.3 INITIALIZING THE PKLR2400 TRANSCEIVER............................................................................................337. MECHANICAL OVERVIEW ..............................................................................................................................348. ORDERING INFORMATION.............................................................................................................................358.1 PRODUCT PART NUMBERS...........................................................................................................................358.2 DEVELOPER KIT PART NUMBERS..............................................................................................................35
Overview Preliminary 7DOC: 504JDSR21. OverviewThis document contains information about the hardware and software interface between anAeroComm PKLR2400 transceiver and an OEM Host. Information includes the theory of operation, systemissues, and a basic command set for operational control of the system and transceiver.The Transceiver is designed to allow flexibility at the hardware interface level with a minimumnumber of actual hardware pins connecting the transceiver and the OEM Product. The transceiver iscontrolled by a Dallas 87C520 microcontroller providing program storage. A separate EEPROM providesuser definable parameter storage.The RF system is Server/Client (Master/Slave) architecture. Data can be transmitted from Client toServer or Server to Client, but not from Client to Client, or Server to Server.The Serial Interface Modes provide four different serial interfaces. This protocol providessignificant flexibility to the OEM allowing them to provide data in many forms including packet, endcharacter and fixed-length with and without timeouts.
PKLR2400 Specifications Preliminary 8DOC: 504JDSR22. PKLR2400 SpecificationsGENERALInterface Serial (TTL Level Asynchronous) 40 pin miniconnector. Amp P/N 177986-1Interface Data Rate Serial Programmable to 882Kbps. PC rates to 57.6 KbpsPower Consumption TX/RX Active (All Modes) Interface ON/RF OFF (API Mode Only) Sleep Walk (All Modes) Standby (API Mode Only)400mA/115mA typical45mA typical25mA typical20mA typicalChannels Supports 77 non-interfering channelsSecurity User assigned System ID. Unique IEEE addresses oneach transceiver.RADIOFrequency Band 2.402 – 2.478 GHzTransceiver Type Spread Spectrum Frequency HoppingOutput Power (Conducted, no antenna) 199.5mWEffective Radiated Isotropic Power (EIRP withHighest Gain Antenna)363.1mWInput Voltage 5V nominal +2%, + 50mV rippleSensitivity -90dBmData Rate 882KbpsRange Indoors up to 1000 ft., Outdoors up to 10,000 ft.ENVIRONMENTALTemperature (Operating) 0 °C to +70 °CTemperature (Storage) -50 °C to +85 °CHumidity (non-condensing) 10% to 90%PHYSICALDimensions 1.65” x 2.65” x 0.20”Antenna Connector Standard MMCX jackWeight Less than 0.5 ounceSOFTWAREUser Configurable Options Host Interface Data Rate Up to 882Kbps Variable Packet Length Up to 2Kbyte Serial Interface Modes (3) Transparent and (1) API Diagnostic Error Counters API mode User Programmable Attempts Up to 255
Theory of Operation Preliminary 9DOC: 504JDSR23. Theory of OperationThe PKLR2400 has a serial interface that allows the OEM Host to send and receive communicationsto and from the transceiver. All I/O is 5Vdc TTL level signals except for RSSI. All outputs are weakly pulledlogic high (20k – 50k ohms) when left unconnected and are driven logic high at reset.3.1 DefinitionsServer Host: The Server Host is the OEM device controlling the Server transceiverClient Host: The Client Host is the OEM device controlling the Client transceiverHost: Host refers to both the Server Host and the Client HostServer Transceiver: The Server transceiver is the “master” transceiver. It is the hub of communicationsClient Transceiver: The Client transceiver is a “slave” transceiver. It is controlled by it’s own Host, but is aslave to the Server transceiverAuthentication: The acquisition of the IEEE 802.3 address of the Server transceiver by the Client transceiverand the subsequent issuance of an In-Range* command by the Client transceiver 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 a multiple recipients as specified in IEEE 802.3.
Theory of Operation Preliminary 10DOC: 504JDSR23.2 Interface Signal DefinitionsThe following pinout is for the 40-pin mini-connector J1 (Amp P/N 177986-1). I/O direction is withregard to the transceiver.Table 1. Transceiver Interface Signal DefinitionsPin Type Signal Name Function1GNDGNDSignal Ground2IPKTMODE Packet Mode - When active (Active Low), the transceiver is forced into API Mode 33VCC VCC 5V + 2%4NC NC No Connect5VCC VCC 5V + 2%6NC NC No Connect7NC NC No Connect8NC NC No Connect9NC NC No Connect10 NC NC No Connect11 ORSSI Received Signal Strength - An analog output giving a relative indication of received signalstrength while in receive mode.12 NC NC No Connect13 NC NC No Connect/Data 714 OTXD Transmitted data out of the transceiver15 OIn-Range In-Range - Provides a logic low signal when the Client detects a master with the same SystemID and Channel. This pin is active only in Transparent Serial Interface Modes 1, 2 and 4.16 IRXD Data input to the transceiver17 IRI_IN Ring Indicator to communicate to modem18 NC NC No Connect19 ORI_OUT Ring Indicator to communicate to computer20 GND GND Ground21 GND GND Ground22 IDCD_IN Data Carrier Detect to communicate to modem23 OCTS Clear to Send – Active Low when the transceiver is ready to accept data for transmission.24 Reserved Reserved Reserved25 Reserved Reserved Reserved26 IBDSEL Baud Select – Take this pin active (Active Low) to force the transceiver into a known serialinterface baud rate (9600 8-N-1)27IRTSRTS - MUST BE LOW TO ALLOW THE HOST TO RECEIVE DATA FROM THE PKLR2400.28 NC NC No Connect29 NC NC No Connect30 NC NC No Connect31 NC NC No Connect32 ODSR Data Set Ready33 NC NC No Connect34 IDTR Data Terminal35 NC NC No Connect36 ODCD_OUT Data Carrier Detect to communicate to computer37 IWR_ENA EEPROM Write Enable – Enabled when pin 37 is logic low. Pin 37 must be logic low to Write tothe EEPROM.NOTE: The transceiver should NOT be write enabled during the initial power up or upon ahardware reset to ensure the integrity of the EEPROM data.38 IuP_RESET Microprocessor Reset – The transceiver is reset by holding pin 38 logic high for a minimum of2ms. If a reset is performed after power has been applied to the transceiver and is stable, thereset time will be significantly less. At all other times, pin 38 should be logic low. If pin 38 is notconnected, the microprocessor will hold pin 38 at logic low.39 VCC VCC 5V + 2%40 GND GND Signal GroundI = Input to the transceiverO = Output from the transceiver
Theory of Operation Preliminary 11DOC: 504JDSR23.3 Host Software/Hardware Interface Definition3.3.1 Clear To Send (CTS)Clear To Send (CTS), pin 23, requires a minimum delay of 40µs between (1) and (2) after the end ofeach data packet.Figure 1. Timing Note for CTS Pin3.3.2 ReservedAeroComm uses the reserved pins 24 and 25 for internal testing and/or future transceiverenhancements. These pins should be treated as No Connect pins and must not be connected to logic highor low, but must be left floating.3.3.3 Baud Rate Selector (BDSEL)The Baud Rate Selector (BDSEL), pin 26, provides the user a default method of communicating withthe transceiver in the event the EEPROM baud rate parameters become corrupted. If pin 26 is logic high ornot connected, the baud rate will default to that specified in EEPROM. If pin 26 is logic low at RESET, thebaud rate will default to 9600 baud.3.3.4 In RangeThe IN_RANGE pin at the connector will be driven logic low when a Client is in range of a Serveron the same channel and system ID. If the Client cannot hear a PKLR2400 Server for an amount of time thatis programmable (Range refresh time) in the EEPROM, the PKLR2400 Client drives the IN_RANGE pin logichigh and enters a search mode looking for a PKLR2400 Server. As soon as it detects a Server, theIN_RANGE pin will be driven logic low.CTSfromTransceiverDelay for reply command*Note: This graph represents CTS as itwould be seen at the DB-9 connector. Atthe transceiver, the signal will be inverted.TXDMSB FirstFrom Host Command Length ChecksumData(1) (2)
Theory of Operation Preliminary 12DOC: 504JDSR23.3.5 Received Signal Strength IndicatorReceived Signal Strength Indicator is used by the Host as an indication of instantaneous signalstrength at the receiver. The Host must calibrate RSSI without a signal being presented to the receiver.Figure 1 shows approximate RSSI performance. The RSSI pin requires the Host to provide a 27kΩ pull-downto ground. Output is 1.20V to 5.0V.3.3.6 Request To Send (RTS)When the RTS bit is enabled in the PKLR2400 EEPROM, pin 27 (RTS) must be logic low to allowthe Host to receive data from the PKLR2400.3.3.7 Microprocessor Reset (uP_RESET)Microprocessor Reset (uP_RESET) is achieved by holding pin 38 at logic high for a minimum of2ms. If uP_RESET is performed after power has been applied to the transceiver and is stable, the reset timewill be significantly less. At all other times, pin 38 should be logic low. If pin 38 is not connected, themicroprocessor will hold pin 38 at logic low.3.3.8 EEPROM Write Enable (WR_ENA)EEPROM Write Enable (WR_ENA) is enabled when pin 37 is logic low. Pin 37 must be logic low towrite to the EEPROM.NOTE: The OEM must ensure that the transceiver is NOT write-enabled during initial power up and duringa hardware RESET. Failure to do so may result in corruption of important EEPROM data.Figure 1 - RSSI Voltage vs. Received Signal Strength-100-90-80-70-60-50-40-30-20-1001.2 1.3 1.57 2.3 3.8 4.5Voltage (VDC)Signal at Receiver (dBm)
Configuring the PKLR2400 Preliminary 13DOC: 504JDSR24. Serial Interface ModesThe PKLR2400 provides four different Serial Interface Modes with programmability in each modeallowing maximum system flexibility. These four Serial Interface Modes include three transparent modes andone API mode. The transceiver-to-transceiver protocol is identical for all three Transparent Serial InterfaceModes. This allows all three Transparent Serial Interface Modes to coexist within the same network. TheAPI Serial Interface Mode 03 is not interoperable with Transparent Serial Interface Modes 01, 02 and 04.4.1 Serial Interface Mode 01 – Transparent, Fixed Length, with TimeoutMode 01 specifies transparent mode with fixed length packets and active timeout. Packets will betransmitted 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 bythe user in EEPROM address locations 43H and 44H.• A byte gap larger than the timeout specified by the user in EEPROM location 4DH occurs.4.2 Serial Interface Mode 02 – Transparent, End CharacterMode 02 specifies transparent mode with an End Character. Packets will be transmitted over the RFinterface when the user-defined End Character is received by the transceiver over the interface. The EndCharacter is defined by the user at EEPROM location 3EH.4.3 Serial Interface Mode 03 – APIMode 03 specifies API Mode. In this mode, the OEM has control of the transceiver command setdetailed 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 thetransceiver and system. These commands allow the customer to establish system parameters through theprogramming of variables in EEPROM as well as monitoring system performance. These commands can onlybe exercised when the transceiver is in API Serial Interface Mode 03. It is important to understand twoaspects of the software commands.1. There are only three commands that are issued from the Client to the Client Host. These threecommands are Out_of_range*, In_range* and Receive_data*. The Receive_data*command is the only command issued from the Server to the Server Host. It is important tonote that these commands will NOT get an acknowledgement, they are signals to the Host toalert it to incoming data, or a change of status.2. All remaining commands initiated by the Host MUST receive an acknowledge from thetransceiver to signal completion of the assigned task. This works as flow control for theinformation going to the transceiver.Since more than one Client can transmit to the Server, it is possible that there will be multipleReceive_data* commands at the same time. Since there is no reply command at the completion ofReceive_data*, the Host must be capable of handling multiple Receive_data* commands at one time.Note: This means that whenever a command is initiated by the transceiver to the Host, the Host must beready to accept the command and any data following the command.
Configuring the PKLR2400 Preliminary 14DOC: 504JDSR2Note: A full list of commands, definitions, and implementation can be found in Section 6.4.4 Serial Interface Mode 04 – Transparent, Fixed Length, No TimeoutMode 04 specifies transparent mode with fixed length packets and no timeout. Packets will betransmitted over the RF interface when the number of data bytes received over the interface is equal to thebuffer specified by the user in EEPROM address locations 43H and 44H.4.5 Serial Interface BufferThe serial interface buffer provides 8Kbytes of memory broken into four dynamic regions. In APISerial Interface Mode 03, only one region is utilized. In Transparent Serial Interface Modes 01, 02 and 04, abuffer 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 firstregion and the remaining 7.5Kbytes will be dynamically allocated for the next three packets. It is stronglyrecommended that CTS or upper layer protocol with acknowledgements be used by the OEM whenoperating in any of the Transparent Serial Interface 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 bediscarded by the transceiver. This can be eliminated if the OEM utilizes CTS.4.6 Initialization SequenceUpon reset or power-up, the PKLR2400 requires a minimum of 400ms for hardware initialization priorto receiving any data or commands. When operating in the three Transparent Serial Interface Modes, theinitialization sequence is managed by the AeroComm protocol. In-Range commands are not issued and thereis no acknowledge from the transceiver on data delivery unless the OEM protocol has built-inacknowledgement. An In-Range hardware pin, 15, provides In-Range information for Transparent SerialInterface Modes.When operating in the API Serial Interface Mode 03, the following initialization sequenceoccurs. During the power up sequence or upon a Reset* command, the Clear to Send (CTS) line is drivenlogic high (5V TTL logic levels). While CTS is logic high, initialization occurs, and when finished, CTS isdriven logic low indicating successful initialization is complete.Note: At this point, the only command that can not be issued is the Send_data* command. This commandcan only be issued after the RF_enable* and In_range* commands have been issued.Before data communications can begin, a Client needs to be authenticated. The Client Host mustissue an RF_enable* command to activate the Client and receive an acknowledgement from the Client. TheServer transmits a beacon containing its IEEE 802.3 address. Once the Client has been activated by use ofthe RF_enable* command, it will receive the Server IEEE 802.3 address once it is in range. Upon receivingthe IEEE 802.3 Server address, the Client will issue an In_range* command to the Client Host containing theIEEE 802.3 Server address.The Client Host must receive the In_range* command from the Client before the Send_data*command is invoked. Broadcast mode, as defined by IEEE 802.3, is supported and can be used to send data
Configuring the PKLR2400 Preliminary 15DOC: 504JDSR2to all transceivers that are within range but its use should be limited because reception of the message is notguaranteed.When the last bit of data is transferred from the Host to the transceiver, the Host must wait for theCTS line to transition logic high (meaning that the transceiver has found the end of the data packet) andthen transition back to logic low (meaning that the transceiver is ready for the next command).Clear To Send minimum delay of 40µµs between (1) and (2) after end of data packetNote: All serial data must be transmitted LSB first.Note: These transceivers 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 commandinterleaving.CTSfromTranscDelay for reply command*Note: This graph represents CTS as itwould be seen at the DB-9 connector. Atthe transceiver, the signal will be inverted.TXDLSB FirstFrom Host Command Length ChecksumData(1) (2)
Configuring the PKLR2400 Preliminary 16DOC: 504JDSR25. Configuring the PKLR2400The various configurable parameters are stored in the EEPROM in the transceiver. Theseparameters are read by the AeroComm firmware on power-up or when a reset is executed. These parameterscan be configured by AeroComm or by the customer using a PC and a serial adapter board included in theDeveloper Kit. If the customer is writing to the EEPROM, they must use the Write EEPROM Command andenable pin 37 (WR_ENA), or switch 2 on the serial adapter board. The different configurable parameters andtheir respective EEPROM locations are highlighted in this chapter.NOTE: WRITING TO ANY OTHER LOCATIONS IN EEPROM CAN CAUSE THE RADIO TOMALFUNCTION5.1 System EEPROM ParametersThe system EEPROM parameters provide general system configuration information for thetransceiver. These parameters can be monitored and changed independent of the serial interface protocol.These parameters can only be changed when the API Serial Interface Mode 03 is active. See Section 7.1for details.EEPROMAddress Size Description0H 40 bytes Product identifier string/Version Info28H 6 bytes IEEE assigned MAC Address2EH 1 byte Channel number – Range = 00-4C; Default = 00;33H 1 byte Client/Server mode01 – Server mode02 – Client mode (default)34H 8 bytes System ID – Used to demarcate RF networks (default=00 00 00 00 00 0000 01)40H 1 byte Baud High (BH) – Range = 00-FF; Default = FF41H 1 byte Baud Low (BL) – Range = 00-FF; Default = F15.1.1 Product Identifier String/Version InformationEEPROM Address: 0HSize: 40 bytesUseful for OEM to read AeroComm version information. This information should not beoverwritten by the OEM. Original information is restored when a RESET EEPROM command is issued.5.1.2 IEEE assigned MAC AddressEEPROM Address: 28HSize: 6 bytesThis is the unique, 6-byte, IEEE 802.3 Ethernet address assigned by AeroComm to each transceiver.This unique address should not be changed.
Configuring the PKLR2400 Preliminary 17DOC: 504JDSR25.1.3 Channel NumberEEPROM Address: 2EHSize: 1 byteDefault: 00Range: 00-4CThis provides 77 unique and non-interfering pseudorandom hopping sequences or channels. Thisallows for up-to 77 independent, co-located data networks. Default shipped at 00. It is highly recommendedthat this be changed to a channel number other than 00.Note: Channel Number AND System ID between Clients and Server must be identical for transceivers tocommunicate.5.1.4 Client/Server ModeEEPROM Address: 33HSize: 1 byteDefault: 02Range: 01-02Specifies whether the transceiver is operating in the Client Mode (02) or Server Mode (01)5.1.5 System IDEEPROM Address: 34HSize: 8 bytesDefault: 00 00 00 00 00 00 00 01Range: 00 00 00 00 00 00 00 00 to FF FF FF FF FF FF FF FFNote: Channel Number AND System ID between Clients and Server must be identical for transceivers tocommunicate.
Configuring the PKLR2400 Preliminary 18DOC: 504JDSR25.1.6 Baud High (BH) and Baud Low (BL)EEPROM Address: 40H and 41H respectivelySize: 1 byteDefault: FF for BH and F1 for BLRange: 00-FF for BH and BLBaud High (BH) along with Baud Low (BL) is used to establish the data rate over the interfacebetween the OEM transceiver and Host as follows:Sample BHBL selections for common Baud Rates(Using a 28.224 MHz Crystal)Baud Rate BH BL300 F4 842,400 FE 914,800 FF 489,600 FF A419,200 FF D228,800 FF E138,400 FF E957,600 (default) FF F1115,200 Not Supported Not SupportedCustom baud rates can be obtained through the use of the following formula:28.224 * 106Baud Rate = 32.0 * (65,536 – B ,BL)Note: The calculated value must be within 3% of the actual value.
Configuring the PKLR2400 Preliminary 19DOC: 504JDSR25.2 Protocol EEPROM ParametersThe protocol EEPROM parameters are related to the Serial Mode interface selection. A summary ofthe 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. When inTransparent Serial Interface Modes, this can be accomplished by holding pin 2, PKTMODE, logic low andresetting.Note: When writing to EEPROM using the developer kit, remember to hold the EEPROM write enable switchduring the write command.EEPROMAddressSize Description2FH 1 byte Transmit data link attempts; Range = 01 - FF;Default = 10H;31H 1 byte Receive mode - determines what type of data frames are received by theOEM Product, based on MAC address of received frame01 - unicast/broadcast data (default)02 - unicast only03 - all (promiscuous mode)32H 1 byte In-Range, Out-of-Range Refresh. This byte specifies the number of 250ms ticks between range indications. This gives a range of .05 secondsto 12.5 seconds.3EH 1 byte End Character Definition. This byte specifies the character that will beused to signify the end of a packet.43H 1 byte Fixed Packet Length HIGH BYTE44H 1 byte Fixed Packet Length LOW BYTE4AH 1 byte Serial Interface/Power Down Modes01 – Transparent, Fixed Length, with Timeout02 – Transparent, End Character03 – API04 – Transparent, Fixed Length, No Timeout4BH 1 byte Destination Address Control00 – Addressed Mode: Destination address is the IEEE 6 bytes at 50H.This mode utilized RF-Layer acknowledges to guarantee delivery of thepacket.01 – Broadcast Mode: No RF-Layer acknowledge, must set TransmitAttempts (2FH) to 01.4DH 1 byte Interface Timeout Control00 – 4 mS40 – 40 mS80 – 300 mSC0 – 2.6 S4EH 1 byte Broadcast Attempts; Range 01-FF; Default 044FH 1 byte RF Mode Byte01 – Turbo Bit disabled03 – Turbo Bit enabled
Configuring the PKLR2400 Preliminary 20DOC: 504JDSR25.2.1 Transmit Data Link AttemptsEEPROM Address: 2FHSize: 1 byteDefault: 10HRange: 01-FFThis parameter specifies the maximum number of attempts over the RF interface. Serial Interfacemode 03 will respond with a Send Data Failure when maximum Data Link attempts is achieved. All othermodes will not receive an acknowledge.Note: Transmit Data Link Attempts must be set to 01 when operating in the Broadcast Mode of theAddress Transparent Control.5.2.2 Receive modeEEPROM Address: 31HSize: 1 byteDefault: 03Range: 01-03This parameter applies only to API Serial Interface Mode 03. The default, 01, specifiesUnicast/Broadcast. Unicast will receive all packets that match the receiving unit IEEE assigned address.Broadcast is achieved by placing FF in all six bytes of the IEEE assigned destination address sent fromsender. In Broadcast mode, the receiver will accept all data with a destination address that has FF in all sixbytes. It is important to note that there is no RF acknowledge on Broadcast packets. Mode 01 will acceptUnicast and Broadcast data packets and discard all others. In Unicast only mode, 02, The receivingtransceiver will receive only Unicast packets and discard all others. In Promiscuous mode, 03, the receivingtransceiver will accept all packets with the same System ID.Note: The Receive Mode must be set to 03 in all Transparent Serial Interface Modesincluding 01, 02 and 04 specified by EEPROM address 4AH.5.2.3 In-Range, Out-of-Range RefreshEEPROM Address: 32HSize: 1 byteDefault: 14HRange: 01-FFThis parameter is used only when the transceiver is operating in API Serial Interface Mode 03. TheIn-Range, Out-of-Range Refresh parameter allows the user to select the interval between which the Clientsearches for Server beacon that includes the Server IEEE source address. This parameter is very usefulwhen operating in a fringe condition to minimize the In-Range and Out-of-Range commands that may floodthe Host. AeroComm has established a default value of 5 seconds through extensive testing.
Configuring the PKLR2400 Preliminary 21DOC: 504JDSR25.2.4 End Character DefinitionEEPROM Address: 3EHSize: 1 byteDefault: FFRange: 00-FFThis parameter is used only when the transceiver is operated in Serial Interface Mode 02 specifiedby EEPROM address 4AH. Otherwise, this parameter is ignored by the system. The parameter specified bythe user will indicate the last character in a data packet. When this end character is seen by the transceiver,the packet will be transmitted. The packet length including the end character can not exceed 2Kbytes.5.2.5 Fixed Packet Length High Byte/Low ByteEEPROM Address: 43H/44HSize: 1 byte eachDefault: 01/00Range: 00/01 to 07/FFHTHIS PARAMETER IS ACTIVE ONLY WHEN THE TRANSCEIVER IS IN SERIAL INTERFACEMODES 01 OR 04 SPECIFIED BY EEPROM ADDRESS 4AH. THIS PARAMETER IS IGNORED IN ALLOTHER MODES. THE FIXED PACKET LENGTH CAN NOT EXCEED 2KBYTES OR IT WILL NOT BERECEIVED.
Configuring the PKLR2400 Preliminary 22DOC: 504JDSR25.2.6 Serial Interface/Power Down ModesEEPROM Address: 4AHSize: 1 byteDefault: 01Range: 01-04THERE ARE FOUR SERIAL INTERFACE MODES FOR THE OEM TRANSCEIVER INCLUDINGONE PACKET MODE AND THREE TRANSPARENT MODES. ALL MODES ARE DIFFERENTIATED BYTHE DEFINITION OF WHEN DATA WILL BE TRANSMITTED BY THE TRANSCEIVER.MODE 01 SPECIFIES TRANSPARENT MODE WITH FIXED LENGTH PACKETS AND ACTIVETIMEOUT. PACKETS WILL BE TRANSMITTED OVER THE RF INTERFACE WHEN ONE OF THEFOLLOWING CONDITIONS OCCURS:• THE NUMBER OF DATA BYTES RECEIVED OVER THE INTERFACE IS EQUAL TOTHE BUFFER SPECIFIED BY THE USER IN EEPROM ADDRESS LOCATIONS 43HAND 44H.• A BYTE GAP LARGER THE TIMEOUT SPECIFIED BY THE USER IN EEPROMLOCATION 4DH OCCURS.Mode 02 specifies transparent mode with End Character. Packets will be transmitted over the RFinterface when the user-defined End Character is received by the transceiver over the interface. The EndCharacter is defined by the user at EEPROM location 3EH.Mode 03 specifies API Mode. In this mode, the OEM has control of the transceiver command setdetailed in Section 6.2. Packets are buffered and transmitted at the direction of the OEM.Mode 04 specifies transparent mode with fixed length packets and no timeout. Packets will betransmitted over the RF interface when the number of data bytes received over the interface is equal to thebuffer specified by the user in EEPROM address locations 43H and 44H.Note: EEPROM parameters cannot be read or written once the transceivers are programmed and reset in anyof the Transparent modes 01, 02 or 04. The transceiver must be forced to API mode 03 to access EEPROMparameters. This can only be accomplished by holding pin 2 logic low during and after reset.5.2.6.1 Power Down ModesThe PKLR2400S Power Down Modes include a Sleep Walk and Deep Sleep mode. Sleep Walk isfor Clients only and Deep Sleep is for Servers only.If bit 7 of the Serial Interface/Power down Mode Byte is set, the Client enters into Sleep Walk mode. Thisapplies to ALL modes (01-04).In API mode 3, the user can issue commands to place the transceiver into the power down modes. Thecommands are as follows: (CS is checksum)API mode commands.88 01 00 00 CS This is to command the transceiver into Sleep Walk88 01 00 01 CS This is to command the transceiver into Deep Sleep mode.88 01 00 04 CS This will cancel the power down functions.
Configuring the PKLR2400 Preliminary 23DOC: 504JDSR2*Note: it is necessary to enable the RF before commanding the transceiver into a power down mode in APIMode 03.5.2.6.1.1 Power Down Wake-up eventA power down wake-up event occurs when data is sent to the transceiver over the serialinterface or over the RF channel causing the transceivers to leave power down.Deep Sleep mode: (Servers only)In Deep Sleep mode the Server completely shuts down and remains in a powered down mode untila byte is received over the serial interface. This is the only wake-up event that is valid in Deep Sleep mode.The Server will not wake up if a Client tries to transmit data to the Server. Therefore, this mode is intendedfor use on Servers that do not need to monitor the RF for incoming packets because it initiates allcommunications.Sleep Walk mode: (Clients only)In Sleep Walk mode, the Client will shut down after a certain amount of inactivity, this is called theWait Time. In Sleep Walk mode, the Client will wake up when it receives either a RF packet or a byte overthe serial interface. The amount of time is user programmable and can be programmed in EEPROM location7D. The user can also program how long the Client is asleep (Sleep Time) in location 7A. After the amountof time programmed in 7A has elapsed, the Client will wake up and listen to the RF for any incoming traffic.If the Client hears the Server beacon and there is no pending RF data to be received, then the Client willreturn to sleep 2mS later. If the Client does not hear the Server’s beacon, it will stay awake for 50mS to tryand find the beacon. If a Client does not hear a beacon after 50ms, it will go back to sleep and repeat thecycle.7AH Sleep Time (3 Byte number) – This is loaded in 200mS increments and is how long the Client isasleep when it is in Sleep Walk mode.7DH Wait Time (3 Byte number) – This is also in 200mS increments and is how long the Client waits,before going to sleep.5.2.6.2 ModemIf bit 6 of the serial control byte is set, then the transceiver uses all of the modem lines (DCD, DSR, DTR, RI,RTS, and CTS). If bit 3 is set, then the transceiver will listen to and respect RTS.*Note: If bit 6 is set, enabling modem control lines, then bit 3 must be set for the transceivers to operateproperly.
Configuring the PKLR2400 Preliminary 24DOC: 504JDSR25.2.7 Destination Address ControlEEPROM Address: 4BHSize: 1 byteDefault: 00Range: 00-01THIS PARAMETER SETS THE DESTINATION ADDRESS FOR TRANSPARENT SERIALINTERFACE MODES ONLY. THE API SERIAL INTERFACE MODE 03 UTILIZES THE RECEIVE MODEAT EEPROM ADDRESS 31H TO SPECIFY ADDRESS MODES. WITH DESTINATION ADDRESSCONTROL SET AT THE DEFAULT, 00, THE TRANSCEIVER WILL DETERMINE IF THE SIX BYTE IEEEADDRESS AT 50H MATCHES. IF THE DESTINATION ADDRESS MATCHES, THE DATA PACKET ISFORWARDED TO THE OEM HOST. OTHERWISE THE DATA IS DISCARDED. THIS ADDRESSEDMODE GUARANTEES DELIVERY OF THE DATA PACKET OVER THE TRANSCEIVER LINK BY USINGACKNOWLEDGEMENTS.WITH DESTINATION ADDRESS CONTROL SET TO BROADCAST MODE, 01, CLIENTSWILL RECEIVE ALL DATA PACKETS. THERE ARE NO ACKNOWLEDGEMENTS AND NO DATAPACKET RETRIES IN THIS MODE.Clients can operate in Destination Address Control Mode 00, providing more reliable delivery ofdata to the Server. At the same time, the Server can operate in Destination Control Mode 01, acting as abroadcasting Server without guaranteed delivery. This provides a unique method of implementing a datanetwork of many-to-one or one-to-many.5.2.8 Interface Timeout ControlEEPROM Address: 4DHSize: 1 byteDefault: 00HRange: 00, 40, 80 or C0THE TIMEOUT PARAMETER APPLIES ONLY TO THE TRANSPARENT SERIAL INTERFACEMODE 01 WITH FIXED LENGTH PACKETS AND TIMEOUT. THIS PARAMETER SPECIFIES THEAMOUNT OF TIME BETWEEN BYTES THAT THE TRANSCEIVER WILL WAIT BEFORETRANSMITTING THE DATA PACKET.5.2.9 Broadcast AttemptsEEPROM Address: 4EHSize: 1 byteDefault: 04HRange: 01-FFTHE BROADCAST ATTEMPT PARAMETER APPLIES ONLY TO THE BROADCAST MODESFOR ALL FOUR SERIAL PACKET MODES AND SPECIFIES THE NUMBER OF TIMES THAT THE RFWILL BROADCAST EVERY PACKET. THE RECEIVING TRANSCEIVER WILL DISCARD DUPLICATEPACKETS.
Configuring the PKLR2400 Preliminary 25DOC: 504JDSR25.2.10 RF ModeEEPROM Address: 4FHSize: 1 byteDefault: 01HRange: 01 or 0301 = CSMA mode. CSMA mode allows random back off for collision avoidance. The amount ofrandomness is controlled by the byte in 45h in the EEPROM as follows:00 – wait 1 packet time then retry,01 – wait 1 or 2 packet times, then retry03 – wait 1-4 packet times, then retry07 – wait 1-8 packet times, then retry0F – wait 1-16 packet times, then retry*Note: The number of packet times waited is random except in the case of 00.03 = Turbo Mode. If RF Mode Byte is set to 03, then CSMA Turbo mode is enabled. This is useful for aone-to-one connection as it has no back off between errors. In normal CSMA mode, the transceiver will waitone packet time between successful packets. Turbo CSMA mode eliminates the wait time betweensuccessful packets and will transmit packets immediately, one after the other. If the packet is notsuccessfully received then the transceiver will just re-send the packet until a successful receipt isacknowledged.
Configuring the PKLR2400 Preliminary 26DOC: 504JDSR25.3 EEPROM Parameter SummaryEEPROM PARAMETERSBYSERIAL INTERFACE MODESAddress Description AB C DEFG H I4AH Serial Interface Mode 01 01 02 02 03 03 03 04 042FH Transmit Attempts 01-FF 01 01-FF 01 01-FF 01-FF 01-FF 01-FF 0131H Receive Mode 03 03 03 03 01 02 03 03 0332H Range Refresh NA NA NA NA 01-FF 01-FF NA NA NA3EH End Char Definition NA NA 00-FF 00-FF NA NA NA NA NA43H Fixed Pkt Length-HB 01-07 01-07 NA NA NA NA NA 01-07 01-0744H Fixed Pkt Length-LB 00-FF 00-FF NA NA NA NA NA 00-FF 00-FF4BH Dest Address Control 00 01 00 01 NA NA NA 00 014DH Interface Timeout Table Table NA NA NA NA NA NA NAMODE DEFINITIONSA. MODE 01 – TRANSPARENT, FIXED LENGTH PACKET, TIMEOUT, ADDRESSEDB. MODE 01 – TRANSPARENT, FIXED LENGTH PACKET, TIMEOUT, BROADCASTC. Mode 02 – Transparent, End Character, AddressedD. Mode 02 – Transparent, End Character, BroadcastE. Mode 03 – API, Unicast/BroadcastF. Mode 03 – API, Unicast OnlyG. Mode 03 – Packet, PromiscuousH. Mode 04 – Transparent, Fixed Length, No Timeout, AddressedI. Mode 04 – Transparent, Fixed Length, No Timeout, Broadcast
API Command Set Preliminary 27DOC: 504JDSR26. API Command Set (Serial Interface Mode 03 Only)The basic command set consists of several commands from the Host and Transceiver. Thecommand set can be used ONLY when the transceiver is in Serial Interface API Mode 03 determined byEEPROM address 4AH (See Section 3.7, Configuring the PKLR2400). The command set is designed asfollows:Command Length Data ChecksumCommand – 1 Byte. This is the actual command from the appropriate processor.Length – 2 Bytes. This is the total size of the remaining data for this command. The length field isin little endian format.(i.e. low byte/high byte). This length does not include the checksum.Data – N Bytes. The actual data associated with the command or sub-command.Checksum – 1 Byte. The checksum is a byte-by-byte, bitwise “EXCLUSIVE OR” of theCOMMAND, LENGTH, and DATA block.6.1 System Command Set SummaryThe System Commands allow the user to initialize the system and perform general system analysiswhen operating in API Serial Interface Mode 03.Name Command Length Data ChecksumReset* AAH 0H 0H AAHControl* 86H 1 to 5 (depends on sub-command) As Required As RequiredDiagnostic Result* 87H As Required As Required As RequiredStandby* 88H No yet supportedReset EEPROM* 89H 0H 0H 89HStatus Request* 8AH 1H 0-reset error counter1-don’t do anything8AHStatus Reply* 8BH 14H-116H See 6.1.7Update EEPROMChecksum*8CH 0H 0H 8CHCheck EEPROMChecksum*8DH 0H 0H 8DHEEPROM ChecksumStatus*8EH 1H 0-Checksum invalid1-Checksum valid8EHAcknowledge* As Required 0H As Required6.1.1 Reset*This command is issued from the Host processor to the Transceiver. This command provides asoftware reset to the PKLR2400 Transceiver initializing the code at the same location as a hardware reset.This must be followed by an RF Enable.Example: AA|00|00|AA (There are no Data bytes for this command)
API Command Set Preliminary 28DOC: 504JDSR26.1.2 Control*The Host processor will issue this command to Write and Read EEPROM as well as for NOP.Sub-command (Counts as one byte in the Length) Description2H* Read EEPROM. Additional data: first two bytesspecify starting address. Second two bytes specifyending address.8H* NOP.9H* Write EEPROM. Additional data: first two bytesspecify starting address. Second two bytes specifyending address. Remaining bytes specify data to bewritten. (Range 00 to 7F)Data Frame:86H Length Low 0H Sub-command Data ChecksumExample: 86|05|00|02|04|00|09|00|8C (There are no Data bytes for this command)Note: Any additional sub-commands are reserved by the system and if used may cause system operationproblems.Note: Following and EEPROM Write* Command, the user should invoke the Update EEPROMChecksum* command. If this command is not executed, the checksum will not be updated with the newlywritten data. Pin 37 (WR_ENA) must be low for this command to execute successfully.Note: Following the EEPROM Write* Command, the user MUST invoke the Reset* command before anyEEPROM changes will become active. Pin 37 (WR_ENA) must be high for this command to executesuccessfully.6.1.3 Diagnostic result*This command will be sent by the Transceiver to the OEM Host in response to a Control command.Sub result (Counts as one byte in the Length) Description2H* Read EEPROM. Additional data: first two bytesspecify starting address. Second two bytes specifyending address.8H* NOP. Returns 6 bytes (87 02 00 08 00 8D)9H* Write EEPROM status.0 - Write successful. 1- Write failed.Data Frame:87H Length Low Length High Sub-result Data Checksum
API Command Set Preliminary 29DOC: 504JDSR26.1.4 Reset EEPROM*This command is sent by the OEM Host to the Transceiver, the result of which sets the variouslocations/parameters in the EEPROM to their default values. The execution of this command does NOTaffect the IEEE Address and Operation Mode parameters in the EEPROM. This command returns a genericpositive acknowledgment.Example: 89|00|00|89 (The are no Data bytes for this command)6.1.5 Status Request*This command is sent by the OEM Host to the Transceiver to find out the various statisticsassociated with the RF Data Link Layer. The Transceiver sends back the values of the variousparameters/statistics as part of the Status Reply command. 1 byte of data is supplied along with thecommand that determines whether the Transceiver resets the various Error Counters or not.Example: 8A|01|00|01|8A6.1.6 Status Reply*This command will be sent by the Transceiver to the OEM Host in response to a Status Requestcommand. All the different parameters pertain to the data link layer and are cumulative totals. Once thiscommand has been sent back to the OEM Product, depending on whether the OEM Product desired an errorcounter variable reset, the reset operation is carried out. The different statistics and their sizes are shownbelow:Name Type Description SizeTransceiverTimeTime Counter Incremented by 1 every 250ms. Initialized to 0at power on or reset.Unsigned Byte – 3bytes, Low BytefirstTx Failures Error Counter Number of times the Transceiver was not ableto deliver a data frame to the destinationUnsigned Long - 4bytesTx Retries Error Counter Number of times the Transceiver had to retrybefore delivering a data frame to thedestinationUnsigned Long - 4bytesRx Failures Error Counter Number of times the Transceiver had to throwaway a received data frame because of badCRC/checksumUnsigned Long - 4bytesRx Retries Error Counter Number of times data frames had to beretransmitted before a valid data frame wasreceivedUnsigned Long - 4bytesNum ActiveTransceiversData Counter Number of Clients registered to aServer. If the Transceiver under considerationis a Client, just return 0Unsigned Byte - 1ByteList ofRegisteredTransceiversIdentity A list of 6 byte IEEE Addresses of all thetransceiver devices + 3 byte time stamp + 3byte packet count. Time stamp and packetcounter are reset at power on or RESET.12 bytes * NumReg Clients
API Command Set Preliminary 30DOC: 504JDSR2Status Reply ExampleName Type 0 Active Transceivers 2 Active TransceiversTransceiver Time Time Counter 1 Byte – TL1 Byte – TM1 Byte – TH1 Byte – TL1 Byte – TM1 Byte – THTx Failures Error Counter 4 Bytes 4 BytesTx Retries Error Counter 4 Bytes 4 BytesRx Failures Error Counter 4 Bytes 4 BytesRx Retries Error Counter 4 Bytes 4 BytesNum Active Transceivers Data Counter 0 2List of RegisteredTransceiversIdentity 6 bytes IEEE Address3 bytes time stamp3 bytes packet count6 bytes IEEE Address3 bytes time stamp3 bytes packet countChecksum Actual ActualData Frame:8BH 17H 00H Data Checksum6.1.7 Update EEPROM Checksum*This command is sent by the Host to the AeroComm module to tell it to recalculate the checksum.The Host CPU typically does this after it has completed writing data to the EEPROM on the AeroCommmodule. The response to this command is an acknowledge.Example: 8C|00|00|8C (There are no Data bytes for this command)6.1.8 Check EEPROM Checksum*This command is sent by the Host CPU to the AeroComm module to validate the EEPROMchecksum. This is typically done after bringing up the AeroComm module out of reset. The AeroCommmodule reports either a good or a bad checksum, by sending back a response called EEPROM ChecksumStatusExample: 8D|00|00|8D (There are no Data bytes for this command)6.1.9 EEPROM Checksum Status*This command will be sent by the Transceiver to the OEM Host in response to a Check EEPROMChecksum command. The data portion of the command indicates whether the checksum is good or bad,based on which the Host CPU takes the appropriate action.6.1.10 Acknowledge*Some commands in the above set have an implied positive response. The generic positiveresponse is defined as the command sequence just received retransmitted back with a zero length.
API Command Set Preliminary 31DOC: 504JDSR26.2 Transceiver Command Set SummaryThe Transceiver Commands allow the user to control the flow of data into and out of the transceiver as wellas initialization of the transceiver in API Serial Interface Mode 03.Name Command Length Data ChecksumRF enable* 80H 0H 0H 80HSend Data* 81H 1 to 7f0h (includes 802.3 Header) As required As RequiredSend Data Complete* 82H 1H 0 or 1 (see 5.1.4) As RequiredReceived Data* 83H 1 to 7f0h (includes 802.3 Header) As Required As RequiredIn range* 84H 06H IEEE address ofServerAs RequiredOut of Range* 85H 0H 0H 85H6.2.1 RF enable*This command is issued from the Host processor to the Transceiver. The Transceiver must havethis command issued to it prior to any RF data transfers. This is a command with no data. Typically, thiscommand is issued to the Transceiver just after it has been brought out of reset. This enables the RF portionof the Transceiver and turns the transmitter/receiver ON. This command requires an acknowledge.NOTE: ENSURE THAT ONLY ONE RF ENABLE COMMAND IS ISSUED FOLLOWING RESET.6.2.2 Send data*This command is issued by the Host to the Transceiver to send a data frame. The data frame hereis the actual frame that the transport/network protocol wants to send out. The data portion will be deliveredto the appropriate RF device. Broadcast frames will be delivered to all registered Clients without a RF datalink ACK. Broadcast frames are not required to reach all destinations. They are typically sent to everyoneat once.Data Frame:81H Length Low Length High Data ChecksumDestination Address Source Address DataMS Byte…LS Byte MS Byte…LS ByteNote: The Data must include header information as follows:(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 forEEPROM locationNote: The Length must include the IEEE 802.3 Header
API Command Set Preliminary 32DOC: 504JDSR26.2.3 Send data complete*The Transceiver will issue this command upon completion of the data transmission process, asindicated by a RF-layer Acknowledgment from the destination RF-device. An additional byte of dataindicates a success or a failure code. This command must be returned for every send data command unlessthe device power fails.Command: 82HLength: 01Data: 0 - indicates success. 1 - Can’t send packet.Checksum: As requiredData Frame:82H 01H 00H Data Checksum6.2.4 Received data*The Transceiver will issue this command upon reception of data from the RF link. The informationin the data frame is the received data.Data Frame:83h Length Low Length High Data ChecksumDestination Address Source Address DataMS Byte…LS Byte MS Byte…LS Byte6.2.5 In range*The Client will issue this command upon detecting that it is in range of a Server. This command isonly valid after reset or after an out of range command has been issued. This command should have somehysterisis so that the Host processor isn’t flooded with these commands in a fringe coverage area. Thestate of the RF link should be updated with the frequency specified in the Protocol EEPROM Parameters,Chapter 7.2, to provide the needed hysterisis. This command includes the Server IEEE802 Address.Data Frame:84H 06H 00H Data ChecksumServer IEEE AddressMS Byte…LS ByteNote: This is only valid from the viewpoint of Client.
API Command Set Preliminary 33DOC: 504JDSR26.2.6 Out of range*The Transceiver will issue this command upon detecting that it is out of range of a Server. Thiscommand is only valid after reset or after an in range command has been issued to the Host processor. Thiscommand should have some hysterisis so that the Host processor isn’t flooded with these commands in afringe coverage area. The state of the RF link should be updated with the frequency specified in theconfiguration command to provide the needed hysterisis.Note: This is only valid from the viewpoint of a Client.6.3 Initializing the PKLR2400 TransceiverFollowing is an example of the initialization sequence for both the Clients and Servers followingAeroComm or customer configuration of the EEPROM configuration parameters. This occurs only in theAPI Serial Interface Mode 03. Client Transceiver Server TransceiverApply PowerWait for CTS logic low (if 5V)Host issues RF enable commandHost awaits AcknowledgeHost reads EEPROM for IEEEsource addressAwait Server Beacon with IEEEServer addressIssue Server beacon every 5ms –500ms with IEEE Server addressClient issues In range commandto Host with Server addressServer can now transmit orreceive dataClient can now transmit or receivedata
Mechanical Overview Preliminary 34DOC: 504JDSR27. Mechanical OverviewThe 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-1J2 – High frequency MMCX style antenna connector (Telegartner P/N J0134A0081) mateswith any manufacturer MMCX plug(4) Mounting holes are 0.100” diameter.Figure 1. Mechanical Overview of PKLR2400
Ordering Information Preliminary 35DOC: 504JDSR28. Ordering Information8.1 Product Part NumbersPKLR2400S-100, PKLR2400S with 100mW output power, interface data rates to 882Kbps, MMCX antennaconnector8.2 Developer Kit Part NumbersSDK-PKLR2400S-100, Includes (2) PKLR2400S-100 transceivers, (2) RS232 Serial Adapter Boards, (2) 6Vdcunregulated power supplies, (2) Serial cables, (2) WXE2400 dipole antennas with 2” pigtail and MMCXconnector, configuration/testing software, Integration engineering support

Navigation menu