New PCM, is it dead?

[ProfessWRX]

One thing that is easy to watch happen live but you may not notice in the log is the com loss seems to build and get worse. It’s good at first then there’s one and it continues but then they come more frequently and the delays at the end are longer. Don’t know if that gives you insight.

This is of course only on the bench. As I’ve said, in-car the delay causes the dash to reset and coms never come back.

[kur4o]

I think to rule out more variables, some testing needs to be done.

Using the very same conditions, try running universal patcher script.

Using other tool will be also very informative.

It could be software issue, tool issue, tool-software interaction, noisy power supply, PC usb port issue, and last some pcm bus config issue.

Switching form x4 to x1 always resets other modules on bus, and if the tool don`t regain bus control, flash process will fail for sure.

It will be nice if some second tool monitoring can be done, to see exactly the moment of failure.

[ProfessWRX]

I think to rule out more variables, some testing needs to be done.

Using the very same conditions, try running universal patcher script.

Using other tool will be also very informative.

It could be software issue, tool issue, tool-software interaction, noisy power supply, PC usb port issue, and last some pcm bus config issue.

Switching form x4 to x1 always resets other modules on bus, and if the tool don`t regain bus control, flash process will fail for sure.

It will be nice if some second tool monitoring can be done, to see exactly the moment of failure.

Here's the log from Universal patcher. This was on the bench with the battery power supply.
VPW console: Screen checked, buffered unchecked. Same script as before. Successful read, but it looks like it missed quite a few blocks.

[kur4o]

It looks like it takes twice as long for the pcm to dump 4k data[800ms vs 1500ms now].

I increased the timings in script. Hope it helps a bit.

[ProfessWRX]

It looks like it takes twice as long for the pcm to dump 4k data[800ms vs 1500ms now].

I increased the timings in script. Hope it helps a bit.

Looks like it helped a bit. Still see some blocks not make it through.

[ProfessWRX]

Connecting (VPW)...
J2534 client initializing...
Initializing J2534 Device
J2534 client: Device initialization complete.
Connected to the device, ID: 1
Battery Voltage is: 13.128
Versions: Firmware: W, DLL: ", Api: W
Device initialization complete.
Removing all filters
Connected protocol: J1850VPW Speed: ISO14230
Sending file: C:\Users\ScottAnderson\Desktop\P04_read_1000_x4_0E_v3_TimingFix.txt
Setting VPW speed: FourX
Clearing functional address table (primary protocol)
Connected protocol: J1850VPW Speed: J1850PWM
Removing all filters
Disconnecting primary protocol
PCM: F0, Tool: 10
Missed parts in log:
2000 - 3000
5000 - 6000
9000 - A000
12000 - 13000
17000 - 18000
1B000 - 1C000
24000 - 25000
3C000 - 3D000
42000 - 43000
4B000 - 4C000
54000 - 55000
56000 - 57000
5E000 - 5F000
60000 - 61000
69000 - 6A000
6C000 - 6D000
74000 - 75000
7B000 - 7C000

[In-Tech]

Hiya,
A zener diode(if you can find one with the right voltage, it's approx 1000:1 and helps with reverse polarity which affects the non-intended) might work better in this situation of clock jitter.

[kur4o]

Slightly better, but still lots of missed part.

A new version in x4 mode with upped timings, and a version that will read in x1 mode[it will be way slower, just for testing].

[ProfessWRX]

Slightly better, but still lots of missed part.

A new version in x4 mode with upped timings, and a version that will read in x1 mode[it will be way slower, just for testing].

Didn't look any better.
Connecting (VPW)...
Protocol2 have connection from client
J2534 client initializing...
Initializing J2534 Device
J2534 client: Device initialization complete.
Connected to the device, ID: 1
Connected protocol: J1850VPW Speed: ISO14230
Removing all filters
Device initialization complete.
Versions: Firmware: ", DLL: W, Api: M
Battery Voltage is: 13.101
Sending file: C:\Users\ScottAnderson\Desktop\P04 reads\P04_read_1000_x4_0E_v4_TimingFix.txt
Setting VPW speed: FourX
Clearing functional address table (primary protocol)
Disconnecting primary protocol
Removing all filters
Connected protocol: J1850VPW Speed: J1850PWM
PCM: F0, Tool: 10
Missed parts in log:
0000 - 1000
5000 - 6000
8000 - 9000
E000 - 10000
1D000 - 1E000
23000 - 24000
2C000 - 2D000
2E000 - 2F000
30000 - 31000
32000 - 33000
35000 - 36000
3B000 - 3C000
3E000 - 41000
45000 - 46000
4C000 - 4D000
51000 - 52000
60000 - 61000
72000 - 73000

[ProfessWRX]

SUCCESS! It likes the 1x read.

Connecting (VPW)...
J2534 client initializing...
Initializing J2534 Device
J2534 client: Device initialization complete.
Connected to the device, ID: 1
Battery Voltage is: 13.065
Versions: Firmware: W, DLL: W, Api: L*?r
Device initialization complete.
Removing all filters
Connected protocol: J1850VPW Speed: ISO14230
Sending file: C:\Users\ScottAnderson\Desktop\P04 reads\P04_read_1000_x1_0E_v4_TimingFix.txt
PCM: F0, Tool: 10
Writing to file: C:\Users\ScottAnderson\Desktop\FULLREADJUNKYARD.bin
Done
Done
Disconnecting...J2534 Server Quits
Clearing functional address table (primary protocol)
[Done]
Saving to file C:\Users\ScottAnderson\Desktop\1xFULLreadJunkyard.txt... [OK]