beacon advertise interval

[ziv123]

hello Nordic

i am working with nrf52832, sdk 6.0, softdevice s132 v7.0

i read around the forum that i can advertise a beacon packet every 20 ms 

but in the ble_app_beacon example the interval for the advertisement is written to be minimum 100ms ?? so where did that 20 ms go ?

however, since i don't know how to change the data of the message while advertising i put a timer handler that stops the advertise, update the data and start it again.

i put the timer to go every 50 ms and the advertisement interval every 50 ms i put a pin toggle every time i receive a ble from the address i am filtering..

1. the time is not fixed, maybe some messages are lost or maybe not sent, i don't know 

2. the intervals are larger then 50 ms .. more to the 100 ms  when they are sometimes fixed 

can you advice on this matter ?

i need to be sending changeable data in a beacon at list 30 times in one second

best regards

Ziv

[Karl Ylvisaker]

Hello Ziv,

ziv123 said:

i passed ' NRF_RADIO_PRIORITY_NORMAL ' 

ziv123 said:

and it fails

I will need to know which error is generated when a function fail, to be able to help you find the root cause. However, it here seems that you were able to resolve the issue yourself, great!

ziv123 said:

not sure if it works better or how much is a safe distance for a 31 bytes beacon (for now i set it to NRF_RADIO_NOTIFICATION_DISTANCE_3620US ) 

i still only encode the new advdata and nothing else within the handler .. seems ok, hope no surprises later.

As long as you keep the event handler short ( such as just updating the advdata structure ) you should be fine - 3.6 ms is a long time.
However, you should make sure that this update is not postponed due to some other high-priority ( application layer, non-SoftDevice ) event is being generated and processed in the meantime.

ziv123 said:

so a lot of thanks on this long long thread for now

It is not problem at all, Ziv. I am happy to help!

ziv123 said:

my fault, though i guess i am always worried that new threads takes longer time to get replied 

We do not prioritize new tickets over old tickets, no worries. To receive better help faster, it is key to provide all the necessary information immediately, so we quickly get up to speed on the issue and conditions you are facing.

ziv123 said:

we can close this thread i think.. for more questions on this matter or other i will open a new one 

Great! Please do not hesitate to open a new ticket in the future if you should encounter any other issues or questions.
To keep the forums tidy and easy to navigate, it is best to open a new ticket as soon as the questions diverge from the initial ticket.

Good luck with your development, Ziv!

Best regards,
Karl