Skip to main content Accessibility help
×
Hostname: page-component-77c89778f8-vpsfw Total loading time: 0 Render date: 2024-07-24T08:15:12.321Z Has data issue: false hasContentIssue false

15 - OPNET co-simulation with third-party programs

from Part IV - OPNET Modeling Facilities

Published online by Cambridge University Press:  05 February 2012

Zheng Lu
Affiliation:
University of Essex
Hongji Yang
Affiliation:
De Montfort University, Leicester
Get access

Summary

In this chapter, the co-simulation capability of OPNET Modeler is introduced. The co-simulation interface allows OPNET Modeler to interact with external systems during simulation. These external systems can be software programs, hardware devices, or simply humans. Co-simulation is often used in situations where some third-party programs need to be used to process or analyze the intermediate simulation results, or some real-world data needs to be collected and fed back to OPNET Modeler during simulation.

Co-simulation with external programs

Introduction

OPNET Modeler provides a mechanism to support live interaction with an external system during simulation. This co-simulation mechanism involves the following concepts:

  • External System Definition (ESD) model. The ESD model defines a set of interfaces that allow processmodels in OPNETmodeler to communicate with external programs. These interfaces can be read or written by both OPNET process models and external programs.

  • Esys (External System) module. The Esys module is a node domain module that can be placed into a node domain and processed as are other node domain modules, like processor module and queue module. However, the Esys module has extra features: it supports process models with external system communication capability and supports ESD models. The Esys module allows the user's simulation model to talk to external systems.

  • Simulator description file. The simulation description file is a plain-text file containing statements that specify how to build co-simulation. This text file should be placed in the OPNET model directory and has the filename extension “.sd”.

  • […]

Type
Chapter
Information
Publisher: Cambridge University Press
Print publication year: 2012

Access options

Get access to the full version of this content by using one of the access options below. (Log in options will check for institutional or personal access. Content may require purchase if you do not have access.)

Save book to Kindle

To save this book to your Kindle, first ensure coreplatform@cambridge.org is added to your Approved Personal Document E-mail List under your Personal Document Settings on the Manage Your Content and Devices page of your Amazon account. Then enter the ‘name’ part of your Kindle email address below. Find out more about saving to your Kindle.

Note you can select to save to either the @free.kindle.com or @kindle.com variations. ‘@free.kindle.com’ emails are free but can only be saved to your device when it is connected to wi-fi. ‘@kindle.com’ emails can be delivered even when you are not connected to wi-fi, but note that service fees apply.

Find out more about the Kindle Personal Document Service.

Available formats
×

Save book to Dropbox

To save content items to your account, please confirm that you agree to abide by our usage policies. If this is the first time you use this feature, you will be asked to authorise Cambridge Core to connect with your account. Find out more about saving content to Dropbox.

Available formats
×

Save book to Google Drive

To save content items to your account, please confirm that you agree to abide by our usage policies. If this is the first time you use this feature, you will be asked to authorise Cambridge Core to connect with your account. Find out more about saving content to Google Drive.

Available formats
×