Issue: when the battery level is requested for the first time from mobile its responding correctly. but, when it is requested for the second time from mobile, disconnection happens with message unknown error (0x3b).
Issue: when the battery level is requested for the first time from mobile its responding correctly. but, when it is requested for the second time from mobile, disconnection happens with message unknown error (0x3b).
Could you please try to provide some more information? What chip are you using? nRF51? nRF52? nRF24L01+? Is this a custom board, a DK or maybe a EK? What SDK version are you using? What SoftDevice are you using? Are you running one of the examples in the SDK? What mobile device is this? What app are you using on the phone? Android? IOS? Are you able to debug the chip? In what part of the code does the error happen? Which of the devices are issuing the disconnect? Where are you seeing this error, on the mobile or on the chip? Does the chip enter the error handler?
the chip we use is nrf52. its a custom board and sdk 11.0 version. s132 softdevice with proximity profile running. motoE mobile device is used. we are seeing an error in mobile log as unknown error (ox3b)
The error 0x3b is caused by "Unacceptable Connection Interval". What values are you using for these parameters ? MIN_CONN_INTERVAL
, MAX_CONN_INTERVAL
, SLAVE_LATENCY
and CONN_SUP_TIMEOUT
? It may be that the bluetooth stack used in motoE does not accept the connection interval parameters you are using.
Only default value used in the program.
MIN_CONN_INTERVAL : 0.5 seconds
MAX_CONN_INTERVAL : 1 seconds
SLAVE_LATENCY : 0
CONN_SUP_TIMEOUT : 4 seconds
0.5 seconds is actually a bit high as an min connection interval. Try to lower it to 10ms.