Fault evidence
Engine Fault Scan
Review available engine fault-code evidence to inform your next checks. Standard DTCs and trusted, supported enhanced Engine ECU coverage only. A code alone is not a diagnosis.
Understand the evidence your Alfa provides.
Windows diagnostic software for Giulia and Stelvio 2.2 JTD in V1. The documented reference is a 2020 Stelvio 2.2 JTD with Bosch EDC17C69; other years, ECU software and adapters need configuration review.
- Platform
- Windows desktop
- Workflow
- OBSERVE → VERIFY → EXPLAIN
- Documented reference
- 2020 Alfa Romeo Stelvio 2.2 MultiJet / JTD · Bosch EDC17C69
What the software does
Fault evidence, guided measurements and clear reports.
Engine Fault Scan reviews fault-code evidence separately from Guided Diagnostic. SmartReport uses accepted evidence from completed diagnostic runs. These are distinct capabilities, not an automatic scan-to-report sequence.
OBSERVE → VERIFY → EXPLAIN
Guided measurements
Guided Diagnostic
Collect supported measurements under guided operating conditions, with the context needed to review them. Available measurements depend on the vehicle, ECU, adapter and selected diagnostic group.
Preserve
Local Session Library
Keep captured samples, selected groups and quality information in local session files, so the source measurements remain available for review.
Import
Supported Import
Review supported OBDVeloce JSON sessions locally. Importing a file does not by itself create an accepted, completed Guided Diagnostic run for SmartReport.
Evidence review
SmartReport + PDF
Review accepted evidence from completed diagnostic runs in a structured report you can export as a PDF. Conclusions are limited to accepted evidence. A report does not certify the vehicle’s condition.
Context
Vehicle Profile
Review vehicle and ECU context alongside the supported diagnostic scope. V1 Giulia/Stelvio 2.2 JTD scope does not confirm every configuration; compare yours with the documented reference and request review where needed.
Inside the application
Engine Fault Scan: coverage and evidence
Review standard stored, pending and permanent DTCs, plus trusted, supported enhanced coverage for the Engine ECU only. Read the coverage alongside the findings: no records does not mean a healthy vehicle, and a code alone is not a diagnosis.
Focused data groups
Capture groups for the reference configuration.
Core / Standard provides operating and connection context and is present in every capture. One focused Alfa group is normally selected alongside it.
GroupSupported evidenceRecommended duration
Core / Standard
BaseEngine RPM, vehicle speed, coolant temperature and control-module voltage.
Recommended duration 30–60 seconds
Turbo / Air
Actual and desired boost pressure, intake-air quantity, boost-pressure signal and supported turbo-control positions.
Recommended duration 60–90 seconds
Fuel / Injection
Fuel consumption, total and desired fuel quantity, main and pilot injection quantities where available, and injector corrections for cylinders 1 to 4.
Recommended duration 60–90 seconds
EGR
Supported high-pressure EGR opening, actual and target position, high-pressure EGR temperature and low-pressure EGR temperature.
Recommended duration 60–90 seconds
DPF / Exhaust
Differential pressure, particle-filter and pre-catalyser temperatures, particulate-filter clogging and distance from the last regeneration.
Recommended duration 60–90 seconds
Oil / Pedal
Gas-pedal position and oil-degradation level.
Recommended duration 30–60 seconds
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.
Group data provides diagnostic evidence for review. It does not produce an automatic fault verdict, and it does not describe the vehicle's complete mechanical condition.
Why Guided Capture
Why Guided Capture?
Generic dashboards can display many values without showing whether the resulting session is diagnostically complete. OBDVeloce uses focused capture groups, visible capture quality and local session preservation, so you know what was collected and what should be repeated.
- Focused sessions with recommended capture durations.
- Complete, partial but usable, or insufficient quality classification.
- Missing-signal visibility and exact next-capture guidance.
Traceable analysis workflow
- Completed diagnostic run
- Capture summary
- Signal statistics
- Findings
- Recommendations
Deterministic interpretation depends on the accepted evidence, operating context and rule version. A saved session alone is not a completed diagnostic run.
Developer Help
Controlled tools for Alfa diagnostic research.
Alongside the normal guided workflow, OBDVeloce provides controlled internal tools for technical research: the Alfa Registry and the Alfa Transport Lab, used for DID and signal-mapping review, adapter and protocol investigation, and parked-vehicle transport testing.
These tools are secondary to Guided Capture. They are not a public API, they do not provide unrestricted ECU access, and they perform no coding, tuning, actuator control or module programming.
Integrity in diagnostics
What the product is, and what it is not.
Includes
- Windows desktop application
- Guided Diagnostic
- Local session and saved-report files
- OBDVeloce JSON import
- Engine Fault Scan
- Capture-quality validation
- SmartReport + PDF
- Documented reference: 2020 Stelvio 2.2 JTD · Bosch EDC17C69
- Controlled Developer Help tools
Does not claim
- Universal vehicle support
- ECU coding or proxy alignment
- Engine tuning or remapping
- Actuator control or active testing
- ECU programming
- Cloud analytics or cloud synchronisation
- Mobile application
- AI Analysis is a separate prototype/planned capability, not an integrated production feature. SmartReport/PDF is deterministic.
- Fixed high-frequency polling
- Guaranteed mechanical diagnosis
OBDVeloce is coming soon.
Follow the launch or express interest in future validation. Registering interest does not grant software or Beta access.