, Obsession® II, ETCNet2™, EDMX™, Revolution® and Sensor+®,
are either registered trademarks or trademarks of Electronic Theatre Controls, Inc. in the
United States and other countries.
ETC permits the reproduction of materials in this manual only for non-commercial purposes.
All other rights are reserved by ETC.
ETC intends this document, whether printed or electronic, to be provided in its entirety.
Welcome to the Ion Operations Manual. This manual is a comprehensive resource for users of the
Ion control system.
Note:
For information on using show control with your system, see the Eos Family Show
Control User Guide, which is available for download at www.etcconnect.com
•Online Eos Family (Eos Ti, Eos, Gio and Ion) User Forums .8
.
Introduction1
Using this Manual
In order to be specific about where features and commands are found, the following naming and
text conventions will be used:
•Facepanel buttons are indicated in bold [brackets]. For example, [LIVE] or [Enter].
Optional keys are indicated in <angle brackets>, for example, <Cue> or <Sub>.
•Browser menus, menu items, and commands you must perform are indicated in bold text. For example: In the File menu, click Open. Or: Press [Record] [Preset] [Enter].
•Alphanumeric keyboard buttons are indicated in all CAPS. For example, TAB or CTRL.
•Keys which are intended to be pressed or held simultaneously are indicated with the
“and” symbol. For example, [Load] & [Timing Disable].
•Softkeys and clickable buttons in the Central Information Area (CIA) are indicated in
bold {braces}. A note about <More SK> (more softkeys): this command is always
indicated as optional, and is only indicated once in an instruction regardless of how
many pages of softkeys exist. This is because there is no way to predict what softkey
page you are on at any given time. Press <More Softkeys> until you find the required
command.
•References to other parts of the manual are indicated in italics. When viewing this
manual electronically, click on the reference to jump to that section of the manual.
Note:
CAUTION:
WARNING:
Please email comments about this manual to: TechComm@etcconnect.com
Notes are helpful hints and information that is supplemental to the main text.
A Caution statement indicates situations where there may be undefined or
unwanted consequences of an action, potential for data loss or an equipment
problem.
A Warning statement indicates situations where damage may occur, people may
be harmed, or there are serious or dangerous consequences of an action.
2Ion Operations Manual
Register Your Ion
Registering your Ion system with ETC ensures that you will be notified of software and library
updates, as well as any product advisories.
To register your console, you will need to enroll in “My ETC,” a personalized ETC Web site that
provides a more direct path of communication between you and ETC.
Register now at http://www.etcconnect.com/product.registration.asp
.
Help from ETC Technical Services
If you are having difficulties, your most convenient resources are the references given in this user
manual. To search more widely, try the ETC Web site at www.etcconnect.com
resources is sufficient, contact ETC Technical Services directly at one of the offices identified below.
Emergency service is available from all ETC offices outside of normal business hours.
When calling for assistance, please have the following information handy:
•Console model and serial number (located on back panel)
•Dimmer manufacturer and installation type
•Other components in your system (Unison
®
, other control devices, etc.)
AmericasUnited Kingdom
Electronic Theatre Controls Inc.Electronic Theatre Controls Ltd.
Technical Services DepartmentTechnical Services Department
3031 Pleasant View Road26-28 Victoria Industrial Estate
Middleton, WI 53562Victoria Road,
800-775-4382 (USA, toll-free)London W3 6UU England
+1-608 831-4116+44 (0)20 8896 1000
Before using Ion, you should read and familiarize yourself with the concepts defined below. You will
find that understanding these terms and concepts will improve your efficiency with Ion.
Channel = Fixture
A fixture is defined as a group of related addresses that together control a device. An
examples of a fixture would be an ETC Revolution. This moving light contains 31
parameters that together allow you to perform various functions such as pan and tilt. Each
of these attributes is addressed by a different output.
Ion treats fixtures and channels as one and the same. Unlike former ETC consoles where
a fixture occupied one channel for each parameter, Ion assigns each fixture a single
channel number. Individual parameters are then associated with that channel as additional
lines of channel information.
Output
Outputs are the method by which level changes to channels are conveyed to attached
devices. These outputs are patched to channels. In its simplest form, an output is the data
signal sent from the console to turn on a light or modify a fixture parameter.
Record Target
A record target is any data location that you can store data using a [Record] or [Record
Only] command. Examples of record targets are cues, palettes, presets, and macros.
Move Instruction
A move instruction is any change to a parameter from its previous stored value. Any change
to a channel’s intensity is a move instruction. Any change to a channel’s pan or tilt is a move
instruction. Any change to a channel’s color mixing is a move instruction, and so on.
Manual Data
Manual data is any value set for a channel via the command line. Manual data will remain
at its value until a move instruction is provided for it.
Syntax Structure
Most instructions can be entered into Ion through the command line. The Ion command line
expects instructions to be entered in a specific structure, or syntax.
Generally speaking, the order of syntax can be described as:
•What are you trying to affect? (Channel, group)
•What do you want it to do? (Change intensity, focus, pan and tilt)
•What value do you want? (Intensity at full, Iris at 50)
Naturally other commands will be used in the course of programming your show, but most
other functions are modifiers of these three basic steps: modifying the channel(s) you are
are working with, determining what parameters of those channels you are impacting, and
what value you want them to assume. When working with record targets, the syntax is
similar.
Note:
4Ion Operations Manual
Not all actions on Ion must be entered from the command line, although many will
result in a command line instruction. Other actions bypass the command line
entirely.
Enter
Since the command line can receive multiple edits and instructions at once, it is necessary
to let Ion know when you have completed your instruction in the command line. This is done
with the [Enter] key.
There are some commands which are self-terminating, and therefore do not require [Enter]
to be pressed. Some (but not all) of these commands are:
•[Out]
•[Shift] & [+]
•[Shift] & [-]
•[Full] [Full]
•Actions from the direct selects
Parameters and Parameter Categories
Ion divides fixture parameters into four major parameter categories: Intensity, Focus, Color, and
Beam. These are the parameters in each category:
•Intensity . . . . . . . . . . Intensity
•Focus . . . . . . . . . . . . Pan and Tilt
•Color. . . . . . . . . . . . . All color parameters (such as color wheel, CMY, scrollers, and
so on).
•Beam . . . . . . . . . . . . Any parameter not covered in the other categories.
Tracking vs. Cue Only
Ion is, by default, a tracking console. This means two things. First, tracking relates to how
cue lists are created. Once data is in a cue list, it will remain a part of that cue list, at its
original setting, and track forward through subsequent cues, until a new instruction is
provided or until it is removed from the cue list using filters or null commands.
Secondly, tracking relates to how changes to cue data are handled. Unless otherwise
instructed by a Cue Only command, changes to a parameter in a cue will track forward
through the cue list until a move instruction (or block command) is encountered.
It is possible to change the default setting of Ion to “Cue Only”. This prevents changes from
tracking forward into subsequent cues, unless overridden with a track instruction.
Ion also has a [Cue Only/Track] button that allows you to record or update a cue as an
exception to the default setting. Therefore, if the console is set to Tracking, the button acts
as Cue Only. If console is set to Cue Only, it behaves as a Track button.
Introduction5
Move Fade
Move Fade is a lighting control philosophy which determines how cues are played back. Ion
adheres to this philosophy.
In a Move Fade system, parameters do not change from their current setting until they are
provided a move instruction in a cue or are given a new instruction manually.
For example, in cue 1, channel 1 has been given an intensity value of 50%. This value does
not change until cue 20, where channel 1 is moved to 100%. Therefore, channel 1 has a
tracked intensity value of 50% in cues 2-19. If the user applies a manual intensity value of
25% while sitting in cue 5 (for example), that channel will stay at 25% until Cue 20 is
recalled - because 20 is the next cue in which channel 1 has a move instruction. The
original intensity of 50% will not be reapplied in subsequent cues unless specifically called
out by the cue or manually performed.
Cue List Ownership
Ion is capable of running multiple cue lists. In a multiple-cue-list console, cue list ownership
is an important concept. Cue list ownership is determined by the cue from which a channel
is currently receiving its value. In Live, a parameter is considered to be “owned” by a cue
list when it is receiving its current value from that cue list.
When alternating between cue lists in sequential playback, an active cue list does not
necessarily own a channel unless that list has provided the last move instruction for that
channel. For example, assume a channel is owned by cue list 1 and is at a tracked value.
If a cue from another cue list is executed and provides a move instruction for the channel
in the new cue, the channel is now owned by the second cue list. It will not return to cue list
1 until that cue list provides a move instruction for the channel.
Assert may be used to override this default behavior, allowing a cue list’s control over a
channel to resume, even when the channel’s data is tracked.
This rule is not followed when executing an out-of-sequence cue. An out-of-sequence cue
is any cue that is recalled via “Go To Cue”, a Link instruction, or manually changing the
pending cue. In general applications, the entire contents of the cue (both moves and tracks)
will be asserted on an out-of-sequence cue.
Block vs. Assert
In previous ETC consoles, placing a block instruction on a channel was a way to treat a
tracked value as a move instruction, both in editing and playback. In Ion, this behavior is
now split up. Blocked channel data is an editing convention only, and it prohibits tracked
instructions from modifying the associated data. Blocked data has no impact on playback;
the channels will continue to play back as though they were tracks. Assert is used to force
playback of a tracked/blocked value.
6Ion Operations Manual
Live and Blind
Live and Blind are methods to view and edit data in your show files. When you press the
[Live] key, the screen will show you the live display. When you press [Blind], you will see
the blind display. In either case, you may use the [Format] key to alter how the data is
displayed (see Using [Format], page 39).
When in Live, the data displayed represents the data being sent from the console at that
moment. In other words, the parameter data that is “live” on stage. When you edit data in
live, those changes will become active and visible on stage as soon as the command line
is terminated.
When in Blind, the data displayed represents data from the record target you choose to
view (cues, presets, palettes, and so on). When you edit data in Blind, changes will not
automatically appear on stage, since the data you are modifying is not live. This is true even
if the record target you are modifying is active on stage. It is possible to play a cue in Live,
then switch to Blind and edit that cue in blind without affecting levels on stage. Edits in Blind
do not require a [Record] command to be stored. They are considered stored when the
command line is terminated. Any display that is not the Live display is considered Blind, and
the Blind LED will be illuminated. For example, if you open patch, the blue LED on [Blind]
will be lit to show that you are in a Blind display.
HTP vs. LTP
HTP (Highest-Takes-Precedence) and LTP (Latest-Takes-Precedence) are terms used to
define the output of a channel parameter that is receiving data from multiple sources. In
HTP, the highest level of all sources will be executed. In LTP, the most recent level received
will be executed. Cue lists and submasters can operate as HTP or LTP for intensity
parameters only. Non-intensity parameters (NPs) are always LTP. Submasters can operate
as HTP or LTP for intensity. The default is HTP. Ion’s default cue list setting for intensity is
LTP (see HTP/LTP, page 209). Ion’s default submaster setting for intensity is HTP.
HTP
LTP
HTP is only applicable to the intensity of a channel. HTP channels will output the level that
is the highest of all inputs. HTP channels are also referred to as “pile-on”, because as
control inputs are added (for example - you may bring up cues and multiple submasters that
all have the same channel recorded at various levels), the system calculates which input
has the highest level for that channel and outputs that level for the channel. As control
inputs are removed (you pull some of the submasters down to zero), the console will adjust
the channel level, if required, to the highest remaining level.
LTP is applicable to any parameter of any channel. LTP output is based on the most recent
move instruction issued to the channel parameter. Any new values sent to the channel will
supersede any previous values, regardless of the level supplied.
Ion determines the LTP value for a channel, which is overridden by any HTP input values
that are higher than the LTP instruction. This is then finally modified by manual control.
Introduction7
Other Reference Materials
Help System
A keyhelp system is also contained within your system. To access help, press and hold [Help] and
press any key to see:
•the name of the key
•a description of what the key enables you to do
•syntax examples for using the key (if applicable)
Note:
Keyhelp is included on most tangible action buttons on your Ion console. This
includes most softkeys and clickable buttons as well as the traditional keys on the
keypad.
As with hard keys, the “press and hold [Help]” action can be also used with
softkeys and clickable buttons.
Online Eos Family (Eos Ti, Eos, Gio and Ion) User Forums
You are encouraged to visit and participate in the ETC Eos Family (Eos Ti, Eos, Gio and Ion) User
Forum, accessible from the ETC web site (www.etcconnect.com
online community of Eos, Eos Ti, Gio, and Ion users where you can read about other users’
experiences, suggestions, and questions regarding the product as well as submit your own.
To register for the ETC Family (Eos Ti, Eos, Gio and Ion) User Forum:
Step 1:Go to ETC’s community web site (www.etcconnect.com/community
page to the online community will open.
Step 2:You may register for the forum using the “register” link in the introduction or by
clicking the “join” link in the upper right corner of the page.
Step 3:Follow the registration instructions provided by the community page.
). This gives you access to an
). An introduction
8Ion Operations Manual
Chapter 1
System Overview
Inside this chapter you will find general descriptions of your Ion control console, how it fits into a
network control system, and the various areas of user interface.
Ion is designed from conception as a fully integrated controller for conventional lights and
multi-parameter devices (for example: moving lights, LEDs, color scrollers, gobo wheels). Attention
to detail across all areas of the system design and architecture allows you the utmost flexibility and
customization of use.
Ion allows designers and programmers to develop a mutual vocabulary for control. This
implementation of simple and uniform syntax for control provides a solid foundation for both
experienced and inexperienced users.
Remote Processor Unit (RPU)
The RPU can be used as the primary, backup processor for the system, a client, or for primary
playback in installations that do not require a facepanel after initial programming is completed.
For more information, see the appendix Remote Processor Unit (RPU), page 383.
Remote Video Interface (RVI)
The remote video interface allows remote interaction with the lighting control system. This can be
for display purposes only. Additionally, with a mouse and alphanumeric keyboard attached, the RVI
can be used as a remote programming station. The RVI provides supports for a maximum of two
DVI or SVGA monitors, 1280x1024 minimum resolution.
For more information, see the appendix Remote Video Interface (RVI), page 379.
Radio Focus Remote (RFR)
The RFR provides wireless control of key front panel functions.The base station for the RFR can be
networked into the system, or can connect to a console or remote device using the USB interface.
For more information, see the appendix Remote Control, page 377.
iRFR and aRFR
The iRFR and aRFR provide wireless control of key front panel functions.See “iRFR” on
page 388.See “aRFR” on page 388.
10Ion Operations Manual
Gateways
Ion is part of a fully networked system capable of direct output of both ETCNet2 and Net3.
Gateways can be configured to listen to either ETCNet2 or Net3 and provide interface to devices in
the lighting system that do not accept network communication directly. Gateways are provided for
DMX/RDM output, show control input and output and analog input and output.
• Net3 to DMX/RDM gateways are provided with a maximum of four outputs, which can be
male, female, or terminal strip.
Note:
• Show Control Gateway supports MIDI In/Thru and Out and SMPTE In.
• I/O Gateway supports 24 analog inputs, 16 SPDT contact closure outputs, and RS-232 serial
protocol.
Net3 Gateways only support RDM when in Net3 mode.
1System Overview11
Console Geography
Parameter category/
encoder page buttons
Power button
USB port
Level
wheel
Navigation keys
Paged encoders
Control
keypad
Playback
controls
LCD screen
Blackout and
Grandmaster
Softkeys
VGA port
DVI video
ports
IEC receptacle
MIDI Out and In
Hard power switch
Ethernet
port
DMX ports
1 and 2
USB
ports
Remote
trigger
port
Phone
Remote
Port
Current Ion
Rear panel
Audio Ports
(not currently
supported)
VGA port
(blue)
Dual DVI video
port (white)
IEC receptacle
MIDI Out and In
Hard power switch
Ethernet
port
DMX ports
1 and 2
USB
ports
Remote
trigger
port
Phone
Remote
Port
Original Ion
Rear panel
Audio Ports
(not currently
supported)
Below is a diagram of the Ion console with references made to specific areas of use. The terms and
names for each area and interface are used throughout this manual.
12Ion Operations Manual
Terminology
Power Button
The power button on the front of the console is used to power up or power down. A separate power
switch, located in the rear panel, can be used to disconnect power from the console’s internal
components.
WARNING:
Before servicing Ion, you must switch off the power on the rear panel and
disconnect the power cord completely.
USB Ports
One USB port is provided on the front of the console to connect any USB storage device. An
additional USB ports on the rear panel can be used to connect peripherals such as an
alphanumeric keyboard, pointing device, or touchscreen control for external monitors.
.
CAUTION:
The USB ports cannot be used for charging devices such as cell phones.
Encoders
Encoders and the LCD (see below) for control of non-intensity parameters are provided at the top
center of the console. The four encoders are pageable controls, which are populated on the LCD
with the parameters used in your show.
LCD
This display accompanies the CIA as an additional user interface. This LCD offers you softkeys,
encoder information, and an additional view of the command line.
Load
The load button is located above the fader pair at the bottom of the LCD and is used to load the
specified cue.
Control Keypad
The control keypad area is divided into three general sections including record targets, numeric
keypad and modifiers, and special function controls.
Level Wheel
Adjusts intensity for selected channels. It also provides scrolling and zoom functions in various
modes.
Navigation Keypad
Used for quick access to the live and blind displays, format, paging, and navigation within displays.
Parameter Category/ Encoder Page Buttons
Parameter buttons are used to select parameter categories and change encoder pages. To post a
parameter category to the command line, use [Shift] & [Encoder Page Button].
IEEE Ethernet 802.3 Ethernet Port
Ethernet port for connection to a network switch, network gateways, and accessory devices.
1System Overview13
Littlites
Littlite XLR 3-Pin Female Connector
1
2
3
®
You may connect a Littlite to the side of your Ion console.
Dimming Littlites
Attached desk lamps can be dimmed either with the desk lamp control knob on the side of the
console, or from the software.
Desk lamp controls are found in Setup>Desk>Brightness Settings. The {Desk Lamp} slider has
a range of 0% (dimmest) to 100% (brightest). The default setting is 0%. The console will set the
desk lamp to this setting on startup of the application. See “{Brightness Settings}” on page 108.
The desk lamps can also be controlled by holding down [Displays] and rolling the level wheel.
Cleaning Ion
Should the exterior or LCD of your Ion require cleaning, you may gently wipe them with a
dampened (not dripping
If this does not clean the console sufficiently, you may apply some window cleaner (containing
ammonia is fine) to the cloth and repeat the process until clean.
Outputting DMX
In order to output levels from Ion, you can either use the DMX ports on the back of the console, or
to output over a network, you may connect a Net3 gateway or Net2 node. If your devices receive
Net3 or ETCNet2 directly, no gateway or node is required.
Ion has two DMX ports. To output, connect one 5 pin XLR cable per port. The first port will default
to outputting the first universe of DMX, addresses 1-512, and the second port to the second
universe, outputting addresses 513-1024. See Local DMX Outputs, page 351 for information on
reconfiguring the DMX ports.
Nodes and gateways will function with Ion out of the box without previous configuration. However if
custom configuration is required, you will need to use either NCE (Network Configuration Editor) or
GCE (Gateway Configuration Editor). GCE is installed on Ion by default and can be accessed in
ECU>Settings>Maintenance>Gateway Configuration Editor (GCE). NCE can be installed on
the console or a Windows
For more information on Net3 gateways or Net2 nodes, see the product literature that accompanied
the hardware or download it from our website at www.etcconnect.com.
), non-abrasive paper towel or soft cloth.
®
PC for configuration.
14Ion Operations Manual
Loading...
+ 410 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.