Hello.
After pairing with a tablet or computer, if you leave it for a few seconds without operating it
I wrote out the cause of the disconnection by debugging.
"Error 34 (0x22): GATT CONN LMP TIMEOUT"
What are the possible causes and countermeasures?
Hi,
Which SoftDevice version are you using?
BLE_HCI_STATUS_CODE_LMP_RESPONSE_TIMEOUT (0x22) means that a link layer procedure has timed out (data length negotiation for instance). The timeout is 40 seconds, so the easiest way to find out which procedure it was that timed is to get a sniffer trace and see what happened 40 seconds prior to the disconnect.
It may be caused by several reasons, for instance if the application does not not respond to certain SoftDevice events.
Hello.
Thank you very much for your answer which will be right away.
≫Which SoftDevice version are you using?
S132 is being used.
≫get a sniffer trace and see what happened 40 seconds prior to the disconnect.
After a packet was captured.
"LL_TERMINATE_IND" but a slave showed that he's sent and cuts.
"LL_TERMINATE_IND" but sent timing.
"The one of the ble_conn_params_init_t" "I found out that it's dependent on next_conn_params_update_delay".
Therefore a cut thing died to change "next_conn_params_update_delay" for 24 hours from 5 seconds as a temporary measure.
"Can't the reason that LL_TERMINATE_IND" is sent and the above measure have a proper basket view?
I'll give you trouble and I'm sorry, but please take care.
Hello.
Thank you very much for your answer which will be right away.
≫Which SoftDevice version are you using?
S132 is being used.
≫get a sniffer trace and see what happened 40 seconds prior to the disconnect.
After a packet was captured.
"LL_TERMINATE_IND" but a slave showed that he's sent and cuts.
"LL_TERMINATE_IND" but sent timing.
"The one of the ble_conn_params_init_t" "I found out that it's dependent on next_conn_params_update_delay".
Therefore a cut thing died to change "next_conn_params_update_delay" for 24 hours from 5 seconds as a temporary measure.
"Can't the reason that LL_TERMINATE_IND" is sent and the above measure have a proper basket view?
I'll give you trouble and I'm sorry, but please take care.
Hi,
KURODA ELECTRIC said:S132 is being used.
Can you let mw know which exact S132 version you are using (for instance version 6.1.1 or 7.2.0 or some other)? And Which exact SDK version you are using?
KURODA ELECTRIC said:"LL_TERMINATE_IND" but a slave showed that he's sent and cuts.
"LL_TERMINATE_IND" but sent timing.
"The one of the ble_conn_params_init_t" "I found out that it's dependent on next_conn_params_update_delay".Therefore a cut thing died to change "next_conn_params_update_delay" for 24 hours from 5 seconds as a temporary measure.
"Can't the reason that LL_TERMINATE_IND" is sent and the above measure have a proper basket view?
I do not fully understand. Can you please explain a bit more? Also, would it be possible to upload the full sniffer trace to this case so that I can take a look?
Einar
Dear EINAR Sun
Thank you for your support.
≫S132 is being used
This is the Ver. I am using.
SoftDevice:S132 V6.1.1 SDK:15.3.0
Please refer to the attachment.
https://drive.google.com/drive/my-drive
(It is made into a csv file so that product information is not included)
It is a packet capture result when paired with an Android device.
I am pairing with No2286. I'm cutting with No3150.
Thank you for your cooperation.
Hi,
There is a problem with the link so I cannot see sniffer trace. I do se the filename Disconnected.csv though. Please check the link, and upload a full sniffer trace in a native format to make analysis easier (being Wireshark, Ellisys or Frontline).
Einar
Einar san
I am always grateful for your help.
We will upload the requested "Wireshark" data.
● I am pairing with No906.
● It is cut at No1135.
We apologize for the inconvenience, and thank you for your cooperation.