integración en txopen

8/2/2019 Integracin en TXOPEN

1/32

s

DESIGO TX OPEN

TX SED2

Engineering guide

Version 4 or later

CM110573en_04

15 Jun 2010 Building Technologies


2/32

2 / 32

Siemens TX SED2 CM110573en_04

Building Technologies Contents 15 Jun 2010

Contents

1 About this document ..............................................................................41.1 Revision history.........................................................................................41.2 Reference documents...............................................................................41.3 Before you start.........................................................................................41.3.1 Trademarks ...............................................................................................41.3.2 Copyright...................................................................................................41.3.3 Quality assurance .....................................................................................51.3.4 Document use / request to the reader ......................................................51.4 Target readers ...........................................................................................51.5 Glossary of new terms and abbreviations.................................................62 Introduction .............................................................................................72.1 Position of the SED2 solution....................................................................72.2 Functional scope of and limitations to the USS standard .........................93 Planning and commissioning (predefined solution / template) .......103.1 Overview of commissioning workflow .....................................................103.1.1 Recommendation for commissioning PXC .............................................113.1.2 Commissioning SED2 devices................................................................113.1.3 SED2 compounds and templates ...........................................................123.2 Workflows with TXI1.OPEN ....................................................................133.2.1 Main workflow: using a predefined solution from the library to create data

points.......................................................................................................133.2.2 Main workflow variant:

using predefined templates to create data points ...................................143.2.3 Main workflow variant:selecting additional device points and assigning addresses ..................143.2.4 Creating a configuration..........................................................................143.2.5 Loading a configuration to TXI1.OPEN and checking.............................153.2.6 Updating SED2 slave addresses and communication parameters.........153.3 LED indication .........................................................................................163.4 TX OPEN Tool.........................................................................................163.4.1 Diagnostics..............................................................................................173.4.2 Local overwrite ........................................................................................173.4.3 Emergency position value / default value ...............................................173.4.4 Loading firmware.....................................................................................174 Functionality of the SED2 protocol application.................................194.1 Overview .................................................................................................194.2 Communication .......................................................................................194.2.1 USS protocol ...........................................................................................194.2.2 Polling behavior of the SED2 protocol application..................................204.2.3 Updating Initial values from the SED2 master side ................................214.2.4 BACnet reliability.....................................................................................214.3 Parameters for SED2 devices and communication ................................224.4 Parameters for SED2 data points ...........................................................244.4.1 Data types and mapping data to function blocks ....................................25


3/32

3 / 32


Building Technologies Contents 15 Jun 2010

5 Brief Instructions on SED2 commissioning.......................................265.1 Frequency inverter parameter setting for communication with compound

(standard control in the PX) ....................................................................265.2 Frequency inverter parameter setting for communication with compound(control in SED2).....................................................................................275.2.1 Bus termination in the last SED2 of the network ....................................295.3 Troubleshooting ......................................................................................306 Creating protocol applications for projects (by an RC) ....................317 Technical data .......................................................................................318 SW and FW versions ............................................................................31Index ................................................................................................................32


4/32

4 / 32


Building Technologies About this document 15 Jun 2010

1 About this document

1.1 Revision history

Version Date Changes Section Pages

_04 15 Jun 2010 Bus termination and connection, Fig. 5-4 5.2.1 29

_03 30 Mar 2010 BACnet Reliability 4.2.4 21

_02 24 Nov 2009 Baud rates; RS232 not supported various various

_01 15 Sep 2009 First edition

1.2 Reference documents

Ref. Document Title Document Type Document No.

[1] TX OPEN module Data sheet CM1N8185

1.3 Before you start1.3.1 Trademarks

The table below shows the trademarks and their legal owners that are used in this

document. The use of the trademarks is subject to international and national legal

terms and conditions.

Trademarks Legal owner

BACnet American National Standard (ANSI/ASHRAE 135-1995)

Microsoft Microsoft Corporation; see

http://www.microsoft.com/TRADEMARKS/t-mark/nopermit.htm

USS Siemens Universal Serial Interface Protocol

Windows Microsoft Corporation

WindowsCE Microsoft Corporation

All products listed in the table are registered () or unregistered () trademarks of

the corresponding owner shown in the table. In view of this information, additional

markings (such as the use of symbols like and ) for the trademarks are omitted

in the interest of greater legibility.

1.3.2 Copyright

Reproduction and distribution of this document is only permitted with the express

permission of Siemens and only for authorized persons / enterprises with appropri-

ate technical expertise.
http://www.microsoft.com/TRADEMARKS/t-mark/nopermit.htmhttp://www.microsoft.com/TRADEMARKS/t-mark/nopermit.htm


5/32

5 / 32



1.3.3 Quality assurance

These documents were prepared with great care.

The contents of all documents are checked at regular intervals.

Any corrections necessary are included in subsequent versions.

Documents are automatically amended as a consequence of modifications and

corrections to the products described.

Please make sure that you are aware of the latest document revision date.If you find lack of clarity while using this document, or if you have any criticisms or

suggestions, please contact the product manager in your nearest branch office.

The addresses of the Siemens regional companies are available at

www.buildingtechnologies.siemens.com .

1.3.4 Document use / request to the reader

Before using our products, it is important that you read the documents supplied

