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

[ali mokdad]

Dear all

Moreover,

as I mentioned before no data is transmitted in the following case
1- $ mkfifo in
2-: $ cat > in
3- gnuradio : file source (in)  --> stream to tagged stream --> throttle -->
tagged stream to pdu --> message debug
till I press ctrl c, where in file source repeat in no.

if repeat is yes then I have the following error
[/build/gnuradio-BBYmSv/gnuradio-3.7.11/gr-blocks/lib/file_source_impl.cc]
fseek failed

can anyone inform me what is the problem?

Best regards

On Tue, Oct 8, 2019 at 8:00 AM ali mokdad  wrote:

> Dear
>
> thx for your reply
>
> even by using  stdbuf  the problem remains the same
> $ stdbuf -i 0 -o 0 cat > in
>
> I think the problem must be solved from gnuradio because if I run two
> terminals in
> first terminal: $ cat > in
> second terminal: $ cat in
> then whatever I write in the first terminal is sent to the second terminal
> after pressing enter.
>
> while
> if instead of the second terminal I used gnuradio with the following
> flowgraph
> in gnuradio : file source (in)  --> stream to tagged stream --> throttle
> -->
> tagged stream to pdu --> message debug
>
> the data are not sent till I press ctrl c.
>
> thanks again for your help, but my problem is not solved if there is any
> one can help me
>
> Best regards
>
>
>
> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=icon>
>  Virus-free.
> www.avast.com
> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=link>
> <#m_6056736687892377648_m_1211741247935538308_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>
> On Mon, Oct 7, 2019 at 7:06 PM  wrote:
>
>> Send Discuss-gnuradio mailing list submissions to
>> discuss-gnuradio@gnu.org
>>
>> To subscribe or unsubscribe via the World Wide Web, visit
>> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>> or, via email, send a message with subject or body 'help' to
>> discuss-gnuradio-requ...@gnu.org
>>
>> You can reach the person managing the list at
>> discuss-gnuradio-ow...@gnu.org
>>
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of Discuss-gnuradio digest..."
>>
>>
>> Today's Topics:
>>
>>1. fifo / file source (ali mokdad)
>>2. Re: fifo / file source (Müller)
>>3. Re: fifo / file source (ali mokdad)
>>4. Re: fifo / file source (N. Benes)
>>
>>
>> --
>>
>> Message: 1
>> Date: Mon, 7 Oct 2019 13:41:47 +0300
>> From: ali mokdad 
>> To: discuss-gnuradio@gnu.org
>> Subject: [Discuss-gnuradio] fifo / file source
>> Message-ID:
>> <
>> cacn2bhndhnwhkddjfojnm1pgps+nrhdudm7zyeaa6abptke...@mail.gmail.com>
>> Content-Type: text/plain; charset="utf-8"
>>
>> 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 press
>> ctrl c the all the data written in the terminal 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
>> >
>>
>> --
>>
>> Message: 2
>> Date: Mon, 7 Oct 2019 11:11:52 +
>> From: Müller, Marcus (CEL) 
>> To: "discuss-gnuradio@gnu.org" ,
>> "aa.mokdad...@gmail.com" 
>> Subject: Re: [Discuss-gnuradio] fifo / file source
>> Message-ID: <5878b0c98107f9bf6ef01c5853d135ab80888ef5.ca...@kit.edu>
>> Content-Type: text/plain; charset="utf-8"
>>
>> 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,
>> Marcus
>>
>> On Mon, 2019-10-07 at 13:41 +0300, al

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

[ali mokdad]

Dear

thx for your reply

even by using  stdbuf  the problem remains the same
$ stdbuf -i 0 -o 0 cat > in

I think the problem must be solved from gnuradio because if I run two
terminals in
first terminal: $ cat > in
second terminal: $ cat in
then whatever I write in the first terminal is sent to the second terminal
after pressing enter.

while
if instead of the second terminal I used gnuradio with the following
flowgraph
in gnuradio : file source (in)  --> stream to tagged stream --> throttle -->
tagged stream to pdu --> message debug

the data are not sent till I press ctrl c.

thanks again for your help, but my problem is not solved if there is any
one can help me

Best regards


<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=icon>
Virus-free.
www.avast.com
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=link>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

On Mon, Oct 7, 2019 at 7:06 PM  wrote:

