Factory Cal question

[Bent72]

On 8051 ecm for an original 94 Auto F body, 3.23 (confirmed). When I ran the EEHack, it pulled the vin and factory cal

The cal stored in the ECM is 16199611

(edit)
Per FBody, it updates to 16210011
(note: the information on Fbody differs from the EE_CALIBRATION_LIST PDF)



So before I do anything inside the ECM, why shouldn't I put the corrected cal in there?
And I'll be honest, 100% noob

[LeMarky Dissod]

On 8051 ecm for an original 94 Auto F body, 3.23 (confirmed). When I ran the EEHack, it pulled the vin and factory cal
The cal stored in the ECM is 16199611
(edit)
Per FBody, it updates to 16210011
(note: the information on Fbody differs from the EE_CALIBRATION_LIST PDF)

So before I do anything inside the ECM, why shouldn't I put the corrected cal in there?
And I'll be honest, 100% noobYou COULD put the updated calibration in there, of course.
You may want to study the differences between 16199611 and 16210011.
Although it's unlikely that there are any meaningful differences, you never know for sure if you might learn something.

[Bent72]

You COULD put the updated calibration in there, of course.
You may want to study the differences between 16199611 and 16210011.
Although it's unlikely that there are any meaningful differences, you never know for sure if you might learn something.
Hi, and thanks for replying

I did compare each of the two .bin files in TunerPro. Looks like lower VE numbers across the board in the newer bin, as well as some changes in the downshift table on the 3-2 shift. I kinda suspect that just trying it is an option. I wasn’t sure if I would lose anything on the flash. Still reading through all the EEHack info I can find, there’s a lot of tools in there I don’t know how to use yet, and others I don’t even know are there

[LeMarky Dissod]

… some changes in the downshift table on the 3-2 shift.Regarding those changes, did the numbers changed go up or down?
Either way, GM's normal shift table is written to achieve the Corporate Average Fuel Economy City & HiWay MpG scores on the Monroney sticker.
Instead, you should write your normal shift table so that the shifter can stay in 'OD' and need never visit 'D' '2' or '1' under normal circumstances.
It may cost a few MpG compared to the Monroney sticker, but it's usually better for the transmission.
If as a driver you've very unusual circumstances that occasionally necessitate using another shift table, that's what the Performance Shift table is for.
I kinda suspect that just trying it is an option. I wasn’t sure if I would lose anything on the flash. Still reading through all the EEHack info I can find, there’s a lot of tools in there I don’t know how to use yet, and others I don’t even know are there.There's always a non-zero chance that you could brick the pcm each time you try to flash it, but FlashHack minimizes this so well that you should only need one spare pcm to feel perfectly at ease - and most people will never need to use the spare pcm.
If you save 16199611 prior to flashing in 16210011, you'll lose nothing, and you can always go back to 16199611.

[Bent72]

Not at the laptop this moment, but I can post the shift chart later
All the movements on that downshift are negative value (see edit post 8)

I don’t have a spare ECM, but I almost to the point of flashing the ECM anyway to tune it. Haven’t read too many posts about flashhack and ECMs having a problem, so I’m going to give it a go tomorrow I think. I’ll make sure to copy my ECM before sticking my fat fingers in there

[LeMarky Dissod]

Not at the laptop this moment, but I can post the shift chart later.
All the movements on that downshift are negative value.Making the 4L60E less responsive to the enthusiast's foot. No thanks.
I don’t have a spare ECM, but I almost to the point of flashing the ECM anyway to tune it.
Haven’t read too many posts about flashhack and ECMs having a problem, so I’m going to give it a go tomorrow I think.
I’ll make sure to copy my ECM before sticking my fat fingers in there.In my experience with TunerCAT LT1 OBD1's flash utility, I've experienced less than .1% brickage - and FlashHack is clearly superior.
Go ahead and flash it.

[Bent72]

You’ve confirmed what my inclination was, skip the shift table change and add the rest of the updated bin. I’ll give it a shot and post back

Thanks

[Bent72]

Update to correct my information above
On the table for down shift pressure modifier 3>2

mph change
14 15.00
22 8.00
26 -12.00

In the table for "Performance Up/Down Shift Points" for the 3>2
0.0 0.00 0.00 0.00 0.00 -7.00 0.00
6.3 0.00 0.00 0.00 0.00 -7.00 0.00
12.5 0.00 0.00 0.00 0.00 -5.00 0.00
18.8 0.00 0.00 0.00 0.00 -3.00 0.00
25.0 0.00 0.00 0.00 0.00 -2.00 0.00
31.3 0.00 0.00 0.00 0.00 -1.00 0.00
37.5 0.00 0.00 0.00 0.00 -1.00 0.00


Might try it, dunno. It will be hard to test if it doesn't stop raining

[Bent72]

