Laird Connectivity PKLR2400-200 Frequency Hopping Spread Spectrum Transceiver Modu User Manual Aerocomm OEM Radio

AeroComm Corporation Frequency Hopping Spread Spectrum Transceiver Modu Aerocomm OEM Radio

UserManual.wiki >

Laird Connectivity >

PKLR2400-200 User Manual >

Contents

1. revised users manual please remove the other
2. users manual

users manual

AC5124AC5124AC5124AC51242.4 GHz OEM TRANSCEIVER2.4 GHz OEM TRANSCEIVER2.4 GHz OEM TRANSCEIVER2.4 GHz OEM TRANSCEIVERSpecifications Subject to ChangeSpecifications Subject to ChangeSpecifications Subject to ChangeSpecifications Subject to ChangeUser’s ManualUser’s ManualUser’s ManualUser’s ManualVersion 4.4Version 4.4Version 4.4Version 4.410981 EICHER DRIVE10981 EICHER DRIVE10981 EICHER DRIVE10981 EICHER DRIVELENEXA, KS 66219LENEXA, KS 66219LENEXA, KS 66219LENEXA, KS 66219(800) 492-2320(800) 492-2320(800) 492-2320(800) 492-2320www.aerocomm.comwww.aerocomm.comwww.aerocomm.comwww.aerocomm.comwireless@aerocomm.comwireless@aerocomm.comwireless@aerocomm.comwireless@aerocomm.com

11/24/03 2DOCUMENT INFORMATIONDOCUMENT INFORMATIONDOCUMENT INFORMATIONDOCUMENT INFORMATIONCopyrightCopyrightCopyrightCopyrightInformationInformationInformationInformationCopyright © 2000 AEROCOMM, Inc. All rights reserved.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 otherwisedistributing any part of this product without the prior consent of an authorizedrepresentative of AEROCOMM, Inc. is prohibited.All brands and product names in this publication are registeredtrademarks or trademarks of their respective holders.This material is preliminaryThis material is preliminaryThis material is preliminaryThis material is preliminaryInformation furnished by AEROCOMM in this specification is believed to be accurate. Devices soldby AEROCOMM are covered by the warranty and patent indemnification provisions appearing in itsTerms of Sale only. AEROCOMM makes no warranty, express, statutory, and implied or bydescription, regarding the information set forth herein. AEROCOMM reserves the right to changespecifications at any time and without notice.AEROCOMM’s products are intended for use in normal commercial applications. Applicationsrequiring extended temperature range or unusual environmental requirements such as military,medical life-support or life-sustaining equipment are specifically not recommended withoutadditional testing for such application.

11/24/03 3DOCUMENT INFORMATIONDOCUMENT INFORMATIONDOCUMENT INFORMATIONDOCUMENT INFORMATIONRevisionRevisionRevisionRevision DescriptionDescriptionDescriptionDescriptionVersion 3.6 Remove SDK developer kit information – 6/6/00Re-arrange the layout of the specification to ease useCorrect Channels from 75 to 77 and provide range in Hex, Section 5.1.3Version 3.7 6/28/00 – Made data rates uniform at 882 KbpsReformat I/O table to view additional line descriptionsVersion 3.8 8/18/00 – Changed Input Voltage tolerance from 5% to 2%Changed temperature from 0 – 60 °C to 0 – 70 °CChanged Baud Low Default from F7 to F1Updated Section 6 – API Command Set with examples & correctionsAdded pin notations on Figure 1 - Mechanical Overview of AC5124CVersion 3.9 9/25/00 – Corrected DTR pin number from 33 to 34, Pin 33 is NCChanged Pin 24 from Reserved to NCRemove Note from the CTS timing diagram in Sections 3.3.1 & 4.6Changed description for Diagnostic Result command in Section 6.1.3Version 4.2 10/25/01 - Changed PKLR2400S part number to AC5124CAdded AC5124C-200 informationAdded Section 3.3, Electrical SpecificationsAdded RSSI calibration steps in Section 3.2.1Added Section 4.6, Addressed & Broadcast CommunicationAdded Section 4.7, HandshakingUpdated Table 6, EEPROM Parameters to include new parametersUpdated Section 5, API Command Set to include command examplesUpdated Section 6, Configuring the AC5124C to include new parameter definitionsAdded Section 7, Initializing the AC5124C TransceiverUpdated Section 8, Mechanical Overview to include new drawingsVersion 4.3 3/25/01 – Changed Interface Timeout values in Table 6, EEPROM ParametersUpdated RF Mode 1 (EEPROM Address 4Ch) to include new definition for Bit 7Added Section 6.1.15.5, Mixed ModeUpdated Approved Antenna ListVersion 4.4 11/24/03 – Updated all references to operating temperature from 0°C to 60°C to -40°C to80°C. All AC5124 products are industrial temperature. Added AT Commands forreading and writing the EEPROM. Updated RSSI plot for new receiver IC.

11/24/03 4FCC INFORMATIONFCC INFORMATIONFCC INFORMATIONFCC INFORMATIONAgency Approval OverviewAgency Approval OverviewAgency Approval OverviewAgency Approval OverviewPart NumberPart NumberPart NumberPart Number US/FCCUS/FCCUS/FCCUS/FCC CAN/ICCAN/ICCAN/ICCAN/IC EUR/EN**EUR/EN**EUR/EN**EUR/EN** PortablePortablePortablePortable MobileMobileMobileMobileAC5124-10 X X X X XAC5124-200 X X X-20cm** See RF Exposure warning on page 6** Does not include France and SpainNote: The product approvals above are with antennas specified on page 5.Agency Identification NumbersAgency Identification NumbersAgency Identification NumbersAgency Identification NumbersPart NumberPart NumberPart NumberPart Number US/FCCUS/FCCUS/FCCUS/FCC CAN/ICCAN/ICCAN/ICCAN/IC EUR/ENEUR/ENEUR/ENEUR/ENAC5124-10 KQL-PKLR2400 CAN2268391158A XAC5124-200 KQL-PKLR2400-200 CAN2268391180AFCC NoticeFCC NoticeFCC NoticeFCC NoticeAntenna WarningAntenna WarningAntenna WarningAntenna Warning WARNING: WARNING: WARNING: WARNING: This device complies with Part 15 of the FCC Rules. Operation is subject to thefollowing two conditions: (1) This device may not cause harmful interferenceand (2) This device must accept any interference received, includinginterference that may cause undesired operation. WARNING: WARNING: WARNING: WARNING: This device has been tested with an MMCX connector with the antennas listedbelow. When integrated in the OEMs product, these fixed antennas requireinstallation preventing end-users from replacing them with non-approvedantennas. Any antenna not in the following table must be tested to comply withFCC Section 15.203 for unique antenna connectors and Section 15.247 foremissions.

11/24/03 5FCC INFORMATIONFCC INFORMATIONFCC INFORMATIONFCC INFORMATIONApproved Antenna ListApproved Antenna ListApproved Antenna ListApproved Antenna ListItemItemItemItem Part NumberPart NumberPart NumberPart Number ManufacturerManufacturerManufacturerManufacturer Gain (dBi)Gain (dBi)Gain (dBi)Gain (dBi)AC5124-10AC5124-10AC5124-10AC5124-10AC5124-10AAC5124-10AAC5124-10AAC5124-10AAC5124-200AC5124-200AC5124-200AC5124-200AC5124-200AAC5124-200AAC5124-200AAC5124-200A1 WCP-2400-MMCX Centurion 2 PM M 2 WCR-2400-SMRP Centurion 2 PM 3 MFB24008RPN Maxrad 8 PM 4 BMMG24000MSMARP12’ Maxrad 1 PM 5 BMMG24005MSMARP12’ Maxrad 5 PM 6 MP24013TMSMARP12 Maxrad 13 M 7 MUF24005M174MSMARP12 Maxrad 5 PM 8 MC2400 Maxrad 2.5 M 9 NZH2400-MMCX (External) AeroComm 1 PM M 10 NZH2400-I (Integrated) AeroComm 1 PM M11 S131CL-5-RMM-2450S Nearson 2 M 12 S181FL-5-RMM-2450S Nearson 2 PM M 13 S191FL-5-RMM-2450S Nearson 3 PM M 14 S151FL-5-RMM-2450S Nearson 5 PM M15 MLPV1700 Maxrad 4 PM MP=Portable, M=MobileP=Portable, M=MobileP=Portable, M=MobileP=Portable, M=Mobile

11/24/03 6FCC INFORMATIONFCC INFORMATIONFCC INFORMATIONFCC INFORMATIONLabeling RequirementsLabeling RequirementsLabeling RequirementsLabeling RequirementsRF Exposure AC5124-10RF Exposure AC5124-10RF Exposure AC5124-10RF Exposure AC5124-10RF Exposure AC5124-200RF Exposure AC5124-200RF Exposure AC5124-200RF Exposure AC5124-200 WARNING: WARNING: WARNING: WARNING: The Original Equipment Manufacturer (OEM) must ensure that FCC labelingrequirements are met. This includes a clearly visible label on the outside of theOEM enclosure specifying the appropriate AeroComm FCC identifier for thisproduct as well as the FCC Notice above. The FCC identifiers are listed abovein the Agency Identifier Numbers section. WARNING: WARNING: WARNING: WARNING: This equipment has been approved for portable applications where theequipment can be used in direct contact with the human body. Excessive RFexposure should be avoided.The preceding statement must be included as a CAUTION statement inmanuals for products operating with Antennas 3, 4, 5, 6, 7, 14 and 15 in theprevious table to alert users on FCC RF Exposure compliance. WARNING: WARNING: WARNING: WARNING: To satisfy FCC RF exposure requirements for mobile and base stationtransmitting devices, a separation distance of 20cm or more should bemaintained between the antenna of this device and persons during operation.To ensure compliance, operations at closer than this distance is notrecommended.The preceding statement must be included as a CAUTION statement inmanuals for OEM products to alert users on FCC RF Exposure compliance.

11/24/03 7TABLE OF CONTENTSTABLE OF CONTENTSTABLE OF CONTENTSTABLE OF CONTENTSTABLES......................................................................................................................................................... 81. OVERVIEW........................................................................................................................................ 102. AC5124 SPECIFICATIONS.............................................................................................................. 113. THEORY OF OPERATION.............................................................................................................. 121.1 DEFINITIONS .................................................................................................................................. 121.2 INTERFACE SIGNAL DEFINITIONS ................................................................................................... 131.2.1 Received Signal Strength Indicator (RSSI) ........................................................................... 141.1.2 In Range (IN_RANGE).......................................................................................................... 151.1.3 Baud Rate Selector (BDSEL) ................................................................................................ 151.1.4 Microprocessor Reset (µP_RESET)...................................................................................... 151.1.5 EEPROM Write Enable (WR_ENA)...................................................................................... 151.3 ELECTRICAL SPECIFICATIONS......................................................................................................... 164. SERIAL INTERFACE MODES........................................................................................................174.1 SERIAL INTERFACE MODE 01 – TRANSPARENT, FIXED PACKET LENGTH, WITH TIMEOUT ............. 174.2 SERIAL INTERFACE MODE 02 – TRANSPARENT, END CHARACTER ................................................ 174.3 SERIAL INTERFACE MODE 03 – API .............................................................................................. 184.4 SERIAL INTERFACE MODE 04 – TRANSPARENT, FIXED PACKET LENGTH, NO TIMEOUT ................ 184.5 SERIAL INTERFACE BUFFER ........................................................................................................... 184.6 ADDRESSED & BROADCAST COMMUNICATION.............................................................................. 184.6.1 Addressed Mode.................................................................................................................... 194.6.2 Broadcast Mode.................................................................................................................... 204.7 HANDSHAKING............................................................................................................................... 204.7.1 CTS Handshaking ................................................................................................................. 204.7.2 RTS Handshaking.................................................................................................................. 214.7.3 Modem Handshaking ............................................................................................................ 215. API COMMAND SET........................................................................................................................ 225.1 SYSTEM COMMAND SET ................................................................................................................ 235.1.1 Reset...................................................................................................................................... 235.1.2 Control.................................................................................................................................. 245.1.3 Diagnostic Result.................................................................................................................. 245.1.4 Standby.................................................................................................................................. 255.1.5 Status Request....................................................................................................................... 255.1.6 Status Reply........................................................................................................................... 255.1.7 Update EEPROM Checksum................................................................................................. 265.1.8 Check EEPROM Checksum .................................................................................................. 265.1.9 EEPROM Checksum Status................................................................................................... 265.1.10 Acknowledge ......................................................................................................................... 275.2 TRANSCEIVER COMMAND SET....................................................................................................... 275.2.1 RF Enable ............................................................................................................................. 275.2.2 Send Data.............................................................................................................................. 285.2.3 Send Data Complete ............................................................................................................. 285.2.4 Received Data....................................................................................................................... 295.2.5 In Range................................................................................................................................ 295.2.6 Out of Range......................................................................................................................... 296. AT COMMAND SET......................................................................................................................... 306.1 IRAM DEFINED ............................................................................................................................. 30

11/24/03 86.2 COMMAND INSTRUCTIONS/RESPONSES.......................................................................................... 306.2.1 Enter Command Mode.......................................................................................................... 316.2.2 Exit Command Mode............................................................................................................. 316.2.3 Power-on Reset Command.................................................................................................... 326.2.4 Read IRAM Byte.................................................................................................................... 326.2.5 Write IRAM Byte................................................................................................................... 336.2.6 Read EEPROM Byte ............................................................................................................. 346.2.7 Write EEPROM Byte............................................................................................................. 357. CONFIGURING THE AC5124 ......................................................................................................... 367.1.1 Software Version Number ..................................................................................................... 397.1.2 IEEE MAC Address............................................................................................................... 397.1.3 Channel................................................................................................................................. 407.1.4 Transmit Attempts ................................................................................................................. 407.1.5 Receive Mode........................................................................................................................ 407.1.6 Range Refresh....................................................................................................................... 417.1.7 Server/Client Mode ............................................................................................................... 417.1.8 System ID .............................................................................................................................. 427.1.9 End Character....................................................................................................................... 427.1.10 Baud High (BH) and Baud Low (BL).................................................................................... 437.1.11 Fixed Packet Length High & Low......................................................................................... 437.1.12 Random Back-Off.................................................................................................................. 447.1.13 Serial Interface Mode............................................................................................................ 447.1.14 Transmit Mode...................................................................................................................... 477.1.15 RF Mode 1 ............................................................................................................................ 477.1.16 Read Switches ....................................................................................................................... 487.1.17 Interface Timeout.................................................................................................................. 507.1.18 Broadcast Attempts ............................................................................................................... 507.1.19 RF Mode ............................................................................................................................... 507.1.20 Destination IEEE MAC Address ........................................................................................... 527.1.21 Sleep Time............................................................................................................................. 527.1.22 Wait Time.............................................................................................................................. 528. INITIALIZING THE AC5124 TRANSCEIVER ............................................................................. 538.1 TRANSPARENT MODE INITIALIZATION ........................................................................................... 538.2 API MODE INITIALIZATION ............................................................................................................ 539. MECHANICAL OVERVIEW...........................................................................................................5510. ORDERING INFORMATION...................................................................................................... 5710.1 PRODUCT PART NUMBERS............................................................................................................. 5710.2 DEVELOPER KIT PART NUMBERS................................................................................................... 57FiguresFiguresFiguresFiguresFigure 1 - RSSI Voltage vs. Received Signal Strength.......................................................................... 14Figure 2 - API Mode Initialization..............................................................................................................54Figure 3 – AC5124 with MMCX.................................................................................................................55Figure 4 – AC5124 with Integral Antenna................................................................................................ 56TablesTablesTablesTablesTable 1 - Interface Signal Definitions ....................................................................................................... 13Table 2 - DC Input Voltage Characteristics............................................................................................. 16Table 3 - DC Output Voltage Characteristics.......................................................................................... 16Table 4 - System Command Set ..............................................................................................................23

