SVM is the tip of the iceberg, many of these parameterisations will be difficult or impossible using a pass through connection. The future is bright, but may not be grey & orange.
as Ian says SVM is used increasingly more to code & parameterize new control units or optional extras on VAG.
The basis of SVM (Software Version Management) is:
For VAG to monitor replaced control units.
Authorise modifications to their vehicle ( tie towbars into ABS, PDC, ACC etc, sound system activations etc).
Enable monitoring of stolen vehicle components illegally fitted to notify law enforcement agencies.
Maintaining their own parts catalogue & other systems (Server 42 etc) up to date for a specific vehicle after a vehicle has had a update, new system or control unit installed.
Matching a security component to a vehicle & updating the VAG security systems database (FAZIT).
Parameterizing new control units which can be installed on many different models (i.e Airbag ECU, door control unit, PCM, TCM etc) for use in a specific model, market or application specific to a certain model.
For example a component using the same part number can now be parameterised completely differently across a range of models - this is going to wreak havoc in the second hand parts market very soon.
To explain further - Where workshops purchase a second hand component of the same part number as a failed component to find they are unable to match it / enable functionality on the vehicle they've fitted it too - just changing the coding on newer models is no longer possible.
A few other reasons I have possibly forgotten.
In short!
It allows VAG to code & parameterize their own vehicle systems online (including steering torque curve characteristics which workshops not specialising in VAG commonly know nothing about - ever driven a VAG vehicle with heavy steering after a rack replacement??), remove component protection, use fewer control units for the same application across many models, test BETA software updates for success by knowing which vehicles have had the 'BETA' update & whether it required a return workshop visit to rectify a SVM update induced fault, keep their parts cat updated, track components that have been stolen from a vehicle for spares etc...
What it means for aftermarket diagnostic tools - trouble.
A list of later VAG models requiring systems to have an SVM activation or update is rapidly increasing.
There has been much written on here about the future of diagnostic tools for the aftermarket & pass thru capabilities etc.
Some of it has been disputed.
On newer Audi models 2009>, replacing control units via SVM is more common than not.
All other VAG brands are following suit, with component protection deactivation & SVM parameterizations commonplace on the latest MQB models just coming out of warranty & entering the aftermarket for repairs & maintenance.
To link this to the thread on Autologics new product, SVM activations, CP deactivations & control unit software updates are not possible on the new AL platform - note the companies change in stance from claiming "dealer level diagnostics" to "OEM like functionality".
The Blue Box used to be able to perform some of these SVM based functions, but it was a time consuming process for the software engineers at Autologic & the workshop attempting to apply the Autologic method of SVM for a specific single task parameterization.
When selecting "security functions" on AL on a later model VAG starting 2008 MY> - more often than not you will now receive a message stating - "this function is not possible using Autologic, please seek an alternative repair solution".
hth,
Jon.
Message Thread
« Back to index | View thread »
Copyright © uk autotalk