Installation Guide DECS Contents

Transcription

1 Installation Guide DECS Contents 1.0 Contents Introduction DECS Hard- and software requirements, server side DECS 2.0 server Data communication interface on DECS 2.0 server Hard- and software requirements, client side DECS 2.0 client Installation and setup Atvise installation OPC UA server installation Auto start and bat file Communication setup Browser setup General settings Billing Billing methods Standard Tannheim Sono Solarcomplex Danfoss District Energy VI.HX.C2.02 DEN-SMT/DK 1

2 2.0 Introduction 2.1 DECS 2.0 The Danfoss Energy Control System (DECS) is a web-based SCADA software solution (Supervisory Control And Data Acquisition) for district heating systems. This SCADA solution is typically installed locally at the heating utility and will automatically configure its user interface and functionality to support the application on the controller (for example Danfoss ECL Comfort 310). The user of the DECS 2.0 system is able to remote control and monitor the parameters settings in the controllers and also monitor actual, reference and historical values of sensors and meters connected to the controller. Danfoss ECL Comfort 310, OPR0010 and OPR0020 controllers are supported by the auto-configuration features of DECS 2.0, but other district heating controllers, e.g. the ECL Apex 20 controller can also be supported by manually adding graphics and programs into DECS 2.0. This installation guide is intended for installers who are responsible for the installation of the DECS 2.0 software at district heating utilities, in larger plants or at owners/operators of stand-alone district heating plants. Data is constantly exchanged between controllers and the DECS 2.0 server, and configuration reports and alarm reports are generated automatically. In addition the heating station and substation installations can be controlled and monitored from everywhere, as the server provides an intuitive user interface that is accessible from any standard browser on a PC, laptop or smartphone connected to the internet. The present installation guide contains detailed explanation on how to install the DECS 2.0 system as well as requirements to hard- and software. If you need further information on keys to be used together with the DECS 2.0 system, please see List of application keys supported by DECS 2.0. Go to In the Products menu select SCADA Solutions > Documentation > SCADA Solutions > Data sheet. Additional technical literature related to the DECS 2.0 Danfoss Energy Control system: * Data sheet on DECS 2.0 VD.HX.A * Quick guide for end users on DECS 2.0 VI.HX.B * User guide for operators on DECS 2.0 VI.HX.A For further information on supported application keys please visit In the Products menu select SCADA Solutions > Documentation > SCADA Solutions > Instruction. 3.0 Hard- and software requirements, server side 3.1 DECS 2.0 server Operating system Microsoft Windows XP (SP3 with latest updates installed) (32-bit) Microsoft Windows 7 (SP1 with latest updates installed) (32-bit) CPU Intel or AMD processor (>= 1,6 GHz) RAM Minimum: 4 GB RAM Free disc space 500 GB (depending on the number of controllers connected to DECS 2.0 and archieving frequency) Video A windows certified graphics card and driver. Minimum resolution is 1280*1024 pixel 3 rd party software Atvise server V (Certec) Loytec network interface software 4.1.x for LON networks Microsoft.NET Framework 3.5 and compatible versions Web browser SVG capable internet browser: Mozilla Firefox Internet Explorer Google Chrome Web browser must comply with requirements of Atvise SCADA Client software. For details about specific browser versions compatible with Atvise please visit compatibilitylist Backup recommendations RAID Level 1 or RAID Level 5 2 DEN-SMT/DK VI.HX.C2.02 Danfoss District Energy

3 3.2 Data communication interface on DECS 2.0 server Modbus TCP/IP LON bus RS485 port compatible with MOXA UPort 1130 MOXA NPort 5150 Phoenix Contact FL COM SERVER RS485 Ethernet compatible interface Loytec LON NIC (LonWorks/EIA 709) using PCI, Parallel or USB for LON networks 4.0 Hard- and software requirements, client side 4.1 DECS 2.0 client Operating system Microsoft Windows XP (SP3 with latest updates installed) Microsoft Windows 7 (SP1 with latest updates installed) CPU Intel or AMD processor (>= 1,6 GHz) RAM Minimum: 2 GB RAM Free disk space 1 GB Video A windows certified graphics card and driver. Minimum resolution is 1280*1024 pixel Web browser SVG capable internet browser: Mozilla Firefox Internet Explorer Google Chrome Web browser must comply with requirements of Atvise SCADA Client software. For details about specific browser versions compatible with Atvise please visit Danfoss District Energy VI.HX.C2.02 DEN-SMT/DK 3

4 5.0 Installation and setup 5.1 Atvise installation To install the Atvise system, execute the installer atvise win32.exe. In the installer welcome screen, click Next. The wizard will guide you through the necessary steps. Fig. 1: Installer welcome screen Choose the destination folder for the Atvise system and click Next. Fig. 2: Destination folder 4 DEN-SMT/DK VI.HX.C2.02 Danfoss District Energy

