quickstart kursus_manual v1.pdf

8/10/2019 Quickstart kursus_manual v1.pdf

1/144


2/144

1 Project Creation and Interface

Functionalities of Visu+

Project Wizard

Basic Tools

Project Explorer

2 Initial Steps for Visualization Creation

and Animations

Data Basis for Communication Objects

Project Resources

Process Screen Creation

Selected Animations

3 Selected Data and User Management

Alarm Management

Language Management

User and User Groups

Data Recording

Trend RecordingRecipes

4 Transferring a Project to a Touch Panel

A1 AX OPC Server

Configuration of the AX OPC Server

OPC Preparation on the Control System Side

OPC Configuration Check with AX OPC TestClient

A2 Tasks

A3 Solut ions

No part of this document may be reproduced,

stored in a retrieval system or transmitted in any

form or by any means, electronic, mechanical,

photocopying, recording or otherwise, without the

prior permission in writing of the Publisher.

Violations shall give rise to claims for damages. All

rights reserved.

All other product names are trademarks or

registered trademarks of their respective

companies, and they are used withoutrepresentation as to their general use.

2009 by Phoenix Contact GmbH & Co. KG

Visu+ User Course

Speaker:_____________________

CCAX / Competence Center

AUTOMATIONWORXPlease contact us if you have any questions

or suggestions: 05281 946 2101

_____________________________________

_____________________________________

IB2041 V1.0


3/144

_____________________________________Project Creation and Interface

1 - 1

_____________________________________

Project Creation and Interface

Chapter 1

V1.0


4/144


1 - 2

_____________________________________

Notes:


5/144


1 - 3

_____________________________________

Contents

This chapter takes you through the first steps of the project creation wizard and describes the basicfunctionality and tools in Visu+.

Note: In order to efficiently work with the visualization, extending the desktop with a secondmonitor is recommended. As a basis for the data link, the system variable structure fromVisu+ can be used for simulation as an alternative to an automation project.


6/144


1 - 4

_____________________________________

Notes:


7/144


1 - 5

_____________________________________

Functionality of Visu+


8/144


1 - 6

_____________________________________

Basic Functions

Full SCADA functionality

Multilingual software and projects Projects encryption

Project compression

Control coupling with OPC

Access protect ion with user management

Web Client capabili ty

Fully scalable process screens

Real time database connection

Automat ic data recording and recipe management

Scripts can be created in VBA and IL

FDA CRF 21 part 11 compatible

Visu+ provides full SCADA (Supervisory Control And Data Acquisition) functionality withvisualization, trend display and alarm management. The software is multilingual and supports morethan one language in a project. Because of the possibility for project encryption, know-how is safely

protected and project compression saves resources. With the help of OPC, Visu+ can be easilycoupled to control systems and supports databases linking with ODBC to MS ACCESS, MS-EXCELand SQL server. Generated process screens are fully scalable and therefore ideally suited for usewith own designs on various large devices. Together with Web Client capability, Visu+ alsoprovides access protection with user management, automatic data recording and recipemanagement as well as the possibility to create scripts in VBA and IL and FDA CRF 22 part 11compatibility.


9/144


1 - 7

_____________________________________

Runtime Licenses

Without limit for I/O data and variables in scripting,SMS, voice, fax, modem connection, 1 web client user

RT PRO XT

Without limit for I/O data and variables in scriptingRT PRO

Limited to 512 bytes for I/O data and variables in scripting,

SMS, voice, fax, modem connection, 1 web client userRT BASIC XT

Limited to 512 bytes for I/O data and variables in scriptingRT BASIC

Limited to 128 bytes for I/O data and variables in scripting,

SMS, voice, fax, modem connection, 1 web client userRT LITE XT

Limited to 128 bytes for I/O data and variables in scriptingRT LITE

DescriptionType

An overview of the various different runtime licenses that are available for Visu+ is shown above.


10/144


1 - 8

_____________________________________

Notes:


11/144


1 - 9

_____________________________________

Project Wizard


12/144


1 - 10

_____________________________________

Notes:


13/144


1 - 11

