Long Coding helper for Polo 6R - Is my cable lying to me?

   #1  

DV52

Verified VCDS User
Verified
Joined
May 16, 2014
Messages
3,705
Reaction score
4,125
Location
Melbourne, Australia
VCDS Serial number
C?ID=194404
Hello VCDS Gurus!
Don't know how to ask my question tactfully, so here goes...... is anyone at Ross-Tech aware that their VCDS cables are... well, how do I say this... not entirely honest with their owners? The reason that I ask is because for some time now I've been intrigued by the reports that I keep getting from the Long Coding Helper for the 09- Cent Elect. module on my new VW Polo 6R (77TSI). The screen shots below are examples of these reports from the car without any changes being made to any of the bits




My particular issue is with the unticked status of the Lamp diagnostic settings which are in fact active on the car. Also, the unticked status of the Daytime Running Lights which are also active. I've been discussing my confusion with a fellow VWWatercooled forum member (here in Australia) and he informs me that his cable gives similar, apparently inaccurate reports on his Polo 6R vehicle - albeit my colleague asserts that this problem is intermittent on his car.

Before I forcibly take my VCDS cable to my local priest to have its confession heard (for the henous sin of lying to me), can anyone tell me if this is a known problem?


Here is the autoscan for the car


Code:
Tuesday,20,May,2014,12:38:19:03521
VCDS -- Windows Based VAG/VAS Emulator
VCDS Version: 14.4.0.3
Data version: 20140411


VIN: WVWZZZ6RZEU018831   License Plate: 
Mileage: 100km   Repair Order: Polo 6R 1st scan 



--------------------------------------------------------------------------------
--------------------------------------------------------------------------------


Chassis Type: 6R (6N0)
Scan: 01 02 03 08 09 15 17 19 25 2E 44 56 77

VIN: WVWZZZ6RZEU018831   Mileage: 100km-62miles

01-Engine -- Status: OK 0000
02-Auto Trans -- Status: OK 0000
03-ABS Brakes -- Status: OK 0000
04-Steering Angle -- Status: OK 0000
08-Auto HVAC -- Status: OK 0000
09-Cent. Elect. -- Status: OK 0000
15-Airbags -- Status: OK 0000
17-Instruments -- Status: OK 0000
19-CAN Gateway -- Status: OK 0000
25-Immobilizer -- Status: OK 0000
2E-Media Player 3 -- Status: OK 0000
44-Steering Assist -- Status: OK 0000
56-Radio -- Status: OK 0000
77-Telephone -- Status: OK 0000
 
-------------------------------------------------------------------------------
Address 01: Engine (J623-CBZB)       Labels: 03F-906-070-CBZ.clb
   Part No SW: 03F 906 070 HF    HW: 03F 907 309 AJ
   Component: SIMOS10.22AH10 5489  
   Revision: --H10---    Serial number:               
   Coding: 002500D6202400080000
   Shop #: WSC 31414 790 50316
   ASAM Dataset: EV_ECM12TFS02103F906070HF 004008
   ROD: EV_ECM12TFS02103F906070FJ.rod
   VCID: 6DD1250CBC9C3F539B-8038

No fault code found.
Readiness: 0110 0101

-------------------------------------------------------------------------------
Address 02: Auto Trans        Labels: 0AM-927-769.lbl
   Part No SW: 0AM 300 058 G    HW: 0AM 927 769 D
   Component: GSG DSG AG7     431 4530  
   Revision: 00043014    Serial number: CU501309097002
   Coding: 0000020
   Shop #: WSC 44551 111 44551
   VCID: 3561CD6C5F4CB793A3-5106

No fault code found.

-------------------------------------------------------------------------------
Address 03: ABS Brakes (J104)       Labels: 6R0-907-37x-ESP90.clb
   Part No SW: 6R0 907 379 AS    HW: 6R0 907 379 AS
   Component: ESP9.0i front H03 0003  
   Serial number: --------------
   Coding: 23DD2885412400C8C41C146C825200800905
   Shop #: WSC 31414 790 50316
   ASAM Dataset: EV_Brake1ESP90iBOSCH 003020
   ROD: EV_Brake1ESP90iBOSCH_AU21.rod
   VCID: 0F2D5F84D650AD43C9-805A

No fault code found.

