Do RF24 radios need a physical reboot every few minutes to maintain a communication link?

RE: Do RF24 radios need a physical reboot every few minutes to maintain a communication link?

mikebyrne — Tue, 13 Apr 2021 08:12:28 GMT

Hi Kenneth,

I've now got my code working as expected. Thanks again for your help. I've left a full description my code changes in my other current RF24 ticket being handled by Håkon Alseth.

Kind Regards

Mike

RE: Do RF24 radios need a physical reboot every few minutes to maintain a communication link?

mikebyrne — Wed, 07 Apr 2021 16:14:33 GMT

Hi Kenneth,

Thank you again for your comments. To answer your points:

i) OK - I'm pleased to hear that regular resets are NOT needed for continued communication between the RF24s. This means that it's my code that is at fault.

ii) No, my code has not been using R_RX_PL_WID to check packet width, even though my code only ever transmits 3 or 4 bytes, but I will now add this check into my receive subroutines in case an event somehow produces > 32 bytes.

iii) As my setup is purely one PTX and one PRX, they use pipe0 only with the same address (as per the data sheet).

iv) My code doesn't need to actively read the pipe information in STATUS because of point iii above.

v) I will also re-code to reflect the full RX handling procedure described in the RF24 datasheet's table 27, STATUS register footnote (c), which I realise now I didn't implement fully.

I'll try the above code modifications and let you know how I get on.

Kind Regards & Thanks again!

Mike Byrne

RE: Do RF24 radios need a physical reboot every few minutes to maintain a communication link?

Kenneth — Tue, 06 Apr 2021 14:01:31 GMT

There should be no "reset" required no, though you may want to check out these Notes from the nRF24L01+ datasheet:

Note: Always check if the packet width reported is 32 bytes or shorter when using the R_RX_PL_WID command. If its width is longer than 32 bytes then the packet contains errors and must be discarded. Discard the packet by using the Flush_RX command.

Note: Always ensure that none of the data pipes have the same address.

Note: The 3 bit pipe information in the STATUS register is updated during the IRQ pin high to low transition. The pipe information is unreliable if the STATUS register is read during an IRQ pin high to low transition.