ol boy wrote:Instead of messing with VE why not figure out if one could increase the spark table to 16x16.
ol boy wrote:I was wondering, it's in the 1/10 scale which is why it's limited to 12x12 in size...?
dontz125 wrote:... which suggests that a 12x12 VE (HR) table could fit in the space of 16x16 VE1 and VE2.
racingmini_mtl wrote:Using different outputs is significantly (not to say completely) different from using memory differently. I won't go in details but that's not desirable in the least.
racingmini_mtl wrote:From a code stability, maintenance and support point of view, I don't think this is a good idea. Having a variable that can be either an 8-bit or 16-bit value depending on settings is asking for trouble. And this will have an impact on support due to user confusion among other things.
I'll let Ken and James chime in but as mentioned I don't think this is desirable even as a side project.
racingmini_mtl wrote:To be on a more positive note, I should add that I could see having an option to have VE2 be a global trim table similar to what exists for the sequential injection trim tables. This allows a 0.1 accuracy on a multiplication factor applied to the main VE table. So you can go from 87.6% to 112.4% while still using the 8-bit value.
I understand that it's not the same and would require using 2 tables but that seems to minimize the changes from the current code and everything around it while still allowing more precision on individual cells.
But I'll wait for comments from Ken and James on this matter.
Users browsing this forum: Google [Bot] and 1 guest