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% noob

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.

[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.