with or ordered at the same time as the products (equipment, applications, tools

etc.) carefully and in full.

We assume that persons using our products and documents are authorized and

trained appropriately and have the technical knowledge required to use our

products as intended.

More information on the products and applications is available:

On the intranet (Siemens employees only) at

https://workspace.sbt.siemens.com/content/00001123/default.aspx

From the Siemens branch office near you

www.buildingtechnologies.siemens.com or from your system supplier

From the support team at headquarters [email protected]

there is no local point of contact

Siemens assumes no liability to the extent allowed under the law for any losses

resulting from a failure to comply with the aforementioned points or for the improper

compliance of the same.

1.4 Target readers

The document describes TXI1.OPEN commissioning.

Commissioning with a predefined solution in the library or with a predefined

configuration template is described in section 3.
http://www.buildingtechnologies.siemens.com/http://www.buildingtechnologies.siemens.com/mailto:[email protected]:[email protected]://www.buildingtechnologies.siemens.com/http://www.buildingtechnologies.siemens.com/


6/32

6 / 32



1.5 Glossary of new terms and abbreviations

This table contains important terms (not all inclusive), where, to some extent,

outdated terms are used in the referenced documents.

Term Description

USS The USS protocol is a communications protocol based on a master/slave

architecture and transmitted over a serial interface (applicable standard: EIA-

RS485).

DESIGO Siemens building automation and control system.

AS,

automation station

Controller for the DESIGO system (PXC100, PXC200).

TX I/O I/O modules product range for the DESIGO system.

Island bus Field bus for TX I/O.

TX OPEN Hardware with loaded protocol application for Modbus.

Also includes the associated tools, workflows and files.

TXI1.OPEN ASN for the HW product TX OPEN, island bus device, device for the TX I/O

product range.

Protocol application Software for TXI1.OPEN for processing a specific protocol on the serial bus. Can

be reloaded locally in TXI1.OPEN. This document describes the protocol

application properties for SED2 devices.

XWP XWORKS plus, DESIGO system toolset (as of Version 4).

Point configurator Component of XWP for generating data points and assigning data points to

DESIGO system components, including TXI1.OPEN and data points for

TXI1.OPEN as well.

IOOCD IO OPEN Configuration Description = data exchange file for configuration data

for the TXI1.OPEN device.

IOOPT IO OPEN Point Template = data exchange file for a configuration that describes

a specific third-party device.

IOMD+ Internal data file used to download to the TXI1.OPEN device (content = required

data from IOOCD, XML code).

RS-232 Standardized serial interface, EIA-RS-232.

RS-485 Standardized serial interface, EIA-RS-485.

VSD Variable Speed Drive.

VISUAL C++ Programming language for generating protocol applications.


7/32

7 / 32


Building Technologies Introduction 15 Jun 2010

2 Introduction

2.1 Position of the SED2 solution

10573Z01

PXM20

PXC12-T.DPXC22-T.D

PXC36-T.D

BACnet / LonTalk

PXC100.DPXC200.DPXA40-T

TXS1.12F10

TX-I/O modules

TXI1.OPEN

TXM1.....

PXC12-E.DPXC22-E.DPXC36-E.D

BACnet /IP

PXC100-E.DPXC200-E.DPXA40-TPXA40-W0PXA40-W1PXA40-W2

TXS1.12F10

TX-I/O modulesTXM1.....

WEB clientPXM20-E

DESIGONSIGHT

PXG80-N

BACnetRouter

DESIGONSIGHT

TXI1.OPEN

RS485

TX SED2

PX OPEN Monitor

TX SED2

RS485

Figure 21: TXI1.OPEN in the DESIGO PXC product range

Figure 22: TXI1.OPEN hardware


8/32

8 / 32



SED2 devices are integrated into the DESIGO system using the TXI1.OPEN. TX

OPEN is a package of tools, workflows and files to configure and commission with

DESIGO.

TXI1.OPEN is loaded with the protocol applications for SED2 and then operates as

USS master.

The values of the SED2 data points and the status of the existing data connection

with the data points are transmitted to the automation station (AS) via the island

bus and mapped to BACnet objects in the automation station using duplex

transmission. This way, SED2 data points can be made available to all the devices

and applications in the DESIGO system.

An operator interface is available in the TX-I/O OPEN tool to monitor and analyze

data traffic on the USS for diagnostics, value display and reading of versions.

TXI1.OPEN supports 100 data points. The data points can be freely distributed to a

maximum of 8 SED2 devices.

Createasmanytimesasneeded

Installonce

TXOPEN

Developer Environment

IoOpen

API

library

Application

IOOPEN

Point

Template

IOOCD

CB

TXOPENTool

XWPPointConfigurator

Downloadvia

TXOPENTool

Protocolspecificdevelopment

Commissioningonsite

ApplicationEngineering

IOOPEN

Point

TemplateRelatedtemplate

TXOPENTool

EmbeddedVisualC ++

Protocol

Diagnostics

Figure 23: Overview of TX OPEN


9/32

9 / 32



2.2 Functional scope of and limitations to theUSS standard

Software options:

Use as USS master

Hardware option

RS485 bus connection: with / without bus connection.

Bus connection = terminating resistor (120 ).

Table 21: Supported USS task IDs

Task ID Description

1 Request paramter value

3 Change parameter value (double word) [RAM only]

