Re: [Discuss-gnuradio] Python Unit Test with message ports - "Could not find port"

[Steven Knudsen]

 I tried digging into gr-blocks to look for
  differences, but so far none that I can
  see.


Sorry this is kind of long,
  but it’s a weird problem, weird because my
  stuff works fine in GRC!?!


regards, and thanks,


steven


















  
  

  
From:
Marcus
  Müller
  
  
    Subject:
        Re:
  [Discuss-gnuradio] Python Unit
      Test with message ports - "Could
  not find port"
  
  
Date:
Wed, 11
  Jan 2017 14:49:40 +0100
  
  
User-agent:
Mozilla/5.0
  (X11; Linux x86_64; rv:45.0)
  Gecko/20100101 Thunderbird/45.2.0
  

  
  
  

  
Hi Steven, 
that's strange
  indeed. In various ways. 
Could you tell us:1. where do you
  register the message port?
  Could you copy that
  exact line?
  2. could you copy
  both message_connect lines
  from the GRC-generated and
  your unit test python?Thanks,Marcus

On
  01/11/2017 01:35 AM, Steven
  Knudsen wrote:

Hi all,
  
  
  I am trying to
write a unit test for a
message-only block, let’s
call it “foo”, that has an
input message port
“generate". When I use the
block in GRC, everything is
fine. I can connect its
message ports to standard
GNU Radio message blocks,
like message_strobe and
message_debug with no
problems.
  
  
  However, when I
try and do the same in a
Python unit test, I get the
message
  
  
  Could not find
   

Re: [Discuss-gnuradio] Python Unit Test with message ports - "Could not find port"

[Marcus Müller]

;>> unit test and modified only by changing ‘self’ to self.tb’. When I
>>>> run that code, I get the could not find port error. 
>>>>
>>>> If I modify that code to connect only the output of the Message
>>>> Strobe to the print port of the Message Debug, it works.
>>>>
>>>> That is, this does not work,
>>>> self.tb.msg_connect((self.blocks_message_strobe_0,
>>>> 'strobe'), (self.jitc_random_sequenced_pdu_0, 'generate'))
>>>> #self.tb.msg_connect((self.blocks_message_strobe_0,
>>>> 'strobe'), (self.blocks_message_debug_0, 'print'))
>>>> self.tb.msg_connect((self.jitc_random_sequenced_pdu_0,
>>>> 'pdus'), (self.blocks_message_debug_0, 'print'))
>>>>
>>>>
>>>> But this does work
>>>>
>>>> #self.tb.msg_connect((self.blocks_message_strobe_0,
>>>> 'strobe'), (self.jitc_random_sequenced_pdu_0, 'generate'))
>>>> self.tb.msg_connect((self.blocks_message_strobe_0,
>>>> 'strobe'), (self.blocks_message_debug_0, 'print'))
>>>> #self.tb.msg_connect((self.jitc_random_sequenced_pdu_0,
>>>> 'pdus'), (self.blocks_message_debug_0, 'print'))
>>>>
>>>> Last observation is that if I replace my random_sequenced_pdu with
>>>> block’s random_pdu,it all works. So, it’s definitely something with
>>>> my module. Is something not generated via/by swig maybe? I tried
>>>> digging into gr-blocks to look for differences, but so far none
>>>> that I can see.
>>>>
>>>> Sorry this is kind of long, but it’s a weird problem, weird because
>>>> my stuff works fine in GRC!?!
>>>>
>>>> regards, and thanks,
>>>>
>>>> steven
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> 
>>>>> *From*:   Marcus Müller
>>>>> *Subject*:Re: [Discuss-gnuradio] Python Unit Test with message
>>>>> ports - "Could not find port"
>>>>> *Date*:   Wed, 11 Jan 2017 14:49:40 +0100
>>>>> *User-agent*: Mozilla/5.0 (X11; Linux x86_64; rv:45.0)
>>>>> Gecko/20100101 Thunderbird/45.2.0
>>>>>
>>>>> 
>>>>>
>>>>> Hi Steven, 
>>>>>
>>>>> that's strange indeed. In various ways. 
>>>>>
>>>>> Could you tell us:
>>>>>
>>>>> 1. where do you register the message port? Could you copy
>>>>> that exact line?
>>>>> 2. could you copy both message_connect lines from the
>>>>> GRC-generated and your unit test python?
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Marcus
>>>>>
>>>>> On 01/11/2017 01:35 AM, Steven Knudsen wrote:
>>>>>> Hi all,
>>>>>>
>>>>>> I am trying to write a unit test for a message-only block, let’s
>>>>>> call it “foo”, that has an input message port “generate". When I
>>>>>> use the block in GRC, everything is fine. I can connect its
>>>>>> message ports to standard GNU Radio message blocks, like
>>>>>> message_strobe and message_debug with no problems.
>>>>>>
>>>>>> However, when I try and do the same in a Python unit test, I get
>>>>>> the message
>>>>>>
>>>>>> Could not find port: generate in:
>>>>>> generate
>>>>>> system
>>>>>>
>>>>>> If, for example, in the same unit test I connect the
>>>>>> message_strobe with message_debug, all is well.
>>>>>>
>>>>>> If I then connect message_strobe to foo, I get the error above.
>>>>>>
>>>>>> I double checked that the message port declarations are the same
>>>>>> as you find in a block like message_strobe. 
>>>>>>
>>>>>> I double checked the syntax of msg_connect, making sure it looks
>>>>>> exactly the same as it does in the GRC generated Python file.
>>>>>>
>>>>>> Anyone seen this recently? I have found some references by
>>>>>> searching online, but nothing that has helped.
>>>>>>
>>>>>> Thanks very much!
>>>>>>
>>>>>> steven
>>>>>
>>>>
>>>
>>
>