5 When the installation is done, click Finish (see figure 3). Fig. 3: Atvise setup completed Upon installation, the Proect Console is displayed. Before the Atvise system can be used a license must be entered. Enter the License dialog (see figure 5) by clicking the License menu item. Copy and paste the license code supplied by your system provider and click OK. Now stop the Atvise server (see figure 4) by clicking the Stop button, wait for the start button to turn green. The supplied Nodes.db can now be copied to the root of the Atvise installation directory (see figure 2). Afterwards start the server from the Proect Console (see figure 4). Wait for the stop button to turn red. The DECS 2.0 system can now be entered by clicking the Browser button in the Proect Console. Fig. 4: Proect console The context menu of the Atvise program in the notification area. If the windows security settings request administrator privileges, then the context menu will ask you to click the menu item Run As Administrator. Fig. 5: Context menu Danfoss District Energy VI.HX.C2.02 DEN-SMT/DK 5

6 5.2 OPC UA server installation To install the OPC UA server, simply copy and paste the supplied OPC-Server and Config folder to a desired destination folder. Fig. 6: OPC server folder 5.3 Auto start and bat file To add automatically startup of the DECS system upon Windows reboot, a bat file can be added to the start / startup folder of the Windows system. To make the bat file or to modify, start MS. Notepad and write in the necessary lines to start up the system with your configuration. Save the file in your desired destination with File->SAVE AS and change the save as type: to all files (*.*) and input the file name with the extension bat. Fig. 7: How to make the bat file A network driver is necessary to make it possible for the OPC server to communicate with the controllers. An installation can contain a mix of the following types of network, if so then a driver for each type should be added to the bat file. If the controller network is of the type TCP, then the following line should be part of the bat file: (In the following example the desired destination folder is: C:\DECS\2_1_18\) start /b Driver C:\DECS\2_1_18\OPC-Server\Driver\CommDrvTcp.exe If the controller network is of the type LON, then the following line should be part of the bat file: (In the following example the desired destination folder is: C:\DECS\2_1_18\) start /b Driver C:\DECS\2_1_18\OPC-Server\Driver\CommDrv- Lon.exe If the controller network is of the type Modbus, then the following line should be part of the bat file: (In the following example the desired destination folder is: C:\DECS\2_1_18\) start /b Driver C:\DECS\2_1_18\OPC-Server\Driver\CommDrv- Modbus.exe 6 DEN-SMT/DK VI.HX.C2.02 Danfoss District Energy

7 Application example showing a locally centralized communication system. o m p o m q r k l o o m m n Private house k Communication server + OPC l Internet m Fieldbus: LON, Modbus, Ethernet communication n DECS 2.0 client (external service provider/district heating end users) o ECL Comfort 310 controller p District heating utility q SCADA server *) r DESC 2.0 client (central administration) *) The SCADA server will automatically start up with Windows. Note: To deactivate lines, place REM in front of the lines. Fig. 8: Automatic startup of OPC server Danfoss District Energy VI.HX.C2.02 DEN-SMT/DK 7

8 Application example showing the DECS 2.0 system distributed in several sub-systems. o m p o m r s k l q l o m k n o m Private house k Communication server l Internet m Fieldbus: LON, Modbus, Ethernet communication n DECS 2.0 client (external service provider/district heating end users) o ECL Comfort 310 controller p District heating utility q OPC server r SCADA server *) s DESC 2.0 client (central administration) *) The SCADA server will automatically start up with Windows. Note: To deactivate lines, place REM in front of the lines. Fig. 9: Automatic startup of Communication server Fig. 10: Automatic startup of OPC server 8 DEN-SMT/DK VI.HX.C2.02 Danfoss District Energy

9 Application example showing all sub-systems installed on one localized server at the district heating utility. k l n p m o q Private house k District heating utility l Modbus-RS485 network m Internet n Communication server, SCADA, OPC o DECS 2.0 client (external service provider/district heating end users) p DESC 2.0 client (central administration) q ECL Comfort 310 controller Note: To deactivate lines, place REM in front of the lines. Fig. 11: Automatic startup of Communication server Fig. 12: Automatic startup of OPC server Danfoss District Energy VI.HX.C2.02 DEN-SMT/DK 9

10 5.4 Communication setup The communication drivers for the DECS system can be found under the OPC Server / Driver folder. If the connected controllers are using LON, then the CommDrv- Lon.exe must be started and the Loytec NIC Driver must be installed and setup (see figure 13). CommDrvLon.ini must be modified in regard to the LON-Domain and the HostAddress, if the host address is not the localhost. We recommend the use of PCI LON NIC. Fig. 13: Loytec NIC driver setup The CommDrvLon.ini file must be modified, so that the LONPort is pointing to the right com port. The HostAddress must be modified, if the localhost is not used (see figure 14). When using the LON communication driver, please make sure that the lt_proxy.dll is compatibel with the Loytec NIC driver. The version can be verified in the first lines of the LOG file after starting the driver. You will find the LOG file in the desired destination folder under OPC\driver\log. It should read: LON-CheckNic: Proxy DLL , NIC Software , DLLs OK Note that the version number can vary! (see figure 15). In doubt please overwrite the actual lt_proxy.dll with the file from the Loytec NIC install directory. The file location is normally: C:\ Program Files\LOYTEC\NIC\Windows\OrionStack\dll\ Fig. 14: CommDrvLon.ini setup Fig. 15: LonDebugLOG 10 DEN-SMT/DK VI.HX.C2.02 Danfoss District Energy

