Sign up for our newsletter! 
Home News Products Downloads Forum Distributors Store Contact Us
PPE User Forum
May 18, 2013, 11:56:26 am *
Welcome, Guest. Please login or register.

Login with username, password and session length
 
   Home   Help Search Login Register  
Pages: 1 [2]  All
  Print  
Author Topic: 97 F350 7.3 Powerstroke Diesel Issues- No readouts- readout fine with scangauge  (Read 2362 times)
0 Members and 1 Guest are viewing this topic.
John@PPE
Administrator
Hero Member
*****
Offline Offline

Posts: 761


View Profile
« Reply #15 on: June 19, 2012, 05:26:28 pm »

I haven't talked to our support team about this. I've been away from the office for a bit, so I don't know what your tech log showed.

Has PLX gotten back to you as to whether your hardware works with those 7.3 trucks?
Logged
nossliw
Newbie
*
Offline Offline

Posts: 16


View Profile
« Reply #16 on: November 14, 2012, 04:46:59 pm »

I wanted to just follow up on Dash Command and compatability with the 7.3 diesel. It simply is not compatable, and definantly should be stated in the app info. Ford released a specific bundle that allows scan tools to communicate with the FORD diesel PIDS. The only two companies I know using this bundle are Scan Gauge and Auto Enginuity.

It simply is a Ford 7.3 specific codec that allows the OBD2 and scan tool to communicate correctly. When I use Dash Command it does not communicate whatsoever with the OBD2 system, and my log reads that my vehicle is not OBD2 supported..which it is... Even typical scan tools at auto parts stores that do not have this codec can't communicate with a diesels PID readout.

I also wanted to note when Dash Command is used and connected with any of the 7 diesels I have tested it on (All 96 and 97 obd2 equipped trucks)... it kills the truck randomly when connected over a long period of time. Completely shuts the truck off under power, and going down the highway this is dangerous...

I will also comment that I tested this on Auto, manual, and 7.3 diesels that were chipped, and not chipped. Same result in all trucks...
« Last Edit: November 14, 2012, 04:49:40 pm by nossliw » Logged
Weston@PPE
Administrator
Hero Member
*****
Offline Offline

Posts: 1725


View Profile
« Reply #17 on: November 14, 2012, 05:32:03 pm »

There is a vehicle settings called "Disable Mode $09", which will stop DashCommand from killing the engine. Its a bug in the ECU itself, it does happen with some other scantools, and has nothing to do with DashCommand. I'm not aware of any other vehicles or engines that have an issue like this.

This setting was added specifically for this engine, there is no reason for it otherwise.
Logged
nossliw
Newbie
*
Offline Offline

Posts: 16


View Profile
« Reply #18 on: February 09, 2013, 08:44:34 pm »

Thank you for the info. I am still unable to get any read out. These trucks are absolutely obd2 compatible I have taken two to the dealer to verify and after a vin check on my 97 it came off the line in early 98 and was one of the last old body style trucks before the switch to the super duty release in 99.

I shure would like to get this resolved!
Logged
Pages: 1 [2]  All
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.13 | SMF © 2006-2011, Simple Machines LLC Valid XHTML 1.0! Valid CSS!
Page created in 0.096 seconds with 19 queries.
Home | News | Products | Downloads | Forum | Distributors | Store | Contact Us
Copyright © 2012 Palmer Performance Engineering, Inc. All Rights Reserved.