-
First off: This is pretty off-topic to this repo, I just hope someone here would be able to help me out since it seems related :D I have a 2.4GHz remote which uses a LT8900 chip. I have sniffed its SPI communication to figure out its registers, this is them:
Based off the NRF & LT documentation, I'd need to set the Channel to 78 which I have done
Now I have disabled AutoAck, Retries and CRC and set the data rate to 1MBPS, however no matter what I try as the address for the reading pipe, with no setup do I actually receive messages whenever I press a button on the remote - at best I get nothing, at worst I just get random messages unrelated to my keypresses. I am aware that the preamble of the remote is set to 3 bytes, so I tried prepending either 0xAA or 0x55 to the Syncword but to no avail so I am kinda stuck now. Any help would be appreciated, much thanks! |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments 8 replies
-
I got desperate and soldered my own MCU to the remotes LT Chip and I'm really out of ideas now. I am literally "forging" my own packets on the sender by sending |
Beta Was this translation helpful? Give feedback.
-
What's the bitrate ? |
Beta Was this translation helpful? Give feedback.
-
Its 1mbps |
Beta Was this translation helpful? Give feedback.
-
EDIT: Nevermind I got hex / dec / binary confused, it gets set to 250 kbps which is supported by the nRF but for some reason will not receive anything either. More things to look into I guess. |
Beta Was this translation helpful? Give feedback.
-
One more question if you dont mind, the receiver module I have is not a NRF24L01+ but rather its clone, Si24R1 Now I have replicated all the registers of the remote, including the syncword on my replicated transmitter (LT):
And adapted your emulation layer code on the receiver - And this works fine, if I use 1Mbps as the transfer rate, if I switch to 250kbps tho which is used by the remote I dont receive anything anymore all-else-equal. Are you aware of any differences between 1mbps and 250kbps or could this just be an incompatability of the cloned receiver? |
Beta Was this translation helpful? Give feedback.
I cracked the code, I think - For the one person who will stumble upon this thread in 10 years:
The LT chips have a configurable trailer after the syncword bytes, by default this one is 4 bits long - We can simply account for this by making the 0 bytes of the trailer part of the syncword / by adding 4 0 bits into the syncword
Furthermore, every byte sent by the LT chips is sent in reverse order, so when setting the address on the receiver, every byte needs to be reversed compared to the original syncword
Given these criteria, this is the syncword setup on the sender (LT)