You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am trying to receive an XN297L with an NRF24L01.
CRC is disabled, No ACK, and fixed payload size (8 bytes).
I did SPI sniffing on the XN297L so I know what data it is sending and what is the real TX address.
But the problem is that when I use an NRF24L01 to try to receive it receives but in some weird behaviour.
I set the Address of the NRF to 0x710F55LL
I set the Address width to 3 bytes.
No CRC, disable Dynamic, Payload to 13 bytes...
And it works, but the data that I receive are distorted. Instead of a integer zero I receive 169. Instead of the real address I receive what appears to be another address. When the values must move from 0 to 50 I receive a lot of changing numbers but never the real one. Curiously the numbers does not change randomly, they change always in the same way.
Then I conclude that the modules are incompatible on how they transmit the payload data. Maybe in the preamble and in the address portion are the same (or maybe instead of 55 0F 71 the real value is other). Because when putting the remaining bytes of the address it does not acknowledge reception anymore.
I am still investigating.
The text was updated successfully, but these errors were encountered:
I found no solution it appears that they pack in a different way the data of the payloads. So no solution other than using an NRF24L01 in both sides.
I tested just reeplacing the XN297L with an NRF24L01 and that worked without modifying nothing on the other side (it is a controller for a quadcopter that I cannot modify the firmware). So the controller is working with stock firmware but using an NRF24L01 instead.
I am trying to receive an XN297L with an NRF24L01.
CRC is disabled, No ACK, and fixed payload size (8 bytes).
I did SPI sniffing on the XN297L so I know what data it is sending and what is the real TX address.
But the problem is that when I use an NRF24L01 to try to receive it receives but in some weird behaviour.
I set the Address of the NRF to 0x710F55LL
I set the Address width to 3 bytes.
No CRC, disable Dynamic, Payload to 13 bytes...
And it works, but the data that I receive are distorted. Instead of a integer zero I receive 169. Instead of the real address I receive what appears to be another address. When the values must move from 0 to 50 I receive a lot of changing numbers but never the real one. Curiously the numbers does not change randomly, they change always in the same way.
Then I conclude that the modules are incompatible on how they transmit the payload data. Maybe in the preamble and in the address portion are the same (or maybe instead of 55 0F 71 the real value is other). Because when putting the remaining bytes of the address it does not acknowledge reception anymore.
I am still investigating.
The text was updated successfully, but these errors were encountered: