Software & Firmware Archives

Important

• ULX-D 2.X firmware versions are incompatible with ULX-D or QLX-D 1.X firmware versions. To ensure all receivers and transmitters in a configuration function with each other, update all devices to the same firmware version.

Improvement

• Support new hardware revisions of ULX-D. New revisions can't be downgraded below version 2.3.4.

Known Issues

• New hardware revisions of ULX-D version 2.3.4 are not compatible with SystemOn 2.0-3.0.1.
• ULX-D devices on J50A or L50A frequency bands are not compatible with SystemOn 2.0-3.0.1.

Notes

• User Guide
• ULXD1/2 transmitters used with receivers must be updated via IR sync. After a receiver is updated, follow these steps:
  1. Go to the receiver menu: DEVICE UTILITIES > TX FW UPDATE
  2. Align the infrared ports with the transmitter
  3. Press ENTER
• To operate ULX-D version 2.3.4 devices with other Shure networked systems and software, see the following list of minimum versions:
  • ULX-D ULXD1/2/6/8 Transmitters and ULXD4/4D/4Q Receivers 2.3.4
  • SBC250/450/850 Networked Charging Stations 2.3.4
  • QLX-D QLXD1/2 Transmitters and QLXD4 Receivers 2.2.11
  • PSM1000 1.6.19
  • Axient AXT600 Spectrum Manager 2.1.22
  • Wireless Workbench 6.12.6
  • Shure Update Utility 2.4.3
  • ShurePlus Channels 1.4.2

Important

• ULX-D 2.X firmware versions are incompatible with ULX-D or QLX-D 1.X firmware versions. To ensure all receivers and transmitters in a configuration function with each other, update all devices to the same firmware version.

Improvement

• Changed version number to allow all ULX-D devices in a configuration to have the same firmware version.

Known Issues

• New hardware revisions of ULX-D version 2.3.4 are not compatible with SystemOn 2.0-3.0.1.
• ULX-D devices on J50A or L50A frequency bands are not compatible with SystemOn 2.0-3.0.1.

Notes

• User Guide
• If your ULXD1/2 transmitter is on version 2.2.23, updating to version 2.2.24 will unexpectedly reset your ULXD1 to its factory default settings and your previous settings will need to be recovered via IR sync.
• ULXD1/2 transmitters used with receivers must be updated via IR sync. After a receiver is updated, follow these steps:
  1. Go to the receiver menu: DEVICE UTILITIES > TX FW UPDATE
  2. Align the infrared ports with the transmitter
  3. Press ENTER
• To operate ULX-D version 2.3.4 devices with other Shure networked systems and software, see the following list of minimum versions:
  • ULX-D ULXD4/4D/4Q Receivers 2.3.4
  • QLX-D QLXD1/2 Transmitters and QLXD4 Receivers 2.2.11
  • Axient AXT600 Spectrum Manager 2.1.22
  • Wireless Workbench  6.12.6
  • Shure Update Utility 2.4.3
  • ShurePlus Channels 1.4.2

Important

• ULX-D receivers must be on version 2.2.24 or higher and QLXD4 receivers on version 2.2.11 or higher in order to be used with SBC250 charging stations.
• ULX-D receivers must be on version 2.1.6 or higher and QLXD4 receivers on version 2.1.5 or higher in order to be used with SBC450/850 charging stations.

Improvement

• Changed version number to allow all ULX-D devices in a configuration to have the same firmware version.

Known Issue

• SBC250/450/850 devices are not compatible with SystemOn 2.0-3.0.1

Notes

• SBC450/850 User Guide
• To set up ULXD6/8 transmitters to receive firmware updates while docked in SBC250/450/850 Networked Charging Stations, follow these steps:
  1. Place transmitters on a charging station and ensure the charging station is connected to the network.
  2. Launch Shure Update Utility to find firmware updates.
  3. Download updates and select Send Updates.
