AN633
Rev. 0.7
65
10.11. Custom Packet Reception Containing Variable Length Field
This example code works the same way as the standard packet reception with the exception that the content of the
payload fields in the packet is customizable. It is possible to receive a packet whose payload data field length is not
known in advance. In such a scenario, the transmitted packet must contain byte(s) that specify the length of the
variable field. There is no requirement for length byte(s) to occur at one mandatory location in the packet (e.g.,
immediately following the Sync Word). However, the receiver must obviously know in advance which byte(s) of the
received packet represents the length value. Furthermore, these length byte(s) must be located in the packet
before the variable length field, else the packet handler in the receiver will not have the information in time to
allocate the received data bytes to the appropriate data field. The variable packet length byte(s) can be either in
field1, field2, field3, or field4. The variable packet length information must necessarily be a fixed length field.
The variable-length field need not immediately follow the length byte(s) but must occur after the field containing the
length byte(s). The variable-length field can be either in field2, field3, field4, or field5.
Figure 46. Structure of Valid Variable-Length Packet
Summary of Contents for EZRADIOPRO Si4060
Page 24: ...AN633 24 Rev 0 7 Figure 20 Supply Current versus Time Diagram from Shutdown to RX State...
Page 67: ...AN633 Rev 0 7 67 Figure 48 Variable Length Packet Reception Flowchart...
Page 69: ...AN633 Rev 0 7 69 Figure 50 Packet Matching Reception Flowchart...
Page 73: ...AN633 Rev 0 7 73 Figure 54 Packet Reception with Automatic RX Hopping Flowchart...
Page 75: ...AN633 Rev 0 7 75 Figure 56 Packet Reception with Manual Rx Hopping...
Page 80: ...AN633 80 Rev 0 7 Figure 62 Long Packet Transmission Workflow...
Page 81: ...AN633 Rev 0 7 81 Figure 63 Long Packet RX Flowchart...
