OBDII issue

[tommckay]

I have a 2004 Ranger Supercab 2wd with a 4.0. No issues with it, but I was going to run my OBDII scanner on it to see what might pop up. The scanner connected but the errored out saying to make sure the vehicle is OBDII compliant. Huh??

I have used this scanner on a 2012 Cadillac SRX, a 1998 Chevy S10 and another vehicle so it does work on those. Granted this is not a high dollar scanner, it's just one of those dongles that connects to your phone.

Any advice on what the issue may be? I'd like to be able to scan it when necessary!

 

[franklin2]

There is a fuse that can blow and you will not have any power to the port. It's the same fuse as the cigar lighter, in the smart junction box it's fuse 29, 20 amp.

 

[tommckay]

It does seem to have power. the lights on the dongle illuminate as they should and it emits the WiFi signal my phone can connect to. It does connect to the dongle, but the dongle can't communicate with the truck.

 

[sgtsandman]

Is the read CAN complaint? I'm pretty sure OBDII Rangers are CAN Bus and not all readers are able to read CAN.

 

[SenorNoob]

I'd be kinda surprised if anything new enough to do bluetooth to a phone wasn't CAN compatible. But OP should probably post up what they have just in case.

 

[tommckay]

Is the read CAN complaint? I'm pretty sure OBDII Rangers are CAN Bus and not all readers are able to read CAN.

OK, that I did not know. I have a WiFi OBDII interface (ELM327 type) and the 'auto Doctor App" on my i-phone that easily read codes and cleared them on the GM vehicles I have used it on. I thought OBDII was OBDII on all makes. Didn't realize Ford was different.

 

[sgtsandman]

OK, that I did not know. I have a WiFi OBDII interface (ELM327 type) and the 'auto Doctor App" on my i-phone that easily read codes and cleared them on the GM vehicles I have used it on. I thought OBDII was OBDII on all makes. Didn't realize Ford was different.

There are different busses. The Hondas I owned were different than Ford. I couldn't tell you the difference, only that there is one.

I believe the wired adapter I have for forscan is an ELM327 type. The blue tooth one I have, I believe is the same.

I could be the app that is the problem but that is only a guess since I've never used it. Up until forscan, I've only used dedicated scanners and I had to setup the ScangaugeII code reader to read Honda, and later Ford, since they were different.

 

[tommckay]

@sgtsandman - Thank you. I appreciate the information. I'm sure what I have is not FORscan compliant and therefore causing my issue.