Hum XXX Pro

HumPRO TM 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).
Table of Contents
1^
1^
2^
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.
2^
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.
12^
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.
3^
5^
10^
10^
13^
14^
15^
16^
18^
19^
20^
20^
21^
21^
22^
23^
26^
28^
28^
29^
30^
30^
31^
32^
Description
Features
Ordering Information
Absolute Maximum Ratings
Electrical Specifications
Typical Performance Graphs
Pin Assignments
Pin Descriptions
Pre-Certified Module Pin Assignments
Module Dimensions
Theory of Operation
Module Description
Overview
Addressing Modes
Automatic Addressing
Acknowledgements and Assured Delivery
Compatibility with the 250 Series
Address Register Use
Networking
Transmitting Packets
Receiving Packets
Exception Engine
Carrier Sense Multiple Access (CSMA)
Using the Buffer Empty (BE) Line
Using the Command Response (CRESP) Line
Using the CMD Line
External Amplifier Control
AES Encryption
Restore Factory Defaults
32^
34^
36^
37^
38^
75^
76^
76^
77^
78^
78^
78^
80^
80^
81^
82^
83^
84^
85^
86^
86^
86^
88^
90^
92^
94^
Using the Low Power Features

The Command Data Interface
Writing to Registers
Reading from Registers
The Command Data Interface Command Set
Typical Applications
Usage Guidelines for FCC Compliance
Additional Testing Requirements
Information to the user
Product Labeling
FCC RF Exposure Statement
Antenna Selection
Power Supply Requirements
Antenna Considerations
Interference Considerations
Pad Layout
Microstrip Details
Board Layout Guidelines
Helpful Application Notes from Linx
Production Guidelines
Hand Assembly
Automated Assembly
General Antenna Rules
Common Antenna Styles
Regulatory Considerations
Notes
HumPRO TM Series
RF Transceiver Module
Data Guide
Description
0.55"
(13.97)
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.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
Revised 12/3/14
Electrical Specifications
HumPROTM Series Transceiver Specifications
Part Number
Description
Parameter
HUM-***-PRO
HumPRO
Series Data Transceiver
Power Supply
HUM-***-PRO-CAS
HumPRO
Series Data Transceiver with Castellation Connection
HUM-***-PRO-UFL
HumPROTM Series Data Transceiver with u.FL Connector
EVM-***-PRO
HumPRO
MDEV-***-PRO
HumPROTM Series Master Development System
EVAL-***-PRO
HumPRO
TM
TM
TM
TM
Symbol
Min.
Operating Voltage
VCC
2.0
TX Supply Current
lCCTX
900MHz at +10dBm
Series Carrier Board
900MHz at 0dBm
Series Basic Evaluation Kit
*** = Frequency; 900MHz
Typ.
Max.
Units
3.6
VDC
40.5
41.5
mA
1,2
22
24
mA
1,2
RX Supply Current
lCCRX
23.5
24.5
mA
1,2,3
Power-Down Current
lPDN
0.7
1,2
RF Section
Figure 2: Ordering Information
Operating Frequency Band

HUM-900-PRO
FC
MHz
902
928
MHz
Number of hop channels

Supply Voltage Vcc
0.3
to
+3.9
VDC
Any Input or Output Pin
0.3
to
VCC + 0.3
VDC
RF Input
dBm
Operating Temperature
40
to
+85
Storage Temperature
40
to
+85
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
@ 19.2kbps RF Rate
50/64
@ 152.34kbps RF Rate
26/32
Channel spacing
@ 19.2kbps RF Rate
375.9
kHz
751.81
kHz
@ 19.2kbps RF Rate
64
kHz
315
kHz
@ 19.2kbps RF Rate
102
kHz
232
kHz
19.2
kHz
51
kHz
20 dB OBW
Receiver BW
FSK deviation
@ 19.2kbps RF Rate
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.
Scan time / channel (avg)
@ 19.2kbps RF Rate
1.2
ms
0.335
ms
@ 19.2kbps RF Rate
63
ms
26
ms
FHSS Lock time
Modulation
2FSK
Data Encoding
6/7 RLL
Number of Hop Sequences
Notes

Parameter
Symbol
Min.

Typ.
Max.
Units
Notes
Parameter
Receiver Section
Spurious Emissions
47
IF Frequency
304.7
dBm
kHz
Receiver Sensitivity
HUM-900-PRO @min rate
98
101
dBm
HUM-900-PRO @max rate
91
94
dBm
RSSI Dynamic Range
85
dB
CSMA RSSI Threshold
70
dBm
+8.5
PH
+9.5
dBm
41
dBc
dB
Output Power Range

HUM-900-PRO
PH
Typ.
Max.
Units
Notes
VOLM
0.3*VCC
VDC
1,9
Logic High, RFACTV, BE
VOHM
Logic Low
VOL
Logic High
VOH
0.7*VCC
VDC
0.3*VCC
0.7*VCC
CRESP Hold Time
1,9
1,10
1,10
10
Bits
11
1.
2.
3.
4.
5.
6.
7.
22,000
cycles
12
Measured at 3.3V VCC

Measured at 25C
Input power < -60dBm
Characterized but not tested
PER = 5%
Into a 50-ohm load
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
Figure 4: Electrical Specifications
Antenna Port
RF Impedance
Logic Low, RFACTV, BE
Flash Write Cycles
PO
HUM-900-PRO
Harmonic Emissions
Min.
Flash (Non-Volatile) Memory Specifications
Transmitter Section
Output Power
Symbol
Output
RIN
+85
129.5
50
Environmental
Operating Temp. Range
40
Timing
Module Turn-On Time
ms
Via POWER_DOWN
51.7
4
ms
Via Standby
ms
Serial Command Response

Volatile R/W
0.4
ms
NV Update
2.2
31.5
ms
Factory Reset
107
ms
Channel Dwell Time

CMD low to trigger TX with
option TXnCMD
400
tTXnCMD
ms
ms
11.0
10.5
-40C
10.0
25C
9.5
9.0
85C
Interface Section
UART Data rate
Typical Performance Graphs

TX Output Power (dBm)
Via VCC
9,600
115,200
bps
8.5
2.0
2.5
3.3
Supply Voltage (V)
Input
Logic Low
VIL
Logic High
VIH
0.3*VCC
0.7*VCC
VDC
Figure 5: HumPROTM Series Transceiver Max Output Power vs. Supply Voltage - HUM-900-PRO
VDC
3.6
40.00
-40C
39.50
35
25C
-40C
30
85C
25
20
Supply Current (mA)
Supply Current (mA)
40
39.00
38.50
25C
38.00
85C
37.50
37.00
36.50
15
-5
2V
2.5V
Figure 6: HumPROTM Series Transceiver Average Current vs. Transmitter Output Power at 2.5V - HUM-900-PRO
40
3.6V
Figure 9: HumPROTM Series Transceiver TX Current vs. Supply Voltage at Max Power - HUM-900-PRO
23.40
25C
38
-40C
23.20
36
Supply Current (mA)
Supply Current (mA)
3.3V
Supply Voltage (V)
34
32
30
28
-40C
26
85C
24
23.00
25C
22.80
85C
22.60
22.40
22.20
22
22.00
20
-5
Figure 7: HumPROTM Series Transceiver Average TX Current vs. Transmitter Output Power at 3.3V -HUM-900-PRO
2V
2.5V
3.3V
Supply Voltage (V)
Figure 8: HumPROTM Series Transceiver TX Current vs. Supply Voltage at 0dBm - HUM-900-PRO
3.6V
24.5
1.40
24.1
23.9
25C
23.7
-40C
23.5
85C
1.20
85C
23.3
23.1
22.9
Standby Current (A)
Supply Current (mA)
24.3
1.00
0.80
25C
0.60
-40C
0.40
0.20
22.7
22.5
2
2.1 2.2 2.3 2.4 2.5 2.6 2.7 2.8 2.9
0.00
2.5
3.1 3.2 3.3 3.4 3.5 3.6
3.3
Supply Voltage (V)
3.6
Supply Voltage (V)
Figure 10: 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.
23
22.6
25C
22.4
22.2
-40C
22
21.8
21.6
21.4
-25.00
RSSI Reading (dBm)
Supply Current (mA)
-15.00
85C
22.8
-35.00
-45.00
-55.00
-65.00
-75.00
-40C
25C
85C
-85.00
-95.00
21.2
21
2
2.1 2.2 2.3 2.4 2.5 2.6 2.7 2.8 2.9
3.1 3.2 3.3 3.4 3.5 3.6
Supply Voltage (V)
Figure 11: HumPROTM Series Transceiver RX Scan Current vs. Supply Voltage, 115.2kbps - HUM-900-PRO
-105.00
-100.00 -90.00 -80.00 -70.00 -60.00 -50.00 -40.00 -30.00 -20.00 -10.00
Input Power (dBm)
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.
0.00
Pin Descriptions
VCC
RESET
LNA_EN
PA_EN
Pin Number
GND
CMD_DATA_OUT
CMD_DATA_IN
CTS
PB
Pin Assignments
29 28 27 26 25 24 23 22 21
30
20
GND
BE
31
19
ANT
NC
32
18
GND
NC
17
GND
NC
16
GND
NC
15
GND
GND
CMD
EX
14
9 10 11 12 13
POWER_DOWN
NC
7
CRESP
6
NC
NC
NC
NC
GND
RFACTV
Name
I/O
CMD
19
ANTENNA
50-ohm RF Antenna Port
21
VCC
Supply Voltage
22
RESET
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.
23
LNA_EN
Low Noise Amplifier Enable. This line is

