usrp-users@lists.ettus.com

Discussion and technical support related to USRP, UHD, RFNoC

View all threads

Re: [USRP-users] [Discuss-gnuradio] RuntimeError: fifo ctrl timed out looking for acks

MM
Marcus Müller
Tue, Jan 9, 2018 12:34 PM

Dear Bakshi,

this error is from UHD, not GNU Radio; an appropriate mailing list
would be usrp-users (in CC:).

Please follow up there with information on which USRP you're using,
what you're doing, and the full console output (not just the error).

Best regards,
Marcus

On Tue, 2018-01-09 at 02:01 +0000, Bakshi, Arjun wrote:

I get this error when trying to open 2 tx steams and 3 rx streams,
where some usrps are both rx and tx: "RuntimeError: fifo ctrl timed
out looking for acks"

I found a mention of the error on this page: http://www.ni.com/produc
t-documentation/53455/en/

Which gives a workaround: Open an Rx and Tx session to the same list
of devices. You can disable the unused channel in the session where
you added it.

How do I interpret this in GRC?

My specific setup is that I want to:
--- TX using usrps with IP1 and IP2
--- RX using usrps with IP1, IP3, and IP4

How do I go about doing this? How do I fill out the device args
fields and make the connections?

Thanks,

AB


Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Dear Bakshi, this error is from UHD, not GNU Radio; an appropriate mailing list would be usrp-users (in CC:). Please follow up *there* with information on which USRP you're using, what you're doing, and the full console output (not just the error). Best regards, Marcus On Tue, 2018-01-09 at 02:01 +0000, Bakshi, Arjun wrote: > I get this error when trying to open 2 tx steams and 3 rx streams, > where some usrps are both rx and tx: "RuntimeError: fifo ctrl timed > out looking for acks" > > I found a mention of the error on this page: http://www.ni.com/produc > t-documentation/53455/en/ > > Which gives a workaround: Open an Rx and Tx session to the same list > of devices. You can disable the unused channel in the session where > you added it. > > How do I interpret this in GRC? > > My specific setup is that I want to: > --- TX using usrps with IP1 and IP2 > --- RX using usrps with IP1, IP3, and IP4 > > How do I go about doing this? How do I fill out the device args > fields and make the connections? > > Thanks, > > AB > _______________________________________________ > Discuss-gnuradio mailing list > Discuss-gnuradio@gnu.org > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
BA
Bakshi, Arjun
Tue, Jan 9, 2018 6:36 PM

Hello all,

I have 4 USRP N210s synced with an octo-clock and connected to a host PC via a switch. I'm trying to use the multi-usrp blocks in GRC for the following setup:

-- TX using usrps with IP1 and IP2
-- RX using usrps with IP1, IP3, and IP4

All IPs are in the same subnet 192.168.10.X

I've attached the grc file and screenshot of the flowgraph.

I get the following output when trying to run the flowgraph (error in last line):

[INFO] [UHDlinux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_4.0.0.rfnoc-devel-409-gec9138eb] 
[INFO] [USRP2] Opening a USRP2/N-Series device...
[INFO] [USRP2] Current recv frame size: 1472 bytes
[INFO] [USRP2] Current send frame size: 1472 bytes
[INFO] [MULTI_USRP]     1) catch time transition at pps edge
[INFO] [MULTI_USRP]     2) set times next pps (synchronously)
[INFO] [USRP2] Opening a USRP2/N-Series device...
[INFO] [USRP2] Current recv frame size: 1472 bytes
[INFO] [USRP2] Current send frame size: 1472 bytes
[INFO] [MULTI_USRP]     1) catch time transition at pps edge
[INFO] [MULTI_USRP]     2) set times next pps (synchronously)
thread[thread-per-block[3]: <block gr uhd usrp source (18)>]: RuntimeError: fifo ctrl timed out looking for acks

The error shows up in the known issues page here: http://www.ni.com/product-documentation/53455/en/

With a workaround: Open an Rx and Tx session to the same list of devices. You can disable the unused channel in the session where you added it.

However, it is not clear to me how this can be done in GRC using the multi-usrp block. How does the "device arguments" field change? How do I "disable" unwanted/unused channels?

Is there a fix for this issue or just the workaround?

Thank you,

AB


From: Marcus Müller marcus.mueller@ettus.com
Sent: Tuesday, January 9, 2018 7:34:05 AM
To: Bakshi, Arjun; discuss-gnuradio@gnu.org
Cc: usrp-users
Subject: Re: [Discuss-gnuradio] RuntimeError: fifo ctrl timed out looking for acks

Dear Bakshi,

this error is from UHD, not GNU Radio; an appropriate mailing list
would be usrp-users (in CC:).

