communication via ethernet with visonik bps v20.06

s

VISONIK® Communication via Ethernet with VISONIK BPS V20.06 Documentation on basics

Building Technologies

CM110662en_01 26.11.07 For internal use only

Siemens Switzerland Ltd Building Technologies Group International Headquarters Gubelstrasse 22 CH-6301 Zug Tel. +41 41-724 24 24 Fax +41 41-724 35 22 www.siemens.com/sbt

© 2007 Siemens Switzerland Ltd Subject to change

2 / 32 For internal use only

Siemens Communication via Ethernet with VISONIK BPS CM110662en_01 Building Technologies 26.11.07

http://www.siemens.com/sbt

Table of contents

1 Revision history ......................................................................................4 2 Introduction .............................................................................................5 2.1 About this document .................................................................................5 2.2 Terms and abbreviations...........................................................................6 2.3 Purpose of BPS firmware V20.06 .............................................................7 2.4 BPS hardware product range....................................................................8 3 Configuration...........................................................................................9 3.1 Overview ...................................................................................................9 3.2 General .....................................................................................................9 3.2.1 Hardware / Firmware identification ...........................................................9 3.2.2 Communication parameter settings ........................................................10 3.2.3 TTY parameter settings........................................................................... 11 3.3 Configuration as Net-BPS.......................................................................12 3.3.1 Hardware combinations ..........................................................................12 3.3.2 Communication parameter settings ........................................................12 3.3.3 Commissioning workflow ........................................................................13 3.4 Configuration as Net-ECU ......................................................................14 3.4.1 Hardware combination ............................................................................14 3.4.2 Communication parameter settings ........................................................14 3.4.3 Commissioning workflow ........................................................................15 3.5 Configuration as Tele-BPS......................................................................16 3.5.1 Hardware combinations ..........................................................................16 3.5.2 Communication parameter settings ........................................................16 3.5.3 Commissioning workflow ........................................................................17 3.5.4 Brief instructions for configuration on the DCS.......................................18 3.6 Configuration as Tele-ECU .....................................................................19 3.6.1 Hardware combinations ..........................................................................19 3.6.2 Communication parameter settings ........................................................19 3.6.3 Commissioning workflow ........................................................................19 3.7 Configuration as SDLC-BPS...................................................................20 3.7.1 Hardware combinations ..........................................................................20 3.7.2 Communication parameter settings ........................................................20 3.7.3 Commissioning workflow ........................................................................21 3.8 P-bus and TX-I/O settings.......................................................................22 4 Network communication ......................................................................23 4.1 Overview .................................................................................................23 4.2 Information on protocols .........................................................................23 4.3 Configure IP addresses ..........................................................................25 4.4 Operate via network................................................................................26 4.4.1 Operation via DCS ..................................................................................26 4.4.2 Operation via Visotool .............................................................................26 4.4.3 Operation from another PS.....................................................................26 4.5 Programmed data exchange...................................................................27 4.5.1 Exchange data with DEX (data exchange) .............................................27 4.5.2 Exchange data with MSG / REP (message / report) ..............................29 4.5.3 Exchange ASCII strings ..........................................................................29

For internal use only 3 / 32

Siemens Communication via Ethernet with VISONIK BPS CM110662en_01 Building Technologies Table of contents 26.11.07

1 Revision history

Version Date Changes Section Pages 20.06 26.11.2007 New document


Siemens Communication via Ethernet with VISONIK BPS CM110662en_01 Building Technologies Revision history 26.11.07

2 Introduction 2.1 About this document

This document describes the new functions of BPS firmware V20.06 as compared to earlier versions. These primarily are an improved functionality of the ECU function along with adjustments of the reduced COM1 and COM2 insert product range to the new TX-I/O modules range.

Purpose

VISONIK system and service technicians. Target audience

Knowledge of the VISONIK system and VISONIK BPS in particular. Prerequisites

This document describes how to configure and apply the various BPS operating modes with regard to communication. The focus clearly is on communication via the Ethernet. This documents summarizes information from other documents such as Net-BPS, Ecu-BPS, and telephony in a clear and concise manner. For detailed information on telephony, the corresponding documents are referenced.

Content

CM2T8332E Telephony with VISONIK BPS Documentation on basics. Reference documents CM110442en Net-BPS V2x.xx Documentation on basics, CM2P8307en Ecu-BPS Documentation on basics.

If there is conflicting information, the information in this document is valid.

See document TX-I/O documentation CM110641 "TX-I/O tool" for the new TX-I/O modules and how to integrate them in VISONIK. This document is available via STEP.


Siemens Communication via Ethernet with VISONIK BPS CM110662en_01 Building Technologies Introduction 26.11.07

2.2 Terms and abbreviations

The table below explains the terms and abbreviations used in this document.

Term Explanation Network Stands for Ethernet network in this document. ECU Abbreviation for Enhanced Communication Unit. ECU function BPS1.ECU function as gateway between process stations

on an SDLC ring and partner stations on the Ethernet or modem connection (DCS / Net-BPS / Tele-BPS / notebook with Visotool).

Net-ECU BPS1.ECU with active ECU function for Ethernet. Tele-ECU BPS1.ECU with active ECU function for modem

