RE: Proprietary 2.4G low latency

Edvin — Tue, 23 Mar 2021 14:46:48 GMT

Hello,

All of these things are a tradeoff. A throughput of 50kbps is not much, but it is significant. In addition, it really depends on the number of peripheral connections, and the latency that you need on the proprietary 2.4GHz.

We do not have any examples doing all this, but if you want to send custom data to multiple connections, I would start by looking into the ble_app_multilink_central, and exchange the lbs service with the uart_central service. After this, you need to add the TimeSlot API to work with proprietary protocol, and you also need to add advertising and 1 connection as a peripheral (where the nRF is the central).

Please note that when you have many connections like this, and also do scanning, you may experience some latency because the nRF can't handle all the connections every connection interval. There are quite a lot of threads on this topic on DevZone. Ideally, you want to have many connections, decent throughput, low latency. But these are tradeoffs. Depending on the number of connections and the connection event length, you will get more or less time (timeslots) to do your proprietary radio protocol.

Best regards,

Edvin

RE: Proprietary 2.4G low latency

awneil — Tue, 23 Mar 2021 10:04:14 GMT

[quote userid="55636" url="~/f/nordic-q-a/73135/proprietary-2-4g-low-latency"]they want the latency can be as small as possible[/quote]

Can you put some numbers on that - how low is "low" ?