• Hey Guest💡👉 We have just launched our new Dealer Directory and review service Find out more now
While banging my head against the wall, i cross referenced between the fault log where everything connected fine, before the battery died, to the one yesterday which showed 'excessive communicatiuon errors' or 'no communications - intermittant' on pretty much everything, it makes me think that there is a loose connection somewhere, likely behind the dash, as i havent touched anything under the bonnet apart from the battery.

i found this thread (http://www.seatcupra.net/forums/showthread.php?t=401692) which mentions the same fault codes (01314 - Engine Control Module 49-10 - No Communications - Intermittent and 01317 - Control Module in Instrument Cluster (J285) 49-10 - No Communications - Intermittent) which i now have, plus a bunch of other no/intermittant comms errors which all cleared after finding a loose connection, the pictures wont load for me though, probably the work computer. The only difference is my car will run and drive.

Where do i look for this connection?
 
Last edited:
That was me!

The plug is located at the bull head. You need to drop the Comfort Module, relay rack and fuse box and you'll be able to see the plugs
 
That was me!

The plug is located at the bull head. You need to drop the Comfort Module, relay rack and fuse box and you'll be able to see the plugs

What/where is the comfort module? lol. I'll give this a go tonight. If I sort this problem, at least I can do some proper diagnostics.

I briefly managed to get into the wheel speed sensor measuring blocks yesterday before it simply said no. F/n/s wheel showed 0mph, all others increased speed and were matched to each other. Strange that the f/n/s shows 0mph when the speedo works.

Any ideas on my post before the last one with the abs fault codes?
 
Cheers

I have the wire/connector repair kit now. So I'll change that out as well. I really hope this will be fixed by something so simple.
 
Some progress... Finally!

I checked the wire on the f/n/s abs sensor, unplugged it and pulled fairly gently and the wires just separated. There was a clean break in both wires, God knows how the speedo was getting its reading, I thought it came from that wheel. I repaired the wire and the abs light instantly went off! I ran vcds but didn't get very far, the scan took ages, but I cleared the codes.

Now the car brakes fine, without the abs kicking in on the f/n/s wheel :)

The esp and steering lights are still illuminated. While driving the warning alarm still goes off, it gives off 3 beeps and the brake stop light flashes, what does 3 beeps usually mean?

I will change the pas pump on Wednesday, which should take care of the steering light. Is there anything I can check (without vcds) which might be causing the esp light to stay on?

I will pull the dash out as well when I have day light on Wednesday and hopefully fix the comms errors.

Also the airbag light is on, I thought this may have just been caused by the comms errors, but strangely when I scanned yesterday, it said drivers side resistance too low, but now says too high. What does that usually indicate?
 
Last edited:
PAS pump changed. I now have power steering and the light has gone out.

Can anyone advise what a 3 beep warning alarm and the handbrake light flickering on while driving would indicate? I have topped up the fluid, to rule fluid level out. The warning alarm sounds every minute or so. And only a few minutes into driving.

Also the ESP light is constantly on. ABS works fine. I read it could be the maf, I bought a new one and changed that last night, no change though.
 
Last edited:
Have you ran a full scan of all modules?

I still can't connect. I've had a fish about for a loose connection behind the dash like you posted about, but as yet I can't find anything. I'm just trying to rule out a few things before I pay someone to fix it.

When I initially changed the instrument cluster, everything connected fine until the battery died. But since fitting a new battery, nothing will connect. I had the same connection issues with the old cluster as well, so surely it must be a loose connection somewhere behind the dash.

When it did briefly connect, these were the only abs module faults listed.


01314 - Engine Control Module
000 - -


18055 - Check Coding of ECUs on Powertrain Data Bus
P1647 - 000 -


00283 - ABS Wheel Speed Sensor; Front Left (G47)
012 - Electrical Fault in Circuit

16347 - Control Module - EEPROM Error
014 - Defective


These two were listed under a few modules though


01314 - Engine Control Module
49-10 - No Communications - Intermittent
01317 - Control Module in Instrument Cluster (J285)
49-10 - No Communications - Intermittent
 
Last edited:
I'll try and connect to that tonight. You mentioned before about connecting directly to the k line on the abs module. Can I do the same on the instrument cluster, I believe it's pin 7 on the obd port. Just thinking if I can bypass where the dodgy connection is I might have more luck.


That's what I thought regarding the fluid, everything I've read online points towards that. But I brimmed the bottle and it made absolutely no difference. The warning alarm goes off at random points too. It doesn't matter if I'm driving up a hill, down a hill, turning a corner, or sitting on my drive way as I was in that video so it's not as if the fluid level is moving and the sensor is picking it up. I have sprayed contact cleaner inside the sensor plug, but no joy. I'm half tempted to just buy a brand new resevoir bottle, but I can't keep just throwing money at it and hoping for the best
 
Last edited:
I just ran vcds for module 17. It reported no fault codes. But while I was in the module, I checked the coding and strangely my engine code wasn't even listed within the options. Shortly after this it said 'too many communication errors', then timed out. I swapped back to the old cluster to check the coding, that listed my engine code, although it wasn't set to it. I changed back to the new cluster and now it won't connect at all.

So either this new cluster is in fact faulty, or I have further disturbed the loose connection, I don't know how I could have though as I only touched the cluster and there are no connection plugs to be seen anywhere near there
 
Last edited:
Have you tried a different VCDS cable?

No, I only have this one available to me. I have tried a vag commander cable along with the software, same problem

I tested the vcds cable on a friends Leon last night though and it connected without issues
 
Last edited:
Well at least it rules that out. Does Sean strange however, if the coding says BLT instead of ASZ etc... It's still the same.

My engine code is BPX, that wasn't even listed on the available codes for the new cluster. Even the code list options between both clusters were different. For instance the old cluster the code should have been 00401, but was set at 00405. The last number indicates the engine code. The new cluster was set at 00445, there wasn't even an '1' option under the engine code of the available codes and as I say, no code set mentioned BPX. So the 4th digit on the coding string by default is different.

Not really sure where to go with this now, as it all seems to work, all baring warning lights that are lit, which may well be indicating a problem that actually does exist.