It's possible, but I would think that could possibly be from still being a bit lean.
Mick, check your email.
FWIW, I built that .cax file for the Holden platform & had a look at a few stock files. The Holden platform uses a much lower factory setting between 1.03-1.09ms, where the US platform is around 1.27ms. This is more than likely the reason why I never had the same issues getting a low enough PW when I run 60lbers on my car.
I will be doing some quick tests on mine tonight to see if this table has any effect. Will keep you all posted.
so this table you altered is a table that efilive doesn't normally show ?? so how did you find it or know about it?
After repeatedly pestering MICK for some cax files he sent me 2 .bin files that I could play with & attempt to build definitions for. With some maps etc I had found on the web a few years ago I managed to find what parameters I was chasing plus a bit more.
I am still learning at this stage, but as long as I stay away from the code areas of the .bin file damage will be minimal.:rotflmao:
:master:
Hey Mick,
Ryan's file is COS3 based on a 2002 Camaro file... does that mean it's based on 12212156...?
In my mind, the answer is yes...
This means your 02020003 cax file also applies to 02020005 and 12212156... 3 birds with one stone... :cheers: ...good job.
That's correct Joe. From what I can see so far (though I am not really looking as it is way beyond my skills) the COS's still use the same main table addresses, apart from the custom tables which either use a code change to change axis, or use other sections of the file, leaving the base calibration intact.
The Corvette is in the shop trying to get it sorted for a Sunday prestart, ready for next weeks first round, so playing with mine has been put on hold till tomorrow. I will post up the results of the .cax test ASAP.
If any of you are interested check out acracing.com.au. This car really is a work of art & makes the late nights bearable.
Nice looking Corvette Mick