Re: [Discuss-gnuradio] Debugging ControlPort/Thrift problem (Re: costas ambiguity and correlate-and-sync block in qpsk)

On Sun, 2016-04-03 at 13:01 -0400, Andy Walls wrote: > >On April 3, 2016 11:31:02 AM EDT, Tom Rondeau wrote: > >>On Sun, Apr 3, 2016 at 11:27 AM, Landsman, Arik wrote: [snip] > Here is some good info on how GRNURadio's control port works at a > >>high > level: >

Re: [Discuss-gnuradio] Debugging ControlPort/Thrift problem (Re: costas ambiguity and correlate-and-sync block in qpsk)

fair enough :) From: Andy Walls [a...@silverblocksystems.net] Sent: Sunday, April 03, 2016 1:01 PM To: Landsman, Arik; Tom Rondeau Cc: discuss-gnuradio@gnu.org Subject: RE: Debugging ControlPort/Thrift problem (Re: [Discuss-gnuradio] costas ambiguity and

Re: [Discuss-gnuradio] Debugging ControlPort/Thrift problem (Re: costas ambiguity and correlate-and-sync block in qpsk)

Well, on that machine (Fedora 20) I never built thrift. No problem. ;) On April 3, 2016 12:51:31 PM EDT, "Landsman, Arik" wrote: >setting port=0 in thrift.conf did the trick, GRC now runs all >flowgraphs as expected. > >Andy, still at odds on how you got yours to

Re: [Discuss-gnuradio] Debugging ControlPort/Thrift problem (Re: costas ambiguity and correlate-and-sync block in qpsk)

setting port=0 in thrift.conf did the trick, GRC now runs all flowgraphs as expected. Andy, still at odds on how you got yours to work.. did you modify thrift.conf in any way? From: Andy Walls [a...@silverblocksystems.net] Sent: Sunday, April 03, 2016

Re: [Discuss-gnuradio] Debugging ControlPort/Thrift problem (Re: costas ambiguity and correlate-and-sync block in qpsk)

Hmm. Maybe GRC trying to evaluate the block for the sake of values in other blocks is spawning and keeping the mini flowgraph open. Weird. On April 3, 2016 11:31:02 AM EDT, Tom Rondeau wrote: >On Sun, Apr 3, 2016 at 11:27 AM, Landsman, Arik >

Re: [Discuss-gnuradio] Debugging ControlPort/Thrift problem (Re: costas ambiguity and correlate-and-sync block in qpsk)

On Sun, Apr 3, 2016 at 11:27 AM, Landsman, Arik wrote: > Hi Tom, > > Where is thrift.conf usually located?.. > > Thanks, > Arik > In ~/.gnuradio/thrift.conf And interesting observation about having to remove Modulate Vector completely. That might be the same problem

Re: [Discuss-gnuradio] Debugging ControlPort/Thrift problem (Re: costas ambiguity and correlate-and-sync block in qpsk)

Hi Tom, Where is thrift.conf usually located?.. Thanks, Arik From: trond...@trondeau.com [trond...@trondeau.com] on behalf of Tom Rondeau [t...@trondeau.com] Sent: Sunday, April 03, 2016 11:22 AM To: Andy Walls Cc: Landsman, Arik; discuss-gnuradio@gnu.org

Re: [Discuss-gnuradio] Debugging ControlPort/Thrift problem (Re: costas ambiguity and correlate-and-sync block in qpsk)

On Sun, Apr 3, 2016 at 8:49 AM, Andy Walls wrote: > > > Otherwise, you didn't drop a control port related block on the > > flowgraph did you? > > > Here is some good info on how GRNURadio's control port works at a high > level: >

Re: [Discuss-gnuradio] Debugging ControlPort/Thrift problem (Re: costas ambiguity and correlate-and-sync block in qpsk)

Hi Andy, So the issue is with the modulate vector block like you suggested. Disabling it alone is not enough, had to be removed altogether and GRC restarted. Only then the flowgraph runs ok. how did you menage to run it on your setup?.. different Thrift config? To this end, how would I go

Re: [Discuss-gnuradio] Debugging ControlPort/Thrift problem (Re: costas ambiguity and correlate-and-sync block in qpsk)

error still there in Rx_syncd_3.grc. Feels like a version or dependencies issue on the GRC side.. With the .py running, going to use Rx_syncd_2.grc for now as a reference to copy essential blocks to a working (earlier) version of Rx_syncd.grc. if this works I'll continue off of the other

Re: [Discuss-gnuradio] Debugging ControlPort/Thrift problem (Re: costas ambiguity and correlate-and-sync block in qpsk)

Hi Andy, Looks like the issue is connected to the .grc like you mentioned - without opening Rx_syncd_2.grc, the Rx_syncd.py you attached earlier runs fine. Just opening the Rx_syncd_2.grc, w/o ever running or generating a new .py, while attempting to run any other .grc gives the same error.