Excel Plus OpenLink - Honeywell...Controller Installation, Operation, & Maintenance Manual, Release 1.2 August 1995 • Model FVC-2000 Face Velocity Monitor and Controller Instruction

U.S. Registered Trademark

Copyright © 2000 Honeywell Inc. • All rights Reserved

74-3397

Excel Plus OpenLink

FOR TEK-AIR(S1032)

APPLICATION GUIDE

Software License Advisory This document supports software that is proprietary to Honeywell Inc. and/or tothird party software vendors. Before software delivery, the end user mustexecute a software license agreement that governs software use. Softwarelicense agreement provisions include limiting use of the software to equipmentfurnished, limiting copying, preserving confidentiality and prohibiting transfer to athird party. Disclosure, use or reproduction beyond that permitted in the licenseagreement is prohibited.

74-3397 2

Table of Contents

1. INTRODUCTION ...................................................................................................................................... 3

1.1 PRODUCT OVERVIEW ..................................................................................................................... 31.2 USE OF THIS MANUAL ..................................................................................................................... 31.3 APPLICABLE LITERATURE .............................................................................................................. 41.4 TERMS AND ABBREVIATIONS......................................................................................................... 5

2. SYSTEM ARCHITECTURE...................................................................................................................... 5

3. INTERFACE FUNCTIONALITY ............................................................................................................... 7

3.1 SYSTEM OPERATION....................................................................................................................... 73.2 FAILURE/ERROR MODES .............................................................................................................. 10

4. APPLICATIONS...................................................................................................................................... 10

4.1 TYPICAL APPLICATIONS................................................................................................................ 114.2 CUSTOM APPLICATIONS............................................................................................................... 11

5. SYSTEM PLANNING ............................................................................................................................. 11

5.1 CNI MEMORY SIZING ..................................................................................................................... 125.2 PHYSICAL BUS LIMITATIONS........................................................................................................ 125.3 DEVICE RESPONSE TIME.............................................................................................................. 13

6. SYSTEM PROCUREMENT.................................................................................................................... 13

6.1 THIRD PARTY SUPPLIED COMPONENTS .................................................................................... 136.2 SOFTWARE COMPONENTS .......................................................................................................... 136.3 DOCUMENTATION/MANUALS ....................................................................................................... 13

7. INSTALLATION & SYSTEM CONFIGURATION................................................................................... 14

7.1 COMPUTER AIDED ENGINEERING (CAE) .................................................................................... 147.2 PRODUCT INSTALLATION ............................................................................................................. 217.3 INSTALLATION CHECKLIST.......................................................................................................... 217.4 STARTUP PROCEDURE................................................................................................................ 227.5 DIAGNOSTIC & TROUBLESHOOTING ......................................................................................... 23

8. TECHNICAL TRAINING REQUIREMENTS........................................................................................... 24

9. REGULATORY AGENCY CERTIFICATION.......................................................................................... 25

10. APPENDIX A - TEK-AIR DELTANET POINT DEFINITION................................................................. 25

A1 - TEK-TRAK II CONTROLLER POINT LIST..................................................................................... 25A2 - FVC-2000 CONTROLLER POINT LIST........................................................................................... 30A3 - FVC-2000 PLUS CONTROLLER POINT LIST ................................................................................ 31A4 - ISO-TEK CONTROLLER POINT LIST ........................................................................................... 32

11. APPENDIX B - CNI BOARD DIAGRAM.............................................................................................. 34

12. APPENDIX C - RS232/RS485 CONVERTER ...................................................................................... 36

13. APPENDIX D - RS485 HALF DUPLEX NETWORK ............................................................................ 37

3 74-3397

1. INTRODUCTION

1.1 PRODUCT OVERVIEW

The Excel Plus OpenLink Tek-Air Interface (S1032) product provides an interface toboth the Tek-Air TEK-TRAK IItm controllers and the FVC 2000, FVC 2000 Plus, andISO-TEK controllers. The interface to the TEK-TRAK II controllers will beaccomplished by interfacing through a FVCNet GATEWAY to the TEK-TRAK IIcontrollers via the RS485 connection of the CNI board. FVC 2000 fume hoodcontrollers may be attached to the B port of the TEK-TRAK II controller. There is alsoa direct link available for the FVC 2000, FVC 2000 Plus and ISO-TEK controllers.This will be accomplished by connecting these devices directly to the Vendor Bus.NOTE: you may NOT mix TEK-TRAK II controllers with any other type of Tek-Aircontrollers on the Vendor Bus.

The datafile for this interface will be created via CAE and downloaded to the CNIboard. Software residing in EPROM on this board will utilize this datafile to determinewhat controllers and points will be scanned and the R7044 will be updated as Tek-Aircontroller point values change.

The points that will be included in this interface from the Tek-Air system is listed inAppendix A of this document. The interface will allow operators to command points (if the Tek-Air system allows ) and will send those commands out to the Tek-Aircontrollers.

Only the configurations listed in this document will be supported.

It should be noted that it is not the intent of this interface for this project to update thetime on the third party bus or to allow global point update to that bus. Nor will thisinterface provide any programming or storage of programs written in any of the Tek-Air controllers.

1.2 USE OF THIS MANUAL

This OpenLink Tek-Air Interface Application Guide is to be used as a referencemanual in laying out the hardware and software for a particular job site that interfacesto Tek-Air controllers. It requires that the reader have in his possession the manualsand forms listed under APPLICABLE LITERATURE. These manuals and forms arerequired in order to properly install and operate the interface. This guide is acombination document that contains both Application Guide and the Installation andCheckout & Test documentation. This will be the sole reference document providedfor this interface.

74-3397 4

1.3 APPLICABLE LITERATURE

The following is a list of potentially useful manuals and documents. Some of thesedocuments may or may not be required, depending on the specific engineeringrequirements. Obtaining a copy of all of the following documents would greatlysimplify the engineering and future troubleshooting of the installation.

Reference Literature

• DeltaNet Micro Central Excel Plus System Application Guide 74-3878

• DeltaNet HPEP Excel Plus Controller Application Guide 74-2548

• DeltaNet Micro Central/Excel Plus PC CAE Utility Manual 74-3894

• DeltaNet Graphic Central Overview/Operator Manual 74-3541

• DGC Graphics Operator's Manual 74-3536

• DGC System Summary 74-2529

• DeltaNet HPEP D, E Excel Plus Controller C-NAP Network Interface, Installation Instructions 95-7441

• DeltaNet Gateway Check Out and Test 74-2529

• DeltaNet HPEP A-G Excel Plus Controller Maintenance & Repair 85-0160

The following Tek-Air documents contain information about the FVC-2000, FVC-2000Plus, ISO-TEK, TEK-TRAK II controllers and the FVCNet Gateway device.

• ISO-TEK Space Pressurization Monitor (Models SPM-5000 / SPM-5100)Controller Installation, Operation, & Maintenance Manual,Release 1.2 August 1995

• Model FVC-2000 Face Velocity Monitor and Controller Instruction Manual,Release 2.0a

• Specification: Fume Hood Controller (FVC 2000 Plus), Revision A.1

