PCMHammer P04

[ProfessWRX]

Hey everybody thanks for all of this work, I’m having an issue with pcm hammer not recognizing my pcm at all. I was able to get a script from kur4o on gearheadefi that read my pcm. It’s an 04 Monte Carlo and I’m using the OBDxpro vt. What can I gather for you in order to troubleshoot?

[MudDuck514]

Are you using the LATEST version that Gampy posted on 10-06?
If not, you may want to grab a copy.

Mike

[ProfessWRX]

Yes, I attached the script we used. I don't see any PCMHammer options to change to sort out the settings he used.

[10:24:30:621] PCM Hammer - Public AKernel TEST 824.0. (10/6/2023, 10:00 AM)
[10:24:30:629] Saturday, October 14 2023 @10:24:30:62
[10:24:30:633] Initializing J2534 Device
[10:24:30:665] Loaded DLL
[10:24:31:696] Connected to the device.
[10:24:31:727] Battery Voltage is: 11.898
[10:24:30:805] Loaded credits.html from network.
[10:24:30:805] Loaded start.txt from network.
[10:24:30:852] Loaded help.html from network.
[10:24:31:759] Protocol Set
[10:24:31:821] Device initialization complete.
[10:24:31:759] Thanks for using PCM Hammer.
[10:24:35:066] WARNING: This version uses the new Assembly Kernels, USE AT YOUR OWN RISK!
[10:24:41:382] Will save to C:\Users\ScottAnderson\Desktop\test.bin
[10:24:42:742] Querying operating system of current PCM.
[10:24:42:820] TX: 6C 10 F0 3C 0A
[10:24:45:910] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[10:24:45:913] Sending 'test device present' notification.

[antus]

Use the native OBD Xpro driver, not the J2534 for the XPro in PCMHammer. There is a known incompatibility with J2534 in the app. Tazzi has advised there will be fixes in a future version of PCMHammer, but for now it does work fine when using the native XPro support.

[ProfessWRX]

Use the native OBD Xpro driver, not the J2534 for the XPro in PCMHammer. There is a known incompatibility with J2534 in the app. Tazzi has advised there will be fixes in a future version of PCMHammer, but for now it does work fine when using the native XPro support.

You mean the serial port device? I'm getting an error trying to choose anything else.

edit: got it on another usb port, thanks! i see communication now

[MudDuck514]

[10:24:31:727] Battery Voltage is: 11.898

This COULD cause you problems down the road when the PCM tries either erasing, or writing to, flash memory!

Mike

[ProfessWRX]

[10:24:31:727] Battery Voltage is: 11.898

This COULD cause you problems down the road when the PCM tries either erasing, or writing to, flash memory!

Mike

Yeah I noticed it was getting low. When I started it was 12.7 or higher. Have to sit with the door open because it was 100 degrees out so after that long process the battery slowly dropped with the dome light on.

[Gampy]

Figure this might be a good time to post this again ...

Intel recommended programming voltage 12v +-5% = v11.4 -> v12.6.

I personally have tested outside this range, low is a concern, high not so much.

I run my bench at 13.5.

-Enjoy

[zack4200]

I tested a couple PCMs:
P08 Intel, XProVT, read & test write, both OK. have not tried a true write on the p08 yet.

P04 AMD, XProVT, read OK. Wrote the same file back as a clone write and obviously it skipped everything and succeeded. then did another clone write with a different file, which was successful as well. but now attempting to read the pcm fails every time, even after removing and restoring power to the PCM as suggested.

logs and BINs in the zip.

also possibly worth noting, Read Properties now returns:

Code: Select all

[08:19:21:565]  Calibration ID: 0
[08:19:21:589]  Hardware ID: 0
[08:19:21:664]  Serial Number: 
[08:19:21:700]  MEC: 0

debug log from reading properties:

Code: Select all

