HumPRO-A TM Series 900MHz RF Transceiver Module Data Guide
! Warning: Some customers may want Linx radio frequency (“RF”) products to control machinery or devices remotely, including machinery or devices that can cause death, bodily injuries, and/or property damage if improperly or inadvertently triggered, particularly in industrial settings or other applications implicating life-safety concerns (“Life and Property Safety Situations”). NO OEM LINX REMOTE CONTROL OR FUNCTION MODULE SHOULD EVER BE USED IN LIFE AND PROPERTY SAFETY SITUATIONS.
40^ 40^ 41^ 42^ 43^ 44^ 45^ 46^ 48^ 95^ 96^ 96^ 97^ 98^ 98^ 98^ 100^ 100^ 101^ 102^ 102^ 103^ 104^ 105^ 106^ 106^ 106^ 108^ 110^ 112^ 114^ Restore Factory Defaults Using the Low Power Features Baud Rate and Transmitter Output Power The Command Data Interface Reading from Registers Writing to Registers Command Length Optimization Example Code for Encoding Read/Write Commands The Command Data Interface Command Set Typical Applications Usage Guidelines for FCC Compliance Additional Testing Requirements Inform
Ordering Information Electrical Specifications HumPRO-ATM Series Transceiver Specifications Ordering Information Part Number Description Parameter HUM-A-900-PRO-CAS HumPRO-A Series High Power Data Transceiver with Castellation Connection Power Supply HUM-A-900-PRO-UFL HumPRO-ATM Series High Power Data Transceiver with u.
HumPRO-ATM Series Transceiver Specifications Parameter Symbol Min. Number of Hop Sequences HumPRO-ATM Series Transceiver Specifications Typ. Max. Units Notes Parameter 6 Receiver Section Spurious Emissions –47 IF Frequency dBm 304.7 kHz @ min rate –108 dBm 5 @ max rate –101 dBm 5 RSSI Dynamic Range 86 dB CSMA RSSI Threshold –70 dBm +25 dBm 6 dBc 6 dB 6 Ω 4 Receiver Sensitivity 5 PO Harmonic Emissions PH Output Power Range PH TBD –9.
400.00 520.0 -40°C 300.00 25°C 250.00 85°C 200.00 150.00 100.00 420.0 25°C 370.0 320.0 85°C 270.0 50.00 0.00 -15.00 -40°C 470.0 Supply Current (mA) Supply Current (mA) 350.00 -10.00 -5.00 0.00 5.00 10.00 15.00 20.00 25.00 220.0 2.7 30.00 3.0 Figure 6: HumPRO-ATM Series Transceiver Average Current vs. Transmitter Output Power at 2.5V 450.0 450.00 400.00 350.00 Supply Current (mA) -40°C 25°C 300.00 85°C 250.00 3.6 Figure 9: HumPRO-ATM Series Transceiver TX Current vs.
2.50 240.0 -40°C 200.0 25°C 180.0 160.0 85°C 1.50 25°C 1.00 -40°C 0.50 140.0 120.0 2.7 85°C 2.00 Supply Current (µA) Supply Current (mA) 220.0 0.00 3.0 3.3 2.7 3.6 3.0 3.3 Figure 10: HumPRO-ATM Series Transceiver TX Current vs. Supply Voltage at 20dBm 44.00 Figure 12: HumPRO-ATM Series Transceiver Standby Current Consumption vs. Supply Voltage 0 85°C -10 RSSI Reading (dBm) Supply Current (mA) 42.00 25°C 40.00 38.00 -40°C 36.00 -20 -30 -40 -50 -60 -70 -80 34.00 32.00 2.7 3.
1 NC 2 NC 3 BE 4 NC 5 NC 6 NC 7 NC 8 GND 9 GND 44 43 42 41 40 39 38 37 36 35 34 NC ANT CTS Pin Number CMD MODE_IND NC NC NC RESET NC Pin Descriptions NC POWER_DOWN NC Pin Assignments 33 32 ANT NC 10 NC 11 13 Name CRESP I/O O Command Response. This line is low when the data on the CMD_DATA_OUT line is a response to a command and not data received over the air. 14 PB I Push Button input. This line can be connected to Vcc through a normally open push button.
Module Pin Assignments Module Dimensions 1 NC 2 NC 3 BE 4 NC 5 NC 6 NC 7 NC 8 GND 9 GND 44 43 42 41 40 39 38 37 36 35 34 NC ANT CTS 0.66 in (16.66 mm) CMD MODE_IND NC NC NC RESET NC NC POWER_DOWN NC The module has two versions that differ in the antenna connection. The antenna connection is routed to either a castellation (-CAS) or a u.FL connector (-UFL), depending on the part number ordered. 33 32 NC 1.01 in (25.70 mm) NC 10 NC 11 0.11 in (2.
Theory of Operation Module Description The HumPROTM Series transceiver is a low-cost, high-performance synthesized FSK / GFSK / MSK transceiver. Figure 19 shows the module’s block diagram. The HumPROTM Series module is a completely integrated RF transceiver and processor designed to transmit digital data across a wireless link. It employs a fast-locking FHSS system for noise immunity and higher transmitter output power as allowed by government regulations.
Overview The HumPRO Series RF transceiver module offers a number of features that make it suitable for many data transfer applications. This section provides a basic overview of the features while following sections dive into them in more detail. TM Addressing The modules have a very powerful addressing method. Each module is given a unique 16 or 32 bit address. The receiving modules use an address mask that determines how it responds to a received transmission.
Addressing Modes The module has very flexible addressing methods selected with the ADDMODE register. It can be changed during operation. The transmitting module addresses packets according to the addressing mode configuration. The receiving module processes all addressing types regardless of the ADDMODE configuration. If the received message matches the addressing criteria, it is output on the UART. Otherwise it is discarded. The ADDMODE configuration also enables assured delivery.
Automatic Addressing Acknowledgements and Assured Delivery The module supports an automatic addressing mode that reads the Source Address from a valid received packet and uses it to fill the Destination Address register. This makes sure that a response is sent to the device that transmitted the original message. This also allows the host microcontroller to read out the address of the sending unit. The automatic addressing is enabled for the different addressing modes with register AUTOADDR.
Frequency Hopping Spread Spectrum The module uses Frequency Hopping Spread Spectrum to allow operation at higher power levels per regulations and to reduce interference with other transmitters. The module is configured for operation in one of 6 different hopping sequences. Each sequence uses 26 channels for the high RF data rate or 50 channels for the low RF data rate. Modules must use the same hopping sequence to communicate.
Transmitting Packets Receiving Packets In default operation when transmitting, the host microcontroller writes bytes to the CMD_DATA_IN line while the CMD line is held high at the baud rate selected by the UARTBAUD register.
DSN Address Packet Header CMD Tag CMD_DATA_IN CMD_DATA_OUT Any Command Read Packet Command Any Response 0x01 ACK Packet to UART CONTROL EX Header Length 1 Frame Type 1 User Address Packet Header Tag Header Frame Length Type 0x01 1 1 Hop ID Sequence Dest DSN 1 1 4 Source DSN 4 Hop ID Sequence Cust ID Dest Addr 1 1 2 2 or 4 Data Length 1 Source Addr 2 or 4 Source DSN 4 Data Length 1 Exception for unread packet Packet In Figure 21: HumPRO-ATM Series Transceiver Received Packet Tr
The header and data structures for explicit encrypted packets are shown in Figure 24. The header and data blocks returned by the module are the decrypted message contents. The Dest DSN, Source DSN, Dest Addr and Source Addr fields are the source and destination addresses, the same as in unencrypted packets. Encrypted DSN Address Packet Header The EBlock length field is the total number of bytes of data in the encrypted payload block. This length includes the Payload Type byte.
Exception Engine The HumPRO is equipped with an internal exception engine to notify the host microcontroller of an unexpected event. If errors occur during module operation, an exception is raised. There are two methods of driving the EX pin when an exception condition exists: TM The EX line can be asserted to indicate to the host that an error has occurred. The EXCEPT register must be read to reset the line. Figure 27 lists some example exception masks.
Carrier Sense Multiple Access (CSMA) Using the Command Response (CRESP) Line CSMA is an optional feature. It is a best-effort delivery system that listens to the channel before transmitting a message. If CSMA is enabled and the module detects another transmitter on the same channel, it waits until the active transmitter finishes before sending its payload. This helps to eliminate RF message corruption and make channel use more efficient.
Using the CMD Line AES Encryption The CMD line informs the module where incoming UART data should be routed. When the line is high, all incoming UART data is treated as payload data and is routed to the transmitter to be sent over the air. If the CMD line is low, the incoming UART data is treated as command bytes and is routed to the controller for processing. HumPROTM Series modules with firmware version 2.0 and above offer AES encryption.
A module is set as an administrator by pressing and holding the button for 30 seconds to start the Generate Key function. While the button is held, the MODE_IND line is on. After 30s, the MODE_IND line repeats a double blink, indicating that the function has begun. When the button is released the key and address generation are complete and the module is an administrator. A) If UMASK is pre-set when Generate Key is initiated, then the JOIN process uses that mask and sets the address accordingly.
Using the MODE_IND Line Figure 33 shows the MODE_IND displays in a graphical format. The MODE_IND line is designed to be connected to an LED to provide visual indication of the module’s status and current actions. The pattern of blinks indicates the particular feedback from the module. Figure 31 shows the different blink patterns and their meanings. Module Status Join Operation Two quick blinks Administrator Join. The administrator is looking for a node to join with. One quick blink Node Join.
Restore Factory Defaults The transceiver is reset to factory default by taking the PB line high briefly 4 times, then holding PB high for more than 3 seconds. Each brief interval must be high 0.1 to 2 seconds and low 0.1 to 2 seconds. (1 second nominal high / low cycle). The sequence helps prevent accidental resets. Once the sequence is recognized, the MODE_IND line blinks in groups of three until the PB line goes low.
The Command Data Interface The HumPRO Series transceiver has a serial Command Data Interface (CDI) that is used to configure and control the transceiver through software commands. This interface consists of a standard UART with a serial command set. The CMD_DATA_IN and CMD_DATA_OUT lines are the interface to the module’s UART. The UART is configured for 1 start bit, 1 stop bit, 8 data bits, no parity and a serial data rate set by register UARTBAUD (default 9,600bps).
Writing to Registers Command Length Optimization To allow any byte value to be written, values of 128 (0x80) or greater can be encoded into a two-byte escape sequence of the format 0xFE, [value - 0x80]. This includes register addresses as well as values to be written to the registers. The result is that there are four possible packet structures because of the possible escape sequences. These are shown in Figure 36.
Example Code for Encoding Read/Write Commands This software example is provided as a courtesy in “as is” condition. Linx Technologies makes no guarantee, representation, or warranty, whether express, implied, or statutory, regarding the suitability of the software for use in a specific application. The company shall not, in any circumstances, be liable for special, incidental, or consequential damages, for any reason whatsoever. File EncodeProCmd.
The Command Data Interface Command Set The following sections describe the registers.
CRCERRS - CRC Error Count Volatile Address = 0x40 The value in the CRCERRS register is incremented each time a packet with a valid header is received that fails the CRC check on the payload. This check applies only to unencrypted packets. Overflows are ignored. Writing 0x00 to this register initializes the count. Figure 38 shows the command and response. channels. Figure 41 shows the hop sequences referenced by channel number.
HumPRO-ATM Series Hop Sequences by Channel Number, 19,200bps and below 0 25 63 28 26 16 61 4 29 0 44 46 22 36 34 24 2 21 11 27 1 35 37 55 8 10 54 13 32 43 12 23 48 14 39 40 15 57 18 60 41 9 49 58 38 45 56 50 42 62 47 1 30 60 59 14 16 32 4 47 26 43 1 25 36 15 57 10 48 21 8 17 37 45 44 13 33 0 46 62 34 7 24 22 58 42 50 12 20 39 27 2 35 5 28 49 29 18 38 3 52 40 2 11 12 0 62 23 43 25 34 61 26 24 6 31 7 32 55 39 1 41 29 15 57 3 42 47 2 56 33 9 14 30 21 4 54 59 51 22 38 58 60 52 45 37 13 35 36 8 46 40 49 3 58
TXPWR - Transmitter Output Power Volatile Address = 0x4D; Non-Volatile Address = 0x02 The value in the TXPWR register sets the module’s output power. Figure 43 shows the command and response and Figure 44 available power settings and typical power outputs for the module. The default setting is 0x0A.
ADDMODE - Addressing Mode Volatile Address = 0x4F; Non-Volatile Address = 0x04 The module supports three addressing modes: DSN, User, and Extended User, which are configured using bits 0 - 2. If bit 3 is set, the module sends an extended preamble. This allows modules that have just awakened or have not yet synchronized to find and temporarily synchronize with the transmitting module. This can be useful in systems that require the endpoints to spend most of their time sleeping.
DATATO - Transmit Wait Timeout Volatile Address = 0x50; Non-Volatile Address = 0x05 When a byte is received from the UART, the module starts a timer that counts down every millisecond. The timer is restarted when each byte is received. The value for the DATATO register is the number of milliseconds to wait before transmitting the data in the UART receive buffer. The default setting for this register is 0x10 (~16ms delay).
ENCRC - CRC Enable Volatile Address = 0x53; Non-Volatile Address = 0x08 The protocol includes a Cyclic Redundancy Check (CRC) on the received unencrypted packets to make sure that there are no errors. Encrypted packets use a key-based error detection method. Any packets with errors are discarded and not output on the UART. This feature can be disabled if it is desired to perform error checking outside the module. Set the ENCRC register to 0x01 to enable CRC checking, or 0x00 to disable it.
SHOWVER - Show Version Non-Volatile Address = 0x0A Setting the SHOWVER register to 0x00 suppresses the start-up message, including firmware version, which is sent out of the UART when the module is reset. A value of 0x01 causes the message to be output after reset. By default, the module start-up message is output. Figure 56 shows examples of the commands and Figure 57 shows the available values.
IDLE - Idle Mode Volatile Address = 0x58; Non-Volatile Address = 0x0D The value in the IDLE register sets the operating mode of the transceiver. If the module remains properly powered, and is awakened from a low power mode properly, the volatile registers retain their values. If the volatile registers become corrupted during low power, a software reset is forced and the module reboots. Awake is the normal operating setting.
UDESTID - User Destination Address Volatile Address = 0x5A-0x5D; Non-Volatile Address = 0x0F-0x12 These registers contain the address of the destination module when User Addressing mode or Extended User Addressing mode are enabled. User Addressing mode uses bytes 0 and 1 to determine the destination address. Extended User Addressing mode uses all four bytes.
UMASK - User ID Mask Volatile Address = 0x62-0x65; Non-Volatile Address = 0x17-0x1A These registers contain the user ID mask when User Addressing mode or Extended User Addressing mode are enabled. Please see the Addressing Modes section for more details. Each register byte is read and written separately. Figure 66 shows the User ID Mask registers.
CMDHOLD - CMD Halts Traffic Volatile Address = 0x6E; Non-Volatile Address = 0x23 A CMDHOLD register setting of 0x01 causes the module to store incoming RF traffic (up to the RF buffer size) while the CMD line is low. When the CMD line is returned high, the module outputs all buffered data. A register value of 0 allows received bytes to be output on the UART immediately with CRESP high to indicate that the bytes are received data. See Using the Command Response (CRESP) Line section for details.
AUTOADDR - Auto Addressing Volatile Address = 0x71; Non-Volatile Address = 0x26 When the AUTOADDR feature is enabled, the module reads the Source Address from a received packet and uses it to fill the Destination Address registers (UDESTID or DESTDSN, depending on the addressing mode of the received message). This ensures that a response is sent to the device that transmitted the original message. The response ADDMODE should be the same as ADDMODE used to send the original message.
MYDSN - Local Device Serial Number Non-Volatile Address = 0x34-0x37 These registers contain the factory-programmed read-only Device Serial Number. This address is unique for each module and is included in all packet types as a unique origination address. Figure 76 shows the Device Serial Number registers.
RELEASE - Release Number Non-Volatile Address = 0x78 This register contains a number designating the firmware series and hardware platform. Figure 79 shows examples of the commands and Figure 80 lists current releases to date.
PRSSI - Last Good Packet RSSI Volatile Address = 0x7B This register holds the received signal strength in dBm of the last successfully received packet. A successful packet reception is one that causes payload data to be output on the UART interface. The value in this register is overwritten each time a new packet is successfully processed. The register value is an 8-bit signed integer representing the RSSI in dBm. It is accurate to ±3dB.
NVCYCLE - Non-Volatile Refresh Cycles Non-Volatile Address = 0xC4-0xC5 These read-only non-volatile registers contain the number of lifetime refresh cycles performed for the non-volatile memory. The minimum lifetime refreshes is 2,000 refresh cycles. Beyond this the refreshes may not be complete and the module’s operation can become unpredictable.
CMD - Command Register Volatile Address = 0xC7 This volatile write-only register is used to issue special commands. HumPRO-ATM Series Command Register Write Command Header Size Escape Address Value 0xFF 0x03 0xFE 0x47 V The Get Packet Header command returns the received packet header using a received packet transfer cycle (see the Receiving Packets section). The header is discarded after transfer. This command is normally issued after receiving an RXWAIT exception.
The Join Process Control command allows the software to initiate or stop the secure JOIN process. It has the following subcommands. If KeyN is 0x01, the command writes to the volatile key register. If it is 0x02, it writes to the non-volatile key register. HumPRO-ATM Series JOINCTL Subcommand Values Subcommand Value Figure 92 shows the command for writing the AES key to the module. Operation 0 Halt JOIN operation 1 Generate a random network key and address.
SECSTAT - Security Status Volatile Address = 0xC9 This volatile read-only register provides status of the security features. JOINST - Join Status Volatile Address = 0xCA This volatile read-only register shows the current or previous state of join activity since the module was last reset.
EEXFLAG - Extended Exception Flags Volatile Address = 0xCD - 0xCF These volatile registers contain flags for various events. Similar to the EXCEPT register, they provide a separate bit for each exception. HumPRO-ATM Series Extended Exception Flags Registers Flag EX_SEQSKIP is 1 when a received encrypted packet has a sequence number that is more than one higher than the previously received packet.
Multiple outgoing packets can be buffered. Changing this option clears the incoming buffer, losing un-transmitted or unacknowledged data. PKTOPT - Packet Options Volatile Address = 0xD3; Non-Volatile Address = 0x83 This register selects options for transferring packet data.
When PGKEY is 1 the JOIN process is allowed to change or clear the network key. The key can always be changed through serial commands. SECOPT - Security Options Volatile Address = 0xD4; Non-Volatile Address = 0x84 This register selects options for security features. When CHGADDR is 1 the JOIN process is allowed to generate a random network address if the module is an administrator. If the module is a node it is allowed to accept an address assignment from the administrator.
Non-Volatile Address EEXMASK2 0xD0 0x80 Byte 2 of the extended exception mask EEXMASK1 0xD1 0x81 Byte 1 of the extended exception mask EEXMASK0 0xD2 0x82 Byte 0 of the extended exception mask GND Description GND 1 2 3 4 5 6 7 8 9 10 11 NC NC NC BE NC NC NC NC GND NC NC 12 13 14 15 16 17 18 19 20 21 22 Figure 104: HumPRO-ATM Series Transceiver Extended Exception Mask Registers To use this value, register EXMASK must be zero.
Usage Guidelines for FCC Compliance Information to the user The pre-certified versions of the HumPRO-ATM Series module (HUM-A-900-PRO-UFL and HUM-A-900-PRO-CAS) are provided with an FCC and Industry Canada Modular Certification. This certification shows that the module meets the requirements of FCC Part 15 and Industry Canada license-exempt RSS standards for an intentional radiator.
Product Labeling The end product containing the HUM-A-900-PRO-UFL or HUM-A-900-PRO-CAS must be labeled to meet the FCC and IC product label requirements. It must have the below or similar text: Contains FCC ID: OJM-HUMA-900 / IC: 5840A-HUMA900 The label must be permanently affixed to the product and readily visible to the user.
Power Supply Requirements Interference Considerations The module does not have an internal voltage regulator, therefore it requires a clean, well-regulated power source. The power supply noise should be less than 20mV. Power supply noise can significantly affect the module’s performance, so providing a clean power supply for the module should be a high priority during design. The RF spectrum is crowded and the potential for conflict with unwanted sources of RF is very real.
Pad Layout Microstrip Details The pad layout diagrams below are designed to facilitate both hand and automated assembly. Figure 109 shows the footprint for the module. A transmission line is a medium whereby RF energy is transferred from one place to another with minimal loss. This is a critical factor, especially in high-frequency products like Linx RF modules, because the trace leading to the module’s antenna can effectively contribute to the length of the antenna, changing its resonant bandwidth.
Board Layout Guidelines The module’s design makes integration straightforward; however, it is still critical to exercise care in PCB layout. Failure to observe good layout techniques can result in a significant degradation of the module’s performance. A primary layout goal is to maintain a characteristic 50-ohm impedance throughout the path from the antenna to the module. Grounding, filtering, decoupling, routing and PCB stack-up are also important considerations for any RF design.
The module is housed in a hybrid SMD package that supports hand and automated assembly techniques. Since the modules contain discrete components internally, the assembly procedures are critical to ensuring the reliable function of the modules. The following procedures should be reviewed with and practiced by all assembly personnel. Hand Assembly Pads located on the bottom Soldering Iron of the module are the primary Tip mounting surface (Figure 113).
General Antenna Rules The following general rules should help in maximizing antenna performance. 1. Proximity to objects such as a user’s hand, body or metal objects will cause an antenna to detune. For this reason, the antenna shaft and tip should be positioned as far away from such objects as possible. 2. Optimum performance is obtained from a ¼- or ½-wave straight whip mounted at a right angle to the ground plane (Figure 116).
Common Antenna Styles There are hundreds of antenna styles and variations that can be employed with Linx RF modules. Following is a brief discussion of the styles most commonly utilized. Additional antenna information can be found in Linx Application Notes AN-00100, AN-00140, AN-00500 and AN-00501. Linx antennas and connectors offer outstanding performance at a low price. Whip Style A whip style antenna (Figure 119) provides outstanding overall performance and stability.
Regulatory Considerations Note: Linx RF modules are designed as component devices that require external components to function. The purchaser understands that additional approvals may be required prior to the sale or operation of the device, and agrees to utilize the component in keeping with all laws governing its use in the country of operation.
Notes –114– –115–
Linx Technologies 159 Ort Lane Merlin, OR, US 97532 Phone: +1 541 471 6256 Fax: +1 541 471 6251 www.linxtechnologies.com Disclaimer Linx Technologies is continually striving to improve the quality and function of its products. For this reason, we reserve the right to make changes to our products without notice. The information contained in this Data Guide is believed to be accurate as of the time of publication. Specifications are based on representative lot samples.