driven high when receiving. It is intended to
activate an optional external LNA.
24
PA_EN
Power Amplifier Enable. This line is driven

high when transmitting. It is intended to
activate an optional external power amplifier.
26
CMD_DATA_OUT
Command Data Out. Output line for data

and serial commands
27
CMD_DATA_IN
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.
Reset non-volatile memory. A sequence

of 4 high pulses on this line, followed by a
prolonged high state causes the module
to reset the non-volatile configuration
parameters to factory default values.
RF Packet Transfer. This line goes high

when the module is transmitting a packet,
receiving a potentially valid packet or when
the PB line is high
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.
28
CTS
29
PB
Pin Descriptions
Pin Number
1, 2, 3, 4, 5,
6, 10, 11, 32
7
Name
NC
CRESP
I/O
Description
No Electrical Connection. Do not connect

any traces to these lines.
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.
EX
Exception Output. A mask can be set

to take this line high when an exception
occurs. The line is lowered when the
exception register is read (EXCEPT).
9, 14, 15, 16,

17, 18, 20, 25
GND
Ground
12
POWER_DOWN
Command Input. When this line is low,

incoming bytes are command data.
When high, incoming bytes are data to be
transmitted.
13
Figure 14: HumPROTM Series Transceiver Pin Assignments (Top View)
Pin Descriptions
Description
30
31
RFACTV
BE
Figure 15: HumPROTM Series Transceiver Pin Descriptions
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.
10
11
Pre-Certified Module Pin Assignments
Module Dimensions
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.
ANT
GND
18
NC
NC
0.07"
(1.78)
NC
0.812"
(20.62)
9 10 11 12 13
CMD
NC
NC
0.45"
(11.43)
Figure 17: HumPROTM Series Transceiver Dimensions
POWER_DOWN
NC
NC
GND
32
EX
NC
NC
31
CRESP
BE
GND
VCC
RESET
LNA_EN
PA_EN
CMD_DATA_OUT
19
CTS
29 28 27 26 25 24 23 22 21
30
PB
RFACTV
CMD_DATA_IN
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.
0.55"
(13.97)
0.45"
(11.43)
Figure 16: HumPROTM Series Transceiver Pre-certified Version Pin Assignments (Top View)
0.116"
(2.95)
Figure 18: HumPROTM Series Transceiver Pre-certified Version Dimensions
12
13
Theory of Operation
Module Description
The HumPROTM Series transceiver is a low-cost, high-performance

synthesized FSK / MSK transceiver. Figure 19 shows the modules block
diagram.
The HumPROTM Series module is a completely integrated RF transceiver

and processor designed to transmit digital data across a wireless link.
It employs a fast-locking FHSS system for noise immunity and higher
transmitter output power as allowed by government regulations.
DEMODULATOR
ADC
LNA
ADC
ANTENNA
FREQ
90
SYNTH
PROCESSOR
INTERFACE
GPIO /
INTERFACE
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.
MODULATOR
PA
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.
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 HumPRO Series RF transceiver module offers a number of features
that make it suitable for many data transfer applications. This section
provides a basic overview of the features while following sections dive into
them in more detail.
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 HumPRO Addressing Mode Reference Guide has
details about configuring the addressing.
Streaming Data and Explicit Packets

The modules default configuration is for streaming data. In this operation
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 engine 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.

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.
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 pairing operation.
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 routs
the data to the transmitter for transmission over-the-air. The CMD line is
normally controlled by an external microcontroller.
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.

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 waits for it to clear or hops to the next
channel if the channel time expires. This reduces the overall potential for
interference and improves the robustness of the link.

16
Encryption is not yet enabled on the initial release of HumPRO modules.
17
Addressing Modes
The module has very flexible addressing schemes 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 schemes, 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.
User Addressing Mode

User Addressing Mode is a more flexible method than DSN Addressing
Mode. It uses the customer ID bytes (CUSTID[1-0]) 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.
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.
In normal operation each module has a user ID mask (UMASK[3-0]) that

splits the 32 address bits into 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. This mode only uses
the 16 bits in the USRCID[1-0] registers, but the mask includes the 16 high
order 0 bits in USRCID[3-2].
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.
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.
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.
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
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.
Figure 20 shows the address registers that are used with each addressing
mode.
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.
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. 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.
HumPROTM Series Transceiver Address Registers

COMPAT
ADDMODE
0x00 (Relaxed Addressing)

0x04
(DSN)
0x06
(User)
0x07
(Ex User)
0x04
(DSN)
0x06
(User)
0x07
(Ex User)
0x14
(DSN
+ACK)
0x16
(User
+ACK)
0x17
(ExUser
+ACK)
0x14
(DSN
+ACK)
0x16
(User
+ACK)
0x17
(ExUser
+ACK)
UDESTID[3-0]
UDESTID[1-0]
USRC[1-0]
X
X
UMASK[3-0]
UMASK[1-0]
X
X
Figure 20: HumPROTM Series Transceiver Address Register Use
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.
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.
20
USRC[3-0]
DESTDSN[3-0]
0x02 (Normal Addressing)
21
Transmitting Packets
Receiving Packets
In default operation when transmitting, the host microcontroller writes bytes

to the CMD_DATA_IN line while the CMD line is held high at the baud rate
selected by the UARTBAUD register. The incoming bytes are buffered until
one of four conditions triggers the packet to be transmitted:
In default operation when receiving 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.
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 number of buffered bytes exceeds what can be sent before the
radio must hop channels.
The first three 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 it is desired for all data to be sent in the same packet or
where the microcontroller needs a greater level of control over the radio,
the HumPROTM offers explicit control of packet transmission through
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 these options are 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.
22
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 when 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.
23
DSN Address Packet Header
CMD
Tag
CMD_DATA_IN
CMD_DATA_OUT
Any Command
Read Packet Command

Any Response
0x01
ACK
Packet to UART
CONTROL
EX
Header
Length
1
Frame
Type
1
User Address Packet Header

