[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Discuss-gnuradio] grc Python generation error: QT GUI time, other sync
[Discuss-gnuradio] grc Python generation error: QT GUI time, other sync blocks not being called correctly
Sat, 01 Jun 2019 20:28:24 +0000
Evolution 3.32.2 (3.32.2-1.fc30)
This is for a version of gnuradio from git on May 24, 2019.
If I connect my block to a qtgui time sink in grc it grc displays the
input port as "in0" but the time_sink_c_impl.cc code declares the
message port as "in," causing execution of the flowgraph to fail.
I've found two short term options: 1. modify time_sink_c_impl.cc to
accept "in0" as:
// setup PDU handling input port
I suspect that this will break things if I add more input ports.
Option 2: Modify the python code that grc generates
This isn't a great solution since it has to be done every time the flow
graph changes. I suspect that a better solution would be to get grc to
make flow graphs that understand the input port name. I just want
through the process of porting my OOT modules from xml to yml and don't
have this problem because I specified the port names explicitly with
the "-label" field. I looked at doing this with the qt gui blocks but
they're using $variables beyond my yml skills.
Am I missing something in making my flowgraphs, or is this just a case
of imperfect automated xml-yml porting that will get corrected soon.
|[Prev in Thread]
||[Next in Thread]|
- [Discuss-gnuradio] grc Python generation error: QT GUI time, other sync blocks not being called correctly,