This sentence makes no sense on its own. Please post a whole description of what you're doing: I'll from now on will ignore your questions that don't follow that methodology. See also:
http://www.catb.org/esr/faqs/smart-questions.html https://lists.gnu.org/archive/html/discuss-gnuradio/2017-10/msg00213.ht ml On Wed, 2018-06-20 at 14:00 +0000, Amirhosein naseri wrote: > Another point is : > > If u in python code generated from GRC construct transmit chain completely > (definition of blocks and their connections ) and then construct receive > chain or vise versa , u can use both chain in same flowgragh ...... > > > > On Wednesday, June 20, 2018, 4:55:31 PM GMT+4:30, Müller, Marcus (CEL) > <muel...@kit.edu> wrote: > > > Please try to keep answers on the list. > Also, it's pretty frustrating to have helped you, but not knowing how, and > also, doubting you do something sensible. > > Best regards, > Marcus > > On Wed, 2018-06-20 at 12:23 +0000, Amirhosein naseri wrote: > > Tnx Marcus for your answers > > > > I split flowgraph in two part and it worked ... > > and it does'nt matter run witch flowgraph first > > > > > > Best Regards. > > > > On Wednesday, June 20, 2018, 4:49:56 PM GMT+4:30, Müller, Marcus (CEL) > > <muel...@kit.edu> wrote: > > > > > > Again, can't tell what you're trying to do, can't help you! Describe > > what problem you're trying to solve. > > > > On Wed, 2018-06-20 at 12:15 +0000, Amirhosein naseri wrote: > > > The flowgraph i mentioned was a simplified version of my work ... > > > > > > I can seprate it in two flowgraph, so in this situation i must run which > > > side of transfer first?? > > > > > > On Wednesday, June 20, 2018, 4:40:06 PM GMT+4:30, Müller, Marcus (CEL) > > > <muel...@kit.edu> wrote: > > > > > > > > > Well, I don't know what problem you're solving. It works if you're not > > > doing this in the same flow graph. > > > > > > On Wed, 2018-06-20 at 12:09 +0000, Amirhosein naseri wrote: > > > > Tnx Marcus for replying > > > > > > > > so based on what u said ... we can not use such configuration with FIFO > > > > , is it ture??? > > > > if NO , what is the solution??? > > > > > > > > On Wednesday, June 20, 2018, 4:28:52 PM GMT+4:30, Müller, Marcus (CEL) > > > > <muel...@kit.edu> wrote: > > > > > > > > > > > > That's normal FIFO behaviour! From `man 3 mkfifo`: > > > > > > > > > Opening a FIFO for reading normally blocks until some other process > > > > opens the same FIFO for writing, and vice versa. > > > > > > > > Remember, the GRC file is just converted to a Python program, in which > > > > the different blocks are instantiated sequentially. Now, the problem > > > > follows is that you can't even initialize the file source if the file > > > > sink doesn't finish initializing, or the other way around, whichever > > > > comes first. > > > > > > > > Best regards, > > > > Marcus > > > > > > > > On Wed, 2018-06-20 at 10:52 +0000, Amirhosein naseri wrote: > > > > > Hi everybody, > > > > > > > > > > I have a simple GRC like this: > > > > > > > > > > Signal Source ------> Throttle ------> File Sink > > > > > File Source ------> Throttle -----> Qt Freq Sink > > > > > > > > > > and i have a Piped File with mkfifo that GRC work with it. but when i > > > > > run GRC , it freezes ....... Why??? > > > > > > > > > > > > > > > Tnx?? > > > > > > > > > _______________________________________________ > > > > > 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
