Difference between revisions of "Timezone clocks"
m (→Wired or wifi) |
Realitygaps (talk | contribs) m |
||
| Line 1: | Line 1: | ||
{{Project | {{Project | ||
| − | |ProjectSkills=Electronics, PCB design, Programming, Networking, TCP/IP, NTP. | + | |ProjectSkills=Electronics, PCB design, Programming, Networking, TCP/IP, NTP. |
|ProjectStatus=Planning | |ProjectStatus=Planning | ||
|ProjectNiche=Electronics | |ProjectNiche=Electronics | ||
| Line 45: | Line 45: | ||
* Amsterdam | * Amsterdam | ||
* Moscow | * Moscow | ||
| − | * | + | * Sydney |
Revision as of 15:05, 2 March 2017
| Projects | |
|---|---|
| Participants | Katje |
| Skills | Electronics, PCB design, Programming, Networking, TCP/IP, NTP. |
| Status | Planning |
| Niche | Electronics |
| Purpose | Fun |
Contents
Intro
I thought it would be a fun idea to have some clocks above the entrance way between the main space, and the aux space.
Feature wish list:
- NTP based time, so as to avoid need to change clocks to keep time or for DST.
- LED based displays (Easy to use/see)
- 24 hour clock.
- KISS design that doesn't solely rely on funky code to work.
Basic design thoughts
74HC4543 driver chip, this allows latching of input so all 4 or 6 digits needs just 4 data pins, and 1 pin per digit for latching.
Design questions?
4 digits or 6?
Having 5 clocks with seconds displayed where sink may not be spot on perfect could really jar. Maybe have a 6 digit version for local time, with 4 digit display for the others?
Which micro?
Arduino pro mini is cheap, small and should have enough grunt, but could be an interesting challenge getting TCP/IP, NTP, Timezones, DST, and clock functionality all in 2k of ram.
Wired or wifi?
We'll need wires to power it, so ethernet + PoE may be the simplest solution?
Timezones
Which timezones to use?
- Boston
- London
- Amsterdam
- Moscow
- Sydney
Status
2017-03-02
Crazy idea discussed on the mailing list.
