-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
emane-spectrum-analyser not working #1
Comments
You can verify your install without using CORE by running
Or if you want to use emane-jammer-simple:
You'll need to install letce2 and letce2-plugin-lxc either by compiling from source or from the latest bundle. |
Hi Steven, I downloaded:
unzip them under Download: Changed to: ~/Downloads/letce2-0.2.7 Changed to: ~/Downloads/letce2-plugin-lxc-0.2.5 Changed to: ~/Downloads/letce2-tutorial-master ==> I started the experiment with: ==> see the output I attached I saw errors like: I tried then to access node-1 via ssh: enter: ssh node-1 Did I something wrong with the installation? Thank you Steven for your help! |
You are just missing some of the dependencies, like oslrd which are used in the experiment. This tutorial has the same external dependencies as the emane-tutorial and the same addressing:
You can ignore the |
Hello Steven, ssh 10.99.0.1 worked! but not node-1 Question: what is missing that radio's and node's are known to the system with their respective address? Do I something missing -maybe in the installation? Was my installation correct as described in the last post? "ping" was also possible! Then I tried to run the script emane-spectrum-analyzer.sh
==> nothing happens! Any idea why the GUI dosn't show up? |
Add the following to /etc/hosts
What linux distro and version are you running? |
ubuntu18.04 CORE-Version: 7,4.0 was this correct? |
I typically install debs, either prebuilt or via |
Hello Steven,
I added some screen shots, I would really appreciate if you could have a look to it. best regards, |
One additional hint:
Then I reinstalled the skipped deb file one-by-one... mt@mt-VirtualBox:~/Downloads/emane-1.2.7-release-1/debs/ubuntu-18_04/amd64/exlude_debs$ sudo gdebi python3-pynodestatviz_0.2.3-1_all.deb Could this be the source of the problem?? |
You need to ping over the |
python3-pynodestatviz_0.2.3-1_all.deb could not been installed because of missing python3_pmw... |
In this experiment, think of the emane-spectrum-monitor as a spectrum analyzer positioned at the same location as node-6. It will show you any energy it sees based on pathloss between nodes. You can give the emane-spectrum-monitor any NEM id, you just need to supply pathloss between the transmitter(s) and that id. Here we reused NEM id 6, to show you what 6 would see. One downside to not using a unique NEM id for the emane-spectrum-monitor is that it will not display any energy transmitted by the radio model instance with the same id. python3-pmw is not needed for this experiment. It is a dependency for a display tool (pynodestatviz) used in the emane-tutorial. |
Thank you Steven for you valuable infos!!! If I want to see the spectrum of node-6 of received and transmitted data over the ota-channel - what you suggest to do? Or - if I just have 2 nodes and want to verify the spectrum over the air - maybe with a potential jammer - and if the jammer is transmitting - that I can see this in the spectrum. As I would see it when I have 2 real radios and add some broadband noise in this channel. Or the pathloss changes and the spectrum get's smaller and smaller... Do you have some more infos concerning the OTA channel and how it works under the hood ...? (just that I can explain it in a better way to colleagues if I show them the "virtual" spectrum-analyzer) Thank you Steven! |
emane-spectrum-monitor uses the same physical layer model as emane. There are protections in the code that prevent the model from receiving its own energy over-the-air. This is different than modeling self interference which is handled internally within some radio models. If you change the configuration of emane-spectrum-monitor and assign a different NEM id, one that is unique, you will see all energy that is received based on the pathloss set between all transmitters and the emane-spectrum-monitor id. Yes, the activity you are seeing is from the routing protocol: olsrd. If you disable olsrd you will not see any activity unless you generate over-the-air transmissions. For example, from any node ping the radio address (10.100.0.0/24) of any other node. If you want to try jamming, you can clone and build emane-jammer-simple. And do the following:
|
I am trying to build the EMANE Spectrum Analyzer on an EMANE v1.2.5 build running on RHEL8. However, running Install EMANE Spectrum Tools (version 0.2.2)
Install LETCE2 (version 0.2.5)
Install LETCE2-Plugin-LXC (version 0.2.3)
Clone letce2-tutorial Install the following dependencies:
I'm do get the |
If you install from the latest bundle release you will have all the dependencies managed for you. A bundle release contains prebuilt packages for all @adjacentlink foss. As far as |
Thanks for the response! As of right now, I am trying to get the Spectrum Tools to work with EMANE v1.2.5 since my project is using a third-party EMANE Model that requires v1.2.5 of EMANE. That being said, do you have any suggestions on how to troubleshoot why the GUI does not pop up at all? For reference, I have tried running the following code (some parts such as the grid and the style was taken directly from emane-spectrum-analyzer:
The code above has the output: Since the GUI pops up with a simple plot, I am convinced that matplotlib and it's required dependencies are installed correctly. Does the spectrum analyzer have some sort of logging system that would log events when the script is called? I am aware that there are catch statements but I do not see any errors thrown on the console. Another thing I'd like to point out is that when I perform a Thank you for your time. |
HEllo,
after installation of CORE and EMANE
CORE-Version: 7,4.0
Emane.Version: 1.2.7
and installation of emane-spectrum-tools version: v0.2.5
according to the command lines in the readme file:
$ cd /home/mt/Downloads/emane-spectrum-tools-0.2.5
$ ./autogen.sh && ./configure emane_SRC_ROOT=/home/mt/emane
then
make
sudo make install
--> emane spectrum tools got installed in: /usr/local/bin
I use a simple core model consisting out of 3 wireless routers configured for rfpipe channel model.
I tried to get the OTA channel working / accessing it – in particular tried to get the spectrum analyzer working for this small scenario.
Using Wireshark I can see the Multicast packet from the 3 nodes. So far so good.
I also be able to ping the other nodes.
Then I tried to get the emane-spectrum-analyser to work.
I did the following:
My software configuration:
CORE: 7.4.0
EMANE: 1.2.7
Emane-spectrum-tools: 0.2.5
I use the following CORE model:
3 wireless CORE nodes using the rfpipe channel model
„emane-spectrum-monitor“ configuration: (from your example on github)
FILE: emane-spectrum-monitor.xml
“emane-spectrum-analyser” configuration:
emane-spectrum-analyzer /
10.0.0.1:8883 /
-100 /
--hz-min 2300000000 /
--hz-max 2500000000
Steps I did:
emane-spectrum-monitor
--config emane-spectrum-monitor.xml
-r
-d
-l 3
-f /var/log/emane-spectrum-monitor.log
--pidfile /var/run/emane-spectrum-monitor.pid
--uuidfile /var/run/emane-spectrum-monitor.uuid
7. go to the host and open a terminal
8 . enter ssh –X 176.16.0.1 to get access to node 1 in my CORE/EMANE model
9. change then to the folder of node 1: cd /tmp/pycore.45749/n1.conf
And copy/paste this:
emane-spectrum-analyzer
10.0.0.1:8883
-100
--hz-min 2300000000 \
--hz-max 2500000000
No GUI appears on the screen...
I also had seen a GUI before I struggle around with python versions... but without any spectrum...
How I can verify that the emane-spectrum-monitor is working correctly?
I would really appreciate any help from you guys.
Thank you very much for you effort! You guys do a fantastic job!
best regards,
Martin
emane-rfpipe_simple_mt02.txt
P.S: I attached my model as well
The text was updated successfully, but these errors were encountered: