9 destinations
Engineering outline placeholder for the CAN Isolated pilot interface

CAN Isolated

Planned price · $69.00

Pilot configuration · isolated USB-C CAN interface · public checkout closed until release gates pass.

Public checkout is not open. Join the engineering pilot to receive test results and release timing before payment.

Is this pilot a fit?

Good fit
Classical CAN bench capture at a known bitrate on Windows, Linux or macOS.
Not a fit
CAN FD, safety-critical control, universal vehicle coverage or undocumented pinouts.
Before payment
A named compatibility matrix, the public validation ledger and applicable firmware or source identifiers.
Apply for CAN Isolated pilot

Application only. No payment details are collected.

SKU: MM-CAN-ISO-PILOT

Development and diagnostic use

This product is not intended for safety-critical control or as the sole basis for on-road repair decisions. Compatibility and performance claims apply only to published test conditions.

Description

A planned isolated USB-C interface for Classical CAN bench capture, paired with a local browser analyzer. The product is in pilot validation; the specifications below are targets, not final performance claims.

Who the pilot is for

CAN Isolated is being evaluated for embedded, robotics, industrial automation, education and independent engineering benches that need a traceable path from CANH/CANL to a local capture and decoded signal view.

A useful pilot case names the operating system, bitrate, connector, topology, higher-layer protocol and a reproducible task such as “capture a known 500 kbit/s bench and decode our authorized DBC.”

Target configuration

Host connection USB-C
CAN mode Classical CAN 2.0 target; CAN FD is not promised for v1
Nominal bitrates 125, 250, 500 and 1000 kbit/s targets
Physical layer Electrical-isolation target with switchable 120 Ω termination
Connector path DB9 and pluggable-terminal path; final pinout pending pilot BOM lock
Analyzer Local browser workflow for raw capture, DBC, J1939, CANopen and record/replay targets
Desktop scope Windows, Linux and macOS targets; tested versions will be named in the compatibility matrix

What the local workflow is intended to do

  1. Connect to a documented, powered bench with the correct pinout and topology.
  2. Set the intended Classical CAN bitrate and termination state.
  3. Capture identifiers, payloads, timestamps and error information.
  4. Import an authorized DBC or use a documented J1939/CANopen workflow.
  5. Keep the raw trace beside any decoded export.

Not promised in the first release

  • CAN FD;
  • compatibility with every vehicle, ECU, machine or connector;
  • a bundled proprietary vehicle/J1939 database;
  • professional-instrument timestamp equivalence;
  • safety-certified control or roadworthiness decisions;
  • cloud storage or a mandatory cloud account.

Pilot evidence required before public checkout

The public validation ledger tracks these gates and keeps every unfinished item labelled pending.

  • locked BOM, pinout, enclosure and package contents;
  • isolation, protection, thermal and long-run capture test records;
  • bitrate and operating-system compatibility matrix;
  • firmware/source release and license notices;
  • shipping weight, dispatch process and regional compliance scope;
  • successful payment, failure, refund and webhook tests.

Start with a documented bench