Tag
Header
Frame
Length
Type
0x01
1
1
Hop ID
Sequence Dest DSN
Source
DSN
4
Hop ID
Sequence
Cust ID
Dest Addr
2 or 4
Data
Length
1
Source
Addr
2 or 4
Source
DSN
4
Data
Length
1
Exception for unread packet
Packet In
Figure 21: HumPROTM Series Transceiver Received Packet Transfer Cycle
Packet Data
Tag
Data
Length
0x02
1
Data
Data Length Bytes
Figure 22: HumPRO Series Transceiver Packet Header and Data Structure
TM
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.
Although not part of the normal packet transfer, if CMD is set low while the
control line is high (received packet transfer in progress), data transmission
stops, the control line goes low, and the module processes and responds
to incoming commands. If CMD is again taken high, the control line is
raised and the packet transfer continues where it left off. This gives the host
microcontroller very fine control over when received packets are output and
how much data needs to be managed.
The header and data structures for explicit 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.
24
HumPROTM Series Transceiver Frame Types

Exception Mask
Exception Name
0x04
DSN Addressing Mode
0x14
DSN Addressing with Acknowledgement
0x06
0x16
User Addressing with Acknowledgement
0x07
0x17
Extended User Addressing with Acknowledgement
Figure 23: HumPROTM Series Transceiver Frame Types
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.
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.
25
Exception Engine
The HumPRO is equipped with an internal exception engine to notify the
host microcontroller of an unexpected event. If errors occur during module
operation, an exception is raised. There are two methods of driving the EX
pin when an exception condition exists:
TM
The EX line can be asserted to indicate to the host that an error has
occurred. The EXCEPT register must be read to reset the line. Figure 25
lists some example exception masks.
HumPROTM Series Transceiver Example Exception Masks
Exception Mask
Exception Name
1. From the EXMASK and EXCEPT registers (legacy operation)
0x08
Allows only EX_BUFOVFL and EX_RFOVFL to trigger the EX line
2. From the EEXMASKx and EEXFLAGx registers (standard operation)
0x10
Allows only EX_WRITEREGFAILED to trigger the EX line
0x20
Allows only EX_NORFACK to trigger the EX line
If EXMASK is non-zero, the first method is used, otherwise the second

method is used.
0x40
Allows only EX_BADCRC, EX_BADHEADER, EX_BADSEQID and

EX_BADFRAMETYPE exceptions to trigger the EX line
0x60
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
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 24 lists the exception codes
and their meanings.
HumPROTM Series Transceiver Exception Codes
Exception Code
Exception Name
Description
0x08
EX_BUFOVFL
Incoming UART buffer overflowed.
0x09
EX_RFOVFL
Outgoing UART buffer overflowed.
0x13
EX_WRITEREGFAILED
Attempted write to register failed.
0x20
EX_NORFACK
Acknowledgement packet not received

after maximum number of retries.
0x40
EX_BADCRC
Bad CRC detected on incoming packet.
0x42
EX_BADHEADER
Bad CRC detected in packet header.
0x43
EX_BADSEQID
Sequence ID was incorrect in ACK packet.
0x44
EX_BADFRAMETYPE
Attempted transmit with Invalid setting in

reg:NETMODE or invalid packet type in
received packet header
Figure 25: 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.
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.
Figure 24: HumPROTM Series Transceiver Exception Codes
26
27
Using the Command Response (CRESP) Line
CSMA is an optional feature. It is a best-effort delivery system that listens

to the channel before transmitting a message. If CSMA is enabled and
the module detects another transmitter on the same channel, it waits until
the active transmitter finishes before sending its payload. This helps to
eliminate RF message corruption and make channel use more efficient.
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 until one byte time after the last byte for the indicated source
(command response or data).
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.
In these cases, the module waits for a random interval, then checks again
for activity. If no activity is detected after waiting, it starts transmitting.
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.
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 in 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 protocol engine processes
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 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 configuring 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 ten bit times after the stop bit of the last
command response. Figure 26 shows the timing.
CMD_DATA_OUT
0xFF
...
CRESP
Figure 26: HumPROTM Series Transceiver CRESP Line Timing
The state of the BE line can be read in the LSTATUS register, reducing the
number of hardware connections that are needed.
28
29
D6
D7
Stop
10 bit
times
Using the CMD Line
AES Encryption
The CMD line informs the module where incoming UART data should be
routed. When the line is high, all incoming UART data is treated as payload
data and is routed to the transmitter to be sent over the air. If the CMD line
is low, the incoming UART data is treated as commands and is routed to
the controller for processing.
Encryption algorithms are complex mathematical equations that use a

number, called a key, to encrypt data before transmission. This is done
so that unauthorized persons who may intercept the transmission cannot
access the data. In order to decrypt the transmission, the decoder must
use the same key that was used to encrypt it. The decoder performs the
same calculations as the encoder and, if the key is the same, the data is
recovered.
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.
Figure 27 shows this timing.
CMD_DATA_IN
0xFF
...
CMD
D6
D7
Stop
10 bit
times
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 stored in the NKEY registers to
encrypt the transmitted data. The source and destination addresses are
sent in the clear.
Encryption is disabled by default.
Figure 27: HumPRO Series Transceiver CMD Line Timing

TM
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.
AES Encryption is not yet implemented on the HumPROTM module.
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 what state the radio is in.
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 RFACTV line blinks once per second
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.
Output Line Sleep States

Output Line
Sleep State
EX
Unchanged
CRESP
Low
LNA_EN
Low
PA_EN
Low
TXD
High
CTS
High
RFACTV
Low
BE
Unchanged
Figure 28: 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 module then begins normal operation.
Pulsing RESET low causes the module to restart rather than continue from
sleep.
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 28.
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.
On wakeup, the CRESP line is taken high.
32
33
The Command Data Interface

The HumPRO Series transceiver has a serial Command Data Interface
(CDI) that is used to configure and control the transceiver through
software commands. This interface consists of a standard UART with a
serial command set. The CMD_DATA_IN and CMD_DATA_OUT lines are
the interface to the 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).
TM
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.
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 must be changed into 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.
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 data in the UART receive buffer,
the BE line is low; when this buffer is empty, 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.
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]
34
35
Writing to Registers
Reading from Registers
Byte values of 128 (0x80) or greater must 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. These are shown in Figure 29.
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 30.
HumPROTM Series Write to Configuration Register Command

Command for a Register and Value less than 128 (0x80)
Header
Size
Address
Value
0xFF
0x02
REG
V1
HumPROTM Series Read From Configuration Register

Command
Command for a Register less than 128 (0x80) and a Value greater than 128 (0x80)
Header
0xFF
Size
0x03
Address
REG
Value 1
0xFE
Value 2
Command for a Register greater than 128 (0x80) and a Value less than 128 (0x80)
Size
Addr1
Addr2
Value
0xFF
0x03
0xFE
REG-0x80
V1
Size
Escape
Address
0xFF
0x02
0xFE
REG
ACK
Address
Value
0x06
REG
V1
Response
V-0x80
Header
Header
Command for an Address greater than 128 (0x80)
Command for a Register and Value greater than 128 (0x80)

Header
Size
Addr1
Addr2
Value 1
Value 2
0xFF
0x04
0xFE
REG-0x80
0xFE
V-0x80
Figure 29: HumPROTM Series Write to Configuration Register Command
Generally, there are three steps to creating the command.
Header
Size
Escape
Addr1
Addr2
0xFF
0x03
0xFE
0xFE
REG-80
ACK
Address
Value
0x06
REG
V1
Response
Figure 30: HumPROTM Series Read from Configuration Register Command and Response
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.
36
37
The Command Data Interface Command Set

The following sections describe the registers.
Note: Values are shown in hexadecimal format unless otherwise stated.
HumPROTM Series Configuration Registers
Name
NV
Addr
CRCERRS
Vol
Addr
R/W
Default
Value
0x40
R/W
0x00
CRC Error Count
Description
HOPTABLE
0x00
0x4B
R/W
0x00
Channel Hop Table
TXPWR
0x02
0x4D
R/W
0x03
Transmit Power
UARTBAUD
0x03
0x4E
R/W
0x01
UART data rate
ADDMODE
0x04
0x4F
R/W
0x04
Addressing mode
DATATO
0x05
0x50
R/W
0x10
Data timeout
MAXTXRETRY
0x07
0x52
R/W
0x1A
Maximum Transmit Retries
ENCRC
0x08
0x53
R/W
0x01
Enable CRC checking
BCTRIG
0x09
0x54
R/W
0x40
Byte Count trigger
SHOWVER
0x0A
R/W
0x01
Show version on startup
ENCSMA
0x0B
0x56
R/W
0x01
Enable CSMA
IDLE
0x0D
0x58
R/W
0x00
Idle Mode
WAKEACK
0x0E
0x59
R/W
0x01
UART Acknowledge on Wake
UDESTID3
0x0F
0x5A
R/W
0xFF
Destination Address for User Packet

Type, extended
UDESTID2
0x10
0x5B
R/W
0xFF

Type, extended
UDESTID1
0x11
0x5C
R/W
0xFF

Type
UDESTID0
0x12
0x5D
R/W
DESTDSN2
0x1E
0x69
R/W
0xFF
Destination Device Serial Number
DESTDSN1
0x1F
0x6A
R/W
0xFF
DESTDSN0
0x20
0x6B
R/W
0xFF
EXMASK
0x21
0x6C
R/W
0x00
Exception Mask to activate EX
CMDHOLD
0x23
0x6E
R/W
0x00
Hold RF data when nCMD pin is low
COMPAT
0x25
0x70
R/W
0x02
Compatibility
AUTOADDR
0x26
0x71
R/W
0x00
Automatic Reply Address
MYDSN3
0x34
Factory programmed Serial Number
MYDSN2
0x35
MYDSN1
0x36
MYDSN0
0x37
CUSTID1
0x39
0xFF
Factory programmed customer ID
CUSTID0
0x3A
0xFF
Factory programmed customer ID
CRSSI
0x3F
R/W
0xBA
Carrier Sense minimum RSSI
RELEASE
0x78
EXCEPT
Release number
0x79
0x00
Exception code
PRSSI
0x7B
0x00
Packet RSSI
ARSSI
0x7C
0x00
Ambient RSSI
FWVER3
0xC0
Firmware version, major
FWVER2
0xC1
Firmware version, minor
FWVER1
0xC2
Firmware version, increment
FWVER0
0xC3
Firmware version, suffix
NVCYCLE1
0xC4
NV Erase Cycles, MS
NVCYCLE0
0xC5
NV Erase Cycles, LS
0xC6
Output line status
0xFF

Type
LSTATUS
CMD
0xC7
EEXFLAG2
0xCD
R/W
0x00
Extended exception flags
EEXFLAG1
0xCE
R/W
0x00
Command register
USRCID3
0x13
0x5E
R/W
0xFF
Source Address for User Packet

Type, extended
USRCID2
0x14
0x5F
R/W
0xFF
Source Address for User Packet

Type, extended
0xCF
R/W
0x00
USRCID1
0x15
0x60
R/W
0xFF
Source Address for User Packet Type
EEXMASK2
0x80
0xD0
R/W
0x00
Extended exception mask
USRCID0
0x16
0x61
R/W
0xFF
Source Address for User Packet Type
EEXMASK1
0x81
0xD1
R/W
0x00
EEXMASK0
0x82
0xD2
R/W
0x00
PKTOPT
0x83
0xD3
R/W
0x00
Packet options
UMASK3
0x17
0x62
R/W
0xFF
Address Mask for User Packet Type,

extended
UMASK2
0x18
0x63
R/W
0xFF
Address Mask for User Packet Type,

extended
UMASK1
0x19
0x64
R/W
0xFF
Address Mask for User Packet Type
UMASK0
0x1A
0x65
R/W
0xFF
Address Mask for User Packet Type
DESTDSN3
0x1D
0x68
R/W
0xFF
38
EEXFLAG0
Figure 31: HumPROTM Series Configuration Registers
39
CRCERRS - CRC Error Count

Volatile Address = 0x40
The value in the CRCERRS register is incremented each time a packet is
received that fails the CRC check. Overflows are ignored. Writing 0x00
to this register initializes the count. Figure 32 shows the command and
response.
HumPROTM Series CRC Error Count
Read Command
Read Response
Header
Size
Escape
Address
ACK
Address
Value
0xFF
0x02
0xFE
0x40
0x06
0x40
V1
Write Command
Header
Size
Address
Value
0xFF
0x02
0x40
V1
Figure 32: 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 33
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
V1
Write Command
Header
Size
Address
Value
0xFF
0x02
0x4B
0x00
V1
number. When the baud rate is 38,400bps and higher, the module uses
26 hopping channels. Figure 36 shows the hop sequences referenced by
channel number. Only even channels are used. The default hop sequence
is 0.
HumPROTM Series RF Channels
Channel Number
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
Frequency (MHz)
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
Channel Number
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
Figure 34: HumPROTM Series RF Channels
Figure 33: HumPROTM Series Channel Hop Table Command and Response
Figure 34 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
channels. Figure 35 shows the hop sequences referenced by channel
40
41
Frequency (MHz)
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
HumPROTM Series Hop Sequences by Channel Number for 19,200bps and below
0
25
63
28
26
16
61
4
29
0
44
46
22
36
34
24
2
21
11
27
1
35
37
55
8
10
54
13
32
43
12
23
48
14
39
40
15
57
18
60
41
9
49
58
38
45
56
50
42
62
47
1
30
60
59
14
16
32
4
47
26
43
1
25
36
15
57
10
48
21
8
17
37
45
44
13
33
0
46
62
34
7
24
22
58
42
50
12
20
39
27
2
35
5
28
49
29
18
38
3
52
40
2
11
12
0
62
23
43
25
34
61
26
24
6
31
7
32
55
39
1
41
29
15
57
3
42
47
2
56
33
9
14
30
21
4
54
59
51
22
38
58
60
52
45
37
13
35
36
8
46
40
49
3
58
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
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
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
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
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
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
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
Figure 36: HumPROTM Series Hop Sequences for UART rates of 19,200bps and above
Figure 35: HumPROTM Series Hop Sequences for UART rate of 9,600bps
42
43
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.
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
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.
HumPROTM Series UART Baud Rate
Read Command
Read Response
Header
Size
Escape
Address
ACK
Address
Value
0xFF
0x02
0xFE
0x4E
0x03
0x06
0x4E
0x03
V1
Size
Address
Value
0x02
0x4E
0x03
V1
Write Command
Header
Figure 37: HumPROTM Series Transmitter Output Power Mode Command and Response
HumPROTM Series Transmitter Output Power Mode Register Settings

PWR
Typical Output Power (dBm)
0x00
-5
0x01
0x02
+5
0x03
+9
Figure 38: HumPROTM Series Transmitter Output Power Mode Settings
0xFF
Figure 39: HumPROTM Series UART Baud Rate Command and Response
HumPROTM Series UART Baud Rate Register Settings
V1
Baud Rate (bps)
RF Data Rate (bps)
0x01
9,600
19,200
0x02
19,200
19,200
0x03
38,400
153,600
0x04
57,600
153,600
0x05
115,200
153,600
0x06
10,400*
153,600
0x07
31,250*
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: 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,000bps (0x01).
44
45
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. For each of these modes,
assured delivery (acknowledgement) can be either enabled or disabled.
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.
Figure 41 shows the command and response and Figure 42 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
V1
Write Command
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 have been received by the UART. All of the bytes
are sent once the trigger has been reached. Figure 43 shows examples of
the commands. Figure 44 shows the minimum timeout values based on
baud rate.
HumPROTM Series Transmit Wait Timeout
Read Command
Read Response
Header
Size
Address
Value
Header
Size
Escape
Address
ACK
Address
Value
0xFF
0x02
0x4F
0x04
V1
0xFF
0x02
0xFE
0x50
0x05
0x06
0x50
0x05
V1
Size
Address
Value
0x02
0x50
0x05
V1
Write Command
Figure 41: HumPROTM Series Addressing Mode Command and Response
HumPROTM Series Addressing Mode Register Settings
Addressing Mode
Header
0xFF
Meaning
0x04
DSN Addressing Mode
0x06
0x07
0x14
DSN Addressing Mode with Acknowledgement
0x16
User Addressing Mode with Acknowledgement
0x17
Extended User Addressing Mode with Acknowledgement
+0x00
Send normal preamble
+0x08
Send extended preamble
All other addressing modes are reserved and may cause undesired operation.
Figure 42: HumPROTM Series Addressing Mode Register Settings
46
Figure 43: HumPROTM Series Transmit Wait Timeout Command and Response
HumPROTM Series Minimum DATATO Values
Baud Rate
Minimum DATATO
9,600
3ms
19,200
2ms
38,400
2ms
57,600
2ms
115,200
2ms
Figure 44: HumPROTM Series Transmit Wait Timeout Minimum Values

