It is possible to run multiple POOSL simulations at once. To connect to the simulator, the debugger uses a TCP/IP port. This port is set in the run configuration created when you run or debug a model for the first time. The default TCP/IP port is 10001. In order to debug multiple models at the same time, the used TCP/IP ports should be unique.
To change the port, continue reading at "Change launch configuration settings".
When simulating POOSL models with many recursive calls of data methods, it may be necessary to increase the maximum stack size. The default setting is 8 MB.
To change the maximum stack size, continue reading at "Change launch configuration settings".
The non-determinism in POOSL models has to be resolved by the simulator. Eclipse POOSL offers the option to set the seed that is used by the simulator for resolving non-determinism. There are two options, either manually set a fixed seed, or choose a random seed each time a simulation is started. The user can make an independent choice for every single launch configuration. The default choice is to use the fixed seed 1.
The seed that is used for a specific simulation can be seen in the headline of the Console view. In particular this can be useful when using a random seed.
To change the seed, continue reading at "Change launch configuration settings".
For the simulation of a POOSL model that contains one or more external system ports, the simulator requires an External Port Configuration file. Similar to setting the POOSL model itself, the External Port Configuration file is set by providing a path to the configuration file. The configuration file has to have the INI format. By default, an INI file in the same directory as the POOSL model will be recognized and set as the External Port Configuration file.
To change the External Port Configuration file, continue reading at "Change launch configuration settings". For information on how to make use of external ports, continue reading at "Co-simulation".
To change the settings for a specific launch configuration follow these steps:
Models that are outside the workspace can be selected and run or debugged just like models inside the workspace.
You may choose to this when, for example, a model is too large to be imported into the workspace. Two features will be disabled during debugging with a model outside the workspace: