Datasheet RFM69HCW
Datasheet RFM69HCW
Datasheet RFM69HCW
ND
Page 1
Tel: +86-755-82973805 Fax: +86-755-82973550 E-mail: sales@hoperf.com http:/ / www.hoperf.com
RFM69HCW
Page 2
Page 3
Page 4
Page 5
Page 6
Acronyms
Page 7
This product datasheet contains a detailed description of the RFM69HCW performance and functionality.
1. General Description
The RFM69HCW is a transceiver module ideally suited for today's high performance ISM band RF applications. It is
intended for use as high-performance, low-cost FSK and OOK RF transceiver for robust frequency agile, half-duplex bi-
directional RF links, and where stable and constant RF performance is required over the full operating range of the
device down to 1.8V.
The RFM69HCW is intended for applications over a wide frequency range, including the 315MHz,433 MHz,868 MHz
and 915MHz ISM bands. Coupled with a link budget in excess of 140 dB, the advanced system features of the
RFM69HCW include a 66 byte TX/RX FIFO, configurable automatic packet handler, listen mode, temperature sensor and
configurable DIOs which greatly enhance system flexibility whilst at the same time significantly reducing MCU
requirements.
The RFM69HCW complies with both ETSI and FCC regulatory requirements and is available
Page 8
Page 9
10 GND - Ground
11 DIO3 I/O Digital I/O, software configured
12 DIO4 I/O Digital I/O, software configured
13 3.3V - Supply voltage
14 DIO0 I/O Digital I/O, software configured
15 DIO1 I/O Digital I/O, software configured
16 DIO2 I/O Digital I/O, software configured
Page 10
2. Electrical Characteristics
Page 11
IDDST Supply current in Standby mode Crystal oscillator enabled - 1.25 1.5 mA
IDDT Supply current in Transmit mode RFOP = +20 dBm, on PA_BOOST - 130 - mA
with appropriate matching, sta- RFOP = +17 dBm, on PA_BOOST - 95 - mA
ble across VDD range RFOP = +13 dBm, on RFIO pin - 45 - mA
RFOP = +10 dBm, on RFIO pin - 33 - mA
RFOP = 0 dBm, on RFIO pin - 20 - mA
RFOP = -1 dBm, on RFIO pin - 16 - mA
Page 12
2.3.3. Receiver
All receiver tests are performed with RxBw = 10 kHz (Single Side Bandwidth) as programmed in RegRxBw, receiving a
PN15 sequence with a BER of 0.1% (Bit Synchronizer is enabled), unless otherwise specified. The LNA impedance is set
to 200 Ohms, by setting bit LnaZin in RegLna to 1. Blocking tests are performed with an unmodulated interferer. The
wanted signal power for the Blocking Immunity, ACR, IIP2, IIP3 and AMR tests is set 3 dB above the nominal sensitivity
level.
Table 6 Receiver Specification
RFS_F FSK sensitivity, highest LNA gain FDA = 5 kHz, BR = 1.2 kb/s - -118 - dBm
FDA = 5 kHz, BR = 4.8 kb/s - -114 - dBm
FDA = 40 kHz, BR = 38.4 kb/s - -105 - dBm
RFS_O OOK sensitivity, highest LNA gain BR = 4.8 kb/s - -112 -109 dBm
IIP2 2nd order Input Intercept Point Lowest LNA gain - +75 - dBm
Unwanted tones are 20 MHz Highest LNA gain - +35 - dBm
above the LO
Page 13
IIP3 3rd order Input Intercept point Lowest LNA gain - +20 - dBm
Unwanted tones are 1MHz and Highest LNA gain -23 -18 - dBm
1.995 MHz above the LO
IMR_OOK Image rejection in OOK mode Wanted signal level = -106 dBm 27 30 - dB
TS_RE Receiver wake-up time, from PLL RxBw = 10 kHz, BR = 4.8 kb/s - 1.7 - ms
locked state to RxReady RxBw = 200 kHz, BR = 100 kb/s - 96 - us
TS_RE_AGC Receiver wake-up time, from PLL RxBw = 10 kHz, BR = 4.8 kb/s - 3.0 ms
locked state, AGC enabled RxBw = 200 kHz, BR = 100 kb/s 163 us
TS_RE_AGC Receiver wake-up time, from PLL RxBw = 10 kHz, BR = 4.8 kb/s 4.8 ms
&AFC lock state, AGC and AFC enabled RxBw = 200 kHz, BR = 100 kb/s 265 us
* Set SensitivityBoost in RegTestLna to 0x2D to reduce the noise floor in the receiver
2.3.4. Transmitter
Table 7 Transmitter Specification
RF_OP RF output power in 50 ohms Programmable with 1dB steps Max - +20 - dBm
On RFIO pin Min - -18 - dBm
RF_OPH Max RF output power, on With external match to 50 ohms - +20 - dBm
PA_BOOST pin
Page 14
tnsetup NSS setup time from NSS falling edge to SCK rising 30 - - ns
edge
tnhold NSS hold time from SCK falling edge to NSS rising 30 - - ns
edge, normal mode
Page 15
3. Module Description
This section describes in depth the architecture of the RFM69HCW low-power, highly integrated
transceiver.
Page 16
Note to minimize the current consumption of the RFM69HCW, please ensure that the CLKOUT signal is disabled when
not required.
3.2.3.1. VCO
The VCO runs at 2, 4 or 6 times the RF frequency (respectively in the 915, 434 and 315 MHz bands) to reduce any LO
leakage in receiver mode, to improve the quadrature precision of the receiver, and to reduce the pulling effects on the VCO
during transmission.
The VCO calibration is fully automated. A coarse adjustment is carried out at power on reset, and a fine tuning is
performed each time the RFM69HCW PLL is activated. Automatic calibration times are fully transparent to the end-user,
as their processing time is included in the TS_TE and TS_RE specifications.
The carrier frequency is programmed through RegFrf, split across addresses 0x07 to 0x09:
F RF = FSTEP Frf(23,0)
Note The Frf setting is split across 3 bytes. A change in the center frequency will only be taken into account when the
least significant byte FrfLsb in RegFrfLsb is written. This allows for more complex modulation schemes such as m-
ary FSK, where frequency modulation is achieved by changing the programmed RF frequency.
Page 17
When performing an AFC, which usually corrects very small frequency errors, the PLL response time is approximately:
= -------------
In a frequency hopping scheme, the timings TS_HOP given in the table of specifications give an order of magnitude for the
expected lock times.
Note The lock detect block may indicate an unlock condition (signal toggling low) when the transmitter is FSK modulated
with large frequency deviation settings.
Page 18
LNA
PA0
Local
Oscillator
PA1
PA_BOOST
PA2
In Packet mode or in Continuous mode with Gaussian filtering enabled (refer to section 5.5 for details), the Bit Rate (BR) is
controlled by bits BitRate in RegBitrate:
FXOSC
BR = -------------------
BitRate
Page 19
Classical modem baud rates 0x68 0x2B 1.2 kbps 1.2 kbps 1200.015
(multiples of 1.2 kbps)
0x34 0x15 2.4 kbps 2.4 kbps 2400.060
Round bit rates 0x0A 0x00 12.5 kbps 12.5 kbps 12500.00
(multiples of 12.5, 25 and
50 kbps) 0x05 0x00 25 kbps 25 kbps 25000.00
Watch Xtal frequency 0x03 0xD1 32.768 kbps 32.768 kbps 32753.32
Note no constraint applies to the modulation index of the transmitter, but the frequency deviation must exceed 600 Hz.
Page 20
Note the transmitter must be restarted if the PaRamp setting is changed, in order to recalibrate the built-in filter.
A higher power mode, when PA1 and PA2 are combined, providing up to +20 dBm to a matched load.
When PA1 and PA2 are combined to deliver +20 dBm to the antenna, a specific impedance matching / harmonic filtering
design is required to ensure impedance transformation and regulatory compliance.
All PA settings are controlled by RegPaLevel, and the truth table of settings is given in Table 10.
1 0 0 PA0 output on pin RFIO -18 to +13 dBm -18 dBm + OutputPower
0 1 1 PA1 and PA2 combined on pin PA_BOOST +2 to +17 dBm -14 dBm + OutputPower
0 1 1 PA1+PA2 on PA_BOOST with high output +5 to +20 dBm -11 dBm + OutputPower
power +20dBm settings (see 3.3.7)
Notes - To ensure correct operation at the highest power levels, please make sure to adjust the Over Current Protection
Limit accordingly in RegOcp, except above +18dBm where it must be disabled
- If PA_BOOST pin is not used (+20dBm applications and less), the pin can be left floating.
Page 21
Note High Power settings MUST be turned off when using PA0, and in Receive mode
The Duty Cycle of transmission at +20dBm is limited to 1%, with a maximum VSWR of 3:1 at antenna port, over the
standard operating range [-40;+85C].
18
14
10
6
Pout [dBm]
-2
Pout on PA0 [dB m ]
-6
Pout on PA1 [dB m ]
-10
P out on P A 1+ P A 2 [dB m ]
-14
P out on P A 1+ P A 2 with 20dB m s ettings [dB m ]
-18
-22
-18 -14 -10 -6 -2 2 6 10 14 18
Pr o g r am m e d Po w e r [d Bm ]
Note Imax sets a limit on the current drain of the Power Amplifier only, hence the maximum current drain of the
RFM69HCW is equal to Imax + IFS
Page 22
Rx Cal ibration
Reference
LNA / CORDIC
Single to Mi x ers Modulators Channel DC Complex
Differential Fil ter Cancel lation Fi lter Phase FSK
RFIO Output Demodulator
Processing
Dec imator
Module OOK
From Output RSSI
Demodul ator
PA1
By pass ed
in FSK
Local
Os c illator AFC
AGC
The following sections give a brief description of each of the receiver blocks.
Note In the specific case where the LNA gain is manually set by the user, the receiver will not be able to properly handle
FSK signals with a modulation index smaller than 2 at an input power greater than the 1dB compression point,
tabulated in section 3.4.3.
Page 23
The receiver stays in WAIT mode, until RssiValue exceeds RssiThreshold for two consecutive samples. Its power
consumption is the receiver power consumption.
When this condition is satisfied, the receiver automatically selects the most suitable LNA gain, optimizing the
sensitivity/linearity trade-off.
The programmed LNA gain, read-accessible with LnaCurrentGain in RegLna, is carried on for the whole duration of the
packet, until one of the following conditions is fulfilled:
Packet mode: if AutoRxRestartOn = 0, the LNA gain will remain the same for the reception of the following packet. If
AutoRxRestartOn = 1, after the controller has emptied the FIFO the receiver will re-enter the WAIT mode described
above, after a delay of InterPacketRxDelay, allowing for the distant transmitter to ramp down, hence avoiding a false
RSSI detection. In both cases (AutoRxRestartOn=0 or AutoRxRestartOn=1), the receiver can also re-enter the WAIT
mode by setting RestartRx bit to 1. The user can decide to do so, to manually launch a new AGC procedure.
Continuous mode: upon reception of valid data, the user can decide to either leave the receiver enabled with the
same LNA gain, or to restart the procedure, by setting RestartRx bit to 1, resuming the WAIT mode of the receiver,
described above.
Notes - the AGC procedure must be performed while receiving preamble in FSK mode
- in OOK mode, the AGC will give better results if performed while receiving a constant 1 sequence
Towards
-125 dBm
16dB 7dB 11dB 9dB 11dB Pin [dBm]
G1 G2 G3 G4 G5 G6
The following table summarizes the performance (typical figures) of the complete receiver:
Page 24
Note When AFC is enabled and performed automatically at the receiver startup, the channel filter used by the receiver
during the AFC and the AGC is RxBwAfc instead of the standard RxBw setting. This may impact the sensitivity of
the receiver, and the setting of RssiThreshold accordingly
With:
NF = 7dB : LNAs Noise Figure at maximum gain
DemodSnr = 8 dB : SNR needed by the demodulator
RxBw : Single sideband channel filter bandwidth
FadingMargin = 5 dB : Fading margin
The DAGC is enabled by setting RegTestDagc to 0x20 for low modulation index systems (i.e. when AfcLowBetaOn=1,
refer to section 3.4.16), and 0x30 for other systems. It is recommended to always enable the DAGC.
Page 25
The single-side channel filter bandwidth RxBw is controlled by the parameters RxBwMant and RxBwExp in RegRxBw:
When FSK modulation is enabled:
FXOSC
RxBw = -----------------------------------------------------------------
RxBwE x p + 2
RxBwMant 2
When OOK modulation is enabled:
FXOSC
RxBw = -----------------------------------------------------------------
RxBwE x p + 3
RxBwMant 2
The following channel filter bandwidths are accessible (oscillator is mandated at 32 MHz):
Table 14 Available RxBw Settings
RxBwMant RxBwExp RxBw (kHz)
(binary/value) (decimal) FSK OOK
ModulationType=00 ModulationType=01
10b / 24 7 2.6 1.3
01b / 20 7 3.1 1.6
00b / 16 7 3.9 2.0
10b / 24 6 5.2 2.6
01b / 20 6 6.3 3.1
00b / 16 6 7.8 3.9
10b / 24 5 10.4 5.2
01b / 20 5 12.5 6.3
00b / 16 5 15.6 7.8
10b / 24 4 20.8 10.4
Page 26
3.4.7. DC Cancellation
DC cancellation is required in zero-IF architecture transceivers to remove any DC offset generated through self-reception.
It is built-in the RFM69HCW and its adjustable cutoff frequency fc is controlled in RegRxBw:
The default value of DccFreq cutoff frequency is typically 4% of the RxBw (channel filter BW). The cutoff frequency of the
DCC can however be increased to slightly improve the sensitivity, under wider modulation conditions. It is advised to adjust
the DCC setting while monitoring the receiver sensitivity.
3.4.9. RSSI
The RSSI block evaluates the amount of energy available within the receiver channel bandwidth. Its resolution is 0.5 dB,
and it has a wide dynamic range to accommodate both small and large signal levels that may be present. Its acquisition
time is very short, taking only 2 bit periods. The RSSI sampling must occur during the reception of preamble in FSK, and
constant 1 reception in OOK.
Page 27
-20.0
-40.0
RssiValue [dBm]
-60.0
-80.0
-100.0
-120.0
-120 -110 -100 -90 -80 -70 -60 -50 -40 -30 -20 -10 0
Pin [dBm]
3.4.10. Cordic
The Cordic task is to extract the phase and the amplitude of the modulation vector (I+j.Q). This information, still in the
digital domain is used:
Phase output: used by the FSK demodulator and the AFC blocks.
Amplitude output: used by the RSSI block, for FSK demodulation, AGC and automatic gain calibration purposes.
Q(t)
Real-time
Magnitude
Real-time Phase
I(t)
Page 28
0.5
The output of the FSK demodulator can be fed to the Bit Synchronizer (described in section 3.4.13), to provide the
companion processor with a synchronous data stream in Continuous mode.
RSSI
[dBm]
Peak -6dB Threshold
Noise floor of
receiver
Time
Zoom
Decay in dB as defined in
OokPeakThreshStep Fixed 6dB difference
Period as defined in
OokPeakThreshDec
When the RSSI output is null for a long time (for instance after a long string of "0" received, or if no transmitter is present),
the peak threshold level will continue falling until it reaches the "Floor Threshold", programmed in OokFixedThresh.
The default settings of the OOK demodulator lead to the performance stated in the electrical specification. However, in
applications in which sudden signal drops are awaited during a reception, the three parameters should be optimized
accordingly.
Page 29
It is therefore important to note that the setting of OokFixedThresh will be application dependant. The following procedure
is recommended to optimize OokFixedThresh.
Increment
OokFixedThresh
Glitch activity
on DATA ?
Optimization complete
The new floor threshold value found during this test should be used for OOK reception with those receiver settings.
Page 30
The Bit Synchronizer is automatically activated in Packet mode. Its bit rate is controlled by BitRateMsb and BitRateLsb in
RegBitrate.
Raw demodulator
output
(FSK or OOK)
DATA
BitSync Output To
pin DATA and
DCLK in continuous
mode
DCLK
To ensure correct operation of the Bit Synchronizer, the following conditions have to be satisfied:
A preamble (0x55 or 0xAA) of 12 bits is required for synchronization (from the RxReady interrupt)
The subsequent payload bit stream must have at least one transition form '0' to '1' or '1' to '0 every 16 bits during data
transmission
The bit rate matching between the transmitter and the receiver must be better than 6.5 %.
Notes - If the Bit Rates of transmitter and receiver are known to be the same, the RFM69HCW will be able to receive
an infinite unbalanced sequence (all 0s or all 1s) with no restriction.
- If there is a difference in Bit Rate between Tx and Rx, the amount of adjacent bits at the same level that the
BitSync can withstand can be estimated as follows:
- This implies approximately 6 consecutive unbalanced bytes when the Bit Rate precision is 1%, which is easily
achievable (crystal tolerance is in the range of 50 to 100 ppm).
Page 31
signed result is loaded in FeiValue in RegFei, in 2s complement format. The time required for an FEI evaluation is 4 times
the bit period.
The frequency error, in Hz, can be calculated with the following formula:
SX1239
RFM69HCW in Rx
mode
Preamble-modulated input s ignal
Signal level > Sensitivity
Set FeiStart
=1
No
FeiDone
=1
Yes
Read
FeiValue
Page 32
When the AFC is automatically triggered (AfcAutoOn = 1), the user has the option to:
Clear the former AFC correction value, if AfcAutoClearOn = 1
Start the AFC evaluation from the previously corrected frequency. This may be useful in systems in which the LO keeps
on drifting in the same direction. Ageing compensation is a good example.
The RFM69HCW offers an alternate receiver bandwidth setting during the AFC phase, to accommodate large LO drifts. If
the user considers that the received signal may be out of the receiver bandwidth, a higher channel filter bandwidth can
be programmed in RegAfcBw, at the expense of the receiver noise floor, which will impact upon sensitivity.
The user should ensure that the programmed offset exceeds the DC cancellers cutoff frequency, set through DccFreqAfc
in RegAfcBw.
RX TX RX & TX
f f
RX TX TX RX
f f
Before AFC After AFC
As shown on Figure 15, a standard AFC sequence uses the result of the FEI to correct the LO frequency and align both
local oscillators. When the optimized AFC is enabled (AfcLowBetaOn=1), the receivers LO is corrected by FeiValue +
LowBetaAfcOffset.
When the optimized AFC routine is enabled, the receiver startup time can be computed as follows (refer to section 4.2.3):
Page 33
The response of the temperature sensor is -1C / Lsb. A CMOS temperature sensor is not accurate by nature, therefore it
should be calibrated at ambient temperature for precise temperature readings.
TempValue
-1C/Lsb
TempValue(t)
TempValue(t)-1
It takes less than 100 microseconds for the RFM69HCW to evaluate the temperature (from setting TempMeasStart to 1
to
TempMeasRunning reset).
This timeout interrupt can be used to warn the companion processor to shut down the receiver and return to a lower power
mode.
Page 34
4. Operating Modes
4.1. Basic Modes
The circuit can be set in 5 different basic modes which are described in Table 16.
By default, when switching from a mode to another one, the sub-blocks are woken up according to a pre-defined and
optimized sequence. Alternatively, these operating modes can be selected directly by disabling the automatic sequencer
(SequencerOff in RegOpMode = 1).
In applications where the target average power consumption, or the target startup time, do not require setting the
RFM69HCW in the lowest power modes (Sleep or Standby), the respective timings TS_OSC and TS_FS in the former
equations can be omitted.
Page 35
where PaRamp is the ramp-up time programmed in RegPaRamp and Tbit is the bit time.
Tx startup request
(sequencer or user)
TS_TR
1.25 x PaRamp
Analog
XO Started and PLL is locked 0.5 x Tbit (only in FSK Transmission of Packet
group delay
mode)
5 us
ModeReady
TxReady
Page 36
Rx startup request
(sequencer or user)
TS_RE
ModeReady
RxReady
Analog FEs Channel Filters DC Cutoffs RSSI RSSI Channel Filters DC Cutoffs RSSI
XO Started and PLL is locked Reception of Packet
group delay group delay group delay sampling sampling group delay group delay sampling
ModeReady
RxReady
XO Started and Analog FEs Channel Filters DC Cutoffs RSSI RSSI Channel Filters DC Cutoffs RSSI PLL Channel Filters DC Cutoffs
AFC Reception of Packet
PLL is locked group delay group delay group delay sampling sampling group delay group delay sampling lock group delay group delay
Tana Tcf Tdcc Trssi Trssi Tcf Tdcc Trssi Tafc Tpllafc Tcf Tdcc
ModeReady
RxReady
Note The above timings represent maximum settling times, and shorter settling times may be observed in real cases
Page 37
Note all sequences described above are assuming that the sequencer is turned on (SequencerOff=0 in RegOpMode).
Page 38
tListenIdle
Rx Idle Rx time
tListenRx tListenRx
4.3.1. Timings
The duration of the Idle phase is given by tListenIdle. The time during which the receiver is on and waits for a signal is given
by tListenRx. tListenRx includes the wake-up time of the receiver, described in section 4.2.3. This duration can be
programmed in the configuration registers via the serial interface.
Both time periods tListenRx and tListenIdle (denoted tListenX in the following text) are fixed by two parameters from the
configuration register and are calculated as follows:
where ListenResolX is the Rx or Idle resolution and is independently programmable on three values (64us, 4.1ms or
262ms), whereas ListenCoefX is an integer between 1 and 255. All parameters are located in RegListen registers.
Notes - the accuracy of the typical timings given in Table 17 will depend in the RC oscillator calibration
- RC oscillator calibration is required, and must be performed at power up. See section 4.3.5 for details
4.3.2. Criteria
The criteria taken for detecting a wanted signal and hence deciding to maintain the receiver on is defined by ListenCriteria
in RegListen1.
Page 40
PayloadReady
ListenCriteria
passed
Idle Rx
ListenEnd = 00
Listen Mode
Idle Rx Mode
ListenEnd = 01
Listen Mode
Idle Rx Idle Rx
ListenEnd = 10
Listen Mode
For applications enduring large temperature variations, and for which the power supply is never removed, RC calibration
can be performed upon user request. RcCalStart in RegOsc1 can be used to trigger this calibration, and the flag
RcCalDone will be set automatically when the calibration is over.
Page 41
4.4. AutoModes
Automatic modes of packet handler can be enabled by configuring the related parameters in RegAutoModes.
The intermediate mode of the module is called IntermediateMode and the enter and exit conditions to/from this
intermediate mode can be configured through the parameters EnterCondition & ExitCondition.
The enter and exit conditions cannot be used independently of each other i.e. both should be enabled at the same time.
The initial and the final state is the one configured in Mode in RegOpMode. The initial & final states can be different by
configuring the modes register while the module is in intermediate mode. The pictorial description of the auto modes is
shown
below.
Intermediate State
defined by IntermediateMode
EnterCondition ExitCondition
Page 42
5. Data Processing
5.1. Overview
The circuit contains several control blocks which are described in the following paragraphs.
Tx/Rx DIO0
DIO1
DIO2
CONTROL
DIO3
DIO4
DIO5
Data Rx SYNC
RECOG.
PACKET FIFO SPI
HANDLER (+SR)
Tx NSS
SCK
MOSI
MISO
The RFM69HCW implements several data operation modes, each with their own data path through the data
processing section. Depending on the data operation mode selected, some control blocks are active whilst others remain
disabled.
Page 43
Each of these data operation modes is described fully in the following sections.
MOSI is generated by the master on the falling edge of SCK and is sampled by the slave (i.e. this SPI interface) on the
rising edge of SCK. MISO is generated by the slave on the falling edge of SCK.
A transfer always starts by the NSS pin going low. MISO is high impedance when NSS is high.
The second byte is a data byte, either sent on MOSI by the master in case of a write access, or received by the master on
MISO in case of read access. The data byte is transmitted MSB first.
Proceeding bytes may be sent on MOSI (for write access) or received on MISO (for read access) without rising NSS and
re-sending the address. In FIFO mode, if the address was the FIFO address then the bytes will be written / read at the
FIFO address. In Burst mode, if the address was not the FIFO address, then it is automatically incremented at each new
byte received.
Page 44
The frame ends when NSS goes high. The next frame must start with an address byte. The SINGLE access mode is
actually a special case of FIFO / BURST mode with only 1 data byte transferred.
During the write access, the byte transferred from the slave to the master on the MISO line is the value of the written
register before the write operation.
5.2.2. FIFO
The FIFO is 1 byte wide hence it only performs byte (parallel) operations, whereas the demodulator functions serially. A
shift register is therefore employed to interface the two devices. In transmit mode it takes bytes from the FIFO and outputs
them serially (MSB first) at the programmed bit rate to the modulator. Similarly, in Rx the shift register gets bit by bit data
from the demodulator and writes them byte by byte to the FIFO. This is illustrated in figure below.
FIFO
byte1
byte0
8
Data Tx/Rx
SR (8bits)
1
MSB LSB
5.2.2.2. Size
The FIFO size is fixed to 66 bytes.
Page 45
FifoLevel
Note - FifoLevel interrupt is updated only after a read or write operation on the FIFO. Thus the interrupt cannot be
dynamically updated by only changing the FifoThreshold parameter
- FifoLevel interrupt is valid as long as FifoFull does not occur. An empty FIFO will restore its normal operation
Table 20 Status of FIFO when Switching Between Different Modes of the Module
From To FIFO status Comments
Stdby Sleep Not cleared
Sleep Stdby Not cleared
Stdby/Sleep Tx Not cleared To allow the user to write the FIFO in Stdby/Sleep before Tx
Stdby/Sleep Rx Cleared
Rx Tx Cleared
Rx Stdby/Sleep Not cleared To allow the user to read FIFO in Stdby/Sleep mode after Rx
Tx Any Cleared
5.2.3.1. Overview
Sync word recognition (also called Pattern recognition) is activated by setting SyncOn in RegSyncConfig. The bit
synchronizer must also be activated in continuous mode (automatically done in Packet mode) .
The block behaves like a shift register; it continuously compares the incoming data with its internally programmed Sync
word and sets SyncAddressMatch when a match is detected. This is illustrated in Figure 28 below.
Page 46
Rx DATA
Bit N-x = Bit N-1 = Bit N =
(NRZ) Sync_value[x] Sync_value[1] Sync_value[0]
DCLK
SyncAddressMatch
During the comparison of the demodulated data, the first bit received is compared with bit 7 (MSB) of RegSyncValue1 and
the last bit received is compared with bit 0 (LSB) of the last byte whose address is determined by the length of the Sync
word.
When the programmed Sync word is detected the user can assume that this incoming packet is for the node and can be
processed accordingly.
5.2.3.2. Configuration
Size: Sync word size can be set from 1 to 8 bytes (i.e. 8 to 64 bits) via SyncSize in RegSyncConfig. In Packet mode
this field is also used for Sync word generation in Tx mode.
Error tolerance: The number of errors tolerated in the Sync word recognition can be set from 0 to 7 bits to via
SyncTol.
Value: The Sync word value is configured in SyncValue(63:0). In Packet mode this field is also used for Sync word
generation in Tx mode.
5.2.5. Control
The control block configures and controls the full module's behavior according to the settings programmed in the
configuration registers.
Note Received Data is only shown on the Data signal between RxReady and PayloadReadys rising edges
Page 48
Tx/Rx DIO0
DIO1/DCLK
DIO2/DATA
CONTROL DIO3
DIO4
DIO5
Data Rx
SYNC
RECOG.
SPI
NSS
SCK
MOSI
MISO
5.4.2. Tx Processing
In Tx mode, a synchronous data clock for an external uC is provided on DIO1/DCLK pin. Clock timing with respect to the
data is illustrated in Figure 30. DATA is internally sampled on the rising edge of DCLK so the uC can change logic state
anytime outside the grayed out setup/hold zone.
T_DATA T_DATA
DATA
(NRZ)
DCLK
Page 49
5.4.3. Rx Processing
If the bit synchronizer is disabled, the raw demodulator output is made directly available on DATA pin and no DCLK signal
is provided.
Conversely, if the bit synchronizer is enabled, synchronous cleaned data and clock are made available respectively on
DIO2/DATA and DIO1/DCLK pins. DATA is sampled on the rising edge of DCLK and updated on the falling edge as
illustrated below.
DATA (NRZ)
DCLK
Note in Continuous mode it is always recommended to enable the bit synchronizer to clean the DATA signal even if the
DCLK signal is not used by the uC (bit synchronizer is automatically enabled in Packet mode).
In addition, the RFM69HCW packet handler performs several packet oriented tasks such as Preamble and Sync word
generation, CRC calculation/check, whitening/dewhitening of data, Manchester encoding/decoding, address filtering, AES
encryption/decryption, etc. This simplifies software and reduces uC overhead by performing these repetitive tasks within
the RF module itself.
Another important feature is ability to fill and empty the FIFO in Sleep/Stdby mode, ensuring optimum power consumption
and adding more flexibility for the software.
Page 50
DIO0
DIO1
DIO2
CONTROL DIO3
DIO4
DIO5
Data Rx
SYNC
RECOG.
PACKET FIFO
HANDLER SPI
(+SR)
Tx NSS
SCK
MOSI
MISO
In applications where the packet length is fixed in advance, this mode of operation may be of interest to minimize RF
overhead (no length byte field is required). All nodes, whether Tx only, Rx only, or Tx/Rx should be programmed with the
same packet length value.
The length of the payload is limited to 255 bytes if AES is not enabled else the message is limited to 64 bytes (i.e. max 65
bytes payload if Address byte is enabled).
The length programmed in PayloadLength relates only to the payload which includes the message and the optional
address byte. In this mode, the payload must contain at least one byte, i.e. address or message byte.
An illustration of a fixed length packet is shown below. It contains the following fields:
Preamble (1010...)
Sync word (Network ID)
Optional Address byte (Node ID)
Message data
Optional 2-bytes CRC checksum
Page 51
Preamble
Sync Word Address Message CRC
0 to 65535
0 to 8 bytes byte Up to 255 bytes 2-bytes
bytes
Payload
(min 1 byte)
This mode is useful in applications where the length of the packet is not known in advance and can vary over time. It is then
necessary for the transmitter to send the length information together with each packet in order for the receiver to operate
properly.
In this mode the length of the payload, indicated by the length byte, is given by the first byte of the FIFO and is limited to
255 bytes if AES is not enabled else the message is limited to 64 bytes (i.e. max 66 bytes payload if Address byte is
enabled). Note that the length byte itself is not included in its calculation. In this mode, the payload must contain at least 2
bytes, i.e. length + address or message byte.
An illustration of a variable length packet is shown below. It contains the following fields:
Preamble (1010...)
Sync word (Network ID)
Length byte
Optional Address byte (Node ID)
Message data
Optional 2-bytes CRC checksum
DC free Data encoding
CRC checksum calculation
AES Enc/Dec
Preamble
Sync Word Length Address Message CRC
0 to 65535
0 to 8 bytes byte byte Up to 255 bytes 2-bytes
bytes
Payload
(min 2 bytes)
The user can then transmit and receive packet of arbitrary length and PayloadLength register is not used in Tx/Rx modes
for counting the length of the bytes transmitted/received. This mode is a replacement for the legacy buffered mode in
RF63/RF64 transceivers.
In Tx the data is transmitted depending on the TxStartCondition bit. On the Rx side the data processing features like
Address filtering, Manchester encoding and data whitening are not available if the sync pattern length is set to zero
(SyncOn = 0). The filling of the FIFO in this case can be controlled by the bit FifoFillCondition. The CRC detection in Rx is
also not supported in this mode of the packet handler, however CRC generation in Tx is operational. The interrupts like
CrcOk & PayloadReady are not available either.
Preamble
Sync Word Address Message
0 to 65535
0 to 8 bytes byte unlimited length
bytes
Payload
Only the payload (including optional address and length fields) is required to be provided by the user in the FIFO.
Page 53
The transmission of packet data is initiated by the Packet Handler only if the module is in Tx mode and the transmission
condition defined by TxStartCondition is fulfilled. If transmission condition is not fulfilled then the packet handler transmits a
preamble sequence until the condition is met. This happens only if the preamble length /= 0, otherwise it transmits a zero or
one until the condition is met to transmit the packet data.
Only the payload (including optional address and length fields) is made available in the FIFO.
When the Rx mode is enabled the demodulator receives the preamble followed by the detection of sync word. If fixed
length packet format is enabled then the number of bytes received as the payload is given by the PayloadLength
parameter.
In variable length mode the first byte received after the sync word is interpreted as the length of the received packet. The
internal length counter is initialized to this received length. The PayloadLength register is set to a value which is greater
than the maximum expected length of the received packet. If the received length is greater than the maximum length stored
in PayloadLength register the packet is discarded otherwise the complete packet is received.
If the address check is enabled then the second byte received in case of variable length and first byte in case of fixed
length is the address byte. If the address matches to the one in the NodeAddress field, reception of the data continues
otherwise it's stopped. The CRC check is performed if CrcOn = 1 and the result is available in CrcOk indicating that the
CRC was successful. An interrupt (PayloadReady) is also generated on DIO0 as soon as the payload is available in the
FIFO. The payload available in the FIFO can also be read in Sleep/Standby mode.
If the CRC fails the PayloadReady interrupt is not generated and the FIFO is cleared. This function can be overridden by
setting CrcAutoClearOff = 1, forcing the availability of PayloadReady interrupt and the payload in the FIFO even if the CRC
fails.
5.5.5. AES
AES is the symmetric-key block cipher that provides the cryptographic capabilities to the transceiver. The system proposed
can work with 128-bit long fixed keys. The fixed key is stored in a 16-byte write only user configuration register, which
retains its value in Sleep mode.
Page 54
As shown in Figure 33 and Figure 34 above the message part of the Packet can be encrypted and decrypted with the
cipher 128- cipher key stored in the configuration registers.
5.5.5.1. Tx Processing
1. User enters the data to be transmitted in FIFO in Stdby/Sleep mode and gives the transmit command.
2. On Tx command the Packet handler state machine takes over the control and If encryption is enabled then the
message inside the FIFO is read in blocks of 16 bytes (padded with 0s if needed), encrypted and stored back to FIFO.
All this processing is done in Tx mode before enabling the packet handling state machine. Only the Message part of the
packet is encrypted and preamble, sync word, length byte, address byte and CRC are not encrypted.
3. Once the encryption is done the Packet handling state machine is enabled to transmit the data.
5.5.5.2. Rx Processing
1. The data received is stored in the FIFO, The address, CRC interrupts are generated as usual because these
parameters were not encrypted.
2. Once the complete packet has been received. The data is read from the FIFO, decrypted and written back to FIFO.
The PayloadReady interrupt is issued once the decrypted data is ready in the FIFO for reading via the SPI interface.
The AES encryption/decryption cannot be used on the fly i.e. while transmitting and receiving data. Thus when AES
encryption/decryption is enabled, the FIFO acts as a simple buffer. This buffer is filled before initiating any transmission.
The data in the buffer is then encrypted before the transmission can begin. On the receive side the decryption is initiated
only once the complete packet has been received in the buffer.
The encryption/decryption process takes approximately 7.0 us per 16-byte block. Thus for a maximum of 4 blocks (i.e. 64
bytes) it can take up to 28 us for completing the cryptographic operations.
The receive side sees the AES decryption time as a sequential delay before the PayloadReady interrupt is available.
The Tx side sees the AES encryption time as a sequential delay in the startup of the Tx chain, thus the startup time of the
Tx will increase according to the length of data.
In Fixed length mode the Message part of the payload that can be encrypted/decrypted can be 64 bytes long. If the
address filtering is enabled, the length of the payload should be at max 65 bytes in this case.
In Variable length mode the Max message size that can be encrypted/decrypted is also 64 bytes when address filtering is
disabled, else it is 48 bytes. Thus, including length byte, the length of the payload is max 65 or 50 bytes (the latter when
address filtering is enabled).
If the address filtering is expected then AddressFiltering must be enabled on the transmitter side as well to prevent address
byte to be encrypted.
Crc check being performed on encrypted data, CrcOk interrupt will occur "decryption time" before PayloadReady interrupt.
Page 55
For Tx:
FIFO can be prefilled in Sleep/Standby but must be refilled "on-the-fly" during Tx with the rest of the payload.
1) Prefill FIFO (in Sleep/Standby first or directly in Tx mode) until FifoThreshold or FifoFull is set
2) In Tx, wait for FifoThreshold or FifoNotEmpty to be cleared (i.e. FIFO is nearly empty)
3) Write bytes into the FIFO until FifoThreshold or FifoFull is set.
4) Continue to step 2 until the entire message has been written to the FIFO (PacketSent will fire when the last bit of the
packet has been sent).
For Rx:
FIFO must be unfilled "on-the-fly" during Rx to prevent FIFO overrun.
1) Start reading bytes from the FIFO when FifoNotEmpty or FifoThreshold becomes set.
2) Suspend reading from the FIFO if FifoNotEmpty clears before all bytes of the message have been read
3) Continue to step 1 until PayloadReady or CrcOk fires
4) Read all remaining bytes from the FIFO either in Rx or Sleep/Standby mode
Note AES encryption is not feasible on large packets, since all Payload bytes need to be in the FIFO at the same time to
perform encryption
Every received packet which does not start with this locally configured Sync word is automatically discarded and no
interrupt is generated.
When the Sync word is detected, payload reception automatically starts and SyncAddressMatch is asserted.
Page 56
Please note that the received address byte, as part of the payload, is not stripped off the packet and is made available in
the FIFO. In addition, NodeAddress and AddressFiltering only apply to Rx. On Tx side, if address filtering is expected, the
address byte should simply be put into the FIFO like any other byte of the payload.
As address filtering requires a Sync word match, both features share the same interrupt flag SyncAddressMatch.
Please note that the received length byte, as part of the payload, is not stripped off the packet and is made available in the
FIFO.
To disable this function the user should set the value of the PayloadLength to 255.
By default, if the CRC check fails then the FIFO is automatically cleared and no interrupt is generated. This filtering function
can be disabled via CrcAutoClearOff bit and in this case, even if CRC fails, the FIFO is not cleared and only PayloadReady
interrupt goes high. Please note that in both cases, the two CRC checksum bytes are stripped off by the packet handler
and only the payload is made available in the FIFO.
The CRC is based on the CCITT polynomial as shown below. This implementation also detects errors due to leading and
trailing zeros.
Page 57
For such purposes, two techniques are made available in the packet handler: Manchester encoding and data whitening.
The NRZ data is converted to Manchester code by coding '1' as "10" and '0' as "01".
In this case, the maximum chip rate is the maximum bit rate given in the specifications section and the actual bit rate is half
the chip rate.
Manchester encoding and decoding is only applied to the payload and CRC checksum while preamble and Sync word are
kept NRZ. However, the chip rate from preamble to CRC is the same and defined by BitRate in RegBitRate (Chip Rate =
Bit Rate NRZ = 2 x Bit Rate Manchester).
Manchester encoding/decoding is thus made transparent for the user, who still provides/retrieves NRZ data to/from the
FIFO
Page 58
The whitening/de-whitening process is enabled if DcFree = 10. A 9-bit LFSR is used to generate a random sequence. The
payload and 2-byte CRC checksum is then XORed with this random sequence as shown below. The data is de-whitened
on the receiver side by XORing with the same random sequence.
Payload whitening/de-whitening is thus made transparent for the user, who still provides/retrieves NRZ data to/from the
FIFO.
L F S R P o ly n o m ia l = X 9 + X 5 + 1
X8 X7 X6 X5 X4 X3 X2 X1 X0
T ra n s m it d a ta W h ite n e d d a ta
Page 59
Default
Reset
Address Register Name (recom Description
(built-in)
mended)
Page 60
Tel: +86-755-82973805 Fax: +86-755-82973550 E-mail: sales@hoperf.com http:/ / www.hoperf.com
RFM69HCW
ADVANCED COMMUNICATIONS & SENSING DATASHEET
Default
Reset
Address Register Name (recom Description
(built-in)
mended)
0x1A RegAfcBw 0x8A 0x8B Channel Filter BW control during the AFC routine
0x1B RegOokPeak 0x40 OOK demodulator selection and control in peak mode
0x26 RegDioMapping2 0x05 0x07 Mapping of pins DIO4 and DIO5, ClkOut frequency
0x27 RegIrqFlags1 0x80 Status register: PLL Lock state, Timeout, RSSI > Threshold...
0x2A RegRxTimeout1 0x00 Timeout duration between Rx request and RSSI detection
0x2B RegRxTimeout2 0x00 Timeout duration between RSSI detection and PayloadReady
Page 61
Tel: +86-755-82973805 Fax: +86-755-82973550 E-mail: sales@hoperf.com http:/ / www.hoperf.com
RFM69HCW
Default
Reset
Address Register Name (recom Description
(built-in)
mended)
0x71 RegTestAfc 0x00 AFC offset for low modulation index AFC
Note - Reset values are automatically refreshed in the chip at Power On Reset
- Default values are recommended register values, optimizing the device operation
- Registers for which the Default value differs from the Reset value are denoted by a * in the tables of section 6
Page 62
Tel: +86-755-82973805 Fax: +86-755-82973550 E-mail: sales@hoperf.com http:/ / www.hoperf.com
RFM69HCW
in OOK:
00 no shaping
01 filtering with fcutoff = BR
10 filtering with fcutoff = 2*BR
11 reserved
RegBitrateMsb 7-0 BitRate(15:8) rw 0x1a MSB of Bit Rate (Chip Rate when Manchester encoding is
(0x03) enabled)
Page 63
Tel: +86-755-82973805 Fax: +86-755-82973550 E-mail: sales@hoperf.com http:/ / www.hoperf.com
RFM69HCW
ADVANCED COMMUNICATIONS & SENSING DATASHEET
RegBitrateLsb 7-0 BitRate(7:0) rw 0x0b LSB of Bit Rate (Chip Rate if Manchester encoding is
(0x04) enabled)
FXO SC
BitRate = ----------------------------------
BitRate(15,0)
Default value: 4.8 kb/s
RegFdevMsb 7-6 - r 00 unused
(0x05) 5-0 Fdev(13:8) rw 000000 MSB of the frequency deviation
RegFdevLsb 7-0 Fdev(7:0) rw 0x52 LSB of the frequency deviation
(0x06) Fdev = Fstep Fdev(15,0)
Default value: 5 kHz
RegFrfMsb 7-0 Frf(23:16) rw 0xe4 MSB of the RF carrier frequency
(0x07)
RegFrfMid 7-0 Frf(15:8) rw 0xc0 Middle byte of the RF carrier frequency
(0x08)
RegFrfLsb 7-0 Frf(7:0) rw 0x00 LSB of the RF carrier frequency
(0x09) Frf = Fstep Frf 23;0
Default value: Frf = 915 MHz (32 MHz XO)
RegOsc1 7 RcCalStart w 0 Triggers the calibration of the RC oscillator when set.
(0x0A) Always reads 0. RC calibration must be triggered in
Standby mode.
6 RcCalDone r 1 0 RC calibration in progress
1 RC calibration is over
5-0 - r 000001 unused
RegAfcCtrl 7-6 - r 00 unused
(0x0B) 5 AfcLowBetaOn rw 0 Improved AFC routine for signals with modulation index
lower than 2. Refer to section 3.4.16 for details
0 Standard AFC routine
1 Improved AFC routine
4-0 - r 00000 unused
Reserved0C 7-0 - r 0x02 unused
(0x0C)
Page 64
Tel: +86-755-82973805 Fax: +86-755-82973550 E-mail: sales@hoperf.com http:/ / www.hoperf.com
RFM69HCW
ADVANCED COMMUNICATIONS & SENSING DATASHEET
RegListen1 7-6 ListenResolIdle rw 10 Resolution of Listen mode Idle time (calibrated RC osc):
(0x0D) 00 reserved
01 64 us
10 4.1 ms
11 262 ms
5-4 ListenResolRx rw 01 Resolution of Listen mode Rx time (calibrated RC osc):
00 reserved
01 64 us
10 4.1 ms
11 262 ms
3 ListenCriteria rw 0 Criteria for packet acceptance in Listen mode:
0 signal strength is above RssiThreshold
1 signal strength is above RssiThreshold and
SyncAddress matched
2-1 ListenEnd rw 01 Action taken after acceptance of a packet in Listen mode:
00 chip stays in Rx mode. Listen mode stops and must
be disabled (see section 4.3).
01 chip stays in Rx mode until PayloadReady or
Timeout interrupt occurs. It then goes to the mode defined
by Mode. Listen mode stops and must be disabled (see
section 4.3).
10 chip stays in Rx mode until PayloadReady or
Timeout interrupt occurs. Listen mode then resumes in
Idle state. FIFO content is lost at next Rx wakeup.
11 Reserved
0 - r 0 unused
RegListen2 7-0 ListenCoefIdle rw 0xf5 Duration of the Idle phase in Listen mode.
(0x0E) t ListenIdle = ListenCoefIdle ListenResolIdle
RegListen3 7-0 ListenCoefRx rw 0x20 Duration of the Rx phase in Listen mode (startup time
(0x0F) included, see section 4.2.3)
t ListenRx = ListenCoefRx ListenResolRx
RegVersion Version code of the chip. Bits 7-4 give the full revision
(0x10) 7-0 Version r 0x24 number; bits 3-0 give the metal mask revision number.
Page 65
Tel: +86-755-82973805 Fax: +86-755-82973550 E-mail: sales@hoperf.com http:/ / www.hoperf.com
RFM69HCW
ADVANCED COMMUNICATIONS & SENSING DATASHEET
Page 66
Tel: +86-755-82973805 Fax: +86-755-82973550 E-mail: sales@hoperf.com http:/ / www.hoperf.com
RFM69HCW
ADVANCED COMMUNICATIONS & SENSING DATASHEET
OOK Mode:
FXOSC
RxBw = -----------------------------------------------------------------
RxBwExp + 3
RxBwMant 2
See Table 14 for tabulated values
RegAfcBw 7-5 DccFreqAfc rw 100 DccFreq parameter used during the AFC
(0x1A) 4-3 RxBwMantAfc rw 01 RxBwMant parameter used during the AFC
2-0 RxBwExpAfc rw 011 * RxBwExp parameter used during the AFC
Page 67
Tel: +86-755-82973805 Fax: +86-755-82973550 E-mail: sales@hoperf.com http:/ / www.hoperf.com
RFM69HCW
ADVANCED COMMUNICATIONS & SENSING DATASHEET
RegOokPeak 7-6 OokThreshType rw 01 Selects type of threshold in the OOK data slicer:
(0x1B) 00 fixed 10 average
01 peak 11 reserved
5-3 OokPeakTheshStep rw 000 Size of each decrement of the RSSI threshold in the OOK
demodulator:
000 0.5 dB 001 1.0 dB
010 1.5 dB 011 2.0 dB
100 3.0 dB 101 4.0 dB
110 5.0 dB 111 6.0 dB
2-0 OokPeakThreshDec rw 000 Period of decrement of the RSSI threshold in the OOK
demodulator:
000 once per chip 001 once every 2 chips
010 once every 4 chips 011 once every 8 chips
100 twice in each chip 101 4 times in each chip
110 8 times in each chip 111 16 times in each chip
RegOokAvg 7-6 OokAverageThreshFilt rw 10 Filter coefficients in average mode of the OOK
(0x1C) demodulator:
00 fC chip rate / 32. 01 fC chip rate / 8.
10 fC chip rate / 4. 11 fC chip rate / 2.
5-0 - r 000000 unused
RegOokFix 7-0 OokFixedThresh rw 0110 Fixed threshold value (in dB) in the OOK demodulator.
(0x1D) (6dB) Used when OokThresType = 00
RegAfcFei 7 - r 0 unused
(0x1E) 6 FeiDone r 0 0 FEI is on-going
1 FEI finished
5 FeiStart w 0 Triggers a FEI measurement when set. Always reads 0.
4 AfcDone r 1 0 AFC is on-going
1 AFC has finished
3 AfcAutoclearOn rw 0 Only valid if AfcAutoOn is set
0 AFC register is not cleared before a new AFC phase
1 AFC register is cleared before a new AFC phase
2 AfcAutoOn rw 0 0 AFC is performed each time AfcStart is set
1 AFC is performed each time Rx mode is entered
1 AfcClear w 0 Clears the AfcValue if set in Rx mode. Always reads 0
0 AfcStart w 0 Triggers an AFC when set. Always reads 0.
RegAfcMsb 7-0 AfcValue(15:8) r 0x00 MSB of the AfcValue, 2s complement format
(0x1F)
RegAfcLsb 7-0 AfcValue(7:0) r 0x00 LSB of the AfcValue, 2s complement format
(0x20) Frequency correction = AfcValue x Fstep
RegFeiMsb 7-0 FeiValue(15:8) r - MSB of the measured frequency offset, 2s complement
(0x21)
RegFeiLsb 7-0 FeiValue(7:0) r - LSB of the measured frequency offset, 2s complement
(0x22) Frequency error = FeiValue x Fstep
RegRssiConfig 7-2 - r 000000 unused
(0x23) 1 RssiDone r 1 0 RSSI is on-going
1 RSSI sampling is finished, result available
0 RssiStart w 0 Trigger a RSSI measurement when set. Always reads 0.
RegRssiValue 7-0 RssiValue r 0xFF Absolute value of the RSSI in dBm, 0.5dB steps.
(0x24) RSSI = -RssiValue/2 [dBm]
Page 68
Tel: +86-755-82973805 Fax: +86-755-82973550 E-mail: sales@hoperf.com http:/ / www.hoperf.com
RFM69HCW
ADVANCED COMMUNICATIONS & SENSING DATASHEET
Page 69
Tel: +86-755-82973805 Fax: +86-755-82973550 E-mail: sales@hoperf.com http:/ / www.hoperf.com
RFM69HCW
ADVANCED COMMUNICATIONS & SENSING DATASHEET
RegIrqFlags2 7 FifoFull r 0 Set when FIFO is full (i.e. contains 66 bytes), else
(0x28) cleared.
6 FifoNotEmpty r 0 Set when FIFO contains at least one byte, else cleared
5 FifoLevel r 0 Set when the number of bytes in the FIFO strictly exceeds
FifoThreshold, else cleared.
4 FifoOverrun rwc 0 Set when FIFO overrun occurs. (except in Sleep mode)
Flag(s) and FIFO are cleared when this bit is set. The
FIFO then becomes immediately available for the next
transmission / reception.
3 PacketSent r 0 Set in Tx when the complete packet has been sent.
Cleared when exiting Tx.
2 PayloadReady r 0 Set in Rx when the payload is ready (i.e. last byte
received and CRC, if enabled and CrcAutoClearOff is
cleared, is Ok). Cleared when FIFO is empty.
1 CrcOk r 0 Set in Rx when the CRC of the payload is Ok. Cleared
when FIFO is empty.
0 - r 0 unused
RegRssiThresh 7-0 RssiThreshold rw 0xE4 RSSI trigger level for Rssi interrupt :
(0x29) * - RssiThreshold / 2 [dBm]
RegRxTimeout1 7-0 TimeoutRxStart rw 0x00 Timeout interrupt is generated TimeoutRxStart*16*Tbit
(0x2A) after switching to Rx mode if Rssi interrupt doesnt occur
(i.e. RssiValue > RssiThreshold)
0x00: TimeoutRxStart is disabled
RegRxTimeout2 7-0 TimeoutRssiThresh rw 0x00 Timeout interrupt is generated TimeoutRssiThresh*16*Tbit
(0x2B) after Rssi interrupt if PayloadReady interrupt doesnt
occur.
0x00: TimeoutRssiThresh is disabled
Page 70
Page 71
Page 72
Page 73
Page 74
7. Application Information
7.1. Crystal Resonator Specification
Table 31 shows the crystal resonator specification for the crystal reference oscillator circuit of the RFM69HCW.
This specification covers the full range of operation of the RFM69HCW and is employed in the reference design.
Notes - the initial frequency tolerance, temperature stability and ageing performance should be chosen in accordance
with the target operating temperature range and the receiver bandwidth selected.
- the loading capacitance should be applied externally, and adapted to the actual Cload specification of the XTAL.
- A minimum XTAL frequency of 28 MHz is required to cover the 863-870 MHz band, 29 MHz for the 902-928 MHz
band
7.2.1. POR
If the application requires the disconnection of VDD from the RFM69HCW, despite of the extremely low Sleep Mode
current, the user should wait for 10 ms from of the end of the POR cycle before commencing communications over the SPI
bus. Pin
6 (Reset) should be left floating during the POR sequence.
VDD
Pin Reset
Undefined
(output)
Wait for Module is ready
10 ms from this point on
Page 75
Note whilst pin RESET is driven high, an over current consumption of up to ten milliamps can be seen on VDD.
Page 76
8. Packaging Information
Page 77
8.1. Package Outline Drawing
Tel: +86-755-82973805 Fax: +86-755-82973550 E-mail: sales@hoperf.com http:/ / www.hoperf.com
RFM69HCW
Page 78
DRFM69HCW 433 S2
Package
Operation Band
Mode Type
P/N: RFM69HCW-315S2
RFM69HCW module at 315MHz band, SMD Package
P/N: RFM69HCW-433S2
RFM69HCW module at 433MHz band, SMD Package
P/N: RFM69HCW-868S2
RFM69HCW module at 868MHz band, SMD Package
P/N: RFM69HCW-915S2
RFM69HCW module at 915MHz band, SMD PackageV
Page 79