• TEK-TRAK II Technical Manual and Programming Guide, Version 0.21,December 1, 1992

• FVCNet GATEWAY, Protocol Converter and Interface Module as Usedwith FVC-2000 Fume hood Controllers, Instruction Manual Release 2.0December 1992

5 74-3397

1.4 TERMS AND ABBREVIATIONS

For readability of this document the following terms are used:

CAE - shall refer to both CAE and Customer Program Pak ( release 4.5 orgreater ) unless specifically excluded.

CNI - C-NAP Network Interface is the board that is installed in the R7044 D, Eor G and will run the subsystem bus for this interface.

Interfaced subsystem/subsystem - shall refer to the Tek-Air controllers thatare connected to the CNI board via the RS485 bus.

R7044 - is also known as the HPEP (High Performance Excel Plus) controller.

SBC-Micro DDC Control System - This is the Tek-Air product literature namefor the TEK-TRAK II controller. Throughout this specification it will be referredto as the TEK-TRAK II controller. All internal engineering documents receivedfrom Tek-Air refer to this unit as the TEK-TRAK II.

Tek-Air controllers - shall refer to the Tek-Air TEK-TRAK II and FVC2000controllers and no other Tek-Air controllers.

Vendor interface - shall refer to the Tek-Air interface attached to the CNIboard.

Vendor Bus - shall refer to the physical Tek-Air interface bus attached to theCNI board.

2. SYSTEM ARCHITECTURE

The Tek-Air interface software resides on the CNI board in a single 512K EPROM. The CNIboard is attached per standard application off the R7044 motherboard.

There are two configurations of the Tek-Air system that is supported by this interface :

The first method consists of connecting the Tek-Air FVCNet Gateway to the RS232side of the RS485/RS232 converter and the CNI board will connect to the RS485 sideof the RS485/RS232 converter. The FVCNet Gateway communicates with a bus ofTEK-TRAK II controllers which in turn communicates with the FVC 2000 controllers.The RS485/RS232 converter is a B & B 485TBLED converter or equivalent. Theconnection between the CNI board and the RS485/RS232 converter is a AK3702Rcable or equivalent. The part number for the cable between the Tek-Air FVCNet

74-3397 6

Gateway and the RS485/RS232 converter is 1402654-002. This is a standardstraight through 25 pin cable. This configuration is shown below.

RS485 Bus to Vendor System

#1 #2 #62

PORT APORT A PORT A

TEK-TRAK

FVC 2000

FVC 2000

FVC 2000

#1

#2

#12

TEK-TRAK

FVC 2000

FVC 2000

FVC 2000

#1

#2

#12

TEK-TRAK

FVC 2000

FVC 2000

FVC 2000

#1

#2

#12

PORT B PORT B PORT B

FVCNETGateway

Bus Repeater

XBSi

Vendor Bus9600 Baud

RS485

R7044

CNI

RS485/RS232

Converter

The second method consists of directly connecting the FVC 2000, FVC 2000 Plus orISO-TEK controllers to the RS485 side of the CNI board. You may not mix these

7 74-3397

controllers and the TEK-TRAK II controllers on the same Vendor bus. Thisconfiguration is shown below :

Vendor Bus9600 Baud

RS485

R7044

CNI

DeltaNet L1 Bus

XBSi

Note: A maximum of 198controllers are allowed perCNI (1-99, 101-199).The TEK-TRAK is NOTallowed in thisconfiguration. (Userepeaters as specified byTek -Air).

FVC 2000Controller Ver. 2.77

FVC 2000 PlusController Ver. A12

ISO-TEKController Ver. D.02

3. INTERFACE FUNCTIONALITY

The OpenLink Tek-Air interface is a communications vehicle which allows for the integrationof Tek-Air controllers to the Excel 5000 system. In general, the interface is "seamless" inthat any interfaced point appears to the Excel 5000 system just like any other "true" systempoint. Specifically any Excel 5000 local or central OI that can access MicroCel points shallbe able to access the OpenLink interface points.

3.1 SYSTEM OPERATION

74-3397 8

The key system functionality includes:

1. Capability to read selected point data ( analog & digital ) at theoperators discretion from any DeltaNet system local or central OI. Referto the appendices for the specific values that may be obtained from theTek-Air controllers listed in Appendix A.

2. Capability to command selected points ( as long as these arecommandable points in the Tek-Air system ) at the operators discretionfrom any DeltaNet system local or central OI as follows:

2.1. on/off for digital points2.2. to a value within valid range for analog points (-9999.9 to 99999.9)

3. Capability for DeltaNet system to annunciate, acknowledge, and archivecritical alarm points from the interfaced subsystem at central OIs.

4. Capability to prioritize alarms relative to other alarms in the DeltaNetsystem .

5. Capability to add/delete/modify points contained in the interfacedsubsystem from CAE. However, it is a requirement that, if any points areprogrammed for a controller, then the first point in the controller must beprogrammed.

6. Capability to include selected subsystem points within the confines ofthe DeltaNet historical storage capabilities ( just as if it were a true ExcelPlus Micro-Cel controller family point ).

7. Capability for points contained within the interfaced subsystem to beaddressed in a manner consistent with other system controllers.

8. The points from the interfaced subsystem can act as initiators for globalcommands in the DeltaNet system. A maximum of 16 R7044 initiatorsfrom the interfaced system is allowed. The ability to be receptors isbeyond the scope of this product. The only way for the vendors systemto obtain information from the DeltaNet system is through a command.The vendors subsystem will not be able to request or obtain DeltaNetpoint information.

9. Capability for any point in the interfaced subsystem to be included onany graphic, contained within any schedule, etc. just as though it were a"true" MicroCel system point.

10. The Tek-Air FVCNet Gateway will connect to the RS232 side of theRS485/RS232 converter and the CNI board will connect to the RS485

9 74-3397

side of the RS485/RS232 converter. The FVC 2000, FVC 2000 Plusand ISO-TEK controllers can be connected directly to the RS485 port ofthe CNI. However, if TEK-TRAK II controllers are connected to theVendor bus, no other controller types may be connected to the Vendorbus.

11. The TEK-TRAK II Controller is a programmable control device thatreceives input signals and performs calculations based upon the inputsignals. It then produces output signals that vary in response tochanges in the input signals in ways that are determined by the controlprogram. The TEK-TRAK II program language is written in terms whichare familiar to control engineers and designers. A knowledge ofprogramming is helpful in programming the TEK-TRAK II. The branch isresponsible for the software programming in the TEK-TRAK II.

12. No command override processing is allowed for the interfacedsubsystem. The Micro-CEL system allowed command overridecapability at the Micro-CEL controller level. Since the Graphic Centralthinks the vendor points are Micro-CELs it will allow command overridecapability. This function is not available for the vendor controllers.

13. No DeltaNet point information will be sent as global data to interfacedsubsystem.

14. The allowable controller addresses shall be 1 to 62 for the TEK-TRAK IIcontrollers and 1-99 & 101-199 for the FVC 2000, FVC 2000 Plus andISO-TEK controllers that are directly connected to the Vendor bus.WARNING : It should be noted that you may require arepeater on the vendor bus for every 31 devices on thebus.

