Re: [Discuss-gnuradio] Discuss-gnuradio Digest, Vol 204, Issue 6

2019-10-07 Thread ali mokdad
are sent to the message > debug. > > How can I solve this problem? > -- next part -- > An HTML attachment was scrubbed... > URL: < > https://lists.gnu.org/archive/html/discuss-gnuradio/attachments/20191007/c17ad733/attachment.html > > > > --

Re: [Discuss-gnuradio] Tx and Rx on USRP simultaneously, device already claimed

2019-10-07 Thread Marcus D. Leech
On 10/07/2019 05:25 PM, Mark Wagner wrote: Yeah, here's a basic example of the flowgraph On Mon, Oct 7, 2019 at 11:17 AM Marcus D Leech mailto:patchvonbr...@gmail.com>> wrote: Could you share a minimal flow graph that displays the issue? Sent from my iPhone > On Oct 7, 2019,

Re: [Discuss-gnuradio] Tx and Rx on USRP simultaneously, device already claimed

2019-10-07 Thread Mark Wagner
Yeah, here's a basic example of the flowgraph On Mon, Oct 7, 2019 at 11:17 AM Marcus D Leech wrote: > Could you share a minimal flow graph that displays the issue? > > Sent from my iPhone > > > On Oct 7, 2019, at 2:08 PM, Mark Wagner wrote: > > > > Hey everyone, > > > > I'm trying to transmit

Re: [Discuss-gnuradio] Tx and Rx on USRP simultaneously, device already claimed

2019-10-07 Thread Marcus D Leech
Could you share a minimal flow graph that displays the issue? Sent from my iPhone > On Oct 7, 2019, at 2:08 PM, Mark Wagner wrote: > > Hey everyone, > > I'm trying to transmit from the TX/RX port of a USRP while receiving from RX2 > but I'm getting a 'device already claimed' error message.

[Discuss-gnuradio] Tx and Rx on USRP simultaneously, device already claimed

2019-10-07 Thread Mark Wagner
Hey everyone, I'm trying to transmit from the TX/RX port of a USRP while receiving from RX2 but I'm getting a 'device already claimed' error message. Here are some details: My USRP sink block uses multiple USRP addresses, i.e. "addr0=192.168.1.2,addr1=192.168.2.2,addr3=192.168.3.2,..." and

Re: [Discuss-gnuradio] fifo / file source

2019-10-07 Thread N. Benes
ali mokdad: > do you know a special program I can test? "stdbuf" could be of help here. But beware that the input stream into "cat" may still be (line) buffered because of bash. Example: $ stdbuf -i 0 -o 0 cat > in Cheers! ___ Discuss-gnuradio

Re: [Discuss-gnuradio] fifo / file source

2019-10-07 Thread ali mokdad
Thx for your reply "it's not quite certain which program you run in that terminal" I just wrote cat > in even I run a .c file in the .c file I opened a file and the data are not sent only when I close the file. do you know a special program I can test? On Mon, Oct 7, 2019 at 2:11 PM Müller,

Re: [Discuss-gnuradio] fifo / file source

2019-10-07 Thread CEL
Hi Ali, it's not quite certain which program you run in that terminal, but: File I/O is usually buffered, and this sounds like the data is never written to your FIFO before you exit your terminal program. Solution: Use a terminal program that doesn't buffer or flushes regularly. Best regards,

[Discuss-gnuradio] fifo / file source

2019-10-07 Thread ali mokdad
Dear all I tested the following 1- in terminal, I created a fifo file by: mkfifo in 2- in terminal, I run: cat > in 3- in gnuradio i run : file source (in) --> stream to tagged stream --> tagged stream to pdu --> message debug 4- in terminal, I write and press enter nothing is sent, only if I