11/24/03 9Table 5 - Transceiver Command Set....................................................................................................... 27Table 6 - EEPROM Parameters ................................................................................................................37Table 7 - BH/BL Selections For Common Baud Rates .........................................................................43

AC5124-10 SpecificationsAC5124-10 SpecificationsAC5124-10 SpecificationsAC5124-10 Specifications 11/24/03 101.1.1.1. OverviewOverviewOverviewOverviewThis document contains information about the hardware and software interface between anAeroComm AC5124 transceiver and an OEM Host. Information includes the theory of operation,system issues, 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 minimum number ofactual hardware pins connecting the transceiver and the OEM Host. The transceiver is controlled by aTemic TS87C51U2 microcontroller providing program storage. A separate EEPROM provides userconfigurable parameter storage.AC5124 transceivers operate in a Point-to-Point or Point-to-Multipoint, Client/Server architecture. Onetransceiver is configured as a Server and the others are configured as Clients. Data can be transmittedfrom Client to Server or Server to Client, but not from Client to Client, or Server to Server.The AC5124 runs a proprietary Carrier Sense Multiple Access (CSMA) protocol. Years ofdevelopment, testing and field operation have proven this protocol to be a stable, reliable and efficientmethod for wireless network communications. Furthermore, the AeroComm protocol is configurable,allowing the OEM to optimize system performance. There are four different Serial Interface Modesprovided by the protocol firmware. These Modes offer significant flexibility to the OEM, allowing themto provide data in many forms including API, End Character and Fixed Packet Length with and withoutTimeouts.

AC5124-10 SpecificationsAC5124-10 SpecificationsAC5124-10 SpecificationsAC5124-10 Specifications 11/24/03 112.2.2.2. AC5124 SpecificationsAC5124 SpecificationsAC5124 SpecificationsAC5124 SpecificationsGENERALGENERALGENERALGENERALBus Interface Serial (TTL Level Asynchronous) through 40 pin miniconnector. AMP P/N 177986-1Serial Interface Data Rate Programmable to 882 Kbps. PC rates to 115.2 KbpsComplianceAC5124-10Certifiable under:US (FCC 15.247); Canada (IC); Europe (EN)AC5124-200 US (FCC 15.247); Canada (IC)Power ConsumptionAll Serial Interface ModesInterface ON/RF OFF (API Mode Only)Sleep Walk (Clients in all Modes Only)Deep Sleep (Servers in API Mode Only)Duty Cycle (TX=Transmit; RX=ReceiveDuty Cycle (TX=Transmit; RX=ReceiveDuty Cycle (TX=Transmit; RX=ReceiveDuty Cycle (TX=Transmit; RX=Receive))))25%TX25%TX25%TX25%TX 50%TX50%TX50%TX50%TX 100%TX100%TX100%TX100%TX 100%RX100%RX100%RX100%RXAC5124-10: 111mA 123mA 158mA 100mAAC5124-200: 185mA 280mA 472mA 110mA45mA typical25mA typical20mA typicalChannels Supports 77 non-interfering channelsSecurity User assigned System ID. Unique IEEE addresses on eachtransceiver.TRANSCEIVERTRANSCEIVERTRANSCEIVERTRANSCEIVERFrequency Band 2.402 – 2.478 GHzTransceiver Type Frequency Hopping Spread SpectrumOutput PowerAC5124-10AC5124-20010mW200mWInput Voltage 5V nominal +2%, + 50mV rippleSensitivity -90dBmRF Data Rate 882 KbpsRangeAC5124-10AC5124-200Can be extended with directional antennaIndoors up to 300 ft., Outdoors up to 3,000 ft.Indoors up to 500 ft., Outdoors up to 10,000 ft.Synchronization Time Average = 750ms; Maximum = 1.5sENVIRONMENTALENVIRONMENTALENVIRONMENTALENVIRONMENTALTemperature (Operating) -40°C to +80°CTemperature (Storage) -50°C to +85°CHumidity (non-condensing) 10% to 90%PHYSICALPHYSICALPHYSICALPHYSICALDimensions 1.65” x 2.65” x 0.20”Antenna Connector Standard MMCX jackWeight Less than 0.75 ouncesSOFTWARESOFTWARESOFTWARESOFTWAREUser Configurable OptionsHost Interface Data Rate Up to 882 KbpsMaximum bi-directional throughput Up to 170kbpsVariable Packet Length Up to 2 KBytesSerial Interface Modes (3) Transparent and (1) APIDiagnostic Error Counters API ModeUser Programmable Attempts Up to 255

AC5124-10 SpecificationsAC5124-10 SpecificationsAC5124-10 SpecificationsAC5124-10 Specifications 11/24/03 123.3.3.3. Theory of OperationTheory of OperationTheory of OperationTheory of OperationThe AC5124 has a serial interface that allows the OEM Host to send and receive communications toand from the transceiver. All I/O is 5Vdc TTL level signals except for RSSI, which is an analog output.All outputs are weakly pulled logic high (20 kΩ – 50 kΩ) when left unconnected and are driven logichigh at reset.3.13.13.13.1 DDDDEFINITIONSEFINITIONSEFINITIONSEFINITIONSServer Host:Server Host:Server Host:Server Host: The Server Host is the OEM device controlling the Server transceiver.Client Host:Client Host:Client Host:Client Host: The Client Host is the OEM device controlling the Client transceiver.Host:Host:Host:Host: Host refers to both the Server Host and the Client Host.Server Transceiver:Server Transceiver:Server Transceiver:Server Transceiver: The Server transceiver is the “Master” transceiver. It is the hub of allcommunications.Client Transceiver:Client Transceiver:Client Transceiver:Client Transceiver: The Client transceiver is a “Slave” transceiver. It is controlled by it’s ownHost, but is a slave to the Server transceiver.Authentication:Authentication:Authentication:Authentication: The acquisition of a Server IEEE 802.3 address by a Client transceiver and asubsequent issue of an In RangeIn RangeIn RangeIn Range command by the Client transceiver to the Client Host.Unicast Address:Unicast Address:Unicast Address:Unicast Address: A frame that is directed to a single recipient as specified in IEEE 802.3.Broadcast Address:Broadcast Address:Broadcast Address:Broadcast Address: A frame that is directed to multiple recipients as specified in IEEE 802.3.

AC5124-10 SpecificationsAC5124-10 SpecificationsAC5124-10 SpecificationsAC5124-10 Specifications 11/24/03 133.23.23.23.2 IIIINTERFACE NTERFACE NTERFACE NTERFACE SSSSIGNAL IGNAL IGNAL IGNAL DDDDEFINITIONSEFINITIONSEFINITIONSEFINITIONSThe following pinout is for the 40-pin mini-connector, J1 (AMP P/N 177986-1). I/O direction is withregard to the transceiver. All pins not used by the OEM may be left floating.Table Table Table Table 1111 - Interface Signal Definitions - Interface Signal Definitions - Interface Signal Definitions - Interface Signal DefinitionsPinPinPinPin TypeTypeTypeType Signal NameSignal NameSignal NameSignal Name FunctionFunctionFunctionFunction1 GND GND Signal Ground2 I PKTMODE Logic low (Active Low) will force transceiver into “pseudo” Serial InterfaceMode 03 (API). Used for programming the EEPROM. Not recommended forfull API Mode operation. See Section 6, Configuring the AC5124Section 6, Configuring the AC5124Section 6, Configuring the AC5124Section 6, Configuring the AC5124.3 VCC VCC 5V + 2%, ±50 mV ripple4 NC NC No Connect5 VCC VCC 5V + 2%, ±50 mV ripple6 NC NC No Connect7 NC NC No Connect8 NC NC No Connect9 NC NC No Connect10 NC NC No Connect11 O RSSI Received Signal Strength Indicator - Analog output giving relative indicationof received signal strength while in receive mode.12 NC NC No Connect13 NC NC No Connect/Data 714 O TXD Transmitted data out of the transceiver15 O IN_RANGE Logic low when a Client detects a Server with same Channel and System ID.16 I RXD Data input to the transceiver17 I RI_IN Ring Indicator to communicate to modem18 NC NC No Connect19 O RI_OUT Ring Indicator to communicate to computer20 GND GND Ground21 GND GND Ground22 I DCD_IN Data Carrier Detect to communicate to modem23 O CTS Clear to Send – Logic Low (Active Low) when the transceiver is ready toaccept data for transmission. See Section 4.7.1, CTS HandshakingSection 4.7.1, CTS HandshakingSection 4.7.1, CTS HandshakingSection 4.7.1, CTS Handshaking.24 NC NC No Connect25 Reserved Reserved Reserved, must be left floating and not connected to logic high or low.26 I BDSEL Baud Select – Logic low (Active Low) will force the transceiver into a knownserial interface baud rate (9600 8-N-1)27 I RTS Request to Send – Logic low (Active Low) when enabled and Host is readyto receive data from the transceiver. See Section 4.7.2, RTS HandshakingSection 4.7.2, RTS HandshakingSection 4.7.2, RTS HandshakingSection 4.7.2, RTS Handshaking.28 NC NC No Connect29 NC NC No Connect30 NC NC No Connect31 NC NC No Connect32 O DSR Data Set Ready33 NC NC No Connect34 I DTR Data Terminal Ready35 NC NC No Connect36 O DCD_OUT Data Carrier Detect to communicate to computer37 I WR_ENA EEPROM Write Enable – Logic low will enable writes to the EEPROM.The transceiver should NOTNOTNOTNOT be write-enabled during the initial power upor upon a hardware reset to ensure the integrity of the EEPROM data.38 I µP _RESET Microprocessor Reset - Logic high for a minimum of 2ms will reset thetransceiver. If a reset is performed after power has been applied and is stable,the reset time will decrease significantly. All other times, Pin 38 should belogic low. If Pin 38 is not connected, the microprocessor will hold Pin 38 logiclow.39 VCC VCC 5V + 2%, ±50 mV ripple40 GND GND Signal GroundI = Input to the transceiverO = Output from the transceiver

AC5124-10 SpecificationsAC5124-10 SpecificationsAC5124-10 SpecificationsAC5124-10 Specifications 11/24/03 143.2.13.2.13.2.13.2.1 Received Signal Strength Indicator (RSSI)Received Signal Strength Indicator (RSSI)Received Signal Strength Indicator (RSSI)Received Signal Strength Indicator (RSSI)The Received Signal Strength Indicator is used by the Host to determine the instantaneous signalstrength at the receiver. The Host must calibrate RSSI without a signal being presented to the receiver.RSSI is invalid when a transceiver is transmitting. Calibration is accomplished by following the stepslisted below to find a minimum and maximum voltage value.1) Power up only one transceiver in the coverage area.2) Measure the RSSI signal to obtain the minimum value with no other signal present.3) Power up a transceiver that is the opposite type of the one measured in Step 2 (i.e. if thetransceiver was a Client, power up a Server, otherwise power up a Client). Make sure thetwo transceivers are in close proximity and measure RSSI to obtain a maximum value atfull signal strength.Figure 1 shows approximate RSSI performance. There are two versions of receivers used by theAC5124. As of January of 2003 forward, only the New Revision receiver will be shipped. The RSSI pinof the old revision requires the Host to provide a 27kΩ pull-down to ground. No pull-down should beused with the new revision.Figure Figure Figure Figure 1111 - RSSI Voltage vs. Received Signal Strength - RSSI Voltage vs. Received Signal Strength - RSSI Voltage vs. Received Signal Strength - RSSI Voltage vs. Received Signal Strength0123456-20-25-30-35-40-45-50-55-60-65-70-75-80-85-90-95Input Power (dBm)Voltage (V)New Revision Old Revision

AC5124-10 SpecificationsAC5124-10 SpecificationsAC5124-10 SpecificationsAC5124-10 Specifications 11/24/03 153.2.23.2.23.2.23.2.2 In Range (IN_RANGE)In Range (IN_RANGE)In Range (IN_RANGE)In Range (IN_RANGE)The IN_RANGE pin will be driven logic low when a Client is in range of a Server on the same Channeland System ID. If a Client cannot hear a Server for the amount of time that is programmed in theRange Refresh EEPROM address 32h, the Client drives the IN_RANGE pin logic high and enters asearch mode looking for a Server. As soon as it detects a Server, the IN_RANGE pin will be drivenlogic low.3.2.33.2.33.2.33.2.3 Baud Rate Selector (BDSEL)Baud Rate Selector (BDSEL)Baud Rate Selector (BDSEL)Baud Rate Selector (BDSEL)The Baud Rate Selector (BDSEL) pin provides the OEM a default method of communicating with atransceiver in the event the EEPROM baud rate parameters become corrupted. If Pin 26 is logic highor not connected, the baud rate will default to that specified in EEPROM. If Pin 26 is logic low atRESET, the baud rate will default to 9600 baud.3.2.43.2.43.2.43.2.4 Microprocessor Reset (µP_RESET) Microprocessor Reset (µP_RESET) Microprocessor Reset (µP_RESET) Microprocessor Reset (µP_RESET)Microprocessor Reset (µP_RESET) is achieved by holding Pin 38 at logic high for a minimum of 2ms.If µP_RESET is performed after power has been applied to a 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 logic low.3.2.53.2.53.2.53.2.5 EEPROM Write Enable (WR_ENA)EEPROM Write Enable (WR_ENA)EEPROM Write Enable (WR_ENA)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. The OEM must ensure a transceiver is NOT write-enabled during initial powerup or during a hardware RESET. Failure to do so may result in corruption of important EEPROM data.

