beautypg.com

Echelon SmartServer 2.2 User Manual

Page 490

background image

SmartServer

2.2 User’s Guide

491

functional blocks), verify that the dynamic network variables in the functional block have the same
SNVTs or UNVTs as the network variables on the external device. If the SNVTs or UNVTs are
different, change them so they are compatible.

The following sections describe how to connect network variables in the SmartServer’s functional
blocks to network variables on external devices:

The first section describes how to connect SmartServer functional blocks that only have static
network variables in their stencils. It demonstrates how to do this using the SmartServer’s
Scheduler and Data Logger functional blocks.

The second section describes how to connect SmartServer functional blocks that have dynamic
network variables in their stencils. It demonstrates how to do this using the SmartServer’s Alarm
Generator and Alarm Notifier functional blocks.

Binding SmartServer FBs (with only Static NVs in Stencils)

You can use OpenLNS CT to connect the network variables of external devices to the following
SmartServer functional blocks that only have static network variables in their stencils: the Data
Logger, Scheduler, Type Translator, Virtual Functional Block, and Web Server functional blocks.

To do this, add dynamic network variables to a SmartServer functional block that has the same SNVT
or UNVT as the source or target network variable on the external device. Then create a L

ON

W

ORKS

connection between the dynamic network variables on the SmartServer functional block to the source
or target network variables on the external device. Finally, add the dynamic network variables as input
points in the functional blocks’ corresponding configuration Web pages in the SmartServer Web
interface.

Consider a scenario in which you want to connect a SmartServer Scheduler, a lighting system, and a
SmartServer Data Logger so that the lights are turned on and off at a given time and the state and lux
of the lights are logged.

To create the solution for this scenario, you could follow these steps:

1. In OpenLNS CT, drag the functional blocks for the external devices to the OpenLNS CT drawing,

and drag the SmartServer’s Scheduler and Data Logger functional blocks from the SmartServer
Static Shapes
stencil to the drawing.

2. Because the input network variables on the lights have SNVT_switch types, drag an nvoSwitch

output network variable shape from the LonMaker NV Shapes stencil onto the Scheduler
functional block.

3. Note: When you add a dynamic network variable to a SmartServer functional block, the change to

the OpenLNS network database is automatically propagated to the SmartServer over the
L

ON

W

ORKS

channel. As a result, the functional block and the dynamic network variable are

automatically added to the navigation pane. You do not need to manually synchronize the
SmartServer to the OpenLNS network database in order to display these objects in the navigation
pane.

4. Connect the nvoSwitch output network variable on the Scheduler functional block to the

SNVT_switch input network variables on the lights’ functional blocks.

5. Because the feedback output network variables on the lights have SNVT_switch types, drag an

nviSwitch input network variable shape from the LonMaker NV Shapes stencil onto the Data
Logger functional block and create two nviSwitch input network variables.

6. Connect the feedback output network variables on the lights’ functional blocks to the nviSwitch

input network variables on the Data Logger functional block.