For me, after a lot of hassle and manually fixing stuff I had an apparently unfixable library mismatch. To do this, start by installing pip:. For the impatient, these were the commands that did the trick the last time I checked:.
This last step can easily take a few hours, so be patient. Normally, Linux would install everything in various locations; doing this ensures everything is installed in one folder. This is really useful if you mess things up, since you can simply delete the prefix folder and try again.
Now, every time you want to start GNUradio in a new terminal, execute the following commands:. Forgetting this has cost me a lot of extra hassle at times. Now GNUradio should be working! Next up is installing the repository by Bastian Bloessl, you can find out how to do this in detail here.
Some tips to overcome obstacles I encountered are:. Now, you should have Bastian's blocks working. Try to go through some of his examples to see if they are working. Note that this is not a full Feel free to pick this up if you're interested! If things don't work out, please check Bastian's repository first. I tried to mess around with installing and changing custom drivers for my ethernet adapter, but all to no avail.
Installing native Linux immediately solved this and many other problems. Therefore I heavily recommend to isntall Linux natively, especially if you are not an advanced Linux user like me.
Skip to content. Star IEEE Branches Tags. The physical layer is encapsulated in a hierarchical block to allow for a clearer transceiver structure in GNU Radio Companion. This hierarchical block is not included in the installation process. Therefore, please open the flow graphs and assert that everything is connected. It should be pretty obvious how the blocks are supposed to be wired.
Actually this should not happen anymore, so if your ports are still unconnected please drop me a mail. If you want to run the receive demo the one that plots the subcarrier constellations , please assert that you have python-opengl installed. The nongl version of the plot does not work for me. It benchmarks different SIMD implementations on your PC and creates a configuration file that stores the fastest version of every function.
This can speed up the computation considerably and is required in order to deal with the high rate of incoming samples. See the application notes. This flow graph does not need any hardware and allows you to ensure that the software part is installed correctly. So open the flow graph and run it. If everything works as intended you should see some decoded packets on the console.
If GRC complains that it can't find some blocks other than performance counters and hierarchical blocks like. Therefore, the blocks of the module ended up in a different directory and GRC can't find them. The loopback flow graph should give you an idea of how simulations can be conducted. To ease use, most blocks have debugging and logging capabilities that can generate traces of the simulation.
Just open the flow graphs in GNU Radio companion and execute them. If it does not work out of the box, try to play around with the gain. Please check compile and installation logs. They might contain interesting information. These blocks allow you to monitor the performance of the transceiver while it is running, but are not required. You can just delete them from the flow graph. You must now use ifconfig to set its IP address. Skip to content. Star
0コメント