Shure Wireless Workbench 6 - Frequency Coordination Tab

Поделиться
HTML-код
  • Опубликовано: 24 ноя 2024
  • Create a comprehensive frequency coordination for your wireless rig in the Frequency Coordination Tab.
    Scan the RF spectrum to visualize RF activity and avoid noisy spectrum.
    Calculate clean and compatible frequencies to assign and deploy to your Inventory, saving both time and effort. Coordinated frequencies can be deployed directly to Shure networked components.
    Download WWB6 for free: www.shure.com/a...
    Access the WWB6 Forum to interact with WWB6 experts around the globe: shure-community...

Комментарии • 8

  • @metalstrand2795
    @metalstrand2795 6 лет назад +5

    Best Workbench "beginner" video I have come across so far.

    • @shure
      @shure  6 лет назад

      Glad you found it helpful!

  • @RD-ni7qe
    @RD-ni7qe Год назад

    Can this is be used for calculating IM with non-Shure products, such as 2-Way VHF/UHF Radio Base Stations and FM band Transmitters?

  • @user-gx3st2th8q
    @user-gx3st2th8q 6 лет назад

    Should I do this with our transmitters (HH, LAV) off?

    • @shure
      @shure  6 лет назад +1

      In short, yes. We recommend that any spectrum scans captured for the purposes of classifying your RF environment be performed with all of your own wireless systems off (or RF muted). This will allow the scan to best capture the raw environment, and best enable WWB6 to optimally fit frequencies for your wireless systems into the spectrum.

  • @MEANDMYHOMEGIRLSPODCAST
    @MEANDMYHOMEGIRLSPODCAST 5 лет назад

    After I assign and deploy the frequencies to my units, I notice they no longer have a group number and a channel number. Am i missing a step?
    Very helpful video though.

    • @shure
      @shure  5 лет назад

      Great question, Michael! Our support team can talk you through this. You can reach them by submitting this form: www.shure.com/contact

    • @r0bertfrank
      @r0bertfrank 5 лет назад +3

      I had the same situation, which I realized isn't an issue: I believe it indicates that the frequency that is being deployed to said channel is not included in the factory default groups/channels configuration. So for instance, 492.425 MHz isn't included in any channel of any group, but is still a valid frequency to occupy and operate on.