So here is some thing new my truck has started doing.

I have a 2000 F350 stock 7.3 and when I try to pull error codes with any brand of ODB2 scanner, as soon as the reader queries the computer the SES indicator lights up and shuts the engine off.

I've been getting intermittent SES lights and wanted to read the error codes to see what is going on. It doesn't matter what scanner I plug in, when I start the truck and it tries to read the computer the SES light comes on and it stalls the truck. I can't get the truck to start again until I unplug the scanner then it starts just fine.

Anyone have any ideas?

 

What kind of scanner are you using? These Trucks are not OBD Compliant the standard OBD scanners will not scan these Trucks. Do you know anybody with AE? (Auto Enginuity).

 

As far as I know you aren't supposed to have a vehicle running when you hook up an obd scanner, just have the key in the run position.

 

I have a similar issue with my 99 f350. The dealership can not read anything on the computer, says their scanners just come up blank.

 

Not sure what you dealer has, but is should read your truck and you can and should be able to reader/scanner hooked up while running, I do it with my AE all the time.

 

huh, same here man. I got a POS scanner, says it can run live data, but kills the motor when cycling. Think i'll save up for an AE

 

I was talking about a regular code reader, not the ones that can pull live data.

 

Generally you will see this with a scanner that is attempting to connect using Standard OBD-II protocol. If you can find someone with AE, and you set the connection settings to J1850PWM and NON-OBDII, it should connect without stuttering the engine. This is because with these settings the tool doesn't have to try to do any "auto-detect" for the protocol and it doesn't try to connect with OBD-II communication methods that the PCM doesn't like. Any tool that doesn't let you disable the "auto-detect" and OBD-II protocols is likely to cause the problem.

 

No I plug in the scanner first, then start the vehicle. After it is running, when the scanner tries to get codes, it stalls.

I've used several different brands, like Actron, Aultel, Xitech and one that used a Ford specific plugin module to read Ford specific codes. The latest was a bluetooth XiTech module that connects to my Droid X phone. It works awesome with my Saturn and Kia!

Have not used Auto Enginuity as I don't know anyone with one. Looks like I'll have to suck it up and take it to the stealership and have them try to read it.

 

Dan, Kwikordead, is somewhere out that way and I think he has an AE.

 

OBDII scanners will not read the codes on these trucks. I have a SuperChip Tuner that will scan codes off of the 7.3s.

 

like said before you dont have to have engine running for code retrieval or erasing . try with just the key on . i use a snap on scanner and it does both codes and live (running)data.

 

i kind of just ran across this thread by accident... while coming over here from the OBDLink forum, but thought i'd comment about this.

The ECU in the Ford F350 with 7.3 litre engines has a bug with mode 9 OBD2 queries that will shut the engine off. So if scanner software (or OBD software like Torque) makes a request for mode $9 data like a VIN... it will shut the engine down. That is why they've added a disable for mode $9 for the protocol used by this engine.

https://www.scantool.net/forum/index...53173#msg53173

 

Just in case the rest of you are wondering, these are what the 9 OBD2 modes are. I know I was.

@rvborgh1 , the thread you replied to is 9 years old but your information is much appreciated. It sounds like you have delved deeper into OBD2 than most of us shadetree mechanics on here have.

 

@rvborgh1 Excellent post. Reps sent. It doesn't matter how old this thread is, it is still YEARS NEWER than the trucks which it pertains to, and the trucks cannot magically change themselves to something different than how they were originally built.

Far better to raise up an old thread that is precisely on topic, so that there is context and a sense of resonance on how others had the same concern. Additionally, it makes finding all proposed solutions to the concern under one heading, in one thread.

So no one should be made to feel bad for bringing up an old thread. This forum began coinciding with the introduction of the 99-up Super Duty, which renders nearly every thread in the 99-03 archives as newer than the foundation vehicle to which it applies.

For what it is worth, not even the Ford Rotunda / Hickok Instruments New Generation Star Tester factory dealership scan tool can read the VIN on a '99-'03 7.3L via the J1850 protocol. A separate J2534 protocol device is used for reflashing the calibration to the PCM.