> Ali Siddiqi wrote:
> >
> > Hi,
> > Did the flowgraph of the code (in which you added the timeout)
involved
> > receive_path???
> >
> > Regards,
> > Ali
> >
> > On Mon, Aug 3, 2009 at 11:21 AM, Dan Rosenqvist
wrote:
> >
> >>
> >>
> >>
> >> Umair Nasir wrote:
> >> >
> >> > Hi all,
> >> >
> >> > Th
Ali Siddiqi wrote:
>
> Hi,
> Did the flowgraph of the code (in which you added the timeout) involved
> receive_path???
>
> Regards,
> Ali
>
> On Mon, Aug 3, 2009 at 11:21 AM, Dan Rosenqvist wrote:
>
>>
>>
>>
>> Umair Nasir wrote:
>> >
>> > Hi all,
>> >
>> > This question is asked a number o
Hi,
Did the flowgraph of the code (in which you added the timeout) involved
receive_path???
Regards,
Ali
On Mon, Aug 3, 2009 at 11:21 AM, Dan Rosenqvist wrote:
>
>
>
> Umair Nasir wrote:
> >
> > Hi all,
> >
> > This question is asked a number of times. And I believe it shouldn't be
> > that
> >
Umair Nasir wrote:
>
> Hi all,
>
> This question is asked a number of times. And I believe it shouldn't be
> that
> tough. Somebody explain where to put this logic in benchmark_rx.py
>
> If no data received
> set freq to freq number 2
> else
> stay on the current freq
Hi all,
This question is asked a number of times. And I believe it shouldn't be that
tough. Somebody explain where to put this logic in benchmark_rx.py
If no data received
set freq to freq number 2
else
stay on the current freq
Waiting for a response.
--
Umair
___
Hi all,
This question is asked a number of times. And I believe it shouldn't be that
tough. Somebody explain where to put this logic in benchmark_rx.py
If no data received
--
Umair
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http:/
