'411 Transients

[Jim Blackwood]

OK, did that. Found the updater and it did a firmware update and then confirmed that it was up to date.
Logger now appears to connect on J2534 (Device initiation complete) but not on com3 or BT. No improvement from PCH.

Jim

[kur4o]

Can you try pcm hammer with j-device selected, and post debug log.

You can test logger if it have actual communication in dtc tab when connected, test some random buttons.

[Jim Blackwood]

J2534 on PCH, log below. Finally getting somewhere I think:
--------------------------------------------------------------------
[09:55:02:408] PCM Hammer 021
[09:55:02:408] Monday, April 08 2024 @09:55:02:40
[09:55:02:408] Initializing J2534 Device
[09:55:02:408] Loaded DLL
[09:55:05:587] Connected to the device.
[09:55:05:591] Battery Voltage is: 12.685
[09:55:12:952] VIN: 1G1FP31S61N240478
[09:55:12:983] OS ID: 1253002
[09:55:12:983] Hardware Type: P01_P59
[09:55:13:014] Calibration ID: 12206911
[09:55:13:049] Hardware ID: 9386530
[09:55:13:120] Serial Number: 2EB2K9S62010
[09:55:13:158] Broad Cast Code: DJZX
[09:55:13:182] MEC: 0
[09:55:29:689] Will save to C:\Users\Jim\OneDrive\Desktop\MG\300 Iron Head\2024\PCM Hammer\C test.bin
[09:55:32:959] Querying operating system of current PCM.
[09:55:32:991] OSID: 1253002
[09:55:33:062] Unlock succeeded.
[09:55:33:081] Attempting switch to VPW 4x
[09:55:33:100] Module 0x10 (engine controller) has agreed to enter high-speed mode.
[09:55:37:674] Kernel upload 22% complete.
[09:55:38:114] Kernel upload 48% complete.
[09:55:38:579] Kernel upload 74% complete.
[09:55:39:012] Kernel upload 100% complete.
[09:55:39:267] Kernel Version: 01030501
[09:55:39:271] kernel uploaded to PCM succesfully. Requesting data...
[09:55:39:291] Flash chip: Intel 28F400B, 512kb
[09:55:39:295] Read complete.
[09:55:39:302] All read-request messages succeeded on the first try. You have an excellent connection to the PCM.
[09:55:39:302] We're not sure how much retrying is normal for a read operation on a 0kb PCM.
[09:55:39:316] Please help by sharing your results in the PCM Hammer thread at pcmhacking.net.
[09:55:39:322] Starting verification...
[09:55:39:334] Calculating CRCs from file.
[09:55:39:334] Initializing CRC algorithm on PCM, this will take a minute...
[09:55:39:382] Requesting CRCs from PCM.
[09:55:39:402] Range File CRC PCM CRC Verdict Purpose
[09:55:39:402] 060000-07FFFF not needed not needed n/a OperatingSystem
[09:55:39:413] 040000-05FFFF not needed not needed n/a OperatingSystem
[09:55:39:413] 020000-03FFFF not needed not needed n/a OperatingSystem
[09:55:39:433] 008000-01FFFF not needed not needed n/a Calibration
[09:55:39:433] 006000-007FFF not needed not needed n/a Parameter
[09:55:39:459] 004000-005FFF not needed not needed n/a Parameter
[09:55:39:470] 000000-003FFF not needed not needed n/a Boot
[09:55:39:480] The contents of the file match the contents of the PCM.
[09:55:39:502] Clearing trouble codes.
[09:55:40:603] Clearing trouble codes.
[09:55:41:687] Elapsed time 00:00:08.6197110
[09:55:41:698] Saving contents to C:\Users\Jim\OneDrive\Desktop\MG\300 Iron Head\2024\PCM Hammer\C test.bin
---------------------------------------------------------------------------------
This is the my first good read with the OBDX Pro GT.
----------------------------------------------------------------------------------

Results for serial connections to follow:
--------------------------------------------
Com3 usb:
[10:03:24:294] PCM Hammer 021
[10:03:24:310] Monday, April 08 2024 @10:03:24:31
[10:03:24:636] Thanks for using PCM Hammer.
[10:03:24:994] Device Found: OBDX Pro GT
[10:03:25:079] Device Successfully Initialized and Ready

Re-Initialized:
[10:05:38:875] PCM Hammer 021
[10:05:38:876] Monday, April 08 2024 @10:05:38:87
[10:05:39:539] Device Found: ATZ
[10:05:39:544] Failed to switch to DVI protocol
[10:05:39:546] Unable to reset DVI device.
[10:05:39:546] Unable to initialize OBDX Pro on COM3

Test results in Unhandled Exception, access to com3 denied.
[09:40:44:866] PCM Hammer 021
[09:40:44:882] Monday, April 08 2024 @09:40:44:88
[09:40:45:215] Thanks for using PCM Hammer.
[09:40:45:587] Device Found: OBDX Pro GT
[09:40:45:650] Device Successfully Initialized and Ready
[09:41:37:916] VIN query failed: Timeout

[09:52:29:082] PCM Hammer 021
[09:52:29:082] Monday, April 08 2024 @09:52:29:08
[09:52:29:757] Device Found: ATZ
[09:52:29:757] Failed to switch to DVI protocol
[09:52:29:757] Unable to reset DVI device.
[09:52:29:773] Unable to initialize OBDX Pro on COM3

BT:
[09:42:58:443] PCM Hammer 021
[09:42:58:457] Monday, April 08 2024 @09:42:58:45
[09:42:58:457] Unable to initialize OBDX Pro on COM4

BT:
[09:44:27:768] PCM Hammer 021
[09:44:27:768] Monday, April 08 2024 @09:44:27:76
[09:44:44:059] Unable to initialize OBDX Pro on COM5

Logger:

Connecting (VPW)...
J2534 client initializing...
Initializing J2534 Device
J2534 client: Device initialization complete.
Connected to the device, ID: 1
Battery Voltage is: 12.947
Timeout requesting OS
Versions: Firmware: 01.00, DLL: 1.4.8834.14573, Api: 04.04
Connected protocol: J1850VPW Speed: ISO14230
Removing all filters
Device initialization complete.
Filtering parameters by OS:
Start logging...
No profile configured
Disconnecting...J2534 Server Quits
Clearing functional address table (primary protocol)
Disconnecting primary protocol
[Done]
Connecting (VPW)...
J2534 client initializing...
Initializing J2534 Device
J2534 client: Device initialization complete.
Connected to the device, ID: 1
Battery Voltage is: 12.721
Versions: Firmware: 01.00, DLL: 1.4.8834.14573, Api: 04.04
Connected protocol: J1850VPW Speed: ISO14230
Removing all filters
Device initialization complete.
Device in use
Done

Attempting to connect to Logger with BT:

Connecting (VPW)...
J2534 client initializing...
Initializing J2534 Device
J2534 client: Device initialization fail.
Unable to connect to the device: 34
J2534 server: Device initialization failed
J2534 Server Quits


I do not have any parameters set for logging so I'm not getting any readings. yet.


Jim