Using Flashhack, copied and saved what was in the PCM just fine. Loaded the new bin, said success.
Running EEHack, it was displaying the original bin number. Not sure if I did something wrong of if it is just showing the start point. I hit "RELOAD" and had no change

[kur4o]

I suggest you load the latest cal from GM, unmodified and start tuning from there.

There is a service bulletin about the 3-2 clunk which I actually had long time ago and the update fixed it.

Here is some more info

https://tis2web.service.gm.com/tis2web/?target=AG2USGSTSB3US&target.method=onSubmit&AKQVS1VVSH4WS=1&bm=_top#_top

[kur4o]

Using Flashhack, copied and saved what was in the PCM just fine. Loaded the new bin, said success.
Running EEHack, it was displaying the original bin number. Not sure if I did something wrong of if it is just showing the start point. I hit "RELOAD" and had no change


The cal number is written in the eeprom and is not updated during flash. You can manually edit in eehack main window. Write your new cal id and hit Set CALID.

[Bent72]

I dumped it straight in, no changes. I figured it was best to log it and if there was an issue, fix it later. For some reason got the CEL to come on and turned the fans on that time. Haven't found what it was though

I think I'm going to start using a notebook and just keep track as I go. That's how I deal with tech stuff at work, it leaves a nice paper trail.
Thanks for the info!

[Bent72]

I suggest you load the latest cal from GM, unmodified and start tuning from there.

There is a service bulletin about the 3-2 clunk which I actually had long time ago and the update fixed it.

Here is some more info

https://tis2web.service.gm.com/tis2web/?target=AG2USGSTSB3US&target.method=onSubmit&AKQVS1VVSH4WS=1&bm=_top#_top

Got an E4214 error trying to open that link. Is there a browser setting i need to manipulate to make it open? This laptop is a bit clunky itself...

[kur4o]

Got an E4214 error trying to open that link. Is there a browser setting i need to manipulate to make it open? This laptop is a bit clunky itself...
The link is broken. Try this site and enter the random google vin. Than follow instruction.

https://tis2web.service.gm.com/tis2web/

2G1FP22P8R2106454

[Bent72]

The link is broken. Try this site and enter the random google vin. Than follow instruction.

https://tis2web.service.gm.com/tis2web/

2G1FP22P8R2106454

It comes back with 16210011 as the "part number" and then has "CalId#", am I correct that those CalID numbers (16209578 and 9) are included in the 16210011?

I hope so, that's the one I loaded earlier!
Thanks for the link

[NomakeWan]

It comes back with 16210011 as the "part number" and then has "CalId#", am I correct that those CalID numbers (16209578 and 9) are included in the 16210011?
You are correct. The "Calibration ID T-Side" value in the BIN is the "part number" as well as the BIN's filename, and is what's updated when you flash. As kur4o pointed out, the secondary number (what TIS calls Cal.ID#) isn't updated during flash and can be set manually using EEHack after flashing.

And you can rest assured that flashing with Flashhack is completely safe, no need for spare PCMs. It's so much more advanced than TunerCats it would make your head spin.

[Bent72]

You are correct. The "Calibration ID T-Side" value in the BIN is the "part number" as well as the BIN's filename, and is what's updated when you flash. As kur4o pointed out, the secondary number (what TIS calls Cal.ID#) isn't updated during flash and can be set manually using EEHack after flashing.

And you can rest assured that flashing with Flashhack is completely safe, no need for spare PCMs. It's so much more advanced than TunerCats it would make your head spin.
When I started my journey about a month ago, other folks (not here) were steering me towards TC. After doing nothing but research for a month, and then using the Flashhack program, I was amazed how easy that was. Same with EEHACK. I actually feel comfortable enough to do this myself without messing up

Of course there’s a ton of threads here. I have a lot of catch up to play in the learning dept

[NomakeWan]

When I started my journey about a month ago, other folks (not here) were steering me towards TC. After doing nothing but research for a month, and then using the Flashhack program, I was amazed how easy that was. Same with EEHACK. I actually feel comfortable enough to do this myself without messing up

Of course there’s a ton of threads here. I have a lot of catch up to play in the learning dept
This is because most folks outside this specific hacking community are not even aware that an alternative exist, and have come to trust TunerCats since they have been around for so long. In fact, I even had someone on a Corvette forum claim that merely the fact that TC existed longer than Flashhack was why TC was reliable and Flashhack wasn't. Didn't matter that I had actual serial data logs demonstrating the difference, didn't matter that the data handling between the two is demonstrably more reliable in Flashhack's case.

So don't be alarmed if a bunch of "old guys" tell you to use TC or JET. They just don't understand that something better exists.

[Bent72]

Well I was blessed that Eagle Mark perused another site we were on for trucks, so I knew what was here. His work on that site still gets much use repairing Tbi era stuff. RIP Mark

Once I figured out there was LT1 specific tools, that kinda made my day