User manual
<Variables>
Variables are used to help configure automation scripting:
 <Variables>
 <PioneerSerial>COM3,9600,N,8,1</PioneerSerial>
 <AP20>IP:10.30.100.165:14500</AP20>
 <JNIOR>IP:10.30.100.14:9200</JNIOR>
 </Variables>
Variables are used in the XML configuration files to help set up device control.  For example, in the 
above example, the variable name “AP20” is defined as “IP:10.30.100.165:14500”.   Any 
appearance  of  the  variable name in  the  form  of  ${AP20}  in an XML configuration  file,  will  be 
replaced with the string: “IP:10.30.100.165:14500”
In order to  demonstrate  this for readers,  the  following  is  taken  from  the  Datasat_AP20.xml 
module used as an <Include> for controlling the Datasat AP20 cinema audio processor:
 <Power>
 <On>${AP20} PO%0d</On>
 <Off>${AP20} PF%0d</off>
 </Power>
As the variable ${AP20} is defined as “IP:10.30.100.165:14500”, the dCine will actually 
see the automation command string as:
 <Power>
 <On>IP:10.30.100.165:14500 PO%0d</On>
 <Off>IP:10.30.100.165:14500 PF%0d</off>
 </Power>
This allows  the Datasat_AP20.xml module to refer to  a variable for  the communications 
address (i.e. the IP address and port number that the dCine will connect to). The use of variables has 
a number of advantages. First, it enables support engineers to change all the automation commands 
by modifying just that single variable. Further, it allows for the implementation of a control module 
by using the <Include> option for that module. 
Support engineers are encouraged to try and utilise the modules as are. However the modules can be 
customised to suit. 
Copyright©2012 digitAll Pty Ltd 23










