Wheatstone GSX Troubleshooting guide

1
GSX D IGITAL A UDIO C ONSOLE
Networked AoIP Broadcast Console
Installation Guide & User Manual
Designed & built by
New Bern, North Carolina, U.S.A.

2
Publication Information
©2021 Wheatstone Corporation
Wheatstone considers this document and its contents to be proprietary and confidential. Except for making a reasonable number of copies for your own
internal use, you may not reproduce this publication, or any part thereof, in any form, by any method, for any purpose, or in any language other than English
without the written consent of Wheatstone Corporation. All other uses are illegal.
This publication is designed to assist in the installation and use of the product as it exists on the date of publication of this manual and may not reflect the
product at the current time or an unknown time in the future. This publication does not in any way warrant description accuracy or guarantee the use for the
product to which it refers.
Wheatstone reserves the right, without notice, to make such changes in equipment, design, specifications, components, or documentation, as progress may
warrant, improving the performance of the product.
Trademarks
Product names and other appropriate trademarks, e.g., GSX, WheatNet®-IP, VoxPro®, and Vorsis®are registered trademarks of Wheatstone. Microsoft®and
Windows®are registered trademarks of Microsoft Corporation. All other trademarks and trade names are the property of their respective companies.
Customer Service Contact Information
Wheatstone
600 Industrial Drive
New Bern, NC 28562 USA
For technical support, including on-site service, general product training, repair, and parts, contact Wheatstone through our webpage
(www.wheatstone.com), through email at [e-mail], or by phone [phone]).
Manual Revisions
pre-release, February 2021
initial release, March 2021 (revision A)

3
TABLE OF CONTENTS
❖Publication Information .......................................................... 2
❖Safety Instructions & Hazard/Warning Labels ..................... 4
❖1 –Introducing the GSX Console ............................................ 5
GSX Overview ............................................................... 6
Warranty Statement .................................................... 8
FCC Compliance Statement ......................................... 8
❖2 –GSX Hardware Installation ............................................... 9
Locating the GSX Components ................................... 9
Mix Engine Connections .............................................. 11
GSX Console Power Up ................................................ 12
❖3 –GSX Apps and Console Configuration ............................. 13
GSX Software Apps ...................................................... 15
Using the Navigator App.............................................. 15
GSX Surface Setup App ................................................ 30
Using the GSX GUI ........................................................ 36
❖4 –GSX Operation and Applications ..................................... 48
GSX Surface Operation ................................................ 48
GSX Mix Engine Controls ............................................. 55
GSX HDMI 1080P Monitor ............................................ 55
Using the GSX Console ................................................. 57
GSX Applications .......................................................... 66
❖5 –GSX Service Information ................................................... 69
❖Appendix A –Creating a WNIP Network .............................. 73

4

5
1 INTRODUCING THE GSX CONSOLE
hanks for joining the growing ranks of broadcasters
employing Wheatstone products, designed and built at our
factory in New Bern, NC. To obtain the maximum benefit
from the GSX console’s capabilities, please read through this
Introduction chapter along with Chapters 2 and 3 prior to installing your
new GSX console.
For those in a hurry, the GSX Quick Guide has a summary of the
physical connections, software setup applications, basic Surface
operations, and the HDMI monitor views. The Quick Guide ships with the
console (a PDF version is included on the USB flash drive that also ships
with the GSX console). All GSX and Wheatstone documentation can also be
downloaded from www.wheatstone.com (Support & Downloads).
Your new GSX console consists of these main components:
❖GSX-12 or GSX-24 Surface –This part is commonly referred to as
the “console”since it sits on the countertop and has all board operator
controls. Figure 1-1 shows a GSX-1212 Surface, but every GSX Surface
includes these features:
Four-Fader Input Panels –GSX uses separate Input Fader Panels,
each with four fader channel strips per field-replaceable panel. A GSX-
12 frame can hold up to three Input Panels while the GSX-24 frame can
hold up to six Input Panels. Every fader channel strip has a 100 mm
conductive plastic fader plus ten push buttons, some with programma-
ble color LEDs, for Channel On, Channel Off, Talkback, Cue, bus assigns
for PGM, AUD, AUX, and OL, Set, and Mode. One color Organic Light
Emitting Diode (OLED) channel info display and a rotary encoder with
push-to-take for on-the-fly channel source selection round out the fad-
er channel controls.
❖Headphone output –A board operator headphone amp is included in
the GSX Surface with a ¼” TRS jack on the right side of the chassis, in-
line with the OLED displays.
❖Master/Monitor Panel –This three-slot wide panel has the controls
for the control room, the operator headphones, and a talk studio. There
are also eight Spare buttons available to take Salvos, function as talk-
back controls, take additional Events, etc.
❖Accessory Slots –GSX-12 frames have a 1-slot wide blank panel
(BKN). When removed, an SS8-GSX 8-button OLED control panel
(shown in Figure 1-1) or an SS4-GSX 4-button panel can be installed.
GSX-24 frames have three slots, covered by a BKN and a BKW dual-
width blank panel to allow multiple single-width SS4-GSX or SS8-GSX
button panels and/or a dual-width scriptable panels to be installed.
Figure 1-1 GSX-1212 Surface
❖Mix Engine Blade –The 1RU Mix Engine Blade (Figure 1-2) contains
the Surface Host processor, the console’s DSP for signal mixing and
control, and the WheatNet-IP (WNIP) system interface. Its front panel
has sixteen meters for monitoring internal console signals, with various
logic and status LEDs, two OLED displays, with a rotary encoder and
two buttons, for menu selection and local control of the Mix Engine
Blade. A front panel headphone jack allows one to monitor almost any
source in your WNIP system.
Figure 1-2 Mix Engine Blade, front panel
❖PS-1600 Power Supply –A 1RU 16V DC supply powers the GSX
Surface using a 16-foot PS-1600 power cable. A redundant DC power
jack on the Surface allows for adding another PS-1600 and PS-1600
cable for redundant power (optional feature). The connections on the
power supply’s rear panel are shown in Figure 1-3.
Figure 1-3 PS-1600 Power Supply, rear connections
T

