Hooking a charger is real bad ides, regulated filtered power supply is much better.
You need to select device as serial with comport.
Hooking a charger is real bad ides, regulated filtered power supply is much better.
You need to select device as serial with comport.
When I open PCH with the OBDX plugged in it tells me it found the OBDX on com3, serial port is selected, and it says the device is initialized and ready. However, Test doesn't work, access to com3 denied. Then it says it found ATZ but failed to switch to DVI protocol or reset DVI or initiate the OBDX. It's been a couple years since I did this and I can't remember what I'm doing wrong.
Jim
'71 MGB w/ 340 Buick/Eaton/'411 P01
Which obdx device do you have.
You can try to get latest drivers from their website, and upgrade firmware if there is any.
ANother test will be to get it working with universal patcher logger.
utiliies->logger->settings tab->select device->connect
The OBDXPro GT.
About the battery charger, I have a 12v battery in the simulator. I switch on the battery charger to charge it up. I can switch on either or both so it's easy to run on just the battery and charge it afterwards. I expected the battery to be a reasonably effective filter but apparently not.
I just downloaded and installed the software from the OBDXProGT page, seemed odd that there were about 4 or so install cycles but I went through the complete process. Tried to connect with both PCH and Universal Patcher, on com3 with a usb cable and then on com4 and com5 with bluetooth. No joy. PCH did say it found ATZ then failed to switch to DVI. UP just gave me a connection failed.
Jim
'71 MGB w/ 340 Buick/Eaton/'411 P01
Can you test with j2534 device selection, in patcher and hammer.
In logger it says "32534 client: Device initialization fail.
IN PCH if I say OK without running test it tells me an update for the OBDX Pro scantool is required so I went to the update download site and downloaded and installed every update that looked like it could be related to the GT then went back to PCH and got the exact same result. Trying Test brings up the same dialog which happens right after it loaded DLL. On com3 (usb) it fails to switch DVI, on com4 (BT) access to com4 is denied, on com5 it times out.
Incidentally, the laptop does not beep when the GT is plugged in, if that means anything. My desktop PC does though. Guess I could try the install there but it won't help me much on tuning the car. Though I suppose I could always bring in the ECM and put it on the simulator. Do my logging with HPT.
Jim
'71 MGB w/ 340 Buick/Eaton/'411 P01
The update might not have completed successfully.
Here is some other user with similar issue fix.
Well finally got it sorted. Firmware wasn't loading by clicking on the download even though it was telling me it was ready. Went into my computer/ program files and found it there so tried from there and it's working finally. Thanks everyone for your help and Tazzie you're a genius
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
'71 MGB w/ 340 Buick/Eaton/'411 P01
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.
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
'71 MGB w/ 340 Buick/Eaton/'411 P01
Posting Permissions
Reply With Quote
Bookmarks