Hello all,

I digged the internet to find any Fiat specific OBD2 PIDs, to complete my full LCD instrument cluster. There is very little to no info on the internet about those PIDs, but I found a list of Alfa PIDs, where in that list, it mentioned Fiat. Can it be that those Alfa PIDs are also used in Fiat vehicels, because they are from the same manufacturer?

The list i found (it is a long list):

PID PID_Name Calculation_Formula Result Text BytesInResponse StartFromByte BytesForCalculation
1A80 Reading Identification Code FIAT drawing number 61 0 11
1A80 Reading Identification Code HW number 61 11 11
1A80 Reading Identification Code HW version 61 22 1
1A80 Reading Identification Code SW number 61 23 11
1A80 Reading Identification Code SW version 61 34 2
1A80 Reading Identification Code Homologation number 61 36 6
1A80 Reading Identification Code ISO code 61 42 5
1A80 Reading Identification Code Tester code 61 47 10
1A80 Reading Identification Code Production date 61 57 4
1A91 FIAT drawing number FIAT drawing number 11 0 11
1A92 HW number HW number 11 0 11
1A93 HW version HW version 1 0 1
1A94 SW number SW number 11 0 11
1A95 SW version SW version 2 0 2
1A96 Homologation number Homologation number 6 0 6
1A98 Tester code Tester code 10 0 10
1A99 Production date Production date 4 0 4
2101 Injection control unit X&0b00000001 X=0b00000000 Programmed 1 0 1
2101 Engine startup X&0b00000010 X=0b00000000 Allowed 1 0 1
2101 Universal code X&0b00000101 X=0b00000101 Received 1 0 1
2101 Injection control unit X&0b11111111 X=X Not programmed 1 0 1
2101 Engine startup X&0b11111111 X=X Not allowed 1 0 1
2101 Universal code X&0b00000101 X=0b00000001 Not received 1 0 1
2101 Universal code X&0b11111111 X=X Not enabled 1 0 1
2103 Odometer X*0.1 km 3 0 3
2108 Number of overrevs X*1 1 0 1
2109 Max. eng. speed counter X*10 msec. 2 0 2
210A Maximum engine speed X*40 Rpm 1 0 1
210B Number of rewrites X*1 1 0 1
210C Odometer at last rewrite X*0.1 km 3 0 3
2121 Cyl. 1 fuel correct. (X<0x8000) ? X*0.01 : (X-0x10000)*0.01 mm3/inject2 0 2
2122 Cyl. 2 fuel correct. (X<0x8000) ? X*0.01 : (X-0x10000)*0.01 mm3/inject2 0 2
2123 Cyl. 3 fuel correct. (X<0x8000) ? X*0.01 : (X-0x10000)*0.01 mm3/inject2 0 2
2124 Cyl. 4 fuel correct. (X<0x8000) ? X*0.01 : (X-0x10000)*0.01 mm3/inject2 0 2
2125 Cyl. 5 fuel correct. (X<0x8000) ? X*0.01 : (X-0x10000)*0.01 mm3/inject2 0 2
2130 Engine speed X*0.25 Rpm 2 0 2
2131 Vehicle speed X/128.0 km/h 2 0 2
2132 Cruise lamp X&0b0000000000000001 X=0b0000000000000001 Off 2 0 2
2132 Cruise lamp X&0b0000000000000010 X=0b0000000000000010 On 2 0 2
2132 Cruise lamp X&0xFFFF X=X Flashing 2 0 2
2133 Glow plugs lamp X&0b0000000000000001 X=0b0000000000000001 Off 2 0 2
2133 Glow plugs lamp X&0b0000000000000010 X=0b0000000000000010 On 2 0 2
2133 Glow plugs lamp X&0xFFFF X=X Flashing 2 0 2
2134 Water temperature w. lamp X&0b0000000000000001 X=0b0000000000000001 Off2 0 2
2134 Water temperature w. lamp X&0b0000000000000010 X=0b0000000000000010 On2 0 2
2134 Water temperature w. lamp X&0xFFFF X=X Flashing 2 0 2
2135 Oil pressure w. lamp X&0b0000000000000001 X=0b0000000000000001 Off 2 02
2135 Oil pressure w. lamp X&0b0000000000000010 X=0b0000000000000010 On 2 0 2
2135 Oil pressure w. lamp X&0xFFFF X=X Flashing 2 0 2
2136 Water in fuel filter lamp X&0b0000000000000001 X=0b0000000000000001 Off2 0 2
2136 Water in fuel filter lamp X&0b0000000000000010 X=0b0000000000000010 On2 0 2
2136 Water in fuel filter lamp X&0xFFFF X=X Flashing 2 0 2
2137 Power-latch duration X*1 msec. 2 0 2
2139 Failure lamp X&0b0000000000000001 X=0b0000000000000001 Off 2 0 2
2139 Failure lamp X&0b0000000000000010 X=0b0000000000000010 On 2 0 2
2139 Failure lamp X&0xFFFF X=X Flashing 2 0 2
213D Brake pedal status X&0b00010000 X=0b00010000 Pressed 1 0 1
213D Clutch pedal X&0b00000001 X=0b00000001 Pressed 1 0 1
213D Brake contact 2 X&0b00100000 X=0b00100000 Pressed 1 0 1
213D Accelerator pedal X&0b00000010 X=0b00000010 Accelerator potent. track 11 0 1
213D Brake pedal status X&0b11111111 X=X Released 1 0 1
213D Clutch pedal X&0b11111111 X=X Released 1 0 1
213D Brake contact 2 X&0b11111111 X=X Released 1 0 1
213D Accelerator pedal X&0b11111111 X=X Accelerator potent. track 2 1 0 1
213E Accelerator pedal (X*100)/65535 % 2 0 2
213F AD/C accelerator posit. 1 X*0.1 mV 2 0 2

Problem is that I don't have a way to test this. I am planning to buy all the components only when I think the project is able to be completed.

Since the guys at MultiECUScan will have already done all of this leg work, I'd suggest you pop onto the forums there and ask, they're much more likely to know than anyone here I suspect

Eklipze3k said:

Since the guys at MultiECUScan will have already done all of this leg work, I'd suggest you pop onto the forums there and ask, they're much more likely to know than anyone here I suspect

Click to expand...

I already asked a few questions on their forum about obd specific PIDs, but their forum lacks response, but I will try.

Just in case anyone here on this forum knows anything about this, please let me know.

I moderate the MultiECUScan Forum and approved your post.

For all manufacturers their PID codes are fairly closely guarded secrets. MultiECUScan, Snaop On, FICOM and of diagnostic manufacturers either pay Fiat, BMW, Mercedes ...... for the technical information OR do testing and monitoring (which is legal) and then by observation deduce the info they are looking for.

With this said if they have paid for, or spent many hours deducing stuff they are not very likely to just spill the beans. Doing so would reduce their sales and also they open themselves up to legal action regarding the discemination of propriety information.

The above sort of explains why much of this information is hard to come by.

Now you have through your own research and efforts identified various Alfa PIDs which is fine and great and will be of value to others.

An even more sought after info is that that of Fiat PROXI byte locations and values to enable/disable/reconfigure the vehicle various functions. Again these are avalible to paying customers under legal agreements but not freeley available. However people do play with their cars proxi data and by observation deduce the poking byte number nn to value xx makes their car explode Again perfectly legal.

Finally you are a trail blazer......... and hard work is required.

I write software to control radio equipment. My free software generates money for the DEBRA charity. Some of the control codes I use are publically released by manufacturers for certain models. Others manufacturers have graciously released "confidential" information to me. I've also done my own legal observation methods and found and diagnosed undocumented commands. I have been asked how I did what I do (that no one else does) and I have politely declined. Firstly I've spent 100s++++ hours working stuff out, writing to manufacturers, accepting legal terms etc.. But most importanlty for me I want to protect the charity income to DEBRA. Were I to publish those commands and respones that I have discovered then that would give commerical competitors an easy route to competing with my software AND thus damage charity income.

So as you can see there are various reasons why much of this information is hard to get hold of.

And if I were to encourage private enterprise then all the research and other testing you are doing could enable you to write your own "income generating" App etc. If you chose this route then you too would be protective of all your hard work.

Please NOTE! I write this post as hopefully general background information of why all this landscape of information etc. is often shrouded in mystery and often down right brick walls.

s130 said:

I moderate the MultiECUScan Forum and approved your post.

Click to expand...

Dear s130,

Thank you very much for your reply. First I want to thank you for your charity work. This is very noble and should ofcourse be protected.

Yes I already did a lot of research and found some very usefull info and gathered most of the info already. I think in this case, it is not my intentoin to write anything similar to MES or any alternative of that software. Also, this is a DIY project and I will share everything I did and found, so others can build the same thing, because the end result is not something I will, can and want to produce commercially.

The PIDs I found are already on the internet, so denying or acknowledging will not make a difference I think, but I could be wrong. The only difference it will make is that I know if they are also for Fiat, I still don't know how to implement those PIDs and I think you can not do something with these PIDs, rather then read the status/values of them.

If it is better to keep the info off the open internet, you can maybe contact me about this by private message. Again, I have no intention to harm anyones income, to steal things or to make any income using the info I gather for this project. Hence it will cost me a fair amount of money to build this LCD Cluster haha.

htevents said:

Dear s130,
If it is better to keep the info off the open internet, you can maybe contact me about this by private message. Again, I have no intention to harm anyones income, to steal things or to make any income using the info I gather for this project. Hence it will cost me a fair amount of money to build this LCD Cluster haha.

Click to expand...

Anything that you gather in your travels that is in the public domain you can basically republish so there is no need to keep it to yourself etc.

Anything you legally discover yourself by observation, test and response is again perfectly publishable.

Where one could come unstuck is if you happened across say a Fiat document marked "confidential" etc. on a website or given to you then publishing it or any part of it, even though others may have done so, could land one in a legal puddle.

I hope your project continues to proceed at pace and as far as I can see/tell you are perfectly OK and free to publish for all.

s130 said:

Anything that you gather in your travels that is in the public domain you can basically republish so there is no need to keep it to yourself etc.

Anything you legally discover yourself by observation, test and response is again perfectly publishable.

Where one could come unstuck is if you happened across say a Fiat document marked "confidential" etc. on a website or given to you then publishing it or any part of it, even though others may have done so, could land one in a legal puddle.

I hope your project continues to proceed at pace and as far as I can see/tell you are perfectly OK and free to publish for all.

Click to expand...

Thank you for your quick response.
Good to hear that publishing my findings will not lead to trouble haha.

I guess that there is no way that you are in the position to point me in the right direction about the mentioned PIDs being valid also for Fiat cars?

Well as for your project you will have to connect to the OBD socket and send the appropriate commands to get the data for your instruments then you are almost home.

Get yourself an ELM interface and a PC. you can then send the above PID and read back any data. I've not done this but there are plenty of programs on the web for simple generic OBD diagnostics. e.g. http://www.obdtester.com/pyobd and https://sourceforge.net/projects/freediag/