33 New task ID for control of the STW (on/off & fault ack.)

34 New task ID for control of the setpoint value (HSW)

Cannot be used as a USS slave in the described protocol application.

Maximum of 100 points from the SED2 as the sum total for all devices.

Recommended are 3 20 points per SED2, depending on the application

Extreme values:

100 for exactly 1 SED2 device.

Maximum of 8 SED2 devices

Functional scope

Limitations


10/32

10 / 32


Building Technologies Planning and commissioning (predefined solution / template) 15 Jun 2010

3 Planning and commissioning(predefined solution / template)

This section describes commissioning using a predefined solution in the library or

a predefined configuration template.

3.1 Overview of commissioning workflow

To commission, the configuration is loaded with the DESIGO tools XWP (DESIGO

XWORKS Plus) via USB to the TXI1.OPEN device and the automation station

(ALCORE Modular V4) is set up.

INSIGHT

BACnet

PXCModular

V4

TX- IO

modules

TXI1.

OPEN

3rd-PartyRS232,

RS4845

XWP- DESIGOXWORKSplus

IOCV4V4IOC

Download

CFC

Point

Configurator

IOOCD

Downloadvia

TXOpenTool

TXOpen

Tool

TXOpen

Tool

IOOCD

IOOpenCFC

Solutions

Protocol

Application

IOOpenPoint

Template

Step1Step2

Step3

Islandbus

Figure 31: Overview of commissioning workflow

Overview


11/32

11 / 32



1. Use the four predefined solutions tailored for the device from the library

(CAS library from HQ).

Tip: Each TX OPEN solution has an IO OPEN point template.

2. In XWP and specifically in the Point Configurator: Set device address,

deselect unused points, extend the application program and create the

IOOCD and IOC configuration files for the following devices on the island

bus:

TXI1.OPEN (IOOCD file) and PXC (IOC file).

3. From XWP, start the TX OPEN tool for the project using the correct IOOCD

file. Set communications parameters

Load the IOOCD file.

Commission with the help of the diagnostics functions of the TX OPEN tool.

3.1.1 Recommendation for commissioning PXC

The TX OPEN tool is used to load IOOCD on the TXI1.OPEN. This must becoordinated with IOC load to PXC to ensure that the devices do not attempt to

communicate on the island bus using differing definitions.

3.1.2 Commissioning SED2 devices

This section expands on the commissioning workflow with information on how to

enter SED2-specific parameters.

In step 1, an SED2 solution is selected using the Point Configurator.

All points are then assigned to a TX OPEN module. This can be repeated for

multiple SED2 devices. A CFC program can be created. The SED2 function can

also, however, be verified without the CFC program using the TX OPEN tool.

In step 2, the SED2 slave address is entered using the Point Configurator.

No. 1 is the default setting.

Note: This parameter can also be entered later in the TX OPEN tool, but in this

case the changes in XWP must be reproduced in the project according to the

section "Updating Device Addresses and Comm. Settings".

Figure 32: Setting up the device address in the Point Configurator

Steps

Selecting device and

points with XWP

Setting up the device

address


12/32

12 / 32



In step 3, go to the TX OPEN tool from the Point Configurator. The bus communi-

cations settings are tested and, at most, modified in the TX OPEN tool.

Communication settings (for each device) are optional and are only required if

different from default. The configuration is then loaded into the TX OPEN

module.

Figure 33: Setting up communication parameters in the TX OPEN tool

TX OPEN tool initially checks in the "Diagnostics" page whether the download was

correct after the configuration is downloaded. The SED2 points can then be directly

retrieved from the "Values" page.

3.1.3 SED2 compounds and templates

Two compounds are provided for pumps and fans in each case.

Table 31: Compounds and templates

Compound Template (IOOPT) Protocol application

FanMdSED2 FanMdSED2_lib.ioopt SED2_HQ_V4.00.223.exe

FanPSED2 FanPSED2_lib.ioopt SED2_HQ_V4.00.223.exe

PuMdSED2 PuMdSED2_lib.ioopt SED2_HQ_V4.00.223.exe

PuPSED2 PuPSED2_lib.ioopt SED2_HQ_V4.00.223.exe

The functional descriptions are contained in the "Help on Compounds" found in the

application library.

Setting up

communication

Testing

communication


13/32

13 / 32



3.2 Workflows with TXI1.OPEN

The section describes the workflows included in the TXI1.OPEN. The workflows

are described in greater detail in the documentation and in the help functions for

XWP and the TX OPEN tool. The workflows are only outlined here.

3.2.1 Main workflow: using a predefined solution from thelibrary to create data points

1. In XWP:

Set up the network, then the automation station (AS).

Relation to TXI1.OPEN: Select AS with island, since TXI1.OPEN is an island

bus device.

2. Go to the XWP Point Configuration (Tools menu).

3. In the Point Configurator:

Select Get data points out of solution to enter the desired mode.

4. In this mode:

Select New plant/new area and then a solution with New solution.

Relation to TXI1.OPEN: Select one of the four predefined SED2 solutions for

TXI1.OPEN. All points of the template belonging to the solution appear in the

point table.

5. Deselect unwanted points.

Relation to TXI1.OPEN: You may only clear, but not add, points. Adding

requires a new template (see below).

6. Select Create data points.

