shinysdr --create dir-name #143
Assignees
Labels
Comments
|
From the module path, you're running Python 3. Check if your GNU Radio installation is compatible — you need to either use GNU Radio 3.8 or later for Python 3 compatibility, or run ShinySDR with Python 2.7 as GR 3.7 or earlier only works with Python 2. (Note: Unfortunately, because the package I use myself is lagging, I haven't gotten to testing ShinySDR with GR 3.8 yet, so there might be problems. I've worked to ensure ShinySDR runs on Python 2 and 3 but only the non-GR-using parts have been actually tested. But, that's not the problem you're seeing.) |
|
My GNU Radio version is 3.7.13.5 and i set my comp to run programs with python2.7 by default: This program is part of GNU Radio [fort@localhost shinysdr]$ python --version |
|
The version being used by the shinysdr command is 3.7 as indicated by the paths: So, you need to reinstall shinysdr using your python 2.7.17 instead of your python 3.7. |
|
After i remove everything, I started fresh install. I used comand $python2.7 setup.py build and python2.7 setup.py install. Thats the full log I get : |
|
It looks like the |
|
Ok thank you so much, now i was able to create config dir, but when i execute $shinysdr ./config-myConfig-dir i get error. Here is the output |
|
As the message says, you are missing the Python bindings for gr-osmosdr. Make sure you have gr-osmosdr installed. I've heard there was some delay in updating gr-osmosdr for GNU Radio 3.8 — you might need to get a package from somewhere other than your distribution; I don't know what the situation on Fedora is. A quick direct test without using shinysdr is to run |
|
Thanks for your replay, installing gr-osmosdr server was able to start, but as soon i enter the link localhost:8100/........./ i get segmentation fault(core dumped) error. Here is the output: INFO:shinysdr:Mode WSPR unavailable |
|
This is almost certainly a bug in GNU Radio or other libraries loaded by ShinySDR, but there might be a workaround. In order to give any further advice I will need a stack trace extracted from that core dump. |
|
Alright yesterday i create ubuntu19 VM on my machine and install shinysdr with gnuradio 3.7 without any problems, but because its VM i was having some serious lags, so i decided to fully migrate to Ubuntu. I installed ubuntu 20 but when i installed GNUradio and tried to run shinysdr i got error: ImportError: No module named gnuradio Again i installed Shinysdr with python 2.7 , but this time my GNUradio was 3.8 version, I guess thats why when i type python >>> import gnuradio , its gives me error no module, but when i type: python3 >>> import gnuradio , there is no longer error. So my question is is it possible to install Shinysdr with GNUradio 3.8 or latter, because I am having difficult installing GNUradio 3.7 or earlier ? |
|
I have not yet tested ShinySDR with GNU Radio 3.8. I don't know of any reason it won't work, and I certainly want to fix it if it doesn't, but I can't make any guarantees, and it's highly likely there will be some problem — hopefully easily fixed once we see the error message. |
|
Yah 3.8 is a major upgrade and it won’t work. I wanted to write some TSCM modules and signal intelligence modules for it but thing I’m going to scrap that idea because it can’t work w 3.8 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello I'm having problems with creating config directory, when i add command shinysdr --create /configSDR/ i get this:
P.S The program was working great when i was running Fedora 29, but when i upgrade to Fedora 31 i start having problems.
Any suggestions ?
The text was updated successfully, but these errors were encountered: