pcmhacking.net

Hope this is the right place for this, I have a couple of comments and questions about obdxplorer:

1. First of all, it is a breath of fresh air to have software with an interface that looks like it was designed after windows 3.1. Im really liking how readable and intuitive this is.
2. It looks like theres a bug in pid selection, If I sort the list by name, and then select pids, the wrong ones are put on the graph.
3. It might be my misunderstanding, but it doesnt look like its coming up with the correct code numbers when scanning for faults. My truck currently has a p1336 code, and in obdxplorer it comes up as p3336 (these numbers are from memory and so might be wrong, but the codes I get from obdx are different than other scan tools.)
4. Does this do the gm specific pids? Or even just custom defined pids?
5. I see you mentioned histograms, and external sensors, and man I cannot wait for that stuff. This is so much easier than other software. Any idea on a release date for that stuff?

Overall, this looks like an amazing piece of kit. For sure a big step up over other devices and software. Im excited to see where it goes.

pmcquay wrote:Hope this is the right place for this, I have a couple of comments and questions about obdxplorer:

1. First of all, it is a breath of fresh air to have software with an interface that looks like it was designed after windows 3.1. Im really liking how readable and intuitive this is.
2. It looks like theres a bug in pid selection, If I sort the list by name, and then select pids, the wrong ones are put on the graph.
3. It might be my misunderstanding, but it doesnt look like its coming up with the correct code numbers when scanning for faults. My truck currently has a p1336 code, and in obdxplorer it comes up as p3336 (these numbers are from memory and so might be wrong, but the codes I get from obdx are different than other scan tools.)
4. Does this do the gm specific pids? Or even just custom defined pids?
5. I see you mentioned histograms, and external sensors, and man I cannot wait for that stuff. This is so much easier than other software. Any idea on a release date for that stuff?

Overall, this looks like an amazing piece of kit. For sure a big step up over other devices and software. Im excited to see where it goes.

Sorting the list by name should have been disabled.
there is an actual search bar available now in the newest version available on the website.

Newest version also has histogram enabled

And finally, the fault code bug was also fixed in the latest revision.

I downloaded this software yesterday using the individual download because the all in one installer link was disabled, maybe I coincedentally hit on the time you were updating the site or something! I will check for updates!

Hmm. I must be missing something, the only version I can see is 1.0.0.2. is there somewhere else that I should be looking?

pmcquay wrote:Hmm. I must be missing something, the only version I can see is 1.0.0.2. is there somewhere else that I should be looking?

I will double check today!

*Edit
I had to clear the cache on the downloads page, it reverted to an old copy for whatever reason. Is downloaded the latest copy now.

Tazzi wrote:

pmcquay wrote:Hmm. I must be missing something, the only version I can see is 1.0.0.2. is there somewhere else that I should be looking?

I will double check today!

*Edit
I had to clear the cache on the downloads page, it reverted to an old copy for whatever reason. Is downloaded the latest copy now.

Thank Tazzi,
I had the same problem earlier.
Downloading new version as I type this.

Mike

Oh yes this is much better. Not a whole lot of chance to play with it before the kids got up, but it looks like the correct codes are coming through, and I like the new graphs. I did notice that the pid list is still sortable, and I think at least one of the codes that I have has the description incorrect. (P1665, evap vent. It says something about an oil pressure output). Super interested in the histogram interface, that will make tuning much simpler.

Are there plans to allow external sensors? I noticed on one of the dev documents that the obdx tools have adc channels, but I assume since its a generic case there would be some hardware hacking involved in using those. Perhaps some sort of interface for using the datalogging facilities of the more common widebands?

I saw ...somewhere? That there may be plans for bidirectional tests? Man that would put this thing on another playing field entirely.

pmcquay wrote:Oh yes this is much better. Not a whole lot of chance to play with it before the kids got up, but it looks like the correct codes are coming through, and I like the new graphs. I did notice that the pid list is still sortable, and I think at least one of the codes that I have has the description incorrect. (P1665, evap vent. It says something about an oil pressure output). Super interested in the histogram interface, that will make tuning much simpler.

Are there plans to allow external sensors? I noticed on one of the dev documents that the obdx tools have adc channels, but I assume since its a generic case there would be some hardware hacking involved in using those. Perhaps some sort of interface for using the datalogging facilities of the more common widebands?

I saw ...somewhere? That there may be plans for bidirectional tests? Man that would put this thing on another playing field entirely.

Fault codes should be correct, they are matched against GMs DTC list.
If you send me a fault code, I can verify against it.

External sensors will be something we are working on in the form of:
1) An OBDX scantool tool that will support external input
2) A new hardware that allows logging external inputs over canbus

As for bidirection tests, not too sure what you mean there? As in controlling parts of the car using diagnostic requests?

Yeah, P1665 is listed as "Engine oil pressure output circuit", when it should be evap vent circuit. Having a 96 c1500, the evap system is only partially compatible with the 0411, and the vent solenoid is left unplugged. Image attached, sorry about the photo of a screen.

I was talking about diagnostic requests yes, one of the things I see a lot on these is people who want to bleed the ABS system, and while there are workarounds, its not possible to trigger the OEM bleed procedure on the later Kelsey Hayes systems without the diagnostic requests, AFAIK.

In my specific case, I would like to be able to do a CASE learn without having to buy the dealer tool, or go to a shop.

I will likely buy the 3 day tech2win subscription, its not that expensive, now that I know that the VT is capable of performing as the hardware in that scenario. I read through the posts in this topic on the reverse engineering on that, and I'm only able to grasp the barest part of it. Really great work there. I've dealt with some similar buffoonery in APIs that are not for public consumption, but never on that scale.

pmcquay wrote:Yeah, P1665 is listed as "Engine oil pressure output circuit", when it should be evap vent circuit. Having a 96 c1500, the evap system is only partially compatible with the 0411, and the vent solenoid is left unplugged. Image attached, sorry about the photo of a screen.

I was talking about diagnostic requests yes, one of the things I see a lot on these is people who want to bleed the ABS system, and while there are workarounds, its not possible to trigger the OEM bleed procedure on the later Kelsey Hayes systems without the diagnostic requests, AFAIK.

In my specific case, I would like to be able to do a CASE learn without having to buy the dealer tool, or go to a shop.

I will likely buy the 3 day tech2win subscription, its not that expensive, now that I know that the VT is capable of performing as the hardware in that scenario. I read through the posts in this topic on the reverse engineering on that, and I'm only able to grasp the barest part of it. Really great work there. I've dealt with some similar buffoonery in APIs that are not for public consumption, but never on that scale.

Might need to read with the tech2 and see what it says? Id trust that over anything else.

The definitions I have match that of GDS2 (What they use for GM diagnostics on all new vehicles) which indicates P1665 is related to engine oil pressure?
I wonder if your specific vehicle uses a different fault code list??