Jump to content
Ford Galaxy Owners Club

Recommended Posts

Posted

Right then, used car to take kids to school this morning and guess what, the car was running fine, went through the gears with no power loss, got up to 80mph quite easily, unfortunately no hills on the way to school. But then coming home the car was sluggish again, shame because the hill on the way home would have been the ultimate test.

Did manage to do the MAF test again last night to find there is in fact 1.2V at 1000rpm and 2.6v at 3000rpm.

Other than adding some water to the coolant and testing the MAF last night nothing else has been done so shall look into the wiring at the MAF sensor, possibly a loose or broken/corroded connection causing intermittent results.

Still no sign of the vag-com lead so can't really do a lot at the moment, probably won't arrive until Monday, Tuesday at the latest.

  • Replies 90
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Posted Images

Posted
clear the codes first then test and look for new codes :lol:
Posted

OK, so had the Vag-com connected and set Chassis as VW Sharan, guess thats right? Anyone please confirm.

Anyway got the following errors from the ECU before clearing faults.

After connecting lead, then running software I selected 'Program Options' and highlighted COM4, my selected com port, hit 'Test' then 'Save'.

Then back to Home Page -

Selected 'Select Control Module'

Selected '01 Engine'

Selected 'Fault Codes'

and heres the results:

 

6 Faults Found :

00575 - Intake Manifold Pressure

17-10 - control difference - intermittent

00550 - Shareware Version. To decode all DTCs

17-00 - Please Register/Activate

01269 - Shareware Version. To decode all DTCs

31-10 - Please Register/Activate - Intermittent

01237 - fuel shut off valve (N109)

31-10 - Open or Short to Ground - Intermittent

65535 - Shareware Version. To Decode all DTCs

37-10 - Please Register/Activate - Intermittent

00553 - Shareware Version. To Decode all DTCs

17-00 - Please Register/Activate - Intermittent

 

Then cleared the fault codes on the '01 Engine' page.

Thats as good as memory serves anyway!

Now I'm off for a short drive to gather more fault codes before logging new codes.

Posted (edited)

Ran the Vag-com again just to check no fault codes present, so OK no codes as I cleared them yesterday.

Took the car for a short burst up the road including up the dreaded hill, ran fine with no problems, so all good so far!

 

Got back and connected Vag-com back up to find the following fault code:

 

1 Fault Found :

65535 - Internal Control Module Memory Error

37-00 - Faulty

 

This didn't come up on yesterdays diagnostic test but has today and I cannot clear the fault, when I click on Clear codes the code clears but immediately shows back up again.

Well, I say it didn't come up yesterday but the 65535 37-10 looks close to it!

Edited by junky
Posted

Yeah, found that on Ross-Tech site after doing a search on 65535 but wondered what you guys had to say on the matter.

 

Internal Control Module Memory Error

 

Possible Causes

Wiring from/to Control Module faulty Voltage Supply and/or Ground Supply faulty

 

Control Module faulty Control Module Housing leaky

 

 

Possible Solutions

Check/Clean Wiring from/to Control Module Check Voltage Supply and Ground Supply including the Main Supply/Connections at the Battery

 

Replace Control Module

 

Special Notes

This fault is NOT to be ignored when found in a major and/or critical system (Airbag, ABS etc.).

When stored in other unimportant systems (Radio etc.) the general suggestion is to ignore it unless you notice functional limitations. Within the warranty period dealers are usually required to replace such control modules, but there have been a couple of cases with similar codes where these are getting ignored due to flaws in the control module software. If in doubt please refer to technical bulletins and similar documents provided by the vehicle manufacturer.

Audi Airbag 6 & 7 Problem: A fault of the acceleration sensor may result in the above fault.

Solution: Replace Airbag control module and both acceleration sensors.

 

Audi Airbag 8 Problem: Due to under voltage the control module does not complete it's self test successfully.

Solution: Replace Airbag control module and install a under voltage protection relay for it.

 

Certain older TDI ECUs which have a vacuum line going to them Problem: Vacuum line broken, either before ECU or inside ECU.

Solution: Inspect and repair vacuum lines to ECU and inside ECU.

Posted

