Why UART still undergoes connection after setting to scannable/non-connectable state

RE: Why UART still undergoes connection after setting to scannable/non-connectable state

Jared — Tue, 18 Aug 2020 08:13:25 GMT

Hi,

Sorry for the late reply, I was Out of Office.

Regarding your question, the parameters set in the advertising_init.c is just initial default parameters used as a starting point. The parameters will be changed accordingly to what is set in the main file when starting the advertisement. Meaning if you want to change the advertisement type then do it before you call the ble_advertising_init() and the change will take effect right before you start advertising.

regards

Jared

RE: Why UART still undergoes connection after setting to scannable/non-connectable state

destiny98 — Fri, 07 Aug 2020 12:34:31 GMT

The debug terminal & Putty terminal just prints something along the line of "UART connected". I think a good verification that it was connected was that I was able to send messages using Putty from peripheral to central, vice versa.

RE: Why UART still undergoes connection after setting to scannable/non-connectable state

Jared — Fri, 07 Aug 2020 07:23:22 GMT

Hi.

[quote user=""]p_advertising->adv_params.properties.type = BLE_GAP_ADV_TYPE_EXTENDED_NONCONNECTABLE_SCANNABLE_UNDIRECTED; //by right this means the advertising packet is advertising but connection does not occur, however despite changing this to a nonconnectable/scannable state, the central and peripheral still connects[/quote]

Strange. Is the Connected event generated in the ble handler? How do you verify that it actually connects?

regards

Jared