Code only runs in debugging

RE: Code only runs in debugging

Håkon Alseth — Thu, 28 Jun 2018 09:02:32 GMT

You could loop over it to ensure that it is fetched when it's non-zero, similar to this:

{

es_battery_voltage_get(&vbatt);

} while (vbatt == 0);

Best regards,

Håkon

RE: Code only runs in debugging

Vishwas Jain — Wed, 27 Jun 2018 04:16:43 GMT

Thank you Hakon,

I moved es_battery_voltage_get() just before setting it as the manufacturer data and disabled the logging but it is not working. To check, I kept es_battery_voltage_get() in advertising function only and enabled the logging and now everything works fine!

I also tried to add delay(500ms) between these two, _init() & _get() functions but didn't work.

RE: Code only runs in debugging

Håkon Alseth — Tue, 26 Jun 2018 13:49:54 GMT

I suspect that this added a smaller delay, allowing the SAADC callback handler to execute before you call es_battery_voltage_get(), so that you got the correct value. Best option is to move the call further in time so that you do not end up in this scenario again when disabling logging.

RE: Code only runs in debugging

Vishwas Jain — Tue, 26 Jun 2018 12:35:44 GMT

I do not know the reason but I did SAADC_CONFIG_LOG_ENABLED 1 in sdk_config.h and the true values start broadcasting.

Can it be the problem? If yes, why was it the problem because it is just a log info, nothing to do with values.

If no, then according to your suggestion, I would try to add delay between es_battery_voltage_get() & es_battery_voltage_init().

RE: Code only runs in debugging

Håkon Alseth — Tue, 26 Jun 2018 12:27:23 GMT

Hi,

The es_battery_voltage_saadc library will initially start a conversion, and if you call es_battery_voltage_get() straight after the _init(), it will not be done yet and you will get the default value (0) back.

Could you try to call es_battery_voltage_get() just before setting it as the manufacturer data in your advertising payload, and see if this works better?

Best regards,

Håkon