pcmhacking.net

Johnfx wrote:Blue and red connector not green my mistake.........anyways left off the red and was able to flash a modified bin. Really had me stumped tried different vers of both Hammer and cable OS. Need to get a bench setup!

John,

Something that I do know to help reliability is to make sure the systems voltage stays high enough when reading and writing. Some of these hardware interfaces can be really slow when doing a full write. I've only programmed these 1220411 PCM's on the bench, but I'm guessing you can attach a battery charger to the battery if needed to insure things stay above 12 volts while doing this in the vehicle. I would recommend attaching the battery charger with the ignition off, before you hook up the obd2 interface and start any reading or writing of the pcm.

DavidBraley wrote:

Johnfx wrote:Blue and red connector not green my mistake.........anyways left off the red and was able to flash a modified bin. Really had me stumped tried different vers of both Hammer and cable OS. Need to get a bench setup!

John,

Something that I do know to help reliability is to make sure the systems voltage stays high enough when reading and writing. Some of these hardware interfaces can be really slow when doing a full write. I've only programmed these 1220411 PCM's on the bench, but I'm guessing you can attach a battery charger to the battery if needed to insure things stay above 12 volts while doing this in the vehicle. I would recommend attaching the battery charger with the ignition off, before you hook up the obd2 interface and start any reading or writing of the pcm.

The read time for OBDlink sx is horrible but write time was 6 mins....not too bad. Im used to BMW tools which can take hours for a full write. Just took a 4 hour trip to Savannah..had to come catch this hurricane. Yukon is running great! but I'm still getting some low rpm heavy load spark knock. Going to pull the plugs when the weather clears and see whats up. Excellent forum!

Thanks for the feedback! The obdlink sx is probably the slowest least capable interface currently supported. The elm protocol its based on was really not designed for this type of work. It has its own extended protocol which has the potential to improve speed a bit, but to date its not implemented. For speed your better off with a device that supports vpw 4x and can stream packets rather than requiring polling. To date that is a J2534 interface (which themselves can be a mixed bag - I use an MDI, and drewtech GM interfaces with success), and the AVT. It sounds like your on the right path.

Antus, or anyone that can help with a cable.

I have 3 cables now. None will read past this error
[09:47:28:039] Querying operating system of current PCM.
[09:47:28:044] OSID: 12593358
[09:47:28:067] Unlock succeeded.
[09:47:28:080] This interface does not support VPW 4x
[09:47:28:091] Uploading kernel to PCM.
[09:47:28:099] Permission to upload kernel was denied.
[09:47:28:103] Failed to upload kernel to PCM
[09:47:28:112] Clearing trouble codes.
[09:47:28:121] Elapsed time 00:00:00.0510054
[09:47:28:125] Read failed, Error

I'm searching for "J2534 J1850 VPW USB obdii" and this is what I come up with.
will this cable work?

Thanks,
Dan

what cables are you using? want to post up the debug tab output so we can see whats going on? It might not be a problem with all of the cables. But that osid looks like the same OS that NSFW has so it should be expected to work.

I don't believe I have the right cable. but this log will probably tell you that.
I have a K+DCAN cable, HPTuners, and an ELMm 327 cable that said it supported VPW, but since I now see ELM 327 isn't supported I'm sure I need a new cable. I just don't know where to go from here. I sure don't want to order a $275 cable...
Here is the log, I which I could pair it down to just what you need.

