Unity/NexSys 2.2 Subsystem - .NET Framework

UNITY/NexSys 2.2 Supplement Version 5.8

POWER

TEC DOC # LIT-TD-1029 09/2002

Table of Contents UNITY/NexSys 2.2 Subsystem UNITY 5.8

ii

The documentation contained in this publication is the exclusive property of Johnson Controls, Inc., and its use is restricted to the licensed software with which it is furnished. This publication may not be used for any other purpose without the express written consent of Johnson Controls, Inc. Johnson Controls, Inc., reserves the right to update specifications when appropriate. Information contained in this document is based on specifications believed to be correct at the time of publication.

Echelon ©, Coactive©, Windows NT©, and General Electric© are registered trademarks and service marks of companies other than Johnson Controls, Inc. FSC™, CPL™ and NexSys™ are trademarks of Johnson Controls, Inc.

© 2002 Johnson Controls, Inc. All Rights Reserved

UNITY 5.8 UNITY/NexSys 2.2 Subsystem Table of Contents

iii

Table of Contents

Chapter 1: UNITY/ NexSys Basics ........................................ 5 1 NexSys Hardware (Controller) Overview ................................................................ 6

1.1 Flexible System Controller (FSC) .............................................................................. 6 1.2 Flexible Lighting Controller (FLC) ........................................................................... 6 1.3 Variable Air Volume Controllers (VAV-01 and VAV-02) .................................... 7 1.4 Heat Pump (HPU-01) ................................................................................................. 7 1.5 Packaged Equipment Controller (PEC-01) ............................................................. 7 1.6 Fan Coil Unit (FCU-01) ..............................................................................................7 1.7 Roof Top Unit (RTU-01) ...........................................................................................7

2.0 UNITY/NexSys Subsystem Software Interaction ................................................. 8 2.1 UNITY and the NexSys 2.2 Subsystem ...................................................................8 2.2 NexSys 2.2 Software Architecture ............................................................................. 9

3.0 NexSys Subsystem Point Command ...................................................................... 10 3.1 NexSys Points ........................................................................................................... 10 3.2 Request Point Status ................................................................................................ 10 3.3 Command a Point ..................................................................................................... 12

4.0 Enable/Disable the UNITY/NexSys Subsystem ................................................ 13 4.1 Enable the UNITY/NexSys Subsystem ............................................................... 13 4.2 Disable the UNITY/NexSys Subsystem ............................................................... 14

Chapter 2: Group and Point Programming ...........................17 1 UNITY/NexSys Group Programming ................................................................. 18

1.1 Add a UNITY/NexSys Group ............................................................................... 18 1.2 Map NexSys Points to UNITY/NexSys Points ................................................... 21 1.3 Modify UNITY/NexSys Points ............................................................................. 24 1.4 Delete a Point from a UNITY/NexSys Group ................................................... 25 1.5 Delete a UNITY/NexSys Group ........................................................................... 27 1.6 Print UNITY/NexSys Group Information .......................................................... 28

2 Alarms ........................................................................................................................ 29 2.1 Analog Point Alarms ................................................................................................ 29 2.2 Digital Point Alarms ................................................................................................. 29

NexSys Subsystem Index .......................................................31

Table of Contents UNITY/NexSys 2.2 Subsystem UNITY 5.8

iv

Chapter 1: UNITY/ NexSys Basics

This chapter contains infor• NexSys Hardware Overview • UNITY/NexSys Software Interaction • Subsystem Functions

• Request Point Status • Commanding Points

• Enable/Disable Subsystem

This chapter contains information on UNITY/NexSys: • NexSys Hardware Overview • UNITY/NexSys Software Interaction • Subsystem Functions

• Request Point Status • Commanding Points

• Enable/Disable Subsystem

Chapter Overview

Chapter 1: UNITY/NexSys Basics UNITY/NexSys UNITY 5.8

6

1 NexSys Hardware (Controller) Overview This Section gives a brief introduction to NexSys hardware (controller) devices. Two main types of controllers are discussed:

• Flexible System Controllers (FSC, FLC) • Application Specific Controllers (VAV, HPU, PEC, RTU, FCU) Note: It is assumed that the User is knowledgeable about general building automation

systems, and also has a working knowledge of the NexSys field equipment. For further information on NexSys hardware devices, please consult the NexSys 2.2 User’s Guide.