connections. Net-BPS BPS1.xx on Ethernet. Tele-BPS BPS1.xx on modem. SDLC-BPS BPS1.xx on SDLC ring. PS Abbreviation for Process Station: BPS/PRV2/PRV1/EKL-X. DCS Data Communication Server (VISONIK mgmt. station). COM server Terminal server chip for Ethernet communication on COM1

inserts BPS1.C1/1E or BPS1.C1/1ES. DUART Dual Universal Asynchronous Receiver Transmitter.

Chip for two RS232 channels on COM1 inserts BPS1.C1/1E or BPS1.C1/1ES. Channel A is the modem interface, channel B is the connection to the COM Server.

ASX protocol Application protocol to transmit COLBAS data. Attribute protocol Application protocol to exchange VISONIK point parameters

between PS and DCS. ECU ring SDLC ring on an ECU. ECU slave PS on an ECU ring. The ECU is the ring master. On the

DCS, "daughter" rather than slave is used. LU P-bus load units. P-bus BIM P-bus module interface. Gateway between P-bus and island

bus for TX-I/O modules. Represents the connection TX-I/O modules as P-bus modules.



2.3 Purpose of BPS firmware V20.06

BPS firmware V20.06 primarily contains extensions and improvements of the ECU function to support step-by-step migration from SDLC ring operation to Ethernet communication. This, as a result, will replace the SDLC ring card in the mid-term. The drawing shows the planned migration path.

Migration from SDLC to Ethernet

Depending on topology and framework conditions, an entire ring (with max. 34 process stations) can be reconnected to a Net-ECU, or, individual process stations from the ring can be upgraded to Net-BPS and connected directly to the Ethernet. No restrictions apply to existing communication connections between process stations and the DCS.



2.4 BPS hardware product range

This section provides an overview of currently available basic units, communication and program cards.

ASN Description BPS1.00 Basic unit without P-bus function for CFE applications. BPS1.32 BPS1.64 BPS1.128

Basic unit with P-bus function for 32 / 64 / 128 load units.

BPS1.ECU Basic unit for ECU function.

Basic units

ASN Description BPS1.C1/1E COM1 card with DUART and COM Server. BPS1.C1/1ES COM1 card with SDLC-ASIC, DUART and COM Server.

COM1 cards for Ethernet

RJ45 plug (COM Server output) for Ethernet. RS232 interface (output DUART channel A) for modem or terminal.

As the new product range no longer contains the old cards for telephony (PVC1.1ST or BPS1.C1/1ST), we adapted the BPS firmware V20.06 to ensure that the RS232 interface can be used for telephony. However, Ethernet access is blocked during telephony operation.

Telephony function with C1/E cards

BPS1.C1/ES is the only card with SDLC-ASIC that remains available as part of the new range. It allows you to configure a BPS1.xx as SDLC-BPS. Access to the Ethernet, however, is precluded in this operating mode.

SDLC-ASIC

ASN Description BPS1.C2/1F COM2 card for TEC controllers (Profibus). BPS1.C2/1M COM2 card for Monogyr.

COM2 cards for TEC / Monogyr

The current program card is BPS1.M /E2-V20 with firmware version 20.06. Program card

The P-bus ASIC and P-bus connection are located on the power supply card RG1.64 or PRG1.128 of the basic unit.

P-bus connection

You can operate the new TX-I/O modules via a P-bus BIM. See "P-bus and TX-I/O settings" on how to set up this operating mode.

TX-I/O modules

The operating mode as Tele-ECU or Net-ECU also now allows for operating the P-bus (with max. 64 load units). However, we recommend to use this option only for small applications to avoid performance problems. See "P-bus and TX-I/O settings" on how to set up this operating mode.

BPS1.ECU with P-bus



3 Configuration 3.1 Overview

This section shows how to configure the five operating modes of the BPS firmware: Operating modes • Net-BPS • Net-ECU • Tele-BPS • Tele-ECU • SDLC-BPS For each operating mode, the required hardware, communication parameter settings and commissioning workflows are described.

3.2 General 3.2.1 Hardware / Firmware identification

Basic unit and inserted cards are identified by the Boardident parameters. They are available in the Ethernet or ECU report (query ENREP or ECUREP). The firmware version is located in the report header.

Check both boardident and firmware version only after initial hardware boot.

@BPS.TMBD Basic unit @BPS.TCM1 COM1 card @BPS.TCM2 COM2 card @BPS.TMEM Program card

Boardident parameters

If a COMx card is missing, boardident parameter is TCMx = 0.

Boardident for the current product range. Current product range

Device ASN Boardident BPS1.00 /32 /64 /128 TMBD = 8/9/10/11

Basic unit BPS1.ECU TMBD = 7 BPS1.C1/1E TCM1 = 7

COM1 card BPS1.C1/1ES TCM1 = 12 BPS1.C2/1F TCM2 = 4

COM2 card BPS1.C2/1M TCM2 = 5

Program card BPS1.M /E2-V20 TMEM = 14


Siemens Communication via Ethernet with VISONIK BPS CM110662en_01 Building Technologies Configuration 26.11.07

Boardidents for older, no longer available product ranges: Old product range

Device ASN Boardident Basic unit PRV2.00 /32 /64 /128 TMBD = 1/2/3/4

PVC1/1ST TCM1 = 1 PVC1/1S TCM1 = 2 PVC1/1T TCM1 = 3 BPS1.C1/1S TCM1 = 10

COM1 card

