Modular V10 (6.8l)  

OBDII not seeing ECU/never mind

Thread Tools
 
Search this Thread
 
  #1  
Old 10-17-2015, 01:23 PM
dogugotw's Avatar
dogugotw
dogugotw is offline
New User
Thread Starter
Join Date: Jul 2015
Posts: 7
Likes: 0
Received 0 Likes on 0 Posts
OBDII not seeing ECU/never mind

I have a bluetooth dongle type OBDII sensor that connects to the Torque app. It connects under the dash without any issue and connects to the phone but the dongle doesn't find the sensor.

I have a 97 Triton V-10 85L Super Duty chassis. My suspicion is that the truck's electronics are too old for the dongle I'm using but thought I'd toss it out here to see if anyone had any ideas. I'll also post on the Torque site.

I want to be able to see and clear error codes and possibly display RPMs or maybe engine temps.

Thanks for any ideas you may have.

Doug

Edit
Never mind...The truck is ODB1 not ODB2 and my sensor and app are not compatible.
 

Last edited by dogugotw; 10-17-2015 at 01:48 PM. Reason: figured it out
  #2  
Old 11-19-2015, 02:10 PM
Sam I Am's Avatar
Sam I Am
Sam I Am is offline
Posting Guru
Join Date: Jun 2009
Location: Fort Smith, Arkansas
Posts: 1,908
Likes: 0
Received 11 Likes on 11 Posts
Torque reads my 1999 V10 truck, no problems.
If the Bluetooth dongle you have is not reading the truck, try another dongle. Some dongles are not compatible with some protocols.
 
  #3  
Old 11-19-2015, 05:51 PM
dogugotw's Avatar
dogugotw
dogugotw is offline
New User
Thread Starter
Join Date: Jul 2015
Posts: 7
Likes: 0
Received 0 Likes on 0 Posts
yep

Originally Posted by Sam I Am
Torque reads my 1999 V10 truck, no problems.
If the Bluetooth dongle you have is not reading the truck, try another dongle. Some dongles are not compatible with some protocols.
Totally right, the dogleg doesn't work. Any suggestion for one that works with obd1?
 
  #4  
Old 11-19-2015, 11:28 PM
Sam I Am's Avatar
Sam I Am
Sam I Am is offline
Posting Guru
Join Date: Jun 2009
Location: Fort Smith, Arkansas
Posts: 1,908
Likes: 0
Received 11 Likes on 11 Posts
The Bluetooth dongle I have was given to me by a friend who bought it on ebay so I don't know what brand or seller.
It is black, about 3.5" long, and says ELM327 1.5. It has connected to every OBD2 vehicle I have tried.
It looks exactly like the one in this link except mine is black instead of blue:
Newest ELM327 V1 5 Bluetooth EOBD OBD2 Interface Auto Diagnostic Scanner Adapter | eBay
 
  #5  
Old 11-20-2015, 04:20 AM
dogugotw's Avatar
dogugotw
dogugotw is offline
New User
Thread Starter
Join Date: Jul 2015
Posts: 7
Likes: 0
Received 0 Likes on 0 Posts
OBDI also?

Just to confirm, the dongle you posted also talks to ODBI systems?
Thanks
 
  #6  
Old 11-20-2015, 06:21 AM
projectSHO89's Avatar
projectSHO89
projectSHO89 is online now
Hotshot
Join Date: Jan 2004
Location: St Louis
Posts: 19,344
Likes: 0
Received 875 Likes on 727 Posts
97 Triton V-10 85L Super Duty chassis.
That doesn't make any sense.

Just to confirm, the dongle you posted also talks to ODBI systems?
For a Ford, it has to be an EEC-V PCM which can (and does) run both OBDI and OBDII software). The specific PCM calibration has no bearing on whether or not the dongle can communicate with the PCM as the communications protocol is the same.
 
  #7  
Old 11-20-2015, 07:45 AM
dogugotw's Avatar
dogugotw
dogugotw is offline
New User
Thread Starter
Join Date: Jul 2015
Posts: 7
Likes: 0
Received 0 Likes on 0 Posts
Originally Posted by projectSHO89
That doesn't make any sense.



For a Ford, it has to be an EEC-V PCM which can (and does) run both OBDI and OBDII software). The specific PCM calibration has no bearing on whether or not the dongle can communicate with the PCM as the communications protocol is the same.
Ok, you just moved beyond my understanding. The dongle I have talks to my phone app. The app shows no connection to the truck by the dongle. As I understand, my dongle is only able to read odb2 and the truck puts our odb1 so I would need a different dongle.

Also, not sure what doesn't make sense about the truck description. I didn't get the decimal point in the engine size so let me know what's out of whack. I bought this used and am not a gearhead so I am trying to piece the spec together from various stickers on or near the engine.

thanks for sticking with this, I appreciate the help.
 
  #8  
Old 11-21-2015, 08:26 AM
projectSHO89's Avatar
projectSHO89
projectSHO89 is online now
Hotshot
Join Date: Jan 2004
Location: St Louis
Posts: 19,344
Likes: 0
Received 875 Likes on 727 Posts
As I understand, my dongle is only able to read odb2 and the truck puts our odb1 so I would need a different dongle.
Your "understanding" is incorrect, see previous response. The dongle, in a Ford, talks to a specific version of the main computer (EEC-V processor). The EEC-V can and does run both OBD1 and OBDII calibrations. Therefore, saying the dongle talks only to OBDII is a misunderstanding. For example, my 2001 has an EEC-V PCM but it's an OBDI calibration and all the scan tools and dongles work just fine with it.




If you post the first 10 digits of your VIN, it's easier to determine what you have.
 
  #9  
Old 11-21-2015, 12:35 PM
Sam I Am's Avatar
Sam I Am
Sam I Am is offline
Posting Guru
Join Date: Jun 2009
Location: Fort Smith, Arkansas
Posts: 1,908
Likes: 0
Received 11 Likes on 11 Posts
OP is confusing OBD 1 compliance and OBD 1 equipment.
OBD2 became universally adopted for vehicles in USA for the 1996 model year but had been "phased in" on various models by different manufacturers over the prior couple of years due to variations in product design cycles.
OBD2 compliance requires broader and more comprehensive emissions controls than OBD1. Passenger cars and light duty trucks built for the 1996 model year and later are required to comply with OBD2 standards.
But since almost all the vehicles that the V10 is installed into are rated over 8500 pounds GVWR heavy duty trucks, these heavier vehicles were exempted from the tougher OBD2 standards and instead need only to comply with the less strict OBD1 standards.

The above mentioned heavy duty vehicles in the American (USA) market still have OBD2 hardware and are compatible with OBD2 "code readers". But they have some of the sensors "locked out" because they are not required for OBD1 compliance.

Regarding using the OBD2 dongle
Just to cover the most rudimentary basics, the key must be in the "On" position for the dongle to get any info from the vehicle computer.
First off, plug in the dongle to the OBD2 port and turn the ignition key to the "ON" position. Then make sure Bluetooth is enabled on your device and make sure the dongle is "paired" to the device.
Once the dongle is paired, open the Torque app and wait for the app to recognize the dongle and the vehicle's computer.
 
  #10  
Old 11-21-2015, 12:41 PM
Sam I Am's Avatar
Sam I Am
Sam I Am is offline
Posting Guru
Join Date: Jun 2009
Location: Fort Smith, Arkansas
Posts: 1,908
Likes: 0
Received 11 Likes on 11 Posts
The reason that I previously suggested trying a different dongle is that prior to 2008, there was not a unified signalling standard and some Bluetooth adapters may not communicate correctly with some vehicles.
 
  #11  
Old 11-21-2015, 03:09 PM
dogugotw's Avatar
dogugotw
dogugotw is offline
New User
Thread Starter
Join Date: Jul 2015
Posts: 7
Likes: 0
Received 0 Likes on 0 Posts
thanks

Originally Posted by Sam I Am
The reason that I previously suggested trying a different dongle is that prior to 2008, there was not a unified signalling standard and some Bluetooth adapters may not communicate correctly with some vehicles.
It is defiantly older than 2008!

VIN 1FDLE4057V
 
Related Topics
Thread
Thread Starter
Forum
Replies
Last Post
Tyler Babinski
1999 to 2016 Super Duty
2
12-05-2015 08:17 AM
skyfox10
1999 to 2016 Super Duty
3
03-08-2014 04:38 PM
Treker58
Excursion - King of SUVs
21
08-16-2013 04:37 PM
shivesy
Modular V10 (6.8l)
5
07-02-2008 02:46 PM
Monsta
Modular V10 (6.8l)
7
11-02-2007 09:07 PM



Quick Reply: OBDII not seeing ECU/never mind



All times are GMT -5. The time now is 09:12 PM.