I am ready to take a V10 in a motor home on a long trip. After lengthy repairs, I finally have some sensor data from the OBDII Data Link Connector, maybe. I have an AutoEnginuity data receiver connected. It isn't reading properly: only 8 cylinders.

There are no codes except an EVAP system leak.

The B1 S1 (Bank 1 Side 1?) and B2S1 sensors are reading normal. The B1S2 voltage is reading zero unless driving hard. The fuel trim reports 99% all the time. There are no B2S2 sensors available in the software.

The fuel circuit goes into Open/Normal driving when on the road. But it went back to closed when idling at home.

Also, it is reading high levels of Catalytic Converter Bank 2. Bank 1 is okay. Not sure if there are two banks or not and it reads 98% misfires on cylinders 5-8. But it doesn't report 9 and 10. Based on the engine's power, it isn't missing and the total misfires reported is 0. I don't think the software knows what kind of engine this is, despite giving it the vehicle information, including the VIN.

So the question is, if there is a B1S2 O2 sensor and it is flaky, would you cancel your trip because of it and get it repaired ASAP?

Something else to note, the short term and long term trims on both sides are giving nominal values.

I not an experienced mechanic, just a DIY'r, so feel free to talk down to me and give your honest opinion!

Dan

 

The first thing I would do is get up underneath the motor home and look to see if there is one or two catalytic convertors and then I would look to see how many oxygen sensors there are. Look to see if they are before the catalytic convertor and after. Then you need to get the scanner to read for the correct engine that you have. Right now I would not trust anything that it is reading.

 

is this a 2-valve or 3-valve V10? What year?

If it's pre-2005, there IS no O2 sensor after the cat. And there is only one cat.

And in the F53 motorhome chassis, I'm not sure a 3-valve has O2 sensors after the cats either.

I have an Autotap, an older version. It won't figure out that my V10 doesn't have an O2 sensor after the cat. And it shows all sorts of other weirdness. Which sounds like exactly what yours is doing.

The fact that you have an EVAP code (no CEL light though?) and it goes into open loop on the highway, may or may not mean you have other issues.

But definitely get back to us with the year of the chassis, and look underneath to see how many cats you have, and if there really are O2 sensors afterwards. Then we can work on the rest of the stuff.

 

[quote=Krewat;10227423]
If it's pre-2005, there IS no O2 sensor after the cat.
.....................
My 2003 is an OBDII compliant ( as per emission sticker )and indeed I do have two O2 sensors before the cat ( one on each bank ) and ONE O2 sensor after the cat .

Question To Krewat :
Also my 2003 does not have an EGR pipe ( since I do not see any obvious EGR pipe , there should not be any EGR valve either, so no EGR system ) . EGR is supposedly circulates small amount of exhaust gases when engine is hot in order to reduce NOX emission . Since I am living in FL where there is no inspection/emission test , truck had never been subjected to any testing. Without the EGR , how this truck would be passing an OBDII emission test ?
Any explanation is appreciated .

Ken

 

You know, looking back at that, I shouldn't have said pre-2005 has no O2 after the cat. There are some that do.

Federal emissions says up to 2007, anything over 8500lbs GVWR does not need an EGR. In 2007, I think they changed that to 14K lbs. I don't know why Ford did the '99 w/an EGR, maybe they figured it was going to need one sooner or later and then dropped it. Dunno.

California is different, which I suspect your truck may have CA emissions so it's OBD-II.

 

Thank you for the responses. I tried to respond earlier but couldn't log into FTE.

Just got back from a roughly 700 mile round trip without problems. Everything ran good and it passed an emission smog check (sniffer version since the OBDII wasn't working; smog check required in Clark County, Nevada).

The chassis was manufactured in 1997 but the engine was replaced approximately 9 years ago. So I don't know what engine it has or if it has 2 or 3 valves. How might I figure this out? I fear the VIN won't give the details since the entire engine was replaced by Ford and I don't know how much of it was swapped out.

I'm going to climb under the chassis and look into the the catalytic converters, oxygen sensors, and EGR this week and I'll report back.

I think there is a voltage problem to some of the instrument cluster so no Check Engine, Anti-lock, or Cruise Control indicators. I need to look into that further. I didn't discover it until I looked into these problems.

I noticed the gasket on the gas cap is bad so perhaps that is throwing the EVAP code.

 

If the engine was replaced by Ford, it's almost 100% certain it's exactly the same as what was in there.

The big question that no one asked (including me) is what vehicle is this? You mention a '97 chassis build date. That means it HAS to be an E-series. F-series didn't come with V10s until model-year 1999 (manufacture starting in 1998).

When you first turn the key to ON, the check engine, ABS and such lights do not light up?

 

Sorry to be lax on the details. I'm usually good about those sort of things.

This is a 1998 Tioga motorhome branded Phoenix by Fleetwood. It is on an E-350 chassis with a 1997 manufacture date. I know it has the Triton V10 engine in it but little else.

You are correct that none of those lights come on when first starting the engine.

I've been dealing with several different problems with this rig. First the engine didn't run except when connnected to the Coach batteries, no AC, no Data Link Connector (DLC) activity, and several other issues. I replaced several fuses (some were actually missing) and have most of the life back. Once I got life back to the DLC, I got the funny readings with my Enginuity OBDII interface and software. I believe the software doesn't know this engine and I need to look further into that, too. Perhaps the DLC is not OBDII compliant.

But it did read the EVAP Leak code (Gross Leak). I should compare the code with the service manual (saw one on Ebay) to make sure it really is the EVAP.

Before the trip, I was mostly concerned about the O2 sensors and Catalytic converter. Since it passed the emmissions check and ran so smoothly, I'm not as concerned that they are real issue but I would like to get to the bottom of it all.

 

I'll bet there's a bad ground somewhere, probably at or near the instrument cluster, causing all those lights to be out. If I remember correctly, there's almost no common point between the ABS/Airbag/Check-engine except for a ground.

Otherwise, the ABS, AND the PCM would have to have no power going to them, and I seriously doubt that. It runs, AND your speedo works? (which means the ABS is sending speed output to the speedo, at least in the F-series).

Your system is OBD-II in terms of how it communicates with a scanner. Whether or not it's strictly "OBD-II compliant" in terms of emissions, that's another story. Under the hood, is there an emissions sticker, and if so, it should say something about OBD-II.