BPS1.C1/1ST TCM1 = 11 PVC2.1F TCM2 = 1

COM2 card PVC2.2M TCM2 = 2 PVA3.01 TMEM = 6

Program card PVA3.02 TMEM = 7

The new program card and the COM cards BPS1.C1/1E, BPS1.C2/1F, BPS1.C2/1M can also be plugged into old PRV2 basic units.

Compatibility of the product ranges

Do not use old program cards PVA03 on BPS basic units Caution Reason: Different timing of the RAM blocks may result in problems at extreme operating temperatures.

EPROM set V20.06 can also be used on old program cards. 3.2.2 Communication parameter settings

The communication parameters are also available in the Ethernet report (query ENREP). Check them after the initial hardware boot and set them for the selected operating mode. Enter the settings local and without connection to the DCS.

Meaning of communication parameters in the Ethernet report:

@BLN.SWAY Setpoint communication medium (Ethernet / Modem connection / SDLC).

@BLN.AWAY Actual value communication medium (Ethernet / Modem connection / SDLC).

@PHON.PHON Activate telephony package (for Ethernet and modem connection).

@PHON.BD

Depending on communication medium (Ethernet / Modem connection / SDLC). – Baud rate DUART channel B to COM Server or – Baud rate DUART channel A to modem.

IP-Address Subnet-Mask Gateway-IP

IP configuration, relevant only for Net-BPS and Net-ECU.

@BLN.MPS Value for @BPS.NR, own PS number. @BLN.MSY Own system number. @BLN.PPS(1) DCS number. @BLN.PSY(1) DCS system number.



@BLN.SWAY The basic parameter for the operating mode is @BLN.SWAY.

SWAY Comm.medium Operating mode as 1 Ethernet Net-BPS 2 SDLC SDLC-BPS 3 Ethernet + SDLC Net-ECU 4 Modem connection. Tele-BPS 6 Modem connection +

SDLC. Tele-ECU, SDLC-BPS with telephony.

@BLN.SWAY is saved in the EEPROM of the program card. The factory setting regardless of COM1 card is @BLN.SWAY=2 (operating mode as SDLC-BPS). For all other operating modes, @BLN.SWAY must be changed accordingly.

Caution

The address parameters MPS and PPS(1) are critical for a successful connection between DCS via Ethernet or modem connection. The ASX protocol requires correct values for MSY and PSY(1). As long as data are not exchanged across system limits, we recommend to keep default value 0 for MSY and PSY(1).

Address parameter

3.2.3 TTY parameter settings

@TTY1 When @PHON.PHON=1 (telephony package active), parameters for @TTY1-point have no function. The RS232 interface (DUART channel A) is initialized directly by the firmware.

@TTY2 With COM1 cards with Ethernet connection (RJ45 plugs), the parameters of point @TTY2 do not have any function. The COM Server interface (DUART channel B) is initialized directly by the firmware.

In both cases, the interface's baud rate is given by @PHON.BD. Baud rate



3.3 Configuration as Net-BPS 3.3.1 Hardware combinations

The table shows possible basic units and COM cards for Net-BPS operating mode. All combinations are possible.

Device ASN Boardident PRV2.00 /32 /64 /128 TMBD = 1/2/3/4

Basic unit BPS1.00 /32 /64 /128 TMBD = 8/9/10/11 BPS1.C1/1E TCM1 = 7

COM1 card BPS1.C1/1ES TCM1 = 12

COM2 card Optional, all possible TCM2 = 0/1/2/4/5 3.3.2 Communication parameter settings

Parameter Desired value Writable @BLN.SWAY 1 Yes @BLN.AWAY 1 No (derived from @BLN.SWAY) @PHON.PHON 1 Yes @PHON.BD 9600 Yes IP-Address Subnet-Mask Gateway-IP

Project-specific Yes, via ENET$

@BPS.NR Yes @BLN.MPS No (inherited from @BPS.NR) @BLN.MSY Yes @BLN.PPS(1) Yes @BLN.PSY(1)

Project-specific

Yes

Enter PS IP-address Enter the IP address of the PS via COLBAS variable ENET, e.g.:

ENET$:= "IP=10.169.8.211; SN=255.255.255.0; GW=10.169.8.250"

IP, SN (subnet) and GW (gateway) can be changed individually, e.g.:

ENET$:= "IP=10.169.8.211" ENET$:= "" (blank string) deletes the previous entry.

All changes become effective only after RESET command (restart BPS). Changes to @BPS.NR automatically trigger a restart.

The baud rate @PHON.BD must match the baud rate set in the COM Server. The factory setting is 9600 baud. If the baud rates differ, communication is impossible. In this case, the Ethernet report reads the following under ACTUAL NET CONNECTION:

Caution @PHON.BD

'No Link to COM Server'

You can check and adjust the baud rate in the COM server only via Telnet: Enter telnet ip-address 1111 in the PC's command window. The COM server dialog box opens. SETUP port (serial), UART setup takes you to the baud rate.



3.3.3 Commissioning workflow

Step 1 Assemble hardware combination, carry out hardware boot. Step 2 Connect Visotool to tool interface, check Boardident parameters in

Ethernet report (query ENREP). Step 3 Set the configuration parameters, enter RESET. Step 4 After restarting, check the CONFIGURATION in the Ethernet report.

