Laird Connectivity 4X90200 RF Transceiver Module User Manual 4490 manual

AeroComm Corporation RF Transceiver Module 4490 manual

Contents

Users Manual 1

VERSION 3.1
ContentsAC4490 TRANSCEIVER MODULE 1AC4490 features 1Overview 1SPECIFICATIONS 3Pin Definitions 4Electrical Specifications 6THEORY OF OPERATION 7RF Architecture 7Modes of Operation 7Transmit Mode 7Receive Mode 7Command Mode 8API CONTROL 8Receive API Packet 9API Transmit Packet 9API Send Data Complete 9API Receive Packet 9Protocol Status/Receive Acknowledgement 10Protocol Status 10Receive Acknowledgement 10Long Range Mode 10SERIAL INTERFACE 12Serial Communications 12Asynchronous Operation 12Parity 12OEM Host Data Rate 13Serial Interface Baud Rate 13Interface Timeout / RF Packet Size 14Flow Control 15Half Duplex / Full Duplex 15System Timing & Latency 15System Throughput 16SOFTWARE INTERFACE 17Networking 17One Beacon Mode / Range Refresh 18Auto Config Parameters 18Interface Options 19Modem Mode 19RS485 Modem Mode 20Max Power 20TIMING DIAGRAMS 21AC4490 Timing Diagrams 21HARDWARE INTERFACE 23Pin Definitions 23Generic I/O 23TXD & RXD 23Hop Frame 23CTS 23GND 23RTS 23Test / 9600 Baud 24RSSI 24UP_Reset 25Command/Data 25AD In 25CONFIGURING THE AC4490 26AT Commands 27On-the-Fly Control Commands 27Command Descriptions 30EEPROM PARAMETERS 36DIMENSIONS 40Mechanical Drawings 40ORDERING INFORMATION 44Product Part Number Tree 44Developer Kit Part Numbers 44COMPLIANCY INFORMATION 45AC4490-1x1 45Agency Identification Numbers 45Approved Antenna List 45FCC / IC Requirements for Modular Approval 46OEM Equipment Labeling Requirements 46Antenna Requirements 47Warnings required in OEM Manuals 47Channel Warning 47APPENDIX I - SAMPLE POWER SUPPLY 48Bill of Materials 48Schematic 49PCB Layout 49APPENDIX II - 5V TO 3.3V LEVELS 51Voltage Level Conversion IC’s 51Passive Resistor Voltage Divider 51APPENDIX III - API 52Polling Network 52Addressed Transmit API 53Broadcast Transmit API 53Receive API 54
ContentsEnhanced Receive API 55Normal Receive Mode (non-API) 55Loopback Repeater 55Time Division Multiple Access Network 56APPENDIX IV - SYNC TO CHANNEL 57Sync to Channel 57What is it and do I need it? 57How do I configure Sync to Channel? 59I've configured my radios, what's next? 65
DOCUMENT INFORMATIONCopyright © 2007 AeroComm, Inc. All rights reserved.The information contained in this manual and the accompanying software programs are copyrighted and all rights arereserved by AeroComm, Inc. AeroComm, Inc. reserves the right to make periodic modifications of this product withoutobligation to notify any person or entity of such revision. Copying, duplicating, selling, or otherwise distributing anypart of this product or accompanying documentation/software without the prior consent of an authorizedrepresentative of AeroComm, Inc. is strictly prohibited.All brands and product names in this publication are registered trademarks or trademarks of their respective holders.This material is preliminaryInformation furnished by AeroComm in this specification is believed to be accurate. Devices sold by AeroComm arecovered by the warranty and patent indemnification provisions appearing in its Terms of Sale only. AeroComm makesno warranty, express, statutory, and implied or by description, regarding the information set forth herein. AeroCommreserves the right to change specifications at any time and without notice.AeroComm’s products are intended for use in normal commercial and industrial applications. Applications requiringunusual environmental requirements such as military, medical life-support or life-sustaining equipment are specificallynot recommended without additional testing for such application.Limited Warranty, Disclaimer, Limitation of LiabilityFor a period of one (1) year from the date of purchase by the OEM customer, AeroComm warrants the OEMtransceiver against defects in materials and workmanship. AeroComm will not honor this warranty (and this warrantywill be automatically void) if there has been any (1) tampering, signs of tampering; 2) repair or attempt to repair byanyone other than an AeroComm authorized technician.This warranty does not cover and AeroComm will not be liable for, any damage or failure caused by misuse, abuse,acts of God, accidents, electrical irregularity, or other causes beyond AeroComm’s control, or claim by other than theoriginal purchaser.In no event shall AeroComm be responsible or liable for any damages arising: From the use of product; From the lossof use, revenue or profit of the product; or As a result of any event, circumstance, action, or abuse beyond the controlof AeroComm, whether such damages be direct, indirect, consequential, special or otherwise and whether suchdamages are incurred by the person to whom this warranty extends or third party.If, after inspection, AeroComm determines that there is a defect, AeroComm will repair or replace the OEM transceiverat their discretion. If the product is replaced, it may be a new or refurbished product.
DOCUMENT INFORMATIONRevision DescriptionVersion 1.0 3/15/02 - Initial Release VersionVersion 1.1 12/18/02 - Preliminary ReleaseVersion 1.2 12/20/02 - Preliminary Release. Changed location of new interface pins for highercompatibility with AC4424 family.Version 1.3 1/29/03 - Updated interface baud rate formula/table. Updated current consumptiontable. Corrected RSSI plot. Updated interface timeout information. Renamedproduct family to AC4490. Multiple EEPROM read/write now allowed.Version 1.4 2/18/03 - Added Max Power Byte. Removed Write Enable references. Fixed PowerDown/Up command response. Removed peer-to-peer bit. Added Auto Destination.Added unicast only bit. Added 500 mW product. Revised part numbers. Updatedchannel number settings.Version 1.5 Not released.Version 1.6 11/07/03 - Added One beacon and modem modes. Included AC4486 product line.Added 500 mW specifications. Updated part numbers. Added AT Commands.Eliminated Commercial designation; All transceivers are now Industrial qualified.Version 1.7 7/9/04 - Changed Range Refresh so 0x00 is an invalid setting. Updated AC4490-500output power. Added warranty information. Updated part numbers. Removedsupport of One Beacon mode. Added DES.Version 1.8 1/03/04 - Changed minimum timeout at 19,200 to 3. Added support for One Beaconmode. Changed voltage requirements for -200. Added on the fly read temperatureand EEPROM read/write commands. Removed AC4486 product information. AddedAuto Channel.Version 1.9 7/29/05 - Removed documentation for static commands. Added Australian channels.Added CC 26 command. Updated mechanical drawing for MMXC version. Includednew RSSI table. Added 1x1 documentation. Added Protocol Status, ReceivedAcknowledgement, and Receive API modes.Version 2.0 9/06/05 - Added Appendix 1 - Sample Power SupplyVersion 2.1 10/06/05 - Added CC 27 command. Added Long Range mode. Added EEPROMwrite warning.Version 2.2 11/08/05 - Removed CC 27 command. Removed Long Range mode. Corrected RS-485 DE Control.Version 2.3 12/20/05 - Removed stream mode documentation. Added Enhanced API commands.Updated Australian channels.Version 2.4 Not released.Version 2.5 7/03/06 - Removed sub hop adjust documentation. Removed Configuration Modedocumentation. Added Probe command. Added Max Power Backup byte (address0x8E). Added Product ID bytes (addresses 0x90 - 0x9F). Changed default EnhancedAPI value to 0xF8. Added Serial Communications documentation. Added 4490LR-200 documentation. Updated ording information and product tree. Added AppendixII - 5V to 3.3V levels. Added Appendix III - API. Added Appendix IV - Sync to Channel.
DOCUMENT INFORMATIONVersion 2.6 7/13/06 - Added AC4490LR-1000 documentation. Added Long Range documentationand EEPROM parameters. Removed Read/Write API Control Commands. Updatedordering information and product tree.Version 2.7 8/3/06 - Added Table of Contents.Version 2.8 10/16/06 - Updated Approved Antenna List.Version 2.9 1/9/07 - Updated Approved Antenna List. Updated Agency Identification numbers.Version 3.0 2/1/07 - Added CMD/Data RX disable and RS485 Modem Modes. Added IndustrialTemperature enhancement information and commands. Changed range refreshdefintion for servers with sync-to-channel enabled and updated sync-to-channelinformation.Version 3.1 7/8/07 - Updated Approved Antenna List. Updated Agency Identification numbers.Revision Description
www.aerocomm.comAC4490 TRANSCEIVER MODULE1The compact AC4490 900MHz transceiver can replace miles of cable in harsh industrial environments. Using field-provenFHSS technology which needs no additional FCC licensing in the Americas, OEMs can easily make existing systems wirelesswith little or no RF expertise.AC4490 FEATURESNETWORKING AND SECURITY• Drop-in replacement for AC4424 2.4 GHz product family• Generic I/O digital lines and integrated DAC/ADC functions• Retries and Acknowledgements• API Commands to control packet routing and acknowledgement on a packet-by-packet basis• Frequency Hopping Spread Spectrum for security and interference rejection• Customizable RF Channel number and system ID• Dynamic link analysis, remote radio discovery• Low latency and high throughput• Hardware Protocol Status monitoringEASY TO USE• Continuous 76.8 kbps RF data stream• Software selectable interface baud rates from 1200 bps to 115.2 kbps• Low cost, low power and small size ideal for high volume, portable and battery powered applications• All modules are qualified for Industrial temperatures (-40°C to 80°C)• Advanced configuration available using AT commandsOVERVIEWThe AC4490 is a member of AeroComm’s ConnexRF OEM transceiver family. The AC4490 is a cost effective, highperformance, frequency hopping spread spectrum transceiver; designed for integration into OEM systems operatingunder FCC part 15.247 regulations for the 900 MHz ISM band.AC4490 transceivers provide an asynchronous TTL/RS-485 level serial interface for OEM Host communications.Communications include both system and configuration data. The Host supplies system data for transmission toother Host(s). Configuration data is stored in the on-board EEPROM. All frequency hopping, synchronization, and RFsystem data transmission/reception is performed by the transceiver.To boost data integrity and security, the AC4490 uses AeroComm’s field-proven FHSS technology featuring optionalData-Encryption Standards (DES). Fully transparent, these transceivers operate seamlessly in serial cablereplacement applications.AC4490 transceivers can operate in a Point-to-Point, Point-to-Multipoint, Client-Server, or Peer-to-Peer architecture.One transceiver is configured as a Server and there can be one or many Clients. To establish synchronizationbetween transceivers, the Server emits a beacon. Upon detecting a beacon, the Client transceiver informs its Hostand an RF link is established.
AC4490 TRANSCEIVER MODULE2This document contains information about the hardware and software interface between an AeroComm AC4490transceiver and an OEM Host. Information includes the theory of operation, specifications, interface definition,configuration information and mechanical drawings. The OEM is responsible for ensuring the final product meets allappropriate regulatory agency requirements listed herein before selling any product.Note: Unless mentioned specifically by name, the AC4490 modules will be referred to as the “radio” or “transceiver”.Individual naming is used to differentiate product specific features. The host (PC/Microcontroller/Any device to whichthe AC4490 module is connected) will be referred to as “OEM Host”.
www.aerocomm.comSPECIFICATIONS2Table 1: AC4490 SpecificationsGeneral20 Pin Interface Connector Molex 87759-0030, mates with Samtec SMM-110-02-S-DRF Connector Johnson Components 135-3711-822Antenna AC4490-1x1: Customer must provide AC4490-200: MMCX Connector or integral antennaAC4490-1000: MMCX ConnectorSerial Interface Data Rate Baud rates from 1200 bps to 115,200 bpsPower Consumption (typical) Duty Cycle (TX=Transmit; RX=Receive) 10%TX 50%TX 100%TX 100%RX Pwr-Down Deep Sleep1x1: 33mA 54mA 80mA 28mA 15mA 3mA200: 38mA 68mA 106mA 30mA 19mA 6mA1000: 130mA 650mA 1300mA 30mA 19mA 6mAChannels 3 Channel Sets comprising 56 total channelsSecurity One byte System ID. 56-bit DES encryption key.Interface Buffer Size Input/Output:256 bytes eachTransceiverFrequency Band 902 – 928 MHzRF Data Rate 76.8 kbps fixedRF Technology Frequency Hopping Spread SpectrumOutput Power Conducted (no antenna) EIRP (3dBi gain antenna)AC4490-1x1: 10mW typical 20mW typicalAC4490-200: 100mW typical 200mW typicalAC4490-1000: 743mW typical 1486mW typicalSupply Voltage AC4490-1x1: 3.3V, ±50mV rippleAC4490-200: 3.3 – 5.5V, ±50mV rippleAC4490-1000*: Pin 10: 3.3 – 5.5V ±50mV ripple Pin 11: 3.3 ±3%, ±100mV ripple* Pins 10 and 11 may be tied together, provided the supply voltage never falls below 3.3 V andis capable of supplying 1.5 A of current. Pins 10 & 11 are internally connected on the AC4490-200 only.Sensitivity -100dBm typical @ 76.8kbps RF Data Rate-110dBm typical @ 76.8kbps RF Data Rate (AC4490LR-200/-1000)EEPROM write cycles 20000Hop period 20 ms
SPECIFICATIONS4PIN DEFINITIONSThe AC4490 has a simple interface that allows OEM Host communications with the transceiver. The table belowshows the connector pin numbers and associated functions. The I/O direction is with respect to the transceiver. Alloutputs are 3.3VDC levels and inputs are 5VDC TTL (with the exception of AC4490-1x1 and AC4490-1000 transceiverswhich have 3.3V inputs). All inputs are weakly pulled High and may be left floating during normal operation (with theexceptions listed for the AC4490-1x1).Transceiver (Cont’d)Range, Line of Site (based on 3dBi gainantenna)AC4490-1x1: Up to 1 mileAC4490-200: Up to 4 milesAC4490LR-200: Up to 8 milesAC4490-1000: Up to 20 milesAC4490LR-1000: Up to 40 milesEnvironmentalTemperature (Operating) -40°C to 80°CTemperature (Storage) -50°C to +85°CHumidity (non-condensing) 10% to 90%PhysicalDimensions Transceiver with MMCX Connector: 1.65” x 1.9” x 0.20”Transceiver with Integral Antenna: 1.65” x 2.65” x 0.20”AC4490-1x1: 1.00” x 1.00” x 0.162”CertificationsAC4490-200A AC4490-200/AC4490LR-200 AC4490-1000 FCC Part 15.247 KQLAC4490-100 KQL-4x90200 KQLAC4490Industry Canada (IC) 2268C-AC4490 2268C-4x90200 2268C-AC44901000Table 2: AC4490 Pin DefinitionsModule Pin1x1 Pin Type Signal Name Function1 4 O GO0 Generic Output pin2 6 O TXD Transmitted data out of the transceiverI/O RS485 A (True)1Non-inverted RS-485 representation of serial data3 7 I RXD Data input to the transceiverI/O RS485 B (Invert) 1Mirror image of RS-485 ATable 1: AC4490 Specifications
5SPECIFICATIONSwww.aerocomm.com4 52GI0 Generic Input pin5 3 GND GND Signal Ground6 O Hop Frame Pulses low when the transceiver is hopping frequencies.7 9 O CTS Clear to Send – Active Low when the transceiver is ready to accept data for transmission.8102IRTS Request to Send – When enabled in EEPROM, the OEM Host can take this High when it is notready to accept data from the transceiver. NOTE: Keeping RTS High for too long can causedata loss.919 OGO1 Generic Output pin10 2PWR VCC1 AC4490-1x1: 3.3V, ±50mV rippleAC4490-200: 3.3 – 5.5V, ±50mV ripple (Pin 10 is internally connected to Pin 11)AC4490-1000: 3.3 – 5.5V, ±50mV ripple11 11 PWR VCC2 AC4490-1x1: 3.3V, ±50mV rippleAC4490-200: 3.3 – 5.5V, ±50mV ripple (Pin 11 is internally connected to Pin 10)AC4490-1000: 3.3V ±3%, ±100mV ripple12 23 ITest Test Mode – When pulled logic Low and then applying power or resetting, the transceiver’sserial interface is forced to a 9600, 8-N-1 rate. To exit, the transceiver must be reset or power-cycled with Test Mode logic High.13 12 ORSSI Received Signal Strength - An analog output giving an instantaneous indication of receivedsignal strength. Only valid while in Receive Mode.14 212IGI1 Generic Input pin15 16 IUP_RESET RESET – Controlled by the AC4490 for power-on reset if left unconnected. After a stable power-on reset, a logic High pulse will reset the transceiver. 16 13 GND GND Signal Ground17 17 ICMD/Data When logic Low, the transceiver interprets OEM Host data as command data. When logic High,the transceiver interprets OEM Host data as transmit data.18 153IAD In 10 bit Analog Data Input19 204ODA_Out 10 bit Analog Data Output20 18 OIn_Range When logic Low, a Client is in range of a Server on same Channel and System ID. Always low ona Server radio.N/A 14 RF RF Port RF InterfaceN/A 22 IReset Active Low version of UP_RESET. If RESET is used, UP_RESET should be left floating and ifUP_RESET is used, RESET should be left floating.1. When ordered with a RS-485 interface (not available on the AC4490-1x1).2. Must be tied to VCC or GND if not used. Should never be permitted to float.3. If used, requires a shunt 0.1μF capacitor at pin 15 followed by a series 1k resistor.4. If used, requires a series 1k resistor at pin 20 followed by a shunt 0.1μF capacitor.Table 2: AC4490 Pin DefinitionsModule Pin1x1 Pin Type Signal Name Function
SPECIFICATIONS6ELECTRICAL SPECIFICATIONSTable 3: Input Voltage CharacteristicsAC44901x1 / AC4490-1000M AC4490-200XSignal Name High Min.High Max.Low Min.Low Max.High Min.High Max.Low Min.Low Max. UnitRS485A/B N/A 12 -7 N/A N/A 12 -7 N/A VRXD 2.31 3.3 00.99 25.5 00.8 VGI0 2.31 3.3 00.99 25.5 00.8 VRTS 2.31 3.3 00.99 25.5 00.8 VTest 2.31 3.3 00.99 25.5 00.8 VGI1 2.31 3.3 00.99 25.5 00.8 VUP_RESET 0.8 3.3 00.6 0.8 5 0 0.6 VCommand/Data 2.31 3.3 00.99 25.5 00.8 VAD In N/A 3.3 0N/A N/A 3.3 0N/A VTable 4: Output Voltage CharacteristicsSignal Name Module Pin1x1Pin Type HighMin.LowMax. UnitGO0 119 O2.5 @ 8mA 0.4 @ 8mA VTXD 2 6 O 2.5 @ 2mA 0.4 @ 2mA VRS485A/B 2,3 N/A I/O 3.3 @ 1/8 Unit Load N/A VHop Frame 6 1 O 2.5 @ 2mA 0.4 @ 2mA VCTS 7 9 O 2.5 @ 2mA 0.4 @ 2mA VGO1 919 O2.5 @ 2mA 0.4 @ 2mA VRSSI 13 12 OSee Figure 1 See Figure 1 VDA_Out 19 20 ON/A N/A V11. DA_Out is an unbuffered, high impedance output and must be buffered by the OEM Host when used.In Range 20 18 O2.5 @ 2mA 0.4 @ 2mA V
www.aerocomm.comTHEORY OF OPERATION3RF ARCHITECTUREThe AC4490 utilizes a Server-Client network where all Clients synchronize their hopping to the Server. The Servertransmits a beacon during the first 1 ms of every hop (20 ms). The Client transceivers listen for this beacon and uponhearing it assert their In_Range Low and synchronize their hopping with the Server.Each network should consist of only one Server and there should never be two servers on the same RF Channelnumber in the same coverage area as the interference between the two servers will severely hinder RFcommunications. For those applications requiring collocated servers, Aerocomm recommends using the Sync-to-Channel feature which is further explained in the Sync-to-Channel Appendix.MODES OF OPERATIONThe AC4490 has three different operating modes; Receive, Transmit, & Command Mode. If the transceiver is notcommunicating with another radio, it will be in Receive Mode actively listening for a beacon from the Server. If theClient determines that the beacon is from a server operating on the same RF Channel and System ID, it will respondby asserting In_Range Low. A transceiver will enter Transmit or Command mode when the OEM Host sends data overthe serial interface. The state of the Command/Data pin (Pin 17) or the data contents determine which of the twomodes will be entered.Transmit ModeAll packets sent over the RF are either Addressed or Broadcast packets. Broadcast and Addressed delivery can becontrolled dynamically with the API Control byte and corresponding on-the-fly commands. To prohibit transceiversfrom receiving broadcast packets, Unicast only can be enabled.ADDRESSED PACKETSWhen sending an addressed packet, the RF packet is sent only to the receiver specified in destination address. Toincrease the odds of successful delivery, Transmit retries are utilized. transparent to the OEM Host; the sending radiowill send the RF packet to the intended receiver. If the receiver receives the packet free of errors, it will return an RFacknowledge within the same 20 ms hop. If a receive acknowledgement is not received, the radio will use a transmitretry to resend the packet. The radio will continue sending the packet until either (1) an acknowledgement is receivedor (2) all transmit retries have been used. The received packet will only be sent to the OEM Host if and when it isreceived free of errors.BROADCAST PACKETSWhen sending a broadcast packet, the RF packet is sent out to every eligible transceiver on the network. To increasethe odds of successful delivery, Broadcast attempts are utilized. Transparent to the OEM Host, the sending radio willsend the RF packet to the intended receiver(s). Unlike transmit retries, all broadcast attempts are used; regardless ofwhen the RF packet is actually received and without RF acknowledgements. If the packet is received on the firstattempt, the receiver will ignore the remaining broadcast attempts. The received packet will only be sent to the OEMHost if and when it is received free of errors.Receive ModeWhen a transceiver is not in Transmit or Command mode, it will be in Receive Mode listening for data. While inReceive Mode, subsequent data of up to 80 bytes can be received every hop (20 ms).
THEORY OF OPERATION8Command ModeA radio will enter Command Mode when data is received over the serial interface from the OEM Host and either theCommand/Data pin (pin 17) is logic Low or the received data contains the “AT+++” (Enter AT Command Mode)command. Once in Command Mode, all data received by the radio is interpreted as command data. Command Datacan be either EEPROM Configuration or On-The-Fly commands.Figure 1: Pending RF and Data in Buffer FlowAPI CONTROLAPI Control is a powerful feature that the AC4490 offers. When enabled, the API Receive Packet, API Transmit Packet,API Send Data Complete and Enhanced API Receive Packet features provide dynamic packet routing and packetaccounting ability to the OEM Host, thereby eliminating the need for extensive programming on the OEM Host side.This ability of the protocol makes it ideal for any legacy system. API operation utilizes specific packet formats;Receive ModeBroadcast PacketReceive full packet and check CRC Addressed PacketMatching Destination MACValidate CRCDuplicate PacketSend RF AcknowledgeSend Packet over RFDuplicate PacketDiscard PacketDiscard PacketSend Packet over RFPending RF ReceivedYesYesYesYesYesYesReceive ModePin 17 LowData in BufferAT+++RF DataBroadcast PacketAddressed PacketTransmit PacketTransmit PacketDecrement Broadcast Attem ptsBroadcast Attempts = 0Receive ACKDecrement Transmit AttemptsTransmit Attempts = 0Command/Data Mode
9THEORY OF OPERATIONwww.aerocomm.comspecifying various vital parameters used to control radio settings and packet routing on a packet-by-packet basis.The API features can be used in any combination that suits the OEM’s specific needs.Receive API PacketImplemented in v6.3 of the firmware and later. Receive API Packet can be enabled to determine the sender of amessage. This causes the radio to append a header to the received packet detailing the length of the data packet andthe sender’s MAC address. The Receive API Packet will follow the following format.API Transmit PacketImplemented in v6.7 of the firmware and later. API Transmit Packet is a powerful command that allows the OEM Hostto send data to a single or multiple (broadcast) transceivers on a packet-by-packet basis. This can be useful for manyapplications; including polling and/or mesh networks. Refer to the API Appendix for further details.API Transmit Packet is enabled when bit-1 of the Enhanced API Control byte is enabled. The OEM Host should usethe following format to transmit a packet over the RF.1If the OEM Host does not encode the header correctly, the transceiver will send the entire string (up to 80 bytes) and will look for the header in the next data.2Although the 7 bytes of overhead are not sent over the RF, they are kept in the buffer until the packet is sent. Keep this in mind so as not to overrun the 256-byte buffer.3Setting the MAC to 0xFF 0xFF 0xFF will broadcast the packet to all available transceivers.API Send Data CompleteImplemented in v6.7 of the firmware and later. API Send Data complete can be used as a software acknowledgementindicator. When a radio sends an addressed packet, it will look for a received acknowledgement (transparent to OEMHost). If an acknowledgement is not received, the packet will be retransmitted until one is received or all retries havebeen used.API Send Data Complete is enabled when bit-2 of the Enhanced API Control byte is enabled. The transceiver sendsthe OEM Host the following data upon receiving an RF acknowledge or exhausting all attempts.1RSSI* is how strong the local transceiver heard the remote transceiver.2Successful RF Acknowledge updates the Success/Failure bit.3A success will always be displayed when sending broadcast packets after all broadcast attempts have been exhausted.API Receive PacketImplemented in v6.7 of the firmware and later. By default, the source MAC is not included in the received data stringsent to the OEM Host. For applications where multiple radios are sending data, it may be necessary to determine theorigin of a specific data packet. When API Receive Packet is enabled, all packets received by the transceiver will0x83Payload Data LengthSender’s MAC Payload Data0x81Payload Data Length (0x01 - 0x80)Aerocomm UseTransmit Retries/Broadcast AttemptsDestination MAC (2,1,0)Payload Data0x82 Aerocomm Use RSSI* 0x00: Failure0x01: Success
THEORY OF OPERATION10include the MAC address of the source radio as well as an RSSI indicator which can be used to determine the linkquality between the two.API Receive Packet is enabled when bit-0 of the Enhanced API Control byte is enabled. Upon receiving a packet theradio sends its OEM Host the packet in the following format:Note: If Enhanced Receive API is enabled, the Receive API feature should be disabled by setting EEPROM byte 0xC1to 0xFF.PROTOCOL STATUS/RECEIVE ACKNOWLEDGEMENTImplemented in v6.3 of the firmware and later. When enabled in EEPROM, GO0 and GO1 will perform the functions ofProtocol Status and Receive Acknowledgement.Protocol StatusEvery time the radio hops to hop bin 0, the radios will assert GO0 Low for the entire hop bin. GO0 will go Low at thefalling edge of the Hop Frame at the start of bin 0 and will go High with the rising edge of Hop Frame at the end of bin0. During all other hops, GO0 will be high. This mode is incompatible with modem mode.Receive AcknowledgementThe radio uses GO1 to signal that a valid RF acknowledgement has been received from the remote radio. GO1 isnormally Low and will go High within approximately 75 us of receivinng a valid RF acknowledgement. It will remainHigh until the end (rising edge) of the next hop. This mode is incompatible with Modem mode.LONG RANGE MODESpecific to the AC4490LR-200 and AC4490LR-1000 transceivers, Long Range mode increases the receiver sensitivityand range of the radio when enabled in EEPROM. Under some circumstances, such as in areas with extrememly highinterference levels, Long Range Mode may provide unsatisfactory results. In such cases, normal radio operation canbe achieved by disabling Long Range Mode; either temporarily using CC Commands or permanently by writing to theEEPROM.0x81Payload Data Length (0x01 - 0x80)Aerocomm Use RSSI* Source MAC (2,1,0)Payload DataENGINEER’S TIPWhen both API Send Data Complete and API Receive Packet are enabled, the Send DataComplete will be received before the transceiver sees the Receive API Packet. This order mayget reversed when the API Send Data Complete is missed and is being resent after the APIReceive Packet is received.
11THEORY OF OPERATIONwww.aerocomm.comNote: Long Range Mode is only available on the AC4490LR-200 and AC4490LR-1000 transceivers with the followingboard revisions and firmware v6.7+.Table 5: Long Range RequirementsModule Board Number Board RevisionAC4490LR-200 0050-00100 Rev. 1 and higherAC4490LR-1000 0050-00102 Rev. 1 and higher
www.aerocomm.comSERIAL INTERFACE4In order for the OEM Host and a transceiver to communicate over the serial interface they need to have the sameserial data rate. Refer to the following sections to ensure that the OEM Host data rate matches the serial interfacebaud rate.SERIAL COMMUNICATIONSThe AC4490 is a TTL device which can be interfaced to a compatible UART (microcontroller) or level translator to allowconnection to serial devices. UART stands for Universal Asynchronous Receiver Transmitter and its main function isto transmit or receive serial data.Asynchronous OperationSince there is no seperate clock in asynchronous operation, the receiver needs a method of synchronizing with thetransmitter. This is achieved by having a fixed baud rate and by using START and STOP bits. A typical asynchronousmode signal is shown below.Figure 2: Asynchronous Mode SignalThe UART outputs and inputs logic level signals on the TX and RX pins. The signal is high when no data is beingtransmitted and goes low when transmission begins.The signal stays low for the duration of the START bit and is followed by the data bits; LSB first. The STOP bit followsthe last data bit and is always high. After the STOP bit has completed, the START bit of the next transmission canoccur.ParityA parity bit is used to provide error checking for a single bit error. When a single bit is used, parity can be either evenor odd. Even parity means that the number of ones in the data and parity sum to an even number and vice-versa. Theninth data bit can be used as a parity bit if the data format requires eight data bits and a parity bit as shown below.
13SERIAL INTERFACEwww.aerocomm.comFigure 3: Even Parity BitNote: Enabling parity cuts throughput and the interface buffer in half.OEM HOST DATA RATEThe OEM Host Data Rate is the rate with which the OEM Host and transceiver communicate over the serial interface.This rate is independent of the RF baud rate, which is fixed at 76.8 kbps. Possible values range from 1200 bps to115,200 bps. Note: Enabling Parity cuts throughput in half and the Interface Buffer size in half. The followingasynchronous serial data formats are supported:SERIAL INTERFACE BAUD RATEThis two-byte value determines the baud rate used for communicating over the serial interface to a transceiver. TheTable below lists values for some common baud rates. Baud rates below 1200 baud are not supported. For a baudrate to be valid, the calculated baud rate must be within ±3% of the OEM Host baud rate. If the Test pin (Pin 12) ispulled logic Low at reset, the baud rate will be forced to 9,600. The RF baud rate is fixed at 76.8 Kbps and isindependent of the interface baud rate. For Baud Rate values other than those shown below, the following equationscan be used:Table 6: Supported Serial FormatsData Bits Parity Stop Bits Transceiver Programming Requirements8 N 1 Parity Disabled7 N 2 Parity Disabled7E, O, M, S 1Parity Disabled9 N 1 Parity Enabled8 N 2 Parity Enabled8E, O, M, S 1Parity Enabled7E, O, M, S 2Parity EnabledMark (M) corresponds to 1 & Space (S) corresponds to 0
SERIAL INTERFACE14INTERFACE TIMEOUT / RF PACKET SIZEInterface Timeout (EEPROM address 0x58), in conjunction with RF Packet Size (EEPROM address 0x5B), determineswhen a buffer of data will be sent out over the RF as a complete RF packet, based on whichever condition occurs first.Interface Timeout – Interface Timeout specifies a maximum byte gap between consecutive bytes. When that byte gapis exceeded, the bytes in the transmit buffer are sent out over the RF as a complete packet. Interface Timeout isadjustable in 0.5ms increments and has a tolerance of ±0.5ms. Therefore, the Interface Timeout should be set to aminimum of 2. The default value for Interface Timeout is 0x04 (2ms) and should be adjusted accordingly whenchanging the transceiver baud rate.RF Packet Size – When the number of bytes in the transceiver transmit buffer equals RF Packet Size, those bytes aresent out as a complete RF packet. It is much more efficient to send a few large packets rather than several shortpackets as every packet the transceiver sends over the RF contains extra header bytes which are not included in theRF Packet Size. RF packet size can be set to a maximum of 0x50 (80 bytes) and must be set to a minimum of 0x06 inorder to send the Enter AT Command mode command. To change the RF packet size from the default value, AutoConfig must be disabled and the appropriate Auto Config parameters must be changed.Table 7: Baud Rate / Interface TimeoutBaud Rate BaudL (0x42)BaudH (0x43)Minium Interface Timeout (0x58) Stop Bit Delay (0x3F)115,200 0xFE 0x00 0x02 0xFF57,60011. 57,600 is the default baud rate0xFC 0x00 0x02 0x0338,400 0xFA 0x00 0x02 0x0828,800 0xF8 0x00 0x02 0x0E19,200 0xF4 0x00 0x03 0x1914,400 0xF0 0x00 0x04 0x239,600 0xE8 0x00 0x05 0x394800 0xD0 0x00 0x09 0x7A2400 0xA0 0x00 0x11 0xFC1200 0x40 0x00 0x21 0x0022. 0x00 will yield a stop bit of 421 uS. The stop bit at 1200 baud should actually be 833 uS.BAUD 14.7456 6×1064 DesiredBaud×-----------------------------------------------=BaudH Always 0=BaudL Low 8 bits of BAUD (base 16)=
15SERIAL INTERFACEwww.aerocomm.comFLOW CONTROLFlow control refers to the control of data flow between transceivers. It is the method used to handle data in thetransmit/receive buffer and determines how data flow between the transceivers is started and stopped. Often, onetransceiver is capable of sending data much faster than the other can receive and flow control allows the slowerdevice to tell the faster device when to pause and resume data transmission.When a transceiver has data to send, it sends a Ready To Send signal and waits for a Clear To Send response fromthe receiving unit. If the receiving radio is ready to accept data it will assert its CTS low. CTS will be reasserted whenthe buffer contains the number of bytes specified by CTS_OFF (EEPROM address 0x5D). These signals are sentapart from the data itself on separate wires.HALF DUPLEX / FULL DUPLEXWhen Half Duplex communication is chosen, the AC4490 will send a packet out over the RF whenever it can. This cancause packets sent by multiple transceivers at the same time to collide with each other over the RF. To prevent this,Full Duplex communication can be chosen. Full Duplex shares the bandwidth intelligently to enable two-waycollision-free communication without any collision. This is done by calculating the amount of time until the next hop toensure that it has time to send the packet; if there is enough time, it will send the packet and if not, it will wait until itsnext appropriate hop. The Server transmits during the even hops while the Client(s) will transmit during the odd hops.Although the RF hardware is still technically half duplex, the bandwidth sharing it makes the transceiver seem fullduplex. Enabling Full Duplex can cause overall throughputs to be cut in half.SYSTEM TIMING & LATENCYCare should be taken when selecting transceiver architecture, as it can have serious effects on data rates, latency,and overall system throughput. The importance of these three characteristics will vary from system to system andENGINEER’S TIPCan I implement a design using just Txd, Rxd and Gnd (Three-wire Interface)?Yes. However, it is strongly recommended that your hardware monitor the CTS pin of theradio. CTS is taken High by the radio when its interface buffer is getting full. Your hardwareshould stop sending at this point to avoid a buffer overrun (and subsequent loss of data).You can perform a successful design without monitoring CTS. However, you need to take intoaccount the amount of latency the radio adds to the system, any additional latency caused byTransmit Retries or Broadcast Attempts, how often you send data, non-delivery networktimeouts and interface data rate. Polled type networks, where the Server host requests datafrom the Client host and the Client host responds, are good candidates for avoiding the use ofCTS. This is because no one transceiver can monopolize the RF link. Asynchronous typenetworks, where any radio can send to another radio at any point in time, are much moredifficult to implement without the use of CTS.
SERIAL INTERFACE16should be a strong consideration when designing the system.SYSTEM THROUGHPUTWhen operating as shown below, an AC4490 transceiver is capable of achieving the listed throughput. However, inthe presence of interference or at longer ranges, the transceiver may be unable to meet the specified throughput.ENGINEER’S TIPIn High-density applications, what amount of latency should be expected?It is not easy to predict the exact amount of latency in high-density applications. There aremany variables that affect system latency. The three variables that most affect the latency arethe network load, the distance between transceivers, and whether the transceivers areoperating in a broadcast or addressed mode. There is no fixed answer as to how much latencywill be introduced in the system when considering high-density applications. In these caseswe can just offer qualitative analysis of the latency in high-density applications. As the networkload increases, then the number of collisions that will occur increases. As the number ofcollisions increase, then the system latency increases. As the distance between thetransceivers increases, so to does the system latency. Finally, when transceivers operate inaddressed mode they will retry sending a packet up to the number of time specified in thetransmit retry parameter specified in the EEPROM. As the number of retries increases, thesystem latency will increase also.Table 8: Maximum System ThroughputOne Beacon Mode Parity Mode Half Duplex Throughput (bps)Full Duplex Throughput (bps) each wayDisabled Disabled 38k 19kEnabled Disabled 48k 24kDisabled Enabled 19k 9.5kEnabled Enabled 24k 12k
www.aerocomm.comSOFTWARE INTERFACE5NETWORKINGSystem ID - System ID (EEPROM address 0x76) is similar to a password character or network number and makesnetwork eavesdropping more difficult. A transceiver will not establish a Session or communicate with a transceiveroperating on a different System ID or Channel Number.RF Channel Number - Channels 0x00 - 0x0F and 0x30 - 0x37 hop on 26 different frequencies. Channels 0x10 - 0x2Fuse 50 different frequencies.Auto Channel - To allow for more flexible network configurations, Auto Channel can be enabled on Client transceiversto allow them to automatically synchronize with the first Server they hear a beacon from, regardless of the Server’sChannel Number or signal strength. Note: A Client with Auto Channel enabled will only synchronize with a Serveroperating in the same Channel set and with the same System ID.DES (Data Encryption Standard) - DES (Data Encryption Standard) – Encryption is the process of encoding aninformation bit stream to secure the data content. The DES algorithm is a common, simple and well-establishedencryption routine. An encryption key of 56 bits is used to encrypt the packet. The receiver must use the exact samekey to decrypt the packet; otherwise garbled data will be produced.To enable DES, EEPROM Byte 0x45, bit 6 must be set to a value of 1. To disable DES, set bit 6 to a value of 0. The 7byte (56 bits) Encryption/Decryption Key is located in EEPROM Bytes 0xD0 – 0xD6. It is highly recommended that thisKey be changed from the default.Sync to Channel - The AC4490 is a frequency hopping transceiver with a fixed hopping sequence. Withoutsynchronizing their frequency hopping, collocated systems on different channels can interfere with each other. Toavoid this, sync-to-channel can be used to synchronize the collocated Servers. A Server transceiver with sync-to-channel enabled must have its Sync Channel set to another Server’s RF Channel number. It is required that a Serverwith sync-to-channel enabled have its sync channel set to a value less than its RF Channel number. Collocatednetworks using sync-to-channel must use the same channel set.Note: If Server A (with sync-to-channel enabled) cannot synchronize to Server B (on the sync channel), Server A willnot be able to communicate with its Clients and must wait until it synchronizes with Server B (at which point In_RangeTable 9: RF Channel Number SettingsChannel Set11. All Channels in a Channel Set use the same frequencies in a different order.RF Channel Number Range (0x40)Frequency Details & Regulatory requirements Countries0 (AC4490 - 1x1 AC4490 - 200)0x00 - 0x0F 902 - 928 MHz (26 hop bins) US / Canada1 (AC4490 - 1x1 AC4490 - 1000)0x10 - 0x2F 902 - 928 MHz (50 hop bins) US / Canada2 (AC4490 - 1x1 AC4490 - 200 AC4490 - 1000)0x30 - 0x37 915 - 928 MHz (26 hop bins) US / Canada (-1x1 / -200)Australia(-1x1/-200/-1000)
SOFTWARE INTERFACE18will be asserted), before establishing communications. Server B will not be affected and can communicate with itsClients.Refer to the Sync-to-Channel Appendix for further details and sample configuration.ONE BEACON MODE / RANGE REFRESHOne Beacon - The 4490 maintains synchronization by using the timing information in the Server’s beacon. Thisbeacon lasts approximately 1 ms and by default is sent by the Server at the beginning of every hop to the particularfrequency that the Server is hopping on. If One Beacon mode is enabled, the 1 ms synchronization pulse is sent onlyonce per complete hop cycle. For example, a Server operating in Channel Set 1 (channels 0x10 - 0x2F) hops on 50frequencies at 20 ms per frequency. Assuming that the Client hears the beacon on the first attempt, it can take up to1 second (50 hops x 20 ms per hop) for a Client to hear the beacon and report In_Range.Using One Beacon mode can make initial synchronization take longer and can make communications more difficult ifoperating on the fringe but can increase net throughput.Range Refresh - Range Refresh specifies the maximum amount of time a Client reports in range without having hearda beacon from the Server. Each time the Client hears a beacon, it resets its Range Refresh timer. If the timer reacheszero, the Client will go out of range, take its In_Range pin High and enter aquisition mode attempting to find the Serveronce again. The range refresh is equal to the hop period (20 ms) x Range refresh value. Note: Range Refresh should not be set to 0x00.AUTO CONFIG PARAMETERSThe AC4490 has several variables that vary by RF mode and architecture. By default, Auto Config is enabled andbypasses the values stored in EEPROM and uses predetermined values for the given operating mode. Below is a listof the variables controlled by Auto Config and their respective predetermined values. If Auto Config is disabled, thesevalues must be programmed in the transceiver EEPROM for the corresponding mode of operation.Table 10: One Beacon Mode SettingsEEPROM Address One Beacon Mode Enabled One Beacon Mode Disabled0x45 Set bit 7 Clear bit 70x3C 0x18 0x280x3D Channels 0x10 - 0x2F: 0xC8All other Channels: 0x680x18Table 11: Auto Config ParametersParameter EEPROMAddress Default One Beacon Mode DisabledOne Beacon Mode Enabled0x36 0x66 0xA0 0xA00x47 0x0E 0x0E 0x0E0x48 0x90 0x90 0x90
19SOFTWARE INTERFACEwww.aerocomm.comINTERFACE OPTIONSModem ModeFull modem handshaking is supported by the AC4490 when enabled in EEPROM. Modem mode is incompatible withRS-485 DE. The line states are updated a maximum of once per 20 ms and only change when toggled by theappropriate line on the remote radio. Because Command/Data performs an alternate function when modem mode isenabled, on-the-fly CC Commands cannot be used and Configuration Mode is entered by forcing 9600 baud throughthe 9600_Baud pin (pin 12). Therefore, modem mode is disabled when the radio is forced to 9600 baud. Bothmodem interfaces are shown in the tables below.0x4E 0x09 0x09 0x090x53 0x80 0x80 0x800x54 0x07 0x07 0x07RF Packet Size 0x5B 0x46 0x50 0x68CTS On 0x5C 0xD2 0xDC 0xDCCTS Off 0x5D 0xAC 0xB0 0xB00x5E 0x23 0x23 0x230x5F 0x08 0x08 0x08Table 12: Transceiver Interface to DCE (Server)DCE Pin Number DCE Pin NameDirection with respect to transceiverAC4490 Pin Name AC4490 Pin Number1DCD In GI1 142RXD In RXD 33TXD Out TXD 24DTR Out GO0 15GND -GND 56DSR In Command/Data 177RTS Out CTS 78CTS In RTS 89RI In GI0 4Table 11: Auto Config ParametersParameter EEPROMAddress Default One Beacon Mode DisabledOne Beacon Mode Enabled
SOFTWARE INTERFACE20RS-485 DE Control - When enabled in EEPROM, the transceiver will use the GO0 pin to control the DE pin on externalRS-485 circuitry. If enabled, when the transceiver has data to send to the host, it will assert GO0 High, send the datato the Host and then take GO0 Low.RS485 Modem ModeThis mode is only useful for customers that wish to use RS485 DE in conjunction with standard Modem Mode. Whenenabled in EEPROM in conjunction with Modem Mode, allows modem control lines over the RF. This mode shouldonly be used when RS485 DE is also being used. For all other applications, standard Modem Mode is preferred.Available Modem control lines when RS485 Modem Mode is enabled:• Command/Data on Server controls Hop Frame on Client• GI1 on Server controls GO1 on ClientMAX POWERMax Power provides a means for controlling the RF output power of the AC4790. Output power and currentconsumption can vary by as much as ±10% per transceiver for a particular Max Power setting. Contact AeroCommfor assistance in adjusting Max Power. Table 13: Transceiver Interface to DTE (Client)DTE Pin Number DTE Pin NameDirection with respect to transceiverAC4490 Pin Name AC4490 Pin Number1DCD Out GO0 12RXD Out TXD 23TXD In RXD 34DTR In GI0 45GND -GND 56DSR Out Hop Frame 67RTS In RTS 78CTS Out CTS 89RI Out G01 9ENGINEER’S TIPThe max power is set during Production and may vary slightly from one transceiver to another.The max power can be set as low as desired but should not be set higher than the originalfactory setting. A backup of the original power setting is stored in EEPROM address 0x8E.
www.aerocomm.comTIMING DIAGRAMS6AC4490 TIMING DIAGRAMSFigure 4: Addressed Mode with TimeoutFigure 5: Addressed Mode with Fixed Packet Length
TIMING DIAGRAMS22Figure 6: Broadcast Mode with TimeoutFigure 7: Broadcast Mode with Fixed Packet Length
www.aerocomm.comHARDWARE INTERFACE7Below is a description of all hardware pins used to control the AC4490.PIN DEFINITIONSGeneric I/OBoth GIn pins serve as generic input pins and both GOn pins server as generic output pins. Reading and writing ofthese pins can be performed using CC Commands. These pins alternatively serve as control pins when modemmode is enabled.TXD & RXDSERIAL TTLThe AC4490-200 accepts 3.3 or 5VDC TTL level asynchronous serial data on the RXD pin and interprets that data aseither Command Data or Transmit Data. Data is sent from the transceiver, at 3.3V levels, to the OEM Host via the TXDpin. Note: The AC4490-1000 & AC4490-1x1 transceivers ONLY accept 3.3V level signals.RS-485When equipped with an onboard RS-485 interface chip, TXD and RXD become the half duplex RS-485 pins. Thetransceiver interface will be in Receive Mode except when it has data to send to the OEM Host. TXD is the non-inverted representation of the data (RS485A) and RXD is a mirror image of TXD (RS485B). The transceiver will still useRTS (if enabled).Hop FrameTransitions logic Low at the start of a hop and transitions logic High at the completion of a hop. The OEM Host is notrequired to monitor Hop Frame.CTSThe AC4490 has an interface buffer size of 256 bytes. If the buffer fills up and more bytes are sent to the transceiverbefore the buffer can be emptied, data loss will occur. The transceiver prevents this loss by asserting CTS High as thebuffer fills up and taking CTS Low as the buffer is emptied. CTS On and CTS Off control the operation of CTS. CTS Onspecifies the amount of bytes that must be in the buffer for CTS to be disabled (logic High). Even while CTS isdisabled, the OEM Host can still send data to the transceiver, but it should do so carefully. Note: The CTS On/Off bytes of the EEPROM can be set to 1, in which case CTS will go high as data is sent in and lowwhen buffer is empty.GNDSignal Ground. Pins are internally connected.RTSWith RTS disabled, the transceiver will send any received data to the OEM Host as soon as it is received. However,some OEM Hosts are not able to accept data from the transceiver all of the time. With RTS enabled, the OEM Host can
HARDWARE INTERFACE24prevent the transceiver from sending it data by disabling RTS (logic High). Once RTS is enabled (logic Low), thetransceiver can send packets to the OEM Host as they are received. Note: Leaving RTS disabled for too long can cause data loss once the transceiver’s 256 byte receive buffer fills up.Test / 9600 BaudWhen pulled logic Low before applying power or resetting, the transceiver’s serial interface is forced to a 9600, 8-N-1(8 data bits, No parity, 1 stop bit). To exit, the transceiver must be reset or power-cycled with Test pin logic High. Thispin is used to recover transceivers from unknown baud rates only. It should not be used in normal operation. Insteadthe transceiver Interface Baud Rate should be programmed to 9600 baud if that rate is desired for normal operation.RSSIINSTANTANEOUS RSSIReceived Signal Strength Indicator is used by the OEM Host as an indication of instantaneous signal strength at thereceiver. The OEM Host must calibrate RSSI without an RF signal being presented to the receiver. Calibration isaccomplished by following the steps listed below.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 another transceiver and begin sending data from that transceiver to the transceiver being measured.Make sure the two transceivers are separated by approximately ten feet.4) Measure the peak RSSI, while the transceiver is in Session, to obtain a maximum value at full signal strength.VALIDATED RSSIAs RSSI is only valid when the local transceiver is receiving an RF packet from a remote transceiver, instantaneousRSSI can be very tricky to use. Therefore, the transceiver stores the most recent valid RSSI value. The OEM Hostissues the Report Last Good RSSI command to request that value. Additionally, validated RSSI can be obtained fromReceive Packet and Send Data Complete API commands and from the Probe command. Validated RSSI is notavailable at the RSSI pin. The following equation approximates the RSSI curve:ENGINEER’S TIPAerocomm does not recommend permantly grounding the Forced_9600 pin. This mode wasintended for recovering transceivers from unknown settings and was not intended to be usedin real-time communications. The following modes are affected:Modem mode = disabledParity mode = disabledInterface Timeout = 0x40It is also possible that future modes not yet implemented will be disabled by groundingForced_9600.Signal Strength (dBm) = (-46.9 VRSSI)× 53.9–
25HARDWARE INTERFACEwww.aerocomm.comFigure 8: RSSI Voltage vs. Received Signal StrengthUP_ResetUP_Reset provides a direct connection to the reset pin on the AC4490 microprocessor and is used to force a softreset.Command/DataWhen logic High, the transceiver interprets incoming OEM Host data as transmit data to be sent to other transceiversand their OEM Hosts. When logic Low, the transceiver interprets OEM Host data as command data.AD InAD In can be used as a cost savings to replace Analog-to-Digital converter hardware. Reading of this pin can beperformed locally using the Read ADC command found in the On-the-Fly Control Command Reference.In RangeReports logic Low when a Client transceiver is in range of a Server radio operating on the same RF Channel andsystem ID. If a Client cannot hear a Server for the amount of time defined by Range Refresh, it will drive In_RangeHigh and enter search mode looking for a Server. When a server is detected, In_Range will be asserted Low.In_Range will always report Low on Server transceivers. 00.20.40.60.811.2-105 -100 -95 -90 -85 -80 -75 -70 -65 -60 -55 -50Signal at Receiver (dBm)Voltage (VDC)
www.aerocomm.comCONFIGURING THE AC44908The AC4490 can be configured using the CC Configuration Commands. The CC Commands can be issued usingeither Hardware or Software Configuration. To use Hardware Configuration, pin 17 of a transceiver must be assertedLow. Software Configuration can be used by entering AT Command Mode before issuing the CC Commands.Figure 9: AC4490 Configuration FlowUse AT CommandsReceive ModeTake Pin 17 Low (Hardware Configuration)AT+++ (Software Configuration)Send CC Commands Exit Command ModeIn AT Command ModeSend CC CommandSend Another CC CommandSend Exit AT Command Mode Command Take Pin 17 HighNoNoNo NoNo
27CONFIGURING THE AC4490www.aerocomm.comAT COMMANDSThe AT Command mode implemented in the AC4490 creates a virtual version of the Command/Data pin. The “EnterAT Command Mode” Command asserts this virtual pin Low (to signify Command Mode) and the “Exit AT CommandMode” Command asserts this virtual pin High (to signify Data). Once this pin has been asserted Low, all On-the-FlyCC Commands documented in the manual are supported.On-the-Fly Control CommandsThe AC4490 transceiver contains static memory that holds many of the parameters that control the transceiveroperation. Using the “CC” command set allows many of these parameters to be changed during system operation.Because the memory these commands affect is static, when the transceiver is reset, these parameters will revert backto the settings stored in the EEPROM. While in CC Command mode using pin 17 (Command/Data), the RF interfaceof the transceiver is still active. Therefore, it can receive packets from remote transceivers while in CC Commandmode and forward these to the OEM Host.COMMAND/DATA RX DISABLEThe Command/Data RX Disable feature can be enabled in firmware versions 8.6+. When enabled in EEPROM, theradio disables the RF receiver while pin 17 (Command/Data) is Low. To ensure that the radio is not in the middle oftransmitting data to the OEM Host, the host should be prepeared to receive data for up to 20 ms after taking pin 17Low.AT COMMAND MODEWhile in CC Command mode using AT Commands, the RF interface of the transceiver is active, but packets sent fromother transceivers will not be received. The transceiver uses Interface Timeout/RF Packet Size to determine when aCC Command is complete. Therefore, there should be no delay between each character as it is sent from the OEMHost to the transceiver or the transceiver will not recognize the command. If the OEM Host has sent a CC Commandto the transceiver and an RF packet is received by the transceiver, the transceiver will send the CC Commandresponse to the OEM Host before sending the packet. However, if an RF packet is received before the InterfaceTimeout expires on a CC Command, the transceiver will send the packet to the OEM Host before sending the CCCommand response.When an invalid command is sent, the radio scans the command to see if it has a valid command followed by bytesnot associated with the command, in which case the radio discards the invalid bytes and accepts the command. In allother cases, the radio returns the first byte of the invalid command back to the user and discards the rest.
CONFIGURING THE AC449028Table 14: Command Quick ReferenceCommand Name Command (All Bytes in Hex) Return (All Bytes in Hex)AT EnterCommandMode0x41 0x54 0x2B 0x2B 0x2B 0x0D 0xCC 0x43 0x4F 0x4DExit AT Command-Mode0xCC 0x41 0x54 0x4F 0x0D -0xCC 0x44 0x41 0x54Status Request 0xCC 0x00 0x00 - - - 0xCC FirmwareVersion0x00: Server0x01: Client in range0x03: Client out of rangeChange Channel 0xCC 0x02 New Channel - - 0xCC New Channel -Change Server/Client 0xCC 0x03 0x00: Server0x03: Client- - 0xCC FirmwareVersion0x00: Server0x03: ClientChange SyncChannel0xCC 0x05 New SyncChannel- - 0xCC New Sync Channel- -Sleep Walk Power Down0xCC 0x06 - - - - 0xCC Channel - -Sleep Walk Wake Up 0xCC 0x07 - - - - 0xCC Channel -BroadcastPackets0xCC 0x08 0x00: Broadcast0x01: Addressed-0xCC 0x00 or 0x01 - -Write Destination Address0xCC 0x10 Byte 4 of Dest. MACByte 5 Byte 60xCC Byte 4 of Dest. MACByte 5 Byte 6Read Destination Address0xCC 0x11 - - - - 0xCC Byte 4 of Dest. MACByte 5 Byte 6Forced Calibration 0xCC 0x12 0x00 0x00 - - 0xCC Firmware Version0x00: Server in Normal Operation0x01: Client in Normal Operation0x02: Server in Acquisition Sync0x03: Client in Acquisition SyncAuto Destination 0xCC 0x15 bit-0: Auto Destinationbit-1: Auto Channelbit-4: Enable Auto Destinationbit-5: Enable Auto Channel0xCC bit-0: Auto Destinationbit1: Auto Channelbits-2-7: 0Read Digital Inputs 0xCC 0x20 - - - - 0xCC bit-0: GI0bit-1: GI1- -Read ADC 0xCC 0x21 0x01: AD In0x02: Temp0x03: RSSI- - 0xCC MSB of 10 bit ADCLSB of 10 bit ADCReport Last Valid RSSI 0xCC 0x22 - - - - 0xCC RSSI - -Write Digital Outputs0xCC 0x23 bit-0: GO0bit-1: GO1- - 0xCC bit-0: GO0bit-1: GO1- -Write DAC 0xCC 0x24 Update PeriodDuty Cycle- - 0xCC Update Period Duty Cycle-
29CONFIGURING THE AC4490www.aerocomm.comSet Max Power 0xCC 0x25 New Max Power -0xCC Max Power - -Report Last Packet RSSI0xCC 0x26 - - - - 0xCC RSSI - -Long Range Mode10xCC 0x27 0x00: Normal Mode (Disabled)0x01: Long Range Mode (Enabled)0xCC 0x00: Normal Mode (Disabled)0x01: Long Range Mode (Enabled)Transmit Buffer Empty 0xCC 0x30 - - - - 0xCC 0x00 - -Disable Sync to Channel0xCC 0x85 - - - - 0xCC Channel - -Deep Sleep Mode 0xCC 0x86 - - - - 0xCC Channel - -Enter Probe 0xCC 0x8E 0x00: Enter Probe0x01: Exit Probe-0xCC 0x00 or 0x01 - -Read Temperature 0xCC 0xA4 - - - - 0xCC Temp (C) - -Read Temperature at last calibration0xCC 0xA5 - - - - 0xCC Temp (C)EEPROM Byte Read 0xCC 0xC0 Start Address Length 0xCC Starting AddressLength DataEEPROM Byte Write 0xCC 0xC1 Start Address Length Data Starting Address Length Data writtenSoft Reset 0xCC 0xFF - - - - - - - -1. Available only on AC4490LR-200 and AC4490LR-1000 transceivers.Table 14: Command Quick ReferenceCommand Name Command (All Bytes in Hex) Return (All Bytes in Hex)
CONFIGURING THE AC449030COMMAND DESCRIPTIONSEnter AT Command ModePrior to sending this command, the OEM Host must ensure that thetransceiver’s RF transmit buffer is empty. If the buffer is not empty, theradio will interpret the command as data and it will be sent over the RF.This can be accomplished by waiting up to one second between thelast packet and the AT command.Command: 0x41 0x54 0x2B 0x2B 0x2B 0x0DNumber of Bytes Returned: 4Response: 0xCC 0x43 0x4F 0x4DExit AT Command ModeThe OEM Host should send this command to exit AT Command modeand resume normal operation.Command: 0xCC 0x41 0x54 0x4F 0x0DNumber of Bytes Returned: 4Response: 0xCC 0x44 0x41 0x54Status RequestThe OEM Host issues this command to request the status of thetransceiver.Command: 0xCC 0x00 0x00Number of Bytes Returned: 3Response: 0xCC <Version> <Radio State>Parameter Range: Radio State = 0x00 for Server, 0x01 forClient in Range, 0x03 for Client out of RangeChange ChannelThe OEM Host issues this command to change the channel of thetransceiver.Command: 0xCC 0x02 <Channel>Number of Bytes Returned: 2Response: 0xCC <Channel>Change Server/ClientThe OEM Host issues this command to change the mode of thetransceiver from Server to Client and vice versa.Command: 0xCC 0x03 Data1Number of Bytes Returned: 3Response: 0xCC <Version> <Mode>Parameter Range: Mode = 0x00 for Server, 0x03 for ClientChange Sync ChannelThe OEM Host issues this command to change the sync channel byteand enable sync to channel.Command: 0xCC 0x05 <Channel>Number of Bytes Returned: 3Response: 0xCC 0x05 <Channel>
31CONFIGURING THE AC4490www.aerocomm.comSleep Walk Power-DownAfter the Host issues this command, the transceiver will de-assert itsIn_Range line after entering power down. A Client in power down willremain in sync with a Server for a minimum of 2 minutes. To maintainsyncronization with the Server, the Client should re-sync at least onceevery 2 minutes. This is done by sending the Power Down wake upcommand and waiting for the In_Range line to go active. Once thisoccurs, the Client is in sync with the server and can be put back intopower-down mode. This command is valid only for Client transceivers.Command: 0xCC 0x06Number of Bytes Returned: 2Response: 0xCC <Channel>Sleep Walk Power-Down Wake UpThe OEM Host issues this command to bring the transceiver out ofPower Down mode.Command: 0xCC 0x07Number of Bytes Returned: 2Response: 0xCC <Channel>Broadcast PacketsThe OEM Host issues this command to change the transceiveroperation between Addressed Packets and Broadcast Packets. IfAddressed Packets are selected, the transceiver will send all packets tothe transceiver designated by the Destination Address programmed inthe transceiver. If Broadcast Packets are selected, the transceiver willsend its packets to all transceivers on that network. Setting bit-7 of APIControl to 1 can also enable Broadcast Packets.Command: 0xCC 0x08 <Addressing Mode>Number of Bytes Returned: 2Response: 0xCC <Addressing Mode>Parameter Range: Addressing Mode = 0x00 for Addressed,0x01 for BroadcastWrite Destination AddressThe OEM Host issues this command to the transceiver to change theDestination Address. Note: Only the three Least Significant Bytes of the MAC Address areused for packet delivery.Command: 0xCC 0x10 MAC3 MAC2 MAC1Number of Bytes Returned: 4Response: 0xCC MAC3 MAC2 MAC1Parameter Range: 0x00 - 0xFF corresponding to 3 LSB’s ofdestination MAC AddressRead Destination AddressThe OEM Host issues this command to the transceiver to read thedestination address.Note: Only the three Least Significant Bytes of the MAC Address areused for packet delivery.Command: 0xCC 0x11Number of Bytes Returned: 4Response: 0xCC MAC3 MAC2 MAC1Parameter Range: 0x00 - 0xFF corresponding to 3 LSB’s ofdestination MAC AddressForced CalibrationThe OEM Host issues this command to force a recalibration to occur.During the recalibration, the radio will assert CTS high. Recalibrationcan take up to 3 seonds and the command response will not be sent tothe OEM Host until recalibration is complete.Command: 0xCC 0x12 0x00 0x00Number of Bytes Returned: 3Response: 0xCC <Version> <Radio State>Parameter Range: Radio State = 0x00 for Server in range,0x01 for Client in range, 0x02 for Server out of range, 0x03 forClient out of range
CONFIGURING THE AC449032Auto DestinationThe Host issues this command to change the Auto Destination & AutoChannel settings. When issuing this command, the AutoDestination/Auto Channel settings will only be changed if thecorresponding enable bit is set (Control1 Parameter, EEPROM address0x56, bits-4,5)Command: 0xCC 0x15 <Data1>Number of Bytes Returned: 2Response: 0xCC <Data2>Parameter Range: Data1 = bit-0: Auto Destination, bit-1: AutoChannel, bit-4: Enable Auto Destination modification, bit-5:Enable Auto Channel Modification; Data2 = bit-0: New AutoDestination setting, bit-1: New Auto Channel Setting, bits 2 -7:0Read Digital InputsThe OEM Host issues this command to read the state of both digitalinput lines.Command: 0xCC 0x20Number of Bytes Returned: 2Response: 0xCC <Data1>Parameter Range: Data1 = bit-0: GI0, bit-1: GI1Read ADCThe OEM Host issues this command to read any of the three onboard10-bit A/D converters. Because the RF is still active in On-the-FlyCommand Mode, the transceiver will not process the command untilthere is no activity on the network. The Read RSSI command istherefore useful for detecting interfering sources but will not report theRSSI from a remote transceiver on the network. The equations forconverting these 10 bits into analog values are as follows:Analog Voltage = (10 bits / 0x3FF) * 3.3VTemperature (oC) = ((Analog Voltage - 0.3) / 0.01) - 30RSSI value (dBm) = -105 + (0.22 * (0x3FF - 10 bits))Command: 0xCC 0x21 <Data1>Number of Bytes Returned: 3Response: 0xCC <Data2> <Data3>Parameter Range: Data1 = 0x00: AD In, 0x01: Temperature,0x02: RSSI; Data2 = MSB of requested 10-bit ADC value;Data3 = LSB of requested 10-bit ADC valueReport Last Valid RSSISince RSSI values are only valid when the local transceiver is receivingan RF packet from a remote transceiver, instantaneous RSSI can betricky to use. Therefore, the transceiver stores the most recent validRSSI value as measured the last time the transceiver received a packetor beacon. The Host issues this command to retrieve that vale. Note: This value will default to 0xFF on a Client and 0x00 on a Server ifno valid RSSI measurement has been made since power-up.Command: 0xCC 0x22Number of Bytes Returned: 2Response: 0xCC <Last Valid RSSI>Table 15: Received Signal StrengthSignal Strength (dBm) RSSI Value (Hex) Signal Strength (dBm) RSSI Value (Hex)40x0E -62 0x2B-2 to 1 0x0D -66 0x40-12 to -6 0x0C -69 0x55-36 to -22 0x0B -72 0x62
33CONFIGURING THE AC4490www.aerocomm.com-42 to -39 0x0C -76 0x71-46 0x0D -79 0x78-49 0x0E -82 0x84-52 0x11 -86 0x9A-56 0x17 -89 0xAD-59 0x1C -92 0xBDWrite Digital OutputsThe OEM Host issues this command to write both digital output lines toparticular states.Note: This command should only be used when Protocol Status (0xC2)is not set to 0xE3.Command: 0xCC 0x23 <Data1>Number of Bytes Returned: 2Response: 0xCC <Data1>Parameter Range: Data1 = bit-0: GO0, bit-1: GO1Write DACThe OEM Host issues this command to write DA_Out to a particularvoltage. The transceiver uses a PWM (Pulse Width Modulator) togenerate the analog voltage. The theory behind a PWM is that a binarypulse is generated with a fixed duty cycle and rate. As such, this pintoggles between High & Low. This signal is filtered via an on-board R-Ccircuit and an analog voltage is generated. Duty cycle specifies theratio of time in one cycle that the pulse spends High proportionate tothe amount of time it spends Low. So, with a duty cycle of 50% (0x80),the pulse is High 50% of the time and Low 50% of the time; therefore theanalog voltage would be half of 3.3V or 1.15V. A broad filter has beenimplemented on the transceiver and there is no advantage to using aslower update period. Generally, a faster update period is preferred.Command: 0xCC 0x24 <Data1> <Data2>Number of Bytes Returned: 3Response: 0xCC <Data1> <Data2>Parameter Range: Data1 = Update Period; Data2 = DutycycleSet Max PowerThe OEM Host issues this command to limit the maximum transmitpower emitted by the transceiver. This can be useful to minimizecurrent consumption and satisfy certain regulatory requirements. Theradios are shipped at maximum allowable power.Command: 0xCC 0x25 <Max Power>Number of Bytes Returned: 2Response: 0xCC <Max Power>Long Range ModeThe OEM Host issues this command to temporarily enable or disableLong Range Mode in the transceiver.Note: Only available on AC4490LR-200 / AC4490LR-1000 transceiverswith firmware v6.7+.Command: 0xCC 0x27Number of Bytes Returned: 2Response: 0xCC <Data1>Parameter Range: Data1 = 0x00: Disabled, 0x01: EnabledTable 15: Received Signal StrengthSignal Strength (dBm) RSSI Value (Hex) Signal Strength (dBm) RSSI Value (Hex)Tupdate 255 Data1 1+()×()14.74566--------------------------------------------------=Vout Data20xFF--------------- 3.3V×=
CONFIGURING THE AC449034Transmit Buffer EmptyThe OEM Host issues this command to determine when the RF transmitbuffer is empty. The Host will not receive the transceiver response untilthat time.Command: 0xCC 0x30Number of Bytes Returned: 2Response: 0xCC 0x00Disable Sync-to-ChannelThe OEM Host issues this command to disable Sync to Channel mode.This command is valid only for Servers.Command: 0xCC 0x85Number of Bytes Returned: 2Response: 0xCC <Channel>Deep Sleep ModeThe OEM Host issues this command to put the transceiver into DeepSleep mode. Once in Deep Sleep mode, the transceiver disables all RFcommunications and will not respond to any further commands untilbeing reset or power-cycled. This command is valid for both Servers and Clients.Command: 0xCC 0x86Number of Bytes Returned: 2Response: 0xCC <Channel>Read TemperatureThe OEM Host issues this command to read the onboard temperaturesensor. The transceiver reports the temperature in oC where 0x00 -0x80 corresponds to 0 - 80 oC and where 0xD8 - 0x00 corresponds to -40 - 0 oC.Command: 0xCC 0xA4Number of Bytes Returned: 2Response: 0xCC <Temperature>Parameter Range: Temperature = 0xD8 - 0x80Read Temperature at Last CalibrationThe OEM Host issues this command to read the temperature of theradio at the time of its last calibration. The transceiver reports thetemperature in oC where 0x00 - 0x80 corresponds to 0 - 80 oC andwhere 0xD8 - 0x00 corresponds to -40 - 0 oC.Command: 0xCC 0xA5Number of Bytes Returned: 2Response: 0xCC <Temperature>Parameter Range: Temperature = 0xD8 - 0x80ProbeWhen the OEM Host issues this command, the transceiver sends out aquery every 500 ms. The transceivers, upon receiving the query,randomly choose a query to respond to. After responding to a Probe,the transceiver will wait at least 10 seconds before responding toanother probe.Note: This command can only be sent from a server radio.Transceiver’s ResponseUpon hearing the remote transceiver’s probe acknowledge, thetransceiver sends a response to the OEM Host.Command: 0xCC 0x8E <Data1>Number of Bytes Returned: 2Response: 0xCC <Data1>Parameter Range: 0x00 = Disable Probe, 0x01 = EnableProbeCommand: N/ANumber of Bytes Returned: 5Response: 0xCC Data1 MAC3 MAC2 MAC1Parameter Range: Data 1 = bit-7: 0 for Client, bit-7: 1 forServer; bits 6-0: RF Channel
35CONFIGURING THE AC4490www.aerocomm.comEEPROM Byte ReadUpon receiving this command, a transceiver will respond with thedesired data from the addresses requested by the OEM Host.Command: 0xCC 0xC0 <Address> <Length>Number of Bytes Returned: 4+Response: 0xCC <Address> <Length> <Requested Data>EEPROM Byte WriteUpon receiving this command, a transceiver will write the data byte tothe specified address but will not echo it back to the OEM Host until theEEPROM write cycle is complete (up to 10 ms).Multiple byte writes of up to 128 bytes are allowed. An EEPROMboundary exists between addresses 0x7F and 0x80. No singleEEPROM write command shall write to addresses on both sides of thatEEPROM boundary.Note: Only the last byte wriiten will be displayed in the commandresponse.Command: 0xCC 0xC1 <Address> <Lenght> <Data>Number of Bytes Returned: 4+Response: 0xCC <Address> <Lenght> <Data written>ResetThe OEM Host issues this command to perform a soft reset of thetransceiver. Any transceiver settings modified by CC commands willrevert to the values stored in the EEPROM.Command: 0xCC 0xFFNumber of Bytes Returned: NoneResponse: None
www.aerocomm.comEEPROM PARAMETERS9The OEM Host can program various parameters that are stored in EEPROM which become active after a power-onreset. The table below gives the locations and descriptions of the parameters that can be read/written by the OEMHost. Factory default values are also shown. Do not write to any EEPROM addresses other than those listed below.Do not copy one transceiver’s EEPROM to another transceiver as doing so may cause the transceiver to malfunction.Table 16: EEPROM ParametersParameter EEPROM AddressLength (Bytes) Range Default DescriptionProduct ID 0x00 40 40 bytes - Product identifier string. Includes revisioninformation for software and hardware.Range Refresh 0x3D 10x01 -0xFF0x18 Specifies the maximum amount of time a transceiver willreport In Range without having heard a Server’s beacon(equal to hop period * value). Do not set to 0x00.Stop Bit Delay 0x3F 10x00 -0xFF0xFF For systems employing the RS-485 interface or Parity, theserial stop bit might come too early. Stop bit delay controlsthe width of the last bit before the stop bit occurs.0xFF = Disable Stop Bit Delay (12 us)0x00 = (256 * 1.6 us) + 12 us0x01 - 0xFE = (value * 1.6 us) + 12 usChannel Number 0x40 10x00 -0x371x1: 0x00200: 0x001000: 0x10Set 0 = 0x00 - 0x0F (US/Canada): 1x1/200Set 1 = 0x10 - 0x2F (US/Canada): 1x1/1000Set 2 = 0x30 - 0x37 (US/Canada): 1x1/200; Australia: 1x1/200/1000Server/Client Mode 0x41 10x01 -0x020x02 0x01 = Server0x02 = ClientBaud Rate Low 0x42 10x00 -0xFF0xFC Low byte of the interface baud rate. Default baud rate is57,600.Baud Rate High 0x43 10x00 0x00 High byte of interface baud. Always 0x00
37EEPROM PARAMETERSwww.aerocomm.comControl 0 0x45 10x00 -0xFF0x14 Settings are:bit-7: One Beacon Mode0 = Beacon every hop (disabled)1 = Beacon once per hop cycle (enabled)bit-6: DES Enable0 = Disable Encryption1 = Enable Encryptionbit-5: Sync to Channel0 = Disabled1 = Enabledbit-4: Aerocomm Use Onlybit-3: Aerocomm Use Onlybit-2: Aerocomm Use Onlybit-1: RF Delivery0 = Addressed packets1 = Broadcast packetsbit-0: Aerocomm Use OnlyFrequency Offset 0x46 10x00 -0xFF0x01 Protocol parameter used in conjunction with ChannelNumber to satisfy unique regulations.CMD/Data RX Disable 0x4B 10xE3,0xFF0xFF oxE3 = Enable CMD/Data RX Disable0xFF = Disable CMD/Data RX DisableTransmit Retries 0x4C 10x01 -0xFF0x10 Maximum number of times a packet is sent out whenAddressed packets are selected.Broadcast Attempts 0x4D 10x01 -0xFF0x04 Maximum number of times a packet is sent out whenBroadcast packets are selected.API Control 0x56 10x00 -0xFF0x43 Settings are:bit-7: Aerocomm Use Onlybit-6: Aerocomm Use Onlybit-5: Unicast Only0 = Disabled1 = Enabledbit-4: Auto Destination0 = Use destination address1 = Use auto destinationbit-3: Client Auto Channel0 = Disabled1 = Enabledbit-2: RTS Enable0 = Ignore RTS1 = Transceiver obeys RTSbit-1: Duplex 0 = Half Duplex 1 = Full Duplexbit-0: Auto Config0 = Use EEPROM values1 = Auto Configure valuesInterface Timeout 0x58 10x02 -0xFF0x04 Specifies a byte gap timeout, used in conjunction with RFPacket Size to determine when a packet coming over theinterface is complete (0.5 ms per increment).Sync Channel 0x5A 10x00 -0xFF0x01 Used to synchronize the hopping of collocated systems tominimize interference.Table 16: EEPROM ParametersParameter EEPROM AddressLength (Bytes) Range Default Description
EEPROM PARAMETERS38RF Packet Size 0x5B 10x01 -0x800x80 Used in conjunction with Interface Timeout; specifies themaximum size of an RF packet.CTS On 0x5C 10x01 -0xFF0xD2 CTS will be deasserted (High) when the transmit buffercontains at least this many characters.CTS Off 0x5D 10x00 -0xFE0xAC Once CTS has been deasserted, CTS will be reasserted(Low) when the transmit buffer is contains this many or lesscharacters.Max Power 0x63 10x00 -0x60Set inProduction& can varyUsed to increase/decrease the output power. Thetransceivers are shipped at maximum allowable power.Modem Mode 0x6E 10xE3,0xFF0xFF oxE3 = Enable Modem Mode0xFF = Disable Modem ModeParity 0x6F 10xE3,0xFF0xFF 0xE3 = Enable Parity0xFF = Disable ParityNote: Enabling parity cuts throughput and the interface buffersize in half.Destination ID 0x70 60x00 -0xFF0xFF Specifies destination for RF packetsSystem ID 0x76 10x00 -0xFF0x01 Similar to network password. Radios must have the samesystem ID to communicate with each other.Long Range Mode 0x7D 10xE3,0xFF0xE3 Used to enable/disable Long Range mode.0xE3 = Enable Long Range Mode0xFF = Disable Long Range ModeNote: Only valid on AC4490LR-200 and AC4490LR-1000transceivers with firmware v6.7+.RS-485 DE 0x7F 10xE3,0xFF0xFF 0xE3 = GO0 is active Low DE for control of external RS-485hardware0xFF = Disable RS-485 DEMAC ID 0x80 60x00 -0xFFFactory programmed unique IEEE MAC address.Original Max Power 0x8E 1Set inProductionand can varyCopy of original max power EEPROM setting. This addressmay be referenced but should not be modified.RS485 Modem Mode 0x8F 10xE3,0xFF0xFF oxE3 = Enable RS485 Modem Mode0xFF = Disable RS485 Modem ModeProduct ID 0x90 15 0x90 - 0x93: Product ID0x94 - 0x95: Prefix (CL, CN, or AC)0x96 - 0x99: Power (200M, 200A, 1000, 1x1)Note: There will be a period in front of the 1x1 to keep thefield at four bytes0x9A - 0x9C: Interface (232, 485, TTL)0x9D - 0x9E: Setup script (01 is stock)0x9F: Reserved for future use; always 0xFFTable 16: EEPROM ParametersParameter EEPROM AddressLength (Bytes) Range Default Description
39EEPROM PARAMETERSwww.aerocomm.comProtocol Status /Receive ACK0xC0 10xE3,oxFFoxFF oxE3 = GO0 outputs the Protocol Status and GO1 outputsthe Received Acknowledgement signal0xFF = Disable Protocol Status / Receive ACKReceive API 0xC1 10xE3,0xFF0xFF 0xE3 = Enabled0xFF = DisabledEnhanced APIControl0xC6 10xF8 Settings are:bit-7: Enhanced API Control Enable0 = Enable Enhanced API Control1 = Disable Enhanced API Controlbit-6: Aerocomm Use Onlybit-5: Aerocomm Use Onlybit-4: Aerocomm Use Onlybit-3: Aerocomm Use Onlybit-2: Send Data Complete Enable0 = Disable1 = Enablebit-1: API Transmit Packet Enable0 = Disable1 = Enablebit-0: Enhanced API Receive Packet Enable0 = Disable1 = EnableAuto Calibrate 0xCC 10xE3,0xFF0xFF oxE3 = Enable Auto Calibrate0xFF = Disable Auto CalibrateDES Key 0xD0 70x00 -0xFF56-bit Data Encryption keyTable 16: EEPROM ParametersParameter EEPROM AddressLength (Bytes) Range Default Description
www.aerocomm.comDIMENSIONS10MECHANICAL DRAWINGSInterface Connector - 20 pin OEM Interface connector (Molex 87759-0030, mates with Samtec SMM-110-02-S-DMMCX Jack - Antenna Connector (Johnson Components 135-3711-822)Figure 10: AC4490 (with MMCX connector) Mechanical0.0000.1000.1500.4351.9001.8750.8250.125 dia non-plated holes (2) places0.0000.1001.0101.6501.550 pins1 21.6500.0000.0670.0000.1570.0620.180MMCX jackJ120 pin header, 0.020 sq. posts on 0.079 inch (2mm) centers1.3201.7600.100 dia non-plated hole (1) place, under shieldMMCX jack 0.145 dia
41DIMENSIONSwww.aerocomm.comFigure 11: AC4490 with integral gigaAnt Antenna (on bottom) Mechanical0.0000.1000.1501.8752.5502.6500.4350.125 dia non-plated holes (4) places0.0000.1001.0101.6501.550 pins1 21.6500.0000.0000.1570.062J120 pin header, 0.020 sq. posts on 0.079 inch (2mm) centers-0.1520.0000.1800.0861.1802.0302.345GigaAnt Snap-In Antenna
DIMENSIONS42Figure 12: AC4490-1x1 Mechanical0.0000.2000.3000.0000.0801.0001.080cut corner indicates pin 10.0.0.AC4490-1X1100.100 typ.01.0000050680045030.2200.2600.10 typ.0.8600.080 x 0.040 padtypicalRECOMMENDED PAD PATTERN (viewed from top)0.0000.0800.2200.8601.0001.080Module Outline28127234567262524232221 20 19 18 17 16 15891011121314N/CCTSRTSVCC (note 1)RSSIGND (note 2)RF_PORTAD_INUP_RESETCMD/DATAIN_RANGEDO1DA_OUTDI1N/CN/CN/CN/CN/C9600_BAUD (TST_MODE)RESETRXDTXDDI0DO0GNDVCC (note 1)HOP_FRAMENotes:1) VCC must not exceed +3.3V DC.2) This GND pin to be used for RF ground3) Operating temperature -40C to +80C3) Storage temperature -60C to +140C
43DIMENSIONSwww.aerocomm.comFigure 13: AC4490-1x1 PCB Considerations
www.aerocomm.comORDERING INFORMATION11PRODUCT PART NUMBER TREEDEVELOPER KIT PART NUMBERSAll of the above part numbers can be ordered as a development kit by prefacing the part number with “SDK-”. As anexample, part number AC4490-200A can be ordered as a development kit using the part number: SDK-AC4490-200A.All developer’s kits include (2) transceivers, (2) development boards, (2) 7.5 VDC unregulated power supplies, (2)serial cables, (2) USB cables, (2) antennas, configuration/testing software and integration engineering support.
www.aerocomm.comCOMPLIANCY INFORMATION 12AC4490-1X1Due to the RF antenna trace residing on the OEM Host PCB, the FCC will not grant modular approval for the AC4490-1x1 and requires the OEM to submit their completed design for approval. Contact AeroComm for the approvalprocedure.AGENCY IDENTIFICATION NUMBERSAgency compliancy is a very important requirement for any product development. AeroComm has obtained modularapproval for its products so the OEM only has to meet a few requirements to be eligible to use that approval. Thecorresponding agency identification numbers and approved antennas are listed below.APPROVED ANTENNA LISTThe following antennas are approved for use with the AC4490 as identified. The OEM is free to choose anothervendor’s antenna of like type and equal or lesser gain as a listed antenna and still maintain compliance.Table 13: Agency Identification NumbersPart Number US/FCC Canada/ICAC4490-200AKQLAC4490-100 2268C-AC4490AC4490-200/AC4490LR-200 KQL-4X90-200 2268C-4X90200AC4490-1000KQL-AC4490 2268C-AC44901000To reduce potential radio interference to other users, the antenna type and its gain should be so chosen that theequivalent isotropically radiated power (e.i.r.p.) is not more than that permitted for successful communication.This device has been designed to operate with the antennas listed below, and having a maximum gain of 11.0 dBd.Antennas not included in this list or having a gain greater than 11.0 dBd are strictly prohibited for use with thisdevice. The required antenna impedance is 50 ohms.
COMPLIANCY INFORMATION46FCC / IC REQUIREMENTS FOR MODULAR APPROVALIn general, there are two agency classifications of wireless applications; portable and mobile.Portable - Portable is a classification of equipment where the user, in general, will be within 20 cm of the transmittingantenna. Portable equipment is further broken down into two classes; within 2.5 cm of human contact and beyond2.5 cm (Note: Ankles, feet, wrists, and hands are permitted to be within 2.5 cm of the antenna even if the equipment isdesignated as being greater than 2.5 cm). The AC4790 is not agency approved for portable applications. The OEM isrequired to have additional testing performed to receive this classification. Contact AeroComm for more details.Mobile - Mobile defines equipment where the user will be 20 cm or greater from the transmitting equipment. Theantenna must be mounted in such a way that it cannot be moved closer to the user with respect to the equipment,although the equipment may be moved. (Note: Ankles, feet, wrists, and hands are permitted to be within 20 cm ofmobile equipment).-1020B5812-04 Flavus gigaAnt Microstrip -0.5 X - - --Y22831Comtelco Yagi 6 dBd - X X X-Y2283A0915-10RP Comtelco Yagi 6 dBd - X X X-SG101N9152Nearson Omni 5 - X X X-SG101NT-915 Nearson Omni 5 - X X X-GM113 V.Torch Omni 3.5 - X X --PC8910NRTN Cushcraft Yagi 11 dBd - - X --ANT-DB1-RMS Antenna Factor Monopole 3 - X X -1. Strictly requires professional installation.2. Strictly requires professional installation.Table 18: AC4490 Approved AntennasAeroCommPart NumberManufacturer Part Number Manufacturer Type Gain (dBi)200A200M200LR1000M0600-00019 S467FL-5-RMM-915S Nearson 1/2 Wave Dipole 2 - X X X0600-00025 S467FL-5-RMM-915 Nearson 1/2 Wave Dipole 2 - X X X0600-00024 S467AH-915 Nearson 1/2 Wave Dipole 2 - X X X0600-00027 S467AH-915R Nearson 1/2 Wave Dipole 2 - X X X0600-00028 S161AH-915R Nearson 1/2 Wave Dipole 2.5 - X X X0600-00029 S161AH-915 Nearson 1/2 Wave Dipole 2.5 - X X X0600-00030 S331AH-915 Nearson 1/4 Wave Dipole 1 - X X X
47COMPLIANCY INFORMATIONwww.aerocomm.comLabel and text information should be in a size of type large enough to be readiily legible, consistent with thedimensions of the equipment and the label. However, the type size for the text is not required to be larger than eightpoint.ANTENNA REQUIREMENTSWARNING: This device has been tested with an MMCX connector with the above listed antennas. When integratedinto the OEM’s product, these fixed antennas require professional installation preventing end-users from replacingthem with non-approved antennas. Antenna Y2283 & SG101N915 strictly require professional installation. Anyantenna not in the previous table must be tested to comply with FCC Section 15.203 for unique antenna connectorsand Section 15.247 for emissions. Contact AeroComm for assistance.Caution: Any change or modification not expressly approved by AeroComm could void the user's authority to operatethe equipment.WARNINGS REQUIRED IN OEM MANUALSWARNING: This equipment has been approved for mobile applications where the equipment should be used atdistances greater than 20 cm from the human body (with the exception of hands, feet, wrists, and ankles). Operationat distances of less than 20 cm is strictly prohibited and requires additional SAR testing.CHANNEL WARNINGThe OEM must prevent the end-user from selecting a channel not approved for use by the FCC.OEM EQUIPMENT LABELING REQUIREMENTSWARNING: The OEM must ensure that FCC labeling requirements are met. This includes a clearly visible label on theoutside of the OEM enclosure specifying the appropriate AeroComm FCC identifier for this product as well as the FCCnotice below. The FCC identifiers are listed above.Contains FCC ID: KQLAC4490-100 / KQLAC4490 / KQL-4X90200Operation is subject to the following two conditions: (1) this device may not causeinterference, and (2) this device must accept any interference, including interferencethat may cause undesired operation of the device.
www.aerocomm.comAPPENDIX I - SAMPLE POWER SUPPLYIBelow is a simple switching power supply that provides enough current to easily power any Aerocomm OEM module.It utilizes low cost, off the shelf components that fit into a small area. This supply has an input voltage range of +6volts to +18 volts and will output +3.4 volts at 1.5 amps. Included is a schematic, bill of materials with manufacture's name and part numbers and a sample PCB layout. It isimportant to follow the layout suggestions and use large areas of copper to connect the devices as shown in thelayout. It is also important to hook up the ground traces as shown and use multiple vias to connect input and outputcapacitors to the bottom side ground plane. If the input voltage will be less than 12 volts then C1 and C2 can be replaced with a single 100uF 20 volt capacitor(same part number as C7). This will reduce board space and lower costs further. If you are powering an AC5124module, R1 can be changed to a 373 ohm 1% resistor. This will change the output to +5 volts at 1.0 amps. BILL OF MATERIALSTable 19: Power Supply Bill of MaterialsQty Reference Value Description Mfg. Mfg. part number 1 R1 210 Res, 0603, 210, 1/16W, 1% KOA RK73H1JT2100F 1 R2 127 Res, 0603, 127, 1/16W, 1% KOA RK73H1JT1270F 2 C1 C2 47uF Cap, Tant, 7343, 47uF, 35V AVX TPSE476M035R0200 3 C3 C4 C5 0.1uF Cap, Cer, 0603, 0.1uF, Y5V, 25V Murata GRM39Y5V104Z025AD 1 C6 3300pF Cap, Cer, 0603, 3300pF, X7R, 50V Murata GRM39X7R332K050AD 1 C7 100uF Cap, Tant, 7343, 100uF, 20V Kemet T491X107K020A5 1 D1 B230/A Diode, SMB, B230/A, 2A, Schott-key Diodes, Inc. B230/A 1 D2 LL4148 Diode, MELF, LL4148, Switch Diode Diodes, Inc. LL4148 1 L1 15uH Xfmr, 2P, SMT, 15uH, 2A Coiltronics UP2.8B150 1 U1 CS51413 IC, CS51413, 8P, SO, Switch Reg Ctrl. On-Semi-cond. CS51413
49APPENDIX I - SAMPLE POWER SUPPLYwww.aerocomm.comSCHEMATICPCB LAYOUT
APPENDIX I - SAMPLE POWER SUPPLY50
www.aerocomm.comAPPENDIX II - 5V TO 3.3V LEVELSIIAll inputs on the AC4490-200 & AC4490-1000 are weakly pulled high via 10 kohm resistors. The AC4490-200 has 5Vinputs while the AC4490-1000 & AC4490-1x1 have 3.3V inputs. The AC4490-200 uses an octal buffer to drop the 5V tothe required 3.3V level; the -1000 and -1x1 leave this to the OEM.Some of the most common voltage conversion methods are described below.VOLTAGE LEVEL CONVERSION IC’SThis is the easiest and most efficient method. Aerocomm recommends the TI SN74LVC244A Octal Buffer/Driver.Inputs can be driven from either 3.3 or 5V systems, allowing the device to be used in a mixed 3.3/5V system.PASSIVE RESISTOR VOLTAGE DIVIDERWhile a resistor voltage divider can successfully drop the 5V to the required 3.3V, it will draw static current all of thetime. Typically this method is only suitable for one-way 5V to 3.3V conversion. When choosing the resistor values,one needs to include the radio’s internal 10 kohm resistors on the input signals.74LVC2442Y0GND92Y010 GND1Y32A01Y32A012111OE11A0232Y341A1VCC2OE1Y02A3201918172Y251A2672Y181A31Y12A21Y22A116151413Y018Y11614 Y212 Y3A0A1A2A32468OE1Input AInput BInput CInput D74LVC244
www.aerocomm.comAPPENDIX III - APIIIIThe API feature set of the AC4490 provides powerful packet routing capabilities to the OEM Host. The number of APIconfigurations is endless as individual radios can all be configured differently to suit the OEM Host’s varying needs.Some of the most common implementations are described in the following pages.POLLING NETWORKMany applications require multiple locations to report back to a single access point. One solution would be to enterCommand mode, change the transceiver’s destination address and then exit Command mode to resume normaloperation. When it is time to communicate with another transceiver, the process would be repeated; costing time andinevitably reduction in throughput as unnecessary commands are issued. As an alternative, the Transmit APIcommand can be used to control packet routing on a packet-by-packet basis.The simplest implementation consists of a smart Shared Access Point (SAP) with a microcontroller or processor ofsome type which has transmit API enabled. The SAP controls which transceiver(s) each packet is routed to.Broadcast packets should be used when all remotes are to receive the same message and addressed packets whencommunication with a single remote only is desired. An example of each is shown in the following pages.MAC 12 34 56Shared Access PointMAC 12 34 A3MAC 12 34 A2MAC 12 34 A1MAC 12 34 A6MAC 12 34 A4MAC 12 34 A5Channel: 0x10System ID: 0x011 23456
53APPENDIX III - APIwww.aerocomm.comAddressed Transmit API1To poll radio 1, the SAP transmits the packet using the following format:2To poll radio 2, the SAP transmits the packet using the following format:3To poll radio 2, the SAP transmits the packet using the following format:4This continues until all radios have successfully been polled by the SAP.Broadcast Transmit APITo send out a universal poll request or data packet, the OEM may wish to utilize the broadcast portion of the TransmitAPI command. The Broadcast command is similar to the addressed command; only with the Destination MACAddress set to all 0xFF.
APPENDIX III - API54The remote response is dependent on the OEM’s specific needs and equipment. In many cases, remote radios areconnected to dumb devices without the intelligence to filter out or append specific portions of a packet that istransmitted or received. Since the 7 bytes of overhead in the Transmit API command are not sent over the RF, theremotes will receive only the payload data, “STATUS”. If auto destination is enabled on the remote radio, thetransceiver will automatically change its destination address to that of the radio it last received a packet from. Whenthe remote device sends its response, it will therefore automatically be routed back to the SAP.Depending on the API configuration of the SAP, the packet will be received in one of two formats:Receive APIWhen Receive API is enabled, the transceiver will receive the reply data + the MAC address of the source radio.When Receive API is enabled, every packet received by the transceiver will be sent to the Host in the following format.
55APPENDIX III - APIwww.aerocomm.comEnhanced Receive APIWhen Enhanced Receive API is enabled, the transceiver will receive the reply data + the MAC address of the sourceradio and one RSSI value; RSSI* is how strong the local heard the remote transceiver.It may be useful to the OEM Host to determine which radio each packet originated from. When Enhanced Receive APIis enabled, every packet received by the transceiver will be received in the above format.Normal Receive Mode (non-API)If Receive API is not enabled, the transceiver will receive the reply data only (i.e. “ALLGOOD”) from each transceiver.LOOPBACK REPEATERThe simplest repeater to implement is a loopback repeater. A loopback repeater can be created by connecting thetransceiver’s RXD and TXD lines together. When the radio receives data, it will retransmit the data to all availabletransceivers on the network. It is important not to have two loopback repeaters in range of each other as they willcontinuously transmit data back and forth.If radios B & C in the above picture are not within range of radio A, they will not be able to receive or respond tocommunications from radio A. A loopback repeater can be added between the three such that it is in range of bothradio A and radios B & C. When the repeater receives a packet from radio A, it will transmit the packet out to radios BMAC 12 34 56 MAC 12 34 A3MAC 12 34 A2MAC 12 34 A1Loopback RepeaterA B C
APPENDIX III - API56& C. If the repeater is set to Broadcast mode, radio A will receive a copy of each packet that it sends. If the repeaterhas a specific destination address (i.e. 12 34 A2), then radio A will not receive the packet as its MAC address will notmatch the specified destination address.TIME DIVISION MULTIPLE ACCESS NETWORKFor a more intelligent network, a TDMA system can be implemented. In this system various radios transmit data to aShared Access Point (SAP) during an assigned time interval. The system is synchronous so that only one radio istransmitting at a time and has full access to the SAP’s bandwidth. In a TDMA network, each radio must store its datafor the amount of time between its transmissions or bursts. A typical format for data passing through a SAP is shownbelow. A frame consists of arriving bursts from remote radios and each frame is then divided into multiple time slots.The bursts can be of varying lengths and can be longer for heavy-traffic stations. To prevent overlaps, guard intervalscan be inserted to absorb small timing errors in burst arrivals.Example:•Shared Access Point (SAP) sends broadcast packet which includes a sync pulse•Remote radios hear the sync pulse and join the session•Radio A transmits during time interval t = 1•Radio B transmits during time interval t = 2•Radio N transmits during time interval t = N - 1This type of implementation requires careful planning and should allow enough time for retries if necessary. When fullduplex is enabled, the radio which initiated the Session (SAP) will transmit during the even numbered hops and theremote radios will transmit only during odd numbered hops.123456GB1 Radio A Data GB2Radio B DataGB3GB4Radio C Data61TDMA Frame1 Timeslot
www.aerocomm.comAPPENDIX IV - SYNC TO CHANNELIVSYNC TO CHANNELWhat is it and do I need it? AeroComm uses frequency hopping protocol with a fixed pseudo-random hopping sequence on our transceivers.This protocol yields superior interference rejection and multipath immunity. The Server radio sends timing beaconsout on a regular interval and the Clients hear these beacons and synchronize their frequency hopping to the Server. Though Servers cannot send packets to each other, they can hear the timing beacons sent out by other Servers.Normally, they simply ignore the beacons sent out by the other Servers. However, when Sync-to-Channel is enabled,they will listen for the beacons sent out by another Server and then synchronize their hop timing to that Server. Why is this important? If two Servers (and their Clients) are operating in the same area and their frequency hopping isnot synchronized to each other it's possible that they might try to occupy the same frequency at the same time. Insevere cases, they could interfere with each other on every frequency, causing very sluggish communications. To avoid this kind of interference, collocated Servers can use Sync-to-Channel. Sync-to-Channel synchronizes thefrequency hop timing between these Servers so that they never occupy the same frequency at the same time. To use Sync-to-Channel, you should select one Server (preferably the most centrally located Server) to be the "HopMaster." This Server should be programmed to a numerically low Channel Number and should have Sync-to-Channeldisabled. All other Servers in the area should have Sync-to-Channel enabled. These other Servers should have Sync-Channel set to the Channel of another Server in the area that they are in range of. Preferably, if all Servers are inrange of the Hop Master, they should all have their Sync-Channel set to the Channel Number of the Hop Master. Thefollowing rules apply to Sync-to-Channel: One Server should perform the function of Hop Master. It should have its Channel Number set to a numerically lowvalue and should have Sync-to-Channel disabled. It's preferable that it be centrally located. All other Servers in thearea should have Sync-to-Channel enabled. They should have their Sync-Channel set to a value lower than theirChannel Number. If they are in range of the Hop Master, its preferable that they have the Sync-Channel set to theChannel Number of the Hop Master. All collocated Servers must be programmed to the same Channel Set. There are 56 available channels for theAC4490, shown in Table 19 below.Table 20: RF Channels for AC4490Channel Set11. All collocated Servers must operate in the same Channel Set.RF Channel Number Range (0x40)Frequency Details & Regulatory requirements Countries0 (AC4490 - 1x1 AC4490 - 200)0x00 - 0x0F 902 - 928 MHz (26 hop bins) US / Canada1 (AC4490 - 1x1 AC4490 - 1000)0x10 - 0x2F 902 - 928 MHz (50 hop bins) US / Canada2 (AC4490 - 1x1 AC4490 - 200 AC4490 - 1000)0x30 - 0x37 915 - 928 MHz (22 hop bins) US / Canada (-1x1 / -200)Australia(-1x1/-200/-1000)
APPENDIX IV - SYNC TO CHANNEL58What happens if you don't enable Sync-to-Channel and you have collocated Servers? You have good odds that youwill see a decrease in throughput due to the systems trying to occupy the same frequency at the same time. In severecases, you could lose communications all together depending on how much bandwidth your system requires. Due tocrystal differences between the Servers, you could see the interference come and go.Figure 14: Servers without Sync-to-Channel Enabled
59APPENDIX IV - SYNC TO CHANNELwww.aerocomm.comFigure 15: Servers with Sync-to-Channel EnabledHow do I configure Sync to Channel? To configure sync to channel, you must use our OEM configuration software. This can be downloaded from ourwebsite http://www.aerocomm.com by clicking the software link at the top of the screen and selecting the DeveloperKit Software. You will be prompted to install the software on your PC. Once the install is completed, you can open the softwarefrom Start -> All Programs -> Aerocomm Wireless -> Aerocomm OEM.exe 1. The software will open and prompt you to select a product. Select AC4490 as the product on the PC settings page(Figure 16). 2. Verify that the Read/Write with AT commands box is checked. 3. Select the COM Port that your radio is connected to. If you are unsure, press the Find Ports button and the dropdown list will be updated with available COM ports. 4. Select the baud rate that matches the baud rate that the radio is programmed to.
APPENDIX IV - SYNC TO CHANNEL60Figure 16: PC Settings Page5. Go to the Configure page and click the read radio button at the bottom right of the screen. A message stating"Read Successful" should appear after a successful read (Figure 17).
61APPENDIX IV - SYNC TO CHANNELwww.aerocomm.comFigure 17: Configure Page - Read Successful6. To configure the hop master, change the Mode to Server and select Broadcast. Make note of the RF Channel(Figure 18). Once the appropriate changes have been made, press the Write Radio button. A Write Successfulprompt will appear after a successful write.
APPENDIX IV - SYNC TO CHANNEL62Figure 18: Hop Master Settings7. Configure all clients that will communicate with the hop master as Clients in Auto Destination and with the same RFchannel as the hop master (Figure 19) and press the Write Radio button.
63APPENDIX IV - SYNC TO CHANNELwww.aerocomm.comFigure 19: Client Settings8. Set the second server as a server in broadcast mode with an RF channel at least 2-5 steps above the RF channel ofthe hop master. Under the radio features section, select the Sync Channel box and in the Radio RF section, set theSync to Channel to the RF channel of the hopmaster (Figure 20). Press the Write Radio button to write the changes tothe radios EEPROM.
APPENDIX IV - SYNC TO CHANNEL64Figure 20: Server #2 Settings9. Configure the Clients that will communicate with Server #2 as Clients in Auto Destination and with the same RFchannel as Server #2 (Figure 21). Press the Write Radio to write the changes to the radios EEPROM.
65APPENDIX IV - SYNC TO CHANNELwww.aerocomm.comFigure 21: Client SettingsI've configured my radios, what's next? Once you have configured all radios, your network should be setup similar to the one shown in Figure 22 below. Themain server or hop master will need to be powered on anytime that the other servers are connected or they will neversynchronize and will not be able to communicate with their clients. If a centralized network will not work and allservers will not be in range of the hop master, a daisy chain network can be utilized as shown in Figure 23.
APPENDIX IV - SYNC TO CHANNEL66Figure 22: Centralized Sync-to-Channel ConfigurationFigure 23: Daisy Chain Sync-to-Channel Configuration

Navigation menu