_____________________________________

Target System

The first step in creating a visualization project under Visu+ is to select the target system to beused. A TP Panel with Windows CE is used in the training session on which visualization can beperformed in full-screen display.


14/144


1 - 12

_____________________________________

Project Directory

After entering a name, a directory should be chosen that enables better access to the data than thestandard project directory. This is related to the install path of the software.


15/144


1 - 13

_____________________________________

Project Protection

The VISU+ visualization project can be protected on individual levels from unauthorized operationvia Windows user management.

Initially it makes sense to remove protection for development purposes. In particular if the

protection is performed via Windows management since the development computer is usually notthe computer on which the visualization will subsequently be executed in runtime mode.


16/144


1 - 14

_____________________________________

Driver Selection

Together with communication via OPC, visualization can be linked to the process using additionaldrivers.


17/144


1 - 15

_____________________________________

Process Screens

In addition to the possibility for adding process screens to an existing project, the start-up wizardalso provides an option to insert process screens together with the necessary navigation bars forselection of them. The screen size used later in the project is based on the screen resolution. This

is 800x600 pixels in the case of the TP panel.


18/144


1 - 16

_____________________________________

Protocol Databases

Despite deselecting, the event protocol database is always created.

In the case of registered user accounts, tracing allows subsequent reconstruction of which user

executed which actions via the visualization and at what point in time. Tracing is set up in the RealTime DB section of the project explorer and must be selected for each single variable.


19/144


1 - 17

_____________________________________

Data Recording Database

The data recording database makes sections available in the project explorer to which variablescan be forwarded for recording. As in previous selection items, subsequent modifying and editing ispossible at any time.


20/144


1 - 18

_____________________________________

Alarm Templates

Two typical alarm elements of the project explorer structure are added via selection of theseoptions.


21/144


1 - 19

_____________________________________

Basic Tools


22/144


1 - 20

_____________________________________

Notes:


23/144


1 - 21

_____________________________________

Project Explorer

ResourcesResources

CommandsCommands

As management tool, the project explorer allows structured access to all existing elements in theproject. It is separated in the element and methods sections, whereby the latter makes context-related function of the selected elements available.


24/144


1 - 22

_____________________________________

Properties

Just like the project explorer methods, the properties dialogue window also shows the context-related values of the elements selected in the project explorer.

Confirm (confirm data entered)Deleting

Categorized (displayed elements sorted according to categories)

Alphabetic (sorting)

Expand/collapse (open/close tree structure)

Description area (show/hide)

Help (F1)

Simplified display (most used elements only)


25/144


1 - 23

_____________________________________

Tool Box

The tool box makes basic elements available for creating the visualization screen.


26/144


1 - 24

_____________________________________

Template Library

The template library provides plenty of predefined objects of which some already have animations.Further symbols and symbol library can be added or created by the user himself.


27/144


1 - 25

_____________________________________

Window Arrangement

ResultResult

The above displayed symbol is displayed during moving of tools. By positioning the mouse pointerover the five direction arrows, the selected window can be integrated within the framework ofanother window (depending on the selected direction, simultaneously) or via tabs (when selecting

the circle). Windows can be subsequently removed via their title bar.


28/144


1 - 26

_____________________________________

Notes:


29/144


1 - 27

_____________________________________

Project Explorer


30/144


1 - 28

_____________________________________

Notes:


31/144


1 - 29

_____________________________________

Project Explorer 1/2

Alarm List

Contains the digital and analog signals, that are to be monitored according to their limits by VISU+(basic setting via project wizard).

Basic Scripts

The VBA code that is to be executed on command or at the start of a visualization can be storedhere.

Users And User Groups

For definition of access rights (basic setting via project wizard).

Data Logger and Recipes

Defines trend recording of stored signals (basic setting via project wizard).

Event Object ListStored events can trigger actions.

Communication Objects

Linked to SPS via driver, variable linking and user-defined data types, internal variable storage ofthe project.

Keyboard Shortcuts

Adding a keyboard shortcut to a project.

Menus

Allows creation and activating of pop-up menus with the mouse as well as adjusting menu bars that

