usrp-users@lists.ettus.com
Discussion and technical support related to USRP, UHD, RFNoC
View all threadsRX Channel out of range
Hello,
I am writing this code from terminal:
benchmark_rate --rx_rate 10e6 --tx_rate 10e6
and the output is:
*[INFO] [UHD] Win32; Microsoft Visual C++ version 14.1; Boost_107000; UHD_4.2.0.0-release
[00:00:00.000100] Creating the usrp device with: ...
[INFO] [B200] Detected Device: B200
[INFO] [B200] Operating over USB 3.
[INFO] [B200] Initialize CODEC control...
[INFO] [B200] Initialize Radio control...
[INFO] [B200] Performing register loopback test...
[INFO] [B200] Register loopback test passed
[INFO] [B200] Setting master clock rate selection to 'automatic'.
[INFO] [B200] Asking for clock rate 16.000000 MHz...
[INFO] [B200] Actually got clock rate 16.000000 MHz.
Using Device: Single USRP:
Device: B-Series Device
Mboard 0: B200
RX Channel: 0
RX DSP: 0
RX Dboard: A
RX Subdev: FE-RX1
TX Channel: 0
TX DSP: 0
TX Dboard: A
TX Subdev: FE-TX1
Error: LookupError: IndexError: multi_usrp: RX channel 2106923663889 out of range for configured RX frontends*
I tried to enter channels manual but outcomes is same
Hello,
I'm guessing here, but: /
/
/RX channel 2106923663889/
is not the worst indication that your benchmark_rate calls a UHD function with a different
function signature than it thinks it has.
This would only happen if you have competing installations of UHD on your machine: one
from which your benchmark_rate.exe is, and a different one supplying the library that that
program uses.
Can you make sure that's not the case? How did you install UHD?
Best regards,
Marcus
On 03.01.23 15:29, henry.powell.xx@gmail.com wrote:
Hello,
I am writing this code from terminal:
/benchmark_rate --rx_rate 10e6 --tx_rate 10e6/ and the output is: /[INFO] [UHD] Win32;
Microsoft Visual C++ version 14.1; Boost_107000; UHD_4.2.0.0-release [00:00:00.000100]
Creating the usrp device with: ... [INFO] [B200] Detected Device: B200 [INFO] [B200]
Operating over USB 3. [INFO] [B200] Initialize CODEC control... [INFO] [B200] Initialize
Radio control... [INFO] [B200] Performing register loopback test... [INFO] [B200]
Register loopback test passed [INFO] [B200] Setting master clock rate selection to
'automatic'. [INFO] [B200] Asking for clock rate 16.000000 MHz... [INFO] [B200] Actually
got clock rate 16.000000 MHz. Using Device: Single USRP: Device: B-Series Device Mboard
0: B200 RX Channel: 0 RX DSP: 0 RX Dboard: A RX Subdev: FE-RX1 TX Channel: 0 TX DSP: 0
TX Dboard: A TX Subdev: FE-TX1 Error: LookupError: IndexError: multi_usrp: RX channel
2106923663889 out of range for configured RX frontends/
I tried to enter channels manual but outcomes is same
USRP-users mailing list --usrp-users@lists.ettus.com
To unsubscribe send an email tousrp-users-leave@lists.ettus.com
I installed via Anaconda and the code which i run benchmark is anaconda prompt actually. So, my uhd environment is in anaconda.
Hi,
Happy New Year!
I am using X310. Our application prints some log information. Meanwhile, UHD also prints log information. Currently, all the logs are streamed to a file. Saving log to file involves access to HD which is a low-speed device. I want to save all logs into RAM first; then only at spare time or after testing, the logs will be saved to file. I think this will improve the speed and reliability of our application.
My questions are:- how to save UHD logs into a buffer which is allocated in my code? - how to maintain the time order between UHD logs and the logs generated by my code?
Thanks,Hongwei
Hi again :)
I just confirmed that at least as far as the maintainer of the UHD and GNU Radio anaconda
packaging is concerned, the anaconda builds are 64 bit, but yours seems to be 32 bit, so
this very likely is a competing installation!
Best regards,
Marcus
On 03.01.23 16:14, henry.powell.xx@gmail.com wrote:
I installed via Anaconda and the code which i run benchmark is anaconda prompt actually.
So, my uhd environment is in anaconda.
USRP-users mailing list -- usrp-users@lists.ettus.com
To unsubscribe send an email to usrp-users-leave@lists.ettus.com
On 03/01/2023 10:24, zhou via USRP-users wrote:
Hi,
Happy New Year!
I am using X310. Our application prints some log information.
Meanwhile, UHD also prints log information. Currently, all the logs
are streamed to a file. Saving log to file involves access to HD which
is a low-speed device. I want to save all logs into RAM first; then
only at spare time or after testing, the logs will be saved to file. I
think this will improve the speed and reliability of our application.
My questions are:
- how to save UHD logs into a buffer which is allocated in my code?
- how to maintain the time order between UHD logs and the logs
generated by my code?
Thanks,
Hongwei
Have you looked at:
Hello, again.
My system is 64bit and I made uhd installation again without anaconda complying with “Building and Installing UHD from source” from here: https://files.ettus.com/manual/page_build_guide.html
So, when i try uhd_find_devices, it works no problem.
But when try “benchmark_rate --tx_rate=6e6 --rx_rate=6e6”, gave me this error: Error: LookupError: IndexError: multi_usrp: RX channel 1768203151377 out of range for configured RX frontends.
The problem is same.
Hi,
can you share the outputs of
which sh
which benchmark_rate
which uhd_find_devices
with us? Could you also try to search for any "libuhd.dll" on your system, and verify that
only there's only the one that you expect to be there?
The person actually in charge of maintaining the UHD package for anaconda was pretty
certain that the build of the UHD library used when you run benchmark_rate is not the
one from the anaconda repo; so, the problem persists that for some reason, a wrong UHD
library being loaded instead of the one that your build or anaconda's build.
Best regards,
Marcus
DISCLAIMER: Any attached Code is provided As Is. It has not been tested or validated as a product, for use in a deployed application or system, or for use in hazardous environments. You assume all risks for use of the Code. Use of the Code is subject to terms of the licenses to the UHD or RFNoC code with which the Code is used. Standard licenses to UHD and RFNoC can be found at https://www.ettus.com/sdr-software/licenses/.
NI will only perform services based on its understanding and condition that the goods or services (i) are not for the use in the production or development of any item produced, purchased, or ordered by any entity with a footnote 1 designation in the license requirement column of Supplement No. 4 to Part 744, U.S. Export Administration Regulations and (ii) such a company is not a party to the transaction. If our understanding is incorrect, please notify us immediately because a specific authorization may be required from the U.S. Commerce Department before the transaction may proceed further.
On 09.01.23 08:19, henry.powell.xx@gmail.com wrote:
Hello, again.
My system is 64bit and I made uhd installation again without anaconda complying with
“Building and Installing UHD from source” from here:
https://files.ettus.com/manual/page_build_guide.html
So, when i try uhd_find_devices, it works no problem.
But when try “benchmark_rate --tx_rate=6e6 --rx_rate=6e6”, gave me this error: Error:
LookupError: IndexError: multi_usrp: RX channel 1768203151377 out of range for
configured RX frontends.
The problem is same.
USRP-users mailing list -- usrp-users@lists.ettus.com
To unsubscribe send an email to usrp-users-leave@lists.ettus.com
Hi,
On 1/9/23 7:31 AM, Marcus Müller wrote:
Hi,
can you share the outputs of
which sh
which benchmark_rate
which uhd_find_devices
with us? Could you also try to search for any "libuhd.dll" on your
system, and verify that only there's only the one that you expect to be
there?
The person actually in charge of maintaining the UHD package for
anaconda was pretty certain that the build of the UHD library used when
you run benchmark_rate is not the one from the anaconda repo; so, the
problem persists that for some reason, a wrong UHD library being loaded
instead of the one that your build or anaconda's build.
I just fired up my VM and checked my radioconda environment with UHD
4.3, and it does actually identify itself with the line
[INFO] [UHD] Win32; Microsoft Visual C++ version 14.2; Boost_107800;
UHD_4.3.0.0-release
including the "Win32". So I take it back: it is reasonable to conclude
that this is not a case of mixed installations.
That's as far as I can take it, unfortunately, since running
benchmark_rate with my B200mini works as expected.
Cheers,
Ryan
Best regards,
Marcus
DISCLAIMER: Any attached Code is provided As Is. It has not been tested
or validated as a product, for use in a deployed application or system,
or for use in hazardous environments. You assume all risks for use of
the Code. Use of the Code is subject to terms of the licenses to the UHD
or RFNoC code with which the Code is used. Standard licenses to UHD and
RFNoC can be found at https://www.ettus.com/sdr-software/licenses/.
NI will only perform services based on its understanding and condition
that the goods or services (i) are not for the use in the production or
development of any item produced, purchased, or ordered by any entity
with a footnote 1 designation in the license requirement column of
Supplement No. 4 to Part 744, U.S. Export Administration Regulations and
(ii) such a company is not a party to the transaction. If our
understanding is incorrect, please notify us immediately because a
specific authorization may be required from the U.S. Commerce Department
before the transaction may proceed further.
On 09.01.23 08:19, henry.powell.xx@gmail.com wrote:
Hello, again.
My system is 64bit and I made uhd installation again without anaconda
complying with “Building and Installing UHD from source” from here:
https://files.ettus.com/manual/page_build_guide.htmlSo, when i try uhd_find_devices, it works no problem.
But when try “benchmark_rate --tx_rate=6e6 --rx_rate=6e6”, gave me
this error: Error: LookupError: IndexError: multi_usrp: RX channel
1768203151377 out of range for configured RX frontends.The problem is same.
USRP-users mailing list -- usrp-users@lists.ettus.com
To unsubscribe send an email to usrp-users-leave@lists.ettus.com
USRP-users mailing list -- usrp-users@lists.ettus.com
To unsubscribe send an email to usrp-users-leave@lists.ettus.com