Door controlers and window auto up/down Golf 7.5

   #1  

MaticMD

Verified VCDS User
Verified
Joined
Sep 20, 2019
Messages
25
Reaction score
18
Location
Slovenia
Hello, I would like to brainstorm here with you about my problem.

I have Golf 7.5. One day I removed and reinserted the cables in the driver door controller and my auto up/down function stopped working only on the front driver window.
I tried button hold up/down, reseting adaptation, and other reset/adapt options in VCDS, nothing worked.
Later I changed the controllers (upgrade for ambient lights) and the problem is still there.
I still have warranty, but they could not help me, because their ODIS doesnt recognize the controllers.

Any body have any ideas how to solve this?
How does this work, where this function comes from, window switch, controller, window regulator?
I dont have this second click after driver window is in full up or down position and still holding the switch. On other 3 windows, you can hear that click. Where does this click comes from?
 
   #2  

TBAx

Verified VCDS User
Verified
Joined
Dec 3, 2016
Messages
686
Reaction score
590
Location
Germany
VCDS Serial number
C?ID=287144
Not really a tweak, but anyhow. As long as you didn't kill the parametrization (which could happen when you used basic settings in the module 42) the way is to just hold the window regulator in the following way:
  1. push and hold DOWN until the window is fully open
  2. release DOWN and push it one more time
  3. push and hold UP until the window is fully closed
  4. release UP and push it one more time
This sould store the end stops and the automatic down/up should work again.
 
   #3  

DV52

Verified VCDS User
Verified
Joined
May 16, 2014
Messages
4,016
Reaction score
4,508
Location
Melbourne, Australia
VCDS Serial number
C?ID=194404
@MatricMD: Hi On a mk7.5, all of the equipment related to the driver side windows is connected directly to (and controlled by) the hex42 module. Here's a very simplified WD for a mk7.5 LHD showing the wiring arrangement

ixQZvBQ.png

As you can see - it's a very direct and self-contained arrangement.

Given that the only switch that is problematic is the front left door window (and assuming that the newly fitted J386 is fully compatible with the OEM arrangement) why not grab a multi-meter and test the switch-bank pins with the driver window switch operated. It's not clear from the WD, which pin operates the front driver window on E512, but you should see a change of state on one of these pins. When you identify the correct pin, check voltages on the mating pin (same wire colors) on the 32 x pin connector on the actual door card.

Don

PS: If my suggestion doesn't help, perhaps post-up an auto-scan of the car

Don
 
Last edited:
   #4  

MaticMD

Verified VCDS User
Verified
Joined
Sep 20, 2019
Messages
25
Reaction score
18
Location
Slovenia
Thanks for ideas.
I believe seeing autoscan will not help here.

@TBAx I tried that and it didnt help, It is quite possible that I messed up the parameters with basic settings. I have no idea how to solve this, because at my dealer ODIS throws an error.

@DV52 right now it is very cold in our country, so I dont want to remove any plastic parts from my car. Any way, I think it should be ok. One switch has three wires, one is ground, second window up + , third window down + . Window is working so there should be nothing wrong with the wiring. I am not sure what the swith does when you pull it all the way up? Does it hold the window up + for you until the window regulator signals that the widnow is closed? Maybe the switch is bad?
 
   #5  

Bruce

Active Member
Staff member
Ross-Tech Employee
Joined
Jan 30, 2014
Messages
1,644
Reaction score
2,961
Location
Near Philadelphia, PA, USA
VCDS Serial number
--------
I believe seeing autoscan will not help here.
An Autoscan gives the user community here an idea of how your car is equipped so they might be able to make further suggestions. How could supplying said Autoscan be problematic for you other than your having to go outside in the cold and run the scan?
 
   #7  

MaticMD

Verified VCDS User
Verified
Joined
Sep 20, 2019
Messages
25
Reaction score
18
Location
Slovenia
@Bruce it is not a problem, I just assumed that autoscan would not help to gather more information about my problem. Looks like I was wrong.
@downtime I didnt think of that

Form now on I wont make any more asumptions and post the autoscan first.

Code:
Thursday,21,January,2021,17:15:59:30226
VCDS -- Windows Based VAG/VAS Emulator Running on Windows 10 x64
VCDS Version: 20.12.0.0 (x64)  HEX-V2 CB: 0.4529.4
Data version: 20201124 DS322.0
www.Ross-Tech.com


VIN: WVWZZZAUZKP038555   License Plate: 21.1.2021
Mileage: 51670km-32106mi   Repair Order:



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


Chassis Type: AU-VW37 (3Q0)
Scan: 01 02 03 08 09 10 13 15 17 19 42 44 52 5F A5

VIN: WVWZZZAUZKP038555   Mileage: 51670km-32106miles

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
13-Auto Dist. Reg -- Status: OK 0000
15-Airbags -- Status: OK 0000
17-Instruments -- Status: OK 0000
19-CAN Gateway -- Status: Malfunction 0010
42-Door Elect, Driver -- Status: OK 0000
44-Steering Assist -- Status: OK 0000
52-Door Elect, Pass. -- Status: OK 0000
5F-Information Electr. -- Status: OK 0000
A5-Frt Sens. Drv. Assist -- Status: OK 0000
-------------------------------------------------------------------------------
Address 01: Engine (J623-DFGA)       Labels:. 04L-907-309-V1.clb
   Part No SW: 04L 906 026 NF    HW: 04L 907 309 P
   Component: R4 2.0l TDI   X25 9528 
   Revision: B4X25---   
   Coding: 01250412036405082000
   Shop #: WSC 92521 052 00000
   ASAM Dataset: EV_ECM20TDI01104L906026NF 004010
   ROD: EV_ECM20TDI01104L906026NF_VW37.rod
   VCID: 7BA3F6D8F36201F3261-802E

No fault code found.
Readiness: 0 0 0 0 1

-------------------------------------------------------------------------------
Address 02: Auto Trans (J743)       Labels:. 0BH-927-711.clb
   Part No SW: 0GC 300 043 T    HW: 0GC 927 711 H
   Component: TVS DQ381     H06 9999 
   Revision: 00H06V09   
   Coding: 0014
   Shop #: WSC 00000 000 00000
   ASAM Dataset: EV_TCMDQ381061 001
   ROD: EV_TCMDQ381061.rod
   VCID: 382929D482D4EAEB8B3-806C

No fault code found.

-------------------------------------------------------------------------------
Address 03: ABS Brakes (J104)       Labels: 5Q0-907-379-IPB-V1.clb
   Part No SW: 5Q0 614 517 DE    HW: 5Q0 614 517 AD
   Component: ESC           H25 0524 
   Revision: 00000000    Serial number: 62798000002843
   Coding: 01FA62A124230974477C060560C82980462490E26006947338625078C222430B00000012121212B835351919323200
   Shop #: WSC 12345 123 61029
   ASAM Dataset: EV_Brake1UDSContiMK100IPB 037009
   ROD: EV_Brake1UDSContiMK100IPB_037_VW37.rod
   VCID: 77ABEAE8CF4A2593429-8022

No fault code found.

-------------------------------------------------------------------------------
Address 08: Auto HVAC (J255)       Labels:| 5G0-907-044.clb
   Part No SW: 5G0 907 044 CE    HW: 5G0 907 044 CE
   Component: Climatronic   H04 1801 
   Revision: 00001K08   
   Coding: 00020104202110011005004000101022
   Shop #: WSC 00028 028 00026
   ASAM Dataset: EV_ACClimaBHBVW37X 006145
   ROD: EV_ACClimaBHBVW37X_006_VW37.rod
   VCID: 6C81C584860C964BBFB-8038

   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-V2.clb
   Part No SW: 5Q0 937 084 DA    HW: 5Q0 937 084 CD
   Component: BCM MQBAB B   H38 0273 
   Serial number: 00001828900588
   Coding: 000000000000000000000000000000000000000000000000000000000000
   Shop #: WSC 00028 028 00026
   ASAM Dataset: EV_BCMMQB 019001
   ROD: EV_BCMBOSCH_019_VW37.rod
   VCID: 7AADF3DCFC5838FB3D7-802E

   Wiper motor control module:
   Subsystem 1 - Part No SW: 5G1 955 119 A    HW: 5G1 955 119 A  Labels: 5QX-955-119-V1.CLB
   Component: WWS    180913  043 0551
   Serial number:         180917224719
   Coding: 0E4DDD

   Rain/Light Recognition Sensor:
   Subsystem 2 - Part No SW: 5Q0 955 547 B    HW: 5Q0 955 547 B  Labels: 5Q0-955-547.CLB
   Component: RLHS  052 0107
   Serial number: S7Y18M10D12H17M51S57
   Coding: 05A8DD

   Steering Column Switch:
   Subsystem 3 - Part No SW: 5Q1 953 507     HW: 5Q1 953 549
   Component: J527 SMLS MQB  004 0060
   Serial number: 00000018101808490440

