Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
Error: E_FETCH_SIGNAL_HW_TIMEOUT _ RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello,

    I am running simple rx/tx experiment with iperf. However, I am having trouble with the error called E_FETCH_SIGNAL_HW_TIMEOUT. The error message are shown below.

    We installed SDRmini port driver to Windows XP. SDK version 1.6 and the board have WBX radio front end plugged in. Our desktop PC is shuttle PC model SZ77R5.

    Sender's IP 192.168.0.100 and receiver's IP 192.168.0.200.

    Sender's side is running: iperf -c 192.168.0.255 -i 1 -t 1000000 -l 1000 -u -b 10m

    Receiver's side is running:  iperf -s -i 1 -u and rxgain was set using dot11config.exe --rxgain 0x3a00 

    This error will not appear immediately. In general, this problem will show up after we run such experiment about 20 minutes or even longer. Also, both sender and receiver could have chance to get this error. 

    Uninstall and re-install driver cannot solve this problem. The only solution we currently have is to turn off the machine and turn on again after few minutes. 

    Can anyone tell us where to troubleshoot for this type of problem.

    Thanks in advance

    Muye Liu 

    04642804 1479.69055176 [RX] BB11ARx succeed, packet length=1064
    04642805 1479.69055176 [RX] Destination is not ONLY me
    04646401 1480.07116699 [MAC_CS][Error] E_FETCH_SIGNAL_HW_TIMEOUT
    04646402 1480.07116699 [Error] E_FETCH_SIGNAL_HW_TIMEOUT
    04646403 1480.07128906 [MAC_CS][Error] E_FETCH_SIGNAL_HW_TIMEOUT
    04646404 1480.07128906 [Error] E_FETCH_SIGNAL_HW_TIMEOUT
    04646405 1480.07165527 [MAC_CS][Error] E_FETCH_SIGNAL_HW_TIMEOUT
    04646406 1480.07165527 [Error] E_FETCH_SIGNAL_HW_TIMEOUT
    04646407 1480.07165527 [Error] Reset MAC send
    04646408 1480.07177734 [MAC_CS][Error] E_FETCH_SIGNAL_HW_TIMEOUT
    04646409 1480.07177734 [Error] E_FETCH_SIGNAL_HW_TIMEOUT
    04646410 1480.07189941 [MAC_CS][Error] E_FETCH_SIGNAL_HW_TIMEOUT
    04646411 1480.07189941 [Error] E_FETCH_SIGNAL_HW_TIMEOUT
    04646412 1480.07202148 [MAC_CS][Error] E_FETCH_SIGNAL_HW_TIMEOUT
    04646413 1480.07202148 [Error] E_FETCH_SIGNAL_HW_TIMEOUT
    04646414 1480.07214355 [MAC_CS][Error] E_FETCH_SIGNAL_HW_TIMEOUT
    04646415 1480.07214355 [Error] E_FETCH_SIGNAL_HW_TIMEOUT
    04646416 1480.07250977 [MAC_CS][Error] E_FETCH_SIGNAL_HW_TIMEOUT
    04646417 1480.07250977 [Error] E_FETCH_SIGNAL_HW_TIMEOUT
    04646418 1480.07263184 [MAC_CS][Error] E_FETCH_SIGNAL_HW_TIMEOUT
    04646419 1480.07263184 [Error] E_FETCH_SIGNAL_HW_TIMEOUT
    04646420 1480.07275391 [MAC_CS][Error] E_FETCH_SIGNAL_HW_TIMEOUT
    04646421 1480.07275391 [Error] E_FETCH_SIGNAL_HW_TIMEOUT
    04646422 1480.07287598 [MAC_CS][Error] E_FETCH_SIGNAL_HW_TIMEOUT
    04646423 1480.07287598 [Error] E_FETCH_SIGNAL_HW_TIMEOUT
    04646424 1480.07299805 [MAC_CS][Error] E_FETCH_SIGNAL_HW_TIMEOUT
    04646425 1480.07299805 [Error] E_FETCH_SIGNAL_HW_TIMEOUT
    04646426 1480.07336426 [MAC_CS][Error] E_FETCH_SIGNAL_HW_TIMEOUT
    04646427 1480.07336426 [Error] E_FETCH_SIGNAL_HW_TIMEOUT
    04646428 1480.07348633 [MAC_CS][Error] E_FETCH_SIGNAL_HW_TIMEOUT
    04646429 1480.07348633 [Error] E_FETCH_SIGNAL_HW_TIMEOUT
    04646430 1480.07348633 [Error] Reset MAC send
    04646431 1480.07360840 [MAC_CS][Error] E_FETCH_SIGNAL_HW_TIMEOUT
    04646432 1480.07360840 [Error] E_FETCH_SIGNAL_HW_TIMEOUT
    04646433 1480.07373047 [MAC_CS][Error] E_FETCH_SIGNAL_HW_TIMEOUT
    04646434 1480.07373047 [Error] E_FETCH_SIGNAL_HW_TIMEOUT
    04646435 1480.07385254 [MAC_CS][Error] E_FETCH_SIGNAL_HW_TIMEOUT
    04646436 1480.07385254 [Error] E_FETCH_SIGNAL_HW_TIMEOUT

    Friday, October 25, 2013 7:00 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi Muye,
    The error code E_FETCH_SIGNAL_HW_TIMEOUT means that receiving a complete signal block is time out. Normally it indicates something goes wrong with hardware reception.
    1. You can try: disable the drivers, reset the RCB board, reset the radio board, enable the driver
    2. We recommend you use latest Sora SDK 2.0. You can conduct the same iperf experiment with HWTest.sys driver and user mode 802.11a/b sample 'umxsdrbrick.exe' or 'umxsdra.exe'. They are better supported and improved compared with the previous implementation.
    3. You can diagnose the sora to sora environemnt with 'umxdot11.exe', which is straight forward frame generator and monitor. It is easier to tune than a full-fledged MAC/PHY program.

    Thanks, -Qi

    • Edited by Qi LuoEditor Monday, October 28, 2013 5:53 AM
    • Proposed as answer by Qi LuoEditor Monday, October 28, 2013 5:54 AM
    • Marked as answer by MUYE20 Tuesday, July 22, 2014 1:12 AM
    Monday, October 28, 2013 5:52 AM
    Answerer
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Muye,

    You need to upgrade your RAB firmware to support WBX radio.

    You may need to contact V3 again to ensure that the proper firmware. Sora SDK version may not be an issue.

    Thanks,

    - Kun

    • Marked as answer by MUYE20 Tuesday, July 22, 2014 1:12 AM
    Tuesday, October 29, 2013 3:12 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi Muye,
    The error code E_FETCH_SIGNAL_HW_TIMEOUT means that receiving a complete signal block is time out. Normally it indicates something goes wrong with hardware reception.
    1. You can try: disable the drivers, reset the RCB board, reset the radio board, enable the driver
    2. We recommend you use latest Sora SDK 2.0. You can conduct the same iperf experiment with HWTest.sys driver and user mode 802.11a/b sample 'umxsdrbrick.exe' or 'umxsdra.exe'. They are better supported and improved compared with the previous implementation.
    3. You can diagnose the sora to sora environemnt with 'umxdot11.exe', which is straight forward frame generator and monitor. It is easier to tune than a full-fledged MAC/PHY program.

    Thanks, -Qi

    • Edited by Qi LuoEditor Monday, October 28, 2013 5:53 AM
    • Proposed as answer by Qi LuoEditor Monday, October 28, 2013 5:54 AM
    • Marked as answer by MUYE20 Tuesday, July 22, 2014 1:12 AM
    Monday, October 28, 2013 5:52 AM
    Answerer
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello Qi:

    Thanks for your suggestions.

    We will try the hardware reset you mentioned. 

    We have WBX radio front end plugged into the RCB board. Seems like this radio front end only works with SDK version 1.6.

    We contacted the V3 because we had "Error: no radio discovered" when we install SDK 2.0 to a Windows 7 desktop. The V3 tech support told us to use SDK 1.6 and Windows XP may solve the problem.

    However, we tried SDK 2.0 with Windows XP last week. It still produced error message "Error: no radio discovered". So, We think only SDK 1.6 works with WBX radio front end.

    Thanks

    Muye Liu



    Monday, October 28, 2013 8:13 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Muye,

    You need to upgrade your RAB firmware to support WBX radio.

    You may need to contact V3 again to ensure that the proper firmware. Sora SDK version may not be an issue.

    Thanks,

    - Kun

    • Marked as answer by MUYE20 Tuesday, July 22, 2014 1:12 AM
    Tuesday, October 29, 2013 3:12 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    The V3 tech support gave us a copy of firmware last month (Sep/13/2013). We have uploaded that firmware to the RAB, it still gave us the same error message "Error: no radio discovered". We had to contact V3 again because we got the same error. 

    V3 tech support told us they ran test before they shipped out these boards. At that moment, their testing machines have Windows XP and SDK 1.6 installed. That is why we downgraded OS from Windows 7 to Windows XP and installed SDK 1.6

    Thanks

    Muye Liu 

     

    Tuesday, October 29, 2013 4:59 AM