Difference between revisions of "Event Keywords"
Jump to navigation
Jump to search
(→IO) |
(→IO) |
||
| Line 54: | Line 54: | ||
* name - the data point name of the input or output port. According to the type of server, the format changes but it generally appears as server name, as declared with the ioServers parameter in hsyco.ini, followed by a dot and the input/output port name. See the Application Notes for more information. | * name - the data point name of the input or output port. According to the type of server, the format changes but it generally appears as server name, as declared with the ioServers parameter in hsyco.ini, followed by a dot and the input/output port name. See the Application Notes for more information. | ||
| − | |||
Revision as of 17:46, 4 February 2014
An event is defined as a keyword that identifies the event type, usually followed by one or more parameters and conditional operators. Every keyword uses a specific syntax that interprets parameters according to its own rules.
Contents
System Events
DAY
HAACTIVE
HSYCOSTART
NIGHT
POWER
PROGRAMTIMER
SUNAZIMUTH
SUNELEVATION
TIME
Cameras
CAMERA
CAMERACOMMAND
CAMERAVIEW
DMX
DMX
DMXSTART
Infrared Control
IR
I/O Servers
IO
Triggered by a status change of any data port of an I/O server.
| Event | State | Description |
| IO name | transient | any change of an I/O variable |
| IO name = value IO name > value |
stable | the value is equal, greater, greater or equal, less, less or equal to the given value.
|
The names and values of the I/O variables are specifically related to the type of I/O server. Values can be numeric or strings.
Parameters:
- name - the data point name of the input or output port. According to the type of server, the format changes but it generally appears as server name, as declared with the ioServers parameter in hsyco.ini, followed by a dot and the input/output port name. See the Application Notes for more information.
Examples:
IO tempmeter.indoor > 25.5 IO contacts.c1 = 1
