曝光台 注意防骗
网曝天猫店富美金盛家居专营店坑蒙拐骗欺诈消费者
Please be very careful when editing existing blocks in the FDC libraries: since
they may be called by several other models, it is not recommended to alter their input/
output definitions (e.g. increase the number of outputs), or change the names
of blocks within a library. The latter is important, because library links are defined
7.10. Summary of the model and library structure 113
by reference to the blocknames (changing blocknames in models doesn’t matter, because
in that case only the name of the link placeholders is modified). A save method
to implement big changes is to create a clone of the original block first, by copying
the block and breaking its library link.
7.10 Summary of the model and library structure
Let’s summarize these last two sections before proceeding. All FDC models have a
modular and layered structure, because of the use of subsystems and masked blocks.
A mask interface hides the contents of a subsystem beneath an additional layer that
can provides short block-information, a help-button with a link to extensive blockinformation,
an indication that tells us whether we are dealing with the actual block
or a linked copy, and possibly also one or several parameter fields. It is possible to
zoom in to masked subsystems by using the ‘Look Under Mask’ option in the Edit or
context menus to ‘unmask’ these blocks.
Almost all subsystems from the FDC models have been sorted in libraries. The
link status of masked subsystems is indicated in their mask-dialog window; linked
subsystems which have not been masked are distinguished by a light-blue background
colour. Direct editing of these blocks within the models in which they are
applied is not possible, except when the library link is broken first, which will cause
the editing to be limited to the new, local, copy of the block. Editing blocks within a
library is possible after unlocking the library first.
The easiest way to open the required library is to follow the library link from the
model, but it is also possible to open libraries directly from the command-line. In
addition, all FDC libraries can also be accessed via the main library FDCLIB.
Relevant help information for masked blocks will be shown in a webbrowser or
in theMATLAB help browser if the Help button is clicked in the mask-dialog. Doubleclicking
the title block of a model or subsystem will have the same effect, whether
the subsystem has been masked or not.
7.11 Colour conventions for the FDC models
In general, the blocks in FDC models use a simple black-on-white colour scheme,
but there are some exceptions. In the previous section, we already saw that a lightblue
background colour for subsystem blocks has been used to indicate that those
subsystems are contained in a library. In addition, the following colours have been
used:
black-on-cyan (with shadow border):
used for button-blocks, i.e. blocks that will start a related MATLAB utility when
double-clicked,
black-on-yellow (no shadow border):
used to indicate places where data is sent from the SIMULINK systems to theMATLAB
workspace
black-on-yellow (with shadow border):
used to highlight signal switches that require user-interaction,
114 Chapter 7. Getting started with the FDC toolbox
blue-on-white (no shadow border):
used for title blocks which do not link to additional help-information,
blue-on-white (with shadow border):
used for title blocks that will reveal related help information in the webbrowser
or the MATLAB help browser when double clicked; also used for the Mux blocks
in the first level of the aircraft model, to indicate that double-clicking these blocks
will reveal additional help-information about the muxed signals,
magenta-on-white:
used to highlight the internal feedback-loops of the nonlinear aircraft model,
black-on-green:
used to highlight Scope blocks and other blocks with similar plotting functions.
Additional colour combinations have been used for the autopilot models; these will
be discussed later in chapter 15.
7.12 Some cautions
Although you are encouraged to use, modify, and extend the FDC models and tools
for your own experiments, it is important to be aware of the many interactions between
the various models, libraries, tools, and helpfiles, which may not always be
obvious. As noted before, be especially careful when changing blocknames and/or
editing existing blocks in libraries, to prevent inadvertently breaking library links or
mismatching connections. When in doubt, it is safer to create a clone of the original
block before doing any editing, by copying the block and breaking its library link.
For example, in the case of the system Beaver and its subsystem equivalents,
中国航空网 www.aero.cn
航空翻译 www.aviation.cn
本文链接地址：
FDC 1.4 – A SIMULINK Toolbox for Flight Dynamics and Contro(57)
