Local operator · checking session…

Local sign-in identifies the operator on this computer. It does not authorize vehicle writes, DTC Clear, Service Reset, or control of another Run.

Session status is not yet verified.

Local diagnostic workspace

Overview

Check the motorcycle, choose a diagnostic adapter and save evidence locally. This console cannot make permanent changes to motorcycle settings.

API
—
—
Adapters
—
—
Artifacts
—
latest local records
Quick start

Adapter connection

No adapter selected yet.
Safety boundary

Local diagnostics · no permanent motorcycle writes

Connection
loopback only
Vehicle capability
read
Artifact capability
read + generated report output
Web writes
not exposed
Diagnostic adapter workspace

Adapters

Discover, select, test and inspect one exact diagnostic adapter here. Advanced bring-up remains available below without splitting adapter work across another navigation view.

Help & safety
One adapter workspace

Discovery, selection, qualification and inspection stay distinct

Find adapters lists available devices. Set selected saves the exact choice. Test selected checks its connection; Inspect selected checks more capabilities. q4t never silently picks another adapter.

Discovery vehicle requests
0
Adapter test vehicle requests
0
Complete inspection vehicle requests
0
Automatic fallback
never
Adapter identity: Bluetooth uses the provider-reported device name. USB serial discovery uses passive host USB/PnP metadata when available, so a device-reported product name can be shown instead of a blind COM/tty label. q4t does not open arbitrary serial ports during discovery.
Persistent exact selection

Selected adapter

No adapter selected
Provider/ID: —

Test is the fast qualification path. Inspect is the complete Adapter Inspect v2 inventory. Link-layer actions are off by default; ordinary inspection sends zero vehicle application requests and performs zero persistent writes. Neither action changes the persistent selection.

Candidate discovery

Find diagnostic adapters

Cached is passive. Discover is bounded and still sends zero vehicle diagnostic requests.

Selected adapter state

Connection checks

No adapter selected

Your selected adapter stays saved after a page reload. Pairing alone does not confirm the connection, transport or diagnostic protocol; each check has its own result.

Complete Adapter Inspection

Adapter identity and connection capabilities

0 vehicle requests

Inspect selected checks identity and connection capabilities. Optional link-layer actions require a fresh explicit choice. Normal inspection sends no motorcycle diagnostic requests and does not change stored motorcycle settings.

Select an adapter and choose Inspect selected to collect the complete q4t-adapter-inspection/v2 evidence inventory.
Candidates

Detected adapters

Advanced adapter diagnostics / bring-up
Bounded transport bring-up

Advanced adapter diagnostics

Adapter-only is the default. Optional shallow service identify is the only part of this section that may add disclosed vehicle diagnostic requests.

Advanced help & safety
Before you run

Review the authoritative request plan

The default bring-up is adapter-local only. Enabling shallow service identify may add vehicle requests, but the exact conditional plan and request count are shown before the Run starts. Manual SecurityAccess and persistent writes are never exposed here.

Default vehicle requests
0
Shallow identify
optional, plan disclosed first
SecurityAccess control
not exposed
Persistent write
not permitted
Operation context

Selected adapter and safety boundary

Local · bounded
Selected adapter
No adapter selected
Provider/ID: —
Default vehicle requests
0
SecurityAccess
not permitted
Persistent write
not permitted
Authoritative Application plan

