15.2 s112 proximity example, battery service value not updating

RE: 15.2 s112 proximity example, battery service value not updating

Simon — Wed, 26 Sep 2018 19:46:45 GMT

expecting not 0x64
there is no diode on board
removed the diode addition in code, still 0x64
then checked for pin conflicts (its happened before)
changed button pins from pins used on 832 (but not on 810),
to actual 810 pins that are not being used,
and now getting a value like 0x26

thank-you again for this help, ...much appreciated

RE: 15.2 s112 proximity example, battery service value not updating

Jørgen Holmefjord — Wed, 26 Sep 2018 08:12:46 GMT

What value do you expect the output to be? The proximity example adds a voltage drop for a diode on the DK, DIODE_FWD_VOLT_DROP_MILLIVOLTS, to the battery voltage measurement. If you do not have this diode on your board, you should remove it from the code. Everything above 3000 mV (measurement + diode drop voltage) will output 100% (0x64).

RE: 15.2 s112 proximity example, battery service value not updating

Simon — Tue, 25 Sep 2018 23:10:51 GMT

clock source? sdk_config.h > nRF_Softdevice > NRF_SDH_ENABLED > Clock

RTT does show in both custom & DK of entering
battery_level_meas_timeout_handler, and saadc_event_handler.

But in RTT debug, the value will always be 0x64.
Issue is when powered by cr2032.
How best to debug in this situation?

thank-you,

RE: 15.2 s112 proximity example, battery service value not updating

Jørgen Holmefjord — Tue, 25 Sep 2018 12:14:35 GMT

Hi,

Where and how did you change the clock source to LF RC? You should debug the application and check if it enters the timout handler, battery_level_meas_timeout_handler, and saadc_event_handler. The first handler will trigger the SAADC sample, and the second handler will update the battery level.

Best regards,
Jørgen