HumPRC TM Series 900MHz Remote Control 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.
2^ 34^ 35^ 36^ 37^ 38^ 40^ 78^ 82^ 84^ 84^ 85^ 86^ 86^ 86^ 88^ 90^ 90^ 91^ 92^ 93^ 94^ 95^ 96^ 96^ 96^ 98^ 100^ 102^ Using the Low Power Features 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 HumPRCTM Series Long-Range Handheld Transmitter Usage Guidelines for FCC Compliance Additional Testing Requirements Information to the User Product Labeling FC
Electrical Specifications Ordering Information HumPRCTM Series Transceiver Specifications Ordering Information Part Number Description Parameter HUM-900-PRC 900MHz HumPRC™ Series Remote Control Transceiver, Castellation Interface, External Antenna Connection Power Supply HUM-900-PRC-CAS 900MHz HumPRC™ Series Remote Control Transceiver, Castellation Interface, External Antenna Connection, FCC & IC Certified HUM-900-PRC-UFL 900MHz HumPRC™ Series Remote Control Transceiver, Castellation Interface,
HumPRCTM Series Transceiver Specifications Parameter Symbol Min. HumPRCTM Series Transceiver Specifications Typ. Max. Units Notes Parameter Receiver Section Spurious Emissions –47 IF Frequency 304.7 dBm kHz Receiver Sensitivity 5 @min rate –98 –101 dBm 5 @max rate –91 –94 dBm 5 RSSI Dynamic Range 85 dB CSMA RSSI Threshold –70 dBm Min. Typ. Max. Units Notes Max Output Power PO Harmonic Emissions PH Output Power Range +8.
40.00 -40°C 39.50 35 25°C -40°C 30 85°C 25 20 Supply Current (mA) Supply Current (mA) 40 39.00 38.50 25°C 38.00 85°C 37.50 37.00 36.50 15 -5 0 5 2V 9 2.5V Figure 6: HumPRCTM Series Transceiver Average Current vs. Transmitter Output Power at 2.5V 40 3.6V Figure 9: HumPRCTM Series Transceiver TX Current vs. Supply Voltage at Max Power 23.40 25°C 38 -40°C 23.20 36 Supply Current (mA) Supply Current (mA) 3.
24.5 1.40 24.1 23.9 25°C 23.7 -40°C 23.5 85°C 1.20 85°C 23.3 23.1 22.9 Standby Current (µA) Supply Current (mA) 24.3 1.00 0.80 25°C 0.60 -40°C 0.40 0.20 22.7 22.5 2 2.1 2.2 2.3 2.4 2.5 2.6 2.7 2.8 2.9 3 0.00 2.5 3.1 3.2 3.3 3.4 3.5 3.6 3.3 Supply Voltage (V) 3.6 Supply Voltage (V) Figure 10: HumPRCTM Series Transceiver RX Scan Current vs. Supply Voltage, 9.6kbps Figure 12: HumPRCTM Series Transceiver Standby Current Consumption vs.
GND S4 4 14 9 10 11 12 13 GND 8 NC GND GND VCC RESET LNA_EN PA_EN CMD_DATA_OUT CMD_DATA_IN PB 5 6 7 8 9 10 11 12 13 Figure 16: HumPRCTM Series Transceiver Pre-certified Version Pin Assignments - UFL Connection (Top View) LATCH_EN 7 4 LATCH_EN 15 3 S4 POWER_DOWN 3 S5 ANT C1 GND S5 2 C0 GND 16 1 S6 GND 17 2 6 32 S7 S0 1 S6 5 GND S1 S7 18 S2 GND 19 31 S3 18 POWER_DOWN 32 C1 GND C0 ANT GND 19 S0 31 S1 ACK_OUT S2 GND S3 29 28 27 26 25 24
Module Dimensions Pin Descriptions Pin Number I/O Description If this line is high, then the status line outputs are latched (a received command to activate a status line toggles the output state). If this line is low, then the output lines are momentary (active for as long as a valid signal is received). Do not leave floating. 13 LATCH_EN I 19 ANTENNA — 50-ohm RF Antenna Port 21 VCC — Supply Voltage 22 2 RESET I This line resets the module when pulled low.
Theory of Operation Module Description The HumPRCTM Series transceiver is a low-cost, high-performance synthesized FSK transceiver. Figure 20 shows the module’s block diagram. The HumPRCTM Series remote control transceiver module is a completely integrated RF transceiver and processor that is designed to send the logic state of its inputs to a remote unit and replicate the logic states of the remote unit’s inputs. This allows for the easy creation of basic remote control systems.
Transceiver Operation Transmit Operation The transceiver has two roles: Initiating Unit (IU) that transmits control messages and Responding Unit (RU) that receives control messages. If all of the status lines are set as inputs, then the module is set as an IU only. In this role, the module stays in a low power sleep mode until a status line goes high, starting the Transmit Operation. When a status line input goes high, the module enters the Initiating Unit role.
System Operation Transmitters and receivers are paired using the built-in Join Process (see the Join Process for details). One device is configured as an Administrator and creates the network address and encryption key. When Nodes join, the Administrator sends them the encryption key, network address and their unique address within the network.
Frequency Hopping Spread Spectrum Addressing Modes 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 RF data rate and hopping sequence to communicate.
AES Encryption The Join Process HumPRCTM Series modules offer 128-bit AES encryption. Encryption algorithms are complex mathematical calculations that use a large number called a key to scramble data before transmission. This is done so that unauthorized persons who may intercept the signal cannot access the data. To decrypt the data, the receiver must use the same key that was used to encrypt it. It performs the same calculations as the transmitter and if the key is the same, the data is recovered.
A module becomes a node by joining with an administrator. This is done by pressing and releasing the PB button on both units. The modules automatically search for each other using a special protocol. When they find each other, the administrator sends the node the encryption key, UMASK and its network address. The UDESTID is set to the network broadcast address. The values are encrypted using a special factory-defined key.
Operation with the HumPROTM Series The commands from the HumPRC Series module can be received by a HumPROTM Series transceiver and vice versa. The modules should be joined using the normal Join Process. The IU sends a REMOTE_ACTIVATE packet and accepts a REMOTE_CONFIRM reply. TM A microcontroller connected to the HumPROTM Series can be programmed to take action based on the STATUS byte in a REMOTE_ACTIVATE packet that is received from a HumPRCTM Series module.
Acknowledgement Configuring the Status Lines A responding module is able to send an acknowledgement to the transmitting module. This allows the initiating module to know that the responding side received the command. Each of the eight status lines can operate as a digital input or output. The line direction is determined by bit 0 (ENC01) in the RCCTL register. By default, this bit is 1, meaning that the status line directions are determined by the logic states of the C0 and C1 lines.
Using the MODE_IND Line Figure 26 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 25 shows the different blink patterns and their meanings. HumPRCTM Series Transceiver MODE_IND Line Timing Display [on/off time in seconds] Module Status Join Operation Two quick blinks Administrator 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 Reading from Registers The HumPRCTM 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 30.
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 32 shows the command and response. HumPRCTM Series CRC Error Count Figure 34 shows the RF channels used by the HumPRCTM Series.
HumPRCTM Series Hop Sequences by Channel Number for 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 37 shows the command and response and Figure 38 available power settings and typical power outputs for the module. The default setting is 0x03.
MAXTXRETRY - Maximum Transmit Retries Volatile Address = 0x52; Non-Volatile Address = 0x07 The value in the MAXTXRETRY register sets the number of transmission retries performed if an acknowledgement is not received. If an acknowledgement is not received after the last retry, exception EX_ NORFACK is raised. Figure 41 shows examples of the command.
ENCSMA - CSMA Enable Volatile Address = 0x56; Non-Volatile Address = 0x0B Carrier-Sense Multiple Access (CSMA) is a best-effort transmission protocol that listens to the channel before transmitting a message. If another device is already transmitting on the same channel when a message is ready to send, the module waits before sending its payload or changes to an unused channel. This helps to eliminate RF message corruption at the expense of additional latency. By default, CSMA is enabled.
WAKEACK - ACK on Wake Volatile Address = 0x59; Non-Volatile Address = 0x0E When UART Acknowledge on Wake is enabled, the module sends an ACK (0x06) character out of the CMD_DATA_OUT line after the module resets or wakes from sleep. This indicates that the module is ready to accept data and commands. A value of 0x01 enables this feature; 0x00 disables it. The default value is 0x01. Figure 49 shows examples of the commands and Figure 50 shows the available values.
USRCID - User Source Address Volatile Address = 0x5E-0x61; Non-Volatile Address = 0x13-0x16 These registers contain the address of the module when User Addressing mode or Extended User Addressing mode are enabled. User Addressing mode uses bytes 0 and 1 to determine the source address for both transmitted messages and matching received messages. Extended User Addressing mode uses all four bytes. When the COMPAT register is 0x02 in User Address mode, bytes 3 and 2 must be 0.
DESTDSN - Destination Serial Number Volatile Address = 0x68-0x6B; Non-Volatile Address = 0x1D-0x20 These registers contain the serial number of the destination module when DSN Addressing Mode is enabled. Please see the Addressing Modes section for more details. Each register byte is read and written separately. RCCTL - RC Control Volatile Address = 0x6D; Non-Volatile Address = 0x22 This register controls RC behavior. HumPRCTM Series RC Control Read Command Figure 54 shows the Destination DSN registers.
CMDHOLD - CMD Halts Traffic Volatile Address = 0x6E; Non-Volatile Address = 0x23 This register selects options for transferring packet data in the HumPROTM Series. These options are controlled automatically by the HumPRCTM application and do not have any effect on its operation. RCDIR - RC Status Line Direction Select Volatile Address = 0x6F; Non-Volatile Address = 0x24 This register controls the direction of the associated status line. When bit n is 1, status line Sn is an input line.
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 59 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 62 shows examples of the commands and Figure 63 lists current releases to date. HumPRCTM Series Release Number RCSLS - RC Status Line States Volatile Address = 0x7A This register contains the debounced state of the status lines. When status line Sn is high, bit n is 1. When low, bit n is 0. The register reflects the state of both input and output status lines.
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. HumPRCTM Series Command Register When the Join Process is started the KEYRCV flag in the SECOPT register determines whether the module is an administrator or node and whether a key can be sent or changed. The Join Process uses and modifies the non-volatile address registers. After a successful Join, the modified non-volatile registers are copied to the corresponding volatile registers.
to the volatile location (NKV). This allows a sophisticated system to change the keys during operation and quickly revert back to the default key. The Non-volatile Reset command (FF 07 FE 47 20 FE 2A FE 3B) sets all non-volatile registers to their default values. When the configuration is reset, the following message, shown in quotes, is sent out the UART at the current baud rate, then the module is reset, similar to a power cycle: “\r\nConfiguration Reset\r\n”.
EEXFLAG - Extended Exception Flags Volatile Address = 0xCD - 0xCF These volatile registers contain flags for various events. They provide a separate bit for each exception. HumPRCTM 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.
EEXMASK - Extended Exception Mask Volatile Address = 0xD0-0xD2; Non-Volatile Address = 0x80-0x82 These registers contain a mask for the events in EEXFLAG, using the same offset and bit number. HumPRCTM Series Extended Exception Mask Registers LASTNETAD - Last Network Address Assigned Non-Volatile Address = 0x8C-0x8F These bytes contain the last address assigned using the Join Process. When a new unit joins the network, it is assigned the next address and this value is incremented in the administrator.
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.
Typical Applications VCC Series module VCC VCC S4 21 17 16 15 14 GND GND GND GND GND 13 12 11 9 8 7 5 A VCC VCC VCC VCC VCC VCC 21 VCC RESET 22 23 LNA_EN PA_EN 24 25 GND 26 CMD_DATA_OUT CMD_DATA_IN 27 S0 LATCH_EN POWER_DOWN C1 GND 13 12 C0 GND 11 GND 9 10 5 S0 S4 S3 B ACK_EN GND S6 S1 4 GND S5 S3 S4 3 ANT GND 8 S5 2 GND S7 S1 S6 1 GND S2 S7 ACK_OUT 7 32 VCC MODE_IND S2 31 6 30 GND 28 29 PB GND GND GND VCC VCC GND VCC GND G
Figure 88 shows a typical circuit using the HumPRCTM Series transceiver with an external microcontroller.
HumPRCTM Series Long-Range Handheld Transmitter The HumPRC Series Long-Range Handheld Transmitter is ideal for general-purpose remote control and command applications. It incorporates the HumPRCTM Series remote control transceiver, antenna and a coin-cell battery into a plastic enclosure. A membrane switch array is used to activate the unit. An LED embedded into the membrane switch indicates acknowledgement from the remote device. It has a transmission range of up to 1,300m (0.
Usage Guidelines for FCC Compliance Information to the User The pre-certified versions of the HumPRCTM Series module (HUM-900-PRC-UFL and HUM-900-PRC-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-900-PRC-UFL or HUM-900-PRC-CAS must be labeled to meet the FCC and IC product label requirements. It must have the below or similar text: Contains FCC ID: OJM900MCA / IC: 5840A-900MCA The label must be permanently affixed to the product and readily visible to the user.
14.00mil 1.4mil FR-4 (Er = 4.6) Dielectric 2 28.00mil FR-4 (Er = 4.6) Mid-Layer 2 Dielectric 3 1.4mil 14.00mil Copper FR-4 (Er = 4.6) Copper 380 619 216 Bottom Layer 1.4mil Copper ANT-916-CW-QW ANT-916-CW-HW ANT-916-WRT-RPS Dielectric 1 Mid-Layer 1 Microstrip Width = 24mil Ground plane on Mid-Layer 1 Units are in mils Thickness Material Copper 1.
Power Supply Requirements Interference Considerations Vcc TO MODULE 10Ω Vcc IN + 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.
Pad Layout Microstrip Details The pad layout diagrams below are designed to facilitate both hand and automated assembly. Figure 95 shows the footprint for the standard version and Figure 96 shows the footprint for the pre-certified version. A transmission line is a medium whereby RF energy is transferred from one place to another with minimal loss.
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 100).
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 103).
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 106) 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.
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.