Hi, 
Guest
Pic
Sign In

usrp-users@lists.ettus.com

Discussion and technical support related to USRP, UHD, RFNoC

View all threads

fifo ctrl timed out error (LFRX on a N210)

MF
Mikio Fukushima
Mon, Oct 17, 2022 7:41 AM

Hi,
I want to use one or two channels on one LFRX on a N210 on Windows.
but fifo ctrl timeout error occured.
uhd_usrp_probe, uhd_find_device and ping are OK.
Why?

  • Environment

Windows 10
UHD 4.3.0.0 (x64, VS2019)
LFRX on USRP2(r4)

  • error message

C:\Program Files\UHD\lib\uhd\examples>rx_samples_to_file.exe --args
"addr=192.168.1.52" --rate 1e6  --freq 1e6

Creating the usrp device with: addr=192.168.1.52...
[INFO] [UHD] Win32; Microsoft Visual C++ version 1925; Boost_107000;
UHD_4.2.0.0-release
[INFO] [USRP2] Opening a USRP2/N-Series device...
[INFO] [USRP2] Current recv frame size: 1472 bytes
[INFO] [USRP2] Current send frame size: 1472 bytes
Using Device: Single USRP:
Device: USRP2 / N-Series Device
Mboard 0: USRP2 r4
RX Channel: 0
RX DSP: 0
RX Dboard: A
RX Subdev: LFRX (AB)
TX Channel: 0
TX DSP: 0
TX Dboard: A
TX Subdev: LFTX (AB)

Setting RX Rate: 1.000000 Msps...
[ERROR] [UHD] Exception caught in safe-call.
in usrp2_fifo_ctrl_impl::~usrp2_fifo_ctrl_impl
at
C:\Users\buildbot\worker0\Builder_uhdPackage_Windows_x64_vs2019\work\uhd\host\lib\usrp\usrp2\usrp2_fifo_ctrl.cpp:51
this->peek32(0); -> RuntimeError: fifo ctrl timed out looking for acks
Error: LookupError: IndexError: multi_usrp: RX channel 12 out of range for
configured RX frontends

Hi, I want to use one or two channels on one LFRX on a N210 on Windows. but fifo ctrl timeout error occured. uhd_usrp_probe, uhd_find_device and ping are OK. Why? - Environment Windows 10 UHD 4.3.0.0 (x64, VS2019) LFRX on USRP2(r4) - error message C:\Program Files\UHD\lib\uhd\examples>rx_samples_to_file.exe --args "addr=192.168.1.52" --rate 1e6 --freq 1e6 Creating the usrp device with: addr=192.168.1.52... [INFO] [UHD] Win32; Microsoft Visual C++ version 1925; Boost_107000; UHD_4.2.0.0-release [INFO] [USRP2] Opening a USRP2/N-Series device... [INFO] [USRP2] Current recv frame size: 1472 bytes [INFO] [USRP2] Current send frame size: 1472 bytes Using Device: Single USRP: Device: USRP2 / N-Series Device Mboard 0: USRP2 r4 RX Channel: 0 RX DSP: 0 RX Dboard: A RX Subdev: LFRX (AB) TX Channel: 0 TX DSP: 0 TX Dboard: A TX Subdev: LFTX (AB) Setting RX Rate: 1.000000 Msps... [ERROR] [UHD] Exception caught in safe-call. in usrp2_fifo_ctrl_impl::~usrp2_fifo_ctrl_impl at C:\Users\buildbot\worker0\Builder_uhdPackage_Windows_x64_vs2019\work\uhd\host\lib\usrp\usrp2\usrp2_fifo_ctrl.cpp:51 this->peek32(0); -> RuntimeError: fifo ctrl timed out looking for acks Error: LookupError: IndexError: multi_usrp: RX channel 12 out of range for configured RX frontends
MD
Marcus D. Leech
Mon, Oct 17, 2022 2:18 PM

On 2022-10-17 03:41, Mikio Fukushima wrote:

Hi,
I want to use one or two channels on one LFRX on a N210 on Windows.
but fifo ctrl timeout error occured.
uhd_usrp_probe, uhd_find_device and ping are OK.
Why?

  • Environment

Windows 10
UHD 4.3.0.0 (x64, VS2019)
LFRX on USRP2(r4)

  • error message

C:\Program Files\UHD\lib\uhd\examples>rx_samples_to_file.exe --args
"addr=192.168.1.52" --rate 1e6  --freq 1e6

