nRF52833 cannot reply to the ack automatically after it receives a packet from the nRF24L01+

RE: nRF52833 cannot reply to the ack automatically after it receives a packet from the nRF24L01+

JackLan — Wed, 12 Jun 2024 07:39:29 GMT

Thanks!😁

RE: nRF52833 cannot reply to the ack automatically after it receives a packet from the nRF24L01+

Håkon Alseth — Wed, 12 Jun 2024 07:10:53 GMT

Always happy to help out. Hope you have a wonderful day!

Kind regards,

Håkon

RE: nRF52833 cannot reply to the ack automatically after it receives a packet from the nRF24L01+

JackLan — Tue, 11 Jun 2024 02:03:30 GMT

Fantastic! It works now.

Thanks very much.

RE: nRF52833 cannot reply to the ack automatically after it receives a packet from the nRF24L01+

Håkon Alseth — Mon, 10 Jun 2024 14:47:33 GMT

Hi,

This could be the culprit:

    NRF24L01_Set_TxAddr( &txAddr[0], 5 );                     
    NRF24L01_Set_RxAddr( 0, &addr[0], 5 );

Try setting the TX_ADDR equal to the RX P0 ADDR, as described in appendix A in the nrf24l01+ datasheet:

...
The RX address for data pipe 0 (RX_ADDR_P0) must be equal to the
TX address (TX_ADDR) in the PTX device

Kind regards,

Håkon

RE: nRF52833 cannot reply to the ack automatically after it receives a packet from the nRF24L01+

JackLan — Fri, 07 Jun 2024 14:15:18 GMT

- You're receiving a .length of 0x20 (32) on the nRF5-side, while the nRF24L series code seems to send 18 bytes?

No, the nRF24L+ sent out 32 bytes data.

- Is the content of the received payload correct?

The nRF5-side got the correct data.

- Have you tried dumping the register state of the nRF24L01+ side to see if everything is set as per wanted behavior?

I will check it later. But I don't think it's the nRF24L01+ issue because it runs well with other nRF24L01+ boards.

Does the nRF24L01+ need a specific configuration when it communicates with nRF52833? And could you help to provide a demo of nRF24L01+ communicating with nRF52833?

RE: nRF52833 cannot reply to the ack automatically after it receives a packet from the nRF24L01+

Håkon Alseth — Fri, 07 Jun 2024 12:12:58 GMT

Hi,

Thank you for sharing this debug information.

You're receiving a .length of 0x20 (32) on the nRF5-side, while the nRF24L series code seems to send 18 bytes?

Is the content of the received payload correct?

Have you tried dumping the register state of the nRF24L01+ side to see if everything is set as per wanted behavior?

Kind regards,

Håkon

RE: nRF52833 cannot reply to the ack automatically after it receives a packet from the nRF24L01+

JackLan — Fri, 07 Jun 2024 02:00:29 GMT

Hi Håkon,

Thanks for your help.

The following image shows the data of the full struct.

RE: nRF52833 cannot reply to the ack automatically after it receives a packet from the nRF24L01+

Håkon Alseth — Thu, 06 Jun 2024 13:03:07 GMT

Hi,

On the nRF52-side, when receiving a payload and the event NRF_ESB_EVENT_RX_RECEIVED, can you check the rx_payload struct (the full struct, not just the payload content) content and share it here?

Kind regards,

Håkon