netscada devices with atvise builder - hilscher.com · user manual netscada devices with atvise...

Table of contents 2/175

Table of contents1 Introduction............................................................................................................................... 51.1 About this document......................................................................................................... 5

1.1.1 Description of the contents ................................................................................ 51.1.2 List of revisions.................................................................................................. 51.1.3 Conventions in this manual ............................................................................... 61.1.4 Reference on hardware, firmware and software................................................ 7

1.2 Scope of delivery and contents of the product DVD......................................................... 71.3 Documentation overview .................................................................................................. 81.4 Internet security considerations........................................................................................ 9

1.4.1 HTTP server security considerations................................................................. 91.4.2 FTP server security considerations ................................................................... 9

1.5 Legal notes..................................................................................................................... 101.5.1 Copyright ......................................................................................................... 101.5.2 Important notes................................................................................................ 101.5.3 Exclusion of liability ......................................................................................... 111.5.4 Warranty .......................................................................................................... 111.5.5 Export regulations............................................................................................ 121.5.6 Trademarks ..................................................................................................... 12

1.6 Licenses ......................................................................................................................... 12

2 Safety....................................................................................................................................... 132.1 General safety notes ...................................................................................................... 132.2 Intended use................................................................................................................... 132.3 Personnel qualification .................................................................................................. 132.4 References safety .......................................................................................................... 142.5 Property damage messages .......................................................................................... 14

2.5.1 Supply voltage ................................................................................................. 142.5.2 Electrostatic discharge .................................................................................... 142.5.3 Possible device damage by compensating current at Modbus RTU interface

(NSCDT52RS/ATVISE/MBR)........................................................................ 152.6 Labeling of safety messages.......................................................................................... 15

3 Description.............................................................................................................................. 16

4 Requirements.......................................................................................................................... 194.1 Requirements for operating the netSCADA devices ...................................................... 194.2 System requirements for the configuration PC............................................................... 194.3 System requirements of atvise builder ........................................................................... 19

4.3.1 Supported web browser .................................................................................. 194.3.2 Required disk space ........................................................................................ 204.3.3 Internet connection for installing atvise software ............................................ 20

5 Device drawings and connectors ......................................................................................... 215.1 Dimensional drawings .................................................................................................... 215.2 Connectors and LEDs .................................................................................................... 22

5.2.1 Overview connectors and LEDs NL 50NMPIATVISE ................................... 225.2.2 Overview connectors and LEDs NSCDT52RS/ATVISE/MBR....................... 235.2.3 Overview connectors and LEDs NSCDT52EN ............................................. 245.2.4 Ethernet interface ............................................................................................ 25

netSCADA devices with atvise builder | User ManualDOC120103UM06EN | Revision 6 | English | 201601 | Released | Public

© Hilscher 2010 – 2016


5.2.5 PROFIBUS interface (NL 50NMPIATVISE) .................................................. 265.2.6 Modbus RTU interface (NSCDT52RS/ATVISE/MBR)................................... 275.2.7 Voltage supply X1............................................................................................ 28

5.3 Galvanic isolation schematic diagrams ......................................................................... 29

6 Mounting ................................................................................................................................. 326.1 Mounting NL 50NMPIATVISE...................................................................................... 326.2 Mounting NSCDT52 ...................................................................................................... 33

7 Installing the software ........................................................................................................... 35

8 Creating visualization with the atvise builder...................................................................... 388.1 Overview ........................................................................................................................ 388.2 Starting the atvise builder............................................................................................... 398.3 Assigning temporary IP address .................................................................................... 438.4 Creating projects for NL 50NMPIATVISE and NSCDT52EN/ATVISE/PN................. 46

8.4.1 Overview.......................................................................................................... 468.4.2 Using existing STEP 7 project file ................................................................... 468.4.3 Creating project for NL 50NMPIATVISE (netLINK SCADA for PROFIBUS

MPI) ................................................................................................................ 548.4.4 Creating project for NSCDT52EN/ATVISE/PN (netSCADA for PROFINET) 63

8.5 Creating project for NSCDT52EN/ATVISE/OMB (netSCADA for Modbus TCP) ........ 718.5.1 Overview of the necessary steps..................................................................... 718.5.2 Configuring netSCADA device ........................................................................ 728.5.3 Configuring Modbus TCP parameters ............................................................ 758.5.4 Configuring signals in the Signal Editor .......................................................... 77

8.6 Creating project for NSCDT52RS/ATVISE/MBR (netSCADA for Modbus RTU) ........ 838.6.1 Overview of the necessary steps..................................................................... 838.6.2 Configuring netSCADA device ........................................................................ 848.6.3 Configuring Modbus RTU parameters ............................................................ 878.6.4 Configuring signals in the Signal Editor .......................................................... 89

8.7 Importing Modbus signals from “symbol file” (CSV text file) .......................................... 958.7.1 Overview.......................................................................................................... 958.7.2 Structure of CSV symbol file............................................................................ 958.7.3 Importing symbol file...................................................................................... 103

8.8 Creating the visualization (designing the displays) ...................................................... 1088.8.1 Overview........................................................................................................ 1088.8.2 Default displays ............................................................................................. 1088.8.3 Creating displays .......................................................................................... 1098.8.4 GUI of the display editor ................................................................................ 1118.8.5 Adding display elements and assigning signals ............................................ 112

8.9 Alarms and trending ..................................................................................................... 1158.9.1 Configuring alarms ........................................................................................ 1158.9.2 Configuring trending ...................................................................................... 118

8.10 Generating visualization and transferring it into netSCADA device ............................. 1218.11 Displaying visualization in browser............................................................................... 123

9 Using the Web Configuration Interface of the netSCADA devices.................................. 1259.1 Overview ...................................................................................................................... 1259.2 Accessing the Web Configuration Interface ................................................................. 127

9.2.1 Prerequisites.................................................................................................. 127


© Hilscher 2010 – 2016


9.2.2 User authentication........................................................................................ 1279.2.3 Connecting to Web Configuration Interface................................................... 128

9.3 Start page (Device Information) ................................................................................... 1299.4 Configuring permanent IP address (Network Settings) ................................................ 1309.5 Updating firmware ....................................................................................................... 1329.6 Resetting device .......................................................................................................... 1359.7 Configuring the system time ........................................................................................ 1369.8 Trend recording ............................................................................................................ 1399.9 Erasing visualization project (application data) ........................................................... 1429.10 Factory restore ............................................................................................................. 143

10 Firmware recovery of NSCDT52 via USB .......................................................................... 145

11 General troubleshooting...................................................................................................... 150

12 LED descriptions .................................................................................................................. 15112.1 LEDs NL 50NMPIATVISE.......................................................................................... 15112.2 LEDs NSCDT52RS/ATVISE/MBR ............................................................................. 15212.3 LEDs NSCDT52EN/ATVISE/PN ................................................................................ 15412.4 LEDs NSCDT52EN/ATVISE/OMB............................................................................. 156

13 Technical data....................................................................................................................... 15813.1 NL 50NMPIATVISE.................................................................................................... 15813.2 NSCDT52RS/ATVISE/MBR ...................................................................................... 16013.3 NSCDT52EN/ATVISE/PN.......................................................................................... 16213.4 NSCDT52EN/ATVISE/OMB....................................................................................... 16413.5 Integrated WebServer .................................................................................................. 16613.6 Real time clock ............................................................................................................. 16613.7 Supported web browser ............................................................................................... 166

14 Disposal of waste electronic equipment ............................................................................ 167

15 Glossary ................................................................................................................................ 168

List of figures........................................................................................................................ 170

List of tables ......................................................................................................................... 173

Contacts ................................................................................................................................ 175


© Hilscher 2010 – 2016

Introduction 5/175

1 Introduction

1.1 About this document

1.1.1 Description of the contentsThis user manual describes installation, operation, configuration and thehardware of the Hilscher netSCADA devices

NL 50NMPIATVISE (netLink SCADA for PROFIBUS/MPI)

NSCDT52EN/ATVISE/PN (netSCADA for PROFINET/RFC1006)

NSCDT52EN/ATVISE/OMB (netSCADA for Modbus TCP/IP)

NSCDT52EN/ATVISE/MBR (netSCADA for Modbus RTU)

with integrated atvise web visualization. It contains information oncommissioning and using the netSCADA devices for visualizing data from acommunication network. It also describes how to create visualizationprojects for the netSCADA devices with the atvise builder software and howto administer the devices via integrated web configuration interface.

1.1.2 List of revisionsIndex Date Revision1 20120606 Document created

Description for atvise version 2.1.182 20130621 Description updated for atvise version 2.2.33 20131111 Description updated for atvise version 2.5

Section Reference to hardware, firmware and softwareupdatedSection Contents of the product DVD updatedSection System requirements of the configuration PC addedSection Software installation updated

4 20140612 New netSCADA device NSCDT52RS/ATVISE/MBR addedDocument completely revised

5 20150225 Title of document changed from “netSCADA with atvisebuilder” to “netSCADA devices with atvise builder”New netSCADA devices NSCDT52EN/ATVISE/PN andNSCDT52EN/ATVISE/OMB addedDocument completely revised

6 20160113 Section Importing Modbus signals from “symbol file” (CSVtext file) added

Table 1: List of revisions


© Hilscher 2010 – 2016

Introduction 6/175

1.1.3 Conventions in this manualNotes, instructions and results of operating steps are marked as follows:

Notes

Important:<important note you must follow to avoid malfunction>

Note:<general note>

<note where to find further information>

Instructions1. Operational stepØ Instruction

2. Operational stepØ Instruction

Results

Intermediate result

Final result

For a description of the labeling of Safety Messages, see section Labelingof safety messages [ page 15].


© Hilscher 2010 – 2016

Introduction 7/175

1.1.4 Reference on hardware, firmware and software

Reference on hardware and firmwareDevice Article name Part number Hardware

revisionFirmware Firmware

versionnetLINK SCADA NL 50NMPIATVISE 1701.431 1 LN303100.nxf 1.3.x.xnetSCADA Modbus NSCDT52RS/ATVISE/

MBR1880.100 2 T07100R0.nxf 1.1.x.x

netSCADA PROFINET NSCDT52EN/ATVISE/PN 1880.110/ATVISE/PN 2 T07100M0.nxf 1.1.x.xnetSCADA ModbusTCP

NSCDT52EN/ATVISE/OMB

1880.110/ATVISE/OMB

2 T07100L0.nxf 1.1.x.x

Table 2: Reference on hardware and firmware

Reference on softwareSoftware Versionatvise builder 2.5.xHilscher Symbolizer 1.0003.xHilscher atvise Plugins 2.5.xTable 3: Reference on software

1.2 Scope of delivery and contents of the product DVD

Scope of delivery

The following items are included in the delivery of the netSCADA:· SCADA supporting device for atvise web visualization· netSCADA Solutions product DVD including atvise builder software,Hilscher software components, firmware, USB driver anddocumentation

Optional accessories· Vector graphics library ATVISE ELEMENTS, part number: 1701.432

Contents of the product DVD

The netSCADA product DVD contains the following software:· atvise builder· Hilscher atvise Plugin containing Symbolizer, Hilscher WebMIServerDLL, predefined display designs and Hilscher LAN Scanner andConfiguration Tool

· USB drivers for Windows


© Hilscher 2010 – 2016

Introduction 8/175

Folder ContentsDocumentation Documentation in PDF format

Adobe Reader installation program for displaying the PDF documentsFirmware Loadable firmware for the netSCADA devicesfscommand Files for displaying the start screen and the installation menus of the product DVDSetups & Drivers Installation programs for the delivered softwareSupplements & Examples Device Recovery:

Tools for recovering NSCDT52 devices via USBExample Projects:· atvise example projects to be loaded into the netSCADA devices

· For NL 50NMPIATVISE and NSCDT52EN/ATVISE/PN devices only: STEP 7example projects to be loaded into a SIMATIC S7 PLC

· For NSCDT52EN/ATVISE/OMB and NSCDT52RS/ATVISE/MBR devices only:examples of symbol files containing Modbus signals to be imported into atvise

VideoAudio Tutorials Pod and screen cast presentations about commissioning netSCADA devices with atviseTable 4: Directory of the netSCADA product DVD

1.3 Documentation overviewThe subsequent table shows where to find information aboutcommissioning the netSCADA devices.

Media Contents Document/file Path on product DVDUser ManualnetSCADA deviceswith atvise builder(this document)

Installation, web visualization,operation and hardware descriptionof the netSCADA devices

netSCADA withatvise builder –WebVisualizationUM xx EN.pdf

Documentation\english\1.User Manual

atvise ReleaseNotes v2.5

Release Notes for version 2.5 of theatvise builder

release_notes_atvise_v2.5.pdf

Documentation\english\2.atvise WebVisualization

Online help of theatvise builder

Online help/operating instructionmanual of the atvise builderNote: The online help was createdby Certec EDV GmbH

atvise WebVisualization.html

Documentation\english\2.atvise WebVisualization

Note: Can be opened directly in atvise after having installedthe atvise builder on your configuration PC

netLINK SCADAPodcast

Audiovisual description of a simplecommissioning example for thenetLINK SCADA NL 50NMPIATVISE

netLINK SCADAPodcast x.x CommissioningExample.flv

VideoAudio Tutorials\netLINK SCADA

netSCADAModbusScreencast

Visual description of a simplecommissioning example for theNSCDT52RS/ATVISE/MBR

netSCADA ModbusScreencast QuickStart Guide.flv

VideoAudio Tutorials\netSCADA Modbus

netSCADAPROFINETScreencast

Visual description of a simplecommissioning example for theNSCDT52EN/ATVISE/PN

netSCADA PROFINETScreencast QuickStart Guide.flv

VideoAudio Tutorials\netSCADA PROFINET

Table 5: Dokumentation overview


© Hilscher 2010 – 2016

Introduction 9/175

Note:The screen/podcasts can be launched in the Quick Start VideoScreencasts menu of the netSCADA DVD flash start screen. As analternative, you can also play the FLV files by using any otherplayer that supports Flash videos, like e. g. the VLC Media Player.The VideoAudio Tutorials folder on the DVD contains a linkto a website, from which you can download the VLC Media Playerfor free.

1.4 Internet security considerations

1.4.1 HTTP server security considerationsAuthentication method: HTTP digest (user name and password are sentencrypted from client to server).

Any FTP client has full access to the user list and the passwords.

1.4.2 FTP server security considerations

FTP Server

Authentication method: Standard FTP (user name and password are sentunencrypted from client to server).

Recommendations

The best way to protect the device from unauthorized access is to keep itdisconnected from the Internet.

If the device must be accessible over the Internet, a secure connection likean encrypted VPN tunnel must be used.

Note:You MUST NOT allow access to FTP port (21) from the Internet byany means!


© Hilscher 2010 – 2016

Introduction 10/175

1.5 Legal notes

1.5.1 Copyright© Hilscher 2010 – 2016, Hilscher Gesellschaft für Systemautomation mbH

All rights reserved.

The images, photographs and texts in the accompanying material (usermanual, accompanying texts, documentation, etc.) are protected byGerman and international copyright law as well as international trade andprotection provisions. You are not authorized to duplicate these in whole orin part using technical or mechanical methods (printing, photocopying orother methods), to manipulate or transfer using electronic systems withoutprior written consent. You are not permitted to make changes to copyrightnotices, markings, trademarks or ownership declarations. The includeddiagrams do not take the patent situation into account. The companynames and product descriptions included in this document may betrademarks or brands of the respective owners and may be trademarked orpatented. Any form of further use requires the explicit consent of therespective rights owner.

1.5.2 Important notesThe user manual, accompanying texts and the documentation were createdfor the use of the products by qualified experts, however, errors cannot beruled out. For this reason, no guarantee can be made and neither juristicresponsibility for erroneous information nor any liability can be assumed.Descriptions, accompanying texts and documentation included in the usermanual do not present a guarantee nor any information about proper useas stipulated in the contract or a warranted feature. It cannot be ruled outthat the user manual, the accompanying texts and the documentation donot correspond exactly to the described features, standards or other data ofthe delivered product. No warranty or guarantee regarding the correctnessor accuracy of the information is assumed.

We reserve the right to change our products and their specification as wellas related user manuals, accompanying texts and documentation at alltimes and without advance notice, without obligation to report the change.Changes will be included in future manuals and do not constitute anyobligations. There is no entitlement to revisions of delivered documents.The manual delivered with the product applies.

Hilscher Gesellschaft für Systemautomation mbH is not liable under anycircumstances for direct, indirect, incidental or followon damage or loss ofearnings resulting from the use of the information contained in thispublication.


© Hilscher 2010 – 2016

Introduction 11/175

1.5.3 Exclusion of liabilityThe software was produced and tested with utmost care by HilscherGesellschaft für Systemautomation mbH and is made available as is. Nowarranty can be assumed for the performance and flawlessness of thesoftware for all usage conditions and cases and for the results producedwhen utilized by the user. Liability for any damages that may result from theuse of the hardware or software or related documents, is limited to cases ofintent or grossly negligent violation of significant contractual obligations.Indemnity claims for the violation of significant contractual obligations arelimited to damages that are foreseeable and typical for this type of contract.

It is strictly prohibited to use the software in the following areas:· for military purposes or in weapon systems;· for the design, construction, maintenance or operation of nuclearfacilities;

· in air traffic control systems, air traffic or air traffic communicationsystems;

· in life support systems;· in systems in which failures in the software could lead to personal injuryor injuries leading to death.

We inform you that the software was not developed for use in dangerousenvironments requiring failproof control mechanisms. Use of the softwarein such an environment occurs at your own risk. No liability is assumed fordamages or losses due to unauthorized use.

1.5.4 WarrantyAlthough the hardware and software was developed with utmost care andtested intensively, Hilscher Gesellschaft für Systemautomation mbH doesnot guarantee its suitability for any purpose not confirmed in writing. Itcannot be guaranteed that the hardware and software will meet yourrequirements, that the use of the software operates without interruption andthat the software is free of errors. No guarantee is made regardinginfringements, violations of patents, rights of ownership or the freedom frominterference by third parties. No additional guarantees or assurances aremade regarding marketability, freedom of defect of title, integration orusability for certain purposes unless they are required in accordance withthe law and cannot be limited. Warranty claims are limited to the right toclaim rectification.


© Hilscher 2010 – 2016

Introduction 12/175

1.5.5 Export regulationsThe delivered product (including the technical data) is subject to export orimport laws as well as the associated regulations of different counters, inparticular those of Germany and the USA. The software may not beexported to countries where this is prohibited by the United States ExportAdministration Act and its additional provisions. You are obligated tocomply with the regulations at your personal responsibility. We wish toinform you that you may require permission from state authorities to export,reexport or import the product.

1.5.6 TrademarksAcrobat® is a registered trademark of Adobe Systems Incorporated in theUSA and further countries.

atvise® is a registered trademark of Certec EDV GmbH, ThomasAlvaEdisonstrasse 1, A7000 Eisenstadt, Austria

Modbus is a registered trademark of Schneider Electric.

PROFIBUS® and PROFINET® are registered trademarks of PROFIBUSInternational, Karlsruhe.

SIMATIC®, STEP®7, S7®, S7300®, S7400®, S71200®, S71500® and MPI®are registered trademarks of Siemens AG, Berlin and Munich.

Windows XP®, Windows® 7 and Windows® 8 are registered trademarks ofMicrosoft Corporation.

All other mentioned trademarks are property of their respective legalowners.

1.6 LicensesA license for the atvise builder (a product of Certec EDV GmbH, ThomasAlvaEdisonstrasse 1, A7000 Eisenstadt, Austria www.atvise.com) belongsto the netSCADA device in order to be used in conjunction with the device.

An automatic license download is performed during the installation of theatvise builder. The installation program uses web services of the sitewww.atvise.com. Prerequisite for this is a working access to the Internet. Ifthe license download fails, then the license for the PC can be requestedafterwards from Certec by using the atvise project console and using acreated account.


© Hilscher 2010 – 2016

http://www.atvise.com


Safety 13/175

2 Safety

2.1 General safety notesThe user manual, accompanying texts and the documentation were createdfor the use of the products by qualified experts. When using the products,all safety notes and applicable regulations must be observed. Technicalknowledge is required. The user must comply with legal provisions.

2.2 Intended useThe netSCADA devices may only be used as a part of a communicationsystem as described in this manual.

The NL 50NMPIATVISE device (netLINK SCADA for PROFIBUS MPI)has been designed exclusively for use in connection with the SIMATIC S7PLCs· S7300· S7400

manufactured by Siemens AG.

The NSCDT52EN/ATVISE/PN device (netSCADA for PROFINET/RFC1006) has been designed exclusively for use in connection with one ofthe following SIMATIC S7 PLC equipped with a PROFINET interface:· S7300· S7400· S71200· S71500

The devices may not be opened or used without the housing.

2.3 Personnel qualificationThe netSCADA device is used as a part of a system which must fulfillsafety and accident precaution regulations depending on the respectiveconditions of use. The user of the system is exclusively responsible for thefulfillment of those regulations.

Therefore the system to which the netSCADA device belongs may only beused by personnel who has been informed and educated about all relevantregulations.

Professional qualification in the following specific areas of electricalengineering is required:· Security and protection of health at work· Mounting and attaching of electrical equipment· Measurement and analysis of electrical functions and systems· Evaluation of the security of electrical equipment


© Hilscher 2010 – 2016

Safety 14/175

2.4 References safetyReferences Safety:

[1] ANSI Z535.62006 American National Standard for Product Safety Information inProduct Manuals, Instructions, and Other Collateral Materials

[2] EN 6134051 and EN 6134052 as well as IEC 6134051 and IEC 6134052

2.5 Property damage messagesTo avoid property damage, respectively device destruction of thenetSCADA device or damage to your system, you necessarily must read,understand and follow the following and all other property damagemessages in this manual.

2.5.1 Supply voltage

Device destruction by exceeding allowed supply voltage!The voltage must not exceed 30 V, otherwise the device may be destroyedor damaged.

2.5.2 Electrostatic dischargeObserve the safety precautions for components that are vulnerable withelectrostatic discharge.

Electrostatically sensitive deviceThis equipment is sensitive to electrostatic discharge, which causes internaldamage and affects normal operation. Follow these guidelines when youhandle this equipment:Ø Touch a grounded object to discharge potential static.Ø Do not touch connectors or pins on component boards.Ø Do not touch circuit components inside the equipment.Ø When not in use, store the equipment in appropriate staticsafepackaging.

Reference safety [2]


© Hilscher 2010 – 2016

Safety 15/175

2.5.3 Possible device damage by compensating current at Modbus RTUinterface (NSCDT52RS/ATVISE/MBR)

Device damage of NSCDT52RS/ATVISE/MBR by compensatingcurrentThe reference potential of the power supply and the reference potential ofthe RS232/RS422/RS485 interface of the NSCDT52RS/ATVISE/MBRdevice are galvanically connected.Avoid compensating currents between the reference potentials of thedevices connected via RS232/RS422/RS485.

2.6 Labeling of safety messagesIn this document, the safety instructions and property damage messagesare designed according both to the internationally used safety conventionsas well as to the ANSI standard.· The Section Safety Messages at the beginning of a chapter arepinpointed particularly. They are highlighted by a specific safety symboland a signal word according to the degree of endangerment. In thesafety message, the nature of the hazard is indicated.

· The Integrated Safety Messages embedded in operating instructionsare highlighted by a signal word according to the degree ofendangerment and possibly by a safety symbol. In the safety message,the nature of the hazard is indicated.

Safetysymbol

SafetysymbolUSA

Sort of warning or principle

Warning of lethal electrical shock

Warning of damages by electrostatic discharge

Principle: Disconnect the power plug

Table 6: Safety Symbols and Sort of Warning or Principle

Signal word Meaning Meaning USADANGER Indicates a direct hazard with high risk, which will

have as consequence death or grievous bodilyharm if it is not avoided.

Indicates a hazardous situation which, if not avoided,will result in death or serious injury.

WARNING Indicates a possible hazard with medium risk,which will have as consequence death or(grievous) bodily harm if it is not avoided.

Indicates a hazardous situation which, if not avoided,could result in death or serious injury.

CAUTION Indicates a minor hazard with medium risk, whichcould have as consequence personal injury, if itis not avoided.

Indicates a hazardous situation which, if not avoided,may result in minor or moderate injury.

NOTICE Indicates a property damage message. Indicates a property damage message.Table 7: Signal Words