11 If the controllers are using Modbus, then the CommDrvModbus. exe must be started. The CommDrvModbus.ini file must be modified, so the Modbus- Port is pointing to the right com port. The HostAddress must be modified, if the localhost is not used (see figure 16). Fig. 16: CommDrvModbus.ini setup Port configuration is done with comredir_ exe and the setup can look like the following (see figure 17). Fig. 17: Comredirector setup Danfoss District Energy VI.HX.C2.02 DEN-SMT/DK 11

12 If the connected controllers are using TCP/IP, then the Comm- DrvTcp.exe must be started. The CommDrvTcp.ini must be modified if the HostAddress is not the localhost (see figure 18). Fig. 18: CommDrvTcp.ini setup The communication drivers are located under the folder OPC- Server\Driver. Fig. 19: Location of the communication drivers 12 DEN-SMT/DK VI.HX.C2.02 Danfoss District Energy

13 5.5 Browser setup To avoid the browser in updating to a new, not supported version, remove the automatic check for update. Please consult the user guide of your browser. To permit the browser in showing old data upon an update, deactivate the cache management. Please consult the user guide of your browser. 5.6 General settings Before changes to General settings you need to login. Please see the section on login in User Guide VI.HX.A1. In the General settings page you can find the settings for the placing of files. If desired, the field Export Path controls where the csv output from Reports are stored. If customer folders are created, the field Customer Folder controls their placing. The path must be terminated with single backslash ( \ ). Fig. 20: General settings page Danfoss District Energy VI.HX.C2.02 DEN-SMT/DK 13

14 5.7 Billing There are four different billing types: Kind 0 Kind 1 Kind 2 Kind 3 Standard Tannheim Sono Solarcomplex Each kind has different formatting and limitations. The billing kind is chosen by setting the type number as the value in the system parameters Billing Kind1. Fig. 21: Billing Kind 1 To set the destination folder for the billing data, set the value of the system parameters Billing Path. The path must be written with double backslash ( \\ ). The path must be terminated with double backslash ( \\ ). Fig. 22: Billing Path 14 DEN-SMT/DK VI.HX.C2.02 Danfoss District Energy

15 5.8 Billing methods Billing method 0: Standard File name: ZStand_DD_MM_YY ZStich_DD_MM_YY Format: ZStand_DD_MM_YY DD.MM.YYY For each controller: R + ControllerID + : Max. 10 (OPR20) or 5 (ECL310 + OPR10) meter data amount of heat + read-out time ZStich_DD_MM_YY DD.MM.YYY For each controller: R + ControllerID + : Max. 10 (OPR20) or 5 (ECL310 + OPR10) meter data amount of heat, reading + read-out time Billing method 1: Tannheim File name: Billing_DD_MM_YY.csv Format: Obect number _ Meter number _ Calculator unit _ Date in the format: DD.MM.YY _ Volume _ Heat amount _ Date in the format: DD.MM.YY _ 1 _ Date/time of the read-out is in the format: DD.MM.YYY HH:MM:SS The format is split up with semicolon and all lines are terminated with a new line. Danfoss District Energy VI.HX.C2.02 DEN-SMT/DK 15

16 5.8 Billing methods (continued) Billing method 2: Sono File name: Billing_Tarif_DD_MM_YY.csv Format: _ ControllerID _ Number for each MBusUnit (from 1 10, if available) _ Amount of heat _ Tariff energy 1 _ Tariff energy 2 _ Tariff energy 3 (=amount of heat Tariff energy 1 Tariff energy 2) _ Date/time from read out in the format: DD.MM.YYY HH:MM:SS The format is split up with semicolon and all lines are terminated with a new line. Billing method 3: Solarcomplex File name: Billing_YYYYMMDD_HHMM.txt Format: _ Billing: _ Meter number (Fixed length 80 Byte; if not used, filled with ) _ Additional name (Fixed length 16 Byte; if not used, filled with ) _ EdisKZ (Fixed length 30 Byte; if not used, filled with ) _ Amount of heat (Fixed length 13 Byte; if not used, filled with ) _ Read-out date in the format: YYYYMMDD (Fixed length 8 Byte) _ Read-out indicator (Fixed length 5 Byte; if not used, filled with ) _ Settlement date in the format: YYYYMMMDD (Fixed length 8 Byte) 16 DEN-SMT/DK VI.HX.C2.02 Danfoss District Energy

17 Danfoss District Energy VI.HX.C2.02 DEN-SMT/DK 17

18 18 DEN-SMT/DK VI.HX.C2.02 Danfoss District Energy

19 Danfoss District Energy VI.HX.C2.02 DEN-SMT/DK 19

20 *087H9114* *VIHXC202* Produced by Danfoss A/S 07/2013