1.1 Flexible System Controller (FSC) The NexSys Flexible System Controller (FSC) is a controller designed to oversee, communicate, and direct activity between a variety of field devices. The FSC Panel is comprised of a CPU motherboard and from one to eight I/O modules communicating via an SPI bus. The CPU board is an Intel i386 EX based, single-board computer with an integrated LONTALK interface. The CPU board is the decision-making component of the FSC-01. The I/O modules gather data from devices in the field and send the data to the CPU. The FSC-01 makes decisions based on this data, and sends commands back to the field via the I/O modules. The I/O module is a circuit board that gathers information from the field and communicates it to the FSC CPU. No ID processing is done at this level. Input states are passed to the CPU, where the desired calculations are made.

The FSC-01 currently supports the use of an 8 UI (Universal Input) module, a 4 DO (Digital Output)/4 AO (Analog Output) module, and a 4 DO (Digital Output) module. Please see the NexSys FSC Installation Guide for more information on the FSC panel.

1.2 Flexible Lighting Controller (FLC) The NexSys Flexible Lighting Controller (FLC) is a controller designed to oversee, communicate, and direct activity between a variety of field devices. The FLC Panel is comprised of a CPU motherboard and from one to eight I/O modules communicating via an SPI bus. The CPU board is an Intel i386 EX based, single-board computer with an integrated LONTALK interface. The CPU board is the decision-making component of the FLC-01. The I/O modules gather data from devices in the field and send the data to the CPU. The FLC-01 makes decisions based on this data, and sends commands back to the field via the I/O modules. The lighting I/O modules control up to four Lighting relays per module, and accepts either GE® RR7 or GE® RR9 relays. Four additional inputs are available for status feedback, and they are generally used for contact feedback on the RR9s, or as a push button override. A ribbon cable connects up to four lighting I/O modules on each I/O module connector of the CPU board. Ribbon cable also connects the lighting I/O modules together. Since the FLC contains the same CPU board as the FSC, it also can perform basic HVAC control. Lighting modules can be used in conjunction with standard HVAC modules. Please see the NexSys FLC Installation Guide for more information.

UNITY 5.8 UNITY/NexSys Chapter 1: UNITY/NexSys Basics

7

1.3 Variable Air Volume Controllers (VAV-01 and VAV-02) The NexSys VAV-01 and VAV-02 (Variable Air Volume) controllers are LON-MARK certified application specific controllers. The VAVs feature a microprocessor that provides VAV control.

• The VAV-01 controller is used with systems containing remote actuator devices.

• The VAV-02 controller has an integrated actuator for direction connection. Please see the VAV-01/VAV-02 Engineering Guide and the VAV-01/VAV- 02 Installation Guide for more information.

1.4 Heat Pump (HPU-01) The NexSys HPU-01 (Heat Pump Unit) controller is a LONMARK certified application specific controller. The HPU features a microprocessor that provides control to the heat pump. Its primary purpose is to provide control for an individual heat pump. Please see the HPU-01 Engineering Guide and the HPU-01 Installation Guide for more information.

1.5 Packaged Equipment Controller (PEC-01) The NexSys PEC-01 (Packaged Equipment Controller) is a LONMARK certified application specific controller. The PEC features a microprocessor that provides control to the field devices. Features include:

• Discrete or Floating Cooling • Discrete or Floating Heating • Full Floating Economizer • Discharge Air Temperature (DAT) Control • Designed for use with 2- or 4-pipe systems

The PEC-01 is intended for use with non-built up air handlers. Please see the PEC-01 Engineering Guide and the PEC-01 Installation Guide for more information.

1.6 Fan Coil Unit (FCU-01) The NexSys FCU-01 (Fan Coil Unit) controller is a LONMARK certified application specific controller. The FCU features a microprocessor that provides control to the field devices. The FCU is:

• Designed for use with 2- or 4-pipe systems The FCU-01 is intended for use with hydronic units. Please see the FCU-01 Installation Guide for more information.

1.7 Roof Top Unit (RTU-01) The NexSys RTU-01 (Roof Top Unit) controller is a LONMARK certified application specific controller. The RTU features a microprocessor that provides control to the field devices. Features include:

• Discrete or Floating Cooling • Discrete or Floating Heating • Full Floating Economizer • Discharge Air Temperature (DAT) Control • Designed for use with 2- or 4-pipe systems

The RTU-01 is intended for use with non-built up air handlers. Please see the RTU-01 Installation Guide for more information.


8

2.0 UNITY/NexSys Subsystem Software Interaction Three separate PCs are required to run the NexSys subsystem:

