VFRDiscussion ARCHIVE / READ-ONLYREAD-ONLY

Baro Sensor On The Way Out? - Fifth Generation VFR's

10 posts Started 22 Mar 2015 Last recovered post 29 Mar 2015 Wayback Machine snapshot 21 Jun 2015

#1

I've been getting intermittent Fi codes, but as I haven't ridden the VFR much I forget to do anything about it. Today it came on again and I read a Baro Code from the MIL. Found it and the electrical connection looks good. Blew out the tube with low pressure compressed air.

Is there really anything to do, or is it just a 16 y/o electrical sensor that is past it's prime? 

#2

I think there is a resistance test you can do to see if its in spec. You will need an accurate multimeter

#3
I doubt mine is accurate enough.
#4
It might be an erroneous error. I had a baro sensor error and #2 injector error recentlyish, and I was sure it was bollocks. After much testing following all the procedures in the manual, and the baro sensor passing them all, it turned out some numpty serviceman had bolted the clutch cylinder on top of of one of the O2 sensor cables, shorting it out on the engine.
The baro sensor is only used to compensate for high altitude, and even without it behaving itself the bike should run OK.
Anyway - the manual is available on here, and the testing procedure isn't too difficult; I used a fairly cheap digital meter to check it out; it's either OK or not, but it's more likely to be a wiring problem than the sensor itself.
#5

Well I'm the only serviceman who's touched it in the last 10 years, numpty or not...

Also no O2 sensors on my '99.

I did clear the code, then remove the Baro sensor and start it to get the Fi light to come back on. That induced the same flashing pattern I initially observed. Cleared it again and started with the Baro installed, and no code. I'll give the test procedure a look, but it's clearly an intermittent fault. First time I saw it was an hour into a long road trip, and after a fuel stop. Turned the bike off and back on and it went away. Came back later, but the off/on trick worked again. Didn't see it for a while after. Doesn't affect performance.

#6

290 bucks for a new sensor!  :ohmy:

#7

290! Ouch!  B aware that a bad conductor or crimp connector could cause the code as well.  Our outdated EFI system does not readily discern the difference between a bad sensor and a low or high voltage condition.  I had a coolant temp sensor code that eventually was fixed when I replaced the sensor.  But that was only after carefully checking the wiring and terminals back to the ECM. 

Good luck,  Jeff J.

#8

Looks like there's a used one on ebay for $50 (doesn't look like the seller describes it correctly).  Those probably are not a hot seller - maybe make them an offer . . .  If I read the FSM right, the Baro sensor and Fuel Cut relay are attached to the same bracket - so maybe changing one requires swapping out both. 

#9

No, they come off separately.

It is the same part as the MAP sensor that is attached to the air box. I guess if the code comes back I could swap them out and see if it comes back as MAP sensor fault.

#10

Couple hundred miles today with no Fi light! Maybe it just needed some attention... :rolleyes:

End of thread · 10 posts recovered Wayback Machine snapshot 21 Jun 2015