OBDVeloce
Coming soon · Windows

A guided run, from measurements to a useful report.

Guided Diagnostic helps you collect supported measurements under guided operating conditions, review their quality and complete a diagnostic run. SmartReport then organises the accepted evidence for review and local PDF export. Engine Fault Scan is a separate way to inspect fault-code evidence.

Check compatibilityRegister interest
Guided Diagnostic

From configuration review to diagnostic follow-up.

These stages explain the guided measurement workflow. Engine Fault Scan is independent: its standard DTC and trusted enhanced Engine ECU coverage does not become a SmartReport automatically. No fault records does not certify vehicle health.

  1. Compatibility

    Check the exact configuration.

    Review the vehicle, model year, engine, market, ECU family, ECU identifiers, adapter and connection method.

    ResultReviewed configuration scope

  2. Connection

    Verify adapter and ECU communication.

    Configure the Windows COM port, confirm adapter response, establish the standard OBD baseline and verify supported Alfa diagnostic communication.

    ResultCapture ready

  3. Diagnostic focus

    Choose one focused capture group.

    Use Core / Standard plus one supported Alfa group for the clearest collection and the most readable report interpretation.

    ResultSelected group

  4. Guided Capture

    Request and record diagnostic values.

    Run the recommended condition and duration while recognised ECU responses are decoded and written into the active local session.

    ResultStructured samples

  5. Local session

    Finalise the local source session.

    Save the session identity, timestamps, selected groups, samples, capture statistics, missing signals and source metadata.

    ResultSource session

  6. Quality review

    Classify the captured evidence.

    Review the result as complete, partial but usable, or insufficient data.

    ResultCapture quality

  7. SmartReport + PDF

    Review accepted evidence from a completed run.

    SmartReport preserves evidence context and limitations. Export the structured report to PDF locally when you need a document to review or share yourself.

    ResultSource-linked report

  8. Follow-up

    Choose the next diagnostic action.

    Review the evidence, repeat a focused capture when useful, compare it with vehicle symptoms and verify mechanically when required.

    ResultInformed next step

Useful reports need usable evidence.

A report cannot repair an unstable connection or replace a measurement the ECU did not provide. Review capture quality and accepted evidence before completing the run; a saved file is not enough on its own.

Stage dependency
  1. Compatibility
  2. Connection
  3. Diagnostic focus
  4. Guided Capture
  5. Local session
  6. Quality review
  7. SmartReport + PDF
  8. Follow-up

Diagnostic evidence collection, not vehicle modification.

Included in the normal workflow

  • Compatibility review
  • Windows COM-port connection
  • Supported standard OBD requests
  • Supported Alfa diagnostic read requests
  • Guided Capture
  • Local diagnostic sessions
  • OBDVeloce JSON sessions can be reviewed locally.
  • Capture-quality classification
  • Deterministic diagnostic reports
  • Source-session traceability

Not part of the normal workflow

  • ECU coding
  • Proxy alignment
  • Injector coding
  • Adaptation writing
  • Actuator control
  • Active testing
  • Forced DPF regeneration
  • Fault-code clearing
  • Tuning or remapping
  • Immobiliser operations
  • Firmware flashing
  • Module programming
  • Automatic repair
Compatibility

Start with the exact vehicle, ECU, market and adapter.

V1 is intended for Giulia and Stelvio 2.2 JTD on Windows. That scope is separate from configuration validation: year, ECU software, market and adapter can change the diagnostic responses available.

Documented reference configuration

Reference
Vehicle
2020 Alfa Romeo Stelvio
Engine
2.2 MultiJet / JTD
ECU
Bosch EDC17C69
Protocol
ISO 15765-4 CAN 29/500
Platform
Windows desktop

Reference evidence: 2020 Stelvio 2.2 JTD, Bosch EDC17C69. Other configurations need review; selecting Giulia or Stelvio does not confirm validation.

What the compatibility review considers

  • Model and year
  • Engine variant
  • Country or market
  • ECU family
  • ECU hardware identifier
  • ECU software identifier
  • OBD protocol
  • Adapter type
  • Connection method
  • Diagnostic behaviour

Possible review outcomes

Configuration review required
Pending
Review required
Pending
Not confirmed
Unverified

