[time-nuts] NTP Clock suggestions?
lists at rtty.us
Mon May 27 14:27:07 EDT 2013
If you go with the Pi's I2C port, it's strictly a 3.3 volt port. Some (but not all) of the display boards are 5V gizmos.
If you go with a WiFi approach, be careful about latency. NTP only understands symmetric delays. Of course if you are on a cable modem there's noting in the WiFi that's worse than what you already have.
On May 27, 2013, at 1:25 PM, mike cook <mc235960 at gmail.com> wrote:
> Le 27 mai 2013 à 16:56, Miguel Barbosa Gonçalves a écrit :
>> I don't understand why a microprocessor with an Ethernet controller and a 7
>> segment display would cost so much to manufacture... I think I'll build my
> One advantage of having an OS and NTP client on board is that you get automatic TZ and DST offsets if you want. A Pi also works fine with a USB WiFi dongle so no ugly CAT5 wiring required. One of the Pi s I2C buses could be used to drive a 7 seg display controller such as those from Adafruit.
> As you would have the full TCP stack you could configure it over the same wiFi . It's not Windows but doesn't need much power so long as you don't want to drive giant LEDs.
>> Good joke :-) I imagine the electricity bill at the end of the month.
>> I would like to have a clock sync with my super precise stratum 1 servers
>> :-) what's the point in having them if I can see the time anywhere? :-)
>> time-nuts mailing list -- time-nuts at febo.com
>> To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
>> and follow the instructions there.
> time-nuts mailing list -- time-nuts at febo.com
> To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
> and follow the instructions there.
More information about the time-nuts