Difference between revisions of "Simulink Tester for T-VEC"

From T-VEC Wiki
Jump to: navigation, search
(Test Driver Generation)
 
Line 17: Line 17:
  
 
There are potential [[Simulink Tester Issues|limitations, usage issues, and guidelines]] associated with the integration of  Simulink/Stateflow with T-VEC.
 
There are potential [[Simulink Tester Issues|limitations, usage issues, and guidelines]] associated with the integration of  Simulink/Stateflow with T-VEC.
 +
 +
==Recent Changes==
 +
<p>
 +
<b>T-VEC Tester for Simulink and Stateflow 4.5.0 is now generally available.</b>
 +
</p>
 +
<p>
 +
New and improved features in the Simulink Tester include:<ul><li>Improvements in the support of the following Simulink blocks - matrix concatenation, if, relay, sum, gain, product, lookup tables, data type conversion, initial condition, for,
 +
multiport switch, subsystem, and discrete time integrator blocks.</li>
 +
<li>Stateflow chart and truth table support has been enhanced.</li>
 +
<li>Additional checks warn of model problems or issues detected during translation</li>
 +
<li>Improved Simulink simulator test driver support in default schema.</li>
 +
<li>Improved C/C++ test driver support in default schema.</li>
 +
<li>Enhanced Embedded Matlab (EML) support</li>
 +
<li>Corrected issues with default support of Matlab R14 SP2</li>
 +
<li>Sl2tvec GUI now provides explicit indications of the inline vs atomic function status of each subsystem. All Simulink subsystems that are non-atomic, or atomic-auto, or atomic-inline will be indicated as "inlined into Parent".</li>
 +
</ul>
 +
 +
Please see the [https://www.t-vec.com/support/secure/readme.php?ID=147 Release Notes] for more details on the changes in this release.
 +
</p>
  
 
==Design Model==
 
==Design Model==
Line 52: Line 71:
 
==Test Driver Generation==
 
==Test Driver Generation==
  
The Simulink Tester provide test driver schemas for the ERT and GRT code generators supported by the Mathworks RTW, as well as the Matlab Simulator. Howevever, target execution environment have differences, and the tools provide a general purpose test driver template/schema language for describing a generic test driver that can then be instantiated with test vector information by running the test driver generator. An organization can create any number of test driver scripts/programs that are targeted to specific target environments. Schemas can be created from scratch or tailored from schemas provided with the tool installation.
+
The Simulink Tester provide test driver schemas for the ERT and GRT code generators supported by the Mathworks RTW, as well as the Matlab Simulator. Howevever, target execution environments have differences, and the tools provide a general purpose test driver template/schema language for describing a generic test driver that can then be instantiated with test vector information by running the test driver generator. An organization can create any number of test driver scripts/programs that are targeted to specific target environments. Schemas can be created from scratch or tailored from schemas provided with the tool installation.
  
In the case of LDRA's TBRun environment, the installation provides a few default test driver schemas that are designed to produce .tcf  files. These are located in the install area, normally in the directory  
+
These are located in the install area, normally in the directory  
  
 
   C:\t-vec\translators\sl2tvec\test_drivers
 
   C:\t-vec\translators\sl2tvec\test_drivers
  
Schemas are provided also with the TTM training examples that are normally located in the directory
+
In the case of LDRA's TBRun environment, the Simulink Tester for T-VEC installation provides a few default test driver schemas that are designed to produce .tcf  files.
 +
 
 +
There are other schema examples with the TTM training examples that are normally located in the directory
  
 
   C:\t-vec\examples\ttm\course\exercise_answers
 
   C:\t-vec\examples\ttm\course\exercise_answers

Latest revision as of 11:25, 21 May 2010