Seen my name mentioned over here a few times so thought I would pop over and say hello...
So far I have only worked on one MLB A4 and is was an interesting experience as I found that the platform demands multiple methods for configuration:
*Permissions and Programming are terms I have assigned
- Programming (Parameterisation)
People versed in VCDS will already be aware of 1 and 2 as these are the traditional methods of modification that we all know and love so I will, in part, skip explaining them but...
Permissions - One thing I noticed while plugged in to said A4 was that even though I had tried coding and adapting some of the more common features they would not work. Normally when this happens I unplug VCDS, put the cable back in my bag and whip out VAG CAN Professional as with VCP I can enter "engineering mode" and force changes through but again this did not work. Digging further via VCP I found that this new platform has a permissions "matrix" hidden within most of the control modules. I am not going to go in to this too much as VCDS (Hex-CAN) cannot access this "matrix" let alone edit it, no idea on Hex-NET as I have never seen it. ODB11? Maybe but I do not trust that application as I have seen first hand the damage that it can do via completing basic modifications.
Basically for some modifications you have to "allow them" before you can code or adapt them which limits the use of VCDS for the moment. Ross-Tech will be releasing a new cable next year which will sit between Hex-CAN and Hex-NET and hopefully they will introduce the ability to access this matrix and parameterisation...
An example for permissions - Acoustic Alarm Beep on Lock and Unlock:
*via VAG CAN Professional
- Control Module 46
- Access Permissions and Programming Matrix
- Search for Horn Acknowledgment and set to "active"
- Adaptation Channel beep-time closing central locking = Single Beep (Double or No Beep also available)
- Adaptation Channel beep-time opening central locking = Double Beep (Single or No Beep also available)
So you could complete steps 5 and 6 but without step 3 both 5 and 6 will not work.
Programming - or Parameterisation as I understand it is the editing of a control modules firmware. In short some modifications are now activated etc by editing the firmware of a control module directly. I have no examples of this as I did not want to destroy the car I was working on due to lack of experience with the new MLB platform... the parameters are presented in a nice matrix though. What I do know is that this is something which VCDS has never been able to do. I do know that ODB11 can do this, to an extent, as this is how Video In Motion is activated on MMI/MIB 4G v1 and 2 systems. The firmware of the 5F unit is downloaded, edited and then a delta is uploaded back to the 5F unit, changing the cut off speed from 3kph to 255kph.
Hope the above helps...
Now a request if I may... Is anyone here located in or around London? If willing it would be great to be able to hook up and have a testing / coding session in order to dig further in to whats possible