Supported vehicles

Compatibility starts with the exact vehicle and ECU.

Coming soon for Windows. V1 is built first for Alfa Romeo Giulia and Stelvio 2.2 JTD / Multijet. The documented reference is a 2020 Stelvio with Bosch EDC17C69; other configurations require review.

Check compatibility Register interest

Configuration-specific
Read-only workflow
Documented reference

Documented reference configuration

Documented reference

Vehicle: Alfa Romeo Stelvio (2020)
Engine: 2.2 MultiJet / JTD
ECU: Bosch EDC17C69
Protocol: ISO 15765-4 CAN 29/500
Platform: Windows desktop

V1 scope does not approve every Giulia or Stelvio configuration. Year, ECU software, adapter and diagnostic mode still matter.

Current validation detail

One profile, described exactly.

The reference documents development on a 2020 Stelvio 2.2 JTD / Multijet with Bosch EDC17C69. It provides a starting point for comparison, not approval of every configuration in V1 scope.

What the development work covered

Connecting a supported diagnostic adapter through a Windows COM port
Verifying adapter response and supported standard OBD communication
Establishing supported Alfa-specific diagnostic read communication
Running Guided Capture across the six supported groups
Writing structured local sessions
Reviewing captured signals, missing signals and capture quality
Creating SmartReport and local PDF exports from accepted evidence in completed diagnostic runs

Details to review separately

The reference year is 2020. Other model years, power outputs, transmissions, drivetrains, emissions variants, markets and ECU hardware/software revisions are not approved by that reference alone.

Understanding the reference

Evidence for a workflow, within a defined configuration.

The profile has been used for structured development and verification: the expected protocol and ECU family are identified, supported standard OBD and Alfa-specific read communication are part of the workflow, and Guided Capture collects recognised evidence for the supported groups.

What validation does not mean

That every individual signal is available on every vehicle
That every production-year variant behaves identically
That every diagnostic adapter will work
That every ECU software revision responds the same way
That every vehicle fault can be diagnosed
That every capture will be complete
That the vehicle is mechanically healthy
That any write operation is supported
That another vehicle sharing the engine or ECU family is automatically approved

Validation is evidence that a documented workflow runs on a specific configuration. It is not a compatibility guarantee, and it is not a statement about the condition of any vehicle.

Guided Capture coverage

Six groups of diagnostic evidence.

Core / Standard is foundational and present in every capture. Guided Diagnostic normally combines it with one focused Alfa group. Hybrid Experimental remains available for controlled use but is not the recommended default.

Six groups of diagnostic evidence.
Group	Supported evidence	Recommended duration
Core / StandardFoundational	Engine RPM, vehicle speed, coolant temperature and control-module voltage.	30–60 seconds
Turbo / AirFocused	Actual and desired boost pressure, intake-air quantity, boost-pressure signal and supported turbo-control positions.	60–90 seconds
Fuel / InjectionFocused	Fuel consumption, total and desired fuel quantity, main and pilot injection quantities where available, and injector corrections for cylinders 1 to 4.	60–90 seconds
EGRFocused	Supported high-pressure EGR opening, actual and target position, high-pressure EGR temperature and low-pressure EGR temperature.	60–90 seconds
DPF / ExhaustFocused	Differential pressure, particle-filter and pre-catalyser temperatures, particulate-filter clogging and distance from the last regeneration.	60–90 seconds
Oil / PedalFocused	Gas-pedal position and oil-degradation level.	30–60 seconds

Availability boundary

Capture coverage describes the evidence areas reviewed for the reference configuration. It is not a guarantee that every listed signal is returned during every capture, on every configuration. Signals that are unavailable stay visible as missing rather than being estimated.

Compatibility factors

What a review actually weighs.

These are review inputs, not a rejection checklist. A difference in any one of them raises a question to answer with evidence; it does not decide an outcome on its own, and not every factor is relevant to every configuration.

Vehicle

Exact Alfa Romeo model
Model year
Engine and fuel type
Power-output variant
Emissions configuration
Transmission or drivetrain where relevant
Regional configuration

ECU

ECU family
ECU hardware identifier
ECU software identifier
Diagnostic protocol

Adapter and connection

Supported diagnostic adapter
Windows COM port availability
Adapter firmware and behaviour

Observed behaviour

Whether standard OBD communication succeeds
Whether supported Alfa-specific communication succeeds
Actual signal availability during a capture

There is no VIN lookup here, and no vehicle identification number alone can confirm compatibility.

Configuration dependency

Each link depends on the one before it.

This is why a model name cannot settle the question. The answer is produced at the end of the chain, by what the ECU actually returns.

Configuration dependency

Vehicle configuration
ECU family and software
Diagnostic protocol
Diagnostic adapter
Windows COM port
Established communication
Recognised signals

A break anywhere in the chain changes what a capture can contain. A compatible vehicle with an adapter that cannot hold a stable connection still produces no usable evidence.

Review outcomes

Clear status instead of a vague promise.

A model selection can identify V1 scope. Confirming the exact configuration requires more information and, where needed, real diagnostic evidence.

Within V1 scope

