Testbench setup?

   #141  

Uwe

Benevolent Dictator
Administrator
Joined
Jan 29, 2014
Messages
48,925
Reaction score
33,653
Location
USA
VCDS Serial number
HC100001
OK - more questions to the knowledgeable folk here to get the BCM on my test-bench to stop lying about the doors being locked (post #130 above);

First question
(and it's a particularly fundamental question - the answer to which I hope does not impinge on any VCDS commercial secrets): Other than operating as the "Fat-controller", what other must-have data does the CAN Gateway provide for successful communications with the VCDS cable. More specifically, I'm trying to understand why when I plug-in the CAN high/low lines from the OBD port on my test-bench directly into the CAN pins on any other control module (with volts connected, of course) - I can't get my HEX-NET to talk. I'm thinking that perhaps the Hex19 module adds/subtracts data from the message header on the other modules - but I'm guessing.

Second Question: Assuming that direct CAN (wiring) connection is possible, what software switch settings should I use on VCDS to maximize the chance of success?

As usual, any response is welcomed - and thanks muchly in advance,

Don
Some modules will communicate directly, without a gateway in between VCDS and the module, and others won't (or may be somewhat flaky). I do not think the Gateway adds or subtracts stuff from/to the message headers, but it can do stuff like bit-rate shifting (not all the modules and CAN buses in the car use the 500 kbps expected on the diagnostic CAN bus!) and buffering / message timing adjustments. The normal sequence VCDS uses is to ask the gateway to open a channel to a particular module. The Gateway then responds with something to the effect of, "OK, I'll do that for you, and you should use the following timing parameters". If that negotiation with the Gateway fails, VCDS will still try the module directly (necessary due to the very few models such as the B7 A4 that have some modules that only talk via CAN but have no proper gateway), however this approach may result in less than optimal timing being used, and may not work at all if the module is using a bit rate other than 500 kbps.

There's also an added consideration: Some modules won't power up (come out of sleep mode and accept a diagnostic session) without other modules being present and telling them, "hey, wake up and smell the coffee" first.

-Uwe-
 
   #142  

FandaTDI

Verified VCDS User
Verified
Joined
Feb 24, 2018
Messages
141
Reaction score
47
Location
Czech Republic
VCDS Serial number
C?ID=204559
Great thread... I´m wondering (question for Jack and it also can be partly an answer for DV52) what about the terminating resistor(s) and the connection of them? Which resistors are the best and has the positioning of them in a circuit something to do/influence on topology of the units(which themselves had theirs own)? The break-out box(-es) has(-ve) also it´s own?
And about full BCM wake-up/coding change,etc. - when I see the faults in 17, isn´t the problem with coding change,etc. related with immo or CP? Or check the pinout again... (some other 31 or 30,...?)
 
   #143  

DV52

Verified VCDS User
Verified
Joined
May 16, 2014
Messages
5,469
Reaction score
5,934
Location
Melbourne, Australia
VCDS Serial number
C?ID=194404
^^^ Fanda: many thanks for taking an interest in my problem and for making the time to put your thoughts in writing- very much appreciated!

As to your question about terminating resistors, great minds think alike (let's not contemplate the other side of this saying;)). I asked this very same question way back on post #1 and based on the sage response of a very bright colleague, I proceeded without resistors with absolutely no adverse effects to date. I'm not sure if some (all?) modules on my test bench have internal impedance matching circuits on their CAN high/low pins - but I haven't observed any comms problems thus far from the absence of external resistors.

As to your other observation about IMMO/CP errors, yes these have been evident since day 1 - but again (for CP errors at least) the fact of their existence hasn't (and as I understand from Sebastian, doesn't) stop access to the modules that are captured within the CP "constellation"
Niether has (or, again from Sebastian's advice - does) CP errors stop my test bench from changing code-string values, or adaptation channel settings in the affected modules.

Don
 
   #144  

1975 Kombi

Verified VCDS User
Verified
Joined
Apr 1, 2014
Messages
93
Reaction score
8
Location
Acton, Ontario, Canada
VCDS Serial number
C?ID=211204
CANBusfor-RNS5102-15-switch.jpg



Is the above setup close?? I must be missing something
 
   #145  

Uwe

Benevolent Dictator
Administrator
Joined
Jan 29, 2014
Messages
48,925
Reaction score
33,653
Location
USA
VCDS Serial number
HC100001
Is the above setup close?? I must be missing something
Yes, you are. What's supposed to go to pins 6 and 14 on the diagnostic connector is the (dedicated) diagnostic CAN from the Gateway, not the Infotainment CAN itself.

Data should flow through the Gateway, not past it. ;)

-Uwe-
 
   #146  

1975 Kombi

Verified VCDS User
Verified
Joined
Apr 1, 2014
Messages
93
Reaction score
8
Location
Acton, Ontario, Canada
VCDS Serial number
C?ID=211204
CANBusfor-RNS5102-15-switchfix.jpg


Any better? lol I still must be missing something.
 
Last edited:
   #147  

DV52

Verified VCDS User
Verified
Joined
May 16, 2014
Messages
5,469
Reaction score
5,934
Location
Melbourne, Australia
VCDS Serial number
C?ID=194404
^^ Brett: Your wiring diagram is progressing well (see my latest PM for further suggestions), but I thought that I would mention here publicly (because it might help others thinking about doing the same) that a vital part of my test bench was the wake-up signal that trigger module turn-on (from a software perspective, rather than the voltage turn-on signal that happens via the T15 point on your WD).

In the first incarnation of my test bench - I underestimated this aspect of the design. It's one of those logical things that all makes sense in hindsight, but it can be overlooked at the early stages of the build. Without intending any offense (and I apologize if you have already considered this of the design, but the wake-up facility ostensibly involves a simulation of the dynamic for the ignition key switch.

I'm not familiar with the RNS510, but I assume that stuff doesn't happen until the key is turned in the lock. Yes, some of the signal to wake-up the infotainment module may come from the resulting T15 voltage which happens at ignition switch-on/off, but if the later model Golf is any indication, there is also dialogue that happens over the CAN bus at ignition switch-on (in the case of the 1K chassis, I suspect it's the Comfort CAN bus).

On my Test Bench, the CAN dialogue to wake-up various modules necessitated installation of the steering wheel module @ address hex16 - because the ignition key barrel is directly connected to this module. I think from memory that RT folk found that they had to also simulate the ignition key on their test-bench - but I can't remember if they did this via the hex16 module.

Anyhow, might be worth looking at the WD to see if the same applies for the particular vehicle that has the RNS510

Don

PS: the other thing that you might want to consider is the K line connection. From my scant understanding of the 1K chassis, I think that it uses this wire and it might not apply for just the 2 x modules that you are considering. But if you intend to increase the module count, it could be a confounded- perhaps
 
   #148  

Uwe

Benevolent Dictator
Administrator
Joined
Jan 29, 2014
Messages
48,925
Reaction score
33,653
Location
USA
VCDS Serial number
HC100001
Any better? lol I still must be missing something.
Yes. Now let's cover basics:

Can you access the Gateway itself with VCDS?

-Uwe-
 
   #150  

Uwe

Benevolent Dictator
Administrator
Joined
Jan 29, 2014
Messages
48,925
Reaction score
33,653
Location
USA
VCDS Serial number
HC100001
Nope. It tries but does not connect to the gateway.
Well, getting it to talk to the Gateway is step number 1. But I don't see anything obviously wrong with the wiring you now have between the diagnostic socket and the Gateway.

Is it safe to assume you have the switch for Terminal 15 closed?

-Uwe-
 
   #151  

siLc

Verified VCDS User
Verified
Joined
Jul 9, 2014
Messages
1,804
Reaction score
1,531
Location
Tallinn, Estonia
VCDS Serial number
C?ID=330192
Invested some 4-5hrs and made my own little testbench out of leftover factory wiring and connectors. Powered it by an old 500W ATX computer power supply. Its for setting up 3Q098065x Lane Assist cameras, MQB-style PDC modules and instrument clusters with the 32pin blue connector on the VW PQ platform. It has provisions to add stuff on Infotainment and Comfort CAN busses.

Picture

I wired it so when powered up, terminal 15 is always on. This shouldn't pose a problem with any said modules which take a direct terminal 15 input to work correctly? I only have a gateway at the moment to test with and it talked fine.
 
Last edited:
   #152  

Uwe

Benevolent Dictator
Administrator
Joined
Jan 29, 2014
Messages
48,925
Reaction score
33,653
Location
USA
VCDS Serial number
HC100001
Picture

I wired it so when powered up, terminal 15 is always on. This shouldn't pose a problem with any said modules which take a direct terminal 15 input to work correctly? I only have a gateway at the moment to test with and it talked fine.
Picture link doesn't work for me.

Most of our test-bench setups do not have a separately switchable Terminal 15 either; power them on, and both 30 and 15 are on. It usually only matters when modules do "house keeping" after terminal 15 turns off. For example, some older ECUs would only store changes to adaptation channels when that happened, and they obviously couldn't do that if Terminal 30 shut down at the same time.

-Uwe-
 
   #153  

siLc

Verified VCDS User
Verified
Joined
Jul 9, 2014
Messages
1,804
Reaction score
1,531
Location
Tallinn, Estonia
VCDS Serial number
C?ID=330192
Picture link doesn't work for me.

Most of our test-bench setups do not have a separately switchable Terminal 15 either; power them on, and both 30 and 15 are on. It usually only matters when modules do "house keeping" after terminal 15 turns off. For example, some older ECUs would only store changes to adaptation channels when that happened, and they obviously couldn't do that if Terminal 30 shut down at the same time.

-Uwe-
I corrected the link - (hopefully) it works now.

Nice to know. For my purpuses, I don't think I'll be hooking up any ECU-s.
 
  • Like
Reactions: Uwe
   #154  

DV52

Verified VCDS User
Verified
Joined
May 16, 2014
Messages
5,469
Reaction score
5,934
Location
Melbourne, Australia
VCDS Serial number
C?ID=194404
^^^ hmm......... picture is not available to me either - not sure if it's because stuff happens differently in the southern hemisphere (like water draining in a sink), but that's quite a long URL string in your post!!!;)
Don

h ttps://lh3.googleusercontent.com/u_3o-D25Pa6C2nJk3iPTBjPW5hibfIfEgyVpd2nuKOgJKieV7qJWS2TUI5XzdgufzuQ8L7w6Jlolv1DPQX9jgQZG8HOL3x2r9-JGFv3mL6QhV1N7YnqikGzC4dmA0i85cBFtedHwrHEVWH1U4T8M8dO9YeF3ksZb4ynSbzAShbJYypWBfzZirdD6c_yN38rclvnVQ9bPYcHf6Bq9973mfy4Khh6ABo09huE8E5blc3i3Pugr8eAzlOTagSRR7Rlce92Dkzcc3EsbLQIpvqmXu86FjZIfOznPbUpkwNzb7s7BcG7C304a62wUKGVyCsNSnEX5RSDXqlAfZ9scuRx0WkciLqZEN0BSZzYYSRaIohAIidyUo6BEgcj-sWNcUYYlYJZ-tklKwD_9GjbGNzzlGCPqpiD9Mut6aCzVGxi5i-Cm6cGO-roTxhELHpmGmlSOoT4mXSLCK_oLtQYuUhfuVO3xSDxgjXzhjfrYB5yelVVhWWTjBe0UFWhJh5tlNrLLmbYdpb7R8e8GRW-uPwadnS8KL_Li-aM6QOraN1pElsJdTgwRbmpyL80mkZilFkvcpF7MVsFxokiEI2SAzCsK1PVXAzNd4IDdzRm8PrB-J-N4seoymg4xgNm4u2CDjKSXyVinieAlYkjGoA-H9qJOgDALIzA9C3_b=w2414-h1297-no
 
   #155  

siLc

Verified VCDS User
Verified
Joined
Jul 9, 2014
Messages
1,804
Reaction score
1,531
Location
Tallinn, Estonia
VCDS Serial number
C?ID=330192
That's just Google Photos giving me a hard time once again...

IMG_0507.JPG


Most PQ modules have power/GND wire gauge specified as 0,5mm2 but some have larger 1,5 to 2,5mm2. An example is the Passat B6/B7/CC CCM module. With nothing attached, would this really need 2,5mm2 gauge wiring?
 
Last edited:
  • Like
Reactions: Uwe
   #156  

Uwe

Benevolent Dictator
Administrator
Joined
Jan 29, 2014
Messages
48,925
Reaction score
33,653
Location
USA
VCDS Serial number
HC100001
That's just Google Photos giving me a hard time once again...
Google photos does not seem to be forum-friendly at all.

Most PQ modules have power/GND wire gauge specified as 0,5mm2 but some have larger 1,5 to 2,5mm2. An example is the Passat B6/B7/CC CCM module. With nothing attached, would this really need 2,5mm2 gauge wiring?
I don't think so. The reason it has such large wiring in the car is that it powers lots of other stuff; lights and so on. If you just want to talk to it on the bench, you only need to power the module itself, not all the down-stream stuff that the module powers.

-Uwe-
 
   #157  

1975 Kombi

Verified VCDS User
Verified
Joined
Apr 1, 2014
Messages
93
Reaction score
8
Location
Acton, Ontario, Canada
VCDS Serial number
C?ID=211204
That's just Google Photos giving me a hard time once again...

IMG_0507.JPG


Most PQ modules have power/GND wire gauge specified as 0,5mm2 but some have larger 1,5 to 2,5mm2. An example is the Passat B6/B7/CC CCM module. With nothing attached, would this really need 2,5mm2 gauge wiring?

1K0 gateway???
 
   #160  

_Val

Verified VCDS User
Verified
Joined
Nov 7, 2017
Messages
191
Reaction score
144
Location
Latvia
VCDS Serial number
C?ID=356659
2) CAN-High/Low for Powertrain, Infotainment, Comfort, Extended, Running Gear makes up for 10 pins - that leaves CAN-Diagnostics and CAN-Instruments which brings us up to 16 pins already.
Actually it's 7 pairs of wires (not 8) :D Please, explain what did I miss. Building similar box with DB25 right now.
 
Back
Top