15. DDC programs and TEP's will be able to issue commands to the Tek-Airunits. However, the Tek-Air TEK-TRAK II will process the commands ata rate of 2.5 seconds per command. Allow at least 2.5 seconds forprocessing each command. This includes both types of methods. It isalso required to not issue more than thirty commands in one instance.An example would be to only send thirty commands from any source (i.e. TEP ) and wait for at least 75 seconds before the next thirty are sentto a single bus. For all other devices, allow 1 second per command.

16. There is no global point update to the Tek-Air bus or points on that bus.For example, if the application was to change SetPoint values for aseries of SetPoints, it would need to individually command the SetPointin each controller.

17. The value of clock time will not be updated to the Vendor bus.

74-3397 10

18. There is no internodal point update done by the CNI for the Tek-Airsystem. Hence there is no point sharing for Tek-Air like that done forCNAP.

19. There is no command override processing for the Tek-Air controllers. Becareful not to write an application that relies on override not to cancelthe last command issued. Also, there is no DeltaNet 'FIXED' pointcapability.

3.2 FAILURE/ERROR MODES

The Excel Plus OpenLink product displays error conditions on the CNI 7-segmentdisplay so that field installations may more quickly determine what problem may existin the interface and also so they can determine that the interface is running. Thefollowing conditions will be displayed momentarily on the 7-segment display:

5 - no response from all subsystem controllers.7 - command failed.8 - no response from a single subsystem controller.E - Invalid Group Requested from R7044 controller

The startup conditions of the CNI and what shall be displayed on the 7-segmentdisplay are as follows:

1 - Initializing.2 - Not enough local database RAM.3 - Bad RAM chip.4 - Bad EPROM chip - checksum error.F - Bad CAE Database - check CAE

After a device goes into a no response condition, ( 8 on the 7-segment display ) theTek-Air Interface software will not attempt to communicate with the no responsedevice for up to 5 minutes.

4. APPLICATIONS

The OpenLink interface product uses the CNI board ( R7044 C-NAP Network Interface14506839 kit). This board may be installed in the R7044 D, E, or G controllers.

The points in the Tek-Air system are updated to the R7044 controller in a manner similar tothat of MicroCel points. The points may be manipulated in the R7044 similar to anyMicroCel point with the following exceptions:

11 74-3397

4.1 TYPICAL APPLICATIONS

It is expected that the typical Tek-Air interface application will be to monitor the valuesin the Tek-Air system. The only expected intervention is for an operator to alter acontroller alarm or SetPoint values.

If the installation requires alarms at the DGC from the Tek-Air FVC-2000 controllers,the high and low alarm values must be entered via CAE or through the DGC in theappropriate fields for the appropriate SetPoint of the Tek-Air controller. In this waythe R7044 will process the values returned from the controller and annunciate theproper conditions throughout the DeltaNet system. The DeltaNet system willgenerate alarm conditions on digital points if the digital points are programmed inCAE as alarm points. See Section 7.1 Computer Aided Engineering for information onhow to program digital alarm points.

The TEK-TRAK II requires specific application software to read and write FVC-2000points. The branch must coordinate the CAE database and the TEK-TRAK IIprogramming.

4.2 CUSTOM APPLICATIONS

Custom application involve using the controller pressure values as input to an airhandler which services the particular area. These would need to be written in DDC ona as needed basis. Remember that the Tek-Air controller points will look like pseudopoints in the R7044 controller.

5. SYSTEM PLANNING

In order to effectively plan the layout or program a database for the Tek-Air interfacedsystem, A general understanding is needed as to how points and devices are mappedbetween the Tek-Air system and the DeltaNet system. First let us review the DeltaNet pointand device/subdevice method and limitations.

DeltaNet Point Capabilities

The DeltaNet system supports a maximum of 5000 points in a single CNI board as long assufficient RAM is installed on that board. There is no limit as to the number of analog ordigital points other than the maximum point count. The DeltaNet system allows for up to198 subdevices through a CNI board. The DeltaNet point format ( cc.bbb.dd.ss.ppp )allows for an entry between 1 to 99 for the subdevice field ( ss ).

Examples of subdevice addresses are:

74-3397 12

DeltaNet addressGG.BBB.DD.SS.PPP

Tek-Aircontrolleraddress

Tek-Airpoint in

controller05.001.30.05008 05 00805.001.30.06014 06 01405.001.30.06114 106 01405.001.30.24012 24 012

Where 05.001.30 is the address of the R7044 controller containing the OpenLink Tek-AirInterface.

Point Mapping from Tek-Air to DeltaNet

Each TEK-TRAK II controller maps to one Excel Plus subdevice, controller address,cc.bbb.dd.ss. Each TEK-TRAK II controller has a specific point layout which is listed in theAppendix A at the end of this document. The first point must be entered in CAE for eachcontroller for the system to function properly. The entry of all other points is optional.

5.1 CNI MEMORY SIZING

Each TEK-TRAK II controller requires 8 bytes of RAM for each point. A maximumsystem could have 62 groups and 187 points per group. ( 62 X 8 X 187 = 92,752 )Thus using 96K bytes of RAM on the CNI board. The board is shipped with 16,384bytes of RAM for point datafile. See diagram in Appendix C for chip locations on theCNI board or refer to 95-7441 or 85-0160.

In addition, creating large numbers of subdevice points in CAE does affect thegenerated EPROM size for the R7044 controller containing the CNI board. Refer toHPEP & MicroCel CAE literature for sizing guidelines and any additional installationrequirements for CAE generated EPROMS.

5.2 PHYSICAL BUS LIMITATIONS

The Tek-Air FVCNet Gateway will connect to the RS232 side of the RS485/RS232converter and the CNI board will connect to the RS485 side of the RS485/RS232converter. The Tek-Air FVCNet Gateway will support at most 62 TEK-TRAK IIcontrollers and each TEK-TRAK II controller can support at most 12 FVC-2000controllers. The CNI board will support one Tek-Air FVCNet Gateway. The locationof the FVCNet Gateway must be within 50 feet of the RS232/RS485 converter. TheR7044/CNI may be up to 4,000 feet from the RS232/RS485 converter. Refer toappendix C of this document for RS232 installation details and appendix D for RS485

13 74-3397

installation details. A repeater may be required for every 32 Tek-Air controllers on theVendor bus.

The RS232 interface is referenced in appendix C. This interface is mounted on apiece of metal that is 4 1/2" by 7 1/2". This allows the interface to be mounted in theR7044 cabinet or remotely mounted by the vendors equipment.

The cable for the RS485 will be the same as DeltaNet MicroCel Controller. Refer toDeltaNet MicroCel Controller Application Guide ( 77-0156). The wire recommendedis AK3702R or AK3744. The MicroCel Application Guide has a discussion section onhow the bus should be implemented.

5.3 DEVICE RESPONSE TIME

The Tek-Air TEK-TRAK II controller has the following general response time in orderto scan all possible controllers and points:

2.5 seconds per TEK-TRAK II controller with a maximum of 62 TEK-TRAK IIcontrollers per subsystem yields a 155.0 second scan time for one completescan of all possible TEK-TRAK II controllers.

