discuss-gnuradio
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Discuss-gnuradio] Passing the payload to the application level


From: trondeau
Subject: Re: [Discuss-gnuradio] Passing the payload to the application level
Date: Thu, 21 Sep 2006 01:27:51 -0400
User-agent: Internet Messaging Program (IMP) 3.2.8

Right now, I'd suggest waiting a few days. We've been working on the digital
modulations for the next bundled release, and I think I'm about to check in a
few of the last changes. Once this is merged with the trunk, the digital
modulations should be much simpler to handle, including having a generic pkt.py
instead of the gmsk_pkt.py.

That having been said, your problem probably isn't going to disappear with the
changes we've made, but it will hopefully simplify the understanding and
tracing through the flow graph. There is still the _queue_watcher_thread that
makes a blocking call the the rcvd_pktq (received packet queue). When the PHY
layer demodulator gets bits, it packs them into this message queue, whereby the
watching thread blocking call gets released and the packet is sent to the
specified callback function.

If you do need more help soon, I can give you more tomorrow (or Eric will soon).

Tom



Quoting Michael Ford <address@hidden>:

> I am trying to pass the payload from the layer where it is obtained back to
> the application level. However, I'm having some problems. When examining
> benchmark_gmsk_rx.py, I see that the rx_callback funstion is passed into the
> receive_path class. Going further, I see that the function is passed from
> benchmark_gmsk_rx.py to the receive_path class to the gmsk_demod_pkts class,
> which I understand to be in
> /usr/local/lib/python2.4/site-packages/gnuradio/blksimpl/gmsk2_pkt.py. Here,
> the function is finally called in a class called _queue_watcher_thread.
> However, no matter what I do, I can't get the payload data back to the app
> layer. Just to test things, I commented out the instance of
> _queue_watcher_thread that is instantiated by the gmsk2_demod_pkts() class,
> and the rx_callback function is still running, which leads me to believe
> that I'm not looking in the right place. Also, when I try to make a member
> variable of the _queue_watcher_thread class called self.thepayload and make
> a a return of the payload in the rx_callback function, and then try to print
> self.thepayload from the watcher class, nothing happens. If I make a print
> statement in the rx_callback function, the payload prints.
>
> -Michael Ford-
>




reply via email to

[Prev in Thread] Current Thread [Next in Thread]