6
❖Installation Kit –The GSX shipment includes: two IEC AC power
cords for the Mix Engine Blade and the PS-1600 supply, a PS-1600 DC
cable, and a USB thumb drive with the PDF documentation files and the
software installers for Navigator-3 and the GSX Surface Setup app
(GSX GUI), the two software apps used configure the GSX console.
Note: Navigator is a licensed application. A 30-day trial license is
included with your GSX console purchase. Contact Wheatstone
technical support (page 2) to obtain your Navigator trial license.
To continue using all Navigator features, beyond the 30-day trial
period, requires purchasing a Navigator-3 license from Wheatstone
sales or from an authorized Wheatstone dealer.
GSX OVERVIEW
The GSX console is a compact AoIP (Audio over Internet Protocol)
broadcast or production console using the WheatNet-IP (WNIP) networking
protocol. Designed for 24/7 operation, the console has two main hardware
components: a 1RU rackmount Mix Engine Blade, and the GSX Surface,
a countertop board operator hardware controller. The Surface, PS-1600
power supply, and the Mix Engine Blade are all fully FCC and CE certified.
The GSX is a sister to Wheatstone’s flagship console, the fully field-
programmable LXE console. The GSX is scaled-down for use in smaller
broadcast studios, newsrooms, production studios, and remote trucks.
Cosmetically resembling the LXE, but with a smaller footprint, the GSX
uses a customer supplied 1080p HDMI monitor for level metering and
advanced console control. Although the standard GSX models do not have
access to any of LXE’s most advanced features, four software licenses are
available for the GSX GUI to add these advanced features at any time:
•A GSX Panel Layout License allows one to change the function of just
about every Surface knob, button, or fader from its default
assignment to one of twenty-five common control functions. It also
allows one to customize the Surface’s color OLED displays.
•A Scripting License integrates the ScreenBuilder™ UI to create your
own Custom Views on the HDMI monitor using drag-and-drop
objects and the built-in scripting wizard in the GSX GUI. This license
also allows adding scripting to the Surface controls.
•A Panel Layers License increases the flexibility of the console by
adding the Layers feature where up to eight control layers can be
setup for very advanced console control. Layers are especially useful
when doing remote live broadcasts with lots of live mics which must
be quickly setup for different scenes or shows.
•An Automix License activates the Automix View where multiple
sources, like several mics in a talk studio can be assigned to be
“auto-mixed” for automatic level control using signal weighting to
keep guests from talking over the host and to duck mics which are
not actively in use. Automix is also valuable for TV news where audio
from video playbacks can be “auto-mixed” to yield consistent levels.
•The optional Remote GSX client software, when run on a remote
laptop or desktop, mirrors, and remotely controls, the physical GSX
console at the station.
The GSX can be networked with any WNIP audio network, an AES67-
compatible AoIP system with end-to-end audio transport and logic control,
with an audio toolkit at every I/O point in the network, to enable
exceptionally intelligent deployment and operation.
Note: Your GSX console must be networked with one or more
WheatNet-IP Blades, running v3.8.26 or later software, to
provide audio I/O and add additional logic I/O, since the GSX Mix
Engine and Surface do not have any audio inputs and outputs—
outside of their headphone jacks and the built-in cue speaker.
Appendix A has an overview of networking your GSX console with
one or more Blades using Gigabit Ethernet switches configured for
AoIP operation.
The Navigator and GSX GUI applications, when installed on any current
Windows PC/server networked with the GSX and your I/O Blades, are used
to configure the GSX for use in an on-air studio, a production room, a
newsroom, or for use in other live broadcast or streaming applications.
Chapter 3 covers how to install and use these two software apps to
configure your GSX.
The GSX Surface
The GSX Surface has two frame sizes: the GSX-12 is available with eight
or twelve fader channels, while the GSX-24 frame is available with sixteen,
twenty, or twenty-four fader channels. Four fader channels are on each
Input panel which plugs into a Panel Host board using a keyed ribbon
cable for easy field replacement with minimal interruption to operations in
case of spills or other damage to the Surface controls. The Master/Monitor
panel also uses a single ribbon cable that also plugs into the Panel Host
Board.
Figure 1-4, on the next page, shows the right-end of a GSX Surface with
one Input Panel, the Master/Monitor Panel, and an SS8-GSX OLED control
panel, an optional panel that can be installed in the GSX accessory slots.
Each fader channel has a rotary encoder at its top so the board operator
can select between the audio sources available on each fader. There are
two user-defined buttons (default settings: Set and Mode) and four bus
assign buttons directly below the encoder. A color OLED channel status
display shows the current channel source name along with other
information about the channel’s source, like its format, whether that
channel is controlling logic associated with the audio source, whether a
monitor destination is being muted, etc. TB and Cue buttons are located

7
below the OLED display. A 100 mm conductive plastic fader and the
channel on and off buttons complete the channel strip controls.
Each fader channel may be assigned to any combination of the Program,
Audition, Auxiliary, and Offline busses using the four channel assignment
buttons. Channels are assigned to the secondary busses (four Mix-Minus
and/or four Aux Sends) using the HDMI monitor on-screen controls
(touchscreen or mouse-driven). The fader channel strip controls are
identified in Figure 4-2, on page 48.
Figure 1-4 Surface Controls
The Master/Monitor Panel has three columns of controls. These are
identified in Figure 4-4, on page 52. The left column has the Control Room
speaker controls with the four top buttons or the encoder selecting the
source feeding the Control Room’s monitor output. The middle column
controls do the same for the board operator headphone output, although
the headphones can also be set to Follow the CR Monitor source selection.
A Spilt Cue button controls how cue is fed to the headphones: in stereo or
in split mode with cue in one ear and monitor in the other (whether cue is
switched into the headphones is set in the GSX GUI).
The right column has the talk studio controls along with timer, two Event
select buttons, eight user-defined Spare buttons and cue volume control.
The studio monitor controls include a source selector, Studio volume
control, and a Talk to Studio button (TB).
The three Master/Monitor OLED displays show the current levels of the
CR, HP, Cue, and Studio outputs and their status (a red X over a bar graph
icon indicates that output is currently muted). When the encoders are used
to assign sources to the various programmable buttons, these displays list
the available or visible sources for that monitor. The Select encoder in the
left column selects and takes a “wild source” for the CR monitor output.
The Select encoder in the right column selects and takes the monitor
source for the Studio monitor output.
Because program audio flows through the Mix Engine and not the
Surface—except for the audio going to the Surface’s headphone jack and
cue speaker, the Surface could be separately powered down from the Mix
Engine without affecting program audio.
Mix Engine Blade
The Mix Engine Blade has the DSP to control, process, and mix the GSX
audio. It doesn’t have any audio inputs or outputs, other than a front
panel headphone jack. As viewed from the rear (Figure 1-5), the Surface
Host Processor connections are on the left. The Surface Host Processor
gets power from the Mix Engine Blade only, so it has its own Ethernet
connection to a 1GB Ethernet switch port, configured as an access port.
The HDMI port connects to the customer supplied 1080p monitor along
with two USB ports for connecting a touchscreen or a mouse and a
keyboard to select and control the GSX’s advanced controls on the
monitor.
On the right side are the Mix Engine Blade connections: three RJ45 jacks
and an AC input. The 1GB Ethernet jack connects the Mix Engine Blade to
a 1GB Ethernet switch port (configured as an access port). The two Logic
jacks have 12 GPIO connections for local control of hot mic LEDs and the
control room on-air tally.
Figure 1-5 Mix Engine Blade, rear panel

