|
|
Post by anthonylj on Oct 26, 2019 18:01:50 GMT
|
|
|
|
Post by dv52 (Australia) on Oct 27, 2019 21:51:17 GMT
^^^ Anthony: generally "not active" means that the function described has not been enabled for some reason - which could result from the fact that that the equipment is not installed, or it could also mean that the firmware in the module is missing that option, or it could mean that Audi in the country of sale just hasn't factory set the option as standard for the model car.
But you need to read the actual descriptor. Sometimes the descriptor is a negative (like "XXXX is not deactivated") - so the general rule isn't always true!!
Don
|
|
|
|
Post by anthonylj on Oct 28, 2019 1:18:35 GMT
^^^ Anthony: generally "not active" means that the function described has not been enabled for some reason - which could result from the fact that that the equipment is not installed, or it could also mean that the firmware in the module is missing that option, or it could mean that Audi in the country of sale just hasn't factory set the option as standard for the model car. But you need to read the actual descriptor. Sometimes the descriptor is a negative (like "XXXX is not deactivated") - so the general rule isn't always true!! Don So I can try and write it as active and see what happens? |
|
|
|
Post by dv52 (Australia) on Oct 28, 2019 2:48:16 GMT
Anthony: As is the central theme in my first response - it's impossible to be definitive and while it is generally true that when changes are made they can be reverted to their original value - it is not the case that there will always be no consequences.
As an example, some entries are dependent on initializing parameters within the control module (which OBD11 software calls "Basic Settings"). When changes are made to these entries, the old initializing parameters are lost and if the values are then reinstated, Basic Setting procedures must be re-run.
My advice is to be brave, but first try to find-out the most that you can about an entry before you make changes. The net and Mr Google is a great facility for this purpose - or just ask here on this forum, lot's of advice available on this forum!!
I believe that your picture is taken from the long code screen for the KESSY module (@ address hex05) - The Audi A3 8V is built on a MQB platform and as such it uses what's called UDS/ODX modules which are adaptation channel rich. Hence, there's upward of 5,000 adaptation channels in these cars - in addition to the Long code software switches in your picture.
So- lots of possible changes!!
Don
|
|
|
|
Post by anthonylj on Oct 29, 2019 23:53:29 GMT
If I mess anything up or of something goes wrong, I just look at the back up and re-code it to what it was?
|
|
|
|
Post by dv52 (Australia) on Oct 30, 2019 4:44:22 GMT
Yes - that's a good start (always make a back-up before making changes).
Or you could take refuge in the "history" part of OBD11. There is a "History" facility for each control module and there is also an accumulated "History" facility under "garage". The History facility in OBD11 records EVERY change that you make - it time stamps the change and it lists both the before and after values (very useful when the wet fecal matter collides with the fan)
But regardless of which approach that you adopt, remember - DON'T PANIC!!!
Don
|
|
