Re: [Discuss-gnuradio] Scheduling a block even with no input items RE: Flow graph blocking when doing 2x1 transmission

2014-06-04 Thread Activecat
On Wed, Jun 4, 2014 at 7:10 PM, David Halls wrote: > Activecat, > In fact my horrible hack doesn't work properly. Once items start arriving > at Payload TD Tx 2, they still don't arrive as 'consistently' (for want of > a better word), as those from the Noise Source block, and thus zeros are > ins

Re: [Discuss-gnuradio] tx_time tag accuraccy

2014-06-04 Thread bob wole
Sorry for not stating the hardware earlier. I am using USRP N210, with RFX2400 and WBX boards. -- Bob On Wed, Jun 4, 2014 at 11:07 PM, Marcus Leech wrote: > I don't know the detailed answer, but any such answer will depend very > much on which USRP hardware you're talking about. > > One of the

[Discuss-gnuradio] GNu radio examples not running

2014-06-04 Thread jason sam
Hi All, When i try to run any of built in examples (in .py form) with GRC,i get the following error: Error: /usr/local/share/gnuradio/examples/audio/audio_fft.py:1:1:FATAL:PARSER:ERR_DOCUMENT_EMPTY: Start tag expected, '<' not found An example of such file is as attached. #!/usr/bin/python #!/usr

[Discuss-gnuradio] Doxygen documentation

2014-06-04 Thread jason sam
How can i configure GNU Radio Companion 3.7.3 with Doxygen so taht i can view the blocks' documentation from inside GRC?I have Doxygen installed but its not configured with GRC. Regards, Ali ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https

Re: [Discuss-gnuradio] signal level

2014-06-04 Thread jason sam
Hi Tom, Can you tell what is the constraint for USRP B210? On Thu, Jun 5, 2014 at 8:13 AM, Tom McDermott wrote: > Hi Ali - some sinks care about the amplitude, and others do not. > > For example, the instruments built into gnuradio (Scope, Frequency > display, etc.) can examine a signal of almo

Re: [Discuss-gnuradio] signal level

2014-06-04 Thread Tom McDermott
Hi Ali - some sinks care about the amplitude, and others do not. For example, the instruments built into gnuradio (Scope, Frequency display, etc.) can examine a signal of almost any amplitude within floating-point range because you can adjust the display scale factor. However other sinks, such as

[Discuss-gnuradio] signal level

2014-06-04 Thread jason sam
Hi, In GRC is it necessary that we give a signal to any sink having an amplitude greater than 1? Regards, Ali ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] Getting overflows at 50 Msps (not sure why)

2014-06-04 Thread Ron Economos
On 6/4/2014 2:16 PM, Orin Lincoln wrote: Hello, I am trying to get samples from a B200 at 50 Msps into GNU Radio. The UHD benchmark_rate tool receives at 50 Msps without any overflows detected. My GNU Radio flowgraph is simply a USRP source connected to a null sink, and I'm still getting over

Re: [Discuss-gnuradio] Getting overflows at 50 Msps (not sure why)

2014-06-04 Thread Tom Tsou
On Wed, Jun 4, 2014 at 5:16 PM, Orin Lincoln wrote: > I am trying to get samples from a B200 at 50 Msps into GNU Radio. The UHD > benchmark_rate tool receives at 50 Msps without any overflows detected. My > GNU Radio flowgraph is simply a USRP source connected to a null sink, and > I'm still getti

Re: [Discuss-gnuradio] Getting overflows at 50 Msps (not sure why)

2014-06-04 Thread Marcus D. Leech
On 06/04/2014 05:16 PM, Orin Lincoln wrote: Hello, I am trying to get samples from a B200 at 50 Msps into GNU Radio. The UHD benchmark_rate tool receives at 50 Msps without any overflows detected. My GNU Radio flowgraph is simply a USRP source connected to a null sink, and I'm still getting o

[Discuss-gnuradio] Getting overflows at 50 Msps (not sure why)

2014-06-04 Thread Orin Lincoln
Hello, I am trying to get samples from a B200 at 50 Msps into GNU Radio. The UHD benchmark_rate tool receives at 50 Msps without any overflows detected. My GNU Radio flowgraph is simply a USRP source connected to a null sink, and I'm still getting overflows. I've tried expanding the min_outpu

[Discuss-gnuradio] Call for Volunteers - GNU Radio Website