8
WARRANTY STATEMENT
LIMITED WARRANTY BY WHEATSTONE CORPORATION
1. All equipment sold and shipped to final destinations within the USA and its
possessions warranted for one (1) full year from the date of purchase against
defects in material and workmanship. All equipment sold and shipped to final
destinations outside the U.S.A. and its possessions warranted for one (1) full
year from the date of purchase against defects in material and workmanship.
All repairs to maintain the unit at original specification will be made at no
charge to the original purchaser, except for shipping and insurance costs to be
prepaid by the owner to the factory in the event the unit cannot be serviced by
an authorized Wheatstone Corporation dealer.
2. This Warranty is subject to the following restrictions and conditions:
a) Owners can register their products online at www.wheatstone.com.
Expand the top menu item “Support & Downloads”and select “Register
Product,” near bottom of list or, at the time of servicing, the owner must
provide proof of purchase from an authorized Wheatstone distributor or
dealer.
b) This Warranty is valid for the original purchaser on the unit. Parts used for
replacement are warranted for the remainder of the original warranty peri-
od. Repair or replacement is in the discretion of Wheatstone Corporation
and is the exclusive remedy hereunder.
c) This Warranty DOES NOT apply to damage or defects resulting from abuse,
careless use, misuse, improper installation, electrical spikes or surges, or
alteration, repair, or service of the unit or equipment by anyone other than
Wheatstone Corporation or its authorized dealer.
d) This Warranty is void if the serial number has been removed, altered, or
defaced.
e) This Warranty DOES NOT cover loss or damage, direct or indirect, arising
out of the use or inability to use this unit or for shipping or transportation
to any dealer.
f) Wheatstone Corporation reserves the right to modify or change any unit in
whole or in part at any time prior to return delivery to incorporate electron-
ic or mechanical improvements deemed appropriate by the Wheatstone
Corporation but without incurring any responsibility for modifications or
changes of any unit previously delivered or to supply any new equipment in
accordance with any earlier specifications.
g) THERE ARE NO OTHER WARRANTIES, EXPRESSED, IMPLIED, OR STATUTO-
RY, INCLUDING ANY WARRANTIES OF MERCHANTABILITY OR FITNESS FOR
A PARTICULAR PURPOSE. IF FOR ANY REASON, ANY IMPLIED OR STATU-
TORY WARRANTY CANNOT BE DISCLAIMED, THEY ARE LIMITED TO THIRTY
(30) DAYS FROM THE DATE OF PURCHASE. WHEATSTONE COPORATION IS
NOT RESPONSIBLE FOR ELECTRICAL DAMAGE, LOSS OF USE, INCONVEN-
IENCE, DAMAGE TO OTHER PROPERTY, OR ANY OTHER INCIDENTAL OR
CONSEQUENTIAL, WHETHER DIRECT OR INDIRECT, AND WHETHER ARIS-
ING IN CONTRACT, TORT, OR OTHERWISE. NO REPRESENTATIVES, DEAL-
ERS, OR WHEATSTONE PERSONNEL ARE AUTHORIZED TO MAKE ANY WAR-
RANTIES, REPRESENTATIONS, OR GUARANTIESS OTHER THAN THOSE EX-
PRESSLY STATED HEREIN.

9
2 GSX HARDWARE INSTALLATION
he GSX Surface has two frame sizes. The GSX-12 supports
up to three Input Panels (12 fader channels) while the GSX-
24 supports up to six Input Panels (24 fader channels). Each
GSX Surface includes a three-column Master/Monitor Panel.
Each control panel plugs into a Surface Panel Host board which has three
RJ45 Ethernet jacks: one to connect the Surface to a WNIP network switch
port, while the other two are available to connect power and Ethernet to
two accessory panels. GSX supports using SS4-GSX or SS8-GSX OLED
Smart Panels within the frame (Figure 4-1 on page 7 shows the SS8-GSX
OLED Smart Panel). GSX-12 frames support one smart panel while GSX-24
frames support up to three panels. The GSX Surface comes with a PS-
1600 power supply and a locking DC cable.
The GSX Mix Engine Blade holds the GSX Surface Host, an SBC (Single
Board Computer) running Linux, which drives a customer supplied 1080p
HDMI monitor for level display and advanced GSX control. Three customer
supplied Ethernet cables network the GSX Surface, GSX Surface Host, and
the Mix Engine to three WNIP system gigabit switch ports.
LOCATING THE GSX COMPONENTS
The GSX Surface is meant to set on a countertop with its palm rest
between six and twelve inches (15 to 30 cm) from the edge of the
countertop (Figure 2-1). This “setback” allows keyboards, mice, a VoxPro
controller, copy or log sheets, etc. to be set in front of the GSX Surface.
The Mix Engine (1RU) is rack mounted in a 19” rack located below the
countertop. We recommend adding 1RU vented panels above and below
the Mix Engine to ensure adequate ventilation. Since its front panel has
level meters and status displays, and a headphone jack for signal
monitoring, it should be placed in an accessible position. Its rear panel
must also be accessible to connect a 1080p HDMI monitor and the USB
cables for the touchscreen or mouse and keyboard, and the Ethernet
cables to connect the local logic and network jacks.
The PS-1600 power supply (1RU) is also rack mounted below the
countertop. There are no user controls on the supply, so it’s typically
mounted at the bottom of the rack. Place a 1RU blank panel above the
supply for ventilation since the supply is convection cooled.
A 16-foot locking DC cable (included) connects the GSX Surface to a
PWR OUT jack on the back of the PS-1600 Power Supply. This constrains
how far from the Surface the power supply can physically be located since
the locking DC cable must not be put under strain when connected
between the GSX Surface and power supply.
The Surface’s Ethernet port and the two Ethernet ports on the Mix
Engine’s rear panel must all connect to WNIP network switch ports using
straight-thru Ethernet cables (customer-supplied, CAT5e or CAT6 cables).
The GSX Surface is typically set on the countertop since its weight (16
lbs. for a GSX-1212 or 26 lbs. for a GSX-2424) and rubber feet should
hold it firmly in place. If the Surface needs to be fastened to the
countertop for security reasons, a step-by-step procedure is listed in the
next section Fastening the Surface to the Countertop, starting on page 10.
Figure 2-1 GSX Surface, Countertop Positioning
T

