Hammer not reading ECU
Hammer not reading ECU
G'day guys, i have an ecu with O/S 9381344 and i can't get it to read with PCM hammer. Ls droid reads it that's how i got the O/S number. Any ideas?
- antus
- Site Admin
- Posts: 8259
- 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: Hammer not reading ECU
Either post a debug log so we have something to look at, or use lsdroid.
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
Re: Hammer not reading ECU
This is what i got on the debug log after putting the o/s number in manually
[03:41:20:387] PCM Hammer 021
[03:41:20:387] Sunday, July 30 2023 @03:41:20:38
[03:41:20:389] Initializing J2534 Device
[03:41:20:390] Loaded DLL
[03:41:22:341] Connected to the device.
[03:41:22:341] Battery Voltage is: 13.671
[03:41:22:341] Protocol Set
[03:41:22:351] Device initialization complete.
[03:41:38:504] Will save to C:\Users\HP\Desktop\Car stuff\Ls1\OS, XDF and bin\Matts.bin
[03:41:41:782] Querying operating system of current PCM.
[03:41:41:793] TX: 6C 10 F0 3C 0A
[03:41:43:810] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[03:41:43:812] Sending 'test device present' notification.
[03:41:43:812] TX: 8C FE F0 3F
[03:41:45:818] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[03:41:45:818] Sending 'test device present' notification.
[03:41:45:818] TX: 8C FE F0 3F
[03:41:47:824] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[03:41:47:824] Sending 'test device present' notification.
[03:41:47:824] TX: 8C FE F0 3F
[03:41:49:831] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[03:41:49:831] Sending 'test device present' notification.
[03:41:49:831] TX: 8C FE F0 3F
[03:41:51:837] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[03:41:51:837] Receive timed out. Attempt #5, Timeout #5.
[03:41:51:837] TX: 6C 10 F0 3C 0A
[03:41:53:843] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[03:41:53:843] Sending 'test device present' notification.
[03:41:53:843] TX: 8C FE F0 3F
[03:41:55:851] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[03:41:55:851] Sending 'test device present' notification.
[03:41:55:851] TX: 8C FE F0 3F
[03:41:57:859] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[03:41:57:859] Sending 'test device present' notification.
[03:41:57:859] TX: 8C FE F0 3F
[03:41:59:864] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[03:41:59:864] Sending 'test device present' notification.
[03:41:59:864] TX: 8C FE F0 3F
[03:42:01:870] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[03:42:01:870] Receive timed out. Attempt #5, Timeout #5.
[03:42:01:870] Operating system query failed, will retry: Error
[03:42:01:870] J2534 setting VPW 4X
[03:42:01:878] TX: 6C 10 F0 20
[03:42:01:878] J2534 setting VPW 1X
[03:42:01:878] TX: 6C 10 F0 20
[03:42:01:878] TX: 6C 10 F0 3C 0A
[03:42:03:893] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[03:42:03:893] Sending 'test device present' notification.
[03:42:03:893] TX: 8C FE F0 3F
[03:42:05:898] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[03:42:05:898] Sending 'test device present' notification.
[03:42:05:898] TX: 8C FE F0 3F
[03:42:07:905] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[03:42:07:905] Sending 'test device present' notification.
[03:42:07:905] TX: 8C FE F0 3F
[03:42:09:911] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[03:42:09:911] Sending 'test device present' notification.
[03:42:09:911] TX: 8C FE F0 3F
[03:42:11:918] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[03:42:11:918] Receive timed out. Attempt #5, Timeout #5.
[03:42:11:918] TX: 6C 10 F0 3C 0A
[03:42:13:917] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[03:42:13:917] Sending 'test device present' notification.
[03:42:13:917] TX: 8C FE F0 3F
[03:42:15:923] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[03:42:15:923] Sending 'test device present' notification.
[03:42:15:923] TX: 8C FE F0 3F
[03:42:17:929] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[03:42:17:929] Sending 'test device present' notification.
[03:42:17:929] TX: 8C FE F0 3F
[03:42:19:935] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[03:42:19:935] Sending 'test device present' notification.
[03:42:19:935] TX: 8C FE F0 3F
[03:42:21:941] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[03:42:21:941] Receive timed out. Attempt #5, Timeout #5.
[03:42:21:949] Operating system query failed: Error
[03:42:21:949] Unable to get operating system ID. Will assume this can be unlocked with the default seed/key algorithm.
[03:42:21:949] Sending 'test device present' notification.
[03:42:21:949] TX: 8C FE F0 3F
[03:42:30:585] Sending 'test device present' notification.
[03:42:30:586] TX: 8C FE F0 3F
[03:42:30:595] Using OsID: 9381344
[03:42:30:597] Suppressing VPW chatter.
[03:42:30:597] TX: 6C FE F0 28 00
[03:42:30:597] Sending 'test device present' notification.
[03:42:30:597] TX: 8C FE F0 3F
[03:42:32:605] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[03:42:32:715] Sending seed request.
[03:42:32:715] TX: 6C 10 F0 27 01
[03:42:34:723] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[03:42:34:723] No response to seed request.
[03:42:34:723] Unlock was not successful.
[03:41:20:387] PCM Hammer 021
[03:41:20:387] Sunday, July 30 2023 @03:41:20:38
[03:41:20:389] Initializing J2534 Device
[03:41:20:390] Loaded DLL
[03:41:22:341] Connected to the device.
[03:41:22:341] Battery Voltage is: 13.671
[03:41:22:341] Protocol Set
[03:41:22:351] Device initialization complete.
[03:41:38:504] Will save to C:\Users\HP\Desktop\Car stuff\Ls1\OS, XDF and bin\Matts.bin
[03:41:41:782] Querying operating system of current PCM.
[03:41:41:793] TX: 6C 10 F0 3C 0A
[03:41:43:810] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[03:41:43:812] Sending 'test device present' notification.
[03:41:43:812] TX: 8C FE F0 3F
[03:41:45:818] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[03:41:45:818] Sending 'test device present' notification.
[03:41:45:818] TX: 8C FE F0 3F
[03:41:47:824] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[03:41:47:824] Sending 'test device present' notification.
[03:41:47:824] TX: 8C FE F0 3F
[03:41:49:831] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[03:41:49:831] Sending 'test device present' notification.
[03:41:49:831] TX: 8C FE F0 3F
[03:41:51:837] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[03:41:51:837] Receive timed out. Attempt #5, Timeout #5.
[03:41:51:837] TX: 6C 10 F0 3C 0A
[03:41:53:843] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[03:41:53:843] Sending 'test device present' notification.
[03:41:53:843] TX: 8C FE F0 3F
[03:41:55:851] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[03:41:55:851] Sending 'test device present' notification.
[03:41:55:851] TX: 8C FE F0 3F
[03:41:57:859] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[03:41:57:859] Sending 'test device present' notification.
[03:41:57:859] TX: 8C FE F0 3F
[03:41:59:864] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[03:41:59:864] Sending 'test device present' notification.
[03:41:59:864] TX: 8C FE F0 3F
[03:42:01:870] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[03:42:01:870] Receive timed out. Attempt #5, Timeout #5.
[03:42:01:870] Operating system query failed, will retry: Error
[03:42:01:870] J2534 setting VPW 4X
[03:42:01:878] TX: 6C 10 F0 20
[03:42:01:878] J2534 setting VPW 1X
[03:42:01:878] TX: 6C 10 F0 20
[03:42:01:878] TX: 6C 10 F0 3C 0A
[03:42:03:893] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[03:42:03:893] Sending 'test device present' notification.
[03:42:03:893] TX: 8C FE F0 3F
[03:42:05:898] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[03:42:05:898] Sending 'test device present' notification.
[03:42:05:898] TX: 8C FE F0 3F
[03:42:07:905] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[03:42:07:905] Sending 'test device present' notification.
[03:42:07:905] TX: 8C FE F0 3F
[03:42:09:911] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[03:42:09:911] Sending 'test device present' notification.
[03:42:09:911] TX: 8C FE F0 3F
[03:42:11:918] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[03:42:11:918] Receive timed out. Attempt #5, Timeout #5.
[03:42:11:918] TX: 6C 10 F0 3C 0A
[03:42:13:917] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[03:42:13:917] Sending 'test device present' notification.
[03:42:13:917] TX: 8C FE F0 3F
[03:42:15:923] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[03:42:15:923] Sending 'test device present' notification.
[03:42:15:923] TX: 8C FE F0 3F
[03:42:17:929] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[03:42:17:929] Sending 'test device present' notification.
[03:42:17:929] TX: 8C FE F0 3F
[03:42:19:935] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[03:42:19:935] Sending 'test device present' notification.
[03:42:19:935] TX: 8C FE F0 3F
[03:42:21:941] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[03:42:21:941] Receive timed out. Attempt #5, Timeout #5.
[03:42:21:949] Operating system query failed: Error
[03:42:21:949] Unable to get operating system ID. Will assume this can be unlocked with the default seed/key algorithm.
[03:42:21:949] Sending 'test device present' notification.
[03:42:21:949] TX: 8C FE F0 3F
[03:42:30:585] Sending 'test device present' notification.
[03:42:30:586] TX: 8C FE F0 3F
[03:42:30:595] Using OsID: 9381344
[03:42:30:597] Suppressing VPW chatter.
[03:42:30:597] TX: 6C FE F0 28 00
[03:42:30:597] Sending 'test device present' notification.
[03:42:30:597] TX: 8C FE F0 3F
[03:42:32:605] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[03:42:32:715] Sending seed request.
[03:42:32:715] TX: 6C 10 F0 27 01
[03:42:34:723] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[03:42:34:723] No response to seed request.
[03:42:34:723] Unlock was not successful.
- antus
- Site Admin
- Posts: 8259
- 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: Hammer not reading ECU
No comms with the car at all, there is no received data (RX) at all, only transmit (TX). Either ignition is not on or there is a problem with connection, interface or power. Depending what interface it is, it might not support VPW protocol.
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
Re: Hammer not reading ECU
Its a bench top setup with desktop power supply. LS droid reads it just fine but have no idea how to change things in it so trying Hammer. OBDX pro gt cableantus wrote:No comms with the car at all, there is no received data (RX) at all, only transmit (TX). Either ignition is not on or there is a problem with connection, interface or power. Depending what interface it is, it might not support VPW protocol.
- antus
- Site Admin
- Posts: 8259
- 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: Hammer not reading ECU
OBDX Pro GT should work fine either with its J2534 driver or with native XPro settings and the right com port selected. How old is your J2534 driver? Maybe it needs an update. I know lsdroid uses the native option to talk to it. Do you have lsdroid open or is it interfering with the interface somehow?
As for changing things both tools read and write bin files and do not edit the file. You need tunerpro + the right XDF, or universal patcher for that.
As for changing things both tools read and write bin files and do not edit the file. You need tunerpro + the right XDF, or universal patcher for that.
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
Re: Hammer not reading ECU
Pcmhammer handles the mask/filters in j2534 a bit obscure which doesn’t match how GM does it in their factory software, so the obdx pro GT doesn’t seem to work with its j2534 dll with pcmhammer until I get the next update out.
Use the OBDX Pro native option under the devices to connect for now.
Use the OBDX Pro native option under the devices to connect for now.
Your Local Aussie Reverse Engineer
Contact for Software/Hardware development and Reverse Engineering
Site:https://www.envyouscustoms.com
Mob:+61406 140 726
Contact for Software/Hardware development and Reverse Engineering
Site:https://www.envyouscustoms.com
Mob:+61406 140 726
Re: Hammer not reading ECU
I will update the driver and see what happens. No LS droid wasn't open. I watched a couple more videos last night so have a slightly better understanding of how it works now. Thanks mateantus wrote:OBDX Pro GT should work fine either with its J2534 driver or with native XPro settings and the right com port selected. How old is your J2534 driver? Maybe it needs an update. I know lsdroid uses the native option to talk to it. Do you have lsdroid open or is it interfering with the interface somehow?
As for changing things both tools read and write bin files and do not edit the file. You need tunerpro + the right XDF, or universal patcher for that.
Re: Hammer not reading ECU
Tazzi wrote:Pcmhammer handles the mask/filters in j2534 a bit obscure which doesn’t match how GM does it in their factory software, so the obdx pro GT doesn’t seem to work with its j2534 dll with pcmhammer until I get the next update out.
Use the OBDX Pro native option under the devices to connect for now.
I will give that a shot. Thanks mate
Re: Hammer not reading ECU
Well i tried those but no joy. I tried opening a bin in universal patcher and i get the following message. Anyone have any ideas what is going on there or should i start a new thread?
Error, frmTuner , line 0: C:\Users\HP\Desktop\Icons\explorer.ico
Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index
Importing tableseek...Seeking tables...
Importing TableSeek tables... [OK]
Importing DTC codes...DTC search: can't find DTC code table
[OK]
Error, frmTuner , line 0: C:\Users\HP\Desktop\Icons\explorer.ico
Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index
Importing tableseek...Seeking tables...
Importing TableSeek tables... [OK]
Importing DTC codes...DTC search: can't find DTC code table
[OK]