• The User Interface (UI) PC (OS/2) runs the UNITY software • The NexSys 2.2 subsystem PC (Windows NT) links NexSys 2.2 to UNITY. • The NexSys 2.2 NWS PC (Windows NT) runs the NexSys 2.2 software.

As noted above, UNITY requires a PC with the OS/2 operating system installed, while both the NexSys Subsystem and NexSys NWS run on a Windows NT platform.

2.1 UNITY and the NexSys 2.2 Subsystem UNITY communicates with the NexSys 2.2 Subsystem over the LAN (Local Area Network) using TCP/IP Protocol (Figure 1-). The NexSys Subsystem serves as the liaison between Unity and NWS (NexSys Workstation). TCP/IP data packages are sent over the LAN from UNITY to the NexSys Subsystem, which in turn routes them to NWS (and vice versa). As shown in Figure 1-2, Unity resides on an OS/2 PC and communicates over the LAN to the NexSys Subsystem Windows NT PC. The communication between Unity, NexSys Subsystem, and NWS flows back and forth as follows:

• All information between Unity and the NexSys Subsystem passes through the UNITY IRM (Information Routing Manager).

• The NexSys Subsystem PC routs the information to LNServer, also using TCP/IP protocol.

• LNServer sends the information to LNS (LONWORKS Network Services) 3.0, located on the NWS PC.

• NexSys then processes the data as described in Section 2.2, NexSys Software Architecture. The information is then sent back to UNITY along the same path.

��

��

��

��

��

��

��

��

��

��

��

��

��

��

Figure 1-1. Communication between UNITY, NexSys Subsystem, and NexSys


9

2.2 NexSys 2.2 Software Architecture The NexSys 2.2 PC allows the User to set up and configure a building control database. NexSys can be divided into three separate components:

• NWS (NexSys Workstation) • LNServer (NexSys LONWORKS Network Server) • LNS (LONWORKS Network Services) 3.0

NexSys communicates with devices in the field (called nodes) over the LONWORKS control network technology (LON). The routing of information (data) is accom-plished in several steps:

1. The NWS is the User Interface. The User can add nodes to the system, configure and edit system parameters, and monitor system activity and alarms.

2. NWS sends the data to LNServer using a TCP/IP connection. LNServer then sends the data to LNS via a COM (Component Object Model) connection.

3. LNS routs the data to appropriate nodes (field devices) using Echelon’s LONTALK protocol.

4. Nodes communicate data to NWS using the reverse order of steps 1- 3.

Figure 1-2 below shows several examples of the NexSys 2.2 Architecture.

��

�� ! � "�!��#��$ %�%&��! �

��'��#(��#)

%�%&��! �

��!)��

��

*��) ��+!�,��-.�

��) ��!)/#.�� -�-

��

%�%&��! ��

��

��

��

��

Figure 1-2. NexSys 2.2 Software Architecture

Once NexSys is installed on the PC, both LNServer and LNS run transparently in the background. For complete information on using NexSys 2.2, please see the NexSys 2.2 User’s Guide.


10

3.0 NexSys Subsystem Point Command This section describes the Point Command function of the UNITY/NexSys subsystem. This function allows the User to:

1. View the Status of a NexSys point. 2. Command the point.

3.1 NexSys Points A Point is a single element of data in the system. Points can be:

• Hardware (a physical point with an actual value) • Software (data bound in by software, often by a CPL program). • Analog or digital • Inputs (network variable inputs, or NVIs) or outputs (network variable

outputs, or NVOs). • Points can be predefined on the device, as for ASCs, or can be set up by the

User, as with FSCs and FLCs.

The NexSys Subsystem points fall into one of four general categories: Analog Inputs (AI) - Analog inputs are sensors that report the value of point. This value can be temperature readings, humidity, etc. Analog Outputs (AO) - Analog outputs are analog controls that adjust the variable position of 0-10VDC devices. Digital Inputs (DI) - Digital inputs are points that sense the condition of input devices with two or more states. Digital Outputs (DO) - Digital outputs are points that control output devices with two or more states. For the UNITY NexSys subsystem, the points are SNVT (Standard Network Variable Type) switch-type devices.

For more information on Points and SNVTs, please see the Operations section of the NexSys 2.2 User’s Guide.

3.2 Request Point Status 1) Select Point from the Commands menu (Figure 1-3).

Figure 1-3. Point Command


11

The Point Command dialog box appears (Figure 1-4).

Figure 1-4. Point Command Dialog Box

2) Enter the point address into the Point field or use the red drop-down arrows (Figure 1-5) to select a point from the drop-down list.

