|
|
Post by johanjd on May 16, 2020 7:05:07 GMT
Hi all,
I use obdeleven gen 2 on IOS. I have done a longcoding change in module 09 byte 17 and selected HEX 00. Unfortunately i made a mistake as i shouldnt do it in that module. Now the dimlights of the golf plus 2008 are not working anymore. Is there a way to see the original setting? Or is there anybody who knows? In the android version i had a history of the longcoding changes but i can’t find them in IOS.
Thanks a lot in advance.
|
|
|
|
Post by Thirsty on May 16, 2020 7:37:32 GMT
The "car backup and programming history" feature is currently in development for IOS. See more here: obdeleven.com/en/apps-and-featuresThis should be the description data of unit 09 byte 17:
Byte 17 Bit 0: Emergency brake flashing active Byte 17 Bit 1: Deactivation of additional high beam with bi-xenon Byte 17 Bit 2: heated windscreen installed Byte 17 Bit 3: Diagnostics terminal 50 on Byte 17 Bit 4: Fog lights active as daytime running lights Byte 17 Bit 5: Fog light switch off when high beam is active Byte 17 Bit 6: free Byte 17 Bit 7: free Maybe you can reverse it with this  |
|
|
|
Post by johanjd on May 16, 2020 9:00:17 GMT
Thank you for your answer. I have an emulator for android on my mac and i can see i made long coding changes. Is it possible to restore to an earlier value if i use an android device? Or type in the long code? The following code should be the correct one, is it somewhere in the app possible to enter this complete value? Or maybe break it up in understandable pieces, i cannot really decode it when i look at it.
048F0F2700041814470A00000F8000C0060159035D400101000000000000
|
|
|
|
Post by Thirsty on May 16, 2020 9:14:32 GMT
Do you see the long coding change you made on IOS on the android history? Should work if you use the same account on both apps.
Yes you can enter the complete long coding value on android.
To see how it works do the following on the android app:
1) Open the "burger" menu
2) Select "Help"
3) Select "Application usage for Android"
4) Select "Long coding"
You can split the value you posted easily.
04 is the value of byte 00
8F is the value of byte 01
and so on
|
|
|
|
Post by johanjd on May 16, 2020 10:26:01 GMT
So if i understand correctly a byte contains 2 characters in the long string of the long coding?
New value (wrong)
048F0F2700041814470A00000F8000C0060759035D400101000000000000
Old value (correct)
048F0F2700041814470A00000F8000C0060159035D400101000000000000
The strange part is the difference in both codes is at character 35 and 36 which is position 18 if you calculate with 2 characters per byte.
Where in this code do i see the bit values, as the bit descriptions where added earlier. Or is the 2 digit value a decrypted outcome of all bit values?
Byte 17 Bit 0: Emergency brake flashing active
Byte 17 Bit 1: Deactivation of additional high beam with bi-xenon
Byte 17 Bit 2: heated windscreen installed
Byte 17 Bit 3: Diagnostics terminal 50 on
Byte 17 Bit 4: Fog lights active as daytime running lights
Byte 17 Bit 5: Fog light switch off when high beam is active
Byte 17 Bit 6: free
Byte 17 Bit 7: free
|
|
|
|
Post by Thirsty on May 16, 2020 10:46:53 GMT
Yes each byte has a hex value of two characters. No it is not position 18 because you start counting from 0. 04 => Byte 00 This means that your marked value is byte 17. I only gave you the description data not the value of each bit. In the table below you can see the int and hex values for each bit. | Bit | Int value | Hex value | | 00 | 01 | 01 | | 01 | 02 | 02 | | 02 | 04 | 04 | | 03 | 08 | 08 | | 04 | 16 | 10 | | 05 | 32 | 20 | | 06 | 64 | 40 | | 07 | 128 | 80 |
So in your old correct coding (which was 01 for byte 17) only bit 00 was checked. In your wrong coding (which was 07 for byte 17) you had checked bits 00, 01 and 02. I hope that i could help you with this answer |
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on May 16, 2020 11:21:57 GMT
And in that thread there is a excel spreadsheet you can use to type in the hex code and it will show you which bits have been ticked.
|
|
|
|
Post by johanjd on May 16, 2020 18:18:11 GMT
Thank you very much. I will have a look and try to adjust the long coding. I will post an update with the result.
|
|
|
|
Post by johanjd on May 17, 2020 10:22:31 GMT
I have reversed the coding and the lights are working again properly. The only issue we face is that while braking the 3rd braking light is working correct also the blinkers in de back are shining and not the braking lights. So we have yellow braking lights, which looks cool by the way but the wife doesn't like it so much.
Does anybody know where to search for this error?
|
|
