Yes, the mismatch of IfEqualValue with IfAboveAction can't work. Indeed, consider it "forbidden".Note something which doesn't really make sense in the initial code, nor in the second one: you've used IfEqualValue option, along with an IfAboveAction option. Usually these should be used in pairs: IfEqualValue with IfEqualAction and IfAboveValue with IfAboveAction. Even if not forbidden, this approach is at least weird. Check this please.
In addition, the Formula=(MeasureSystemTimerOld<>MeasureSystemTimerCurr) isn't really the right way to go either. Yes, it will return either 0 - false or 1 - true, but then what do you do with that?
A better way to compare the relative equality or inequality of two values is to use IfCondition.
Code:
IfCondition=MeasureSystemTimerOld <> MeasureSystemTimerCurrIfTrueAction=[!Log "True!"]IfFalseAction=[!Log "False!"]I don't ever recommend IfAction at all. It's just too limited due to there being no "false" trigger. IfAction is more or less deprecated by the addition of IfCondition.
Using IfAction(s) is ok I guess, but in this case, more complicated than it needs to be. You would pairs of each of IfEqualValue/IfEqualAction, IfAboveValue/IfAboveAction, and IfBelowValue/IfBelowAction to get to the vasty simpler IfCondition/IfTrueAction/IfFalseAction.
Statistics: Posted by jsmorley — 34 minutes ago