Figure 1-5. Red Arrows to Display Drop-Down List of Points

3) Click . Information about the point is displayed in the Status and Detail sections of the Point Command Dialog Box (Figure 1-6).

Figure 1-6. Point Status and Detail Sections

4) Click to close the Point Command dialog box.


12

3.3 Command a Point 1) Complete Steps 1-3 of Section 3.2, Request Point Status.

The Point Command dialog box (Figure 1-7) appears with updated informa-tion in the Status and Detail sections.

Figure 1-7. Updated Point Command Dialog Box

2) Select the command to be issued. a.) The Commands section of the dialog box (Figure 1-8) displays the

commands available for the selected point.

Note: Commands are point-specific - not all commands are available for all points.

Figure 1-8. Commands Section of Point Command Dialog Box

b.) A “Request Complete” message appears in the bottom right corner of the Point Command dialog box (Figure 1-9) showing that the command request has been completed.

Figure 1-9. Request Complete Message

4) Click to close the dialog box. Note: You can also command a point from a graphic. For more information, please see

Chapter 2 of the User’s Guide to UNITY.


13

4.0 Enable/Disable the UNITY/NexSys Subsystem The NexSys Subsystem default setting is Enabled. The User can select Disable if desired. However, NexSys Subsystem MUST be Enabled to communicate with UNITY.

4.1 Enable the UNITY/NexSys Subsystem 1) Select Enable/Disable from the NexSys menu (Figure 1-10).

Figure 1-10. Enable/Disable Command

The System Command dialog box opens, with the current NexSys status displayed (Figure 1-11).

Figure 1-11. System Command Dialog Box

If NexSys is currently Enabled, click . If NexSys is currently Disabled, proceed with Steps 2 and 3.

2) Select the System Enable radio button and click . The System Command Request Completed message box appears (Figure 1- 12). The UNITY/NexSys subsystem is now Enabled.

Figure 1-12. System Command Message Box.

3) Click to close the message box.


14

4.2 Disable the UNITY/NexSys Subsystem When the UNITY/NexSys subsystem is Disabled, UNITY ignores all NexSys controllers. When the NexSys subsystem is disabled, UNITY will not send any information to the subsystem, and ignores any incoming data.

1) Select Enable/Disable from the NexSys menu (Figure 1-13).

Figure 1-13. Enable/Disable Command The System Command dialog box appears (Figure 1-14).

Figure 1-14. System Command Dialog Box

If NexSys is currently Disabled, click . If NexSys is currently Enabled, proceed with Steps 2 and 3.

2) Select the System Disable radio button and click . The System Command Request Completed message box appears (Figure 1-15). The UNITY/NexSys subsystem is now Disabled.

Figure 1-15 System Command Message Box

3) Click to close the message box.

Note: NexSys Subsystem MUST be Enabled to in order to communicate with UNITY.


15


16

Chapter 2: Group and Point Programming

Chapter Overview This chapter of the UNITY/NexSys Subsystem will tell you: • How to create, edit, print, and delete UNITY/NexSys

groups • How to map NexSys points to UNITY points • Alarm Information

Chapter 2: Group and Point Programming UNITY/NexSys UNITY 5.8

18

1 UNITY/NexSys Group Programming 1.1 Add a UNITY/NexSys Group

NexSys field points must be mapped to a UNITY group point before being controlled by the UNITY/NexSys subsystem. Mapping a field point assigns the field point to a UNITY software point. Once mapped, the NexSys field point status or point command can be requested using the corresponding UNITY point in the UNITY/NexSys subsystem. To add a UNITY/NexSys group, at least one point must be mapped.

1) Select Groups from the Edit menu (Figure 2-1).

Figure 2-1. Groups Command

The Edit Groups dialog box appears (Figure 2-2).

Figure 2-2. Edit Groups Dialog Box

2) Enter the number of the group being added and click . Group numbers are assigned to subsystems during the installation of UNITY. To view your group numbers, select Misc. / System Map from the UNITY Menu Bar (Figure 2-3). The System Map window (Figure 2-4) opens, showing the assigned group numbers for all installed subsystems. Use the scroll bar to view the NexSys group numbers. The Edit NexSys Group dialog box appears (Figure 2-5).

Figure 2-3. System Map Command

UNITY 5.8 UNITY/NexSys Chapter 2: Group and Point Programming

19

Figure 2-4. UNITY System Map Window

Figure 2-5. The Edit NexSys Group Dialog Box

