PCM Hammer P01 and P59 flash tool v015

They go by many names, P01, P59, VPW, '0411 etc. Also covering E38 and newer here.
User avatar
antus
Site Admin
Posts: 8237
Joined: Sat Feb 28, 2009 8:34 pm
cars: TX Gemini 2L Twincam
TX Gemini SR20 18psi
Datsun 1200 Ute
Subaru Blitzen '06 EZ30 4th gen, 3.0R Spec B
Contact:

Re: PCM Hammer - new ls1 flash tool

Post by antus »

No thats not the one. The USA have a VPW PCM on the Buick v6, that was supported by DHP, and Tiny Tuner. http://theblattners.com/Projects/TinyTuner/default.html

Thats the one mostly being talked about when V6 support is requested. I think ls1droid has it now, but we dont have access to that kernel at this stage (and its architected quite differently too).

There are a bunch of bin files from that PCM and car models listed in this thread. viewtopic.php?f=27&t=5174 which also says its service number 09380717.
Have you read the FAQ? For lots of information and links to significant threads see here: http://pcmhacking.net/forums/viewtopic.php?f=7&t=1396
MudDuck514
Posts: 397
Joined: Wed Jul 05, 2017 8:30 am
cars: 2001 Pontiac Grand AM SE
LD9 2.4l I4, 4T40E
2005 Chevrolet Venture
LA1 3400 V6, 4T65E
Location: North TX, USA

Re: PCM Hammer - new ls1 flash tool

Post by MudDuck514 »

Holden202T wrote:when you say adding support for V6 PCM's what do you mean ?

ie. i have an 02 chev blazer V6 PCM, its an 0411, pcm hammer technically already supports it in that it can ID it and start a read, however it fails to complete at 4% (quick chat to Antus he thought it might be a timing issue or something)

or are you referring to other model V6 PCM's ?

The V6s in question would be those that run the 60 degree v6 series in front-wheel drive applications. I.E. the Pontiac Grand Am.
Also there are 90 degree v6 cars using the Buick 3800s, such as the Pontiac Grand Prix.

Mike
dynotech
Posts: 13
Joined: Thu Oct 12, 2017 5:27 pm
cars: BA XR6 turbo

Re: PCM Hammer - new ls1 flash tool

Post by dynotech »

Any hints on getting PCM hammer to recognize my Drew Tech Mongoose Pro ISO/CAN J2534 cable

I get the message "Unable to initialize J2534 Device"

Device is installed correctly and working with other programs

Regards
Phil
User avatar
antus
Site Admin
Posts: 8237
Joined: Sat Feb 28, 2009 8:34 pm
cars: TX Gemini 2L Twincam
TX Gemini SR20 18psi
Datsun 1200 Ute
Subaru Blitzen '06 EZ30 4th gen, 3.0R Spec B
Contact:

Re: PCM Hammer - new ls1 flash tool

Post by antus »

Hmm it works with mine, the GM variant. I'd assume its some kind of driver issue, but not sure. I have one of those and an MDI2 both as J2534 devices on my system and I can select either or.
Have you read the FAQ? For lots of information and links to significant threads see here: http://pcmhacking.net/forums/viewtopic.php?f=7&t=1396
dynotech
Posts: 13
Joined: Thu Oct 12, 2017 5:27 pm
cars: BA XR6 turbo

Re: PCM Hammer - new ls1 flash tool

Post by dynotech »

antus wrote:Hmm it works with mine, the GM variant. I'd assume its some kind of driver issue, but not sure. I have one of those and an MDI2 both as J2534 devices on my system and I can select either or.
My cable isn’t the GM one, but it’s fully J2534 compliant and a genuine drew tech item
User avatar
antus
Site Admin
Posts: 8237
Joined: Sat Feb 28, 2009 8:34 pm
cars: TX Gemini 2L Twincam
TX Gemini SR20 18psi
Datsun 1200 Ute
Subaru Blitzen '06 EZ30 4th gen, 3.0R Spec B
Contact:

Re: PCM Hammer - new ls1 flash tool

Post by antus »

Post up the debug tab log.
Have you read the FAQ? For lots of information and links to significant threads see here: http://pcmhacking.net/forums/viewtopic.php?f=7&t=1396
dynotech
Posts: 13
Joined: Thu Oct 12, 2017 5:27 pm
cars: BA XR6 turbo

Re: PCM Hammer - new ls1 flash tool

Post by dynotech »

antus wrote:Post up the debug tab log.