No fault code found.

-------------------------------------------------------------------------------
Address 10: Park/Steer Assist (J446)       Labels:| 5Q0-919-294.clb
   Part No SW: 5QA 919 294 C    HW: 5QA 919 294
   Component: PDC 8 KanalH07 0050 
   Serial number: 000308418618284
   Coding: 0471051811
   Shop #: WSC 00028 028 00026
   ASAM Dataset: EV_EPHVA18AU3700000 009039
   ROD: EV_EPHVA18AU3700000.rod
   VCID: 4CC16504E64C764BDFB-8018

No fault code found.

-------------------------------------------------------------------------------
Address 13: Auto Dist. Reg (J428)       Labels:| 3Q0-907-572.clb
   Part No SW: 5Q0 907 572 P    HW: 3QF 907 572 A
   Component: ACC BOSCH MQB H11 0682 
   Coding: 3318076115FFC728009C811580400600000000000004000004
   Shop #: WSC 12345 123 61029
   ASAM Dataset: EV_ACCBOSCHVW416 002008
   ROD: EV_ACCBOSCHVW416_002_VW37.rod
   VCID: 44D14D24CE1CBE0B17B-8010

No fault code found.

-------------------------------------------------------------------------------
Address 15: Airbags (J234)       Labels:| 5Q0-959-655.clb
   Part No SW: 5Q0 959 655 BH    HW: 5Q0 959 655 BH
   Component: AirbagVW21    006 0336 
   Serial number: 003VVR4MPJPF
   Coding: 98CCC000000000005C0000CF000800000065
   Shop #: WSC 00028 028 00003
   ASAM Dataset: EV_AirbaVW20SMEVW37X 002158
   ROD: EV_AirbaVW20SMEVW37X_VW37.rod
   VCID: 074B9A28BFAA5513329-8052

   Crash sensor for side airbag: driver side:
   Subsystem 1 - Part No SW: -----------    HW: 480 001 110 18
   Component: SideSensor_Df  001 0887
   Serial number: 3570000000037929353D
   Coding: 2D2D2D

   Front Passenger's Side Airbag Crash Sensor:
   Subsystem 2 - Part No SW: -----------    HW: 480 001 110 18
   Component: SideSensor_Pf  001 0887
   Serial number: 358000000008A971253I
   Coding: 2D2D2D

   Rear Side Airbag Crash Sensor (on driver's side):
   Subsystem 3 - Part No SW: -----------    HW: 480 400 810 18
   Component: SideSensor_Dr  004 6149
   Serial number: 3510001302B76CF4237$
   Coding: 2D2D2D

   Passenger side rear thorax airbag crash sensor:
   Subsystem 4 - Part No SW: -----------    HW: 480 400 810 18
   Component: SideSensor_Pr  004 6149
   Serial number: 3520001302B76CF4B804
   Coding: 2D2D2D

   Crash sensor for front airbag: driver side:
   Subsystem 5 - Part No SW: -----------    HW: 480 401 310 18
   Component: FrontSensor_D  003 6149
   Serial number: 3550001A52DA6D9266BL
   Coding: 2D2D2D

No fault code found.

-------------------------------------------------------------------------------
Address 17: Instruments (J285)       Labels:| 5G0-920-XXX-17.clb-SRI3
   Part No SW: 5G1 920 741 D    HW: 5G1 920 741 D
   Component: KOMBI         211 2500 
   Coding: 07A529086780000801883A031401000000000000
   Shop #: WSC 12345 123 61029
   ASAM Dataset: EV_DashBoardVDDMQBAB 009065
   ROD: EV_DashBoardVDDMQBAB_009_VW37.rod
   VCID: 2809F99452747A6B1B3-807C

No fault code found.

-------------------------------------------------------------------------------
Address 19: CAN Gateway (J533)       Labels:| 3Q0-907-530-V1.clb
   Part No SW: 3Q0 907 530 Q    HW: 3Q0 907 530 C
   Component: GW MQB High   518 5344 
   Serial number: 13101810520466
   Coding: 030100045F086800FA0002481C0F00010001070000000000000000000000
   Shop #: WSC 00028 028 00026
   ASAM Dataset: EV_GatewNF 013023
   ROD: EV_GatewNF_VW37.rod
   VCID: 3D2738C0ADF6CFC3585-8068

   Generator:
   Component: 1-01-13-01-04 

   Multifunction steering wheel control module:
   Subsystem 2 - Part No SW: 5G0 959 442 AB    HW: 5G0 959 442 AB  Labels: 3C8-959-537.CLB
   Component: E221__MFL-DC1  H17 0052
   Serial number: 39180002352190108463
   Coding: 2FFFFF

   Battery Monitoring Control Module:
   Subsystem 3 - Part No SW: 5Q0 915 181 K    HW: 5Q0 915 181 K
   Component: J367-BDMHella  H10 9070
   Serial number: 5156179304         

1 Fault Found:
8531970 - Quiescent Current
          U1406 00 [008] - Too High
          [Ruhestrom oberer Grenzwert überschritten]
          Intermittent - Confirmed - Tested Since Memory Clear
             Freeze Frame:
                    Fault Status: 00000001
                    Fault Priority: 7
                    Fault Frequency: 3
                    Reset counter: 55
                    Mileage: 51558 km
                    Date: 2021.01.19
                    Time: 23:48:29

                    Terminal 30 power supply: 12.1 V
                    Terminal 15: OFF


-------------------------------------------------------------------------------
Address 42: Door Elect, Driver (J386)       Labels:| 5QX-959-X93-42.clb
   Part No SW: 5Q0 959 593 E    HW: 5Q0 959 593 B
   Component: TSG FS        020 0041 
   Serial number: 280715BGR07384
   Coding: 001103200002080000001000
   Shop #: WSC 12345 123 61029
   ASAM Dataset: EV_DCUDriveSideEWMAXKLO 006003
   ROD: EV_DCUDriveSideEWMAXCONT.rod
   VCID: 43D34E38CB12B9332E1-8016

   Rear Driver Side Door Control Module:
   Subsystem 1 - Part No SW: 5Q4 959 811 F    HW: 5Q4 959 811 F  Labels: 5QX-959-81X-V1.CLB
   Component: Fond FHSG DRV  010 0004
   Serial number: 00000000000010292407
   Coding: 010000

No fault code found.

-------------------------------------------------------------------------------
Address 44: Steering Assist (J500)       Labels:| 5Q0-909-144.clb
   Part No SW: 5Q0 909 144 AB    HW: 5Q0 909 144 AA
   Component: EPS_MQB_ZFLS  131 1082 
   Coding: 111F0000
   Shop #: WSC 00028 028 00026
   ASAM Dataset: EV_SteerAssisMQB 015157
   ROD: EV_SteerAssisMQB_015.rod
   VCID: 74B1DDE4DE3C4E8B67B-8020

No fault code found.

-------------------------------------------------------------------------------
Address 52: Door Elect, Pass. (J387)       Labels:| 5QX-959-X92-52.clb
   Part No SW: 5Q0 959 592 E    HW: 5Q0 959 592 B
   Component: TSG BFS       020 0041 
   Serial number: 310715BGU04733
   Coding: 001101200A00040000001000
   Shop #: WSC 12345 123 61029
   ASAM Dataset: EV_DCUPasseSideEWMAXKLO 006003
   ROD: EV_DCUPasseSideEWMAXCONT.rod
   VCID: 42DD4B3CD408B03B257-8016

   Rear Passenger Door Control Module:
   Subsystem 1 - Part No SW: 5Q4 959 812 F    HW: 5Q4 959 812 F  Labels: 5QX-959-81X-V1.CLB
   Component: Fond FHSG PSG  010 0004
   Serial number: 00000000000010289930
   Coding: 090000

No fault code found.

-------------------------------------------------------------------------------
Address 5F: Information Electr. (J794)       Labels:| 5G0-035-MIB-STD2.clb
   Part No SW: 3Q0 035 819 C    HW: 3Q0 035 819 C
   Component: MU-S--ER      H41 0472 
   Serial number: VWZAZ2U1231377
   Coding: 02731000FF0000005111000100080A001F050FC40120010001
   Shop #: WSC 12345 123 61029
   ASAM Dataset: EV_MUStd4CTSAT 001022
   ROD: EV_MUStd4CTSAT_VW26.rod
   VCID: 313F14F061AE3BA3CCD-8064

   Display and control head 1 for information electronics:
   Subsystem 1 - Part No SW: 5G6 919 605     HW: 5G6 919 605
   Component: ABT_Std-2  H52 8130
   Serial number: VWZ6ZJV2830893     

No fault code found.

-------------------------------------------------------------------------------
Address A5: Frt Sens. Drv. Assist (R242)       Labels:| 3Q0-980-65X-A5.clb
   Part No SW: 3Q0 980 654 L    HW: 3Q0 980 654 A
   Component: MQB_B_MFK     H12 0610 
   Serial number: 04071915P11366
   Coding: 0003070000000401002200448150890098000E00002000
   Shop #: WSC 12345 123 12345
   ASAM Dataset: EV_MFKBoschMQBB 002041
   ROD: EV_MFKBoschMQBB_002.rod
   VCID: 40D94134DA04A22B333-8014

No fault code found.
 
End----(Elapsed Time: 01:20, VBatt start/end: 11.7V/11.7V. VIgn 11.7V)-----
 
   #8  

Bruce

Active Member
Staff member
Ross-Tech Employee
Joined
Jan 30, 2014
Messages
1,644
Reaction score
2,961
Location
Near Philadelphia, PA, USA
VCDS Serial number
--------
I just assumed
We make assumptions all the time don't we? How often are our assumptions correct or accurate?

When a person with the knowledge and skill of @DV52 makes a request, I for one will likely honor that request for I know he knows far more than I. In this forum, such requests should be honored for most of the people trying to help are not compensated. Their help is freely given such that the community of knowledge might expand. Help them help you.

Thanks for taking the time to post. Give some time for others to take a look and postulate some ideas.
 
   #9  

MaticMD

Verified VCDS User
Verified
Joined
Sep 20, 2019
Messages
25
Reaction score
18
Location
Slovenia
You are right. I never meant to look like I disrespect DV52. I can say that most knowledge about MQB coding I have is from his forum posts. He is always here sharing his knowledge for free and that is something I appreciate a lot.
 
   #10  

downtime

Verified VCDS User
Verified
Joined
May 27, 2017
Messages
2,089
Reaction score
1,318
Location
Finland
VCDS Serial number
C?ID=280813
I don't see any apparent problem with the modules.

Do you know from which car the replacement modules are from? If they're not from Golf it might explain the problem with the basic setting. It does not complain though that the door module is missing basic settings
 
   #11  

MaticMD

Verified VCDS User
Verified
Joined
Sep 20, 2019
Messages
25
Reaction score
18
Location
Slovenia
I dont know from which car are they. Part numbers are the same as in my friends Golf 7.5.

When brainstorming it is good to keep in mind, that I had the same problem before with my stock controllers. Maybe the controllers are not the problem. It is just that because of the new controllers the dealer cant help me, ODIS throws an error for not matching the VIN.

And because of that I would like to find out how this window auto up/down works, so I can exclude possible switch, controller or window regulator failure.
 
   #12  

downtime

Verified VCDS User
Verified
Joined
May 27, 2017
Messages
2,089
Reaction score
1,318
Location
Finland
VCDS Serial number
C?ID=280813
What I'm after is that to my understanding the dataset contains limit parameters for the window lift motor as well and if it's from a different car the window size and shape is different thus the limit params don't match. You won't be able to make basic settings for auto up down to work as it will never reach the programmed extremes or it goes way over them. Do you understand what I'm after?

Then even the part numbers are the same it does not say anything. Same part numbers are used across VAG range. Skoda, Seat, VW and Audi all share the same part numbers but the differences are made with software and in this case with the datasets.
Cost reduction at it's most extreme :D

You can parameterize the unit even if it's not from your car / VIN range, but most likely the official dealer is not going to do it.
 
   #13  

MaticMD

Verified VCDS User
Verified
Joined
Sep 20, 2019
Messages
25
Reaction score
18
Location
Slovenia
Yes I totally understand what you are saying.

I cant imagine then why the passenger side works without a problem. Everything is ok, you can even hear second click when you hold full up and full down position.

On the drivers side there is no second click, just the first click for stopping the motor at full up or down position. And of course the same behaviour was there even before replacing the controllers.

If there are issues with parameters, both controllers would have them? What do you think?
 
   #14  

DV52

Verified VCDS User
Verified
Joined
May 16, 2014
Messages
4,016
Reaction score
4,508
Location
Melbourne, Australia
VCDS Serial number
C?ID=194404
@Bruce it is not a problem, I just assumed that autoscan would not help to gather more information about my problem. Looks like I was wrong.
@downtime I didnt think of that

@MaticMD: Thanks for the auto-scan. I suspect (hope, really) that it might contain a plausible explanation for your window regulator problem - maybe?

So, from your auto-scan, here's a better view of the long-code strings on both your driver and passenger side door modules:

ByteDriver-sideDriver-sidePassenger-sidePassenger-side
HexBinaryHexBinary
000000000000000000000
111000100011100010001
203000000110100000001
320001000002000100000
400000000000A00001010
502000000100000000000
608000010000400000100
700000000000000000000
800000000000000000000
900000000000000000000
1010000100001000010000
1100000000000000000000

@downtime conversation about the module dataset is spot-on (I reckon). I've highlighted Byte 6 in the table above to show that there is an apparent difference between the coding of Driver/Passenger modules.

Now, normally different Byte values across both modules is not unusual on MQB platform vehicles, but the software switches on Byte 6 selects the window regulator Dataset that the module uses to control the "fast-glass".

Remembering that binary numbers are read from right-to-left and the right-most digit is Bit 0 - I hope you can agree with the following observations from the table above:
  • on your Passenger-side module, Byte 6, Bit 2 is set- which means that the lower-nibble has a value hex04, which means that the module is using Window Regulator Dataset 1.
  • on your Driver-side module, Byte 6, Bit 3 is set - which means that the lower-nibble has a value hex08, which means that the module is using Window Regulator Dataset Auto-recognition.

My suspicion (guess, really) is that the hex42 module might be having problems selecting the correct Dataset when in AUTO mode. I'm not sure why this might be happening. Perhaps, there is a degree of un-OEM-ness about this non-standard module that's causing confusion with this part of its operation (again, just a guess)

So - given your statement that the hex52 module is operating OK, it's probably safe to assume that Dataset 1 is also the appropriate protocol for the hex42 module.

Therefore, try changing Byte 6 on the hex42 module to hex04.

Don

PS: here's the relevant long-code helper screen FYI:
HXRGoVa.png
 
   #15  

MaticMD

Verified VCDS User
Verified
Joined
Sep 20, 2019
Messages
25
Reaction score
18
Location
Slovenia
Another knowledge bomb from DV52 :)

I did it, auto up down works now. But it was something else, not a wrong data set. I remember trying all data sets some time ago and it did not work.

I sat in the car today for more than an hour and trying different things. I have put all measuring vales for front window in the row and record up/down and auto up/down sequence, so I could show them here for you to see. Even window motor overhated 2 times in the process. I saw that in the mesauring values, at first I thought that I f.. something up for good.
After excluding switch and window regulator failure, DV52 post got in my head. I have to compare the coding between the two controllers. Of course they not 100% the same, but I still compared every bit and find the culprit. It was "light tank" that had a tick in the box on the driver side, but not on the passenger side. Looks like I put a tick here on my previus controller when trying to find out if I have any pins for the lights in it. When I removed that and initiate window adaptation, the problem was solved.

I realy like brainstorming here with you. Without this, I could not imagine how would I solve this problem. I always had in my head that there is some mechanical or parameter problem that I could not solve with VCDS.

Thank you all and special thanks to DV52 for putting my mind in a different direction.
 
Top