SIT unable to 'look under' simulink library link

[AmitDeshpande]

I have used older versions of SIT. I recently installed LabVIEW 8.2 and SIT 3.0.2. I work with very complex simulink models. As a result all the models I work with have library linked blocks (subsystems) in them. When I tried to use current version (as specified above), I realised that I am unable to browse any deeper than the top level block (which happens to be a library linked subsystem). All I can see in the inputs and the outputs of the block with I got 'mapping' tab of the SIT GUI. My entire model in under this block which consists of various masked subsystems, library linked blocks. I had this problem with a version just before this version (I guess it must be 3.0). I was thinking this would have been addressed in the newer release. Apparently not so. Is this a bug with LabVIEW SIT or a limitation or am I doing anything wrong?
Thanks.

Amit

[RDR]

Are you referring to the blocks in MathWorks® Simulink?

-Bob

Message Edited by B O B on 09-12-2007 04:58 PM

[AmitDeshpande]

Yes. I am refering to Mathworks Simulink blocks. But, the focus is not the blocks but the subsystems.those are masked.
Regards,

Amit

[RDR]

Perhaps I am lost, but how does your question relate to SIT?  It seems like more of a question about operation in MathWorks® Simulink?  Please clarify.

-Bob

[AmitDeshpande]

The reason my question is related to SIT is that once I select the Simulink model and I need to connect the instruments on the VI to certain variables within the model I need to use the mapping tab. The mapping tab within the SIT is supposed to pull the model tree structure. What is happening is that I can make connections to the blocks at the root level of the simulink model and also browse to a subsystem AS LONG AS it is not a library link or IS NOT a masked subsystem. When a subsystem is a library link or masked then SIT does not load the information contained within those blocks. Thus, SIT is not able to pull complete information from the Simulink models.
The earlier versions of SIT were able to do that. I believe that I was able to do so until 2.0.2. I am not absolutely sure about the version number.

Regards,

Amit

[RDR]

Hello Amit,

From the SIT help file:

"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."

-Bob

[AmitDeshpande]

Bob,

  I have read that help from SIT. I have been using simulink for over 6 years now. So, I know that masked subsystems and linked library elements are. What is it that I should be reading about in the Simulink documentation? Because that statement in the help is not really helpful. If you could point me to what am I looking for in the Simulink documentation, then it will be relevant.
  We have a tool that imports simulink model structure and that works fine with all the version of matlab/simulink. As I have been saying 'earlier versions of SIT were able to pull this information from the model'. The newer version cannot.

Regards,

Amit
 

[RDR]

Hello Amit,

I did not mean to be condescending with my previous comment.  Sorry if it came across the wrong way.  What version of MathWorks® Simulink were you using with the older version of SIT when mapping linked libraries worked and what version are you using now?

-Bob

[AmitDeshpande]

Sorry Bob, I believe on the second read, my comment also seem to come the wrong way. When I said I have used Matlab/Simulink for over 6 years, I was citing my experience with those tools. I am a fairly new user of LabView/SIT. So, I understand what are the linked subsystem etc. As far as versions are concerned, Matlab version Release 13 SP1 (6.5.1) seemed to have worked fine. This corresponds to Simulink version 5.1. The SIT version 2.0 (or 2.0.2).
I would like to understand what is the cause of the problem. Also, I was able to find a work around, but that is not a workable solution in our case. The reason is most of our model have a lot of library links. The work around is to disable the library link within the simulink model and then establish the connections between the VI instruments and model blocks at all whichever level. Then restore the simulink model library links. It seems to work fine but is not a viable option.

[RDR]

It is ok.  I talked with R&D about this and the response is you are seeing expected behavior under the newer version of SIT.  We do not intend to have the ability to see the sub-levels of a masked library in later versions of SIT.  We treat these blocks as masked blocks meaning you cannot see the sub-diagram within.

-Bob