TAC Vista TAC Pangaea WorkStation TAC Xenta Server – Gateway Technical Manual
TAC Vista TAC Xenta Server – Gateway Technical Manual
Copyright © 2009-2011 Schneider Electric Buildings AB. All rights reserved. This document, as well as the product it refers to, is only intended for licensed users. Schneider Electric Buildings AB owns the copyright of this document and reserves the right to make changes, additions or deletions. Schneider Electric Buildings AB assumes no responsibility for possible mistakes or errors that might appear in this document. Do not use the product for other purposes than those indicated in this document.
TAC Xenta Server – Gateway, Technical Manual Contents Contents INTRODUCTION 1 About this Manual 11 1.1 1.2 1.3 1.4 1.5 1.6 11 13 14 14 14 15 Product Features......................................................................................................... Structure ..................................................................................................................... Typographic Conventions ..........................................................................................
Contents 4.2.2 4.2.3 5 6 7 8 9 TAC Xenta Server – Gateway, Technical Manual Adding Signals for a Device....................................................................................... Adding a Device to a Communications Interface....................................................... 39 41 Creating the Logical Structure 43 5.1 5.1.1 5.1.2 43 44 45 Creating the Folder Structure ..................................................................................... Renaming the Root Folder..
TAC Xenta Server – Gateway, Technical Manual 11.2 11.3 11.4 11.5 11.5.1 11.6 11.7 11.8 11.9 11.9.1 11.9.2 Contents The Communications Interface .................................................................................. The Device Templates................................................................................................ Device Template File Format..................................................................................... Working with Existing Device Templates .............
Contents B.5.3 B.5.4 B.6 B.6.1 B.6.2 B.6.3 B.6.4 B.7 B.7.1 B.7.2 B.7.3 B.7.4 B.8 B.8.1 B.8.2 B.8.3 B.8.4 B.8.5 B.8.6 B.8.7 TAC Xenta Server – Gateway, Technical Manual BACnet Target Devices.............................................................................................. BACnet Object I/O Signals ........................................................................................ BACnet PTP (Point To Point) ..................................................................................
INTRODUCTION 1 About this Manual
TAC Xenta Server – Gateway, Technical Manual 1 1 About this Manual About this Manual This manual describes a particular process. For information on certain products, we refer you to the manual for the product in question. For information on how to install software, we refer you to the instructions delivered with the software. For information on third party products, we refer you to the instructions delivered with the third party product.
1 About this Manual TAC Xenta Server – Gateway, Technical Manual Table 1.1: Major features Product LON Xenta 511 x Xenta 527 x Xenta 527-NPR I/NET MicroNet x Xenta 701 Xenta Supp.b Weba x C x x C x x x Xenta 555 I/O Modules ModBus S x x C x x ST 10 Xenta 711 x x C 10 x Xenta 721 x x ST 20 x Xenta 731 x x x C 20 x Xenta 913c x x x S x x a. S – Service.
TAC Xenta Server – Gateway, Technical Manual 1.2 1 About this Manual Structure The manual is divided into the following parts: • Introduction The Introduction section contains information on how this manual is structured and how it should be used to find information in the most efficient way. • Getting Started The Getting Started section contains a step-by-step description of how to engineer or carry out different tasks. It also gives you guided instructions on how to complete a sample project.
1 About this Manual 1.3 TAC Xenta Server – Gateway, Technical Manual Typographic Conventions Throughout the manual the following specially marked texts may occur. ! Warning • Alerts you that failure to take, or avoid, a specific action might result in physical harm to you or to the hardware. Caution • Alerts you to possible data loss, breaches of security, or other more serious problems. Important • Alerts you to supplementary information that is essential to the completion of a task.
TAC Xenta Server – Gateway, Technical Manual 1.6 1 About this Manual Related Documents • Classic Networks, Technical Manual Part No.: 04-00015 • LNS Networks, Technical Manual Part No.: 04-00016 • TAC Software, Installation Manual Part No.: 04-00001 • TAC Xenta 500/700/911/913, Product Manual Part No.: 04-00071 • TAC Xenta Server – TAC Networks, Technical Manual Part No.: 04-00121 • TAC Xenta Server – Web Server, Technical Manual Part No.
1 About this Manual 16 (184) TAC Xenta Server – Gateway, Technical Manual Schneider Electric Buildings AB, June 2011 04-00124-06-en
GETTING STARTED 2 Planning the Project 3 Creating a Project 4 Configuring Modbus Communication 5 Creating the Logical Structure 6 Visualizing Signals 7 Adding the TAC Xenta 913 to the LonWorks Network 8 Connecting to the LonWorks Network 9 Creating SNVTs
TAC Xenta Server – Gateway, Technical Manual 2 Planning the Project 2.1 The Function of the TAC Xenta 913 2.1.1 Gateway 2 Planning the Project The TAC Xenta 913 can act as a gateway between LonWorks and I/NET systems and the targeted third party system. Using the applicable communications protocol, the Xenta 913 can read values from the target system and make them available to the LonWorks and I/NET systems. Similarly, LonWorks and I/NET variables can be written to the target system.
2 Planning the Project 2.2 TAC Xenta Server – Gateway, Technical Manual The Target System The TAC Xenta 913 includes interface drivers for a number of serial or Ethernet communication protocols. Any target equipment that can communicate by means of an RS-232/485 serial network or Ethernet using one of the supported protocols can be used with the Xenta 913. The available types of target networks are outlined in Fig. 2.1.
TAC Xenta Server – Gateway, Technical Manual 2.3 2 Planning the Project Surveying the Target System Installation Normally, the target system is installed and commissioned before you install the Xenta 913. Of course, it is possible to install the Xenta 913 first, but it cannot be fully commissioned until the target equipment is operational. So, in most cases, the first step is to survey an existing installation and verify the operation of the target devices. 2.3.
2 Planning the Project 2.4 TAC Xenta Server – Gateway, Technical Manual Understanding the Example System We are going to create a system for a fictitious company, ACME Inc., which has one office bulding as illustrated in Fig. 2.2. The building is a typical, small two-storey office building, served by packaged roof-top equipment. The first floor area serves the Entrance Lobby, Accounts, Marketing, and Senior Management. The second floor area serves Customer Support and Engineering.
TAC Xenta Server – Gateway, Technical Manual 2.4.1 2 Planning the Project Units The building is divided into 2 floors: First Floor • Lobby: Served by a roof-top air handling unit with a constant volume controlling a single zone. • Accounts: Served by a roof-top air handling unit with a constant volume. The roof-top unit has central cooling and heating. Nine dump dampers control the return air plenum.
2 Planning the Project 2.4.2 TAC Xenta Server – Gateway, Technical Manual Devices In the example, we have simplified the ACME Inc. building as follows: RTU4 Energy Meter ACME_Gateway Fig. 2.3: Simplified ACME building In the example, the gateway system ACME_Gateway (that is Xenta 913) works with the following devices. Modbus Energy meter PM710 LonWorks (Second Floor) RTU4 Xenta 401 I/O-Modules Xenta 422 Xenta 452 Fig. 2.4: The devices.
TAC Xenta Server – Gateway, Technical Manual 2 Planning the Project TAC Vista Device Structure The LonWorks network is called ACME_Inc after the company. The device structure is created in TAC Vista. Since the building has two floors, the network is designed with its devices divided into two Xenta groups named 1st_Floor and 2nd_Floor. The device RTU4 is located on the second floor and belongs to the Xenta group 2nd_Floor.
2 Planning the Project TAC Xenta Server – Gateway, Technical Manual 2.5 Developing the Project 2.5.1 TAC XBuilder TAC XBuilder is a programming tool for creating the gateway application for the Xenta 913. Connections between signals in the device structure are created using XBuilder. The signals can also be displayed on different web pages in a web browser. The gateway application is subsequently sent to Xenta 913 and the transferring of data between the devices is then handled by the Xenta 913. 2.5.
TAC Xenta Server – Gateway, Technical Manual 2 Planning the Project 2.6 Creating a Project Folder on the Hard Disk 2.6.1 Folder Structure A project for a complete system is best placed in a directory containing the folders and subfolders similar to the figure below. Fig. 2.6: The folder structure on the hard disk. This structure should be prepared when the device structure of the project is created, as described in Classic Networks, Technical Manual or LNS Networks, Technical Manual.
2 Planning the Project 28 (184) TAC Xenta Server – Gateway, Technical Manual Schneider Electric Buildings AB, June 2011 04-00124-06-en
TAC Xenta Server – Gateway, Technical Manual 3 3 Creating a Project Creating a Project The connections between signals in the different devices are made using XBuilder, the programming tool for creating the Xenta 913 gateway application. The XBuilder project for the Xenta 913, in the example ACME_Gateway, is stored in the C:\ProjectACME folder. 3.1 The User Interface Read the User Interface chapter in the TAC XBuilder Help to learn more about the TAC XBuilder user interface and terminology. Fig. 3.
3 Creating a Project 3.2 TAC Xenta Server – Gateway, Technical Manual Creating a Project Ensure that XBuilder is installed according to TAC Software, Installation Manual. To create a project 30 (184) 1 On the Start menu, point to Programs, point to Schneider Electric, point to TAC Tools, and then click XBuilder. 2 On the File menu, click New Project. 3 In the Project name box, type the name of the project. In the example “ACME_Gateway”.
TAC Xenta Server – Gateway, Technical Manual 3 Creating a Project 6 In the Project template list ensure that the required project template is selected. In the example, Xenta 913 Project. 7 Click OK. The Settings dialog box appears. 8 In the Description box, type a descriptive text. In the example, “Project for ACME Gateway”. 9 In the Measurement system list, click the required measurement system. In the example, U.S.
3 Creating a Project TAC Xenta Server – Gateway, Technical Manual 10 Select the Send Project backup file to target device check box. 11 Click OK. The project has now been created. In the project folder on the hard disk, C:\ProjectACME, a new subfolder, ACME_Gateway, is present. ACME_Gateway in turn contains several subfolders.
TAC Xenta Server – Gateway, Technical Manual 3.3 3 Creating a Project Configuring the TAC Xenta 913 Object The gateway application created in XBuilder is sent to the Xenta 913. As the communication takes place on the TCP/IP network, XBuilder needs to know where to send the project. This information, that is, the IP address of the Xenta 913 and other relevant information, is entered in the XBuilder project. In this event, the Xenta 913 is also referred to as the target system.
3 Creating a Project TAC Xenta Server – Gateway, Technical Manual Notes 3.4 • Other parameters for the Xenta 913 are configured at later stages in the project. • For more information about the Xenta 913 configuration, see TAC Xenta 500/700/911/913, Product Manual. Saving the Project In XBuilder you can now continue to develop the project and its presentation for the Xenta 913. Before you continue, save the project. To save the project • On the File menu, click Save.
TAC Xenta Server – Gateway, Technical Manual 4 4 Configuring Modbus Communication Configuring Modbus Communication The Xenta 913 can exchange data with devices on different networks. A gateway application within the Xenta 913 enables exchange of data between devices on the different networks. For example, by using the serial interfaces RS-232 or RS-485, the Xenta 913 can be configured for communicating using a serial protocol such as Modbus.
4 Configuring Modbus Communication TAC Xenta Server – Gateway, Technical Manual 4.1 Adding a Modbus Master Interface 4.1.1 Adding a Modbus Master Interface You enable the serial communication on the RS-485 A port on the Xenta 913 by adding a communications interface in your XBuilder project, in the example, a Modbus Master interface. To add a Modbus Master interface 36 (184) 1 In XBuilder, in the network pane, right-click RS232-485 A.
TAC Xenta Server – Gateway, Technical Manual 4 Configuring Modbus Communication Important • 4.2 To enable Ethernet communication to a remotely controlled device you add an interface to the TCP-IP port in XBuilder, for example a Modbus TCP Client. Creating a Device Template A device template is created for every type of device that the Xenta 913 communicates with. Knowledge of the information that is exchanged, such as boolean signals or registers, must be readily available.
4 Configuring Modbus Communication 4.2.1 TAC Xenta Server – Gateway, Technical Manual Creating a Device Template In the PM710 energy meter, a number of values are to be read and later be sent to the RTU4 device on the LonWorks network. The Xenta 913 collects this information using the Modbus serial communications interface. Some configuration parameters are also to be sent to the meter. To create a device template 1 In the network pane, right-click the serial communications interface.
TAC Xenta Server – Gateway, Technical Manual 4.2.2 4 Configuring Modbus Communication Adding Signals for a Device In the protocol specific pane, signals are configured according to communication needs. The following signals are used in the example and the manual for the energy meter provides the information about each signal. Note • This example shows only the signals required for one of the phases. Fig. 4.1: The required signals from the PM710 energy meter.
4 Configuring Modbus Communication TAC Xenta Server – Gateway, Technical Manual To add signals for a device 1 In the device editor, in the protocol specific area, on row 3, click the Name cell, and type the name of the first signal. In the example, “Total_real_power”. 2 In the Description cell, type a descriptive text. In the example, “Total real power”. 3 In the Number cell, type the register number. In the example, “44006”. 4 In the Type cell list, click the register type.
TAC Xenta Server – Gateway, Technical Manual 4.2.3 4 Configuring Modbus Communication Adding a Device to a Communications Interface After the device template is created, you add a device of that type to the communications interface in the network pane. To add a device to the communications interface 1 In the network pane, right-click the communications interface. In the example, Modbus_Master. 2 Click Add Device. 3 In the Open dialog box, specify device template. In the example, [Modbus Ext]PM710.
4 Configuring Modbus Communication TAC Xenta Server – Gateway, Technical Manual The signals created for the device appears in the network pane and are now ready for use. For widely used equipment, such as the PM710 energy meter, template files may already be available in the device library. For more information about the device library and how to use existing device templates, see Section 11.5, “Working with Existing Device Templates”, on page 95.
TAC Xenta Server – Gateway, Technical Manual 5 5 Creating the Logical Structure Creating the Logical Structure Once the serial communications interface and the Modbus device have been inserted into the XBuilder project, it is time to add a folder structure that facilitates the work of the engineer, as well as a logical presentation structure. The latter is visible on the Xenta 913 web site you connect to using a web browser and is used for communication diagnostics.
5 Creating the Logical Structure 5.1.1 TAC Xenta Server – Gateway, Technical Manual Renaming the Root Folder The name of the root folder (by default “The site name”) should reflect what the system displays, such as the name or the function of the Xenta 913. To rename the root folder 44 (184) 1 In XBuilder, in the system pane, right-click “The site name” and click Rename. 2 Type the name. In the example, “ACME_Gateway”.
TAC Xenta Server – Gateway, Technical Manual 5.1.2 5 Creating the Logical Structure Adding a Folder To add a folder 1 In the system pane, right-click the root folder. In the example, ACME_Gateway. 2 Point to New and click Folder. 3 Type a name for the new folder. In the example, “Engineering”. 4 In the properties pane, under Page, in the Visible list, click visibility option. In the example, False.
5 Creating the Logical Structure 46 (184) TAC Xenta Server – Gateway, Technical Manual Schneider Electric Buildings AB, June 2011 04-00124-06-en
TAC Xenta Server – Gateway, Technical Manual 6 6 Visualizing Signals Visualizing Signals To easily view signal values on the web site, the signals in the system can be made available. The signals are available on values pages, which present the values as tables on web pages. Values pages are displayed in the status viewer when a values page is clicked in the navigator.
6 Visualizing Signals 6.2 TAC Xenta Server – Gateway, Technical Manual Adding a Signal In the following example, you add the signals from the Modbus device, that is, the energy meter PM710. To add a signal 1 In the network pane, drag the required signals to the destination folder in the system pane.
TAC Xenta Server – Gateway, Technical Manual 2 6 Visualizing Signals In the example, drag the signals IP Backbone-TAC_Xenta_913Modbus_Master-PM710-ComsFail and all other signals in the PM710 in the network pane to the folder ACME_Gateway-Engineering-PM710_Signals in the system pane.
6 Visualizing Signals 6.2.1 TAC Xenta Server – Gateway, Technical Manual Changing the Unit of a Signal The ACME_Gateway project uses the U.S. system of measurement. If required, any individual signal can be changed to display an SI unit. For example, the Tot_real_power is displayed in Btu/s but can easily be changed to display kW instead. To change the unit of a signal 50 (184) 1 In the system pane, click the required signal. In the example, ACME_Gateway-Engineering-PM710_Signals-Tot_real_power.
TAC Xenta Server – Gateway, Technical Manual 6.3 Adding a Values Page 6.3.1 Adding a Values Page 6 Visualizing Signals In the following example, you add values pages that display the signals from the energy meter. These pages can be used for monitoring the communications. To add a values page 1 In the system pane, right-click the root folder. In the example, ACME_Gateway. 2 Point to New, point to Page, and then click Values Page. 3 Type the name of the values page.
6 Visualizing Signals TAC Xenta Server – Gateway, Technical Manual 7 In the properties pane, in the description box for the ComsFail_2 shortcut, type “PM710 is offline or incorrectly addressed” and in the description box for the online_2 shortcut, type “PM710 is online”. In the Xenta 913, after sending the project, the values page appears as follows. Note • 52 (184) The text displayed in the Name column of a value is taken from the Description property of the signal’s shortcut in XBuilder.
TAC Xenta Server – Gateway, Technical Manual 6 Visualizing Signals To add more values pages 1 In the example, in the system pane, right-click ACME_Gateway. 2 Point to New, point to Page, and then click Values Page. 3 Type the name of the values page, in the example “PM710_Values”. 4 Select the following signals in the folder ACME_GatewayPM710_Signals and drag them to the PM710_Values values page.
6 Visualizing Signals 6.4 TAC Xenta Server – Gateway, Technical Manual Verifying the Modbus Communication After the project is sent to the Xenta 913, the communication on the Modbus network can be verified. Open the web pages containing the signals from the energy meter and verify that they appear as expected. Important • To verify communication, generate the project and send it to the Xenta 913. In the Xenta 913, the web site appears as follows. 6.
TAC Xenta Server – Gateway, Technical Manual 7 7 Adding the TAC Xenta 913 to the LonWorks Network Adding the TAC Xenta 913 to the LonWorks Network Before you can connect the signals from the Modbus devices to devices on the LonWorks network, you install the Xenta 913 on the LonWorks network. This is done so that the Xenta 913 can transfer data from the Modbus device to, in the example, the RTU4 device. 7.
7 Adding the TAC Xenta 913 to the LonWorks Network 7 TAC Xenta Server – Gateway, Technical Manual Point to New, point to Device, and then click LonWorks Device. Important • Adding devices can only be made in engineering mode 8 Click OK. The Add a LonWorks device wizard appears. 9 Click Next. 10 Type the name of the LonWorks device. In the example, “ACME_Gateway”. 11 Select the The device type is TAC Xenta 511/527555//701/711/ 721/731/913 check box. 12 Click Next.
TAC Xenta Server – Gateway, Technical Manual 7 Adding the TAC Xenta 913 to the LonWorks Network 14 On the Xenta 913, press the service pin button. Note • If the Xenta 913 has yet to be installed on the LonWorks network, the Neuron ID for the Xenta 913 can be typed in. 15 Under Load XIF file from, use the .xif file created in your XBuilder project or leave the box empty. Note • By selecting the device type X511/527/913 the Xenta 913 automatically becomes a member of the TAC group.
7 Adding the TAC Xenta 913 to the LonWorks Network 58 (184) TAC Xenta Server – Gateway, Technical Manual Schneider Electric Buildings AB, June 2011 04-00124-06-en
TAC Xenta Server – Gateway, Technical Manual 8 8 Connecting to the LonWorks Network Connecting to the LonWorks Network Once communication to the energy meter is set up and verified and the Xenta 913 is installed on the LonWorks network, you can connect the signals through the Xenta 913 to another device, in the example RTU4. In XBuilder, the signals from the energy meter are connected to signals in RTU4. The connections are made using connection objects or multiconnection objects added in XBuilder.
8 Connecting to the LonWorks Network 8.1.1 TAC Xenta Server – Gateway, Technical Manual Inserting a LonWorks Network in TAC XBuilder The TAC Xenta 913 object in XBuilder has a LON object which is used when the physical network is inserted. The Vista server must be running before it is possible to insert the network. To insert a LonWorks network in TAC XBuilder 1 Start Vista Server with the network you want to insert.
TAC Xenta Server – Gateway, Technical Manual 8 Connecting to the LonWorks Network 5 In the Password box type a password. In the example, “system”. 6 Click OK. The Select dialog box appears. 7 In the Select dialog box, browse to the required network level. In the example, the VistaSRV1-LTA_1-ACME_Inc-2nd_floor. 8 Click the required device and then click Open. In the example, RTU4. The ACME_Inc network device is now present in the network pane, under LON.
8 Connecting to the LonWorks Network TAC Xenta Server – Gateway, Technical Manual Unrecognized Units ! 62 (184) Notes • If the inserted network contains unrecognized units, you have to associate them to units known to the Xenta 913. • If the signal is of a category that is not known to the Xenta 913, set the category to No Category.
TAC Xenta Server – Gateway, Technical Manual 8.2 8 Connecting to the LonWorks Network Updating a LonWorks Network in TAC XBuilder After you have made changes to the devices in the LonWorks network, the XBuilder project must be updated to reflect the changes; for example, if you have downloaded an application from Vista to one of the devices to which you have added some signals. 8.2.
8 Connecting to the LonWorks Network 8.3 TAC Xenta Server – Gateway, Technical Manual Connecting Signals to and from LON Once the serial communication network and the LonWorks network are in place, the Xenta 913 is used to transfer values between the devices on the networks. The physical signals from the networks are connected to connection objects or multi-connection objects in XBuilder. The following example connects signals from the energy meter to public signals in the RTU4 Xenta device.
TAC Xenta Server – Gateway, Technical Manual 8.3.1 8 Connecting to the LonWorks Network Adding Signal Objects for RTU4 Signal objects can be created in the system pane for the LonWorks signals that are to be used in XBuilder. To add signal objects for RTU4 1 In XBuilder, in the network pane, drag the required signals to the destination folder in the system pane.
8 Connecting to the LonWorks Network TAC Xenta Server – Gateway, Technical Manual Tip • 8.3.2 If required, change the unit of the Usage_Tot_real_power signal to kW. Adding a Connection Object Now it is possible to transfer various values from one device to another by connection objects. As ComsFail and online signals are used for generating alarms in RTU4, these signals from the Modbus network and the energy meter are transferred to RTU4.
TAC Xenta Server – Gateway, Technical Manual 8 8 Connecting to the LonWorks Network In the properties pane, under General, in the Period (s) box, type the required transfer period in seconds. In the example, “10”. The value of the From signal is now transferred to the To signal at the specified interval. In the example, the Modbus Link ComsFail signal is transferred to Usage_Link_ComsFail in RTU4 every 10 seconds.
8 Connecting to the LonWorks Network 8.3.3 TAC Xenta Server – Gateway, Technical Manual Adding a Multi-Connection Object To simplify the engineering process of connecting signals between the devices multi-connection objects can be used. These objects act as containers of many connection objects and they allow you to make several connections in one dialog box.
TAC Xenta Server – Gateway, Technical Manual 8 Connecting to the LonWorks Network 4 In XBuilder, in the system pane, drag the receiving signal to the To column in the connection manager. In the example, ACME_Gateway-Engineering-RTU4_SignalsUsage_Inst_curr_ph_1 to the first row of the To column in the connection manager. 5 In the connection manager, in the Send Option list, click Write initially and on change.
8 Connecting to the LonWorks Network TAC Xenta Server – Gateway, Technical Manual Before you close the connection manager, verify the connections to ensure that the connections are valid. 7 In the Connection Manager dialog box, click Validate. 8 Click OK. 9 In the system pane, right-click the new multi-connection object. In the example, 1. 10 Click Rename. 11 Type the name. In the example, “PM710_to_RTU4”, and then press ENTER.
TAC Xenta Server – Gateway, Technical Manual 8.4 8 Connecting to the LonWorks Network Verifying the Gateway Application After the signals are connected between the energy meter and RTU4, and the project has been sent to the Xenta 913, you have to verify that the result is as expected. Adding the signals to values pages is one way of verifying that the communication functions as expected. 8.4.
8 Connecting to the LonWorks Network TAC Xenta Server – Gateway, Technical Manual 5 If required, rearrange the shortcuts. 6 Generate the project and send it to the Xenta 913. 7 Open the Communications values page in a web browser and verify that all values appear as expected. 8 Open the RTU4 values page in a web browser and verify that all values appear as expected.
TAC Xenta Server – Gateway, Technical Manual 9 9 Creating SNVTs Creating SNVTs For more information about SNVTs and controller objects, see Section 10.1, “Defining SNVTs and Controller Objects”, on page 81. 9.1 Adding a Controller Object and a SNVT In the following example, you create a SNVT in the Xenta 913 that propagates a value, in the example Tot_real_power, from the energy meter on the Modbus interface.
9 Creating SNVTs 9.1.1 TAC Xenta Server – Gateway, Technical Manual Adding a Controller Object and a SNVT To add a Controller Object and a SNVT 74 (184) 1 In the network pane, right-click IP Backbone-TAC_Xenta_913SNVTs-LonMarkObjects and click Add Controller Object. 2 Type the name. In the example “Energy_Meter”. 3 Right-click NetworkVariables and click New SNVT. 4 In the Name box, type the name of the SNVT. In the example “nvo_Tot_real_pow”. 5 In the Type list, click power_kilo.
TAC Xenta Server – Gateway, Technical Manual 7 In the Period (s) box, type the required value. 8 In the Delta box, type type the required value. 9 Click OK. 9 Creating SNVTs The controller object and its SNVT are now created and the SNVT can be used in the XBuilder project.
9 Creating SNVTs 9.1.2 TAC Xenta Server – Gateway, Technical Manual Connecting a Signal to an Output SNVT An output SNVT created in the Xenta 913 is given its value by using a connection object. For more information about connection objects, see Section 10.2, “Connection Objects”, on page 87. To connect a signal to an output SNVT 1 In the system pane, in the example, expand ACME_GatewayEngineering-Connection_Objects. 2 Right-click Connection_Objects, point to New, and then click Folder.
TAC Xenta Server – Gateway, Technical Manual 9 Creating SNVTs The .xif file for the Xenta 913 is created when you generate the project. It is automatically downloaded to the Xenta 913 when you send the project to the Xenta 913. Tips • In this example, you will find the .xif file in the following location: C:\Project_ACME\ACME_Gateway\TargetImage\configdb\lon\TAC_Xenta_913.xif. • You can generate a new .
9 Creating SNVTs 78 (184) TAC Xenta Server – Gateway, Technical Manual Schneider Electric Buildings AB, June 2011 04-00124-06-en
REFERENCE 10 Using Signals 11 Configuring Serial or Ethernet Communication 12 Working with Third-party Communication Diagnostics
TAC Xenta Server – Gateway, Technical Manual 10 Using Signals 10.1 Defining SNVTs and Controller Objects 10 Using Signals Public signals on the network are always polled when they are used in the Xenta 913. SNVTs from devices on the network can also be used for display in values pages and transferring to other devices. These are also polled. SNVTs can be added to the Xenta 913 to make them available on the LonWorks network. Using LonMaker, you can bind these to other devices on the network.
10 Using Signals TAC Xenta Server – Gateway, Technical Manual You can have either input or output SNVTs; this is set in the device to which the SNVT is added. You can add both input and output SNVTs to the Xenta 913. Tip • You can add several controller objects containing SNVTs with the same name. This is very useful when your system communicates with many devices of the same type. For an example on how to add a controller object and a SNVT, see Section 9.
TAC Xenta Server – Gateway, Technical Manual 10.1.2 10 Using Signals Output SNVTs Output SNVTs are used for sending (propagating) information from devices on a LonWorks network. The value of the SNVT can be sent regularly or it can be sent upon change, that is when the signal the SNVT represents changes. When you add a SNVT to XBuilder the following dialog box appears (the Direction has been changed to Output).
10 Using Signals TAC Xenta Server – Gateway, Technical Manual • Members – You use the Members list to inspect the signals contained by the SNVT, if the SNVT you selected in the Type list is structured. • Initial Value – If you want the output SNVT to have an initial value you type the value required in the Initial Value box. This value is kept until the signal the SNVT represents changes. • Unit – If the SNVT has a unit you enter that unit in the Unit box.
TAC Xenta Server – Gateway, Technical Manual 10.1.3 10 Using Signals Input SNVTs Input SNVTs are used for collecting information from devices on the LonWorks network. An input SNVT can be used in two ways, either as an: • Update, that is, the SNVT that supplies the value to the input SNVT decides when to send an updated value, or • Poll, that is, the Xenta 913 asks for the signal value at regular intervals.
10 Using Signals TAC Xenta Server – Gateway, Technical Manual • Backup – By selecting the Backup check box, the momentary value of the SNVT is stored in the memory of the Xenta 913. If the Xenta 913 is restarted, the stored value is used until a new value is propagated on the network or until the Xenta_913 polls the value. • Members – You use the Members list to inspect the signals contained by the SNVT, if the SNVT you selected in the Type list is structured.
TAC Xenta Server – Gateway, Technical Manual 10.2 10 Using Signals Connection Objects Setting up the transfer of signal values from one device to another is carried out in XBuilder. This is made using connection objects or multiconnection objects. After sending the XBuilder project (the gateway application) to the Xenta 913, the signals are transferred at regular intervals between the devices. For examples on how to connect signals between devices using connection objects, see Section 8.3.
10 Using Signals 10.3 TAC Xenta Server – Gateway, Technical Manual Multi-Connection Objects For examples on how to connect signals between devices using multiconnection objects, see Section 8.3.3, “Adding a Multi-Connection Object”, on page 68. Multi-connection objects are used to simplify the engineering process of connecting signals between the devices.
TAC Xenta Server – Gateway, Technical Manual 10.3.1 10 Using Signals Validating the Signals After the required signals are added to the connection manager you must validate them, that is check that the selected signals comply with the rules so that connection objects can be created. You can click the Validate button at any time. The result of the validation is presented in the box beside the button: If any errors are detected, you are notified in the connection manager..
10 Using Signals 10.3.2 TAC Xenta Server – Gateway, Technical Manual Using the Find and Replace Function In the connection manager there is a find and replace function that is very useful, for example, if you have several devices of the same kind on your communication interface and you only need to rename a part of every signal name to make a second device. To use the Find and Replace function 1 Click the Show Find and Replace check box. The Find and Replace area becomes visible.
TAC Xenta Server – Gateway, Technical Manual 11 Configuring Serial or Ethernet Communication 11 Configuring Serial or Ethernet Communication 11.1 Overview The Xenta 913 can exchange data with devices on networks other than the LonWorks network. By using the serial interfaces RS-232 or RS-485, the Xenta 913 can be configured for communication using a serial protocol such as Modbus.
11 Configuring Serial or Ethernet Communication 11.2 TAC Xenta Server – Gateway, Technical Manual The Communications Interface You enable the communication on the RS-232/485 A port or the 10Base-T port on the Xenta 913 by adding an interface in your XBuilder project. The interface specifies which protocol is used, which port to use and parameters controlling the communication.
TAC Xenta Server – Gateway, Technical Manual 11.3 11 Configuring Serial or Ethernet Communication The Device Templates TAC Device Editor is used to configure the data that is to be exchanged using the communication protocol selected for the port on the Xenta 913. The device editor is included in the XBuilder installation. A new folder is installed together with the device editor, and is located at C:\Program files\TAC\Device Library.
11 Configuring Serial or Ethernet Communication 11.4 TAC Xenta Server – Gateway, Technical Manual Device Template File Format A file saved using the device editor has the extension .dev. The file name is automatically in the format []..dev, for example [Modbus Ext].My_File.dev. The maximum number of characters for the file name, including the protocol name and the file name extension, is 31 characters.
TAC Xenta Server – Gateway, Technical Manual 11.5 11 Configuring Serial or Ethernet Communication Working with Existing Device Templates If you are working with equipment that is used widely, such as the PM710 energy meter, it is generally a good idea to create a device template with all the signals for the device. If you then store the template file on a server, other users can access that template as it is or, if required, you can remove unused signals and save the template under a new name.
11 Configuring Serial or Ethernet Communication 11.6 TAC Xenta Server – Gateway, Technical Manual Updating the Devices in a TAC XBuilder Project After you have modified a device template file, you save it in the device library, C:\Program files\TAC\Device Library. When you quit the device editor after making changes to a template file, its behaviour varies depending on how it was started. If it was started from the Program menu, it simply quits.
TAC Xenta Server – Gateway, Technical Manual 11.7 11 Configuring Serial or Ethernet Communication Replacing a Device Template File If the physical device connected to the serial or TCP-IP communication port is replaced with another kind of device, you must also replace the device template file for the device in XBuilder. To replace a device template file 1 In the network pane, right-click the device you want to replace, and click Replace Device Template.
11 Configuring Serial or Ethernet Communication 11.9 TAC Xenta Server – Gateway, Technical Manual Enumerations Instead of displaying a figure to describe the state of a signal texts can be used on, for example, values pages. These texts are defined using enumeration. 11.9.1 Creating enumeration By creating enumeration in the device editor for the signal you can let the status of a signal be displayed in clear text, rather than as a number.
TAC Xenta Server – Gateway, Technical Manual 12 12 Working with Third-party Communication Diagnostics Working with Third-party Communication Diagnostics The communications for the protocols that use the serial interfaces (RS232 and RS-485) on the Xenta 913 can be monitored using HyperTerminal or on the Xenta 913 web site. To monitor the communications for the protocols that use the Ethernet network, you connect a network listener. 12.
12 Working with Third-party Communication Diagnostics 12.2 TAC Xenta Server – Gateway, Technical Manual Testing Target Communications To test a Xenta 913, target communications should be monitored using the diagnostics log using either HyperTerminal or a web page. Several commands are provided to support testing, as described below. These commands are activated using either a web browser or HyperTerminal.
TAC Xenta Server – Gateway, Technical Manual 12 Working with Third-party Communication Diagnostics Driver Selection The command vx D prints a numbered list of the configured drivers in the system together with the version number of the driver. • • Using HyperTerminal, just type in vx D and the available drivers are listed on the screen. • In a system without any configured drivers all drivers available are listed. • In a configured system, only the configured drivers are listed.
12 Working with Third-party Communication Diagnostics TAC Xenta Server – Gateway, Technical Manual Start/Stop Target Communication The Xenta 913 target communications can be started and stopped at any time without restarting the whole gateway application. When the Xenta 913 is first started, there is a ten second pause before the gateway application starts up, allowing you to prevent it from running when conducting a separate test.
TAC Xenta Server – Gateway, Technical Manual 12 Working with Third-party Communication Diagnostics At a verbosity level of 9, the log records all communications activity between the Xenta 913 and the target system. However, the large volume of messages resulting may obscure simple configuration problems, so this is normally only used in short bursts to locate protocol faults.
12 Working with Third-party Communication Diagnostics 12.3 TAC Xenta Server – Gateway, Technical Manual Diagnosing Incorrect Target Communications Run the diagnostics log at the appropriate verbosity level and monitor the resulting communications activity. If necessary, record the log to file for later playback. The type of log data is dependent on the target system. However, the basic form should resemble the following log excerpts from the Modbus Master example.
TAC Xenta Server – Gateway, Technical Manual 12 Working with Third-party Communication Diagnostics Example log: Modbus Timeout Error The messages prefixed by !MBM in this log indicate that a Modbus device has not responded. The most likely cause of such errors depends on how many target devices are affected. Consider, therefore, the following: • If the fault is to a single unit only, then this indicates a fault in that particular device, or possibly the wiring to it.
12 Working with Third-party Communication Diagnostics 106 (184) TAC Xenta Server – Gateway, Technical Manual Schneider Electric Buildings AB, June 2011 04-00124-06-en
APPENDIX A Network Connections Overview B Protocols
TAC Xenta Server – Gateway, Technical Manual A Network Connections Overview A Network Connections Overview A.1 General The Xenta 913 acts both as an interface between IP/LonWorks networks and as a coordinator/presentation system for numerous application facilities in these networks. To accomplish this, several configuration and application parameters have to be set, web pages designed and user authorities defined. These settings are described in the sections below.
A Network Connections Overview TAC Xenta Server – Gateway, Technical Manual Upon sending the project to the Xenta 913, parameters from XBuilder may overwrite parameters set directly in the Xenta 913; a warning is displayed before this occurs, however. Tip • 110 (184) Parameters set in the Xenta 913 should be uploaded to XBuilder so they are saved in the XBuilder project.
TAC Xenta Server – Gateway, Technical Manual A Network Connections Overview The configuration and application parameters relate to the network connections in accordance with the following schematic overview.
A Network Connections Overview A.2 TAC Xenta Server – Gateway, Technical Manual Basic TCP/IP Settings Ask the network administrator for the basic IP address information. TCP/IP The Ethernet interface includes the IP Address, Subnet Mask, Default Gateway, DNS (Domain Name System) and DHCP (Dynamic Host Configuration Protocol). These properties can be set using the setip command from the terminal interface.
TAC Xenta Server – Gateway, Technical Manual A Network Connections Overview • DHCP IP address Server Failure. If the DHCP server fails, the Xenta 913 cannot retrieve its addresses, and as a result will use a temporary IP address. • Maintenance. Each Xenta 913 may require an individual address reservation in the DHCP server. Creating these address reservations typically includes collecting the MAC IDs from each Xenta 913. Replacing an Xenta 913 requires changing the DHCP reservation as well.
A Network Connections Overview A.3 TAC Xenta Server – Gateway, Technical Manual Application Server Setting – HTTP HTTP The Xenta 913 is an HTTP (Hypertext Transfer Protocol) server. Several users can view the web pages at the same time, but they are limited by the number of HTTP sessions allowed. • Max. simultaneous HTTP sessions, choose a number from the list. The default setting is 15. Several users can view files at the same time. • HTTP port, define a port number. The default setting is 80.
TAC Xenta Server – Gateway, Technical Manual A.4 A Network Connections Overview Network Management Settings – SNMP The Simple Network Management Protocol is a set of protocols for managing complex networks. SNMP works by sending messages, called protocol data units (PDUs), to different parts of a network. These messages can be picked up and analyzed by a network supervisor. To utilize this function (SNMP v 1), a number of parameters must be set in the Xenta 913.
A Network Connections Overview TAC Xenta Server – Gateway, Technical Manual SNMP Agent (requesting information from the Xenta 913) • Management Station IP Address – The IP address of the network supervisor. IP 0.0.0.0 means that messages can be picked up at any point in the network. • SNMP Port Number – Port no. used for SNMP access, not to be changed. • Community Name – As set up with the Agent. • System Contact – Optional descriptive text. • System Location – Optional descriptive text.
TAC Xenta Server – Gateway, Technical Manual B Protocols B Protocols B.1 Modbus Serial Line Master The Xenta 913 can be configured to act as the sole master on a Modbus and/or J-Bus serial network to allow monitoring and control of one or more slave devices through an I/NET or LON control system. Both the RTU and ASCII protocol formats are supported. Modbus Master LON or I/NET Control System Value exchange Xenta 913 RS-485 A Modbus Network RS-485 Extender RTU or ASCII Slave Slave Slave Fig. B.
B Protocols B.1.1 TAC Xenta Server – Gateway, Technical Manual Modbus Master Networks A Modbus Master Network consists of a single master and one or more independent slaves interconnected by an RS-485 serial link. While the Xenta 913 is attached to the network it continuously polls the attached slaves to read the required register values. It can also write the necessary control system values out to the slaves. All devices on the network must use the same Modbus framing mode (RTU or ASCII).
TAC Xenta Server – Gateway, Technical Manual B.1.2 B Protocols Modbus Master Interface The Modbus Master interface is added into the network pane of XBuilder, as shown for a Modsim example network in the following screenshot. Interface Properties • Port Type – In most cases the RS-485 port option will be selected.
B Protocols TAC Xenta Server – Gateway, Technical Manual • B.1.3 online – Flags ONLINE during normal network communications, and will change to OFFLINE only if communication has failed to all slaves on the Modbus network. An OFFLINE condition normally indicates incorrect communication property settings, or faulty wiring of the network between the Xenta 913 and the slave devices.
TAC Xenta Server – Gateway, Technical Manual B Protocols Device Status Signal For each device the Modbus Master driver generates a communication status signal. • ComsFail – Flags if communications with the slave device have failed. May be caused by an incorrect device address having been entered, or by incorrect wiring of the RS-485 network connection to it. • online – Flags ONLINE during normal device communications, and will change to OFFLINE if communications with the slave device have failed.
B Protocols B.1.4 TAC Xenta Server – Gateway, Technical Manual Modbus I/O Signals Each Modbus Slave device represents a specific type of hardware device. There are two main ways to work with Modbus I/O signals, Fixed Address Block and Full Address Range register. Fixed Address Blocks When Fixed Address Blocks is used for the device all data types have to adhere to the fixed address number according to Table B.
TAC Xenta Server – Gateway, Technical Manual B.1.5 B Protocols The Modbus Device Editor The device editor is used to create new slave types, or to modify existing types, as shown in the following screenshot. Each signal can be used to read or write the value of one or more Modbus registers within any slave devices of the type being defined. • Register Number – Allows the base number of each required Modbus register set to be selected.
B Protocols TAC Xenta Server – Gateway, Technical Manual Table B.1: Fixed Address Blocks number ranges (Contd.) Fixed Address Blocks number ranges Functions codes Description 30001–40000 4 Read one or more 16-bit input registers. (Input Register) 40001–50000 3, 6, 10 Read and write one or more 16-bit holding registers. (Holding Register) X0001–XFFFF (hex) 3, 6, 10 Read and write one or more 16-bit J-Bus registers. Table B.
TAC Xenta Server – Gateway, Technical Manual B Protocols value using the special MOD10k format. The registers can also be reversed, in these cases they are specified as: 32 bit MOD10k Reverse, 48 bit MOD10k Reverse, or 64 bit MOD10k Reverse. • Bit Mask Start and Stop – Allows several signals to be split off from the applicable N-bit subsets of a single register.
B Protocols TAC Xenta Server – Gateway, Technical Manual integer it will produce a real value, so the default DataType would be changed to REAL in this case. • Signal Measurement System – The measurement system parameters need to be manually set to match the absolute form of the register value after conversion by the coefficient gain and offset, being either an enumeration or analogue engineering unit as applicable..
TAC Xenta Server – Gateway, Technical Manual B.2 B Protocols Modbus Serial Line Slave The Xenta 913 can be configured to act as one or more slaves on a Modbus and/or J-Bus serial network to allow an external master to read and write values from an I/NET or LON control system. Both the RTU and ASCII protocol formats are supported. Modbus Slave LON or I/NET Control System Value exchange Xenta 913 RS-485 A Modbus Network RTU or ASCII Master Slave Slave Fig. B.
B Protocols B.2.1 TAC Xenta Server – Gateway, Technical Manual Modbus Slave Networks A Modbus Slave Network consists of a single master and one or more independent slaves interconnected by an RS-485 serial link. While the Xenta 913 is attached to the network it appears as one or more pseudo slave devices to an external master. Through these pseudo slaves the master can write values to the corresponding inputs within the control system, and can also read output values from it.
TAC Xenta Server – Gateway, Technical Manual B.2.2 B Protocols Modbus Slave Devices The Modbus Slave interface is added into the network pane of XBuilder, as shown for an XLink example network in the following screenshot. Interface Properties • Port Type – In most cases the RS-485 port option will be selected. The RS-232 option may be suitable for connecting directly to a master or simulator, but RS-485 will be required if additional slave devices are attached to the Modbus serial line.
B Protocols TAC Xenta Server – Gateway, Technical Manual • B.2.3 online – Flags ONLINE during normal network communications, and will change to OFFLINE only if communication has failed to the master on the Modbus network. An OFFLINE condition normally indicates incorrect communication property settings, or faulty wiring of the network between the Xenta 913 and the master.
TAC Xenta Server – Gateway, Technical Manual B Protocols incorrect device address having been entered, or by incorrect wiring of the network connection to it.
B Protocols B.2.4 TAC Xenta Server – Gateway, Technical Manual Modbus I/O Signals Each Pseudo Slave device represents a logical group of I/O signals within the LON or I/Net control system. The device editor is used to create new pseudo-slave types, or to modify existing types, as shown in the following screenshot. Each signal can be used to allow the Modbus master to access a LON or I/Net value as if it was a register within a slave device.
TAC Xenta Server – Gateway, Technical Manual • B Protocols Register Number– Allows the base number of each required Modbus register set to be selected. The entered number should contain 5 characters in one of the following forms: Table B.3: Register numbers. Number Range Format Functions Description 00001–10000 Decimal 1, 5 Read and write a single-bit coil state. 10001–20000 Decimal 2 Read a single-bit input status. 30001–40000 Decimal 4 Read one or more 16-bit input registers.
B Protocols TAC Xenta Server – Gateway, Technical Manual Notes 134 (184) • The R and R/W I/O options should only be selected for the register types that are described as having read and write capability in the preceding Register Number table. • In a few cases it may be necessary to control a coil or holding register’s value, in which case I/O should be set to Write-only (W) or Read/Write (R/W).
TAC Xenta Server – Gateway, Technical Manual • B Protocols Coefficient Gain and Offset – Allow the raw register value to be converted into the desired absolute units. If the raw register value is a real number then normally no conversion is necessary and the default gain and offset of 1 and 0 can be used. But if the raw register value is an integer then it often needs to have a gain and offset applied.
B Protocols B.3 TAC Xenta Server – Gateway, Technical Manual Modbus TCP Client The Xenta 913 can be configured to act as a client to a Modbus TCP server to allow monitoring and control of one or more slave devices through an I/NET or LON control system. Both the RTU and ASCII protocol formats are supported. Modbus TCP LON or I/NET Control System Value exchange Xenta 913 10Base-T Ethernet LAN 10Base-T Ethernet Modbus Network RTU or ASCII Slave Slave Slave Fig. B.
TAC Xenta Server – Gateway, Technical Manual B.3.1 B Protocols Modbus TCP Networks A Modbus TCP Network consists of one or more clients connected to a server. The server may act as device containing one or more virtual slaves, or as a router to a separate RS-485 serial sub-network containing one or more independent slaves.
B Protocols B.3.2 TAC Xenta Server – Gateway, Technical Manual Modbus TCP Interface The Modbus TCP interface is added into the network pane of XBuilder, as shown for an IPSim example network in the following screenshot. Interface Properties • Server IP Address – Numeric IP address of the applicable Modbus TCP server. The IP address must uniquely identify the server on the network, and be directly accessible to any Xenta 913 clients through their 10Base-T Ethernet connections.
TAC Xenta Server – Gateway, Technical Manual B.3.3 B Protocols Modbus Slave Devices One or more slave devices are added to the Modbus TCP interface node in the network pane of XBuilder, as shown for the Panel slave device of the IPSim example network in the following screenshot. Device Template Device templates having a [Modbus_Ext] filename prefix are used to create Modbus Slave devices in XBuilder.
B Protocols B.3.4 TAC Xenta Server – Gateway, Technical Manual Modbus I/O Signals Each Modbus Slave device represents a specific type of hardware device. There are two main ways to work with Modbus I/O signals, Fixed Address Block and Full Address Range register. Fixed Address Blocks When Fixed Address Blocks is used for the device all data types have to adhere to the fixed address number according to Table B.
TAC Xenta Server – Gateway, Technical Manual B.3.5 B Protocols The Modbus Device Editor Each Modbus Slave device represents a specific type of hardware device. The device editor is used to create new slave types, or to modify existing types, as shown in the following screenshot. Each signal can be used to read or write the value of one or more Modbus registers within any slave devices of the type being defined.
B Protocols TAC Xenta Server – Gateway, Technical Manual Table B.4: Fixed Address Blocks number ranges (Contd.) Fixed Address Blocks number ranges Functions codes Description 30001–40000 4 Read one or more 16-bit input registers. (Input Register) 40001–50000 3, 6, 10 Read and write one or more 16-bit holding registers. (Holding Register) X0001–XFFFF (hex) 3, 6, 10 Read and write one or more 16-bit J-Bus registers. Table B.
TAC Xenta Server – Gateway, Technical Manual B Protocols Register or Holding Register). The first number in the Register Number will not be used for identifying the register type. Note • It is not possible to mix Fixed Address Blocks register table type with Full Address Range register table types in the same device template. • Register Table – If Full Address range is used, select the table type Discrete Input, Coil, Input Register or Holding Register in this column.
B Protocols TAC Xenta Server – Gateway, Technical Manual Xenta 913 to read the register’s value once at start-up before it assumes control of it. Note • The W and R/W I/O options should only be selected for the register types that are described as having read and write capability in the preceding Register Number table. • Coefficient Gain and Offset – Allow the raw register value to be converted into the desired absolute units.
TAC Xenta Server – Gateway, Technical Manual B.4 B Protocols BACnet IP (Internet Protocol) The Xenta 913 can be configured to connect to one or more target BACnet IP devices to allow values within them to be monitored and controlled through an I/NET or LON control system. BACnet IP LON or I/NET Control System Value exchange Xenta 913 10Base-T Ethernet LAN 10Base-T Ethernet BACnet IP Device Network Device Device Device Fig. B.
B Protocols B.4.1 TAC Xenta Server – Gateway, Technical Manual BACnet IP Networks The BACnet IP protocol allows one or more clients to communicate with one or more server devices over a TCP/IP network. Any client can poll a set of devices to read their data values, or can write data values to them if applicable. The Xenta 913 operates as the client. While connected to the network it continuously polls the targeted BACnet IP devices to read the required data values for use within a control system.
TAC Xenta Server – Gateway, Technical Manual B.4.2 B Protocols BACnet IP Interface One or more BACnet IP interface drivers are added into the network pane of XBuilder, as shown for the single IPSim example network in the following screenshot. Interface Properties • IP Address – Sets the IP address that uniquely identifies the server device on the network. The selected address must be directly accessible by the Xenta 913 client through its 10Base-T Ethernet connection.
B Protocols TAC Xenta Server – Gateway, Technical Manual Interface Status Signals The BACnet IP interface driver generates several network specific communication status signals, as described below. • ComsFail – Flags a complete communications failure. Activated only if communications has failed to the target device.
TAC Xenta Server – Gateway, Technical Manual B Protocols Device Template Device templates having a [BACnetIP] filename prefix are used to create BACnet IP network devices in XBuilder. Subsequently, each device node is used to configure communications with a logical group of values within the host server device. Note • The Xenta 913 does not use value grouping when communicating with the target device.
B Protocols B.4.3 TAC Xenta Server – Gateway, Technical Manual BACnet Object I/O Signals Each BACnet IP device represents a specific group of I/O signals within a server device. The device editor is used to create new pseudo device types, or to modify existing types, as shown in the following screenshot. Each signal can be used to read or write the present value a BACnet object within any device signal groups of the type being defined.
TAC Xenta Server – Gateway, Technical Manual B Protocols ever, this means that the Xenta 913 will continuously read the register to fetch the latest value even though it is expecting to have control of it.
B Protocols B.5 TAC Xenta Server – Gateway, Technical Manual BACnet MS/TP (Master Slave/Token Passing) The Xenta 913 can be configured to connect to a BACnet MS/TP serial network to allow monitoring and control of one or more devices through an I/NET or LON control system. BACnet MS/TP LON or I/NET Control System Value exchange Xenta 913 RS-485 A Master BACnet MS/TP Network Slave Slave Slave Fig. B.
TAC Xenta Server – Gateway, Technical Manual B.5.2 B Protocols BACnet MS/TP Interface The BACnet MS/TP interface driver is added into the network pane of XBuilder, as shown for a SrlSim example network in the following screenshot. Interface Properties • Port Type – In most cases the RS-485 port option will be selected.
B Protocols TAC Xenta Server – Gateway, Technical Manual The entered priority is sent with all object value write requests. If the target object is not commendable then the priority is ignored and the last written value is applied. However, if the target object is commendable then the highest priority written value is applied, while lower priority values are ignored.
TAC Xenta Server – Gateway, Technical Manual B.5.3 B Protocols BACnet Target Devices One or more slave devices are added to the BACnet MS/TP interface node in the network pane of XBuilder, as shown for the Panel device of the SrlSim example network in the following screenshot. Device Template Device templates having a [BACnet] filename prefix are used to create BACnet MS/TP network devices in XBuilder.
B Protocols B.5.4 TAC Xenta Server – Gateway, Technical Manual BACnet Object I/O Signals Each BACnet MS/TP device represents a specific type of hardware device. The device editor is used to create new slave types, or to modify existing types, as shown in the following screenshot. Each signal can be used to read or write the “present value” a BACnet object within any network devices of the type being defined.
TAC Xenta Server – Gateway, Technical Manual B Protocols Setting an object’s present-value signal to Read/Write (R/W) allows both monitoring of its value as well as control of it. However, this means that the Xenta 913 will continuously read the register to fetch the latest value even though it is expecting to have control of it.
B Protocols B.6 TAC Xenta Server – Gateway, Technical Manual BACnet PTP (Point To Point) The Xenta 913 can be configured to connect to a target network through a BACnet PTP half router to allow monitoring and control of one or more devices through an I/NET or LON control system. BACnet PTP LON or I/NET Control System Value exchange Xenta 913 RS-232 A BACnet or other Network Device Device Device Fig. B.
TAC Xenta Server – Gateway, Technical Manual B.6.1 B Protocols BACnet PTP Networks The BACnet Point To Point protocol allows two nodes to communicate over either a dedicated RS-232 serial connection or a modem. In either case, each node is termed a half-router because together they are able to route messages between 2 BACnet networks using the RS-232 or modem link. In practice, however, even nodes that do not connect to a BACnet network can still exchange values using the PTP protocol.
B Protocols B.6.2 TAC Xenta Server – Gateway, Technical Manual BACnet PTP Interface The BACnet PTP interface driver is added into the network pane of XBuilder, as shown for a SrlSim example network in the following screenshot. Interface Properties • Port Type – In most cases the RS-232 port option will be selected. The RS-485 option should only be used in the rare case of a target half-router using either RS-422 or RS-485.
TAC Xenta Server – Gateway, Technical Manual B Protocols The entered priority is sent with all object value write requests. If the target object is not commendable then the priority is ignored and the last written value is applied. However, if the target object is commendable then the highest priority written value is applied, while lower priority values are ignored.
B Protocols B.6.3 TAC Xenta Server – Gateway, Technical Manual BACnet Target Devices One or more slave devices are added to the BACnet PTP interface node in the network pane of XBuilder, as shown for the Panel device of the SrlSim example network in the following screenshot. Device Template Device templates having a [BACnet] filename prefix are used to create BACnet PTP network devices in XBuilder.
TAC Xenta Server – Gateway, Technical Manual B.6.4 B Protocols BACnet Object I/O Signals Each BACnet PTP device represents a specific type of hardware device. The device editor is used to create new slave types, or to modify existing types, as shown in the following screenshot. Each signal can be used to read or write the “present value” a BACnet object within any network devices of the type being defined.
B Protocols TAC Xenta Server – Gateway, Technical Manual Setting an object’s present-value signal to Read/Write (R/W) allows both monitoring of its value as well as control of it. However, this means that the Xenta 913 will continuously read the register to fetch the latest value even though it is expecting to have control of it.
TAC Xenta Server – Gateway, Technical Manual B.7 B Protocols M-Bus Metering The Xenta 913 can be configured to communicate with an M-Bus serial adaptor to allow meter monitoring through an I/NET or LON control system. M-Bus LON or I/NET Control System Value exchange Xenta 913 RS-232 A M-Bus Serial Interface M-Bus Network RTU or ASCII Meter Meter Meter Fig. B.
B Protocols B.7.1 TAC Xenta Server – Gateway, Technical Manual M-Bus Metering Networks Each M-Bus Network consists of a number of independent meters that record data on behalf of a master metering application. Each meter may capture and store a number of metered values such as power or water consumption. The master application can then read each metered value as required to record consumption for billing purposes, and so on.
TAC Xenta Server – Gateway, Technical Manual B.7.2 B Protocols M-Bus Metering Interface The Meter Bus interface is added into the network pane of XBuilder, as shown for a PW3 example network in the following screenshot. Interface Properties • Port Type – In most cases the RS-232 port option will be selected. The RS-485 option should only be needed in the rare case of an M-Bus adaptor using either RS-422 or RS-485.
B Protocols TAC Xenta Server – Gateway, Technical Manual Interface Status Signals The Meter Bus interface generates a number of general and meter specific communication status values, as described below. 168 (184) • ComsFail – Flags a complete communications failure. Activated only if communications have failed to all meters on the M-Bus. • MetersFail – Flags if communications have failed to one or more meters on the M-Bus. Will always show FAILED before ComsFail.
TAC Xenta Server – Gateway, Technical Manual B.7.3 B Protocols M-Bus Meters One or more meter devices are added to the M-Bus interface node in the network pane of XBuilder, as shown for the Wh and kWh metering devices of the PW3 example network in the following screenshot. Device Template Device templates having a [MBus] filename prefix are used to create M-Bus Meter devices in XBuilder.
B Protocols TAC Xenta Server – Gateway, Technical Manual Note • Time-outs should be minimized where possible to reduce the amount of time it takes for the Xenta 913 to detect any failed meters. Device Status Signal For each metering device the M-Bus interface driver generates several status signals. 170 (184) • ComsFail – Flags if communications with the meter have failed. May be because of a meter or cable fault, or because of an address mismatch.
TAC Xenta Server – Gateway, Technical Manual B.7.4 B Protocols M-Bus I/O Signals Each M-Bus device represents a specific type of hardware meter. The device editor is used to create new device types, or to modify existing types, as shown in the following screenshot. Each signal can be used to read or write the value of one or more metered values within any meter devices of the type being defined. • Field Type and Sub-Type – Allow the required metered value type to be selected for the applicable meter.
B Protocols TAC Xenta Server – Gateway, Technical Manual • Storage# – Allows the applicable storage level of the Metered Value to be defined. Normally this can be left blank or set to 0 to select the instantaneous metered value. However, to read stored or historical metered values a whole number between 1 and 10 can be entered to represent the storage depth of the required value. Note • Stored values are likely to only update periodically, such as once per month.
TAC Xenta Server – Gateway, Technical Manual B Protocols • Signal DataType – Is set to a default of INTEGER or REAL based on the selected field type. But the default data type may subsequently need to be changed to suit the applied conversion coefficient. For example, if a gain of 0.1 is applied to an integer it will produce a real value, so the default DataType would be changed to REAL in this case.
B Protocols B.8 TAC Xenta Server – Gateway, Technical Manual Clipsal C-Bus Lighting Control The Xenta 913 can be configured to connect to a Clipsal C-Bus serial adaptor to allow monitoring and control of a lighting system through an I/NET or LON control system. Clipsal C-Bus LON or I/NET Control System Value exchange Xenta 913 RS-232 A Clipsal C-Bus PC Interface C-Bus Network RTU or ASCII Fig. B.
TAC Xenta Server – Gateway, Technical Manual B.8.1 B Protocols C-Bus Lighting Networks Each C-Bus Lighting Network consists of a number of input and output nodes. An output node can be a relay or a dimmer that is connected to a bank of lights. An input node can be either human-operated or automated, and can cause messages to be sent to any output nodes OVER the C-Bus to control these banks of lights. Optional C-Bus bridges can be used to extend the number of nodes on a network.
B Protocols B.8.2 TAC Xenta Server – Gateway, Technical Manual C-Bus Lighting Interface The Clipsal C-Bus interface is added into the network pane of XBuilder, as shown for a Workshop example network in the following screenshot. Interface Properties • Port Type – Only the RS-232 option can be used for the Clipsal C-Bus PC Interface. • Baud Rate, Parity, #Data Bits, #Stop Bits – All the communication parameters, such as baud rate and parity, must be set to match those of the C-Bus PC Interface.
TAC Xenta Server – Gateway, Technical Manual B.8.3 B Protocols C-Bus Application Pseudo-Devices One or more application pseudo-devices are added to the C-Bus interface node in the network pane of XBuilder, as shown for the dimmer application of the Workshop example network in the following screenshot. Device Template Device templates having a [CBus] filename prefix are used to create C-Bus application pseudo-devices in XBuilder.
B Protocols TAC Xenta Server – Gateway, Technical Manual cates an incorrect Application# having been entered, or by incorrect wiring of the network connection to it. B.8.4 C-Bus I/O Signals Each C-Bus pseudo-device represents a specific set of lighting groups in an application. The device editor is used to create new pseudo-device types, or to modify existing types, as shown in the following screenshot.
TAC Xenta Server – Gateway, Technical Manual B Protocols allow group control to be cooperatively shared with other control devices. Note B.8.5 • ON Only and OFF Only types are NOT applicable to read-only values. • Group Ramp Rate – Optional parameter that is normally left blank or set to Instant to cause lighting state changes to occur immediately. However, if dimming is available then some other rate may be selected to cause the light level to ramp gradually if preferred.
B Protocols B.8.6 TAC Xenta Server – Gateway, Technical Manual Multiple Read-Only Signals Per Group Variable During normal operation each read-only signal should reflect the state of its associated Group Variable on the C-Bus network. However, input values are only updated in response to C-Bus events, so the value will be “unknown” for 5 to 10 seconds after startup.
TAC Xenta Server – Gateway, Technical Manual Index B BackupLM (folder) 27 BACnet IP (Internet Protocol) 145 BACnet MS/TP (Master Slave/Token Passing) (protocol) 152 BACnet PTP (Point To Point) (protocol) 158 Index F folder add 45 folder structure, see project folder structure G gateway application verify 71 Graphics (folder) 27 C I Clipsal C-Bus Lighting Control (protocol) 174 communication monitor 54 test target communication 100 communication diagnostics 99 communication interface 92 connection man
Index project folder BackupLM 27 DeviceDescr 27 Documentation 27 Graphics 27 VistaDb 27 project folder structure on hard disk 27 project folder, create on hard disk 27 TAC Xenta Server – Gateway, Technical Manual values page add 51 VistaDb (folder) 27 R root folder, rename 44 S serial communication configure 91 signal add 48 change unit of 50 connect to an output SNVT 76 connect to and from LON 64 validate 89 visualizing 47 signal object add 65 SNVT add 73 adding in the TAC Xenta 913 81 define 81 input
Copyright © 2009-2011, Schneider Electric Buildings AB All brand names, trademarks and registered trademarks are the property of their respective owners. Information contained within this document is subject to changewithout notice. All rights reserved. 04-00124-06-en For more information visit www.schneider-electric.
