Need help with a p0193 code
That's odd but my truck does that occasionally as well and doesn't have any fuel error codes. Actually my gauge seems to slowly creep up to full over around 30 miles. Other times it works normally. Not sure what that's all about.
So I traced the wire to 57 pin no broke or anything. Everything ohms out. I just can't figure it out im really at a loss I took it to a Mechanic I know and he ran some test said if it aint missing just run it but I hate my engine lite being on and I know its hurting my mpg. Not sure what to do
@Drew Hicks , this isn't looking good. I still say the code indicates the PCM (computer) doesn't _"SEE"_ the circuit in tact. That is not to doubt your test results. The _"signal"_ has to get through the pin, onto the PCM circuit board and through some electronics to be complete / effective. Unfortunately, it could be a cold solder joint or just a BAD PCM.
The software in the PCM makes every effort to keep the truck running. There are 'default' values that he software falls back on if a sensor fails or produces irrational information. It's called FMEM mode (Failure Mode Effects Management).
My research indicates there are TWO flag bytes where this condition is registered, but I cannot verify their 'bit' assignments. You can read them with a custom PID entry in Torque Pro. It would be tremendously helpful to me (and forum members) to find out if one of those flag bits are set TRUE. I know the PID byte numbers - but with a properly working truck, I never see any of the flags set ! They both should ALWAYS be zero. I do not know which bit means what, but know both bytes should be zero.
It would be most interesting if you would create TWO custom PIDs, If you go to >Settings >Manage Extra Sensors/PIDs - select Menu and >Add
Mode/PID - 221106
Long Name - MFEM Flag1
Short Nm - MFEM1
Equation - A
Mode/PID - 22107
Long Name - MFEM Flag2
Short Nm - MFEM2
Equation - A
You could then select them from the create gauge list and report their reading on your truck.
The software in the PCM makes every effort to keep the truck running. There are 'default' values that he software falls back on if a sensor fails or produces irrational information. It's called FMEM mode (Failure Mode Effects Management).
My research indicates there are TWO flag bytes where this condition is registered, but I cannot verify their 'bit' assignments. You can read them with a custom PID entry in Torque Pro. It would be tremendously helpful to me (and forum members) to find out if one of those flag bits are set TRUE. I know the PID byte numbers - but with a properly working truck, I never see any of the flags set ! They both should ALWAYS be zero. I do not know which bit means what, but know both bytes should be zero.
It would be most interesting if you would create TWO custom PIDs, If you go to >Settings >Manage Extra Sensors/PIDs - select Menu and >Add
Mode/PID - 221106
Long Name - MFEM Flag1
Short Nm - MFEM1
Equation - A
Mode/PID - 22107
Long Name - MFEM Flag2
Short Nm - MFEM2
Equation - A
You could then select them from the create gauge list and report their reading on your truck.
You did FANTASTIC. Though it seems it's not going to be the silver bullet. But I am VERY confident of my research - indicating that BOTH those bytes should be ZERO (Have No bits turned on). Now regrettably, I have NOT been able to verify the accuracy of my ALL data on most of the bit assignments.
The formula I gave you just takes the contents of the PID response and converts it to a digital value. SO_ 33 indicates there are two flag bits turned ON in PID byte 1107. In binary that looks like this "00100001". Bit Zero (the far right one) indicates the PCM is operating in Camshaft Position Sensor Failure Mode. ???? I do not quiet understand that, but that bit has been verified. [I remove the question mark and replace it in my database with the Bit# when they are verified).
The other bit (bit 5) -[with a value of 32), is one of those I don't trust. (What the hell is "Exhaust Gas 01 sensor" ???. That bit COULD have something to do with Fuel Rail Pressure also - casting doubt on results of my research. I will be MOST interested in following any feedback/resolution to this case.
Perhaps best approach available here is to share all the data I have (for better or worse) on these two FLAG BYTES. What I can tell you is : They BOTH should be ZERO / NO bits set. So something is wrong, and the PCM is operating based on default values for some sensors or parameters. If there is any hint of problems with Cam retard - I have reasonable faith in the Bit Zero indicator (enough that I might spring for a couple of CPS sensors. I Just don't understand it fully here or its association with Fuel Rail pressure problems. Actually, I suspected and had hoped one of the Unknown bits would be set and indicate Fuel Rail Pressure failure mode. As I mentioned, that May be Bit 5 instead of the listed bizzar Exhaust Gas 01 Sensor ....!!
PID.........Mode/PID ..OBD rsp..Bit.. Acrynom ..Description
1106 221106 62110600 ba? PCFM In Electronic pressure control failure mode
1106 221106 62110600 bb? MAFFM Mas Air Flow in FMEM mode (mfmflg)
1106 221106 62110600 bc? ECTF Engine Coolant Temperature Failure FMEM mode
1106 221106 62110600 bd? EGRFM EGR system in failure FMEM mode
1106 221106 62110600 be? IATFM Intake Air Temperature Failure FMEM mode
1106 221106 62110600 bf? VSSFM Vehicle Speed Sensor Failure FMEM mode
1106 221106 62110600 bg? X?unk X?unk
1106 221106 62110600 bh? X?unk X?unk
1107 221107 62110700 ba0 CMPFM Camshaft Position Sensor Fault MFEM Mode
1107 221107 62110700 bb? OSSFM In Output shaft speed failure FMEM mode
1107 221107 62110700 bc2 TFTFM Transmission oil temperature sensor failure FMEM mode
1107 221107 62110700 bd3 TCCFM Torque Converter Clutch unlocked (FMEM) due to excessive slip
1107 221107 62110700 be? O2S11_FL HO2S21 Lack of switching failure
1107 221107 62110700 bf? O2S11FM Exhaust Gas O1 sensor failure
1107 221107 62110700 bg? O2S21_FL HO2S11 Lack of switching failure
1107 221107 62110700 bh? O2S21FM Exhaust Gas O2 sensor failure
Please Keep me posted on progress with this.
The formula I gave you just takes the contents of the PID response and converts it to a digital value. SO_ 33 indicates there are two flag bits turned ON in PID byte 1107. In binary that looks like this "00100001". Bit Zero (the far right one) indicates the PCM is operating in Camshaft Position Sensor Failure Mode. ???? I do not quiet understand that, but that bit has been verified. [I remove the question mark and replace it in my database with the Bit# when they are verified).
The other bit (bit 5) -[with a value of 32), is one of those I don't trust. (What the hell is "Exhaust Gas 01 sensor" ???. That bit COULD have something to do with Fuel Rail Pressure also - casting doubt on results of my research. I will be MOST interested in following any feedback/resolution to this case.
Perhaps best approach available here is to share all the data I have (for better or worse) on these two FLAG BYTES. What I can tell you is : They BOTH should be ZERO / NO bits set. So something is wrong, and the PCM is operating based on default values for some sensors or parameters. If there is any hint of problems with Cam retard - I have reasonable faith in the Bit Zero indicator (enough that I might spring for a couple of CPS sensors. I Just don't understand it fully here or its association with Fuel Rail pressure problems. Actually, I suspected and had hoped one of the Unknown bits would be set and indicate Fuel Rail Pressure failure mode. As I mentioned, that May be Bit 5 instead of the listed bizzar Exhaust Gas 01 Sensor ....!!
PID.........Mode/PID ..OBD rsp..Bit.. Acrynom ..Description
1106 221106 62110600 ba? PCFM In Electronic pressure control failure mode
1106 221106 62110600 bb? MAFFM Mas Air Flow in FMEM mode (mfmflg)
1106 221106 62110600 bc? ECTF Engine Coolant Temperature Failure FMEM mode
1106 221106 62110600 bd? EGRFM EGR system in failure FMEM mode
1106 221106 62110600 be? IATFM Intake Air Temperature Failure FMEM mode
1106 221106 62110600 bf? VSSFM Vehicle Speed Sensor Failure FMEM mode
1106 221106 62110600 bg? X?unk X?unk
1106 221106 62110600 bh? X?unk X?unk
1107 221107 62110700 ba0 CMPFM Camshaft Position Sensor Fault MFEM Mode
1107 221107 62110700 bb? OSSFM In Output shaft speed failure FMEM mode
1107 221107 62110700 bc2 TFTFM Transmission oil temperature sensor failure FMEM mode
1107 221107 62110700 bd3 TCCFM Torque Converter Clutch unlocked (FMEM) due to excessive slip
1107 221107 62110700 be? O2S11_FL HO2S21 Lack of switching failure
1107 221107 62110700 bf? O2S11FM Exhaust Gas O1 sensor failure
1107 221107 62110700 bg? O2S21_FL HO2S11 Lack of switching failure
1107 221107 62110700 bh? O2S21FM Exhaust Gas O2 sensor failure
Please Keep me posted on progress with this.
Ok first off thanks for the help. First you think I should look into the crank shaft sensor and 2nd I wonder if the exhaust gas sensor is the downstream o2 sensor because i did notice while playing with torque app that one of bank 1 o2 sensor 2 (downstream) had zero volts while bank 2 sensor 2 was reading
Drew, that is interesting and just the type information I was hoping to flush out. Please keep in mind - the data I have been able to acquire in this area is very 'sketchy' at best. Even including non-Ford, non-mechanical factors (ie: counting bits. MANY people incorrectly count bits starting with ONE instead of ZERO. That fact alone COULD change your Bit with a weight of 32 from "Exhaust Gas 01 sensor failure" to the immediately before it.
Then - on top of that, the description of that particular one references the different sensor from the Acronym. I noticed that originally, but do not have sufficient information to reliably correct the text.
Additionally - many people count from the wrong end of the digital byte!! (But experimenting with that makes less sense). Doesn't seem Trans Temp or Torque convertor issues are relevant.
But I am comfortable that these bytes store failure mode indicators. FORD's IDS (diagnostic system) tells the user IF certain sensor values are Default values - and NOT directly from the sensor. It has to have a way to know that - and I am sure these are the bytes contain that data.
As for CPS (Camshaft Position Sensor), I have verified that one with another Forum Member. But unfortunately and confusingly, I do not know what the meaning of either bit zero or bit five in your scenario has to do with P0193. But neither should be there.
Maybe - just maybe, this information can help somewhere. And just maybe we can purify the list. Your O2 sensor readings DO SEEM TO FALL AMONG the ones dealing with lack of switching or O2 failure. If in your shoes, I would be inclined to try to make them go away.
Then - on top of that, the description of that particular one references the different sensor from the Acronym. I noticed that originally, but do not have sufficient information to reliably correct the text.
Additionally - many people count from the wrong end of the digital byte!! (But experimenting with that makes less sense). Doesn't seem Trans Temp or Torque convertor issues are relevant.
But I am comfortable that these bytes store failure mode indicators. FORD's IDS (diagnostic system) tells the user IF certain sensor values are Default values - and NOT directly from the sensor. It has to have a way to know that - and I am sure these are the bytes contain that data.
As for CPS (Camshaft Position Sensor), I have verified that one with another Forum Member. But unfortunately and confusingly, I do not know what the meaning of either bit zero or bit five in your scenario has to do with P0193. But neither should be there.
Maybe - just maybe, this information can help somewhere. And just maybe we can purify the list. Your O2 sensor readings DO SEEM TO FALL AMONG the ones dealing with lack of switching or O2 failure. If in your shoes, I would be inclined to try to make them go away.
Well I switched bank 2 o2 sensor (the one showing 0 volts) to bank 1 to see if i had sensor failure. But even after switching it it still says 0 volts bank 2. I do have voltage at the plug of bank 2 same as voltage at bank 1 plug .Its like the pcm isn't seeing it.
Just to update I did find some bent pins in my pcm 2 was almost if not touching. I pulled out my pcm and carefully tried my best to straighten them up. The bent pins was not the ones that go to the FRP sensor but was the 2 right beside them. But after I fixed everything best I could and reset my pcm cranked engine run good but the engine lite came right on with same p0193 code.






