Yep, that is all consistent with what I have here. Don't know what that green wire (pin 14) on the GM OBD2 connector is for, so I measured the voltage on that pin of the AllPro and got 2.5v, which I suppose must have some purpose, I just don't know what. I don't have it connected to anything in my bench harness. Orange wire connected to pin 16, pink wire from pcm is switched to pwr. I think the wiring of the bench harness is correct from what I've seen. I'm able to load files using OBDLink-LX.

So do these symptoms match the Chinese counterfeit chip problem, or does it sound like something else?

Jim

 

Hi all,

Jim. Pin 14 is for CAN Low. Which is NOT needed for our purposes, so I wouldn't be surprised to find the Devices applying voltage to the pin.
As for the "Counterfeit chip" problem, from all I have read most cheap Chinese products use v1 firmware - usually modified to indicate v1.5.
THOSE devices ALSO usually do NOT have any circuitry for J1850 ! i.e. NOTHING connected to Pin 2 of the DLC connector.
Officially, there is v1, 1.2, 1.3, 1.4, 1.4a, and then it skips to 2.x with 2.1 being the latest.
SO, if the OBDLink-SX device works, yet the AllPro does NOT, I would suspect the AllPro. If it was a port problem, you would not be able to receive ANYTHING in response to commands sent to the Device.

Mike

 

Thanks Mike, that all makes sense. If Scott was a little closer I'd see if he could try the cable since his works but Columbus is about 1-1/2hrs from here and I don't want to impose. If that's the USB to UART chip though that doesn't look very hard to replace at all. Just have to find the right one at digikey. Does that sound feasible? I'd need to know how to tell if it is the right chip.

Jim

 

Hi all,
Jim, the USB to UART chip seems to be OK - otherwise you would NOT be communicating with the "Interpreter chip."
Beyond this, I am unsure how to proceed other than to find someone with a newer CANBUS vehicle (2008+) and try running some apps to access IT,
Even running a "terminal app" such as PUTTY should tell if the rest of the cable is OK.
Of course PCMHammer WILL NOT work on those newer PCMs.

Mine

 

OK, Sounds like I'm SOL then. Thanks for helping troubleshoot it, I very much appreciate the help. I'll just wait until I see Scott again and maybe he'll want to try it then but likely as not it is a write off. (After all, if he gets it to work then I have bigger problems.) In the meantime I hope things go smoothly in finding a replacement for pcm-hammer. I'll probably have to buy a tune from someone since I'm on a deadline in about 3 months, but maybe I can use it for fine tuning on down the road.

Jim

 

Hi all,

Jim, if you're able to use an OBDLink LX device, then all is not lost.
It will just take longer to read or write the PCM!

Mike.

 

Thanks Mike. I guess I had assumed that just because I couldn't access anything in pcmh because the allpro wouldn't connect, that there were things there like being able to open and save files and manipulate the tune in some ways that TunerPro might not be able to do. Frankly at this point I must admit that I really have a very poor understanding of what pcmh actually does do, other than speed up the access.

In all fairness, I've merely scratched the surface with TunerPro and should probably concentrate my efforts there. Still I want you all to know that I'm very favorably impressed with your efforts and wish you good karma, etc.

Jim

 

I just ordered an ObdLink LX to test with. Until now I've been using an SX.

Pete tells me that the LX/MX/MX+ can send and receive larger messages than the SX, so they should be a lot faster, after some changes to the app to take advantage of that.

 

I think you will like the LX. It could be a little sensitive to fluctuations in the power supply so that's something to watch but otherwise seems quite solid.

Jim

 

Did you get your LX yet?

Jim

 

Seems that the pre-write checks are not working for all OSes? Seems like the only ones it's happy with are 01-02 OSes. I have PCMs directly out of stock vehicles and other stock bins i've downloaded and almost every one of them it thinks is corrupt and prevents me from doing anything. The one that I didnt have issues with I know has issues since the serial number is corrupt on it. These are all the older 4896 PCMs


[07:32:17:516] C:\Users\jamesr\Downloads\'oo Camaro LS1 M6 os9381344.bin
[07:32:17:533] Validating 512k file.
[07:32:17:538] Start End Result File Actual Content
[07:32:17:545] 0 7FFFD Good 5E0D 5E0D Operating system
[07:32:17:551] 8002 13FFF BAD 510F 0B4C Engine calibration
[07:32:17:557] 14002 16DFF BAD AAAA E7E7 Engine diagnostics.
[07:32:17:564] 16E02 1BDFF BAD 0000 A5C5 Transmission calibration
[07:32:17:571] 1BE02 1C7FF BAD 0000 3BA8 Transmission diagnostics
[07:32:17:581] 1C802 1E51F BAD 005A 8BB3 Fuel system
[07:32:17:590] 1E522 1EE9F BAD 4AFC 1DFC System
[07:32:17:599] 1EEA2 1EF9F BAD 4AFC CCFC Speedometer
[07:32:17:610] This file is corrupt. It would render your PCM unusable.

 

Sorry about that. I'm pretty sure we have that fixed now, it'll be in the next release.

 

Wow. Not sure how i missed this thread over the years. I have an ObdLink MX sitting around so this is very interesting indeed.

I want to add a thanks to those putting in work on this!

 

Speaking of ObdLink MX... does it support 4x yet?

 

The ObdLink hardware doesn't support 4x, but I'm working on changes now that will allow the app to take better advantage of the LX and MX, so they'll be much faster than the SX. Coincidentally, my first successful write with an LX finished while I was typing this, and it took 2 minutes 53 seconds. If I remember right, the SX took about 8 minutes.

 

No...and it probably never will....

 

NSFW: nice work!

Pete: boo! (j/k, big fan, you're doing some really great work here) You need to convince them to implement 4x - they said they're just waiting for a compelling reason to enable it

 

After about 8 months talking to them on and off about this...I can tell you it's not going to happen. Right about the time I was expecting them to give me a thumbs up on implementing 4x the conversation took a rather unexpected turn and any chances of it being added was made clear that it was not going to happen now or ever. I'm summarizing how an 8 month long conversion ended but they were not exactly polite in my last contact with them.

 

Ouch. Well, their loss then.

 

Correction - flashing with the SX took 4.5 minutes, not 8. The LX is certainly faster at 3 minutes, but the difference isn't quite as dramatic as I thought.

When the next release goes out, the ObdLink LX or MX-Bluetooth (not wifi) will be the recommendations for people who don't already have something.