After a little debugging, I found where exactly the pipe seems to break. Please forgive the redundancy to follow, those of you who are already familiar with the gnuradio graph class hierarchy.
AFTER the socket connection between the two computers is established: 1.) usrp_rx_cfile.my_graph.run() is called, and usrp_rx_cfile.__init__ is progressed through 2.) then at the end of it, flow_graph.run() is called. ( located in /usr/local/lib/python2.3/...(etc).../gr/flow_graph.py ) 3.) Control goes to flow_graph, and scheduler.py is called via self.scheduler.start() 4.) and at line 57 in scheduler.py, thread.start() is called. After it is called (probably sometime during it, rather), the pipe breaks. I don't know Python very well, and I am not proficient at network programming. Any help is appreciated. Sorry I cannot easily post output to the forum; this LAN is isolated from the internet. Written Eric Blossom wrote: > > On Tue, Sep 05, 2006 at 03:50:12PM -0700, Written wrote: >> >> Hello again, >> >> Here is my setup. I have a Debian Sarge linux LAN isolated from the >> outside >> world. I have the USRP hooked up to one computer, and I am trying to >> have >> that computer feed another computer data via Python sockets. >> >> On the computer being fed (the one WITHOUT the USRP), I am running a >> program very similar to usrp_fft.py. This program, instead of accessing >> the >> USRP directly, accepts data from gr.file_descriptor_source AFTER I have >> established a socket with the computer feeding this one the data. >> >> As for the feeding computer, it is running usrp_rx_cfile.py with the >> sink, >> instead of gr.file_sink, is now gr.file_descriptor_sink. This computer >> is >> listening for the other computer in order to create a connection with it. >> >> Then, for the actual process: I run the feeding computer, then run the >> computer being fed, but there is an error. The feeding computer starts >> listing the USRP data (Rev number, etc.), but then it says >> "gr.file_descriptor_sink: broken pipe". > > It's almost certain that the file handle corresponding to the file > descriptor you are using has gone out of scope and thus has been > closed. > > Eric > > > _______________________________________________ > Discuss-gnuradio mailing list > Discuss-gnuradio@gnu.org > http://lists.gnu.org/mailman/listinfo/discuss-gnuradio > > -- View this message in context: http://www.nabble.com/USRP-access-via-sockets-tf2223875.html#a6181035 Sent from the GnuRadio forum at Nabble.com. _______________________________________________ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