7. Drag all points to the lower section of the window using drag and drop.

Relation to TXI1.OPEN: Dragging an individual point is enough to add all

points for the TXI1.OPEN to the module. If no TX OPEN module is yet

available, a new one is automatically created.

8. Set the device addresses on the Modbus.

Relation to TXI1.OPEN: Only this input is required. All other addresses and

parameters are predefined in the template.

9. Create the points in the CFC and then create the IOC.

10. Select Navigate to TX OPEN tool in the Point Configurator or in the CFC.

This creates the IOOCD and opens the TX OPEN tool with this file.

Relation to TXI1.OPEN: The integration is then taken into operation in the TX

OPEN tool. The configuration is downloaded and then checked using the

diagnostics help functions.11. Optional concluding work: Check the created configuration in the TX OPEN

tool (see Section 3.2.4 for details). You may change communication settings

that must then be reloaded to the XWP for the customer project.

Relation to TXI1.OPEN: The configuration verified and modified in the TX

OPEN tool is saved for later changes in this way.


14/32

14 / 32



3.2.2 Main workflow variant: using predefined templates tocreate data points

The initial steps differ to some extent from the main workflow as follows:

1. In XWP:

Set up the network, then the automation station (AS).

Relation to TXI1.OPEN: Select AS with island, since TXI1.OPEN is an island

bus device.2. Go to the XWP Point Configuration (Tools menu).

3. Select "3rd-party subsystem with template".

4. Select "New IO Open Integration via point template" and find your template in

the subsequent dialog box.

5. Continue with the main workflow at "Deselect unwanted points".

3.2.3 Main workflow variant: selecting additional devicepoints and assigning addresses

You can use the XWP Point Configurator to add and remove points as follows:

You can reactivate deselected points from the template in the Point Configurator

in the same user interface where the deselection occurred.

A library compound may not have activated all possible points of the template. In

this case, you can add additional points in the Point Configurator.

Different first steps in the main workflow:

1. In the XWP Point Configurator, go to the TXI1.OPEN device.

2. From the template, select the additional data points or remove unneeded data

points.

3. Continue with the device / point list created in this way in the main workflow

from "Select Create data points".

Limitations:

You can only clear points from the template; you cannot add new ones. A new or

modified template is required to add new points.

You can only change point addresses by changing the template

(troubleshooting) or creating a modified template (device variants).

3.2.4 Creating a configuration

Part of the main workflow executed when changes are made to the program in theCFC.

Preparations

Points and devices are created using CFC, Point Configurator and elements

from the library and template.

Steps

1. In the Point Configurator or in the CFC, select Navigate to TX OPEN tool to

create the configuration file (IOOCD).

2. In the Point Configurator, select Start TX OPEN tool with this file.


15/32

15 / 32



Additional task

Optional: Send the created IOOCD to the panel builder (mail, ), using the

"Pack and Go" function in the Point Configurator.

3.2.5 Loading a configuration to TXI1.OPEN and checking

Preparations

Create the configuration as described in the section "Creating a Configuration".

Start the TX OPEN tool with the IOOCD file created in XWP.

Steps

1. The IOOCD is visible in the TX OPEN tool (in the grid). Check the IOOCD

visually.

2. Load the IOOCD to TXI1.OPEN (USB connection).

3. Commission with the aid of the Diagnostic tabs: Version, Diagnostics, Values.

4. Verify the commissioning.

5. You can modify the setting parameters for the USS communication (e.g.

telegram timeout delay, device addresses, etc.) in the TX OPEN tool and then

download them (step 2).

Concluding work

When commissioning, COMM settings and slave addresses may change. These

are located in the modified IOOCD file (save).

Update the settings in the Point Configurator using Import IOOCD file and

check the log window for errors.

In the Diagnostics tab, select Expert to read IOOCD problems that could not be

checked in advance by the tools; in particular, errors in USS parameters.

3.2.6 Updating SED2 slave addresses and communicationparameters

Preparations

When commissioning you can change the communication parameters (comm.

settings) and SED2 slave addresses in the TX OPEN tool.

Using the TX OPEN tool, load the configuration to the TXI1.OPEN and check

communications using the diagnostic tools.

Click "Save" to save the changes to the IOOCD file.

Steps

1. In the Point Configurator, read the IOOCD using Import IOOCD file.

2. The changes are applied.

Note


16/32

16 / 32



3.3 LED indication

The LEDs indicate activities on the island bus and on the serial interface (one color

each for receive and transmit).

Normal state

RUN (green) The LED indicates whether island bus communication isoperating. Constant green means that communications

are running.

COM (green/red) The LED indicates communication on the RS side.

Red = TX (transmit); green = RX (receive).

Error: Only TXI1.OPEN sends if the color does not

change. No devices respond. The color is then stable or

flashes red.

Error state

RUN (green) The LED flashes in the event of an error.

No indication (neither flashing nor lit) indicates that the

device is only operating to a limited extent.

COM (green/red) Continuous red indicates an error. Flashing red withoutintermittent short, green flashing indicates that the deviceis operating in principle but none of the connecteddevices are responding. This occurs, for example, whencommunication is not set up correctly (such as anincorrect baud rate, incorrect parity, etc).

3.4 TX OPEN Tool

The TX OPEN tool is integrated and documented in XWP (Help function).

The following is a short list of the main functions:

The tool can be started from XWP with preselected options. The tool may,

however, be used separately.

It reads the IOOCD configuration files created by XWP and presents it in a table.

It allows changes, limited to commissioning parameters for the RS232/RS485

connection.

It loads the IOOCD configuration files to the TXI1.OPEN device. It loads the protocol applications to the TXI1.OPEN device.

It loads a new platform to the TXI1.OPEN device.

It presents diagnostics information from the TXI1.OPEN device.

It creates templates.

Backup/restoration of the loaded application and configuration data.

Back up of the log files.


17/32

17 / 32



3.4.1 Diagnostics

The TX OPEN tool has diagnostic functions for TXI1.OPEN. You can read data

such as software versions, device and point setting parameters, present values,

present states and protocol inspection.

3.4.2 Local overwrite

The TX OPEN tool has a function to overwrite an output value temporarily or

permanently:

Temporary: Until closing the view in the TX OPEN tool or until the USB

connection is interrupted.

Permanently: Until the next generation of a configuration (persistently stored

in the device).

Note: Local Overwrite always suppresses all present values and emergency

positioning values. The present valid values or emergency positioning values are

sent upon exiting Local Overwrite.

3.4.3 Emergency position value / default value

The emergency positioning value is defined in DESIGO at the point and

transmitted via the island bus to the TX OPEN module.

The TX OPEN tool has a data field (DefaultValue) for defining the emergency

position value that is output as long as no emergency position value has been sent

via the island bus.

3.4.4 Loading firmware

The firmware is preinstalled. The TX OPEN tool is used to reload the firmware.

The firmware comprises platform and protocol applications. HQ supplies the

platform together with a protocol application in the TXI1.OPEN device. The platform

allows reloading of protocol applications.

The protocol application delivered by default must be overwritten by the right

protocol application once before loading the configuration.

The platform is based on the real-time operating system Windows CE.

The platform comes with Windows CE. Windows CE is licensed for the device.

HQ supplies some protocol applications. RCs can create their own protocol

applications. The platform allows creation of protocol applications, but only by staff

with specialized programming knowledge. Instructions can be obtained from HQ.

TXI1.OPEN contains a default protocol application that can be used for testing.

This protocol application can be used to trigger data transfer on the island bus and

serial bus.


18/32

18 / 32



HQ supplies protocol applications for widespread protocols and oft-used devices

with the library, including the SED2 protocol application described here.

You install the protocol application in the TXI1.OPEN using the TX OPEN tool.

After device restart, load the configuration and take the device into operation with

its communications via the island bus and RS232 or RS485.

The latest version of the platform and protocol application supplied by HQ is

available for download from the intranet.

Downloading is recommended, but is only required if the protocol application

supplied with the current library does not include the latest functions or if specific

troubleshooting actions are needed for the specific plant.

The latest deliveries for download are available on the Field Support WEB page

under TXI1.OPEN at:

https://intranet.sbt.siemens.com/swanweb/en/webcrawl/?src=txio

The platform is supplied with the device already loaded. The TX OPEN tool can be

used to reload the platform. The platform can be ordered from the Field Support

WEB page, along with a description of the installation:

https://intranet.sbt.siemens.com/swanweb/en/webcrawl/?src=txio

Loading a protocol

application from HQ

Updating platform and

protocol applications

from HQ

Loading the platform
https://intranet.sbt.siemens.com/swanweb/en/webcrawl/?src=txiohttps://intranet.sbt.siemens.com/swanweb/en/webcrawl/?src=txiohttps://intranet.sbt.siemens.com/swanweb/en/webcrawl/?src=txiohttps://intranet.sbt.siemens.com/swanweb/en/webcrawl/?src=txiohttps://intranet.sbt.siemens.com/swanweb/en/webcrawl/?src=txiohttps://intranet.sbt.siemens.com/swanweb/en/webcrawl/?src=txio


19/32

19 / 32


Building Technologies Functionality of the SED2 protocol application 15 Jun 2010

4 Functionality of the SED2 protocolapplication

4.1 Overview

The SED2 protocol application enables integration of data points from SED2

devices to the DESIGO system. The values of the SED2 data points and the status of the data connection at the

time of the data point are mapped by the SED2 protocol application to BACnet

objects.

The hardware platform consists of system controllers from the PXC series together

with TXI1.OPEN. The data sheet CM2N8185de/CM2N8185en describes the

device.

Maximum number of SED2 data

points:

100

Number of SED2 slaves inTXI1.OPEN:

Limited by 100 data points; maximum 31devices on the USS bus.

Electrical interface: RS232 (peer to peer) / RS 485 (multidrop) /

RS 485 T (with terminating resistor)

Baud rate: 2400, 4800, 9600, 19200, 38400, 57600,

76800, 93750, 115200 baud

! TX SED2 only supports RS485 and RS485T, not RS232 !

! TX SED2 only supports Baud rates up to 9600 baud !

Task ID Description

1 Request parameter value

3 Change parameter value (doubleword) (RAM only)

33 Used for control word (STW) to start and acknowledge

34 Used for the main setpoint word (HSW) to send the setpoint value

Task IDs 33 and 34 are not official USS protocol IDs. They are only used internally

at the company to be able to activate the SED2 devices by STW and HSW and to

