Open TimeCard — initial timebeat.yml configuration

Minimum viable config, oscillator selection, GNSS signals, SFP precision mode and verification.

10 min read

The Open TimeCard is configured as a secondary clock under secondary_clocks using the timebeat_opentimecard protocol. Every per-card setting lives in a card_config: string array. Below is the minimum viable config — add to your existing /etc/timebeat/timebeat.yml and restart the service.

Sign in to read more

Free access — just your email

Drop your work email and we’ll send a one-time sign-in link. No password to remember, no account to create. Stays valid for 30 days.

By signing in, you agree to receive the requested document and may receive occasional product updates. We never share your details. See our Privacy Policy.

Software setup

The Timebeat software configuration is the same across all TimeBeat hardware. See the Timebeat software guides →

Need a human?

Still working through Open TimeCard?

The guides cover the configuration surface, but if your deployment has a wrinkle we have not documented, our engineering team is one email away. Most enquiries get a same-day answer.