Song,
Every transmitted pkt has structure
preamble:access_code:header:payload_with_crc:'\x55'
header consists of 2 16-bit shorts, having payload length and whitener
offset.
On receiver side "framer sink" extracts the payload depending upon the
value of header (2 shorts).
see "packet_util
Just to follow up, have you tried using the auto calibration of the IQ
channel released recently?
As far as we can discern, this might give you a good deal of reduction in
the problematic spurious frequencies.
Also by using manual tuning where the daughterboard tuning is at least 12.5
kHz away (fo
Thank you so much for your suggestions. I am wondering how to connect these
work class with other blocks in the flowgraph which have been built? In other
words, how to use them in flowgraph building?
On 12/01/11, Josh Blum wrote:
>
>
> On 12/01/2011 01:31 PM, Yan Nie wrote:
> > Dear all,
> >
Hi Kouki,
I don't think you will see the signal in an FFT window. GPS is spread
spectrum and the signal is below the noise floor. But the signal is
still decodable.
On 12/07/2011 08:38 PM, 山本弘貴 wrote:
> Hi,all.
>
> I want to receive GPS L1 signal.and want to analyze location data in PC
>
> Now I
2011/12/8 Dan CaJacob
> Hi Kouki,
>
> I don't think you will see the signal in an FFT window. GPS is spread
> spectrum and the signal is below the noise floor. But the signal is
> still decodable.
I thought this was the case; but as someone without any DSP experience this
boggles the mind... Do
http://en.wikipedia.org/wiki/Process_gain
On Thu, Dec 8, 2011 at 12:30 PM, Matt Mills wrote:
> 2011/12/8 Dan CaJacob
>>
>> Hi Kouki,
>>
>> I don't think you will see the signal in an FFT window. GPS is spread
>> spectrum and the signal is below the noise floor. But the signal is
>> still decodab
On Wed, Dec 7, 2011 at 3:27 PM, Matt Mills wrote:
> *frowns at ubuntu*
>
After updating to Ubuntu 11.10 (which has boost 1.46) I still experience
the lockup.
linux; GNU C++ version 4.6.1; Boost_104601; UHD_003.004.000-7dc76db
___
Discuss-gnuradio mail
In a less mathematical and more qualitative explanation, consider that
at any point in time, one bit of your signal is spread out over a wide
frequency spectrum. If you think of adding up all of the measurements
of little frequency bins across the whole spread spectrum, the noise
in each bin, bei
I noticed dramatic changes in the 3.5.0 release in the generation of the
constellation points of digital modulations. So, if the easy part is to
again modify the source code to match my needs, i need some help in
using the new block :
/digital.constellation_decoder_cb(arg1)/
instead of
/
gr.c
On Dec 8, 2011, at 1:05 PM, Matt Mills wrote:
> After updating to Ubuntu 11.10 (which has boost 1.46) I still experience the
> lockup.
For the record, I was testing on this:
morbo:~$ cat /etc/slackware-version; uname -a
Slackware 13.37.0
Linux morbo 2.6.37.6 #3 SMP Sat Apr 9 22:49:32 CDT 2011
I noticed dramatic changes in the 3.5.0 release in the generation of the
constellation points of digital modulations. So, if the easy part is to
again modify the source code to match my needs, i need some help in
using the new block :
/digital.constellation_decoder_cb(arg1)/
instead of
/
gr.c
On Thu, Dec 8, 2011 at 5:33 PM, Arturo Rinaldi wrote:
> I noticed dramatic changes in the 3.5.0 release in the generation of the
> constellation points of digital modulations. So, if the easy part is to
> again modify the source code to match my needs, i need some help in using
> the new block :
>
On Thu, Dec 8, 2011 at 2:05 PM, Matt Mills wrote:
> After updating to Ubuntu 11.10 (which has boost 1.46) I still experience
> the lockup.
>
Also, Here's the python I've been using to reproduce:
http://pastebin.com/at0FdzXp
and the GDB backtrace after its locked up: http://pastebin.com/vx9cgSzp
On Thu, Dec 8, 2011 at 21:47, Matt Mills wrote:
>
> Also, Here's the python I've been using to reproduce:
> http://pastebin.com/at0FdzXp
> and the GDB backtrace after its locked up: http://pastebin.com/vx9cgSzp
>
The unlock() code, when the number of calls to unlock() reaches the same as
the num
On Thu, Dec 8, 2011 at 11:02 PM, Johnathan Corgan <
jcor...@corganenterprises.com> wrote:
> It's possible that whatever thread is being interrupted is somewhere in an
> uninterruptible state, though I'm not sure what that could be. If you
> could do an "info threads" in gdb, that might shed some
On Thu, Dec 8, 2011 at 22:15, Matt Mills wrote:
> With an even simpler version of the app (signal -> null sink) just running
> lock() unlock() in the loop it still locks up; using that version gives
> this info from gdb (info threads, and bt on both threads included)
>
> http://pastebin.com/YwTF
On Thu, Dec 8, 2011 at 11:15 PM, Matt Mills wrote:
> With an even simpler version of the app (signal -> null sink) just running
> lock() unlock() in the loop it still locks up; using that version gives
> this info from gdb (info threads, and bt on both threads included)
>
> http://pastebin.com/Yw
There are various kind of USRP series, USRP1, USRP2, E100, B100, and N200.
At a glance I could find some differences between them.
1. USB connection and Ethernet connection which determines the data rate
between the USRP and a PC.
(and it also makes difference when addressing USRP in GNU Radio.)
Hello,
Is there anyone seeing message like
Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",
when calling any GUI window?
I'm wondering that this message is caused by Ubuntu 11, or by GR 3.5.x
before I got this message, I've used Ubuntu 10 and GR 3.4.x
and I upgraded both OS
19 matches
Mail list logo
