PCM Hammer 98/99 Black Box Support

[Backwoodsracing]

You mean before or after it writes the changes? If before, no changes to be written. If after, then it worked and passed the self check it was successful
Thanks for posting a success report. I know 98/99 black box is working, but we've had almost zero feedback so a report of success is welcome and helpful and its good to know someone is using it.

It was my own fault I loaded the wrong file, But it did write the vats off bin successful.

[cmaje72]

Here is another blackbox bin from a 99 Suburban I am trying to help a buddy with. Reads and writes went fine but there is an issue with the checksum on the transmission section.
It does not seem to get corrected in PCMhammer so if a change is made and the tune is flashed the truck will not run.

I opened the bin in universal patcher and corrected the checksum for the trans section. I am awaiting results.

I have not read through all of the blackbox threads so if this has already been corrected let me know.

[antus]

I am not sure what you are talking about. PCM Hammer reads and writes, it does not touch checksums. It will validate them, and it will reject a write if a checksum that it is aware of is incorrect. Are you saying there is bad checksum in the factory tune on the PCM? There are some early tunes like that. Are you saying you are editing the file in 3rd party software and it is not updating the checksum? If so, that is a problem with the tool you are editing it with. Are you saying that is the case, and PCM Hammer is not aware of the checksum and cannot see the problem and is flashing it when it should reject it?

[cmaje72]

PCM Hammer is not aware of the checksum and cannot see the problem and is flashing it when it should reject it?

This. I thought PCMhammer also fixed the checksums. At any rate it will let you flash this file with an incorrect checksum for the transmission segment. Maybe its this particular bin. Don't know.

[12:59:17:121] Thanks for using PCM Hammer.
[12:59:42:100] Examining C:\Users\user\Desktop\99 Burb.bin
[12:59:42:115] Identifying 512KiB file.
[12:59:42:131] File is Vortec BlackBox 512KiB.
[12:59:42:162] File operating system ID: 9365095
[12:59:42:178] File is Vortec BlackBox 512KiB.
[12:59:42:178] Start End Stored Needed Verdict Segment Name
[12:59:42:194] 20002 66F63 81E3 81E3 Good Operating system
[12:59:42:209] 08002 0E651 0EF1 0EF1 Good Engine calibration
[12:59:42:209] 0E654 0EF93 1205 1205 Good Engine diagnostics.
[12:59:42:225] 0EF96 0F0D1 9B19 9B19 Good Transmission calibration
[12:59:42:240] 0F0D4 0F109 6EE4 6EE4 Good Transmission diagnostics
[12:59:42:240] All checksums are valid.



99 Burb.bin (blackbox (v 1))

Segments:
OS PN: 9365095, Ver: PE, Nr: 1 [20000 - 66F63], Size: 46F64
EngineCal PN: 9364759, Ver: AC, Nr: 2 [8000 - E651], Size: 6652
FuelSystem PN: 16250420, Ver: AS, Nr: 3 [E652 - EF93], Size: 942
System PN: 16216223, Ver: AZ, Nr: 4 [EF94 - F0D1], Size: 13E
Speedo PN: 16188989, Ver: BM, Nr: 5 [F0D2 - F109], Size: 38
vin PN: 3GNFK16R1XG134156 , Nr: 6 [148FE - 1491D], Size: 20
TransCal PN: 16216105, Ver: BP, Nr: 7 [F10A - 148FD], Size: 57F4

Checksums:
OS Checksum 1: 81E3 [OK] Checksum2: 7954 [n/a]
EngineCal Checksum 1: 0EF1 [OK] Checksum2: 7D2A [stock]
FuelSystem Checksum 1: 1205 [OK] Checksum2: 2CAC [stock]
System Checksum 1: 9B19 [OK] Checksum2: 4C16 [stock]
Speedo Checksum 1: 6EE4 [OK] Checksum2: 3A7D [stock]
vin Checksum 1: E9F8 [OK] Checksum2: D242 [n/a]
TransCal Checksum 1: D52A [OK] Checksum2: F6D1 [stock]

[antus]

I don't see a problem with the file from your output, sums are OK according to universal patcher. But then you say you fixed them. I tested what you posted with EFI Live for another opinion and it says file is OK too. What makes you think there is a checksum problem? That bin does not look to use Engine Diagnostics or Transmission Diagnostics if they are the segments you are looking at and tools are not looking there. DTCs are in the engine and trans calibration segments which have correct sums. Can you post the original file that you say it is flashing when it shouldn't? I want to have a look at what is going on there and see if PCM Hammer needs more 98/99 Black Box logic.

