On 12/06/2011 06:39 PM, Paul Miller wrote:
> On Tue, Dec 06, 2011 at 12:44:17PM -0800, Josh Blum wrote:
>> Whats your OS? I have tested it on a few recent ubuntus and fedoras, and
>> windows with a recent boost.
>
> Arch. Everything is wacky new because of rolling release. It's
> super easy to
On Tue, Dec 06, 2011 at 12:44:17PM -0800, Josh Blum wrote:
> Whats your OS? I have tested it on a few recent ubuntus and fedoras, and
> windows with a recent boost.
Arch. Everything is wacky new because of rolling release. It's
super easy to get going if you build a test box, and I will
happily
On 12/06/2011 02:56 PM, Tom Rondeau wrote:
> On Tue, Dec 6, 2011 at 5:51 PM, Josh Blum wrote:
>
>>
>>>
>>> [ 47%] Generating general_swig_doc.i
>>> Error in xml in file
>> /home/gr/source/git/gnuradio/build/gnuradio-core/src/lib/swig/general_swig_doc_swig_docs/xml/gr__simple__framer__sync_8h.x
Dear all,
I finally figure out how to receive packet using OFDM and Alamouti but
unfortunately looks like I cannot detect all the peaks.
10% of the packets that I receive are right.
I think that I experience a phase rotation, i.e. instead of receiving
-1, I receive +1 for some preamble symbols and
On Tue, Dec 6, 2011 at 6:11 PM, Marcus D. Leech wrote:
> On 12/06/2011 06:02 PM, Tom Rondeau wrote:
>
>>
>> Alright, good. Just making sure we didn't actually need the .la files.
>> Which is good, since making them "correctly" (that is, identical to the
>> output of autotools) could have been a r
On Thu, Dec 1, 2011 at 10:15 PM, Muhammad Rosli wrote:
> Hi,
>
> Thanks for your reply. I am using the narrowband example.
>
> If I attempt using
>
> ./benchmark_tx.py -f 400M -r 250k -S 4
>
> and
>
> ./benchmark_rx.py -f 400M -r 250k -S 4
>
> which I worked out from reading the README file, the r
On 12/06/2011 06:02 PM, Tom Rondeau wrote:
Alright, good. Just making sure we didn't actually need the .la files.
Which is good, since making them "correctly" (that is, identical to
the output of autotools) could have been a real pain.
Thanks!
Tom
Ok, "this evening" has arrived with a sicke
2011/12/4 Nakajo Tomoyuki
> Dear all,
>
> I try to use uhd_fft.py.
>
> The viewing area is displayed, but, no waveform is displayed on viewing
> area.
> Please tell me how to manage the trouble.
>
> A result of uhd_fft.py is below,
>
> -
On Tue, Dec 6, 2011 at 4:16 PM, Alexandru Csete wrote:
> On Tue, Dec 6, 2011 at 6:33 PM, Tom Rondeau wrote:
>
>> On Tue, Dec 6, 2011 at 12:56 AM, Josh Blum wrote:
>>
>>> >>
>>> http://gnuradio.org/cgit/gnuradio.git/commit/?id=56fcd5f9b22af33976f9413d3a9d0aec41a7b556
>>> >>
>>> >> -josh
>>> >
On Tue, Dec 6, 2011 at 5:06 PM, John Coppens wrote:
> On Tue, 6 Dec 2011 12:51:50 -0500
> Tom Rondeau wrote:
>
> > John,
> > Where are you running GRC from? And are you trying to run this inside GRC
> > or on the command line after you generate the .py file?
>
> I call gnuradio-companion from a
On Tue, Dec 6, 2011 at 5:35 PM, Justin Ford wrote:
>
> Is there a solution for building gnuradio on 64-bit Linux using the stable
> v3.4.2 release?
>
> I'm seeing errors similar to the following thread when building gnuradio
> from the v3.4.2 source tarball on RHEL 5.7 x86_64:
> http://lists.gnu
On Tue, Dec 6, 2011 at 5:51 PM, Josh Blum wrote:
>
> >
> > [ 47%] Generating general_swig_doc.i
> > Error in xml in file
> /home/gr/source/git/gnuradio/build/gnuradio-core/src/lib/swig/general_swig_doc_swig_docs/xml/gr__simple__framer__sync_8h.xml
> > Traceback (most recent call last):
> > Fil
>
> [ 47%] Generating general_swig_doc.i
> Error in xml in file
> /home/gr/source/git/gnuradio/build/gnuradio-core/src/lib/swig/general_swig_doc_swig_docs/xml/gr__simple__framer__sync_8h.xml
> Traceback (most recent call last):
> File "/home/gr/source/git/gnuradio/docs/doxygen/swig_doc.py", li
Is there a solution for building gnuradio on 64-bit Linux using the stable
v3.4.2 release?
I'm seeing errors similar to the following thread when building gnuradio from
the v3.4.2 source tarball on RHEL 5.7 x86_64:
http://lists.gnu.org/archive/html/discuss-gnuradio/2011-09/msg2.html.
I f
On Tue, 6 Dec 2011 12:51:50 -0500
Tom Rondeau wrote:
> John,
> Where are you running GRC from? And are you trying to run this inside GRC
> or on the command line after you generate the .py file?
I call gnuradio-companion from a terminal window (That's where the
error messages come from)
> I'm a
On Tue, Dec 6, 2011 at 6:33 PM, Tom Rondeau wrote:
> On Tue, Dec 6, 2011 at 12:56 AM, Josh Blum wrote:
>
>> >>
>> http://gnuradio.org/cgit/gnuradio.git/commit/?id=56fcd5f9b22af33976f9413d3a9d0aec41a7b556
>> >>
>> >> -josh
>> >>
>> >>
>> >> Marcus, would you be up for trying that? The resulti
On 12/05/2011 06:40 PM, Paul Miller wrote:
> On Mon, Dec 05, 2011 at 08:30:17AM -0800, Josh Blum wrote:
>> Looks like I had a typo in the forecast call, fix is pushed. I should
>> have had unit testing for the general_work as well.
>> http://gnuradio.org/cgit/jblum.git/log/?h=python_blocks
>
> C
>
> How do I get configure to see the correct libraries and includes?
>
Well, I found what I think is a solution...I made two symlinks:
/usr/include/boost141/include -> /usr/include/boost141/boost
/usr/include/boost141/boost/boost -> /usr/include/boost141/boost
This can't be "the right way" to
>
> How do I point configure for gnuradio to the boost141 include directory?
>
I discovered that libraries from a failed attempt at building boost from source
were being used. I removed these, and now my problem is more fundamental:
configure fails to identify boost. I have boost141 (v1.41)
Hello gnuradio world! I'm trying to get started and I'm getting hung up
building and installing. I'm following the build guide.
How do I point configure for gnuradio to the boost141 include directory?
I am building gnuradio-3.4.2 from the source tarball on RHEL 5.7 x86_64. When
I try to mak
Patrik,
Can you please check to see that the WBX LO is locked? If you have a
GRC flowgraph, you can use a function probe block with the following
settings:
ID: lo_locked
Block ID: uhd_usrp_source_0 (or whatever your UHD source block is named)
Function name: get_dboard_sensor
Function args: '"lo_
On Tue, Dec 6, 2011 at 12:20 AM, John Coppens wrote:
> Hi,
>
> Pardon my newness to gnuradio... I compiled and installed the latest
> dev tar.gz. I tried to compile 3.4.2 with autotools, but didn't get
> anywhere. So I followed an advice in a mail I found, and, using
> cmake/gmake, all went well
On Tue, Dec 6, 2011 at 5:21 AM, wrote:
> Hello all,
> I was using usrp2_rx_cfile.py module to sense 2.4G channel by using RX2400
> board(2.2G to 2.9G). Now I want to sense TV frequencies so I have changed
> the daughter board to wbx daughter board ( 50 MHz to 2.2G). But now I
> cannot sense the s
On Tue, Dec 6, 2011 at 12:56 AM, Josh Blum wrote:
> >>
> http://gnuradio.org/cgit/gnuradio.git/commit/?id=56fcd5f9b22af33976f9413d3a9d0aec41a7b556
> >>
> >> -josh
> >>
> >>
> >> Marcus, would you be up for trying that? The resulting la files do not
> >> match what comes out of autotools. We d
>
Hi,
While I was testing the DQPSK-(de)modulation blocks in GRC.
>>> I found a frequency region where the reception failed. I
>>>
>> started with
>>
>>> the ISM-band (433 MHz) as the center frequency, and the reception
>>> didn't work. After checking my
Hello all,
I was using usrp2_rx_cfile.py module to sense 2.4G channel by using RX2400
board(2.2G to 2.9G). Now I want to sense TV frequencies so I have changed the
daughter board to wbx daughter board ( 50 MHz to 2.2G). But now I cannot sense
the signal by using coaxial cable connected to my usr
26 matches
Mail list logo
