Wrong data received for BLE char

RE: Wrong data received for BLE char

Sigurd — Tue, 15 Oct 2024 22:49:43 GMT

Looks like the slave just stopped replying.

Do you have any nrf_logs? Did the device reset? Could be that an error was passed to APP_ERROR_CHECK() the default behavior is then to reset.

RE: Wrong data received for BLE char

DanisXZ — Tue, 15 Oct 2024 22:21:53 GMT

Sigurd Thank you for looking into this. I am using google pixel-6 phone. I am not sure why it does use BT instead of BLE.

However I used nrf52DK on the central side and again captured the data. I am attaching both the working and non-working logs.
devzone.nordicsemi.com/.../Not-working-example.pcapng

devzone.nordicsemi.com/.../Working-Example.pcapng

I see from the logs that the client is sending the full data. It looks like it is not receiving the data on the receiver side. Can you please have a look into the sniffer logs ?

RE: Wrong data received for BLE char

Sigurd — Tue, 15 Oct 2024 21:14:17 GMT

Hi!

That was a strange sniffer trace,

Looks like the phone is sending a MCAP packet. This packet is associated with Bluetooth Classic, and not Bluetooth Low Energy.

What phone brand and model is used ? Could you try a different phone?

RE: Wrong data received for BLE char

DanisXZ — Mon, 14 Oct 2024 20:39:22 GMT

devzone.nordicsemi.com/.../write-char-issue.pcapng

Sigurd Thank you for your reply.

I see from row 184 (from the sniffer) that the entire data is not sent. This time I used nrf connect app from my android phone to check if it is something to do with my central+client device. But it looks like the behaviour is same from the android app also. See the snapshot from the android app .

RE: Wrong data received for BLE char

Sigurd — Mon, 14 Oct 2024 12:29:14 GMT

Hi! Could you capture a sniffer trace of the behavior ?

https://www.nordicsemi.com/Products/Development-tools/nRF-Sniffer-for-Bluetooth-LE