47
MAXTXRETRY - Maximum Transmit Retries

The value in the MAXTXRETRY register sets the number of transmission
retries if an acknowledgement is not received. If an acknowledgement is
not received after the last retry, exception EX_NORFACK is raised. Figure
45 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
V1
Write Command
Header
Size
Address
Value
0xFF
0x02
0x52
0x07
V1
ENCRC - CRC Enable

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 47 shows examples of the
commands and Figure 48 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
V1
Size
Address
Value
0x02
0x53
0x08
V1
Write Command
Header
Figure 45: HumPROTM Series Maximum Transmit Retries Command and Response
The time between retries depends on the current baud rate. Figure 46
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
0xFF
Figure 47: HumPROTM Series CRC Enable Command and Response

HumPROTM Series CRC Enable Register Settings
Baud Rate
Timeout Time
V1
9,600
50ms
0x00
CRC Disabled
19,200
50ms
0x01
CRC Enabled
38,400
30ms
57,600
30ms
115,200
30ms
Figure 46: HumPROTM Series Acknowledgement Timeout Times
48
Mode
Figure 48: 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.
49
BCTRIG - UART Byte Count Trigger

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 49 shows
examples of the commands.
HumPROTM Series UART Byte Count Trigger
Read Command
Header
0xFF
Size
0x02
Read Response
Escape
Address
0xFE
0x54
0x09
ACK
Address
Value
0x06
0x54
0x09
V1
0xFF
HumPROTM Series Show Version

Read Command
Read Response
Header
Size
Escape
Address
ACK
Address
Value
0xFF
0x02
0xFE
0x0A
0x06
0x0A
V1
Write Command
Header
Size
Address
Value
0xFF
0x02
0x0A
V1
Figure 50: HumPROTM Series Show Version Command and Response

HumPROTM Series Show Version Register Settings
Write Command
Header
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 50 shows examples
of the commands and Figure 51 shows the available values.
Size
Address
0x02
0x54
0x09
Value
V1
V1
0x00
Startup message is NOT output on reset or power-up.
0x01
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.
0x02
Startup message is displayed upon reset or power-up. This is a

non-blocking operation. Any incoming UART data is buffered, and
incoming UART commands are processed. If a change of baud
rate is commanded while the startup message is being output, the
current byte finishes at the current baud rate, and subsequent bytes
are transmitted at the new baud rate.
Figure 49: HumPROTM Series UART Byte Count Trigger Command and Response
This trigger can be overridden by enabling the TXPKT option (PKTOPT

register, bit 0).
Meaning
Figure 51: HumPROTM Series Show Version Register Settings
Example:
HUM-900-PRO v1.2.3
(C) 2014 Linx Technologies Inc. All rights reserved.
50
51
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
HumPROTM module 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
52 shows examples of the commands and Figure 53 shows the available
values.
HumPROTM Series CSMA Enable
Read Command
Header
Size
0xFF
0x02
Read Response
Escape
Address
0xFE
0x56
0x0B
ACK
Address
Value
0x06
0x56
0x0B
V1
Write Command
Header
Size
Address
Value
0xFF
0x02
0x56
0x0B
V1
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 54 shows
examples of the commands and Figure 55 shows the available values.
HumPROTM Series Idle Mode
Read Command
Figure 52: HumPROTM Series CSMA Enable Command and Response
Read Response
Header
Size
Escape
Address
ACK
Address
Value
0xFF
0x02
0xFE
0x58
0x0D
0x06
0x58
0x0D
V1
Write Command
HumPRO
TM
V1
Series CSMA Enable Register Settings

Mode
0x00
Disable CSMA
0x01
Enable CSMA
Header
Size
Address
Value
0xFF
0x02
0x58
0x0D
V1
Figure 54: HumPROTM Series Idle Mode Command and Response
Figure 53: HumPROTM Series CSMA Enable Register Settings
HumPROTM Series Idle Mode Register Settings
The module only checks for other HumPRO

transmissions from other systems.
TM
modules. It does not defer to
V1
Mode
0x00
Awake
0x01
Sleep
Figure 55: HumPROTM Series Idle Mode Register Settings
52
53
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 wakes.
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 56 shows examples of the commands and Figure 57 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
V1
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. When the COMPAT
register is 0x02 in User Address mode, bytes 3 and 2 must be 0. 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 58
shows the User Destination ID registers.
HumPROTM Series User Destination Address Registers
Name
Volatile
Address
Non-Volatile
Address
Description
UDESTID3
0x5A
0x0F
MSB of the extended destination address
Header
Size
Address
Value
UDESTID2
0x5B
0x10
Byte 2 of the extended destination address
0xFF
0x02
0x59
0x0E
V1
UDESTID1
0x5C
0x11
Byte 1 of the extended destination address,

MSB of the short destination address
UDESTID0
0x5D
0x12
LSB of the extended destination address and

short destination address
Write Command
Figure 56: HumPRO Series ACK on Wake Command and Response

TM
Figure 58: HumPROTM Series User Destination Address Registers

HumPRO
TM
V1
Series ACK on Wake Register Settings

Mode
0x00
Disable ACK
0x01
Enable ACK
Figure 57: HumPROTM Series ACK on Wake Register Settings
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. Extended User
Addressing mode uses all four bytes. Please see the Addressing Modes
section for more details. Each register byte is read and written separately.
Figure 59 shows the User Source ID registers.
HumPROTM Series User Source Address Registers
Name
Volatile
Address
Non-Volatile
Address
USRCID3
0x5E
0x13
MSB of the extended source address
USRCID2
0x5F
0x14
Byte 2 of the extended source address
USRCID1
0x60
0x15
Byte 1 of the extended source address

MSB of the short source address
USRCID0
0x61
0x16
LSB of the extended source address and short

source address
Description
Figure 59: HumPROTM Series User Source Address Registers

54
55
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 60 shows the User ID Mask registers.
HumPROTM Series User ID Mask 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.
Figure 62 shows examples of the commands and Figure 63 shows the
available values.
Name
Volatile
Address
Non-Volatile
Address
UMASK3
0x62
0x17
MSB of the extended mask
HumPROTM Series Exception Mask
UMASK2
0x63
0x18
Byte 2 of the extended mask
Read Command
Header
Size
Escape
Address
ACK
Address
Value
0xFF
0x02
0xFE
0x6C
0x21
0x06
0x6C
0x21
V1
Description
UMASK1
0x64
0x19
Byte 1 of the extended mask

MSB of the short mask
UMASK0
0x65
0x1A
LSB of the extended mask and short mask
Read Response
Write Command
Figure 60: 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 61 shows the Destination DSN registers.
HumPRO
TM
Series Destination DSN Registers
Header
Size
Address
Value
0xFF
0x02
0x6C
0x21
V1
Figure 62: HumPROTM Series Transceiver Exception Mask Command and Response
HumPROTM Series Example Exception Masks

