Re: [Discuss-gnuradio] Delayed Repitition In GRC

[sreeraj r]

Hi Sumit,

You could also pad enough zeros to your .bin file or use Bastian's gr-foo
[1] blocks to get the job done (burst_tagger + packet_pad?).

[1] https://github.com/bastibl/gr-foo

Regards
Sreeraj Rajendran

On Tue, Sep 13, 2016 at 5:45 PM, Marcus Müller 
wrote:

> Hi Sumit,
>
> what about using a patterned interleaver?
>
> Best regards,
>
> Marcus
>
>
> On 09/13/2016 07:29 AM, sumitstop wrote:
> > Hello,
> >
> > I am playing back a data using file source (file recorded from MATLAB and
> > converted to .bin) in gnuradio-companion and feeding it to USRP.
> >
> > I have checked "Repeat : Yes" How can I introduce some delay/idle
> time
> > between the repetitions.
> >
> > TIA
> > Sumit
> >
> >
> >
> > --
> > View this message in context: http://gnuradio.4.n7.nabble.
> com/Delayed-Repitition-In-GRC-tp61461.html
> > Sent from the GnuRadio mailing list archive at Nabble.com.
> >
> > ___
> > 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 mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] PSK31 (from audio to radio)

[Ron Economos]

I have an alternative flow graph. It's based on the multi_tx.grc flow 
graph in https://github.com/argilo/sdr-examples. The osmocom Sink is set 
up for a bladeRF, so be sure to change that for hackRF. The message in 
the Vector Source block in "This is W6RZ testing." with a trailing line 
feed.


http://www.w6rz.net/psk31.grc

Ron

On 09/13/2016 11:11 PM, Cinaed Simson wrote:

On 09/10/2016 05:19 PM, pen tester wrote:

Thanks Cinaed for your response.

For everything up to the multiply on the TX side - this is actually from
a working example that TXs using an audio card [1]. So just for a proof
of concept I would like to leave that as-is and just append on TX over
Osmocom Sink. Happy to look at simplifying later, just wanted to get POC
for PSK31 over radio for now on the transmit and receive.

Also thanks for spotting my Freq mistake too.

My plan now is to use the fldigi app for testing the rx side while I try
and make the rx side work - just figuring out how to write to a wav file
sink that is accepted by fldigi too... and trying to find some TX examples.

[1] https://github.com/tkuester/gr-psk31/
 (examples/psk31_tx.grc)


The output of the psk31_tx.grc example doesn't appear to be either BPSK
or QPSK - both which should have a constant envelope  - or at least
approximately constant.

Instead, the output looks like a beat signal of 2 signals close in
frequency - resulting in an envelope varying in amplitude.

I'm presuming psk31 implies BPSK with a low baud rate - 31 symbols per
second.

I may be missing something.



On 10 September 2016 at 11:40, pen tester mailto:testerofp...@gmail.com>> wrote:

 Hi,
Still playing around and I have a question about the value which
 should go in the Polyphase Resampler on the tx side please. Any
 advice on the AM rx too would be helpful :-)

 Transmit

   * Simply trying make the working PSK31 audio tx to tx over HackRF
 instead using [1] and updates from Tim's response
   * Screenshot: http://pasteboard.co/1dLjHxMAU.png
 


 Receive

   * Simply trying to make the working PSK31 audio rx work using a
 RTLSDR instead based on [2]
   * The first line is an attempt to take in the AM signal and just
 pass it on to [2]
   * For the AM rx, I used [3] as a guide
   * Screenshot: http://pasteboard.co/1dLZWV9mv.png
 


 [1] https://github.com/tkuester/gr-psk31/
  (examples/psk31_tx.grc)
 [2] https://github.com/tkuester/gr-psk31/
  (examples/psk31_rx.grc)
 [3] https://www.csun.edu/~skatz/katzpage/sdr_project/sdr/grc_tutorial3.pdf
 

 On 6 September 2016 at 05:49, pen tester mailto:testerofp...@gmail.com>> wrote:

 Tim,
Yes, your graphs are really useful :-) Thank you for
 responding in such detail!

Here is what I am up to:

 Transmit side:

   * I made your changes to your transmit graph [1]
   * All the changes were fine but I was confused about the use
 of the Polyphase Resampler as I could not get the values to
 work without underflows when executing i.e. "..."
   * So instead (this is probably wrong) I tried using a Rational
 Resampler with an Interpolation of 1e6 and a Decimation of 48e3.
   * Updated version: http://pasteboard.co/hmyGOGTE4.png
 
   * Either way, the tx graph looks healthier - just need some
 advice on the resampler perhaps?


 Receive side:

   * I am using the start of this receive graph [2] as it was
 using radio rx already
   * and just modifying the demod portion to be more like your rx
 graph
   * Updated version: http://pasteboard.co/hmzrMBAIi.png
 
   * I also need advice from anyone who could point in the right
 direction on the AM rx side please?


 [1] https://github.com/tkuester/gr-psk31/
  (examples/psk31_tx.grc)
 [2] https://github.com/argilo/sdr-examples
  (tutorial/6_psk.grc)
 [3] https://github.com/tkuester/gr-psk31/
  (examples/psk31_rx.grc)

 On 4 September 2016 at 12:33, Tim K mailto:tpkues...@gmail.com>> wrote:

 Hey hey!

 Glad to see someone using this. (And that it's apparently
 still working! Goodness... I need to clean this up...)

 I'm giving advice freehand right now, as I don't have my
 radios with me to test this. 

