New PCM, is it dead?

[ProfessWRX]

I bought an ebay PCM with the same part number supposedly for the car. It looks like the calibration code on the sticker is for an impala ( I have a monte carlo)
Anyway, I can't get universal patcher to see anything on the bus. I can't get it to pull any trouble codes. Is the PCM dead or am I missing a step that I need to do before it will read the PCM through my car? I don't have a bench setup, just the car.

[antus]

Is this the same one as you are asking about here? viewtopic.php?f=4&t=8008&start=170#p124584 And so you have it talking now?

[ProfessWRX]

Is this the same one as you are asking about here? viewtopic.php?f=4&t=8008&start=170#p124584 And so you have it talking now?

This is a different one. I got it to connect the same way. It was able to read the VIN and change the VIN, then I did a full read, I did a test write and then I attempted a clone of the stock PCM. It failed to write and now it can't communicate again.

[ProfessWRX]

[03:48:29:116] VIN query failed: Timeout
[03:48:41:043] WARNING: This version uses the new Assembly Kernels, USE AT YOUR OWN RISK!
[03:48:48:083] C:\Users\ScottAnderson\Desktop\Tuning\L67\CarlSTOCK.bin
[03:48:48:090] Validating 512k file.
[03:48:48:106] Start End Stored Needed Verdict Segment Name
[03:48:48:122] 00000 7FFFF 28C06998 28C06998 Good Whole File
[03:48:48:122] Requesting operating system ID...
[03:48:58:366] Operating system request failed, checking for a live kernel...
[03:49:04:032] Checking for recovery mode...
[03:49:14:349] PCM is not responding to OSID, kernel version, or recovery mode checks.
[03:49:14:356] Unlock may not work, but we'll try...
[03:49:14:365] WARNING: P04 Support is still under development!
[03:49:16:991] Unlock was not successful.
[03:49:32:885] VIN query failed: Timeout
[03:49:56:909] Operating system query failed: Error
[03:50:32:623] WARNING: This version uses the new Assembly Kernels, USE AT YOUR OWN RISK!
[03:50:37:381] C:\Users\ScottAnderson\Desktop\Tuning\L67\CarlSTOCK.bin
[03:50:37:396] Validating 512k file.
[03:50:37:412] Start End Stored Needed Verdict Segment Name
[03:50:37:443] 00000 7FFFF 28C06998 28C06998 Good Whole File
[03:50:37:443] Requesting operating system ID...
[03:50:47:568] Operating system request failed, checking for a live kernel...
[03:50:53:128] Checking for recovery mode...
[03:51:03:389] PCM is not responding to OSID, kernel version, or recovery mode checks.
[03:51:03:397] Unlock may not work, but we'll try...
[03:51:03:426] WARNING: P04 Support is still under development!
[03:51:06:964] Unlock was not successful.

[antus]

Did you save the debug log of what happened with the initial write? There is no detail in your post that can help us with - what pcm it is, what you did, or what happened. We need service number, operating system ID (OSID), and a description of your process and the operation you ran on it. That alone still may not be enough without the debug log from the write if something went wrong.

[ProfessWRX]

At some point it cleared out the log. Not sure what option I tried that did that.

[ProfessWRX]

This is the stock bin I was able to pull.

Service: 12583827 YFXS
HDW: 12582720

[ProfessWRX]

I believe I tried to write OS/Cal/Boot and that is what failed and it was VERY early on in the write.

[antus]

In future, especially if you think you might need some help and you are not sure it worked, save the debug log from the process. Especially as you are running a test build that we are still seeking initial testing and feedback on from. You are probably the very first person to try what you did in car and it would be very useful to see how it failed. I understand going for it with the excitement but that is what the warnings that you clicked through are about. That initial read confirms that it is a p04 pcm. But if the debug log was not saved and is now gone, we have no way to see why or how it failed. None of the developers have a vehicle with a P04 in it, we are all developing on the bench, and the in car testing to date has been other pcm types.

All I can suggest is a power cycle if you have not. Beyond that the only way to recover it is probably with BDM which requires specialist hardware and good soldering / electronics skills.

[ProfessWRX]

I am noticing a problem with the Com ports when initializing the ODBX. It only seems to work first on COM5 but my cord is too short so I switch to COM4 to be able to reach it better, but COM4 keeps giving an initialization error unless I start on COM5. I believe the write was attempted on COM4 and possibly I think when I switched back to COM5 after the failure that deleted the logs prior.

Does any of that sound like a probable cause? Obviously there's no way for you to know for sure. But maybe I'll just deal with COM5 from now on.

The good news is that I did this on a spare PCM so I can still drive the car. I guess I'll head to the local junkyard and pick up a couple more PCMs on monday. Supposedly they have 4 left.