About esb_ptx_ble & esb_prx_ble.

[Leo Mo]

Can I copy the ESB code from SDK v3.3.0-preview3 into SDK v2.9.0, and then get the functionality in esb_ptx_ble & esb_prx_ble?

 

Is there any way to achieve it quickly?

[Leo Mo]

It is in a BLE connection.

CONFIG_CONN_INTERVAL_MIN=990  //ms

CONFIG_CONN_INTERVAL_MAX=1010

CONFIG_CONN_LATENCY=6

[Kenneth]

I don't have any good reason why this occurs no. 

What you can try is to measure the current consumption using a Nordic PPK2, and also toggle some gpios in your application (one pin when OK, and one pin when fail), for instance when you are actively in ESB RX mode, and check if you can see based on the current consumption if it may be that the application is doing something else at the same time as you should be receiving based on the current consumption when you fail to receive. The Nordic PPK2 can measure current and monitor up to 8 digital pins at the same time.

Kenneth

[Leo Mo]

Hi,

Thank you very much！
Is it possible that this is caused by the cumulative error of the low-speed crystal oscillator (20ppm)?

Leo Mo

[Kenneth]

Hi Leo,

I assume you have some algorithm that adjust wakeup interval to ensure that the expected packet is received in the middle of the wakeup period. But if the wakeup window is 15ms, I would expect you should always be able to receive a packet that is transmitted every 5-10ms even without any adjustment to the wakeup interval.

Kenneth

[Leo Mo]

Hi Kenneth,

Now the RX interval is fixed at 7.3 seconds and the RX window is 15 milliseconds. In theory, there are 4 chances to receive data in 30 seconds, but now the phenomenon is that some devices cannot receive data for tens of minutes in a row, which is very strange. I am adding debugging IO to monitor where problems occur.

Leo Mo