|
Post by tristanj on Nov 22, 2022 23:50:54 GMT
Hi all, I've put this thread here because it is such a general higher level question, admin please move if incorrectly placed.
I've recently acquired OBDeleven and am trying to find my way around its functionality by reading forums, watching Youtube etc. Whilst there are a few introductory videos on how to connect and scan, I've yet to find any comprehensive tutorials on next level up functionality.
I've been trying to learn how to scan my existing faulty CCM in a Golf5 2009 and transfer this across to a replacement (used) module.
As they say, a little knowledge is a dangerous thing and I am not particularly comfortable just 'playing around' but I do feel there is probably some really great online training I've not yet found that will explain the building blocks of how such things are done at a conceptual and practical level.
Any help would be much appreciated.
|
|
|
Post by whataboutthis on Nov 23, 2022 0:11:51 GMT
end of this helpfile shows you how to copy and paste long coding
|
|
|
Post by tristanj on Nov 23, 2022 1:12:09 GMT
That's awesome. I will try tonight.
Being that the CCM is responsible for pairing with the ignition key (s), will a backup / transfer thus allow the 'new' module to link with the key and open the car? Or is there a secondary coding / pairing process that will have to be completed?
Thanks!
|
|
|
Post by whataboutthis on Nov 23, 2022 8:41:48 GMT
Sorry that's not something that I have come across,
My suspicion though is that you will have to pair the key to the new module, the other thing to be aware of (and its not something i have had to deal with) is Component Protection which is not something that OBD11 can deal with
|
|
|
Post by dv52 (Australia) on Nov 23, 2022 23:37:45 GMT
To add to the sage advice already provided by my colleague and with the added caveat that PQ35 platform cars (like your mkV) are not my strong-suit, I invite that you consider the following:
AFAIA, OBD11 does not have an equivalent facility to "Raw Hex" for VCDS devices - which will re-program the long-code string and the adaptation channel database from an old module into a new module.
What this means for OBD11 users is that the necessary alignment of coded values in a newly installed module must be conducted manually. Again, I'm not sure about the CCM on a KWP2000 protocol vehicle, but I wouldn't think that hand-changing coding values one-by-one would be an arduous task. Of course, the manual process assumes that the OBD11 user has access to the complete module database from the old module (back-up file as already suggested).
The other consideration when replicating databases across modules is differences in the part numbers/software numbers. Obviously not a problem if replacing like-for-like - however, when the new module has the same part number, but a different software number (as often happens), the possibility arises that the new module might have adaptation channels that do not appear in the old module. If this occurs, the user needs to make an informed judgement as to the appropriate setting in these new adaptation channels.
Don
|
|