User manual

Triggers are used to configure the messages that can be sent out from the dCine to external systems,

such as a lighting or screen masking/curtain system. Once configured by support engineers, many

of these triggers (e.g. those associated with auditorium control, audio processor control, and

projector control) will appear in the automation section of the GUI.

A typical example of a trigger configuration has been set out below.

<CueOut>Serial %6f%07%05%47%20%83%ff</CueOut>

<Proj>

<Include>PJLink.xml</Include>

</Proj>

<Audio>

<Include>Pioneer.xml</Include>

</Audio>

<Off>Device 00 Pulse Pin:0</Off>

<Prg1>Device 00 Pulse Pin:1</Prg1>

<Prg2>Device 00 Pulse Pin:2</Prg2>

<Up>Device 00 Pulse Pin:3</Up>

<Cleaning>Device 00 Pulse Pin:4</Cleaning>

</Lights>

<Door>

<Open>Device 00 Pulse Pin:5</Open>

<Close>Device 00 Pulse Pin:6</Close>

</Door>

<Open>Device 00 Pulse Pin:7</Open>

<Close>Device 00 Pulse Pin:8</Close>

</Curtains>

<Scope>Device 00 Pulse Pin:9</Scope>

<Wide>Device 00 Pulse Pin:10</Wide>

</Masking>

</Trigger>

Trigger syntaxEach trigger can be defined using the following process:

(i)

The following entry defines a trigger that will not show up on the GUI interface with a button as it

is not defined within a <DeviceNameToTrigger> tag. This named trigger is still accessible

from the automation programming interface and will show up in the full trigger list..

<TriggerName>MessageChannel Message</TriggerName>

(ii)

The following code defines a device to which the dCine can send a trigger. That device is then

configured to have a number of possible states as defined within the

<DeviceNameToTrigger> tag. The DeviceNameToTrigger name will show up on the GUI