Modeling with External Systems

The esys module is a superset of the queue module, containing all of the attributes of a queue. If the possibility exists that a model will be used in a cosimulation at some point, even if not immediately planned, use the esys module instead of the queue or processor object. It is much more difficult to upgrade a queue or processor to an external system than it is to start out with the external system in the first place. When upgrading to an external system from an existing processor or queue, you must delete the previous module and then create an esys module, set its attributes, and establish streams and other links.

Because Modeler treats an external system as a black box, it has no way to know what happens to the data it passes through the external system. The model developer must decide on the meaning and format of the data that is to be passed through the ESD in both directions. On the Modeler side, the model developer is responsible for building the ESD and constructing the process model that serves as an interface between the external system and Modeler. The external code determines the behavior of the external system and then sends data through the ESD’s esys interfaces for the module’s process model to handle.