V1
Exception Name
0x08
Allows only EX_BUFOVFL and EX_RFOVFL to trigger the EX line
0x10
Allows only EX_WRITEREGFAILED to trigger the EX line
0x20
Allows only EX_NORFACK to trigger the EX line
0x40
Allows only EX_BADCRC, EX_BADHEADER, EX_BADSEQID and EX_

BADFRAMETYPE exceptions to trigger the EX line
Name
Volatile
Address
Non-Volatile
Address
DESTDSN3
0x68
0x1D
MSB of the destination DSN
DESTDSN2
0x69
0x1E
Byte 2 of the destination DSN
0x60
Allows EX_BADCRC, EX_BADHEADER, EX_BADSEQID, EX_BADFRAMETYPE

and EX_NORFACK exceptions to trigger the EX line
DESTDSN1
0x6A
0x1F
Byte 1 of the destination DSN

MSB of the short destination DSN
0xFF
Allows all exceptions to trigger the EX line
DESTDSN0
0x6B
0x20
LSB of the extended and short DSN
Description
Figure 63: HumPROTM Series Transceiver Example Exception Masks
Figure 61: HumPROTM Series Destination DSN Registers
56
57
CMDHOLD - CMD Halts Traffic

Volatile Address = 0x6E; Non-Volatile Address = 0x23
When configuring the modules register settings, it is possible that incoming
RF data can intermix with the modules response, making it difficult to
separate command responses and data bytes. 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. The external host processor must
distinguish the command response bytes from the received data bytes by
using the CRESP line.
Figure 64 shows examples of the commands and Figure 65 shows the
available values.
COMPAT - Compatibility Mode

Compatibility mode allows the HumPROTM Series modules to communicate
with the 250 Series modules. Please see the Compatibility Mode section
for more details. Figure 66 shows examples of the commands and Figure
67 shows the available values.
HumPROTM Series Compatibility Mode
Read Command
Header
0xFF
Size
Read Response
Escape
Address
0xFE
0x70
0x25
Size
Address
Value
0x02
0x70
0x25
V1
0x02
ACK
Address
Value
0x06
0x70
0x25
V1
Write Command
Header
0xFF
HumPROTM Series CMD Halts Traffic

Read Command
Header
Size
0xFF
Escape
Address
0xFE
0x6E
0x23
Size
Address
Value
0x02
0x6E
0x23
V1
0x02
Figure 66: HumPROTM Series Transceiver Compatibility Mode Command and Response
Read Response
ACK
Address
Value
0x06
0x6E
0x23
V1
Write Command
Header
0xFF
V1
Mode
0x00
Enable 250 Series Compatibility Mode
0x02
Enable normal Addressing Operation
Figure 67: HumPROTM Series Compatibility Mode Register Settings
Figure 64: HumPROTM Series Transceiver CMD Halts Traffic Command and Response
HumPROTM Series CMD Halts Traffic Register Settings
V1
HumPROTM Series Compatibility Mode Register Settings
Mode
0x00
Disable Halt (received data is sent to the UART immediately)
0x01
Enable Halt (received data is sent when the CMD line is high)
Figure 65: HumPROTM Series CMD Halts Traffic Register Settings
AUTOADDR - Auto Addressing

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
58
59
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 68 summarizes the configuration values for the lower 4 bits of the
register.
HumPROTM Series Auto Addressing Register Settings
Auto Address Value
Meaning
Action
Auto Addressing disabled
Destination Registers not

populated
0x04
DSN Auto Address
Auto-populates DSN Address

Destination Register Only
0x06
User Auto Address Mode
Auto-populates User Address

Destination Register
0x07
Extended User Auto Address

Mode
Auto-populates Extended User

Address Destination Register
0x0F
Any Auto Address Mode
Auto-populates any Address

Destination Register
0x00
Figure 68: HumPROTM Series Transceiver Auto Addressing Register Settings
Figure 69 shows the Addressing Mode values that the module writes to the
upper 4 bits after successfully receiving a packet.
HumPROTM Series Auto Addressing Mode Indicator
Addressing Mode
Meaning
0x4
DSN Addressing Mode
0x6
0x7
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 used by all packet
types as a unique origination address.
Figure 70 shows the Device Serial Number registers.
HumPROTM Series DSN Registers
Name
Non-Volatile
Address
MYDSN3
0x34
MSB of the serial number
MYDSN2
0x35
Byte 2 of the serial number
MYDSN1
0x36
Byte 1 of the serial number
MYDSN0
0x37
LSB of the serial number
Description
Figure 70: 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 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 71 shows the Customer ID registers.
HumPROTM Series Customer ID Registers
Name
Non-Volatile
Address
CUSTID1
0x39
MSB of the customer ID
CUSTID0
0x3A
LSB of the customer ID
Description
Figure 71: HumPROTM Series Transceiver Customer ID Registers
Figure 69: HumPROTM Series Transceiver Auto Addressing Mode Indicator
60
61
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 shows examples of the
commands.
HumPROTM Series Carrier Sense Minimum RSSI
Read Command
Read Response
Header
Size
Escape
Address
ACK
Address
Value
0xFF
0x02
0xFE
0x3F
0x06
0x3F
V1
0xFF
Size
0x02
HumPROTM Series Exception Code

Read Command
Write Command
Header
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. Figure 75 shows
examples of the commands and Figure 76 shows the available values.
Address
0x3F
Read Response
Value
Header
Size
Escape
Address
ACK
Address
Value
V1
0xFF
0x02
0xFE
0x79
0x06
0x79
V1
Figure 75: HumPROTM Series Transceiver Exception Code Command and Response
Figure 72: 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.
RELEASE - Release Number

Non-Volatile Address = 0x78
This register contains a number designating the firmware version and
hardware platform. Figure 73 shows examples of the commands and
Figure 74 lists current releases to date.
HumPROTM Series Release Number
Read Command
Read Response
Header
Size
Escape
Address
ACK
Address
Value
0xFF
0x02
0xFE
0x78
0x06
0x78
V1
HumPROTM Series Transceiver Exception Codes

V1
Exception Name
Description
0x08
EX_BUFOVFL
Internal UART buffer overflowed.
0x09
EX_RFOVFL
Internal RF packet buffer overflowed.
0x13
EX_WRITEREGFAILED
0x20
EX_NOACK
Acknowledgement packet not received after

maximum number of retries.
0x40
EX_BADCRC
0x42
EX_BADHEADER
0x43
EX_BADSEQID
0x44
EX_BADFRAMETYPE
Unsupported frame type specified.
Figure 76: HumPROTM Series Transceiver Exception Codes
Figure 73: HumPROTM Series Transceiver Release Number Command and Response
HumPROTM Series Release Number Register Settings
V1
Release Number
0x20
HUM-900-PRO
Figure 74: HumPROTM Series Transceiver Release Number Register Settings
A more detailed firmware version is available for versions 0x20 and above in
the FWVER register.
62
63
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
Read 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 and written separately. Figure
79 shows the Firmware Version registers.
HumPROTM Series Firmware Version Registers
Name
Non-Volatile
Address
FWVER3
0xC0
Major version number
Description
Header
Size
Escape
Address
ACK
Address
Value
FWVER2
0xC1
Minor version number
0xFF
0x02
0xFE
0x7B
0x06
0x7B
V1
FWVER1
0xC2
Incremental version number
FWVER0
0xC3
Suffix
Figure 77: HumPROTM Series Transceiver Last Good Packet RSSI Command and Response
Figure 79: HumPROTM Series Firmware Version Registers
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
Read Response
Header
Size
Escape
Address
ACK
Address
Value
0xFF
0x02
0xFE
0x7C
0x06
0x7C
V1
Figure 78: HumPROTM Series Transceiver Ambient RSSI Command and Response
64
65
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
Non-Volatile
Address
NVCYCLE1
0xC4
MSB of the number of erase cycles
NVCYCLE0
0xC5
LSB of the number of erase cycles
Description
Figure 80: 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
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 80 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
Read Response
Header
Size
Escape
Escape
Address
ACK
Address
Value
0xFF
0x03
0xFE
0xFE
0x46
0x06
0xC6
LSTATUS
Figure 81: 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 82 shows which line each bit
represents.
HumPROTM Series Output Line Status LSTATUS Values
LSTATUS Bit
Line Status
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
RFACTV RF Active, 1 = RF data transfer is active (TX or RX)
BE Buffer Empty, 1 = UART buffer is empty
Reserved
Reserved
Figure 82: HumPROTM 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.
HumPROTM Series Command Register
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.
Write Command
Header
Size
Escape
Address
Value
0xFF
0x03
0xFE
0x47
V1
Figure 83: HumPROTM Series Transceiver Command Register Command and Response
Value V1 is chosen from among the options in Figure 84.