• To operate SBC250/450/850 version 2.3.4 with other Shure networked systems and software, see the following list of minimum versions:
  • ULX-D ULXD6/8 Transmitters and ULXD4/4D/4Q Receivers 2.3.4
  • QLX-D QLXD4 Receivers 2.2.11
  • Wireless Workbench 6.12.6
  • Shure Update Utility 2.4.3
  • ShurePlus Channels 1.4.2

Improvements

• Support for updates to ULX-D
• Bug fixes

Known Issues

• Exporting TV exclusions to Spectrum Managers when a TV Channel  Width other than 6 MHz can result in improper TV range exclusions.
• ULX-D receivers running firmware version 2.0.28 or earlier may  trigger a Settings Conflict when rediscovered after updating their  firmware to version 2.1 or later. There is no issue with the device –  there was simply a new property added in version 2.1. To dismiss the  alert, resolve the Settings Conflict by selecting the properties you  wish to keep.
• Audio Summing reported from ULX-D receivers reports an Audio  Overload on all channels instead of on the specific channel(s)  experiencing the overload.
• Timeline System Events displayed when using the Axient Digital  FD-Override (in FD-S, selecting to Lock to Rx 1/2/Auto Switch) do not  get displayed on both FD channels.
• Timeline System Events displayed for Active Transmitter Online for  ULXD6/8 transmitters do not always include Transmitter Device ID in the  event description.
• On Macs, when users open show files and launch the Frequency  Analysis dialog (by checking the checkbox and pressing “Analyze”), the  Frequency Coordination tab may stop responding to keyboard inputs (for  example, editing or deleting frequencies with the keyboard). To work  around this issue, select another tab in the application (e.g.:  Inventory or Monitor) and then reselect the Frequency Coordination tab.
• SLX and ULX frequencies in Master List mode cannot be manually  entered in the Coordination Workspace. They can, however, be coordinated  and analyzed.
• When scanning with AXT400 receivers, the Band Preset value in the  Live Scan Settings dialog does not always stay in sync with the  currently selected band of the receiver. The Band Preset can be manually  changed to scan any supported range.
• Alerts logged when devices first come online may list device  parameters and their values as they are being discovered even though the  parameter values themselves have not changed.
• Certain bodypack portables are not compatible with SBC220 (P3RA,  P9HW, and UR5), in that the charging status and other attributes cannot  be remotely monitored from WWB. These bodypack portables will still be  charged when using SBC220, but viewing the charge percentage or other  attributes of those batteries will not be available from WWB.

Notes

• To operate Wireless Workbench successfully, you must run it as an  administrator. (Consult your IT department if you have questions.)
• Tags that have been added to a show file but are not assigned to any devices are not saved within the show file.
• Opening show files created with older versions of Wireless  Workbench may result in the Settings Conflicts dialog opening once the  file has loaded. This is due to newly supported hardware parameters that  have been introduced with updated firmware versions. To maintain all  settings from the show file, select "Keep all settings from: Wireless  Workbench".
• On machines running Windows 7, Wireless Workbench will not be able  to discover devices when the machine has fallen back to its  169.254.xxx.yyy fallback IP address, regardless of the IP addressing of  the connected Shure devices.  To address this, perform one of the  following:
  • Insert a DHCP server onto your network and set your machine and Shure devices to accept automatic IP addressing.
  • Statically assign your machine's IP address to the 169.254.xxx.yyy  fallback subnet with a different IP address than the one it fell back  to originally.

These release notes cover the following models:

• MXWNCS2/4/8 Networked Chargers
• MXWANI4/8 Audio Network Interfaces
• MXWAPT2/4/8 Access Point Transceivers
• MXW1/2/6/8 Wireless Microphones

Bug Fixes

• When an interfering DECT device is transmitting nearby an MXW Access Point, the Access point may occasionally drop the connection to microphones 1-4. To recover mic connectivity, reset the Access Point.
  • Examples of interfering DECT devices are other MXW Access Points that are not on the same subnet as the affected Access point; however, in many cases, the interfering DECT devices are wireless headsets for wired desk telephones.