___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] Python Unit Test with message ports - "Could not find port"

[Steven Knudsen]

ut this does work
>>> 
>>> #self.tb.msg_connect((self.blocks_message_strobe_0, 'strobe'), 
>>> (self.jitc_random_sequenced_pdu_0, 'generate'))
>>> self.tb.msg_connect((self.blocks_message_strobe_0, 'strobe'), 
>>> (self.blocks_message_debug_0, 'print'))
>>> #self.tb.msg_connect((self.jitc_random_sequenced_pdu_0, 'pdus'), 
>>> (self.blocks_message_debug_0, 'print'))
>>> 
>>> Last observation is that if I replace my random_sequenced_pdu with block’s 
>>> random_pdu,it all works. So, it’s definitely something with my module. Is 
>>> something not generated via/by swig maybe? I tried digging into gr-blocks 
>>> to look for differences, but so far none that I can see.
>>> 
>>> Sorry this is kind of long, but it’s a weird problem, weird because my 
>>> stuff works fine in GRC!?!
>>> 
>>> regards, and thanks,
>>> 
>>> steven
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>>> 
>>>> From:  Marcus Müller
>>>> Subject:   Re: [Discuss-gnuradio] Python Unit Test with message ports - 
>>>> "Could not find port"
>>>> Date:  Wed, 11 Jan 2017 14:49:40 +0100
>>>> User-agent:Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 
>>>> Thunderbird/45.2.0
>>>> Hi Steven, 
>>>> that's strange indeed. In various ways. 
>>>> Could you tell us:
>>>> 
>>>> 1. where do you register the message port? Could you copy that exact 
>>>> line?
>>>> 2. could you copy both message_connect lines from the GRC-generated 
>>>> and your unit test python?
>>>> 
>>>> Thanks,
>>>> 
>>>> Marcus
>>>> On 01/11/2017 01:35 AM, Steven Knudsen wrote:
>>>>> Hi all,
>>>>> 
>>>>> I am trying to write a unit test for a message-only block, let’s call it 
>>>>> “foo”, that has an input message port “generate". When I use the block in 
>>>>> GRC, everything is fine. I can connect its message ports to standard GNU 
>>>>> Radio message blocks, like message_strobe and message_debug with no 
>>>>> problems.
>>>>> 
>>>>> However, when I try and do the same in a Python unit test, I get the 
>>>>> message
>>>>> 
>>>>> Could not find port: generate in:
>>>>> generate
>>>>> system
>>>>> 
>>>>> If, for example, in the same unit test I connect the message_strobe with 
>>>>> message_debug, all is well.
>>>>> 
>>>>> If I then connect message_strobe to foo, I get the error above.
>>>>> 
>>>>> I double checked that the message port declarations are the same as you 
>>>>> find in a block like message_strobe. 
>>>>> 
>>>>> I double checked the syntax of msg_connect, making sure it looks exactly 
>>>>> the same as it does in the GRC generated Python file.
>>>>> 
>>>>> Anyone seen this recently? I have found some references by searching 
>>>>> online, but nothing that has helped.
>>>>> 
>>>>> Thanks very much!
>>>>> 
>>>>> steven
>>> 
>> 
> 

