- Joined
- Jun 26, 2014
- Messages
- 1,412
- Reaction score
- 2,124
- Location
- Newcastle, England
- VCDS Serial number
- C?ID=24330
When using Coding - 07; an entry is made at the bottom of your Auto-Scan log and also in the \Debug folder in CodingLog.txt. I feel the data stored there is slightly misleading. Consider the following Auto-Scan and CodingLog as an example (this is from my 'virtual car' - a single module on the desk 
):
...and also the CodingLog.TXT:
This isn't really what happened; as the module wasn't recoded from 00000 to 00020 - the recode was rejected and it stayed coded at 00000. I know some of the newer modules report either coding accepted or why it was rejected (out of range etc.) but the log entry is still the same.
Would you consider adding either [accepted] or [rejected] or similar to the debug entries to reflect the true situation? I know the best VCDS-er should have written down the original code but it gets a bit tedious with long coding. This may be acomplished with the older KW1281 modules too, as after the coding (attempt) takes place, VCDS requests the module header information again and may compare the requested new coding value with the one returned in the refreshed header.
):
Code:
Sunday,20,July,2014,09:49:18:26758
VCDS -- Windows Based VAG/VAS Emulator
VCDS Version: 14.7.2.0
Data version: 20140714
VIN: License Plate: TESTBENCH
Mileage: 1234 Repair Order: CodingDebug
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Chassis Type: CJW - My Test-Bench
Scan: 25
-------------------------------------------------------------------------------
Address 25: Immobilizer Labels: 4A0-953-234.lbl
Part No: 4A0 953 234 F
Component: IMMO AUZ9Z0V6235256 D77
Coding: 00000
Shop #: WSC 00724
VCID: 254B8ABCBF898012D0-5178
1 Fault Found:
00750 - Warning Lamp
31-00 - Open or Short to Ground
End-------------------------(Elapsed Time: 00:09)--------------------------
Sunday,20,July,2014,09:50:42:26758
VCDS -- Windows Based VAG/VAS Emulator
VCDS Version: 14.7.2.0
Data version: 20140714
VIN: License Plate: TESTBENCH
Mileage: 1234 Repair Order: CodingDebug
Chassis Type: CJW - My Test-Bench
Scan: 25
-------------------------------------------------------------------------------
Address 25: Immobilizer Labels: 4A0-953-234.lbl
Part No: 4A0 953 234 F
Component: IMMO AUZ9Z0V6235256 D77
Coding: 00000
Shop #: WSC 00724
VCID: 254B8ABCBF898012D0-515A
1 Fault Found:
00750 - Warning Lamp
31-00 - Open or Short to Ground
End-------------------------(Elapsed Time: 00:09)--------------------------
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Address 25:4A0 953 234 F recoded (Short coding) from 00000 to 00020 (00724/---/-----)...and also the CodingLog.TXT:
Code:
Address 25:4A0 953 234 F recoded (Short coding) from 00000 to 00020 (00724/---/-----) Sunday,20,July,2014,09:51:44:26758This isn't really what happened; as the module wasn't recoded from 00000 to 00020 - the recode was rejected and it stayed coded at 00000. I know some of the newer modules report either coding accepted or why it was rejected (out of range etc.) but the log entry is still the same.
Would you consider adding either [accepted] or [rejected] or similar to the debug entries to reflect the true situation? I know the best VCDS-er should have written down the original code but it gets a bit tedious with long coding. This may be acomplished with the older KW1281 modules too, as after the coding (attempt) takes place, VCDS requests the module header information again and may compare the requested new coding value with the one returned in the refreshed header.
