SERIOUS QUALITY PRODUCT DEVICE

[Alessio]

Hi,

i'm the manager of brand "Promethos" and i write you about that concern the case ID 247688.
In your last reply you have suggest :for the USB port I used many of them, directy into USB3 on PC, with USB2 1,5m extension cord, in an USB2 hub but with a not appreciable difference
is not reasonable to use a cord, the device must work perfectly connected directly to the port;
we have already try to use the device connected to USB3 and USB2.1 port without difference;;
we use in our SW the standard registers (we have sent to your team our source code) ;
we've been experimenting for two weeks (without changing SW) because communication stops at less than 1mt, in mode one to one and mode one to two;

For me is very expensive to lose the time of my collaborator to check radio instead to write SW and develop the application.
It's URGENT that NS solve the radio problems in NS device we are using!
If is necessary to use different versions is not a problem, but i need to receive a full exsaustive solution.

Thanks

[Turbo J]

This question has serious quality issues. I cannot understand anything useful for an answer.

Did you use an automatic translation service (and if so, which one)?

[Alessio]

The reason of the main post is that we still have issues in using a nRF24 series transmitter and receiver (as in case ID 247688) where the transmission range is not going over 1 meter.
We tried using different USB ports, USB extension cords, etc. for the USB receiver dongle and using default settings (as suggested by you) but without success (even thow the intended use of the USB dongle is to plug it directly into the PC).
It was said that, instead of focusing on developing the system and the application arround the Nordic chip, we spent lot of time to test radio part (where we were expecting something that just works without wasting time on it).

So the point of question is: are you able to give us a solution for the radio problems on nRF24? Or do we need to move to a newer device (such as nRF52 which still have communication methods other than Bluetooth which doesn't require pairing)? In any case we're waiting for a full exaustive solution that works.

Giovanni Battistin

[Turbo J]

Note: I am NOT A NORDIC EMPLOYEE.

Also you cannot really seach for case numbers here - thus I was not able to find the original post.

Low range is usually an antenna problem - but could be software, too (like off-by-one in channel number).

I see that you are using "modules". If these are soldered on PCBs with ground pour or traces in the antenna area, that would reliably kill the RF performance.

Also check your working environment for metal and other conductive surfaces...

[Alessio]

The title of the original post is "nRF24 transmission range" if this is useful.

We made the tests using the NordicSemiconductor development kit so PCB antennas should be fine. We tried many channel numbers and of course the same number on both TX and RX.
The modules from the development kit are used on a wood made table without metal parts, not close to concrete walls.

Hoping this details the situation better, if you have some tricks for the problem.

Waiting for a reply by Nordic.

[ketiljo]

It doesn't help starting a new case when the there are open issues in the original case. Here's a link to the original case, please continue the discussion there: https://devzone.nordicsemi.com/f/nordic-q-a/60089/nrf24-transmission-range