Engineering / Exubits Engineering

Exubits Engineering

Embedded product engineering team

The Exubits engineering team writes and maintains the Reference pages on this site. Posts under this byline are collective work — PCB, firmware, embedded Linux, control and connectivity engineers reviewing each other's drafts. Individually authored posts carry an individual byline instead.

  • PCB, firmware, Linux, control and connectivity in one team
  • Roughly a decade shipping production embedded hardware
  • Every claim on this site links to its proof

Posts by Exubits Engineering

6 published posts.

  1. Reference7 min readLast verified 3 September 2026

    Choosing between CAN, CAN FD and Ethernet industrial links

    CAN suits cheap, rugged, low-rate event traffic; CAN FD when payloads outgrew 8 bytes but a bus still fits; industrial Ethernet (PROFINET, EtherCAT, TSN) for megabits or tight cycle times. Expect to bridge, not replace.

  2. Reference7 min readLast verified 3 September 2026

    What a production hand-over pack has to contain

    It lets someone else build, test, certify and change the product without the original team: design data, a reproducible firmware build, factory tests with limits, the compliance file, an SBOM, and known issues.

  3. Reference7 min readLast verified 3 September 2026

    What a schematic review should catch before layout starts

    A schematic review catches the errors that get far more expensive after layout: power sequencing and budgets, reset and strapping, every net's return path, connector pinout and ESD, test access, and BOM risk.

  4. Reference7 min readLast verified 3 September 2026

    Where the milliseconds go between sensor and display

    Glass-to-glass latency is exposure + sensor readout + CSI-2 + ISP + buffer and queue waits + composition + one or two display refreshes. Most of it is exposure and buffering, not code; shrink queues and sync to vsync.

  5. Reference7 min readLast verified 3 September 2026

    Stating a determinism budget for a control loop

    Before writing loop code, fix four numbers: sample rate, allowed jitter on the sampling instant, worst-case actuation latency, and the deadline-miss policy. Every downstream choice then checks against the budget.

  6. Reference8 min readLast verified 3 September 2026

    What a Yocto BSP hand-over should actually contain

    A usable Yocto BSP hand-over: a pinned manifest, vendored layers, a documented DISTRO/MACHINE, a reproducible build, a signed image with its SPDX SBOM, and the rationale for every kernel and U-Boot config choice.

Talk to an engineer

The bylines on this site are the people who answer when you get in touch.