Well, I guess it's debatable but in short the datasheet for the nRF24L01+ says that data should be clocked over the SPI bus LSByte first. However this is not what RF24 does!
For RF24.cpp↔︎RF24.cpp communication, this isn't a problem since it's read back in the same order too. But because of that right now users of our code will get everything "in reverse" when talking to an e.g. Arduino :-/
Probably best to just add a special option to openPipe to handle this automatically for the user, otherwise this will be a major compatibility annoyance!
Well, I guess it's debatable but in short the datasheet for the nRF24L01+ says that data should be clocked over the SPI bus LSByte first. However this is not what RF24 does!
For RF24.cpp↔︎RF24.cpp communication, this isn't a problem since it's read back in the same order too. But because of that right now users of our code will get everything "in reverse" when talking to an e.g. Arduino :-/
Probably best to just add a special option to openPipe to handle this automatically for the user, otherwise this will be a major compatibility annoyance!