vsTASKER 7 User Manual
×
Menu
Index
Search
 
   
   
   
 
Copyright VirtualSim 2004-2020 - All rights reserved

Runtime

 
vsTASKER generates C++ code and produces an executable (or a dll depending on the settings).
If the GUI needs a database (.db) located normally in data/db directory, the runtime engine needs the corresponding compacted database containing everything needed by the engine for the simulation.
 
This database must be associated with the executable. It carries the same name as the executable with .rt extension. The runtime database is recreated every time the database is changed and saved from the GUI. You will find it in the same directory as the executable.
 
 
Runtime
1

Path

1. Path
Directory where the output (EXE/DLL/COM) is produced, the makefile is generated and the Runtime Database (.rt) is located.
 
2

Name

2. Name
Name of the executable (without .exe or .dll) and the corresponding runtime database.
The extension depends on the output type selected in Link (Generates).
 
To remember: For deployment of the simulation engine, in standalone mode, always include the runtime database (.rt). Standalone executable can be obtained from the Scenario property window.
 
3

Slave Mode

3. Slave Mode
If checked, the RTC waits for an external TIC to advance of one cycle.
 
4

Real-Time Mode

4. Real-Time Mode
Specify if the RTC must run in Real-Time or Asynchronous mode. In Real-Time mode, The frequency is kept (if possible) through cycles. For example, if 30 Hz specified, then, every second (on the user clock), the RTC would have processed 30 cycles (one cycle every 33 milliseconds). In Asynchronous mode, the Integration Time is used to define the cycle length.
 
5

Settings

5. Settings
RTC Base: Value of the base frequency for the RTC in Real-Time mode.
Clock Base: Not used
Integ Time: In Asynchronous mode, value of the cycle in milliseconds the RTC must keep.
 
6

Working Dir

6. Working Dir
Add here the directories which will be added to the path when calling the Simulation Engine.
The paths added will not change the User or System path. It will only be set for the duration of the simulation run.
 
7

Reduced Path

7. Reduced Path
When checked, the runtime path will be cleaned and only contains the $(VSTASKER)\bin... directories plus the Working Dir ones (see above).
Use this option when the simulation engine crashes because of some others DLL found on the path instead of the correct ones.
When unchecked, the user/system path will be used as is.
 
 
8

Reduced Database

8. Reduced Database
When selected, User (entered) code and help data are excluded from the Runtime Database (.rt), making it smaller in size and reducing the memory foot-print.
This is the default.
 
9

Time Control Mode

9. Time Control Mode
Choose between:
- Best for CPU release the CPU between cycle if time permits.
- Best for Accuracy keeps the load and wait for the integration time to be over before triggering the next cycle (or returning in case of an external call).
 
10

When Overrun

10. When Overrun
Choose between:
- Ignore will leave the internal time unchanged.
- Recup Time will try to keep the same number of cycles per second by reducing the wait time between cycles.
 
11

Starting Mode

11. Starting Mode
Choose between:
- Launch Only (default) does not start automatically (unless standalone mode). User must depress the Start button to start the simulation.
- Start and Pause will initiate a one cycle only start (without any time advance) to prepare the simulation. Pause mode is engaged. Press Start button to start the simulation.
- Auto-Start will start normally the simulation right after launch of the simulation engine. This mode should be selected for standalone executable, unless a START button is added into the HMI or if the start is provided by another mean (then Start and Pause shall be a better option).
The Start and Pause mode works only once. When Stop is depressed, the restart will be operating normally (no pause).