The following must be displayed: Routing not active, Ethernet Mode active,

Configuration parameters including @BLN.AWAY as per the settings. Step 5 Check ACTUAL NET CONNECTION in the Ethernet report.

After 10-20 seconds, the following must be displayed: COM Server ok, No Net Access

Step 6 Plug in the connection cable for the Ethernet (RJ45 plug COM1 port). After 10-20 seconds, the following must be displayed: COM Server ok, Net Access ok

Step 7 On the DCS, enter the corresponding data for the Net-BPS in the profile file Visoprf.prf , section [NET]. Example: [NET] $ps[11] = uwt 10.169.8.211

Step 8 After entering the data, the DCS starts to negotiate the protocol with the Net-BPS as soon as the physical connection is established. In the Ethernet report, the display in ACTUAL NET CONNECTION part changes from 'No Link to DCS' to 'DCS connection ok'.

Procedure



3.4 Configuration as Net-ECU 3.4.1 Hardware combination

Device ASN Boardident Basic unit BPS1.ECU TMBD = 7 COM1 card BPS1.C1/1ES TCM1 = 12 COM2 card Not allowed TCM2 = 0 Program card Only BPS1.M /E2 TMEM = 14

Caution Operation as Net-ECU is possible only with this hardware combination.

3.4.2 Communication parameter settings

Parameter Desired value Writable @BLN.SWAY 3 Yes @BLN.AWAY 3 No (derived from @BLN.SWAY) @PHON.PHON 1 Yes @PHON.BD 9600 Yes @RING.BD 4800 / 9600 Yes IP-Address Subnet-Mask Gateway-IP

Project-specific Yes, via ENET$

@BPS.NR Yes @BLN.MPS No (inherited from @BPS.NR) @BLN.MSY Yes @BLN.PPS(1) Yes @BLN.PSY(1)

Project-specific

Yes

IP address entry See previous section "Configuration as Net-BPS

Configuration as Net-BPS

".

Caution @PHON.BD See comment in previous section " ".

Caution @RING.BD All connected ring slaves must have the same baud rate. For PRV1 and EKL-X, only 4800 bd are possible (max. baud rate).

The max. number of slaves is 34. Although more than 34 slaves on the ring may be displayed in the ECU report, only 34 can communicate with the DCS.

Number of slaves





Ethernet report (query ENREP). Step 3 Set the configuration parameters, enter RESET.

After restarting, check the CONFIGURATION in the Ethernet report. The following must be displayed: Routing active, Ethernet Mode active,

Configuration parameters including @BLN.AWAY as per the settings. Step 4 Connect the Net-ECU on the ring. Then check ring communication in

the ECU report (query ECUREP). After a few seconds, the display under RING DIAGNOSTIC must show: Vicemaster: active SlaveCount: (Number of slave PS on ring) Slave Stations: (List of slave PS numbers) The yellow REM LED must flash at a 2 s bright, 1 s dark rhythm.

Commissioning on the ring side:

Same workflow as for commissioning the Net-BPS (from Step 5). Commissioning on the

network side: After communication between the DCS and Net-ECU is established, the process stations on the ECU ring are identified automatically and entered as ECU slaves. Check with parameter LPS (link PS) in $xxBLN point:

Parameter LPS Value of LPS = PS number of the ECU for all ECU slaves.



3.5 Configuration as Tele-BPS 3.5.1 Hardware combinations

The table shows possible basic units and COM cards for Tele-BPS operating mode. All combinations are possible.

Device ASN Boardident Basic unit PRV2.00 /32 /64 /128 TMBD = 1/2/3/4 BPS1.00 /32 /64 /128 TMBD = 8/9/10/11 COM1 card PVC1.1ST TCM1 = 1 PVC1.1T TCM1 = 3 BPS1.C1/1E TCM1 = 7 BPS1.C1/1ST TCM1 = 11 BPS1.C1/1ES TCM1 = 12 COM2 card Optional, all possible TCM2 = 0/1/2/4/5

Ring connection and Ethernet connection, if available, have no impact on this operating mode.

Caution

3.5.2 Communication parameter settings

Parameter Desired value Writable @BLN.SWAY 4 Yes @BLN.AWAY 4 No (derived from @BLN.SWAY) @PHON.PHON 1 / 2 Yes (value 2 : Tele-event function) @PHON.BD Yes (max. 19200 baud) @BPS.NR Yes @BLN.MPS No (inherited from @BPS.NR) @BLN.MSY

Project-specific

Yes @BLN.PPS(1) Yes @BLN.PSY(1) Yes @BLN.PPS(2) Yes @BLN.PSY(2)

PS number System number Partner 1 and 2

Yes To place a call from one partner device to another, a number of specific telephony parameters are required. The most important parameters are (text numbers as examples):

Telephony parameters

@PHON.MSEQL=100 Text number for local modem sequence. @BLN.MSEQP(1)=101 Text number for dial-up sequence partner 1. @BLN.MSEQP(2)=102 Text number for dial-up sequence partner 2. @TXC#p100 Local modem sequence. @TXC#p101 Dial-up sequence partner 1. @TXC#p102 Dial-up sequence partner 2.

@TXC#p100.$ = "1: Elsa 28.8 QT;IN='at&fs0=2';C1=ATDT;fb=1." Typical modem/dial-up