link to process screens.


32/144


33/144


1 - 31

_____________________________________

Notes:


34/144


35/144

_____________________________________Visualization Creation and Animations

2 - 1

_____________________________________

First Steps in Visualization Creationand Animations

Chapter 2

V1.0


36/144


2 - 2

_____________________________________

Notes:


37/144


2 - 3

_____________________________________

Contents

This chapter describes the first steps for setting up a visualization project like, for instanceintegration of OPC variables and provides an overview on various animations that could be usedwithin a process screen.


38/144


2 - 4

_____________________________________

Notes:


39/144


2 - 5

_____________________________________

Real Time DBData Basis


40/144


2 - 6

_____________________________________

Notes:


41/144


2 - 7

_____________________________________

Structure

Real Time DB

Variable database

Variable in Visu+

Variable in an SPS

automation

project

OPC tag

in the AX OPC

server

It is recommended to create a data basis in the Real Time DB of the Visu+ project for a systematicprocedure with existing automation projects including OPC data structure. For this, OPC tags of theserver are mapped to communication object variables.


42/144


2 - 8

_____________________________________

Variable Groups and Variables

11

22

In the case of larger projects, it is recommended adding a variable group from the context menu ofthe variable database (Real Time DB element of the project explorer) in order to maintain anoverview of a large number of the variables. Local Visu+- variables can also be added from this

context menu. Variables with OPC connection should however be added via the OPC Client DAsection and edited in the variable database.


43/144


2 - 9

_____________________________________

OPC Variable Creation

Adding an OPC element to a project while creating a VISU+ variable is performed with the help ofthe tag browser. The tag browser lists the communication paths that are available to Visu+. Accessto the OPC server registered on the PC is gained via Local (My Computer). For the purposes of this

training session, the AUTOMATIONWORX OPC server is used which represents the projectstructure of the application programmed by PC WORX with respect to the OPC data. As is the casewith the Testclient which is a part of the AX OPC server installation, the server functions and valuesor the values made available to it can be checked with the tag browser (Option: current values).

Several OPC tags can be simultaneously transferred.

Under certain circumstances, arrays and structures from the application project can also be used inVisu+.


44/144


2 - 10

_____________________________________

OPC Group with Tags

Those variables added are served by the refresh rate (in ms) of the OPC group.


45/144


2 - 11

_____________________________________

OPC Tag and Variable

If the name of a variable in the variable list under Visu+ 2.0 is changed, connection to the OPC tagwill be maintained. After any move operation, for instance in groups, OPC tags must besubsequently reconnected to the renamed variable.


46/144


2 - 12

_____________________________________

Structure (Variables)

Structure definitionStructure definition

Variable declarationVariable declaration

In addition to variables that are based on elementary data types, there is also the possibility tointegrate structure and field variables into Visu+ . The basis for this is the definition of a Visu+-structure. Correct data transfer of the identical structure format according to the data type

declaration in PC WORX must be observed.

Automatically generated variables that are not based on elementary data types must be set to thecorrect type.


47/144


2 - 13

_____________________________________

System Variables

Visu+ makes basic information available to the user in the system variable structure of thevisualization application. After adding the system variable structure, the corresponding variable isautomatically ready. As with user-declared variables, access to single elements of these variables

occurs via the tree structure of the tag browser.


48/144


2 - 14

_____________________________________

Standard Object List

The standard object list can be used in order to make OPC tag raw sizes available in Visu+ instandard form.


49/144


2 - 15

_____________________________________

Project Resources


50/144


2 - 16

_____________________________________

Notes:


51/144


2 - 17

_____________________________________

Project Explorer - Project Resources

All existing elements in the project (process screens, folders, scripts, popup menus etc.) are listedunder Screens. The example shows resources generated by the tasks (six process screens withembedded tool bar).


52/144


2 - 18

_____________________________________

Notes:


53/144


2 - 19

_____________________________________

Process Screen Creation


54/144


2 - 20

_____________________________________

Notes:


55/144


2 - 21

_____________________________________

Process Screen

Embedded

navigation

Embedded

