https://devzone.nordicsemi.com/f/nordic-q-a/78778/radio-length-field-and-actual-number-of-received-bytesHi all I am developing a proprietary radio protocol application using the nRF52805. I am not using a softdevice. Instead, this is all done by accessing the radio registers directly. This is not a BLE application. Briefly, the application involvesen-USTelligent Community 13Fri, 20 Aug 2021 14:51:13 GMThttps://devzone.nordicsemi.com/thread/326005?ContentTypeID=1Fri, 20 Aug 2021 14:51:13 GMT137ad170-7792-4731-bb38-c0d22fbe4515:a4e0ae9d-210b-4a4f-a463-c6d2dde98fa6Rob Garner<p>Hi run_ar</p> <p>Thank you for the quick reply. Yes, I do enable CRC checking. I also enable address filtering as well as Device Address filtering. Also, thanks for clarifying how the length field is handled during reception. I consider the question answered.</p> <p></p> <p>Thanks</p> <p>Rob&nbsp;</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/325937?ContentTypeID=1Fri, 20 Aug 2021 11:25:36 GMT137ad170-7792-4731-bb38-c0d22fbe4515:326b0341-8380-42f8-bc51-491588e6da64run_ar<p>1. No it doesn&#39;t update the field. IT echoes the value sent by the peripheral.</p> <p>2. No, you need to check the length of the packet that is copied to ram, for details see <span><a title="Packet configuration" href="https://infocenter.nordicsemi.com/topic/com.nordic.infocenter.nrf52832.ps.v1.1/radio.html?cp=4_2_0_22_1#concept_hz4_cjl_4r">Packet configuration</a></span></p> <p><span>Did you enable CRC checking? this will help tell your application if the packet is truncated or has error (to help detect the short packets you describe). You also need to make sure your logic handles buffer overflows, that could happen if the length field of the packet is corrupted on air.</span></p><div style="clear:both;"></div>