I have a 2000 Astro RWD, just went to 235/75/15's and 3.73 gear from a 3.42. Speedo is off 5 mph at 55 and I would like to correct it. After reading through a few threads here on that, I bought an OBDlink LX and downloaded PCM Hammer. Got the OBDLink LX and PCM Hammer talking to each other, but I am unable to get the PCM to unlock and be read by PCM Hammer.
Here's a quick snapshot of what PCM Hammer is telling me about the attempts to unlock it:
[04:56:04:370] PCM Hammer 021
[04:56:04:370] Friday, December 06 2024 @04:56:04:37
[04:56:05:461] Voltage: 12.0V
[04:56:05:508] Elm ID: ELM327 v1.4b
[04:56:05:524] ScanTool device ID: STN1155 v5.6.19
[04:56:16:133] Will save to C:\Users\cvn\Desktop\astropcm.bin
[04:56:26:242] Querying operating system of current PCM.
[04:56:26:398] OSID: 16265175
[04:56:26:570] The PCM didn't accept the unlock key value
[04:56:29:663] Unable to process unlock response.
[04:56:29:663] Unlock was not successful.
The full debug log:
04:56:04:370] PCM Hammer 021
[04:56:04:370] Friday, December 06 2024 @04:56:04:37
[04:56:04:370] ElmDevice initialization starting.
[04:56:04:555] TX:
[04:56:04:571] TX: AT Z
[04:56:05:414] ELM327 v1.4b
[04:56:05:414] TX: AT E0
[04:56:05:446] AT E0 OK
[04:56:05:446] TX: AT S0
[04:56:05:446] OK
[04:56:05:446] TX: AT RV
[04:56:05:461] Voltage: 12.0V
[04:56:05:461] TX: AT I
[04:56:05:508] Elm ID: ELM327 v1.4b
[04:56:05:508] Initializing PcmHacking.AllProDeviceImplementation
[04:56:05:508] TX: AT #1
[04:56:05:524] This is not an AllPro device.
[04:56:05:524] Determining whether PcmHacking.ScanToolDeviceImplementation is connected.
[04:56:05:524] TX: ST I
[04:56:05:524] ScanTool device ID: STN1155 v5.6.19
[04:56:05:524] TX: STPTO 3000
[04:56:05:539] OK
[04:56:05:539] TX: AT AL
[04:56:05:539] OK
[04:56:05:539] TX: AT SP2
[04:56:05:539] OK
[04:56:05:555] TX: AT DP
[04:56:05:555] SAE J1850 VPW
[04:56:05:555] TX: AT AR
[04:56:05:555] OK
[04:56:05:555] TX: AT AT0
[04:56:05:570] OK
[04:56:05:570] TX: AT SR F0
[04:56:05:570] OK
[04:56:05:570] TX: AT H1
[04:56:05:602] OK
[04:56:05:602] TX: AT ST 20
[04:56:05:617] OK
[04:56:16:133] Will save to C:\Users\cvn\Desktop\astropcm.bin
[04:56:26:242] Querying operating system of current PCM.
[04:56:26:242] TX: STPX H:6C10F0, R:1, D:3C0A
[04:56:26:398] RX: 6C F0 10 7C 0A 00 F8 2F D7
[04:56:26:398] OSID: 16265175
[04:56:26:398] Suppressing VPW chatter.
[04:56:26:398] TX: STPX H:6CFEF0, R:1, D:2800
[04:56:26:445] RX: 6C F0 40 68 00
[04:56:26:445] Sending 'test device present' notification.
[04:56:26:445] Setting timeout for Minimum, 0 ms.
[04:56:26:445] TX: STPTO 0
[04:56:26:461] OK
[04:56:26:461] TX: STPX H:8CFEF0, R:0, D:3F
[04:56:26:477] Empty response to STPX with data. OK.
[04:56:26:477] Setting timeout for ReadProperty, 25 ms.
[04:56:26:477] TX: STPTO 25
[04:56:26:477] OK
[04:56:26:477] Ignoring chatter: 6C F0 40 68 00
[04:56:26:477] Sending seed request.
[04:56:26:477] TX: STPX H:6C10F0, R:1, D:2701
[04:56:26:523] RX: 6C F0 10 67 01 5E 5E
[04:56:26:523] Parsing seed value.
[04:56:26:523] Sending unlock request (5E5E, 34EF)
[04:56:26:523] TX: STPX H:6C10F0, R:1, D:270234EF
[04:56:26:570] RX: 6C F0 10 67 02 35
[04:56:26:570] The PCM didn't accept the unlock key value
[04:56:27:601] Timeout during receive.
[04:56:27:601] No response to unlock request. Attempt #2
[04:56:28:632] Timeout during receive.
[04:56:28:632] No response to unlock request. Attempt #3
[04:56:29:663] Timeout during receive.
[04:56:29:663] No response to unlock request. Attempt #4
[04:56:29:663] Unable to process unlock response.
[04:56:29:663] Unlock was not successful.
Yes, my voltage is low. That's a brand new battery I bought today too, it's just cold as shit outside right now. I'll try again tomorrow with the charger hooked up to it, I know low voltage can cause issues during write and reflashing and such. But I don't have high hopes for it being related to low voltage, seems more like another issue. Just my luck, my PCM is probably too old or just not compatible. I registered over at the pcmhacking forum, but my account has not been approved so I can't post there yet. Figured I'd ask here and see if you guys have any ideas why the PCM is not able to be read by PCM Hammer.
If I can't get this working in the next day or two I will be ready to throw in the towel and just pay someone to program it, if that's even an option. I am running out of time with my project, completely swamped with a million other things that need to get done and just don't have time to figure out this tech stuff. Don't live in a big city so there's noone local that could do that kind of thing. Suggestions on some place I can send the PCM away to have this programming done, if I can't get it working this weekend?
Here's a quick snapshot of what PCM Hammer is telling me about the attempts to unlock it:
[04:56:04:370] PCM Hammer 021
[04:56:04:370] Friday, December 06 2024 @04:56:04:37
[04:56:05:461] Voltage: 12.0V
[04:56:05:508] Elm ID: ELM327 v1.4b
[04:56:05:524] ScanTool device ID: STN1155 v5.6.19
[04:56:16:133] Will save to C:\Users\cvn\Desktop\astropcm.bin
[04:56:26:242] Querying operating system of current PCM.
[04:56:26:398] OSID: 16265175
[04:56:26:570] The PCM didn't accept the unlock key value
[04:56:29:663] Unable to process unlock response.
[04:56:29:663] Unlock was not successful.
The full debug log:
04:56:04:370] PCM Hammer 021
[04:56:04:370] Friday, December 06 2024 @04:56:04:37
[04:56:04:370] ElmDevice initialization starting.
[04:56:04:555] TX:
[04:56:04:571] TX: AT Z
[04:56:05:414] ELM327 v1.4b
[04:56:05:414] TX: AT E0
[04:56:05:446] AT E0 OK
[04:56:05:446] TX: AT S0
[04:56:05:446] OK
[04:56:05:446] TX: AT RV
[04:56:05:461] Voltage: 12.0V
[04:56:05:461] TX: AT I
[04:56:05:508] Elm ID: ELM327 v1.4b
[04:56:05:508] Initializing PcmHacking.AllProDeviceImplementation
[04:56:05:508] TX: AT #1
[04:56:05:524] This is not an AllPro device.
[04:56:05:524] Determining whether PcmHacking.ScanToolDeviceImplementation is connected.
[04:56:05:524] TX: ST I
[04:56:05:524] ScanTool device ID: STN1155 v5.6.19
[04:56:05:524] TX: STPTO 3000
[04:56:05:539] OK
[04:56:05:539] TX: AT AL
[04:56:05:539] OK
[04:56:05:539] TX: AT SP2
[04:56:05:539] OK
[04:56:05:555] TX: AT DP
[04:56:05:555] SAE J1850 VPW
[04:56:05:555] TX: AT AR
[04:56:05:555] OK
[04:56:05:555] TX: AT AT0
[04:56:05:570] OK
[04:56:05:570] TX: AT SR F0
[04:56:05:570] OK
[04:56:05:570] TX: AT H1
[04:56:05:602] OK
[04:56:05:602] TX: AT ST 20
[04:56:05:617] OK
[04:56:16:133] Will save to C:\Users\cvn\Desktop\astropcm.bin
[04:56:26:242] Querying operating system of current PCM.
[04:56:26:242] TX: STPX H:6C10F0, R:1, D:3C0A
[04:56:26:398] RX: 6C F0 10 7C 0A 00 F8 2F D7
[04:56:26:398] OSID: 16265175
[04:56:26:398] Suppressing VPW chatter.
[04:56:26:398] TX: STPX H:6CFEF0, R:1, D:2800
[04:56:26:445] RX: 6C F0 40 68 00
[04:56:26:445] Sending 'test device present' notification.
[04:56:26:445] Setting timeout for Minimum, 0 ms.
[04:56:26:445] TX: STPTO 0
[04:56:26:461] OK
[04:56:26:461] TX: STPX H:8CFEF0, R:0, D:3F
[04:56:26:477] Empty response to STPX with data. OK.
[04:56:26:477] Setting timeout for ReadProperty, 25 ms.
[04:56:26:477] TX: STPTO 25
[04:56:26:477] OK
[04:56:26:477] Ignoring chatter: 6C F0 40 68 00
[04:56:26:477] Sending seed request.
[04:56:26:477] TX: STPX H:6C10F0, R:1, D:2701
[04:56:26:523] RX: 6C F0 10 67 01 5E 5E
[04:56:26:523] Parsing seed value.
[04:56:26:523] Sending unlock request (5E5E, 34EF)
[04:56:26:523] TX: STPX H:6C10F0, R:1, D:270234EF
[04:56:26:570] RX: 6C F0 10 67 02 35
[04:56:26:570] The PCM didn't accept the unlock key value
[04:56:27:601] Timeout during receive.
[04:56:27:601] No response to unlock request. Attempt #2
[04:56:28:632] Timeout during receive.
[04:56:28:632] No response to unlock request. Attempt #3
[04:56:29:663] Timeout during receive.
[04:56:29:663] No response to unlock request. Attempt #4
[04:56:29:663] Unable to process unlock response.
[04:56:29:663] Unlock was not successful.
Yes, my voltage is low. That's a brand new battery I bought today too, it's just cold as shit outside right now. I'll try again tomorrow with the charger hooked up to it, I know low voltage can cause issues during write and reflashing and such. But I don't have high hopes for it being related to low voltage, seems more like another issue. Just my luck, my PCM is probably too old or just not compatible. I registered over at the pcmhacking forum, but my account has not been approved so I can't post there yet. Figured I'd ask here and see if you guys have any ideas why the PCM is not able to be read by PCM Hammer.
If I can't get this working in the next day or two I will be ready to throw in the towel and just pay someone to program it, if that's even an option. I am running out of time with my project, completely swamped with a million other things that need to get done and just don't have time to figure out this tech stuff. Don't live in a big city so there's noone local that could do that kind of thing. Suggestions on some place I can send the PCM away to have this programming done, if I can't get it working this weekend?