Page 1 of 1

FP2.0 to new FP2.1 migration bug

Posted: Mon Jun 13, 2022 5:03 am
by skylinegtrhr
Hello,



when we try to convert current map which is on FP2.0 to new FP2.1 we get this problem with the Feature Control flags 2 table



if we open the ROM Pack file S14_SR20DET_74F0I_MT_FP_maps.bin the Feature Control flags 2 table look like these:



Image


then we copy all the tables from current map which is on FP2.0 and we got these:





Image


Referring to your manual Nistune Feature Pack.pdf on Page 31, the only thing on the Feature Control flag 2 table that should be thick is Bit 0 - Flatshift Enable

if we try to ''untick'' Bit 2, Bit 3, Bit 4, Bit 5, Bit 7 then the Total Injection Multiplier automatically changes



Image



and also if we then try to manually change the Total Injection Multiplier back to target value the Bit's on the Feature Control flag 2 table automatically ''thick'' again

Image

Re: FP2.0 to new FP2.1 migration bug

Posted: Tue Jun 14, 2022 6:20 pm
by Matt
if we try to ''untick'' Bit 2, Bit 3, Bit 4, Bit 5, Bit 7 then the Total Injection Multiplier automatically changes
There must be an overlap with these two parameters. I'll look into it

Re: FP2.0 to new FP2.1 migration bug

Posted: Sat Jun 18, 2022 10:58 am
by Matt
TOTAL_INJECTION_MULTIPLIER,&HF459,2,1,2,1
FEATURE_CONTROL2,&HF45A,1,1,1,1
TPS_FLAT_SHIFT,&HF45B,1,1,1,1
REV_LIMIT_FLAT_SHIFT,&HF45C,2,1,2,12.5
Yeah we have a memory overlap with TIM and the FC2 flags. I'll have to push them out 1 byte and rebuild and test the ENTs

Previous testing just checked things one at a time, but not both which is why this wasn't detected when flat shift was used

Re: FP2.0 to new FP2.1 migration bug

Posted: Fri Jun 24, 2022 3:43 pm
by Matt
Fixed and re-tested with version put up today
viewtopic.php?f=6&t=3292&p=28717
Release
viewtopic.php?f=12&t=3665&p=28719