Creating the usrp device with: addr=192.168.1.52...
[INFO] [UHD] Win32; Microsoft Visual C++ version 1925; Boost_107000;
UHD_4.2.0.0-release
[INFO] [USRP2] Opening a USRP2/N-Series device...
[INFO] [USRP2] Current recv frame size: 1472 bytes
[INFO] [USRP2] Current send frame size: 1472 bytes
Using Device: Single USRP:
  Device: USRP2 / N-Series Device
  Mboard 0: USRP2 r4
  RX Channel: 0
    RX DSP: 0
    RX Dboard: A
    RX Subdev: LFRX (AB)
  TX Channel: 0
    TX DSP: 0
    TX Dboard: A
    TX Subdev: LFTX (AB)

Setting RX Rate: 1.000000 Msps...
[ERROR] [UHD] Exception caught in safe-call.
  in usrp2_fifo_ctrl_impl::~usrp2_fifo_ctrl_impl
  at
C:\Users\buildbot\worker0\Builder_uhdPackage_Windows_x64_vs2019\work\uhd\host\lib\usrp\usrp2\usrp2_fifo_ctrl.cpp:51
this->peek32(0); -> RuntimeError: fifo ctrl timed out looking for acks
Error: LookupError: IndexError: multi_usrp: RX channel 12 out of range
for configured RX frontends

The "fifo ctrl timed out" message usually happens when the network
buffering is inadequate, and UHD is losing packets--although
  at 1Msps, it surely shouldn't be.  But this is a windows deployment,
and I'm much less familiar with its quirks.

The MORE concerning thing is the message about RX channel 12 out of
range.   I'm not sure what it's trying to convey,
  but there's no way to have 12 channels on a single USRP N210.

Could you try dropping back to an older version of UHD (3.15 perhaps?)
to see if this is still present?

On 2022-10-17 03:41, Mikio Fukushima wrote: > Hi, > I want to use one or two channels on one LFRX on a N210 on Windows. > but fifo ctrl timeout error occured. > uhd_usrp_probe, uhd_find_device and ping are OK. > Why? > > - Environment > > Windows 10 > UHD 4.3.0.0 (x64, VS2019) > LFRX on USRP2(r4) > > - error message > > C:\Program Files\UHD\lib\uhd\examples>rx_samples_to_file.exe --args > "addr=192.168.1.52" --rate 1e6  --freq 1e6 > > Creating the usrp device with: addr=192.168.1.52... > [INFO] [UHD] Win32; Microsoft Visual C++ version 1925; Boost_107000; > UHD_4.2.0.0-release > [INFO] [USRP2] Opening a USRP2/N-Series device... > [INFO] [USRP2] Current recv frame size: 1472 bytes > [INFO] [USRP2] Current send frame size: 1472 bytes > Using Device: Single USRP: >   Device: USRP2 / N-Series Device >   Mboard 0: USRP2 r4 >   RX Channel: 0 >     RX DSP: 0 >     RX Dboard: A >     RX Subdev: LFRX (AB) >   TX Channel: 0 >     TX DSP: 0 >     TX Dboard: A >     TX Subdev: LFTX (AB) > > Setting RX Rate: 1.000000 Msps... > [ERROR] [UHD] Exception caught in safe-call. >   in usrp2_fifo_ctrl_impl::~usrp2_fifo_ctrl_impl >   at > C:\Users\buildbot\worker0\Builder_uhdPackage_Windows_x64_vs2019\work\uhd\host\lib\usrp\usrp2\usrp2_fifo_ctrl.cpp:51 > this->peek32(0); -> RuntimeError: fifo ctrl timed out looking for acks > Error: LookupError: IndexError: multi_usrp: RX channel 12 out of range > for configured RX frontends > The "fifo ctrl timed out" message usually happens when the network buffering is inadequate, and UHD is losing packets--although   at 1Msps, it surely shouldn't be.  But this is a windows deployment, and I'm much less familiar with its quirks. The MORE concerning thing is the message about RX channel 12 out of range.   I'm not sure what it's trying to convey,   but there's no way to have 12 channels on a single USRP N210. Could you try dropping back to an older version of UHD (3.15 perhaps?) to see if this is still present?
MF
Mikio Fukushima
Tue, Oct 18, 2022 4:23 AM

Hi, Marcus
Thank you for your reply.

I tried a UHD 3.15(x64 VS2009).
There is no "Error: LookupError: IndexError: multi_usrp: RX channel 12 out
of range for configured RX frontends".
But when press "Ctrl + C" to stop rx_samples_to_file.exe then fifo timed
out error occured.

Setting RX Freq: 1.000000 MHz...
Setting RX LO Offset: 0.000000 MHz...
Actual RX Freq: 1.000000 MHz...

Press Ctrl + C to stop streaming...

Done!

[ERROR] [UHD] Exception caught in safe-call.
in __cdecl usrp2_fifo_ctrl_impl::~usrp2_fifo_ctrl_impl(void)
at
C:\Users\buildbot\worker\Builder_uhdPackage_Windows_x64_vs2019\work\uhd\host\lib\usrp\usrp2\usrp2_fifo_ctrl.cpp:54
this->peek32(0); -> RuntimeError: fifo ctrl timed out looking for acks