sequences: @TXC#p101.$ = "1: DCS;C2=0443361592." @TXC#p102.$ = "2: Teleprinter;C2=0443361580."

(C2 = Partner modem phone number).

For a detailed description of telephony, refer to CM2T8332E.





ECU report (query ECUREP). Step 3 Set the configuration parameters, enter RESET.

After restarting, check the CONFIGURATION in the ECU report. The following must be displayed: Routing not active, Ethernet Mode not active,

Configuration parameters including @BLN.AWAY as per the settings. Step 4 Display all other telephony parameters and texts via:

LIST @PHON/R LIST @BLN/R LIST @TXC#p

Step 5 Check PHONE DIAGNOSTIC in the ECU report.. If no modem is connected, the following is displayed: PHON PHAS: Modem failure

Step 6 Connect and enable modem with RS232 interface (TTY1 / DUART channel A) and telephone plug.

Step 7 Set the following parameters for the initial function test: @PHON.PROTTY=3 (log for opening connection TTY). @BLN.PPSEL=1 (manual dial-up command to partner 1). Then change with @PHON.PON change from 0 to 1. Open call and monitor modem, i.e. connection initialization phases.

In Step 7, a connection is established only if the partner is configured accordingly. The next section provides brief instructions for the DCS.

Refer to document CM2T8332E for additional information.


Siemens Communication viaEthernet with VISONIK BPS CM110662en_01 Building Technologies Configuration 26.11.07

3.5.4 Brief instructions for configuration on the DCS

Step 1 Connect the modem to the COM or USB port. Check the COM port assigned to the modem in the Windows Device Manager.

Step 2 Define a terminal channel in profile file Visoprf.prf, section [PCV], for the COM port. Example (terminal channel $T3 for COM1):. $Tytype[3] = COMx $Tycomxname[3]= COM1

Step 3 Generate a terminal channel with ctrl-P,PKG,GNP,$T3 and set the following parameters: DTYP = Modem MCAT = 1 (modem category, value range 1..7). MSEQ = 200 (number TXC clear text for modem sequence). BD = 19200 (baud rate for connection DCS − modem, max. 38400 bd).

Step 4 Set the following parameters in point $xxBLN of the Tele-BPS: MCAT = 1 (link to terminal channel). MSEQ = 201 (number TXC clear text for dial-up sequence).

Step 5 Define the TXC clear text for modem sequence ($T3 MSEQ): ctrl-P,TXC,AEND,Number: 200 Typical modem sequence on the DCS: C 0200= 1: Elsa 28.8 QT;C1=ATDT;IN=at&fs0=1.

Step 6 Define the TXC clear text for dial-up sequence ($xxBLN MSEQ): ctrl-P, TXC, AEND, Number: 201 Typical dial-up sequence on the DCS: C 0201= 1: PS11;C2=0443361592. (C2 = Partner modem phone number).

Always use different text numbers on BPS and DCS to make sure that the DCS does not overwrite the BPS texts.

Caution: Text numbers


Siemens Communication via Ethernet with VISONIK BPS CM110662en_01 Building Technologies Configurati 26.11.07

3.6 Configuration as Tele-ECU 3.6.1 Hardware combinations

Device ASN Boardident Basic unit BPS1.ECU TMBD = 7

BPS1.C1/1ST TCM1 = 11 COM1 card

BPS1.C1/1ES TCM1 = 12 COM2 card Not allowed TCM2 = 0 Program card Only BPS1.M /E2 TMEM = 14

The Ethernet connection on BPS1.C1/1ES in this operating mode has no function.

Caution

COM1 port PVC1.1ST cannot be used due to the processor clock frequency 24 MHz. 3.6.2 Communication parameter settings

Parameter Desired value Writable @BLN.SWAY 6 Yes @BLN.AWAY 6 No (derived from @BLN.SWAY) @PHON.PHON 1 Yes @RING.BD 4800 / 9600 Yes

Set all other communication and specific telephony parameters identical to section "Configuration as Tele-BPS"

Caution @RING.BD All connected ECU slaves must have the same baud rate. For PRV1 and EKL-X, only 4800 bd are possible (max. baud rate).

We recommend to limit the number of slaves to max. 10. Number of slaves 3.6.3 Commissioning workflow


ECU report (query ECUREP). Step 3 Set the configuration parameters, enter RESET.

After restarting, check the CONFIGURATION in the ECU report. The following must be displayed: Routing active, Ethernet Mode not active, Configuration parameters including @BLN.AWAY as per the settings.

Step 4 Connect the Tele-ECU on the ring. Then check ring communication in the ECU report. After a few seconds, the display under RING DIAGNOSTIC must show: Vicemaster: active SlaveCount: (Number of slave PS on ring) Slave Stations: (List of slave PS numbers)

The yellow REM LED must flash at a 2 s bright, 1 s dark rhythm.

Commissioning on ring side:



Same workflow as for commissioning the Tele-BPS. Commissioning on the modem side

Same workflow as for configuring the Tele-BPS. In addition, check parameter LPS (link PS) in $xxBLN point of the slaves:

Configuration on the DCS

Value of LPS = PS number of the ECU for all ECU slaves.

3.7 Configuration as SDLC-BPS 3.7.1 Hardware combinations

The two tables show possible basic units and COM cards for SDLC-BPS operating mode. Mixing PRV and BPS product ranges does not work (incompatible SDLC-ASIC and processor clock frequency).

Device ASN Boardident Basic unit BPS1.00 /32 /64 /128 TMBD = 8/9/10/11

BPS1.C1/1S TCM1 = 10 BPS1.C1/1ST TCM1 = 11 COM1 card BPS1.C1/1ES TCM1 = 12

COM2 card Optional, all possible TCM2 = 0/1/2/4/5

BPS product range

Device ASN Boardident Basic unit PRV2.00 /32 /64 /128 TMBD = 1/2/3/4 COM1 card PVC1.1ST TCM1 = 1 PVC1.1S TCM1 = 2 COM2 card Optional, all possible TCM2 = 0/1/2/4/5

PRV product range

Caution BPS1.C1/1ES COM1 card BPS1.C1/1ES continues to be available as the only card.

The Ethernet connection on the in this operating mode has no function. 3.7.2 Communication parameter settings

In operating mode SDLC-BPS, two variants are possible: SDLC stand-alone or SDLC + telephony (provided a card with modem interface is inserted).

Two variants

The telephony function in this only allows for transmitting ASCII strings to a teleterminal / teleprinter (e.g. send clear text messages via modem connection).

Parameter Desired value Stand-alone SDLC

Desired value SDLC + telephony

@BLN.SWAY 2 6 @BLN.AWAY 2 2 (read-only) @PHON.PHON 0 1 @PHON.BD No meaning Project-specific

Max. 19200 bd. In the case of SDLC + telephony, address and telephony parameters must be set as in the Tele-BPS configuration.




Step 1 Assemble hardware combination, carry out hardware boot. Step 2 Connect Visotool to tool interface, check Boardident parameters in ECU

report (query ECUREP). Step 3 Set the configuration parameters, enter RESET.

After restarting, check the CONFIGURATION in the ECU report. The following must be displayed: Routing not active, Ethernet Mode not active, Configuration parameters as per setting, @BLN.AWAY=2.

Step 4 Check based on the yellow REM LEDs if the BPS works as ring slave: Fast flashing on the ECU ring, irregular flashing on the DCS ring (image of current general query).

Commissioning on ring side:

Same workflow as for commissioning the Tele-BPS. Modem-side

commissioning for SDLC + telephony



3.8 P-bus and TX-I/O settings

The P-bus is supported as per the basic unit's ASN type. xx in PRV2.xx or BPS1.xx designates the max. number of P-bus load units (LU). The supply card PRG1.64 limits the LUs to 64.

Basic unit BPS1.ECU allows P-bus operation with firmware V20.06 for small applications (max. 64 load units). P-bus operation must be activated explicitly. This is possible with the following physical write command:

BPS1.ECU with P-bus

PHYW(4008,0,LU) with LU=32 / 64 / 0 for switch-off.

The factory setting is LU=0. The set number becomes effective after the next restart. The set number is saved to EEPROM and survives all restarts. It is read via PHYR(4008,0)

BPS firmware V20.06 supports integration of TX-I/O modules via the P-bus BIM. The following functionality is available:

TX-I/O integration

– Delayed startup of the P-bus driver after power up. – Tolerance to response times of the P-bus-BIM. Set the delayed power up via the following physical write command:

PHYW(4007,0,DT) with DT = Delay time in seconds.

The recommended value is DT=30. After a hardware boot, DT=0. DT is saved to EEPROM and can be read any time via PHYR(4007,0).

The parameters for tolerance are set by default. Change them in the event of problems only after consultation with Field Support or Development.

See the TX-I/O manual on how to configure and commission the TX-I/O modules (part of the DESIGO V2.37 documentation on STEP).



4 Network communication 4.1 Overview

This section discusses the various methods to exchange data between VISONIK devices via the Ethernet. The following topology shows the communication partners. Included: Process stations on the SDLC ring that can communicate via the network.

VISONIK devices on the network

4.2 Information on protocols

VISONIK knows two application protocols:

The attribute protocol helps transmit VISONIK point parameters. With the attribute protocol, data can be exchanged only between PS and DCS. (The DCS maintains the central process image of all process stations in the system).

Attribute protocol

ASX protocol to transmit COLBAS data. With the ASX protocol, data is interchanged between process stations and exchanged with the DCS (primarily to back up and restore COLBAS tasks, dispatcher, timeswitch programs, and text catalogs).

ASX protocol

There is no special application protocol to exchange COLBAS data between Visotool and the process stations via the network. Data is exchanged as pure ASCII strings (printable characters plus a few control characters such as LF, CR, NUL, Ctrl-E). The data is embedded in the underlying UDP/IP protocol to transport via Ethernet and not visible to users.

ASCII data

Users do not handle the attribute protocol. However, users should be familiar with the overall concept from the ASX protocol to ensure correct programming in COLBAS.


Siemens Communication via Ethernet with VISONIK BPS CM110662en_01 Building Technologies Network communication 26.11.07

ASX connections are temporary, logical channels between two partner stations to exchange COLBAS data. An ASX connection is established by a station to send an open command to a partner. Data is transferred after connection is established. The connection is again closed via a close command; or due to a timeout in exceptional cases.

ASX connections

The ASX client is the partner station that opens the connection; the other station is the ASX server. The term client/server only refers to an individual ASX connection.

ASX client/server

The ASX protocol knows four application services: ASX services

DUS (dialog with partner), DEX (data exchange), MSG (message), and REP (report).

Each service is handled via a separate ASX connection. The connection is opened and closed via service-specific COLBAS commands or statements.

With DUS, operator entries in a $Tn window of the DCS or a TTYn interface of a PS are sent transparent to a partner station and answered by the partner station. A DUS connection is opened via an immediate command DUS(US,SYS,WAY) and closed via Ctrl-E.

DUS (dialog with partner)

DEX is used for programmed data exchange between two PS. A DEX connection is opened upon execution of statement OPEN CONNECTION and closed upon execution of CLOSE CONNECTION. The statements SEND, REQUIRE, TRANSMIT and RECEIVE are used to transfer data.

DEX (data exchange)

The MSG service is used for programmed output of individual messages to a local interface TTYn of a partner station. The data transfer occurs upon execution of the PRINT statement. An MSG connection is opened and closed implicitly.

MSG (message)

The REP service is used for programmed output of reports to a local interface TTYn of a partner station. With standard reports (ALR, SYR), the REP connection is opened and closed explicitly. For own, programmed reports (with RES, PRINT statements and ENDRES), the REP connection is opened upon RES and closed upon ENDRES.

REP (report)

A BPS can have several open ASX connections to the same or different partner stations.

ASX connections

2 DUS connections, one as client, one as server. 2 DEX connections, one as client, one as server. 3 MSG or REP connections, either client or server.



4.3 Configure IP addresses

For communication to work via the network, the communication partners must know each others address.

On the DCS, enter the IP addresses of all partner stations on the network in the profile file visoprf.prf , section [NET]. Example:

IP addresses in the DCS

[NET] $ps[11] = uwt 10.169.8.211

In Visotool, the IP addresses of the Net-BPS /ECU must be entered in register "Connection > Open via TCP/IP" and NetBPS selected.

IP addresses in Visotool

In a Net-BPS / ECU, all IP addresses of all partner stations on the network are managed in a so-called partner address table. In this table, the IP addresses are linked to the PS numbers. There are two different alarm entries:

IP addresses in Net-BPS / ECU

Dynamic entries carried out spontaneously by the BPS firmware upon receipt of the first telegram from a to date unknown partner. This includes an entry for the DCS and for a notebook with Visotool, but also entries carried out upon receipt of the initial open command of a to date unknown ASX client.

Dynamic entries

Planned entries entered explicitly via COLBAS. A planned entry is required whenever an ASX connection is to be opened as client on the corresponding process station (as a user with DUS or upon programmed data exchange). Enter the planned entry with a C-text.

Planned entries

Examples: @TXC#p11 = "pps[11] = 10.169.8.211" @TXC#p20 = "pps[20] = 10.169.8.220; Net-ECU for ring 2"

Following the IP address, a comment may be appended for display in the Ethernet report following a semicolon ; . Text that does not match the required syntax is not entered in the partner address table, and there is no associated error message (handles as regular C-text entry).

An existing, planned entry can be changed any time via the C-text or DEL @TXC#pn (the partner address table continues to display the old entry to avoid interruption of an open ASX connection).

ENREP/P allows for checking the entries in the partner address table any time. Planned and dynamic entries differ by their text number indication and possible comments.

Display entries

ENREP/H (history)

allows for checking all partners on the network with whom the BPS has exchanged data since the last RESET. The partner's port is also displayed in addition to PS number and IP address (8000 for Net-BPS/ECU, 8500 for DCS, 8501 for Visotool).

Max 40 entries can be planned. Number of entries The table always offers space for at least 10 dynamic entries.



4.4 Operate via network 4.4.1 Operation via DCS

ctrl-P, DUS, $nn (station number) allows for reaching each PS in the earlier topology diagram (Net-BPS, Net-ECU, ECU slave). ctrl-E interrupts the DUS connection.

4.4.2 Operation via Visotool

Every Net-BPS / Net-ECU can be reached via a Visotool connected to the network. In Visotool, the IP address of the Net-BPS /ECU must be entered in register "Connection > Open via TCP/IP" and NetBPS selected.

Follow-on connections with DUS are then possible: DUS connections a) From a Net-ECU to an ECU slave. DUS (US=nn, SYS=0, WAY=2) nn=station number ECU slave.

b) From a Net-BPS / Net-ECU to the DCS with DUS (US=nn, SYS=0, WAY=1) nn=system number DCS ($S,SYNR)

c) From a Net-BPS / Net-ECU to another Net-BPS with DUS (US=nn, SYS=0, WAY=1) nn=station number Net-BPS

For variant c), the Net-BPS to be reached must be entered in the partner address table of the first station (ASX client) along with its IP address.

ctrl-E exits the DUS and returns to operation of the first station. 4.4.3 Operation from another PS

Rather than via the network, Visotool can also be connected to a PS via a local I/O interface (normally TTY3). The above operating options of a partner device via DUS are identical.

If the PS is an ECU slave, DUS parameter WAY must always be 2 (communication medium SDLC). The DUS connection for a DUS connection from a ECU slave to a Net-BPS must be entered in the partner address table of the Net-ECU.

DUS from ECU slave



4.5 Programmed data exchange

For data to be exchanged with partner devices as programmed in a COLBAS task, the task variables for communication

Task variable for communication

TSKWAY,TSKPPA,TSKUS,TSKSYS,TSKTTY

