Skip to content

Skoda Superb II - Total Ignition Dead (No Terminal 15) After Alternator & Battery Replacement - Out of Ideas!

Featured Replies

Hi everyone,

New to the forum but I really need your help.

I’m completely stuck on a Skoda Superb II 2.0 TDI (170Hk) DSG6 (manual ignition key, NO electronic steering lock/ELV) and I’m officially out of ideas. I really hope someone here can point me in the right direction.

The Backstory:
The car died while driving due to a failed alternator (battery drained completely). The car was driven home, parked, and the battery was disconnected. While replacing the alternator, a faulty xenon ballast was also replaced. A brand-new battery was installed. Upon reconnecting the battery terminals (there was a normal minor spark), the car's ignition went completely dead.

Current Symptoms:

  • No Terminal 15: Turning the key does absolutely nothing. The instrument cluster (dashboard) is 100% pitch black—not even the center MFD screen turns on or gives any warnings.

  • Working Comfort Electrics: Central locking, interior lights, hazard lights, radio, and parking lights work perfectly.

  • Manual Jumpering: If I manually jumper the Terminal 15 relay under the steering wheel (bridging pins 30 and 87), power is successfully sent to the cabin fuse box (verified 12V at dashboard fuse SC6, and steering column fuses SC2 and SC16). However, the cluster still remains completely black.

Diagnostic Data (OBDeleven):
When the Terminal 15 relay is manually jumpered, I can establish VCDS/OBDeleven communication with the car.

  • BCM / Central Electrics Live Data: BCM successfully registers the physical key positions! Terminal 15 (input) and Terminal 50 (input) switch from OFF to ON when I turn the key.

  • The Conflict: However, another live data channel shows Terminal 15 (via LIN) / Steering column switch information as "Not Installed".

  • Fault Codes: The system is flooded with permanent communication codes that cannot be cleared:

    • Terminal 15 implausible signal

    • No signal/communication / Lost connection to: Instrument Cluster (J285) and Steering Column Module (J527).

  • Network Status: Modules like the ECU, TCU, ABS, Gateway, and BCM are fully awake and communicating with the scanner, but they ALL complain about missing communication from specifically the Cluster and the Steering Column Module.

What has been verified and tested so far:

  1. Fuses & Relays: Every single fuse (engine bay E-box, cabin fuse box, and the large SA-metal strip fuses in front of the engine e-box) has been continuity tested and confirmed OK and power-supplied. All "Relay 100" relays have been bench-tested and function perfectly. No pins in the relay carriers are backed out or damaged.

  2. Ignition Switch & Lock: The mechanical lock and the electrical ignition switch (D-switch) behind it have been tested and are fully operational.

  3. Steering Column Module (J527): The module's internal circuit board has been inspected and measured—it appears to be fully functional. (Note: The indicator stalk had some intermittent glitches months prior to this event, and the car occasionally threw a steering angle sensor G85 code before, but worked fine).

  4. Wiring & Grounding: Tested with a jumper cable directly from battery negative to the engine block with no change. The wiring harness near the engine/DPF/ABS is verified intact and has not been pinched or damaged during the alternator swap. B+ on the new alternator is connected correctly to the designated M8 post.

  5. LIN-bus: The LIN-bus wire from the alternator regulator is verified not shorted.

The Dilemma:
Since the BCM sees the key turning "ON" in live data, the hardware signal gets into the car. But the BCM refuses to ground the Terminal 15 relay automatically. Even when I bypass the relay manually, the Cluster and J527 refuse to boot up on the CAN-bus network, leaving them completely dead to the rest of the car.

It feels like a digital lockout or a specific power line (Terminal 30/constant power) to just these two modules has died, but all fuses are intact.

Has anyone encountered the BCM or Gateway completely dropping/disabling the LIN-bus to the steering column after a battery reconnect? Could a voltage spike during battery connection have locked the BCM logic, or am I missing a hidden fuse/fusible link somewhere?

Any input or crazy ideas are highly appreciated. I am completely out of options!

Thanks in advance.

Could it be the new zenon ballast thats causing problems. Its the only other thing that was replaced and cant see new alternator or battery being cause. Might be cluster related??

Alasdair

