Echelon LonMaker - Manual (Page 127)

LonMaker User’s Guide 111
Subsystem Contents
Copy Select which objects to copy in the subsystem and any nested
subsystems. You have three choices:
• Do not copy. Only the subsystem shape will be copied. None
of the contents of the original subsystem will be copied into the
new subsystem. This is the only option available when you
create a new subsystem by dragging a Subsystem shape from
the LonMaker Basic Shapes stencil to the drawing (all of the
options are available when you create a new subsystem by
copying an existing one).
• Copy only Selected Subsystem. Only the contents of the
original subsystem will be copied to the new subsystem. Nested
subsystems and their contents will not be copied.
• Copy Selected. All contents of the original subsystem,
including nested subsystems and their contents, will be copied
to the new subsystem.
Open as Current
Page Open the new subsystem after it has been created. If this check box is
cleared, the LonMaker tool will create the new subsystem but remain
in the current subsystem. This check box is cleared by default.
Exclude Nested
Subsystems from
Subsystem
Operations Applies subsystem operations to only the devices in the parent
subsystem. This check box is cleared by default, which means that
subsystem operations are applied to devices in the parent subsystem
and all of its nested subsystems.
Description Provides an optional description of the subsystem. This description
has no effect on network operation, but you can use it to provide
additional documentation for as-built reports.
3. If you are creating this subsystem in a network that uses user profiles and passwords, click Next to
set Guest Privileges for this subsystem (see User Profiles in Chapter 3, Getting Started for more
information). Otherwise, click Finish to add the subsystem to your LonMaker drawing.
Creating a Supernode
A supernode is a subsystem with its own network variable interface. Using a supernode allows you to
provide a simple interface to an arbitrarily complex subsystem. For example, a supernode that
contains lighting controls may have a network variable interface that allows the devices contained
within it to be put into emergency override. This allows the integrator to identify easily the critical
interfaces into the subsystem while ignoring those that are typically only used internally by the
subsystem.
Any network variable on any functional block in a subsystem may be exported one or more levels up
the subsystem hierarchy to the subsystem shape and be used as a supernode.
To create a supernode, follow these steps:
1. Create a subsystem, and then create one or more devices and one or more functional blocks in that
subsystem.
2. Go back to the parent subsystem and drag a network variable shape onto the subsystem shape you
just created.
3. A dialog opens in which you select a network variable of the appropriate direction in that
subsystem.