Author Topic: Running rich topic again:(  (Read 2579 times)

Offline javalin

  • I live here
  • *****
  • Posts: 1,457
Re: Running rich topic again:(
« Reply #10 on: 15 January 2013, 15:02 »
only if its open circuit - i.e. totally failed.  Worth noting that its two sensors in one unit, one for dash one for ECU - so even if dash says 90c then ecu might be getting 60c reading.
You only ever need two tools in life. If it moves and it shouldn't use Duct Tape. If it does not move and it should, use WD40.

Offline itavaltalainen

  • I live here
  • *****
  • Posts: 2,693
  • VCDS and VCP - fault codes, coding, VIM activation
Re: Running rich topic again:(
« Reply #11 on: 15 January 2013, 16:29 »
ignition timing does not cause running rich, but the only indicator that that MIGHT be the case is increased consumption......

since jas changed a number of things, like cambelt which drives the dizzy shaft it is quite possible that ignition timing is off.... and yes this can increase consumption and slightly reduce power...


btw temp sensor can be checked with a cheap multimeter.... cant remember how many times i've posted this here:

« Last Edit: 15 January 2013, 16:32 by itavaltalainen »
2019 Seat Leon ST FR DSG 135kW - eclipse orange - 23k miles

Offline Jasikasisback

  • I live here
  • *****
  • Posts: 782
Re: Running rich topic again:(
« Reply #12 on: 02 February 2013, 18:17 »
Ok I checked the ohms resistance on the temperature sensor.

I put up some pics on flickr so you can take a look here...

I have done this without the key in the ignition.. the temp guage inside read 90.

then i took the temp sensor off and got these readings. This is without the key in the ignition..

top- 3.99 k Ω

bottom 0,291 k Ω

temp guage at 70

top 4.00 k  Ω

bottom 0.287 k  Ω

You can take a look at the pictures.. on this link

http://www.flickr.com/photos/67897318@N06/8438946308/in/photostream

or look under vwgolfcl1996...at the newest photos...

Thanks


just wondering if i am doing it correctly..:)


« Last Edit: 02 February 2013, 18:30 by Jasikasisback »

Offline itavaltalainen

  • I live here
  • *****
  • Posts: 2,693
  • VCDS and VCP - fault codes, coding, VIM activation
Re: Running rich topic again:(
« Reply #13 on: 02 February 2013, 18:42 »
you measured the ecu and temp gauge :)

you need to measure the sensor that is in the flange. well at least you now know that the wiring is intact, which is not bad either cos you can now exclude it as a cause.
2019 Seat Leon ST FR DSG 135kW - eclipse orange - 23k miles

Offline Jasikasisback

  • I live here
  • *****
  • Posts: 782
Re: Running rich topic again:(
« Reply #14 on: 02 February 2013, 18:44 »
aha silly me...I will try it again then tomorrow...

Does the ignition need to be switched on so the temp guage is active or no key in ignition needed?

Offline itavaltalainen

  • I live here
  • *****
  • Posts: 2,693
  • VCDS and VCP - fault codes, coding, VIM activation
Re: Running rich topic again:(
« Reply #15 on: 02 February 2013, 19:18 »
to check temp sensor take it out, put in freezer for 15 min, should be well below 0, then leave 30 mins at room temp should then be around 20 degrees, then put it in the oven for 15 min at around 80 degrees.

you won't need ignition to measure the sensor. it's diconnected anyway when you take the cable off
2019 Seat Leon ST FR DSG 135kW - eclipse orange - 23k miles

Offline Jasikasisback

  • I live here
  • *****
  • Posts: 782
Re: Running rich topic again:(
« Reply #16 on: 02 February 2013, 22:16 »
how much coolant will l lose when I take this out?

Offline itavaltalainen

  • I live here
  • *****
  • Posts: 2,693
  • VCDS and VCP - fault codes, coding, VIM activation
Re: Running rich topic again:(
« Reply #17 on: 02 February 2013, 22:57 »
a liter or two. if you put a funnel under the flange and take off rad hose and collect in a bottle you will really only use far less than that.
2019 Seat Leon ST FR DSG 135kW - eclipse orange - 23k miles

Offline Jasikasisback

  • I live here
  • *****
  • Posts: 782
Re: Running rich topic again:(
« Reply #18 on: 03 February 2013, 10:17 »
it appears to be working normally. i will have to look for the cause elsewhere. this looks like it will need a professional diagnostic check.