The Tek-Air controllers directly connected to the Vendor bus has the following generalresponse time in order to scan a single controllers for all possible points:

0.3 seconds per FVC 2000 controller .0.6 seconds per FVC 2000 Plus controller .1.5 seconds per ISO-TEK controller .

6. SYSTEM PROCUREMENT

6.1 THIRD PARTY SUPPLIED COMPONENTS

• Obtain any Tek-Air components directly from that vendor.

• Obtain software support for the TEK-TRAK II directly from Tek-Air.

6.2 SOFTWARE COMPONENTS

• 27c512 EPROM containing the OpenLink Tek-Air controller Interface software(14006081-924820) is available from Honeywell in Arlington Hts. as part numberS1032.

6.3 DOCUMENTATION/MANUALS

74-3397 14

A list of applicable documents are detailed in Section 1.3, APPLICABLELITERATURE, of this document.

It is expected that the branch will maintain any forms or other documents relating tothe installation of the specific system.

No custom data sheets or forms are supplied for datafile programming of the Tek-Airinterface

7. INSTALLATION & SYSTEM CONFIGURATION

7.1 COMPUTER AIDED ENGINEERING (CAE)

The OpenLink Tek-Air Interface requires that the first point must be entered in CAEfor each controller. The entry of all other points is optional. CAE will automaticallybring up the MicroCel templates when programming an automation point in asubdevice. The instructions that follow will relate to those MicroCel point templates.

The first step is to decide which R7044 controller will contain the CNI board. Use thatR7044 device gateway, bus and device address when entering the Tek-Air controllerdatafile in CAE. Program the proc record for that R7044 in CAE first beforeproceeding to programming of the Tek-Air subdevices.

Define the subdevice address of the Tek-Air controller

Each TEK-TRAK II controller is addressed as a subdevice to the R7044 controllersimilar to MicroCels. A maximum of 62 TEK-TRAK II controllers may reside on thebus.

Tek-Air controller point programming

The specific parameters and point numbers for each controller is listed in theappendices of this document. It must be followed exactly for the system to workproperly.

To begin programming the Tek-Air points, the point type must be selected for thepoint to be programmed. This is the DI, DO, AI, AO listed for that point. Do not usethe dev (non standard point device) programming - use pnt. Select the appropriateCAE menu and proceed.

The first field that must be entered is the cnapnode field. This entry will contain theactual Tek-Air controller address plus fifty ( 50 ).

15 74-3397

The next field is cnapnt. Enter the CNAP POINT NUMBER from appendix A.

The screens for analog and digital points are different. Specific entries for these pointtypes are given in the corresponding sections that follow. Entries that are at the optionof the user such as descriptor will not be discussed and may be entered withwhatever value(s) are appropriate for the system being installed.

Digital Input Point DI (No Alarm Processing)

Each digital input point must have the certain fields programmed in the followingmanner:

type point type - enter regular.

dnam device name - Prohibited for CNI OpenLink points.

term1-3 physical terminal for point - Prohibited for CNI OpenLink points.

mtrxbrd matrix board number - Prohibited for CNI OpenLink points.

mtrxm terminal on matrix board - Prohibited for CNI OpenLink points.

spare spare record - enter n.

debounce debounce time - Prohibited for CNI OpenLink points.

shorg shared origin - Prohibited for CNI OpenLink points.

use point function - enter misc.

fbcor feedback correlation - Prohibited for CNI OpenLink points.

euk engineering unit - enter the unit listed in the controller point tablefrom the appendix. Be very careful not to enter a three positionunit as the point processing will be incorrect when the system isrunning.

cnapeuk cnap eng unit - enter 1.

apt alarm point - enter y or n as required. A no in this field will stopalarm messages on the central indicating no graphic assigned tothose points not used on a graphic.

74-3397 16

almst/almpr/almcl/urgent/alm/lkpnt/lkst/lkdly - various alarm fields that areassigned values as appropriate for the application.

runtp run time for point - if required enter cnt.

rtchk/maxrt/run run time parameters if runtp was set - enter as appropriatefor application.

org global origin - Prohibited for CNI OpenLink points.

scan fast/slow scan - Prohibited for CNI OpenLink points.

segid seg index - enter as appropriate.

des point descriptor - enter as appropriate.

pd point description - enter as appropriate.

Digital Input Point DI (With Alarm Processing)

Each digital input point must have the certain fields programmed in the followingmanner:




mtrxbrd matrix board number - Prohibited for CNI OpenLink points.

mtrxm terminal on matrix board - Prohibited for CNI OpenLink points.


debounce debounce time - Prohibited for CNI OpenLink points.




17 74-3397

euk engineering unit - enter the unit listed in the controller point tablefor the appendix. Be very careful not to enter a three position unitas the point processing will be incorrect when the system isrunning.


apt alarm point - enter y

almst Engineering unit state for alarm enter on

almpr Alarm priority enter 1

almcl Alarm classification enter 1

urgent enter blank

alm Alarm descriptor number enter 1

lkpnt Lockout point address enter blank

lkst Lockout state enter blank

lkdly Lockout delay








Digital Output Point DO

Each digital output point must have the certain fields programmed in the followingmanner:

74-3397 18




quasi quasi digital - enter n.




euk engineering unit - enter the unit listed in the controller point tablefor the appendix. Be very careful not to enter a three position unitas the point processing will be incorrect when the system isrunning.


fbk feedback point address - Prohibited for CNI OpenLink points.

rspt fail to respond - Prohibited for CNI OpenLink points.

almst/almpr/almcl/urgent/alm/ - various alarm fields that are not allowed forCNI OpenLink points

mnof/mnon/mxof/cmdly/dftsu/ - various fields that are not allowed for CNIOpenLink points



kwhi/kwlo kilowatt rating - Prohibited for CNI OpenLink points.




19 74-3397


Analog Input Point AI

Each analog input point must have the certain fields programmed in the followingmanner:



term1 physical terminal for point - Prohibited for CNI OpenLink points.



use point function - enter misc or appropriate value from mnemonictable.

euk engineering unit - enter the unit listed in the controller point tablefor the appendix.

decpl number of decimal places - use 2 unless job requires displayoutput in specific format.

almck alarm point flag - enter y or n as required. If point is not assignedto a graphic then enter no to stop change of state alarmmessages at the central.

almst/almpr/almcl/urgent/alm/seta/ha1/ha2/la1/la2 - various alarm fields thatare assigned values as appropriate for the application.

dbnd deadband - typically 0 for CNI OpenLink.

cmdh/cmdl command range - enter values from appendix table for the pointand controller type being entered.


rthrs amount of change before value reported - enter as appropriate 0recommended.

lkpnt/lkst/lkdly lockout fields - enter as appropriate.

74-3397 20


unr unreasonableness value - Prohibited for CNI OpenLink points.

pov offset - enter 0.




Analog Output Point AO

Each analog output point must have the certain fields programmed in the followingmanner:



term1 physical terminal for point - Prohibited for CNI OpenLink points.


use point function - enter misc or appropriate value from mnemonictable.

