• State Verified Answer
  • Locked Locked
  • Replies 3 replies
  • Subscribers 88 subscribers
  • Views 965 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 280855
Options
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

How to change the advertise status from fast mode to idle mode

Shuto Kimura

Hi,

I am creating a BLE communication device (peripheral) using softdevice S132 (v7.0.1) and SDK 16.0.0 on the nRF52832 microcomputer.

I have implemented the BLE communication function, but sometimes I do not understand it. It is the file and timing to change the advertising from fast mode to idle mode.

The application uses ble_advertising_start () to start advertising and enable fast mode. After that, advertising will stop once the connection is established. However, sd_ble_gap_adv_stop is not executed on the application side. Where and who is stopping advertising (idle mode)?

I referred to the following sequence.
https://infocenter.nordicsemi.com/topic/com.nordic.infocenter.s132.api.v7.0.1/group___b_l_e___g_a_p___a_d_v___m_s_c___l_e_g_a_c_y.html

thank you.

shuto

Parents
  • 0

    Hi Shuto Kimura, 

    I am sorry that our documentation didn't make it clear that when the peripheral get connected it will automatically stopped advertising. This is described in the Bluetooth Spec (v5.2) at section 9.2 Part C Vol 3: 

    So the advertising process is stopped automatically when the connection is established. If you want to continue advertising you would need to start advertising again. You can have a look at the experimental\ble_app_multiperipheral example. 

    The same with when the connection is terminated, the softdevice won't start advertising automatically. You would need to start advertising from the code. In our ble_advertising.c it's handled in on_disconnected() event. 

Reply
  • 0

    Hi Shuto Kimura, 

    I am sorry that our documentation didn't make it clear that when the peripheral get connected it will automatically stopped advertising. This is described in the Bluetooth Spec (v5.2) at section 9.2 Part C Vol 3: 

    So the advertising process is stopped automatically when the connection is established. If you want to continue advertising you would need to start advertising again. You can have a look at the experimental\ble_app_multiperipheral example. 

    The same with when the connection is terminated, the softdevice won't start advertising automatically. You would need to start advertising from the code. In our ble_advertising.c it's handled in on_disconnected() event. 

Children
Related