Hi all, Hi Ross-Tech,
It came to my attention that VCDS is not the best tool when it comes to Basic Settings on modern UDS units.
Other colleagues do have similar experiences regarding complex basic setting procedures that go beyond "Start lighting basic settings" and "Quit basic lighting settings".
My understanding is that of course all available options that come with ASAM data will show up in the Basic Settings dropdown dialog because ASAM data predefines what is possible for that unit.
I cannot think of any Basic Setting procedure that does not work properly for old KWP2000/CAN-only units.
The common answer when it comes to Basic Settings for UDS is "Use ODIS".
Due to personal curiosity I did some research on that UDS ASAM topic to get a better understanding of everything.
I found some interesting slides that show a good comparison between KWP2000 and UDS:
https://slideplayer.com/slide/2496907/
There are two slides that illustrate the principle of actuator test on KWP2000 and UDS:
and
The main statement is that on UDS units the tester itself has to implement the sequence of any test because it is no more implemented as a routine within the control module.
This could make sense as the sequence could be improved or changed on the tester side when ASAM data is updated, without having the need to update the control module.
Is this also adaptable for the Basic Settings topic? Does VCDS lack the needed implementations on the tester side for this?
I'd like to understand where the difficulties are and why ODIS is the place to be for the most newer basic setting routines like Air Suspension Recalibration on Audi B9 or Magnet Ride Recalibration on Audi 8V and so on...
Cheers,
hadez16
It came to my attention that VCDS is not the best tool when it comes to Basic Settings on modern UDS units.
Other colleagues do have similar experiences regarding complex basic setting procedures that go beyond "Start lighting basic settings" and "Quit basic lighting settings".
My understanding is that of course all available options that come with ASAM data will show up in the Basic Settings dropdown dialog because ASAM data predefines what is possible for that unit.
I cannot think of any Basic Setting procedure that does not work properly for old KWP2000/CAN-only units.
The common answer when it comes to Basic Settings for UDS is "Use ODIS".
Due to personal curiosity I did some research on that UDS ASAM topic to get a better understanding of everything.
I found some interesting slides that show a good comparison between KWP2000 and UDS:
https://slideplayer.com/slide/2496907/
There are two slides that illustrate the principle of actuator test on KWP2000 and UDS:
and
The main statement is that on UDS units the tester itself has to implement the sequence of any test because it is no more implemented as a routine within the control module.
This could make sense as the sequence could be improved or changed on the tester side when ASAM data is updated, without having the need to update the control module.
Is this also adaptable for the Basic Settings topic? Does VCDS lack the needed implementations on the tester side for this?
I'd like to understand where the difficulties are and why ODIS is the place to be for the most newer basic setting routines like Air Suspension Recalibration on Audi B9 or Magnet Ride Recalibration on Audi 8V and so on...
Cheers,
hadez16