10
Two cables: a customer supplied CAT5e or CAT6 cable, and the supplied
DC power cable, must be run into the right side of the Surface to plug into
the Panel Host board. Two Cable Access openings are provided for these
cables thru the chassis: a rear panel opening and a bottom opening, as
shown in Figures 2-1 and 2-2.
For the cleanest installation, drill a one-inch hole thru the countertop to
align with the Cable Access opening in the chassis following these steps:
1. Set the GSX Surface onto the countertop with the palm rest set
parallel to the countertop edge, typically with a six to twelve inch
(15 to 30 cm) setback space.
2. On a GSX-12 frame, remove the accessory or blank panel and the
Master panel to view the cable access opening shown in Figure 2-2.
On a GSX-24 frame you’ll only need to remove the three accessory
or blank panels. Mark the countertop below the chassis opening.
3. Move the GSX Surface safely out of the way to drill a one-inch hole
thru the countertop.
4. Set the GSX Surface back into position aligned over the hole.
Fastening the GSX Surface to the Countertop
The GSX Surface can be fastened to the countertop using four #8 screws
or bolts. The stick-on rubber feet can be removed to yield the lowest
Surface profile or just left in place. Remove the left-most Input Panel and
remove the blank or accessory panel, if not already removed to drill a
cable access thru the countertop, to have access to the four corner chassis
holes shown in Figure 2-1 on the previous page. The right rear hole is also
identified in Figure 2-2. Mark the countertop thru the holes, then move the
GSX Surface safely out of the way.
If the countertop has a laminate top, use a new 1/4” drill bit to drill just
thru the laminate to ensure the #8 screw threads won’t touch the
laminate. This prevents future laminate cracks from forming. Use an 1/8”
drill bit to drill pilot holes for the four #8 screws. You could also drill a
thru-hole sized and use a #8 bolt to fasten the GSX Surface.
Set the GSX Surface back into place and use four #8 wood screws, with
washers and lock washers, to fasten the Surface to the countertop.
Tighten the screws just enough to hold the GSX Surface securely,
especially if the rubber feet were left on, since overtightening the screws
could distort the chassis. Reinstall the Input Panel by plugging in its ribbon
cable and setting it into the chassis before reinstalling its four screws.
Surface Cable Connections
Two cables need to be run into and connect to the GSX Surface: a
customer supplied Ethernet cable to connect the Surface to a WNIP gigabit
switch port and a DC cable (supplied) to connects it to the PS-1600 power
supply. These cables enter the right rear section of the Surface thru a rear
panel opening (a rear cosmetic cover must be removed to access this
opening) or thru a bottom chassis opening aligned with a hole drilled thru
the countertop. The cables plug into jacks on the console’s Panel Host
board, mounted to the bottom of the Surface chassis below the control
panels, as shown in Figure 2-2.
To use the rear panel cable access hole, remove the GSX Surface’s rear
cosmetic cover. Remove the Master Panel (four hex screws and one keyed
ribbon cable) and each blank panel (two or four hex screws) for access to
the Panel Host board jacks shown in Figure 2-2. The customer supplied
Ethernet cable (black cable in Figure 2-2) plugs into the RJ45 jack closest
to the rear panel. The DC cable (white cable in Figure 2-2) plugs into the
adjacent DC power jack, locking to it using a threaded collar on the plug.
A second DC jack is available for a redundant PS-1600 power supply.
If you’re installing an accessory panel into a GSX-12 frame, or one or
two accessory panels in a GSX-24 frame, short Ethernet cables are used to
connect them to the Accessory Panel RJ45 jacks on the Panel Host
board. Figure 2-2 shows a GSX-12 frame with one accessory panel
connected using a short blue Ethernet cable.
Note: Accessory panels are typically powered by the Panel Host
board. To apply power to the RJ45 jacks, a shunt must be installed
onto two-pin header J1 and/or J3, located behind each RJ45
Accessory Panel jack, as shown in Figure 2-2.
Figure 2-2 Panel Host Board Connections
Once the Panel Host connections are made, the Master Panel and blank
or Accessory Panel(s) can be reinstalled into the frame.

11
PS-1600 CONNECTIONS
Figure 2-3 shows the rear panel of the Surface power supply. The DC
cable can plug into any DC output jack. The plug has a locking collar to
securely fasten it to the threaded jack.
Figure 2-3 GSX Surface Power Supply, Rear Panel
MIX ENGINE CONNECTIONS
There are no audio connections on the Mix Engine other than the ¼” TRS
headphone jack on the front panel. The audio I/O for your GSX console is
supplied by one or more I/O Blades. The Blades’ inputs and outputs are
then cross-connected in Navigator to connect to the GSX console signals.
Audio inputs (sources) connect to the GSX fader channels and External
monitors (destinations), while the GSX busses, channel bus minus signals,
and CR and Studio monitor signals connect to audio outputs on one or
more I/O Blades or directly to a PC using an audio driver.
The Mix Engine’s rear panel (Figure 2-4) has two sets of connectors: the
left side has the GSX Surface Host jacks (Ethernet, HDMI, and two USB
ports), the right side has the Mix Engine jacks: Logic 1-6 and 7-12,
Ethernet (ETH 1G), and an IEC AC input.
The Surface Host’s Ethernet jack uses a customer supplied Ethernet
cable to connect to an access port on a managed gigabit Ethernet switch
configured for multicast audio streaming. The ETH 1G Mix Engine jack
connects the Mix Engine to another access port. Because it’s carrying
multiple streaming audio signals to/from the GSX it must be a CAT6 or
better Ethernet cable.
The Surface Host’s HDMI jack connects a customer supplied 1080p
HDMI video monitor or touchscreen. The two USB ports connect the
touchscreen or a USB mouse. A USB keyboard can also be connected when
User passwords are being used and to enter Event and Preset names. A
wireless transceiver could alternately be plugged into a USB port to
support a wireless mouse and/or keyboard.
The right side has the Mix Engine connections: the top two RJ45 jacks,
labeled Logic 1–6and 7–12, each have six LIO (Logic In/Out) ports per
jack. These LIO ports are also known as GPIO (General Purpose
Input/Output). Figure 2-5 shows the signals on each pin of a WNIP system
Logic jack.
Figure 2-5 Logic RJ45 Pin Outs & Signals
To simplify wiring for logic-controlled devices, a WNIP GPIO Logic
Adapter is available from NotaBotYet (www.notabotyet.com) which breaks
out the logic connections from one RJ45 logic jack to screw terminals so
multiple “old school” peripheral devices, like warning lights and hot mic
LEDs, can easily be wired to one Logic jack. The WNIP GPIO Logic Adapter
connects to a Mix Engine or Blade Logic jack using an Ethernet cable.
Figure 2-4 Mix Engine, Rear Panel Connections

12
GSX CONSOLE POWER UP
The Mix Engine, PS-1600 power supply, and WNIP Blades do not have
power switches since all are designed for continuous 24/7 operation. Each
is designed for AC mains supplying 90-240 VAC at either 50 or 60 Hz. For
the most reliable operation, all GSX components should only plug into
isolated ground circuits (identified by orange outlets in the USA). Using a
UPS (Uninterruptible Power Supply) is also recommended.
Plug the supplied IEC AC cords into the Mix Engine and the PS-1600, and
then plug the cables into AC outlets. It takes about 90 seconds for the GSX
console to boot up, connect to the WNIP network, and be ready for use.
Note: Larger gigabit switches can take ten or more minutes to
boot, configure its ports, and be ready for network traffic. If power
cycling all network components, wait for your switches to fully
come up, then power up your System and Route master Blades,
followed, after a minute or so, by the rest of the Blades and Mix
Engines in your system. You can then power up each Surface.
The Mix Engine’s front panel (Figure 2-6) has various level displays,
logic activity LEDs, and Status LEDs (Link, Route Master, and Clock
Master) along with two OLED displays, two select buttons, and a rotary
encoder. The LINK LED lights up solid green when the Mix Engine is
powered and its ETH 1G jack is connected to a network switch port. After
about 90 seconds, if that GSX Mix Engine is not connected to a network, or
does not detect any other devices, the ROUTE MASTER and CLOCK
MASTER LEDs will be lit solid green. Normally, the GSX is networked with
one or more other Blades so these both LEDs may be off, indicating other
Blades in the WNIP network are set as the Route Master and Clock Master.
In a WNIP system, one Blade will be designated as the Route Master while
a second Blade will be designated as the Clock Master.
If the red ERROR LED should ever light, it indicates an error condition
has occurred within the Mix Engine. To reset this error, first try rebooting
the Mix Engine using the Reboot Blade command in Navigator or use the
front panel controls to select Rebooting the Mix Engine. If the red LED
remains lit even after the Mix Engine is rebooted, power cycle the Mix
Engine. Unplug its IEC AC cord, wait five seconds or so, then plug the IEC
cord back in.
If the red Error LED again lights up after the Mix Engine powers up it
indicates a serious fault. Contact Wheatstone technical support for
assistance. See Chapter 5 (page 69) for information on obtaining service
and support for your GSX console.
The GSX Surface OLED displays show various start-up messages as the
Surface Panel Host and Control Panels boot up. Once the boards connect
to their GSX Surface Host, the OLED displays will show their default
settings, with NoSource shown on all channels on a new Surface. Once the
Surface is ready, moving a monitor fader or rotating the Studio pot will
update the levels shown in the Master/Monitor panel OLED displays. One
could also rotate a channel encoder to see the channel display switch to
show visible source names to verify the Surface is ready.
The GSX Surface Host in the Mix Engine must have a 1080p HDMI
monitor plugged into its HDMI jack to operate properly. The Surface Host
runs Linux, so various Linux-related messages may be displayed on the
monitor as the Surface Host boots. Once it finishes booting Linux, the GSX
system software is loaded and shortly thereafter the Home View is
displayed on the HDMI monitor (Figure 2-7).
Figure 2-7 Home View on the GSX HDMI Monitor
Figure 2-6 Mix Engine Front Panel

13
3 GSX APPS & CONSOLE CONFIGURATION
he GSX console doesn’t have its own physical audio inputs
and outputs, like WheatNet-IP consoles that use a Console
Blade with local I/O. The GSX has a Mix Engine, which
doesn’t have local audio I/O, other than a front panel
headphone jack, thus the GSX console’s destinations must be connected to
Blade or audio server inputs and the studio sources signals (Control Room
& Studio Monitors, the various bus outputs, bus minus signals, etc.) must
be cross-connected to Blade outputs.
Configuring your Mix Engine, Surface, and I/O Blade signals is done
using Navigator and the GSX Surface Setup app, Windows®programs
included on a USB flash drive that shipped with the console. The two apps
can also be downloaded on-line, but you’ll need to contact Wheatstone
Technical Support for the download links ([email protected]).
The Navigator and GSX Surface Setup (GSX GUI) are installed on an
admin PC, a Win7 or Win10 PC with two Network Interface Controllers
(NICs). The admin PC’s on-board NIC must be set to a fixed IP address to
communicate with the Mix Engine, the GSX Surface Host, and the system’s
Blades and other devices. That NIC connects to an access port on a WNIP
system gigabit switch. If your WNIP devices will use the factory-assigned
subnet (192.168.87.0), we recommend setting the admin PC’s NIC to
192.168.87.21 with a subnet mask of 255.255.255.0.
A second NIC is used for remote access to these WNIP apps, either by
being networked with your facility LAN or by a direct internet connection
thru an ISP. This NIC can even be a USB-to-NIC adapter which, for
security, could be unplugged anytime remote access is not required.
Once installed on the admin PC, Navigator is first used to edit the GSX
component settings, then edit the default I/O Blade signal names and
configure their audio inputs and outputs, setup logic control, and cross-
connect the GSX sources and destinations to I/O Blade inputs and outputs.
The GSX GUI app is used to configure the GSX Surface features and
functionality by assigning VDip (Virtual DIP Switch) logic controls to
selected audio signals, setting channel source Visibility lists, and setting up
board operator Users to set access to selected advanced console features.
To ensure both apps are installed properly, right-click on their installer
icon or file name and select “Run as Administrator.” Shortcut icons are
added to the desktop and the apps are added to the Windows Start menu.
On a Win10 PC, both apps are added to a Wheatstone folder and, for a
while at least, will appear in the Recently Added list in the Start menu.
New Mix Engines and Blades, when first powered after shipping from the
factory, start in Setup Mode where one assigns a Blade ID, which then sets
the IP address (detailed in the next section). The GSX Surface Host SBC
(Single Board Computer), mounted in the Mix Engine, is shipped set for
192.168.87.90. The GSX Surface, even though it connects to a WNIP
switch port, does not need an assigned IP address since it uses Link-Local
network addressing to communicate with its Surface Host.
Note: To prevent duplicate IP addresses and/or Blade ID numbers,
and the subsequent network communications issues this causes,
all WNIP device settings should be recorded in a spreadsheet
listing the device, its location, its IP address and, for Blades, the
Blade ID number.
The GSX Mix Engine and Surface Host can be set to use other Class B or
C subnets but, if possible, we recommend leaving them using the default
192.168.87.0 subnet. When a WNIP system is set for another subnet,
every default IP address, on every WNIP component, will need to be
changed to fall within the new subnet to be networked with an existing
system. This can complicate system troubleshooting and system
expansion, since all Wheatstone AoIP devices are shipped with IP
addresses set to use the 192.168.87.0 subnet at the factory (unless pre-
configuration is ordered with your hardware purchase).
We also recommend that the WNIP system be created using isolated
hardware switches and ideally, Cisco switches, rather than being
networked using VLAN 1 on your facility’s LAN switches.
GSX MIX ENGINE BLADE SETUP
As shipped from the factory, the GSX Mix Engine powers up in Blade
Setup mode (Figure 3-1).
Figure 3-1 Mix Engine Front Controls, in Setup Mode
T

