Page 34 of 97

Re: PCM Hammer - new ls1 flash tool

Posted: Sat Feb 23, 2019 12:50 pm
by NSFW
I suspect we can fix reading for that P59 if we add that OS to the app's internal list of known OSes. I'll see if I can get you a test build this weekend.

Re: PCM Hammer - new ls1 flash tool

Posted: Sat Feb 23, 2019 1:08 pm
by DavidBraley
NSFW wrote:I suspect we can fix reading for that P59 if we add that OS to the app's internal list of known OSes. I'll see if I can get you a test build this weekend.
No hurry. When PCM Hammer is able to read this odd OSID, I can compare the bins generated by the BDM device and PCM Hammer and report back if it helps.

Re: PCM Hammer - new ls1 flash tool

Posted: Sat Feb 23, 2019 1:23 pm
by Speedy
David,

Using PCM Hammer v4 and an AllPro USB cable, I sucessfully read a P59, with the same service# 12586243 / hardware# 12583659; however, it contained a different operating system# 12587603.

Re: PCM Hammer - new ls1 flash tool

Posted: Sat Feb 23, 2019 1:29 pm
by DavidBraley
Speedy wrote:David,

Using PCM Hammer v4 and an AllPro USB cable, I sucessfully read a P59, with the same service# 12586243 / hardware# 12583659; however, it contained a different operating system# 12587603.
Speedy,

I too have a Service# 12586243 / Hardware# 12583659 with OSID# 12587603 here on my bench, and PCM Hammer reads it just fine. It's possible that the problem is what NSFW mentions above about the OSID 12612114 not being in a list of OS's in PCM Hammer.

Re: PCM Hammer - new ls1 flash tool

Posted: Mon Feb 25, 2019 3:32 am
by BillNobody
I tried PCM Hammer last night. I'm excited about the possibilities, but having an issue with hardware. Using a Mini-VCI j2534 tool, the program "connects" successfully to the device but does not connect to the PCM, fails VIN query. PCM is a 411, 5.3 truck bin, etc etc. I can read the PCM fine with hp tuners so I know the PCM is fine. PCM is not locked etc. I'll have to get on my PC later and post screen shots of the logs, but basically it just has a timeout error when trying to connect to the pcm. Any thoughts or suggestions, modifications and what direction to take? I'm not afraid of delving into the .cs file fairly familiar with the .net end of things. Thanks for reading, my apologies if it's hard to read, typing on my phone and a tad scatter brained until the coffee kicks in. Have a good day/evening.

Bill Nobody

Re: PCM Hammer - new ls1 flash tool

Posted: Mon Feb 25, 2019 7:48 am
by antus
Do you have any details about the mini vci interface? I dont think any one has tried one of those yet. Is a full blown interface or some kind of cut down one which may be lacking? The vin is the first packets that are slightly too long for an elm, so Im suspect of the interface. Can you cut and paste all the logs from the debug tab in to a text file and upload?

Re: PCM Hammer - new ls1 flash tool

Posted: Mon Feb 25, 2019 8:57 am
by yager
Hi, :)
I sorta get this far, which is good.
As you can see a have a P04 PCM and not the P01/P05 etc.
but i figure that i can at read the .BIN and i can muddle my way through it..

[05:45:36:628] PCM Hammer 005
[05:45:36:659] Voltage: 11.9V
[05:45:36:659] Elm ID: ELM327 v2.1
[05:45:36:675] All Pro ID: Copyright (c) 2009-2018 ObdDiag.Net This is free software; see the source for copying conditions.
[05:45:36:691] All Pro self test result: PWM wiring is OK VPW wiring is OK ISO9141/14230 wiring is OK CAN wiring is OK
[05:45:36:697] All Pro firmware: 1.22
[05:45:49:961] VIN: 1G2WR5216YF313778
[05:45:50:046] OS ID: 12201791
[05:45:50:124] Calibration ID: 12201784
[05:45:50:193] Hardware ID: 9357440
[05:45:50:394] Serial Number: 8DCDL40295
[05:45:53:562] BCC query failed: Error
[05:45:53:631] MEC: 0


This is just 'Read Properties'
Cool !

Re: PCM Hammer - new ls1 flash tool

Posted: Mon Feb 25, 2019 9:38 am
by antus
Sorry but p04 is not supported. Thanks for posting up what you have got but you wont be able to read a bin.

Re: PCM Hammer - new ls1 flash tool

Posted: Mon Feb 25, 2019 1:18 pm
by flyn-brian
Here is an 03 Sierra In which I reversed the fuel guage to work in my Avalanche