[08:54:48:299] PCM Hammer 006
[08:54:48:311] Initializing J2534 Device
[08:54:48:331] Loaded DLL
[08:54:48:391] Connected to Scantool
[08:54:48:391] Battery Voltage is: 0
[08:54:48:391] Battery Voltage is: 0
[08:54:48:395] Unable to initialize J2534 Device
[08:54:48:403] System.FormatException: Format String can be only "G", "g", "X", "x", "F", "f", "D" or "d".
at System.Enum.ToString(String format)
at PcmHacking.J2534Device.InitializeInternal() in C:\GitHub\PcmHacks\Apps\PcmHammer\Devices\J2534Device.cs:line 151
at PcmHacking.J2534Device.<Initialize>d__16.MoveNext() in C:\GitHub\PcmHacks\Apps\PcmHammer\Devices\J2534Device.cs:line 82
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
at PcmHacking.Vehicle.<ResetConnection>d__16.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
at PcmHacking.MainForm.<InitializeCurrentDevice>d__23.MoveNext() in C:\GitHub\PcmHacks\Apps\PcmHammer\MainForm.cs:line 454
[08:54:48:607] Thanks for using PCM Hammer.
dynotech
Posts: 13
Joined: Thu Oct 12, 2017 5:27 pm
cars: BA XR6 turbo

Re: PCM Hammer - new ls1 flash tool

Post by dynotech »

Heres 1 connected to the whilst plugged into the OBD port on a vehicle

02:12:11:358] PCM Hammer 006
[02:12:11:358] Initializing J2534 Device
[02:12:11:359] Loaded DLL
[02:12:11:413] Connected to Scantool
[02:12:11:416] Battery Voltage is: 13.8
[02:12:11:417] Battery Voltage is: 13.8
[02:12:11:418] Unable to initialize J2534 Device
[02:12:11:420] System.FormatException: Format String can be only "G", "g", "X", "x", "F", "f", "D" or "d".
at System.Enum.ToString(String format)
at PcmHacking.J2534Device.InitializeInternal() in C:\GitHub\PcmHacks\Apps\PcmHammer\Devices\J2534Device.cs:line 151
at PcmHacking.J2534Device.<Initialize>d__16.MoveNext() in C:\GitHub\PcmHacks\Apps\PcmHammer\Devices\J2534Device.cs:line 82
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
at PcmHacking.Vehicle.<ResetConnection>d__16.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
at PcmHacking.MainForm.<InitializeCurrentDevice>d__23.MoveNext() in C:\GitHub\PcmHacks\Apps\PcmHammer\MainForm.cs:line 454
User avatar
NSFW
Posts: 679
Joined: Fri Feb 02, 2018 3:13 pm

Re: PCM Hammer - new ls1 flash tool

Post by NSFW »

Based on the trace messages and the exception message, it looks like the code below blew up. The call to ConnectToProtocol failed, and after that the call to m.Value.ToString("X2") failed because of the 2 in X2, so the app wasn't able to print a useful error message.

But, if not for that 2nd bug, I suspect that the app would have logged an error code that indicates that your J2534 device doesn't support J1850 VPW.

Code: Select all

            m = ConnectToProtocol(ProtocolID.J1850VPW, BaudRate.J1850VPW_10400, ConnectFlag.NONE);
            if (m.Status != ResponseStatus.Success)
            {
                this.Logger.AddDebugMessage("Failed to set protocol, J2534 error code: 0x" + m.Value.ToString("X2"));
                return false;
            }
Please don't PM me with technical questions - start a thread instead, and send me a link to it. That way I can answer in public, and help other people who have the same question. Thanks!
User avatar
Tazzi
Posts: 3422
Joined: Thu May 17, 2012 8:53 pm
cars: VE SS Ute
Location: WA
Contact:

Re: PCM Hammer - new ls1 flash tool

Post by Tazzi »

NSFW wrote:Based on the trace messages and the exception message, it looks like the code below blew up. The call to ConnectToProtocol failed, and after that the call to m.Value.ToString("X2") failed because of the 2 in X2, so the app wasn't able to print a useful error message.

But, if not for that 2nd bug, I suspect that the app would have logged an error code that indicates that your J2534 device doesn't support J1850 VPW.

Code: Select all

            m = ConnectToProtocol(ProtocolID.J1850VPW, BaudRate.J1850VPW_10400, ConnectFlag.NONE);
            if (m.Status != ResponseStatus.Success)
            {
                this.Logger.AddDebugMessage("Failed to set protocol, J2534 error code: 0x" + m.Value.ToString("X2"));
                return false;
            }
I think thats correct, the X2 should have put it into hex string format.. so not sure why thats errored out there?
But the response is likely saying that the tool does not support that protocol.
Your Local Aussie Reverse Engineer
Contact for Software/Hardware development and Reverse Engineering
Site:https://www.envyouscustoms.com
Mob:+61406 140 726
Image
Post Reply