14
Note: If you arranged with the factory to preconfigure your
system’s Device IDs and IP addresses, you can skip this section
since your Mix Engine will already be setup for your WNIP system.
To begin setting up your Mix Engine, touch any front panel control: press
the left or right arrow button or rotate the rotary encoder (the large
“knob”) to begin the Blade Setup procedure. A “setup wizard” will guide
you through making several choices regarding your WNIP system, which
appear in the right-hand display, allowing it to configure the Mix Engine for
your system based on your selections.
The first choice is setting the WNIP System Size between two choices:
❖1-99 Blades –The selection used for most systems. When selected,
the wizard automatically assigns network settings based on the select-
ed Blade ID (your next choice). An IP address is assigned to the Mix
Engine in the 192.168.87.0 subnet with the last octet being 100 plus
the selected Blade ID (i.e., .101 to .199). A subnet mask of
255.255.255.0 is set and the gateway is set to 192.168.87.1. If you’re
setting up a system which will never have more than 99 Blades, this is
your best choice.
❖100+ Blades –Select this choice if the GSX is part of a large, multi-
station system which will have over 100 Blades and PCs with audio
drivers all networked together. The wizard again assigns network set-
tings based on the Blade ID you select in the next step. For Blade IDs
of 1 to 99, the IP address is assigned to the 192.168.87.0 subnet with
the last octet being 100 plus the Blade ID (i.e., .101 up to .199) with a
subnet mask of 255.255.0.0 and a gateway set to 192.168.87.1. Blade
IDs from 100 to 199 are assigned IP addresses in the 192.168.88.0
subnet, with the last octet being assigned a value equal to the Blade ID
(i.e., .100 up to .199) with a subnet mask of 255.255.0.0 and the
gateway set to 192.168.88.1. If you’re setting up a system that has
more than 100 Blades, or if you suspect your system may someday
grow beyond 99 Blades, this selection is your best choice.
Note: The Mix Engine’s network settings can be manually edited,
using Navigator, after running the setup wizard if your GSX will
need to be set to use another subnet.
To make a choice rotate the knob to highlight the desired system size
then click the right arrow button to select that size. The wizard steps you
to the next selection: setting the Blade ID. Every Console Blade, Mix
Engine, I/O Blade, and PC/server with an audio driver is assigned a unique
Blade ID, from 1 up to 99, or from 1 to 199 for the 100+ Blade selection.
We recommend creating a spreadsheet to list all Blades and other
devices in your WNIP system to keep track of every device’s system
settings (mainly Blade Device number and IP address). For consoles, we
recommend starting with Blade 1 and going up sequentially. I/O Blade ID
numbers and audio driver ID numbers can be set in blocks above these
numbers, as required.
Rotate the knob to highlight the desired Blade ID number then press the
right arrow button to select the highlighted number. The wizard then
displays the results in the right display.
Press the right arrow button to advance to your next choice: System
Sample Rate. There are only two choices: 48K (48 kHz) or 44K (44.1
kHz). In general, select 44K if you’re in radio, select 48K if you’re in TV.
Use the knob to highlight your desired sample rate then press the right
arrow button to select your choice.
Note: The sample rate setting is easily changed later using
Navigator, if required.
The setup wizard now applies your choices and reboots the Mix Engine to
use the new settings. The right front panel display shows this process
(Figure 3-2) which takes about 90 seconds.
Figure 3-2 Mix Engine Front Controls, Entering the System
Once the Mix Engine reboots and joins the WNIP system, the front panel
displays show the Mix Engine’s System Info (Figure 3-3). The left display
shows the selected Sample Rate and whether that Blade is the system’s
Route or Clock master, its Name and Blade ID number, whether it’s
communicating with the WNIP system (the green RJ45 jack symbol), and
its CPU temperature. The right display shows a mini signal level meter, the
Mix Engine’s IP address, and the amount of time the Mix Engine has been
powered up (its Runtime).
Figure 3-3 Mix Engine Front Controls, System Info Displays
When the front panel controls sit idle after a specified time, or the left
arrow button is pressed from the System Info displays, a Screen Saver
(Figure 3-4 on the next page) gets applied to both displays since OLED
displays are sensitive to burn-in when left showing a static display for a

15
long period. Navigator has a Blade Display Setting section on its Info tab
to sets how long to wait after the panel controls are idle to turn on the
Screen Saver and/or to dim the two OLED displays.
Figure 3-4 Mix Engine Front Panel, Display Screen Savers
When the screen saver is active, touching any front panel control
(pressing the left or right arrow button or rotating the knob) switches the
displays to show a WheatNet-IP logo and the main menu screen (Figure 3-
5). To show the System Info displays, press the left arrow button twice
from this menu. To get back to the main menu from the System Info
displays, press the right arrow button.
Figure 3-5 Mix Engine Front Controls, Main Menu Display
When the Main Menu is shown, rotating the knob moves highlighting up
or down thru the menu items. To select the highlighted menu item, press
the right arrow button. On an item with … after the name, this displays
that item’s sub‑menu. Again, rotate the knob to highlight each submenu
item then press the knob to “take”the highlighted item.
To edit a parameter or a name, press the right arrow button to highlight
the parameter. Turn the knob to highlight the desired value or character,
then press the right arrow button to select it. When a parameter has more
than one field, pressing the knob steps through the fields.
GSX SOFTWARE APPS
Navigator and the GSX GUI communicate with the WNIP system devices
using multicast messaging. If you find that one or both apps don’t see any
WNIP devices—especially if they were installed prior to networking that PC
with the WNIP system, then turn off the Windows Firewall on the NIC
connected to the WNIP system or add Navigator and the GSX GUI to the
programs allowed thru the Firewall and/or any anti-virus app.
Navigator is a licensed application. A Navigator site license must be
purchased to unlock all Navigator features, but basic functions, like
making crosspoints, editing signal names, and setting up logic can all be
done using Navigator unlicensed, although you’ll see plenty of “nagging”
pop-ups like this:
Note: A 30-day demo Navigator license is included with GSX. Click
on Obtain a License Key to get a “Seed ID” text string, which
identifies that PC, and email it to: [email protected]
along with your GSX Surface or Mix Engine serial number to
receive your demo license.
The next section covers how to use the Navigator app. A section on
using the GSX GUI begins on page 30. It is assumed, in each case, these
apps are installed onto an admin PC that is networked with your WNIP
system, including your new GSX console components, as outlined at the
beginning of this chapter.
Using the Navigator App
Navigator will initially be used to edit the factory-assigned default signal
names and configure the input and output signals on the I/O Blades
networked with your GSX Mix Engine, Surface, and Surface Host in a
WheatNet-IP (WNIP) system. These activities can all be done without
obtaining a Navigator license but, to access advanced features like
updating the Mix Engine and Blade software, you’ll need a Navigator site
license, available thru your Wheatstone dealer or Wheatstone sales.
Once your audio and logic signals are configured, Navigator is then
primarily used to connect sources and destinations using the Crosspoint
and Salvos/Macros tabs. Here’s a list of Navigator’s other main functions
or features:

