pc-ble-driver 1.0 bandwidth configuration

RE: pc-ble-driver 1.0 bandwidth configuration

Mike — Wed, 12 Oct 2016 12:46:08 GMT

I'va made a new question for this issue here.

RE: pc-ble-driver 1.0 bandwidth configuration

Hung Bui — Tue, 11 Oct 2016 07:51:51 GMT

@Mike: I would suggest you to create a new question. In your question please include more information on how many peripherals you connected to the central. I assume you set high bandwidth with option API sd_ble_opt_set() before you call the connect request from central.

A sniffer trace can help telling which side caused the low bandwidth.

RE: pc-ble-driver 1.0 bandwidth configuration

Mike — Mon, 10 Oct 2016 13:41:23 GMT

Hi again, setting a bandwidth works but I am still not able to achieve maximum data throughput (128 kbit/s). I am able only to achieve around 16,8 kbit/s which is not enough for my application. Is there any limitation in ble_connectivity firmware which does not allow to achieve maximum data throughput?

I noticed that my peripheral device can't send to me 6 packet per connection every time. Sometimes it is able to send 3 or only 1 packet. The same device has no problem to send 6 packets in every connection with Master Control Panel 3.10 and achieve maximum data throughput.

Could You tell me if it is possible to achieve maximum data throughput with ble_connectivity and pc-ble-driver 1.0 ? If yes, what I have to do?

RE: pc-ble-driver 1.0 bandwidth configuration

Hung Bui — Thu, 06 Oct 2016 08:23:01 GMT

Hi Mike,

Status code 4 means PKT_SEND_ERROR as defined in sd_rpc_app_status_t in sd_rpc_types.h. Error code 3 and 13 match with NRF_ERROR_INTERNAL and NRF_ERROR_TIMEOUT as in nrf_error.h

RE: pc-ble-driver 1.0 bandwidth configuration

Mike — Wed, 05 Oct 2016 13:27:37 GMT

Thank You Hung Bui for help. It seems to be working now. Could tell me also, how to interpret messages from a 'sd_rpc_status_handler_t' (status / error codes)?

RE: pc-ble-driver 1.0 bandwidth configuration

Christian Waldmann — Wed, 05 Oct 2016 12:27:09 GMT

the correct path for the file is: components\serialization\connectivity\codecs\s130\middleware\conn_mw_ble.c

RE: pc-ble-driver 1.0 bandwidth configuration

Christian Waldmann — Wed, 05 Oct 2016 12:09:53 GMT

To use an up to date serialization, one have to use a patch from github and the patch you mention above. And Nordic reports that S130 serialization is deprecated That is not the expected maintenance of the only "active" supported softdevice for the nRF51 family.

RE: pc-ble-driver 1.0 bandwidth configuration

Hung Bui — Wed, 05 Oct 2016 11:29:45 GMT

Hi Mike,

Thanks for reporting the issue. It's actually a bug in the serialization code.

It's fixed in the code in SDK v12.1 but since we don't have serialization code for S130 in SDK v12.1 you would need to do the patch in the code for SDK v11.

So the bug was that we didn't provide the instance for ble_conn_bw_counts_t struct in the param for sd_ble_enable() in the code. You would need to add this two lines

ble_conn_bw_counts_t conn_bw_counts;
params.common_enable_params.p_conn_bw_counts = &conn_bw_counts;

At line 258 in conn_mw_ble.c file in the firmware of \examples\ble_central_and_peripheral\ble_connectivity, right under the declaration of params.

After that you can compile the project and flash the hex file to your dongle.

RE: pc-ble-driver 1.0 bandwidth configuration

Mike — Mon, 03 Oct 2016 12:28:11 GMT

Yes, I compiled my own 'pc_ble_driver_shared.so' (I use Linux) but also tried with library from nRF Connect source files. Effect was the same (I test it also with PCA10040 and desktop).

RE: pc-ble-driver 1.0 bandwidth configuration

Christian Waldmann — Mon, 03 Oct 2016 12:14:55 GMT

Have you compiled the "pc_ble_driver_shared.dll" on your system with the same settings?

When not, you may have some packing/byte mangling problem when using the ble_conn_bw_counts_t struct.

There are two times 3 bytes in ble_conn_bw_count_t for tx_count and rx_count, and a uin16_t in front of this in the enclosing type ble_common_enable_params_t.

I am using the "pc_ble_driver_shared.dll", Versin 1.0.0, from the Python package and a VS2013 C/C++ project to talk to my custom connectivity chip. I can receive advertising telegram, but conneting fails with error 18. May be I have the same problems.

Happy coding Chris