seems it's ok: $ uhd_usrp_probe [INFO] [UHD] linux; GNU C++ version 11.3.0; Boost_107400; UHD_4.3.0.0-14-g1e718d9b [INFO] [USRP2] Opening a USRP2/N-Series device... [INFO] [USRP2] Current recv frame size: 1472 bytes [INFO] [USRP2] Current send frame size: 1472 bytes _____________________________________________________ / | Device: USRP2 / N-Series Device | _____________________________________________________ | / | | Mboard: N200r4 | | hardware: 2576 | | mac-addr: 00:80:2f:0a:ce:45 | | ip-addr: 192.168.20.2 | | subnet: 255.255.255.255 | | gateway: 255.255.255.255 | | gpsdo: none | | serial: F1700B | | name: ali_01 | | FW Version: 12.4 | | FPGA Version: 11.1 | | | | Time sources: none, external, _external_, mimo | | Clock sources: internal, external, mimo | | Sensors: mimo_locked, ref_locked | | _____________________________________________________ | | / | | | RX DSP: 0 | | | | | | Freq range: -50.000 to 50.000 MHz | | _____________________________________________________ | | / | | | RX DSP: 1 | | | | | | Freq range: -50.000 to 50.000 MHz | | _____________________________________________________ | | / | | | RX Dboard: A | | | ID: WBX v3, WBX v3 + Simple GDB (0x0057) | | | Serial: EDR29PFXW | | | _____________________________________________________ | | | / | | | | RX Frontend: 0 | | | | Name: WBXv3 RX+GDB | | | | Antennas: TX/RX, RX2, CAL | | | | Sensors: lo_locked | | | | Freq range: 68.750 to 2200.000 MHz | | | | Gain range PGA0: 0.0 to 31.5 step 0.5 dB | | | | Bandwidth range: 40000000.0 to 40000000.0 step 0.0 Hz | | | | Connection Type: IQ | | | | Uses LO offset: No | | | _____________________________________________________ | | | / | | | | RX Codec: A | | | | Name: ads62p44 | | | | Gain range digital: 0.0 to 6.0 step 0.5 dB | | | | Gain range fine: 0.0 to 0.5 step 0.1 dB | | _____________________________________________________ | | / | | | TX DSP: 0 | | | | | | Freq range: -200.000 to 200.000 MHz | | _____________________________________________________ | | / | | | TX Dboard: A | | | ID: WBX v3 (0x0056) | | | Serial: EDR29PFXW | | | ID: WBX + Simple GDB, WBX v3 + Simple GDB, WBX v4 + Simple GDB, WBX-120 + Simple GDB (0x004f) | | | Serial: EDR29PFGS | | | _____________________________________________________ | | | / | | | | TX Frontend: 0 | | | | Name: WBXv3 TX+GDB | | | | Antennas: TX/RX, CAL | | | | Sensors: lo_locked | | | | Freq range: 68.750 to 2200.000 MHz | | | | Gain range PGA0: 0.0 to 31.0 step 1.0 dB | | | | Bandwidth range: 40000000.0 to 40000000.0 step 0.0 Hz | | | | Connection Type: IQ | | | | Uses LO offset: No | | | _____________________________________________________ | | | / | | | | TX Codec: A | | | | Name: ad9777 | | | | Gain Elements: None
On Thu, Dec 29, 2022 at 8:17 AM Marcus D. Leech <patchvonbr...@gmail.com> wrote: > On 28/12/2022 23:35, Ali G. Dezfuli wrote: > > thanks Marcus, > I have checked benchmark_rate with no lost packets even at the highest > rate of 25 Ms/s. > It is connected via ethernet 1G. > > Isn't it because of outdated firmware and fpga? > > If the FPGA code is out-of-date, UHD will complain. > > What does > > uhd_usrp_probe have to say about it. > > > > > the output of benchmark_rate: > > $ ./benchmark_rate --rx_rate 25e6 > > [INFO] [UHD] linux; GNU C++ version 11.3.0; Boost_107400; > UHD_4.3.0.0-14-g1e718d9b > [00:00:00.000444] Creating the usrp device with: ... > [INFO] [USRP2] Opening a USRP2/N-Series device... > [INFO] [USRP2] Current recv frame size: 1472 bytes > [INFO] [USRP2] Current send frame size: 1472 bytes > Using Device: Single USRP: > Device: USRP2 / N-Series Device > Mboard 0: N200r4 > RX Channel: 0 > RX DSP: 0 > RX Dboard: A > RX Subdev: WBXv3 RX+GDB > TX Channel: 0 > TX DSP: 0 > TX Dboard: A > TX Subdev: WBXv3 TX+GDB > > [00:00:01.466484658] Setting device timestamp to 0... > [00:00:01.467214590] Testing receive rate 25.000000 Msps on 1 channels > [00:00:11.467783232] Benchmark complete. > > > Benchmark rate summary: > Num received samples: 249982026 > Num dropped samples: 0 > Num overruns detected: 0 > Num transmitted samples: 0 > Num sequence errors (Tx): 0 > Num sequence errors (Rx): 0 > Num underruns detected: 0 > Num late commands: 0 > Num timeouts (Tx): 0 > Num timeouts (Rx): 0 > > > Done! > > On Thu, Dec 29, 2022 at 8:04 AM Ali G. Dezfuli <ali69...@gmail.com> wrote: > >> thanks Marcus, >> I have checked benchmark_rate with no lost packets even at the highest >> rate of 25 Ms/s. >> It is connected via ethernet 1G. >> >> Isn't it because of outdated firmware and fpga? >> >> >> the output of benchmark_rate: >> >> $ ./benchmark_rate --rx_rate 25e6 >> >> [INFO] [UHD] linux; GNU C++ version 11.3.0; Boost_107400; >> UHD_4.3.0.0-14-g1e718d9b >> [00:00:00.000444] Creating the usrp device with: ... >> [INFO] [USRP2] Opening a USRP2/N-Series device... >> [INFO] [USRP2] Current recv frame size: 1472 bytes >> [INFO] [USRP2] Current send frame size: 1472 bytes >> Using Device: Single USRP: >> Device: USRP2 / N-Series Device >> Mboard 0: N200r4 >> RX Channel: 0 >> RX DSP: 0 >> RX Dboard: A >> RX Subdev: WBXv3 RX+GDB >> TX Channel: 0 >> TX DSP: 0 >> TX Dboard: A >> TX Subdev: WBXv3 TX+GDB >> >> [00:00:01.466484658] Setting device timestamp to 0... >> [00:00:01.467214590] Testing receive rate 25.000000 Msps on 1 channels >> [00:00:11.467783232] Benchmark complete. >> >> >> Benchmark rate summary: >> Num received samples: 249982026 >> Num dropped samples: 0 >> Num overruns detected: 0 >> Num transmitted samples: 0 >> Num sequence errors (Tx): 0 >> Num sequence errors (Rx): 0 >> Num underruns detected: 0 >> Num late commands: 0 >> Num timeouts (Tx): 0 >> Num timeouts (Rx): 0 >> >> >> Done! >> >> On Wed, Dec 28, 2022 at 7:00 PM Marcus D. Leech <patchvonbr...@gmail.com> >> wrote: >> >>> On 28/12/2022 04:55, Ali G. Dezfuli wrote: >>> > Hi all, >>> > I have gnuradio on this system: >>> > ubuntu 22.04 >>> > uhd 4.3.0.0-14-g1e718d9b >>> > gnuradio v3.11.0.0git-316-gc11667ef >>> > >>> > I have a USRP N200 from 2011 but have not worked with it for the last >>> > couple of years. >>> > After a long while, I just run $ uhd_cal_tx_dc_offset but got the >>> > following error: >>> > >>> > Creating the usrp device with: ,ignore_cal_file=1,ignore-cal-file=1... >>> > [INFO] [UHD] linux; GNU C++ version 11.3.0; Boost_107400; >>> > UHD_4.3.0.0-14-g1e718d9b >>> > [INFO] [USRP2] Opening a USRP2/N-Series device... >>> > [INFO] [USRP2] Current recv frame size: 1472 bytes >>> > [INFO] [USRP2] Current send frame size: 1472 bytes >>> > Running calibration for WBXv3 TX+GDB >>> > Daughterboard serial: EDR29PFXW >>> > Calibration frequency range: 68.75 MHz -> 2200 MHz >>> > >>> SSUSUSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS[WARNING] >>> >>> > TX error detected! Repeating current iteration >>> > >>> SSSSSSSSSSSSSSUSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS[WARNING] >>> >>> > TX error detected! Repeating current iteration >>> > >>> SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS[WARNING] >>> >>> > TX error detected! Repeating current iteration >>> > SSSSSSSSSSSSSSSSSSS[WARNING] TX error detected! Repeating current >>> > iteration >>> > [WARNING] TX error detected! Repeating current iteration >>> > [WARNING] TX error detected! Repeating current iteration >>> > [WARNING] TX error detected! Repeating current iteration >>> > [WARNING] TX error detected! Repeating current iteration >>> > [WARNING] TX error detected! Repeating current iteration >>> > [WARNING] TX error detected! Repeating current iteration >>> > terminate called without an active exception >>> > Aborted (core dumped) >>> > >>> > I would be grateful if somebody helps me with this error. >>> > regards >>> > AGD >>> The occurrence of 'S' signifies a sequence-number error, the underlying >>> cause of which is usually the network stack. >>> >>> If you use the "benchmark_rate" example at modest sample-rates, does >>> this still occur? >>> >>> >>> How are you connected to the USRP? What type of network interface do >>> you have? Are you running on the native hardware, >>> or in a VM? Have you tried replacing the network cable? >>> >>> >>> >>> >