specify setpoint values.

4.2 Communication

4.2.1 USS protocol

The following section provides only a brief overview of the USS protocol.

For detailed specifications, see "Using USS Protocol with SED2".

The USS protocol is a master/slave protocol. By definition, this means that a USS

network contains one, and only one, master and at least one slave.

Hardware platform

Technical information

Supported USS task

IDs

Master/slave protocol


20/32

20 / 32



The USS master starts the transactions in the network with a slave query. The

addressed slave responds to the query either positively (Reply ID) with the task ID

requested in the query, or negatively (Reply ID).

The transaction type is defined by the task ID provided in the query telegram.

Task ID Description Positive

reply ID

Negative reply ID

1 Request parameter value 1 or 2 73 Change parameter value

(doubleword) (RAM only)

2 7 or 8

33 Used for control word (STW)

to start and acknowledge

None None

34 Used for the main setpoint

word (HSW) to send the

setpoint value

None None

4.2.2 Polling behavior of the SED2 protocol application

The SED2 master periodically reads the data points from the slaves using the

appropriate task IDs (1, 2, 33 or 34). If a slave fails to respond, the master waits

after each query for the timeout period to elapse. This causes a minor delay in the

exchange of data with the slaves that are responding.

To avoid this situation, the SED2 protocol application acts as the SED2 master as

follows:

The telegram is repeated.

If the slave still fails to respond, pending queries (reading or writing) for this

slave are skipped until all the pending queries for the other slaves have been

processed once.

01580

Slave 1 / Telegram 1







(3 x) Timeout

Transactions on the

USS bus

Task ID / reply ID

A) Slave fails to respond

to polling by the master


21/32

21 / 32



The telegram is repeated.

If the slave continues to respond with an exception message, the next pending

query is transmitted.

01581








(3 x) Exception

The status of the SED2 data points is mapped to the parameter [Rlb] (Reliability),see Section 4.2.4 on BACnet Reliability).

4.2.3 Updating Initial values from the SED2 master side

The task IDs 3, 33 and 34 are used to write data point values to the SED2 slave.

These values are written once when starting the master (positively acknowledged)

and then only each time the data point value changes.

Since a value is only updated after being changed in the master, there is a danger

of inconsistency after a reset or replacement of the SED2 slave device.To prevent this happening, the SED2 protocol application provides the following

mechanism in master mode:

If a slave does not respond to queries sent by the master within a specified time, all

values are written to the slave again after a new connection has been set up

(Connected).

4.2.4 BACnet reliability

The status of the SED2 data points is mapped to the parameter [Rlb] (Reliability).In the standard I/O blocks, an Rlb parameter is available for each SED2 data point.

Reliability value Meaning in the master

NO_FAULT_DETECTED The connection between data point and slave is

OK.

PROCESS_ERROR Setting parameter error.

UNRELIABLE OTHER The slave responds with a negative reply ID.

INVALID VALUE Error during data conversion.

Additional information can be obtained using TX OPEN tool (diagnostics) in the

event of an error.

B) Slave responds to a

query by sending an

exception message

Note


22/32

22 / 32



If one or more slaves fail to respond, the SED2 master normally sets the Reliability

parameter of all the affected I/O blocks to UNRELIABLE_OTHER. In the case of a

common source, a very large number of alarms can be triggered (a "burst"), which

can overload the entire system.

This burst can be prevented if an alarm reference point is selected for each device

and all other points are mapped to simple system objects without alarm handling.

4.3 Parameters for SED2 devices andcommunication

Information for the devices is stored in three fields:

ThirdDevice DevAddr containing a number, the device address.

ThirdBus BusType RS485, RS485T (with terminating resistor).

GlobalCommSettings, BusCommSettings or DeviceCommSettings containing a

string with a number of fixed parameters followed by optional additional

information.

The data in these engineering fields are not checked when entering them into XWP

and TX OPEN TOOL. Errors are only indicated if the data type was not correctly

specified.

GlobalCommSettings and DeviceCommSettings are used for monitoring

communication. A USS network is normally operated with just one communications

type that is set in the GlobalCommSettings.

The parameters are preset in the POINT template. The template is adapted to the

plant in the Point Configurator and TX OPEN tool, and is transferred from the Point

Configurator to the TX OPEN tool and downloaded from there to TXI1.OPEN asthe IOOCD.

These parameters are read after each power up and for each change to the

configuration. In other words, changes during runtime take effect only after a restart

of TXI1.OPEN or after the download of a new IOOCD with the TX OPEN tool.

Structure of the setting parameters in the GlobalCommSettings and

DeviceCommSettings fields:

"Baudrate,Parity,Length,Stopbit,,FrameTimeout,CharTimeout,/T_offTimeout"

Suppressing alarm

messages in the event

of a bus failure

Monitoring

communication


23/32

23 / 32



Table 41: Setting parameters for communication

Type Input field Description Example

Device

address

SED2 address 1 .. 31

1

Bus type BusType RS485, for RS485 with/without bus termination(RS485, RS485T) RS485

Baud

rate

CommSettings Baud rate in the USS network:

600 / 1200 / 2400 / 4800 / 96009600

Parity CommSettings Parity in the USS network

N: No parity; E: Even; O: Odd; M: Mark parity;

S: Space parity.

E

