I am sorry that we did not consider the case of power failure when we were designing.
i just bought one of these and have discovered the same problem. how is that NOT one of the first things you think of when creating a sensor that is going to be connected to a microcontroller? especially when you’re touting easy of use w/ “plug and play” components.
has any progress been made on a software solution to fixing this issue that doesn’t require flashing the firmware? i’d really like be able to use it as part of an automated solution.
Hi
I have just bought 2 of these for a project to fill a couple of containers.
But as everyone above has noticed after a POR the results come back to 0.
This post is now 3 years old so why isn’t the firmware fixed already?
Mike
I built the required .hex files for both MCUs and uploaded them in a fork of jenskeiner’s GitHub repository. They’re located in the firmware directory at the root of the project. I used a USB to UART adapter and pymcuprog to flash the two ATTINY1616s.
Similar to pyudpi, the documentation for pymcuprog contains the wiring needed to initiate communication. The process was straightforward, and the water level sensor functions as intended after updating my code to account for the extra byte per pad.
If you want to build the firmware yourself, I’d recommend using Microchip Studio.
A huge thanks goes out to jenskeiner. I appreciate what you did.