AC5124-10 SpecificationsAC5124-10 SpecificationsAC5124-10 SpecificationsAC5124-10 Specifications 11/24/03 163.33.33.33.3 EEEELECTRICAL LECTRICAL LECTRICAL LECTRICAL SSSSPECIFICATIONSPECIFICATIONSPECIFICATIONSPECIFICATIONSTable Table Table Table 2222 - DC Input Voltage Characteristics - DC Input Voltage Characteristics - DC Input Voltage Characteristics - DC Input Voltage CharacteristicsPinPinPinPin TypeTypeTypeType NameNameNameName High Min.High Min.High Min.High Min. High Max.High Max.High Max.High Max. Low Min.Low Min.Low Min.Low Min. Low Max.Low Max.Low Max.Low Max. UnitUnitUnitUnit2 I PKTMODE 0.2Vcc + 0.9 Vcc + 0.5 -0.5 0.2Vcc - 0.1 V16 I RXD 0.2Vcc + 0.9 Vcc + 0.5 -0.5 0.2Vcc - 0.1 V17 I RI_IN 2 Vcc + 1 -0.5 0.8 V22 I DCD_IN 2 Vcc + 1 -0.5 0.8 V26 I BDSEL 0.2Vcc + 0.9 Vcc + 0.5 -0.5 0.2Vcc - 0.1 V27 I RTS 0.2Vcc + 0.9 Vcc + 0.5 -0.5 0.2Vcc - 0.1 V34 I DTR 2 Vcc + 1 -0.5 0.8 V37 I WR_ENA 0.7Vcc Vcc + 1 -0.3 0.5 V38 I µP_RESET 0.7Vcc Vcc + 0.5 -0.5 0.2Vcc - 0.1 VTable Table Table Table 3333 - DC Output Voltage Characteristics - DC Output Voltage Characteristics - DC Output Voltage Characteristics - DC Output Voltage CharacteristicsPinPinPinPin TypeTypeTypeType NameNameNameName High Min.High Min.High Min.High Min. Low Max.Low Max.Low Max.Low Max. UnitUnitUnitUnit11 O RSSI Analog Analog V14 O TXD Vcc - 1.5 @ -60uA 0.45 @ 1.6mA V15 O IN_RANGE 2.4 @ -4mA 0.45 @ 4mA V19 O RI_OUT 2.4 @ -4mA 0.45 @ 4mA V23 O CTS Vcc - 1.5 @ -60uA 0.45 @ 1.6mA V32 O DSR 2.4 @ -4mA 0.45 @ 4mA V36 O DCD_OUT 2.4 @ -4mA 0.45 @ 4mA V

AC5124-10 SpecificationsAC5124-10 SpecificationsAC5124-10 SpecificationsAC5124-10 Specifications 11/24/03 174.4.4.4. Serial Interface ModesSerial Interface ModesSerial Interface ModesSerial Interface ModesThe AC5124 provides four Serial Interface Modes for interfacing to the Host, each having protocolparameters that can be programmed for maximum system optimization. Serial Interface Modes 01, 02,and 04 are referred to as Transparent Modes, indicating Host protocol is unnecessary for operation inthese modes – much like a serial cable. In addition, the transceiver-to-transceiver protocol for theTransparent Modes is identical, allowing all three modes to coexist in the same network. SerialInterface Mode 03, referred to as API Mode, is not interoperable with the Transparent Modes.4.14.14.14.1 SSSSERIAL ERIAL ERIAL ERIAL IIIINTERFACE NTERFACE NTERFACE NTERFACE MMMMODE ODE ODE ODE 01 – T01 – T01 – T01 – TRANSPARENTRANSPARENTRANSPARENTRANSPARENT, F, F, F, FIXED IXED IXED IXED PPPPACKET ACKET ACKET ACKET LLLLENGTHENGTHENGTHENGTH, , , , WITH WITH WITH WITH TTTTIMEOUTIMEOUTIMEOUTIMEOUTTransparent Mode 01 is the most popular interface mode because it can be used for many serial cablereplacement applications that meet any or all of the following conditions:1) The Host always sends data packets that are the same size, allowing a transceiver totake advantage of the fixed packet length option.2) The Host sends variable-sized data packets, all of which are equal to or smaller than theFixed Packet Length. A transceiver will wait until the Interface Timeout expires or until theFixed Packet Length size is reached. Therefore, if multiple packets and/or portions ofpackets are sent before the Interface Timeout expires, the receiving transceiver Hostmust be able to process the multiple packets and/or portions of packets.Packets will be transmitted over the RF interface when one of the following conditions occurs:1) The number of data bytes received over the serial interface is equal to the Fixed PacketLength specified by the OEM at EEPROM addresses 43h and 44h (43h is the MSB). Themaximum packet size is 07FFh or 2KB.2) A byte gap larger than the Interface Timeout specified by the OEM at EEPROM address4Dh occurs. This can be set to 00h, 40h, 80h, or C0h designating 4ms, 40ms, 300ms,and 2.6s timeouts, respectively.Any packets larger than the Fixed Packet Length will be parsed and sent consecutively by atransceiver. For example, if the Fixed Packet Length is 128 bytes and the Host sends 150 bytes,a transceiver will send 128 bytes and then 22 bytes after the timeout expires, consecutively.4.24.24.24.2 SSSSERIAL ERIAL ERIAL ERIAL IIIINTERFACE NTERFACE NTERFACE NTERFACE MMMMODE ODE ODE ODE 02 – T02 – T02 – T02 – TRANSPARENTRANSPARENTRANSPARENTRANSPARENT, E, E, E, END ND ND ND CCCCHARACTERHARACTERHARACTERHARACTERTransparent Mode 02 is useful for applications where a particular character (such as a carriage return –0Dh) is used to signify the end of each packet. The End Character is specified by the OEM atEEPROM address 3Eh and can be set from 00h to FFh. Packets will be transmitted over the RFinterface when the OEM-defined End Character is received by a transceiver. The maximum packetsize is 07FFh or 2KB, including the End Character. Note that the End Character will be transmitted tothe Host.

AC5124-10 SpecificationsAC5124-10 SpecificationsAC5124-10 SpecificationsAC5124-10 Specifications 11/24/03 184.34.34.34.3 SSSSERIAL ERIAL ERIAL ERIAL IIIINTERFACE NTERFACE NTERFACE NTERFACE MMMMODE ODE ODE ODE 03 – API03 – API03 – API03 – APIAPI Mode is the most complex and detailed mode, where most of the control is given to the Host. Thismode may seem extensive at first glance; however, it follows a specific pattern of commands andresponses similar to an Ethernet protocol. The commands are grouped into two categories, SystemCommands and Transceiver Commands. See Section 5, API Command SetSection 5, API Command SetSection 5, API Command SetSection 5, API Command Set for the full list ofcommands and definitions.4.44.44.44.4 SSSSERIAL ERIAL ERIAL ERIAL IIIINTERFACE NTERFACE NTERFACE NTERFACE MMMMODE ODE ODE ODE 04 – T04 – T04 – T04 – TRANSPARENTRANSPARENTRANSPARENTRANSPARENT, F, F, F, FIXED IXED IXED IXED PPPPACKET ACKET ACKET ACKET LLLLENGTHENGTHENGTHENGTH, N, N, N, NO O O O TTTTIMEOUTIMEOUTIMEOUTIMEOUTIn Transparent Mode 04, packets will be transmitted over the RF interface when the number of databytes received over the serial interface is equal to the Fixed Packet Length specified by the OEM atEEPROM addresses 43h and 44h (43h is the MSB). The maximum packet size is 07FFh or 2KB. Thismode of operation is recommended for applications that meet any of the following conditions:1) The Host always sends data packets that are the same size.2) The Host sends variable-sized data packets, all of which are equal to or smaller than theFixed Packet Length. A transceiver will wait indefinitely until the Fixed Packet Length sizeis reached. Therefore, multiple packets and/or portions of packets will be sent,depending on the timing and size of the packets. As a result, the receiving transceiverHost must be able to process the multiple packets and/or portions of packets.4.54.54.54.5 SSSSERIAL ERIAL ERIAL ERIAL IIIINTERFACE NTERFACE NTERFACE NTERFACE BBBBUFFERUFFERUFFERUFFERThe serial interface buffer provides 8 KBytes of memory segmented into four dynamic regions. In APIMode, only one region is utilized. In all Transparent Modes, a buffer region is used each time a packetrelease condition is met. As an example, in Transparent Mode 02, if 500 Bytes are transmitted,including the specified End Character, 500 Bytes will be stored in the first region and the remaining 7.5KBytes will be dynamically allocated for the next three packets. It is strongly recommended that CTSor upper layer protocol with acknowledgements be used by the OEM when operating in any of theTransparent Modes to prevent lost data. Otherwise, if all four buffers are filled and the Host continues tosend data over the serial interface, the data will be discarded by the transceiver. This condition can beeliminated by using CTS.4.64.64.64.6 AAAADDRESSED DDRESSED DDRESSED DDRESSED & B& B& B& BROADCAST ROADCAST ROADCAST ROADCAST CCCCOMMUNICATIONOMMUNICATIONOMMUNICATIONOMMUNICATIONThe AC5124 supports both Addressed and Broadcast Modes of communication in all Serial InterfaceModes. As necessary, refer to Section 5, API Command SetSection 5, API Command SetSection 5, API Command SetSection 5, API Command Set for API command definitions and SectionSectionSectionSection6, Configuring the AC51246, Configuring the AC51246, Configuring the AC51246, Configuring the AC5124 for EEPROM address definitions.

AC5124-10 SpecificationsAC5124-10 SpecificationsAC5124-10 SpecificationsAC5124-10 Specifications 11/24/03 194.6.14.6.14.6.14.6.1 Addressed ModeAddressed ModeAddressed ModeAddressed Mode4.6.1.14.6.1.14.6.1.14.6.1.1 Transparent Mode OperationTransparent Mode OperationTransparent Mode OperationTransparent Mode OperationAddressed communication in a Transparent Mode is achieved by programming the Transmit Modebyte, located at EEPROM address 4Bh, to a value of 00h. In addition, the 6-byte IEEE destinationaddress must be programmed in the respective transceivers starting at EEPROM address 50h (i.e. theServer IEEE address must be programmed in the Client and the Client IEEE address must beprogrammed in the Server). Auto Destination could also be enabled in the Client transceiver asdescribed in Section 4.6.1.2, Auto DestinationSection 4.6.1.2, Auto DestinationSection 4.6.1.2, Auto DestinationSection 4.6.1.2, Auto Destination.In this configuration, a packet is sent to the destination transceiver until a positive acknowledgement isreceived or until all Transmit Attempts have completed. The number of Transmit Attempts is specifiedat EEPROM address 2Fh and can be programmed with values ranging from 01h to FFh. If a packet isnot received successfully after all attempts have been made, the packet transmission will be aborted.The RF acknowledgements in all Transparent Modes are not sent to the Hosts; therefore, the Host isresponsible for detecting a non-deliverable packet, if necessary. Addressed Mode is recommendedfor all point-to-point (one Server and on Client) applications because a transceiver only sends thepacket as many times as necessary. For example, if a transceiver receives a positiveacknowledgement before all attempts are made, it will ignore the remaining attempts and start sendingthe next packet.4.6.1.24.6.1.24.6.1.24.6.1.2 Auto DestinationAuto DestinationAuto DestinationAuto DestinationThe AC5124 also supports an addressed mode of communication called Auto Destination. AutoDestination is only for Clients operating in one of the Transparent Modes. To configure a Client forAuto Destination, set bit 7 of EEPROM address 4Fh to a value of 1. With Auto Destination enabled, aClient has the ability to detect any Server with the same Channel and System ID. Hence, a Client’sDestination IEEE MAC Address, located at EEPROM address 50h, is not required to be programmedwith the Server’s IEEE address.Auto Destination allows a Client to dynamically route all communications to the Server that is in range,making it useful for mobile or roaming applications where a Client will be interfacing with differentServers from time to time. It is important to note that multiple Servers with the same Channel andSystem ID must not be located in range of one another. Doing so will cause inoperability of thesystem.4.6.1.34.6.1.34.6.1.34.6.1.3 API Mode OperationAPI Mode OperationAPI Mode OperationAPI Mode OperationIn API Mode, the IEEE Source and Destination Address must be included in the data frame of the SendSendSendSendData Data Data Data command. The Host is responsible for constructing the packet before sending it to thetransceiver. Like a transceiver operating in a Transparent Mode, a packet will be sent until a successfulSend Data CompleteSend Data CompleteSend Data CompleteSend Data Complete command is sent to the Host or all Transmit Attempts are completed. If thepacket is not received successfully after all attempts have been made, the Host will be notified by theSend Data CompleteSend Data CompleteSend Data CompleteSend Data Complete command with a failure code of 1. Thus, the acknowledgements in API Mode aresent to the Hosts and can be used to guarantee packet delivery.

AC5124-10 SpecificationsAC5124-10 SpecificationsAC5124-10 SpecificationsAC5124-10 Specifications 11/24/03 204.6.24.6.24.6.24.6.2 Broadcast ModeBroadcast ModeBroadcast ModeBroadcast Mode4.6.2.14.6.2.14.6.2.14.6.2.1 Transparent Mode OperationTransparent Mode OperationTransparent Mode OperationTransparent Mode OperationBroadcast communication in a Transparent Mode is intended for use in a point-to-multipoint network(one Server and many Clients). In this configuration, the Server must be programmed for BroadcastMode by programming the Transmit Mode byte, located at EEPROM address 4Bh, to a value of 01h. Itis recommended that all Clients be programmed in Addressed Mode or Auto Destination Mode toprovide more reliable delivery of data to the Server, resulting in more efficient network communications.Unlike the Transmit Attempts process in Addressed Mode, a packet will be transmitted until allBroadcast Attempts are completed. The number of Broadcast Attempts is specified at EEPROMaddress 4Eh and can be programmed with values ranging from 01h to FFh. If a transceiver receives apacket multiple times without error, only the first error-free packet will be sent to the Host. All others willbe discarded. The OEM should carefully determine the number of Broadcast Attempts by performingextensive testing in their application. If a packet is sent more times than necessary, networkperformance can degrade.4.6.2.24.6.2.24.6.2.24.6.2.2 API Mode OperationAPI Mode OperationAPI Mode OperationAPI Mode OperationSending a broadcast packet is accomplished by constructing the data frame of the Send DataSend DataSend DataSend Datacommand with all six bytes of the IEEE Destination Address set to a value of FFh.Unlike the Transmit Attempts process in Addressed Mode, a packet will be transmitted until allBroadcast Attempts are completed, after which, a successful Send Data CompleteSend Data CompleteSend Data CompleteSend Data Complete command will besent to the Host. The number of Broadcast Attempts is specified at EEPROM address 4Eh and can beprogrammed with values ranging from 01h to FFh. If a transceiver receives a packet multiple timeswithout error, only the first error-free packet will be sent to the Host. All others will be discarded. TheOEM should carefully determine the number of Broadcast Attempts by performing extensive testing intheir application. If a packet is sent more times than necessary, network performance can degrade.4.74.74.74.7 HHHHANDSHAKINGANDSHAKINGANDSHAKINGANDSHAKINGThough handshaking is not required for transceiver operation, it is recommended to achieve optimumsystem performance. Most applications benefit from using Clear To Send (CTS) only, while othersmay also need Request To Send (RTS). In addition, some applications may require full modemhandshaking.4.7.14.7.14.7.14.7.1 CTS HandshakingCTS HandshakingCTS HandshakingCTS HandshakingCTS is used by the transceiver to keep the Host from transmitting data to it. If the Host sends thetransceiver data when CTS is logic high (inactive), the data will be lost. Normally, CTS will go logichigh for a minimum of 40µs following the transmission of a data packet from the Host to thetransceiver. However, if the serial interface buffers on a transceiver become full and the transceivercannot transmit the data, the transceiver will hold CTS logic high until it can free a buffer. For example,this can occur when a transceiver goes out of range. Therefore, it is strongly recommended that theHost use CTS. All serial data must be transmitted LSB first.

