A Trillion Year Clock. (addons: bigbang, current time, and eeprom backup, are included)
Clock Loop
Posts: 2,069
I created a clock that runs to 2,147,483,647 Trillion years, at which point it will roll over to 0. (At least in software)
If you need something longer, then you need to write it down on a piece of paper.
Connect putty to your propeller's p30/p31 debug output. :P
https://hackaday.io/project/162734-a-trillion-year-clock
If you need something longer, then you need to write it down on a piece of paper.
Connect putty to your propeller's p30/p31 debug output. :P
https://hackaday.io/project/162734-a-trillion-year-clock
ADDON INCLUDED wrote:eerpom backup
NOTE: THIS CLOCK USES THIS FORMAT: TrilionYear.BillionYear.MillionYear.Millennium.Century.Decade.Year.Day.Hour.Minute.Second The numbers completely populated before it rolls over would look like this: 2,147,483,647 Trillion Years 999 Billion Years 999 Million Years 999 Millennium 9 Centuries 9 Decades 9 Years 364 Days 23 Hours 59 Minutes 59 Seconds IF 1 second is added to this, all numbers (should)become 0.
Comments
Thats a valid point.
The best I can do is force the propeller to run the counter as fast as it can.
And my code isn't very efficient, so it will still take a time machine to test, with the non-optimized code I posted.
Hmm, thats a legit reason to start work on the time machine, to test the trillion year clock...
So many ways to go.. so little.... time...
Ok, I think I have the proper time it should be set to.
13,799,792,018.342.15.51.42 years old.
13,799,000,000 = (13.799±0.021)×10^9
790,000 = Fudge number. Speed of light is 299,792,458, so i stole from its middle.
2018 = Our year.
Countdown timer since beginning of 2018
https://www.timeanddate.com/countdown/generic?
342 days
15 hours
51 minutes
42 seconds
old.
Now none of us can use the excuse our clocks are wrong.
TO THE FUTURE!
You might want to check the best known limits on the lifetime of the proton too, thinking about it
All clocks need to be adjusted once in a while, its accuracy could improve with atomic sources, and better math.
The clock should be modified to adjust for proton lifetime limits, when that is of concern, it would be advisable to have a better clock technology and storage medium developed.
Since time is relative, in this case, it relates to the humans home planet and birth epoch.
You do understand that over that long of a time span that any error in your timing will be greatly multiplied.
When traveling in a car, eventually you need to stop and take a break.
So I would advise the same for long time traveling.
Take a break, get out of the DeLorean, and make sure to adjust clocks accordingly.
Never navigate by clock alone, use your eyes, if it looks off, don't stop in that town... era..
OH, and never pickup hitchhikers, ESPECIALLY NOT ONE THAT LOOKS LIKE YOU.
You wouldn't drive off a cliff even if the road map said.... Your eyes would say, NO.
Well don't go so far (in any direction) that you drive off your "island of stability". https://en.wikipedia.org/wiki/Island_of_stability
Since its never been done before, I plant a flag on the "Island Of Stability", and declare it the 51st state of the United States of America.
As such, protected by all such laws and rules granted to member states within, and without.
...
But do, stop and let the kids see the dinosaurs, etc...
But it has been done before, I just didn't have my smartphone with me to take a photo of it. So, like a large chunk of Antarctica, it is a protectorate of Australia!
" i "
Gotta pick something...
All that jive about staying current with the earth spin etc.. Its all relative.
If you wake up the sun is at high noon, then I suggest you adjust your clocks.
The room for error in the calculation is...
13,799,000,000 = ± 21,000,000
42 MILLION YEARS is your window of error or play.
I think OUR standard of local time fits nicely in that window.
Sure we still have room to grow. 42 million years of it.
Oh, there it is again... 42.
SO WHAT!
Everyday, I feel the sun on my skin and feel its lovely radiation.
And I do actually love my sun. It keeps me ALIVE!
I updated the code to properly calculate the uptime.
I also put the timer in its own cog, and reduce its duty to timing only.
My timing is still off from spin execution cycyles.
So I measured my Repeat code and adjusted the waitcnt value till it measured 1/10th of a second.
Time = 8_000_000
So the execution time of
Should be 8_000_000...
I have found that the program has timing hysteresis with this method, between waitcnt(7_999_019 + cnt) and (7_999_020 + cnt)
it also runs slow still.
https://forums.parallax.com/discussion/download/124678/TrillionYearClock.zip