Technical Connecting with AlfaOBD - unknown ISO code for ECU - help please!

Currently reading:
Technical Connecting with AlfaOBD - unknown ISO code for ECU - help please!

Grayducato

New member
Joined
Feb 19, 2021
Messages
7
Points
3
AlfaOBD (purchased copy) reports "Unknown ISO code" when trying to connect to the ECU. All other modules are fine, 2021 Ducato 2.3 Adblue 9 speed X290 Series 7. My ECU selection is Marelli 9DF. (MJ9DFH....)

MES (demo copy) also reports the same error. I'm in Australia.

I have sent on several occasions the error report to AlfaOBD, but don't hear any further. The recent update to 2.4.2 didn't fix the problem.

Questions:

How often does Alfa update the database?
What's involved in an update, does anyone know?
Is there a temporary work around?
Would I have more success with MES?
Need to reset oil change flags, can I do damage if the ISO doesn't match. Alfa attaches a warning, but implies changes will be ignored, rather than trash the ECU.

Back story is that vehicle was in for a PM sensor replacement last year. Apparently a Bosch unit was re-fitted and because it's different to the OEM, an ECU re-flash is required and of course, a different ISO code. I have WiTech printouts to show the two ISO codes, before and after.

Here's the error report that the Android App sends to AlfaOBD:

Unsupported control module:
ECU ID: 6801
ISO Code: 0001504222
VarVer: /


The pre repair ISO code was 0001607017, software version 0032
The post-repair ISO is 0001504222, software version 0051


Thanks for reading my post.
 
Last edited:
Hi,🙂
My FIAT and Alfa petrols are the same mechanics, but different Euro standards

I am in the habit of using

"Search for Devices"

That will list every module.. That it Can Find.. 👍

Do look on the MES Supported Vehicle List

As the Coloured Cables required can be quite confusing...

I've only ever used MES, Alfaobd may not work like this🤔
 
AlfaOBD (purchased copy) reports "Unknown ISO code" when trying to connect to the ECU. All other modules are fine, 2021 Ducato 2.3 Adblue 9 speed X290 Series 7. My ECU selection is Marelli 9DF. (MJ9DFH....)

MES (demo copy) also reports the same error. I'm in Australia.

I have sent on several occasions the error report to AlfaOBD, but don't hear any further. The recent update to 2.4.2 didn't fix the problem.

Questions:

How often does Alfa update the database?
What's involved in an update, does anyone know?
Is there a temporary work around?
Would I have more success with MES?
Need to reset oil change flags, can I do damage if the ISO doesn't match. Alfa attaches a warning, but implies changes will be ignored, rather than trash the ECU.

Back story is that vehicle was in for a PM sensor replacement last year. Apparently a Bosch unit was re-fitted and because it's different to the OEM, an ECU re-flash is required and of course, a different ISO code. I have WiTech printouts to show the two ISO codes, before and after.

Here's the error report that the Android App sends to AlfaOBD:

Unsupported control module:
ECU ID: 6801
ISO Code: 0001504222
VarVer: /


The pre repair ISO code was 0001607017, software version 0032
The post-repair ISO is 0001504222, software version 0051


Thanks for reading my post.

Hi, 🙂

Made any progress with this? 🤔
 
In 2022 i used Alfaobd for a while hoping to use it to monitor every run i made using my phone. I already had MES and preffer using it for various reasons. After an upgrade For a while i was unable to read my van 2017 ducato but an email prompted a reply within 2 days an said would be resolved in next update (not given a date and they dont come on a regular basis just when sufficient reason) I was resolved maybe a month later, cant remember precisely.
My ecu is a 9df BUT HAVE TO SELECT A 8df.
 
In 2022 i used Alfaobd for a while hoping to use it to monitor every run i made using my phone. I already had MES and preffer using it for various reasons. After an upgrade For a while i was unable to read my van 2017 ducato but an email prompted a reply within 2 days an said would be resolved in next update (not given a date and they dont come on a regular basis just when sufficient reason) I was resolved maybe a month later, cant remember precisely.
My ecu is a 9df BUT HAVE TO SELECT A 8df.
Thanks,
Good to know you have found a similar issue 🙂

Which was upgraded..? 🤔
 
In 2022 i used Alfaobd for a while hoping to use it to monitor every run i made using my phone. I already had MES and preffer using it for various reasons. After an upgrade For a while i was unable to read my van 2017 ducato but an email prompted a reply within 2 days an said would be resolved in next update (not given a date and they dont come on a regular basis just when sufficient reason) I was resolved maybe a month later, cant remember precisely.
My ecu is a 9df BUT HAVE TO SELECT A 8df.
That is interesting @theoneandonly as the 150HP version is 9df, If 8df is selected an invalid iso is triggered.
 
Daryl, do you mean the 150 is a 9DF, or did you mean to say the 180 is the 9DF?
Neither, what I am saying is what seems to be valid for MES. Both @theoneandonly and I own dual EGR vehicles with no AdBlue. MES recognises my engine (150HP) as a 9DF (it will report an invalid ISO for anything else). Whereas theoneandonly has a 130HP, and according to him he has to select an 8DF, otherwise he gets and Invalid ISO. So, perhaps MES has some interesting quirks, or perhaps theoneandonly should try the 9DF again and see if it now accepts it as a valid ISO.
 
Aye I get that invalid thing with my wife’s TA 4x4 2023 Panda it doesn’t recognise the engine ECU (think) and I have to select a different one then I can read whatever and do whatever. I actually contacted MES about that issue and they just said it takes them a while to update the database so suck it up basically.

Pretty sure there’s a thread on here about MES not recognising some ECUs/Modules in newer cars.
 
Back
Top