Struggling to add items to Gateway (19)

Hi Don,

Thanks for your reply,

I'll start with the RVC as I've done more fault finding on that, the CAN lines are currently wired to pins 6&12 on the blue connector for the Quadlock on the MIB(2.5) unit.

I'll be totally honest I'm not sure if that's on the Convenience or infotainment bus, I was following a guide by mr-fix.

I've checked both the power and ground, power is via an existing line as I previously had RVC low wired in and it was working prior to this install, the ground is currently temporarily rigged up to the tailgate earth for testing. I've got voltage, and I've continuity tested the CAN lines back to the MIB to be sure they're the right way around and not broken.

I did try swapping them too just for completeness but still no dice.

On the 20 modules, it was something I read online about Low/Medium/High modules supporting so many modules, as you say I've already got 30 modules so it didn't make much sense, but when you can't get something to work you start to fear the worst and come up with convoluted ways it could be true. Glad it sounds like it's not as running the cables was a mission.

Wondering if there's something I'm missing, could be a dead unit, but seemed odd that I had same problem with 2 different modules. I've done a few bits of coding but this is the first time I've added modules so concerned I missed a step maybe. So much info on the internet, never sure what to trust, I read somewhere that Gateways are locked for adding new modules on certain MQB models? No idea If that's true.

Hi Don

Apologies, mistake in my response, the CAN wires are terminated on on the Grey connector, not blue as I stated. However on further inspection it appears I flipped the connector when I turned it over and accidentally tapped T12/1 & 7 rather than 6 & 12.

The video connections I haven't touched as they were already present.

I've fixed that and I can now access the camera, thanks a lot, sometimes you need a push to check it a 3rd time.

I'm getting a few fault codes on it including B201000, I'll do some research as I've seen stuff about that before on the forum I think.

I'll have a look at the TPMS wiring later.

Thanks again for your help!

^^^hmm......... NO, paramaterisation and calibration are different.


"Calibration" solves the problem of small variances in each car that rolls out-of the vehicle factory. As you will appreciate, the fundamental goal when building vehicles on a production-line is for each car to be an exact clone of every other car. Whilst a global conglomerate like VAG is able to largely succeed in this objective - nevertheless, individual vehicles do have slight variances. There are lots of examples of these differences - but a common example is in modules that use distance measurement transducers. In these modules, it's often necessary to initialize the distance measurement function for each individual car. Hence the "calibration" procedure!

• Gareth's 2019 eGolf - 01730101E2002017040062
• 2019 mk7.5 UK       - 0184010162002017000040
• 2016 e-Golf USA      - 01840102C2002217000042

• 01840101E2002017000042

hmm..... the high-line camera talks to the CAN network for ALL of its operations, so it receives/sends information from/to a number of other modules. For example, whereas the low-line camera is activated by a physical wire that's connected to the reversing light - the high-line camera gets the signal that reverse-gear has been selected from the CAN bus directly. Similarly, the high-line camera receives the turn-OFF signal when the car's forward speed is beyond the threshold value directly as a CAN message.

In this case and looking through your SCAN report - none of the other modules in this car are complaining that they are having problems with the camera (the thermal management fault is unrelated)

The calibration procedure should be able to be done with OBD11 -  and you can buy the domino board on-line (google it)

Maybe - but if it was due to "another module", I suspect that it's because the 6C module is incorrectly coded and it's expecting a response from another module that is NOT installed in the car (I'm guessing of course)

I wouldn't expect  that the 2 x golfs wiuld have different files - again check with seller

So I seem to have found the coding error that was causing the U112100 fault.

I've set "equipment_automatic_transmission" to not installed. The fault no longer is generated, however upon activating this again the fault immediately returns.

My guess is that the gearbox in my eGolf isn't the "auto box" (probably DSG) it's describing.

I also attempted to calibrate the unit with both VCDS and OBDeleven, and I can't seem to find a security access code that works and allows the function to proceed.

Any information on security access codes or the calibration on Golf 7 would be appreciated, the info I found was for Skoda Superb or VW Tuareg.

mathi9020010 did you just leave your camera uncalibrated?

Well I guess that makes sense regarding the automatic gearbox coding bit for the camera.

The security access code 20103 didn't seem to work, I actually tried the list of codes in that post yesterday before your reply.

I also stumbled across this post, which said if you change service to EOL, prior to entering the security code 801129 that it would then accept the code.

This does seem to work, however although the code is accepted I can't seem to get the calibration process to begin.

I tried the following settings under basic settings and hitting "go" but I just get an immediate "oops something went wrong". Nothing changes on the screen in the car.



I think I'm maybe missing something to tell the camera it's in "calibration mode"

I've not been able to find any walk-thrus/demo's of the calibration process in OBDeleven, only lost of people saying you can't do it. I also tried in VCDS but couldn't find a way to get it into EOL mode to accept the security access code.