3) Click . The Select NexSys Node dialog box appears (Figure 2-6).

Figure 2-6. Select NexSys Node Dialog Box


20

4) Highlight the node you want to map and click . The Edit NexSys Group dialog box appears (Figure 2-7). The points from the selected NexSys node appear on the right.

Figure 2-7. Edit NexSys Group Dialog Box

5) Select the point number from the UNITY Point list (left window). Then, select a NexSys point (right window) to map to the UNITY point. Click

. Note: Double-clicking on a NexSys point also maps the point to the highlighted UNITY

point. The Point Detail dialog box appears (Figure 2-8).

Figure 2-8. Point Detail Dialog Box

6) Change the descriptor for the point, if necessary. Note: The point descriptor displayed is the one stored on the NexSys server. Changing a

descriptor here changes the descriptor in UNITY only, NOT in NexSys. 7) Select an engineering unit from the Engineering Unit list. 8) Click to close the Point Detail dialog box.

The Edit NexSys Group dialog box reappears with the NexSys point and descriptor displayed in the UNITY Point list. The hardware point number, point type, and node areshown directly below the UNITY Point list (Figure 2-9).


21

Figure 2-9. Edit NexSys Group Dialog Box with NexSys Point Mapped to UNITY

9) Repeat steps 5 - 8 for each point being added to the group. 10) Click to close the NexSys Point Editor dialog box.

The Edit Groups dialog box reappears. 11) Repeat steps 1 - 10 for each group being added.

12) Click to close the Edit Groups dialog box.

1.2 Map NexSys Points to UNITY/NexSys Points Once a group has been added in the UNITY/ NexSys subsystem, NexSys field points can then be mapped to UNITY group points. Mapping a field point assigns the field point to a UNITY software point. Once mapped, a NexSys field point can be controlled by the UNITY/NexSys subsystem using the corresponding UNITY point in the UNITY/NexSys subsystem.





22


2) Enter the number of the group to which the points will be mapped and

click . The Edit NexSys Group dialog box appears (Figure 2-12).


3) Select the point number from the UNITY Point list, and select a NexSys

point to map to the UNITY point and click . Note: Double-clicking on a NexSys point will also map the NexSys point to the highlighted

UNITY point. Depending on the point type, the analog (Figure 2-13) or digital (Figure 2-14) Point Detail dialog box appears .

Figure 2-13. Analog Point Detail Box


23

Figure 2-14. Digital Point Detail Box

4) Change the descriptor for the point, if necessary. Note: The point descriptor displayed is the one stored on the NexSys server. Changing a

descriptor here changes the descriptor in UNITY only, NOT in NexSys. 5) Select an engineering unit from the Engineering Unit list.

6) Click to close the Point Detail dialog box.

The Edit NexSys Group dialog box reappears with the NexSys Point and Descriptor in the UNITY Point list. The Hardware Point number, Point Type, and Node appear at the bottom of the UNITY Point list (Figure 2-15).

Figure 2-15. NexSys Point Mapped to UNITY Point

7) Repeat steps 2 - 6 for each point being added to the group.

8) Click to close the Edit NexSys Group dialog box.



24

1.3 Modify UNITY/NexSys Points Unity/NexSys point configurations can be modified using the Edit NexSys dialog box:





2) Enter the number of the group to which the points that need to be modified are assigned and click .

The Edit NexSys dialog box appears (Figure 2-18).

Figure 2-18. Edit NexSys Dialog Box

3) Select the point number from the UNITY Point list that needs to be modified and click .

Depending on the point type, the analog (Figure 2-19) or digital (Figure 2-20) Point Detail dialog box appears . Note: Double-clicking on a point also opens the Point Detail dialog box.


25

Figure 2-19. Analog Point Detail Box

Figure 2-20. Digital Point Detail Box

4) Change the appropriate information and click . The Point Detail dialog box closes and the NexSys Editor dialog box reappears.

5) Repeat steps 3 - 4 for each point being modified in the group.

6) Click to close the dialog box.


1.4 Delete a Point from a UNITY/NexSys Group 1) Select Groups from the Edit menu (Figure 2-21).



26



2) Enter the number of the group in which the point to be deleted is

assigned and click . The Edit NexSys Group dialog box appears (Figure 2-23).


3) Select the point number from the UNITY Point list that is to be deleted and click .

The point is removed from the UNITY point list and added to the NexSys point list.

4) Repeat steps 2 - 3 until all the desired points have been deleted.

5) Click to close the dialog box.



27

