7.8 Advanced Engine 7 ADDITIONAL ITEMS: BEYOND BASIC FUEL AND IGNITION CONTROL
> = < This “logical operator” forms part of the equation.
• > is greater than
• = is equals. Usually, you don’t want to use the = sign here. This will turn on the output only when the variable
is exactly equal to the threshold number, with zero difference. There are a few variables, such as SD card
error conditions, where this can be useful. Most of the time, a variable won’t hit your threshold right on the
nose, and the output will stay unactivated.
• < is less than
Threshold The value compared against.
Hysteresis It is very common for a value to hover around the threshold, which would cause the output to turn
on and off rapidly. This setting helps to prevent that by creating a dead band below the threshold before the output
turns back off again.
• & is a bitwise AND function. This is normally used with Status, CELStatus, or Port fields. Both the Threshold
and Hysteresis values work completely differently when using this mode. This output is triggered when
the result of performing a bitwise AND function between the parameter and the threshold is equal to the
hysteresis value.
For example, suppose you want a value to activate when launch control is armed, but not active. Looking at the
Status2 field, we see we have the following bits in the field.
128 64 32 16 8 4 2 1
Closed loop
idle
Overboost
protection
Spark cut Flat shift
active
Launch
control
active
Launch
control
armed
Nitrous
stage 2
active
Nitrous
stage 1
active
We see launch control active has a value of 8, and launch control armed has a value of 4. So to look at both
these bits, we add these values together and set the “threshold” (bitmask) to 12. The bitmask “trims down” the
Status2 field like this:
128 64 32 16 8 4 2 1
Blocked by
bitmask
Blocked by
bitmask
Blocked by
bitmask
Blocked by
bitmask
Launch
control
active
Launch
control
armed
Blocked by
bitmask
Blocked by
bitmask
So, the possible values you can get through the bitmask are 0 (launch neither armed nor active), 4 (launch
active but not armed), 8 (launch active but not armed - not really possible) and 12 (launch both armed and active).
We then want to check that the value that makes it through the bitmask has launch armed (4) active, but NOT
launch 8. So we set the “hysteresis” (match) value to 4.
Additional condition
• No additional condition - only a single condition is used
• Or - output triggers if either condition 1 OR condition 2 is met
• And - output triggers only when condition 1 AND condition 2 are both met
7.8.24 Programmable on/off outputs 2
This screen works in the same way as the first programmable on/off outputs, but is used to trigger outputs on
remote CAN devices and loop conditions. Loop outputs behave as if you have “looped” a wire from an MS3Pro
output pin back into one of its own input pins to use it to trigger an external device such as a table switching input
or three step rev limiter - except you don’t have to use up any real pins.
AMP EFI MS3Pro manual version 1.202, firmware 1.5.0, 4/21/2017 Page 257