© Hilscher 2010 – 2016

Description 16/175

3 DescriptionHilscher netSCADA devices are Ethernet gateways for visualizing Fieldbusor RealTime Ethernet process data. Currently available are netSCADAdevices for the following communication protocols:· NL 50NMPIATVISE for PROFIBUS MPI (because of its compact,pluglike housing also called netLINK SCADA)

· NSCDT52EN/ATVISE/PN for PROFINET/RFC1006 for top hat railmounting

· NSCDT52RS/ATVISE/MBR for Modbus RTU for top hat rail mounting· NSCDT52EN/ATVISE/OMB for Modbus TCP/IP for top hat railmounting

The data is being visualized by the atvise software running on theintegrated HTTP server of the netSCADA device. The visualization can beaccessed by any standard web browser from an external PC via the 10/100MBit/s Ethernet interface of the device. Operation and configuration of thedevice also takes place via browser and Ethernet interface.

Manufacturer of the atvise visualization software is CERTEC EDV GmbH (www.atvise.com). The visualization software is integrated into thenetSCADA devices as an embedded solution.

The atvise builder software, which is part of the delivery, can be used tobuild a relation between the process data that is to be visualized and thevisualization contents (such as HTML pages, graphics, links, animations),and also to generate the visualization project. After loading the project intothe netSCADA device, it will be stored there power failsafe in a nonvolatilememory.

netSCADA devices are equipped with a trend recording functionality and anSNTP client for realtime synchronization of the system time with anyexternal SNTP server.

In order to keep the data load in the Fieldbus or RTE network low, anetSCADA device requests the signalstobevisualized from the busparticipants only at the very same moment when the visualization pages inthe device are being accessed by the web browser. However, in case atrend recording has been configured for certain signals, the device requeststhe state of the concerned signals (in order to be able to record them) alsoat times when the corresponding visualization pages are currently not beingdisplayed/accessed by the web browser, i. e. when no visualization accessis taking place.


© Hilscher 2010 – 2016

http://www.atvise.com/

Description 17/175

netLINK SCADA NL 50NMPIATVISE

Due to its compact DSublike housing, the netLINK SCADA NL 50NMPIATVISE can be fitted directly onto the bus connector of a PROFIBUSMPIcapable SIMATIC S7 component. It is connected to the nearest switch orhub via Ethernet cable. The visualization project, which has beforehandbeen created and downloaded to the device by the atvise builder and isnow running in the device, can be accessed via this Ethernet connection byan ordinary web browser on a PC or a notebook.

Figure 1: Overview data flow of netLINK SCADA NL 50NMPIATVISE

The power can be supplied directly via the DSub interface of the device (ifsupported by the SIMATIC S7 component), or alternatively externally via aCOMBICON plug with a voltage of 24 V.


© Hilscher 2010 – 2016

Description 18/175

netSCADA NSCDT52

The netSCADA devices for PROFINET, Modbus TCP/IP and Modbus RTUare to be mounted onto a top hat rail according to the DIN EN 60715standard. The devices require an external voltage supply of 24 V (viaCOMICON plug).

Figure 2: Overview data flow netSCADA NSCDT52RS/ATVISE/MBR

The devices are equipped with a realtime clock and a trend data buffer (8MByte Flash) for nonvolatile selective storage of signal values.


© Hilscher 2010 – 2016

Requirements 19/175

4 Requirements

4.1 Requirements for operating the netSCADA devicesThe following preconditions must be met in order to operate the netSCADAdevices successfully:· The supply voltage must be in the range between 18 V and 30 V DC.· Ethernet connection between the configuration PC and the netSCADAdevice.

· The netSCADA device must have a valid IP address which is accessiblefrom the configuration PC.

· License for atvise builder must be installed.· Visualization project has been successfully downloaded to the device.· Web browser

4.2 System requirements for the configuration PC· PC with 1 GHz processor or higher· Windows XP SP3, Windows 7 (32 bit) SP1 or Windows 7 (64 bit) SP1· Administrator privilege required for installation· DVD ROM drive· Graphic resolution: min. 1024 x 768 pixel· Keyboard and mouse

4.3 System requirements of atvise builder