> Send Discuss-gnuradio mailing list submissions to
> discuss-gnuradio@gnu.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
> or, via email, send a message with subject or body 'help' to
> discuss-gnuradio-requ...@gnu.org
>
> You can reach the person managing the list at
> discuss-gnuradio-ow...@gnu.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Discuss-gnuradio digest..."
>
>
> Today's Topics:
>
>1. fifo / file source (ali mokdad)
>2. Re: fifo / file source (Müller)
>3. Re: fifo / file source (ali mokdad)
>4. Re: fifo / file source (N. Benes)
>
>
> --
>
> Message: 1
> Date: Mon, 7 Oct 2019 13:41:47 +0300
> From: ali mokdad 
> To: discuss-gnuradio@gnu.org
> Subject: [Discuss-gnuradio] fifo / file source
> Message-ID:
> <
> cacn2bhndhnwhkddjfojnm1pgps+nrhdudm7zyeaa6abptke...@mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> 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 press
> ctrl c the all the data written in the terminal 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
> >
>
> --
>
> Message: 2
> Date: Mon, 7 Oct 2019 11:11:52 +
> From: Müller, Marcus (CEL) 
> To: "discuss-gnuradio@gnu.org" ,
> "aa.mokdad...@gmail.com" 
> Subject: Re: [Discuss-gnuradio] fifo / file source
> Message-ID: <5878b0c98107f9bf6ef01c5853d135ab80888ef5.ca...@kit.edu>
> Content-Type: text/plain; charset="utf-8"
>
> 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,
> Marcus
>
> On Mon, 2019-10-07 at 13:41 +0300, ali mokdad wrote:
> > 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 press
> ctrl c the all the data written in the terminal are sent to the message
> debug.
> >
> > How can I solve this problem?
> >
> >
> >
> > ___
> > Discuss-gnuradio mailing list
> > Discuss-gnuradio@gnu.org
> > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
> -- next part --
> A non-text attachment was scrubbed...
> Name: smime.p7s
> Type: application/x-pkcs7-signature
> Size: 6582 bytes
> Desc: not available
> URL: <
> https://lists.gnu.org/archive/html/discuss-gnuradio/attachments/20191007/5f1b0f0b/attachme

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

[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, at 2:08 PM, Mark Wagner mailto:m2wag...@eng.ucsd.edu>> 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. 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 each address goes to a different USRP in an array. I want to
transmit a calibration tone across the array from the TX channel
of the first USRP (addr0), but when I add a USRP source block it
gives a 'device already claimed' message. This doesn't happen when
I make individual USRP sink blocks for each USRP in the array.
>
> Unfortunately if I separate my devices into several USRP sink
blocks I can't guarantee the devices will be synched to the PPS.
Is there a workaround for this?
>
> -Mark
>
> --
> Mark Wagner
> University of California San Diego
> Electrical and Computer Engineering
>
> ___
> Discuss-gnuradio mailing list
> Discuss-gnuradio@gnu.org 
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio



--
Mark Wagner
University of California San Diego
Electrical and Computer Engineering

Could you give more details of your hardware configuration.  Are these 
N210s?  X310s?



Also, I'll note that 32K as a sample rate is well below what is normally 
supported--do the start-up messages complain about that?



___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

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

[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 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 each address goes to a different USRP in an array. I want to
> transmit a calibration tone across the array from the TX channel of the
> first USRP (addr0), but when I add a USRP source block it gives a 'device
> already claimed' message. This doesn't happen when I make individual USRP
> sink blocks for each USRP in the array.
> >
> > Unfortunately if I separate my devices into several USRP sink blocks I
> can't guarantee the devices will be synched to the PPS. Is there a
> workaround for this?
> >
> > -Mark
> >
> > --
> > Mark Wagner
> > University of California San Diego
> > Electrical and Computer Engineering
> >
> > ___
> > Discuss-gnuradio mailing list
> > Discuss-gnuradio@gnu.org
> > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>


-- 
Mark Wagner
University of California San Diego
Electrical and Computer Engineering


example.grc
Description: Binary data
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

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

[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. 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 each address goes to a different USRP in an array. I want to transmit a 
> calibration tone across the array from the TX channel of the first USRP 
> (addr0), but when I add a USRP source block it gives a 'device already 
> claimed' message. This doesn't happen when I make individual USRP sink blocks 
> for each USRP in the array. 
> 
> Unfortunately if I separate my devices into several USRP sink blocks I can't 
> guarantee the devices will be synched to the PPS. Is there a workaround for 
> this?
> 
> -Mark
> 
> -- 
> Mark Wagner
> University of California San Diego
> Electrical and Computer Engineering
>  
> ___
> Discuss-gnuradio mailing list
> Discuss-gnuradio@gnu.org
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

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

[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 each address goes to a different USRP in an array. I want to transmit a
calibration tone across the array from the TX channel of the first USRP
(addr0), but when I add a USRP source block it gives a 'device already
claimed' message. This doesn't happen when I make individual USRP sink
blocks for each USRP in the array.

Unfortunately if I separate my devices into several USRP sink blocks I
can't guarantee the devices will be synched to the PPS. Is there a
workaround for this?

-Mark

-- 
Mark Wagner
University of California San Diego
Electrical and Computer Engineering
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] fifo / file source

[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 mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] fifo / file source

[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, Marcus (CEL)  wrote:

> 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,
> Marcus
>
> On Mon, 2019-10-07 at 13:41 +0300, ali mokdad wrote:
> > 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 press
> ctrl c the all the data written in the terminal are sent to the message
> debug.
> >
> > How can I solve this problem?
> >
> >
> >
> > ___
> > Discuss-gnuradio mailing list
> > Discuss-gnuradio@gnu.org
> > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] fifo / file source

[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,
Marcus

On Mon, 2019-10-07 at 13:41 +0300, ali mokdad wrote:
> 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 press ctrl 
> c the all the data written in the terminal are sent to the message debug.
> 
> How can I solve this problem?
> 
> 
> 
> ___
> Discuss-gnuradio mailing list
> Discuss-gnuradio@gnu.org
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio


smime.p7s
Description: S/MIME cryptographic signature
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

[Discuss-gnuradio] fifo / file source

[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 press
ctrl c the all the data written in the terminal are sent to the message
debug.

How can I solve this problem?
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio