Re: [Discuss-gnuradio] Post Binary Slicer question

[madengr]

I guess I'm confused then.  I'm using the hex FIFO dump as I described to
examine AX.25 packets one bit at a time.  Since the output of the slicer is
a byte whose LSB is the only thing you are interested in, I believe you can
use the unpacked-to-packed block to strip off the LSB from 8 bytes and pack
those into a single byte; at least I'm using packed-to-unpacked to feed a
binary file to a modulator so the reverse should work.  Run that into a FIFO
and dump with xxd - bits.  Baudline is also handy for visually scrolling
through the binary stream, although it's visually irritating with only one
sample per symbol.

Lou



Jay Radcliffe wrote
> The protocol is unknown at this time.  I need to see the packets to figure
> some of this out.
> 
> Ideally, I would like to see the entire packet (including the preamble and
> sync word) to start to work my way to the format of the packets from
> there.
>  I am using the power squelch with the gate to limit the captures to just
> when a signal is over a certain strength. In a perfect world, I would like
> to have "Binary Slicer" -> "File Sink" where the file contents are the
> binary stream (10101010101010 not to be confused for a binary file) or hex
> output (0xAA 0xAA).  I could probably tag the preamble in with the
> Correlate Access Code?
> 
> Jay Radcliffe
> Twitter: @jradcliffe02
> E-Mail: 

> jay.radcliffe@

> LinkedIn + Resume: http://www.linkedin.com/in/jradcliffe02





--
View this message in context: 
http://gnuradio.4.n7.nabble.com/Post-Binary-Slicer-question-tp47828p47888.html
Sent from the GnuRadio mailing list archive at Nabble.com.