-------------------------------------------------------------------------------
Address 08: Auto HVAC (J255)       Labels: 6R0-907-044.clb
   Part No SW: 6R0 907 044 H    HW: 6R0 907 044 H
   Component: Climatronic   H12 0812  
   Revision: V0000000    
   VCID: 387FC4588B5E4AFBB8-806D

No fault code found.

-------------------------------------------------------------------------------
Address 09: Cent. Elect. (J519)       Labels: 6R0-937-08x-09.clb
   Part No SW: 6R0 937 087 P    HW: 6R0 937 087 
   Component: BCM PQ25 H+4  H34 0411  
   Revision: BF034001    Serial number: 0581 205130557
   Coding: 64B02B2F08A10000013808002D2B0ED100C0410F60060000200000000000
   Shop #: WSC 31414 790 31414
   VCID: 4A9B8E90E5B2C86BDE-801F

   Subsystem 1 - Part No: 1K0 955 559 AH  Labels: 1K0-955-559-AG.CLB
   Component: RLS 110713 05  54  0403 
   Coding: 03302D

   Subsystem 2 - Part No SW: 6R0 959 802 AT    HW: 6R0 959 802 AT  Labels: 6R0-959-802.CLB
   Component: J386__TSG_FT  003 8611 
   Coding: 1000A0

   Subsystem 3 - Part No SW: 6R0 959 801 AD    HW: 6R0 959 801 AD
   Component: J387__TSG_BT  008 1611 
   Coding: 18BC30

   Subsystem 4 - Part No SW: 5K0 959 542 C    HW: 5K0 959 542 C
   Component: E221__MFL-TAS  H31 0037 
   Coding: 020000

   Subsystem 5 - Part No SW: 6R0 959 811 N    HW: 6R0 959 811 N
   Component: J388__TSG_HL  003 8610 
   Coding: 0000A0

   Subsystem 6 - Part No SW: 6R0 959 812 G    HW: 6R0 959 812 G
   Component: J389__TSG_HR  008 1611 
   Coding: 18BC32

No fault code found.

-------------------------------------------------------------------------------
Address 15: Airbags (J234)       Labels: 5K0-959-655.clb
   Part No SW: 6R0 959 655 L    HW: 6R0 959 655 L
   Component: VW10Airbag027 H10 0020  
   Revision: --------    Serial number: 003GY009Y2U%
   Coding: 003237
   Shop #: WSC 31414 790 31414
   ASAM Dataset: EV_AirbaVW10BPAVW250 A01001
   ROD: EV_AirbaVW10BPAVW250.rod
   VCID: 4B958B94E2C8D163E5-801E

   Crash sensor for side airbag; driver side: 
   Serial number: 3575HRB401C50J5M60J$

   Crash sensor for side airbag; passenger side: 
   Serial number: 3585HRB400C50IPGG9HQ

   Crash sensor for side airbag; rear driver side: 
   Serial number: 3515RRB400Q50L30E8PD

   Crash sensor for side airbag; rear passenger side: 
   Serial number: 3525RRB400Q50L30LHFK

No fault code found.

-------------------------------------------------------------------------------
Address 17: Instruments (J285)       Labels: 5K0-920-xxx-17.clb
   Part No SW: 6R0 920 860 M    HW: 6R0 920 860 M
   Component: KOMBI         H04 0709  
   Serial number: 00000000000000
   Coding: 140A01
   Shop #: WSC 31414 790 50316
   ASAM Dataset: EV_Kombi_UDS_VDD_RM09 A04723
   ROD: EV_Kombi_UDS_VDD_RM09_VW21.rod
   VCID: 3E73D240A17A74CB72-806B

No fault code found.

-------------------------------------------------------------------------------
Address 19: CAN Gateway (J533)       Labels: 6N0-909-901-6R.clb
   Part No SW: 6N0 909 901     HW: 6R0 937 087 
   Component: GW-K-CAN TP20 H34 0411  
   Revision: BF034001    
   Coding: 002300
   Shop #: WSC 31414 790 31414
   VCID: 70EF3C78A3AED2BBB0-8025

No fault code found.

