Hi Armin, What happens if you set the number of channels to 4 (with the skip_dram arg removed), and drive the two unused TX channels with a const source 0?
Jonathon On Fri, Jul 9, 2021 at 11:56 AM Marcus D. Leech <[email protected]> wrote: > On 07/09/2021 11:54 AM, Armin Ghani wrote: > > 5Msps > > If there's a way to up it to 10Msps (keeping the same bandwidth), that > might help with the "L"--which basically means the > pipeline is starving for samples. Now, it might also mean that your > computer cannot "keep up" and is delivering samples > a little late. > > > On 9/7/21 17:50, Marcus D. Leech wrote: > > On 07/09/2021 10:31 AM, Armin Ghani wrote: > > Thanks Marcus. > > It helped to resolve the error. But UHD consistently prints "L" in the > output. > > Would you what DRAM FIFO block actually does? > > It's a FIFO between the DUC and the ADC as far as I know. > > What is your sample rate? > > > Regards > On 9/7/21 14:41, Marcus D. Leech wrote: > > On 07/09/2021 07:40 AM, Armin Ghani wrote: > > Dear community > > I've been trying to make a fully synchronous multi USRP transmitter in > GNURadio v3.8.2.0 and UHD v3.15.0.0. > > In order to have a common clock and time between 2 USRPs, an octoclock is > also used. > > when trying to run a flowgraph which consists one multi_usrp sink block > that is connected to a signal source in GNURadio and running the flowgrapth > I get this error: > > Executing: /usr/bin/python3 -u > /home/.../Documents/gnuradio-tests/octoclock_test.py > > [INFO] [UHD] linux; GNU C++ version 9.3.0; Boost_107100; > UHD_3.15.0.HEAD-0-gaea0e2de > [INFO] [X300] X300 initialization sequence... > [INFO] [X300] Maximum frame size: 7972 bytes. > [WARNING] [X300] For the 192.168.30.2 connection, UHD recommends a receive > frame size of at least 8000 for best > performance, but your configuration will only allow 7972.This may > negatively impact your maximum achievable sample rate. > Check the MTU on the interface and/or the recv_frame_size argument. > [INFO] [X300] Maximum frame size: 7972 bytes. > [WARNING] [X300] For the 192.168.50.2 connection, UHD recommends a receive > frame size of at least 8000 for best > performance, but your configuration will only allow 7972.This may > negatively impact your maximum achievable sample rate. > Check the MTU on the interface and/or the recv_frame_size argument. > [INFO] [X300] Radio 1x clock: 200 MHz > [INFO] [0/DmaFIFO_0] Initializing block control (NOC ID: > 0xF1F0D00000000000) > [INFO] [X300] Radio 1x clock: 200 MHz > [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1308 MB/s) > [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1312 MB/s) > [INFO] [1/DmaFIFO_0] Initializing block control (NOC ID: > 0xF1F0D00000000000) > [INFO] [1/DmaFIFO_0] BIST passed (Throughput: 1316 MB/s) > [INFO] [1/DmaFIFO_0] BIST passed (Throughput: 1304 MB/s) > [INFO] [0/Radio_0] Initializing block control (NOC ID: 0x12AD100000000001) > [INFO] [1/Radio_0] Initializing block control (NOC ID: 0x12AD100000000001) > [INFO] [0/Radio_1] Initializing block control (NOC ID: 0x12AD100000000001) > [INFO] [1/Radio_1] Initializing block control (NOC ID: 0x12AD100000000001) > [INFO] [0/DDC_0] Initializing block control (NOC ID: 0xDDC0000000000000) > [INFO] [1/DDC_0] Initializing block control (NOC ID: 0xDDC0000000000000) > [INFO] [0/DDC_1] Initializing block control (NOC ID: 0xDDC0000000000000) > [INFO] [1/DDC_1] Initializing block control (NOC ID: 0xDDC0000000000000) > [INFO] [0/DUC_0] Initializing block control (NOC ID: 0xD0C0000000000000) > [INFO] [1/DUC_0] Initializing block control (NOC ID: 0xD0C0000000000000) > [INFO] [0/DUC_1] Initializing block control (NOC ID: 0xD0C0000000000000) > [INFO] [1/DUC_1] Initializing block control (NOC ID: 0xD0C0000000000000) > [INFO] [MULTI_USRP] 1) catch time transition at pps edge > [INFO] [MULTI_USRP] 2) set times next pps (synchronously) > thread[thread-per-block[6]: <block usrp_sink(1)>]: RuntimeError: Multiple > sampling rates downstream of TX Terminator 0: RuntimeError: Node 0/DUC_0 > specifies 1e+06, node 0/DUC_1 specifies 390625. > > What happens if you use the "skip_dram=1" argument in the device argument? > > > > _______________________________________________ > USRP-users mailing list -- [email protected] > To unsubscribe send an email to [email protected] > > -- > > Armin Ghani > > Research Engineer | Communication Systems Division (CSD) > > [email protected] | +34 93 645 29 08 (2143) > > Centre Tecnològic de Telecomunicacions de Catalunya (CTTC) > > Av. Carl Friedrich Gauss, 7 - Edifici B4 - PMT > > 08860 - Castelldefels (Barcelona, Spain) > > www.cttc.cat > > > _______________________________________________ > USRP-users mailing list -- [email protected] > To unsubscribe send an email to [email protected] > > > > _______________________________________________ > USRP-users mailing list -- [email protected] > To unsubscribe send an email to [email protected] > > -- > > Armin Ghani > > Research Engineer | Communication Systems Division (CSD) > > [email protected] | +34 93 645 29 08 (2143) > > Centre Tecnològic de Telecomunicacions de Catalunya (CTTC) > > Av. Carl Friedrich Gauss, 7 - Edifici B4 - PMT > > 08860 - Castelldefels (Barcelona, Spain) > > www.cttc.cat > > > _______________________________________________ > USRP-users mailing list -- [email protected] > To unsubscribe send an email to [email protected] > > > _______________________________________________ > USRP-users mailing list -- [email protected] > To unsubscribe send an email to [email protected] >
_______________________________________________ USRP-users mailing list -- [email protected] To unsubscribe send an email to [email protected]
