Home

TAC Xenta and LonMaker Release 3

1. From Device CALonveorksumportiT A CV m XIF ZH External Interface Definition Select Load XIF to import the XIF file as a file Should you select Upload From Device you will have problems with the unit already exists etc For Template Name enter a new previously unused name Then click Next 78 88 0 004 7775 1 GB TAC AB 2001 02 15 TAC Xenta and LonMaker 7 Unit Maintenance Replace Device Wizard Pint Select Manual that is manual Neuron ID entry as the node is already installed and is there BrOWSE Make sure you do not checkmark the Load Application Image box As the TAC Xenta controllers are host based you must not change the Neuron program from the network management tool this is done from TAC Menta TAC AB 2001 02 15 0 004 7775 1 GB 79 88 TAC Xenta and LonMaker 7 Unit Maintenance Determine the state of the new unit after the installation If everything goes according to plan the SNVTs of the new application are now supposed to be included Use drag and drop to put the new network variables into the function blocks of the unit will also restore all bindings formerly in the unit To clean up it may be convenient to look up which Device Templates are no longer in use Use the tool bar to select LonMaker Device Templates Device Templates Template Name Pr
2. 6 Pick out Hub and Target in the usual way When the new binding type has been created you can henceforth select it under Connection Attributes New Connections 62 88 0 004 7775 1 GB TAC AB 2001 02 15 TAC Xenta and LonMaker 6 Installation of the Units 6 Installation of the Units 6 1 Network Interface and Routers Now that we have designed the network it is time to physically install the units that is all units are to be connected and given their address Depending on the extent of the network it may be more convenient to bring along the PC with the database to the site treating one area at a time If the PC with the LNS Network Interface is to be temporarily connected to any other channel apart from the original you must specify so in LM3 In this case you may either move the LNS Network Interface symbol to the drawing with the intended channel or let the system redraw the intended channel connection in the page where the LNS symbol already resides Procedure Leave LM3 move the commissioning PC to the new channel and reopen LM3 Make sure that Network Attached is indicated normal case during commissioning Click right on the LNS Network IF symbol and select Change Channel Enter the items for the intended destination and confirm that the PC has been moved in the Move devices and routers window If the routers are missing at this stage or if you do not wish to install them rig
3. Br Ho application program Carnet vaite EEPROM Xenta 103 Plug in Other parameters In the Plug in window title the Plug in name and the associated function block name are displayed The names are shown according to the following format NetworkName SubnetName Device FunctionalBlock The OK button finishes the Plug in but sees to that any modified nci s are sent away first The Cancel button finishes the Plug in without sending away any modified nci s This means that if the Apply button is not highlighted nothing will be lost If however the Apply button is highlighted those changes which were made since the Apply button last were pressed will be lost 44 88 0 004 7775 1 GB TAC AB 2001 02 15 TAC Xenta and LonMaker 4 Step by step The TAC Xenta Units 4 2 TAC Xenta 300 401 free programmable Device Enter Device Name Use the Drag and drop technique to put TAC Xenta 300 units on the drawing As the TAC Xenta 300 401 series consist of free programmable units there are no ready made templates in stead you have to use the general functions of LM3 Select Device Enter a suitable Device Name Device Name If you want to work on line checkmark Tongue Mane Commission Device otherwise let it rest Number of Devices to Create Commission Device Then click on Next EY New Device Wizard x Specify
4. Template for new networks Languages metric US English Move Up Exit Design Manager after launching Visio Move Down Disable warning display if Visio version is greater than 5 0 Remove Reselect the General tab TAC AB 2001 02 15 0 004 7775 1 GB 23 88 TAC Xenta and LonMaker 3 Step by step The Network Echelon LonMaker lal xi General Options Ls ECHELON r Existing Network Lo n M ake r 3 Drawing Directory lt none gt EUM Open Copy Drawing Name none e Delete Database snone X Defragment Database Show all network option dialogs Backup R LNS Restore ECHELON 1 Settings Subject to termz of licenze agreement ji Copyright 1336 2000 Echelon Corp Drawing Base Path c Wmidrawwings m Add All Rights Reserved Select New Network Give the network Name p Naming This will become the default Network name of the paths for the Testnet Browse Database and the Drawings that is the Visio files in Recover database from network Drawing Path Network Database Path Then click on Next gt as in cuniDb Testnet Browse the succeeding data entries of the Network Wizard Network Drawing Path clmidrawings TestnetiTestnet vsd Browse Network Description
5. C 6 1 10014 JGuueu lld equeyd quawaseg pue 100 e 10014 jouueyd omy pue 100 4 ufisAsqng auoqyoeg PUOMIEN SHIT 4 Arrangement of drawings and pages Visio an example TAC AB 2001 02 15 32 88 0 004 7775 1 GB TAC Xenta and LonMaker 3 Step by step The Network 3 4 Some Subsystem examples We will now return to the Visio drawing we got at the end of section 3 1 and add links symbols for subsystems for those channels that are connected to the Backbone via a router The new subsystems are created as separate files for the respective channels Create new Subsystems by pulling the Subsystem symbol onto the drawing Here you also specify if the subsystem is to be put in a new Visio drawing file Drawing New or in an existing Drawing Existing Do not forget though the recommendation to store at most 10 drawing pages subsystems per Visio file x Subsystem Name Subsystem Drawing Existing TESTNET Name TestnetSubsystem Subsystem Contents Copy Do not copy ony selected Subsystem Floor3 and Roof Floor 3 Floor 2 Floor 2 Floor 1 and Basement Floor 1 TAC AB 2001 02 15 0 004 7775 1 GB 33 88 TAC Xenta and LonMaker 3 Step by step The Network Note If
6. Also the TACNV messages are affected by the group addressing If you install the units with TAC Menta NCT before you have used LM3 you can start by setting the addresses in TAC Xenta 300 401 and the I O modules This is done in the usual way in TAC Menta NCT LM3 will use a whole set of different address values but this is no drawback and will help us avoid address conflicts at a later stage Try to use high subnet values to minimise the risk of having the same subnet number on both sides of a router Checkmark the Binding tool used and the Preconfigured boxes for the respective I O modules Uncheck the Download group addresses and perform another download The TAC Xenta units and their I O modules are now set up to be used in the network After an installation with LM3 a restart of the TAC Xenta is sufficient for it to get in contact with its respective I O modules TAC AB 2001 02 15 0 004 7775 1 GB 69 88 TAC Xenta and LonMaker 6 Installation of the Units 6 4 Special actions for the TAC Xenta units 6 4 1 TAC Xenta 300 401 e TAC Xenta 300 401 whose applications do not use SNVTS always have the same program ID and so the same XIF file Also used by 901 e TAC Xenta 300 hardware type 1 will incorrectly get the same XIF file from TAC Menta as hardware type 2 As hardware type 1 has another type of Neuron which cannot be installed in a correct way hardware type 1 must never be used
7. Groups in LM3 Group binding eseesessesessosessesoesesooseososoosoeoessesossesossesossesse 52 5 3 Bindings between the Function blocks essesessosessoesesoesessescosesoessosossesossesoesessoscesoeoessesossesoesessosessese 57 5 4 Sending to several nodes using only one line of the address table ecce 59 6 Installation of the Units ccce eene ed eno oco eo ee ou co oet o oae ood OS 6 1 Network Interface and Routers eee eee eee eee eee esee enses seta statu 63 6 2 The TAC Xeta imis civ 64 6 2 1 OME unit ata time is eee emerat Hee Meteo x eee mr R e EDI E 64 6 2 2 Several umts together sissies ged Ry Riles pee em ene MEER 66 6 3 The need for the TAC Menta Configuration tool 4 ecce eee ee eres eene eene eese tn tense tn sense neto ata 68 6 4 Special actions for the TAC Xenta units 4 eres eere esee eee teet tanen etse setas eae eae sse neta 70 6 4 1 TAG Kenta 300 40 tee etit citet ee e ete edicere Lo ed eere tems 70 6 4 2 TAC Xenta 400 O modules estes eee emat fect decree idee tre eoe e Dade 70 6 4 3 Xenta OP ia costs e n esito ede rete eb e RR pede bere 70 6 4 4 TAG 100 osea eei ere ad ee e He NUR 73 6 4 5 Xenta Q0
8. Only licensed users of the product and the document are permitted to use the document or any information therein Distribution disclosure copying storing or use of the product the information or the illustrations in the document on the part of non licensed users in electronic or mechanical form as a recording or by other means including photocopying or information storage and retrieval systems without the express written permission of TAC AB will be regarded as a violation of copyright laws and is strictly prohibited TAC Xenta TAC Menta and TAC Vista are registered trademarks of TAC AB in Sweden and other countries All other brand names are trade marks of their respective owners List of Revisions Part no Comments Writer Date 0 004 7775 0 Original preliminary release KW 2000 03 10 0 004 7775 1 Revised due to LonMaker v 3 0 KW 2001 02 15 4 88 0 004 7775 1 GB TAC AB 2001 02 15 TAC Xenta and LonMaker Contents TAC Xenta and LonMaker Release 3 Subject to modification 2001 TAC AB Contents 1 PING OG UCOOB taces ea ener eto beo 11 7 1 2 SCOPE ANA restrictions M 7 1 3 1 eos rosin 8 14 Terminology 10 2 DE LO
9. 2 1 MEHICOLEES IVO VS CURRERE 15 2 1 1 Project libraty ies tubes tt UR i e ne IO er ies 15 2 1 2 Decimal symbol 2 eie OBS Sip p pU Rete terne 16 2 2 Installation of LonMaker Tool csccssscsccssscssscscscsscsssccssccssssccsssssscssssscsssscsessssesesssessessecsseeseeees 17 2 3 Bon Maker Ovi 18 2 4 Restrictions when using LM eerie eee ee ee eee ettet eese ee tense tosta seta sense eese tee sesto enata 20 24 1 TAG Kenta OP de tm euntis a te die EMEND 20 2 4 2 Restrictions TAC Xenta software and hardware versions 21 2 5 Backup Restore of a LonMaker network cscssscssssssssscsscceccssscsscssccscsesssscssscssesssessecssesseesseeseeee 21 2 6 Several integration tools used simultaneously sesseseesesoesesoosessoesesoesesoesoosoeoessesossesoesesoossesossesossesse 21 3 Step by step The Network 4 eee ecce eere eee ee seen oe eeeo sesso se eesoseeeseseeeseseeese 29 3 1 Create a new network eese eee eee ine den Seios SSos ses senso seta sie 23 3 2 Network demo example ccsccccscsssssscssscsccssscssccssescccssccsscccesssecsessscssscscssescssssscssssssesssessessecsseeseeses 30 3 3 Graphic disposition LM RE 31 3 4 Some Subsystem examples cccssccscscsssscccscscsccsescsccsessssssss
10. 24 88 0 004 7775 1 GB TAC AB 2001 02 15 TAC Xenta and LonMaker 3 Step by step The Network Network Interface Network Interface Network Attached Network Interface Name z If you work off line Engineering Mode recommended as commissioning will be much easier leave the box unchecked If you work directly on the network the Ad hoc mode you indicate this with a check mark in Network Attached You will then also have to specify the Network Interface Name Leave the Skip this prompt when box unchecked Skipthis prompt when re opening this drawing in this and succeeding windows as the on line conditions may differ from time to time Management Mode Management Mode Offnet save device changes This window appears only if you d selle deat specified Network Attached for later processing Onnet online Skip this prompt when re opening this drawing Offnet later processing Onnet or Offnet this choice may be altered later When you work Onnet changes will propagate directly to the units in the network At the command Commission Device the node address and other items will be sent to the node When you work Offnet nothing is sent to the nodes but still data is stored in the database At the command Commission Device the Neuron ID will be read into the database Plug in Registration Select which Plug ins are to be registered for the
11. It is convenient to collect all XIF files that are to be used in a directory of their own for example C LonWorks Import TAC A Device Template may in LMG be associated with a unit in three different ways Uploaded from the respective units mported from a XIF file Anexisting Device Template is used In order to enter units to LM3 you must let the tool have access to the corresponding Device Templates in one of the ways described whether you design your network on line or off line Network Variable Input and Output Values that are sent to nvi or out from nvo a unit An example could be the outdoor temperature Network Configuration variable Input A number of parameters to set the behaviour of the unit for example the P band value Please note that nci often is stored in the flash memory or in EEPROM In that case you must not let the variable be frequently written into as these kinds of memory only stand a certain number of write procedures for example 10 000 for one type A Plug in is usually a software specially designed for a certain type of node associated via the Program ID of the node to facilitate work with this node Such a Plug in is handled via a dialogue window with tabs a Property Sheet dialogue where all the parameters and variables can be reached Visio Technical 2000 is a program tool used by LM3 to handle and present all network drawings The following terms are used P T O
12. Note If an I O module needs to be replaced the primary objective is to change the Neuron ID in the database of TAC Vista and in the parameter set of the base unit The procedure below applies only if the original I O module was installed using the network management tool Replace the I O module it is convenient to note the Neuron ID of the module at this stage In LMG click right on the current I O module select Replace and follow the instructions appearing on the screen similar to those used at the installation of a new node Should you miss the Neuron ID of the new module click right on the unit select Properties and note the Neuron ID Export the ndb file from the database of TAC Vista Use TAC Menta NCT to enter the new Neuron ID make sure that the Pre configured box is checked Re insert the updated ndb file in TAC Vista e Perform Download Application and Parameters to the base unit of the new I O module TAC AB 2001 02 15 0 004 7775 1 GB 81 88 TAC Xenta and LonMaker 7 Unit Maintenance Blank page 82 88 0 004 7775 1 GB TAC AB 2001 02 15 TAC Xenta and LonMaker Appendix Application Key Appendix Application Key This is an example on the way it may look when you receive an Application Key opening up for the use of new Credits chapter 2 TO Name Customer s information Company from the order Business unit Phone Fax Email x
13. RU IRE rH RR RTI IN HH tur 74 6 4 6 Status SUmmaty oie geimiigteelet ee namen e E DB GEI BER Sa eh 74 7 Unit Maintenance sicscccescccscessccsecesscccecesccsswocescocucestsssadessccencecesssedecscccucesdessecesscccocscescsessee 7 1 System Backup and documentation ccscsssssscssssscsssssscscssscssessscsscsssssecssesssessessseesecssessessseescees 77 7 2 Changing the application in TAC Xenta 300 401 sessososoossesossesossesoesesseseesosoesseoessssossesossesoesossesose 78 7 3 Replacing Xenta 400 I O module etes tts etes neta 81 Appendix Application Key siiscesccerssscssoosssssosvessaresnsentsoensebonsenasooseonensesnsdsnsbconessoossonssussoanstsonsse OD Ini dq E This manual contains in all 88 pages 6 88 0 004 7775 1 GB TAC AB 2001 02 15 TAC Xenta and LonMaker 1 Introduction 1 Introduction 1 1 Purpose This manual intends to show how to use Echelon Corporation s network management tool LonMaker Integration Tool Release 3 LM3 when working with TAC Xenta components in a LONWorKS network runs as an application on the LNS LonWorks Network Services network operating system LNS is a client server system with all the functions that are needed to handle an open LonWorks network The manual is intended to be a complement to Echelon s LonMaker for
14. TAC AB 2001 02 15 0 004 7775 1 GB 11 88 TAC Xenta and LonMaker 1 Introduction drawing drawing file subsystem Visio page shape stencil File types in Visio LM3 Domain table A LonMaker drawing consists of one or several drawing files see below Each file may include one or several subsystems where each subsystem makes up one Visio page In the Visio manual a couple of terms also need to be explained shapes and stencils A shape is a screen based sticker that is a drawing object which can be copied onto the drawings It may consist of a line or a rectangle but may also have a more complex design to represent a LonMaker unit or a function block These shapes are collected in separate drawings labelled stencils in Visio and are then often referred to as master shapes To use shapes you open the required stencil command Open Stencil or click on a dedicated button in the tool bar of the window point on the requested master shape and draw it to its place in the drawing getting a copy of the shape The drawing files which are created when you work with Visio via are true Visio files The respective file types may be identified by the following name additions vsd Visio drawing file vst Visio drawing file as template vss Visio stencil file TAC Xenta was originally designed to work with two domains the application domain and the zero length domain Using the network
15. 2001 02 15 TAC Xenta and LonMaker 1 Introduction The TAC Xenta 300 and 401 controllers and the Operator panel are described in the following documents e TAC Xenta 300 and 401 Handbook part no 0 004 7768 e TAC Xenta Network guide part no 0 004 7460 The data sheet for TAC Xenta 300 C 90 05 The data sheet for TAC Xenta 401 C 92 05 The data sheet for TAC Xenta OP Operator panel C 98 05 e ashort installation instruction OFL enclosed with each product TAC Xenta 901 a serial LonTalk adapter is described in e TAC Xenta 901 Handbook part no 0 004 7660 The data sheet for TAC Xenta 901 C 96 10 TAC Xenta 911 an IP modem replacing the telephone modem is described in The data sheet for TAC Xenta 911 C 96 15 TAC Xenta 511 a unit which can supervise a minor LoNWonks network or act as a local presentation system in a large network is described in The data sheet for TAC Xenta 511 C 97 1 Furthermore useful instructions are presented in TAC s web products Engineering guidelines part no 0 004 7790 TAC Menta with its network configuration tool is described in e TAC Menta v3 User s manual part no 0 004 7608 e TAC Menta v3 Reference manual part no 0 004 7609 TAC Vista and those modules which are treated in this manual are described in the following manuals e TAC Vista 3 2 Operator guide part no 0 004 7571 e TAC Vista 3 21 Basic
16. Normal nvi Flow CloakRm IC WIE Use References Connections Show Connections Selected Connections Selected Connection Targets Between Selected FB SNs From or To Selected FB SNs Connection Attributes New Connections Default Connection Description Properties Assign 58 88 0 004 7775 1 2001 02 15 TAC Xenta and LonMaker 5 Step by step Bindings ZoneManager1 Func Block 1 ZoneManager1 Binding Functional Block Unit The result after the binding 5 4 Sending to several nodes using only one line of the address table Normally one line of the address table is used in the sending node for each receiving node or group that you wish to send to As there are no more than 15 table lines at the most for each node you will soon run out of address lines even in small sized networks If you need to send more messages you may in LMG create a special type of binding using the so called broadcast message Characteristics for this type of messages are Only one address the subnet address is used in the sending node in spite of the fact that the transmission is for several nodes Message acknowledge cannot be requested It is not possible to identify the receiving nodes using a line analyzer The message is a broadcast message meaning that every single node listens The message is then ignored by nodes that do not belong to this b
17. an external binding tool will be used no addressing will be done on the zero length domain that is TAC Xenta will only listen on the application domain Please note that in TAC Menta NCT the Binding tool used is specified per I O module under the label Preconfigured Checkmarking the Preconfigured box means that TAC Xenta will not set the address of the I O module x No 1 r Database Base unit Subnet 3 Mode 3 Neuron 10 010082577C00 450 Version fi 02 04 Status Cancel Service Pin 68 88 0 004 7775 1 GB TAC AB 2001 02 15 TAC Xenta and LonMaker 6 Installation of the Units TAC Menta NCT is also used to set the group addresses of TAC Xenta both for the general TAC group default 51 and for the respective TAC Xenta groups default value starting with 16 When configuring TAC Xenta with LM3 you have to create the TAC group by creating bindings between all the TAC Xenta 300 401 units of the network and for the TAC Xenta groups a binding between all TAC Xenta 300 401 units of the respective groups In this case the group addresses will reside in the LNS data base and they will be transferred to the nodes at the installation Please note that you must specify in TAC Menta NCT that the group addresses are not to be down loaded Otherwise you may risk an address conflict Configuration Delay for restart in seconds 30
18. configuration tool of TAC Menta NCT you can configure the TAC Xenta 300 401 units assigning the Xenta a subnet node address the same in both domains An LNS network uses only one domain the application domain Additionally the management tool of LM3 assigns its own address values to the respective units these assignments are completely beyond the influence of the operator When a TAC Xenta 300 401 unit is to be used in an LNS network you check mark the NCT box Using Network Management Software NCT will then no longer address the TAC Xenta units instead this will be handled by LM3 As for example the Service pin message from an I O module is always sent on the zero length domain a TAC Xenta installed with LNG cannot receive this message Instead you must use the TAC Menta program for network configuration NCT at the installation enter the neuron ID of the I O module manually and mark it as pre configured 12 88 0 004 7775 1 GB TAC AB 2001 02 15 TAC Xenta and LonMaker 1 Introduction TAC group TAC Xenta group TAC Xenta Group master All TAC units except TAC Vista belong to the common TAC group 51 TAC Vista can however communicate with the TAC group The TAC Xenta group is a simpleway to build a hierarchy of the Xenta units for example when a presentation system like TAC Vista is connected to a LonWorks net The communication is handled by a Group master The Group master has the
19. together with LM3 6 4 2 TAC Xenta 400 I O modules When TAC Xenta 300 401 is installed using LM3 it is not possible to address the I O modules in TAC Menta NCT using the Service pin as this message is sent on the zero length domain This means that you have to enter the Neuron ID manually when installing an I O module in TAC Menta NCT However if the TAC Xenta 300 401 has not yet been installed with LM3 the Service pin method will work If you wish to program the network off line all XIF files must be available Different versions of the I O modules have different program IDs To match the XIF files with the modules when designing your network off line you must know which version is used in the respective I O modules 6 4 3 TAC Xenta OP How the TAC Xenta OP is treated depends somewhat on the program version Starting with version 3 32 the OP Service menu has been changed Mode TAC INST MAN has replaced Bindable OFF ON 70 88 0 004 7775 1 GB TAC AB 2001 02 15 TAC Xenta and LonMaker 6 Installation of the Units Mode INST orBindable ON nci_config_src 1 Mode TAC nci_config_src CFG_EXTERNAL When TAC Xenta OP is installed in LM3 the variable nci_config_src will be switched from 0 LOCAL to 1 CFG EXTERNAL TAC Xenta OP is addressed using LM3 which means that it must be mounted permanently in a cabinet or similar It must not be moved around in the
20. 1 GB 85 88 TAC Xenta and LonMaker Index R References 51 remote 21 Repeater 63 Replacing a TAC Xenta 400 81 restrictions 7 router 20 30 63 71 S Servicepin 12 65 67 shape 12 17 signal 57 SNVT 45 49 70 74 78 stencil 12 17 subnet 20 subnet node address Subsystem 67 subsystem 12 Synchronize 41 12 68 T TAC 20 71 TAC group 13 48 52 69 TAC Menta network configura tiontool 68 TAC ToolPack for Echelon LonMaker 17 TAC Xenta 100 25 37 73 TAC Xenta 103A 25 TAC Xenta 300 401 69 TAC Xenta 300 401 45 70 TAC Xenta 400 I O mod ules 70 TAC Xenta511 81 TAC Xenta 901 45 49 74 TAC Xenta group 48 TAC Xenta group 13 52 TAC Xenta group 69 TAC Xenta Group master 13 TAC Xenta I O modules 49 TAC Xenta OP 20 49 70 TACNV 69 tag 0 55 tag 1 56 Target 10 57 timer 26 U Unit Maintenance 77 Upload values from device 41 V WebTool 81 Windows2000 8 Visio Technical 11 X XIF file 10 Z Zone Manager 30 86 88 0 004 7775 1 GB TAC AB 2001 02 15 tace TAC talking buildings Head office Finland UK Ireland Poland Singapore For more information come Sweden 358 9 584 25 00 44 1582 81 67 00 48 58 782 00 11 65 748 23 93 and visit us on the Web at 46 40 38 68 50 China Office Germany Austria Norway Russia 86 21 6317 4111 www tac se Subsidiaries Switzerland 47 23 24 40 00 7 095 737 02 26 Denmark 49 208 8 24 86 0 Sweden 45 44 88 12 12 46 8 685 1
21. AB 2001 02 15 TAC Xenta and LonMaker 4 Step by step The TAC Xenta Units Senta 103 Plugein TesthelSubsyshenm Block i Help TAC Xenta 103 Plug in Parameters that relate to the controller itself All entries are limit checked If they exceed the limits a buzzer is heard and you will have to make another try You cannot leave an entry field with an incorrect value in it For some nci s this check has been extended to cover other dependent nci s One example nciDamperMinPosn is checked so that its value does not exceed the nciDamperMaxPosn value etc When you position the cursor above the intended entry field an InfoTip appears presenting a short descriptive text for the current variable TAC AB 2001 02 15 0 004 7775 1 GB 43 88 TAC Xenta and LonMaker 4 Step by step The TAC Xenta Units ITAL Senha 103 Plug in Testhet Subsystem 1Flonr 3 Xenia 10539 Black 1 Gereral Hardware Controller noes tis D Operasion mode Aem 2 Staus moallaemStatus Alarm configuration meo tectiiceup Devising zone hernperabune ncispace empLow 35 Application made Low zone bempsatue nr amp paceTempDey 20 High carbon damde level D pic Skea Adaptation of themistar does net work T Slava mods enable Bound variables not received Hot vald value cn input
22. Files section 2 6 Several integration tools used simultaneously Several persons may work simultaneously on the same network All persons not working on the PC with the LNS Server are running remotely This requires however that the network is connected and that you run in a remote mode either via TCP IP Remote Lightweight Client or via the LonWorks network Remote Full Client However only one user at a time is allowed access to a specified Visio file This file must reside on the corresponding PC and allows for example only addition of nodes whose XIF files already exist no import of any new XIF files For more information please study the LonMaker User s Guide chapter 2 section Using the LonMaker Tool Remotely TAC AB 2001 02 15 0 004 7775 1 GB 21 88 TAC Xenta and LonMaker 2 Preparations Blank page 22 88 0 004 7775 1 GB TAC AB 2001 02 15 TAC Xenta and LonMaker 3 Step by step The Network 3 Step by step The Network 3 1 Create a new network To create a new network you begin by starting LonMaker Drawing fmt A4 or US Letter Click on the Options tab and select which background picture Template for new networks you prefer If you check the Exit Design Manager after launching Visio box you will not have to close the dialogue window manually Click Apply to execute Echelon LonMaker x General Options Set LonMark Resource Files Languages
23. Scope Filters All subsystems Channels C The current subsystem and its dependent subsystems Device Templates The current subsystem only sinus NOTE All routers should be installed and Wink Interval 5 Seconds commissioned prior to using this feature JV Match using location string IV Display location as text Include devices with unknown programs Discover configured devices Allow channel override Cancel Help Device Selection Scope Decide if you want to work with The current subsystem only or The current subsystem and its dependent subsystems If the units reside on the other side of a repeater or a Router configured as a repeater you may in Options have to checkmark the box Allow channel override 66 88 0 004 7775 1 GB TAC AB 2001 02 15 TAC Xenta and LonMaker 6 Installation of the Units Options Checkmark the boxes Match using location string Display location as text and Enable service pin matching Select Devices to be Commissioned E x Discovered Devices Defined Devices Neuro Channel Template Location Discover Subs Name Chan Template Location 1 01005 Backbone OP Subsy Zone Chan ZoneMa Vink Subsy 421 Chan X420w02 Subsy X451 Chan X450w03 Exclude Exclude gt 4 gt Match Devices to be Commissioned Subsystem Name Channel_ Template Location Neuron Remo
24. TAC Xenta and LonMaker 5 Step by step Bindings Device Properties Attributes Self documentation Functional Blocks Device Name Basic Properties Address Table Advanced Properties Identifiers Network Yariable Contig ZoneManager1 IE eo Yes Yes No No No No Group 0 096 0 048 Member Group 0 096 0 048 Member SubnetNode 4 2 3 0 096 0 048 Unused Unused Unused In TAC Xenta 300 401 index 0 is reserved for the TAC group while index 1 is reserved for the TAC Xenta group Had the TAC group been the first group binding performed in the LonMaker project tag_0 this binding would have got group address CID 0 In the example above TAC group received group address 3 To protect these group addresses during work with TAC Menta NCT there is in TAC Menta NCT under Alternatives Settings a check box Download group addresses Deselect this box in order to leave the group addressing to LM3 Configuration x Delay for restart in seconds TAC AB 2001 02 15 0 004 7775 1 GB 53 88 TAC Xenta and LonMaker 5 Step by step Bindings Bindings for the TAC Group Bindings to crate the TAC group are made in the following way Add a virtual Function Block to all TAC Xenta 300 401 units New Functional Block Wizard Ss ESS cun 722 29 ae Ventilation H Select the virtual Function Blocks ri
25. Windows User s Guide please refer to section 1 3 below Our manual describes primarily procedures recommended by TAC and facts that should be known when installing TAC Xenta products For LonMaker standard procedures we will in the succeeding chapters refer to the corresponding information in Echelon s manual We build on a specific example and will show how this is implemented from the initial system considerations via network configuration to the commissioning and certain types of maintenance A basic idea is to use as much as possible Templates in LM3 to decrease the amount of data that has to be manually entered This applies primarily to the controllers in the TAC Xenta 100 series and to the I O modules in the TAC Xenta 400 series 1 2 Scope and restrictions The descriptions in this manual are valid for the following products and releases TAC Xenta 100 v 1 10 TAC Xenta 301 and 302 v 3 2 hardware type 2 TAC Xenta 401 v 3 2 TAC Xenta OP v 3 0 or later TAC Xenta 41x I O modules v 1 02 04 TAC Xenta 42x I O modules v 1 02 04 TAC AB 2001 02 15 0 004 7775 1 GB 7 88 TAC Xenta and LonMaker 1 Introduction Note TAC Xenta 45x I O modules v 1 02 04 TAC Xenta 471 I O modules v 1 00 04 TAC Xenta 49x I O modules v 1 00 02 TAC Xenta 511 Web Server for LonWorks network TAC Xenta 901 Serial LonTalk adapter TAC Menta v 3 24 TAC Vista v 3 1 e LonMark certified foreign z
26. certain things as these will invalidate you current PC Key You are not allowed to delete or decommission commissioned units or merge networks You may however add or commission new devices or delete devices that are not currently commissioned Should credits be lost due to mistakes node corrections or similar they may be regained through a Replacement Order TAC AB 2001 02 15 0 004 7775 1 GB 19 88 TAC Xenta and LonMaker 2 Preparations 2 4 Restrictions when using LM3 2 4 1 TAC Xenta OP INST MAN TAC The idea with using LNS LonWorks Network Services is to have an open system To achieve this all nodes must be registered in the LNS database This means that all units which are connected to the network also Operator panels and I O modules must be addressed and installed using LM3 For TAC Xenta OP with system program version below 3 32 we recommend that you always install the OP A considerable drawback with this is that the OP can no longer be moved around in the network In stead it must belong to a specific subnet or rather a channel As the same subnet number may not appear on both sides of a router this means that a specific OP can never be used on more than one channel that is on one side of the router Therefore the OP should be mounted permanently in a cabinet or similar An OP TAC mode see below which only is connected to TAC Xenta 100 controllers can of course still be
27. functions part no 0 004 7647 e TAC Vista 3 21 Communication LonWorks part no 0 004 7585 e TAC Vista 3 21 Database generator part no 0 004 7578 e TAC Vista 3 21 Colour graphic editor part no 0 004 7576 For a description of the interface between TAC Vista and the network LonTalk Adapter please refer to the corresponding product documents TAC AB 2001 02 15 0 004 7775 1 GB 9 88 TAC Xenta and LonMaker 1 Introduction 1 4 Terminology Bindings Hub Target Program ID Location String Acronyms LNS LonWorks Network Services LM3 LonMaker Tool Release 3 HMI sometimes MMI HuMan Machine Interface FBD Functional Block Diagram XIF file eXternal Interface File vsd Visio drawing file vst Visio drawing file as template VSS Visio stencil files NCT Network Configuration Tool for example the TAC Menta NCT WebTool Programming tool from TAC to design a supervisory presentation system in the TAC Xenta 511 unit Concepts To be able to send a value from one unit to another on the network you must perform a binding hence Binding tool By defining one or several bindings you will establish a signal path between two or more units Hub is the name of that end of the signal path which is alone in sending or receiving Target is the name of the opposite end s When sending from one unit to one other unit these designations loose their meaning Each LonMark product ha
28. have several rooms per page The finer the subdivision the greater the possibility to use copies Do not forget that Visio supports commentary texts make free use of comments so the design will be easy to understand Remember also that it is often better to comment why not exactly how as the latter often is obvious from the picture On the next page we show an example on the layout of the demo example network TAC AB 2001 02 15 0 004 7775 1 GB 31 88 3 Step by step The Network TAC Xenta and LonMaker 92 10014 92 9 21 EZA zzy 9 1 gec 10014 gz 20014 9 1 82 sews 1 210014 gz gz 11 W 220014 es Ls Q C z 1001547 ge 2 10014 auoqpeg jeuueYD Z jauUeYD 09 X Ocv X WUeAX omv 20014 sey Ley 10014 E 10014 S vt Dg GL VE auoqyoeg
29. made units select the respective TAC Xenta I O module the remaining procedures are the same as for TAC Xenta 300 401 As there are no network variables in the TAC Xenta I O modules you do not have to add any functional blocks for these 44 TAC Xenta OP Unit with Shape Use Drag and drop technique to put the TAC Xenta Operator panel on the drawing There is a ready made unit the rest is the same as for TAC Xenta 300 401 As there are no bindings to the TAC Xenta OP you do not have to add any functional blocks 4 5 TAC Xenta 901 Device unit Use Drag and drop technique to put the TAC Xenta 901 unit on the drawing There is no ready made unit handle according to TAC Xenta 300 401 As it is not possible to make bindings to TAC Xenta 901 no function block is needed TAC Xenta 901 has the same program ID as a Xenta 300 401 with an application without SNVTs So in those cases where a Xenta 300 401 is already installed you may get a message that the corresponding Device Template already exists This has no adverse effects but shows that this type of Device Template should be given a neutral name please refer to en earlier section of this chapter concerning TAC Xenta 300 401 TAC AB 2001 02 15 0 004 7775 1 GB 49 88 TAC Xenta and LonMaker 4 Step by step The TAC Xenta Units 4 6 Entering the Neuron ID Location String Neuron ID Location String If the Neuron ID for network nodes TAC Xent
30. network The Echelon LonMaker Browser is used to show and modify current values for the network variables of the units The Echelon LNS Report Generator is used to create documentation from the database All object data will be included so some editing for example in Excel may be required The 7AC Xenta 100 Plug in is conveniently installed with the installation kit TAC ToolPack If any type of TAC Xenta 100 is used in the network make sure that the TAC Xenta 100 Plug In is registered Should it be missing in the current network move the cursor to the toolbar select LonMaker Network Properties click on the Plug In Registration tab look up the required Plug In and click on Add to have it registered TAC AB 2001 02 15 0 004 7775 1 GB 25 88 TAC Xenta and LonMaker 3 Step by step The Network Note Before you move on you should check mark the box Continue with advanced options It may be convenient to check mark Skip this prompt when Network Wizard Already Registered Echelon LNS Report Generator Version 3 00 Echelon LonMaker Batch Commissioning Utility Version 1 1 Echelon LonMaker Browser version 3 00 Remove Echelon LonMaker Device Report Generator Version 1 1 TAC Xenta 100 Plug in Version 1 1 The Set LonMaker Resource Files Languages window is passed with a click on Next gt Network Timing Retries This is where you enter different transmit and retr
31. network as you then may risk that the OP with its old subnet number will be put on another channel The same subnet number must never appear on both sides of a router as the router then will stop communicating e You cannot use a permanently installed OP with the TAC Xenta 100 units as the TAC Xenta 100 unit will send out a Service pin message when the OP is connected electrically to it This is done in order to find out which unit the OP communicates with As the OP does not belong to the zero length domain no contact will be established When the OP is connected electrically to a TAC Xenta 100 unit the OP will first wait for the operator to press Enter if none appears the OP will start looking for a TAC Xenta 300 401 as a server However this request will be sent on the zero length domain As the units of an LNS network are only installed in one domain no unit will answer and the OP will show No Answer Bindable OFF 0 CFG LOCAL This mode requires that the TAC Xenta OP has not been installed with LM3 which means that the variable nci config src is not affected This is the only mode that can be used when TAC Xenta OP is to communicate with a TAC Xenta 100 TAC Xenta OP will now get its address from a TAC Xenta 300 401 meaning that you always have to reserve the two succeeding node addresses of a TAC Xenta 300 401 This is done when you build the network by adding two dummy nodes each time you have inclu
32. to the correct channel Specify the Transceiver Type of the channel TP FT 10 for all TAC Xenta units and its Name as stated earlier Now the unit itself but also its function blocks with all the bindable variables will be placed in the drawing please turn the page TAC AB 2001 02 15 0 004 7775 1 GB 37 88 TAC Xenta and LonMaker 4 Step by step The TAC Xenta Units Ate Page 3 of 3 in the drawing file After just a few units the page will become cluttered Try to spread the blocks over the surface so that there will be room also for the intended bindings Create new pages as needed keeping a suitable hierarchy grouping in mind After about 10 pages at most it is time to create a new Visio file In LM3 it is possible to bind also to nci type variables configuration parameters If you wish to bind to one in TAC Xenta 100 you must add a new functional block of the type Virtual Functional Block please refer to the next page Note Do not forget that nci often is stored in the flash memory or in EEPROM In that case you must not let the variable be frequently written into as these kinds of memory only stand a certain number of write procedures 38 88 0 004 7775 1 GB TAC AB 2001 02 15 TAC Xenta and LonMaker 4 Step by step The TAC Xenta Units New Functional Block Wizard x Select Device and Functional Block Instance So
33. will compare the entered text string with the unit s own string That is the reason why it is important that the string is entered Location ASCII below exactly as it appears in the NCT iNew Device Wizard 46 88 0 004 7775 1 GB TAC AB 2001 02 15 TAC Xenta and LonMaker 4 Step by step The TAC Xenta Units Functional Blocks Use Drag and drop to add functional blocks for the TAC Xenta 300 units to the drawing The free programmable Devices have no ready made function blocks in stead you will have to use the general functions of LM3 Drag a Functional Block to the drawing and you will start the New Functional Block Wizard New Functional Block Wizard E xl Select Device and Functional Block Instance Source FB Name Func Block 1 FB Type Subsystem Name Subsystem 1 Floor 3 Roof Browse Device Type ZoneM anager2 Name ZonM anager r Eunctional Block Type Controller object ID Name Controller 1 v Check that the function block that you add indicates the correct unit look in the Device box the Name field As TAC Xenta 300 401 has all its network variables in the Controller object you must also check that in Functional Block the field Name specifies the Controller 1 object TAC AB 2001 02 15 0 004 7775 1 GB 47 88 TAC Xenta and LonMaker 4 Step by step The TAC Xenta Units New Functional
34. 1 00 rw TAC develops manufactures and markets system solutions products and software for the control and supervision of tace li 1 i building services systems via open integrated systems intended for use by customers looking for optimum indoor m comfort safety and operating costs TAC has about 2000 employees with subsidiary companies in the Nordic countries the UK Germany Poland and Singapore complemented by partners some 70 countries Mge
35. Block Wizard As we when creating the network checkmarked Enter Functional Block Name FB Name Include device name in default FB name we can use the suggested name of the function block FB Name FB Type Controler object Number of FBs to Create Choose A Network Yariable B xl EN Use the general functions of LM3 select Input Network Variable or Output Network Variable Please select the network variable s you wish this shape to represent Selecting multiple network variables will result in shapes being automatically dropped Cancel nvi Flow amp ulaS1 nvi_FlowAulaS2 nvi_FlowAulaS3 nvi FlowCafeteri nvi Flow CloakRm nvi FlowkKitchen nvi_FlowMeetingR Select All nvi_FlowRecept nvi space temp Help Md Remove prefix from NY names v Remove array subscripts from NY names Now you either select only those variables that you will use for bindings or you save trouble and time by clicking on Select All In order to create the TAC group and the TAC Xenta groups you have to add Functional Blocks of the type Virtual Functional Block This is done in the same way as before although you do not have to define any network variables 48 88 0 004 7775 1 GB TAC AB 2001 02 15 TAC Xenta and LonMaker 4 Step by step The TAC Xenta Units 43 TAC Xenta l O modules Units with Shapes Use Drag and drop technique to put the TAC Xenta I O modules on the drawing There are ready
36. Device Template Current Template Device Name s ZonM anager External Interface Definition Upload From Device Existing Template LoadXIF File Browse Template Name Name AppDevice_88 External Interface Definition For a new type of device mark Load XIF and enter the search path for the XIF File generated by TAC Menta Also specify a suitable Template Name Remember that for Xenta 300 401 and for TAC Xenta 901 with applications missing SNVTs they will all have the same XIF file This means the units will have the same Template Name a reason to give it a neutral name If you have a unit which uses the same XIF file as one already installed you select of course Existing Template and its Name TAC AB 2001 02 15 0 004 7775 1 GB 45 88 TAC Xenta and LonMaker 4 Step by step The TAC Xenta Units Channel Auto Detect Check that your installation will be 9 connected to the correct channel Device Properties For TAC Xenta 300 401 with system program version 3 4 or higher you can specify a Location String that is the last six characters of the unit name stated in TAC Menta NCT This will make it easier for to identify the respective units during the installation procedure Please note that the TAC Xenta unit automatically will use the last six characters of the unit s name for the Location String and that LM3
37. FROM TAC Order Department Email order tac se Fax 46 8 500 101 96 please use email if available SUBJECT Application Key Generation Report DATE 2000 04 11 15 26 21 Thank you for your order It has been successfully processed gt Your Application Key is E1FB 86D7 6F84 CC88 79A0 5EBB 92 Please use your License Wizard to enter the Application Key and view a report on the upgraded license Order Summary PC Key DFBB E4DC 7646 3D7B E8 ADFA 79A9 4363 354F 18AD FD16 A943 60EA 4F18 2DF9 91AA 3050 Product License LonMaker Serial Number 9947B73 04673 Credits Added Item Number 9 008 0003 0 Number of credits ordered Add 50 gt Number of credits charged 50 Price Each Subtotal Resulting Features ID 4 Standard Features Subtotal Total Price Credits Features This order was processed by Administrator ID N N TAC AB 2001 02 15 0 004 7775 1 GB 83 88 TAC Xenta and LonMaker Appendix Application Key Blank page 84 88 0 004 7775 1 GB TAC AB 2001 02 15 TAC Xenta and LonMaker Index Index Special characters ndb 81 vsd 10 vss 10 vst 10 XIF 11 A4 23 Acronyms 10 Ad hoc mode 25 Application Key authentication 29 B backup 21 77 bindasignal 57 Bindable 71 binding 80 bindings 10 broadcast meddelande 59 C Changing the application 78 Concepts 10 Configuration parameters 11 configuration parameters 11 Connector 51 Credit
38. Lp iil LONMARK LonMaker TAC Xenta and LonMaker Release 3 0 004 7775 1 GB 2001 02 15 tac TAC Xenta and LonMaker Forword Forword Welcome to the manual of TAC Xenta and LonMaker release 3 Should you discover errors and or unclear descriptions in this manual please contact your TAC representative You may also want to send an e mail to helpdesk tac se This manual describes the recommended method of procedure when designing LonWorks networks based on TAC Xenta controllers from version 3 2 using Echelon s binding tool LonMaker Release 3 often abbreviated LM3 This edition 1 uses version 3 0 of this tool described in the LonMaker User s Guide Release 3 published by Echelon Co USA part no 078 0168 02D The manual assumes that the reader is familiar with the products and their use The page numbering is continuous in stead of chapter based TAC AB 2001 02 15 0 004 7775 1 GB 3 88 TAC Xenta and LonMaker Forword Copyright 2001 TAC AB This document as well as the product it refers to is only intended for licensed users of the product and the document TAC AB owns the copyright of this document and reserves the right to make changes additions or deletions TAC AB assumes no responsibility for possible mistakes or errors that might appear in this document Do not use the product for any other purposes than those indicated in this document
39. Neuron Id has not been set Subsystem 1 Xenta511 Error communicating with device Subsystem 1 Flo Light Neuron Id has not been set VN NN ow gt Save As Summary includes 7 device s and 0 router s Cancel Help Click Get Now to examine the network If everything is on line and working you will only get a text Summary includes telling you the number of nodes and routers that have been checked If there are problems the corresponding node will be shown in the lower window with a text indicating the type of problem In the upper window the status of the Functional Blocks is shown As this is not supported by TAC Xenta all TAC Xenta units will show Error accessing LonMark Object For other nodes than TAC Xenta this may indicate a problem for TAC nodes it can be ignored TAC AB 2001 02 15 0 004 7775 1 GB 75 88 TAC Xenta and LonMaker 6 Installation of the Units Blank page 76 88 0 004 7775 1 GB TAC AB 2001 02 15 TAC Xenta and LonMaker 7 Unit Maintenance 7 Unit Maintenance 7 1 System Backup and documentation As was mentioned in section 2 5 we strongly recommend regular backups of all information about the network connected units and their settings This is specially true when you are about to modify something in the network so that it will be easy to restore the earlier working status In LMG you may specify if the back up applies to the database and or
40. Xenta and LonMaker 6 Installation of the Units 6 4 4 TAC Xenta 100 Note When the OP is connected electrically to a TAC Xenta 100 unit the OP will first wait for the operator to press Enter if none appears the OP will start looking for a TAC Xenta 300 401 as a server However this request will be sent on the zero length domain As the units of an LNS network are only installed in one domain no unit will answer and the OP will show No Answer If a TAC Xenta OP is no longer used in an LNS network it must be deconfigured according to the following System program lower than 3 32 Start the LM3 Browser Look for SNVT config src labelled var 2 in the browser with rightclick and Properties the name will become visible Reset SNVT config src manually from 1 CFG_EXTERNAL to 0 LOCAL Check that Bindable OFF in the Xenta OP Service menu Disconnect the OP electrically Remove the OP from the LM3 data base System program 3 32 or higher Check that Mode MAN in the Xenta OP Service menu Disconnect the OP electrically Remove the OP from the LM3 data base The next time that the TAC Xenta OP is powered up it will automatically reset nci config src to LOCAL If you wish to program the network off line you must get the XIF file for the OP from TARAI or other source To start up local zones before the network is connected it is possible to set up the ma
41. a or others are known these may be entered in advance without connecting the nodes or installing them on the network For TAC Xenta 300 401 with system program version 3 4 or higher in stead of the Neuron ID you can already in the Device Properties section 4 2 specify a Location String to identify the respective units Please note that it is the last six characters of the TAC Xenta 300 401 which are used as Location String Entering the Location Strings or the Neuron IDs in advance will facilitate the commissioning Engineering Mode that is not connected to the network Right click on the unit and select Commission Should a warning Offnet appear it can be clicked away Commission Device Wizard Device Identification Method Device Name s FonManager Service Pin Manual Neuron ID 01001D436000 Enter the current Neuron ID using a bar code reader or the PC keyboard Ad hoc Mode that is connected to the network To enter the Neuron ID without installing the node presently you select from the tool bar LonMaker Network Properties click on the sheet Onnet Offnet and specify Offnet Now right click on the unit select Commission and enter the Neuron ID according to the example above Finish the procedure by returning to the Onnet Offnet sheet and specify Onnet again 50 88 0 004 7775 1 GB TAC AB 2001 02 15 TAC Xenta and LonMaker 5 Step by step Bi
42. all network variables except the configuration parameters are available The file TAC Xenta 400 series vss contains the corresponding data for TAC Xenta OP and I O modules The file TAC Xenta 400 older vss contains shapes for older versions of the I O modules It can be opened in Visio with File Stencils Open Stencil Select TAC Xenta 400 older vss and open Now LonMaker should be ready for use TAC AB 2001 02 15 0 004 7775 1 GB 17 88 TAC Xenta and LonMaker 2 Preparations 2 3 LonMaker Credits To be allowed to use LonMaker you must acquire a number of Credits With the original license there are 64 Credits normally enough to build a medium network Credits are not used for Routers nor for testing or educational purposes No of available Credits Go to the tool bar and select LonMaker LonMaker Credits Info LonMaker Credits Info Available Credis 63 Close Help Available Credits shows the number of remaining Credits Order more Credits More Credits can be ordered from TAC in the following way The first time open the file orderfrm txt in the LonWorks folder normally in c LonWorks LonMaker At the FROM section enter your address phone no etc These items will then accompany all your future orders Click on Add Credits in the window above LonMaker License Wizard e LonMaker Credit Info Credit Order Max B Enter number of credits Cr
43. cking on Finish After this you will enter the drawing program Visio with a drawing showing the network interface that is your PC connection to the network Foi 2 ard Goat Flare 2 rj Fiy and Basement m Backing T E ja aj A Visio drawing showing the computer network interface However there are still some network items that have to be specified Go to the tool bar under LonMaker Network Properties where you will find the sheets Authentication and Domain see next page 28 88 0 004 7775 1 GB TAC AB 2001 02 15 TAC Xenta and LonMaker 3 Step by step The Network Network Properties BOW Sty DIGVVSEP Authentication Should any of the units for example a door lock system need authentication then checkmark the box Enable Authentication Domain Definition Indicate how the current domain is to be defined Entered values are normally used in TAC networks After this you press Finish It is now time to build the network with its channels routers and application nodes In the remaining part of this chapter we will show a small demo example a minor Zone system and how its layout may be arranged in the Visio drawing program TAC AB 2001 02 15 0 004 7775 1 GB 29 88 TAC Xenta and LonMaker 3 Step by step The Network 3 2 Network demo example Our example is designed with two TAC Xenta 300 to control heating and ventilation one TAC Xen
44. ded a TAC Xenta 300 401 letting the dummy nodes get the addresses immediately after Always check the addresses when you have changed application in a TAC Xenta 300 401 or when units have been replaced TAC Xenta OP may now be moved around in the network as it will get its address from a TAC Xenta 300 401 However the great disadvantage with this procedure is that You have to enter two dummy nodes directly after each TAC Xenta 300 401 TAC AB 2001 02 15 0 004 7775 1 GB 71 88 TAC Xenta and LonMaker 6 Installation of the Units You have to check addresses when changing application in TAC Xenta 300 401 as LM3 may assign the unit a new Subnet Node address You have to check the addresses when replacing TAC Xenta 300 401 units as LM3 may assign the unit a new Subnet Node address Before the TAC Xenta OP gets its address from a TAC Xenta 300 401 unit it will automatically belong to the zero length domain When OP is electrically connected to a TAC Xenta 100 unit the OP will wait for the operator to press Enter if none appears the OP will start looking for a TAC Xenta 300 401 as a server This request will be sent on the zero length domain As the OP in this case belongs to the zero length domain communication can now be established between TAC Xenta OP and TAC Xenta 100 Mode MAN Only for TAC Xenta OP version 3 32 or higher This mode requires that the TAC Xenta OP has not been installed
45. edits Deficits to add Credits fs Deficits 0 so Available Remaining Welcome to the LonMaker License Wizard The information below shows the current usages for this license Click Next gt to purchase additional credits Days Unlimited v Keep used credits recommended Remaining Enter the required number Credit Order even multiples of 10 a minimum of 50 and click Next 18 88 0 004 7775 1 GB TAC AB 2001 02 15 TAC Xenta and LonMaker 2 Preparations LonMaker License Wizard Based on the serial number of your PC and internal ID information a key is generated PC Key which is unique for your computer By clicking on Copy to Clipboard you will get a form with this and all other relevant information all ready to be pasted into a suitable document later to be sent via fax or e mail to the order dept of TAC The form contains your required number of Credits Also check the applicable order options of the form An example on this form is shown in LonMaker User s Guide At TAC a license key an Application Key will be generated and returned Please refer to the example in the Appendix of this manual By copying the key into the field Application Key on the same PC and clicking Finish your Credits will increase by the ordered number Note 1 Waiting for Credits Note 2 Lost Credits Before the new Application Key has been received you are not allowed to do
46. ght click and select Connect 54 88 0 004 7775 1 GB TAC AB 2001 02 15 TAC Xenta and LonMaker 5 Step by step Bindings Point on any Hub and the variable tag_0 Select target specify the same variable tag 0 for all TAC Xenta 300 401 units of the network Message Tag Connection x OK Subsystem 1 Floor 3 Roof Help Ei XVentilation E Func Block 1 Addi Fad AT Default Connection Description As this binding was the first made in this network it was assigned group no 0 Specify this in TAC Vista TAC AB 2001 02 15 0 004 7775 1 GB 55 88 TAC Xenta and LonMaker 5 Step by step Bindings Bindings for the TAC Xenta Groups Again select the virtual Function Blocks but this time only to bind the units of the first TAC Xenta group Rightclick and select Connect Point to Hub preferably the Group master and the variable tag_ Then select Target specify the same variable fag 7 for all TAC Xenta 300 401 units of the first TAC Xenta group Message Tag Connection Hub Subsystem 1 Floor 3 Roof X VentilationfFunc Block 1 _1 EQ Xventilation E Func Block 1 i msa in Graphics Normal Use References Show Connections Selected Connections Selected Connection Targets Between Selected FB SNs From or To Selected FB SNs Default Connection Description Properties Assion Connec
47. group with a special group address Communication from TAC Vista and the transmission of TAC NV values between units of different TAC Xenta groups occur using this group address The transmissions of TAC NVs between units of the same TAC Xenta group use the respective TAC Xenta group no Also the TAC OP uses these group addresses To build the TAC group you must perform a binding between all TAC Xenta 300 401 units of the network To build a TAC Xenta group you must perform a binding between all TAC Xenta 300 401 units of that group TAC groups and TAC Xenta groups must not be in 100 accordance with each other Should this be the case you must add a dummy node to one of the groups in order to produce two different group bindings This dummy node must be of the TAC Xenta 300 401 type The first group binding gets group address 0 and then in ascending order In order to determine which address a group binding will get you must see to that this binding is made first of all In practice this may be difficult to achieve so to find out which group addresses the bindings received you can do as follows If you click right on a unit in on line mode and select Device Properties you can under the header Address Table see the address table of the unit containing information about messages to and from the unit In the column JD you will find the current group address for the binding 52 88 0 004 7775 1 GB TAC AB 2001 02 15
48. ht now then specify them as Repeaters otherwise you will get no contact between the channels Click right on the router select Properties Router Properties X Attributes Identifiers Basic Properties Advanced Properties Butters Specify Advanced Router Properties Router Name RTR 3 Router Type Configured Authentication Y Priority Channel 1 Priority Channel 3 Disable Disable Enable Automatic Enable Automatic Enable Manual Slot fe Enable Manual Slot fe Under the tab Advanced Properties you will find the settings for the type of router you have got TAC AB 2001 02 15 0 004 7775 1 GB 63 88 TAC Xenta and LonMaker 6 Installation of the Units 6 2 The TAC Xenta units 6 2 1 One unit at a time If you are to install occasional units then open the subsystem where the unit is defined click right on the unit and select Commission As the TAC Xenta units are Host based that is the application does not reside in the neuron but outside you are not to download the application via the network management tool Note Consequently do not checkmark the Load Application Image box Commission Device Wizard DIOvVVSe 64 88 0 004 7775 1 GB TAC AB 2001 02 15 TAC Xenta and LonMaker 6 Installation of the Units State Determine what State the unit should have directly after the installation Also specify which val
49. ice and Functional Block At Target only NVs of the correct type will appear that is the same types as selected for Hub Click on Add to add the binding If necessary select a new Target to bind the same signal to more units Do not forget to Add each new one TAC AB 2001 02 15 0 004 7775 1 GB 57 88 TAC Xenta and LonMaker 5 Step by step Bindings Network Variable Connection Hub Floor 3 Roof ZoneManager1 Func Block 1 nvi_FlowAulaS1 If you select a signal and click on Add All the corresponding binding will be made for all the selected units to NVs that have that same name Do not forget however to check under Connection that the correct signal was selected before you apply the binding by clicking OK If the bindings appear on the same page you may use Graphics Normal If the units reside on different pages the binding will automatically be done using references Use References Did you miss some nodes that also were to receive the same signal Then click on Add FB SNs and select the specific Function Blocks now checkmark those Function Blocks x OK Cancel Subsystem 1 Floor 2 Offices H Q otfice2 1 Help gy Func Block 1 Subsystem 1 Floor 3 Roof Edd Ventilation Func Block 1 Add All ZoneManager1 Func Block 1 nvi Flow amp ulaS1 Add FB SNs nvi Flow amp ulaS2 nvi Flow amp ulaS3 Graphics nvi FlowCafeteri
50. in parameters using the OP This works only if TAC Xenta 100 has been set up as Configured If you want to keep these parameters at future downloads you must save them in the data base for LM3 or TAC Vista After the most important parameters have been set the subnet node addresses cannot be changed Xenta 100 must be reset to the Unconfigured state Otherwise conflict will arise with all remaining units which have the same subnet node address 1 1 factory set If you get addressing problems already when using the OP you may set the OP as bindable as the communication with TAC Xenta 100 then will use the Neuron ID TAC AB 2001 02 15 0 004 7775 1 GB 73 88 TAC Xenta and LonMaker 6 Installation of the Units 6 4 5 TAC Xenta 901 e TAC Xenta 901 uses the same Device Template as TAC Xenta 300 401 with no SNVTs in the application Therefore you may be asked if you wish to rename the Device Template file when adding a unit As it should be easy to detect which unit uses which Device Template your answer will depend on the circumstances 6 4 6 Status Summary In the LonMaker Status Summary window an overview is displayed showing the status of the units installed in the network Among things reported are units without Neuron ID that is units that have not yet been commissioned units off line etc Status Summary Options Scope C Subsystem Page v In Override Set All S
51. inding This means that a broadcast requires a larger bandwidth than a normal binding If the broadcast crosses several Subnets it may become a Domain broadcast reaching the whole network TAC AB 2001 02 15 0 004 7775 1 GB 59 88 TAC Xenta and LonMaker 5 Step by step Bindings Working method 1 Choose those nodes between which you wish to bind rightclick and select Connect i Network Variable Connection Subsystem 1 Floor 2 Offices Subsystem 1 Floor 3 Root ge Ada All Normal fe Use References Unacknowledged 2 Under Connection Attributes New Connections select Unacknowledged Click on the Properties button 60 88 0 004 7775 1 GB TAC AB 2001 02 15 TAC Xenta and LonMaker 5 Step by step Bindings Connection Details SULGHTeGell apy nese CONTE GEH GTI ELE SEG OT OTLUTT E Gorin ect Gres 3 Select the New button New Connection Description Broadcast message 4 Assign a name to the new binding type click OK 5 Thenclick on the Advanced button TAC AB 2001 02 15 0 004 7775 1 GB 61 88 TAC Xenta and LonMaker 5 Step by step Bindings Advanced Connection Details tomato tomatic m huma haac 2 automatic m 5 Under Use Broadcast select Yes click on OK Back to the Network Variable Connection window you select the new binding type under Connection Attributes New Connections
52. information about which TAC Xenta units are on line or off line and forwards this to the presentation system The TAC Xenta groups are also used in TAC Xenta OP TAC Xenta groups must not span Routers TAC Xenta unit which in TAC Menta is appointed to be group master for the information exchange between the Xenta group and TAC Vista TAC AB 2001 02 15 0 004 7775 1 GB 13 88 TAC Xenta and LonMaker 1 Introduction Blank page 14 88 0 004 7775 1 GB TAC AB 2001 02 15 TAC Xenta and LonMaker 2 Preparations 2 Preparations 2 1 Windows environment 2 1 1 Project library LonMaker Network Management Tool must be installed All work files should also be put in a project library structured something like the one below Current project Files for TAC Vista TAC Menta Command file Network configuration ir a 7 log 7 D Description and Xenta100 XIF files for the TAC Xenta 100 units 3 1 1 1 Application dependent files Copy these XIF files C LonWorks Import TAC Files for LonMaker created at the XIF files for the installation TAC Xenta 100 units ToolPack XIF files for TAC Xenta OP and so on Suggested project library for XIF files and other working files TAC AB 2001 02 15 0 004 7775 1 GB 15 88 TAC Xenta and LonMaker 2 Preparations 2 1 2 Decimal symbol LonMaker assumes that the dot is used as the decimal symbol This is
53. ing Cooking vale Heating value 4 Enable e Ense E Enable nciDsmperMinPosn Output Actuator type G C Thwmo 300 amp p Tnv C 2 30V zFosn Hamal 1000 5 Open ncHeatActstTimel TE Ee OF Xenta 103 Plug in Parameters that relate to the controlled hardware nci values The displayed nci values are fetched from the data base If the nci value in the unit has been changed from for example an OP or TAC Vista the unit s current value will not be present in the data base and cannot be displayed in the Plug in windows To transfer the unit s parameters to the data base Synchronize the Configuration Properties you may if the unit is online right click on the unit select Resync CPs and request Upload values from device Set Configuration Properties Device Office 2 Namefs Cancel Help Operation C Download current values to device mm Reset device to default values TAC AB 2001 02 15 0 004 7775 1 GB 41 88 TAC Xenta and LonMaker 4 Step by step The TAC Xenta Units nvi values nvo values When a nci value has been changed in the Plug in window the Apply button is highlighted As long as the Apply button is highlighted it is a sign that the latest changed nci values have not yet been sent to the database When you press the Apply bu
54. mobile but then it must be connected to the TAC Xenta 100 via the respective room units and must not be connected to a TAC Xenta 300 401 The advantage with installing also the OP is that you no longer have to define dummy nodes to reserve addresses for the OP as it will always have the same address Using TAC Xenta OP with system program version 3 32 or higher it is possible to have a mobile OP In the OP service menu you can select one of three different modes MAN INST or TAC Of these it is recommended that you use the INST mode in a LonWorks network In this mode you can install the TAC Xenta OP and all the nodes of the network will appear in the LNS data base Now the OP will get a fixed address and must not be moved In stead it should be permanently mounted in a cabinet or similar The MAN mode means that you can have a mobile OP the OP will find available addresses on subnet 255 which normally works on both sides of a router without causing problems In this case the OP is not to be installed in LM3 This means however that not all nodes of the network reside in the LNS data base an exception from the principles of an LNS system The TAC mode means that you will have a mobile OP but that you must define two dummy nodes after each TAC Xenta 300 401 Furthermore you must check all addresses when changing application or unit These are reasons why we do not recommend this mode as it generally causes problems later on As
55. ndings 5 Step by step Bindings 5 1 Binding by Connector or by Reference There are different ways of arranging the binding Use Connector to make a direct connection between the corresponding input and output signals However this works only when binding between function blocks situated on the same page Select two or more function blocks click on the first then keep the Shift bar pressed when clicking on the rest click right select Connect In the right part of the window you can now mark Graphics Normal or Graphics Use References Normal means that you will get a line drawn between the function blocks recommended within the same page References means that you will get a number referring to another position in the network where you will find the same number This pair of numbers may be altered to a designation of your own choice References are always used when the function blocks reside on different pages As we already have split up the network into a number of pages we recommend the latter method If the binding lies within the same page use Normal otherwise References TAC AB 2001 02 15 0 004 7775 1 GB 51 88 TAC Xenta and LonMaker 5 Step by step Bindings 5 2 TAC and TAC Xenta Groups in LM3 Group binding Note All TAC Xenta units in a network know the unit names of their own TAC Xenta group and of the other group names All TAC Xenta units belong to the
56. ogramo Ion Description AppDevice 101 9000130210040414 AppDevice 102 9000130500004400 9000130528000400 510 001 300013FFFFOD0000 Imported from P TOOLS MAILBOXIMK tz x101v01 800013501 4060401 Imported from P TOOLS MAILBOXIMK tz x102v02 8000135004060402 Imported from P TOOLS MAILBOXIMK tz x103v04 8000135046060404 Imported from P TOOLS MAILBOXIMK tz 90001 3FFFFO31621 Imported from P LMavViHuset ZM zm xi 900013FFFFO1127E Imported from PALMdWiHusehZMum ny Eun Zm nyare 900013FFFF02185F Imported from PALM4 ViHusetiZMizm Mark Device Templates no longer in use and select Remove Should you mark a Device Template still being used you will get an error message stating that this Device Template is in use and cannot be removed 80 88 0 004 7775 1 GB TAC AB 2001 02 15 TAC Xenta and LonMaker 7 Unit Maintenance Action in TAC Xenta 511 If the selected TAC Xenta 300 401 is part of a network under a TAC Xenta 511 also data in this unit must be updated Please follow the guidelines presented earlier in this chapter After that start WebTool and LNS Explorer under Tools in WebTool and pull in the TAC Xenta 300 401 anew from LNS Explorer to its position in WebTool Add any NVs in TAC Xenta 511 Generate and download to TAC Xenta 511 Start LM3 and replace TAC Xenta 511 in the same way as TAC Xenta 300 401 Perform any required bindings 7 3 Replacing a TAC Xenta 400 I O module
57. ol LonMaker Tool Put the CD with the LonMaker Tool program in the CD reader Select program installation Please note that you do not have to restart the PC before all programs have been installed If you know that you are going to use Echelon s LonPoint modules you will have to install Plug ins for these otherwise we recommend that you postpone the installation until they are needed If you still prefer to install the Plug ins you should be aware that creating new networks for example will take longer time Follow the installation instructions appearing on the screen TAC ToolPack for Echelon LonMaker TAC specific directories and files are generated with an installation kit that can be fetched from TARAI Note LonMaker must be installed first Start the installation of TAC ToolPack for Echelon LonMaker by double clicking on the file Setup exe The first question is a reminder that LonMaker must be installed first TAC ToolPack for LonMaker 1 1 xi Pp This installation requires that the program LonMaker for Windows is already installed on your computer Do you wish to continue DE Follow the installation instructions on the screen When the installation is finished directories and files have been created according to the lower diagram in the figure on the previous page The file TAC Xenta 100 series vss contains stencils with shapes for pre configured TAC Xenta 100 units and function blocks where
58. one controllers Unfortunately an upgrade to LM3 of a system built with other kinds of binding tools often requires major reprogramming LM v 2 cannot be used with Windows2000 whereas v 3 can 1 3 More information The working method follows the guidelines given in the manual e TAC Xenta family v3 Engineering Guidelines part no 0 004 7639 The Integration tool is described in the manual e LonMaker User s Guide Release 3 Echelon Co USA part no 078 01628 02D Information is also obtainable from Internet www echelon com The Drawing tool Visio Technical is described in the manual Using Visio Technical 5 0 Visio Co USA part no 11748 0897 The TAC Xenta 100 controllers are described in a number of data sheets and installation instructions and in the manuals for TAC Xenta 101 part no 0 004 7513 TAC Xenta 102 part no 0 004 7516 TAC Xenta 102 ES part no 0 004 7663 and TAC Xenta 103 part no 0 004 7526 The TAC Xenta 400 I O modules are described in the following documents e TAC Xenta 400 I O modules handbook part no 0 004 7771 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 The data sheet for TAC Xenta 471 C 92 25 The data sheet for TAC Xenta 491 492 C 92 30 e a short installation instruction OFL enclosed with each product 8 88 0 004 7775 1 GB TAC AB
59. room Pentry Conference Office 1 1 Office 1 2 Office 1 3 Office 1 4 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 30 88 0 004 7775 1 GB TAC AB 2001 02 15 TAC Xenta and LonMaker 3 Step by step The Network 3 8 Graphic disposition in LM3 As Visio has a graphical hierarchy you should before creating the network think it through the way the network should appear on paper A general piece of advice is to put at the top the LNS interface one subsystem for each channel At the top of each subsystem we then put supervisory network functions like routers etc and a number of subsystems secondary drawings A subsystem may make up one Visio file alternatively up to 10 subsystems pages may be included in a Visio file You should not include more than ten pages in the same Visio file as this may degrade system performance That is why it is recommended to let each channel have its own Visio file The actual distribution must be considered for each individual case depending on amongst other the final number of nodes If there are several nodes in a room it is convenient to use one page per room otherwise you can
60. s right click on the function block and choose Configure alternatively choose Plug ins If you have selected several function blocks one Plug in for each TAC Xenta 100 will be started As there are several types of controllers in the Plug in for TAC Xenta 100 you must the first time specify the appropriate device type Select appropriate device type r Select type of TAC Xenta 101 TAC Xenta 101 1VF C TACXenta 101 1VFC C TAC Xenta 101 2VF C TACXenta 101 2VFC To use the Plug in for TAC Xenta 100 The dialogue window of the Plug in for TAC Xenta 100 consists of three sheets General Hardware and Controller It is simple to switch between the sheets by clicking on the headers or by using the short commands Ctrl PgUp and Ctrl PgDown The parameters are explained in the respective TAC Xenta 100 Manuals The manuals can be reached via Internet at www tac se Those items in the sheets that miss variable names nci nvi nvo are included as bits of the nciAppOptions and nciSetpoints parameters When the Plug in for a TAC Xenta 100 is started you will get the Hardware sheet The pictures below show the plug in for the TAC Xenta 103A 40 88 0 004 7775 1 GB TAC AB 2001 02 15 TAC Xenta and LonMaker 4 Step by step The TAC Xenta Units E TAC Senla 103 Subsystem tena 10S LIII i4 1 General Hardware Tamper coo
61. s 83 D database 21 decimal symbol 16 device name 28 Device Tem plate 11 49 74 80 domain 12 29 68 71 73 drawing 12 drawing file 12 33 drawing library 21 drawing tool 11 dummy node 52 dummy nodes 20 19 83 E Engineering Mode 25 example 30 external binding tool 68 F FBD 10 Filetypes 12 flash memory 11 38 functionblock 28 47 51 G group address 69 group master 13 H hardware type 1 70 hardware type 2 7 21 70 HMI 10 Hub 10 55 56 57 module 81 INST 20 71 Installation 63 Installation of LonMaker 17 Integrationtool 8 Internet 8 K konfigurationsparametrar 38 L Letter 23 LM3 7 10 LNS 7 10 20 LNS Network Interface 63 Location String 10 46 50 LonMaker Integration Tool Release 3 7 LonPoint module 17 LonTalk Adapter 9 LonTool 68 LonWorks network 7 20 72 master shapes 12 MMI 10 move the commissioning PC 63 N nci 11 38 nci values 41 nci config src 71 nciAppOptions 40 nciSetpoints 40 NCT 10 68 network 23 network configuration too 9 Network Variables 11 network variables 11 Neuron ID 50 65 70 79 81 No Answer 71 73 Node Identification String 10 nvi 11 nvi values 42 nyo 11 nvo values 42 Offnet 25 Onnet 25 12 parameters 73 PC Key 19 PCLTA 30 Plug in 11 17 25 40 Pre configured 81 Preconfigured 68 program ID 10 11 49 66 70 project library 15 TAC AB 2001 02 15 0 004 7775
62. s a Node Identification String also called program ID It consists of eight hexadecimal number pairs and contains information about the program manufacturer product identification program release status and other things Different products carry different program IDs but for a specific product the IDs will differ only if they are loaded with different application programs A text string of six characters mainly indicating where the unit is situated or what purpose it serves As default Location String TAC Xenta 300 401 with system program version 3 4 or higher uses the last six characters of the unit name specified in TAC Menta NCT can use this text string in order to simplify the identification of the specific units on the network Example Floor3apt12 becomes 3apt12 10 88 0 004 7775 1 GB TAC AB 2001 02 15 TAC Xenta and LonMaker 1 Introduction XIF files Device Templates Network Variables nvi nvo Configuration parameters nci Note Plug in Visio drawing tool Available network variables for the unit and its configuration parameters are stored in a XIF file eXternal Interface File When this file has been imported to LM3 it is called a Device Template Also the program ID of the unit is stored here The program ID is used by to check that the unit being installed is of the correct type and version The Program ID must be unique for a specified set of network variables
63. s per file but often it is better to use fewer say 5 6 pages per file Also remember that if several persons are to work simultaneously you will have to work on different files even though you are using a common network database TAC AB 2001 02 15 0 004 7775 1 GB 35 88 TAC Xenta and LonMaker 3 Step by step The Network Blank page 36 88 0 004 7775 1 GB TAC AB 2001 02 15 TAC Xenta and LonMaker 4 Step by step The TAC Xenta Units 4 Step by step The TAC Xenta Units 4 1 Xenta 100 Unit having a Shape 4 1 1 Putting the Unit onto the Drawing Point the cursor on the TAC Xenta 101 unit to the left keep the left mouse button pressed while dragging the cursor to the drawing Release the button and a New Device Wizard will start up Enter Device Name Enter Device Name Enter a suitable Name Device Name Senta 101 You may have to specify the directory path for Template Name 01w02 the respective XIF files Template Name These as mentioned before chapter 2 Number of Devices to Create should be stored in the directory Commission Device C LonWorks Import TAC Working on line you may install the unit Commission Device but this can also wait Specify Device Channel Specify Device Channel Device Name Kenta 101 Auto Detect Specify Channel Xcvr Type 10 Name By Check that the unit will be connected
64. ssessssscsssscssssscsssssscssesssessesssesssesseeseeses 33 4 Step by step The TAC Xenta Units ccssccssssccssscccsssccssssccssssscsssscssssscsssssssssssccees 27 41 Xenta 100 Unit having a Shape e sessesesseseosescsosesoessosossosoesesseseosesoesosoessesossesossesoesessosoessessssess 37 4 1 1 Putting the Unit onto the Drawing eiii et des sagt te tpe od 37 4 1 2 Plug in Tor Xenta 100 teorie e e t e ahead aaa dere 40 4 2 TAC Xenta 300 401 free programmable Device 45 4 3 TAC Xenta I O modules Units with Shapes 1 eee eere esee esee eene enean eene eas toe sette sonata 49 4 4 TAC Xenta OP Unit with Shape eese eese aetas tasses ese teste sete enata 49 4 5 TAC Xenta 901 Device unit ts ta senses enses toissa 49 4 6 Entering the Neuron ID Location String 1 eee eese ee ee eee esee esee entes enean etae toas tae e nette sette 50 TAC AB 2001 02 15 0 004 7775 1 GB 5 88 TAC Xenta and LonMaker Contents 5 Step by step Rx T OL 5 1 Binding by Connector or by Reference csscscscccsscscsccssccscesssssscesssscssccssesscsseesecssecsessseesesseseees 51 5 2 TAC and TAC
65. ta 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 Attic TAC Xenta 300 300 421 451 TAC Xenta 401 401 Ventilation unit XVent Dig Anlg O 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 heating heating heating heating heating heating heating heating heating only only only only only only only only cooling 101 1VF 101 1VF 101 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 Fancoil Fancoil Fancoil Fancoil Fancoil Fancoil 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 2VF 101 2VF Floor Cafeteria Reception Cloak
66. the drawing library A corresponding choice is made when you want to restore your network with the command Restore See also LonMaker For Windows User s Guide chapter 2 the section about Using LonMaker Backup Files To document all objects bindings etc LM3 has an LNS Report generator Please study chapter 7 section The LNS Report Generator of the LonMaker For Windows User s Guide Unfortunately the collected information is hard to survey and possibly too extensive TAC AB 2001 02 15 0 004 7775 1 GB 77 88 TAC Xenta and LonMaker 7 Unit Maintenance 72 Changing the application in TAC Xenta 300 401 If you change the application program in TAC Xenta 300 401 without affecting the SNVTS it will suffice to download the new program from TAC Menta If on the other hand the new application does affect the SNVT contents we have another situation First when you work with LM version 3 only add new SNVTs Do not take away or rename existing SNVTs Should you still decide to do this LM might think that this is a brand new application and so erase all associated function blocks with all their bindings We assume that you have followed our piece of advice and only added some SNVTs Download the new application to the TAC Xenta via TAC Menta At this moment the contents of the LNS database will not be up to date In LM3 click right on the unit select Replace Replace Device Wizard Ju NNNM ZM
67. the reason why it is very important that you let the general settings of Windows specify the dot as decimal symbol Start Settings Control Panel and open the Regional Options The designations may differ slightly between the different Windows versions Under the header Numbers select the dot in Decimal symbol Regional Options 2 x General Numbers Currency Time Date Input Locales Appearance samples Positive 23 456 799 00 Negative 1 23 456 783 00 Decimal symbol Y No of digits after decimal 2 m If the installed Windows has an inherent language different from what you have specified under General Settings for the current user you must also click on Set default to make the change universal Regional Options a 2 General Numbers Currency Time Date Input Locales r Settings for the current user Many programs support international settings for numbers currencies times and dates Set the locale in order to use the standard settings Your locale location Language settings for the system Your system is configured to read and write documents in multiple languages O Arabic Armenian Baltic Central Europe Cyrillic Set default Advanced Apply 16 88 0 004 7775 1 2001 02 15 TAC Xenta and LonMaker 2 Preparations 2 2 Installation of LonMaker To
68. there are routers in the network that are not connected to the Backbone they will appear at a lower level of the hierarchy on the channel where they are connected If there are so many channels connected to the Backbone that they tend to fill the page it is of course possible to create a new page within the current file in order to keep a clear network overview Subsystem Floor 3 contains Router 3 between the channel Channel 3 and the Backbone and links to the different subordinate pages A LonMaker convention is to label Side A of a router that side which is closest to the interface of the LNS network Channel3 Floor 3 Office 1 Floor 3 Office 6 If there are sub channels connected to this channel you add links for them in the same way as before that is each channel in a new subsystem and a new file 34 88 0 004 7775 1 GB TAC AB 2001 02 15 TAC Xenta and LonMaker 3 Step by step The Network Chanel 3 In the subsystem Roof we finally find the actual nodes It may be an advantage to introduce more levels in the hierarchy If there are several nodes in a room it is convenient to use one page per room The finer the subdivision the greater the possibility to use copies Root am mde aas ath aU 2 Then the corresponding subsystems for Floor 3 Office 1 to 5 and for Floor 3 Office 6 to 9 are created After that you continue with Floor 2 and so on Echelon recommends at most 10 page
69. tion Attributes New Connections Repeat the procedure for all TAC Xenta groups Note At least three nodes are required to produce a group binding otherwise you have to add a dummy unit 56 88 0 004 7775 1 GB TAC AB 2001 02 15 TAC Xenta and LonMaker 5 Step by step Bindings 5 3 Bindings between the Function blocks Point out those Function Blocks that you are going to bind by rightclicking on them and then select Connect If there are several in the same window then click on the first keep the Shift key pressed when you click on the next Function Block Rightclick and then select Connect Network Variable Connection E Display OK Nys C MTs Cancel Help Add Add All Add FB SNs Graphics Normal Use References Show Connections Selected Connections Selected Connection Targets Between Selected FB SNs From or To Selected FB SNs Connection Attributes New Connections Default Connection Description Properties Assign Are you going to bind a signal between more than two units First find out which end will be single that is will you send one to many or many to one This will determine which is Hub and which is Target Hub is the single end select the correct Subsystem Device and NV Under Target you select the corresponding Subsystem Dev
70. tton all nci s that have been changed compared to the database values will be sent So you can send one or several nci s at a time When the nci s have been sent the Apply button will be dimmed again The displayed nvi values however are in principle fetched from the unit An nvi can be changed if you click on the button gt gt to the right of the respective nvi You will then get a little dialogue box where you can enter the value that the nvi is to have The dialogue box has two buttons Set Value and Cancel If you press Cancel the dialogue box will close and the nvi will remain unchanged If you press Set Value the entered value will be sent directly to the database which in turn will forward it to the controller To modify a nvi is possible only in the Onnet mode Otherwise the button beside the nvi s is not highlighted and you cannot get the dialogue box Displayed nvo values are fetched from the unit An nvo cannot be changed it shows only the value present in the database where it origi nates from the controller nvo values are shown only in the Onnet mode Summary nci values are fetched from the data base One or several nci s can be modified and sent by the use of the Apply button nvi values are fetched from the unit Only one nvi can be modified and sent by the use of the respective dialogue box nvo values are fetched from the unit An nvo cannot be modified 42 88 0 004 7775 1 GB TAC
71. ubsystem Hierarchy Entire Network In Alarm Clear All Functional Block Status to Report Disabled Set as default options Communication failure v Self test failure v Advanced options Specify if you want to check the status of the Entire Network of the current Subsystem Hierarchy or only of the current Subsystem Page The Functional Block Status to Report is not supported by TAC Xenta In spite of this you should Set All as there may be other units in the network that may have things to report Checkmarking the Advanced options box will give you further options for the presented information Advanced Status Summary Options xi JV Locked out v Open circuit Functional Block Status to Report Electrical fault v Feedback failure v Out of service JV Manual control v Under range v Mechanical fault v Unable to measure v Alarm notify disabled v Programming failure Out of limits Set All v Over range Clear All v Programming mode 74 88 0 004 7775 1 GB TAC AB 2001 02 15 TAC Xenta and LonMaker 6 Installation of the Units Subsystem Device Functional Block old s E F L m Subsystem 1 Flo ZoneManager1 Func Block 1 Subsystem __ Devicemouter State Comments Subsystem 1 Flo Xwentilation Error communicating with device Subsystem 1Flo X451 Neuron Id has not been set Subsystem 1 Flo X421
72. ues are to used here Current values in database As we chose On line when creating the network we do not have to set this for each unit Determine what procedure you are going to use Service Pin or a Manual value of the Neuron ID Echelon LonMaker Now we have to press the Service pin on the proper unit Unless you selected the manual neuron ID entry then the service pin will not be used caai _ 2001 02 15 0 004 7775 1 GB 65 88 TAC Xenta and LonMaker 6 Installation of the Units 6 2 2 Several units together If you select several units and then rightclick and use Commission all the selected units will be installed in the way described above Another method is described below The principle is to install one channel at a time It may be convenient to bring the PC to the selected channel in order not to work against the whole network How to move the Network interface has been described earlier in this chapter If you have unique units that is each unit has a unique program ID test the Auto Match then you will not even have to look up the units The same holds true if you specified the Location String when you added the nodes to the drawing file valid for TAC Xenta 300 401 with system program version 3 40 or higher Go to the current Subsystem Select LonMaker Discover Devices Device Discovery Filters E x r Device Selection
73. urce FB Name Func Block 1 FB Type r Subsystem Name Subsystem 1 Floor 3 Floor 3 Office 1to5 Browse r Device Type a 01w02 Name 101 Y r Eunctional Block Type Virtual Functional Block ID Name Virtual Functional Block After a click upon Next gt you can change the Functional Block Name You may select the default name here Functional Block 1 Point and drag Input Network Variable to the functional block and then choose either to add all nci s quickest way but it requires more space on the drawing or only to add those nci s which will be used for bindings Choose A Network Variable Please select the network variable s you wish this shape to represent Selecting multiple network variables will result in shapes being automatically dropped Xi Cancel nciRcvHrtBt nciCool amp ctStTime nciSetpoints nciDischAirMax ncisndHrtBt Help nciDischAirMin ncispaceTempDev nciGainCool nciSpaceTempLow nciGainHeat nciSpaceTempOfst nciHeatActStTime nciXoverLimit Select All nciHeatPrimMin ncilnstallType nciltimeCool nciltimeHeat nciLocation nciMinFanSpeed Remove prefix from NY names v Remove array subscripts from NY names TAC AB 2001 02 15 0 004 7775 1 GB 39 88 TAC Xenta and LonMaker 4 Step by step The TAC Xenta Units 4 1 2 Plug in for TAC Xenta 100 To start the Plug in You can start the Plug in for a TAC Xenta 100 in different way
74. ve Details Provided that the units have unique Neuron IDs and or Location Strings your pressing Auto Match will cause the program to move the identified units down to the window Devices to be Commissioned Defined Devices Choose a unit in the list Defined Devices by clicking on the Subsystem of the respective unit After that you press the Service pin of the corresponding unit The unit will now move down to the list Devices to be Commissioned This will select the nodes sequentially as you press Service Pin Note the order of the units in the list and then seek out to the respective units in the same order and press Service Pin Check that you have matched the correct unit with the corresponding Neuron ID before you click Finish and the units will be installed TAC AB 2001 02 15 0 004 7775 1 GB 67 88 TAC Xenta and LonMaker 6 Installation of the Units 6 3 The need for the TAC Menta Configuration tool In the TAC Menta network configuration tool sometimes called TAC Menta NCT there is an option to specify if an external binding tool will be used at the installation of the units If this has not been marked that is no external binding tool will be used TAC Menta NCT will copy the subnet node addresses from the application domain to the zero length domain Thus TAC Xenta will get the same subnet node address in both the application and the zero length domain If there is a checkmark that is
75. with LM3 which means that the variable nci config src is not affected TAC Xenta OP must belong to the correct domain As a standard the domain ID 11 hex is used and we recommend that you keep to this domain address The current domain can be set on the TAC Xenta OP in the service menu item 4 LON address 00 255 Please note that the 1 byte domain address 00 is not the same as the zero length domain When a TAC Xenta OP is connected to the network it will automatically look for a free address on subnet 255 node 70 or higher Is no free address available the OP will fall silent not to disturb the network traffic If a node address is available the OP will use it Subnet 255 can be used on both sides of those Routers that TAC has used Be careful though as this is not according to standard Should problems arise you will have to install the OP permanently as described above If however no problems appeared this means that the OP in this mode is movable without the dummy nodes normally required after each TAC Xenta 300 401 An OP in this mode cannot be used for the TAC Xenta 100 units as the TAC Xenta 100 unit sends its Service pin message on the zero length domain when the OP is electrically connected to it This is done in order to make sure which unit the OP communi cates with As the OP does not belong to the zero length domain no contact will be established 72 88 0 004 7775 1 GB TAC AB 2001 02 15 TAC
76. with MAN not all nodes of the network will reside in the LNS data base To be used with TAC Xenta 100 however the TAC mode must be used as this is the only mode where OP uses both the application and the zero length domain See also section 6 4 20 88 0 004 7775 1 GB TAC AB 2001 02 15 TAC Xenta and LonMaker 2 Preparations 2 4 2 Restrictions on TAC Xenta software and hardware versions Once again a reminder about the restrictions on the TAC Xenta controllers to get the correct XIF files etc The TAC Menta software must be 3 24 or higher Please note that in the dialogue for Unit Configuration the box Add new Network variables SNVT at the end of the XIF file must be checked The software for TAC Xenta 301 302 and 401 must be v 3 2 or higher However if the procedure with Location String is to be used at least version 3 4 is required TAC Xenta 301 and 302 must be hardware type 2 2 5 Backup Restore of a LonMaker network We recommend strongly that you make regular backups of all information about the network the connected units and their settings In LMG you can specify whether backup is to be made of the database and or the drawing library Backup of the drawing library only is mainly intended for remote work A corresponding choice is made when it is time to restore the network with the Restore command Please study the LonMaker User s Guide chapter 2 the Using LonMaker Backup
77. y timers Normally you can use the default values 26 88 0 004 7775 1 GB TAC AB 2001 02 15 TAC Xenta and LonMaker 3 Step by step The Network General Options A window for certain general settings for example the Auto Save C Lonworks Graphics interval The default value is one hour which is EveryHow reasonable especially as the auto save is done in the foreground and delays current proceedings su Mu Configuration properties Configuration Properties Settings that specify how new units are to be installed Device Options Settings for new units below We recommend that you set New 5 Po Device State App Devices as Online This will facilitate addressing commissioning as the installed units will go directly online without further action pee E CALonvvorksumport CALonvveorksumport lt lt m TAC AB 2001 02 15 0 004 7775 1 GB 27 88 TAC Xenta and LonMaker 3 Step by step The Network Network Wizard Functional Block Options Set Include device name in default FB name as this will make it simpler to keep track on which function block belongs to which unit By checkmarking here you can use the default names of the respective FBs yet easily see which FB belongs to which unit Now the entry of the basic data items for the network has been completed Store them in the database by cli

TAC Xenta and LonMaker Release 3

Contents

Download Pdf Manuals

Related Search

Related Contents