Jump to content
Ford Galaxy Owners Club

Recommended Posts

Posted

Here is the story: In my mkII galaxy 2.3 automatic speedo stopped working and fuel gauge started beeping. Fault code said it was vehicle speed sensor but vcds was able to show the correct speed so decided to try another cluster. That cluster was from an Alhambra 1.9 tdi, so only parts of it worked straight away. Speedo did work but showed way too much speed. I tried to recode the distance impulse number with vcds. I did not get any error messages, but the new values did not get saved either. This I tried with my own vcds lite and friends vcds full version but with similar results. What could cause this problem? How could I get it to work?

 

Since that did not work, I decided to use VAG Tacho to save the eeprom of the original cluster and import that to the new cluster. No success here either. Vag tacho says there is a short circuit to ground in the k-line and it does not find the ecu. I wonder why so? VCDS does connect without any problems and works well apart from not being able to save the coding I mentioned before. 

 

Any advice is appreciated here!

Posted

I suspect no one has tried. There is a cluster from a 2.3 auto MkII on ebay at the moment for 66 quid, on a BIN. Might be better than all the faffing your doing, and you could re-sell the 1.9 one you have?

Posted

p.s. any rumors I'm an employee of ebay are completely unfounded! :-)

Posted

I used VAG-TACHO just to enable the "Miles to Empty" on the trip computer of my Galaxy and didn't have any issues.  Mirez has done an excellent guide on doing this though.

Posted

30 quid is cheap! Unfortunately I am in Finland and they only deliver to UK. I could live with the speedo showing miles/hour while km/h is also there with a small print but actually we use metric meters here. For some reason the metric clusters in Germany seem to cost much more. 

 

I just wish I didn't have to spend 150 euros on this since it SHOULD be possible to get it done with the stuff I already have.

Posted

OK, the original problem is solved and the original cluster is now working fine. It was just the vehicle speed sensors "axle" that was broken. It is a bit surprising why this also effects the fuel gauge so that it continuously swings along with the fuel level in the tank and warns about too low fuel level. But fixing the sensor fixed the speedo AND the fuel gauge. It was also confusing that VCDS was able to show the speed correctly and the alhambra 1.9tdi cluster was also able to show speed (although way too much). The reason for this must be that the 1.9tdi cluster and VCDS use ABS sensors to measure speed, not the vehicle speed sensor in the auto gearbox that the original cluster was using. I wrote this post, because there seemed to be many questions about this speedo/fuel gauge problem but at least I was not able to find a solution for it. Hope it helps someone else to save some effort!

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