Looking at the 'How to' No.74 MK1 ECU removal I have noticed a couple of differing things, could I have some comments please.

 

Firstly, I do not appear to have a bulb control monitor mounted on top of the ECU.

 

Secondly, my instrument panel only has one socket/plug.

 

Thought my Galaxy was a MK1, is there an early and late MK1 and so slightly differ?

Posted

Bulb failure module would depend on spec of car not all models have it, same with the clocks extra spec more wiring required to clocks.

OK, thanks. Clears that up. Yeah think this is a basic model Galaxy so not got all the gadgets!

Posted

Well I think I am just going to ignore that fault code, afterall it is the only one showing up and the car appears to be running just fine now.

I think all the original fault codes arose from the original fault which was the fuel filter and my testing attempts on the fuel stop solenoid and MAF, so now these codes have been cleared and the fuel filter replaced I think the problem has been fixed and the car running fine.

Of course I shall keep tabs on performance and run a diagnostic once in a while just to check but for now all is well and we are happy!!!

 

Thankyou everyone for your help and assistance.

 

Just a quick note for anyone interested:

Having cleared all codes except the control module memory error I decided to disconnect the ECU hose (the end under the bonnet), ran the car with poor performance and did another Vag-com check with the result of a fault code 00575 17-00 as well as the 65535 fault. Don't know if this eliminates the ECU hose(s) for the 65535 37-10 fault but sounds pretty conclusive to me. If it were a hose leak surely it would come up with the 00575 fault. Well, anyway cleared the fault, re-connected the ECU hose and now back to running all good!!! HAPPY HAPPY HAPPY!!!!

Posted
It would appear there are two sensors inside the ECU, the MAP sensor connected to the small hose inside the unit and an atmospheric sensor, problems with either would involve a new ECU but as you say it's running OK now so leave alone, quite possibly fault code was there even before filter change
Posted (edited)

It would appear there are two sensors inside the ECU, the MAP sensor connected to the small hose inside the unit and an atmospheric sensor, problems with either would involve a new ECU but as you say it's running OK now so leave alone, quite possibly fault code was there even before filter change

 

Hi chrisp, do you happen to know the differences between VCDS Lite ver1.0 and 1.1? Is it likely different codes will arise depending on the SW Ver in use?

 

All I can find is this according to the Ross-Tech site:

 

'5. November 2010:

 

VCDS-Lite Release 1.1 is now available. This improved version for non-CAN cars covers certain newer engines and other systems than the previous version 1.0. VCDS-Lite is available for download from this page.

 

 

1. April 2010:

 

VCDS-Lite Release 1.0 is now available. This new shareware version for non-CAN cars and "dumb" interfaces replaces the old VAG-COM versions 311 and 409, which are no longer supported. VCDS-Lite is available for download from this page.'

Edited by junky
Posted

I had version 1.0 and as far as I can remember it had about 7500 fault codes, I just paid for the full version but was told to download the latest version first 1.1 and noticed it has over 9000 fault codes

hope that answers your question.

Posted

I had version 1.0 and as far as I can remember it had about 7500 fault codes, I just paid for the full version but was told to download the latest version first 1.1 and noticed it has over 9000 fault codes

hope that answers your question.

Doesn't seem to be any release notes regarding update from version 1.0 to 1.1, so other than additional DTC's just wondered if there were any fixes such as incorrect code reporting.

There are as you say about 7500 (actually 7770) fault codes in ver1.0 and alot more in 1.1 (i.e. 9673 codes loaded). The Main screen appears the same as does the Program Options screen and from what I can make out so are all the other pages.

 

The reason I ask:

Ver1.1 shows only the 65535 fault whereas 1.0 gives the additional fault code 00576 - Terminal 15 17-00 Control Difference

I shall have to re-install ver1.1 to see if the Terminal 15 code still resides or has miraculously disappeared just to verify whether it is the software or genuinely on the ECU.

Another peculiarity is that up til now I have been running the diags on Wins XP but running Ver1.1 on Wins 7 the 65535 DTC shows up with 37-00 Faulty as opposed to 37-10 Faulty - Intermittent

 

Just for clarification I shall continue running both versions on both OS's to log future findings.

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...