Hello,
What are the specifications of your host computer (processor, RAM, SSD or
hard drive, etc)? What type of USB controller are you using?
-Trip
On Thu, Jun 30, 2016 at 6:48 PM, Przemek Lewandowski
wrote:
> Hello
>
> I need to generate as wide bandwith as possible. Yes I know that this is
>
Hi Shahnaz,
Could you run the install step again but with the verbose flag (-v)?
$ pybombs [-p myprefix] install gnuradio gr-osmosdr -v
It might produce more helpful debugging information. Can you post the
relevant output here when it hits the error?
-Trip
On Wed, Apr 20, 2016 at 9:12 PM, Shah
Hi Jason,
I replied to the other thread as well, but could you also do this to see if
its the same error?
Could you run the install step again but with the verbose flag (-v)?
$ pybombs [-p myprefix] install gnuradio gr-osmosdr -v
It might produce more helpful debugging information. Can you post
Hi Henry,
There is a script, read_complex_binary.m, that is included with gnuradio.
You can use that with Octave or Matlab to read the I/Q recordings from a
file as a time vector.
-Trip
On Sat, Mar 19, 2016 at 12:43 PM, Henry Barton wrote:
> Is there any simple formula for plotting spectrum (f
Hi Dennis,
Have you seen these:
https://gnuradio.org/doc/doxygen/page_python_blocks.html
and
http://gnuradio.org/redmine/projects/gnuradio/wiki/Guided_Tutorial_GNU_Radio_in_Python
They have some good info on how to setup your Python block.
-Trip
On Wed, Mar 16, 2016 at 4:51 PM, Dennis Glatti
Hi Varun,
PyBOMBS2 is now just PyBOMBS:
https://github.com/gnuradio/pybombs/issues
pybombs1 is now listed at pybombs_legacy.
-Trip
On Mon, Mar 7, 2016 at 2:03 PM, Varun Kumar wrote:
> Hi,
> I've been using GNURadio for past 1 year, and I decided to look into
> PyBOMS2 issues for GSoC'16, but
overwritten? Or do I need to delete something
> before doing so?
>
> Thanks,
> Zhihong
>
> On Wed, Feb 10, 2016 at 7:43 PM, James Humphries <
> james.humphr...@ettus.com> wrote:
>
>> Hi Zhihong,
>>
>> 4ae7a6015ba719a4720f61cc6f3857de2ebda89f is the commit
Hi Zhihong,
4ae7a6015ba719a4720f61cc6f3857de2ebda89f is the commit hash that refers to
a specific commit on the GNU Radio repository.
If you built GNU Radio recently (I believe this commit was last August),
then you should be OK.
-Trip
On Wed, Feb 10, 2016 at 6:42 PM, Zhihong Luo wrote:
> Hi
What was the whole command that you used to identify the USRP by serial
number? It should look like:
uhd_usrp_probe --args="serial=xx"
You shouldn't need it if you are using only a single USRP though.
You still get the same error in GRC when you add the type to device
arguments? Can you doub
Hello,
Do you have multiple USRP's hooked up? If so, try only having one plugged
in for this initial test.
You can provide a device hint in the arguments of the UHD source block. Try:
"type=b200"
As another test, make sure you can use the built in utilities of UHD to
detect your USRP.
uhd_usrp
Hi Daniel,
The output power of the USRP is controlled by the TX gain setting. Keep in
mind that the output power of the USRP is not calibrated and will vary from
device to device. Some may have higher output power than others.
Isolation between the transmit and receive sections of the USRP is a p
Hi Ekko,
The sample rate has to be some fraction of the clock rate divided by an
integer. The clock rate on the E310 defaults to 32MHz I believe, so 32MHz
divided by 4 gives you 8 Msps. The system will get you as close as it can
to the desired sample rate. You can set the clock rate to something e
Hi Kerry,
Did you hook your computer back up to the internet before you ran
uhd_images_downloader.py?
-Trip
On Mon, Nov 30, 2015 at 3:22 PM, kerry wrote:
> Hi,all:
>
> I try to run an example about gnu radio. The runtime errors are captured
> as:
>
> Using Volk machine: sse4_1_64_orc
> gr-osmo
smitter with a real only signal s(t)=cos(w0*t), why
> does the received signal has an imaginary component (i.e. Q(t) is not zero)?
>
> Thanks again,
> Roee
>
>
> On 16 Nov 2015, at 14:34, James Humphries
> wrote:
>
> Hi Roee,
>
> The USRP is not expecting any
ver performs some low pass filtering which
> removes the lower-side-band or something similar.
>
> Can anyone confirm that the USRP expects single-side-band signals so I can
> put this issue to rest?
>
> Thanks in advance,
> Roee
>
>
>
>
>
> On 13 Nov 2015, at 19:40, Ja
ash
>
> On Fri, Nov 6, 2015 at 10:57 AM, James Humphries <
> james.humphr...@ettus.com> wrote:
>
>> Hi Ash,
>>
>> Yes, you need to use an attenuator if you are connecting the B200's
>> directly together with a cable. I would recommend at least 30dB of
>
Hi Ash,
Yes, you need to use an attenuator if you are connecting the B200's
directly together with a cable. I would recommend at least 30dB of
attenuation, but that depends on your settings. It is recommended that you
do not input more that -15 dBm into the receiver of the B200, as this can
damage
Hi Julio,
You need to instruct the USRP which reference to use. See this page in the
UHD manual:
http://files.ettus.com/manual/page_sync.html
Are you using a GNU Radio flowgraph? Or are you writing code directly using
the GNU Radio python API or UHD C++ API?
-Trip
On Mon, Oct 19, 2015 at 1:12
eran the script and now things are
> "different"
> >
> > This seems like it may take a while. I'll report back when it's done.
> >
> > Hmm.. so far one error - it couldn't find libzmq1-dev; I don't know
> > what that'll mean
>
Hi Mike,
Did you update your package manager? Usually helps when I get errors.
sudo apt-get update && sudo apt-get upgrade
Also, make sure build-essential is installed (Do this after update and
upgrade).
sudo apt-get install build-essential
-Trip
On Mon, Sep 21, 2015 at 11:13 PM, Mike Gilmer
Hi Daniele / Marcus,
I'll add my experience as well. I have been testing installs of Ubuntu
15.04 in a VMware virtual machine. I limit it to 2GB of RAM. I was using
pybombs to install UHD + GNURadio. Install would halt at a certain point
(no error) every time. Solution was to limit make to 2 threa
21 matches
Mail list logo
