RomRaider

Can we get a taste of the spreadsheet?
How close does it get you to actual degrees?

Subscribing

You know, there's button for that ...

Fun fact: the three GOV tables (GOV, GOV3, and GOVL) are deceleration ignition timing tables. So they also have two tables that add timing based off coolant temperature (and whether it’s in drive or neutral) But these completely bypass trimming and MBT calculations. They also only have two set of limiters, with only one that seems necessary to alter! I still need to do some testing, as there’s a section dedicated to setting something GOV based. But I think even just removing the limiter would allow you to retard ignition timing as far as you want during deceleration.

So if you want pops and bangs, flames, burbles, etc, the GOV tables are the ones you need to alter! After removing the limiter, of course. Which is code based. I’ll provide more updates later once I get a chance to test it out.

One thing actually, it’s possible that there are more limiters and compensations at play. But this is just for the GOVIDL calculation. This theoretically shouldn’t be compensated for past what I just listed, but who knows. I still need to follow it to see how GOVIDL is implemented into the main ignition timing function.

Edit; Unfortunately, the GOV tables are also used as idle timing tables. So any changes to them will affect idle alongside deceleration. This means custom coding is required to have no adverse effects.

My understanding of the GOV tables is the axis is RPM so you can leave the left few cells alone and still do what you want with the right ones.

It's been a really long time since I defined these but in my defs, I have all 3 GOV tables with RPM axis of 0, 400, 800, 1200, 1600, 2000, 2400, 2800. I only need to change the 400 and 800 cells to get my idle timing up or down.

Yup! 0-2800 RPM is the axis. For some reason I was thinking the GOV tables were coolant temp based haha So I suppose tuning for decel is back on! I do want to datalog some of the RAM parameters that get checked to determine GOV vs GOV3 though. I'm just hoping it'll stick with the coolant temp threshold.

I think I got the tables confused with the mTAVCD1 tables, since they're coolant based (and seemingly AT Gear Position Based) + their value is added ontop of GOV.

I use another tool for manipulating timing tables then just open, checksum and save in RomRaider. In the defs for the other tool, I use X-64 conversion for all cells outside the knock window and X-192 conversion for cells in the knock window. I have no desire to change where the knock window is.