[cmaje72]

What PCMHammer thinks the checksum for the trans segment is:
[12:59:42:225] 0EF96 0F0D1 9B19 9B19 Good Transmission calibration

What it actually is (from universal patcher, note the different location):
TransCal PN: 16216105, Ver: BP, Nr: 7 [F10A - 148FD], Size: 57F4
TransCal Checksum 1: D52A [OK] Checksum2: F6D1 [stock]

The bin I attached is the original bin. So if you make a change in the transmission segment (in this case TCC lockup tables were being modified) the checksums for the trans cal change. I used tunerpro to make the changes and apparently it does not fix the trans segment checksum either (I don't know if I have the plugins loaded on that laptop). You go to flash this new bin and PCMhammer will allow you to proceed even though the checksum for the trans segment is incorrect. This results in a non-running engine. Load the same modified bin up in UP and run the fix checksums, flash again and all is well.

[antus]

OK, I see what you mean. Good pick.

It looks like operating system and Engine Calibration is OK.
Then what PCMHammer calls Engine Diagnostics / Transmission Calibration / Transmission Diagnostics are actually Fuel System / System / Speedometer. And Transmission Calibration and Transmission Diagnostics are missing and not checked.
I'll look in to that, and you'll need to add the trans section checksums to whatever XDF you are using.

[antus]

Well that is strange. The sum table is out of order so need a special case for this. That's no problem. Yet another edge case. Pretty standardly non-standard for this stuff. But I bumped the checksum table size from 5 up to 7 and it found and checked 7 checksums including the ones we wanted. They are all valid. So I can see which labels to move to make the descriptions to agree with universal patcher and efilive, but then we have 2 more checksums that appear to be real and valid. But what are they? I could leave them in as unknown and still validate them. Or skip them like they're not there. But if they're present and correct they must be something that nobody has uncovered yet. Fun times doing 27 year old PCM archeology. I think I'll test if they are the diagnostic segments. That'd make sense as they are the two unaccounted for. Change some MIL flags and see if they change...

[antus]

Latest development version has this fixed. It looks like there is a very small segment with the VIN and a couple of flags only, and a different segment order. The PCMHammer output now looks like this and would find your bad sum.

The segments are listed in the order they exist in the segment index in the bin, that's why they're a bit different to the other platforms which are also in index order, just GM was tidier on the other ones. This was likely one of the first to have segments.

Code: Select all

[01:56:59:123]  Examining 99 Burb.bin
[01:56:59:136]  Identifying 512KiB file.
[01:56:59:142]  File is Vortec BlackBox 512KiB.
[01:56:59:149]  File operating system ID: 9365095
[01:56:59:157]  File is Vortec BlackBox 512KiB.
[01:56:59:159]  	Start	End	Stored	Needed	Verdict	Segment Name
[01:56:59:163]  	20002	66F63	81E3	81E3	Good	Operating system
[01:56:59:168]  	08002	0E651	0EF1	0EF1	Good	Engine calibration
[01:56:59:179]  	0E654	0EF93	1205	1205	Good	Fuel system
[01:56:59:186]  	0EF96	0F0D1	9B19	9B19	Good	System
[01:56:59:195]  	0F0D4	0F109	6EE4	6EE4	Good	Speedometer
[01:56:59:203]  	14900	1491D	E9F8	E9F8	Good	VIN
[01:56:59:212]  	0F10C	148FD	D52A	D52A	Good	Transmission calibration
[01:56:59:219]  All checksums are valid.

You can get it from the download link on github here (requires account and logged in): https://github.com/PcmHammer/PcmHammer/ ... 1615722093

[SmichaelR22]

trying to talk to a 2000 black box s10 4.3/4l60 swapped to a rock crawler, just need VATS deleted (no future tuning desired). I have done many other p01/p59 swaps so i'm somewhat confident in the process basics here- but never have done black box stuff. I have a 0411 on the shelf, connectors, and printouts put together but hoping i don't have to do that, if its just something simple i missing here.

My read gets stuck on the CRC process step after it reads, then fails read. same result with any of the versions i tried of github i found with multiple attempts.

Obdlink LX
logs attached

It reads but crc check procedure not started
ObdLink SX latest firmware
PCM were tuned by HP tuners before (not locked) by me

I've been occasionally getting that same Object reference error during crc checks, restarting my laptop usually solves it for a while so I can get a few reads/writes before it starts throwing the error again.