euk engineering unit - enter the unit listed in the controller point tablefor the appendix.

decpl number of decimal places - use 2 unless job requires displayoutput in specific format.

cmdh/cmdl command range - enter values from appendix table for the pointand controller type being entered.


fbk feedback point address - Do not enter a value for this field.

dftcu default actuator value - Prohibited for CNI OpenLink points.


21 74-3397




After programming points for all Tek-Air controllers

At this point it should be possible to validate the CAE and generate the database.Remember to make a hard copy ( printout ) of the subdevice points. It may be usefulwhen debugging at the site.

7.2 PRODUCT INSTALLATION

Install and check out the Tek-Air controllers per Tek-Air guidelines before attachingthe bus to the CNI.

After installing the R7044 controller and CNI per standard product literature. Thespecial EPROM is inserted in the CNI existing EPROM socket replacing the standardsupplied chip. If the TEK-TRAK II controllers are used, the Tek-Air FVCNet Gatewaywill connect to the RS232 side of the RS485/RS232 converter and the CNI board willconnect to the RS485 side of the RS485/RS232 converter. Otherwise, the Tek-Aircontrollers will connect directly to the Vendor bus. The datafile created in CAE forthis R7044 will be downloaded to the CNI at power-up.

7.3 INSTALLATION CHECKLIST

The following checklist should be followed to insure proper installation and operationof the Honeywell to Tek-Air interface. Please read all steps first before startingsystem planning or installation.

1. Make a copy of all EPROMs provided with this product. Install the copiedEPROMs in the CNI boards as needed. The master EPROMS should bekept in the job file at the branch. This will facilitate quicker repair of theCNI should the EPROM fail on the CNI board.

2. Determine what Tek-Air controllers will be on the interfaced bus. Recordthe controller type and network address. Verify that no illegal addressesare used. i.e. 1 to 62.

74-3397 22

3. Determine that the HPEP to install the CNI board in is of a revision thatwill accept a CNI board. Refer to the HPEP installation guide for thisinformation.

4. Determine if the overall bus is within physical length limits. The HPEP mayneed to be moved to accommodate these limits.

5. If Honeywell is responsible for the Tek-Air installation, verify the Tek-Aircontroller address before attaching it to the bus.

6. Generate the CAE for the job using the guidelines listed in section 7.1.

7. With power turned off, install the generated CAE EPROMS for the HPEPas described in the 7044 literature for an HPEP with a CNI to MicroCels.

8. After installing the CNI board per standard literature insert the OpenLinkEPROM on the CNI board in socket Z207. Add any additional RAMneeded on the CNI in sockets Z209, Z210 & Z211 in order.