16
•Setting the audio input and output mode between mono, stereo, and
5.1 surround.
•Editing names of system sources and destinations.
•Viewing and updating the Mix Engine and Blade software.
•Manually updating the system’s
device settings: name, the IP
address, etc.
•Assigning system-wide settings
like setting the sample rate and
the system’s date/time.
•Setting up weighting so specific
Blades will be set as the Route
Master or Clock Master in
multiple Blade systems.
•Assigning functions to the LIO
(RJ45 Logic jacks) and to the
SLIO (Software Logic I/O)
available on every Blade and
Mix Engine.
•Creating Associated Connections
to make one or more signal
connections in response to a
triggered connection.
•Viewing device status for every
device in the system.
•Viewing the system activity log.
•Viewing signal metering, and
listening, to just about any
signal in the WNIP system.
To start Navigator,
double-click its desktop
icon or, from the Start
Menu, select WheatNet
IP Navigator from the
Wheatstone folder.
WheatNet-IP Navigator-3, more
commonly called Navigator, opens
showing the Crosspoint Tab, shown
in Figure 3-6, pointing out
Navigator’s main features and
context menu items. A Login popup
box appears when starting Navigator.
Click OK to close the popup since no password is set by default. We do
recommend setting a password (click Set Password… in the popup
window)—if Navigator is run on a studio PC since unexpected audio
connection changes and other undesired operation could occur if the app is
used by untrained personnel.
Figure 3-6 Navigator App Crosspoint Tab and Docked Panes, with context menus overview

17
System Tabs
The System > Crosspoint tab gets the most use in Navigator, which
explains why it appears when the app starts up. Clicking on another tab,
on a Page Tab, or on a Blade, a Surface, or other device icon in the
System Dock, switches the window from showing the Crosspoint grid to
show another tab or window. To redisplay the Crosspoint Grid, click the
System icon at the top of the System Dock, or click the System page tab,
then click the Crosspoint tab. A floating Crosspoint Grid window can also
be opened by clicking the X Point window selector.
The Crosspoint grid shows the WNIP system’s sources on the horizontal
axis and the system destinations on the vertical axis. The signal names are
colored to match the device colors shown in the System Dock. The
assigned colors are edited using the Blade Preferences section of the
System > Preferences tab.
Icons in the XY grid indicate connected signals. Audio connections are
shown by round icons with the color indicating signal level: dark blue
indicates no or very low signal; green indicates a normal level signal; and
red indicates a high-level signal. These default colors can be changed
using the Preferences tab.
A small green square on a crosspoint indicates a logic-only connection. A
single round icon on a crosspoint indicates a mono source and mono
destination connection. Two round icons at a 45° angle indicate a stereo
source and stereo destination connection. Two round icons stacked
vertically indicate a mono source connected to a stereo destination and
two horizontal round icons indicate a stereo source connected to a mono
destination. A large blue multicolor round icon indicates a 5.1 connection,
rarely used in radio but often used in TV. The 5.1 icon shows various
colors to indicate the individual 5.1 channel levels.
If clicking on a crosspoint yields a large gold circle, that means the
destination could not subscribe to the selected source. This typically
means there’s a system fault, but this can also occur if the system’s
Ethernet switch or the access ports are not properly configured, or if the
switch itself has a fault.
Connecting Signals
As the mouse pointer moves over the grid, purple XY crosshairs point to
a source and destination to help identify which signals will be connected
when you click on that grid crosspoint. This is shown in Figure 3-6 on the
last page. Clicking on a crosspoint adds an icon to the grid to indicate that
connection is now active. To disconnect a signal, click on an active
crosspoint to silence the destination on an audio connection, or to turn off
the logic on a logic crosspoint.
Note: You can require that the CTRL key be pressed to click on a
crosspoint connection as a safeguard against making accidental
connections or disconnections. This option is set in the General
section of the System > Preferences tab.
A destination with a horizontal red line across the grid indicates that
destination is locked from changes, which typically indicates it's actively
being used. Locked signals may be manually assigned, often done with the
PGM, AUX, or AUD busses once they’re connected to outputs, but more
often a red line indicates a Surface channel that’s currently On.
Regardless, any locked signal can be unlocked by right-clicking on the
destination name and selecting Unlock Signal from the destination context
menu (shown in Figure 3-6 on the last page).
Note: Use caution when unlocking GSX channel destinations
GSXIn01 –GSXIn24, since those red lines indicate a channel that’s
currently On. This is also the case with dedicated outputs feeding
air or going to an internet streamer since changing their sources
could affect your air or stream feeds.
Remote Monitoring of Audio Signals
Right-clicking on an active crosspoint
connection, on a source name, or on some
destination names, brings up a context menu
(shown in Figure 3-6 on the previous page).
Selecting Monitor…, Monitor Source…, or
Monitor Destination… opens a Monitor window
(Figure 3-7) showing the source levels and, if
that signal is connected to a Destination, the
Destination levels.
The bottom section of this window has
controls to listen to that audio stream. A
drop-down list selects the PC destination to
use to listen to the signal (typically the PC’s
built-in speakers). Click Listen to Source… to
hear the audio in your PC speakers or
headphones. Use the Volume slider to adjust
the listening level.
Note: This monitoring feature is even more valuable when you
remote into the system from home or the road since the audio
plays back on the remote PC allowing one to confirm the correct
audio is present. For remote access into your admin PC, one
popular app to use is TeamViewer.
Salvos/Macros Tab
Clicking the System > Salvos/Macros tab shows a display that looks
like an unpopulated Crosspoint grid. The difference is that this grid is not
“live.” In the Salvo grid (Figure 3-8 on the next page) the signal
connections needed for a future show or a new daypart, or to setup the
Figure 3-7 Signal
Monitor Pop-Up Window

18
system for a special event, can all be saved as a Salvo. When that Salvo is
then “fired” the system makes the various crosspoints saved in that Salvo.
Figure 3-8 Salvo/Macro Tab
Dozens of audio and logic crosspoints can be set and saved in dozens of
Salvos. Each Salvo begins life as a number (Salvo 1, Salvo 2, and so on),
which doesn’t mean much, so you’ll want to immediately rename any
Salvos you create. In Figure 3-8, Salvo 1 was renamed as RAZOR IO by
selecting that Salvo in the drop-down list then clicking Rename. Be sure to
use a name that easily identifies what that Salvo does. And even though
you can enter a Salvo name using an almost unlimited number of
characters, only about 25 characters are shown in the Salvo drop-down
list. However, when assigning a Salvo to a programmable button in the
LIO tab, only the first eight characters are shown, so we recommend
limiting your Salvo names to eight characters, like: RAZOR IO, DanceRMT,
SuperPre, or GrdnShow, or just make sure the first eight characters of a
longer name can easily identify that Salvo.
Click New to create a new Salvo with the name Salvo X (empty), with X
being the next unused Salvo number. Any existing connections from a
previous Salvo are removed so you have a clean slate. As soon as you
make the first connection “(empty)” is removed from the name indicating
that Salvo is now in-use. There’s no Save Salvo button since the active
Salvo is updated with every edit.
When you select a Salvo in the drop-down list, its connections are shown
in the Salvo Edit Screen in read-only mode. The Details Dock also lists
that Salvo’s connections by their destination and source signal numbers
and names. If you want to make changes, click the Editable button, then
you can add or remove crosspoints, as required.
To take a Salvo, select it from the drop-down list then click Fire. The
crosspoints assigned in the Salvo are all quickly connected—except for any
connection going to a locked destination, like channels that are On. To
make those connections, turn off the channel(s) or unlock the locked
destinations, then fire the Salvo again. You can also assign one of the
Spare buttons in the monitor section of the GSX Surface, or a button on a
programmable button panel, to fire a Salvo.
Info Tab
This tab has three sections, highlighted in Figure 3-9, which may need to
be checked and/or set. In the Set Date and Time section check Use this
PC’s time then click Apply to update the time on the HDMI monitor to that
PC’s date and time. If the PC running Navigator is connected to the
Internet using a separate NIC, click the NTP radio button then select a
remote time server to keep the system time synchronized.
Figure 3-9 Info Tab
Note: If the Mix Engine Blade is power cycled, or the Surface is
rebooted, the date and time may need to be manually updated.

19
In the Clock Master Info section, check that the Clock Master
Frequency is properly set. The default setting is 44.1, but this can be
changed to 48 kHz (needed by some audio playback systems and most TV
stations) by clicking the 48 kHz radio button.
The Blade Display Settings section is used to control the brightness of
the front panel OLED displays on the Mix Engine and I/O Blades. These
settings adjust the Brightness and Dim Brightness, and how long before
the Screen Saver turns on and/or the Screen Dim is activated.
Refer to the Blade-3 User Manual about using the other settings in this
tab since they are not usually accessed by GSX users.
LIO Properties Tab
This tab (Figure 3-10) is used to set the unconnected state condition of
the user-defined logic functions (User 1–User 500). Each user-defined logic
function can be set so its unconnected state is High, Low, or left at its Last
State when disconnected. The default setting is Low. This tab also shows
the unconnected state settings for the built-in or assigned logic functions
which are all are set for Low and cannot be edited.
Figure 3-10 LIO Properties Tab
Associated Connections Tab
This tab is used to create, view, and edit Associated Connections. An
Associated Connection is used to automate common system connections
by monitoring for a Triggered Connection. When the Triggered
Connection occurs, one or more Associated Connections are then made.
A typical use for an Associated Connection (AC) is to automate
connecting a bus-minus signal to a caller or remote by creating an AC for
each channel that the caller or remote are set as visible. The Trigger
Connection occurs when the board op takes the caller or remote on a
“trigger channel.” The Associated Connection then connects that channel’s
bus-minus signal to that caller or remote.
This type of AC is shown in Figure 3-11, but one can automate many
other system operations in response to a predefined trigger connection
which can also be a disconnect—removing a crosspoint or taking NoSource
or another source on a fader channel.
Figure 3-11 Associated Connections Tab
Setting up an AC is a four-step process as listed in Figure 3-11. In the
left side Triggered Connections section, click the Add… button (1) to
open the Add Triggered Connection dialog box (2) where a source and
destination are selected. In the example, the triggered connection is the
PHONE being taken on channel 8 (In08). Clicking OK adds that entry to
the Triggered Connections list and closes the dialog box.
With that Triggered Connection highlighted, click the Add… button in the
right side Associated Connections section (3) to open the Add
Associated Connection dialog box (4) to select the source and destination
you want connected when the trigger connection is detected. In most
cases you’ll want to checkmark the Lock Override option. When it’s
checked, and the trigger connection is detected, the selected source is
connected to the destination regardless of whether that destination is

20
locked. When Lock Override is not checked, the Associated Connection will
not be made if the destination is locked.
As shown in Figure 3-11, multiple Associated Connections can be
assigned to the same trigger. In the example, when the PHONE is taken on
channel 8, the channel 8 bus-minus signal is connected to the PHONE plus
the caller and host mic audio are connected to a VoxPro editor (the host
mic, BL01MIC1, connects to the left channel and the incoming PHONE
audio connects to the right channel of the VoxPro destination).
Once you complete setting up the Associated Connections, click the all-
important Apply button, below the middle of the tab, to tell the system to
start monitoring for the Triggered Connections.
In the example, this process is repeated for each channel the PHONE is
visible on, so the correct signals are always returned to the caller and
VoxPro, regardless of which channel the PHONE is taken on.
Additional details on Associated Connection applications can be found on
page 29.
AES67 Visibility
This tab (Figure 3-12) is not active unless Navigator has an AES67
License (which is gratis). To use this tab the WNIP system must have at
least one Blade-3 blade designated as an “AES67 Translator” along with
one or more AES67-compatible devices networked with the WNIP system.
Figure 3-12 AES67 Visibility Tab
Sources and Destinations are selected using the same procedure as
selecting signals in the GSX GUI Visibilities tab (see page 46 for signal
selection details). When sources are selected, and Apply is clicked, the
selected sources are connected to the AES67 Translation Blade in
preparation for being streamed to an AES67 device. Since each AES67
Translator Blade can handle eight AES67 receive and eight AES667
transmit streams, selecting more than eight signals per Translator Blade
could cause audio streaming traffic issues and, even when the network is
properly configured, could lead to running out of bandwidth across some
sections of your system. The bottom line: select only those signals that
will be streamed to AES67 devices. Likewise, for selecting Destinations,
check only those that will receive audio from the AES67 Translation
Blade(s).
For more information on networking AES67 devices with your WNIP
system, refer to the Blade-3 User Manual, WheatNet-IP & AES667
Appendix, or the Commissioning AES67 White Paper, both available for
downloading from the main Wheatstone web page using the Support &
Downloads menu item.
Meters Tab
This tab (Figure 3-13) displays up to 64 meters to show the levels on
any combination of system sources and destinations, although there are a
few signals which can’t be metered like AES67 signals and Mix
Engine/Surface destinations (the console fader channels and the external
monitor inputs).
The Meters tab can also be set as a Floating Window by clicking the Float
button in the upper right corner. To re-dock the tab, click the Unfloat
button.
Figure 3-13 Meters Tab
Meters are shown in eight rows of eight meters, with mono and stereo
signals each taking up one meter space (shown in the top row of Figure 3-
13), and 5.1 signals taking up three meter spaces, as shown in the second
row in Figure 3-13.