|
Post by geometric on Jan 21, 2023 11:33:24 GMT
Hello. I wanted to know if there was a way to know the hitoric of the draining thanks to the obdeleven. Thanks in advance.
|
|
|
Post by dv52 (Australia) on Jan 21, 2023 23:20:47 GMT
geometric : Hi. My French language skills ain't good - but Mr Google says Hello. I wanted to know if there was a way to know the history of emptying thanks to the obdeleven. Thanks in advance. "History of emptying"? Not sure that I understand - but if you mean does a VW/Audi keep a historic record of the quantity of fuel that is used to fill the tank, then AFAIK - the answer is NO (alas)
Don
|
|
|
Post by geometric on Jan 21, 2023 23:48:11 GMT
I mean does a VW/Audi keep a historic record of oil service dates or how many times does the car did oil service? Thanks.
|
|
|
Post by dv52 (Australia) on Jan 22, 2023 0:58:35 GMT
geometric : Hmm........... of course there are many versions of vehicles in various different markets around the world - so my answer is a gross generalization. But on the vehicles with which I'm familiar, the answer alas is again NO!! I'm sure that registered dealers keep records of past oil-service referenced to the car's VIN (if the car is serviced at a dealer) - but the information related to oil-service within the car's own memory is ALL about the current oil-service period. If you want to check the elements that are recorded in the car related to oil-service, do this: - Fire-up OBD11 and connect to the dongle
- Go to the Control Unit screen
- Select Dashboard module
- Scroll-down the screen and select Live Data
- Enter "FIX" into search box and click Select ALL
- Enter "SIE" into search box and click Select ALL
As you will see - ALL the data is about the current service interval - there are no historic records (alas)
Don
|
|
|
Post by geometric on Jan 22, 2023 10:19:22 GMT
Some one said me that this (in the picture) is the historic of oil servise but i couldn't understant what does it mean, so if you could explain me the meaning of this values. thanks
Service-interval-display history4
Block1 3ff210d8 Block2 Ff23780 Block3 4ff00569 Block4 8ff23780 Block5 Cff00569 Block6 4ff00569 Block7 Ff23780 Block8 8ff23780 Block9 Cff00569 Block10
Ffffffff Block11 Ffffffff
..... Etc
Nb: there is before (Service-interval-display history4) Service-interval-display history1 2 and 3
|
|
|
Post by dv52 (Australia) on Jan 22, 2023 21:23:48 GMT
OK, so this is what happens when you write a post in a forum without any mention of the model, make, or year of manufacture. I assume that it's a relatively modern car, when in reality it is a vehicle that uses older technology!
ALL modern cars have modules that use UDS/ODX protocols (which is a set of OBD Standards for communication in these modules) . These modules have adaptation channels that use names like "FIX" and "SIE". And these UDS/ODX modules also have values that use both words and numbers
Your car has older style modules that were built before UDS/ODX. The modules in your car have adaptation channels that don't use words. Instead, your modules have adaptation channels that use numbers - hence the block numbers. And in your older style modules, the values for the adaptation channels are also numbers ONLY! Hence the number-strings in your response - these are hexadecimal numbers (i.e. the numbers use base 16 arithmetic - they are NOT decimal numbers).
As for what the numbers mean - this depends on the car. I'm not familiar with non-USD/ODX modules
Don
|
|
|
Post by geometric on Jan 22, 2023 21:56:48 GMT
sorry, i had to give you first the model it's a Seat ibiza 2019. So, does "service interval display history" represent the intervale between each oil service? And can we estimate the mileage from these intervales? Thanks for your help.
|
|
|
Post by dv52 (Australia) on Jan 25, 2023 3:27:28 GMT
geometric :OK - if your car is a MY 19 build then the modules most definitely have UDS/ODX protocols!!
I've had a look at a hex17 module (what OBD11 calls "dashboard" module) from a car that was built in 2019 and these are the equivalent block values:
Service -interval- display: history 1-Block 1 Service -interval- display: history 1-Block 2 Service -interval- display: history 1-Block 3 Service -interval- display: history 1-Block 4 Service -interval- display: history 1-Block 5 Service -interval- display: history 1-Block 6 Service -interval- display: history 1-Block 7 Service -interval- display: history 1-Block 8 Service -interval- display: history 1-Block 9 Service -interval- display: history 1-Block 10 Service -interval- display: history 1-Block 11 Service -interval- display: history 1-Block 12 Service -interval- display: history 1-Block 13 Service -interval- display: history 1-Block 14 Service -interval- display: history 1-Block 15 Service -interval- display: history 1-Block 16 Service -interval- display: history 2-Block 1 Service -interval- display: history 2-Block 2 Service -interval- display: history 2-Block 3 Service -interval- display: history 2-Block 4 Service -interval- display: history 2-Block 5 Service -interval- display: history 2-Block 6 Service -interval- display: history 2-Block 7 Service -interval- display: history 2-Block 8 Service -interval- display: history 2-Block 9 Service -interval- display: history 2-Block 10 Service -interval- display: history 2-Block 11 Service -interval- display: history 2-Block 12 Service -interval- display: history 2-Block 13 Service -interval- display: history 2-Block 14 Service -interval- display: history 2-Block 15 Service -interval- display: history 2-Block 16 Service -interval- display: history 3-Block 1 Service -interval- display: history 3-Block 2 Service -interval- display: history 3-Block 3 Service -interval- display: history 3-Block 4 Service -interval- display: history 3-Block 5 Service -interval- display: history 3-Block 6 Service -interval- display: history 3-Block 7 Service -interval- display: history 3-Block 8 Service -interval- display: history 3-Block 9 Service -interval- display: history 3-Block 10 Service -interval- display: history 3-Block 11 Service -interval- display: history 3-Block 12 Service -interval- display: history 3-Block 13 Service -interval- display: history 3-Block 14 Service -interval- display: history 3-Block 15 Service -interval- display: history 3-Block 16 Service -interval- display: history 4-Block 1 Service -interval- display: history 4-Block 2 Service -interval- display: history 4-Block 3 Service -interval- display: history 4-Block 4 Service -interval- display: history 4-Block 5 Service -interval- display: history 4-Block 6 Service -interval- display: history 4-Block 7 Service -interval- display: history 4-Block 8 Service -interval- display: history 4-Block 9 Service -interval- display: history 4-Block 10 Service -interval- display: history 4-Block 11 Service -interval- display: history 4-Block 12 Service -interval- display: history 4-Block 13 Service -interval- display: history 4-Block 14 Service -interval- display: history 4-Block 15 Service -interval- display: history 4-Block 16
So, as you can see - the module stores 4 x tranches of history data and within each tranche there are 16 x Blocks (i.e. a total of 64 Blocks of service history information).
The values for each of the above records is like this: FF FF FF FF. So the data is a string of 4 x hexadecimal numbers, separated by a space.
The car from which my data was taken had 2 x routine services at a dealer and 1 x service at an independent workshop - so it was in it's fourth service interval cycle when my data was extracted from the hex17 module
For the module in my investigation, these are the actual values (arranged by "History #"):
history 1 history 2 history 3 history 4 Block 1 > 4F F0 00 7B 2F F0 3A 8B 0F F0 66 C3 FF FF FF FF Block 2 > 0F F0 00 0D 4F F0 02 56 4F F0 06 22 FF FF FF FF Block 3 > 8F F0 00 0D 0F F0 3A 8B 0F F0 71 B4 FF FF FF FF Block 4 > CF F0 00 7B 8F F0 3A 8B 8F F0 71 B4 FF FF FF FF Block 5 > 4F F0 00 7B CF F0 02 56 CF F0 06 22 FF FF FF FF Block 6 > 0F F0 00 0D 6F F0 03 C1 FF FF FF FF FF FF FF FF Block 7 > 8F F0 00 0D CF F0 03 C1 FF FF FF FF FF FF FF FF Block 8 > CF F0 00 7B 2F F0 54 A8 FF FF FF FF FF FF FF FF Block 9 > 6F F0 00 CA 4F F0 03 C1 FF FF FF FF FF FF FF FF Block 10> 2F F0 00 17 0F F0 54 A8 FF FF FF FF FF FF FF FF Block 11> 8F F0 00 17 4F F0 03 D0 FF FF FF FF FF FF FF FF Block 12> 4F F0 01 CD 0F F0 55 35 FF FF FF FF FF FF FF FF Block 13> 0F F0 28 90 8F F0 55 35 FF FF FF FF FF FF FF FF Block 14> 4F F0 02 1D CF F0 03 D0 FF FF FF FF FF FF FF FF Block 15> 0F F0 34 5B 7F F0 05 3D FF FF FF FF FF FF FF FF Block 16> 6F F0 02 56 CF F0 05 3D FF FF FF FF FF FF FF FF
And finally, these are the decimal equivalent values for the above numbers:
history 1 history 2 history 3 history 4 Block 1 79 240 0 123 47 240 58 139 15 240 102 195 255 255 255 255 Block 2 15 240 0 13 79 240 2 86 79 240 6 34 255 255 255 255 Block 3 143 240 0 13 15 240 58 139 15 240 113 180 255 255 255 255 Block 4 207 240 0 123 143 240 58 139 143 240 113 180 255 255 255 255 Block 5 79 240 0 123 207 240 2 86 207 240 6 34 255 255 255 255 Block 6 15 240 0 13 111 240 3 193 255 255 255 255 255 255 255 255 Block 7 143 240 0 13 207 240 3 193 255 255 255 255 255 255 255 255 Block 8 207 240 0 123 47 240 84 168 255 255 255 255 255 255 255 255 Block 9 111 240 0 202 79 240 3 193 255 255 255 255 255 255 255 255 Block 10 47 240 0 23 15 240 84 168 255 255 255 255 255 255 255 255 Block 11 143 240 0 23 79 240 3 208 255 255 255 255 255 255 255 255 Block 12 79 240 1 205 15 240 85 53 255 255 255 255 255 255 255 255 Block 13 15 240 40 144 143 240 85 53 255 255 255 255 255 255 255 255 Block 14 79 240 2 29 207 240 3 208 255 255 255 255 255 255 255 255 Block 15 15 240 52 91 127 240 5 61 255 255 255 255 255 255 255 255 Block 16 111 240 2 86 207 240 5 61 255 255 255 255 255 255 255 255 So, what does this all mean? I don't know how to decode these values - my only observation is that the value FF FF FF FF means "no data stored in this field"!
Maybe you or some else reading this reply can see pattern in the numbers? Any insights would be welcomed!
Don
PS: the other interesting measurement values related to service history in the Dashboard module are these: - ESI: service exceedance in km
- ESI: service exceedance in days
Alas and again, I'm not sure what these values are meant to signify!
|
|