Difference between revisions of "SL2TVEC Test Driver Issues"

From T-VEC Wiki
Jump to: navigation, search
Line 20: Line 20:
 
Place this in the Advance Translation Options, as shown in the following image.
 
Place this in the Advance Translation Options, as shown in the following image.
  
[[Image:Advanced_Translation_Options.png|center|Advanced Translation Options]]
+
[[Image:Advanced_Translation_Options.png|Advanced Translation Options]]
 +
 
 +
===Update Model Reference Names and Types===
 +
The typical location where code is generated for a model reference is reflected by the following figure.
 +
 
 +
[[Image:stoplight_sm_example.png|Model Reference Code Generation]]
 +
 
 +
The names extracted from the exported model information does not necessarily correspond with the different the code generation works. There is tool provided with the release called
 +
 
 +
get_rtw_types.bat --- Download it here [http://www.t-vec.com/download/get_rtw_types.bat get_rtw_types.bat]
 +
 
 +
This is a perl program that takes two parameters:
 +
 
 +
*Project Directory
 +
*Subsystem Name
 +
 
 +
It then updates the object mapping associated with that subsystem by looking through the .h file associated with the subsystem. The object mapping provides the name of the code in the user-defined variable called: <simulinkSubsystemName>. It updates two key user defined variable:
 +
 
 +
  <rtDWStruct> - defines the localDW variable relating to state data
 +
  <rtZCEStruct> - defines the localZCE variable relating to triggers

Revision as of 15:29, 24 February 2008