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:
then we copy all the tables from current map which is on FP2.0 and we got these:
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
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
FP2.0 to new FP2.1 migration bug
Moderator: Matt
-
- Posts: 301
- Joined: Sat Jun 21, 2008 1:50 am
- Location: Croatia
- Contact:
Re: FP2.0 to new FP2.1 migration bug
There must be an overlap with these two parameters. I'll look into itif we try to ''untick'' Bit 2, Bit 3, Bit 4, Bit 5, Bit 7 then the Total Injection Multiplier automatically changes
Re: FP2.0 to new FP2.1 migration bug
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 ENTsTOTAL_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
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
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
viewtopic.php?f=6&t=3292&p=28717
Release
viewtopic.php?f=12&t=3665&p=28719