See [anytrim]
Note that some combinations can be configured, but not normally configured because meaningless:
- Lambda target trim can be adjusted based on Lambda-Target (difference from target) (meaningless)
- however the RPM based dwell has not been implemented (in anytrim or elsewhere)
- RPM based dwell is normally not needed. But some old, low-tech distributers require long dwell at idle and low RPM, but don't work well at high RPM with long dwell (misfire at high RPM with long dwell, almost like a HW rev limiter). So appr +20% dwell at low RPM might be reasonable (likely not overheating the ignition transformer at low RPM, should be safe).
(config_ext.anytrim3_type & 0xF0) == 1) means "lambda trim" (also
Gory details... to check config and/or VemsTune ini based on this, just in case
- trimconfig == 0x31 means lambda - lambda target diff input
- trimconfig == 0x32 means scale with tps saturate at 60%
- trimconfig == 0x33 means scale with tps saturate at 90%
- trimconfig == 0x34 means scale with map saturate at 60 kpa
- trimconfig == 0x35 means scale with map saturate at 90 kpa
So Please note if( trimconfig >= 0x31 && trimconfig < 0x36) ... have special scaling above 0x31, and the lambda - lambda target calculation has some special cases for sparkcut, fuelcut and similar special modes.
- Also,
The anytrim config bits are (roughly) the following:\nÿ1ÿ
Either Anytrim 1, Anytrim 2 or Anytrim 3 (or Anytrim4 or Anytrim 5 ) but:
Lambda target, Launch RPM and Cranking pulsewidth can be trimmed by only one Anytrim control at the same time
- (if you enable it multiple times, the first function will take action ... or undefined behavior).
- TODO: review and retest the effect of noncompliant setting (likely ignored)