Connect

Choose a passive data source. Hardware transports normalize into the same CAN frame pipeline as imported captures and the simulator.

Adapter

OFFLINE

Transport

Built-in profiles appear automatically for the selected transport. Choose a profile, then connect. Advanced Mode exposes driver UUIDs, framing, serial baud, and other low-level settings.

Adapter driver

USB PROFILE

CAN bitrate

Frame mode

Serial baud

Channel label

Mode

No hardware activity occurs until you choose CONNECT. Simulator mode is entirely local and marked SIMULATED.

Capabilities

GENERIC

Frames / sec

0

rolling 1 s window

RX frames

0

current session

Bus load

0%

estimated

Parser errors

0

transport parser

Connection guide

Observe first.
Use a CAN adapter that supports listen-only where possible. ROADWIRE starts in passive mode and does not transmit arbitrary CAN frames.

Check the physical layer.
CAN-H, CAN-L and reference ground must be correct. Vehicle networks may use manufacturer-specific connectors or multiple buses.

If there are no frames.
Check ignition state, bitrate, termination, wiring and whether the selected adapter is actually configured for listen-only reception.

Release readiness

CHECKING

Preflight never transmits CAN frames. It checks browser capabilities, storage, project integrity and the selected transport configuration.

Live Traffic

Windowed frame rendering, collapsed ID analysis, persistent change tracking and a detailed message inspector. Pausing or freezing the view never stops capture processing.

Frame stream

Message inspector

Select a CAN identifier from FRAMES or IDS.

Chart

A focused live plot for the values you care about. Raw bytes can be plotted directly from LIVE DATA; decoded signals appear here when they exist.

Quick charting
Select one or more decoded signals below. If no signals are defined, go to LIVE DATA, select a CAN ID, and choose PLOT BYTES. Advanced Mode exposes signal definition and DBC tools.

Signal plotter

Shared live timeline · last 60 s

Record

Capture traffic and mark physical events so changes can be correlated with what happened to the vehicle.

Capture state

IDLE

Frames

0

Duration

0.0s

Events

0

Capture storage

Calculating…

Frames are committed in 2,000-frame chunks. Live rendering remains bounded independently of recording.

Quick markers

Capture timeline

Saved captures

Name	Role	Started	Duration	Frames	Events	Tags	Storage	Actions

CHANGE

Guided reverse-engineering workflow: establish a baseline, perform one physical action, compare captures, then rank the messages and bits most associated with that action.

01 · BASELINE

Record the vehicle before the action.

02 · ACTION

Perform only the action you want to isolate.

03 · CAPTURE

Record the changed state or action.

04 · RANK

ROADWIRE ranks candidates; it does not claim semantic meaning automatically.

Baseline capture

Changed / action capture

Candidate ranking

Choose two captures.

Rank	Score	ID	Status	Rate Δ	Changed bytes	Changed bits	Why it ranked

Candidate detail

Run CHANGE, then select a candidate.

Signals

Advanced signal-definition workbench. Define and validate physical values here; use CHART for routine live visualization.

Signal definitions

0 SIGNALS

Name	Channel	ID	Bits	Encoding	Scale	Range	Unit	Confidence	Live

Selected signal

Select or create a signal.

Signal Library

Durable vehicle knowledge: definition + provenance + evidence + lifecycle + revision history. Decoder rows become traceable engineering objects rather than isolated bit definitions.

Signals

0

Confirmed

0

Revisions

0

Library baselines

0

Engineering signal library

Name	State	Channel	ID	Bits	Unit	Node	Confidence	Evidence	Rev	Updated

Library object

NONE

Select a signal from the library.

Library baselines

Compare

Compare two recorded captures to find identifiers, rates and payload bytes that changed between vehicle states.

Capture A · baseline

Capture B · changed

Differences

ID	Status	DLC A/B	Rate A	Rate B	Rate Δ	Changed bytes	Changed bits	Range shifts	Evidence

Test Laboratory

