I am running gnuradio 3.7.0 and been using grc with good results. When I
try to make Multimon (recent trunk) I get the following errors:
trunk # make
/usr/local/bin/grcc -d . multimode.grc
Error: Block key “gr_complex_to_real” not found in Platform -
grc(GNU Radio Companion)
Traceback (most recent call last):
File “/usr/local/bin/grcc”, line 25, in
from grc.python.Platform import Platform
ImportError: No module named grc.python.Platform
Error: Block key “gr_keep_one_in_n” not found in Platform - grc(GNU
Radio Companion)
Traceback (most recent call last):
File “/usr/local/bin/grcc”, line 25, in
from grc.python.Platform import Platform
ImportError: No module named grc.python.Platform
Error: Block key “gr_feedforward_agc_cc” not found in Platform -
grc(GNU Radio Companion)
Traceback (most recent call last):
File “/usr/local/bin/grcc”, line 25, in
from grc.python.Platform import Platform
ImportError: No module named grc.python.Platform
Error: Block key “gr_keep_one_in_n” not found in Platform - grc(GNU
Radio Companion)
Traceback (most recent call last):
File “/usr/local/bin/grcc”, line 25, in
from grc.python.Platform import Platform
ImportError: No module named grc.python.Platform
Error: Block key “gr_keep_one_in_n” not found in Platform - grc(GNU
Radio Companion)
Traceback (most recent call last):
File “/usr/local/bin/grcc”, line 25, in
from grc.python.Platform import Platform
ImportError: No module named grc.python.Platform
Error: Block key “gr_fft_filter_xxx” not found in Platform -
grc(GNU Radio Companion)
Traceback (most recent call last):
File “/usr/local/bin/grcc”, line 25, in
from grc.python.Platform import Platform
ImportError: No module named grc.python.Platform
I have heard good things about how it handles nbfm and wanted to compare
it to what I have hacked together. I have been reviewing examples of
nbfm demodulation and would appreciate any pointers to “ideal” approach
in this area.
Discuss-gnuradio mailing list [email protected] Discuss-gnuradio Info Page
You can pull the .grc into gnuradio-companion, although that might not
work out that well, since the block-names changed across 3.7.
I cannot see where “mh” should be brought into the flow graph. There
may be other errors bu this one appears pretty common on initial look.
This issue can be ignored. I was so focused on editing the file I
ignored the part where I needed to set PYTHONPATH. After I followed the
instructions in make install it worked.
There are a few ways you can go about fixing it. The easiest would be
to have a version of 3.6.5.1 installed on your system. When you open
up your .grc file, look for any block with “(old)” in the name. Those
are blocks that will disappear in 3.7. You can just find the new
version of that block (same name without the “(old)”) and replace it.
When you then open the newly saved grc file in 3.7, those blocks will
still be there.
[snip]
I have gone down this path and see the references to those with “(old)”
in the name. However, I also see some errors that need to be addressed
(search has not yielded anything yet). A typical one manifests itself
in something as simple as definition of samp_rate variable:
Param - Value(value):
Value “int(mh.get_good_rate(devinfo,srate))” cannot be evaluated:
name ‘mh’ is not defined
I cannot see where “mh” should be brought into the flow graph. There may
be other errors bu this one appears pretty common on initial look.
You can pull the .grc into gnuradio-companion, although that might not
work out that well, since the block-names changed across 3.7.
When I do this a large percentage of blocks/connectors do mot render.
Yes, as Marcus said, a lot of names have changed in 3.7 so the same
blocks aren’t recognized from your .grc file.
There are a few ways you can go about fixing it. The easiest would be
to have a version of 3.6.5.1 installed on your system. When you open
up your .grc file, look for any block with “(old)” in the name. Those
are blocks that will disappear in 3.7. You can just find the new
version of that block (same name without the “(old)”) and replace it.
When you then open the newly saved grc file in 3.7, those blocks will
still be there.
You can also just edit the .grc. XML file yourself. Most of the
changes are from “gr.someblock” to “block.someblock” (or
“filter.someblock” or “analog.someblock”), but this way requires
either a lot of intimate knowledge about the new locations of blocks
or looking at each block and locating what the new block name and its
new location are.
In a separate thread I can present what I have so far to get some input.
Also note that I could not get Multimon to work in 3.6.5.1 prior to
making changes in 3.7 (although it didn’t work differently). On the
premise that was issue with my install of that version I did not work
through resolving those issues.
You should work with [email protected] who has also made an attempt
to get it working under 3.7.
His attempt comes up, but “stalls” after a few seconds, and then just
gets continuous “O”. Curiously enough, Andrew’s port of simple_fm_rcv
to 3.7 went swimmingly well. Not sure what’s going on.
Indeed that “import firdes” in the “helper” .py hasn’t been necessary
for a long time, and was just a bit of detritus.
The osmocom sources changed across 3.6->3.7 boundary, so you have to
re-instantiate in 3.7, and hopefully replicate what was in 3.6
–
Marcus L.
Principal Investigator
Shirleys Bay Radio Astronomy Consortium