Nature of pseudo-random delay advDelay (0-10 ms) added to the advertising interval

RE: Nature of pseudo-random delay advDelay (0-10 ms) added to the advertising interval

Sukriti — Fri, 11 Mar 2022 12:35:03 GMT

Alright, thanks Susheel! :)

RE: Nature of pseudo-random delay advDelay (0-10 ms) added to the advertising interval

Susheel Nuguru — Fri, 11 Mar 2022 12:32:21 GMT

Hi Sukrit,

It is not possible to model the adv Delay as the random seed is generated in the hardware based on many conditions that are not possible to model in firmware. Including many states within the MCU/Temperature and other factors which we cannot give details on.

RE: Nature of pseudo-random delay advDelay (0-10 ms) added to the advertising interval

Sukriti — Fri, 11 Mar 2022 11:32:08 GMT

Hi Susheel, thanks for the response. We are actually trying to advertise sensor data from multiple nodes with maximum collision avoidance. We were trying to achieve this by changing the time at which each node begins sending out advert packets. But since there already is an inherent random delay added to the advertising interval, we got stuck here because we would have to consider the nature of this delay as well. It would become a lot easier if we could model this delay mathematically.

Just for a bit more clarity, our application does not require the nodes to advertise continuously. An end node logs sensor data, advertises the logged data for a few seconds, goes to sleep for the next few minutes, again wakes up and logs the sensor data. The cycle repeats. This is done at each end node.

I tried to give you an outline of what we're trying to achieve. Hope it's not very vague..

Regards,

Sukriti

RE: Nature of pseudo-random delay advDelay (0-10 ms) added to the advertising interval

Susheel Nuguru — Fri, 11 Mar 2022 11:25:24 GMT

Hi Gautam,

The random number is achieved by the random number pool we maintain dynamically in the link layer which is created from NRF_RNG peripheral. The exact details of it can be implementation dependent as the application or peer does not need to know anything about the delay apart from spec saying that it should be within 10ms. Just out of curiosity, why do you need the implementation details of this delay?