Re: [Discuss-gnuradio] Receiving errors with Viterbi decoder block/Decoding AIM spacecraft

2016-01-30 Thread Marcus Müller
Hi Michael, I'm just jumping in to advertise a GRC feature: if you use the "screenshot" menu item (identical to the printer button in the tool bar), you get a png of your canvas, rather than a picture of your UI and everything. Best regards, Marcus On 01/30/2016 05:50 PM, Michael Sabino wrote: >

Re: [Discuss-gnuradio] Receiving errors with Viterbi decoder block/Decoding AIM spacecraft

2016-01-30 Thread Michael Sabino
Here's an image of the flowgraph, in addition: http://i.imgur.com/45B2MyL.png Michael On 1/30/16, Michael Sabino wrote: > I abandoned the FSM constructor and decided to just use the decode > CCSDS27 block. > > > Michael > > On 1/30/16, Achilleas Anastasopoulos wrote: >> Michael, >> >> I haven'

Re: [Discuss-gnuradio] Receiving errors with Viterbi decoder block/Decoding AIM spacecraft

2016-01-30 Thread Michael Sabino
I abandoned the FSM constructor and decided to just use the decode CCSDS27 block. Michael On 1/30/16, Achilleas Anastasopoulos wrote: > Michael, > > I haven't seen your flowgraph, but as I wrote in my previous email you are > using the fsm constructor probably in the wrong way: > > You are conf

Re: [Discuss-gnuradio] Receiving errors with Viterbi decoder block/Decoding AIM spacecraft

2016-01-30 Thread Achilleas Anastasopoulos
Michael, I haven't seen your flowgraph, but as I wrote in my previous email you are using the fsm constructor probably in the wrong way: You are confusing the (n,k,K) parameters of a CC. k = number of input bits per period n = number of output bits per period K = constraint length of the code (re

Re: [Discuss-gnuradio] Receiving errors with Viterbi decoder block/Decoding AIM spacecraft

2016-01-29 Thread Michael Sabino
I'm going to post my flowgraph. I have added a CCSDS decoder block. Please, if you can, provide input on how to improve the amount of successfully decoded data with a short wave file and a doppler shifting BPSK carrier. My .wav file: http://1drv.ms/1bS3KxX and here is my gnuradio flowgraph: http:

Re: [Discuss-gnuradio] Receiving errors with Viterbi decoder block

2016-01-27 Thread Achilleas Anastasopoulos
The problem is not the length 2048 but the way you use the fsm constructor trellis.fsm(2,7,[79,109]) You are trying to create an FSM for a (7,2) CC. This means you need to provide a vector of 2x7 integers, each representing the generator polynomial between the i-th input (i=0,1) to the j-th ou

Re: [Discuss-gnuradio] Receiving errors with Viterbi decoder block

2016-01-26 Thread Michael Sabino
How do I determine the block size? I tried several different large/small values and they return similar errors. Thanks, Michael On 1/26/16, Marcus Müller wrote: > Hi Michael, > > On 01/26/2016 08:38 PM, Michael Sabino wrote: >> trellis.viterbi_b(trellis.fsm(2,7,[79,109]), 2048, 0, -1) > > 204

Re: [Discuss-gnuradio] Receiving errors with Viterbi decoder block

2016-01-26 Thread Marcus Müller
Hi Michael, On 01/26/2016 08:38 PM, Michael Sabino wrote: > trellis.viterbi_b(trellis.fsm(2,7,[79,109]), 2048, 0, -1) 2048 looks wrong. Best regards, Marcus ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/list

[Discuss-gnuradio] Receiving errors with Viterbi decoder block

2016-01-26 Thread Michael Sabino
I am receiving the following errors with the Viterbi decoding block: Number -2013265152 requires more than 31 digits.Number -2013264896 requires more than 31 digits.Number -2013264640 requires more than 31 digits.Traceback (most recent call last): File "C:\Users\Michael\Desktop\top_block.py", li