1.5 Delete a UNITY/NexSys Group 1) Select Groups from the Edit menu (Figure 2-24).




2) Enter the number of the group being deleted and click . A warning dialog box appears (Figure 2-26).

Figure 2-26. Warning Dialog Box

3) If the group being deleted is the correct group click . If the

group is not to be deleted, click .



28

1.6 Print UNITY/NexSys Group Information 1) Select Groups from the Edit menu (Figure 2-27).




2) Enter the number of the group being printed and click . The Print Group dialog box appears (Figure 2-29).

Figure 2-29. Select Printer Dialog Box.

3) Select the destination printer. 4) Click the appropriate button for the Group information you want.

For example, if you click a report with the group number, point numbers , point descriptors, point types and the corresponding hardware points prints at the destination printer. If you click a report with the group number, point numbers, message names and alarm types prints at the destination printer. If you click a report with a complete TOD programming list for this group’s points prints at the destination printer.

5) Click to close the Print Groups dialog box.



29

2 Alarms The UNITY/NexSys subsystem is responsible for generating and reporting alarms. This is done by demanding the point statuses for each controller and comparing the point’s current status to its previous status. In the UNITY/ NexSys subsystem, alarms are reported every 30 seconds. Standard UNITY alarm types will be used for the NexSys alarms generated. There are analog and digital point alarms. Point alarms can be used as Events to trigger EIAs from a given point.

2.1 Analog Point Alarms • Normal - Normal alarms occur when an analog point changes from an alarm

state to a normal state. These alarms are generated by a group or point, and signify that an alarm has been reset or an error has been corrected. This is also the normal status of a point not in error.

• High Alarm - High Alarms occur when an analog point’s assigned high limit is exceeded.

• High Limit Warning - High Limit Warning Alarms occur when an analog point’s assigned high limit warning is exceeded.

• Low Alarm - Low Alarms occur when an analog point’s assigned low limit is exceeded.

• Low Limit Warning - Low Limit Warning Alarms occur when an analog point’s assigned low limit warning is exceeded.

• Acknowledged - Acknowledged alarms occur when a UNITY operator acknowledges any of the alarms listed above.

2.2 Digital Point Alarms • Normal - Normal alarms occur when a digital point changes from an alarm

state to a normal state. These alarms are generated by a group or point, and signify that an alarm has been reset an error has been corrected. This is also the normal status of a point not in error.

• Alarm - Alarm alarms occur when a digital point changes from its normal state to alarm state. These alarms are generated by either of two conditions:

• Digital status points when they are not in the correct state. • By commandable digital points when the sensed state does not agree with the commanded state.

• Acknowledged - Acknowledged alarms occur when a UNITY operator acknowledges any of the alarms listed above.

• Command Fail - Command Fail alarms occur when a digital input, assigned as a feedback point, does not match the state of the corresponding digital output.


30

31

UNITY 5.8 UNITY/NexSys Index

NexSys Subsystem Index

A

Acknowledged 29 Add Group 18 Alarm 29 Analog Inputs (AI) 10 Analog Outputs (AO) 10

C

Command a Point 12 Command Fail 29

D

Delete a Group 27 Delete a Point 25 Digital Inputs (DI) 10 Digital Outputs (DO) 10 Disable the Subsystem 14

E

EIAs 29 Enable the Subsystem 13 Enable/Disable Subsystem 13

F

Flexible Lighting Controller 6 Flexible System Controller 6

G

Group Add 18 Delete 27 Print Information 28

H

Heat Pump 7 High Alarm 29 High Limit Warning 29

I IRM 8

L

LAN 8 LON 9 Low Alarm 29 Low Limit Warning 29

M

Map Points 21 Modify Points 24

N

NexSys NWS PC 8 NexSys Points 10 NexSys Software Architecture 9 NexSys Subsystem PC 8 Nodes 9 Normal 29

O

OS/2 8

P

Package Equipment Controller (PEC) 7 Package Equipment Controller(PEC) 7 Point

Delete 25 Point Alarms 29 Points 10

Map 21 Modify 24

Print Group Information 28

R

Request Point Status 10

T

TOD 28

U

UNITY PC 8 UNITY/NexSys Subsystem

Communication 8 Software Interaction 8

V

Variable Air Volume 7 VAV 7

W

Windows NT PC 8

Index UNITY/NexSys UNITY 5.8

32

Unity/NexSys 2.2 Subsystem - .NET Framework

Documents

Transcript of Unity/NexSys 2.2 Subsystem - .NET Framework