Jump to content
Ford Galaxy Owners Club

Recommended Posts

  • Replies 79
  • Created
  • Last Reply

Top Posters In This Topic

Posted

So under the plastic kick covers to the side, say where the bonnet release handle is screwed in??

S32 splice is on front passenger side L/H this is a joint between fuse 32, data link terminal 16, and instrument cluster.

Posted

So under the plastic kick covers to the side, say where the bonnet release handle is screwed in??

S32 splice is on front passenger side L/H this is a joint between fuse 32, data link terminal 16, and instrument cluster.

 

Hmmm, very interesting!! That could make sense as to Fuse 32 giving power but pin 16 not receiving. And also maybe why clocks are playing up too???

I wonder if Radio gets power from here too??

 

Can I ask where are you reading this from - Do you have wiring diagrams? If so could you send me some pretty please?

Posted

So under the plastic kick covers to the side, say where the bonnet release handle is screwed in??

S32 splice is on front passenger side L/H this is a joint between fuse 32, data link terminal 16, and instrument cluster.

 

WOO!

 

S32 - I think this is it!! Lifted the plastic trim up and instantly saw that the rear washer pipe connection wasn't connected properly and was leaking under the carpet.

Trimmed the tape off the wires traced it back, and found the S32 connection. As soon as i touched it it fell apart in my hands!!

 

Im off back out there now to carry on. :blush:

 

Will report back in twenty.

 

B)

Posted

Right, well ermmm... BUGGER i think is the word im looking for.

 

The wiring was well corroded It broke apart in my hands. I trimmed it back and wrapped it all together (for now)

Clocks work perfectly, they dont reset any more, radio works aswell, and central locking has stopped its funny shit! lol The hazards also flash when using the central locking from a door barrel too!

Oh and ive got 12v at pin 16 on diagnostics!!

 

But....

 

Still getting no response from controller! B)

Posted

Worth noting for anyone else that is having problems with any of the instrumentation behaving irratically, or being jumpy or jolty, or misreading, or resetting to double check the wiring under the kick panel below the passenger front door ;) :thumb:

 

Still struggling with my no response from controller though B) :blush: :(

Posted

Result on the instruments etc, Chrispb123456 patiently sorted the first problem I posted (re aux heater controller reset) and really helped me too.

 

Has this made any difference to the voltage you see on pin 7 now?

Posted

Result on the instruments etc, Chrispb123456 patiently sorted the first problem I posted (re aux heater controller reset) and really helped me too.

 

Has this made any difference to the voltage you see on pin 7 now?

 

Errmmm, Havent checked! Will check tomorrow now.

 

Im still thinking a module shorting k1? If i repeatedly test in options, sometimes it comes back k1 - ok, k2 - ok, Can - not ready. Then a few tests after K1 short to ground!!

 

Ive disconnected ABS, AIRBAGS, AUX HEATER, RADIO, And CENTRAL LOCKING multi plug on fusebox. What else has a diagnostic line to it??

Posted

Just been through wiring diagrams on elsawin, and the only other module i can see with a K line running to it is the Immobiliser box.

 

Every diagram has a line going back to J501 which is the fusebox. P5/7 which is the central locking Connector.

 

Will check K line for continuity to ecu from obd port and resistance tomorrow and post back my findings here.

Posted

Remember sleep? (3.31 am) can't be sure but I think candidates are Instrument cluster, abs, and if you have them autobox & climatronic. Sure this sort of thing must be documented somewhere- - vag issue briefings for new engine types etc, you'd think there'd be one for diagnostics but it's the old "minimum information" thing. You'd assume they'd be on the wiring diagram but I'm sure I've read somewhere of undocumented links.

 

Wondered why you use 10.3 (apart from the obvious "I proved it works on my laptop") and also what you used with your elm327 - I was thinking about getting one + torque probably just for otr issues.

Posted

Sleep? Pahhhh whats that?

 

I use 10.3 because it was cheap and it works ;)

And the elm adaptor is used with my torque app - quite a cool piece of kit... well worth it for the 'look what my phone can do' factor!

 

