OBDVeloce
Support and troubleshooting

Find the stage. Review the evidence. Prepare a useful request.

OBDVeloce is coming soon. Use these guides to understand connection, Guided Diagnostic and SmartReport/PDF. Engine Fault Scan is separate: standard DTCs and trusted supported enhanced Engine ECU coverage only. No records does not confirm a healthy vehicle.

Check compatibilityRegister interest

Where did the workflow stop?

  1. Adapter and connection
  2. Guided Capture
  3. Sessions and imports
  4. Diagnostic reports
  5. Vehicle compatibility
  6. Feature availability

This page is reference guidance. It does not open a support case, and no request is sent from here.

Support routing

Isolate the stage before describing the symptom.

Start with the area that matches what you were doing. Connection, saved evidence and reporting have different checks; not every feature is a step in one automatic sequence.

  1. Adapter and connection

    Stage 1

    Is Windows detecting the adapter, and is the COM port available?

  2. Guided Capture

    Stage 2

    Does the ECU respond, and does the selected group collect recognised data?

  3. Sessions and imports

    Stage 3

    Can the saved or imported session be opened and classified?

  4. Diagnostic reports

    Stage 4

    Does SmartReport reflect the accepted evidence from the completed run?

  5. Vehicle compatibility

    Stage 5

    Do the exact vehicle, ECU, protocol and adapter match the reviewed scope?

  6. Feature availability

    Stage 6

    Is the feature part of the current product or a separate prototype?

A later stage rarely explains an earlier failure. If standard OBD communication never succeeded, the report is not the problem to investigate.

Support areas

Six areas, each with a real destination.

Choose the relevant guide for the task or message you are seeing.

Adapter and COM port

Check physical connection, Windows device recognition, the assigned COM port and whether another application is using it.

Common questions
  • Windows does not list the adapter
  • COM port not found or already in use
  • The connection drops during a capture

Adapter and setup guidance

Guided Capture

Choosing capture groups, running supported read requests and verifying that the ECU responds.

  • No response from the ECU
  • Signals remain in the waiting state
  • Which operating condition to use

How It Works

Sessions and imports

OBDVeloce JSON sessions can be reviewed locally.

  • A session is not listed
  • OBDVeloce JSON
  • An import was classified as insufficient

Frequently asked questions

Diagnostic reports

Reading a deterministic report, and understanding missing data and stated limitations.

  • The report shows partial findings
  • A report section is missing
  • The source session is unavailable

Diagnostic reports

Vehicle compatibility

Whether an exact Alfa Romeo configuration, ECU and adapter fall inside the reviewed scope.

  • Which engines are currently reviewed
  • Which adapter configuration is required
  • How to identify the ECU

Compatibility check

Current and planned features

AI Analysis is a separate prototype/planned capability. It is not integrated production functionality; SmartReport/PDF uses deterministic processing.

  • Engine Fault Scan coverage
  • Completed Guided Diagnostic runs
  • AI Analysis prototype boundary

Product overview

Product guidance does not provide coding, clearing, repair or remote access services.

Connection checklist

Five checks, in dependency order.

Check the first incomplete connection stage and note the exact message. This helps narrow the issue without assuming its cause.

  1. Windows detection

    Windows lists the adapter as a serial port with an assigned COM number.

    Typical symptomNo COM port is offered

  2. Port availability

    No other application is holding the same COM port open.

    Typical symptomAccess to the port is denied

  3. Adapter response

    The adapter answers basic initialisation before any vehicle request is sent.

    Typical symptomThe adapter does not answer

  4. Standard OBD communication

    Supported standard OBD requests return recognised responses.

    Typical symptomRequests return no data

  5. Alfa-specific communication

    Where available, manufacturer-specific diagnostic-session setup and supported read requests are accepted.

    Typical symptomThe session request is rejected

Confirm the vehicle is in the state the capture instructions require, and do not begin driving until the setup is stable and the instructions permit it.

A working connection confirms communication, not coverage. Not every signal is available on every configuration, and not every connection problem originates in the adapter.

Guided Capture troubleshooting

Read the capture result before repeating the test.

Core / Standard is always foundational. Guided Diagnostic normally combines Core / Standard with one focused Alfa group. Hybrid Experimental remains available for controlled use but is not the recommended default.

Capture quality classifications

Complete
The required recognised data for the selected group was captured.
Partial but usable
Some requested signals are missing, but useful recognised evidence remains available. This is not a failed capture.
Insufficient data
Too little recognised group data exists for useful deterministic interpretation. A better source session is needed.

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