navigation

Process screens set up by the project wizard are equipped with navigation buttons as well as titlebars by default. The former is made available via their own embedded process screen in the size ofthe required buttons.


56/144


2 - 22

_____________________________________

Object Properties

The parameters made available to the object as well as the animation possibility can be called upunder Properties. If present, animations must be switched to active.

Correction for a pixel-exact creation of the visualization is provided via the parameters in thePosition (X/Y/width/height) section.


57/144


2 - 23

_____________________________________

Selected Animations


58/144


2 - 24

_____________________________________

Notes:


59/144


2 - 25

_____________________________________

Visible

The Visible animation allows hiding of an object independent of a variable and its accordance toanimation conditions.


60/144


2 - 26

_____________________________________

Composed Movement

The composed movement animation puts an object into a position to follow a path graphicallydetermined by the user that is independent of a variable value. Beginning from the initial position ofthe object, further items can be successively added to the path.


61/144


62/144


2 - 28

_____________________________________

X Start Point

The X start point animation (similarly the Y start point, X end point and Y end point) changes thecoordinate of the left outer border of an object. This is pixel-based as with the X/Y movements. Thedependent variable is also to be scaled if necessary.


63/144


2 - 29

_____________________________________

Scaling

Scaling changes the size of the selected object. As opposed to previously mentioned animations,scaling is performed in percentage terms. The direction of scaling of a Visu+ object depends on thevariables and can be selected from a number of different options.


64/144


2 - 30

_____________________________________

Rotating

Here the point of

rotation is the X-Y

position of the

rectangle

Here the point of

rotation is the X-Y

position of the

rectangle

As with the X-Y movement, the process size and the desired angle must however be put intorelation in the case of rotation as animation of an object. The point of rotation arises from theselection of the Barycenterparameter in the General section. The rotation animation is not available

when a Windows CE platform has been selected.


65/144


2 - 31

_____________________________________

Background Color

The Background color animation allows a changing the color of an object depending on a digitalsignal or an analog color change for analog values. A special option for determining other variablesin the same selected alarm group is possible via the Variable is alarm group parameter.


66/144


67/144


68/144


2 - 34

_____________________________________

Notes:


69/144

_____________________________________Selected Data and User Management

3 - 1

_____________________________________

Selected Data and User Management

Chapter 3

V1.0


70/144


71/144


3 - 3

_____________________________________

Contents

This chapter provides an overview of some selected functions in Visu+. This includes for example,simple standardization of data, alarm and user management as well as language switching in theproject and recording of data.


72/144


3 - 4

_____________________________________

Notes:


73/144


3 - 5

_____________________________________

Command List

The command list is available for a large number of events, where the user can execute variousdifferent actions.


74/144


3 - 6

_____________________________________

Standardization

The standardization list allows transmitted raw sizes e.g. from analog values to be easily scaled.New variables must be assigned to the standardized values.


75/144


3 - 7

_____________________________________

Alarm Management


76/144


3 - 8

_____________________________________

Alarm List

Standard elements

by the project wizard

Standard elements

by the project wizard

As is usual with other systems, alarms are available for processing both analog and digital signals.The typical threshold values provided by the project wizard can be extended by user-definedthresholds if necessary. The Alarm Variable parameter is to be connected to the variable to be

monitored. The switch-on variable should only be assigned if the alarm is to be conditionallytriggered.


77/144


3 - 9

_____________________________________

Alarm Window

The alarm window lists all pending alarms according to the alarm list and conditions. Depending onaccess level, it is possible to acknowledge alarm messages (tracing according to registered user).

The Select Field column configuration is called via the Open parameter in the General section. If a

text has been entered into the alarm properties under General Alarm Help, it will be displayed bydouble-clicking the alarm text in the alarm window.


78/144


3 - 10

_____________________________________

Notes:


79/144


3 - 11

_____________________________________

Language Management


80/144


3 - 12

_____________________________________

Notes:


81/144


3 - 13

_____________________________________

Switching Languages 1

