Re: [Discuss-gnuradio] Meaning of header_payload_demux0 - Parser returned #f

Looks like I only replied to Michael and not the list...

The example is included with gnuradio is available on the gnuradio github.

https://github.com/gnuradio/gnuradio/tree/master/gr-digital/examples/packet

 

From my understanding of this particular example, OFDM carrier allocation and all the good stuff that comes along with OFDM is not part of the example. It just performs constellation encoding, header/payload muxing, correlation estimation, carrier frequency recovery w/ costas loop, and header / payload demuxing.

 

Thanks,

Alex.

------

 

Alex Roberts

Research Engineer
Applied Power Division (11)

Southwest Research Institute
Office: (210) 522-6014 | Pager (210) 513-1672

---

From: Roberts, Alex S.
Sent: Wednesday, March 28, 2018 8:56 AM
To: Michael Dickens
Subject: RE: [Discuss-gnuradio] Meaning of header_payload_demux0 - Parser returned #f

 

The example is included with gnuradio is available on the gnuradio github.

https://github.com/gnuradio/gnuradio/tree/master/gr-digital/examples/packet

 

From my understanding of this particular example, OFDM carrier allocation and all the good stuff that comes along with OFDM is not part of the example. It just performs constellation encoding, header/payload muxing, correlation estimation, carrier frequency recovery w/ costas loop, and header / payload demuxing.

 

Thanks,

Alex.

 

From: Michael Dickens [mailto:michael.dickens@ettus.com]
Sent: Wednesday, March 28, 2018 8:44 AM
To: Roberts, Alex S.; discuss-gnuradio@gnu.org
Subject: Re: [Discuss-gnuradio] Meaning of header_payload_demux0 - Parser returned #f

 

Hi Alex - If you want to share your GRC file with me (privately) and/or the list, we'll see what we can figure out. Guessing it's an OFDM sync issue, since GR's OFDM implementation is for async messages, and those are on a message by message basis. - MLD

 

On Tue, Mar 27, 2018, at 8:50 PM, Roberts, Alex S. wrote:

Michael that provides insight into the error, unfortunately it does not explain the behavior of the example. The example uses the tx_packet and rx_packet hierarchical blocks. The output of the tx is routed to the input of the rx. I bypassed the example channel model and I’m not using hardware at the moment, so I would expect the example would have little issue with poor SNR and would maintain sync.