Phoenix |
|
Phoenix |
|
Phoenix |
|
Phoenix |
|
Loading...
The Phoenix Device in the Configuration dialog allows to easily monitor and remote control different functions of a Christie Phoenix controller. Note that the device is only available in the licensed Widget Designer edition, not the Free version.
To add a Phoenix device, open the Devices menu and select "Christie > Phoenix > Create Phoenix". This opens the Configuration dialog. Alternatively, you can add a new device in the Configuration dialog with the "+" button.
On the right side, you see several options:
The Type informs you about the type of device or connection.
The Groups lists the groups to which this device belongs.
The Name is the unique identifier for this Phoenix object in WD and the general rules for naming objects apply here as well: only letters, numbers and underscores are allowed; the first symbol must be a letter.
It is possible to change the default name to a more descriptive one. When scripting, enter this Name to access available members or use the Project object and device Type instead; examples are shown further down.
The Id offers an alternative way to address the device when scripting.
The "Enable" check box is selected by default. On the left side, you should later see that the icon in front of your Phoenix device is a filled blue circle. An empty blue circle indicates an enabled device where the IP address is not available. A filled gray circle indicates a disabled device.
Now, please enter the IP address of the Phoenix controller. Click the "Apply" button to save any changes done here. The shortcut [Ctrl + Enter] can also be used to apply changes.
Once the settings are applied, the dialog can be closed. The newly created device will also be added to the Devices menu > Christie > Phoenix and can be opened from here or with the Devices menu > Configuration.
As soon as a device is created, it can be addressed via scripting to perform actions on the device as well as retrieve information from it.
To send commands to the device, create a CustomScript button or anything with a scripting field. Enter the device's identifier name into the script field (per default that is "Christie_Phoenix1") and Script Assist will offer a list of all Phoenix Members.
Some of them are commands to perform actions on the device, e.g. applying a layout:
Christie_Phoenix1.ApplyLayout("FullView")
You can also retrieve specific values via scripting in the same way as from other widgets (e.g. a Fader value):
vlist = Christie_Phoenix1.LayoutNames
This member returns all layout names as a list that can be displayed in the Debug Logger or assigned to a variable, DropDown List, etc.
As an alternative to explicitly naming the device, the "Project" object can be used. Choose the device type and address the device by entering its ID or name. Script Assist then offers you the same list of members. This is the alternative for the first example from above:
Project.Christie_Phoenix(1).ApplyLayout("FullView")
Substituting the ID with a dynamic variable allows automation. Actions can be performed on many connections of the same type simultaneously, e.g. by using for-loops:
For i = 1 to 10 {
Project.Christie_Phoenix(i).ApplyLayout("FullView")
}
The chapter "Project and Context Member" shows more examples with for-loops and if-clauses; of course, normal variables can also be used.
The Phoenix tutorial shows how to build a small interface to interact with a Phoenix system and uses the most important commands and Event Listeners.
Event Listeners can be added in the Configuration dialog and provide a simple way of listening to triggers from connected devices.
Please see the chapter Event Listener and Group Event Listener for a detailed description of its functionality and Phoenix Events for an overview (with examples and description) over the events raised by a Phoenix device.