A Giulia/Stelvio 2.2 JTD selection is within V1 scope, but cannot establish compatibility. ECU, software, year, adapter and diagnostic mode need evidence-based review.

ECU identification may be needed
Adapter and connection details may be needed
Observed diagnostic responses may need review

Scope is not configuration approval or software access.

Configuration review required

The configuration differs in one or more relevant details, so support cannot be stated until those details are reviewed individually.

ECU identification may be needed
Adapter and connection details may be needed
Observed diagnostic responses may need review

No compatibility claim is made at this stage, in either direction.

Evidence not yet sufficient

The available information is insufficient, or the configuration has not been validated. Support must not be assumed.

Additional evidence is required
No universal-support assumption applies
The current workflow should not be assumed compatible

Not currently confirmed describes the state of the evidence, not a fault in the vehicle and not a permanent decision.

Why a configuration may not be confirmed

Configuration details are incomplete
The ECU identity differs from the reference configuration
A different diagnostic protocol is in use
Adapter behaviour is not supported by the current workflow
Communication was never established
Responses were not recognised
No real capture evidence is available yet

Adapter and connection

The adapter is part of compatibility.

A configuration also depends on a reliable adapter connection. The current desktop workflow uses a Windows COM port and the communication conditions below.

Current requirements

A diagnostic adapter supported by the current workflow
Reliable detection by Windows
An available Windows COM port
Exclusive access to that port for the duration of a capture
Stable serial communication throughout
A successful adapter response before any vehicle request
Successful supported standard OBD communication
Supported Alfa-specific communication where the capture requires it

What a working connection does not establish

That every OBD adapter works, whichever interface or standard it advertises
That an adapter’s marketing claims prove compatibility
That connection success means every Alfa-specific signal is available
That the adapter alone determines whether a vehicle is supported

An approved adapter model and firmware list is not yet available. A COM port or an OBD compatibility claim alone does not confirm suitability.

Adapter and setup guidance

Other configurations

Other configurations within V1 need individual review.

This review scope is limited to Giulia and Stelvio 2.2 JTD / Multijet within V1. Configurations that differ from the documented 2020 Stelvio / Bosch EDC17C69 reference need individual technical review. Similar engines or ECUs do not confirm compatibility; no broader Alfa support programme is offered here.

What individual review does not mean

That the configuration is already supported
That it is provisionally approved
That a shared engine or ECU family carries the same status
That support will be added
That support will be added by any particular date

What evaluation depends on

Access to accurate vehicle and ECU information
Suitable real diagnostic captures
Adapter behaviour the current workflow supports
Available development capacity

Depth before breadth

Review needs to cover communication, recognised signals, capture quality and the completed diagnostic workflow together. Similar specifications alone cannot establish support.

Compatibility review

Details that help a future review.

These details may help a later technical review; you do not need to collect them to register interest. The interest page shows whether registration is open and does not approve a configuration or provide software access.

Vehicle

Alfa Romeo model
Model year
Engine designation and fuel type
Power output, and transmission or drivetrain where relevant
Market or regional configuration where relevant

ECU

ECU family
ECU hardware identifier where available
ECU software identifier where available
Diagnostic protocol information where available
How the ECU identification was obtained

Adapter and Windows

Adapter model and connection type
Windows version
The detected COM port
Whether the adapter responds
Whether standard OBD and Alfa-specific communication succeed

Existing evidence

The exact wording of any connection message shown
Recognised ECU identification
The capture group selected, and the signals captured
Missing or waiting signals, and the capture-quality classification
Whether the behaviour can be reproduced

Never send

Passwords or account credentials
Payment-card information
Personal information unrelated to the review
A full backup of your computer
Any form of remote access to your machine
Files still containing identifiers the review does not need

Do not send a VIN, registration documents or diagnostic files for interest registration.

Where to go next

Compatibility check
Check V1 scope and what needs further review.
Adapter and setup
Connection preparation and COM port guidance.
How It Works
The full workflow from compatibility through to a saved report.
Support
Troubleshooting guidance if a connection or capture is already failing.

Honest limitations

What a compatibility result never covers.

Compatibility is configuration-specific.
A model name alone is not sufficient.
A shared engine family is not sufficient.
An ECU family alone may not be sufficient.
Adapter detection alone is not sufficient.
Successful standard OBD communication does not guarantee that Alfa-specific signals are available.
A validated workflow does not guarantee complete signal availability.
Missing data does not automatically prove a mechanical fault.
Compatibility does not guarantee a diagnosis or a repair.
Compatibility does not replace professional mechanical inspection.
A compatibility review is not automatic approval.

A confirmed status means the software can communicate with the ECU and capture evidence within a defined scope. It says nothing about the mechanical condition of the vehicle, the cause of a symptom, or the outcome of a repair.

Not part of the normal workflow

ECU coding
Proxy alignment
Injector coding
Adaptation writing
Actuator control
Active tests
Forced DPF regeneration
Fault-code clearing
Tuning or remapping
Immobiliser operations
Firmware flashing
Module programming
Automatic repair

These define the current product boundary. They are not withheld features and no plan unlocks them.

Coming soon

Interested in future validation?

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.

Check compatibility Future-validation interest

Contact support