nRF24L01 in multiceiver mode

RE: nRF24L01 in multiceiver mode

ovrebekk — Tue, 05 May 2020 09:34:39 GMT

Hi Viorel

I would recommend starting out with a device from the nRF52 family.

Please note that these are all SoC devices, meaning they have their own embedded MCU for running your application, so they need to be programmed in order to do anything useful.

Either you can use the nRF52 as the only MCU in your system (which means you need to port over any code you have running on some other MCU today), or you can use it in tandem with another MCU by communicating over UART, SPI or I2C.

The smallest device in the nRF52 family is the nRF52810, which is probably sufficient if you only need to run ESB communication.

Best regards
Torbjørn

RE: nRF24L01 in multiceiver mode

ves — Mon, 04 May 2020 16:01:55 GMT

One more thing

As i understand you do not recommend nrf24l01+ for new design, but what is your recommendation?

thx again

RE: nRF24L01 in multiceiver mode

ves — Mon, 04 May 2020 15:43:47 GMT

Hi Torbjørn

I changed the pipes name to CHNN0, CHNN1, CHNN2, CHNN2 same result :(

Then i took the addresses in the documentation (nRF24L01+ Product Specification, fig 14) so

on RX side

uint8_t PIPE0_ADDR[5] = {0x78, 0x78, 0x78, 0x78, 0x78};
uint8_t PIPE1_ADDR[5] = {0xB3, 0xB4, 0xB5, 0xB6, 0xF1};
uint8_t PIPE2_ADDR[1] = {0xCD};
uint8_t PIPE3_ADDR[1] = {0xA3};

And on TX side

uint8_t PIPE0_ADDR[5] = {0x78, 0x78, 0x78, 0x78, 0x78};
uint8_t PIPE1_ADDR[5] = {0xB3, 0xB4, 0xB5, 0xB6, 0xF1};
uint8_t PIPE2_ADDR[5] = {0xB3, 0xB4, 0xB5, 0xB6, 0xCD};
uint8_t PIPE3_ADDR[5] = {0xB3, 0xB4, 0xB5, 0xB6, 0xA3};

this time i could communicate over pipe 0 and 1 but no luck with pipe2 or 3

I also tried with a reduced address length to 3B with same result

It looks pipe address has some impact but not clear how

RE: nRF24L01 in multiceiver mode

ovrebekk — Mon, 04 May 2020 12:48:26 GMT

Hi Viorel

First off I have to mention that the nRF24L01 has been deprecated for a long time and we don't recommend this device for new designs. We still sell it so we can support existing products in the market, but the support we can provide is limited.

On to the issue, it is possible that this is address related. In general using an address starting with 0x5 or 0xA is not recommended, as it will make the address an extension of the preamble leading to reduced RF performance.

Could you try to change the first byte of the pipe 0 address to something not starting with 0x5 or 0xA and see if it makes a difference?

Best regards
Torbjørn