This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Consumption after advertising stop

Hello i'm looking at the current consumption with the nrf PPK2 and i'm observing a strange behaviour : 

the nrf advertise for a while then should stop the advertising using the APP_ADV_DURATION 

#define APP_ADV_INTERVAL				MSEC_TO_UNITS(200, UNIT_0_625_MS)		/**< The advertising interval (40 = 40 ms). */
#define APP_ADV_DURATION				2000//BLE_GAP_ADV_TIMEOUT_GENERAL_UNLIMITED	/**< The advertising time-out (in units of seconds/10). When set to 0, we will never time out. */

i can see the end of advertising with the 200ms period : 

But then every 8 s i have a unexpected current consumption : 

When i zoom in it look like this :

Do you have any idea where it can come from ?

I tried removing everything exept the bluetooth and i still observe the same behaviour.

Can it be linked to the BLE ? 

Thank you 

Parents
  • Hello,

    Do you have any idea where it can come from ?

    Could you detail what else your application is doing? Which other peripherals are you using, for example?

    I tried removing everything exept the bluetooth and i still observe the same behaviour.

    Can it be linked to the BLE ? 

    When you say removing everything, do you mean that you disable the SoftDevice completely, or that you remove all code that is not strictly SoftDevice related?
    In case of the former, the SoftDevice will not draw any current when disabled, and we will then have to look into what else might be going on in the application.
    In case of the latter, what parts is still left of the SoftDevice code?
    Is your device only ever advertising, and if so, do you receive the advertising IDLE event at the end of the 2000 ms period?

    i can see the end of advertising with the 200ms period : 

    This does not correspond to the #defined values you share. With a 200 ms interval and 2000 ms duration, you should see ~10 advertisements before finishing the advertising. In your diagram, there are more than 10 advertisements. Could you confirm for me that these defines is what is actually used in the advertising initialization?
    Could it be that you are entering SLOW advertising following the end of the normal advertising?
    It would be helpful if you could share your advertising initialization function.

    Please use the Insert -> Code option when sharing code here on DevZone.

    Looking forward to resolving this issue together!

    Best regards,
    Karl

Reply
  • Hello,

    Do you have any idea where it can come from ?

    Could you detail what else your application is doing? Which other peripherals are you using, for example?

    I tried removing everything exept the bluetooth and i still observe the same behaviour.

    Can it be linked to the BLE ? 

    When you say removing everything, do you mean that you disable the SoftDevice completely, or that you remove all code that is not strictly SoftDevice related?
    In case of the former, the SoftDevice will not draw any current when disabled, and we will then have to look into what else might be going on in the application.
    In case of the latter, what parts is still left of the SoftDevice code?
    Is your device only ever advertising, and if so, do you receive the advertising IDLE event at the end of the 2000 ms period?

    i can see the end of advertising with the 200ms period : 

    This does not correspond to the #defined values you share. With a 200 ms interval and 2000 ms duration, you should see ~10 advertisements before finishing the advertising. In your diagram, there are more than 10 advertisements. Could you confirm for me that these defines is what is actually used in the advertising initialization?
    Could it be that you are entering SLOW advertising following the end of the normal advertising?
    It would be helpful if you could share your advertising initialization function.

    Please use the Insert -> Code option when sharing code here on DevZone.

    Looking forward to resolving this issue together!

    Best regards,
    Karl

Children
No Data
Related