Length CommSettings Number of data bits per character in the USS network:

8 (fixed).8

Stopbit CommSettings Number of stop bits in the USS network:

1 1.5 2. 1

FrTmo CommSettings Not used.

ChTmo CommSettings Not used.

T_off CommSettings Due to many problems in communication between the

USS network and the former PTE modules, a new

function is implemented in TX SED2, which allows

delaying of communication fault messages.

This T_off value (0 65535 ms) defines a time after

which a fault in communication will be generated if no

telegram or no valid telegram is received.

A 6000 ms time delay is configured by default.

T_off=0 will disable the delay and a communicationfault is generated immediately if no telegram is

received.

6000

Assumption of communications by the TXI1.OPEN and its slave devices must be

monitored as much as possible with a tool working with the communications cable.

As an alternative, you can set the "/TRACE" in the GlobalCommSettings

parameters in the IOOCD. This starts the trace with the first telegram sent by the

master in the USS network.

Do not forget to turn the device off! Risk: Files are created continuously, reducingthe lifetime of persistent memory.

When TXI1.OPEN is communicating, the exchanged telegrams can be viewed in

the TX OPEN tool with the following operation:

Diagnostics >Expert button opens the expert page with abundant information

on the device, software versions, the bus state and the selected parameters.

Use the buttons ProtocolAnalyserand ProtocolLog on the expert page.Start

and stop the logs on these pages.

Monitoring

communication

STOP Attention


24/32

24 / 32



4.4 Parameters for SED2 data points

The information for the data points is stored in 2 fields:

ThirdConversionSet containing 4 numerical values: MI1;MI2;MI3;MI4

ThirdSignalType containing a text with the data type "Data type" and optional

additional information.

The data in these engineering fields are not checked when entering them into XWP

and TX OPEN TOOL. Errors are only indicated if the data type was not correctly

specified.

Table 42: Setting parameters for the data points

Element Meaning Ranges Description

Device address SED2 address 1 .. 31 SED2 slave address; set on the

device and does not have to be

repeated at the point

MappingInfo1 USS task ID 1,3,33,34 Task ID with which the data pointis transmitted

MappingInfo2 Parameter no. R / P

0 .. 65535

R for read and P for write

accesses.

Parameter number of SED2

devices

MappingInfo3 Index 0 .. 32 Parameter index

MappingInfo4 Bit 0 .. 32 Parameter bit

Data Type Data type UINT16,

UINT32,

FLOAT

Free syntax Not used

The index and bit of parameter numbers can be viewed in the parameter overview

of the SED2 drive. Basically speaking, there are three different configurations.

Figure 41: Reading parameter bit fields


25/32

25 / 32



Figure 42: Reading parameter indexes

Figure 43: Write parameter

4.4.1 Data types and mapping data to function blocks

Supported function blocks: AI, AO, DI, DO, MI, MO, CI.

Note: These are resource types in V4. Sometimes there are multiple types of

function blocks for each resource type for example, function blocks CI and ACC

for resource type CI.

The data with the data types U8, U16, U32, F32 are transmitted via the island bus.

These types are automatically used when creating the function blocks.

Note: Additional processing functions are available in the function blocks

depending on the block (e.g. Slope/Intercept).

DataType designates the data type in which the SED2 data point is mapped. The

following types are implemented: UINT16, UINT32, FLOAT


26/32

26 / 32


Building Technologies Brief Instructions on SED2 commissioning 15 Jun 2010

5 Brief Instructions on SED2commissioning

5.1 Frequency inverter parameter setting forcommunication with compound

(standard control in the PX)

In order for the TX-OPEN module to be able to communicate with the frequency

inverters using the USS protocol, the following parameters must be set with the

appropriate values in the frequency inverter. The procedure for changing

parameters can be referenced in the documentation for the SED2 frequency

inverter e.g., in the document CM1G5192.

Figure 51: Control schematic in the PX

P0003 = 4 For defining user access stage filters4=Expert: Enables USS settings to be made (including PKW)

P3950 = 46 User access stage password

46=Release that enables USS settings to be made (includingPKW)

P0700[0] = 5 For selection of a command source5=USS on COM link

P1000[0] = 5 For selection of the frequency setpoint value5=USS on COM link

P2009[0] = 1 USS standardization (serial interface COM link)1=Released

P2010[0] = 6 USS baud rate (serial interface COM link)6=9600 baud

P2011[0] = 1 ... 31 USS address (slave address)Address range from 1 to 31

P2013[0] = 4 USS PKW lengthDefines the number of 16-bit words in the PKW section of the

USS telegram.

4 = PWK length always has 4 words

P2014[0] = 0 ... 65535 ms USS telegram downtime

If no telegram is received via the USS channels during this

period, an error is triggered on the SED2 (F0072).


27/32

27 / 32



The frequency setpoint value of the PX is then written to the SED2 parameter

P2018[1] (access level 4 with password required, see above).

r2018[8] CO: PZD


28/32

28 / 32



P2011[0] = 1 ... 31 USS address (slave address)

Address range from 1 to 31

P2013[0] = 4 USS PKW length

(Defines the number of 16-bit words in the PKW section of

the USS telegram)=

4 = PWK length always has 4 words

P2014[0] = 0 ... 65535 ms USS telegram downtime

If no telegram is received via the USS channels during this

