P04 R&W Testing

[kur4o]

My first thought was to just go by utility file part number. The utility file should be unique to a given hardware type. You can also work backwards through the database to get VIN data from software part numbers. So you'd know this software goes to that make, model, engine and year.

I don't think it's possible to get 100% coverage, but it should be possible to close up a lot of the gaps.

The other problem is the data ends at Nov 2007. I've heard of a mid 2008 update, but that might be for Global TIS.

I only just got it converted the other day and I'm still working on pulling meaningful data. My SQL isn't much better than my Python. I did come up with a list of 71 P04 OSIDs based on a common utility number, so that was promising. My sincere wish is to contribute quality data instead of just exchanging one truckload of shit for another.

In other news, I finally wired up my P04 for bench use. Nearly all of the DIDs either return zeroes, or 7F 31. So that's annoying.

I can`t link the utility file with OS number on a single file flash. Can you generate a list with it. Than we can match it with my extracted list of P/n.

[Gatecrasher]

I won't have time to mess with it until later tonight.

I pulled software for a module similar to the one Antus posted earlier. I didn't buy it. I just picked the auction because it had VIN and a legible end item part number on the label.
https://www.ebay.com/itm/254362473299

It's 512k. It'll be up to you guys to decide if this qualifies as a P04 family module or not.

Utility, OS, VIN info and software info included.

[Gampy]

On the way ...

Unknown-7-003.jpg (58.42 KiB) Viewed 2564 times

1997, Buick, Park Avenue, Ultra Sedan 4-Door, 3.8L 3800CC 231Cu. In. V6 GAS OHV Supercharged

If someone would be so kind as to dig me up some accurate numbers for a 256k unit I'll have one on the way.
Not gonna stake ya on a ant hill if you're wrong ... It happens.
Thank You!

-Enjoy

[Gampy]

I won't have time to mess with it until later tonight.

I pulled software for a module similar to the one Antus posted earlier. I didn't buy it. I just picked the auction because it had VIN and a legible end item part number on the label.
https://www.ebay.com/itm/254362473299

It's 512k. It'll be up to you guys to decide if this qualifies as a P04 family module or not.

Utility, OS, VIN info and software info included.

Looks to have the same DLC and Flash registers as the P04, as well as COP's ... Not sure on the load address.
It is older then the typical 512k (P01 look alike) P04, obviously it looks completely different other then the twin 80 pin connectors, even has CLEAR on one.

That adds another alphabet to the mix ...

-Enjoy

[kur4o]

I finally found the missing file that have utility vs OS from database. Now it is matter to make a crossreference, of all p/n used for a given utility. Than we are good to go with some custom database.

[Gampy]

What is this 'Utility File' ??

Thank You!
-Enjoy

[antus]

Its the SPS Flash kernel.

[kur4o]

I found the lists but there is 2 entries part number and calibration number. I am trtying to figure what is what and how it can be read from pcm.

Can someone run some script on p04 on any version, early style, late style.

From universal patcher->utilities->logger
settings tab->select device->connect vpw->vpw console->uncheck buffered, check screen->upload script-> select the attached file-> save,copy log to .rtf file

[antus]

Just pcmhammer gives you calibration ID through the standard API.

Code: Select all

[06:19:20:755]  Thanks for using PCM Hammer.
[06:19:22:441]  VIN: 6H8VXK69F1L000000
[06:19:22:541]  OS ID: 12202088
[06:19:22:551]  Hardware Type: P01_P59
[06:19:22:649]  Calibration ID: 92108771
[06:19:22:749]  Hardware ID: 9386530
[06:19:22:875]  Serial Number: 1EB05W4V1029
[06:19:22:971]  Broad Cast Code: DFNN
[06:19:23:055]  MEC: 0

Thats not a p04 lol, thats the p01 ive been working on the asm flash kernel in lol, but you get the idea.

This is the P04, same requests.

Code: Select all

[06:25:30:720]  VIN: 1G2NG52E5YM750297
[06:25:30:807]  OS ID: 12589762
[06:25:30:809]  Hardware Type: P04
[06:25:30:812]  **********************************************
[06:25:30:815]  WARNING: P04 Support is still in development.
[06:25:30:818]  It may or may not read your P04 correctly.
[06:25:30:820]  There is currently no ETA for P04 Write.
[06:25:30:823]  **********************************************
[06:25:30:907]  Calibration ID: 9389414
[06:25:30:996]  Hardware ID: 9357440
[06:25:31:131]  Serial Number: 8DWY3C9290
[06:25:31:217]  MEC: 

Code: Select all

[06:25:30:890]  TX: 6C 10 F0 3C 08
[06:25:30:906]  RX: 6C F0 10 7C 08 00 8F 45 66
[06:25:30:907]  Calibration ID: 9389414

edit: I tried the script, I havn't used patcher like that before, it looked like it worked but nothing appeared on the screen. It found my device, and connected to the OSID, and took a minute or two to run, screen is checked, buffer unchecked, but not sure where the output went.

[joukoy]

Do you have "Enable VPW Console" checked?
(This selection should be removed, but is currently there)