Maybe worth me trying a 'legitimate' vagcom on my car? Although my vcds works with everything i have tried it on...

 

Anyway, how comes the sharan has can wires, but my vcds says can not ready? Does yours connect via can?

Posted

Thanks for that - think I'll go for the elm327 - sounds worthwhile addition/flash. I have a mk1, which I didn't think had canbus. The haynes mk1 manual shows the mk1 diesel as having odbc canbus pins 6 and 14 connected to engine ecu - which they aren't - they're unpopulated. My interface is a cheapie klline only one and works fine. All the unmatched pins on my i/f are unconnected apart from 15.

 

Which interface do you have - does it support canbus? Am I right you're using a genuine vcds/um "evaluation" clone with the vagcom version designed for a ross-tech i/f? fwiw looking today the current vcds is 11.11.3 and I think there have been a few driver issues in vagcom's past, some vehicle specific.

Which extra connections do you have on your odbc port? Wondering if your interface may be physically connected to more than one data pin, and if you have extra connections it doesn't really understand this may be related to the problem. I expect you've been here http://download.ross-tech.com/VCDS/download/VCDSCompatibilityCharts.pdf but in any case I have a feeling (others may know better!) that canbus was in there somewhere on mk2.

Posted

Yeah, evaluation clone! Nice!

 

Yes hex+can cable, 10.3. No problems on anything else including my mates 2008 Audi A4.

 

The other thing is, when its trying to connect to a controller(after successful. Test) it will try three times to connect in the top left hand corner and says hexinit -2 (or -3) which ive never seen before!

 

Definitely a canbus car, orange/black twizzled wires rum to clocks, ecu etc.

 

Anyway, no continuity from obd to back of pin 16 at ecu... so surely my next bet is to connect my own can line?

Posted

Funny - after digging around this morning I'd come to the conclusion it wasn't canbus and was about to post humble pie, based on the supported i/f info on ross-tech and some other sites. Yet clearly it is.

 

If it was me I'd be connecting directly too. Might also look for voltage at the kline odb pin (to see if there's anything there with those other controllers disconnected if they still are) and at the corresponding ecu pin before rigging a connection. Don't have proper pinout for your ecu - is pin 16 kline - I seem to recall it is, but my memory is rubbish...

 

Good if the diags are available on the canbus - nice and speedy i would think...

 

Do you have autobox?

Posted

No autobox so one less thing to worry about diagnostic-wise

Will check voltage at both ends quickly before connecting my own k line.

 

Yes pin 16 at ecu 121pin connection. white wire.

 

Diagnostics would be very speedy if they worked! Lol

Posted

Well and truly stuck now!

 

Tested continuity from k line at obd to ecu pin 16 and nothing! Found it goes through immobilser box, in at pin 8 and out at pin 7 to ecu. Got continuity into it but not out. But if i jump pin 7 and 8 together, i get continuity back to ecu, so that rules out wiring to or from ecu.

But why isnt k line working coming out of the immo box?

 

When trying to connect with vagcom i tested continuity at pin 7 obd port to earth and it keeps jumping off 1 to somewhere around 1000 every couple of seconds. This makes me think something is pulling k line to earth, but everything with a k line is disconnected!

 

What do i do now? Ecu knackered?

Posted
Not really following this thread, but I expect you already know that the ignition has to be turned on to access OBD, maybe that why the immobiliser is blocking it.
Posted

Not really following this thread, but I expect you already know that the ignition has to be turned on to access OBD, maybe that why the immobiliser is blocking it.

 

Please follow it! Ive seen numerous posts of yours in previous threads being very knowledgeable on certain things.

 

And yes, I do know ignition needs to be on.

 

One thing i never thought about when unplugging modules is to unplug the ecu! Ive just unplugged it and it allowed me to connect for the first time!!

 

Here is the scan on everything bar the ecu:

 

 

Sunday,29,July,2012,16:51:22:10074

VCDS Version: Beta 11.3.0

Data version: 20110801

 

 

 

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

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

 

 

Chassis Type: 7M - VW Sharan I

