Ive been super busy with work and ive had little time to delve into this area lately. but im trying to understand how the look up routines for the map sensor valvues all hook together. like how do i rescale the map input values and not loose table resolution. it would be really nice to be able to make larger tables that change via map voltage so there were in fact sevral tables for each level of boost like

0 -110
110-190
200-290


etc etc etc. this would mostly apply to spark becuase the fueling calc with the BPW multiplier seem to work good it just be nice to have more row in the 2d tables to get picky with maybe change it to 5 kpa increments.

Im getting there dammit. if i only had a brain !

 

ldaA RPM
ldX table 2
ldaB map more than 1 bar
bne to call
ldaB map up to 1 bar
ldX table 1
call 3-d interpolate
staA main spark advance

You can divide map by subtracting then multiplying.

In this example map up to 1 bar would be (raw map * 2) and map more than 1 bar would be ((raw map - 128) * 2) This created the situation where if raw map is greater than 1 bar then map more than 1 bar is non-zero and it uses the upper table. Otherwise map more than 1 bar is zero and the lower table is used. This same concept can be used for 3 4 or 5 bars. You just need to be sure there is an overlap row because you cant interpolate the space in between the tables.

HTH

John

 

We already have a proper 3 bar code modification for the 58, I just need 72 or more hours inna day now.

Plus some other stuff that'll knock your socks off.

Like the line from Midnight Run, "This is good, real good".

 

with out a loose of table resolution??. youve got me listening now for sure. throw me a email.

 

All the answers are in Grumpy's other posts about the $58, $59 and $60 stuff :-)

I've seen it and when he says theres lots of room for patches he isnt lying :-)

Now i just need to get to the point where i can do patches like a VE table I'll be happy ;-)

LAter
Jeremy