Switching languages during the project process can be performed with the character sequencetable. New columns and rows can be added via the context menu. The character sequence ID canthen be used as an object in the project that outputs the selected column. The cell content can be

edited if the cell is marked and clicked again after a short wait.


82/144


3 - 14

_____________________________________

Switching Languages 2

The desired character sequence ID is selected in the Object properties under the General sectionand Object Title parameter. Now a new Language command type, for instance during release, willbe added under the Execute section where the character sequence table column was selected.


83/144


3 - 15

_____________________________________

Users and User Groups


84/144


3 - 16

_____________________________________

Notes:


85/144


3 - 17

_____________________________________

Adding a New User

A user group must be created before a user can be added. This group has an extendable standardlevel to which all users within the group have access. A standard access level can added exactly inthis way. Settings can be made for each user in a group whether he remains on the group level or is

assigned to another level. The access level for the selected user can be set under User AccessLevel. In order to be able to use password prompting, a password must be set for each user andthe password manager activated. The password manager is activated in the main User And UserGroup properties in the project explorer under the General section by adding a tick.


86/144


3 - 18

_____________________________________

Access and User Levels

There are 16 selectable access and 11 user levels. If a user is logged onto user level 8, he then hasaccess to all levels below that. A user logged onto user level 1 could only use the above buttonafter logging onto user level 2 and then only if he is authorized for access level 5. If a user is logged

onto user level 0, he will not be able to see the button on account of the set read access level.Access and user levels can be set in the properties of the Access levels section. Read and writelevels are displayed in hexadecimal format.


87/144


3 - 19

_____________________________________

User Logon and Logoff

11

If a user would like to press a button that is designed for a higher level, he must log onto a higherlevel (1). A login window will then automatically appear. Automatic logoff is set under the propertiesof the user to 60 seconds by default (auto logoff timeout (sec.)) and can be changed. There is a

possibility to log off via user commands in order to achieve immediate logoff (or login).


88/144


3 - 20

_____________________________________

Notes:


89/144


3 - 21

_____________________________________

Data Recording


90/144


3 - 22

_____________________________________

Notes:


91/144


3 - 23

_____________________________________

Data Logger

33 44 55

11 22

The data logger records data according to certain conditions. These must be assigned in the formof columns. Time or event dependent recording can be set. The data logger always writes to adatabase. This is SQL by default however a .dat file is written (IMDB) in the case of WinCE

platforms . Visu+ searches for a server and automatically creates a database with the name of theproject. The data can be displayed via a data logger window within Visu+.


92/144


3 - 24

_____________________________________

Data Logger Window

The data logger window can be found in the toolbox and displays the data of a selected data loggerin the process screen (Properties Execution section Data logger recipe parameter). Thedisplayed columns can be outputted in the same way as the alarm window. If visualization is

running, the display is not updated. The corresponding button must be pressed in order to displaythe current values.


93/144


94/144


3 - 26

_____________________________________

Adding a Variable for Tracing

In order to add a variable for tracing, a tick must be set underActivate tracing in the Trace Options(Audit) section. In addition, the data service life can be adapted to any necessities.

If the trace comments (audit) parameter has been activated, the user is requested to comment his

change before the change to the variable is performed.


95/144


3 - 27

_____________________________________

Trend Recording


96/144


3 - 28

_____________________________________

Notes:


97/144


3 - 29

_____________________________________

Trend Recording Window

In order to display a trend, the desired window is added from the toolbox into a process screenunder Trend-Charts-Data. The above example shows the Horizontal Trend window.


98/144


3 - 30

_____________________________________

Properties of the Trend Window

The trend type can be subsequently changed in the Properties of the trend window. The times andproperties of the recording are set under Execution. Depending on the setting, curves in the windoware displayed either drawn out or compressed together. In order to display lines, variables must first

be added as so-called pins. This is performed via the Edit Pens button. If the values of a datalogger are displayed as a trend, it is only necessary to add the data logger under Data Logger Link.This way the corresponding pins are created automatically and can then be adapted under EditPens if necessary.


99/144


100/144


3 - 32

_____________________________________

Notes:


101/144


3 - 33

_____________________________________

Recipes


