PCM Hammer Release 012

[Jim Blackwood]

Right, sorry I'm a bit out of practice. So, the log:

[11:00:13:893] PCM Hammer 012
[11:00:13:893] ElmDevice initialization starting.
[11:00:14:392] Loaded start.txt from network.
[11:00:14:392] Loaded help.html from network.
[11:00:15:001] Loaded credits.html from network.
[11:00:18:987] TX:
[11:00:19:159] TX: AT Z
[11:00:18:987] Thanks for using PCM Hammer.
[11:00:20:159] AT Z ELM327 v1.3a
[11:00:20:159] TX: AT E0
[11:00:20:159] AT E0 OK
[11:00:20:175] TX: AT S0
[11:00:20:175] OK
[11:00:20:175] TX: AT RV
[11:00:20:190] Voltage: 13.4V
[11:00:20:190] TX: AT I
[11:00:20:190] Elm ID: ELM327 v1.3a
[11:00:20:190] Initializing PcmHacking.AllProDeviceImplementation
[11:00:20:190] TX: AT #1
[11:00:20:206] This is not an AllPro device.
[11:00:20:206] Determining whether PcmHacking.ScanToolDeviceImplementation is connected.
[11:00:20:206] TX: ST I
[11:00:20:206] ScanTool device ID: STN1155 v4.6.1
[11:00:20:222] TX: AT ST FF
[11:00:20:222] OK
[11:00:20:222] TX: AT AL
[11:00:20:222] OK
[11:00:20:237] TX: AT SP2
[11:00:20:237] OK
[11:00:20:237] TX: AT DP
[11:00:20:237] SAE J1850 VPW
[11:00:20:237] TX: AT AR
[11:00:20:253] OK
[11:00:20:253] TX: AT AT0
[11:00:20:253] OK
[11:00:20:269] TX: AT SR F0
[11:00:20:269] OK
[11:00:20:269] TX: AT H1
[11:00:20:284] OK
[11:00:20:284] TX: AT ST 20
[11:00:20:284] OK
[11:00:42:467] C:\Users\Jim\Documents\MG\First Files\MGBaGHN5UB240478G.bin
[11:00:52:486] Validating 512k file.
[11:00:52:486] Start End Stored Needed Verdict Segment Name
[11:00:52:486] 00000 7FFFD 3D37 3D37 Good Operating system
[11:00:52:501] 08002 13FFF 2D82 2D82 Good Engine calibration
[11:00:52:501] 14002 16DFF BF5D BF5D Good Engine diagnostics.
[11:00:52:517] 16E02 1BDFF 5D3A 5D3A Good Transmission calibration
[11:00:52:533] 1BE02 1C7FF 7BF9 7BF9 Good Transmission diagnostics
[11:00:52:533] 1C802 1E51F 6D0C 6D0C Good Fuel system
[11:00:52:548] 1E522 1EE9F DBD4 DBD4 Good System
[11:00:52:580] 1EEA2 1EF9F BD17 BD17 Good Speedometer
[11:00:52:595] Requesting operating system ID...
[11:00:52:611] Setting timeout for ReadProperty, 47 ms.
[11:00:52:611] TX: AT ST 0B
[11:00:52:702] OK
[11:00:52:811] TX: STPX H:6C10F0, R:1, D:3C0A
[11:00:53:234] Timeout during receive.
[11:00:53:234] Sending 'test device present' notification.
[11:00:53:234] TX: STPX H:8CFEF0, R:0, D:3F
[11:00:53:265] Empty response to STPX with data. That's OK
[11:00:53:593] Timeout during receive.
[11:00:53:593] Sending 'test device present' notification.
[11:00:53:593] TX: STPX H:8CFEF0, R:0, D:3F
[11:00:53:656] Empty response to STPX with data. That's OK
[11:00:53:968] Timeout during receive.
[11:00:53:968] Sending 'test device present' notification.
[11:00:53:968] TX: STPX H:8CFEF0, R:0, D:3F
[11:00:54:062] Empty response to STPX with data. That's OK
[11:00:54:359] Timeout during receive.
[11:00:54:359] Sending 'test device present' notification.
[11:00:54:359] TX: STPX H:8CFEF0, R:0, D:3F
[11:00:54:422] Empty response to STPX with data. That's OK
[11:00:54:734] Timeout during receive.
[11:00:54:734] Receive timed out. Attempt #5, Timeout #5.
[11:00:54:734] TX: STPX H:6C10F0, R:1, D:3C0A
[11:00:55:156] Timeout during receive.
[11:00:55:156] Sending 'test device present' notification.
[11:00:55:156] TX: STPX H:8CFEF0, R:0, D:3F
[11:00:55:187] Empty response to STPX with data. That's OK
[11:00:55:484] Timeout during receive.
[11:00:55:484] Sending 'test device present' notification.
[11:00:55:484] TX: STPX H:8CFEF0, R:0, D:3F
[11:00:55:500] Empty response to STPX with data. That's OK
[11:00:55:813] Timeout during receive.
[11:00:55:813] Sending 'test device present' notification.
[11:00:55:813] TX: STPX H:8CFEF0, R:0, D:3F
[11:00:55:891] Empty response to STPX with data. That's OK
[11:00:56:203] Timeout during receive.
[11:00:56:203] Sending 'test device present' notification.
[11:00:56:203] TX: STPX H:8CFEF0, R:0, D:3F
[11:00:56:219] Empty response to STPX with data. That's OK
[11:00:56:532] Timeout during receive.
[11:00:56:532] Receive timed out. Attempt #5, Timeout #5.
[11:00:56:532] Operating system request failed, checking for a live kernel...
[11:00:56:547] TX: STPX H:6C10F0, R:1, D:3D00
[11:00:56:969] Timeout during receive.
[11:00:57:079] TX: STPX H:6C10F0, R:1, D:3D00
[11:00:57:500] Timeout during receive.
[11:00:57:610] TX: STPX H:6C10F0, R:1, D:3D00
[11:00:57:985] Timeout during receive.
[11:00:58:095] TX: STPX H:6C10F0, R:1, D:3D00
[11:00:58:485] Timeout during receive.
[11:00:58:595] TX: STPX H:6C10F0, R:1, D:3D00
[11:00:58:970] Timeout during receive.
[11:00:59:079] Checking for recovery mode...
[11:00:59:094] TX: STPX H:6C10F0, R:1, D:62
[11:00:59:532] Timeout during receive.
[11:00:59:532] TX: STPX H:6C10F0, R:1, D:62
[11:00:59:970] Timeout during receive.
[11:00:59:970] TX: STPX H:6C10F0, R:1, D:62
[11:01:00:361] Timeout during receive.
[11:01:00:361] TX: STPX H:6C10F0, R:1, D:62
[11:01:00:767] Timeout during receive.
[11:01:00:767] TX: STPX H:6C10F0, R:1, D:62
[11:01:01:158] Timeout during receive.
[11:01:01:158] TX: STPX H:6C10F0, R:1, D:62
[11:01:01:595] Timeout during receive.
[11:01:01:595] TX: STPX H:6C10F0, R:1, D:62
[11:01:01:986] Timeout during receive.
[11:01:01:986] TX: STPX H:6C10F0, R:1, D:62
[11:01:02:408] Timeout during receive.
[11:01:02:408] TX: STPX H:6C10F0, R:1, D:62
[11:01:02:815] Timeout during receive.
[11:01:02:815] TX: STPX H:6C10F0, R:1, D:62
[11:01:03:237] Timeout during receive.
[11:01:03:237] PCM is not responding to OSID, kernel version, or recovery mode checks.
[11:01:03:252] Unlock may not work, but we'll try...
[11:01:03:267] Suppressing VPW chatter.
[11:01:03:267] TX: STPX H:6CFEF0, R:1, D:2800
[11:01:03:345] Sending 'test device present' notification.
[11:01:03:345] TX: STPX H:8CFEF0, R:0, D:3F
[11:01:03:361] Empty response to STPX with data. That's OK
[11:01:03:361] Sending seed request.
[11:01:03:361] TX: STPX H:6C10F0, R:1, D:2701
[11:01:03:768] Timeout during receive.
[11:01:03:768] No response to seed request.
[11:01:03:768] Unlock was not successful.


