Silicon-native Data Acquisition
& Logging.
Capture, timestamp, and archive every signal from your embedded system. Multi-channel analog, digital, and bus capture on real silicon — FPGA-accurate, calibrated, append-only. Same Yocto BSP, same IV&V evidence framework.
Kria K26 · Yocto Linux · FreeRTOS · AMD FPGA · CAN-FD · Analog I/O · UART · SPI · I²C
Capture every signal. Miss nothing. Prove it.
Data loggers that miss signals under load, lose timestamps across reboots, or require proprietary readers for exported files are not acceptable in safety-critical programs. The SoCcentric Datalogger runs on the same Kria K26 SoM, the same Yocto BSP, and the same IV&V evidence framework as the rest of the platform family.
FPGA-accurate edge timestamps. Calibrated analog channels. Append-only evidence database. Every capture session signed, every artefact traceable to a requirement. And when you need to validate the data, the Datalogger connects directly to the IV&V framework — no intermediate toolchain.
Every captured edge, sample, and bus message is stamped by the PL fabric — not the APU OS. No timestamp jitter from Linux scheduling. Sub-microsecond accuracy, aligned to a PTP grandmaster or GPS UTC reference.
Each analog input channel is factory-calibrated with a traceable reference standard. Calibration provenance — reference, date, operator, and measurement chain — is stored in the evidence database and included in every certification report.
Capture records are written to a Write-Once-Read-Many NVMe store. No record can be modified or silently deleted. Invalidations are written as new records referencing the original, with reason and operator identity.
One unit. Every signal. All the evidence.
Three layers: the K26 brain (APU runs Yocto + IV&V ingest daemon, RPU runs FreeRTOS watchdog, PL hosts FPGA timestamping and protocol-capture soft-IP), the channel front-end (calibrated analog ADCs, DIO capture, and bus monitor engines behind individual channel isolation), and the append-only storage layer (NVMe with optional cloud replication, signed at write time).
APU runs Yocto + IV&V ingest daemon; RPU runs FreeRTOS watchdog and safe power-cycle; PL hosts FPGA timestamping, DIO edge-capture, and bus-monitor soft-IP
Calibrated 24-bit differential ADCs, configurable DIO, and passive protocol monitors for CAN-FD, UART, SPI, I²C, and Ethernet — individually isolated to prevent ground loops
Local NVMe with Write-Once-Read-Many policy enforced at the driver level. Each record signed with the IV&V platform key at write time. Optional cloud replication over TLS
Native gRPC and REST API into the IV&V evidence database — same dashboard, same evidence query, same requirement-linkage and certification-report generation
Four modes. One evidence trail.
Continuous logging for burn-in and endurance. Triggered logging for fault-onset capture. Burst mode for high-rate transient acquisition. Streaming mode for real-time dashboard visibility. All modes write to the same append-only store and produce the same IV&V-compatible certification artifact.
Continuous
MODE 01 / CONTINUOUSLog all configured channels at a user-defined sample rate, indefinitely. Automatically segments the output at a configurable interval. Used for burn-in tests, long-run endurance programs, and field data collection campaigns.
Triggered
MODE 02 / TRIGGEREDArm the Datalogger and wait for a configurable trigger condition — digital edge, analog threshold crossing, CAN message ID, or a Boolean combination across channels. Capture a configurable pre/post window around the event.
Burst
MODE 03 / BURSTSwitch all analog channels to maximum sample rate (up to 1 MSPS) for a short configurable window. Used to capture high-frequency transients, power-supply noise, resonance events, or EMI signatures that would be aliased at normal operating rates.
Streaming
MODE 04 / STREAMINGStream live data to the IV&V dashboard, a Grafana endpoint, or a custom consumer over gRPC — while simultaneously writing to the append-only store. Used for real-time visibility during test campaigns and road-load data collection.
Five interface categories. Every signal your system produces.
The Datalogger front-end organises inputs into five categories, each with independently configurable sample rates, trigger conditions, and ranges. Channels are individually isolated to prevent ground loops and cross-contamination between DUT subsystems.
Five capture disciplines. Evidence up.
From high-resolution analog capture to passive protocol bus monitoring, power-rail analysis to GPS-synchronised multi-unit campaigns. Every discipline writes to the same append-only evidence database — ready for the IV&V dashboard and certification submission.
Analog signal capture
Up to 16 calibrated differential analog channels at configurable rates up to 1 MSPS burst. Individual channel calibration with traceable provenance. Used for ADC/DAC validation, sensor characterisation, and power-supply analysis. Calibration certificate included in every certification report.
Protocol bus monitoring
Passive, non-intrusive capture on CAN-FD, UART, SPI, I²C, and Ethernet simultaneously. Full frames with FPGA-accurate inter-frame timestamps. Export to Wireshark-compatible pcap and CSV. The DUT never sees the Datalogger on the bus — no protocol disruption.
Triggered event capture
Configurable trigger conditions across any channel — digital edge, analog threshold, CAN message ID, or a Boolean combination. Pre- and post-trigger window configurable per capture. Captures the exact moment of fault onset with context.
Power rail analysis
Simultaneous voltage and current on 8 rails at 1 kHz, correlated with digital events and bus traffic in the same evidence record. Detects brown-out onset, inrush events, and supply coupling. Rail maps to evidence requirement automatically.
Certification evidence
Calibration provenance on every analog channel. Signed, timestamped, requirement-mapped capture records. Append-only evidence database — every session, every channel, every sample. ISO 26262, DO-178C, IEC 62304, and IEC 61508 artifact shapes supported.
Nine industries. Purpose-built capture missions.
Road-load data collection on an ADAS ECU — ISO 26262 ASIL-B.
CAN-FD, IMU channels, and power rails captured at 1 kHz GPS-disciplined to UTC; evidence mapped to ASIL-B requirements with no post-processing toolchain.
UAV flight data recorder with FPGA timestamps — DO-178C.
UART telemetry, analog sensors, and power rails captured at each flight phase; exported as DO-178C artifacts with calibration provenance on every channel.
Tactical vehicle data bus capture — MIL-STD-810 field evidence.
CAN-FD and UART buses passively tapped; power-rail and IMU telemetry GPS-synchronised into a tamper-evident trail with no vehicle integration changes.
Safety PLC runtime monitoring — IEC 61508 SIL-2 evidence.
Ethernet safety-bus traffic, digital I/O states, and power-rail quality captured at 1 kHz; automated SIL-2 reports generated at end of each production shift.
AGV navigation data collection — IEC 61508 SIL-2 run-time.
CAN-FD traffic, encoder analog signals, and motor rails captured at 1 kHz with 500 ms triggered windows on motor current fault events.
EV battery pack cell telemetry — ISO 26262 ASIL-D endurance.
128 analog cell channels, I²C BMS bus, and pack power rails captured across 500 charge–discharge cycles with GPS-synchronised records imported into IV&V.
Train control bus monitoring — EN 50128 SIL-3 evidence trail.
Ethernet and serial safety-bus traffic monitored passively; append-only evidence trail built for safety authority submission with zero impact on vital systems.
Satellite telemetry downlink capture — ECSS-Q-ST-60 provenance.
SpaceWire telemetry, power-bus monitoring, and timing channels captured simultaneously with GPS-synchronised calibration provenance on every measurement.
Smart grid edge controller event logging — IEC 62443.
Modbus/RTU and Ethernet traffic, power-rail quality, and I/O states captured with triggered windows on disturbance events for cyber-physical security review.
Every channel calibrated. Every capture traceable.
Calibration provenance on every analog input. Signed, timestamped, requirement-mapped capture records. Append-only evidence database — every session, every channel, every sample. The IV&V evidence framework extended with Datalogger channel and time-reference provenance.
Engineering questions, answered straight.
Connect
Ready to capture every signal from your system?
Get in touch with our engineers. Tell us your platform, your signals, and what evidence you need to generate. We will scope the right channel configuration and storage tier. Already running IV&V or HIL? The Datalogger connects to the same server — no new tooling required.
NO SALES PRESSURE. NO PRICING WALL. ENGINEERS TALKING TO ENGINEERS.