Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Reference Manual
For:
Acrobat G6, Nomad, Illusionist,
PC Wing, Solo G3, Solo G3W & Preset Station
Notices
About this document
This user’s manual has a two-fold purpose: to provide background information about the proper use
of the system, and to act as a guide to the functionality of the control system. It is intended to
supplement, not replace, authorised classroom and hands-on training.
Details of operation may vary due to differences in mechanical or electrical implementation at your
venue. Local safety regulations may require further training and operating procedures to those
discussed in this document for proper operation of the equipment.
Copyright Notice
This document contains material that is proprietary to Stage Technologies Ltd. This information is
provided on the understanding that it is used solely for the purpose of installing and maintaining the
equipment described, and that `it will not be revealed to third parties or otherwise disposed of
without the prior written consent of Stage Technologies Ltd.
Copyright for all design, software, electronic circuits, drawings and the text of this manual remains
with Stage Technologies Ltd. The publication of any part of parts thereof in any form, by any
method, for any purpose is prohibited without prior written consent of the copyright holder.
Further copies may be obtained from Stage Technologies Ltd on request.
Table of Contents
Notices ..................................................................................................................................................... i
Table of Contents .................................................................................................................................... ii
1 Introduction .................................................................................................................................... 6
1.1 The Manual ............................................................................................................................ 6
1.2 eChameleon Features Overview ............................................................................................ 6
1.2 eChameleon Features Overview ............................................................................................ 7
1.3 System Overview..................................................................................................................... 9
1.3.1 Control Desks .................................................................................................................. 10
1.3.2 Server .............................................................................................................................. 11
1.3.3 Database.......................................................................................................................... 11
1.3.4 Nodes .............................................................................................................................. 11
1.3.5 Networks ......................................................................................................................... 11
1.3.6 Control racks ................................................................................................................... 12
1.3.7 Mechanics and power transmission................................................................................ 12
1.4 Definitions ..................................................................................................................................... 13
1.4.1 Axis .................................................................................................................................. 13
1.4.2 Playback (PB) ................................................................................................................... 13
1.4.3 Deads ............................................................................................................................... 13
1.4.4 Groups ............................................................................................................................. 13
1.4.5 Action .............................................................................................................................. 13
1.4.6 State ................................................................................................................................ 14
1.4.7 Macro .............................................................................................................................. 14
1.4.8 Control points.................................................................................................................. 14
1.4.9 Control Graph .................................................................................................................. 14
1.5 The Control Desk ................................................................................................................... 15
1.5.1 Powering up .................................................................................................................... 15
1.5.2 Keypad ............................................................................................................................. 16
1.5.3 Button functions.............................................................................................................. 17
1.5.4 Playback........................................................................................................................... 17
1.5.5 Dead Man’s Handle ......................................................................................................... 17
1.5.6 Shortcut Panel ................................................................................................................. 18
1.5.7 eChameleon Launcher .................................................................................................... 18
2 Features and Functionality ........................................................................................................... 20
2.1 Playbacks ............................................................................................................................... 20
2.1.1 Joystick mode .................................................................................................................. 21
2.1.2 Speed mode .................................................................................................................... 21
2.1.3 Reverse mode.................................................................................................................. 22
2.1.4 Speed Override................................................................................................................ 22
2.1.5 Playback Stealing ............................................................................................................. 23
2.2 Axes ....................................................................................................................................... 24
2.3 Groups ................................................................................................................................... 25
2.3.1 Free Group ...................................................................................................................... 25
2.3.2 Safe Group....................................................................................................................... 25
2.3.3 Locked Group .................................................................................................................. 25
2.3.4 Sculptor Group ................................................................................................................ 26
2.3.5 On Demand Groups ......................................................................................................... 26
2.4 Deads .................................................................................................................................... 27
2.4.1 Recording Deads ............................................................................................................. 27
2.5 Move Parameters.................................................................................................................. 29
2.5.1 Target, Move & Dead ...................................................................................................... 29
1 Introduction
eChameleon is the common software platform across all Stage Technologies control consoles,
offering unrivalled ease of use, power and flexibility. It is the next generation of Chameleon
software, simplifying the tried and tested concepts of its predecessors whilst enhancing the deeper
functionality aimed at running the most demanding of performances.
The software is easy to learn and fast to operate, making eChameleon suitable for all scales of
automation systems, from small school theatres to the largest of casino shows.
eChameleon offers real-time, 3D and tabular views of automation systems and can be used with
touch screen operation on the Nomad control console. The package also includes a full, logical
command line interface for rapid programming. eChameleon offers practically inexhaustible storage
and allows multiple consoles to operate together seamlessly. It also integrates with our Connect
service for continuous off-site backups of show data.
As a security enhancement, eChameleon runs on Windows Embedded Standard, which means that
the user is only given access to the eChameleon launcher. The user is only allowed access to the
Stage Technologies software, thereby configuring the console in a safe and simple manner.
• Introduction
A general description of the man parts of a Stage Technologies Automation system, and
explanation of the broad philosophies and nomenclature utilised within Stage Technologies
eChameleon and control desks.
NB: For a detailed description of system elements please refer to the individual hardware
manuals.
• Features and Functionality
Detailed coverage of concepts which are shared by all elements within the Stage
Technologies eChameleon Suite, description of specific features, and the best practices
available to the user.
• The Software
Specific instructions for each element of the eChameleon Suite of software.
The examples show the result of a command line input without defining each process to achieve this
input. In some cases abbreviations are used such as DMH for Dead Man’s Handle or PB for Playback;
these abbreviations may be explained throughout the manual.
For more information on command line inputs and Keypad functions; please refer to the
“Keypad functions” section of this manual.
A Stage Technologies automation system will contain a varying number of parts and peripherals. The
actual layout of the system and constituent parts will vary according to the application; however the
basic infrastructure will remain the same:
Stage Technologies utilise a modularised control system with standardised components and a
selection of control desks, control and processing units and hardware to suit the requirements of the
application.
A standard system will comprise one or more control desks, mobile panels or wall mounted control
panels, an Emergency stop and safety system, a range of control gear suitable for the application
(containing intelligent drives and communication nodes), an industrial standard network and a range
of mechanical solutions (that may include winches, hydraulics and any other driven systems).
For example: a west end show may expect a high level operator to deal with a great many axis
simultaneously and would not normally expect to re-position the desk or an opera house may
require several desks running only a few axis, but with the ability to easily re-position the desk or a
lower level operator may be asked just to fly in a projection screen in an arts centre or cruise ship
and as such would prefer an immediate wall mount solution rather than a fully functional control
desk.
Acrobat G6: Latest generation of Acrobat desk, with unique dual redundancy, dual
widescreens, instant shortcut panel and 6 playbacks and enhanced
functionality. This desk is designed primarily for high productivity with
flexible operation and programming.
Nomad: The perfect solution for a multi-operator or large multi venue application.
The desk is designed to be portable requiring only a single connection to
any control point throughout the installation and features low weight and
brief case size and a user friendly touch screen.
Illusionist: The economical solution to control, featuring the full eChameleon package,
rack mount options, 3 playbacks and is offered as a perfect solution to the
smaller installation.
Solo and Solo G3W: Solo is a handheld, multi axis controller. It can be used as the primary
venue controller or a part of an integrated solution with other control
desks. Solo runs a version of eChameleon feature many of the functions of
the full software suite. Solo G3 is available as a wired or wireless (G3W)
option using an industrial Ethernet radio link.
Preset Station: The Preset Station is a robust touch screen offering simplistic control for
lower level operation. It is easily configured and restricted and can be an
invaluable addition to a system or used as the primary operational option.
PC Wing: The PC wing is a USB interface for eChameleon running on a PC. The PC
wing can provide invaluable support for training and offline program
applications.
NB: For more information on Stage Technologies’ control desks please refer to the Control
Desks appendix at the back of this manual and the individual data sheets and
hardware manuals supplied by stage Technologies or available on our web-site.
1.3.2 Server
A server is generally added to a multi-desk or multiple operator system or a system requiring a large
amount of data backup or archiving. A server will always be present on installations featuring a Solo
G3.
The server holds the current database and any archives created and provides a networked
centralised data source for all control desks.
1.3.3 Database
The eChameleon Suite utilises a centralised System database, held on a server for multiple desk
applications, or stored locally in single desk applications. The database contains all information
pertinent to all axis parameters, defaults and higher level commissioning options. The database
holds any number of shows and all pertinent information relating to those shows including all user
recorded show information including states, actions, views, soft limits etc.
In a multiple desk application, the System database will be held securely on the server and accessed
simultaneously every control desk or mobile controller. This ensures that no conflicts can occur
between ownership of axis and data update refresh (i.e. an axis may only be controlled by one desk
at a time and any changes made to the database from any control platform will be reflected at each
and every desk).
A duplicate of the System database is also held locally on each desk, which allows work to continue
from the desk if for any reason communication to the server is unavailable, however in a multi-desk
environment this should be considered an emergency situation only suitable for running tried and
tested sequences, as the safety features provided by a shared database are no longer available.
eChameleon Monitor also uses an Events database for logging all user operations and events, and a
Telemetry database for storing of system status information for detailed diagnosis.
1.3.4 Nodes
A node is the centralised communications point for a system of axis.
Stage Technologies eChameleon defines five types of nodes:
• Normal: standard system
• Radio: system with radio data
• F:light: This node provides communication for the Stage Technologies F:light automation to
moving light integration system
• Monitoring : a node external from the main system used for SIL 3 applications
• Legacy: A node allowing integration of older hardware systems
1.3.5 Networks
Stage Technologies offers a selection of network types, additional to the standard Ethernet
communications. These network types can be used in combination and will be assigned during
commissioning, as appropriate for the installation.
The MCR (Motion control rack) will contain the network Nodes and Hubs and often any integrated
safety solutions, including system level PLCs and often also include the server.
The MCC (Motor control cabinet) will usually contain the intelligent drives, networking to the MCR,
axis level PLCS and all applicable power solutions.
Stage Technologies control solutions may be centralised or localised (i.e. centralised within a control
“rack room” or localised to the winches or moving axis)
1.4 Definitions
This section briefly describes the names and definitions used within this document to describe the
functions and elements within the Stage Technologies system:
1.4.1 Axis
Stage Technologies uses the term AXIS to refer to any individually controlled element of motion. A
single axis might be a single winch, hydraulic ram, I/O axis. A piece of scenery or lift may, for
example, use a single axis or many axes to create its movement. Axes may be grouped together in
several differing ways to create groups appropriate to their usage.
A Playback has one or more buttons capable of Starting and Stopping the axes loaded on it, and a
speed override, which allows cues to be executed at 0 – 200% of programmed speed.
1.4.3 Deads
(Also marks or trims (US)) - A designated height for a piece of scenery or bar; a label or marker for a
physical position or target. Manual flymen use a Dead on a rope as an indication of the position of a
scenic piece i.e. all the way in (in view) or out (out of view) or at a mid point. For manual operation,
this mark would traditionally be a cotton tape wound through the strands of the rope but this has
been replaced more recently with PVC tape or similar. Automation operators label Deads with a
number and/or colour system such as ‘Dead 1’.
1.4.4 Groups
Many theatrical effects in modern productions require the synchronised movement of multiple axes,
and in many cases these axes are used together to lift a single, large piece of scenery. To address
these issues Stage technologies use GROUPS.
eChameleon offers a variety of permanent and temporary group types including free, safe and
locked. Each grouping will consist of a number of axes that are required to be addressed or act as
one entity.
Grouping within eChameleon is dynamic, meaning that multiple group definitions may be created
and held within a show and each axis maybe a member of several groups simultaneously.
1.4.5 Action
An ACTION is a way to record anything that can be achieved on a single playback and store it for later
recall to any other playback.
Actions may be simple building blocks with which to plot your show and design States. They can
equally be used to store commonly-used moves, groups of moves or complex moves that would
normally require a long command line.
1.4.6 State
eChameleon uses the nomenclature STATE for what is often referred to as CUES. Stage Technologies
use the terminology of states to describe a page of pre-recorded axis move parameters. eChameleon
makes use of multiple playbacks, giving the user the choice to fire one or multiple playbacks
concurrently. One page could therefore contain one or multiple cue points.
A state therefore contains all move data relating to any axis assigned to any playback, also any
screen layouts (VIEWS) and notes associated with that state.
1.4.7 Macro
A Macro is a means of controlling a System Output, such as hydraulic pumps, or a kabuki drop. A
Macro can be loaded onto a playback in the same way as an axis, and recorded into States, and will
then execute when the playback Start button is pressed. A single output could be controlled by
multiple Macros, for different operations including Activate, Deactivate and Pulse.
eChameleon provides a soft-control point ID for instances when a hardware control point ID is
unavailable.
Nomad
Once connected to a Control Point the power button on the left side of the desk will flash green
rapidly for 5 seconds, and then begin to flash slowly. Push the button once the slow flashing begins
to power up the desk. The Nomad must always be shut down correctly from within the software.
Illusionist
The illusionist desk has a single main power rocker switch at the rear of the desk. Switch this to ON
to power up the desk. The Illusionist must always be shut down correctly from within the software.
When the desk has powered down, this rocker switch should be manually switched to the OFF
position. The user must wait for approximately 30 seconds after switching to OFF before attempting
to restart.
Solo G3
The Solo G3 is self-powered from a control point and has no power switch. It does not have a shut
down process; however the software should always be exited correctly before unplugging the Solo
G3.
Solo G3W
TBC
Preset Station
The Preset Station has a momentary power switch on the front of the panel, which should be
pressed once to power up the device. The Preset Station must always be shut down correction from
within the software.
1.5.2 Keypad
Each control desk has a keypad for command line entry and functionality. The keypad can be split
into several sections for ease of description:
Resource Keys
Toggles
(cyclic)
The top text on each button is the result of a toggle of the button.
In a few cases the buttons also have a push and hold function.
1.5.4 Playback
The Playback includes the playback colour selector, playback eBelt (used for varying plotted velocity
percentages) and the Start/Stop button.
Each type of desk has a differing number of playbacks. The Acrobat∙G6 has 6 playbacks, Nomad 5,
Illusionist 3 playbacks etc. The playbacks are colour coded for simplicity and their percentage status
is displayed within the E-Belt with LEDs and also onscreen in the playbacks section.
E Belts
Start/Stop Buttons
The Nomad, Illusionist and other Stage Technologies control platforms use an “On screen” version of
these buttons via the Shortcut pages.
The Launcher (home screen) contains shortcuts for eChameleon, General Settings, eChameleon
Manager, eChameleon Monitor and Archives.
Settings &
Archives
Control Panel
NB: for detail on the functions and use of Manager, Monitor, Archives and Settings please
refer to the associated appendix items and the end of this document.
eChameleon
eChameleon provides the main user interface for all plotting and movement functionality
of the desk. This is the main user interface and will provide all tools and links for day to
day operation.
eChameleon Manager
eChameleon Manager provides the user and commissioning engineers with tools to set up
the “front end” of the system. This tool provides database management and allows the
user to set up or modify system level axis, IO, Nodes, Control points, roles, users and
restrictions and administrative tools including database scheduled archiving. eChameleon manager is
pin code protected.
eChameleon Monitor
eChameleon Monitor displays a live and historical system status, displaying real time axis
telemetry and historical timelines of system errors and user inputs. This auditing software
allows for filtering for specific historical events in several methods.
Archives
The Archives button allows quick shortcut buttons for archiving and retrieving system
databases.
Settings
The settings button supplies quick selections for fundamental system set up options. Most
of these options are self-configuring. The settings include: Display, Network, System
Options and general system information.
NB: for a detailed description of commands and command line entries, please refer to
the “Command line reference” section later in this manual.
2.1 Playbacks
• A Playback is a method of gaining control of one or more axes. Axes, Groups and Actions
may be loaded onto a Playback, which then provides the means to Start and Stop the axes,
and a “speed override” capability for varying the plotted velocity by percentage.
• Each Playback is colour coded, for selection and recognition – depending on type of control
desk, a subset of the 6 possible Playbacks may be provided, coloured Red, Blue, Yellow,
Green, Orange and Purple.
• Playbacks can generally be considered to have a Select button, Start button and Stop button
irrespective of type of control desk.
Joystick mode: Allows the User to “Jog” an axis or group of axis between pre-defined software limits.
The playback slider, in this case, determines “jog” direction and percentage of positive or negative
velocity.
Speed mode: Speed mode is used for all moves where a target is defined. In this case the playback
does not need to determine direction and therefore the playback slider becomes a speed override
function from 0 to 200% of plotted speed.
• The currently selected playback’s mode may be cycled between Speed and Joystick by
pressing the PB Mode keypad button, or by pressing the playback select button. Toggling
between modes will not affect the Speed mode moves programmed, allowing the user to
switch into Joystick mode to jog an axis if necessary, and then switch back to run the cue.
• A playback will automatically change mode from Joystick to Speed mode if a target is
assigned to an axis. If Speed mode is selected without a target given, the current position
will be taken as the target.
[Axis 1 Enter]
[Axis number Target number Enter] or [Axis number Dead number Enter] etc.
Naturally most pre-recorded states and actions will have playbacks in speed mode.
If no speeds, accelerations or decelerations have been defined then the axis will utilise the defaults
preset within the database.
NB: In speed mode zero percent is at the base of the E-Belt’s travel (as no negative percentage is
required)
In eChameleon, Reverse is the push and hold function of the PBMode key and affects the current
playback.
NB: This function is only designed to provide a quick re-set, it is not a “run backwards” function and
so there is the potential that axes could be given targets which would cause a collision, and it is the
Operator’s responsibility to ensure the moves generated are safe to execute
When a playback is in Speed mode, it will generally default to 100%, with a maximum of 200%. The
maximum will be automatically limited based on the maximum speeds of the axes on the playback,
such that the relationship between moves is always maintained, and maximum speeds are never
unintentionally exceeded.
When recording a State, Playback Start and Maximum Percentages may be specified:
Start Percentage
A playback start percentage is the percentage of plotted speed (that the playback loads at on each
given state. In most cases this will be 100% for “show running” and Zero% for “out of show” states
for safety.
Maximum Percentage
A maximum playback percentage is a percentage limitation on the override of a playback percentage
speed. If unspecified a playback may be overridden to either 200% of the plotted speed or the
maximum allowable axis speed if below 200%. Whilst the speed override can be a useful feature if a
cue is delayed and needs to be sped up to catch up with a sequence, there may be scenarios where it
is undesirable to ever exceed a specific percentage of plotted speed.
In order to steal an axis or group, select a new playback, and enter a selection only command (i.e.
Axis # Enter), and the axis will be transferred. If any other operation is applied on the same
command line, an error will be thrown reminding you that the axis is already on another playback.
2.2 Axes
Stage Technologies control systems can control a selection of different axis types; theses types are
defined within the database and can be a selection of Variable Speed, Fixed Speed, Non-Positioning
and Rotary.
The parameters relating to each type are customisable and defined within eChameleon Manager.
Axis maybe labelled with a name relevant to their current application. The Axis will have a name
associated to it from the initial database setup and the user may choose to retain this name or to
change it per show.
For example: a single show application will generally use the axis name set up in the database as the
name throughout its use (as this will generally be the only use of this axis), however a Repertory
house may use standardised labels (such as Bar 1, Bar 2) within the database and show specific
names throughout the shows.
2.3 Groups
Many of the major reasons for installing an automation system are realised by using Groups. Many
theatrical effects in modern productions require the synchronised movement of multiple axes, and in
many cases these axes are used together to lift a single, large piece of scenery. To address these and
other demands eChameleon utilises Group functionality.
In order to record a Group, the user must select more than one axes, and specify a Group number to
record as, such as:
This command will start to create a Group 1 using Axes 1 and 2 and will prompt the user for which
type of Group to create.
For more information about multiple axis selection; please refer to the Command
reference section of this manual.
eChameleon supports four primary types of group - Free, Safe, Locked and Sculptor which are
described below.
This command will only allow a Group to be deleted if it is not used in any States or Actions.
The members of the group have no inter-relationship, and the Group will only appear as single axes
once loaded.
A safe group is used for a group of axis that may need to move independently, but should all stop if
an error occurs.
A Locked Group is used to move multiple axes which are interconnected and are rigged such that
each axis must maintain the same position relative to the others in the group at all times. For
example, a heavy ceiling flown on 6 point hoists. As with safe groups, if one axis in the group faults,
all axes in the group will stop.
NB When a locked Group is created the User is presented with the options to “Rig” or
“Not Rig” the Group.
If the Group is rigged, then a warning is given to the User when the Grouping is
broken i.e. axis addressed separately.
Safe on Demand creates a temporary Safe Group of all axes on the playback, ensuring that if one axis
was to fault or error all axes will stop.
Locked on Demand creates a temporary Locked Group, with an arbitrary axis as master, ensuring
synchronisation between all axes on the playback based on the positions when the Locked on
Demand Group is loaded.
To remove the On Demand Group, either Clear Down the playback, or issue the On Demand
command again.
2.4 Deads
A “Dead” is a numerical label for a target.
Deads are commonly used for targets that are repeatedly used throughout a show i.e. IN Dead or
OUT Dead.
If a Dead is recorded into a selection of States, any subsequent change to that Dead will be reflected
throughout the plotted states.
The currently recorded Deads list for each axis may be views by query the axis.
1. Clicking the Query Tab, then clicking Axis, then clicking the query on the required axis
2. Right clicking the Axis number at the top of it’s grid and clicking Query
For more information about Query; please refer to the Query Tab section of this
manual
This command line will result in the current position of each axis on the currently selected
playback being recorded as the Dead number specified in the command line
The above command line will result in the current target of all axis held on the current
playback being recorded to the desired Dead number
Please refer to “Current Playback” and “Playback modes” for more information
The command line may also contain a text entry in order to label the Dead:
A Dead maybe recorded for a single or selection of axis or groups on a particular playback by
specifying the selection within command line:
[Axis1 + Axis2 + Group1 Target number Dead number Text “IN Dead” Record]
Reverse: Move directly back to the start position of the move that has just completed
Triggered: Any of the previous move types maybe triggered in a variety of ways
Sculptor: Move in a 1D, 2D or 3D path either along a plotted course or via joystick input
[Axis 1 Target 1000 Enter} would program a move to an absolute position of 1000mm
It should be noted that relative moves are only a means of programming an absolute target, once
the move is recorded then only the target is recorded, the fact that it was recorded as a move
relative is ignored. It should also be noted that in all cases the move will be verified as valid, before
the user can continue i.e. the move relative does not take the axis beyond its working limits.
A Dead (also known as Mark or Trim) allows the recording of absolute targets which may be used in
multiple states. A Dead has a target position, saved with an associated name and number, and is
unique to a single axis.
The benefit of using a Dead is that if the user wishes to change a target position in multiple states,
they can simply re-record the Dead position and it will be automatically changed in every state.
Speed is described in user units per second (millimetres, feet, inches etc.), and Time is always
displayed and entered in seconds.
A maximum speed for each axis will be configured in the database during commissioning and the
User will not be allowed to plot speeds above this maximum axis speed or above any User axis
restrictions that may be applied.
A default speed will also be configured for each axis during commissioning. This speed is nominated
as a generally safe speed and utilised by eChameleon if the User does not specify any other speeds.
Whilst eChameleon constantly displays “time left” (to complete the plotted move) for all axes under
control, it is often useful to plot moves over a time, rather than entering speeds for each axis. A
traditional scene change will often use many axis travelling in different planes, from differing
positions and starting at different times but all finishing at the same point in time.
When a Time command is entered the user is presented with several options of calculation:
• Current Position
• Previous Position (Either the last position that the axis moved to within the state list, or the
target of the preceding Multi-Target move)
To Time a move:
• Plot the final target for each axis (target, dead, move etc.).
• Plot any other move parameters (Accel, Decel, delay etc.)
• Time the move (i.e. Axis Time 20 Enter)
• Select the type of timing calculation from the presented options (from current position,
previous state position, with/without delay).
Timing will only be applied if the generated speed is within allowable limits. If this is not the case an
error will be thrown indicating the minimum achievable time.
Timings should always be applied as the final part of a command line – any changes to any other
move parameters subsequent to the timing calculation will result in an invalid speed for the altered
move.
It is also possible to convert to and from a Timed Move. By entering Axis # Time Enter, a move
programmed with Speed will be issued a Time command which matches the plotted speed.
Conversely, if a Time is no longer relevant to the control graph, then Axis # Speed Enter will remove
the Time parameter, but retain the same Speed.
NB: The speed and subsequent timing of an axis will never be automatically adjusted. When
loading a move programmed with time it will always run at the same Speed as when
programmed. If the current distance to travel makes the Time invalid, it will be displayed in Red.
Acceleration rate may be entered into the command line by pressing the Accel Key
Acceleration time may be entered into the command line by using the toggle function of the Accel
Key.
Deceleration rate may be entered into the command line by pressing the Decel Key
Deceleration time may be entered into the command line by using the toggle function of the Decel
Key.
Whilst both methods have merit in differing applications, it is often simpler to consider Accel, Decel
rates in times, especially when using an overall time for a cue.
If a time is used, then changes in the cue speed will not affect the general move shape (particularly
useful when using multiple joined axis i.e. bridals)
However, in some cases a basic rate of Accel or Decel is preferable, if for example, an axis is
mechanically designed to work at its optimum at a fixed rate of Accel, Decel.
2.5.5 Ramps
A standard move within eChameleon employs a
trapezoidal ramp shape.
In some applications this is not desirable, since it can lead to the sway or bounce of an axis, and as
such it is useful to apply and remove the acceleration or deceleration in a more gentle manner, with
what eChameleon calls a Ramp Shape.
The most extreme case is known as an S-Ramp, due to the speed graph resembling an S, with no
constant acceleration phase, however this can dramatically alter the ‘look’ of a move, and
sometimes more subtle correction is all that is required.
Ramps can be defined by the user in eChameleon Manager, although eChameleon offers 3 standard
Ramp Shapes:
• Ramp 1 - S-Ramp
• Ramp 2 - Intermediate
• Ramp 3 - Nearly Trapezoidal
When defining a Ramp Shape, the user must specify the percentage of time the axis should spend in
each of the regions shown below. The whole acceleration or deceleration phase must add up to
100%, ranging from the trapezoidal case where all are set to 0% and so 100% of the time is spent at
constant Accel through to a true S-Ramp which has 50% in each of regions 1 to 4, leaving no constant
acceleration phases.
This definability allows the user to create asymmetrical behaviour between Accel and Decel, and
even within each phase, and so some quite complex effects can be achieved if desired.
Ramps are can be particularly useful in situations with high inertia. The user should take care,
however that the use of a ramp does not mask an inherent mechanical problem. Equally a ramp can
become a problem if the axis has other mechanical issues, such as lost motion due to slack
counterweight assist lines. In this case the gentle part of the acceleration will be lost during the lost
motion and the full load will be hit with a greater rate of acceleration than a standard trapezoidal
move.
Ramp shape is the toggle function on the Speed key, and a ramp may be entered using the following
command:
To remove:
In the case of a Multi-target move (see Multi-targets) differing accelerations, decelerations and ramp
shapes may be applied to each section of a multi-target move.
2.5.6 Delays
Simple Pre-move delays may be added to any command line using the toggle function on the
Time/Delay button.
i.e.
This will result in the move for axis 1 executing 10.5 seconds after the playback is fired. During this
delay period the axis will enable, but not move, while the delay is counted down within the “Time
left” display on screen.
Delay can be entered into the command line with the toggle function on the time key.
By default all axes in Speed Mode have a single target, which is implicitly referred to when applying
an operation to an axis. If an axis has more than one move, they must then be referred to explicitly,
using the Target Number command, counting the first move as Target Number 1.
When addressing Multi-Target moves, the Plus, Minus and Thru commands may be used to select
multiple moves at once.
If a Target Number is selected which does not exist, this will be added as long as it is the next
incremental move in the list. Targets may also be inserted using the Insert Target Number
command.
The Target Number functions can be found as 2nd and 3rd toggles on the “Dead/M-Tgt” button.
eChameleon offers the user the ability to plot multiple-target moves for single or multiple axis. A
Multi-target has many uses but in most cases will be a string of linked move parameters with varying
targets, speed, accels, delays etc.
A singular point to point move is regarded by the system as “move 1” and as such it becomes a
simple user command to add “move 2, move 3” etc and even to insert a move in between existing
moves.
A multi-target command is entered using one of two methods, the simplest of which is by the use of
the “Dead/MT” button.
Pressing “Dead” once reflects on the command line as “Dead”, the second press enters “Target
number” and the third press “Insert target”
It is then a simple step to create a multi-target such as “Target number 1, Dead 2, target number 2,
Target 2000, speed 1200” etc .
When a multi-target is present then the move profiles are displayed as a graphical list within the
control view and a target symbol is displayed on the grids or dynamic axis grids. The target symbol
forms a drop down displaying the list of move parameters. The move parameters may be edited
simply by clicking on any of parameters displayed, this will enter the relevant command line for
editing or issue.
Pushing and holding the “MTarget” button will open the Multi-target and triggers editor.
The multi-target editor displays any multi-targets already present as a list, with options to add a
selection of triggers for each move.
Only axis under control of the current playback will be displayed as available for editing.
2.5.7 Repeat
If an Axis has a Multi-Target Move with two or more targets, a Repeat may be used to loop back to
the beginning after the completion of the last move.
A Repeat may be either infinite or a specified number of repeats. A normal Multi-Target move has a
repeat of Zero, and so a Repeat of 1 implies the moves will execute twice.
A Repeat may be programmed from the Multi-Target Editor, or using a Command Shortcut.
2.6 Actions
An Action is a collection of Axes and/or Groups with associated move data.
In order to record or delete an Action, the user must have appropriate privileges.
An Action is especially useful for sequences which are used often, or as a more permanent clipboard.
They also are ideal for saving moves for emergency show recovery scenarios which do not belong in
a specific State.
When recording an Action, the user may either select a specific sub-set of axes from the current
playback, or simply record the whole playback using the commands such as:
Please note that an Action may be deleted at any time without affecting previously programmed
States. In the same way, updating an Action will not update any States which had used it.
2.6 Triggers
A Trigger is a means of starting, stopping or modifying motion of an axis, based on the movement of
another axis. There are many forms of types and conditions of triggering available within
eChameleon. The axis/group or playback involved in the triggering should be considered in two
ways: the “triggerer” or source (the object that is providing the trigger point) and the “triggeree” or
target (the object that receives the trigger.
The condition of the Trigger (i.e. at what point is the Trigger executed) from its source may be:
• By absolute position
• Dead (i.e. Dead position reached)
• End of move (number)
• Speed reached
NB: Triggers do not only refer to multi-target moves, they can be used with
standard point to point moves!
2.7 Shows
A Show is the basis of all States, Groups, Actions, and Deads and much more in eChameleon. As with
all items in the system, it must have a unique number.
A new Show can be created at any time from eChameleon using the syntax
Shows may not be recorded over, and so must be deleted before a show number may be reused.
However this process is not one which can be undone, and may result in the loss of a large amount
of data if accidentally issued. For this reason the user will be prompted to confirm this in a message
box which will prevent input until the user has clearly read the warning message.
In Edit mode, all operations are possible (depending on user privileges), however on desks without a
dedicated Next and Last key, States must be loaded numerically since the arrow keys are performing
command line cursor navigation.
In Performance mode (indicated by a White background on the Current State bar in eChameleon), it
is intended that the user is running a pre-programmed show, and thus should not be making
changes. It is therefore not possible to Record or Delete any item whilst in Performance Mode.
Show mode may be toggled at any time, including during a show, without affecting the currently
loaded state.
It is worthy of note that any axis loaded to any playbacks are always live and ready to execute and
that states are simply a method of recalling a known set of sequences.
The state list is essentially a list of pre-defined sequences with axis and move parameters recorded
to the playbacks. For show running purposes the operator will use the Next key to advance through
the states after each state has been run.
It is usual to build a state list to include sections for axis testing, pre-show checks, preset moves,
show cues and après show moves. This obviously differs from show to show and venue to venue
where and in venues where the system is used more for performance space modification rather than
show running.
The states are numbered in a way useful to the user and have an option to add a textual title. The
state list also displays coloured indicators of available state, loaded state, tracking state and other
roles states.
To delete a state:
To re-name a state:
NB: In order to facilitate Tracking (see below), when a new State is ready to be
created, the “Clear All Playbacks”, or “New” command must be issued, which
remembers the prior state number (indicated with brackets in eChameleon), and
assumes that the next state to be recorded follows this in sequence. If states are to
be recorded out of order, it is recommended that the operator loads the state
immediately preceding the intended new state first.
2.8.2 Roles
A Role is means of partitioning the cues in order that multiple operators may share the operation of
single show.
A Role is a system item which is created using eChameleon Manager, and has a unique number and
name. Roles will often represent a location of operation, for example “Fly Floor”, or “Sub Stage”, as
this location will have a set of cues assigned to it. It is important not to confuse Roles and Control
Points. A Control Point is a physical connection location which may have restrictions on the axes
which can be operated, whereas a Role may be used from any Control Point, and merely represents
a sub set of the cues for a Show.
A single state may have an entry for multiple roles, each of which can have a unique name. This can
allow for cues to be called with the same number for all operators. When multiple roles all
participate in a state, it is assumed that all roles will load their states at the same time, therefore
eChameleon will not allow a state to be recorded which use the same axis in multiple roles.
Multiple users may have the same Role loaded at one time, which allows for powerful multi-desk
plotting, and running of cues for other operators in unexpected show situations.
When logging in to eChameleon, a specific role must be selected, which then determines which role
all states are loaded for, however at any time a state may be loaded for another role:
2.8.3 Tracking
A tracking or tracked state allows a playback/s and associated move parameters to be carried
forward into subsequent states. This option allows the operator to Next or Last to add additional
states whilst playbacks are in motion and hence allows continuous motion throughout state
advances.
A revolve (turntable) moving throughout a scene change, whilst, on a called cue, a flown piece flys in
and then flys out. The operator in this case needs to set the revolve in motion and execute the flying
“IN” cue, then “Next” in order to load an “OUT” cue for the flown piece, without affecting the
revolve.
Tracked playback/s may be tracked through any number of subsequent states, but must be explicitly
recorded into those states. The tracked playback move parameters remain in the base state, and the
subsequent states merely link to the same information.
When loading a state which uses Tracking (indicated in eChameleon with a purple icon in the state
list), it will always load with all tracked information present, irrespective of the order that state is
loaded in.
If alterations are made to tracked playbacks in anything other than their originating state, they will
not be recorded. The changes must be made to the original state and will therefore appear in all
Tracked states. When running states in sequence, alterations to tracked playbacks will remain
current if using Next and Last commands, however if a state is loaded by number, the original
Tracked information will be reloaded.
• The Tracking selections are accessed using the “State Options” button
• Tick playback is the box for the playback to be carried forward into the current state (only
allowable if the playback is unused in the current state and the axis concerned are not
assigned playbacks in the current state)
• Once the playback is “ticked” then the move information (brought forward from the last
state that the playback was used) will be displayed in the current state and a “Tracked”
statement will appear next to state options
• The current state must now be re-recorded in order to retain the tracking.
2.9 Simulation
eChameleon features a full simulation, which allows axes to loaded and run in real time, however no
move data is transferred to the nodes and no ‘real’ axis will be set in motion. The simulation can be
used in Offline mode, or temporarily enabled in Preview mode.
2.9.1 Offline
Offline mode is selectable at log in of eChameleon, and is also used in the event that the automation
network cannot be contacted on boot (an error will warn the user). It is most useful for pre-plotting
and training of new operators, as there is no risk of accidental real-world motion. To exit offline
mode and return to a live online configuration, the user must restart eChameleon.
2.9.2 Preview
The Preview function within eChameleon allows the control desk to be placed in an instant
simulation mode. All standard functionality remains available and all states may be accessed and
run. If positions are changed for axes in Preview, this will not affect the real axes.
When in Preview mode, there is an option to “Preview state start positions”. This means that when
a State is loaded, then the axes current positions are snapped to the appropriate starting positions to
run the loaded state. These positions are calculated from target position on the last occasion that an
axis was used in a state prior to the loaded state. It is always, therefore, advisable to plot a ‘preset’
state at the beginning of a show’s state list which includes all axes targeted to their show starting
positions.
When exiting preview mode then the axes current positions and status are updated to that of the
real system.
When any item is recorded or deleted, the undo chain is broken, and so it is impossible to go back.
2.11.2 Refresh
In a multi-desk environment, it is necessary to keep up to date items which may have been altered
on another desk. This typically includes States, Deads, Groups and Actions. eChameleon performs
automatic updates of this data in most circumstances as it is altered on other desks, but to avoid
conflict with loaded axes and states, there may be some items not updated instantly. In this case an
explicit Refresh command may be performed in order to synchronise the data with other desks.
Refresh may take a longer amount of time to execute than most commands, due to the quantity of
data being exchanged.
2.12 Labelling
The Text key allows alphanumeric data to be entered on the command line, in order to name any
recorded objects such as States or Deads or Actions and also allows re-naming of Axis within a show
Text can either be specified within the command line at the point of Record, or it may be added or
modified at a later date. For example:
Note that when used to alter the name of a recorded item, the command is followed by Enter and
not Record.
The Text command also offers the ability to textually edit the name of an item. When selecting an
item to rename, if Text is pressed twice it will populate the command line with the existing name,
allowing the use of the command line cursor to edit it. On typing Enter, the item is then renamed as
normal.
NB When labelling objects such as Deads, States and Actions it is worth thinking
about a standardised approach to your labelling before you start work. This will
help with consistency across your shows, the aid the operators and provide you
with an efficient way of referencing back to your work at a later date.
Names like “Current” “This one” “new” and “amended” should be avoided as
inevitably you will end up with several “new” or “current” objects.
It is worth having a few basics such as “IN Dead”, “Out Dead” and “Show Dead” as
venue standards and then potentially labelling further objects with some relevance
to their use.
It is also worth avoiding hugely long and cumbersome textual or numerical labels,
especially with Deads, where a quick look up is essential and with States when a
quick reference of called Cue number is often all that is needed.
2.13 Shortcuts
eChameleon shortcuts offer the user a powerful selection of tools enabling instant access or
execution.
Shortcuts may be executed directly from the shortcut pages (via mouse or touch screen)
When using an Acrobat with integral shortcut buttons, the first page of shortcuts relate directly to
the hardware buttons
The shortcut buttons on the Acrobat∙G6 are in the form of full colour OLEDs and as such can be
labelled and colour coded to match the generated shortcuts.
Shortcuts that execute external motion may be assignable and push and hold to execute and dead
man dependant.
Shortcuts may be combined to offer full sequence execution and monitoring from one button.
NB: Please refer to “Shortcuts Editor” for Shortcut setup procedures in eChameleon.
Shortcuts are a very powerful tool within eChameleon. The shortcuts screen may be accessed via the
“ …” button. The current shortcuts will be displayed on screen as a selection of pages and maybe
executed directly from the touch screen, if using a Nomad.
NB: The first page of shortcuts relate directly to the shortcut buttons on an Acrobat∙G6, from
where they can be immediately executed.
NB: Pushing and holding the “…” button opens the shortcut editor. See “Shortcuts Editor”
• Actions:
o Allow a pre-defined action (sequence of motion (any series of moves that can be
programmed to a playback)) to be loaded to a shortcut. Very useful for “get out of
jail” cues and emergency cues
• Command capture:
o Allow any command typed into the command line to be allocated to a shortcut. Very
useful for frequently used commands and complex sequences.
• IO Tracing:
o Allows any system IO to be permanently displayed on a shortcut
• Macros:
o Allow any digital axis or sequence to be allocated to a shortcut
In most cases this is all a user needs to do to access the system, however options are also presented
for User, Show, Online, Offline, local and server connections. These options will relate to pre-defined
or recorded selections within the database.
In order to select a different or new database, the user must open the eChameleon settings (please
refer to the appendix “eChameleon settings” or “Starting a new database”)
The User and Pin number options are defined within eChameleon manager, the Show and Role
options are defined within eChameleon.
Menu and
Launcher Information Bar Axis Grids Tabs
Information
Circles
Dynamic Grids
The bottom left circle displays the last selected “resource” i.e. axis, group, state etc. –
this is important as a numerical selection alone will always add the last selected
resource as the initial command line entry.
The circle bottom right has toggle functions to display the currently used control
point, local or server connection, Online or Offline and A or B machine (if using an
Acrobat G6
The information strip sits at the top of the main screen and displays current selections of Show, Role,
Filter, User, view and time. These displays are drop down options enabling the User to change any of
these selections on the fly.
The Playback display provides information on the percentage of plotted speed applied to each
playback (therefore controlled axis) and the time left for each move. The Playback graphic is
dynamically related to the physical E Belt adjustments.
In addition to Device status, when using a SIL3 system, there is an additional border which
displays SIL3 verification status. The border will be striped yellow and black if the state is
3.2.7 Menu
The eChameleon icon (extreme top left) contains option for basic system set up of Units,
Language, Display, Control surface, System and State Management. There is also an
option to print screen.
Units allow the user to select units for position display, Load
and Torque.
• Show all Role states – includes all states within the state list regardless of Role ownership. If
not selected then only the states belonging to the current role will be displayed
• State list Queries States – when selected, clicking on a state title within the state list will
display the state query. If not selected then clicking on the state title in the state list will load
the state
• Always show dynamic grids – when selected dynamic grids will always be displayed,
regardless of any Tabular grids in the current view – this option is particularly useful for early
commissioning
• Query as you type - This option will enable or disable the dynamic command line syntax
checking. If the command line is valid, the text will be white; if invalid then the text will be
red.
• Show Torque and Load – these options are only applicable if the control system is configured
to output these values to the desk. The user may choose to display these values within the
grids
• Flash Dynamic Grid Errors – this option enables or disable the flashing status of the dynamic
grids when an axis is in error
• Show Last Command – when ticked this option displays the last command line entered in
Italics, within the command line entry box. If un-ticked then the command line entry box will
clear once a command is entered or executed. The last commands may always be viewed or
re-issued via the command line history
• Show Sculptor Borders – this is an option for use within the Sculptor graphical interface and
allows the user to view or not view any borders that are in place. Borders appear as semi-
transparent blocks within the performance space.
• When Show Soft Desk is enabled the playbacks area of the main screen mimics the
behaviour of the hardware playbacks and provides Start/Stop buttons and the ability to vary
the playback percentage. This function is normally used by engineers running eChameleon
on a pc rather than a desk and is not intended for show running.
• Logarithmic speed override – this function affects the scaling of the playback e belts. In its
normal state the playback eBelt will return a linear change in percentage increase or
decrease (essentially it will take two full strokes of the eBelt for a 100 percent change in
speed override. If Logarithmic override is enabled then the eBelt response is no longer linear
and provides more granular control at the lower percentages than the higher percentages.
• Disable playback flashing – This function disables the flashing of the currently selected
playback selector button (at the top of each playback).
• Disable Playback Mode toggle – In its normal state the playback selector button will toggle
the playback mode from speed mode to joystick mode. Some users prefer to disable this
functionality and keep the selector buttons solely as a playback selection as this
functionality is also available from the playback mode button on the keypad.
• Next/Last Keys in Edit Mode – Whilst the Acrobat G6 has permanent Last and Next keys, the
Nomad and Illusionist do not and instead use the arrow keys for last and Next in show mode.
In Edit mode the arrow keys allow movement
• SIL3 Monitoring – This function enables or disables the Sil3 safety monitoring functionality
within eChameleon. Sil3 is an option within Stage Technologies systems and will not be
available on all systems.
• Preview State Start Positions sets the Preview Mode behaviour to one of two options. When
this option is un-ticked the axis current positions are unaffected when eChameleon is taken
into instant Preview mode. If this option is ticked then the current axis positions are changed
(temporarily and only within preview) to be the correct position to run the currently loaded
state. This position is derived from the last target assigned within the state list. The axis
current position will be returned to its true state when Preview mode is de-selected.
• Disable State Skip Warning – State Skip warning will display a warning when Next is used to
advance a state (within the state list) without having executed any of the moves from the
original state, whilst in show mode. This is essentially a tool to provide warning of a “double
Next” in show mode.
If using multiple screens, a different tab may be visible on each screen at the same time. Each tab
button may be sent to the other screen by right clicking on it, which will then cause that tab to open
on the alternate screen.
To exit eChameleon:
Click on the X icon on the top right of the main screen and acknowledge the confirmation. The user
will now be returned to the Launcher, with options described as above.
Click on the X button top right of the screen. The user is now presented with another screen
containing buttons for shutdown, restart, exit and cancel. If no action is taken then the desk will
power down after 25 seconds.
eChameleon makes full use of the command line for User input – all functions and inputs can be
made directly through the command line allowing the user to input solely with the keypad and in
most cases avoid mouse or keyboard use.
Command lines however can be entered in several ways, either directly from the keypad or by
double clicking any parameter field within the user interface. The command line can also be
generated directly from immediate action keys and from command line captures held within
shortcuts.
The command line entries are stored in a history (of the entire eChameleon session). These historical
entries may be accessed either from a drop down at the end of the command line or by scrolling up
and down the history with the arrow keys. The historical command line may be dropped back into
the current command line, edited and re-issued.
A cursor is available within the command line. The cursor may be manipulated with the arrow keys.
Backspace will retard a single character, push and hold backspace will delete the entire command
line.
All data and move parameter changes are made through the command line. The command line is
displayed along the base of the main screen (above the playbacks and state list). The Acrobat has a
second command line mimic on the base of the second screen.
This option allows the Query pages to expand to the relevant section as each command is typed and
hence display to the user all options and parameter relevant to the command line being typed.
Each command line entry of an eChameleon session is stored as an entry in the command line
history. The history can be viewed and command lines re-selected (re-issues) from either the drop
down to the right of the command line (with the mouse) or via the up/down keys.
A historical command line may be “dropped” back into the current command line and re-issued by
selecting the command line with the mouse.
The On Screen Keyboard is an option, selected through the menu settings. If selected, the keyboard
will be displayed on screen on each occasion that text entry is demanded. (If using a Nomad or other
touch screen device then the keyboard can be controlled via the touch screen.) The keyboard will
close once the text is entered.
The states are numbered in a way useful to the user and have an option to add a textual title. The
state list also displays coloured indicators of available state, loaded state, tracking state and other
roles states.
If a change is made to a state (a change made to any axis parameter) then the state will be identified
as a “modified state” in red, hence prompting the user to re-record the state, if the changes are to
be saved.
Recorded view relates to the general screen layouts. The user can choose to record a
selection of views containing a number of differing grids, layouts and 3D camera views.
These views maybe assigned to particular states such that the general view will be loaded at
state load and only relevant information is displayed to the operator.
State notes can be used for any useful and pertinent text I.e. warnings, checks or Q sheets.
• Confirm any errors present to clear the state notes field and click the “Edit” button
• Add your notes using the standard text functions and options and click the “Apply” button
• The current State must now be re-recorded to include your new state notes
• If state notes already exist, then use the “Clear” button within the state notes section to
clear these notes.
NB: This screen area is also used for user input and system errors and will therefore be masked
by any current errors until they are “confirmed”
Any errors displayed are layered in order of generation and the errors may be “confirmed”
individually or as a group. The user confirmation is also logged within “eChameleon Monitor”.
Once all errors have been confirmed then the state notes will again be displayed.
Node in maintenance
3.5.1 Nodes
The Nodes section of the Devices Tab displays the status of all Nodes within the system.
• A green light beside the Node name indicates that communication to the node is good. A red
light indicates that communications are down.
• Any Node may be immediately placed into Maintenance mode (see below) via the tick box
beside the Node name.
• The drop down box selection (left of the maintenance selector) will display all axis associated
with the Node.
Maintenance
• Any Node may be placed in maintenance mode via the Devices query. Each Node has a tick
box selection for maintenance node (to the left of the title).
• When a node is placed in “maintenance” the desk ceases polling the node. This enables the
user to continue working in an online configuration, whilst a nodes communications are
down, without receiving warnings and faults.
• All axes relating to a node in maintenance will be displayed in
“maintenance”.
• A screen tip will display the IP address for each Node
• An IO state can be of serious consequence (i.e. E Stop struck) or simply information (i.e.
Pumps running). eChameleon therefore provides several colour, hence severity warnings and
indications for the state of the IO.
• A struck E Stop, therefore would indicate as Red (Critical), whilst a pumps running may
indicate as Blue (Information).
• The IO header groupings are reflected within the mini-devices view (see below).
• The tick boxes beside each IO nominate whether the IO status change is reflected within the
Mini devices View.
• A tick box is provided for Io groups (within each header) to “auto-tick” the entire group.
The view is designed to be a permanent and instant general view of the system status. As with the
Devices query, the mini view is for the most part green for good and red for bad. If, for example, an E
Stop is struck, then the E Stop section of the mini view will turn red. Clicking on this section will
immediately return the user to the individual devices I/O query where the Input/Output can be seen
immediately with its corresponding label (i.e. DSL E Stop Hit)
The control graph shows a graphical representation of trapezoidal move for each playback with axis
under control.
Each PB may be expanded or contracted with the drop down arrow. All playbacks may be extracted
or contracted via the state drop down arrow.
Speed
Target
Acceleration
Delay
Dead number
Example:
A user input of [Axis 1 Dead 2 Speed 1000 Accel 300 Decel 200]
The eChameleon main screen contains sectioned displays for all stored data, live data and feedback.
The centre section of the GUI (graphical user interface) is entirely user-customisable and is formed
of various types of grids (information displays). The user need not create any grids in the first
instance as eChameleon will create dynamic grids as required for any axis under control
A view is a generic name for a main screen layout. These layouts may be constructed, by the user,
from a selection of differing grid types. A selection of views may be recorded and subsequently
assigned to the loading of any state.
The grids have many options for customisation, available within the tabs. The grid options become
available as each grid is highlighted.
The grids may be positioned within the screen layout as required and eChameleon will not allow
grids to overlap and therefore hide controlled axis.
• The current view is displayed in the Information bar, with a drop down for all available views.
• The current view contains all information for the current main screen layout (including grids:
positions, members, rows etc.)
• The current view is definable within the Views Tab.
A simple tabulated grid displaying individual axis move parameters and status (user definable).
The row options are found in the view tab, when the grid to be edited is highlighted.
Removable fields:
3.7.6 3D Grid
3D graphical representation of the performance space showing axis under control and in motion
(User definable).
Time left
Current position
Target
Dynamic grids are displayed either always by User option from the menu or at any point that an axis
is under playback control but not displayed within a defined grid.
They appear dynamically on the left hand side of the main screen and contain all information
pertinent to axis move parameters, current position, errors, status and time left.
All grid types can be added via the Views tab with simple Add grid
buttons.
If using an Acrobat, the grid will appear on the primary screen
To move a grid the User must click and hold the left mouse on the name tab of the grid. The grid
may now be dragged to the desired position.
If the grid is dragged to an invalid position then the grid will be shown in red and if dropped by the
user, the grid will return to its original position.
All grids within the main screen may be enlarged or shrunk within allowable limits with use of the +
and – buttons (bottom of Tabs field).
A “View” may be recorded once all grids have been positioned as desired.
Multiple views with separate grid layouts may be recorded and re-called.
NB: Once a grid is highlighted then the “Delete grid” option becomes
available (Grids field within View Tab). Press “delete Grid” – grid will be
removed and other grids re-sized.
The buttons along the top right of each 3D grid are instant camera options.
The first six buttons along the 3D menu bar are quick select camera views. The highlighted portion of
the cube, pictured, shows the location of the camera relative to the defined graphic.
The button between the – and + toggles between rotation and flat plane motion when moving the
graphic with the mouse. These functions are also available directly via the mouse.
• Holding the left mouse button and moving the mouse moves the graphic in a single plane.
• Holding the right mouse button and moving the mouse moves the graphic rotationally.
NB: If an axis is added to the graphic, then the axis will always
appear within the graphic – if the axis is into added to the graphic,
then it will only appear when the axis is under playback control.
Drag to re-size
3.7.15 Perspective vs. Orthographic
Perspective/Orthographic button toggles between a perspective view and a “flat” view without
perspective.
The standard cameras may well be useful without modification, however if the user requires a more
specific camera view, then the graphic can be manipulated, as described above and a new camera
view recorded. The User defined cameras do not appear as quick access keys, but instead appear as
cameras (which may now be named) within the Cameras section of the Views Tab.
• Press the “New” button within the camera section of the views tab.
• Manipulate the graphic, as described above, until the desired camera view is achieved.
• Press the “Save” or “Save as” button within the camera section of the views Tab.
• The new camera will appear as a numbered camera in the list of currently recorded cameras.
• The order of the recorded cameras may be changed using the “move up” and “move down”
buttons.
• Select the camera view to be deleted: either click on or press on the camera within the
cameras section or use the Camera number Enter command line entry.
• Press the “Delete” function button within the current cameras section of the Views Tab.
The Query home contains standard options for Home, Back and Up Level
NB: If the Dynamic Query option is selected and Query Home is displayed
then the appropriate queries will be displayed as the user inputs command
lines. (I.e. as Axis 1 is typed then the axis level query, for axis 1 will be
displayed, showing all telemetry, properties, Deads and inputs.)
• Axis
Axis Query displays all individual axis telemetry, properties, associated Deads and axis level
inputs (i.e. limit switches, slack ropes etc.). The axis level query also gives the user options to
change/set software limits (high and low), current position and to acknowledge a drive fault
and “Freeze” an axis.
• Groups
The groups query contains information about each group currently recorded within the
current show. It displays group type and axis members.
• Actions
The action query displays information about all actions currently recorded within the current
show. When an individual action is queried then the display shows a graphical representation
of all associated axis and move parameters.
• States
The state query displays information about all actions currently recorded within the current
show. When an individual action is queried then the display shows a graphical representation
of all associated axis and move parameters.
• Shows
The shows query displays a list of all current shows within the database. Querying an
individual show displays a few properties for the show type.
• Macros
The Macro query displays a list of all Macros currently recorded within the show. Querying an
individual Macro will display a description of the Macro properties.
• Control points
The control point query displays a list of control points currently defined within the database
along with the current usage status (i.e. if a desk is currently connected, with the user role
and logged in user.
NB: The available Queries are dependent upon desk type and system configuration.
Display Options
Summary
The summary displays the current status of an axis – position, Status, any
errors present, load and torque (if applicable).
Properties
The properties section displays all axis level properties (as defined within
eChameleon Manager)
Deads
The Deads section displays a list of current Deads defined for the axis.
Each Dead has a numerical selection, name and target (in user units)
If the axis current position matches any of the Deads targets, then the Dead
will be displayed in green.
Axis Inputs
The axis inputs section displays the current status of any traced inputs associated with the axis.
These would normally be traced safety devices local to the axis (I.e. hardware limits, cross groove
switches etc.
Associated Inputs
The Associated inputs section displays the current status of any general IO associated (within
eChameleon Manager) with the current axis.
Associated IO would normally be any general level IO that impacts on the functionality of an axis (I.e.
a hydraulic lift may have pumps running and pumps pressure associated with the axis)
Operations
The Axes Operations section contains buttons for immediate changing/editing soft limits, current
position and for Drive Resets, “Freezing and Thawing” axes.
Operations
The Group operations selections live at the base of the Group Query
window.
• Set master Axis – allowing the master axis of a locked group to be re-defined
• Set Alignment – allows a locked group alignment to be set, after the group has been recorded
• Correct alignment – allows a locked group to be reset to its alignment, relative to the master
axis position.
• Freeze/Thaw – Allows a group to be frozen/thawed
This list mimics the State list within the main screen, with the additional option
of a state level query button.
Filter By Role
The State list Query may be filtered by Role. The currently defined Roles are
displayed within the drop down (top right of the State Query). An individual role
may be selected to filter the state list query to only those states recorded to
that Role.
The State Query displays as a control graph for all axis recorded within the
state.
The Macro list Query displays a numerical selection, name and a Query button
The Macro Query (individual Query) displays the Macro name, mode and any other associated
parameters.
Each control point displays the current logged in User name and Role.
Command line approach: (NB in all cases Target may be replaced with Dead)
[Axis number Target number Enter] applies the first Target to the
chosen axis
[Axis number Target number 2 Target number Enter] applies a second move to the axis
[Axis number Insert Target number 2 Target number Enter] applies a new target for move 2
and shifts the old move 2 to
move 3
[Axis 1 Target number 1 Dead 3 Speed 500 Accel time 3 sec Target number 2 Target 3000
Accel 250 Decel 300 Time 15 sec Enter] etc.
Once a multi-target move has been entered it may be edited in the same method or by directly
clicking on the appropriate fields in the grids or control graph
NB It is often simplest and most efficient to edit existing multi-targets directly from the
Control Graph.
The picture below shows a multi target for a single axis, again any of the fields may be edited by
clicking on them. Add a Trigger to this move
An input display allows a shortcut to constantly display the status of any system level IO.
Command line shortcuts allow any valid command line to be stored on a shortcut and re-issued at
will. This can be useful for command lines that are regularly used, especially during plotting; it can
also be used for “get out of jail” cues or cues that may require instant, out of sequence execution.
(I.e. front tabs IN, performer flying rescue etc.)
• Message textual message entered via the … - this message should be a simple
description of the result of the command line
• Choose “close shortcuts window” if the shortcuts window may obstruct the desired
command line input.
• Press “Start Capture”
• Input desired command line (with or without “Enter”)
• Press “Stop Capture”
• Save and close
NB: It can be useful to use the arrow keys UP and Down to reinstate or edit a previous command line.
• Action number: Numeric selection entered via the … - will only allows input of
available Actions.
• Require DMH: Tick box selection making allowing the Action to be deadman’s
dependant
• Latch: Tick box selection – making the execution single push or push and
hold.
Macros are currently created within the database and display as a drop down selection within the
shortcuts editor.
NB: For more information command line entry please refer to the “Command line” section
within features and functions
This function clears down all playbacks, releasing all objects currently loaded.
It creates a new, blank state to record into, and must be used to ensure Tracking playbacks link to
the correct state when plotting multiple states.
If an Axis is not loaded onto the current playback, eChameleon will attempt to gain
control, and thus load the Axis. If the axis is already under the control of another desk,
this operation will fail, however if it is on another playback on the current desk then it
may be ‘stolen’ depending on the syntax used. See Playback Stealing.
Once the object has been selected it can then be modified by other commands.
If loading an Action or Group, then multiple axes will be loaded onto the playback at once, and must
all be available for the command to succeed.
When selecting a resource, it is not always necessary to explicitly prefix the numerical selection with
a key press. The command line remembers the last resource type to be used and as such will
automatically enter the previous resource for you.
This is displayed on the screen to the left of the command line, and on a Nomad control desk the
appropriate key will be illuminated in Orange.
Examples:
[Axis 1 Enter] takes Axis 2 into playback control
If a command line is prefixed by Plus, this will add the selection of objects to the current playback.
If a command line is prefixed by Minus, this will remove the selection of objects from the current
playback (if they are already loaded)
A complex selection of objects can be achieved by the use of Plus, Minus and Thru within the
command line, where the modifiers add or subtract objects from the selection.
The Thru command (which is accessed by pressing the + key twice), represents an inclusive selection.
i.e. Axis 1 Thru 3 means axes 1, 2 and 3.
NB: Minus may also be used numerically, for example when entering a soft limit of -1000mm.
Examples:
[Axis 1 + Axis 2] results in Axis 1 and Axis 2 taken into playback control
[Axis 1 + Axis 2 Target 1000] results in Axis 1 and 2 being assigned a target of 1000
[Group 1 Thru. Group 6 speed 200] assigns a speed of 200 for groups 1,2,3,4,5 and 6
[Axis 1 Thru 5 – Axis 3 + Axis 7] takes axes 1,2,4,5 and 7 into playback control
Since not all objects of differing types may have the same properties or capabilities, it may not
always be possible to use implicit selection.
Examples:
[Axis 1 Thru Axis 4 Speed 500] Assigns a speed of 500 to Axis 1, 2, 3 and 4 without
affecting any other axis
[- Axis 3 – Axis 4] removes axis 3 and 4 without affecting any other axis
[Axis 3 Target Number 2 Dead 3] Assigns a target of Dead 3 as a second target to Axis 2
without affecting any other axis
Select the coloured playback for the axis to move to (with playback colour selectors)
Type:
[Axis numbers Enter] will remove the any currently controlled axis and replace
with the new selection
[+ Axis numbers Enter] will add the axis selection to the new playback
As discussed in Implicit Selection above, if no axes are explicitly selected, the operations are applied
to all axes on the current playback.
Examples:
[Axis 1 Accel 250] Assigns an acceleration rate of 250mm/s/s (of feet/s/s)
[Axis 20 + Axis 21 Accel Time 3] Assigns an acceleration time of 3 seconds to Axis 20 and 21
[Group 4 thru Group 6 Decel 1100] Assigns a Deceleration rate of 1100 to Groups 4, 5and 6
[Axis 1 + Axis 5 dead 2] Assigns a Dead and associated Target to Axis 1 and 5
[Axis 3 + Group 2 Move 330] Assigns a target to Axis 3 and Group2 that is +330 from
their current positions
[Axis 4 Target number 2 Dead 2] Assigns the target of Dead 2 to the 2nd move (in a multi-
target for Axis 4
[Axis 4 Insert Target number 2] Inserts a new move number two in a multi-target and
shuffles all further moves down a number i.e. what was
move 2 becomes move 3 etc.
[Axis number Speed number Enter] Assigns a speed to the selected Axis
[Axis number + Axis number Speed number Enter] Assigns a speed to the selected Axis
[Group number + Axis number Speed number Enter] Assigns a speed to the selected
Axis/Groups
[Axis number Time number Enter] Assigns a time to the selected Axis
[Axis number + Axis number Time number Enter] Assigns a time to the selected Axis
[Group number + Axis number Time number Enter] Assigns a time to the selected
Axis/Groups
In the case of time commands the User is presented with several options
The user may select the time calculation either with the mouse, Keypad 1, 2, 3, or 4 or touch screen
To maintain a cue timing after any change, the cue must be re-timed after the
changes are made.
Ramp shapes are defined within the database and can be selected with a numerical selection
For more information on Ramp shapes: refer to the Ramp Shape section in
Functions
NB For more information on multi-target and triggered moves; please refer to the
multi-target and Trigger sections in the functionality section of this manual
Examples:
To enter a single target for an Axis:
[Axis 1 Target number 2 Target 1000] adds the target 1000 as the second
target for Axis 1
[Axis 1 Target number 2 Speed 200] changes the speed of Move 2 to 200
[Axis 1 Target number 2 Accel time 2 Decel time 2 time 20] changes the Accel and Decel rate
and adds an overall timing of 20
seconds to move 2 for Axis 1
[Axis 1 Insert Target number Target 300] Inserts a Target of 300 as move 2
and shifts the original move 2 to
move 3
[Axis 1 Insert Target number 2 Dead 5] Inserts Dead 5 as the second Target
for Axis 1 and shifts the original
move 2 to move 3
[Axis 1 Insert Target number 2 Dead 5 Accel 500 Decel time 2 Delay 5 time 15 + Group 2 Dead 4]
Examples:
[Axis 1 Text “Front cloth” Enter] Assigns the name “Front Cloth” to Axis 1 in
the current show – this method of labelling can be
employed for all objects (states, actions etc.)
[Action 15 + Action 17 Enter] Loads Actions 15 and 17 onto the current playback
[Sculptor action 100 Enter] Loads Sculptor action 100 onto the current playback
[Group 1 Record] Records the currently selected axis to group 1 and offers
the selection of group type
[State 99 Delete] Deletes State 99
[State 1.01 record] Records State 1.01 for the current role
[Role 3 State 1.01 Record] Records this state into another Roles State list
When recording a State with entries for multiple Roles, the contents of the State are assumed to be
loaded at the same time, and so eChameleon will check that the same axes are not used in another
Role at the point of Record.
The currently loaded State may be re-recorded by simply pressing Record without any other
command line entry.
To Delete a State, the syntax may be used as above, replacing Record for Delete.
NB: eChameleon uses the terminology of State for what is often referred to as a Cue. This is because
eChameleon makes use of multiple playbacks in one State, thus giving the user the choice to either
split a Cue across multiple playbacks, or to place one Cue per playback for rapid sequences.
[Axis 1 Target 1000 Dead 1 record] Will record Dead 1 using a target of 1000 for Axis 1
[Axis 1 Dead 1 Record] Will record the current position as the target for
Dead 1 if the current playback is in joystick mode. If
the Playback is in Speed Mode then the current
target will be recorded.
Deads may be overwritten at which time eChameleon will update the targets for all States in which
the Dead is used.
A Dead may only be deleted if it is not used in any States. Once it is no longer used, it may be
deleted using syntax such as:
To record an Action:
To Delete an Action:
The user may now select the show with the Show number specified
These options maybe selected with the mouse, touch-screen or via the keypad with 1, 2, 3 or 4
For more information on Group types and rigging please refer to the Group types
section of this manual
For more information on Sculptor Groups please refer to the Sculptor section of
functionality in this manual .
A view is the overall layout of grids within the eChameleon screens, including any cameras and
specific settings.
Once the layout of a screen has been established it may be recorded as a view and applied to a
particular state either from the Views Tab functions or directly via the command line:
The view must be selected from the State options section of the main screen
Tick the Recorded View box and select the appropriate view
The current State must now be re-recorded for this view to remain associated with the state.
Text can either be specified within the command line at the point of Record, or it may be added or
modified at a later date. For example:
Note that when used to alter the name of a recorded item, the command is followed by Enter and
not Record.
The Text command also offers the ability to textually edit the name of an item. When selecting an
item to rename, if Text is pressed twice it will populate the command line with the existing name,
allowing the use of the command line cursor to edit it. On typing Enter, the item is then renamed as
normal.
[PB Mode]
The Query tab, as described previously, allows the user to view, for example, all of the Axes on the
system, or the specific properties of an individual axis by navigating on screen.
The Query key is an extension of this allowing rapid access to every query page from the command
line.
Query commands are generally logical extensions of the related selection commands, for example:
The same logic applies for any item which can be accessed in the Query tab using the mouse, such as
groups, states, roles, actions etc.
NB For further information on Query; please refer to the Query Tab section of
this manual and also the Query on demand section of this manual
When any item is recorded or deleted, the undo chain is broken, and so it is impossible to go back.
Example:
[Axis 1 + 3 Dead 1 Speed 500] loads Axis 1 and 3 to the current playback
with a speed of 500 and assigns the targets
for Dead 1
[+ Axis 2 Dead 2 speed 200} Adds Axis 2 to the current playback with a speed of
200 and a target of Dead 2
If we now use:
And again:
We can now:
[Redo] (Push and hold Undo) to re-instate the previous changes in the same manner as Undo.
4.12.2 Preview
The Preview command allows eChameleon to be placed in an instant offline (virtual) state, such that
all functionality is available, but no real axis will be affected.
[Preview]
Once preview mode is engaged, the coloured border of the main screen will appear as a hashed line,
rather than a solid line. Preview has 2 modes, set within the eChameleon menu.
To disable Preview mode and return to normal operation press [Preview] again
Quick view commands allow instant access to the various Query and Tab functions of eChameleon.
All of the following functions and views maybe accessed via the mouse or touch-screen or directly
from the command line:
[Control] push and hold Opens the Devices section of the Tabs
[View] push and hold Opens the Views section of the Tabs
5 Appendix
5.1 Keypad functions chart
PLAYBACK KEYS:
[PB Clear] push and hold Push and hold – clears all playbacks, new
state
[PB Mode] push and hold Push and hold – sets the axis in playback
control to reverse mode
[Group] push and hold Push and hold – sets Safe on Demand or
Locked on Demand
[Dead] Push and hold Push and hold – opens the multi-
target/trigger editor
[Speed] push and hold Push and hold - opens the multi-
target/trigger editor
ACTION KEYS: (Keys that execute and terminate the command line)
ARROW KEYS:
Up and down Cycle through the command line history, in order that the user may edit
and/or re-issue
Left and right: Acrobat∙G6: These keys move a cursor through the command line for
editing.
Nomad/Illusionist: These keys move a cursor through the command line
for editing in edit mode.
(Left and right arrows act as “Next” and “Last” (advance and
Retard through state list in “Show mode”.)
OTHER KEYS:
eChameleon allows for a high level of scheduled and immediate archiving and restoration of
databases. As part of the commissioning process a set of scheduled archive plans will be established,
such that there should always be a current database, the most recent archive and a selection of pre-
dated archives.
The user also has simple controls (through the eChameleon Launcher) to prompt immediate archives
and restorations.
The basic archiving options presented to the user will be determined by the system configuration.
I.e. On an Acrobat (with 2 machines) the “Send to other machine” button is present etc
The Advanced Archive option will display the list of archived databases available for restoration or
deletion.
NB When an archive is selected for installation, eChameleon will firstly create a new archive of the
currently used database!
• Latest DB (Latest archive contain DB and Log – this can be scheduled or user generated)
• General archives
eChameleon holds its DBs in a folder named “eChameleonData” – this is always located at the root of
the C drive.
eChameleon also holds archives of Events and Telemetry and can be scheduled or forced in the same
way as the DB.
NB: The majority of these settings are self discovery and in most cases will not need to be
changed
• Database
o Database selection
o Database creation/deletion
o Update local DB on Boot
• Desk
o Desk type (Acrobat, Nomad, Illusionist, running on PC)
o Acrobat A/B machine and machine names
• Server
o Server available/not available
o Server name
• User interface options
o Use dual displays
o Swap User interface
o Low resolution mode
The display settings again are self discovery and allow the User to identify, swap or select differing
attached displays.
The eChameleon network settings are once again self discovery and present as several pages of IP
addressing for the Internal and external networks.
• The system information displays the current versions of system and eChameleon software
and firmware
• Log off provides the route for system administrators to access the windows desktop.
5.5 Sculptor
5.5.1 Introduction to Functionality
Sculptor is the name given to Stage Technologies suite of multi-dimensional programming
tools and functionality.
Each tool within the Sculptor suite results as a “Sculptor action” at desk level. It is therefore
a simple key-press selection to recall any series of complex motion, created in any of the
following formats onto any (playback) start button within Stage Technologies Chameleon
software. Once the Sculptor action has been loaded onto a playback, then the motion
maybe immediately executed or recorded into a state (Cue) or action list for later use.
• Primarily plotted using a single high grade USB joystick. The joystick has X, Y, Z (+ and -)
outputs, allowing 3 dimensional motion from a single joystick.
• Teach and learn records an objects vectors spatially (i.e. records the profile of the object
within the playing area, rather than simply recording strings of positions over time for each
winch)
• The joystick maybe simply configured to allow individual axis control based on each output
axis of the joystick. I.E. the forwards/backwards motion of the joystick may control a single
or group of axis, whilst the left/right output may control a differing selection of axis.
• Visual creator records each path as a series of maps (one for each winch)
• An object profile/path can be created and viewed offline before applying to the real world
axis
o Stage Technologies have created a bolt on tool set for 3D max that allows the
animator to line up axis parameters with the real world axis and thus limit any
animation only to motion that can, in reality, be achieved. Any motion that is
created can then be output directly to Stage Technologies control software as a pre-
checked and approved sculptor path.
• The joystick axis are simply configured through the software interface to provide the most
intuitive user input.
In the case of a multi-axis object (i.e. 4 way bridal), the axis must be defined as a safe group and the
bridal geometry must be assigned – this is a once only procedure and should take only a few
minutes.
• Secondly, the winch rigging positions must be set; these are the physical positions of the
final divert for each winch. The positions are relative to any useful datum (usually X 0, Y 0, Z
0).
• It is usual for the virtual world zero datum to be at the lowest point (i.e. deck level) in the
centre of the playing area, however for speed this can be allocated at any useful datum, for
example at the base of a divert tower.
• Finally, the winches require an offset to be input into the software – the offset is the
distance from their final pulley to the datum 0, 0, 0.
• The joystick may now be used to fly and record and path within the space.
• N.B. The software will generate safe borders of travel, based upon the inputted geometry
and will utilise all the standard axis limitations (soft limits, max speeds etc.) to ensure that
each move remains within safe parameters.
• Once a flight has been recorded it appears within the standard desk software as a Sculptor
action and maybe queried or actioned using a simple command string.
i.e. “Scupltor Action 1 enter” : will load the action onto a playback for immediate playback.
• If the geometry of the playing space should change then it is simply a case of adjusting the
winch rigging positions, as before, to match the changes.
• It is not necessary to re-record the motion path, as the path has been recorded spatially and
references the object vectors rather than the individual winch line lengths. Therefore, the
path will always remain the same no matter what happens to the rigging positions.
• The path can naturally be re-recorded and stored as often as necessary if it should transpire
that differing paths are required for differing venues.
To access windows:
To leave windows:
NB: This may take a few seconds and will re-start the eChameleon Launcher.
In normal cases this file need not be edited as it is written to from the eChameleon settings options
within the launcher (as above)
i.e.
<LocalSettings xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<DeskType>Acrobat</DeskType>
<RunningOnPC>true</RunningOnPC> This should be False if running on a desk and
also False if running on a pc and using a USB wing.
<IsSecondMachine>false</IsSecondMachine> Only applicable to Acrobats
<AssociateAcrobatMachineName /> A or B machine
<ServerName>RENTALSERVER1</ServerName>
<SoftControlPointID>3</SoftControlPointID> Should be a unique number within the
system
<IsStandalone>true</IsStandalone>
<LastShowID>1</LastShowID>
<LastUserID>1</LastUserID>
<LastRoleID>1</LastRoleID>
<DefaultOffline>true</DefaultOffline>
<LogTelemetry>true</LogTelemetry>
<RefreshEventInterval>0</RefreshEventInterval>
<UICPNodeAddress>192.168.255.71</UICPNodeAddress> Internal comms
<AutomationSubnet>192.168.1.0</AutomationSubnet> External comms
<NetworkSimulation>false</NetworkSimulation> applicable only when using a separate net sim.
<SimulationIPAddress>192.168.1.1</SimulationIPAddress>
<Is24HourClock>true</Is24HourClock>
<SynchroniseWithTimeServer>false</SynchroniseWithTimeServer>
<LowResolution>false</LowResolution>
<FontSize>10</FontSize>
<KeyboardLanguage>en-GB</KeyboardLanguage>
<SystemLanguage>en-GB</SystemLanguage>
<NomadKeyboardBrightness>20</NomadKeyboardBrightness>
<UpdateLocalOnBoot>false</UpdateLocalOnBoot> Option to sync local DB with current
system DB on boot of eCham
<LoadMonitorOnSecondScreen>false</LoadMonitorOnSecondScreen>
<ReadOnlyMode>false</ReadOnlyMode>
<AutoLogin>false</AutoLogin>
<JobCode>PINK2010</JobCode> sets current DB folder
<UseSecondScreen>false</UseSecondScreen>
<SwapScreens>false</SwapScreens>
</LocalSettings>
• EventsDB
• TelemetryDB
Each of these folders will contain the current DB and archives as above.
This location also contains content and axis folders for .iv graphic files used by Visual Creator.
6 Glossary of Terms
• Action – a pre-recorded set of instructions for moving axes from one position to another. An
action, unlike a state, does not include playback information. An action contains instructions
only for a single playback and can be loaded onto any playback for execution.
• Axis – the general term used to refer to a motor and all of its associated hardware: Drive
Motor Winch, but could refer to any individual axis of motion.
• Commission – the act of setting up a control system for a customer and ensuring that all of
the components perform properly.
• Control Graph – a contextual representation of the axes under control. Includes: controlled
the axes, what playback they are loaded on, how they are loaded (as a group, or
individually), and the motion parameters for each axis.
• Counterweight system - Method of flying scenery that uses a cradle containing weights to
counterbalance the weight of the scenery being moved.
• Closed loop - Refers to a system which has reference sensors that provide constant feedback
to enable machinery etc. to automatically adjust and maintain performance (see also ‘Open
loop’).
• Control desk/control console - A piece of automation equipment which sends control signals
to the automation system and allows the operator to view system information.
• Cue – a change of state as called by the stage manager. See also “State”.
• Dead (also marks or trims (US)) - A designated height for a piece of scenery or bar; a label or
marker for a physical position or target. Manual flymen use a Dead on a rope as an
indication of the position of a scenic piece i.e. all the way in (in view) or out (out of view) or
at a mid point. For manual operation, this mark would traditionally be a cotton tape wound
through the strands of the rope but this has been replaced more recently with PVC tape or
similar. Automation operators label Deads with a number and/or colour system such as
‘Dead 1’.
• Devices – in the context of this manual and the eChameleon software, a device is a
monitored input. The specific devices that are monitored via these inputs are site specific.
Any monitored input has only two states, normal and abnormal. When configured, device
status can be observed from the Query-View and / or the mini devices view.
• DMH – Dead Man’s Handle – an integral safety switch which is a part of every Stage
Technologies control desk. In order to move an axis, the dead-man’s handle must be
pressed and held for the duration of the move.
• E-Belt – the speed control portion of a playback on Stage Technologies control desks.
• Encoder - A device which converts information from one format into another.
• Ethernet - Ethernet is the most widely-installed local area network (LAN) technology.
Ethernet was named by Robert Metcalfe, one of its developers, after the passive substance
called "luminiferous ether" that was once thought to pervade the universe, illustrating the
way that Ethernet cabling, also a passive medium, could similarly carry data everywhere
throughout the network.
• E-Stop – Emergency Stop – an electro-mechanical switch which when engaged cuts power to
the drives and brings all axes to a controlled but expedient stop E Stops are generally
“Global” (i.e. stop all motion within the system) although in some instances they can be
“local” (i.e. stop only axis relevant to their location)
• Flying bar (flybar, Barrel, Pipe) - The metal bars to which scenery and lanterns are attached
for flying above the stage.
• Flytower (also flys or fly loft (US)) - Upward extension of the stage walls to allow scenery to
be flown up until it is out of sight of the audience; it is also a structural support for the grid.
The ideal flytower should be more than twice the height of the proscenium arch, when it is
said to have 'full flying height'. The load on the grid is transferred to the ground via the walls
of the theatre.
• Free groups - Axes that move simultaneously but with each axis maintaining independence
from the others (see also ‘Locked groups’ and ‘Safe groups’).
• Grid - The support structure located near to the top of the flytower on which the pulleys of a
flying system are supported. The grid is usually constructed from metal or wooden beams.
Grid is short for ‘gridiron’.
• Group – a show specific collection of axes which can be loaded and programmed as a unit.
There are various types of groups ranging from simple plotting groups (Free Groups) with no
interdependence, to Safe groups (if one member see an error, then all members of the
group will stop and locked groups that map relative positions as slaves against a master.
• Hydraulic - Of, involving, moved by, or operated by a fluid, especially water, under pressure.
• Kabuki drop - a technique for dropping a drape or other lightweight fabric in a quick, single
motion from the ceiling to reveal the stage or performers. The system consists of a bar that
attaches to a standard flying bar and is able to spin around. The bar has prongs welded to it
on which the curtain is hung. On cue, the pole is rotated so that the prongs point
downwards and the curtain consequently falls.
• I/O – the abbreviation for Input / Output. The non axis specific inputs are called General
Inputs and can be monitored via the Devices portion of the QueryView. See also Devices.
• Limits – all axes have at least two types of limits: software limits and hardware limits.
Software limits are set by the operator and / or commissioning engineer via the eChameleon
software. No axis will be allowed to go past a software limit when under program control.
Hardware limits are mechanical devices which are activated by the rotation of the motor or
winch drum. These are set to protect the hardware. In most cases two sets of limits are
used at each end of travel (initial and Ultimate). It is often the case that the Ultimate
(Overtravel) is set to protect the mechanics of the system and the initial set to protect the
object moved by the system, although this will depend upon the application.
• Locked groups - Axes that move simultaneously and are linked together to maintain their
relative position (see also ‘Free groups’ and ‘Safe groups’).
• Macro – a low level sequence of commands designed to perform a specific function. Macros
are site specific and are generally created by the commissioning engineer.
• Open loop - Refers to a system that does not have the capacity for feedback, meaning that
errors have to be manually corrected (see also ‘Closed loop’).
• Point hoist - A simple winch that provides a single suspension point that can be deployed at
any position in a grid.
• Playback – in order to move any axis, it must be loaded onto one of the control desk’s
playbacks. The playback is comprised of the following components:
• Rack and pinion - A device for the conversion of rotary and linear motion, consisting of a
pinion and a corresponding rack.
• Safe edge - (Astragal) A rubber rim that is used around the edge of a lift, to stop the lift in
case of an emergency, thereby protecting limbs that could get trapped.
• Safe groups - Axes that are linked to a single piece of scenery but may have differing speeds
or paths (see also ‘Free groups’ and ‘Locked groups’).
• Sprocket - A tooth like projection arranged on a wheel rim to engage the links of a chain.
• Safe On Demand – a function which allows the operator to temporarily treat the axes loaded
on a single playback as a Safe group.
• State – a pre-recorded set of instructions for moving one or more axes to a different
position. A state may be functionally equivalent to a called cue but very often is made up of
more than one called cue. A state, unlike an action, contains instructions that are specific to
the playbacks on which they were recorded.
• Travelator - A motorised, horizontally-moving belt at stage level, the direction and speed of
which can be controlled. Travelators are used for moving scenery or actors onstage or
offstage.
• Trim – An American term meaning a pre-defined target position. See also Dead.
• User units – a term for the measurement units employed on a particular system . I.e. mm,
feet, second, minutes etc.
• VCA – Visual Creator Action – contains the definitional elements (resources) required to
move an object along a path, map, or profile.
• Visual Creator – an add-on package which allows the operator to easily define two and three
dimensional moves for an object being controlled by two or more axes.
7 Index
3D Display, 66 Grids, 64, 65, 66
Accel and Decel, 31, 32, 33 Groups, 13, 25, 36, 38, 43, 58, 69, 71, 118
Action, 13, 36, 45, 72, 77, 80, 96, 117, 120 History, 59
Control Graph, 14, 60, 98, 117 Locked, 25, 26, 71, 96, 118, 119
Database, 11, 101, 104, 108 Macro, 14, 62, 69, 73, 78, 96, 100, 119
Dead, 17, 29, 34, 37, 62, 70, 88, 97, 117, 118, Macros, 14, 45, 46, 62, 69, 73, 78, 119
120
Maintenance, 58
Default Cameras, 67
Manager, 18, 19, 32, 58, 70, 71
delay, 30, 33, 62
Menu, 50, 54
Delay, 33, 62, 98
Monitor, 18, 19, 57
Devices, 49, 58, 59, 60, 98, 117, 119
Move, 21, 29, 31, 33, 35, 62, 72, 97
Dynamic Grids, 63
Network, 11, 19, 103, 104, 105
Edit Mode, 52
Nodes, 11, 19, 58
Error stack, 57
Offline, 42, 49, 104
Exit, 53
On screen keyboard, 55
Flash Dynamic Grid Errors, 51
Online, 49
Free Group, 25
Orthographic, 67
Freeze, 69, 72
Query, 51, 54, 59, 60, 69, 70, 71, 72, 73, 93, Speed, 21, 30, 31, 33, 37, 62, 88, 97
99, 117
Speed mode, 21, 88
Query as you type, 51, 54
State, 14, 36, 38, 39, 41, 42, 50, 51, 53, 57, 72,
Query Home, 69 79, 88, 96, 99, 117, 119, 120
Redo, 42, 94, 100 Target, 29, 30, 33, 34, 35, 88, 97
Refresh, 43, 99 Time, 30, 31, 33, 62, 97, 98, 106
Resources, 80 Triggers, 37
Role, 47, 49, 51, 72, 73, 88, 96 Visual Creator, 120