Custom Gpi Output Script - Imagine Selenio X100 Installation And Operation Manual

90
Selenio X100
Installation and Operation Manual

Custom GPI Output Script

<statement> ::= IF <condition> THEN <assignment> { <assignment> }
<condition> ::= <comparison> { <logic op> <comparison> }
<comparison> ::= GPIx <comparison op> y
Where x is in the range of [0, 7], y could be 0 or 1
<assignment> ::= PARAM[x] = y
Where x is the CCSP ID of a device parameter, y is a value for that parameter. At this time,
only integer and enum type of parameter assignments are supported. String type parameter
assignment is not supported.
<comparison op> ::= == | > | < | >= | <= | !=
<logic op> ::= && | ||
Comparisons can be ANDed together using &&, and then can be ORed together using ||.
The AND operation always has precedence over the OR operation when AND and OR both
exist in a condition.
To enable a custom GPI input script, set the direction of the specific pin in the select GPI
Output To Edit parameter (GPI and Rules Engine > GPI > GPI Output) and then set the
Event parameter to Custom GPI Output Script.
Enter your script into the GPI Output Script (Part I) field. The parameter allows a
maximum of 251 characters to be entered. If additional script space is needed, use the
Custom Output Script (Part II to IV) parameter. GPI Output Script Status reports the
parsing and active status of the script. If a syntax error is detected when a new script is
entered, this parameter will report Error: x message. The variable x is an index number
starting from the beginning of the script to indicate around which character the script
parser first encounters a syntax error. Custom GPI Output Level Status displays current
custom GPI output pin level information. From left to right, the symbols indicate the level
status of GPI ping 0 to 7, with 1 representing a high, 0 representing a low, and
representing Not Valid—which means the pin is assigned to the input direction, or
assigned to an event that's not custom GPI output script.
GPI output scripts are made up of one or multiple statements. Each statement consists of
one condition and one or multiple assignments. During device operation, if the condition in
a statement becomes true, the assignments in the statement will take effect.
<script> ::= <statement> { <statement> }
<statement> ::= IF <condition> THEN <assignment> { <assignment> }
<condition> ::= <comparison> { <logic op> <comparison> }
<comparison> ::= PARAM[x] <comparison op> y
Where x is the CCSP ID of a device parameter, y is a value for that parameter. The device
parameter could be one of three types: integer, enum, string. Depending on the parameter
type, y could take different format:
-