Hi,
I have used USRP N210 with CBX40 at 1.18GHz
I got a low performance when two USRP N210 communicate
I used 'benchmark_tx.py' and 'benchmark_rx.py' located at
~/gnuradio/gr-digital/example/ofdm
Commands I used are below each other :
Tx) ./benchmark_tx -f 1.18G -m qpsk --tx-gain=31.5 -W 25000
I'm not super familiar with the octoclock-g, will it produce an output if
the GPS isn't locked? I see what looks like a disconnected GPS Antenna
connector, which would make it unlikely for the GPS to ever lock.
Nick
On Fri, Jul 8, 2016 at 12:12 AM, Pavan Yedavalli
wrote:
> It's an Octoclock-G (
It's an Octoclock-G (https://www.ettus.com/product/details/OctoClock-G is
what I ordered). And yes, that is true about the external clock inputs and
GPS lock. Does that matter if it's an Octoclock-G?
On Thu, Jul 7, 2016 at 7:46 PM, wrote:
> Is this an Octoclock, or Octoclock-G?
>
> If it's just
Hello,
I am a new GNU Radio user. I am looking to build a system that can transmit
a packet at a pre-defined time with very high accuracy (about 1
nanosecond). Having gone through the mailing list I am aware that timed
transmission is a common task and many people have asked similar questions.
How
Is this an Octoclock, or Octoclock-G?
If it's just an Octoclock, then it has no internal clocks, and acts as a
high-quality clock/pps distributor.
I notice you don't have the external clock inputs connected to anything,
and there's no GPS LOCK indicator.
On 2016-07-07 17:08, Pavan Yedavalli w
Mostafa,
I'm not sure why you were not able to download it, I just checked the site
and confirmed the download link is active. Can you tell me what sort of
error you are getting?
As Gavin mentioned, the scripts really are for the intrepid only at this
point, the windows world is more focused on
Gavin,
Thanks for that. I will include your instructions, and see what I can do
to make it more streamlined.
Geof
On Thu, Jul 7, 2016 at 2:28 PM, Gavin Jacobs
wrote:
> You may recall that I asked if it was feasible to build an OOT
> module/block for GRC on Windows. To answer my own question,
Dave,
if you've fixed one issue, please start a new thread for the next issue.
As for your q's:
On 07/07/2016 04:37 PM, Dave wrote:
> One more question however, should I run volk_profile or did the pybombs
> install already take care of that?
pybombs does not run volk_profile for you (it used to
Thanks Derek and Martin.
I followed the instructions regarding permission access to USB. I’m not
positive but I think I had to rerun setup_env.sh as well. Now
uhd_find_devices functions as expected. Thanks you. I ran the
uhd_wbfm_receive flow graph. At first I did not get any audio. I
First I should give some context on my project. What we are trying to build
is a python server that utilizes gnuradio's blocks to get information from
hardware and send it outbound, as well as receiving requests from clients
to the server about configuration of flowgraph. More specifically, right
n
Hello Dave,
Here are the instructions for setting up USB permissions on Linux.
http://files.ettus.com/manual/page_transport.html#transport_usb_udev
Regards,
Derek
On Thu, Jul 7, 2016 at 2:19 PM, Dave wrote:
> Thanks Martin.
>
> I successfully deleted UHD and I believe successfully installed gn
Thanks Martin.
I successfully deleted UHD and I believe successfully installed gnuradio et
el using pybombs. I then ran setup_env.sh.
However now I cannot seem to connect to the B100.
I ran uhd_find_devices and followed the instructions to download images as
per the transcript that follows. Wa
You may recall that I asked if it was feasible to build an OOT module/block for
GRC on Windows. To answer my own question, it is barely feasible. The folks who
created the windows binary package cleared the path through the jungle, but
they left a lot of breadcrumbs in the resulting build. If an
On 07/06/2016 11:53 PM, Dave wrote:
> Thanks Martin. I have changed my subscription to individual messages.
>
> I ran the command you mentioned below and attached the result. I’m not
> sure if I should delete all the entries listed or even why I get all the
> “permission denied” messages. As yo
On 07/06/2016 11:34 PM, Robert Kraml wrote:
> Thank you Martin.
>
> This one looks like it will involve some research. If I have time I'll
> pursue it. In the meantime if anyone has some C++ example code that
> shows how an application might extract time tags, I would be grateful.
The header_pa
Jan,
also, don't forget, code you write is yours. You can even have multiple
licenses for the same code (at least for modules and parts that don't
use GNU Radio or other GPL'd libraries).
Cheers,
Martin
On 07/07/2016 06:18 AM, Jan Krämer wrote:
> Thanks Michael, now fingers crossed that I am all
Hi Jan -
If you have any further questions regarding licenses as they pertain to GNU
Radio, feel free to e-mail me directly. I'm happy to answer questions &
help.
Thanks to Sylvain and MLD for providing great answers!
Cheers,
Ben
On Thu, Jul 7, 2016 at 9:18 AM, Jan Krämer wrote:
> Thanks Mich
You wanted to use the packaged Gnu Radio, which packages UHD 3.9.3, so,
that header show the correct version coming out of the UHD version that
is packaged with the GNu Radio package for windows.
I asked you to remove the UHD 3.9.4 package that you'd installed
separately, because it was in confli
Thanks Michael, now fingers crossed that I am allowed to publish the code
under one of those licenses.
Cheers,
Jan
2016-07-07 12:18 GMT+02:00 Michael Dickens :
> What Sylvain wrote is correct: if you publish your GR OOT module, then you
> have to choose GPLv3 or a compatible FOSS license. I beli
What Sylvain wrote is correct: if you publish your GR OOT module, then
you have to choose GPLv3 or a compatible FOSS license. I believe that by
default the license is GPLv3, since that's what GR is. See also <
http://www.gnu.org/licenses/license-list.html > for a list of compatible
(and incompatibl
Hey Silvain,
I think I talked to Tom about this some years ago, and he stated that the
GNURadio OOT block code has to be GPLv3 or at least a compatible license.
Because that for sure is a derivative work. But you might be right that it
does not need to be strictly GPLv3 and Tom might have also sta
> I think the GNURadio OOT block glue has to be GPLv3 in any case and that is
> fine.
Why ?
As long as the license is GPLv3 compatible you can publish it under
what you like.
Now of course when re-distributed as binary/complete system, the
effective license will be GPLv3 because the gplv3 compati
Hey all,
I think I already asked this but I wanted to be sure.
I am asking permission from my employer to rewrite some of our GPU SDR
blocks
as a GNURadio OOT. Now they asked me to provide a list of possible licenses
for our code.
I think the GNURadio OOT block glue has to be GPLv3 in any case a
thank you for your help, but I currently could not download the
*"gnuradio_3.7.9.2_win64.msi"* file!!
why?
Best,
Mostafa
***
Tehran
IRAN
Tel: +98 (919) 158-7730
Emails: m.alizade...@gmail.com, m.alizade...@aut.ac.ir
Homepage: Linkedin
24 matches
Mail list logo