https://devzone.nordicsemi.com/f/nordic-q-a/47729/different-advertising-initialisationHi I&#39;ve been experimenting with the ble_app_att_mtu_throughput example and have it running between 2 custom boards using PuTTY, but I&#39;m struggling to understand why the advertising is initialised differently to other ble examples (heart rate sensoren-USTelligent Community 13Wed, 29 May 2019 13:45:25 GMThttps://devzone.nordicsemi.com/thread/189908?ContentTypeID=1Wed, 29 May 2019 13:45:25 GMT137ad170-7792-4731-bb38-c0d22fbe4515:761eac43-c3b9-4893-9507-5af861a5203dPete W<p>Thanks for the reply. After spending a few hours digging I managed to figure out that the throughput example is using the softdevice calls directly, so you confirmed what I suspected.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/189280?ContentTypeID=1Mon, 27 May 2019 11:14:22 GMT137ad170-7792-4731-bb38-c0d22fbe4515:3bea3587-ad23-4eaf-99dc-5c76796578a6Kenneth<p>It seems the&nbsp;advertising_init() is different because two different engineers have worked on the two different projects.</p> <p>One project use the&nbsp;ble_advertising module in the nRF5 SDK to setup advertisement, the ble_advertising_init() will call the softdevice specific api calls. The second project use the softdevice api calls directly, for instance&nbsp;sd_ble_gap_adv_set_configure().</p> <p>Both can work, though using the ble_advertising module may make it easier for you:<br /><a href="https://infocenter.nordicsemi.com/topic/com.nordic.infocenter.sdk5.v15.3.0/lib_ble_advertising.html?cp=5_1_3_2_1">https://infocenter.nordicsemi.com/topic/com.nordic.infocenter.sdk5.v15.3.0/lib_ble_advertising.html?cp=5_1_3_2_1</a>&nbsp;</p> <p>Best regards,<br />Kenneth</p><div style="clear:both;"></div>