• MXW microphones intermittently drop off the Monitor status screen and their LED turns from green to flashing red for 10 to 30 seconds before recovering back to green, and then recovering their status activity on the Monitor screen. This may occur in environments with large reflective surfaces, such as windows, large LED monitors, and auditoriums with high walls and ceilings. These environments introduce RF reflections that interfere with the heartbeat signal from an MXW Access Point to a microphone. Microphones overcompensate for the interference and lose connectivity with the Access Point, restarting the scan process (seen as a red blinking LED) to find a valid Access Point signal.

Known Issue

• SystemOn 3.0.1 is compatible with MXW 6.0.3, but will incorrectly warn “Check system requirements, your current firmware version may not be confirmed compatible.”

Notes

• To operate MXW version 6.0.3 with other Shure networked systems, see the following list of minimum software and firmware versions:
  • SCM820 1.3.3
  • Shure Web Device Discovery 1.2
  • Shure Update Utility 2.4.3
  • SystemOn 3.0.1

These release notes cover the following models:

• MXWNCS2/4/8 Networked Chargers
• MXWANI4/8 Audio Network Interfaces
• MXWAPT2/4/8 Access Point Transceivers
• MXW1/2/6/8 Wireless Microphones

Bug Fixes

• When an interfering DECT device is transmitting nearby an MXW Access Point, the Access point may occasionally drop the connection to microphones 1-4. To recover mic connectivity, reset the Access Point.
  • Examples of interfering DECT devices are other MXW Access Points that are not on the same subnet as the affected Access point; however, in many cases, the interfering DECT devices are wireless headsets for wired desk telephones.
• MXW microphones intermittently drop off the Monitor status screen and their LED turns from green to flashing red for 10 to 30 seconds before recovering back to green, and then recovering their status activity on the Monitor screen. This may occur in environments with large reflective surfaces, such as windows, large LED monitors, and auditoriums with high walls and ceilings. These environments introduce RF reflections that interfere with the heartbeat signal from an MXW Access Point to a microphone. Microphones overcompensate for the interference and lose connectivity with the Access Point, restarting the scan process (seen as a red blinking LED) to find a valid Access Point signal.

Known Issue

• SystemOn 3.0.1 is compatible with MXW 6.0.3, but will incorrectly warn “Check system requirements, your current firmware version may not be confirmed compatible.”

Notes

• To operate MXW version 6.0.3 with other Shure networked systems, see the following list of minimum software and firmware versions:
  • SCM820 1.3.3
  • Shure Web Device Discovery 1.2
  • Shure Update Utility 2.4.3
  • SystemOn 3.0.1

These release notes cover the following models:

• MXWNCS2/4/8 Networked Chargers
• MXWANI4/8 Audio Network Interfaces
• MXWAPT2/4/8 Access Point Transceivers
• MXW1/2/6/8 Wireless Microphones

Bug Fixes

• When an interfering DECT device is transmitting nearby an MXW Access Point, the Access point may occasionally drop the connection to microphones 1-4. To recover mic connectivity, reset the Access Point.
  • Examples of interfering DECT devices are other MXW Access Points that are not on the same subnet as the affected Access point; however, in many cases, the interfering DECT devices are wireless headsets for wired desk telephones.
• MXW microphones intermittently drop off the Monitor status screen and their LED turns from green to flashing red for 10 to 30 seconds before recovering back to green, and then recovering their status activity on the Monitor screen. This may occur in environments with large reflective surfaces, such as windows, large LED monitors, and auditoriums with high walls and ceilings. These environments introduce RF reflections that interfere with the heartbeat signal from an MXW Access Point to a microphone. Microphones overcompensate for the interference and lose connectivity with the Access Point, restarting the scan process (seen as a red blinking LED) to find a valid Access Point signal.

Known Issue

• SystemOn 3.0.1 is compatible with MXW 6.0.3, but will incorrectly warn “Check system requirements, your current firmware version may not be confirmed compatible.”

Notes

• To operate MXW version 6.0.3 with other Shure networked systems, see the following list of minimum software and firmware versions:
  • SCM820 1.3.3
  • Shure Web Device Discovery 1.2
  • Shure Update Utility 2.4.3
  • SystemOn 3.0.1