|
|
Post by phantoma6 on Jan 26, 2017 17:41:40 GMT
Does anyone know how to read the history of coding that is stored in the module? I'm trying to figure out how to undo something but can't figure out which "byte" or "bit" simply from the history that is stored. I simply get strings of numbers with no identification. Sample below. TIA
Date: 2017-01-26 08:51
VIN: WAUFGAFC6EN065732
Car: Audi A6
Year: 2014
Engine: CTUA
Mileage: 64438 KM
---------------------------------------------------------------
Long coding
Control unit: 09 Central Electrics
Old value:
0600A093473C9FE28701088380003908CF9ED248A6090221000004406000
New value:
0600A093473C9FE28701088380003B08CF9ED248A6090221000004406000
Mileage: 62130 km
Date: 2016-12-19 10:53
---------------------------------------------------------------
Long coding
Control unit: 09 Central Electrics
Old value:
0600A093473C9FE28701088380003908CF9ED248A6090221000004406000
New value:
0600A093473C9FE28701088380003B08CF9ED248A6090221000004406000
Mileage: 61985 km
Date: 2016-12-17 10:22
---------------------------------------------------------------
|
|
vwgti
New Member
Posts: 4 
|
Post by vwgti on Jan 27, 2017 18:28:32 GMT
I don't believe that this is actually a problem with the app. The way the long-coding works, is that it uses a hexadecimal base (numbers 0-15: 0,1,2,3,4,5,6,7,8,9,A,B,C,D,E,F respectively). You should be able to read what you changed and go to the corrrect byte to change it to a value you want assuming you know how to use binary
|
|
|
|
Post by phantoma6 on Jan 27, 2017 19:18:37 GMT
Thank you so much for chiming in, and we can assume that I do not know how to read or decipher binary. Where can I go to figure out how to decipher the code that is recorded in the History modules? Ok the examples provided earlier, I see that the 2 strings vary only at 1 character. There must be recorded the Bit and Byte as well as value that was changed. Wheee do I begin?
|
|
vwgti
New Member
Posts: 4
|
Post by vwgti on Jan 28, 2017 8:29:17 GMT
Okay, so first off, I'm actually not 100% sure how the long-coding bytes are printed in the history tab. However, I'm assuming each digit represents a byte of 4 bits (digits). So first, let's figure out what hexadecimal is.
So hexadecimal as a base 16 numbering system that utilizes natural numbers as well as letters since> I have mentioned the values above (0,1,2,3,4,5,6,7,8,9,A,B,C,D,E,F) to make a total of 16 different unique characters to show.
Now, what is binary? I could go into a lengthy explanation here, but for simplicity sake, I won't. So binary is a base 2 numbering system (0,1). This is generally how most computers communicate. Using multiple bits, however, you can represent bigger numbers. Let's take 4 bits as an example (This means it will be for binary digits _ _ _ _). You can think of each place is a 2^x value starting with zero from right to left. So in this case, you can look at it like 2^3, 2^2, 2^1, 2^0 (or 8, 4, 2, 1). If the binary at that place is one, you shall add that power to the total number (Yes I know, I'm sure there's better ways to say this, but I'm probably explaining it horribly).
Let me show you some examples to help explain. Let's take 0101 - in this case, you shall add 2^0 + 2^2 (or 1+4) and you shall get 5
Another example is 1000 - in this case, you shall add 2^3 (or 8) and no other number which means the number shall be 8
This last example I'll show you is 1111 - In this case you shall add up all of the powers 2^3 + 2^2 + 2^1 + 2^0 (or 8 + 4 + 2 + 1) which shall be 15
Lastly is converting this number to hexadecimal. Since you can convert binary to natural numbers, it should be very easy. the first 10 digits shall continue to be the natural number (0,1,2,3,4,5,6,7,8,9), but past that, it shall turn into a character. 10=A 11=B 12=C 13=D 14=E 15=F
And viola! That's how you get all the bytes (or at least it should be)
|
|
|
|
Post by phantoma6 on Aug 27, 2017 17:33:31 GMT
Hey all, it's been a long (and winding) road with using the OBD11. The learning curve has been steep. But I've finally figured out how to use the History function as it relates to all the coding changes and how to revert if one was so inclined. This is what I've been able to decipher (instructions would have been so much more helpful - from manufacturers).
When you pull up the history in any of the modules, you will see old and new values, shown in hex format. At first, this is daunting, but after reading this, you'll laugh at how simple this is, as created by the OBD11 team. That string of hex codes correlates exactly to the string of bits on top of the screen in the actual coding screens. If you go into a coding screen (Long Coding) you will see a screen with 2-digit hex codes on the top row, with the Byte ID on the left side of the 2nd row and its corresponding Hex id on the right.. As you scroll RIGHT, you will see the Byte id's count up and its corresponding Hex id's. Each one of those Hex id's is also shown on the hex string on the history screen - they're just not separated into 2 digit mode.
So, write down what you see on the history screen, but write them down in 2-digit form, right across the page. Then go back to that Long Coding screen and you'll see which Bit you changed. Simple.
Good luck and have fun, but pray you have a backup of everything, especially the original layout of your codings PRIOR to any changes.
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Aug 27, 2017 19:59:21 GMT
|
|
|
|
Post by phantoma6 on Aug 29, 2017 20:39:19 GMT
My pleasure..least I can do considering how long it took me to understand how to properly use the History function. This is a very good platform, I have the VAG COM product but choose to use the OBD11 every time. I can even have the unit in the car, car on accessory mode, and sitting in my kitchen not missing a second of the season finale of GOT while running scans. Hope it saves another member some valuable time!
Edit: Btw, I believe a certain feature was just introduced, although I cannot claim that it hasn't been in the program the entire time as I was not looking for it - and that in the Long Coding screens (any module), you will see (if errors exist) that the Bytes with errors will be underlined in RED. Pay attention to those as they can be minor or major errors.
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Aug 29, 2017 22:02:27 GMT
That's very helpful I will check it out and add this to the instructions.
|
|
|
|
Post by hgfygf on Oct 8, 2017 1:08:37 GMT
Hey all, it's been a long (and winding) road with using the OBD11. The learning curve has been steep. But I've finally figured out how to use the History function as it relates to all the coding changes and how to revert if one was so inclined. This is what I've been able to decipher (instructions would have been so much more helpful - from manufacturers). When you pull up the history in any of the modules, you will see old and new values, shown in hex format. At first, this is daunting, but after reading this, you'll laugh at how simple this is, as created by the OBD11 team. That string of hex codes correlates exactly to the string of bits on top of the screen in the actual coding screens. If you go into a coding screen (Long Coding) you will see a screen with 2-digit hex codes on the top row, with the Byte ID on the left side of the 2nd row and its corresponding Hex id on the right.. As you scroll RIGHT, you will see the Byte id's count up and its corresponding Hex id's. Each one of those Hex id's is also shown on the hex string on the history screen - they're just not separated into 2 digit mode. So, write down what you see on the history screen, but write them down in 2-digit form, right across the page. Then go back to that Long Coding screen and you'll see which Bit you changed. Simple. Good luck and have fun, but pray you have a backup of everything, especially the original layout of your codings PRIOR to any changes. |
|
|
|
Post by berhun on Mar 3, 2018 13:44:18 GMT
Hi guys i messed up somethin ln my car and i dont know how to fix it i could use some help from u guys
In history it says central electrics 09
And value
And i dont know how to read that value
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Mar 3, 2018 14:41:35 GMT
take a screen shot and post it or if that's difficult then then email the history log and post the bit that is your change you are having problems with.
|
|
