Disconnected: 0 BLEHci.remote_user_terminated_connection [using pc_ble_driver_py]

Disconnected: 0 BLEHci.remote_user_terminated_connectio

This means that  sd_ble_gap_disconnect() was called on the peer, with the reason BLE_HCI_REMOTE_USER_TERMINATED_CONNECTION. If you can debug your peer you should be able to find where this is called.

Kenneth

Hello,

I edited the function connect() and I added a tag = 1 = CFG_TAG (the macro in the line number 33), I don't have anymore the problem BLEHci.remote_user_terminated_connection neither the errors.

However, after like 250~253 secondes the connection will stop and I receive the message below :

---> Disconnected: 0 BLEHci.conn_interval_unacceptable

Does anyone have any solution?

Thanks in advance.

Joe

Please try to make the pcapng file work. Maybe check that you stop sniffing before saving, try a restart of PC and wireshark etc.

Kenneth

Hello Kenneth,

I tried to solve the crash problem by installing wireshark on different PCs and I followed step by step as it mentionned in this link https://infocenter.nordicsemi.com/pdf/nRF_Sniffer_BLE_UG_v3.2.pdfhttps://infocenter.nordicsemi.com/pdf/nRF_Sniffer_BLE_UG_v3.2.pdf .

But everytime I want to save log,  wireshark crash, I  have seen that this is a bug 14631 with Qt and there is no update since 4 years to this: https://devzone.nordicsemi.com/f/nordic-q-a/15429/nrf-sniffer-crash-can-be-fixedhttps://devzone.nordicsemi.com/f/nordic-q-a/15429/nrf-sniffer-crash-can-be-fixed .

when I try to click on file save, the buttons are not enabled and when I click on the red stop icon wireshark crash and exit the app.

Could you perhaps try to use my python code and sniff if your sniffer works well.

Hello Kenneth,

I finally succeeded to get a pcapng file. In the line number 2838, you will find that I am able to connect to the blinky dongle. after that I am able to send ON/OFF and receive the state of the led every 3 secondes. and after like 200 secondes, the blinky dongle will disconnect and the python script will show me "Disconnected: 0 BLEHci.conn_interval_unacceptable" and at the line number 17172 in pcapng file you will see "control opcode: LL_TERMINATE_IND".

Thanks

I really suspect the real problem here are the unhandled connection parameter update requests:

Can you look into this reply:
https://devzone.nordicsemi.com/f/nordic-q-a/73685/modify-pc-ble-driver-example-for-nordic-uart-service/303474#303474

Kenneth

Hello,

We are going to investigate in that again, but you think they might be some unhandled connection parameter update requests in your example code (from SDK ble_blinky_app )?

And since it is working correctly with your nRF connect application, is there a specific reason we missed that makes you not suspect the python librairy pc-ble-driver-py?

I will share a pcapng file using nrfconnect and I have the same info: "Connection Parameter Update Request" at line 8482.

Thanks

Hello,

We are going to investigate in that again, but you think they might be some unhandled connection parameter update requests in your example code (from SDK ble_blinky_app )?

And since it is working correctly with your nRF connect application, is there a specific reason we missed that makes you not suspect the python librairy pc-ble-driver-py?

I will share a pcapng file using nrfconnect and I have the same info: "Connection Parameter Update Request" at line 8482.

Thanks

I can see the nrf connect app reply with an connection parameter update response:

So is is the handling of the request that is missing here.

Kenneth

Hello,

yes indeed, I saw this too. Therefore, could you please tell us wich function schould we use according to the python script in the attachments so I could handle the request.

Thanks

I am not able to look into the details here, but I do believe that the answer I linked here show the steps you need to perform:

https://devzone.nordicsemi.com/f/nordic-q-a/73685/modify-pc-ble-driver-example-for-nordic-uart-service/303474#303474