How To Set Up A Tieline Gateway with WheatNet-IP

The Gateway platform will act as a WheatNet-IP blade in the WNIP system.

You will change these settings from the WebGUI of the Gateway...

Audio > Audio Options > Edit > Audio over IP mode > WheatNet-IP > Save
Audio > Audio Options > Edit > Digital Input Type > Audio over IP > Save
Audio > Audio Options > Edit > Digital Output Type > Audio over IP > Save
Audio > Inputs > Select the Input "Wrench" icon > Change the "Type" to Audio over IP
Audio > Outputs > Select the Output "Wrench" icon > Change the "Type" to Audio over IP
Settings > Options > System > Edit > Enable WheatNet LIO > Enable > Save

Note, you can have a mix set of Analog and Digital Inputs/Outputs (i.e., some on the StudioHub+ connectivity, and others coming from Wheatnet IP).

Once you have the above done on the unit, simply plug in the Gateway into your Wheatnet Network, and Navigator will discover the unit as a detached blade.

Right-click on the Tieline in the System tree and choose Initialize Blade.

Here you will set the IP address and Blade ID. (don't forget to set the netmask and gateway, the same you do on Wheatnet-IP blades!)

Click Configure Blade, and the WheatNet card in the Tieline Gateway will restart and join the system.

Like all micro-Blades, the Tieline doesn’t do its own multicast communications. It chooses a blade to be its host automatically and routes the communications through that host blade. You will see the host IP in Locator. Again, it doesn’t matter which blade it uses, it just picks one. The WNIP card in the Tieline then gets from its host a list of all of the sources and destinations. In a very large system, it can time out before it finishes getting this list so it starts over. It can take a long time for the Tieline to join the system because it has to finish building the list before it joins. Be patient.

After it has joined, you can look in the Crosspoint grid to see that the sources and destinations have appeared. You can click on the Tieline in the System tree and go to the Source and Destination tabs and rename them from their defaults to how you want them to appear in your system.

The following information is from the Tieline manual:

Ensure audio is routed in the codec Matrix Editor from inputs to outputs if the codec is feeding audio into the WheatNet-IP network from codec input sources. I.e. route audio from inputs to outputs to create a WheatNet source in this way:

In addition, if input audio is routed to outputs to create a WheatNet source, ensure the Outputs panel sliders used to output Send/Return audio from the output are mixing Send 100% audio to the outputs. Otherwise audio will not be outputted to the Blade Source. By default, the outputs are configured as Return 100% without Send audio mixed in. If Return audio is not required this can be removed from the mix.

When the codec is configured for WheatNet-IP the Tieline AoIP Web-GUI in the codec is inactive because the device is controlled by Wheatstone's Navigator software.

By default, when a Gateway or Gateway 4 codec is added to Navigator as a Blade it is configured with 16 available channels, or Signals in Navigator. If you have purchased a Gateway with fewer than 16 channels, e.g. Gateway 8, or have purchased a Gateway 4 codec supporting 4 channels, it may be necessary to delete the unavailable Source Signals and Destination Signals in Navigator. This will avoid any confusion with unavailable Signals, whereby Sources and Destinations within Navigator appear as available, even though they are not.

For example, if the codec Blade in the following image was a Gateway 8 with 8 available channels/Signals, simply select the Sources tab in Navigator for the device and delete the 4 unavailable stereo Source Signals. Then do the same in the Destinations tab for 4 unavailable stereo Destination Signals.

The same principle would apply for mono Source Signals and Destination Signals in Navigator, i.e. delete 8 the unavailable mono Source Signals and Destination Signals. If a Gateway is upgraded to increase channel density, e.g. from 8 channels to 16, it is relatively simple in Navigator to add Source Signals and Destination Signals as required. (click the Add button in Navigator, just like you do for any source or destination on a Blade!)

• Related Articles

• How To Set Up WheatNet-IP On Eventide 600W+

  The Eventide delay ships set to a default of 192.168.87.239. If you are deploying more than one, or if you need it on a different address, change the IP using Telnet: Open PuTTY and connect to the device. username: wheatstone there is no password, ...

• About Wheatnet-IP Navigator

  Navigator is the "control center" for your Wheatnet IP System. You'll use Navigator frequently to add or change signal parameters (including signal names), set up logic signals, salvos and associated connections, and make routing (crosspoint) changes ...

• WheatNet-IP Event Scheduler

  What is WNIP Event Scheduler? This program works in conjunction with Blade logic and automation to allow for automated and timed control of Wheatnet-IP functionality, up to and including remote machine control, on air lights, tallies, transmitter ...

• WheatNet-IP Micro Blades Cannot Become Clock Master

  The WheatNet-IP Micro Blade, which is the WheatNet-IP card built into the Tieline Gateway, Eventide BD600W+, and Wheatstone Stagebox, is designed to only follow the WheatNet-IP metronome generated by the Clock Master Blade. It is not capable of ...

• How To Configure Netgear M4250 AV Series for WheatNet-IP

  Netgear’s M4250 AV Series is a line of Ethernet switches designed for Audio/Video over IP and targeted at the broadcast and sound contracting markets. While many features used for multicast IP audio are enabled on this switch by default, careful ...