Hi Barry, The way the flowgraph is right now, the vector source generates samples as fast as it can and it's directly treated by the EPyB and floods the buffers. When a pdu is to be inserted, there is already tons of filler samples to treat first so that greatly delays the moment you can see the pdu samples in the time sink.
You need to add a throttle block before the input to your embedded block. That way the input stream will have a limited sample rate and it will allow the samples from the pdus to be inserted in real time. Le 20 novembre 2021 03:28:09 GMT+01:00, Barry Duggan <[email protected]> a écrit : >My objective: In reference to the >https://wiki.gnuradio.org/index.php/Packet_Communications#Using_BPSK_with_Hardware_Simulation_.28version_3.9.29 > tutorial: it sends packets but has dead time in-between, which may cause the >BPSK receiver to lose sync. I would like to fill the time (and stream) with an >idle code so there is always a signal for the receiver. My latest attempt to >use a Python Source block didn't work out - probably a timing problem or a >lack of understanding of the scheduler. > > > >This Embedded Python block receives a stream input of idle bytes and a PDU >message input. It outputs the PDU message when received, otherwise it outputs >the idle bytes. However, the PDU data never appears downstream. > > > >Note: this flowgraph uses AFSK instead of BPSK, but the objective is the same. > > > >See https://pastebin.com/GJgnzjCP Embedded Python block > >https://pastebin.com/C6XVsCZx AFSK flowgraph > > > >Any help will be appreciated. > > > >--- > >Barry Duggan KV4FV > >https://github.com/duggabe Cyrille Morin
