Re: [Discuss-gnuradio] Post Binary Slicer question

2014-05-24 Thread Andre Puschmann
Hi, as I have mentioned a few weeks ago I was working on a GR module that can be used for receiving and decoding messages sent from TI CC11xx based devices. I've now pushed a first version of it to my github repo [1]. It features a 2-FSK receiver entirely built from stock GR blocks and a deframer

Re: [Discuss-gnuradio] Post Binary Slicer question

2014-05-02 Thread Andre Puschmann
Hi, By chance I am also working on an OOT module for a CC1100-based device. I started out with a Python version as Michael also suggested, but now I am migrating it to C++. I actually plan working on it during the EU Hackfest next week in Karlsruhe. John, Jay, perhaps we can create a single modul

Re: [Discuss-gnuradio] Post Binary Slicer question

2014-04-30 Thread Michael Ossmann
Oops. I forgot part of it: def advance(lfsr, num): for i in range(num): nextbit = (lfsr & 1) ^ ((lfsr >> 5) & 1) lfsr >>= 1 lfsr |= (nextbit << 8) return lfsr On Wed, Apr 30, 2014 at 10:38:54AM -0600, Michael Ossmann wrote: > > Coo

Re: [Discuss-gnuradio] Post Binary Slicer question

2014-04-30 Thread John Malsbury
Of course - I forgot whitening as a nother parameter to be tried. Thanks! -John On Wed, Apr 30, 2014 at 9:38 AM, Michael Ossmann wrote: > Cool! In case either of you doesn't have this yet, here is an > implementation of the CC11xx whitening algorithm: > > # XOR the output of this with a pack

Re: [Discuss-gnuradio] Post Binary Slicer question

2014-04-30 Thread Michael Ossmann
Cool! In case either of you doesn't have this yet, here is an implementation of the CC11xx whitening algorithm: # XOR the output of this with a packet def whitening(length): lfsr = 0x1ff white = 0 for i in range(length): white <<= 8 white |=

Re: [Discuss-gnuradio] Post Binary Slicer question

2014-04-30 Thread John Malsbury
Jay, As it turns out I am working on an out-of-tree module to work with the CC1101, which I think I'll be able to release. The number of possible formats for the frame are relatively few if you know they are using CRC and you know the packets aren't fixed length. (use_sequence_number?, use_addres

Re: [Discuss-gnuradio] Post Binary Slicer question

2014-04-30 Thread Michael Ossmann
My workflow in this case is to dump the output of Correlate Access Code to a file and then write small Python programs to read that file. Yes, the tools within GNU Radio for handling this kind of thing are getting better, but they still haven't been as useful (to me) as a few lines of Python here

Re: [Discuss-gnuradio] Post Binary Slicer question

2014-04-30 Thread Jay Radcliffe
Maybe I should rephrase: I don't know the entire protocol. I know there is a preamble, and I know the sync word. I know the packets are not fixed length, I know there is a CRC. This can all be determined from looking at the register settings for the CC1101 chip. The format of the data portion of

Re: [Discuss-gnuradio] Post Binary Slicer question

2014-04-30 Thread John Malsbury
Jay, If you stream the output of the correlate access code to file, and you leave them unpacked, Bit 1 being set will show where the sync word is (I think the bit after). Of course Bit 0 will be the data. This assumes you're using correlate access code, and not "correlate access code - tag". Thi

Re: [Discuss-gnuradio] Post Binary Slicer question

2014-04-30 Thread 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 pa

Re: [Discuss-gnuradio] Post Binary Slicer question

2014-04-30 Thread Martin Braun
On 29.04.2014 22:43, Jay Radcliffe wrote: The protocol is unknown at this time. I need to see the packets to figure some of this out. Jay, does the QT GUI Time Raster sink help you in any way? M Ideally, I would like to see the entire packet (including the preamble and sync word) to start

Re: [Discuss-gnuradio] Post Binary Slicer question

2014-04-29 Thread Jay Radcliffe
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 t

Re: [Discuss-gnuradio] Post Binary Slicer question

2014-04-27 Thread John Malsbury
Jay, Thanks for the inquiry. Is there a specific protocol or format you are trying to work with? Are the frame size fixed in length or variable? The answers to these questions will dictate whether you can use an existing block or if you will need to write your own. Writing a block to parse thi

Re: [Discuss-gnuradio] Post Binary Slicer question

2014-04-27 Thread madengr
mkfifo my_fifo.bin hexdump my_fifo.bin Point your file sink to the my_fifo.bin and turn off the buffering. It will then dump the data to the terminal in real time. Lou KD4HSO Jay Radcliffe wrote > I have a question about handling data after binary slicing in the > demodulation portion of hand

[Discuss-gnuradio] Post Binary Slicer question

2014-04-27 Thread Jay Radcliffe
I have a question about handling data after binary slicing in the demodulation portion of handling a signal. Currently I am taking that data and pushing it through the Correlate Access Code block then into a file sink. This produces a data file. I didn't know if someone could tell me a block or me