Recommended duration by group

  • Core / Standard30–60 seconds
  • Turbo / Air60–90 seconds
  • Fuel / Injection60–90 seconds
  • EGR60–90 seconds
  • DPF / Exhaust60–90 seconds
  • Oil / Pedal30–60 seconds

Durations are recommendations for collecting useful evidence, not guarantees that every listed signal is available on a given configuration.

Capture troubleshooting sequence

  1. Confirm the connection
  2. Select one Alfa group
  3. Follow the operating condition
  4. Run the recommended duration
  5. Stop and finalise
  6. Review quality and missing signals

Capture cannot be started

Confirm the adapter is connected and an active vehicle profile is selected.

The session does not finalise

Allow the save to complete before closing the application.

Core values update, Alfa values do not

Manufacturer-specific requests may not be supported on that exact configuration, or the diagnostic session may not have been accepted.

A value appears once and then stops

Check connection stability, the selected group and the operating condition. A single sample does not establish why later responses are missing.

Before any driving capture

Do not operate the application when it is not safe to do so. A driving capture should only be attempted when conditions permit safe operation, with a passenger or in a controlled environment.

Waiting and missing are different states.

Waiting

The application has not yet received recognised evidence for that signal in the current context. It may still arrive, or it may not be available at all.

Missing

Expected recognised evidence was not available in the finalised capture. The signal is listed as missing rather than estimated or replaced.

Why a value can remain waiting

  • The group containing that signal was not selected
  • The signal has not been requested yet in this capture
  • The vehicle state does not produce it, for example with the engine off
  • The signal is not available on this configuration
  • The adapter or diagnostic session is not returning recognised responses
  • The capture was too short for the value to appear

A missing signal does not invalidate every other recognised sample, and it is not proof of a mechanical fault. Unsupported or unavailable data stays visible as a limitation instead of being filled in.

Sessions and imports

Know where a diagnostic file belongs and how it is classified.

Live captures, supported imports, saved reports, archived sessions, demo data and technical logs are kept apart so each file appears in the correct part of the application.

Source badges

Live
Recorded directly through Guided Capture.
Imported JSON
A supported OBDVeloce JSON session brought in from elsewhere.
Legacy
An older file format retained for reference.
Demo
Clearly identified demonstration or test data.

Legacy and Demo files keep their badge and must not quietly become the newest real capture while genuine Live or Imported sessions exist.

How a supported import is handled

  1. Select
  2. Parse
  3. Normalise
  4. Rebuild summary
  5. Classify
  6. Save
  7. Open

Import classification

Valid
Recognised samples support a full interpretation.
Partial but usable
Useful recognised evidence remains, with the gaps listed.
Insufficient data
Too little recognised data for useful deterministic interpretation.
Unrecognised file
Check that the file is a supported OBDVeloce JSON session. Renaming a file does not convert its format.

A missing summary is not the same as insufficient evidence

When a supported imported session does not already contain a capture summary, it can be rebuilt from recognised samples. A missing summary alone does not make a recognised session insufficient when usable samples exist.

A session is not listed

  • Is the file saved where the application expects it?
  • OBDVeloce JSON sessions can be reviewed locally.
  • Was it a temporary or partial save?
  • Are you looking for a saved report rather than a session?
  • Has the session been archived out of the active library?
  • Is the file readable, or held open by another process?
  • Has the library been refreshed?

Saved sessions and reports remain distinct. SmartReport uses accepted evidence from completed diagnostic runs; importing a JSON session does not automatically create one.

Editing a diagnostic file by hand is not a normal fix, and a damaged file cannot always be recovered.

Diagnostic report help

Check the completed run and its accepted evidence.

SmartReport/PDF is generated locally from accepted evidence in completed Guided Diagnostic runs. Check the run context and missing evidence before interpreting the result. Engine Fault Scan and standalone session review are separate capabilities.

From completed run to SmartReport

  1. Completed run
  2. Accepted evidence
  3. Signal statistics
  4. Deterministic rules
  5. Findings
  6. Recommendations
  7. SmartReport + PDF

Interpretation depends on accepted evidence, run context and the report-rule version.

Checks for report problems