period, an error is triggered on the SED2 (F0072).

P2200 [0] = 52.2 Release of PID controller in SED2

BiCo link so that the PID controller in SED2 is activated when

releasing the SED2.

P2253 [0] = 2224 Source of the PID setpoint value

BiCo link so that the PID controller in SED2 uses the setpoint

value that is sent by the PX.

P2280 = 0 65 PID proportional amplification

Enables setting of the proportional amplification for the PID

controller in SED2.

P2285 = 0 65535 ms PID integration timeSets the integration time constant for the PID controller in

SED2.

P2306 = 0 or 1 PID operating direction

Same direction = 0 = increasing plant power causes

increased controller power.

Opposite direction = 1 = falling plant power causes reduced

controller power.

The PID setpoint value of the PX is now written to the SED2 parameter P2201

(access level 3).

P2201 Fixed PID setp. 1 Min: -200.00CStat: CUT Datatype: Float Unit: % Def: 0.00P-Group: TECH Active: Immediately QuickComm.: No Max: 200.00

Defines Fixed PID Setpoint

Note on installation of the frequency inverter

To obtain correct communication between the TX-OPEN module and frequency

inverter, the electric installation of the frequency inverter must strictly conform with

the EMC specifications of the SED2 commissioning manual (CM1G5192).


29/32

29 / 32



5.2.1 Bus termination in the last SED2 of the network

Non-terminated bus lines can generate errors during the data transmission. The

RS-485 bus should therefore be terminated. This is implemented by means of

terminating resistors at the start and end of the bus.

An active termination is recommended for the last SED2 frequency inverter at the

end of the bus. A resistor network is provided for this purpose; it can be acquired

under the ASN SED2-RS485-NT in a minimum quantity of 100 items.

Figure 53: Connection of the SED2-RS485-NT resistor network:

The resistor network is to be connected

to the last SED2 frequency inverter of

the bus as shown in the adjacent figure.

1.5 k 120 470 10573Z21en

+10 Verminal 1

P+Terminal 29

N-Terminal 30

0VTerminal 2

Figure 54: Connections and wiring


30/32

30 / 32



5.3 Troubleshooting

The SED2 starts and stops correctly. All values and status information sent to the

PX are also correct, but the output frequency of the SED2 always remains at the

minimum value.

Check that the compound is correct

Check the USS standardization settings in the P2009

Check the transmitted value in the corresponding register (r2018[1] or P2201

see above)

The SED2 values are correctly displayed in the PX while the SED2 is in standby.

Once the SED2 is started, the communication between TX-OPEN and SED2

breaks down.

The electrical installation of the SED2 does not conform to the EMC

specifications given in the SED2 commissioning manual. Ensure that the

electrical installation fully (100%) satisfies the specifications stated in the SED2

commissioning manual.

The key points are as follows:

Potential equalization on the SED2 (16 mm)

Potential equalization on the motor (16 mm)

Potential equalization on the control panel of the TX mounting rail (16 mm)

Motor cable shield well connected at both ends (SED2 and on the motor) with

potential equalization

Motor cable shield in the inspection switch is well connected (no gaps in the

shielding are permitted)

If there is a suspicion of insufficient potential equalization of the SED2, you can

try not to lay the bus cable shield on the SED2 in order to prevent the EMCinterference that has not been dissipated by the shield from being propagated

through the bus cable shield, thereby interfering with the communication

between TX-OPEN and the SED2.

Error scenario 1

Error scenario 2


31/32

31 / 32


Building Technologies Creating protocol applications for projects (by an RC) 15 Jun 2010

6 Creating protocol applications forprojects (by an RC)

HQ offers advanced training. Participants must have solid knowledge of C++

programming and basic knowledge of DESIGO. The course provides the

necessary tools and know-how to create new protocol applications. This

specifically includes development environment, programming guides, interfacedescriptions, source samples, and template samples.

Hosting and course prices by agreement.

Note: Normally, no programming is required to define additional devices in existing

protocol applications. It is enough to create a template. Examples of templates for

Modbus are provided by the library. You can edit the templates in the TX OPEN

tool or use them to create new templates.

7 Technical data

For technical data, refer to the following documents:

Type Device Data sheet

PXC00... System controller with island bus communication N9225

TXI1.OPEN TX OPEN RS232/485 module N8185

TX OPEN tool (online help) --

Point Configurator in XWP (online help) --

8 SW and FW versions

See Release Notes CM1N8185en.doc.


32/32

Index

AApplication ............................................................19

BBACnet reliability...................................................21

CConfiguration template..........................................10

DData conversion....................................................25

Diagnostics .............................................................8

MMaster/slave protocol............................................19Modbus master .......................................................8

Polling................................................................20

PPolling................................................................... 20

Predefined solution............................................... 10

Predefined template ............................................. 10

RReliability Rlb........................................................ 21

TTX OPEN tool ....................................................... 24

UUpdating initial values .......................................... 21

XXWP ..................................................................... 24

Siemens Switzerland Ltd

Industry Sector

Building Technologies Division

International Headquarters

Gubelstrasse 22

CH-6301 Zug

Tel. +41 41-724 24 24

Fax +41 41-724 35 22 2009 - 2010 Siemens Switzerland Ltd
http://www.buildingtechnologies.siemens.com/