Jump to content
CBR1100XX.org Forum

IcePrick

Members
  • Content Count

    10,977
  • Joined

  • Last visited

  • Days Won

    133

IcePrick last won the day on April 7

IcePrick had the most liked content!

Community Reputation

2,152 Excellent

About IcePrick

  • Rank
    The Power of the 'tard
  • Birthday 01/01/1964

Previous Fields

  • Other Bikes
    '97XX, '03 XR400, '08 KTM 530EXCR, '08 KTM 990ADV, a couple GasGas 450s (SM and Enduro)

Profile Information

  • Gender
    Male
  • Location
    Prescott, AZ

Recent Profile Visitors

13,248 profile views
  1. Something Italian.
  2. Well, it IS the Dave channel now... only fair that you fund it. I'm prepared to give up my free speech, but when does it IPO? 😚
  3. I hope this is the answer. It still wouldn't eliminate a problem in the harness along the way or a PCM/FICM malady, but here's to hoping. When I encounter a new problem on one of my machines, I have to ask myself "okay, what's the last thing you monkeyed with? Aaaand that's usually where I find my answer.
  4. Cool, you taught me something about Forscan. 😁
  5. What about trying a screen recorder app? Let the truck run while connected to the laptop, recording the screen to a video file. You won't have to stay glued to the screen waiting for it to randomly quit.
  6. I never understood this. Shouldn't a properly operating engine thermostat allow the engine to come to temp? Or is there enough constant bypass to keep it cold in those temps?
  7. Brown wire didn't work - key in "run" position? It isn't a manual, right? (don't hit me next time you see me) Based on what you say about temps - especially the minute or two of startup - guessing it is a false... so, how to find the source? Did you install the resistor, or was it modded when you bought it? Just a resistor to give a static value, or resistor in addition to sensor in order to send a lower but still variable value? If you disconnect the sensor (and don't have it jumped with a resistor), it should run but give a number of codes. One of th
  8. The starter bypass is a wire near one of your battery positive terminals - look for a lone wire that has a rubber pull-apart connection close enough to the positive lug to reach it when you pull it apart. It should be brown with a green tracer. It is on the passenger side on my 7.3, assumedly to keep you out of traffic if you need to be messing with it, so I'd guess it is on the passenger side of yours as well. Turn the key on, touch the male end of the connector to the battery positive clamp bolt, and viola - you bypassed the starter interrupt from the PCM, and while the 60-minute time-out
  9. Not sure if you ran across this more complete description in your search yet. P200E - Catalyst System Over Temperature (Bank 1) Description: The powertrain control module (PCM) monitors the exhaust gas temperature bank 1, sensor 2 (EGT12) and exhaust gas temperature bank 1, sensor 3 (EGT13) sensors for an over temperature concern. If the EGT12 sensor temperature is greater than 830°C (1,526°F) or the EGT13 sensor temperature is greater then 950°C (1,742°F), the DTC is set. This DTC causes the PCM to immediately illuminate the malfunction indicator lamp (MIL) and enter a torque
  10. Has anyone from FTE posted the diagnostics procedure (pinout) from the Ford manual for your code? It won't find an intermittent for you, but it can give you a laundry list of the systems, subsystems, harnesses, sensors, and dependencies involved. I like your guess about the non-specific code - my limited experience with the "generic" codes, ones that don't specifically say something like "EGT2, out of range (high)", are systemic and caused by ground problems, rfi, or wierdness in the responsible ecm. Are there any accessories installed in the truck that might induce rfi or otherwise cause a
  11. When you do the scan of stored codes, does it not indicate exactly which EGT sensor it is? I'm pretty certain that in Forscan, you can monitor each parameter in real time, and record it as well. I've seen people post up some nice graphs of selected parameters. Set it up to record, go change those carb shield bolts again? Graphs can be very telling when diagnosing intermittents, if you see a very radical value change in a very short time (near vertical line on a graph) it is likely a connectivity issue or failed sensor. Super Duties/Excursions have historically had
  12. They obviously access the same data, but Forscan can do a lot more than TP - especially in later-model vehicles. It's very versatile, but as it is a user-supported enthusiast application (read: both computer geek AND car freak), it can be a little mysterious or nonintuitive in certain modules. I've had good luck with it, but then again I've only used it for monitoring and diagnostics on older, less complex modules - not changing operational parameters and such. What you can do with it is dependent on the capabilities of the module you're working with, which is obviously affected by the yea
  13. Diesels in 2002 were not fully OBDII compliant. They have much of the data, just not in OBDII form. FORSCAN and a couple others have this reverse-engineered so that a user can read almost all of the necessary data with it. I can't recall the year of Joe's pickup but it should be recent enough for full OBDII. The issue is monkeying with more than just output data - there are a lot of defaults you can change in the software. Again, FORSCAN is fairly functional for most things, but not quite up to the OEM diagnostic/customization equipment.
×
×
  • Create New...

Important Information

Terms of Use