Engineering / All posts
All posts
The whole publication in one stream, newest first. Browse by topic on the hub grid instead.
Page 1 of 1 · 6posts
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.
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.
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.
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.
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.
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.