Dual peripheral feature?

RE: Dual peripheral feature?

Petter Myhre — Thu, 06 Apr 2017 13:21:49 GMT

0x7 is NRF_ERROR_INVALID_PARAM - Invalid Client RX MTU size supplied, see documentation above sd_ble_gattc_exchange_mtu_request(). I see that you call sd_ble_gap_adv_start(&adv_params, 0), with conn_cfg_tag = 0? I think you need to use the tag you used in ble_stack_init(). So it should be something like sd_ble_gap_adv_start(&adv_params, CONN_CFG_TAG)

RE: Dual peripheral feature?

rct42 — Wed, 05 Apr 2017 21:27:54 GMT

Petter, if you would be able to look into this it would be much appreciated! What I've found so far is that the dual peripheral example does not handle the ATT MTU requests (compared to the ble_app_uart example). I've modified your example a little bit, and here's the modified project. In order to run this example, unzip the v13.0.0 SDK (nRF5_SDK_13.0.0_04a0bfd.zip), create a folder called "test" under examples/, then put the "multi_uart" project in this "test" folder. I have also captured the RTT messages between the "ble_app_uart"/"ble_app_uart_c" and "multi_uart"/"ble_app_uart_c" in a file called "multi_uart_debug.txt". The current issue on the "multi_uart" is "sd_ble_gattc_exchange_mtu_request() returned unexpected value 0x7". Suggestions?

RE: Dual peripheral feature?

Petter Myhre — Wed, 05 Apr 2017 15:15:22 GMT

Sorry for the delayed reply. I don't remember what I tested this with, but I don't think I used ble_app_uart_c. Is this still an issue? Let me know, and I'll look into it.

RE: Dual peripheral feature?

rct42 — Tue, 28 Mar 2017 03:07:26 GMT

Petter,

Firstly thanks for the example. I'm aware that it is not an official release and hasn't been fully tested. Having said that, could you please confirm that the dual peripheral example was tested with the "ble_central\ble_app_uart_c" example in the v13.0.0 SDK? I can confirm that I'm able to get the system working with the Nordic UART v2.0 Android app, but for me the ble_app_uart_c never is able to connect to the "Nordic UART Service". Meanwhile, if I use the "ble_peripheral/ble_app_uart" in place of the dual peripheral example, I am able to get both the ble_app_uart_c and the Android app connecting and sending/receiving data from it.

RE: Dual peripheral feature?

Petter Myhre — Thu, 23 Mar 2017 14:01:32 GMT

This explaines how to handle this error.

RE: Dual peripheral feature?

rct42 — Thu, 23 Mar 2017 04:21:46 GMT

I'm also evaluating this example project and have made some slight modifications (running on a PCA10056, extended to N-peripherals, echo out the RX data to all connected peripherals). However, I get an error of 0x3401 (BLE_ERROR_GATTS_SYS_ATTR_MISSING) when the call is made to sd_ble_gatts_hvx. Is this error on the peripheral side (firmware), or on the central side (NRF UART v2.0), or both? Note that this occurs when when I have two NRF UART v2.0 central devices connected. It is able to echo back the data to a single NRF UART v2.0 central. I have yet to try three central devices.

RE: Dual peripheral feature?

Petter Myhre — Tue, 28 Feb 2017 13:01:13 GMT

Sorry if I was unclear, the feature will definately make it :)

RE: Dual peripheral feature?

Harm — Tue, 28 Feb 2017 12:50:04 GMT

Good to hear, I was afraid that this feature would not make it to a stable version. I'll use S132 4.0.0-2.alpha for now.

RE: Dual peripheral feature?

Petter Myhre — Tue, 28 Feb 2017 12:47:01 GMT

It is possible with the nRF52, currently with S132 4.0.0-2.alpha, and with S132 4.0.0 and S132 5.0.0 when they are released.

RE: Dual peripheral feature?

Harm — Tue, 28 Feb 2017 12:09:19 GMT

That's unfortunate. I am seeking a solution where all my nRF52 devices can do the following simultaneously: 1. peripheral role and being connected to a central (e.g. phone/laptop with Web Bluetooth API ) 2. connect to one of the other nRF52 wirelessly. I see there is are ble_central_and_peripheral examples which I could use for one nRF52, the other nRF52 would then need to act as 2 peripherals. Is this possible with the nRF52? Texas Instruments supports multi-role...

RE: Dual peripheral feature?

Petter Myhre — Tue, 28 Feb 2017 09:56:11 GMT

This feature is not supported by S132 5.0.0-1.alpha.

RE: Dual peripheral feature?

Harm — Tue, 28 Feb 2017 09:47:30 GMT

Do you have an example for the nRF52832 13.0.0-1.alpha SDK and softdevice 5.0.0-1.alpha? This example does not compile in that environment with armgcc.

RE: Dual peripheral feature?

Petter Myhre — Sat, 07 Jan 2017 15:58:17 GMT

Actually S132 4.0.0-2.alpha is not compatible with SDK 12.2.0 or SDK 13.0.0-1.alpha, but I made a minimalistic example that demonstrates the dual peripheral feature.

I used ble_app_uart as a starting point, but I modified it so that two centrals can connect. Then if one client writes into the UART RX characteristic, the data will be notified to the other client, and vice versa.

I added some logging to make it easy to see the reason, if anything is not working, for example that you haven’t connected two centrals, that you haven’t set the CCCDs to be able to receive notifications, and so on. So I recommend using a terminal on the PC.

Please add a comment if you have trouble getting it to work.

The example is not an official release, and is only tested with Keil and PCA10040, and this testing was very superficial.