must be initialized correctly. The corresponding value assignments must precede the instructions for data transfer.

TSKWAY Variable TSKWAY must correspond to the communication medium.

TSKWAY Comm.medium Partner type Protocol 0 Local interface Terminal ASCII 1 Ethernet PS / DCS ASX 2 SDLC ring PS / DCS ASX

With TSKWAY=1, enter TSKPPA=1 (historical reasons; a Net partner is handled the same as modem partner 1). For TSKWAY=0/2, function TSKPPA has no meaning.

Caution TSKPPA

TSKUS,TSKSYS For TSKWAY>0, TSKUS=station number, TSKSYS=system number of the partner. For TSKWAY=0, TSKUS,TSKSYS have no meaning.

Caution TSKSYS To exchange data directly between process stations on the Ethernet or on the SDLC ring, the partner stations must have the same system number (TSKSYS=0 or [email protected]). In the event of different system numbers, opening a connection via DCS is attempted.

TSKTTY TSKTTY designates the I/O interface for message output via task. With TSKWAY=0, TSKTTY is the local TTYn interface. With TSKWAY>0, TSKTTY is the TTYn interface of the partner station. For data exchange DEX (data exchange), TSKTTY has no meaning.

The station with the operating communication task always is the ASX client in the case of programmed data exchange. The partner station (TSKUS,TSKSYS) always is the ASX server.

ASX client/server role

4.5.1 Exchange data with DEX (data exchange)

Permissible COLBAS statements for DEX:

OPEN CONNECTION

SEND, REQUIRE, TRANSMIT und RECEIVE

CLOSE CONNECTION

The programmed data exchange with DEX must have troubleshooting ON ERROR GOTO. In this case, it must be ensured that an open DEX connection is interrupted. The troubleshooting process must contain instruction CLOSE CONNECTION.

Troubleshooting

Document CM110434en "COLBAS language description“ (10.12.2004), section 4.14 "Data exchange" contains detailed information on the COLBAS statements fro DEX.

COLBAS reference



The following options are available for DEX connections: DEX connections

DEX from Net-BPS to Net-BPS /Net-ECU TSKWAY=1, TSKPPA=1, TSKUS=station number Net-BPS / Net-ECU.

The ASX server (Net-BPS / Net-ECU) must be entered in the partner address table of the ASX client along with its IP address.

DEX from Net-BPS via Net-ECU to ECU slave TSKWAY=1, TSKPPA=1, TSKUS=station number ECU slave.

The ASX server (ECU slave) must be entered in the partner address table of the ASX client along with the IP address of the Net-ECU. Example:

Net-ECU Station number 20, IP address 10.169.8.220 ECU slave Station number 25, entry in the partner address table:

@TXC#p25 = "pps[25] = 10.169.8.220"

DEX from Net-ECU to Net-BPS TSKWAY=1, TSKPPA=1, TSKUS=station number Net-BPS.

The ASX server (Net-BPS) must be entered in the partner address table of the ASX client along with its IP address.

DEX from Net-ECU to ECU slave TSKWAY=2, TSKPPA=0, TSKUS=station number ECU slave.

No entry in the partner address table of the Net-ECU.

DEX from ECU slave to ECU slave/Net-ECU TSKWAY=2, TSKUS=station number ECU slave / Net-ECU.

DEX from ECU slave via Net-ECU to Net-BPS TSKWAY=2, TSKUS=station number Net-BPS.

The ASX server (Net-BPS) must be entered in the partner address table of the Net-ECU along with its IP address.



4.5.2 Exchange data with MSG / REP (message / report)

When TSKWAY>0, a PRINT statement opens an MSG connection.

When TSKWAY>0, the COLBAS statements for standard reports (SYR,ALR,ERP...) as well as the RES statement (reservation of an I/O interface) open a REP connection. In the latter case, the REP connection must be closed explicitly with ENDRES; any number of PRINT statements can exist between RES and ENDRES, but no statements for standard reports.

Variable TSKTTY For MSG / REP connections, the I/O interface for at the partner station must be defined via variable TSKTTY to output messages.

MSG / REP connections offer the same possibilities as DEX connections. For the values TSKWAY,TSKPPA,TSKUS and the entries in the partner address table of the ASX client or the Net-ECU, the same process applies as for exchanging data with DEX.

MSG / REP connections

In addition, messages and reports can be sent to a $Tn window of the DCS. TSKTTY in this case stands for the $Tn window and TSKUS for the DCS number. The firmware enters the IP address of the DCS (ASX server) in the partner address table of the ASX client.

Messages to the DCS

4.5.3 Exchange ASCII strings

Setting the following variables in the Net-BPS:

TSKWAY=0 local I/O interface TSKTTY=2 on the Ethernet

Allows for programming data exchange via Visotool connected to the network. Prerequisite is a connection from Visotool to the corresponding Net-BPS. (See section "Configure IP addresses“). This operating mode e.g. allows for reading data processing profiles.



Siemens Switzerland Ltd Building Technologies Group International Headquarters Gubelstrasse 22 CH-6301 Zug Tel. +41 41-724 24 24 Fax +41 41-724 35 22 www.siemens.com/sbt

© 2007 Siemens Switzerland Ltd Subject to change



http://www.siemens.com/sbt

communication via ethernet with visonik bps v20.06

Documents