2014-06-04 Thread John Malsbury
Hello list! It's been a few weeks since I've been connected/active on the list. After talking things over Tom and others in the community it is apparent that the GNU Radio "home site" is becoming more critical. Here's some background: Sometime around GR Con 13, it became evident that the GNU R

Re: [Discuss-gnuradio] tx_time tag accuraccy

2014-06-04 Thread Marcus Leech
I don't know the detailed answer, but any such answer will depend very much on which USRP hardware you're talking about.   One of the R&D people who deals with the FPGA codebase may be able to give a precise answer, given stated hardware.       on Jun 04, 2014, bob wole wrote: Marcus! Thanks fo

Re: [Discuss-gnuradio] tx_time tag accuraccy

2014-06-04 Thread bob wole
Marcus! Thanks for you comment. I think that USRP transmit FIFO is at the start of the DSP chain in FPGA i.e it is prior to both of the interpolation filters? right? I am not talking about when the burst will be over the air, I want to know when the first sample of the burst will leave the transm

Re: [Discuss-gnuradio] [USRP-users] tx_time tag accuraccy

2014-06-04 Thread Marcus Leech
It will depend some on the effective group delay of both the interpolation filters in the the FPGA and the analog group delay of the analog bits of whatever daughtercard you're using.   The only way to be sure is to measure...     on Jun 04, 2014, bob wole via USRP-users wrote: I am using stream

Re: [Discuss-gnuradio] Scheduling a block even with no input items RE: Flow graph blocking when doing 2x1 transmission

2014-06-04 Thread Activecat
Please do not top post. Refer http://gnuradio.org/redmine/projects/gnuradio/wiki/MailingLists#Guidelines-for-posting ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] Scheduling a block even with no input items RE: Flow graph blocking when doing 2x1 transmission

2014-06-04 Thread Activecat
On Wed, Jun 4, 2014 at 10:25 PM, David Halls wrote: > Yes, there are 3. The Source Tx, the Relay Tx, and the Relay Rx. > To clarify, i). the "Source Tx" USRP may or may not receive data at any time interval. ii). the "Relay Tx" USRP transmit data only when the "Source Tx" USRP receive data, an

[Discuss-gnuradio] tx_time tag accuraccy

2014-06-04 Thread bob wole
I am using stream tags for the transmission control. I want to know what is the accuracy/precision of the tx_time tag? E.g if I tag a burst A with tx_time=X, then the burst A will come out of the USRP transmit FIFO at X+delta, how large the value of delta could be? -- Bob

Re: [Discuss-gnuradio] Scheduling a block even with no input items RE: Flow graph blocking when doing 2x1 transmission

2014-06-04 Thread Activecat
On Wed, Jun 4, 2014 at 7:10 PM, David Halls wrote: > Activecat, > > In fact my horrible hack doesn't work properly. Once items start arriving > at Payload TD Tx 2, they still don't arrive as 'consistently' (for want of > a better word), as those from the Noise Source block, and thus zeros are > i

Re: [Discuss-gnuradio] Scheduling a block even with no input items RE: Flow graph blocking when doing 2x1 transmission

2014-06-04 Thread Activecat
On Wed, Jun 4, 2014 at 8:53 PM, David Halls wrote: > Hi Activecat, > > I have disconnected the rest of the flow graph because it is extremely > complex. > > In the system I have a Source, a Relay (1 rx USRP, 1 tx USRP), a > Destination. S ---> R_rx/R_tx --> D > > The two transmitters that you see

Re: [Discuss-gnuradio] Scheduling a block even with no input items RE: Flow graph blocking when doing 2x1 transmission

2014-06-04 Thread David Halls
From: Activecat [active...@gmail.com] Sent: 04 June 2014 16:13 To: David Halls Cc: discuss-gnuradio@gnu.org Subject: Re: [Discuss-gnuradio] Scheduling a block even with no input items RE: Flow graph blocking when doing 2x1 transmission On Wed, Jun 4, 2014

Re: [Discuss-gnuradio] Scheduling a block even with no input items RE: Flow graph blocking when doing 2x1 transmission

2014-06-04 Thread David Halls
From: Activecat [active...@gmail.com] Sent: 04 June 2014 16:02 To: David Halls Cc: discuss-gnuradio@gnu.org Subject: Re: [Discuss-gnuradio] Scheduling a block even with no input items RE: Flow graph blocking when doing 2x1 transmission On Wed, Jun 4, 2014

Re: [Discuss-gnuradio] Scheduling a block even with no input items RE: Flow graph blocking when doing 2x1 transmission

2014-06-04 Thread Activecat
On Wed, Jun 4, 2014 at 10:52 PM, David Halls wrote: > Not quite... > > i). the "Source Tx" USRP has a constant stream of data, and is constantly > transmitting. If the codewords in the file are exhausted it repeats. > ii). the "Relay Tx" USRP transmits data only when data has been received > by t

Re: [Discuss-gnuradio] Scheduling a block even with no input items RE: Flow graph blocking when doing 2x1 transmission

2014-06-04 Thread Activecat
On Wed, Jun 4, 2014 at 10:52 PM, David Halls wrote: > Not quite... > > i). the "Source Tx" USRP has a constant stream of data, and is constantly > transmitting. If the codewords in the file are exhausted it repeats. > ii). the "Relay Tx" USRP transmits data only when data has been received > by t

Re: [Discuss-gnuradio] Scheduling a block even with no input items RE: Flow graph blocking when doing 2x1 transmission

2014-06-04 Thread David Halls
From: Activecat [active...@gmail.com] Sent: 04 June 2014 15:39 To: David Halls Cc: discuss-gnuradio@gnu.org Subject: Re: [Discuss-gnuradio] Scheduling a block even with no input items RE: Flow graph blocking when doing 2x1 transmission On Wed, Jun 4, 2014

Re: [Discuss-gnuradio] GRC uses OSS instead of ALSA??

2014-06-04 Thread Tom Rondeau
On Mon, Jun 2, 2014 at 12:54 PM, John Meloche wrote: > Hi guys, > > My application requires that I use a multi-channel audio device as an > audio source. I have in my system of hardware the Presonus 1818VSL > external USB device. This audio source is definetely working correctly > with Ubuntu a

Re: [Discuss-gnuradio] Scheduling a block even with no input items RE: Flow graph blocking when doing 2x1 transmission

2014-06-04 Thread David Halls
From: Activecat [active...@gmail.com] Sent: 04 June 2014 15:21 To: David Halls Cc: discuss-gnuradio@gnu.org Subject: Re: [Discuss-gnuradio] Scheduling a block even with no input items RE: Flow graph blocking when doing 2x1 transmission On Wed, Jun 4, 2014

Re: [Discuss-gnuradio] Gardner timing sync loop quetion

2014-06-04 Thread Tom Rondeau
On Tue, Jun 3, 2014 at 4:12 AM, Tiankun Hu wrote: > Hi all, > I am designing a 2 order Gardner timing sync loop(with 1 order PI loop > filter) for QAM64. > As Best's PLL book metioned, timing sync loop's parameter can be > calculated by using PLL theory. > Now I need calculate the PI loop filter'

Re: [Discuss-gnuradio] Scheduling a block even with no input items RE: Flow graph blocking when doing 2x1 transmission

2014-06-04 Thread Activecat
On Wed, Jun 4, 2014 at 8:53 PM, David Halls wrote: > Hi Activecat, > > I have disconnected the rest of the flow graph because it is extremely > complex. > > In the system I have a Source, a Relay (1 rx USRP, 1 tx USRP), a > Destination. S ---> R_rx/R_tx --> D > > The two transmitters that you see

Re: [Discuss-gnuradio] Scheduling a block even with no input items RE: Flow graph blocking when doing 2x1 transmission

2014-06-04 Thread David Halls
Activecat, In fact my horrible hack doesn't work properly. Once items start arriving at Payload TD Tx 2, they still don't arrive as 'consistently' (for want of a better word), as those from the Noise Source block, and thus zeros are inserted when they are not required! David -Original Mes

Re: [Discuss-gnuradio] Scheduling a block even with no input items RE: Flow graph blocking when doing 2x1 transmission

2014-06-04 Thread David Halls
Sorry – I meant to hit reply all! From: Activecat [mailto:active...@gmail.com] Sent: 04 June 2014 10:51 To: discuss-gnuradio@gnu.org Cc: David Halls Subject: Re: [Discuss-gnuradio] Scheduling a block even with no input items RE: Flow graph blocking when doing 2x1 transmission On Wed, Jun 4, 201

Re: [Discuss-gnuradio] Scheduling a block even with no input items RE: Flow graph blocking when doing 2x1 transmission

