Advanced Programming
lighting component is represented by the first parameter on each line, followed by a single space, and then the address.
Here is an example of what the data in this file may look like:
4[1:4:1:1:1]
3[1:4:1:1:2]
21:[1:4:1:1:1];[1:4:1:1:2]
1[1]
This configuration file is read only at reboot of the AMX system.
The Duet communication module also writes a file for each scene configured through the AMX system. Each scene file is called <vdev>_Scene_X.txt, where X is the scene number and <vdev> is your virtual device number. The data stored in this file matches the syntax of the FADEDIM command documented in the H48 protocol document except that if several dimmer addresses are specified on the same line, they must be separated by semicolons (;) instead of commas (,). A maximum of up to an including 10 addresses can be specified per line. Each line must end with a carriage return and line feed and there must be a single space after each comma. It is recommended that you do not manually edit these files. It is recommended that you copy your scene configuration files, once you have configured the scenes, as a backup. Here is an example of what the data in these files may look like:
FADEDIM, 100, 00:00:05, 00:00:03, [1:4:1:1:1]
FADEDIM, 95, 00:01:08, 00:00:03, [1:4:1:1:2]
FADEDIM, 55, 00:00:28, 00:00:02, [1:4:1:1:3];[1:4:1:1:4];[1:4:1:1:5]
The sample user interface and touch panel file are provided as an example only and are not to be used as is in an actual installation. This sample code assumes certain things, documented in the sample source code, therefore code changes must be made in order to meet your specific installation requirements. This sample code should be used as a guide/code example for developing your own user interface.
The Duet communication module will report the time every 1 minute as well as the date.
If the AMX system is rebooted while connected and logged in to the H48, the TCP/IP link may need to timeout before another connection can be
35 |
| |
|
|
|