SDK15 long advertising and long range connect

RE: SDK15 long advertising and long range connect

Vidar Berg — Fri, 31 Aug 2018 12:44:10 GMT

Hello,

I think there must be a different problem. I tried to run the attached projects with v.6.1.0 and it worked. Have you made any other changes apart from changing to the latest softdevice version?

RE: SDK15 long advertising and long range connect

l.r.97 — Fri, 31 Aug 2018 08:09:12 GMT

Hello Vidar Beg,

I downloaded the example and flashed it on two SDK boards. The example is working properly.

In the second step, I provided the Central with the new 6.1.0 stack. The connection to the peripheral is still possible.

Then I also wanted to adjust the stack for the peripheral. The project can also be compiled and flashed.

The peripheral also starts advertising.

However, no connection is established to the central, where is the problem?

Many Thanks

RE: SDK15 long advertising and long range connect

Vidar Berg — Fri, 17 Aug 2018 13:43:05 GMT

Hello Tina,

1. It will use code phy if the advertisement is done with code phy

2. sd_ble_gap_phy_update() can be used to change the PHY once connected. What PHY use to advertise is configured in advertising init (1M or coded)

3. You will not get a BLE_GAP_EVT_PHY_UPDATE_REQUEST unless the peer request a phy change

4. Sorry I'm not sure I understand the question, could you elaborate?

RE: SDK15 long advertising and long range connect

helen — Thu, 16 Aug 2018 03:27:23 GMT

Hello Vidor Berg,

Thanks for your reply, and I still have doubts.

1.Central how to know the send connect request used PHY CODED or 1Mbps or 2Mbps ?(whether is same to advertising?)

2. If I have no request the connected used sd_ble_gap_phy_update(), which is the connect physical channel?(1Mbps 2Mbps 125kbps or related connect request)

3. I see the docment and test , according to document connected and will enter event BLE_GAP_EVT_PHY_UPDATE_REQUEST, but test result is central and peripheral has not enter this case event. Only I call the sd_ble_gap_phy_update() in BLE_GAP_EVT_CONNECTED, and wiil enter BLE_GAP_EVT_PHY_UPDATE event, Why ?

4.Softdevice is default support three physical channel and have not params to set support which one?

Best Regards,

Tina

RE: SDK15 long advertising and long range connect

Vidar Berg — Mon, 13 Aug 2018 11:48:41 GMT

Hello Tina,

You can establish the connection with code phy if both sides support it. Attached a modified version of the UART client and peripheral example that do this.

1. See modifications I made in UART example:

devzone.nordicsemi.com/.../enable_5F00_ext_5F00_adv_5F00_coded_5F00_phy.diff

2. Central will connect with coded PHY

3. Softdevice configures the radio at the beginning of radio events, and resets it when the event is finished. Thus, it's hard to read the radio registers when debugging as you need to halt the CPU while the radio is being used.

4. It depends on GAP role. Please have a look the message sequence charts here: http://infocenter.nordicsemi.com/topic/com.nordic.infocenter.s140.api.v6.0.0/group___b_l_e___g_a_p___e_v_t___p_h_y___m_s_c.html?cp=2_3_2_1_0_2_1_3_7

5. Max. adv. length should be 255 with advertisement extension.

devzone.nordicsemi.com/.../ble_5F00_app_5F00_uart_5F00_c_5F00_lr.zip devzone.nordicsemi.com/.../ble_5F00_app_5F00_uart_5F00_lr.zip

Note: S140 v.6.1.0 has qualified support for LE Advertising Extensions and Long range and replaces s140 6.0.0 distributed with SDK 15.0.0