One point of possible concern, was the ignition switched on when you connected the battery? - the reason I ask is your sentence ('there was a normal minor spark), the cars ignition went completely dead'

Got this from AI so ???

1. The Steering Column Module (J527) is "Bricked" or Frozen

A sudden surge during a battery reconnection can easily scramble the volatile memory or freeze the microprocessor of the J527 module. Because the module is completely unresponsive, it is not broadcasting its digital ID over the LIN bus. The BCM, seeing total silence on that data line, assumes the module is physically missing or "Not Installed."

  • How to fix it: Perform a hard microprocessor reset. Keep the car battery connected, but locate the large multi-pin harness plugged directly into the Steering Column Module (under the plastic shroud behind the steering wheel). Unplug it completely for 5 to 10 minutes, then plug it back in. This completely cuts local power to the chip and forces a hard reboot.

2. The BCM Lost its Gateway Coding (EEPROM Corruption)

When car batteries are changed, a massive voltage arc can sometimes corrupt the EEPROM memory inside the BCM or the Gateway module. The car hasn't physically changed, but the BCM's internal configuration file has suddenly "forgotten" that a steering column module is supposed to be there.

  • How to fix it: If you are using VCDS, OBDeleven, or a similar high-level scan tool, go into Address 19 (Can Gateway) or Address 09 (Central Electrics / BCM). Look at the Installation List. Check to see if the Steering Column Module (often Address 16) has become unticked or deselected in the gateway configuration. If it is unchecked, re-tick it and save the coding.

Why this keeps the Dashboard Blank

Even though the BCM sees you turning the physical key via hardwired pins, VAG security and power-distribution logic requires a valid digital handshake over the LIN/CAN bus from the steering column electronics before it will authorize the Instrument Cluster to wake up. Without that handshake, the car stays in a digital "sleep" state to prevent theft.

You may have already tried the above but you did say any ideas.

Alasdair

  • Author
1 hour ago, Warrior193 said:

One point of possible concern, was the ignition switched on when you connected the battery? - the reason I ask is your sentence ('there was a normal minor spark), the cars ignition went completely dead'

No the ignition was off when the battery was Connected.

  • Author

Hi everyone,

I wanted to update this thread with the final solution, as the car is now 100% fixed and running perfectly! It turned out to be a classic, physical wiring issue hidden behind phantom voltage, and NOT a digital/software lock or component protection.

How the fault was isolated:
After systematically verifying that the ignition switch (D-switch) and the internal board of the J527 Steering Column Module were healthy, I started measuring the actual voltage under load.

I discovered that Pin 1 (Red wire - Terminal 30 / Constant Power) on the main 20-pin connector (T20a) going into the Steering Column Module (J527) was only receiving between 1.5V and 3.5V.

This was a classic phantom voltage situation. The wire had enough physical continuity to pass a basic multimeter beep/continuity test, but under any form of load, the voltage collapsed completely. Because the J527 module was only getting a few volts, its internal network chip couldn't boot up. This caused the LIN-bus to shut down, made the instrument cluster go completely pitch black, and threw the whole car's CAN-bus into a frenzy, triggering all the Lost Communication codes.

The Root Cause:
While the fuse box under the hood (E-box) was delivering a healthy 13V, the voltage dropped to 1.5V on the inside of the cabin where the wire changes color/thickness.

When the alternator originally failed (draining the system) and the new battery was connected, the initial inrush current/spark acted as a "fuse" at the weakest link of that specific power line. The wire had physically burned out/melted inside the factory crimp/welded splice inside the wiring harness harness right where it passes through the firewall (torpedvägg). Only a single strand of copper was left touching, allowing just enough "ghost voltage" through to trick a multimeter, but not enough to wake up the modules.

The Fix:
I hooked up a power probe to inject a clean, fused 12V/13V Terminal 30 source directly into Pin 1 on the J527 connector—and the entire car instantly woke up! The dashboard lit up, the Terminal 15 relay clicked automatically, and the car started right up with zero issues.

To make a reliable and permanent fix without ripping apart the entire insulated factory wiring loom under the firewall, I performed a permanent bypass:

  1. Ran a new, high-quality 12V wire from a verified, constant Terminal 30 slot in the cabin fuse box.

  2. Added an inline 5A fuse to protect the new circuit.

  3. Snipped the damaged original wire a few centimeters before the J527 connector (insulating the old 1.5V end).

  4. Spliced the new, clean 12V line directly into Pin 1.

Everything is now working flawlessly, and all communication errors are gone. Thank you to everyone who read along—if you ever experience a completely black dash and dead ignition after a battery change on a VAG car, always load-test Pin 1 on your steering column module!

Create an account or sign in to comment

Recently Browsing 2

Important Information

Welcome to BRISKODA. Please note the following important links Terms of Use. We have a comprehensive Privacy Policy. We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.

Account

Navigation

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.