102/144


3 - 34

_____________________________________

Notes:


103/144


104/144


3 - 36

_____________________________________

Activating Recipes

*Activate*

Variables must be specified under Recipe Temp. Variable and Variable for every column. Thetemporary variable is the variable that specifies a predefined value that is transferred to the variableunder the Variable item after activation of the recipe.

In order to activate the recipe, a variable is specified in the properties of the relevant recipe underthe Activate Variable item. If the value of the variables is set from 0 to 1, each of the individualtemporary values of the columns are written to the relevant specified variable. After execution,Visu+ automatically resets the variable.


105/144


3 - 37

_____________________________________

Recipe Examples

In the above example, the default values of the temporary recipe variables are specified on the left.Clicking the activation button confirms the corresponding recipe and displays it on the right.


106/144


3 - 38

_____________________________________

Notes:


107/144

_____________________________________Transferring a Project to a Touch Panel

4 - 1

_____________________________________

Transferring a Projectto a Touch Panel

Chapter 4

V1.0


108/144


4 - 2

_____________________________________

Notes:


109/144


4 - 3

_____________________________________

Contents

In this chapter it is explained how a Visu+- project is transferred to a visualization device such as atouch panel and how its network settings are modified.


110/144


4 - 4

_____________________________________

Notes:


111/144


112/144


4 - 6

_____________________________________

Access to the HMI Service Tool

The window shown above is displayed for two seconds. Click on Press For Setup Main Menu tostart the HMI Service Tool. If a key or button is not pressed within this two second period, theoperator panel returns to the start screen or the previously loaded project and the Visu+

visualization software is loaded with the current project.


113/144


4 - 7

_____________________________________

Setting the IP Address

In order to change the IP address, click the Setup Main Menu button in the HMI Service Tool andthe window will be displayed as shown above. Subsequently perform the steps shown above.

Note: In the case of TP operator panels, the software keyboard that is shown may hide theinput field. Move the keyboard so that it is above the title bar.

All addresses must be specified in xxx.xxx.xxx.xxx format. Numbers < 100 must be filled withleading zeros (example: 192.168.42.1 = 192.168.042.001)

Confirm the address entered with OK. You can return to the previous menu via Home.

Enter the corresponding subnet mask.

Press Exit and confirm the Save Registry? request with Yes.

Restart the device by disconnecting the 3-pos connector from the power supply andreconnecting.


114/144


4 - 8

_____________________________________

Resource (OPC) Settings

Settings for data transmission between the operator panel and visualization are performed in theResource Editor. To modify the Resource Editor, click on Setup Main Menu in the HMI ServiceTool. The menu shown above is opened. Perform the specified steps.

ClickAdd.

Enter the name of the OPC resource under Resource and confirm with OK.

Note: The same name must be displayed in Resource as for instance in the OPCconfigurator (AX-OPC-Server)

Enter the IP address of the Inline controller under Parameter (default: -ip127.0.0.1(local host)).

Click Save to save the settings.

Restart the device by disconnecting the 3-pos connector from the power supply andreconnecting.


115/144


4 - 9

_____________________________________

Transfer Project to the Operator Panel (1)

Once you have linked all the variables and saved the project, send the project to the operator panel.

Click on Example in the project explorer for this.

Click on Upload Project to Device/FTP under the Commands menu item.


116/144


4 - 10

_____________________________________

Transfer Project to the Operator Panel (2)

If a visualization is running on the operator panel, close this before transferring via the StopDevice button.

Click the TCP transfer type in the Upload Visu_Training window and subsequently Upload

project. Enter the IP address of the operator panel in the Server IP data window and click OK. The

project is uploaded to the operator panel.

After the Upload completed successfully message is displayed, click Start Device. The project isnow started on the operator panel.


117/144


4 - 11

_____________________________________

Notes:


118/144


4 - 12

_____________________________________

Notes:


119/144

_____________________________________AX OPC Server

A1 - 1

_____________________________________

AX OPC Server

Appendix 1

V1.0


120/144

_____________________________________AX OPC Server

A1 - 2

_____________________________________