[Discuss-gnuradio] Could not connect to ControlPort

[Ihab Zine]

Hi ,

after many tries i thinks i was able to install Apache thrift.  now my
problem is when i run the command

 gr-perf-monitorx  xxx.xxx.x.xxx  9090

got the folllowing error:

Could not connect to ControlPort endpoint at xxx.xxx.x.xxx:9090.

Exception socket.error: (32, 'Broken pipe') in > ignored

so, do i need to run a server? if  i do where can i find it ? what command
should I use? Or am i missing some steps?

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

Re: [Discuss-gnuradio] Could not connect to ControlPort

[Marcus Müller]

Did you enable ctrlport in  your gnuradio config?


On 09/14/2016 05:45 AM, Ihab Zine wrote:
> Hi , 
>
> after many tries i thinks i was able to install Apache thrift.  now my
> problem is when i run the command 
>
>  gr-perf-monitorx  xxx.xxx.x.xxx  9090 
>
> got the folllowing error:
>
> Could not connect to ControlPort endpoint at xxx.xxx.x.xxx:9090.
>
> Exception socket.error: (32, 'Broken pipe') in  ThriftRadioClient.__del__ of
>  0x7f1cf4f1bc68>> ignored
>
> so, do i need to run a server? if  i do where can i find it ? what
> command should I use? Or am i missing some steps?
>
> Thanks 
> Ihab 
>
>
>
> ___
> 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] Could not connect to ControlPort

[Ihab Zine]

yes i did as you see, ** gr-ctrlport, ** * * thrift*

##
-- # Gnuradio enabled components
-- ##
--   * python-support
--   * testing-support
--   * volk
--   * doxygen
--   * gnuradio-runtime
*--   * gr-ctrlport*
*--   * * thrift*
--   * gr-blocks
--   * gnuradio-companion
--   * gr-fft
--   * gr-filter
--   * gr-analog
--   * gr-digital
--   * gr-audio
--   * * alsa
--   * * oss
--   * gr-channels
--   * gr-noaa
--   * gr-pager
--   * gr-qtgui
--   * gr-trellis
--   * gr-uhd
--   * gr-utils
--   * gr-vocoder
--   * gr-fcd
--   * gr-wxgui
-- 


but i have noticed something when i run   gnuradio-config-info
--enabled-components. I don't see thrift there but it is installed


python-support;testing-support;volk;doxygen;gnuradio-runtime;*gr-ctrlport*;gr-blocks;gnuradio-companion;gr-fft;gr-filter;gr-analog;gr-digital;gr-audio;*
alsa;*
oss;gr-channels;gr-noaa;gr-pager;gr-qtgui;gr-trellis;gr-uhd;gr-utils;gr-vocoder;gr-fcd;gr-wxgui

ihab


On 14 September 2016 at 12:45, Ihab Zine  wrote:

> Hi ,
>
> after many tries i thinks i was able to install Apache thrift.  now my
> problem is when i run the command
>
>  gr-perf-monitorx  xxx.xxx.x.xxx  9090
>
> got the folllowing error:
>
> Could not connect to ControlPort endpoint at xxx.xxx.x.xxx:9090.
>
> Exception socket.error: (32, 'Broken pipe') in  ThriftRadioClient.__del__ of 
>  instance at 0x7f1cf4f1bc68>> ignored
>
> so, do i need to run a server? if  i do where can i find it ? what command
> should I use? Or am i missing some steps?
>
> Thanks
> Ihab
>
>
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

[Discuss-gnuradio] RFC: Updates to GNU Radio Wiki

[Martin Braun]

Hi everyone,

as you may remember, we had some announcements regarding the GNU Radio
website a while back. The plan was to create a new front-end website
outside of the wiki, that looks nice and can host static content etc.,
and then move away from Redmine and replace the issue tracker, wiki etc.

The former part has been implemented for quite a while, thanks to Ben
Hilburn, and we now have a nice orange website with a blog etc. However,
as you may have noticed, we're still on Redmine. There's several reasons
for this: Firstly, and most importantly, we don't have a lot of
volunteers on the web front, so pretty much all of the work falls into
the hands of Johnathan Corgan, who is also CTO of GNU Radio and our
chief architect. The second, and more subtle, issue is that we're not
entirely sure what the best solution would be.

