Problem with the autonomy and the connection parameters

[brunky]

Hello

I have developed an application for the smart beacon and I have the following problem:

I use two diferent sets of values for the connection parameters in order to make two different tests

1st

MIN_CONN_INTERVAL MSEC_TO_UNITS(20, UNIT_1_25_MS)
MAX_CONN_INTERVAL MSEC_TO_UNITS(40, UNIT_1_25_MS)
SLAVE_LATENCY 0
CONN_SUP_TIMEOUT MSEC_TO_UNITS(800, UNIT_10_MS)

2nd

MIN_CONN_INTERVAL MSEC_TO_UNITS(1000, UNIT_1_25_MS)
MAX_CONN_INTERVAL MSEC_TO_UNITS(1750, UNIT_1_25_MS)
SLAVE_LATENCY 0
CONN_SUP_TIMEOUT MSEC_TO_UNITS(6000, UNIT_10_MS)



When I use the second set of parameters, a coin cell battery only lasts 1 or 2 days instead about the 20 days that lasts with the first set of parameters.

I think the parameters are the problem because now I am testing again with lower parameters and it looks like it works fine again but I want to extend the autonomy to the limit and I don't understand why the second set of parameters doesn't work

I'm using sdk11, s130, segger and keil IDE and nrf51 in Smart beacon kit

Thanks

[Vidar Berg]

Hello,

I would have expected significantly longer battery life with 2nd configuration. Do you use any peripherals such as and  UART/TWI in your code, and are you calling sd_app_evt_wait() from your main loop?