climatix™ remote opc server pol0l9.00/xxx ... -...
TRANSCRIPT
Ethernet LAN
POL687.70POL638.00
RemoteOPC
Server
Climatix™ Remote OPC Server POL0L9.00/xxxDocumentation on basics
CB1P3904en 09.07.2011
Building Technologies
2 / 80
Siemens Remote OPC Server CB1P3904en Building Technologies 09.07.2011
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
© 2009 Siemens Switzerland Ltd. Subject to change
3 / 80
Siemens Remote OPC Server CB1P3904en Building Technologies Table of contents 09.07.2011
Table of contents
1 About this document ................................ ..............................................5 1.1 Revision history.........................................................................................5 1.2 Before you start.........................................................................................5 1.3 Reference documents ...............................................................................6 1.4 Document conventions .............................................................................6 1.5 Important information on safety ................................................................7 1.6 Trademarks and copyrights.......................................................................8 1.7 Quality assurance .....................................................................................8 1.8 Document use/ request to the reader .......................................................9
2 The Climatix RemoteOPC Server ...................... .................................. 11 2.1 OPC protocol........................................................................................... 11 2.2 OPC networks ......................................................................................... 11 2.3 Tools........................................................................................................ 11 2.4 Functional design ....................................................................................12 2.5 Remote OPC via Ethernet LAN ..............................................................13 2.6 Remote OPC over modem......................................................................14
3 Installation of the RemoteOPC Server ............... .................................15 3.1 General ...................................................................................................15 3.2 RemoteOPC Licensing ...........................................................................17
4 Configuration...................................... ...................................................19 4.1 Configure controller.................................................................................19 4.2 Configuration file .....................................................................................20 4.3 Parameters..............................................................................................21
5 Commissioning ...................................... ...............................................23 5.1 Creating cache files ................................................................................23
6 Optimizing the RemoteOPC Server.................... .................................27 6.1 Quantity structure....................................................................................27 6.2 Optimizing the server ..............................................................................28 6.3 Optimizing the client................................................................................31 6.4 Registry entries .......................................................................................32
7 Running the RemoteOPC Server....................... ..................................33 7.1 OPC Server operation as Windows service............................................33 7.2 Running the server automatically............................................................33 7.3 View RemoteOPC.log file .......................................................................34 7.4 Troubleshooting ......................................................................................35
8 OPC client view .................................... .................................................37 8.1 OPC tag selection ...................................................................................37 8.2 Searching and selecting..........................................................................38
9 SAPHIR RCC setup ................................... ............................................43 9.1 Start page................................................................................................43
4 / 80
Siemens Remote OPC Server CB1P3904en Building Technologies Table of contents 09.07.2011
9.2 RAS parameters for an outgoing call ......................................................44 9.3 RAS parameters for an incoming call .....................................................45 9.4 Trigger event to initialize an outgoing call automatically.........................46
10 AWM setup.......................................... ...................................................47 10.1 General....................................................................................................47 10.2 RAS incoming calls .................................................................................47 10.3 RAS user creation ...................................................................................48 10.4 RAS dial-up creation ...............................................................................49
11 Computer to modem connections...................... .................................53 11.1 General....................................................................................................53 11.2 Creating a RAS entry for incoming connections .....................................54 11.3 Creating a RAS entry for outgoing connections......................................58
12 Standard application AHU V1.x...................... ......................................63 12.1 Overview .................................................................................................63 12.2 OPC tags of AHU V1.x ............................................................................64
Index ............................................. ...................................................................79
5 / 80
Siemens Remote OPC Server CB1P3904en Building Technologies About this document 09.07.2011
1 About this document 1.1 Revision history
Version Date Changes Section Pages
0.8 21.12.2009 Provisional edition
26.05.2010 Creation of the cache files AWM needed for remote OPC over modem
2.6 / 3.1 / 4.2 2.6
14 / 15 / 20, 21 14
1.0 18.02.2011 Configuration file: additional column (F) 4.2 / 4.3 20, 21
25.03.2011 New tool to generate the cache files 5.1 23, 24
06.04.2011 Updated screenshots and data paths 3 / 6 / 7
10.05.2011 Subjects "RCC setup" and "modem configurations" added
9, 10, 11
09.07.2011 Subject "AWM setup" extended with RAS 10 47 … 49
1.2 Before you start
This document applies to the following products:
Name Type (ASN) Short name Climatix RemoteOPC Software POL0L9.00/STD RemoteOPC
Description and functional scope of the products are based on the Climatix Valid Version Set 8.0 or higher.
This document is intended for the following audience: • System integrators • Measuring and control engineering staff of OEM customers • Sales and commissioning staff of OEM customers • Siemens employees in sales and support
This document intends to help the target audience to: • Create offers for OPC integration of Climatix controllers, types POL63x and
POL68x. • Engineer and commission ventilation and air conditioning plants equipped with
these device combinations.
The above target audience: • Has general professional knowledge on planning and commissioning HVAC
technology measuring and control solutions. • Has basic knowledge of OPC.
Validity
Product versions
Target audience
Use
Prerequisites
6 / 80
Siemens Remote OPC Server CB1P3904en Building Technologies About this document 09.07.2011
1.3 Reference documents
The following documents contain additional information on the products described in this manual:
Document Order no. Climatix, Documentation on basics "Controllers POL6XX and I/O modules POL9XX"
CB1P3903en
1.4 Document conventions
Below is an overview of all symbols used in this document denoting risks or important information: This symbol draws your attention to special safety notes and warnings. Failing to observe these notes may result in injury and/or serious damages.
This symbol denotes special information that, when failed to observe, may result in faulty functionality or loss of data.
Notes with this symbol provide important information that requires appropriate attention.
This symbol marks passages containing tips and tricks.
The following abbreviations are used in text and illustrations:
Abbreviation Meaning BACS Building Automation and Control System BSP Board Support Package (operating system) Climatix Controller family with common tools HVAC Heating, Ventilating, Air Conditioning MS Management Station OPC OLE for Process Control SAPRO Programming tool SAPRO SCADA Supervisory Control and Data Acquisition SCOPE Commissioning and service tool SCOPE SELV Safety Extra-Low Voltage
Further information
Symbols used
STOP
Abbreviations
7 / 80
Siemens Remote OPC Server CB1P3904en Building Technologies About this document 09.07.2011
1.5 Important information on safety
Use Remote OPC communication only for control and monitoring functions in ventilation, air conditioning and refrigeration plants.
Trouble-free and safe product operation of the above products presupposes transport, storage, mounting, installation, and commissioning as intended as well as careful operation.
Fuses, switches, wiring and grounding must comply with local safety regulations for electrical installations.
When wiring, strictly separate AC 230 V mains voltage from AC 24 V safety extra-low voltage (SELV) to protect against electrical shock!
Only qualified staff trained accordingly may prepare for use, commission, and maintain OPC server software.
Only authorized staff may diagnose and correct faults and recommission the plant. This applies to working within the panel as well (e.g. testing or changing fuses).
Refer to the environmental conditions specified in the respective data sheets for storage and transport. If in doubt, contact your supplier.
Devices contain electrical and electronic components; do not dispose of them in household garbage. Observe all local and applicable laws .
Field of application
Intended use
Electrical installation
Wiring
Commissioning and maintenance
Faults
Storage and transport
Disposal
8 / 80
Siemens Remote OPC Server CB1P3904en Building Technologies About this document 09.07.2011
1.6 Trademarks and copyrights
The table below lists the third-party trademarks used in this document and their legal owners. The use of trademarks is subject to international and domestic provisions of the law. Trademarks Legal owner OPC Microsoft Corporation
All product names listed in the table are registered (®) or not registered (™) trademarks of the owner listed in the table. We forgo the labeling (e.g. using the symbols ® and ™) of trademarks for the purposes of legibility based on the reference in this section.
This document may be duplicated and distributed only with the express permission of Siemens, and may be passed on only to authorized persons or companies with the required technical knowledge.
1.7 Quality assurance
These documents were prepared with great care. • The contents of all documents are checked at regular intervals. • All necessary corrections 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.siemens.com/sbt.
Trademarks, legal owners
Copyright
Document contents
Suggestions
9 / 80
Siemens Remote OPC Server CB1P3904en Building Technologies About this document 09.07.2011
1.8 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.siemens.com/sbt or from your
system supplier • From the support team at headquarters [email protected] if
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.
Request to the reader
More information
Exemption from liability
10 / 80
Siemens Remote OPC Server CB1P3904en Building Technologies About this document 09.07.2011
Blank page
11 / 80
Siemens Remote OPC Server CB1P3904en Building Technologies The Climatix RemoteOPC Server 09.07.2011
2 The Climatix RemoteOPC Server 2.1 OPC protocol
OPC (Openness, Productivity & Collaboration) is a standard by the OPC Foundation. It bridges the communication barriers between software applications (visualization software, supervisory control systems, etc.) and different devices.
• OPC provides uniform access to process data and alarm and event messages on the field level as well as to data on the company level (facility management systems, information systems, etc).
• OPC ensures the easy and uniform integration of subsystems from different manufacturers into a manufacturer-independent and open BMS.
• OPC allows leveraging the vast variety of specialized bus systems and provides great freedom in the choice of automation components for BMS expansion. More and more building automation manufacturers meanwhile offer OPC-capable BA components.
See www.OPC.org
2.2 OPC networks
Remote OPC communications are used • over Ethernet LAN but also • over Modem connections.
2.3 Tools
Within OPC network you distinguish between Server and Client: • The Server provides the data • The Client reads and writes the OPC datapoints, so called OPC tags.
What is OPC
For more information about OPC
LAN or Modem
OPC Server and Client
12 / 80
Siemens Remote OPC Server CB1P3904en Building Technologies The Climatix RemoteOPC Server 09.07.2011
2.4 Functional design
Even BACnet, LON and Modbus are most favorable integrations, OPC integration is often requested, where ever a SCADA system does have an OPC Client to integrate certain data from an air handling unit or a chiller machine.
Climatix provides a RemoteOPC Server, where all POL6XX controllers with onboard Ethernet or over modem connection can be connected and OPC data points integrated into a Building Automation and Control System.
The following picture shows a RemoteOPC Server example via an Ethernet LAN:
P3904Z01
Ethernet LAN
POL687.70POL638.00
RemoteOPC
Server
BACS
BACS Building Automation and Control System POL6XX Climatix controllers, Ethernet version.
The RemoteOPC server runs as a service on the building automation computer and provides the Climatix data points as OPC tags. If the BACS does have an OPC client, it is possible to read and write those OPC tags.
To run the RemoteOPC server, an activation key is needed (License). The license can be ordered (POL0L9.00/STD) according the amount of necessary data points (OPC tags) and the amount of connected Controllers. By giving the unique ID of the target computer, the activation key will be received.
OPC integration purpose
Remote OPC
Example
General function
License
13 / 80
Siemens Remote OPC Server CB1P3904en Building Technologies The Climatix RemoteOPC Server 09.07.2011
2.5 Remote OPC via Ethernet LAN
The figure shows an example for Climatix controller types 638, controlling and monitoring a number of air handling devices individually:
MS
Ethernet LANP3904Z02
AHU AHU
POL638 POL638
RemoteOPC
Server
MS Management station and Climatix RemoteOPC Server. AHU Air handling unit. POL638 Climatix controller, Ethernet version.
Integration aims at providing all required controller data to the management station to be able to change selected set points and stages.
The Climatix RemoteOPC Server is running on the Management Station and is able to read and write Climatix data points and provide it as OPC Tags.
An OPC client, which is also running on this Management Station is now able to read and write this OPC tags and display the values within a certain management station in a graphical way.
Example
Description
14 / 80
Siemens Remote OPC Server CB1P3904en Building Technologies The Climatix RemoteOPC Server 09.07.2011
2.6 Remote OPC over modem
If a LAN network is not available or a couple of controllers are not within the LAN Network (far distance), a modem connection can help to integrate the data into the Building Automation and Control System (BACS).
The figure shows an example for Climatix controller types 6XX, controlling and monitoring a number or air handling devices individually:
MS
P3904Z03AHU AHU
POL909/POL6xx POL909/POL6xx
T+T
RemoteOPC
Server
MS Management station and Climatix RemoteOPC Server AHU Air handling unit POL909 Advanced Web Module POL6xx Climatix controller Modem Analog or GSM modem
Integration aims at providing all required controller data to the management station to be able to change selected set points and stages.
Like the remote OPC via Ethernet LAN, the remote OPC server is running on the Management Station and is reading and writing Climatix data point over the modem connection.
The integration is basically the same as the integration via Ethernet LAN, but with the following differences: • An Advanced Web Module POL909 is needed together with each controller. It
provides the Remote Access Server (RAS). The settings of the connections are different. See chapter 11 "Computer to modem connections". On the Management Station a RAS connection must be created for each Modem link.
Purpose
Example
Description
15 / 80
Siemens Remote OPC Server CB1P3904en Building Technologies Installation of the RemoteOPC Server 09.07.2011
3 Installation of the RemoteOPC Server 3.1 General
The Remote OPC Server is supplied as a Setup.exe file (for example: SetupRemoteOPC V8.00.exe).
If an older version of the Remote OPC Server is installed on the target computer, the server (runs as a service) must be deactivated prior to installation. We recommend that you uninstall the existing server.
The RemoteOPC Server is started as a Windows Service. This can either happen automatically when the computer is started up, or the user can do it manually. Standard PC with Windows NT or XP operating system plus network access.
If client and server are installed on different computers, a DCOM parameter setting is required. Specialist knowledge is required to set up a configuration of this nature and this is not covered in these commissioning instructions.
The OPC core components (server or clients) must be installed on the target computer prior to installation of the Remote OPC Server. The latest version of the OPC core components can be downloaded from the website of the OPC Foundation.
Link: http://www.opcfoundation.org/ Install OPC core component first, apart of the Remote OPC delivery.
The example below shows how to install Climatix RemoteOPC Server software:
Step Action 1 Execute the SetupRemoteOPC_Vxy.exe :
P3904O01
Click Next . 2 Select Start Menu Folder:
P3904O02
You can change the default start menu folder if required. This default setting is used for all instructions in this commissioning guide.
Version
Prerequisites software
OPC core elements
STOP
Installation steps
16 / 80
Siemens Remote OPC Server CB1P3904en Building Technologies Installation of the RemoteOPC Server 09.07.2011
General, continued
Step Action 3 Ready to Install:
P3904O03
The default settings are displayed once more prior to launching the installation. Click Install to start the installation: � A series of windows will now appear with information on the installation.
4 Completing RemoteOPC Server installation:
P3904O04
Installation is now complete.
The following folders and files are located under "C:\Program Files\SBT\RemoteOPC":
P3904O05
The log file "RemoteOPC.log" is located in the Log folder (see chapter 7.3 "View RemoteOPC.log file").
Installation steps, cont.
Folder Structure
Log File location
17 / 80
Siemens Remote OPC Server CB1P3904en Building Technologies Installation of the RemoteOPC Server 09.07.2011
3.2 RemoteOPC Licensing
This Climatix RemoteOPC Server needs a license to connect to Climatix controllers. The description below explains how to get and how to enter the necessary license to run the Climatix RemoteOPC Server.
A Remote OPC license is valid for installation of the server on one computer. During RemoteOPC software installation a license tool is provided on the target computer for this purpose. This license tool calculates a unique ID number based on various hardware components of the computer.
The RemoteOPC software has been installed properly according to the previous chapter.
To license the Climatix RemoteOPC software proceed as follows:
Step Action 1 Run RemoteOPC Activator.exe in the folder
C:\Program Files\SBT\Remote OPC created during software installation. A unique serial PC number is calculated:
P3904O06
2 Send this Serial number with the order of POL0L9.00/STD to your Siemens branch office to get the activating key.
3 Siemens will return you the requested activation key and billing the license cost.
4 Run RemoteOPC Activator.exe and enter the received license key. Then click the OK button to register the entered key:
P3904O07
5 Start to set up Remote OPC and run the service with the activated license.
If no valid license is available, the server will terminate with the message "LicenseViolation ===> NO VALID ACTIVATION KEY FOUND!" in the Log-File.
If some of the hardware components will be changed, the Serial No. and the Activation Key won’t match any more. In this case a new Activation key is needed.
Remote OPC License
Single installation License
Prerequisites
Licensing procedure
No valid Activation Key
18 / 80
Siemens Remote OPC Server CB1P3904en Building Technologies Installation of the RemoteOPC Server 09.07.2011
Blank page
19 / 80
Siemens Remote OPC Server CB1P3904en Building Technologies Configuration 09.07.2011
4 Configuration
This section describes the configuration of the Remote OPC Server:
Subject Chap. Configure controller 4.1 Configuration file 4.2 Parameters 4.3 Configure remote OPC over TCP/IP 4.3 Controller parameters, column D Configure remote OPC over TCP/IP via modem connection
4.3 do.
4.1 Configure controller
Each POL6xx controller with inbuilt Ethernet controller does have its own MAC address. For an OPC integration, the controllers need to have a certain IP address. There are two ways of getting an IP address: • Fixed IP • Dynamic IP (DCHP) It depends on the network topology, which way is chosen.
Contents
Configuration over HMI
20 / 80
Siemens Remote OPC Server CB1P3904en Building Technologies Configuration 09.07.2011
4.2 Configuration file
The configuration file is a *.csv file (character separated values) and is normally processed with the Excel tool. As well as describing certain control parameters, the file also describes all controllers linked to the OPC server. When the server is started, connections to all defined controllers are established. The server sets parameters for the data points that are to be managed and commences IO communication with all available controllers. Changes to this file come into operation with the next server start. If a controller name or it’s IP-Address in column A changes, the old Cache Files must be deleted.
The following table shows an example of a configuration file:
A B C D E F G
1 3 // Con_Retry ( number of dial tries to connect)
2 1 // Time_Con_Retry (timout between redials)
3 20 // Con_TimeOut, (time in minutes for Dial-In und AutoConnect links until the server gets off hook) 0=no timeout!
4 1 // Name in the RemoteOPC.log file: 0=link name (column A) 1=technological name (column B)
5 sbt_rcc_v2_22F3 Master_010 D 0x4000 MemLang.csv 6 // COM1 language
6 sbt_rcc_v2_22F4 Master_011 D 0x4000 MemLang.csv 6 // COM1 language
7 sbt_rcc_v2_22F5 Master_012 D 0x4000 MemLang.csv 6 // COM1 language
8 sbt_rcc_v2_22F6 Master_013 D 0x4001 MyMemLang.csv 6 // COM2 language
9 sbt_rcc_v2_22F7 Master_014 D 0x4001 MyMemLang.csv 6 // COM2 language
10 sbt_rcc_v2_22F8 Master_015 D -1 ShortMem.csv 6 // default language
11 sbt_rcc_v2_22F9 Master_016 D -1 ShortMem.csv 6 // default language
12
13 sbt_rcc_v2_22FA Master M -1 ShortMem.csv 6 // default language, Modem connection
14 POL687_FF4006 Slave_01 D -1 SlaveMem.csv 22 // the pure slave
With the MemLang file a fine tuning of the available OPC-Tags is possible, see chapter 6.2 "Optimizing the server".
Function of the file
Example
21 / 80
Siemens Remote OPC Server CB1P3904en Building Technologies Configuration 09.07.2011
4.3 Parameters
In case of using a modem connection to configure the remote OPC, some special settings have to be considered.
Below a list of the necessary settings and items:
Row Item Explanation 1 Con_Retry Number of dial attempts to connect to the remote
modem ("3" in the example). 2 Time_Con_Retry Time between redials in seconds ("1" in the
example). 3 Con_TimeOut Time in minutes for incoming modem connections
("20" in the example) The value 0 means no timeout.
4 Name Name of connection in the *.log file ("1" in the example) 0 = IP or domain name 1 = technological name
The following table explains the controller parameters:
Column Explanation A Controller's IP address or domain name. B Technological name of connection. This name is used for output in the
log file. C D = Direct LAN connection
M = Modem connection D Language to be used in object description, selection of OPC tags (see
chapter 4.2 "Configuration file"): -1 = Default Language 0x4000 = COM1 Language 0x4001 = COM2 Language
E Name of the MemLang file for this controller. See chapter 6.2 "Optimizing the server".
F Target Communication ID Saphir ACX32/34 = 6 POL687.xx = 22 POL63x.xx = 23
G Comment
A controller configuration row can be deactivated by indenting the row information (beginning in column "B"). This corresponds to a semicolon at the start of column "A".
Modem parameters
Controller parameters
22 / 80
Siemens Remote OPC Server CB1P3904en Building Technologies Configuration 09.07.2011
Blank page
23 / 80
Siemens Remote OPC Server CB1P3904en Building Technologies Commissioning 09.07.2011
5 Commissioning 5.1 Creating cache files
After successful installation and set up of the requested connections (Modem or Ethernet LAN), the Remote OPC Server now needs to be commissioned. It is necessary to generate certain cache files first, before the Remote OPC Server can run in normal operation mode.
Three configuration files must be available for each controller that is to be connected to the Remote OPC Server. These three files describe the selected data points of an application running in the controller. The choice of controller data points can be defined via the language selection (-1, 0x4000, 0x4001). This language dependent object definition is described via the object selection in the corresponding parameter files (ObjLang.csv and MemLang.csv), created as an OBH.bin file using the SCOPE tool and stored in the controller. If a controller application is changed, the relevant cache files must also be deleted and new files created in the configuration mode. Default path to the cache files: C:\Program Files\SBT\RemoteOPC\CacheFiles Examples for a controller with name "POL636_xxyy":
– POL636_xxyy_TypeInfo.bin – POL636_xxyy_TypeDesc.bin – POL636_xxyy_ObjData.bin
If no cache files are available for configured controllers or a controller application has changed, the files have to be created. The creation is done with the aid of the Cache files generator . Proceed as follows:
Step Action 1 Stop the "Remote OPC Server" service if running (e.g. in case you
added new controllers after the first commissioning). 2 Recommendations:
– Verify the connection to each controller directly connected with a "ping" before running the "Cache files generator".
– Test modem connections first, too. 3 Ensure that the corresponding old cache files are deleted before starting
configuration after reloading a controller application. 4 Start the "Cache files generator" in order to create the cache files:
Programs -> Climatix Suite -> OPC -> Cache files ge nerator 5 Click on the Generate button:
The generator will connect to each controller contained in the configuration file and check if cache files are available and up to date. If the cache files are not available or do not match the current application the relevant files will be created. � See pictures on next page. Note: A running session can be interrupted by pressing the Cancel button.
6 If all cache files are present, start the "Remote OPC Server" as a service (normal operating mode).
7 Check license, number of actual tags.
Introduction
Three cache files needed
Examples of file names
Create cache files TCP/IP
24 / 80
Siemens Remote OPC Server CB1P3904en Building Technologies Commissioning 09.07.2011
Creating cache files, continued
The following pictures show two examples of cache files creation by the "Cache files generator".
Example 1: All cache files have been successfully created.
P3904O14
Example 2: Two controller cache file creations failed.
P3904O15
Besides the information shown in the application window, a "Log.txt" file with current session information is available in the "CacheFiles" folder.
Creating cache files TCP/IP, cont.
Log.txt file
25 / 80
Siemens Remote OPC Server CB1P3904en Building Technologies Commissioning 09.07.2011
Creating cache files, continued
The OPC server creates four additional virtual tags for a modem connection. These are used for establishing and hanging up a connection, as well as for information on connection status. Tag Explanation ManualConnect (read/write) Set tag to "1": An outgoing modem connection is
set up Hang up (read/write) An existing modem connection is hung up. ModemConnection (read) 1 = Modem connection exists
0 = No modem connection active TCPIPConnection (read) A TCPIP connection exists via the modem
connection. LanguageID COM language used to create the cache files. It
can be COM1 = 0x4000, COM2 = 0x4001 or as default -1 = application language.
The creation of cache files for a controller via a modem proceeds as follows:
Step Action 1 Set the virtual tag "ManualConnect" to "1" using the OPC client.
Note: A configured RAS connection on the computer is required to establish the connection.
2 Once the connection is established, the "ModemConnection" tag and soon afterwards the "TCPIPConnection" tag assume the status TRUE. The cache files are created and the connection is hung up after.
3 One modem connection after another (or in parallel, depending on the No. of available modems) can be set up in this way in order to create the files.
Modem connection
Tags, explanation
Create cache files via modem connection
26 / 80
Siemens Remote OPC Server CB1P3904en Building Technologies Commissioning 09.07.2011
Blank page
27 / 80
Siemens Remote OPC Server CB1P3904en Building Technologies Optimizing the RemoteOPC Server 09.07.2011
6 Optimizing the RemoteOPC Server 6.1 Quantity structure
The following declarations are not verified yet ! The amount of controllers, respectively the amount of members per controllers which can be handled by the RemoteOPC Server, mainly affects the needed memory for the so-called „Name Space" area. It means, that we can not forecast a possible CPU load only with a view on these two parameters.
Mainly, if an OPC-Client connects to the RemoteOPC-Server and subscribes tags out of the „Name Space", the CPU load will increase. While an item is subscribed, a COV declaration is done for the appropriate object to the controllers Object-Handler with the result of a value update (COV-Event) send to the RemoteOPC Server. During this OPC-Client connection, the CPU load will be the highest, until all tags are subscribed. This is because of the reason that COV's happen while a new subscription runs and also the already subscribed items will send COV events due to value changes on the controller.
If all the subscription is done the load should decrease, because from then on only the COV updates affected by value changes will occur. In this normal operation condition, mainly the COV events and the read member cycle time of the OPC-Client, make up the CPU load, caused by the RemoteOPC-Server and the Client.
If in this normal running condition the CPU is overloaded (near 100% all the time), the following parameters should be reviewed. • Number of tags, subscribed by an OPC-Client (minor influence). • Number of COV-Events per second (major influence). • Update cycle time used by an OPC-Client (medium influence).
The No. of controllers handled by the RemoteOPC Server is not really restricted. It should be no problem to handle 500 controllers with one server.
The No. of OPC items per controller, also depends on the No. of controllers handled by the RemoteOPC-Server. The overall OPC items shouldn’t considerably exceed 30'000.
The No. of COV events per second mainly cause the CPU load needed by the RemoteOPC Server. • If the load is permanently near 100%, it should be decreased by tuning the COV
thresholds. • Also the No. of subscribed OPC tags by an OPC client is a question which has
to be reconsidered: Is it reasonable to subscribe always all possible tags, or is it more efficient just to subscribe the currently needed items, e.g. for a plant view screen page on a SCADA system?
Introduction
CPU load on connection
CPU load in normal operation
Parameters to be reviewed
Amount of controllers
Amount of OPC items per controller
No. of COV events
28 / 80
Siemens Remote OPC Server CB1P3904en Building Technologies Optimizing the RemoteOPC Server 09.07.2011
6.2 Optimizing the server
The number of data points for the OPC server function of a controller should be limited using the "Object-Language" (ObjLang.csv) and "Member-Language" (MemLang.csv) description files on the OPC tags to be used. It makes no sense to have all data points of a controller created in the cache files. This creates unnecessary overheads and considerably impairs performance.
The languages COM1 (0x4000) and COM2 (0x4001) are available for data point selection. The corresponding language is saved in the OPC server configuration file, with -1 standing for the application language and thus for selection of all data points.
The modules to be used are selected in the Object-Language. In this way, all members of a selected module are available. If you wish to limit the selected modules to certain members, this is further restricted in the member language. This means that it is only possible to select members that are actually to be read or written using OPC.
Below an example file:
A B C D E F
0x1003 0xC56A39DD 0x1100 Heating
0x1012 0xC56AE07F 0x1100 HeatingReg HeatingReg Värme
0x1003 0xC56AE6CA 0x1100 HMI_Switch
0x1012 0xC56AA581 0x1100 HMISwitchFunc HMISwitchFunc Function
0x1003 0xC56A003D 0x1100 HeatRecovery
0x1012 0xC56A16CF 0x1101 HRC*Dmpr*Plade*Wat HRC*Dmpr*Plade*Wat Rot-VVX* Återluft*Pl...
0x1003 0xC56AD159 0x1100 HRC_Eff
Column Explanation
A Type and instance (ID) B Object name member or virtual member C Object type's application name D COM1 language 0x4000; two objects are enabled here for the OPC
server. E COM2 language 0x4001; one object is enabled here for the OPC
server. F The HMI languages start from here
The information on whether COM1 or COM2 is selected is defined in the RemoteOPC Server configuration file.
The number of OPC server tags is greatly reduced through the selective enabling of objects.
Data point selection
Object selection
Explanation to the columns
29 / 80
Siemens Remote OPC Server CB1P3904en Building Technologies Optimizing the RemoteOPC Server 09.07.2011
Optimizing the server, continued
Below an example of MemLang file:
A B C D E
0x1012 0x1000 FullSize
0x1012 0x1001 DynamicSize
0x1012 0x1100 ObjectName
0x1012 0x1101 StatusText
0x1012 0x0000 UserAccess UserAccess
0x1012 0x0001 HighLimit HighLimit
0x1012 0x0002 Setpoint Setpoint
Column Explanation
A Object type Setpoint ENUM 0x1012 B All members of this object type C Corresponding member name (application name) D COM1 language 0x4000; the members 0, 1 and 2 are enabled here for
the OPC server. E COM2 language 0x4001
In the OPC server, the members 0, 1 and 2 are offered to all the SetpointEnum object types (0x1012) available in the application.
For object types with a large number of members, such a selection can greatly reduce the number of OPC tags offered for each object type.
The COV threshold can be optimized with the COV setting of an object.
The COV thresholds for all objects can be predefined with entries in the registry HKEY_LOCAL_MACHINE\SOFTWARE\SBT\RemoteOPC subject to a range of values (high and low limits). For the list of all registry setting see chapter 6.4 "Registry entries". Member x has a value range from 0 to 5. The COV threshold 0.0001 is used here. Member y has a value range up to 5000. The COV threshold 0.3 is used here.
P3904O08 1. You can navigate to the relevant object using the tree view of an OPC client
and set the COV threshold (write member). When the server terminates, all COV’s will be saved in the "Cov" directory in a file named like the controller and the extension CovValueTable.txt. In the appropriate file you must set the Flag of the member to "1" to activate the specific threshold with the next server start.
2. You can change the wanted threshold values in the COV files (also set the Flag to "1" before starting the server.
Member selection
Explanation to the columns
COV optimization
Example
Setting the COV threshold values
30 / 80
Siemens Remote OPC Server CB1P3904en Building Technologies Optimizing the RemoteOPC Server 09.07.2011
Optimizing the server, continued
Example of saved COV files:
P3904O09
When the server is started, the COV thresholds from the registry are read first and applied across-the-board for all objects. After this default initialization, the saved object-specific COV thresholds where the Flag is set to "1" overwrite the default threshold values.
In this way, the events of an OPC server controller can be optimized, thus reducing the CPU load when there is a large volume of OPC tags.
Conversely, a tag update can be forced with each cycle of the controller (test case) if the COV threshold is set to 0.
P3904O10
An entry consists of object type, object ID, COV1 and COV2 threshold.
COV optimization, cont.
Initialization
Benefit of optimization
Forced tag update
31 / 80
Siemens Remote OPC Server CB1P3904en Building Technologies Optimizing the RemoteOPC Server 09.07.2011
6.3 Optimizing the client
There are three measures for optimizing:
Measure Explanation
1 The client should only include the OPC server tags that are required for the current display or operation.
The server's performance will be impaired if all available OPC tags are included.
2 Adapting polling cycle to startup and operating status.
3 Optimizing COV parameters.
OPC server with 20'000 tags:
When an OPC client which includes all tags of the server is started up, it takes approximately 120 minutes for all data in the client to assume the status "GOOD".
This startup time strongly depends on the client's polling cycle and the COV thresholds set.
During startup, the server requests all values at once. The server reads all requested values from the controller. At the same time, the client polls the server and COV updates are applied.
A more favorable startup time can be achieved if the client's polling cycle during registration has a relatively high value (for example: 5s or higher) and then, once all values have been registered, this cycle is decreased to an operating status value (2s for instance).
Optimizing the COV parameters and the client polling cycle help to reduce die CPU load when there is a large number of tags. This in turns greatly reduces the startup time. The polling cycle can be changed during operation in most clients.
Measures for optimizing
Example
Reasons for long startup time
Adapting polling cycle
32 / 80
Siemens Remote OPC Server CB1P3904en Building Technologies Optimizing the RemoteOPC Server 09.07.2011
6.4 Registry entries
The following registry entries were created under the following folder. HKEY_LOCAL_MACHINE\SOFTWARE\SBT\RemoteOPC
P3904O11
0=no unit switching, 1=unit switching on, 2=use metric unit system, 3=use imperial unit system 0=highest 65535=lowest 0=no Trace 1=Trace After a controller reconnection, the COV registrations can be traced into a controller specific file. The file name is the technological name of the controller and is placed into the COV folder. Reconnection Timeout 0=No link connection retry wanted. x=Time in Seconds between connection retries.
Registry settings of Remote OPC Server
Engineering Unit
Security Level
TraceCOV
ReConTio
33 / 80
Siemens Remote OPC Server CB1P3904en Building Technologies Running the RemoteOPC Server 09.07.2011
7 Running the RemoteOPC Server 7.1 OPC Server operation as Windows service
Command input for start :
Start-> Programs-> Climatix Suite-> OPC->Start Service The server is started as a "Windows Service" for normal operation. This operating mode runs in the background and is not represented by any icon on the monitor. Suitable OPC clients can now connect to the server. Command input for stop :
Start-> Programs-> Climatix Suite-> OPC->Stop Service The OPC service is stopped. It is important to ensure that all clients were stopped before the service is stopped.
7.2 Running the server automatically
An OPC server is capable of starting automatically as soon as a client attempts to connect to this server. The server stops again when the last client logs off.
It is not intended to use this operating mode for the RemoteOPC Server.
Reason: The RemoteOPC Server would behave in the correct way and would start and be operational. However, the service will remain on after the last client logs off.
If the RemoteOPC Server needs to be started automatically when the computer restarts, the parameters for this can be set using the Windows Service Control Manager.
Start-> Settings-> Control Panel-> Administrative Tools->Services
P3904O12 In the column "Startup Type", the start type must be set to "Automatic".
Handling and process
Automatic start by client attempts
Use Windows Service Control Manager
34 / 80
Siemens Remote OPC Server CB1P3904en Building Technologies Running the RemoteOPC Server 09.07.2011
7.3 View RemoteOPC.log file
When the server is started, the log file "RemoteOPC.log" opens. The file: • shows the server version • provides information about controllers to be connected • shows the connection status of the controllers during operation
P3904O13
By default, the file is located under C:\Program Files\SBT\RemoteOPC\Log. The file content can be viewed with a text editor. The log file can be opened by going to Start->Programs->Climatix Suite->OPC->Logfile.
When the server is started, various settings from the configuration file are shown along with the version. – After that, the individual controllers indicated in the configuration file are listed
under their "technological name". – Information on the cache files and the connection status is then given. – The message "Server successfully started" indicates that the server is
operational. The message "No incoming Modem calls accepted!" appears if none of the controllers was configured using a modem connection.
– Every entry in the log file has a timestamp.
Contents of the file
Example
Location of the file
Server information
35 / 80
Siemens Remote OPC Server CB1P3904en Building Technologies Running the RemoteOPC Server 09.07.2011
View RemoteOPC.log file, continued
If a connection status changes during operation, the user will be notified.
P3904O23 Controller WiGa_0FC2 is disconnected from and then reconnected to the LAN.
The connection status of all controllers is monitored during operation via a "KeepAlive" function. If the connection is interrupted (for example: controller's RJ45 connector is removed or controller was switched off), the server will try to reestablish the connection. The above example shows the relevant messages from the log file.
7.4 Troubleshooting
When the server is started, the component "RainbowCOMHandler.exe" is also always started. It must also stop (approx. 5s) after the server stopped. The component does not stop if the server did not stop in the proper way, for example, if it crashed or was stopped using the "Task Manager". This will cause problems the next time the server is started. The component then exists in duplicate. In this case, a client will not be connected to the server. A possible workaround involves first ending the processes "RemoteOPC.exe" and "RainbowCOMHandler.exe" using the Windows Task Manager and then restarting the server. RainbowCOMHandler.exe should only appear once in the process list.
We distinguish between: • Outgoing connection • Incoming connection See chapter 11.3 "Creating a RAS entry for outgoing connections".
When setting the controller parameters, you can decide whether an alarm should trigger the establishment of a connection to the OPC server. An "incoming connection" must already be configured on the computer. When the event is triggered, the controller will call the computer and establish the connection. A SCADA application can now react via the virtual tag "TCPIP/Connection" and show the corresponding page with current data on this connection. An incoming connection will be disconnected again after the "Con_TimeOut" delay (see chapter 4.3 "Parameters" There will be no timeout if this value was defined as "0".
Error messages
Example
"KeepAlive" function
RainbowCOMHandler
Possible problem
Workaround
Modem connection
Outgoing connection
Incoming connection
36 / 80
Siemens Remote OPC Server CB1P3904en Building Technologies Running the RemoteOPC Server 09.07.2011
Blank page
37 / 80
Siemens Remote OPC Server CB1P3904en Building Technologies OPC client view 09.07.2011
8 OPC client view 8.1 OPC tag selection
After configuration and commissioning the Remote OPC it is needed to validate the available OPC tags with an OPC client (example Softing OPC Client):
P3904O16 Virtual controller data points are always available, regardless of the data point selection -1, 0x4000 or 0x4001.
In the case of a direct connection, only the virtual data point "TCP/IP Connection" is available. The current controller connection status is displayed here.
For a modem connection, a further four virtual data points exist alongside the virtual data point "TCP/IP Connection". These are used • to set up a connection manually, or • to display the status of a modem connection. If the "ManualConnect" data point is set to "1" using a client, the server polls the controller using a RAS connection with parameters already assigned.
– The controller name from the RemoteOPC configuration must be the same as the RAS connection name.
– When the modem connection is established, the "ModemConnection" tag changes to "TRUE", and as soon as the TPC/IP connection exists, the "TCPIP Connection" tag changes to "TRUE".
This status indicates an existing TCP/IP connection via the modem. The OPC tags will now be updated. A manually set-up modem connection has no timeout. In order to hang up the connection, the "HangUp" tag must be set to "TRUE". The "LanguageID" tag is used to define the configuration to be read (-1, 0x4000, 0x4001) in order to create the cache files.
Example Softing client
Virtual OPC tags
Direct LAN connection
Modem connection
"ManualConnect" data point
"HangUp" tag
"LanguageID" tag
38 / 80
Siemens Remote OPC Server CB1P3904en Building Technologies OPC client view 09.07.2011
8.2 Searching and selecting
The number of clients logging on to the RemoteOPC Server is not limited and is determined solely by the computer's resources. In practice, however, only one client (SCADA system) will ever log on to the server. A maximum of three OPC client accesses have been tested on a RemoteOPC Server.
In the following you find examples of a Softing OPC test client In this example, the OPC client is searching for local DataAccess V3 servers:
P3904O17 Note: The RemoteOPC DA server also appears.
Number of clients
Example of a Softing OPC test client
Client searching servers
39 / 80
Siemens Remote OPC Server CB1P3904en Building Technologies OPC client view 09.07.2011
Searching and selecting, continued
The RemoteOPC Server is selected:
P3904O18 The server is shown on the left-hand side of the client. A group was also created when the RemoteOPC Server was selected. The group's name was changed here to "Saphir_OPC".
On the right-hand side of the client, five controllers with the technological names 04DD, 0B47, 0FC2, 0B0E and 0A4A can be seen in this example. The controller 04DD is expanded.
Selecting Remote OPC Server
Explanations to the picture
40 / 80
Siemens Remote OPC Server CB1P3904en Building Technologies OPC client view 09.07.2011
Searching and selecting, continued
Clients usually allow the user the option of selecting individual data points in a level or all data points:
P3904O19 In this example, three system clock OPC tags were selected.
The data is updated and the status displayed in the "Quality" column:
P3904O20
Selecting data points
DA Items view
41 / 80
Siemens Remote OPC Server CB1P3904en Building Technologies OPC client view 09.07.2011
Searching and selecting, continued
If the connection to the controller is interrupted, the "Quality" changes to "Uncertain" after a short interval:
P3904O21
After a few seconds with no connection, the status will then change to "BAD (not connected)":
P3904O22
Connection to controller interrupted
42 / 80
Siemens Remote OPC Server CB1P3904en Building Technologies OPC client view 09.07.2011
Blank page
43 / 80
Siemens Remote OPC Server CB1P3904en Building Technologies SAPHIR RCC setup 09.07.2011
9 SAPHIR RCC setup 9.1 Start page
The parameters of the RCC card on the Saphir controller can be set using a web browser. One way of doing this is by entering the name of the RCC or the IP-address with Internet Explorer. – The name is always SBT_RCC_V2_xxxx , with xxxx being replaced by the last
four digits of the MAC address. – The MAC address is indicated on a label located on the RCC card.
Step Action 1 Enter the appropriate data into the web browser.
� The start page of the RCC Web server appears:
P3904O24
2 Select Open RMS to go to the configuration page.
General procedure
44 / 80
Siemens Remote OPC Server CB1P3904en Building Technologies SAPHIR RCC setup 09.07.2011
9.2 RAS parameters for an outgoing call
Step Action 1 Select RAS Config in the configuration menu:
P3904O255
2 Enter the controller's dial-up connection parameters .
The following parameters are to be entered:
Parameter Explanation Name of Connection Choose any name, such as the technological name of the
controller. Phone Number Phone number of modem on server computer.
Tel. of target computer User Name Enter name. It must match the UserName of the RAS
connection on the computer. Password It must correspond with the password of the RAS
connection on the computer. Has to be the same as password you define later in the User
RAS configuration
Parameter entries
45 / 80
Siemens Remote OPC Server CB1P3904en Building Technologies SAPHIR RCC setup 09.07.2011
9.3 RAS parameters for an incoming call
To allow an incoming call, one ore more RAS users must be defined in two steps. This is done in the Server Config page:
Step Action 1 Define one ore more RAS users in the User Manager :
P3904O45 The user "REMOTEOPC" is added in the above picture
2
Activate the user or users for the RAS service:
P3904O26 In this example the user "REMOTEOPC" is activated to use the RAS service. The change gets available after a RCC reset.
Server configuration
46 / 80
Siemens Remote OPC Server CB1P3904en Building Technologies SAPHIR RCC setup 09.07.2011
9.4 Trigger event to initialize an outgoing call automatically
The parameters for a trigger event can be set in the RAS Config page. When this event occurs, a modem connection to the RemoteOPC server computer is established. Once the connection is established, the corresponding OPC tag "ModemConnection" is set to TRUE. A client (Building Management System) would then be able to react as appropriate.
P3904O27
Parameter Explanation Trigger string (Typ ID MemberID)
Example: 'Unit 1'‚ 'HierarchyNewFault’ OPC Alarm server name Always use IP number, compare with the TCP/IP
address assignment, define later. You can use the same IP range as described here. And use Port 42058
Function
Parameter entries
47 / 80
Siemens Remote OPC Server CB1P3904en Building Technologies AWM setup 09.07.2011
10 AWM setup 10.1 General
The setup is most likely the same as the one for the Saphir RCC if the RMS pages of the AWM are called by a browser.
Example: http://POL687_FF4006/rms
If the AWM will get configured via the MCT WEB-Interface, use the AWM documentation (CB1P3935en_0.8) for detailed information.
Call it either via POL909_FF43DA/MCT or call POL909_FF43DA and click the button Management . The MCT might be protected by a password.
10.2 RAS incoming calls
As default, the RAS incoming call of the AWM (since version BSP 9.10) is not activated. To activate the RAS "incoming call" functionality, do the followings steps:
Step Action 1 Call the RMS page > Registry Manager and navigate to the following
key: HKEY_LOCAL_MACHINE\Comm\ppp\Server\Line\Standard Modem on COM1:
2
Set the Enable to 1. A "Persist Registry" is needed if you want to keep the settings also after a reboot.
From now on "Incoming Calls" are accepted if a RAS user (e.g. REMOTEOPC) has been created.
Main principle
Configuration via MCT WEB-Interface
STOP
Activate RAS "incoming call"
48 / 80
Siemens Remote OPC Server CB1P3904en Building Technologies AWM setup 09.07.2011
10.3 RAS user creation
To create a new RAS user proceed as follows:
Step Action 1 Select the User Management tab in the Management menu.
� The list of existing users is shown:
P3904O46
2
Click Add a new user. � The Edit user input page opens:
P3904O47
Enter user name and password . 3 Complete the inputs by clicking OK.
� The list of users shows the new entry:
P3904O48
4 Allocate the user to groups via the Edit group membership icon in the Options menu and confirm your entries with OK.
P3904O50
Note: The user must at least belong to the RasUsers group.
Procedure
49 / 80
Siemens Remote OPC Server CB1P3904en Building Technologies AWM setup 09.07.2011
10.4 RAS dial-up creation
Such a connection will be established if a parameterized event occurs.
To create a dial-up connection proceed as follows:
Step Action 1 Select the Dial-up connections menu in the Network tab.
� The list of existing connections is shown:
P3904O51
2 Click Add a new connection. The General settings input fields opens:
P3904O52
Fill in the connection parameters and confirm your entries with OK. 3 Optionally customize the new connection in the Advanced settings
input fields and confirm your entries with OK.
P3904O53
Procedure
50 / 80
Siemens Remote OPC Server CB1P3904en Building Technologies AWM setup 09.07.2011
RAS dial-up creation, continued
Step Action 4
Activate a connection by clicking the traffic light symbol in the Options menu.
Just one dial-up connection can be active. Example 1 The previously defined dial-up connection POL909_FF43DA is inactive:
P3904O54 Example 2 The dial-up connection POL909_FF43DA is set to active:
P3904O55 Example 3 Connection POL909_FF43DA again is set to active whereas connection POL909_FFABCD is inactive:
P3904O56
Procedure, cont.
51 / 80
Siemens Remote OPC Server CB1P3904en Building Technologies AWM setup 09.07.2011
RAS dial-up creation, continued
Step Action 5 Define the Trigger events in the Dial-up connections menu and confirm
your entries with OK.
P3904O57
Procedure, cont.
52 / 80
Siemens Remote OPC Server CB1P3904en Building Technologies AWM setup 09.07.2011
Blank page
53 / 80
Siemens Remote OPC Server CB1P3904en Building Technologies Computer to modem connections 09.07.2011
11 Computer to modem connections 11.1 General
Both outgoing (computer dials the controller) and incoming connections (Climatix controller dials the computer) can be established with the RemoteOPC Server computer and a Climatix controller. In the case of an incoming call, a connection is usually established to provide an event alert (event trigger). A RAS connection must be set up on the computer in order to create a modem link between the RemoteOPC Server computer and a controller. See chapter 9 "SAPHIR RCC setup" for instructions on how to set the controller's parameters. The figure shows an example for RAS connection to Climatix controllers:
MS
P3904Z03AHU AHU
POL909/POL6xx POL909/POL6xx
T+T
RemoteOPC
Server
MS Management station and Climatix RemoteOPC Server AHU Air handling unit POL909 Advanced Web Module POL6xx Climatix controller Modem Analog or GSM modem
On the following pages you find the instructions how to create the RAS entries on the computer for: • incoming connections • outgoing connections
Outgoing and incoming connections
Incoming call
RAS connection
Example of use
Setup
54 / 80
Siemens Remote OPC Server CB1P3904en Building Technologies Computer to modem connections 09.07.2011
11.2 Creating a RAS entry for incoming connections
To create a RAS entry for incoming connections proceed as follows:
Step Action 1 Go to the Control Panel with Start >>>> Settings >>>> Control Panel and click
the Network Connections icon. The window Network Connections opens:
P3904O28
2 Click Create a new connection . The New Connections Wizard opens:
P3904O29
3 Click Next and then select Set up an advanced connection :
P3904O30
Procedure
55 / 80
Siemens Remote OPC Server CB1P3904en Building Technologies Computer to modem connections 09.07.2011
Creating a RAS entry for incoming connections, continued
Step Action 4 Click Next and then select Accept incoming connections:
P3904O31
5 Click Next and then choose all modems your computer uses to accept incoming connections from controllers:
P3904O32 Remark: Only one modem is available and selected in this example.
6 Click Next and then select Allow virtual private connections :
P3904O33
Procedure, cont.
56 / 80
Siemens Remote OPC Server CB1P3904en Building Technologies Computer to modem connections 09.07.2011
Creating a RAS entry for incoming connections, continued
Step Action 7
STOP
Click Next and then select the users allowed to connect:
P3904O34
The user name and password have to match the RCC settings.
8 Click Next and then select TCP/IP properties:
P3904O35
9 Click Next and then enter the IP settings for modem connections:
P3904O36
Procedure, cont.
57 / 80
Siemens Remote OPC Server CB1P3904en Building Technologies Computer to modem connections 09.07.2011
Creating a RAS entry for incoming connections, continued
Step Action 10 Click OK to complete the New Connection Wizard:
P3904O37
11 Click Finish : The connection is created and saved.
Procedure, cont.
58 / 80
Siemens Remote OPC Server CB1P3904en Building Technologies Computer to modem connections 09.07.2011
11.3 Creating a RAS entry for outgoing connections
To create a RAS entry for outgoing connections proceed as follows:
Step Action 1 Go to the Control Panel with Start >>>> Settings >>>> Control Panel and click
the Network Connections icon. The window Network Connections opens:
P3904O28
2 Click Create a new connection . The New Connections Wizard opens:
P3904O29
3 Click Next and then select Connect to the network at my workplace :
P3904O38
Procedure
59 / 80
Siemens Remote OPC Server CB1P3904en Building Technologies Computer to modem connections 09.07.2011
Creating a RAS entry for outgoing connections, continued
Step Action 4 Click Next and then select Dial-up connection :
P3904O39
5
STOP
Click Next and then enter either the Name or the IP address :
P3904O40 The connection name must match the name in the RemoteOPC configuration file.
When connecting using the virtual tag "ManualConnect", the OPC server will use this name to find the phone connection.
6 Click Next and then enter the Phone number of the controller you wish to connect to.
P3904O41
Procedure, cont.
60 / 80
Siemens Remote OPC Server CB1P3904en Building Technologies Computer to modem connections 09.07.2011
Creating a RAS entry for outgoing connections, continued
Step Action 7 Click OK to complete the New Connection Wizard:
P3904O42
8 Click Finish : The connection is created and saved.
Pay attention to the following rules and hints for RAS entries: • A RAS entry is required for every controller to be connected via the modem(s). • The name of the entry must match the domain name of the controller (for
example: SBT_RCC_V2_xxxx ). • If only one modem is connected and several remote controllers can be dialed,
the same modem must be used for every RAS connection. The disadvantage of this is that only one connection to a controller can be active.
• You can test the connection manually with configured controllers (RAS configuration).
• If no connection is found, the cause can usually be traced to the username or password.
Procedure, cont.
Rules and hints
61 / 80
Siemens Remote OPC Server CB1P3904en Building Technologies Computer to modem connections 09.07.2011
Creating a RAS entry for outgoing connections, continued
After a connection has been created proceed as follows:
Step Action 1 Open the property dialog with a right mouse click and select Network >
InternetProtocol(TCP/IP) > Properties >Extendet >Ge neral 2 Remove the default gateway selection:
P3904O43
If the default gateway is selected, some system action slow down if the communication tries to send data via the local network first.
If the controller got an IP-Address in the LAN network before, the name table must be reset before making a modem connection.
This is done as follows:
With the command shell type in the command: nbtstat –R
P3904O44
Remove default gateway selection
STOP
Reset the name table
62 / 80
Siemens Remote OPC Server CB1P3904en Building Technologies Computer to modem connections 09.07.2011
Blank page
63 / 80
Siemens Remote OPC Server CB1P3904en Building Technologies Standard application AHU V1.x 09.07.2011
12 Standard application AHU V1.x 12.1 Overview
Standard applications for Climatix comprise predefined monitoring and control functions for a particular plant type. Features: • OEM customers receive standard applications as a set of loadable files. They
can be loaded in the controller via SD card. • An HMI operator unit allows for assigning inputs and outputs to the respective
plant as well as select, configure and parameterize the required functions.
Standard application AHU V1.x is available at this time. It contains all common functions to control and monitor air conditioning units (Air Handling Units). The following diagram provides an overview of selectable measured values and control equipment:
See document CE1P3977en for a detailed description of standard application AHU V1.x.
What are standard applications?
Standard application AHU V1.x
Detailed information
64 / 80
Siemens Remote OPC Server CB1P3904en Building Technologies Standard application AHU V1.x 09.07.2011
12.2 OPC tags of AHU V1.x
The following tables list all OPC tags provided by standard application AHU V1.x to integrate Climatix in a building automation and control system.
The list is grouped by object type or in special cases more detailed grouping, the object type is then described separately. This can be useful when parameters used for each object type must be changed via the Memlang file. See description in chapter 6.2 "Optimizing the server".
The list also describes the hierarchy and the full OPC tag name excluded the specific parameter/tag name for each object, example PresentValue or TimeDelay.
The full OPC tag name always starts with the technological name, for the connection, used in the configuration file. Here presented just as "TechnologicalName".
TechnologicalName, Hierarchy, objects and parameters are separated with a dot "." TechnologicalName=Office: Office.Device.Unit.OutTmp.PresentValue
TechnologicalName. Object name Object type Object description VirtualControl Virtual tags Virtual tags for connection
Device Hierarchy, Device Climatix controller
TechnologicalName.Device. Object name Object type Object description State texts
System Hierarchy, Collection System related functions
Unit Hierarchy, Unit Unit e.g. AHU related functions
Global Hierarchy General functions Alarms Hierarchy General alarm functions
Comm Hierarchy General communication functions
Diagnostic Systemobject Application information
AckAlmPls Setpoint Multistate Alarm acknowledge – Off
– On
TechnologicalName.Device.System. Object name Object type Object description
SystemClock Systemobject Systemclock for the controller
IP-Config Systemobject IP configuration for the controller
Introduction
Grouping of the list
Syntax OPC tag name
Example full OPC tag name
Top hierarchy
Device
System objects
65 / 80
Siemens Remote OPC Server CB1P3904en Building Technologies Standard application AHU V1.x 09.07.2011
OPC tags of AHU V1.x, continued
TechnologicalName.Device.Unit. Object name Object type Object description LOL HIL Dim. SupplyTmp Analog Input Supply air temp -64.0 99.0 °C RoomTmp “ Room temperature -64.0 99.0 °C RoomTmp2 Room temperature 2 -64.0 99.0 °C
RmUTmp1 “ Roomunit 1 temperature -64.0 99.0 °C
RmUTmp2 Roomunit 2 temperature -64.0 99.0 °C
ReturnAirTmp Exhaust air temp -64.0 99.0 °C OutTmp Outside air temp -64.0 99.0 °C HtgFrstTmp Heating frost tmp -64.0 99.0 °C HrecWtrTmp Hrec water tmp -64.0 99.0 °C ExhaustTmp Extract air tmp -64.0 99.0 °C HrecSupplyTmp Hrec supply air tmp -64.0 99.0 °C ExtraSupplyTmp Supply air tmp 2 -64.0 99.0 °C ExtraFrstTmp Heating 2 frost tmp -64.0 99.0 °C SupplyPrs Supply air pressure 0.0 5000.0 Pa ReturnPrs Exhaust air press 0.0 5000.0 Pa SupplyFlow Supply air flow 0.0 40000.0 l/s ReturnFlow Exhaust air flow 0.0 20000.0 l/s HrecFrstPrs Hrec frost pressure 0.0 5000.0 Pa SupplyHum Sply air hum rel 0.0 100.0 %rH RoomHum Room humidity rel 0.0 100.0 %rH OutHum Outs air hum rel 0.0 100.0 %rH AirQuality Air quality 0.0 3000.0 ppm ExtSetpointSpv External setpoint -64.0 64.0 °C AuxTmp Auxiliary tmp -64.0 99.0 °C
TechnologicalName.Device.Unit. Object name Object type Object description LOL HIL Dim. SplyFanVarPos Analog Output Sply fan outp sign 0 100 % ExhFanVarPos “ Exh fan outp signal 0 100 % HumidityCtrlPos Hum outp signal 0 100 % ElectricalHtgPos El htg outp signal 0 100 % HrecDampPos Hrec dmpr outp sign 0 100 % HrecPos Hrec outp signal 0 100 % CoolingPos Cooling outp signal 0 100 % HeatingPos Heating outp signal 0 100 % ExtraElHtgPos El htg 2 outp sign 0 100 % ExtraHtgPos Htg 2 outp signal 0 100 % ExtraClgPos Clg 2 outp signal 0 100 % AuxOutput Aux A outp fan 0 100 %
Analog Inputs
Analog Outputs
66 / 80
Siemens Remote OPC Server CB1P3904en Building Technologies Standard application AHU V1.x 09.07.2011
OPC tags of AHU V1.x, continued
TechnologicalName.Device.Unit. Object name Object type Object description HIL LOL ValidRoomTmp Display Value Act room tmp SuCmpFanPrVal “ Act summer comp fan WiCmpFanPrVal Act winter comp fan SplyFanActVal Act sply fan value ExhFanActVal Act exh fan value SplyFanActSpv Act sply fan stpt ExhFanActSpv Act exh fan stpt AirQCmpPrVal Act airquality comp SplyEnth Supply air enthalpy SplyHumAbs Supply air hum abs RmEnth Room enthalpy RmHumAbs Room humidity abs ActCascSpvHum Act sply hum stpt ActCascSpvDeh Act sply dehum stpt ActMainSpvHum Act hum stpt ActMainSpvDeh Act dehum stpt ActCtrlValHum Act controlled hum FanCmpHumPrVal Act fan comp hum DeHumidityPrVal Act dehum value OutEnth Outs air enthalpy OutHumAbs Outs air hum abs Dewpoint Analog Value Dew point 64.0 -64.0 SuCmpTmpPrVal Display Value Act summer comp tmp WiCmpTmpPrVal “ Act winter comp tmp ActCascSpvHtg Act sply htg stpt ActCascSpvClg Act sply clg stpt ActMainSpvHtg Act heating stpt ActMainSpvClg Act cooling stpt ActCtrlVal Act controlled tmp FanCmpTmpPrVal Act fan comp tmp HrecDampRec Hrec dmpr recov val FanHtgPrVal Act fan htg value FanClgPrVal Act fan clg value HrecEffEff Analog Value Hrec efficiency 101.0 0.0
TechnologicalName.Device.Unit. Object name Object type Object description HIL LOL ExtControlDlyOfTm Setpoint Value Ext ctrl off delay NightCoolRmSpv “ Night clg room stpt NightCoolRmHys Night clg room hys NightCoolMinOutTmp Night clg minOutTmp NightCoolOnDiff Night clg on delta TmpStartHtgStrt Tmp start start htg TmpStartHtgSpv Tmp start htg stpt TmpStartClgStrt Tmp start clg start TmpStartClgSpv Tmp start clg stpt BoostRmSpv Boost room tmp stpt BoostPreStrtTm Boost comp time BoostHtgSpv Boost start htg BoostClgSpv Boost start clg
Analog Values
Analog Setpoints
67 / 80
Siemens Remote OPC Server CB1P3904en Building Technologies Standard application AHU V1.x 09.07.2011
OPC tags of AHU V1.x, continued
TechnologicalName.Device.Unit. Object name Object type Object description HIL LOL SlaveOffset Setpoint Value Fan slave offset
SplyFanSpvSt1Spv Setpoint Value Limit Sply fan st1 stpt 5000.0 0.0
SplyFanSpvSt2Spv “ Sply fan st2 stpt 5000.0 0.0 SplyFanSpvSt3Spv Sply fan st3 stpt 5000.0 0.0 SplyFanSpvMaxForce Sply fan max force 4900.0 0.0 ExhFanSpvSt1Spv Exh fan step 1 stpt 5000.0 0.0 ExhFanSpvSt2Spv Exh fan step 1 stpt 5000.0 0.0 ExhFanSpvSt3Spv Exh fan step 1 stpt 5000.0 0.0 ExhFanSpvMaxForce Exh fan force max 4900.0 0.0 SplyFanDevAlmMaxDev Setpoint Value Max dev sply fan ExhFanDevAlmMaxDev “ Max dev exh fan AirQSpv Air quality stpt HumSpvRelSpv Humidity stpt rel HumSpvRelDz Humidity deadz rel
HumSpvRelSpvDehum Setpoint Value Limit Dehum stpt rel 100.0 0.0
HumSpvRelSpvHum “ Hum stpt rel 100.0 0.0 HumSpvAbsSpv Setpoint Value Humidity stpt abs HumSpvAbsDz “ Humidity deadz abs
HumSpvAbsSpvDehum Setpoint Value Limit Dehum stpt abs 100.0 0.0
HumSpvAbsSpvHum “ Hum stpt abs 100.0 0.0 HumMaxCtlrMaxSpv Setpoint Value Supply hum max stpt FanCmpHumSpv “ Setpoint SplyHumDevAlmMaxDev Max dev sply hum RmHumDevAlmMaxDev Max dev room hum DewpointDz Dew point dead zone TmpSpvRtTmp1 Exh air tmp stpt 1 TmpSpvSplyDiff1 Supply tmp delta 1 TmpSpvRtTmp2 Exh air tmp stpt 2 TmpSpvSplyDiff2 Supply tmp delta 2 TmpSpvCoSpv Comfort tmp stpt TmpSpvCoDz Comfort tmp deadz
TmpSpvCoSpvClg Setpoint Value Limit Comfort clg stpt 99.0 0.0
TmpSpvCoSpvHtg “ Comfort htg stpt 99.0 0.0 TmpSpvEcSpv Setpoint Value Economy tmp stpt TmpSpvEcDz “ Economy tmp deadz
TmpSpvEcSpvClg Setpoint Value Limit Economy clg stpt 99.0 0.0
TmpSpvEcSpvHtg “ Economy htg stpt 99.0 0.0 SuCmpTmpDta Setpoint Value Su comp tmp delta WiCmpTmpDta “ Wi comp tmp delta SwtchSplyCmp Su/wi supply comp CascFlowLmtMaxDevLmt Draught htg max dev CascFlowLmtMinDevLmt Draught clg max dev
TmpMinMaxCtlrMaxSpv Setpoint Value Limit Supply tmp max stpt 50.0 0.0
TmpMinMaxCtlrMinSpv “ Supply tmp min stpt 26.0 0.0 HrecPrsFrstSpv Setpoint Value Hrec frost stpt st1 HrecPrsFrstSpvStBy “ Hrec frost stpt st2 DeFrstMxSpd Max speed defrost FanCmpHtgDz Fan htg deadzone FanCmpClgDz Fan clg deadzone FanCmpTmpSpv Fan comp tmp stpt
Analog Setpoints, cont.
68 / 80
Siemens Remote OPC Server CB1P3904en Building Technologies Standard application AHU V1.x 09.07.2011
OPC tags of AHU V1.x, continued
TechnologicalName.Device.Unit. Object name Object type Object description HIL LOL ExtraSpv Setpoint Value Extra Seq setpoint HrecDampminFrshAir “ Min fresh air HrecFrstSpv Hrec frost setpoint CoolingOffTmp Clg disbl outs tmp HeatingFrstSpv Htg frost stpt HeatingFrstSpvStBy Standby stpt htg HeatingPreHtgX1 Pre htg outs tmp X1 HeatingPreHtgY1 Pre htg pos Y1 HeatingPreHtgX2 Pre htg outs tmp X2 HeatingPreHtgY2 Pre htg pos Y2 SplyTmpDevAlmMaxDev Max dev sply tmp RtRmTmpDevAlmMaxDev Max dev room tmp ExtraHtgFrstSpv Extrahtg frost stpt ExtraHtgFrstSpvStBy Standby stpt htg 2 ExtraHtgPreHtgX1 Pre htg outs tmp X1 ExtraHtgPreHtgY1 Pre htg pos Y1 ExtraHtgPreHtgX2 Pre htg outs tmp X2 ExtraHtgPreHtgY2 Pre htg pos Y2 ExtraClgOffTmp Clg2 disbl outs tmp
Analog Setpoints, cont.
69 / 80
Siemens Remote OPC Server CB1P3904en Building Technologies Standard application AHU V1.x 09.07.2011
OPC tags of AHU V1.x, continued
TechnologicalName.Device.Unit. Object name Object type Object description State texts
HtgFrstDtctr Binary Input Htg frost monitor – OK – Frost
HtgPmpAlm “ Htg pump alarm – OK – Alarm
ElHtgAlm El htg alarm – OK – Alarm
HrecFrstDtctr Hrec frost monitor – OK – Frost
HRecPmpAlm Hrec pump alarm – OK – Alarm
HRecAlm Heat recovery alarm – OK – Alarm
ClgPmpAlm Cooling pump alarm – OK – Alarm
ClgAlm Cooling DX alarm – OK – Alarm
HumPmpAlm Hum pump alarm – OK – Alarm
ExtraFrstDtctr Htg 2 frost monitor – OK – Frost
ExtraHtgPmpAlm Heating 2 pump alm – OK – Alarm
ExtraElHtgAlm El heating 2 alarm – OK – Alarm
ExtraClgPmpAlm Cooling 2 pump alm – OK – Alarm
ExtraClgAlm Cooling 2 DX alarm – OK – Alarm
FanAlm Fan alarm – OK – Alarm
SplyFanAlm Supply fan alarm – OK – Alarm
ExhFanAlm Exhaust fan alarm – OK – Alarm
FilterAlm Filter alarm – OK – Alarm
SplyFilterAlm Supply filter alarm – OK – Alarm
ExhFilterAlm Exh filter alarm – OK – Alarm
FireAlm Fire alarm – OK – Alarm
Binary Inputs
70 / 80
Siemens Remote OPC Server CB1P3904en Building Technologies Standard application AHU V1.x 09.07.2011
OPC tags of AHU V1.x, continued
TechnologicalName.Device.Unit.
Object name Object type Object description State texts
ExtCtrl1 Binary Input Ext control input 1 – Off
– On
ExtCtrl2 “ Ext control input 2 – Off – On
EmergencyStop Emergency stop – Off – On
SuWiSwtch Su/Wi input – Winter – Summer
DamperSplyFBFbVal Outs air dampr fdbk – OK – No
DamperExhFBFbVal Extr air dmper fdbk – OK – No
FireDamperFdbkOpn Fire damper opened – OK – No
FireDamperNoMove Fire damper no move – OK – Alarm
FireDamperFdbkClsd Fire damper closed – OK – No
SplyFanFBFbVal Supply fan fdbk – OK – Alarm
ExhFanFBFbVal Exhaust fan fdbk – OK – Alarm
HumidityCtrlCmdFBFbVal Humidifier fdbk – OK – No Fdbk
HumidityCtrlPmpCmdFBFbVal Hum pump fdbk – OK – No Fdbk
HrecPmpCmdFBFbVal Hrec pump fdbk – OK – No Fdbk
CoolingPmpCmdFBFbVal Cooling pump fdbk – OK – No Fdbk
CoolingFBFbVal Cooling DX fdbk – OK – No Fdbk
HeatingPmpCmdFBFbVal Htg pump fdbk – OK – Alarm
ExtraHtgPmpCmdFBFbVal Heating 2 pump fdbk – OK – No Fdbk
ExtraClgPmpCmdFBFbVal Cooling 2 pump fdbk – OK – No Fdbk
ExtraClgFBFbVal Cooling 2 DX fdbk – OK – Alarm
AuxAlm Aux alarm – Passive – Active
AuxInp Auxiliary input – Off – On
Binary Inputs, cont.
71 / 80
Siemens Remote OPC Server CB1P3904en Building Technologies Standard application AHU V1.x 09.07.2011
OPC tags of AHU V1.x, continued
TechnologicalName.Device.Unit. Object name Object type Object description State texts
DamperSplyOnOff Binary Output Outs air damper cmd – Off
– On
DamperExhOnOff “ Extr air damper cmd – Off – On
FireDamperCmd Fire damper cmd – Off – On
HumidityCtrlCmdOnOff Humidifier cmd – Off – On
HumidityCtrlPmpCmdOnOff Humidifier pump cmd – Off – On
HrecPmpCmdOnOff Hrec (pump) cmd – Off – On
CoolingPmpCmdOnOff Cooling pump cmd – Off – On
HeatingPmpCmdOnOff Htg pump cmd – Off – On
ExtraHtgPmpCmdOnOff Heating 2 pump cmd – Off – On
ExtraClgPmpCmdOnOff Cooling 2 pump cmd – Off – On
AuxTspOutput Aux TSP output – Off – On
AuxOpModeInd Aux op mode output – Off – On
HrecOnOff Hrec puls cmd – Off – On
TechnologicalName.Device.Unit. Object name Object type Object description State texts
SplyTmpFireAlm Binary Value Supply tmp fire alm – OK – Alarm
RtTmpFireAlm “ Exh tmp fire alarm – OK – Alarm
SplyFanDevAlmAlm Sply fan deviation – Passive – Active
ExhFanDevAlmAlm Exh fan deviation – Passive – Active
FanOpHrsAlm Fan op hours alarm – Passive – Active
SplyHumDevAlmAlm Sply hum deviation – Passive – Active
RmHumDevAlmAlm Room hum deviation – Passive – Active
SplyTmpDevAlmAlm Sply tmp deviation – Passive – Active
RtRmTmpDevAlmAlm Room tmp deviation – Passive – Active
MBCommAlm Modbus comm alarm – OK – Alarm
PBCommAlm Processbus comm alarm – OK – Alarm
Binary Outputs
Binary Values
72 / 80
Siemens Remote OPC Server CB1P3904en Building Technologies Standard application AHU V1.x 09.07.2011
OPC tags of AHU V1.x, continued
TechnologicalName.Device.Unit. Object name Object type Object description State texts
SplyFanCmdSt Multistate Output Supply fan cmd
– Off – Stage1 – Stage2 – Stage3
ExhFanCmdSt “ Exhaust fan cmd
– Off – Stage1 – Stage2 – Stage3
ElectricalHtgCmdStSt El heating cmd
– Off – Stage1 – Stage2 – Stage3
CoolingCmdDxSt Cooling DX cmd
– Off – Stage1 – Stage2 – Stage3
ExtraElHtgCmdStSt El heating 2 cmd
– Off – Stage1 – Stage2 – Stage3
ExtraClgCmdDxSt Cooling 2 DX cmd
– Off – Stage1 – Stage2 – Stage3
Multistate Outputs
73 / 80
Siemens Remote OPC Server CB1P3904en Building Technologies Standard application AHU V1.x 09.07.2011
OPC tags of AHU V1.x, continued
TechnologicalName.Device.Unit. Object name Object type Object description State texts
TimeSchedSt Setpoint Multistate TSP steps
– Off – Stage1 – Stage2 – Stage3
TimeSchedStTmp “ TSP steps/tmp
– Off – Eco St1 – Comf St1 – Eco St2 – Comf St2 – Eco St3 – Comf St3
ExtControlActMode Display Multistate Act Opmode ext ctrl
– Auto – Off – Stage1 – Stage2 – Stage3
ActOpMode “ Act operating mode
– Off – On/Comfort – Economy – Na – Osstp – NightClg – UnOcc – NightKick – FireDamper – Fire – Stop – OverRun – StartUp
FireDamperState Fire damper state
– NotDefined – Closed – Move – Opened
FireDamperOperation Fire damper mode
– NotDefined – OK – Test – Alarm
ActFanStep Act fan step
– Off – Stage1 – Stage2 – Stage3
ActCtrlModeHum Act ctrl mode hum – Room – Supply
ActCtrlMode Act ctrl mode tmp – Room – Return – Supply
MECHActv Hrec clg recovery – Passive – Active
HeatingPreHtgactv Pre htg state – Passive – Active
ExtraHtgPreHtgactv Pre htg 2 state – Passive – Active
TimeSchedAux Setpoint Multistate Aux TSP output – Off
– On
Multistate Values
74 / 80
Siemens Remote OPC Server CB1P3904en Building Technologies Standard application AHU V1.x 09.07.2011
OPC tags of AHU V1.x, continued
TechnologicalName.Device.Unit. Object name Object type Object description State texts
OpModeTspCopyUnitPls Setpoint Multistate Copy schedule – MondayTo
– Tu-Fr
ExtControlStep “ Ext ctrl fan step
– Auto – Off – Stage1 – Stage2 – Stage3
OpModeAutoManStSwtch Op mode man steps
– Auto – Off – Stage1 – Stage2 – Stage3
OpModeAutoManStTmpSwtch Op mode man st/tmp
– Auto – Off – Eco St1 – Comf St1 – Eco St2 – Comf St2 – Eco St3 – Comf St3
OpModeBmsTimeStSwtch BMS TSP steps
– Auto – Off – Stage1 – Stage2 – Stage3
OpModeBmsTimeStTmpSwtch BMS TSP steps/tmp
– Auto – Off – Eco St1 – Comf St1 – Eco St2 – Comf St2 – Eco St3 – Comf St3
FireDamperTestStrtHMIPls Fire damper test – Passive – Active
AuxiliaryTspCopyAuxPls Copy schedule – MondayTo – Tu-Fr
AuxiliaryBmsTimeAuxSwtch Aux BMS TSP output – Auto – Off – On
Multistate Setpoints
75 / 80
Siemens Remote OPC Server CB1P3904en Building Technologies Standard application AHU V1.x 09.07.2011
OPC tags of AHU V1.x, continued
Not supported at moment. TechnologicalName.Device.Unit. Object name Object type Object description CalendarEx Calendar Calendar exception CalendarOff “ Calendar fix off CalendarAux Calendar aux
Not supported at moment. TechnologicalName.Device.Unit. Object name Object type Object description State texts
ScheduleSt Scheduler Schedule steps
– Off – St1 – St2 – St3
ScheduleStTmp “ Schedule steps/tmp
– Off – Ec1 – Co1 – Ec2 – Co2 – Ec3 – Co3
ScheduleAux Schedule aux output – Off – On
Not supported at moment. TechnologicalName.Device.Unit.ScheduleXXX Object name Object type Object description State texts
Monday…Sunday, Exception Scheduler Day Day schedule, Time and
Value/Stage
Stages as above + Time entries
Calendar
Schedule
Schedule Day
76 / 80
Siemens Remote OPC Server CB1P3904en Building Technologies Standard application AHU V1.x 09.07.2011
OPC tags of AHU V1.x, continued
TechnologicalName.Device.Unit. Object name Object type Object description HIL LOL − CoolingCtlr Loop
Controller − Cooling
− HrecCtlr “ − Heat recovery − HrecFrstCtlr − Heat recovery frost
protection
− HrecPrsFrstCtlr − Heat recovery frost pressure
− HrecDampCtlr − Heat recovery damper − HeatingCtlr − Heating − HeatingFrstCtlr − Heating frost protection − ElectricalHtgCtlr − Electrical heating − ExtraClgCtlr − Cooling 2 − ExtraHtgCtlr − Heating 2 − ExtraHtgFrstCtlr − Heating 2 frost protection − ExtraElHtgCtlr − Electrical Heating 2 − TmpMinMaxCtlrMinCtlr − Min supply temperature − TmpMinMaxCtlrMaxCtlr − Max supply temperature − FanClgCtlr − Fan cooling − FanHtgCtlr − Fan heating − FanCmpTmpCtlr − Fan compensation
temperature
− FanCmpHumCtlr − Fan compensation humidity
− SplyFanVarCtlr − Supply fan − ExhFanVarCtlr − Exhaust fan − HumidityCtrlCtlr − Humidification − HumMaxCtlrMaxCtlr − Max supply humidity − DeHumidityCtlr − Dehumidification − AirQCmpCtlr − Air quality − TmpCascCtlr Cascade
Controller − Cascade controller
temperature
− HumCascCtlr “ − Cascade controller humidity
Controllers
77 / 80
Siemens Remote OPC Server CB1P3904en Building Technologies Standard application AHU V1.x 09.07.2011
OPC tags of AHU V1.x, continued
TechnologicalName.Device.Global. Object name Object type Object description State texts SuWiSwtchCheckOutTmpDampd Display Value Outs air tmp damped
SuWiSwtchCheckState Display Multistate Su/Wi mode – Winter
– Summer
CommTestEn Setpoint Multistate Enable comm test – No
– Yes
CommTest Binary Value Communication test – Off – On
ManualMode Binary Value Manual mode – Auto – Manual
TechnologicalName.Device.Alarms. Object name Object type Object description State texts
AlmCl0 Display Multistate Danger alarm (A) – Normal
– Alarm
AlmCl1 “ Critical alarm (A) – Normal – Alarm
AlmCl2 Low alarm (B) – Normal – Alarm
AlmCl3 Warning alarm (C) – Normal – Alarm
AlmOutHigh Binary Output Alarm output 1 – Normal – Alarm
AlmOutLow “ Alarm output 2 – Normal – Alarm
TechnologicalName.Device.Comm. Object name Object type Object description State texts
CG_EM24_1ResetParPls Setpoint Multistate Energy reset part – Passive
– Active CG_EM24_1ActPower Display Value Energy act power CG_EM24_1AvePower “ Energy ave power CG_EM24_1TotEnergy Energy total CG_EM24_1ParEnergy Energy partial CG_EM24_1OpHours Energy ophours
RoomUnitsOccTm Setpoint Multistate
Precence time for roomunits
RoomUnitsActSpvShift Display Value Actual setpoint shift for roomunits
RoomUnitsActRmUMode Display Multistate
Actual operationmode for roomunits
– Auto – Comfort – Standby – Economy – Off
Global functions
General alarms
Communication
78 / 80
Siemens Remote OPC Server CB1P3904en Building Technologies Standard application AHU V1.x 09.07.2011
Blank page
79 / 80
Siemens Remote OPC Server CB1P3904en Building Technologies Index 09.07.2011
Index
A Abbreviations .......................................................... 6 AWM setup ........................................................... 47
B Before you start ...................................................... 5
C Cache files generator............................................ 23 Computer to modem connections
General.............................................................. 53 RAS entry for incoming connections................. 54 RAS entry for outgoing connections ................. 58
Configuration file................................................... 20 Configuration parameters ..................................... 21 Configure controller .............................................. 19 Creating cache files .............................................. 23
D Document conventions ........................................... 6 Document use, Request to the reader.................... 9 Document validity ................................................... 5
F Functional design.................................................. 12
I Installation of the RemoteOPC Server ................. 15
L Licensing of RemoteOPC ..................................... 17
O OPC client view .................................................... 37 OPC networks........................................................11 OPC protocol .........................................................11 OPC tag selection................................................. 37 OPC tags
Analog Inputs .................................................... 65 Analog Outputs.................................................. 65 Analog Setpoints ............................................... 66 Analog Values ................................................... 66 Binary Inputs ..................................................... 69 Binary Outputs................................................... 71 Binary Values .................................................... 71 Calendar............................................................ 75 Communication ................................................. 77
Controllers..........................................................76 Device ................................................................64 General alarms ..................................................77 Global functions .................................................77 Multistate Outputs ..............................................72 Multistate Setpoints............................................74 Multistate Values................................................73 Schedule ............................................................75 Schedule Day.....................................................75 System objects...................................................64 Technological name ...........................................64
OPC tags of AHU V1.x ..........................................64 Optimizing the client ..............................................31 Optimizing the RemoteOPC Server ......................27
Q Quality assurance....................................................8 Quantity structure ..................................................27
R RAS dial-up creation .............................................49 RAS incoming calls ...............................................47 RAS user creation .................................................48 Reference documents .............................................6 Registry entries .....................................................32 Remote OPC over modem....................................14 Remote OPC via Ethernet LAN.............................13 Running the RemoteOPC Server..........................33
S Safety notes. ...........................................................7 SAPHIR RCC setup
RAS parameters for incoming call .....................45 RAS parameters for outgoing call......................44 Start page...........................................................43 Trigger an outgoing calll.....................................46
Searching and selecting........................................38 Standard application AHU V1.x .............................63 Symbols in document ..............................................6
T Tools ......................................................................11 Trademarks and copyrights.....................................8 Troubleshooting.....................................................35
V View RemoteOPC.log file......................................34
80 / 80
Siemens Remote OPC Server CB1P3904en Building Technologies 09.07.2011
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
© 2009 Siemens Switzerland Ltd. Subject to change