Documentation
Quick Start, compatibility, firmware, release notes, safety and evidence status for the unreleased MallMars CAN Isolated engineering pilot.
Release-safe documentation for the CAN Isolated engineering pilot. Start with the intended bench workflow, then check the evidence status for the exact host, firmware and hardware revision.
Start with the task
CAN Isolated Quick Start
Prepare a controlled two-node Classical CAN bench, choose the host path and define the first-capture acceptance record without treating a target configuration as shipped hardware.
Compatibility Matrix
See the Windows, Linux and macOS paths under consideration, their current status and the evidence required before any compatibility claim is published.
Firmware and Downloads
Confirm whether a signed release package, source tag, binary hash, recovery path and licence record actually exist before installing or flashing anything.
Changelog
Track documentation and validation changes separately from future hardware and firmware releases.
Validation Status
Review the eight evidence gates covering supplier identity, traceability, isolation, compatibility, capture integrity, shipping, pilot reliability and commerce.
Current release boundary
| Hardware | Target configuration only; supplier, BOM and production revision are not locked. |
|---|---|
| Compatibility | No released host matrix; every Windows, Linux and macOS row remains pending DVT. |
| Firmware | No MallMars firmware binary, USB identity or recovery image is published. |
| Commerce | Public checkout remains closed; the pages do not constitute an offer to sell. |
Reference and safety routes
- CAN bus guides for vendor-neutral selection, driver and bench procedures;
- safety and intended use before wiring or powering a bench;
- open-source notices for the release and attribution policy;
- support for the information required in a reproducible issue report.
Match documentation to the unit
A future release note must name the hardware revision, firmware version and hash, host version, driver or backend, tested bitrate and known limits. If those identifiers are absent, treat the page as planning material.