___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] Python Unit Test with message ports - "Could not find port"

[Steven Knudsen]

Thanks very much, Marcus, for the help.

As requested, I used

self.tb.msg_connect((self.blocks_message_strobe_0, 
pmt.string_to_symbol('strobe')), (self.jitc_random_sequenced_pdu_0, 
pmt.string_to_symbol('generate')))

Sadly, no change in that the “Could not find port” problem persists.

To be sure, I also applied your suggestion with the gr-blocks random_pdu block 
in the same source (much as I did below) and used

self.tb.msg_connect((self.blocks_message_strobe_0, 
pmt.string_to_symbol('strobe')), (self.jitc_random_pdu_0, 
pmt.string_to_symbol('generate')))

which worked just fine.

I’ll continue to compare the gr-blocks implementation with my OOT module. I 
would still like to think there is a difference somewhere in the source or a 
script or something, but I can’t see how that would explain why my OOT works 
fine in GRC.

Last, I did try to follow the logic/code that tracks the registered ports 
starting with gnuradio-runtime/lib/flowgraph.cc <http://flowgraph.cc/>, but I 
became a bit lost as things moved through swig…

BTW, my GR version is 3.7.10.1

Again, thanks for your help!

steven


> On Jan 12, 2017, at 03:39, Marcus Müller <marcus.muel...@ettus.com> wrote:
> 
> Hi Steven,
> 
> On 12.01.2017 02:21, Steven Knudsen wrote:
>> You worry me with your “various ways” comment :-/
> That's what I do: I comment and worry people. And I just finished my comment.
> No, really, I was just surprised that a) it doesn't work and b) it claims "a 
> is not in set {a,b}". That feels ever so slightly wrong.
>> 
>> All I have done is extended the random_pdu from gr-blocks by including a 
>> sequence number in the PDU. So, the constructor is where the message ports 
>> are registered and is identical to the random_pdu constructor. I’ve attached 
>> a snippet (rsp_constructor.snippet) that contains my exact code.
> Thanks, OK the most relevant line here is
> 
>   message_port_register_in(pmt::mp("generate"));
> 
> which looks right; I really sense shenanigans here. So, to narrow this down: 
> 
> Can you do a 
> 
> self.tb.msg_connect((self.blocks_message_strobe_0, 
> pmt.string_to_symbol('strobe')), (self.jitc_random_sequenced_pdu_0, 
> pmt.string_to_symbol('generate')))
> 
> to rule out any strangenesses that the whole behind-the-scenery PMT 
> conversion does?
> 
> Best regards,
> Marcus
> 
>> 
>> My version works the same as the original when run from GRC. I’ve attached a 
>> screencap of the simple flowgraph used to verify this. I’ve also attached 
>> the generated python. 
>> 
>> I took the main code from that generated python and added to my unit test 
>> and modified only by changing ‘self’ to self.tb’. When I run that code, I 
>> get the could not find port error. 
>> 
>> If I modify that code to connect only the output of the Message Strobe to 
>> the print port of the Message Debug, it works.
>> 
>> That is, this does not work,
>> self.tb.msg_connect((self.blocks_message_strobe_0, 'strobe'), 
>> (self.jitc_random_sequenced_pdu_0, 'generate'))
>> #self.tb.msg_connect((self.blocks_message_strobe_0, 'strobe'), 
>> (self.blocks_message_debug_0, 'print'))
>> self.tb.msg_connect((self.jitc_random_sequenced_pdu_0, 'pdus'), 
>> (self.blocks_message_debug_0, 'print'))
>> 
>> 
>> But this does work
>> 
>> #self.tb.msg_connect((self.blocks_message_strobe_0, 'strobe'), 
>> (self.jitc_random_sequenced_pdu_0, 'generate'))
>> self.tb.msg_connect((self.blocks_message_strobe_0, 'strobe'), 
>> (self.blocks_message_debug_0, 'print'))
>> #self.tb.msg_connect((self.jitc_random_sequenced_pdu_0, 'pdus'), 
>> (self.blocks_message_debug_0, 'print'))
>> 
>> Last observation is that if I replace my random_sequenced_pdu with block’s 
>> random_pdu,it all works. So, it’s definitely something with my module. Is 
>> something not generated via/by swig maybe? I tried digging into gr-blocks to 
>> look for differences, but so far none that I can see.
>> 
>> Sorry this is kind of long, but it’s a weird problem, weird because my stuff 
>> works fine in GRC!?!
>> 
>> regards, and thanks,
>> 
>> steven
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>>> 
>>> From:   Marcus Müller
>>> Subject:Re: [Discuss-gnuradio] Python Unit Test with message ports - 
>>> "Could not find port"
>>> Date:   Wed, 11 Jan 2017 14:49:40 +0100
>>> User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 
>>> Thunderbird/45.2.0
>>> Hi Steven, 
>>> t