Not generated yet
Check that the Guided Diagnostic run is complete and has accepted evidence. A saved capture alone is not sufficient to describe a completed run.
Partial report
Useful findings exist, with missing signals and capture limitations stated.
Report from an earlier run
Compare the run context and evidence dates with the report you opened. Do not assume a saved report updates when a new capture is made.
Source session unavailable
Check whether the original run evidence has been moved, archived or deleted. Do not edit source identifiers or assume a saved report can reconstruct missing evidence.

Interpret within the evidence scope

A report status reflects the captured diagnostic evidence. It is not a statement about the complete mechanical condition of the vehicle.

The report appears to describe the wrong capture

Check the source-session identifier, the source badge, the selected groups and the capture timestamp in the report header before assuming a fault in the report.

A report section is missing

Check whether the relevant run completed and whether the required evidence was accepted. Read the stated limitations; a missing section does not by itself identify a vehicle fault.

What a useful review checks

  • Overall status
  • Capture quality
  • Selected group findings
  • Supporting evidence
  • Missing data
  • Stated limitations
  • Recommendations
  • Recommended next capture
  • The source-session relationship

Diagnostic interpretation, not automatic repair

OBDVeloce organises recognised diagnostic evidence, applies explicit report rules, identifies limitations and recommends useful next steps. It does not replace physical inspection, professional diagnosis, repair verification or qualified mechanical judgement.

What reporting does not do
  • Automatic repair
  • Guaranteed diagnosis
  • ECU coding
  • Actuator control
  • Forced regeneration
  • Tuning or remapping
Preparation checklist

Provide enough context to reproduce the problem.

For a future support request, describe only the details relevant to the problem: the action, exact message, software version and, for diagnostic questions, the V1 vehicle and connection context. Do not gather identifiers or files just to contact us.

Application

  • OBDVeloce version
  • Windows version
  • The exact wording of any message shown
  • Whether Developer Mode was in use

Vehicle and ECU

  • Alfa Romeo model and model year
  • Engine and power variant, and drivetrain where relevant
  • ECU identifier where available
  • Protocol information where available

Adapter and connection

  • Adapter model and connection method
  • Windows version and the selected COM port
  • The connection stage reached
  • Whether standard OBD and Alfa-specific communication succeeded

Session or report

  • Describe the source as a live or imported OBDVeloce JSON session
  • Capture mode, group and operating condition
  • Approximate duration and capture quality
  • Completed run context and the report section involved

Reproduction

  • What you expected, and what happened instead
  • The sequence of actions that led to it
  • Whether it happens every time, occasionally or once
  • Whether it can be reproduced deliberately

Describe the relevant evidence

  • The exact message, without personal identifiers
  • The run or capture step affected
  • The missing or unexpected evidence
  • What you already tried
  • No uploads are available on the contact form

Never include

  • Passwords or account credentials
  • Payment-card information
  • Personal data unrelated to the diagnostic question
  • A full backup of your computer
  • Any form of remote access to your machine
Support request

Check contact availability before writing.

The Contact page shows whether requests are open. While closed, use the published guides and follow OBDVeloce for launch updates.

The form is on Contact Support

The contact form is text-only. When enabled, a request is retained before receipt is confirmed; notification and receipt emails are attempted separately. A saved request does not establish email delivery or a promised response.

Where to go next

What is not offered

  • No fixed or guaranteed response time
  • No live chat, telephone support or callback
  • No remote access to your computer or to the vehicle
  • No remote ECU diagnosis, coding or programming
  • No guaranteed diagnosis, repair or compatibility approval
  • No automatic ticket number or assigned engineer

Support guidance helps you organise evidence and identify the next appropriate step. It does not replace professional mechanical inspection.

Privacy and file sharing

Review a diagnostic file before you share it.

A diagnostic session may contain vehicle identification numbers, ECU identifiers, timestamps, notes and operational telemetry.

  • Review contents before choosing to share anything.
  • Agree a suitable recipient and sharing method before sending files.
  • The contact form accepts text only when available.
  • Website submissions are separate from local desktop diagnostic processing.

Sharing boundaries

  • Do not assume identifiers are removed automatically.
  • No diagnostic-file uploads are available here.
  • A local file is not automatically anonymised or safe to publish.
  • Review the privacy policy for website processing.

Remove information that is not needed for the technical question before sharing a file.

How we handle your information
Before you connect

Start with compatibility, not with the symptom.

Check whether your Giulia or Stelvio 2.2 JTD / Multijet is within V1 scope, then review the connection guidance. Model selection alone does not confirm a configuration.

Check compatibilityRegister interest

Contact support