Alcorn Mcbride V+ series, User Manual

Page: 245 / 276

15-9 Appendix A
– Adding User-Defined Serial Protocols
Ap
p
end
ice
s
A
place, instead of just removing the 'Q', the compiler replaces it with the optional
byte h41 ( "A" ). For example, the parameter equipment would result in the
string equipment being put into the compiler buffer.
Since validation of a parameter is key to compiling what is truly desired, several
different types of validation can be performed on a parameter. To facilitate this,
allowing different types of data to validate is possible using the OR operator |,
and forcing multiple validations on the same data is possible using the AND
operator &.
This is an example of the OR operator. In this case, if either an output or a flag
was found as parameter 1 the validation for this event passes:
param1=output|flag,"A valid Output or Flag was not found as parameter 1"
Whichever type of validation succeeds, that is the validation type that is used to
process the parameter, and to put the data into the compilers buffer. If multiple
validations would pass, the first one to pass is the one that's used.
This is an example of the AND operator. If both validations pass, the validation
for the overall event passes. Both validation processes are performed, in order,
from left to right. In this case, the parameter must contain the letter 'R" and the
data that remains after the letter "R" is removed must be a byte in size, no
smaller than 1 and no larger than 16.
param2=contains(r) & byte(1,16), "No valid reproducer card
number was found as parameter 2"
OR and AND operators can be combined. There can be up to 5 OR operators.
For each OR operator, there can be up to 3 AND operators. The following is a
generic example:
paramX= validationA1 & validationA2 & validationA3 |
validationB1 & validateionB2 & validationB3 |
validationC1 & validationC2 & validationC3, "error message"
The first OR operator that passes validation is used. In order for OR validation
B to pass, validationB1 , validationB2 , and validationB3 all have to pass, and
remember that validationB1 uses the actual parameter as data, validationB2 uses
the result of validationB1 as data, and validationB3 uses the result of
validationB2 as data. The result, what is put into the compiler buffer, would be
the result of validationB3 .
The
Message
field specifies what bytes are sent out the port for this event.
The message can range from very easy to very complex. Our PlayUntil event
has a very simple message field, but still illustrates two of the three different
concepts that can help make up the
message field. Possible types of data that
can be put into a
message
field are literal data, parameters , and functions .
Literal data are bytes that are specified in the message field directly, and can be
a decimal number, hexadecimal number, or string.