Re: [Discuss-gnuradio] Python Unit Test with message ports - "Could not find port"

[Marcus Müller]

Hi Steven,

On 12.01.2017 02:21, Steven Knudsen wrote:
> You worry me with your “various ways” comment :-/
That's what I do: I comment and worry people. And I just finished my
comment.
No, really, I was just surprised that a) it doesn't work and b) it
claims "a is not in set {a,b}". That feels ever so slightly wrong.
>
> All I have done is extended the random_pdu from gr-blocks by including
> a sequence number in the PDU. So, the constructor is where the message
> ports are registered and is identical to the random_pdu constructor.
> I’ve attached a snippet (rsp_constructor.snippet) that contains my
> exact code.
Thanks, OK the most relevant line here is

  message_port_register_in(pmt::mp("generate"));

which looks right; I really sense shenanigans here. So, to narrow this
down:

Can you do a

self.tb.msg_connect((self.blocks_message_strobe_0,
pmt.string_to_symbol('strobe')), (self.jitc_random_sequenced_pdu_0,
pmt.string_to_symbol('generate')))

to rule out any strangenesses that the whole behind-the-scenery PMT
conversion does?

Best regards,
Marcus

>
> My version works the same as the original when run from GRC. I’ve
> attached a screencap of the simple flowgraph used to verify this. I’ve
> also attached the generated python. 
>
> I took the main code from that generated python and added to my unit
> test and modified only by changing ‘self’ to self.tb’. When I run that
> code, I get the could not find port error. 
>
> If I modify that code to connect only the output of the Message Strobe
> to the print port of the Message Debug, it works.
>
> That is, this does not work,
> self.tb.msg_connect((self.blocks_message_strobe_0, 'strobe'),
> (self.jitc_random_sequenced_pdu_0, 'generate'))
> #self.tb.msg_connect((self.blocks_message_strobe_0, 'strobe'),
> (self.blocks_message_debug_0, 'print'))
> self.tb.msg_connect((self.jitc_random_sequenced_pdu_0,
> 'pdus'), (self.blocks_message_debug_0, 'print'))
>
>
> But this does work
>
> #self.tb.msg_connect((self.blocks_message_strobe_0, 'strobe'),
> (self.jitc_random_sequenced_pdu_0, 'generate'))
> self.tb.msg_connect((self.blocks_message_strobe_0, 'strobe'),
> (self.blocks_message_debug_0, 'print'))
> #self.tb.msg_connect((self.jitc_random_sequenced_pdu_0,
> 'pdus'), (self.blocks_message_debug_0, 'print'))
>
> Last observation is that if I replace my random_sequenced_pdu with
> block’s random_pdu,it all works. So, it’s definitely something with my
> module. Is something not generated via/by swig maybe? I tried digging
> into gr-blocks to look for differences, but so far none that I can see.
>
> Sorry this is kind of long, but it’s a weird problem, weird because my
> stuff works fine in GRC!?!
>
> regards, and thanks,
>
> steven
>
>
>
>
>
>
>
>
>
>> ----
>> *From*:  Marcus Müller
>> *Subject*:   Re: [Discuss-gnuradio] Python Unit Test with message
>> ports - "Could not find port"
>> *Date*:  Wed, 11 Jan 2017 14:49:40 +0100
>> *User-agent*:Mozilla/5.0 (X11; Linux x86_64; rv:45.0)
>> Gecko/20100101 Thunderbird/45.2.0
>>
>> 
>>
>> Hi Steven, 
>>
>> that's strange indeed. In various ways. 
>>
>> Could you tell us:
>>
>> 1. where do you register the message port? Could you copy that
>> exact line?
>> 2. could you copy both message_connect lines from the
>> GRC-generated and your unit test python?
>>
>> Thanks,
>>
>> Marcus
>>
>> On 01/11/2017 01:35 AM, Steven Knudsen wrote:
>>> Hi all,
>>>
>>> I am trying to write a unit test for a message-only block, let’s
>>> call it “foo”, that has an input message port “generate". When I use
>>> the block in GRC, everything is fine. I can connect its message
>>> ports to standard GNU Radio message blocks, like message_strobe and
>>> message_debug with no problems.
>>>
>>> However, when I try and do the same in a Python unit test, I get the
>>> message
>>>
>>> Could not find port: generate in:
>>> generate
>>> system
>>>
>>> If, for example, in the same unit test I connect the message_strobe
>>> with message_debug, all is well.
>>>
>>> If I then connect message_strobe to foo, I get the error above.
>>>
>>> I double checked that the message port declarations are the same as
>>> you find in a block like message_strobe. 
>>>
>>> I double checked the syntax of msg_connect, making sure it looks
>>> exactly the same as it does in the GRC generated Python file.
>>>
>>> Anyone seen this recently? I have found some references by searching
>>> online, but nothing that has helped.
>>>
>>> Thanks very much!
>>>
>>> steven
>>
>