Scan: 25 01 02 03 08 09 15 16 17 18 19 22 29 36 37 39 45 46 55 56

76

 

VIN: WVWZZZ7MZ1V000490 Mileage: 340680km/211688miles

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

Address 25: Immobilizer Labels: 6X0-953-257.lbl

Part No: 6X0 953 257

Component: IMMO 0003

Coding: 00003

Shop #: WSC 00000

VCID: FDF57DC7D8D5

WVWZZZ7MZ1V000490 VWZ1Z0Y0442145

 

1 Fault Found:

00750 - Warning Lamp

31-00 - Open or Short to Ground

 

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

Address 03: ABS Brakes Labels: 1J0-907-37x-ABS.lbl

Part No: 1J0 907 379 P

Component: ABS 20 IE CAN 0001

Coding: 12502

Shop #: WSC 01317

VCID: 3E773ACB1553

 

1 Fault Found:

01312 - Powertrain Data Bus

37-00 - Faulty

 

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

Address 09: Cent. Elect. Labels: None

Part No: 7M3 962 258 G

Component: Multifunkt.Einheit 0001

Coding: 04097

Shop #: WSC 01317

VCID: 3E773ACB1553

 

No fault code found.

 

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

Address 15: Airbags Labels: 6Q0-909-605-VW5.lbl

Part No: 6Q0 909 601

Component: 0H AIRBAG VW5 0003

Coding: 12360

Shop #: WSC 01317

VCID: F0EB54F39F87

 

No fault code found.

 

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

Address 17: Instruments Labels: 7Mx-920-xxx-17.lbl

Part No: 7M3 920 920 C

Component: KOMBIINSTRUMENT VDO V03

Coding: 13421

Shop #: WSC 19411

VCID: 306B14F3DF07

 

2 Faults Found:

00562 - Sensor for Oil Level/Temperature (G266)

30-00 - Open or Short to Plus

01312 - Powertrain Data Bus

37-00 - Faulty

 

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

Address 19: CAN Gateway Labels: 6N0-909-901-19.lbl

Part No: 6N0 909 901

Component: Gateway K<->CAN 0001

Coding: 00006

Shop #: WSC 00000

VCID: F0EB54F39F87

 

1 Fault Found:

01312 - Powertrain Data Bus

37-00 - Faulty

 

End ---------------------------------------------------------------------

 

 

Does that mean for sure my ecu is faulty??

Posted

Progress if not neccessarily what you were hoping for...

 

With the ecu disconnected, do you still get the same changes in continuity from obd pin 7? Also wondered what voltage you see on that pin now? Would be nice to be able to connect directly to ecu pin 16 without any other kline connected - suppose if nothing was showing on the line when it was disconnected from the immob and ecu that would be a clue....

Posted

Have found out the powertrain issues are due to the ECU being disconnected, so some consolation there.

 

Have tested voltages all over, with ECU Connected and not, and this is the result:

 

OBD port pin 7 - 10.27v Ign on - 1.9v Ign off.

ECU connected pin 16 - 11.03v Ign on - 0.26v Ign off.

ECU disconnected pin 16 - 10.94v Ign on - 0.41v Ign off.

 

Vagcom connecting but ECU disconnected - At Pin 16 -

Fluctuating between 10.7v and 0.73v before vagcom comes up no response.

 

Vagcom connecting ECU connected - At Pin 16 -

Fluctuating between 9.6v and 0.73v before vagcom comes up no response.

Then goes from 9.6v back upto 11.3v when interface unplugged from OBD port.

 

Have no idea where to go from here, so decided to whip EGR off for now, and will order some blanks to bypass it! :)

Posted
When I can, I'll try to pull the ecu and track the vcds init voltages as you have. As I've got a mk1, may not be entirely valid. I don't know how easy it would be for you to follow the init when talking to say the immobiliser? At this point I'm getting a bit worried that the best response to your original query might turn out to have been "yes - get a new ecu". Still hopeful that not so, and the nice thing about here is you never know when somebody may turn up with the answer...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×
×
  • Create New...