- Joined
- Feb 7, 2015
- Messages
- 65
- Reaction score
- 14
- Location
- Czech Republic
- VCDS Serial number
- C?ID=236893
And that help me? :-) Because I'm not so nicely in speaking via PM :-)
FEC/SWaP (Enabling APPCONNECT Apple/Android) in MIB unit possible to add codes with OBD11 and ODIS but not VCDS--- WHY?
- Thread starter adam_m87
- Start date
There is an important step that needs to be switched ON and Uwe can tell you how to do this, RT have asked that it's not published publicly. I had to ask for it too and then the process you are trying will work.
- Joined
- Feb 7, 2015
- Messages
- 65
- Reaction score
- 14
- Location
- Czech Republic
- VCDS Serial number
- C?ID=236893
Uwe sent me it and now I dont need ODIS and VCP :-)
Hi,
I have the same problem as my colleagues in this thread, I need to know that missing step about switching from standard mode to EOL mode. I'll probably type the mode number in the security access unit window, but what? Please, give me an advice. Thank you.
I have the same problem as my colleagues in this thread, I need to know that missing step about switching from standard mode to EOL mode. I'll probably type the mode number in the security access unit window, but what? Please, give me an advice. Thank you.
I suspect you're missing an important step and you might need to re-read the thread from the very beginning.
-Uwe-
- Joined
- May 16, 2014
- Messages
- 5,469
- Reaction score
- 5,938
- Location
- Melbourne, Australia
- VCDS Serial number
- C?ID=194404
hmm.......... I'm aware that this matter has been discussed previously - but this is totally bizarre (IMO)!
Either the EOL instructions for VCDS are in the public domain, or they are not - Shirley it's a binary thing !!
With due respect to Ross-Tech and the current process - when a PM/email request is sent, what decision making criteria does Ross-Tech use behind the scene to disclose (or not) these instructions?
Is this criteria simply a warning that caution is needed with the EOL facility (i.e. an overt confirmation of "user-beware" to mitigate a legal risk to Ross-Tech)? Or is the requesting user required to digitally "sign" a risk waiver in Ross-Tech's favor? Or are these instructions ONLY available to professionals - defined in some way by Ross-Tech ?
If the first option above, why can't the same cautions be added to the software and the facility made available to all. If not the first option - can users be told what the threshold criteria is for allowing access to the EoL function which Ross-Tech publicly discloses is available in VCDS, please?
Don
Either the EOL instructions for VCDS are in the public domain, or they are not - Shirley it's a binary thing !!
With due respect to Ross-Tech and the current process - when a PM/email request is sent, what decision making criteria does Ross-Tech use behind the scene to disclose (or not) these instructions?
Is this criteria simply a warning that caution is needed with the EOL facility (i.e. an overt confirmation of "user-beware" to mitigate a legal risk to Ross-Tech)? Or is the requesting user required to digitally "sign" a risk waiver in Ross-Tech's favor? Or are these instructions ONLY available to professionals - defined in some way by Ross-Tech ?
If the first option above, why can't the same cautions be added to the software and the facility made available to all. If not the first option - can users be told what the threshold criteria is for allowing access to the EoL function which Ross-Tech publicly discloses is available in VCDS, please?
Don
The threshold is to contact me privately, and tell me what you intend to use this facility for. IMO, it's a bad idea for people to use it willy-nilly.
-Uwe-
- Joined
- May 16, 2014
- Messages
- 5,469
- Reaction score
- 5,938
- Location
- Melbourne, Australia
- VCDS Serial number
- C?ID=194404
@Uwe: Thank you for the response - I feel the need to add that in asking my previous questions - I should have said that I fully acknowledge Ross-Tech's right to decide this matter in any way that it chooses (of course). I also should have said that it wasn't my intention to criticize the current practice (per se) - my primary aim was to seek an understanding of the reasoning behind the current protocol! My apology for these omissions!
I really do understand your desire to minimize possible harm from the facility - and in a sense, it's a laudable objective for Ross-Tech to take-on this "guardianship" role (albeit I might not agree)
However and with the important caveats above (and with your indulgence, a little further) - I invite that you consider the following: If you agree that the requesting user's intent is legitimate and a decision is made to disclose the EOL instructions - isn't the "genie is out of the bottle" for the user?
By this I mean that the threshold basis for Ross-Tech's initiating authority to gain access to the EOL instructions can never apply for any subsequent use of the facility. It logically follows therefore (I think) that the harm mitigation objective which appears to be the central platform for this protocol is extremely limited (i.e. it's at best a one-time-only facility)! And of course, the entire basis of the protocol assumes that the requesting user is honest (i.e. the user isn't dumb-enough to provide a silly reason for wanting EOL access)!
I tread very gently here and again, I intend no offense - I simply seek to understand
Don
Last edited:
Sure, but at that point I have some idea that the user is responsible and knows what he's doing, rather than being someone who's just poking around with, "I wonder what this button does?" Hence I prefer this facility to remain undocumented and un-obvious, and if someone has a legitimate use for it, they must ask.
-Uwe-
- Joined
- May 16, 2014
- Messages
- 5,469
- Reaction score
- 5,938
- Location
- Melbourne, Australia
- VCDS Serial number
- C?ID=194404
@Uwe: understood - I truly envy your ability to make these judgements from a PM, or email request!!
Anyhow - I hope that no one else reads beyond this point - but given your obvious abilities, I suspect that you recognize a barracuda-like tenacity of conviction in the diatribe that I have left littered throughout this forum - like the fecal droppings of someone afflicted with diarrhea (end of analogy - I promise)!!
It may not be obvious, but sometimes (on very few occasions), I'm able to see when I'm flogging-a-dead-horse and at this point in our discussion, I'm sensing no equine heartbeat !!!
So, I won't labor the point any further - but thank you for participating!
Don
PS: as an aside and again with absolutely no offense intended - one of the consequences of my self-conviction is a life-long decision never to participate in processes with which I can't agree. EOL is a very trivial example of this; I use other devices for this function for which I don't have to rely on the manufacturer to decide whether I can be trusted with software!!
Anyhow - I hope that no one else reads beyond this point - but given your obvious abilities, I suspect that you recognize a barracuda-like tenacity of conviction in the diatribe that I have left littered throughout this forum - like the fecal droppings of someone afflicted with diarrhea (end of analogy - I promise)!!
It may not be obvious, but sometimes (on very few occasions), I'm able to see when I'm flogging-a-dead-horse and at this point in our discussion, I'm sensing no equine heartbeat !!!
So, I won't labor the point any further - but thank you for participating!
Don
PS: as an aside and again with absolutely no offense intended - one of the consequences of my self-conviction is a life-long decision never to participate in processes with which I can't agree. EOL is a very trivial example of this; I use other devices for this function for which I don't have to rely on the manufacturer to decide whether I can be trusted with software!!
Last edited:
- Joined
- May 16, 2014
- Messages
- 5,469
- Reaction score
- 5,938
- Location
- Melbourne, Australia
- VCDS Serial number
- C?ID=194404
Arrrhh.............. I've just figured it out !!
Even though I don't agree with the process, in polite submission and respect for the Ross Tech protocol, I won't disclose. However and not surprisingly (and as expected), either something is in the public domain, or it is not - and it would appear that EOL for VCDS is in the public domain. So Mr Google is your friend
hint: many already know the answer although they may not realize it (as was the case for me)!!
Don
Even though I don't agree with the process, in polite submission and respect for the Ross Tech protocol, I won't disclose. However and not surprisingly (and as expected), either something is in the public domain, or it is not - and it would appear that EOL for VCDS is in the public domain. So Mr Google is your friend
hint: many already know the answer although they may not realize it (as was the case for me)!!
Don
Last edited:
Is it possible still to download VCDS 22.3.1.4 with the fix for the SwAP adaptation field length?
The limit of 1 byte still applies in 22.3.1 which is the release version I have from the web site.
Thanks...
The limit of 1 byte still applies in 22.3.1 which is the release version I have from the web site.
Thanks...
Last edited:
- Joined
- Apr 3, 2020
- Messages
- 1,211
- Reaction score
- 1,091
- Location
- Germany (AIB)
- VCDS Serial number
- C?ID=56975
In 22.3.1 its fixed used it many times since release. It doesn't matter if EN or DRV Version
That's strange - I get a warning like "Please enter only one hex byte separated by spaces" when trying to enter the long SWaP code into the IDE4330 channel.
The steps I'm taking are:
1. Open 5F, wait for session to start
2. < Make the necessary mode change >
3. Confirm that the IDE4330 channel is available (yes, shows FF)
4. Open IDE4330-Transfer of release code for a SWaP function
5. Paste generated code
6. Do It!
7. Error comes up like: "what you have entered is longer than what is saved in the channel do you want to continue", choose Yes
8. Error comes up like: "Please enter only one hex byte separated by spaces"
9. Can't continue... :-(
I get the same result whether I put spaces between the bytes or just paste as one long string.
Here is my scan... the 5F is a Discovery Media Technisat/Preh.
Can you help me work out what I'm doing wrong?
Thank you for any help...
The steps I'm taking are:
1. Open 5F, wait for session to start
2. < Make the necessary mode change >
3. Confirm that the IDE4330 channel is available (yes, shows FF)
4. Open IDE4330-Transfer of release code for a SWaP function
5. Paste generated code
6. Do It!
7. Error comes up like: "what you have entered is longer than what is saved in the channel do you want to continue", choose Yes
8. Error comes up like: "Please enter only one hex byte separated by spaces"
9. Can't continue... :-(
I get the same result whether I put spaces between the bytes or just paste as one long string.
Here is my scan... the 5F is a Discovery Media Technisat/Preh.
Can you help me work out what I'm doing wrong?
Thank you for any help...
Code:
Thursday,09,June,2022,21:50:43:39451
VCDS -- Windows Based VAG/VAS Emulator Running on Windows 10 x64(VMWare)
VCDS Version 22.3.1.4 (x64) HEX-V2 CB: 0.4615.4
Data version: 20220407 DS337.0
www.Ross-Tech.com
VIN: WVWZZZAUZEW35xxxx License Plate: xxxx
Mileage: 57776km-35900mi Repair Order: 9999
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Chassis Type: AU-VW37 (5Q0)
Scan: 01 02 03 08 09 10 14 15 16 17 19 22 42 44 52 55 5F A9
VIN: WVWZZZAUZEW353373 Mileage: 57776km-35900miles
01-Engine -- Status: OK 0000
02-Auto Trans -- Status: OK 0000
03-ABS Brakes -- Status: OK 0000
08-Auto HVAC -- Status: OK 0000
09-Cent. Elect. -- Status: OK 0000
10-Park/Steer Assist -- Status: OK 0000
14-Susp. Elect. -- Status: OK 0000
15-Airbags -- Status: OK 0000
16-Steering wheel -- Status: OK 0000
17-Instruments -- Status: OK 0000
19-CAN Gateway -- Status: OK 0000
22-AWD -- Status: OK 0000
42-Door Elect, Driver -- Status: OK 0000
44-Steering Assist -- Status: OK 0000
52-Door Elect, Pass. -- Status: OK 0000
55-Headlight Range -- Status: OK 0000
5F-Information Electr. -- Status: OK 0000
A9-Struct. Borne Sound -- Status: OK 0000
-------------------------------------------------------------------------------
Address 01: Engine (J623-CJXC) Labels:. 06K-907-425-V1.clb
Part No SW: 5G0 906 259 B HW: 06K 907 425 B
Component: 2.0l R4 TFSI H13 0102
Revision: --H13--- CVN: BB15373B
Coding: 091D00322426050B2004
Shop #: WSC 01357 011 00200
ASAM Dataset: EV_ECM20TFS0205G0906259B 001003
ROD: EV_ECM20TFS0205G0906259B.rod
VCID: 2D07F56F6D989FD3549-8079
VINID: 9E69EAAAA465A959C31430C70C5556BF9A
No fault code found.
Readiness: 1110 0000
-------------------------------------------------------------------------------
Address 02: Auto Trans (J743) Labels: 0D9-927-770.clb
Part No SW: 0D9 300 012 L HW: 02E 927 770 AQ
Component: DQ250-6A MQB H53 4517
Revision: 03253104 Serial number: TFK01407150115 CVN: 0000141E
Coding: 0014
Shop #: WSC 04742 780 00200
ASAM Dataset: EV_TCMDQ250021 001001
ROD: EV_TCMDQ250021.rod
VCID: 1F1B1FA717347D43D65-804B
No fault code found.
-------------------------------------------------------------------------------
Address 03: ABS Brakes (J104) Labels: 5Q0-907-379-IPB-V1.clb
Part No SW: 5Q0 907 379 AA HW: 5Q0 907 379 G
Component: ESC H31 0457
Revision: 00000000 Serial number: 6066400000010B
Coding: 01FA93A15425296F037A070741C66980C92A94C0E08296F7004200F8C208
Shop #: WSC 01357 011 00200
ASAM Dataset: EV_Brake1UDSContiMK100IPB 033001
ROD: EV_Brake1UDSContiMK100IPB_033_VW37.rod
VCID: 7BA30B37E36CC1639AD-802F
No fault code found.
-------------------------------------------------------------------------------
Address 08: Auto HVAC (J255) Labels:| 5G0-907-044.clb
Part No SW: 5G0 907 044 AA HW: 5G0 907 044 AA
Component: Climatronic H02 0805
Revision: 00001K06
Coding: 00120004200100011005000000101000
Shop #: WSC 01357 011 00200
ASAM Dataset: EV_ACClimaBHBVW37X 003018
ROD: EV_ACClimaBHBVW37X_003_VW37.rod
VCID: 66954A4388EE6C8B553-8033
Fresh air blower control module (front):
A/C pressure/coolant temperature sensor:
Air quality sensor:
No fault code found.
-------------------------------------------------------------------------------
Address 09: Cent. Elect. (J519) Labels:| 5Q0-937-08X-HV1.clb
Part No SW: 5Q0 937 084 AE HW: 5Q0 937 084 AE
Component: BCM MQBAB H H16 0124
Serial number: 00011407101272
Coding: 03001A46C24122F30BA44080B10C07281000000000000000000000000000
Shop #: WSC 01357 011 00200
ASAM Dataset: EV_BCMCONTI 012001
ROD: EV_BCMBOSCH_012.rod
VCID: 7BA30B37E36CC1639AD-802F
Wiper motor control module:
Subsystem 1 - Part No SW: 5G2 955 119 A HW: 5G2 955 119 A Labels: 5QX-955-119-V1.CLB
Component: WWS 140302 042 0551
Serial number: 140305200301
Coding: 0E4DFD
Rain/Light Recognition Sensor:
Subsystem 2 - Part No SW: 5Q0 955 547 HW: 5Q0 955 547 Labels: 5Q0-955-547.CLB
Component: RLFS 024 0042
Serial number: Y14M03D18H19M28S17S9
Coding: 06A8DD
Anti-theft alarm system sensor:
Subsystem 3 - Part No SW: 5Q0 951 172 HW: 5Q0 951 172
Component: Sensor, DWA 005 0315
Serial number: 000000000ZY140481774
Alarm horn:
Subsystem 4 - Part No SW: 5Q0 951 605 HW: 5Q0 951 605
Component: Sirene, DWA 004 0311
Serial number: 00000000000028779421
No fault code found.
-------------------------------------------------------------------------------
Address 10: Park/Steer Assist (J791) Labels:| 5Q0-919-294.clb
Part No SW: 5Q0 919 294 F HW: 5Q0 919 294 A
Component: PARKHILFE 8K H03 0142
Revision: -------- Serial number: 39331407601015
Coding: 0031151011
Shop #: WSC 01357 011 00200
ASAM Dataset: EV_EPHVA18AU3700000 002024
ROD: EV_EPHVA18AU3700000_002_VW37.rod
VCID: 3E25C223B0FE144BFD3-806B
No fault code found.
-------------------------------------------------------------------------------
Address 14: Susp. Elect. (J250) Labels: 5Q0-907-376.clb
Part No SW: 5Q0 907 376 HW: 5Q0 907 376
Component: DAEMPFUNGS-SG H15 0115
Serial number: 17021441350079
ASAM Dataset: EV_DRCONTITEMIC 001019
ROD: EV_DRCONTITEMIC_VW37.rod
VCID: 76B51A03D84E9C0BE53-8023
No fault code found.
-------------------------------------------------------------------------------
Address 15: Airbags (J234) Labels:| 5Q0-959-655.clb
Part No SW: 5Q0 959 655 AA HW: 5Q0 959 655 AA
Component: AirbagVW20 014 0386
Serial number: 003MLR04DB6L
Coding: 98CCC000000000005C0000CF00C800000065
Shop #: WSC 01357 011 00200
ASAM Dataset: EV_AirbaVW20SMEVW37X 002130
ROD: EV_AirbaVW20SMEVW37X_VW37.rod
VCID: 7F5BFF27F774DD43B65-802B
Left seat belt tensioner:
Subsystem 1 - Part No SW: 5G0 980 945 B HW: 5G0 980 945 B
Component: BeltPretRevFL H35 0341
Serial number: 34169677B17031471534
Coding: 333135
Right seat belt tensioner:
Subsystem 2 - Part No SW: 5G0 980 946 B HW: 5G0 980 946 B
Component: BeltPretRevFR H35 0341
Serial number: 34169676B17031471583
Coding: 333135
Crash sensor for side airbag: driver side:
Subsystem 3 - Part No SW: ----------- HW: 480 001 303 14
Component: SideSensor_Df 001 0887
Serial number: 35767000000A1B092F0X
Coding: 2D2D2D
Front Passenger's Side Airbag Crash Sensor:
Subsystem 4 - Part No SW: ----------- HW: 480 001 103 14
Component: SideSensor_Pf 001 0887
Serial number: 35867000000488E80F00
Coding: 2D2D2D
Rear Side Airbag Crash Sensor (on driver's side):
Subsystem 5 - Part No SW: ----------- HW: 480 400 703 14
Component: SideSensor_Dr 001 6149
Serial number: 35165029B14D3E72B23G
Coding: 2D2D2D
Passenger side rear thorax airbag crash sensor:
Subsystem 6 - Part No SW: ----------- HW: 480 400 703 14
Component: SideSensor_Pr 001 6149
Serial number: 3526502C512F62919188
Coding: 2D2D2D
Crash sensor for front airbag: driver side:
Subsystem 7 - Part No SW: ----------- HW: 480 401 303 14
Component: FrontSensor_D 001 6149
Serial number: 3556502B914476B1F15F
Coding: 2D2D2D
No fault code found.
-------------------------------------------------------------------------------
Address 16: Steering wheel (J524) Labels:| 5Q0-953-549.clb
Part No SW: 5Q0 953 521 P HW: 5Q0 953 569 A
Component: Lenks.Modul 075 0135
Revision: FF027027 Serial number: 20140311400263
Coding: 0410
Shop #: WSC 01357 011 00200
ASAM Dataset: EV_SMLSVALEOMQB 001015
ROD: EV_SMLSVALEOMQB.rod
VCID: 3FDBBF27B7F41D43F65-806B
No fault code found.
-------------------------------------------------------------------------------
Address 17: Instruments (J285) Labels:| 5G0-920-XXX-17.clb-SRI3
Part No SW: 5G6 920 870 B HW: 5G6 920 870 B
Component: KOMBI 314 2210
Coding: 27AD0808BB80000800087A00040000
Shop #: WSC 01357 011 00200
ASAM Dataset: EV_DashBoardVDDMQBAB 008031
ROD: EV_DashBoardVDDMQBAB_008_VW37.rod
VCID: 2E05F263609EE4CB6D3-807B
No fault code found.
-------------------------------------------------------------------------------
Address 19: CAN Gateway (J533) Labels:| 5Q0-907-530-V1.clb
Part No SW: 5Q0 907 530 Q HW: 5Q0 907 530 F
Component: GW MQB High 125 1164
Revision: -------- Serial number: 0001723779
Coding: 030100042B085900FF00026E9C0F00010001000000000000000000000000
Shop #: WSC 01357 011 00200
GVL: 01D43C1000000000400C10000000CC0000000000000000000000000000000000
ASAM Dataset: EV_GatewLear 010015
ROD: EV_GatewLear_010.rod
VCID: 3FDBBF27B7F41D43F65-806B
Generator:
Multifunction steering wheel control module:
Subsystem 2 - Part No SW: 5G0 959 442 M HW: 5G0 959 442 M Labels: 3C8-959-537.CLB
Component: E221__MFL-DC1 H11 0103
Serial number: 29160001933560046415
Coding: 29FFFF
Battery Monitoring Control Module:
Subsystem 3 - Part No SW: 5Q0 915 181 E HW: 5Q0 915 181 E
Component: J367-BDMHella H03 8043
Serial number: 9791872703
No fault code found.
-------------------------------------------------------------------------------
Address 22: AWD (J492) Labels:* 0CQ-907-554.clb
Part No SW: 0CQ 907 554 D HW: 0CQ 907 554 D
Component: Haldex4Motion H52 7076
Serial number: HA1-00012.02.14
Coding: 0001
Shop #: WSC 01357 011 00200
ASAM Dataset: EV_AllWheelContrHA1VW37X 002001
ROD: EV_AllWheelContrHA1VW37X.rod
VCID: 46D5AAC3E82E4C8BB53-8013
No fault code found.
-------------------------------------------------------------------------------
Address 42: Door Elect, Driver (J386) Labels:| 5QX-959-X93-42.clb
Part No SW: 5Q0 959 593 B HW: 5Q0 959 593 B
Component: TSG FS 020 0025
Serial number: 08031403110303
Coding: 003F0220D001048000001000
Shop #: WSC 01357 011 00200
ASAM Dataset: EV_DCUDriveSideEWMAXKLO 006003
ROD: EV_DCUDriveSideEWMAXCONT.rod
VCID: 40D9BCDBCA0A62BB8FF-8015
Rear Driver Side Door Control Module:
Subsystem 1 - Part No SW: 5Q0 959 812 A HW: 5Q0 959 812 A Labels: 5QX-959-81X-V1.CLB
Component: FOND_FHSG_DRV 005 0005
Serial number: 00000000000002154744
Coding: 1D0000
No fault code found.
-------------------------------------------------------------------------------
Address 44: Steering Assist (J500) Labels:| 5Q0-909-144.clb
Part No SW: 3Q0 909 144 F HW: 3Q0 909 144 F
Component: EPS_MQB_ZFLS 503 5043
Coding: 8103
Shop #: WSC 01357 011 00200
ASAM Dataset: EV_SteerAssisMQB 010031
ROD: EV_SteerAssisMQB_010.rod
VCID: 3537DD0F85C8D7132C9-8061
No fault code found.
-------------------------------------------------------------------------------
Address 52: Door Elect, Pass. (J387) Labels:| 5QX-959-X92-52.clb
Part No SW: 5Q0 959 592 B HW: 5Q0 959 592 B
Component: TSG BFS 020 0025
Serial number: 10031402090480
Coding: 003F0020DE01048000801000
Shop #: WSC 01357 011 00200
ASAM Dataset: EV_DCUPasseSideEWMAXKLO 006003
ROD: EV_DCUPasseSideEWMAXCONT.rod
VCID: 3FDBBF27B7F41D43F65-806B
Rear Passenger Door Control Module:
Subsystem 1 - Part No SW: 5Q0 959 811 A HW: 5Q0 959 811 A Labels: 5QX-959-81X-V1.CLB
Component: FOND_FHSG_PSG 005 0005
Serial number: 00000000000002133561
Coding: 050000
No fault code found.
-------------------------------------------------------------------------------
Address 55: Headlight Range (J745) Labels:| 7P6-907-357.clb
Part No SW: 7P6 907 357 D HW: 7P6 907 357 A
Component: AFS-ECU H07 0090
Revision: -------- Serial number: --------------
Coding: 02A602000B000200
Shop #: WSC 01357 011 00200
ASAM Dataset: EV_HeadlRegulVWAFSMQB 001120
ROD: EV_HeadlRegulVWAFSMQB.rod
VCID: 40D9BCDBCA0A62BB8FF-8015
Left Headlamp Power Output Stage:
Subsystem 1 - Part No SW: 3D0 941 329 HW: 3D0 941 329 Labels: 3D0-941-329.CLB
Component: LeiMo links H05 0012
Coding: 2E0000
Right Headlamp Power Output Stage:
Subsystem 2 - Part No SW: 3D0 941 329 HW: 3D0 941 329 Labels: 3D0-941-329.CLB
Component: LeiMo rechts H05 0012
Coding: 2E0000
No fault code found.
-------------------------------------------------------------------------------
Address 5F: Information Electr. (J794) Labels:| 5G0-035-MIB-STD2.clb
Part No SW: 3Q0 035 874 C HW: 3Q0 035 874 C
Component: MU-S-ND-ER H41 0468
Serial number: VWZAZ2T1869482
Coding: 02730001FF0000001111000100080A001F0107D6012001008E
Shop #: WSC 00046 123 12345
ASAM Dataset: EV_MUStd4CTSAT 001022
ROD: EV_MUStd4CTSAT_VW37.rod
VCID: 323DE61374A6C02B09B-8067
Display and control head 1 for information electronics:
Subsystem 1 - Part No SW: 3G0 919 605 D HW: 3G0 919 605 D
Component: ABT_Std-2_Nav H53 1031
Serial number: VWZ8Z9SJU043RR
Data carrier:
Subsystem 2 - Part No SW: 5NA 919 866 C HW: -----------
Component: MRM2 2018/19 --- 1010
Serial number: --------------------
No fault code found.
-------------------------------------------------------------------------------
Address A9: Struct. Borne Sound (J869) Labels: 4H0-907-159.clb
Part No SW: 5G0 907 159 B HW: 4H0 907 159 A
Component: SAS-GEN 2 H07 0006
Serial number: 140225200044
ASAM Dataset: EV_SoundActuaGen2AU64X 003010
ROD: EV_SoundActuaGen2AU64X.rod
VCID: 2D07F56F6D989FD3549-8079
No fault code found.
End----------(Elapsed Time: 01:11, VBatt start/end: 12.5V/12.5V)-----------Hmmm… interesting. I redownloaded 22.3.1 and used the updater on the .de site and now VCDS is showing data version 20220530 DS337.1 rather than 20220407 DS337.0 as shown previously in the scan.
Maybe that was it - I will retest later today.
Maybe that was it - I will retest later today.
I retested with the updated data version and the same issue occurs.
I also noticed that if I enter just 00 as the New Value, I still get the error of "Your input appears to be a different length from the stored value. Are you sure you want to continue?", but it does accept it in that case.
I also noticed that if I enter just 00 as the New Value, I still get the error of "Your input appears to be a different length from the stored value. Are you sure you want to continue?", but it does accept it in that case.
... any help is very much appreciated. 
Unless you ask @Uwe for the access code, it will never work.
Thanks, yes, I have spoken to Uwe to get into the correct mode. I still hit a 1 byte limit though on the channel.
is there also a security code required or some such? - I did try 20103 without success.
is there also a security code required or some such? - I did try 20103 without success.
Solved it!
I was looking at the wrong part of the error message. Rather than the error being "Please enter 1 hexadecimal bytes" the error was actually "Please enter 1 hexadecimal bytes".
The problem was not the length of the input, but rather that there was an invalid character in the hex entry. I had AO (Oh) rather than A0 (zero) in the VCRN portion of the code due to a typo and that was what was stopping the entry being accepted.
Took a while to nut out, but got there in the end. Thanks to those who read these messages and provided help.
I was looking at the wrong part of the error message. Rather than the error being "Please enter 1 hexadecimal bytes" the error was actually "Please enter 1 hexadecimal bytes".
The problem was not the length of the input, but rather that there was an invalid character in the hex entry. I had AO (Oh) rather than A0 (zero) in the VCRN portion of the code due to a typo and that was what was stopping the entry being accepted.
Took a while to nut out, but got there in the end. Thanks to those who read these messages and provided help.
- Joined
- Apr 3, 2020
- Messages
- 1,211
- Reaction score
- 1,091
- Location
- Germany (AIB)
- VCDS Serial number
- C?ID=56975
The code don't need to be seperated by spaces, but yes "O" and "0" should be correct ;-)