posible bug: K ,O and M keys on fuel/ignition map

[ByReaL]

version xxxx14

not shure if this are bugs

when you press M key on a cell from the fuel map, the respective cell change his color but i could not find the usage of this change.

if you press the K key in a fuel cell this has efect and i belive a bad one

if you press the O key in a ignition cell this has also efect

[Matt]

M / SPACE = mark cell

This was a requested item for highlighting cells manually during tuning. These cells disappear when the window is closed/reopened

K = Knock
O = O2 sensor

Currently do not discriminate on which map is selected and will change flags regardless. Raised CR10348 to check the map type before using the key



We have a problem with the O2 sensor flags which remove off bits 0x80 and 0x40 (total 0xC0) when O2 sensor flag removed

So values C0-FF equal 00-3F with O2 sensor flag off

But with images like R31 in the fuel map we see O2 sensor flag using values in range 0x80-0xFF

But I cannot pull the O2 flags from this otherwise it stuffs up the cell. Anyone know the correct way to pull O2 flags off these range of values? ie what should this range be without O2 flags?

I have currently remove O2 sensor flag in the next version for values 80-BF

Live Edit does not handle this well either (stuffs up the values)

[ByReaL]

maybe this could be a solution

to remove logical AND betwen the value that should be changed and 01111111 (0 where the flag bite is and the rest filed with 1)

to add logical OR betwen the value that should be changed and 10000000 (1 where the flag bite is and the rest filed with 0)

or use bite manipulation function if available like bitset ,bitunset....

[Matt]

That is what I do currently...

The problem is that for O2 feedback... there appears to be two flags used 11000000 when above 0xc0

[ByReaL]

in cells with 18x raw value O2 flag canot be turned off