Dear Dialog,
I have two questions about advertising.
Q1: I'd like to know the time lag between app_adv_start() and actual advertising start timing.
Does advertising starts just after FW executes app_adv_start() or ther are some time lag relating to BLE's advertise_delay
(random value up to 10mS)?
Q2: What happens if FW excutes app_adv_stop() just during the actual advertising is on going? For example, advertising
is stopped in between channel #37 to #38 and no error is reported to FW?
Best Regards,
yukio
Device:
Hi yterasaki,
Q1: Yes there is a random generated time lag (not enabled by default) in order to avoid collision between two simultaniously advertising devices (a random delay is generated from TRNG) because of that we are not able to track the time between the command the actual advertising event.
Q2: We ve never encounterd an incident when during advertising an app_adv_stop to interrupt the advertising procedure and stop advertise while not ended advertising in all channels, and from some tests i performed i dont think that this is possible. Have you encountered such thing and without reporting an error in the FW?
Thanks MT_dialog
Thanks Dialog staff,
Q1: Regarding your comment, please allow me to confirm the meaning of "(not enabled by default)".
Following statement are copied from app.c. This sounds that advDelay is always enabled in the interval setting.
Am I missunderstanding your comment? and if advDeley(0-10mS random) is not enabled by default, please tell
me how to enable it.
/// Advertising minimum interval
#定义APP_ADV_INT_MIN 1100
/// Advertising maximum interval
#定义APP_ADV_INT_MAX 1100
#if (BLE_HID_DEVICE)
#undef APP_ADV_INT_MIN
#定义APP_ADV_INT_MIN 0x20 // *0.625ms (+ pseudo random advDelay from 0 to 10ms)
# undef APP_ADV_INT_MAX
#定义APP_ADV_INT_MAX 0x20 // *0.625ms (+ pseudo random advDelay from 0 to 10ms)
#endif
Q2: So far, I'm dedugging the problem about advertising, but at this moment, there is no phenomenon which is
strongly indicating this situation.
Best Regards,
yukio