Schematics Platform Modeler

Creating a Schematic Network Object

Given a list of independent objects, this macros shows how to create a Schematic network for each member in the list. The network will include the member itself and all the objects that are connected to it.

This macro opens the CAASCH_Network01.CATProduct document.

Through special naming convention (i.e. the word "network" embedded in the instance name), the macro knows to include the following Schematic component instances in the input list.

1. V-082_network_scale_instance.
2. V_084_network instance (the control valve in the screen shot).

Special environment must be available to successfully run this macro:

• Prerequisites:

1. RADE must be installed.
2. CAASchPlatformModeler.edu must exist in CAADoc folder.

• Setup:

1. Build CAASchAppBase.m and CAASchAppUtilities.m, located in CAASchPlatformModeler.edu (RADE is required).
2. Copy generated DLLs, CAASchAppBase.dll and CAASchAppUtilities.m, respectively, to the run-time environment folder "intel_a\code\bin."
3. Copy CAASCHEDUApp.CATfct, located CAASchPlatformModeler.edu\CNext\resources\graphic, to the run-time environment folder "intel_a\resources\graphic."
4. Copy CAASchPlatformModeler.edu\CNext\code\dictionary\CAASchPlatformModeler.edu.dico to the run-time environment folder "intel_a\code\dictionary."

CAASchNetwork.CATScript is located in the CAAScdSchUseCases module. Execute macro (Windows only).

1. Prolog
2. Create a list of network objects using the SchBaseFactory interface
3. Query the member of the list of network objects

Prolog

The macro first loads CAASCH_Network01.CATProduct.

Next, the macro acquires the schematic root object from the document. The schematic root is the top node of the object instance tree in a schematic document.

Create a list of network objects using the SchBaseFactory interface

The macro calls the GetSchBaseFactory method to get a handle of the SchBaseFactory interface.

This macro provides a private Find2ComponentInst function which searches for 2 component instances in the model based on a specific naming convention. Those instances which have the word "network" as parts of their instance names will be included. For each instance returned by Find2ComponentInst, the graphical image of the instance is also returned. Notice that two global variables: objLCntbl_g and objLGRR_g are used to stored these results in Find2ComponentInst. They are available to the main subroutine to be used in calling the CreateNetwork method.

Query the member of the list of network objects

Each network object in the list contains the following information.

1. The input object itself.
2. A list of Schematic component instances that are directly or indirectly connected to the input object. This list of connected component instances can be retrieved using the ListNetworkObjects method.
3. The listing procedure is recursive, and it will stop when the connected object is a Schematic route. This Schematic route (known as the "extremity") will be stored in a separate list. This list of "extremity" objects can be retrieved using the ListExtremityObjects method.

The macro first find out the number of network objects in the output list. Then, for each member in the output list it does the following.

1. Call the ListNetworkObjects method to get a list of connected Schematic component.
2. Call the ListExtremityObjects method to get a list of extremity objects (the Schematic route objects).
3. For each member in those lists, the macro obtain a Product interface handle to report their instance names.