Thanks.

2022年10月17日(月) 23:19 Marcus D. Leech patchvonbraun@gmail.com:

On 2022-10-17 03:41, Mikio Fukushima wrote:

Hi,
I want to use one or two channels on one LFRX on a N210 on Windows.
but fifo ctrl timeout error occured.
uhd_usrp_probe, uhd_find_device and ping are OK.
Why?

  • Environment

Windows 10
UHD 4.3.0.0 (x64, VS2019)
LFRX on USRP2(r4)

  • error message

C:\Program Files\UHD\lib\uhd\examples>rx_samples_to_file.exe --args
"addr=192.168.1.52" --rate 1e6  --freq 1e6

Creating the usrp device with: addr=192.168.1.52...
[INFO] [UHD] Win32; Microsoft Visual C++ version 1925; Boost_107000;
UHD_4.2.0.0-release
[INFO] [USRP2] Opening a USRP2/N-Series device...
[INFO] [USRP2] Current recv frame size: 1472 bytes
[INFO] [USRP2] Current send frame size: 1472 bytes
Using Device: Single USRP:
Device: USRP2 / N-Series Device
Mboard 0: USRP2 r4
RX Channel: 0
RX DSP: 0
RX Dboard: A
RX Subdev: LFRX (AB)
TX Channel: 0
TX DSP: 0
TX Dboard: A
TX Subdev: LFTX (AB)

Setting RX Rate: 1.000000 Msps...
[ERROR] [UHD] Exception caught in safe-call.
in usrp2_fifo_ctrl_impl::~usrp2_fifo_ctrl_impl
at
C:\Users\buildbot\worker0\Builder_uhdPackage_Windows_x64_vs2019\work\uhd\host\lib\usrp\usrp2\usrp2_fifo_ctrl.cpp:51
this->peek32(0); -> RuntimeError: fifo ctrl timed out looking for acks
Error: LookupError: IndexError: multi_usrp: RX channel 12 out of range for
configured RX frontends

The "fifo ctrl timed out" message usually happens when the network
buffering is inadequate, and UHD is losing packets--although
at 1Msps, it surely shouldn't be.  But this is a windows deployment, and
I'm much less familiar with its quirks.

The MORE concerning thing is the message about RX channel 12 out of
range.  I'm not sure what it's trying to convey,
but there's no way to have 12 channels on a single USRP N210.

Could you try dropping back to an older version of UHD (3.15 perhaps?) to
see if this is still present?

USRP-users mailing list -- usrp-users@lists.ettus.com
To unsubscribe send an email to usrp-users-leave@lists.ettus.com

--
2021/09/27から新事務所に移転しました！

---=
福島 幹雄 (Mikio Fukushima)
株式会社ドルフィンシステム (Dolphin System Co.,Ltd)

〒171-0014 東京都豊島区池袋１－８－５
ミントロンビル５Ｆ

Mail: mikio@dolphinsystem.jp
URL : http://www.dolphinsystem.jp/
TEL/FAX : 03-6658-4949

---=

Hi, Marcus Thank you for your reply. I tried a UHD 3.15(x64 VS2009). There is no "Error: LookupError: IndexError: multi_usrp: RX channel 12 out of range for configured RX frontends". But when press "Ctrl + C" to stop rx_samples_to_file.exe then fifo timed out error occured. Setting RX Freq: 1.000000 MHz... Setting RX LO Offset: 0.000000 MHz... Actual RX Freq: 1.000000 MHz... Press Ctrl + C to stop streaming... Done! [ERROR] [UHD] Exception caught in safe-call. in __cdecl usrp2_fifo_ctrl_impl::~usrp2_fifo_ctrl_impl(void) at C:\Users\buildbot\worker\Builder_uhdPackage_Windows_x64_vs2019\work\uhd\host\lib\usrp\usrp2\usrp2_fifo_ctrl.cpp:54 this->peek32(0); -> RuntimeError: fifo ctrl timed out looking for acks Thanks. 2022年10月17日(月) 23:19 Marcus D. Leech <patchvonbraun@gmail.com>: > On 2022-10-17 03:41, Mikio Fukushima wrote: > > Hi, > I want to use one or two channels on one LFRX on a N210 on Windows. > but fifo ctrl timeout error occured. > uhd_usrp_probe, uhd_find_device and ping are OK. > Why? > > - Environment > > Windows 10 > UHD 4.3.0.0 (x64, VS2019) > LFRX on USRP2(r4) > > - error message > > C:\Program Files\UHD\lib\uhd\examples>rx_samples_to_file.exe --args > "addr=192.168.1.52" --rate 1e6 --freq 1e6 > > Creating the usrp device with: addr=192.168.1.52... > [INFO] [UHD] Win32; Microsoft Visual C++ version 1925; Boost_107000; > UHD_4.2.0.0-release > [INFO] [USRP2] Opening a USRP2/N-Series device... > [INFO] [USRP2] Current recv frame size: 1472 bytes > [INFO] [USRP2] Current send frame size: 1472 bytes > Using Device: Single USRP: > Device: USRP2 / N-Series Device > Mboard 0: USRP2 r4 > RX Channel: 0 > RX DSP: 0 > RX Dboard: A > RX Subdev: LFRX (AB) > TX Channel: 0 > TX DSP: 0 > TX Dboard: A > TX Subdev: LFTX (AB) > > Setting RX Rate: 1.000000 Msps... > [ERROR] [UHD] Exception caught in safe-call. > in usrp2_fifo_ctrl_impl::~usrp2_fifo_ctrl_impl > at > C:\Users\buildbot\worker0\Builder_uhdPackage_Windows_x64_vs2019\work\uhd\host\lib\usrp\usrp2\usrp2_fifo_ctrl.cpp:51 > this->peek32(0); -> RuntimeError: fifo ctrl timed out looking for acks > Error: LookupError: IndexError: multi_usrp: RX channel 12 out of range for > configured RX frontends > > The "fifo ctrl timed out" message usually happens when the network > buffering is inadequate, and UHD is losing packets--although > at 1Msps, it surely shouldn't be. But this is a windows deployment, and > I'm much less familiar with its quirks. > > The MORE concerning thing is the message about RX channel 12 out of > range. I'm not sure what it's trying to convey, > but there's no way to have 12 channels on a single USRP N210. > > Could you try dropping back to an older version of UHD (3.15 perhaps?) to > see if this is still present? > > > > _______________________________________________ > USRP-users mailing list -- usrp-users@lists.ettus.com > To unsubscribe send an email to usrp-users-leave@lists.ettus.com > -- 2021/09/27から新事務所に移転しました！ ================================== 福島 幹雄 (Mikio Fukushima) 株式会社ドルフィンシステム (Dolphin System Co.,Ltd) 〒171-0014 東京都豊島区池袋１－８－５ ミントロンビル５Ｆ Mail: mikio@dolphinsystem.jp URL : http://www.dolphinsystem.jp/ TEL/FAX : 03-6658-4949 ==================================
MD
Marcus D. Leech
Tue, Oct 18, 2022 4:32 PM

On 2022-10-18 00:23, Mikio Fukushima wrote:

Hi, Marcus
Thank you for your reply.

I tried a UHD 3.15(x64 VS2009).
There is no "Error: LookupError: IndexError: multi_usrp: RX channel 12
out of range for configured RX frontends".
But when press "Ctrl + C" to stop rx_samples_to_file.exe then fifo
timed out error occured.

Setting RX Freq: 1.000000 MHz...
Setting RX LO Offset: 0.000000 MHz...
Actual RX Freq: 1.000000 MHz...

Press Ctrl + C to stop streaming...

Done!

[ERROR] [UHD] Exception caught in safe-call.
 in __cdecl usrp2_fifo_ctrl_impl::~usrp2_fifo_ctrl_impl(void)
 at
C:\Users\buildbot\worker\Builder_uhdPackage_Windows_x64_vs2019\work\uhd\host\lib\usrp\usrp2\usrp2_fifo_ctrl.cpp:54
this->peek32(0); -> RuntimeError: fifo ctrl timed out looking for acks

Thanks.

That's probably just due to the way Windows deals with interrupted
system calls, and doesn't mean anything is broken.

On 2022-10-18 00:23, Mikio Fukushima wrote: > Hi, Marcus > Thank you for your reply. > > I tried a UHD 3.15(x64 VS2009). > There is no "Error: LookupError: IndexError: multi_usrp: RX channel 12 > out of range for configured RX frontends". > But when press "Ctrl + C" to stop rx_samples_to_file.exe then fifo > timed out error occured. > > Setting RX Freq: 1.000000 MHz... > Setting RX LO Offset: 0.000000 MHz... > Actual RX Freq: 1.000000 MHz... > > Press Ctrl + C to stop streaming... > > Done! > > [ERROR] [UHD] Exception caught in safe-call. >  in __cdecl usrp2_fifo_ctrl_impl::~usrp2_fifo_ctrl_impl(void) >  at > C:\Users\buildbot\worker\Builder_uhdPackage_Windows_x64_vs2019\work\uhd\host\lib\usrp\usrp2\usrp2_fifo_ctrl.cpp:54 > this->peek32(0); -> RuntimeError: fifo ctrl timed out looking for acks > > Thanks. > > That's probably just due to the way Windows deals with interrupted system calls, and doesn't mean anything is broken.
Empathy v1.0   2025 ©emwd.com
Documentation