Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

ThomDietrich/multiUAV-simulation

Folders and files

NameName
Last commit message
Last commit date

Latest commit

History

319 Commits

Repository files navigation

multiUAV Simulation in OMNeT++

  • Stationary, mobile and airborne nodes (UAVs,...)
  • Charging stations
  • Mission control
  • MAVLink commands based flight planning
  • Energy consumption simulation
  • Energy maintenance operations
  • Optimization
  • Visualization

simulation example

Preparation

Boost is needed by this program. Please download here: http://www.boost.org/users/history/version_1_55_0.html Copy the folder boost into the subdirectory include-boost of the OMNeT++ base directory.

Example Result: C:\omnetpp-5.4\include-boost\boost\version.hpp

Running the simulation

scenario example

Running in OMNeT++ IDE

In subdirectory ./run_config you can find predefined run and debug configuration ready to go with OMNeT++ IDE.

All launches are preconfigured to run the Gabelbach scenario.

  • multiUAV-simulation cmdenv.launch 🡺 launches all runs without user interface (i.e. QTenv), that includes interating over all replacement modes and repeat for 10 times
  • multiUAV-simulation cmdenv (0).launch 🡺 launches without user interface Run 0, i.e. replacement mode 0 and no repetition
  • multiUAV-simulation debug.launch 🡺 launches the simulation with user interface, with debug information (should be run as debug) and Run 0
  • multiUAV-simulation release.launch 🡺 launches the simulation with user interface in release state and Run 0

Results

Results for Gabelbach scenario will be placed in subdirectory ./results. Depending on your launch configuration, you will find a different amount of output files. However, for each successfully finished simulation run, there should be following files:

  • *.elog: Eventlog
  • *.out: everything written to the ouput console
  • *.sca: scalar results that include the final results including the six main figures:
    • utilizationEnergyOverdrawMaintenance
    • utilizationEnergyOverdrawMission
    • utilizationEnergyMaintenance
    • utilizationEnergyMission
    • utilizationSecMaintenance
    • utilizationSecMission

About

Discrete event simulation framework aimed at UAV movement, energy management, and signal propagation

Resources

License

Stars

Watchers

Forks

Packages

Contributors

AltStyle によって変換されたページ (->オリジナル) /