I'm trying to get a channel estimate, therefore I need to access the
data before the demodulator, since the demodulator will quantize the
data. My flow-graph isnt using USRP's for the meantime, just a channel
model. So my system receiver goes like this:
CHANNEL_MODEL -> MESSAGE_SINK -> DO SOME PY
On Mon, Sep 3, 2012 at 5:44 PM, Travis Collins wrote:
> By "not processing data" I mean I look at the size of the source
> queue, which is attached to the dpsk_demod block and it just grows
> without data being removed. I just use the queue.count() method to
> observe this. I can even stop addin
By "not processing data" I mean I look at the size of the source
queue, which is attached to the dpsk_demod block and it just grows
without data being removed. I just use the queue.count() method to
observe this. I can even stop adding data to the message source block
and the queue count remains
On Fri, Aug 31, 2012 at 3:13 PM, Travis Collins
wrote:
> Ive change the connected block from a dbpsk_demod to a null_sink and a
> file_sink and the queue is processed, but I'm still having an issue
> with the demod block.
>
> I believe the problem has to be with the data type conversion
> "process
Ive change the connected block from a dbpsk_demod to a null_sink and a
file_sink and the queue is processed, but I'm still having an issue
with the demod block.
I believe the problem has to be with the data type conversion
"processed.tostring()". Should I convert each individual value of the
nump
Im having an issue with the my dpsk demodulator block not processing
any data provided by a message source block.
This is how I'm passing it to the queue:
msg = gr.message_from_string(processed.tostring(), gr.sizeof_gr_complex)
tb.source_queue.insert_tail(msg)
The "processed" data is a numpy arra