Similar names do not guarantee identical diagnostic behaviour. A matching badge, engine displacement, ECU-family label or advertised adapter version may still use different software, emissions logic, available diagnostic signals or adapter behaviour. Compatibility applies only to the reviewed configuration and the current diagnostic scope.

Submit accurate information. Unknown ECU or adapter fields should stay marked as unknown rather than guessed.

Check compatibility

Connection

Verify Windows, the COM port, the adapter and the ECU response.

Guided Capture depends on a stable serial connection and recognised ECU communication. The standard OBD baseline should work before manufacturer-specific Alfa diagnostic values are expected. Normally only one application can control the serial diagnostic adapter at a time.

Connection sequence

  1. Windows detection
  2. COM port
  3. Adapter response
  4. Standard OBD baseline
  5. Alfa diagnostic session
  6. Capture ready
The OBDVeloce adapter connection screen, showing the port configured, the adapter unplugged and baseline signal values waiting for a connected session.
Connection state before an adapter responds. Baseline values stay empty rather than showing placeholder readings.

Expected baseline signals

These confirm recognised standard OBD responses. Actual values are available only during a connected diagnostic session.

  • Engine RPM01 0CConfirms a recognised engine-speed response.
  • Vehicle speed01 0DConfirms a recognised road-speed response.
  • Coolant temperature01 05Confirms a supported coolant-temperature response.
  • Module voltage01 42Confirms supported electrical-system context.

If the serial port is unavailable

  • Close other diagnostic software using the port
  • Close serial terminal software
  • Stop any active Guided Capture
  • Confirm the previous session was finalised
  • Reconnect the adapter when required
Capture ready

Connection and ECU communication verified. A capture group can now be selected.

Diagnostic focus

Choose one focused diagnostic area at a time.

Core / Standard provides the baseline operating context. Adding one supported Alfa diagnostic group gives the selected values more opportunities to be collected and makes capture-quality review easier to understand. Multi-group capture remains available for controlled use, but Core / Standard plus one Alfa group is the recommended diagnostic workflow.

Why focused captures work better

More polling opportunities
Fewer requested signals mean each selected value is checked more often during the session.
Clearer missing-data review
When expected signals are missing, it is easier to tell whether the ECU supports them at all.
More useful report context
Related values are captured together under the same engine condition.
Less transport switching
Focusing on one Alfa group alongside Core requests reduces communication overhead.

Capture modes

  • Core only

    Core / Standard alone.

  • Guided diagnostic

    Core / Standard plus exactly one Alfa group. The recommended workflow.

  • Hybrid experimental

    Core / Standard plus two or more Alfa groups. Controlled use, not the default.

Supported capture groups

  • Core / Standard
  • Turbo / Air
  • Fuel / Injection
  • EGR
  • DPF / Exhaust
  • Oil / Pedal

Group-selection workflow

  1. Keep Core selected
  2. Select one Alfa group
  3. Read the guidance
  4. Confirm safe conditions
Guided Capture

The live cards are a preview. The saved session is the diagnostic record.

Recognised ECU responses are decoded and recorded in a local session. Live cards help you follow collection, but SmartReport uses evidence accepted within a completed Guided Diagnostic run, not whatever happens to be visible on screen.

Live status meanings

Live
Actively receiving and decoding data.
Waiting
Awaiting the first valid response.
Snapshot only
Captured once, not continuously updated.
Review required
Unexpected or missing data that needs attention.

What happens during a capture

Application
Profile, COM port, adapter and ECU check, request, decode, record, track signals.
User
Select, read the guidance, confirm, start, run the duration, stop, review.

What a structured sample records

  • Timestamp
  • Signal identifier
  • Group
  • Value and unit
  • Source command
  • Raw response
  • Sample type

Safe capture conditions

  • Parked where the recommended condition allows it
  • Passenger-assisted when a driving capture is required
  • Controlled environment
  • Stop the capture whenever conditions become unsafe

Do not watch live values or operate the computer while you are driving.

Stopping a capture

  1. Stop
  2. Flush
  3. Summary
  4. Classify
  5. Save

Normal Guided Capture is limited to requesting, decoding and recording. Coding, remapping and repair are not part of it.

Local session

Keep the source measurements available for review.

