TAC Xenta Zone System Guidelines
Contents
1. PROJECT TAC Vista TAC Xenta DESCRIPTION LON1 des Main SYSTEM objects for LonWorks and Xenta AUTHOR Simon Template DATUM 1998 04 30 DECL INCL lt system frm gt DATA Name of the current Communication port LTA NAME ADDRESS x i FO KKK RK RK ke ke Communication port for LonWo etwor Ti Works network NAME ADDRESS DESCRIPTIO CATEGORY AUTHORITY LTA PORT TAC DOMAIN ON 1 0000000000 0 onTool Configuration file NDB 3 9 9 XX OR XC OE XO LON_COW IG NAME a DESCRIPTIO CATEGORY AUTHORITY SOURCE_FILE STANDARD STANDARD_FILE SNDB LON_CONFIG CNETWORR NDB file Snfiguration file 0000000000 0 TAC A2. ko ko ko ko DECL INCL lt lonworks frm gt bs LonWorks group X XXd Xd X4 X XX X k X k XX k k k k k I IA I k ROI LONWORKS GROUP NAME ADDRESS DESCRIPTION CATEGORY AUTHORITY Kk K X XX X K K K K k K k K K KKK K KKK K ke K KK KKK K KKK K K ee ee ee ees LONWORKS GROUP NETWORK FLOOR1 NETWORK LWG 01 2 0000000000 0 LonWorks process unit RRR RK KKK KK KKK KKK kc k ck ckckck kk ko LONWORKS UNIT NAME ADDRESS DESCRIPTION CATEGORY AUTHORITY NEURONID SUBNET NODE MODE d KK KK KKK gt KKK KKK KKK KKK KKK KKK KKK KK KKK KK KKK LONWORKS UNITCENETWORK FLOOR1 AUDIT SD NETWORK FLOOR1 LWU_02 Xenta 102 unt 0000000000 0 01002412b400 ae i DESCRIPTION CATEGORY AUTHORITY RCE FILE STANDARD STANDARD FILE ck kk kk kk kk kk CK Nc gt ke kk kk kk ck kk gt ckck ck ck ck ck ck LWU_APP ETWORK FLOORS AUDIT SD XIF a 0000000000 0 Xental02 Logical unit LU NAME ADDRESS DESCRIPTION Dk ck kk kk kk ke ck kk kk ck ck ee ee ee ee ee ck ck ck
3. KK IMPORT HOUSE NETWORK LON1 DES ge I o C 02 ENHEAT VENTMHEAT DES ENHEAT VENTNVENT DES a T o C ca HOUSE HEAT_VENT ZM DES ENZON ENZO ENZO ENZO ENZO ENZO ENZO ENZO ENZO ENZO EGNAUDIT M DES EGNAUDIT S1 DES EGNAUDIT S2 DE EGNCAFETERIA DES EGNCLOAKROOM DI EGNCONFROOM DES EG PENTRY DES EG RECEPTION DES EG OFFICE11 DES EG OFFICE12 DES CY CY OOO OOOO Or 30 SO X 6 lE ee ai crib c ae ut cn ai A 0 0 0 0 0 0 0 0 0 50 6 0 J C HOUSE ZO d EGNOFFICE39 DES You can perform a syntax check by first running the command file with the entry line IMPORT replaced with SYNTAX TAC AB 1998 12 01 0 004 7637 1 GB 5 13 14 TAC Xenta Zone System Guidelines Programming In the Database generator open the command file with File Open house_imp des and run it with the command Tools Run as batch file When this has been done
4. Every Xenta unit has a self adhesive removable label with its Neuron ID Collect these during your inspection tour in the plant and put them in the commissioning protocol or any other suitable document see for example the Appendix ID items for all nodes so that each unit can be easily identified during the configuration of the network and its nodes please refer to the chapter Commissioning the network 6 2 2 0 004 7637 1 GB TAC AB 1998 12 01 TAC Xenta Zone System Guidelines Commissioning the Network 7 Commissioning the Network 7 1 Nodes and Routers Note Check that all network cables have been installed Also verify that the correct type of terminator has been connected to each segment Use MetraVision to install the Xenta units including the I O modules and the Routers Often it is most convenient to concentrate on one section at a time for example a Channel for one floor or similar Every node has to be installed that is identified by its Neuron ID This may be done in two ways Entering the Neuron ID recommended If you have got the Neuron ID for every unit you can enter it directly in the installation menu The input can be done as a normal keyboard entry or with the help of an EAN scanner using code 128 for the Xenta units The Neuron ID is printed on each unit and on a detachable label which can be pasted to the commissioning protocol or any other suitable document Ne
5. 0 004 7576 For a description of the interface between TAC Vista and the network LonTalk Adapter please refer to the corresponding product documents 1 2 2 0 004 7637 1 GB TAC AB 1998 12 01 TAC Xenta Zone System Guidelines Working method 2 Working method Note In this chapter we will present an overview of the normal working method in a project with zone controllers We mainly use the same point by point numbering and adhere where suitable to the description given in the manual TAC Xenta family Engineering guidelines art no 0 004 7511 It is important that you perform all steps and in the correct order as should any part be neglected it will be difficult to catch up with this later during the project In the succeeding chapters we will use a specific example to illustrate the details of the working method According to the guidelines a project may be divided in three parts A Basic project analysis B Programming guidelines C Commissioning 2 1 Basic project analysis 1 2 Main structure Study specifications and other project documents to get a clear picture of what is to be accomplished with the system Network structure Make a rough drawing on what is to be included in the physical network configuration see also the TAC Xenta Network guide art no 0 004 7460 comprising for example e TAC Xenta 300 control of units heating ventilation e TAC Xenta 400 Zone Manage
6. Blank page 8 4 4 0 004 7637 1 GB TAC AB 1998 12 01 TAC Xenta Zone System Guidelines Unit Maintenance 9 Unit Maintenance 9 1 Changing the application program If you want to change the application program of TAC Xenta 300 400 do as follows Ifchanges have been made to the values or parameters these must be uploaded to the TAC Vista data base In this way you will make sure that the contents of the TAC Vista data base and the TAC Xenta unit which may have been affected via an OP will be identical Select the menu Display Status in TAC Vista Move to the current unit in the tree select the unit and click right Select Upload parameters only in the popup menu and perform the upload 2 Start the Data base generator by selecting the menu Tools Data base generator in TAC Vista Then select Data base Export data from data base in the Data base generator To export one MTA file Select the TAC Xenta object by clicking on the Browse button In the Select object dialogue click on the radio button Physical navigation and move downwards in the tree to the required TAC Xenta unit Mark the MTA object and click OK To export several MTA files If you want to export several TAC Xenta application programs select the object type TAC Xenta application program and export them A description file is created and the MTA file s exported from the TAC Vista data base and saved in the directory WRK in the
7. Menta NCT the configuration tool you must check the Pre configured box for every I O module otherwise the NCT will try to assign a new subnet node address to the I O module e All Xenta 100 300 400 units are to be defined in the TAC application domain with the hexadecimal ID value of 11 Subnets are defined in the application domain in MetraVision designated Subnet 1 e All TAC Xenta 300 400 units must also have subnets defined for the zero length default domain in MetraVision called Subnet 2 TAC Xenta 100 as well as all Routers are not to have any subnet address in the zero length domain When you assign the subnets you must remember that there may be several subnet numbers on each side of a Router but that each individual subnet number may only appear once that is on only one side of the Router The Router may be destroyed if the same subnet number appears on both sides of the Router I O modules should be put on the same side of the Router as their Base unit This will limit the amount of traffic over the Router If an I O module still has to be put on the other side of the Router it must be given another subnet number than the base unit 5 6 14 0 004 7637 1 GB TAC AB 1998 12 01 TAC Xenta Zone System Guidelines Programming 5 2 4 Creating Templates in MetraVision Templates for the binding of NVs in MetraVision are a great help when the same type of bindings
8. Otherwise incorrect information may remain in the zero length domain Routers Certain Routers will cause problems if by mistake you should use the same Subnet number on both sides which is not allowed but might occur for example if pre configured Xenta units are connected In order to avoid difficulties you can start by installing all Routers as Repeaters This reconfiguration has to be done before the unit is connected to the network When all units have been configured those Routers which temporarily worked as Repeaters are restored Finish the procedure with a Load to the Router 7 2 4 0 004 7637 1 GB TAC AB 1998 12 01 TAC Xenta Zone System Guidelines Commissioning the Network 7 2 Completing the Description files When all units have been installed you generate in MetraVision a report File Create Report which contains data about all the nodes of the network In the created file only the lines which contain the name of the node the Neuron ID and type of unit are useful Other lines can be ignored and may be deleted One example Nodes Node name Loc Program Type Stat Neuron ID HW Audit_M Floor2 X102V02 STD ONLINE 01 00 21 97 35 00 3150 Subnet TAC_Floor2 Subnet lt none gt Variable Dir Bound nciAppOptions IN N nciCO2PerVolt IN N nciFlowOfstSlave IN N Start TAC Vista open the description files for the Xenta units and enter the items about the Neuron ID without the hyphens
9. input variables via the network are polled at program start but only then Receive heartbeat If this is not received within a preset time nvi will be reset to the LonMarks profile standard value TAC AB 1998 12 01 0 004 7637 1 GB App 1 1 4 TAC Xenta Zone System Guidelines General Zone System Limits For TAC Vista v 3 1 e 30 TAC Xenta Groups with at most 30 units in any Group e At most 400 TAC Xenta base per LonWorks network e At most 50 LonWorks groups per LonWorks network with a maximum of 64 LonWorks units per group e At most 1000 LonWorks units per TAC Vista system At most 16 Operator stations in a TAC Vista network of these at most 6 may communicate with units in the LonWorks network Number of TAC Xenta 100 connected to a TAC Xenta 400 Itis not possible to state an unambiguous figure on how many Xenta 100 that can be connected to a Xenta 400 as the number is so closely related to which SNVT bindings are used and how they are arranged An efficient use will allow perhaps 100 connected units while an inefficient use may limit the number to 13 In the following we will study how the type of binding affects the available address tables of the Xenta units Key figures for SNVT bindings Item TAC Xenta 400 TAC Xenta 101 102 103 Lines in address table 13 15 NV Selector 16384 16384 SNVTS 125 1n 125 out 40 Lines in address table states how many addresses unit or group addre
10. you can check that you have got the correct objects for every unit In TAC Vista go to File Select object select Logical navigation and double click on some unit for example the Zone Manager HOUSE ZM displaying the available objects in the Objects list as shown below Object selection FLOW_AUDITM FLOW_CAFETERIA FLOW_CLOAKROOM FLOW_PENTRY FLOW_RECEPTION OPERATION OPERATION_MODE RV_RECEPTION RV_GONF RV_OFFICE 9 e s Logical object ha ogged 5 14 14 0 004 7637 1 GB TAC AB 1998 12 01 TAC Xenta Zone System Guidelines Installation and Program download 6 Installation and Program download 6 1 Program download to TAC Xenta 300 400 Begin with the TAC Xenta 300 application to get the heat and ventilation going Check all connections for the network it is sufficient at this stage with the connections to any I O modules Connect the installation PC and download the application programs into the respective units via the serial port Use TAC Menta NCT to configure any I O modules to their base units If the network has been connected you must first install the I O units with the binding tool and then download the network information to the base unit with the NCT Remember to check mark the Pre configured box for every I O module as the I O modules already have got their subnet node address from the binding tool see previous chapter Even if t
11. 1VF 101 1VF 101 1VF 101 1VF 101 1VF 101 1VF 101 2VF Router Floor Auditorium M Auditorium S1 Auditorium S2 Office 2 1 Office 2 2 Office 2 3 Office 2 4 Office 2 5 Office 2 6 Master VAV Slave VAV Slave VAV Fancoil Fancoil Fancoil Fancoil Fancoil Fancoil 2 air qual control heating heating heating heating heating heating cooling cooling cooling cooling cooling cooling 102 B 102 B 102 B 101 2VF 101 2VF 101 2VF 101 2VF 101 2 101 2VF Floor Cafeteria Reception Cloakroom Pentry Conference Office 1 1 Office 1 2 Office 1 3 Office 4 VAV VAV VAV VAV room Chilled Chilled Chilled Chilled 1 electric electric electric electric VAV ceiling ceiling ceiling ceiling air heater air heater air heater air heater Outdoor sensor 102 EF 102 EF 102 EF 102 EF 102 B 103 A 103 A 103 A 103 A Conf Tool TAC Vista Base ment TAC Xenta 300 X300 Heating central XHeat v 98 04 30 TAC AB 1998 12 01 0 004 7637 1 GB 3 3 4 TAC Xenta Zone System Guidelines Main structure an example 3 2 Acronyms and IDs SNVT out SNVT in conf parameters Follow the ID structure for the logical unit names that are recommen ded in the Engineering Guidelines It must work both in TAC Vista TAC Xenta OP and when you configure the network As the binding tool MetraVision and the network variables both use the English language we recommend that you use English words or at least avoid special letters like
12. After this we stop TAC Vista in order to use MetraVision to bind the network variables TAC AB 1998 12 01 0 004 7637 1 GB 8 1 4 TAC Xenta Zone System Guidelines Parameters and NVs in TAC Xenta 100 8 2 Binding the Network variables 8 2 1 Binding with Templates In the Programming chapter we created templates for SNVT binding In this section we will perform the bindings using these templates Select Tools NV Template Binder and the required Template File for example s ave tbd and then Connection for example FlowSlave102 In this window we bind an NV from one node to one or several NVs in other nodes By specifying Domain Subnet Channel and or Location we limit the selection of nodes available for the current binding Select the required nodes Source output Nodes and Destination input Nodes slave tbd M Connection FlowSlave102 M Online Source output Nodes Template Le Node Name Domain TAC domain Prog Name lt aLL gt Audit S1 2 Audit 2 Channel Floor2 Le KE Location lt ALL gt Update Node List Destination input Nodes Prog Name Node Name Domain TAC domain X102V02 Audit M lt gt Audit S1 Subnet Audit S2 Channel Floor2 Location lt ALL gt lt Update Node List Hew Template Editor Bind Out of the list we here get nod
13. MetraVision select Tools Generate Binding Spec available from v 4 1 and specify a suitable file 10 Note the Neuron ID of the node and then Uninstall it 11 Import the xif file to MetraVision You do not have to invent a new name of the application or for the xif file If necessary that is if MetraVision complains over the xif file you may first remove the old one with the command File Remove Program Then point out the current xif file and import it once again 12 Install the node using MetraVision You may have to state the Neuron ID of the node Up till now all upload download has been performed via the network but during the installation process some network data will be overwritten which means that we have to restore the information using TAC Menta NCT However this program cannot be run via the network instead we must connect to the serial port 13 Download the network data using TAC Menta NCT 14 If necessary reconnect to the network and correct the affected templates in MetraVision 15 Remake all bindings that affect the current unit by selecting Tools Restore Bindings from Spec indicate current bindings possibly all click OK and wait for the question if you wish to see the logg file Restore Binding Spec From ZM BSP ConfSV_01 OfficeSV 01 ReceptSV 01 SlaveFlow 01 SlaveHeat 01 SpaceTemp 01 o ce Note If you have added removed other nodes it may happen that th
14. TAC Vista data base directory normally C TAC310 DB 3 To edit MTA files you use TAC Menta To edit via TAC Menta Start TAC Menta and open the MTA file s residing in the WRK directory Make any changes of the program and save them Select the menu Options Simulation mode and then Command Generate A new MTA file will be generated Save the file in the TAC Menta and replace the MTA file in the WRK directory with the new file TAC AB 1998 12 01 0 004 7637 1 GB 9 1 2 TAC Xenta Zone System Guidelines Unit Maintenance 4 Return to the Data base generator For each MTA file you now MUST generate a new TAC Xenta description file for the new MTA file Import the description file to the TAC Vista data base At the import of a TAC Xenta description file the following happens The application program MTA must be defined under the selected TAC Xenta base unit for example LON_B1 V_XENTA1 or XNET B2 V XENTAI When the new description file is imported the former physical objects for the application program modules and signals are replaced by the new physical objects You can use the existing logical object or create new ones for the application program modules and signals Logical objects that are not used will remain and must be removed manually via the Select object dialogue In TAC Vista 3 1 TAC Menta 3 1 the NWC file has been replaced by a NDB file that contains the informati
15. ck ck ck ee gt gt ck ck gt gt ck NETWORK FLOOR1 AUDIT S Furthermore you have to specify a number of variables for the controllers and definitions for the graphics The description files are listed in the command file for TAC Vista see below C HOUSE ZONREG AUD_S1 DES TAC AB 1998 12 01 0 004 7637 1 GB 5 11 1 4 TAC Xenta Zone System Guidelines Programming To this you should add the colour graphics for the air handling units standard graphics for the Zone Controllers with all variables public at least to be able to check the current status see example below You may have to split the contents over several graphics Configuration programming picture Daily operation check the transmitted and current values Note It may not be possible to change these variables from here they are updated via the network In the directory C NV TAC310NS INI there are files for the standard graphics x101v01 sgr x102v02 sgr and x103v04 sgr shown below The graphics are opened end edited in the standard graphics editor If you connect these pictures to the corresponding controller objects you will get easy access to all parameters N 0 co 12 13 14 15 16 nciLocation nvoEffectOccup nvoUnitStatus heat output primary heat output secondary cool output econ outout fan o
16. controller is sent to the Zone Manager via SNVT adding the values to give the total air flow for floor 1 and floor 2 The sending of the room temperature The room temperatures is sent to the Zone Manager from the Zone Controllers The Zone Manager input should be of the type no poll this 1s indicated for TAC Xenta 300 400 in TAC Menta the TAC Xenta 100 outputs are fixed as sending TAC AB 1998 12 01 0 004 7637 1 GB 4 1 4 TAC Xenta Zone System Guidelines Zone Functions To secure their function the Send Heartbeat of the Zone Controllers should be set to a value 1 2 minutes different in different units to get an even distribution The set value applies to all nvo output values of the controller An approximate mean value is calculated based on those values that have reached the Zone Manager during the last 20 minutes a period during which each unit should appear at least once Please see the figure at the bottom of the opposite page Also the min max values are based on 20 minutes intervals that is the values are calculated every second but the out values are updated only each 20 minutes 4 2 FBD for the Zone Manager The Function Block Diagrams FBD for the Zone Manager look as follows Get operation signal from air handling unit Set operation mode of zones Operation MET 1 fan on O fan off O OC_OCCUPIED Area is occupied 1 OC UNOCCUPIED Area is unoccupied 2 OC BYPASS Area i
17. d d d Fore the NV names of the network the following standard designations apply nvosignal name nvisignal name ncisignal name 3 4 4 0 004 7637 1 GB TAC AB 1998 12 01 TAC Xenta Zone System Guidelines Zone Functions 4 Zone Functions 4 1 Signals and Points In our example we have chosen the following exchange of signals Running mode The running mode for the ventilation unit is fetched from the TAC Xenta 300 controller that handles the ventilation unit via TACNV from a signal labelled TFO1_D which indicates that the supply air fan has been started From the Xenta 300 a O or 1 is sent to the Zone Manager TAC Xenta 401 depending on if the fan is idle or started The Zone Manager in turn sends if the fan has been started the value 0 to Xenta 100 which corresponds to the value OC OCCUPIED otherwise the value OC UNOCCUPIED is sent This signal is sent via SNVT to all Xenta 100 controllers Outdoor temperature The outdoor temperature sensor is connected to the basement Xenta 300 the value is then sent via TACNV to the Zone Manager and the attic Xenta 300 Setpoints The outdoor temperature value enters the Zone Manager curves one for each Group to produce an outdoor compensated value The values from the curves can then be offset for each Group The setpoints are sent to the different Groups offices conference rooms or reception via SNVT Air flow The current air flow for each VAV
18. for example e Replace the text NETWORK with the name of the current network e With an addition to the template please refer to the adjacent example the units may be collected in LonWorks groups up to 50 groups with at most 64 units in each Save the document as Xenta10x des Use these files and enter what is special for each controller e Replace the text LWU1 with the name of the specific unit Replace the text LU with the name of the logical unit for example HOUSE1 FLOOR2 The edited files are saved with suitable names as des files in the same catalogue as the xif files Below we show a section with the most important changes 5 10 14 0 004 7637 1 GB TAC AB 1998 12 01 TAC Xenta Zone System Guidelines Programming Addition to template current unit Neuron ID The name of the Network Group name Name of the_ FLOOR1 AUDIT S Current logical unit TT ko KKK TAC Vista KK KKK KKK KKK KKK KKK KKK KK KKK KKK KKK PROJECT TAC VISTA 3 1 DESCRIPTION Xenta 102 Audit S1 Date 1998 06 11 occ ck ck ck
19. of district heating a heat exchanger in the basement VSO1 and the ventilation an air handling system in the attic LB01 one TAC Xenta 401 acting as Zone Manager 15 TAC Xenta 101 to control Fan coil heating cooling eight TAC Xenta 102 for VAV control four TAC Xenta 103 to control chilled ceilings These units belong to a LonWorks network which is connected through three Routers The network is configured and supervised by a PC connected via an LTA adapter for example a PCLTA card The following Network Variables NV are exchanged between the Xenta units via the network Running mode control for the Zones Outdoor compensation of the Zone Group setpoints Current air flow from the VAV controllers Slave control of the VAV boxes Outdoor temperature to the ventilation unit and the Zone Manager Roomtemperature of the Zones NV may be of the following types TACNV TAC Network Variable SNVT Standard Network Variable Type according to LoNMARK Please note that the example is presented with precisely these assumptions concerning NVs via the network Other applications may require other NVs other units another configuration etc TAC AB 1998 12 01 0 004 7637 1 GB 3 1 4 TAC Xenta Zone System Guidelines Main structure an example Sending unit TAC Xenta 300 1 Zone Manager TAC Xenta 300 VSOI Zone Manager Zone Manager Zone Manager TAC Xenta 102 Auditorium M A
20. relevant TAC Xenta 100 units and any other LonWorks products Programming Use TAC Menta to build the most complex application program of the plant regarding heat ventilation and the OP configuration Test the program first by simulation in TAC Menta then the OP functions by connection to some unit with a downloaded application program This is listed as step no 8 in the Engineering Guidelines Program and test by simulation the Zone Manager application Use for example MetraVision to configure off line that is before it is connected the complete network e Define Channels including any Backbone Domains and Subnets Put all units with their correct logical unit names IDs on the respective channels Insert the required Routers between the channels Build the templates which later can be used for the binding of the standardised network variables SNVTS 2 2 4 0 004 7637 1 GB TAC AB 1998 12 01 TAC Xenta Zone System Guidelines Working method 8 9 10 Build the TAC Vista functions Prepare the description files for the network and for all units Enterthe preliminary description files into the data base of TAC Vista Create in TAC Vista the graphics reports etc for the application Copy the files to the next application and continue the programming 2 3 Commissioning 11 12 Note The Installation work Check what has been electrically connected and where the
21. some basic knowledge of the products TAC AB 1998 12 01 0 004 7637 1 GB i 2 TAC Xenta Zone System Guidelines Foreword Revisions list Art no Comments Editor Date 0 004 7637 0 First version KW 1998 04 30 0 004 7637 1 Revised according to TAC Vista Menta Xenta 3 1 KW 1998 12 01 ii 2 0 004 7637 1 GB TAC AB 1998 12 01 TAC Xenta Zone System Guidelines Contents TAC Xenta Zone System Guidelines Subject to modification 1998 TAC AB Contents 1 1 1 1 2 13 2 2 1 2 2 2 3 3 3 1 3 2 4 41 4 2 4 3 5 5 1 52 5 2 1 5 2 2 35 2 3 5 2 4 05 6 6 1 6 2 1 1 056 ee 1 1 Scope and 0 1 1 More information cC 1 1 Workme method svi e221 Basic project analysis sscccccsscscscssscssccssscscssscssscesssscsscessccsscsseeseesseesscssecssccsssssssssssessssssscsssesscsseess 2 1 2 2 COonmmssionine dn 2 3 Mam structure an example se dl THE Plant sr ilo 3 1 Acronyms and IDS 00006000 i ei 3 4 7 06 FunctiOns sn dle i 1 Signals and POMS os 4 1 FBD for 2 4 2 The most important 0 0 7 4 4 PrOPFADIIIIBD vn DEL Preparations S 5 1 Ignricinnieee E 5 4 The Application program of TAC Xenta 300 400 5008060 eene 5 4 Configunng the NetWork LL sis ius be Hees ies is i i a i i a A a is V i vdeo 5 4 Configuring the TAC Xenta uni
22. when the window NV Template Editor is reopened please turn over TAC AB 1998 12 01 0 004 7637 1 GB 5 7 14 TAC Xenta Zone System Guidelines Programming Then click on Add New and create the template HeatSlave102 in the same way NV Template Editor SLAVE TBD File Connection Name Add New HeatSlave102 Modify Delete Add To MV Help Connection Attributes nviBoxFlow nvoBoxFlow Service Type App Cnfg 5 2 5 Preliminary Description files for TAC Vista In this section we will show how to draw up the description files for TAC Vista Several of the steps are described in detail in the manual TAC Vista version 3 Communication TAC Xenta Some of the files will at this stage only get preliminary contents as all the addresses or other facts are still not known To save time and work at the final generations we postpone the description files import until the end and then lets one command file house_imp des perform the task see below Connecting the LTA card See the chapter Connecting to the LonWorks network via LonTalk Adapter in the manual above Not handled by the command file Description file for the LTA port and the LonWorks network and the TAC Xenta units and TAC Xenta Groups See the chapter Define the LTA Port and LonWorks network in TAC Vista the section Definition and import via description file in the manual above
23. 1 1 Purpose This manual is designed to show how a zone system can be built with TAC Xenta components in a LonWorks network with software from TAC Menta and TAC Vista using MetraVision as the binding tool We work with a specific example and show how this is implemented from the initial system design concepts via the network configuration to commissioning and certain types of service A basic idea is to use TAC Xenta 401 as a Zone Manager for a number of controllers of the TAC Xenta 100 series and to use Templates in Metra Vision in order to simplify the binding of the variables that are to be exchanged between different units 1 2 Scope and Limits The methods described in this manual are valid for the following products and releases e TAC Xenta 400 3 1 e TAC Xenta 100 v 1 0 e TAC Xenta 300 3 1 e TAC Menta v 3 1 TAC Vista v 3 1 MetraVision v 3 0 or 4 1 required only in chapter 9 when changing the application program if you want to use the Generate Restore Binding Spec utility LonMark certified zone controllers from other vendors 1 3 More information The working method follows the guidelines which are given in the manual e TAC Xenta family v3 Engineering Guidelines art no 0 004 7639 TAC AB 1998 12 01 0 004 7637 1 GB 1 1 2 TAC Xenta Zone System Guidelines Introduction The TAC Xenta 400 controller and the associated I O modules are described in the following documents e T
24. 8 M Main structure 2 1 MetraVision 5 4 N nci 3 4 nciAppOptions 4 4 nciMaxFlow 4 4 nciNomFlow 4 4 network 7 1 Network structure 2 1 Network Variables NV 3 1 NeuronID 6 2 7 1 App 2 1 nodenumber 9 4 Nodes and Routers 7 1 nvi 3 4 nvo 3 4 NVsin TAC Xenta 100 8 1 0 ON OFF 4 4 P Parameter download 8 1 Parameter download TAC Xenta 100 2 4 PCLTA 3 1 5 9 Preparations 2 2 Programdownload 2 3 6 1 Programming 2 2 5 1 5 4 projectanalysis 2 1 project library 5 1 R Repeater 5 5 7 2 restore the addresses 8 3 Router 3 1 5 5 7 2 5 Service pin 7 2 settings 4 4 SNVT 3 1 subnetnumber 5 6 Subnet node addresses 7 3 subscriptions App 1 1 T TAC application domain 5 6 TAC Menta 5 4 TAC Vista v 3 0 App 1 2 TACNV 3 1 Template 5 7 8 2 TP FT 10 5 4 TP XF 1250 5 4 V Working method 2 1 2 Zone functionality 2 2 Zone Functions 4 1 Zone Manager 3 1 4 1 TAC AB 1998 12 01 0 004 7637 1 GB Ind 1 2 TAC Xenta Zone System Guidelines Index Blank page Ind 2 2 0 004 7637 1 GB TAC AB 1998 12 01 TAC Xenta Zone System Guidelines Reply form You can help us make this manual even better Please help us make our documentation as good as possible Use this form to let us know of any errors unclear descriptions or suggested improvements Send the form to Alternatively send an e mail to TAC AB helpdesk tac se Helpdesk Jagershillgatan 18 SE 213 75 MALMO
25. AC Xenta 400 Handbook art no 0 004 7520 e TAC Xenta Network guide art no 0 004 7460 The data sheet for TAC Xenta 400 C 92 05 The data sheet for TAC Xenta 411 412 C 92 10 The data sheet for TAC Xenta 421 422 C 92 15 The data sheet for TAC Xenta 451 452 C 92 20 e ashort installation instruction OFL enclosed with each product The TAC Xenta 100 controllers are described in a number of data sheets and installation instructions and in the manuals for TAC Xenta 101 art no 0 004 7513 TAC Xenta 102 art no 0 004 7516 and TAC Xenta 103 art no 0 004 7526 The TAC Xenta 300 controllers and Operator Panel are described in the following documents e TAC Xenta 300 Handbook art no 0 004 7470 The data sheet for TAC Xenta 300 C 90 05 The data sheet for TAC Xenta OP Operator Panel C 98 05 e ashort installation instruction OFL enclosed with each product TAC Menta is described in e TAC Menta v3 User s manual art no 0 004 7608 TAC Menta v3 Reference manual art no 0 004 7609 TAC Vista and those modules which are treated in this manual are described in the following manuals TAC Vista 3 1 Operator guide art no 0 004 7571 e TAC Vista 3 1 Basic functions art no 0 004 7647 e TAC Vista 3 1 Communication TAC Xenta art no 0 004 7585 e TAC Vista 3 1 Database generator art no 0 004 7578 e TAC Vista 3 1 Colour graphic editor art no
26. B 1998 12 01 0 004 7637 1 GB 5 9 14 TAC Xenta Zone System Guidelines Programming Description files for TAC Xenta 300 3000 400 For each TAC Xenta unit we must create a description file des which we then import into the data base of TAC Vista We assume that we in TAC Menta have created application files mta for all the TAC Xenta 300 and 400 units These are used to generate the corresponding description files des The method is described in the chapter TAC Xenta application program in the manual TAC Vista 3 1 Communication TAC Xenta Note The description files des must reside in the same catalogue as the corresponding application files mta TAC Xenta 300 400 to make the public signals configuration work For the TAC Xenta 3000 units there are complete aut files These may be opened in TAC Menta in simulation mode and then saved as mta If the aut file is opened in editing mode the standard application 3000 will be converted into a custom designed 300 Description files for TAC Xenta 100 For the TAC Xenta 100 units we start with the template files dem that are included with TAC Vista From these we get suitable default values standard texts for alarms etc The template files reside in the TAC Vista catalogue in tmp1 one for each type of controller Xental0x dem Copy the required template files change the general items in the document header and in the relevant text sections
27. Network configuration file objects At the import of the description file for the network LON des a network configuration file object SNDB is connected the contents of which we get from the network configuration file LONI ndb that was created by the configuration tool in TAC Menta As the LonWorks network is defined we may get a few alarms telling us that the Lon Talk Adapter s Subnet Node address has been changed This may occur if we already have run MetraVision and the LTA got a subnet node address at that occasion These alarms can normally be viewed as pure information 5 8 14 0 004 7637 1 GB TAC AB 1998 12 01 TAC Xenta Zone System Guidelines Programming LTA port and LonWorks network Data about our operator station PC name network port PCLTA network name and the name of the network configuration file LONI ndb are edited into the description file LONI des as shown below Objects for the TAC Xenta units and TAC Xenta Groups Besides describing the network for TAC Vista the reference to LONI ndb will also help us get the physical objects for the TAC Xenta 300 400 Groups and units but not for TAC Xenta 100 See also the section Physical and logical structure in the data base of TAC Vista in the chapter mentioned above network port Current PC name Network name Name of the
28. SWEDEN I have found the following errors and or unclear descriptions in the TAC Xenta Zone System Guidelines part number 0 004 7637 1 GB I suggest the following improvements Syro ias ces a i T i a ia i Name Company TAC AB 1998 12 01 TAC Xenta Zone System Guidelines Reply form TAC AB 1998 12 01 tace TAC AB J gershillgatan 18 SE 213 75 MALM SWEDEN 46 40 38 68 50 switchboard
29. TAC Xenta Zone System Guidelines Add individual adjustment R Office SNYT 300 421 451 XVent Dig I O Anlg I O 401 ZM e a EMO RV Conf o 101 1VF 101 1VF 101 1VF 101 1VF 101 1VF 101 1VF 101 1VF 101 1VF 101 2VF Router RV Entre 9 L T5 E o 102 B 102 B 102 B 101 2VF 101 2VF 101 2VF 101 2VF 101 2VF 101 2VF Router default channel Floorl e 4 1 ttrFlofor2 Flobr3 Floor2 Cloak 102 EF 102 B Router X300 XHeat 0 004 7637 1 GB 1998 12 01 tace TAC Xenta Zone System Guidelines Foreword Foreword This manual describes the recommended working procedures when designing a zone system based upon TAC Xenta products version 3 1 by help of TAC Menta for the application programming and with TAC Vista as the supervisory system also both of version 3 1 We use MetraVision as an example on a binding tool but thanks to the open LonWorks technology also other binding tools may be used The manual requires that the user has
30. a 100 models Fetched from the directory TAC310 ini Log file created by TAC Vista data base generator as the file des is imported Contains assorted status messages 5 2 14 0 004 7637 1 GB TAC AB 1998 12 01 TAC Xenta Zone System Guidelines Programming house_imp des For the import of description files to the data base of TAC Vista Edited according to an example later in this chapter run as a command file supplying the data base of TAC Vista with relevant information about the network TAC Groups applications public variables and SNVTs TAC AB 1998 12 01 0 004 7637 1 GB 5 3 14 TAC Xenta Zone System Guidelines Programming 5 2 Programming 5 2 1 The Application program of TAC Xenta 300 400 Use TAC Menta to design the application programs of TAC Xenta 300 or start from the Xenta 3000 applications Examples and guidelines appear in the TAC Menta User s Manual and in the TAC Menta Reference Manual Create suitable menus for the OP Test the programs by simulation in TAC Menta Treat the Zone Manager TAC Xenta 400 in a similar way 5 2 2 Configuring the network MetraVision 3 0 HOUSE Topology Open the binding tool MetraVision specify File Project New with the name House All data for the new project will now be put in the catalogue Program Metra House Select View Open Topology to get a window where the network can be designed Begin by draw
31. commissioning may be started It is often desirable to start with the TAC Xenta 300 applications for heating ventilation Program download to TAC Xenta 300 400 Copy the data base and the required programs to the commissioning PC Download the applications into the respective 300 units Use the TAC Menta NCT to connect any I O modules to the base units If possible make a preliminary test of the I O modules Download the application into the Zone Manager TAC Xenta 400 Then use the binding tool for example MetraVision to install the 400 and 300 units with their I O modules and to assign their network addresses Commissioning of TAC Xenta 100 Look up the different Zone controllers apply power and use the binding tool for example MetraVision to install the units and to assign their network addresses Then use TAC Xenta OP or the binding tool to set the most important parameters according to the list from step 4 Commissioning the network Use MetraVision to install the nodes for example the TAC Xenta units and the Routers The Neuron ID of the nodes should be entered directly via the keyboard or a bar code scanner It is also possible to do by help of the Service pin but this method should be avoided as there is a risk for installing the wrong node At first Routers are installed as Repeaters as this will simplify the commissioning work The reconfiguration of a Repeater must be done before the Router is connected to
32. e unit will get a new node number TAC AB 1998 12 01 0 004 7637 1 GB 9 3 2 TAC Xenta Zone System Guidelines Unit Maintenance Blank page 9 4 2 0 004 7637 1 GB TAC AB 1998 12 01 TAC Xenta Zone System Guidelines General Zone System Limits Appendix 1 General Zone System Limits For the TAC Xenta equipment the following general limits or recommended values apply General LonWorks limits for the TAC products No of I O modules No of subscriptions No of address table pos s Send Poll selectable Conditions TAC Xenta 400 10 125 NV in 125 NV out 13 Yes A and or time SNVT and TACNV not t 0 for TACNV TAC Xenta 300 2 15 NV in 30 NV out 12 Yes A and or time SNVT and TACNV not t 0 for TACNV TAC Xenta 100 about 40 NV 15 No LonMarks standard also see below These TACNVs may origin from at most 70 other units TAC Xenta 300 400 Of these 70 at most 40 may reside outside the own Xenta Group that is a Group defined in TAC Menta Network Configuration Tool For TAC Xenta 100 Send SNVT will always cause a send at a significant change e Send heartbeat means for TAC Xenta 100 send on interval and will be performed for certain SNVTs namely those that are listed in the Xenta handbook The time may be set to 0 turned off or to an interval 5 s or greater The value can be changed using TAC Xenta OP or a binding tool Poll All nvi
33. epends on how the bindings are arranged It is vital to identify and group nodes and SNVTs that are to be bound as this will save significant amounts of space in the address tables App 1 4 4 0 004 7637 1 GB TAC AB 1998 12 01 TAC Xenta Zone System Guidelines ID items for the Nodes Page SECUON FLOOL csi Dale Aa i as RE Sign aeaiee No Name Neuron ID Notes TAC Xenta Zone System Guidelines Index Index Special characters des 3 2 5 3 9 9 log 2 mta 5 2 ndb 5 2 Xif 5 2 A actuator type 4 4 addresstable App 1 1 Application program 5 4 B Backbone 5 4 bind the network variables 8 1 Binding the network variables 2 4 C Changing the application program 9 1 command file 5 3 Commissioning 2 3 Commissioning the network 2 3 Configuring 5 4 D descriptionfiles 5 1 description files for TAC Vista 5 8 Description files for TAC Xenta 100 5 10 Description files for TAC Xenta 300 3000 400 5 10 E EANscanner 7 1 example 3 1 F Function Block Diagrams FBD 4 2 Functionaltest 2 4 H house imp des 5 13 I O modules App 1 1 IDitems App 2 1 ID structure 3 4 Import of the Description files 5 13 increase decrease 4 4 installation PC 6 1 Installation work 2 3 L label 6 2 7 1 Learning 5 5 library 5 1 limits App 1 1 logical unitnames 3 4 LTA card 5
34. es for the OP you should in the respective subnets add two dummy nodes which will not be installed but only defined However these dummy nodes must be assigned the proper subnets otherwise no Subnet Node address will be reserved The binding tool will mark up these addresses as reserved and will not assign them to other nodes at a future system extension After this any I O modules can be defined on the same subnet not mandatory though as its base unit Remember that the units are assigned node addresses in the order which they are defined in MetraVision TAC AB 1998 12 01 0 004 7637 1 GB 5 5 14 TAC Xenta Zone System Guidelines Programming Warning This means that you must first define the TAC Xenta unit assign a subnet then define the two dummy units assign the same subnet to them and then any I O modules preferably on the same subnet In this way you will get the same subnet for both the base unit and its I O module s making it simpler to see to which base unit a certain I O module belongs If the number of subnets is insufficient you may assign several TAC Xenta units to the same subnet With this method however it is more important that all units real and dummy are defined in the correct order Also the I O modules should be installed with the binding tool preferably directly after the base unit s dummy positions for the OP When the I O modules are to be configured to their base units in TAC
35. es only from Channel Floor2 Specify if you want to bind On or Off line In On line the binding is performed and loaded directly to the respective unit in the Off line case you will have to wait to perform the download later on Select your Master in the Source output box select the slaves in the Destination input box Use the Shift and Ctrl keys to select the relevant nodes and then click on Bind 8 2 4 0 004 7637 1 GB TAC AB 1998 12 01 TAC Xenta Zone System Guidelines Parameters and NVs in TAC Xenta 100 8 3 To restore the addresses in TAC Vista During the binding procedure in MetraVision it may happen that the address references of TAC Vista are overwritten To restore the address values in TAC Vista you select the menu File Configure physical unit and perform Remove or Insert on suitable units If only single units have to be treated you can specify them individually otherwise it can be done on the network level which may take a long time in the computer Select View Status and click downwards in the network Click right on the network select Read address and get the Subnet Node address for all units of the network El Read address lolx Start gt Status window NETWORK LON1 NETWORK HOUSE XG01 NETWORK XHEAT XU02 NETWORK XVENT XU03 TAC AB 1998 12 01 0 004 7637 1 GB 8 3 4 TAC Xenta Zone System Guidelines Parameters and NVs in TAC Xenta 100
36. he network has not yet been completely connected it is recommended that you install the units and assign their addresses with the binding tool To find out which address has been assigned for a unit go to Browser Network select the respective node and check mark the Num erical value box to obtain the current address Network Browser x Node Connection Node XVentiO1 DomainiSubnetiNode ID Num m Neuron Type 3150 11 6 4 System Type STD Zero Length 6 4 Program Neuron ID 00 00 63 52 95 01 Channel Plan3 State BLANK Network Variables TAC AB 1998 12 01 0 004 7637 1 GB 6 1 2 TAC Xenta Zone System Guidelines Installation and Program download Install the I O unit first with the binding tool and then with NCT check mark the Pre configured box for each I O unit and perform a new download to the base unit Use TAC Xenta OP to check the heat vent functions and that the connected I O modules work Also download the application program for the Zone Manager 6 2 Commissioning of TAC Xenta 100 Look up the different Zone controllers apply power and use the binding tool to install the units and to assign their network addresses Then use TAC Xenta OP or the binding tool to set the most important parameters according to the list from the chapter about the Zone functionality This means specifying the type of hardware actuator etc that will be controlled
37. in the respective description files are downloaded to the controllers The Network Variable nciAppOptions is used to set the outputs and application types Here you may set already at the first commissioning Occupancy sensor connected not connected Energy saving window contact connected not connected e Slave mode active passive Occupancy sensor normally open closed and so on Examples on important parameter settings Zone nciA ppOptions nciMaxFlow nciNomFlow Cafeteria 00001000 11000000 300 300 Reception 00001000 11000000 60 100 Conf room 00001000 11000000 150 200 Audit Master 00001000 11000000 200 250 Audit Slave 1 00001001 11000000 200 200 Audit Slave 2 00001001 11000000 200 200 In the TAC Xenta OP display you call up for example the following menu bit 0 to the left 24 nciAppOptions 00001000 11000000 and so on 4 4 4 0 004 7637 1 GB TAC AB 1998 12 01 TAC Xenta Zone System Guidelines Programming 5 Programming 5 1 Preparations To be able to connect the network to TAC Vista we must create a number of definitions and description files which are used to update the data base of TAC Vista The following items must be defined described performed in TAC Vista The connection of an LTA adapter e A description file for the LTA port and the LonWorks network and the TAC Xenta units and the TAC Xenta Groups Application and description files for TAC Xen
38. ing the network Channels Often you have a Backbone TP XF 1250 or TP FT 10 between the different floors of the building to which the configuration and supervision PC is connected e Put all units with their correct ID on their respective Channel Add the Routers between the different Channels E File Edit View Network Browser Tools Options Security Window Help default_channel E Cafeteria Im Floor E Lf LI pene ag ger A per a pen a pen a per A ge er ee rtrFloor2 Cloakroom Conftoom Officel1 Officel2 Office13 Officel4 Pentry Reception Heat Floor2 Floor3 ae eee 4 4 ttrFlor3 4a 4S 4S a E a ed e d a E ae E En Audit M Audit S51 Audit S2 Office21 Olfice22 Office23 Office24 Office25 Office26 Ea A ag p age p A a ee O p ee eg Office31 Office32 Office33 Office34 Office35 0000835 Offce3 Office38 Olfice39 XVent ZM 5 4 14 0 004 7637 1 GB TAC AB 1998 12 01 TAC Xenta Zone System Guidelines Programming Routers transform the traffic between the Backbone highspeed if TP XF 1250 is used to the lower speed of TP FT 10 used by the Xenta units However the Router also works as a filter for the traffic that only affects the local nodes If the
39. ll TAC Xenta 102 All TAC Xenta 10x NV Type Vent unit Running mode TACNV Running mode Current outdoor temp Outdoor compensated Setpoint Outdoor compensated Setpoint Outdoor compensated Setpoint Slave control Current air flow Current room temp SNVT TACNV SNVT SNVT SNVT SNVT SNVT SNVT Receiving unit Zone Manager All TAC Xenta 10x TAC Xenta 300 1 Zone Manager All offices Auditoriums Conference rooms Other rooms at Floor 1 Xenta 102 Auditorium S1 Xenta 102 Auditorium S2 Zone Manager Zone Manager Please refer to the Network guide for advice concerning the choice of TACNV or SNVT especially the chapter describing Networks that use SNVTs 3 2 4 0 004 7637 1 GB TAC AB 1998 12 01 TAC Xenta Zone System Guidelines Main structure an example Attic TAC Xenta 300 300 421 451 TAC Xenta 401 401 Ventilation unit XVent Dig I O Anlg Zone Manager ZM Cooling pump Floor Office 3 1 Office 3 2 Office 3 3 Office 3 4 Office 3 5 Office 3 6 Office 3 7 Office 3 8 Office 3 9 Fancoil Fancoil Fancoil Fancoil Fancoil Fancoil Fancoil Fancoil Fancoil 3 heating heating heating heating heating heating heating heating heating only only only only only only only only cooling 101 1VF 101 1VF 101
40. number of units is small then several floors can be connected to the same Router possibly with a Repeater to extend the network cable Normally you connect the Channels via a Router to the Backbone In this way each unit can reach every other unit without having to pass more than two Routers If several Routers have to be passed there may be problems caused by the added delay e All Routers can be configured as Configured or Learning during normal operation However during commissioning they should be set as Repeaters as any errors in the subnet enumeration will then not cause errors in the Router If TACNVs are used between some nodes Routers in between must be configured as Learning during operation otherwise there is a risk that messages will not be let through 5 2 8 Configuring the TAC Xenta units When you use a binding tool like MetraVision all the nodes of the network should be included in the data base of the binding tool If for any reason you would like the TAC units to work with another Domain ID than the normal TAC 11 hex all units must be installed with the binding tool As the number of subnets within a domain may be up to 255 each TAC Xenta 300 400 unit can have its own subnet 11 the number of units is reasonable When the Operator Panel is connected it will get one of the two succeeding node addresses of the Xenta unit that it is served by To reserve these two address
41. og will be generated Note The procedure requires the LON ndb file in the same catalogue For the TAC Xenta 300 3000 400 units Heat Vent Created by TAC Menta for each Xenta unit Contains data about the application and its public variables Created by TAC Vista data base generator based on the information of mta Contains data about the public variables Imported to the data base of TAC Vista with the command file house imp des The procedure requires the mta file in the same catalogue Created by TAC Menta for each Xenta unit Contains data about which SNVTs the application uses Log file created by TAC Vista data base generator as the file des is imported Contains assorted status messages For the TAC Xenta 100 units Zone control Edited using the corresponding template files der according to instructions later in this chapter Contains application parameters standard alarm texts and similar Imported to the data base of TAC Vista with the command file house imp des The procedure requires the xif file in the same catalogue Exists in standard form for each type of TAC Xenta 100 Contains data about which SNVTs the unit uses Used when des is to be imported to the data base of TAC Vista xif files can be fetched directly from the units or downloaded via Internet at http www tac se tarai Standard graphics for a simplified display in TAC Vista of most of the SNVTs that are used in the different TAC Xent
42. on of the NWC file and the IOD file When you select Download application and parameters in the Status window and perform the download the NDB file must already be updated with information about the I O units IOD connected to the current TAC Xenta Otherwise you will lose contact with the I O units At upgrade to TAC Vista 3 1 the NWC files are transformed to NDB files However these NDB files miss the information from the IOD file Consequently the automatically converted NDB files must be replaced with NDB files created with the Network configuration tool that comes with TAC Menta Open the old NWC file and save it as a new NDB file Insert the updated NDB file in the NDB object for your network in the TAC Vista data base For more information on the definition of networks see the chapters Define a LonWorks network in TAC Vista and Definition of a Xenta network dialled up Xenta network in TAC Vista 5 Open the Status window in TAC Vista and download the changed TAC Xenta application program s MTA to your TAC Xenta unit s Select the menu View Status in TAC Vista Indicate the required unit s in the tree an click right Use Download application and parameters in the pop up menu and perform the download 9 2 2 0 004 7637 1 GB TAC AB 1998 12 01 TAC Xenta Zone System Guidelines Unit Maintenance If the change also involves the use of SNVTs you must also 9 Start
43. r functions e TAC Xenta 100 Zone controllers which types Fan coil VAV Chilled ceiling and how many Routers Network separation for faster traffic and or message routing Repeaters Cable extension more nodes e TAC Vista Central system functions and network connection TAC AB 1998 12 01 0 004 7637 1 GB 2 1 4 TAC Xenta Zone System Guidelines Working method 3 4 Determine the logical structure that is an ID structure which will work both in TAC Vista and when you configure the network You should probably use the method which is described in the Engineering Guidelines Zone functionality Decide which functionality will be required of the Zone system e Which signals are needed and between which units one one one many Which points are needed and to which units are they to be connected Which groups should be created to cater for common functions Which functions should be included in the Zone Manager TAC Xenta 400 List the most important settings for the zone controllers around 2 3 per unit to simplify the commissioning The settings should include the hardware type actuators etc which are to be controlled The remaining settings are easily made from TAC Vista 2 2 Programming guidelines 5 6 7 Preparations Prepare for the programming by creating a suitable structure for the necessary directories and files Obtain the XIF files for the
44. s for the Zone Controller TAC Xenta 103 5 12 14 0 004 7637 1 GB TAC AB 1998 12 01 TAC Xenta Zone System Guidelines Programming Import of the Description files for TAC Vista In order to organize our work we create a final description file which contains all the description files that are to be imported This is described in the chapter Define Direct port and TAC Xenta network in TAC Vista the section Definition and import via a description file The resulting command file house_imp des will be TA Vista DATA BASE GENERATOR PROJECT TAC Vista TAC Xenta DESCRIPTION house_imp des The House AUTHOR Simon Template TIME 1998 04 02 13 11 39 KKK KK KKK KKK
45. s temporarily occupied for the bypass period 3 OC STANDBY Area is temporarily unoccupied Set outdoor temperature compensated reference value for each zone Get Outdoor temeperature from heat controller OutdoorTemp Add individual adjustment FBD for Running mode and for Room temperature Setpoint 4 2 4 0 004 7637 1 GB TAC AB 1998 12 01 TAC Xenta Zone System Guidelines Zone Functions Get current flow from VAV units How Conf FBD for the Sum flow per floor Current temperature from each zone ZoneTemp New value Sum Every 20 minutes Current temperature Lowest tempetgture FBD for the Temperature values TAC AB 1998 12 01 0 004 7637 1 GB 4 3 4 TAC Xenta Zone System Guidelines Zone Functions 4 3 The most important settings To simplify the Zone Controller commissioning you should list the two three most important hardware settings This can be done as you go through the specification For example you can set the current actuator type ON OFF or increase decrease When it is time to commission the zones you look up the Zone controllers apply power connect the TAC Xenta OP change the settings according to the list and check that the controllers work correctly At this stage it does not pay to perform a complete commissioning Later we will connect the controllers to TAC Vista Then all the settings that have been specified
46. sses that are available NV selector shows how many individual variables that can be handled and this figure is seldom limiting in this context SNVTS states how many SNVTs that can be specified for each unit When you wish to connect one variable in a node to one variable in another node you perform a binding This means that you put an address in the address table of one or both of the nodes and a notation about which variable is bound in the NV Selector table of each node Before any binding has been done the tables are empty App 1 2 4 0 004 7637 1 GB TAC AB 1998 12 01 TAC Xenta Zone System Guidelines General Zone System Limits Types of Binding When binding is performed between Xenta 400 and Xenta 100 there are two types of SNVT bindings e Send Only the node that sends data for example Xenta 400 needs to use one position in the address table e Send and Poll This means that normally Xenta 400 sends to Xenta 100 but that the receiving unit Xenta 100 at the start up polls asks for sending from Xenta 400 Consequently both the Xenta 100 node polling and the Xenta 400 node sending have to use their address tables Addressing types Unit addressing If you bind one or several SNVTS between two nodes this will require one position in the address table of one or both nodes depending on the type of binding as discussed above Group addressing If you bind one or several same to all SNVTs bet
47. ta 300 3000 400 Description files for the TAC Xenta 100 units Import of the description files to TAC Vista The files that are used or created can be put in a library with the following structure Note All of the procedure in this chapter can be done off line from the network Current project Command file Network configuration Application dependent files Description and Zonreg XIF files for the TAC Xenta 100 units A suggested project library for description files etc TAC AB 1998 12 01 0 004 7637 1 GB 5 1 14 TAC Xenta Zone System Guidelines Programming LONI ndb LON1 des mta des xif log des xif ser log The methods to create these files and their main contents are explained below For the LonWorks network Created by TAC Menta NCT Network Configuration Tool Contains data about the TAC Groups Group masters and I O modules Imported separately to the data base of TAC Vista Please refer to the chapter Network configuration in TAC Menta User s Manual LONI ndb must reside in the same catalogue as LON des Note If LONI ndb is changed in any way it has to be imported again to the data base of TAC Vista Edited according to the example below Contains data about the current PC the network port the name of the network and of the file above Imported to the data base of TAC Vista with the command file house imp des The log file LONI l
48. tem Guidelines General Zone System Limits Send and Poll SNVT When the first binding of a Send and Poll type from one Xenta 400 to one Xenta 100 is made the address of the Xenta 100 node will be put in the address table of the Xenta 400 At the same time a reference to the bound variable type will be put in the Selector table The corresponding items will be put in the Xenta 100 node in order for it to poll data Worst binding case Address table ZM 1 X100 no 1 Xenta 100 Address table 13 1 X400 ZM Ea Send and PoliNv1 MO ETS ai 3 TAC Xenta 400 Send and Poll NV2 i 4 5 1 Send and Poll NV13 13 X100 no 13 M5 X100 no 14 Xenta 100 no 14 If you have bound 13 different SNVTs from one Xenta 400 to 13 different Xenta 100 you will have filled up the address table of the Xenta 400 and can bind no further Xenta 100 should these use other SNVT types Best binding case Address table ZM 1 G r E Address table roup amp enta 2 X Send and ho 1 100 Group 1 3 TAC Xenta 400 NVI Z 2 X400 ZM 4 NV2 3 Fy k 4 NV5 2 amp 7 13 F 15 If you bind for example five SNVTs in the same way from one Xenta 400 to 100 different Xenta 100 you will only use one position group address in the address table of Xenta 400 and two in the respective Xenta 100 units Conclusion There is no simple answer to how many TAC Xenta 100 can be connected to one TAC Xenta 400 It all d
49. the network TAC AB 1998 12 01 0 004 7637 1 GB 2 3 4 TAC Xenta Zone System Guidelines Working method 13 14 When the units have been installed you generate in MetraVision a report which you can edit so that only the name of the units their Neuron ID and type are saved Using this report you can enter the Neuron ID into the description files from step 8 Start TAC Vista and import the now completed description files After that it should be possible to read the Subnet node addresses from the network Reconfigure those Repeaters that are to work as Routers Configured or Learning Parameter download TAC Xenta 100 Download the zone controller parameters TAC Xenta 100 units from TAC Vista Binding the network variables Restart MetraVision to perform the network variables binding This will be simplified if the templates from step 7 are used During the binding procedure certain addresses for TAC Vista may be overwritten In order to restore these you must go back to TAC Vista please refer to section 8 3 Functional test Now it is time to perform real functional tests and to backup the system 2 4 4 0 004 7637 1 GB TAC AB 1998 12 01 TAC Xenta Zone System Guidelines Main structure an example 3 Main structure an example 3 1 The Plant From here we will work with an example on a fairly small zone system This example comprises two TAC Xenta 300 to control the use
50. though Now run house imp des as a command file to import the complete description files to TAC Vista After this it should be possible to read the Subnet node addresses from the network to TAC Vista Select View Status and click downwards in the network Click right on the network select Read address and read Subnet Node for all units of your network Read address lolx Start lt Status window 0 Error mess NETWORK LON1 NETWORK HOUSE XG01 NETWORK XHEAT XU02 NETWORK XVENT XU03 2 TAC AB 1998 12 01 0 004 7637 1 GB 7 3 4 TAC Xenta Zone System Guidelines Commissioning the Network Blank page 7 4 4 0 004 7637 1 GB TAC AB 1998 12 01 TAC Xenta Zone System Guidelines Parameters and NVs in TAC Xenta 100 8 Parameters and NVs in TAC Xenta 100 8 1 Parameter download After the Zone Controllers have been configured to TAC Vista and so can be treated as on line alarms begin to appear TA Vista Logged in SYSTEM File View Alarms Tools Options Window Help vv v CIE S 4 Number of alarms 3 Itis now time to download the Zone Controller parameters from TAC Vista Select View Status and click downwards in the network Click right on the network select Download parameters only and send them down H Download parameters only Iof x NETWORK FLOOR3 LWG03 NETWORK FLOOR3 OFF3 NETWORK FLOORGS OFF3 NETWORK FLOORG OFF3
51. ts rito e E ren e HEP EE FERIA HERE a vs 22 Creating Templates in Metta Vision retenue an ii ini Asi ss ij is 5 7 Preliminary Description files for TAC Vista 00 rp i aa 5 8 Installation and Program download ee OFL Program download to TAC Xenta 300 400 220 6 1 Commissioning of TAC 6 2 TAC AB 1998 12 01 0 004 7637 1 GB 1 2 TAC Xenta Zone System Guidelines Contents 7 Commissioning the 1 71 Nodes and ROUES seed sai senis sis eO SERIE eases ss ss CHE sios ses 7 2 Completing the Description files 8 Parameters and NVs in TAC Xenta 100 8 8 1 Parameter download 8 2 Binding the Network variables 8 2 1 Binding with Templates eerte trente etre einen pedo 8 3 To restore the addresses in TA C Vista e eee esee eee eee eene 9 Unit Maintenant wl 9 1 Changing the application nnn aaa Appendix 1 General Zone System Limits ID items for the Nodes Index This manual contains a total of 30 leaves GTAC Xenta TAC Menta and TAC Vista are registered trademarks of TAC Sweden GEchelon LON LonTalk LoNWonks and Neuron are registered trademarks of Echelon Corporation California USA TMLonMark and LonMaker are trademarks of Echelon Corporation California USA MetraVision is a trademark of Metra Corporation USA 2 2 0 004 7637 1 GB TAC AB 1998 12 01 TAC Xenta Zone System Guidelines Introduction 1 Introduction
52. uron Node Cafeteria x A Neuron ID 01 00 20 1d 2d 00 Cafeteria Description Location Application Program Name X102V02 Eu Self Document Network Channel default channel zl Priority p Subnetl TAC default Auth Keyt HW Properties Install Replace vd Remo En Load App i Wink On Test Reset Off line close 5 TAC AB 1998 12 01 0 004 7637 1 GB 7 1 4 TAC Xenta Zone System Guidelines Commissioning the Network Installation with the Service pin If you are the sole user of the network and have an assistant you can identify the units by pressing the service pin on each unit After that you should perform a Wink command to verify that you have got the Neuron ID from the correct unit as it may easily happen that a Neuron ID from another unit enters via the network Some units may need several trials before the installation is accepted Should this fail you may have to replace the unit If the Neuron ID of the old unit has been noted you will have to enter a new Neuron ID manually or even remove the node completely Remove in MetraVision before it can be installed anew Note For TAC Xenta 100 you have to make final Load if the following two conditions both apply Metra Vision is used and TAC Xenta 100 is as has been recommended configured only in the application domain
53. utput mode nvoAlarmStatus bit0 0 bitB bitl O bit9 bit2 bit10 bit3 bit11 bit4 bit12 bit5 bit13 bit6 bit14 bit bit15 fl if If Meiji em nvoEffectSetpt nroSpaceTemp nvoHeatPrimary nvoHeatPrimaryR nvoCoolPrimary nvoCoolSecondary nvoSpaceCO2 nvoEnergyHoldOff value state nviManOccCmd nviApplicMode nviSpaceTemp nviSetpoint nviSetpntOffset 0 00 0 00 0 00 0 00 0 00 0 00 0 00 0 00 0 00 0 00 0 00 0 00 0 00 0 00 0 00 0 00 0 00 0 00 0 00 0 00 0 00 0 00 17 nviSpaceCO2 0 00 34 nciCO2PerVolt 0 00 18 nviEnergyHoldOff 35 nciSpaceCO2Low 0 00 value 0 00 E oN SP 0 00 36 xd E 0 00 19 nviHeatPriSlaveR 000 i MOD 20 nviCoolPriSlave 0 00 a 0 00 21 nviCoolSecSlave 0 00 a 22 nciAppOptions 40 nciSndHrtBt 0 00 bit 0 bit8 0 41 nciRcvHrBt 0 00 biti O bit9 0 0 biti0 0 bit3 D bitlf 0 bit O bitt2 0 bits O bitl3 O bit D bitl4 0 biz 0 bitl5 23 nciSetpoints occupied cool 0 00 standby_cool 0 00 unoccupied_cool 0 00 occupied_heat 0 00 standby_heat 0 00 unoccupied_heat 0 00 24 nciSpaceTempDev 0 00 25 nciSpaceTempLow 0 00 26 nciGainHeat 0 00 27 nciltimeHeat 0 00 28 nciHeatActStTime 0 00 29 nciGainCool 0 00 30 nciltimeCool 0 00 31 nciGainDamper 0 00 32 nciltimeDamper 0 00 33 nciSpaceTempOfst 0 00 Standard graphic
54. ween a Xenta 400 and a number of Xenta 100 units this will always require one position the group number in the address table of all affected nodes Should the type of binding be Send and Poll one further address position will be required in each Xenta 100 to request a sending from the Xenta 400 Examples on bindings Send SNVT When the first binding of a Send SNVT is made from a Xenta 400 to a Xenta 100 the address to the Xenta 100 node will be put in the address table of Xenta 400 At the same time a reference to the bound variable type will be put in the Selector table of both nodes If after that you bind the same SNVT of the Xenta 400 node to another Xenta 100 no further positions will be required from the Xenta 400 address table Instead the binding tool will switch from unit addressing to group addressing The new node will get the group address in its address table and a reference to the current SNVT in its Selector table If instead you should bind another SNVT between the two original nodes no further address positions would be required only an additional reference in the Selector table of the two nodes To sum up New positions in the address table are only required if the addresses unit or group have not already been defined in the table If it is possible same SNVT to several nodes the unit address is replaced with a group address TAC AB 1998 12 01 0 004 7637 1 GB App 1 3 4 TAC Xenta Zone Sys
55. will be made for several nodes In our case we have an auditorium consisting of three zones which are controlled via a Master with two slaves The Master is supposed to send two signals nvoBoxFlow and nvoHeatSlave to the slaves where the corresponding inputs are called nviBoxFlow and nviHeatSlave Select Tools NV Template Editor Add new In the template editor of MetraVision we look up the specific XIF files Program Name in our case 1021 02 both for Output and for Input We create the first connection Connection and name it CName FlowSlavel02 Specify which signals shall be included in the connection by double clicking on them As a result they will be copied to Connection Item Should an incorrect signal be included it will be removed if you double click on it in the window Connection Item When all required NVs have been included you acknowledge by clicking OK Network Variable Output Program Name X102V02 NV InvoAlarmStatus out SNVT_state 2 nvoBoxFlow out SNVT flow 2 EE nvoEffectOccup out SNVT occupancy 1 X Network Variable Input Program Name X102V02 NY InviApplicMode in SNVT_hvac_mode 1 in SNVT flow in SNVT hvac emerg nviBoxFlow i Name FlowSlave102 nvoBoxFlow Service App Cnfg 0 MV Lon Manager No _ ar ep Save the first template File Save in the file Slave tbd
Download Pdf Manuals
Related Search