9. Verify that the Tek-Air controllers are operational before they areconnected. If the FVCNet Gateway is used, verify that it is operationalbefore it is connected to the RS232 side of the RS485/RS232 converter.Connect the CNI board to the RS485 side of the RS485/RS232 converter.Verify that polarity is correct ( CNAP+ to converter TD (B) and RD (B),CNAP- to converter TD (A) and RD (A). See Appendix C. Note theRS232/RS485 converter power cube needs 110 volt AC power.For RS485 connections for see Appendix D.

10. Install the software in the TEK-TRAK II controllers, if applicable.

11. See attached "Literature Requirements" for manuals and documents thatmay be necessary. The Tek-Air manuals must be obtained from Tek-Air.The DeltaNet manuals must be obtained from Honeywell Homes andBuildings Control Technical Literature Distribution Center.

12. Bring up the graphics of the Tek-Air points on the DGC and verify that thevalues appear in range.

7.4 STARTUP PROCEDURE

The startup procedure for the OpenLink interface lists the items unique to thisinterface. It is assumed that the DGC has been programmed with graphics tocorrespond to the point datafile as appropriate for the job. In addition, it is assumedthat CAE has been generated and that the specific CAE guidelines for the Tek-Airinterfaced have been followed exactly. Also, the TEK-TRAK II must be loaded with

23 74-3397

appropriate software. Install the CAE files produced for the gateway(s) and 7044(s)as the standard product procedures. The OpenLink interface 7044 and CNI arestarted up as follows :

1. With power turned off, install the generated CAE EPROMS for the HPEPas described in the 7044 literature for an HPEP with a CNI to Micro Cels.

2. After installing the CNI board per standard literature insert the OpenLinkEPROM on the CNI board in socket Z207. Add any additional RAMneeded on the CNI in sockets Z209, Z210 & Z211 in order.

3. Verify that the Tek-Air system is operational by displaying point values onthe appropriate Tek-Air display.

4. The Tek-Air FVCNet Gateway will connect to the RS232 side of theRS485/RS232 converter and the CNI board will connect to the RS485side of the RS485/RS232 converter . See Appendix C.For RS485 connections for see Appendix D.

5. Power up the HPEP. Within a minute the CNI will receive its point datafileand should begin scanning. The led digit should "circle" and the red sendand receive LEDs should be flashing.

6. Verify that the point values are being displayed at the DGC for the Tek-Airsubsystem.

7. Refer to the DIAGNOSTIC & TROUBLESHOOTING section if problemsare encountered.

8. The system should now be operational.

7.5 DIAGNOSTIC & TROUBLESHOOTING

Condition where no values are received from the Tek-Air at the DGC

1. Verify that the Tek-Air system is operational. See attached "LiteratureRequirements" for manuals and documents that may be necessary. TheTek-Air manuals must be obtained from Tek-Air. The DeltaNet manualsmust be obtained from Honeywell Homes and Buildings Control TechnicalLiterature Distribution Center.

2. Verify that the HPEP AC Power is Operational. This is easilyaccomplished by observing if any of the panel lights are on, and if themiddle LED of the 3 green LEDs is flashing ( indicates scan ). In all casesbe sure to conform to the applicable local electrical codes.

74-3397 24

3. Verify that the DeltaNet Graphic Central (DGC) and HPEP containing theCNI board are operational. This may be easily done if some "real" pointoff the HPEP can be displayed on the DGC. If a standard HPEP point willnot display on the DGC refer to "Literature Requirements" for manualscontaining more detail on how to make these operational.

4. Verify that the CNI board is scanning its datafile. This is done byobserving if the red 7-Segment digit is blinking in a circle pattern. If it is, itmeans that CNI has received a datafile and is scanning it. If the digitdisplays a value refer to the error diagnostic section and correct theproblem.

5. Verify that the CNI board is scanning the Tek-Air devices. This is done byobserving if the red send and receive LEDs are blinking on the bottom ofthe CNI board. If both LEDs are blinking it means that responses arebeing received by the CNI from the Tek-Air system. If both lights are notblinking it could indicate that the RS485 bus wires are not connectedproperly, or the polarity of the wires is incorrect. If only the red XMIT LED (leftmost LED of the pair ) is blinking than the RS485 bus or the Tek-Airequipment is not properly connected. Check for proper address setting onthe Tek-Air controllers. Check that bus signal is getting to the controllers.If a bus monitor is used to check communications, remember to set it for 8bit, 1 stop, IGNORE parity. The Tek-Air system uses a 8 bit protocol andthe above settings should produce a readable display.

Condition where some Tek-Air points respond

1. If some of the Tek-Air point values displayed at the DGC give abnormalreadings or generate a "NO RESPONSE", verify that the CAE listing forthese points matches the addressing selected for the Tek-Air controllersand that the point addressing for the DGC graphics is correct.

2. If some of the Tek-Air point values displayed at the DGC give abnormalreadings, verify that the CAE listing for these points matches the typesand is in proper point order as listed in the appendices at the end of thisdocument.

3. If some Tek-Air points still do not give valid values - verify that the DGChas the proper point class assigned for each point.

8. TECHNICAL TRAINING REQUIREMENTS

The TEK-TRAK II II Controller is a programmable control device that receives inputsignals and performs calculations based upon the input signals. It then produces

25 74-3397

output signals that vary in response to changes in the input signals in ways that aredetermined by the control program. The TEK-TRAK II program language is written interms which are familiar to control engineers and designers. A knowledge ofprogramming is helpful in programming the TEK-TRAK II. The branch is responsiblefor the software programming in the TEK-TRAK II.

It is expected that the technician installing or programming this job is trained in CAEand HPEP controllers. If training is deemed necessary for installation and checkoutof the Tek-Air controllers then the branch may need to make arrangements to receivetraining from Tek-Air.

The branch is expected to contact Tek-Air directly when dealing with the Tek-Airportion of the installation unless the issue is related to the Honeywell interface or theability of that interface to read or command Tek-Air controller points.

9. REGULATORY AGENCY CERTIFICATION

The changes made in the software will not void FCC class A on the HPEP panel.

10. APPENDIX A - TEK-AIR DELTANET POINT DEFINITION

This section describes the Tek-Air points that can be accessed by the OpenLinkinterface. The point descriptions as well as the mapping information from the Tek-Aircontrollers to a DeltaNet point number are listed. The first point (DeltaNet Point 001)must be setup for each controller in CAE; all other points are optional.

The information is given in a CAE related format. Point number in controller refers toPPP in the DeltaNet point format GG.BBB.DD.SS.PPP. The subdevice number SSwill map directly to the Tek-Air controller address. All mappings will use theHIGH/LOW subdevice concept for MicroCels so 198 ( 1-99, 101-199) controllerscould be addressable on the Tek-Air bus. However there is a limit of 62 TEK-TRAK IIcontrollers (1-62), all other Tek-Air controllers on the Vendor bus are addressed from1-99, 101-199.

A1 - TEK-TRAK II CONTROLLER POINT LIST

Point

number

in

controller

Description of point Point

Type

CNAP

point

number

EUK Command

Range High

Command Range

Low

1 Analog Output AO 1 ana 4095 02 Analog Output AO 2 ana 4095 03 Analog Output AO 3 ana 4095 0

74-3397 26

4 Analog Output AO 4 ana 4095 05 Analog Output AO 5 ana 4095 06 Analog Output AO 6 ana 4095 07 Analog Output AO 7 ana 4095 08 Analog Output AO 8 ana 4095 09 Analog Input AI 9 ana 4095 010 Analog Input AI 10 ana 4095 011 Analog Input AI 11 ana 4095 012 Analog Input AI 12 ana 4095 013 Analog Input AI 13 ana 4095 014 Analog Input AI 14 ana 4095 015 Analog Input AI 15 ana 4095 016 Analog Input AI 16 ana 4095 017 Digital Input DI 17 fon 1 018 Digital Input DI 18 fon 1 019 Digital Input DI 19 fon 1 020 Digital Input DI 20 fon 1 021 Digital Output DO 21 fon 1 022 Digital Output DO 22 fon 1 023 Digital Output DO 23 fon 1 024 Digital Output DO 24 fon 1 025 Health Output(Cont. Fail) DO 25 fon 1 026 A0 - Variable Parameter AO 26 ana 1000.0 0.027 B0 AO 27 ana 1000.0 0.028 C0 AO 28 ana 1000.0 0.029 D0 AO 29 ana 1000.0 0.030 E0 AO 30 ana 1000.0 0.031 F0 AO 31 ana 1000.0 0.032 G0 AO 32 ana 1000.0 0.033 H0 AO 33 ana 1000.0 0.034 I0 AO 34 ana 1000.0 0.035 J0 AO 35 ana 1000.0 0.036 K0 AO 36 ana 1000.0 0.037 L0 AO 37 ana 1000.0 0.038 M0 AO 38 ana 1000.0 0.039 N0 AO 39 ana 1000.0 0.040 O0 AO 40 ana 1000.0 0.041 P0 AO 41 ana 1000.0 0.042 Q0 AO 47 ana 1000.0 0.043 R0 AO 48 ana 1000.0 0.044 S0 AO 49 ana 1000.0 0.045 T0 AO 50 ana 1000.0 0.046 U0 AO 51 ana 1000.0 0.047 V0 AO 52 ana 1000.0 0.048 W0 AO 53 ana 1000.0 0.049 X0 AO 54 ana 1000.0 0.050 Y0 AO 55 ana 1000.0 0.051 Z0 AO 56 ana 1000.0 0.052 A1 - Variable Parameter AO 57 ana 1000.0 0.053 B1 AO 58 ana 1000.0 0.0

27 74-3397

54 C1 AO 59 ana 1000.0 0.055 D1 AO 60 ana 1000.0 0.056 E1 AO 61 ana 1000.0 0.057 F1 AO 62 ana 1000.0 0.058 G1 AO 63 ana 1000.0 0.059 H1 AO 64 ana 1000.0 0.060 I1 AO 65 ana 1000.0 0.061 J1 AO 66 ana 1000.0 0.062 K1 AO 67 ana 1000.0 0.063 L1 AO 68 ana 1000.0 0.064 M1 AO 69 ana 1000.0 0.065 N1 AO 70 ana 1000.0 0.066 O1 AO 71 ana 1000.0 0.067 P1 AO 72 ana 1000.0 0.068 Q1 AO 73 ana 1000.0 0.069 R1 AO 74 ana 1000.0 0.070 S1 AO 75 ana 1000.0 0.071 T1 AO 76 ana 1000.0 0.072 U1 AO 77 ana 1000.0 0.073 V1 AO 78 ana 1000.0 0.074 W1 AO 79 ana 1000.0 0.075 X1 AO 80 ana 1000.0 0.076 Y1 AO 81 ana 1000.0 0.077 Z1 AO 82 ana 1000.0 0.078 A2 - Variable Parameter AO 83 ana 1000.0 0.079 B2 AO 84 ana 1000.0 0.080 C2 AO 85 ana 1000.0 0.081 D2 AO 86 ana 1000.0 0.082 E2 AO 87 ana 1000.0 0.083 F2 AO 88 ana 1000.0 0.084 G2 AO 89 ana 1000.0 0.085 H2 AO 90 ana 1000.0 0.086 I2 AO 91 ana 1000.0 0.087 J2 AO 92 ana 1000.0 0.088 K2 AO 93 ana 1000.0 0.089 L2 AO 94 ana 1000.0 0.090 M2 AO 95 ana 1000.0 0.091 N2 AO 96 ana 1000.0 0.092 O2 AO 97 ana 1000.0 0.093 P2 AO 98 ana 1000.0 0.094 Q2 AO 99 ana 1000.0 0.0101 R2 AO 1 ana 1000.0 0.0102 S2 AO 2 ana 1000.0 0.0103 T2 AO 3 ana 1000.0 0.0104 U2 AO 4 ana 1000.0 0.0105 V2 AO 5 ana 1000.0 0.0106 W2 AO 6 ana 1000.0 0.0107 X2 AO 7 ana 1000.0 0.0108 Y2 AO 8 ana 1000.0 0.0109 Z2 AO 9 ana 1000.0 0.0

74-3397 28

110 A3 - Variable Parameter AO 10 ana 1000.0 0.0111 B3 AO 11 ana 1000.0 0.0112 C3 AO 12 ana 1000.0 0.0113 D3 AO 13 ana 1000.0 0.0114 E3 AO 14 ana 1000.0 0.0115 F3 AO 15 ana 1000.0 0.0116 G3 AO 16 ana 1000.0 0.0117 H3 AO 17 ana 1000.0 0.0118 I3 AO 18 ana 1000.0 0.0119 J3 AO 19 ana 1000.0 0.0120 K3 AO 20 ana 1000.0 0.0121 L3 AO 21 ana 1000.0 0.0122 M3 AO 22 ana 1000.0 0.0123 N3 AO 23 ana 1000.0 0.0124 O3 AO 24 ana 1000.0 0.0125 P3 AO 25 ana 1000.0 0.0126 Q3 AO 26 ana 1000.0 0.0127 R3 AO 27 ana 1000.0 0.0128 S3 AO 28 ana 1000.0 0.0129 T3 AO 29 ana 1000.0 0.0130 U3 AO 30 ana 1000.0 0.0131 V3 AO 31 ana 1000.0 0.0132 W3 AO 32 ana 1000.0 0.0133 X3 AO 33 ana 1000.0 0.0134 Y3 AO 34 ana 1000.0 0.0135 Z3 AO 35 ana 1000.0 0.0136 A4 - Variable Parameter AO 36 ana 1000.0 0.0137 B4 AO 37 ana 1000.0 0.0138 C4 AO 38 ana 1000.0 0.0139 D4 AO 39 ana 1000.0 0.0140 E4 AO 40 ana 1000.0 0.0141 F4 AO 41 ana 1000.0 0.0142 G4 AO 47 ana 1000.0 0.0143 H4 AO 48 ana 1000.0 0.0144 I4 AO 49 ana 1000.0 0.0145 J4 AO 50 ana 1000.0 0.0146 K4 AO 51 ana 1000.0 0.0147 L4 AO 52 ana 1000.0 0.0148 M4 AO 53 ana 1000.0 0.0149 N4 AO 54 ana 1000.0 0.0150 O4 AO 55 ana 1000.0 0.0151 P4 AO 56 ana 1000.0 0.0152 Q4 AO 57 ana 1000.0 0.0153 R4 AO 58 ana 1000.0 0.0154 S4 AO 59 ana 1000.0 0.0155 T4 AO 60 ana 1000.0 0.0156 U4 AO 61 ana 1000.0 0.0157 V4 AO 62 ana 1000.0 0.0158 W4 AO 63 ana 1000.0 0.0159 X4 AO 64 ana 1000.0 0.0

29 74-3397

160 Y4 AO 65 ana 1000.0 0.0161 Z4 AO 66 ana 1000.0 0.0162 A5 - Variable Parameter AO 67 ana 1000.0 0.0163 B5 AO 68 ana 1000.0 0.0164 C5 AO 69 ana 1000.0 0.0165 D5 AO 70 ana 1000.0 0.0166 E5 AO 71 ana 1000.0 0.0167 F5 AO 72 ana 1000.0 0.0168 G5 AO 73 ana 1000.0 0.0169 H5 AO 74 ana 1000.0 0.0170 I5 AO 75 ana 1000.0 0.0171 J5 AO 76 ana 1000.0 0.0172 K5 AO 77 ana 1000.0 0.0173 L5 AO 78 ana 1000.0 0.0174 M5 AO 79 ana 1000.0 0.0175 N5 AO 80 ana 1000.0 0.0176 O5 AO 81 ana 1000.0 0.0177 P5 AO 82 ana 1000.0 0.0178 Q5 AO 83 ana 1000.0 0.0179 R5 AO 84 ana 1000.0 0.0180 S5 AO 85 ana 1000.0 0.0181 T5 AO 86 ana 1000.0 0.0182 U5 AO 87 ana 1000.0 0.0183 V5 AO 88 ana 1000.0 0.0184 W5 AO 89 ana 1000.0 0.0185 X5 AO 90 ana 1000.0 0.0186 Y5 AO 91 ana 1000.0 0.0187 Z5 AO 92 ana 1000.0 0.0

74-3397 30

A2 - FVC-2000 CONTROLLER POINT LIST

R7044

Point

number

R7044

Point Descriptor

Point

Type

CNAP

point

number

EUK Command

Range High

Command Range

Low

1 Face Velocity AI 2 fpm 1,000 02 Face Velocity SetPoint AO 12 fpm 1,000 03 Controller Output AI 13 pct 100 04 High FV Alarm SetPoint AO 14 fpm 1,000 05 Low FV Alarm SetPoint AO 15 fpm 1,000 06 High FV Alarm DI 16 fon ON (Alarm) OFF (Normal)7 Low FV Alarm DI 17 fon ON (Alarm) OFF (Normal)8 Low Low FV Alarm DI 18 fon ON (Alarm) OFF (Normal)9 Local Emergency Override DI 19 fon ON

(Override)OFF (Normal)

10 Remote Emergency Override DO 20 fon ON(Override)

OFF (Normal)

11 Auxiliary Input AI 21 pct 100 012 Low Low FV Alarm SetPoint AO 22 fpm 1,000 0

31 74-3397

A3 - FVC-2000 PLUS CONTROLLER POINT LIST

R7044

Point

number

R7044

Point Descriptor

Point

Type

CNAP

point

number

EUK Command

Range High

Command

Range Low

1 Face Velocity AI 3 fpm 1000 02 Face Velocity SetPoint AO 12 fpm 1000 03 Controller Output to Valve AI 13 pct 100 04 High FV Alarm SetPoint AO 14 fpm 1000 05 Low FV Alarm SetPoint AO 15 fpm 1000 06 High FV Alarm DI 16 fon ON (Alarm) OFF (Normal)7 Low FV Alarm DI 17 fon ON (Alarm) OFF (Normal)8 Low Low FV Alarm DI 18 fon ON (Alarm) OFF (Normal)9 Local Emergency Override DI 19 fon ON

(Override)OFF (Normal)

10 Remote Emergency Override DO 20 fon ON(Override)

OFF (Normal)

11 Air Flow Volume AI 21 cfm 5000 012 Low Low FV Alarm SetPoint AO 22 cfm 1000 013 Sash Position (%open) AI 23 pct 100 014 Air Flow Volume AI 24 cfm 5000 015 Air Flow Volume SetPoint AO 25 cfm 5000 016 High AF Alarm SetPoint AO 26 cfm 5000 017 Low AF Alarm SetPoint AO 27 cfm 5000 018 High AF Alarm Status DI 28 fon ON (Alarm) OFF (Normal)19 Low AF Alarm Status DI 29 fon ON (Alarm) OFF (Normal)20 Day/Night Reset (Dig) DO 30 fon ON (Night) OFF (Day)21 FV Reset SetPoint AO 31 cfm 1000 022 AF Volume Reset SetPoint AO 32 cfm 5000 0

74-3397 32

A4 - ISO-TEK CONTROLLER POINT LIST

R7044

Point

number

R7044

Point Descriptor

Point

Type

CNAP

point

number

EUK Command

Range High

Command

Range Low

1 Configuration Setup1 AI 4 ind 3411 02 Room Air Pressure / Velocity

(See hundreds and ones digitsof Configuration Setup )

AI 12 fpmfpmfpmfpminwinwinwinw

1000500250100

0.1000.0100

0.005000.00100

-1000-500-250-100

-0.100-0.0100

-0.00500-0.00100

3 High Transfer Alarm SetPoint


AO 13 fpmfpmfpmfpminwinwinwinw

1000500250100

0.1000.0100

0.005000.00100

-1000-500-250-100

-0.100-0.0100

-0.00500-0.00100

4 Low Transfer Alarm SetPoint


AO 14 fpmfpmfpmfpminwinwinwinw

1000500250100

0.1000.0100

0.005000.00100

-1000-500-250-100

-0.100-0.0100

-0.00500-0.00100

5 High Transfer Alarm DI 15 fon ON (Alarm) OFF(Normal)

6 Low Transfer Alarm DI 16 fon ON (Alarm) OFF(Normal)

7 System Condition (Bit Map)2 AI 17 ind 1111 08 Local Alarm Acknowledge DI 18 fon ON (Not

Acked)OFF (Acked)

9 Remote Alarm Horn Disable DO 19 fon ON (Disable) OFF(Normal)

10 Alarm Time Delay3 AO 20 sec 120 15

( See Notes on next page )

NOTES:

1) The value of the Configuration Setup point is as follows :