___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] Python Unit Test with message ports - "Could not find port"

[Steven Knudsen]

Hi Marcus,You worry me with your “various ways” comment :-/All I have done is extended the random_pdu from gr-blocks by including a sequence number in the PDU. So, the constructor is where the message ports are registered and is identical to the random_pdu constructor. I’ve attached a snippet (rsp_constructor.snippet) that contains my exact code.My version works the same as the original when run from GRC. I’ve attached a screencap of the simple flowgraph used to verify this. I’ve also attached the generated python. I took the main code from that generated python and added to my unit test and modified only by changing ‘self’ to self.tb’. When I run that code, I get the could not find port error. If I modify that code to connect only the output of the Message Strobe to the print port of the Message Debug, it works.That is, this does not work,        self.tb.msg_connect((self.blocks_message_strobe_0, 'strobe'), (self.jitc_random_sequenced_pdu_0, 'generate'))#        self.tb.msg_connect((self.blocks_message_strobe_0, 'strobe'), (self.blocks_message_debug_0, 'print'))        self.tb.msg_connect((self.jitc_random_sequenced_pdu_0, 'pdus'), (self.blocks_message_debug_0, 'print'))But this does work#        self.tb.msg_connect((self.blocks_message_strobe_0, 'strobe'), (self.jitc_random_sequenced_pdu_0, 'generate'))        self.tb.msg_connect((self.blocks_message_strobe_0, 'strobe'), (self.blocks_message_debug_0, 'print'))#        self.tb.msg_connect((self.jitc_random_sequenced_pdu_0, 'pdus'), (self.blocks_message_debug_0, 'print'))Last observation is that if I replace my random_sequenced_pdu with block’s random_pdu,it all works. So, it’s definitely something with my module. Is something not generated via/by swig maybe? I tried digging into gr-blocks to look for differences, but so far none that I can see.Sorry this is kind of long, but it’s a weird problem, weird because my stuff works fine in GRC!?!regards, and thanks,steven#!/usr/bin/env python2
# -*- coding: utf-8 -*-
##
# GNU Radio Python Flow Graph
# Title: Msg Connect Block
# Generated: Wed Jan 11 18:04:49 2017
##

if __name__ == '__main__':
import ctypes
import sys
if sys.platform.startswith('linux'):
try:
x11 = ctypes.cdll.LoadLibrary('libX11.so')
x11.XInitThreads()
except:
print "Warning: failed to XInitThreads()"

