LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

What's meaning of this error (with USRP 2943 or 53), Thank you!

Dear friends, 

 

In my project, I am using just one USRP RIO 2943 (or 2953). I randomly get this error, but I have no idea the meaning of it. Could you someone teach me the meaning and how to solve it in details?  Thank you !!!  

 

Error -1074118627 occurred at niUSRP Configure Signal.vi

Possible reason(s):
A runtime or configuration error occurred.
Code: 312
Details: EnvironmentError: IOError: 0/Radio_0 user_reg_read64() failed: EnvironmentError: IOError: [0/Radio_0] sr_read64() failed: EnvironmentError: IOError: Block ctrl (CE_01_Port_40) no response packet - AssertionError: bool(buff)
in unsigned __int64 __cdecl ctrl_iface_impl::wait_for_ack(const bool)
at P:/Measurements/FlexRIO/SWCode/usrp/niuhd2/trunk/17.0/objects/uhdrepo/host/lib/rfnoc/ctrl_iface.cpp:205

0 Kudos
Message 1 of 6
(3,425 Views)

Hi sunson,

 

The error text mentions having "no response packet" and I saw a couple other instances of this sort of behavior coming up when talking to a USRP RIO over Ethernet, is that how you're communicating in your application? Do you have a MXIe interface you could test instead, by chance? Alternatively, do you have a different computer (with a different Ethernet chipset, so a different manufacturer ideally) that you could test? Looks like this can be caused by issues with some Ethernet chipset manufacturers.

 

If you aren't using Ethernet, then this is obviously something else. Have you implemented your own FPGA on this module, or is it running the default image? When you say in happens "randomly," is there any pattern at all? Different lengths of running the application, different IQ rates, measuring noise vs. actual signal; anything that narrows it down would be helpful.

 

Regards,

 

Cason

NI Applications Engr.

Cassandra Longley
Senior Technical Support Engineer - FlexRIO, High Speed Serial and VRTS
0 Kudos
Message 2 of 6
(3,374 Views)

wow! Cason, Thanks so much for your reply. 

Let me answer your question one by one,lol

1. You are right, I am using: usb to ethernet adapter, then a switch to collect the usrp.  

2. I do have MXI, but I have to use the switch (connected by ethernet adapter), because this project will be used by a laptop eventually.

3.Hmm. I only have one PC now. 

4. FPGA? I never use it. The vi is on PC, use PC to control usrp.

5. It is totally random, this means the project vi can run perfect without any error, but few chances, I do get this error.  

6, for receiver, I am using QPSK, IQ sampling: 40M, carrier f:2.6G, gain 10dB. 

 

Thank you!

0 Kudos
Message 3 of 6
(3,362 Views)

a quick update, i tired using MIXe, it seems that the error is gone. But I have to use the Ethernet cable eventually.  Could you give me some idea how to reduce the error?  

0 Kudos
Message 4 of 6
(3,353 Views)

Hey sunson,

 

That makes sense, and what you’ve said pretty much proves that the issue is the networking. The USRP needs a pretty uninterrupted connection to continuously stream back and forth. In this case, there’s really nothing that can be changed other than the network chain. If at all possible, removing pieces of the chain would be helpful: you have both a USB to Ethernet adapter and a switch in the middle. I’m sure if you could you would have already done so, but it’s worth another hard look.

 

Reducing other network traffic, if any, might help. It sounds like this is happening at Configure Signal rather than in the middle of data acquisition; that being the case, you could look at implementing some error handling to retry connecting to the USRP in the case of this error. But ultimately, it just comes down to the relative unreliability of the network connection.

 

Cason

NI Applications Engr.

Cassandra Longley
Senior Technical Support Engineer - FlexRIO, High Speed Serial and VRTS
0 Kudos
Message 5 of 6
(3,346 Views)

Thank you. 

I made something in vi, if the error happens, it will keep the previous result, and restart it from the previous result.  Thank you again for your detail answer. 

0 Kudos
Message 6 of 6
(3,341 Views)