|
nossliw
|
 |
« on: June 12, 2012, 12:55:05 pm » |
|
I specifically bought an I phone for this app to start managing our fleet of 7.3's. I was wondering if there were any other users that have played around with PID's for diesels yet, or the 7.3 in specific. For instance it would be really nice to get a reading on ICP, IPR, and a few others. I have read others who are using "torque app" are able to use PIDs and extending their parameters to create readouts for ICP, IPR, and so on.
It may be completely possible I am not looking in the right area for these read outs since I am a complete newb(2 days in) to this app and have yet to get a read out regarding any parameter. However I will say there are a ton of 7.3 owners on the net very curious in this app and are wondering what the full capabilities for readouts are versus purchasing a scan gauge to get these readings. I was hoping Dash Command would do so since the developers produce a very similar software.
Any help would be appreciated....
|
|
|
|
« Last Edit: June 12, 2012, 09:34:10 pm by nossliw »
|
Logged
|
|
|
|
|
nossliw
|
 |
« Reply #1 on: June 12, 2012, 08:41:08 pm » |
|
Well on another note I am having absolutely no luck getting a single read out at all... Tonight was the first night I got to play around with the app and kiwi device and absolutley nothing after 1.5 hours. I know the OBD-II connection is being made since the green dot on the left stays lit green. It also cuts the truck out for a split second when connecting while running. Says its reading the VIN but does not write it under the vehicle profile. States its checking PIDs but nothing comes of it. I get absolutely nothing on any read outs revs/speed/map/coolant/and so on. These are all parameters that can be checked on a scan gauge including:
rpm
speed
volts
pw
ICP
trans temp
oil temp
coolant temp
DC %
and many more
What am I doing wrong. there is a connection or load that is not being made. Is there other sofware I need to be using in conjunction with the kiwi device to translate to dashcommand? Did not think it would be this hard.
I have set up the subnet/router/ and so on set correctly as stated on the trouble shooting page. I even deleted the router number just to try it.
Trucks are FORD 97 F350 7.3 PSD'S,
On another note it did not work in the gas trucks either....
|
|
|
|
|
Logged
|
|
|
|
|
nossliw
|
|
« Reply #2 on: June 12, 2012, 09:29:48 pm » |
|
after looking at the console i noticed that there is not one single supported parameter.... The software scans and does not upload any PID information since it is supposedly not supported. After reading the fuel mileage consumption errors it strictly can not calculate them since I currently do not have a lambda value.... The only information that is being used is the data I entered in for the calc section. not a single PID is supported, so in other words does this mean this software is complete non compatible with Fords 7.3 diesel trucks? 99-03 trucks have the exact same PID read outs plus a couple more. Sort of worried about the statement of functions with all OBD-II supported vehicles now....  |
|
|
|
|
Logged
|
|
|
|
|
nossliw
|
|
« Reply #3 on: June 13, 2012, 07:42:57 am » |
|
Any tech support comments from any one. Is this sys incompatible with diesels? Once again this morning absolutely nothing......
|
|
|
|
|
Logged
|
|
|
|
|
Cody@PPE
|
|
« Reply #4 on: June 13, 2012, 09:02:53 am » |
|
Start by clicking the box to disable mode $09 in the Vehicle Manager. Then try changing the OBD-II timeout to 600ms. After that, connect and click "Validate PIDs" from the vehicle settings. Let me know if that works
|
|
|
|
« Last Edit: June 13, 2012, 09:28:43 am by Weston@PPE »
|
Logged
|
|
|
|
|
nossliw
|
|
« Reply #5 on: June 13, 2012, 10:27:50 am » |
|
Ok I will give that a shot when it get back home this evening. Thank you for the response. Hope it's a start!  |
|
|
|
|
Logged
|
|
|
|
|
|
|
nossliw
|
|
« Reply #7 on: June 13, 2012, 11:32:33 am » |
|
Well this is not good to hear by any means. I really hope this is not the issue and some thing much more simple or this entire ordeal is a wasted 220 bucks. I guess I'll give Plx a call here soon too. I'll try the new settings when I get home to the trucks. I have a feeling that it is connecting ok but the software is not reading the pids. I will send the log if it gets to that but I hope i can get it resolved.
|
|
|
|
|
Logged
|
|
|
|
|
John@PPE
|
|
« Reply #8 on: June 13, 2012, 01:02:35 pm » |
|
I think we'll be able to figure it out. If it turns out to be hardware then I would expect PLX to refund your money, so you can get a device that works on your trucks.
If it is software then we'll be able to get it working.
|
|
|
|
|
Logged
|
|
|
|
|
nossliw
|
|
« Reply #9 on: June 13, 2012, 01:34:57 pm » |
|
Well I tried calling them with no luck. Opened up their support ticket and described my issues. Also included a link to this thread. Hopefully I have some luck tonight if not I will send a support email to you guys.
|
|
|
|
|
Logged
|
|
|
|
|
nossliw
|
|
« Reply #10 on: June 14, 2012, 06:48:10 am » |
|
I gave it a shot last night with the new settings and had the same issue. It connects fine to the truck however does not relay any of the PIDS. Therefore not a single gauge works. Also I noticed I have a red circle with a exclamation mark when I go into the code reader for the truck. Its for a readiness monitor. Not sure if this helps out at all but I was not sure why it did it.
I sent my techlog to you guys so hopefully that provides you with more insight of the issues I'm having.
Hopefully we can get this figured out!
|
|
|
|
|
Logged
|
|
|
|
|
nossliw
|
|
« Reply #11 on: June 15, 2012, 07:16:09 am » |
|
I have not received an email back from support. Nor a reply where to go from here. Please let me know.....
|
|
|
|
|
Logged
|
|
|
|
|
John@PPE
|
|
« Reply #12 on: June 15, 2012, 08:47:10 am » |
|
You should be getting a reply back by today, I would expect. Sometimes the logs have a lot of information to sift through.
|
|
|
|
|
Logged
|
|
|
|
|
nossliw
|
|
« Reply #13 on: June 18, 2012, 07:06:27 am » |
|
Still no reply 3 days later it woul be nice to get this working.......
|
|
|
|
|
Logged
|
|
|
|
|
nossliw
|
|
« Reply #14 on: June 19, 2012, 07:21:52 am » |
|
Well just an update..: I tried using the app with a friends Subaru and Chevy pick up. Worked great. The reply from tech support asked what country my truck was sold in since it was relating that it was not obd-2 supported. Like I said I know it's supported since the scan gauge I use is strictly based off the obd-2 platform. And all these trucks were american made and sold here in colorado. Like I said, this app did not work on 3 different 7.3 diesels. I know that their pid I'd is a bit different than most has vehicles but if the app does not read them then a disclaimer should be written in the app description that it does not cover 7.3 ford diesels.
|
|
|
|
|
Logged
|
|
|
|
|
John@PPE
|
|
« 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
|
|
« 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
|
|
« 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
|
|
« 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
|
|
|
|
|
