RF96 datasheet(72/121 Pages) HOPE

72 / 121 page

Page 72

RF96/97/98

Tel: +86-755-82973805

Fax: +86-755-82973550

E-mail: sales@hoperf.com http://www.hoperf.com

WIRELESS & SENSING

PRELIMINARY

DATASHEET

Address Based

Address filtering can be enabled via the AddressFiltering bits. It adds another level of filtering, above Sync word (i.e. Sync

must match first), typically useful in a multi-node networks where a network ID is shared between all nodes (Sync word)

and each node has its own ID (address).

Two address based filtering options are available:

 AddressFiltering = 01: Received address field is compared with internal register NodeAddress. If they match then the

packet is accepted and processed, otherwise it is discarded.

 AddressFiltering = 10: Received address field is compared with internal registers NodeAddress and BroadcastAddress.

If either is a match, the received packet is accepted and processed, otherwise it is discarded. This additional check with

a constant is useful for implementing broadcast in a multi-node networks

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.

Length Based

In variable length Packet mode, PayloadLength must be programmed with the maximum payload length permitted. If

received length byte is smaller than this maximum then the packet is accepted and processed, otherwise it is discarded.

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 2047.

CRC Based

The CRC check is enabled by setting bit CrcOn in RegPacketConfig1. It is used for checking the integrity of the message.

 On Tx side a two byte CRC checksum is calculated on the payload part of the packet and appended to the end of the

message

 On Rx side the checksum is calculated on the received payload and compared with the two checksum bytes received.

The result of the comparison is stored in bit CrcOk.

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. Two CRC implementations are selected with bit CrcWhiteningType.

Table 76 CRC Description

Crc Type

CrcWhiteningType

Polynomial

Seed Value

Complemented

CCITT

0 (default)

X16 + X12 + X5 + 1

0x1D0F

Yes

IBM

X16 + X15 + X2 + 1

0xFFFF

A C code implementation of each CRC type is proposed in Application Section 7.

RF96 Datasheet(PDF) 72 Page - HOPE Microelectronics CO., Ltd.

RF96 Datasheet(HTML) 72 Page - HOPE Microelectronics CO., Ltd.

Html Pages

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 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 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 ...More

Datasheet Descarga

Enlace URL