NRF24L01+ working irregulary

[Fred Lamer]

Hi everyone,

I bought two NRF24L01+ off ebay a couple of week ago and started to work on them this week. I seem to have problem with establishing a reliable communication between both devices. I enabled Shockburst by setting register EN_AA all to "1" and register EN_RXADDR all to "1". I should then have auto-acknowledgement on the TX device. Both device work with the IRQ pin with external interrupt on my two MCU (ATMEGA8) and interrupt are masked with the STATUS register to show what interrupt is trigerred by the NRF. I seem to have a bad communication, but the packet still cross from the TX to the RX irregularly. I checked the value of the received packet and it is the same as the one sent., but no acknowledge received in the TX device...

Any fast thoughts on why it would do this?

Thanks, Fred

[Ivo Milev]

Hi Hakon,

I think you misunderstand my problem. In my case, at one moment the PRX acts as "PTX" and the "PTX3" device acts as PRX. This is the way to do bidirectional communication and not only one way ( i.e PTX3 to send to PRX ).

And I will repeat - If I communicate with PTX6 ( which is on PIPE0) I succesfully observe TX_DS interrupt Could you please explain why it is happen , why only on PIPE0 I am observing TX_DS

On all other PIPES the data is recieved successfully but no ACK is returned ( TX_DS not asserted) and MAX_RT is asserted instead of that - i.e. exactly as Fred's issue. I am sending all data bytes in the payload ( which was the Fred's issue) so that is not my issue.

I added diagram for better understanding of my case

Best Regards, Ivo Milev

nrf24L01.pdf

[Håkon Alseth]

I am sorry for misunderstanding your application. The PRX seems to act as a "PTX" in your attached diagram.

What you should then do is to use PIPE0 instead of PIPE1 on the device labeled "PRX", as it is now configured as a PTX device.

Every device that is configured to be a PTX device (ie: has PRIM_RX in CONFIG register set to '0') must have TX_ADDR and PIPE0 address set equal for the hardware ACKing to work.

Best regards Håkon