I was running my simulation in OMNeT++ 3 months ago, and now that I've tried to launch it, it says initializing and it's stuck. The only "error" I get is the java.lang.runtimeError which doesn't really say much. Even that error doesn't pop up, you need to bring it up by clicking inside the OMNeT IDE. I am using OMNeT++ 5.4.1, SUMO 0.32.0, and Veins 4.7.1.
Sumo was checked with the gui, and it runs normally. I don't know which java version needs to be installed..
Picture attached,
Simulation stuck
Please if any1 could offer a solution?
The .metadata directory in your workspace contains a detailed log of the IDE. I would try to upgrade to OMNeT++ 5.6.2 though, to use a later version of the IDE (and Eclipse which the IDE is based on)
Related
In using the Pickit4 for flashing the code.
When I first open the MPLAB X IDE and use the Make and Flash button to flash the MCU, it works fine.
But the next time in the same session, the Make and Flash button goes grey and does not do anything and I get and error saying:
Failed to initialize PICkit 4.
Then when I try to clean and build, I get an error saying:
Script engine is not supported.
I have tried deleting the persistent files and starting fresh, but the errors remain. I tried with multiple different projects, but I still have the same issue.
I'm not sure what do do next?
Is it a PICkit 4 issue?
How can I fix this?
I started seeing the same thing today. Worked fine for months until now. No MCC installed. Turns out some packs were out of date. I updated them and everything is back to normal so far.
PicKit 4
Product Version: MPLAB X IDE v6.05
Windows 10 Pro 22H2
PIC16F887
This is an issue of the MCC:
If you want to work with MPLABX5.05 you need MCC 5.2.2 (or the other way around)
It also may be neccessary when upgrading to MPLAB X IDE v6.05/MCC v5.2 on an existing MCC Classic configuration it may be necessary to update your MCC libraries for some GUIs to display properly
I've just installed MPLAB X IDE v5.30 on my computer, connected a Curiosity HPC development board, which has an integrated programmer (PICkit-on-board, PKOB), and tried to use it on a project, however, on the project settings menu, the board is detected and listed under "Starter kits (PKOB)" but shows as unsupported (like the venerable PICkit2)
Has microchip discontinued this product or is it some sort of configuration error? How can I solve it?
Project is using a PIC18F23K22 microcontroller, and the compiler is XC8 (free).
After running it through MPLAB IPE v5.20 once, by selecting the microcontroller and clicking "Apply" then "Connect" the IPE tool updated the board firmware from 01.51.07 to 01.56.00.
IPE v5.20 (old) output:
Once completed, the tool is detected by IPE version v5.30 without any apparent issue, even updating it to firmware revision 01.56.02. At this point the tool is detected no issue by the IDE as well.
OMNeT++ 5.0 with cmdenv:
Is there a way to stop a running simulation, which consists of multiple repetitions?
The Terminate-Button only terminates the current iteration, but not the whole simulation.
That is an issue with the Eclipse version OMNeT++ 5.0 is built on (Eclipse 4.4). OMNeT++ 5.1 will be based on Eclipse 4.6 and it will handle the batch cancellation correctly. OMNeT++ 5.1 pre 2 version should also work.
I'm running with OMNET 5.0 veins 4.4 and SUMO 0.25.0 ...
Everything works fine until the last time when I tried to run my code the simulation window does not appear but its icon exists in the taskbar and the simulation crashes with this error
I have all reinstaller but the problem persists (I have read in other topics that I have to verify the versions but my version is countable according to http://veins.car2x.org/download/)
Can you help me please ?!
I know only OMNeT++ Version 5.0 with INET 3.4 and Versions before ...
In OMNeT++ is Language C++ used, you have to take about nullptr or
garbarge in memory.
The first step is to run GDB in OMNeT++ this graphical user interface
in eclipse editor is quite enough to get neccessary information.
If it don't run after simple checking memory, objects, nullptr, exceptions and so on. See working with valgrind http://www.eclipse.org/linuxtools/projectPages/valgrind/
But usally it is enough to workout with GDB, try to initialize everything, check exception and it works sthhow ...
I wonder why every once in a while, Intel RealSense 3D camera fails to start? I have re-installed the drivers and SDK as well as the DCM but still it is whacky and very unpredictable. Any idea what the source of the problem could be? It should be able to run the examples in the SDK in a normal working situation.
Well, previously that it couldn't init problem was that only two of the its drivers could be recognized (not the virtual driver) like the following but now all of its driver are recognized and still it can't init.
so I am receiving an init failed message when running the SDK examples.
Any pointer for fixing is really appreciated.
If you are also showing an integrated webcam (other than the 3 RealSense listings), try disabling that so the RS camera can be seen as the primary.
Actually you can select the device you want to run the sample on in the menu "Device". If you installed the RealSense correctly and if the latest DCM is running (the current version is 1.4 if I remember), you should be able to select the RealSense device there and then run the sample.
Sometimes the DCM Service fails to start (e.g. if you force-restarted your machine recently). Then you just need to make the service restart and it should work.
Hope this helps.
I’m also facing the same problem (on windows 10), and found a way that solved it for me: search “Scanners and Cameras” in Control Panel, choose “Add Device”, under “Manufacturer” choose “Intel” and under “Model” choose “Intel(R) RealSense(TM) Camera SR300 Virtual Driver” or the version you use, and continue to install.
Have you installed the right drivers? There are two versions of the real sense cameras. The Windows 10 works with Intel Real Sense R3 which has completely different architecture than its predecessor.