Structure repeatable vehicle-network experiments as QUESTION → SETUP → BASELINE → ACTION → CAPTURE → ANALYSIS → RESULT. Trials remain linked to captures, evidence and conclusions.

01 · QUESTIONWhat are you trying to learn?

02 · SETUPRecord vehicle state and test conditions.

03 · BASELINECapture the unmodified state.

04 · ACTIONPerform one controlled action.

05 · ANALYSISCompare trials and inspect repeatability.

06 · RESULTRecord conclusion and supporting evidence.

Test sessions

0

Selected session

NO SESSION

Create or select a test session.

Trial comparison

Repeatability uses capture duration, frame count and event-marker consistency as session-level indicators.

A session with two or more completed trials will show repeatability statistics here.

Dashboard Studio

Build reusable field dashboards from signals, raw messages and test-session state. Drag to reorder, resize widgets, save multiple layouts, then open a stripped-down Field Mode.

Studio

Dashboard layout

LAYOUT

Drag widgets to reorder. W cycles through compact / wide / full-width. Widget settings stay entirely inside the local ROADWIRE project.

Evidence Graph

Trace conclusions back through signals, hypotheses, nodes, tests, captures, findings and diagnostic evidence. Derived relationships are shown separately from explicit project links.

Graph nodes

0

Relationships

0

Evidence items

0

Orphan evidence

0

Evidence topology

Graph Inspector

Select a graph object.

Relationships

Explicit links are authored by the user. Derived links come from existing ROADWIRE object references.

From	Relationship	To	Origin	Confidence	Evidence / rationale

Vehicle State Model

Build a higher-level vehicle state only from explicitly selected decoded signals. Confirmed Signal Library objects are preferred; ROADWIRE keeps the source signal and evidence visible.

State definitions

0

Confirmed sources

0

Live values

0

Unresolved

0

Current vehicle state

Derived locally from selected ROADWIRE signals.

State model definitions

Vehicle state	Signal	Source status	Mapping	Evidence

Session Playback

Replay a recorded capture virtually through ROADWIRE's decoded-signal and vehicle-state model. Playback never transmits the capture to a physical CAN bus.

Playback controls

IDLE

00:00.000

Virtual playback updates decoded signals and the state model only. It does not call a hardware transmit path.

Playback vehicle state

Playback events

Load a capture.

Vehicle Behavior Timeline

Transform decoded state changes and recorded event markers into a higher-level chronological narrative. Every derived transition retains its source signal.

Behavior events

0

State transitions

0

User markers

0

Duration

—

Chronology

Choose a capture and build the behavior timeline.

Anomaly Detection

Compare a capture against a saved ROADWIRE baseline for unexpected message inventory, timing, signal-range and state-transition behavior. Results are findings candidates, not automatic diagnoses.

Candidates

0

High

0

Medium

0

Low / info

0

Anomaly candidates

Promote individual candidates into the normal Findings register after engineering review.

Severity	Category	Object	Baseline	Observed	Confidence

Message Family Detection

Cluster observed CAN messages by timing, payload length, byte-change pattern and known node context. Families are behavioral candidates, not asserted ECU ownership.

Families

0

Messages

0

High confidence

0

Unclustered

0

Candidate message families

Similarity uses observable behavior only.

Family	Members	Channels	DLC	Rate / timing	Confidence	Rationale

Redundant Signal Detection

Find decoded signals on different messages or buses that track the same underlying behavior. ROADWIRE estimates correlation, lag, scale and offset without declaring that the signals are semantically identical.

Candidates

0

Cross-bus

0

Correlation ≥ .95

0

Median lag

—

Candidate redundant signals

Signal A	Signal B	Correlation	Lag	Transform A→B	Confidence

Gateway Transformation Discovery

Investigate cross-bus signal relationships that may represent forwarding, rescaling, offsetting, quantization or update-rate conversion. Results remain gateway candidates until independently supported.

Candidates

0

Near copies

0

Scaled / offset

0

Strongest fit

—

Cross-bus transformation candidates

Source	Destination	Fit	Lag	Scale	Offset	Type

External Instrumentation

Import timestamped logic-analyzer, oscilloscope, GPS and IMU measurements as local engineering references. ROADWIRE preserves source timing and never claims synchronization accuracy beyond the imported data.

Datasets

0

Samples

0

Reference channels

0

Latest span

—

Imported datasets

Original rows remain local in the project. Time offset is applied only when creating aligned reference channels.

Name	Type	Samples	Columns	Time base	Offset	Imported

Dataset inspector

Import or select a dataset.

GPS / IMU Data Fusion

Align external motion/reference channels with recorded CAN signals and measure their relationship. Alignment offsets are explicit project data—not hidden corrections.

Capture

CAN signal

External reference

Search lag ± ms

ALIGNMENT DISCIPLINE

ROADWIRE reports the best observed lag and correlation. Clock offset, sample rate and sensor latency remain potential sources of error.

Fusion result

NO ANALYSIS

Choose a capture, decoded signal and external reference.

Signal	Reference	Correlation	Lag	Scale	Offset	Samples	Confidence

Saved fusion runs

Signal	Reference	Correlation	Lag	Created

Engineering Review Queue

Review hypotheses, node assignments, state models, findings and dependency links without changing their underlying technical state. Review disposition is a separate engineering record.

Queued

0

Open

0

Accepted

0

Rejected

0

Review queue

Type	Object	Technical state	Review	Reviewer	Updated

Assumption Register

Keep assumptions visibly separate from observations and confirmed conclusions. Track impact, confidence, validation method, evidence and disposition.

Assumptions

0

Unverified

0

High impact

0

Validated

0

Assumptions

Statement	Category	Impact	Confidence	Status	Owner	Evidence

Project Audit Trail

Chronological record of meaningful project actions. Audit entries are append-only through normal ROADWIRE workflows and are included in Vehicle Knowledge Packages.

Entries

0

Review actions

0

Assumption actions

0

Last activity

—

Audit events

Time	Category	Action	Object	Details

Investigation Report Builder

Generate focused engineering reports from the same evidence-backed project model. Report content is assembled locally and preserves limitations, confidence and provenance.

Report configuration

Report type

Title

Prepared by

Purpose / scope

Assumptions / limitations

Include evidence register Include project history Include assumption register

Saved report definitions

Preview

NOT GENERATED

Choose a report type and generate a preview.

Report

Print-friendly engineering summary of the current project, message inventory, captures, decoded signals and evidence.

Vehicle Network Map

Evidence-backed topology of buses, hypothesized nodes, observed messages and decoded signals. ROADWIRE never infers ECU ownership solely from arbitration ID.

BUS → NODE → MESSAGE → SIGNAL

0 NODES

Map Inspector

Select a node on the map.

ECU / Node Workbench

Organize observed traffic into explicit node hypotheses. Assign messages only when you have evidence; track confidence, notes and supporting evidence independently.

Nodes

0

Node Inspector

Create or select a node.

CAN Activity Atlas

A visual survey of the 11-bit identifier space. Each tile covers eight CAN IDs and shows observed density/activity while preserving known/unknown and node-assignment context.

11-bit ID space · 0x000–0x7FF

0 ACTIVE IDS

Each tile = 8 IDsNumber = active IDs in tileHigher fill = more activityOutline = selected tile

Atlas Detail

Channel	ID	Node	Rate	Count	Changed	DBC / Signals

State Machine Discovery

Characterize discrete or quasi-discrete decoded signals as observed states and transitions. Results are candidate behavioral models until confirmed by repeated testing.

Capture

Decoded signal

State tolerance

OBSERVED, NOT NAMED

ROADWIRE groups observed values and transitions. A cluster is not automatically PARK, DRIVE, DOOR OPEN, etc. until evidence supports that meaning.

Candidate state model

NO ANALYSIS

Choose a capture and signal, then run discovery.

Saved behavioral models

Name	Signal	States	Transitions	Confidence	Evidence

Event Explorer

Ask what changed across the vehicle network around a marked event. Compare the pre-event and post-event windows without assigning semantic meaning automatically.

Capture

Event marker

Before · ms

After · ms

Event summary

NO ANALYSIS

Select a capture containing event markers.

Network changes around event

Rank	Channel	ID	Before	After	Rate Δ	Payload change	Node

Dependency Graph

Document evidence-backed behavioral relationships between signals, messages, nodes and events. Edges remain hypotheses with explicit confidence and provenance.

Behavior graph

0 LINKS

Relationship inspector

Select a relationship.

From	Relationship	To	Lag	Confidence	Evidence

Pattern Classifier

Classify observed fields by behavior: static, toggle, enum-like, ramp, sensor-like, counter-like, periodic heartbeat, or high-entropy integrity candidate. Classification is descriptive, not semantic.

Capture

Channel

Minimum samples

BEHAVIOR, NOT MEANING

A smooth ramp may be sensor-like, but ROADWIRE will not label it speed, temperature, steering, etc. without a test or trusted reference.

Classifier summary

NO ANALYSIS

Choose a capture and classify its observed fields.

Rank	Channel	ID	Field	Pattern	Score	Unique	Change	Notes

Guided Signal Discovery

Define the signal you are trying to find, select a capture and optional trusted reference, then rank candidate encodings. Results remain hypotheses until repeated testing confirms them.

Question / target

Capture

Trusted reference

Channel

GUIDED EXPERIMENT

Best results come from controlled captures with repeated changes and a known reference such as OBD-II speed, RPM, GPS speed, or a manually measured quantity.

Discovery result

NO ANALYSIS

Describe the target and run discovery.

Rank	Channel	ID	Candidate	Encoding	Fit	Scale	Offset	Evidence

Saved discovery runs

Target	Capture	Reference	Candidates	Best fit	Created

Encoding Solver

Test common integer layouts, endian conventions, signedness, and linear scale/offset models against a trusted reference—or rank them by smoothness when no reference exists.

Capture

Observed message

Trusted reference

Maximum field width

Solver summary

NO ANALYSIS

Choose a capture and observed message.

Rank	Field	Endian	Signed	Score	Scale	Offset	Range

Counter & Checksum Detection

Identify likely rolling counters and simple checksum/integrity fields from recorded traffic. ROADWIRE characterizes observed behavior only; it does not generate or transmit physical bus payloads.

Capture

Channel

IDENTIFICATION ONLY

Detection covers counters plus simple XOR/additive checksum relationships and checksum-like high-entropy fields. It intentionally does not create transmit-ready frames.

Integrity summary

NO ANALYSIS

Analyze a capture to find likely integrity fields.

Rank	Channel	ID	Byte / nibble	Candidate	Score	Observation

Bit Matrix

Click-drag contiguous bit ranges. ROADWIRE previews little-endian and big-endian interpretations, tracks bit activity, and can turn the selection directly into a candidate signal.

CAN ID

SELECTION

—

BITS

0

INTEL / LE

—

MOTOROLA / BE

—

SELECTED RANGE HISTORY

Payload bit matrix

classic: 64 bits · CAN FD: up to 512 bits · outline = selected

Timing

Period, frequency and jitter are calculated incrementally from observed frames.

Channel	ID	Count	Avg period	Min	Max	Jitter	Frequency

Correlation

Compare a decoded CAN signal with a known reference channel. Metrics are evidence aids—not automatic declarations of signal meaning.

Capture

Candidate signal

Reference channel

Correlation metrics

No analysis yet.

Candidate ↔ Reference

Choose a capture, signal and reference channel.

Reference channels

Name	Type	Samples

Engineering Timeline

Synchronized capture activity, decoded signal traces and event evidence. Click twice on the plot to place measurement cursors.

Capture

Signal overlay

Range start %

Range end %

CURSORS —

Full capture

Capture timeline

Choose a capture.

DBC Workbench

Import, inspect and author CAN database definitions, then compare observed traffic against the database expectation.

Messages

0

Signals

0

Nodes

0

Enums

0

Search messages / signals / nodes

Messages

No DBC loaded

Message inspector / authoring

Import a DBC or create a message.

Nodes

DBC browser

No nodes.

Enumerations

Value tables

Message	Signal	Values

Signals

Database signal registry

Message	Signal	Bits	Encoding	Scale / offset	Range	Unit

Observed ↔ DBC overlay

No database loaded.

ID	DBC message	Observed	Expected DLC	Observed DLC	Status	Out-of-range signals

DBC Engineering Suite

Validation · revision comparison · traffic conformance

Validation is a screening aid. Motorola/complex bit layouts and manufacturer conventions may require manual engineering review.

DBC Validation

NOT RUN

Severity	Object	Issue

Revision Comparison

NO COMPARISON

Type	Object	Change

DBC ↔ Observed Traffic Validation

NOT RUN

Severity	Channel	ID	Message	Issue

Baselines & Drift

Freeze a capture-derived message/signal inventory, then compare revisions, repairs, temperatures, or firmware states without overwriting the evidence.

Named baselines

0

No baselines.

Compare baselines

Baseline A

Baseline B

Drift result

Choose two baselines.

ID	Change	A	B	Severity	Finding
No comparison run.

Findings

Formal review items generated from baseline drift and diagnostics. Severity describes consequence; confidence describes evidential strength.

Severity	Confidence	Category	Finding	Status	Evidence

OBD-II Diagnostics

Read-oriented standardized diagnostics: live PIDs, readiness, freeze-frame context, vehicle information, DTC recurrence and before/after repair comparison. Separate from raw CAN observation.

Diagnostic source

READ ONLY

Source

Serial baud

Poll interval

Reference capture

ROADWIRE sends only explicit read-oriented diagnostic requests. Mode 04 clear-DTC, security access, coding and write services are not implemented.

Adapter

Source

NONE

Protocol

—

Requests

0

Errors

0

Diagnostic trouble codes

Not read

Code	State	Description	Evidence
No DTC snapshot.

Reference recording

While live PID polling runs, ROADWIRE keeps timestamped samples for correlation with captured CAN traffic. Save those samples as project reference channels when the test is complete.

Readiness monitors

NOT READ

Read Mode 01 PID 01 to inspect MIL status and standardized monitor readiness.

Vehicle information

MODE 09

VIN / calibration identifiers have not been read.

Freeze-frame context

MODE 02

No freeze-frame snapshot.

DTC recurrence

0 SNAPSHOTS

Repeated DTC reads will build a local recurrence history.

Diagnostic baselines

Baseline A

Baseline B

Save before/after diagnostic states to compare DTCs, readiness and standardized PID values.

Hypotheses

Keep proposed meanings separate from confirmed signal definitions.

Proposed meaning	ID	Bits	Status	Confidence	Tests	Evidence

Evidence

A traceable register linking observations, captures, event markers and test results to engineering conclusions.

Type	Label	Reference	Linked hypothesis	Created	Notes

Transport

Adapter-driver registry, saved hardware profiles, diagnostics and normalized-frame transport state.

Adapter profiles

BLE profiles

Runtime

Connection Doctor

Run diagnostics to inspect the selected transport. The doctor never sends CAN frames.

Last parser / adapter messages

ROADWIRE Gateway

Versioned local bridge for CAN hardware that browsers cannot access directly. Gateway control is receive-only: CONFIGURE and START may initialize listen-only capture, but FRAME_TX is not accepted by ROADWIRE.

Saved endpoints

RWG/1.1

Active gateway

OFFLINE

Protocol—

Gateway—

RTT—

Sequence gaps0

Capabilities

Connect to a ROADWIRE Gateway endpoint.