Battery Request Second time disconnection

RE: Battery Request Second time disconnection

Sigurd — Wed, 02 Nov 2016 12:32:49 GMT

Try to set it to 20ms then, so you have something like this:

#define MIN_CONN_INTERVAL                   MSEC_TO_UNITS(20, UNIT_1_25_MS)             /**< Minimum acceptable connection interval (20 ms).  */
#define MAX_CONN_INTERVAL                   MSEC_TO_UNITS(1000, UNIT_1_25_MS)            /**< Maximum acceptable connection interval (1 second). */

There is no uniform connection settings for Android. What Android version are you using on the motoE ?

RE: Battery Request Second time disconnection

magesh vasudevan — Wed, 02 Nov 2016 12:13:07 GMT

if I change the value as suggested, its not listing in mobile (not advertising). whether the connection parameter will change from mobile to mobile or uniform settings is there for android mobiles?

RE: Battery Request Second time disconnection

Sigurd — Wed, 02 Nov 2016 08:27:03 GMT

0.5 seconds is actually a bit high as an min connection interval. Try to lower it to 10ms.

RE: Battery Request Second time disconnection

magesh vasudevan — Wed, 02 Nov 2016 05:32:40 GMT

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

RE: Battery Request Second time disconnection

Sigurd — Fri, 28 Oct 2016 12:47:39 GMT

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.

RE: Battery Request Second time disconnection

magesh vasudevan — Fri, 28 Oct 2016 03:43:18 GMT

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)

RE: Battery Request Second time disconnection

Sigurd — Thu, 27 Oct 2016 14:21:30 GMT

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?