Is is possible at some point in time to have an ECU/module ISO code cross listing reference.
e.g.
Code 123456789 - Supported - Used in vehicles - list of vehicles
Now to keep a manually updated list on the web would be yet an extra burden of work, however for Registered Users of MultiECUScan for the program to have the option to enter an ISO code and find in which vehicles it is used and supported would be a great addition. Or something similar.
ISO Code / Usage Chart
ISO Code / Usage Chart
Fiat Strada/Ritmo Abarth 130TC, Barchetta 2005 , 500X Cross Plus
-
- Posts: 870
- Joined: 12 Feb 2010, 09:03
- Location: EU, Germany
Re: ISO Code / Usage Chart
Iti is good idea s130!
I like the idea...
I like the idea...
Coded Keys & CODE card for Alfa Romeo, Fiat and Lancia cars
Re: ISO Code / Usage Chart
Thanks for the support.
I would love this to be a simple solution to implement but I have this niggling doubt/thought in the back of my mind that it may not be a simple as I think.
I'm hoping that ANY device with an ISO code is absolutely unique. i.e./e.g same commands, same connection protocols, same everything. This should be the case but I defer to the experts on this.
Another point is this:
If ECU ISO Code 1234567890 is used in a Fiat Tank MkI and it is decided to support the Fiat Tank MkI then even if the same ECU is used in the Fiat Ship Mk0 and Fiat Bus MkIII then whilst possibly known Yani wants to get the Tank MkI supported as quickly as possible. Ideally MultiECUScan should support the Tank, Ship and Bus at the same time.
This is where my suggestion falls down.
The have the MultiECUScan program cross reference ISO codes is OK, however it can only do this if say the Tank and Ship have been implemented. If the Bus has not been implemented then the only way to handle this cross reference would be to have a web page or a separated reference file the MutliECUScan could read.
So this now raises the question? "Is there a master ISO Code Reference Document" or is ISO code usage only ever discovered when you look at a particular model?
I would love this to be a simple solution to implement but I have this niggling doubt/thought in the back of my mind that it may not be a simple as I think.
I'm hoping that ANY device with an ISO code is absolutely unique. i.e./e.g same commands, same connection protocols, same everything. This should be the case but I defer to the experts on this.
Another point is this:
If ECU ISO Code 1234567890 is used in a Fiat Tank MkI and it is decided to support the Fiat Tank MkI then even if the same ECU is used in the Fiat Ship Mk0 and Fiat Bus MkIII then whilst possibly known Yani wants to get the Tank MkI supported as quickly as possible. Ideally MultiECUScan should support the Tank, Ship and Bus at the same time.
This is where my suggestion falls down.
The have the MultiECUScan program cross reference ISO codes is OK, however it can only do this if say the Tank and Ship have been implemented. If the Bus has not been implemented then the only way to handle this cross reference would be to have a web page or a separated reference file the MutliECUScan could read.
So this now raises the question? "Is there a master ISO Code Reference Document" or is ISO code usage only ever discovered when you look at a particular model?
Fiat Strada/Ritmo Abarth 130TC, Barchetta 2005 , 500X Cross Plus