Equation Troubleshooting Tips - Emerson E2 Einstein User Manual

Flexible combiner programming
Hide thumbs Also See for E2 Einstein:
Table of Contents

Advertisement

Message
Mismatch()
Mismatched parenthesis
Missing()
A function that requires arguments in parenthesis
does not have parenthesis.
Missing Arg
A function does not have enough arguments.
Bad Type
A function name or operator is incorrectly used or
spelled, or a type mismatch or typographical error
has occurred in one or more arguments.
Bad Syntax
A function has too many arguments, or there is
some other problem with the equation formatting.
Divide by 0
Based on the current values of all inputs used in
this equation, a number is being divided by zero,
thus giving an invalid result.
Bad Result
Based on the current values of all inputs used in
this equation, the result is not a real number.
Bad Value
A value passed to a function is incorrect for that
function.
Table 3-1
- Equation Errors
3.1.1
Equation Troubleshooting
Tips
Test Your Equations
Especially if an equation you are using is complex,
validate the equation is working as you intended it by con-
trolling the input values being fed into the equation.
The easiest way to do that is to override inputs from
the Flex Combiner Status screen and watch what happens
3-2
E2 User's Manual Supplement: Flexible Combiner
Description
Resolution
Verify that each open parenthesis "(" has a corresponding
close parenthesis.
Example: ((AI3+7)*2 should be ((AI3+7)*2).
Verify if a function needs parenthesis that they are present and
correctly paired: for example, SIN(PI) is correct, not SIN PI
or SIN (PI. This will also occur if you used a function that
requires no arguments and did not include the parenthesis:
TIME() is correct, not TIME.
Verify the function has all the arguments they require, and that
each argument is separated by a comma. CUTIN-
OUT(AI1,60,100) will return a Missing Arg error (no between
argument).
Check the equation carefully and make sure all input and out-
put variable names and function names are spelled correctly.
Bad Type can also occur when a type suffix is misspelled:
AI1+38F is a Bad Type error because there is no F type suffix
(AI1+38DDF is correct).
This can also be caused by incorrect operators: DI1&DI7 is
wrong; DI1&&DI7 is correct.
Check the arguments for each function and make sure there
are exactly the number required, separated by commas and
properly closed in parenthesis. If using a function that takes no
arguments, verify the parenthesis after the function name have
nothing between them: NEWMINUTE(TIME()) is incorrect;
NEWMINUTE() is correct.
This might occur if you are using an input as a divisor. For
example, DI1/DI2 would be just fine as long as DI2 is ON
(1.0); however, when DI2 is 0.0, the result is DI1/0.0, which is
invalid. Avoid creating equations that use inputs as divisors.
This might occur if using an input in a function that, depend-
ing upon the value of the input, yields an imaginary number.
SQRT(AI1) would be a Bad Result error when AI1 is negative
because the result is an imaginary number; also ASIN(AI2)
would give a Bad Result error if AI2 was greater than 1 or less
than -1.
If using inputs as arguments, verify the values being passed
from these inputs are valid values the function can use as argu-
ments.
to the outputs.
• On the Flex Combiner Status screen, highlight the
input value with the arrow keys.
026-1620 Rev 3 06-JAN-2011

Advertisement

Table of Contents
loading

Table of Contents