|
Creating the VTB models
The VTB entities can be created in many different ways. The
VTB models created using various tools can be classified as interactive and
compiled entities. Interactive entities are built and executed during the VTB
software run time, while compiled entities are typically created by means of
other computer languages that require subsequent compilation of the entity’s
code. An advantage of interactive VTB models is that it is very easy to change
the structure of the model while the VTB software is running. However,
interactive models may be executed more slowly. An advantage of compiled VTB
models is that they are executed faster than interactive models. On the other
hand, it is not possible to change the model’s structure while the VTB is
running. To make any change in the compiled VTB model it is necessary to perform
subsequent re-compilation of the entity’s code.
The interactive signal VTB models can be created using the following methods.
1) Interactive Simulink model import. The model is originally created in Simulink and imported to the VTB using the VTB wrapper entity. This method requires a valid copy of the Matlab/Simulink software. When performing simulation, Matlab will start automatically and will run concurrently with the VTB software.
2) Interactive Matlab model import. The model is originally created in Matlab and imported to the VTB using the VTB wrapper entity. This method requires a valid copy of the Matlab software. When performing simulation, Matlab will start automatically and will run concurrently with the VTB software.
3) Interactive signal models can also be created in the VTB using the User-Defined Device. This method does not require any additional software besides the VTB.
The interactive natural VTB models can be created using the following methods.
4) Interactive Simulink model import. The model is originally created in Simulink and imported to the VTB using the VTB wrapper entity. This method requires a valid copy of the Matlab/Simulink software. When performing simulation, Matlab will start automatically and will run concurrently with the VTB software.
5) Interactive natural models can also be created in the VTB using the User-Defined Device. This method does not require any additional software besides the VTB.
The compiled signal VTB models can be created using the following methods.
6) Compiled Simulink model import. The model is originally created and compiled in Simulink. This method does not require use of the VTB wrapper entity. The model is directly available in the VTB. This method requires a valid copy of the Matlab/Simulink software with the Real-time Workshop and a C++ compiler.
7) Compiled Labview model import. The model is originally created and compiled in Labview and imported to the VTB using the VTB wrapper entity.
8) Compiled ACSL model import. The model is originally created and compiled in ACSL and imported to the VTB using the VTB wrapper entity.
9) Compiled Fortran model import. The model is originally created and compiled in Fortran and imported to the VTB using the VTB wrapper entity.
The compiled natural VTB models can be created using the following methods.
10) Compiled Simulink model import. The model is originally created and compiled in Simulink. This method does not require use of the VTB wrapper entity. The model is directly available in the VTB. This method requires a valid copy of the Matlab/Simulink software with the Real-time Workshop and a C++ compiler.
11) Compiled ACSL model import. The model is originally created and compiled in ACSL and imported to the VTB using the VTB wrapper entity.
12) Compiled Fortran model import. The model is originally created and compiled in Fortran and imported to the VTB using the VTB wrapper entity.
13) Compiled natural models can be created in the VTB using the VTB Model Builder. This method requires Matlab, Real-time Workshop, and C++ compiler. The VTB Model Builder uses SPICE-like language to create the VTB models.
14) Compiled natural model import through the Paragon software. Models originally created in Modelica, VHDL-AMS, ACSL, etc. can be brought to the VTB environment through the Paragon software. Paragon first invokes the Multi-Translator, which brings the model into the universal XML based specification. After that, Paragon brings the XML specification of the model into the form required by the User-Defined Device (UDD) software, which is part of the VTB development kit. The UDD creates the C++ source code for the model, which can then be compiled and used as a native VTB entity.
15) Compiled natural models can also be created in the VTB using the User-Defined Device . This method requires a C++ compiler.
Finally, VTB models can be created in the C++ language directly. For more information about how to create VTB model entities in C++, please see the VTB Modeler’s Guide.
