Wippersnapper: Fatal error suddenly appeared

[T_Mo]

It might be difficult to replicate, as I'd been running that setup for several weeks before the bad thing happened.

I'm still using it (after restoring the json file). The issue has not recurred so far.

[T_Mo]

Note that there is another bad habit of the INA219 when used with Wippersnapper.

For no apparent reason, at random times, the INA219 will stop reporting updates to its feeds (both voltage and current).

Looking at the USB serial port when this happens, the device is no longer being polled for data. There are no error messages, it just isn't reporting data, so the feeds don't get updated.

The only fix for this is to cold-start the unit. Pushing the board reset button won't fix it. You have to disconnect all power sources and restart it from scratch.

Looking at the code in the INA219 library (I think it was the CP library, but can't remember for sure), there are comments that indicate the part has a known issue when exposed to current spikes. However the library includes some work-around for it. Maybe the work-around isn't totally successful, or maybe Wippersnapper doesn't have the same work-around.

[brubell]

For no apparent reason, at random times, the INA219 will stop reporting updates to its feeds (both voltage and current).

Looking at the USB serial port when this happens, the device is no longer being polled for data. There are no error messages, it just isn't reporting data, so the feeds don't get updated.

The current spike theory may be the case, especially if the fix wasn't pushed to the Arduino Library. Is this the issue you are referring to? https://github.com/adafruit/Adafruit_Ci ... /issues/10

[T_Mo]

I don't recall seeing that issue, so that's not it.
I'll try to find the comments I noticed in some library code.

[T_Mo]

Here is the reference for the work-around in the CP INA219 library.
https://docs.circuitpython.org/projects ... na219.html

ina219_workaround.JPG (41.01 KiB) Viewed 9 times