This is a public Group  public


  • Sam Drazin
    Wireless Workbench 6 - Quick Start Guide33.0
    Topic last edited October 25, 2016 by Sam DrazinExpert, tagged how-to 
    Wireless Workbench 6 - Quick Start Guide

    New to Wireless Workbench 6?  Need some assistance networking your Shure devices?


    Check out the Wireless Workbench 6 Quick Start Guide! (updated for version 6.12)


    This document will walk through the essential steps to get you up and running with WWB6 and your Shure wireless system, including:

    • Downloading the software
    • Configuring your network and computer to connect to devices
    • Performing RF Scan
    • Performing basic Frequency Coordination
    • Deploying frequencies to channels


    Want to see additional topics covered in this guide?  Let us know in the comments below.

  • Sam Drazin
    Firmware Update UHF-R24
    Topic last edited February 13, 2014 by Sam DrazinExpert, tagged how-to 
    Firmware Update UHF-R


    In order for Wireless Workbench 6 to work with UHF-R wireless receivers, the firmware of those devices must be updated to firmware version 1.166 or later. The following article will explain how to firmware upgrade UHF-R receivers.

    Related Links

    Check UR4 Current Firmware Version

    To check which version of firmware your UHF-R receiver is currently running, power-cycle the rack device, and pay attention to the front panel display as it boots up. The installed version of firmware will be displayed in the lower right-hand corner of each display. If the version is 1.166 or later, your receiver is compatible to operate with Wireless Workbench 6.

    Updating Firmware

    If your receivers are on a version of firmware earlier than 1.166, they will need to be updated in order to be discovered and controlled by Wireless Workbench 6.

    In order to upgrade the firmware for UHF-R receivers, you can now use the Shure Update Utility (v2.0.2 or later). Follow the steps listed out below to complete the firmware upgrade.


    1. If you do not have the Shure Update Utility, you can download it here.

    2. Power on your UHF-R receivers. Connect your network of receivers to your computer, and launch the Shure Update Utility.

    Note: UHF-R receivers will not appear as online devices within Wireless Workbench while the Shure Update Utility is running.  Once the Shure Update Utility is closed, the UHF-R devices will reappear as online devices in Wireless Workbench 6.

    3. Select "Check for Updates".

    4. Download any available updates.

    5. Once the downloads have completed, select the "Update Devices" tab and ensure that your UHF-R receivers are discovered.

    6. For each UHF-R receiver to be updated, select the checkbox on the far right of it's row, and then select the desired version to install in the "Version to Install" column.

    7. To begin the firmware update, select "Send Updates".

    Do not power off or disconnect your device from the network while the firmware update is in process.

    8. Once the update has been sent, your device will reboot.  The Shure Update Utility will wait for the receivers to be rediscovered and verify that the sent firmware was properly installed.



    The UHF-R transmitters were designed to be forwards compatible with newer versions of UHF-R receiver firmware. It will likely not be necessary to upgrade the firmware of your UHF-R transmitters. NOTE: this implies that differing firmware versions between UHF-R transmitters and receivers is an acceptable mis-match of firmware versioning.

    If you have any questions, please contact Shure Service and Repairs.

  • ksepede
    Channel Strip Size1
    Topic posted January 28, 2016 by ksepedeNovice, tagged how-to 
    Channel Strip Size
    Personal Computer:
    MacBook Pro 15inch. OSX 10.10.5

    Hi there,

    Is there a way of having a mixture of 'Full' and 'Condensed' channel strip sizes?

  • oberta
    wwb 6_11_2_13 with Linux OS12.0
    Topic posted August 31, 2015 by obertaNovice, tagged how-to 
    wwb 6_11_2_13 with Linux OS
    Personal Computer:
    openSUSE 13.1 + 13.2 64-bit

    Hi ,

    we are using wwb only to calculate our Frequency Setups works fine with openSUSE 13.1 + 13.2 using wine

    KDE  4.14.9 + 10

    System works in German
    native Language !!
  • mihau89
    ShurePlus Channels1
    Topic last edited July 7, 2015 by mihau89Beginner, tagged how-to 
    ShurePlus Channels
    Personal Computer:
    MacBook Pro Retina 13" early 2015, OS X 10.10.4,
    Shure Hardware:


    Sometimes I don't have any router or access point and I would like to use my ShurePlus Channels app. I've tried connecting ethernet cable into macbook pro and then using internet sharing (thunderbolt ethernet > wifi)  to create a private network. Although ShurePlus Channels shows Macbook pro network name and it seems to be connected, I can't see any devices.

    Is it possible to connect your shure devices to macbook pro and then, via port sharing (in Preferences > Sharing), send all data to iOS device to use ShurePlus App?

  • Sam Drazin
    Proper Network Setup12
    Topic last edited November 20, 2013 by AdminProficient, tagged how-to 
    Proper Network Setup


    Below are some high-level topics which will guide you through successful practices of setting up your network.

    Related Links

    Network Topology

    There are several ways to configure a network of devices. In general, you should always use a "star" network topology where each device uses one connection to an Ethernet switch port. If multiple switches are used, each switch is individually connected to one connection to the next level of Ethernet switch.

    Automatic vs. Manual IP Mode

    Each Shure wireless device on your network has two IP modes:

    • Automatic (or DHCP for UHF-R)
    • Manual

    When in automatic mode, a device expects for a DHCP server to automatically assign it a valid and free IP address. With a DHCP server available (like the AXT620 Network Switch with onboard DHCP server), this makes your life easy. This is also the mode we recommend.

    When in manual mode, a each device must have it's IP address manually set to correspond with all other devices on the network. Some basic rules that need to be followed include:

    • Each device on the network (including computers) must have a unique IP address.
    • All devices on the network (including computers) should share the exact same Subnet mask (this is not always the case, but is a good idea to align)
    • Considering the four octets of a subnet mask:
    • Where the value is 255, that corresponding value of the IP addresses for all devices must be identical
    • Where the value is 0, that corresponding value of the IP addresses for all devices must be unique


    Assume all devices on our network have a subnet mask of Because the first two octets of the Subnet mask have the value of 255, the first two octets of all IP addresses for devices on our network must match. Below is a valid set of a few IP addresses for this fictitious network:


    Notice the first two octets of the IP addresses always match, and the last two octets never match.

    Firewall Setup

    In order for Wireless Workbench to discover devices on the network, various portions of the application require network access which may be initially hindered by OS-native or 3rd party security software.

    Configure any firewall or anti-virus software to allow the following processes network access:

    For Macs

    • Wireless Workbench
    • slpd
    • snetDameon
    • acnproxy

    For Windows

    • WWB6.exe
    • SLPD.exe
    • snetDameon.EXE
    • ShureFirmwareUpgrader.exe
    • snetConfigureexe.exe

    Consult the Wireless Workbench 6 Help System for more information on configuring OS-native Firewall Settings appropriately.

    DHCP Management

    If your network is configured to receive IP addresses automatically (from a DHCP server), there are some basic rules you must follow to ensure proper IP address assignment.

    • All Shure wireless devices must have their IP modes set to Automatic (or DHCP in the case of UHF-R)
    • There must only be one active DHCP server on your network.
    • If you are using multiple switches or routers that have the ability to be DHCP servers, all others (clients) besides the master server must have their DHCP disabled.

    You can verify that your computer is set up to receive automatically assigned IP addresses by checking the DHCP client table on the AXT620 Ethernet switch.

    Check the DHCP server configuration

    Log into the AXT620 Ethernet switch by opening the Internet Explorer web browser to the DHCP server address (default = The default username and password to log in are both "root".


    Select the "System' from the main menu, then "DHCP server' option, and finally the "System Configuration' from the middle menu.


    The DHCP server switch should be ON and the IP address fields should be set to the above values (as default). If you do not see this configuration and want to restore the factory default, you can select the "Factory Default' option from the main menu.

    NOTE: If you factory reset the DHCP server, you should also power cycle the all other devices on the network after the DHCP server reboots.

    Check the DHCP client table.


    Select "DHCP server' from the main menu and then "Client Entries' from the middle menu.

    The DHCP client table should include the computer IP address as well as the IP addresses of all the devices on the net- work. If you do not see the IP address of your computer in the client table, check the DHCP server switch on the front panel to ensure it is set to ON.

    NOTE: You may need to power cycle the DHCP server and computer is the switch was set to OFF and you subsequently turned it to ON.

    Configuring Wi-Fi for Wireless Networking

    When using Wireless Workbench over Wi-Fi, it's important to setup the wireless router properly for best performance. Wireless Workbench employs "multicast" data protocols to communicate to the Axient and PSM1000 devices. Wi-Fi treats broadcast and multicast packets differently than general packets for backward compatibility reasons. In some cases, the Wi-Fi router will limit the multicast packet transmission rate to a value that is too slow for Wireless Workbench to properly operate.

    By default, most Wi-Fi routers are configured to operate in "b/g-mode', which tells the router to allow both 802.11g and older 802.11b devices to operate over the network. In this configuration, some routers will automatically limit the multicast data rates (or sometimes referred to as "basic rate', or "management rate') to 1-2Mbps. For small wireless microphone configurations of less than 20-30 channels, this Wi-Fi setting should not cause any problems with Wireless Workbench. However, for larger wireless microphone configurations of greater than 30 channels, it's recommended to configure the Wi-Fi router to operate in "g-mode' only. Most routers will increase the multicast transmission rate to 6Mbps when operating in "g-mode' thereby providing adequate bandwidth to Wireless Workbench.

    Caution: We have tested Netgear-brand Wi-Fi routers and found that they typically limit the multicast rate to 1-2Mbps even when operating in "g-mode' only, so it's not recommended to use Netgear Wi-Fi routers with Wireless Workbench.

  • Michael Calder
    Inventory Report Sort6
    Topic posted February 13, 2014 by Michael CalderNovice, tagged how-to 
    Inventory Report Sort
    Shure Hardware:

    How do I sort the Inventory Report? I've looked everywhere in the program and can't find an answer in the forums.

  • Sam Drazin
    What is wrong with my network configuration?265.0
    Topic last edited December 10, 2013 by AdminProficient, tagged how-to 
    What is wrong with my network configuration?


    This page will outline a set of tests and diagnostic measures you can run to ensure that your network is properly configured.

    The end-goal is to have a properly configured network such that Wireless Workbench discovers all Shure wireless devices online, and that your computer can effectively and reliably communicate with said devices. This page will act as a troubleshooting guide for debugging your network setup.

    Related Links

    Step 1: Selecting a Network Interface

    Wireless Workbench gives you the flexibility to choose which of your computer's network interfaces you would like to connect to. To inspect or modify which network interface Workbench is currently connected to, go to the Preferences menu and select the Network tab.

    To access the Preferences menu, select Tools -> Preferences.


    From this display, all available network interfaces known to your computer are displayed. To view more details about a particular network interface, select the "Details" button next to one of the network interface options.


    Once you have selected the network interface you'd like to use to connect to your devices, select "Save" to commit the change.

    Note: If you have configured your computer for both wired and wireless networking, the two IP addresses must be on separate subnets for WWB to work properly. The wired and wireless adapters on the computer should not be "bridged".

    Network Status Indicator

    Wireless Workbench offers a simple "Network Status" label that, at a cursory glance, allows you to assess the basic state of your connection to a network.

    The Network Status indicator is in the bottom right corner of the application, and is visible in all three tabs.


    The Network Status indicator can read one of the following states:

    • Network Off: there is no network seen by your computer. If you see this, the network interface you've selected is either invalid, or disabled.


    • Network On: there is a network seen by your computer, and the label will indicate the number of Shure wireless devices seen online.


    When you first configure your network of wireless gear, this indicator can serve as a first-check of whether or not your computer sees a valid network or not.

    Step 2: Check your Computer/Hardware

    Pinging devices

    When configuring a network, you may find yourself in the scenario where you are not sure you have a valid connection to a particular networked device. Pinging a device is a precise way to discover whether or not a device is available on the network, regardless of other signs that it may or may not be exhibiting.

    First, isolate the device that you want to ping- you will need to get it's current IP address. On the device's front panel, access the Network menu. For Axient, PSM1000 and UHF-R rack devices, this menu can be accessed by selecting Util -> Network.


    The device's IP adress will be listed next to the label "IP:".


    If you are working with a UHF-R receiver, be sure to check the IP address on the left front panel, not the right. This is because the IP address for
    devices in DHCP (Automatic) IP mode is only listed on the left panel.

    Note the device's IP address. For this example, let's use the IP address of the AXT400 receiver above:

    Next, open a command prompt on your computer. For Macs, this would be Terminal. For Windows machines, this would be Command Prompt.

    Type the following command:


    Press return. The results of this command will indicate to you whether your device is online or not.

    The ping command will send a small packet of information the IP address that you listed, and wait for a response. If none was heard, you will see messages similar to this:

    pcni4299al:~ drazins$ ping
    PING ( 56 data bytes
    Request timeout for icmp_seq 0
    Request timeout for icmp_seq 1
    Request timeout for icmp_seq 2
    Request timeout for icmp_seq 3
    ping: sendto: No route to host

    Notice that there was a "Request timeout". This indicates that your computer waited for a response for a certain amount of time, and none came.

    If your ping was successful, you will see a message similar to this:

    pcni4299al:~ drazins$ ping
    PING ( 56 data bytes
    64 bytes from icmp_seq=0 ttl=30 time=0.863 ms
    64 bytes from icmp_seq=1 ttl=30 time=1.086 ms
    64 bytes from icmp_seq=2 ttl=30 time=1.120 ms
    64 bytes from icmp_seq=3 ttl=30 time=1.050 ms
    64 bytes from icmp_seq=4 ttl=30 time=1.088 ms
    64 bytes from icmp_seq=5 ttl=30 time=1.183 ms

    Notice that each line after the PING command reads something like "64 bytes from". This is a sign that the device we pinged is on the network.

    If you're still not discovering devices in your inventory after a successful ping, check your firewall settings. Be sure to allow all processes listed in the "Firewall Setup" section of the Proper Network Setup through any and all security and firewall software your computer is running.

    If you ping a device and it does not appear to be connected on the network, some of your next steps should be:

    • ensure that there is a valid network connection from that device to your network (operational ethernet cables/ports, etc)
    • ensure that your computer is connected to the same network as the device you are trying to ping
    • ensure that the device itself is operational

    Common Mistakes

    Below is a listing of common mistakes made when setting up a network.

    • No two devices (including a computer on the network) can ever share identical IP addresses.
    • Ensure that all devices on your network share the same Subnet Mask. Consult the Automatic vs. Manual IP Mode section of this page for more details on proper IP/Subnet Mask configuration practices.
    • Do not connect a device to the same network twice, ie: via ethernet AND Wi-Fi. Connecting a device to the same network interface with two connections will not yield valid results.
    • Ensure that all devices on your network are set to the proper IP mode.
    • Check your ethernet cables and ethernet ports. Replace old cables and look for data transfer indicator lights on ethernet ports with LEDs to indicate such. If these lights are present but not illuminated, this may indicate a faulty or incomplete connection.
  • Diogo Nunes Pereira
    Importing RF Explorer scans tutorial15.0
    Topic posted October 30, 2014 by Diogo Nunes PereiraCompetent, tagged how-to 
    Importing RF Explorer scans tutorial
    Personal Computer:
    Dell M4800; Windows 7 SP1; 64-bit; Wired Ethernet
    Shure Hardware:
    2x AXT400 L3E, AXT600, 6x UR4D J5E, 6x UR4D+ J5E, 4x U4D Mk2, 1x U4D Mk1, 4x PSM700, 6x PSM900

    Hello everybody,

    after digging thru this forum and other places in order to get it to work, (and finally getting there) here's my own tutorial on how to import RF Explorer scans into Wireless Workbench 6. For those (many) of us who can't always grab the Spectrum Manager for the next gig. 

    There's an English and a Spanish version...

    Feels good to give something back.


  • Sam Drazin
    Merging Online and Offline Devices1
    Topic last edited December 6, 2013 by AdminProficient, tagged how-to 
    Merging Online and Offline Devices


    Wireless Workbench allows you to plan out a show's inventory and perform frequency coordination ahead of time. Without access to the hardware in advance, all device settings and frequency values will likely be initialized on offline devices representing your gear.

    When you arrive to the venue, Merging will allow you to take the settings and values from your offline devices and push them to the online devices once discovered in Wireless Workbench.

    Related Links

    Adding Offline Devices

    Initially, you'll want to set up an offline version of your show. This will involve adding all the hardware you expect to coordinate for or around to your Inventory. Select the "Add new device" button from the global menu to access the Add New Device dialog.


    From the Add New Device dialog, select the Manufacturer/Model/Band of the device you want to add. You can add multiple devices from this view by selecting a number greater than 1 in the "Active Devices" field.


    You can configure select device and channel parameters from this dialog, but this can also be done later from several other views. Once you're ready to add the device(s), select "Add".

    Configure your Offline Inventory

    Once your devices are added in the Inventory view, you can proceed in modifying device parameters and frequency values to your liking. This will often include running Frequency Coordination, calculating compatible frequencies for the devices accounted for.

    For more information on performing Frequency Coordination, refer to the Frequency Coordination tutorial video.


    Save your Show File

    A show file is a file that encapsulates all modifiable parameters and devices within your inventory, as well as scan files, show properties, and other elements of your Wireless Workbench environment. Saving your show file will allow you to prepare an entire show's setup ahead of time, and load the show file when you arrive at the venue.

    To save the show file, select File -> Save, or press Command+S for Mac, Control+S for Windows.


    Merging your Show File and Online Devices

    Once you arrive at the venue, launch Wireless Workbench and open your show file. To open a show file, select File -> Open, or press Command+O for Mac, Control+O for Windows.

    With your show file loaded, you should see your entire offline inventory set up as you last saved it. You are now ready to connect to your network of Shure wireless hardware.

    Ensure that you have a properly configured network of Shure wireless devices. Connect your computer to the network. If everything is properly configured, you should discover your devices and they will be displayed in the Inventory view alongside your offline pre-configured devices.


    We want to take the parameters from the offline devices and apply them to the online devices. This can be accomplished simply by dragging and dropping the offline device on-top of the online device.


    This tells Wireless Workbench that you want to merge the offline and online versions of the device into a single entry.

    NOTE: Merges are only allowed if the following criteria are met:

    • Both devices of the same model and band
    • One of the devices is offline, and the other device is online

    The yellow border around the destination device indicates that a merge is allowed to occur. If that yellow border does not show up, then you have not met the 2 requirements needed to perform a valid merge.

    In order to allow you to specify which parameters you want to keep (either offline from the show file, or online from the live devices), the Device Association dialog is displayed.


    To briefly summarize this dialog's functionality, the toggle buttons shown allow you to specify the source of the parameters that will be kept for the devices in merge. Choose to keep offline or live settings for both the Frequency parameters and Settings parameters for each device you want to merge.

    To keep the settings we set on the offline device and overwrite the hardware's current settings, we'll select "From OFF-LINE Device" for both Frequency and Settings buckets of parameters.


    Select "Apply" to apply the merge.

    For more detailed information on the specifics of how to use the Device Association dialog, consult the Device Association Dialog page.

    After the Merge

    Once the merge is complete, notice that the old offline version has gone away, and the online version of the device now has all the parameters that were set on the offline version. Awesome!


    Continue to drag-and-drop offline and online devices to merge until all offline versions of the devices have passed their parameters to their online counterparts.

© 2009-2014 Shure Incorporated All rights reserved.
  • Privacy
  • Powered by RightNow