Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

5
  • 1
    Have thought about embedding an ID into the transmission and appending each transmission with a checksum? Commented Jun 11, 2017 at 10:57
  • @Andyaka 1- Good idea but I have already 32 byte limitation in packet transmission. 2- I think nRF24 does have default CRC checksum. Commented Jun 11, 2017 at 11:05
  • Without an ID, you cannot reliably detect the transmission source or do you have a cunning plan that you haven't mentioned? Commented Jun 11, 2017 at 11:07
  • @Andyaka I guess TMRH's RF24 library's available() method does take this issue into account. I don't know how to use it. tmrh20.github.io/RF24/… Commented Jun 11, 2017 at 11:33
  • You could use the pipe addresses as the ID for a small number of nodes by using a different one for each. Commented Jun 11, 2017 at 11:51