Re: [Discuss-gnuradio] GRC 3.6 / 802.11 a/g test signal

2014-10-05 Thread Bastian Bloessl
Please, stay on the list. On 04 Oct 2014, at 18:20, Ernest Szczepaniak wrote: > Hi, > > we are talking about 'frame.bin' signal right? yes > Becouse my decoder says: > > Service: 'ok' > Protocol_version: 'Supported' > Type: 'Menagement' > Subtype: 'Probe Request' > To_DS: 'True' > From_DS: '

Re: [Discuss-gnuradio] Bypass work function

2014-10-05 Thread bob wole
Well, in my case the tx/rx would not be stationary, so the channel is not quite. -- Bob > If you can tolerate the stream stopping, use Power Squelch. Otherwise, > time to dive in and follow Tom's advice from May - disable the CMA taps > update loop when there's no signal. This whole idea assume

[Discuss-gnuradio] Win32 and gr-blocks/lib/stream_pdu_base.cc

2014-10-05 Thread Gisle Vanem
Since my previous message seems to be ignored, here is something simpler for you to comment on. In gr-blocks/lib/stream_pdu_base.cc, the read() and write() functions are used on sockets. This doesn't work well on Windows as you're probably aware. A simple fix is to has something like this at t

Re: [Discuss-gnuradio] GRC 3.6 / 802.11 a/g test signal

2014-10-05 Thread Ernest Szczepaniak
Greetings, Ok, got this. After some test's i think that the problem is with my descrambler (de-interleaver and Viterbi seems to be ok). Currently, im using Matlab's one provided by comm. toolbox. Is it correct to use 127-bit length pre-defined scrambling/descrambling seq? (i found it in 802.11 s

Re: [Discuss-gnuradio] TVRX2 and GRC

2014-10-05 Thread Daniel Marlow
On Oct 4, 2014, at 6:39 PM, Marcus D. Leech wrote: >> >> On Oct 3, 2014, at 7:30 PM, Marcus D. Leech wrote: >> >>> If you put your flow-graph itself (.grc file) somewhere, or attach it, we >>> can take a better look. >>> >>> What kind of comptuer? (OS, CPU/MEM specifics, etc). >>> >>> >>>

Re: [Discuss-gnuradio] Win32 and gr-blocks/lib/stream_pdu_base.cc

2014-10-05 Thread Josh Blum
On 10/05/2014 04:25 AM, Gisle Vanem wrote: > Since my previous message seems to be ignored, here is something simpler > for you to comment on. > > In gr-blocks/lib/stream_pdu_base.cc, the read() and write() functions > are used on sockets. This doesn't work well on Windows as you're > probably a

Re: [Discuss-gnuradio] GRC 3.6 / 802.11 a/g test signal

2014-10-05 Thread Bastian Bloessl
On 10/05/2014 01:37 PM, Ernest Szczepaniak wrote: Greetings, Ok, got this. After some test's i think that the problem is with my descrambler (de-interleaver and Viterbi seems to be ok). Currently, im using Matlab's one provided by comm. toolbox. Is it correct to use 127-bit length pre-defined s

Re: [Discuss-gnuradio] TVRX2 and GRC

2014-10-05 Thread Martin Braun
On 10/03/2014 11:23 PM, Daniel Marlow wrote: > As the second attached screen shot shows, however, the system does > not run properly, producing a string of "D's", with the FFT window > going dark. The warning that reads "Sensor 'lo_locked' failed to lock > within timeout on channel 0" se

Re: [Discuss-gnuradio] CGRAN down indefinitely, but hopefully not for long (want feedback)

2014-10-05 Thread Martin Braun
On 10/03/2014 12:44 AM, George Nychis wrote: > Marcus, I like the idea of an uber-repo with external submodules. That > would mean these submodules could link to a repo we could provide the > user, a repo they already have on github, or a repo they have on some > other external server. But in th

Re: [Discuss-gnuradio] CGRAN down indefinitely, but hopefully not for long (want feedback)

2014-10-05 Thread Bastian Bloessl
On 10/06/2014 08:21 AM, Martin Braun wrote: but I don't really like this except as a temporary/transition solution. Assume CGRAN really takes off and grows. Do you really want all OOTs out there in a single repo? What exactly is their logical connection, which would warrant them all being tied to