|
⇤ ← Revision 1 as of 2011-06-02 18:52:34
Size: 846
Comment:
|
Size: 851
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 2: | Line 2: |
| 1. From within Simulink, select File:New:Library. 1. In the new empty model file, build your model from "approved" CDS parts (CDS_PARTS) or other CDS user library parts. 1. Once you have a model, select the entire model and "create subsystem". The library part should be a single subsystem enclosing your entire model. |
|
| Line 3: | Line 6: |
| * From within Simulink, select File:New:Library. * In the new empty model file, build your model from "approved" CDS parts (CDS_PARTS) or other CDS user library parts. * Once you have a model, select entire model and "create subsystem". The library part should be a single subsystem enclosing your entire model. * Give the inputs and outputs sensible names. * Give the subsystem block a sensible unique name in the library. The name can be changed when the part is included/linked/dragged into another file, but the part name in the library file is how the parser finds the part, so it can't be changed after the fact without modifying all models that link to this part. * Save the library file with a sensible name, in the appropriate cds_user_apps/<subsystem>/common directories. |
1. Give the inputs and outputs sensible names. 1. Give the subsystem block a sensible unique name in the library. The name can be changed when the part is included/linked/dragged into another file, but the part name in the library file is how the parser finds the part, so it can't be changed after the fact without modifying all models that link to this part. 1. Save the library file with a sensible name, in the appropriate cds_user_apps/<subsystem>/common directory. |
Building a library part from scratch
From within Simulink, select File:New:Library.
- In the new empty model file, build your model from "approved" CDS parts (CDS_PARTS) or other CDS user library parts.
- Once you have a model, select the entire model and "create subsystem". The library part should be a single subsystem enclosing your entire model.
- Give the inputs and outputs sensible names.
- Give the subsystem block a sensible unique name in the library. The name can be changed when the part is included/linked/dragged into another file, but the part name in the library file is how the parser finds the part, so it can't be changed after the fact without modifying all models that link to this part.
Save the library file with a sensible name, in the appropriate cds_user_apps/<subsystem>/common directory.