Please follow up there with information on which USRP you're using,
what you're doing, and the full console output (not just the error).

Best regards,
Marcus

On Tue, 2018-01-09 at 02:01 +0000, Bakshi, Arjun wrote:

I get this error when trying to open 2 tx steams and 3 rx streams,
where some usrps are both rx and tx: "RuntimeError: fifo ctrl timed
out looking for acks"

I found a mention of the error on this page: http://www.ni.com/produc
t-documentation/53455/en/

Which gives a workaround: Open an Rx and Tx session to the same list
of devices. You can disable the unused channel in the session where
you added it.

How do I interpret this in GRC?

My specific setup is that I want to:
--- TX using usrps with IP1 and IP2
--- RX using usrps with IP1, IP3, and IP4

How do I go about doing this? How do I fill out the device args
fields and make the connections?

Thanks,

AB


Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Discuss-gnuradio Info Page - lists.gnu.orghttps://lists.gnu.org/mailman/listinfo/discuss-gnuradio
lists.gnu.org
To see the collection of prior postings to the list, visit the Discuss-gnuradio Archives. Using Discuss-gnuradio: To post a message to all the list ...

Hello all, I have 4 USRP N210s synced with an octo-clock and connected to a host PC via a switch. I'm trying to use the multi-usrp blocks in GRC for the following setup: -- TX using usrps with IP1 and IP2 -- RX using usrps with IP1, IP3, and IP4 All IPs are in the same subnet 192.168.10.X I've attached the grc file and screenshot of the flowgraph. I get the following output when trying to run the flowgraph (error in last line): [INFO] [UHDlinux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_4.0.0.rfnoc-devel-409-gec9138eb]  [INFO] [USRP2] Opening a USRP2/N-Series device... [INFO] [USRP2] Current recv frame size: 1472 bytes [INFO] [USRP2] Current send frame size: 1472 bytes [INFO] [MULTI_USRP]  1) catch time transition at pps edge [INFO] [MULTI_USRP]  2) set times next pps (synchronously) [INFO] [USRP2] Opening a USRP2/N-Series device... [INFO] [USRP2] Current recv frame size: 1472 bytes [INFO] [USRP2] Current send frame size: 1472 bytes [INFO] [MULTI_USRP]  1) catch time transition at pps edge [INFO] [MULTI_USRP]  2) set times next pps (synchronously) thread[thread-per-block[3]: <block gr uhd usrp source (18)>]: RuntimeError: fifo ctrl timed out looking for acks The error shows up in the known issues page here: http://www.ni.com/product-documentation/53455/en/ With a workaround: Open an Rx and Tx session to the same list of devices. You can disable the unused channel in the session where you added it. However, it is not clear to me how this can be done in GRC using the multi-usrp block. How does the "device arguments" field change? How do I "disable" unwanted/unused channels? Is there a fix for this issue or just the workaround? Thank you, AB ________________________________ From: Marcus Müller <marcus.mueller@ettus.com> Sent: Tuesday, January 9, 2018 7:34:05 AM To: Bakshi, Arjun; discuss-gnuradio@gnu.org Cc: usrp-users Subject: Re: [Discuss-gnuradio] RuntimeError: fifo ctrl timed out looking for acks Dear Bakshi, this error is from UHD, not GNU Radio; an appropriate mailing list would be usrp-users (in CC:). Please follow up *there* with information on which USRP you're using, what you're doing, and the full console output (not just the error). Best regards, Marcus On Tue, 2018-01-09 at 02:01 +0000, Bakshi, Arjun wrote: > I get this error when trying to open 2 tx steams and 3 rx streams, > where some usrps are both rx and tx: "RuntimeError: fifo ctrl timed > out looking for acks" > > I found a mention of the error on this page: http://www.ni.com/produc > t-documentation/53455/en/ > > Which gives a workaround: Open an Rx and Tx session to the same list > of devices. You can disable the unused channel in the session where > you added it. > > How do I interpret this in GRC? > > My specific setup is that I want to: > --- TX using usrps with IP1 and IP2 > --- RX using usrps with IP1, IP3, and IP4 > > How do I go about doing this? How do I fill out the device args > fields and make the connections? > > Thanks, > > AB > _______________________________________________ > Discuss-gnuradio mailing list > Discuss-gnuradio@gnu.org > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio Discuss-gnuradio Info Page - lists.gnu.org<https://lists.gnu.org/mailman/listinfo/discuss-gnuradio> lists.gnu.org To see the collection of prior postings to the list, visit the Discuss-gnuradio Archives. Using Discuss-gnuradio: To post a message to all the list ...
BA
Bakshi, Arjun
Tue, Jan 9, 2018 9:42 PM

Never mind. Fixed it after reading this post: http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/2017-January/023347.html

TLDR: Increase read/write socket buffer sizes. Something like this:

sudo sysctl -w net.core.rmem_max=50000000
sudo sysctl -w net.core.wmem_max=50000000

And then making the device addresses the same and "consistent".

The multi usrp source and sink blocks take the exact same string for the device arguments field. In my case:

device args: "addr0=192.168.10.7,addr1=192.168.10.4,addr2=192.168.10.2,addr3=192.168.10.3"

I use usrps with last octet 7 and 4 to TX via the multi usrp sink block. I set the number of channels to 2 in that block, and therefore the first 2 IPs from the device args are used for TX-ing.

I use ALL usrps to RX via the multi usrp source block. I set the number of channels to 4 in that block, and therefore all the IPs from the device args are used for RX-ing.

This works out for my setup, but I don't know who it works for more complex setups.

Screenshot and grc file attached.

Thanks,

AB


From: Bakshi, Arjun
Sent: Tuesday, January 9, 2018 1:36:49 PM
To: usrp-users@lists.ettus.com
Subject: Re: [Discuss-gnuradio] RuntimeError: fifo ctrl timed out looking for acks

Hello all,

I have 4 USRP N210s synced with an octo-clock and connected to a host PC via a switch. I'm trying to use the multi-usrp blocks in GRC for the following setup:

-- TX using usrps with IP1 and IP2
-- RX using usrps with IP1, IP3, and IP4

All IPs are in the same subnet 192.168.10.X

I've attached the grc file and screenshot of the flowgraph.

I get the following output when trying to run the flowgraph (error in last line):

[INFO] [UHDlinux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_4.0.0.rfnoc-devel-409-gec9138eb] 
[INFO] [USRP2] Opening a USRP2/N-Series device...
[INFO] [USRP2] Current recv frame size: 1472 bytes
[INFO] [USRP2] Current send frame size: 1472 bytes
[INFO] [MULTI_USRP]     1) catch time transition at pps edge
[INFO] [MULTI_USRP]     2) set times next pps (synchronously)
[INFO] [USRP2] Opening a USRP2/N-Series device...
[INFO] [USRP2] Current recv frame size: 1472 bytes
[INFO] [USRP2] Current send frame size: 1472 bytes
[INFO] [MULTI_USRP]     1) catch time transition at pps edge
[INFO] [MULTI_USRP]     2) set times next pps (synchronously)
thread[thread-per-block[3]: <block gr uhd usrp source (18)>]: RuntimeError: fifo ctrl timed out looking for acks

The error shows up in the known issues page here: http://www.ni.com/product-documentation/53455/en/

With a workaround: Open an Rx and Tx session to the same list of devices. You can disable the unused channel in the session where you added it.

However, it is not clear to me how this can be done in GRC using the multi-usrp block. How does the "device arguments" field change? How do I "disable" unwanted/unused channels?

Is there a fix for this issue or just the workaround?

Thank you,

AB


From: Marcus Müller marcus.mueller@ettus.com
Sent: Tuesday, January 9, 2018 7:34:05 AM
To: Bakshi, Arjun; discuss-gnuradio@gnu.org
Cc: usrp-users
Subject: Re: [Discuss-gnuradio] RuntimeError: fifo ctrl timed out looking for acks

Dear Bakshi,

this error is from UHD, not GNU Radio; an appropriate mailing list
would be usrp-users (in CC:).

Please follow up there with information on which USRP you're using,
what you're doing, and the full console output (not just the error).

Best regards,
Marcus

On Tue, 2018-01-09 at 02:01 +0000, Bakshi, Arjun wrote:

I get this error when trying to open 2 tx steams and 3 rx streams,
where some usrps are both rx and tx: "RuntimeError: fifo ctrl timed
out looking for acks"

I found a mention of the error on this page: http://www.ni.com/produc
t-documentation/53455/en/

Which gives a workaround: Open an Rx and Tx session to the same list
of devices. You can disable the unused channel in the session where
you added it.

How do I interpret this in GRC?

My specific setup is that I want to:
--- TX using usrps with IP1 and IP2
--- RX using usrps with IP1, IP3, and IP4

How do I go about doing this? How do I fill out the device args
fields and make the connections?

Thanks,

AB


Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Discuss-gnuradio Info Page - lists.gnu.orghttps://lists.gnu.org/mailman/listinfo/discuss-gnuradio
lists.gnu.org
To see the collection of prior postings to the list, visit the Discuss-gnuradio Archives. Using Discuss-gnuradio: To post a message to all the list ...

Never mind. Fixed it after reading this post: http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/2017-January/023347.html TLDR: Increase read/write socket buffer sizes. Something like this: sudo sysctl -w net.core.rmem_max=50000000 sudo sysctl -w net.core.wmem_max=50000000 And then making the device addresses the same and "consistent". The multi usrp source and sink blocks take the exact same string for the device arguments field. In my case: device args: "addr0=192.168.10.7,addr1=192.168.10.4,addr2=192.168.10.2,addr3=192.168.10.3" I use usrps with last octet 7 and 4 to TX via the multi usrp sink block. I set the number of channels to 2 in that block, and therefore the first 2 IPs from the device args are used for TX-ing. I use ALL usrps to RX via the multi usrp source block. I set the number of channels to 4 in that block, and therefore all the IPs from the device args are used for RX-ing. This works out for my setup, but I don't know who it works for more complex setups. Screenshot and grc file attached. Thanks, AB ________________________________ From: Bakshi, Arjun Sent: Tuesday, January 9, 2018 1:36:49 PM To: usrp-users@lists.ettus.com Subject: Re: [Discuss-gnuradio] RuntimeError: fifo ctrl timed out looking for acks Hello all, I have 4 USRP N210s synced with an octo-clock and connected to a host PC via a switch. I'm trying to use the multi-usrp blocks in GRC for the following setup: -- TX using usrps with IP1 and IP2 -- RX using usrps with IP1, IP3, and IP4 All IPs are in the same subnet 192.168.10.X I've attached the grc file and screenshot of the flowgraph. I get the following output when trying to run the flowgraph (error in last line): [INFO] [UHDlinux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_4.0.0.rfnoc-devel-409-gec9138eb]  [INFO] [USRP2] Opening a USRP2/N-Series device... [INFO] [USRP2] Current recv frame size: 1472 bytes [INFO] [USRP2] Current send frame size: 1472 bytes [INFO] [MULTI_USRP]  1) catch time transition at pps edge [INFO] [MULTI_USRP]  2) set times next pps (synchronously) [INFO] [USRP2] Opening a USRP2/N-Series device... [INFO] [USRP2] Current recv frame size: 1472 bytes [INFO] [USRP2] Current send frame size: 1472 bytes [INFO] [MULTI_USRP]  1) catch time transition at pps edge [INFO] [MULTI_USRP]  2) set times next pps (synchronously) thread[thread-per-block[3]: <block gr uhd usrp source (18)>]: RuntimeError: fifo ctrl timed out looking for acks The error shows up in the known issues page here: http://www.ni.com/product-documentation/53455/en/ With a workaround: Open an Rx and Tx session to the same list of devices. You can disable the unused channel in the session where you added it. However, it is not clear to me how this can be done in GRC using the multi-usrp block. How does the "device arguments" field change? How do I "disable" unwanted/unused channels? Is there a fix for this issue or just the workaround? Thank you, AB ________________________________ From: Marcus Müller <marcus.mueller@ettus.com> Sent: Tuesday, January 9, 2018 7:34:05 AM To: Bakshi, Arjun; discuss-gnuradio@gnu.org Cc: usrp-users Subject: Re: [Discuss-gnuradio] RuntimeError: fifo ctrl timed out looking for acks Dear Bakshi, this error is from UHD, not GNU Radio; an appropriate mailing list would be usrp-users (in CC:). Please follow up *there* with information on which USRP you're using, what you're doing, and the full console output (not just the error). Best regards, Marcus On Tue, 2018-01-09 at 02:01 +0000, Bakshi, Arjun wrote: > I get this error when trying to open 2 tx steams and 3 rx streams, > where some usrps are both rx and tx: "RuntimeError: fifo ctrl timed > out looking for acks" > > I found a mention of the error on this page: http://www.ni.com/produc > t-documentation/53455/en/ > > Which gives a workaround: Open an Rx and Tx session to the same list > of devices. You can disable the unused channel in the session where > you added it. > > How do I interpret this in GRC? > > My specific setup is that I want to: > --- TX using usrps with IP1 and IP2 > --- RX using usrps with IP1, IP3, and IP4 > > How do I go about doing this? How do I fill out the device args > fields and make the connections? > > Thanks, > > AB > _______________________________________________ > Discuss-gnuradio mailing list > Discuss-gnuradio@gnu.org > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio Discuss-gnuradio Info Page - lists.gnu.org<https://lists.gnu.org/mailman/listinfo/discuss-gnuradio> lists.gnu.org To see the collection of prior postings to the list, visit the Discuss-gnuradio Archives. Using Discuss-gnuradio: To post a message to all the list ...