AC5124-10 SpecificationsAC5124-10 SpecificationsAC5124-10 SpecificationsAC5124-10 Specifications 11/24/03 214.7.24.7.24.7.24.7.2 RTS HandshakingRTS HandshakingRTS HandshakingRTS HandshakingWhen the RTS bit is enabled by setting bit 3 of the Serial Interface Mode byte at EEPROM address 4Ahto a value of 1, Pin 27 is used by the Host to keep a transceiver from transmitting data to it. When RTSis logic high (inactive), a transceiver cannot send data to the Host. Holding RTS logic high for too longcan congest RF communications. For example, if RTS is held logic high while a transceiver continuesto receive data, eventually the receive buffer will fill. If this occurs, a transceiver will not be able to sendor receive any data until it can free the buffer.4.7.34.7.34.7.34.7.3 Modem HandshakingModem HandshakingModem HandshakingModem HandshakingIn Modem Mode, a transceiver uses all standard RS232 (TTL level) handshaking lines to negotiatecommunications. These lines include TXD, RXD, CTS, RTS, DTR, DSR, DCD_IN, DCD_OUT, RI_IN andRI_OUT.To enable Modem Mode, set bit 6 and bit 3 of EEPROM address 4Ah to a value of 1. Bit 6 will enableall modem lines except RTS. As mentioned in Section 4.7.2, RTS HandshakingSection 4.7.2, RTS HandshakingSection 4.7.2, RTS HandshakingSection 4.7.2, RTS Handshaking, setting bit 3 to a valueof 1 enables RTS. Modem Mode is overkill for most applications and is intended mainly for wirelessmodem applications.4.7.3.14.7.3.14.7.3.14.7.3.1 Radio Connected to DTERadio Connected to DTERadio Connected to DTERadio Connected to DTEWhen a transceiver is connected to a Data Terminal Equipment (DTE) device, like a PC, and fullmodem support is desired, a transceiver will use the following configuration in most applications:DTE (PC)DTE (PC)DTE (PC)DTE (PC) TXD RXD CTS RTS DTR DSR DCD RITransceiverTransceiverTransceiverTransceiver RXD(16)TXD(14)CTS(23)RTS(27)DTR(34)DSR(32)DCD_OUT(36)RI_OUT(19)4.7.3.24.7.3.24.7.3.24.7.3.2 Radio Connected to DCERadio Connected to DCERadio Connected to DCERadio Connected to DCEWhen a transceiver is connected to a Data Communication Equipment (DCE) device, like a modem,and full modem support is desired, a transceiver will use the following configuration in mostapplications:DCE (Modem)DCE (Modem)DCE (Modem)DCE (Modem) TXD RXD CTS RTS DTR DSR DCD RITransceiverTransceiverTransceiverTransceiver RXD(16)TXD(14)RTS(27)CTS(23)DSR(32)DTR(34)DCD_IN(22)RI_IN(17)

AC5124-10 SpecificationsAC5124-10 SpecificationsAC5124-10 SpecificationsAC5124-10 Specifications 11/24/03 225.5.5.5. API Command SetAPI Command SetAPI Command SetAPI Command SetIn API Mode, the Host and transceiver utilize a set of commands to program the EEPROM parametersdefined in Section 6, Configuring the AC5124Section 6, Configuring the AC5124Section 6, Configuring the AC5124Section 6, Configuring the AC5124, as well as control and monitor network communications.As mentioned in Section 4.3, Serial Interface Mode 03 – APISection 4.3, Serial Interface Mode 03 – APISection 4.3, Serial Interface Mode 03 – APISection 4.3, Serial Interface Mode 03 – API, the commands are grouped into twocategories, System Commands and Transceiver Commands. Each group of commands are listed anddefined in this section. It is important to note these commands can only be used when a transceiver isoperating in the API Mode, which is accomplished by programming bits 0 and 1 of EEPROM address4Ah to a value of 1. The command format is defined as follows:Command Length Data ChecksumCommandCommandCommandCommand (1 Byte) – Hex command as shown in Table 4 – System Command SetTable 4 – System Command SetTable 4 – System Command SetTable 4 – System Command Set and TableTableTableTable5 – Transceiver Command Set5 – Transceiver Command Set5 – Transceiver Command Set5 – Transceiver Command Set.LengthLengthLengthLength (2 Bytes) – This is the total size of the remaining data for this command. The lengthfield is in little endian format (i.e. low byte/high byte). This length does not include thechecksum.DataDataDataData (N Bytes) – The actual data associated with the command or sub-command.ChecksumChecksumChecksumChecksum (1 Byte) – The checksum is a byte-by-byte, bitwise “EXCLUSIVE OR” of theCommand, Length and Data block.Here are some important facts to remember when operating in API Mode:Here are some important facts to remember when operating in API Mode:Here are some important facts to remember when operating in API Mode:Here are some important facts to remember when operating in API Mode:1) All commands issued by the Host must receive an AcknowledgeAcknowledgeAcknowledgeAcknowledge command from thetransceiver to signal completion of the issued command. This serves as flow control forthe information going to the transceiver.2) When a command is issued by the transceiver to the Host, the Host must be ready toaccept the command and any data following the command. The transceiver will not getan AcknowledgeAcknowledgeAcknowledgeAcknowledge command from the Host.3) Although the Host will receive an AcknowledgeAcknowledgeAcknowledgeAcknowledge command for every command sent to thetransceiver, the Host must be able to accept any command issued by the transceiverprior to receiving the AcknowledgeAcknowledgeAcknowledgeAcknowledge command.

AC5124-10 SpecificationsAC5124-10 SpecificationsAC5124-10 SpecificationsAC5124-10 Specifications 11/24/03 235.15.15.15.1 SSSSYSTEM YSTEM YSTEM YSTEM CCCCOMMAND OMMAND OMMAND OMMAND SSSSETETETETThe System Commands allow the OEM to initialize the system and perform general system analysis.In addition, the EEPROM parameters can only be programmed using these commands. The tablebelow summarizes the commands.Table Table Table Table 4444 - System Command Set - System Command Set - System Command Set - System Command SetNameNameNameName CommandCommandCommandCommand LengthLengthLengthLengthLowLowLowLowLengthLengthLengthLengthHighHighHighHighDataDataDataData ChecksumChecksumChecksumChecksumReset AAh 00h 00h No Data AAhControl 86h 1 to 5 (depends onsub-command)As Required As RequiredDiagnostic Result 87h As Required As Required As RequiredStandby 88h 01h 00h 00h – Client Sleep Walk01h – Server Deep Sleep04h – Cancel StandbyAs RequiredStatus Request 8Ah 01h 00h 0 – Reset error counter1 – Don’t do anything8AhStatus Reply 8Bh 14h - 74h 00h See Section 5.1.6, StatusSection 5.1.6, StatusSection 5.1.6, StatusSection 5.1.6, StatusReplyReplyReplyReplyAs RequiredUpdate EEPROMChecksum8Ch 00h 00h No Data 8ChCheck EEPROMChecksum8Dh 00h 00h No Data 8DhEEPROM ChecksumStatus8Eh 01h 00h 0 – Checksum invalid1 – Checksum valid8EhAcknowledge As Required As Required As Required As Required5.1.15.1.15.1.15.1.1 ResetResetResetResetThe Host issues this command to a transceiver. This command provides a software reset to atransceiver, initializing the code at the same location as a hardware reset. The Host must wait for theAcknowledgeAcknowledgeAcknowledgeAcknowledge command before issuing any additional commands. This command must be followedby an RF EnableRF EnableRF EnableRF Enable command.Example: AA|00|00|AA (There are no Data bytes for this command)Acknowledge: AA|01|00|00|AB

AC5124-10 SpecificationsAC5124-10 SpecificationsAC5124-10 SpecificationsAC5124-10 Specifications 11/24/03 245.1.25.1.25.1.25.1.2 ControlControlControlControlThe Host issues this command to a transceiver to write and read EEPROM addresses as well as forNOP. The Host must wait for the Diagnostic ResultDiagnostic ResultDiagnostic ResultDiagnostic Result command before issuing any additionalcommands. Refer to Section 6, Configuring the AC5124Section 6, Configuring the AC5124Section 6, Configuring the AC5124Section 6, Configuring the AC5124 for the list of configurable EEPROMparameters.Sub-command (Counts as 1 Byte in theSub-command (Counts as 1 Byte in theSub-command (Counts as 1 Byte in theSub-command (Counts as 1 Byte in theLength)Length)Length)Length)DescriptionDescriptionDescriptionDescription02h Read EEPROM. Additional data: first 2 bytes specifystarting address. Second 2 bytes specify endingaddress.08h NOP.09h Write EEPROM. Additional data: first 2 Bytes specifystarting address. Second 2 Bytes specify endingaddress. Remaining bytes specify data to be written.(Range 00h to 7Fh)Data Frame:86h Length Low 00h Sub-command Data ChecksumRead EEPROM Example (Addresses 04h to 09h): 86|05|00|02|04|00|09|00|8CDiagnostic Result: 87|07|00|02|FF|FF|FF|FF|FF|FF|82Example (NOP): 86|01|00|08|8FDiagnostic Result: 87|02|00|08|00|8DWrite EEPROM Example (write value 01h to address 31h): 86|06|00|09|31|00|31|00|01|88Diagnostic Result: 87|02|00|09|00|8CAny additional sub-commands are reserved by the system and if used may cause system operationproblems.5.1.35.1.35.1.35.1.3 Diagnostic ResultDiagnostic ResultDiagnostic ResultDiagnostic ResultA transceiver issues this command to the Host in response to a ControlControlControlControl command.Sub result (Counts as 1 Byte in the Length)Sub result (Counts as 1 Byte in the Length)Sub result (Counts as 1 Byte in the Length)Sub result (Counts as 1 Byte in the Length) DescriptionDescriptionDescriptionDescription02h Read EEPROM08h NOP. Returns 6 Bytes (87 02 00 08 00 8D)09h Write EEPROM status.0 - Write successful. 1- Write failed.Data Frame:87h Length Low Length High Sub-result Data Checksum

AC5124-10 SpecificationsAC5124-10 SpecificationsAC5124-10 SpecificationsAC5124-10 Specifications 11/24/03 255.1.45.1.45.1.45.1.4 StandbyStandbyStandbyStandbyThe Host issues the following commands to enable Sleep Walk Mode for Clients and Deep SleepMode for Servers. See Section 6.1.13.3, Power Down ModesSection 6.1.13.3, Power Down ModesSection 6.1.13.3, Power Down ModesSection 6.1.13.3, Power Down Modes for detailed information on these modes.• 88 01 00 00 89 – This will command the Client into Sleep Walk mode.• 88 01 00 01 88 – This will command the Server into Deep Sleep mode.• 88 01 00 04 8D – This will cancel the power down functions.5.1.55.1.55.1.55.1.5 Status RequestStatus RequestStatus RequestStatus RequestThe Host issues this command to a transceiver to determine various statistics associated with the RFData Link Layer. A Data value of 00h will reset the Error Counters while a value of 01h will leave themat their current values. The Host must wait for the Status ReplyStatus ReplyStatus ReplyStatus Reply command before issuing any additionalcommands.Example: 8A|01|00|01|8AStatus Reply (0 Active Transceivers): 8B|20|00|A8|03|00|00|00|00|00|01|00|00|00|00|00|00|00|00|00|00|00|01|00|50|67|00|3C|3D|D3|01|00|07|00|00|E35.1.65.1.65.1.65.1.6 Status ReplyStatus ReplyStatus ReplyStatus ReplyA transceiver issues this command to the Host in response to a Status RequestStatus RequestStatus RequestStatus Request command. Theparameters pertain to the RF Data Link Layer and provide cumulative totals. The statistics and theirsizes are shown below:NameNameNameName TypeTypeTypeType DescriptionDescriptionDescriptionDescription SizeSizeSizeSizeTransceiver Time TimeCounterIncremented by 1 every 250ms. Initializedto 0 at power on or reset.Unsigned Byte –3 Bytes, LowByte firstTx Failures ErrorCounterNumber of times a transceiver was not ableto deliver a data frame to the destinationUnsigned Long -4 BytesTx Retries ErrorCounterNumber of times a transceiver had to retrybefore delivering a data frame to thedestinationUnsigned Long -4 BytesRx Failures ErrorCounterNumber of times a transceiver had to throwaway a received data frame because of badCRC/checksumUnsigned Long -4 BytesRx Retries ErrorCounterNumber of times data frames had to beretransmitted before a valid data frame wasreceivedUnsigned Long -4 BytesNum ActiveTransceiversDataCounterNumber of Clients registered to aServer. If the Transceiver underconsideration is a Client, just return 0Unsigned Byte -1 ByteList of RegisteredTransceiversIdentity List of 6-Byte IEEE 802.3 transceiveraddresses + 3 Byte time stamp + 3 Bytepacket count. Time stamp and packetcounter are reset at power on or Reset.12 Bytes * NumReg Clients

AC5124-10 SpecificationsAC5124-10 SpecificationsAC5124-10 SpecificationsAC5124-10 Specifications 11/24/03 26Status Reply ExampleStatus Reply ExampleStatus Reply ExampleStatus Reply ExampleNameNameNameName TypeTypeTypeType 0 Active Transceivers0 Active Transceivers0 Active Transceivers0 Active Transceivers 2 Active Transceivers2 Active Transceivers2 Active Transceivers2 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 Length Low 00h Data Checksum5.1.75.1.75.1.75.1.7 Update EEPROM ChecksumUpdate EEPROM ChecksumUpdate EEPROM ChecksumUpdate EEPROM ChecksumThe Host issues this command to a transceiver to recalculate the checksum. The Host typically issuesthis command after it has completed writing data to the EEPROM. The Host must wait for theAcknowledgeAcknowledgeAcknowledgeAcknowledge command before issuing any additional commands.Example: 8C|00|00|8C (There are no Data bytes for this command)Acknowledge: 8C|00|00|8C5.1.85.1.85.1.85.1.8 Check EEPROM ChecksumCheck EEPROM ChecksumCheck EEPROM ChecksumCheck EEPROM ChecksumThe Host issues this command to a transceiver to validate the EEPROM checksum. The Host typicallyissues this command after resetting a transceiver. A transceiver replies with a valid or invalidchecksum by sending back the EEPROM Checksum StatusEEPROM Checksum StatusEEPROM Checksum StatusEEPROM Checksum Status command.Example: 8D|00|00|8D (There are no Data bytes for this command)EEPROM Checksum Status: 8E|01|00|01|8E5.1.95.1.95.1.95.1.9 EEPROM Checksum StatusEEPROM Checksum StatusEEPROM Checksum StatusEEPROM Checksum StatusA transceiver issues this command to the Host in response to a Check EEPROM ChecksumCheck EEPROM ChecksumCheck EEPROM ChecksumCheck EEPROM Checksumcommand. A Data value of 00h indicates an invalid Checksum while a value of 01h indicates a validChecksum.

