2006 f 350
Bought an elm 327, and a cheapo android small tablet, installed the ford pids, everything is working just like it is suppose to, reading the following;
coolant temp, oil temp, deltas, trans temp, ficm power, ficm sync and some others.
I do not think that Ive done any thing that would cause a failure, I did the blue spring mod, in doing so I unplugged the sensors on the air filter housing and the pipe going to the turbo, I cycled the key a number of times to activate the fuel pump,when I was done I plugged everything back in. Started the truck and CEL was on. I hooked up my obd scanner and cleared the codes. Since then no light or any problems. Except the torque pro says ECU cannot read pids.
I get a reading on engine coolant , and trans temp but everything else is 0 or blank
I am at loss as what to do.

 

Check and see if the cig lighter has voltage,if not check the fuse. I'll bet you get your pics back

 

I'll check thanks for the idea

 

ok update,
cig lighter was fine no blown fuses, what I did was to disconnect both batteries wait about 15 minutes and try again, this time all I could get out of the torque pro was "sleeping"
never seen that before, messed around with it, shut the tablet off and turned it on a few times and low and behold its working fine, it connected to the OBD quicker than it ever has and seem that all pids are working.... what the heck did I do. I hate it when something screws up then it just kind of fixes itself.

the user name is different im using someone elses computer sorry

 

I have messed around some in the settings for the OBD adapter, and it is interesting as to how many PIDs you are interrogating (that is what Torque is doing: asking your truck's PCM for data), and how fast the PCM can respond, or the OBD unit can handle the back and forth.

I have a cheap-o OBD BT adapter and have it set on doing quicker requests/reads, and it is just fine. Maybe less than 20 PIDs per screen? You get a big screen, where you can do more PIDs, and... Well you'll have to figure out what the update rate can handle....

 

I have two screens set up,
screen one, two large gauges oil and coolant temp with delta
screen two, mainly ficm power and 6 other items, never had a problem reading the and displaying the values.
This whole thing was out of the blue. It was working just fine and then its not working.
I do have another question,
I have a 1999 f 250 7.3 that I inserted the BT OBD reader into and tried to use torque pro, it would not connect to the PCM and it would not display any values in torque pro.
I am wondering if this might of caused all my problems?

 

They run two different systems. Did you create a new profile for the older truck? Because then Torque will see them as two different vehicles, and not the one that is "talking" differently all of the sudden...

 

Don't sweat it. Mine does that occasionally. My scanguage does it to so it might be the vehicle and not the app.

 

Dan, do you think it was because I didn't set up a new profile for the 1999 f 250, I think that is when the real trouble started... I just plugged it in and started torque pro.
Like I said above, the torque pro and the 06 f 350 are working just like they are suppose to now, I guess it just finally recognized the f 350 profile.

 

I don't think so. I have my truck's profile set up in torque pro and it still occasionally does it.

 

This is nothing to worry about. When it pops up with that statement, just touch the screen again and it will start to scan for codes.

My does it too.

 

I'm not knowledgeable enough to answer, I do know that starting somewhere around 2003 is when the CAN Bus data protocol came out. But since Torque can talk to earlier protocols, that was my thought: maybe it confused it? I know I tried reading some codes off a '99 PSD and couldn't get crap to work, but I didn't try for long and I didn't even think to set up a new vehicle profile. The '99 was my ex-truck a friend now owns, so I might try hooking up to it again.

I don't recall any issues the next time I used Torque on my 6.0, so that was just a stab in the dark on my part....

It sounds like your up and running, which is the good news