Re: [Discuss-gnuradio] RTTY receiver
Just FYI, the pulseaudio_pa_sink block is part of: https://github.com/bitglue/gr-pulseaudio Ron W6RZ On 6/12/19 03:59, ba...@dcsmail.net wrote: 3) When I loaded 'examples/rtty_demod.grc', there was a missing block 'pulseaudio_pa_sink'. Where is it, and what does it do? Since it didn't seem directly required for the rest of the example to work, I deleted it and the two blocks feeding it. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] RTTY receiver
Hi Kyeong and all the others who helped me on this issue! Ron Economos identified the basic problem: it depends on how gnu radio was loaded as to whether to use '/usr/local' or '/usr'. So I tried 'cmake -DCMAKE_INSTALL_PREFIX=/usr ../' and it works :) Also, per your suggestion, I rebuilt without the '-DCMAKE_INSTALL_PREFIX=/usr', followed by "sudo ldconfig", and that works as well. So, this issue is closed. I will be submitting a change I made to get 'baudot_encode_bb_impl.cc' to compile, along with suggested additions to the README for installation instructions (for newbees like me). Thanks again, Barry KV4FV P.S. Since I didn't get an email from Ron Economos directly, I can't respond to him right now. The system presents a button to "reply via email to" the person, but I don't have an email client loaded in my rPi yet... I'm using a webmail interface right now. --- Barry Duggan cell: 256-426-0824 On 2019-06-12 23:20, Kyeong Su Shin wrote: Hello Barry: I replicated this on my Pi, and "sudo ldconfig" fixed it. Could you try that, if you haven't already The runtime path of the swig source library is set to "" like in yours, but it does not prevent the script from running (at least on my machine (tm)). (I always run "sudo ldconfig" after installing a GNU Radio module, because many modules simply require that to function properly.) Regards, Kyeong Su Shin 보낸 사람: Barry Duggan 보낸 날짜: 2019년 6월 13일 목요일 오전 9:26:11 받는 사람: Muller, Marcus (CEL); Kyeong Su Shin 참조: Discuss Gnuradio; Cinaed Simson 제목: Re: [Discuss-gnuradio] RTTY receiver Here is my current status. I performed the following commands in the /home/pi/gr-radioteletype/build directory: pi@raspberrypi:~/gr-radioteletype/build $ make clean pi@raspberrypi:~/gr-radioteletype/build $ cmake ../ -- Build type not specified: defaulting to release. -- Boost version: 1.62.0 -- Found the following Boost libraries: -- filesystem -- system Checking for GNU Radio Module: RUNTIME * INCLUDES=/usr/include * LIBS=/usr/lib/arm-linux-gnueabihf/libgnuradio-runtime.so;/usr/lib/arm-linux-gnueabihf/libgnuradio-pmt.so GNURADIO_RUNTIME_FOUND = TRUE -- Extracting version information from git describe... -- Using install prefix: /usr/local -- Building for version: 3a00e28a / 1.0.0git -- -- Checking for module SWIG -- Found SWIG version 3.0.10. -- Configuring done -- Generating done -- Build files have been written to: /home/pi/gr-radioteletype/build pi@raspberrypi:~/gr-radioteletype/build $ make [ 4%] Building CXX object lib/CMakeFiles/gnuradio-radioteletype.dir/async_word_extractor_bb_impl.cc.o [ 8%] Building CXX object lib/CMakeFiles/gnuradio-radioteletype.dir/baudot_decode_bb_impl.cc.o [ 12%] Building CXX object lib/CMakeFiles/gnuradio-radioteletype.dir/baudot_encode_bb_impl.cc.o [ 16%] Building CXX object lib/CMakeFiles/gnuradio-radioteletype.dir/varicode_decode_bb_impl.cc.o [ 20%] Building CXX object lib/CMakeFiles/gnuradio-radioteletype.dir/varicode_encode_bb_impl.cc.o [ 24%] Linking CXX shared library libgnuradio-radioteletype-1.0.0git.so [ 24%] Built target gnuradio-radioteletype [ 28%] Building CXX object lib/CMakeFiles/test-radioteletype.dir/test_radioteletype.cc.o [ 32%] Building CXX object lib/CMakeFiles/test-radioteletype.dir/qa_radioteletype.cc.o [ 36%] Linking CXX executable test-radioteletype [ 36%] Built target test-radioteletype [ 40%] Building CXX object swig/CMakeFiles/_radioteletype_swig_doc_tag.dir/_radioteletype_swig_doc_tag.cpp.o [ 44%] Linking CXX executable _radioteletype_swig_doc_tag [ 44%] Built target _radioteletype_swig_doc_tag [ 48%] Generating doxygen xml for radioteletype_swig_doc docs [ 52%] Generating python docstrings for radioteletype_swig_doc [ 52%] Built target radioteletype_swig_swig_doc [ 56%] Building CXX object swig/CMakeFiles/_radioteletype_swig_swig_tag.dir/_radioteletype_swig_swig_tag.cpp.o [ 60%] Linking CXX executable _radioteletype_swig_swig_tag [ 60%] Built target _radioteletype_swig_swig_tag [ 64%] Generating radioteletype_swig.tag Scanning dependencies of target radioteletype_swig_swig_2d0df [ 68%] Building CXX object swig/CMakeFiles/radioteletype_swig_swig_2d0df.dir/radioteletype_swig_swig_2d0df.cpp.o [ 72%] Linking CXX executable radioteletype_swig_swig_2d0df Swig source [ 72%] Built target radioteletype_swig_swig_2d0df [ 76%] Generating radioteletype_swig.pyc [ 80%] Generating radioteletype_swig.pyo [ 80%] Built target pygen_swig_07109 Scanning dependencies of target _radioteletype_swig [ 84%] Building CXX object swig/CMakeFiles/_radioteletype_swig.dir/radioteletype_swigPYTHON_wrap.cxx.o [ 88%] Linking CXX shared module _radioteletype_swig.so [ 88%] Built target _radioteletype_swig [ 92%] Generating radioteletype/__init__.pyc, radioteletype/filters.pyc, radioteletype/modulators.pyc, radioteletype/demodulators.pyc [ 96%] Generating radioteletype/__init__.pyo, radioteletype/filters.pyo, radioteletype/m
Re: [Discuss-gnuradio] RTTY receiver
On Wed, 2019-06-12 at 16:26 -0400, Barry Duggan wrote: > Hi Marcus, > > I wasn't careful in getting the filenames right, but the intent and the > execution were there :) > > If you look at bitglue/gr-radioteletype/lib/baudot_encode_bb_impl.h, the > tables have a '-1' to indicate characters which do not have a > corresponding Baudot code. In > bitglue/gr-radioteletype/lib/baudot_encode_bb_impl.cc in lines 77 and > 93, there is a test of the '-1'. makes sense! I just assumed that all positive integers were valid codes. If that's not the case: nevermind :) > However, it is not good practice to put integers in a table of > characters. Therefore, I picked another value which is not a valid > Baudot code, but is a seven-bit value, thereby avoiding any sign issues. > > Git can tell you the 'what' and the 'when', but not always the 'why'. > Good comments are worth the effort! Ha! That's why I force people with a draconian strictness, to write *good* commit messages when they want to do something with the GNU Radio main source tree :) Your comment would actually make a good commit message; maybe with a subject line "Compiling on ARM/RPi: circumvent char signedness confusion" or so. This is not a GNU Radio mainline code repository, so I have no jurisdiction there. I personally strongly believe that people should be writing and documenting code so that they themselves in the future, and others, can optimally work with it - and I'd say, for your own projects, it's pretty certain you'll be most happy with comments. So roll with it :) > BTW, when I started from scratch (again), I did a git clone instead of > downloading the zip file. So now I can track my changes better. When we > finish this, I will offer my changes as well as some additions to > README. Thanks! That's the optimum case :) Best regards, Marcus smime.p7s Description: S/MIME cryptographic signature ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] RTTY receiver
Hi Ron, Why do you think this would be the case? On Debian systems, Python can use site-packages from /usr/local as well, I have several GR modules installed in /usr/local and they work just fine. Moreover, you can have two versions of the same thing, one from the distro and one built manually, and LD_LIBRARY_PATH will determine which one to run. Regards, Adrian On June 13, 2019 12:34:01 AM UTC, Ron Economos wrote: >How did you install GNU Radio itself? If you used apt-get, then you >need >to install in /usr, not /usr/local. You can test where GNU Radio is >installed with: > >which gnuradio-companion > >To install in /usr, use this cmake invocation: > >cmake -DCMAKE_INSTALL_PREFIX=/usr ../ > >Ron > >On 6/12/19 17:26, Barry Duggan wrote: >> Here is my current status. >> >> I performed the following commands in the >> /home/pi/gr-radioteletype/build directory: >> >> pi@raspberrypi:~/gr-radioteletype/build $ make clean >> pi@raspberrypi:~/gr-radioteletype/build $ cmake ../ >> -- Build type not specified: defaulting to release. >> -- Boost version: 1.62.0 >> -- Found the following Boost libraries: >> -- filesystem >> -- system >> Checking for GNU Radio Module: RUNTIME >> * INCLUDES=/usr/include >> * >> >LIBS=/usr/lib/arm-linux-gnueabihf/libgnuradio-runtime.so;/usr/lib/arm-linux-gnueabihf/libgnuradio-pmt.so >> GNURADIO_RUNTIME_FOUND = TRUE >> -- Extracting version information from git describe... >> -- Using install prefix: /usr/local >> -- Building for version: 3a00e28a / 1.0.0git > >___ >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
Re: [Discuss-gnuradio] RTTY receiver
Hello Barry: I replicated this on my Pi, and "sudo ldconfig" fixed it. Could you try that, if you haven't already The runtime path of the swig source library is set to "" like in yours, but it does not prevent the script from running (at least on my machine (tm)). (I always run "sudo ldconfig" after installing a GNU Radio module, because many modules simply require that to function properly.) Regards, Kyeong Su Shin 보낸 사람: Barry Duggan 보낸 날짜: 2019년 6월 13일 목요일 오전 9:26:11 받는 사람: Muller, Marcus (CEL); Kyeong Su Shin 참조: Discuss Gnuradio; Cinaed Simson 제목: Re: [Discuss-gnuradio] RTTY receiver Here is my current status. I performed the following commands in the /home/pi/gr-radioteletype/build directory: pi@raspberrypi:~/gr-radioteletype/build $ make clean pi@raspberrypi:~/gr-radioteletype/build $ cmake ../ -- Build type not specified: defaulting to release. -- Boost version: 1.62.0 -- Found the following Boost libraries: -- filesystem -- system Checking for GNU Radio Module: RUNTIME * INCLUDES=/usr/include * LIBS=/usr/lib/arm-linux-gnueabihf/libgnuradio-runtime.so;/usr/lib/arm-linux-gnueabihf/libgnuradio-pmt.so GNURADIO_RUNTIME_FOUND = TRUE -- Extracting version information from git describe... -- Using install prefix: /usr/local -- Building for version: 3a00e28a / 1.0.0git -- -- Checking for module SWIG -- Found SWIG version 3.0.10. -- Configuring done -- Generating done -- Build files have been written to: /home/pi/gr-radioteletype/build pi@raspberrypi:~/gr-radioteletype/build $ make [ 4%] Building CXX object lib/CMakeFiles/gnuradio-radioteletype.dir/async_word_extractor_bb_impl.cc.o [ 8%] Building CXX object lib/CMakeFiles/gnuradio-radioteletype.dir/baudot_decode_bb_impl.cc.o [ 12%] Building CXX object lib/CMakeFiles/gnuradio-radioteletype.dir/baudot_encode_bb_impl.cc.o [ 16%] Building CXX object lib/CMakeFiles/gnuradio-radioteletype.dir/varicode_decode_bb_impl.cc.o [ 20%] Building CXX object lib/CMakeFiles/gnuradio-radioteletype.dir/varicode_encode_bb_impl.cc.o [ 24%] Linking CXX shared library libgnuradio-radioteletype-1.0.0git.so [ 24%] Built target gnuradio-radioteletype [ 28%] Building CXX object lib/CMakeFiles/test-radioteletype.dir/test_radioteletype.cc.o [ 32%] Building CXX object lib/CMakeFiles/test-radioteletype.dir/qa_radioteletype.cc.o [ 36%] Linking CXX executable test-radioteletype [ 36%] Built target test-radioteletype [ 40%] Building CXX object swig/CMakeFiles/_radioteletype_swig_doc_tag.dir/_radioteletype_swig_doc_tag.cpp.o [ 44%] Linking CXX executable _radioteletype_swig_doc_tag [ 44%] Built target _radioteletype_swig_doc_tag [ 48%] Generating doxygen xml for radioteletype_swig_doc docs [ 52%] Generating python docstrings for radioteletype_swig_doc [ 52%] Built target radioteletype_swig_swig_doc [ 56%] Building CXX object swig/CMakeFiles/_radioteletype_swig_swig_tag.dir/_radioteletype_swig_swig_tag.cpp.o [ 60%] Linking CXX executable _radioteletype_swig_swig_tag [ 60%] Built target _radioteletype_swig_swig_tag [ 64%] Generating radioteletype_swig.tag Scanning dependencies of target radioteletype_swig_swig_2d0df [ 68%] Building CXX object swig/CMakeFiles/radioteletype_swig_swig_2d0df.dir/radioteletype_swig_swig_2d0df.cpp.o [ 72%] Linking CXX executable radioteletype_swig_swig_2d0df Swig source [ 72%] Built target radioteletype_swig_swig_2d0df [ 76%] Generating radioteletype_swig.pyc [ 80%] Generating radioteletype_swig.pyo [ 80%] Built target pygen_swig_07109 Scanning dependencies of target _radioteletype_swig [ 84%] Building CXX object swig/CMakeFiles/_radioteletype_swig.dir/radioteletype_swigPYTHON_wrap.cxx.o [ 88%] Linking CXX shared module _radioteletype_swig.so [ 88%] Built target _radioteletype_swig [ 92%] Generating radioteletype/__init__.pyc, radioteletype/filters.pyc, radioteletype/modulators.pyc, radioteletype/demodulators.pyc [ 96%] Generating radioteletype/__init__.pyo, radioteletype/filters.pyo, radioteletype/modulators.pyo, radioteletype/demodulators.pyo [ 96%] Built target pygen_python_17c4d [ 96%] Built target pygen_apps_9a6dd [100%] Generating documentation with doxygen [100%] Built target doxygen_target pi@raspberrypi:~/gr-radioteletype/build $ sudo make install [ 24%] Built target gnuradio-radioteletype [ 36%] Built target test-radioteletype [ 44%] Built target _radioteletype_swig_doc_tag [ 52%] Built target radioteletype_swig_swig_doc [ 60%] Built target _radioteletype_swig_swig_tag [ 72%] Built target radioteletype_swig_swig_2d0df [ 80%] Built target pygen_swig_07109 [ 88%] Built target _radioteletype_swig [ 96%] Built target pygen_python_17c4d [ 96%] Built target pygen_apps_9a6dd [100%] Built target doxygen_target Install the project... -- Install configuration: "Release" -- Up-to-date: /usr/local/lib/cmake/radioteletype/radioteletypeConfig.cmake -- Up-to-date: /usr/local/include/radioteletype/api.h -- Up-to-date: /usr/local/include/radioteletype/varicode_decod
Re: [Discuss-gnuradio] RTTY receiver
How did you install GNU Radio itself? If you used apt-get, then you need to install in /usr, not /usr/local. You can test where GNU Radio is installed with: which gnuradio-companion To install in /usr, use this cmake invocation: cmake -DCMAKE_INSTALL_PREFIX=/usr ../ Ron On 6/12/19 17:26, Barry Duggan wrote: Here is my current status. I performed the following commands in the /home/pi/gr-radioteletype/build directory: pi@raspberrypi:~/gr-radioteletype/build $ make clean pi@raspberrypi:~/gr-radioteletype/build $ cmake ../ -- Build type not specified: defaulting to release. -- Boost version: 1.62.0 -- Found the following Boost libraries: -- filesystem -- system Checking for GNU Radio Module: RUNTIME * INCLUDES=/usr/include * LIBS=/usr/lib/arm-linux-gnueabihf/libgnuradio-runtime.so;/usr/lib/arm-linux-gnueabihf/libgnuradio-pmt.so GNURADIO_RUNTIME_FOUND = TRUE -- Extracting version information from git describe... -- Using install prefix: /usr/local -- Building for version: 3a00e28a / 1.0.0git ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] RTTY receiver
Here is my current status. I performed the following commands in the /home/pi/gr-radioteletype/build directory: pi@raspberrypi:~/gr-radioteletype/build $ make clean pi@raspberrypi:~/gr-radioteletype/build $ cmake ../ -- Build type not specified: defaulting to release. -- Boost version: 1.62.0 -- Found the following Boost libraries: -- filesystem -- system Checking for GNU Radio Module: RUNTIME * INCLUDES=/usr/include * LIBS=/usr/lib/arm-linux-gnueabihf/libgnuradio-runtime.so;/usr/lib/arm-linux-gnueabihf/libgnuradio-pmt.so GNURADIO_RUNTIME_FOUND = TRUE -- Extracting version information from git describe... -- Using install prefix: /usr/local -- Building for version: 3a00e28a / 1.0.0git -- -- Checking for module SWIG -- Found SWIG version 3.0.10. -- Configuring done -- Generating done -- Build files have been written to: /home/pi/gr-radioteletype/build pi@raspberrypi:~/gr-radioteletype/build $ make [ 4%] Building CXX object lib/CMakeFiles/gnuradio-radioteletype.dir/async_word_extractor_bb_impl.cc.o [ 8%] Building CXX object lib/CMakeFiles/gnuradio-radioteletype.dir/baudot_decode_bb_impl.cc.o [ 12%] Building CXX object lib/CMakeFiles/gnuradio-radioteletype.dir/baudot_encode_bb_impl.cc.o [ 16%] Building CXX object lib/CMakeFiles/gnuradio-radioteletype.dir/varicode_decode_bb_impl.cc.o [ 20%] Building CXX object lib/CMakeFiles/gnuradio-radioteletype.dir/varicode_encode_bb_impl.cc.o [ 24%] Linking CXX shared library libgnuradio-radioteletype-1.0.0git.so [ 24%] Built target gnuradio-radioteletype [ 28%] Building CXX object lib/CMakeFiles/test-radioteletype.dir/test_radioteletype.cc.o [ 32%] Building CXX object lib/CMakeFiles/test-radioteletype.dir/qa_radioteletype.cc.o [ 36%] Linking CXX executable test-radioteletype [ 36%] Built target test-radioteletype [ 40%] Building CXX object swig/CMakeFiles/_radioteletype_swig_doc_tag.dir/_radioteletype_swig_doc_tag.cpp.o [ 44%] Linking CXX executable _radioteletype_swig_doc_tag [ 44%] Built target _radioteletype_swig_doc_tag [ 48%] Generating doxygen xml for radioteletype_swig_doc docs [ 52%] Generating python docstrings for radioteletype_swig_doc [ 52%] Built target radioteletype_swig_swig_doc [ 56%] Building CXX object swig/CMakeFiles/_radioteletype_swig_swig_tag.dir/_radioteletype_swig_swig_tag.cpp.o [ 60%] Linking CXX executable _radioteletype_swig_swig_tag [ 60%] Built target _radioteletype_swig_swig_tag [ 64%] Generating radioteletype_swig.tag Scanning dependencies of target radioteletype_swig_swig_2d0df [ 68%] Building CXX object swig/CMakeFiles/radioteletype_swig_swig_2d0df.dir/radioteletype_swig_swig_2d0df.cpp.o [ 72%] Linking CXX executable radioteletype_swig_swig_2d0df Swig source [ 72%] Built target radioteletype_swig_swig_2d0df [ 76%] Generating radioteletype_swig.pyc [ 80%] Generating radioteletype_swig.pyo [ 80%] Built target pygen_swig_07109 Scanning dependencies of target _radioteletype_swig [ 84%] Building CXX object swig/CMakeFiles/_radioteletype_swig.dir/radioteletype_swigPYTHON_wrap.cxx.o [ 88%] Linking CXX shared module _radioteletype_swig.so [ 88%] Built target _radioteletype_swig [ 92%] Generating radioteletype/__init__.pyc, radioteletype/filters.pyc, radioteletype/modulators.pyc, radioteletype/demodulators.pyc [ 96%] Generating radioteletype/__init__.pyo, radioteletype/filters.pyo, radioteletype/modulators.pyo, radioteletype/demodulators.pyo [ 96%] Built target pygen_python_17c4d [ 96%] Built target pygen_apps_9a6dd [100%] Generating documentation with doxygen [100%] Built target doxygen_target pi@raspberrypi:~/gr-radioteletype/build $ sudo make install [ 24%] Built target gnuradio-radioteletype [ 36%] Built target test-radioteletype [ 44%] Built target _radioteletype_swig_doc_tag [ 52%] Built target radioteletype_swig_swig_doc [ 60%] Built target _radioteletype_swig_swig_tag [ 72%] Built target radioteletype_swig_swig_2d0df [ 80%] Built target pygen_swig_07109 [ 88%] Built target _radioteletype_swig [ 96%] Built target pygen_python_17c4d [ 96%] Built target pygen_apps_9a6dd [100%] Built target doxygen_target Install the project... -- Install configuration: "Release" -- Up-to-date: /usr/local/lib/cmake/radioteletype/radioteletypeConfig.cmake -- Up-to-date: /usr/local/include/radioteletype/api.h -- Up-to-date: /usr/local/include/radioteletype/varicode_decode_bb.h -- Up-to-date: /usr/local/include/radioteletype/async_word_extractor_bb.h -- Up-to-date: /usr/local/include/radioteletype/baudot_decode_bb.h -- Up-to-date: /usr/local/include/radioteletype/varicode_encode_bb.h -- Up-to-date: /usr/local/include/radioteletype/baudot_encode_bb.h -- Installing: /usr/local/lib/libgnuradio-radioteletype-1.0.0git.so.0.0.0 -- Up-to-date: /usr/local/lib/libgnuradio-radioteletype-1.0.0git.so -- Up-to-date: /usr/local/lib/libgnuradio-radioteletype.so -- Up-to-date: /usr/local/lib/libgnuradio-radioteletype-1.0.0git.so.0 -- Installing: /usr/local/lib/python2.7/dist-packages/radioteletype/_radioteletype_swig.so -- Set runtime
Re: [Discuss-gnuradio] RTTY receiver
Hi Marcus,
I wasn't careful in getting the filenames right, but the intent and the
execution were there :)
If you look at bitglue/gr-radioteletype/lib/baudot_encode_bb_impl.h, the
tables have a '-1' to indicate characters which do not have a
corresponding Baudot code. In
bitglue/gr-radioteletype/lib/baudot_encode_bb_impl.cc in lines 77 and
93, there is a test of the '-1'.
However, it is not good practice to put integers in a table of
characters. Therefore, I picked another value which is not a valid
Baudot code, but is a seven-bit value, thereby avoiding any sign issues.
Git can tell you the 'what' and the 'when', but not always the 'why'.
Good comments are worth the effort!
BTW, when I started from scratch (again), I did a git clone instead of
downloading the zip file. So now I can track my changes better. When we
finish this, I will offer my changes as well as some additions to
README.
Best wishes.
---
Barry Duggan
cell: 256-426-0824
On 2019-06-12 12:40, Müller wrote:
Hi Barry,
On Wed, 2019-06-12 at 06:59 -0400, ba...@dcsmail.net wrote:
Hi Kyeong,
1) In lib/radioteletype/baudot_encode_bb.h I tried replacing "static
const char" with "static const signed char", but it caused
complications
in radioteletype/baudot_encode_bb.cc, so I took an alternate approach:
Wait, these filenames don't align with the ones I'm looking at – could
you verify we're both looking at the code from github.com/bitglue/gr-
radioteletype ?
Since this really just "spells out" the original code's intent, there
shouldn't be *any* problems at all with that. Maybe we should have a
look at these problems that arose?
/*
* modified by Barry Duggan KV4FV
* 11 June 2019
* with RaspberryPi compiler, an error is produced comparing char and
signed char values.
* to circumvent this problem, I have changed all "-1" entries to
"0x7f"
Hm, -1 would be 0xFF in my math, wouldn't it? 0x7F is plain 127!
in the table
* and in the code
*/
By the way, spot the experienced old-school programmer: That's a
classical beautiful changelog comment from the pre-git era. Kudos :)
Always a pleasure to see.
So now the 'make' works without errors.
I presume that also includes the negative number comparisons in
lib/baudot_encode_bb_impl.cc 's general_work() function?
2) In 'sudo make install' I got the following:
-- Installing:
/usr/local/lib/python2.7/dist-packages/radioteletype/_radioteletype_swig.so
-- Set runtime path of
"/usr/local/lib/python2.7/dist-packages/radioteletype/_radioteletype_swig.so"
to ""
which leads to a run-time error...
Traceback (most recent call last):
File "/home/pi/gr-radioteletype/examples/rtty_demod.py", line 30,
in
from radioteletype.demodulators import rtty_demod_cb
File
"/usr/local/lib/python2.7/dist-packages/radioteletype/demodulators.py",
line 9, in
from radioteletype_swig import (
File
"/usr/local/lib/python2.7/dist-packages/radioteletype/radioteletype_swig.py",
line 21, in
_radioteletype_swig = swig_import_helper()
File
"/usr/local/lib/python2.7/dist-packages/radioteletype/radioteletype_swig.py",
line 20, in swig_import_helper
return importlib.import_module('_radioteletype_swig')
File "/usr/lib/python2.7/importlib/__init__.py", line 37, in
import_module
__import__(name)
ImportError: No module named _radioteletype_swig
So, where should '_radioteletype_swig.so' go, and how do I specify it?
That file should have gotten installed just OK if it was successfully
built. Are we sure that the build itself is successful? Sometimes, SWIG
(which generates our C++/Python glue half-automatedly) gets stuck, so
you really have to "make clean; make; make install". It's a bummer, but
I've seen it get nearly extinct over the years.
3) When I loaded 'examples/rtty_demod.grc', there was a missing block
'pulseaudio_pa_sink'.
That seems to be a block from a different out-of-tree module.
However, you really don't need a pulseaudio block to speak to that most
common Linux user audio subsystem. Just replace that block with the
"audio sink" that GNU Radio brings itself.
Where is it, and what does it do?
Its purpose is probably to send audio to your Sound card, in the end.
Since it didn't
seem directly required for the rest of the example to work, I deleted
it
and the two blocks feeding it.
4) I really appreciate all that you and the others are doing to help
with this.
We really appreciate you asking here, so keep up the good work!
Cheers,
Marcus
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] RTTY receiver
Hi Barry,
On Wed, 2019-06-12 at 06:59 -0400, ba...@dcsmail.net wrote:
> Hi Kyeong,
>
> 1) In lib/radioteletype/baudot_encode_bb.h I tried replacing "static
> const char" with "static const signed char", but it caused complications
> in radioteletype/baudot_encode_bb.cc, so I took an alternate approach:
Wait, these filenames don't align with the ones I'm looking at – could
you verify we're both looking at the code from github.com/bitglue/gr-
radioteletype ?
Since this really just "spells out" the original code's intent, there
shouldn't be *any* problems at all with that. Maybe we should have a
look at these problems that arose?
> /*
> * modified by Barry Duggan KV4FV
> * 11 June 2019
> * with RaspberryPi compiler, an error is produced comparing char and
> signed char values.
> * to circumvent this problem, I have changed all "-1" entries to "0x7f"
Hm, -1 would be 0xFF in my math, wouldn't it? 0x7F is plain 127!
> in the table
> * and in the code
> */
By the way, spot the experienced old-school programmer: That's a
classical beautiful changelog comment from the pre-git era. Kudos :)
Always a pleasure to see.
> So now the 'make' works without errors.
I presume that also includes the negative number comparisons in
lib/baudot_encode_bb_impl.cc 's general_work() function?
>
> 2) In 'sudo make install' I got the following:
> -- Installing:
> /usr/local/lib/python2.7/dist-packages/radioteletype/_radioteletype_swig.so
> -- Set runtime path of
> "/usr/local/lib/python2.7/dist-packages/radioteletype/_radioteletype_swig.so"
> to ""
> which leads to a run-time error...
> Traceback (most recent call last):
>File "/home/pi/gr-radioteletype/examples/rtty_demod.py", line 30, in
>
> from radioteletype.demodulators import rtty_demod_cb
>File
> "/usr/local/lib/python2.7/dist-packages/radioteletype/demodulators.py",
> line 9, in
> from radioteletype_swig import (
>File
> "/usr/local/lib/python2.7/dist-packages/radioteletype/radioteletype_swig.py",
> line 21, in
> _radioteletype_swig = swig_import_helper()
>File
> "/usr/local/lib/python2.7/dist-packages/radioteletype/radioteletype_swig.py",
> line 20, in swig_import_helper
> return importlib.import_module('_radioteletype_swig')
>File "/usr/lib/python2.7/importlib/__init__.py", line 37, in
> import_module
> __import__(name)
> ImportError: No module named _radioteletype_swig
>
> So, where should '_radioteletype_swig.so' go, and how do I specify it?
That file should have gotten installed just OK if it was successfully
built. Are we sure that the build itself is successful? Sometimes, SWIG
(which generates our C++/Python glue half-automatedly) gets stuck, so
you really have to "make clean; make; make install". It's a bummer, but
I've seen it get nearly extinct over the years.
>
> 3) When I loaded 'examples/rtty_demod.grc', there was a missing block
> 'pulseaudio_pa_sink'.
That seems to be a block from a different out-of-tree module.
However, you really don't need a pulseaudio block to speak to that most
common Linux user audio subsystem. Just replace that block with the
"audio sink" that GNU Radio brings itself.
> Where is it, and what does it do?
Its purpose is probably to send audio to your Sound card, in the end.
> Since it didn't
> seem directly required for the rest of the example to work, I deleted it
> and the two blocks feeding it.
>
> 4) I really appreciate all that you and the others are doing to help
> with this.
We really appreciate you asking here, so keep up the good work!
Cheers,
Marcus
smime.p7s
Description: S/MIME cryptographic signature
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] RTTY receiver
Hi Kyeong,
1) In lib/radioteletype/baudot_encode_bb.h I tried replacing "static
const char" with "static const signed char", but it caused complications
in radioteletype/baudot_encode_bb.cc, so I took an alternate approach:
/*
* modified by Barry Duggan KV4FV
* 11 June 2019
* with RaspberryPi compiler, an error is produced comparing char and
signed char values.
* to circumvent this problem, I have changed all "-1" entries to "0x7f"
in the table
* and in the code
*/
So now the 'make' works without errors.
2) In 'sudo make install' I got the following:
-- Installing:
/usr/local/lib/python2.7/dist-packages/radioteletype/_radioteletype_swig.so
-- Set runtime path of
"/usr/local/lib/python2.7/dist-packages/radioteletype/_radioteletype_swig.so"
to ""
which leads to a run-time error...
Traceback (most recent call last):
File "/home/pi/gr-radioteletype/examples/rtty_demod.py", line 30, in
from radioteletype.demodulators import rtty_demod_cb
File
"/usr/local/lib/python2.7/dist-packages/radioteletype/demodulators.py",
line 9, in
from radioteletype_swig import (
File
"/usr/local/lib/python2.7/dist-packages/radioteletype/radioteletype_swig.py",
line 21, in
_radioteletype_swig = swig_import_helper()
File
"/usr/local/lib/python2.7/dist-packages/radioteletype/radioteletype_swig.py",
line 20, in swig_import_helper
return importlib.import_module('_radioteletype_swig')
File "/usr/lib/python2.7/importlib/__init__.py", line 37, in
import_module
__import__(name)
ImportError: No module named _radioteletype_swig
So, where should '_radioteletype_swig.so' go, and how do I specify it?
3) When I loaded 'examples/rtty_demod.grc', there was a missing block
'pulseaudio_pa_sink'. Where is it, and what does it do? Since it didn't
seem directly required for the rest of the example to work, I deleted it
and the two blocks feeding it.
4) I really appreciate all that you and the others are doing to help
with this.
Many thanks, Barry
On 2019-06-11 00:05, Kyeong Su Shin wrote:
Hello Barry,
Apparantly, the module has portability issues (will build on x86 but
won't build on ARM) due to data type issues. To build the package, you
will have to edit lib/baudot_encode_bb_impl.h:
"static const char ascii_to_letters[128]" should become
"static const signed char ascii_to_letters[128]", and
"static const char ascii_to_figures[128]" should become
"static const signed char ascii_to_figures[128]".
That will allow the module to build, although you may have to make
further changes to get "Boudot Encode" block working correctly (I
didn't test that; maybe I should make a pull request after that).
Regards,
Kyeong Su Shin
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] RTTY receiver
Cinaed Simson wrote: It builds find on my ARM 64 Odroid running jessie. Maybe it just doesn't build on the raspberry pi 3. I'm running a slightly dated version of gnuradio - 3.7.12git-295-ga0adcd33. Just out of curiosity, I built using MSVC-2017. The only issue I found was the need to add a '#include ' in some place due to things like: if (bits_eaten >= bits_per_word and sample) Otherwise it links fine; not tested. -- --gv ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] RTTY receiver
Yeah, char signedness is compiler-dependent (and can be configured with
-f[un]signed-char in GCC). Neither C nor C++ specify a "default"
signedness in the standard.
So, if you want to do arithmetic on chars, you need to specify which
data type you'd want – signed char or unsigned char.
That's what Kyeong's change does.
If it works without, it's by luck.
If you look into embedded software, you'll often find that C developers
prefer to use `int8_t` instead of `signed char` and `uint8_t` instead
of `unsigned char` if they're using these datatypes to (logically)
transport bytes of data or actually numbers, as opposed to dealing with
character data ("text" in the human sense, not the ld sense).
Here it's kind of a hybrid, so explicity saying you want unsigned char
is probably the most intuitive :)
Thanks for this discussion!
Best regards,
Marcus
On Mon, 2019-06-10 at 23:27 -0700, Cinaed Simson wrote:
> On 6/10/19 9:05 PM, Kyeong Su Shin wrote:
> > Hello Barry,
> >
> >
> > Apparantly, the module has portability issues (will build on x86
> > but
> > won't build on ARM) due to data type issues.
>
> It builds find on my ARM 64 Odroid running jessie. Maybe it just
> doesn't
> build on the raspberry pi 3. I'm running a slightly dated version of
> gnuradio - 3.7.12git-295-ga0adcd33.
>
> -- Cinaed
>
> To build the package, you
> > will have to edit lib/baudot_encode_bb_impl.h:
> >
> >
> > "static const char ascii_to_letters[128]" should become
> >
> >
> > "static const *signed* char ascii_to_letters[128]", and
> >
> >
> > "static const char ascii_to_figures[128]" should become
> >
> >
> > "static const *signed* char ascii_to_figures[128]".
> >
> >
> > That will allow the module to build, although you may have to make
> > further changes to get "Boudot Encode" block working correctly (I
> > didn't
> > test that; maybe I should make a pull request after that).
> >
> >
> > Regards,
> >
> > Kyeong Su Shin
> >
> >
> > -
> > ---
> > *보낸 사람:* ba...@dcsmail.net
> > *보낸 날짜:* 2019년 6월 11일 화요일 오전 2:56:02
> > *받는 사람:* Kyeong Su Shin
> > *참조:* discuss-gnuradio@gnu.org
> > *제목:* Re: [Discuss-gnuradio] RTTY receiver
> >
> > Thank you for your response. Since this is my first issue on
> > 'discuss-gnuradio', I am not sure how to get my reply to you posted
> > in
> > the thread. This looks like it might work. If not, please let me
> > know
> > what to do.
> >
> > I did the "sudo ldconfig" and it got rid of the "include could not
> > find
> > load file: GrPython", but not the other problem, so I decided to
> > start
> > from scratch.
> >
> > I have
> > Raspberry Pi 3 B+
> > Rasbian Linux (v2)
> >
> > I deleted the folder 'gr-radioteletype'
> > download zip from https://github.com/bitglue/gr-radioteletype
> > <https://github.com/bitglue/gr-radioteletype>
> >
> > GitHub - bitglue/gr-radioteletype: GNU Radio blocks for RTTY and
> > PSK31
> > <https://github.com/bitglue/gr-radioteletype>
> > github.com
> > GNU Radio blocks for RTTY and PSK31. Contribute to
> > bitglue/gr-radioteletype development by creating an account on
> > GitHub.
> >
> >
> > extract zip to /home/pi
> > cd ~/gr-radioteletype-master
> > mkdir build
> > cd build
> > cmake ../
> > make
> > [ 5%] Building CXX object
> > lib/CMakeFiles/gnuradio-
> > radioteletype.dir/async_word_extractor_bb_impl.cc.o
> > [ 10%] Building CXX object
> > lib/CMakeFiles/gnuradio-
> > radioteletype.dir/baudot_decode_bb_impl.cc.o
> > [ 15%] Building CXX object
> > lib/CMakeFiles/gnuradio-
> > radioteletype.dir/baudot_encode_bb_impl.cc.o
> > In file included from
> > /home/pi/gr-radioteletype-master/lib/baudot_encode_bb_impl.cc:26:0:
> > /home/pi/gr-radioteletype-master/lib/baudot_encode_bb_impl.h:65:5:
> > error: narrowing conversion of ‘-1’ from ‘int’ to ‘char’ inside { }
> > [-Wnarrowing]
> > };
> > ^
> > /home/pi/gr-radioteletype-master/lib/baudot_encode_bb_impl.h:100:5:
> > error: narrowing conversion of ‘-1’ from ‘int’ to ‘char’ inside { }
> > [-Wnarrowing]
> > };
> > ^
> > /home/pi/gr-radioteletype-master/lib/baudot_encode_bb_impl.h:100:5:
> > error: narrowing conversion of ‘-1’ from ‘int’ to ‘char’ inside { }
> > [-Wnarrowing]
> >
Re: [Discuss-gnuradio] RTTY receiver
On 6/10/19 9:05 PM, Kyeong Su Shin wrote:
> Hello Barry,
>
>
> Apparantly, the module has portability issues (will build on x86 but
> won't build on ARM) due to data type issues.
It builds find on my ARM 64 Odroid running jessie. Maybe it just doesn't
build on the raspberry pi 3. I'm running a slightly dated version of
gnuradio - 3.7.12git-295-ga0adcd33.
-- Cinaed
To build the package, you
> will have to edit lib/baudot_encode_bb_impl.h:
>
>
> "static const char ascii_to_letters[128]" should become
>
>
> "static const *signed* char ascii_to_letters[128]", and
>
>
> "static const char ascii_to_figures[128]" should become
>
>
> "static const *signed* char ascii_to_figures[128]".
>
>
> That will allow the module to build, although you may have to make
> further changes to get "Boudot Encode" block working correctly (I didn't
> test that; maybe I should make a pull request after that).
>
>
> Regards,
>
> Kyeong Su Shin
>
>
> ----
> *보낸 사람:* ba...@dcsmail.net
> *보낸 날짜:* 2019년 6월 11일 화요일 오전 2:56:02
> *받는 사람:* Kyeong Su Shin
> *참조:* discuss-gnuradio@gnu.org
> *제목:* Re: [Discuss-gnuradio] RTTY receiver
>
> Thank you for your response. Since this is my first issue on
> 'discuss-gnuradio', I am not sure how to get my reply to you posted in
> the thread. This looks like it might work. If not, please let me know
> what to do.
>
> I did the "sudo ldconfig" and it got rid of the "include could not find
> load file: GrPython", but not the other problem, so I decided to start
> from scratch.
>
> I have
> Raspberry Pi 3 B+
> Rasbian Linux (v2)
>
> I deleted the folder 'gr-radioteletype'
> download zip from https://github.com/bitglue/gr-radioteletype
> <https://github.com/bitglue/gr-radioteletype>
>
> GitHub - bitglue/gr-radioteletype: GNU Radio blocks for RTTY and PSK31
> <https://github.com/bitglue/gr-radioteletype>
> github.com
> GNU Radio blocks for RTTY and PSK31. Contribute to
> bitglue/gr-radioteletype development by creating an account on GitHub.
>
>
> extract zip to /home/pi
> cd ~/gr-radioteletype-master
> mkdir build
> cd build
> cmake ../
> make
> [ 5%] Building CXX object
> lib/CMakeFiles/gnuradio-radioteletype.dir/async_word_extractor_bb_impl.cc.o
> [ 10%] Building CXX object
> lib/CMakeFiles/gnuradio-radioteletype.dir/baudot_decode_bb_impl.cc.o
> [ 15%] Building CXX object
> lib/CMakeFiles/gnuradio-radioteletype.dir/baudot_encode_bb_impl.cc.o
> In file included from
> /home/pi/gr-radioteletype-master/lib/baudot_encode_bb_impl.cc:26:0:
> /home/pi/gr-radioteletype-master/lib/baudot_encode_bb_impl.h:65:5:
> error: narrowing conversion of ‘-1’ from ‘int’ to ‘char’ inside { }
> [-Wnarrowing]
> };
> ^
> /home/pi/gr-radioteletype-master/lib/baudot_encode_bb_impl.h:100:5:
> error: narrowing conversion of ‘-1’ from ‘int’ to ‘char’ inside { }
> [-Wnarrowing]
> };
> ^
> /home/pi/gr-radioteletype-master/lib/baudot_encode_bb_impl.h:100:5:
> error: narrowing conversion of ‘-1’ from ‘int’ to ‘char’ inside { }
> [-Wnarrowing]
> lib/CMakeFiles/gnuradio-radioteletype.dir/build.make:110: recipe for
> target
> 'lib/CMakeFiles/gnuradio-radioteletype.dir/baudot_encode_bb_impl.cc.o'
> failed
> make[2]: ***
> [lib/CMakeFiles/gnuradio-radioteletype.dir/baudot_encode_bb_impl.cc.o]
> Error 1
> CMakeFiles/Makefile2:137: recipe for target
> 'lib/CMakeFiles/gnuradio-radioteletype.dir/all' failed
> make[1]: *** [lib/CMakeFiles/gnuradio-radioteletype.dir/all] Error 2
> Makefile:138: recipe for target 'all' failed
> make: *** [all] Error 2
>
> Both of the error messages were repeated *many* times. I looked at the
> code for baudot_encode_bb_impl.h, but could not see any problems with
> it.
>
> I appreciate any help you can give.
>
> Best wishes,
>
> Barry
>
> On 2019-06-10 00:29, Kyeong Su Shin wrote:
>> Hello Barry:
>>
>> Did you try "sudo ldconfig"?
>>
>> If so, could you provide us the relevant software versions (GNU Radio
>> version, Linux distro type, etc) and the full steps that you took to
>> build the module? gr-radioteletype from "
>> https://github.com/bitglue/gr-radioteletype/ " builds and runs fine on
>> my machine (tm).
>>
>>
>> Regards,
>>
>> Kyeong Su Shin
>>
>>
>>
>> 보낸 사람: ba...@dcsmail.net 대신 Discuss-gnuradio
>>
>> 보낸 날짜: 2019년 6월 10일 월요일 오전 5:08:32
>> 받는 사람: discuss-gnuradio@gnu.org
>
Re: [Discuss-gnuradio] RTTY receiver
Hello Barry,
Apparantly, the module has portability issues (will build on x86 but won't
build on ARM) due to data type issues. To build the package, you will have to
edit lib/baudot_encode_bb_impl.h:
"static const char ascii_to_letters[128]" should become
"static const signed char ascii_to_letters[128]", and
"static const char ascii_to_figures[128]" should become
"static const signed char ascii_to_figures[128]".
That will allow the module to build, although you may have to make further
changes to get "Boudot Encode" block working correctly (I didn't test that;
maybe I should make a pull request after that).
Regards,
Kyeong Su Shin
보낸 사람: ba...@dcsmail.net
보낸 날짜: 2019년 6월 11일 화요일 오전 2:56:02
받는 사람: Kyeong Su Shin
참조: discuss-gnuradio@gnu.org
제목: Re: [Discuss-gnuradio] RTTY receiver
Thank you for your response. Since this is my first issue on
'discuss-gnuradio', I am not sure how to get my reply to you posted in
the thread. This looks like it might work. If not, please let me know
what to do.
I did the "sudo ldconfig" and it got rid of the "include could not find
load file: GrPython", but not the other problem, so I decided to start
from scratch.
I have
Raspberry Pi 3 B+
Rasbian Linux (v2)
I deleted the folder 'gr-radioteletype'
download zip from https://github.com/bitglue/gr-radioteletype
[https://avatars1.githubusercontent.com/u/1232472?s=400=4]<https://github.com/bitglue/gr-radioteletype>
GitHub - bitglue/gr-radioteletype: GNU Radio blocks for RTTY and
PSK31<https://github.com/bitglue/gr-radioteletype>
github.com
GNU Radio blocks for RTTY and PSK31. Contribute to bitglue/gr-radioteletype
development by creating an account on GitHub.
extract zip to /home/pi
cd ~/gr-radioteletype-master
mkdir build
cd build
cmake ../
make
[ 5%] Building CXX object
lib/CMakeFiles/gnuradio-radioteletype.dir/async_word_extractor_bb_impl.cc.o
[ 10%] Building CXX object
lib/CMakeFiles/gnuradio-radioteletype.dir/baudot_decode_bb_impl.cc.o
[ 15%] Building CXX object
lib/CMakeFiles/gnuradio-radioteletype.dir/baudot_encode_bb_impl.cc.o
In file included from
/home/pi/gr-radioteletype-master/lib/baudot_encode_bb_impl.cc:26:0:
/home/pi/gr-radioteletype-master/lib/baudot_encode_bb_impl.h:65:5:
error: narrowing conversion of ‘-1’ from ‘int’ to ‘char’ inside { }
[-Wnarrowing]
};
^
/home/pi/gr-radioteletype-master/lib/baudot_encode_bb_impl.h:100:5:
error: narrowing conversion of ‘-1’ from ‘int’ to ‘char’ inside { }
[-Wnarrowing]
};
^
/home/pi/gr-radioteletype-master/lib/baudot_encode_bb_impl.h:100:5:
error: narrowing conversion of ‘-1’ from ‘int’ to ‘char’ inside { }
[-Wnarrowing]
lib/CMakeFiles/gnuradio-radioteletype.dir/build.make:110: recipe for
target
'lib/CMakeFiles/gnuradio-radioteletype.dir/baudot_encode_bb_impl.cc.o'
failed
make[2]: ***
[lib/CMakeFiles/gnuradio-radioteletype.dir/baudot_encode_bb_impl.cc.o]
Error 1
CMakeFiles/Makefile2:137: recipe for target
'lib/CMakeFiles/gnuradio-radioteletype.dir/all' failed
make[1]: *** [lib/CMakeFiles/gnuradio-radioteletype.dir/all] Error 2
Makefile:138: recipe for target 'all' failed
make: *** [all] Error 2
Both of the error messages were repeated *many* times. I looked at the
code for baudot_encode_bb_impl.h, but could not see any problems with
it.
I appreciate any help you can give.
Best wishes,
Barry
On 2019-06-10 00:29, Kyeong Su Shin wrote:
> Hello Barry:
>
> Did you try "sudo ldconfig"?
>
> If so, could you provide us the relevant software versions (GNU Radio
> version, Linux distro type, etc) and the full steps that you took to
> build the module? gr-radioteletype from "
> https://github.com/bitglue/gr-radioteletype/ " builds and runs fine on
> my machine (tm).
>
>
> Regards,
>
> Kyeong Su Shin
>
>
> ________
> 보낸 사람: ba...@dcsmail.net 대신 Discuss-gnuradio
>
> 보낸 날짜: 2019년 6월 10일 월요일 오전 5:08:32
> 받는 사람: discuss-gnuradio@gnu.org
> 제목: [Discuss-gnuradio] RTTY receiver
>
> I have been a real-time programmer for over 50 years, and a ham for 66
> years, but am new to Gnu Radio. My project is to build a complete RTTY
> receiver with SDR. In looking about for any applicable code, I found
> gr-radioteletype, but seem to be missing some of the pieces. Using the
> cmake, make, and make install steps I was able to get the flow graph to
> work, but when I try to execute it I get:
>
> "from radioteletype.demodulators import rtty_demod_cb
>No module named radioteletype.demodulators"
> and
> "include could not find load file: GrPython"
>
> What am I missing? I have searched for GrPython and not found any
> mention of it.
>
> As an alternative, I have the RTTY signal demodulated into a bit
> stream,
> and I have Python code to extract R
Re: [Discuss-gnuradio] RTTY receiver
Thank you for your response. Since this is my first issue on
'discuss-gnuradio', I am not sure how to get my reply to you posted in
the thread. This looks like it might work. If not, please let me know
what to do.
I did the "sudo ldconfig" and it got rid of the "include could not find
load file: GrPython", but not the other problem, so I decided to start
from scratch.
I have
Raspberry Pi 3 B+
Rasbian Linux (v2)
I deleted the folder 'gr-radioteletype'
download zip from https://github.com/bitglue/gr-radioteletype
extract zip to /home/pi
cd ~/gr-radioteletype-master
mkdir build
cd build
cmake ../
make
[ 5%] Building CXX object
lib/CMakeFiles/gnuradio-radioteletype.dir/async_word_extractor_bb_impl.cc.o
[ 10%] Building CXX object
lib/CMakeFiles/gnuradio-radioteletype.dir/baudot_decode_bb_impl.cc.o
[ 15%] Building CXX object
lib/CMakeFiles/gnuradio-radioteletype.dir/baudot_encode_bb_impl.cc.o
In file included from
/home/pi/gr-radioteletype-master/lib/baudot_encode_bb_impl.cc:26:0:
/home/pi/gr-radioteletype-master/lib/baudot_encode_bb_impl.h:65:5:
error: narrowing conversion of ‘-1’ from ‘int’ to ‘char’ inside { }
[-Wnarrowing]
};
^
/home/pi/gr-radioteletype-master/lib/baudot_encode_bb_impl.h:100:5:
error: narrowing conversion of ‘-1’ from ‘int’ to ‘char’ inside { }
[-Wnarrowing]
};
^
/home/pi/gr-radioteletype-master/lib/baudot_encode_bb_impl.h:100:5:
error: narrowing conversion of ‘-1’ from ‘int’ to ‘char’ inside { }
[-Wnarrowing]
lib/CMakeFiles/gnuradio-radioteletype.dir/build.make:110: recipe for
target
'lib/CMakeFiles/gnuradio-radioteletype.dir/baudot_encode_bb_impl.cc.o'
failed
make[2]: ***
[lib/CMakeFiles/gnuradio-radioteletype.dir/baudot_encode_bb_impl.cc.o]
Error 1
CMakeFiles/Makefile2:137: recipe for target
'lib/CMakeFiles/gnuradio-radioteletype.dir/all' failed
make[1]: *** [lib/CMakeFiles/gnuradio-radioteletype.dir/all] Error 2
Makefile:138: recipe for target 'all' failed
make: *** [all] Error 2
Both of the error messages were repeated *many* times. I looked at the
code for baudot_encode_bb_impl.h, but could not see any problems with
it.
I appreciate any help you can give.
Best wishes,
Barry
On 2019-06-10 00:29, Kyeong Su Shin wrote:
Hello Barry:
Did you try "sudo ldconfig"?
If so, could you provide us the relevant software versions (GNU Radio
version, Linux distro type, etc) and the full steps that you took to
build the module? gr-radioteletype from "
https://github.com/bitglue/gr-radioteletype/ " builds and runs fine on
my machine (tm).
Regards,
Kyeong Su Shin
보낸 사람: ba...@dcsmail.net 대신 Discuss-gnuradio
보낸 날짜: 2019년 6월 10일 월요일 오전 5:08:32
받는 사람: discuss-gnuradio@gnu.org
제목: [Discuss-gnuradio] RTTY receiver
I have been a real-time programmer for over 50 years, and a ham for 66
years, but am new to Gnu Radio. My project is to build a complete RTTY
receiver with SDR. In looking about for any applicable code, I found
gr-radioteletype, but seem to be missing some of the pieces. Using the
cmake, make, and make install steps I was able to get the flow graph to
work, but when I try to execute it I get:
"from radioteletype.demodulators import rtty_demod_cb
No module named radioteletype.demodulators"
and
"include could not find load file: GrPython"
What am I missing? I have searched for GrPython and not found any
mention of it.
As an alternative, I have the RTTY signal demodulated into a bit
stream,
and I have Python code to extract RTTY characters from a bit stream,
but
haven't figured out how to plug the two together.
Any help on either issue would be appreciated greatly.
Thanks, Barry KV4FV
___
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
Re: [Discuss-gnuradio] RTTY receiver
Hello Barry: Did you try "sudo ldconfig"? If so, could you provide us the relevant software versions (GNU Radio version, Linux distro type, etc) and the full steps that you took to build the module? gr-radioteletype from " https://github.com/bitglue/gr-radioteletype/ " builds and runs fine on my machine (tm). Regards, Kyeong Su Shin 보낸 사람: ba...@dcsmail.net 대신 Discuss-gnuradio 보낸 날짜: 2019년 6월 10일 월요일 오전 5:08:32 받는 사람: discuss-gnuradio@gnu.org 제목: [Discuss-gnuradio] RTTY receiver I have been a real-time programmer for over 50 years, and a ham for 66 years, but am new to Gnu Radio. My project is to build a complete RTTY receiver with SDR. In looking about for any applicable code, I found gr-radioteletype, but seem to be missing some of the pieces. Using the cmake, make, and make install steps I was able to get the flow graph to work, but when I try to execute it I get: "from radioteletype.demodulators import rtty_demod_cb No module named radioteletype.demodulators" and "include could not find load file: GrPython" What am I missing? I have searched for GrPython and not found any mention of it. As an alternative, I have the RTTY signal demodulated into a bit stream, and I have Python code to extract RTTY characters from a bit stream, but haven't figured out how to plug the two together. Any help on either issue would be appreciated greatly. Thanks, Barry KV4FV ___ 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
[Discuss-gnuradio] RTTY receiver
I have been a real-time programmer for over 50 years, and a ham for 66 years, but am new to Gnu Radio. My project is to build a complete RTTY receiver with SDR. In looking about for any applicable code, I found gr-radioteletype, but seem to be missing some of the pieces. Using the cmake, make, and make install steps I was able to get the flow graph to work, but when I try to execute it I get: "from radioteletype.demodulators import rtty_demod_cb No module named radioteletype.demodulators" and "include could not find load file: GrPython" What am I missing? I have searched for GrPython and not found any mention of it. As an alternative, I have the RTTY signal demodulated into a bit stream, and I have Python code to extract RTTY characters from a bit stream, but haven't figured out how to plug the two together. Any help on either issue would be appreciated greatly. Thanks, Barry KV4FV ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
