|
Size: 851
Comment:
|
Size: 1270
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 8: | Line 8: |
| 1. Save the library file with a sensible name, in the appropriate cds_user_apps/<subsystem>/common directory. | 1. Save the library file with a sensible name, in the appropriate cds_user_apps/<subsystem>/common directory. == Building a library part from an existing model subsystem == 1. Open the model that contains the subsystem that you wish to make in to a library part. 1. == Notes about library parts == * At the moment (2011/06/02) there is a bug such that library parts and the files that they are saved in can not have identical names. This is a bug that will hopefully be fixed soon. * Library parts should not |
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.
Building a library part from an existing model subsystem
- Open the model that contains the subsystem that you wish to make in to a library part.
Notes about library parts
- At the moment (2011/06/02) there is a bug such that library parts and the files that they are saved in can not have identical names. This is a bug that will hopefully be fixed soon.
- Library parts should not