-------------------------------------------------------------------------------
Address 25: Immobilizer (J334)       Labels: 5K0-920-xxx-25.clb
   Part No SW: 5K0 953 234     HW: 5K0 953 234 
   Component: IMMO          H04 0709  
   Serial number:               
   Coding: 000000
   Shop #: WSC 00000 000 00000
   ASAM Dataset: EV_Immo_UDS_VDD_RM09 A03710
   ROD: EV_Immo_UDS_VDD_RM09_SE36.rod
   VCID: 6ADB2E108D72286BFE-803F

No fault code found.

-------------------------------------------------------------------------------
Address 44: Steering Assist        Labels: 6Q0-423-156.clb
   Part No: 6R0 423 156 C
   Component: LenkhilfeTRW        V278  
   Coding: 11230
   Shop #: WSC 31414  
   VCID: 306FFC78F72E92BBF0-8065

No fault code found.

-------------------------------------------------------------------------------
Address 56: Radio (J503)       Labels: 5M0-035-1xx-56.clb
   Part No SW: 5M0 035 186 J    HW: 5M0 035 186 J
   Component: Radio RCD310  042 0082  
   Revision: 01000001    Serial number: VWZ1Z2N1638082
   Coding: 01000400020001
   Shop #: WSC 31414 790 31414
   VCID: 3365F3749238A9A38D-8066

No fault code found.

-------------------------------------------------------------------------------
Address 77: Telephone (J412)       Labels: None
   Part No SW: 5N0 035 729 B    HW: 5N0 035 729 B
   Component: TELEFON       H05 0315  
   Revision: 1B001001    Serial number: 00007665205918
   Coding: 0200000080000210
   Shop #: WSC 31414 790 50316
   ASAM Dataset: EV_UHVUMI 001007
   ROD: EV_UHVUMI.rod
   VCID: 2F6DFF0476108D43E9-807A

No fault code found.

End   ---------------------------------------------------------------------
 
Last edited:
   #2  

Uwe

Benevolent Dictator
Staff member
Joined
Jan 29, 2014
Messages
30,459
Reaction score
21,730
Location
USA
VCDS Serial number
HC100001
Cables are usually pretty honest, they just pass data back and forth, without making any kind of value judgement regarding what that data might mean. ;)

Now the software (taken as a whole), that's a different story. It does in indeed interpret the meaning of the data from your car, and it's certainly not inconceivable that the files it uses to do that with could have some errors, for example, confusing "active" and "inactive". If you were brave, you'd tick the box for Byte 23, bit 6 and let us know if that makes your DRLs go away. We can't do this for you 'cause nobody at RT has a 6R Polo.

-Uwe-
 
   #3  

DV52

Verified VCDS User
Verified
Joined
May 16, 2014
Messages
3,705
Reaction score
4,125
Location
Melbourne, Australia
VCDS Serial number
C?ID=194404
Uwe: I'm not entirely sure that my allegation of delinquency (on my cable) is misplaced, but I'm prepared to accept your advice about this!

I tried making the changes that you suggested - for the DRLs. The change was accepted and the hexadecimal value for the byte altered accordingly (00100000=hex40, I think).

However the DRLs remained on (after I closed down the software and turned the ignition off/on again). I tried rolling back the status of this bit, but it had absolutely no impact on the operation of the DRLs. It seems that, notwithstanding the descriptor of this bit, it's status is ineffective.

To add further confusion to my predicament, I did successfully alter the status of byte 0 (bits 0&1) of the Cent.Elect. module to enable the car's auto locking function above 15km/hr. So, I can confirm that this part of the software is working.

Whilst it's a mystery to me why these things are happening, I'm not terribly fussed about this dilemma. Clearly RT hasn't been aware of this issue before, so mine might be an isolated problem. I'll try other stuff at my end (not sure what) and provide further advice.
Thanks again

PS: I'm happy to make my Polo available to your staff for analysis. What's the longest cable length that RT has in stock?
 
Last edited:
   #4  

Uwe

Benevolent Dictator
Staff member
Joined
Jan 29, 2014
Messages
30,459
Reaction score
21,730
Location
USA
VCDS Serial number
HC100001
Well, one possible explanation is that VW changed the meanings of some of the bits and bytes in the BCM in that brand new car you have there from what they were in older ones. In that case, we'll need to sort out the new meanings as well as figure out how to discern the new scheme from the old.

-Uwe-
 
   #5  

DV52

