[Discuss-gnuradio] QAM modulation

2014-01-07 Thread Irfan Ullah 
hello all,
checking my mail subscribsion
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

[Discuss-gnuradio] gr-rds

2014-01-07 Thread Bastian Bloessl 

Hi all,

Clayton and I worked on the FM RDS project over the last weeks. I think 
that the receiving side is in a pretty good state now. It works well 
with the RTL SDR.


You can find a demo here:
www.youtube.com/watch?v=05i9C5lhorY

and the code here:
https://github.com/bastibl/gr-rds

There was also a talk about FM RDS at 30C3:
http://www.youtube.com/watch?v=R-2k6TMPMRo

Best,
Bastian

___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

[Discuss-gnuradio] QAM modulation

2014-01-07 Thread Irfan Ullah 
Hello all,
       is it possible to design our own block of QAM from small blocks like 
filters, synchronizers, adders etc.
regards,
Irfan Ulllah  ___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

[Discuss-gnuradio] PYBOMBs Testing

2014-01-07 Thread Dan CaJacob 
Hi,

I've been trying out pybombs again for building the latest gnuradio.  I
keep getting errors, but interestingly, if I just run the build again, I
always get a little further.  That seems strange.  Here's the tail of one
of the errors:

[ 65%] Building CXX object
gr-blocks/lib/CMakeFiles/gnuradio-blocks.dir/ctrlport_probe2_s_impl.cc.o
[ 65%] Building CXX object
gr-blocks/lib/CMakeFiles/gnuradio-blocks.dir/ctrlport_probe2_i_impl.cc.o
[ 65%] Building CXX object
gr-blocks/lib/CMakeFiles/gnuradio-blocks.dir/ctrlport_probe2_b_impl.cc.o
Linking CXX shared library libgnuradio-blocks-3.7.3git.so
[ 65%] Built target gnuradio-blocks
make: *** [all] Error 2
ERROR:root:PyBOMBS Make step failed for package (gnuradio) please see bash
output above for a reason (hint: look for the word Error)

If I can provide any clearer information, I will.

I am building on a 8-core Ubuntu laptop, but only letting the compiler use
4 cores.

Thanks!
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

