Tag: Real Time Clock

Using DFRobot tipping rain bucket with Raspberry Pico and Waveshare real time clock

The DFRobot tipping rain bucket was developed and example code provided to run on an Arduino Uno. There are some limitations that are better addressed using a pico as the controller. The pico has adequate internal memory to store readings and can be mounted with the Waveshare real time clock for accurate time stamps. More importantly, the WS RTC controls the power to the pico and turns the power to it off and on. The DFRobot unit only stores time elapsed and not real time. With the Uno I would need to add memory and RTC modules and do additional programming.

The python library available from DFRobot is for a Pi 4 or 5, not compatible with the pico. The core electronics shop has posted a software library that allows the DFRobot sensor module to be managed by a pico. https://forum.core-electronics.com.au/t/gravity-tipping-bucket-rainfall-sensor-i2c-uart-sen0575/20840

It uses the PiicoDev Unified Library. The default i2c connection is channel 0, scl pin 9, sda pin 8. A problem arises when using the Waveshare RTC module which is also on channel 0. This causes any read of either unit to fail. They can be separated but that involved digging thru a lot of unfamiliar code. The quick solution is to move the default connection to channel 1. I used scl pin 11, sda pin 10. You can change it in the call in DFRobot python code or directly in a local copy of PiicoDev library.

Once the 2 units are on separate channels, you can read from both without interference.

The end use is to record rainfall at a remote location for 6 to 8 months without service. The DFRobot sensor unit can run on a separate battery with solar trickle charge. Current drain is under 3mA. This will accumulate the rainfall readings for the pico to read hourly. The pico uses the WS RTC to turn on the power every hour, read and store the values, then turn off power until the next hourly read. The pico battery doesn’t need a trickle charge as the power consumption is for less than 100 milliseconds each hour.

DS3231 Real Time Clock. How to set the alarm

This is in combination with the Raspberry Pi Pico. Use the chip to keep time while the Pico is in deep sleep or powered off. I need to trigger a P-MOSFET, wake up the Pico, make & store a measurement then power off again.

The timer chip is the core of a number of products from a variety of makers. However, when it comes to setting an alarm, there is remarkably little information for the average user. Here is the function; here are the 8 variables. No meaningful examples or explanation. Fortunately, there are enough software versions that I was able to look at the source code and figure out what settings are needed to get the alarm to work.

This code is from https://RandomNerdTutorials.com/raspberry-pi-pico-ds3231-rtc-micropython/
Alarm times (year, month, day, weekday, hour, minute, second, millisecond)
alarm_time = urtc.datetime_tuple(2025, 04, 09, None, 21, 12, 00, 0)
Sets the alarm time for Apr 9, 2025 at 9:12PM.

However if you want to set the alarm to trigger every second, this is what you need.
alarm_time = urtc.datetime_tuple(None, None, None, None, None, None, None, 0
This outputs an alarm every time the millisecond counter reaches zero. That is every second.
To trigger every minute, set the seconds to 0 and milliseconds to None.

Couple of notes on hardware/software

The Waveshare chip needs to have a jumper installed to get the signal to the output pin. However, the physical layout and tiny size make it very difficult to actually solder anything into place.

There are drivers from an assortment of vendors based on the Hinch github repository. They use the same name for driver file but the driver is specific to the board. That can cause a lot of confusion when you run the software and it errors out. I had to put remarks in the header of all files as to source and which chip it runs on.

If you change the driver, unplug the Pico and allow it to clear. Prior drivers can leave settings that cause the new driver to fail.