In our project we want to report the time that the core was started. In setup() we made a call to Time.now() and stashed the value away for later use. This works great when the core is started from the reset button. However, when the core is actually power cycled the reported time is very small. Li…

@JSchrempp , take a lot at this topic: https://community.sparkdevices.com/t/time-now-in-setup-gives-bad-time-after-power-on/9098

@peekay123 , You pointed me back to my same topic. Maybe you meant to include a different link? BTW, I now see that after a power on Time.now() takes about 2 seconds to become stable. Jim

I hate my ipad sometimes :stuck_out_tongue: The correct link is: [image] Time Synchronization: Can't Set RTC Time Upon Reboot [SOLVED] Firmware Hello there, So I’m using the Spark.syncTime(); function in my void setup() and …

I’ve added this code to our setup() function. It seems to do the trick. do { resetTime = Time.now(); // the the current time = time of last reset delay(10); } while (resetTime < 1000000 && millis() < 20000); // wait for a reasonable epoc time, but not longer than 20 seconds Jim

this seemed to do the trick for me if(CurrentTime < Time.now()){ CurrentTime == Time.now(); }

[Solved/Fixed] Time.now() in setup() gives bad time after power on

Firmware

peekay123 January 2, 2015, 8:57pm 4

I hate my ipad sometimes

The correct link is:

Topic		Replies	Views
Time Synchronization: Can't Set RTC Time Upon Reboot [SOLVED] Firmware	9	3794	December 16, 2014
How can I test if Spark.syncTime() has finished after startup? Cloud	2	2502	July 16, 2014
Photon - Time.now() returns December 1999 Troubleshooting photon	5	652	May 2, 2019
[SOLVED] Reset does not pull in Time from the Cloud Troubleshooting	7	1493	November 5, 2016
Time value error during cold boot Troubleshooting	13	2312	September 15, 2014

[Solved/Fixed] Time.now() in setup() gives bad time after power on

Related topics