RXM-900-HP3 Datasheet, PDF (7/13 Pages) List of Unclassifed Manufacturers – HP3 SERIES RECEIVER MODULE DATA

PROTOCOL GUIDELINES
While many RF solutions impose data formatting and balancing requirements,
Linx RF modules do not encode or packetize the signal content in any manner.
The received signal will be affected by such factors as noise, edge jitter, and
interference, but it is not purposefully manipulated or altered by the modules.
This gives the designer tremendous flexibility for protocol design and interface.
Despite this transparency and ease of use, it must be recognized that there are
distinct differences between a wired and a wireless environment. Issues such as
interference and contention must be understood and allowed for in the design
process. To learn more about protocol considerations, we suggest you read Linx
Application Note AN-00160.
Errors from interference or changing signal conditions can cause corruption of
the data packet, so it is generally wise to structure the data being sent into small
packets. This allows errors to be managed without affecting large amounts of
data. A simple checksum or CRC could be used for basic error detection. Once
an error is detected, the protocol designer may wish to simply discard the corrupt
data or implement a more sophisticated scheme to correct it.
INTERFERENCE CONSIDERATIONS
The RF spectrum is crowded and the potential for conflict with other 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 will produce noise and hashing on the output and reduce the link’s
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 it is 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, thus, shorter useful distances
for the link.
Page 12
TYPICAL APPLICATIONS
The figure below shows a typical RS-232 circuit using the HP3 Series receiver
and a Maxim MAX232. The receiver outputs a serial data stream and the
MAX232 converts that to RS-232 compliant signals. The MODE line is grounded
so the channels are selected by the DIP switches.
VCC
VCC
C1
4.7uF
C3
+
4.7uF
C4
+
4.7uF
C5
4.7uF
1
2
3
4
5
6
7
8
C1+
V+
C1-
C2+
C2-
V-
T2OUT
R2IN
MAX232
VCC
GND
T1OUT
R1IN
R1OUT
T1IN
T2IN
R2OUT
+ C2
4.7uF
DB-9
1
16
GND
6
15
2
14
7
13
3
12
11
4
10
9
9
5
GND
GND
GND
VCC
GND
Figure 14: HP3 Receiver and MAX232 IC
1 _ANT
2 _GND
3 _GND
4 _GND
5 _GND
6 _GND
7 _GND
8 _GND
9 _NC
10 _CS0
11 _{CS1 / SS CLOCK}
12 _{CS2 / SS DATA}
13 _PDN
14 _RSSI
15 _MODE
16 _VCC
17 _AUDIO
18 _DATA
NC ³⁶
NC ³⁵
NC ³⁴
NC ³³
NC ³²
NC ³¹
NC ³⁰
NC ²⁹
NC ²⁸
NC ²⁷
NC ²⁶
NC ²⁵
NC ²⁴
NC ²³
NC ²²
NC ²¹
NC ²⁰
NC ¹⁹
The figure below shows a circuit using the QS Series USB module. The QS
converts the data from the receiver into USB compliant signals to be sent to a
PC. The MODE line is high, so the module is in Serial Channel Select mode. The
RTS and DTR lines are used to load the channels. Application Note AN-00155
shows sample source code that can be adapted to use on a PC. The QS Series
Data Guide and Application Note AN-00200 discuss the hardware and software
set-up required for QS Series modules.
USB-B
GND
4
3
DAT -
5V
2
1
GND
GND
GND GND
1 _USBDP
RI ¹⁶
2 _USBDM
DCD ¹⁵
3 _GND
DSR
4 _VCC
DATA_IN ¹³
5 _{SUSP_IND DATA_OUT} 12
6 _{RX_IND}
RTS ¹¹
7 _{TX_IND}
CTS ¹⁰
8 _{485_TX}
DTR ⁹
SDM-USB-QS
1
2
3
4
5
6
GND 7
8
9
10
11
12
13
VCC 14
16
17
18
ANT
GND
GND
GND
GND
GND
GND
GND
NC
CS0
CS1 / SS CLOCK
CS2 / SS DATA
PDN
RSSI
MODE
VCC
AUDIO
DATA
NC ³⁶
NC ³⁵
NC ³⁴
NC ³³
NC ³²
NC ³¹
NC ³⁰
NC ²⁹
NC ²⁸
NC ²⁷
NC ²⁶
NC ²⁵
NC ²⁴
NC ²³
NC ²²
NC ²¹
NC ²⁰
NC ¹⁹
Figure 15: HP3 Receiver and Linx QS Series USB Module
The receiver can also be connected to a microcontroller, which will interpret the
data and take specific actions. A UART may be employed or an I / O line may be
used to continuously monitor the DATA line for a valid packet. The receiver may
be connected directly to the microcontroller without the need for buffering or
amplification.
Page 13