33 74-3397

Thousands Digit :3 = Netural, 2 = Negative, 1 = Positive, 0 = Standby

Hundreds Digit :4 = 1000 FPM (.1”Wc), 3 = 500 FPM (.01”Wc),

2 = 250 FPM (.005”Wc), 1 = 100 FPM (.001”Wc)Tens Digit :

1 = Latched, 0 - Not LatchedOnes Digit :

1 = FPM, 0 = “Wc (inw)

2)The value of the System condition is as follows :Thousands Digit = 1 for Checksum ErrorHundreds Digit = 1 for Display CommunicationsTens Digit = 1 for Hardware MalfunctionOnes Digit = 1 for Invalid Alarm LimitsValue of Zero (0) indicates no errors or OK.

3) Allowable command values for Alarm Time Delay are 120, 60, 30 and 15 only.

74-3397 34

11. APPENDIX B - CNI BOARD DIAGRAM

J17

Z511 Z512

Z513 Z514

JB402

JB401

S301

Z207

Z208

Z209

Z210

Z211

TB1

J3

J4

CR201

OPTIONAL R7044D-GDATA FILE EPROM EXPANSION

OPTIONAL R7044D-GWORKING RAM EXPANSION

OS EPROM

LOCAL DATABASE RAM

OPTIONAL ADDITIONALLOCAL DATABASE RAM}

