| all | frequencies |
|
|
|
|
|
exhibits | applications |
|---|---|---|---|---|---|---|---|---|
| manuals | ||||||||
| app s | submitted / available | |||||||
|---|---|---|---|---|---|---|---|---|
| 1 2 |
|
User Guide - PRO | Users Manual | 2.63 MiB | May 06 2015 | |||
| 1 2 |
|
User Guide - RC | Users Manual | 2.60 MiB | May 06 2015 | |||
| 1 2 |
|
User Manual - PRC | Users Manual | 2.29 MiB | ||||
| 1 2 |
|
User Manual - Pro | Users Manual | 2.75 MiB | ||||
| 1 2 |
|
User Manual - RC | Users Manual | 2.66 MiB | ||||
| 1 2 |
|
Class II Permissive Change Letter | Cover Letter(s) | 223.66 KiB | ||||
| 1 2 |
|
Letter of Authority and Anti-Drug Abuse | Attestation Statements | 293.23 KiB | ||||
| 1 2 |
|
Non-duplicate Submittal Letter | Attestation Statements | 204.14 KiB | ||||
| 1 2 | RF Exposure Info | |||||||
| 1 2 | Test Report | May 06 2015 | ||||||
| 1 2 | Test Report | May 06 2015 | ||||||
| 1 2 | Test Report | May 06 2015 | ||||||
| 1 2 | Test Report | May 06 2015 | ||||||
| 1 2 | Test Report | May 06 2015 | ||||||
| 1 2 | Test Report | May 06 2015 | ||||||
| 1 2 | Test Report | May 06 2015 | ||||||
| 1 2 | Attestation Statements | May 06 2015 | ||||||
| 1 2 | Cover Letter(s) | May 06 2015 | ||||||
| 1 2 | External Photos | May 06 2015 | ||||||
| 1 2 | ID Label/Location Info | May 06 2015 | ||||||
| 1 2 | ID Label/Location Info | May 06 2015 | ||||||
| 1 2 | ID Label/Location Info | May 06 2015 | ||||||
| 1 2 | ID Label/Location Info | May 06 2015 | ||||||
| 1 2 | ID Label/Location Info | May 06 2015 | ||||||
| 1 2 | Internal Photos | May 06 2015 | ||||||
| 1 2 | RF Exposure Info | May 06 2015 | ||||||
| 1 2 | Attestation Statements | May 06 2015 | ||||||
| 1 2 | Test Report | May 06 2015 | ||||||
| 1 2 | Test Report | May 06 2015 | ||||||
| 1 2 | Test Report | May 06 2015 | ||||||
| 1 2 | Test Report | May 06 2015 | ||||||
| 1 2 | Test Report | May 06 2015 | ||||||
| 1 2 | Test Report | May 06 2015 | ||||||
| 1 2 | Test Report | May 06 2015 | ||||||
| 1 2 | Test Report | May 06 2015 | ||||||
| 1 2 | Test Report | May 06 2015 | ||||||
| 1 2 | Test Report | May 06 2015 | ||||||
| 1 2 | Test Setup Photos | May 06 2015 | ||||||
| 1 2 | Test Setup Photos | May 06 2015 | ||||||
| 1 2 | Test Setup Photos | May 06 2015 |
| 1 2 | User Guide - PRO | Users Manual | 2.63 MiB | May 06 2015 |
HumPROTM Series 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. No OEM Linx Remote Control or Function Module should be modified for Life and Property Safety Situations. Such modification cannot provide sufficient safety and will void the products regulatory certification and warranty. Customers may use our (non-Function) Modules, Antenna and Connectors as part of other systems in Life Safety Situations, but only with necessary and industry appropriate redundancies and in compliance with applicable safety standards, including without limitation, ANSI and NFPA standards. It is solely the responsibility of any Linx customer who uses one or more of these products to incorporate appropriate redundancies and safety standards for the Life and Property Safety Situation application. Do not use this or any Linx product to trigger an action directly from the data line or RSSI lines without a protocol or encoder/
decoder to validate the data. Without validation, any signal from another unrelated transmitter in the environment received by the module could inadvertently trigger the action. All RF products are susceptible to RF interference that can prevent communication. RF products without frequency agility or hopping implemented are more subject to interference. This module does have a frequency hopping protocol built in, but the developer should still be aware of the risk of interference. Do not use any Linx product over the limits in this data guide. Excessive voltage or extended operation at the maximum voltage could cause product failure. Exceeding the reflow temperature profile could cause product failure which is not immediately evident. Do not make any physical or electrical modifications to any Linx product. This will void the warranty and regulatory and UL certifications and may cause product failure which is not immediately evident. Table of Contents 1 Description 1 Features 2 Ordering Information 2 Absolute Maximum Ratings 3 Electrical Specifications 5 Typical Performance Graphs 10 Pin Assignments 10 Pin Descriptions 12 Pre-Certified Module Pin Assignments 13 Module Dimensions 14 Theory of Operation 15 Module Description 16 Overview 18 Addressing Modes 20 Automatic Addressing 20 Address Register Use 21 Acknowledgements and Assured Delivery 22 Frequency Hopping Spread Spectrum 23 Compatibility with the 250 Series 23 Networking 24 Transmitting Packets 25 Receiving Packets 29 Using the Buffer Empty (BE) Line 30 Exception Engine 32 Carrier Sense Multiple Access (CSMA) 33 Using the Command Response (CRESP) Line 34 Using the CMD Line 34 External Amplifier Control 35 AES Encryption 38 Using the MODE_IND Line 39 Using the PB Line 40 Restore Factory Defaults 40 Using the Low Power Features 42 The Command Data Interface 43 Reading from Registers 44 Writing to Registers 45 Command Length Optimization 45 Example Code for Encoding Read/Write Commands 48 The Command Data Interface Command Set 95 Typical Applications 96 Usage Guidelines for FCC Compliance 96 Additional Testing Requirements 97 Information to the user 98 Product Labeling 98 FCC RF Exposure Statement 98 Antenna Selection 100 Castellation Version Reference Design 102 Power Supply Requirements 102 Antenna Considerations 103 Interference Considerations 104 Pad Layout 105 Microstrip Details 106 Board Layout Guidelines 107 Helpful Application Notes from Linx 108 Production Guidelines 108 Hand Assembly 108 Automated Assembly 110 General Antenna Rules 112 Common Antenna Styles 114 Regulatory Considerations HumPROTM Series RF Transceiver Module Data Guide Description The HumPROTM Series is a frequency hopping spread spectrum (FHSS) transceiver designed for the reliable transfer of digital data. It has a very fast lock time so that it can quickly wake up, send data and go back to sleep, saving power in battery-powered applications. The module is available in the 915MHz frequency band. 0.55"
(13.97) 0.45"
(11.43) 0.07"
(1.78) Figure 1: Package Dimensions The module has several features that increase the data transfer reliability. It ensures that no other modules are transmitting before it begins transmitting data. Automatic acknowledgements ensure that the remote side received valid data. Multiple hopping patterns enable several systems to operate in proximity without interference. A standard UART interface is used for module configuration and data transfer. A few simple serial commands are all that are needed for configuration. All modules have a unique 32-bit serial number that can be used as an address. Source and destination addressing support point-to-point and broadcast links. Address masking by the receiving module allows for creating subnets. Other network topologies can also be implemented. Housed in a tiny compact reflow-compatible SMD package, the transceiver requires no external RF components except an antenna, which greatly simplifies integration and lowers assembly costs. Versions are available that have obtained FCC and Industry Canada modular certification. Features FHSS Algorithm Fast Lock (<30ms at 115kbps) Low power modes FCC and IC Pre-certified version Simple UART interface No external RF components required No production tuning required Tiny PLCC-32 footprint 1 Revised 4/8/2015 Ordering Information Ordering Information Part Number Description HUM-900-PRO HumPROTM Series Data Transceiver HUM-900-PRO-CAS HumPROTM Series Data Transceiver with Castellation Connection HUM-900-PRO-UFL HumPROTM Series Data Transceiver with u.FL Connector EVM-900-PRO HumPROTM Series Carrier Board EVM-900-PRO-CAS HumPROTM Series Carrier Board with Certified module, Castellation Connection EVM-900-PRO-UFL HumPROTM Series Carrier Board with Certified module, UFL Connector MDEV-900-PRO HumPROTM Series Master Development System Figure 2: Ordering Information Absolute Maximum Ratings Absolute Maximum Ratings Supply Voltage Vcc Any Input or Output Pin RF Input Operating Temperature Storage Temperature 0.3 0.3 40 40 to to 0 to to
+3.9 VCC + 0.3
+85
+85 VDC VDC dBm C C Exceeding any of the limits of this section may lead to permanent damage to the device. Furthermore, extended operation at these maximum ratings may reduce the life of this device. Figure 3: Absolute Maximum Ratings Warning: This product incorporates numerous static-sensitive components. Always wear an ESD wrist strap and observe proper ESD handling procedures when working with this device. Failure to observe this precaution may result in module damage or failure. Electrical Specifications HumPROTM Series Transceiver Specifications Parameter Power Supply Operating Voltage TX Supply Current 900MHz at +10dBm 900MHz at 0dBm RX Supply Current Power-Down Current RF Section Operating Frequency Band HUM-900-PRO-xxx Number of hop channels
@ 19.2kbps RF Rate
@ 152.34kbps RF Rate Channel spacing
@ 19.2kbps RF Rate
@ 152.34kbps RF Rate 20 dB OBW
@ 19.2kbps RF Rate
@ 152.34kbps RF Rate Receiver BW
@ 19.2kbps RF Rate
@ 152.34kbps RF Rate FSK deviation
@ 19.2kbps RF Rate
@ 152.34kbps RF Rate Scan time / channel (avg)
@ 19.2kbps RF Rate
@ 152.34kbps RF Rate FHSS Lock time
@ 19.2kbps RF Rate
@ 152.34kbps RF Rate Modulation Data Encoding Number of Hop Sequences Symbol Min. Typ. Max. Units Notes VCC lCCTX lCCRX lPDN FC 2.0 3.6 VDC 1,2 1,2 1,2,3 1,2 41.5 24 24.5 6 928 mA mA mA A MHz MHz kHz kHz kHz kHz kHz kHz kHz kHz ms ms ms ms 902 40.5 22 23.5 0.7 50/64 26/32 375.9 751.81 64 315 102 232 19.2 51 1.2 0.335 63 26 2FSK 6/7 RLL 6 2 3 HumPROTM Series Transceiver Specifications HumPROTM Series Transceiver Specifications Symbol Min. Typ. Max. Units Notes Symbol Min. Typ. Max. Units Notes Parameter Receiver Section Spurious Emissions IF Frequency Receiver Sensitivity HUM-900-PRO-xxx @
min rate HUM-900-PRO-xxx @
max rate RSSI Dynamic Range CSMA RSSI Threshold Transmitter Section Output Power HUM-900-PRO-xxx Harmonic Emissions Output Power Range HUM-900-PRO-xxx Antenna Port RF Impedance Environmental Operating Temp. Range Timing Module Turn-On Time Via VCC Via POWER_DOWN Via Standby Serial Command Response Volatile R/W NV Update Factory Reset Channel Dwell Time 98 91
+8.5 5 40 51.7 PO PH PH RIN 304.7 101 94 85 70
+9.5 41 50 4 4 0.4 2.2 107 47 dBm kHz dBm dBm dB dBm dBm dBc 9 dB
+85 129.5 5 31.5 400 C ms ms ms ms ms ms ms ms 5 5 5 6 6 6 4 4 4 4 4 8 8 8 CMD low to trigger TX with option TXnCMD tTXnCMD 2 Interface Section UART Data rate 9,600 115,200 bps 0.3*VCC VDC VDC 0.3*VCC VDC VDC 0.3*VCC 10 Bits 1,9 1,9 1,10 1,10 11 cycles 12 22,000 8. From end of command to start of response 9. 60mA source/sink 10. 6mA source/sink 11. End of CMD_DATA_OUT stop bit to change in CRESP 12. Number of register write operations Parameter Input Logic Low Logic High Output Logic Low, MODE_IND, BE Logic High, MODE_IND, BE Logic Low Logic High CRESP Hold Time VIL VIH VOLM VOHM VOL VOH 0.7*VCC 0.7*VCC 0.7*VCC Flash (Non-Volatile) Memory Specifications Flash Write Cycles Input power < -60dBm 1. Measured at 3.3V VCC 2. Measured at 25C 3. 4. Characterized but not tested 5. PER = 5%
6. Into a 50-ohm load 7. No RF interference Figure 4: Electrical Specifications Typical Performance Graphs
) m B d
(
r e w o P t t u p u O X T 11.0 10.5 10.0 9.5 9.0 8.5
-40C 25C 85C 3.6 2.0 2.5 3.3 Supply Voltage (V) Figure 5: HumPROTM Series Transceiver Max Output Power vs. Supply Voltage - HUM-900-PRO 4 5
) A m
(
t n e r r u C y p p u S l 40 35 30 25 20 15 25C
-40C 85C
) A m
(
t n e r r u C y p p u S l 40.00 39.50 39.00 38.50 38.00 37.50 37.00 36.50
-40C 25C 85C
-5 0 5 9 2V 2.5V 3.3V 3.6V TX Output Power (dBm) Supply Voltage (V) Figure 6: HumPROTM Series Transceiver Average Current vs. Transmitter Output Power at 2.5V - HUM-900-PRO Figure 9: HumPROTM Series Transceiver TX Current vs. Supply Voltage at Max Power - HUM-900-PRO
) A m
(
t n e r r u C y p p u S l 40 38 36 34 32 30 28 26 24 22 20 25C
-40C 85C
) A m
(
t n e r r u C y p p u S l 23.40 23.20 23.00 22.80 22.60 22.40 22.20 22.00
-40C 25C 85C
-5 0 5 9 2V 2.5V 3.3V 3.6V TX Output Power (dBm) Supply Voltage (V) Figure 7: HumPROTM Series Transceiver Average TX Current vs. Transmitter Output Power at 3.3V -HUM-900-PRO Figure 8: HumPROTM Series Transceiver TX Current vs. Supply Voltage at 0dBm - HUM-900-PRO 6 7
) A m
(
t n e r r u C y p p u S l 24.5 24.3 24.1 23.9 23.7 23.5 23.3 23.1 22.9 22.7 22.5 85C 25C
-40C
) A
(
t n e r r u C y b d n a S t 1.40 1.20 1.00 0.80 0.60 0.40 0.20 0.00 85C 25C
-40C 2 2.1 2.2 2.3 2.4 2.5 2.6 2.7 2.8 2.9 3 Supply Voltage (V) 3.1 3.2 3.3 3.4 3.5 3.6 2.5 3.3 Supply Voltage (V) 3.6 Figure 10: HumPROTM Series Transceiver RX Scan Current vs. Supply Voltage, 9.6kbps - HUM-900-PRO Figure 12: HumPROTM Series Transceiver Standby Current Consumption vs. Supply Voltage - HUM-900-PRO Current consumption while the module is scanning for a transmission. The current is approximately 0.5mA higher when receiving data at 9.6kbps.
) A m
(
t n e r r u C y p p u S l 23 22.8 22.6 22.4 22.2 22 21.8 21.6 21.4 21.2 21 85C 25C
-40C
) m B d
(
g n d a e R i I S S R
-15.00
-25.00
-35.00
-45.00
-55.00
-65.00
-75.00
-85.00
-95.00
-105.00
-40C 25C 85C 2 2.1 2.2 2.3 2.4 2.5 2.6 2.7 2.8 2.9 3 Supply Voltage (V) 3.1 3.2 3.3 3.4 3.5 3.6
-100.00 -90.00 -80.00 -70.00 -60.00 -50.00 -40.00 -30.00 -20.00 -10.00 0.00 Input Power (dBm) Figure 11: HumPROTM Series Transceiver RX Scan Current vs. Supply Voltage, 115.2kbps - HUM-900-PRO Figure 13: HumPROTM Series Transceiver RSSI Voltage vs. Input Power - HUM-900-PRO Current consumption while the module is scanning for a transmission. The current is approximately 2mA higher when receiving data at 115.2kbps. 8 9 Pin Assignments T U O _ A T A D _ D M C I N _ A T A D _ D M C S T C B P N E _ A N L T E S E R N E _ A P D N G C C V 29 28 27 26 25 24 23 22 21 MODE_IND BE NC NC NC NC NC 30 31 32 1 2 3 4 20 19 18 17 16 15 14 GND ANT GND GND GND GND GND 5 6 78 9 10 11 12 13 C N C N P S E R C X E D N G C N C N D M C N W O D _ R E W O P Figure 14: HumPROTM Series Transceiver Pin Assignments (Top View) Pin Descriptions Pin Descriptions Pin Number 1, 2, 3, 4, 5, 6, 10, 11, 32 7 8 Name NC CRESP EX I/O Description No Electrical Connection. Do not connect any traces to these lines. 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. Exception Output. A mask can be set to take this line high when an exception occurs. 9, 14, 15, 16, 17, 18, 20, 25 GND Ground 12 POWER_DOWN I Power Down. Pulling this line low places the module into a low-power state. The module is not functional in this state. Pull high for normal operation. Do not leave floating. Pin Descriptions Pin Number Name I/O Description 13 19 21 22 23 24 26 27 28 29 30 31 CMD I Command Input. When this line is low, incoming bytes are command data. When high, incoming bytes are data to be transmitted. ANTENNA 50-ohm RF Antenna Port VCC Supply Voltage RESET LNA_EN PA_EN I O O This line resets the module when pulled low. It should be high for normal operation. This line has an internal 10k resistor to supply, so leave it unconnected if not used. Low Noise Amplifier Enable. This line is driven high when receiving. It is intended to activate an optional external LNA. Power Amplifier Enable. This line is driven high when transmitting. It is intended to activate an optional external power amplifier. CMD_DATA_OUT O Command Data Out. Output line for data and serial commands CMD_DATA_IN I CTS PB O I MODE_IND O BE O Command Data In. Input line for data (CMD is high) and serial commands (CMD is low). UART Clear To Send, active low. This line indicates to the host microcontroller when the module is ready to accept data. When CTS is high, the module is busy. When CTS is low, the module is ready for data. Push Button input. This line can be connected to Vcc through a normally open push button. Button sequences can reset configurations to default and join modules into a network. Mode Indicator. This line indicates module activity. It can source enough current to drive a small LED, causing it to flash. The duration of the flashes indicates the modules current state. Buffer Empty. This line is high when the UART input buffer is empty, indicating that all data has been transmitted. If acknowledgment is active, it also indicates that the receiving module has acknowledged the data or a retry exception has occurred. Figure 15: HumPROTM Series Transceiver Pin Descriptions 10 11 Pre-Certified Module Pin Assignments The pre-certified version of the module has mostly the same pin assignments as the standard version. The antenna connection is routed to either a castellation (-CAS) or a u.FL connector (-UFL), depending on the part number ordered. The antenna pad is disconnected on the version with the connector. The RF is routed as shown in Figure 16 for the version without the connector. T U O _ A T A D _ D M C I N _ A T A D _ D M C S T C B P N E _ A N L T E S E R N E _ A P D N G C C V 29 28 27 26 25 24 23 22 21 MODE_IND BE NC NC NC NC NC 30 31 32 1 2 3 4 T N A 19 D N G 18 5 6 78 9 10 11 12 13 C N C N P S E R C X E D N G C N C N D M C N W O D _ R E W O P Figure 16: HumPROTM Series Transceiver Pre-certified Version Pin Assignments (Top View) Module Dimensions 0.55"
(13.97) 0.45"
(11.43) 0.07"
(1.78) 0.812"
(20.62) 0.271"
(6.88) 0.078"
(1.98) 0.195"
(4.96) Figure 17: HumPROTM Series Transceiver Dimensions 0.45"
(11.43) 0.116"
(2.95) Figure 18: HumPROTM Series Transceiver Pre-certified Version Dimensions 12 13 Theory of Operation The HumPROTM Series transceiver is a low-cost, high-performance synthesized FSK / MSK transceiver. Figure 19 shows the modules block diagram. ANTENNA ADC ADC R O T A L U D O M E D 0 90 FREQ SYNTH MODULATOR LNA PA PROCESSOR INTERFACE GPIO /
INTERFACE Figure 19: HumPROTM Series Transceiver RF Section Block Diagram The HumPROTM Series transceiver operates in the 902 to 928MHz frequency band. The transmitter output power is programmable. The range varies depending on the antenna implementation and the local RF environment. The RF carrier is generated directly by a frequency synthesizer that includes an on-chip VCO. The received RF signal is amplified by a low noise amplifier (LNA) and down-converted to I/Q quadrature signals. The I/Q signals are digitized by ADCs. A low-power onboard communications processor performs the radio control and management functions including Automatic Gain Control
(AGC), filtering, demodulation and packet synchronization. A control processor performs the higher level functions and controls the serial and hardware interfaces. A crystal oscillator generates the reference frequency for the synthesizer and clocks for the ADCs and the processor. Module Description 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. When the module does not have data to send it scans all of the channels for incoming data. If it finds a valid preamble, it pauses and looks for the start of a packet. When it receives a valid packet with a matching destination address the module outputs the data through the UART. The transmitting module accepts packets through its UART until a configurable number of bytes is reached or a configurable timeout expires between bytes on the UART. At this point the module transmits the packet. When the module has data to send it goes to the next channel in its hopping pattern. It measures the RSSI on that channel to ensure that the channel is clear. If the RSSI check passes, then it transmits the packets. If the RSSI fails, then it implements a random wait time and tries again. When the channel is clear, the module transmits the data. The module can stay on one channel for up to 400ms. If the module is ready to start transmitting near the end of the channel time, it transmits the number of bytes that it can in the remaining time. It then hops to the next channel in its hopping pattern to transmit the remaining data. The module supports automatic acknowledgements for assured delivery. When enabled, the receiving module responds to a valid transmission with an acknowledgement to let the transmitting module know that it received the data. If an acknowledgement is not received then the transmitting module repeats the transmission for a configurable number of retries. If the retry limit is exceeded without an acknowledgement then the transmitting module issues an exception error to let the host micro know of the communication problem. A standard UART interface is used to configure the module for operation and for the data input and output. This is suitable for direct connection to UARTs on many microcontrollers, USB converters and RS-232 converters. A simple command set is used for configuration and control. Modules can be pre-configured for fixed point-to-point or broadcast topologies allowing streaming data (no commands) during operation. 14 15 Overview The HumPROTM 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. 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. The addressing and masking allow for the creation of point-to-point, many-to-one and one-to-many wireless links. This allows the creation of many network topologies, such as star, tree and mesh. The routing for the network topology is managed outside the module. The addressing is the primary configuration when getting started with the modules. RG-00105, the HumPROTM Addressing Mode Reference Guide has details about configuring the addressing. Acknowledgements and Assured Delivery The modules support assured delivery in the form of acknowledgements and retries. When the acknowledgements are enabled, the receiving device sends an acknowledge message to let the sender know that the transmission was received. If the sender does not get an acknowledgement it resends the message up to a configurable number of retries. If there is still no acknowledgement, the module triggers an exception to let the host processor know of the error. Command Mode and Data Mode The module has two main interface modes controlled by the state of the CMD line. Command mode routes the data coming in on the CMD_DATA_ IN line to the processor for configuring the module. Data mode routes the data to the transmitter for transmission over-the-air. The CMD line is normally controlled by an external microcontroller. Streaming Data and Explicit Packets The modules default configuration is for streaming data. At some UART rates the module sends the data at a higher rate over-the-air than it is input on the UART. This hides the time required for the protocol transactions and the frequency hopping. The result is that the data appears to stream through the module with no breaks in the data apparent to the host processor. Alternatively, the module can be configured for explicit packet transmission. This allows the host processor to control when packets are sent and what data is in each packet Exceptions and Host Processor Interface The module has several indicator lines that provide feedback to the host processor on the modules operation and current status. This includes an exception line (EX) that informs the processor when errors occur so that it can take steps to manage the issue gracefully. The state of the status lines can also be read through the modules Command Data Interface to reduce the number of hardware connections that are required. Command Data Interface The module has a Command Data Interface that consists of a set of serial commands entered through a UART. These are shorter and simpler than AT commands that are popular with many modules. These commands control the configuration of the module as well as allow feedback on the operation and status of the module. Carrier Sense Multiple Access (CSMA) The module implements a Carrier Sense Multiple Access method. It listens to the channel and makes sure that it is clear before it transmits. If the channel is in use, the module either waits for it to clear or hops to the next channel depending on its current state. This reduces the overall potential for interference and improves the robustness of the link. Encryption The module supports AES-128 encryption to provide a secure wireless link. All of the modules must have encryption enabled and be using the same key in order for communication to be successful. There are two ways of entering an encryption key: directly by writing the key to registers through the Command Data Interface or through a JOIN process. 16 17 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. There are three addressing modes: DSN, User and Extended User. Each mode offers different communications methods, but all use source and destination addressing. The source address is for the transmitting unit, the destination address is the intended receiver. Each mode uses different registers for the source and destination addresses. All three addressing modes can be configured to be compatible with the older 250 Series modules. The default operation has an additional level of masking on the receiving module that helps prevent interference from adjacent networks. The following sections give brief descriptions of the three modes, but a detailed explanation and examples are given in RG-00105, the HumPROTM Addressing Mode Reference Guide. DSN Addressing Mode Device Serial Number Addressing mode is the simplest mode and supports point-to-point communications. Each module is programmed at the factory with a unique 4-byte serial number that cannot be changed. These bytes are found in the non-volatile read-only MYDSN registers
(MYDSN[3-0]). DSN Addressing mode uses this serial number as an address. The transmitting units DSN is used as the source address and the intended receivers DSN is written into the destination address registers
(DESTDSN[3-0]). All modules within range hear the transmission, but only the module with the serial number that matches the destination address outputs the data on its UART. All others ignore the transmission. User Addressing Mode User Addressing Mode is a more flexible method than DSN Addressing Mode. It uses the customer ID bytes (CUSTID[1-0]) for unencrypted messages and two of the user destination bytes (UDESTID[1-0]) as a destination address. The customer ID bytes are programmed at the factory and cannot be changed. These are determined by the factory for specific customers to prevent their systems from operating with any other systems. Contact Linx for more details. The modules local address is contained in two of the user source ID registers (USRCID[1-0]). In this mode, USRCID [1-0] contain the node address and USRCID [3-2] must be 0 in the receiver. In normal operation each module has a user ID mask (UMASK[3-0]) that splits the 32 address bits into up to three fields to provide a network address and address fields for sub-networks, supporting both individual addressing and broadcast addressing within the users network. A detailed explanation and examples are given in Reference Guide RG-00105. The 16 bits in the UDESTID[1-0] registers are transmitted. The upper 16 bits of USRCID[3-2] in the receiver must be 0. If acknowledgements are enabled, only the module with a user source ID that exactly matches the transmitted user destination ID responds. The mask is not used for this determination. Extended User Addressing Mode Extended User Addressing mode is the same as User Addressing mode but uses 32-bit addresses. The two customer ID bytes are still used (CUSTID[1-0]) but four bytes are used for the user destination address (UDESTID[3-0]), user source ID (USRCID[3-0]) and user ID mask
(UMASK[3-0]). This provides more addressing capabilities at the expense of more overhead in the packet. 18 19 Automatic Addressing 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. Address Register Use Figure 20 shows the address registers that are used with each addressing mode. HumPROTM Series Transceiver Address Registers COMPAT 0x00 (Relaxed Addressing) 0x02 (Normal Addressing) ADDMODE UDESTID[3-0]
UDESTID[1-0]
USRC[3-0]
USRC[1-0]
UMASK[3-0]
UMASK[1-0]
0x04
(DSN) 0x14
(DSN
+ACK) 0x06
(User) 0x16
(User
+ACK) 0x07
(Ex User) 0x17
(ExUser
+ACK) 0x04
(DSN) 0x14
(DSN
+ACK) 0x06
(User) 0x16
(User
+ACK) 0x07
(Ex User) 0x17
(ExUser
+ACK) X X X X X X X X X X X X DESTDSN[3-0]
X X Figure 20: HumPROTM Series Transceiver Address Register Use Acknowledgements and Assured Delivery When a module transmits with assured delivery enabled, the receiving module returns an acknowledgement packet. The transmitting module waits for this acknowledgement for a preset amount of time based on the data rate. If an acknowledgement is not received, it retransmits the packet. If the receiver receives more than one of the same packet, it discards the duplicate packet contents but sends an acknowledgment. This way, duplicate data is not output by the module. If the received destination address matches the local address, the receiving module immediately sends an acknowledgement. This packet lets the sending module know that the message has been received. An acknowledgement packet is sent immediately following reception;
CSMA delay is not applied to these packets since permission belongs to the interacting modules. When the sending module receives the acknowledgement packet, it marks the current block of data as completed. If this is the last message in the queue, the sending module takes the BE line high to indicate that all outgoing data has been sent. Assured delivery should only be used when addressing a specific module in a point-to-point link. It should not be used when multiple receivers are enabled. When address masking is used, only the receiver with an exact match to the address in the transmitted packet responds. If none of the enabled receivers has an exact match, then there is no response and the transmitting module continues to re-transmit the data until the max number of retries is attempted. This causes the transmitting module to appear slow or unresponsive. It also impedes valid communications. 20 21 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. Assigning different hopping sequences to multiple networks in the same area minimizes the interference. When the module is awake and not transmitting, it rapidly scans all channels for a packet preamble. When a module starts transmitting at the beginning of a new channel, it transmits a packet with a long preamble of alternating 0 and 1 bits. This long preamble is sufficient to allow receiving modules to scan through all of the channels in the hopping sequence and find it. Modules that are scanning detect the preamble and pause on that channel, waiting for a valid packet. If a packet is received with a valid CRC (unencrypted) or authentication
(encrypted), the header is examined to determine whether the module should synchronize to the transmitter. Synchronization requires that the hop sequence matches and that the message is addressed to the receiver. When synchronized, the receiver stays on the current channel to either transmit a packet or to receive an additional packet. Additional packets transmitted on the same channel within the time slot use short preambles since the receivers are already listening to the current channel. At the end of the time slot for the current channel, all modules which locked to the original transmission switch to the next channel in the hop sequence. The first transmission on each new channel has a long preamble. A receiver that has synchronized to a transmitter continues to stay in synchronism by staying on the received channel until the expiration of the time slot, then waiting on the next hop channel for the duration of the time slot. If no further packets are received, the receiver loses lock and reverts to scanning. This allows the receiver to stay synchronized for a short while if a packet is not received correctly. The module supports the option to send the long preamble with every packet rather than just the first packet on each channel. This can be beneficial for systems that have modules asleep most of the time. It gives modules that just woke up the chance to synchronize to any transmitted packet instead of having to wait for the transmitter to complete its time slot and jump to the next channel. This can reduce the synchronization time and power consumption of the sleeping nodes. Compatibility with the 250 Series When DSN mode is used with a specific address, the module can communicate with 250 Series modules at UART data rates of 38,400 to 115,200 bps, non-encrypted. For other addressing modes, the HumPROTM Series modules can be configured to operate with them. Setting the COMPAT register to 0x00 enables the compatible operation. This allows mixed-mode systems and upgrades of legacy products that still maintain backwards compatibility. Only the higher baud rates are compatible. The main feature of compatibility operation is that it configures the same addressing methods used by the 250 Series. These methods are more susceptible to interference from adjacent networks of 250 Series modules which use DSN (GUI) broadcast messages. Please see Reference Guide RG-00105 for more details. Networking The HumPROTM Series modules can be used to create many types of wireless networks. The modules do not provide network routing since the internal memory size of the module would limit the overall network size. The HumPROTM can work as the MAC/PHY layers of a network stack and the memory and processing speed of the external microcontroller can be sized according to the size of the network that is needed for the application. This requires more software development, but avoids the cost of adding extra memory on the module for applications that dont need it. Linx can assist with network frameworks and concepts and can create custom designs on a contract basis. Contact Linx for more details. 22 23 Transmitting 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. The incoming bytes are buffered until one of four conditions triggers the packet to be transmitted:
1. The number of bytes in the buffer exceeds the value in the Byte Count Trigger (BCTRIG) register. 2. The time since the last received byte exceeds the value in the Data Timeout (DATATO) register. 3. A SENDP command is written to the CMD register. 4. The CMD line is taken low with option PKOPT: TXnCMD = 1. 5. The number of buffered bytes exceeds what can be sent before the radio must hop channels. The first four conditions can be controlled by the host microcontroller. In the last case, the module transmits what it can in the remaining time then sends the rest on the next channel. This can cause the data to be divided up into multiple packets and is not within the control of the host micro. In cases where all data needs to be sent in the same packet or where the microcontroller needs greater control over the radio, the HumPROTM offers explicit control of packet transmission with options in the PKTOPT register. When the TXPKT option is enabled (PKTOPT register, bit 0 = 1), the data is held until a SENDP command is written to the CMD register. Alternatively, if option TXnCMD is enabled (PKTOPT register, bit 1 = 1), then lowering the CMD line triggers the packet transmission, reducing the number of UART transactions that are required. The BCTRIG and DATATO conditions are ignored when the TXPKT option is enabled. Once triggered, the transmitted packet contains the bytes in the buffer as of the trigger event, even if more data bytes are received before the packet can be sent. Multiple outgoing packets can be buffered in this way. If the full packet cannot be sent in the time remaining on the current channel, then it is held until the module hops to the next channel. This option gives the host microcontroller very fine control over when packets are transmitted and what they contain. Receiving Packets In default operation when receiving valid packets, the module outputs all received bytes as soon as the packet is validated (CRC checks pass) and if the addressing permits it at the baud rate selected by the UARTBAUD register. No command or control bytes are output and no action is required of an external microcontroller. The first byte from a packet directly follows the last byte of the previously received packet. In cases where the host microcontroller needs more control over the data or where dynamic configuration changes could set up race conditions between incoming data and outgoing commands, the module offers explicit control over received packets. When the RXPKT option is enabled (PKTOPT register, bit 2 = 1), received data is output on the CMD_DATA_OUT line one packet at a time after a GETPH, GETPD, or GETPHD command is written to the CMD register. Writing one of these commands begins the received packet transfer cycle. Two lines are used as flow control and indicators during the transfer cycle. The CMD line is controlled by the host microcontroller. The module uses either the CTS line or the CRESP line as a status line, depending on the state of the RXP_CTS option in the PKOPT register. When a valid packet is received, the EX_RXWAIT exception flag is set in the EEXFLAG1 register. If the corresponding bit in the EEXMASK1 register is set, then the EX line goes high. The host microcontroller can monitor the EX line or periodically check the EEXFLAG or LSTATUS registers to determine if data is ready to be read. The transfer cycle is begun by writing a Get Packet Header (GETPH), Get Packet Data (GETPD), or Get Packet Header and Data (GETPHD) command to the CMD register. The module sends the command ACK byte and sets the selected status line high. Once the status line goes high, the host microcontroller sets the CMD line high and the module outputs the received data. The command sent determines whether the bytes sent are the header, data, or header followed by data. When all packet bytes have been sent the control line goes low. When the host microcontroller detects that the line is low, it sets CMD low, completing the transfer cycle. The cycle is shown in Figure 21. 24 25 CMD CMD_DATA_IN Any Command Read Packet Command CMD_DATA_OUT Any Response ACK Packet to UART CONTROL EX Exception for unread packet Packet In Figure 21: HumPROTM Series Transceiver Received Packet Transfer Cycle If a GETPH was sent and header data received, the following data can then be read by repeating the cycle with the GETPD command. If the next GETPx command is a GETPH or GETPHD, the data associated with the header read by GETPH is discarded and the header or header plus data of the following packet is returned. If there is RF-received data waiting to be sent to the UART and the mask for EX_RXWAIT is set in the EEXMASK register, EX is raised if it is low. If there is no packet waiting when a GETPx command is sent, the control line is still taken high and not reset until after CMD goes high, thereby performing a zero-byte transfer cycle. The header and payload structures differ between encrypted packets and unencrypted packets. The header and data structures for explicit unencrypted packets are shown in Figure 22. The Tag field identifies the start of the block and if it is the header information (0x01) or the packet data (0x02). The Header Length field identifies the number of header bytes that follow. The Frame Type field identifies what kind of packet was received. The values are shown in Figure 23. The Hop ID field is the hop sequence number, 0 - 5. The Sequence byte is incremented for each new packet, modulo 255. A received packet is discarded if the sequence byte matches the previously received packet to prevent delivering duplicate copies of an automatically retransmitted packet. DSN Address Packet Header Tag 0x01 Header Length 1 Frame Type 1 User Address Packet Header Tag 0x01 Header Length 1 Frame Type 1 Hop ID Sequence Dest DSN 1 1 4 Source DSN 4 Data Length 1 Hop ID Sequence Cust ID Dest Addr 1 1 2 2 or 4 Source Addr 2 or 4 Source DSN 4 Data Length 1 Packet Data Tag 0x02 Data Length 1 Data Data Length Bytes Figure 22: HumPROTM Series Transceiver Unencrypted Packet Header and Data Structure HumPROTM Series Transceiver Frame Types Frame Type Packet Type 0x04 0x06 0x07
+0x10
+0x20
+0x40 DSN Addressing Mode User Addressing Mode Extended User Addressing Mode Acknowledgements Enabled Encrypted Packet Long Preamble Packet Figure 23: HumPROTM Series Transceiver Frame Types The Cust ID field is a number that can be assigned to a specific customer. Only modules with the same customer ID respond to transmissions. By default, Cust ID is 0x7FFF for packets transmitted with COMPAT = 2 or 0xFFFF for packets transmitted with COMPAT = 0. The Dest Addr field has the received destination address. This is 2 bytes long with User Addressing Mode and 4 bytes with DSN and Extended User Addressing Modes. The Source Addr Field is the address of the transmitting module. This is 2 bytes long with User Addressing Mode and 4 bytes with DSN and Extended User Addressing Modes. The Data Length byte indicates how many bytes of data are in the packet. This value is the same in the packet header and the associated data block. 26 27 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. Encrypted DSN Address Packet Header Tag 0x11 Header Length 1 Frame Type 1 Hop Key Sequence Dest DSN 1 6 4 Source DSN 4 EBlock Length 1 Payload Type 1 Encrypted User Address Packet Header Tag 0x11 Header Length 1 Frame Type 1 Hop Key Sequence Dest Addr 1 6 2 or 4 Source Addr 2 or 4 Source DSN 4 EBlock Length 1 Payload Type 1 Encrypted Packet Data Tag 0x12 Data Length 1 Data Data Length Bytes Figure 24: HumPROTM Series Transceiver Encrypted Packet Header and Data Structure The Tag, Header Length and Frame Type fields are the same as for unencrypted packets. The Hop Key field uses the first three low-order bits to indicate the Hop Sequence number, which is the same as unencrypted packets. The upper two bits indicate which key is being used. Either the factory-set key that is used to securely transfer the network key or a network key that has been written or created by the JOIN process. This is shown in Figure 25. HumPROTM Series HopKey Byte Values HopKey Bit Value 0 - 3 4 - 5 6 - 7 Hop Sequence Number, 1 to 5
= 0 Encryption key 0 = factory 1 = user network Figure 25: HumPROTM Series HopKey Byte Values The Sequence bytes contain a counter that is incremented for each new transmitted message. The initial value is randomized when the module is reset. The extended sequence becomes part of an initialization vector which is used to vary the encrypted contents of identical packets. A received packet is discarded if the sequence byte matches the previously received packet to prevent delivering duplicate copies of an automatically retransmitted packet. The Dest DSN, Source DSN, Dest Addr and Source Addr fields are the source and destination addresses, the same as in unencrypted packets. The EBlock length filed is the total number of bytes of data in the encrypted payload block. This length includes the Payload Type byte. The Payload Type byte indicates what data is contained in the payload. 0x00 indicates that the payload is user data. 0x01 indicates that the payload is the 16-byte AES key followed by any user data. This is used for transferring the network encryption key during the JOIN process. For the Encrypted Packet Data packet, the Data Length byte indicates the number of bytes of data payload that follow. This value is one less than the EBlock length in the header. The reason for this is that the Payload Type byte is included in the encrypted block, but is reported with the header since it is not user data. Using the Buffer Empty (BE) Line The BE line indicates the state of the modules UART buffer. It is high to indicate that the UART input buffer is empty, indicating that all data has been transmitted. When the module receives data on the CMD_DATA_IN line and the CMD line is high, the BE line is lowered until all data in the buffer has been processed by the protocol engine. If acknowledgement is not enabled, the BE line is raised as soon as the module transmits the outgoing packets. If acknowledgement is enabled, the buffer is not updated until either the data transmissions are acknowledged by the remote end or delivery fails after the maximum number of retries. When the BE line returns high, the EX line may be sampled, or the EXCEPT or EEXFLAG register polled to determine if an error occurred during transmission. The state of the BE line can be read in the LSTATUS register, reducing the number of hardware connections that are needed. 28 29 Exception Engine The HumPROTM 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:
1. From the EXMASK and EXCEPT registers (legacy operation) 2. From the EEXMASKx and EEXFLAGx registers (standard operation) If EXMASK is non-zero, the first method is used, otherwise the second method is used. For legacy operation with the 250 and 25 Series, the EX line is set and reset by the Exception (EXCEPT) register processing. It is set when an exception occurs and the exception code ANDed with the current Exception Mask (EXMASK) register is non-zero. It is reset when the EXCEPT register is read through a command. No other operations affect the state of EX. Setting EXMASK non-zero does not change the state of EX. If an exception code is already present in the register when an error occurs, the new exception code overwrites the old value. Exception codes are organized by type for ease of masking. Figure 26 lists the exception codes and their meanings. HumPROTM Series Transceiver Exception Codes Exception Code Exception Name Description 0x08 0x09 0x13 0x20 0x40 0x42 0x43 0x44 EX_BUFOVFL EX_RFOVFL Incoming UART buffer overflowed. Outgoing UART buffer overflowed. EX_WRITEREGFAILED Attempted write to register failed. EX_NORFACK Acknowledgement packet not received after maximum number of retries. EX_BADCRC Bad CRC detected on incoming packet. EX_BADHEADER Bad CRC detected in packet header. EX_BADSEQID Sequence ID was incorrect in ACK packet. EX_BADFRAMETYPE Attempted transmit with Invalid setting in reg:NETMODE or invalid packet type in received packet header Figure 26: HumPROTM Series Transceiver Exception Codes 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. HumPROTM Series Transceiver Example Exception Masks Exception Mask Exception Name 0x08 0x10 0x20 0x40 0x60 0xFF Allows only EX_BUFOVFL and EX_RFOVFL to trigger the EX line Allows only EX_WRITEREGFAILED to trigger the EX line Allows only EX_NORFACK to trigger the EX line Allows only EX_BADCRC, EX_BADHEADER, EX_BADSEQID and EX_BADFRAMETYPE exceptions to trigger the EX line Allows EX_BADCRC, EX_BADHEADER, EX_BADSEQID, EX_ BADFRAMETYPE and EX_NORFACK exceptions to trigger the EX line Allows all exceptions to trigger the EX line Figure 27: HumPROTM Series Transceiver Example Exception Masks The exception mask has no effect on the exceptions stored in the exception register. It only controls which exceptions affect the EX line. The extended exception registers offer more functionality with more exceptions and a separate bit for each exception. These registers are the default and should be used with new applications. When an exception sets an exception code in the EXCEPT register, the corresponding flag in the EEXFLAG register is also set. The EX line is set and reset by the Extended Exception Flags (EEXFLAG) and Extended Exception Mask (EEXMASK) register processing. It is set whenever the EEXFLAG value ANDed with the EEXMASK value is non-zero. EX can change on any write to either of these registers that affects the result of ANDing the registers. Clearing an EEXFLAG register bit or value can leave EX set if there is another masked condition bit set. The state of the EX line can also be read in the LSTATUS register, reducing the number of hardware lines that are required. 30 31 Carrier Sense Multiple Access (CSMA) 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. When a module has data ready to transmit and CSMA is enabled, it listens on the intended transmit channel for activity. If no signal is detected, transmission is started. If a carrier is detected with an RSSI above the CSMA threshold in the CRSSI register, transmission is inhibited. If a signal below the threshold is detected that has a compatible preamble or packet structure, transmission is also inhibited. If the module is synchronized from a recent packet transfer, it waits for a random interval, then checks again for activity. If the detected carrier lasts longer than the time allowed for the current channel, the module hops to the next channel in the hop sequence and again waits for a clear channel before transmitting. If the module is not synchronized, it hops to the next channel and again checks for interference. When no activity is detected it starts transmitting. Using the Command Response (CRESP) Line The CRESP line is normally high, but the module lowers this line when responding to a UART command. This indicates to an external host microcontroller that the data on the CMD_DATA_OUT line is a response to a command and not data received over-the-air. CRESP is held in the correct state at least one byte time after the last byte for the indicated source (command response or data, although it normally stays in the same state until a change is required). The module normally outputs received RF data immediately following the command response. The CRESP line does rise before resuming RF data, but some microcontrollers cannot react quickly enough to this signal and may not able to separate the command responses from RF data. When reading or writing the modules register settings, it is possible for incoming RF data to intermix with the modules response to a configuration command. This can make it difficult to determine if commands were successfully processed as well as to capture the received RF data. Setting the CMDHOLD register to 0x01 causes the module to store incoming RF traffic (up to the RF buffer capacity) while the CMD line is low. When the CMD line is returned high, the module outputs the buffered data on the UART. This allows the external host microcontroller to have separate configuration times and data times instead of potentially having to handle both at once. The CRESP line stays low for at least ten bit times after the stop bit of the last command response. Figure 28 shows the timing. CMD_DATA_OUT Start Stop D0 D6 D7
... 10 bit times CRESP Figure 28: HumPROTM Series Transceiver CRESP Line Timing 32 33 Using the CMD Line 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. Since the modules controller looks at UART data one byte at a time, the CMD line must be held low for the entire duration of the command plus time for ten bits as margin for processing. Leaving the line low for additional time (for example, until the ACK byte is received by the application) does not adversely affect the module. If RF packets are received while the CMD line is active, they are still processed and output on the modules UART
(assuming CMDHOLD=0 and PKOPT:RXPKT=0). Figure 29 shows this timing. CMD_DATA_IN Start Stop D7 D0 D6
... 10 bit times CMD Figure 29: HumPROTM Series Transceiver CMD Line Timing Commands can be entered sequentially without having to raise the CMD line after each one. The CMD line just needs to be raised to be able to enter data for transmission. If the CMDHOLD register is 0x01 then any received data is held until the CMD line is raised. This prevents received data from being intermingled with command responses. External Amplifier Control The HumPROTM Series transceiver has two output lines that are designed to control external amplifiers. The PA_EN line goes high when the module activates the transmitter. This can be used to activate an external power amplifier to boost the signal strength of the transmitter. The LNA_EN line goes high when the module activates the receiver. This can be used to activate an external low noise amplifier to boost the receiver sensitivity. These external amplifiers can significantly increase the range of the system at the expense of higher current consumption and system cost. The states of the PA_EN and LNA_EN lines can be read in the LSTATUS register. This offers a quick way to determine the current state of the radio. AES Encryption HumPROTM Series modules with firmware version 2.0 and above offer 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. The HumPROTM Series module has the option to use AES encryption, arguably the most common encryption algorithm on the market. This is implemented in a secure mode of operation to ensure the secrecy of the transmitted data. It uses a 128-bit key to encrypt the transmitted data. The source and destination addresses are sent in the clear. Encryption is disabled by default. There are two ways to enable encryption and set the key: sending serial commands and using the JOIN process. Writing an encryption key to the module with the CDI The module has no network key when shipped from the factory. An encryption key can be written to the module using the CDI. The CMD register is used to write or clear a key. The key cannot be read. The same key must be written to all modules that are to be used together. If they do not have the same key then they will not communicate in encrypted mode. The JOIN Process The JOIN process is a method of generating an encryption key and distributing the key and addresses to associated modules through a series of button presses. This makes it very simple to establish an encrypted network in the field or add new nodes to an existing network without any additional equipment. It is also possible to trigger the JOIN process through commands on the Command Data Interface. The JOIN process configures a star network with the central unit as system master. Other units are added to the network one at a time. The hardware required is a pushbutton that is connected to the PB line. This takes the line to VCC when it is pressed and ground when it is released. An LED connected to the MODE_IND line provides visual indication of the modules state. 34 35 A module is set as a master 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 is complete and the module is now a master unit. When Generate Key is performed, the unit is set as the system master and ADDMODE is set to Extended User Address with encryption (0x27). It generates a random 128-bit AES encryption key based on ambient RF noise and scrambled through an encryption operation. If UMASK is the default value (0xFFFFFFFF), then it is set to 0x000000FF, supporting up to 255 nodes. A random 32-bit address is generated. By default, the lower 8 bits are 0. The address of the master unit is the network base address. Other nodes are assigned sequential addresses, starting with network base address +1. Finally, UDESTID is set to the bitwise OR of USRCID and UMASK, which is the network broadcast address. Setting a module to be a slave is accomplished by joining it with a master unit. 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 master sends the slave the encryption key, UMASK value and its network address. The UDESTID is set to the address of the master. The values are encrypted using a special key that is defined at the factory. Once the JOIN process is complete, the MODE_IND blinks on both units and they now operate together. This is shown in Figure 30 A. If UMASK is pre-set when Generate Key is initiated, then the JOIN process uses that mask and sets the address accordingly. This can allow more nodes in the network. This is shown in Figure 30 B. Likewise, the network key can be written to the module and the JOIN process used to create an address and associate new modules. Or the master can be completely configured through the CDI and the JOIN process used to associate nodes in the field. This gives the system designer many options for configuration. The JOIN process protocol detects if there are multiple masters or slaves in the area attempting to join and fails the process automatically. This ensures that the correct modules are joined. The SECOPT register is used to configure options related to the JOIN process. This allows the OEM to set desired values at the factory and allow final network configuration in the field. This includes disabling the ability to change the address, change the key and share the key. 36 A) Key Generation and Network Join from Factory Default Generate Key D M UMASK = FF FF FF FF USRCID = FF FF FF FF UDESTID = FF FF FF FF No Key UMASK = 00 00 00 FF USRCID = 76 54 32 00 UDESTID = 76 54 32 FF Network Key JOIN D S UMASK = FF FF FF FF USRCID = FF FF FF FF UDESTID = FF FF FF FF No Key UMASK = 00 00 00 FF USRCID = 76 54 32 01 UDESTID = 76 54 32 00 Network Key M UMASK = 00 00 00 FF USRCID = 76 54 32 00 UDESTID = 76 54 32 FF Network Key B) Key Generation and Network Join from Preset Mask Generate Key P M UMASK = 00 00 0F FF USRCID = FF FF FF FF UDESTID = FF FF FF FF No Key UMASK = 00 00 0F FF USRCID = 76 54 30 00 UDESTID = 76 54 3F FF Network Key JOIN D S UMASK = FF FF FF FF USRCID = FF FF FF FF UDESTID = FF FF FF FF No Key UMASK = 00 00 0F FF USRCID = 76 54 30 01 UDESTID = 76 54 30 00 Network Key M D = Factory Default M = Network Master S = Network Slave P = OEM Preset Unit UMASK = 00 00 0F FF USRCID = 76 54 30 00 UDESTID = 76 54 3F FF Network Key Figure 30: HumPROTM Series JOIN Process 37 Using the MODE_IND Line The MODE_IND line is designed to be connected to an LED to provide visual indication of the modules 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. MODE_IND Line Timing Display
[on/off time in seconds]
Join Operation Two quick blinks One quick blink Quick blink Slow Blink Module Status Master Join. The master unit is looking for a slave unit to join with. Slave Join. The slave unit is looking for a master unit to join with. Key Transfer Active. Key transfer is taking place (master and slave). Key Transfer Complete. The module has completed a key transfer (master and slave). Temporary On On when the PB line is high Two quick blinks, one time Join Canceled. Slow blink, repeat 3 times Slow blink and two quick blinks Key Test Results One quick blink Three times Failure. For Share Key or Get Key, there are multiple units attempting to pair, protocol error, or timeout without response Long Hold Acknowledgement. The long hold period for Generate Key or Reset Sequence was recognized (PB is asserted) No Key. There is no network key or network address. Two quick blinks Three times Key Set, slave. The network key and network address are set on a slave unit. Three quick blinks Three times Key Set, master. The network key and network address are set on a master unit. Normal operation Off No activity Temporarily on Transmitting or receiving packet Figure 31: HumPROTM Series MODE_IND Line Timing Figure 33 shows the MODE_IND displays in a graphical format. Operation Master Join Slave Join Key Transfer Active Key Transfer Complete JOIN Cancelled Long Hold Failure No Key Set Key Set, Slave Key Set, Master Time (seconds) MODE_IND Display Comments Repeats for 30 seconds or until JOIN is complete Repeats for 30 seconds or until JOIN is complete Repeats for the duration of the transfer Six blinks total Repeats for as long as the PB line is asserted after the long hold period has been recognized Repeats, three times total Repeats, three times total Repeats, three times total 0 0.5 1 1.5 2 2.5 Figure 33: HumPROTM Series MODE_IND Displays Using the PB Line The PB Line is used to trigger functions associated with the JOIN process. This line should be connected to a momentary pushbutton that pulls the line to VCC when it is pressed and opens the circuit when it is released. There is no internal pull-down, so a resistor to ground should be used to pull the line down when the button is not pressed. A value of 10k to 100k works well. The sequence of presses determines which function is triggered. Figure 32 shows the sequences. PB Line Operation Function Sequence Join a network 1 short pulse Cancel a Join Process that is in progress 1 short pulse Generate a network key and address Hold PB high for 30 seconds Reset to factory defaults Test key and address 4 short pulses and hold high for 3 seconds 3 short pulses A short pulse is a logic high that is between 100 and 2,000ms in duration. Figure 32: HumPROTM Series PB Line Operation 38 39 Output Line Sleep States Output Line EX CRESP LNA_EN PA_EN TXD CTS MODE_IND BE Sleep State Unchanged Low Low Low High High Low Unchanged Figure 34: HumPROTM Series Output Line Sleep States If the volatile registers have been corrupted during sleep, a software reset is performed. This restarts the module as if power were cycled. This can be caused by power surges or brownout among other things. After the module wakes up, it sets the IDLE register to 0 (active). If the WAKEACK register is set to 1, then the module outputs the 0x06 byte on the CMD_DATA_OUT line. The CRESP line is taken high and the module then begins normal operation. Pulsing RESET low causes the module to restart rather than continue from sleep. 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. After PB goes low, the non-volatile configurations are set to the factory default values and the module is restarted. The default UART data rate is 9,600bps. If the timing on PB does not match the specified limits, the sequence is ignored. Another attempt can be made after lowering PB for at least 3 seconds. Using the Low Power Features The module supports several low-power features to save current in battery-powered applications. This allows the module to be asleep most of the time, but be able to quickly wake up, send data and go back to sleep. Taking the Power Down (POWER_DOWN) line low places the module into the lowest power state. In this mode, the internal voltage regulator and all oscillators are turned off. All circuits powered from the voltage regulator are also off. The module is not functional while in this mode and current consumption drops to below 6A. Taking the line high wakes the module. When the POWER_DOWN line is high, the IDLE register determines sleep operation. If IDLE is set to 1 during normal operation, the module sends an ACK byte, waits for completion of an active transmission, then goes into sleep mode. Unsent data in the incoming UART data buffer does not inhibit sleep. During sleep mode, the output lines are in the states in Figure 34. A rising transition on the POWER_DOWN or CMD_DATA_IN lines wakes the module. If a negative-going pulse is needed to generate a rising edge, the pulse width should be greater than 1 s. Other lines also wake the module but it immediately goes back to sleep. Floating inputs should be avoided since they may cause unintended transitions and cause the module to draw additional current. 40 41 The Command Data Interface The HumPROTM 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 modules 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). The CMD line tells the module if the data on the UART is for configuration commands (low) or data transmission
(high). The module has a 256 byte buffer for incoming data. The module starts transmitting when the buffer reaches a specified limit or when the time since the last received byte on the UART reaches a specified value. This allows the designer to optimize the module for fixed length and variable length data. If the buffer gets nearly full (about 224 bytes), the module pulls the CTS line high, indicating that the host should not send any more data. Data sent by the host while the buffer is full is lost, so the CTS line provides a warning and should be monitored. When there is outgoing data waiting to be transmitted or acknowledged the BE line is low, otherwise BE is high. Configuration settings are stored in two types of memory inside the module. Volatile memory is quick to access, but it is lost when power is removed from the module. Non-volatile memory takes longer to access, but is retained when power is removed. When a configuration parameter has both a non-volatile and volatile register, the volatile register controls the operation. The non-volatile register is the default value that is loaded into the volatile register on power-up. Configuration settings are read from non-volatile memory on power up and saved in volatile memory since it is faster to read and write the volatile memory locations. The volatile and non-volatile registers have different address locations, but the same read and write commands. The two locations can be changed independently. The general serial command format for the module is:
[FF] [Length] [Command]
The Length byte is the number of bytes in the Command field. The Command field contains the register address that is to be accessed and, in the case of a write command, the value to be written. Neither Length nor Command can contain a 0xFF byte. Byte values of 128 (0x80) or greater can be sent as a two-byte escape sequence of the format:
0xFE, [value - 0x80]
For example, the value 0x83 becomes 0xFE, 0x03. The Length count includes the added escape bytes. A response is returned for all valid commands. The first response byte is CMD_ACK (0x06) or CMD_NACK (0x15). Additional bytes may follow, as determined by the specific command. Reading from Registers A register read command is constructed by placing an escape character
(0xFE) before the register number. The module responds by sending an ACK (0x06) followed by the register number and register value. The register value is sent unmodified, so if the register value is 0x83, 0x83 is returned. If the register number is invalid, the module responds with a NACK (0x15). The command and response are shown in Figure 35. HumPROTM Series Read From Configuration Register Command Header 0xFF Size 0x02 Escape Address 0xFE REG Response ACK 0x06 Address Value REG V Command for an Address greater than 128 (0x80) Header 0xFF Size 0x03 Response Escape Addr1 Addr2 0xFE 0xFE REG-80 ACK 0x06 Address Value REG V 42 43 Figure 35: HumPROTM Series Read from Configuration Register Command and Response Command Length Optimization Some commands may be shortened by applying the following rules:
1. Escape sequences are not required for byte values 0x00 to 0xEF
(besides 0xFE and 0xFF, bytes 0xF0 0xFD are reserved for future use). 2. An escape byte inverts bit 7 of the following data byte. 3. The 0xFE as the first byte of the Read Register Command field is an escape byte. 4. Two consecutive escape bytes cancel unless the following data byte is 0xf0-0xff. Examples:
FF 02 FE 02 (read nv:TXPWR) is equivalent to FF 01 82. FF 03 FE FE 53 (read v:PKOPT) is equivalent to FF 01 53. FF 03 1A FE 7F (write FF to nv:UMASK0) cannot be shortened. FF 03 1A FE 40 (write C0 to nv:UMASK0) is equivalent to FF 02 1A C0. These rules are implemented in the sample code file EncodeProCmd.c, which can be downloaded from the Linx website. Writing to Registers 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. HumPROTM Series Write to Configuration Register Command Command for a Register and Value less than 128 (0x80) Header Size Address Value 0xFF 0x02 REG V Command for a Register less than 128 (0x80) and a Value greater than 128 (0x80) Header Size Address Escape Value 0xFF 0x03 REG 0xFE V-0x80 Command for a Register greater than 128 (0x80) and a Value less than 128 (0x80) Header Size Addr1 Addr2 Value 0xFF 0x03 0xFE REG-0x80 V Command for a Register and Value greater than 128 (0x80) Header Size Addr1 Addr2 Escape Value 0xFF 0x04 0xFE REG-0x80 0xFE V-0x80 Figure 36: HumPROTM Series Write to Configuration Register Command Generally, there are three steps to creating the command. 1. Determine the register address and the value to be written. 2. Encode the address and value as either the number (N) or the encoded number (0xFE, N-0x80) as appropriate. 3. Add the header (0xFF) and the size. The module responds with an ACK (0x06). If the ACK is not received, the command should be resent. The module responds with a NACK (0x15) if a write is attempted to a read-only or invalid register. As an example, to write 01 to register 0x83, send FF 03 FE 03 01 Note: The non-volatile memory has a life expectancy of at least 26,000 write operations. 44 45 return dx;
}
/* Function: HumProRead
** Description: This function encodes a read command to the specified
** register address.
*/
unsigned char /* number of encoded bytes, 3 to 4 */
HumProRead(
unsigned char *cmd, /* out: encoded read command, length >= 4 */
unsigned char reg /* register number to read, 0..0xff */
) {
unsigned char ra; /* read register byte */
ra = reg ^ 0x80;
return HumProCommand(cmd, &ra, 1);
}
/* Function: HumProWrite
** Description: This function encodes a command to write a single byte to
** a specified register address.
*/
unsigned char /* number of encoded bytes, 4 to 6 */
HumProWrite(
unsigned char *cmd, /* out: encoded read command, length >= 6 */
unsigned char reg, /* register number to write, 0..0xff */
unsigned char val /* value byte, 0..0xff */
) {
unsigned char cs[2];
cs[0] = reg;
cs[1] = val;
return HumProCommand(cmd, &cs, 2);
}
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.c
/* Sample C code for encoding Hum-xxx-PRO commands
**
** Copyright 2015 Linx Technologies
** 155 Ort Lane
** Merlin, OR, US 97532
** www.linxtechnologies.com
**
** License:
** Permission is granted to use and modify this code, without royalty, for
** any purpose, provided the copyright statement and license are included.
*/
#include EncodeProCmd.h
/* Function: HumProCommand
** Description: This function encodes a command byte sequence.
** If len = 1, a read command is generated.
** If len > 1, a write command is generated.
** rcmd[0] = register number
** rcmd[1..(n-1)] = bytes to write
*/
unsigned char /* number of encoded bytes, n+2 to 2*n+2 */
HumProCommand(
unsigned char *ecmd, /* out: encoded command, length >= 2*n + 2 */
const unsigned char *rcmd, /* in: sequence of bytes to encode */
unsigned char n /* number of bytes in rcmd, 1..32 */
) {
unsigned char dx; /* destination index */
unsigned char sx; /* source index */
unsigned char v; /* value to be encoded */
dx = 2;
sx = 0;
while (n--) {
v = rcmd[sx++];
if (v >= 0xf0) {
ecmd[dx++] = 0xfe;
v &= 0x7f;
}
ecmd[dx++] = v;
}
ecmd[0] = 0xff;
ecmd[1] = dx - 2;
46 47 The Command Data Interface Command Set The following sections describe the registers. HumPROTM Series Configuration Registers Name CRCERRS HOPTABLE TXPWR UARTBAUD ADDMODE DATATO MAXTXRETRY ENCRC BCTRIG SHOWVER ENCSMA IDLE WAKEACK NV Addr CRC Error Count Channel Hop Table Transmit Power UART data rate Addressing mode Data timeout Vol Addr R/W Default Value Description 0x00 0x40 0x00 0x4B 0x03 0x4D 0x4E 0x01 0x04 0x4F 0x10 0x50 0x52 0x1A Maximum Transmit Retries 0x01 0x53 0x40 0x54 0x01 0x01 0x00 0x01 R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W 0x00 0x02 0x03 0x04 0x05 0x07 0x08 0x09 0x0A 0x0B 0x56 0x0D 0x58 0x0E 0x59 Enable CRC checking Byte Count trigger Show version on startup Enable CSMA Idle Mode UART Acknowledge on Wake Destination Address for User Packet Type, extended Destination Address for User Packet Type, extended Destination Address for User Packet Type Destination Address for User Packet Type Source Address for User Packet Type, extended Source Address for User Packet Type, extended Source Address for User Packet Type Source Address for User Packet Type Address Mask for User Packet Type, extended Address Mask for User Packet Type, extended Address Mask for User Packet Type Address Mask for User Packet Type Destination Device Serial Number Destination Device Serial Number Destination Device Serial Number UDESTID3 0x0F 0x5A R/W 0xFF UDESTID2 0x10 0x5B R/W 0xFF UDESTID1 0x11 0x5C R/W 0xFF UDESTID0 0x12 0x5D R/W 0xFF USRCID3 0x13 0x5E R/W 0xFF USRCID2 0x14 0x5F R/W 0xFF USRCID1 USRCID0 0x15 0x16 0x60 0x61 R/W R/W 0xFF 0xFF UMASK3 0x17 0x62 R/W 0xFF UMASK2 0x18 0x63 R/W 0xFF UMASK1 UMASK0 DESTDSN3 DESTDSN2 DESTDSN1 0x64 0x19 0x1A 0x65 0x1D 0x68 0x1E 0x69 0x6A 0x1F R/W R/W R/W R/W R/W 0xFF 0xFF 0xFF 0xFF 0xFF 48 0x20 0x21 0x23 0x25 0x26 0x34 0x35 0x36 0x37 0x39 0x3A 0x3F 0x78 DESTDSN0 EXMASK CMDHOLD COMPAT AUTOADDR MYDSN3 MYDSN2 MYDSN1 MYDSN0 CUSTID1 CUSTID0 CRSSI RELEASE EXCEPT PRSSI ARSSI FWVER3 FWVER2 FWVER1 FWVER0 NVCYCLE1 NVCYCLE0 LSTATUS CMD SECSTAT JOINST EEXFLAG2 EEXFLAG1 EEXFLAG0 0x80 EEXMASK2 0x81 EEXMASK1 0x82 EEXMASK0 0x83 PKTOPT 0x84 SECOPT LASTNETAD[3] 0x8C LASTNETAD[2] 0x8D LASTNETAD[1] 0x8E LASTNETAD[0] 0x8F 0xC0 0xC1 0xC2 0xC3 0xC4 0xC5 0x6B 0x6C 0x6E 0x70 0x71 R/W R/W R/W R/W R/W 0xFF 0x00 0x00 0x02 0x00 R R R R R R 0xFF 0xFF Destination Device Serial Number Exception Mask to activate EX Hold RF data when nCMD pin is low Compatibility Automatic Reply Address Factory programmed Serial Number Factory programmed Serial Number Factory programmed Serial Number Factory programmed Serial Number Factory programmed customer ID Factory programmed customer ID R/W 0xBA Carrier Sense minimum RSSI 0x79 0x7B 0x7C R R R R R R R R R R R W R R 0xC6 0xC7 0xC9 0xCA 0xCD R/W R/W 0xCE R/W 0xCF 0xD0 R/W R/W 0xD1 R/W 0xD2 R/W 0xD3 0xD4 R/W R/W R/W R/W R/W Release number Exception code Packet RSSI Ambient RSSI Firmware version, major Firmware version, minor Firmware version, increment Firmware version, suffix NV Erase Cycles, MS NV Erase Cycles, LS Output line status Command register Security Status Join Status Extended exception flags Extended exception flags Extended exception flags Extended exception mask Extended exception mask Extended exception mask Packet options Security Options Last Network Address Assigned Last Network Address Assigned Last Network Address Assigned Last Network Address Assigned 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0xFF 0x00 0x00 0x00 0x00 49 Figure 37: HumPROTM Series Configuration 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. When the baud rate is 38,400bps and higher, the module uses 26 hopping channels and only even channels are used. Figure 42 shows the hop sequences referenced by channel number. The default hop sequence is 0. HumPROTM Series RF Channels Channel Number Frequency (MHz) Channel Number Frequency (MHz) HumPROTM Series CRC Error Count Read Command Header 0xFF Size 0x02 Write Command Header 0xFF Size 0x02 Escape Address 0xFE 0x40 Address Value 0x40 V Read Response ACK 0x06 Address Value 0x40 V Figure 38: HumPROTM Series CRC Error Count Command and Response HOPTABLE - Channel Hop Table Volatile Address = 0x4B; Non-Volatile Address = 0x00 The module supports 6 different hop sequences with minimal correlation. The sequence is set by the value in the HOPTABLE register. Changing the hop sequence changes the band utilization, much the same way that a channel does for a non-hopping transmitter. The hop table selection must match between the transmitter and receiver. Valid values are 0-5. Figure 39 shows the command and response. HumPROTM Series Channel Hop Table Read Command Read Response Header Size Escape Address ACK Address Value 0xFF 0x02 0xFE 0x4B 0x00 0x06 0x4B 0x00 V Write Command Header Size Address Value 0xFF 0x02 0x4B 0x00 V 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 902.971 903.347 903.723 904.099 904.475 904.851 905.227 905.602 905.978 906.354 906.730 907.106 907.482 907.858 908.234 908.610 908.986 909.361 909.737 910.113 910.489 910.865 911.241 911.617 911.993 912.369 912.745 913.120 913.496 913.872 914.248 914.624 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 915.000 915.376 915.752 916.128 916.504 916.880 917.255 917.631 918.007 918.383 918.759 919.135 919.511 919.887 920.263 920.639 921.014 921.390 921.766 922.142 922.518 922.894 923.270 923.646 924.022 924.398 924.773 925.149 925.525 925.901 926.277 926.653 Figure 39: HumPROTM Series Channel Hop Table Command and Response Figure 40 shows the RF channels used by the HumPROTM Series. When the baud rate is set to 9,600 or 19,200 bps, the module uses 50 hopping Figure 40: HumPROTM Series RF Channels 50 51 HumPROTM Series Hop Sequences by Channel Number for 19,200bps and below HumPROTM Series Hop Sequences by Channel Number for 38,400bps and Above 0 32 2 4 10 20 42 22 46 28 58 54 44 24 48 34 6 14 30 62 60 56 50 38 12 26 52 1 30 60 58 52 42 20 40 16 34 4 8 18 38 14 28 56 48 32 0 2 6 12 24 50 36 10 2 6 40 42 48 58 16 60 20 2 32 28 18 62 22 8 44 52 4 36 34 30 24 12 50 0 26 3 56 22 20 14 4 46 2 42 60 30 34 44 0 40 54 18 10 58 26 28 32 38 50 12 62 36 4 44 14 16 22 32 54 34 58 40 6 2 56 36 60 46 18 26 42 10 8 4 62 50 24 38 0 Figure 42: HumPROTM Series Hop Sequences for UART rates of 19,200bps and above 5 18 48 46 40 30 8 28 4 22 56 60 6 26 2 16 44 36 20 52 54 58 0 12 38 24 62 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 11 52 37 36 42 25 15 1 55 2 12 26 27 41 9 8 31 49 13 47 14 33 48 38 45 59 3 46 0 39 57 56 5 40 23 62 24 54 17 22 32 7 61 34 63 50 30 43 28 4 52 10 54 62 21 33 44 51 61 36 34 2 57 50 12 29 6 8 46 48 11 39 4 45 22 56 18 43 60 31 47 0 20 37 59 35 7 15 25 16 23 42 24 32 28 26 13 3 5 49 5 35 23 41 45 7 42 63 24 9 27 10 17 20 22 18 32 3 8 15 4 0 48 13 61 31 56 52 54 55 62 6 37 36 38 51 59 5 43 21 40 14 12 30 16 34 46 60 39 58 33 Figure 41: HumPROTM Series Hop Sequences for UART rate of 9,600bps 52 53 TXPWR - Transmitter Output Power Volatile Address = 0x4D; Non-Volatile Address = 0x02 The value in the TXPWR register sets the modules 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 0x03. HumPROTM Series Transmitter Output Power Mode Read Command Read Response Header Size Escape Address ACK Address Value 0xFF 0x02 0xFE 0x4D 0x02 0x06 0x4D 0x02 PWR Write Command Header Size Address Value 0xFF 0x02 0x4D 0x02 PWR Figure 43: HumPROTM Series Transmitter Output Power Mode Command and Response UARTBAUD - UART Baud Rate Volatile Address = 0x4E; Non-Volatile Address = 0x03 The value in UARTBAUD sets the data rate of the UART interface. Changing the non-volatile register changes the data rate on the following power-up or reset. Changing the volatile register changes the data rate immediately following the command acknowledgement. Figure 45 shows the command and response and Figure 46 shows the valid settings. HumPROTM Series UART Baud Rate Read Command Read Response Header Size Escape Address ACK Address Value 0xFF 0x02 0xFE 0x4E 0x03 0x06 0x4E 0x03 V Write Command Header Size Address Value 0xFF 0x02 0x4E 0x03 V Figure 45: HumPROTM Series UART Baud Rate Command and Response HumPROTM Series Transmitter Output Power Mode Register Settings HumPROTM Series UART Baud Rate Register Settings PWR 0x00 0x01 0x02 0x03 Typical Output Power (dBm)
-5 0
+5
+9 Figure 44: HumPROTM Series Transmitter Output Power Mode Settings V 0x01 0x02 0x03 0x04 0x05 0x06 0x07 Baud Rate (bps) RF Data Rate (bps) 9,600 19,200 38,400 57,600 115,200 10,400*
31,250*
19,200 19,200 153,600 153,600 153,600 153,600 153,600
* These data rates are not supported by PC serial ports. Selection of these rates may cause the module to fail to respond to a PC, requiring a reset to factory defaults. Figure 46: HumPROTM Series UART Baud Rate Settings If the modules UART baud rate is different than the host processor UART baud rate then the module will not communicate correctly. If mismatched, every rate can be tested until the correct one is found or the module can be reset to factory defaults. The default baud rate is 9,600bps (0x01). 54 55 HumPROTM Series Addressing Mode Register Settings Addressing Mode Meaning 0x04 0x06 0x07
+0x00
+0x08
+0x10
+0x20 DSN Addressing Mode User Addressing Mode Extended User Addressing Mode Send normal preamble Send long preamble Send acknowledgments Encrypt packets All other addressing modes are reserved and may cause undesired operation. Figure 48: HumPROTM Series Addressing Mode Register Settings 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. Endpoints can awaken, receive a message from the transmitter, and go back to sleep. This message could contain scheduling information as to when to wake again for a full bi-directional communications session. If bit 4 is set, then the receiver is instructed to transmit an acknowledgement packet for assured delivery signifying to the transmitter that the message was received. If bit 5 is set then the module transmits data in encrypted mode. Figure 47 shows the command and response and Figure 48 shows the valid settings. HumPROTM Series Addressing Mode Read Command Read Response Header Size Escape Address ACK Address Value 0xFF 0x02 0xFE 0x4F 0x04 0x06 0x4F 0x04 V Write Command Header Size Address Value 0xFF 0x02 0x4F 0x04 V Figure 47: HumPROTM Series Addressing Mode Command and Response 56 57 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). If the timer reaches zero before the next byte is received from the UART, the module begins transmitting the data in the buffer. This timeout value should be greater than one byte time at the current UART baud rate with a minimum of 0x02. It should not be set any value less than one byte time as unpredictable results could occur. If the timeout value is set to 0x00, the transmit wait timeout is deactivated. In this case, the transceiver waits until a number of bytes equal to the UART Byte Count Trigger (BCTRIG) have been received by the UART. All of the bytes are sent once the trigger has been reached. Figure 49 shows examples of the commands. Figure 50 shows the minimum timeout values based on baud rate. HumPROTM Series Transmit Wait Timeout Read Command Read Response Header Size Escape Address ACK Address Value 0xFF 0x02 0xFE 0x50 0x05 0x06 0x50 0x05 V Write Command Header Size Address Value 0xFF 0x02 0x50 0x05 V 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 51 shows examples of the command. HumPROTM Series Maximum Transmit Retries Read Command Read Response Header Size Escape Address ACK Address Value 0xFF 0x02 0xFE 0x52 0x07 0x06 0x52 0x07 V Write Command Header Size Address Value 0xFF 0x02 0x52 0x07 V Figure 51: HumPROTM Series Maximum Transmit Retries Command and Response The time between retries depends on the current baud rate. Figure 52 shows the time between retries based on baud rate. The elapsed transmit and acknowledgment time is (retries+1) (PacketTransmitTime + Timeout). HumPROTM Series Acknowledgement Timeout Times Baud Rate Timeout Time 9,600 19,200 38,400 57,600 115,200 50ms 50ms 30ms 30ms 30ms Figure 49: HumPROTM Series Transmit Wait Timeout Command and Response Figure 52: HumPROTM Series Acknowledgement Timeout Times HumPROTM Series Minimum DATATO Values Baud Rate Minimum DATATO 9,600 19,200 38,400 57,600 115,200 3ms 2ms 2ms 2ms 2ms Figure 50: HumPROTM Series Transmit Wait Timeout Minimum Values 58 59 ENCRC - CRC Enable Volatile Address = 0x53; Non-Volatile Address = 0x08 The protocol includes a Cyclic Redundancy Check (CRC) on the received packets to make sure that there are no errors. 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. The default CRC mode setting is enabled. Figure 53 shows examples of the commands and Figure 54 shows the available values. HumPROTM Series CRC Enable Read Command Read Response Header Size Escape Address ACK Address Value 0xFF 0x02 0xFE 0x53 0x08 0x06 0x53 0x08 V Write Command Header Size Address Value 0xFF 0x02 0x53 0x08 V Figure 53: HumPROTM Series CRC Enable Command and Response HumPROTM Series CRC Enable Register Settings V 0x00 0x01 Mode CRC Disabled CRC Enabled Figure 54: HumPROTM Series CRC Enable Register Settings Although disabling CRC checking allows receiving packets with errors in the payload, errors in the header can still prevent packets from being output by the module. BCTRIG - UART Byte Count Trigger Volatile Address = 0x54; Non-Volatile Address = 0x09 The BCTRIG register determines the UART buffer level that triggers the transmission of a packet. The minimum value is decimal 1 and the maximum value is 192. The default value for this register is 64, which provides a good mix of throughput and latency. At the maximum data rate, a value of 128 optimizes throughput. This register does not guarantee a particular transmission unit size; rather, it specifies the minimum desired size. If there is not enough time left in the channel dwell time before the module must hop to the next channel, for instance, the protocol engine sends as many characters as it can to fill the current channel dwell time, and sends the remaining characters on the next channel. Figure 55 shows examples of the commands. HumPROTM Series UART Byte Count Trigger Read Command Read Response Header Size Escape Address ACK Address Value 0xFF 0x02 0xFE 0x54 0x09 0x06 0x54 0x09 V Write Command Header Size Address Value 0xFF 0x02 0x54 0x09 V Figure 55: HumPROTM Series UART Byte Count Trigger Command and Response This trigger can be overridden by enabling the TXPKT option (PKTOPT register, bit 0). 60 61 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. HumPROTM Series Show Version Read Command Header 0xFF Size 0x02 Write Command Header 0xFF Size 0x02 Escape Address 0xFE 0x0A Address Value 0x0A V Read Response ACK 0x06 Address Value 0x0A V Figure 56: HumPROTM Series Show Version Command and Response HumPROTM Series Show Version Register Settings V 0x00 0x01 Meaning Startup message is NOT output on reset or power-up. Startup message is output on reset or power-up. This is a blocking operation, and any incoming UART data is lost during the transmission of this message through the CMD_DATA_OUT line. All UART commands must be sent after this message has completed. Figure 57: HumPROTM Series Show Version Register Settings Example:
HUM-900-PRO v1.2.3
(C) 2014 Linx Technologies Inc. All rights reserved. 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 at the same baud rate when a message is ready to send, the module waits before sending its payload. This helps to eliminate RF message corruption at the expense of additional latency. By default, CSMA is enabled. Figure 58 shows examples of the commands and Figure 59 shows the available values. HumPROTM Series CSMA Enable Read Command Read Response Header Size Escape Address ACK Address Value 0xFF 0x02 0xFE 0x56 0x0B 0x06 0x56 0x0B V Write Command Header Size Address Value 0xFF 0x02 0x56 0x0B V Figure 58: HumPROTM Series CSMA Enable Command and Response HumPROTM Series CSMA Enable Register Settings V 0x00 0x01 Mode Disable CSMA Enable CSMA Figure 59: HumPROTM Series CSMA Enable Register Settings See the Carrier Sense Multiple Access section for details. 62 63 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. This is the only setting in which the RF circuitry is able to receive and transmit RF messages. Sleep disables all circuitry on-board the module. This is the lowest-power setting available for the module. Please see the Low Power States section for more details. Figure 60 shows examples of the commands and Figure 61 shows the available values. HumPROTM Series Idle Mode Read Command Read Response Header Size Escape Address ACK Address Value 0xFF 0x02 0xFE 0x58 0x0D 0x06 0x58 0x0D V Write Command Header Size Address Value 0xFF 0x02 0x58 0x0D V Figure 60: HumPROTM Series Idle Mode Command and Response HumPROTM Series Idle Mode Register Settings V 0x00 0x01 Mode Awake Sleep Figure 61: HumPROTM Series Idle Mode Register Settings 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. If the SHOWVER register is 1, the ACK is sent after the firmware version. 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 62 shows examples of the commands and Figure 63 shows the available values. HumPROTM Series ACK on Wake Read Command Read Response Header Size Escape Address ACK Address Value 0xFF 0x02 0xFE 0x59 0x0E 0x06 0x59 0x0E V Write Command Header Size Address Value 0xFF 0x02 0x59 0x0E V Figure 62: HumPROTM Series ACK on Wake Command and Response HumPROTM Series ACK on Wake Register Settings V 0x00 0x01 Mode Disable ACK Enable ACK Figure 63: HumPROTM Series ACK on Wake Register Settings 64 65 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. These registers are automatically filled with the source address from a received message if AUTOADDR = 1. Please see the Addressing Modes section for more details. Each register byte is read and written separately. Figure 64 shows the User Destination ID registers. HumPROTM Series User Destination Address Registers Name Volatile Address Non-Volatile Address Description UDESTID3 UDESTID2 0x5A 0x5B UDESTID1 0x5C UDESTID0 0x5D 0x0F 0x10 0x11 0x12 MSB of the extended destination address Byte 2 of the extended destination address Byte 1 of the extended destination address, MSB of the short destination address LSB of the extended destination address and short destination address 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. Please see the Addressing Modes section for more details. Each register byte is read and written separately. Figure 65 shows the User Source ID registers. HumPROTM Series User Source Address Registers Volatile Address Non-Volatile Address Description Name USRCID3 USRCID2 USRCID1 0x5E 0x5F 0x60 USRCID0 0x61 0x13 0x14 0x15 0x16 MSB of the extended source address Byte 2 of the extended source address Byte 1 of the extended source address MSB of the short source address LSB of the extended source address and short source address Figure 64: HumPROTM Series User Destination Address Registers Figure 65: HumPROTM Series User Source Address Registers 66 67 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. HumPROTM Series User ID Mask Registers Name UMASK3 UMASK2 UMASK1 UMASK0 Volatile Address Non-Volatile Address Description 0x62 0x63 0x64 0x65 0x17 0x18 0x19 0x1A MSB of the extended mask Byte 2 of the extended mask Byte 1 of the extended mask MSB of the short mask LSB of the extended mask and short mask Figure 66: HumPROTM Series User ID Mask Registers 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. Figure 67 shows the Destination DSN registers. HumPROTM Series Destination DSN Registers Name DESTDSN3 DESTDSN2 DESTDSN1 DESTDSN0 Volatile Address Non-Volatile Address Description 0x68 0x69 0x6A 0x6B 0x1D 0x1E 0x1F 0x20 MSB of the destination DSN Byte 2 of the destination DSN Byte 1 of the destination DSN LSB of the destination DSN Figure 67: HumPROTM Series Destination DSN Registers EXMASK - Exception Mask Volatile Address = 0x6C; Non-Volatile Address = 0x21 The module has a built-in exception engine that can notify the host processor of an unexpected event. When an exception occurs, this register is ANDed with the exception code. A non-zero result causes the EX line to go high. Reading the EXCEPT register clears the exception and resets the EX line. If the ANDed result is zero, the EX line is not asserted but the exception code is stored in the EXCEPT register. Please see the Exception Engine section for more details. Figure 68 shows examples of the commands and Figure 69 shows the available values. HumPROTM Series Exception Mask Read Command Read Response Header Size Escape Address ACK Address Value 0xFF 0x02 0xFE 0x6C 0x21 0x06 0x6C 0x21 V Write Command Header Size Address Value 0xFF 0x02 0x6C 0x21 V Figure 68: HumPROTM Series Transceiver Exception Mask Command and Response HumPROTM Series Example Exception Masks V Exception Name 0x08 0x10 0x20 0x40 0x60 Allows only EX_BUFOVFL and EX_RFOVFL to trigger the EX line Allows only EX_WRITEREGFAILED to trigger the EX line Allows only EX_NORFACK to trigger the EX line Allows only EX_BADCRC, EX_BADHEADER, EX_BADSEQID and EX_ BADFRAMETYPE exceptions to trigger the EX line Allows EX_BADCRC, EX_BADHEADER, EX_BADSEQID, EX_BADFRAMETYPE and EX_NORFACK exceptions to trigger the EX line 0xFF Allows all exceptions to trigger the EX line Figure 69: HumPROTM Series Transceiver Example Exception Masks 68 69 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. This register setting is overridden when PKOPT:RXPKT=1. Figure 70 shows examples of the commands and Figure 71 shows the available values. HumPROTM Series CMD Halts Traffic Read Command Read Response Header Size Escape Address ACK Address Value 0xFF 0x02 0xFE 0x6E 0x23 0x06 0x6E 0x23 V Write Command Header Size Address Value 0xFF 0x02 0x6E 0x23 V Figure 70: HumPROTM Series Transceiver CMD Halts Traffic Command and Response COMPAT - Compatibility Mode Volatile Address = 0x70; Non-Volatile Address = 0x25 Compatibility mode allows the HumPROTM Series modules to communicate with the 250 Series modules. Please see the Compatibility Mode section for more details. Figure 72 shows examples of the commands and Figure 73 shows the available values. HumPROTM Series Compatibility Mode Read Command Read Response Header Size Escape Address ACK Address Value 0xFF 0x02 0xFE 0x70 0x25 0x06 0x70 0x25 V Write Command Header Size Address Value 0xFF 0x02 0x70 0x25 V Figure 72: HumPROTM Series Transceiver Compatibility Mode Command and Response HumPROTM Series Compatibility Mode Register Settings V 0x00 0x02 Mode Enable 250 Series Compatibility Mode Enable normal Addressing Operation HumPROTM Series CMD Halts Traffic Register Settings Figure 73: HumPROTM Series Compatibility Mode Register Settings V 0x00 0x01 Mode Disable Halt (received data is sent to the UART immediately) Enable Halt (received data is sent when the CMD line is high) Figure 71: HumPROTM Series CMD Halts Traffic Register Settings 70 71 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. The non-volatile register only uses the lower 4 bits to configure the automatic addressing. The upper 4 bits are not used. The volatile register is split in half with the lower 4 bits configuring the automatic addressing, the same as the non-volatile register. The upper 4 bits indicate the type of packet that was last received. This indication is the same as the Addressing Mode register setting. These bits are not used by the module and are only written by the module after successfully receiving a packet. As an example, if AUTOADDR is set to 0x0F (Any Auto Address) and a DSN packet is received from another module, then AUTOADDR reads back as 0x4F. The lower 4 bits (0xF) indicate that the module is set to any auto address (0xF). The upper 4 bits (0x4) indicate that the packet that was just received was a DSN Addressing Mode packet. Figure 74 summarizes the configuration values for the lower 4 bits of the register. Figure 75 shows the Addressing Mode values that the module writes to the upper 4 bits after successfully receiving a packet. HumPROTM Series Auto Addressing Register Settings Auto Address Value Meaning Action 0x00 0x04 0x06 0x07 Auto Addressing disabled DSN Auto Address User Auto Address Mode Destination Registers not populated Auto-populates DSN Address Destination Register Only Auto-populates User Address Destination Register Extended User Auto Address Mode Auto-populates Extended User Address Destination Register 0x0F Any Auto Address Mode Auto-populates DSN Destination or User Address Destination, depending on the received message type. Figure 74: HumPROTM Series Transceiver Auto Addressing Register Settings HumPROTM Series Auto Addressing Mode Indicator Addressing Mode Meaning 0x4 0x6 0x7 DSN Addressing Mode User Addressing Mode Extended User Addressing Mode Figure 75: HumPROTM Series Transceiver Auto Addressing Mode Indicator 72 73 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. CRSSI - Carrier Sense Minimum RSSI Non-Volatile Address = 0x3F This value is the minimum RSSI that causes the module to wait for a clear channel when CSMA is enabled. Figure 78 shows examples of the commands. HumPROTM Series Carrier Sense Minimum RSSI Read Command Header 0xFF Size 0x02 Write Command Header 0xFF Size 0x02 Escape Address 0xFE 0x3F Address Value 0x3F V Read Response ACK 0x06 Address Value 0x3F V Figure 78: HumPROTM Series Transceiver Carrier Sense Minimum RSSI Command and Response The value is a negative number in twos complement from -128 (0x80) to -1
(0xff). The default value is -70dBm.
!
Warning: The CRSSI value can have a significant impact on the performance of the module. Setting it too low could prevent the module from ever transmitting. Setting it too high can result in transmission collisions. Care must be taken if this value is adjusted. Figure 76 shows the Device Serial Number registers. HumPROTM Series DSN Registers Name MYDSN3 MYDSN2 MYDSN1 MYDSN0 Non-Volatile Address Description 0x34 0x35 0x36 0x37 MSB of the serial number Byte 2 of the serial number Byte 1 of the serial number LSB of the serial number Figure 76: HumPROTM Series DSN Registers CUSTID - Customer ID Non-Volatile Address = 0x39-0x3A These registers contain the factory-programmed customer ID. A unique value is assigned to a specific customer and that value is programmed into that customers modules. The unencrypted User and Extended User Addressing modes use these bytes as part of the addressing. The unique value ensures that the custom modules will not communicate with any other systems. Contact Linx for details. Figure 77 shows the Customer ID registers. HumPROTM Series Customer ID Registers Name CUSTID1 CUSTID0 Non-Volatile Address Description 0x39 0x3A MSB of the customer ID LSB of the customer ID Figure 77: HumPROTM Series Transceiver Customer ID Registers 74 75 RELEASE - Release Number Non-Volatile Address = 0x78 This register contains a number designating the firmware version and hardware platform. Figure 79 shows examples of the commands and Figure 80 lists current releases to date. HumPROTM Series Release Number Read Command Header 0xFF Size 0x02 Escape Address 0xFE 0x78 Read Response ACK 0x06 Address Value 0x78 V Figure 79: HumPROTM Series Transceiver Release Number Command and Response HumPROTM Series Release Number Register Settings V 0x20 Release Number HUM-900-PRO Figure 80: HumPROTM Series Transceiver Release Number Register Settings A more detailed firmware version is available for versions 0x20 and above in the FWVER register. EXCEPT - Exception Code Volatile Address = 0x79 The module has a built-in exception engine that can notify the host processor of an unexpected event. If an exception occurs, the exception code is stored in this register. Reading from this register clears the exception and resets the EX line. If an exception occurs before the previous exception code is read, the previous value is overwritten. Please see the Exception Engine section for more details. Figure 81 shows examples of the commands and Figure 82 shows the available values. HumPROTM Series Exception Code Read Command Header 0xFF Size 0x02 Escape Address 0xFE 0x79 Read Response ACK 0x06 Address Value 0x79 V Figure 81: HumPROTM Series Transceiver Exception Code Command and Response HumPROTM Series Transceiver Exception Codes V 0x08 0x09 0x13 0x20 0x40 0x42 0x43 0x44 Exception Name Description EX_BUFOVFL EX_RFOVFL Internal UART buffer overflowed. Internal RF packet buffer overflowed. EX_WRITEREGFAILED Attempted write to register failed. EX_NOACK Acknowledgement packet not received after maximum number of retries. EX_BADCRC Bad CRC detected on incoming packet. EX_BADHEADER Bad CRC detected in packet header. EX_BADSEQID Sequence ID was incorrect in ACK packet. EX_BADFRAMETYPE Unsupported frame type specified. Figure 82: HumPROTM Series Transceiver Exception Codes 76 77 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. HumPROTM Series Last Good Packet RSSI Read Command Header 0xFF Size 0x02 Escape Address 0xFE 0x7B Read Response ACK 0x06 Address Value 0x7B V Figure 83: HumPROTM Series Transceiver Last Good Packet RSSI Command and Response ARSSI - Ambient RSSI Volatile Address = 0x7C This register returns the ambient receive signal strength on the current channel in dBm. The signal strength is measured as soon as the command is received. The register value is an 8-bit signed integer representing the RSSI in dBm. It is accurate to 3dB. HumPROTM Series Ambient RSSI Read Command Header 0xFF Size 0x02 Escape Address 0xFE 0x7C Read Response ACK 0x06 Address Value 0x7C V Figure 84: HumPROTM Series Transceiver Ambient RSSI Command and Response FWVER - Firmware Version Non-Volatile Address = 0xC0 - 0xC3 These read-only registers contain the firmware version number currently on the module. Each byte is a hexadecimal value: 12 03 01 00 indicates version 18.3.1.0. Each register byte is read separately. Figure 85 shows the Firmware Version registers. HumPROTM Series Firmware Version Registers Name FWVER3 FWVER2 FWVER1 FWVER0 Non-Volatile Address Description 0xC0 0xC1 0xC2 0xC3 Major version number Minor version number Incremental version number Suffix Figure 85: HumPROTM Series Firmware Version Registers Note: Encryption is implemented on modules with FWVER3 = 2 and higher. 78 79 NVCYCLE - Non-Volatile Erase Cycles Non-Volatile Address = 0xC4-0xC5 These read-only non-volatile registers contain the number of lifetime erase cycles performed for the non-volatile memory. The minimum lifetime erases is 2,000 erase cycles. Beyond this the erases may not be complete and the modules operation can become unpredictable. HumPROTM Series Non-Volatile Erase Cycles Registers Name NVCYCLE1 NVCYCLE0 Non-Volatile Address Description 0xC4 0xC5 MSB of the number of erase cycles LSB of the number of erase cycles Figure 86: HumPROTM Series Non-Volatile Erase Cycles Registers Between 13 and 158 non-volatile write operations can be made before an erase cycle is necessary. Writing the registers from lowest to highest address maximizes the number of write operations. It is recommended to write the desired default values to non-volatile memory and use the volatile registers for values that change frequently. These registers show the total number of erase cycles that have occurred. This gives an indication of the remaining life expectancy of the memory. Figure 86 shows the Non-Volatile Erase Cycles registers. LSTATUS - Output Line Status Volatile Address = 0xC6 This register contains the logic states of the output indicator lines, providing information to the host processor while using fewer GPIO lines. HumPROTM Series Output Line Status Read Command Header 0xFF Size 0x03 Read Response Escape Escape Address 0xFE 0xFE 0x46 ACK 0x06 Address Value 0xC6 LSTATUS Figure 87: HumPROTM Series Transceiver Output Line Status Command and Response Each bit in the byte that is returned by the read represents the logic state of one of the output indicator lines. Figure 88 shows which line each bit represents. HumPROTM Series Output Line Status LSTATUS Values LSTATUS Bit Line Status 0 1 2 3 4 5 6 7 EX Exception, 1 = exception has occurred PA_EN PA Enable, 1 = the transmitter is active LNA_EN LNA Enable, 1 = the receiver is active CTS Clear To Send, 1 = incoming data buffer near full MODE_IND Mode Indicator, 1 = RF data transfer is active (TX or RX) BE Buffer Empty, 1 = UART buffer is empty Reserved Reserved Figure 88: HumPROTM Series Output Line Status LSTATUS Values 80 81 CMD - Command Register Volatile Address = 0xC7 This volatile write-only register is used to issue special commands. HumPROTM Series Command Register Write Command Header 0xFF Size 0x03 Escape Address Value 0xFE 0x47 V Figure 89: HumPROTM Series Transceiver Command Register Command and Response Value V is chosen from among the options in Figure 90. HumPROTM Series CMD Values CMD Value Operation 0x1 0x2 0x3 0x4 0x5 0x6 0x07 0x10 0x11 0x12 0x13 SENDP Send Packet GETPH Get Packet Header GETPD Get Packet Data GETPHD Get Packet Header and Data CLRRXP Clear Received Packet CLROB Clear Outbound Buffer CLRIB Clear Input Buffer JOINCTL Join Process Control WRKEY Write Key CLRKEY Clear Key RLDKEY Reload Key 0x20 0xAA 0xBB NVRESET Reset non-volatile registers to factory default Figure 90: HumPROTM Series Command Register Values The Send Packet command starts data transmission. Operation differs depending on whether option TXPKT is set in the PKTOPT register. TXPKT = 0; this command operates the same as a data timeout with DATATO. All waiting data, up to the maximum allowed in the remaining channel time, is transmitted. TXPKT = 1; this command marks the end of an explicit packet in the outgoing buffer. All bytes in the packet are transmitted together. Following bytes are sent in the next packet. The max packet length is 192 bytes. Multiple packets can be queued with this command. 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 packet data can be read after completion of the header transfer. If the data is not read before this command is issued a second time, then the data is discarded and the header for the following packet is returned. A NAK response is returned if option RXPKT is disabled in the PKTOPT register or the previous GETPx command was not completed. The Get Packet Data command returns the received packet data using a received packet transfer cycle. If the packet header is not read first, then it is discarded. The packet data is then discarded after transfer. A NAK response is returned if option RXPKT is disabled in the PKTOPT register or the previous GETPx command was not completed. The Get Packet Header and Data command returns the received packet header, followed by the packet data using a received packet transfer cycle. The packet is discarded after transfer. A NAK response is returned if option RXPKT is disabled in the PKTOPT register or the previous GETPx command was not completed. The Clear Received Packet command removes the next unread packet from the RF incoming queue if RXPKT is enabled in the PKTOPT register. If the packet header was read but not the data, this command causes the data to be discarded. Although not required before reading the next packets header, it frees buffer space for more or longer messages. If a previous GETPx command did not deliver all the associated data, this command removes the undelivered data and terminates the previous GETPx command. If option RXPKT is disabled this command discards all received data which has not been delivered. The Clear Outbound Buffer command cancels any transmission in progress and clears the buffer of data to be transmitted. The Clear Input Buffer command discards all RF-received bytes and clears the EX_RXWAIT flag. 82 83 The Join Process Control command allows the software to initiate or stop the secure JOIN process. It has the following subcommands. The Clear Key command sets the selected key to all zeros. Figure 93 shows the structure of this command. HumPROTM Series Clear Key Command Write Command Header 0xFF Size 0x04 Escape Address 0xFE 0x47 Value 0x12 KeyN KeyN Figure 93: HumPROTM Series Transceiver Clear Key Command If KeyN is 0x01, the command writes to the volatile key registers. If it is 0x02, it writes to the non-volatile key registers. The Reload Key command copies the key in non-volatile memory (NKN) 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. This reset can also be done by toggling the PB line as described in the Restore Factory Defaults section. HumPROTM Series JOINCTL Subcommand Values Subcommand Value Operation 0 1 2 Halt JOIN operation Generate a random network key and address. This sets the module as the network master (SECOPT:KEYRCV=0) Perform the JOIN operation with another module Figure 91: HumPROTM Series JOINCTL Subcommand Values These operations are equivalent to the push-button initiated operation. If a JOIN operation is started by the serial command (CMD:JOINCTL[2]), push-button operation is ignored until the JOIN operation finishes. Register write operations are inhibited when a JOIN process is active except that a Halt JOIN command is never inhibited. A Halt JOIN operation completes before the ACK is sent. When the JOIN operation is started the KEYRCV flag in the SECOPT register determines whether the module is a master or slave and whether a key can be sent or changed. The JOIN process uses and modifies the non-volatile address registers. The Write Key command writes a 16-byte AES key to the selected key register. As with most of the registers, the encryption key has both volatile and non-volatile registers. The volatile register is used during run time, but is lost on a power cycle or reset. When the module powers up, the volatile register is loaded from the non-volatile register. This makes the non-volatile register value the default on power-up. HumPROTM Series Write Key Command Write Command Header 0xFF Size Size Escape Address 0xFE 0x47 Value 0x11 KeyN KeyN Key0 Key0
... .. Key15 Key15 Figure 92: HumPROTM Series Transceiver Write Key Command The key value of all zero bytes is reserved as a no key indication. Figure 92 shows the command for writing the AES key to the module. If KeyN is 0x01, the command writes to the volatile key register. If it is 0x02, it writes to the non-volatile key register. 84 85 SECSTAT - Security Status Volatile Address = 0xC9 This volatile read-only register provides status of the security features. HumPROTM Series Security Status 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. Read Command Header 0xFF Size 0x03 Escape Escape Address 0xFE 0xFE 0x49 ACK 0x06 Address Value 0xC9 V Read Response HumPROTM Series Join Status Figure 94: HumPROTM Series Transceiver Security Status Command and Response The command returns a single byte. Figure 95 shows the meanings of the bits in the returned value byte. HumPROTM Series Security Status Value Bit 0 1 2 3 4 5 6 7 Status Reserved 0 = No volatile key is set 1 = A volatile key is set 0 = No non-volatile key is set 1 = A non-volatile key is set Reserved Reserved Reserved Reserved Reserved Figure 95: HumPROTM Series Security Status Values Read Command Header 0xFF Size 0x03 Escape Escape Address 0xFE 0xFE 0x4A Read Response ACK 0x06 Address Value 0xCA V Figure 96: HumPROTM Series Transceiver Join Status Command and Response The command returns a single byte. Figure shows the meanings of the returned value byte. HumPROTM Series Join Status Value Bit Status Last Join Result (decimal):
Last Operation Successful 0: Module unpaired since restart 1: New key generated 2: Successfully sent address to another unit 3: Successfully sent address and key to another unit 4: Successfully obtained key from master 5: Successfully obtained address from master 6: Successfully obtained key and address from master 0 - 5 Last Operation Failed 10: Fail: operation canceled 11: Fail: timeout 12: Fail: too many joining units 13: Fail: Assignment message didnt contain key 14: Fail: Master has no key to send when SECOPT:PSHARE=1 15: Fail: Master has no address to send 16: Fail: Inconsistent Network Address Registers USRC, UMASK, LASTNETAD Current Operation 32: Detecting PB sequence 33: Waiting for joining unit 34: Another joining unit detected. Joining is in progress. 6 JOINACT MODE_IND is active with pairing status, serial write operations are inhibited Figure 97: HumPROTM Series Transceiver Join Status Value 86 87 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. HumPROTM Series Extended Exception Flags Registers Name EEXMASK2 EEXMASK1 EEXMASK0 Volatile Address Description 0xCD 0xCE 0xCF Byte 2 of the extended exception flags Byte 1 of the extended exception flags LSB of the extended exception flags Figure 98: HumPROTM Series Transceiver Extended Exception Code Registers When an exception occurs, the associated bit is set in this register. If the corresponding bit in the EEXMASK is set and EXMASK is zero, the EX status line is set. Reading an EEXFLAG register does not clear the register. Writing to an EEXFLAG register causes the register to be set to the BIT_AND(current_value, new_value). This provides a way of clearing bits that have been serviced without clearing a bit that has been set since the flag register was read. This prevents a loss of notification of an exception. Register bits can only be cleared, not set, from the write command though some flags are also cleared internally. Flag EX_TXDONE is set when a data packet has been transmitted. If the packet was sent with acknowledgement enabled, this flag indicates that the acknowledgment has also been received. It is cleared by writing a zero bit to EX_TXDONE in the register. Flag EX_RXWAIT is 1 when there are buffered incoming data bytes which have not been sent to the UART. It is cleared by reading or discarding all data bytes. Flag EX_UNENCRYPT is 1 when a received packet is not encrypted. This can only occur when SECOPT:EN_UNC=1. Flag EX_SEQDEC is 1 when a received encrypted packet has a smaller sequence number than the previously received packet. Possible causes are an attempt to replay a previous message by an attacker, receiving a message from a different transmitter or restarting the transmitter. 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. Possible causes are an attempt to replay a previous message by an attacker, receiving a message from a different transmitter or restarting the transmitter. HumPROTM Series Transceiver Extended Exception Codes Bit Exception Name Description EEXFLAG0 (0xCF) 0 1 2 3 4 5 6 7 EX_BUFOVFL EX_RFOVFL Internal UART buffer overflowed. Internal RF packet buffer overflowed. EX_WRITEREGFAILED Attempted write to register failed. EX_NOACK Acknowledgement packet not received after maximum number of retries. EX_BADCRC Bad CRC detected on incoming packet. EX_BADHEADER Bad CRC detected in packet header. EX_BADSEQID Sequence ID was incorrect in ACK packet. EX_BADFRAMETYPE Unsupported frame type specified. EEXFLAG1 (0xCE) 0 1 2 3 4 EX_TXDONE EX_RXWAIT EX_UNENCRYPT EX_SEQDEC EX_SEQSKIP 5 - 7 Reserved EEXFLAG2 (0xCD) 0 - 7 Reserved A data packet has been transmitted. Received data bytes are waiting to be read. Received packet was not encrypted. This can only occur when SECOPT: EN_UNENC=1. Received encrypted packet sequence number is less than previous Received encrypted sequence number is more than one higher the previous sequence number Figure 99: HumPROTM Series Transceiver Extended Exception Codes 88 89 Multiple outgoing packets can be buffered. Changing this option clears the incoming buffer, losing un-transmitted or unacknowledged data. When TXnCMD is 1, lowering the CMD line has the same effect as writing the SENDP command to the CMD register, triggering buffered data to be transmitted. Packet grouping is affected by option TXPKT. The minimum low time on the CMD line to terminate the packet is given in the Electrical Specifications. When RXPKT is 1, incoming packets are held until a GETPH, GETPD, or GETPHD command is written to the CMD register. Transfer uses a Packet Receive transfer. The CMDHOLD setting has no effect. When RXPKT is 0, incoming UART data is delivered without headers. The data flow is controlled by the CMDHOLD setting. When RXP_CTS is 1, the CTS line is used for the status line during a Packet Receive transfer and not for controlling data flow into the module. When it is 0, CTS is used for flow control and CRESP is used for the status line. PKTOPT - Packet Options Volatile Address = 0xD3; Non-Volatile Address = 0x83 This register selects options for transferring packet data. HumPROTM Series Packet Options Read Command Read Response Header Size Escape Address ACK Address Value 0xFF 0x02 0xFE 0xD3 0x83 0x06 0xD3 0x83 V Write Command Header Size Address Value 0xFF 0x02 0xD3 0x83 V Figure 100: HumPROTM Series Transceiver Packet Options Command and Response Each bit in the register sets an option as shown in Figure 101. HumPROTM Series Transceiver Packet Option Codes Bit 0 1 2 3 4 - 7 Name TXPKT TXnCMD RXPKT RXP_CTS Reserved Description Packet Transmit Transmit when nCMD Lowered Packet Receive Use CTS for RXPKT Transfer Reserved Figure 101: HumPROTM Series Transceiver Packet Option Codes The TXPKT option allows the module to transmit data in explicit packets. TXPKT = 0 (default); a packet transmission is enabled when the number of waiting bytes reaches BCTRIG bytes, the time since the last received byte exceeds DATATO ms, the number of waiting bytes exceeds the number that can be sent within the remaining slot time, or a Send Packet command is written to the CMD register. TXPKT = 1; all bytes written to the module are held until a SENDP command is written to the CMD register or the CMD line is lowered with TXnCMD = 1. The DATATO or BCTRIG conditions are ignored with this option. The transmitted packet consists of the bytes in the buffer at the time a packet is triggered, even if more data bytes are received before the packet can be sent. 90 91 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. When CHGADDR is 1 the JOIN process is allowed to generate a random network address if the module is a master unit. If the module is a slave unit it is allowed to accept an address assignment from the master unit. When KEYRCV is 1 the module is set to receive a network key from a master unit and act as a slave. When it is 0, the module is set to act as a master and send a network key and assign an address to the slave unit. In order for this bit to change from 1 to 0, the network key must be cleared, preventing slave units from being manipulated to transmit the key. This bit is cleared by the GENERATE_KEY push-button function. When EN_UNENC is 1 the module accepts unencrypted packets. If this bit is 0, unencrypted received packets are ignored. When EN_CHANGE is 1, changes to the SECOPT register bits 0-3, 5-7 are permitted from serial commands. Clearing this bit prevents any of these bits from changing without resetting the module to factory default, which clears the network key. SECOPT - Security Options Volatile Address = 0xD4; Non-Volatile Address = 0x84 This register selects options for security features. HumPROTM Series Security Options Read Command Read Response Header Size Escape Escape Address ACK Address Value 0xFF 0x03 0xFE 0xFE 0x54 0x04 0x06 0xD4 0x84 V Write Command Header Size Escape Address Value 0xFF 0x03 0xFE 0x54 0x04 V Figure 102: HumPROTM Series Transceiver Packet Options Command and Response Each bit in the register sets an option as shown in Figure 103. HumPROTM Series Transceiver Security Option Codes Bit Name Description 0 1 2 3 4 5 6 7 PB_RESET Permit factory reset from PB input sequence PSHARE PGKEY Permit key sharing Permit clearing key and changing key CHGADDR Permit changing an address KEYRCV 1: Receive key and address during JOIN operation (slave) 0: Send key and address during JOIN operation (master) EN_UNENC Enable receiving unencrypted packets Reserved Reserved EN_CHANGE Enable changes to security options Figure 103: HumPROTM Series Transceiver Security Option Codes When PB_RESET is 1 the Factory Reset function is enabled from the PB input. This allows a user to reset the module configurations back to the factory defaults with 4 short presses and a 3 second hold of a button connected to the PB input. When PSHARE is 1 the Share Network Key function is enabled during the JOIN process. This allows a master unit to share the encryption key it created. 92 93 EEXMASK - Extended Exception Mask Volatile Address = 0x80-0x82; Non-Volatile Address = 0xD0-0xD2 These registers contain a mask for the events in EEXFLAG, using the same offset and bit number. HumPROTM Series Extended Exception Mask Registers Name EEXMASK2 EEXMASK1 EEXMASK0 Volatile Address Non-Volatile Address Description 0x80 0x81 0x82 0xD0 0xD1 0xD2 Byte 2 of the extended exception mask Byte 1 of the extended exception mask LSB of the extended exception mask Figure 104: HumPROTM Series Transceiver Extended Exception Mask Registers To use this value, register EXMASK must be zero. If EXMASK is non-zero, this register has no effect on the EX line. When an exception bit is set in EEXFLAG, the corresponding EEXMASK bit is set, and EXMASK is zero, the EX status line is set, otherwise the EX line is reset. Mask bits for unassigned flags should be zero for future compatibility. Typical Applications Figure 106 shows a typical circuit using the HumPROTM Series transceiver. RXD TXD GPIO GPIO GPIO INT/GPIO GPIO GPIO VCC GND GND 30 31 32 1 2 3 4 BE NC NC NC NC NC GND VCC GND 9 2 8 2 7 2 6 2 5 2 4 2 3 2 2 2 1 2 B P S T C MODE_IND D N G N E _ A P C C V N E _ A N L T E S E R N I _ A T A D _ D M C T U O _ A T A D _ D M C GND ANT GND GND GND GND GND 20 19 18 17 16 15 14 GND GND GND GND GND GND P S E R C C N C N D N G X E C N C N N W O D _ R E W O P D M C 5 6 7 8 9 0 1 1 1 2 1 3 1 GND Figure 106: HumPROTM Series Transceiver Basic Application Circuit An external microcontroller provides data and configuration commands. Its UART (TXD, RXD) is connected to the modules UART (CMD_DATA_IN, CMD_DATA_OUT). The CTS line is monitored for flow control. GPIOs on the microcontroller are connected to lines on the module:
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 master. It is initially set to the master address It monitors the CRESP line to know when the data coming out of the module is transmitted data or a response to a command. It monitors the EX line to know if there is an error. This line may be connected to an interrupt line for faster response. HumPROTM Series Extended Exception Mask Registers Name Non-Volatile Address Description LASTNETAD3 LASTNETAD2 LASTNETAD1 LASTNETAD0 0x8C 0x8D 0x8E 0x8F MSB of the last network address assigned Byte 2 of the last network address assigned Byte 1 of the last network address assigned LSB of the last network address assigned Figure 105: HumPROTM Series Transceiver Extended Exception Mask Registers when a network key is generated. It controls the POWER_DOWN line to place the module into a low power state. It controls the CMD line to toggle between configuration commands and data to be transmitted over the air. The MODE_IND line is connected to an LED for visual indication that the module is active. The PB line is connected to a pushbutton that takes the line to VCC when it is pressed. A resistor pulls the line to ground when the button is not pressed. 94 95 Usage Guidelines for FCC Compliance The pre-certified versions of the HumPROTM Series module
(HUM-900-PRO-UFL and HUM-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. The integrator does not need to conduct any further testing under these rules provided that the following guidelines are met:
An approved antenna must be directly coupled to the modules U.FL connector through an approved coaxial extension cable or to the modules castellation pad using an approved reference design and PCB layer stack. Alternate antennas can be used, but may require the integrator to perform certification testing. The module must not be modified in any way. Coupling of external circuitry must not bypass the provided connectors. End product must be externally labeled with Contains FCC ID:
OJM900MCA / IC: 5840A-900MCA. The end products users manual must contain an FCC statement equivalent to that listed on page 97 of this data guide. The antenna used for this transceiver must not be co-located or operating in conjunction with any other antenna or transmitter. The integrator must not provide any information to the end-user on how to install or remove the module from the end-product. Any changes or modifications not expressly approved by Linx Technologies could void the users authority to operate the equipment. Additional Testing Requirements The HUM-900-PRO-UFL and HUM-900-PRO-CAS have been tested for compliance as an intentional radiator, but the integrator is required to perform unintentional radiator testing on the final product per FCC sections 15.107 and 15.109 and Industry Canada license-exempt RSS standards. Additional product-specific testing might be required. Please contact the FCC or Industry Canada regarding regulatory requirements for the application. Ultimately is it the integrators responsibility to show that their product complies with the regulations applicable to their product.Versions other than the -UFL and -CAS have not been tested and require full compliance testing in the end product as it will go to market. Information to the user The following information must be included in the products user manual. FCC / IC NOTICES This product contains FCC ID: OJM900MCA / IC: 5840A-900MCA. This device complies with Part 15 of the FCC rules and Industry Canada license-exempt RSS standards. Operation of this device is subject to the following two conditions:
1. This device may not cause harmful interference, and 2. this device must accept any interference received, including interference that may cause undesired operation. This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses and can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio communications. However, there is no guarantee that interference will not occur in a particular installation. If this equipment does cause harmful interference to radio or television reception, which can be determined by turning the equipment off and on, the user is encouraged to try to correct the interference by one or more of the following measures:
Reorient or relocate the receiving antenna. Connect the equipment into an outlet on a circuit different from that to which Increase the separation between the equipment and receiver. the receiver is connected. Consult the dealer or an experienced radio/TV technician for help. Any modifications could void the users authority to operate the equipment. Le prsent appareil est conforme aux CNR dIndustrie Canada applicables aux appareils radio exempts de licence. Lexploitation est autorise aux deux conditions suivantes:
1. 2. lappareil ne doit pas produire de brouillage, et utilisateur de lappareil doit accepter tout brouillage radiolectrique subi, mme si le brouillage est susceptible den compromettre le fonctionnement. 96 97 Product Labeling The end product containing the HUM-900-PRO-UFL or HUM-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: OJM900MCA / IC: 5840A-900MCA The label must be permanently affixed to the product and readily visible to the user. Permanently affixed means that the label is etched, engraved, stamped, silkscreened, indelibly printed, or otherwise permanently marked on a permanently attached part of the equipment or on a nameplate of metal, plastic, or other material fastened to the equipment by welding, riveting, or a permanent adhesive. The label must be designed to last the expected lifetime of the equipment in the environment in which the equipment may be operated and must not be readily detachable. FCC RF Exposure Statement To satisfy RF exposure requirements, this device and its antenna must operate with a separation distance of at least 20cm from all persons and must not be co-located or operating in conjunction with any other antenna or transmitter. Antenna Selection Under FCC and Industry Canada regulations, the HUM-900-PRO-UFL and HUM-900-PRO-CAS radio transmitters may only operate using an antenna of a type and maximum (or lesser) gain approved for the transmitter by the FCC and Industry Canada. To reduce potential radio interference to other users, the antenna type and its gain should be so chosen that the equivalent isotropically radiated power (e.i.r.p.) is not more than that necessary for successful communication. The HUM-900-PRO-UFL and HUM-900-PRO-CAS radio transmitters have been approved by the FCC and Industry Canada to operate with the antenna types listed in Figure 107 with the maximum permissible gain and required antenna impedance for each antenna type indicated. Antenna types not included in this list, having a gain greater than the maximum gain indicated for that type, are strictly prohibited for use with this device. Conformment la rglementation dIndustrie Canada, le prsent metteur radio peut fonctionner avec une antenne dun type et dun gain maximal
(ou infrieur) approuv pour lmetteur par Industrie Canada. Dans le but de rduire les risques de brouillage radiolectrique lintention des autres utilisateurs, il faut choisir le type dantenne et son gain de sorte que la puissance isotrope rayonne quivalente (p.i.r.e.) ne dpasse pas lintensit ncessaire ltablissement dune communication satisfaisante. Le prsent metteur radio (HUM-900-PRO-UFL, HUM-900-PRO-CAS) a t approuv par Industrie Canada pour fonctionner avec les types dantenne numrs la Figure 107 et ayant un gain admissible maximal et limpdance requise pour chaque type dantenne. Les types dantenne non inclus dans cette liste, ou dont le gain est suprieur au gain maximal indiqu, sont strictement interdits pour lexploitation de lmetteur. Antennas / Antennes Linx Part Number Rfrence Linx Tested Antennas Type Gain Impedance Impdance Valid For ANT-916-CW-QW Wave Whip ANT-916-CW-HW Wave Dipole Helical ANT-916-PW-LP Wave Whip ANT-916-PW-QW-UFL Wave Whip ANT-916-SP Wave Planar 1.8dBi 1.2dBi 2.4dBi 1.8dBi 1.4dBi ANT-916-WRT-RPS ANT-916-WRT-UFL Wave Dipole Helical 0.1dBi Antennas of the same type and same or lesser gain ANT-916-CW-HD ANT-916-PW-QW ANT-916-CW-RCL ANT-916-CW-RH Wave Whip Wave Whip Wave Whip Wave Whip 0.3dBi 1.8dBi 2.0dBi 1.3dBi ANT-916-CW-HWR-RPS Wave Dipole Helical 1.2dBi ANT-916-PML Wave Dipole Helical 0.4dBi ANT-916-PW-RA Wave Whip ANT-916-USP Cable Assemblies / Assemblages de Cbles Wave Planar 0.0dBi 0.3dBi 50 50 50 50 50 50 50 50 50 50 50 50 50 50 CAS Both CAS UFL CAS CAS UFL Both Both Both Both Both Both CAS CAS Linx Part Number Rfrence Linx Description CSI-RSFB-300-UFFR*
RP-SMA Bulkhead to U.FL with 300mm cable CSI-RSFE-300-UFFR*
RP-SMA External Mount Bulkhead to U.FL with 300mm cable
* Also available in 100mm and 200mm cable length Figure 107: HumPROTM Series Transceiver Approved Antennas 98 99 Castellation Version Reference Design The castellation connection for the antenna on the pre-certified version allows the use of embedded antennas as well as removes the cost of a cable assembly for the u.FL connector. However, the PCB design and layer stack must follow one of the reference designs for the certification on the HUM-900-PRO-CAS to be valid. Figure 108 shows the PCB layer stack that should be used. Figure 109 shows the layout and routing designs for the different antenna options. Please see the antenna data sheets for specific ground plane counterpoise requirements. Layer Name Top Layer Dielectric 1 Mid-Layer 1 Thickness Material Copper 1.4mil FR-4 (Er = 4.6) 14.00mil Copper 1.4mil Dielectric 2 28.00mil FR-4 (Er = 4.6) Mid-Layer 2 Dielectric 3 Bottom Layer 1.4mil 14.00mil 1.4mil Copper FR-4 (Er = 4.6) Copper Figure 108: HumPROTM Series Transceiver Castellation Version Reference Design PCB Stack Note: The PCB design and layer stack for the HUM-900-RC-CAS must follow these reference designs for the pre-certification to be valid. The HUM-900-RC-UFL and the HUM-900-RC-CAS must use one of the antennas in Figure 44 in order for the certification to be valid. The HUM-900-RC and HUM-2.4-RC have not been tested and require full compliance testing in the end product as it will go to market. All modules require unintentional radiator compliance testing in the end product as it will go to market. 1 6 3 5 3 5 3 2 7
. 2 6 0 3 0 0 A M S V E R N O C 0 2 3 9 1 6 0 0 2 5 6 1 5 6 1 0 7 4 0 3 2 0 4 1 0 3 2 P L
-
W P
-
6 1 9
-
T N A
-
A R W P
-
6 1 9
-
T N A 6 1 2 0 8 3 P S
-
6 1 9
-
T N A S P R
-
T R W
-
6 1 9
-
T N A
-
W Q W C
-
6 1 9
-
T N A
-
W H W C
-
6 1 9
-
T N A 1 l i i t m 4 2
=
h d W p i r t s o r c M i r e y a L
-
d M n o i e n a p l d n u o r G s l i m n i e r a s t i n U 100 101 Figure 109: HumPROTM Series Transceiver Castellation Version Reference Design Power Supply Requirements 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 modules performance, so providing a clean power supply for the module should be a high priority during design. 10 Vcc IN Vcc TO MODULE
+
10F Figure 110: Supply Filter A 10 resistor in series with the supply followed by a 10F tantalum capacitor from Vcc to ground helps in cases where the quality of supply power is poor (Figure 110). This filter should be placed close to the modules supply lines. These values may need to be adjusted depending on the noise present on the supply line. Antenna Considerations The choice of antennas is a critical and often overlooked design consideration. The range, performance and legality of an RF link are critically dependent upon the antenna. While adequate antenna performance can often be obtained by trial and error methods, antenna design and matching is a complex task. Professionally designed antennas such as those from Linx (Figure 111) help ensure maximum performance and FCC and other regulatory compliance. Figure 111: Linx Antennas Linx transmitter modules typically have an output power that is higher than the legal limits. This allows the designer to use an inefficient antenna such as a loop trace or helical to meet size, cost or cosmetic requirements and still achieve full legal output power for maximum range. If an efficient antenna is used, then some attenuation of the output power will likely be needed. It is usually best to utilize a basic quarter-wave whip until your prototype product is operating satisfactorily. Other antennas can then be evaluated based on the cost, size and cosmetic requirements of the product. Additional details are in Application Note AN-00500. Interference Considerations The RF spectrum is crowded and the potential for conflict with unwanted sources of RF is very real. While all RF products are at risk from interference, its effects can be minimized by better understanding its characteristics. Interference may come from internal or external sources. The first step is to eliminate interference from noise sources on the board. This means paying careful attention to layout, grounding, filtering and bypassing in order to eliminate all radiated and conducted interference paths. For many products, this is straightforward; however, products containing components such as switching power supplies, motors, crystals and other potential sources of noise must be approached with care. Comparing your own design with a Linx evaluation board can help to determine if and at what level design-specific interference is present. External interference can manifest itself in a variety of ways. Low-level interference produces noise and hashing on the output and reduces the links overall range. High-level interference is caused by nearby products sharing the same frequency or from near-band high-power devices. It can even come from your own products if more than one transmitter is active in the same area. It is important to remember that only one transmitter at a time can occupy a frequency, regardless of the coding of the transmitted signal. This type of interference is less common than those mentioned previously, but in severe cases it can prevent all useful function of the affected device. Although technically not interference, multipath is also a factor to be understood. Multipath is a term used to refer to the signal cancellation effects that occur when RF waves arrive at the receiver in different phase relationships. This effect is a particularly significant factor in interior environments where objects provide many different signal reflection paths. Multipath cancellation results in lowered signal levels at the receiver and shorter useful distances for the link. 102 103 Pad Layout The pad layout diagrams below are designed to facilitate both hand and automated assembly. Figure 112 shows the footprint for the smaller version and Figure 113 shows the footprint for the pre-certified version. 0.520"
0.015"
0.420"
0.015"
0.028"
0.050"
0.070"
Figure 112: HUM-***-PRO Recommended PCB Layout 0.015"
0.060"
0.100"
0.101"
0.136"
0.090"
0.015"
0.028"
0.065"
0.060"
0.420"
0.015"
0.050"
0.070"
Figure 113: HUM-***-PRO-UFL/CAS Recommended PCB Layout Microstrip Details 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 modules antenna can effectively contribute to the length of the antenna, changing its resonant bandwidth. In order to minimize loss and detuning, some form of transmission line between the antenna and the module should be used unless the antenna can be placed very close (<18in) to the module. One common form of transmission line is a coax cable and another is the microstrip. This term refers to a PCB trace running over a ground plane that is designed to serve as a transmission line between the module and the antenna. The width is based on the desired characteristic impedance of the line, the thickness of the PCB and the dielectric constant of the board material. For standard 0.062in thick FR-4 board material, the trace width would be 111 mils. The correct trace width can be calculated for other widths and materials using the information in Figure 114 and examples are provided in Figure 115. Software for calculating microstrip lines is also available on the Linx website. Trace Board Ground plane Figure 114: Microstrip Formulas Example Microstrip Calculations Dielectric Constant Width / Height Ratio (W / d) Effective Dielectric Constant Characteristic Impedance () 4.80 4.00 2.55 1.8 2.0 3.0 3.59 3.07 2.12 50.0 51.0 48.8 104 Figure 115: Example Microstrip Calculations 105 Board Layout Guidelines The modules 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 modules 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 following section provides some basic design guidelines. During prototyping, the module should be soldered to a properly laid-out circuit board. The use of prototyping or perf boards results in poor performance and is strongly discouraged. Likewise, the use of sockets can have a negative impact on the performance of the module and is discouraged. The module should, as much as reasonably possible, be isolated from other components on your PCB, especially high-frequency circuitry such as crystal oscillators, switching power supplies, and high-speed bus lines. When possible, separate RF and digital circuits into different PCB regions. Make sure internal wiring is routed away from the module and antenna and is secured to prevent displacement. Do not route PCB traces directly under the module. There should not be any copper or traces under the module on the same layer as the module, just bare PCB. The underside of the module has traces and vias that could short or couple to traces on the products circuit board. The Pad Layout section shows a typical PCB footprint for the module. A ground plane (as large and uninterrupted as possible) should be placed on a lower layer of your PC board opposite the module. This plane is essential for creating a low impedance return for ground and consistent stripline performance. Use care in routing the RF trace between the module and the antenna or connector. Keep the trace as short as possible. Do not pass it under the module or any other component. Do not route the antenna trace on multiple PCB layers as vias add inductance. Vias are acceptable for tying together ground layers and component grounds and should be used in multiples. The -CAS version must follow the layout in Figure 109. Each of the modules ground pins should have short traces tying immediately to the ground plane through a via. Bypass caps should be low ESR ceramic types and located directly adjacent to the pin they are serving. A 50-ohm coax should be used for connection to an external antenna. A 50-ohm transmission line, such as a microstrip, stripline or coplanar waveguide should be used for routing RF on the PCB. The Microstrip Details section provides additional information. In some instances, a designer may wish to encapsulate or pot the product. There are a wide variety of potting compounds with varying dielectric properties. Since such compounds can considerably impact RF performance and the ability to rework or service the product, it is the responsibility of the designer to evaluate and qualify the impact and suitability of such materials. Helpful Application Notes from Linx It is not the intention of this manual to address in depth many of the issues that should be considered to ensure that the modules function correctly and deliver the maximum possible performance. We recommend reading the application notes listed in Figure 116 which address in depth key areas of RF design and application of Linx products. These applications notes are available online at www.linxtechnologies.com or by contacting the Linx literature department. Helpful Application Note Titles Note Number Note Title AN-00100 AN-00126 AN-00130 AN-00140 AN-00500 AN-00501 RF 101: Information for the RF Challenged Considerations for Operation Within the 902928MHz Band Modulation Techniques for Low-Cost RF Data Links The FCC Road: Part 15 from Concept to Approval Antennas: Design, Application, Performance Understanding Antenna Specifications and Operation Figure 116: Helpful Application Note Titles 106 107 Production Guidelines 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. Soldering Iron Tip Hand Assembly Pads located on the bottom of the module are the primary mounting surface (Figure 117). Since these pads are inaccessible during mounting, castellations that run up the side of the module have been provided to facilitate solder wicking to the modules underside. This allows for very quick hand soldering for prototyping and small volume production. If the recommended pad guidelines have been followed, the pads will protrude slightly past the edge of the module. Use a fine soldering tip to heat the board pad and the castellation, then introduce solder to the pad at the modules edge. The solder will wick underneath the module, providing reliable attachment. Tack one module corner first and then work around the device, taking care not to exceed the times in Figure 118. Solder PCB Pads Castellations Figure 117: Soldering Technique Warning: Pay attention to the absolute maximum solder times. Absolute Maximum Solder Times Hand Solder Temperature: +427C for 10 seconds for lead-free alloys Reflow Oven: +255C max (see Figure 119) Figure 118: Absolute Maximum Solder Times Automated Assembly For high-volume assembly, the modules are generally auto-placed. The modules have been designed to maintain compatibility with reflow processing techniques; however, due to their hybrid nature, certain aspects of the assembly process are far more critical than for other component types. Following are brief discussions of the three primary areas where caution must be observed. Reflow Temperature Profile The single most critical stage in the automated assembly process is the reflow stage. The reflow profile in Figure 119 should not be exceeded because excessive temperatures or transport times during reflow will irreparably damage the modules. Assembly personnel need to pay careful attention to the ovens profile to ensure that it meets the requirements necessary to successfully reflow all components while still remaining within the limits mandated by the modules. The figure below shows the recommended reflow oven profile for the modules. Recommended RoHS Profile Max RoHS Profile Recommended Non-RoHS Profile 255C 235C 217C 185C 180C 125C 300 250 200 150 100 50
) C o
(
t e r u a r e p m e T 0 30 60 90 120 150 180 210 240 270 300 330 360 Time (Seconds) Figure 119: Maximum Reflow Temperature Profile Shock During Reflow Transport Since some internal module components may reflow along with the components placed on the board being assembled, it is imperative that the modules not be subjected to shock or vibration during the time solder is liquid. Should a shock be applied, some internal components could be lifted from their pads, causing the module to not function properly. Washability The modules are wash-resistant, but are not hermetically sealed. Linx recommends wash-free manufacturing; however, the modules can be subjected to a wash cycle provided that a drying time is allowed prior to applying electrical power to the modules. The drying time should be sufficient to allow any moisture that may have migrated into the module to evaporate, thus eliminating the potential for shorting damage during power-up or testing. If the wash contains contaminants, the performance may be adversely affected, even after drying. 108 109 General Antenna Rules The following general rules should help in maximizing antenna performance. 1. Proximity to objects such as a users 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 120). In many cases, this isnt desirable for practical or ergonomic reasons, thus, an alternative antenna style such as a helical, loop or patch may be utilized and the corresponding sacrifice in performance accepted. plane as possible in proximity to the base of the antenna. In cases where the antenna is remotely located or the antenna is not in close proximity to a circuit board, ground plane or grounded metal case, a metal plate may be used to maximize the antennas performance. 5. Remove the antenna as far as possible from potential interference sources. Any frequency of sufficient amplitude to enter the receivers front end will reduce system range and can even prevent reception entirely. Switching power supplies, oscillators or even relays can also be significant sources of potential interference. The single best weapon against such problems is attention to placement and layout. Filter the modules power supply with a high-frequency bypass capacitor. Place adequate ground plane under potential sources of noise to shunt noise to ground and prevent it from coupling to the RF stage. Shield noisy board areas whenever practical. 3. 4. OPTIMUM USABLE NOT RECOMMENDED Figure 120: Ground Plane Orientation 6. CASE If an internal antenna is to be used, keep it away from other metal components, particularly large items like transformers, batteries, PCB tracks and ground planes. In many cases, the space around the antenna is as important as the antenna itself. Objects in close proximity to the antenna can cause direct detuning, while those farther away will alter the antennas symmetry. GROUND PLANE
(MAY BE NEEDED) NUT ANTENNA (MARCONI) VERTICAL /4 GROUNDED In many antenna designs, particularly -wave whips, the ground plane acts as a counterpoise, forming, in essence, a -wave dipole (Figure 121). For this reason, adequate ground plane area is essential. The ground plane can be a metal case or ground-fill areas on a circuit board. Ideally, it should have a surface area less than or equal to the overall length of the -wave radiating element. This is often not practical due to size and configuration constraints. In these instances, a designer must make the best use of the area available to create as much ground GROUND PLANE VIRTUAL /4 DIPOLE DIPOLE ELEMENT
/4
/4 E I In some applications, it is advantageous to place the module and antenna away from the main equipment (Figure 122). This can avoid interference problems and allows the antenna to be oriented for optimum performance. Always use 50 coax, like RG-174, for the remote feed. NOT RECOMMENDED OPTIMUM USABLE CASE GROUND PLANE
(MAY BE NEEDED) NUT Figure 122: Remote Ground Plane Figure 121: Dipole Antenna 110 111 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 123) provides outstanding overall performance and stability. A low-cost whip can be easily fabricated from a wire or rod, but most designers opt for the consistent performance and cosmetic appeal of a professionally-made model. To meet this need, Linx offers a wide variety of straight and reduced height whip style antennas in permanent and connectorized mounting styles. Figure 123: Whip Style Antennas L =
234 FMHz The wavelength of the operational frequency determines an antennas overall length. Since a full wavelength is often quite long, a partial - or -wave antenna is normally employed. Its size and natural radiation resistance make it well matched to Linx modules. The proper length for a straight -wave can be easily determined using the formula in Figure 124. It is also possible to reduce the overall height of the antenna by using a helical winding. This reduces the antennas bandwidth but is a great way to minimize the antennas physical size for compact applications. This also means that the physical appearance is not always an indicator of the antennas frequency. Figure 124:
L = length in feet of quarter-wave length F = operating frequency in megahertz Loop Style A loop or trace style antenna is normally printed directly on a products PCB (Figure 126). This makes it the most cost-effective of antenna styles. The element can be made self-resonant or externally resonated with discrete components, but its actual layout is usually product specific. Despite the cost advantages, loop style antennas are generally inefficient and useful only for short range applications. They are also very sensitive to changes in layout and PCB dielectric, which can cause consistency issues during production. In addition, printed styles are difficult to engineer, requiring the use of expensive equipment including a network analyzer. An improperly designed loop will have a high VSWR at the desired frequency which can cause instability in the RF stage. Figure 126: Loop or Trace Antenna Linx offers low-cost planar (Figure 127) and chip antennas that mount directly to a products PCB. These tiny antennas do not require testing and provide excellent performance despite their small size. They offer a preferable alternative to the often problematic printed antenna. Figure 127: SP Series Splatch and uSP MicroSplatch Antennas Specialty Styles Linx offers a wide variety of specialized antenna styles (Figure 125). Many of these styles utilize helical elements to reduce the overall antenna size while maintaining reasonable performance. A helical antennas bandwidth is often quite narrow and the antenna can detune in proximity to other objects, so care must be exercised in layout and placement. Figure 125: Specialty Style Antennas 112 113 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. When working with RF, a clear distinction must be made between what is technically possible and what is legally acceptable in the country where operation is intended. Many manufacturers have avoided incorporating RF into their products as a result of uncertainty and even fear of the approval and certification process. Here at Linx, our desire is not only to expedite the design process, but also to assist you in achieving a clear idea of what is involved in obtaining the necessary approvals to legally market a completed product. For information about regulatory approval, read AN-00142 on the Linx website or call Linx. Linx designs products with worldwide regulatory approval in mind. In the United States, the approval process is actually quite straightforward. The regulations governing RF devices and the enforcement of them are the responsibility of the Federal Communications Commission (FCC). The regulations are contained in Title 47 of the United States Code of Federal Regulations (CFR). Title 47 is made up of numerous volumes; however, all regulations applicable to this module are contained in Volume 0-19. It is strongly recommended that a copy be obtained from the FCCs website, the Government Printing Office in Washington or from your local government bookstore. Excerpts of applicable sections are included with Linx evaluation kits or may be obtained from the Linx Technologies website, www.linxtechnologies.com. In brief, these rules require that any device that intentionally radiates RF energy be approved, that is, tested for compliance and issued a unique identification number. This is a relatively painless process. Final compliance testing is performed by one of the many independent testing laboratories across the country. Many labs can also provide other certifications that the product may require at the same time, such as UL, CLASS A / B, etc. Once the completed product has passed, an ID number is issued that is to be clearly placed on each product manufactured. Questions regarding interpretations of the Part 2 and Part 15 rules or the measurement procedures used to test intentional radiators such as Linx RF modules for compliance with the technical standards of Part 15 should be addressed to:
Federal Communications Commission Equipment Authorization Division Customer Service Branch, MS 1300F2 7435 Oakland Mills Road Columbia, MD, US 21046 Phone: + 1 301 725 585 | Fax: + 1 301 344 2050 Email: labinfo@fcc.gov ETSI Secretaria 650, Route des Lucioles 06921 Sophia-Antipolis Cedex FRANCE Phone: +33 (0)4 92 94 42 00 Fax: +33 (0)4 93 65 47 16 International approvals are slightly more complex, although Linx modules are designed to allow all international standards to be met. If the end product is to be exported to other countries, contact Linx to determine the specific suitability of the module to the application. All Linx modules are designed with the approval process in mind and thus much of the frustration that is typically experienced with a discrete design is eliminated. Approval is still dependent on many factors, such as the choice of antennas, correct use of the frequency selected and physical packaging. While some extra cost and design effort are required to address these issues, the additional usefulness and profitability added to a product by RF makes the effort more than worthwhile. 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. Values may vary from lot-to-lot and are not guaranteed. Typical parameters can and do vary over lots and application. Linx Technologies makes no guarantee, warranty, or representation regarding the suitability of any product for use in any specific application. It is the customers responsibility to verify the suitability of the part for the intended application. NO LINX PRODUCT IS INTENDED FOR USE IN ANY APPLICATION WHERE THE SAFETY OF LIFE OR PROPERTY IS AT RISK. Linx Technologies DISCLAIMS ALL WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL LINX TECHNOLOGIES BE LIABLE FOR ANY OF CUSTOMERS INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING IN ANY WAY FROM ANY DEFECTIVE OR NON-CONFORMING PRODUCTS OR FOR ANY OTHER BREACH OF CONTRACT BY LINX TECHNOLOGIES. The limitations on Linx Technologies liability are applicable to any and all claims or theories of recovery asserted by Customer, including, without limitation, breach of contract, breach of warranty, strict liability, or negligence. Customer assumes all liability
(including, without limitation, liability for injury to person or property, economic loss, or business interruption) for all claims, including claims from third parties, arising from the use of the Products. The Customer will indemnify, defend, protect, and hold harmless Linx Technologies and its officers, employees, subsidiaries, affiliates, distributors, and representatives from and against all claims, damages, actions, suits, proceedings, demands, assessments, adjustments, costs, and expenses incurred by Linx Technologies as a result of or arising from any Products sold by Linx Technologies to Customer. Under no conditions will Linx Technologies be responsible for losses arising from the use or failure of the device in any application, other than the repair, replacement, or refund limited to the original product purchase price. Devices described in this publication may contain proprietary, patented, or copyrighted techniques, components, or materials. Under no circumstances shall any user be conveyed any license or right to the use or ownership of such items. 2015 Linx Technologies. All rights reserved. The stylized Linx logo, Wireless Made Simple, WiSE, CipherLinx and the stylized CL logo are trademarks of Linx Technologies.
| 1 2 | User Guide - RC | Users Manual | 2.60 MiB | May 06 2015 |
HumRCTM Series Remote Control and Sensor Transceiver 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. No OEM Linx Remote Control or Function Module should be modified for Life and Property Safety Situations. Such modification cannot provide sufficient safety and will void the products regulatory certification and warranty. Customers may use our (non-Function) Modules, Antenna and Connectors as part of other systems in Life Safety Situations, but only with necessary and industry appropriate redundancies and in compliance with applicable safety standards, including without limitation, ANSI and NFPA standards. It is solely the responsibility of any Linx customer who uses one or more of these products to incorporate appropriate redundancies and safety standards for the Life and Property Safety Situation application. Do not use this or any Linx product to trigger an action directly from the data line or RSSI lines without a protocol or encoder/
decoder to validate the data. Without validation, any signal from another unrelated transmitter in the environment received by the module could inadvertently trigger the action. All RF products are susceptible to RF interference that can prevent communication. RF products without frequency agility or hopping implemented are more subject to interference. This module does have a frequency hopping protocol built in, but the developer should still be aware of the risk of interference. Do not use any Linx product over the limits in this data guide. Excessive voltage or extended operation at the maximum voltage could cause product failure. Exceeding the reflow temperature profile could cause product failure which is not immediately evident. Do not make any physical or electrical modifications to any Linx product. This will void the warranty and regulatory and UL certifications and may cause product failure which is not immediately evident. Table of Contents 1 Description 1 Features 2 Ordering Information 2 Electrical Specifications 4 Absolute Maximum Ratings 5 Typical Performance Graphs 10 Pin Assignments 10 Pin Descriptions 12 Theory of Operation 13 Module Description 14 Transceiver Operation 15 Transmit Operation 16 Receive Operation 16 Acknowledgement 17 Automatic Responses 17 Permissions Mask 18 The Pair Process 19 Configuring the Status Lines 19 External Amplifier Control 20 Mode Indicator 20 Reset to Factory Default 21 Using the LVL_ADJ Line 22 Receiver Duty Cycle 23 Using the LATCH_EN Line 23 Using the Low Power Features 24 Triggered Transmissions 25 Frequency Hopping 26 The Command Data Interface 28 Serial Setup Configuration for Stand-alone Operation 30 Basic Hardware Operation 32 Typical Applications 34 Power Supply Requirements 34 Antenna Considerations 35 Helpful Application Notes from Linx 36 Interference Considerations 37 Pad Layout 37 Board Layout Guidelines 39 Microstrip Details 40 Production Guidelines 40 Hand Assembly 40 Automated Assembly 42 General Antenna Rules 44 Common Antenna Styles 46 Regulatory Considerations 0.55"
(13.97) HumRCTM Series Remote Control and Sensor Transceiver Data Guide Description The HumRCTM Series transceiver is designed for reliable bi-directional remote control applications. It consists of a highly optimized Frequency Hopping Spread Spectrum (FHSS) RF transceiver and integrated remote control transcoder. The FHSS system allows higher RF output power and, therefore, longer range than narrowband radios. It also provides much more noise immunity than narrowband radios, making the module suitable for use in noisy environments. Eight status lines can be set up in any combination of inputs and outputs for the transfer of button or contact states. A selectable acknowledgement indicates that the transmission was successfully received. Versions are available in the 902 to 928MHz and 2,400 to 2,483MHz frequency bands. Figure 1: Package Dimensions 0.45"
(11.43) 0.07"
(1.78) Primary settings are hardware-selectable, which eliminates the need for an external microcontroller or other digital interface. For advanced features, optional software configuration is provided by a UART interface; however, no programming is required for basic operation. Housed in a compact reflow-compatible SMD package, the transceiver requires no external RF components except an antenna, which greatly simplifies integration and lowers assembly costs. Features Low power consumption 232 possible addresses 8 status lines Bi-directional remote control Analog voltage and sensor inputs Low power receive modes Selectable acknowledgements No external RF components required No programming/tuning required Serial interface for optional software operation/configuration Tiny PLCC-32 footprint 1 Revised 5/14/2015 Ordering Information Ordering Information Part Number HUM-***-RC HUM-900-RC-UFL HUM-900-RC-CAS Description HumRCTM Series Remote Control Transceiver HumRCTM Series Remote Control Transceiver, Certified, UFL Connector HumRCTM Series Remote Control Transceiver, Certified, Castellation Connection EVM-***-RC HumRCTM Series Carrier Board EVM-900-RC-UFL EVM-900-RC-CAS MDEV-***-RC EVAL-***-RC HumRCTM Series Carrier Board with Certified module, UFL Connector HumRCTM Series Carrier Board with Certified module, Castellation Connection HumRCTM Series Master Development System HumRCTM Series Basic Evaluation Kit
*** = Frequency; 900MHz, 2.4GHz Figure 2: Ordering Information Absolute Maximum Ratings Absolute Maximum Ratings Supply Voltage Vcc Any Input or Output Pin RF Input Operating Temperature Storage Temperature 0.3 0.3 40 40 to to 0 to to
+3.9 VCC + 0.3
+85
+85 VDC VDC dBm C C Exceeding any of the limits of this section may lead to permanent damage to the device. Furthermore, extended operation at these maximum ratings may reduce the life of this device. Figure 3: Absolute Maximum Ratings Warning: This product incorporates numerous static-sensitive components. Always wear an ESD wrist strap and observe proper ESD handling procedures when working with this device. Failure to observe this precaution may result in module damage or failure. 2 Electrical Specifications HumRCTM Series Transceiver Specifications Parameter Power Supply Symbol Min. Typ. Max. Units Notes Operating Voltage Peak TX Supply Current VCC lCCTX 2.0 3.6 VDC 2.4GHz at +1dBm 2.4GHz at 10dBm 900MHz at +10dBm 900MHz at 0dBm Average TX Supply Current 2.4GHz at +1dBm 900MHz at +10dBm RX Supply Current Standby Current Power-Down Current RF Section Operating Frequency Band HUM-2.4-RC HUM-900-RC-xxx Number of Channels Channel Spacing HUM-2.4-RC HUM-900-RC-xxx Modulation Rate Receiver Section Spurious Emissions Receiver Sensitivity HUM-2.4-RC HUM-900-RC-xxx RSSI Dynamic Range Transmitter Section Output Power HUM-2.4-RC HUM-900-RC-xxx Harmonic Emissions lCCRX lSBY lPDN FC PO PH 2400 902 95 94 0
+8.5 3 28 19 36 22 22 27.5 25.5 0.5 0.5 25 2.03 500 38.4 99 98 85
+1
+9.5 41 29 20 38.5 24 24 28.5 28 1.4 1.4 mA mA mA mA mA mA mA A A 1,2 1,2 1,2 1,2 1,2 1,2 1,2,3 1,2 1,2 MHz 2483.5 MHz 928 MHz MHz kHz kbps
-47 dBm 5 5 5 6 6 6 dBm dBm dB dBm dBm dBc HumRCTM Series Transceiver Specifications Symbol Min. Typ. Max. Units Notes Parameter Output Power Control Range HUM-2.4-RC HUM-900-RC-xxx Antenna Port RF Impedance Environmental RIN Operating Temp. Range 40 Timing Module Turn-On Time Via VCC Via POWER_DOWN Via Standby Serial Command Response Status, Volatile R/W Analog Input Reading NV Update, Factory Reset IU to RU Status High Channel Dwell Time Interface Section Input Logic Low Logic High Output Logic Low, MODE_IND, CONFIRM Logic High, MODE_IND, CONFIRM Logic Low Logic High VIL VIH VOLM VOHM VOL VOH 0.7*VCC 0.7*VCC 0.7*VCC 56 40 50 1 6 80 6 6 4 4 4 4 4 8 8 8 7 dB dB C ms ms ms ms ms ms ms ms
+85 108 57 57 10 16 110 50 13.33 0.3*VCC VDC VDC 0.3*VCC VDC VDC 0.3*VCC 1,9 1,9 1,10 1,10 VON TX Vcc TX Sx TX MODE_IND RX Sx RX MODE_IND A B C D E F G H AB TX Power up Response <80ms HumRCTM Series Transceiver Timings TX Response from VCC or POWER_DOWN1,4 TX Response from Status line while IU in idle2 Item Description BC RX Initial Response 8 to 50ms with no interference CD Data Settle 4 to 8us EF Data Update Delay During Active Session 5 to 25ms EG Shutdown Duration 25 to 342ms GH RX MODE_IND Drop 6 to 8ms TX Response from Status line while IU / RU idle in RX3 AB RX Initial Response BC CD EF EG GH Data Settle Data Update Delay During Active Session Shutdown Duration RX MODE_IND Drop Minimum Maximum 8ms 12ms 1ms 50ms 8s 25ms 342ms 8ms 4ms 4s 5ms 25ms 6ms 1. 2. 3. From module off to VCC applied The module is set as an IU only and is in idle pending status line activation The module is set as an IU and RU and is idling in receive mode pending status line activation or receipt of a valid packet. 4. Maximum 80ms if VCC < 2.6V Figure 5: HumRCTM Series Timings Input power < 60dBm 1. Measured at 3.3V VCC 2. Measured at 25C 3. 4. Characterized but not tested 5. PER = 5%
6. Into a 50-ohm load 7. No RF interference 8. From end of command to start of response 9. 60mA source/sink 10. 6mA source/sink Figure 4: Electrical Specifications 4 5 Typical Performance Graphs
) m B d
(
r e w o P t t u p u O X T 5.00 0.00
-5.00
-10.00
-15.00
-20.00
-25.00
-30.00 0.00 0.25 0.50 0.75 1.00 1.25 1.50 1.75 2.00 2.25 2.50 2.75 3.00 3.25 3.30 5.0 4.0 3.0 2.0 1.0 0.0
) m B d
(
r e w o P t u p t u O r e t t i m s n a r T
-1.0 2.0 2.5 3.3 Supply Voltage (V) Figure 6: HumRCTM Series Transceiver Output Power vs. LVL_ADJ Resistance - HUM-2.4-RC LVL_ADJ Voltage (V) Figure 8: HumRCTM Series Transceiver Max Output Power vs. Supply Voltage - HUM-2.4-RC
) m B d
(
r e w o P t t u p u O X T 15.00 10.00 5.00 0.00
-5.00
-10.00
-15.00
-20.00
-25.00 0.00 0.08 0.15 0.23 0.30 0.38 0.45 0.53 0.61 0.68 0.76 0.83 0.91 0.98 1.00 LVL_ADJ Voltage (V) Figure 7: HumRCTM Series Transceiver Output Power vs. LVL_ADJ Resistance - HUM-900-RC
) m B d
(
r e w o P t u p t u O X T 11.0 10.5 10.0 9.5 9.0 8.5 2.0 2.5 3.3 Supply Voltage (V) Figure 9: HumRCTM Series Transceiver Max Output Power vs. Supply Voltage - HUM-900-RC
-40C 25C 85C 3.6
-40C 25C 85C 3.6 6 7
) A m
(
t n e r r u C y p p u S l 25C 85C
-40C 29.0 27.0 25.0 23.0 21.0 19.0 17.0 15.0
) A m
(
t n e r r u C y p p u S l 85C 25C
-40C 31.0 29.0 27.0 25.0 23.0 21.0 19.0 17.0 15.0
-35.0
-30.0
-25.0
-20.0
-15.0
-10.0
-5.0 0.0 5.0 10.0
-35.0
-30.0
-25.0
-20.0
-15.0
-10.0
-5.0 0.0 5.0 10.0 TX Output Power (dBm) TX Output Power (dBm) Figure 10: HumRCTM Series Transceiver Average Current vs. Transmitter Output Power at 2.5V - HUM-2.4-RC Figure 13: HumRCTM Series Transceiver Average TX Current vs. Transmitter Output Power at 3.3V - HUM-2.4-RC
) A m
(
t n e r r u C y p p u S l 40.0 35.0 30.0 25.0 20.0 15.0 85C
-40C 25C
) A m
(
t n e r r u C y p p u S l 40.0 35.0 30.0 25.0 20.0 15.0 85C
-40C 25C
-30.0
-25.0
-20.0
-15.0
-10.0
-5.0 0.0 5.0 10.0 15.0 TX Output Power (dBm)
-30.0
-25.0
-20.0
-15.0
-10.0
-5.0 0.0 5.0 10.0 15.0 TX Output Power (dBm) Figure 11: HumRCTM Series Transceiver Average Current vs. Transmitter Output Power at 2.5V - HUM-900-RC Figure 12: HumRCTM Series Transceiver Average TX Current vs. Transmitter Output Power at 3.3V - HUM-900-RC 8 9
) A m
(
t n e r r u C y p p u S l 29.0 28.5 28.0 27.5 27.0 26.5 26.0 85C
-40C 25C 2.0 2.5 3.3 3.6 Supply Voltage (V)
) A m
(
t n e r r u C y p p u S l 28.5 28.3 28.1 27.9 27.7 27.5 27.3 27.1 26.9 26.7 26.5 2.0 85C
-40C 25C 2.5 3.3 Supply Voltage (V) 3.6 Figure 14: HumRCTM Series Transceiver TX Current vs. Supply Voltage at Max Power - HUM-2.4-RC Figure 16: HumRCTM Series Transceiver TX Current vs. Supply Voltage at 0dBm - HUM-2.4-RC
) A m
(
t n e r r u C y p p u S l 39.5 39.0 38.5 38.0 37.5 37.0 36.5 36.0 35.5 2.0
-40C 25C 85C 2.5 3.3 Supply Voltage (V) 3.6 23.5 23.0 22.5 22.0 21.5 21.0 20.5
) A m
(
t n e r r u C y p p u S l 2.0
-40C 25C 85C 2.5 3.3 Supply Voltage (V) 3.6 Figure 15: HumRCTM Series Transceiver TX Current vs. Supply Voltage at Max Power - HUM-900-RC Figure 17: HumRCTM Series Transceiver TX Current vs. Supply Voltage at 0dBm - HUM-900-RC 10 11
) A m
(
t n e r r u C y p p u S l 27.00 26.50 26.00 25.50 25.00 24.50 24.00 23.50 23.00 85C 25C
-40C 10.00
) A m
(
t n e r r u C X R e g a r e v A 1.00 0.10 0.01 2.5V 3.3V 3.6V 2 2.1 2.2 2.3 2.4 2.5 2.6 2.7 2.8 2.9 3 3.1 3.2 3.3 3.4 3.5 3.6 0 15 30 45 60 75 90 105 120 135 150 165 180 195 210 225 240 255 Supply Voltage (V) Duty Cycle (s) Figure 18: HumRCTM Series Transceiver RX Current Consumption vs. Supply Voltage - HUM-2.4-RC Figure 20: HumRCTM Series Transceiver Average RX Current Consumption vs. Duty Cycle - HUM-2.4-RC
) A m
(
t n e r r u C y p p u S l 25.00 24.50 24.00 23.50 23.00 22.50 22.00 2 85C 25C
-40C
) A m
(
t n e r r u C X R e g a r e v A 10.00 1.00 0.10 0.01 2.5V 3.3V 3.6V 2.1 2.2 2.3 2.4 2.5 2.6 2.7 2.8 2.9 3 Supply Voltage (V) 3.1 3.2 3.3 3.4 3.5 3.6 0 15 30 45 60 75 90 105 120 135 150 165 180 195 210 225 240 255 Duty Cycle (s) Figure 19: HumRCTM Series Transceiver RX Current Consumption vs. Supply Voltage - HUM-900-RC Figure 21: HumRCTM Series Transceiver Average RX Current Consumption vs. Duty Cycle - HUM-900-RC 12 13
-40C 25C 85C
) m B d
(
i g n d a e R I S S R
-15.00
-25.00
-35.00
-45.00
-55.00
-65.00
-75.00
-85.00
-95.00
-105.00
-100.00 -90.00 -80.00 -70.00 -60.00 -50.00 -40.00 -30.00 -20.00 -10.00 0.00 Input Power (dBm)
) A
(
t n e r r u C y b d n a S t 1.80 1.60 1.40 1.20 1.00 0.80 0.60 0.40 0.20 0.00 2.5 85C 25C
-40C 3.3 Supply Voltage (V) Figure 22: HumRCTM Series Transceiver RSSI Voltage vs. Input Power - HUM-2.4-RC Figure 24: HumRCTM Series Transceiver Standby Current Consumption vs. Supply Voltage - HUM-2.4-RC
) m B d
(
i g n d a e R I S S R
-15.00
-25.00
-35.00
-45.00
-55.00
-65.00
-75.00
-85.00
-95.00
-105.00
-40C 25C 85C
-100.00 -90.00 -80.00 -70.00 -60.00 -50.00 -40.00 -30.00 -20.00 -10.00 0.00 Input Power (dBm)
) A
(
t n e r r u C y b d n a S t 1.40 1.20 1.00 0.80 0.60 0.40 0.20 0.00 2.5 85C 25C
-40C 3.3 Supply Voltage (V) Figure 23: HumRCTM Series Transceiver RSSI Voltage vs. Input Power - HUM-900-RC Figure 25: HumRCTM Series Transceiver Standby Current Consumption vs. Supply Voltage - HUM-900-RC 3.6 3.6 14 15 Pin Assignments T U O _ A T A D _ D M C I N _ A T A D _ D M C N E _ K C A I R A P N E _ A N L T E S E R N E _ A P D N G C C V 29 28 27 26 25 24 23 22 21 MODE_IND ACK_OUT LVL_ADJ S7 S6 S5 S4 30 31 32 1 2 3 4 20 19 18 17 16 15 14 GND ANT GND GND GND GND GND 5 6 78 9 10 11 12 13 3 S 2 S 1 S 0 S 0 C 1 C D N G N E _ H C T A L N W O D _ R E W O P Figure 26: HumRCTM Series Transceiver Pin Assignments (Top View) Pin Descriptions Pin Descriptions Pin Number Name I/O Description 1, 2, 3, 4, 5, 6, 7, 8 9, 14, 15, 16, 17, 18, 20, 25 S0S71 I/O Status Lines. Each line can be configured as either an input to register button or contact closures or as an output to control application circuitry. GND Ground 10 11 C0 C1 I I This line sets the input/output direction for status lines S0-S3. When low, the lines are outputs; when high they are inputs. This line sets the input/output direction for status lines S4-S7. When low, the lines are outputs; when high they are inputs. Pin Descriptions Pin Number Name I/O Description 12 POWER_DOWN I I Power Down. Pulling this line low places the module into a low-power state. The module is not functional in this state. Pull high for normal operation. Do not leave floating. 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). LATCH_EN ANTENNA 50-ohm RF Antenna Port VCC RESET LNA_EN PA_EN Supply Voltage I 0 O This line resets the module when pulled low. It should be pulled high for normal operation. Low Noise Amplifier Enable. This line is driven high when receiving. It is intended to activate an optional external LNA. Power Amplifier Enable. This line is driven high when transmitting. It is intended to activate an optional external power amplifier. CMD_DATA_OUT O Command Data Out. Output line for the serial interface commands CMD_DATA_IN ACK_EN PAIR 1 MODE_IND ACK_OUT LVL_ADJ Command Data In. Input line for the serial interface commands. If serial control is not used, this line should be tied to ground or POWER_DOWN to minimize current consumption. Pull this line high to enable the module to send an acknowledgement message after a valid control message has been received. A high on this line initiates the Pair process, which causes two units to accept each others transmissions. It is also used with a special sequence to reset the module to factory default configuration. This line indicates module activity. It can source enough current to drive a small LED, causing it to flash. The duration of the flashes indicates the modules current state. This line goes high when the module receives an acknowledgement message from another module after sending a control message. Level Adjust. The voltage on this line sets the transmitter output power level. I I I O O I 13 19 21 22 23 24 26 27 28 29 30 31 32 1. These lines have an internal 20k pull-down resistor Figure 27: HumRCTM Series Transceiver Pin Descriptions 16 17 Pre-Certified Module Pin Assignments The pre-certified version of the module has mostly the same pin assignments as the standard version. The antenna connection is routed to either a castellation (-CAS) or a u.FL connector (-UFL), depending on the part number ordered. The antenna pad is disconnected on the version with the connector. The RF is routed as shown in Figure 28 for the version without the connector. T U O _ A T A D _ D M C I N _ A T A D _ D M C S T C B P N E _ A N L T E S E R N E _ A P D N G C C V 29 28 27 26 25 24 23 22 21 RFACTV BE NC NC NC NC NC 30 31 32 1 2 3 4 T N A 19 D N G 18 5 6 7 8 9 10 11 12 13 C N C N P S E R C X E D N G C N C N D M C N W O D _ R E W O P Figure 28: HumRCTM Series Transceiver Pre-certified Version Pin Assignments (Top View) Module Dimensions 0.55"
(13.97) 0.45"
(11.43) Figure 29: HumRCTM Series Transceiver Dimensions 0.07"
(1.78) 0.812"
(20.62) 0.45"
(11.43) 0.116"
(2.95) Figure 30: HumRCTM Series Transceiver Pre-certified Version Dimensions 18 19 Theory of Operation The HumRCTM Series transceiver is a low-cost, high-performance synthesized FSK transceiver. Figure 31 shows the modules block diagram. ANTENNA ADC ADC R O T A L U D O M E D 0 90 FREQ SYNTH MODULATOR LNA PA PROCESSOR INTERFACE GPIO /
INTERFACE Figure 31: HumRCTM Series Transceiver RF Section Block Diagram The HumRCTM Series transceiver operates in the 2400 to 2483MHz and 902 to 928MHz frequency bands. The transmitter output power is programmable. The range varies depending on the modules frequency band, antenna implementation and the local RF environment. The RF carrier is generated directly by a frequency synthesizer that includes an on-chip VCO. The received RF signal is amplified by a low noise amplifier (LNA) and down-converted to I/Q quadrature signals. The I/Q signals are digitized by ADCs. A low-power onboard communications processor performs the radio control and management functions including Automatic Gain Control
(AGC), filtering, demodulation and packet synchronization. A control processor performs the higher level functions and controls the serial and hardware interfaces. A crystal oscillator generates the reference frequency for the synthesizer and clocks for the ADCs and the processor. Module Description The HumRCTM Series Remote Control module is a completely integrated RF transceiver and processor. It has two main modes of operation: hardware and software. Hardware operation is suitable for applications like keyfobs where no other processor, PC or interface is present. Software operation is more advanced and allows for more features and functionality. This guide focuses on hardware operation with some references to software operation. Please see Reference Guide RG-00104: the HumRCTM Series Command Data Interface for details on software operation. Since this module can act as both transmitter and receiver, terminology and descriptions can get confusing. This guide uses the term Initiating Unit (IU) to describe a module that is transmitting commands. Responding Unit (RU) is used to describe a module that is receiving commands. The module has 8 status lines numbered S0 through S7. These can be set as inputs for buttons or contacts or as outputs to drive application circuitry. When S0 is taken high on the IU, S0 goes high on the RU, and so forth. A line that is an input on one side needs to be set as an output on the other side. Up to two of the lines S4, S5, S6 and S7 can be configured as analog inputs through the Command Data Interface. The voltage on an analog input can be transmitted upon activation of a digital input, or automatically sent in response to a query from an IU. These are ideal for sensor-based applications. A trigger configuration provides self-timed periodic or limited-length transmission when an input goes high. The transceiver uses a Frequency Hopping Spread Spectrum (FHSS) algorithm. This allows for higher output power and longer range than narrow-band systems while still maintaining regulatory compliance. All aspects of managing the FHSS operations are automatically handled by the module. 20 21 Transceiver Operation The transceiver has two modes of operation: 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. The module stays in a low power sleep mode until a status line goes high, starting the Transmit Operation. If all of the status lines are set as outputs, then the module is set as an RU only. It stays in Receive Operation looking for a valid transmission from a paired IU. A module with both input and output status lines can operate as an IU and an RU. The module idles in Receive Operation until either a valid transmission is received or a status line input goes high, initiating the Transmit operation. When an input goes high, the transceiver captures the logic state of each of the status lines. The line states are placed into a packet along with the local 32-bit address. The IU transmits the control packets as it hops among 25 RF channels. An RU receives the packet and checks its Paired Module List to see if the IU has been paired with the module and is authorized to control it. If the IUs address is not in the table, then the RU ignores the transmission. If the address is in the table, then the RU calculates the channel hopping pattern from the IUs address and sets its status line outputs according to the received packet. It then hops along with the IU and updates the states of its outputs with every packet. Its outputs can be connected to external circuitry that activates when the lines go high. The RU can also send an acknowledgement back to the IU. Using the serial interface the RU can include up to two bytes of custom data with the acknowledgement, such as sensor data or battery voltage levels. Using the hardware control, if ACK_EN is high when a valid control packet is received, the RU sends back a simple acknowledgement (ACK). It can send an Acknowledge with Data (AWD) response when custom data is programmed into the module using a serial command. Transmit Operation Transmit operation can be started by a status line input going high or a serial command. Basic remote control applications use the status line activation. The module pulls the MODE_IND line high and repeatedly transmits control messages containing the local address and the state of all status lines. Between transmissions the module listens for acknowledgement messages. If an Acknowledge (ACK) or Acknowledge with Data (AWD) message is received for the transmitted data, the ACK_OUT line is asserted for 100ms. The ACK_OUT timing restarts on each ACK or AWD packet that is received. The transceiver sends control messages every 13.33ms as long as any of the status line inputs is high, updating the status line states with each packet. When all input lines are low, the module starts the shutoff sequence. During the shutoff sequence, the transmitter sends at least one packet with all outputs off. It then continues to transmit data until the current channel hopping cycle is complete, resulting in balanced channel use. If an input line is asserted during the shutoff sequence, the transmitter cancels the shutoff and extends the transmission sequence. The Transmit Control Data and Transmit IU Packet serial commands instruct the module to send control messages. The Transmit Control Data command is the serial command version of taking a status line input high. An external microcontroller can use this command to send a specified number of packets with a specified Status byte rather than taking status lines high. The Transmit IU Packet command sends a packet that causes the RU to respond with a packet that can include the readings of its two analog inputs. This is good for reading remote sensors without having a microcontroller on the sensor unit. This reduces the cost and development time for remote sensor units. The trigger configuration causes the module to send a pre-specified number of packets when a status line input goes high. This is good for remote monitoring and transmitting when an exception occurs without needing a microcontroller on the remote unit. 22 23 Receive Operation During Receive Operation, the module waits for a valid control message from an authorized (paired) transceiver. When a valid message is received, it locks onto the hopping pattern of the transmitter and asserts the MODE_ IND line. It compares the received status line states to the Permission Mask for the IU to see if the IU is authorized to activate the lines. The module sets all authorized outputs to match the received states. Only status line outputs are affected by received commands. The RU then checks the state of the ACK_EN line and transmits an acknowledgement packet if it is high. It looks for the next valid packet while maintaining the frequency hopping timing. As long as an RU is receiving valid commands from a paired IU, it will not respond to any other unit. Once eight consecutive packets are missed, the RU is logically disconnected from the IU and waits for the next valid packet from any IU. Acknowledgement 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. When the Responding Unit (RU) receives a valid Control Packet, it checks the state of the ACK_EN line. If it is high the module sends an Acknowledgement Packet. If the Initiating Unit (IU) receives an Acknowledgement Packet that has the same Address and Status Byte as in the Control Packet it originally sent, then it pulls the ACK_OUT line high. A continuous stream of Control Packets that triggers a continuous stream of Acknowledgement Packets keeps the ACK_OUT line high. Connecting the ACK_EN line to VCC causes the RU to transmit Acknowledgement Packets as soon as it receives a valid Control Packet. Alternately this line can be controlled by an external circuit that raises the line when a specific action has taken place. This confirms to the IU that the action took place rather than just acknowledging receipt of the signal. The module can also be configured to transmit an acknowledgement with two bytes of preset data. This feature is enabled using the Control Source parameter through the Command Data Interface (CDI). The IU outputs the received bytes on its CDI for presentation to an external microcontroller or computer. The data can include sensor values, battery voltage levels or current status line states. Note: Only one RU should be enabled to transmit an acknowledgement response for a given IU since multiple acknowledgements will interfere with each other. Automatic Responses Two of the status lines can be configured as analog inputs to measure voltage levels. An IU can send a Request Sample command to an RU to respond with the analog measurements in the acknowledgement. This allows a master unit to remotely read a sensor device without having to place a microcontroller on the sensor. The transceiver can be configured to respond with one or both analog values through the CDI. Please see Reference Guide RG-00104: the HumRC Series Command Data Interface for details on the CDI. Permissions Mask The HumRCTM Series Transceiver has a Permissions Mask in the RU that is used to control which status lines an IU is authorized to control. With most systems, if a transmitter is associated with a receiver then it has full control over the receiver. With the Permissions Mask, a transmitter can be granted authority to control only certain receiver outputs. If an IU does not have the authority to activate a certain line, then the RU does not set it. As an example, a factory worker can be given a fob that only opens the door to the factory floor while the CEO has a fob that can also open the executive offices. The hardware in the fobs is the same, but the permissions masks are set differently for each fob. The Pair process always sets the Permission Mask to full access. The mask can be changed through the serial interface. 24 25 The Pair Process The Pair process enables two transceivers to communicate with each other. Each transceiver has a local 32-bit address that is transmitted with every packet. If the address in the received packet is not in the RUs Paired Module List, then the transceiver does not respond. Adding devices to the authorized list is accomplished through the Pair process or by a serial command. Each module can be paired with up to 40 other modules. The Pair process is initiated by taking the PAIR line high or by sending the Pair Control serial command on both units to be associated. Activation on the PAIR line can either be a momentary pulse (less than two seconds) or a sustained high input, which can be used to extend the search and successful pairing display. With a momentary activation, the search is terminated after 30 seconds. If Pairing is initiated with a sustained high input, the search continues as long as the PAIR input is high. When Pair is activated, the module displays the Pair Search sequence on the MODE_IND line (Figure 33) and goes into a search mode where it looks for another module that is also in search mode. It alternates between transmit and receive, enabling one unit to find the other and respond. Once bidirectional communication is established, the two units store each others addresses in their Paired Module List with full Permissions Mask and display the Pair Found sequence on their MODE_IND lines. The Pair Found sequence is displayed for at least 3 seconds. If PAIR is held high, the Pair Found display is shown for as long as PAIR is high. If a paired unit is already in the Paired Module List, then no additional entry is added though the existing entrys Permissions Mask may be modified. When Pairing is initiated, the module pairs with the first unit it finds that is also in Pair Search. If multiple systems are being Paired in the same area, such as in a production environment, then steps should be taken to ensure that the correct units are paired with each other. The Pair process can be cancelled by taking PAIR high a second time or by issuing the Pair Control command with Cancel Pairing option. If the address table is full when the PAIR line is raised, the Pair Table Full sequence is displayed on the MODE_IND line for 10 seconds and neither of the Pairing units stores an address. In this case, the module should either be reset to clear the address table or the serial interface can be used to remove addresses. Configuring the Status Lines Each of the eight status lines can operate as a digital input or output. Configuring their direction can be done in two ways. Basic operation uses the C0 and C1 lines. When C0 is low, S0 through S3 are outputs; when C0 is high, S0 through S3 are inputs. Likewise when C1 is low, S4 through S7 are outputs; when C1 is high, S4 through S7 are inputs. This is shown in Figure 32. Status Line Direction Configuration Line C0 C1 0 1 S0 through S3 are outputs S0 through S3 are inputs S4 through S7 are outputs S4 through S7 are inputs Figure 32: MODE_IND Timing Advanced operation uses the CDI to set each line direction individually with the Status Line I/O Mask item. In addition, the Control Source Item is used to tell the module to use the serial command instead of the hardware line configuration. Up to two of the status lines in the S4 through S7 group can be configured as analog inputs. An analog input line is used only for reading an input line voltage and converting it to a digital value (Analog to Digital Conversion, ADC). The analog input selection is primary, overriding digital input/output selection. An analog input reading can be transmitted to another module when functioning as either an IU or RU. The digitized reading must be read through a serial command at the receiving end. The analog setting is configured through the CDI using the Analog Input Select item. Please see Reference Guide RG-00104: the HumRCTM Series Command Data Interface for details on the CDI. External Amplifier Control The HumRCTM Series transceiver has two output lines that are designed to control external amplifiers. The PA_EN line goes high when the module enters transmit mode. This can be used to activate an external power amplifier to boost the signal strength of the transmitter. The LNA_EN line goes high when the module enters receive mode. This can be used to activate an external low noise amplifier to boost the receiver sensitivity. These external amplifiers can significantly increase the range of the system at the expense of higher current consumption and system cost. 26 27 Mode Indicator The Mode Indicator line (MODE_IND) provides feedback about the current state of the module. This line switches at different rates depending on the modules current operation. When an LED is connected to this line it blinks, providing a visual indication to the user. Figure 33 gives the definitions of the MODE_IND timings. MODE_IND Timing Module Status Display Transmit Mode Solid ON when transmitting packets. Receive Mode Solid ON when receiving packets. Pair Search Pair Found Pair Error Remote Pair Error ON for 100ms, OFF for 900ms while searching for another unit during the Pair process ON for 400ms, OFF for 100ms when the transceiver has been Paired with another transceiver. This is displayed for at least 3 seconds. ON for 100ms, OFF for 100ms when the address table is full and another unit cannot be added. ON for 100ms, OFF for 100ms, ON for 100ms OFF for 300ms when the remote units address table is full and a Pair cannot be completed. Pair Cancelled ON for 100ms, OFF for 200ms, ON for 100ms when the Pair process is cancelled. Reset Acknowledgement ON for 600ms, OFF for 100ms, ON for 200ms, OFF for 100ms, ON for 200ms and OFF for 100ms when the reset sequence is recognized. Extended Pair Cancelled Solid ON when the pairing operation is cancelled and waiting for the PAIR line to go low. Figure 33: MODE_IND Timing Reset to Factory Default The transceiver is reset to factory default by taking the Pair line high briefly 4 times, then taking and holding Pair 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 the Reset Acknowledgement defined in Figure 33 until the PAIR line goes low. After the Reset Acknowledgement is shown and PAIR goes low, the configuration is initialized. Factory reset also clears the Paired Module table but does not change the local address. If the PAIR input timing doesnt match the reset sequence timing an Extended Pair Cancel sequence is shown when PAIR goes low. The module reverts to normal operation without a reset or pairing. Using the LVL_ADJ Line The Level Adjust (LVL_ADJ) line allows the transceivers output power to be easily adjusted for range control or lower power consumption. This is done by placing a voltage on the LVL_ADJ line. This can be done using a voltage divider or a voltage source. When the transceiver powers up, the voltage on this line is measured and the output power level is set accordingly. When LVL_ADJ is connected to VCC, the output power and current consumption are the highest. When connected to ground, the output power and current are the lowest. See the Typical Performance Graphs section (Figure 6) for a graph of the output power vs. LVL_ADJ voltage. Even in designs where attenuation is not anticipated, it is a good idea to place resistor pads connected to LVL_ADJ so that it can be used if needed. Figure 34 shows the voltages needed to set each power level and gives the approximate output power for each level. The output power levels are approximate and may vary part-to-part. Power Level vs. LVL_ADJ Voltage Ratio VLVL_ADJ/VCC ratio POUT @ 915MHz POUT @ 2.4GHz 0.00 0.08 0.15 0.23 0.30 0.38 0.45 0.53 0.61 0.68 0.76 0.83 0.91 0.98 1.00 19.83 15.46 15.48 10.59 10.60 6.05 6.03 0.95 0.96 4.30 4.29 6.66 9.84 9.84 9.83 27.96 26.50 24.88 21.32 18.74 16.94 14.66 10.82 9.26 7.39 5.26 1.99 0.57 1.73 1.73 Figure 34: Power Level vs. LVL_ADJ Voltage Voltage Ratio 28 29 Receiver Duty Cycle The module can be configured to automatically power on and off while in receive mode. Instead of being powered on all the time looking for transmissions from an IU, the receiver can wake up, look for data and go back to sleep for a configurable amount of time. If it wakes up and receives valid data, then it stays on and goes back to sleep when the data stops. This significantly reduces the amount of current consumed by the receiver. It also increases the time from activating the IU to getting a response from the RU. The duty cycle is controlled by the Duty Cycle serial command through the CDI. DCycle sets the number of seconds between receiver turn-on points as shown in Figure 35. DCycle TON TSBY ON Standby KeepOn Activity Figure 20 and Figure 21 show graphs of the average current consumption vs. duty cycle for several supply voltages. They show that the average current consumption can be significantly reduced with even a small duty cycle value. This is ideal for battery-powered applications that need infrequent updates or where response time is not critical. The KeepOn time is used to keep the receiver on after it has completed some activity. This activity includes completing a transmission and receiving a valid packet. After KeepOn seconds have elapsed with no transmit or valid receive activity, the module resumes duty cycle operation by going into standby for DCycle seconds. Please see Reference Guide RG-00104: the HumRCTM Series Command Data Interface for details on configuring the receiver duty cycle. Figure 35: Receiver Duty Cycle The modules average current consumption can be calculated with the following equation.
) +
DCycle
(
T
(
T AVG SBY SBY ON RX
=
) I I I Figure 36: Receiver Duty Cycle Average Current Consumption Equation TON is fixed at about 0.326 seconds and TSBY = DCycle - TON. The receiver current (IRX) and standby current (ISBY) vary with supply voltage, but some typical values are in Figure 37. HumRCTM Series Typical Current Consumption HUM-2.4-RC HUM-900-RC VCC
(VDC) IRX
(mA) ISBY
(mA) IRX
(mA) ISBY
(mA) 2.5 21.45 3.3 21.82 3.6 22.03 0.00040 0.00058 0.00063 22.94 23.73 24.02 0.00040 0.00058 0.00063 Figure 37: HumRCTM Series Transceiver Typical Current Consumption 30 31 Using the LATCH_EN Line The LATCH_EN line sets the outputs to either momentary operation or latched operation. During momentary operation the outputs go high for as long as control messages are received instructing the module to take the lines high. As soon as the control messages stop, the outputs go low. During latched operation, when a signal is received to make a particular status line high, it remains high until a separate activation is received to make it go low. The transmission must stop and the module must time out before it will register a second transmission and toggle the outputs. When the LATCH_EN line is high, all of the outputs are latched. A serial command is available to configure latching of individual lines. Using the Low Power Features The Power Down (POWER_DOWN) line can be used to completely power down the transceiver module without the need for an external switch. This line allows easy control of the transceiver power state from external components, such as a microcontroller. The module is not functional while in power down mode. If all of the status lines are configured as inputs, then the module operates as an IU only. It automatically goes into a low power state waiting for one of the inputs to be asserted. This conserves battery power until a transmission is required. Triggered Transmissions The HumRCTM Series Transceiver has a triggered transmission feature configured through the serial interface. This causes the IU to transmit messages as soon as a configured status line input goes high, but stop transmissions based on configuration selection. The logic allows timed or periodic transmissions for simple transmit-on-event conditions without an external microcontroller or other timing logic. This reduces the required energy and potential interference with other RF units when automatically transmitting. The configuration options are:
1. Transmission occurs as long as input is high. This is the same as normal, non-triggered operation. 2. Transmission lasts for the specified duration after a high-going edge, then stops until the next high-going edge (fixed ON period). 3. Transmission starts when an input goes high, stopping when the input goes low or the specified duration elapses, whichever occurs first. The transmission wont occur again until the input goes low, then high. 4. Transmission is periodic, with configured duration and interval, as long as the trigger status line is high (periodic ON when trigger is high). 5. The transmission terminates under conditions 14 above, or when an ACK is received. After an ACK no further trigger transmission occurs until the triggered status line goes low, then high again. 6. The transmission is periodic, like condition 4, but each transmission duration is terminated by receiving an acknowledgement. A status input not selected for trigger timing operates normally, transmitting as long as the input is high. It doesnt affect the timing of periodic transmissions, causing the two transmission requests to be logically ORed. Receiving control messages during the off period of a triggered periodic transmission can delay, but doesnt cancel periodic transmission. If there are multiple lines with edge triggers, they are logically ORed together to generate a single trigger signal. Please see Reference Guide RG-00104: the HumRCTM Series Command Data Interface for details on configuring triggered transmissions. 32 33 Frequency Hopping The module incorporates a Frequency Hopping Spread Spectrum (FHSS) algorithm. This provides immunity from narrow-band interference and complies with FCC and IC guidelines. The module uses 25 RF channels as shown in Figure 38. Each channel has a time slot of 13.33ms before the module hops to the next channel. This equal spacing allows a receiver to hop to the next channel at the correct time even if a packet is missed. Up to seven consecutive packets can be missed without losing synchronization. The hopping pattern (sequence of transmit channels) is determined from the transmitters address. Each sequence uses all 25 channels, but in different orders. Once a transmission starts, the module continues through a complete cycle. If the input line is taken low in the middle of a cycle, the module continues transmitting through the end of the cycle to ensure balanced use of all channels. Frequency hopping has several advantages over single channel operation. Hopping systems are allowed a higher transmitter output power, which results in longer range and better performance within that range. Since the transmission is moving among multiple channels, interference on one channel causes loss on that channel but does not corrupt the entire link. This improves the reliability of the system. Channel Frequencies Channel Number HUM-2.4-RC Frequency (MHz) HUM-900-RC Frequency (MHz) 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 2,420.25 2,422.25 2,424.25 2,426.25 2,428.25 2,430.25 2,432.25 2,434.25 2,436.25 2,438.25 2,440.25 2,442.25 2,444.25 2,446.25 2,448.25 2,450.25 2,452.25 2,454.25 2,456.25 2,458.25 2,460.25 2,462.25 2,464.25 2,466.25 2,468.25 Figure 38: HumRCTM Series Transceiver RF Channel Frequencies 902.750 903.250 903.750 904.250 904.750 905.249 905.749 906.249 906.749 907.249 907.749 908.249 908.749 909.248 909.748 910.248 910.748 911.248 911.748 912.248 912.748 913.247 913.747 914.247 914.747 34 35 The Command Data Interface The HumRCTM Series transceiver has a serial Command Data Interface
(CDI) that offers the option to configure and control the transceiver through software instead of through hardware. This interface consists of a standard UART with a serial command set. This allows for fewer connections in applications controlled by a microcontroller as well as for more control and advanced features than can be offered through hardware pins alone. The CMD_DATA_IN and CMD_DATA_OUT connect to the modules UART. An automatic baud rate detection system allows the interface to run at a variable data rate from 9.0kbps to 60.0kbps, covering standard rates from 9.6 to 57.6kbps. The Command Data Interface has two sets of operators. One is a set of commands that performs specific tasks and the other is a set of parameters that are for module configuration and status reporting. The HumRCTM Series Transceiver Command Data Interface Reference Guide has full details on each command. Some key features available with the serial interface are:
Configure the module through software instead of setting the hardware lines. Change the output power, providing the ability to lower power consumption when signal levels are good and extend battery life. Individually set which status lines are inputs and outputs. Individually set status line outputs to operate as momentary or latched. Add or remove specific paired devices. Individually set Permission Masks that prevent certain paired devices from activating certain status line outputs. Change the modules local address for production or tracking purposes or to replace a lost or broken product. Put the module into a low power state to conserve battery power. Activate an automatic receiver duty cycle to conserve battery power. Receive the entire control message serially instead of needing to monitor individual status lines. Get the IU address for logging access attempts. Receive control messages from unpaired modules, allowing for expansion of the system beyond the maximum of 40 paired units. Access control and address validation can be undertaken by an external processor or PC with more memory than the module. Serially configure and control acknowledge messages. Send and receive 2 bytes (16 bits) of custom data with each command message and acknowledge message. Serially initiate transmission of control messages instead of triggering the status line inputs. Set interrupts to notify an external processor when specific events occur, such as receiving a control message. Read out the RSSI value for the last received packet and the current ambient RF level. Query a remote unit to respond with its analog input voltage measurements. Configure the module to send triggered control messages that automatically stop transmitting based on the settings, conserving battery power. The serial interface offers a great deal of flexibility for use more complicated designs. Please see Reference Guide RG-00104: the HumRCTM Series Command Data Interface for details on the CDI. Lists of the serial commands and parameters are shown in Figure 39 and Figure 40 for reference. 36 37 Serial Setup Configuration for Stand-alone Operation The serial interface offers access to a number of advanced features that cannot be controlled through hardware configuration alone. However, not all products need or use a microcontroller or processor, but would benefit from some of the advanced features. Many of the configuration settings can be written once and then used by the module thereafter. This allows the modules to be configured through a temporary serial connection and then operate in a stand-alone fashion without a permanent serial connection. For example, a product can have a small header or connector so that the serial lines can be connected to a PC in production test. The PC writes the configurations required by the application to the module and is then disconnected. The module uses these configurations in its normal operation. Command Data Interface Commands Command Description Read Write Read NV Program Set Default Configuration Read the current value in volatile memory. If there is no volatile value, then the non-volatile value is returned. Write a new value to volatile memory. Read the value in non-volatile memory. Program a new value to non-volatile memory. Set all configuration items to their factory default values. Erase All Addresses Erase all paired addresses from memory. Transmit Control Data Transmit a control message. Transmit ACK Transmit an acknowledgement for received data. Transmit AWD Transmit an Acknowledge With Data (AWD) response with two bytes of custom data. Transmit IU Packet Transmit a general IU packet. NV Update Pair Control Write all NV changes to NV memory Initiate / Cancel RF Pairing with another module Figure 39: HumRCTM Series Transceiver Command Data Interface Commands Command Data Interface Parameters Parameter Description Device Name NULL-terminated string of up to 16 characters that identifies the module. Read only. Firmware Version 2 byte firmware version. Read only. Serial Number Local Address 4 byte factory-set serial number. Read only. The modules 32-bit local address. Status Line I/O Mask Status lines direction (1 = Inputs, 0 = Outputs), LSB = S0, used when enabled by Control Source. Latch Mask TX Power Level Latching enable for output lines, LSB = S0, used when enabled by Control Source. TX output power, signed nominal dBm, used when enabled by Control Source. Control Source Configures the control options. Message Select Select message types to capture for serial readout. Analog Input Select Define analog sources, averaging, reference, and offset for analog readings. Custom Data Source Source of transmitted custom data. Paired Module Descriptor Sets the address and permissions mask of paired modules. Trigger Operation Input Trigger operation. Receiver Duty Cycle Receiver Duty Cycle control. I/O Lines Read the current state of the status and control lines. Read only. RSSI LADJ Read the RSSI of the last packet received and ambient level. Read only. Read the voltage on the LVL_ADJ line. Read only. Module Status Read the operating status of the module. Read only. Captured Receive Packet Interrupt Mask Read the last received packet. Read only. Sets the mask for events to generate a break on CMD_DATA_ OUT. Event Flags Event flags that are used with the Interrupt Mask. Analog Input Reading Readout of the analog input lines. Read only. Trigger Input Status Status of Trigger Inputs. Read only. Pairing Status Status of Last Pair attempt since power-up. Read only. Figure 40: HumRCTM Series Transceiver Command Data Interface Parameters 38 39 Basic Hardware Operation The following steps describe how to use the HumRCTM Series module with hardware only. Basic application circuits that correspond to these steps are shown in Figure 41. 1. Set the C0 and C1 lines opposite on both sides. 2. Press the PAIR button on both sides. The MODE_IND LED begins flashing slowly to indicate that the module is searching for another module. 3. Once the pairing is complete, the MODE_IND LED flashes quickly to indicate that the pairing was successful. 4. The modules are now paired and ready for normal use. 5. Pressing a status line button on one module (the IU) activates the corresponding status line output on the second module (the RU). 6. Taking the ACK_EN line high on the RU causes the module to send an acknowledgement to the IU. The ACK_OUT line on the IU goes high to indicate that the acknowledgement has been received. Tying the line to Vcc causes the module to send an acknowledgement as soon as a command message is received. This is suitable for basic remote control or command systems. No programming is necessary for basic hardware operation. The Typical Applications section shows additional example schematics for using the modules. The Command Data Interface section describes the more advanced features that are available with the serial interface. VCC VCC VCC GND VCC GND 9 2 8 2 7 2 6 2 5 2 4 2 3 2 2 2 1 2 D N G N E _ A P C C V N E _ A N L T E S E R N E _ K C A I R A P MODE_IND ACK_OUT LVL_ADJ I N _ A T A D _ D M C T U O _ A T A D _ D M C S7 S6 S5 S4 3 S 2 S 1 S 0 S D N G 0 C 1 C N W O D _ R E W O P N E _ H C T A L 5 6 7 8 9 0 1 1 1 2 1 3 1 GND VCC GND VCC GND GND ANT GND GND GND GND GND 20 19 18 17 16 15 14 GND GND GND GND GND GND VCC VCC VCC VCC VCC VCC VCC GND VCC GND 9 2 8 2 7 2 6 2 5 2 4 2 3 2 2 2 1 2 D N G N E _ A P C C V N E _ A N L T E S E R N E _ K C A I R A P MODE_IND ACK_OUT LVL_ADJ I N _ A T A D _ D M C T U O _ A T A D _ D M C S7 S6 S5 S4 3 S 2 S 1 S 0 S D N G 0 C 1 C N W O D _ R E W O P N E _ H C T A L 5 6 7 8 9 0 1 1 1 2 1 3 1 3 S 2 S 1 S 0 S GND GND VCC VCC GND GND ANT GND GND GND GND GND 20 19 18 17 16 15 14 GND GND GND GND GND GND S7 S6 S5 S4 30 31 32 1 2 3 4 30 31 32 1 2 3 4 GND GND VCC GND A B GND GND VCC GND VCC VCC VCC VCC 40 41 Figure 41: HumRCTM Series Transceiver Basic Application Circuits for Bi-directional Remote Control Typical Applications Figure 42 and Figure 43 show circuits using the HumRCTM Series transceiver. VCC VCC VCC VCC VCC GND 9 2 8 2 7 2 6 2 5 2 4 2 3 2 2 2 1 2 GND VCC GND GND VCC GND 30 31 32 1 2 3 4 GND GND VCC GND S7 S6 S5 S4 I R A P MODE_IND ACK_OUT LVL_ADJ S7 S6 S5 S7 S4 S6 3 S S5 S4 30 31 32 1 2 3 2 S 4 N E _ K C A I N _ A T A D _ D M C 9 2 T U O _ A T A D _ D M C I R A P MODE_IND ACK_OUT LVL_ADJ VCC VCC D N G N E _ A P 7 2 8 2 N E _ A N L 6 2 GND T E S E R 5 2 C C V 4 2 D N G N E _ K C A N I _ A T A D _ D M C T U O _ A T A D _ D M C N W O D _ R E W O P N E _ H C T A L D N G 0 S 0 C 1 C S7 S6 S5 1 S S4 3 2 GND N ANT E _ A N GND L N E _ A P GND GND GND GND 5 6 7 8 9 0 1 1 1 2 1 3 1 3 S 2 GND S 1 S 0 GND S VCC VCC GND 0 C 1 C D N G GND 20 19 18 17 16 15 14 GND GND GND GND GND GND 2 2 20 1 2 GND T 19 E S E 18 R 17 16 15 14 N W O D _ R E W O P C C V GND GND GND ANT GND GND GND GND GND GND GND GND N E _ H C T A L RXD TXD GPIO GPIO GPIO RXD TXD GPIO VCC GPIO GPIO GND GND VCC GND VCC VCC VCC VCC GND GND VCC GND VCC VCC VCC VCC VCC GND 9 2 8 2 7 2 6 2 5 2 4 2 3 2 2 2 1 2 30 31 32 1 2 3 4 VCC R A P I MODE_IND ACK_OUT LVL_ADJ S7 S6 S5 S4 3 S N E _ K C A 30 31 32 1 2 3 2 S 4 D N G 8 2 N E _ A P 7 2 N E _ A N L 6 2 T E S E R 9 2 GND C C V 5 2 I N _ A T A D _ D M C T U O _ A T A D _ D M C I R A P MODE_IND ACK_OUT LVL_ADJ S7 S6 N E _ K C A N I _ A T A D _ D M C S5 1 S 0 S D N G 0 C 1 C S4 4 2 3 2 GND N E _ A P GND ANT N E _ A N L GND GND GND GND T U O _ A T A D _ D M C N W O D _ R E W O P D N G N E _ H C T A L 5 6 7 8 9 0 1 1 1 2 1 3 S 2 S 1 S 0 S 3 GND S 2 GND VCC S 1 S 0 S 3 1 D N G GND 0 C 1 C GND VCC 1 2 GND C C V GND GND GND ANT GND GND GND GND GND GND GND GND N E _ H C T A L 2 2 20 T 19 E S E 18 R 17 16 15 14 N W O D _ R E W O P GND 20 19 18 17 16 15 14 GND GND GND GND GND GND 5 6 7 8 9 0 1 1 1 2 1 3 1 3 S 2 S 1 S 0 S GND GND VCC GND Figure 43: HumRCTM Series Transceiver Typical Application Circuit with External Microprocessor In this example, C0 is low and C1 is high, so S0S3 are outputs and S4S7 are inputs. This is inverted from the circuit in Figure 42 making it the matching device. In this circuit, the Command Data Interface is connected to a microcontroller for using some of the advanced features. The microcontroller controls the state of the ACK_EN line. It can receive a command, perform an action and then take the line high to send Acknowledgement packets. This lets the user on the other end know that the action took place and not just that the command was received. 5 6 7 8 9 0 1 1 1 2 1 3 1 GND VCC GND VCC GND VCC VCC VCC VCC VCC VCC VCC VCC Figure 42: HumRCTM Series Transceiver Basic Application Circuit In this example, C0 is high and C1 is low, so S0S3 are inputs and S4S7 are outputs. The inputs are connected to buttons that pull the lines high and weak pull-down resistors to keep the lines from floating when the buttons are not pressed. The outputs would be connected to external application circuitry. LATCH_EN is low, so the outputs are momentary. The Command Data Interface is not used in this design, so CMD_DATA_IN is tied high and CMD_DATA_OUT is not connected. ACK_OUT and MODE_IND are connected to LEDs to provide visual indication to the user. PAIR is connected to a button and pull-down resistor to initiate the Pair Process when the button is pressed. ACK_EN is tied high so the module sends acknowledgements as soon as it receives a control message. 42 43 Usage Guidelines for FCC and IC Compliance The pre-certified versions of the HumRCTM Series module
(HUM-900-RC-UFL and HUM-900-RC-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. The integrator does not need to conduct any further testing under these rules provided that the following guidelines are met:
An approved antenna must be directly coupled to the modules U.FL connector through an approved coaxial extension cable or to the modules castellation pad using an approved reference design and PCB layer stack. Alternate antennas can be used, but may require the integrator to perform certification testing. The module must not be modified in any way. Coupling of external circuitry must not bypass the provided connectors. End product must be externally labeled with Contains FCC ID:
OJM900MCA / IC: 5840A-900MCA. The end products users manual must contain an FCC statement equivalent to that listed on page page 45 of this data guide. The antenna used for this transceiver must not be co-located or operating in conjunction with any other antenna or transmitter. The integrator must not provide any information to the end-user on how to install or remove the module from the end-product. Any changes or modifications not expressly approved by Linx Technologies could void the users authority to operate the equipment. Additional Testing Requirements The HUM-900-RC-UFL and HUM-900-RC-CAS modules have been tested for compliance as an intentional radiator, but the integrator is required to perform unintentional radiator testing on the final product per FCC sections 15.107 and 15.109 and Industry Canada license-exempt RSS standards. Additional product-specific testing might be required. Please contact the FCC or Industry Canada regarding regulatory requirements for the application. Ultimately is it the integrators responsibility to show that their product complies with the regulations applicable to their product. Versions other than the -UFL and -CAS have not been tested and require full compliance testing in the end product as it will go to market. Information to the user The following information must be included in the products user manual. FCC / IC NOTICES This product contains FCC ID: OJM900MCA / IC: 5840A-900MCA. This device complies with Part 15 of the FCC rules and Industry Canada license-exempt RSS standards. Operation of this device is subject to the following two conditions:
1. This device may not cause harmful interference, and 2. this device must accept any interference received, including interference that may cause undesired operation. This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses and can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio communications. However, there is no guarantee that interference will not occur in a particular installation. If this equipment does cause harmful interference to radio or television reception, which can be determined by turning the equipment off and on, the user is encouraged to try to correct the interference by one or more of the following measures:
Reorient or relocate the receiving antenna. Connect the equipment into an outlet on a circuit different from that to which Increase the separation between the equipment and receiver. the receiver is connected. Consult the dealer or an experienced radio/TV technician for help. Any modifications could void the users authority to operate the equipment. Le prsent appareil est conforme aux CNR dIndustrie Canada applicables aux appareils radio exempts de licence. Lexploitation est autorise aux deux conditions suivantes:
1. 2. lappareil ne doit pas produire de brouillage, et utilisateur de lappareil doit accepter tout brouillage radiolectrique subi, mme si le brouillage est susceptible den compromettre le fonctionnement. 44 45 Product Labeling The end product containing the HUM-900-RC-UFL or HUM-900-RC-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. Permanently affixed means that the label is etched, engraved, stamped, silkscreened, indelibly printed, or otherwise permanently marked on a permanently attached part of the equipment or on a nameplate of metal, plastic, or other material fastened to the equipment by welding, riveting, or a permanent adhesive. The label must be designed to last the expected lifetime of the equipment in the environment in which the equipment may be operated and must not be readily detachable. FCC RF Exposure Statement To satisfy RF exposure requirements, this device and its antenna must operate with a separation distance of at least 20cm from all persons and must not be co-located or operating in conjunction with any other antenna or transmitter. Antenna Selection Under FCC and Industry Canada regulations, the HUM-900-RC-UFL and HUM-900-RC-CAS radio transmitters may only operate using an antenna of a type and maximum (or lesser) gain approved for the transmitter by the FCC and Industry Canada. To reduce potential radio interference to other users, the antenna type and its gain should be so chosen that the equivalent isotropically radiated power (e.i.r.p.) is not more than that necessary for successful communication. The HUM-900-RC-UFL and HUM-900-RC-CAS radio transmitters have been approved by the FCC and Industry Canada to operate with the antenna types listed in Figure 44 with the maximum permissible gain and required antenna impedance for each antenna type indicated. Antenna types not included in this list, having a gain greater than the maximum gain indicated for that type, are strictly prohibited for use with this device. Conformment la rglementation dIndustrie Canada, le prsent metteur radio peut fonctionner avec une antenne dun type et dun gain maximal
(ou infrieur) approuv pour lmetteur par Industrie Canada. Dans le but de rduire les risques de brouillage radiolectrique lintention des autres utilisateurs, il faut choisir le type dantenne et son gain de sorte que la puissance isotrope rayonne quivalente (p.i.r.e.) ne dpasse pas lintensit ncessaire ltablissement dune communication satisfaisante. Le prsent metteur radio (HUM-900-RC-UFL, HUM-900-RC-CAS) a t approuv par Industrie Canada pour fonctionner avec les types dantenne numrs la Figure 44 et ayant un gain admissible maximal et limpdance requise pour chaque type dantenne. Les types dantenne non inclus dans cette liste, ou dont le gain est suprieur au gain maximal indiqu, sont strictement interdits pour lexploitation de lmetteur. Antennas / Antennes Linx Part Number Rfrence Linx Tested Antennas Type Gain Impedance Impdance Valid For ANT-916-CW-QW Wave Whip ANT-916-CW-HW Wave Dipole Helical ANT-916-PW-LP Wave Whip ANT-916-PW-QW-UFL Wave Whip ANT-916-SP Wave Planar 1.8dBi 1.2dBi 2.4dBi 1.8dBi 1.4dBi ANT-916-WRT-RPS ANT-916-WRT-UFL Wave Dipole Helical 0.1dBi Antennas of the same type and same or lesser gain ANT-916-CW-HD ANT-916-PW-QW ANT-916-CW-RCL ANT-916-CW-RH Wave Whip Wave Whip Wave Whip Wave Whip 0.3dBi 1.8dBi 2.0dBi 1.3dBi ANT-916-CW-HWR-RPS Wave Dipole Helical 1.2dBi ANT-916-PML Wave Dipole Helical 0.4dBi ANT-916-PW-RA Wave Whip ANT-916-USP Cable Assemblies / Assemblages de Cbles Wave Planar 0.0dBi 0.3dBi 50 50 50 50 50 50 50 50 50 50 50 50 50 50 CAS Both CAS UFL CAS CAS UFL Both Both Both Both Both Both CAS CAS Linx Part Number Rfrence Linx Description CSI-RSFB-300-UFFR*
RP-SMA Bulkhead to U.FL with 300mm cable CSI-RSFE-300-UFFR*
RP-SMA External Mount Bulkhead to U.FL with 300mm cable
* Also available in 100mm and 200mm cable length Figure 44: HumRCTM Series Transceiver Approved Antennas 46 47 Castellation Version Reference Design The castellation connection for the antenna on the pre-certified version allows the use of embedded antennas as well as removes the cost of a cable assembly for the u.FL connector. However, the PCB design and layer stack must follow one of the reference designs for the certification on the HUM-900-RC-CAS to be valid. Figure 45 shows the PCB layer stack that should be used. Figure 46 shows the layout and routing designs for the different antenna options. Please see the antenna data sheets for specific ground plane counterpoise requirements. Layer Name Top Layer Dielectric 1 Mid-Layer 1 Thickness Material Copper 1.4mil FR-4 (Er = 4.6) 14.00mil Copper 1.4mil Dielectric 2 28.00mil FR-4 (Er = 4.6) Mid-Layer 2 Dielectric 3 Bottom Layer 1.4mil 14.00mil 1.4mil Copper FR-4 (Er = 4.6) Copper Figure 45: HumRCTM Series Transceiver Castellation Version Reference Design PCB Stack Note: The PCB design and layer stack for the HUM-900-RC-CAS must follow these reference designs for the pre-certification to be valid. The HUM-900-RC-UFL and the HUM-900-RC-CAS must use one of the antennas in Figure 44 in order for the certification to be valid. The HUM-900-RC and HUM-2.4-RC have not been tested and require full compliance testing in the end product as it will go to market. All modules require unintentional radiator compliance testing in the end product as it will go to market. 1 6 3 5 3 5 3 2 7
. 2 6 0 3 0 0 A M S V E R N O C 0 2 3 9 1 6 0 0 2 5 6 1 5 6 1 0 7 4 0 3 2 0 4 1 0 3 2 P L
-
W P
-
6 1 9
-
T N A
-
A R W P
-
6 1 9
-
T N A 6 1 2 0 8 3 P S
-
6 1 9
-
T N A S P R
-
T R W
-
6 1 9
-
T N A
-
W Q W C
-
6 1 9
-
T N A
-
W H W C
-
6 1 9
-
T N A 1 l i i t m 4 2
=
h d W p i r t s o r c M i r e y a L
-
d M n o i e n a p l d n u o r G s l i m n i e r a s t i n U 48 49 Figure 46: HumRCTM Series Transceiver Castellation Version Reference Design Power Supply Requirements 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 modules performance, so providing a clean power supply for the module should be a high priority during design. 10 Vcc IN Vcc TO MODULE
+
10F Figure 47: Supply Filter A 10 resistor in series with the supply followed by a 10F tantalum capacitor from Vcc to ground helps in cases where the quality of supply power is poor (Figure 47). This filter should be placed close to the modules supply lines. These values may need to be adjusted depending on the noise present on the supply line. Antenna Considerations The choice of antennas is a critical and often overlooked design consideration. The range, performance and legality of an RF link are critically dependent upon the antenna. While adequate antenna performance can often be obtained by trial and error methods, antenna design and matching is a complex task. Professionally designed antennas such as those from Linx (Figure 48) help ensure maximum performance and FCC and other regulatory compliance. Please see General Antenna Rules for more information. Figure 48: Linx Antennas It is usually best to utilize a basic quarter-wave whip until your prototype product is operating satisfactorily. Other antennas can then be evaluated based on the cost, size and cosmetic requirements of the product. Additional details are in Application Note AN-00500. Interference Considerations The RF spectrum is crowded and the potential for conflict with unwanted sources of RF is very real. While all RF products are at risk from interference, its effects can be minimized by better understanding its characteristics. Interference may come from internal or external sources. The first step is to eliminate interference from noise sources on the board. This means paying careful attention to layout, grounding, filtering and bypassing in order to eliminate all radiated and conducted interference paths. For many products, this is straightforward; however, products containing components such as switching power supplies, motors, crystals and other potential sources of noise must be approached with care. Comparing your own design with a Linx evaluation board can help to determine if and at what level design-specific interference is present. External interference can manifest itself in a variety of ways. Low-level interference produces noise and hashing on the output and reduces the links overall range. High-level interference is caused by nearby products sharing the same frequency or from near-band high-power devices. It can even come from your own products if more than one transmitter is active in the same area. It is important to remember that only one transmitter at a time can occupy a frequency, regardless of the coding of the transmitted signal. This type of interference is less common than those mentioned previously, but in severe cases it can prevent all useful function of the affected device. Although technically not interference, multipath is also a factor to be understood. Multipath is a term used to refer to the signal cancellation effects that occur when RF waves arrive at the receiver in different phase relationships. This effect is a particularly significant factor in interior environments where objects provide many different signal reflection paths. Multipath cancellation results in lowered signal levels at the receiver and shorter useful distances for the link. 50 51 Pad Layout The pad layout diagrams below are designed to facilitate both hand and automated assembly. Figure 49 shows the footprint for the smaller version and Figure 50 shows the footprint for the pre-certified version. 0.520"
0.015"
0.420"
0.015"
0.028"
0.050"
0.070"
Figure 49: HUM-***-RC Recommended PCB Layout 0.015"
0.060"
0.100"
0.101"
0.136"
0.090"
0.015"
0.028"
0.065"
0.060"
0.420"
0.015"
0.050"
0.070"
Figure 50: HUM-***-RC-UFL/CAS Recommended PCB Layout Microstrip Details 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 modules antenna can effectively contribute to the length of the antenna, changing its resonant bandwidth. In order to minimize loss and detuning, some form of transmission line between the antenna and the module should be used unless the antenna can be placed very close (<18in) to the module. One common form of transmission line is a coax cable and another is the microstrip. This term refers to a PCB trace running over a ground plane that is designed to serve as a transmission line between the module and the antenna. The width is based on the desired characteristic impedance of the line, the thickness of the PCB and the dielectric constant of the board material. For standard 0.062in thick FR-4 board material, the trace width would be 111 mils. The correct trace width can be calculated for other widths and materials using the information in Figure 51 and examples are provided in Figure 52. Software for calculating microstrip lines is also available on the Linx website. Trace Board Ground plane Figure 51: Microstrip Formulas Example Microstrip Calculations Dielectric Constant Width / Height Ratio (W / d) Effective Dielectric Constant Characteristic Impedance () 4.80 4.00 2.55 1.8 2.0 3.0 3.59 3.07 2.12 50.0 51.0 48.8 52 Figure 52: Example Microstrip Calculations 53 Board Layout Guidelines The modules 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 modules 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 following section provides some basic design guidelines. During prototyping, the module should be soldered to a properly laid-out circuit board. The use of prototyping or perf boards results in poor performance and is strongly discouraged. Likewise, the use of sockets can have a negative impact on the performance of the module and is discouraged. The module should, as much as reasonably possible, be isolated from other components on your PCB, especially high-frequency circuitry such as crystal oscillators, switching power supplies, and high-speed bus lines. When possible, separate RF and digital circuits into different PCB regions. Make sure internal wiring is routed away from the module and antenna and is secured to prevent displacement. Do not route PCB traces directly under the module. There should not be any copper or traces under the module on the same layer as the module, just bare PCB. The underside of the module has traces and vias that could short or couple to traces on the products circuit board. The Pad Layout section shows a typical PCB footprint for the module. A ground plane (as large and uninterrupted as possible) should be placed on a lower layer of your PC board opposite the module. This plane is essential for creating a low impedance return for ground and consistent stripline performance. Use care in routing the RF trace between the module and the antenna or connector. Keep the trace as short as possible. Do not pass it under the module or any other component. Do not route the antenna trace on multiple PCB layers as vias add inductance. Vias are acceptable for tying together ground layers and component grounds and should be used in multiples. The -CAS version must follow the layout in Figure 46. Each of the modules ground pins should have short traces tying immediately to the ground plane through a via. Bypass caps should be low ESR ceramic types and located directly adjacent to the pin they are serving. A 50-ohm coax should be used for connection to an external antenna. A 50-ohm transmission line, such as a microstrip, stripline or coplanar waveguide should be used for routing RF on the PCB. The Microstrip Details section provides additional information. In some instances, a designer may wish to encapsulate or pot the product. There are a wide variety of potting compounds with varying dielectric properties. Since such compounds can considerably impact RF performance and the ability to rework or service the product, it is the responsibility of the designer to evaluate and qualify the impact and suitability of such materials. Helpful Application Notes from Linx It is not the intention of this manual to address in depth many of the issues that should be considered to ensure that the modules function correctly and deliver the maximum possible performance. We recommend reading the application notes listed in Figure 53 which address in depth key areas of RF design and application of Linx products. These applications notes are available online at www.linxtechnologies.com or by contacting the Linx literature department. Helpful Application Note Titles Note Number Note Title AN-00100 AN-00126 AN-00130 AN-00140 AN-00500 AN-00501 RG-00104 RF 101: Information for the RF Challenged Considerations for Operation Within the 902928MHz Band Modulation Techniques for Low-Cost RF Data Links The FCC Road: Part 15 from Concept to Approval Antennas: Design, Application, Performance Understanding Antenna Specifications and Operation RC Series Transceiver Command Data Interface Reference Guide Figure 53: Helpful Application Note Titles 54 55 Production Guidelines 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. Soldering Iron Tip Hand Assembly Pads located on the bottom of the module are the primary mounting surface (Figure 54). Since these pads are inaccessible during mounting, castellations that run up the side of the module have been provided to facilitate solder wicking to the modules underside. This allows for very quick hand soldering for prototyping and small volume production. If the recommended pad guidelines have been followed, the pads will protrude slightly past the edge of the module. Use a fine soldering tip to heat the board pad and the castellation, then introduce solder to the pad at the modules edge. The solder will wick underneath the module, providing reliable attachment. Tack one module corner first and then work around the device, taking care not to exceed the times in Figure 55. Solder PCB Pads Castellations Figure 54: Soldering Technique Warning: Pay attention to the absolute maximum solder times. Absolute Maximum Solder Times Hand Solder Temperature: +427C for 10 seconds for lead-free alloys Reflow Oven: +255C max (see Figure 56) Figure 55: Absolute Maximum Solder Times Automated Assembly For high-volume assembly, the modules are generally auto-placed. The modules have been designed to maintain compatibility with reflow processing techniques; however, due to their hybrid nature, certain aspects of the assembly process are far more critical than for other component types. Following are brief discussions of the three primary areas where caution must be observed. Reflow Temperature Profile The single most critical stage in the automated assembly process is the reflow stage. The reflow profile in Figure 56 should not be exceeded because excessive temperatures or transport times during reflow will irreparably damage the modules. Assembly personnel need to pay careful attention to the ovens profile to ensure that it meets the requirements necessary to successfully reflow all components while still remaining within the limits mandated by the modules. The figure below shows the recommended reflow oven profile for the modules. Recommended RoHS Profile Max RoHS Profile Recommended Non-RoHS Profile 255C 235C 217C 185C 180C 125C 300 250 200 150 100 50
) C o
(
t e r u a r e p m e T 0 30 60 90 120 150 180 210 240 270 300 330 360 Time (Seconds) Figure 56: Maximum Reflow Temperature Profile Shock During Reflow Transport Since some internal module components may reflow along with the components placed on the board being assembled, it is imperative that the modules not be subjected to shock or vibration during the time solder is liquid. Should a shock be applied, some internal components could be lifted from their pads, causing the module to not function properly. Washability The modules are wash-resistant, but are not hermetically sealed. Linx recommends wash-free manufacturing; however, the modules can be subjected to a wash cycle provided that a drying time is allowed prior to applying electrical power to the modules. The drying time should be sufficient to allow any moisture that may have migrated into the module to evaporate, thus eliminating the potential for shorting damage during power-up or testing. If the wash contains contaminants, the performance may be adversely affected, even after drying. 56 57 General Antenna Rules The following general rules should help in maximizing antenna performance. 1. Proximity to objects such as a users 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 57). In many cases, this isnt desirable for practical or ergonomic reasons, thus, an alternative antenna style such as a helical, loop or patch may be utilized and the corresponding sacrifice in performance accepted. plane as possible in proximity to the base of the antenna. In cases where the antenna is remotely located or the antenna is not in close proximity to a circuit board, ground plane or grounded metal case, a metal plate may be used to maximize the antennas performance. 5. Remove the antenna as far as possible from potential interference sources. Any frequency of sufficient amplitude to enter the receivers front end will reduce system range and can even prevent reception entirely. Switching power supplies, oscillators or even relays can also be significant sources of potential interference. The single best weapon against such problems is attention to placement and layout. Filter the modules power supply with a high-frequency bypass capacitor. Place adequate ground plane under potential sources of noise to shunt noise to ground and prevent it from coupling to the RF stage. Shield noisy board areas whenever practical. 3. 4. OPTIMUM USABLE NOT RECOMMENDED Figure 57: Ground Plane Orientation 6. CASE If an internal antenna is to be used, keep it away from other metal components, particularly large items like transformers, batteries, PCB tracks and ground planes. In many cases, the space around the antenna is as important as the antenna itself. Objects in close proximity to the antenna can cause direct detuning, while those farther away will alter the antennas symmetry. GROUND PLANE
(MAY BE NEEDED) NUT ANTENNA (MARCONI) VERTICAL /4 GROUNDED In many antenna designs, particularly -wave whips, the ground plane acts as a counterpoise, forming, in essence, a -wave dipole (Figure 58). For this reason, adequate ground plane area is essential. The ground plane can be a metal case or ground-fill areas on a circuit board. Ideally, it should have a surface area less than or equal to the overall length of the -wave radiating element. This is often not practical due to size and configuration constraints. In these instances, a designer must make the best use of the area available to create as much ground GROUND PLANE VIRTUAL /4 DIPOLE DIPOLE ELEMENT
/4
/4 E I In some applications, it is advantageous to place the module and antenna away from the main equipment (Figure 59). This can avoid interference problems and allows the antenna to be oriented for optimum performance. Always use 50 coax, like RG-174, for the remote feed. NOT RECOMMENDED OPTIMUM USABLE CASE GROUND PLANE
(MAY BE NEEDED) NUT Figure 59: Remote Ground Plane Figure 58: Dipole Antenna 58 59 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 60) provides outstanding overall performance and stability. A low-cost whip can be easily fabricated from a wire or rod, but most designers opt for the consistent performance and cosmetic appeal of a professionally-made model. To meet this need, Linx offers a wide variety of straight and reduced height whip style antennas in permanent and connectorized mounting styles. Figure 60: Whip Style Antennas L =
234 FMHz The wavelength of the operational frequency determines an antennas overall length. Since a full wavelength is often quite long, a partial - or -wave antenna is normally employed. Its size and natural radiation resistance make it well matched to Linx modules. The proper length for a straight -wave can be easily determined using the formula in Figure 61. It is also possible to reduce the overall height of the antenna by using a helical winding. This reduces the antennas bandwidth but is a great way to minimize the antennas physical size for compact applications. This also means that the physical appearance is not always an indicator of the antennas frequency. Figure 61:
L = length in feet of quarter-wave length F = operating frequency in megahertz Loop Style A loop or trace style antenna is normally printed directly on a products PCB (Figure 63). This makes it the most cost-effective of antenna styles. The element can be made self-resonant or externally resonated with discrete components, but its actual layout is usually product specific. Despite the cost advantages, loop style antennas are generally inefficient and useful only for short range applications. They are also very sensitive to changes in layout and PCB dielectric, which can cause consistency issues during production. In addition, printed styles are difficult to engineer, requiring the use of expensive equipment including a network analyzer. An improperly designed loop will have a high VSWR at the desired frequency which can cause instability in the RF stage. Figure 63: Loop or Trace Antenna Linx offers low-cost planar (Figure 64) and chip antennas that mount directly to a products PCB. These tiny antennas do not require testing and provide excellent performance despite their small size. They offer a preferable alternative to the often problematic printed antenna. Figure 64: SP Series Splatch and uSP MicroSplatch Antennas Specialty Styles Linx offers a wide variety of specialized antenna styles (Figure 62). Many of these styles utilize helical elements to reduce the overall antenna size while maintaining reasonable performance. A helical antennas bandwidth is often quite narrow and the antenna can detune in proximity to other objects, so care must be exercised in layout and placement. Figure 62: Specialty Style Antennas 60 61 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. When working with RF, a clear distinction must be made between what is technically possible and what is legally acceptable in the country where operation is intended. Many manufacturers have avoided incorporating RF into their products as a result of uncertainty and even fear of the approval and certification process. Here at Linx, our desire is not only to expedite the design process, but also to assist you in achieving a clear idea of what is involved in obtaining the necessary approvals to legally market a completed product. For information about regulatory approval, read AN-00142 on the Linx website or call Linx. Linx designs products with worldwide regulatory approval in mind. In the United States, the approval process is actually quite straightforward. The regulations governing RF devices and the enforcement of them are the responsibility of the Federal Communications Commission (FCC). The regulations are contained in Title 47 of the United States Code of Federal Regulations (CFR). Title 47 is made up of numerous volumes; however, all regulations applicable to this module are contained in Volume 0-19. It is strongly recommended that a copy be obtained from the FCCs website, the Government Printing Office in Washington or from your local government bookstore. Excerpts of applicable sections are included with Linx evaluation kits or may be obtained from the Linx Technologies website, www.linxtechnologies.com. In brief, these rules require that any device that intentionally radiates RF energy be approved, that is, tested for compliance and issued a unique identification number. This is a relatively painless process. Final compliance testing is performed by one of the many independent testing laboratories across the country. Many labs can also provide other certifications that the product may require at the same time, such as UL, CLASS A / B, etc. Once the completed product has passed, an ID number is issued that is to be clearly placed on each product manufactured. Questions regarding interpretations of the Part 2 and Part 15 rules or the measurement procedures used to test intentional radiators such as Linx RF modules for compliance with the technical standards of Part 15 should be addressed to:
Federal Communications Commission Equipment Authorization Division Customer Service Branch, MS 1300F2 7435 Oakland Mills Road Columbia, MD, US 21046 Phone: + 1 301 725 585 | Fax: + 1 301 344 2050 Email: labinfo@fcc.gov ETSI Secretaria 650, Route des Lucioles 06921 Sophia-Antipolis Cedex FRANCE Phone: +33 (0)4 92 94 42 00 Fax: +33 (0)4 93 65 47 16 International approvals are slightly more complex, although Linx modules are designed to allow all international standards to be met. If the end product is to be exported to other countries, contact Linx to determine the specific suitability of the module to the application. All Linx modules are designed with the approval process in mind and thus much of the frustration that is typically experienced with a discrete design is eliminated. Approval is still dependent on many factors, such as the choice of antennas, correct use of the frequency selected and physical packaging. While some extra cost and design effort are required to address these issues, the additional usefulness and profitability added to a product by RF makes the effort more than worthwhile. 62 63 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. Values may vary from lot-to-lot and are not guaranteed. Typical parameters can and do vary over lots and application. Linx Technologies makes no guarantee, warranty, or representation regarding the suitability of any product for use in any specific application. It is the customers responsibility to verify the suitability of the part for the intended application. NO LINX PRODUCT IS INTENDED FOR USE IN ANY APPLICATION WHERE THE SAFETY OF LIFE OR PROPERTY IS AT RISK. Linx Technologies DISCLAIMS ALL WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL LINX TECHNOLOGIES BE LIABLE FOR ANY OF CUSTOMERS INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING IN ANY WAY FROM ANY DEFECTIVE OR NON-CONFORMING PRODUCTS OR FOR ANY OTHER BREACH OF CONTRACT BY LINX TECHNOLOGIES. The limitations on Linx Technologies liability are applicable to any and all claims or theories of recovery asserted by Customer, including, without limitation, breach of contract, breach of warranty, strict liability, or negligence. Customer assumes all liability
(including, without limitation, liability for injury to person or property, economic loss, or business interruption) for all claims, including claims from third parties, arising from the use of the Products. The Customer will indemnify, defend, protect, and hold harmless Linx Technologies and its officers, employees, subsidiaries, affiliates, distributors, and representatives from and against all claims, damages, actions, suits, proceedings, demands, assessments, adjustments, costs, and expenses incurred by Linx Technologies as a result of or arising from any Products sold by Linx Technologies to Customer. Under no conditions will Linx Technologies be responsible for losses arising from the use or failure of the device in any application, other than the repair, replacement, or refund limited to the original product purchase price. Devices described in this publication may contain proprietary, patented, or copyrighted techniques, components, or materials. Under no circumstances shall any user be conveyed any license or right to the use or ownership of such items. 2015 Linx Technologies. All rights reserved. The stylized Linx logo, Wireless Made Simple, WiSE, CipherLinx and the stylized CL logo are trademarks of Linx Technologies.
| 1 2 | User Manual - PRC | Users Manual | 2.29 MiB |
HumPRCTM 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. No OEM Linx Remote Control or Function Module should be modified for Life and Property Safety Situations. Such modification cannot provide sufficient safety and will void the products regulatory certification and warranty. Customers may use our (non-Function) Modules, Antenna and Connectors as part of other systems in Life Safety Situations, but only with necessary and industry appropriate redundancies and in compliance with applicable safety standards, including without limitation, ANSI and NFPA standards. It is solely the responsibility of any Linx customer who uses one or more of these products to incorporate appropriate redundancies and safety standards for the Life and Property Safety Situation application. Do not use this or any Linx product to trigger an action directly from the data line or RSSI lines without a protocol or encoder/
decoder to validate the data. Without validation, any signal from another unrelated transmitter in the environment received by the module could inadvertently trigger the action. All RF products are susceptible to RF interference that can prevent communication. RF products without frequency agility or hopping implemented are more subject to interference. This module does have a frequency hopping protocol built in, but the developer should still be aware of the risk of interference. Do not use any Linx product over the limits in this data guide. Excessive voltage or extended operation at the maximum voltage could cause product failure. Exceeding the reflow temperature profile could cause product failure which is not immediately evident. Do not make any physical or electrical modifications to any Linx product. This will void the warranty and regulatory and UL certifications and may cause product failure which is not immediately evident. Table of Contents 1 Description 1 Features 2 Ordering Information 2 Absolute Maximum Ratings 3 Electrical Specifications 5 Typical Performance Graphs 10 Pin Assignments 11 Pin Descriptions 13 Module Dimensions 14 Theory of Operation 15 Module Description 16 Transceiver Operation 17 Transmit Operation 17 Receive Operation 18 System Operation 19 Reading the Transmitter Address 20 Frequency Hopping Spread Spectrum 21 Addressing Modes 22 AES Encryption 23 The Join Process 26 Operation with the HumPROTM Series 27 Carrier Sense Multiple Access (CSMA) 28 Acknowledgement 28 External Amplifier Control 29 Configuring the Status Lines 29 Using the LATCH_EN Line 30 Using the MODE_IND Line 31 Using the PB Line 32 Restore Factory Defaults 32 Using the Low Power Features 34 The Command Data Interface 35 Reading from Registers 36 Writing to Registers 37 Command Length Optimization 38 Example Code for Encoding Read/Write Commands 40 The Command Data Interface Command Set 78 Typical Applications 82 HumPRCTM Series Long-Range Handheld Transmitter 84 Usage Guidelines for FCC Compliance 84 Additional Testing Requirements 85 Information to the User 86 Product Labeling 86 FCC RF Exposure Statement 86 Antenna Selection 88 Castellation Version Reference Design 90 Power Supply Requirements 90 Antenna Considerations 91 Interference Considerations 92 Pad Layout 93 Microstrip Details 94 Board Layout Guidelines 95 Helpful Application Notes from Linx 96 Production Guidelines 96 Hand Assembly 96 Automated Assembly 98 General Antenna Rules 100 Common Antenna Styles 102 Regulatory Considerations HumPRCTM Series 900MHz Remote Control RF Transceiver Module Data Guide Description The HumPRCTM Series is the most complete system to integrate bi-directional remote control into many different applications. No programming is required, and both module and finished hardware options are available, making it the easiest solution to implement. Figure 1: Packages The module provides long-range transmission at 900MHz utilizing frequency hopping and industry-standard encryption for secure and robust communications. The HumPRCTM Series interoperates with Linxs HumPROTM family, making it the only remote control solution that simultaneously supports data applications for seamless integration with sensor and control IoT applications. Eight status lines can be set up in any combination of inputs and outputs for the transfer of button or contact states. A selectable acknowledgement indicates that the transmission was successfully received. Primary settings are hardware-selectable, which eliminates the need for an external microcontroller or other digital interface. For advanced features, optional software configuration is provided by a UART interface. Housed in a compact reflow-compatible SMD package, the transceiver requires no external RF components except an antenna, which greatly simplifies integration and lowers development and assembly costs. Features Add Bi-directional remote control capabilities to any product Pre-compiled software No programming required 128-bit AES encryption 8 status lines FHSS Algorithm Selectable acknowledgements FCC and IC Pre-certified versions Fully interoperable with all HumPROTM Series devices &
gateways 1 Revised 8/15/2019 Ordering Information Ordering Information Part Number Description HUM-900-PRC 900MHz HumPRC Series Remote Control Transceiver, Castellation Interface, External Antenna Connection HUM-900-PRC-CAS HUM-900-PRC-UFL 900MHz HumPRC Series Remote Control Transceiver, Castellation Interface, External Antenna Connection, FCC & IC Certified 900MHz HumPRC Series Remote Control Transceiver, Castellation Interface, U.FL / MHF Compatible Connector, FCC &
IC Certified EVM-900-PRC-CAS 900MHz HumPRC Series Carrier Board, Through-Hole Pin Interface, RP-SMA Connector, FCC & IC Certified EVM-900-PRC-UFL 900MHz HumPRC Series Carrier Board, Through-Hole Pin Interface, U.FL / MHF Compatible Connector, FCC & IC Certified MDEV-900-PRC 900MHz HumPRC Series Master Development System Figure 2: Ordering Information Absolute Maximum Ratings Absolute Maximum Ratings Supply Voltage Vcc Any Input or Output Pin RF Input Operating Temperature Storage Temperature 0.3 0.3 40 40 to to 0 to to
+3.9 VCC + 0.3
+85
+85 VDC VDC dBm C C Exceeding any of the limits of this section may lead to permanent damage to the device. Furthermore, extended operation at these maximum ratings may reduce the life of this device. Figure 3: Absolute Maximum Ratings Warning: This product incorporates numerous static-sensitive components. Always wear an ESD wrist strap and observe proper ESD handling procedures when working with this device. Failure to observe this precaution may result in module damage or failure. Electrical Specifications HumPRCTM Series Transceiver Specifications Parameter Power Supply Operating Voltage TX Supply Current 900MHz at +10dBm 900MHz at 0dBm RX Supply Current Power-Down Current RF Section Operating Frequency Band Number of hop channels
@ 19.2kbps RF Rate
@ 152.34kbps RF Rate Channel spacing
@ 19.2kbps RF Rate
@ 152.34kbps RF Rate 20 dB OBW
@ 19.2kbps RF Rate
@ 152.34kbps RF Rate Receiver BW
@ 19.2kbps RF Rate
@ 152.34kbps RF Rate FSK deviation
@ 19.2kbps RF Rate
@ 152.34kbps RF Rate Scan time / channel (avg)
@ 19.2kbps RF Rate
@ 152.34kbps RF Rate FHSS Lock time
@ 19.2kbps RF Rate
@ 152.34kbps RF Rate Modulation Data Encoding Number of Hop Sequences Symbol Min. Typ. Max. Units Notes VCC lCCTX lCCRX lPDN FC 2.0 3.6 VDC 40.5 22 23.5 0.7 41.5 24 24.5 1.4 mA mA mA A 1,2 1,2 1,2,3 1,2 902 928 MHz 50/64 26/32 375.9 751.81 64 315 102 232 19.2 51 1.2 0.335 63 26 2FSK 6/7 RLL 6 kHz kHz kHz kHz kHz kHz kHz kHz ms ms ms ms 2 3 HumPRCTM Series Transceiver Specifications HumPRCTM Series Transceiver Specifications Parameter Receiver Section Spurious Emissions IF Frequency Receiver Sensitivity
@min rate
@max rate RSSI Dynamic Range CSMA RSSI Threshold Transmitter Section Max Output Power Harmonic Emissions Output Power Range Antenna Port RF Impedance Environmental Operating Temp. Range Timing Module Turn-On Time Via VCC Via POWER_DOWN Via Standby Serial Command Response Volatile R/W NV Update Factory Reset Channel Dwell Time Interface Section UART Data rate Input Logic Low Logic High Symbol Min. Typ. Max. Units Notes PO PH RIN 304.7 101 94 85 70
+9.5 41 50 35 4 0.4 2.4 98 91
+8.5 5 40 63 204 47 9
+85 173 5 50 329 400 dBm kHz dBm dBm dB dBm dBm dBc dB C ms ms ms ms ms ms ms 5 5 5 6 6 6 4 4 4 4 4 8 8 13 9,600 115,200 bps VIL VIH 0.7*VCC 0.3*VCC VDC VDC Parameter Output Logic Low, MODE_IND, ACK_OUT Logic High, MODE_IND, ACK_OUT Logic Low Logic High Symbol Min. Typ. Max. Units Notes VOLM 0.3*VCC VDC 1,9 VOHM 0.7*VCC VOL VOH 0.7*VCC 0.3*VCC VDC 1,9 1,10 1,10 11 cycles 2,000 9. 60mA source/sink 10. 6mA source/sink 11. Number of non-volatile memory refresh cycles. The number of write operations per refresh cycle varies from 8 to 150. 12. With CSMA disabled 13. Start of factory reset command to end of last ACK response Flash (Non-Volatile) Memory Specifications Flash Refresh Cycles Input power < -60dBm 1. Measured at 3.3V VCC 2. Measured at 25C 3. 4. Characterized but not tested 5. PER = 1%
6. Into a 50-ohm load 7. No RF interference 8. From end of command to start of response Figure 4: Electrical Specifications Typical Performance Graphs
) m B d
(
r e w o P t t u p u O X T 11.0 10.5 10.0 9.5 9.0 8.5 2.0 2.5 3.3 Supply Voltage (V) Figure 5: HumPRCTM Series Transceiver Max Output Power vs. Supply Voltage
-40C 25C 85C 3.6 4 5
) A m
(
t n e r r u C y p p u S l 40 35 30 25 20 15 25C
-40C 85C
) A m
(
t n e r r u C y p p u S l 40.00 39.50 39.00 38.50 38.00 37.50 37.00 36.50
-40C 25C 85C
-5 0 5 9 2V 2.5V 3.3V 3.6V TX Output Power (dBm) Supply Voltage (V) Figure 6: HumPRCTM Series Transceiver Average Current vs. Transmitter Output Power at 2.5V Figure 9: HumPRCTM Series Transceiver TX Current vs. Supply Voltage at Max Power
) A m
(
t n e r r u C y p p u S l 40 38 36 34 32 30 28 26 24 22 20 25C
-40C 85C
) A m
(
t n e r r u C y p p u S l 23.40 23.20 23.00 22.80 22.60 22.40 22.20 22.00
-40C 25C 85C
-5 0 5 9 2V 2.5V 3.3V 3.6V TX Output Power (dBm) Supply Voltage (V) Figure 7: HumPRCTM Series Transceiver Average TX Current vs. Transmitter Output Power at 3.3V Figure 8: HumPRCTM Series Transceiver TX Current vs. Supply Voltage at 0dBm 6 7
) A m
(
t n e r r u C y p p u S l 24.5 24.3 24.1 23.9 23.7 23.5 23.3 23.1 22.9 22.7 22.5 85C 25C
-40C
) A
(
t n e r r u C y b d n a S t 1.40 1.20 1.00 0.80 0.60 0.40 0.20 0.00 85C 25C
-40C 2 2.1 2.2 2.3 2.4 2.5 2.6 2.7 2.8 2.9 3 Supply Voltage (V) 3.1 3.2 3.3 3.4 3.5 3.6 2.5 3.3 Supply Voltage (V) 3.6 Figure 10: HumPRCTM Series Transceiver RX Scan Current vs. Supply Voltage, 9.6kbps Figure 12: HumPRCTM Series Transceiver Standby Current Consumption vs. Supply Voltage Current consumption while the module is scanning for a transmission. The current is approximately 0.5mA higher when receiving data at 9.6kbps.
) A m
(
t n e r r u C y p p u S l 23 22.8 22.6 22.4 22.2 22 21.8 21.6 21.4 21.2 21 85C 25C
-40C
) m B d
(
g n d a e R i I S S R
-15.00
-25.00
-35.00
-45.00
-55.00
-65.00
-75.00
-85.00
-95.00
-105.00
-40C 25C 85C 2 2.1 2.2 2.3 2.4 2.5 2.6 2.7 2.8 2.9 3 Supply Voltage (V) 3.1 3.2 3.3 3.4 3.5 3.6
-100.00 -90.00 -80.00 -70.00 -60.00 -50.00 -40.00 -30.00 -20.00 -10.00 0.00 Input Power (dBm) Figure 11: HumPRCTM Series Transceiver RX Scan Current vs. Supply Voltage, 115.2kbps Figure 13: HumPRCTM Series Transceiver RSSI Voltage vs. Input Power Current consumption while the module is scanning for a transmission. The current is approximately 2mA higher when receiving data at 115.2kbps. 8 9 Pin Assignments There are three version of the module. The standard version is the smallest. The other versions have mostly the same pin assignments, but the antenna is routed to either a castellation (-CAS) or a U.FL connector (-UFL), depending on the part number ordered. T U O _ A T A D _ D M C I N _ A T A D _ D M C N E _ K C A B P N E _ A N L T E S E R N E _ A P D N G C C V 29 28 27 26 25 24 23 22 21 MODE_IND ACK_OUT GND S7 S6 S5 S4 30 31 32 1 2 3 4 20 19 18 17 16 15 14 GND ANT GND GND GND GND GND 5 6 7 8 9 10 11 12 13 3 S 2 S 1 S 0 S 0 C 1 C D N G N E _ H C T A L N W O D _ R E W O P Figure 15: HumPRCTM Series Transceiver Standard Version Pin Assignments (Top View) MODE_IND ACK_OUT GND S7 S6 S5 S4 T U O _ A T A D _ D M C I N _ A T A D _ D M C N E _ K C A B P N E _ A N L T E S E R N E _ A P D N G C C V 29 28 27 26 25 24 23 22 21 30 31 32 1 2 3 4 5 6 7 8 9 10 11 12 13 3 S 2 S 1 S 0 S 0 C 1 C D N G N E _ H C T A L N W O D _ R E W O P T N A 19 D N G 18 NC MODE_IND ACK_OUT GND S7 S6 S5 S4 T U O _ A T A D _ D M C I N _ A T A D _ D M C N E _ K C A B P N E _ A N L T E S E R N E _ A P D N G C C V 29 28 27 26 25 24 23 22 21 30 31 32 1 2 3 4 5 6 7 8 9 10 11 12 13 3 S 2 S 1 S 0 S 0 C 1 C D N G N E _ H C T A L N W O D _ R E W O P C N 19 D N G 18 ANT Figure 16: HumPRCTM Series Transceiver Pre-certified Version Pin Assignments - UFL Connection (Top View) Pin Descriptions Pin Descriptions Pin Number Name 1, 2, 3, 4, 5, 6, 7, 8 9, 14, 15, 16, 17, 18, 20, 25, 32 S0S71 I/O I/O Description Status Lines. Each line can be configured as either an input to register button or contact closures or as an output to control application circuitry. GND Ground 10 11 12 C0 C1 POWER_DOWN I I I This line sets the input/output direction for status lines S0-S3. When low, the lines are outputs; when high they are inputs. Do not leave floating. This line sets the input/output direction for status lines S4-S7. When low, the lines are outputs; when high they are inputs. Do not leave floating. Power Down. Pulling this line low places the module into a low-power state. The module is not functional in this state. Pull high for normal operation. Do not leave floating. Figure 14: HumPRCTM Series Transceiver Pre-certified Version Pin Assignments - Castellation Connection (Top View) 10 11 Pin Descriptions Pin Number Name I/O Description 13 19 21 22 23 24 26 27 28 29 30 31 LATCH_EN I 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. ANTENNA 50-ohm RF Antenna Port VCC Supply Voltage RESET2 LNA_EN PA_EN CMD_DATA_OUT CMD_DATA_IN ACK_EN PB1 MODE_IND ACK_OUT I 0 O O I I I O O This line resets the module when pulled low. It should be pulled high for normal operation. Leave unconnected to minimize leakage current. Low Noise Amplifier Enable. This line is driven high when receiving. It is intended to activate an optional external LNA. Power Amplifier Enable. This line is driven high when transmitting. It is intended to activate an optional external power amplifier. Command Data Out. Output line for the serial interface commands Command Data In. Input line for the serial interface commands. If serial control is not used, this line should be tied to supply to minimize current consumption. Pull this line high to enable the module to send an acknowledgement message after a valid control message has been received. Do not leave floating. A high on this line initiates the Join process, which causes two units to accept each others transmissions. It is also used with a special sequence to reset the module to factory default configuration. This line indicates module activity. It can source enough current to drive a small LED, causing it to flash. The duration of the flashes indicates the modules current state. This line goes high when the module receives an acknowledgement message from another module after sending a control message. 1. 2. These lines have an internal 20k pull-down resistor These lines have an internal 10k pull-up resistor Figure 17: HumPRCTM Series Transceiver Pin Descriptions Module Dimensions 0.55"
(13.97) 0.45"
(11.43) 0.07"
(1.78) 0.812"
(20.62) 0.271"
(6.88) 0.078"
(1.98) 0.195"
(4.96) Figure 18: HumPRCTM Series Transceiver Dimensions 0.45"
(11.43) 0.116"
(2.95) Figure 19: HumPRCTM Series Transceiver Pre-certified Version Dimensions 12 13 Theory of Operation The HumPRCTM Series transceiver is a low-cost, high-performance synthesized FSK transceiver. Figure 20 shows the modules block diagram. ANTENNA ADC ADC R O T A L U D O M E D 0 90 FREQ SYNTH MODULATOR LNA PA PROCESSOR INTERFACE GPIO /
INTERFACE Figure 20: HumPRCTM Series Transceiver RF Section Block Diagram The HumPRCTM Series transceiver operates in the 902 to 928MHz frequency band. The transmitter output power is programmable. The range varies depending on the antenna implementation and the local RF environment. The RF carrier is generated directly by a frequency synthesizer that includes an on-chip VCO. The received RF signal is amplified by a low noise amplifier (LNA) and down-converted to I/Q quadrature signals. The I/Q signals are digitized by ADCs. A low-power onboard communications processor performs the radio control and management functions including Automatic Gain Control
(AGC), filtering, demodulation and packet synchronization. A control processor performs the higher level functions and controls the serial and hardware interfaces. A crystal oscillator generates the reference frequency for the synthesizer and clocks for the ADCs and the processor. Module Description 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 units inputs. This allows for the easy creation of basic remote control systems. The module operates through a series of dedicated I/O lines, resulting in a solution that does not need any software development. The module does have a serial interface that allows for some configuration in applications that need specific control. This interface is likely not needed for basic remote control applications. Since this module can act as both transmitter and receiver, terminology and descriptions are important. This guide uses the term Initiating Unit (IU) to describe a module that is transmitting commands. Responding Unit (RU) is used to describe a module that is receiving commands. The module has 8 status lines numbered S0 through S7. These can be set as inputs for buttons or contacts or as outputs to drive application circuitry. When S0 is taken high on the IU, S0 goes high on the RU, and so forth. A line that is an input on one side needs to be set as an output on the other side. The HumPRCTM Series adds a remote control application layer to the HumPROTM Series data modem protocol stack. This enables the simple creation of remote control systems that benefit from the robust feature set of the protocol stack, such as a fast locking Frequency Hopping Spread Spectrum (FHSS) algorithm, AES128 encryption, 32-bit addressing, assured delivery and a simple Join Process for associating multiple modules with each other. As a result, much of the HumPRCTM Series terminology is the same as the HumPROTM Series. Likewise, most of the software registers are the same though some do not apply to the remote control application. A result of this common protocol stack is that HumPRCTM Series transmissions can be received by another HumPRCTM Series module for simple remote control applications or by a HumPROTM Series module for applications that want to combine data transmissions (such as sensor values) with remote control functionality. 14 15 Transceiver 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. If all of the status lines are set as outputs, then the module is set as an RU only. It stays in Receive Operation looking for a valid transmission from a paired IU. A module with both input and output status lines can operate as an IU and an RU. The module idles in Receive Operation until either a valid transmission is received or a status line input goes high, initiating the Transmit operation. Transmit Operation When a status line input goes high, the module enters the Initiating Unit role. In this role, the module captures the logic states of the status line inputs and automatically creates a REMOTE_ACTIVATE packet. The packet is transmitted every 140ms nominally (240ms max) for as long as a status line input is held high. After each transmission, the module listens for a REMOTE_CONFIRM reply from the RU. This continues for as long as any status line input is high. The REMOTE_CONFIRM packet contains two values. One indicates how long the ACK_OUT line should go high on the IU (20ms by default) and the other indicates if the IU should stay awake after the status line inputs go low (go to sleep by default). The module activates the ACK_OUT line for as long as instructed and loops back to check the status line inputs and send another REMOTE_ACTIVATE packet. When an input goes high, the transceiver captures the logic state of each of the status lines. The line states are placed into a packet and transmitted using the configured addressing mode, hop sequence and encryption key
(if enabled). When all status line inputs go low, the module transmits two REMOTE_ ACTIVATE packets indicating that all lines are low. If all status lines are inputs, it then goes to sleep after 760ms unless a REMOTE_CONFIRM packet is received instructing the IU to stay awake longer. An associated RU receives the packet and sets its status line outputs according to the received packet. It then stays synchronized with the IU and updates the states of its outputs with every packet. Its outputs can be connected to external circuitry that activates when the lines go high. The RU can also send an acknowledgement back to the IU. If the ACK_EN line is high when a valid control packet is received, the RU sends back an acknowledgement. When the IU receives the acknowledgement, it raises its ACK_OUT line. The ACK_EN line can be connected to ground to disable acknowledgements, connected to the power supply to acknowledge on receipt of the valid command or controlled by external circuitry to acknowledge when an action has taken place. The ACK_EN can be connected to an LED as an indication to the user or used by the system in other ways, such as updating a display or being used to deactivate an automated system. Note: Although the functionality of the HumPRCTM is very similar to the HumRCTM, the underlying protocol and operation are very different. The two families are not compatible. Receive Operation When the module is awake and not in transmit operation, it is in receive operation listening for valid packets. When a REMOTE_ACTIVATE packet is received, the module enters the Responding Unit role and processes the received status line states. It remains in the RU mode until 760ms elapses without an incoming REMOTE_ACTIVATE message. Unlatched status line outputs are set to match the corresponding bit state in the received packet. For latched outputs, the line changes state (off on or on off) whenever the corresponding bit changes from 0 to 1. All other combinations of the new and old status bit do not change the status line. This normally changes the output state every time that the associated transmitter input changes from 0 to 1. If the ACK_EN line is high when a valid message is received, a REMOTE_ CONFIRM message is transmitted to the IU with values to set the ACK_ OUT high for 20ms and go to sleep after the default 760ms. These values cannot be changed in the HumPRCTM Series, but a packet with different values can be generated using the HumPROTM Series and a microcontroller. 16 17 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. The addressing method used by the HumPRCTM Series modules can support up to hundreds of nodes, depending on the use model (duration of activations and how often they are sent). It is up to the designer to determine which device makes the most sense as the Administrator in the final system, but there are some common configurations. In a system with one transmitter and one receiver, it does not matter which is the Administrator. In a system where one transmitter is going to activate several receivers, the transmitter is normally the Administrator (Figure 21 a). In a system with one receiver and multiple transmitters, the receiver is normally the Administrator (Figure 21 b). Administrator Administrator a b Figure 21: HumPRCTM Series Transceiver Transmitter to Receiver Ratios A system with multiple transmitters and receivers can use any of the devices as an Administrator (Figure 22 a) or may use a separate device that is only used to join new devices to the network (Figure 22 b). Once all system nodes have received the key and their address, the Administrator node operates the same as any other node. By default, the Administrator and all Nodes broadcast to the entire network. All transmitters can activate all receivers in the network. An external microcontroller can be used to change the UDESTID0 register to activate a specific Node in the network. This is a more advanced operation and requires the microcontroller and custom firmware. a b Administrator Figure 22: HumPRCTM Series Transceiver Multiple TX and RX Reading the Transmitter Address The HumPRCTM Series modules do not require any software for basic operation. There is no compiler to get, no code to write and download into the module. However, the built-in Command Data Interface (CDI) can be used to add additional or advanced functionality to a system. One such feature is the ability to read out of the receiver the identity of the transmitter that sent the commands. This allows an external processor to log access attempts or set additional controls over which transmitters are allowed to activate the product outside of the module. By default, the module automatically configures itself to respond to the transmitting module (AUTOADDR = 0x07). This configuration takes the source address from the received packet and writes it to the UDESTID registers UDESTID[0-3]. Reading these registers after a valid transmission has been received indicates the transmitter that sent the command. 18 19 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 RF data rate and hopping sequence to communicate. Assigning different hopping sequences to multiple networks in the same area minimizes the interference. When the module is awake and not transmitting, it rapidly scans all channels for a packet preamble. When a module starts transmitting at the beginning of a new channel, it transmits a packet with a long preamble of alternating 0 and 1 bits. This long preamble is sufficient to allow receiving modules to scan through all of the channels in the hopping sequence and find it. Modules that are scanning detect the preamble and pause on that channel, waiting for a valid packet. If a packet is received with a valid CRC (unencrypted) or authentication
(encrypted), the header is examined to determine whether the module should synchronize to the transmitter. Synchronization requires that the hop sequence matches and that the message is addressed to the receiver. When synchronized, the receiver stays on the current channel to either transmit a packet or to receive an additional packet. Additional packets transmitted on the same channel within the time slot use short preambles since the receivers are already listening to the current channel. At the end of the time slot for the current channel, all modules which locked to the original transmission switch to the next channel in the hop sequence. The first transmission on each new channel has a long preamble. A receiver that has synchronized to a transmitter continues to stay in synchronism by staying on the received channel until the expiration of the time slot, then waiting on the next hop channel for the duration of the time slot. If no further packets are received, the receiver loses lock and reverts to scanning. This allows the receiver to stay synchronized for a short while if a packet is not received correctly. 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. There are three addressing modes: DSN, User and Extended User. Each mode offers different communications methods, but all use source and destination addressing. The source address is for the transmitting unit, the destination address is the intended receiver. Each mode uses different registers for the source and destination addresses. Extended User Addressing mode uses the customer ID bytes
(CUSTID[1-0]) for unencrypted messages and the four user destination address bytes (UDESTID[3-0]) as a destination address. The modules local address is contained in the four user source ID registers (USRCID[3-0]). In normal operation, each module has a user ID mask (UMASK[3-0]) that splits the 32 address bits into up to three fields to provide a network address and address fields for sub-networks, supporting both individual addressing and broadcast addressing within the users network. The HumPRCTM Series is normally configured using the Join Process, which sets the addressing mode to Extended User mode. The other modes would normally only be used if the HumPRCTM Series is being implemented in a mixed system that also uses the HumPROTM Series modules. Please see the HumPROTM Series data guide for a description of the other addressing modes. A detailed explanation and examples for each addressing mode are given in Reference Guide RG-00105. 20 21 AES Encryption 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. The HumPRCTM Series module has the option to use AES encryption, arguably the most common encryption algorithm on the market. This is implemented in a secure mode of operation to ensure the secrecy of the transmitted data. It uses a 128-bit key to encrypt the transmitted data. The source and destination addresses are sent in the clear. There are two ways to enable encryption and set the key: sending serial commands and using the Join Process. Writing an encryption key to the module with the CDI The module has no network key when shipped from the factory. An encryption key can be written to the module using the CDI. The CMD register is used to write or clear a key. The key cannot be read. The same key must be written to all modules that are to be used together. If they do not have the same key, then they will not communicate in encrypted mode. The Join Process The Join Process can be used to generate and distribute the encryption key and addresses through a series of button presses. The key is stored in an Administrator device and the process uses a factory key to distribute the key to node devices in a secure manner. See the Join Process section for more information on this feature. The Join Process The Join Process is a method of generating a random encryption key and random network base address, then distributing the key and addresses to associated modules through a series of button presses. This makes it very simple to establish an encrypted network in the field or add new nodes to an existing network without any additional equipment. It is also possible to trigger the Join Process through commands on the Command Data Interface. All modules configured from the same administrator using the Join Process can communicate with each other. Other modules are added to the network one at a time. The hardware required is a pushbutton that is connected to the PB line. This takes the line to VCC when it is pressed and ground when it is released. An LED connected to the MODE_IND line provides visual indication of the modules state. 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 is selected. When the button is released the key and address generation are performed and the module becomes an administrator. An alternative way to set a module as administrator is by briefly pressing the button twice before holding it for 30 seconds. This method selects the high UART (57600 bps) data rate and high RF data rate. When other units are Joined, they will also be set to the high data rates. When Generate Key is performed, the unit is set as the network administrator. It generates a random 128-bit AES encryption key based on ambient RF noise and scrambled by an encryption operation. If UMASK is the default value (0xFFFFFFFF), it is set to 0x000000FF, supporting up to 254 nodes, and ADDMODE is set to Extended User Address with encryption (0x27) (or without encryption (0x07) if flag PGKEY in the SECOPT register was set to 0 by serial command). UMASK and ADDMODE are not changed if UMASK is not 0xFFFFFFFF. A random 32-bit address is generated. By default, the lower 8 bits are 0, forming the network base address. Other nodes are assigned sequential addresses, starting with network base address +1. UDESTID is set to the bitwise OR of USRCID and UMASK, which is the network broadcast address. 22 23 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. Once the Join Process is complete, the MODE_IND blinks on both units and they now operate together. This is shown in Figure 23 A. If UMASK is pre-set when Generate Key is initiated, then the Join Process uses that mask and sets the address accordingly. This can allow more nodes in the network. This is shown in Figure 23 B. Likewise, the network key can be written to the module with the CDI interface. If the PGKEY bit in the SECOPT register is also set to 0, the Generate Key process will generate a network address without changing the preset key. Or the administrator can be completely configured through the CDI and the Join Process used to associate nodes in the field. This gives the system designer many options for configuration. The SECOPT register is used to configure options related to the Join Process. This allows the OEM to set desired values at the factory and allow final network configuration in the field. This includes disabling the ability to change the address, change the key, share the key or perform a factory reset through the PB line. The built-in security prohibits changing a node to an administrator without changing the key. Please see Reference Guide RG-00107, The HumPROTM Series Join Process for more details and examples of the Join Process. A) Key Generation and Network Join from Factory Default Generate Key D A UMASK = FF FF FF FF USRCID = FF FF FF FF UDESTID = FF FF FF FF No Key UMASK = 00 00 00 FF USRCID = 76 54 32 00 UDESTID = 76 54 32 FF Network Key JOIN D N UMASK = FF FF FF FF USRCID = FF FF FF FF UDESTID = FF FF FF FF No Key UMASK = 00 00 00 FF USRCID = 76 54 32 01 UDESTID = 76 54 32 FF Network Key A UMASK = 00 00 00 FF USRCID = 76 54 32 00 UDESTID = 76 54 32 FF Network Key Key Generation and Network Join from Preset Mask Generate Key P A UMASK = 00 00 0F FF USRCID = FF FF FF FF UDESTID = FF FF FF FF No Key UMASK = 00 00 0F FF USRCID = 76 54 30 00 UDESTID = 76 54 3F FF Network Key JOIN D N UMASK = FF FF FF FF USRCID = FF FF FF FF UDESTID = FF FF FF FF No Key UMASK = 00 00 0F FF USRCID = 76 54 30 01 UDESTID = 76 54 3F FF Network Key B) A D = Factory Default A = Network Administrator N = Network Node P = OEM Preset Unit UMASK = 00 00 0F FF USRCID = 76 54 30 00 UDESTID = 76 54 3F FF Network Key Figure 23: HumPRCTM Series and HumPRCTM Series Join Process Examples 24 25 Operation with the HumPROTM Series The commands from the HumPRCTM 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. 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. It can also read out the packet header and know the address of the sending module and respond with a REMOTE_CONFIRM packet to activate the ACK_OUT line on the HumPRCTM module. Likewise, the microcontroller can be programmed to send a REMOTE_ ACTIVATE packet to a HumPRCTM Series module. This opens up many options for creative mixed-mode design. Remote Activation The REMOTE_ACTIVATE packet consists of six bytes:
0x03 0x00 0x00 0x00 0x10 <STATUS>
The first byte is 0x03 with the next three bytes 0x00. Byte five is 0x10 which indicates a Remote Activation. Byte six is the STATUS byte, which is a bit map of the status line states. Bit 0 corresponds to status line S0 and so forth. Each bit is 1 if the corresponding line is high. Remote Confirm The REMOTE_CONFIRM packet has the following format:
0x03 0x00 0x00 0x00 0x11 <DURATION> <ALIVE>
The first byte is 0x03 with the next three bytes 0x00. Byte five is 0x11 and indicates that the packet is a remote confirm packet. The DURATION byte indicates the amount of time that the ACK_OUT line should be held high. This value is multiplied by 10ms. If the value is 0, the output is immediately taken low. The default value is 0x02 for 20ms. This value overrides the effect of a previously received REMOTE_CONFIRM packet. The ALIVE byte indicates how long after the transmission the IU module should stay awake in receive mode. This value is multiplied by 0.1s. Once this duration expires, the module returns to sleep mode. This message is transmitted to the IUs address. It must be received by the IU within one second of initial transmission or within the ALIVE interval of the previous REMOTE_CONFIRM packet. Carrier Sense Multiple Access (CSMA) 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. When a module has data ready to transmit and CSMA is enabled, it listens on the intended transmit channel for activity. If no signal is detected, transmission is started. If a carrier is detected with an RSSI above the CSMA threshold in the CSRSSI register, transmission is inhibited. If a signal below the threshold is detected that has a compatible preamble or packet structure, transmission is also inhibited. If the module is synchronized from a recent packet transfer, it waits for a random interval, then checks again for activity. If the detected carrier lasts longer than the time allowed for the current channel, the module hops to the next channel in the hop sequence and again waits for a clear channel before transmitting. If the module is not synchronized, it hops to the next channel and again checks for interference. When no activity is detected it starts transmitting. This feature is disabled by default in the HumPRCTM so that the fastest response time is obtained. Enabling it can impact transmission timing, so care should be taken with its use. 26 27 Acknowledgement 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. When the Responding Unit receives a valid REMOTE_ACTIVATE packet, it immediately checks the state of the ACK_EN line. If it is high the module sends a REMOTE_CONFIRM packet. When the Initiating Unit receives a REMOTE_CONFIRM packet, it pulls the ACK_OUT line high for an amount of time specified by the REMOTE_ CONFIRM packet (20ms by default). Connecting the ACK_EN line to VCC causes the RU to transmit REMOTE_ CONFIRM packets as soon as it receives a valid REMOTE_ACTIVATE packet. Alternately this line can be controlled by an external circuit that raises the line when a specific action has taken place. This confirms to the IU that the action took place rather than just acknowledging receipt of the signal. Note: Only one RU should be enabled to transmit an acknowledgement response for a given IU since multiple acknowledgements will interfere with each other. External Amplifier Control The HumPRCTM Series transceiver has two output lines that are designed to control external amplifiers. The PA_EN line goes high when the module activates the transmitter. This can be used to activate an external power amplifier to boost the signal strength of the transmitter. The LNA_EN line goes high when the module activates the receiver. This can be used to activate an external low noise amplifier to boost the receiver sensitivity. These external amplifiers can significantly increase the range of the system at the expense of higher current consumption and system cost. The states of the PA_EN and LNA_EN lines can be read in the LSTATUS register. This offers a quick way to determine the current state of the radio. Note: Adding an external power amplifier and/or low noise amplifier to the pre-certified module will invalidate its regulatory certifications. Configuring the Status Lines 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. When C0 is low, S0 through S3 are outputs; when high, they are inputs. Likewise, when C1 is low, S4 through S7 are outputs; when high, they are inputs. This is shown in Figure 24. The C0 and C1 lines are sensed at power-up and when the RCCTL register is changed. HumPRCTM Series Transceiver Status Line Direction Configuration Line C0 C1 0 1 S0 through S3 are outputs S0 through S3 are inputs S4 through S7 are outputs S4 through S7 are inputs Figure 24: HumPRCTM Series Transceiver Status Line Direction Configuration When the ENC01 bit is 0 the status line direction is determined by the RCDIR register. This register acts as a bit map of the status lines. When bit n is 1, status line Sn is an input line. When bit n is 0, status line Sn is an output line. Using the LATCH_EN Line The LATCH_EN line sets the outputs to either momentary operation or latched operation. During momentary operation, the outputs go high for as long as control messages are received instructing the module to take the lines high. As soon as the control messages stop, the outputs go low. During latched operation, when a signal is received to make a particular status line high, it remains high until a separate activation is received to make it go low. The controlling line on the IU must go low then high to toggle the latched output on the RU. Latch operation is controlled by bit 1 in the RCCTL register. When this bit is a 1 all outputs are latched. When it is a 0, the state of the LATCH_EN line sets the latching status. In this case, when the LATCH_EN line is high, all of the outputs are latched. 28 29 Using the MODE_IND Line The MODE_IND line is designed to be connected to an LED to provide visual indication of the modules 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 One quick blink Quick blink Slow Blink Administrator Join. The administrator is looking for a node to join with. Node Join. The node is looking for an administrator to join with. Key Transfer Active. Key transfer is taking place
(administrator and node). Key Transfer Complete. The module has completed a key transfer (administrator and node). Temporary On On when the PB line is high Two quick blinks, one time Join Canceled. Failure. For Share Key or Get Key, there are multiple units attempting to pair, protocol error, or timeout without response Long Hold Acknowledgement. The long hold period for Generate Key or Reset Sequence was recognized (PB is asserted) Slow blink, repeat 3 times Slow blink and two quick blinks Key Test Results One quick blink Three times Figure 26 shows the MODE_IND displays in a graphical format. Operation Administrator Join Node Join Key Transfer Active Key Transfer Complete JOIN Cancelled Long Hold Failure No Key Set Key Set, Node Key Set, Administrator Time (seconds) MODE_IND Display Comments Repeats for 30 seconds or until JOIN is complete Repeats for 30 seconds or until JOIN is complete Repeats for the duration of the transfer Six blinks total Repeats for as long as the PB line is asserted after the long hold period has been recognized Repeats, three times total Repeats, three times total Repeats, three times total 0 0.5 1 1.5 2 2.5 Figure 26: HumPRCTM Series MODE_IND Displays Using the PB Line The PB Line is used to trigger functions associated with the Join Process. This line should be connected to a momentary pushbutton that pulls the line to VCC when it is pressed and opens the circuit when it is released. The sequence of presses determines which function is triggered. Figure 27 shows the sequences. No Key. There is no network key or network address. Function Sequence HumPRCTM Series Transceiver PB Line Operation Two quick blinks Three times Key Set, node. The network key and network address are set on a node. Three quick blinks Three times Key Set, administrator. The network key and network address are set on an administrator. Normal operation Off No activity Temporarily on Transmitting or receiving packet Figure 25: HumPRCTM Series MODE_IND Line Timing Join a network 1 short pulse Cancel a Join Process that is in progress 1 short pulse Generate a network key and address;
9,600bps Generate a network key and address;
57,600bps Reset to factory defaults Test key and address Hold high for 30 seconds 2 short pulses and hold high for 30 seconds 4 short pulses and hold high for 3 seconds 3 short pulses A short pulse is a logic high that is between 100 and 2,000ms in duration. Figure 27: HumPRCTM Series PB Line Operation 30 31 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. After PB goes low, the non-volatile configurations are set to the factory default values and the module is restarted. The default UART data rate is 9,600bps. If the timing on PB does not match the limits, the sequence is ignored. Another attempt can be made after lowering PB for at least 3 seconds. Using the Low Power Features The module supports a sleep state to save current in battery-powered applications. During the sleep state, no module activity occurs and no packets can be received but current consumption is less than 1A typical. There are two ways of putting the module to sleep. First, pulling the Power Down (POWER_DOWN) line low puts the module to sleep. Taking the line high wakes the module. Second, all of the following should be true:
1. There is no transmission in progress 2. All status lines are low and either IDLE = 1 (default) and all status lines are configured as inputs, or IDLE = 2 (allows sleeping when incoming control message can be missed) 3. The internal KeepAlive timer has expired. The internal KeepAlive timer is set by the following events:
1. On wakeup from a transition on the CMD_DATA_IN line, KeepAlive is set to 2s. This allows time for an external unit to change IDLE to 0 to keep the unit awake. 2. On each transmission, KeepAlive is set to 760ms if the remaining KeepAlive time is less.
[max(760ms, KeepAlive)]
3. On reception of a REMOTE_CONFIRM packet, KeepAlive is set to received ALIVE value multiplied by 0.1s if the remaining KeepAlive time is less. The KeepAlive can be extended indefinitely by periodic reception of REMOTE_CONFIRM messages. max(REMOTE_CONFIRM.keepAlive * 100ms, KeepAlive) During sleep mode, the output lines are in the states in Figure 28. HumPRCTM Series Transceiver Output Line Sleep States Output Line S0 - S7 output LNA_EN PA_EN CMD_DATA_OUT MODE_IND ACK_OUT Sleep State Low Low Low Low Low Low Figure 28: HumPRCTM Series Output Line Sleep States When the POWER_DOWN line is high, the module awakens when a status line input goes high, the PB line goes high or there is a change on the CMD_DATA_IN lines. If a negative-going pulse is needed to generate a rising edge, the pulse width should be greater than 1 s. If the volatile registers have been corrupted during sleep, a software reset is performed. This restarts the module as if power were cycled. This can be caused by power surges or brownout among other things. Pulsing RESET low causes the module to restart rather than continue from sleep. IDLE = 1 is used when the module is an IU only. This puts it to sleep when all status line inputs are low. IDLE = 2 is used when the module is primarily an IU, but can accept activation commands from remote units. In this case, the module stays asleep until a status line input goes high. While awake, the module can receive activation commands and will remain awake while commands are received. As soon as all status line inputs and outputs go low, the module returns to sleep. 32 33 Reading from Registers A register read command is constructed by placing an escape character
(0xFE) before the register number. The module responds by sending an ACK (0x06) followed by the register number and register value. The register value is sent unmodified, so if the register value is 0x83, 0x83 is returned. If the register number is invalid, the module responds with a NACK (0x15). The command and response are shown in Figure 29. HumPRCTM Series Read From Configuration Register Command Header 0xFF Size 0x02 Escape Address 0xFE REG Response ACK 0x06 Address Value REG V Command for an Address greater than 128 (0x80) Header 0xFF Size 0x03 Response Escape Addr1 Addr2 0xFE 0xFE REG-80 ACK 0x06 Address Value REG V Figure 29: HumPRCTM Series Read from Configuration Register Command and Response The Command Data Interface 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 modules 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). Configuration settings are stored in two types of memory inside the module. Volatile memory is quick to access, but it is lost when power is removed from the module. Non-volatile memory has a limited number of write cycles, but is retained when power is removed. When a configuration parameter has both a non-volatile and volatile register, the volatile register controls the operation unless otherwise stated. The non-volatile register holds the default value that is loaded into the volatile register on power-up. Configuration settings are read from non-volatile memory on power up and saved in volatile memory. The volatile and non-volatile registers have different address locations, but the same read and write commands. The two locations can be changed independently. The general serial command format for the module is:
[FF] [Length] [Command]
The Length byte is the number of bytes in the Command field. The Command field contains the register address that is to be accessed and, in the case of a write command, the value to be written. Neither Length nor Command can contain a 0xFF byte. Byte values of 128 (0x80) or greater can be sent as a two-byte escape sequence of the format:
0xFE, [value - 0x80]
For example, the value 0x83 becomes 0xFE, 0x03. The Length count includes the added escape bytes. A response is returned for all valid commands. The first response byte is CMD_ACK (0x06) or CMD_NACK (0x15). Additional bytes may follow, as determined by the specific command. 34 35 Command Length Optimization Some commands may be shortened by applying the following rules:
1. Escape sequences are not required for byte values 0x00 to 0xEF
(besides 0xFE and 0xFF, bytes 0xF0 0xFD are reserved for future use). 2. An escape byte inverts bit 7 of the following data byte. 3. The 0xFE as the first byte of the Read Register Command field is an escape byte. 4. Two consecutive escape bytes cancel unless the following data byte is 0xf0-0xff. Examples:
FF 02 FE 02 (read nv:TXPWR) is equivalent to FF 01 82. FF 03 FE FE 53 (read v:PKOPT) is equivalent to FF 01 53. FF 03 1A FE 7F (write FF to nv:UMASK0) cannot be shortened. FF 03 1A FE 40 (write C0 to nv:UMASK0) is equivalent to FF 02 1A C0. These rules are implemented in the sample code file EncodeProCmd.c, which can be downloaded from the Linx website. Writing to Registers 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. HumPRCTM Series Write to Configuration Register Command Register and Value less than 128 (0x80) Header Size Address Value 0xFF 0x02 REG V Register less than 128 (0x80) and a Value greater than or equal to 128 (0x80) Header Size Address Escape Value 0xFF 0x03 REG 0xFE V-0x80 Register greater than or equal to 128 (0x80) and a Value less than 128 (0x80) Header Size Escape Address Value 0xFF 0x03 0xFE REG-0x80 V Register and Value greater than or equal to 128 (0x80) Header Size Escape Address Escape Value 0xFF 0x04 0xFE REG-0x80 0xFE V-0x80 Figure 30: HumPRCTM Series Write to Configuration Register Command Generally, there are three steps to creating the command. 1. Determine the register address and the value to be written. 2. Encode the address and value as either the number (N) or the encoded number (0xFE, N-0x80) as appropriate. 3. Add the header (0xFF) and the size. The module responds with an ACK (0x06). If the ACK is not received, the command should be resent. The module responds with a NACK (0x15) if a write is attempted to a read-only or invalid register. As an example, to write 01 to register 0x83, send FF 03 FE 03 01 Note: The non-volatile memory has a life expectancy with a limited number of refresh cycles. Please see the electrical specifications. 36 37 return dx;
}
/* Function: HumProRead
** Description: This function encodes a read command to the specified
** register address.
*/
unsigned char /* number of encoded bytes, 3 to 4 */
HumProRead(
unsigned char *cmd, /* out: encoded read command, length >= 4 */
unsigned char reg /* register number to read, 0..0xff */
) {
unsigned char ra; /* read register byte */
ra = reg ^ 0x80;
return HumProCommand(cmd, &ra, 1);
}
/* Function: HumProWrite
** Description: This function encodes a command to write a single byte to
** a specified register address.
*/
unsigned char /* number of encoded bytes, 4 to 6 */
HumProWrite(
unsigned char *cmd, /* out: encoded read command, length >= 6 */
unsigned char reg, /* register number to write, 0..0xff */
unsigned char val /* value byte, 0..0xff */
) {
unsigned char cs[2];
cs[0] = reg;
cs[1] = val;
return HumProCommand(cmd, &cs, 2);
}
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.c
/* Sample C code for encoding HUM-fff-PRO commands
**
** Copyright 2015 Linx Technologies
** 159 Ort Lane
** Merlin, OR, US 97532
** www.linxtechnologies.com
**
** License:
** Permission is granted to use and modify this code, without royalty, for
** any purpose, provided the copyright statement and license are included.
*/
#include EncodeProCmd.h
/* Function: HumProCommand
** Description: This function encodes a command byte sequence.
** If len = 1, a read command is generated.
** If len > 1, a write command is generated.
** rcmd[0] = register number
** rcmd[1..(n-1)] = bytes to write
*/
unsigned char /* number of encoded bytes, n+2 to 2*n+2 */
HumProCommand(
unsigned char *ecmd, /* out: encoded command, length >= 2*n + 2 */
const unsigned char *rcmd, /* in: sequence of bytes to encode */
unsigned char n /* number of bytes in rcmd, 1..32 */
) {
unsigned char dx; /* destination index */
unsigned char sx; /* source index */
unsigned char v; /* value to be encoded */
dx = 2;
sx = 0;
while (n--) {
v = rcmd[sx++];
if (v >= 0xf0) {
ecmd[dx++] = 0xfe;
v &= 0x7f;
}
ecmd[dx++] = v;
}
ecmd[0] = 0xff;
ecmd[1] = dx - 2;
38 39 The Command Data Interface Command Set The following sections describe the registers. HumPRCTM Series Configuration Registers Name CRCERRS HOPTABLE TXPWR UARTBAUD ADDMODE DATATO MAXTXRETRY ENCRC BCTRIG ENCSMA IDLE WAKEACK NV Addr Vol Addr 0x40 0x4B 0x00 0x4D 0x02 0x4E 0x03 0x4F 0x04 0x50 0x05 0x52 0x07 0x53 0x08 0x09 0x54 0x0B 0x56 0x0D 0x58 0x59 0x0E R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W Default Value Description CRC Error Count Channel Hop Table Transmit Power UART data rate Addressing mode Data timeout 0x00 0xFF 0x03 0x01 0x0F 0x10 0x02 Maximum Transmit Retries 0x01 0x40 0x01 0x01 0x01 Enable CRC checking Byte Count trigger Enable CSMA Idle Mode UART Acknowledge on Wake Destination Address for User Packet Type, extended Destination Address for User Packet Type, extended Destination Address for User Packet Type Destination Address for User Packet Type Source Address for User Packet Type, extended Source Address for User Packet Type, extended Source Address for User Packet Type Source Address for User Packet Type Address Mask for User Packet Type, extended Address Mask for User Packet Type, extended Address Mask for User Packet Type Address Mask for User Packet Type Destination Device Serial Number Destination Device Serial Number Destination Device Serial Number Destination Device Serial Number UDESTID3 0x0F 0x5A R/W 0xFF UDESTID2 0x10 0x5B R/W 0xFF UDESTID1 0x11 0x5C R/W 0xFF UDESTID0 0x12 0x5D R/W 0xFF USRCID3 0x13 0x5E R/W 0xFF USRCID2 0x14 0x5F R/W 0xFF USRCID1 USRCID0 0x15 0x16 0x60 0x61 R/W R/W 0xFF 0xFF UMASK3 0x17 0x62 R/W 0xFF UMASK2 0x18 0x63 R/W 0xFF UMASK1 UMASK0 DESTDSN3 DESTDSN2 DESTDSN1 DESTDSN0 0x64 0x19 0x1A 0x65 0x1D 0x68 0x69 0x1E 0x1F 0x6A 0x6B 0x20 R/W R/W R/W R/W R/W R/W 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 40 0x22 0x23 0x24 0x25 0x26 0x34 0x35 0x36 0x37 0x39 0x3A 0x3F 0x78 RCCTL CMDHOLD RCDIR COMPAT AUTOADDR MYDSN3 MYDSN2 MYDSN1 MYDSN0 CUSTID1 CUSTID0 CSRSSI RELEASE RCSLS PRSSI ARSSI FWVER3 FWVER2 FWVER1 FWVER0 NVCYCLE1 NVCYCLE0 LSTATUS CMD SECSTAT JOINST EEXFLAG2 EEXFLAG1 EEXFLAG0 0x80 EEXMASK2 0x81 EEXMASK1 0x82 EEXMASK0 0x83 PKTOPT 0x84 SECOPT LASTNETAD[3] 0x8C LASTNETAD[2] 0x8D LASTNETAD[1] 0x8E LASTNETAD[0] 0x8F 0xC0 0xC1 0xC2 0xC3 0xC4 0xC5 0x6D 0x6E 0x6F 0x70 0x71 R/W R/W R/W R/W R/W 0x01 0x01 0xFF 0x02 0x07 R R R R R R 0xFF 0xFF RC control Hold RF data when nCMD pin is low RC status line direction select Compatibility Automatic Reply Address Factory programmed Serial Number Factory programmed Serial Number Factory programmed Serial Number Factory programmed Serial Number Factory programmed customer ID Factory programmed customer ID R/W 0xBA Carrier Sense minimum RSSI 0x7A 0x7B 0x7C R R R R R R R R R R R W R R 0xC6 0xC7 0xC9 0xCA 0xCD R/W R/W 0xCE R/W 0xCF 0xD0 R/W R/W 0xD1 R/W 0xD2 R/W 0xD3 0xD4 R/W R/W R/W R/W R/W Release number RC status line state Packet RSSI Ambient RSSI Firmware version, major Firmware version, minor Firmware version, increment Firmware version, suffix NV Refresh Cycles, MS NV Refresh Cycles, LS Status lines Command register Security Status Join Status Extended exception flags Extended exception flags Extended exception flags Extended exception mask Extended exception mask Extended exception mask Packet options Security Options Last Network Address Assigned Last Network Address Assigned Last Network Address Assigned Last Network Address Assigned 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x01 0xFF 0x00 0x00 0x00 0x00 41 Figure 31: HumPRCTM Series Configuration 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 Read Command Header 0xFF Size 0x02 Write Command Header 0xFF Size 0x02 Escape Address 0xFE 0x40 Address Value 0x40 V Read Response ACK 0x06 Address Value 0x40 V Figure 32: HumPRCTM Series CRC Error Count Command and Response HOPTABLE - Channel Hop Table Volatile Address = 0x4B; Non-Volatile Address = 0x00 The module supports 6 different hop sequences with minimal correlation. The sequence is set by the value in the HOPTABLE register. Changing the hop sequence changes the band utilization, much the same way that a channel does for a non-hopping transmitter. The hop table selection must match between the transmitter and receiver. Valid values are 0-5. The default value of 0xFF must be changed before communication can occur. This is normally done by the Join Process. Figure 33 shows the command and response. HumPRCTM Series Channel Hop Table Read Command Read Response Header Size Escape Address ACK Address Value 0xFF 0x02 0xFE 0x4B 0x00 0x06 0x4B 0x00 V Write Command Header Size Address Value 0xFF 0x02 0x4B 0x00 V Figure 34 shows the RF channels used by the HumPRCTM Series. When the baud rate is set to 9,600 or 19,200 bps, the module uses 50 hopping channels. Figure 35 shows the hop sequences referenced by channel number. When the baud rate is 38,400bps and higher, the module uses 26 hopping channels and only even channels are used. Figure 36 shows the hop sequences referenced by channel number. The default hop sequence is 0. HumPRCTM Series RF Channels Channel Number Frequency (MHz) Channel Number Frequency (MHz) 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 902.971 903.347 903.723 904.099 904.475 904.851 905.227 905.602 905.978 906.354 906.730 907.106 907.482 907.858 908.234 908.610 908.986 909.361 909.737 910.113 910.489 910.865 911.241 911.617 911.993 912.369 912.745 913.120 913.496 913.872 914.248 914.624 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 915.000 915.376 915.752 916.128 916.504 916.880 917.255 917.631 918.007 918.383 918.759 919.135 919.511 919.887 920.263 920.639 921.014 921.390 921.766 922.142 922.518 922.894 923.270 923.646 924.022 924.398 924.773 925.149 925.525 925.901 926.277 926.653 Figure 33: HumPRCTM Series Channel Hop Table Command and Response Figure 34: HumPRCTM Series RF Channels 42 43 HumPRCTM Series Hop Sequences by Channel Number for 19,200bps and below HumPRCTM Series Hop Sequences by Channel Number for 38,400bps and Above 0 32 2 4 10 20 42 22 46 28 58 54 44 24 48 34 6 14 30 62 60 56 50 38 12 26 52 1 30 60 58 52 42 20 40 16 34 4 8 18 38 14 28 56 48 32 0 2 6 12 24 50 36 10 2 6 40 42 48 58 16 60 20 2 32 28 18 62 22 8 44 52 4 36 34 30 24 12 50 0 26 3 56 22 20 14 4 46 2 42 60 30 34 44 0 40 54 18 10 58 26 28 32 38 50 12 62 36 4 44 14 16 22 32 54 34 58 40 6 2 56 36 60 46 18 26 42 10 8 4 62 50 24 38 0 Figure 36: HumPRCTM Series Hop Sequences for UART rates of 38,400bps and above 5 18 48 46 40 30 8 28 4 22 56 60 6 26 2 16 44 36 20 52 54 58 0 12 38 24 62 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 11 52 37 36 42 25 15 1 55 2 12 26 27 41 9 8 31 49 13 47 14 33 48 38 45 59 3 46 0 39 57 56 5 40 23 62 24 54 17 22 32 7 61 34 63 50 30 43 28 4 52 10 54 62 21 33 44 51 61 36 34 2 57 50 12 29 6 8 46 48 11 39 4 45 22 56 18 43 60 31 47 0 20 37 59 35 7 15 25 16 23 42 24 32 28 26 13 3 5 49 5 35 23 41 45 7 42 63 24 9 27 10 17 20 22 18 32 3 8 15 4 0 48 13 61 31 56 52 54 55 62 6 37 36 38 51 59 5 43 21 40 14 12 30 16 34 46 60 39 58 33 Figure 35: HumPRCTM Series Hop Sequences for UART rate of 19,200bps and below 44 45 TXPWR - Transmitter Output Power Volatile Address = 0x4D; Non-Volatile Address = 0x02 The value in the TXPWR register sets the modules 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. HumPRCTM Series Transmitter Output Power Mode Read Command Read Response Header Size Escape Address ACK Address Value 0xFF 0x02 0xFE 0x4D 0x02 0x06 0x4D 0x02 PWR Write Command Header Size Address Value 0xFF 0x02 0x4D 0x02 PWR Figure 37: HumPRCTM Series Transmitter Output Power Mode Command and Response UARTBAUD - UART Baud Rate Volatile Address = 0x4E; Non-Volatile Address = 0x03 The value in UARTBAUD sets the data rate of the UART interface. Changing the non-volatile register changes the data rate on the following power-up or reset. Changing the volatile register changes the data rate immediately following the command acknowledgement. Figure 39 shows the command and response and Figure 40 shows the valid settings. HumPRCTM Series UART Baud Rate Read Command Read Response Header Size Escape Address ACK Address Value 0xFF 0x02 0xFE 0x4E 0x03 0x06 0x4E 0x03 V Write Command Header Size Address Value 0xFF 0x02 0x4E 0x03 V Figure 39: HumPRCTM Series UART Baud Rate Command and Response HumPRCTM Series Transmitter Output Power Mode Register Settings HumPRCTM Series UART Baud Rate Register Settings PWR 0x00 0x01 0x02 0x03 Typical Output Power (dBm)
-5 0
+5
+9 Figure 38: HumPRCTM Series Transmitter Output Power Mode Settings ADDMODE - Addressing Mode Volatile Address = 0x4F; Non-Volatile Address = 0x04 This register is controlled automatically by the HumPRCTM application and the Join Process, so should not be changed by external commands. DATATO - Transmit Wait Timeout Volatile Address = 0x50; Non-Volatile Address = 0x05 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. V 0x01 0x02 0x03 0x04 0x05 0x06 0x07 Baud Rate (bps) RF Data Rate (bps) 9,600 19,200 38,400 57,600 115,200 10,400*
31,250*
19,200 19,200 153,600 153,600 153,600 153,600 153,600
* These data rates are not supported by PC serial ports. Selection of these rates may cause the module to fail to respond to a PC, requiring a reset to factory defaults. Figure 40: HumPRCTM Series UART Baud Rate Settings If the modules UART baud rate is different than the host processor UART baud rate then the module will not communicate correctly. If mismatched, every rate can be tested until the correct one is found or the module can be reset to factory defaults. The default baud rate is 9,600bps (0x01). 46 47 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. HumPRCTM Series Maximum Transmit Retries Read Command Read Response Header Size Escape Address ACK Address Value 0xFF 0x02 0xFE 0x52 0x07 0x06 0x52 0x07 V Write Command Header Size Address Value 0xFF 0x02 0x52 0x07 V Figure 41: HumPRCTM Series Maximum Transmit Retries Command and Response The time between retries depends on the current baud rate. Figure 42 shows the time between retries based on baud rate. The elapsed transmit and acknowledgment time is (retries+1) (PacketTransmitTime + Timeout). HumPRCTM Series Acknowledgement Timeout Times Baud Rate Timeout Time 9,600 19,200 38,400 57,600 115,200 50ms 50ms 30ms 30ms 30ms Figure 42: HumPRCTM Series Acknowledgement Timeout Times 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. The default CRC mode setting is enabled. Figure 43 shows examples of the commands and Figure 44 shows the available values. HumPRCTM Series CRC Enable Read Command Read Response Header Size Escape Address ACK Address Value 0xFF 0x02 0xFE 0x53 0x08 0x06 0x53 0x08 V Write Command Header Size Address Value 0xFF 0x02 0x53 0x08 V Figure 43: HumPRCTM Series CRC Enable Command and Response HumPRCTM Series CRC Enable Register Settings V 0x00 0x01 Mode CRC Disabled CRC Enabled Figure 44: HumPRCTM Series CRC Enable Register Settings Although disabling CRC checking allows receiving packets with errors in the payload, errors in the header can still prevent packets from being output by the module. BCTRIG - UART Byte Count Trigger Volatile Address = 0x54; Non-Volatile Address = 0x09 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. 48 49 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. Figure 45 shows examples of the commands and Figure 46 shows the available values. HumPRCTM Series CSMA Enable Read Command Read Response Header Size Escape Address ACK Address Value 0xFF 0x02 0xFE 0x56 0x0B 0x06 0x56 0x0B V Write Command Header Size Address Value 0xFF 0x02 0x56 0x0B V Figure 45: HumPRCTM Series CSMA Enable Command and Response HumPRCTM Series CSMA Enable Register Settings V 0x00 0x01 Mode Disable CSMA Enable CSMA Figure 46: HumPRCTM Series CSMA Enable Register Settings See the Carrier Sense Multiple Access section for details. 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. This is the only setting in which the RF circuitry is able to receive and transmit RF messages. Sleep disables all circuitry on-board the module. This is the lowest-power setting available for the module. Please see the Low Power States section for more details. Figure 47 shows examples of the commands and Figure 48 shows the available values. HumPRCTM Series Idle Mode Read Command Read Response Header Size Escape Address ACK Address Value 0xFF 0x02 0xFE 0x58 0x0D 0x06 0x58 0x0D V Write Command Header Size Address Value 0xFF 0x02 0x58 0x0D V Figure 47: HumPRCTM Series Idle Mode Command and Response HumPRCTM Series Idle Mode Register Settings V 0x00 0x01 0x02 Mode Awake Sleep when all status lines are inputs and low Sleep when all status lines are low Figure 48: HumPRCTM Series Idle Mode Register Settings 50 51 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. HumPRCTM Series ACK on Wake Read Command Read Response Header Size Escape Address ACK Address Value 0xFF 0x02 0xFE 0x59 0x0E 0x06 0x59 0x0E V Write Command Header Size Address Value 0xFF 0x02 0x59 0x0E V Figure 49: HumPRCTM Series ACK on Wake Command and Response 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. These registers are automatically filled with the source address from a received message if the received message address type matches the value in AUTOADDR. Please see the Addressing Modes section for more details. Each register byte is read and written separately. Figure 51 shows the User Destination ID registers. HumPRCTM Series User Destination Address Registers Name Volatile Address Non-Volatile Address Description UDESTID3 UDESTID2 0x5A 0x5B UDESTID1 0x5C UDESTID0 0x5D 0x0F 0x10 0x11 0x12 MSB of the extended destination address Byte 2 of the extended destination address Byte 1 of the extended destination address, MSB of the short destination address LSB of the extended destination address and short destination address HumPRCTM Series ACK on Wake Register Settings Figure 51: HumPRCTM Series User Destination Address Registers V 0x00 0x01 Mode Disable ACK Enable ACK Figure 50: HumPRCTM Series ACK on Wake Register Settings 52 53 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. Please see the Addressing Modes section for more details. Each register byte is read and written separately. Figure 52 shows the User Source ID registers. HumPRCTM Series User Source Address Registers Volatile Address Non-Volatile Address Description Name USRCID3 USRCID2 USRCID1 0x5E 0x5F 0x60 USRCID0 0x61 0x13 0x14 0x15 0x16 MSB of the extended source address Byte 2 of the extended source address Byte 1 of the extended source address MSB of the short source address LSB of the extended source address and short source address 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 53 shows the User ID Mask registers. HumPRCTM Series User ID Mask Registers Name UMASK3 UMASK2 UMASK1 UMASK0 Volatile Address Non-Volatile Address Description 0x62 0x63 0x64 0x65 0x17 0x18 0x19 0x1A MSB of the extended mask Byte 2 of the extended mask Byte 1 of the extended mask MSB of the short mask LSB of the extended mask and short mask Figure 53: HumPRCTM Series User ID Mask Registers Figure 52: HumPRCTM Series User Source Address Registers 54 55 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. Figure 54 shows the Destination DSN registers. HumPRCTM Series Destination DSN Registers Name DESTDSN3 DESTDSN2 DESTDSN1 DESTDSN0 Volatile Address Non-Volatile Address Description 0x68 0x69 0x6A 0x6B 0x1D 0x1E 0x1F 0x20 MSB of the destination DSN Byte 2 of the destination DSN Byte 1 of the destination DSN LSB of the destination DSN Figure 54: HumPRCTM Series Destination DSN Registers RCCTL - RC Control Volatile Address = 0x6D; Non-Volatile Address = 0x22 This register controls RC behavior. HumPRCTM Series RC Control Read Command Read Response Header Size Escape Address ACK Address Value 0xFF 0x02 0xFE 0x6D 0x22 0x06 0x6D 0x22 V Write Command Header Size Address Value 0xFF 0x02 0x6D 0x22 V Figure 55: HumPRCTM Series RC Control Command and Response HumPRCTM Series RC Control Values RCCTL Bit Control 0 1 2 3 4 5 6 7 ENC01 Enable C0 and C1 control inputs LATCHOP latch outputs Reserved Reserved Reserved Reserved Reserved Reserved Figure 56: HumPRCTM Series RC Control Register Settings When ENC01 is 1, the C0 and C1 lines control the status line direction. When 0, register RCDIR controls the status line direction. Please see the Configuring the Status Lines section for more details. When LATCHOP is 1, all output status lines are latched, regardless of the LATCH_EN line state. When 0, the LATCH_EN line determines the latching status of the output lines. 56 57 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. When bit n is 0, status line Sn is an output line. COMPAT - Compatibility Mode Volatile Address = 0x70; Non-Volatile Address = 0x25 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. AUTOADDR - Auto Addressing Volatile Address = 0x71; Non-Volatile Address = 0x26 This register is controlled automatically by the HumPRCTM application, so should not be changed by external commands. HumPRCTM Series RC Status Line Direction Select Read Command Read Response Header Size Escape Address ACK Address Value 0xFF 0x02 0xFE 0x6F 0x24 0x06 0x6F 0x24 V Write Command Header Size Address Value 0xFF 0x02 0x6F 0x24 V Figure 57: HumPRCTM Series Transceiver RC Status Line Direction Select Command and Response On startup, if the ENC01 bit in the RCCTL register is 0, v:RCDIR is set to nv:RCDIR. If ENC01 is 1 on startup, nv:RCDIR is set by control lines C0 and C1. An attempt to write this register when nv:RCCTL.ENC01 = 1 results in a CMD_NACK response. HumPRCTM Series RC Status Line Direction Select Values RCDIR Bit 0 1 2 3 4 5 6 7 Status Line S0 Direction S1 Direction S2 Direction S3 Direction S4 Direction S5 Direction S6 Direction S7 Direction Value 0 = Output 1 = Input Figure 58: HumPRCTM Series Transceiver RC Status Line Direction Select Values 58 59 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. CSRSSI - Carrier Sense Minimum RSSI Non-Volatile Address = 0x3F This value is the minimum RSSI that causes the module to wait for a clear channel when CSMA is enabled. Figure 61 shows examples of the commands. HumPRCTM Series Carrier Sense Minimum RSSI Read Command Header 0xFF Size 0x02 Write Command Header 0xFF Size 0x02 Escape Address 0xFE 0x3F Address Value 0x3F V Read Response ACK 0x06 Address Value 0x3F V Figure 61: HumPRCTM Series Transceiver Carrier Sense Minimum RSSI Command and Response The value is a negative number in twos complement from -128 (0x80) to -1
(0xff). The default value is -70dBm.
!
Warning: The CRSSI value can have a significant impact on the performance of the module. Setting it too low could prevent the module from ever transmitting. Setting it too high can result in transmission collisions. Care must be taken if this value is adjusted. Figure 59 shows the Device Serial Number registers. HumPRCTM Series DSN Registers Name MYDSN3 MYDSN2 MYDSN1 MYDSN0 Non-Volatile Address Description 0x34 0x35 0x36 0x37 MSB of the serial number Byte 2 of the serial number Byte 1 of the serial number LSB of the serial number Figure 59: HumPRCTM Series DSN Registers CUSTID - Customer ID Non-Volatile Address = 0x39-0x3A These registers contain the factory-programmed customer ID. A unique value is assigned to a specific customer and that value is programmed into that customers modules. The unencrypted User and Extended User Addressing modes use these bytes as part of the addressing. The unique value ensures that the custom modules will not communicate with any other systems. Contact Linx for details. Figure 60 shows the Customer ID registers. HumPRCTM Series Customer ID Registers Name CUSTID1 CUSTID0 Non-Volatile Address Description 0x39 0x3A MSB of the customer ID LSB of the customer ID Figure 60: HumPRCTM Series Transceiver Customer ID Registers 60 61 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 Read Command Header 0xFF Size 0x02 Escape Address 0xFE 0x78 Read Response ACK 0x06 Address Value 0x78 V Figure 62: HumPRCTM Series Transceiver Release Number Command and Response 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. Figure 64 shows examples of the commands. HumPRCTM Series RC Status Line States Read Command Header 0xFF Size 0x02 Escape Address 0xFE 0x7A Read Response ACK 0x06 Address Value 0x7A V HumPRCTM Series Release Number Register Settings Figure 64: HumPRCTM Series Transceiver RC Status Line States Command and Response V 0x24 0x25 Release Number HUM-868-PRC HUM-900-PRC Figure 63: HumPRCTM Series Transceiver Release Number Register Settings A more detailed firmware version is available for versions 0x20 and above in the FWVER register. 62 63 FWVER - Firmware Version Non-Volatile Address = 0xC0 - 0xC3 These read-only registers contain the firmware version number currently on the module. Each byte is a hexadecimal value: 12 03 01 00 indicates version 18.3.1.0. Each register byte is read separately. Figure 67 shows the Firmware Version registers. HumPRCTM Series Firmware Version Registers Name FWVER3 FWVER2 FWVER1 FWVER0 Non-Volatile Address Description 0xC0 0xC1 0xC2 0xC3 Major version number Minor version number Incremental version number Suffix Figure 67: HumPRCTM Series Firmware Version Registers 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. HumPRCTM Series Last Good Packet RSSI Read Command Header 0xFF Size 0x02 Escape Address 0xFE 0x7B Read Response ACK 0x06 Address Value 0x7B V Figure 65: HumPRCTM Series Transceiver Last Good Packet RSSI Command and Response ARSSI - Ambient RSSI Volatile Address = 0x7C This register returns the ambient receive signal strength on the current channel in dBm. The signal strength is measured as soon as the command is received. The register value is an 8-bit signed integer representing the RSSI in dBm. It is accurate to 3dB at the high RF data rate, and +3 to
-20 dB at the low RF data rate. The channel being read may be any of the channels in the selected hopping sequence. HumPRCTM Series Ambient RSSI Read Command Header 0xFF Size 0x02 Escape Address 0xFE 0x7C Read Response ACK 0x06 Address Value 0x7C V Figure 66: HumPRCTM Series Transceiver Ambient RSSI Command and Response 64 65 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 modules operation can become unpredictable. LSTATUS - Output Line Status Volatile Address = 0xC6 This register contains the logic states of the HumPROTM indicator lines. Many of these status lines are not connected to an external line in the HumPRCTM Series, but this register shows their logical state. Please see the HumPROTM Series Data guide for a full description of these lines. HumPRCTM Series Non-Volatile Refresh Cycles Registers HumPRCTM Series Output Line Status Name NVCYCLE1 NVCYCLE0 Non-Volatile Address Description 0xC4 0xC5 MSB of the number of refresh cycles LSB of the number of refresh cycles Figure 68: HumPRCTM Series Non-Volatile Refresh Cycles Registers Between 8 and 150 non-volatile write operations can be made before a refresh cycle is necessary. Writing the registers from lowest to highest address maximizes the number of write operations per refresh cycle. It is recommended to write the desired default values to non-volatile memory and use the volatile registers for values that change frequently. These registers show the total number of refresh cycles that have occurred. This gives an indication of the remaining life expectancy of the memory. Figure 68 shows the Non-Volatile Refresh Cycles registers. Read Command Header 0xFF Size 0x03 Read Response Escape Escape Address 0xFE 0xFE 0x46 ACK 0x06 Address Value 0xC6 LSTATUS Figure 69: HumPRCTM Series Transceiver Output Line Status Command and Response Each bit in the byte that is returned by the read represents the logic state of one of the output indicator lines. Figure 70 shows which line each bit represents. HumPRCTM Series Output Line Status LSTATUS Values LSTATUS Bit Line Status 0 1 2 3 4 5 6 7 EX Exception, 1 = exception has occurred PA_EN PA Enable, 1 = the transmitter is active LNA_EN LNA Enable, 1 = the receiver is active CTS Clear To Send, undefined MODE_IND Mode Indicator, 1 = RF data transfer is active (TX or RX) BE Buffer Empty, 1 = UART buffer is empty ACK_OUT Acknowledgement Output, 1 = ACK was received Reserved, 0 Figure 70: HumPRCTM Series Output Line Status LSTATUS Values 66 67 CMD - Command Register Volatile Address = 0xC7 This volatile write-only register is used to issue special commands. HumPRCTM Series Command Register Write Command Header 0xFF Size Size Escape Address Value 0xFE 0x47 V Figure 71: HumPRCTM Series Transceiver Command Register Command and Response Value V is chosen from among the options in Figure 72. HumPRCTM Series CMD Values CMD Value Operation 0x10 0x11 0x12 0x13 JOINCTL Join Process Control WRKEY Write Key CLRKEY Clear Key RLDKEY Reload Key 0x20 0xAA 0xBB NVRESET Reset non-volatile registers to factory default Figure 72: HumPRCTM Series Command Register Values The Join Process Control command allows the software to initiate or stop the secure Join process. It has the following subcommands. HumPRCTM Series JOINCTL Subcommand Values Subcommand Value Operation 0 1 2 Halt Join Process Generate a random network key and address. This sets the module as the network administrator (SECOPT:KEYRCV=0) Perform the Join Process with another module Figure 73: HumPRCTM Series JOINCTL Subcommand Values These operations are equivalent to the push-button initiated operation. If the Join Process is started by the serial command (CMD:JOINCTL[2]), push-button operation is ignored until the Join Process finishes. Register write operations are inhibited when a Join Process is active except that a Halt Join command is never inhibited. A Halt Join operation completes before the ACK is sent. 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. The Write Key command writes a 16-byte AES key to the selected key register. As with most of the registers, the encryption key has both volatile and non-volatile registers. The volatile register is used during run time, but is lost on a power cycle or reset. When the module powers up, the volatile register is loaded from the non-volatile register. This makes the non-volatile register value the default on power-up. The key value of all zero bytes is reserved as a no key indication. Figure 74 shows the command for writing the AES key to the module. If KeyN is 0x01, the command writes to the volatile key register. If it is 0x02, HumPRCTM Series Write Key Command Write Command Header 0xFF Size Size Escape Address 0xFE 0x47 Value 0x11 KeyN KeyN Key0 Key0
... .. Key15 Key15 Figure 74: HumPRCTM Series Transceiver Write Key Command it writes to the non-volatile key register. The Clear Key command sets the selected key to all zeros. Figure 75 shows the structure of this command. If KeyN is 0x01, the command clears the volatile key registers. If it is 0x02, HumPRCTM Series Clear Key Command Write Command Header 0xFF Size 0x04 Escape Address 0xFE 0x47 Value 0x12 KeyN KeyN Figure 75: HumPRCTM Series Transceiver Clear Key Command it clears the non-volatile key registers. The Reload Key command copies the key in non-volatile memory (NKN) 68 69 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. This reset can also be done by toggling the PB line as described in the Restore Factory Defaults section. SECSTAT - Security Status Volatile Address = 0xC9 This volatile read-only register provides status of the security features. The command returns a single byte. Figure 77 shows the meanings of the HumPRCTM Series Security Status Read Command Header 0xFF Size 0x03 Escape Escape Address 0xFE 0xFE 0x49 ACK 0x06 Address Value 0xC9 V Read Response Figure 76: HumPRCTM Series Transceiver Security Status Command and Response bits in the returned value byte. HumPRCTM Series Security Status Value Bit 0 1 2 3 4 5 6 7 Status Reserved 0 = No volatile key is set 1 = A volatile key is set 0 = No non-volatile key is set 1 = A non-volatile key is set Reserved Reserved Reserved Reserved Reserved 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. HumPRCTM Series Join Status Read Command Header 0xFF Size 0x03 Escape Escape Address 0xFE 0xFE 0x4A Read Response ACK 0x06 Address Value 0xCA V Figure 78: HumPRCTM Series Transceiver Join Status Command and Response The command returns a single byte. Figure shows the meanings of the returned value byte. HumPRCTM Series Join Status Value Bit Status Last Join Result (decimal):
Last Operation Successful 0x00: Module unpaired since restart 0x01: New key generated 0x02: Successfully sent address to another unit 0x03: Successfully sent address and key to another unit 0x04: Successfully obtained key from administrator 0x05: Successfully obtained address from administrator 0x06: Successfully obtained key and address from administrator 0x07: New address generated without key 0x08: New key generated without address 0 - 5 Last Operation Failed 0x0A: Fail: operation canceled 0x0B: Fail: timeout 0x0C: Fail: Invalid Generate Key and Address request 0x0D: Fail: Assignment message didnt contain key 0x0E: Fail: Administrator has no key to send when SECOPT:PSHARE=1 0x0F: Fail: Administrator has no address to send 0x10: Fail: Inconsistent Network Address Registers USRC, UMASK, LASTNETAD 0x11: Fail: LASTNETAD overflow 0x12: Fail: GET_KEY key and address change disabled. Current Operation 0x20: Detecting PB sequence 0x21: Waiting for joining unit 0x22: Another joining unit detected. Joining is in progress. 6
+0x40: JOINACT MODE_IND is active with pairing status, serial write operations are inhibited Figure 77: HumPRCTM Series Security Status Values 70 Figure 79: HumPRCTM Series Transceiver Join Status Value 71 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 Name EEXFLAG2 EEXFLAG1 EEXFLAG0 Volatile Address Description 0xCD 0xCE 0xCF Byte 2 of the extended exception flags Byte 1 of the extended exception flags LSB of the extended exception flags Figure 80: HumPRCTM Series Transceiver Extended Exception Code Registers When an exception occurs, the associated bit is set in this register. If the corresponding bit in the EEXMASK is set and EXMASK is zero, the EX status line is set. Reading an EEXFLAG register does not clear the register. Writing to an EEXFLAG register causes the register to be set to the BIT_AND(current_value, new_value). This provides a way of clearing bits that have been serviced without clearing a bit that has been set since the flag register was read. This prevents a loss of notification of an exception. Register bits can only be cleared, not set, from the write command though some flags are also cleared internally. Unless otherwise noted, exceptions are cleared by writing a zero to the corresponding register bit. Flag EX_TXDONE is set when a data packet has been transmitted. If the packet was sent with acknowledgement enabled, this flag indicates that the acknowledgment has also been received. Flag EX_RXWAIT is 1 when there are buffered incoming data bytes which have not been sent to the UART. It is cleared automatically by the HumPRCTM application. Flag EX_UNENCRYPT is 1 when a received packet is not encrypted. This can only occur when SECOPT:EN_UNC=1. Flag EX_SEQDEC is 1 when a received encrypted packet has a smaller sequence number than the previously received packet. Possible causes are an attempt to replay a previous message by an attacker, receiving a message from a different transmitter or restarting the transmitter. 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. Possible causes are an attempt to replay a previous message by an attacker, receiving a message from a different transmitter or restarting the transmitter. HumPRCTM Series Transceiver Extended Exception Codes Bit Exception Name Description EEXFLAG0 (0xCF) 0 1 2 3 4 5 6 7 EX_BUFOVFL EX_RFOVFL Internal UART buffer overflowed. Internal RF packet buffer overflowed. EX_WRITEREGFAILED Attempted write to register failed. EX_NORFACK Acknowledgement packet not received after maximum number of retries. EX_BADCRC Bad CRC detected on incoming packet. EX_BADHEADER Bad CRC detected in packet header. EX_BADSEQID Sequence ID was incorrect in ACK packet. EX_BADFRAMETYPE Unsupported frame type specified. EEXFLAG1 (0xCE) 0 1 2 3 4 5 EX_TXDONE EX_RXWAIT EX_UNENCRYPT EX_SEQDEC EX_SEQSKIP EX_JOIN 6 - 7 Reserved EEXFLAG2 (0xCD) 0 - 7 Reserved A data packet has been transmitted. Received data bytes are waiting to be read. Received packet was not encrypted. This can only occur when SECOPT: EN_UNENC=1. Received encrypted packet sequence number is less than previous. Received encrypted sequence number is more than one higher the previous sequence number. The Join Process has been started, which can result in register changes and write lockouts. Figure 81: HumPRCTM Series Transceiver Extended Exception Codes 72 73 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. It is initially set to the administrator address when a network key is generated. HumPRCTM Series Extended Exception Mask Registers Name Non-Volatile Address Description LASTNETAD3 LASTNETAD2 LASTNETAD1 LASTNETAD0 0x8C 0x8D 0x8E 0x8F MSB of the last network address assigned Byte 2 of the last network address assigned Byte 1 of the last network address assigned LSB of the last network address assigned Figure 83: HumPRCTM Series Transceiver Extended Exception Mask Registers 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 Name EEXMASK2 EEXMASK1 EEXMASK0 Volatile Address Non-Volatile Address Description 0xD0 0xD1 0xD2 0x80 0x81 0x82 Byte 2 of the extended exception mask Byte 1 of the extended exception mask Byte 0 of the extended exception mask Figure 82: HumPRCTM Series Transceiver Extended Exception Mask Registers To use this value, register EXMASK must be zero. If EXMASK is non-zero, this register has no effect on the EX line. When an exception bit is set in EEXFLAG, the corresponding EEXMASK bit is set, and EXMASK is zero, the EX status line is set, otherwise the EX line is reset. Mask bits for unassigned flags should be zero for future compatibility. PKTOPT - Packet Options Volatile Address = 0xD3; Non-Volatile Address = 0x83 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. 74 75 SECOPT - Security Options Volatile Address = 0xD4; Non-Volatile Address = 0x84 This register selects options for security features. HumPRCTM Series Security Options Read Command Read Response Header Size Escape Escape Address ACK Address Value 0xFF 0x03 0xFE 0xFE 0x54 0x04 0x06 0xD4 0x84 V Write Command Header Size Escape Address Value 0xFF 0x03 0xFE 0x54 0x04 V Figure 84: HumPRCTM Series Transceiver Packet Options Command and Response Each bit in the register sets an option as shown in Figure 85. Unlike other registers, the non-volatile register (0x84) affects all Join operations. The EN_UNENC bit in the volatile register affects data packet reception. HumPRCTM Series Transceiver Security Option Codes Bit Name Description 0 1 2 3 4 5 6 7 PB_RESET Permit factory reset from PB input sequence PSHARE PGKEY Permit key sharing Permit clearing key and changing key CHGADDR Permit changing an address KEYRCV 1: Receive key and address during Join Process (node) 0: Send key and address during Join Process (admin) EN_UNENC Enable receiving unencrypted packets Reserved Reserved (must be 1) EN_CHANGE Enable changes to security options Figure 85: HumPRCTM Series Transceiver Security Option Codes When PB_RESET is 1 the Factory Reset function is enabled from the PB input. This allows a user to reset the module configurations back to the factory defaults with 4 short presses and a 3 second hold of a button connected to the PB input. When PSHARE is 1 the Share Network Key function is enabled during the Join Process. This allows an administrator to share the encryption key it created. When 0, a Join Process sends the network address, but no key. 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. 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. When KEYRCV is 1 the module is set to receive a network key from an administrator and act as a node. When it is 0, the module is set as an administrator and sends a network key and assigns an address to the node. In order for this bit to change from 1 to 0, both volatile and non-volatile copies of the network key must be cleared, preventing nodes from being manipulated to transmit the key. This bit is cleared by the GENERATE_KEY push-button function. When EN_UNENC is 1 the module accepts unencrypted packets. If this bit is 0, unencrypted received packets are ignored. When EN_CHANGE is 1, changes are permitted to the SECOPT register, except as noted for KEYRCV changes. Clearing this bit prohibits the following SECOPT changes to enhance security:
1. changing PSHARE from 0 to 1 2. changing EN_CHANGE from 0 to 1. 3. changing EN_UNENC from 0 to 1. An attempt to make a prohibited change causes a NACK command response. When EN_CHANGE is 0, these restrictions can only be removed by resetting the module configuration to the factory default. 76 77 Typical Applications The following steps describe how to use the HumPRCTM Series module with hardware only. 1. Set the C0 and C1 lines opposite on both sides. 2. Press and hold the PB button for 30s on the unit chosen as Administrator. When MODE_IND flashes, release PB. The unit is set as the Administrator. 3. Press the PB button on both sides. The MODE_IND LED begins flashing slowly to indicate that the module is searching for another module. 4. Once the pairing is complete, the MODE_IND LED flashes quickly to indicate that the pairing was successful. 5. The modules are now paired and ready for normal use. 6. Pressing a status line button on one module (the IU) activates the corresponding status line output on the second module (the RU). 7. Taking the ACK_EN line high on the RU causes the module to send an acknowledgement to the IU. The ACK_OUT line on the IU goes high to indicate that the acknowledgement has been received. Tying the line to Vcc causes the module to send an acknowledgement as soon as a command message is received. This is suitable for basic remote control or command systems. No programming is necessary for basic hardware operation. Basic application circuits for one-way remote control are shown in Figure 86. Circuits for bi-directional remote control are shown in Figure 87. VCC VCC VCC GND VCC GND 9 2 8 2 7 2 6 2 5 2 4 2 3 2 2 2 1 2 D N G N E _ A P N E _ A N L T E S E R C C V B P MODE_IND ACK_OUT GND N E _ K C A N I _ A T A D _ D M C T U O _ A T A D _ D M C S7 S6 S5 S4 3 S 2 S 1 S 0 S D N G 0 C 1 C N W O D _ R E W O P N E _ H C T A L 5 6 7 8 9 0 1 1 1 2 1 3 1 GND GND VCC GND ANT GND GND GND GND GND 20 19 18 17 16 15 14 GND GND GND GND GND GND VCC VCC VCC VCC VCC VCC VCC GND VCC GND 9 2 8 2 7 2 6 2 5 2 4 2 3 2 2 2 1 2 GND ANT GND GND GND GND GND 20 19 18 17 16 15 14 GND GND GND GND GND GND D N G N E _ A P N E _ A N L T E S E R C C V B P MODE_IND ACK_OUT GND N E _ K C A I N _ A T A D _ D M C T U O _ A T A D _ D M C S7 S6 S5 S4 3 S 2 S 1 S 0 S D N G 0 C 1 C N W O D _ R E W O P N E _ H C T A L 5 6 7 8 9 0 1 1 1 2 1 3 1 3 S 2 S 1 S 0 S GND VCC GND GND 30 31 32 1 2 3 4 30 31 32 1 2 3 4 S7 S6 S5 S4 GND GND VCC GND VCC VCC VCC VCC A GND GND VCC GND B 78 79 Figure 86: HumPRCTM Series Transceiver Basic Application Circuits for Remote Control VCC VCC VCC GND VCC GND 9 2 8 2 7 2 6 2 5 2 4 2 3 2 2 2 1 2 D N G N E _ A P N E _ A N L T E S E R C C V B P MODE_IND ACK_OUT GND N E _ K C A I N _ A T A D _ D M C T U O _ A T A D _ D M C S7 S6 S5 S4 3 S 2 S 1 S 0 S D N G 0 C 1 C N W O D _ R E W O P N E _ H C T A L 5 6 7 8 9 0 1 1 1 2 1 3 1 GND VCC GND VCC GND GND ANT GND GND GND GND GND 20 19 18 17 16 15 14 GND GND GND GND GND GND VCC VCC VCC VCC VCC VCC VCC GND VCC GND 9 2 8 2 7 2 6 2 5 2 4 2 3 2 2 2 1 2 D N G N E _ A P N E _ A N L T E S E R C C V B P MODE_IND ACK_OUT GND N E _ K C A I N _ A T A D _ D M C T U O _ A T A D _ D M C S7 S6 S5 S4 3 S 2 S 1 S 0 S D N G 0 C 1 C N W O D _ R E W O P N E _ H C T A L 5 6 7 8 9 0 1 1 1 2 1 3 1 3 S 2 S 1 S 0 S GND GND VCC VCC GND GND ANT GND GND GND GND GND 20 19 18 17 16 15 14 GND GND GND GND GND GND S7 S6 S5 S4 30 31 32 1 2 3 4 30 31 32 1 2 3 4 GND GND VCC GND A GND GND VCC GND VCC VCC VCC VCC B Figure 87: HumPRCTM Series Transceiver Basic Application Circuits for Bi-directional Remote Control Figure 88 shows a typical circuit using the HumPRCTM Series transceiver with an external microcontroller. RXD TXD GPIO GPIO GPIO GND GND VCC VCC VCC VCC VCC GND 30 31 32 1 2 3 4 GND VCC GND 9 2 8 2 7 2 6 2 5 2 4 2 3 2 2 2 1 2 D N G N E _ A P N E _ A N L T E S E R C C V B P MODE_IND ACK_OUT GND N E _ K C A I N _ A T A D _ D M C T U O _ A T A D _ D M C S7 S6 S5 S4 3 S 2 S 1 S 0 S D N G 0 C 1 C N W O D _ R E W O P N E _ H C T A L 5 6 7 8 9 0 1 1 1 2 1 3 1 3 S 2 S 1 S 0 S GND GND VCC GND GND ANT GND GND GND GND GND 20 19 18 17 16 15 14 GND GND GND GND GND GND Figure 88: HumPRCTM Series Transceiver Basic Application Circuit with a Microcontroller In this example, C0 is low and C1 is high, so S0S3 are outputs and S4S7 are inputs. The inputs are connected to buttons that pull the lines high. Internal pull-down resistors keep the lines from floating when the buttons are open. The outputs are connected to external application circuitry. LATCH_EN is low, so the outputs are momentary. ACK_OUT and MODE_IND are connected to LEDs to provide visual indication to the user. PB is connected to a button and pull-down resistor to initiate the Join Process when the button is pressed. In this circuit, the Command Data Interface is connected to a microcontroller for using some of the advanced features. The microcontroller controls the state of the ACK_EN line. It can receive a command, perform an action and then take the line high to send Acknowledgement packets. This lets the user on the other end know that the action took place and not just that the command was received. 80 81 HumPRCTM Series Long-Range Handheld Transmitter The HumPRCTM 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.8 mile) depending on the receiver antenna and operating environment. The transmitter is available in 868MHz and 900MHz for multi-region operation. The 868MHz version has been tested to European ETSI requirements and received its CE mark. The 900MHz version has been certified by the United States FCC and Industry Canada. This reduces development costs and time to market. 3 4 2 A 1 B D C FASCO ON ON ON ON OFF Lights ON OFF Pool ON OFF Spa ON The membrane switch array can be customized to have specific artwork, logos, colors, number of buttons (up to eight) and button positions. A one-time NRE is required to create the custom switch, but minimum order quantities can be as low as 200 pieces. Contact Linx for more information. Ordering Information Part Number Description OTX-***-HH-LR8-PRC HumPRCTM Long-Range Handheld Transmitter
*** = 868, 900MHz Figure 89: HumPRCTM Series Long-Range Handheld Transmitter Ordering Information Key Features R 5.08 mm
(0.20 in) 50.80 mm
(2.00 in) 34.29 mm
(1.35 in) 34.93 mm
(1.38 in) 71.37 mm
(2.81 in) S0 S1 S2 S3 S7 S6 S5 S4 41.15 mm
(1.62 in) 5.08 mm
(0.20 in) 15.24 mm
(0.60 in) Small Package Up to 8 buttons MODE_IND PAIR Button Join Process Pairing CR2032 Coin Cell Battery 82 83 Usage Guidelines for FCC Compliance 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. The integrator does not need to conduct any further intentional radiator testing under these rules provided that the following guidelines are met:
An approved antenna must be directly coupled to the modules U.FL connector through an approved coaxial extension cable or to the modules castellation pad using an approved reference design and PCB layer stack. Alternate antennas can be used, but may require the integrator to perform certification testing. The module must not be modified in any way. Coupling of external circuitry must not bypass the provided connectors. End product must be externally labeled with Contains FCC ID:
OJM900MCA / IC: 5840A-900MCA. The end products users manual must contain an FCC statement equivalent to that listed on page 85 of this data guide. The antenna used for this transceiver must not be co-located or operating in conjunction with any other antenna or transmitter. The integrator must not provide any information to the end-user on how to install or remove the module from the end-product. Any changes or modifications not expressly approved by Linx Technologies could void the users authority to operate the equipment. Additional Testing Requirements The HUM-900-PRC-UFL and HUM-900-PRC-CAS have been tested for compliance as an intentional radiator, but the integrator is required to perform unintentional radiator testing on the final product per FCC sections 15.107 and 15.109 and Industry Canada license-exempt RSS standards. Additional product-specific testing might be required. Please contact the FCC or Industry Canada regarding regulatory requirements for the application. Ultimately is it the integrators responsibility to show that their product complies with the regulations applicable to their product. Versions other than the -UFL and -CAS have not been tested and require full compliance testing in the end product as it will go to market. Information to the User The following information must be included in the products user manual. FCC / IC NOTICES This product contains FCC ID: OJM900MCA / IC: 5840A-900MCA. This device complies with Part 15 of the FCC rules and Industry Canada license-exempt RSS standards. Operation of this device is subject to the following two conditions:
1. This device may not cause harmful interference, and 2. this device must accept any interference received, including interference that may cause undesired operation. This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses and can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio communications. However, there is no guarantee that interference will not occur in a particular installation. If this equipment does cause harmful interference to radio or television reception, which can be determined by turning the equipment off and on, the user is encouraged to try to correct the interference by one or more of the following measures:
Reorient or relocate the receiving antenna. Connect the equipment into an outlet on a circuit different from that to which Increase the separation between the equipment and receiver. the receiver is connected. Consult the dealer or an experienced radio/TV technician for help. Any modifications could void the users authority to operate the equipment. Le prsent appareil est conforme aux CNR dIndustrie Canada applicables aux appareils radio exempts de licence. Lexploitation est autorise aux deux conditions suivantes:
1. 2. lappareil ne doit pas produire de brouillage, et utilisateur de lappareil doit accepter tout brouillage radiolectrique subi, mme si le brouillage est susceptible den compromettre le fonctionnement. 84 85 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. Permanently affixed means that the label is etched, engraved, stamped, silkscreened, indelibly printed, or otherwise permanently marked on a permanently attached part of the equipment or on a nameplate of metal, plastic, or other material fastened to the equipment by welding, riveting, or a permanent adhesive. The label must be designed to last the expected lifetime of the equipment in the environment in which the equipment may be operated and must not be readily detachable. FCC RF Exposure Statement To satisfy RF exposure requirements, this device and its antenna must not be co-located or operating in conjunction with any other antenna or transmitter. Antenna Selection Under FCC and Industry Canada regulations, the HUM-900-PRC-UFL and HUM-900-PRC-CAS radio transmitters may only operate using an antenna of a type and maximum (or lesser) gain approved for the transmitter by the FCC and Industry Canada. To reduce potential radio interference to other users, the antenna type and its gain should be so chosen that the equivalent isotropically radiated power (e.i.r.p.) is not more than that necessary for successful communication. The HUM-900-PRC-UFL and HUM-900-PRC-CAS radio transmitters have been approved by the FCC and Industry Canada to operate with the antenna types listed in Figure 90 with the maximum permissible gain and required antenna impedance for each antenna type indicated. Antenna types not included in this list, having a gain greater than the maximum gain indicated for that type, are strictly prohibited for use with this device. Conformment la rglementation dIndustrie Canada, le prsent metteur radio peut fonctionner avec une antenne dun type et dun gain maximal
(ou infrieur) approuv pour lmetteur par Industrie Canada. Dans le but de rduire les risques de brouillage radiolectrique lintention des autres utilisateurs, il faut choisir le type dantenne et son gain de sorte que la puissance isotrope rayonne quivalente (p.i.r.e.) ne dpasse pas lintensit ncessaire ltablissement dune communication satisfaisante. Le prsent metteur radio (HUM-900-PRC-UFL, HUM-900-PRC-CAS) a t approuv par Industrie Canada pour fonctionner avec les types dantenne numrs la Figure 90 et ayant un gain admissible maximal et limpdance requise pour chaque type dantenne. Les types dantenne non inclus dans cette liste, ou dont le gain est suprieur au gain maximal indiqu, sont strictement interdits pour lexploitation de lmetteur. Antennas / Antennes Linx Part Number Rfrence Linx Tested Antennas Type Gain Impedance Impdance Valid For ANT-916-CW-QW Wave Whip ANT-916-CW-HW Wave Dipole Helical ANT-916-PW-LP Wave Whip ANT-916-PW-QW-UFL Wave Whip ANT-916-SP Wave Planar 1.8dBi 1.2dBi 2.4dBi 1.8dBi 1.4dBi ANT-916-WRT-RPS ANT-916-WRT-UFL Wave Dipole Helical 0.1dBi Antennas of the same type and same or lesser gain ANT-916-CW-HD ANT-916-PW-QW ANT-916-CW-RCL ANT-916-CW-RH Wave Whip Wave Whip Wave Whip Wave Whip 0.3dBi 1.8dBi 2.0dBi 1.3dBi ANT-916-CW-HWR-RPS Wave Dipole Helical 1.2dBi ANT-916-PML Wave Dipole Helical 0.4dBi ANT-916-PW-RA Wave Whip ANT-916-USP Cable Assemblies / Assemblages de Cbles Wave Planar 0.0dBi 0.3dBi 50 50 50 50 50 50 50 50 50 50 50 50 50 50 CAS Both CAS UFL CAS CAS UFL Both Both Both Both Both Both CAS CAS Linx Part Number Rfrence Linx Description CSI-RSFB-300-UFFR*
RP-SMA Bulkhead to U.FL with 300mm cable CSI-RSFE-300-UFFR*
RP-SMA External Mount Bulkhead to U.FL with 300mm cable
* Also available in 100mm and 200mm cable length Figure 90: HumPRCTM Series Transceiver Approved Antennas 86 87 Castellation Version Reference Design The castellation connection for the antenna on the pre-certified version allows the use of embedded antennas as well as removes the cost of a cable assembly for the U.FL connector. However, the PCB design and layer stack must follow one of the reference designs for the certification on the HUM-900-PRC-CAS to be valid. Figure 91 shows the PCB layer stack that should be used. Figure 92 shows the layout and routing designs for the different antenna options. Please see the antenna data sheets for specific ground plane counterpoise requirements. Layer Name Top Layer Dielectric 1 Mid-Layer 1 Thickness Material Copper 1.4mil FR-4 (Er = 4.6) 14.00mil Copper 1.4mil Dielectric 2 28.00mil FR-4 (Er = 4.6) Mid-Layer 2 Dielectric 3 Bottom Layer 1.4mil 14.00mil 1.4mil Copper FR-4 (Er = 4.6) Copper Figure 91: HumPRCTM Series Transceiver Castellation Version Reference Design PCB Stack Note: The PCB design and layer stack for the HUM-900-PRC-CAS must follow these reference designs for the pre-certification to be valid. The HUM-900-PRC-UFL and the HUM-900-PRC-CAS must use one of the antennas in Figure 108 in order for the certification to be valid. The HUM-900-PRC has not been tested and requires full compliance testing in the end product as it will go to market. All modules require unintentional radiator compliance testing in the end product as it will go to market. 1 6 3 5 3 5 3 2 7
. 2 6 0 3 0 0 A M S V E R N O C 0 2 3 9 1 6 0 0 2 5 6 1 5 6 1 0 7 4 0 3 2 0 4 1 0 3 2 P L
-
W P
-
6 1 9
-
T N A
-
A R W P
-
6 1 9
-
T N A 6 1 2 0 8 3 P S
-
6 1 9
-
T N A S P R
-
T R W
-
6 1 9
-
T N A
-
W Q W C
-
6 1 9
-
T N A
-
W H W C
-
6 1 9
-
T N A 1 l i i t m 4 2
=
h d W p i r t s o r c M i r e y a L
-
d M n o i e n a p l d n u o r G s l i m n i e r a s t i n U 88 89 Figure 92: HumPRCTM Series Transceiver Castellation Version Reference Design Power Supply Requirements 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 modules performance, so providing a clean power supply for the module should be a high priority during design. 10 Vcc IN Vcc TO MODULE
+
10F Figure 93: Supply Filter A 10 resistor in series with the supply followed by a 10F tantalum capacitor from Vcc to ground helps in cases where the quality of supply power is poor (Figure 93). This filter should be placed close to the modules supply lines. These values may need to be adjusted depending on the noise present on the supply line. Antenna Considerations The choice of antennas is a critical and often overlooked design consideration. The range, performance and legality of an RF link are critically dependent upon the antenna. While adequate antenna performance can often be obtained by trial and error methods, antenna design and matching is a complex task. Professionally designed antennas such as those from Linx (Figure 94) help ensure maximum performance and FCC and other regulatory compliance. Figure 94: Linx Antennas Linx transmitter modules typically have an output power that is higher than the legal limits. This allows the designer to use an inefficient antenna such as a loop trace or helical to meet size, cost or cosmetic requirements and still achieve full legal output power for maximum range. If an efficient antenna is used, then some attenuation of the output power will likely be needed. It is usually best to utilize a basic quarter-wave whip until your prototype product is operating satisfactorily. Other antennas can then be evaluated based on the cost, size and cosmetic requirements of the product. Additional details are in Application Note AN-00500. Interference Considerations The RF spectrum is crowded and the potential for conflict with unwanted sources of RF is very real. While all RF products are at risk from interference, its effects can be minimized by better understanding its characteristics. Interference may come from internal or external sources. The first step is to eliminate interference from noise sources on the board. This means paying careful attention to layout, grounding, filtering and bypassing in order to eliminate all radiated and conducted interference paths. For many products, this is straightforward; however, products containing components such as switching power supplies, motors, crystals and other potential sources of noise must be approached with care. Comparing your own design with a Linx evaluation board can help to determine if and at what level design-specific interference is present. External interference can manifest itself in a variety of ways. Low-level interference produces noise and hashing on the output and reduces the links overall range. High-level interference is caused by nearby products sharing the same frequency or from near-band high-power devices. It can even come from your own products if more than one transmitter is active in the same area. It is important to remember that only one transmitter at a time can occupy a frequency, regardless of the coding of the transmitted signal. This type of interference is less common than those mentioned previously, but in severe cases it can prevent all useful function of the affected device. Although technically not interference, multipath is also a factor to be understood. Multipath is a term used to refer to the signal cancellation effects that occur when RF waves arrive at the receiver in different phase relationships. This effect is a particularly significant factor in interior environments where objects provide many different signal reflection paths. Multipath cancellation results in lowered signal levels at the receiver and shorter useful distances for the link. 90 91 Pad Layout 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. 0.520"
0.015"
0.420"
0.015"
0.028"
0.050"
0.070"
Figure 95: HUM-***-PRC Recommended PCB Layout 0.015"
0.060"
0.100"
0.101"
0.136"
0.090"
0.015"
0.028"
0.065"
0.060"
0.420"
0.015"
0.050"
0.070"
Figure 96: HUM-***-PRC-UFL/CAS Recommended PCB Layout Microstrip Details 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 modules antenna can effectively contribute to the length of the antenna, changing its resonant bandwidth. In order to minimize loss and detuning, some form of transmission line between the antenna and the module should be used unless the antenna can be placed very close (<18in) to the module. One common form of transmission line is a coax cable and another is the microstrip. This term refers to a PCB trace running over a ground plane that is designed to serve as a transmission line between the module and the antenna. The width is based on the desired characteristic impedance of the line, the thickness of the PCB and the dielectric constant of the board material. For standard 0.062in thick FR-4 board material, the trace width would be 111 mils. The correct trace width can be calculated for other widths and materials using the information in Figure 97 and examples are provided in Figure 98. Software for calculating microstrip lines is also available on the Linx website. Trace Board Ground plane Figure 97: Microstrip Formulas Example Microstrip Calculations Dielectric Constant Width / Height Ratio (W / d) Effective Dielectric Constant Characteristic Impedance () 4.80 4.00 2.55 1.8 2.0 3.0 3.59 3.07 2.12 50.0 51.0 48.8 92 93 Figure 98: Example Microstrip Calculations Board Layout Guidelines The modules 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 modules 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 following section provides some basic design guidelines. During prototyping, the module should be soldered to a properly laid-out circuit board. The use of prototyping or perf boards results in poor performance and is strongly discouraged. Likewise, the use of sockets can have a negative impact on the performance of the module and is discouraged. The module should, as much as reasonably possible, be isolated from other components on your PCB, especially high-frequency circuitry such as crystal oscillators, switching power supplies, and high-speed bus lines. When possible, separate RF and digital circuits into different PCB regions. Make sure internal wiring is routed away from the module and antenna and is secured to prevent displacement. Do not route PCB traces directly under the module. There should not be any copper or traces under the module on the same layer as the module, just bare PCB. The underside of the module has traces and vias that could short or couple to traces on the products circuit board. The Pad Layout section shows a typical PCB footprint for the module. A ground plane (as large and uninterrupted as possible) should be placed on a lower layer of your PC board opposite the module. This plane is essential for creating a low impedance return for ground and consistent stripline performance. Use care in routing the RF trace between the module and the antenna or connector. Keep the trace as short as possible. Do not pass it under the module or any other component. Do not route the antenna trace on multiple PCB layers as vias add inductance. Vias are acceptable for tying together ground layers and component grounds and should be used in multiples. The -CAS version must follow the layout in Figure 92. Each of the modules ground pins should have short traces tying immediately to the ground plane through a via. Bypass caps should be low ESR ceramic types and located directly adjacent to the pin they are serving. A 50-ohm coax should be used for connection to an external antenna. A 50-ohm transmission line, such as a microstrip, stripline or coplanar waveguide should be used for routing RF on the PCB. The Microstrip Details section provides additional information. In some instances, a designer may wish to encapsulate or pot the product. There are a wide variety of potting compounds with varying dielectric properties. Since such compounds can considerably impact RF performance and the ability to rework or service the product, it is the responsibility of the designer to evaluate and qualify the impact and suitability of such materials. Helpful Application Notes from Linx It is not the intention of this manual to address in depth many of the issues that should be considered to ensure that the modules function correctly and deliver the maximum possible performance. We recommend reading the application notes listed in Figure 99 which address in depth key areas of RF design and application of Linx products. These applications notes are available online at www.linxtechnologies.com or by contacting the Linx literature department. Helpful Application Note Titles Note Number Note Title AN-00100 AN-00126 AN-00130 AN-00140 AN-00500 AN-00501 RF 101: Information for the RF Challenged Considerations for Operation Within the 902928MHz Band Modulation Techniques for Low-Cost RF Data Links The FCC Road: Part 15 from Concept to Approval Antennas: Design, Application, Performance Understanding Antenna Specifications and Operation Figure 99: Helpful Application Note Titles 94 95 Production Guidelines 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. Soldering Iron Tip Hand Assembly Pads located on the bottom of the module are the primary mounting surface (Figure 100). Since these pads are inaccessible during mounting, castellations that run up the side of the module have been provided to facilitate solder wicking to the modules underside. This allows for very quick hand soldering for prototyping and small volume production. If the recommended pad guidelines have been followed, the pads will protrude slightly past the edge of the module. Use a fine soldering tip to heat the board pad and the castellation, then introduce solder to the pad at the modules edge. The solder will wick underneath the module, providing reliable attachment. Tack one module corner first and then work around the device, taking care not to exceed the times in Figure 101. Solder PCB Pads Castellations Figure 100: Soldering Technique Warning: Pay attention to the absolute maximum solder times. Absolute Maximum Solder Times Hand Solder Temperature: +427C for 10 seconds for lead-free alloys Reflow Oven: +255C max (see Figure 102) Figure 101: Absolute Maximum Solder Times Automated Assembly For high-volume assembly, the modules are generally auto-placed. The modules have been designed to maintain compatibility with reflow processing techniques; however, due to their hybrid nature, certain aspects of the assembly process are far more critical than for other component types. Following are brief discussions of the three primary areas where caution must be observed. Reflow Temperature Profile The single most critical stage in the automated assembly process is the reflow stage. The reflow profile in Figure 102 should not be exceeded because excessive temperatures or transport times during reflow will irreparably damage the modules. Assembly personnel need to pay careful attention to the ovens profile to ensure that it meets the requirements necessary to successfully reflow all components while still remaining within the limits mandated by the modules. The figure below shows the recommended reflow oven profile for the modules. Recommended RoHS Profile Max RoHS Profile Recommended Non-RoHS Profile 255C 235C 217C 185C 180C 125C 300 250 200 150 100 50
) C o
(
t e r u a r e p m e T 0 30 60 90 120 150 180 210 240 270 300 330 360 Time (Seconds) Figure 102: Maximum Reflow Temperature Profile Shock During Reflow Transport Since some internal module components may reflow along with the components placed on the board being assembled, it is imperative that the modules not be subjected to shock or vibration during the time solder is liquid. Should a shock be applied, some internal components could be lifted from their pads, causing the module to not function properly. Washability The modules are wash-resistant, but are not hermetically sealed. Linx recommends wash-free manufacturing; however, the modules can be subjected to a wash cycle provided that a drying time is allowed prior to applying electrical power to the modules. The drying time should be sufficient to allow any moisture that may have migrated into the module to evaporate, thus eliminating the potential for shorting damage during power-up or testing. If the wash contains contaminants, the performance may be adversely affected, even after drying. 96 97 General Antenna Rules The following general rules should help in maximizing antenna performance. 1. Proximity to objects such as a users 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). In many cases, this isnt desirable for practical or ergonomic reasons, thus, an alternative antenna style such as a helical, loop or patch may be utilized and the corresponding sacrifice in performance accepted. plane as possible in proximity to the base of the antenna. In cases where the antenna is remotely located or the antenna is not in close proximity to a circuit board, ground plane or grounded metal case, a metal plate may be used to maximize the antennas performance. 5. Remove the antenna as far as possible from potential interference sources. Any frequency of sufficient amplitude to enter the receivers front end will reduce system range and can even prevent reception entirely. Switching power supplies, oscillators or even relays can also be significant sources of potential interference. The single best weapon against such problems is attention to placement and layout. Filter the modules power supply with a high-frequency bypass capacitor. Place adequate ground plane under potential sources of noise to shunt noise to ground and prevent it from coupling to the RF stage. Shield noisy board areas whenever practical. 3. 4. OPTIMUM USABLE NOT RECOMMENDED Figure 103: Ground Plane Orientation 6. CASE If an internal antenna is to be used, keep it away from other metal components, particularly large items like transformers, batteries, PCB tracks and ground planes. In many cases, the space around the antenna is as important as the antenna itself. Objects in close proximity to the antenna can cause direct detuning, while those farther away will alter the antennas symmetry. GROUND PLANE
(MAY BE NEEDED) NUT ANTENNA (MARCONI) VERTICAL /4 GROUNDED In many antenna designs, particularly -wave whips, the ground plane acts as a counterpoise, forming, in essence, a -wave dipole (Figure 104). For this reason, adequate ground plane area is essential. The ground plane can be a metal case or ground-fill areas on a circuit board. Ideally, it should have a surface area less than or equal to the overall length of the -wave radiating element. This is often not practical due to size and configuration constraints. In these instances, a designer must make the best use of the area available to create as much ground GROUND PLANE VIRTUAL /4 DIPOLE DIPOLE ELEMENT
/4
/4 E I In some applications, it is advantageous to place the module and antenna away from the main equipment (Figure 105). This can avoid interference problems and allows the antenna to be oriented for optimum performance. Always use 50 coax, like RG-174, for the remote feed. NOT RECOMMENDED OPTIMUM USABLE CASE GROUND PLANE
(MAY BE NEEDED) NUT Figure 105: Remote Ground Plane Figure 104: Dipole Antenna 98 99 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. A low-cost whip can be easily fabricated from a wire or rod, but most designers opt for the consistent performance and cosmetic appeal of a professionally-made model. To meet this need, Linx offers a wide variety of straight and reduced height whip style antennas in permanent and connectorized mounting styles. Figure 106: Whip Style Antennas L =
234 FMHz The wavelength of the operational frequency determines an antennas overall length. Since a full wavelength is often quite long, a partial - or -wave antenna is normally employed. Its size and natural radiation resistance make it well matched to Linx modules. The proper length for a straight -wave can be easily determined using the formula in Figure 107. It is also possible to reduce the overall height of the antenna by using a helical winding. This reduces the antennas bandwidth but is a great way to minimize the antennas physical size for compact applications. This also means that the physical appearance is not always an indicator of the antennas frequency. Figure 107:
L = length in feet of quarter-wave length F = operating frequency in megahertz Loop Style A loop or trace style antenna is normally printed directly on a products PCB (Figure 109). This makes it the most cost-effective of antenna styles. The element can be made self-resonant or externally resonated with discrete components, but its actual layout is usually product specific. Despite the cost advantages, loop style antennas are generally inefficient and useful only for short range applications. They are also very sensitive to changes in layout and PCB dielectric, which can cause consistency issues during production. In addition, printed styles are difficult to engineer, requiring the use of expensive equipment including a network analyzer. An improperly designed loop will have a high VSWR at the desired frequency which can cause instability in the RF stage. Figure 109: Loop or Trace Antenna Linx offers low-cost planar (Figure 110) and chip antennas that mount directly to a products PCB. These tiny antennas do not require testing and provide excellent performance despite their small size. They offer a preferable alternative to the often problematic printed antenna. Figure 110: SP Series Splatch and uSP MicroSplatch Antennas Specialty Styles Linx offers a wide variety of specialized antenna styles (Figure 108). Many of these styles utilize helical elements to reduce the overall antenna size while maintaining reasonable performance. A helical antennas bandwidth is often quite narrow and the antenna can detune in proximity to other objects, so care must be exercised in layout and placement. Figure 108: Specialty Style Antennas 100 101 Questions regarding interpretations of the Part 2 and Part 15 rules or the measurement procedures used to test intentional radiators such as Linx RF modules for compliance with the technical standards of Part 15 should be addressed to:
Federal Communications Commission Equipment Authorization Division Customer Service Branch, MS 1300F2 7435 Oakland Mills Road Columbia, MD, US 21046 Phone: + 1 301 725 585 | Fax: + 1 301 344 2050 Email: labinfo@fcc.gov International approvals are slightly more complex, although Linx modules are designed to allow all international standards to be met. If the end product is to be exported to other countries, contact Linx to determine the specific suitability of the module to the application. All Linx modules are designed with the approval process in mind and thus much of the frustration that is typically experienced with a discrete design is eliminated. Approval is still dependent on many factors, such as the choice of antennas, correct use of the frequency selected and physical packaging. While some extra cost and design effort are required to address these issues, the additional usefulness and profitability added to a product by RF makes the effort more than worthwhile. 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. When working with RF, a clear distinction must be made between what is technically possible and what is legally acceptable in the country where operation is intended. Many manufacturers have avoided incorporating RF into their products as a result of uncertainty and even fear of the approval and certification process. Here at Linx, our desire is not only to expedite the design process, but also to assist you in achieving a clear idea of what is involved in obtaining the necessary approvals to legally market a completed product. For information about regulatory approval, read AN-00142 on the Linx website or call Linx. Linx designs products with worldwide regulatory approval in mind. In the United States, the approval process is actually quite straightforward. The regulations governing RF devices and the enforcement of them are the responsibility of the Federal Communications Commission (FCC). The regulations are contained in Title 47 of the United States Code of Federal Regulations (CFR). Title 47 is made up of numerous volumes; however, all regulations applicable to this module are contained in Volume 0-19. It is strongly recommended that a copy be obtained from the FCCs website, the Government Printing Office in Washington or from your local government bookstore. Excerpts of applicable sections are included with Linx evaluation kits or may be obtained from the Linx Technologies website, www.linxtechnologies.com. In brief, these rules require that any device that intentionally radiates RF energy be approved, that is, tested for compliance and issued a unique identification number. This is a relatively painless process. Final compliance testing is performed by one of the many independent testing laboratories across the country. Many labs can also provide other certifications that the product may require at the same time, such as UL, CLASS A / B, etc. Once the completed product has passed, an ID number is issued that is to be clearly placed on each product manufactured. 102 103 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. Values may vary from lot-to-lot and are not guaranteed. Typical parameters can and do vary over lots and application. Linx Technologies makes no guarantee, warranty, or representation regarding the suitability of any product for use in any specific application. It is the customers responsibility to verify the suitability of the part for the intended application. NO LINX PRODUCT IS INTENDED FOR USE IN ANY APPLICATION WHERE THE SAFETY OF LIFE OR PROPERTY IS AT RISK. Linx Technologies DISCLAIMS ALL WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL LINX TECHNOLOGIES BE LIABLE FOR ANY OF CUSTOMERS INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING IN ANY WAY FROM ANY DEFECTIVE OR NON-CONFORMING PRODUCTS OR FOR ANY OTHER BREACH OF CONTRACT BY LINX TECHNOLOGIES. The limitations on Linx Technologies liability are applicable to any and all claims or theories of recovery asserted by Customer, including, without limitation, breach of contract, breach of warranty, strict liability, or negligence. Customer assumes all liability
(including, without limitation, liability for injury to person or property, economic loss, or business interruption) for all claims, including claims from third parties, arising from the use of the Products. The Customer will indemnify, defend, protect, and hold harmless Linx Technologies and its officers, employees, subsidiaries, affiliates, distributors, and representatives from and against all claims, damages, actions, suits, proceedings, demands, assessments, adjustments, costs, and expenses incurred by Linx Technologies as a result of or arising from any Products sold by Linx Technologies to Customer. Under no conditions will Linx Technologies be responsible for losses arising from the use or failure of the device in any application, other than the repair, replacement, or refund limited to the original product purchase price. Devices described in this publication may contain proprietary, patented, or copyrighted techniques, components, or materials. Under no circumstances shall any user be conveyed any license or right to the use or ownership of such items. 2018 Linx Technologies. All rights reserved. The stylized Linx logo, Wireless Made Simple, WiSE, CipherLinx and the stylized CL logo are trademarks of Linx Technologies.
| 1 2 | User Manual - Pro | Users Manual | 2.75 MiB |
HumPROTM 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. No OEM Linx Remote Control or Function Module should be modified for Life and Property Safety Situations. Such modification cannot provide sufficient safety and will void the products regulatory certification and warranty. Customers may use our (non-Function) Modules, Antenna and Connectors as part of other systems in Life Safety Situations, but only with necessary and industry appropriate redundancies and in compliance with applicable safety standards, including without limitation, ANSI and NFPA standards. It is solely the responsibility of any Linx customer who uses one or more of these products to incorporate appropriate redundancies and safety standards for the Life and Property Safety Situation application. Do not use this or any Linx product to trigger an action directly from the data line or RSSI lines without a protocol or encoder/
decoder to validate the data. Without validation, any signal from another unrelated transmitter in the environment received by the module could inadvertently trigger the action. All RF products are susceptible to RF interference that can prevent communication. RF products without frequency agility or hopping implemented are more subject to interference. This module does have a frequency hopping protocol built in, but the developer should still be aware of the risk of interference. Do not use any Linx product over the limits in this data guide. Excessive voltage or extended operation at the maximum voltage could cause product failure. Exceeding the reflow temperature profile could cause product failure which is not immediately evident. Do not make any physical or electrical modifications to any Linx product. This will void the warranty and regulatory and UL certifications and may cause product failure which is not immediately evident. Table of Contents 1 Description 1 Features 2 Ordering Information 2 Absolute Maximum Ratings 3 Electrical Specifications 5 Typical Performance Graphs 10 Pin Assignments 10 Pin Descriptions 12 Pre-Certified Module Pin Assignments 13 Module Dimensions 14 Theory of Operation 15 Module Description 16 Overview 18 Addressing Modes 20 Automatic Addressing 20 Address Register Use 21 Acknowledgements and Assured Delivery 22 Frequency Hopping Spread Spectrum 23 Compatibility with the 250 Series 23 Networking 24 Transmitting Packets 25 Receiving Packets 29 Using the Buffer Empty (BE) Line 30 Exception Engine 32 Carrier Sense Multiple Access (CSMA) 33 Using the Command Response (CRESP) Line 34 Using the CMD Line 34 External Amplifier Control 35 AES Encryption 38 Using the MODE_IND Line 39 Using the PB Line 40 Restore Factory Defaults 40 Using the Low Power Features 42 The Command Data Interface 43 Reading from Registers 44 Writing to Registers 45 Command Length Optimization 45 Example Code for Encoding Read/Write Commands 48 The Command Data Interface Command Set 95 Typical Applications 96 Usage Guidelines for FCC Compliance 96 Additional Testing Requirements 97 Information to the user 98 Product Labeling 98 FCC RF Exposure Statement 98 Antenna Selection 100 Castellation Version Reference Design 102 Power Supply Requirements 102 Antenna Considerations 103 Interference Considerations 104 Pad Layout 105 Microstrip Details 106 Board Layout Guidelines 107 Helpful Application Notes from Linx 108 Production Guidelines 108 Hand Assembly 108 Automated Assembly 110 General Antenna Rules 112 Common Antenna Styles 114 Regulatory Considerations HumPROTM Series 900MHz RF Transceiver Module Data Guide Description The HumPROTM Series is a frequency hopping spread spectrum (FHSS) transceiver designed for the reliable transfer of digital data. It has a very fast lock time so that it can quickly wake up, send data and go back to sleep, saving power in battery-powered applications. The module is available in the 915MHz frequency band. 0.55"
(13.97) 0.45"
(11.43) 0.07"
(1.78) Figure 1: Package Dimensions The module has several features that increase the data transfer reliability. It ensures that no other modules are transmitting before it begins transmitting data. Automatic acknowledgements ensure that the remote side received valid data. Multiple hopping patterns enable several systems to operate in proximity without interference. A standard UART interface is used for module configuration and data transfer. A few simple serial commands are all that are needed for configuration. All modules have a unique 32-bit serial number that can be used as an address. Source and destination addressing support point-to-point and broadcast links. Address masking by the receiving module allows for creating subnets. Other network topologies can also be implemented. Housed in a tiny compact reflow-compatible SMD package, the transceiver requires no external RF components except an antenna, which greatly simplifies integration and lowers assembly costs. Versions are available that have obtained FCC and Industry Canada modular certification. Features FHSS Algorithm Fast Lock (<30ms at 115kbps) Low power modes FCC and IC Pre-certified version Simple UART interface No external RF components required No production tuning required Tiny PLCC-32 footprint 1 Revised 8/15/2019 Ordering Information Ordering Information Part Number Description HUM-900-PRO HumPRO Series Data Transceiver HUM-900-PRO-CAS HumPRO Series Data Transceiver with Castellation Connection HUM-900-PRO-UFL HumPRO Series Data Transceiver with u.FL Connector EVM-900-PRO HumPRO Series Carrier Board EVM-900-PRO-CAS HumPRO Series Carrier Board with Certified module, Castellation Connection EVM-900-PRO-UFL HumPRO Series Carrier Board with Certified module, UFL Connector MDEV-900-PRO HumPRO Series Master Development System Figure 2: Ordering Information Absolute Maximum Ratings Absolute Maximum Ratings Supply Voltage Vcc Any Input or Output Pin RF Input Operating Temperature Storage Temperature 0.3 0.3 40 40 to to 0 to to
+3.9 VCC + 0.3
+85
+85 VDC VDC dBm C C Exceeding any of the limits of this section may lead to permanent damage to the device. Furthermore, extended operation at these maximum ratings may reduce the life of this device. Figure 3: Absolute Maximum Ratings Warning: This product incorporates numerous static-sensitive components. Always wear an ESD wrist strap and observe proper ESD handling procedures when working with this device. Failure to observe this precaution may result in module damage or failure. Electrical Specifications HumPROTM Series Transceiver Specifications Parameter Power Supply Operating Voltage TX Supply Current 900MHz at +10dBm 900MHz at 0dBm RX Supply Current Power-Down Current RF Section Operating Frequency Band Number of hop channels
@ 19.2kbps RF Rate
@ 152.34kbps RF Rate Channel spacing
@ 19.2kbps RF Rate
@ 152.34kbps RF Rate 20 dB OBW
@ 19.2kbps RF Rate
@ 152.34kbps RF Rate Receiver BW
@ 19.2kbps RF Rate
@ 152.34kbps RF Rate FSK deviation
@ 19.2kbps RF Rate
@ 152.34kbps RF Rate Scan time / channel (avg)
@ 19.2kbps RF Rate
@ 152.34kbps RF Rate FHSS Lock time
@ 19.2kbps RF Rate
@ 152.34kbps RF Rate Modulation Data Encoding Number of Hop Sequences Symbol Min. Typ. Max. Units Notes VCC lCCTX lCCRX lPDN FC 2.0 3.6 VDC 40.5 22 23.5 0.7 41.5 24 24.5 1.4 mA mA mA A 1,2 1,2 1,2,3 1,2 902 928 MHz 50/64 26/32 375.9 751.81 64 315 102 232 19.2 51 1.2 0.335 63 26 2FSK 6/7 RLL 6 kHz kHz kHz kHz kHz kHz kHz kHz ms ms ms ms 2 3 HumPROTM Series Transceiver Specifications HumPROTM Series Transceiver Specifications Symbol Min. Typ. Max. Units Notes Parameter Output Symbol Min. Typ. Max. Units Notes Parameter Receiver Section Spurious Emissions IF Frequency Receiver Sensitivity
@min rate
@max rate RSSI Dynamic Range CSMA RSSI Threshold Transmitter Section Max Output Power Harmonic Emissions Output Power Range Antenna Port RF Impedance Environmental Operating Temp. Range Timing Module Turn-On Time Via VCC Via POWER_DOWN Via Standby Serial Command Response Volatile R/W NV Update Factory Reset Channel Dwell Time PO PH PH RIN 304.7 101 94 85 70
+9.5 41 50 4 4 0.4 2.4 98 91
+8.5 5 40 63 204 47 9
+85 173 5 31.5 329 400 dBm kHz dBm dBm dB dBm dBm dBc dB C ms ms ms ms ms ms ms ms 5 5 5 6 6 6 4 4 4 4 4 8 8 14 13 CMD low to trigger TX with option TXnCMD tTXnCMD 2 Interface Section UART Data rate Input Logic Low Logic High 9,600 115,200 bps VIL VIH 0.7*VCC 0.3*VCC VDC VDC Logic Low, MODE_IND, BE Logic High, MODE_IND, BE Logic Low Logic High CRESP Hold Time VOLM VOHM VOL VOH 0.7*VCC 0.7*VCC 10 Flash (Non-Volatile) Memory Specifications 0.3*VCC VDC 0.3*VCC VDC Bits 1,9 1,9 1,10 1,10 11 Flash Write Cycles 22,000 cycles 12 Input power < -60dBm 1. Measured at 3.3V VCC 2. Measured at 25C 3. 4. Characterized but not tested 5. PER = 1%
6. Into a 50-ohm load 7. No RF interference 8. From end of command to start of response 9. 60mA source/sink 10. 6mA source/sink 11. End of CMD_DATA_OUT stop bit to change in CRESP 12. Number of register write operations 13. With CSMA disabled 14. Start of factory reset command to end of last ACK response Figure 4: Electrical Specifications Typical Performance Graphs
) m B d
(
r e w o P t t u p u O X T 11.0 10.5 10.0 9.5 9.0 8.5 2.0 2.5 3.3 Supply Voltage (V) Figure 5: HumPROTM Series Transceiver Max Output Power vs. Supply Voltage - HUM-900-PRO
-40C 25C 85C 3.6 4 5
) A m
(
t n e r r u C y p p u S l 40 35 30 25 20 15 25C
-40C 85C
) A m
(
t n e r r u C y p p u S l 40.00 39.50 39.00 38.50 38.00 37.50 37.00 36.50
-40C 25C 85C
-5 0 5 9 2V 2.5V 3.3V 3.6V TX Output Power (dBm) Supply Voltage (V) Figure 6: HumPROTM Series Transceiver Average Current vs. Transmitter Output Power at 2.5V - HUM-900-PRO Figure 9: HumPROTM Series Transceiver TX Current vs. Supply Voltage at Max Power - HUM-900-PRO
) A m
(
t n e r r u C y p p u S l 40 38 36 34 32 30 28 26 24 22 20 25C
-40C 85C
) A m
(
t n e r r u C y p p u S l 23.40 23.20 23.00 22.80 22.60 22.40 22.20 22.00
-40C 25C 85C
-5 0 5 9 2V 2.5V 3.3V 3.6V TX Output Power (dBm) Supply Voltage (V) Figure 7: HumPROTM Series Transceiver Average TX Current vs. Transmitter Output Power at 3.3V -HUM-900-PRO Figure 8: HumPROTM Series Transceiver TX Current vs. Supply Voltage at 0dBm - HUM-900-PRO 6 7
) A m
(
t n e r r u C y p p u S l 24.5 24.3 24.1 23.9 23.7 23.5 23.3 23.1 22.9 22.7 22.5 85C 25C
-40C
) A
(
t n e r r u C y b d n a S t 1.40 1.20 1.00 0.80 0.60 0.40 0.20 0.00 85C 25C
-40C 2 2.1 2.2 2.3 2.4 2.5 2.6 2.7 2.8 2.9 3 Supply Voltage (V) 3.1 3.2 3.3 3.4 3.5 3.6 2.5 3.3 Supply Voltage (V) 3.6 Figure 10: HumPROTM Series Transceiver RX Scan Current vs. Supply Voltage, 9.6kbps - HUM-900-PRO Figure 12: HumPROTM Series Transceiver Standby Current Consumption vs. Supply Voltage - HUM-900-PRO Current consumption while the module is scanning for a transmission. The current is approximately 0.5mA higher when receiving data at 9.6kbps.
) A m
(
t n e r r u C y p p u S l 23 22.8 22.6 22.4 22.2 22 21.8 21.6 21.4 21.2 21 85C 25C
-40C
) m B d
(
g n d a e R i I S S R
-15.00
-25.00
-35.00
-45.00
-55.00
-65.00
-75.00
-85.00
-95.00
-105.00
-40C 25C 85C 2 2.1 2.2 2.3 2.4 2.5 2.6 2.7 2.8 2.9 3 Supply Voltage (V) 3.1 3.2 3.3 3.4 3.5 3.6
-100.00 -90.00 -80.00 -70.00 -60.00 -50.00 -40.00 -30.00 -20.00 -10.00 0.00 Input Power (dBm) Figure 11: HumPROTM Series Transceiver RX Scan Current vs. Supply Voltage, 115.2kbps - HUM-900-PRO Figure 13: HumPROTM Series Transceiver RSSI Voltage vs. Input Power - HUM-900-PRO Current consumption while the module is scanning for a transmission. The current is approximately 2mA higher when receiving data at 115.2kbps. 8 9 Pin Assignments T U O _ A T A D _ D M C I N _ A T A D _ D M C S T C B P N E _ A N L T E S E R N E _ A P D N G C C V 29 28 27 26 25 24 23 22 21 MODE_IND BE NC NC NC NC NC 30 31 32 1 2 3 4 20 19 18 17 16 15 14 GND ANT GND GND GND GND GND 5 6 78 9 10 11 12 13 C N C N P S E R C X E D N G C N C N D M C N W O D _ R E W O P Figure 14: HumPROTM Series Transceiver Pin Assignments (Top View) Pin Descriptions Pin Descriptions Pin Number 1, 2, 3, 4, 5, 6, 10, 11, 32 7 8 Name NC CRESP EX I/O Description No Electrical Connection. Do not connect any traces to these lines. 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. Exception Output. A mask can be set to take this line high when an exception occurs. 9, 14, 15, 16, 17, 18, 20, 25 GND Ground 12 POWER_DOWN I Power Down. Pulling this line low places the module into a low-power state. The module is not functional in this state. Pull high for normal operation. Do not leave floating. Pin Descriptions Pin Number Name I/O Description 13 19 21 22 23 24 26 27 28 29 30 31 CMD I Command Input. When this line is low, incoming bytes are command data. When high, incoming bytes are data to be transmitted. ANTENNA 50-ohm RF Antenna Port VCC Supply Voltage RESET LNA_EN PA_EN I O O This line resets the module when pulled low. It should be high for normal operation. This line has an internal 10k resistor to supply, so leave it unconnected if not used. Low Noise Amplifier Enable. This line is driven high when receiving. It is intended to activate an optional external LNA. Power Amplifier Enable. This line is driven high when transmitting. It is intended to activate an optional external power amplifier. CMD_DATA_OUT O Command Data Out. Output line for data and serial commands CMD_DATA_IN I CTS PB O I MODE_IND O BE O Command Data In. Input line for data (CMD is high) and serial commands (CMD is low). UART Clear To Send, active low. This line indicates to the host microcontroller when the module is ready to accept data. When CTS is high, the module is busy. When CTS is low, the module is ready for data. Push Button input. This line can be connected to Vcc through a normally open push button. Button sequences can reset configurations to default and join modules into a network. Pull low when not in use;
do not leave floating. Mode Indicator. This line indicates module activity. It can source enough current to drive a small LED, causing it to flash. The duration of the flashes indicates the modules current state. Buffer Empty. This line is high when the UART input buffer is empty, indicating that all data has been transmitted. If acknowledgment is active, it also indicates that the receiving module has acknowledged the data or a retry exception has occurred. Figure 15: HumPROTM Series Transceiver Pin Descriptions 10 11 Pre-Certified Module Pin Assignments The pre-certified version of the module has mostly the same pin assignments as the standard version. The antenna connection is routed to either a castellation (-CAS) or a u.FL connector (-UFL), depending on the part number ordered. Module Dimensions 0.55"
(13.97) T U O _ A T A D _ D M C I N _ A T A D _ D M C S T C B P N E _ A N L T E S E R N E _ A P D N G C C V 29 28 27 26 25 24 23 22 21 MODE_IND BE NC NC NC NC NC 30 31 32 1 2 3 4 5 6 78 9 10 11 12 13 C N C N P S E R C X E D N G C N C N D M C N W O D _ R E W O P T N A 19 D N G 18 NC Figure 16: HumPROTM Series Transceiver Pre-certified Version Pin Assignments - Castellation Connection (Top View) 0.45"
(11.43) Figure 18: HumPROTM Series Transceiver Dimensions 0.07"
(1.78) 0.812"
(20.62) 0.271"
(6.88) 0.078"
(1.98) 0.195"
(4.96) 0.45"
(11.43) 0.116"
(2.95) Figure 19: HumPROTM Series Transceiver Pre-certified Version Dimensions T U O _ A T A D _ D M C I N _ A T A D _ D M C S T C B P N E _ A N L T E S E R N E _ A P D N G C C V 29 28 27 26 25 24 23 22 21 MODE_IND BE NC NC NC NC NC 30 31 32 1 2 3 4 5 6 78 9 10 11 12 13 C N C N P S E R C X E D N G C N C N D M C N W O D _ R E W O P C N 19 D N G 18 ANT Figure 17: HumPROTM Series Transceiver Pre-certified Version Pin Assignments - UFL Connection (Top View) 12 13 Theory of Operation The HumPROTM Series transceiver is a low-cost, high-performance synthesized FSK / GFSK / MSK transceiver. Figure 20 shows the modules block diagram. ANTENNA ADC ADC R O T A L U D O M E D 0 90 FREQ SYNTH MODULATOR LNA PA PROCESSOR INTERFACE GPIO /
INTERFACE Figure 20: HumPROTM Series Transceiver RF Section Block Diagram The HumPROTM Series transceiver operates in the 902 to 928MHz frequency band. The transmitter output power is programmable. The range varies depending on the antenna implementation and the local RF environment. The RF carrier is generated directly by a frequency synthesizer that includes an on-chip VCO. The received RF signal is amplified by a low noise amplifier (LNA) and down-converted to I/Q quadrature signals. The I/Q signals are digitized by ADCs. A low-power onboard communications processor performs the radio control and management functions including Automatic Gain Control
(AGC), filtering, demodulation and packet synchronization. A control processor performs the higher level functions and controls the serial and hardware interfaces. A crystal oscillator generates the reference frequency for the synthesizer and clocks for the ADCs and the processor. Module Description 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. When the module does not have data to send it scans all of the channels for incoming data. If it finds a valid preamble, it pauses and looks for the start of a packet. When it receives a valid packet with a matching destination address the module outputs the data through the UART. The transmitting module accepts data bytes through its UART until a configurable number of bytes is reached or a configurable timeout expires between bytes on the UART. At this point the module transmits the packet. When the module has data to send it goes to the next channel in its hopping pattern. It measures the RSSI on that channel to ensure that the channel is clear. If the RSSI check passes, then it transmits the packets. If the RSSI fails, then it implements a random wait time and tries again. When the channel is clear, the module transmits the data. The module can stay on one channel for up to 400ms. If the module is ready to start transmitting near the end of the channel time, it transmits the number of bytes that it can in the remaining time. It then hops to the next channel in its hopping pattern to transmit the remaining data. The module supports automatic acknowledgements for assured delivery. When enabled, the receiving module responds to a valid transmission with an acknowledgement to let the transmitting module know that it received the data. If an acknowledgement is not received then the transmitting module repeats the transmission for a configurable number of retries. If the retry limit is exceeded without an acknowledgement then the transmitting module issues an exception error to let the host micro know of the communication problem. A standard UART interface is used to configure the module for operation and for the data input and output. This is suitable for direct connection to UARTs on many microcontrollers, USB converters and RS-232 converters. A simple command set is used for configuration and control. Modules can be pre-configured for fixed point-to-point or broadcast topologies allowing streaming data (no commands) during operation. 14 15 Overview The HumPROTM 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. 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. The addressing and masking allow for the creation of point-to-point, many-to-one and one-to-many wireless links. This allows the creation of many network topologies, such as star, tree and mesh. The routing for the network topology is managed outside the module. The addressing is the primary configuration when getting started with the modules. RG-00105, the HumPROTM Addressing Mode Reference Guide has details about configuring the addressing. Acknowledgements and Assured Delivery The modules support assured delivery in the form of acknowledgements and retries. When the acknowledgements are enabled, the receiving device sends an acknowledge message to let the sender know that the transmission was received. If the sender does not get an acknowledgement it resends the message up to a configurable number of retries. If there is still no acknowledgement, the module triggers an exception to let the host processor know of the error. Command Mode and Data Mode The module has two main interface modes controlled by the state of the CMD line. Command mode routes the data coming in on the CMD_DATA_ IN line to the processor for configuring the module. Data mode routes the data to the transmitter for transmission over-the-air. The CMD line is normally controlled by an external microcontroller. Streaming Data and Explicit Packets The modules default configuration is for streaming data. At some UART rates the module sends the data at a higher rate over-the-air than it is input on the UART. This hides the time required for the protocol transactions and the frequency hopping. The result is that the data appears to stream through the module with no breaks in the data apparent to the host processor. Alternatively, the module can be configured for explicit packet transmission. This allows the host processor to control when packets are sent and what data is in each packet Exceptions and Host Processor Interface The module has several indicator lines that provide feedback to the host processor on the modules operation and current status. This includes an exception line (EX) that informs the processor when errors occur so that it can take steps to manage the issue gracefully. The state of the status lines can also be read through the modules Command Data Interface to reduce the number of hardware connections that are required. Command Data Interface The module has a Command Data Interface that consists of a set of serial commands entered through a UART. These are shorter and simpler than AT commands that are popular with many modules. These commands control the configuration of the module as well as allow feedback on the operation and status of the module. Carrier Sense Multiple Access (CSMA) The module implements a Carrier Sense Multiple Access method. It listens to the channel and makes sure that it is clear before it transmits. If the channel is in use, the module either waits for it to clear or hops to the next channel depending on its current state. This reduces the overall potential for interference and improves the robustness of the link. Encryption The module supports AES-128 encryption to provide a secure wireless link. All of the modules must have encryption enabled and be using the same key in order for communication to be successful. There are two ways of entering an encryption key: directly by writing the key to registers through the Command Data Interface or through a JOIN process. 16 17 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. There are three addressing modes: DSN, User and Extended User. Each mode offers different communications methods, but all use source and destination addressing. The source address is for the transmitting unit, the destination address is the intended receiver. Each mode uses different registers for the source and destination addresses. All three addressing modes can be configured to be compatible with the older 250 Series modules. The default operation has an additional level of masking on the receiving module that helps prevent interference from adjacent networks. The following sections give brief descriptions of the three modes, but a detailed explanation and examples are given in RG-00105, the HumPROTM Addressing Mode Reference Guide. DSN Addressing Mode Device Serial Number Addressing mode is the simplest mode and supports point-to-point communications. Each module is programmed at the factory with a unique 4-byte serial number that cannot be changed. These bytes are found in the non-volatile read-only MYDSN registers
(MYDSN[3-0]). DSN Addressing mode uses this serial number as an address. The transmitting units DSN is used as the source address and the intended receivers DSN is written into the destination address registers
(DESTDSN[3-0]). All modules within range hear the transmission, but only the module with the serial number that matches the destination address outputs the data on its UART. All others ignore the transmission. User Addressing Mode User Addressing Mode is a more flexible method than DSN Addressing Mode. It uses the customer ID bytes (CUSTID[1-0]) for unencrypted messages and two of the user destination bytes (UDESTID[1-0]) as a destination address. The customer ID bytes are programmed at the factory and cannot be changed. These are determined by the factory for specific customers to prevent their systems from operating with any other systems. Contact Linx for more details. The modules local address is contained in two of the user source ID registers (USRCID[1-0]). In this mode, USRCID [1-0] contain the node address and USRCID [3-2] must be 0 in the receiver. In normal operation each module has a user ID mask (UMASK[3-0]) that splits the 32 address bits into up to three fields to provide a network address and address fields for sub-networks, supporting both individual addressing and broadcast addressing within the users network. A detailed explanation and examples are given in Reference Guide RG-00105. The 16 bits in the UDESTID[1-0] registers are transmitted. The upper 16 bits of USRCID[3-2] in the receiver must be 0. If acknowledgements are enabled, only the module with a user source ID that exactly matches the transmitted user destination ID responds. The mask is not used for this determination. Extended User Addressing Mode Extended User Addressing mode is the same as User Addressing mode but uses 32-bit addresses. The two customer ID bytes are still used
(CUSTID[1-0]) for unencrypted messages but four bytes are used for the user destination address (UDESTID[3-0]), user source ID (USRCID[3-0]) and user ID mask (UMASK[3-0]). This provides more addressing capabilities at the expense of more overhead in the packet. Network Addressing Network Addressing is selected by setting COMPAT to 0x03. It allows the receiver to receive all messages sent in User Address or Extended User Address mode with a destination address matching the USRCID group 1 bits (continuous high-order zero bits in UMASK). For example, with USRCID = 0x12345678 and UMASK = 0x000FFFFF, messages with destination address 0x123zzzzz, where z is any value, is received. 18 19 Automatic Addressing 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. Address Register Use Figure 21 shows the address registers that are used with each addressing mode. HumPROTM Series Transceiver Address Registers COMPAT 0x00 (Relaxed Addressing) 0x02 (Normal Addressing) ADDMODE UDESTID[3-0]
UDESTID[1-0]
USRC[3-0]
USRC[1-0]
UMASK[3-0]
UMASK[1-0]
0x04
(DSN) 0x14
(DSN
+ACK) 0x06
(User) 0x16
(User
+ACK) 0x07
(Ex User) 0x17
(ExUser
+ACK) 0x04
(DSN) 0x14
(DSN
+ACK) 0x06
(User) 0x16
(User
+ACK) 0x07
(Ex User) 0x17
(ExUser
+ACK) X X X X X X X X X X X X DESTDSN[3-0]
X X Figure 21: HumPROTM Series Transceiver Address Register Use Acknowledgements and Assured Delivery When a module transmits with assured delivery enabled, the receiving module returns an acknowledgement packet. The transmitting module waits for this acknowledgement for a preset amount of time based on the data rate. If an acknowledgement is not received, it retransmits the packet. If the receiver receives more than one of the same packet, it discards the duplicate packet contents but sends an acknowledgment. This way, duplicate data is not output by the module. If the received destination address matches the local address, the receiving module immediately sends an acknowledgement. This packet lets the sending module know that the message has been received. An acknowledgement packet is sent immediately following reception;
CSMA delay is not applied to these packets since permission belongs to the interacting modules. When the sending module receives the acknowledgement packet, it marks the current block of data as completed. If this is the last message in the queue, the sending module takes the BE line high to indicate that all outgoing data has been sent. Assured delivery should only be used when addressing a specific module in a point-to-point link. It should not be used when multiple receivers are enabled. When address masking is used, only the receiver with an exact match to the address in the transmitted packet responds. If none of the enabled receivers has an exact match, then there is no response and the transmitting module continues to re-transmit the data until the max number of retries is attempted. This causes the transmitting module to appear slow or unresponsive. It also impedes valid communications. 20 21 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. Assigning different hopping sequences to multiple networks in the same area minimizes the interference. When the module is awake and not transmitting, it rapidly scans all channels for a packet preamble. When a module starts transmitting at the beginning of a new channel, it transmits a packet with a long preamble of alternating 0 and 1 bits. This long preamble is sufficient to allow receiving modules to scan through all of the channels in the hopping sequence and find it. Modules that are scanning detect the preamble and pause on that channel, waiting for a valid packet. If a packet is received with a valid CRC (unencrypted) or authentication
(encrypted), the header is examined to determine whether the module should synchronize to the transmitter. Synchronization requires that the hop sequence matches and that the message is addressed to the receiver. When synchronized, the receiver stays on the current channel to either transmit a packet or to receive an additional packet. Additional packets transmitted on the same channel within the time slot use short preambles since the receivers are already listening to the current channel. At the end of the time slot for the current channel, all modules which locked to the original transmission switch to the next channel in the hop sequence. The first transmission on each new channel has a long preamble. A receiver that has synchronized to a transmitter continues to stay in synchronism by staying on the received channel until the expiration of the time slot, then waiting on the next hop channel for the duration of the time slot. If no further packets are received, the receiver loses lock and reverts to scanning. This allows the receiver to stay synchronized for a short while if a packet is not received correctly. The module supports the option to send the long preamble with every packet rather than just the first packet on each channel. This can be beneficial for systems that have modules asleep most of the time. It gives modules that just woke up the chance to synchronize to any transmitted packet instead of having to wait for the transmitter to complete its time slot and jump to the next channel. This can reduce the synchronization time and power consumption of the sleeping nodes. Compatibility with the 250 Series When DSN mode is used with a specific address, the module can communicate with 250 Series modules at UART data rates of 38,400 to 115,200 bps, non-encrypted. For other addressing modes, the HumPROTM Series modules can be configured to operate with them. Setting the COMPAT register to 0x00 enables the compatible operation. This allows mixed-mode systems and upgrades of legacy products that still maintain backwards compatibility. Only the higher baud rates are compatible. The main feature of compatibility operation is that it configures the same addressing methods used by the 250 Series. These methods are more susceptible to interference from adjacent networks of 250 Series modules which use DSN (GUI) broadcast messages. Please see Reference Guide RG-00105 for more details. Networking The HumPROTM Series modules can be used to create many types of wireless networks. The modules do not provide network routing since the internal memory size of the module would limit the overall network size. The HumPROTM can work as the MAC/PHY layers of a network stack and the memory and processing speed of the external microcontroller can be sized according to the size of the network that is needed for the application. This requires more software development, but avoids the cost of adding extra memory on the module for applications that dont need it. Linx can assist with network frameworks and concepts and can create custom designs on a contract basis. Contact Linx for more details. 22 23 Transmitting 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. The incoming bytes are buffered until one of the following conditions triggers the packet to be transmitted:
1. The number of bytes in the buffer exceeds the value in the Byte Count Trigger (BCTRIG) register. 2. The time since the last received byte exceeds the value in the Data Timeout (DATATO) register. 3. A SENDP command is written to the CMD register. 4. The CMD line is taken low with option PKOPT: TXnCMD = 1. 5. The number of buffered bytes exceeds what can be sent before the radio must hop channels. The first four conditions can be controlled by the host microcontroller. In the last case, the module transmits what it can in the remaining time then sends the rest on the next channel. This can cause the data to be divided up into multiple packets and is not within the control of the host micro. In cases where all data needs to be sent in the same packet or where the microcontroller needs greater control over the radio, the HumPROTM offers explicit control of packet transmission with options in the PKTOPT register. When the TXPKT option is enabled (PKTOPT register, bit 0 = 1), the data is held until a SENDP command is written to the CMD register. Alternatively, if option TXnCMD is enabled (PKTOPT register, bit 1 = 1), then lowering the CMD line triggers the packet transmission, reducing the number of UART transactions that are required. The BCTRIG, DATATO and hop-timing conditions are ignored when the TXPKT option is enabled. Once triggered, the transmitted packet contains the bytes in the buffer as of the trigger event, even if more data bytes are received before the packet can be sent. Multiple outgoing packets can be buffered in this way. If the full packet cannot be sent in the time remaining on the current channel, then it is held until the module hops to the next channel. This option gives the host microcontroller very fine control over when packets are transmitted and what they contain. Receiving Packets In default operation when receiving valid packets, the module outputs all received bytes as soon as the packet is validated (CRC checks pass if unencrypted or key-based verification if encrypted) and if the addressing permits it at the baud rate selected by the UARTBAUD register. No command or control bytes are output and no action is required of an external microcontroller. The first byte from a packet directly follows the last byte of the previously received packet. In cases where the host microcontroller needs more control over the data or where dynamic configuration changes could set up race conditions between incoming data and outgoing commands, the module offers explicit control over received packets. When the RXPKT option is enabled (PKTOPT register, bit 2 = 1), received data is output on the CMD_DATA_OUT line one packet at a time after a GETPH, GETPD, or GETPHD command is written to the CMD register. Writing one of these commands begins the received packet transfer cycle. Two lines are used as flow control and indicators during the transfer cycle. The CMD line is controlled by the host microcontroller. The module uses either the CTS line or the CRESP line as a status line, depending on the state of the RXP_CTS option in the PKOPT register. When a valid packet is received, the EX_RXWAIT exception flag is set in the EEXFLAG1 register. If the corresponding bit in the EEXMASK1 register is set, then the EX line goes high. The host microcontroller can monitor the EX line or periodically check the EEXFLAG or LSTATUS registers to determine if data is ready to be read. The transfer cycle is begun by writing a Get Packet Header (GETPH), Get Packet Data (GETPD), or Get Packet Header and Data (GETPHD) command to the CMD register. The module sends the command ACK byte and sets the selected status line high. Once the status line goes high, the host microcontroller sets the CMD line high and the module outputs the received data. The command sent determines whether the bytes sent are the header, data, or header followed by data. When all packet bytes have been sent the control line goes low. When the host microcontroller detects that the line is low, it sets CMD low, completing the transfer cycle. The cycle is shown in Figure 22. 24 25 CMD CMD_DATA_IN Any Command Read Packet Command CMD_DATA_OUT Any Response ACK Packet to UART CONTROL EX Exception for unread packet Packet In Figure 22: HumPROTM Series Transceiver Received Packet Transfer Cycle If a GETPH was sent and header data received, the following data can then be read by repeating the cycle with the GETPD command. If the next GETPx command is a GETPH or GETPHD, the data associated with the header read by GETPH is discarded and the header or header plus data of the following packet is returned. If there is RF-received data waiting to be sent to the UART and the mask for EX_RXWAIT is set in the EEXMASK register, EX is raised if it is low. If there is no packet waiting when a GETPx command is sent, the control line is still taken high and not reset until after CMD goes high, thereby performing a zero-byte transfer cycle. The header and payload structures differ between encrypted packets and unencrypted packets. The header and data structures for explicit unencrypted packets are shown in Figure 23. The Tag field identifies the start of the block and if it is the header information (0x01) or the packet data (0x02). The Header Length field identifies the number of header bytes that follow. The Frame Type field identifies what kind of packet was received. The values are shown in Figure 24. The Hop ID field is the hop sequence number, 0 - 5. The Sequence byte is incremented for each new packet, modulo 255. A received packet is discarded if the sequence byte matches the previously received packet to prevent delivering duplicate copies of an automatically retransmitted packet. DSN Address Packet Header Tag 0x01 Header Length 1 Frame Type 1 User Address Packet Header Tag 0x01 Header Length 1 Frame Type 1 Hop ID Sequence Dest DSN 1 1 4 Source DSN 4 Data Length 1 Hop ID Sequence Cust ID Dest Addr 1 1 2 2 or 4 Source Addr 2 or 4 Source DSN 4 Data Length 1 Packet Data Tag 0x02 Data Length 1 Data Data Length Bytes Figure 23: HumPROTM Series Transceiver Unencrypted Packet Header and Data Structure HumPROTM Series Transceiver Frame Types Frame Type Packet Type 0x04 0x06 0x07
+0x10
+0x20
+0x40 DSN Addressing Mode User Addressing Mode Extended User Addressing Mode Acknowledgements Enabled Encrypted Packet Long Preamble Packet Figure 24: HumPROTM Series Transceiver Frame Types The Cust ID field is a number that can be assigned to a specific customer. Only modules with the same customer ID respond to unencrypted transmissions. By default, Cust ID is 0x7FFF for packets transmitted with COMPAT = 2 or 0xFFFF for packets transmitted with COMPAT = 0. This field is not used in DSN mode. The Dest Addr field has the received destination address. This is 2 bytes long with User Addressing Mode and 4 bytes with DSN and Extended User Addressing Modes. The Source Addr Field is the address of the transmitting module. This is 2 bytes long with User Addressing Mode and 4 bytes with DSN and Extended User Addressing Modes. The Data Length byte indicates how many bytes of data are in the packet. This value is the same in the packet header and the associated data block. 26 27 The header and data structures for explicit encrypted packets are shown in Figure 25. The header and data blocks returned by the module are the decrypted message contents. Encrypted DSN Address Packet Header Tag 0x11 Header Length 1 Frame Type 1 Hop Key Sequence Dest DSN 1 6 4 Source DSN 4 EBlock Length 1 Payload Type 1 Encrypted User Address Packet Header Tag 0x11 Header Length 1 Frame Type 1 Hop Key Sequence Dest Addr 1 6 2 or 4 Source Addr 2 or 4 Source DSN 4 EBlock Length 1 Payload Type 1 Encrypted Packet Data Tag 0x12 Data Length 1 Data Data Length Bytes Figure 25: HumPROTM Series Transceiver Encrypted Packet Header and Data Structure The Tag, Header Length and Frame Type fields are the same as for unencrypted packets. The Hop Key field uses the first three low-order bits to indicate the Hop Sequence number, which is the same as unencrypted packets. The upper two bits indicate which key is being used. Either the factory-set key that is used to securely transfer the network key or a network key that has been written or created by the JOIN process. This is shown in Figure 26. HumPROTM Series HopKey Byte Values HopKey Bit Value 0 - 3 4 - 5 6 - 7 Hop Sequence Number, 1 to 5
= 0 Encryption key 0 = factory 1 = user network Figure 26: HumPROTM Series HopKey Byte Values The Sequence bytes contain a counter that is incremented for each new transmitted message. The initial value is randomized when the module is reset. The extended sequence becomes part of an initialization vector which is used to vary the encrypted contents of identical packets. A received packet is discarded if the sequence byte matches the previously received packet to prevent delivering duplicate copies of an automatically retransmitted packet. The Dest DSN, Source DSN, Dest Addr and Source Addr fields are the source and destination addresses, the same as in unencrypted packets. The EBlock length field is the total number of bytes of data in the encrypted payload block. This length includes the Payload Type byte. The Payload Type byte indicates what data is contained in the payload. 0x00 indicates that the payload is user data. 0x01 indicates that the payload is the 16-byte AES key followed by any user data. This is used for transferring the network encryption key during the JOIN process. For the Encrypted Packet Data packet, the Data Length byte indicates the number of bytes of data payload that follow. This value is one less than the EBlock length in the header. The reason for this is that the Payload Type byte is included in the encrypted block, but is reported with the header since it is not user data. Using the Buffer Empty (BE) Line The BE line indicates the state of the modules UART buffer. It is high to indicate that the UART input buffer is empty, indicating that all data has been transmitted. When the module receives data on the CMD_DATA_IN line and the CMD line is high, the BE line is lowered until all data in the buffer has been processed by the protocol engine. If acknowledgement is not enabled, the BE line is raised as soon as the module transmits the outgoing packets. If acknowledgement is enabled, the buffer is not updated until either the data transmissions are acknowledged by the remote end or delivery fails after the maximum number of retries. When the BE line returns high, the EX line may be sampled, or the EXCEPT or EEXFLAG register polled to determine if an error occurred during transmission. The state of the BE line can be read in the LSTATUS register, reducing the number of hardware connections that are needed. 28 29 Exception Engine The HumPROTM 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:
1. From the EXMASK and EXCEPT registers (legacy operation) 2. From the EEXMASKx and EEXFLAGx registers (standard operation) If EXMASK is non-zero, the first method is used, otherwise the second method is used. For legacy operation with the 250 and 25 Series, the EX line is set and reset by the Exception (EXCEPT) register processing. It is set when an exception occurs and the exception code ANDed with the current Exception Mask (EXMASK) register is non-zero. It is reset when the EXCEPT register is read through a command. No other operations affect the state of EX. Setting EXMASK non-zero does not change the state of EX. If an exception code is already present in the register when an error occurs, the new exception code overwrites the old value. Exception codes are organized by type for ease of masking. Figure 27 lists the exception codes and their meanings. HumPROTM Series Transceiver Exception Codes Exception Code Exception Name Description 0x08 0x09 0x13 0x20 0x40 0x42 0x43 0x44 EX_BUFOVFL EX_RFOVFL Incoming UART buffer overflowed. Outgoing UART buffer overflowed. EX_WRITEREGFAILED Attempted write to register failed. EX_NORFACK Acknowledgement packet not received after maximum number of retries. EX_BADCRC Bad CRC detected on incoming packet. EX_BADHEADER Bad CRC detected in packet header. EX_BADSEQID Sequence ID was incorrect in ACK packet. EX_BADFRAMETYPE Attempted transmit with Invalid setting in reg:NETMODE or invalid packet type in received packet header Figure 27: HumPROTM Series Transceiver Exception Codes 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 28 lists some example exception masks. HumPROTM Series Transceiver Example Exception Masks Exception Mask Exception Name 0x08 0x10 0x20 0x40 0x60 0xFF Allows only EX_BUFOVFL and EX_RFOVFL to trigger the EX line Allows only EX_WRITEREGFAILED to trigger the EX line Allows only EX_NORFACK to trigger the EX line Allows only EX_BADCRC, EX_BADHEADER, EX_BADSEQID and EX_BADFRAMETYPE exceptions to trigger the EX line Allows EX_BADCRC, EX_BADHEADER, EX_BADSEQID, EX_ BADFRAMETYPE and EX_NORFACK exceptions to trigger the EX line Allows all exceptions to trigger the EX line Figure 28: HumPROTM Series Transceiver Example Exception Masks The exception mask has no effect on the exceptions stored in the exception register. It only controls which exceptions affect the EX line. The extended exception registers offer more functionality with more exceptions and a separate bit for each exception. These registers are the default and should be used with new applications. When an exception sets an exception code in the EXCEPT register, the corresponding flag in the EEXFLAG register is also set. The EX line is set and reset by the Extended Exception Flags (EEXFLAG) and Extended Exception Mask (EEXMASK) register processing. It is set whenever the EEXFLAG value ANDed with the EEXMASK value is non-zero. EX can change on any write to either of these registers that affects the result of ANDing the registers. Clearing an EEXFLAG register bit or value can leave EX set if there is another masked condition bit set. The state of the EX line can also be read in the LSTATUS register, reducing the number of hardware lines that are required. 30 31 Carrier Sense Multiple Access (CSMA) 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. When a module has data ready to transmit and CSMA is enabled, it listens on the intended transmit channel for activity. If no signal is detected, transmission is started. If a carrier is detected with an RSSI above the CSMA threshold in the CRSSI register, transmission is inhibited. If a signal below the threshold is detected that has a compatible preamble or packet structure, transmission is also inhibited. If the module is synchronized from a recent packet transfer, it waits for a random interval, then checks again for activity. If the detected carrier lasts longer than the time allowed for the current channel, the module hops to the next channel in the hop sequence and again waits for a clear channel before transmitting. If the module is not synchronized, it hops to the next channel and again checks for interference. When no activity is detected it starts transmitting. Using the Command Response (CRESP) Line The CRESP line is high when sending data bytes and low when sending command response bytes. This indicates to an external host microcontroller that the data on the CMD_DATA_OUT line is a response to a command and not data received over-the-air. CRESP is held in the correct state at least one byte time after the last byte for the indicated source (command response or data, although it normally stays in the same state until a change is required). If a data packet is received when the module is processing a command, it sends the command response, raises CRESP, and then sends the received data bytes. When reading or writing the modules register settings, it is possible for incoming RF data to intermix with the modules response to a configuration command. This can make it difficult to determine if commands were successfully processed as well as to capture the received RF data. Setting the CMDHOLD register to 0x01 causes the module to store incoming RF traffic (up to the RF buffer capacity) while the CMD line is low. When the CMD line is returned high, the module outputs the buffered data on the UART. This allows the external host microcontroller to have separate configuration times and data times instead of potentially having to handle both at once. The CRESP line stays low for at least ten bit times after the stop bit of the last command response. Figure 29 shows the timing. CMD_DATA_OUT Start D0
... D6 D7 Stop CRESP Figure 29: HumPROTM Series Transceiver CRESP Line Timing 10 bit times 32 33 Using the CMD Line 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. Since the modules controller looks at UART data one byte at a time, the CMD line must be held low for the entire duration of the command plus time for ten bits as margin for processing. Leaving the line low for additional time (for example, until the ACK byte is received by the application) does not adversely affect the module. If RF packets are received while the CMD line is active, they are still processed and output on the modules UART
(assuming CMDHOLD=0 and PKOPT:RXPKT=0). Figure 30 shows this timing. CMD_DATA_IN Start Stop D7 D0 D6
... 10 bit times CMD Figure 30: HumPROTM Series Transceiver CMD Line Timing Commands can be entered sequentially without having to raise the CMD line after each one. The CMD line just needs to be raised to be able to enter data for transmission. If the CMDHOLD register is 0x01 then any received data is held until the CMD line is raised. This prevents received data from being intermingled with command responses. External Amplifier Control The HumPROTM Series transceiver has two output lines that are designed to control external amplifiers. The PA_EN line goes high when the module activates the transmitter. This can be used to activate an external power amplifier to boost the signal strength of the transmitter. The LNA_EN line goes high when the module activates the receiver. This can be used to activate an external low noise amplifier to boost the receiver sensitivity. These external amplifiers can significantly increase the range of the system at the expense of higher current consumption and system cost. The states of the PA_EN and LNA_EN lines can be read in the LSTATUS register. This offers a quick way to determine the current state of the radio. AES Encryption HumPROTM Series modules with firmware version 2.0 and above offer 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. The HumPROTM Series module has the option to use AES encryption, arguably the most common encryption algorithm on the market. This is implemented in a secure mode of operation to ensure the secrecy of the transmitted data. It uses a 128-bit key to encrypt the transmitted data. The source and destination addresses are sent in the clear. Encryption is disabled by default. There are two ways to enable encryption and set the key: sending serial commands and using the JOIN process. Writing an encryption key to the module with the CDI The module has no network key when shipped from the factory. An encryption key can be written to the module using the CDI. The CMD register is used to write or clear a key. The key cannot be read. The same key must be written to all modules that are to be used together. If they do not have the same key then they will not communicate in encrypted mode. The JOIN Process The JOIN process is a method of generating an encryption key and distributing the key and addresses to associated modules through a series of button presses. This makes it very simple to establish an encrypted network in the field or add new nodes to an existing network without any additional equipment. It is also possible to trigger the JOIN process through commands on the Command Data Interface. The JOIN process configures a star network with the central unit as system administrator. Other units are added to the network one at a time. The hardware required is a pushbutton that is connected to the PB line. This takes the line to VCC when it is pressed and ground when it is released. An LED connected to the MODE_IND line provides visual indication of the modules state. 34 35 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. When Generate Key is performed, the unit is set as the network administrator. It generates a random 128-bit AES encryption key based on ambient RF noise and scrambled by an encryption operation. If UMASK is the default value (0xFFFFFFFF), it is set to 0x000000FF, supporting up to 255 nodes, and ADDMODE is set to Extended User Address with encryption (0x27) (or without encryption (0x07) if flag PGKEY in the SECOPT register is 0). UMASK and ADDMODE are not changed if UMASK is not 0xFFFFFFFF. A random 32-bit address is generated. By default, the lower 8 bits are 0, forming the network base address. Other nodes are assigned sequential addresses, starting with network base address +1. UDESTID is set to the bitwise OR of USRCID and UMASK, which is the network broadcast address. 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 address of the administrator. The values are encrypted using a special factory-defined key. Once the JOIN process is complete, the MODE_IND blinks on both units and they now operate together. This is shown in Figure 31 A. If UMASK is pre-set when Generate Key is initiated, then the JOIN process uses that mask and sets the address accordingly. This can allow more nodes in the network. This is shown in Figure 31 B. Likewise, the network key can be written to the module with the CDI interface and the JOIN process used to create an address and associate new modules. Or the administrator can be completely configured through the CDI and the JOIN process used to associate nodes in the field. This gives the system designer many options for configuration. The SECOPT register is used to configure options related to the JOIN process. This allows the OEM to set desired values at the factory and allow final network configuration in the field. This includes disabling the ability to change the address, change the key and share the key. The built-in security prohibits changing a node to an administrator without changing the key. 36 A) Key Generation and Network Join from Factory Default Generate Key D A UMASK = FF FF FF FF USRCID = FF FF FF FF UDESTID = FF FF FF FF No Key UMASK = 00 00 00 FF USRCID = 76 54 32 00 UDESTID = 76 54 32 FF Network Key JOIN D N UMASK = FF FF FF FF USRCID = FF FF FF FF UDESTID = FF FF FF FF No Key UMASK = 00 00 00 FF USRCID = 76 54 32 01 UDESTID = 76 54 32 00 Network Key A UMASK = 00 00 00 FF USRCID = 76 54 32 00 UDESTID = 76 54 32 FF Network Key B) Key Generation and Network Join from Preset Mask Generate Key P A UMASK = 00 00 0F FF USRCID = FF FF FF FF UDESTID = FF FF FF FF No Key UMASK = 00 00 0F FF USRCID = 76 54 30 00 UDESTID = 76 54 3F FF Network Key JOIN D N UMASK = FF FF FF FF USRCID = FF FF FF FF UDESTID = FF FF FF FF No Key UMASK = 00 00 0F FF USRCID = 76 54 30 01 UDESTID = 76 54 30 00 Network Key A D = Factory Default A = Network Administrator N = Network Node P = OEM Preset Unit UMASK = 00 00 0F FF USRCID = 76 54 30 00 UDESTID = 76 54 3F FF Network Key Figure 31: HumPROTM Series JOIN Process 37 Using the MODE_IND Line The MODE_IND line is designed to be connected to an LED to provide visual indication of the modules status and current actions. The pattern of blinks indicates the particular feedback from the module. Figure 32 shows the different blink patterns and their meanings. HumPROTM Series Transceiver MODE_IND Line Timing Display
[on/off time in seconds]
Module Status Join Operation Two quick blinks One quick blink Quick blink Slow Blink Administrator Join. The administrator is looking for a node to join with. Node Join. The node is looking for an administrator to join with. Key Transfer Active. Key transfer is taking place
(administrator and node). Key Transfer Complete. The module has completed a key transfer (administrator and node). Temporary On On when the PB line is high Two quick blinks, one time Join Canceled. Slow blink, repeat 3 times Slow blink and two quick blinks Key Test Results One quick blink Three times Failure. For Share Key or Get Key, there are multiple units attempting to pair, protocol error, or timeout without response Long Hold Acknowledgement. The long hold period for Generate Key or Reset Sequence was recognized (PB is asserted) No Key. There is no network key or network address. Two quick blinks Three times Key Set, node. The network key and network address are set on a node. Three quick blinks Three times Key Set, administrator. The network key and network address are set on an administrator. Normal operation Off No activity Temporarily on Transmitting or receiving packet Figure 32: HumPROTM Series MODE_IND Line Timing Figure 34 shows the MODE_IND displays in a graphical format. Operation Administrator Join Node Join Key Transfer Active Key Transfer Complete JOIN Cancelled Long Hold Failure No Key Set Key Set, Node Key Set, Administrator Time (seconds) MODE_IND Display Comments Repeats for 30 seconds or until JOIN is complete Repeats for 30 seconds or until JOIN is complete Repeats for the duration of the transfer Six blinks total Repeats for as long as the PB line is asserted after the long hold period has been recognized Repeats, three times total Repeats, three times total Repeats, three times total 0 0.5 1 1.5 2 2.5 Figure 34: HumPROTM Series MODE_IND Displays Using the PB Line The PB Line is used to trigger functions associated with the JOIN process. This line should be connected to a momentary pushbutton that pulls the line to VCC when it is pressed and opens the circuit when it is released. There is no internal pull-down, so a resistor to ground should be used to pull the line down when the button is not pressed. A value of 10k to 100k works well. The sequence of presses determines which function is triggered. Figure 33 shows the sequences. HumPROTM Series Transceiver PB Line Operation Function Sequence Join a network 1 short pulse Cancel a Join Process that is in progress 1 short pulse Generate a network key and address Hold PB high for 30 seconds Reset to factory defaults Test key and address 4 short pulses and hold high for 3 seconds 3 short pulses A short pulse is a logic high that is between 100 and 2,000ms in duration. Figure 33: HumPROTM Series PB Line Operation 38 39 HumPROTM Series Transceiver Output Line Sleep States Output Line EX CRESP LNA_EN PA_EN TXD CTS MODE_IND BE Sleep State Unchanged Low Low Low High High Low Unchanged Figure 35: HumPROTM Series Output Line Sleep States If the volatile registers have been corrupted during sleep, a software reset is performed. This restarts the module as if power were cycled. This can be caused by power surges or brownout among other things. After the module wakes up, it sets the IDLE register to 0 (active). If the WAKEACK register is set to 1, then the module outputs the 0x06 byte on the CMD_DATA_OUT line. The CRESP line is taken high and the module then begins normal operation. Pulsing RESET low causes the module to restart rather than continue from sleep. 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. After PB goes low, the non-volatile configurations are set to the factory default values and the module is restarted. The default UART data rate is 9,600bps. If the timing on PB does not match the specified limits, the sequence is ignored. Another attempt can be made after lowering PB for at least 3 seconds. Using the Low Power Features The module supports several low-power features to save current in battery-powered applications. This allows the module to be asleep most of the time, but be able to quickly wake up, send data and go back to sleep. Taking the Power Down (POWER_DOWN) line low places the module into the lowest power state. In this mode, the internal voltage regulator and all oscillators are turned off. All circuits powered from the voltage regulator are also off. The module is not functional while in this mode and current consumption drops to below 6A. Taking the line high wakes the module. When the POWER_DOWN line is high, the IDLE register determines sleep operation. If IDLE is set to 1 during normal operation, the module sends an ACK byte, waits for completion of an active transmission, then goes into sleep mode. Unsent data in the incoming UART data buffer does not inhibit sleep. During sleep mode, the output lines are in the states in Figure 35. A rising transition on the POWER_DOWN or CMD_DATA_IN lines wakes the module. If a negative-going pulse is needed to generate a rising edge, the pulse width should be greater than 1 s. Other lines also wake the module but it immediately goes back to sleep. Floating inputs should be avoided since they may cause unintended transitions and cause the module to draw additional current. 40 41 The Command Data Interface The HumPROTM 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 modules 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). The CMD line tells the module if the data on the UART is for configuration commands (low) or data transmission
(high). The module has a 256 byte buffer for incoming data. The module starts transmitting when the buffer reaches a specified limit or when the time since the last received byte on the UART reaches a specified value. This allows the designer to optimize the module for fixed length and variable length data. If the buffer gets nearly full (about 224 bytes), the module pulls the CTS line high, indicating that the host should not send any more data. Data sent by the host while the buffer is full is lost, so the CTS line provides a warning and should be monitored. When there is outgoing data waiting to be transmitted or acknowledged the BE line is low, otherwise BE is high. Configuration settings are stored in two types of memory inside the module. Volatile memory is quick to access, but it is lost when power is removed from the module. Non-volatile memory has a limited number of write cycles, but is retained when power is removed. When a configuration parameter has both a non-volatile and volatile register, the volatile register controls the operation unless otherwise stated. The non-volatile register holds the default value that is loaded into the volatile register on power-up. Configuration settings are read from non-volatile memory on power up and saved in volatile memory. The volatile and non-volatile registers have different address locations, but the same read and write commands. The two locations can be changed independently. The general serial command format for the module is:
[FF] [Length] [Command]
The Length byte is the number of bytes in the Command field. The Command field contains the register address that is to be accessed and, in the case of a write command, the value to be written. Neither Length nor Command can contain a 0xFF byte. Byte values of 128 (0x80) or greater can be sent as a two-byte escape sequence of the format:
0xFE, [value - 0x80]
For example, the value 0x83 becomes 0xFE, 0x03. The Length count includes the added escape bytes. A response is returned for all valid commands. The first response byte is CMD_ACK (0x06) or CMD_NACK (0x15). Additional bytes may follow, as determined by the specific command. Reading from Registers A register read command is constructed by placing an escape character
(0xFE) before the register number. The module responds by sending an ACK (0x06) followed by the register number and register value. The register value is sent unmodified, so if the register value is 0x83, 0x83 is returned. If the register number is invalid, the module responds with a NACK (0x15). The command and response are shown in Figure 36. HumPROTM Series Read From Configuration Register Command Header 0xFF Size 0x02 Escape Address 0xFE REG Response ACK 0x06 Address Value REG V Command for an Address greater than 128 (0x80) Header 0xFF Size 0x03 Response Escape Addr1 Addr2 0xFE 0xFE REG-80 ACK 0x06 Address Value REG V 42 43 Figure 36: HumPROTM Series Read from Configuration Register Command and Response Command Length Optimization Some commands may be shortened by applying the following rules:
1. Escape sequences are not required for byte values 0x00 to 0xEF
(besides 0xFE and 0xFF, bytes 0xF0 0xFD are reserved for future use). 2. An escape byte inverts bit 7 of the following data byte. 3. The 0xFE as the first byte of the Read Register Command field is an escape byte. 4. Two consecutive escape bytes cancel unless the following data byte is 0xf0-0xff. Examples:
FF 02 FE 02 (read nv:TXPWR) is equivalent to FF 01 82. FF 03 FE FE 53 (read v:PKOPT) is equivalent to FF 01 53. FF 03 1A FE 7F (write FF to nv:UMASK0) cannot be shortened. FF 03 1A FE 40 (write C0 to nv:UMASK0) is equivalent to FF 02 1A C0. These rules are implemented in the sample code file EncodeProCmd.c, which can be downloaded from the Linx website. Writing to Registers 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 37. HumPROTM Series Write to Configuration Register Command Register and Value less than 128 (0x80) Header Size Address Value 0xFF 0x02 REG V Register less than 128 (0x80) and a Value greater than or equal to 128 (0x80) Header Size Address Escape Value 0xFF 0x03 REG 0xFE V-0x80 Register greater than or equal to 128 (0x80) and a Value less than 128 (0x80) Header Size Escape Address Value 0xFF 0x03 0xFE REG-0x80 V Register and Value greater than or equal to 128 (0x80) Header Size Escape Address Escape Value 0xFF 0x04 0xFE REG-0x80 0xFE V-0x80 Figure 37: HumPROTM Series Write to Configuration Register Command Generally, there are three steps to creating the command. 1. Determine the register address and the value to be written. 2. Encode the address and value as either the number (N) or the encoded number (0xFE, N-0x80) as appropriate. 3. Add the header (0xFF) and the size. The module responds with an ACK (0x06). If the ACK is not received, the command should be resent. The module responds with a NACK (0x15) if a write is attempted to a read-only or invalid register. As an example, to write 01 to register 0x83, send FF 03 FE 03 01 Note: The non-volatile memory has a life expectancy of at least 18,000 write operations. 44 45 return dx;
}
/* Function: HumProRead
** Description: This function encodes a read command to the specified
** register address.
*/
unsigned char /* number of encoded bytes, 3 to 4 */
HumProRead(
unsigned char *cmd, /* out: encoded read command, length >= 4 */
unsigned char reg /* register number to read, 0..0xff */
) {
unsigned char ra; /* read register byte */
ra = reg ^ 0x80;
return HumProCommand(cmd, &ra, 1);
}
/* Function: HumProWrite
** Description: This function encodes a command to write a single byte to
** a specified register address.
*/
unsigned char /* number of encoded bytes, 4 to 6 */
HumProWrite(
unsigned char *cmd, /* out: encoded read command, length >= 6 */
unsigned char reg, /* register number to write, 0..0xff */
unsigned char val /* value byte, 0..0xff */
) {
unsigned char cs[2];
cs[0] = reg;
cs[1] = val;
return HumProCommand(cmd, &cs, 2);
}
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.c
/* Sample C code for encoding Hum-xxx-PRO commands
**
** Copyright 2015 Linx Technologies
** 159 Ort Lane
** Merlin, OR, US 97532
** www.linxtechnologies.com
**
** License:
** Permission is granted to use and modify this code, without royalty, for
** any purpose, provided the copyright statement and license are included.
*/
#include EncodeProCmd.h
/* Function: HumProCommand
** Description: This function encodes a command byte sequence.
** If len = 1, a read command is generated.
** If len > 1, a write command is generated.
** rcmd[0] = register number
** rcmd[1..(n-1)] = bytes to write
*/
unsigned char /* number of encoded bytes, n+2 to 2*n+2 */
HumProCommand(
unsigned char *ecmd, /* out: encoded command, length >= 2*n + 2 */
const unsigned char *rcmd, /* in: sequence of bytes to encode */
unsigned char n /* number of bytes in rcmd, 1..32 */
) {
unsigned char dx; /* destination index */
unsigned char sx; /* source index */
unsigned char v; /* value to be encoded */
dx = 2;
sx = 0;
while (n--) {
v = rcmd[sx++];
if (v >= 0xf0) {
ecmd[dx++] = 0xfe;
v &= 0x7f;
}
ecmd[dx++] = v;
}
ecmd[0] = 0xff;
ecmd[1] = dx - 2;
46 47 The Command Data Interface Command Set The following sections describe the registers. HumPROTM Series Configuration Registers Name CRCERRS HOPTABLE TXPWR UARTBAUD ADDMODE DATATO MAXTXRETRY ENCRC BCTRIG SHOWVER ENCSMA IDLE WAKEACK NV Addr Vol Addr 0x40 0x4B 0x4D 0x4E 0x4F 0x50 0x52 0x53 0x54 0x00 0x02 0x03 0x04 0x05 0x07 0x08 0x09 0x0A 0x0B 0x56 0x0D 0x58 0x0E 0x59 R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W Default Value Description CRC Error Count Channel Hop Table Transmit Power UART data rate Addressing mode Data timeout 0x00 0x00 0x03 0x01 0x04 0x10 0x1A Maximum Transmit Retries 0x01 0x40 0x01 0x01 0x00 0x01 Enable CRC checking Byte Count trigger Show version on startup Enable CSMA Idle Mode UART Acknowledge on Wake Destination Address for User Packet Type, extended Destination Address for User Packet Type, extended Destination Address for User Packet Type Destination Address for User Packet Type Source Address for User Packet Type, extended Source Address for User Packet Type, extended Source Address for User Packet Type Source Address for User Packet Type Address Mask for User Packet Type, extended Address Mask for User Packet Type, extended Address Mask for User Packet Type Address Mask for User Packet Type Destination Device Serial Number Destination Device Serial Number Destination Device Serial Number UDESTID3 0x0F 0x5A R/W 0xFF UDESTID2 0x10 0x5B R/W 0xFF UDESTID1 0x11 0x5C R/W 0xFF UDESTID0 0x12 0x5D R/W 0xFF USRCID3 0x13 0x5E R/W 0xFF USRCID2 0x14 0x5F R/W 0xFF USRCID1 USRCID0 0x15 0x16 0x60 0x61 R/W R/W 0xFF 0xFF UMASK3 0x17 0x62 R/W 0xFF UMASK2 0x18 0x63 R/W 0xFF UMASK1 UMASK0 DESTDSN3 DESTDSN2 DESTDSN1 0x64 0x19 0x1A 0x65 0x1D 0x68 0x1E 0x69 0x6A 0x1F R/W R/W R/W R/W R/W 0xFF 0xFF 0xFF 0xFF 0xFF 48 0x20 0x21 0x23 0x25 0x26 0x34 0x35 0x36 0x37 0x39 0x3A 0x3F 0x78 DESTDSN0 EXMASK CMDHOLD COMPAT AUTOADDR MYDSN3 MYDSN2 MYDSN1 MYDSN0 CUSTID1 CUSTID0 CSRSSI RELEASE EXCEPT PRSSI ARSSI FWVER3 FWVER2 FWVER1 FWVER0 NVCYCLE1 NVCYCLE0 LSTATUS CMD SECSTAT JOINST EEXFLAG2 EEXFLAG1 EEXFLAG0 0x80 EEXMASK2 0x81 EEXMASK1 0x82 EEXMASK0 0x83 PKTOPT 0x84 SECOPT LASTNETAD[3] 0x8C LASTNETAD[2] 0x8D LASTNETAD[1] 0x8E LASTNETAD[0] 0x8F 0xC0 0xC1 0xC2 0xC3 0xC4 0xC5 0x6B 0x6C 0x6E 0x70 0x71 R/W R/W R/W R/W R/W 0xFF 0x00 0x00 0x02 0x00 R R R R R R 0xFF 0xFF Destination Device Serial Number Exception Mask to activate EX Hold RF data when nCMD pin is low Compatibility Automatic Reply Address Factory programmed Serial Number Factory programmed Serial Number Factory programmed Serial Number Factory programmed Serial Number Factory programmed customer ID Factory programmed customer ID R/W 0xBA Carrier Sense minimum RSSI 0x79 0x7B 0x7C R R R R R R R R R R R W R R 0xC6 0xC7 0xC9 0xCA 0xCD R/W R/W 0xCE R/W 0xCF 0xD0 R/W R/W 0xD1 R/W 0xD2 R/W 0xD3 0xD4 R/W R/W R/W R/W R/W Release number Exception code Packet RSSI Ambient RSSI Firmware version, major Firmware version, minor Firmware version, increment Firmware version, suffix NV Refresh Cycles, MS NV Refresh Cycles, LS Output line status Command register Security Status Join Status Extended exception flags Extended exception flags Extended exception flags Extended exception mask Extended exception mask Extended exception mask Packet options Security Options Last Network Address Assigned Last Network Address Assigned Last Network Address Assigned Last Network Address Assigned 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0xFF 0x00 0x00 0x00 0x00 49 Figure 38: HumPROTM Series Configuration 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 39 shows the command and response. channels. Figure 42 shows the hop sequences referenced by channel number. When the baud rate is 38,400bps and higher, the module uses 26 hopping channels and only even channels are used. Figure 43 shows the hop sequences referenced by channel number. The default hop sequence is 0. HumPROTM Series RF Channels Channel Number Frequency (MHz) Channel Number Frequency (MHz) HumPROTM Series CRC Error Count Read Command Header 0xFF Size 0x02 Write Command Header 0xFF Size 0x02 Escape Address 0xFE 0x40 Address Value 0x40 V Read Response ACK 0x06 Address Value 0x40 V Figure 39: HumPROTM Series CRC Error Count Command and Response HOPTABLE - Channel Hop Table Volatile Address = 0x4B; Non-Volatile Address = 0x00 The module supports 6 different hop sequences with minimal correlation. The sequence is set by the value in the HOPTABLE register. Changing the hop sequence changes the band utilization, much the same way that a channel does for a non-hopping transmitter. The hop table selection must match between the transmitter and receiver. Valid values are 0-5. Figure 40 shows the command and response. HumPROTM Series Channel Hop Table Read Command Read Response Header Size Escape Address ACK Address Value 0xFF 0x02 0xFE 0x4B 0x00 0x06 0x4B 0x00 V Write Command Header Size Address Value 0xFF 0x02 0x4B 0x00 V 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 902.971 903.347 903.723 904.099 904.475 904.851 905.227 905.602 905.978 906.354 906.730 907.106 907.482 907.858 908.234 908.610 908.986 909.361 909.737 910.113 910.489 910.865 911.241 911.617 911.993 912.369 912.745 913.120 913.496 913.872 914.248 914.624 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 915.000 915.376 915.752 916.128 916.504 916.880 917.255 917.631 918.007 918.383 918.759 919.135 919.511 919.887 920.263 920.639 921.014 921.390 921.766 922.142 922.518 922.894 923.270 923.646 924.022 924.398 924.773 925.149 925.525 925.901 926.277 926.653 Figure 40: HumPROTM Series Channel Hop Table Command and Response Figure 41 shows the RF channels used by the HumPROTM Series. When the baud rate is set to 9,600 or 19,200 bps, the module uses 50 hopping Figure 41: HumPROTM Series RF Channels 50 51 HumPROTM Series Hop Sequences by Channel Number for 19,200bps and below HumPROTM Series Hop Sequences by Channel Number for 38,400bps and Above 0 32 2 4 10 20 42 22 46 28 58 54 44 24 48 34 6 14 30 62 60 56 50 38 12 26 52 1 30 60 58 52 42 20 40 16 34 4 8 18 38 14 28 56 48 32 0 2 6 12 24 50 36 10 2 6 40 42 48 58 16 60 20 2 32 28 18 62 22 8 44 52 4 36 34 30 24 12 50 0 26 3 56 22 20 14 4 46 2 42 60 30 34 44 0 40 54 18 10 58 26 28 32 38 50 12 62 36 4 44 14 16 22 32 54 34 58 40 6 2 56 36 60 46 18 26 42 10 8 4 62 50 24 38 0 Figure 43: HumPROTM Series Hop Sequences for UART rates of 38,400bps and above 5 18 48 46 40 30 8 28 4 22 56 60 6 26 2 16 44 36 20 52 54 58 0 12 38 24 62 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 11 52 37 36 42 25 15 1 55 2 12 26 27 41 9 8 31 49 13 47 14 33 48 38 45 59 3 46 0 39 57 56 5 40 23 62 24 54 17 22 32 7 61 34 63 50 30 43 28 4 52 10 54 62 21 33 44 51 61 36 34 2 57 50 12 29 6 8 46 48 11 39 4 45 22 56 18 43 60 31 47 0 20 37 59 35 7 15 25 16 23 42 24 32 28 26 13 3 5 49 5 35 23 41 45 7 42 63 24 9 27 10 17 20 22 18 32 3 8 15 4 0 48 13 61 31 56 52 54 55 62 6 37 36 38 51 59 5 43 21 40 14 12 30 16 34 46 60 39 58 33 Figure 42: HumPROTM Series Hop Sequences for UART rate of 19,200bps and below 52 53 TXPWR - Transmitter Output Power Volatile Address = 0x4D; Non-Volatile Address = 0x02 The value in the TXPWR register sets the modules output power. Figure 44 shows the command and response and Figure 45 available power settings and typical power outputs for the module. The default setting is 0x03. HumPROTM Series Transmitter Output Power Mode Read Command Read Response Header Size Escape Address ACK Address Value 0xFF 0x02 0xFE 0x4D 0x02 0x06 0x4D 0x02 PWR Write Command Header Size Address Value 0xFF 0x02 0x4D 0x02 PWR Figure 44: HumPROTM Series Transmitter Output Power Mode Command and Response UARTBAUD - UART Baud Rate Volatile Address = 0x4E; Non-Volatile Address = 0x03 The value in UARTBAUD sets the data rate of the UART interface. Changing the non-volatile register changes the data rate on the following power-up or reset. Changing the volatile register changes the data rate immediately following the command acknowledgement. Figure 46 shows the command and response and Figure 47 shows the valid settings. HumPROTM Series UART Baud Rate Read Command Read Response Header Size Escape Address ACK Address Value 0xFF 0x02 0xFE 0x4E 0x03 0x06 0x4E 0x03 V Write Command Header Size Address Value 0xFF 0x02 0x4E 0x03 V Figure 46: HumPROTM Series UART Baud Rate Command and Response HumPROTM Series Transmitter Output Power Mode Register Settings HumPROTM Series UART Baud Rate Register Settings PWR 0x00 0x01 0x02 0x03 Typical Output Power (dBm)
-5 0
+5
+9 Figure 45: HumPROTM Series Transmitter Output Power Mode Settings V 0x01 0x02 0x03 0x04 0x05 0x06 0x07 Baud Rate (bps) RF Data Rate (bps) 9,600 19,200 38,400 57,600 115,200 10,400*
31,250*
19,200 19,200 153,600 153,600 153,600 153,600 153,600
* These data rates are not supported by PC serial ports. Selection of these rates may cause the module to fail to respond to a PC, requiring a reset to factory defaults. Figure 47: HumPROTM Series UART Baud Rate Settings If the modules UART baud rate is different than the host processor UART baud rate then the module will not communicate correctly. If mismatched, every rate can be tested until the correct one is found or the module can be reset to factory defaults. The default baud rate is 9,600bps (0x01). 54 55 HumPROTM Series Addressing Mode Register Settings Addressing Mode Meaning 0x04 0x06 0x07
+0x00
+0x08
+0x10
+0x20 DSN Addressing Mode User Addressing Mode Extended User Addressing Mode Send normal preamble Send long preamble Request acknowledgments Encrypt packets All other addressing modes are reserved and may cause undesired operation. Figure 49: HumPROTM Series Addressing Mode Register Settings 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. Endpoints can awaken, receive a message from the transmitter, and go back to sleep. This message could contain scheduling information as to when to wake again for a full bi-directional communications session. If bit 4 is set, then the receiver is instructed to transmit an acknowledgement packet for assured delivery signifying to the transmitter that the message was received. If bit 5 is set then the module transmits data in encrypted mode. Figure 48 shows the command and response and Figure 49 shows the valid settings. HumPROTM Series Addressing Mode Read Command Read Response Header Size Escape Address ACK Address Value 0xFF 0x02 0xFE 0x4F 0x04 0x06 0x4F 0x04 V Write Command Header Size Address Value 0xFF 0x02 0x4F 0x04 V Figure 48: HumPROTM Series Addressing Mode Command and Response 56 57 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). If the timer reaches zero before the next byte is received from the UART, the module begins transmitting the data in the buffer. This timeout value should be greater than one byte time at the current UART baud rate with a minimum of 0x02. It should not be set any value less than one byte time as unpredictable results could occur. If the timeout value is set to 0x00, the transmit wait timeout is deactivated. In this case, the transceiver waits until a number of bytes equal to the UART Byte Count Trigger (BCTRIG) have been received by the UART. All of the bytes are sent once the trigger has been reached. Figure 50 shows examples of the commands. Figure 51 shows the minimum timeout values based on baud rate. HumPROTM Series Transmit Wait Timeout Read Command Read Response Header Size Escape Address ACK Address Value 0xFF 0x02 0xFE 0x50 0x05 0x06 0x50 0x05 V Write Command Header Size Address Value 0xFF 0x02 0x50 0x05 V 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 52 shows examples of the command. HumPROTM Series Maximum Transmit Retries Read Command Read Response Header Size Escape Address ACK Address Value 0xFF 0x02 0xFE 0x52 0x07 0x06 0x52 0x07 V Write Command Header Size Address Value 0xFF 0x02 0x52 0x07 V Figure 52: HumPROTM Series Maximum Transmit Retries Command and Response The time between retries depends on the current baud rate. Figure 53 shows the time between retries based on baud rate. The elapsed transmit and acknowledgment time is (retries+1) (PacketTransmitTime + Timeout). HumPROTM Series Acknowledgement Timeout Times Baud Rate Timeout Time 9,600 19,200 38,400 57,600 115,200 50ms 50ms 30ms 30ms 30ms Figure 50: HumPROTM Series Transmit Wait Timeout Command and Response Figure 53: HumPROTM Series Acknowledgement Timeout Times HumPROTM Series Minimum DATATO Values Baud Rate Minimum DATATO 9,600 19,200 38,400 57,600 115,200 3ms 2ms 2ms 2ms 2ms Figure 51: HumPROTM Series Transmit Wait Timeout Minimum Values 58 59 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. The default CRC mode setting is enabled. Figure 54 shows examples of the commands and Figure 55 shows the available values. HumPROTM Series CRC Enable Read Command Read Response Header Size Escape Address ACK Address Value 0xFF 0x02 0xFE 0x53 0x08 0x06 0x53 0x08 V Write Command Header Size Address Value 0xFF 0x02 0x53 0x08 V Figure 54: HumPROTM Series CRC Enable Command and Response HumPROTM Series CRC Enable Register Settings V 0x00 0x01 Mode CRC Disabled CRC Enabled Figure 55: HumPROTM Series CRC Enable Register Settings Although disabling CRC checking allows receiving packets with errors in the payload, errors in the header can still prevent packets from being output by the module. BCTRIG - UART Byte Count Trigger Volatile Address = 0x54; Non-Volatile Address = 0x09 The BCTRIG register determines the UART buffer level that triggers the transmission of a packet. The minimum value is decimal 1 and the maximum value is 192. The default value for this register is 64, which provides a good mix of throughput and latency. At the maximum data rate, a value of 128 optimizes throughput. This register does not guarantee a particular transmission unit size; rather, it specifies the minimum desired size. If there is not enough time left in the channel dwell time before the module must hop to the next channel, for instance, the protocol engine sends as many characters as it can to fill the current channel dwell time, and sends the remaining characters on the next channel. Figure 56 shows examples of the commands. HumPROTM Series UART Byte Count Trigger Read Command Read Response Header Size Escape Address ACK Address Value 0xFF 0x02 0xFE 0x54 0x09 0x06 0x54 0x09 V Write Command Header Size Address Value 0xFF 0x02 0x54 0x09 V Figure 56: HumPROTM Series UART Byte Count Trigger Command and Response This trigger can be overridden by enabling the TXPKT option (PKTOPT register, bit 0). 60 61 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 57 shows examples of the commands and Figure 58 shows the available values. HumPROTM Series Show Version Read Command Header 0xFF Size 0x02 Write Command Header 0xFF Size 0x02 Escape Address 0xFE 0x0A Address Value 0x0A V Read Response ACK 0x06 Address Value 0x0A V Figure 57: HumPROTM Series Show Version Command and Response HumPROTM Series Show Version Register Settings V 0x00 0x01 Meaning Startup message is NOT output on reset or power-up. Startup message is output on reset or power-up. This is a blocking operation, and any incoming UART data is lost during the transmission of this message through the CMD_DATA_OUT line. All UART commands must be sent after this message has completed. Figure 58: HumPROTM Series Show Version Register Settings Example:
HUM-900-PRO v1.2.3
(C) 2014 Linx Technologies Inc. All rights reserved. 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. Figure 59 shows examples of the commands and Figure 60 shows the available values. HumPROTM Series CSMA Enable Read Command Read Response Header Size Escape Address ACK Address Value 0xFF 0x02 0xFE 0x56 0x0B 0x06 0x56 0x0B V Write Command Header Size Address Value 0xFF 0x02 0x56 0x0B V Figure 59: HumPROTM Series CSMA Enable Command and Response HumPROTM Series CSMA Enable Register Settings V 0x00 0x01 Mode Disable CSMA Enable CSMA Figure 60: HumPROTM Series CSMA Enable Register Settings See the Carrier Sense Multiple Access section for details. 62 63 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. This is the only setting in which the RF circuitry is able to receive and transmit RF messages. Sleep disables all circuitry on-board the module. This is the lowest-power setting available for the module. Please see the Low Power States section for more details. Figure 61 shows examples of the commands and Figure 62 shows the available values. HumPROTM Series Idle Mode Read Command Read Response Header Size Escape Address ACK Address Value 0xFF 0x02 0xFE 0x58 0x0D 0x06 0x58 0x0D V Write Command Header Size Address Value 0xFF 0x02 0x58 0x0D V Figure 61: HumPROTM Series Idle Mode Command and Response HumPROTM Series Idle Mode Register Settings V 0x00 0x01 Mode Awake Sleep Figure 62: HumPROTM Series Idle Mode Register Settings 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. If the SHOWVER register is 1, the ACK is sent after the firmware version. 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 63 shows examples of the commands and Figure 64 shows the available values. HumPROTM Series ACK on Wake Read Command Read Response Header Size Escape Address ACK Address Value 0xFF 0x02 0xFE 0x59 0x0E 0x06 0x59 0x0E V Write Command Header Size Address Value 0xFF 0x02 0x59 0x0E V Figure 63: HumPROTM Series ACK on Wake Command and Response HumPROTM Series ACK on Wake Register Settings V 0x00 0x01 Mode Disable ACK Enable ACK Figure 64: HumPROTM Series ACK on Wake Register Settings 64 65 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. These registers are automatically filled with the source address from a received message if the received message address type matches the value in AUTOADDR. Please see the Addressing Modes section for more details. Each register byte is read and written separately. Figure 65 shows the User Destination ID registers. HumPROTM Series User Destination Address Registers Name Volatile Address Non-Volatile Address Description UDESTID3 UDESTID2 0x5A 0x5B UDESTID1 0x5C UDESTID0 0x5D 0x0F 0x10 0x11 0x12 MSB of the extended destination address Byte 2 of the extended destination address Byte 1 of the extended destination address, MSB of the short destination address LSB of the extended destination address and short destination address Figure 65: HumPROTM Series User Destination Address Registers 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. Please see the Addressing Modes section for more details. Each register byte is read and written separately. Figure 66 shows the User Source ID registers. HumPROTM Series User Source Address Registers Volatile Address Non-Volatile Address Description Name USRCID3 USRCID2 USRCID1 0x5E 0x5F 0x60 USRCID0 0x61 0x13 0x14 0x15 0x16 MSB of the extended source address Byte 2 of the extended source address Byte 1 of the extended source address MSB of the short source address LSB of the extended source address and short source address Figure 66: HumPROTM Series User Source Address Registers 66 67 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 67 shows the User ID Mask registers. HumPROTM Series User ID Mask Registers Name UMASK3 UMASK2 UMASK1 UMASK0 Volatile Address Non-Volatile Address Description 0x62 0x63 0x64 0x65 0x17 0x18 0x19 0x1A MSB of the extended mask Byte 2 of the extended mask Byte 1 of the extended mask MSB of the short mask LSB of the extended mask and short mask Figure 67: HumPROTM Series User ID Mask Registers 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. Figure 68 shows the Destination DSN registers. HumPROTM Series Destination DSN Registers Name DESTDSN3 DESTDSN2 DESTDSN1 DESTDSN0 Volatile Address Non-Volatile Address Description 0x68 0x69 0x6A 0x6B 0x1D 0x1E 0x1F 0x20 MSB of the destination DSN Byte 2 of the destination DSN Byte 1 of the destination DSN LSB of the destination DSN Figure 68: HumPROTM Series Destination DSN Registers EXMASK - Exception Mask Volatile Address = 0x6C; Non-Volatile Address = 0x21 The module has a built-in exception engine that can notify the host processor of an unexpected event. When an exception occurs, this register is ANDed with the exception code. A non-zero result causes the EX line to go high. Reading the EXCEPT register clears the exception and resets the EX line. If the ANDed result is zero, the EX line is not asserted but the exception code is stored in the EXCEPT register. Please see the Exception Engine section for more details. It is recommended to use the EEXMASK registers instead for new designs. Figure 69 shows examples of the commands and Figure 70 shows the available values. HumPROTM Series Exception Mask Read Command Read Response Header Size Escape Address ACK Address Value 0xFF 0x02 0xFE 0x6C 0x21 0x06 0x6C 0x21 V Write Command Header Size Address Value 0xFF 0x02 0x6C 0x21 V Figure 69: HumPROTM Series Transceiver Exception Mask Command and Response HumPROTM Series Example Exception Masks V Exception Name 0x08 0x10 0x20 0x40 0x60 Allows only EX_BUFOVFL and EX_RFOVFL to trigger the EX line Allows only EX_WRITEREGFAILED to trigger the EX line Allows only EX_NORFACK to trigger the EX line Allows only EX_BADCRC, EX_BADHEADER, EX_BADSEQID and EX_ BADFRAMETYPE exceptions to trigger the EX line Allows EX_BADCRC, EX_BADHEADER, EX_BADSEQID, EX_BADFRAMETYPE and EX_NORFACK exceptions to trigger the EX line 0xFF Allows all exceptions to trigger the EX line Figure 70: HumPROTM Series Transceiver Example Exception Masks 68 69 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. This register setting is overridden when PKOPT:RXPKT=1. Figure 71 shows examples of the commands and Figure 72 shows the available values. HumPROTM Series CMD Halts Traffic Read Command Read Response Header Size Escape Address ACK Address Value 0xFF 0x02 0xFE 0x6E 0x23 0x06 0x6E 0x23 V Write Command Header Size Address Value 0xFF 0x02 0x6E 0x23 V Figure 71: HumPROTM Series Transceiver CMD Halts Traffic Command and Response HumPROTM Series CMD Halts Traffic Register Settings V 0x00 0x01 Mode Disable Halt (received data is sent to the UART immediately) Enable Halt (received data is sent when the CMD line is high) Figure 72: HumPROTM Series CMD Halts Traffic Register Settings COMPAT - Compatibility Mode Volatile Address = 0x70; Non-Volatile Address = 0x25 Compatibility mode allows the HumPROTM Series modules to communicate with the 250 Series modules. Please see the Compatibility Mode section for more details. Figure 73 shows examples of the commands and Figure 74 shows the available values. HumPROTM Series Compatibility Mode Read Command Read Response Header Size Escape Address ACK Address Value 0xFF 0x02 0xFE 0x70 0x25 0x06 0x70 0x25 V Write Command Header Size Address Value 0xFF 0x02 0x70 0x25 V Figure 73: HumPROTM Series Transceiver Compatibility Mode Command and Response HumPROTM Series Compatibility Mode Register Settings V 0x00 0x02 0x03 Mode Enable 250 Series Compatibility Mode Enable Normal Addressing Operation Enable Network Addressing Operation Figure 74: HumPROTM Series Compatibility Mode Register Settings 70 71 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. The non-volatile register only uses the lower 4 bits to configure the automatic addressing. The upper 4 bits must be set to 0. The volatile register is split in half with the lower 4 bits configuring the automatic addressing, the same as the non-volatile register. The upper 4 bits indicate the type of the last received packet satisfying the AUTOADDR mask. These bits must be written as 0. This indication is the same as the Addressing Mode register setting. These bits are not used by the module and are only written by the module after successfully receiving a packet. As an example, if AUTOADDR is set to 0x0F (Any Auto Address) and a DSN packet is received from another module, then AUTOADDR reads back as 0x4F. The lower 4 bits (0xF) indicate that the module is set to any auto address (0xF). The upper 4 bits (0x4) indicate that the packet that was just received was a DSN Addressing Mode packet. Figure 75 summarizes the configuration values for the lower 4 bits of the register. Figure 76 shows the Addressing Mode values that the module writes to the upper 4 bits after successfully receiving a packet. HumPROTM Series Auto Addressing Register Settings Auto Address Value Meaning Action 0x00 0x04 0x06 0x07 Auto Addressing disabled DSN Auto Address User Auto Address Mode Destination Registers not populated Auto-populates DSN Address Destination Register Only Auto-populates User Address Destination Register Extended User Auto Address Mode Auto-populates Extended User Address Destination Register 0x0F Any Auto Address Mode Auto-populates DSN Destination or User Address Destination, depending on the received message type. Figure 75: HumPROTM Series Transceiver Auto Addressing Register Settings HumPROTM Series Auto Addressing Mode Indicator Addressing Mode Meaning 0x4 0x6 0x7 DSN Addressing Mode User Addressing Mode Extended User Addressing Mode Figure 76: HumPROTM Series Transceiver Auto Addressing Mode Indicator 72 73 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. CSRSSI - Carrier Sense Minimum RSSI Non-Volatile Address = 0x3F This value is the minimum RSSI that causes the module to wait for a clear channel when CSMA is enabled. Figure 79 shows examples of the commands. HumPROTM Series Carrier Sense Minimum RSSI Read Command Header 0xFF Size 0x02 Write Command Header 0xFF Size 0x02 Escape Address 0xFE 0x3F Address Value 0x3F V Read Response ACK 0x06 Address Value 0x3F V Figure 79: HumPROTM Series Transceiver Carrier Sense Minimum RSSI Command and Response The value is a negative number in twos complement from -128 (0x80) to -1
(0xff). The default value is -70dBm.
!
Warning: The CRSSI value can have a significant impact on the performance of the module. Setting it too low could prevent the module from ever transmitting. Setting it too high can result in transmission collisions. Care must be taken if this value is adjusted. Figure 77 shows the Device Serial Number registers. HumPROTM Series DSN Registers Name MYDSN3 MYDSN2 MYDSN1 MYDSN0 Non-Volatile Address Description 0x34 0x35 0x36 0x37 MSB of the serial number Byte 2 of the serial number Byte 1 of the serial number LSB of the serial number Figure 77: HumPROTM Series DSN Registers CUSTID - Customer ID Non-Volatile Address = 0x39-0x3A These registers contain the factory-programmed customer ID. A unique value is assigned to a specific customer and that value is programmed into that customers modules. The unencrypted User and Extended User Addressing modes use these bytes as part of the addressing. The unique value ensures that the custom modules will not communicate with any other systems. Contact Linx for details. Figure 78 shows the Customer ID registers. HumPROTM Series Customer ID Registers Name CUSTID1 CUSTID0 Non-Volatile Address Description 0x39 0x3A MSB of the customer ID LSB of the customer ID Figure 78: HumPROTM Series Transceiver Customer ID Registers 74 75 RELEASE - Release Number Non-Volatile Address = 0x78 This register contains a number designating the firmware series and hardware platform. Figure 80 shows examples of the commands and Figure 81 lists current releases to date. HumPROTM Series Release Number Read Command Header 0xFF Size 0x02 Escape Address 0xFE 0x78 Read Response ACK 0x06 Address Value 0x78 V Figure 80: HumPROTM Series Transceiver Release Number Command and Response HumPROTM Series Release Number Register Settings V 0x20 0x22 Release Number HUM-900-PRO HUM-868-PRO Figure 81: HumPROTM Series Transceiver Release Number Register Settings A more detailed firmware version is available for versions 0x20 and above in the FWVER register. EXCEPT - Exception Code Volatile Address = 0x79 The module has a built-in exception engine that can notify the host processor of an unexpected event. If an exception occurs, the exception code is stored in this register. Reading from this register clears the exception and resets the EX line. If an exception occurs before the previous exception code is read, the previous value is overwritten. Please see the Exception Engine section for more details. It is recommended to use the EEXFLAG registers for new designs. Figure 82 shows examples of the commands and Figure 83 shows the available values. HumPROTM Series Exception Code Read Command Header 0xFF Size 0x02 Escape Address 0xFE 0x79 Read Response ACK 0x06 Address Value 0x79 V Figure 82: HumPROTM Series Transceiver Exception Code Command and Response HumPROTM Series Transceiver Exception Codes V 0x08 0x09 0x13 0x20 0x40 0x42 0x43 0x44 Exception Name Description EX_BUFOVFL EX_RFOVFL Internal UART buffer overflowed. Internal RF packet buffer overflowed. EX_WRITEREGFAILED Attempted write to register failed. EX_NORFACK Acknowledgement packet not received after maximum number of retries. EX_BADCRC Bad CRC detected on incoming packet. EX_BADHEADER Bad CRC detected in packet header. EX_BADSEQID Sequence ID was incorrect in ACK packet. EX_BADFRAMETYPE Unsupported frame type specified. Figure 83: HumPROTM Series Transceiver Exception Codes 76 77 FWVER - Firmware Version Non-Volatile Address = 0xC0 - 0xC3 These read-only registers contain the firmware version number currently on the module. Each byte is a hexadecimal value: 12 03 01 00 indicates version 18.3.1.0. Each register byte is read separately. Figure 86 shows the Firmware Version registers. HumPROTM Series Firmware Version Registers Name FWVER3 FWVER2 FWVER1 FWVER0 Non-Volatile Address Description 0xC0 0xC1 0xC2 0xC3 Major version number Minor version number Incremental version number Suffix Figure 86: HumPROTM Series Firmware Version Registers Note: Encryption is implemented on modules with FWVER3 = 2 and higher. 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. HumPROTM Series Last Good Packet RSSI Read Command Header 0xFF Size 0x02 Escape Address 0xFE 0x7B Read Response ACK 0x06 Address Value 0x7B V Figure 84: HumPROTM Series Transceiver Last Good Packet RSSI Command and Response ARSSI - Ambient RSSI Volatile Address = 0x7C This register returns the ambient receive signal strength on the current channel in dBm. The signal strength is measured as soon as the command is received. The register value is an 8-bit signed integer representing the RSSI in dBm. It is accurate to 3dB at the high RF data rate, and +3 to
-20 dB at the low RF data rate. The channel being read may be any of the channels in the selected hopping sequence. HumPROTM Series Ambient RSSI Read Command Header 0xFF Size 0x02 Escape Address 0xFE 0x7C Read Response ACK 0x06 Address Value 0x7C V Figure 85: HumPROTM Series Transceiver Ambient RSSI Command and Response 78 79 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 modules operation can become unpredictable. HumPROTM Series Non-Volatile Refresh Cycles Registers Name NVCYCLE1 NVCYCLE0 Non-Volatile Address Description 0xC4 0xC5 MSB of the number of refresh cycles LSB of the number of refresh cycles Figure 87: HumPROTM Series Non-Volatile Refresh Cycles Registers Between 8 and 150 non-volatile write operations can be made before a refresh cycle is necessary. Writing the registers from lowest to highest address maximizes the number of write operations per refresh cycle. It is recommended to write the desired default values to non-volatile memory and use the volatile registers for values that change frequently. These registers show the total number of refresh cycles that have occurred. This gives an indication of the remaining life expectancy of the memory. Figure 87 shows the Non-Volatile Refresh Cycles registers. LSTATUS - Output Line Status Volatile Address = 0xC6 This register contains the logic states of the output indicator lines, providing information to the host processor while using fewer GPIO lines. HumPROTM Series Output Line Status Read Command Header 0xFF Size 0x03 Read Response Escape Escape Address 0xFE 0xFE 0x46 ACK 0x06 Address Value 0xC6 LSTATUS Figure 88: HumPROTM Series Transceiver Output Line Status Command and Response Each bit in the byte that is returned by the read represents the logic state of one of the output indicator lines. Figure 89 shows which line each bit represents. HumPROTM Series Output Line Status LSTATUS Values LSTATUS Bit Line Status 0 1 2 3 4 5 6 7 EX Exception, 1 = exception has occurred PA_EN PA Enable, 1 = the transmitter is active LNA_EN LNA Enable, 1 = the receiver is active CTS Clear To Send, 1 = incoming data buffer near full MODE_IND Mode Indicator, 1 = RF data transfer is active (TX or RX) BE Buffer Empty, 1 = UART buffer is empty Reserved Reserved Figure 89: HumPROTM Series Output Line Status LSTATUS Values 80 81 CMD - Command Register Volatile Address = 0xC7 This volatile write-only register is used to issue special commands. HumPROTM Series Command Register Write Command Header 0xFF Size 0x03 Escape Address Value 0xFE 0x47 V Figure 90: HumPROTM Series Transceiver Command Register Command and Response Value V is chosen from among the options in Figure 91. HumPROTM Series CMD Values CMD Value Operation 0x01 0x02 0x03 0x04 0x05 0x06 0x07 0x10 0x11 0x12 0x13 SENDP Send Packet GETPH Get Packet Header GETPD Get Packet Data GETPHD Get Packet Header and Data CLRRXP Clear Received Packet CLROB Clear Outbound Buffer CLRIB Clear Input Buffer JOINCTL Join Process Control WRKEY Write Key CLRKEY Clear Key RLDKEY Reload Key 0x20 0xAA 0xBB NVRESET Reset non-volatile registers to factory default Figure 91: HumPROTM Series Command Register Values The Send Packet command starts data transmission. Operation differs depending on whether option TXPKT is set in the PKTOPT register. TXPKT = 0; this command operates the same as a data timeout with DATATO. All waiting data, up to the maximum allowed in the remaining channel time, is transmitted. TXPKT = 1; this command marks the end of an explicit packet in the outgoing buffer. All bytes in the packet are transmitted together. Following bytes are sent in the next packet. The max packet length is 192 bytes. Multiple packets can be queued with this command. 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 packet data can be read after completion of the header transfer. If the data is not read before this command is issued a second time, then the packet data is discarded and the header for the following packet is returned. A NACK response is returned if option RXPKT is disabled in the PKTOPT register or the previous GETPx command was not completed. The Get Packet Data command returns the received packet data using a received packet transfer cycle. If the packet header is not read first, then it is discarded. The packet data is then discarded after transfer. A NACK response is returned if option RXPKT is disabled in the PKTOPT register or the previous GETPx command was not completed. The Get Packet Header and Data command returns the received packet header, followed by the packet data using a received packet transfer cycle. The packet is discarded after transfer. A NACK response is returned if option RXPKT is disabled in the PKTOPT register or the previous GETPx command was not completed. The Clear Received Packet command removes the next unread packet from the RF incoming queue if RXPKT is enabled in the PKTOPT register. If the packet header was read but not the data, this command causes the data to be discarded. Although not required before reading the next packets header, it frees buffer space for more or longer messages. If a previous GETPx command did not deliver all the associated data, this command removes the undelivered data and terminates the previous GETPx command. If option RXPKT is disabled this command discards all received data which has not been delivered. The Clear Outbound Buffer command cancels any transmission in progress and clears the buffer of data to be transmitted. The Clear Input Buffer command discards all RF-received bytes and clears the EX_RXWAIT flag. 82 83 The Join Process Control command allows the software to initiate or stop the secure JOIN process. It has the following subcommands. HumPROTM Series JOINCTL Subcommand Values Subcommand Value Operation 0 1 2 Halt JOIN operation Generate a random network key and address. This sets the module as the network administrator (SECOPT:KEYRCV=0) Perform the JOIN operation with another module Figure 92: HumPROTM Series JOINCTL Subcommand Values These operations are equivalent to the push-button initiated operation. If a JOIN operation is started by the serial command (CMD:JOINCTL[2]), push-button operation is ignored until the JOIN operation finishes. Register write operations are inhibited when a JOIN process is active except that a Halt JOIN command is never inhibited. A Halt JOIN operation completes before the ACK is sent. When the JOIN operation 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. The Write Key command writes a 16-byte AES key to the selected key register. As with most of the registers, the encryption key has both volatile and non-volatile registers. The volatile register is used during run time, but is lost on a power cycle or reset. When the module powers up, the volatile register is loaded from the non-volatile register. This makes the non-volatile register value the default on power-up. The key value of all zero bytes is reserved as a no key indication. HumPROTM Series Write Key Command Write Command Header 0xFF Size Size Escape Address 0xFE 0x47 Value 0x11 KeyN KeyN Key0 Key0
... .. Key15 Key15 Figure 93: HumPROTM Series Transceiver Write Key Command Figure 93 shows the command for writing the AES key to the module. If KeyN is 0x01, the command writes to the volatile key register. If it is 0x02, it writes to the non-volatile key register. The Clear Key command sets the selected key to all zeros. Figure 94 shows the structure of this command. HumPROTM Series Clear Key Command Write Command Header 0xFF Size 0x04 Escape Address 0xFE 0x47 Value 0x12 KeyN KeyN Figure 94: HumPROTM Series Transceiver Clear Key Command If KeyN is 0x01, the command clears the volatile key registers. If it is 0x02, it clears the non-volatile key registers. The Reload Key command copies the key in non-volatile memory (NKN) 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. This reset can also be done by toggling the PB line as described in the Restore Factory Defaults section. 84 85 SECSTAT - Security Status Volatile Address = 0xC9 This volatile read-only register provides status of the security features. HumPROTM Series Security Status 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. Read Command Header 0xFF Size 0x03 Escape Escape Address 0xFE 0xFE 0x49 ACK 0x06 Address Value 0xC9 V Read Response HumPROTM Series Join Status Figure 95: HumPROTM Series Transceiver Security Status Command and Response The command returns a single byte. Figure 96 shows the meanings of the bits in the returned value byte. HumPROTM Series Security Status Value Bit 0 1 2 3 4 5 6 7 Status Reserved 0 = No volatile key is set 1 = A volatile key is set 0 = No non-volatile key is set 1 = A non-volatile key is set Reserved Reserved Reserved Reserved Reserved Figure 96: HumPROTM Series Security Status Values Read Command Header 0xFF Size 0x03 Escape Escape Address 0xFE 0xFE 0x4A Read Response ACK 0x06 Address Value 0xCA V Figure 97: HumPROTM Series Transceiver Join Status Command and Response The command returns a single byte. Figure shows the meanings of the returned value byte. HumPROTM Series Join Status Value Bit Status Last Join Result (decimal):
Last Operation Successful 0x00: Module unpaired since restart 0x01: New key generated 0x02: Successfully sent address to another unit 0x03: Successfully sent address and key to another unit 0x04: Successfully obtained key from administrator 0x05: Successfully obtained address from administrator 0x06: Successfully obtained key and address from administrator 0x07: New address generated without key 0x08: New key generated without address 0 - 5 Last Operation Failed 0x0A: Fail: operation canceled 0x0B: Fail: timeout 0x0C: Fail: Invalid Generate Key and Address request 0x0D: Fail: Assignment message didnt contain key 0x0E: Fail: Administrator has no key to send when SECOPT:PSHARE=1 0x0F: Fail: Administrator has no address to send 0x10: Fail: Inconsistent Network Address Registers USRC, UMASK, LASTNETAD 0x11: Fail: LASTNETAD overflow 0x12: Fail: GET_KEY key and address change disabled. Current Operation 0x20: Detecting PB sequence 0x21: Waiting for joining unit 0x22: Another joining unit detected. Joining is in progress. 6
+0x40: JOINACT MODE_IND is active with pairing status, serial write operations are inhibited 86 Figure 98: HumPROTM Series Transceiver Join Status Value 87 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. HumPROTM Series Extended Exception Flags Registers Name EEXFLAG2 EEXFLAG1 EEXFLAG0 Volatile Address Description 0xCD 0xCE 0xCF Byte 2 of the extended exception flags Byte 1 of the extended exception flags LSB of the extended exception flags Figure 99: HumPROTM Series Transceiver Extended Exception Code Registers When an exception occurs, the associated bit is set in this register. If the corresponding bit in the EEXMASK is set and EXMASK is zero, the EX status line is set. Reading an EEXFLAG register does not clear the register. Writing to an EEXFLAG register causes the register to be set to the BIT_AND(current_value, new_value). This provides a way of clearing bits that have been serviced without clearing a bit that has been set since the flag register was read. This prevents a loss of notification of an exception. Register bits can only be cleared, not set, from the write command though some flags are also cleared internally. Unless otherwise noted, exceptions are cleared by writing a zero to the corresponding register bit. Flag EX_TXDONE is set when a data packet has been transmitted. If the packet was sent with acknowledgement enabled, this flag indicates that the acknowledgment has also been received. Flag EX_RXWAIT is 1 when there are buffered incoming data bytes which have not been sent to the UART. It is cleared by reading or discarding all data bytes. Flag EX_UNENCRYPT is 1 when a received packet is not encrypted. This can only occur when SECOPT:EN_UNC=1. Flag EX_SEQDEC is 1 when a received encrypted packet has a smaller sequence number than the previously received packet. Possible causes are an attempt to replay a previous message by an attacker, receiving a message from a different transmitter or restarting the transmitter. 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. Possible causes are an attempt to replay a previous message by an attacker, receiving a message from a different transmitter or restarting the transmitter. HumPROTM Series Transceiver Extended Exception Codes Bit Exception Name Description EEXFLAG0 (0xCF) 0 1 2 3 4 5 6 7 EX_BUFOVFL EX_RFOVFL Internal UART buffer overflowed. Internal RF packet buffer overflowed. EX_WRITEREGFAILED Attempted write to register failed. EX_NORFACK Acknowledgement packet not received after maximum number of retries. EX_BADCRC Bad CRC detected on incoming packet. EX_BADHEADER Bad CRC detected in packet header. EX_BADSEQID Sequence ID was incorrect in ACK packet. EX_BADFRAMETYPE Unsupported frame type specified. EEXFLAG1 (0xCE) 0 1 2 3 4 5 EX_TXDONE EX_RXWAIT EX_UNENCRYPT EX_SEQDEC EX_SEQSKIP EX_JOIN 6 - 7 Reserved EEXFLAG2 (0xCD) 0 - 7 Reserved A data packet has been transmitted. Received data bytes are waiting to be read. Received packet was not encrypted. This can only occur when SECOPT: EN_UNENC=1. Received encrypted packet sequence number is less than previous. Received encrypted sequence number is more than one higher the previous sequence number. A JOIN operation has been started, which can result in register changes and write lockouts. Figure 100: HumPROTM Series Transceiver Extended Exception Codes 88 89 Multiple outgoing packets can be buffered. Changing this option clears the incoming buffer, losing un-transmitted or unacknowledged data. When TXnCMD is 1, lowering the CMD line has the same effect as writing the SENDP command to the CMD register, triggering buffered data to be transmitted. Packet grouping is affected by option TXPKT. The minimum low time on the CMD line to terminate the packet is given in the Electrical Specifications. When RXPKT is 1, incoming packets are held until a GETPH, GETPD, or GETPHD command is written to the CMD register. Transfer uses a Packet Receive transfer. The CMDHOLD setting has no effect. When RXPKT is 0, incoming UART data is delivered without headers. The data flow is controlled by the CMDHOLD setting. When RXP_CTS is 1, the CTS line is used for the status line during a Packet Receive transfer and not for controlling data flow into the module. When it is 0, CTS is used for flow control and CRESP is used for the status line. PKTOPT - Packet Options Volatile Address = 0xD3; Non-Volatile Address = 0x83 This register selects options for transferring packet data. HumPROTM Series Packet Options Read Command Read Response Header Size Escape Escape Address ACK Address Value 0xFF 0x03 0xFE 0xFE 0x53 0x03 0x06 0xD3 0x83 V Write Command Header Size Escape Address Value 0xFF 0x03 0xFE 0x53 0x03 V Figure 101: HumPROTM Series Transceiver Packet Options Command and Response Each bit in the register sets an option as shown in Figure 102. HumPROTM Series Transceiver Packet Option Codes Bit 0 1 2 3 4 - 7 Name TXPKT TXnCMD RXPKT RXP_CTS Reserved Description Packet Transmit Transmit when nCMD Lowered Packet Receive Use CTS for RXPKT Transfer Reserved (must be 0) Figure 102: HumPROTM Series Transceiver Packet Option Codes The TXPKT option allows the module to transmit data in explicit packets. TXPKT = 0 (default); a packet transmission is enabled when the number of waiting bytes reaches BCTRIG bytes, the time since the last received byte exceeds DATATO ms, the number of waiting bytes exceeds the number that can be sent within the remaining slot time, or a Send Packet command is written to the CMD register. TXPKT = 1; all bytes written to the module are held until a SENDP command is written to the CMD register or the CMD line is lowered with TXnCMD = 1. The DATATO or BCTRIG conditions are ignored with this option. The transmitted packet consists of the bytes in the buffer at the time a packet is triggered, even if more data bytes are received before the packet can be sent. 90 91 SECOPT - Security Options Volatile Address = 0xD4; Non-Volatile Address = 0x84 This register selects options for security features. HumPROTM Series Security Options Read Command Read Response Header Size Escape Escape Address ACK Address Value 0xFF 0x03 0xFE 0xFE 0x54 0x04 0x06 0xD4 0x84 V Write Command Header Size Escape Address Value 0xFF 0x03 0xFE 0x54 0x04 V Figure 103: HumPROTM Series Transceiver Packet Options Command and Response Each bit in the register sets an option as shown in Figure 104. Unlike other registers, the non-volatile register (0x84) affects all Join operations. The EN_UNENC bit in the volatile register affects data packet reception. HumPROTM Series Transceiver Security Option Codes Bit Name Description 0 1 2 3 4 5 6 7 PB_RESET Permit factory reset from PB input sequence PSHARE PGKEY Permit key sharing Permit clearing key and changing key CHGADDR Permit changing an address KEYRCV 1: Receive key and address during JOIN operation (node) 0: Send key and address during JOIN operation (admin) EN_UNENC Enable receiving unencrypted packets Reserved Reserved (must be 1) EN_CHANGE Enable changes to security options Figure 104: HumPROTM Series Transceiver Security Option Codes When PB_RESET is 1 the Factory Reset function is enabled from the PB input. This allows a user to reset the module configurations back to the factory defaults with 4 short presses and a 3 second hold of a button connected to the PB input. When PSHARE is 1 the Share Network Key function is enabled during the JOIN process. This allows an administrator to share the encryption key it created. When 0, a JOIN process sends the network address, but no key. 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. 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. When KEYRCV is 1 the module is set to receive a network key from an administrator and act as a node. When it is 0, the module is set as an administrator and sends a network key and assigns an address to the node. In order for this bit to change from 1 to 0, both volatile and non-volatile copies of the network key must be cleared, preventing nodes from being manipulated to transmit the key. This bit is cleared by the GENERATE_KEY push-button function. When EN_UNENC is 1 the module accepts unencrypted packets. If this bit is 0, unencrypted received packets are ignored. When EN_CHANGE is 1, changes are permitted to the SECOPT register, except as noted for KEYRCV changes. Clearing this bit prohibits the following SECOPT changes to enhance security:
1. changing PSHARE from 0 to 1 2. changing EN_CHANGE from 0 to 1. 3. changing EN_UNENC from 0 to 1. An attempt to make a prohibited change causes a NACK command response. When EN_CHANGE is 0, these restrictions can only be removed by resetting the module configuration to the factory default. 92 93 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. HumPROTM Series Extended Exception Mask Registers Name EEXMASK2 EEXMASK1 EEXMASK0 Volatile Address Non-Volatile Address Description 0xD0 0xD1 0xD2 0x80 0x81 0x82 Byte 2 of the extended exception mask Byte 1 of the extended exception mask Byte 0 of the extended exception mask Figure 105: HumPROTM Series Transceiver Extended Exception Mask Registers To use this value, register EXMASK must be zero. If EXMASK is non-zero, this register has no effect on the EX line. When an exception bit is set in EEXFLAG, the corresponding EEXMASK bit is set, and EXMASK is zero, the EX status line is set, otherwise the EX line is reset. Mask bits for unassigned flags should be zero for future compatibility. 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. It is initially set to the administrator address when a network key is generated. HumPROTM Series Extended Exception Mask Registers Name Non-Volatile Address Description LASTNETAD3 LASTNETAD2 LASTNETAD1 LASTNETAD0 0x8C 0x8D 0x8E 0x8F MSB of the last network address assigned Byte 2 of the last network address assigned Byte 1 of the last network address assigned LSB of the last network address assigned Figure 106: HumPROTM Series Transceiver Extended Exception Mask Registers Typical Applications Figure 107 shows a typical circuit using the HumPROTM Series transceiver. RXD TXD GPIO GPIO GPIO INT/GPIO GPIO GPIO VCC GND GND 30 31 32 1 2 3 4 BE NC NC NC NC NC GND VCC GND 9 2 8 2 7 2 6 2 5 2 4 2 3 2 2 2 1 2 B P S T C MODE_IND D N G N E _ A P N E _ A N L T E S E R C C V N I _ A T A D _ D M C T U O _ A T A D _ D M C GND ANT GND GND GND GND GND 20 19 18 17 16 15 14 GND GND GND GND GND GND P S E R C C N C N D N G X E C N C N N W O D _ R E W O P D M C 5 6 7 8 9 0 1 1 1 2 1 3 1 GND Figure 107: HumPROTM Series Transceiver Basic Application Circuit An external microcontroller provides data and configuration commands. Its UART (TXD, RXD) is connected to the modules UART (CMD_DATA_IN, CMD_DATA_OUT). The CTS line is monitored for flow control. GPIOs on the microcontroller are connected to lines on the module:
It monitors the CRESP line to know when the data coming out of the module is transmitted data or a response to a command. It monitors the EX line to know if there is an error. This line may be connected to an interrupt line for faster response. It controls the POWER_DOWN line to place the module into a low power state. It controls the CMD line to toggle between configuration commands and data to be transmitted over the air. The MODE_IND line is connected to an LED for visual indication that the module is active. The PB line is connected to a pushbutton that takes the line to VCC when it is pressed. A resistor pulls the line to ground when the button is not pressed. 94 95 Usage Guidelines for FCC Compliance The pre-certified versions of the HumPROTM Series module
(HUM-900-PRO-UFL and HUM-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. The integrator does not need to conduct any further intentional radiator testing under these rules provided that the following guidelines are met:
An approved antenna must be directly coupled to the modules U.FL connector through an approved coaxial extension cable or to the modules castellation pad using an approved reference design and PCB layer stack. Alternate antennas can be used, but may require the integrator to perform certification testing. The module must not be modified in any way. Coupling of external circuitry must not bypass the provided connectors. End product must be externally labeled with Contains FCC ID:
OJM900MCA / IC: 5840A-900MCA. The end products users manual must contain an FCC statement equivalent to that listed on page 97 of this data guide. The antenna used for this transceiver must not be co-located or operating in conjunction with any other antenna or transmitter. The integrator must not provide any information to the end-user on how to install or remove the module from the end-product. Any changes or modifications not expressly approved by Linx Technologies could void the users authority to operate the equipment. Additional Testing Requirements The HUM-900-PRO-UFL and HUM-900-PRO-CAS have been tested for compliance as an intentional radiator, but the integrator is required to perform unintentional radiator testing on the final product per FCC sections 15.107 and 15.109 and Industry Canada license-exempt RSS standards. Additional product-specific testing might be required. Please contact the FCC or Industry Canada regarding regulatory requirements for the application. Ultimately is it the integrators responsibility to show that their product complies with the regulations applicable to their product.Versions other than the -UFL and -CAS have not been tested and require full compliance testing in the end product as it will go to market. Information to the user The following information must be included in the products user manual. FCC / IC NOTICES This product contains FCC ID: OJM900MCA / IC: 5840A-900MCA. This device complies with Part 15 of the FCC rules and Industry Canada license-exempt RSS standards. Operation of this device is subject to the following two conditions:
1. This device may not cause harmful interference, and 2. this device must accept any interference received, including interference that may cause undesired operation. This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses and can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio communications. However, there is no guarantee that interference will not occur in a particular installation. If this equipment does cause harmful interference to radio or television reception, which can be determined by turning the equipment off and on, the user is encouraged to try to correct the interference by one or more of the following measures:
Reorient or relocate the receiving antenna. Connect the equipment into an outlet on a circuit different from that to which Increase the separation between the equipment and receiver. the receiver is connected. Consult the dealer or an experienced radio/TV technician for help. Any modifications could void the users authority to operate the equipment. Le prsent appareil est conforme aux CNR dIndustrie Canada applicables aux appareils radio exempts de licence. Lexploitation est autorise aux deux conditions suivantes:
1. 2. lappareil ne doit pas produire de brouillage, et utilisateur de lappareil doit accepter tout brouillage radiolectrique subi, mme si le brouillage est susceptible den compromettre le fonctionnement. 96 97 Product Labeling The end product containing the HUM-900-PRO-UFL or HUM-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: OJM900MCA / IC: 5840A-900MCA The label must be permanently affixed to the product and readily visible to the user. Permanently affixed means that the label is etched, engraved, stamped, silkscreened, indelibly printed, or otherwise permanently marked on a permanently attached part of the equipment or on a nameplate of metal, plastic, or other material fastened to the equipment by welding, riveting, or a permanent adhesive. The label must be designed to last the expected lifetime of the equipment in the environment in which the equipment may be operated and must not be readily detachable. FCC RF Exposure Statement To satisfy RF exposure requirements, this device and its antenna must not be co-located or operating in conjunction with any other antenna or transmitter. Antenna Selection Under FCC and Industry Canada regulations, the HUM-900-PRO-UFL and HUM-900-PRO-CAS radio transmitters may only operate using an antenna of a type and maximum (or lesser) gain approved for the transmitter by the FCC and Industry Canada. To reduce potential radio interference to other users, the antenna type and its gain should be so chosen that the equivalent isotropically radiated power (e.i.r.p.) is not more than that necessary for successful communication. The HUM-900-PRO-UFL and HUM-900-PRO-CAS radio transmitters have been approved by the FCC and Industry Canada to operate with the antenna types listed in Figure 108 with the maximum permissible gain and required antenna impedance for each antenna type indicated. Antenna types not included in this list, having a gain greater than the maximum gain indicated for that type, are strictly prohibited for use with this device. Conformment la rglementation dIndustrie Canada, le prsent metteur radio peut fonctionner avec une antenne dun type et dun gain maximal
(ou infrieur) approuv pour lmetteur par Industrie Canada. Dans le but de rduire les risques de brouillage radiolectrique lintention des autres utilisateurs, il faut choisir le type dantenne et son gain de sorte que la puissance isotrope rayonne quivalente (p.i.r.e.) ne dpasse pas lintensit ncessaire ltablissement dune communication satisfaisante. Le prsent metteur radio (HUM-900-PRO-UFL, HUM-900-PRO-CAS) a t approuv par Industrie Canada pour fonctionner avec les types dantenne numrs la Figure 108 et ayant un gain admissible maximal et limpdance requise pour chaque type dantenne. Les types dantenne non inclus dans cette liste, ou dont le gain est suprieur au gain maximal indiqu, sont strictement interdits pour lexploitation de lmetteur. Antennas / Antennes Linx Part Number Rfrence Linx Tested Antennas Type Gain Impedance Impdance Valid For ANT-916-CW-QW Wave Whip ANT-916-CW-HW Wave Dipole Helical ANT-916-PW-LP Wave Whip ANT-916-PW-QW-UFL Wave Whip ANT-916-SP Wave Planar 1.8dBi 1.2dBi 2.4dBi 1.8dBi 1.4dBi ANT-916-WRT-RPS ANT-916-WRT-UFL Wave Dipole Helical 0.1dBi Antennas of the same type and same or lesser gain ANT-916-CW-HD ANT-916-PW-QW ANT-916-CW-RCL ANT-916-CW-RH Wave Whip Wave Whip Wave Whip Wave Whip 0.3dBi 1.8dBi 2.0dBi 1.3dBi ANT-916-CW-HWR-RPS Wave Dipole Helical 1.2dBi ANT-916-PML Wave Dipole Helical 0.4dBi ANT-916-PW-RA Wave Whip ANT-916-USP Cable Assemblies / Assemblages de Cbles Wave Planar 0.0dBi 0.3dBi 50 50 50 50 50 50 50 50 50 50 50 50 50 50 CAS Both CAS UFL CAS CAS UFL Both Both Both Both Both Both CAS CAS Linx Part Number Rfrence Linx Description CSI-RSFB-300-UFFR*
RP-SMA Bulkhead to U.FL with 300mm cable CSI-RSFE-300-UFFR*
RP-SMA External Mount Bulkhead to U.FL with 300mm cable
* Also available in 100mm and 200mm cable length Figure 108: HumPROTM Series Transceiver Approved Antennas 98 99 Castellation Version Reference Design The castellation connection for the antenna on the pre-certified version allows the use of embedded antennas as well as removes the cost of a cable assembly for the u.FL connector. However, the PCB design and layer stack must follow one of the reference designs for the certification on the HUM-900-PRO-CAS to be valid. Figure 109 shows the PCB layer stack that should be used. Figure 110 shows the layout and routing designs for the different antenna options. Please see the antenna data sheets for specific ground plane counterpoise requirements. Layer Name Top Layer Dielectric 1 Mid-Layer 1 Thickness Material Copper 1.4mil FR-4 (Er = 4.6) 14.00mil Copper 1.4mil Dielectric 2 28.00mil FR-4 (Er = 4.6) Mid-Layer 2 Dielectric 3 Bottom Layer 1.4mil 14.00mil 1.4mil Copper FR-4 (Er = 4.6) Copper Figure 109: HumPROTM Series Transceiver Castellation Version Reference Design PCB Stack Note: The PCB design and layer stack for the HUM-900-PRO-CAS must follow these reference designs for the pre-certification to be valid. The HUM-900-PRO-UFL and the HUM-900-PRO-CAS must use one of the antennas in Figure 108 in order for the certification to be valid. The HUM-900-PRO has not been tested and requires full compliance testing in the end product as it will go to market. All modules require unintentional radiator compliance testing in the end product as it will go to market. 1 6 3 5 3 5 3 2 7
. 2 6 0 3 0 0 A M S V E R N O C 0 2 3 9 1 6 0 0 2 5 6 1 5 6 1 0 7 4 0 3 2 0 4 1 0 3 2 P L
-
W P
-
6 1 9
-
T N A
-
A R W P
-
6 1 9
-
T N A 6 1 2 0 8 3 P S
-
6 1 9
-
T N A S P R
-
T R W
-
6 1 9
-
T N A
-
W Q W C
-
6 1 9
-
T N A
-
W H W C
-
6 1 9
-
T N A 1 l i i t m 4 2
=
h d W p i r t s o r c M i r e y a L
-
d M n o i e n a p l d n u o r G s l i m n i e r a s t i n U 100 101 Figure 110: HumPROTM Series Transceiver Castellation Version Reference Design Power Supply Requirements 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 modules performance, so providing a clean power supply for the module should be a high priority during design. 10 Vcc IN Vcc TO MODULE
+
10F Figure 111: Supply Filter A 10 resistor in series with the supply followed by a 10F tantalum capacitor from Vcc to ground helps in cases where the quality of supply power is poor (Figure 111). This filter should be placed close to the modules supply lines. These values may need to be adjusted depending on the noise present on the supply line. Antenna Considerations The choice of antennas is a critical and often overlooked design consideration. The range, performance and legality of an RF link are critically dependent upon the antenna. While adequate antenna performance can often be obtained by trial and error methods, antenna design and matching is a complex task. Professionally designed antennas such as those from Linx (Figure 112) help ensure maximum performance and FCC and other regulatory compliance. Figure 112: Linx Antennas Linx transmitter modules typically have an output power that is higher than the legal limits. This allows the designer to use an inefficient antenna such as a loop trace or helical to meet size, cost or cosmetic requirements and still achieve full legal output power for maximum range. If an efficient antenna is used, then some attenuation of the output power will likely be needed. It is usually best to utilize a basic quarter-wave whip until your prototype product is operating satisfactorily. Other antennas can then be evaluated based on the cost, size and cosmetic requirements of the product. Additional details are in Application Note AN-00500. Interference Considerations The RF spectrum is crowded and the potential for conflict with unwanted sources of RF is very real. While all RF products are at risk from interference, its effects can be minimized by better understanding its characteristics. Interference may come from internal or external sources. The first step is to eliminate interference from noise sources on the board. This means paying careful attention to layout, grounding, filtering and bypassing in order to eliminate all radiated and conducted interference paths. For many products, this is straightforward; however, products containing components such as switching power supplies, motors, crystals and other potential sources of noise must be approached with care. Comparing your own design with a Linx evaluation board can help to determine if and at what level design-specific interference is present. External interference can manifest itself in a variety of ways. Low-level interference produces noise and hashing on the output and reduces the links overall range. High-level interference is caused by nearby products sharing the same frequency or from near-band high-power devices. It can even come from your own products if more than one transmitter is active in the same area. It is important to remember that only one transmitter at a time can occupy a frequency, regardless of the coding of the transmitted signal. This type of interference is less common than those mentioned previously, but in severe cases it can prevent all useful function of the affected device. Although technically not interference, multipath is also a factor to be understood. Multipath is a term used to refer to the signal cancellation effects that occur when RF waves arrive at the receiver in different phase relationships. This effect is a particularly significant factor in interior environments where objects provide many different signal reflection paths. Multipath cancellation results in lowered signal levels at the receiver and shorter useful distances for the link. 102 103 Pad Layout The pad layout diagrams below are designed to facilitate both hand and automated assembly. Figure 113 shows the footprint for the smaller version and Figure 114 shows the footprint for the pre-certified version. 0.520"
0.015"
0.420"
0.015"
0.028"
0.050"
0.070"
Figure 113: HUM-***-PRO Recommended PCB Layout 0.015"
0.060"
0.100"
0.101"
0.136"
0.090"
0.015"
0.028"
0.065"
0.060"
0.420"
0.015"
0.050"
0.070"
Figure 114: HUM-***-PRO-UFL/CAS Recommended PCB Layout Microstrip Details 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 modules antenna can effectively contribute to the length of the antenna, changing its resonant bandwidth. In order to minimize loss and detuning, some form of transmission line between the antenna and the module should be used unless the antenna can be placed very close (<18in) to the module. One common form of transmission line is a coax cable and another is the microstrip. This term refers to a PCB trace running over a ground plane that is designed to serve as a transmission line between the module and the antenna. The width is based on the desired characteristic impedance of the line, the thickness of the PCB and the dielectric constant of the board material. For standard 0.062in thick FR-4 board material, the trace width would be 111 mils. The correct trace width can be calculated for other widths and materials using the information in Figure 115 and examples are provided in Figure 116. Software for calculating microstrip lines is also available on the Linx website. Trace Board Ground plane Figure 115: Microstrip Formulas Example Microstrip Calculations Dielectric Constant Width / Height Ratio (W / d) Effective Dielectric Constant Characteristic Impedance () 4.80 4.00 2.55 1.8 2.0 3.0 3.59 3.07 2.12 50.0 51.0 48.8 104 Figure 116: Example Microstrip Calculations 105 Board Layout Guidelines The modules 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 modules 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 following section provides some basic design guidelines. During prototyping, the module should be soldered to a properly laid-out circuit board. The use of prototyping or perf boards results in poor performance and is strongly discouraged. Likewise, the use of sockets can have a negative impact on the performance of the module and is discouraged. The module should, as much as reasonably possible, be isolated from other components on your PCB, especially high-frequency circuitry such as crystal oscillators, switching power supplies, and high-speed bus lines. When possible, separate RF and digital circuits into different PCB regions. Make sure internal wiring is routed away from the module and antenna and is secured to prevent displacement. Do not route PCB traces directly under the module. There should not be any copper or traces under the module on the same layer as the module, just bare PCB. The underside of the module has traces and vias that could short or couple to traces on the products circuit board. The Pad Layout section shows a typical PCB footprint for the module. A ground plane (as large and uninterrupted as possible) should be placed on a lower layer of your PC board opposite the module. This plane is essential for creating a low impedance return for ground and consistent stripline performance. Use care in routing the RF trace between the module and the antenna or connector. Keep the trace as short as possible. Do not pass it under the module or any other component. Do not route the antenna trace on multiple PCB layers as vias add inductance. Vias are acceptable for tying together ground layers and component grounds and should be used in multiples. The -CAS version must follow the layout in Figure 110. Each of the modules ground pins should have short traces tying immediately to the ground plane through a via. Bypass caps should be low ESR ceramic types and located directly adjacent to the pin they are serving. A 50-ohm coax should be used for connection to an external antenna. A 50-ohm transmission line, such as a microstrip, stripline or coplanar waveguide should be used for routing RF on the PCB. The Microstrip Details section provides additional information. In some instances, a designer may wish to encapsulate or pot the product. There are a wide variety of potting compounds with varying dielectric properties. Since such compounds can considerably impact RF performance and the ability to rework or service the product, it is the responsibility of the designer to evaluate and qualify the impact and suitability of such materials. Helpful Application Notes from Linx It is not the intention of this manual to address in depth many of the issues that should be considered to ensure that the modules function correctly and deliver the maximum possible performance. We recommend reading the application notes listed in Figure 117 which address in depth key areas of RF design and application of Linx products. These applications notes are available online at www.linxtechnologies.com or by contacting the Linx literature department. Helpful Application Note Titles Note Number Note Title AN-00100 AN-00126 AN-00130 AN-00140 AN-00500 AN-00501 RF 101: Information for the RF Challenged Considerations for Operation Within the 902928MHz Band Modulation Techniques for Low-Cost RF Data Links The FCC Road: Part 15 from Concept to Approval Antennas: Design, Application, Performance Understanding Antenna Specifications and Operation Figure 117: Helpful Application Note Titles 106 107 Production Guidelines 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. Soldering Iron Tip Hand Assembly Pads located on the bottom of the module are the primary mounting surface (Figure 118). Since these pads are inaccessible during mounting, castellations that run up the side of the module have been provided to facilitate solder wicking to the modules underside. This allows for very quick hand soldering for prototyping and small volume production. If the recommended pad guidelines have been followed, the pads will protrude slightly past the edge of the module. Use a fine soldering tip to heat the board pad and the castellation, then introduce solder to the pad at the modules edge. The solder will wick underneath the module, providing reliable attachment. Tack one module corner first and then work around the device, taking care not to exceed the times in Figure 119. Solder PCB Pads Castellations Figure 118: Soldering Technique Warning: Pay attention to the absolute maximum solder times. Absolute Maximum Solder Times Hand Solder Temperature: +427C for 10 seconds for lead-free alloys Reflow Oven: +255C max (see Figure 120) Figure 119: Absolute Maximum Solder Times Automated Assembly For high-volume assembly, the modules are generally auto-placed. The modules have been designed to maintain compatibility with reflow processing techniques; however, due to their hybrid nature, certain aspects of the assembly process are far more critical than for other component types. Following are brief discussions of the three primary areas where caution must be observed. Reflow Temperature Profile The single most critical stage in the automated assembly process is the reflow stage. The reflow profile in Figure 120 should not be exceeded because excessive temperatures or transport times during reflow will irreparably damage the modules. Assembly personnel need to pay careful attention to the ovens profile to ensure that it meets the requirements necessary to successfully reflow all components while still remaining within the limits mandated by the modules. The figure below shows the recommended reflow oven profile for the modules. Recommended RoHS Profile Max RoHS Profile Recommended Non-RoHS Profile 255C 235C 217C 185C 180C 125C 300 250 200 150 100 50
) C o
(
t e r u a r e p m e T 0 30 60 90 120 150 180 210 240 270 300 330 360 Time (Seconds) Figure 120: Maximum Reflow Temperature Profile Shock During Reflow Transport Since some internal module components may reflow along with the components placed on the board being assembled, it is imperative that the modules not be subjected to shock or vibration during the time solder is liquid. Should a shock be applied, some internal components could be lifted from their pads, causing the module to not function properly. Washability The modules are wash-resistant, but are not hermetically sealed. Linx recommends wash-free manufacturing; however, the modules can be subjected to a wash cycle provided that a drying time is allowed prior to applying electrical power to the modules. The drying time should be sufficient to allow any moisture that may have migrated into the module to evaporate, thus eliminating the potential for shorting damage during power-up or testing. If the wash contains contaminants, the performance may be adversely affected, even after drying. 108 109 General Antenna Rules The following general rules should help in maximizing antenna performance. 1. Proximity to objects such as a users 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 121). In many cases, this isnt desirable for practical or ergonomic reasons, thus, an alternative antenna style such as a helical, loop or patch may be utilized and the corresponding sacrifice in performance accepted. plane as possible in proximity to the base of the antenna. In cases where the antenna is remotely located or the antenna is not in close proximity to a circuit board, ground plane or grounded metal case, a metal plate may be used to maximize the antennas performance. 5. Remove the antenna as far as possible from potential interference sources. Any frequency of sufficient amplitude to enter the receivers front end will reduce system range and can even prevent reception entirely. Switching power supplies, oscillators or even relays can also be significant sources of potential interference. The single best weapon against such problems is attention to placement and layout. Filter the modules power supply with a high-frequency bypass capacitor. Place adequate ground plane under potential sources of noise to shunt noise to ground and prevent it from coupling to the RF stage. Shield noisy board areas whenever practical. 3. 4. OPTIMUM USABLE NOT RECOMMENDED Figure 121: Ground Plane Orientation 6. CASE If an internal antenna is to be used, keep it away from other metal components, particularly large items like transformers, batteries, PCB tracks and ground planes. In many cases, the space around the antenna is as important as the antenna itself. Objects in close proximity to the antenna can cause direct detuning, while those farther away will alter the antennas symmetry. GROUND PLANE
(MAY BE NEEDED) NUT ANTENNA (MARCONI) VERTICAL /4 GROUNDED In many antenna designs, particularly -wave whips, the ground plane acts as a counterpoise, forming, in essence, a -wave dipole (Figure 122). For this reason, adequate ground plane area is essential. The ground plane can be a metal case or ground-fill areas on a circuit board. Ideally, it should have a surface area less than or equal to the overall length of the -wave radiating element. This is often not practical due to size and configuration constraints. In these instances, a designer must make the best use of the area available to create as much ground GROUND PLANE VIRTUAL /4 DIPOLE DIPOLE ELEMENT
/4
/4 E I In some applications, it is advantageous to place the module and antenna away from the main equipment (Figure 123). This can avoid interference problems and allows the antenna to be oriented for optimum performance. Always use 50 coax, like RG-174, for the remote feed. NOT RECOMMENDED OPTIMUM USABLE CASE GROUND PLANE
(MAY BE NEEDED) NUT Figure 123: Remote Ground Plane Figure 122: Dipole Antenna 110 111 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 124) provides outstanding overall performance and stability. A low-cost whip can be easily fabricated from a wire or rod, but most designers opt for the consistent performance and cosmetic appeal of a professionally-made model. To meet this need, Linx offers a wide variety of straight and reduced height whip style antennas in permanent and connectorized mounting styles. Figure 124: Whip Style Antennas L =
234 FMHz The wavelength of the operational frequency determines an antennas overall length. Since a full wavelength is often quite long, a partial - or -wave antenna is normally employed. Its size and natural radiation resistance make it well matched to Linx modules. The proper length for a straight -wave can be easily determined using the formula in Figure 125. It is also possible to reduce the overall height of the antenna by using a helical winding. This reduces the antennas bandwidth but is a great way to minimize the antennas physical size for compact applications. This also means that the physical appearance is not always an indicator of the antennas frequency. Figure 125:
L = length in feet of quarter-wave length F = operating frequency in megahertz Loop Style A loop or trace style antenna is normally printed directly on a products PCB (Figure 127). This makes it the most cost-effective of antenna styles. The element can be made self-resonant or externally resonated with discrete components, but its actual layout is usually product specific. Despite the cost advantages, loop style antennas are generally inefficient and useful only for short range applications. They are also very sensitive to changes in layout and PCB dielectric, which can cause consistency issues during production. In addition, printed styles are difficult to engineer, requiring the use of expensive equipment including a network analyzer. An improperly designed loop will have a high VSWR at the desired frequency which can cause instability in the RF stage. Figure 127: Loop or Trace Antenna Linx offers low-cost planar (Figure 128) and chip antennas that mount directly to a products PCB. These tiny antennas do not require testing and provide excellent performance despite their small size. They offer a preferable alternative to the often problematic printed antenna. Figure 128: SP Series Splatch and uSP MicroSplatch Antennas Specialty Styles Linx offers a wide variety of specialized antenna styles (Figure 126). Many of these styles utilize helical elements to reduce the overall antenna size while maintaining reasonable performance. A helical antennas bandwidth is often quite narrow and the antenna can detune in proximity to other objects, so care must be exercised in layout and placement. Figure 126: Specialty Style Antennas 112 113 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. When working with RF, a clear distinction must be made between what is technically possible and what is legally acceptable in the country where operation is intended. Many manufacturers have avoided incorporating RF into their products as a result of uncertainty and even fear of the approval and certification process. Here at Linx, our desire is not only to expedite the design process, but also to assist you in achieving a clear idea of what is involved in obtaining the necessary approvals to legally market a completed product. For information about regulatory approval, read AN-00142 on the Linx website or call Linx. Linx designs products with worldwide regulatory approval in mind. In the United States, the approval process is actually quite straightforward. The regulations governing RF devices and the enforcement of them are the responsibility of the Federal Communications Commission (FCC). The regulations are contained in Title 47 of the United States Code of Federal Regulations (CFR). Title 47 is made up of numerous volumes; however, all regulations applicable to this module are contained in Volume 0-19. It is strongly recommended that a copy be obtained from the FCCs website, the Government Printing Office in Washington or from your local government bookstore. Excerpts of applicable sections are included with Linx evaluation kits or may be obtained from the Linx Technologies website, www.linxtechnologies.com. In brief, these rules require that any device that intentionally radiates RF energy be approved, that is, tested for compliance and issued a unique identification number. This is a relatively painless process. Final compliance testing is performed by one of the many independent testing laboratories across the country. Many labs can also provide other certifications that the product may require at the same time, such as UL, CLASS A / B, etc. Once the completed product has passed, an ID number is issued that is to be clearly placed on each product manufactured. Questions regarding interpretations of the Part 2 and Part 15 rules or the measurement procedures used to test intentional radiators such as Linx RF modules for compliance with the technical standards of Part 15 should be addressed to:
Federal Communications Commission Equipment Authorization Division Customer Service Branch, MS 1300F2 7435 Oakland Mills Road Columbia, MD, US 21046 Phone: + 1 301 725 585 | Fax: + 1 301 344 2050 Email: labinfo@fcc.gov ETSI Secretaria 650, Route des Lucioles 06921 Sophia-Antipolis Cedex FRANCE Phone: +33 (0)4 92 94 42 00 Fax: +33 (0)4 93 65 47 16 International approvals are slightly more complex, although Linx modules are designed to allow all international standards to be met. If the end product is to be exported to other countries, contact Linx to determine the specific suitability of the module to the application. All Linx modules are designed with the approval process in mind and thus much of the frustration that is typically experienced with a discrete design is eliminated. Approval is still dependent on many factors, such as the choice of antennas, correct use of the frequency selected and physical packaging. While some extra cost and design effort are required to address these issues, the additional usefulness and profitability added to a product by RF makes the effort more than worthwhile. 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. Values may vary from lot-to-lot and are not guaranteed. Typical parameters can and do vary over lots and application. Linx Technologies makes no guarantee, warranty, or representation regarding the suitability of any product for use in any specific application. It is the customers responsibility to verify the suitability of the part for the intended application. NO LINX PRODUCT IS INTENDED FOR USE IN ANY APPLICATION WHERE THE SAFETY OF LIFE OR PROPERTY IS AT RISK. Linx Technologies DISCLAIMS ALL WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL LINX TECHNOLOGIES BE LIABLE FOR ANY OF CUSTOMERS INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING IN ANY WAY FROM ANY DEFECTIVE OR NON-CONFORMING PRODUCTS OR FOR ANY OTHER BREACH OF CONTRACT BY LINX TECHNOLOGIES. The limitations on Linx Technologies liability are applicable to any and all claims or theories of recovery asserted by Customer, including, without limitation, breach of contract, breach of warranty, strict liability, or negligence. Customer assumes all liability
(including, without limitation, liability for injury to person or property, economic loss, or business interruption) for all claims, including claims from third parties, arising from the use of the Products. The Customer will indemnify, defend, protect, and hold harmless Linx Technologies and its officers, employees, subsidiaries, affiliates, distributors, and representatives from and against all claims, damages, actions, suits, proceedings, demands, assessments, adjustments, costs, and expenses incurred by Linx Technologies as a result of or arising from any Products sold by Linx Technologies to Customer. Under no conditions will Linx Technologies be responsible for losses arising from the use or failure of the device in any application, other than the repair, replacement, or refund limited to the original product purchase price. Devices described in this publication may contain proprietary, patented, or copyrighted techniques, components, or materials. Under no circumstances shall any user be conveyed any license or right to the use or ownership of such items. 2018 Linx Technologies. All rights reserved. The stylized Linx logo, Wireless Made Simple, WiSE, CipherLinx and the stylized CL logo are trademarks of Linx Technologies.
| 1 2 | User Manual - RC | Users Manual | 2.66 MiB |
HumRCTM Series Remote Control and Sensor Transceiver 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. No OEM Linx Remote Control or Function Module should be modified for Life and Property Safety Situations. Such modification cannot provide sufficient safety and will void the products regulatory certification and warranty. Customers may use our (non-Function) Modules, Antenna and Connectors as part of other systems in Life Safety Situations, but only with necessary and industry appropriate redundancies and in compliance with applicable safety standards, including without limitation, ANSI and NFPA standards. It is solely the responsibility of any Linx customer who uses one or more of these products to incorporate appropriate redundancies and safety standards for the Life and Property Safety Situation application. Do not use this or any Linx product to trigger an action directly from the data line or RSSI lines without a protocol or encoder/
decoder to validate the data. Without validation, any signal from another unrelated transmitter in the environment received by the module could inadvertently trigger the action. All RF products are susceptible to RF interference that can prevent communication. RF products without frequency agility or hopping implemented are more subject to interference. This module does have a frequency hopping protocol built in, but the developer should still be aware of the risk of interference. Do not use any Linx product over the limits in this data guide. Excessive voltage or extended operation at the maximum voltage could cause product failure. Exceeding the reflow temperature profile could cause product failure which is not immediately evident. Do not make any physical or electrical modifications to any Linx product. This will void the warranty and regulatory and UL certifications and may cause product failure which is not immediately evident. Table of Contents 1 Description 1 Features 2 Ordering Information 2 Absolute Maximum Ratings 3 Electrical Specifications 6 Typical Performance Graphs 16 Pin Assignments 16 Pin Descriptions 18 Pre-Certified Module Pin Assignments 19 Module Dimensions 20 Theory of Operation 21 Module Description 22 Transceiver Operation 23 Transmit Operation 24 Receive Operation 24 Acknowledgement 25 Automatic Responses 25 Permissions Mask 26 The Pair Process 27 Configuring the Status Lines 27 External Amplifier Control 28 Mode Indicator 28 Reset to Factory Default 29 Using the LVL_ADJ Line 30 Receiver Duty Cycle 32 Using the LATCH_EN Line 32 Using the Low Power Features 33 Triggered Transmissions 34 Frequency Hopping 36 The Command Data Interface 38 Serial Setup Configuration for Stand-alone Operation 40 Basic Hardware Operation 42 Typical Applications 44 Usage Guidelines for FCC and IC Compliance 44 Additional Testing Requirements 45 Information to the user 46 Product Labeling 46 FCC RF Exposure Statement 46 Antenna Selection 48 Castellation Version Reference Design 50 Power Supply Requirements 50 Antenna Considerations 51 Interference Considerations 52 Pad Layout 53 Microstrip Details 54 Board Layout Guidelines 55 Helpful Application Notes from Linx 56 Production Guidelines 56 Hand Assembly 56 Automated Assembly 58 General Antenna Rules 60 Common Antenna Styles 62 Regulatory Considerations 0.55"
(13.97) HumRCTM Series Remote Control and Sensor Transceiver Data Guide Description The HumRC Series transceiver is designed for reliable bi-directional remote control applications. It consists of a highly optimized Frequency Hopping Spread Spectrum (FHSS) RF transceiver and integrated remote control transcoder. The FHSS system allows higher RF output power and, therefore, longer range than narrowband radios. It also provides much more noise immunity than narrowband radios, making the module suitable for use in noisy environments. Eight status lines can be set up in any combination of inputs and outputs for the transfer of button or contact states. A selectable acknowledgement indicates that the transmission was successfully received. Versions are available in the 902 to 928MHz and 2,400 to 2,483MHz frequency bands. Figure 1: Package Dimensions 0.45"
(11.43) 0.07"
(1.78) Primary settings are hardware-selectable, which eliminates the need for an external microcontroller or other digital interface. For advanced features, optional software configuration is provided by a UART interface; however, no programming is required for basic operation. Housed in a compact reflow-compatible SMD package, the transceiver requires no external RF components except an antenna, which greatly simplifies integration and lowers assembly costs. Features Low power consumption 232 possible addresses 8 status lines Bi-directional remote control Analog voltage and sensor inputs Low power receive modes Selectable acknowledgements No external RF components required No programming/tuning required Serial interface for optional software operation/configuration Tiny PLCC-32 footprint 1 Revised 8/15/2019 Ordering Information Ordering Information Part Number HUM-***-RC HUM-900-RC-UFL HUM-900-RC-CAS Description HumRC Series Remote Control Transceiver HumRC Series Remote Control Transceiver, Certified, UFL Connector HumRC Series Remote Control Transceiver, Certified, Castellation Connection EVM-***-RC HumRC Series Carrier Board EVM-900-RC-UFL EVM-900-RC-CAS MDEV-***-RC EVAL-***-RC HumRC Series Carrier Board with Certified module, UFL Connector HumRC Series Carrier Board with Certified module, Castellation Connection HumRC Series Master Development System HumRC Series Basic Evaluation Kit
*** = Frequency; 900MHz, 2.4GHz Figure 2: Ordering Information Absolute Maximum Ratings Absolute Maximum Ratings Supply Voltage Vcc Any Input or Output Pin RF Input Operating Temperature Storage Temperature 0.3 0.3 40 40 to to 0 to to
+3.9 VCC + 0.3
+85
+85 VDC VDC dBm C C Exceeding any of the limits of this section may lead to permanent damage to the device. Furthermore, extended operation at these maximum ratings may reduce the life of this device. Figure 3: Absolute Maximum Ratings Warning: This product incorporates numerous static-sensitive components. Always wear an ESD wrist strap and observe proper ESD handling procedures when working with this device. Failure to observe this precaution may result in module damage or failure. 2 Electrical Specifications HumRC Series Transceiver Specifications Parameter Power Supply Symbol Min. Typ. Max. Units Notes Operating Voltage Peak TX Supply Current VCC lCCTX 2.0 3.6 VDC 2.4GHz at +1dBm 2.4GHz at 10dBm 900MHz at +10dBm 900MHz at 0dBm Average TX Supply Current 2.4GHz at +1dBm 900MHz at +10dBm RX Supply Current Standby Current Power-Down Current RF Section Operating Frequency Band HUM-2.4-RC HUM-900-RC-ttt Number of Channels Channel Spacing HUM-2.4-RC HUM-900-RC-ttt Modulation Rate Receiver Section Spurious Emissions Receiver Sensitivity HUM-2.4-RC HUM-900-RC-ttt RSSI Dynamic Range Transmitter Section Output Power HUM-2.4-RC HUM-900-RC-ttt Harmonic Emissions lCCRX lSBY lPDN FC PO PH 2400 902 95 94 0
+8.5 3 28 19 36 22 22 27.5 25.5 0.5 0.5 25 2.03 500 38.4 99 98 85
+1
+9.5 41 29 20 38.5 24 24 28.5 28 1.4 1.4 mA mA mA mA mA mA mA A A 1,2 1,2 1,2 1,2 1,2 1,2 1,2,3 1,2 1,2 MHz 2483.5 MHz 928 MHz MHz kHz kbps
-47 dBm 5 5 5 6 6 6 dBm dBm dB dBm dBm dBc HumRC Series Transceiver Specifications Symbol Min. Typ. Max. Units Notes Parameter Output Power Control Range HUM-2.4-RC HUM-900-RC-ttt Antenna Port RF Impedance Environmental RIN Operating Temp. Range 40 Timing Module Turn-On Time Via VCC Via POWER_DOWN Via Standby Serial Command Response Status, Volatile R/W Analog Input Reading NV Update, Factory Reset IU to RU Status High Channel Dwell Time Interface Section Input Logic Low Logic High Output Logic Low, MODE_IND, CONFIRM Logic High, MODE_IND, CONFIRM Logic Low Logic High VIL VIH VOLM VOHM VOL VOH 0.7*VCC 0.7*VCC 0.7*VCC 56 40 50 1 6 80 6 6 4 4 4 4 4 8 8 8 7 dB dB C ms ms ms ms ms ms ms ms
+85 108 57 57 10 16 110 50 13.33 0.3*VCC VDC VDC 0.3*VCC VDC VDC 0.3*VCC 1,9 1,9 1,10 1,10 VON TX Vcc TX Sx TX MODE_IND RX Sx RX MODE_IND A B C D E F G H AB TX Power up Response <80ms HumRCTM Series Transceiver Timings TX Response from VCC or POWER_DOWN1,4 TX Response from Status line while IU in idle2 Item Description BC RX Initial Response 8 to 50ms with no interference CD Data Settle 4 to 8us EF Data Update Delay During Active Session 5 to 25ms EG Shutdown Duration 25 to 342ms GH RX MODE_IND Drop 6 to 8ms TX Response from Status line while IU / RU idle in RX3 AB RX Initial Response BC CD EF EG GH Data Settle Data Update Delay During Active Session Shutdown Duration RX MODE_IND Drop Minimum Maximum 8ms 12ms 1ms 50ms 8s 25ms 342ms 8ms 4ms 4s 5ms 25ms 6ms 1. 2. 3. From module off to VCC applied The module is set as an IU only and is in idle pending status line activation The module is set as an IU and RU and is idling in receive mode pending status line activation or receipt of a valid packet. 4. Maximum 80ms if VCC < 2.6V Figure 5: HumRCTM Series Timings Input power < 60dBm 1. Measured at 3.3V VCC 2. Measured at 25C 3. 4. Characterized but not tested 5. PER = 5%
6. Into a 50-ohm load 7. No RF interference 8. From end of command to start of response 9. 60mA source/sink 10. 6mA source/sink Figure 4: Electrical Specifications 4 5 Typical Performance Graphs
) m B d
(
r e w o P t t u p u O X T 5.00 0.00
-5.00
-10.00
-15.00
-20.00
-25.00
-30.00 0.00 0.25 0.50 0.75 1.00 1.25 1.50 1.75 2.00 2.25 2.50 2.75 3.00 3.25 3.30 5.0 4.0 3.0 2.0 1.0 0.0
) m B d
(
r e w o P t u p t u O r e t t i m s n a r T
-1.0 2.0 2.5 3.3 Supply Voltage (V) Figure 6: HumRCTM Series Transceiver Output Power vs. LVL_ADJ Resistance - HUM-2.4-RC LVL_ADJ Voltage (V) Figure 8: HumRCTM Series Transceiver Max Output Power vs. Supply Voltage - HUM-2.4-RC
) m B d
(
r e w o P t t u p u O X T 15.00 10.00 5.00 0.00
-5.00
-10.00
-15.00
-20.00
-25.00 0.00 0.08 0.15 0.23 0.30 0.38 0.45 0.53 0.61 0.68 0.76 0.83 0.91 0.98 1.00 LVL_ADJ Voltage (V) Figure 7: HumRCTM Series Transceiver Output Power vs. LVL_ADJ Resistance - HUM-900-RC
) m B d
(
r e w o P t u p t u O X T 11.0 10.5 10.0 9.5 9.0 8.5 2.0 2.5 3.3 Supply Voltage (V) Figure 9: HumRCTM Series Transceiver Max Output Power vs. Supply Voltage - HUM-900-RC
-40C 25C 85C 3.6
-40C 25C 85C 3.6 6 7
) A m
(
t n e r r u C y p p u S l 25C 85C
-40C 29.0 27.0 25.0 23.0 21.0 19.0 17.0 15.0
) A m
(
t n e r r u C y p p u S l 85C 25C
-40C 31.0 29.0 27.0 25.0 23.0 21.0 19.0 17.0 15.0
-35.0
-30.0
-25.0
-20.0
-15.0
-10.0
-5.0 0.0 5.0 10.0
-35.0
-30.0
-25.0
-20.0
-15.0
-10.0
-5.0 0.0 5.0 10.0 TX Output Power (dBm) TX Output Power (dBm) Figure 10: HumRCTM Series Transceiver Average Current vs. Transmitter Output Power at 2.5V - HUM-2.4-RC Figure 13: HumRCTM Series Transceiver Average TX Current vs. Transmitter Output Power at 3.3V - HUM-2.4-RC
) A m
(
t n e r r u C y p p u S l 40.0 35.0 30.0 25.0 20.0 15.0 85C
-40C 25C
) A m
(
t n e r r u C y p p u S l 40.0 35.0 30.0 25.0 20.0 15.0 85C
-40C 25C
-30.0
-25.0
-20.0
-15.0
-10.0
-5.0 0.0 5.0 10.0 15.0 TX Output Power (dBm)
-30.0
-25.0
-20.0
-15.0
-10.0
-5.0 0.0 5.0 10.0 15.0 TX Output Power (dBm) Figure 11: HumRCTM Series Transceiver Average Current vs. Transmitter Output Power at 2.5V - HUM-900-RC Figure 12: HumRCTM Series Transceiver Average TX Current vs. Transmitter Output Power at 3.3V - HUM-900-RC 8 9
) A m
(
t n e r r u C y p p u S l 29.0 28.5 28.0 27.5 27.0 26.5 26.0 85C
-40C 25C 2.0 2.5 3.3 3.6 Supply Voltage (V)
) A m
(
t n e r r u C y p p u S l 28.5 28.3 28.1 27.9 27.7 27.5 27.3 27.1 26.9 26.7 26.5 2.0 85C
-40C 25C 2.5 3.3 Supply Voltage (V) 3.6 Figure 14: HumRCTM Series Transceiver TX Current vs. Supply Voltage at Max Power - HUM-2.4-RC Figure 16: HumRCTM Series Transceiver TX Current vs. Supply Voltage at 0dBm - HUM-2.4-RC
) A m
(
t n e r r u C y p p u S l 39.5 39.0 38.5 38.0 37.5 37.0 36.5 36.0 35.5 2.0
-40C 25C 85C 2.5 3.3 Supply Voltage (V) 3.6 23.5 23.0 22.5 22.0 21.5 21.0 20.5
) A m
(
t n e r r u C y p p u S l 2.0
-40C 25C 85C 2.5 3.3 Supply Voltage (V) 3.6 Figure 15: HumRCTM Series Transceiver TX Current vs. Supply Voltage at Max Power - HUM-900-RC Figure 17: HumRCTM Series Transceiver TX Current vs. Supply Voltage at 0dBm - HUM-900-RC 10 11
) A m
(
t n e r r u C y p p u S l 27.00 26.50 26.00 25.50 25.00 24.50 24.00 23.50 23.00 85C 25C
-40C 10.00
) A m
(
t n e r r u C X R e g a r e v A 1.00 0.10 0.01 2.5V 3.3V 3.6V 2 2.1 2.2 2.3 2.4 2.5 2.6 2.7 2.8 2.9 3 3.1 3.2 3.3 3.4 3.5 3.6 0 15 30 45 60 75 90 105 120 135 150 165 180 195 210 225 240 255 Supply Voltage (V) Duty Cycle (s) Figure 18: HumRCTM Series Transceiver RX Current Consumption vs. Supply Voltage - HUM-2.4-RC Figure 20: HumRCTM Series Transceiver Average RX Current Consumption vs. Duty Cycle - HUM-2.4-RC
) A m
(
t n e r r u C y p p u S l 25.00 24.50 24.00 23.50 23.00 22.50 22.00 2 85C 25C
-40C
) A m
(
t n e r r u C X R e g a r e v A 10.00 1.00 0.10 0.01 2.5V 3.3V 3.6V 2.1 2.2 2.3 2.4 2.5 2.6 2.7 2.8 2.9 3 Supply Voltage (V) 3.1 3.2 3.3 3.4 3.5 3.6 0 15 30 45 60 75 90 105 120 135 150 165 180 195 210 225 240 255 Duty Cycle (s) Figure 19: HumRCTM Series Transceiver RX Current Consumption vs. Supply Voltage - HUM-900-RC Figure 21: HumRCTM Series Transceiver Average RX Current Consumption vs. Duty Cycle - HUM-900-RC 12 13
-40C 25C 85C
) m B d
(
i g n d a e R I S S R
-15.00
-25.00
-35.00
-45.00
-55.00
-65.00
-75.00
-85.00
-95.00
-105.00
-100.00 -90.00 -80.00 -70.00 -60.00 -50.00 -40.00 -30.00 -20.00 -10.00 0.00 Input Power (dBm)
) A
(
t n e r r u C y b d n a S t 1.80 1.60 1.40 1.20 1.00 0.80 0.60 0.40 0.20 0.00 2.5 85C 25C
-40C 3.3 Supply Voltage (V) Figure 22: HumRCTM Series Transceiver RSSI Voltage vs. Input Power - HUM-2.4-RC Figure 24: HumRCTM Series Transceiver Standby Current Consumption vs. Supply Voltage - HUM-2.4-RC
) m B d
(
i g n d a e R I S S R
-15.00
-25.00
-35.00
-45.00
-55.00
-65.00
-75.00
-85.00
-95.00
-105.00
-40C 25C 85C
-100.00 -90.00 -80.00 -70.00 -60.00 -50.00 -40.00 -30.00 -20.00 -10.00 0.00 Input Power (dBm)
) A
(
t n e r r u C y b d n a S t 1.40 1.20 1.00 0.80 0.60 0.40 0.20 0.00 2.5 85C 25C
-40C 3.3 Supply Voltage (V) Figure 23: HumRCTM Series Transceiver RSSI Voltage vs. Input Power - HUM-900-RC Figure 25: HumRCTM Series Transceiver Standby Current Consumption vs. Supply Voltage - HUM-900-RC 3.6 3.6 14 15 Pin Assignments T U O _ A T A D _ D M C I N _ A T A D _ D M C N E _ K C A I R A P N E _ A N L T E S E R N E _ A P D N G C C V 29 28 27 26 25 24 23 22 21 MODE_IND ACK_OUT LVL_ADJ S7 S6 S5 S4 30 31 32 1 2 3 4 20 19 18 17 16 15 14 GND ANT GND GND GND GND GND 5 6 78 9 10 11 12 13 3 S 2 S 1 S 0 S 0 C 1 C D N G N E _ H C T A L N W O D _ R E W O P Figure 26: HumRCTM Series Transceiver Pin Assignments (Top View) Pin Descriptions Pin Descriptions Pin Number Name I/O Description 1, 2, 3, 4, 5, 6, 7, 8 9, 14, 15, 16, 17, 18, 20, 25 S0S71 I/O Status Lines. Each line can be configured as either an input to register button or contact closures or as an output to control application circuitry. GND Ground 10 11 C0 C1 I I This line sets the input/output direction for status lines S0-S3. When low, the lines are outputs; when high they are inputs. This line sets the input/output direction for status lines S4-S7. When low, the lines are outputs; when high they are inputs. Pin Descriptions Pin Number Name I/O Description 12 POWER_DOWN I I Power Down. Pulling this line low places the module into a low-power state. The module is not functional in this state. Pull high for normal operation. Do not leave floating. 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). LATCH_EN ANTENNA 50-ohm RF Antenna Port VCC Supply Voltage RESET2 LNA_EN PA_EN I 0 O This line resets the module when pulled low. It should be pulled high for normal operation. Low Noise Amplifier Enable. This line is driven high when receiving. It is intended to activate an optional external LNA. Power Amplifier Enable. This line is driven high when transmitting. It is intended to activate an optional external power amplifier. CMD_DATA_OUT O Command Data Out. Output line for the serial interface commands CMD_DATA_IN ACK_EN PAIR 1 MODE_IND ACK_OUT LVL_ADJ Command Data In. Input line for the serial interface commands. If serial control is not used, this line should be tied to supply to minimize current consumption. Pull this line high to enable the module to send an acknowledgement message after a valid control message has been received. A high on this line initiates the Pair process, which causes two units to accept each others transmissions. It is also used with a special sequence to reset the module to factory default configuration. This line indicates module activity. It can source enough current to drive a small LED, causing it to flash. The duration of the flashes indicates the modules current state. This line goes high when the module receives an acknowledgement message from another module after sending a control message. Level Adjust. The voltage on this line sets the transmitter output power level. I I I O O I 13 19 21 22 23 24 26 27 28 29 30 31 32 1. 2. These lines have an internal 20k pull-down resistor These lines have an internal 10k pull-up resistor Figure 27: HumRCTM Series Transceiver Pin Descriptions 16 17 Pre-Certified Module Pin Assignments The pre-certified version of the module has mostly the same pin assignments as the standard version. The antenna connection is routed to either a castellation (-CAS) or a u.FL connector (-UFL), depending on the part number ordered. Module Dimensions 0.55"
(13.97) T U O _ A T A D _ D M C I N _ A T A D _ D M C N E _ K C A I R A P N E _ A N L T E S E R N E _ A P D N G C C V 29 28 27 26 25 24 23 22 21 MODE_IND ACK_OUT LVL_ADJ S7 S6 S5 S4 30 31 32 1 2 3 4 5 6 78 9 10 11 12 13 3 S 2 S 1 S 0 S 0 C 1 C D N G N E _ H C T A L N W O D _ R E W O P T N A 19 D N G 18 NC Figure 28: HumRCTM Series Transceiver Pre-certified Version Pin Assignments - Castellation Connection (Top View) T U O _ A T A D _ D M C I N _ A T A D _ D M C N E _ K C A I R A P N E _ A N L T E S E R N E _ A P D N G C C V 29 28 27 26 25 24 23 22 21 MODE_IND ACK_OUT LVL_ADJ S7 S6 S5 S4 30 31 32 1 2 3 4 5 6 78 9 10 11 12 13 3 S 2 S 1 S 0 S 0 C 1 C D N G N E _ H C T A L N W O D _ R E W O P C N 19 D N G 18 ANT 0.45"
(11.43) Figure 30: HumRCTM Series Transceiver Dimensions 0.07"
(1.78) 0.812"
(20.62) 0.45"
(11.43) 0.116"
(2.95) Figure 31: HumRCTM Series Transceiver Pre-certified Version Dimensions Figure 29: HumRCTM Series Transceiver Pre-certified Version Pin Assignments - UFL Connection (Top View) 18 19 Theory of Operation The HumRCTM Series transceiver is a low-cost, high-performance synthesized FSK transceiver. Figure 32 shows the modules block diagram. ANTENNA ADC ADC R O T A L U D O M E D 0 90 FREQ SYNTH MODULATOR LNA PA PROCESSOR INTERFACE GPIO /
INTERFACE Figure 32: HumRCTM Series Transceiver RF Section Block Diagram The HumRCTM Series transceiver operates in the 2400 to 2483MHz and 902 to 928MHz frequency bands. The transmitter output power is programmable. The range varies depending on the modules frequency band, antenna implementation and the local RF environment. The RF carrier is generated directly by a frequency synthesizer that includes an on-chip VCO. The received RF signal is amplified by a low noise amplifier (LNA) and down-converted to I/Q quadrature signals. The I/Q signals are digitized by ADCs. A low-power onboard communications processor performs the radio control and management functions including Automatic Gain Control
(AGC), filtering, demodulation and packet synchronization. A control processor performs the higher level functions and controls the serial and hardware interfaces. A crystal oscillator generates the reference frequency for the synthesizer and clocks for the ADCs and the processor. Module Description The HumRCTM Series Remote Control module is a completely integrated RF transceiver and processor. It has two main modes of operation: hardware and software. Hardware operation is suitable for applications like keyfobs where no other processor, PC or interface is present. Software operation is more advanced and allows for more features and functionality. This guide focuses on hardware operation with some references to software operation. Please see Reference Guide RG-00104: the HumRCTM Series Command Data Interface for details on software operation. Since this module can act as both transmitter and receiver, terminology and descriptions can get confusing. This guide uses the term Initiating Unit (IU) to describe a module that is transmitting commands. Responding Unit (RU) is used to describe a module that is receiving commands. The module has 8 status lines numbered S0 through S7. These can be set as inputs for buttons or contacts or as outputs to drive application circuitry. When S0 is taken high on the IU, S0 goes high on the RU, and so forth. A line that is an input on one side needs to be set as an output on the other side. Up to two of the lines S4, S5, S6 and S7 can be configured as analog inputs through the Command Data Interface. The voltage on an analog input can be transmitted upon activation of a digital input, or automatically sent in response to a query from an IU. These are ideal for sensor-based applications. A trigger configuration provides self-timed periodic or limited-length transmission when an input goes high. The transceiver uses a Frequency Hopping Spread Spectrum (FHSS) algorithm. This allows for higher output power and longer range than narrow-band systems while still maintaining regulatory compliance. All aspects of managing the FHSS operations are automatically handled by the module. Each module is programmed with a unique 32-bit serial number at the factory. By default, this is used as the modules local address. The address can be changed through the Command Data Interface so that the module can be given a specific local address. The serial number cannot be changed. 20 21 Transceiver Operation The transceiver has two modes of operation: 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. The module stays in a low power sleep mode until a status line goes high, starting the Transmit Operation. If all of the status lines are set as outputs, then the module is set as an RU only. It stays in Receive Operation looking for a valid transmission from a paired IU. A module with both input and output status lines can operate as an IU and an RU. The module idles in Receive Operation until either a valid transmission is received or a status line input goes high, initiating the Transmit operation. When an input goes high, the transceiver captures the logic state of each of the status lines. The line states are placed into a packet along with the local 32-bit address. The IU transmits the control packets as it hops among 25 RF channels. An RU receives the packet and checks its Paired Module List to see if the IU has been paired with the module and is authorized to control it. If the IUs address is not in the table, then the RU ignores the transmission. If the address is in the table, then the RU calculates the channel hopping pattern from the IUs address and sets its status line outputs according to the received packet. It then hops along with the IU and updates the states of its outputs with every packet. Its outputs can be connected to external circuitry that activates when the lines go high. The RU can also send an acknowledgement back to the IU. Using the serial interface the RU can include up to two bytes of custom data with the acknowledgement, such as sensor data or battery voltage levels. Using the hardware control, if ACK_EN is high when a valid control packet is received, the RU sends back a simple acknowledgement (ACK). It can send an Acknowledge with Data (AWD) response when custom data is programmed into the module using a serial command. Transmit Operation Transmit operation can be started by a status line input going high or a serial command. Basic remote control applications use the status line activation. The module pulls the MODE_IND line high and repeatedly transmits control messages containing the local address and the state of all status lines. Between transmissions the module listens for acknowledgement messages. If an Acknowledge (ACK) or Acknowledge with Data (AWD) message is received for the transmitted data, the ACK_OUT line is asserted for 100ms. The ACK_OUT timing restarts on each ACK or AWD packet that is received. The transceiver sends control messages every 13.33ms as long as any of the status line inputs is high, updating the status line states with each packet. When all input lines are low, the module starts the shutoff sequence. During the shutoff sequence, the transmitter sends at least one packet with all outputs off. It then continues to transmit data until the current channel hopping cycle is complete, resulting in balanced channel use. If an input line is asserted during the shutoff sequence, the transmitter cancels the shutoff and extends the transmission sequence. The Transmit Control Data and Transmit IU Packet serial commands instruct the module to send control messages. The Transmit Control Data command is the serial command version of taking a status line input high. An external microcontroller can use this command to send a specified number of packets with a specified Status byte rather than taking status lines high. The Transmit IU Packet command sends a packet that causes the RU to respond with a packet that can include the readings of its two analog inputs. This is good for reading remote sensors without having a microcontroller on the sensor unit. This reduces the cost and development time for remote sensor units. The trigger configuration causes the module to send a pre-specified number of packets when a status line input goes high. This is good for remote monitoring and transmitting when an exception occurs without needing a microcontroller on the remote unit. 22 23 Receive Operation During Receive Operation, the module waits for a valid control message from an authorized (paired) transceiver. When a valid message is received, it locks onto the hopping pattern of the transmitter and asserts the MODE_ IND line. It compares the received status line states to the Permission Mask for the IU to see if the IU is authorized to activate the lines. The module sets all authorized outputs to match the received states. Only status line outputs are affected by received commands. The RU then checks the state of the ACK_EN line and transmits an acknowledgement packet if it is high. It looks for the next valid packet while maintaining the frequency hopping timing. As long as an RU is receiving valid commands from a paired IU, it will not respond to any other unit. Once eight consecutive packets are missed, the RU is logically disconnected from the IU and waits for the next valid packet from any IU. Acknowledgement 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. When the Responding Unit (RU) receives a valid Control Packet, it checks the state of the ACK_EN line. If it is high the module sends an Acknowledgement Packet. If the Initiating Unit (IU) receives an Acknowledgement Packet that has the same Address and Status Byte as in the Control Packet it originally sent, then it pulls the ACK_OUT line high. A continuous stream of Control Packets that triggers a continuous stream of Acknowledgement Packets keeps the ACK_OUT line high. Connecting the ACK_EN line to VCC causes the RU to transmit Acknowledgement Packets as soon as it receives a valid Control Packet. Alternately this line can be controlled by an external circuit that raises the line when a specific action has taken place. This confirms to the IU that the action took place rather than just acknowledging receipt of the signal. The module can also be configured to transmit an acknowledgement with two bytes of preset data. This feature is enabled using the Control Source parameter through the Command Data Interface (CDI). The IU outputs the received bytes on its CDI for presentation to an external microcontroller or computer. The data can include sensor values, battery voltage levels or current status line states. Note: Only one RU should be enabled to transmit an acknowledgement response for a given IU since multiple acknowledgements will interfere with each other. Automatic Responses Two of the status lines can be configured as analog inputs to measure voltage levels. An IU can send a Request Sample command to an RU to respond with the analog measurements in the acknowledgement. This allows a master unit to remotely read a sensor device without having to place a microcontroller on the sensor. The transceiver can be configured to respond with one or both analog values through the CDI. Please see Reference Guide RG-00104: the HumRC Series Command Data Interface for details on the CDI. Permissions Mask The HumRCTM Series Transceiver has a Permissions Mask in the RU that is used to control which status lines an IU is authorized to control. With most systems, if a transmitter is associated with a receiver then it has full control over the receiver. With the Permissions Mask, a transmitter can be granted authority to control only certain receiver outputs. If an IU does not have the authority to activate a certain line, then the RU does not set it. As an example, a factory worker can be given a fob that only opens the door to the factory floor while the CEO has a fob that can also open the executive offices. The hardware in the fobs is the same, but the permissions masks are set differently for each fob. The Pair process always sets the Permission Mask to full access. The mask can be changed through the serial interface. 24 25 The Pair Process The Pair process enables two transceivers to communicate with each other. Each transceiver has a local 32-bit address that is transmitted with every packet. If the address in the received packet is not in the RUs Paired Module List, then the transceiver does not respond. Adding devices to the authorized list is accomplished through the Pair process or by a serial command. Each module can be paired with up to 40 other modules. The Pair process is initiated by taking the PAIR line high or by sending the Pair Control serial command on both units to be associated. Activation on the PAIR line can either be a momentary pulse (less than two seconds) or a sustained high input, which can be used to extend the search and successful pairing display. With a momentary activation, the search is terminated after 30 seconds. If Pairing is initiated with a sustained high input, the search continues as long as the PAIR input is high. When Pair is activated, the module displays the Pair Search sequence on the MODE_IND line (Figure 34) and goes into a search mode where it looks for another module that is also in search mode. It alternates between transmit and receive, enabling one unit to find the other and respond. Once bidirectional communication is established, the two units store each others addresses in their Paired Module List with full Permissions Mask and display the Pair Found sequence on their MODE_IND lines. The Pair Found sequence is displayed for at least 3 seconds. If PAIR is held high, the Pair Found display is shown for as long as PAIR is high. If a paired unit is already in the Paired Module List, then no additional entry is added though the existing entrys Permissions Mask may be modified. When Pairing is initiated, the module pairs with the first unit it finds that is also in Pair Search. If multiple systems are being Paired in the same area, such as in a production environment, then steps should be taken to ensure that the correct units are paired with each other. The Pair process can be cancelled by taking PAIR high a second time or by issuing the Pair Control command with Cancel Pairing option. If the address table is full when the PAIR line is raised, the Pair Table Full sequence is displayed on the MODE_IND line for 10 seconds and neither of the Pairing units stores an address. In this case, the module should either be reset to clear the address table or the serial interface can be used to remove addresses. Configuring the Status Lines Each of the eight status lines can operate as a digital input or output. Configuring their direction can be done in two ways. Basic operation uses the C0 and C1 lines. When C0 is low, S0 through S3 are outputs; when C0 is high, S0 through S3 are inputs. Likewise when C1 is low, S4 through S7 are outputs; when C1 is high, S4 through S7 are inputs. This is shown in Figure 33. Status Line Direction Configuration Line C0 C1 0 1 S0 through S3 are outputs S0 through S3 are inputs S4 through S7 are outputs S4 through S7 are inputs Figure 33: MODE_IND Timing Advanced operation uses the CDI to set each line direction individually with the Status Line I/O Mask item. In addition, the Control Source Item is used to tell the module to use the serial command instead of the hardware line configuration. Up to two of the status lines in the S4 through S7 group can be configured as analog inputs. An analog input line is used only for reading an input line voltage and converting it to a digital value (Analog to Digital Conversion, ADC). The analog input selection is primary, overriding digital input/output selection. An analog input reading can be transmitted to another module when functioning as either an IU or RU. The digitized reading must be read through a serial command at the receiving end. The analog setting is configured through the CDI using the Analog Input Select item. Please see Reference Guide RG-00104: the HumRCTM Series Command Data Interface for details on the CDI. External Amplifier Control The HumRCTM Series transceiver has two output lines that are designed to control external amplifiers. The PA_EN line goes high when the module enters transmit mode. This can be used to activate an external power amplifier to boost the signal strength of the transmitter. The LNA_EN line goes high when the module enters receive mode. This can be used to activate an external low noise amplifier to boost the receiver sensitivity. These external amplifiers can significantly increase the range of the system at the expense of higher current consumption and system cost. 26 27 Mode Indicator The Mode Indicator line (MODE_IND) provides feedback about the current state of the module. This line switches at different rates depending on the modules current operation. When an LED is connected to this line it blinks, providing a visual indication to the user. Figure 34 gives the definitions of the MODE_IND timings. MODE_IND Timing Module Status Display Transmit Mode Solid ON when transmitting packets. Receive Mode Solid ON when receiving packets. Pair Search Pair Found Pair Error Remote Pair Error ON for 100ms, OFF for 900ms while searching for another unit during the Pair process ON for 400ms, OFF for 100ms when the transceiver has been Paired with another transceiver. This is displayed for at least 3 seconds. ON for 100ms, OFF for 100ms when the address table is full and another unit cannot be added. ON for 100ms, OFF for 100ms, ON for 100ms OFF for 300ms when the remote units address table is full and a Pair cannot be completed. Pair Cancelled ON for 100ms, OFF for 200ms, ON for 100ms when the Pair process is cancelled. Reset Acknowledgement ON for 600ms, OFF for 100ms, ON for 200ms, OFF for 100ms, ON for 200ms and OFF for 100ms when the reset sequence is recognized. Extended Pair Cancelled Solid ON when the pairing operation is cancelled and waiting for the PAIR line to go low. Figure 34: MODE_IND Timing Reset to Factory Default The transceiver is reset to factory default by taking the Pair line high briefly 4 times, then taking and holding Pair 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 the Reset Acknowledgement defined in Figure 34 until the PAIR line goes low. After the Reset Acknowledgement is shown and PAIR goes low, the configuration is initialized. Factory reset also clears the Paired Module table but does not change the local address. If the PAIR input timing doesnt match the reset sequence timing an Extended Pair Cancel sequence is shown when PAIR goes low. The module reverts to normal operation without a reset or pairing. Using the LVL_ADJ Line The Level Adjust (LVL_ADJ) line allows the transceivers output power to be easily adjusted for range control or lower power consumption. This is done by placing a voltage on the LVL_ADJ line. This can be done using a voltage divider or a voltage source. When the transceiver powers up, the voltage on this line is measured and the output power level is set accordingly. When LVL_ADJ is connected to VCC, the output power and current consumption are the highest. When connected to ground, the output power and current are the lowest. See the Typical Performance Graphs section (Figure 6) for a graph of the output power vs. LVL_ADJ voltage. Even in designs where attenuation is not anticipated, it is a good idea to place resistor pads connected to LVL_ADJ so that it can be used if needed. Figure 35 shows the voltages needed to set each power level and gives the approximate output power for each level. The output power levels are approximate and may vary part-to-part. Power Level vs. LVL_ADJ Voltage Ratio VLVL_ADJ/VCC ratio POUT @ 915MHz POUT @ 2.4GHz 0.00 0.08 0.15 0.23 0.30 0.38 0.45 0.53 0.61 0.68 0.76 0.83 0.91 0.98 1.00 19.83 15.46 15.48 10.59 10.60 6.05 6.03 0.95 0.96 4.30 4.29 6.66 9.84 9.84 9.83 27.96 26.50 24.88 21.32 18.74 16.94 14.66 10.82 9.26 7.39 5.26 1.99 0.57 1.73 1.73 Figure 35: Power Level vs. LVL_ADJ Voltage Voltage Ratio 28 29 Receiver Duty Cycle The module can be configured to automatically power on and off while in receive mode. Instead of being powered on all the time looking for transmissions from an IU, the receiver can wake up, look for data and go back to sleep for a configurable amount of time. If it wakes up and receives valid data, then it stays on and goes back to sleep when the data stops. This significantly reduces the amount of current consumed by the receiver. It also increases the time from activating the IU to getting a response from the RU. The duty cycle is controlled by the Duty Cycle serial command through the CDI. DCycle sets the number of seconds between receiver turn-on points as shown in Figure 36. DCycle TON TSBY ON Standby KeepOn Activity Figure 20 and Figure 21 show graphs of the average current consumption vs. duty cycle for several supply voltages. They show that the average current consumption can be significantly reduced with even a small duty cycle value. This is ideal for battery-powered applications that need infrequent updates or where response time is not critical. The KeepOn time is used to keep the receiver on after it has completed some activity. This activity includes completing a transmission and receiving a valid packet. After KeepOn seconds have elapsed with no transmit or valid receive activity, the module resumes duty cycle operation by going into standby for DCycle seconds. Please see Reference Guide RG-00104: the HumRCTM Series Command Data Interface for details on configuring the receiver duty cycle. Figure 36: Receiver Duty Cycle The modules average current consumption can be calculated with the following equation.
) +
DCycle
(
T
(
T AVG SBY SBY ON RX
=
) I I I Figure 37: Receiver Duty Cycle Average Current Consumption Equation TON is fixed at about 0.326 seconds and TSBY = DCycle - TON. The receiver current (IRX) and standby current (ISBY) vary with supply voltage, but some typical values are in Figure 38. HumRCTM Series Typical Current Consumption HUM-2.4-RC HUM-900-RC VCC
(VDC) IRX
(mA) ISBY
(mA) IRX
(mA) ISBY
(mA) 2.5 21.45 3.3 21.82 3.6 22.03 0.00040 0.00058 0.00063 22.94 23.73 24.02 0.00040 0.00058 0.00063 Figure 38: HumRCTM Series Transceiver Typical Current Consumption 30 31 Using the LATCH_EN Line The LATCH_EN line sets the outputs to either momentary operation or latched operation. During momentary operation the outputs go high for as long as control messages are received instructing the module to take the lines high. As soon as the control messages stop, the outputs go low. During latched operation, when a signal is received to make a particular status line high, it remains high until a separate activation is received to make it go low. The transmission must stop and the module must time out before it will register a second transmission and toggle the outputs. When the LATCH_EN line is high, all of the outputs are latched. A serial command is available to configure latching of individual lines. Using the Low Power Features The Power Down (POWER_DOWN) line can be used to completely power down the transceiver module without the need for an external switch. This line allows easy control of the transceiver power state from external components, such as a microcontroller. The module is not functional while in power down mode. If all of the status lines are configured as inputs, then the module operates as an IU only. It automatically goes into a low power state waiting for one of the inputs to be asserted. This conserves battery power until a transmission is required. Triggered Transmissions The HumRCTM Series Transceiver has a triggered transmission feature configured through the serial interface. This causes the IU to transmit messages as soon as a configured status line input goes high, but stop transmissions based on configuration selection. The logic allows timed or periodic transmissions for simple transmit-on-event conditions without an external microcontroller or other timing logic. This reduces the required energy and potential interference with other RF units when automatically transmitting. The configuration options are:
1. Transmission occurs as long as input is high. This is the same as normal, non-triggered operation. 2. Transmission lasts for the specified duration after a high-going edge, then stops until the next high-going edge (fixed ON period). 3. Transmission starts when an input goes high, stopping when the input goes low or the specified duration elapses, whichever occurs first. The transmission wont occur again until the input goes low, then high. 4. Transmission is periodic, with configured duration and interval, as long as the trigger status line is high (periodic ON when trigger is high). 5. The transmission terminates under conditions 14 above, or when an ACK is received. After an ACK no further trigger transmission occurs until the triggered status line goes low, then high again. 6. The transmission is periodic, like condition 4, but each transmission duration is terminated by receiving an acknowledgement. A status input not selected for trigger timing operates normally, transmitting as long as the input is high. It doesnt affect the timing of periodic transmissions, causing the two transmission requests to be logically ORed. Receiving control messages during the off period of a triggered periodic transmission can delay, but doesnt cancel periodic transmission. If there are multiple lines with edge triggers, they are logically ORed together to generate a single trigger signal. Please see Reference Guide RG-00104: the HumRCTM Series Command Data Interface for details on configuring triggered transmissions. 32 33 Frequency Hopping The module incorporates a Frequency Hopping Spread Spectrum (FHSS) algorithm. This provides immunity from narrow-band interference and complies with FCC and IC guidelines. The module uses 25 RF channels as shown in Figure 39. Each channel has a time slot of 13.33ms before the module hops to the next channel. This equal spacing allows a receiver to hop to the next channel at the correct time even if a packet is missed. Up to seven consecutive packets can be missed without losing synchronization. The hopping pattern (sequence of transmit channels) is determined from the transmitters address. Each sequence uses all 25 channels, but in different orders. Once a transmission starts, the module continues through a complete cycle. If the input line is taken low in the middle of a cycle, the module continues transmitting through the end of the cycle to ensure balanced use of all channels. Frequency hopping has several advantages over single channel operation. Hopping systems are allowed a higher transmitter output power, which results in longer range and better performance within that range. Since the transmission is moving among multiple channels, interference on one channel causes loss on that channel but does not corrupt the entire link. This improves the reliability of the system. Channel Frequencies Channel Number HUM-2.4-RC Frequency (MHz) HUM-900-RC Frequency (MHz) 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 2,420.25 2,422.25 2,424.25 2,426.25 2,428.25 2,430.25 2,432.25 2,434.25 2,436.25 2,438.25 2,440.25 2,442.25 2,444.25 2,446.25 2,448.25 2,450.25 2,452.25 2,454.25 2,456.25 2,458.25 2,460.25 2,462.25 2,464.25 2,466.25 2,468.25 Figure 39: HumRCTM Series Transceiver RF Channel Frequencies 902.750 903.250 903.750 904.250 904.750 905.249 905.749 906.249 906.749 907.249 907.749 908.249 908.749 909.248 909.748 910.248 910.748 911.248 911.748 912.248 912.748 913.247 913.747 914.247 914.747 34 35 The Command Data Interface The HumRCTM Series transceiver has a serial Command Data Interface
(CDI) that offers the option to configure and control the transceiver through software instead of through hardware. This interface consists of a standard UART with a serial command set. This allows for fewer connections in applications controlled by a microcontroller as well as for more control and advanced features than can be offered through hardware pins alone. The CMD_DATA_IN and CMD_DATA_OUT connect to the modules UART. An automatic baud rate detection system allows the interface to run at a variable data rate from 9.0kbps to 60.0kbps, covering standard rates from 9.6 to 57.6kbps. The Command Data Interface has two sets of operators. One is a set of commands that performs specific tasks and the other is a set of parameters that are for module configuration and status reporting. The HumRCTM Series Transceiver Command Data Interface Reference Guide has full details on each command. Some key features available with the serial interface are:
Configure the module through software instead of setting the hardware lines. Change the output power, providing the ability to lower power consumption when signal levels are good and extend battery life. Individually set which status lines are inputs and outputs. Individually set status line outputs to operate as momentary or latched. Add or remove specific paired devices. Individually set Permission Masks that prevent certain paired devices from activating certain status line outputs. Change the modules local address for production or tracking purposes or to replace a lost or broken product. Put the module into a low power state to conserve battery power. Activate an automatic receiver duty cycle to conserve battery power. Receive the entire control message serially instead of needing to monitor individual status lines. Get the IU address for logging access attempts. Receive control messages from unpaired modules, allowing for expansion of the system beyond the maximum of 40 paired units. Access control and address validation can be undertaken by an external processor or PC with more memory than the module. Serially configure and control acknowledge messages. Send and receive 2 bytes (16 bits) of custom data with each command message and acknowledge message. Serially initiate transmission of control messages instead of triggering the status line inputs. Set interrupts to notify an external processor when specific events occur, such as receiving a control message. Read out the RSSI value for the last received packet and the current ambient RF level. Query a remote unit to respond with its analog input voltage measurements. Configure the module to send triggered control messages that automatically stop transmitting based on the settings, conserving battery power. The serial interface offers a great deal of flexibility for more complicated designs. Please see Reference Guide RG-00104: the HumRCTM Series Command Data Interface for details on the CDI. Lists of the serial commands and parameters are shown in Figure 40 and Figure 41 for reference. 36 37 Serial Setup Configuration for Stand-alone Operation The serial interface offers access to a number of advanced features that cannot be controlled through hardware configuration alone. However, not all products need or use a microcontroller or processor, but would benefit from some of the advanced features. Many of the configuration settings can be written once and then used by the module thereafter. This allows the modules to be configured through a temporary serial connection and then operate in a stand-alone fashion without a permanent serial connection. For example, a product can have a small header or connector so that the serial lines can be connected to a PC in production test. The PC writes the configurations required by the application to the module and is then disconnected. The module uses these configurations in its normal operation. Command Data Interface Commands Command Description Read Write Read NV Program Set Default Configuration Read the current value in volatile memory. If there is no volatile value, then the non-volatile value is returned. Write a new value to volatile memory. Read the value in non-volatile memory. Program a new value to non-volatile memory. Set all configuration items to their factory default values. Erase All Addresses Erase all paired addresses from memory. Transmit Control Data Transmit a control message. Transmit ACK Transmit an acknowledgement for received data. Transmit AWD Transmit an Acknowledge With Data (AWD) response with two bytes of custom data. Transmit IU Packet Transmit a general IU packet. NV Update Pair Control Write all NV changes to NV memory Initiate / Cancel RF Pairing with another module Figure 40: HumRCTM Series Transceiver Command Data Interface Commands Command Data Interface Parameters Parameter Description Device Name NULL-terminated string of up to 16 characters that identifies the module. Read only. Firmware Version 2 byte firmware version. Read only. Serial Number Local Address 4 byte factory-set serial number. Read only. The modules 32-bit local address. Status Line I/O Mask Status lines direction (1 = Inputs, 0 = Outputs), LSB = S0, used when enabled by Control Source. Latch Mask TX Power Level Latching enable for output lines, LSB = S0, used when enabled by Control Source. TX output power, signed nominal dBm, used when enabled by Control Source. Control Source Configures the control options. Message Select Select message types to capture for serial readout. Analog Input Select Define analog sources, averaging, reference, and offset for analog readings. Custom Data Source Source of transmitted custom data. Paired Module Descriptor Sets the address and permissions mask of paired modules. Trigger Operation Input Trigger operation. Receiver Duty Cycle Receiver Duty Cycle control. I/O Lines Read the current state of the status and control lines. Read only. RSSI LADJ Read the RSSI of the last packet received and ambient level. Read only. Read the voltage on the LVL_ADJ line. Read only. Module Status Read the operating status of the module. Read only. Captured Receive Packet Interrupt Mask Read the last received packet. Read only. Sets the mask for events to generate a break on CMD_DATA_ OUT. Event Flags Event flags that are used with the Interrupt Mask. Analog Input Reading Readout of the analog input lines. Read only. Trigger Input Status Status of Trigger Inputs. Read only. Pairing Status Status of Last Pair attempt since power-up. Read only. Figure 41: HumRCTM Series Transceiver Command Data Interface Parameters 38 39 Basic Hardware Operation The following steps describe how to use the HumRCTM Series module with hardware only. Basic application circuits that correspond to these steps are shown in Figure 42. 1. Set the C0 and C1 lines opposite on both sides. 2. Press the PAIR button on both sides. The MODE_IND LED begins flashing slowly to indicate that the module is searching for another module. 3. Once the pairing is complete, the MODE_IND LED flashes quickly to indicate that the pairing was successful. 4. The modules are now paired and ready for normal use. 5. Pressing a status line button on one module (the IU) activates the corresponding status line output on the second module (the RU). 6. Taking the ACK_EN line high on the RU causes the module to send an acknowledgement to the IU. The ACK_OUT line on the IU goes high to indicate that the acknowledgement has been received. Tying the line to Vcc causes the module to send an acknowledgement as soon as a command message is received. This is suitable for basic remote control or command systems. No programming is necessary for basic hardware operation. The Typical Applications section shows additional example schematics for using the modules. The Command Data Interface section describes the more advanced features that are available with the serial interface. VCC VCC VCC GND VCC GND 9 2 8 2 7 2 6 2 5 2 4 2 3 2 2 2 1 2 D N G N E _ A P N E _ A N L T E S E R C C V N E _ K C A I R A P MODE_IND ACK_OUT LVL_ADJ I N _ A T A D _ D M C T U O _ A T A D _ D M C S7 S6 S5 S4 3 S 2 S 1 S 0 S D N G 0 C 1 C N W O D _ R E W O P N E _ H C T A L 5 6 7 8 9 0 1 1 1 2 1 3 1 GND VCC GND VCC GND GND ANT GND GND GND GND GND 20 19 18 17 16 15 14 GND GND GND GND GND GND VCC VCC VCC VCC VCC VCC VCC GND VCC GND 9 2 8 2 7 2 6 2 5 2 4 2 3 2 2 2 1 2 D N G N E _ A P N E _ A N L T E S E R C C V N E _ K C A I R A P MODE_IND ACK_OUT LVL_ADJ I N _ A T A D _ D M C T U O _ A T A D _ D M C S7 S6 S5 S4 3 S 2 S 1 S 0 S D N G 0 C 1 C N W O D _ R E W O P N E _ H C T A L 5 6 7 8 9 0 1 1 1 2 1 3 1 3 S 2 S 1 S 0 S GND GND VCC VCC GND GND ANT GND GND GND GND GND 20 19 18 17 16 15 14 GND GND GND GND GND GND S7 S6 S5 S4 30 31 32 1 2 3 4 30 31 32 1 2 3 4 GND GND VCC GND A B GND GND VCC GND VCC VCC VCC VCC 40 41 Figure 42: HumRCTM Series Transceiver Basic Application Circuits for Bi-directional Remote Control Typical Applications Figure 43 and Figure 44 show circuits using the HumRCTM Series transceiver. VCC VCC VCC VCC VCC GND 9 2 8 2 7 2 6 2 5 2 4 2 3 2 2 2 1 2 GND VCC GND GND VCC GND 30 31 32 1 2 3 4 GND GND VCC GND S7 S6 S5 S4 N E _ K C A I N _ A T A D _ D M C 9 2 T U O _ A T A D _ D M C I R A P MODE_IND ACK_OUT LVL_ADJ VCC VCC D N G N E _ A P 7 2 8 2 N E _ A N L 6 2 GND T E S E R 5 2 C C V 4 2 D N G N E _ K C A N I _ A T A D _ D M C T U O _ A T A D _ D M C 3 2 GND N ANT E _ A N GND L N E _ A P GND GND GND GND N W O D _ R E W O P N E _ H C T A L I R A P MODE_IND ACK_OUT LVL_ADJ S7 S6 S5 S7 S4 S6 30 31 32 1 2 S5 S4 3 S 3 2 S 4 5 6 S7 S6 S5 1 S S4 7 D N G 0 S 0 C 1 C 8 9 0 1 1 1 2 1 3 1 3 S 2 GND S 1 S 0 S VCC GND VCC GND 0 C 1 C D N G GND 20 19 18 17 16 15 14 GND GND GND GND GND GND 1 2 2 2 20 GND T 19 E S E 18 R 17 16 15 14 N W O D _ R E W O P C C V GND GND GND ANT GND GND GND GND GND GND GND GND N E _ H C T A L RXD TXD GPIO GPIO GPIO RXD TXD GPIO VCC GPIO GPIO GND GND VCC GND VCC VCC VCC VCC GND GND VCC GND VCC VCC VCC VCC VCC GND 9 2 8 2 7 2 6 2 5 2 4 2 3 2 2 2 1 2 30 31 32 1 2 3 4 VCC R A P I MODE_IND ACK_OUT LVL_ADJ S7 S6 S5 S4 3 S N E _ K C A 30 31 32 1 2 3 2 S 4 I N _ A T A D _ D M C T U O _ A T A D _ D M C I R A P MODE_IND ACK_OUT LVL_ADJ S7 S6 D N G N E _ A P 9 2 8 2 7 2 6 2 N E _ A N L GND C C V 5 2 T E S E R N E _ K C A N I _ A T A D _ D M C T U O _ A T A D _ D M C 4 2 3 2 D N G GND N ANT E _ A P GND N E _ A N L GND GND GND GND N W O D _ R E W O P N E _ H C T A L S5 1 S 0 S D N G 0 C 1 C 5 6 7 S4 8 3 S 2 S 1 S 0 S 9 0 1 1 1 2 1 3 GND S 2 GND VCC S 1 S 0 S 3 1 D N G GND 0 C 1 C GND VCC 1 2 GND C C V GND GND GND ANT GND GND GND GND GND GND GND GND N E _ H C T A L 2 2 20 T 19 E S E 18 R 17 16 15 14 N W O D _ R E W O P GND 20 19 18 17 16 15 14 GND GND GND GND GND GND 5 6 7 8 9 0 1 1 1 2 1 3 1 3 S 2 S 1 S 0 S GND GND VCC GND Figure 44: HumRCTM Series Transceiver Typical Application Circuit with External Microprocessor In this example, C0 is low and C1 is high, so S0S3 are outputs and S4S7 are inputs. This is inverted from the circuit in Figure 43 making it the matching device. In this circuit, the Command Data Interface is connected to a microcontroller for using some of the advanced features. The microcontroller controls the state of the ACK_EN line. It can receive a command, perform an action and then take the line high to send Acknowledgement packets. This lets the user on the other end know that the action took place and not just that the command was received. 5 6 7 8 9 0 1 1 1 2 1 3 1 GND VCC GND VCC GND VCC VCC VCC VCC VCC VCC VCC VCC Figure 43: HumRCTM Series Transceiver Basic Application Circuit In this example, C0 is high and C1 is low, so S0S3 are inputs and S4S7 are outputs. The inputs are connected to buttons that pull the lines high and weak pull-down resistors to keep the lines from floating when the buttons are not pressed. The outputs would be connected to external application circuitry. LATCH_EN is low, so the outputs are momentary. The Command Data Interface is not used in this design, so CMD_DATA_IN is tied high and CMD_DATA_OUT is not connected. ACK_OUT and MODE_IND are connected to LEDs to provide visual indication to the user. PAIR is connected to a button and pull-down resistor to initiate the Pair Process when the button is pressed. ACK_EN is tied high so the module sends acknowledgements as soon as it receives a control message. 42 43 Usage Guidelines for FCC and IC Compliance The pre-certified versions of the HumRCTM Series module
(HUM-900-RC-UFL and HUM-900-RC-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. The integrator does not need to conduct any further intentional radiator testing under these rules provided that the following guidelines are met:
An approved antenna must be directly coupled to the modules U.FL connector through an approved coaxial extension cable or to the modules castellation pad using an approved reference design and PCB layer stack. Alternate antennas can be used, but may require the integrator to perform certification testing. The module must not be modified in any way. Coupling of external circuitry must not bypass the provided connectors. End product must be externally labeled with Contains FCC ID:
OJM900MCA / IC: 5840A-900MCA. The end products users manual must contain an FCC statement equivalent to that listed on page page 45 of this data guide. The antenna used for this transceiver must not be co-located or operating in conjunction with any other antenna or transmitter. The integrator must not provide any information to the end-user on how to install or remove the module from the end-product. Any changes or modifications not expressly approved by Linx Technologies could void the users authority to operate the equipment. Additional Testing Requirements The HUM-900-RC-UFL and HUM-900-RC-CAS modules have been tested for compliance as an intentional radiator, but the integrator is required to perform unintentional radiator testing on the final product per FCC sections 15.107 and 15.109 and Industry Canada license-exempt RSS standards. Additional product-specific testing might be required. Please contact the FCC or Industry Canada regarding regulatory requirements for the application. Ultimately is it the integrators responsibility to show that their product complies with the regulations applicable to their product. Versions other than the -UFL and -CAS have not been tested and require full compliance testing in the end product as it will go to market. Information to the user The following information must be included in the products user manual. FCC / IC NOTICES This product contains FCC ID: OJM900MCA / IC: 5840A-900MCA. This device complies with Part 15 of the FCC rules and Industry Canada license-exempt RSS standards. Operation of this device is subject to the following two conditions:
1. This device may not cause harmful interference, and 2. this device must accept any interference received, including interference that may cause undesired operation. This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses and can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio communications. However, there is no guarantee that interference will not occur in a particular installation. If this equipment does cause harmful interference to radio or television reception, which can be determined by turning the equipment off and on, the user is encouraged to try to correct the interference by one or more of the following measures:
Reorient or relocate the receiving antenna. Connect the equipment into an outlet on a circuit different from that to which Increase the separation between the equipment and receiver. the receiver is connected. Consult the dealer or an experienced radio/TV technician for help. Any modifications could void the users authority to operate the equipment. Le prsent appareil est conforme aux CNR dIndustrie Canada applicables aux appareils radio exempts de licence. Lexploitation est autorise aux deux conditions suivantes:
1. 2. lappareil ne doit pas produire de brouillage, et utilisateur de lappareil doit accepter tout brouillage radiolectrique subi, mme si le brouillage est susceptible den compromettre le fonctionnement. 44 45 Product Labeling The end product containing the HUM-900-RC-UFL or HUM-900-RC-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. Permanently affixed means that the label is etched, engraved, stamped, silkscreened, indelibly printed, or otherwise permanently marked on a permanently attached part of the equipment or on a nameplate of metal, plastic, or other material fastened to the equipment by welding, riveting, or a permanent adhesive. The label must be designed to last the expected lifetime of the equipment in the environment in which the equipment may be operated and must not be readily detachable. FCC RF Exposure Statement To satisfy RF exposure requirements, this device and its antenna must not be co-located or operating in conjunction with any other antenna or transmitter. Antenna Selection Under FCC and Industry Canada regulations, the HUM-900-RC-UFL and HUM-900-RC-CAS radio transmitters may only operate using an antenna of a type and maximum (or lesser) gain approved for the transmitter by the FCC and Industry Canada. To reduce potential radio interference to other users, the antenna type and its gain should be so chosen that the equivalent isotropically radiated power (e.i.r.p.) is not more than that necessary for successful communication. The HUM-900-RC-UFL and HUM-900-RC-CAS radio transmitters have been approved by the FCC and Industry Canada to operate with the antenna types listed in Figure 45 with the maximum permissible gain and required antenna impedance for each antenna type indicated. Antenna types not included in this list, having a gain greater than the maximum gain indicated for that type, are strictly prohibited for use with this device. Conformment la rglementation dIndustrie Canada, le prsent metteur radio peut fonctionner avec une antenne dun type et dun gain maximal
(ou infrieur) approuv pour lmetteur par Industrie Canada. Dans le but de rduire les risques de brouillage radiolectrique lintention des autres utilisateurs, il faut choisir le type dantenne et son gain de sorte que la puissance isotrope rayonne quivalente (p.i.r.e.) ne dpasse pas lintensit ncessaire ltablissement dune communication satisfaisante. Le prsent metteur radio (HUM-900-RC-UFL, HUM-900-RC-CAS) a t approuv par Industrie Canada pour fonctionner avec les types dantenne numrs la Figure 45 et ayant un gain admissible maximal et limpdance requise pour chaque type dantenne. Les types dantenne non inclus dans cette liste, ou dont le gain est suprieur au gain maximal indiqu, sont strictement interdits pour lexploitation de lmetteur. Antennas / Antennes Linx Part Number Rfrence Linx Tested Antennas Type Gain Impedance Impdance Valid For ANT-916-CW-QW Wave Whip ANT-916-CW-HW Wave Dipole Helical ANT-916-PW-LP Wave Whip ANT-916-PW-QW-UFL Wave Whip ANT-916-SP Wave Planar 1.8dBi 1.2dBi 2.4dBi 1.8dBi 1.4dBi ANT-916-WRT-RPS ANT-916-WRT-UFL Wave Dipole Helical 0.1dBi Antennas of the same type and same or lesser gain ANT-916-CW-HD ANT-916-PW-QW ANT-916-CW-RCL ANT-916-CW-RH Wave Whip Wave Whip Wave Whip Wave Whip 0.3dBi 1.8dBi 2.0dBi 1.3dBi ANT-916-CW-HWR-RPS Wave Dipole Helical 1.2dBi ANT-916-PML Wave Dipole Helical 0.4dBi ANT-916-PW-RA Wave Whip ANT-916-USP Cable Assemblies / Assemblages de Cbles Wave Planar 0.0dBi 0.3dBi 50 50 50 50 50 50 50 50 50 50 50 50 50 50 CAS Both CAS UFL CAS CAS UFL Both Both Both Both Both Both CAS CAS Linx Part Number Rfrence Linx Description CSI-RSFB-300-UFFR*
RP-SMA Bulkhead to U.FL with 300mm cable CSI-RSFE-300-UFFR*
RP-SMA External Mount Bulkhead to U.FL with 300mm cable
* Also available in 100mm and 200mm cable length Figure 45: HumRCTM Series Transceiver Approved Antennas 46 47 Castellation Version Reference Design The castellation connection for the antenna on the pre-certified version allows the use of embedded antennas as well as removes the cost of a cable assembly for the u.FL connector. However, the PCB design and layer stack must follow one of the reference designs for the certification on the HUM-900-RC-CAS to be valid. Figure 46 shows the PCB layer stack that should be used. Figure 47 shows the layout and routing designs for the different antenna options. Please see the antenna data sheets for specific ground plane counterpoise requirements. Layer Name Top Layer Dielectric 1 Mid-Layer 1 Thickness Material Copper 1.4mil FR-4 (Er = 4.6) 14.00mil Copper 1.4mil Dielectric 2 28.00mil FR-4 (Er = 4.6) Mid-Layer 2 Dielectric 3 Bottom Layer 1.4mil 14.00mil 1.4mil Copper FR-4 (Er = 4.6) Copper Figure 46: HumRCTM Series Transceiver Castellation Version Reference Design PCB Stack Note: The PCB design and layer stack for the HUM-900-RC-CAS must follow these reference designs for the pre-certification to be valid. The HUM-900-RC-UFL and the HUM-900-RC-CAS must use one of the antennas in Figure 45 in order for the certification to be valid. The HUM-900-RC and HUM-2.4-RC have not been tested and require full compliance testing in the end product as it will go to market. All modules require unintentional radiator compliance testing in the end product as it will go to market. 1 6 3 5 3 5 3 2 7
. 2 6 0 3 0 0 A M S V E R N O C 0 2 3 9 1 6 0 0 2 5 6 1 5 6 1 0 7 4 0 3 2 0 4 1 0 3 2 P L
-
W P
-
6 1 9
-
T N A
-
A R W P
-
6 1 9
-
T N A 6 1 2 0 8 3 P S
-
6 1 9
-
T N A S P R
-
T R W
-
6 1 9
-
T N A
-
W Q W C
-
6 1 9
-
T N A
-
W H W C
-
6 1 9
-
T N A 1 l i i t m 4 2
=
h d W p i r t s o r c M i r e y a L
-
d M n o i e n a p l d n u o r G s l i m n i e r a s t i n U 48 49 Figure 47: HumRCTM Series Transceiver Castellation Version Reference Design Power Supply Requirements 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 modules performance, so providing a clean power supply for the module should be a high priority during design. 10 Vcc IN Vcc TO MODULE
+
10F Figure 48: Supply Filter A 10 resistor in series with the supply followed by a 10F tantalum capacitor from Vcc to ground helps in cases where the quality of supply power is poor (Figure 48). This filter should be placed close to the modules supply lines. These values may need to be adjusted depending on the noise present on the supply line. Antenna Considerations The choice of antennas is a critical and often overlooked design consideration. The range, performance and legality of an RF link are critically dependent upon the antenna. While adequate antenna performance can often be obtained by trial and error methods, antenna design and matching is a complex task. Professionally designed antennas such as those from Linx (Figure 49) help ensure maximum performance and FCC and other regulatory compliance. Please see General Antenna Rules for more information. Figure 49: Linx Antennas It is usually best to utilize a basic quarter-wave whip until your prototype product is operating satisfactorily. Other antennas can then be evaluated based on the cost, size and cosmetic requirements of the product. Additional details are in Application Note AN-00500. Interference Considerations The RF spectrum is crowded and the potential for conflict with unwanted sources of RF is very real. While all RF products are at risk from interference, its effects can be minimized by better understanding its characteristics. Interference may come from internal or external sources. The first step is to eliminate interference from noise sources on the board. This means paying careful attention to layout, grounding, filtering and bypassing in order to eliminate all radiated and conducted interference paths. For many products, this is straightforward; however, products containing components such as switching power supplies, motors, crystals and other potential sources of noise must be approached with care. Comparing your own design with a Linx evaluation board can help to determine if and at what level design-specific interference is present. External interference can manifest itself in a variety of ways. Low-level interference produces noise and hashing on the output and reduces the links overall range. High-level interference is caused by nearby products sharing the same frequency or from near-band high-power devices. It can even come from your own products if more than one transmitter is active in the same area. It is important to remember that only one transmitter at a time can occupy a frequency, regardless of the coding of the transmitted signal. This type of interference is less common than those mentioned previously, but in severe cases it can prevent all useful function of the affected device. Although technically not interference, multipath is also a factor to be understood. Multipath is a term used to refer to the signal cancellation effects that occur when RF waves arrive at the receiver in different phase relationships. This effect is a particularly significant factor in interior environments where objects provide many different signal reflection paths. Multipath cancellation results in lowered signal levels at the receiver and shorter useful distances for the link. 50 51 Pad Layout The pad layout diagrams below are designed to facilitate both hand and automated assembly. Figure 50 shows the footprint for the smaller version and Figure 51 shows the footprint for the pre-certified version. 0.520"
0.015"
0.420"
0.015"
0.028"
0.050"
0.070"
Figure 50: HUM-***-RC Recommended PCB Layout 0.015"
0.060"
0.100"
0.101"
0.136"
0.090"
0.015"
0.028"
0.065"
0.060"
0.420"
0.015"
0.050"
0.070"
Figure 51: HUM-***-RC-UFL/CAS Recommended PCB Layout Microstrip Details 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 modules antenna can effectively contribute to the length of the antenna, changing its resonant bandwidth. In order to minimize loss and detuning, some form of transmission line between the antenna and the module should be used unless the antenna can be placed very close (<18in) to the module. One common form of transmission line is a coax cable and another is the microstrip. This term refers to a PCB trace running over a ground plane that is designed to serve as a transmission line between the module and the antenna. The width is based on the desired characteristic impedance of the line, the thickness of the PCB and the dielectric constant of the board material. For standard 0.062in thick FR-4 board material, the trace width would be 111 mils. The correct trace width can be calculated for other widths and materials using the information in Figure 52 and examples are provided in Figure 53. Software for calculating microstrip lines is also available on the Linx website. Trace Board Ground plane Figure 52: Microstrip Formulas Example Microstrip Calculations Dielectric Constant Width / Height Ratio (W / d) Effective Dielectric Constant Characteristic Impedance () 4.80 4.00 2.55 1.8 2.0 3.0 3.59 3.07 2.12 50.0 51.0 48.8 52 Figure 53: Example Microstrip Calculations 53 Board Layout Guidelines The modules 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 modules 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 following section provides some basic design guidelines. During prototyping, the module should be soldered to a properly laid-out circuit board. The use of prototyping or perf boards results in poor performance and is strongly discouraged. Likewise, the use of sockets can have a negative impact on the performance of the module and is discouraged. The module should, as much as reasonably possible, be isolated from other components on your PCB, especially high-frequency circuitry such as crystal oscillators, switching power supplies, and high-speed bus lines. When possible, separate RF and digital circuits into different PCB regions. Make sure internal wiring is routed away from the module and antenna and is secured to prevent displacement. Do not route PCB traces directly under the module. There should not be any copper or traces under the module on the same layer as the module, just bare PCB. The underside of the module has traces and vias that could short or couple to traces on the products circuit board. The Pad Layout section shows a typical PCB footprint for the module. A ground plane (as large and uninterrupted as possible) should be placed on a lower layer of your PC board opposite the module. This plane is essential for creating a low impedance return for ground and consistent stripline performance. Use care in routing the RF trace between the module and the antenna or connector. Keep the trace as short as possible. Do not pass it under the module or any other component. Do not route the antenna trace on multiple PCB layers as vias add inductance. Vias are acceptable for tying together ground layers and component grounds and should be used in multiples. The -CAS version must follow the layout in Figure 47. Each of the modules ground pins should have short traces tying immediately to the ground plane through a via. Bypass caps should be low ESR ceramic types and located directly adjacent to the pin they are serving. A 50-ohm coax should be used for connection to an external antenna. A 50-ohm transmission line, such as a microstrip, stripline or coplanar waveguide should be used for routing RF on the PCB. The Microstrip Details section provides additional information. In some instances, a designer may wish to encapsulate or pot the product. There are a wide variety of potting compounds with varying dielectric properties. Since such compounds can considerably impact RF performance and the ability to rework or service the product, it is the responsibility of the designer to evaluate and qualify the impact and suitability of such materials. Helpful Application Notes from Linx It is not the intention of this manual to address in depth many of the issues that should be considered to ensure that the modules function correctly and deliver the maximum possible performance. We recommend reading the application notes listed in Figure 54 which address in depth key areas of RF design and application of Linx products. These applications notes are available online at www.linxtechnologies.com or by contacting the Linx literature department. Helpful Application Note Titles Note Number Note Title AN-00100 AN-00126 AN-00130 AN-00140 AN-00500 AN-00501 RG-00104 RF 101: Information for the RF Challenged Considerations for Operation Within the 902928MHz Band Modulation Techniques for Low-Cost RF Data Links The FCC Road: Part 15 from Concept to Approval Antennas: Design, Application, Performance Understanding Antenna Specifications and Operation RC Series Transceiver Command Data Interface Reference Guide Figure 54: Helpful Application Note Titles 54 55 Production Guidelines 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. Soldering Iron Tip Hand Assembly Pads located on the bottom of the module are the primary mounting surface (Figure 55). Since these pads are inaccessible during mounting, castellations that run up the side of the module have been provided to facilitate solder wicking to the modules underside. This allows for very quick hand soldering for prototyping and small volume production. If the recommended pad guidelines have been followed, the pads will protrude slightly past the edge of the module. Use a fine soldering tip to heat the board pad and the castellation, then introduce solder to the pad at the modules edge. The solder will wick underneath the module, providing reliable attachment. Tack one module corner first and then work around the device, taking care not to exceed the times in Figure 56. Solder PCB Pads Castellations Figure 55: Soldering Technique Warning: Pay attention to the absolute maximum solder times. Absolute Maximum Solder Times Hand Solder Temperature: +427C for 10 seconds for lead-free alloys Reflow Oven: +255C max (see Figure 57) Figure 56: Absolute Maximum Solder Times Automated Assembly For high-volume assembly, the modules are generally auto-placed. The modules have been designed to maintain compatibility with reflow processing techniques; however, due to their hybrid nature, certain aspects of the assembly process are far more critical than for other component types. Following are brief discussions of the three primary areas where caution must be observed. Reflow Temperature Profile The single most critical stage in the automated assembly process is the reflow stage. The reflow profile in Figure 57 should not be exceeded because excessive temperatures or transport times during reflow will irreparably damage the modules. Assembly personnel need to pay careful attention to the ovens profile to ensure that it meets the requirements necessary to successfully reflow all components while still remaining within the limits mandated by the modules. The figure below shows the recommended reflow oven profile for the modules. Recommended RoHS Profile Max RoHS Profile Recommended Non-RoHS Profile 255C 235C 217C 185C 180C 125C 300 250 200 150 100 50
) C o
(
t e r u a r e p m e T 0 30 60 90 120 150 180 210 240 270 300 330 360 Time (Seconds) Figure 57: Maximum Reflow Temperature Profile Shock During Reflow Transport Since some internal module components may reflow along with the components placed on the board being assembled, it is imperative that the modules not be subjected to shock or vibration during the time solder is liquid. Should a shock be applied, some internal components could be lifted from their pads, causing the module to not function properly. Washability The modules are wash-resistant, but are not hermetically sealed. Linx recommends wash-free manufacturing; however, the modules can be subjected to a wash cycle provided that a drying time is allowed prior to applying electrical power to the modules. The drying time should be sufficient to allow any moisture that may have migrated into the module to evaporate, thus eliminating the potential for shorting damage during power-up or testing. If the wash contains contaminants, the performance may be adversely affected, even after drying. 56 57 General Antenna Rules The following general rules should help in maximizing antenna performance. 1. Proximity to objects such as a users 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 58). In many cases, this isnt desirable for practical or ergonomic reasons, thus, an alternative antenna style such as a helical, loop or patch may be utilized and the corresponding sacrifice in performance accepted. plane as possible in proximity to the base of the antenna. In cases where the antenna is remotely located or the antenna is not in close proximity to a circuit board, ground plane or grounded metal case, a metal plate may be used to maximize the antennas performance. 5. Remove the antenna as far as possible from potential interference sources. Any frequency of sufficient amplitude to enter the receivers front end will reduce system range and can even prevent reception entirely. Switching power supplies, oscillators or even relays can also be significant sources of potential interference. The single best weapon against such problems is attention to placement and layout. Filter the modules power supply with a high-frequency bypass capacitor. Place adequate ground plane under potential sources of noise to shunt noise to ground and prevent it from coupling to the RF stage. Shield noisy board areas whenever practical. 3. 4. OPTIMUM USABLE NOT RECOMMENDED Figure 58: Ground Plane Orientation 6. CASE If an internal antenna is to be used, keep it away from other metal components, particularly large items like transformers, batteries, PCB tracks and ground planes. In many cases, the space around the antenna is as important as the antenna itself. Objects in close proximity to the antenna can cause direct detuning, while those farther away will alter the antennas symmetry. GROUND PLANE
(MAY BE NEEDED) NUT ANTENNA (MARCONI) VERTICAL /4 GROUNDED In many antenna designs, particularly -wave whips, the ground plane acts as a counterpoise, forming, in essence, a -wave dipole (Figure 59). For this reason, adequate ground plane area is essential. The ground plane can be a metal case or ground-fill areas on a circuit board. Ideally, it should have a surface area less than or equal to the overall length of the -wave radiating element. This is often not practical due to size and configuration constraints. In these instances, a designer must make the best use of the area available to create as much ground GROUND PLANE VIRTUAL /4 DIPOLE DIPOLE ELEMENT
/4
/4 E I In some applications, it is advantageous to place the module and antenna away from the main equipment (Figure 60). This can avoid interference problems and allows the antenna to be oriented for optimum performance. Always use 50 coax, like RG-174, for the remote feed. NOT RECOMMENDED OPTIMUM USABLE CASE GROUND PLANE
(MAY BE NEEDED) NUT Figure 60: Remote Ground Plane Figure 59: Dipole Antenna 58 59 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 61) provides outstanding overall performance and stability. A low-cost whip can be easily fabricated from a wire or rod, but most designers opt for the consistent performance and cosmetic appeal of a professionally-made model. To meet this need, Linx offers a wide variety of straight and reduced height whip style antennas in permanent and connectorized mounting styles. Figure 61: Whip Style Antennas L =
234 FMHz The wavelength of the operational frequency determines an antennas overall length. Since a full wavelength is often quite long, a partial - or -wave antenna is normally employed. Its size and natural radiation resistance make it well matched to Linx modules. The proper length for a straight -wave can be easily determined using the formula in Figure 62. It is also possible to reduce the overall height of the antenna by using a helical winding. This reduces the antennas bandwidth but is a great way to minimize the antennas physical size for compact applications. This also means that the physical appearance is not always an indicator of the antennas frequency. Figure 62:
L = length in feet of quarter-wave length F = operating frequency in megahertz Loop Style A loop or trace style antenna is normally printed directly on a products PCB (Figure 64). This makes it the most cost-effective of antenna styles. The element can be made self-resonant or externally resonated with discrete components, but its actual layout is usually product specific. Despite the cost advantages, loop style antennas are generally inefficient and useful only for short range applications. They are also very sensitive to changes in layout and PCB dielectric, which can cause consistency issues during production. In addition, printed styles are difficult to engineer, requiring the use of expensive equipment including a network analyzer. An improperly designed loop will have a high VSWR at the desired frequency which can cause instability in the RF stage. Figure 64: Loop or Trace Antenna Linx offers low-cost planar (Figure 65) and chip antennas that mount directly to a products PCB. These tiny antennas do not require testing and provide excellent performance despite their small size. They offer a preferable alternative to the often problematic printed antenna. Figure 65: SP Series Splatch and uSP MicroSplatch Antennas Specialty Styles Linx offers a wide variety of specialized antenna styles (Figure 63). Many of these styles utilize helical elements to reduce the overall antenna size while maintaining reasonable performance. A helical antennas bandwidth is often quite narrow and the antenna can detune in proximity to other objects, so care must be exercised in layout and placement. Figure 63: Specialty Style Antennas 60 61 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. When working with RF, a clear distinction must be made between what is technically possible and what is legally acceptable in the country where operation is intended. Many manufacturers have avoided incorporating RF into their products as a result of uncertainty and even fear of the approval and certification process. Here at Linx, our desire is not only to expedite the design process, but also to assist you in achieving a clear idea of what is involved in obtaining the necessary approvals to legally market a completed product. For information about regulatory approval, read AN-00142 on the Linx website or call Linx. Linx designs products with worldwide regulatory approval in mind. In the United States, the approval process is actually quite straightforward. The regulations governing RF devices and the enforcement of them are the responsibility of the Federal Communications Commission (FCC). The regulations are contained in Title 47 of the United States Code of Federal Regulations (CFR). Title 47 is made up of numerous volumes; however, all regulations applicable to this module are contained in Volume 0-19. It is strongly recommended that a copy be obtained from the FCCs website, the Government Printing Office in Washington or from your local government bookstore. Excerpts of applicable sections are included with Linx evaluation kits or may be obtained from the Linx Technologies website, www.linxtechnologies.com. In brief, these rules require that any device that intentionally radiates RF energy be approved, that is, tested for compliance and issued a unique identification number. This is a relatively painless process. Final compliance testing is performed by one of the many independent testing laboratories across the country. Many labs can also provide other certifications that the product may require at the same time, such as UL, CLASS A / B, etc. Once the completed product has passed, an ID number is issued that is to be clearly placed on each product manufactured. Questions regarding interpretations of the Part 2 and Part 15 rules or the measurement procedures used to test intentional radiators such as Linx RF modules for compliance with the technical standards of Part 15 should be addressed to:
Federal Communications Commission Equipment Authorization Division Customer Service Branch, MS 1300F2 7435 Oakland Mills Road Columbia, MD, US 21046 Phone: + 1 301 725 585 | Fax: + 1 301 344 2050 Email: labinfo@fcc.gov ETSI Secretaria 650, Route des Lucioles 06921 Sophia-Antipolis Cedex FRANCE Phone: +33 (0)4 92 94 42 00 Fax: +33 (0)4 93 65 47 16 International approvals are slightly more complex, although Linx modules are designed to allow all international standards to be met. If the end product is to be exported to other countries, contact Linx to determine the specific suitability of the module to the application. All Linx modules are designed with the approval process in mind and thus much of the frustration that is typically experienced with a discrete design is eliminated. Approval is still dependent on many factors, such as the choice of antennas, correct use of the frequency selected and physical packaging. While some extra cost and design effort are required to address these issues, the additional usefulness and profitability added to a product by RF makes the effort more than worthwhile. 62 63 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. Values may vary from lot-to-lot and are not guaranteed. Typical parameters can and do vary over lots and application. Linx Technologies makes no guarantee, warranty, or representation regarding the suitability of any product for use in any specific application. It is the customers responsibility to verify the suitability of the part for the intended application. NO LINX PRODUCT IS INTENDED FOR USE IN ANY APPLICATION WHERE THE SAFETY OF LIFE OR PROPERTY IS AT RISK. Linx Technologies DISCLAIMS ALL WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL LINX TECHNOLOGIES BE LIABLE FOR ANY OF CUSTOMERS INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING IN ANY WAY FROM ANY DEFECTIVE OR NON-CONFORMING PRODUCTS OR FOR ANY OTHER BREACH OF CONTRACT BY LINX TECHNOLOGIES. The limitations on Linx Technologies liability are applicable to any and all claims or theories of recovery asserted by Customer, including, without limitation, breach of contract, breach of warranty, strict liability, or negligence. Customer assumes all liability
(including, without limitation, liability for injury to person or property, economic loss, or business interruption) for all claims, including claims from third parties, arising from the use of the Products. The Customer will indemnify, defend, protect, and hold harmless Linx Technologies and its officers, employees, subsidiaries, affiliates, distributors, and representatives from and against all claims, damages, actions, suits, proceedings, demands, assessments, adjustments, costs, and expenses incurred by Linx Technologies as a result of or arising from any Products sold by Linx Technologies to Customer. Under no conditions will Linx Technologies be responsible for losses arising from the use or failure of the device in any application, other than the repair, replacement, or refund limited to the original product purchase price. Devices described in this publication may contain proprietary, patented, or copyrighted techniques, components, or materials. Under no circumstances shall any user be conveyed any license or right to the use or ownership of such items. 2016 Linx Technologies. All rights reserved. The stylized Linx logo, Wireless Made Simple, WiSE, CipherLinx and the stylized CL logo are trademarks of Linx Technologies.
| 1 2 | Class II Permissive Change Letter | Cover Letter(s) | 223.66 KiB |
@ @ @ 159 Ort Lane Merlin, OR, US 97532 Phone: +1 541 471 6256 Fax: +1 541 471 6251 TECHNOLOGIES www.linxtechnologies.com August 8, 2019 CETCB 114 Olinda Drive Brea, CA 92823 Regarding FCC Class II Permissive Change for FCC ID: OJM9OD0MCA Dear CETCB, We would like to request a Class Il permissive change for FCC ID: OJM9O0MCA. Major Changes filed under this application are:
1. Adding RF exposure calculation (SAR exclusion) for handheld device classification (devices operated with minimum 5mm separation distance from the human body) This is a documentation update only and does not affect RF parameters such as output power, frequencies and modulations supported. If you have any questions or need additional information, please feel free to give me a call at (541) 471-6256 Sincerely, By wv Shawn Hogan VP of Engineering and Operations Page 1of1 Wireless made simple
| 1 2 | Letter of Authority and Anti-Drug Abuse | Attestation Statements | 293.23 KiB |
@ee-s 159 Ort Lane Merlin, OR, US 97532 Phone: +1 541 471 6256 Fax: +1 541 471 6251 TECHNOLOGIES www.linxtechnologies.com August 8, 2019 CETCB 114 Olinda Drive Brea, CA 92823 Regarding FCC ID: OJM900MCA (IC: 5840A-900MCA) To Whom It May Concern, This is a letter of authorization to accept Compatible Electronics, Inc., specifically including the employees of Compatible Electronics, as an Agent for Linx Technologies, 159 Ort Lane, Merlin Oregon 97532, for a period of one year, to sign applications before the certification body on our behalf, to make representations to you on our behalf, and to receive and exchange data between our company and the Commission in connection with certification of the following Linx Technologies products:
Hummingbird MCA Module under FCC Docket Number 20780 and General Docket Number 80-284 pursuant to Part 15 of the FCC Rules and Regulations. Please also accept this letter as an attestation that neither Linx Technologies nor any of its officers, directors, or persons holding 5% or more of the outstanding stock or shares, voting or non-voting, have been denied federal benefits under section 5301 of the Anti-Drug-Abuse act of 1988, 21 U.S.C. 853(a). In addition, Linx Technologies will notify the Federal Communications Commission if, at any time, the situation changes causing Linx Technologies to be denied federal benefits. If you have any further questions or need additional information, please feel free to give me a call at (541) 471-
6256. Sincerely, JL U Shawn Hogan VP of Engineering and Operations Page 1 of 1 Wireless made simple
| 1 2 | Non-duplicate Submittal Letter | Attestation Statements | 204.14 KiB |
@e@e se 159 Ort Lane Merlin, OR, US 97532 Phone: +1 541 471 6256 Fax: +1 541 471 6251 TECHNOLOGIES www.linxtechnolagies.com August 8, 2019 Compatible Electronics TCB 114 Olinda Drive Brea, California 92823 Regarding FCC ID: OJM900MCA (IC: 5840A-900MCA) We, Linx Acquisitions, LLC., DBA Linx Technologies, would like to declare that the application being submitted for the device with FCC ID: OJM900MCA (IC: 5840A-900MCA) has not been submitted to another TCB or FCC for certification. If you have any questions, please do not hesitate to contact us at (541) 471-6256. Sincerely, SIL UA Shawn Hogan VP of Engineering and Operations Page 1 of 1 Wireless made simple
| frequency | equipment class | purpose | ||
|---|---|---|---|---|
| 1 | 2019-08-19 | 902.97 ~ 926.65 | DSS - Part 15 Spread Spectrum Transmitter | Class II Permissive Change |
| 2 | 2015-06-05 | 902.97 ~ 926.65 | DSS - Part 15 Spread Spectrum Transmitter | Original Equipment |
| app s | Applicant Information | |||||
|---|---|---|---|---|---|---|
| 1 2 | Effective |
2019-08-19
|
||||
| 1 2 |
2015-06-05
|
|||||
| 1 2 | Applicant's complete, legal business name |
Linx Technologies
|
||||
| 1 2 | FCC Registration Number (FRN) |
0005915772
|
||||
| 1 2 | Physical Address |
159 Ort Lane
|
||||
| 1 2 |
Merlin
|
|||||
| 1 2 |
Merlin, Oregon 97532
|
|||||
| 1 2 |
United States
|
|||||
| app s | TCB Information | |||||
| 1 2 | TCB Application Email Address |
m******@compatible-electronics.com
|
||||
| 1 2 |
m******@celectronics.com
|
|||||
| 1 2 | TCB Scope |
A4: UNII devices & low power transmitters using spread spectrum techniques
|
||||
| app s | FCC ID | |||||
| 1 2 | Grantee Code |
OJM
|
||||
| 1 2 | Equipment Product Code |
900MCA
|
||||
| app s | Person at the applicant's address to receive grant or for contact | |||||
| 1 2 | Name |
S****** H****
|
||||
| 1 2 | Title |
VP of Engineering & Operations
|
||||
| 1 2 | Telephone Number |
541-4********
|
||||
| 1 2 | Fax Number |
541-4********
|
||||
| 1 2 |
s******@linxtechnologies.com
|
|||||
| app s | Technical Contact | |||||
| 1 2 | Firm Name |
Compatible Electronics, Inc.
|
||||
| 1 2 | Name |
K******** F******
|
||||
| 1 2 |
K******** L********
|
|||||
| 1 2 | Physical Address |
114 Olinda Drive
|
||||
| 1 2 |
Brea, California 92823
|
|||||
| 1 2 |
United States
|
|||||
| 1 2 | Telephone Number |
714-5********
|
||||
| 1 2 | Fax Number |
714-5********
|
||||
| 1 2 |
714-5********
|
|||||
| 1 2 |
k******@compatible-electronics.com
|
|||||
| 1 2 |
k******@celectronics.com
|
|||||
| app s | Non Technical Contact | |||||
| n/a | ||||||
| app s | Confidentiality (long or short term) | |||||
| 1 2 | Does this application include a request for confidentiality for any portion(s) of the data contained in this application pursuant to 47 CFR § 0.459 of the Commission Rules?: | No | ||||
| 1 2 | Yes | |||||
| 1 2 | Long-Term Confidentiality Does this application include a request for confidentiality for any portion(s) of the data contained in this application pursuant to 47 CFR § 0.459 of the Commission Rules?: | No | ||||
| if no date is supplied, the release date will be set to 45 calendar days past the date of grant. | ||||||
| app s | Cognitive Radio & Software Defined Radio, Class, etc | |||||
| 1 2 | Is this application for software defined/cognitive radio authorization? | No | ||||
| 1 2 | Equipment Class | DSS - Part 15 Spread Spectrum Transmitter | ||||
| 1 2 | Description of product as it is marketed: (NOTE: This text will appear below the equipment class on the grant) | Hummingbird MCA | ||||
| 1 2 | Related OET KnowledgeDataBase Inquiry: Is there a KDB inquiry associated with this application? | No | ||||
| 1 2 | Modular Equipment Type | Single Modular Approval | ||||
| 1 2 | Purpose / Application is for | Class II Permissive Change | ||||
| 1 2 | Original Equipment | |||||
| 1 2 | Composite Equipment: Is the equipment in this application a composite device subject to an additional equipment authorization? | No | ||||
| 1 2 | Related Equipment: Is the equipment in this application part of a system that operates with, or is marketed with, another device that requires an equipment authorization? | No | ||||
| 1 2 | Grant Comments | Modular approval. Class II permissive change to include portable use. This module can only be used with a host antenna circuit trace layout design in strict compliance with the OEM instructions provided. The antenna(s) used with this transmitter must not be co-located or operating in conjunction with any other antenna or transmitter. Users and installers must be provided with antenna installation instructions and transmitter operating conditions for satisfying RF exposure compliance. | ||||
| 1 2 | Modular approval. This module can only be used with a host antenna circuit trace layout design in strict compliance with the OEM instructions provided. The antenna(s) used with this transmitter must be installed to provide a separation distance of at least 20 cm from all persons and must not be co-located or operating in conjunction with any other antenna or transmitter. Users and installers must be provided with antenna installation instructions and transmitter operating conditions for satisfying RF exposure compliance. | |||||
| 1 2 | Is there an equipment authorization waiver associated with this application? | No | ||||
| 1 2 | If there is an equipment authorization waiver associated with this application, has the associated waiver been approved and all information uploaded? | No | ||||
| app s | Test Firm Name and Contact Information | |||||
| 1 2 | Firm Name |
Compatible Electronics, Inc.
|
||||
| 1 2 | Name |
J**** K******
|
||||
| 1 2 | Telephone Number |
71457********
|
||||
| 1 2 | Fax Number |
71457********
|
||||
| 1 2 |
j******@celectronics.com
|
|||||
| Equipment Specifications | |||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Line | Rule Parts | Grant Notes | Lower Frequency | Upper Frequency | Power Output | Tolerance | Emission Designator | Microprocessor Number | |||||||||||||||||||||||||||||||||
| 1 | 1 | 15C | 902.97 | 926.65 | 0.0118065 | ||||||||||||||||||||||||||||||||||||
| 1 | 2 | 15C | 902.97 | 926.27 | 0.0137443 | ||||||||||||||||||||||||||||||||||||
| 1 | 3 | 15C | 902.75 | 914.74 | 0.0097302 | ||||||||||||||||||||||||||||||||||||
| Line | Rule Parts | Grant Notes | Lower Frequency | Upper Frequency | Power Output | Tolerance | Emission Designator | Microprocessor Number | |||||||||||||||||||||||||||||||||
| 2 | 1 | 15C | 902.97 | 926.65 | 0.0118065 | ||||||||||||||||||||||||||||||||||||
| 2 | 2 | 15C | 902.97 | 926.27 | 0.0137443 | ||||||||||||||||||||||||||||||||||||
| 2 | 3 | 15C | 902.75 | 914.74 | 0.0097302 | ||||||||||||||||||||||||||||||||||||
some individual PII (Personally Identifiable Information) available on the public forms may be redacted, original source may include additional details
This product uses the FCC Data API but is not endorsed or certified by the FCC