Hello Cedric,
Thank you for the comments and observations.
I'd like to know if you managed to obtain information about the calibration
process?
___
USRP-users mailing list -- usrp-users@lists.ettus.com
To unsubscribe send an email to usrp-users-le...@l
The IP address of 192.168.10.2 and the MTU size of 1472 indicate that your
link is a 1Gb link. The max rate this can support is 25MS/s. You will need
to connect at 10Gbe if you want to run at 100MS/s.
Rob
On Wed, Mar 6, 2024 at 2:31 PM White, Joshua J <
jjwh...@riversideresearch.org> wrote:
> The
The underflows you're getting mean your host PC isn't providing samples fast
enough for the rate the radio is consuming them and it's underrunning the TX
buffer. Likely there isn't enough bandwidth between the host PC and the
radio to support 100 Msps. There is a pretty good discussion of bandwidth
On 06/03/2024 13:56, ygurupra...@umass.edu wrote:
Could some help me if this is working as expected?
./bin/txrx_loopback_to_file --tx-args addr=192.168.10.2 --rx-args
addr=192.168.10.2 --tx-rate 100e6 --rx-rate 6.5e6 --tx-freq 20e6
--rx-freq 18e6
Creating the transmit usrp device with: add
Could some help me if this is working as expected?
\
./bin/txrx_loopback_to_file --tx-args addr=192.168.10.2 --rx-args
addr=192.168.10.2 --tx-rate 100e6 --rx-rate 6.5e6 --tx-freq 20e6 --rx-freq 18e6
Creating the transmit usrp device with: addr=192.168.10.2...
\[INFO\] \[UHD\] linux; GNU C++ ver
Hi Dario,
The _d version is optimized for use with DRAM and the non-_d version is
optimized for streaming to a connected host computer over 100 GbE. On the
non-DRAM versions, the wider CHDR width gets applied to the stream
endpoints, which connect to the host computer via 100 GbE. In testing we've
