RF69 datasheet(54/81 Pages) ETC2

54 / 81 page

RF69

Page 53

Tel: +86-755-82973805 Fax: +86-755-82973550 E-mail: sales@hoperf.com http://www.hoperf.com

5.5.2.3. Unlimited Length Packet Format

Unlimited length packet format is selected when bit PacketFormat is set to 0 and PayloadLength is set to 0.

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.

An unlimited length packet shown in is made up of the following fields:



Preamble (1010...).



Sync word (Network ID).



Optional Address byte (Node ID).



Message data



Optional 2-bytes CRC checksum (Tx only)

DC free Data encoding

Preamble

0 to 65535

bytes

Sync Word

0 to 8 bytes

Address

byte

Message

unlimited length

Payload

Fields added by the packet handler in Tx and processed and removed in Rx

Message part of the payload

Optional User provided fields which are part of the payload

Figure 35. Unlimited Length Packet Format

5.5.3. Tx Processing (without AES)

In Tx mode the packet handler dynamically builds the packet by performing the following operations on the payload

available in the FIFO:



Add a programmable number of preamble bytes



Add a programmable Sync word

 Optionally calculating CRC over complete payload field (optional length byte + optional address byte + message)

andappending the 2 bytes checksum.

 Optional DC-free encoding of the data (Manchester or whitening)

Only the payload (including optional address and length fields) is required to be provided by the user in the FIFO.

RF69 Datasheet(PDF) 54 Page - List of Unclassifed Manufacturers

RF69 Datasheet(HTML) 54 Page - List of Unclassifed Manufacturers

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

Datasheet Download

Link URL