Core / Standard
Operating and connection context
Engine RPM, vehicle speed, coolant temperature and control-module voltage. Present in every capture, and the context every focused group is read against.
Typical capture duration30–60 seconds
Check compatibility.
V1 is built first for Alfa Romeo Giulia and Stelvio 2.2 JTD / Multijet on Windows. Use the selector to check scope; confirming your exact configuration needs a separate review.
- Review before confirmation
- Configuration-specific
- Evidence-led
Compatibility search
Start with the configuration you actually have.
Choose what you know. This checks the described V1 scope only. Your selections stay on this page and are not sent or saved.
Checks V1 scope
Checks V1 scope
Checks V1 scope
Review factor only
Review factor only
Result
Configuration review required
Giulia or Stelvio 2.2 JTD / Multijet is within V1 scope. Before compatibility can be confirmed, the year, ECU/software, adapter and diagnostic mode need review. See future-validation interest for availability; registration does not grant review, selection or software access.
Future-validation interest and registration availabilityDetails for a later review
Power and transmission can matter in a technical review, but do not change this scope check. No review request is created here.
Configuration review required: Giulia or Stelvio 2.2 JTD / Multijet is within V1 scope. Before compatibility can be confirmed, the year, ECU/software, adapter and diagnostic mode need review. See future-validation interest for availability; registration does not grant review, selection or software access.
Outside the described V1 scope: Check that the model and engine selections are correct. If they are, support is not established for this configuration. You can read about future-validation interest, but this does not promise review, future support or software access.
Without JavaScript, use the reference below and the future-validation interest link. A model and engine alone cannot confirm compatibility.
Compatibility result
Reference evidence, with boundaries
The documented reference is a 2020 Stelvio 2.2 JTD / Multijet with Bosch EDC17C69. It is narrower than V1’s Giulia and Stelvio scope.
- Vehicle
- Alfa Romeo Stelvio (2020)
- Engine
- 2.2 MultiJet / JTD
- ECU
- Bosch EDC17C69
- Protocol
- ISO 15765-4 CAN 29/500
- Platform
- Windows desktop
ReferenceReference configuration only
Supported capture groups- Core / Standard
- Turbo / Air
- Fuel / Injection
- EGR
- DPF / Exhaust
- Oil / Pedal
- Reports
- SmartReport + PDF: accepted evidence from completed diagnostic runs
- Known limitations
- Engine Fault Scan is separate: standard DTCs and trusted, supported enhanced Engine ECU coverage only. No records does not confirm a healthy vehicle. Interpretation of returned fault records remains under validation.
The reference does not approve other years, ECU/software revisions, adapters or every diagnostic mode. The selector above cannot make that decision.
Validation philosophy
Compatibility is earned, one stage at a time.
A useful review connects the vehicle’s exact configuration with the evidence its ECU returns. These are the main areas to check.
Vehicle
An exact configuration is identified: model, engine, ECU family, protocol and adapter.
Real capture
Guided Capture runs on that vehicle. Nothing proceeds on a datasheet alone.
Evidence review
Recognised signals, missing signals and capture quality are examined together.
Rule validation
Deterministic rules are checked against that evidence to confirm they behave as written.
Published support
Confirmed support needs a stated configuration, tested capabilities and clear limitations.
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.
Supported capture groups
Evidence groups to review for your configuration.
Core / Standard is foundational and present in every capture. The focused groups are selected one at a time, each with its own recommended duration.
Turbo / Air
Boost and intake-air evidence
Actual against desired boost pressure and intake-air quantity, with the supported turbo-control positions and intake temperatures where they are available. Compared only where both sides were recognised.
Typical capture duration60–90 seconds
Fuel / Injection
Fuel quantity and injector balance
Fuel consumption and quantities with injector corrections, read as balancing evidence rather than as a failure verdict.
Typical capture duration60–90 seconds
EGR
Recirculation position and temperature
Supported high-pressure EGR opening with its actual and target position, and the EGR temperatures. Unsupported low-pressure positions stay outside the capture.
Typical capture duration60–90 seconds
DPF / Exhaust
Particulate-filter baseline
Differential pressure, filter and catalyser temperatures, clogging and distance from the last regeneration.
Typical capture duration60–90 seconds
Oil / Pedal
Service interval and driver input
The supported oil-degradation counter alongside gas-pedal position, showing service context and what the driver asked for while the capture ran. No oil temperature is inferred.
Typical capture duration30–60 seconds
Availability boundary
Group availability describes the evidence areas reviewed for the reference configuration. It does not guarantee that every signal is returned during every capture.
Compatibility questions
The questions worth asking before you connect.
Why distinguish scope from the reference?
V1 includes Giulia and Stelvio 2.2 JTD / Multijet. The documented development reference is a 2020 Stelvio with Bosch EDC17C69. A matching model or engine does not establish the same ECU behaviour, signal availability or adapter compatibility.
Why does the ECU matter more than the model?
The ECU is what answers a diagnostic request. Its family and software decide which requests are understood and which responses come back, so two cars with the same badge and different ECUs can behave differently.
Why can identical engines behave differently?
The same engine can ship with a different ECU software revision, a different emissions configuration or a different market specification. Any of those can change which signals are available, even when the engine code is the same.
Why does validation take time?
Because it needs a real vehicle, a real capture and a review of the evidence that capture produced. Access to a suitable vehicle is usually the slowest part, and no amount of desk research replaces it.
Can an unlisted vehicle still connect?
Standard OBD communication may succeed without confirming support. Alfa-specific responses, available signals and diagnostic behaviour still need review on the exact configuration. A successful connection is only one part of that assessment.
Can I request validation for my vehicle?
See future-validation interest for registration availability. Slovenia onsite testing comes first; selected international participants follow a successful Slovenian stage. Interest does not grant a review, selection or access.
Don't see your vehicle?
Register interest
Choose launch updates or interest in future validation. This is an expression of interest, not a verified Beta application. Neither choice establishes eligibility, selection, a licence or software access.