Re: [Discuss-gnuradio] problem in executing benchmark_tx.py

[Jason Uher]

On Mon, Feb 1, 2010 at 5:22 AM, ashwini <address@hidden> wrote:
> Can anyone tell me what is wrong in my approach, (why junk data is getting
> written) and how to resolve this issue.


We need more information on your set up to get an idea of what might
be going wrong (http://gnuradio.org/redmine/wiki/gnuradio/ReportingErrors).
 For example, what do you mean by 'junk data being written'? The
benchmark files don't really write any data, they simply check if the
frames were received correctly and erase them.  Even if you use the
--log option I think you will only get the demodulated bits back in a
binary fashion, not a direct copy of 'payload.dat', but you aren't
even doing that according to your commands.

I would spend some time looking through the appropriate files to
understand what the receiver is doing so you can find out where to
appropriately save your file to disk:
http://gnuradio.org/redmine/repositories/changes/gnuradio/gnuradio-examples/python/digital/benchmark_rx.py
http://gnuradio.org/redmine/repositories/changes/gnuradio/gnuradio-examples/python/digital/usrp_receive_path.py
http://gnuradio.org/redmine/repositories/entry/gnuradio/gnuradio-core/src/python/gnuradio/blks2impl/gmsk.py

The logging is done in the modulation specific files (gmsk.py), so you
don't really have anything like framing or symbol->bit conversion done
yet, you will probably have to add a file sink later in the chain to
get the final data out (maybe there is an existing option for this?).

Jason