This is a public Discussion Forum  public

Topic

    Liam135db
    Ability to merge scan data from different devices
    Topic posted December 16, 2011 by Liam135dbCompetent 
    178 Views, 4 Comments
    Title:
    Ability to merge scan data from different devices
    Description:
    Hi Guys
    Is there any possibility to add a function for merging scan data.

    I would like to be able to add multiple scans and get WWB to merge the files so that it would take a peak level for a given frequency from any of the imported scans.

    An example of operating practice where this could be useful would be moving antennas between scans, performing multiple scans around a large stage, eg with a PSM1K pack. Winradio scans from WWB5 in different positions onstage.

    This would almost be like "flattening" a waterfall plot, and would allow you to effectively import a "worstcase scenario" for interference.

    This feature would benefit from the ability to "equalise" the sensitivity of the scans to align noise floor, and then treat the aggregate scan data as if it were one scan.

    Speak soon

    Comment

     

    • Sam Drazin
      ...
      I would like to be able to add multiple scans and get WWB to merge the files so that it would take a peak level for a given frequency from any of the imported scans.

      An example of operating practice where this could be useful would be moving antennas between scans, performing multiple scans around a large stage, eg with a PSM1K pack. Winradio scans from WWB5 in different positions onstage.

      This would almost be like "flattening" a waterfall plot, and would allow you to effectively import a "worstcase scenario" for interference.
      ...




      Liam, the short answer is: this feature already exists. It might not be clear, however, which data Wireless Workbench is using to generate exclusions. Let me explain with the long answer.

      First off, the assumption is that you have the preference checked to "Automatically calculate exclusions from scan data". This can be set from the Coordination tab of the Preferences menu.

      In the Frequency Coordination tab, the Peak Hold of all scans stored in the Coordination Plot (the embedded plot in the Frequency Coordination tab) is always used to generate exclusions. You can tell which scan files you have loaded because they are all listed in the left side bar under the "Scan Data" section. What's more, this data will be combined with any live scans you've performed, which will be listed in the "Recent Scans" section. Data from both sections will be combined and used to generate exclusions.

      You may want to utilize a combination of saved scan files and live scans to build up a "worst-case" scenario of an RF environment. A simple way to do this would be to perform live scans with your networked Shure devices (or WiNRADiO scanner), and import all desired scan files into WWB such that all data is listed on the left sidebar of the Frequency Coordination tab (in either the "Scan Data" or "Recent Scans" sections). This can be done using the Scan Data dialog, accessible from the Frequency Coordination tab by selecting "Change Scan Data...".

      Performing Frequency Coordination or Analysis will take the Peak Hold of all scan data loaded into the Coordination Plot into account.

      To view the Peak Hold of all data loaded into the plot view, select the "Peak Hold" entry from the Overlays section in the bottom of the left sidebar. This will draw the peak of all scan data loaded in the Coordination plot, regardless of whether the source data is being viewed. By default, the plot-color associated with the Peak Hold will be red.

      It is important to note that the exclusion threshold set in the Coordination plot will be critical in deciding which frequencies are considered exclusions, and which are not.

      NOTE: All scan data listed in the 2 sections on the left sidebar of the Frequency Coordination tab will be used to generating exclusions regardless of whether or not each scan is visible. Even if the scan data is not being displayed (the scan file is not selected and shown on the plot), that scan data will still influence the generation of exclusions.
    • Liam135db
      Sorry Sam, I think I confused things a bit and didn't explain myself properly,
      When using Diversity receivers such as UHF-R, I think it makes a lot more sense to use those receivers for scans rather than the Winradio which I use for most of my 'general' scanning and for covering ranges which I do not have a networkable receiver, eg PSM900, Senn G2/G3 IEMs

      If I import scans from different sources, the sensitivity of the device depicts the noise floor for that scan.
      In WWB6, I can only set one exclusion threshold, so I would like to be able to 'adjust' the scan data so as to equalise the noise floor, and allow the exclusion threshold to remain relevant for all scans, regardless of source.
      Of course, an alternative would be able to adjust the exclusion threshold for different parts of the spectrum, to allow for the variances in sensitivity.

      Not sure if that makes more sense :-)

      Liam
    • Sam Drazin
      Liam, I now understand what you are asking for, thank you for clarifying. You are suggesting methods for considering various noise floor levels of different scans with multiple exclusion thresholds. This is currently not a feature in WWB6, although it is a great idea.
    • Liam135db
      Yep, either allowing multiple exclusion thresholds or having a "trim" for the scan data.
      Kinda like the trim adjustment that can be made to a captured trace in smaart Live 5 (not sure if its available in later versions).
      I would've thought it would be easier to program the ability to "move" a scan trace than to having to work out how to define multiple exclusion thresholds and how to transition between them etc. Unless that was defined by the actual scan trace as you import it, maybe? I think I'd rather trim the scans.

      Met Up with JD yesterday, and he suggested that the apparent difference in noise floor could be down to the RBW of the scans. It seems that it isnt an adjustable parameter when using UR4s to scan though, unlike the AXT600. I still got better results on my coordination after scanning with the UR4s today than I did using the winradio scan. I think that was down to the known offset in WWB5 (when capturing from winradio), and the fact there was a lot of background noise in that band.
      Think I need to try playing with some of the newer units (PSM1Ks AXT600 etc) to get a good comparison against each other.
      I'm kinda running with the idea that while I know the winradio isn't the best option, its better than no scan in moderately noisey areas, but has its limitations, which I watch out for.

      Guess thats probably good advice for anyone using the Winradio/WWB5/WWB6 workaround, to be aware of.

     

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