This is with 4x unchecked. I tested it with a 2nd PCM with the same results. Only other program running is Firefox.
Let me ask this though. If the signal wire from the OBDLink to the PCM was open would it return the validations on the 512K file?

I'm going to reboot the laptop and try again with my scope modules unplugged as I overlooked that but I don't expect that to be the problem.

Jim

Same result with the reboot.

[Gampy]

No apologies necessary ...

Disabling 4x communication is not going to affect the OBDLink LX, The OBDLink LX is a 1x device.
That comment was made for the Allpro device I believe you have. I probably should not of mentioned it at this point ...

On with it,

The Tool is responding, the Pcm is not ...

Basically this is where PcmHammer first communicates with the Pcm,

[11:00:52:595] Requesting operating system ID...

everything prior is between PcmHammer Application or Tool.

The actual command sent for the above Request,

[11:00:52:811] TX: STPX H:6C10F0, R:1, D:3C0A

I'm a bit perplexed, this is basically the same tool I use, the chip version is a bit different, the OBDLink LX uses a STN1155, I'm using a STN1110.

Are you familiar with sending AT commands to the tool from a Terminal Program (Like PuTTY)??
If you are, send the following one at a time.

AT Z
AT E1
AT S0
AT AL
AT SP2
AT AR
AT AT0
AT SRF0
AT H1
AT ST20
AT SH6C10F0
3C0A

The last line should return the OsID ... looking something like: 6CF0107C0Axxxxxxxx??
The 8 x's are the OsID in hex ...
I would be interested in seeing the results.

[edit]
Example of the above Terminal steps with OsID: 12585950

PuTTY OsID.png (8.56 KiB) Viewed 3748 times

6CF0107C0A 00C00BDE E3
00C00BDE hex = 12585950 decimal.

[Jim Blackwood]

I'm perfectly willing to do this, provided I can figure out how. My familiarity with terminal programs is kinda seldom and minimal.
I downloaded PuTTY but don't know how to set it up.
I downloaded cmdr and same problem. I know not much is required, it just takes the right steps. I use a terminal program any time I use the milling machine in my shop but that is just as an operator.