AC5124-10 SpecificationsAC5124-10 SpecificationsAC5124-10 SpecificationsAC5124-10 Specifications 11/24/03 275.1.105.1.105.1.105.1.10 AcknowledgeAcknowledgeAcknowledgeAcknowledgeA transceiver issues this command in response to some of the Host commands indicating a positiveresponse. The AcknowledgeAcknowledgeAcknowledgeAcknowledge consists of the Host command sequence with a zero length, unlessotherwise noted.5.25.25.25.2 TTTTRANSCEIVER RANSCEIVER RANSCEIVER RANSCEIVER CCCCOMMAND OMMAND OMMAND OMMAND SSSSETETETETThe Transceiver Commands allow the OEM to control the flow of data into and out of a transceiver aswell as initialization of a transceiver. The table below summarizes the commands.Table Table Table Table 5555 - Transceiver Command Set - Transceiver Command Set - Transceiver Command Set - Transceiver Command SetNameNameNameName CommandCommandCommandCommand LengthLengthLengthLengthLowLowLowLowLengthLengthLengthLengthHighHighHighHighDataDataDataData ChecksumChecksumChecksumChecksumRF Enable 80h 00h 00h No Data 80hSend Data 81h 0Ch – 7FBh (includes802.3 Header)As Required As RequiredSend Data Complete 82h 01h 00h 00h or 01h (SeeSection 5.2.3, SendSection 5.2.3, SendSection 5.2.3, SendSection 5.2.3, SendData CompleteData CompleteData CompleteData Complete)As RequiredReceived Data 83h 0Ch – 7FBh (includes802.3 Header)As Required As RequiredIn Range 84h 06h 00h IEEE 802.3 address ofServerAs RequiredOut of Range 85h 00h 00h No Data 85h5.2.15.2.15.2.15.2.1 RF EnableRF EnableRF EnableRF EnableThe Host issues this command to a transceiver prior to any RF data transfers. The Host typically issuesthis command after resetting a transceiver. This enables the RF interface of a transceiver and turns thetransmitter/receiver ON. The Host must wait for the AcknowledgeAcknowledgeAcknowledgeAcknowledge command before issuing anyadditional commands. Ensure that only one RF Enable command is issued following a Reset.Example: 80|00|00|80 (There are no Data bytes for this command)Acknowledge: 80|00|00|80

AC5124-10 SpecificationsAC5124-10 SpecificationsAC5124-10 SpecificationsAC5124-10 Specifications 11/24/03 285.2.25.2.25.2.25.2.2 Send DataSend DataSend DataSend DataThe Host issues this command to a transceiver before sending a data packet to it. Broadcast framesare sent to all registered Clients at the same time without RF-Layer acknowledgements. Broadcastframes are not required to reach all destinations. The Host must wait for the Send Data CompleteSend Data CompleteSend Data CompleteSend Data Completecommand before issuing any additional commands.Data Frame:81h Length Low Length High Data ChecksumDestinationDestinationDestinationDestinationAddressAddressAddressAddressSource AddressSource AddressSource AddressSource Address DataDataDataDataMS Byte…LS Byte MS Byte…LS ByteNote: The Data must include the following header information:• (6) Bytes for the IEEE 802.3 destination address, or FF FF FF FF FF FF for broadcastpackets• (6) Bytes for the IEEE 802.3 source addressThese unique IEEE addresses are provided by AeroComm and stored in EEPROM addresses 28h –2Dh.5.2.35.2.35.2.35.2.3 Send Data CompleteSend Data CompleteSend Data CompleteSend Data CompleteA transceiver issues this command upon completion of the data transmission process, as indicated bya RF-layer acknowledgment from the destination transceiver. An additional byte of data indicates asuccess or a failure code. This command will be returned for every Send DataSend DataSend DataSend Data command unless thedevice power fails.• Command:Command:Command:Command: 82h• Length:Length:Length:Length: 01h• Data:Data:Data:Data: 00h – Indicates success. 01h – Can’t send packet.• Checksum:Checksum:Checksum:Checksum: As requiredData Frame:82h 01h 00h Data Checksum

AC5124-10 SpecificationsAC5124-10 SpecificationsAC5124-10 SpecificationsAC5124-10 Specifications 11/24/03 295.2.45.2.45.2.45.2.4 Received DataReceived DataReceived DataReceived DataA transceiver issues this command upon reception of data from the RF interface. The information inthe data frame is the received data.Since more than one Client can transmit to a Server, multiple Received Data Received Data Received Data Received Data commands can be issuedto the Server Host at the same time. The command does not require an AcknowledgeAcknowledgeAcknowledgeAcknowledge command;therefore, the Server Host must be capable of receiving multiple, consecutive Received DataReceived DataReceived DataReceived Datacommands.Data Frame:83h Length Low Length High Data ChecksumDestinationDestinationDestinationDestinationAddressAddressAddressAddressSource AddressSource AddressSource AddressSource Address DataDataDataDataMS Byte…LS Byte MS Byte…LS Byte5.2.55.2.55.2.55.2.5 In RangeIn RangeIn RangeIn RangeThe Client issues this command upon detecting a Server beacon after a Reset or after an Out of RangeOut of RangeOut of RangeOut of Rangecommand has been issued to the Host. The Client Host will get updated with this command at thetime intervals specified by the Range Refresh parameter at EEPROM address 32h. The OEM shouldallow for some hysterisis so the Host isn’t flooded with these commands in a fringe coverage area.AeroComm has established a default value of 5 seconds through extensive testing. This commandincludes the IEEE 802.3 Server Address.Data Frame:84h 06h 00h Data ChecksumServer IEEE AddressServer IEEE AddressServer IEEE AddressServer IEEE AddressMS Byte…LS Byte5.2.65.2.65.2.65.2.6 Out of RangeOut of RangeOut of RangeOut of RangeThe Client issues this command if it does not detect a Server beacon after a Reset or after an In RangeIn RangeIn RangeIn Rangecommand has been issued to the Host. The Client Host will get updated with these commands at thetime intervals specified by the Range Refresh parameter at EEPROM address 32h. The OEM shouldallow for some hysterisis so the Host isn’t flooded with these commands in a fringe coverage area.AeroComm has established a default value of 5 seconds through extensive testing.

AC5124-10 SpecificationsAC5124-10 SpecificationsAC5124-10 SpecificationsAC5124-10 Specifications 11/24/03 306.6.6.6. AT Command SetAT Command SetAT Command SetAT Command SetVersions 3.5 and higher of the AC5124 family firmware implement an AT Command set, which is usedfor modifying settings during runtime without having to use any hardware control lines. AT Commandsare valid for modes 1, 2, and 4 of the AC5124. Whether in mode 1, 2, or 4, this command must be sentto the radio as a complete packet. Any characters before or after this command that becomeappended to this string to form a larger packet will cause the packet to be interpreted as a packet tosend over the RF and not an AT command. If the AT command set is used in mode 2, the endcharacter must be 0DH (13 decimal). If the AT command set is used in mode 4, the fixed length mustbe set to 6. If power is lost while in AT command mode, the radio will power back up into normalmode. All AT command characters should be capitalized. All AT commands end in a 0DH character(13 decimal). The radio will not respond to an AT command unless the 0DH character is detected atthe end of the command.6.16.16.16.1 IRAM DIRAM DIRAM DIRAM DEFINEDEFINEDEFINEDEFINEDIRAM is an acronym for Internal Random Access Memory. IRAM is a static memory that holds many ofthe parameters that control the radio such as channel number. Using the Read/Write IRAM commandallows these parameters to be changed dynamically. Because IRAM is static, when the radio is reset,these parameters will revert back to the settings stored in the E²PROM. Be careful not to changeundocumented IRAM addresses as undesired operation may occur. Below is a list of IRAMparameters that can be changed in the radio:IRAM Address (Hex) DescriptionF5 Channel Number6.26.26.26.2 CCCCOMMAND OMMAND OMMAND OMMAND IIIINSTRUCTIONSNSTRUCTIONSNSTRUCTIONSNSTRUCTIONS/R/R/R/RESPONSESESPONSESESPONSESESPONSESBelow is a description of the AT Commands and their appropriate responses.

AC5124-10 SpecificationsAC5124-10 SpecificationsAC5124-10 SpecificationsAC5124-10 Specifications 11/24/03 316.2.16.2.16.2.16.2.1 Enter Command ModeEnter Command ModeEnter Command ModeEnter Command ModePrior to sending any other AT command, the radio must be sent the Enter Command Mode commandby the OEM Host. Below is a description of that command:AT+++↵Where ↵ is equal to 0DH (13 decimal).If it is unable to successfully receive the command, the radio will interpret the string as a packet to sendout over the RF and will act accordingly. Upon successfully receiving the Enter Command Modecommand, the radio will be ready to receive other AT commands and will issue the following responseto the OEM Host:OK↵Where ↵ is equal to 0DH (13 decimal).After successfully receiving the Enter Command Mode command, the radio will not be able tocommunicate with other radios until AT command mode is exited. If a server is commanded into ATmode, the clients will go out of range.6.2.26.2.26.2.26.2.2 Exit Command ModeExit Command ModeExit Command ModeExit Command ModeTo exit AT mode without resetting the internal static parameters of the radio, an Exit Command Modecommand should be sent to the radio by the OEM Host. Below is a description of that command:ATO↵Where ↵ is equal to 0DH (13 decimal).If it successfully receives the command, the radio will issue the following response to the OEM Host:OK↵Where ↵ is equal to 0DH (13 decimal).If it is at least able to receive the ↵ character but there is an error in the command or part of thecommand is missing, the radio will issue the following response to the OEM Host:ERROR↵Where ↵ is equal to 0DH (13 decimal).Upon successfully receiving the Exit Command Mode command, the radio will resume RFcommunications.

AC5124-10 SpecificationsAC5124-10 SpecificationsAC5124-10 SpecificationsAC5124-10 Specifications 11/24/03 326.2.36.2.36.2.36.2.3 Power-on Reset CommandPower-on Reset CommandPower-on Reset CommandPower-on Reset CommandTo force the radio to perform a Power-on Reset, the Power-on Reset command should be sent to theradio by the OEM Host. Below is a description of that command:ATZ↵Where ↵ is equal to 0DH (13 decimal).If it successfully receives the command, the radio will issue the following response to the OEM Host:OK↵Where ↵ is equal to 0DH (13 decimal).If it is at least able to receive the ↵ character but there is an error in the command or part of thecommand is missing, the radio will issue the following response to the OEM Host:ERROR↵Where ↵ is equal to 0DH (13 decimal).Upon successfully receiving the Power-on Reset Command, the radio will perform a power-on resetand resume RF communications.6.2.46.2.46.2.46.2.4 Read IRAM ByteRead IRAM ByteRead IRAM ByteRead IRAM ByteIRAM Reads are performed one byte at a time. To read a byte of IRAM, the OEM Host should issuethe following command to the radio:ATSXX?↵Where XX is equal to an IRAM address. If the address is less than 10H, the leading zero must still besent such as ATS05?↵Where ↵ is equal to 0DH (13 decimal).If it successfully receives the command, the radio will issue the following response to the OEM Host:YY↵Where YY is equal to the value of the IRAM location requested.Where ↵ is equal to 0DH (13 decimal).If it is at least able to receive the ↵ character but there is an error in the command or part of thecommand is missing, the radio will issue the following response to the OEM Host:ERROR↵Where ↵ is equal to 0DH (13 decimal).

AC5124-10 SpecificationsAC5124-10 SpecificationsAC5124-10 SpecificationsAC5124-10 Specifications 11/24/03 336.2.56.2.56.2.56.2.5 Write IRAM ByteWrite IRAM ByteWrite IRAM ByteWrite IRAM ByteIRAM Writes are performed one byte at a time. To write a byte of IRAM, the OEM Host should issue thefollowing command to the radio:ATSXX=YY↵Where XX is equal to an IRAM address. If the address is less than 10H, the leading zero must still besent such as ATS05=YY↵Where YY is equal to the value to store in the IRAM location. If the value is less than 10H, the leadingzero must still be sent such as ATSFE=0F↵Where ↵ is equal to 0DH (13 decimal).If it successfully receives the command, the radio will issue the following response to the OEM Host:OK↵Where ↵ is equal to 0DH (13 decimal).If it is at least able to receive the ↵ character but there is an error in the command or part of thecommand is missing, the radio will issue the following response to the OEM Host:ERROR↵Where ↵ is equal to 0DH (13 decimal).

AC5124-10 SpecificationsAC5124-10 SpecificationsAC5124-10 SpecificationsAC5124-10 Specifications 11/24/03 346.2.66.2.66.2.66.2.6 Read EEPROM ByteRead EEPROM ByteRead EEPROM ByteRead EEPROM ByteEEPROM Reads are performed one byte at a time. To read a byte of EEPROM, the OEM Host shouldissue the following command to the radio:ATWXX?↵Where XX is equal to an EEPROM address. If the address is less than 10H, the leading zero must stillbe sent such as ATW05?↵Where ↵ is equal to 0DH (13 decimal).If it successfully receives the command, the radio will issue the following response to the OEM Host:YY↵Where YY is equal to the value of the EEPROM location requested.Where ↵ is equal to 0DH (13 decimal).If it is at least able to receive the ↵ character but there is an error in the command or part of thecommand is missing, the radio will issue the following response to the OEM Host:ERROR↵Where ↵ is equal to 0DH (13 decimal).

AC5124-10 SpecificationsAC5124-10 SpecificationsAC5124-10 SpecificationsAC5124-10 Specifications 11/24/03 356.2.76.2.76.2.76.2.7 Write EEPROM ByteWrite EEPROM ByteWrite EEPROM ByteWrite EEPROM ByteEEPROM Writes are performed one byte at a time. To write a byte of EEPROM, the OEM Host shouldissue the following command to the radio (NOTE: before sending this command, the EEPROM WriteEnable pin must be Low):ATWXX=YY↵Where XX is equal to an EEPROM address. If the address is less than 10H, the leading zero must stillbe sent such as ATW05=YY↵Where YY is equal to the value to store in the EEPROM location. If the value is less than 10H, theleading zero must still be sent such as ATWFE=0F↵Where ↵ is equal to 0DH (13 decimal).If it successfully receives the command, the radio will issue the following response to the OEM Host:OK↵Where ↵ is equal to 0DH (13 decimal).If it is at least able to receive the ↵ character but there is an error in the command or part of thecommand is missing, the radio will issue the following response to the OEM Host:ERROR↵Where ↵ is equal to 0DH (13 decimal).