[08:19:13:115]  PCM Hammer - Public AKernel TEST 824.0. (10/6/2023, 1:00 PM)
[08:19:13:116]  Monday, October 16 2023 @08:19:13:11
[08:19:13:118]  Initializing OBDX Pro on COM6
[08:19:14:012]  Device Found: OBDX Pro VT
[08:19:14:180]  Switched to DVI protocol
[08:19:14:190]  XPro: 32 0C 03 4F 42 44 58 20 50 72 6F 20 56 54 76
[08:19:14:193]  XPro: 32 03 01 00 66 63
[08:19:14:195]  Firmware version: v1.02
[08:19:14:198]  XPro: 32 03 00 00 C8 02
[08:19:14:200]  Hardware version: v2.00
[08:19:14:204]  XPro: 32 0D 04 06 65 FF 50 53 52 86 66 87 16 40 17 7D
[08:19:14:206]  Unique Serial: 0665FF505352866687164017
[08:19:14:208]  XPro: 4A 04 00 00 05 CC E0
[08:19:14:210]  Voltage is: 13.63V
[08:19:14:213]  XPro: 41 02 01 01 BA
[08:19:14:215]  OBD Protocol Set to VPW
[08:19:14:217]  XPro: 43 03 00 F0 01 C8
[08:19:14:219]  Filter set and enabled
[08:19:14:221]  XPro: 41 02 02 01 B9
[08:19:14:223]  Network enabled
[08:19:14:225]  Device Successfully Initialized and Ready
[08:19:21:432]  XPro: 20 01 00 DE
[08:19:21:432]  TX: 6C 10 F0 3C 01
[08:19:21:452]  RX: 6C F0 10 7C 01 00 00 00 00 00 00
[08:19:21:459]  XPro: 20 01 00 DE
[08:19:21:459]  TX: 6C 10 F0 3C 02
[08:19:21:478]  RX: 6C F0 10 7C 02 00 00 00 00 00 00
[08:19:21:486]  XPro: 20 01 00 DE
[08:19:21:489]  TX: 6C 10 F0 3C 03
[08:19:21:503]  RX: 6C F0 10 7C 03 00 00 00 00 00 00
[08:19:21:503]  VIN: [08:19:21:512]  XPro: 20 01 00 DE
[08:19:21:513]  TX: 6C 10 F0 3C 0A
[08:19:21:525]  RX: 6C F0 10 7C 0A 00 C0 2D 5F
[08:19:21:525]  OS ID: 12594527
[08:19:21:527]  Hardware Type: P04
[08:19:21:529]  **********************************************
[08:19:21:530]  WARNING: P04 Support is still in development.
[08:19:21:532]  It may or may not read your P04 correctly.
[08:19:21:534]  There is currently no ETA for P04 Write.
[08:19:21:535]  **********************************************
[08:19:21:544]  XPro: 20 01 00 DE
[08:19:21:544]  TX: 6C 10 F0 3C 08
[08:19:21:564]  RX: 6C F0 10 7C 08 00 00 00 00
[08:19:21:565]  Calibration ID: 0
[08:19:21:576]  XPro: 20 01 00 DE
[08:19:21:576]  TX: 6C 10 F0 3C 04
[08:19:21:589]  RX: 6C F0 10 7C 04 00 00 00 00
[08:19:21:589]  Hardware ID: 0
[08:19:21:599]  XPro: 20 01 00 DE
[08:19:21:600]  TX: 6C 10 F0 3C 05
[08:19:21:613]  RX: 6C F0 10 7C 05 00 00 00 00
[08:19:21:620]  XPro: 20 01 00 DE
[08:19:21:623]  TX: 6C 10 F0 3C 06
[08:19:21:639]  RX: 6C F0 10 7C 06 00 00 00 00
[08:19:21:646]  XPro: 20 01 00 DE
[08:19:21:647]  TX: 6C 10 F0 3C 07
[08:19:21:663]  RX: 6C F0 10 7C 07 00 00 00 00
[08:19:21:664]  Serial Number: 
[08:19:21:682]  XPro: 20 01 00 DE
[08:19:21:682]  TX: 6C 10 F0 3C A0
[08:19:21:699]  RX: 6C F0 10 7C A0 00
[08:19:21:700]  MEC: 0

[antus]

Can you post the bin file you wrote to it? It looks like its missing a segment with identifiers. I'd be interesting to take a look. The PCM is answering, as its giving you what it thinks are its IDs. Its like it came from another tool that omitted that information. This PCM will be recoverable, but you might need some functionality to override the Identification which is not yet available.

If there are tools omitting this information on P04, we may need to add some additional checks beyond checksum. Come to think of it, I think tunercat cal format does not include this segment, if people are converting those cal files to bins and reposting them on the internet that could be the root cause. I dont know what other P04 tools do.