[Discuss-gnuradio] ../../lib/libgnuradio-fcd-3.7.3git.so.0.0.0: undefined reference to `libusb_handle_events_completed'

2014-01-07 Thread ikjtel 
This error occurred when attempting to do "./pybombs install gnuradio" - after 
I manually overrode the recipe to build libusb-1.0.9 from source.  That made 
uhd happy [after I found it was still looking for the one in /usr/include/, and 
corrected that], and the process got 90% of the way done compiling gnuradio 
before the above linker error...  Tomorrow I'll fix using whatever trick is 
necessary, just wanted to post in case it's interesting to anyone.  :-)

Best

Max
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] version of libusb in pybombs

2014-01-07 Thread Marcus D. Leech 

pybombs is great!

Ran into a small error compiling uhd which access 'libusb_error_name' 
- that symbol was not added until libusb-1.0.9, but the pybombs recipe 
has "satisfy_deb: libusb-1.0-0-dev" - which doesn't define that 
symbol, so there's a compile error...


Should the recipe be changed to deb libusb-1.0-9-dev?

Best & Happy 2014 to All

Max


___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
The UHD codebase is supposed to deal with this itself, but the B200 code 
has a pending update so that this shouldn't be a problem, even for 
pre-1.0.9 libusb.  Not sure when that update will get posted.



--
Marcus Leech
Principal Investigator
Shirleys Bay Radio Astronomy Consortium
http://www.sbrac.org

___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] [USRP-users] USRP N210 Signal Phase Issue

2014-01-07 Thread Matt Ettus 
It could be the usrp digitally clipping, not the analyzer.

Matt


On Tue, Jan 7, 2014 at 5:17 PM, Jonathan Fox <31...@cardinalmail.cua.edu>wrote:

> On Tue, Jan 7, 2014 at 7:11 PM, Marcus D. Leech  wrote:
>
>>
>> Try reducing the amplitude to 0.7.  Another possibility is that your
>> computer can't keep up.  If you are using one of the standard programs, are
>> there U's printing in the terminal?
>>
>>  Matt
>>
>>  Also, what RF gain are you setting?  Does it exceed the maximum input
>> level of the spectrum analyser?
>>
>> Are you connected directly, or with an antenna?
>>
>>
>>
>> On Tue, Jan 7, 2014 at 3:03 PM, Jonathan Fox 
>> <31...@cardinalmail.cua.edu>wrote:
>>
>>>  A colleague and I are sending a simple signal in GNU Radio (sine wave,
>>> 1 MHz, amplitude of 1) to the USRP sink and have the center frequency at
>>> 500 MHz. The N210 USRP is hooked up to an Agilent spectrum analyzer. On the
>>> analyzer we are seeing a weird phenomena every two seconds. At first we see
>>> the carrier frequency and two sidebands from the sine wave (see attached
>>> normal.gif). Then after two seconds we get two bursts of multiple harmonics
>>> (see odd.gif).
>>>
>>>  The question is, why is this happening? Does the phase of the 1
>>> KHz signal become discontinuous before or after being sent to the USRP?
>>>
>>>  Thanks,
>>>
>>>  Jon Fox
>>>
>>> ___
>>> USRP-users mailing list
>>> usrp-us...@lists.ettus.com
>>> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
>>>
>>>
>>
>> ___
>> Discuss-gnuradio mailing 
>> listDiscuss-gnuradio@gnu.orghttps://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>>
>>
>>
>> --
>> Marcus Leech
>> Principal Investigator
>> Shirleys Bay Radio Astronomy Consortiumhttp://www.sbrac.org
>>
>>
>> ___
>> Discuss-gnuradio mailing list
>> Discuss-gnuradio@gnu.org
>> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>>
>
>
> I don't recall seeing any U's but I can recheck tomorrow. The gain on the
> USRP was set to -2. The USRP was connected directly with an SMA cable. The
> analyzer is an Agilent E4440A, the Analyzer is rated for at least 1 Watt on
> average, 100 Watt on a peak pulse (with the built-in attenuator in use).
> While I am not ruling out the maximum input I thought the N210 tops out at
> 0.5 Watts due to FCC regulations.
>
> Thanks
>
> Jon
>
> ___
> Discuss-gnuradio mailing list
> Discuss-gnuradio@gnu.org
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>
>
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] [USRP-users] USRP N210 Signal Phase Issue

2014-01-07 Thread Jonathan Fox 
On Tue, Jan 7, 2014 at 7:11 PM, Marcus D. Leech  wrote:

>
> Try reducing the amplitude to 0.7.  Another possibility is that your
> computer can't keep up.  If you are using one of the standard programs, are
> there U's printing in the terminal?
>
>  Matt
>
>  Also, what RF gain are you setting?  Does it exceed the maximum input
> level of the spectrum analyser?
>
> Are you connected directly, or with an antenna?
>
>
>
> On Tue, Jan 7, 2014 at 3:03 PM, Jonathan Fox 
> <31...@cardinalmail.cua.edu>wrote:
>
>>  A colleague and I are sending a simple signal in GNU Radio (sine wave,
>> 1 MHz, amplitude of 1) to the USRP sink and have the center frequency at
>> 500 MHz. The N210 USRP is hooked up to an Agilent spectrum analyzer. On the
>> analyzer we are seeing a weird phenomena every two seconds. At first we see
>> the carrier frequency and two sidebands from the sine wave (see attached
>> normal.gif). Then after two seconds we get two bursts of multiple harmonics
>> (see odd.gif).
>>
>>  The question is, why is this happening? Does the phase of the 1
>> KHz signal become discontinuous before or after being sent to the USRP?
>>
>>  Thanks,
>>
>>  Jon Fox
>>
>> ___
>> USRP-users mailing list
>> usrp-us...@lists.ettus.com
>> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
>>
>>
>
> ___
> Discuss-gnuradio mailing 
> listDiscuss-gnuradio@gnu.orghttps://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>
>
>
> --
> Marcus Leech
> Principal Investigator
> Shirleys Bay Radio Astronomy Consortiumhttp://www.sbrac.org
>
>
> ___
> Discuss-gnuradio mailing list
> Discuss-gnuradio@gnu.org
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>


I don't recall seeing any U's but I can recheck tomorrow. The gain on the
USRP was set to -2. The USRP was connected directly with an SMA cable. The
analyzer is an Agilent E4440A, the Analyzer is rated for at least 1 Watt on
average, 100 Watt on a peak pulse (with the built-in attenuator in use).
While I am not ruling out the maximum input I thought the N210 tops out at
0.5 Watts due to FCC regulations.

Thanks

Jon
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

[Discuss-gnuradio] version of libusb in pybombs

2014-01-07 Thread ikjtel 
pybombs is great!  

Ran into a small error compiling uhd which access 'libusb_error_name' - that 
symbol was not added until libusb-1.0.9, but the pybombs recipe has 
"satisfy_deb: libusb-1.0-0-dev" - which doesn't define that symbol, so there's 
a compile error...

Should the recipe be changed to deb  libusb-1.0-9-dev?

Best & Happy 2014 to All

Max___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] [USRP-users] USRP N210 Signal Phase Issue

2014-01-07 Thread Marcus D. Leech 


Try reducing the amplitude to 0.7.  Another possibility is that your 
computer can't keep up.  If you are using one of the standard 
programs, are there U's printing in the terminal?


Matt

Also, what RF gain are you setting?  Does it exceed the maximum input 
level of the spectrum analyser?


Are you connected directly, or with an antenna?




On Tue, Jan 7, 2014 at 3:03 PM, Jonathan Fox 
<31...@cardinalmail.cua.edu > wrote:


A colleague and I are sending a simple signal in GNU Radio (sine
wave, 1 MHz, amplitude of 1) to the USRP sink and have the center
frequency at 500 MHz. The N210 USRP is hooked up to an Agilent
spectrum analyzer. On the analyzer we are seeing a weird phenomena
every two seconds. At first we see the carrier frequency and two
sidebands from the sine wave (see attached normal.gif). Then after
two seconds we get two bursts of multiple harmonics (see odd.gif).

The question is, why is this happening? Does the phase of the 1
KHz signal become discontinuous before or after being sent to the
USRP?

Thanks,

Jon Fox

___
USRP-users mailing list
usrp-us...@lists.ettus.com 
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com



___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio



--
Marcus Leech
Principal Investigator
Shirleys Bay Radio Astronomy Consortium
http://www.sbrac.org

___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] [USRP-users] USRP N210 Signal Phase Issue

2014-01-07 Thread Matt Ettus 
Try reducing the amplitude to 0.7.  Another possibility is that your
computer can't keep up.  If you are using one of the standard programs, are
there U's printing in the terminal?

Matt


On Tue, Jan 7, 2014 at 3:03 PM, Jonathan Fox <31...@cardinalmail.cua.edu>wrote:

> A colleague and I are sending a simple signal in GNU Radio (sine wave, 1
> MHz, amplitude of 1) to the USRP sink and have the center frequency at 500
> MHz. The N210 USRP is hooked up to an Agilent spectrum analyzer. On the
> analyzer we are seeing a weird phenomena every two seconds. At first we see
> the carrier frequency and two sidebands from the sine wave (see attached
> normal.gif). Then after two seconds we get two bursts of multiple harmonics
> (see odd.gif).
>
> The question is, why is this happening? Does the phase of the 1 KHz signal
> become discontinuous before or after being sent to the USRP?
>
> Thanks,
>
> Jon Fox
>
> ___
> USRP-users mailing list
> usrp-us...@lists.ettus.com
> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
>
>
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] 3/4 and 5/6 Convolutional Codes

2014-01-07 Thread Aditya Dhananjay 
Dear All,

Here is my .fsm file for 5/6 rate convolutional coding. The two generators
are: 1+D2 and 1+D+D2. The puncturing pattern is: 10101 and 11010.

I'm sending this email in case anyone else needed the .fsm for a 5/6 rate
code. If you find any errors, please let me know.

Thanks.

best,
Aditya


--

32 8 64

0 4 2 6 1 5 3 7 0 4 2 6 1 5 3 7 0 4 2 6 1 5 3 7 0 4 2 6 1 5 3 7
0 4 2 6 1 5 3 7 0 4 2 6 1 5 3 7 0 4 2 6 1 5 3 7 0 4 2 6 1 5 3 7
0 4 2 6 1 5 3 7 0 4 2 6 1 5 3 7 0 4 2 6 1 5 3 7 0 4 2 6 1 5 3 7
0 4 2 6 1 5 3 7 0 4 2 6 1 5 3 7 0 4 2 6 1 5 3 7 0 4 2 6 1 5 3 7
0 4 2 6 1 5 3 7 0 4 2 6 1 5 3 7 0 4 2 6 1 5 3 7 0 4 2 6 1 5 3 7
0 4 2 6 1 5 3 7 0 4 2 6 1 5 3 7 0 4 2 6 1 5 3 7 0 4 2 6 1 5 3 7
0 4 2 6 1 5 3 7 0 4 2 6 1 5 3 7 0 4 2 6 1 5 3 7 0 4 2 6 1 5 3 7
0 4 2 6 1 5 3 7 0 4 2 6 1 5 3 7 0 4 2 6 1 5 3 7 0 4 2 6 1 5 3 7

0 1 3 2 5 4 6 7 14 15 13 12 11 10 8 9 52 53 55 54 49 48 50 51 58 59 57 56
63 62 60 61
0 1 3 2 5 4 6 7 14 15 13 12 11 10 8 9 52 53 55 54 49 48 50 51 58 59 57 56
63 62 60 61
48 49 51 50 53 52 54 55 62 63 61 60 59 58 56 57 4 5 7 6 1 0 2 3 10 11 9 8
15 14 12 13
48 49 51 50 53 52 54 55 62 63 61 60 59 58 56 57 4 5 7 6 1 0 2 3 10 11 9 8
15 14 12 13
40 41 43 42 45 44 46 47 38 39 37 36 35 34 32 33 28 29 31 30 25 24 26 27 18
19 17 16 23 22 20 21
40 41 43 42 45 44 46 47 38 39 37 36 35 34 32 33 28 29 31 30 25 24 26 27 18
19 17 16 23 22 20 21
24 25 27 26 29 28 30 31 22 23 21 20 19 18 16 17 44 45 47 46 41 40 42 43 34
35 33 32 39 38 36 37
24 25 27 26 29 28 30 31 22 23 21 20 19 18 16 17 44 45 47 46 41 40 42 43 34
35 33 32 39 38 36 37



On Mon, Jan 6, 2014 at 7:25 PM, Aditya Dhananjay wrote:

> Dear All,
>
> Does anyone have .fsm files for 3/4 and 5/6 rate convolutional codes?
>
> (Or alternatively, the state transition matrix and output matrix for these
> codes?)
>
> Thanks for your help in advance!
>
> Best,
> Aditya
>
>
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] [USRP-users] Model name of different components of USRP radio front ends

2014-01-07 Thread Nazmul Islam 
Thanks a lot, Doug. I appreciate your reply.


On Tue, Jan 7, 2014 at 4:25 PM, Doug Knabe  wrote:

> On 01/07/2014 03:02 PM, Nazmul Islam wrote:
>
>> I am working on how channel scheduling algorithm influences system level
>> power consumption in software defined radios. I need the power consumption
>> of different components of SDR front ends.
>>
>> Is there any document that lists the model names of the following
>> components in USRP;
>>
>> 1. ADC
>>
>> 2. DAC
>>
>> 3. Analog filters at different stages of the radio front end chain
>>
>> 4. VCO
>>
>> 5. Mixer
>>
>> 6. Programmmable amplifier, etc.
>>
>> If I get the model names of these components, I can look at the
>> individual data sheets and find the corresponding power measurement.
>>
>> Any feedback will be highly appreciated.
>>
>> Thanks,
>>
>> Nazmul
>>
>>
>> --
>> Muhammad Nazmul Islam
>>
>> Graduate Student
>> Electrical & Computer Engineering
>> Wireless Information & Networking Laboratory
>> Rutgers, USA.
>>
>>  Muhammad,
>
> Schematics for USRP are located here. Pick the model of interest.
> http://code.ettus.com/redmine/ettus/projects/public/documents
>
> Cheers,
> Doug Knabe
>



-- 
Muhammad Nazmul Islam

Graduate Student
Electrical & Computer Engineering
Wireless Information & Networking Laboratory
Rutgers, USA.
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] [USRP-users] Model name of different components of USRP radio front ends

2014-01-07 Thread Doug Knabe 

On 01/07/2014 03:02 PM, Nazmul Islam wrote:
I am working on how channel scheduling algorithm influences system 
level power consumption in software defined radios. I need the power 
consumption of different components of SDR front ends.


Is there any document that lists the model names of the following 
components in USRP;


1. ADC

2. DAC

3. Analog filters at different stages of the radio front end chain

4. VCO

5. Mixer

6. Programmmable amplifier, etc.

If I get the model names of these components, I can look at the 
individual data sheets and find the corresponding power measurement.


Any feedback will be highly appreciated.

Thanks,

Nazmul


--
Muhammad Nazmul Islam

Graduate Student
Electrical & Computer Engineering
Wireless Information & Networking Laboratory
Rutgers, USA.


Muhammad,

Schematics for USRP are located here. Pick the model of interest.
http://code.ettus.com/redmine/ettus/projects/public/documents

Cheers,
Doug Knabe

___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

[Discuss-gnuradio] Model name of different components of USRP radio front ends

2014-01-07 Thread Nazmul Islam 
I am working on how channel scheduling algorithm influences system level
power consumption in software defined radios. I need the power consumption
of different components of SDR front ends.

Is there any document that lists the model names of the following
components in USRP;

1. ADC

2. DAC

3. Analog filters at different stages of the radio front end chain

4. VCO

5. Mixer

6. Programmmable amplifier, etc.

If I get the model names of these components, I can look at the individual
data sheets and find the corresponding power measurement.

Any feedback will be highly appreciated.

Thanks,

Nazmul


-- 
Muhammad Nazmul Islam

Graduate Student
Electrical & Computer Engineering
Wireless Information & Networking Laboratory
Rutgers, USA.
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] Passing a USRP pointer

2014-01-07 Thread Tom Rondeau 
On Tue, Jan 7, 2014 at 12:21 PM, Dan CaJacob  wrote:
> Hey Tom,
>
> Here's some more detail into our problem.
>
> When running the flowgraph, we get the following error:
>
> File "/usr/local/lib/python2.7/dist-packages/sq/sq_swig.py", line 679, in
> make
> return _sq_swig.usrp_pa_control_make(*args, **kwargs)
> TypeError: in method 'usrp_pa_control_make', argument 1 of type
> 'gr::uhd::usrp_sink::sptr'
>
> When setting up a FG, the pa-control block accepts a reference to the
> downstream UHD sink.
>
> I have attached the specific block source.
>
> Thanks!
>
> Very Respectfully,
>
> Dan CaJacob

It's probably the difference between a gr::uhd::usrp_sink and a
gr::uhd::usrp_sink_impl.

A safer way to handle this might be to use the new(ish) block_registry
that we implemented to handle the message passing infrastructure. You
can get a basic_block_sptr from global_block_registry.block_lookup;
you should then be able to cast this to a usrp_sink_sptr. You'll pass
it a PMT symbol containing the alias name of the UHD sink itself.

Take a look at basic_block.cc for a look at how the
global_block_registry is used. I've not done exactly this before, so
it might not go completely smoothly, and I'd be interested in your
experience.

In general, this sounds like something more appropriately implemented
as a message, though, but that would mean changing the gr-uhd code.
Having a message handler for the GPIO stuff would probably be useful
if done generically enough.

Tom




> On Mon, Jan 6, 2014 at 11:25 AM, Dan CaJacob  wrote:
>>
>> Thanks Tom,
>>
>> No problem.  I hope you and the rest of the community had relaxing
>> holidays!  I hope to have some better info for you by tomorrow, if not
>> before.
>>
>> Another way to look at this is: does it make sense to keep doing things
>> this way?  Is there a better way to reference the downstream USRP and toggle
>> the IO?  I could imagine an async message stream or specific stream-tags,
>> but both would probably require changes to the actual UHD sinks.  I'm not
>> sure our use case is generic enough to warrant that.
>>
>> Very Respectfully,
>>
>> Dan CaJacob
>>
>>
>> On Mon, Jan 6, 2014 at 10:46 AM, Tom Rondeau  wrote:
>>>
>>> On Sat, Dec 21, 2013 at 6:29 PM, Dan CaJacob 
>>> wrote:
>>> > We are upgrading some of our custom blocks for 3.7 and have run into a
>>> > snag.
>>> > Our 3.6 era blocks included one that PTTed an external amplifier based
>>> > on
>>> > stream tags.  The IO was generated from the extra GPIO available on the
>>> > WBX.
>>> > One of the inputs to the block was a reference to the USRP sink
>>> > downstream
>>> > in the FG.  The block then calls the necessary methods to enable and
>>> > disable
>>> > the GPIO.  Everything worked nicely, but when we ported our blocks to
>>> > 3.87,
>>> > there seemed to be a problem with this.  I did not personally do the
>>> > testing, so I don't have the exact error, but I can probably re-create
>>> > it
>>> > given some time.
>>> >
>>> > I started the porting of the blocks myself and did notice that getting
>>> > the
>>> > pointer to a USRP object had changed.  But the blocks built without
>>> > error
>>> > when updated appropriately.
>>> >
>>> > Is there anything in principle that would prevent this from working in
>>> > 3.7?
>>> > Or, is there a better approach to controlling the WBX GPIO based on
>>> > stream
>>> > tags that we should consider?
>>> >
>>> > I apologize for the vagueness on the actual error.  I'll try to
>>> > reproduce it
>>> > myself in the meantime.
>>> >
>>> > I can probably post the code for the PTT-controlling block if that
>>> > would be
>>> > any help.
>>> >
>>> > Very Respectfully,
>>> >
>>> > Dan CaJacob
>>>
>>>
>>> Hi Dan,
>>>
>>> Sorry for the silence. Partly due to the holidays, partly due to me
>>> not having a good answer for you. Most likely, your problem is related
>>> in some way to the public/private implementations that we are
>>> enforcing in 3.7 now. If you have more information or have figured
>>> this out, let us know and we can see where we need to go from here.
>>>
>>> Tom
>>
>>
>

___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

[Discuss-gnuradio] Pybombs warning: Do not forget to define "makewidth" after updating pybombs from older version.

2014-01-07 Thread M Dammer 
I just updated pybombs to the latest git version by using git remote update
git pull. A new environment variable "makewidth" was introduced recently
that - if not defined - leads to an infinite number of make processes
been started and the machine freezing because of out of memory errors.
So check your config.dat if it contains a line like
makewidth=4
if not - add it or you may have the same bad experiences I just had.
I already filed an issue on the Pybombs issuetracker.

Happy compiling in a Happy New Gnuradio Year
Mark



___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

[Discuss-gnuradio] Fw: packet encoder purpose

2014-01-07 Thread Irfan Ullah 





On Tuesday, January 7, 2014 2:54 PM, Irfan Ullah  wrote:
 
Hello everyone,
              can someone tell me the purpose of packet encoder/decoder?
Regards,
Irfan Ullah
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

[Discuss-gnuradio] packet encoder purpose

2014-01-07 Thread Irfan Ullah 
Hello everyone,
              can someone tell me the purpose of packet encoder/decoder?
Regards,
Irfan Ullah___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

[Discuss-gnuradio] FOSDEM: Reminder and call for volunteers

2014-01-07 Thread Martin Braun 
Hi everyone,

a quick reminder regarding the upcoming FOSDEM: There is a whole track
dedicated to SDR, and FOSDEM is free (both as in beer as in speech)! GNU
Radio is a big part of this, but so are other interesting SDR projects.

Check out our track's website and the agenda:
http://gnuradio.org/redmine/projects/gnuradio/wiki/FOSDEM14
https://fosdem.org/2014/schedule/track/software_defined_radio/

== Can you help? ==

We are still looking for volunteers to help with the A/V system (*all*
presentations shall be recorded this year, but we need people to handle
the recording system). We already have a couple of volunteers, but we'd
like to make sure our volunteers can take it in turns to supervise the
recording, and get some time off to go and see stuff themselves.

If you're interested, please contact me off-list. Thanks!

Martin

___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio