Re: [Discuss-gnuradio] Tx and Rx on USRP simultaneously, device already claimed

2019-10-11 Thread Martin Braun
Yeah, or UHD can't match the two UHD sessions. There is no downside to it -- you just need to make sure that the TX subdev spec is set correctly, and if you only want to TX on one channel, you need to pick the correct channel index. On Fri, Oct 11, 2019 at 3:30 PM Mark Wagner wrote: > Ahh, are

Re: [Discuss-gnuradio] Clock rate change on x300

2019-10-11 Thread Martin Braun
A bit late here, but the X300 can now (at least on master) also do all the other clock rates in between 184.32 and 200 Msps. On Tue, Aug 6, 2019 at 11:56 AM Derek Kozel wrote: > Hi Paul, > > What rate do you want to adjust it to and for what purpose? The X300 > supports a master clock rate of

Re: [Discuss-gnuradio] ImportError: cannot import name usrp

2019-10-11 Thread Nate Temple
Can you post the code in question? On Fri, Oct 11, 2019 at 1:32 PM Laura Arjona wrote: > Thank you Nate. > > Yes, that is the configuration I had before. But I using someone else's > code for a different USRP, and getting errors with the usrp_sink_c to set > the fusb block size > > On Fri, Oct

Re: [Discuss-gnuradio] ImportError: cannot import name usrp

2019-10-11 Thread Laura Arjona
Thank you Nate. Yes, that is the configuration I had before. But I using someone else's code for a different USRP, and getting errors with the usrp_sink_c to set the fusb block size On Fri, Oct 11, 2019 at 1:28 PM Nate Temple wrote: > You should pass in the cpu_format as an arg such as below:

Re: [Discuss-gnuradio] ImportError: cannot import name usrp

2019-10-11 Thread Nate Temple
You should pass in the cpu_format as an arg such as below: sink = uhd.usrp_sink( ",".join(("", "")), uhd.stream_args( cpu_format="fc32", channels=range(1), ), ) On Fri, Oct 11, 2019 at 1:16 PM Laura Arjona wrote: > Got it, thank you! > > However,

Re: [Discuss-gnuradio] ImportError: cannot import name usrp

2019-10-11 Thread Laura Arjona
Got it, thank you! However, usrp_sink_c is not supported anymore? Get an error there too. tx = usrp_sink_c(fusb_block_size = 1024, fusb_nblocks=8) On Fri, Oct 11, 2019 at 1:11 PM Nate Temple wrote: > Hi Laura, > > It should be: > > from gnuradio import uhd > > source = uhd.usrp_source(...) >

Re: [Discuss-gnuradio] ImportError: cannot import name usrp

2019-10-11 Thread Laura Arjona
Sorry for not being clear, I actually have that from gnuradio import usrp ImportError: cannot import name usrp On Fri, Oct 11, 2019 at 1:08 PM Michael Dickens wrote: > Hi Laura - Try: "from gnuradio import uhd" ... not "import usrp" ... - MLD > > On Fri, Oct 11, 2019 at 4:05 PM Laura Arjona

Re: [Discuss-gnuradio] ImportError: cannot import name usrp

2019-10-11 Thread Nate Temple
Hi Laura, It should be: from gnuradio import uhd source = uhd.usrp_source(...) ... I would suggest to try building out a basic flowgraph in GRC and then use the generate button and checkout the source made from it. Regards, Nate Temple On Fri, Oct 11, 2019 at 1:06 PM Laura Arjona wrote:

Re: [Discuss-gnuradio] ImportError: cannot import name usrp

2019-10-11 Thread Michael Dickens
Hi Laura - Try: "from gnuradio import uhd" ... not "import usrp" ... - MLD On Fri, Oct 11, 2019 at 4:05 PM Laura Arjona wrote: > Hello, > > I am using a usrp b200-mini, and I am trying to define the sink as follows: > *tx = usrp_sink_c(fusb_block_size = 1024, fusb_nblocks=8)* > > However, I get

[Discuss-gnuradio] ImportError: cannot import name usrp

2019-10-11 Thread Laura Arjona
Hello, I am using a usrp b200-mini, and I am trying to define the sink as follows: *tx = usrp_sink_c(fusb_block_size = 1024, fusb_nblocks=8)* However, I get the error * from gnuradio import usrpImportError: cannot import name usrp* I believe my GNU-radio installation is correct. Any clue of

Re: [Discuss-gnuradio] windows 10 need help with 3/7.13.4

2019-10-11 Thread CEL
Looks like you've installed 3.7.13.5 without uninstalling the previous version, and now each block is found twice? Anyway, that has nothing to do with the RTL-SDR not working. My guess is you're using a gr-osmosdr built for 3.7.13.4. That is likely to not work. Best regards, Marcus On Fri,