NEW ISSUE - no GRC??. I can't call it from the target, home or pybombs
directory and there's no recipe for it. any thoughts?
GRC comes with gnuradio itself.
If it's not there, something failed during the cmake/build step, but
without the full logs, can't really say anything.
My guess is that
The audio sinks do that; you might have to use your OS's mixer settings
for selecting the mic.
The audio sink/source are like the UHD blocks in that you pipe in
floats, and 1 maps to FS. So keep your abs value below 1 and you're good.
gr-audio has some examples for you to peruse.
M
On
I've submitted a pull request for the compile issue in gr-dtv.
However, it takes a little while for requests to get merged.
You're missing gnuradio-companion because your version of
SWIG is failing the version check. See line 982 in your first
pastebin. The minimum SWIG version required is
Hi all,
I've got my packet based radio working now, so I want to test it by talking
into a mic on the transmitter laptop and playing the stream on the speakers
of the receiver laptop.
I realized I don't know how to integrate the audio sink floating point
output of the mic to my byte based radio
Another reminder.
Note that SOCIS does not have a Melange or similar, so please upload
your proposals to github and inform the list about them. Earlier
proposals have a higher chance of succeeding, simply because you get
more feedback.
Don't miss out on the €€€ and fame!
M
On 11.03.2015
NEW ISSUE - no GRC??. I can't call it from the target, home or pybombs
directory and there's no recipe for it. any thoughts?
GRC comes with gnuradio itself.
*that's what i thought as it's always been that way.*
If it's not there, something failed during the cmake/build step, but
without the
On 03/23/2015 05:43 PM, Richard Bell wrote:
The second was a 'comment through' option. This comments out the block
and passes data through it to the next block. Saves having to mess
with wires between blocks that are commented out.
Martin's quite right, there is way more to be done, than
Thanks for the early reply Ralph.
First of all, it is normal that the USRP is not detected anymore with
the uhd tools when it is claimed by OpenBTS. So this looks not alarming.
Note that our successful implementation did not have any issue with
UHD-USRP connection. It worked as it was before
Greetings all,
I recently began using gnuradio and GRC with a pair of USRPs.
It's my understanding that plans are underway to ultimately remove WX in
v3.9 as a GUI option from gnuradio, and replace it with QT. It's also my
understanding that QT GUI development is underway in future
Greetings all,
I recently began using gnuradio and GRC with a pair of USRPs.
It's my understanding that plans are underway to ultimately remove WX in
v3.9 as a GUI option from gnuradio, and replace it with QT. It's also my
understanding that QT GUI development is underway in future
Hi Marcus, Thanks for the instant tips. One question. As I aware the latest
bug free UHD package is uhd-master. Though my last build was related with
uhd-master, since I have tried different ways of GNURadio and UHD
installations (pybombs option, download-unzip-build option, debian
download),* I
I'm looking for old BBN 802.11 codes.
But, links in gnuradio.org (
http://gnuradio.org/redmine/projects/gnuradio/wiki/BBN_Technologies_Internetwork_Research_ADROIT_Project)
may not seem to work.
Does anyone know where I can get the codes, or does anyone have the back
ups?
Regrads,
Jeon.
Thanks Martin, got it.
Rich
On Tue, Mar 24, 2015 at 4:43 PM, Martin Braun martin.br...@ettus.com
wrote:
The audio sinks do that; you might have to use your OS's mixer settings
for selecting the mic.
The audio sink/source are like the UHD blocks in that you pipe in floats,
and 1 maps to FS.
On Tue, Mar 24, 2015 at 10:00 AM, Richard Bell richard.be...@gmail.com
wrote:
Is there a plan to improve the layout customizability beyond the GUI
Hints? I think the gui hints are counter-intuitive and don't provide a lot
of control.
Rich
I don't find them that counter-intuitive. The (row,
Thanks, Rich, see below for some comments.
On Tue, Mar 24, 2015 at 11:00 AM, Richard Bell richard.be...@gmail.com
wrote:
Yes. I'm glad you asked :-).
The counter-intuitiveness of it for me, comes from rowspan and colspan. I
might make an incorrect statement here, so please correct me if I
Hey George,
As Marcus mentioned, we are working to rewrite GRC using QT rather than
GTK. If your interested in QT GUI stuff, check out the GRC working group
page and repo:
https://gnuradio.org/redmine/projects/gnuradio/wiki/GRCWG
https://github.com/gnuradio/gnuradio-wg-grc/
On 24.03.2015 09:04, George Hadley wrote:
Greetings all,
I recently began using gnuradio and GRC with a pair of USRPs.
It's my understanding that plans are underway to ultimately remove WX in
v3.9 as a GUI option from gnuradio, and replace it with QT. It's also my
understanding that QT
On Tue, Mar 24, 2015 at 9:55 AM, Richard Bell richard.be...@gmail.com
wrote:
Sebastian,
Now that the issue is on the issue tracker, how long does it usually
take for that to make it into the distributed version of gnu radio? What
has to happen before then? I'm curious.
v/r,
Rich
Rich,
Hi George,
It's also my understanding that QT GUI development is underway in
future versions of gnuradio.
I'd say it's pretty usable and stable in *current* versions of gnuradio.
It's also my understanding that QT GUI development is underway in
future versions of gnuradio.
Have a git blame one
Whoops, didn't see this reply when I wrote my own!
M
On 24.03.2015 09:54, Tom Rondeau wrote:
On Tue, Mar 24, 2015 at 9:01 AM, George Hadley ghad...@purdue.edu
mailto:ghad...@purdue.edu wrote:
Greetings all,
I recently began using gnuradio and GRC with a pair of
USRPs.
On Tue, Mar 24, 2015 at 9:01 AM, George Hadley ghad...@purdue.edu wrote:
Greetings all,
I recently began using gnuradio and GRC with a pair of USRPs. It's
my understanding that plans are underway to ultimately remove WX in v3.9 as
a GUI option from gnuradio, and replace it with QT.
Sebastian,
Now that the issue is on the issue tracker, how long does it usually take
for that to make it into the distributed version of gnu radio? What has to
happen before then? I'm curious.
v/r,
Rich
On Tue, Mar 24, 2015 at 8:02 AM, Koslowski, Sebastian (CEL)
sebastian.koslow...@kit.edu
Is there a plan to improve the layout customizability beyond the GUI Hints?
I think the gui hints are counter-intuitive and don't provide a lot of
control.
Rich
On Tue, Mar 24, 2015 at 9:57 AM, Martin Braun martin.br...@ettus.com
wrote:
On 24.03.2015 09:04, George Hadley wrote:
Greetings
On 24.03.2015 12:10, Anderson, Douglas J. wrote:
[...]
I actually considered implementing the lo_offset message code myself
and then doing a pull request, but I just couldn't think of a good
way to match the flexibility of a tune_request struct within the
confines of a single pmt message.
Hey
Hi Martin, sorry for the slow reply, I've been having fun with SWIG.
I was able to pass the usrp_source instance into my block after I discovered
that SWIG adds a __deref__ method that exposed the naked pointer, then I just
had my block take gr::uhd::usrp_source* type.
u =
Aha! The middle menu button click works after all :-) Thank you very
much for your help everyone!
I was able to get the middle button click functionality to work in the
individual sinks (QT GUI Time Sink, QT GUI Frequency Sink, QT GUI
Constellation Sink, and QT GUI Waterfall Sink) however, I
First of all, it is normal that the USRP is not detected anymore with the uhd
tools when it is claimed by OpenBTS. So this looks not alarming.
Are you able to verify if RF is transmitted? Is there some spectrum analyzer
available, or a receiver that can tune into the used GSM frequency, best
Hi Zamrath,
Could I know the reason for USRP connection loss?
there's no connection loss -- the USRP is just now talking to the
OpenBTS application, and won't talk to other applications, including
uhd_usrp_probe.
Surely transmission LED (labeled A) is not working.
Ok, that means the USRP is not
Yeah the dict idea was kind of what I was going for with the pairs (in pseudo
code)
tuple(
command,
pair(param1, val1),
pair(param2, val2),
...
)
It feels intuitive because it maps pretty well to the function call
command(param1=val1, param2=val2), and it works with the current state
Yes. I'm glad you asked :-).
The counter-intuitiveness of it for me, comes from rowspan and colspan. I
might make an incorrect statement here, so please correct me if I do.
1) I think rowspan and colspan should give you control over the height and
width of the widget. Instead, it defines how
Hello,
the documentation for the PLL blocks in GNURadio says: All settings
max_freq and min_freq are in terms of radians per sample, NOT HERTZ.
Therefore I thought that to specify a bandwidth `bw` it would have to
converted from natural frequency units (Hz) into radians per sample with
something
31 matches
Mail list logo
