This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

15.2 s112 proximity example, battery service value not updating

Hello,
I'm able get an updated battery service value on nrf connect using the 15.2 s112 proximity example on the DK using a cr2032.
Then adjusted the clock to LF RC and removed DEVELOP_IN_NRF52832 (needed for custom 810), flashed again to the DK, and still good.
Flashed same FW to custom 810, connected to battery service, and where on the DK after a number of seconds the battery value is updated from 0x64 to say 0x27, on the custom 810 the value stays at 0x64.

Trying to understand why this is so on the 810, if any slight differences between the two chips might result in how the battery service is calculated and if changes are needed to be applied to the proximity example (if any at all).

thank-you,

Related