Re: [Discuss-gnuradio] Full duplex and half duplex doesnot work

[abbasi9999]

The problem has been resolved.
thanks a lot Eric

abbasi9999 wrote:
> 
> 
> Eric Blossom wrote:
>> 
>> On Tue, Jan 19, 2010 at 06:00:43AM -0800, abbasi9999 wrote:
>> From the backtrace below, it appears that you already have the source
>> open, or you're running something else that has the source open, or
>> you opened it earlier and didn't close it, or still have a live python
>> to the earlier instance.
>> 
> 
> about that I'm running something NO. 
> However, YES the port is open because i dont know how to close it. I
> thought the benchmark_{rx,tx}.py close it self after finishing
> transmitting or receiving if i added the parameter " -v ".
> 
> From other post i saw that 2+Ctrl will reset the usrp, I've tried it but
> its no use.
> Another post said that to free the usb resources i should write the
> command "modprobe -vr ehci_hcd", but it also did not work.
> 
> So how to free the usb resources or how to close the already opened usb
> (opened by benchmark_rx,tx.py program).
> 
> regards,
> 
> 
> Eric Blossom wrote:
>> 
>> Half-duplex vs full-duplex is orthogonal to this issue.  Likewise,
>> Auto T/R has nothing to do with the error below.  With either full or
>> half duplex you would most likely open the source and sink once each
>> at the beginning of the program, then go about your business.
>> 
>> Eric
>> 
> 
> As i said before, should not the parameter "-v" do the trick, or you meant
> that it do not close the usb resources that it already opened. therefore i
> have to do it manually?
> 
> best regards,
> 

-- 
View this message in context: 
http://old.nabble.com/Full-duplex-and-half-duplex-doesnot-work-tp27226209p27297831.html
Sent from the GnuRadio mailing list archive at Nabble.com.