Ble automation on linux

RE: Ble automation on linux

Karl Ylvisaker — Thu, 27 Aug 2020 08:44:13 GMT

Hello,

[quote user="abunai"]Sorry, I just noticed your response. I guess I didn't turn on reply notification.[/quote]

No problem at all.

[quote user="abunai"]Anyways, it is a custom module. I am attaching a log that I got from nrfConnect for Desktop which I used nRF52840 USB Dongle to scan my BLE device. I got basically the same result[/quote]

Thank you for including the log.
It seems indeed that your remote device terminates the connection.
Furthermore, it seems in your log that you are attempting to read some characteristics with different handles, and you keep requesting handle 15, but there does not exist any such characteristic.
The log message associated with this is : "Cannot handle HVX event. No characteristic value with handle 15 found."
And this happens repeatedly before the remote user disconnects.

Could you check what your program is attempting and failing to read here? And, what your custom module is programmed to do when receiving repeated invalid requests?

Best regards,
Karl

RE: Ble automation on linux

abunai — Wed, 26 Aug 2020 21:14:42 GMT

Hi,

Sorry, I just noticed your response. I guess I didn't turn on reply notification.

Anyways, it is a custom module. I am attaching a log that I got from nrfConnect for Desktop which I used nRF52840 USB Dongle to scan my BLE device. I got basically the same result

2020-08-26T19:53:09.879Z DEBUG GAP_EVT_DISCONNECTED time:2020-08-26T19:53:09.877Z connHandle:0 reason:19 reasonName:remoteUserTerminatedConnection
2020-08-26T19:53:09.881Z INFO Disconnected from device XX:XX:XX:XX:XX:XX, reason: BLE_HCI_REMOTE_USER_TERMINATED_CONNECTION

Thanks,

Anh

devzone.nordicsemi.com/.../2020_2D00_08_2D00_26T18_5F00_34_5F00_35.615Z_2D00_log.txt

RE: Ble automation on linux

Karl Ylvisaker — Fri, 14 Aug 2020 08:17:59 GMT

Hello,

I am not familiar with the Bluez stack, but from your btmon HCI event it seems that the connection is terminated by the remote user, i.e your nRF52 device. What program is your nRF52 device running? Could it be that it terminates the connection because of a non-compatible connection configuration with the central device?
What kind of device is the nRF52 device, are you working with a nRF52 development kit or a custom module?

Looking forward to resolving this issue together!

Best regards,
Karl