💾 Archived View for r2aze.observer › archive › 2004-03-08-frame-of-reference.gmi captured on 2022-06-03 at 23:46:23. Gemini links have been rewritten to link to archived content

-=-=-=-=-=-=-

Frame of reference

📅 2004-03-08

📑 Tech

🏷 #idea

🏷 #rant

You’d think it would be easy to have perfectly synchronised time. After all, time’s all around us. 28 sattelites do nothing but shout it out into the ether. The GPS sattelites, I mean. Expensive atomic clocks floating above our heads meant to do nothing else but tell time so we could tell the place.

It _is_ kinda easy. All you need is a GPS receiver and ntpd, right? The NTP daemon knows about the GPS receivers and can get time information from them.

Wrong. You also need a serial port, and these days, it’s a rare commodity, at least on my server motherboard which only has one. And it’s taken up already by the UPS too.

_And_ you also need to actually connect the GPS to the serial port and make sure it’s supplied with power cause batteries will only last it nine hours at most.

So in the end it comes out to:

1. A serial GPS cable with a car lighter socket plug for power. **($35)**

2. A USB to serial converter **($20)**

3. A car lighter socket, from an extension cord or something else. **($10)** _(it might not be optimal, but I’m too stingy to cut up a $35 cable, so it’ll be necessary.)_

4. A 12 volt power supply **($10)** _(actually, Garmin eTrex wants 3 volts and not 12, but see above)_

*$75** just for _cables_. And that not counting that I have the GPS receiver already. It’s either that or making my own Garmin connector, which is not that easy since they use a highly unorthodox plug, unlike anything I’ve ever seen on any other device. You literally have to cut one out of a brick of plastic and set up holes for contact springs.

Grrrr…

✏️ View and leave comments

◀️ 2004-03-05: Воспоминание из вчерашнего

⬅️ Tech: Повод

➡️ Tech: Barcodes: Elaborating on an idea

▶️ 2004-03-11: Yesterday, oh how I long for yesterday…

↩ Home