2014-06-04 Thread Activecat
On Wed, Jun 4, 2014 at 4:59 PM, David Halls wrote: > Hi! > > This shouldn't be the case. But is there any easy way to allow different > rates on the two streams, so I could produce more zeros on stream 1 than > items on stream 0? Or vice versa? > > David > Please stay on the list. To have d

[Discuss-gnuradio] NEWSDR Event This Friday June 6 in Boston

2014-06-04 Thread Golurk Hameshta
* * Fourth-Annual * * * * New England Workshop on Software-Defined Radio* * NEWSDR 2014 * *

Re: [Discuss-gnuradio] Fwd: Re: something about forecast()

2014-06-04 Thread Marcus Müller
Hi Xianda, 1.: Yes, that will be the case Greetings, Marcus ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

[Discuss-gnuradio] Fwd: Re: something about forecast()

2014-06-04 Thread Marcus Müller
Original Message Subject:Re: [Discuss-gnuradio] something about forecast() Date: Wed, 4 Jun 2014 16:52:11 +0800 (CST) From: xianda To: Marcus Müller Hi: Thank you. 1.Oh,I understand it.If i say,this is according to how many input port

Re: [Discuss-gnuradio] using uhd_fft with USRP N210

2014-06-04 Thread Marcus Müller
Ah, missed that. You should not disable VOLK - almost all of GNU Radio uses that by now. On 04.06.2014 10:41, sammy zada wrote: > Hi, > > I'm trying to run uhd_fft with usrp N210, my machine run ubuntu desktop > 12.04.4 LTS. > > When I try to run uhd_fft which is located in > /usr/local/src/gnurad

Re: [Discuss-gnuradio] using uhd_fft with USRP N210

2014-06-04 Thread Marcus Müller
Hi Sammy, when building, basically *everything* was not built, so you don't really have GNU Radio installed. This is usually due to missing a crucial dependency of GNU Radio. How did you install? I recommend using pyBOMBs, if you didn't, because that should take care of installing dependencies: htt

Re: [Discuss-gnuradio] something about forecast()

2014-06-04 Thread Marcus Müller
Hi Xianda, the io_signature specifies a minimum and a maximum number of inputs, so this might be 1,2 or 3. Greetings, Marcus On 04.06.2014 10:24, xianda wrote: > Hi: > Thank you so much. > Now i want to ask:if we set > gr::block("c_vcv

[Discuss-gnuradio] using uhd_fft with USRP N210

2014-06-04 Thread sammy zada
Hi, I'm trying to run uhd_fft with usrp N210, my machine run ubuntu desktop 12.04.4 LTS. When I try to run uhd_fft which is located in /usr/local/src/gnuradio-3.7.2.1/gr-uhd/apps directory, i've got the following message: root@openlab:/usr/local/src/gnuradio-3.7.2.1/gr-uhd/apps# ./uhd_fft Traceba

Re: [Discuss-gnuradio] QT Gui FFT resizing Segfault

2014-06-04 Thread Marcus Müller
I think it's going wrong in getActionFromSize, which easy as it looks[1], I don't get the hang of. Why do we need a specific QAction based on the FFT length we're setting? And why does an FFT size of 4 lead to negative indices in a QList? Anyway, the actual bug was on my side, as I was constantly

Re: [Discuss-gnuradio] QT Gui FFT resizing Segfault

2014-06-04 Thread Marcus Müller
Hi! Alfredo: Jep, did that. GDB was how I figured out things went wrong in FreqDisplayForm::setFFTSize() in the first place :). Jörg: Interesting; but the error is quite reproducibly at the same place; I'll try to set a breakpoint at the kernel call and see if that happens again. But that will req

Re: [Discuss-gnuradio] something about forecast()

2014-06-04 Thread Activecat
On Wed, Jun 4, 2014 at 2:22 PM, xianda wrote: > Hi all: > I want to know something about the forecast(). > I have already known that forcast() can tell scheduler how many > input items are required for each output item. > 1.But now i have read two example: > The fi

Re: [Discuss-gnuradio] something about forecast()

2014-06-04 Thread Marcus Müller
Hi Xianda, Easiest answer first: 2. You need to write a forecast if, and only if, you're using general_work. I generally try to avoid doing that. Then: 1. ninput_items_required is, as you can see in the function signature, a reference to a vector. The size of the vector is the number of input po