AC5124-10 SpecificationsAC5124-10 SpecificationsAC5124-10 SpecificationsAC5124-10 Specifications 11/24/03 367.7.7.7. Configuring the AC5124Configuring the AC5124Configuring the AC5124Configuring the AC5124Table 6 – EEPROM ParametersTable 6 – EEPROM ParametersTable 6 – EEPROM ParametersTable 6 – EEPROM Parameters, contains the many configurable parameters that are stored in theEEPROM on a transceiver. These parameters are read by the AeroComm firmware on power-up orwhen a reset is executed. This section provides the definitions, valid values and use for each of theseparameters.It is important to follow the steps below when writing to the EEPROM. Refer to Section 5, APISection 5, APISection 5, APISection 5, APICommand SetCommand SetCommand SetCommand Set, for all referenced commands.1)1)1)1) Do not write to any EEPROM addresses other than those listed in Table 6 – EEPROMDo not write to any EEPROM addresses other than those listed in Table 6 – EEPROMDo not write to any EEPROM addresses other than those listed in Table 6 – EEPROMDo not write to any EEPROM addresses other than those listed in Table 6 – EEPROMParameters. Do not copy a transceiver’s EEPROM data to another transceiver. Doing soParameters. Do not copy a transceiver’s EEPROM data to another transceiver. Doing soParameters. Do not copy a transceiver’s EEPROM data to another transceiver. Doing soParameters. Do not copy a transceiver’s EEPROM data to another transceiver. Doing somay cause a transceiver to malfunction.may cause a transceiver to malfunction.may cause a transceiver to malfunction.may cause a transceiver to malfunction.2) EEPROM parameters can only be changed when the API Mode is active. Whenoperating in a Transparent Mode, holding Pin 2 (PKTMODE) logic low will force atransceiver to enter a “pseudo” API Mode; however, the full API command set is notsupported.Supported commands include: ResetResetResetReset, ControlControlControlControl (and sub-commands), Update EEPROMUpdate EEPROMUpdate EEPROMUpdate EEPROMChecksumChecksumChecksumChecksum, Check EEPROM ChecksumCheck EEPROM ChecksumCheck EEPROM ChecksumCheck EEPROM Checksum, EEPROM Checksum StatusEEPROM Checksum StatusEEPROM Checksum StatusEEPROM Checksum Status, and AcknowledgeAcknowledgeAcknowledgeAcknowledge.3) Pin 37 (WR_ENA) must be logic low to enable writes to the EEPROM.4) After all desired EEPROM addresses are configured using the Write EEPROMWrite EEPROMWrite EEPROMWrite EEPROM command,the OEM should invoke the Update EEPROM ChecksumUpdate EEPROM ChecksumUpdate EEPROM ChecksumUpdate EEPROM Checksum command. If this command isnot executed, the checksum will not be updated with the newly written data. Pin 37(WR_ENA) must be logic low for this command to execute successfully.5) Once the EEPROM checksum is updated, the OEM must reset the transceiver before anyEEPROM changes will become active. Pin 37 (WR_ENA) must be logic high during thereset. If operating in API Mode, issue the ResetResetResetReset command. If operating in a TransparentMode, Pin 2 (PKTMODE) must be taken logic high and the OEM must use Pin 38(µP_RESET) or cycle power to reset the transceiver. If Pin 2 (PKTMODE) remains lowduring a reset, the transceiver will remain in “pseudo” API Mode.

AC5124-10 SpecificationsAC5124-10 SpecificationsAC5124-10 SpecificationsAC5124-10 Specifications 11/24/03 37Table Table Table Table 6666 - EEPROM Parameters - EEPROM Parameters - EEPROM Parameters - EEPROM ParametersParameterParameterParameterParameter EEPROMEEPROMEEPROMEEPROMAddressAddressAddressAddressLengthLengthLengthLength(Bytes)(Bytes)(Bytes)(Bytes)DefaultDefaultDefaultDefault(Hex)(Hex)(Hex)(Hex) DescriptionDescriptionDescriptionDescriptionSoftware VersionNumber1Dh 8 Unique toeachversionFirmware version number – Must not bemodified by the OEMIEEE MACAddress28h 6 Unique toeach radioIEEE assigned MAC Address – Must not bemodified by the OEM.Byte range = 00h – FFhChannel 2Eh 1 00h Byte range = 00h – 4ChTransmit Attempts 2Fh 1 10h Transmit AttemptsByte range = 01h – FFhReceive Mode 31h 1 03h Determines what type of data frames arereceived by the Host, based on IEEE addressof received frame.01h – Unicast/Broadcast02h – Unicast03h – PromiscuousRange Refresh 32h 1 20h This byte specifies the number of 200ms ticksbetween range indications. Suggested rangeis 6.4s to 10s. Byte range = 20h – 32h.Server/ ClientMode33h 1 02h Server = 01hClient = 02hSystem ID 34h 8 00 00 00 0000 00 00 01Used to demarcate RF networks.Byte range = 00h – FFhEnd Character 3Eh 1 FFh This byte specifies the character that will beused to signify the end of a packet.Byte range = 00h – FFhBaud High 40h 1 FFh See Table 7 – BH/BL Selections for CommonTable 7 – BH/BL Selections for CommonTable 7 – BH/BL Selections for CommonTable 7 – BH/BL Selections for CommonBaud RatesBaud RatesBaud RatesBaud RatesBaud Low 41h 1 F1h See Table 7 – BH/BL Selections for CommonTable 7 – BH/BL Selections for CommonTable 7 – BH/BL Selections for CommonTable 7 – BH/BL Selections for CommonBaud RatesBaud RatesBaud RatesBaud RatesFixed PacketLength High43h 1 00h Byte range = 00h – 07hFixed PacketLength Low44h 1 90h Byte range = 00h – FFhRandom Back-Off 45h 1 03h 00h – wait 1 packet time after error01h – wait 1-2 packet times after error03h – wait 1-4 packet times after error07h – wait 1-8 packet times after error0Fh – wait 1-16 packet times after error1Fh – wait 1-31 packet times after error

AC5124-10 SpecificationsAC5124-10 SpecificationsAC5124-10 SpecificationsAC5124-10 Specifications 11/24/03 38ParameterParameterParameterParameter EEPROMEEPROMEEPROMEEPROMAddressAddressAddressAddressLengthLengthLengthLength(Bytes)(Bytes)(Bytes)(Bytes)DefaultDefaultDefaultDefault(Hex)(Hex)(Hex)(Hex) DescriptionDescriptionDescriptionDescriptionSerial InterfaceMode4Ah 1 01h 01h – Transparent, Fixed Length, Timeout02h – Transparent, End Character03h – API04h – Transparent, Fixed Length, No TimeoutAdditional settings are:Bit 3 – RTS Enable0 = Radio does not listen to RTS1 = Radio respects RTS handshakingBit 4 – Reserved (Always 0)Bit 5 – Parity (9 bit) Mode0 = Radio only transmits 8 bit data1 = Radio transmits 9 bit dataBit 6 – Modem Mode0 = Radio does not use modemhandshaking1 = Radio uses modem handshaking(must set bit 3 also)Bit 7 – Sleep Walk Mode (clients only)0 = Radio will not sleep walk1 = Radio will be in sleep walk modeTransmit Mode 4Bh 1 00h 00h – Addressed Mode01h – Broadcast ModeRF Mode 1 4Ch 1 00h Bit 0 – Reserved (Always 0)Bit 1 – Read Switches0 = Disable Read Switches1 = Enable Read SwitchesBit 2 – End Type0 = Disable End Type1 = Enable End TypeBit 3 – Reserved (Always 0)Bit 4 – Limit RF Buffer0 = Full RF Buffering1 = Only use one RF BufferBit 5 – RF Priority0 = Serial Interface Priority1 = RF Receive PriorityBit 6 – Reserved (Always 0)Bit 7 – Mixed Mode0 = Disable Mixed Mode1 = Enable Mixed ModeInterface Timeout 4Dh 1 00h 00h – 1.8ms40h – 18ms80h – 130msC0h – 222msBroadcastAttempts4Eh 1 04h Byte range = 01h – FFh

AC5124-10 SpecificationsAC5124-10 SpecificationsAC5124-10 SpecificationsAC5124-10 Specifications 11/24/03 39ParameterParameterParameterParameter EEPROMEEPROMEEPROMEEPROMAddressAddressAddressAddressLengthLengthLengthLength(Bytes)(Bytes)(Bytes)(Bytes)DefaultDefaultDefaultDefault(Hex)(Hex)(Hex)(Hex) DescriptionDescriptionDescriptionDescriptionRF Mode 4Fh 1 01h Bit 0 – Reserved (Always 1)Bit 1 – Turbo Mode0 = No turbo mode1 = Enable turbo modeBit 2 – Reserved (Always 0)Bit 3 – Reserved (Always 0)Bit 4 – Baud Rate Double0 = Use programmed baud rate1 = Double programmed baud rateBit 5 – 485 RTS0 = RTS functions normal1= RTS is an output used for RS485systemsBit 6 – In Range Select0 = In Range is at Pin 151 = In Range is at Pin 28Bit 7 – Auto Destination0 = Client uses programmed DestinationIEEE MAC Address1 = Client automatically finds a destinationServer on the same Channel andSystem IDDestination IEEEMAC Address50h 6 FF FF FFFF FF FFUsed in Address Mode.Byte range = 00h – FFhSleep Time 7Ah 3 00 00 0A Byte range = 00h – FFh, 200ms incrementsWait Time 7Dh 3 00 00 20 Byte range = 00h – FFh, 200ms increments7.1.17.1.17.1.17.1.1 Software Version NumberSoftware Version NumberSoftware Version NumberSoftware Version NumberEEPROM Address: 1DhLength: 8 BytesDefault: Depends on versionCan be read by the OEM for AeroComm firmware version information. The OEM must not change thisinformation.7.1.27.1.27.1.27.1.2 IEEE MAC AddressIEEE MAC AddressIEEE MAC AddressIEEE MAC AddressEEPROM Address: 28hLength: 6 BytesA unique 6 Byte, IEEE 802.3 Ethernet address assigned by AeroComm to each transceiver. The OEMmust not change this information.

AC5124-10 SpecificationsAC5124-10 SpecificationsAC5124-10 SpecificationsAC5124-10 Specifications 11/24/03 407.1.37.1.37.1.37.1.3 ChannelChannelChannelChannelEEPROM Address: 2EhLength: 1 ByteDefault: 00hRange: 00h – 4ChProvides 77 unique and non-interfering pseudorandom hopping sequences or Channels. This allowsthe OEM to configure up to 77 independent, co-located data networks. The combination of theChannel and System ID must be unique to each network of transceivers to establish communication.Here are some examples:• Network A: Channel – 05h, System ID – 01 02 03 04 05 06 07 08• Network B: Channel – 4Ah, System ID – 11 22 33 44 55 66 77 88Multiple Servers in the same coverage area must be programmed with different Channels to preventinoperability of the networks.It is highly recommended that the OEM change the Channel and System ID from their default values.7.1.47.1.47.1.47.1.4 Transmit AttemptsTransmit AttemptsTransmit AttemptsTransmit AttemptsEEPROM Address: 2FhLength: 1 ByteDefault: 10hRange: 01h – FFhThis parameter specifies the maximum number of times a packet will be transmitted over the RFinterface. A transceiver operating in API Mode will reply with a Send Data CompleteSend Data CompleteSend Data CompleteSend Data Complete command (with aFailure Code = 1) when the maximum transmits has been attempted without success. Transceiversoperating in any of the Transparent Modes will not send an acknowledgement to their Host.7.1.57.1.57.1.57.1.5 Receive ModeReceive ModeReceive ModeReceive ModeEEPROM Address: 31hLength: 1 ByteDefault: 03hRange: 01h – 03hThere are 3 different interface receive modes. When a transceiver receives a data packet over the RF, itmust determine if the packet is addressed to it or another transceiver on the network. Receive modespecifies the criteria a transceiver uses for validating a data packet. When the transceiver is operatingin any Transparent Mode, Receive Mode must be set to a value of 03h (Promiscuous).7.1.5.17.1.5.17.1.5.17.1.5.1 Unicast/Broadcast (01h)Unicast/Broadcast (01h)Unicast/Broadcast (01h)Unicast/Broadcast (01h)Unicast/Broadcast Mode is only valid for transceivers operating in API Mode. Transceivers will receivepackets that have matching IEEE 802.3 destination addresses and broadcast packets. Broadcastpackets will have a destination address equal to FF FF FF FF FF FF. It is important to note there are noRF acknowledgements for Broadcast packets. All other packets will be discarded.

AC5124-10 SpecificationsAC5124-10 SpecificationsAC5124-10 SpecificationsAC5124-10 Specifications 11/24/03 417.1.5.27.1.5.27.1.5.27.1.5.2 Unicast (02h)Unicast (02h)Unicast (02h)Unicast (02h)Unicast Mode is only valid for transceivers operating in API Mode. Transceivers will only receivepackets that have matching IEEE 802.3 destination addresses. All other packets will be discarded.7.1.5.37.1.5.37.1.5.37.1.5.3 Promiscuous (03h)Promiscuous (03h)Promiscuous (03h)Promiscuous (03h)Promiscuous Mode is valid for transceivers operating in any Serial Interface Mode. Transceivers willreceive allallallall packets. The Host will need to determine what action to take when receiving a packet.7.1.67.1.67.1.67.1.6 Range RefreshRange RefreshRange RefreshRange RefreshEEPROM Address: 32hLength: 1 ByteDefault: 20hRange: 01h – FFhRange Refresh is valid for transceivers operating in any Serial Interface Mode. The Range Refreshparameter allows the OEM to select the interval of time the Client uses when searching for a Serverbeacon. If a Client is out of range, it will search for a Server beacon the amount of time specified bythis parameter before reporting an out of range condition. A Client reports an out of range condition bytaking Pin 15 (IN_RANGE) logic high, and if in API Mode, issuing an Out of RangeOut of RangeOut of RangeOut of Range command. A Clientreports an in range condition by taking Pin 15 (IN_RANGE) logic low, and if in API Mode, issuing and InInInInRangeRangeRangeRange command. This parameter is useful when operating in a fringe condition to minimize the InInInInRangeRangeRangeRange and Out of RangeOut of RangeOut of RangeOut of Range commands that may flood the Host. AeroComm has established a defaultvalue of 5 seconds through extensive testing.7.1.77.1.77.1.77.1.7 Server/Client ModeServer/Client ModeServer/Client ModeServer/Client ModeEEPROM Address: 33hSize: 1 ByteDefault: 02hRange: 01h – 02hSpecifies whether a transceiver is operating in the Client Mode (02h) or Server Mode (01h).

AC5124-10 SpecificationsAC5124-10 SpecificationsAC5124-10 SpecificationsAC5124-10 Specifications 11/24/03 427.1.87.1.87.1.87.1.8 System IDSystem IDSystem IDSystem IDEEPROM Address: 34hLength: 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 FFThe System ID is used in conjunction with the Channel and serves as a password to maintain securetransfers of data. The combination of the Channel and System ID must be unique to each network oftransceivers to establish communication. Here are some examples:• Network A: Channel – 05h, System ID – 01 02 03 04 05 06 07 08• Network B: Channel – 4Ah, System ID – 11 22 33 44 55 66 77 88Multiple Servers in the same coverage area must be programmed with different Channels to preventinoperability of the networks. The System ID will not prevent inoperability that occurs from locatingmultiple Servers with the same Channel in the same coverage area.7.1.97.1.97.1.97.1.9 End CharacterEnd CharacterEnd CharacterEnd CharacterEEPROM Address: 3EhSize: 1 ByteDefault: FFhRange: 00h – FFhThis parameter is only valid for transceivers operating in Transparent Mode 02. The value specified bythe OEM will indicate the last character in a data packet. When this End Character is received by atransceiver, the packet, including the End Character, will be transmitted. The packet length, includingthe End Character, cannot exceed 2 KBytes.

AC5124-10 SpecificationsAC5124-10 SpecificationsAC5124-10 SpecificationsAC5124-10 Specifications 11/24/03 437.1.107.1.107.1.107.1.10 Baud High (BH) and Baud Low (BL)Baud High (BH) and Baud Low (BL)Baud High (BH) and Baud Low (BL)Baud High (BH) and Baud Low (BL)EEPROM Address: 40h and 41h respectivelyLength: 1 Byte eachDefault: FFh for BH and F1h for BLRange: F4h, 84h – FFh, FFh (BH, BL)There are two types of baud rates associated with a transceiver: RF Baud Rate and Serial InterfaceBaud Rate. The RF Baud Rate is not configurable and is fixed at 882 Kbps. The Serial Interface BaudRate is configurable and can be programmed up to 882 Kbps. However, the maximum effective datatransmission rate is approximately 250 Kbps – 300 Kbps due to protocol overhead.Baud High (BH) and Baud Low (BL) are used to configure the serial interface data rate between atransceiver and its Host. Standard PC baud rate values are provided below:Table Table Table Table 7777 - BH/BL Selections For Common Baud Rates - BH/BL Selections For Common Baud Rates - BH/BL Selections For Common Baud Rates - BH/BL Selections For Common Baud Rates(Using a 28.224 MHz Crystal)(Using a 28.224 MHz Crystal)(Using a 28.224 MHz Crystal)(Using a 28.224 MHz Crystal)Baud RateBaud RateBaud RateBaud Rate BHBHBHBH BLBLBLBL Interface TimeoutInterface TimeoutInterface TimeoutInterface Timeout300 F4h 84h 4Ch1,200 FDh 21h 14h2,400 FEh 91h Bh4,800 FFh 48h 69,600 FFh A4h 314,400 FFh C3h 319,200 FFh D2h 328,800 FFh E1h 238,400 FFh E9h 257,600 (default) FFh F1h 2115,200 With BH/BL set to 57,600, set Baud Rate Doublebit in the RF Mode Byte at EEPROM address 4Fh.2Custom baud rates can be calculated using the following formula:28.224 * 106Baud Rate = 32.0 * (65,536 – BH, BL)The calculated value must be within 3% of the actual value.See Section 6.1.18.2, Baud Rate DoubleSection 6.1.18.2, Baud Rate DoubleSection 6.1.18.2, Baud Rate DoubleSection 6.1.18.2, Baud Rate Double for information on how to double the baud rate.7.1.117.1.117.1.117.1.11 Fixed Packet Length High & LowFixed Packet Length High & LowFixed Packet Length High & LowFixed Packet Length High & LowEEPROM Address: 43h and 44h respectivelyLength: 1 Byte eachDefault: 00h for 43h and 90h for 44hRange: 00h – 07h for 43h, 01h – FFh for 44hThis parameter is only valid for transceivers operating in Transparent Modes 01 or 04. This parameteris ignored when a transceiver is operating in all other modes. The Fixed Packet Length cannot exceed2 KBytes.

AC5124-10 SpecificationsAC5124-10 SpecificationsAC5124-10 SpecificationsAC5124-10 Specifications 11/24/03 447.1.127.1.127.1.127.1.12 Random Back-OffRandom Back-OffRandom Back-OffRandom Back-OffEEPROM Address: 45hLength: 1 ByteDefault: 03hThe Carrier Sense Multiple Access (CSMA) protocol does not keep time slots for each registeredClients like some protocols. Instead, CSMA allows all clients to contend for an open time slot on apacket-by-packet basis. Typically, all Clients don’t send data at the same time; however, when theydo, collisions can occur. To avoid further collisions, a Client will wait a random number of packet timesbefore resending its data. The amount of randomness is controlled by this parameter. Here are thevalid values:• 00h – Wait 1 packet time, then retry• 01h – Wait 1 – 2 packet times, then retry• 03h – Wait 1 – 4 packet times, then retry• 07h – Wait 1 – 8 packet times, then retry• 0Fh – Wait 1 – 16 packet times, then retry• 1Fh – Wait 1 – 31 packet times, then retryThis parameter is only used by a transceiver operating with Turbo Mode disabled. See SectionSectionSectionSection6.1.18.1, Turbo Mode6.1.18.1, Turbo Mode6.1.18.1, Turbo Mode6.1.18.1, Turbo Mode for details.7.1.137.1.137.1.137.1.13 Serial Interface ModeSerial Interface ModeSerial Interface ModeSerial Interface ModeEEPROM Address: 4AhLength: 1 ByteDefault: 01hThere are four Serial Interface Modes for the OEM transceiver including one API Mode and threeTransparent Modes. All Transparent Modes are differentiated by the definition of when data will betransmitted by a transceiver. See Section 4, Serial Interface ModesSection 4, Serial Interface ModesSection 4, Serial Interface ModesSection 4, Serial Interface Modes, for detailed information on eachmode.7.1.13.17.1.13.17.1.13.17.1.13.1 RTS EnableRTS EnableRTS EnableRTS EnableEEPROM Address: 4Ah, bit 3Length: 1 BitDefault: 0Range: 0 or 1Setting this bit to a value of 1 will enable the RTS line for standard RTS handshaking. Setting this bit toa value of 0 will disable RTS handshaking. See Section 4.7.2, RTS HandshakingSection 4.7.2, RTS HandshakingSection 4.7.2, RTS HandshakingSection 4.7.2, RTS Handshaking for more information.

AC5124-10 SpecificationsAC5124-10 SpecificationsAC5124-10 SpecificationsAC5124-10 Specifications 11/24/03 457.1.13.27.1.13.27.1.13.27.1.13.2 Parity ModeParity ModeParity ModeParity ModeEEPROM Address: 4Ah, bit 5Length: 1 BitDefault: 0Range: 0 or 1Setting this bit to a value of 1 will enable Parity (9 bit transmit) mode. In this mode, 9 bit bytes can besent over the RF. Enabling this mode will cut net throughput in half. All transceivers on the sameAll transceivers on the sameAll transceivers on the sameAll transceivers on the samenetwork must have the same setting for Parity Mode.network must have the same setting for Parity Mode.network must have the same setting for Parity Mode.network must have the same setting for Parity Mode.7.1.13.37.1.13.37.1.13.37.1.13.3 Modem ModeModem ModeModem ModeModem ModeEEPROM Address: 4Ah, bit 6Length: 1 BitDefault: 0Range: 0 or 1Setting this bit to a value of 1 will enable all of the modem lines (DCD, DSR, DTR, RI, and CTS), exceptRTS. Therefore, bit 3 must also be set to a value of 1 to enable RTS. Otherwise, bit 3 can be setwithout setting bit 6 for normal transceiver RTS operation. Refer to Section 4.7.3, ModemSection 4.7.3, ModemSection 4.7.3, ModemSection 4.7.3, ModemHandshakingHandshakingHandshakingHandshaking, for more information.7.1.13.47.1.13.47.1.13.47.1.13.4 Power Down ModesPower Down ModesPower Down ModesPower Down ModesThe Power Down Modes include a Sleep Walk and Deep Sleep mode. Sleep Walk is for Clients onlyand Deep Sleep is for Servers only.

AC5124-10 SpecificationsAC5124-10 SpecificationsAC5124-10 SpecificationsAC5124-10 Specifications 11/24/03 467.1.13.4.17.1.13.4.17.1.13.4.17.1.13.4.1 SSSSLEEP LEEP LEEP LEEP WWWWALK ALK ALK ALK MMMMODE ODE ODE ODE (C(C(C(CLIENTS LIENTS LIENTS LIENTS OOOONLYNLYNLYNLY))))EEPROM Address: 4Ah, bit 7Length: 1 BitDefault: 0Range: 0 or 1If bit 7 of the Serial Interface Mode byte is set to a value of 1, the Client enters into Sleep Walk Mode.This applies to all Serial Interface Modes (01-04).There are two parameters that control the operation of the Sleep Walk Mode – Sleep Time and WaitTime. Both parameters can be programmed in 200ms increments. See Section 6.1.20, Sleep TimeSection 6.1.20, Sleep TimeSection 6.1.20, Sleep TimeSection 6.1.20, Sleep Timeand Section 6.1.21, Wait TimeSection 6.1.21, Wait TimeSection 6.1.21, Wait TimeSection 6.1.21, Wait Time for details on these parameters.When a Client enters Sleep Walk, the RF section is turned off while maintaining synchronization with aServer. Due to crystal tolerances, a Client can maintain synchronization with a Server for a maximumof two seconds. Upon waking up, a Client must synchronize with a Server before sending any data.There are two wake up events that can occur for a Client:1) A Client will remain “asleep” for the duration of Sleep Time unless it receives a byte over theserial interface. If this occurs, a Client will wake and send the data once it synchronizes with aServer. If a Client does not receive a Server beacon, it will remain awake until a beacon isreceived. Once synchronized, a Client will remain awake for the duration of Wait Time for anyadditional communications with a Server. If a Client receives data within the duration of WaitTime, another Wait Time begins. This process will continue until the Wait Time expires.2) If the Sleep Time expires, a Client will wake and listen for a Server beacon for up to 50ms. If itdoes not receive a Server beacon within 50ms, it will go back to sleep. If it does receive aServer beacon, it will wait up to 2ms for any pending data from the Server. If a Client receivesdata within the 2ms, it will remain awake for the duration of Wait Time. If a Client receives datawithin the duration of this period, another Wait Time begins. This process will continue untilthe Wait Time expires.There are two methods of enabling the Sleep Walk Mode for Clients. If a Client is operating in aTransparent Mode, bit 7 of EEPROM address 4Ah must be set to a value of 1. If a Client is operating inAPI Mode, the Client Host must issue the following commands, only after a RF EnableRF EnableRF EnableRF Enable command isissued.• 88 01 00 00 89 – This will command the Client into Sleep Walk Mode.• 88 01 00 04 8D – This will cancel the power down functions.

AC5124-10 SpecificationsAC5124-10 SpecificationsAC5124-10 SpecificationsAC5124-10 Specifications 11/24/03 477.1.13.4.27.1.13.4.27.1.13.4.27.1.13.4.2 DDDDEEP EEP EEP EEP SSSSLEEP LEEP LEEP LEEP MMMMODE ODE ODE ODE (S(S(S(SERVERS ERVERS ERVERS ERVERS OOOONLYNLYNLYNLY))))Deep Sleep Mode is only valid for Servers operating in API Mode. In Deep Sleep Mode, a Servercompletely shuts down and remains in a powered down mode until a byte is received over the serialinterface. This is the only wake-up event that is valid in Deep Sleep Mode. A Server will not wake up ifa Client tries to transmit data to it; therefore, this mode is intended for use on Servers that initiate allcommunications and do not need to monitor the RF interface for incoming packets.To enter Deep Sleep Mode, a Server Host must issue the following commands, only after a RF EnableRF EnableRF EnableRF Enablecommand is issued.• 88 01 00 01 88 – This will command the Server into Deep Sleep Mode.• 88 01 00 04 8D – This will cancel the power down functions.7.1.147.1.147.1.147.1.14 Transmit ModeTransmit ModeTransmit ModeTransmit ModeEEPROM Address: 4BhLength: 1 ByteDefault: 00hRange: 00h or 01hThis parameter is only valid for transceivers operating in any Transparent Mode. Programming thisbyte to a value of 00h enables Address Mode and a value of 01h enables Broadcast Mode. Refer toSection 4.6, Addressed & Broadcast CommunicationsSection 4.6, Addressed & Broadcast CommunicationsSection 4.6, Addressed & Broadcast CommunicationsSection 4.6, Addressed & Broadcast Communications, for detailed information on each of thesemodes.7.1.157.1.157.1.157.1.15 RF Mode 1RF Mode 1RF Mode 1RF Mode 1EEPROM Address: 4ChLength: 1 ByteDefault: 00hRange: 00h – 7ChThe RF Mode 1 byte contains several settings that provide additional flexibility to an OEM’s application.These settings are described in detail in the following sections.

AC5124-10 SpecificationsAC5124-10 SpecificationsAC5124-10 SpecificationsAC5124-10 Specifications 11/24/03 487.1.167.1.167.1.167.1.16 Read SwitchesRead SwitchesRead SwitchesRead SwitchesEEPROM Address: 4Ch, bit 1Length: 1 BitDefault: 0Range: 0 or 1The Read Switches bit is useful for systems that need to change Channels or Server/Client Modeduring operation. When bit 1 is set to a value of 1, the Host can change the state of Pin 13 to enable ordisable the new pin definitions listed below in the table. When Pin 13 is logic low, Read Switches isenabled and the new pin definitions take precedence over the existing pin definitions. When Pin 13 islogic high, Read Switches is disabled and normal pin functionality is restored.PinPinPinPin 13 15 17 19 22 36 34 32FunctionFunctionFunctionFunction ReadSwitchesServer/ClientChannelBit 5ChannelBit 4ChannelBit 3ChannelBit 2ChannelBit 1ChannelBit 0Channel Bits 0 (least significant bit) through 5 (most significant bit) are used to force a transceiver to aparticular Channel between 0 and 63. When Server/Client (Pin 15) is logic low, a transceiver is forcedto become a Server. When it is disconnected or forced logic high, a transceiver is forced to become aClient.7.1.16.17.1.16.17.1.16.17.1.16.1 End TypeEnd TypeEnd TypeEnd TypeEEPROM Address: 4Ch, bit 2Length: 1 BitDefault: 0Range: 0 or 1This parameter is only valid for transceivers operating in any Transparent Mode. Setting this bit to avalue of 1 enables the End Type function. When enabled, a transceiver monitors for a Server/ClientMode change. If a transceiver changes from a Client to a Server, it automatically broadcasts all datapackets regardless of the Transmit Mode byte configuration. If a transceiver changes from a Server toa Client, it automatically addresses all data packets regardless of the Transmit Mode Byteconfiguration. End Type works well with the Auto Destination Mode described in Section 6.1.18.5, AutoSection 6.1.18.5, AutoSection 6.1.18.5, AutoSection 6.1.18.5, AutoDestinationDestinationDestinationDestination. If Auto Destination is not enabled, the Destination IEEE MAC Address programmed atEEPROM address 50h will be used.

AC5124-10 SpecificationsAC5124-10 SpecificationsAC5124-10 SpecificationsAC5124-10 Specifications 11/24/03 497.1.16.27.1.16.27.1.16.27.1.16.2 Limit RF BufferLimit RF BufferLimit RF BufferLimit RF BufferEEPROM Address: 4Ch, bit 4Length: 1 BitDefault: 0Range: 0 or 1Setting this bit to a value of 1 reduces the number of RF receive buffers to one. Otherwise, there areeight RF receive buffers on the AC5124, each large enough to store the maximum packet size of 2KBytes. This allows the AC5124 to act as a RAM buffer in many applications and actually improvesystem throughput as opposed to wired communications. However, in applications running their ownprotocol, such as TCP-IP, where retries already exist, these buffers can be harmful to the performanceof the system. If a transceiver transmitting data is configured at a higher baud rate than the transceiverreceiving the data, it is possible the receive buffers will fill up very quickly causing communications tostop until a buffer is freed.Depending on how long it takes to free a buffer, TCP-IP could experience a timeout, causing thetransceiver to resend an entire TCP-IP packet. If the transceiver has already sent part of the TCP-IPpacket, the Host receiving the packets could receive them out of order, causing long delays. Insituations like this, it is useful to set the Limit RF Buffer bit to a value of 1, thus eliminating seven of theeight RF buffers. This will allow the Host protocol to control data transfers and hence improve overallthroughput.7.1.16.37.1.16.37.1.16.37.1.16.3 RF PriorityRF PriorityRF PriorityRF PriorityEEPROM Address: 4Ch, bit 5Length: 1 BitDefault: 0Range: 0 or 1Setting this bit to a value of 1 will change a transceiver’s interrupt priority to service the RF interfacebefore the serial interface, given that a contention occurs. For example, if data arrives at bothinterfaces at the same time, a data packet will be received over the RF interface before data is receivedover the serial interface. Thus, CTS will remain logic high even if a transceiver is ready for data. Thesame condition will occur if a transceiver is in process of receiving data over the RF interface. Once theRF interface has completed receiving data, CTS will transition logic low, allowing data to be sent to atransceiver.A value of 0 will allow a transceiver to operate normally, giving the serial interface priority over the RFinterface.7.1.16.47.1.16.47.1.16.47.1.16.4 Mixed ModeMixed ModeMixed ModeMixed ModeEEPROM Address: 4Ch, bit 7Length: 1 BitDefault: 0Range: 0 or 1This parameter is only valid for Client transceivers operating in any Transparent Mode. Setting this bitto a value of 1 enables the Mixed Mode function and allows a Client to communicate with a Serveroperating in API Mode.

