User manual

Here we define events, giving them a name and describing what will trigger that event. As an

example;

<SerialStart>Serial %7e%07%05%47%02%01%ff</SerialStart>

<SocketStart>Socket Start</SocketStart>

<IOstart>Device 00 Pin:21 High</IOstart>

</Events>

Support engineers define the names of events under the <Events> option. Such events might be

defined as follows;

<UserDefined>InputType</UserDefined>

<EventSerial>Serial URLEncodedString</EventSerial>

<EventIP>IP URLEncodedString</EventSerial>

<EventKeyboard>Keyboard URLEncodedString</EventKeyboard>

The <UserDefined> configuration option allows support engineers to specify which input the dCine

will monitor and the string pattern that will fire the relevant event. In the example immediately

above, we are monitoring for three different types of events.

1. <SerialStart>Serial %7e%07%05%47%02%01%ff</SerialStart> : This

configured event monitors for a string pattern of non printable Hex characters on the serial

port as configured in the <Serial> option above. For the current example we expect non-

printable hex characters. The support engineer specifies these characters using the URL

encoded representations of the characters; that is, a “%” symbol is used followed by the Hex

value representing the character as shown in an ascii table (e.g. “%7e” is a hex character

with the value 7e).

2. <SocketStart>Socket Start</SocketStart> : This configured event listens for

the string pattern “start” coming into the socket as configured in the <Socket> option

above.

3. <IOstart>Device 00 Pin:21 High</IOstart> : This configured event

monitors terminal 21 on an IO-Contact-Closure device to see if it moves from low to high,

for example in circumstances where a pushed button or a Master automation system send a

message to the dCine.

Once Events have been configured, there are two methods to configure what actions will arise from

these events;

1. Set up a <Macro> with the same name as the event you wish to trigger your Macro. When