Adapter-local operations

    Vehicle request disclosure

    Optional shallow identify

    Adapter-only plan · 0 vehicle diagnostic requests
      Use the persistently selected adapter, review the exact request plan, then run advanced adapter diagnostics.
      Run events
      Read-only workflow

      Vehicle status

      Read current vehicle status with the selected adapter. Temporary diagnostic access may be used, but no motorcycle settings are permanently changed.

      Help & safety
      Read-only status contract

      The backend owns the complete status Run

      Read status starts the existing typed status workflow on the exact selected adapter. q4t owns diagnostic setup, any profile-required transient access, result classification, and cleanup; the browser does not construct vehicle requests or choose a write path.

      Vehicle operation
      read-only
      Session / access
      backend-owned and reported in the result
      Persistent write
      never
      Browser protocol ownership
      none
      Select an adapter and start a status read.
      Run events
      Bounded ECU information

      Vehicle / ECU

      Read bounded engine ECU information. q4t may open an extended diagnostic session and use temporary SecurityAccess for these reads; it does not change stored ECU data or reveal security keys.

      Help & safety
      Bounded ECU readout

      Profile-selected access is transient and read-only

      The typed ECU Readout workflow may enter an extended diagnostic session and perform the established profile-selected SecurityAccess required for bounded reads. Seed/key material remains backend-private and no persistent ECU data are modified.

      DID / session plan
      backend profile-owned
      SecurityAccess
      may be transiently attempted
      Seed / key exposure
      never through Web API
      Persistent write
      never
      Vehicle data
      Read-only
      bounded profile-selected DIDs
      Diagnostic access
      Transient
      extended session + SecurityAccess
      Persistent writes
      None
      no ECU data are modified
      SecurityAccess here is a transient read-access step selected by the established reference engine profile. Seed/key material is never exposed through the Web API.
      Select an adapter and read the bounded ECU information profile.
      Run events
      Community evidence workflow

      Deep Scan

      Find responding vehicle modules with fixed read-only checks while the motorcycle is parked. The scan produces local evidence and a privacy-reduced Share file; nothing is uploaded automatically.

      Help & safety
      Bounded discovery and evidence

      Park the motorcycle while the backend owns the scan

      The browser cannot choose CAN identifiers, diagnostic bytes, target ranges, sessions, SecurityAccess, retries or write controls. q4t owns the exact bounded request plan. The current Deep Scan performs discovery and default-session characterization only; it does not perform DiagnosticSessionControl, SecurityAccess, persistent writes or programming.

      Motorcycle state
      parked / stationary during the scan
      Request plan
      backend-owned fixed read-only allowlist
      Maximum request ceiling
      3436 vehicle requests
      Live progress
      6 backend stages + current target / transmitted-request counters
      Evidence
      one acquisition → Local + Share artifacts
      Remote upload
      none; Share is derived locally and downloaded explicitly
      Browser disconnect
      does not cancel the backend Run; recover it in Recent runs
      Cancel
      requests bounded backend cancellation; partial evidence is finalized when possible
      Scope
      Bounded discovery
      11-bit + 29-bit responder census
      Hard ceiling
      3436
      theoretical maximum vehicle requests
      Evidence
      Local + Share
      same acquisition, offline privacy transform
      Keep the motorcycle stationary during Deep Scan. This is not a ride capture. The Share artifact is the community-safe file intended to send to the project; q4t does not upload it automatically.
      Select an adapter and start a Deep Scan.
      Run events
      Backend-owned ride evidence

      Capture

      Record motorcycle traffic in PASSIVE mode, or collect bounded read-only diagnostics with TELEMETRY/MIXED after explicit consent. The selected adapter and evidence stay with the backend Run; closing this page does not stop an active Capture.

      Help & safety
      Ride capture boundary

      PASSIVE is zero-diagnostic while moving; TELEMETRY and MIXED are active read-only research modes

      PASSIVE listens to vehicle traffic and must keep diagnostic requests while moving at zero. TELEMETRY and MIXED deliberately issue bounded read-only diagnostic requests during the ride and therefore require an explicit acknowledgement. None of the three modes authorizes a persistent write.

      Run owner
      backend; browser disconnect is not STOP
      Adapter
      exact saved adapter; no automatic replacement
      PASSIVE moving diagnostics
      0 required
      TELEMETRY / MIXED
      active read-only research diagnostics while moving
      Orderly STOP
      only after the motorcycle is parked and stationary
      Persistent vehicle write
      not exposed
      Start a new capture

      Capture policy

      Resume after interruption

      Explicit checkpoint resume

      Resume requires the same saved adapter and mode as the checkpoint. A mismatch is rejected; q4t never switches to another adapter.

      Orderly ride completion

      STOP unlocks stationary post-capture checks

      No active Capture Run
      Do not use STOP while moving. STOP ends ride collection and permits the backend to perform the configured stationary read-only post-capture finalization. Emergency Run cancellation remains a separate backend concept and is not exposed here.
      Select an adapter and start PASSIVE, TELEMETRY or MIXED capture.
      Run events
      Combined read-only workflow

      Diagnostic report

      Create a diagnostic report from one bounded vehicle read. q4t produces a private Local report and a privacy-reduced Share report from that same read, without a second diagnostic session or automatic upload.

      Help & safety
      Acquisition and artifact ownership

      One vehicle acquisition produces both report variants

      Create report uses one backend Run, one exclusive vehicle lease and one adapter session. After that acquisition finishes, q4t publishes the Local artifact and derives the Share artifact offline; sharing never re-acquires the vehicle or performs a second diagnostic read.

      Vehicle acquisitions
      1
      Local + Share
      same typed acquisition
      Share transform
      offline privacy transform
      Persistent write
      never
      Vehicle operation
      Read-only
      no DTC clear or ECU write
      Diagnostic access
      Transient
      extended session + SecurityAccess
      Evidence output
      Local + Share
      two immutable artifacts from the same acquisition
      One vehicle acquisition automatically creates both a Local report and a VIN/adapter-masked Share report. Share is an offline privacy transform and performs no second vehicle read. Both documents embed scoped SHA-256 integrity metadata; Artifact Store separately retains the exact blob SHA-256. Nothing is transmitted remotely.
      Select an adapter and create a diagnostic report.
      Run events
      Read-only workflow

      Diagnostic trouble codes

      Reads pending and confirmed DTCs (fault codes). Manufacturer descriptions appear only when the exact module and profile are qualified; otherwise the meaning remains unknown. This page cannot clear fault codes.

      Help & safety
      DTC evidence

      Pending and confirmed records stay read-only

      The typed DTC workflow reads pending and confirmed records and preserves raw wire truth separately from semantic evidence. Qualified manufacturer descriptions are additive, profile/module scoped, and this Web view exposes no DTC-clear operation.

      DTC clear
      not exposed
      Session / SecurityAccess
      may be transient if the profile requires it
      Unknown description
      remains unknown
      Persistent write
      never
      Observation only: this Web view has no DTC-clear control and exposes no service-write capability. A read may use transient diagnostic-session/SecurityAccess steps required by the selected profile, but it does not attempt a persistent write.
      No DTC read has been started.
      Run events
      Live data dashboard

      Sensors

      Select sensors for one read or a timed watch while parked. q4t collects readings and updates live cards and graphs; the browser does not generate vehicle polling requests.

      Help & safety
      Sampling ownership

      The backend owns polling, limits and diagnostic access

      One-shot reads and timed watches use the existing typed Sensor Run. The backend owns the vehicle session, diagnostic interval, duration and the maximum-eight watch bound; SSE only carries Run state/readings to the browser and does not turn JavaScript into a vehicle polling engine.

      Watch selection
      maximum 8 sensors
      Polling owner
      backend Sensor Run
      SecurityAccess
      backend profile-selected when required
      Persistent write
      never
      Stationary use only. The backend owns the Run lifetime, diagnostic interval and vehicle session. Closing or reloading this browser does not authorize a write and does not turn the browser into a diagnostic polling engine.
      One-shot read

      Selected sensor definitions

      0 selected
      Timed watch

      Timed sensor watch

      Maximum 8 selected sensors per watch Run. Duration and interval remain backend-bounded.
      Sensor dashboard and final typed results will appear here.
      Run events
      Read-only service checks

      Service

      Identify the service system or read more detailed service information. Detailed checks may use temporary diagnostic access; this page cannot reset the service interval or change stored motorcycle settings.

      Help & safety
      Choose the read depth

      Identify is shallow; characterize is deeper but still read-only

      Identify family never attempts SecurityAccess. Characterize read-only may use the profile-selected transient SecurityAccess needed for established read-only records. Neither action exposes service reset, service-date write, or any other persistent mutation.

      Identify SecurityAccess
      never
      Characterize SecurityAccess
      may be attempted
      Persistent write
      never
      Write eligibility result
      evidence only, no Web authority
      Shallow identify

      Family fingerprint

      Checks C1 first and falls back to bounded Legacy identification only when no usable C1 endpoint evidence exists.

      Persistent write
      never
      SecurityAccess
      not permitted
      Session change
      may be transient
      Deeper characterize

      Read-only capability evidence

      For a recognized C1 family this may perform the profile-selected SecurityAccess and strict A500/A000/A010 reads. Legacy characterization remains bounded and read-only.

      Persistent write
      never
      SecurityAccess
      may be attempted
      Secret material
      never exposed by Web API
      Stationary use recommended. A characterization result can report whether the underlying service family is compatible with a separate write workflow, but that is evidence only: this Web surface still has no service-reset control, no service-write capability, and no way to authorize a persistent mutation.
      Select an adapter, then identify or characterize the service family.
      Run events
      Immutable local evidence

      Artifacts

      Browse and download evidence saved on this computer. Local records may contain private diagnostic information; nothing is uploaded automatically.

      Persistent evidence store. Artifacts are read from q4t's Artifact Store, not from the directory containing this executable. The default is ~/.q4t/artifacts (on Windows, %USERPROFILE%\.q4t\artifacts) and it is shared by CLI/Web and across q4t versions. Deleting downloaded JSON files, logs, or an older executable directory does not delete immutable Artifact Store records. Uncheck the current-version filter to inspect historical records.
      Backend-owned lifecycle

      Recent runs

      Review previous operation results after a disconnect or reload. You can request cancellation of an active Deep Scan here; all other operations are for viewing only.

      Operator instructions · display only

      Operator guidance

      Display only · unavailable

      This browser cannot submit operator decisions or authorize vehicle changes. Backend interaction is disabled pending separate security qualification.

      No operator prompt is available in this browser.
      Operator panel safety and access

      Instructions are display-only. A browser is not proof of local presence. Never use this panel while riding. Opening or closing this help does not acknowledge, cancel or change a backend Run.

      Local result file · read-only

      DTC Clear / Service Reset results

      Open a JSON result exported by q4t dtc clear --result-json FILE or saved by q4t service reset. The file is read inside this browser; it is never uploaded to q4t or sent to the motorcycle. This view cannot clear DTCs or reset the service interval.

      Select a saved result to see host transmission, ECU acknowledgement, readback and process HOLD separately.
      Select a recent Run to inspect its retained state and events.
      Project legal information

      About & licence

      Copyright, licence and warranty notices for the q4t build currently serving this Web interface.

      Project

      Quest4Triumph Project

      Application
      q4t
      Version
      —
      Copyright
      Legal notice

      AGPL-3.0-only

      Complete licence text

      GNU Affero General Public License version 3

      Loading licence text…