Client periodic package break-in

RE: Client periodic package break-in

run_ar — Mon, 27 Apr 2020 14:07:29 GMT

ok, I'll wait for your input.

RE: Client periodic package break-in

stackGreen — Mon, 27 Apr 2020 09:13:33 GMT

No I don't have a sniffer trace of the BLE communication. I'll get back to you as soon as I've made a recording.

Thank you.

RE: Client periodic package break-in

run_ar — Mon, 27 Apr 2020 08:57:17 GMT

On the server side you would get errors if you ran out of buffers.

On the client side the SD would start Nacking packets if the receive buffers was filled. I.e. if the application is not able to read the fast enough. Are you sure the data is actually sent from the server? Have you tried logging this or maybe capture a sniffer trace of the BLE communication to see if the data is actually transmitted? that should at least let us know which side to start debugging on.

RE: Client periodic package break-in

stackGreen — Mon, 27 Apr 2020 07:59:32 GMT

Hi,

the image shows the buffer level on the client side (yes the buffer is filled with sensor data).

The sensor data is read via spi using ppi and easyDMA.

No I have no such slow periodic (1s) operations running on the server side.

I could not detect any break-ins on the server side. At least the data is passed with 80Hz to sd_ble_gatts_hvx without error code.

The Ble connection interval is set to 10ms.

My guess is that the softdevice on the client side is holding back the data for some reason. Are you familiar with anything like this?

RE: Client periodic package break-in

run_ar — Fri, 24 Apr 2020 11:12:57 GMT

Hi,

Can you explain what is shown on the picture? is this the sensor data?

Assuming this is sensor data: How do you read sensor data on the device? do you have any periodic events on the server that could block the sensor data from being read? What is the BLE connection interval?