Is there any way in GRC to stop sending a signal? For example, I attach
snapshot of a simple GRC flowgraph with a 250 Hz cosine signal source
outputting floats into an audio sink, and also into a file sink called
“test.dat”. Everything works fine and I see the output, and I can graph
file with a simple python script.
But the problem is that after some time I have to stop the transmission
manually forcing the flow graph to abruptly end.
Is there any way in GRC to automatically stop the signal after some
say a finite pulse? I don’t want to send a continuous signal, but I want
to stop, say, after ten periods.
Now some of you (e.g., Josh) have pointed me to a way of using Python or
C++ to maybe tag the last sample with an EOB metadata, and I will try
when I need to do something in Python or C++, but I don’t understand how
would change anything in this particular flow graph. I mean, just
the last sample with an EOB tag won’t stop the datafile from being
populated by a continuous data stream.
I guess I don’t understand why it should be so hard just using GRC to
sending a signal after some time., or maybe it’s easy, and I just don’t
it. I know there is a burst tagger object in GRC that someone once
mentioned in this group, but it was used to feed into the USRP, and I
assume that the USRP knew somehow to stop reception? I guess I am
and need some kind of help in understanding this. :-(.
Thanks for any insights…