-
Notifications
You must be signed in to change notification settings - Fork 644
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[ERROR] [RNOC: :GRAPH Caught exception while initializing graph: RfocError: Op Timeout: Control operation timed out waiting for ACK #669
Comments
The error means that the host sent a packet to the USRP for some operation (e.g., a register read or write) but the host didn't get a response from the FPGA. This could happen if packets are getting lost, for example. Could be a bad cable, or something unreliable about the network connection. How often is "sometimes"? Is it only when you run uhd_usrp_probe that this occurs? Which interface are you using (HG, XG)? What's the IP address configuration and network topology? Ideally, the USRP is directly connected to your host PC using SFP0, and your PC has a static IP of 192.168.10.1. You could then try specifying the address of the USRP port when running probe, in case something funny is going on with network discovery:
|
You can probably ignore the timeout during flush, it's not usually a problem. From the picture, it looks like you have a 1 GbE port connected in SFP0, so that would have to be the HG image. This is the default. Double check your command. It looks like you didn't type the args correctly. Try:
Normally you would configure your Ethernet port to use a static IP of 192.168.10.1 with a net mask of 255.255.255.0. This is compatible with the USRPs default IP address of 192.168.10.2. The two ethernet devices (host and USRP) need to be on the same subnet to talk to each other properly. |
Hi, thanks for your information. My bad, I made the typos. My static IP addresses for the laptops are 192.168.10.218 and 192.168.10.209 separately. It works well by using Do you have any idea about the four warnings in the first pictures? Thanks for your help! |
That's a known issue also. You can ignore it. |
Thank you very much. Regarding to the problem [ERROR] [RNOC: :GRAPH Caught exception while initializing graph: RfocError: OpTimeout: Control operation timed out waiting for ACK. Do you have any idea how to fix it? Since I may meet the same problem when I run srsRAN software suit. |
You can post on the mailing list for ideas. It sounds like something is wrong with your network configuration. You have two different laptops, one with .218 and the other with .209? And you're directly connecting each to a USRP with the default IP address of 192.168.10.1? No switch or anything in between? Is your network mask for each Ethernet adapter set to 255.255.255.0 (i.e., your subnet is 192.168.10.*)? The details matter. But if that's all correct, then it should work. You could try a different cable and double check any firewall settings (maybe disable the firewall as a sanity check). Make sure you always provide the IP address for the USRP you want to talk to in the args. Make sure you have the right USRP connected to the right Ethernet port on the right laptop. If you mix them up, some things might work, but some things might not). |
Thanks for your information. Will post it on mailing list. I checked all things you mentioned and they should be all correctly configured. I will try to use some different cables. Thank you again for your time! |
When i try to run the gNB with usrp x310, it shows the following error : sleep... if someone know the answer. |
Closing due to lack of information. |
Issue Description
When I run
uhd_usrp_probe
, sometimes it shows the following error:[ERROR] [RNOC: :GRAPH Caught exception while initializing graph: RfocError: Op Timeout: Control operation timed out waiting for ACK.
Error: RuntimeError: Failure to create rfnoc graph.
Setup Details
UHD/FPGA Version: UHD_4.1.0.6-120-971ff96a
OS: Ubuntu 20.04
C++ Version: 9.4.0
Hardware: X310
Expected Behavior
Actual Behaviour
Steps to reproduce the problem
Additional Information
The text was updated successfully, but these errors were encountered: