Difference between revisions of "Simulink Tester Issues"

From T-VEC Wiki
Jump to: navigation, search
(Test Driver Generation)
(Issues)
Line 80: Line 80:
  
 
There is a work around with the current schemas - all mapping descriptors are passed through a Perl function before going into the target file. The perl script parses in an external file that contains new replacement mapping information. The mapping can be defined with the descriptor or a mapping key. If the perl script finds a match then it uses the replacement from the file.  This function can be extended directly through the Perl script.
 
There is a work around with the current schemas - all mapping descriptors are passed through a Perl function before going into the target file. The perl script parses in an external file that contains new replacement mapping information. The mapping can be defined with the descriptor or a mapping key. If the perl script finds a match then it uses the replacement from the file.  This function can be extended directly through the Perl script.
 +
 +
===Project Differences when Translating with Mappings===
 +
By default the function name option for a subsystem is set to “Auto”. The routine RTW uses to derive these function names is unknown to sl2tvec.  As a result, when translating from just the model file, the translator must guess what the function names are, but when translating with the model and RTW mappings file, the translator can determine from the mappings file what the function names are. In the case of reusable subsystems, the reusable subsystem definitions are only combined if they resolve to the same function name.  Since the sl2tvec translator guesses at these function names, the reusable subsystems may be combined differently if the mappings file in included in translation. The result is that a project translated with mappings may have a different number of reusable subsystems (or different subsystem names) than a project translated without mappings.
 +
 +
===Impact of Out of Date Signals===
 +
The translator uses the signal labels in a model to perform the translation process. Sometimes these labels can get out of date when signals are set to show their propagated names. This happens mainly a signal label is changed from one name to another, or when a library is moved from one location to another where the propagated signal label no longer applies.
 +
When the labels get out of date, the translator cannot properly translate the model and produces error messages such as this:
 +
 +
: Determining signal dimensions..ERROR SL0086: 
 +
: Signal dimensions are not consistent for block "Bus_Selector" in subsystem "example" (block expects an input labeled signal2, but could not find it in the input signal)
 +
: WidthIndex 1, BusLabel signal1, Output signal2
 +
: WidthIndex 2, BusLabel signal3, Output signal2
 +
: ERROR SL0115: signal dimension is invalid for signal "signal2" from block "Bus_Selector" <dimension: 0>
 +
: ..Done.
 +
 +
: Translation Aborted!
 +
 +
To avoid this error message, make sure a model is up to date before exporting it by selecting the Edit | Update Diagram menu item or pressing Ctrl + D.

Revision as of 14:10, 30 April 2008