Open TimeCard Mini: Turning a Raspberry Pi CM4 into a PCIe Time Source

Blog · Hardware

Open TimeCard Mini: Turning a Raspberry Pi CM4 into a PCIe Time Source

The Open TimeCard Mini was designed to slot into a Raspberry Pi CM4 carrier board, turning a compact Pi-based deployment into a hardware-grade PTP time source. The design rationale, the use cases and where the Mini fits in the broader hardware lineup.

Lasse Johnsen
Lasse JohnsenCo-founder & CTO, TimeBeat
7 min read
HardwareOpen TimeCard MiniEmbedded

TL;DR

  • The Open TimeCard Mini is a compact PCIe time card designed to integrate with the Raspberry Pi CM4 carrier board ecosystem.
  • It provides hardware-grade GNSS reception, a precision oscillator and hardware PTP timestamping in a footprint that fits spaces a 1U appliance can't.
  • Right answer for edge sites, embedded industrial deployments and distributed sensor networks that need precision timing without rack-mounted hardware.

Why this combination

When the Raspberry Pi Compute Module 4 launched in 2020 with industrial-grade temperature options, ECC memory and PCIe support, it opened up embedded and edge deployments where a full server is impractical. The constraint that remained was precision timing — the CM4's on-board Ethernet doesn't have the hardware timestamping precision that PTP-grade applications need, and an external grandmaster appliance defeats the purpose of using a compact embedded platform in the first place.

The Open TimeCard Mini was designed specifically to close this gap. It slots into a CM4 carrier board via PCIe, providing the hardware-grade GNSS receiver, precision oscillator and PTP timestamping engine that the CM4 doesn't have natively. The combination delivers commercial-grade timing precision in a footprint smaller than a paperback book.

What's on the card

The Mini includes a multi-band GNSS receiver (typically L1+L5 or L1+L2C, depending on the variant), a temperature-compensated or oven-controlled crystal oscillator depending on the holdover requirement, a hardware PTP timestamping engine, and the PCIe interface for CM4 integration. It runs the linuxptp software stack from the CM4 host, exposing time as a hardware reference clock that the host application can read directly and as a PTP grandmaster that other devices on the local network can lock to.

The form factor is intentionally compact. The card is designed to fit inside small embedded enclosures alongside a CM4 carrier board, not to be the primary component of a rack-mounted system. For deployments that need precision timing in a space too small for a 1U appliance, this is the answer.

Where it lives in production

Edge computing platforms where each site needs a local precision time reference. Distributed sensor networks for environmental monitoring, infrastructure monitoring or industrial control. Embedded instruments where the timing source has to be physically integrated with the measurement hardware. Compact test and measurement systems. Mobile and field-deployable measurement platforms. Educational labs and research deployments where the cost of a full grandmaster appliance is a barrier.

Each of these use cases has different specific requirements, but they share the common thread of needing PTP-grade timing in a footprint and at a cost point that traditional grandmaster hardware can't address.

Where it doesn't fit

Production trading floors, broadcast facilities, 5G fronthaul or any other application where the timing fabric needs to scale to dozens of grandmasters across a regulated environment. Use the Open Time Appliance or the standard Open TimeCard for those deployments. The Mini is for embedded and edge use cases where the standard alternatives are too big or too expensive.

Where TimeBeat fits

TimeBeat ships the Open TimeCard Mini alongside the standard Open TimeCard, the Open Time Appliance and the Open Time Node WR — each variant targeting a different deployment context. The Mini is the right answer for embedded and edge deployments where the form factor and price point are binding constraints. For larger deployments, the standard variants are still the right starting point. Talk to the engineering team if you're trying to figure out which variant fits your specific use case.

Frequently asked questions

What is the Open TimeCard Mini?+
A compact PCIe time card designed to integrate with the Raspberry Pi CM4 carrier board ecosystem. It provides hardware-grade GNSS reception, a precision oscillator and hardware PTP timestamping in a footprint that fits inside small embedded enclosures. It runs the linuxptp software stack and exposes time as both a hardware reference clock for the host and a PTP grandmaster for other devices on the local network.
How does it differ from the standard Open TimeCard?+
Smaller form factor designed for embedded deployments rather than standard server racks. The Mini sacrifices some capability (typically a less capable holdover oscillator and a more limited interface set) for size and cost. Both run the same software stack and use the same OCP TAP-aligned design philosophy.
Can it serve as the primary timing reference for a small site?+
Yes, for small embedded deployments or edge sites where the precision requirement is moderate and the operational scale doesn't justify a full grandmaster appliance. For production deployments with regulatory or safety-critical timing requirements, the standard Open TimeCard or Open Time Appliance is the right choice.
What CM4 carrier board do I need?+
Any standard CM4 carrier board with a PCIe slot that matches the Open TimeCard Mini's interface. The exact carrier board choice depends on the specific deployment — different carriers offer different I/O configurations, mounting options and environmental ratings. Talk to the TimeBeat engineering team if you want a recommendation for your specific embedded application.

Talk to us

Got a time-sync question like this in your network?

Book a 30-minute call with a Timebeat engineer — we will tell you which products fit, what the install looks like and what it would cost.