I am not sure if I understand the problem. The first shot shows a
spectrum centred around 2.4766GHz, but the second has an display of
2.399 to 2.401 GHz - since these ranges (from my point of view) don't
overlap, I am not sure how this relates to not being able to see a
signal in one versus
On 18/09/17 21:27, Marcus D. Leech wrote:
On 09/18/2017 05:21 PM, John Shields wrote:
On 18/09/17 20:52, Marcus D. Leech wrote:
On 09/18/2017 03:49 PM, John Shields wrote:
Thanks,
I have attached the GRC. I should note that before I
run, I wait until GPS is locked as evinced
On 18/09/17 20:52, Marcus D. Leech wrote:
On 09/18/2017 03:49 PM, John Shields wrote:
Thanks,
I have attached the GRC. I should note that before I run,
I wait until GPS is locked as evinced by the query_gpsdo_sensor utility:
GPS Locked
Trying to align
:
On 09/18/2017 12:41 AM, John Shields wrote:
Thanks, as always, Marcus,
Here is the relevant code
I am executing:
self.uhd_usrp_source_0.set_clock_source('gpsdo', 0)
self.uhd_usrp_source_0.set_time_source('gpsdo', 0
.
Kind Regards,
John
On 18/09/17 03:20, Marcus D. Leech wrote:
On 09/15/2017 05:38 PM, John Shields wrote:
Hi,
One has O/B GPSDO, the other connected by MIMO cable on Ubuntu
with UHD_003.010.002.000
From the /manual/page_sync.html page there is information on how
Hi,
One has O/B GPSDO, the other connected by MIMO cable on Ubuntu
with UHD_003.010.002.000
From the /manual/page_sync.html page there is information on how to
align the CORDICs and LOs of SBX.
I have modified the python generated by a GRC FG and here are the
relevant changes
.
Kind Regards,
John
On 12/09/17 21:12, mle...@ripnet.com wrote:
Use "unknown PPS" on both of them. The MIMO cable shares both
REFCLOCK and 1PPS signals, so they will both be synchronized to the
same time.
On 2017-09-12 16:13, John Shi
SRPs between tests or just rerunning the
GRC flowgraph? Do you have shared 10 MHz and 1 PPS references? What
version of UHD is printed in the output?
Thanks,
Derek
On Mon, Sep 11, 2017 at 1:50 AM, John Shields <sla1nte2...@gmail.com
<mailto:sla1nte2...@gmail.com>> wrote:
Th
Thanks for the feedback but I am not sure that I understand it. What I
was hoping to do was step through the configurations with increasing
levels of synchronisation and expecting to see same.
Marcus' comment is correct and I have not, yet, put in the code which
synchronises SBXs.
I guess
On 07/17/2017 03:43 PM, Marcus D. Leech wrote:
On 07/17/2017 03:41 AM, John Shields wrote:
On 17/07/17 05:53, Marcus D. Leech wrote:
On 07/17/2017 12:47 AM, John Shields wrote:
Even after I re-installed pyephem (for python 2)
the issue continues i.e. logger_tp undefined
location, figure out what's missing
after that, and rebuild.
Best regards,
Marcus
On 07/17/2017 03:43 PM, Marcus D. Leech wrote:
On 07/17/2017 03:41 AM, John Shields wrote:
On 17/07/17 05:53, Marcus D. Leech wrote:
On 07/17/2017 12:47 AM, John Shields wrote:
Even after I re
On 17/07/17 05:53, Marcus D. Leech wrote:
On 07/17/2017 12:47 AM, John Shields wrote:
Even after I re-installed pyephem (for python 2) the
issue continues i.e. logger_tp undefined and malloc error. GRC is
sane in that I can instantiate a USRP source and display it's FFT
On 17/07/17 03:08, Marcus D. Leech wrote:
On 07/16/2017 11:03 PM, John Shields wrote:
Hi Marcus,
An update - i reinstalled python-wxgtk2.8 and that
dependency was satisfied when I re-ran Marcus' build_gnuradio script.
When I run the same command as before, I
On 17/07/17 03:08, Marcus D. Leech wrote:
On 07/16/2017 11:03 PM, John Shields wrote:
Hi Marcus,
An update - i reinstalled python-wxgtk2.8 and that
dependency was satisfied when I re-ran Marcus' build_gnuradio script.
When I run the same command as before, I
nt RX2 --srate 10.0e6 --dbw 8.0e6 --freq 1420.4057e6 --gain
37.5 --dcg 1000 --lrate 30 --integ 30 --devid
uhd='a',type=usrp2,addr=192.168.10.2,lo_offset=7.34e6,subdev=A:0
--longitude 172.570925 --latitude -43.519023
and then something like
grep osmosdr opened_files.txt
Then, simply
:)
Best regards,
Marcus
On 07/16/2017 11:44 AM, John Shields wrote:
Thanks Marcus,
I used the other Marcus' build_gnuradio
script and I believe that it rebuilt gr-osmosdr. How would I check?
I built 3.7.11.1 on July 7th on 14.04 LTS and
today,
:53 AM, John Shields wrote:
Hi,
While I usually regret it, I decided to update my Ubuntu system
from 14.04 LTS to 16.04 LTS and it seemed to go fine. I rebuilt
GNURadio and UHD and that seemed to go fine but when I run Simple_ra
with:
simple_ra --aperture 2.4 --ant RX2 --srate 10.0e6 --dbw
Hi,
While I usually regret it, I decided to update my Ubuntu system from
14.04 LTS to 16.04 LTS and it seemed to go fine. I rebuilt GNURadio and
UHD and that seemed to go fine but when I run Simple_ra with:
simple_ra --aperture 2.4 --ant RX2 --srate 10.0e6 --dbw 8.0e6 --freq
1420.4057e6
. Mai 2016 01:53:54 MESZ, schrieb John Shields
<sla1nte2...@gmail.com>:
On 30/05/16 22:29, Marcus D. Leech wrote:
On 05/30/2016 06:27 PM, John Shields wrote:
oops, it was not simple_ra that I tried to re-compile against
the new GNURadio etc., it was gr-ra_
On 30/05/16 22:29, Marcus D. Leech wrote:
On 05/30/2016 06:27 PM, John Shields wrote:
oops, it was not simple_ra that I tried to re-compile against the new
GNURadio etc., it was gr-ra_blocks.
Sorry,
John
Which is a pre-req for simple_ra
On 30/05/16 22:05, John Shields wrote:
Hi,
Since I moved from 14.04 LTS to 15.10 a couple of weeks ago, I have
been experiencing segmentation faults on i965_dri (graphics rendering).
In order to (hopefully) move away from this issue, yesterday I
upgraded to 16.04 LTS and rebuilt
Hi,
Since I moved from 14.04 LTS to 15.10 a couple of weeks ago, I have
been experiencing segmentation faults on i965_dri (graphics rendering).
In order to (hopefully) move away from this issue, yesterday I
upgraded to 16.04 LTS and rebuilt GNURadio (3.7.9.2) and UHD using
Marcus'
, and it doesn't always help if your system randomly
hangs in WX things, but if it solves this:
find (or create) your ~/.gnuradio/config.conf and add
[wxgui]
style = nongl
Best regards,
Marcus
On 29.05.2016 02:22, John Shields wrote:
Hi,
Have GNURadio 3.7.9.2 installed on Ubuntu 15.10. I
Hi,
Have GNURadio 3.7.9.2 installed on Ubuntu 15.10. I have been
running simple_ra but don't believe that is germane to the problem at hand.
I am running simple_ra_receiver under debug (have seen segmentation
errors in libc in the past and trying to narrow down) but, again, don't
On 22/05/16 11:06, Marcus D. Leech wrote:
On 05/22/2016 05:19 AM, Marcus Müller wrote:
Hi John,
I don't really know about the memory usage you see, but:
Did you rebuild GNU Radio (and UHD and basically everything you did not
install directly through Ubuntu's apt-get)? Upgrading a distro often
Dear All,
I have been running GNURadio fairly constantly for a
couple of weeks now using simple_ra although, I don't believe it is a
problem with that application as HTOP doesn't indicate memory issues etc.
I run GNURadio version 3.7.9.1 on an Intel® Core™ i7-2600
/16 19:12, mle...@ripnet.com wrote:
The native BER of 1000BASE-T is better than 1.0e-11 or so.
Which means you'd expect a bad bit roughly every half-hour at 2msps
(64Mbit/sec), the bad-bit probabilities get worse as you make the
cable longer.
On 2016-05-03 12:59, John Shields wrote:
On 03
' treatment?
On 2016-05-03 04:32, John Shields wrote:
Thanks Marcus,
Have put answers in-line.
Kind Regards,
John
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org <mailto:Discuss-gnura
Thanks Marcus,
Have put answers in-line.
Kind Regards,
John
On 03/05/16 08:20, Marcus Müller wrote:
On 03.05.2016 09:52, John Shields wrote:
On 03/05/16 02:58, Marcus D. Leech wrote:
On 05/02/2016 10:40 PM, John Shields wrote:
the system runs
On 03/05/16 02:58, Marcus D. Leech wrote:
On 05/02/2016 10:40 PM, John Shields wrote:
Hi,
I am using Ubunutu 14.04 LTS with GNURadio 3.7.9.1 and have a USRP
N200 with SBXv3. I have been using the aptly-named and highly useful
Simple_ra though I believe this is orthogonal to the issues I am
On 03/05/16 02:58, Marcus D. Leech wrote:
On 05/02/2016 10:40 PM, John Shields wrote:
Hi,
I am using Ubunutu 14.04 LTS with GNURadio 3.7.9.1 and have a USRP
N200 with SBXv3. I have been using the aptly-named and highly useful
Simple_ra though I believe this is orthogonal to the issues I am
Hi,
I am using Ubunutu 14.04 LTS with GNURadio 3.7.9.1 and have a USRP
N200 with SBXv3. I have been using the aptly-named and highly useful
Simple_ra though I believe this is orthogonal to the issues I am seeing.
when I run simple_ra with :
simple_ra --srate 2e6 --freq 848e6 --gain 37
Ubuntu 12.04 LTS, GNU Radio 3.6.1git-2-g2c7ea132 (on i7).
I have a simple GRC flow with a couple of file sources - these are
FIFOs. I have a separate application which will simulate various antenna
configurations and it attempts to open both of these FIFOs in
O_WRONLY|O_NONBLOCK . As the
On 23/06/12 14:00, Marcus D. Leech wrote:
Ubuntu 12.04 LTS, GNU Radio 3.6.1git-2-g2c7ea132 (on i7).
I have a simple GRC flow with a couple of file sources - these are
FIFOs. I have a separate application which will simulate various
antenna configurations and it attempts to open both of these
On 12/06/12 21:00, Martin Braun wrote:
On Tue, Jun 12, 2012 at 08:19:21PM +1200, John Shields wrote:
When I add a FFT block in the GRC (gr_fft_vxx if I understand things
correctly) I am offered a boolean parameter 'shift'. When I attempt
to discern the code, there is a comment:
// apply
On 06/06/12 18:40, Josh Blum wrote:
On 06/05/2012 11:38 PM, John Shields wrote:
Hi Josh,
It turns out I was using the block I think you were recommending. Here is a
picture of the flowgraph with the red arrow which would appear to be an issue
as, with it present, the flow graph
I have complex multiplied a couple of 1 msps complex values and I wish
to do a 2048 FFT so am trying to convert to 2048-length vector but I
cannot find a suitable block in the 'stream conversion' group of GRC. By
making vec length 2048 I get the correct kind of connector on the output
of the
Thanks, Josh. Will give it a whirl.
Kind Regards,
John
On 03/06/12 05:33, Josh Blum wrote:
On 06/02/2012 01:00 AM, John Shields wrote:
I have complex multiplied a couple of 1 msps complex values and I wish
to do a 2048 FFT so am trying to convert to 2048
Thanks very much Marcus. I eventually figured out that in the variable block, I
needed to include:
gr.firdes.complex_band_pass (gain,sampling_freq,low_cutoff_freq,
high_cutoff_freq, transition_width, window = WIN_HAMMING,beta = 6.76)
and when I plugged in some variables based on the b/w and
In the April/May 2010 SARA Journal, Marcus Leech had an article entitled
Building an SDR SID Receiver in an Afternoon which was highly
information and inspirational. While my sound card only goes to 48 KHz
sampling, I decided to try his implementation and in terms of entry into
GRC, things have
Have given up on WUBI (Lucid) and build/install according to
gnuradio../wiki/gnuradio/UbuntuInstall
Decided to install boost_1_37_0 as _1_44_0 did not conform to
instructions on above wiki.
This allowed me (Under Installing GNU Radio section) to ./configure
--with -boost=$BOOST_PREFIX which had
Have given up on WUBI (Lucid) environment and build/install according to
gnuradio../wiki/gnuradio/UbuntuInstall on a native Ubuntu(Jaunty)
Decided to install boost_1_37_0 as _1_44_0 which I used previously as it
was the latest version, did not conform to instructions on above wiki.
This allowed
I recently purchased a USRP and have a fresh install of WUBI (HP Pavillion DV5
, Windows Home Vista) and used gnuradio.org/redmine/wiki/gnuradio/UbuntuInstall
to install things.
I passed 'make check' correctly
I have my username in the group usrp
j...@ubuntu:~/gnuradio$ ls -lR /dev/bus/usb |
and O is overrun? I briefly looked at the source
but am not familiar with GNU_Radio and it's classes.
Thanks again for your suggestion,
Regards,
John
- Original Message -
From: Eric Blossom e...@comsec.com
To: John Shields john.shie...@xtra.co.nz
Cc: discuss
44 matches
Mail list logo
