9 destinations

50-unit engineering pilot

Analyze CAN traffic without proprietary software.

An isolated USB-C CAN interface paired with a local browser analyzer. DBC, J1939 and CANopen workflows. No cloud account.

Join pilot See sample decode

Built for development and diagnostics. Not intended for safety-critical control or on-road repair decisions.

Local analyzer · sample frame

interface ready
J1939 · DM1 example decoded locally
CAN ID
18FECA00
PGN
65226
Source
Engine #1
State
Sample data
Interface preview uses labelled sample data; pilot screenshots will replace it after EVT validation.

From wire to readable signal.

Three operations, kept local. The first pilot validates the complete path before public sales open.

Set the bus, then see the frame.

USB-C, classic CAN 2.0 and selectable 120 Ω termination. The pilot targets 125, 250, 500 and 1000 kbps.

Turn raw frames into named signals.

Import DBC files and follow J1939 or CANopen workflows in a browser interface that runs on your machine.

18FEF100  7D 00 FF 7A 09 00
Engine speed
sample
Oil pressure
sample

Keep the session. Replay the question.

Capture a run, inspect it later and export the evidence. No mandatory cloud account is part of the planned workflow.

  1. Record00:00
  2. Inspect02:14
  3. Replay04:32

Pilot specification.

These are target requirements from the execution plan. Final performance claims remain subject to EVT/DVT test records.

AreaPilot targetRelease note
InterfaceUSB-C · Classic CAN 2.0CAN FD is not promised for v1.
Bit rates125 / 250 / 500 / 1000 kbpsValidated per test record.
Physical layerIsolation · ESD design · switchable 120 ΩLab path confirmed before sale.
WorkflowsDBC · J1939 · CANopen · record/replayLocal browser interface.
Desktop supportWindows · Linux · macOSCompatibility matrix will name tested versions.

A development tool, with published limits.

The pilot is not a road-repair oracle, a safety controller or a claim to replace every professional CAN instrument.

  • Not intended for safety-critical control.
  • No claim of compatibility with every vehicle or ECU.
  • No promise of professional-instrument timestamp equivalence.
  • Firmware, test records and known issues remain traceable by release.

Two pilot configurations.

Planned prices are shown for validation, not as a public-sale promise. Checkout stays closed until payment, testing and policy gates pass.

Product photography pending EVT hardware. These labelled line drawings are intentionally placeholders, not product renders.

Help define the 50-unit pilot.

Tell us what you need to connect, decode or record. Pilot applicants receive the compatibility matrix, test report and release timing before any payment request.

No card details are collected by this form.

Used only for pilot, compatibility and release updates.

This helps us prioritise the compatibility matrix.

Test results are published against named operating-system versions.

The first MallMars pilot does not promise CAN FD.

Do not upload proprietary databases or traces here.

This is planning data, not a purchase commitment.

Name one testable task. Do not include confidential vehicle, customer or credential data.

Before you apply.

Is this CAN FD?

No. The first pilot targets classic CAN 2.0. CAN FD support is not part of the v1 promise.

Does the analyzer require a cloud account?

No mandatory cloud account is planned. The browser interface is intended to run locally on a supported desktop system.

Can I use it for vehicle repair decisions?

No. It is a development and diagnostic aid, not a safety-certified road-repair instrument or control device.

When will payment open?

Only after the payment gateway, refund path, DVT tests, shipping policy and operator details have all been verified.

Which payment methods are planned?

Stripe card checkout and PayPal are planned through their official WooCommerce extensions. Availability depends on merchant-account approval and region.