[USRP-users] What do I need to do to make uhd_usrp_probe see my custom RFNOC module?
Hi, I've created a custom RFNOC module with two blocks, and have it installed. The module.yml files are in /usr/share/uhd/rfnoc/blocks, I have a library for it installed in /usr/lib (and VHDL files as well somewhere). When I run uhd_usrp_probe I see the following: [INFO] [UHD] linux; GNU C++ version 10.2.1 20210110; Boost_107400; DPDK_20.11; UHD_4.3.0.0-2molex1 [INFO] [X300] X300 initialization sequence... [INFO] [X300] Maximum frame size: 8000 bytes. [INFO] [X300] Radio 1x clock: 200 MHz [WARNING] [RFNOC::BLOCK_FACTORY] Could not find block with Noc-ID 0xdeadbeef, 0x [INFO] [0/Block#0] Setting default MTU forward policy. [WARNING] [RFNOC::BLOCK_FACTORY] Could not find block with Noc-ID 0xdeadaffe, 0x [INFO] [0/Block#1] Setting default MTU forward policy. _ / | Device: X-Series Device | _ |/ | | Mboard: X300 | | revision: 11 | | revision_compat: 7 | | product: 30817 | | mac-addr0: 00:80:2f:34:fa:ba | | mac-addr1: 00:80:2f:34:fa:bb | | gateway: 192.168.10.1 | | ip-addr0: 192.168.10.2 | | subnet0: 255.255.255.0 | | ip-addr1: 192.168.20.2 | | subnet1: 255.255.255.0 | | ip-addr2: 192.168.30.2 | | subnet2: 255.255.255.0 | | ip-addr3: 192.168.50.2 | | subnet3: 255.255.255.0 | | serial: 3252D36 | | FW Version: 6.0 | | FPGA Version: 39.0 | | FPGA git hash: 1e718d9-dirty | | RFNoC capable: Yes | | | | Time sources: internal, external, gpsdo | | Clock sources: internal, external, gpsdo | | Sensors: ref_locked | _ |/ | | RFNoC blocks on this device: | | | | * 0/Block#0 | | * 0/Block#1 | | * 0/Radio#0 | | * 0/Radio#1 | | * 0/Replay#0 | _ |/ | | Static connections on this device: | | | | * 0/SEP#0:0==>0/Block#0:0 | | * 0/Block#0:0==>0/SEP#0:0 | | * 0/SEP#1:0==>0/Block#1:0 | | * 0/Block#1:0==>0/SEP#1:0 | _ |/ | | TX Dboard: 0/Radio#0 | | ID: UBX-160 v2 (0x007d) | | Serial: 324BFA8 | | Revision: 5 | | _ | |/ | | | TX Frontend: 0 | | | Name: UBX TX | | | Antennas: TX/RX, CAL | | | Sensors: lo_locked | | | Freq range: 10.000 to 6000.000 MHz | | | Gain range PGA0: 0.0 to 31.5 step 0.5 dB | | | Bandwidth range: 16000.0 to 16000.0 step 0.0 Hz | | | Connection Type: QI | | | Uses LO offset: No | _ |/ | | RX Dboard: 0/Radio#0 | | ID: UBX-160 v2 (0x007e) | | Serial: 324BFA8 | | Revision: 5 | | _ | |/ | | | RX Frontend: 0 | | | Name: UBX RX | | | Antennas: TX/RX, RX2, CAL | | | Sensors: lo_locked | | | Freq range: 10.000 to 6000.000 MHz | | | Gain range PGA0: 0.0 to 31.5 step 0.5 dB | | | Bandwidth range: 16000.0 to 16000.0 step 0.0 Hz | | | Connection Type: IQ | | | Uses LO offset: No | _ |/ | | TX Dboard: 0/Radio#1 | | ID: UBX-160 v2 (0x007d) | | Serial: 324BFA6 | | Revision: 5 | | _ | |/ | | | TX Frontend: 0 | | | Name: UBX TX | | | Antennas: TX/RX, CAL | | | Sensors: lo_locked | | | Freq range: 10.000 to 6000.000 MHz | | | Gain range PGA0: 0.0 to 31.5 step 0.5 dB | | | Bandwidth range: 16000.0 to 16000.0 step 0.0 Hz | | | Connection Type: QI | | | Uses LO offset: No | _ |/ | | RX Dboard: 0/Radio#1 | | ID: UBX-160 v2 (0x007e) | | Serial: 324BFA6 | | Revision: 5 | | _ | |/ | | | RX Frontend: 0 | | | Name: UBX RX | | | Antennas: TX/RX, RX2, CAL | | | Sensors: lo_locked | | | Freq range: 10.000 to 6000.000 MHz | | | Gain range PGA0: 0.0 to 31.5 step 0.5 dB | | | Bandwidth range: 16000.0 to 16000.0 step 0.0 Hz | | | Connection Type: IQ | | | Uses LO offset: No How can I make libuhd correctly identify my custom RFNOC modules? Regards, Bas Vermeulen CONFIDENTIALITY NOTICE: This message (including any attachments) may contain Molex confidential information, protected by law. If this message is confidential, forwarding it to individuals, other than those with a need to know, without the permission of the sender, is prohibited. This message is also intended for a
[USRP-users] Re: What do I need to do to make uhd_usrp_probe see my custom RFNOC module?
Just to answer my own question: Run uhd_usrp_probe with LD_PRELOAD=/usr/lib/librfnoc-module.so uhd_usrp_probe and it will be able to find the RFNOC modules. The same for any test programs you use, those need the LD_PRELOAD as well. Regards, Bas Vermeulen From: Vermeulen, Bas (Consultant) via USRP-users Sent: Wednesday, March 1, 2023 11:04 AM To: usrp-users@lists.ettus.com Subject: [USRP-users] What do I need to do to make uhd_usrp_probe see my custom RFNOC module? Sent by an external sender Hi, I've created a custom RFNOC module with two blocks, and have it installed. The module.yml files are in /usr/share/uhd/rfnoc/blocks, I have a library for it installed in /usr/lib (and VHDL files as well somewhere). When I run uhd_usrp_probe I see the following: [INFO] [UHD] linux; GNU C++ version 10.2.1 20210110; Boost_107400; DPDK_20.11; UHD_4.3.0.0-2molex1 [INFO] [X300] X300 initialization sequence... [INFO] [X300] Maximum frame size: 8000 bytes. [INFO] [X300] Radio 1x clock: 200 MHz [WARNING] [RFNOC::BLOCK_FACTORY] Could not find block with Noc-ID 0xdeadbeef, 0x [INFO] [0/Block#0] Setting default MTU forward policy. [WARNING] [RFNOC::BLOCK_FACTORY] Could not find block with Noc-ID 0xdeadaffe, 0x [INFO] [0/Block#1] Setting default MTU forward policy. _ / | Device: X-Series Device | _ |/ | | Mboard: X300 | | revision: 11 | | revision_compat: 7 | | product: 30817 | | mac-addr0: 00:80:2f:34:fa:ba | | mac-addr1: 00:80:2f:34:fa:bb | | gateway: 192.168.10.1 | | ip-addr0: 192.168.10.2 | | subnet0: 255.255.255.0 | | ip-addr1: 192.168.20.2 | | subnet1: 255.255.255.0 | | ip-addr2: 192.168.30.2 | | subnet2: 255.255.255.0 | | ip-addr3: 192.168.50.2 | | subnet3: 255.255.255.0 | | serial: 3252D36 | | FW Version: 6.0 | | FPGA Version: 39.0 | | FPGA git hash: 1e718d9-dirty | | RFNoC capable: Yes | | | | Time sources: internal, external, gpsdo | | Clock sources: internal, external, gpsdo | | Sensors: ref_locked | _ |/ | | RFNoC blocks on this device: | | | | * 0/Block#0 | | * 0/Block#1 | | * 0/Radio#0 | | * 0/Radio#1 | | * 0/Replay#0 | _ |/ | | Static connections on this device: | | | | * 0/SEP#0:0==>0/Block#0:0 | | * 0/Block#0:0==>0/SEP#0:0 | | * 0/SEP#1:0==>0/Block#1:0 | | * 0/Block#1:0==>0/SEP#1:0 | _ |/ | | TX Dboard: 0/Radio#0 | | ID: UBX-160 v2 (0x007d) | | Serial: 324BFA8 | | Revision: 5 | | _ | |/ | | | TX Frontend: 0 | | | Name: UBX TX | | | Antennas: TX/RX, CAL | | | Sensors: lo_locked | | | Freq range: 10.000 to 6000.000 MHz | | | Gain range PGA0: 0.0 to 31.5 step 0.5 dB | | | Bandwidth range: 16000.0 to 16000.0 step 0.0 Hz | | | Connection Type: QI | | | Uses LO offset: No | _ |/ | | RX Dboard: 0/Radio#0 | | ID: UBX-160 v2 (0x007e) | | Serial: 324BFA8 | | Revision: 5 | | _ | |/ | | | RX Frontend: 0 | | | Name: UBX RX | | | Antennas: TX/RX, RX2, CAL | | | Sensors: lo_locked | | | Freq range: 10.000 to 6000.000 MHz | | | Gain range PGA0: 0.0 to 31.5 step 0.5 dB | | | Bandwidth range: 16000.0 to 16000.0 step 0.0 Hz | | | Connection Type: IQ | | | Uses LO offset: No | _ |/ | | TX Dboard: 0/Radio#1 | | ID: UBX-160 v2 (0x007d) | | Serial: 324BFA6 | | Revision: 5 | | _ | |/ | | | TX Frontend: 0 | | | Name: UBX TX | | | Antennas: TX/RX, CAL | | | Sensors: lo_locked | | | Freq range: 10.000 to 6000.000 MHz | | | Gain range PGA0: 0.0 to 31.5 step 0.5 dB | | | Bandwidth range: 16000.0 to 16000.0 step 0.0 Hz | | | Connection Type: QI | | | Uses LO offset: No | _ |/ | | RX Dboard: 0/Radio#1 | | ID: UBX-160 v2 (0x007e) | | Serial: 324BFA6 | | Revision: 5 | | _ | |/ | | | RX Frontend: 0 | | | Name: UBX RX | | | Antennas: TX/RX, RX2, CAL | | | Sensors: lo_locked | | | Freq range: 10.000 to 6000.000 MHz | | | Gain range PGA0: 0.0 to 31.5 step 0.5 dB | | | B
[USRP-users] Re: What do I need to do to make uhd_usrp_probe see my custom RFNOC module?
On Wed, Mar 1, 2023 at 5:40 AM Vermeulen, Bas (Consultant) via USRP-users < usrp-users@lists.ettus.com> wrote: > Just to answer my own question: > > Run uhd_usrp_probe with LD_PRELOAD=/usr/lib/librfnoc-module.so > uhd_usrp_probe and it will be able to find the RFNOC modules. > The same for any test programs you use, those need the LD_PRELOAD as well. > While this is a way to do it, I believe the preferred method is using the UHD_MODULE_PATH environment variable. Set that to a location which contains all the .so files for any RFNoC modules, and UHD will load them automatically. Note that if any non-.so files are in that path, you will get a warning about not being able to load the library. Brian ___ USRP-users mailing list -- usrp-users@lists.ettus.com To unsubscribe send an email to usrp-users-le...@lists.ettus.com
[USRP-users] Re: What do I need to do to make uhd_usrp_probe see my custom RFNOC module?
On Wed, 1 Mar 2023 07:20:22 -0500 Brian Padalino wrote: > On Wed, Mar 1, 2023 at 5:40 AM Vermeulen, Bas (Consultant) via USRP-users < > usrp-users@lists.ettus.com> wrote: > > > Just to answer my own question: > > > > Run uhd_usrp_probe with LD_PRELOAD=/usr/lib/librfnoc-module.so > > uhd_usrp_probe and it will be able to find the RFNOC modules. > > The same for any test programs you use, those need the LD_PRELOAD as well. > > > > While this is a way to do it, I believe the preferred method is using the > UHD_MODULE_PATH environment variable. > > Set that to a location which contains all the .so files for any RFNoC > modules, and UHD will load them automatically. Note that if any non-.so > files are in that path, you will get a warning about not being able to load > the library. > > Brian /usr/lib is a default path for libraries. Maybe using (as root) ldconfig to rebuild/refresh the cache used by the runtime linker? Gwenhael ___ USRP-users mailing list -- usrp-users@lists.ettus.com To unsubscribe send an email to usrp-users-le...@lists.ettus.com
[USRP-users] Re: What do I need to do to make uhd_usrp_probe see my custom RFNOC module?
On Wed, Mar 1, 2023 at 8:59 AM Gwenhael Goavec-Merou wrote: > On Wed, 1 Mar 2023 07:20:22 -0500 > Brian Padalino wrote: > > > On Wed, Mar 1, 2023 at 5:40 AM Vermeulen, Bas (Consultant) via > USRP-users < > > usrp-users@lists.ettus.com> wrote: > > > > > Just to answer my own question: > > > > > > Run uhd_usrp_probe with LD_PRELOAD=/usr/lib/librfnoc-module.so > > > uhd_usrp_probe and it will be able to find the RFNOC modules. > > > The same for any test programs you use, those need the LD_PRELOAD as > well. > > > > > > > While this is a way to do it, I believe the preferred method is using the > > UHD_MODULE_PATH environment variable. > > > > Set that to a location which contains all the .so files for any RFNoC > > modules, and UHD will load them automatically. Note that if any non-.so > > files are in that path, you will get a warning about not being able to > load > > the library. > > > > Brian > > /usr/lib is a default path for libraries. > Maybe using (as root) ldconfig to rebuild/refresh the cache used by the > runtime > linker? > No - this doesn't make sense. Use UHD_MODULE_PATH. You can put your modules in ~/mymodules and point your UHD_MODULE_PATH to ~/mymodules and things will work fine. There is no need to play with LD_PRELOAD or worry about being root or install to default library paths. Use UHD_MODULE_PATH. Brian ___ USRP-users mailing list -- usrp-users@lists.ettus.com To unsubscribe send an email to usrp-users-le...@lists.ettus.com
[USRP-users] Re: Wrong Measurement Results
I don’t understand how this happen. Everythings are same, I just change USRP. First, I tried with USRP B200 and the difference between 0 and 180 degree is 3dB. Then I plug Pico VNA, the difference is zero. Then I plug Nano VNA (It’s 50 dollar VNA cheap.) the difference is zero. I plug my other USRP, It’s B210. The difference is 0,7dB. Anything changed except USRP. After of all this I plug USRP B200 again and the difference is 3dB. When I change the frequency, at some frequencies there is no difference between 0 and 180 degree. I share with you the data. When horn antenna at 0 degree ant rotate 180 degree. # 0 degree: Max. Value at 4001.0 MHz : -32.394 Max. Value at 4002.0 MHz : -32.343 Max. Value at 4003.0 MHz : -32.380 Max. Value at 4004.0 MHz : -32.431 Max. Value at 4005.0 MHz : -32.556 Max. Value at 4006.0 MHz : -32.748 Max. Value at 4007.0 MHz : -32.919 Max. Value at 4008.0 MHz : -33.141 Max. Value at 4009.0 MHz : -33.366 Max. Value at 4010.0 MHz : -33.616 Max. Value at 4011.0 MHz : -33.833 Max. Value at 4012.0 MHz : -34.073 Max. Value at 4013.0 MHz : -34.391 Max. Value at 4014.0 MHz : -34.710 Max. Value at 4015.0 MHz : -35.132 Max. Value at 4016.0 MHz : -35.553 Max. Value at 4017.0 MHz : -35.973 Max. Value at 4018.0 MHz : -36.414 Max. Value at 4019.0 MHz : -36.725 Max. Value at 4020.0 MHz : -36.965 Max. Value at 4021.0 MHz : -37.061 Max. Value at 4022.0 MHz : -37.166 Max. Value at 4023.0 MHz : -37.155 Max. Value at 4024.0 MHz : -37.079 Max. Value at 4025.0 MHz : -36.987 Max. Value at 4026.0 MHz : -36.823 Max. Value at 4027.0 MHz : -36.588 Max. Value at 4028.0 MHz : -36.339 Max. Value at 4029.0 MHz : -36.005 Max. Value at 4030.0 MHz : -35.645 Max. Value at 4031.0 MHz : -35.196 Max. Value at 4032.0 MHz : -34.754 Max. Value at 4033.0 MHz : -34.316 Max. Value at 4034.0 MHz : -33.915 Max. Value at 4035.0 MHz : -33.479 Max. Value at 4036.0 MHz : -33.093 Max. Value at 4037.0 MHz : -32.696 Max. Value at 4038.0 MHz : -32.409 Max. Value at 4039.0 MHz : -32.167 Max. Value at 4040.0 MHz : -31.977 Max. Value at 4041.0 MHz : -31.854 Max. Value at 4042.0 MHz : -31.822 Max. Value at 4043.0 MHz : -31.835 Max. Value at 4044.0 MHz : -31.904 Max. Value at 4045.0 MHz : -32.012 Max. Value at 4046.0 MHz : -32.152 Max. Value at 4047.0 MHz : -32.291 Max. Value at 4048.0 MHz : -32.431 Max. Value at 4049.0 MHz : -32.584 Max. Value at 4050.0 MHz : -32.802 # 180 degree: Max. Value at 4001.0 MHz : -35.370 Max. Value at 4002.0 MHz : -35.371 Max. Value at 4003.0 MHz : -35.313 Max. Value at 4004.0 MHz : -35.241 Max. Value at 4005.0 MHz : -35.188 Max. Value at 4006.0 MHz : -35.077 Max. Value at 4007.0 MHz : -34.964 Max. Value at 4008.0 MHz : -34.802 Max. Value at 4009.0 MHz : -34.577 Max. Value at 4010.0 MHz : -34.347 Max. Value at 4011.0 MHz : -34.106 Max. Value at 4012.0 MHz : -33.773 Max. Value at 4013.0 MHz : -33.499 Max. Value at 4014.0 MHz : -33.289 Max. Value at 4015.0 MHz : -33.163 Max. Value at 4016.0 MHz : -33.038 Max. Value at 4017.0 MHz : -32.974 Max. Value at 4018.0 MHz : -32.941 Max. Value at 4019.0 MHz : -32.970 Max. Value at 4020.0 MHz : -32.913 Max. Value at 4021.0 MHz : -32.829 Max. Value at 4022.0 MHz : -32.795 Max. Value at 4023.0 MHz : -32.805 Max. Value at 4024.0 MHz : -32.885 Max. Value at 4025.0 MHz : -32.939 Max. Value at 4026.0 MHz : -33.064 Max. Value at 4027.0 MHz : -33.199 Max. Value at 4028.0 MHz : -33.337 Max. Value at 4029.0 MHz : -33.483 Max. Value at 4030.0 MHz : -33.656 Max. Value at 4031.0 MHz : -33.830 Max. Value at 4032.0 MHz : -33.992 Max. Value at 4033.0 MHz : -34.175 Max. Value at 4034.0 MHz : -34.362 Max. Value at 4035.0 MHz : -34.555 Max. Value at 4036.0 MHz : -34.726 Max. Value at 4037.0 MHz : -34.893 Max. Value at 4038.0 MHz : -35.080 Max. Value at 4039.0 MHz : -35.218 Max. Value at 4040.0 MHz : -35.424 Max. Value at 4041.0 MHz : -35.564 Max. Value at 4042.0 MHz : -35.700 Max. Value at 4043.0 MHz : -35.749 Max. Value at 4044.0 MHz : -35.735 Max. Value at 4045.0 MHz : -35.665 Max. Value at 4046.0 MHz : -35.505 Max. Value at 4047.0 MHz : -35.261 Max. Value at 4048.0 MHz : -34.974 Max. Value at 4049.0 MHz : -34.658 Max. Value at 4050.0 MHz : -34.302___ USRP-users mailing list -- usrp-users@lists.ettus.com To unsubscribe send an email to usrp-users-le...@lists.ettus.com
[USRP-users] Re: Wrong Measurement Results
On 01/03/2023 09:30, henry.powell...@gmail.com wrote: I don’t understand how this happen. Everythings are same, I just change USRP. First, I tried with USRP B200 and the difference between 0 and 180 degree is 3dB. Then I plug Pico VNA, the difference is zero. Then I plug Nano VNA (It’s 50 dollar VNA cheap.) the difference is zero. I plug my other USRP, It’s B210. The difference is 0,7dB. Anything changed except USRP. After of all this I plug USRP B200 again and the difference is 3dB. When I change the frequency, at some frequencies there is no difference between 0 and 180 degree. I share with you the data. When horn antenna at 0 degree ant rotate 180 degree. ___ USRP-users mailing list -- usrp-users@lists.ettus.com To unsubscribe send an email to usrp-users-le...@lists.ettus.com How far apart are the horns? What are you TX and RX gain settings? Do you have a laboratory signal generator you can use to verify linearity of the receivers? Can you share the code you're using to take these measurements? ___ USRP-users mailing list -- usrp-users@lists.ettus.com To unsubscribe send an email to usrp-users-le...@lists.ettus.com
[USRP-users] Instantaneous bandwidth on Ettus N321
Hello, I am currently looking to see what the highest possible sampling rate is for the ettus N321/N320. I see that the highest master clock rate is 250e6 Mhz, However, on the product website(https://www.ettus.com/all-products/usrp-n321/), it says that it can collect up to an instantaneous bandwidth of 200 Mhz, so I am led to assume that the maximum possible sampling rate is 400 Mhz. Is this true? If so, how do I configure my the ettus to collect at a rate of 400 Mhz without the rate being coerced back down to 250 Mhz. Thanks, Joe ___ USRP-users mailing list -- usrp-users@lists.ettus.com To unsubscribe send an email to usrp-users-le...@lists.ettus.com
[USRP-users] Re: Instantaneous bandwidth on Ettus N321
Joe, Complex sampling does not require the sample rate to be 2x the highest frequency as is the case for real sampling. It only needs to be 1x. So, the 250MS/s sampling rate produces 250MHz of spectrum. But, there are anti-aliasing filters that reduce this to a usable bandwidth of 200Mhz. Rob On Wed, Mar 1, 2023 at 12:52 PM wrote: > Hello, > > > I am currently looking to see what the highest possible sampling rate is > for the ettus N321/N320. I see that the highest master clock rate is 250e6 > Mhz, However, on the product website( > https://www.ettus.com/all-products/usrp-n321/), it says that it can > collect up to an instantaneous bandwidth of 200 Mhz, so I am led to assume > that the maximum possible sampling rate is 400 Mhz. Is this true? If so, > how do I configure my the ettus to collect at a rate of 400 Mhz without the > rate being coerced back down to 250 Mhz. > > > Thanks, > > Joe > ___ > USRP-users mailing list -- usrp-users@lists.ettus.com > To unsubscribe send an email to usrp-users-le...@lists.ettus.com > ___ USRP-users mailing list -- usrp-users@lists.ettus.com To unsubscribe send an email to usrp-users-le...@lists.ettus.com
