page 3 – 2
W H E A T N E T - I P N E T W O R K S
WheatNet-IP BLADE 3
/ Jan 2016
WheatNet-IP BLADE 3
/ July 2018
WheatNet-IP Networks
WheatNet-IP Networks and What They Do
What exactly is an “WheatNet-IP network?” Simply put, it is a collection of Wheat-
Net-IP devices and driver equipped PCs connected together via an Ethernet LAN. In a
WheatNet-IP network, each device is represented as a “BLADE 3” with a unique BLADE 3
ID. Each WheatNet-IP rackmount unit is a BLADE 3, each control surface rackmount
engine is a BLADE 3, and even each driver equipped PC is a BLADE 3. The Navigator
GUI gives a Windows Explorer style device tree system view showing all of the devices
currently connected in the system.
You’ll notice in the example at the right that there are twelve
WheatNet-IP rackmount units connected in this system, with
IDs 1 - 12. You’ll notice 6 and 11 control surface engines, with
the control surface at IPs 192.168.87.206 and 192.168.87.211
associated with them. Finally, you’ll notice PCs with IDs 95
and 97 connected as well; these are typically your Automa-
tion PCs, but in the WheatNet-IP system each is represented
as a PC style BLADE 3.
This system tree view given by the Navigator GUI is a
very handy tool for monitoring your system. It sure beats
scrolling through a long list of names from the front panel of a
BLADE 3. It will always show your system connection status.
This is a very important point and indicates a big feature of
the WheatNet-IP system. Every WheatNet-IP network system
is dynamic. Devices can be added to it or removed from it at
will, in real time, just like computers in your LAN. Creating
and managing a LAN is beyond the scope of this manual, but a
few things must be taken into account. First, the WheatNet-IP
system uses fixed IP addresses for each BLADE3, therefore
your LAN must have the required IP addresses available.
Second, the WheatNet‑IP system comes configured with a
default IP address scheme to make it easy to configure; the
default addresses are 192.168.87.100 through 192.168.87.199,
corresponding to BLADE ID=1 to BLADE ID=99. Third, to
make sure that audio can be streamed throughout the network
without disruption, the bandwidth and traffic patterns on the
network must be carefully controlled. For these reasons,
Wheatstone strongly recommends that the WheatNet-IP sys-
tem and its various components be isolated (either physically
or virtually) on its own LAN using the default IP addressing
scheme. If this is done, a good sized WheatNet-IP system can be brought up and stream-
ing audio in less than an hour.
As you add a WheatNet-IP device to the network (by plugging it in and assigning it a
BLADE 3 ID) it’s associated signals are also automatically added and made available to
the system. They will show up in the front panel displays of other BLADE 3s, and insert
themselves into the crosspoint grid of the Navigator GUI. No complicated configuration
or IP management is required; the BLADE 3s take care of it all for you.
Содержание WheatNet-IP BLADE3
Страница 2: ...Technical Manual Wheatstone Corporation Jan 2016 Audio Over IP Network WheatNet IP BLADE3 ...
Страница 16: ...Quick Start 12 WheatNet IP BLADE 3 Jan 2016 Figure 4 ...
Страница 274: ...page A 48 WheatNet IP BLADE 3 Jan 2016 A P P E N D I C E S Contents Appendix 4 External Controllers A 49 ...
Страница 290: ...page A 61 WheatNet IP BLADE 3 Jan 2016 A P P E N D I C E S Click Next Click Install ...
Страница 336: ...page A 107 WheatNet IP BLADE 3 Jan 2016 A P P E N D I C E S Contents Appendix 9 Introduction to Screen Builder A 108 ...
Страница 338: ...page A 109 WheatNet IP BLADE 3 Jan 2016 A P P E N D I C E S ...
Страница 365: ...WheatNet IP BLADE 3 June 2018 page A 136 A P P E N D I C E S Some Screen Shots of Various Vendors Configuration Screens ...
Страница 366: ...WheatNet IP BLADE 3 June 2018 page A 137 A P P E N D I C E S ...