Quote:
Originally Posted by kevinstotz
I used the hdv100a3 to grab the data.
But that one is only so good. I managed to store the data in MySQL and parse it to draw graphs.i can do it in the fly as well, but I need to parse out the dip records.
The next step is to make it usable for different adapters. It seems they all put out the data a bit different.
I also purchased a Bluetooth adapter, will make that work as well.
I am thinking of adding a producer/consumer option so one can feed the data and pull it down without the risk of losing data and easing the load
There might also be an opportunity for adding other obd cod s from other vehicles. This data surrounding the other vehicles is pretty scattered about the Internet.
What are your thoughts
|
part of the issue is the proprietary data points.. apparently navistar and CAT both have quite a few.. in the case of my Navistar they send more on the 1708 interface than they do on the 1939.. on the later stuff the Maxxforce 2007-2009 that were stil HEUI engines they sent the ICP / IPR related SPN's in a completely one-off PGN that is request only.. and of course those are some important data points if tuning an engine or trying to diagnose a driveability issue or why a code sets..
in the case of the 1708 navistar uses PID 154 / 155 / 164 .. of those only 164 is industry standard... the only way I knew of 154 and 155 and how to decode them are because i have the source-code to their Diagnostic software (servicemaxx)..