Answers, and where each one comes from.
The questions people actually ask before deciding whether OBDVeloce is worth their time: what it is, whether it fits their vehicle, what hardware it needs, what a report contains, and what happens to anything they send us.
- Short answers, full sources
- Links to relevant guidance
- Searchable and deep-linkable
Each answer links to relevant guidance. Availability and configuration review remain separate from registering interest.
Showing every question.
About OBDVeloce
What the software is, who it is for, and where its responsibility ends.
What is OBDVeloce?
Coming-soon Windows software by ARTEODESIGN LTD: Engine Fault Scan, Guided Diagnostic and SmartReport/PDF. V1 is built first for Giulia and Stelvio 2.2 JTD / Multijet. AI Analysis remains a separate prototype/planned capability.
Who is it designed for?
For owners and technicians who want to review diagnostic evidence in context. The software is coming soon; interest registration grants no access, and private validation is not commercial workshop use.
Does OBDVeloce replace professional diagnostics?
No. OBDVeloce helps you organise diagnostic evidence. It does not replace professional mechanical inspection or guarantee a repair decision. A report describes what the evidence shows; a physical inspection is what confirms a fault.
What makes it different from a generic OBD tool?
Guided Diagnostic collects supported measurements under guided operating conditions. SmartReport/PDF reviews accepted evidence from completed runs. Engine Fault Scan is separate; these capabilities are not one automatic code-to-diagnosis sequence.
Vehicle compatibility
Which configurations are supported, how that is decided, and what absence from the list means.
Which vehicles are supported?
V1 covers Giulia and Stelvio 2.2 JTD / Multijet. The documented reference is a 2020 Stelvio with Bosch EDC17C69. Other V1 configurations need review; selecting a model does not approve its ECU, adapter or diagnostic modes.
Why isn't my vehicle listed?
V1 scope is limited to Giulia and Stelvio 2.2 JTD / Multijet. Within that scope, the documented reference does not approve every configuration. Outside it, no broader Alfa support programme or future support is promised.
Does “not listed” mean my vehicle is unsupported?
Do not assume support from a model or engine name. Check V1 scope first; other configurations within that scope need review of the ECU, software, adapter and diagnostic mode. An interest registration is not that review.
How is compatibility validated?
Review identifies the exact configuration, checks communication and supported responses, and examines capture quality and diagnostic evidence. The documented reference is not approval of every V1 configuration or proof that every diagnostic mode has completed validation.
OBD adapters
What an adapter has to do, and why two sold under the same description can behave differently.
Which OBD adapters work?
Confirmed adapter models, firmware and system requirements will be published before software access becomes available. Presented to Windows as a serial COM port, with exclusive access during a capture
Why don't two adapters sold as the same thing behave the same?
Because the chipset is not the whole adapter. Firmware, the serial bridge, timing and how the device presents itself to Windows all vary between units sold under the same description, and those are the things that decide whether a session holds together.
USB or Bluetooth?
Connection type alone does not establish support. The current workflow uses a stable, exclusive Windows COM-port connection; the exact adapter model and firmware still need confirmation. No purchase recommendation is made here.
Can I use an inexpensive clone adapter?
Price, branding and a successful COM-port connection do not establish compatibility. Wait for confirmed adapter models and firmware before choosing hardware for OBDVeloce.
Reports
What a report contains, what it will not do, and why its limits are printed inside it.
What is included in a report?
SmartReport presents accepted evidence from completed Guided Diagnostic runs with its context and limitations, and supports local PDF export. The synthetic examples on the Reports page illustrate evidence boundaries; their layout and invented values are not actual SmartReport output.
Does OBDVeloce diagnose faults automatically?
No. Engine Fault Scan reads standard DTCs and trusted supported enhanced Engine ECU evidence only. A code is not a diagnosis, and no records does not establish a healthy vehicle. Guided Diagnostic and SmartReport help review evidence; they do not identify a failed part automatically or clear fault codes.
Why does a report record its own limitations?
Because missing evidence changes what a report can support, and leaving that out would make a thin capture look like a complete one. Absent evidence is recorded rather than invented, and insufficient data is treated as a real result.
Privacy and security
Where diagnostic data lives, and what the forms on this site collect.
Is my diagnostic data uploaded anywhere?
The current desktop capture and SmartReport/PDF processing run locally and do not include automatic diagnostic-session upload. Website submissions are separate, as are files you voluntarily share and copies made by other software or backup settings.
Does OBDVeloce work locally?
Yes. The current workflow runs on the local Windows machine and does not require a customer cloud account. Sessions and reports are written to that machine, where you can see them.
What do the forms on this website collect?
General Contact needs email, topic and message; name is optional. It records a privacy notice and does not subscribe you to updates. Interest registration remains closed: launch updates would need email and consent; future validation would add country, vehicle, engine and an optional message. Brevo stores request records before email attempts.
Register interest
Launch updates and future-validation interest, without selection or software access.
Does registering interest buy or provide software access?
No. The site is coming soon, with no published price, checkout or public installer. No product account is required merely to register interest. Interest does not grant selection, a licence or software access.
Does requesting access reserve a place or a licence?
No. Launch updates and future-validation interest are separate choices. Neither reserves a place or grants a verified Beta application, selection, licence or software access.
How will validation and launch progress?
Our validation programme will begin with hands-on testing in Slovenia. Selected international participants will follow once that stage is successfully completed. Launch timing will depend on the results.
Technical
What it runs on, what it needs, and how often the supported set changes.
Which Windows versions are supported?
Confirmed adapter models, firmware and system requirements will be published before software access becomes available.
Does OBDVeloce need an internet connection?
The diagnostic workflow runs on your own Windows computer. Guided Capture, the local session and the deterministic report are produced locally, and nothing in the capture workflow uploads a session or a report automatically.
How often is the supported list updated?
No update schedule or broader vehicle programme is promised. V1 remains Giulia and Stelvio 2.2 JTD / Multijet, with configuration-specific review. Published support must follow evidence rather than model selection or interest totals.
Troubleshooting
What most often goes wrong, and where the full checklists live.
Why can't I connect to my vehicle?
The usual causes are a COM port Windows has not assigned or that another program is holding, an adapter that answers on the serial link but not to the vehicle, the ignition state, or a configuration that has not been validated. Adapter & Setup lists each one with what to check.
The adapter is recognised but the vehicle is not. What now?
Detection in Windows does not yet confirm adapter response or vehicle communication. Check the COM port, any error message, ignition state and supported standard OBD responses, then the exact V1 configuration.
Why is my capture incomplete?
A capture is judged on the evidence it actually contains, and a short or interrupted run will not cover the supported groups. The recommended durations and conditions exist for that reason: they are guidance for collecting useful evidence, not a guarantee that every signal is available on a given configuration.
Need more guidance?
Use the support guides or check the Contact page for request availability. No reply time or individual review is promised by browsing or registering interest.