nRF24L01+ as TX / nRF52 as RX no received event

RE: nRF24L01+ as TX / nRF52 as RX no received event

ovrebekk — Tue, 02 Feb 2021 08:36:59 GMT

Thanks for the confirmation!

I was pretty sure this was the way to do it, but great to get it confirmed since I haven't tested it in a while 🙂

Best regards
Torbjørn

RE: nRF24L01+ as TX / nRF52 as RX no received event

Eric Nguyen — Mon, 01 Feb 2021 06:45:03 GMT

Your tip is absolutely correct. I've already changed it into
uint8_t base_addr_0[4] = { 0x02, 0x03, 0x07, 0x07};
uint8_t base_addr_1[4] = { 0x02, 0x03, 0x07, 0x07};
uint8_t addr_prefix[8] = { 0x01, 0x02, 0x03, 0x04, 0x05, 0x06, 0x07, 0x08 };

And it totally works.

RE: nRF24L01+ as TX / nRF52 as RX no received event

ovrebekk — Mon, 01 Feb 2021 06:22:14 GMT

I am glad to hear you were able to figure it out 🙂

Can you confirm whether or not my earlier tip was correct?

"I believe base_addr_0 should be 0x02, 0x03, 0x07, 0x07 in your case, and the first byte of the addr_prefix array should be 0x01"

Best regards
Torbjørn

RE: nRF24L01+ as TX / nRF52 as RX no received event

Eric Nguyen — Sun, 31 Jan 2021 02:45:22 GMT

I've already done with your advice. Thank you so much

RE: nRF24L01+ as TX / nRF52 as RX no received event

ovrebekk — Fri, 29 Jan 2021 09:17:18 GMT

Assuming you can change the address on both side, a general tip is to start with an address that doesn't change if you get the byte order or bit order wrong, such as the default 0xE7, 0xE7, 0xE7, 0xE7, 0xE7.

Once that is working you can change one byte at a time, which makes the room for error much smaller.

Also, I would recommend having a look at this ESB compatibility guide:
https://infocenter.nordicsemi.com/index.jsp?topic=%2Fcom.nordic.infocenter.sdk5.v15.0.0%2Fesb_users_guide.html&cp=4_0_1_5_1_2&anchor=esb_backwards

I believe base_addr_0 should be 0x02, 0x03, 0x07, 0x07 in your case, and the first byte of the addr_prefix array should be 0x01, but I don't currently have an nRF24L01+ available to test with.

Best regards
Torbjørn

RE: nRF24L01+ as TX / nRF52 as RX no received event

Eric Nguyen — Thu, 28 Jan 2021 08:37:18 GMT

Hi ovrebekk

Like you said before:

"I think the problem might be in the address generation.

Assuming this is the address:

const byte addr[5] = {0x30, 0x26, 0xDA, 0x91, 0xD3};

It is the first byte in the buffer (0x30) that is the prefix, and the remaining bytes that are the base. If you change the address configuration on the nRF52 side that should fix the issue."

If my address nRF24L is

uint8_t TX_ADDR_P0={0x01,0x02,0x03,0x07,0x07};

uint8_t RX_ADDR_P0={0x01,0x02,0x03,0x07,0x07};

How do I convert it into base address and prefix?

Please help me fix this problem, what should I fill in blank below . I've stucked with it for a long time:

uint8_t base_addr_0[4] = {0x..., 0x..., 0x..., 0x...};

uint8_t base_addr_1[4] = {0x..., 0x..., 0x..., 0x...};

uint8_t addr_prefix[8] = {0x..., 0x..., 0x..., 0x..., 0x..., 0x..., 0x..., 0x... };

RE: nRF24L01+ as TX / nRF52 as RX no received event

ovrebekk — Mon, 07 Aug 2017 11:43:36 GMT

Hehe, hate when that happens ;)

RE: nRF24L01+ as TX / nRF52 as RX no received event

Sebastien Huet — Fri, 04 Aug 2017 12:12:14 GMT

Yes, the one hiding the other ;o).

RE: nRF24L01+ as TX / nRF52 as RX no received event

ovrebekk — Fri, 04 Aug 2017 08:59:34 GMT

Ok, so the address thing I mentioned below was one of the issues?

RE: nRF24L01+ as TX / nRF52 as RX no received event

Sebastien Huet — Fri, 04 Aug 2017 06:59:40 GMT

Hi Torbjørn,

I will open another thread about my issue regarding NRF52<=>NRF24 static payload communication.

RE: nRF24L01+ as TX / nRF52 as RX no received event

Sebastien Huet — Thu, 03 Aug 2017 16:13:32 GMT

The challenge looks like having NRF52 <=> NRF24 talking with static payload.

RE: nRF24L01+ as TX / nRF52 as RX no received event

Sebastien Huet — Thu, 03 Aug 2017 14:47:13 GMT

FYI I have tested NRF52 -> NRF24 using the sample here and it works until i define NRF_ESB_LEGACY

RE: nRF24L01+ as TX / nRF52 as RX no received event

Sebastien Huet — Thu, 03 Aug 2017 14:18:35 GMT

Hi Torbjørn,

Many thanks ! It helps.

What i see now is that i lost a lot of packets NRF52 -> NRF24 and the datas do not look accurate.

4981 03:00:B1:00
18390 03:00:B1:00
20852 02:0C:D7:55
...

1st col is receiver milliseconds. enormous gap.

NRF24 -> NRF52 does not work at all.

NRF24 -> NRF24 ok.
NRF52 -> NRF52 ok.

Any clue?

RE: nRF24L01+ as TX / nRF52 as RX no received event

ovrebekk — Thu, 03 Aug 2017 13:17:37 GMT

Hi Sebastien

I think the problem might be in the address generation.

Assuming this is the address:

const byte addr[5] = {0x30, 0x26, 0xDA, 0x91, 0xD3};

It is the first byte in the buffer (0x30) that is the prefix, and the remaining bytes that are the base. If you change the address configuration on the nRF52 side that should fix the issue.

Best regards

RE: nRF24L01+ as TX / nRF52 as RX no received event

Sebastien Huet — Wed, 02 Aug 2017 15:04:23 GMT

I have replaced the spyed receiver with another nRF52 pca10040 with esb ptx sample updated to reflect the same configuration: it works.

In short:

 OK: Spyed device => Leonardo + NRF24L01+
 OK: NRF52           => NRF52 
NOK: Spyed device => NRF52 NOK
NOK: NRF52           => Leonardo + NRF24L01+