Verified VCDS User
Verified
Joined
May 16, 2014
Messages
3,705
Reaction score
4,125
Location
Melbourne, Australia
VCDS Serial number
C?ID=194404
Uwe,
OK. Can I provide any more information that might assist in confirming (or, not) your hypothesis regarding possible changes to the BCM parameters?
 
   #6  

Uwe

Benevolent Dictator
Staff member
Joined
Jan 29, 2014
Messages
30,459
Reaction score
21,730
Location
USA
VCDS Serial number
HC100001
Probably not, but if there's is, we'll holler.

-Uwe-
 
   #7  

Uwe

Benevolent Dictator
Staff member
Joined
Jan 29, 2014
Messages
30,459
Reaction score
21,730
Location
USA
VCDS Serial number
HC100001
It now being a workday again, I've discussed this Sebastian, who is our expert on the data that the descriptions you're looking at come from. He's aware that file needs to be updated and an update is in the works, although I we can't promise a date on which an updated version will be available.

Please understand, we are not plugged into VWAG's corporate collective; we get NO help from them at all.

-Uwe-
 
   #8  

DV52

Verified VCDS User
Verified
Joined
May 16, 2014
Messages
3,705
Reaction score
4,125
Location
Melbourne, Australia
VCDS Serial number
C?ID=194404
It now being a workday again, I've discussed this Sebastian, who is our expert on the data that the descriptions you're looking at come from. He's aware that file needs to be updated and an update is in the works, although I we can't promise a date on which an updated version will be available.

Please understand, we are not plugged into VWAG's corporate collective; we get NO help from them at all.

-Uwe-
Uwe: Sebastian's reputation extends all the way from the USA to the southern shores of Tasmania! Thanks for the update
 
   #9  

Sebastian

Ross-Tech Employee
Staff member
Ross-Tech Employee
Joined
Feb 13, 2014
Messages
1,978
Reaction score
1,957
Location
Magdeburg, Germany
VCDS Serial number
HN0-nnnnnn
Essentially what this boils down to is that the coding table displayed at this point is a very generic version which applies to all/most models which use this module (or ones like it), at the time our goal was to cover the basics and make sure people had something to work with. Having said that, this was also a time where (as indicated by Uwe) details for these modules were hard to come by (they still are!). However, as usual time plays for us - meaning our own testing and customer feedback usually provides some decent feedback which we usually base our updates on.

Sadly, with this kind of stuff it is a little more complex. Coding tables often vary based on a module's revision, some bits fall off the wagon while others are added/changed. For us this usually means more separation - so it's not really about fixing what you see as being wrong it is coming up with the proper concept based on where and what the changes are. Once that is done it's "only" a work/time problem, meaning it has to be implemented. To give an idea, on a similar project I've spent about 80+ man hours - so bigger projects like that often are being pushed back or otherwise the regular things we need to do fall behind as well. That's why we can't give you a specific time frame - though this specific issue is quite high on the list. :)
 
   #10  

DV52

Verified VCDS User
Verified
Joined
May 16, 2014
Messages
3,705
Reaction score
4,125
Location
Melbourne, Australia
VCDS Serial number
C?ID=194404
Essentially what this boils down to is that the coding table displayed at this point is a very generic version which applies to all/most models which use this module (or ones like it), at the time our goal was to cover the basics and make sure people had something to work with. Having said that, this was also a time where (as indicated by Uwe) details for these modules were hard to come by (they still are!). However, as usual time plays for us - meaning our own testing and customer feedback usually provides some decent feedback which we usually base our updates on.

Sadly, with this kind of stuff it is a little more complex. Coding tables often vary based on a module's revision, some bits fall off the wagon while others are added/changed. For us this usually means more separation - so it's not really about fixing what you see as being wrong it is coming up with the proper concept based on where and what the changes are. Once that is done it's "only" a work/time problem, meaning it has to be implemented. To give an idea, on a similar project I've spent about 80+ man hours - so bigger projects like that often are being pushed back or otherwise the regular things we need to do fall behind as well. That's why we can't give you a specific time frame - though this specific issue is quite high on the list. :)
Sedastian: Life at Ross-Tech (I wasn't aware of thier Germany office) certainly sounds challenging and interesting! Hope that you get the opportunity "to-smell-the-roses" ocassionally - it's important that you do. Thanks for the explanation. I'll await news of the update.
 
Top