So when i I try to set the master clock rate to 100 MHz directly I get an
error and when I don't set it I get a warning.
Can I just disregard the warning or is there something else going on here?
$ uhd_rx_cfile -r 10e6 -f 850e6 -g 10 -a
'args=192.168.40.2,master_clock_rate=100e6'
tmp.dat
[INFO] [UHD] linux; GNU C++ version 4.8.5 20150623 (Red Hat 4.8.5-36);
Boost_105300; UHD_3.12.0.heads-v3.12.0.0-0-gec786351
Traceback (most recent call last):
File "/test/bin/bin/uhd_rx_cfile", line 263, in <module>
tb = rx_cfile_block(options, filename)
File "/test/bin/bin/uhd_rx_cfile", line 77, in __init__
channels=self.channels,
File "/test/bin/lib64/python2.7/site-packages/gnuradio/uhd/__init__.py",
line 122, in constructor_interceptor
return old_constructor(*args)
File "/test/bin/lib64/python2.7/site-packages/gnuradio/uhd/uhd_swig.py",
line 2334, in make
return _uhd_swig.usrp_source_make(*args)
RuntimeError: RuntimeError: Invalid master clock rate: 100.00 MHz.
Valid master clock rates when using a 10.000000 MHz reference clock are:
120 MHz, 184.32 MHz and 200 MHz.
$ uhd_rx_cfile -r 10e6 -f 850e6 -g 10 -a 'args=192.168.40.2'
tmp.dat
[INFO] [UHD] linux; GNU C++ version 4.8.5 20150623 (Red Hat 4.8.5-36);
Boost_105300; UHD_3.12.0.heads-v3.12.0.0-0-gec786351
[WARNING] [X300] Cannot update master clock rate! X300 Series does not
allow changing the clock rate during runtime.
[WARNING] [X300 RADIO] Requesting invalid sampling rate from device: 200
MHz. Actual rate is: 100 MHz.
[WARNING] [X300 RADIO] Requesting invalid sampling rate from device: 200
MHz. Actual rate is: 100 MHz.
^C
On Tue, May 14, 2019 at 3:08 PM Marcus D. Leech via USRP-users <
usrp-users@lists.ettus.com> wrote:
> On 05/14/2019 11:26 AM, Devin Kelly via USRP-users wrote:
>
> Does anyone have any ideas on this? Is uhd_rx_cfile not the right tool to
> be using?
>
> Devin
>
> The TwinRX *MUST* run with a master clock of effectively 100MHz, because
> of the way the ADCs are shared, and the DDC structure in the
> FPGA. Further, the fixed analog filtering is designed for a 100MHz
> clock frequency, and the synthesizers on the board require a 100MHz
> clock (AFAIR).
>
> Simply don't specify the master clock rate when using uhd_rx_cfile, and
> the correct default *should* happen.
>
>
>
>
> On Thu, May 9, 2019 at 10:39 AM Devin Kelly <dwwke...@gmail.com> wrote:
>
>>
>> Sorry to revive an old post but I'm having the same problem with UHD
>> 3.12.0.0. Am I doing something wrong with uhd_rx_cfile or should I just
>> upgrade to a newer UHD?
>>
>> $ uhd_rx_cfile -r 10e6 -f 850e6 -a
>> 'args=192.168.40.2,master_clock_rate=200e6' tmp.dat
>> [INFO] [UHD] linux; GNU C++ version 4.8.5 20150623 (Red Hat 4.8.5-36);
>> Boost_105300; UHD_3.12.0.heads-v3.12.0.0-0-gec786351
>> [WARNING] [X300] Cannot update master clock rate! X300 Series does not
>> allow changing the clock rate during runtime.
>> [WARNING] [X300 RADIO] Requesting invalid sampling rate from device: 200
>> MHz. Actual rate is: 100 MHz.
>> [WARNING] [X300 RADIO] Requesting invalid sampling rate from device: 200
>> MHz. Actual rate is: 100 MHz.
>> [UHD_RX] Defaulting to mid-point gains:
>> [UHD_RX] Channel 0 gain: 49.5 dB
>> ^C
>>
>> Thanks,
>> Devin
>>
>> On Thu, Jan 17, 2019 at 12:48 PM Rigney, Kevin E via USRP-users <
>> usrp-users@lists.ettus.com> wrote:
>>
>>> I’m working with the TwinRX and am having the same results as Emanuel. I
>>> was ignoring the warning about the sample rate but you said that it must
>>> run at 200MHz. Can you explain why UHD sets the sample rate to 100MHz if
>>> 200 is required?
>>>
>>> Thanks,
>>>
>>> -Kevin
>>>
>>> On Mon, 14 Jan 2019 at 7:06 AM Emanuel via USRP-users <
>>> usrp-users@lists.ettus.com<mailto:usrp-users@lists.ettus.com>> wrote:
>>>
>>> Dear Martin,
>>>
>>> thank you for clarification. Yes, please add this to the manual. We
>>> bought those TwinRX for some phase-coherent LTE signal reception, and now
>>> they seem to be not useful at all (without effort spent in sample rate
>>> conversion in post-processing etc.)
>>>
>>> I'm still wondering about the master clock rate though: I tried the
>>> benchmark with the following settings: ./benchmark_rate --args
>>> "master_clock_rate=200e6" --rx_subdev A:0 --rx_rate 10e6
>>> The TwinRX is mounted on slot A and a CBX-120 is mounted on slot B. I
>>> simply wanted a streaming test on the first TwinRX channel.
>>> During device initialization I get the following warnings, see below.
>>> Can you please comment on them?
>>>
>>> [INFO] [0/DUC_1] Initializing block control (NOC ID: 0xD0C0000000000000)
>>> [WARNING] [X300] Cannot update master clock rate! X300 Series does not
>>> allow changing the clock rate during runtime.
>>> [WARNING] [X300 RADIO] Requesting invalid sampling rate from device: 200
>>> MHz. Actual rate is: 100 MHz.
>>> Using Device: Single USRP:
>>> Device: X-Series Device
>>> Mboard 0: X310
>>> RX Channel: 0
>>> RX DSP: 0
>>> RX Dboard: A
>>> RX Subdev: TwinRX RX0
>>> TX Channel: 0
>>> TX DSP: 0
>>> TX Dboard: A
>>> TX Subdev: Unknown (0x0094) - 0
>>> TX Channel: 1
>>> TX DSP: 0
>>> TX Dboard: B
>>> TX Subdev: CBX-120 TX
>>>
>>> [00:00:05.874991] Setting device timestamp to 0...
>>> .....
>>>
>>> Cheers,
>>> Emanuel
>>>
>>> _______________________________________________
>>> USRP-users mailing list
>>> USRP-users@lists.ettus.com
>>> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
>>>
>>
>
> _______________________________________________
> USRP-users mailing
> listUSRP-users@lists.ettus.comhttp://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
>
>
> _______________________________________________
> USRP-users mailing list
> USRP-users@lists.ettus.com
> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
>
_______________________________________________
USRP-users mailing list
USRP-users@lists.ettus.com
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
