PCM Hammer Release 021

They go by many names, P01, P59, VPW, '0411 etc. Also covering E38 and newer here.
a1953mdl
Posts: 7
Joined: Sat Apr 17, 2021 11:45 am

Re: PCM Hammer Release 021

Post by a1953mdl »

Thank you.
Evidentially it is locked. I haven't tried unlocking it, but tried a different PCM P59 and it read and test wrote fine.
I do get this message when I use "test" when setting up the device.
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
*'- Exception Text
System. UnauthorizedAccess Exception: Access to the port COM5' is denied.
at System.1O.Ports.InternalResources. WinlOError(Int32 errorCode, String str)
at System.IO.Ports.Serial Stream. ctor(String portName, Int32 baudRate, Parity parity
at System.lO.Ports.SerialPort.Open0
I
at PcmHacking.StandardPort.PcmHacking.IPort.OpenAsync(PortConfigurationcom
at PemHacking.OBDXProDevice.<Initialize>d_55.Move/NextO
Could it be I need to configure my com port differently. IIRC it's at 9600.
But it works fine when I read entire or test write.
User avatar
charlay86
Posts: 584
Joined: Thu Sep 17, 2009 2:00 pm
cars: VT S1 SS (L67)
Location: Perth, WA

Re: PCM Hammer Release 021

Post by charlay86 »

I wonder if it is related to the typo "PemHacking.OBDXProDevice" ?
User avatar
Tazzi
Posts: 3428
Joined: Thu May 17, 2012 8:53 pm
cars: VE SS Ute
Location: WA
Contact:

Re: PCM Hammer Release 021

Post by Tazzi »

a1953mdl wrote:Thank you.
Evidentially it is locked. I haven't tried unlocking it, but tried a different PCM P59 and it read and test wrote fine.
I do get this message when I use "test" when setting up the device.
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
*'- Exception Text
System. UnauthorizedAccess Exception: Access to the port COM5' is denied.
at System.1O.Ports.InternalResources. WinlOError(Int32 errorCode, String str)
at System.IO.Ports.Serial Stream. ctor(String portName, Int32 baudRate, Parity parity
at System.lO.Ports.SerialPort.Open0
I
at PcmHacking.StandardPort.PcmHacking.IPort.OpenAsync(PortConfigurationcom
at PemHacking.OBDXProDevice.<Initialize>d_55.Move/NextO
Could it be I need to configure my com port differently. IIRC it's at 9600.
But it works fine when I read entire or test write.
Completely disconnect the OBDX Pro VT device so its powered down, then reconnect to the PC, and then try connect. See if that helps!

Iv noticed in newer versions of PCMHammer that the re-initialize seems to now fail, something in an update of the app has killed its ability to successfully reinitialize.
Your Local Aussie Reverse Engineer
Contact for Software/Hardware development and Reverse Engineering
Site:https://www.envyouscustoms.com
Mob:+61406 140 726
Image
User avatar
antus
Site Admin
Posts: 8250
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 Release 021

Post by antus »

There is no mention of pemhammer in the pcmhammer 021 source code. Is this an edit/error directly just in the post in this forum, or some kind of hacked up pcmhammer you're running @a1953mdl?
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
a1953mdl
Posts: 7
Joined: Sat Apr 17, 2021 11:45 am

Re: PCM Hammer Release 021

Post by a1953mdl »

It's a mistake on my re-typing of the error message. Good proof reading there.
a1953mdl
Posts: 7
Joined: Sat Apr 17, 2021 11:45 am

Re: PCM Hammer Release 021

Post by a1953mdl »

I disconnected the PCM and also rebooted the computer. Reconnected and retried and it failed and I also got the error message when testing the device. I have attached the debug log, but please note this time I have connected to a P04 I want to clone.
Anyway. I still get the error message when I want to test the device after choosing it. I also noticed that it fails a BCC query? Then finally it wont read this PCM (P04) as it fails to unlock also. This is not a tuner locked PCM.
I did get it to read a P59 yesterday but had the error message when testing .
I hope changing to a P04 didn't confuse this too much.
Thoughts?
Should I change this to it's own thread?
Lee
If the P04 change is a problem, I can retry with the P59 I have read.
User avatar
antus
Site Admin
Posts: 8250
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 Release 021

Post by antus »

Sorry, P04 is not supported by pcmhammer.
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
Vampyre
Posts: 261
Joined: Wed Dec 06, 2017 1:02 pm
cars: grand am, trans am

Re: PCM Hammer Release 021

Post by Vampyre »

i got a bunch of guys i know that have cobalts and g5s
User avatar
Tazzi
Posts: 3428
Joined: Thu May 17, 2012 8:53 pm
cars: VE SS Ute
Location: WA
Contact:

Re: PCM Hammer Release 021

Post by Tazzi »

I am going through pcmhammer, trying to sort out this reinitialize issue, have fixed by changing a couple delays and a clear buffer.. seems to have resolved it.

Have test on VT's and GT's, both reinitialize correctly now. Will commit onto my Tazzi/OBDX fork. I "think" I merged the master into my branch.. so all I have to do is now commit my changes to my branch.. assuming that doesnt have some weird conflict, Ill do a pull so this can be put into the next release.
Your Local Aussie Reverse Engineer
Contact for Software/Hardware development and Reverse Engineering
Site:https://www.envyouscustoms.com
Mob:+61406 140 726
Image
spyder09
Posts: 76
Joined: Thu Apr 21, 2022 3:50 am
cars: saturn ion redline
hhr ss

Re: PCM Hammer Release 021

Post by spyder09 »

are we able to add OS numbers to the program easily yet? 12598284 will not read p12.

[07:43:12:071] PCM Hammer 021.2
[07:43:12:086] Wednesday, November 09 2022 @07:43:12:08
[07:43:12:092] Initializing OBDX Pro on COM5
[07:43:12:399] Unable to retrieve start.txt from network: HTTP NotFound.
[07:43:12:399] Unable to retrieve credits.html from network: HTTP NotFound.
[07:43:12:399] Unable to retrieve help.html from network: HTTP NotFound.
[07:43:12:510] Loaded start.txt from cache.
[07:43:12:511] Loaded credits.html from cache.
[07:43:12:513] Loaded help.html from cache.
[07:43:12:514] Thanks for using PCM Hammer.
[07:43:12:865] Device Found: OBDX Pro VT
[07:43:12:873] Switched to DVI protocol
[07:43:12:901] XPro: 32 0C 03 4F 42 44 58 20 50 72 6F 20 56 54 76
[07:43:12:904] XPro: 32 03 01 00 66 63
[07:43:12:905] Firmware version: v1.02
[07:43:12:908] XPro: 32 03 00 01 2D 9C
[07:43:12:909] Hardware version: v3.01
[07:43:12:912] XPro: 32 0D 04 06 6C FF 55 49 48 87 48 87 18 53 25 7F
[07:43:12:915] Unique Serial: 066CFF554948874887185325
[07:43:12:923] XPro: 41 02 01 01 BA
[07:43:12:925] OBD Protocol Set to VPW
[07:43:12:932] XPro: 43 03 00 F0 01 C8
[07:43:12:933] Filter set and enabled
[07:43:12:938] XPro: 41 02 02 01 B9
[07:43:12:939] Network enabled
[07:43:12:941] Device Successfully Initialized and Ready
[07:43:15:585] XPro: 20 01 00 DE
[07:43:15:588] TX: 6C 10 F0 3C 01
[07:43:15:617] XPro: 20 01 00 DE
[07:43:15:619] TX: 6C 10 F0 3C 02
[07:43:15:654] XPro: 20 01 00 DE
[07:43:15:655] TX: 6C 10 F0 3C 03
[07:43:15:687] VIN: 1G8AY12PX5Z125081
[07:43:15:705] XPro: 20 01 00 DE
[07:43:15:706] TX: 6C 10 F0 3C 0A
[07:43:15:738] OS ID: 12598284
[07:43:15:748] Hardware Type: P01_P59
[07:43:15:763] XPro: 20 01 00 DE
[07:43:15:763] TX: 6C 10 F0 3C 08
[07:43:15:785] Calibration ID: 12596924
[07:43:15:801] XPro: 20 01 00 DE
[07:43:15:803] TX: 6C 10 F0 3C 04
[07:43:15:822] Received an unexpected response. Attempt #1, status Truncated.
[07:43:16:322] Timeout.. no data present A
[07:43:16:325] Sending 'test device present' notification.
[07:43:16:339] XPro: 20 01 00 DE
[07:43:16:339] TX: 8C FE F0 3F
[07:43:16:840] Timeout.. no data present A
[07:43:16:841] Sending 'test device present' notification.
[07:43:16:846] XPro: 20 01 00 DE
[07:43:16:847] TX: 8C FE F0 3F
[07:43:17:348] Timeout.. no data present A
[07:43:17:348] Sending 'test device present' notification.
[07:43:17:355] XPro: 20 01 00 DE
[07:43:17:356] TX: 8C FE F0 3F
[07:43:17:856] Timeout.. no data present A
[07:43:17:857] Sending 'test device present' notification.
[07:43:17:863] XPro: 20 01 00 DE
[07:43:17:863] TX: 8C FE F0 3F
[07:43:18:364] Timeout.. no data present A
[07:43:18:365] Receive timed out. Attempt #6, Timeout #5.
[07:43:18:371] XPro: 20 01 00 DE
[07:43:18:372] TX: 6C 10 F0 3C 04
[07:43:18:396] Received an unexpected response. Attempt #1, status Truncated.
[07:43:18:896] Timeout.. no data present A
[07:43:18:901] Sending 'test device present' notification.
[07:43:18:914] XPro: 20 01 00 DE
[07:43:18:916] TX: 8C FE F0 3F
[07:43:19:417] Timeout.. no data present A
[07:43:19:419] Sending 'test device present' notification.
[07:43:19:425] XPro: 20 01 00 DE
[07:43:19:425] TX: 8C FE F0 3F
[07:43:19:926] Timeout.. no data present A
[07:43:19:926] Sending 'test device present' notification.
[07:43:19:932] XPro: 20 01 00 DE
[07:43:19:933] TX: 8C FE F0 3F
[07:43:20:434] Timeout.. no data present A
[07:43:20:434] Sending 'test device present' notification.
[07:43:20:441] XPro: 20 01 00 DE
[07:43:20:441] TX: 8C FE F0 3F
[07:43:20:942] Timeout.. no data present A
[07:43:20:943] Receive timed out. Attempt #6, Timeout #5.
[07:43:20:943] Hardware ID query failed: Error
[07:43:20:960] XPro: 20 01 00 DE
[07:43:20:961] TX: 6C 10 F0 3C 05
[07:43:20:990] XPro: 20 01 00 DE
[07:43:20:990] TX: 6C 10 F0 3C 06
[07:43:21:028] XPro: 20 01 00 DE
[07:43:21:029] TX: 6C 10 F0 3C 07
[07:43:21:066] Serial Number: 4268KG00B
[07:43:21:083] XPro: 20 01 00 DE
[07:43:21:084] TX: 6C 10 F0 3C 14
[07:43:21:110] Broad Cast Code: YKXC
[07:43:21:122] XPro: 20 01 00 DE
[07:43:21:124] TX: 6C 10 F0 3C A0
[07:43:21:144] MEC: 0


thank you!
Post Reply