Currently, we're using a mix of github and Redmine. Already, that's
confusing to some people, because we have our issues on Redmine, but
pull requests on github. So, here's a couple of options we could go with
in the future:

== Do nothing. Keep Redmine and github as-is. ==
Pros:
* Costs us no time. We already have it.
Cons:
* Redmine is annoying to maintain.
* The Redmine/github split is confusing.

== Move everything to github, including the wiki. ==
Pros:
* Costs us little time. We only need to export the issues and wiki pages
to github and then we can nuke Redmine.
* github will run the website for us.
Cons:
* The github wiki is not too popular. The page is cluttered, and people
have raised (valid) concerns about all of our content being hosted by
some random company whom we happen to trust with our code.

== Move everything to github, except the wiki. ==
To clarify: Bugs/Issues, pull requests, milestones, code reviews are
done on github.
Pros:
* Easy transition from what we have right now.
* Issues and pull requests are in the same place.
Cons:
* We still need a decision about which wiki software to use -- keep
Redmine, or switch to something else (e.g. gitlab)?

== Move everything to gitlab, which we host ourself ==
Pros:
* We have full control over everything.
Cons:
* We have full control over everything. Lots of work!



This Friday, I will have a discussion about this with whoever is
interested at the GRCon developer's day, but I'd like to give people who
are not in Boulder this week a chance to voice their opinions (the final
decision will be made by Johnathan and myself).

Note that there could be good suggestions outside of the ones listed
above, and the final solution could also be between one of those. I'm
interested to hear all of them!

Cheers,
Martin

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

Re: [Discuss-gnuradio] Could not connect to ControlPort

[Marcus Müller]

ah, sorry, I meant the run-time config (~/.gnuradio/conf,
/etc/gnuradio/...)


On 09/14/2016 09:53 AM, Ihab Zine wrote:
> yes i did as you see, ** gr-ctrlport, ** * * thrift*
>
> ##
> -- # Gnuradio enabled components 
> -- ##
> --   * python-support
> --   * testing-support
> --   * volk
> --   * doxygen
> --   * gnuradio-runtime
> *--   * gr-ctrlport*
> *--   * * thrift*
> --   * gr-blocks
> --   * gnuradio-companion
> --   * gr-fft
> --   * gr-filter
> --   * gr-analog
> --   * gr-digital
> --   * gr-audio
> --   * * alsa
> --   * * oss
> --   * gr-channels
> --   * gr-noaa
> --   * gr-pager
> --   * gr-qtgui
> --   * gr-trellis
> --   * gr-uhd
> --   * gr-utils
> --   * gr-vocoder
> --   * gr-fcd
> --   * gr-wxgui
> -- 
>
>
> but i have noticed something when i run   gnuradio-config-info
> --enabled-components. I don't see thrift there but it is installed
>
>
> python-support;testing-support;volk;doxygen;gnuradio-runtime;*gr-ctrlport*;gr-blocks;gnuradio-companion;gr-fft;gr-filter;gr-analog;gr-digital;gr-audio;*
> alsa;*
> oss;gr-channels;gr-noaa;gr-pager;gr-qtgui;gr-trellis;gr-uhd;gr-utils;gr-vocoder;gr-fcd;gr-wxgui
>
> ihab
>
>
> On 14 September 2016 at 12:45, Ihab Zine  > wrote:
>
> Hi , 
>
> after many tries i thinks i was able to install Apache thrift.
>  now my problem is when i run the command 
>
>  gr-perf-monitorx  xxx.xxx.x.xxx  9090 
>
> got the folllowing error:
>
> Could not connect to ControlPort endpoint at xxx.xxx.x.xxx:9090.
>
> Exception socket.error: (32, 'Broken pipe') in  ThriftRadioClient.__del__ of
>  at 0x7f1cf4f1bc68>> ignored
>
> so, do i need to run a server? if  i do where can i find it ? what
> command should I use? Or am i missing some steps?
>
> Thanks 
> Ihab 
>
>
>
>
> ___
> 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] QT Gui Frequency Sink Busport Flowgraph Bug

[Chris Evans]

As per:

https://lists.gnu.org/archive/html/discuss-gnuradio/2015-02/msg00054.html

It seems there was an issue with the way the QT GUI components in the
flowgraph handled displaying bus connections (resulting in always n+1,
where n == inputs).

Any chance there is a fix out there? Or some manual edit I could make to
rectify this?
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

[Discuss-gnuradio] How to Transmit Orthogonal Waveforms

[Pavan Yedavalli]

Hi,

