How te setup XML file with extended PID list

General General RealDash discussion
1

Hello,

I have found a list of OBDii PIDs that I want to use to extend the standard OBDii protocol inputs in Realdash, but I realy don’t know where to start and how to edit or create a cloned XML file to add these PIDs.

Also: is it possible to add an “input folder” in Realdash? When I add a gauge and go to input & values, then tap on the input, I can see a list where I can choose form Engine Inputs, Transmission, OBD Specific inputs, etc. Is there a way to add a “folder” that shows up there with my specific PIDs and/or favorites, so I don’t have to search every “folder” to get the right input?

Ok, this is the list I found, but I don’t know how to get this in the XML file, so Realdash can translate this into gauges.

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 X0.1 km 3 0 3
2108 Number of overrevs X1 1 0 1
2109 Max. eng. speed counter X10 msec. 2 0 2
210A Maximum engine speed X40 Rpm 1 0 1
210B Number of rewrites X1 1 0 1
210C Odometer at last rewrite X0.1 km 3 0 3
2121 Cyl. 1 fuel correct. (X<0x8000) ? X0.01 : (X-0x10000)0.01 mm3/inject2 0 2
2122 Cyl. 2 fuel correct. (X<0x8000) ? X0.01 : (X-0x10000)0.01 mm3/inject2 0 2
2123 Cyl. 3 fuel correct. (X<0x8000) ? X0.01 : (X-0x10000)0.01 mm3/inject2 0 2
2124 Cyl. 4 fuel correct. (X<0x8000) ? X0.01 : (X-0x10000)0.01 mm3/inject2 0 2
2125 Cyl. 5 fuel correct. (X<0x8000) ? X0.01 : (X-0x10000)0.01 mm3/inject2 0 2
2130 Engine speed X0.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 X1 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 (X100)/65535 % 2 0 2
213F AD/C accelerator posit. 1 X0.1 mV 2 0 2

Thank you in advance.

2

Anyone?

3

Hope somebody can take a look. We do not have resources to write custom XML files.

4

Wow how much to write! Do you seriously want to force someone to do this? Are you seriously?
After all, on github everything is very detailed, where and what to record! The most that you can help you is to duplicate github here! But you have to do all the burden yourself! Obviously!

5

https://github.com/janimm/RealDash-extras/blob/master/OBD2/README.md

The file itself is a couple of levels higher, similar to it, create your own!

After that, add your written file through the connection selection menu in the Garage! If everything is correct, enjoy the additional parameters of the car!

6

No I don’t want to force anyone to create the XML file for me, I don’t think I ever asked that in my post.

The question was if someone can help me start creating/editing my own XML file.

I am trying to learn everything and sometimes things get complicated and I ask for help, to understand what I hace to do, to get a certain result.

In this case, I have found a list of PIDs and every PID contains some information about the PID number, name of the PID, the calculation, info about the bytes, etc. I just don’t know how to read this and how to translate this to data to record in the XML file. Obviously I see that there is already a calculation in the PID discription, but to me this looks completely different form the example calculations in the manual (yes I already tried doing this on my own, reading manuals and info on the internet, but this is Realdash specific and there is not much to find outside this forum).
Also, in the list I posted I see “bytesinresponse” I guess this is the info I put at “replyLength” in the XML file, but there is also “startformbytes” and “bytesforcalculation” in the list I posted, but I don’t understand how to use that in the XML file or are they even necessary.

Again, I don’t want anyone to do all that work for me, just asking to help me understand that info.

7

again, regarding RD XML, what is responsible for is described in the documentation for RD
Lam says what start bits mean, the number of bits or bytes, where to write what and how to understand it is described!
Once you understand what RD is for, it’s worth referring to the documentation for your PID list!
This, I’m almost sure, no one here will tell, since each has a unique case regarding the car protocol!
Try to formulate a more specific and narrow question regarding the specifics of RealDash!
But not about decrypting your PIDs.

8

Ok, clear.

I try to dig deeper.