Labview real-time and simpowersystems toolbx from matlab

Question

Hello,
I have a simulink model built with SimPowerSystems toolbox. I want to run this model on a RT target which is a desktop ETS in this case. I follwoed the instructions on how to create and deploy the DLL. There are two problems I am facing--
1. The host screen grays out even though the mapping is correct. (This is verfied by using a similar working file.)
2. The RT target hangs and then the connection is lost. I don't get any error message and after some time as there is no communication, I get error 66/63 etc network related error.
The questions are:
1. Is SimPowerSystem toolbox supported in SIT? ( I read that the SimMechanics is not supported.)
2. Is there any limitation on how many nodes I can use so that the RT system can run the model without getting hung up.
The versions I'm using are:
LabView 8.2, SIT 3.0.2
Matlab R2006b, SIMULINK 6.5, Real-time workshop 6.5
microsoft visual C/C++ 6.0
Please let me know ASAP if anyone has faced this problem before or if someone can answer my questions.
Thanks,
Gayatri

Answer 1

Signals also can be removed when the code is generated and compiled due to optimizations.  Right clicking on a signal and making it a testpoint forces RTW to include that signal in the compiled code signal list.  The appropriate discussion is posted below.
Models Using Signal Storage Reuse, Block Reduction Optimization, or Virtual Blocks
Mappings might appear invalid if the model uses either Signal Storage Reuse or Block Reduction Optimization. These items are options you can set in the Simulink application software to reduce the memory footprint of the model. Disabling these options for the entire model makes all signals available for probing but increases the memory footprint of the model. You can mark individual signals as test points to maintain a reduced memory footprint while keeping certain signals available for probing. To make this change, load the model in the Simulink application software and perform the following actions:
For The MathWorks, Inc. MATLAB® application software release 13, right-click a signal and select Signal properties from the shortcut menu. Place a checkmark in the SimulinkGlobal(Test Point) checkbox and click the OK button to save changes.
For the MATLAB® application software release 14 and later, right-click a signal and select Signal properties from the shortcut menu. Click the Logging and accessibility tab, place a checkmark in the Test point checkbox, and click the OK button to save changes.
Note  If you previously converted this model to a model DLL, you must convert the model to a model DLL again after marking signals as test points.
Similarly, you might not be able to probe signals from Virtual Blocks such as Mux, Demux, Bus Selector, and so on. Marking signals from these blocks as test points makes the signals available for probing.
Refer to the Simulink documentation for information about Signal Storage Reuse, Block Reduction Optimization, Virtual Blocks, and test points.
Models Using Inline Parameters
You might not be able to manipulate model parameters if that model uses the Inline parameters option in the Simulink application software. This option writes a constant value to each model parameter. You must launch the Simulink application software and disable this option so the Simulation Interface Toolkit can manipulate the model parameters.
Refer to the Simulink documentation for information about inline parameters.
Models Containing Linked or Masked Subsystems
You can create mappings to parameters and signals of masked subsystems. However, if a subsystem is linked, or linked and masked, any mappings to parameters and signals of that subsystem appear invalid. Refer to the Simulink documentation for information about linked and masked subsystems.
Subsystems without Parameters or Signals
If a model contains a subsystem that does not have any parameters or signals, that subsystem appears in the model tree when you create mappings. However, you cannot create mappings to/from that subsystem.
<SCRIPT type=text/javascript>
if (typeof(Print_Link)=="function") {
Print_Link();
</SCRIPT>