Stopping a capture saves a structured local session with samples and collection context. A session is a source record; it is not the same as a completed Guided Diagnostic run with accepted evidence for SmartReport.

Session finalisation

  1. Stop request
  2. Flush buffer
  3. Calculate statistics
  4. Write the session file
  5. Return the result

Session identity

  • Session identifier
  • Date
  • Time
  • Source type
Source badges
  • Live
  • Imported JSON

Group and signal statistics

  • Total samples
  • Capture duration
  • Captured signals
  • Missing signals

Local library

Live sessions, imported sessions and saved reports are kept separately. A report never replaces the session that produced it.

Local storage does not automatically provide encryption, backup, access control, secure deletion or protection from other users of the same Windows machine.

Quality review

Missing data is classified instead of hidden.

Capture quality describes the evidence that is available. It does not declare the vehicle mechanically healthy or faulty.

Why a requested signal may be missing

  • The ECU does not support the specific identifier
  • Vehicle state, such as the engine being off during a dynamic request
  • Adapter buffer overflow or timeout
  • Communication protocol limitations

Quality is assessed per group

A session may be complete for Turbo / Air but only partial for DPF / Exhaust if specific pressures were unavailable.

Illustrative next-capture advice

Repeat the capture with the engine at operating temperature to verify the response.

SmartReport + PDF

SmartReport organises accepted evidence from completed runs.

Complete the Guided Diagnostic run and review the evidence accepted for it. SmartReport uses that evidence and its operating context to produce a structured, deterministic report with visible limitations. Local PDF export makes it available as a document; it does not add evidence or resolve missing measurements.

How a report is derived

  1. Completed diagnostic run
  2. Accepted evidence
  3. Operating context
  4. Explicit rules
  5. Structured SmartReport
  6. Local PDF export

The interpretation depends on accepted evidence, context and rule version. AI Analysis is a separate prototype/planned capability, not integrated into production SmartReport or PDF export.

What the report contains

Overall status
The highest-severity finding across the analysed groups.
Capture quality
Whether the evidence collection was complete.
Group findings
Rule-based conclusions for the selected diagnostic area.
Evidence
The explicit signal data used to reach those conclusions.
Missing data
Requested signals the ECU did not provide.
Next capture
Guidance on improving the diagnostic context.

Before relying on a report

No report yet
A saved capture alone does not mean a completed run or an available SmartReport.
Partial report
Some requested groups had insufficient data; the limitations are listed.
Newer evidence
Check which completed run the report describes before comparing it with newer measurements.
Source session unavailable
The original capture file cannot be found.

Reports

Follow-up

The report should lead to a clearer and safer next diagnostic action.

Follow-up begins by reviewing the source evidence and the limits of the capture. A better capture, a symptom comparison or a mechanical inspection is often more useful than repeating the same test without changing the diagnostic context.

Evidence-led next steps

Review the evidence
Examine the signals and statistics that triggered the report's explicit rules.
Repeat a focused capture
Run a new session with modified conditions to check intermittent behaviour.
Compare with vehicle symptoms
Cross-reference the findings with the drivability issues actually observed.
Verify mechanically
Carry out physical inspection based on the collected electronic evidence.

Two illustrative follow-ups — not recorded results

Illustrative DPF follow-up

  1. A hypothetical capture shows a pressure pattern worth checking.
  2. Compare it with engine conditions and observed symptoms; pressure is not exhaust flow.
  3. A qualified inspection may check the sensor and hoses before drawing a conclusion.
  4. The illustration does not establish a failed hose or a blocked DPF.

Illustrative turbo follow-up

  1. The capture ended before the boost request was met.
  2. The evidence is insufficient for a conclusion.
  3. Next-capture guidance recommends a longer duration under load.
  4. The capture is repeated with passenger assistance.

OBDVeloce recommends evidence-gathering steps. It does not prescribe or guarantee a mechanical repair.

Start with the right configuration

OBDVeloce is coming soon.

Follow the launch or express interest in future validation. Registering interest does not grant software or Beta access.

Check compatibilityRegister interest
  • Exact configurations
  • Read-only focus
  • Local sessions
  • Deterministic rules
  • No cloud account required for the current core desktop workflow

Documented reference: 2020 Stelvio 2.2 JTD · Bosch EDC17C69