from PyQt4 import Qt
from gnuradio import blocks
from gnuradio import eng_notation
from gnuradio import gr
from gnuradio.eng_option import eng_option
from gnuradio.filter import firdes
from optparse import OptionParser
import jitc
import pmt
import sys
from gnuradio import qtgui


class msg_connect_block(gr.top_block, Qt.QWidget):

def __init__(self):
gr.top_block.__init__(self, "Msg Connect Block")
Qt.QWidget.__init__(self)
self.setWindowTitle("Msg Connect Block")
qtgui.util.check_set_qss()
try:
self.setWindowIcon(Qt.QIcon.fromTheme('gnuradio-grc'))
except:
pass
self.top_scroll_layout = Qt.QVBoxLayout()
self.setLayout(self.top_scroll_layout)
self.top_scroll = Qt.QScrollArea()
self.top_scroll.setFrameStyle(Qt.QFrame.NoFrame)
self.top_scroll_layout.addWidget(self.top_scroll)
self.top_scroll.setWidgetResizable(True)
self.top_widget = Qt.QWidget()
self.top_scroll.setWidget(self.top_widget)
self.top_layout = Qt.QVBoxLayout(self.top_widget)
self.top_grid_layout = Qt.QGridLayout()
self.top_layout.addLayout(self.top_grid_layout)

self.settings = Qt.QSettings("GNU Radio", "msg_connect_block")
self.restoreGeometry(self.settings.value("geometry").toByteArray())

##
# Blocks
##
self.jitc_random_sequenced_pdu_0 = jitc.random_sequenced_pdu(4, 1500, 0xFF, 2, 0)
self.blocks_message_strobe_0 = blocks.message_strobe(pmt.intern("TEST"), 1000)
self.blocks_message_debug_0 = blocks.message_debug()

##
# Connections
##
self.msg_connect((self.blocks_message_strobe_0, 'strobe'), (self.jitc_random_sequenced_pdu_0, 'generate'))
self.msg_connect((self.jitc_random_sequenced_pdu_0, 'pdus'), (self.blocks_message_debug_0, 'print'))

def closeEvent(self, event):
self.settings = Qt.QSettings("GNU Radio", "msg_connect_block")
self.settings.setValue("geometry", self.saveGeometry())
event.accept()


def main(top_block_cls=msg_connect_block, options=None):

from distutils.version import StrictVersion
if StrictVersion(Qt.qVersion()) >= StrictVersion("4.5.0"):
style = gr.prefs().get_string('qtgui', 'style', 'raster')

Re: [Discuss-gnuradio] Python Unit Test with message ports - "Could not find port"

[Marcus Müller]

Hi Steven,

that's strange indeed. In various ways.

Could you tell us:

1. where do you register the message port? Could you copy that
exact line?
2. could you copy both message_connect lines from the
GRC-generated and your unit test python?

Thanks,

Marcus

On 01/11/2017 01:35 AM, Steven Knudsen wrote:
> Hi all,
>
> I am trying to write a unit test for a message-only block, let’s call
> it “foo”, that has an input message port “generate". When I use the
> block in GRC, everything is fine. I can connect its message ports to
> standard GNU Radio message blocks, like message_strobe and
> message_debug with no problems.
>
> However, when I try and do the same in a Python unit test, I get the
> message
>
> Could not find port: generate in:
> generate
> system
>
> If, for example, in the same unit test I connect the message_strobe
> with message_debug, all is well.
>
> If I then connect message_strobe to foo, I get the error above.
>
> I double checked that the message port declarations are the same as
> you find in a block like message_strobe. 
>
> I double checked the syntax of msg_connect, making sure it looks
> exactly the same as it does in the GRC generated Python file.
>
> Anyone seen this recently? I have found some references by searching
> online, but nothing that has helped.
>
> Thanks very much!
>
> steven
>
>
> Steven Knudsen, Ph.D., P.Eng.
> www. techconficio.ca 
> www.linkedin.com/in/knudstevenknudsen
> 
>
> Du bist die Aufgabe. Kein Schüler weit und breit. /- Franz Kafka/
>
>
>
> ___
> Discuss-gnuradio mailing list
> Discuss-gnuradio@gnu.org
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio