pcmhacking.net

MudDuck514 wrote:

Sudsy wrote: Thanks for your reply. Do you know if they come shipped with a cable or is there a special cable needed as well. I couldn't see any mention of it on the site

When I bought mine a couple of years ago, they didn't come with the cable (standard micro USB). Fortunately they are plentiful and cheap (DollarTree ones worked fine).
My understanding is NOW they include a good quality cable with the device! BONUS!

Mike

No worries. I thought i had edited the post but obviously i did something wrong. I did go back and actually looked at the other pics in the ad and there is a cable shown. Just a bit hard to see for this old fart lol

Just for info
My first try to download software from P01 using PCMhammer and OBDlink SX failed
I reflashed OBDlink to latest firmware and .....noope )
So I started thinking
My bench was PC-Obdlink-P01-power source (good 14v 15A stabilized buut its AC/DC inverter)
I checked 14V from source by oscilloscope -all good no spikes
But somehow there is some fluctuation that prevent stable connect
And I realized that PC has AC/DC inverter and source has and they not synchronized but connected between not only by common ground but AC wiring from socket
After that I eliminated PS from chain and power up PCM from PC directly (+12V yellow wire )
Now I have zero disconnects

V8fan wrote:Just for info
My first try to download software from P01 using PCMhammer and OBDlink SX failed
I reflashed OBDlink to latest firmware and .....noope )
So I started thinking
My bench was PC-Obdlink-P01-power source (good 14v 15A stabilized buut its AC/DC inverter)
I checked 14V from source by oscilloscope -all good no spikes
But somehow there is some fluctuation that prevent stable connect
And I realized that PC has AC/DC inverter and source has and they not synchronized but connected between not only by common ground but AC wiring from socket
After that I eliminated PS from chain and power up PCM from PC directly (+12V yellow wire )
Now I have zero disconnects

Now THAT is very strange, as the two power supplies SHOULDN'T interfere with one another.
FYI "AC to DC" is a converter. "DC to AC" is an inverter.

Mike

IMO That would be a faulty VCI, as it (the VCI) should isolate them from each other ... That is part of it's job!

-Enjoy

MudDuck514 wrote: Now THAT is very strange, as the two power supplies SHOULDN'T interfere with one another.
FYI "AC to DC" is a converter. "DC to AC" is an inverter.

Mike

Okay) = PC source and 14 DC source both dc/dc from +310 to +12 (220v AC=310 DC or more if it has active power corrector factor)
And they both isolated inside
But there is some little capacitance between coils into transformers and high frequency can and do penetrate from that capacitance as noise plus into 220ac inlet usually 2 little caps (0.033 or so) that connects both phase and 0 to ground and "-" of PC source is connected to that ground too
Of course I can add battery or big capacitor to be buffer zone (or inductive+cap)
But easiest way for me just use 1 power source with no interference

Gampy wrote:IMO That would be a faulty VCI, as it (the VCI) should isolate them from each other ... That is part of it's job!

-Enjoy

Yes pro adapters has optical isolation -but cheap OBDLink SX hasn't
This info only for information that can be and sometimes better use 12v good battery as PS for PCM for bench supply

I have run into another P59 that PCM Hammer is having trouble reading. Here in the shop I have a 2006 GMC Yukon Danali with 6.0 . OSID is 12587811, and Hardware ID is 12589162. Logs attached.

I feel like timings for "waiting" for devices need a bit of changing based on those logs.

I can see a 4 second gap where no tester present is sent, resulting in a mode 60 response from the engine computer which indicates it has returned back to normal operations.

[11:12:40:583] Module 0x10 (engine controller) has agreed to enter high-speed mode.
[11:12:40:587] Sending 'test device present' notification.
[11:12:40:587] TX: 8C FE F0 3F
[11:12:44:717] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[11:12:44:719] Sending 'test device present' notification.
[11:12:44:719] TX: 8C FE F0 3F
[11:12:46:726] TX: 6C FE F0 A1
[11:12:48:743] RX: 6C F0 10 60 <- This is where engine computer has gone back to sleep.

I actually had a similar issue recently using my MDI and OBDX tool. Ill see if I cant do a fresh pull and edit later today, as I also need to alter some OBDX stuff too

I decided to try and read this PCM with Jet Tuners and it too gave me an error when it got to the task of reading the memory. The error from Jet Tuners is "Memory Read Aborted. Unknown MSComm Error. (F/1) Everything up to that point worked perfect. PCM unlocked, went into 4x speed. Could this truck have been tuned by someone and somehow locked out?

I dont think so, sounds more like falty hardware either a module or the pcm. can you try it on the bench?

antus wrote:I dont think so, sounds more like falty hardware either a module or the pcm. can you try it on the bench?

No was not able to. Customer had to pick up. It does have me wondering though. I know Jet makes those tuner ecus that plug directly into the pcm and then the plug that plugs into pcm plugs into it, pretty much just piggybacking the connector. I am wondering how one of those actually works. Also wonder if one of those can cause this issue. I will take another stab at it next time he brings his truck here.