I am having trouble getting Omnet++, Veins, and Sumo to work together. I am progressing through this tutorial to get started. I am currently on the Final Step and I am getting some error that I was hoping someone had some insight on.
I am installing Omnet++, Veins, and Sumo on a virtual machine in Centos 7. I have been through the installation of these three programs twice and I believe I have correctly completed all the steps, although I am pretty new to linux and could have made a mistake.
Here is a link to a screen shot from Omnet when I run the example code from the Final Step:
The library it failed to load is libosg.so.130. This looks like an Open Scene Graph library. I was getting a very similar error yesterday having to do with a osgEarth library. I was able to get around this by disabling selinux, which was blocking some shared libraries from being accessed. I tried the same solution with libosg with no avail. Is there a different antivirus/firewall on Centos that I should turn off? Or is there another idea I should look into?
Any help would be appreciated! Thanks!
EDIT, SOLUTION: I fixed the error by adding the folder /usr/local/lib64 to my path by editing the bashrc with gedit ~/.bashrc and adding "export PATH=$HOME/omnetpp-5.1.1/bin:$PATH:/path_to_folder" to the bottom of the document.
Related
I am using cubeIDE version 1.8.0 and NucleoF746ZG microcontroller for my project. I have made the codes and when I compile and run they work properly without errors and warnings. But the problem is that when I try to debug, It doesn't work. I mean the debug code uploads to the board but no cursor shows up at the breakpoints. I have tried to make some breakpoints and hault the program at them but no cursor comes to them.
I have opened a trace control tab and it says "Tracing is not supported". I don't know why that happens. The only thing that I know is that after installing the software, It didn't recognized my st-link. It was fixed after replacing the libusb-1.0.dll to a newer version of it. That was the thing that I have changed. But I don't think that it will affect since compiling and running works properly.
If anyone has encountered this issue or if you have any clues about a cause for this matter, please let me know. And request me if you need any more details from my side. I have attached two screenshots for reference.
Thanks and Kind Regards...
Screnshot1
Screenshot2
I was trying to use OMNeT++ earlier today but I was unable to get any simulation to run. I tried numerous model simulations but they began hanging at the same place during initialization. I deleted and re-installed OMNeT++, but the problem persists. So even after a fresh install of OMNeT++ v5.5.1 on a Windows 10 v1903 machine, I am unable to run any simulation. This is what I saw when I ran the Aloha sample simulation executable directly after following all the OMNeT++ installation steps:
The Qtenv simulation window starts up but it's completely blank, and I can't actually focus on it, which leads me to believe there's something up with Qt. The program hangs indefinitely at this point. OMNeT++ was configured using the default values found in configure.user.
Any suggestions?
EDIT:
This is the last console output I receive after running QT_LOGGING_RULES="*.debug=true" ./aloha.
This is the last console output I receive after running QT_DEBUG_PLUGINS=1 ./aloha.
Did you connect additional monitor to your computer? Sometimes Windows remember position of an application on non-existed screen. Try to change your screen properties or connect second screen and look for Qtenv window of Aloha simulation.
Besides the above, delete .qtenvrc from samples/aloha.
OMNETPP 5, GUI nodes are overlapped with each other!
I am new in OMNETPP environment and working with omnet++ 5.
While developing my first network, I created the tic-toc network and find okay.
But after some while, when I again run it, I found the nodes are overlapped with each other (see the attached pic) and its happen every times.
It is happening for most of my own projects, but not with the sample projects.
Does anyone have any clue please?
Check your doctrine configuration. Maybe XML mapping overrides annotations and that's why it's not working.
FH Overlapped Nodes:
I'm having the same issue. In omnet 5 all networks suddenly looked like yours. I changed back to 4.6 as a colleague didn't seem to have this problem and he's running 4.6. In 4.6 the tic/toc examples look and runs fine, however my custom network doesn't.
The screen I attached shows how the network looks in the editor vs how it looks in the simulation environment (in 4.6).
#edit: found the problem: Omnet decided to zoom out to 0.01x without telling me. Zooming in finally revealed, that everything was where it is supposed to be...
I am curious about the Lab of Things and i've just started to learn it.
I am studying it in the network lab of my university. We have a z-wave controller stick, 2 on/off switch, 1 dimmer receiver and 1 sensor.
To set and run the platform, i followed the instructions in this link below:
http://www.lab-of-things.com/GettingStartedLoT_Beta1.pdf
While running the source code and adding a z-wave device, I faced an annoying problem here.
After adding the z-wave driver and running the code i saw 4 different device on the dashboard, it looks like below:
I tried to install these nodes and applications but apps are not installed. I think that's why i get an error message like below when i run the platform:
I searched on the internet for this error and i found a discussion like this error but i couldn't apply the solution. In this discussion they say that the applications (alerts, sensor, lights etc.) should be compiled seperately. I tried to do it but Visual Studio still gives the same error.
Here is the link of discussion that i found on the internet:
https://labofthings.codeplex.com/discussions/476781
All answers will be appreciated.
Thank you in advance.
I solved this problem by following these instructions which are written in this link:
https://labofthings.codeplex.com/discussions/476781
" For starters, it looks from the screenshot posted on stackoverflow that you have broken configuration at this point—the access control rules (in output\configs\config\rules.xml) have a reference to module Alerts but that module is not listed in output\configs\config\modules.xml
To fix the config, 1) run reset.bat, which will reset your configuration to default; or 2) fix it manually if you think you understand the semantics.
Then, make sure that the apps you want to use are compiled. Their binaries should show up in output\binaries\pipeline\addin\homeos.hub.apps.alerts.
Then, go through the setup process again, and things should work at this point in time.
A little more on this: we have confirmed that broken configuration will occur when app binaries are not found. We will post a bug fix soon, but for now, the remedy in my original response (reset, compile, then install device) should work. Let us know if you are still seeing issues. "
I hope this would be helpful for someone.
I believe this is similar to the thread: Canon SDK 2.11 on OSX
However the solution there did not work for me. I'm perplexed because I'm not sure how to figure out what has changed. I had some working software, did not work on it over the holiday and now when I open it up to work it fails. Not only my software but the demo app included with the SDK, which I have never changed and indeed used to work just fine.
I have tried with two different cameras (5DmII and 5DmIII) with the same result.
when I try and run the application, the camera is recognized but, as it attempts to open a session it receives a EXC_BAD_ACCESS signal. In each program it happens when a call is made to EdsOpenSession() with this message...
*** -[NSConcreteData release]: message sent to deallocated instance 0x8157af0
Interestingly, when I tried to use the EOS Utility that would crash also. So I updated and now that works great. I followed the suggestion in the above thread and copied the EDSDK.framework from the working bundle to my program and recompiled but I get the same results.
I'm trying to figure out how to contact Canon to get some information but they don't make it easy to get help so I'm appealing to the one group I know is responsive.
The only thing I can think is that sometime over the holiday I updated some critical library without knowing it.
Has anyone else run into and been able to solve this?
I'm running OS X 10.7.5, xcode 4.1, and EDSDK 2.11.3
Solved this. It did turn out to be the same solution as the mentioned link. However, what I was missing was that I needed to also copy the new EDSDK.framework into /Library/Frameworks not just have it in my source directory. This may be because I don't have everything setup correctly in XCode.