|
|
Post by sandjam on Aug 13, 2018 14:44:42 GMT
I was reviewing my history on OBDeleven and saw a change I did not make in Long Coding.
Is there a guide that tells me the Bytes/bit for control unit 08?
Thanks
Long coding
Control unit: 08 Air Conditioning
Old value:
0002000420010000110500001211140A
New value:
0002000420010000110500401211140A
Mileage: 1517 km
Date: 2018-08-12 18:57
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Aug 13, 2018 14:54:00 GMT
You may not have done any long coding changes but have you used any apps (as these will make changes to long coding if that is what is required.)
Also if the long coding descriptions have been updated (by the user community) then go to long coding and select the correct Byte and hopefully there will be text against the bis there to explain what each one does.
|
|
|
|
Post by sandjam on Aug 13, 2018 15:43:34 GMT
Ok I went to long coding and went to that Byte to see what changed. It was the Blower Display in Auto Mode that was active, which I did change in the long coding section but just by using the text entries on the first page in long coding.
What I don't understand is this.
I made the change for that on 8-7-18. And it showed in History like this,
which is how I did it.
Long coding
Control unit: 08 Air Conditioning
Values:
Blower display in auto operation:
Old value: Not activated
New value: activated
Mileage: 1440 km
Date: 2018-08-07 17:25
5 Days later when I was making another change in Control Unit 8 for the heated seats memory, this showed up even though that was already changed 4 days ago.
Long coding
Control unit: 08 Air Conditioning
Old value:
00 02 00 04 20 01 00 00 11 05 00 00 12 11 14 0A
New value:
00 02 00 04 20 01 00 00 11 05 00 40 12 11 14 0A
Mileage: 1517 km
Date: 2018-08-12 18:57
Why did this not show up along with the other entry in the History back on 8-7-18 instead of showing up yesterday when I made another change unrelated in the same module?
Thanks
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Aug 13, 2018 15:54:14 GMT
Firstly on some modules in long coding you get a 0 and 1 on the top of the scree. The 1 is the proper old style Byte and Bit coding. The 0 is OBD11 Short Cut Long coding so when you use one of these what you will see is the actual long coding change made even though you used a shortcut. If you look at my control unit list forum.obdeleven.com/thread/3262/control-unit-setup under control unit: 08 I have started to map 0 to 1. With regards to the update date my guess is the change (which is on your car) was made sucsesfully but the update to OBD11 Servers did not happen till you did your next update. As I say its only a guess on my part. We have seen history being slow and normally its because there is a slow internet connection so the updates dont get back to Base. So far never seen a problem where updates do not show at all and in any even your backups will allow you to see what has changed |
|
|
|
Post by sandjam on Aug 13, 2018 16:04:42 GMT
Correct. I used the 0 page, not the 1 page in Long Coding area to make the change.
The 0 page history showed up immediately after the change. The 1 page history showed up only after I made another change in that module (5 days later), which was weird. It might confuse some people, but it did make the change correctly and technically both history entries are correct.
Thanks
|
|
|
|
Post by grubsflow on Aug 19, 2018 3:53:40 GMT
Any time any change is made to any of your's car's control modules, whether by OBDeleven, or by user controls in your car (infotainment menus, manual controls, etc), those changes are registered in the respective controller modules as changes in the long coding. If you changes any of your climate control settings from within the car, and not from OBDeleven, it could result in changes in the long coding.
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Aug 19, 2018 9:02:58 GMT
grubsflow just to add / clarify (and this is my understanding) the changes you make in the car can impact both Long Coding and Adaptation. However if if for example I turn off the ESC system using the car's functions you will not see this change in the History file (of changes you have made). If you (like I do) take regular backups and compare the pre and post files then you will see the change because the (in this case) Adaptations have been changed as a result.
|
|
|
|
Post by sandjam on Aug 19, 2018 13:51:30 GMT
That's not the case, because this change can only be done by long coding in OBDEleven (Blower Speed Display in Auto Mode) and not though the cars functions as it is not available in the cars functions on the menu's.
This was definitely OBDEleven. The history is correct it was just delayed 5 days.
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Aug 19, 2018 14:26:04 GMT
Sorry i think I am confusing you. As grubsflow said when you make changes using the cars settings (eg not using obd11) these can be reflected on the Long Coding and Adaptions setup on the car. What I was saying was if you for example turn off the ESC system you would not see anything in the history of changes section but you would if you compared you old and new backup files. The issue you have identified is that there was a lag in time because you used the shortcut (as we all do) long coding and that was shown quickly but the actual real long coding changes were not shown till the next time you logged on. |
|