Apologies for sending this again. I want to transmit orthogonal waveforms
from my USRP N210, and I have tried to mimic the example from ofdm_tx.py.
One thing is that I don't need these signals to have any header, CRC, or
any stuff involved with an actual OFDM signal. I just need them to be
offset square pulses, basically (box functions that are offset).

Having said that, I made it in such a way that I connect a random source
block->digital chunks to symbols->digital ofdm carrier allocator->fft->ofdm
cyclic prefix->blocks multiply const->blocks throttle->USRP sink.

I need to adjust these waveforms so that whenever I call it, each
sequential one is orthogonal to the previous ones, but I am not sure
whether I am going about it the right way. As I mentioned above, really all
I want is to be able to transmit a square pulse and offset it every time by
the length of the square so that the sequential ones are orthogonal. Maybe
there is an easier way using our standard CONST OR SQUARE waveforms. Any
help would be appreciated. Thank you.

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

Re: [Discuss-gnuradio] How to Transmit Orthogonal Waveforms

[Marcus Müller]

Really quick remark while I finish reading your mail:
NEVER use throttle together with hardware! It is only meant to slow down
simulations on average, and MUST NOT be used with hardware.


Best regards,

Marcus

On 09/14/2016 10:55 AM, Pavan Yedavalli wrote:
> Hi,
>
> Apologies for sending this again. I want to
> transmit orthogonal waveforms from my USRP N210, and I have tried to
> mimic the example from ofdm_tx.py. One thing is that I don't need
> these signals to have any header, CRC, or any stuff involved with an
> actual OFDM signal. I just need them to be offset square pulses,
> basically (box functions that are offset).
>
> Having said that, I made it in such a way that I connect a random
> source block->digital chunks to symbols->digital ofdm carrier
> allocator->fft->ofdm cyclic prefix->blocks multiply const->blocks
> throttle->USRP sink. 
>
> I need to adjust these waveforms so that whenever I call it, each
> sequential one is orthogonal to the previous ones, but I am not sure
> whether I am going about it the right way. As I mentioned above,
> really all I want is to be able to transmit a square pulse and offset
> it every time by the length of the square so that the sequential ones
> are orthogonal. Maybe there is an easier way using our standard CONST
> OR SQUARE waveforms. Any help would be appreciated. Thank you.
>
> -- 
> Pavan
>
>
> ___
> 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] remove_item_tag()

[devin kelly]

Hello,

I'm interested in editing stream tags.  So far my approach is to read the
tag I'm interested in, copy the value, remove the tag, edit the tag value
and then add the new tag with add_item_tag.

In looking at the GR documentation, the function remove_item_tag says that
the function will be deprecated as of GR 3.8.  What will replace this
function, or what should my GR 3.8 approach be?

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

Re: [Discuss-gnuradio] remove_item_tag()

[Martin Braun]

You shouldn't use this at all. If you want to modify tags in your block,
you set the tag propagation policy to "none", and then simply write the
updated tag value to the output.

Cheers,
M

On 09/14/2016 11:34 AM, devin kelly wrote:
> Hello,
> 
> I'm interested in editing stream tags.  So far my approach is to read
> the tag I'm interested in, copy the value, remove the tag, edit the tag
> value and then add the new tag with add_item_tag.
> 
> In looking at the GR documentation, the function remove_item_tag says
> that the function will be deprecated as of GR 3.8.  What will replace
> this function, or what should my GR 3.8 approach be?
> 
> Thanks,
> Devin
> 
> 
> ___
> 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] How to Transmit Orthogonal Waveforms

[Pavan Yedavalli]

Hi,

Preliminarily, I think I may have found what I needed in the vector source
block and making the vector a numpy array of 0s and 1s (where I want my
rectangular pulse). I will keep the list posted. Thanks.

On Wed, Sep 14, 2016 at 9:55 AM, Pavan Yedavalli 
wrote:

> Hi,
>
> Apologies for sending this again. I want to transmit orthogonal waveforms
> from my USRP N210, and I have tried to mimic the example from ofdm_tx.py.
> One thing is that I don't need these signals to have any header, CRC, or
> any stuff involved with an actual OFDM signal. I just need them to be
> offset square pulses, basically (box functions that are offset).
>
> Having said that, I made it in such a way that I connect a random source
> block->digital chunks to symbols->digital ofdm carrier allocator->fft->ofdm
> cyclic prefix->blocks multiply const->blocks throttle->USRP sink.
>
> I need to adjust these waveforms so that whenever I call it, each
> sequential one is orthogonal to the previous ones, but I am not sure
> whether I am going about it the right way. As I mentioned above, really all
> I want is to be able to transmit a square pulse and offset it every time by
> the length of the square so that the sequential ones are orthogonal.
> Maybe there is an easier way using our standard CONST OR SQUARE waveforms.
> Any help would be appreciated. Thank you.
>
> --
> Pavan
>



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