Re: PCM Hammer - new ls1 flash tool

Posted: Mon Feb 25, 2019 2:01 pm
by BillNobody
Antus,

1. The Mini VCI J2534 is a "generic" Chinese Clone of the XHorse J2534 pass-thru device. Its primary usage is Toyota products, i got it last year to tinker with and write an API for J2534, but havent made any progress with that, too many outstanding projects. I thought I'd give it a try just for kicks since I saw the PCM Hammer supported J2534.

I also tried with a USB ELM327 device using the Mock Serial port, it reads the VIN...sorta. It just lists the VIN as 12345ABCDEF123456.

Here is the debug log of what I'm seeing. Hope this gives you some sort of indication, although I know its difficult to say since you don't have my particular hardware to test, but maybe its just something in the code we can touch up. Thanks for any input. Have a great day folks.

//***********

[09:39:24:283] PCM Hammer 005
[09:39:24:284] Initializing J2534 Device
[09:39:24:285] Loaded DLL
[09:39:25:029] Connected to Scantool
[09:39:25:045] Battery Voltage is: 12
[09:39:25:047] Battery Voltage is: 12
[09:39:25:061] Protocol Set
[09:39:25:078] Filter Set
[09:40:13:542] Will save to D:\j1850_Data\PcmHammer005\PcmHammer005\ASDF.bin
[09:40:13:547] Querying operating system of current PCM.
[09:40:13:607] TX: 6C 10 F0 3C 0A
[09:40:15:645] ReadMsgs OBDError: ERR_TIMEOUT
[09:40:17:661] ReadMsgs OBDError: ERR_TIMEOUT
[09:40:19:676] ReadMsgs OBDError: ERR_TIMEOUT
[09:40:21:692] ReadMsgs OBDError: ERR_TIMEOUT
[09:40:23:708] ReadMsgs OBDError: ERR_TIMEOUT
[09:40:23:711] Receive timed out. Attempt #5, Timeout #5.
[09:40:23:714] TX: 6C 10 F0 3C 0A
[09:40:25:740] ReadMsgs OBDError: ERR_TIMEOUT
[09:40:27:754] ReadMsgs OBDError: ERR_TIMEOUT
[09:40:29:771] ReadMsgs OBDError: ERR_TIMEOUT
[09:40:31:771] ReadMsgs OBDError: ERR_TIMEOUT
[09:40:33:787] ReadMsgs OBDError: ERR_TIMEOUT
[09:40:33:791] Receive timed out. Attempt #5, Timeout #5.
[09:40:33:795] Operating system query failed, will retry: Error
[09:40:33:836] J2534 setting VPW 4X
[09:40:33:881] TX: 6C 10 F0 20
[09:40:33:898] J2534 setting VPW 1X
[09:40:33:946] TX: 6C 10 F0 20
[09:40:33:995] TX: 6C 10 F0 3C 0A
[09:40:36:026] ReadMsgs OBDError: ERR_TIMEOUT
[09:40:38:025] ReadMsgs OBDError: ERR_TIMEOUT
[09:40:40:025] ReadMsgs OBDError: ERR_TIMEOUT
[09:40:42:025] ReadMsgs OBDError: ERR_TIMEOUT
[09:40:44:024] ReadMsgs OBDError: ERR_TIMEOUT
[09:40:44:030] Receive timed out. Attempt #5, Timeout #5.
[09:40:44:036] TX: 6C 10 F0 3C 0A
[09:40:46:056] ReadMsgs OBDError: ERR_TIMEOUT
[09:40:48:056] ReadMsgs OBDError: ERR_TIMEOUT
[09:40:50:055] ReadMsgs OBDError: ERR_TIMEOUT
[09:40:52:055] ReadMsgs OBDError: ERR_TIMEOUT
[09:40:54:055] ReadMsgs OBDError: ERR_TIMEOUT
[09:40:54:062] Receive timed out. Attempt #5, Timeout #5.
[09:40:54:069] Operating system query failed: Error
[09:40:54:077] Will assume this is a 512kb PCM in recovery mode.
[09:40:54:090] Suppressing VPW chatter.
[09:40:54:100] TX: 6C FE F0 28 00
[09:40:54:137] Sending 'test device present' notification.
[09:40:54:145] TX: 8C FE F0 3F
[09:40:54:199] Sending seed request.
[09:40:54:208] TX: 6C 10 F0 27 01
[09:40:56:230] ReadMsgs OBDError: ERR_TIMEOUT
[09:40:56:237] No response to seed request.
[09:40:56:245] Unlock was not successful.

//****************

Bill