what is the principle of converting Ticks in to seconds

[karan]

Hello

I am trying to change the ticks value of Battery measurement interval (ble_app-prox example) but i am not able to understand how the ticks period is measured based on what i understood from the example 1s is equal to 1000ms so totally we are setting it to120s then the ticks period is equal to 120000 if am wrong please correct me and explain me the correct method my aim to see the battery level changing based on the battery -measure_interval any help would be greatly appreciated

thankyou

[Susheel Nuguru]

Assuming you are using nRF51 and using APP_TIMER (RTC1).

You initialize the APP_TIMER using the prescaler. lets say that the prescaler is 0 then your timer generates 32768 ticks per second.

The macro given in app_timer.h converts the milliseconds to number of ticks.

#define APP_TIMER_TICKS(MS, PRESCALER)\
            ((uint32_t)ROUNDED_DIV((MS) * (uint64_t)APP_TIMER_CLOCK_FREQ, ((PRESCALER) + 1) * 1000))

Above you see that if MS = 120000 and prescaler 0, which is 120 seconds then you will get Ticks = ((120000*32768)/(0+1)*1000) rounded up to integer = 3932160 ticks. This is telling you that the timer will put 3932160 (0X3c0000) in RTC compare register and when RTC is started and is running for this many ticks, then it will be 120 seconds.

Does this answer your question?

[Susheel Nuguru]

At first the application is started with 100% battery because the actual ADC sample is started in battery_level_meas_timeout_handler after 120 seconds from enabling this notification. After this value the actual pin is sampled and then in the ADC_IRQHandler you use battery_level_in_percentto convert the sampled value.

For your CR2032, the 15% might be correct value, but it is displayed after 120 seconds because that is when the first sample is taken. If you want this to be updated faster, you need to change BATTERY_LEVEL_MEAS_INTERVAL.

For your USB, you cannot use battery_level_in_percent in ADDC_IRQHandler as this is for CR2032. You need to write your own interpreting function in case of USB.