98 99 Blackbox XMLs

They go by many names, P01, P10, P12, P59, E38, VPW, '0411 etc.
sparepartsblazer
Posts: 90
Joined: Mon Dec 04, 2023 1:18 am
Location: Missouri

98 99 Blackbox XMLs

Post by sparepartsblazer »

Since we can now read the 98-00 Blackbox PCM, I think I got most of the 98 99 mapped out. Only a few tables have been at the same address. The 00 PCM are way different.

I havent converted them to XDF yet as some of the tables need the rows and colums switched.

Also attached are the addresses for the 99 ECM.
You do not have the required permissions to view the files attached to this post.
Last edited by sparepartsblazer on Sat Nov 08, 2025 4:07 am, edited 1 time in total.
sparepartsblazer
Posts: 90
Joined: Mon Dec 04, 2023 1:18 am
Location: Missouri

Re: 98 99 Blackbox XMLs

Post by sparepartsblazer »

Wont let me post the XML files
User avatar
antus
Site Admin
Posts: 10013
Joined: Sat Feb 28, 2009 10:34 am
cars: TX Gemini 2L Twincam 8psi
TX Gemini SR20 18psi
Datsun 1200 Ute
Subaru Blitzen '06 EZ30 4th gen, 3.0R Spec B
Subaru WRX 2007

Re: 98 99 Blackbox XMLs

Post by antus »

Thanks for sharing!

I could allow the XML extension but its probably best to zip them to save server space and bandwidth. xml compresses very well.

Can you also provide what OSID you are working with, it may be different between different OSIDs and it gives us a known baseline to compare.
Have you read the FAQ? For lots of information and links to significant threads see here: http://pcmhacking.net/forums/viewtopic.php?f=7&t=1396
sparepartsblazer
Posts: 90
Joined: Mon Dec 04, 2023 1:18 am
Location: Missouri

Re: 98 99 Blackbox XMLs

Post by sparepartsblazer »

The 98 OSID is 16263425.
The 99 OSID is 9365085

Mod edit: convert 7z to zip for greater compatibility
You do not have the required permissions to view the files attached to this post.
sparepartsblazer
Posts: 90
Joined: Mon Dec 04, 2023 1:18 am
Location: Missouri

Re: 98 99 Blackbox XMLs

Post by sparepartsblazer »

When reading with PCM Hammer where does it find the Hardware Id and Broadcast Code. I havent been able to find them in the bin file

Code: Select all

[11:29:38:920]  VIN: 1GCDT19X1X8151004
[11:29:38:966]  OSID: 9365085
[11:29:38:966]  Description: Vortec Black Box 98-02, 4 Plug, Service No 16263494
[11:29:39:013]  Hardware ID: 872432466
[11:29:39:060]  Broad Cast Code: CMUD
[11:29:39:116]  MEC: 0
User avatar
antus
Site Admin
Posts: 10013
Joined: Sat Feb 28, 2009 10:34 am
cars: TX Gemini 2L Twincam 8psi
TX Gemini SR20 18psi
Datsun 1200 Ute
Subaru Blitzen '06 EZ30 4th gen, 3.0R Spec B
Subaru WRX 2007

Re: 98 99 Blackbox XMLs

Post by antus »

It uses the Mode 3C service "Read Data by Block Identifier". It's up to the operating system to store and respond with the data. PCM Hammer does not need to know and does not know how the operating system stores it internally.

For more information I'd suggest playing around with universal patcher. It can analyse most GM bin files in more detail than PCM Hammer can, and its logs are quite verbose, as well as its definitions are XML which you can read for additional information.
Have you read the FAQ? For lots of information and links to significant threads see here: http://pcmhacking.net/forums/viewtopic.php?f=7&t=1396
sparepartsblazer
Posts: 90
Joined: Mon Dec 04, 2023 1:18 am
Location: Missouri

Re: 98 99 Blackbox XMLs

Post by sparepartsblazer »

Universal patcher is what I have been using. Im still learning on what it can do.
kur4o
Posts: 1145
Joined: Sun Apr 10, 2016 11:20 am

Re: 98 99 Blackbox XMLs

Post by kur4o »

blackbox don`t have writable eeprom section in main flash. It is buried in cpu or some external chip. Even vin is written as calibration part.
Some data can be accessed only from obd2 and running pcm.

If you need any help with advanced option in Universal Patcher, I can help with some of not well documented features.

The main rule is to use common naming for tables, that way you compare tables between different bins and even between different platforms.
You can also make one xml for all OS versions and add OS:address pairs, or import, update in existing xml addresses using some common key like tablename.

If some bins have some layout but addresses are switched with some offset, you can use the extraoffset column[it can take positive or negative numbers in decimal] to port some addresses of different OS and than export new xml with fields that have extraoffset data, -0 , is used if address is the same between OS.

If any feature is needed that will ease making a better, faster xml, we can add it on demand.
sparepartsblazer
Posts: 90
Joined: Mon Dec 04, 2023 1:18 am
Location: Missouri

Re: 98 99 Blackbox XMLs

Post by sparepartsblazer »

kur4o wrote: Thu Nov 13, 2025 12:16 am blackbox don`t have writable eeprom section in main flash. It is buried in cpu or some external chip. Even vin is written as calibration part.
Some data can be accessed only from obd2 and running pcm.
Thats kind of what I was thinking.
kur4o wrote: Thu Nov 13, 2025 12:16 am The main rule is to use common naming for tables, that way you compare tables between different bins and even between different platforms.
You can also make one xml for all OS versions and add OS:address pairs, or import, update in existing xml addresses using some common key like tablename.
Ive been trying to keep everything named close to what HPTuners uses,as that is what I have.
kur4o wrote: Thu Nov 13, 2025 12:16 am If some bins have some layout but addresses are switched with some offset, you can use the extraoffset column[it can take positive or negative numbers in decimal] to port some addresses of different OS and than export new xml with fields that have extraoffset data, -0 , is used if address is the same between OS.
That part is still way over way head. Still learing,so keeping things somewhat simple.
kur4o wrote: Thu Nov 13, 2025 12:16 am If any feature is needed that will ease making a better, faster xml, we can add it on demand.
To be able to hide columns in the XML editor would help. I move all the columns Im not using to the end, but have to do it everytime I open a new xml.
Also to keep the current line highlighted.
User avatar
Backwoodsracing
Posts: 23
Joined: Mon Apr 05, 2021 2:04 am
cars: I have 4 w-body’s 2 Silverado’s 1 Yukon 2 cavaliers

Re: 98 99 Blackbox XMLs

Post by Backwoodsracing »

i created a VATS patch for OS 16265175 i verified both bins and with the patch added both bins are the same. So if anyone wants to verify if it works and report back i'll look through the others i have here and make vats patches for them as well.
You do not have the required permissions to view the files attached to this post.