Notes:


121/144

_____________________________________AX OPC Server

A1 - 3

_____________________________________

Configuration of the AX OPC Server


122/144

_____________________________________AX OPC Server

A1 - 4

_____________________________________

Notes:


123/144

_____________________________________AX OPC Server

A1 - 5

_____________________________________

Calling the OPC Configurator

In order to configure the OPC server, the configurator can be called under the above-mentionedpath. This path specification via the program menu is part of the standard installation.


124/144


125/144

_____________________________________AX OPC Server

A1 - 7

_____________________________________

Setting up a New Resource

The context menu of the workspace is used for adding a new resource. The resource representsthe CPU of the PC WORX project.


126/144

_____________________________________AX OPC Server

A1 - 8

_____________________________________

Selecting Control Systems

The AX OPC server works with a large number of current controllers of the AUTOMATIONWORXsystem.


127/144

_____________________________________AX OPC Server

A1 - 9

_____________________________________

Resource Name

The name can be changed by simply selecting another name. The "Description" window gives theresource's current communication parameters.

For the sake of clarity, the name should be identical to the resource name in thePC WORX project. There is however, no direct relationship between both names.

The status displays whether OPC data is made available online or offline (Settings), although not,whether a connection to the controller exists.


128/144

_____________________________________AX OPC Server

A1 - 10

_____________________________________

OPC Data Online

If the OPC server is to retrieve the data from the control system online, TCP/IP with the relevantaddress entry must be selected as the communication path.


129/144

_____________________________________AX OPC Server

A1 - 11

_____________________________________

OPC Data Off line

If the control system is not available at the time of creating the visualization, the PC WORX projectcan be used as the basis for the OPC data structure.


130/144

_____________________________________AX OPC Server

A1 - 12

_____________________________________

Notes:


131/144

_____________________________________AX OPC Server

A1 - 13

_____________________________________

OPC preparation onthe Controller Side


132/144


133/144

_____________________________________AX OPC Server

A1 - 15

_____________________________________

Designating Variables as OPC Variables

Data to be accessed by means of visualization must be furnished with the attribute OPC in the localand global variable table (box checked).


134/144

_____________________________________AX OPC Server

A1 - 16

_____________________________________

Sending the ConfigurationFile to the Control System

In order for the OPC server to load the OPC data structure from the control system, it must also bewritten to during the download.

In order to do this, mark the Include OPC data option during transmission of the project.


135/144

_____________________________________AX OPC Server

A1 - 17

_____________________________________

Checking OPC Configuration withAX OPC TestClient


136/144

_____________________________________AX OPC Server

A1 - 18

_____________________________________

Notes:


137/144

_____________________________________AX OPC Server

A1 - 19

_____________________________________

Call ing AX OPC TestClient

The AX OPC TestClient can be used to test OPC data exchange. It can be called via the pathshown above.

This path specification via the program menu is part of the standard installation.


138/144

_____________________________________AX OPC Server

A1 - 20

_____________________________________

Selecting the OPC server

Connection

to the server

Connection

to the server

Confirm the connection to the suggested OPC server (or to the one you have set).


139/144

_____________________________________AX OPC Server

A1 - 21

_____________________________________

Adding a Group

Right-click in the right-hand section of the window (Private Groups) to add a new group. You canthen confirm the above-shown dialog without entries with OK.


140/144

_____________________________________AX OPC Server

A1 - 22

_____________________________________

Adding all OPC variables

Select the group and right-click to open the context menu. Depending on your requirements, addone or all of the OPC variables (Items) to the group.


141/144


142/144

_____________________________________AX OPC Server

A1 - 24

_____________________________________

Current Value of OPC Variables

Current valueCurrent value

Break the

connection

Break the

connection

The current value will be displayed in the Function Result window area.

At tention: The value is not updated automatically!

At tention: Break the connection to the OPC Server before exiting the TestClient!


143/144

_____________________________________AX OPC Server

A1 - 25

_____________________________________

Notes:


144/144

_____________________________________AX OPC Server

Notes:

quickstart kursus_manual v1.pdf

Documents