HumPROTM Series CMD Values
CMD Value
Operation
0x1
SENDP Send Packet
0x2
GETPH Get Packet Header
0x3
GETPD Get Packet Data
0x4
GETPHD Get Packet Header and Data
0x5
CLRRXP Clear Received Packet
0x6
CLROB Clear Outbound Buffer
0x20 0xAA 0xBB
NVRESET Reset non-volatile registers to factory default
Figure 84: 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.
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. 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.
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.
If option RXPKT is disabled this command discards all received data which
has not been delivered.
TXPKT = 1; this command marks the end of an explicit packet in the

outgoing buffer. All bytes within the packet are transmitted together.
Following bytes are transmitted in a following packet. The maximum
packet length is 192 bytes. Multiple packets can be queued with this
command.
The Clear Outbound Buffer command cancels any transmission in

progress and clears the buffer of data to be transmitted.
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 a New Packet exception. The packet data can be read
68
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:
\r\nConfiguration Reset\r\n.
This reset can also be done by toggling the PB line as described in the
Restore Factory Defaults section.
69
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 Transceiver Extended Exception Codes

Bit
Exception Name
Description
EEXFLAG0 (0xCF)
0
EX_BUFOVFL
Internal UART buffer overflowed.
EX_RFOVFL
Internal RF packet buffer overflowed.
Description
EX_WRITEREGFAILED
HumPROTM Series Extended Exception Flags Registers

Name
Volatile
Address
EEXMASK2
0xCD
Byte 2 of the extended exception flags
EX_NOACK
Acknowledgement packet not received after

maximum number of retries.
EEXMASK1
0xCE
Byte 1 of the extended exception flags
EX_BADCRC
EEXMASK0
0xCF
LSB of the extended exception flags
EX_BADHEADER
EX_BADSEQID
EX_BADFRAMETYPE
Unsupported frame type specified.
Figure 85: 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.
EEXFLAG1 (0xCE)
0
EX_TXDONE
A data packet has been transmitted.
EX_RXWAIT
Received data bytes are waiting to be read.
2-7
Reserved
EEXFLAG2 (0xCD)
0-7
Reserved
Figure 86: HumPROTM Series Transceiver Extended Exception Codes
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.
70
71
Multiple outgoing packets can be buffered. Changing this option clears the
incoming buffer, losing untransmitted or unacknowledged data.
PKTOPT - Packet Options

Volatile Address = 0xD3; Non-Volatile Address = 0x83
This register selects options for transferring packet data.
HumPROTM Series Packet Options
Read Command
Header
0xFF
Read Response
Size
Escape
Address
0xFE
0xD3
0x83
0x02
ACK
Address
Value
0x06
0xD3
0x83
V1
Write Command
Header
Size
Address
Value
0xFF
0x02
0xD3
0x83
V1
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.
Figure 87: HumPROTM Series Transceiver Packet Options Command and Response
When RXPKT is 0, incoming UART data is delivered without headers. The

data flow is controlled by the CMDHOLD setting.
Each bit in the register sets an option as shown in Figure 88.

HumPROTM Series Transceiver Extended Exception Codes
Bit
Name
Description
TXPKT
Packet Transmit
TXnCMD
Transmit when nCMD Lowered
RXPKT
Packet Receive
RXP_CTS
Use CTS for RXPKT Transfer
4-7
Reserved
Reserved
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.
Figure 88: HumPROTM Series Transceiver Extended Exception 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.
72
73
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.
22
21
VCC
RESET
23
LNA_EN
24
25
GND
PA_EN
26
27
28
CTS
29
5
GND
GND
GND
19
18
17
16
15
14
GND
GND
GND
GND
GND
CMD
Figure 89: HumPROTM Series Transceiver Extended Exception Mask Registers
NC
NC
NC
POWER_DOWN
20
13
LSB of the extended exception mask
GND
NC
0xD2
NC
12
0x82
GND
11
EEXMASK0
NC
NC
Byte 1 of the extended exception mask
GND
GND
0xD1
NC
GND
ANT
10
0x81
BE
EEXMASK1
32
RFACTV
CMD_DATA_OUT
Byte 2 of the extended exception mask
31
EX
0xD0
30
0x80
GND
CMD_DATA_IN
EEXMASK2
Description
GND
CRESP
Non-Volatile
Address
GND
GND
Volatile
Address
VCC
RXD
TXD
GPIO
GPIO
GPIO
GPIO
GPIO
GPIO
NVRST
Name
Figure 90 shows a typical circuit using the HumPROTM Series transceiver.
NC
HumPROTM Series Extended Exception Mask Registers
Typical Applications
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.
GND
Figure 90: 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.
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 RFACTV line is connected to an LED for visual indication that the
module is active.
74
75
Usage Guidelines for FCC Compliance
Information to the user
The pre-certified version of the HumPROTM Series module is 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:
The following information must be included in the products user manual.
An approved antenna must be directly coupled to the modules U.FL

connector through an approved coaxial extension cable.
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:

OJMHUM900PROA / IC: 5840A-HUM900PROA.
The end products users manual must contain an FCC statement

equivalent to that listed on page 77 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 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.
76
FCC / IC NOTICES
This product contains FCC ID: OJMHUM900PROA / IC: 5840A-HUM900PROA.
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.

Increase the separation between the equipment and receiver.
Connect the equipment into an outlet on a circuit different from that to which
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. lappareil ne doit pas produire de brouillage, et
2. utilisateur de lappareil doit accepter tout brouillage radiolectrique subi,
mme si le brouillage est susceptible den compromettre le fonctionnement.
77
Product Labeling
The end product must be labeled to meet the FCC and IC product label
requirements. It must have the below or similar text:
Contains FCC ID: OJMHUM900PROA / IC: 5840A-HUM900PROA
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.
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 91 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
Type
Gain
Impedance
Impdance
Tested Antennas
ANT-916-CW-QW
Wave Whip
1.84dBi
50
ANT-916-CW-HW
Wave Dipole Helical
1.83dBi
50
ANT-916-PW-LP
Wave Whip
2.44dBi
50
ANT-916-SP
Wave Planar
1.35dBi
50
ANT-916-WRT-RPS
Wave Dipole Helical
1.83dBi
50
ANT-916-CHP
Wave Ceramic
1.34dBi
50
0.26dBi
50
Antenna Selection
Antennas of the same type and same or lesser gain
Under FCC and Industry Canada regulations, this radio transmitter 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.
ANT-916-CW-HD
Wave Whip
ANT-916-PW-QW
Wave Whip
1.84dBi
50
ANT-916-CW-RCL
Wave Whip
2.03dBi
50
ANT-916-CW-RH
Wave Whip
1.31dBi
50
ANT-916-CW-HWR-RPS
Wave Dipole Helical
1.89dBi
50
ANT-916-PML
Wave Dipole Helical
0.38dBi
50
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 91 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.
ANT-916-PW-RA
Wave Whip
0dBi
50
ANT-916-USP
Wave Planar
0.3dBi
50
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
78
Cable Assemblies / Assemblages de Cbles

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 91: HumPROTM Series Transceiver Approved Antennas
79
Power Supply Requirements
Interference Considerations
Vcc TO
MODULE
10
Vcc IN
+
The module does not have an internal

