Re: [Discuss-gnuradio] FEC: Convolutional Encoder Gnuradio and Matlab: different results

2017-03-22 Thread Dan CaJacob
Hi Emanuel, Try bit-reversing the polynomials. By the way, even though the block definitions can take any python representation of the numbers. For instance 91 decimal is 0x5B (hex) and 091 (octal) in python. I often use the leading zero octal notation for stuff like this since the weirdos who

Re: [Discuss-gnuradio] FEC: Convolutional Encoder Gnuradio and Matlab: different results

2017-03-22 Thread Usman Haider
Hi Emanuel, Maybe you find following thread useful. http://lists.gnu.org/archive/html/discuss-gnuradio/2015-09/msg00404.html -- Usman On Wed, Mar 22, 2017 at 1:07 PM, wrote: > Hi together, > > > > I’m using the FEC Async Encoder with the CC Encoder Definition. > Input/Output are unpacked and

[Discuss-gnuradio] FEC: Convolutional Encoder Gnuradio and Matlab: different results

2017-03-22 Thread Emanuel.Staudinger
Hi together, I'm using the FEC Async Encoder with the CC Encoder Definition. Input/Output are unpacked and I use the terminated behavior. In Gnuradio the polynomials for the CC Encoder Definition are defined on a base of 10, and not as octals like in MATLAB, right? I tried the following: 1 bit