OK, so this means the 1/f noise is not from the LO. Otherwise it would finally
appear around the LO offset frequency.
The noise arises in the baseband AFTER the mixing and therefore is not affected
by the DSP magic.
I think, I understand now.
Erik
Von: Nick
Please help, with the error I am seeing.
I am currently using an X310 with a UBX160 daughtercard and I get the error
below when changing the frequency parameters of the radio.
RuntimeError: EnvironmentError: IOError: Radio ctrl (A) packet parse error -
AssertionError: packet_info.packet_count =
Hello Mark:
This may indicate a hardware problem. What is specifically eliciting the
error? Does it occur with every time that there is a tune request? Are
you running your own program, or one the example programs, such as
"rx_samples_to_file"? Could you please try upgrading to UHD 3.14.0.0, a
On 06/06/2019 01:46 PM, Mark Koenig via USRP-users wrote:
Please help, with the error I am seeing.
I am currently using an X310 with a UBX160 daughtercard and I get the
error below when changing the frequency parameters of the radio.
RuntimeError: EnvironmentError: IOError: Radio ctrl (A) pa
I've seen chatter on this around here before (an I think I might have been
involved with it during my failed N310 project a while back), but I haven't
come up with a solution yet.
I have a custom RFNoC bitfile I want to use on the E320. I set things up and
built it with the mods in rfnoc_ce_a
Hi Neel,
Yes, I am using my own program and yes it occurs during a tune request, but not
every time. For example, I could be doing a collection and scanning
frequencies every 10 seconds, but not see the error once in a 2-hour
collection. Once the error is seen, then communication is lost and
I figured it out. The problem was that in noc_block_split_stream.v, rb_stb was
set to 1'b1 in the noc_shell instantiation.
I changed it to ".rb_stb({NUM_OUTPUTS{1'b1}})" and it seems to have build OK.
From: USRP-users on behalf of Jason
Matusiak via USRP-us
