Compatibility Policy
V1 is limited to Alfa Romeo Giulia and Stelvio 2.2 JTD/Multijet configurations. That product scope is broader than the documented reference configuration: a 2020 Stelvio 2.2 JTD with Bosch EDC17C69. A model or engine match alone does not establish approval.
- Scope is not approval
- Evidence from real vehicles
- Configuration-specific evidence
Compatibility Check provides guidance from the current reference and validation evidence. It does not guarantee ECU coverage, adapter compatibility, a successful connection, software access or support.
Compatibility is earned, not inferred.
The points below explain what configuration review needs to establish. They do not claim that every configuration within V1 has completed validation.
Validation happens on a real vehicle
Real vehicle evidenceReal-vehicle testing is needed to establish what a configuration actually returns. The documented reference is evidence for that configuration, not proof for every Giulia or Stelvio with a similar engine or ECU.
Deterministic verification
For SmartReport, accepted evidence from a completed diagnostic run is interpreted with explicit rules. Reproducible interpretation does not prove wider vehicle compatibility.
Capture quality review
Review capture quality, missing signals and operating conditions before relying on the evidence. Incomplete captures cannot establish complete coverage.
Evidence consistency
Signals are checked against each other and against the operating context. Values that cannot be reconciled are investigated rather than averaged away.
Repeatable results
One successful capture is the easiest thing in this process to mistake for a result. A configuration has to behave the same way across separate captures before it counts.
Stable behaviour
Connection, session establishment and signal availability all have to hold steady. A configuration that works intermittently has not been validated, however good the best run looked.
Validation findings must be read with their configuration and limitations.
Absence describes the evidence, not the vehicle.
These are possible gaps in evidence, not a statement that testing has started on a particular vehicle. Configurations outside Giulia/Stelvio 2.2 JTD/Multijet are outside V1.
Not yet validated
Testing may not yet have established how this exact configuration behaves. A shared model or engine name cannot fill that gap.
Incomplete evidence
Available captures may not cover the measurements and operating conditions needed to describe reliable coverage for that configuration.
Insufficient repeatability
A connection or capture that succeeds once may still need repeat testing before its behaviour can be described as consistent.
The vehicle has not been available to test
Validation requires physical access to a vehicle in that configuration, for long enough to capture repeatedly. Access is the practical limit on how quickly the set grows.
Research is still in progress
Where an investigation is ongoing, it remains unconfirmed until the evidence is reviewed. This does not announce work on any additional model or configuration.
Unconfirmed is not a compatibility result
Within V1, missing validation evidence proves neither compatibility nor incompatibility. Future-validation interest is limited to other Giulia/Stelvio 2.2 JTD/Multijet configurations and does not promise their review or inclusion.
What configuration review examines
These steps describe the review method. They are not a record of completed testing or a promise of access.
Configuration selection
A specific configuration is chosen and described precisely — vehicle, engine, ECU family and software, protocol and adapter. Validation applies to that description, not to a model name, which is why the description comes first.
Guided Diagnostic
Collect supported measurements under the guided operating conditions. Check fault-scan coverage separately; do not assume one feature validates another.
Evidence verification
Each session is examined for what it actually contains: recognised signals, missing signals, capture quality and operating context. Values are checked against one another rather than accepted individually.
Repeat testing
Repeat testing checks whether connections and captures remain consistent across attempts. An isolated successful run is insufficient to describe broader reliability.
Validation review
The accumulated evidence is reviewed as a whole, along with the limits it revealed: which signals were never available, which groups were thinner than expected, and what a report on this configuration would therefore not be able to establish.
Published compatibility
Only then does the configuration appear as supported, published together with its capture coverage and its documented limitations. Publication is the last step, not the first.
Any unresolved evidence limits what can be stated about that configuration.
Read the scope and its limits together
A validation claim applies only to the configuration, features and conditions documented with it. The reference configuration is not blanket approval of V1.
What it does mean
The supported capture groups were exercised
Only the groups documented as tested are covered by that evidence; a model name does not add further groups.
The tested workflow is identified
Evidence must identify which steps completed. A connection alone does not prove fault coverage or acceptance of diagnostic-run evidence for SmartReport/PDF.
The behaviour repeated
Repeatability can be claimed only where separate tests support it, within their documented conditions.
Its limitations are written down
What validation did not establish for that configuration is published with it rather than left implicit.
Reporting stays transparent
Missing evidence remains visible in a report for a supported configuration exactly as it would for any other.
What it does not mean
Not universal ECU support
Enhanced Engine Fault Scan coverage is Engine ECU only and limited to trusted supported responses. It is not coverage of every control unit in the vehicle.
Not every software version
A different ECU software revision can respond differently. The published entry describes what was tested.
Not every engine variant
A shared engine name does not make two configurations equivalent. Power variant, emissions configuration and market can all change the answer.
Not a guarantee for the future
A published entry describes validation as it stands. It is not a commitment that later software, later vehicles or later changes will behave the same way.
Not a mechanical diagnosis
Compatibility concerns communication and supported evidence. It does not establish vehicle health; no returned fault codes is not a healthy-vehicle result.
Not unlimited protocol coverage
Supporting a diagnostic protocol is not the same as supporting everything that protocol can theoretically carry. Coverage is what was validated, not what is specified.
Windows is the desktop platform. Confirmed adapter models/firmware and system requirements will be published before software access. A protocol or model match does not guarantee an adapter or connection will work.
Future validation within V1
Validation first, publication second
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.
Registration is currently closed. Future-validation interest concerns only Giulia/Stelvio 2.2 JTD/Multijet configurations within V1. It does not promise review, eligibility, selection, software access, support or a place in a country cohort.
Questions about the policy.
Who decides that a configuration is validated?
Validation is reviewed against the evidence from the configuration tested. Slovenia’s first stage will involve onsite testing by ARTEODESIGN LTD with vehicle access and permission from dealers. A description sent through an interest form cannot approve a configuration.
Can a published configuration be changed or withdrawn?
Yes. A published entry describes validation as it stood when it was reviewed. If later evidence shows the behaviour is less consistent than it appeared, or that a limitation was understated, the entry can be corrected or removed. That is a normal outcome of continuing to test rather than a failure, and it is preferable to leaving a claim in place that the evidence no longer supports.
Is validation a certification or an approval?
No external certification or manufacturer approval is claimed. Validation describes testing and its documented limits; it is not a roadworthiness assessment or a guarantee of successful use on another vehicle.
Why is there no timeline for adding configurations?
Timing depends on access to suitable vehicles and the validation results. Interest in another configuration within V1 does not set a testing date or release commitment.
How much repetition is enough?
Separate tests need to support a consistent account of the configuration and its limits. No fixed number of captures is published here; a successful connection alone does not settle that review.
See Vehicles and Compatibility for the current V1 scope, reference configuration and practical next steps.
Check the current scope
Start with Vehicles and Compatibility. The interest page explains the future-validation purpose and shows the current closed registration.