This is a public Discussion Forum  public

Topic

    hyoseob
    timed out waiting for the scanner to respond' shows up
    Topic posted October 8, 2013 by hyoseobNovice 
    710 Views, 8 Comments
    Title:
    timed out waiting for the scanner to respond' shows up
    Description:

    On Win8 / WWB 6.8.1.1(latest version) with AXT400(also latest version, 1.13.5), when it starts to do frequency plot or scan, it shows up a pop up message. - 'timed out waiting for the scanner to respond'

    There is no problem in network connection. It even run with permission in administrator. I'd like to know what is the matter.

    Answer

     

    • buhmanb

      Here is some background:

      There is an exchange of messages between WWB and the device performing the scan, in your case an AXT400.

      If any of that message exchange fails, then WWB will "time out" waiting for the response.

      There had been some issues during development and testing which I thought had all been fixed. The majority of the earlier issues related to:

      1. WWB requesting out of range values that the AXT400 could not actually scan.

      2. AXT400 already had some other scan in progress, or had terminated a scan non-gracefully. (i.e. powered lost in the middle of a scan)

      While I don't like suggesting "Reboot the AXT400, and try again" - that might work around any case of the scan not terminated correctly.

      More likely - WWB may be requesting an out of range value that we didn't catch before.

      What is the model of your AXT400? i.e. AXT400 D, AXT400 J, ?

      And in the "Scanner Setup" dialog - what are the values chosen for:

      Band: ?

      Scan Status: ?

      Band Preset: ?

      Start: ?

      Stop: ?

      Could you attach a copy of the show file?

      My hunch is that if you are in Korea, that you may have a mix of bands and frequency ranges that could confuse the AXT400.

      Or there have been some rare cases where Firewalls have blocked the messages from the AXT400, resulting in WWB "timing out"

      Can you try disabling all firewalls, try a scan, then re-enable what firewalls you need.

      Best luck!

    • hyoseob

      Sorry for late feedback.

      The cause of "timing out' was on Firewalls. Now everything is okay :)

      Many thanks!

    • sharktooth

      Hi,

      I have the same message with an UR4D Q5 running with WWB 6.8.1.1 on windows 7.

      The firewall is deactivated, I have no problem doing a scan with an other UR4D+ P8, and managed to make a scan with WWB 5.0.4.18 and UR4D Q5.

      The firmware is 1.67 on both devices. Did anybody had this problem too?

      Thanks

    • cwichura

      I've had this a few times with WWB6 on MacOS. It crops up for me when stopping and restarting a scan. Usually fixes itself if you wait a couple minutes before trying to start a scan again, at least in my experience. My UR4Ds have firmware 1.66. I think when this happens, you also get messages in the audit log saying the receiver was disconnected and then reconnected a bit later, which makes me think the receiver has crashed and automatically rebooted itself. Except you don't see an indicaion of this on the front panel (unless the network stuff is handled by a daughter card or something running its own OS, or maybe its a separate process that segfaults and gets restarted or somesuch).

    • sharktooth
      Ok it's still not working for me, I also tried under OSX, it didn't worked neither, it may be the device.
    • Ludo

      Hi,

      I have the same message with an UR4D Q5 running with WWB 6.8.1.1 on windows 7.

      The firewall is deactivated, I have no problem doing a scan with an other UR4D+ P8, and managed to make a scan with WWB 5.0.4.18 and UR4D Q5.

      The firmware is 1.67 on both devices. Did anybody had this problem too?

      Thanks

      Hi Guillaume,

      You can get such message if you're trying to perform a scan with a band limited receiver. In your case, WWB6 is trying to scan the full Q5 band (740 - 814 MHz) but your receiver is band limited up to 790 MHz. I guess.

      To avoid this message, try in WWB scan window to perform a scan between 740 and 790 MHz by changing the upper frequency.

      Hope this can help you

      Ludo

      Algam - Shure France

    • sharktooth

      Merci Ludo,
      I'll try this next tuesday then; that would mean that the receiver band limit is software dependant, since I was able to perform a scan from WWB5?

    • sharktooth

      Hi there,

      indeed it's working good if I limit the scan up to 790MHz. Though it's still weird that it worked pretty well with wwb5.

      Thanks again.

     

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