Timing in ESB TX nRF52840

RE: Timing in ESB TX nRF52840

Sigurd — Mon, 25 Sep 2023 12:01:38 GMT

[quote user="MinhDuc"]So for one round-trip communication, the bytes on-air is 264 bytes. Am I right? [/quote]

Sounds a bit high with 12 bytes for address, crc, etc. Take a look at this link if you are using nRF5-SDK: https://infocenter.nordicsemi.com/topic/sdk_nrf5_v17.1.0/esb_users_guide.html?cp=9_1_5_3_6#esb_addressing

or this if you are using nRF Connect SDK: https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/protocols/esb/index.html#pipes-and-addressing

You might also find this post here helpful: Speeding up ESB on nrf52

RE: Timing in ESB TX nRF52840

MinhDuc — Sat, 23 Sep 2023 07:56:28 GMT

I make a calculation:

tx packet:

address, crc, etc. - 12 bytes

payload 240 bytes

rx ack packet:

address, crc, etc. - 12 bytes

payload 0 bytes

So for one round-trip communication, the bytes on-air is 264 bytes. Am I right?

So the best payload data rate I can get is around 1.8Mbps in 2Mbps bitrate?

Please correct me if I misunderstood some point.

Bests,

RE: Timing in ESB TX nRF52840

MinhDuc — Sat, 23 Sep 2023 07:50:00 GMT

Thank you Sigurd.

I got the concept of ACK.

Now I am using the ESB driver. Is it faster if I work directly with the register like HAL?

Regards,

RE: Timing in ESB TX nRF52840

Sigurd — Fri, 22 Sep 2023 14:34:00 GMT

Hi!

nrf_esb_write_payload() returns NRF_SUCCESS if the payload was successfully queued for writing. When an ACK is successfully received from a PRX, the PTX assumes that the payload was successfully received and added to the PRX's RX FIFO. The successfully transmitted packet is removed from the TX FIFO, so that the next packet in the FIFO can be transmitted.

Assuming that you are waiting for ACK now, then disabling ACK's will allow you to increase the data rate significantly. But this is not a good choice if you need a reliable stream of data.