C-NAP +C-NAP -

7-SEGMENT DISPLAY

POWER LED

J16

S501

RECEIVE LED

TRANSMIT LED

R7044 Memory Density Selections: S501 Switch (CNI board)

35 74-3397

R7044ParomReq'd

R7044ParamReq'd

Z205 & Z206(R7044 board)

Z511 & Z512(CNI board)

Z513 & Z514(CNI board)

S501(CNI board)

0 = OFF

0-64 kb 0-64 kb 32 kb each ------------ ------------- 0 0 0 064-128 kb 64-128 kb 64 kb each ------------ 32 kb each 0 0 0 0128-256 kb 128-256 kb 64 kb each 64 kb each 128 kb each 0 1 0 0256-320 kb 256-320 kb 64 kb each 128 kb each 128 kb each 0 1 0 1320-512 kb 320-512 kb 128 kb each 128 kb each 128 kb each 1 1 1 1

CNI System Configure Settings: S301 Switch (CNI board)

s301-1 offs301-2 on selects 9600 bps clock for RS485 ports301-3 offs301-4 offs301-5 offs301-6 on enables upper 750 ohm bus biasing resistors301-7 on enables lower 750 ohm bus biasing resisters301-8 on enables 120 ohm EOLRs301-9 offs301-10 on use HPEP D/E/G serial clock for RS485 port ( required )

Note: The s301-6 through s301-8 switch settings are site specific. Use these instead ofadding bias and termination resistors (R1,R2 and R3) shown on following page

74-3397 36

12. APPENDIX C - RS232/RS485 CONVERTER

CNAP + 1

CNAP - 2

3

4

TD (A)

TD (B)

RD (A)

RD (B)

+12 vdc

GND

PowerSupply

RS485

RS232

TD

RD

CNIInterface Board Terminal

Converter

120 VAC 60 HZ

Black

Blk / white line

B & B 485TBLED

12

3

4

5

7

6

8

20

Shld Grd

Signal Grd

rts

sd

echo

DB25 F Connector

2

3

7

237

DB25 M Connector

DB25 Male Connector

120 ohm

50 Ft MAX.

14006090-263600 Assy Rev A RS-232 to RS-485 Converter

1 2 3 4 5TB1

2 3 7

2 3 7

AK3702R

Tek-TrakFVCNetGateway

37 74-3397

13. APPENDIX D - RS485 HALF DUPLEX NETWORK

+

-

ProTech

#n 120

TERMIINATION

For detailed information concerning groundingconsult EIA-485 and appropriate electrical codes.

BIAS

TERMINATION R304 R303

R302 750 120 750

BIAS

100

R301 C N I

. .

.+

-

ProTech

#3

+

-

ProTech

#2

+

-

ProTech

#1.FVC 2000

FVC 2000Plus

ISO-TEK

Tek-AirController

# n

A = RS485 (+)B = RS485 (-)

A

B

Home and Building Control Home and Building Control Home and Building Control ProductsHoneywell Inc. Honeywell Limited-Honeywell Limitee Honeywell AGHoneywell Plaza 155 Gordon Baker Road Böblinger Straße 17P.O. Box 524 North York Ontario D-71101 SchönaichMinneapolis, MN 55408-0524 M2H 3N7 Phone (49-7031) 637-01

Fax (49-7031) 637-493

Electronic document only74-3397 www.honeywell.com

Documents

Excel Plus OpenLink - Honeywell...Controller Installation, Operation, & Maintenance Manual, Release 1.2 August 1995 • Model FVC-2000 Face Velocity Monitor and Controller Instruction