BLE UART on SDK15.3. Long Range connection problem

RE: BLE UART on SDK15.3. Long Range connection problem

AndreasF — Wed, 07 Aug 2019 12:34:58 GMT

Hi.

Great to hear :-)

Best regards,

Andreas

RE: BLE UART on SDK15.3. Long Range connection problem

tparkkila — Wed, 07 Aug 2019 12:06:18 GMT

Andreas - The modified ble_uart applications (as posted above) works with our custom boards as well. Therefore, the issue was with the dev kits hardware.

Thank you for your help!

RE: BLE UART on SDK15.3. Long Range connection problem

tparkkila — Wed, 07 Aug 2019 11:41:58 GMT

Andreas - I got the example to work on our custom boards, which both have nRF52840 chip version: QIAAC0-1815AM.

Next, I will test the uart example code, which I modified and posted here originally.

RE: BLE UART on SDK15.3. Long Range connection problem

tparkkila — Wed, 07 Aug 2019 11:10:25 GMT

Not sure where to find the matching version number referred on the page you linked. I can find the following labels/numbers on devkits:

- on Atmel cpu: PCA10056, V0.9.2, 2017.33, 683964418

- on nRF52840 chip: N52840 QIAAAA 1716AK

RE: BLE UART on SDK15.3. Long Range connection problem

AndreasF — Wed, 07 Aug 2019 09:08:43 GMT

Hi.

What versions are your DK's?

There is an errata for Engineering B which causes poor communication link, ref.

Best regards,

Andreas

RE: BLE UART on SDK15.3. Long Range connection problem

tparkkila — Tue, 06 Aug 2019 15:48:26 GMT

Hi Andreas - I tested the project you gave and get the similar results. Client is seen and connected but then immediately disconnected. See the debug logs below from peripheral project:

 app: Debug logging for UART over RTT started.

 nrf_ble_gatt: Requesting to update ATT MTU to 247 bytes on connection 0x0.

 app: Connected

 app: Disconnected

RE: BLE UART on SDK15.3. Long Range connection problem

tparkkila — Tue, 06 Aug 2019 12:26:06 GMT

Hi Andreas, no I haven't try this one. Even though it says its using SDK 15.3, I see the example is not using the same software architecture as SDK 15.3 uart examples. As for example on peripheral code in advertising_start function the SDK example uses function call:

- uint32_t err_code = ble_advertising_start(&m_advertising, BLE_ADV_MODE_FAST), whereas

- err_code = sd_ble_gap_adv_start(m_adv_handle, APP_BLE_CONN_CFG_TAG) function call is used by the github example you referred.

I know by looking at the source code of the stack that ble_advertising_start() function in ble_advertising.c file calls sd_ble_gap_adv_start() function eventually. Is there a way to configure settings in a such a way that the new SDK architecture can be utilized as it for Long Range comms?

I will try this project later today.

Thanks!

RE: BLE UART on SDK15.3. Long Range connection problem

AndreasF — Tue, 06 Aug 2019 09:24:01 GMT

Hi Tommi.

Have you had a look at this example on GitHub?

Best regards,

Andreas

RE: BLE UART on SDK15.3. Long Range connection problem

tparkkila — Mon, 05 Aug 2019 13:19:33 GMT

One more thing:

Forgot to mention, that if I undefine BLE_LONG_RANGE(line 658 on ble_uart_peripheral_main.c, and line 101 on ble_uart_central_main.c) - pre-compilation flags everything works normally, advertisements are seen and connections are established normally.

Thanks