I'm not sure it makes complete sense to me yet but thanks for looking into it!
I've already found by hand that 0x44(44) puts me 2% rich of target so that should be close enough. I was just laboring under the false assumption that this was a 16 bit scalar when in fact it's 8 bit and optimized somehow (for speed?)? I don't really want to delve into motorola machine code but why couldn't something like 0x4646 be valid?
I don't think it's a problem losing maximum possible value - the only reason to change this is to accommodate larger injectors so a tuner theoretically shouldn't need the ability for larger maximum PWs here.
Will give it a try tonight.
I was able to test with your fork of eehack last night and think I must have been mis-using the trims initially. It wasn't clear to me at the time that the ram table needed to be populated manually before enabling it. I know it would be an undertaking, but some of that stuff deserves a bit of a how-to write up in the readme or something. There's only so much intelligence that can be squeezed into the mouse-over tool tips.
Edit: Whatever the case, I suppose the parameter definition for 12680 should be setup as a two byte table instead of a 16 bit scalar.
Reply With Quote
Bookmarks