How to implement "Fast advertising" with SDK 14.10

[Louis Wnag]

Hi All

I'd like to implement "Fast advertising" with SDK14.10

Q1: I add some code in advertising_data_set() to do fast advertising, is that correct ?

Q2: If  want to test current consumption under different  conditions (in red box) these conditions is work for test ?

thank's 

Louis

[Einar Thorsrud]

Hi,

Q1: I add some code in advertising_data_set() to do fast advertising, is that correct ?

This looks OK. But note that the advertising mode configuration is also provided when you initialize the advertising module, so there is no point in calling ble_advertising_modes_config_set() unless you want to change the configuration since you called ble_advertising_init().

Q2: If  want to test current consumption under different  conditions (in red box) these conditions is work for test ?

You have highlighted the different security modes. In this case, you only change the security configuration for the name. But, if this applies to all used characteristics, then generally pairing will not be done if set to Open, and will be done iff set otherwise. The method of pairing (LESC or not or MITM or not) also depends on other factors, but the characteristics. In any case, this does not have a significant impact on current consumption if most cases.  Using encryption or not does not have a big impact, and the different pairing procedures also have a small impact on average current consumption, since pairing is typically not done often (perhaps only once).

[Louis Wnag]

Hi Einar Thorsrud

Thank's your response.

About Q1 I can not fully understand what you mean.

If I change my code. May I need to calle ble_advertising_init() ?

And 

How to verify for "Fast Advertising" ?

Thank you ?

[Einar Thorsrud]

Louis Wnag said:

May I need to calle ble_advertising_init() ?

Yes, that has to be called anyway since you use the advertising module. What does the rest of y our code look like? And does it work?

Louis Wnag said:

How to verify for "Fast Advertising" ?

Fast and slow advertising is just an SDK concept. You can verify that you get the expected advertising interval using a BLE sniffer.

[Louis Wnag]

Hi Einar 

Thank you.

Q1:

About Fast/Slow Advertising. Is it just a convenient feature ?   Is it not a Bluetooth spec feature ? 

Fast and Slow Advertising just define different advertising interval ?

#define APP_ADV_FAST_INTERVAL           0x0028      

#define APP_ADV_SLOW_INTERVAL           0x0C80    

In other words, I can reverse the defined values.

#define APP_ADV_FAST_INTERVAL           0x0C80      

#define APP_ADV_SLOW_INTERVAL           0x0028    

Q2: I want to understand the relevant knowledge first and then ask questions if there are any questions.

[Einar Thorsrud]

Hi,

Louis Wnag said:

About Fast/Slow Advertising. Is it just a convenient feature ?   Is it not a Bluetooth spec feature ? 

Yes. It is an SDK concept, not a Bluetooth spec feature. The Bluetooth specification does limit advertising intervals for certain advertising types (see for instance this post), but that is not related to fast/slow advertising. The reason for having fast/slow advertising is that typically you want fast advertising first to allow a central to connect fast when it is most likely to connect. After that, you typically want slower advertising in order to save power.

Louis Wnag said:

In other words, I can reverse the defined values.

Yes (though I don't see any use cases where that would make sense).