[10:45:15:114] PCM Hammer 006
[10:45:16:715] Sending message 6C 10 F0 3C 01
[10:45:16:721] Mock PCM Received: 6C (Pri3 GM1 No_IFR Phy), Scanner/tester to ECU, Read Data Block / VIN 1 (ASCII)
[10:45:16:726] Sending message 6C 10 F0 3C 02
[10:45:16:726] Mock PCM Received: 6C (Pri3 GM1 No_IFR Phy), Scanner/tester to ECU, Read Data Block / VIN 2 (ASCII)
[10:45:16:727] Sending message 6C 10 F0 3C 03
[10:45:16:727] Mock PCM Received: 6C (Pri3 GM1 No_IFR Phy), Scanner/tester to ECU, Read Data Block / VIN 3 (ASCII)
[10:45:16:729] VIN: 12345ABCDEF123456
[10:45:16:736] Sending message 6C 10 F0 3C 0A
[10:45:16:737] Mock PCM Received: 6C (Pri3 GM1 No_IFR Phy), Scanner/tester to ECU, Read Data Block / 4-byte Operating System ID
[10:45:16:739] OS ID: 12593358
[10:45:16:742] Sending message 6C 10 F0 3C 08
[10:45:16:743] Mock PCM Received: 6C (Pri3 GM1 No_IFR Phy), Scanner/tester to ECU, Read Data Block / calibration ID (UINT32)
[10:45:16:743] Calibration ID: 12345
[10:45:16:746] Sending message 6C 10 F0 3C 04
[10:45:16:746] Mock PCM Received: 6C (Pri3 GM1 No_IFR Phy), Scanner/tester to ECU, Read Data Block / HDW No. (UINT32)
[10:45:16:746] Hardware ID: 23456
[10:45:16:751] Sending message 6C 10 F0 3C 05
[10:45:16:751] Mock PCM Received: 6C (Pri3 GM1 No_IFR Phy), Scanner/tester to ECU, Read Data Block / Serial No 1 (ASCII)
[10:45:16:752] Sending message 6C 10 F0 3C 06
[10:45:16:752] Mock PCM Received: 6C (Pri3 GM1 No_IFR Phy), Scanner/tester to ECU, Read Data Block / Serial No 2 (ASCII)
[10:45:16:752] Sending message 6C 10 F0 3C 07
[10:45:16:753] Mock PCM Received: 6C (Pri3 GM1 No_IFR Phy), Scanner/tester to ECU, Read Data Block / Serial No 3 (ASCII)
[10:45:16:760] Serial Number: 123423453456
[10:45:16:766] Sending message 6C 10 F0 3C 14
[10:45:16:766] Mock PCM Received: 6C (Pri3 GM1 No_IFR Phy), Scanner/tester to ECU, Read Data Block / Broadcast Code (BCC) (ASCII)
[10:45:16:767] Broad Cast Code: 4321
[10:45:16:770] Sending message 6C 10 F0 3C A0
[10:45:16:770] Mock PCM Received: 6C (Pri3 GM1 No_IFR Phy), Scanner/tester to ECU, Read Data Block / Manufacturer Enable Counter
[10:45:16:771] MEC: 123
[10:45:30:647] Will save to F:\Users\Dan\Documents\Cars\914 LS DAN\TUNING LS TunerPro\PcmHammer006\mnbvn.bin
[10:45:30:650] Querying operating system of current PCM.
[10:45:30:653] Sending message 6C 10 F0 3C 0A
[10:45:30:656] Mock PCM Received: 6C (Pri3 GM1 No_IFR Phy), Scanner/tester to ECU, Read Data Block / 4-byte Operating System ID
[10:45:30:658] OSID: 12593358
[10:45:30:664] Suppressing VPW chatter.
[10:45:30:665] Sending message 6C FE F0 28 00
[10:45:30:665] Mock PCM Received: 6C (Pri3 GM1 No_IFR Phy), Scanner/tester to Broadcast, Disable Normal Message Transmission / 4-byte Operating System ID
[10:45:30:667] Sending 'test device present' notification.
[10:45:30:668] Sending message 8C FE F0 3F
[10:45:30:668] Mock PCM Received: 8C (Pri4 GM1 No_IFR Phy), Scanner/tester to Broadcast, Test Device Present / 4-byte Operating System ID
[10:45:30:671] Sending seed request.
[10:45:30:673] Sending message 6C 10 F0 27 01
[10:45:30:673] Mock PCM Received: 6C (Pri3 GM1 No_IFR Phy), Scanner/tester to ECU, Security Access Mode / 4-byte Operating System ID
[10:45:30:674] Parsing seed value.
[10:45:30:677] Sending unlock request (ED2A, A623)
[10:45:30:678] Sending message 6C 10 F0 27 02 A6 23
[10:45:30:679] Mock PCM Received: 6C (Pri3 GM1 No_IFR Phy), Scanner/tester to ECU, Security Access Mode / 4-byte Operating System ID
[10:45:30:680] Unlock succeeded.
[10:45:30:688] Sending 'test device present' notification.
[10:45:30:689] Sending message 8C FE F0 3F
[10:45:30:689] Mock PCM Received: 8C (Pri4 GM1 No_IFR Phy), Scanner/tester to Broadcast, Test Device Present / 4-byte Operating System ID
[10:45:30:692] This interface does not support VPW 4x
[10:45:30:713] Loaded F:\Users\Dan\Documents\Cars\914 LS DAN\TUNING LS TunerPro\PcmHammer006\read-kernel.bin
[10:45:30:718] Uploading kernel to PCM.
[10:45:30:723] Sending upload request for kernel size 4012, loadaddress FF8000
[10:45:30:725] Sending message 6C 10 F0 34 00 0F AC FF 80 00
[10:45:30:725] Mock PCM Received: 6C (Pri3 GM1 No_IFR Phy), Scanner/tester to ECU, Request Download (tool to module) / 4-byte Operating System ID
[10:45:30:728] Permission to upload kernel was denied.
[10:45:30:731] Failed to upload kernel to PCM
[10:45:30:736] Halting the kernel.
[10:45:30:738] Sending message 6C 10 F0 20
[10:45:30:739] Mock PCM Received: 6C (Pri3 GM1 No_IFR Phy), Scanner/tester to ECU, Return to Normal Mode / 4-byte Operating System ID
[10:45:30:740] Clearing trouble codes.
[10:45:30:744] Sending message 68 6A F0 04
[10:45:30:745] Mock PCM Received: 68 (Pri3 GM1 No_IFR Fun), Scanner/tester to DriverInfo, Request to Clear/ Reset Diagnostic Trouble Codes / 4-byte Operating System ID
[10:45:30:745] Sending message 68 6A F0 04
[10:45:30:746] Mock PCM Received: 68 (Pri3 GM1 No_IFR Fun), Scanner/tester to DriverInfo, Request to Clear/ Reset Diagnostic Trouble Codes / 4-byte Operating System ID
[10:45:30:746] Sending message 8C FE F0 14
[10:45:30:747] Mock PCM Received: 8C (Pri4 GM1 No_IFR Phy), Scanner/tester to Broadcast, Clear Diagnostic Information / 4-byte Operating System ID
[10:45:30:747] Sending message 8C FE F0 14
[10:45:30:748] Mock PCM Received: 8C (Pri4 GM1 No_IFR Phy), Scanner/tester to Broadcast, Clear Diagnostic Information / 4-byte Operating System ID
[10:45:30:749] Elapsed time 00:00:00.0639978
[10:45:30:753] Read failed, Error

Yep thats your problem. The first 2 are proprietry, and the elm cable can not do long packets required by programming. The cheapest (but also slowest) cable that is easily obtainable now is the obdlink sx. The vcx nano is a lot faster as its a j2534 interface, but (the big but) the market is flooded with fakes and its hard to get a real one that works. then tazzi and pete have a cable in the works, when that becomes available it'll probably be the cheapest and fastest option. I not sure they have an eta for that though.

Also that mock test is not terribly useful, it was more for us when developing the software. Its not sending data through your elm, so it does not show its limitations.

Thank you Antus.

I understand you also support OBDLink MX bluetooth. If that is correct, what setting should I use to use that?

Thanks,
Dan

For the ObdLink, go through the bluetooth pairing and then choose "ObdLink or AllPro" from the interface-type list.

I think the ObdLink LX and MX are the best option we have until Pete & Tazzi get theirs into production.

Not as fast as the $100+ options, but faster than SX, modest prices, and you know what you're getting when you order one.

Our first 10 boards are here to be soldered up. I do have to make a new update to PCMHammer to support the new device, since it now supports ELM commands by default (To work with OBD apps) but can switch to a byte protocol for speed and flexibility.
I was wanting to finish the J2534 driver for the device, as it would be nice to just select J2534 instead, but that wont be finished for a while.