I installed and ran these commands on my old laptop back when I was trying to get my new AllPro cable to work. Don't remember which terminal program I ended up using. Never did get the AllPro to make the connection even with the new laptop, though Scott Costanza tried it and said it was fine. Just a little background here. The OBDLink LX worked so I've been using that but I took some time off tuning to construct a desktop simulator and get a laptop O'scope working. Replaced a couple of sensors and the engine fires off now so I wanted to enrichen the cold start compensation. But now I've lost communication with the ECM.

So, since I can't remember how I set up Terminal is there a chance you could help out on that?

Jim

[ironduke]

I'm perfectly willing to do this, provided I can figure out how. My familiarity with terminal programs is kinda seldom and minimal.
I downloaded PuTTY but don't know how to set it up.
I downloaded cmdr and same problem. I know not much is required, it just takes the right steps. I use a terminal program any time I use the milling machine in my shop but that is just as an operator.

I installed and ran these commands on my old laptop back when I was trying to get my new AllPro cable to work. Don't remember which terminal program I ended up using. Never did get the AllPro to make the connection even with the new laptop, though Scott Costanza tried it and said it was fine. Just a little background here. The OBDLink LX worked so I've been using that but I took some time off tuning to construct a desktop simulator and get a laptop O'scope working. Replaced a couple of sensors and the engine fires off now so I wanted to enrichen the cold start compensation. But now I've lost communication with the ECM.

So, since I can't remember how I set up Terminal is there a chance you could help out on that?

Jim

Can't help much with PCM hammer but I would suggest termite for serial port software if your looking for something easy.. https://www.compuphase.com/software_termite.htm
Once it's running and you go into settings and try to pick com port it'll show you what's installed/available to select.. I don't know OBDLink LX baud rate but I'd guess 115,200 to start..

Set append cr/lf and leave everything else alone.. close settings and you should be connected if you have the com port and baud rate correct.. Try typing ATI press enter and it should print the identification string of the device.. or type ATZ and it should reset and then print the ID of the device.. If you get that far then try the rest of the commands already suggested..

[Gampy]

PuTTY is light.
PuTTY is simple.
PuTTY is non-intrusive.

That is why I recommend it.

The first time is the hardest, that is setting it up ... though super simple!

First you need to know what COM port number the Tool is using ... In device manager it's under Ports.

Open PuTTY
Don't worry about anything on the left ... Just the following on the right!
Connection Type: Serial
Serial Line: COM? <- Adjust this to the COM port of your Tool.
Speed: 115200
Saved Sessions: Type a name to save the above configuration under if you want to save it, then Select: Save

That's it!

Select Open ... You're in.

Mr. Jim, Are you doing this in Vehicle??
Or on a bench harness following this Schematic??

[Jim Blackwood]

ATI
ATI
?

>ATZ
ATZ


ELM327 v1.3a

>AT Z
AT Z


ELM327 v1.3a

>AT E1
AT E1
OK

>AT SO
AT SO
?

>AT S0
AT S0
OK

>AT AL
AT AL
OK

>AT SP2
AT SP2
OK

>AT ART
AT ART
?

>AT ART
AT ART
?

>AT ART
AT ART
?

>AT ART
AT ART
?

>AT AR
AT AR
OK

>AT AT0
AT AT0
OK

>AT SRF0
AT SRF0
OK

>AT H1
AT H1
OK

>AT ST20
AT ST20
OK

>AT SH6C10F0
AT SH6C10F0
OK

>3C0A
3C0A
NO DATA

>

Jim

[Gampy]

Ok, Now we know it's not PcmHammer, or PC <-> Tool communication.

That pretty much leaves it to a wiring issue or a Pcm issue.

Is this in Vehicle??
Or on a bench harness following this Schematic??

I know you're doing something with a MGB, hopefully LS swapping it ...
We used to have a 54 TF.

[Jim Blackwood]

OK, that's all good news, and I have more of the same. Really something I should have done to start with, live and learn. The problem is with the simulator only and is almost definitely a case of switched wires.

I went out and gave the connection to the car another shot. Good news is, I did a config rewrite with the OBDLink LS and it was successful. Then I grabbed the AllPro cable which I've never been able to get work and got a good connection and a successful test write. The end message said it was a great connection.

So, a better outcome than I hoped for. I'll have to find the problem with the simulator wiring but that should be really simple now that I know where to look.

Thanks for all the help,

Jim

[Gampy]

Awesome great news!

Question, Did you have to disable 4x communication with the Allpro??

[Jim Blackwood]

Quick update. Two reasons why I did not have comm with the simulator, both related to replacing theOBD-II connector with one from a donor vehicle. First, when wiring this plug the purple wire goes to the green wire. Not exactly intuitive and I had it green to green. Secondly there may have been some corrosion on the contacts as it still didn't work. Nothing I could see but after continuity checks turned nothing up I repeatedly plugged and unplugged both the Allpro cable and the OBDLink into the connector and was then able to write to the ECU with either device.

Jim