voltage regulator, therefore it requires a clean,
well-regulated power source. The power supply
noise should be less than 20mV. Power supply
noise can significantly affect the modules
performance, so providing a clean power supply
for the module should be a high priority during
design.
10F
Figure 92: 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 92). 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
Figure 93: Linx Antennas
design and matching is a complex
task. Professionally designed antennas such as those from Linx (Figure
93) help ensure maximum performance and FCC and other regulatory
compliance.
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.
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.
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.
80
81
Pad Layout
Microstrip Details
The pad layout diagrams below are designed to facilitate both hand and
automated assembly. Figure 94 shows the footprint for the smaller version
and Figure 95 shows the footprint for the pre-certified version.
A transmission line is a medium whereby RF energy is transferred from

one place to another with minimal loss. 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 96 and
examples are provided in Figure 97. Software for calculating microstrip lines
is also available on the Linx website.
0.520"
0.015"
0.028"
0.420"
0.050"
0.015"
0.070"
Figure 94: HUM-***-PRO Recommended PCB Layout
Trace
Board
0.136"
0.015" 0.060"
0.100"
0.101"
Ground plane
0.090"
0.060"
0.015"
0.065"
0.028"
0.420"
0.050"
0.070"
0.015"
Figure 96: Microstrip Formulas
Figure 95: HUM-***-PRO-UFL/CAS Recommended PCB Layout
Example Microstrip Calculations

Dielectric Constant
Width / Height
Ratio (W / d)
Effective Dielectric
Constant
Characteristic
Impedance ()
4.80
1.8
3.59
50.0
4.00
2.0
3.07
51.0
2.55
3.0
2.12
48.8
Figure 97: Example Microstrip Calculations

82
83
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.
84
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 98 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
RF 101: Information for the RF Challenged
AN-00126
Considerations for Operation Within the 902928MHz Band
AN-00130
Modulation Techniques for Low-Cost RF Data Links
AN-00140
The FCC Road: Part 15 from Concept to Approval
AN-00500
Antennas: Design, Application, Performance
AN-00501
Understanding Antenna Specifications and Operation
Figure 98: Helpful Application Note Titles
85
The module is housed in a hybrid SMD package that supports hand and
automated assembly techniques. Since the modules contain discrete
components internally, the assembly procedures are critical to ensuring
the reliable function of the modules. The following procedures should be
reviewed with and practiced by all assembly personnel.
Hand Assembly
Pads located on the bottom
Soldering Iron
of the module are the primary
Tip
mounting surface (Figure 99).
Since these pads are inaccessible
during mounting, castellations
that run up the side of the module Solder
have been provided to facilitate
PCB Pads
Castellations
solder wicking to the modules
Figure 99: Soldering Technique
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 100.
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 101)
Figure 100: 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.
86
Reflow Temperature Profile

The single most critical stage in the automated assembly process is the
reflow stage. The reflow profile in Figure 101 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.
300
Recommended RoHS Profile

Max RoHS Profile
Recommended Non-RoHS Profile
255C
250
235C
217C
Temperature (oC)
Production Guidelines
200
185C
180C
150
125C
100
50
30
60
90
120
150
180
210
240
270
300
330
360
Time (Seconds)
Figure 101: 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.
87
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 102). 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.
OPTIMUM
USABLE
NOT RECOMMENDED
Figure 102: Ground Plane Orientation
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.
6. In some applications, it is advantageous to place the module and
antenna away from the main equipment (Figure 104). This can avoid
interference problems and allows the antenna to be oriented for
optimum performance. Always use 50 coax, like RG-174, for the
OPTIMUM
remote feed.
NOT RECOMMENDED
USABLE
CASE
3. If an internal antenna is to be used, keep it away
from other metal
components, particularly large items like
transformers,
batteries,
GROUND PLANE
NUT
PCB tracks and ground planes. In many
the space around the
(MAYcases,
BE NEEDED)
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.
CASE
GROUND PLANE
(MAY BE NEEDED)
NUT
4. In many antenna designs, particularly -wave whips, the ground plane

acts as a counterpoise, forming, in essence,
VERTICAL /4 GROUNDED
a -wave dipole (Figure 103). For this reason, ANTENNA (MARCONI)
adequate ground plane area is essential.
DIPOLE
ELEMENT
The ground plane can be a metal case or
/4
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
GROUND
PLANE
size and configuration constraints. In these
VIRTUAL /4
/4
instances, a designer must make the best use
DIPOLE
of the area available to create as much ground
Figure 104: Remote Ground Plane
Figure 103: Dipole Antenna

88
89
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 105) 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 105: Whip Style Antennas
The wavelength of the operational frequency determines

234
an antennas overall length. Since a full wavelength
L=
F
MHz
is often quite long, a partial - or -wave antenna
Figure 106:
is normally employed. Its size and natural radiation
L = length in feet of
resistance make it well matched to Linx modules.
quarter-wave length
The proper length for a straight -wave can be easily
F = operating frequency
in megahertz
determined using the formula in Figure 106. 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.
Specialty Styles
Linx offers a wide variety of specialized antenna
styles (Figure 107). 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.
90
Loop Style
A loop or trace style antenna is normally printed
directly on a products PCB (Figure 108). 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
Figure 108: Loop or Trace Antenna
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.
Linx offers low-cost planar (Figure 109) 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 107: Specialty Style

Antennas
91
Figure 109: SP Series

Splatch and uSP
MicroSplatch Antennas
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.
92
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.
93
Notes
94
95
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.
2014 Linx Technologies. All rights reserved.
The stylized Linx logo, Wireless Made Simple, WiSE, CipherLinx and the stylized CL logo are trademarks of Linx Technologies.

Hum XXX Pro

Uploaded by

Document Informationclick to expand document informationTransciever Multihop

Document Informationclick to expand document information

Copyright:

Available Formats

Hum XXX Pro

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Hum XXX Pro

Uploaded by

Copyright:

Available Formats

HumPRO TM Series

! Warning: Some customers may want Linx radio frequency (RF)

NO OEM LINX REMOTE CONTROL OR FUNCTION MODULE

Customers may use our (non-Function) Modules, Antenna and

Do not use this or any Linx product to trigger an action directly

Using the Low Power Features

The HumPROTM Series is a frequency hopping

Figure 1: Package Dimensions

Series Data Transceiver

Series Data Transceiver with Castellation Connection

HumPROTM Series Data Transceiver with u.FL Connector

HumPROTM Series Master Development System

Series Carrier Board

Series Basic Evaluation Kit

*** = Frequency; 900MHz

Operating Frequency Band

Absolute Maximum Ratings

Number of hop channels

Absolute Maximum Ratings

Any Input or Output Pin

Warning: This product incorporates numerous static-sensitive

Number of Hop Sequences

HumPROTM Series Transceiver Specifications

HumPROTM Series Transceiver Specifications

HUM-900-PRO @min rate

HUM-900-PRO @max rate

RSSI Dynamic Range

CSMA RSSI Threshold

Output Power Range

Logic High, RFACTV, BE

CRESP Hold Time

Measured at 3.3V VCC

From end of command to start of

Figure 4: Electrical Specifications

Logic Low, RFACTV, BE

Flash Write Cycles

Flash (Non-Volatile) Memory Specifications

Serial Command Response

Channel Dwell Time

Typical Performance Graphs

Supply Current (mA)

Supply Current (mA)

Supply Current (mA)

Supply Current (mA)

TX Output Power (dBm)

TX Output Power (dBm)

Standby Current (A)

Supply Current (mA)

2.1 2.2 2.3 2.4 2.5 2.6 2.7 2.8 2.9

3.1 3.2 3.3 3.4 3.5 3.6

Supply Voltage (V)

Supply Voltage (V)

Supply Current (mA)

2.1 2.2 2.3 2.4 2.5 2.6 2.7 2.8 2.9

3.1 3.2 3.3 3.4 3.5 3.6

Supply Voltage (V)

50-ohm RF Antenna Port