4.3.1 Supported web browserThe web contents produced by atvise builder can be displayed by all webbrowsers supporting the web standards JavaScript (according to standardsECMA 262 or ISO/IEC 16262, see http://www.ecma‐international.org/publications/files/ECMA‐ST/ECMA‐262.pdf) and SVG (according to W3Cstandard, see http://www.w3.org/TR/SVG11/). This applies for newerversions of all commonly used web browsers.

A list of Web browsers which have been tested with atvise by itsmanufacturer can be obtained at http://www.atvise.com/en/vendors/compatibilitylist.

A web browser is also needed on the configuration PC for configuring thenetSCADA device.


© Hilscher 2010 – 2016

http://www.ecma-international.org/publications/files/ECMA-ST/ECMA-262.pdf

http://www.ecma-international.org/publications/files/ECMA-ST/ECMA-262.pdf

http://www.w3.org/TR/SVG11/

http://www.atvise.com/en/vendors/compatibilitylist

http://www.atvise.com/en/vendors/compatibilitylist

Requirements 20/175

4.3.2 Required disk spaceThe atvise builder requires approximately 128 MB of memory on hard diskif completely installed with all options depending on the size of the projectdatabase nodes.db.

The additional software components installed together with atvise requireabout 12.5 MB disk space.

Additional space may also be required for the Microsoft .NET Framework, ifthis has not already been installed previously on your PC.

4.3.3 Internet connection for installing atvise softwareDuring installation of the atvise builder, access to the Internet is required forregistration and licensing purposes. During registration of the atviseinstallation, an internet connection to the Certec EDV GmbH (http://www.atvise.com), the manufacturer of atvise, is established. Note that the internet connection for the atvise installation procedure mustnot be blocked by a firewall, i. e. the 443/TCP port of your PC must beenabled. If the online licensing does not succeed, a license key can berequested and installed via the project console of the installed atvise buildersoftware. To do so, it is necessary to create a web account, to order alicense and to invoke the license key under the created account.


© Hilscher 2010 – 2016



Device drawings and connectors 21/175

5 Device drawings and connectors

5.1 Dimensional drawings

NL 50NMPIATVISE

Figure 3: Dimensional drawing NL 50NMPIATVISE

NSCDT52

Figure 4: Dimensional drawing NSCDT52


© Hilscher 2010 – 2016


5.2 Connectors and LEDs

5.2.1 Overview connectors and LEDs NL 50NMPIATVISE

Figure 5: Connectors and LEDs NL 50NMPIATVISE

Elementposition

Description For details refer to

X1 Connector for power supply Section Voltage supply X1 [ page 28]X2 NL 50NMPIATVISE: PROFIBUS connector 9 pin,

DSub femaleSection PROFIBUS interface (NL 50NMPIATVISE) [ page 26]

X3 Ethernet connector RJ45 Section Ethernet interface [ page 25]X11 PROFIBUS connector 9 pin, DSub male 1:1

connection with X2)Section PROFIBUS interface (NL 50NMPIATVISE) [ page 26]

(1) SYS LED Section LEDs NL 50NMPIATVISE [ page 151](3) S7 COM LED(6) LED, green LINK (Connection) at X3(7) LED, yellow, ACT (Activity) at X3

Table 8: Connectors and LEDs NL 50NMPIATVISE


© Hilscher 2010 – 2016


5.2.2 Overview connectors and LEDs NSCDT52RS/ATVISE/MBR

Figure 6: Connectors and LEDs NSCDT52RS/ATVISE/MBR

Position Description For details refer to(1) Mini USB service interface (protected by a cover)

for resetting the device to its “factorysettings” (firmware reset/recovery)

Chapter Firmware recovery of NSCDT52 via USB [ page 145]

(2) X1 Connector for power supply Section Voltage supply X1 [ page 28](3) LEDs:

SYSTEMCONFIGMODBUSACTIVELOAD

Section LEDs NSCDT52RS/ATVISE/MBR [ page 152]

(4) Address rotary switch (multiplied 10) Not used (5) Address rotary switch (multiplied 1) Not used(6) X2 Modbus RTU connector (COMBICON) Section Modbus RTU interface (NSCDT52RS/ATVISE/

MBR) [ page 27](7) LED, green LINK (Connection) CH0 (IN) Section LEDs NSCDT52RS/ATVISE/MBR [ page 152](8) X3 Ethernet connector RJ45 CH0 (IN) Section Ethernet interface [ page 25](9) LED, yellow, ACT (Activity) CH0 (IN) Section LEDs NSCDT52RS/ATVISE/MBR [ page 152](10) LED, green LINK (Connection) CH1 (OUT)(11) X3 Ethernet connector RJ45 CH1 (OUT) Section Ethernet interface [ page 25](12) LED, yellow, ACT (Activity) CH1 (OUT) Section LEDs NSCDT52RS/ATVISE/MBR [ page 152]

Table 9: Connectors and LEDs NSCDT52RS/ATVISE/MBR


© Hilscher 2010 – 2016


5.2.3 Overview connectors and LEDs NSCDT52ENThis section describes the connectors and LEDs of the netSCADA devicesNSCDT52EN/ATVISE/PN for PROFINET/RFC1006 and NSCDT52EN/ATVISE/OMB for Modbus TCP/IP.

Figure 7: Connectors and LEDs NSCDT52EN

Position Description For details refer to(1) Mini USB service interface (protected by a cover)

for resetting the device to its “factorysettings” (firmware reset/recovery)

Chapter Firmware recovery of NSCDT52 via USB [ page 145]

(2) X1 Connector for power supply Section Voltage supply X1 [ page 28](3) LEDs NSCDT52EN/ATVISE/PN:

SYSTEMCONFIGRFC1006ACTIVELOAD

Section LEDs NSCDT52EN/ATVISE/PN [ page 154]

LEDs NSCDT52EN/ATVISE/OMB:SYSTEMCONFIGMODBUSACTIVELOAD

Section LEDs NSCDT52EN/ATVISE/OMB [ page 156]

(4) Address rotary switch (multiplied 10) Not used (5) Address rotary switch (multiplied 1) Not used(6) LED, green LINK (Connection) Section LEDs NSCDT52EN/ATVISE/PN [ page 154]

or LEDs NSCDT52EN/ATVISE/OMB [ page 156](7) X2 RJ45 RealTime Ethernet connector for

PROFINET/RFC1006 or Modbus TCP/IPSection Ethernet interface [ page 25]


© Hilscher 2010 – 2016


Position Description For details refer to(8) LED, yellow, ACT (Activity) Section LEDs NSCDT52EN/ATVISE/PN [ page 154]

or LEDs NSCDT52EN/ATVISE/OMB [ page 156](9) LED, green LINK (Connection) CH0 (IN)(10) X3 RJ45 Ethernet connector CH0 (IN) Section Ethernet interface [ page 25](11) LED, yellow, ACT (Activity) CH0 (IN) Section LEDs NSCDT52EN/ATVISE/PN [ page 154]

or LEDs NSCDT52EN/ATVISE/OMB [ page 156](12) LED, green LINK (Connection) CH1 (OUT)(13) X3 Ethernet connector RJ45 CH1 (OUT) Section Ethernet interface [ page 25](14) LED, yellow, ACT (Activity) CH1 (OUT) Section LEDs NSCDT52EN/ATVISE/PN [ page 154]

or LEDs NSCDT52EN/ATVISE/OMB [ page 156]Table 10: Connectors and LEDs NSCDT52EN

5.2.4 Ethernet interfaceThis section features the technical details of the Ethernet connectors of thenetSCADA devices. The details are valid for the X3 Ethernet interfaceimplemented on all netSCADA devices (by which the visualization isaccessed) and for the X2 RealTime Ethernet interface implemented on theNSCDT52EN/ATVISE/PN and NSCDT52EN/ATVISE/OMB devices.

Use an RJ45 plug and Ethernet cable Category 5 (CAT5) or higher, whichconsists of 4 wires twisted pairwise and allows a maximum transmissionrate of 100 MBit/s.Parameter ValueMedium Double twisted pair copper cable (2x2 wires), CAT5 (100 MBit/s)Length of line max. 100 mTransmission rate 10 MBit/s / 100 MBit/sTable 11: Data of Ethernet connection

Ethernet Pin Assignment at the RJ45 Socket

The device operates its Ethernet interface in the Autocrossover mode.Thus for the connection with Ethernet devices both crossover cables andpatch cables are applicable.Ethernet Pin Signal Description

RJ45 socket female

1 TX+ Transmit data positive2 TX– Transmit data negative

3 RX+ Receive data positive

4 Term 1 Connected and terminated to PEvia RC combination*5 Term 1

6 RX– Receive data negative

7 Term 2 Connected and terminated to PEvia RC combination*8 Term 2

* Bob Smith TerminationTable 12: RJ45 Ethernet pin assignment


© Hilscher 2010 – 2016


5.2.5 PROFIBUS interface (NL 50NMPIATVISE)

DSub connector (9 pin, male and female)NL 50NMPIATVISE

PROFIBUS interface (DSub femaleconnector, 9 pin)

The X2 DSub male connector connects the deviceto a S7 PLC (or to any free network connector alonga PROBIBUS or MPI bus). The pins of X2 DSub male and the X11 DSubfemale connector have a 1 to 1 connection.

Table 13: Description PROFIBUS interface (DSub Connector, 9 pin)

Connection with DSubmale / female connector

Signal Description

1 unused, is only connected through2 GND Ground (for VS)3 RxD/TxDP Receive / Send DataP respectively connection B

plug4 unused, is only connected through5 ISOGND Reference potential (PROFIBUS)6 unused, is only connected through7 VS Supply voltage input (24 V), alternatively to X18 RxD/TxDN Receive / Send DataN respectively connection A

plug9 unused, is only connected throughShield ShieldTable 14: Pinning PROFIBUS MPI interfaces (DSub female and male connector, 9 pin)


© Hilscher 2010 – 2016


5.2.6 Modbus RTU interface (NSCDT52RS/ATVISE/MBR)The Modbus RTU interface (X2, see position (6) in section Overviewconnectors and LEDs NSCDT52RS/ATVISE/MBR [ page 23]) supportsthe interface types RS232, RS422 and RS485. You have to select theright interface type in the atvise builder when you configure the visualizationproject (see section Configuring Modbus RTU parameters [ page 87]).

Device damage by compensating currentThe reference potential of the power supply and the reference potential ofthe RS232/RS422/RS485 interface are galvanically connected. Avoid compensating currents between the reference potentials of thedevices connected via RS232/RS422/RS485!

RS232 at X2 Pin Signal Description

COMBICONsocket, 5pole

1 GND Reference potential: nonisolated4 RxD Receive data

5 TxD Transmit data

Table 15: Pin assignment RS232 interface (COMBICON socket, 5pole)



2 RxD Receive data negative3 RxD + Receive data positive

4 TxD + Transmit data positive

5 TxD Transmit data negative



© Hilscher 2010 – 2016




2 RxD / TxD Receive data / Transmit data negative3 RxD / TxD + Receive data / Transmit data positive


5.2.7 Voltage supply X1The netSCADA devices need a voltage supply of 24 V (18 V – 30 V) DC.

NL 50NMPIATVISE

If voltage is not supplied by the S7, you can use the X1 connector forexternal voltage supply. The 2pole Mini Combicon socket for connectingan external power supply is located at the bottom side of the device (seeX1 in section Overview connectors and LEDs NL 50NMPIATVISE [ page 22]).

Pin assignment of the 2pole Mini Combicon socket for voltage supply atX1:Supply voltage Pin Signal Description

Mini Combicon

1 0 V / GND Ground of supply voltage2 24 V +24 V supply voltage

Table 18: Pin assignment Mini Combicon socket 2pole

NSCDT52

The 5pole Mini Combicon socket for connecting an external power supplyis located at the top side of the device (see position (2) in section Overviewconnectors and LEDs NSCDT52RS/ATVISE/MBR [ page 23]respectively Overview connectors and LEDs NSCDT52EN [ page 24]).Pin 5 can be connected to a potential equalization conductor (PE).


© Hilscher 2010 – 2016


Pin assignment of the 5pole Mini Combicon socket for voltage supply atX1:Supply voltage Pin Signal Description

Mini Combicon

1 +24 V +24 V supply voltage2 0 V / GND Ground of supply voltage

3

4

5 PE Protective earth

Table 19: Pin assignment Mini Combicon socket 5pole

5.3 Galvanic isolation schematic diagrams

NL 50NMPIATVISE

At the netLINK SCADA NL 50NMPIATVISE, the PE connection is madevia the protective cover of the plug (connection between the shields of thedata cables).

Figure 8: Galvanic isolations NL 50NMPIATVISE

Areaconnection

Interface galv.isolation

Coupling Coupling against PEpotential

Functional earthing to PE

(1)X1

Voltagesupply no

HF (1) Lf = 80 Ω @ 100 MHzCx1 (1) 1 * 1 nF / 1000 V

1 * 22 pF / 63 V(2)X2

PROFIBUSDP

optical Cx2 (2) 1 MΩ // 2.2 nF/ 500 V directly via the metalconnection of the DSubfemale connector

(3)X3

Ethernet inductive Cx3 (3) 4 * 75 Ω, 1 nF / 2000 V directly via the metalconnection of RJ 45 sockets

Table 20: Coupling NL 50NMPIATVISE


© Hilscher 2010 – 2016


NSCDT52RS/ATVISE/MBR

Figure 9: Galvanic isolations NSCDT52RS/ATVISE/MBR

Areaconnection




(1)X1

Voltagesupply no

HF (1) Cf = 10nF / 500 V,Lf = 100 μH

Pin 5 of X1 connecteddirectly to PE

Cx1 (1) 3 * 10 nF / 500 V(1)X2

RS232RS422RS485

no No connection via connector

X2

(2)X3

Ethernet inductive Cx3 (2) 4 * 75 Ω + 1 nF / 2000 V Directly connected via themetal housing of RJ45sockets

Table 21: Coupling NSCDT52RS/ATVISE/MBR

Important:For this device it is recommended to implement a galvanic isolationwithin the voltage supply of the device.


© Hilscher 2010 – 2016


NSCDT52EN

Figure 10: Galvanic isolations NSCDT52EN

Areaconnection




(1)X1

Voltagesupply

no HF (1) Cf = 10nF / 500 V,Lf = 100 μH

Pin 5 of X1 connecteddirectly to PE

Cx1 (1) 3 * 10 nF / 500 V(2)X2

RealTimeEthernet

inductive Cx2 (2) 4 * 75 Ω + 1 nF / 2000 V Directly connected via themetal housing of RJ45socket

(3)X3

Ethernet inductive Cx3 (3) 4 * 75 Ω + 1 nF / 2000 V Directly connected via themetal housing of RJ45sockets

Table 22: Coupling NSCDT52EN


© Hilscher 2010 – 2016

Mounting 32/175

6 Mounting

6.1 Mounting NL 50NMPIATVISE

Mounting

Figure 11: Mounting NL 50NMPIATVISE

The netLINK SCADA NL 50NMPIATVISE is plugged onto an S7PROFIBUSMPI interface or any other compatible device with itsPROFIBUSMPI interface (1) and fixed by screws (2).

Note:The netLINK SCADA can also be connected to any free networkconnector in a PROFIBUS or MPI bus. Note, that in this case, thedevice needs an external 24V voltage supply.

Grounding

The device is grounded via the metal connection of the DSub femaleconnector.

Dismounting

For dismounting, loosen the screws (2) and disconnect the NL 50NMPIATVISE from the PROFIBUS MPI interface.


© Hilscher 2010 – 2016

Mounting 33/175

6.2 Mounting NSCDT52

Mounting

Mount the NSCDT52 device onto a top hat rail according to DIN EN60715. The top hat rail has to be attached horizontally at the intendedlocation.

Figure 12: Mounting NSCDT52

Ø Push the device onto the top hat rail from above (1).Ø Then press the device against the rail until the bolt of the lower hookengages (2).

After mounting, connect the 24 V supply voltage to the device.

Grounding

The rear of the netSCADA device is equipped with a grounding contact. Ifthe DIN top hat rail is connected to a potential equalization conductor (PE),grounding will automatically be achieved via contact of the backside of thedevice and the potential equalization conductor of the top hat rail.

As an alternative, you can connect Pin 5 of the voltage supply connector X1(Mini Combicon socket) to PE (see also sections Voltage supply X1 [ page 28] and Galvanic isolation schematic diagrams [ page 29])


© Hilscher 2010 – 2016

Mounting 34/175

DismountingØ In order to remove the device from the top hat rail, first remove thepower supply cable and all data cables from the device.

Figure 13: Dismounting NSCDT52

Ø Put a screw driver into the slot of the latch at the bottom of the device.Ø To disengage the lock of the hook, pull down the latch with the screwdriver.

Ø Take the device off the top hat rail.


© Hilscher 2010 – 2016

Installing the software 35/175

7 Installing the softwareOverview

The software installation program on the netSCADA DVD contains allsoftware components needed for installation under Windows. It automatically detects which components are already present on yoursystem and which components still need to be installed.

You can start the installation program in the menu of the start screen of thenetSCADA DVD. Instructions for this are provided below.

If you have an older version of the atvise builder installed on your PC:

The installation program on the DVD features a routine which automaticallyuninstalls any older version of the atvise builder from your PC. Please notethat the old nodes.db database file of the old atvise version will not bedeleted from the PC by the uninstallation process, neither by theuninstallation routine which is part the installation program started from theDVD, nor by the Uninstall or change a program feature of the WindowsControl Panel. The nodes.db file is usually stored in the C:\Program Files(x86)\atvise directory. You will be notified if the installation routine findsan old nodes.db database file during installation of the new atvise builder.The routine then automatically opens a dialog window in which you canchoose a directory where you can save the old database file.

In case the old nodes.db database file is incompatible with your new atvisebuilder version, but you still want to keep on using this old file, you can(after having installed the new atvise software) use the atvise databasemaintenance tool to update this old database file to the new atvise version.

Further information on updating old atvise database files belongingto old atvise builder versions can be found in the PDF documents inthe atvise installation folder (usually the C:\Program Files(x86)\atvise directory).

Prerequisites for installation· You need administrator rights for installation under Windows.· An internet connection is required for registration and licensingpurposes.

· Port 443/TCP of your Windows PC must not be blocked by a firewallbecause it is needed for connecting to the atvise website via HTTPS forregistration/licensing!


© Hilscher 2010 – 2016


Stepbystep instructionsØ Close all application programs on the PC onto which you intend toinstall the atvise Software.

Ø Insert the DVD into the local DVD ROM drive of your PC.Ê If the auto start feature of your PC is enabled, the start screen of theDVD opens automatically.

Ø If the auto start feature on your PC is disabled, change to the rootdirectory of the DVD and doubleclick the netSCADA.exe file.

Ê The start screen of the DVD appears:

Figure 14: Start screen netSCADA DVD

Ø In the menu of the start screen, select Install Web Visualization atviseÊ The installation program opens:

Figure 15: atvise installation program


© Hilscher 2010 – 2016


Note:The installations/uninstall options listed in the dialog windowdepend on the configuration of your PC. The configuration isautomatically checked by the installation program, therefore youshould not deselect any of the preselected options. If you dootherwise, the operability of the whole installation might beimpaired.

Ø Click Execute.Ê The installation routines are started. What dialog windows are displayedin the course of the installation process depends on the configuration ofyour PC. If, for instance, an older version of the atvise builder is stillpresent on your PC, this older version will first be automaticallyremoved.

Ø Follow the instructions given in the dialog windows of the installationprogram.

Ê The Installation program installs the atvise Software.Ê If an old nodes.db database file is found on your PC during installation,the following dialog appears:

Figure 16: Save nodes file dialog

Ø Click OK.Ê The Browse For Folder dialog window opens.Ø In the Browse For Folder dialog window, choose the directory whereyou want to store the file, then click OK.

Ê After the atvise builder software has been installed and licensed, thesetup routine for the atvise Hilscher Plugin starts.

Ø Read the license agreement and click I accept the agreement, if youaccept the terms of the license agreement.

Ø Click Next, then click Install.ð After having finished the installation process, a message will be shown.


© Hilscher 2010 – 2016

Creating visualization with the atvise builder 38/175

8 Creating visualization with the atvise builder

8.1 OverviewThis chapter describes how to use the atvise builder to create yourvisualization project and your web content and how to download the projectto the netSCADA.

When generating a visualization, the atvise builder software works withsymbolic names of the data points in order to assign the graphics to thecorresponding data reference. Direct addresses of data points of the deviceto be visualized do not need to be specified; instead, a mapping table of thephysical addresses and the data points has to be configured in the SignalEditor once.

Visualizing STEP 7 projects (NL 50NMPIATVISE and NSCDT52EN/ATVISE/PN)

The atvise builder contains an interpreter called Symbolizer for STEP 7projects which is capable of importing symbols and variables directly fromthe STEP 7 project, making the variables accessible as data points withinatvise. Thus the corresponding STEP 7 project can be loaded directly intoatvise in order to generate the reference data by which the S7 PLC will beaccessed. The reference data can then be assigned simply by selection.

You can also configure the symbols yourself; but you always need a STEP7 file for this. If you haven’t got a STEP 7 file at your disposal, you can findan empty STEP 7 file on the netSCADA Solutions DVD in theSupplements & Examples\Example Projects\[devicename]\Symbolless, empty STEP7 Project folder.

Note:The NL 50NMPIATVISE and NSCDT52EN/ATVISE/PN devicescannot be used for programming a SIMATIC S7 PLC. For thispurpose, a netLINK NL 50MPI or netTAP NT 50MPI device fromHilscher is needed.

Visualizing Modbus data

The variables/signals of the Modbus which are to be visualized bynetSCADA NSCDT52RS/ATVISE/MBR or netSCADA NSCDT52EN/ATVISE/OMB devices can be defined and configured directly in the SignalEditor. An interpreter like the Symbolizer is not needed for this.

If stored in a CSV (comma separated values) text file, lists or tables of preconfigured Modbus signals can be easily imported into your webMI Serverproject (and afterwards reedited, if necessary).


© Hilscher 2010 – 2016


8.2 Starting the atvise builder

Stepbystep instructions

To start the atvise builder, you must first open the Project Console viathe Windows Start menu or via the Windows Task bar:

1. Open Project Console.Ø To open Project Console via Windows Start menu: Choose Start > All Programs > atvise > Project Console.

Figure 17: Open Project Console via Windows Start menu

Ê The Project Console opens.Ø To open Project Console via Windows Task bar: In the right corner of the Task bar, click symbol.

Ê The following menu opens:

Figure 18: Menu of Project Console

Ø Click Project Console entry.


© Hilscher 2010 – 2016


Ê The Project Console opens:

Figure 19: Project Console

2. Start atvise builder.

Ø In the Project Console, click Builder button.Ê If you are starting the atvise builder for the first time and/or if you havenot defined a WebMI Server for your project yet, the Add webMIServer dialog opens. This dialog window appears prior to the startscreen of the “actual” atvise builder GUI, i. e. the editor in which you cancreate the visualization.


© Hilscher 2010 – 2016


Figure 20: Add webMI Server dialog

Ø You can now configure your netSCADA device in the Add webMIServer dialog (for details see the corresponding Configuring netSCADAdevice section for your device type).If you don’t want to use the preset default IP address 192.168.0.133for your netSCADA device, you can click the Device Setup… button toopen the LAN Scanner and Configuration Tools (which is integratedas plugin in the atvise builder) and then use the tool to assign asuitable temporary IP address to your device (see section Assigningtemporary IP address [ page 43]).

Ø If you want to start the atvise builder GUI instantly, and finish theconfiguration of your netSCADA device as WebMI Server in this dialogwindow later, click the OK button in order to close this dialog windownow.

Note:If you want to reopen this configuration dialog window later, inorder to finish the configuration of the netSCADA, doubleclick theserver entry in the project tree of the atvise builder. The reopenedconfiguration dialog window is then called Edit webMI Server andnot Add webMI Server like before.


© Hilscher 2010 – 2016


ð The start screen of the atvise builder appears:

Figure 21: Start screen atvise builder


© Hilscher 2010 – 2016


8.3 Assigning temporary IP addressIn its state of delivery, the netSCADA device has the IP address192.168.0.133. If this preset address is not suitable for you, you must first assign a newtemporary IP address to the device by using the LAN Scanner andConfiguration Tool, which is integrated as plugin in the atvise buildersoftware.

Important:Take care that the netSCADA device can be reached by theconfiguration PC via the local Ethernet network.

To start the LAN Scanner and Configuration Tool, you first need to openthe Add webMI Server respectively the Edit webMI Server dialog window.The Add webMI Server dialog window opens automatically when you startthe atvise builder and haven’t yet defined a WebMI Server for your projectyet. The Edit webMI Server dialog window will be opened if you havealready defined a WebMI Server. In that case, you can select this WebMIServer in the project tree of the atvise builder and then choose EditServer… from the context menu, in order to open the dialog window.

1. Start LAN Scanner and Configuration Tool.Ø In the opened Add webMI Server respectively Edit webMI Serverdialog window, click Device Setup… button.

Figure 22: webMI Server dialog window


© Hilscher 2010 – 2016


Ê The LAN Scanner and Configuration Tool opens.

Figure 23: LAN Scanner and Configuration Tool (1)

2. Search for netSCADA devices.Ø Click Search Device button.Ê The tool now searches for connected netSCADA devices in all Ethernetnetworks available for the configuration PC. All found devices are listed:

Figure 24: LAN Scanner and Configuration Tool (2)

3. Set IP Address.Ø Select the device for which you want to assign a temporary new IPaddress.

Ø Click Configure button, then choose Set temporary IP Address…


© Hilscher 2010 – 2016


Ê The IP Configuration dialog box appears:

Figure 25: Set IP address

Ø Enter the IP address by which the netSCADA shall be accessed by yourconfiguration PC.

Ø Click OK button.ð The IP address is set temporarily in the device (and remains valid untilnext poweron cycle).

Important:In order to set the IP address permanently, so that it remains valideven after powerfail, you later have to use the Web ConfigurationInterface of the netSCADA device (see section Using the WebConfiguration Interface of the netSCADA devices [ page 125]).

If you want to connect directly with the Web Configuration Interface of thenetSCADA device, e. g. in order to configure a permanent (remanentlystored) IP address for your device, you can do so instantly from within theLAN Scanner and Configuration Tool by clicking the Configure button,then choosing Open Web Configuration Page… entry from the contextmenu. The standard web browser of your configuration PC starts andconnects to the login dialog of the Web Configuration Interface of thenetSCADA device.


© Hilscher 2010 – 2016


8.4 Creating projects for NL 50NMPIATVISE and NSCDT52EN/ATVISE/PN

8.4.1 OverviewThis section describes how to create visualization projects from a STEP 7project file for the NL 50MPIATVISE and NSCDT52EN/ATVISE/PNdevices in atvise. Both devices are intended for visualizing data from aSIMATIC PLC and thus need to be configured in atvise by using thecorresponding STEP 7 project file. The atvise builder contains a softwarecomponent called “Symbolizer”, which is capable of interpreting data fromthe STEP 7 project file. The following section Using existing STEP 7 projectfile [ page 46] describes how to import such a project file into atvise. Theinstructions apply to both NL 50MPIATVISE and NSCDT52EN/ATVISE/PN.

8.4.2 Using existing STEP 7 project file

8.4.2.1 Selecting STEP 7 project file

Note:You need access to the entire STEP 7 project folder containing theproject file (the project file can be recognized by its *.s7pextension). Thus, for instance, if you want to use the Demo_Atvexample project provided on the product DVD, make sure that youcopy the entire project folder with all its subfolders before saving iton your local PC and importing it.


© Hilscher 2010 – 2016


Ø For selecting the STEP 7 project whose data points are intended to bevisualized, click on SIMATIC S7 Project… button in the Edit webMIServer dialog window (respectively Add webMI Server dialog window).

Figure 26: webMI Server dialog


© Hilscher 2010 – 2016


Ê The Choose PLC Program to Import dialog opens, in which you canselect a STEP7 project (the file name extension of the project file is*.s7p):

Figure 27: Selecting S7 project dialog

Ø Select the STEP 7 project file, then click Open to import the STEP 7project file.

ð The STEP 7 project file is loaded and the file selection dialog closes.

8.4.2.2 Acquiring data points (signals) from STEP 7 project file

This section describes the selection of the signals which shall be accessedand visualized by atvise.

For this, you first have to select the STEP 7 project (see section SelectingSTEP 7 project file [ page 46]), from which the signals should be acquired.

Important:STRING and ARRAY data types of the STEP 7 program cannot beprocessed. The data type STRUCT is only supported if it does notcontain STRING and ARRAY data types. For more on allowed datatypes, please refer to section STEP 7 data type support of theSymbolizer [ page 52].

Note:If you don’t have a STEP 7 file at your disposal and/or want todefine all data points yourself, you can find an empty STEP 7project file on the netSCADA DVD in the Supplements &Examples\Example Projects\[devicename]\Symbolless, empty STEP7 Project folder.


© Hilscher 2010 – 2016


In order to acquire the signals, proceed as follows:Ø In the project tree of the atvise builder, select the netSCADA devicewhich you have configured as your webMI Server, then use the rightmouse button to open the context menu and choose AcquireDatapoints.

Figure 28: Acquire data points

Or:Ø As an alternative, you can choose Guided Actions > Import allvariables from the menu bar of the atvise builder and then select thenetSCADA device which you have configured as your webMI Server.

Figure 29: Import variables from netSCADA


© Hilscher 2010 – 2016


Ê The dialog window of the Symbolizer opens:

Note:The Symbolizer allows you to select a subset of the data points,which later shall be available for the generation of the visualization.

Figure 30: GUI of the Symbolizer

Important:Reading in the signals from the STEP 7 project happens only once.If this dialog is opened more than once, the Symbolizer alwaysworks with a copy of the signal list.If you want to extend the STEP 7 project and add further signalslater on, you then must either select the project again (as describedin section Selecting STEP 7 project file [ page 46]) or the newsignals must be manually configured in the Signal Editor of theSymbolizer.

· The tree in the Available Signals area lists all data blocks orsymbols which have been readin from the STEP 7 project.

· The tree in the Customized Signals area lists the selected variablesto be included in atvise.

Note:The GUI of the Symbolizer can be enlarged by pulling the lowerright corner.

Ø Transfer the signals intended for being accessed by atvise from area to area . Use the buttons described below.


© Hilscher 2010 – 2016


The three arrow buttons in the center (area ) can be used as describedbelow:· By using the > button (1) you can add STEP 7 variables/data blocks tothe Customized Signals list of STEP 7 variables which shall beaccessible by atvise.

· If you want to exclude an already selected variable from theCustomized Signals list, click on it first in the right list field, then click <button (2).

· If you want to exclude all variables at once from the CustomizedSignals list, click << button (3).

The Customized Signals (area ) features the following elements:· A navigation tree (4) containing control elements for expanding orcompressing items.

· A column featuring icons (5).· The Station Address column (6).The address of the S7 component is tagged with a question mark aslong as no bus address has been configured. Configuring the busaddress is mandatory, otherwise the dialog cannot be left with OK!

Note:Doubleclicking in the marked area on position (6) opens the SignalEditor, allowing you to set the bus address of the PLC and performother signal settings (see section Configuring signals in the SignalEditor [ page 60]).

· The Name column (7) featuring the name of the SIMATIC S7 data blockor symbol (as defined in the STEP 7 project).

· The Access column (8). The Access parameter defines the read, write or read and writeaccess to the signal.

Position Button Description(9) OK Stores the settings and closes the Symbolizer.(10) Cancel Closes the Symbolizer without storing the settings.(11) Apply Stores the settings without closing the Symbolizer.(12) Edit Opens the Signal Editor.

Table 23: Further control elements of the Symbolizer

Ø After selecting and editing the signals, click OK (9) button, in order tomake the Customized Signals available for the atvise builder and thevisualization.

ð You have imported the data points from the STEP 7 project. The signalsare now available for designing your displays. Proceed to sectionCreating the visualization (designing the displays) [ page 108].


© Hilscher 2010 – 2016


8.4.2.3 STEP 7 data type support of the Symbolizer

Simple STEP 7 data types

The following simple STEP 7 data types are supported by the Symbolizer:Data type Description Allowed range of

valuesLower limit

Allowed range ofvaluesUpper limit

Supported bySymbolizer

BOOL Data type for Boolean values. These dataare stored each in a single bit. Theallowed range of values only contains thevalues TRUE and FALSE

FALSE TRUE Yes

BYTE Unsigned 8 bit integer data type 0 255 YesWORD Unsigned 16 bit integer data type 0 65535 YesINT Signed 16 bit integer data type 32768 32767 YesDWORD Unsigned 32 bit integer data type 0 2321 YesDINT Signed 32 bit integer data type 231 2311 YesREAL Signed 32 bit real data type with

exponential representation+/1.175495e38 +/3.402823e+38 Yes

CHAR 8 bit character data type for storing ASCIIcharacters such as ‘a’, ‘b’ and so on.Internal processing as being of typeBYTE.

All ASCII characters allowed Yes

S5TIME Unsigned 16 bit data type for storage ofthe S7internal time in steps of 10milliseconds. Internal processing asbeing of type WORD.

Valid time Yes

DATE Unsigned 16 bit data type for storage ofthe IECtime in steps of 1 day. Internalprocessing as being of type WORD.

Valid date Yes

TIME Signed 32 bit data type for storage of theIECtime in steps of 1 millisecond.Internal processing as being of typeDWORD.

Valid time Yes

TIME_OF_DAY 32 bit data type for storage of the clocktime in steps of 1 millisecond. Internalprocessing as being of type DWORD.

Valid time of day Yes

Table 24: Simple STEP 7 data types


© Hilscher 2010 – 2016


Structured STEP 7 data types

The following structured STEP 7 datatype is only supported by theSymbolizer if it does not contain any ARRAY or STRING elements:· STRUCT

This is a data type for structures of multiple elements consisting of usuallydifferent data types.

The following structured STEP 7 datatypes are not supported by theSymbolizer at all:· ARRAY

This is a data type for a field, i.e. a group of elements of the same type.· STRING

This is a data type for strings, i.e. concatenated characters.

User defined data types and other data types not mentioned here are notsupported by the Symbolizer.As an alternative, the data type Byte can be used.


© Hilscher 2010 – 2016


8.4.3 Creating project for NL 50NMPIATVISE (netLINK SCADA forPROFIBUS MPI)

8.4.3.1 Overview of the necessary steps

To create a visualization project for your NL 50NMPIATVISE device, youneed to perform the following steps:

Configure netLINK SCADA1. Enter a name2. Under Hostname, enter IP address of the netLINK SCADA device3. Under Type, select Hilscher netLINK SCADA (NL 50MPIATVISE)entry

4. Assign temporary IP address (Device Setup…)5. Select STEP 7 project6. Configure MPI Settings

Acquire data points(import and select symbols from STEP 7 program)1. Select variables2. Set access type3. Enter PROFIBUS address of S74. Add marker, if necessary5. Select variables for trending, if necessary

Create displays and link elements to data points1. Select and place display elements2. Link data points3. Layout display

Generate (compile) displays (i. e. visualization web pages) andtransfer them into the netLINK SCADA device

Show generated displays (i. e. visualization web pages) in webbrowser1. Connect to start page2. Show web pages in browser


© Hilscher 2010 – 2016


8.4.3.2 Configuring netLINK SCADA device

A netSCADA device is administered within atvise as webMI Server. Inorder to select and configure the NL 50NMPIATVISE as webMI Server,proceed as follows:

1. Open webMI Server configuration dialog window.

Note:As long as you haven’t added a WebMI Server yet, the Add webMIServer dialog window opens automatically on every startup of theatvise builder.

Ø In the project tree of the atvise builder, select Servers entry. Then usethe right mouse button to open the context menu and choose AddServer… > WebMI.

Figure 31: Add Server

Or:Ø As an alternative, you can choose Guided Actions > Add atvisewebMI compliant Webserver from the menu bar of the atvise builder.

Note:If you have already added a “provisional” webMI Server (forexample on first starting up the atvise builder software), whichhasn’t been properly configured yet, you can reopen the webMIServer dialog for this provisional webMI Server by selecting theentry for this server in the project tree and then choosing EditServer… from the context menu. You can then complete theconfiguration of this provisional webMI Server in the opened EditwebMI Server dialog window.


© Hilscher 2010 – 2016


Ê The Add webMI Server (respectively the Edit webMI Server) dialogwindow opens with the General tab:


2. Enter basic parameters.Ø In the Name field, enter a name for your server (i. e. the netLINKSCADA device).

Ø In the Hostname field, enter the IP address (e.g. 10.11.5.98) underwhich the visualization pages of the netLINK SCADA shall be accessedvia Ethernet LAN and web browser.

Ø In the Type dropdown list, select Hilscher netLINK SCADA (NL 50MPIATVISE) entry.

3. Select STEP 7 project file.Ø After having selected the Hilscher netLINK SCADA (NL 50MPIATVISE) entry, the SIMATIC S7 Project… button becomes visible. Byclicking this button you can open a dialog in which you can select aSTEP 7 Project containing the S7 components that you want to importin order to visualize them. For details, see section Selecting STEP 7project file [ page 46].

4. Assign temporary IP address.Ø Click Device Setup… button to open the LAN Scanner andConfiguration Tool, which is a tool for assigning a temporary IPaddress within the Ethernet LAN. For details, see section Assigningtemporary IP address [ page 43].


© Hilscher 2010 – 2016


5. Configure MPI/PROFIBUS parameters.Ø Click MPI/PROFIBUS Settings… button to open a dialog in which youcan configure the PROFIBUSMPI settings of the netLINK SCADA. Fordetails, see section Configuring PROFIBUSMPI parameters [ page58].

Note:In the Layout tab, you can choose a predefined standard layout forthe visualization which you are going to create.

6. Save webMI Server.Ø After having configured the webMI Server, click OK button, to save theparameters of the webMI Server and to close the dialog window.

ð You have configured the netLINK SCADA device as webMI Server.

Note:If you want to reopen this configuration dialog window later,doubleclick the server entry in the project tree of the atvise builder.The reopened configuration dialog window is then called EditwebMI Server and not Add webMI Server like before.


© Hilscher 2010 – 2016


8.4.3.3 Configuring PROFIBUSMPI parameters

The PROFIBUSMPI communication parameter (like e.g. the bus addressor the Baud rate) can be configured in the MPI/PROFIBUS dialog window.Ø In the Add webMI Server (respectively Edit webMI Server) dialogwindow, click MPI/PROFIBUS Settings… button (see sectionConfiguring netLINK SCADA device [ page 55]).

Ê The MPI/PROFIBUS dialog window opens:

Figure 33: PROFIBUSMPI parameters

Note:The figure above shows the dialog in its initial state, when all valuesare adjusted to their default values. The fields grayed out in thisdialog will open for input only after having chosen a customizedvalue instead of the autodetect entry from the Baud Rate dropdown list.

Ø In the Station Address field, enter the PROFIBUSMPI address of thenetLINK SCADA device at the PROFIBUS.


© Hilscher 2010 – 2016


The subsequent table describes the parameter in detail:Parameter Description Range of Values/ValueStation Address PROFIBUS MPI Address of the netSCADA device. 0 … 126,

Default: 1Baud Rate PROFIBUS MPI Baud Rate

Indicates the velocity of transmission: Number of bits per second.Important: The setting of the Baud Rate is mandatory !The AutoDetect option is only possible if the communication isinitiated by another bus participant.

9,6 kBit/s,19,2 kBit/s,31,25 kBit/s,45,45 kBit/s,93,75 kBit/s,187,5 kBit/s,500 kBit/s,1,5 MBit/s,3 MBit/s,6 MBit/s,12 MBit/s,AutoDetect,Default: 187,5 kBit/s

Slot Time Slot Time (TSL) 'Wait for receipt' monitoring time of the senders (Requestor) oftelegram for the acknowledgement of the recipient (Responder).After expiration, a retry occurs in accordance with the value of 'Max.telegram retries'

37 ... 16383 tBit,Default: 415 tBit

Min. Station DelayResponder

Minimum Station Delay of Responders (min TSDR), This is the shortest time period that must elapse before a remoterecipient (Responder) may send an acknowledgement of a receivedquery telegram. The shortest time period between receipt of the lastBit of a telegram to the sending of the first Bit of a followingtelegram.


Max. Station DelayResponder

Maximum Station Delay of Responders (max TSDR)This is the longest time period that must elapse before a Sender(Requestor) may send a further query telegram. Greatest time periodbetween receipt of the last Bit of a telegram to the sending of the firstBit of a following telegram.The Sender (Requestor, Master) must wait at least for this timeperiod after the sending of an unacknowledged telegram (e.g.Broadcast only) before a new telegram is sent.


Quiet Time Quiet Time (TQUI) This is the time delay that occurs for modulators (Modulatortriptime) and Repeaters (Repeaterswitch time) for the change overfrom sending to receiving.


Setup Time Setup Time (TSET)Minimum period “reaction time” between the receipt of anacknowledgement to the sending of a new query telegram(Reaction) by the Sender (Requestor).

1 … 255 tBit,Default: 1 tBit

Target Rotation Time Target Rotation Time (TTR)Preset nominal Token cycling time within the Sender authorization(Token) will cycle around the ring. How much time the Master stillhas available for sending data telegrams to the Slaves is dependenton the difference between the nominal and the actual token cyclingtime.

≥ 255 tBit,Default: 10000 tBit

GAP ActualizationFactor

GAP Actualization Factor (G)Factor for determining after how many Token cycles an addedparticipant is accepted into the Token ring. After expiry of the timeperiod G*TTR, the Station searches to see whether a furtherparticipant wishes to be accepted into the logical ring.

1 … 255,Default: 20

Highest StationAddress

Highest Station Address (HSA)Station address of the highest active (Master) station.

1 … 126,Default: 31

Max. Retry Limit Max number of telegram retries (Max_Retry_Limit)Maximum number of repetitions allowed for reaching a station.

1 ... 8,Default: 1

Table 25: Parameters PROFIBUS MPI


© Hilscher 2010 – 2016


Note:Please note the following about Bit times: All times for the Busparameters are given in Bit times. The Bit time tBit is the result ofthe reciprocal of the Baud rate: tBit = 1 / Baud rate (Baud rate in Bit/s) The conversion from milliseconds into a Bit time is shown in thefollowing formula:Bit time = Time [milliseconds] * Baud rate.

Ø Click OK to save the set parameters.

orØ Click Cancel to reject the settings.

orØ Click Default to restore the preset default settings.

8.4.3.4 Configuring signals in the Signal Editor

In the Signal Editor, the available signals are displayed hierarchicallywithin a tree structure. The editor allows changing parameters for availablesignals, to erase these and to create new signals manually.

To open the Signal Editor, click Edit button in the Symbolizer or doubleclick the question mark in the Station Address (see positions (12) and (6)in section Acquiring data points (signals) from STEP 7 project file [ page48]).

Figure 34: Signal Editor


© Hilscher 2010 – 2016


Position Column Description(1) This column features the tree structure of the devices, modules and signals.(2) This column features symbols for distinguishing between devices , modules and

signals .(3) Name Name of the STEP 7 program, symbol table or signal.(4) Station

AddressNote: The Station Address is the PROFIBUSMPI address of the S7 component on the buswhich is to be visualized. It can not be extracted out of the STEP 7 project.The value is automatically adjusted to the value 1 when opening the Symbolizer for the firsttime, but must be adjusted to the correct value. Otherwise, no communication will take placebetween the netSCADA device and the S7 component.

(5) Module Type A symbol from the Symbol Table or the Data Blocks.(6) Data Block Number of data block.(7) Access Permitted Access: read, write, read_write(8) Memory Area Memory area(9) Data Type (concerns only signals)(10) Quantity Number of data elements(11) Offset Offset within the memory area(12) Bit Number (if necessary)(13) Alarm Alarm. If checked, this signal is enabled for alarm supervision and will permanently be

supervised by the netSCADA device. For further information, see section Configuringalarms [ page 115].

(14) Trend Trend: If checked, the values of the signal are permanently read and recorded by thenetSCADA device in the trend buffer. For further information, see section Configuringtrending [ page 118].Table 26: Columns in Signal Editor

Position Button Description(15) Add Device Adds a new signal device (S7), when no device exists in the Signal Editor. The button is

grayed out, when a device exists in the Signal Editor.(16) Add Module Adds a new data module.(17) Add Signal Adds a new signal within the selected data module.(18) Remove Deletes the tagged signal object.(19) OK Stores the settings and closes the Signal Editor.(20) Cancel Closes the Signal Editor without storing the settings.

Table 27: Control elements in the Signal Editor

Important:All changes made in this window will be lost, if you import a STEP 7project by using the method described in the section SelectingSTEP 7 project file [ page 46].However, these changes will not be lost, if the dialog for the importof data points of the same S7 project is invoked in the waydescribed in section Acquiring data points (signals) from STEP 7project file [ page 48].

Ø After having configured all signals to be visualized, click OK button toexit the Signal Editor and to take over the signals into your project.


© Hilscher 2010 – 2016


Ê In the project tree of the atvise builder, the signals which have beentaken over are displayed in the OBJECTS folder:

Figure 35: Signals in project tree

ð In area , the references to the data blocks of the imported PLCprogram can be seen. These signals are now available for yourvisualization project.


© Hilscher 2010 – 2016


8.4.4 Creating project for NSCDT52EN/ATVISE/PN (netSCADA forPROFINET)

8.4.4.1 Overview of the necessary steps

To create a visualization project for your NSCDT52EN/ATVISE/PNdevice, you need to perform the following steps:

Configure netSCADA1. Enter a name2. Under Hostname, enter IP address of the netSCADA device3. Under Type, select Hilscher netSCADA PROFINET(NSCDT52EN/ATVISE/PN) entry

4. Assign temporary IP address (Device Setup…)5. Select STEP 7 project6. Configure RFC 1006 Settings

Acquire data points(import and select symbols from STEP 7 program)1. Select variables2. Set access type3. Enter PROFINET address of S74. Add marker, if necessary5. Select variables for trending, if necessary

Create displays and link elements to data points1. Select and place display elements2. Link data points3. Layout display

Generate (compile) displays (i. e. visualization web pages) andtransfer them into the netSCADA device



© Hilscher 2010 – 2016


8.4.4.2 Configuring netSCADA device

A netSCADA device is administered within atvise as webMI Server. Inorder to select and configure the NSCDT52EN/ATVISE/PN as webMIServer, proceed as follows:








© Hilscher 2010 – 2016




2. Enter basic parameters.Ø In the Name field, enter a name for your server (i. e. the netSCADAdevice).

Ø In the Hostname field, enter the IP address (e.g. 10.11.5.98) underwhich the visualization pages of the netSCADA device shall beaccessed via Ethernet LAN and web browser.

Ø In the Type dropdown list, select Hilscher netSCADAPROFINET(NSCDT52EN/ATVISE/PN) entry.

3. Select STEP 7 project file.Ø After having selected the Hilscher netSCADA PROFINET(NSCDT52EN/ATVISE/PN) entry, the SIMATIC S7 Project… button becomesvisible. By clicking this button, you can open a dialog in which you canselect a STEP 7 Project containing the S7 components that you want toimport in order to visualize them. For details, see section SelectingSTEP 7 project file [ page 46].


© Hilscher 2010 – 2016



5. Configure RFC 1006 parameters.Ø Click RFC 1006 Settings… button to open a dialog in which you canconfigure the PROFINET settings of the netSCADA. For details, seesection Configuring PROFINET (RFC 1006) parameters [ page 66].


6. Save webMI Server.Ø After having configured the webMI Server, click OK button to save theparameters of the webMI Server and to close the dialog window.

ð You have configured the netSCADA device as webMI Server.


8.4.4.3 Configuring PROFINET (RFC 1006) parameters

The PROFINET communication parameters can be configured in thePROFINET/RFC1006 dialog window.Ø In the Add webMI Server (respectively Edit webMI Server) dialogwindow, click RFC 1006 Settings… button (see section ConfiguringnetSCADA device [ page 64]).


© Hilscher 2010 – 2016


Ê The PROFINET/RFC1006 dialog window opens:

Figure 38: RFC 1006 parameters

Ø Configure the Modbus parameters.

You can configure the following parameters:Parameter Description Range of Values/ValueConnection Type Type of device used by the neSCADA for identifying itself when

accessing the S7:PG: programming deviceOP: operator panelOther: unspecified deviceIf not specified otherwise in the S7 program, use OP default value.

PGOPOther

Rack Address of rack used by the neSCADA for identifying itself whenaccessing the S7.If not specified otherwise in the S7 program, use 0 default value.

0 … 7Default: 0

Slot Address of slot used by the neSCADA for identifying itself whenaccessing the S7.If not specified otherwise in the S7 program, use 0 default value.

0 … 31Default: 0

Max. wait time foranswer

Timeout value in milliseconds. Defines the maximum waiting time ofthe netSCADA for an answer from the S7.

0 ... 106217308Default: 1000 ms

IP Address IP address of the netSCADA device within the PROFINET LAN.Select Enable checkbox to enter a suitable IP address here.

Default: 192.168.0.134

Netmask Network mask of the netSCADA device within the PROFINET LAN.Select Enable checkbox to enter mask parameters here. Note: When using a manually configured IP address you must alsospecify and enable the net mask.

Default: 255.255.255.0

Gateway IP address of the gateway within the PROFINET LAN (if existing).Select Enable checkbox and enter the gateway address here if thenetSCADA shall be able to communicate outside the PROFINETLAN.

Default: 0.0.0.0

Extras If the netSCADA device shall receive its IP address within thePROFINET LAN from a BootP or DHCP server (if available), youcan select the corresponding option here. If you select the BootP orDHCP option, the manually configured IP address will be disabled.

Default: BootP and DHCP optiondisabled

Table 28: PROFINET/RFC 1006 Parameters


© Hilscher 2010 – 2016


Click OK to save the set parameters.

Click Cancel to reject the settings.

Click Default to restore the preset default settings.

8.4.4.4 Configuring signals in the Signal Editor

In the Signal Editor, the available signals are displayed hierarchicallywithin a tree structure. The editor allows changing parameters for availablesignals, to erase these or to create new signals manually.Ø To open the Signal Editor, click Edit button in the Symbolizer dialogwindow (see position (12) in section Acquiring data points (signals) fromSTEP 7 project file [ page 48]).

Ê The Signal Editor opens:

Figure 39: Signal Editor

Position Column Description(1) This column features the tree structure of the devices, modules and signals.(2) This column features symbols for distinguishing between devices , modules and

signals .(3) Name Name of the STEP 7 program, symbol table or signal.(4) Station

AddressEnter here the IP address of the S7 component of the PROFINET LAN which is to beaccessed by the visualization.Note: The address cannot be extracted out of the STEP 7 project and is thus automaticallyset to value 0.0.0.0 when the project is opened in the Symbolizer for the first time.

(5) Rack Address of the rack which is to be accessed by the visualization.(6) Slot Address of the slot which is to be accessed by the visualization.(7) Module Type A symbol from the Symbol Table or the Data Blocks.(8) Data Block Number of data block.(9) Access Permitted Access: read, write, read_write(10) Memory Area Memory area(11) Data Type (concerns only signals)(12) Quantity Number of data elements(13) Offset Offset within the memory area


© Hilscher 2010 – 2016


Position Column Description(14) Bit Number (if necessary)(15) Alarm Alarm. If checked, this signal is enabled for alarm supervision and will permanently be

supervised by the netSCADA device. For further information, see section Configuringalarms [ page 115].

(16) Trend Trend: If checked, the values of the signal are permanently read and recorded by thenetSCADA device in the trend buffer. For further information, see section Configuringtrending [ page 118].Table 29: Columns in Signal Editor

Position Button Description(17) Add Device Adds a new signal device (S7), when no device exists in the Signal Editor. The button is

grayed out, when a device exists in the Signal Editor.(18) Add Module Adds a new data module.(19) Add Signal Adds a new signal within the selected data module.(20) Remove Deletes the tagged signal object.(21) OK Stores the settings and closes the Signal Editor.(22) Cancel Closes the Signal Editor without storing the settings.

Table 30: Control elements in the Signal Editor

Important:All changes made in this window will be lost if you import a STEP 7project by using the method described in the section SelectingSTEP 7 project file [ page 46].However, these changes will not be lost if the dialog for the importof data points of the same S7 project is invoked in the waydescribed in section Acquiring data points (signals) from STEP 7project file [ page 48].

Ø After having configured all signals to be visualized, click OK button toexit the Signal Editor and to take over the signals into your project.


© Hilscher 2010 – 2016


Ê In the project tree of the atvise builder, the signals which have beentaken over (i. e. the references to the data blocks of the imported PLCprogram) are displayed in the OBJECTS folder:


ð The signals are now available for your visualization project.


© Hilscher 2010 – 2016


8.5 Creating project for NSCDT52EN/ATVISE/OMB (netSCADAfor Modbus TCP)

8.5.1 Overview of the necessary stepsTo create a visualization project for your NSCDT52EN/ATVISE/OMBdevice, you need to perform the following steps:

Configure netSCADA1. Enter a name in the Name field2. Under Hostname, enter die IP address of the netSCADA device3. Under Type select Hilscher netSCADA Modbus TCPServer(NSCDT52EN/ATVISE/OMB) entry or HilschernetSCADA Modbus TCP Client(NSCDT52EN/ATVISE/OMB)entry, depending on whether you intend to use the device asmaster (client) or slave (server).

4. Assign temporary IP address (Device Setup…)5. Configure Modbus Settings (Modbus TCP Settings…)6. Optional: import symbol file containing preconfigured signals to bevisualized (Import Symbol File…)

Select signals in Signal Editor1. Select Modbus node2. Select signals and configure parameters3. Optional: add alarm for signal4. Optional: select trending function for signal

Create displays and link display elements to data points1. Select and place display elements2. Link data points3. Layout display

Generate (compile) displays (i. e. visualization web pages) andtransfer them into the netSCADA



© Hilscher 2010 – 2016


8.5.2 Configuring netSCADA deviceA netSCADA device is administered within atvise as webMI Server. Inorder to select and configure the NSCDT52EN/ATVISE/OMB as webMIServer, proceed as follows:








© Hilscher 2010 – 2016



Figure 42: webMI Server Dialog


Ø In the Hostname field, enter the IP address (e.g. 10.11.5.98) underwhich the visualization pages of the netLINK SCADA shall be accessedvia Ethernet LAN and web browser

Ø In the Type dropdown list, select Hilscher netSCADA Modbus TCPServer (NSCDT52EN/ATVISE/OMB) or Hilscher netSCADAModbus TCP Client (NSCDT52EN/ATVISE/OMB) entry, dependingon whether you intend to use the device as master (= “client”) or slave(= “server”).



© Hilscher 2010 – 2016


4. Configure MODBUS TCP parameters.Ø Click Modbus TCP Settings… button to open a dialog in which you canconfigure the MODBUS TCP settings of the netSCADA device. Fordetails, see section Configuring Modbus TCP parameters [ page 75].

5. Import Symbol File (optional).Ø If stored in a CSV (comma separated values) text file, you can importlists or tables of preconfigured Modbus signals into your webMI Serverproject by clicking the Import Symbol File… button. Details on this canbe found in section Importing Modbus signals from “symbol file” (CSVtext file) [ page 95]. As an alternative, you can define (respectively configure) all signalsintended for visualization manually in the Signal Editor. Details on thiscan be found in the Configuring signals in the Signal Editor [ page77]section.






© Hilscher 2010 – 2016


8.5.3 Configuring Modbus TCP parametersThe MODBUS TCP communication parameters can be configured in theModbus TCP/IP dialog window.Ø In the Add webMI Server (respectively Edit webMI Server) dialogwindow, click Modbus TCP Settings… button (see section ConfiguringnetSCADA device [ page 72]).

Ê The Modbus TCP/IP dialog window opens:

Figure 43: Modbus TCP parameters dialog for client

Ø Configure the Modbus parameters.


© Hilscher 2010 – 2016


You can configure the following parameters:Parameter Description Range of Values/ValueProtocol Mode Determines the role of the device within the Modbus.

This field is preset according to the device type which you havechosen in the webMI Server dialog window (Server or Client).

ServerClient

Client ConnectionWatchdog Time

Only for client jobs in Message Mode (packet mode): The connection to the destinationdevice stays open until timeoutis expired. This timeout starts after receiving the answer to acommand. For interface programming via Open Modbus/TCP, the value forClient Connection Watchdog Time (Omb Open Time) must bedivided by the factor of 100. (Value range for the interfaceprogramming: 1 ... 60,000).Note: This parameter can be set only in Client protocol mode.

100 … 6,000,000 msDefault: 1,000 ms

Response timeout Only for client jobs in Message Mode (packet mode): After expiration of this time, the job will be canceled and an error issend to the application. This timeout starts after command is sendto the destination device via TCP.For interface programming via Open Modbus/TCP, the value forResponse timeout must be divided by the factor of 100. (Valuerange for the interface programming: 1 ... 60,000).Note: This parameter can be set only in Client protocol mode.

100 … 6,000,000 msDefault: 2,000 ms

SendAcknowledgementTimeout

Parameter for TCP task (in milliseconds). Used internally by theOMB task. Specifies the timeout for trying to send messages viaTCP/IP.

0 … 2,000,000,000 msDefault: 31,000 ms

ConnectAcknowledgementTimeout

Parameter for TCP task (in milliseconds). Used internally by theOMB task. Specifies the timeout for trying to establish aconnection via TCP/IP.

0 … 2,000,000,000 msDefault: 31,000 ms

CloseAcknowledgementTimeout

Parameter for TCP task (in milliseconds). Used internally by theOMB task. Specifies the timeout for trying to close a TCP/IPconnection.

0 … 2,000,000,000 msDefault: 13,000 ms

IP Address IP address of the netSCADA device within the PROFINET LAN.Select Enable checkbox to enter a suitable IP address here.

Default: 192.168.0.134

Netmask Network mask of the netSCADA device within the PROFINETLAN. Select Enable checkbox to enter mask parameters here. Note: When using a manually configured IP address you mustalso specify and enable the net mask.

Default: 255.255.255.0

Gateway IP address of the gateway within the PROFINET LAN (if existing).Select Enable checkbox and enter the gateway address here ifthe netSCADA shall be able to communicate outside thePROFINET LAN.

Default: 0.0.0.0

Extras If the netSCADA device shall receive its IP address within thePROFINET LAN from a BootP or DHCP server (if available), youcan select the corresponding option here. If you select the BootPor DHCP option, the manually configured IP address will bedisabled.

Default: BootP and DHCP optiondisabled

Table 31: Modbus TCP/IP Parameters

Click OK to save the set parameters.

Click Cancel to reject the settings.

Click Default to restore the preset default settings.


© Hilscher 2010 – 2016


8.5.4 Configuring signals in the Signal EditorThis section describes how to configure the signals you want to visualize.

1. Open Signal Editor.Ø In the project tree of the atvise builder, select the netSCADA devisewhich you have configured as your webMI Server (see sectionConfiguring netSCADA device [ page 72]), then use the right mousebutton to open the context menu and choose Acquire Datapoints.


Or:Ø As an alternative, you can choose Guided Actions > Import allvariables from the menu bar of the atvise builder and then select thethe netSCADA device which you have configured as your webMIServer.

Figure 45: Open Signal Editor

Ê The Signal Editor opens. The parameters of a Modbus Client (i. e.“master”) differ from the parameters of a Modbus Server (i. e. “slave”):


© Hilscher 2010 – 2016


Modbus TCP/IP Client

Figure 46: Signal Editor Modbus TCP/IP Client

2. Configure the signals which you want to visualize.Ø Click Add Device button, to add a Modbus node containing the signalswhich you want to visualize.

Ø In the Station Address field, enter the IP address of the Modbus node.Ø Click Add Unit button to add a module (i. e. structuring element) to theModbus node.

Ø In the Unit field, enter the ID of the module (i. e. of the “Unit”). This fieldmust be filled. If not specified otherwise, leave the parameter at defaultvalue 0.

Ø Click Add Signal button to add a signal that you want to visualize.Ø Then proceed to configure the Memory Area, Address and Quantity ofthe signal which you want to visualize. If you want to use the Alarm(alarm surveillance) or Trend (trend recording) functions for this signal,activate the corresponding check box.


© Hilscher 2010 – 2016


The Signal Editor features the following elements:Column Description The first column features the tree structure of the Modbus nodes, units

and signals. The second column features symbols for distinguishing between

Modbus nodes (devices) , units and signals .Name Name of the Modbus node, unit or signal. This field can be edited.Station Address Address of the Modbus node within the TCP/IP network. This field can

be edited.Unit ID of the subordinate unit (a.k.a. “module”) of the Modbus node.

Value range: 0 … 247Default: 0

Signal Type Signal types: read access (read), read and write access (read_write). Depends on the selected Memory Area.

Memory Area Memory area of the signal to be visualized:Discrete Input: single bit, read (readonly)Coils: single bit, read_write (read/write)Input Register: 16bit word, read (readonly)Holding Register: 16bit word, read_write (read/write)

Address Address of the signal to be visualized (relative register or bit positionwithin the selected Memory Area). This field can be edited.

Quantity Quantity of data elements. Depends on the selected Memory Area.Alarm Alarm: If checked, this signal is enabled for alarm supervision and will

permanently be supervised by the netSCADA device. For furtherinformation, see section Configuring alarms [ page 115].

Trend Trend: If checked, the values of the signal are permanently read andrecorded by the netSCADA device in the trend buffer. For furtherinformation, see section Configuring trending [ page 118].

Table 32: Columns in Signal Editor Modbus TCP/IP Client

Button DescriptionAdd Device Adds a new Modbus node.Add Unit Adds a new unit (module).Add Signal Adds a new signal within the selected unit/module.Remove Deletes a selected item.OK Closes the Signal Editor and takes over the signals into your project.Cancel Closes the Signal Editor without taking over the signals.Table 33: Control elements in the Signal Editor

3. Store signals.Ø After having configured all signals to be visualized, click OK button toexit the Signal Editor and to take over the signals into your project.


© Hilscher 2010 – 2016




Ê These signals are now available for your visualization project.

Modbus TCP/IP Server

Figure 48: Signal Editor Modbus TCP/IP Server

Configure the signals which you want to visualize.

Note:A netSCADA device that is being used as Modbus Server (i. e.slave device) can only visualize its own signals, not those of theother Modbus nodes. Therefore, you cannot add any other devicesin this editor (the Add Device button is deactivated); you can onlyadd and configure the signals of your own netSCADA device here.


© Hilscher 2010 – 2016


Ø Click Add Signal button, to add a signal that you want to visualize.Ø Then proceed to configure the Memory Area, Address and Quantity ofthe signal which you want to visualize. If you want to use the Alarm(alarm surveillance) or Trend (trend recording) functions for this signal,activate the corresponding check box.

The Signal Editor features the following elements:Column Description The first column features the tree structure of the Modbus nodes, signal

groups and signals. The second column features symbols for distinguishing between

Modbus nodes (devices) , signal groups and signals .Name Name of the Modbus node, signal group or signal. This field can be

edited.Signal Type Signal types: read access (read), read and write access (read_write).

Depends on the selected Memory Area.Memory Area Memory area of the signal to be visualized:

Discrete Input: single bit, read_write (read/write)Coils: single bit, read (readonly)Input Register: 16bit word, read_write (read/write)Holding Register: 16bit word, read (readonly)


Quantity Quantity of data elements. Depends on the selected Memory Area.Alarm Alarm. If checked, this signal is enabled for alarm supervision and will



Table 34: Columns in Signal Editor Modbus TCP/IP Server

Button DescriptionAdd Device DeactivatedAdd Signal Group Adds a new signal group.Add Signal Adds a new signal within the selected signal group.Remove Deletes a selected item.OK Closes the Signal Editor and takes over the signals into your project.Cancel Closes the Signal Editor without taking over the signals.Table 35: Control elements in the Signal Editor

Store signals.Ø After having configured all signals to be visualized, click OK button toexit the Signal Editor and to take over the signals into your project.


© Hilscher 2010 – 2016




ð These signals are now available for your visualization project.


© Hilscher 2010 – 2016


8.6 Creating project for NSCDT52RS/ATVISE/MBR (netSCADAfor Modbus RTU)

8.6.1 Overview of the necessary stepsTo create a visualization project for your NSCDT52RS/ATVISE/MBRdevice, you need to perform the following steps:

Configure netSCADA1. Enter a name2. Under Hostname, enter die IP address of the netSCADA device3. Under Type select Hilscher Modbus RTU Master (NSCDT52RS/ATVISE/MBR) entry or Hilscher Modbus RTU Slave (NSCDT52RS/ATVISE/MBR) entry, depending on whether you intend touse the device as master or slave device.

4. Assign temporary IP address (Device Setup…)5. Configure Modbus RTU settings (Modbus Settings…)6. Optional: import symbol file containing preconfigured signals to bevisualized (Import Symbol File…)

Select signals in Signal Editor1. Select Modbus node2. Select signals and configure parameters3. Optional: add alarm for signal4. Optional: select trending function for signal

Create displays and link display elements to data points1. Select and place display elements2. Link data points3. Layout display

Generate (compile) displays (i. e. visualization web pages) andtransfer them into the netSCADA device



© Hilscher 2010 – 2016


8.6.2 Configuring netSCADA deviceA netSCADA device is administered within atvise as webMI Server. Inorder to select and configure the NSCDT52RS/ATVISE/MBR as webMIServer, proceed as follows:








© Hilscher 2010 – 2016



Figure 51: webMI Server Dialog


Ø In the Hostname field, enter the IP address (e.g. 10.11.5.98) underwhich the visualization pages of the netSCADA device shall beaccessed via Ethernet LAN and web browser.

Ø In the Type dropdown list, select Hilscher netSCADA Modbus RTUMaster (NSCDT52RS/ATVISE/MBR) or Hilscher netSCADAModbus RTU Slave (NSCDT52RS/ATVISE/MBR) entry, dependingon whether you intend to use the device as master or slave.


4. Configure MODBUS RTU parameters.Ø Click Modbus Settings… button to open a dialog in which you canconfigure the MODBUS RTU settings of the netSCADA device. Fordetails, see section Configuring Modbus RTU parameters [ page 87].


© Hilscher 2010 – 2016


5. Import Symbol File (optional).Ø If stored in a CSV (comma separated values) text file, you can importlists or tables of preconfigured Modbus signals into your webMI Serverproject by clicking the Import Symbol File… button. Details on this canbe found in section Importing Modbus signals from “symbol file” (CSVtext file) [ page 95]. As an alternative, you can define (respectively configure) all signalsintended for visualization manually in the Signal Editor. Details on thiscan be found in the Configuring signals in the Signal Editor [ page 77]section.






© Hilscher 2010 – 2016


8.6.3 Configuring Modbus RTU parametersThe MODBUS communication parameter can be configured in the ModbusRTU dialog window.Ø In the Add webMI Server (respectively Edit webMI Server) dialogwindow, click Modbus Settings… button (see section ConfiguringnetSCADA device [ page 84]).

Ê The Modbus RTU dialog window opens:

Figure 52: Modbus parameter dialog for master device

Ø Set the parameters according to the configuration of your Modbusnetwork.

The subsequent table describes the parameters in detail:Parameter Description Range of Values/

ValueProtocol Mode Determines the role of the device as master or slave within the Modbus.

This field is preset according to the device type which you have chosenin the webMI Server dialog window.

MasterSlave

Response Timeout Timeout value in milliseconds. Defines the maximum waiting time of themaster for an answer from the slave.Can only be selected if Protocol Mode is set to Master.

10 … 10000 msDefault: 1000 ms

Modbus Address Defines the address of the netSCADA device in the Modbus. 1 ... 247Default: 2

Send Retries Defines the number of telegram retries when the connection isinterrupted or other transmission errors occur.Can only be selected if Protocol Mode is set to Master.

0 … 10Default: 3

Interface type Serial interface type to be used by the netSCADA device in the Modbus. RS 232RS 485RS 422

RTS Control Signal „Request To Send“ can be switched on or off.Can only be selected if Interface type is set to RS 232.

RTS Control OffRTS Control OnDefault: Off


© Hilscher 2010 – 2016


Parameter Description Range of Values/Value

Baud Rate Modbus RTU network Baud rate in Bits per second. 1200240048009600192003840057600115200Default: 9600

Stop Bits Defines the quantity of stop bits to be used in protocol for serial datacommunication.

12Default: 1

Parity Defines the parity bit for serial data communication. NoneEvenOdd Default: Even

Table 36: Parameters Modbus RTU

Ø Click OK to save the set parameters.

orØ Click Cancel to reject the settings.

orØ Click Default to restore the preset default settings.


© Hilscher 2010 – 2016


8.6.4 Configuring signals in the Signal EditorThis section describes how to configure the signals you want to visualize.

1. Open Signal Editor.Ø In the project tree of the atvise builder, select the netSCADA devisewhich you have configured as your webMI Server (see sectionConfiguring netSCADA device [ page 84]), then use the right mousebutton to open the context menu and choose Acquire Datapoints.


Or:Ø As an alternative, you can choose Guided Actions > Import allvariables from the menu bar of the atvise builder and then select thethe netSCADA device which you have configured as your webMIServer.

Figure 54: Open Signal Editor


© Hilscher 2010 – 2016


Ê The Signal Editor opens. The parameters of a Modbus RTU Masterdiffer from the parameters of a Modbus RTU Slave.

Modbus RTU Master

Figure 55: Signal Editor Modbus RTU Master

2. Configure the signals which you want to visualize.Ø Click Add Device button, to add a Modbus node containing the signalswhich you want to visualize.

Ø In the Station Address field, enter the station address of the Modbusnode.

Ø Click Add Signal Group button to add a signal group (i. e. structuringelement) to the Modbus node.

Ø Click Add Signal button, to add a signal which you want to visualize.Ø Then proceed to configure the Memory Area, Address and Quantityparameters of the signal which you want to visualize. If you want to usethe Alarm (alarm surveillance) or Trend (trend recording) functions forthis signal, activate the corresponding check box.


© Hilscher 2010 – 2016


The Signal Editor features the following elements:Column Description The first column features the tree structure of the Modbus nodes,

signal groups and signals. The second column features symbols for distinguishing between

Modbus nodes (devices) , signal groups and signals .Name Name of the Modbus node, signal group or signal. This field can be

edited.Station Address Address of the Modbus node. This field can be edited.Signal Type Signal types: read access (read), read and write access (read_write).


Discrete Input: single bit, read (readonly)Coils: single bit, read_write (read/write)Input Register: 16bit word, read (readonly)Holding Register: 16bit word, read_write (read/write)


Quantity Quantity of data elements. Depends on the selected Memory Area.Alarm Alarm. If checked, this signal is enabled for alarm supervision and will



Table 37: Columns in Signal Editor Modbus RTU Master

Button DescriptionAdd Device Adds a new Modbus node.Add Signal Group Adds a new signal group.Add Signal Adds a new signal within the selected data module.Remove Deletes a selected item.OK Closes the Signal Editor and takes over the signals into your project.Cancel Closes the Signal Editor without taking over the signals.Table 38: Control elements in the Signal Editor



© Hilscher 2010 – 2016





Modbus RTU Slave

Figure 57: Signal Editor Modbus RTU Slave

Configure the signals which you want to visualize.


© Hilscher 2010 – 2016


Note:A netSCADA device that is being used as Modbus RTU Slave canonly visualize its own signals, not those of the other Modbus nodes.Therefore, you cannot add any other devices in this editor (the AddDevice button is deactivated); you can only add and configure themodules and signals of your own netSCADA device here.

Ø Click Add Signal button, to add a signal that you want to visualize.Ø Then proceed to configure the Memory Area, Address and Quantityparameters of the signal which you want to visualize. If you want to usethe Alarm (alarm surveillance) or Trend (trend recording) functions forthis signal, activate the corresponding check box.

The Signal Editor features the following elements:Column Description The first column features the tree structure of the Modbus nodes, signal

groups and signals. The second column features symbols for distinguishing between Modbus

nodes (devices) , signal groups and signals .Name Name of the Modbus node, signal group or signal. This field can be

edited.Signal Type Signal types: read access (read), read and write access (read_write).


Discrete Input: single bit, read_write (read/write)Coils: single bit, read (readonly)Input Register: 16bit word, read_write (read/write)Holding Register: 16bit word, read (readonly)


Quantity Quantity of data elements. Depends on the selected Memory Area.Alarm Alarm: If checked, this signal is enabled for alarm supervision and will



Table 39: Columns in Signal Editor Modbus RTU Slave

Button DescriptionAdd Device DeactivatedAdd SignalGroup

Adds a new signal group.

Add Signal Adds a new signal within the selected signal group.Remove Deletes a selected item.OK Closes the Signal Editor and takes over the signals into your project.Cancel Closes the Signal Editor without taking over the signals.Table 40: Control elements in the Signal Editor



© Hilscher 2010 – 2016


8.7 Importing Modbus signals from “symbol file” (CSV text file)

8.7.1 OverviewIf you are using netSCADA Modbus devices NSCDT52EN/ATVISE/OMB(netSCADA for Modbus TCP) or NSCDT52RS/ATVISE/MBR (netSCADAfor Modbus RTU), you can import lists or tables of Modbus signals whichyou want to visualize, on condition that they are stored in text files in CSVformat (comma separated values).

The Symbolizer allows you to further select imported symbols, which canafterwards be reconfigured in the Signal Editor, if necessary.

The mandatory structures of the CSV files are described in sectionStructure of CSV symbol file [ page 95], instructions on how to import thefiles are given in section Importing symbol file [ page 103].

8.7.2 Structure of CSV symbol fileThe values and parameters of the Modbus signals must be stored in thesymbol file as comma separated values (CSV) in a predefined order,otherwise the data cannot be properly imported.

The structure of a CSV text file basically corresponds to the structure of asimple table: each set of data is represented in one line, in which individualparameters are separated from each other by semicolons (instead of beingseparated by the columns of a table). The first line functions as “tableheader”. In each following line, the first value relates to the first column ofthe “table header” (i. e. to the first parameter), the second value (separatedfrom the first value by a semicolon) relates to the second column header,and so on.

Note:The first line (“table header”) with the parameter names is ignoredduring the import process. It serves for a better overview of thestructure of the CSV and can be omitted.Only lines beginning with the digits 1, 2 or 3 (these are the validvalues of the Type parameter) will be imported.


© Hilscher 2010 – 2016


Example

Example of a CSV text file containing signal parameters for Modbus TCPClient:

Figure 59: CSV text file

The text file depicted as table (e. g. in Excel):

Figure 60: CSV depicted as table in Excel

After import into atvise, the values of the CSV file will be interpreted by theSignal Editor as follows:

Figure 61: Values of CSV file in Signal Editor


© Hilscher 2010 – 2016


Parameters of CSV file for Modbus TCP Client

For Modbus TCP Client, the CSV file features the following parameters andvalue ranges:

Parameter Positionwithineach line

Description Range of values Corresponds toparameter (column) inSignal Editor

Type 1 Defines to which of the Modbusentities (i. e. node, unit or signal)the data set (i. e. the line) isrelated.

1 = Modbus node(device)2 = Unit

3 = Signal

Corresponds to structuretree and symbols:

= Modbus node

= Unit

= SignalName 2 Defines the name of the Modbus

entity to which the data set (i. e. theline) is related.

Can be freely chosen, e. g. Device_xy for aModbus node orSignal_xy for asignal

Name

Station Address 3 If Type = 1 (= Modbus node):IP address of the Modbus nodewithin the TCP/IP network.If Type = 2 (= Unit):ID of the subordinate unit (a.k.a.“module”) of the Modbus node.If Type = 3 (= Signal) theparameter must be empty (justsemicolon).

If Type = 1 (= Modbusnode) e. g.10.11.5.39

If Type = 2 (= Unit):0...247Default: 0

If Type = 1 (= Modbusnode): Station AddressIf Type = 2 (= Unit): Unit

Memory Area 4 If Type = 1 (= Modbus node) orType = 2 (= Unit), the parametermust be empty (just semicolon).If Type = 3 (= Signal), define herethe memory area of the signal to bevisualized.

0 = Discrete Input(single bit, readonly)1 = Coils (single bit,read/write)2 = Input Register (16bit word, readonly)3 = Holding Register(16 bit word, read/write)

Memory AreaNote: The parameterSignal type is defined bythe value in the MemoryArea.

MemoryAddress

5 If Type = 1 (= Modbus node) orType = 2 (= Unit), the parametermust be empty (just semicolon).If Type = 3 (= Signal), define herethe address of the signal to bevisualized (relative register or bitposition within the selectedMemory Area).

0…65535 Address

Quantity 6 If Type = 1 (= Modbus node) orType = 2 (= Unit), the parametermust be empty (just semicolon).If Type = 3 (= Signal) define herethe quantity of data elements.

Depends on theselected Memory Area.

Quantity

Alarm 7 If Type = 1 (= Modbus node) orType = 2 (= Unit), the parametermust be empty (just semicolon).If Type = 3 (= Signal), enable herealarm supervision for the signal.

0 = alarm supervisiondisabled1 = alarm supervisionactivated

Alarm(Checkbox)


© Hilscher 2010 – 2016




Trend 8 If Type = 1 (= Modbus node) orType = 2 (= Unit), the parametermust be empty (just semicolon).If Type = 3 (= Signal), enable heretrending (reading and buffering ofvalues) for the signal.

0 = trending disabled

1 = trending activated

Trend(Checkbox)

Table 41: CSV file for Modbus TCP Client


© Hilscher 2010 – 2016


Parameters of CSV file for Modbus TCP Server

For Modbus TCP Server, the CSV file features the following parametersand value ranges:




1 = Modbus node(device)2 = Signal group

3 = Signal


= Modbus node

= Signal group




Name

Memory Area 3 If Type = 1 (= Modbus node) orType = 2 (= Signal group), theparameter must be empty (justsemicolon).If Type = 3 (= Signal), define herethe memory area of the signal to bevisualized.

0 = Discrete Input(single bit, read/write)1 = Coils (single bit,readonly)2 = Input Register (16bit word, read/write)3 = Holding Register(16 bit word, readonly)


MemoryAddress

4 If Type = 1 (= Modbus node) orType = 2 (= Signal group), theparameter must be empty (justsemicolon).If Type = 3 (= Signal), define herethe address of the signal to bevisualized (relative register or bitposition within the selectedMemory Area).

Register: 0…5760

Coils: 0…46080

Address

Quantity 5 If Type = 1 (= Modbus node) orType = 2 (= Signal group), theparameter must be empty (justsemicolon).If Type = 3 (= Signal) define herethe quantity of data elements.


Quantity

Alarm 6 If Type = 1 (= Modbus node) orType = 2 (= Signal group), theparameter must be empty (justsemicolon).If Type = 3 (= Signal), enable herealarm supervision for the signal.


Alarm(Checkbox)

Trend 7 If Type = 1 (= Modbus node) orType = 2 (= Signal group), theparameter must be empty (justsemicolon).If Type = 3 (= Signal), enable heretrending (reading and buffering ofvalues) for the signal.



Trend(Checkbox)

Table 42: CSV file for Modbus TCP Server


© Hilscher 2010 – 2016


Parameters of CSV file for Modbus RTU Master

For Modbus RTU Master, the CSV file features the following parametersand value ranges:





3 = Signal


= Modbus node

= Signal group




Name

Station Address 3 If Type = 1 (= Modbus node):Address of the Modbus node.If Type = 2 (= Signal group) orType = 3 (= Signal), the parametermust be empty (just semicolon).

1…255 Station Address


0 = Discrete Input(single bit, readonly)1 = Coils (single bit,read/write)2 = Input Register (16bit word, readonly)3 = Holding Register(16 bit word, read/write)


MemoryAddress


0…65535 Address



Quantity



Alarm(Checkbox)


© Hilscher 2010 – 2016







Trend(Checkbox)

Table 43: CSV file for Modbus RTU Master


© Hilscher 2010 – 2016


Parameters of CSV file for Modbus RTU Slave

For Modbus RTU Slave, the CSV file features the following parameters andvalue ranges:



Type 1 Defines to which of the Modbusentities the data set (i. e. the line) isrelated.


3 = Signal


= Modbus node

= Signal group




Name


0 = Discrete Input(single bit, read/write)1 = Coils (single bit,readonly)2 = Input Register (16bit word, read/write)3 = Holding Register(16 bit word, readonly)


MemoryAddress


Register: 0…5760

Coils: 0…46080

Address



Quantity



Alarm(Checkbox)




Trend(Checkbox)

Table 44: CSV file for Modbus RTU Slave


© Hilscher 2010 – 2016


8.7.3 Importing symbol fileIn order to import the symbol file, you have to open the webMI Serverconfiguration dialog window. The webMI Server configuration dialog iseither called Add webMI Server or Edit webMI Server – depending onwhether or not you have already created a webMI Server.

1. Open webMI Server configuration dialog window.Ø If you want to import the symbol file into a webMI Server which has notbeen created yet, select Servers entry in the project tree of the atvisebuilder and choose Add Server… > WebMI from the context menu.

Figure 62: Add server

Or:Ø If you want to import the symbol file into an already existing webMIServer, open Servers folder in the project tree of the atvise builder andselect the corresponding webMI Server entry. Then choose Edit Server… from the context menu (or doubleclickwebMI Server entry).

Figure 63: Edit server


© Hilscher 2010 – 2016


Ê The webMI Server configuration dialog window Add webMI Server,respectively Edit webMI Server opens:

Figure 64: webMI Server configuration dialog window

Note:If you want to import the symbol file into a newly created webMIServer, you should first configure the webMI server as described insection Configuring netSCADA device [ page 72], respectivelyConfiguring netSCADA device [ page 84].

2. Open symbol file.

Note:Examples of symbol files can be found on the netSCADA SolutionsDVD in the Supplements & Examples\Example Projects\NSCDT52RS_ATVISE_XXX(xxx)\Example Symbol Filedirectory.

Ø Click Import Symbol File… button.


© Hilscher 2010 – 2016


Ê The file selection dialog window opens:

Figure 65: File selection dialog

Ø Select the file you want to import, then click Open button.

Note:If your symbol file is stored as text file carrying a .txt extension,select All Files (*.*) from the Files of type dropdown list inorder to make the file visible.

Ê The File selection dialog closes, and you are back in the webMI Serverconfiguration dialog window.

Ø In the webMI Server configuration dialog window, click OK button.Ê The webMI Server configuration dialog window closes, and you areback in the atvise builder.


© Hilscher 2010 – 2016


3. Use the Symbolizer to select nodes and signals to be visualized.Ø In the Servers folder in project tree of the atvise builder, select yourwebMI Server, then choose Acquire Datapoints from the contextmenu.

Figure 66: Open Symbolizer

Ê The Symbolizer opens:

Figure 67: Symbolizer

Ø In the Available Signals field, select from the symbol file the elementswhich you want to visualize, then click > button (in the center of thewindow) to take over the elements into the Customized Signals field.

Note:Only signals taken over into the Customized Signals field will beavailable in atvise as variables for visualization.


© Hilscher 2010 – 2016


Figure 68: Select signals

Ø If you want to change the configuration of the selected signals, clickEdit button in order to open the Signal Editor. Further information onediting/configuring signals can be found in sections Configuring signalsin the Signal Editor [ page 77] respectively Configuring signals in theSignal Editor [ page 89].

Or:Ø If you want to keep the signal configuration the way it was defined in thesymbol file, click Apply button, then OK button.

Ê The signals are being imported. After successful import, a messageappears:

Figure 69: Symbols imported

Ø Acknowledge the message by clicking OK button.ð You have imported Modbus signals from your symbol file.


© Hilscher 2010 – 2016


8.8 Creating the visualization (designing the displays)

8.8.1 OverviewThis section describes how to use the display editor of the atvise builder todesign the web pages of your visualization project, which later will berunning in the netSCADA device. This design process involves theselection and positioning of readymade display elements according to yourideas and requirements. It also involves the assignment of the signals/datapoints which are to be visualized and which are provided by the S7respectively the Modbus nodes connected to the netSCADA device.

8.8.2 Default displaysAn atvise display is a unit that will later be turned into a visualization webpage. Each visualization project can contain several displays/web pages.Displays are stored in the project tree of the atvise builder in the DISPLAYfolder below your netSCADA project (i. e. below the netSCADA configuredas webMI server):

Figure 70: Main Display

Each newly added webMI server automatically contains four folders forstoring new displays. It also contains a Default template and a displaycalled Main. Please note, that the Main display is the mandatory start pageof your visualization project. After having downloaded the project to yourdevice, the Main display will always be the first page that opens when youconnect to the device via Ethernet IP. Thus, the Main display is alwaysused as start page of the visualization.


© Hilscher 2010 – 2016


8.8.3 Creating displaysTo create a new display, proceed as follows:Ø In the project tree of the atvise builder, select the DISPLAYS folder (ifyou want to store the new display on the first level of the DISPLAYSfolder), or select one of the subordinate DISPLAYS folders in which youwant to store the new display.

Ø Then use the right mouse button to open the context menu and chooseAdd Display…

Figure 71: Create new graphic display

Ê The Name of Display dialog opens:

Figure 72: Name of display dialog

Ø Enter a name for your display, e. g. „Display 1“, then click OK button.


© Hilscher 2010 – 2016


Ê The new display has been added to the project tree:

Figure 73: New display in project tree

Ø To fill your display with content, doubleclick the display entry in theproject tree.

ð The display editor of atvise opens. You can now begin to design yourdisplay.

Use the online help of the atvise builder for instructions on how todesign a display and on how to assign user rights.


© Hilscher 2010 – 2016


8.8.4 GUI of the display editor

Figure 74: Graphics editor of atvise builder

The display (or graphics) editor is divided into five main areas:

· Project tree area

· Drawing tools area

· Drawings area

· Library (display elements area)

· Attributes area (properties of the selected display element)

The Library contains many readymade display elements, which can beused instantly. The following types of elements are available:· Analog controls· Analog meters· Default displays (designed for output and input of boolean, numeric andstring data)

· Digital controls· Digital indicators· General displays


© Hilscher 2010 – 2016


Note:The predefined display elements stored in the ATVISEPluginfolder of the library support more data types than the displayelements stored in the standard ATVISE folder. It is thereforerecommended to use the elements stored in the ATVISEPluginfolder.

8.8.5 Adding display elements and assigning signalsThis section describes how to add an element to your display (e. g. forshowing a simple value of a numeric input/output signal):

1. Select and place element.

Ø In the Library area (see position in section GUI of the display editor [ page 111]) open the ATVISE > Default > Number folder (as analternative, you can open the ATVISEPlugin > Default > Numberfolder).

Figure 75: Select element


© Hilscher 2010 – 2016


Ø Select the In/Out Value element and drag and drop into the drawingarea. Place it onto the display at the intended position.

Figure 76: Drag and drop element onto the display

2. Assign a signal to the element.Ø In the drawing area, select the In/Out Value element, then in theAttributes area, click the pink highlighted Value field next to theParameter > base entry.

Ê The Value field changes its appearance and shows a dotted controlbutton:

Figure 77: Assign attributes to element


© Hilscher 2010 – 2016


Ø Click button to open the Object Selector dialog window, in whichyou can assign a signal to the element, so that this signal will bevisualized by the element.

Ê The Object Selector dialog window opens:

Figure 78: Assign signal to element

Ø Click Objects button.Ê A list featuring the signals from your project opens.Ø Select the desired signal, then click OK button (as an alternative, youcan doubleclick the signal).

Ê The Object Selector dialog window closes. You have connected thesignal to the display element.

You can now proceed to add, place and edit further display elements in theatvise builder and connect them with signals. When you are finished, savethe display.

3. Save display.Ø In the drawing tools area, click the floppy disk symbol:

Figure 79: Save display in atvise builder

ð You have saved the display in your atvise project. Please note, that bysaving the display in the project, it has not yet been stored in thenetSCADA device. The display will be stored in the netSCADA deviceby downloading the project into the device.


© Hilscher 2010 – 2016


8.9 Alarms and trending

8.9.1 Configuring alarms

General

netSCADA devices support the alarm functions of atvise. The signals/variables to be surveilled by the alarm function can be selected in theSignal Editor (see the corresponding Configuring signals in the SignalEditor section for your netSCADA device type). If you activate the checkbox in the Alarm column, the corresponding signal will be permanentlysupervised by the netSCADA device.

Activating and acknowledging alarms

An alarm is pending, if the signal has a value different than 0. An alarm isnot pending, if the signal has the value 0.

At acknowledgment of an alarm signal, the netSCADA device can setanother signal within the S7 component or the Modbus PLC automatically,in order to indicate the acknowledgment there. However, this signal musthave the same name as the alarm signal, extended by .AlarmAck.

Example

An alarm signal has the name OverFlow1. Therefore, the correspondingautomatic acknowledgment signal is named OverFlow.AlarmAck. If thealarm is acknowledged within the visualization, the visualizationautomatically writes the value 1 into the signal OverFlow.AlarmAck. Youhave to reset this value in the S7 component or Modbus PLC, in order thatacknowledgment can take place once again.

For further information about the alarm functions in atvise, pleaseconsult the online help of the atvise builder.

Define wording of alarm messages

To define the wording of alarm messages, proceed as follows:

1. Open Alarm management.Ø In the project tree of the atvise builder, doubleclick the element Library> ATVISE > Quick Dynamics > Alarmmanagement.


© Hilscher 2010 – 2016


Ê The Alarm management table opens:

Figure 80: Alarm management

2. Specify total number of alarm messages.Ø In the TextCount line, check if the number type is selected in theValueType dropdrown list.

Ø In the Default column of the TextCount line, enter the total number ofalarm messages contained in the project.

3. Select signals/variables.Ø In the Datapoint1 line, check if the address type is selected in theValueType dropdrown list.

Ø In the Default column of the Datapoint1 line click button.Ê The Object Selector dialog window opens:

Figure 81: Select signal

Ø Click Objects button.Ø Navigate to the desired signal, select it, then click OK button (as analternative, you can doubleclick the signal).

Ê The Object Selector dialog window closes. You have selected a signal,for which you can now define an alarm message.


© Hilscher 2010 – 2016


4. Enter wording of alarm message.Ø In the Text1 line, check if the string type is selected in the ValueType dropdrown list.

Ø In the Default column of the Text1 line, enter the text of the alarmmessage which shall be displayed in case Datapoint1 triggers analarm.

Ê You have defined your first alarm message.

If you want to define alarm messages for other signals, proceed asdescribed above. You can define more alarm messages than provided bythe two items (Datapoint1 and Datapoint2) in the alarm managementtable.

5. Define more alarm messages (if necessary).

Figure 82: Add new alarm messages

Ø In the next free field of the Name column, enter Datapoint3. Thenselect address type from the ValueType dropdrown list and selectthe signal in the Default column.

Ø In the Name column of the line below Datapoint3, enter Text3.Then select string type from the ValueType dropdrown list andenter the text of the alarm message in the Default column.

For each new alarm message, increment the entries in the Name columnaccordingly (i.e. Datapoint4/Text4, Datapoint5/Text5).


© Hilscher 2010 – 2016


8.9.2 Configuring trending

General

netSCADA devices support „trending“. Trending means that values ofcertain signals/variables are being continuously read and recorded in atrend buffer in defined time intervals. This allows a review of the history ofthe signal.

The signals/variables that shall be recorded can be selected in the SignalEditor (see the corresponding Configuring signals in the Signal Editorsection for your netSCADA device type). To do so, activate the check boxin the Trend column of the Signal Editor.

Basic parameters of the trending function, like e. g. the scan time (i. e. thescanning/sampling interval) can be configured on the Trend Recordingpage of the Web Configuration Interface (see section Trend recording [ page 139]).

For information on how to use the trend displays provided by theatvise builder, please refer to the online help of the atvise builder.

Using the netSCADA trend display

The ATVISEPlugin folder in the library of the display editor contains twopreconfigured elements for displaying trends, which can be readily used.You simply have to add the signals, which you want to use for trending, tothe element.

Note:As an alternative, you can also use other readymade trendingelements that the atvise library offers (e. g. in the folder ATVISE >Standard > Trend). The netSCADA trending elements in the ATVISEPlugin folderhowever have the advantage of being capable of supervising thestate of the signals to be recorded. In case it receives an invalidstatus bit (e. g. if the connection has been disrupted), it resets thelast recorded value for that signal to zero (0).


© Hilscher 2010 – 2016


To add the netSCADA trending element to a display, proceed as follows:

1. Select and place element.Ø In the Library area (see position in section GUI of the display editor [

page 111]), open the folder ATVISEPlugin > Trend.

Figure 83: Trend library

Ø Select the Trend element and drag and drop into the drawing area.Place it onto the display at the intended position.

Figure 84: netSCADA trend display

2. Assign a signal to the element.Ø In the drawing area, select the Trend element.Ø In the Attributes area, open the Property > Parameters > Address1folder, then click into the node1 field.

Ê The node1 field changes its appearance and shows a dotted controlbutton.

Ø Click , button to open the Object Selector dialog window, in whichyou can assign a signal to the element for trending.


© Hilscher 2010 – 2016


Ê The Object Selector dialog window opens:

Figure 85: Assign signal to element

Ø Click Objects button.Ø Navigate to the signal, select it, then click OK button (as an alternative,you can doubleclick the signal).

Ê The Object Selector dialog window closes. You have assigned thesignal to the netSCADA trend element.

If you want to add further signals to the netSCADA trend element, click intothe node2 field below Address2 and proceed as described above.


© Hilscher 2010 – 2016


8.10 Generating visualization and transferring it into netSCADAdevice

After having finished designing displays and assigning signals to thedisplay elements, you can now generate the HTML files for your project anddownload them to your netSCADA device.

Important:For this, you need an Ethernet connection between yourconfiguration PC and your netSCADA device.

Ø In the project tree of the atvise builder, select your netSCADA project.Then use the right mouse button to open the context menu and chooseDistribute.

Figure 86: Generate and download HTML pages

Ê The displays are converted into HTML files and are automaticallydownloaded to the netSCADA device. This process can take severalminutes. During the process the following message is shown:

Figure 87: Generating and downloading project message


© Hilscher 2010 – 2016


Note:If you are using the Trending function for the first time, it can takeup to five minutes before the device will be ready for operation afterdownloading the project. This is because the memory for the trenddata is getting formatted when a project with trending function isbeing downloaded for the first time.This state is indicated by the blinking CONFIG LED of thenetSCADA.

ð You have generated the visualization project and downloaded its HTMLpage(s) to the netSCADA device. The device now automatically resetsitself. After the reset, you can connect to the device and view theresults.

If your configuration PC and the netSCADA device are not properlyconnected during the download, the following message appears:

Figure 88: Download failure message

In this case, check the Ethernet connection between your configuration PCand your netSCADA device; you should check especially, whether thepermanent IP address which you have assigned to the device (see sectionConfiguring permanent IP address (Network Settings) [ page 130]) isidentical with the IP address which you have configured for the netSCADAin the atvise project (see section Configuring netLINK SCADA device [ page 55], respectively section Configuring netSCADA device [ page 84]).


© Hilscher 2010 – 2016


8.11 Displaying visualization in browserIn order to show and check your visualization, you can open your standardweb browser and connect to the integrated HTML server of the netSCADAdevice directly from within the atvise builder. Please note that for showing“real” data on your web visualization pages, a “living” fieldbuscommunication needs be connected to the netSCADA device.Ø In the menu bar of the atvise builder, choose Guided Actions > OpenWeb Browser for Server, then select your netSCADA webMI Server:

Figure 89: Open web browser in atvise builder

ð Your standard web browser on your configuration PC starts, connectsautomatically to the IP address of the netSCADA device and displaysthe visualization:

Figure 90: Example of visualization web page with trend


© Hilscher 2010 – 2016


Note:Of course you can connect to the web visualization pages of thenetSCADA device from any other PC without the atvise builder, justby entering the IP address of your netSCADA device into your webbrowser, e. g. HTTP://10.11.5.98. If you are connected to the netSCADA device and want to changefrom its visualization page to the netSCADA Web ConfigurationInterface, you can do so by simply adding the string /configbehind the IP address of the netSCADA in your web browser, e. g.HTTP://10.11.5.98/config. After entering user name andpassword (default user: admin, default password: admin), the startpage of the Web Configuration Interface opens.


© Hilscher 2010 – 2016

Using the Web Configuration Interface of the netSCADA devices 125/175

9 Using the Web Configuration Interface of the netSCADAdevices

9.1 OverviewThe Web Configuration Interface of the netSCADA device allows you toadminister your device via standard web browser and Ethernet interface.On the pages of the Web Configuration Interface, you can check basicparameters of your device, update its firmware or reset it. Furthermore, youcan configure the IP address, the real time clock and the trend recordingparameters of the netSCADA. Here, you can also delete all visualizationpages and configuration data which have been stored on the device.

Figure 91: Start page Web Configuration Interface

Web page Description For details seeDevice Device Information: Start page of the Web Configuration

Interface. Shows basic device parameters. This page can beopened by using the LAN Scanner and Configuration Tool(integrated in the atvise builder) or by entering the URLHTTP://<IP address>/config in your web browser.

Section Start page (Device Information) [ page 129]

Network Network Settings: Nonvolatile configuration of the IP addressof the device.

Section Configuring permanent IPaddress (Network Settings) [ page 130]

Firmware Firmware Identification / Firmware Update: Display offirmware version and firmware update.

SectionUpdating firmware [ page 132]

Reset Device Reset: Device restart. SectionResetting device [ page 135]

System Time Display and configuration of the system time of the device. Section Configuring the system time [ page 136]

Trend Recording Trend Settings: Configuration of the trend recording function. Section Trend recording [ page 139]

Application Erase Application: Erases the atvise project (including userauthentication parameters) from the device.

Section Erasing visualization project(application data) [ page 142]

Restore Restore Factory Settings: Erases all data except the firmwarefrom the device and thus restores the factory settings of thedevice. This function is available only within five minutes afterdevice reset. This page can be opened directly under the URLhttp://<IP address>/factoryrestore without enteringa password.

Section Factory restore [ page 143]

Table 45: Web pages of the Web Configuration Interface


© Hilscher 2010 – 2016


Note:The Home page shown as hyperlink in the navigation pane is thestart page of the visualization, which can be reached under the URLHTTP://<IP Address>, not of the configuration pages. If youclick on the Home link before any atvise visualization project (i. e.an “application”) was downloaded to the device, an error messagewill be displayed.

The Web Configuration Interface supports user and passwordadministration (user authentication) with MD5 coding. Users and passwordscan be defined in the atvise builder software and downloaded along withthe visualization project to the device.

Important:In its state of delivery, the device has the IP address192.168.0.133. If this preset address is not suitable for you, you must first assign anew temporary IP address to the device by using the LAN Scannerand Configuration Tools (see section Assigning temporary IPaddress [ page 43]), in order to make the Web ConfigurationInterface accessible for you via Ethernet IP in the first place. Thefinal configuration and permanent storage of the IP address canthen be made on the Network page of Web Configuration Interface(see section Configuring permanent IP address (Network Settings) [ page 130].


© Hilscher 2010 – 2016


9.2 Accessing the Web Configuration Interface

9.2.1 Prerequisites· The netSCADA device is ready for operation.· The device is connected to a network via its Ethernet interface.· PC with web browser and connection to Ethernet network.· You must know the IP address of the netSCADA device.· You must know user name and password of the web configurationinterface (see section User Authentication).

9.2.2 User authenticationAccess to the Web Configuration Interface of the netSCADA device isprotected by a user authentication. On calling up one of these webconfiguration pages, a password dialog appears.

Preset default parameters of the user authentication are

User name: admin Password: admin

These default parameters remain valid until you have defined a new adminuser and a password in the atvise builder and downloaded it along withthe visualization project into the netSCADA device.

Important:In order to protect the Web Configuration Interface fromunauthorized access, you must define a new admin user with anew password in the Users & Groups node of the atvise builder.Create a new password, so that it will not be any longer possible toaccess the Web Configuration Interface by using the default adminpassword. For more information on Users & Groups in atvise,please consult the online help of the atvise builder.Please note that a “Factory Restore” (see section Factory restore [ page 143]) resets the user authentication of the netSCADA deviceto its old default parameters admin/admin.


© Hilscher 2010 – 2016


9.2.3 Connecting to Web Configuration InterfaceYou connect to the Web Configuration Interface by entering the IP addressof the netSCADA device with the appending string /config into theaddress bar of your web browser. So, if for instance the IP address of yourdevice is 10.11.5.98, enter http://10.11.5.98/config into theaddress bar.

If you have just recently assigned a temporary IP address to the device byusing the LAN Scanner and Configuration Tool, you can connect to theWeb Configuration Interface instantly from within the still opened tool byclicking the Configure button, then choosing Open Web ConfigurationPage…entry from the context menu. Your standard web browser on yourconfiguration PC starts and connects to the IP address and the login dialogof the Web Configuration Interface of the netSCADA device.

After having entered user name and password, you will be directed to thestart page of the Web Configuration Interface called Device Information.From there, you can navigate to the other web configuration pages byclicking on the hyperlinks in the navigation pane (top area) of the page.


© Hilscher 2010 – 2016


9.3 Start page (Device Information)The home page of the Web Configuration Interface displays basicidentification parameters of your netSCADA device.

The home page opens after choosing the Open Web ConfigurationPage…option in the LAN Scanner and Configuration Tool (see sectionAssigning temporary IP address [ page 43]). You can also open this pageby entering the URL http://<IPAddress>/config into the addressbar of your web browser. After having navigated to other pages of the Web Configuration Interface,you can use the Device hyperlink in the navigation pane to return to thishome page.

Figure 92: Home page of the Web Configuration Interface

The Device Information page displays the following parameters:

Product Name: Name of the device

Device Number: Part number of the device

Serial Number: Serial number of the device

Production Date: Production date of the hardware

Hardware Revision: Hardware revision number

Ethernet Address: MAC Address of the device

Free Disk Space (KB): Free space in flash file system

Free Mem Space (KB): Free space in RAM


© Hilscher 2010 – 2016


9.4 Configuring permanent IP address (Network Settings)On the Network Settings page, you can configure the IP addressparameters of the netSCADA device in the Ethernet LAN. Users ofnetSCADA devices for RealTime Ethernet (NSCDT52EN/ATVISE/PN forPROFINET and NSCDT52EN/ATVISE/OMB for Modbus TCP) shouldnote that the Network Settings page can only be used for configuring theIP address of the Ethernet LAN connection (visualization and configurationaccess), not the IP address for the RTE connection. The IP address for theRTE connection needs to be configured in the atvise builder (see sectionConfiguring PROFINET (RFC 1006) parameters [ page 66] respectivelysection Configuring Modbus TCP parameters [ page 75]).

If you choose the option Yes, store settings, the network settingsconfigured on this web page will be stored permanently in the netSCADAdevice, i. e. they will remain valid even after device reset or power failure.

Note:A temporary IP Address can be assigned to the netSCADA deviceanytime by using the LAN Scanner and Configuration Tool, whichis a plugin of the atvise builder (see section Assigning temporary IPaddress [ page 43]).

To open the Network Settings page, click the Network hyperlink in thenavigation pane.

Figure 93: Network Settings


© Hilscher 2010 – 2016


Important:Keep in mind that changing the IP parameters may cause loss ofconnection!

The Parameter column displays the IP network parameters that can beconfigured:

Parameter DescriptionIP Address IP Address of the netSCADA deviceSubnet Mask Subnet mask of the local IP network.Gateway IP Address of the local gateway. Needs to be specified if the netSCADA

is supposed to communicate with devices outside the local network viaa gateway/router, e. g. with an external SNTP server for the purpose ofsynchronizing the system time of the netSCADA device (see sectionConfiguring the system time [ page 136]).

DHCP If you choose this option by selecting the enable radio button, thenetSCADA device tries to receive its IP address from any availableDHCP server. The manually entered IP address then becomesobsolete and will be used only as “fall back” address.

Table 46: Parameter Network Settings

The Stored Settings column displays the values which have been laststored for the device, respectively the factory default IP settings (in casethey haven’t been changed yet).

The Current Settings column displays the temporarily valid values. Thesesettings can differ from the Stored Settings, e. g. after assigning atemporary address with the LAN Scanner and Configuration Tool or afterchanging the IP address on this page without using the Yes, store settingsoption.

In the New Settings column, you can use the provided fields for enteringnew values for the parameters or enable the DHCP option. If you enablethe DHCP option, the netSCADA tries to receive its IP address from anyavailable DHCP server. The manually entered IP address then becomesobsolete.

Note:If you choose the DHCP option but no DHCP server can be foundafter reset, the netSCADA device will remain unreachable forapproximately one minute. After this period, the last stored valid IPaddress will be used by the device as a “fall back” configuration.

By clicking the Submit button, you can save your new settings. Please notethat if you uncheck the Yes, store settings option, these settings will onlybe stored “volatile” in the device.


© Hilscher 2010 – 2016


The following control elements are available:Control element DescriptionYes, store settings Causes “nonvolatile” storage of the IP parameters, i. e. the

parameters remain valid even after reset or poweron cycle. Ifyou uncheck this option, the parameters will be stored onlytemporarily and “volatile”; i. e. the device falls back to its lastpermanently stored valid IP address after reset or poweroncycle.

Clear Undoes changes that have not yet been submitted.Submit Stores new settings.Table 47: Control elements Network Settings

9.5 Updating firmwareThe Firmware page displays the version of the currently loaded firmwareand provides a function for downloading a new firmware version into yourdevice. Configuration data stored in the device will remain intact after afirmware update.

To open the firmware page, click the Firmware hyperlink in the navigationpane.

Figure 94: Firmware update page

Note:Before the update takes place, the system automatically checkswhether the firmware file you have selected for download fits thedevice class and the hardware properties of the netSCADA device.


© Hilscher 2010 – 2016


Firmware Identification

The Firmware Identification section displays the following informationabout the currently loaded firmware:· Channel: Channel number (Port number)· Name: Name of loaded firmware· Version: Version of loaded Firmware· Date: Date of loaded firmware

Firmware Update

In the Firmware Update section, you can select a new firmware file inorder to replace the old firmware, and start the update.

Click Browse… button to open a dialog to select the firmware you want todownload. Path and name of the selected file are displayed in the adjacentfield.

File names of netSCADA firmware are as follows:

NL 50NMPIATVISE: LN303100.nxfNSCDT52RS/ATVISE/MBR: T07100R0.nxfNSCDT52EN/ATVISE/PN: T07100M0.nxfNSCDT52EN/ATVISE/OMB: T07100L0.nxf

Control elements firmware updateElement DescriptionSelection field Shows selected file and its locationBrowse… Opens the file selection dialogTransfer Downloads selected firmware file to deviceCancel Cancels firmware update and clears selection field

Hazard of device damage by disruption of voltage supply duringfirmware update!Do not interrupt the voltage supply while updating the firmware of thenetSCADA device. Power failure during a writing process within the filesystem can cause severe malfunctioning of the device.


© Hilscher 2010 – 2016


After you have started the download by clicking the Transfer button, thevalidity of the firmware file is being checked by the system. If the file failsthe validity check, the file will not be stored in the device and an errormessage will be displayed on the web page. If the file passes, a Transfersucceeded message will be displayed.

After successful transfer, you will be asked to reset the device in order tostart up the new firmware:

Figure 95: Transfer of firmware succeeded message

Check Please confirm you want to reset the device, then click submitbutton.

Note:If the box in front of Please confirm… is not checked, the oldfirmware keeps on running in the device. However, this firmware isnow “preinstalled” and will become active after the next reset orpoweron cycle.


© Hilscher 2010 – 2016


9.6 Resetting deviceOn the Reset page, you can restart your netSCADA device.

To open the Reset page, click the Reset hyperlink in the navigation pane.

Figure 96: Device reset

A reset has to be made after every firmware or configuration update. It has the following consequences:· The firmware is being restarted and connections will be interrupted ortimed out.

· I/O bus communication is being stopped.· The IP connection may be lost if the IP parameters have not beenconfigured on the Network Settings page and stored in the devicepermanently.

Activate the checkbox in front of Please confirm... to acknowledge that youwant to reset the device. To start the reset, click Submit button. Click Cancel button to uncheck the checkbox in front of Please confirm...


© Hilscher 2010 – 2016


9.7 Configuring the system timeOn the System Time page, you can check the actual system time of thedevice, set a new system time manually or configure automatic timesynchronization via SNTP or NTP server.

To open the System Time page, click the System Time hyperlink in thenavigation pane.

Figure 97: System time

Current System Time

Host System Time: shows date and system time (GMT) of theconfiguration PC (i. e. the PC from which you are currently accessing thenetSCADA) at the time of access.

Target System Time: shows date and system time (UTC) of thenetSCADA at the time of access.


© Hilscher 2010 – 2016


Note:The netLINK SCADA NL 50NMPIATVISE is not equipped with ahardware real time clock. Thus, if you are NOT using timesynchronization via SNTP server for this device, the system time ofthe netLINK SCADA will by default be set on January 1th 2000,00:00:00 o’clock after each reset or poweron cycle. After reset,the clock starts and indicates the time that has elapsed since thereset. If, however, you enable time synchronization via SNTP, thedevice will receive the actual time from the SNTP server after reset.

Target SNTP status: If you have configured time synchronization viaSNTP server, but the netSCADA device can’t connect to the SNTP server,an error message will be shown here.

Target System Time Change (UTC)

Here you can change the system time of the netSCADA device. You havetwo options to do this:You can either enter the time values manually into the fields of the NewSetting column, or you can take over the current date and time values fromthe configuration PC by clicking the Reload button (the display of the actualsystem time of the netSCADA and the host will then also be updated).

By clicking the Submit button, the values of the New Setting field will besaved in the netSCADA device. The Current Setting column shows thelast measured system time of the netSCADA device.

Note:The submitted time will automatically be converted into UTC time.On the visualization pages, the time will be converted back anddisplayed as local time. Summer/winter time will automatically betaken into account.

Target System Time Synchronization (SNTP)

Here you can configure time synchronization by SNTP server for yournetSCADA device. To do so, proceed as follows:Ø In the New Setting fields of the Server IP address parameter, enterthe IP address of the SNTP server that you want to use for timesynchronization.

Important:Please note that you need to set a valid gateway address on theNetwork Settings page (see section Configuring permanent IPaddress (Network Settings) [ page 130]) if you want to use anexternal time server which is located outside of your local Ethernetnetwork. Note also that port 123/UDP of your router device must beenabled.


© Hilscher 2010 – 2016


Ø In the New Setting field of the Update cycle (minutes) parameter,enter the number of minutes after which the SNTP server shall beregularly contacted by the netSCADA device for time synchronization (ifyou want to use cyclic synchronization mode).

Ø Choose the Update mode:cyclic: time synchronization takes place according to the interval whichyou have defined in the Update cycle (minutes) field.startup: time synchronization takes place only after reset/poweroncycle.off: no SNTP service is being used.

Ø Click Test to check the connection to the IP address of the SNTP serverwhich you have entered in the New Setting column.

Ê A note/response will be shown in the footer, indicating whether aconnection to the SNTP can be established or not.

Ø If the Test succeeded messages in the footer indicates that the testconnection to the SNTP server did succeed, click Submit button tosave the values in the New Setting column in the netSCADA.

Ê The Current Settings column displays the last saved values.

With the Submit button, you can save the values in the New Settingcolumn in the netSCADA.

With the Reload button, you can reload the last saved values.

With the Test button, you can establish a test connection to the SNTPserver under the IP address which you have entered in the New Settingfield.


© Hilscher 2010 – 2016


9.8 Trend recordingOn the Trend Recording page, you can check the current parameters ofthe trending function and set the trend buffer mode (circular or ring buffer)and the scan time (scanning/sampling interval).

Here, you can also test, how changing the scan time would affect the othertrending parameters (e. g. the maximum recording time).

Note:The settings on this page affect all variables or signals that havebeen chosen for the trending generally. Please note, that you cannot select individual variables/signals for the trending on this page;the selection of variables/signals to be recorded has to be made inthe Signal Editor of the atvise builder during the creation of thevisualization project (see the corresponding Configuring signals inthe Signal Editor section for your netSCADA device type).

To open the Trend Recording page, click the Trend Recording hyperlinkin the navigation pane.

Figure 98: Trend Recording


© Hilscher 2010 – 2016


The Trend Settings table features the following parameters:Parameter DescriptionTrend buffer mode Here you can set the mode of the trend buffer.

circular: Ring buffer mode. When the buffer is full, the oldest recordeddata will be overwritten by the latest recorded data.linear: When the buffer is full, recording stops and no new data will bewritten.

Trend buffer type Memory type of the trend buffer.volatile: Trend data is being stored in RAM and gets lost after poweroff. This is the case for the NL 50NMPIATVISE device, because it hasno flash memory chip for storing the trend data.nonvolatile: Trend data is being stored in a flash memory chip andsurvives after poweroff (NSCDT52 device types).

Trend buffer size (tags) Maximum quantity of tags which can be stored in the trend buffer.Number of recorded tags Quantity of tags which have been stored in the trend buffer so far. This

value depends on the Number of recorded variables and the Scantime.

Number of recorded variables Quantity of variables/signals to be recorded. These variables/signalsare selected in the Signal Editor of the atvise builder during thecreation of the visualization project.

Scan time (milliseconds, [200..86400000]) Here you can set the sampling interval of the variables/signals inmilliseconds. Possible range is 200 to 86400000 milliseconds (24hours).Example: If you set the Scan time on 5000, the variables/signals whichhave been chosen for trend recording will be scanned every fiveseconds and their values will be recorded as “tags”.

Flush time (milliseconds) Maximum period of time after which recorded tags are finally writteninto the trend buffer. This value depends on the Scan time.

Max. recording time (hours) Maximum recording time period. This value depends on the Number ofrecorded variables, the Scan time and the Trend buffer size.Note: The displayed value has always been automatically roundeddown to the full hour by the system.

Remaining time until stop/overwrite (hours) Remaining time period in hours until the trend buffer will be full, and –in consequence – the recording will be stopped (if linear buffer is used)or old data will be overwritten (if circular buffer is used). This value depends on the Number of recorded variables, the Scantime and the Trend buffer size.Note: The displayed value has always been automatically roundeddown to the full hour by the system.

Table 48: Trend settings parameters

The Current Setting column shows the currently valid parameters.

In the New Setting column, you can change the Trend buffer mode andthe Scan time (scanning/sampling interval), if necessary. By clicking theCalculate Derived Values button after changing the Scan time, you cantest how changing the Scan time will affect the other parameters. Thecalculated new values of the parameters will then be displayed in the NewSetting column.


© Hilscher 2010 – 2016


The following control elements are available:Control element DescriptionSet Defaults All configurable parameters will be reset to their default value,

i. e. Trend buffer mode: circularScan time (milliseconds): 5000

Calculate DerivedValues

Calculates the new values of the depending parameters afterhaving changed the Scan time. The new values will bedisplayed in the New Setting column.

Clear Trend Deletes the stored trend data without changing the configuredtrend settings.

Submit Changes Saves new settings and deletes already stored trend data.Table 49: Control elements Trend Settings


© Hilscher 2010 – 2016


9.9 Erasing visualization project (application data)On the Application page, you can check how much disk space thecurrently loaded application (i. e. the data of the atvise visualization project)consumes on the flash memory component of the netSCADA device. Youcan also erase the currently loaded application from the device here.

To open the Application page, click the Application hyperlink in thenavigation pane.

Figure 99: Erase application page

Important:Erasing the application data also deletes the security.cfg file on thenetSCADA device, which contains the customized userauthentication data that has been defined in the atvise project.Thus, erasing the application data reinstates the old default adminuser and the default admin password. These default authenticationparameters then remain valid until you have downloaded to thedevice a new atvise project containing new customizedauthentication parameters.The device configuration parameters of the netSCADA, like the IPaddress (Network Settings), the system time (System Time) andthe settings of the Trend Recording are not affected by the erasingof the application data. Recorded trending data will not be deletedeither, however the pure trend data might be rendered uselessbecause of the deleted and now missing application.

Erase Application

If you want to erase the application, proceed as follows:

Activate the checkbox in front of Confirm to erase the application..., toacknowledge that you want to erase the application data. To start erasing,click Submit button.If you don’t want to erase, click Cancel button to uncheck the checkbox infront of Confirm to erase…


© Hilscher 2010 – 2016


9.10 Factory restoreOn the Factory Restore page, you can restore the „factory settings“ of thenetSCADA device, i. e. reset the device to its “state of delivery”. Inconsequence, all application or configuration data stored in the device(except for the firmware) will be deleted or reset to default.

This function is available only within five minutes after device reset (seesection Resetting device [ page 135]); the necessary control elements onthe Factory Restore page will be visible/active only if a reset has beenperformed immediately before.

The Factory Restore page can be opened directly under the URLhttp://<IP Address>/factoryrestore without entering a password.

Important:Please note, that by performing a Factory Restore, the IP addressset on the Network Settings page (see section Configuringpermanent IP address (Network Settings) [ page 130]) will bedeleted. The device thus will be reset to its default IP address192.168.0.133, sub net mask 255.255.255.0. If you don’t want to use this preset default IP address, you thenhave to use the LAN Scanner and Configuration Tools (which isintegrated as plugin in the atvise builder) to first assign a temporaryIP address to your device and then connect to the WebConfiguration Interface in order to reconfigure your desiredpermanent IP address on the Network Settings page.Please note, that a Factory Restore also deletes the security.cfgfile, which contains the user authentication data. This reinstates theold default user authentication parameters (user: admin, password:admin) for accessing the Web Configuration Interface, until youhave defined and downloaded new user authentication data in anew atvise project.

To open the Factory Restore page, click the Restore hyperlink in thenavigation pane or enter the URL http://<IP Address>/factoryrestore into the address bar of your web browser.

Note:A “factory restore” for the NSCDT52 devices can also beperformed via USB, in case the device can not be reached viaEthernet IP. For more information, see chapter Firmware recoveryof NSCDT52 via USB [ page 145].


© Hilscher 2010 – 2016


Figure 100: Factory Restore

To restore the factory settings, proceed as follows:Ø Reset the device (see section Resetting device [ page 135]).Ø Open Factory Restore page.Ø Within five minutes after reset, activate the checkbox in front of Pleaseconfirm you want to restore factory settings, to acknowledge thatyou want to reload the factory settings of the device.

Ø Click Submit button to start the restoration.

Note:The Cancel button unchecks the checkbox in front Please confirmyou want to restore…

Ê All files except for the firmware are deleted. This can take a fewseconds.

Ø Reset the device again (see section Resetting device [ page 135]).ð You have restored the factory settings of the device.


© Hilscher 2010 – 2016

Firmware recovery of NSCDT52 via USB 145/175

10 Firmware recovery of NSCDT52 via USBOverview

If after poweron the SYS LED of a NSCDT52 device (see chapter LEDdescriptions [ page 151]) is consistently blinking yellow and green at arate of 1 Hz, the device is in boot mode and is not able to start thefirmware. The firmware file of the netSCADA is missing or corrupted. In thisstate, the device can not be operated and needs to be recovered by loadinga new firmware file into the device via USB connection.

Note:Firmware recovery via USB as described in this chapter is notpossible for the NL 50NMPIATVISE (netLINK SCADA) device.

For this, you need a USB cable with a Mini USB connector and the HilscherComProX tool, which is stored on the netSCADA DVD in theSupplements & Examples\Device Recovery\NSCDT52XXFactory Reset over USB directory. ComProX can be executed directlyfrom DVD, it does not need to be installed on your configuration PC.

Note, that for recovery via USB, you need to install the USB driver for thenetSCADA device on your configuration PC. This driver allowscommunication with devices lacking functional firmware.It is recommended to install the USB driver by using the setup.exeinstallation program before you connect the netSCADA device via USBcable. This driver installation program is stored on the netSCADA DVD inthe Setups & Drivers\USB Driver directory. It can be started by adoubleclick. Then simply follow the instructions given in the dialogwindows of the installer routine.

Note also the following about recovery via USB: Although any old firmware file that may have existed in the netSCADAdevice will be overwritten by downloading the new file (which can berecognized by the .NXF file name extension), all other files stored in theinternal load memory of the device remain untouched. This means that anyexisting configuration file (CONFIG.NXD) or IP address file (NWID.NXD) inthe device can be preserved for further use, if needed. However, if youwant a “complete recovery” of your device via USB (a complete recovery ofthe “factory settings” means that only “fresh” firmware is present in thedevice), you can delete these configuration files separately in the Explorerof the ComProX tool.After having downloaded the new firmware via USB, you can of course, asan alternative, also delete the old configuration files by connecting to theWeb Configuration Interface of the netSCADA device via Ethernet and thenuse the Factory Restore page to delete these files via HTTP (see sectionFactory restore [ page 143]).


© Hilscher 2010 – 2016


Prerequisites· The USB driver for the netSCADA device has been installed on theconfiguration PC

· The configuration PC is connected to the netSCADA device via USBcable

· netSCADA DVD· netSCADA device is supplied with voltage

Stepbystep instructions1. Open ComProX.Ø On the netSCADA DVD, open Supplements & Examples\Device

Recovery\NSCDT52XX Factory Reset over USB directory.Ø Doubleclick comproX.exe file.Ê The ComProX tool opens:

Figure 101: ComProX start screen

2. Connect to netSCADA device.Ø In the menu, choose Connection > Open.Ê After the Windows USB/COM ports have been scanned, the connectionselection dialog opens:

Figure 102: ComProX Connection Dialog

Ø Select Hilscher netSCADA entry, then click OK.Ê The connection dialog closes and you are back in start screen ofComProX.


© Hilscher 2010 – 2016


3. Download firmware file.Ø In the menu, choose Connection > File Explorer.Ê The Explorer window opens:

Figure 103: ComProX File Explorer

Ø Under Filesystem, select PORT_0.Ê The contents of PORT_0 is displayed. This, most likely, will be the oldfirmware file, which you want to overwrite, and the INIBATCH.NXD file.

Ø In the right part of the Explorer window, rightclick to open the contextmenu, then choose Download.

Figure 104: ComProX download

Ê The Choose a file dialog opens:

Figure 105: File selection dialog

Ø Select the firmware file which you want to download to the netSCADAdevice.


© Hilscher 2010 – 2016


The names of the firmware files are as follows:NSCDT52RS/ATVISE/MBR: T07100R0.nxfNSCDT52EN/ATVISE/PN: T07100M0.nxfNSCDT52EN/ATVISE/OMB: T07100L0.nxf

Hazard of device damage by disruption of voltage supply duringfirmware download!Do not interrupt the voltage supply while downloading the firmware to thenetSCADA device. Power failure during a writing process in the file systemcan cause severe malfunctioning of the device.

Ø Click Open button.Ê The firmware file is being downloaded to the netSCADA device. The oldfirmware file is overwritten. This can take a few seconds.

4. Check download.Ø In the right part of the Explorer window, rightclick to open the contextmenu, then choose Refresh.

Ø Wait for a few seconds.Ê If the download has been successful, the downloaded firmware file isdisplayed in Port_0. The name of the new firmware file will be identicalto the name of the old firmware file; however, by checking the differentsize of the file, you might be able to recognize that you havesuccessfully loaded a new firmware version.

Figure 106: Downloaded firmware file in Explorer

Note:If you want to perform a complete recovery of the “factory settings”of the device, you can now delete the configuration files stored inPort_1. To do so, select Port_1 entry under Filesystem in theopened ComProXExplorer, then select the file which you want todelete, then choose Delete from the context menu.


© Hilscher 2010 – 2016


5. Exit ComProX.Ø Close the Explorer window.Ø In the menu of ComProX, choose Connection > Close, to close theconnection to the device.

Ø Close ComProX.6. Restart netSCADA device.Ø Disconnect USB cable from the netSCADA device.Ø Reset the device to start the new firmware.


© Hilscher 2010 – 2016

General troubleshooting 150/175

11 General troubleshootingGeneral

Check if the following preconditions for netSCADA device operation arefulfilled:· A suitable supply voltage must be availableFor NL 50NMPIATVISE: internally from the S7 PLC or externally via24V Mini COMBICON connector.For NSCDT52RS/ATVISE/MBR, NSCDT52EN/ATVISE/PN andNSCDT52EN/ATVISE/OMB via 24V Mini COMBICON connector.

· All software components must have been installed correctly.· The configuration of the netSCADA devices must have been performedcorrectly.

Further information on this topic can be found in section Requirements foroperating the netSCADA devices [ page 19].

LNKLED

The Ethernet link status LED (LNK) of the netSCADA device indicateswhether a connection to the Ethernet exists. If the LED is off, no connectionexists. If the LED is on, the device has a connection to the Ethernet.

ACTLED

The Status LED ACT of the netSCADA device indicates whethercommunication takes place.

Cable

Make sure that all cables are properly connected.

Configuration

Check whether the IP address of the netSCADA device has beenconfigured according to the description given in section Configuringpermanent IP address (Network Settings) [ page 130].

Ethernet TCP/IP interface (Ethernet LAN)

Check the network settings of your PC.

With the ping command in MSDOS Prompt, you can easily check if aconnection via TCP/IP to the netSCADA device is possible. Open the MSDOS Prompt and enter ping 192.168.10.190 (the IP address has to be thesame as set in the netSCADA device) and press the Return key. Could aconnection be established then the answer is displayed by the followingtext Reply from 192.168.10.190... Otherwise a connection timeout isdisplayed.


© Hilscher 2010 – 2016

LED descriptions 151/175

12 LED descriptions

12.1 LEDs NL 50NMPIATVISELED Color State MeaningSYS(1)

Duo LED yellow/green

(green) On Firmware started.

(yellow) On This state is allowed for a short time only. If this LED stays yellow, a hardware defect ispossible.

(yellow/green)

Blinking yellow/green Bootloader active. This state is allowed for ashort time only.

(off) Off Missing power supply or hardware defect.

COM(3)

Duo LED red/green

(green) On StatusThe device currently holds the PROFIBUS tokenand is able to transfer telegrams of data.

(green)Blinking (regularly) 5 Hz

StatusThe device is configured to be a part of thePROFIBUS ring, but it must share thePROFIBUS token with other PROFIBUSMasterdevices present on the PROFIBUS ring.

(green)Blinking (regularly) 0.5 Hz Status

Automatic baud rate detection is running.

(red) On ErrorCommunication error during execution of aPROFIBUSMPI read or write access to S7.Possible reasons: S7 not reachable or S7 reportserror for the last MPI read or write access. The error display is set back with the next errorfree MPI communication.

(off) Off Status/ErrorThe device has not been integrated into thePROFIBUS ring, i.e. it has not been configuredcorrectly or has a wrong configuration or has notreceived the PROFIBUS token.

LNK(6)

LED green (next to RJ45 Ethernet socket)

(green) On The device is currently connected to theEthernet.

(off) Off The device is currently not connected to theEthernet.

ACT(7)

LED yellow (next to RJ45 Ethernet socket)

(yellow) On The device currently sends or receives EthernetFrames.

(off) Off The device does currently not send and receiveany EthernetFrames.

Table 50: LEDs NL 50NMPIATVISE

The position numbers in the LED column refer to the figure in sectionOverview connectors and LEDs NL 50NMPIATVISE [ page 22].


© Hilscher 2010 – 2016


12.2 LEDs NSCDT52RS/ATVISE/MBRLED Color State MeaningSYSTEM(3)

System state – duo LED yellow/green


(yellow) On This state is allowed for a short time only. If this LED stays yellow, a hardware defect is possible.

(yellow/green)

Blinkingyellow/green

Bootloader active. This state is allowed for a short time only. If thisstate persists, the firmware file is corrupted or missing. In this casethe firmware of the device needs to be recovered via USBconnection. For details see Firmware recovery of NSCDT52 viaUSB [ page 145].


CONFIG(3)

Configuration state – duo LED red/green

(green) On Configuration of visualization is OK.Device has a valid atvise configuration. Access to visualization ispossible.

(green)Blinking at 2Hz

Trend buffer is being formatted. This state occurs when an atviseproject featuring trend recording is being downloaded for the firsttime. This state can last up to five minutes.

Blinking at20 Hz

Trend buffer is being analyzed. This state occurs after restarting anetSCADA device that features trend recording and the configurationof the trend recording has not been altered. This state can last up toten seconds.

(red) On Error in configuration of visualization. atvise configuration is missing or inconsistent. Access tovisualization is not possible.

MODBUS(3)

Modbus state – duo LED red/green

(green) On Device has a valid Modbus RTU configuration and is ready forModbus communication, respectively sends/receives Modbus RTUtelegrams.

(red) On Communication error.If device is configured as Modbus RTU Master:· the slave device answered with an error (Modbus Exception), e. g.function code not supported, access to invalid register addressesor coil addresses

· receive error detected, e. g. parity error or checksum error

· timeout (slave device does not answer)If device is configured as Modbus RTU Slave:· the Modbus RTU Master device uses an invalid function code

· the Modbus RTU Master device has accessed invalid registeraddresses or coil addresses

· receive error detected, e. g. parity error or checksum error

· timeout (application does not answer or answers with error)Note: The error display will be set back with the next errorfreeModbus telegram sequence

ACTIVE(3)

Visualization state – duo LED red/green

(green) On Browser accesses visualization.

(red) On Serious error in the visualization component of the firmware.

(off) Off No active visualization connection.


© Hilscher 2010 – 2016


LED Color State MeaningLOAD(3)

File download state – duo LED red/green

(green) On atvise configuration file is being downloaded.

(red) On Error occurred during download of atvise configuration file.

(off) Off No download activity.

LNK(7) and (10)

LED green (next to RJ45 Ethernet socket)

(green) On The device is currently connected to the Ethernet.

(off) Off The device is currently not connected to the Ethernet.

ACT(9) and (12)

LED yellow (next to RJ45 Ethernet socket)

(gelb) On The device currently sends or receives EthernetFrames.

(off) Off The device does currently not send and receive any EthernetFrames.

Table 51: LEDs NSCDT52RS/ATVISE/MBR

The position numbers in the LED column refer to the figure in sectionOverview connectors and LEDs NSCDT52RS/ATVISE/MBR [ page 23].


© Hilscher 2010 – 2016


12.3 LEDs NSCDT52EN/ATVISE/PNLED Color State MeaningSYSTEM(3)




(yellow/green)


Bootloader active. This state is allowed for a short time only. If thisstate persists, the firmware file is corrupted or missing. In this casethe firmware of the device needs to be recovered via USBconnection. For details see chapter Firmware recovery of NSCDT52via USB [ page 145].

(off) Off Missing power supply or a hardware error occurred.

CONFIG(3)





Blinking at20 Hz



RFC1006(3)

RFC1006 state – duo LED red/greenCurrently without function

ACTIVE(3)





LOAD(3)





LNK(6)

Link LED green, next to RJ45 socket (PROFINET/RFC1006 interface)

(green) On The device is currently connected to PROFINET/RFC1006.

(off) Off The device is currently not connected to PROFINET/RFC1006.

ACT(8)

Activity LED yellow, next to RJ45 socket (PROFINET/RFC1006 interface)

(yellow) On The device currently sends or receives PROFINET/RFC1006frames.

(off) Off The device does currently not send or receive any PROFINET/RFC1006 frames.

LNK(9) and (12)

Link LEDs green, next to RJ45 sockets (Ethernet LAN interface)

(green) On The device is currently connected to Ethernet LAN.

(off) Off The device is currently not connected to Ethernet LAN.


© Hilscher 2010 – 2016


LED Color State MeaningACT(11) and (14)

Activity LEDs yellow, next to RJ45 sockets (Ethernet LAN interface)

(yellow) On The device currently sends or receives Ethernet LAN frames.

(off) Off The device does currently not send or receive any Ethernet LANframes.

Table 52: LEDs NSCDT52EN/ATVISE/PN

The position numbers in the LED column refer to the figure in sectionOverview connectors and LEDs NSCDT52EN [ page 24].


© Hilscher 2010 – 2016


12.4 LEDs NSCDT52EN/ATVISE/OMBLED Color State MeaningSYSTEM(3)




(yellow/green)


Bootloader active. This state is allowed for a short time only. If thisstate persists, the firmware file is corrupted or missing. In this casethe firmware of the device needs to be recovered via USBconnection. For details see chapter Firmware recovery of NSCDT52via USB [ page 145].


CONFIG(3)





Blinking at20 Hz



MODBUS(3)

Modbus TCP state – duo LED red/green

(off) Off Not Ready: OMB task is not ready

(green) On Device has a valid Modbus TCP configuration and is ready forModbus TCP communication, respectively sends/receives ModbusTCP telegrams.

(green)Blinkingcyclically at1 Hz

Ready, not configured yet: OMB task is ready and not configuredyet

Blinkingcyclically at5 Hz

Waiting for Communication: OMB task is configured

(red) On Communication error

(red)Blinkingcyclically at2 Hz

System error

ACTIVE(3)





LOAD(3)





LNK(6)

Link LED green, next to RJ45 socket (Modbus TCP interface)

(green) On The device is currently connected to Modbus TCP.

(off) Off The device is currently not connected to Modbus TCP.


© Hilscher 2010 – 2016


LED Color State MeaningACT(8)

Activity LED yellow, next to RJ45 socket (Modbus TCP interface)

(yellow) On The device currently sends or Modbus TCP frames.

(off) Off The device does currently not send or receive any Modbus TCPframes.

LNK(9) and (12)

Link LEDs green, next to RJ45 sockets (Ethernet LAN interface)

(green) On The device is currently connected to Ethernet LAN.

(off) Off The device is currently not connected to Ethernet LAN.

ACT(11) and (14)

Activity LEDs yellow, next to RJ45 sockets (Ethernet LAN interface)

(yellow) On The device currently sends or receives Ethernet LAN frames.

(off) Off The device does currently not send or receive any Ethernet LANframes.

Table 53: LEDs NSCDT52EN/ATVISE/OMB

The position numbers in the LED column refer to the figure in sectionOverview connectors and LEDs NSCDT52EN [ page 24].


© Hilscher 2010 – 2016

Technical data 158/175

13 Technical data

13.1 NL 50NMPIATVISENL 50NMPIATVISE Parameter ValueProcessor Type netX 50Memory RAM 8 MB SDRAM

FLASH 4 MB serial Flash, contains boot loader, firmware,configuration and visualization data.

FLASH available for web application ca. 3 MBRAM available for trend data ca. 1 MB

SIMATIC S7 PLC S7300 with PROFIBUS or MPIinterface

supported

S7400 with PROFIBUS or MPIinterface

supported

S7200 with PROFIBUS or MPIinterface

not supported

PLC data area access Input, Output, Marker, Counter, TimerInterface for S7 –programming tool

Connector DSub (9 pin, female connector)Note: There is a 1:1connection to the correspondingpins of the PROFIBUS interface.

SIMATIC S7 data areas Data blocks Data blocks by import of the symbols from the S7project file.

Marker Marker by manual adding of symbols.Maximum number of STEP 7 datapoints per display

64

PROFIBUSMPICommunication

Type ClientData transport PROFIBUSFDL telegramsNumber of connections Max. 32 MPI connections at the same time.Access to Data block, Marker

PROFIBUS interface Transmission rate 19.2 kBit/s to 1.5 MBit/s supported31.25 kBit/s is not supported

Interface type RS485, isolatedConnector DSub (9 pin, male connector)Automatic Baud rate detection (not at187.5 kBit/s, 500 kBit/s, 1.5 MBit/s)

Supported for MPI. Not supported for PROFIBUS DP.

Max. linkable signals Input signals 5760Input signals 5760

Ethernet communication Data transport TCP/IPConnections Min. 3 TCP connections to browser at the same time

possible.Ethernet interface Transmission rate 10/100 MBit/s

Interface type 10 BASET/100 BASETX, isolatedConnector RJ45 socketAuto Negotiation SupportedAuto Crossover Supported

Integrated Server/Clients FTP server RFC 959, Port 21, passive modeHTTP server RFC 2616, Port 80, HTTP/1.1SNTP client RFC 2030, Port 123, time synchronization


© Hilscher 2010 – 2016


NL 50NMPIATVISE Parameter ValueVisualization Web visualization atvise webMI with Hilscher plugins

Engineering tool atvise builder by CertecSupported web browser See section Supported web browser [ page 166]Variables/data points unlimitedWeb memory consumption 200 kByte per visualization page (typically)Standard functions Alarm, Trend and user managementAdaptability Entirely customizable using Java scriptingMultilingualism Standard: german/english (can be extended)

Trending Trend variables Up to 32 Variables possibleSampling rate 200 ms to 24 hoursRecording time Depending on the number of variables and the

sampling rate. Example:8 Variables @ 60 sec. sampling rate = 11 days18 Variables @ 60 min. sampling rate = 300 days

Real time Real time clock Software supported, precision: 50ppmReal time clock buffering noneSynchronization Manually or cyclically by SNTP

LED indicators LEDs SYS System statusCOM Communication statusACT Ethernet activity statusLNK Ethernet link statusFor details see section LEDs NL 50NMPIATVISE [ page 151]

Power supply Voltage 18 – 30 V DCTypical current at 18 V 72 mATypical current at 24 V 57 mATypical current at 30 V 48 mAConnector for power supply from PLC via DSub (9 pin, male connector) from PLCConnector for external power supply MiniCOMBICON socket

3.81 mm, 2 pinElectrical immunity tointerference

Electrostatic discharge (ESD)according to IEC/EN 6100042:1995

8 kV Air discharge, Criterion B4 kV Contact discharge, Criterion B

Fast transient interferences (Burst),zone B, according to IEC/EN6100044:1995

1 kV Ethernet Communication line, Criterion B

Surge voltage, zone B, according toIEC/EN 6100045:1995

1 kV CM, Ethernet Communication line, Criterion B

Environmental conditions Temperature range 0 … + 50 °CHumidity range 0 … 85 % relative humidity (not condensing)

Device Dimensions (L x W x H) 65 x 48 x 16 mmWeight appr. 40 gMounting/Installation Directly at MPI interface of the SIMATIC S7 PLCProtection Class IP20RoHS Yes

CE Sign CE Sign YesEmission EN 55011:2009 + A1:2010, Class AImmunity EN 611312:2008Table 54: Technical Data NL 50NMPIATVISE


© Hilscher 2010 – 2016


13.2 NSCDT52RS/ATVISE/MBRNSCDT52RS/ATVISE/MBR Parameter ValueProcessor Type netX 52Memory RAM 8 MB SDRAM

Web application memory 6 MB nonvolatile FLASH memoryTrending memory 8 MB nonvolatile FLASH memory

Modbus RTU communication Type Slave or master to 16 slavesModbus interface RS232

RS485RS422

Device damage bycompensating current !The reference potential of the power supply andthe reference potential of the RS232/RS422/RS485 interface are galvanically connected.Avoid compensating currents between thereference potentials of the devices connected viaRS232/RS422/RS485.

Modbus connector COMBICON MSTB 2.5/5 5 pins, greenBaud rate 1.2 kBaud…115.2 kBaudFunction codes FC1, FC2, FC3, FC4, FC5, FC15, FC16

Ethernet communication Data transport TCP/IPConnections Min. 3 TCP connections to browser at the same

time possibleEthernet interface Interface type 10 BASET/100 BASETX, isolated

Transmission rate 10/100 MBit/sConnector 2 x RJ45 sockets with integrated switchAuto Negotiation SupportedAuto Crossover Supported


Visualization Web visualization atvise webMI with Hilscher pluginsEngineering tool atvise builder by CertecSupported web browser See section Supported web browser [ page 166

]Variables/data points unlimitedWeb memory consumption 200 kByte per visualization page (typically)Standard functions Alarm, trend and user managementAdaptability Entirely customizable using Java scriptingMultilingualism Standard: german/english (can be extended)

Trending Trend variables Up to 32 variables possibleSampling rate 200 ms to 24 hoursRecording time Depending on the number of variables and the

sampling rate. Example:8 Variables @ 60 sec. sampling rate = 45 days18 Variables @ 60 min. sampling rate = 1200days

Real time Real time clock Hardware supported, precision: 20ppmReal time clock buffering Min. 7 days, maintenancefree by SuperCapSynchronization Manually or cyclically by SNTP


© Hilscher 2010 – 2016


NSCDT52RS/ATVISE/MBR Parameter ValueLED indicators LEDs SYSTEM System status

CONFIG Configuration statusMODBUS Modbus statusACTIVE Visualization statusLOAD File download status ACT Ethernet activity statusLNK Ethernet link statusFor details see section LEDs NSCDT52RS/ATVISE/MBR [ page 152]

Power supply Voltage 18 – 30 V DCTypical current at 18 V 120 mATypical current at 24 V 88 mATypical current at 30 V 73 mAConnector COMBICON MC 1.5/5 5 pins

Electrical immunity tointerference



Fast transient interferences (Burst),zone B, according to EN6100044:2012

2 kV Power supply connector DC, Criterion B 1 kV Communication lines Ethernet and RS,Criterion B

Surge voltage, zone B, according toEN 6100045:2006

0.5 kV CM/DM Power supply connector DC,Criterion B1 kV CM Communication lines Ethernet and RS,Criterion B


Device Dimensions (L x W x H) 88 x 22,5 x 78 mmWeight ca. 84 gMounting/Installation Top hat rail mounting according to DIN EN 60715Protection Class IP20RoHS Yes

CE Zeichen CE Sign YesEmission EN 55011:2009 + A1:2010, Class AImmunity EN 611312:2008

Table 55: Technical data NSCDT52RS/ATVISE/MBR


© Hilscher 2010 – 2016


13.3 NSCDT52EN/ATVISE/PNNSCDT52EN/ATVISE/PN Parameter ValueProcessor Type netX 52Memory RAM 8 MB SDRAM


SIMATIC S7 SPS PLC types S71200/1500, PROFINET S7300/400PLC data area access Input, Output, Marker, Counter, TimerPLC Ethernet protocol RFC 1006, Port 102, on PROFINET

PROFINET communication Connector 1 x RJ45 socketInterface type 10 BASET/100 BASETX, isolated

Ethernet LAN communication Data transport TCP/IPConnections Min. 3 TCP connections to browser at the same

time possibleInterface type 10 BASET/100 BASETX, isolatedTransmission rate 10/100 MBit/sConnector 2 x RJ45 sockets with integrated switchAuto Negotiation SupportedAuto Crossover Supported







LED indicators LEDs SYSTEM System statusCONFIG Configuration statusRFC1006 PROFINET/RFC1006 statusACTIVE Visualization statusLOAD File download status ACT Ethernet activity statusLNK Ethernet link statusFor details see section LEDs NSCDT52EN/ATVISE/PN [ page 154]


© Hilscher 2010 – 2016


NSCDT52EN/ATVISE/PN Parameter ValuePower supply Voltage 18 – 30 V DC

Typical current at 18 V 190 mATypical current at 24 V 130 mATypical current at 30 V 110 mAConnector COMBICON MC 1.5/5 5 pins





2 kV Power supply connector DC, Criterion B 1 kV Communication lines Ethernet, Criterion B


0.5 kV CM/DM Power supply connector DC,Criterion B1 kV CM Communication lines Ethernet, CriterionB




Table 56: Technical data NSCDT52EN/ATVISE/PN


© Hilscher 2010 – 2016


13.4 NSCDT52EN/ATVISE/OMBNSCDT52EN/ATVISE/OMB

Parameter Value

Processor Type netX 52Memory RAM 8 MB SDRAM


Modbus TCP communication Device type Server or Client to 16 slavesFunction codes FC1, FC2, FC3, FC4, FC5, FC15, FC16Connector 1 x RJ45 socketInterface type 10 BASET/100 BASETX, isolated

Ethernet LAN communication Data transport TCP/IPConnections Min. 3 TCP connections to browser at the same

time possibleInterface type 10 BASET/100 BASETX, isolatedTransmission rate 10/100 MBit/sConnector 2 x RJ45 sockets with integrated switchAuto Negotiation SupportedAuto Crossover Supported







LED indicators LEDs SYSTEM System statusCONFIG Configuration statusMODBUS Modbus statusACTIVE Visualization statusLOAD File download status ACT Ethernet activity statusLNK Ethernet link statusFor details see section LEDs NSCDT52EN/ATVISE/OMB [ page 156]


© Hilscher 2010 – 2016


NSCDT52EN/ATVISE/OMB

Parameter Value

Power supply Voltage 18 – 30 V DCTypical current at 18 V 190 mATypical current at 24 V 130 mATypical current at 30 V 110 mAConnector COMBICON MC 1.5/5 5 pins





2 kV Power supply connector DC, Criterion B 1 kV Communication lines Ethernet, Criterion B


0.5 kV CM/DM Power supply connector DC,Criterion B1 kV CM Communication lines Ethernet, CriterionB




Table 57: Technical data NSCDT52EN/ATVISE/OMB


© Hilscher 2010 – 2016


13.5 Integrated WebServerTechnical data of the servX HTTP server version V1.1.0 (WebServerintegrated in the netSCADA devices)Parameter ValueSupported protocol HTTP/1.1 Hypertext Transfer Protocol

(RFC 2616)Number of connections Min. 3 browser connections at the same timeSupported HTTP methods: GET

HEADPOST

atvise webMI standard SupportedRequest URI to file system mapping SupportedMedia type recognition from filename suffix SupportedServer Side Includes (SSI) SupportedChunked Transfer Encoding Not supportedTable 58: Technical data of the integrated WebServer

13.6 Real time clockDevice Type Precision Power failuresafe Buffering SynchronizationNL 50NMPIATVISE

Softwaresupported

50ppm No No Manually or cyclicallyby SNTP(via 123/UDP port)NSCDT52 Hardware

supported20ppm Yes Min. 7 days,

maintenancefree bySuperCap

Table 59: Technical data real time clock

13.7 Supported web browserWeb browser supported by atvise with min. 3 simultaneously activeconnections:Browser VersionMicrosoft Internet Explorer 8 (with VML conversion), 9 and 10Mozilla Firefox 24Apple Safari 5.1.7Google Chrome 31Opera 16Blackberry 6 or 10Table 60: Web browser supported by atvise


© Hilscher 2010 – 2016

Disposal of waste electronic equipment 167/175

14 Disposal of waste electronic equipmentAccording to the European Directive 2002/96/EG “Waste Electrical andElectronic Equipment (WEEE)”, waste electronic equipment may not bedisposed of as household waste. As a consumer, you are legally obliged todispose of all waste electronic equipment according to national and localregulations.

Waste electronic equipmentThis product must not be treated as household waste.This product must be disposed of at a designated waste electronicequipment collecting point.


© Hilscher 2010 – 2016

Glossary 168/175

15 Glossary10Base T Standard for communication on Ethernet over twisted pair lines with RJ45 connectors and a

baud rate of 10 MBit/s (according to the IEEE 802.3 specification).100Base TX Standard for communication on Ethernet over unshielded twisted pair lines with RJ45

connectors and a baud rate of 100 MBit/s according to the IEEE 802 specification.atvise Package from the Austrian company Certec EDV GmbH (ThomasAlvaEdisonstrasse 1,

A7000 Eisenstadt, Austria, www.atvise.com). The most important part of atvise is the atvisebuilder, which is delivered with the netSCADA device.

atvise builder atvise builder is a software tool from the Austrian company Certec EDV GmbH (ThomasAlvaEdisonstrasse 1, A7000 Eisenstadt, Austria, www.atvise.com which can be used todesign web interfaces and create visualizations for devices in automation such as thenetSCADA.

atvise server atvise server is a component of the atvise software package. It runs permanently on the PCand can be accessed via its icon in the icon tray. If the icon is green, the server is running.

atvise webMI atvise webMI is a set of rules with which Web servers must comply if they are used inconjunction with the atvise builder.

AutoCrossover AutoCrossover is a feature of an interface: An interface with AutoCrossover capability willautomatically detect and correct if the data lines have been exchanged vice versa.

AutoNegotiation AutoNegotiation is a feature of an interface: An interface with Auto Negotiation willautomatically determine a set of correct communication parameters.

Baud rate Data transmission speed of a communication channel or interface.Boot loader Program loading the firmware into the memory of a device in order to be executed.DHCP Dynamic Host Configuration Protocol.

This is a protocol simplifying the configuration of IP networks by automatically assigning IPaddresses.

DHCP server A DHCP server assigns the IP addresses to the other devices within the respective IPnetwork.

Ethernet A networking technology used both for office and industrial communication via electrical oroptical connections. It has been developed and specified by the Intel, DEC and XEROX. Itprovides data transmission with collision control and allows various protocols. As Ethernet isnot necessarily capable for realtime application, various realtime extensions have beendeveloped.

Firmware Software running inside a device providing the basic functionality of this device. The firmwareis stored remanent in the flash memory circuit of the device. It can be updated by a firmwaredownload.

Firmware update Loading the firmware from an external storage to the flash memory circuit of the device.Flash memory A special kind of remanent (nonvolatile) electronic memory circuits.FTP A networking protocol for file transmission defined by the IETF Network Working Group in

RFC959.FTP server A software providing files to other software on other computers in the network (for instance, in

the Internet) requesting these files. The software requesting files is called FTP client.Gateway A device interfacing between two different communication standards. The netLINK SCADA

device is a gateway between the communication standards MPI and Ethernet, the netSCADAModbus device is a gateway between Modbus RTU and Ethernet.

HTTP Hypertext Transfer Protocol. This is a protocol for transmission of web pages (HTMLdocuments). It is defined by the IETF Network Working Group in RFC 2616.

HTTP server A software providing web contents (HTML documents, graphics, JavaScript contents) onrequest via HTTP.

Hub A network component connecting multiple communication partners with each other. A hubdoes not provide own intelligence, thus it does not analyze the data traffic and sends receiveddata to all connected communication partners. A hub can be used for setting up a startopology.

IP address Address within IP (the Internet Protocol, part of TCP/IP). An IP address consists of 4 decimalvalues. Each of these must be in the range between 0 and 255. In the usual representation,these 4 decimal values are separated by points.

Javascript A programming language for creating dynamic and interactive web contents.


© Hilscher 2010 – 2016



Glossary 169/175

LAN Scanner andConfiguration Tool

The Ethernet Device Configuration Tool allows users to temporarily adjust the IP address ofnetXbased devices in TCP/IP networks. It is an easy to use configuration tool for theinstallation and configuration of the netSCADA device.

MPI Multi Point Interface The MPI is a proprietary interface of the SIMATIC S7 series of PLCs. It is compatible toPROFIBUS and based on RS485. It usually works with a transmission rate of 187.5 kBaud.

netX networX on chip, next generation of communication controllers.Nonvolatile See Remanent.PLC Programmable Logic Controller

A digitally programmed device for controlling a machine or facility.Remanent Remanent memory holds its data even after poweroff, for instance flash memory is

remanent. It is also called nonvolatile memory.RJ45 A connector type often used for Ethernet connection. It has been standardized by the Federal

Communications Commission of the USA (FCC).RoHS Restriction of Hazardous Substances

This abbreviation denominates the directive of the European Union on the use of 6 hazardoussubstances in electronic products. It is titled “Directive on the restriction of the use of certainhazardous substances in electrical and electronic equipment2002/95/EC”, adopted in 2003and was getting effective on 1 July 2006.

SCADA Supervisory Control and Data AcquisitionA concept for control and data acquisition of technical processes.

SNTP Simple Network Time ProtocolNetworking protocol for clock synchronization between computer systems over packetswitched data networks.

STEP 7 Programming language for the SIMATIC S7 Series of PLCs.SVG Scalable Vector Graphics

SVG is a standard for freely scalable vector graphics based on XML which has beenpublished by the World Wide Web Consortium (W3C). It defines a description language forgraphical and multimedia objects allowing you to create highquality graphical output in anysize easily. It is ideally suited to create GUIs for humanmachine interfaces.

Switch A network component connecting multiple communication partners (or even entire branchesof a network) with each other. A switch is an intelligent network component which analyzesnetwork traffic in order to decide on its own. For the connected communication partners aswitch behaves transparently.

Symbolizer A tool written and supplied by Hilscher to be used to extract symbolic information from STEP7 project filers used in SIMATIC S7 PLCs and analyze this information for connecting it tographical displays in a GUI.

UTC Coordinated Universal Time Standard reference for worldwide regulation of clocks and time. For example: UTC minus 5hours equals U.S. Eastern Standard Time.


© Hilscher 2010 – 2016

List of figures 170/175

List of figuresFigure 1: Overview data flow of netLINK SCADA NL 50NMPIATVISE ............................ 17Figure 2: Overview data flow netSCADA NSCDT52RS/ATVISE/MBR ............................. 18Figure 3: Dimensional drawing NL 50NMPIATVISE ......................................................... 21Figure 4: Dimensional drawing NSCDT52.......................................................................... 21Figure 5: Connectors and LEDs NL 50NMPIATVISE........................................................ 22Figure 6: Connectors and LEDs NSCDT52RS/ATVISE/MBR........................................... 23Figure 7: Connectors and LEDs NSCDT52EN.................................................................. 24Figure 8: Galvanic isolations NL 50NMPIATVISE............................................................. 29Figure 9: Galvanic isolations NSCDT52RS/ATVISE/MBR ................................................ 30Figure 10: Galvanic isolations NSCDT52EN....................................................................... 31Figure 11: Mounting NL 50NMPIATVISE ............................................................................ 32Figure 12: Mounting NSCDT52 ............................................................................................ 33Figure 13: Dismounting NSCDT52 ....................................................................................... 34Figure 14: Start screen netSCADA DVD ............................................................................... 36Figure 15: atvise installation program.................................................................................... 36Figure 16: Save nodes file dialog .......................................................................................... 37Figure 17: Open Project Console via Windows Start menu................................................... 39Figure 18: Menu of Project Console ...................................................................................... 39Figure 19: Project Console .................................................................................................... 40Figure 20: Add webMI Server dialog ..................................................................................... 41Figure 21: Start screen atvise builder .................................................................................... 42Figure 22: webMI Server dialog window................................................................................ 43Figure 23: LAN Scanner and Configuration Tool (1) ............................................................. 44Figure 24: LAN Scanner and Configuration Tool (2) ............................................................. 44Figure 25: Set IP address ...................................................................................................... 45Figure 26: webMI Server dialog............................................................................................. 47Figure 27: Selecting S7 project dialog ................................................................................... 48Figure 28: Acquire data points............................................................................................... 49Figure 29: Import variables from netSCADA ........................................................................ 49Figure 30: GUI of the Symbolizer .......................................................................................... 50Figure 31: Add Server............................................................................................................ 55Figure 32: webMI Server dialog............................................................................................. 56Figure 33: PROFIBUSMPI parameters ................................................................................ 58Figure 34: Signal Editor ......................................................................................................... 60Figure 35: Signals in project tree ........................................................................................... 62Figure 36: Add Server............................................................................................................ 64Figure 37: webMI Server dialog............................................................................................. 65Figure 38: RFC 1006 parameters .......................................................................................... 67Figure 39: Signal Editor ......................................................................................................... 68Figure 40: Signals in project tree ........................................................................................... 70


© Hilscher 2010 – 2016


Figure 41: Add Server............................................................................................................ 72Figure 42: webMI Server Dialog ............................................................................................ 73Figure 43: Modbus TCP parameters dialog for client ............................................................ 75Figure 44: Acquire data points............................................................................................... 77Figure 45: Open Signal Editor ............................................................................................... 77Figure 46: Signal Editor Modbus TCP/IP Client..................................................................... 78Figure 47: Signals in project tree ........................................................................................... 80Figure 48: Signal Editor Modbus TCP/IP Server ................................................................... 80Figure 49: Signals in project tree ........................................................................................... 82Figure 50: Add Server............................................................................................................ 84Figure 51: webMI Server Dialog ............................................................................................ 85Figure 52: Modbus parameter dialog for master device ........................................................ 87Figure 53: Acquire data points............................................................................................... 89Figure 54: Open Signal Editor ............................................................................................... 89Figure 55: Signal Editor Modbus RTU Master ....................................................................... 90Figure 56: Signals in project tree ........................................................................................... 92Figure 57: Signal Editor Modbus RTU Slave ......................................................................... 92Figure 58: Signals in project tree ........................................................................................... 94Figure 59: CSV text file.......................................................................................................... 96Figure 60: CSV depicted as table in Excel ............................................................................ 96Figure 61: Values of CSV file in Signal Editor ....................................................................... 96Figure 62: Add server ............................................................................................................ 103Figure 63: Edit server ............................................................................................................ 103Figure 64: webMI Server configuration dialog window .......................................................... 104Figure 65: File selection dialog .............................................................................................. 105Figure 66: Open Symbolizer .................................................................................................. 106Figure 67: Symbolizer............................................................................................................ 106Figure 68: Select signals ....................................................................................................... 107Figure 69: Symbols imported................................................................................................. 107Figure 70: Main Display ......................................................................................................... 108Figure 71: Create new graphic display .................................................................................. 109Figure 72: Name of display dialog ......................................................................................... 109Figure 73: New display in project tree ................................................................................... 110Figure 74: Graphics editor of atvise builder ........................................................................... 111Figure 75: Select element...................................................................................................... 112Figure 76: Drag and drop element onto the display............................................................... 113Figure 77: Assign attributes to element ................................................................................ 113Figure 78: Assign signal to element....................................................................................... 114Figure 79: Save display in atvise builder ............................................................................... 114Figure 80: Alarm management .............................................................................................. 116Figure 81: Select signal ......................................................................................................... 116


© Hilscher 2010 – 2016


Figure 82: Add new alarm messages .................................................................................... 117Figure 83: Trend library ......................................................................................................... 119Figure 84: netSCADA trend display....................................................................................... 119Figure 85: Assign signal to element....................................................................................... 120Figure 86: Generate and download HTML pages ................................................................. 121Figure 87: Generating and downloading project message .................................................... 121Figure 88: Download failure message ................................................................................... 122Figure 89: Open web browser in atvise builder ..................................................................... 123Figure 90: Example of visualization web page with trend...................................................... 123Figure 91: Start page Web Configuration Interface ............................................................... 125Figure 92: Home page of the Web Configuration Interface ................................................... 129Figure 93: Network Settings ................................................................................................. 130Figure 94: Firmware update page.......................................................................................... 132Figure 95: Transfer of firmware succeeded message ........................................................... 134Figure 96: Device reset.......................................................................................................... 135Figure 97: System time.......................................................................................................... 136Figure 98: Trend Recording................................................................................................... 139Figure 99: Erase application page ......................................................................................... 142Figure 100: Factory Restore .................................................................................................... 144Figure 101: ComProX start screen .......................................................................................... 146Figure 102: ComProX Connection Dialog................................................................................ 146Figure 103: ComProX File Explorer......................................................................................... 147Figure 104: ComProX download.............................................................................................. 147Figure 105: File selection dialog .............................................................................................. 147Figure 106: Downloaded firmware file in Explorer ................................................................... 148


© Hilscher 2010 – 2016

List of tables 173/175

List of tablesTable 1: List of revisions........................................................................................................ 5Table 2: Reference on hardware and firmware ..................................................................... 7Table 3: Reference on software ............................................................................................ 7Table 4: Directory of the netSCADA product DVD ................................................................ 8Table 5: Dokumentation overview ......................................................................................... 8Table 6: Safety Symbols and Sort of Warning or Principle ................................................... 15Table 7: Signal Words ........................................................................................................... 15Table 8: Connectors and LEDs NL 50NMPIATVISE .......................................................... 22Table 9: Connectors and LEDs NSCDT52RS/ATVISE/MBR.............................................. 23Table 10: Connectors and LEDs NSCDT52EN .................................................................... 24Table 11: Data of Ethernet connection.................................................................................... 25Table 12: RJ45 Ethernet pin assignment ................................................................................ 25Table 13: Description PROFIBUS interface (DSub Connector, 9 pin) ................................... 26Table 14: Pinning PROFIBUS MPI interfaces (DSub female and male connector, 9 pin) ..... 26Table 15: Pin assignment RS232 interface (COMBICON socket, 5pole) ............................. 27Table 16: Pin assignment RS422 interface (COMBICON socket, 5pole) ............................. 27Table 17: Pin assignment RS485 interface (COMBICON socket, 5pole) ............................. 28Table 18: Pin assignment Mini Combicon socket 2pole......................................................... 28Table 19: Pin assignment Mini Combicon socket 5pole......................................................... 29Table 20: Coupling NL 50NMPIATVISE ............................................................................... 29Table 21: Coupling NSCDT52RS/ATVISE/MBR................................................................... 30Table 22: Coupling NSCDT52EN ......................................................................................... 31Table 23: Further control elements of the Symbolizer............................................................. 51Table 24: Simple STEP 7 data types ...................................................................................... 52Table 25: Parameters PROFIBUS MPI ................................................................................... 59Table 26: Columns in Signal Editor ......................................................................................... 61Table 27: Control elements in the Signal Editor ...................................................................... 61Table 28: PROFINET/RFC 1006 Parameters ......................................................................... 67Table 29: Columns in Signal Editor ......................................................................................... 68Table 30: Control elements in the Signal Editor ...................................................................... 69Table 31: Modbus TCP/IP Parameters ................................................................................... 76Table 32: Columns in Signal Editor Modbus TCP/IP Client .................................................... 79Table 33: Control elements in the Signal Editor ...................................................................... 79Table 34: Columns in Signal Editor Modbus TCP/IP Server ................................................... 81Table 35: Control elements in the Signal Editor ...................................................................... 81Table 36: Parameters Modbus RTU........................................................................................ 87Table 37: Columns in Signal Editor Modbus RTU Master....................................................... 91Table 38: Control elements in the Signal Editor ...................................................................... 91Table 39: Columns in Signal Editor Modbus RTU Slave......................................................... 93Table 40: Control elements in the Signal Editor ...................................................................... 93


© Hilscher 2010 – 2016

List of tables 174/175

Table 41: CSV file for Modbus TCP Client .............................................................................. 97Table 42: CSV file for Modbus TCP Server............................................................................. 99Table 43: CSV file for Modbus RTU Master ............................................................................ 100Table 44: CSV file for Modbus RTU Slave .............................................................................. 102Table 45: Web pages of the Web Configuration Interface ...................................................... 125Table 46: Parameter Network Settings ................................................................................... 131Table 47: Control elements Network Settings ......................................................................... 132Table 48: Trend settings parameters ...................................................................................... 140Table 49: Control elements Trend Settings............................................................................. 141Table 50: LEDs NL 50NMPIATVISE..................................................................................... 151Table 51: LEDs NSCDT52RS/ATVISE/MBR ........................................................................ 152Table 52: LEDs NSCDT52EN/ATVISE/PN ........................................................................... 154Table 53: LEDs NSCDT52EN/ATVISE/OMB........................................................................ 156Table 54: Technical Data NL 50NMPIATVISE...................................................................... 158Table 55: Technical data NSCDT52RS/ATVISE/MBR ......................................................... 160Table 56: Technical data NSCDT52EN/ATVISE/PN ............................................................ 162Table 57: Technical data NSCDT52EN/ATVISE/OMB ......................................................... 164Table 58: Technical data of the integrated WebServer ........................................................... 166Table 59: Technical data real time clock ................................................................................. 166Table 60: Web browser supported by atvise .......................................................................... 166


© Hilscher 2010 – 2016

Contacts 175/175

Contacts

HEADQUARTERS

GermanyHilscher Gesellschaft für Systemautomation mbHRheinstrasse 15D65795 HattersheimPhone: +49 (0) 6190 99070Fax: +49 (0) 6190 990750EMail: [email protected]: +49 (0) 6190 990799EMail: [email protected]

SUBSIDIARIES

ChinaHilscher Systemautomation (Shanghai) Co. Ltd.200010 ShanghaiPhone: +86 (0) 2163555161EMail: [email protected]: +86 (0) 2163555161EMail: [email protected]

FranceHilscher France S.a.r.l.69500 BronPhone: +33 (0) 4 72 37 98 40EMail: [email protected]: +33 (0) 4 72 37 98 40 EMail: [email protected]

IndiaHilscher India Pvt. Ltd.Pune, Delhi, MumbaiPhone: +91 8888 750 777EMail: [email protected]

ItalyHilscher Italia S.r.l.20090 Vimodrone (MI)Phone: +39 02 25007068EMail: [email protected]: +39 02 25007068EMail: [email protected]

JapanHilscher Japan KKTokyo, 1600022Phone: +81 (0) 353620521EMail: [email protected]: +81 (0) 353620521EMail: [email protected]

KoreaHilscher Korea Inc.Seongnam, Gyeonggi, 463400Phone: +82 (0) 317893715EMail: [email protected]

SwitzerlandHilscher Swiss GmbH 4500 SolothurnPhone: +41 (0) 32 623 6633EMail: [email protected]: +49 (0) 6190 990799EMail: [email protected]

USAHilscher North America, Inc. Lisle, IL 60532Phone: +1 6305055301EMail: [email protected]: +1 6305055301EMail: [email protected]


© Hilscher 2010 – 2016

mailto:[email protected]
















netscada devices with atvise builder - hilscher.com · user manual netscada devices with atvise...

Documents