AC5124-10 SpecificationsAC5124-10 SpecificationsAC5124-10 SpecificationsAC5124-10 Specifications 11/24/03 507.1.177.1.177.1.177.1.17 Interface TimeoutInterface TimeoutInterface TimeoutInterface TimeoutEEPROM Address: 4DhLength: 1 ByteDefault: 00hRange: 00h - FFhThis parameter applies only to Transparent Mode 01. This parameter specifies the amount of timebetween bytes that a transceiver will wait before transmitting the data packet. If a value other than 00h,40h, 80h or C0h is desired, the following formula can be used to calculate a new timeout value:Timeout (ms) = Decimal value of 4Dh x 0.9 (+0 to –0.9ms accuracy)0H = 6.5ms40H = 21ms80H = 137msC0H = 235msExample:EEPROM address 4Dh = 20h: Decimal equivalent of 20h = 32d; therefore, 32 x 0.9 = 28.8msDue to accuracy, the Interface Timeout in this example will range between 27.9ms and 28.8ms.Therefore, it is important to note that Interface Timeout should be set to be equal to or greater than twobyte times at the programmed interface baud rate.7.1.187.1.187.1.187.1.18 Broadcast AttemptsBroadcast AttemptsBroadcast AttemptsBroadcast AttemptsEEPROM Address: 4EhLength: 1 ByteDefault: 04hRange: 01h – FFhThe parameter is valid for transceivers operating in all Serial Interface Modes with Broadcast Modeenabled. Broadcast Attempts specifies the number of times the RF interface will broadcast eachpacket. The receiving transceiver will discard duplicate packets.7.1.197.1.197.1.197.1.19 RF ModeRF ModeRF ModeRF ModeEEPROM Address: 4FhLength: 1 ByteDefault: 01hRange: 01h – FBhLike the RF Mode 1 byte, the RF Mode byte contains several settings that provide additional flexibility toan OEM’s application. These settings are described in detail in the following sections.

AC5124-10 SpecificationsAC5124-10 SpecificationsAC5124-10 SpecificationsAC5124-10 Specifications 11/24/03 517.1.19.17.1.19.17.1.19.17.1.19.1 Turbo ModeTurbo ModeTurbo ModeTurbo ModeEEPROM Address: 4Fh, bit 1Length: 1 BitDefault: 0Range: 0 or 1If bit 1 is set to a value of 0, a transceiver will operate in CSMA mode, allowing random back-off forcollision avoidance. In CSMA Mode, a transceiver will wait one packet time between successfulpackets. If a collision occurs, a transceiver will wait a random number of packet times beforeresending its data. The amount of randomness is controlled by the Random Back-Off parameterlocated at EEPROM address 45h. See Section 6.1.12, Random Back-OffSection 6.1.12, Random Back-OffSection 6.1.12, Random Back-OffSection 6.1.12, Random Back-Off for details on this parameter.When bit 1 is set to a value of 1, a transceiver will operate in Turbo Mode. Turbo Mode was designedstrictly for high-speed point-to-point communications, as it has no back off between errors. In otherwords, it eliminates the wait time between successful packets and will transmit packets immediately,one after the other. If the packet is not successfully received, a transceiver will just resend the packetuntil a successful receipt is acknowledged.7.1.19.27.1.19.27.1.19.27.1.19.2 Baud Rate DoubleBaud Rate DoubleBaud Rate DoubleBaud Rate DoubleEEPROM Address: 4Fh, bit 4Length: 1 bitDefault: 0Range: 0 or 1Setting this bit to a value of 1 will double the baud rate programmed in the Baud High and Baud Lowbytes at EEPROM addresses 40h and 41h, respectively. See Section 6.1.10, Baud High (BH) andSection 6.1.10, Baud High (BH) andSection 6.1.10, Baud High (BH) andSection 6.1.10, Baud High (BH) andBaud Low (BL)Baud Low (BL)Baud Low (BL)Baud Low (BL) for a table of calculated values for common baud rates and for a formula to calculatecustom baud rates. The OEM must ensure that the doubled baud rate does not exceed 882 Kbps.7.1.19.37.1.19.37.1.19.37.1.19.3 485 RTS485 RTS485 RTS485 RTSEEPROM Address: 4Fh, bit 5Length: 1 BitDefault: 0Range: 0 or 1Setting this bit to a value of 1 will enable Pin 27 to function as a Driver and Receive Enable for RS485systems. Setting this bit to a value of 0 will allow the RTS to function as programmed in bit 3 of theSerial Interface Mode byte located at EEPROM address 4Ah.7.1.19.47.1.19.47.1.19.47.1.19.4 In Range SelectIn Range SelectIn Range SelectIn Range SelectEEPROM Address: 4Fh, bit 6Length: 1 BitDefault: 0Range: 0 or 1Normally, Pin 15 is IN_RANGE; however, setting this bit to a value of 1 will move IN_RANGE to Pin 28.This is useful for applications using Read Switches, which uses Pin 15 for changing the Server/ClientMode.

AC5124-10 SpecificationsAC5124-10 SpecificationsAC5124-10 SpecificationsAC5124-10 Specifications 11/24/03 527.1.19.57.1.19.57.1.19.57.1.19.5 Auto DestinationAuto DestinationAuto DestinationAuto DestinationEEPROM Address: 4Fh, bit 7Length: 1 BitDefault: 0Range: 0 or 1The AC5124 supports an addressed mode of communication called Auto Destination. This mode isonly for Clients operating in one of the Transparent Modes. To configure a Client for Auto Destination,set this bit to a value of 1. With Auto Destination enabled, a Client has the ability to detect any Serverwith the same Channel and System ID. Therefore, a Client can dynamically route all communicationsto the Server that is in range. This mode is useful for mobile or roaming applications where a Client willbe interfacing with different Servers from time to time. It is important to note that multiple Servers withthe same Channel and System ID must not be located in range of one another. Doing so will causeinoperability of the system.7.1.207.1.207.1.207.1.20 Destination IEEE MAC AddressDestination IEEE MAC AddressDestination IEEE MAC AddressDestination IEEE MAC AddressEEPROM Address: 50hLength: 6 BytesDefault: FF FF FF FF FF FFRange: 00h – FFh for each byteThe Destination IEEE MAC Address is used by transceivers operating in any Transparent Mode withAddressed Mode (EEPROM address 4Bh = 00h) enabled. When this address is programmed to anactual transceiver address, RF-layer acknowledgements will be used to guarantee packet delivery. Ifthe address is left programmed to the default value, all packets sent will be considered broadcastpackets without RF-layer acknowledgements. If Auto Destination is enabled, RF layeracknowledgements will be used. See Section 4.6, Addressed & Broadcast CommunicationSection 4.6, Addressed & Broadcast CommunicationSection 4.6, Addressed & Broadcast CommunicationSection 4.6, Addressed & Broadcast Communication for moredetails on using this parameter.7.1.217.1.217.1.217.1.21 Sleep TimeSleep TimeSleep TimeSleep TimeEEPROM Address: 7AhLength: 3 BytesDefault: 00 00 0ARange: 00h – FFh, 200ms incrementsSleep Time is used by Client transceivers programmed to operate in Sleep Walk Mode, described inSection 6.1.13.3.1, Sleep Walk ModeSection 6.1.13.3.1, Sleep Walk ModeSection 6.1.13.3.1, Sleep Walk ModeSection 6.1.13.3.1, Sleep Walk Mode. Each increment in the value of this byte will cause a Client toremain asleep 200ms longer.7.1.227.1.227.1.227.1.22 Wait TimeWait TimeWait TimeWait TimeEEPROM Address: 7DhLength: 3 BytesDefault: 00 00 20Range: 00h – FFh, 200ms incrementsWait Time is used by Client transceivers programmed to operate in Sleep Walk Mode, described inSection 6.1.13.3.1, Sleep Walk ModeSection 6.1.13.3.1, Sleep Walk ModeSection 6.1.13.3.1, Sleep Walk ModeSection 6.1.13.3.1, Sleep Walk Mode. Each increment in the value of this byte will cause a Client toremain awake 200ms longer.

AC5124-10 SpecificationsAC5124-10 SpecificationsAC5124-10 SpecificationsAC5124-10 Specifications 11/24/03 538.8.8.8. Initializing the AC5124 TransceiverInitializing the AC5124 TransceiverInitializing the AC5124 TransceiverInitializing the AC5124 TransceiverUpon reset or power-up, a transceiver requires a minimum of 400ms for hardware initialization tocomplete. During this time, CTS is driven logic high prohibiting the reception of any data orcommands. Once complete, CTS is driven logic low, allowing a transceiver to send or receive dataand commands, depending on the mode of operation.8.18.18.18.1 TTTTRANSPARENT RANSPARENT RANSPARENT RANSPARENT MMMMODE ODE ODE ODE IIIINITIALIZATIONNITIALIZATIONNITIALIZATIONNITIALIZATIONWhen operating in any Transparent Mode, the initialization sequence is managed by the AeroCommprotocol. API commands are not issued and there are no acknowledgements from a transceiver ondata delivery, unless the OEM protocol has built-in acknowledgements. The IN_RANGE pin (Pin 15)provides in range information for the Transparent Modes.8.28.28.28.2 API MAPI MAPI MAPI MODE ODE ODE ODE IIIINITIALIZATIONNITIALIZATIONNITIALIZATIONNITIALIZATIONAfter the hardware initialization has completed, a transceiver operating in API Mode is ready to sendand receive API commands as outlined in Section 5, API Command SetSection 5, API Command SetSection 5, API Command SetSection 5, API Command Set. At this point, the onlycommand that cannot be issued is the Send DataSend DataSend DataSend Data command. This command can only be issued afterthe RF EnableRF EnableRF EnableRF Enable and In RangeIn RangeIn RangeIn Range commands have been issued.Before data communications can begin, a Client needs to be authenticated. The Client Host mustissue an RF EnableRF EnableRF EnableRF Enable command to activate the Client and receive an AcknowledgeAcknowledgeAcknowledgeAcknowledge command from theClient. The Server transmits a beacon containing its IEEE 802.3 address. Once the Client receives theServer beacon, it will issue an In RangeIn RangeIn RangeIn Range command to the Client Host containing the IEEE 802.3 Serveraddress. The Client Host must receive the In RangeIn RangeIn RangeIn Range command from the Client before the Send DataSend DataSend DataSend Datacommand is invoked.The AC5124 transceivers are designed to be single threaded, meaning that for every command issued,there is a reply command that indicates the completion of the command issued. There can be nocommand interleaving.

AC5124-10 SpecificationsAC5124-10 SpecificationsAC5124-10 SpecificationsAC5124-10 Specifications 11/24/03 54The figure below provides an example of the initialization sequence for both Clients and Serversfollowing the configuration of EEPROM parameters. This occurs only in API Mode.Figure Figure Figure Figure 2222 - API Mode Initialization - API Mode Initialization - API Mode Initialization - API Mode InitializationApply PowerWait for CTS logic lowHost issues RF EnableRF EnableRF EnableRF EnablecommandClient issues In RangeIn RangeIn RangeIn Rangecommand to Host with ServeraddressServer can now transmit orreceive dataClient can now transmit orreceive dataHost reads EEPROM for IEEEsource addressHost awaits AcknowledgeAcknowledgeAcknowledgeAcknowledgeClient TransceiverClient TransceiverClient TransceiverClient Transceiver Server TransceiverServer TransceiverServer TransceiverServer Transceiver

AC5124-10 SpecificationsAC5124-10 SpecificationsAC5124-10 SpecificationsAC5124-10 Specifications 11/24/03 559.9.9.9. Mechanical OverviewMechanical OverviewMechanical OverviewMechanical OverviewThe AC5124 measures 1.65”W x 2.65”L. Critical parameters are as follows:• J1J1J1J1 – 40 pin OEM interface connector (AMP P/N 177986-1) mates with AMP P/N 177985-1• MMCX JackMMCX JackMMCX JackMMCX Jack – Antenna connector (Telegartner P/N J01341C0081) mates with anymanufacturer’s MMCX plugFigure Figure Figure Figure 3333 – AC5124 with MMCX – AC5124 with MMCX – AC5124 with MMCX – AC5124 with MMCX

AC5124-10 SpecificationsAC5124-10 SpecificationsAC5124-10 SpecificationsAC5124-10 Specifications 11/24/03 56Figure Figure Figure Figure 4444 – AC5124 with Integral Antenna – AC5124 with Integral Antenna – AC5124 with Integral Antenna – AC5124 with Integral Antenna

AC5124-10 SpecificationsAC5124-10 SpecificationsAC5124-10 SpecificationsAC5124-10 Specifications 11/24/03 5710.10.10.10. Ordering InformationOrdering InformationOrdering InformationOrdering Information10.110.110.110.1 PPPPRODUCT RODUCT RODUCT RODUCT PPPPART ART ART ART NNNNUMBERSUMBERSUMBERSUMBERSAC5124-10:AC5124-10:AC5124-10:AC5124-10: AC5124 with 10mW output power, interface data rates to 882 Kbps, MMCX antennaconnectorAC5124-10A:AC5124-10A:AC5124-10A:AC5124-10A: AC5124 with 10mW output power, interface data rates to 882 Kbps, integralAeroComm NZH microstrip dipole antennaAC5124-200:AC5124-200:AC5124-200:AC5124-200: AC5124 with 200mW output power, interface data rates to 882 Kbps, MMCX antennaconnectorAC5124-200A:AC5124-200A:AC5124-200A:AC5124-200A: AC5124 with 200mW output power, interface data rates to 882 Kbps, integralAeroComm NZH microstrip dipole antenna10.210.210.210.2 DDDDEVELOPER EVELOPER EVELOPER EVELOPER KKKKIT IT IT IT PPPPART ART ART ART NNNNUMBERSUMBERSUMBERSUMBERSSDK-5124C-10:SDK-5124C-10:SDK-5124C-10:SDK-5124C-10: Includes (2) AC5124-10 transceivers, (2) RS232 Serial Adapter Boards, (2) Powersupplies, (2) Serial cables, (2) S191FL-5-RMM-2450S dipole antennas with 5” pigtailand MMCX connector, configuration/testing software, Integration engineeringsupportSDK-5124C-200:SDK-5124C-200:SDK-5124C-200:SDK-5124C-200: Includes (2) AC5124-200 transceivers, (2) RS232 Serial Adapter Boards, (2) Powersupplies, (2) Serial cables, (2) S191FL-5-RMM-2450S dipole antennas with 5”pigtail and MMCX connector, configuration/testing software, Integrationengineering support

Navigation menu