Re: [Discuss-gnuradio] pipes

2006-07-05 Thread Eric Blossom
On Wed, Jul 05, 2006 at 10:32:36AM +, paul munro wrote: > Ok, I have tried the TCP method with no real success. I have set GNUradio > to be the client, Labview as the server. They connect, then the python > script disconnects with errors before any data is communicated. I have > tried a coup

Re: [Discuss-gnuradio] pipes

2006-07-05 Thread paul munro
d pipes with no problems. I'm not sure if the problem is the tcp control or a lower level of gnuradio. Any suggestions?? Regards Paul From: Eric Blossom <[EMAIL PROTECTED]> To: paul munro <[EMAIL PROTECTED]> CC: discuss-gnuradio@gnu.org Subject: Re: [Discuss-gnuradio] pipes D

Re: [Discuss-gnuradio] pipes

2006-07-04 Thread Eric Blossom
On Tue, Jul 04, 2006 at 06:44:55AM +, paul munro wrote: > Is there a way of sending the data from the USRP to another application > using pipes?? I only know the basics of pipes, and need to look into it > more. I was going to try using TCP but thought pipes maybe easier. Also, > labview (th

[Discuss-gnuradio] pipes

2006-07-03 Thread paul munro
Is there a way of sending the data from the USRP to another application using pipes?? I only know the basics of pipes, and need to look into it more. I was going to try using TCP but thought pipes maybe easier. Also, labview (the app i am sending it to) expects data over the TCP port to be in s

Re: [Discuss-gnuradio] pipes for today

2005-04-20 Thread Krzysztof Kamieniecki
Some more information and possible solution (it's been running for about 20 minutes now without any problems and it usually failed in less then a minute). I am transmitting using 4 DACs at 1MS/s and receiving using 4 ADCs at 1MS/s. When the problem occurs: - The USRP Tx thread seems to be running

Re: [Discuss-gnuradio] pipes for today

2005-04-20 Thread Damien B.
Hi, i think i just hit the same issue >From this simple code (no display what so ever): fg = gr.flow_graph () u = usrp.source_c (0, 64, 1, 0xf0f0f0f0, 0) n = gr.null_sink(gr.sizeof_gr_complex); fg.connect(u, n); dest = usrp.sink_c (0, 64) siggen = gr.sig_source_c (dest.d

Re: [Discuss-gnuradio] pipes for today

2005-04-20 Thread cswiger
On Wed, 20 Apr 2005, Rahul Dhar wrote: > On Fri, Apr 08, 2005 at 04:10:20PM -0400, cswiger wrote: > > This is a curious behavior: if > > > > 1) Use a vector source at the head and the USRP at the tail all is OK > > > > 2) Use the pipe fd source at the head and a file sink at the tail all is > > OK

Re: [Discuss-gnuradio] pipes for today

2005-04-20 Thread Krzysztof Kamieniecki
Eric, Have you made any progress with this? I'm having a problem that may be related. The blocks are layed out like this. USRP Rx -> ... -> pipe gr_sig_source -> ... -> USRP Tx When running in gdb: 1. I wait for it to lockup 2. hit Ctrl-Z (to get into gdb) 3. type continue 4. more data is pro

Re: [Discuss-gnuradio] pipes for today

2005-04-08 Thread Eric Blossom
On Fri, Apr 08, 2005 at 04:10:20PM -0400, cswiger wrote: > This is a curious behavior: if > > 1) Use a vector source at the head and the USRP at the tail all is OK > > 2) Use the pipe fd source at the head and a file sink at the tail all is > OK > > but if > > 3) Use a pipe fd source at the hea

[Discuss-gnuradio] pipes for today

2005-04-08 Thread cswiger
This is a curious behavior: if 1) Use a vector source at the head and the USRP at the tail all is OK 2) Use the pipe fd source at the head and a file sink at the tail all is OK but if 3) Use a pipe fd source at the head and the USRP (with a parallel file sink to monitor) at the tail data very s