So close to being able to use Jled sequences natively, if I could figure out how to calculate the number of times to repeat for a given step length.
This looks helpful (https://arduino.stackex…
To send a cycle, we need to set up the duration of each repeating message.
- Need entries (#8) for
- step length
- cycle ID
- number of transmitters
- Need a function…
I thought I had typed this all out, but
- Alarm2 has only minute resolution
- Alarm1 has second resolution
So when I set up Alarm2 but turn off cycle, if I turned cycle back on within the…
Using timespans might work to fix this and #35 if I can fix #27.
Random times every once in a while again.
https://www.reddit.com/r/arduino/comments/hdg70t/ds3231_rtc_random_numbers/
Before I too far, consider just comparing rtc.now() and the start time in loop() to trigger the scheduled program.
Confirming that I can't set an alarm more than a month in advance (or maybe ~2 months if the current month has 30 days and the next month has 31 days, and you set it for the 31st). Wild.
https:/…
I can set Alarm2 and have SQW notify of the alarm. I tried
- setting, turning off the ESP32, waiting past alarm time, and it does not trigger on boot (this is good)
- setting, rebooting ESP32,…
I tried the same if ((rtc.alarmFired(2) == true) ) code on the breadboard version and get the same results (crash on form submission).
Changed true to 1 and it is not crashing.
Also, even though I get stuff like this, the RTC time seems to be right:
It's this bit that's causing the i2cCheckLineState() error and reboot:
I'm getting weird dates again. I will look at the hardware connections tomorrow.
It's also worth considering using the SQW pin: https://garrysblog.com/2020/07/05/using-the-ds3231-real-time-clock…
RTC alarms seem to fire at the next opportunity, even if they happened when ESP32 was off. This is a problem I wanted to avoid.
Reset the alarm in setup() if it's in the past?