1. Welcome Welcome to your PcVue Training course. This course was designed for new or inexperienced PcVue users. It focuses on how to create an application implementing the most common features of SCADA software. This course guide is provided in a USB stick which contains:
Folder Tools: contains all 3rd party tools needed.
Folder Modules: contains all course modules.
This course is organized in modules. Each module is a folder named Module_XX_Name where XX is a number and Name the module‟s name. Each of the module‟s folders contain:
A folder named “3rd Party” (optional): Contains any third party tools needed for the module.
A folder named “Project” (optional): Contains a PcVue project. This project can be used in exercising the actions the module describes.
File Module XX – Name – Basics.pdf: This is the course guide teaching the basics for the module.
File Module XX – Name – Advanced.pdf (optional): This is the course guide teaching some advanced features for the module.
This training course is based on version 10.0 of PcVue. We make every effort to have an up-to-date guide but if the current version is more recent than the one you are using, you may see minor differences in some screenshots. Please let the trainer know about these and we will make a note for the next revision of the guide. The operating system used was Microsoft Windows 7. If you are using another operating system you will find some differences in various screenshots (mainly in the „look and feel‟).
Pcvue Basics - Introduction
Page 3/9
2. Convention In each module you will see keywords and the path that you can use to search for additional information in our online Help documentation. We encourage you to use the Help both during and after the course since that is the most comprehensive and up-to-date source of information about how to use PcVue. When you are learning about a feature you will need to follow the trainer‟s instructions. To facilitate this, the trainer will describe the feature in a series of steps. In this guide each step is represented by this header:
Step 1.
Title of the step
a. Action to take b. Action to take Sometimes you have to select an option or click on a particular button, etc. This guide highlights with an underline the text you have to select or click.
Pcvue Basics - Introduction
Page 4/9
The guides use the following icons: Icon
Name Reminder
Warning
Description An important point to remember, or advice.
An important point to be aware.
Trick
A trick or tip.
Help
Keywords or path for further details in the Help.
Exercise
An exercise or action to do during the module.
Challenge!
A more difficult exercise for advanced trainees.
Question
Answer
Pcvue Basics - Introduction
A question related to the current module, asked by the trainer at the end. An area in the document for writing your answer.
Page 5/9
3. Interact with the guide Each course guide is a PDF file. Because each trainer has a style and tricks you will probably want to add some notes. We recommend using the PDF-XChange Viewer which is free software for reading PDF files. This tool makes it easy to add notes and comments directly to the file. Of course your files will be readable later with any PDF viewer such as Adobe PDF Reader. PDF-XChange Viewer is provided in the Training USB key in this folder: \Tools\PDFXchangeViewer. This version is the Portable version. It means you don‟t have to install it. To use it you have only to copy this folder to your computer and launch PDFXCview.exe To display the Comment toolbar select View/Toolbars/Comment and Markup toolbar.
Main actions available: Icon
Action Add a sticky note Add a free text Add a text box Add a text box with an arrow Highlight the selected text Add a Shape
Pcvue Basics - Introduction
Page 6/9
4. Schedule The complete training course lasts 5 days. This is the proposed schedule: DAY 1 Introduction Module 01 - Introduction - PcVue Setup Module 02 - PcVue Solutions presentation Morning (9:30 – 12:00)
Note: This module can be done during the PcVue Setup. Module 03 - Introduction - Version policy and licensing Module 04 - Introduction - PcVue and project concepts Module 05 - Introduction - Case Study
Afternoon (13:00 – 17:00)
Module 06 - Variables – Real time Database Module 07 - Communication - Common drivers Module 08 - Communication - OPC Day 2 Module 09 - HMI - Mimics
5. Prepare your computer for the training Now we can start our training! The first thing to do is to copy all the modules on to your computer.
Open Windows Explorer.
Create the Folder My Documents\ PcVue Training.
Copy from the USB key the Folder Modules in My Documents\ PcVue Training\
..... and let‟s go to Module 01!
Pcvue Basics - Introduction
Page 9/9
Introduction
Module 01 Setup
Contents
1.
Setup help
3
2.
System requirements
4
3.
Install PcVue
5
4.
Uninstall PcVue
7
5.
Reminder
8
Module 01 - Setup
Page 2/8
1. Setup help The complete set-up (installation) process is well documented in the Help. The best way of installing PcVue for the first time is to follow the procedures and screenshots described here. Insert the DVD and run the Setup.exe. The following dialog appears.
Figure 1
Select Installation and Help for installation.
Figure 2
Module 01 - Setup
Page 3/8
2. System requirements Before installing you must check the System Requirements in the topic “Operating System and PC Requirements”.
Module 01 - Setup
Page 4/8
3. Install PcVue Insert the Supervisor DVD into the DVD drive. If you have Auto Run enabled, the set-up program will automatically start, otherwise you can start the installation manually by locating and running SETUP.EXE from the DVD.
Step 1. Select Supervisor type Click Installation. Here you can select installation of the Normal Supervisor or the Web Supervisor. Click Install Supervisor.
If you need to use PcVue as a Web Server you must select Web Supervisor. Step 2. Setup Pre-requisites The set-up program checks the pre-requisites needed by PcVue and displays a dialog listing the pre-requisite that will be installed. All the pre-requisites are on the distribution media. Click Install to continue.
Figure 3
The list of pre-requisites is in this Help topic: Installing the Software / Starting the Installation and Installing the Pre-requisite Components The set-up program doesn’t install SQL Server Express Edition. Module 01 - Setup
Page 5/8
During the installation process for pre-requisites the PC may have to be restarted one or more times. When the installation of the components is complete, the main Supervisor installation procedure starts.
Step 3. Main PcVue set-up Select the language for the installation. As this course is in English, select English and then OK to continue. You may then be asked to install the protection key driver (Sentinel). Click Install to continue. The main PcVue Installation Wizard then starts. Click Next button until you reach the dialog box with the title: Product and Projects Folders. Click the Change button and select C:\Pcvue projects. Click the Next buttons until you reach the Ready To Install dialog and click the Install button The PcVue installation now proceeds.
Figure 4
We recommend that the default location is not used for the project folder. If you have more than one drive on your PC it is recommended that the project folder is NOT on the system drive. Don't select a network drive as a project location as it may result in erroneous behavior. Module 01 - Setup
Page 6/8
4. Uninstall PcVue You can uninstall PcVue, like any software, by using the Add/Remove tool of Windows.
The set-up program doesn’t uninstall any pre-requisties, the Sentinel driver (the dongle driver) or the BacNet server. These must be uninstalled separately.
Module 01 - Setup
Page 7/8
5. Reminder How to install PcVue? Select Supervisor type. Setup Pre-requisites. Main PcVue.
Module 01 - Setup
Page 8/8
Introduction
Module 02 PcVue Solutions
Contents
1.
PcVue Solutions
Module 02 - PcVue Solutions
3
Page 2/5
1. PcVue Solutions PcVue Solutions is an integrated suite of software and hardware for visualization, control, management and data analysis for industrial, building, energy, infrastructure and utilities applications. It includes the following software: PcVue PcVue is a complete suite of SCADA software (Supervisory Control And Data Acquisition). Its role is to:
Collect the data from equipment,
Manage alarms,
Archive data,
Display the real time and /or archived data in an attractive HMI.
WebVue The Web access solution:
Compatible with all Java compliant Web browsers,
No need to design a special Web application,
Some graphical limits are described in the Help.
PlantVue An HMI software. The main characteristics are:
It is an OPC client only,
It is stand-alone (no client/server architecture and no Web access),
It is limited in number of I/Os.
FrontVue An independent GUI for gathering data via OPC (OLE for Process Control). Dream Report A complete reporting tool running independently or communicating with PcVue. You can see an overview here: http://www.pcvuesolutions.com/index.php?option=com_content&view=article&i d=8&Itemid=21&lang=en IntraVue Automatic Topology and Graphical representation assists local resources who are not network TCP/IP experts easily respond to Ethernet communication issues. You can see an overview here: http://www.pcvuesolutions.com/index.php?option=com_content&view=article&i d=9&Itemid=158&lang=en Web Scheduler Scheduler with a Web interface. This product is bundled with PcVue. Module 02 - PcVue Solutions
Page 3/5
Alert Software for industrial On-call management. It is able to call people on-duty by phone, SMS, email etc. You can see an overview here: http://www.pcvuesolutions.com/index.php?option=com_content&view=article&i d=7&Itemid=156&lang=en
Module 02 - PcVue Solutions
Page 4/5
... and the following hardware: Brad Communication (Molex): Communication boards Moxa: communication switches for Industrial Ethernet.
Module 02 - PcVue Solutions
Page 5/5
Introduction
Module 03 Versions policy and Licensing
Contents
1 Versions policy 1.1
Component registration tool
2 Licensing
3 4
5
2.1
License type
5
2.2
I/O limits
5
2.3
Options
5
2.4
Dedicated licenses
5
3 Updating the license
Module 03 - Versions policy and Licensing
7
Page 2/7
1 Versions policy Each PcVue release is represented by a version number. The current version is 10.0.2476 where:
10 is the major version. A new major version is released when new important features are added.
0 is the minor version. A new minor version is released when new features are added.
2476 is the build number.
Several service packs (SP) can be added when we discover anomalies. For example we will have 10.0.xxxx SP1.
You don’t need to update the license when you add a service pack.
An application designed in a particular PcVue version is compatible with any more recent PcVue version.
Module 03 - Versions policy and Licensing
Page 3/7
1.1 Component registration tool If several PcVue versions have been installed in the same computer there is a problem with sharing their components. Each version uses a set of components registered with Microsoft Windows. The components have the same names irrespective of version and so before you start PcVue you have to be sure that the appropriate set is registered with Windows.
Figure 1
If you want to run PcVue in version X but the latest version that was run was version Y, you must run the Component Registration tool for version X before you run version X. To run the Component Registration tool click on: Start Menu\Programs\ARC Informatique\PcVue version\Tools\Component Registration
Module 03 - Versions policy and Licensing
Page 4/7
2 Licensing The price of a license depends on various factors, of which we will consider the most common. Please contact our Sales Department for further details. The license is coded in a physical protection key (also known as a dongle). USB and parallel port versions are available. Which you require is normally specified at order time.
2.1 License type
Runtime: Run-time environment only. You cannot modify the application.
Complete: Run-time and development environments. Usually each system integrator has at least one Complete dongle.
Development: Development environment with a time limited run-time dongle.
2.2 I/O limits Data collected from an external device is considered as input/output (I/O) irrespective of the communication method used or the type of data. The various licenses reflect to the quantity of I/O:
75 I/O,
250 I/O,
500 I/O,
1,000 I/O,
2,000 I/O,
5,000 I/O,
65,000 I/O,
Unlimited.
During startup PcVue counts the I/O configured in the application. If it is higher than the license, PcVue stops. Then you have to order an upgrade.
2.3 Options Various options are available. The most common are:
SV_NET: Able to manage a networked architecture (Client/Server),
WEBVUE: Web server and/or Web Services,
…
2.4 Dedicated licenses We provide licenses dedicated to specific uses. For example there is the Server license that is dedicated to a Server (no HMI). Module 03 - Versions policy and Licensing
Page 5/7
If you start PcVue without any dongle, it runs in Demo mode. In this mode PcVue operates as a Development license managing 25 I/O maximum and having 1 hour of communication.
Module 03 - Versions policy and Licensing
Page 6/7
3 Updating the license If you have to update the license, there is no need to change the dongle. Instead there is a procedure for upgrading it by software. This software is called the Remote License Manager. You can install it using the Drivers and utilities menu on the PcVue DVD. Then select Remote License Manager and follow the instructions. The procedure to update a license is:
Plug in the dongle to be updated.
Start the Remote License Manager and select Ask for license upgrade.
A file should be generated. Send it to our Sales department (with an order of course!). You will be sent a new file containing the upgraded license.
Start the Remote License Manager and select Upgrade my license now.
Configure the path for the file.
Your license has been updated!
Module 03 - Versions policy and Licensing
Page 7/7
Introduction
Module 04 PcVue and project concepts
Contents
1
2
Introduction 1.1 In this module you will learn how to
3
1.2 Files used in this module
3
1.3 Third party software used in this module
3
Project concepts 2.1 Deploy a project
3
3
Run PcVue
4 4
5
3.1 Shortcuts
5
3.2 Command line
7
3.3 Create a project
8
3.4 What is running?
9
3.5 Traces & logs
10
4
PcVue architecture
11
5
The Application Explorer
12
5.1 Main features
12
5.2 Using the Application Explorer
13
5.2.1 Opening and closing the Application Explorer
13
5.2.2 Changing the appearance of the Application Explorer
13
5.3 What can be configured from the Application Explorer?
Module 04 - PcVue and project concepts
14
Page 2/15
1 Introduction 1.1 In this module you will learn how to Run PcVue using various shortcuts, Collect the traces, Create a new PcVue project, Manage the Application Explorer.
1.2 Files used in this module None.
1.3 Third party software used in this module None.
Module 04 - PcVue and project concepts
Page 3/15
2 Project concepts A PcVue application is named a Project. Each project is contained within a Windows folder. All project folders are located in the root folder that you specified during the set-up or the one specified in the command line with the option –b. Because we have configured “C:\Pcvue projects” our projects must be located in “C:\Pcvue projects\USR\”. PcVue can run only 1 project at the same time.
Figure 1
The set-up program automatically installs the Demo project - SvHmiDemo
2.1 Deploy a project Because each project is in its own folder, deployment is very easy. You have only to copy the project folder to the target computer - that‟s all!
Module 04 - PcVue and project concepts
Page 4/15
3 Run PcVue 3.1 Shortcuts Several shortcuts are installed by the set-up program.
Figure 2
Hmi sample project: Run a demo which highlights the features of the HMI. PcVue: Run PcVue. Web sample project: Run a demo implementing WebVue access.
Module 04 - PcVue and project concepts
Page 5/15
Communication folder: Include shortcuts relative to the BACnet communication.
Figure 3
Documentation folder: The documentation in your chosen language. Documentation for other languages can be installed by re-starting the PcVue installation and selecting the Modify option.
Figure 4
Tools folder: Include shortcuts to launch extra tools.
Figure 5
Components registration: Launch the registration tool (described in Module 03 – Versioning and licensing).
Database Import: Launch the software used to restore database archives.
Database Manager: Launch the software used to manage the database archives.
Remote License Manager: Launch the software used to upgrade the license (described in Module 03 – Versioning and licensing).
Module 04 - PcVue and project concepts
Page 6/15
3.2 Command line The command line for PcVue is "C:\Program Files\ARC INFORMATIQUE\PCVUE …\bin\sv32.exe" -b "C:\Pcvue Projects" –s where: "C:\Program Files\ARC INFORMATIQUE\PCVUE ...\bin\sv32.exe" is the path of the executable. This folder is the one you selected during set-up. -b "C:\Pcvue Projects" is an option indicating to PcVue the path of the projects folder. This folder is the one you selected during set-up. –s opens a dialog box when PcVue starts so that the user can select an existing, or create a new, project. The main options are: Option
Description
-s
PcVue opens a dialog box for the user to select the project. This option is recommended for the designer.
-b “Folder_path”
PcVue uses the projects located in the folder “Folder_path”.
-p project_name
PcVue automatically loads the project project_name. This option is recommended on site.
Exercise 1.
Select the PcVue shortcut on your desktop. Check the options configured by default. Run PcVue. (In the Select Project dialog, select Demo version then OK).
Module 04 - PcVue and project concepts
Page 7/15
3.3 Create a project For our training we are going to create a new project named TRAINING. There are several ways to do it. Using Windows Explorer to create a new folder in “C:\Pcvue projects\USR\TRAINING”, Using the PcVue HMI.
Run PcVue. Select Demo version.
In the Select Project dialog„s Project field, type TRAINING.
Figure 6
Click the OK button and confirm.
Switch off PcVue by pressing the F10 key or by selecting the menu File/Exit or clicking the icon
.
Now a new project has been created. We can see a new folder “C:\Pcvue projects\USR\TRAINING”. Each project has several sub-folders. The list of the folder structure is described in the Help file here: About the Supervisor‟s projects \ About projects.
Module 04 - PcVue and project concepts
Page 8/15
3.4 What is running? When PcVue is running you can see:
Figure 7
[A] PcVue workspace. [B] Event viewer icon located in the taskbar. (See the Traces chapter.) [C] HDS icon located in the System Tray. (See the Module Archives – HDS.)
Module 04 - PcVue and project concepts
Page 9/15
3.5 Traces & logs The PcVue Event Viewer is a vital tool because it is the place where all important information is displayed. When something is not working as you expect you must check the Event Viewer. It should be your first recourse. The traces are recorded in the following file: "C:\ARC INFORMATIQUE\PCVUE ...\bin\Log Files\trace.dat" If you check this folder you can see many files. These traces and logs are useful for helping our developers to analyze any problem. If you have a crash you must send the complete Log Files folder to our Technical Support.
Module 04 - PcVue and project concepts
Page 10/15
4 PcVue architecture PcVue is modular software running several processes. Each process is in charge of a function. The following diagram shows the processes and features.
Figure 8
Module 04 - PcVue and project concepts
Page 11/15
5 The Application Explorer The Application Explorer is a new way to manage the configuration of a PcVue application. It replaces the old style one-at-a-time configuration dialogs with a tool that allows you to visualize the configuration of the entire application in one Windows Explorer style view.
5.1 Main features
Figure 9
[A]: Main menu. [B]: Main toolbar. [C]: Task pane. Displays tasks relevant to both the selected configuration folder and the item selected in the contents pane. [D]: Configuration window. The main configuration window from where the configuration tree is navigated and the configuration modified.
Module 04 - PcVue and project concepts
Page 12/15
[E]: Configuration tree. Displays all the configuration items, available to the Application Explorer, in a tree display. Each major configuration aspect is represented by a folder. [F]: Contents pane. Displays the contents (either configuration sub folders or configuration items) of the folder selected in the configuration tree. [G]: Tool bar. Displays icons representing the tasks relevant to both the selected configuration folder and the item selected in the contents pane. In general, a copy of what is displayed in the task pane. [H]: Behaviors pane. Only displayed when the Variables Tree is selected in the configuration tree. Displays any associated behavior for the variable selected in the contents pane. (Events, trending etc.) [I]: Behaviors tool bar. Only displayed when the Behaviors Pane is displayed. Displays icons that represent the tasks that add, modify and delete variable behaviors.
5.2 Using the Application Explorer This topic explains how you use the Application Explorer in general, not how you create a particular configuration using it. 5.2.1 Opening and closing the Application Explorer
The Application Explorer is opened from PcVue‟s main menu using the command Configure / Application Explorer. To close the Application Explorer use the File.Exit command on the Application Explorer‟s menu or the Exit tool on the toolbar. Although it can only be started from within PcVue, the Application Explorer runs as a separate task within Windows. If you click in PcVue‟s Workspace while the Application Explorer is open, PcVue is moved to the front and takes focus. The Application Explorer remains open but is hidden by the Workspace. 5.2.2 Changing the appearance of the Application Explorer
The size of the Application Explorer can be changed by dragging its borders or corners. The size of any of its three panes can be changed by dragging the border separating it from the adjacent pane. The position of the Application Explorer is changed in the normal way by dragging its title bar. You can select the columns that appear in the Contents Pane from a pop-up menu that is displayed by right clicking in it (outside of any items it is displaying). The columns that are available depend on the type of configuration folder that is selected. Changes that you make to the Application Explorer's appearance are remembered. If you close and then re-open the Application Explorer it appears in the same position, with the same panes sizes etc. Module 04 - PcVue and project concepts
Page 13/15
5.3 What can be configured from the Application Explorer? Communication o Data acquisition - OPC, DDE, LNS, BACnet, IEC 104 & IEC 61850 o Networking - Inter-station networking for client-server applications o Servers - When using the Supervisor as an OPC server or Web server. Variables o Variables tree - Branches, Bit, Register and Text variables o Associated behaviors - Overflow processing, Thresholds, Discrepancy checking, Chronometer, Counter and Events o Domain and Nature o Expressions o Alarm synthesis Archives o Archive units - Free, Proprietary and Database o Databases o Trend Groups Actions o Messages - Email and SMS o Cyclics o Events User accounts o Users o Profiles
Exercise 2.
To open and become familiar with the operation of the Application Explorer a. Open the Application Explorer using the main menu command Configure.Application Explorer. b. Expand the configuration tree and observe what is available. c. Note how the tasks available in the Task List change depending on which configuration aspect is selected.
Module 04 - PcVue and project concepts
Page 14/15
With the Application Explorer open, click into the PcVue Worskspace. The Application Explorer disappears. Try opening it again using the menu command Configure / Application Explorer. What happens? Why?
It appears faster than the first opening. That‟s normal because the Application Explorer stays opened.
Module 04 - PcVue and project concepts
Page 15/15
Introduction
Module 05 Study case
Contents
1
Study case
3
2
Design process
4
3
Study
5
3.1 Specifications and needs
5
3.2 Architecture proposed
5
3.3 HMI navigation proposed
6
3.4 Functional blocks
7
Module 05 - Study case
Page 2/7
1 Study case During this training course we will create a complete project implementing the common features needed for most real projects. SCADA software is used in various industries (power supply, water treatment, manufacturing etc.). We have selected a building management project because it can be understood without specialist knowledge.
Figure 1
Module 05 - Study case
Page 3/7
2 Design process You can design a PcVue project in several ways but, because PcVue is object oriented, there is one best way represented by the following diagram.
Figure 2
We will try to follow this procedure to design our study case.
Module 05 - Study case
Page 4/7
3 Study 3.1 Specifications and needs Our imaginary customer requires a project with the following features:
This building has three floors.
The first floor has three rooms. The second and third floors have five rooms and are identical.
All rooms have one air conditioner and one light.
One room on the first floor has two air conditioners and two lights.
Collect the data from one PLC and one OPC server.
The same layout for each mimic.
Good, clear navigation among mimics.
Display all data about all the air conditioners and lights.
Manage the alarms.
Archive the data and display them on trends and logs.
Display the status of the devices we are communicating with.
Manage several User Accounts.
Specifically for the training we want to have mimics to display some basic features such as animations. Later when you design an actual project you can come back to these mimics to remind you.
3.2 Architecture proposed This project will implement a single PcVue station in stand-alone mode. The following diagram represents the architecture:
Figure 3
Module 05 - Study case
Page 5/7
3.3 HMI navigation proposed We can represent the navigation by the following diagram:
Figure 4
Module 05 - Study case
Page 6/7
3.4 Functional blocks We can identify 3 ‘functional blocks’.
Air conditioners. The data involved are: o Temperature value, o On/Off, o Temperature set point, o Temperature High/Low limit, o Brand, model, vendor details.
Lights. The data involved are: o On/Off, o Luminosity value, o Control.
The mimic layout. The common objects we want to display are: o Logo, o Navigation bar, o Login/Logout button, o Date, time and current user, o Current alarms.
Module 05 - Study case
Page 7/7
Variables
Module 06 Real time database Basics
Contents
1
Introduction
3
1.1 In this module you will learn
3
1.2 Files used in this module
3
1.3 Third party software used in this module
3
2
This feature in PCVUE architecture
4
3
Basics
5
3.1 Mandatory properties
5
3.1.1 Type
5
3.1.2 Name
5
3.1.3 Source
7
3.2 Main optional properties
7
3.2.1 Description
7
3.2.2 Command
7
3.2.3 Properties related to variable type
7
3.3 Managing variables using Application Explorer 3.3.1 Creating a branch 3.3.2 Creating a variable 3.4 Variable Selector 3.4.1 The variables tool bar
8 9 10 12 13
4
Run-time properties
15
5
Summing-up
16
Module 06 - Real time database Basics
Page 2/16
1 Introduction 1.1 In this module you will learn About the main properties of PcVue’s variables, How to manage variables using the Application Explorer, How to use the Variable Selector.
1.2 Files used in this module None
1.3 Third party software used in this module None
Module 06 - Real time database Basics
Page 3/16
2 This feature in PCVUE architecture
Figure 1
Module 06 - Real time database Basics
Page 4/16
3 Basics Real-time data is the engine of PcVue. It is managed as a collection of tags. In PcVue terminology a tag is called a Variable. The collection of variables in a project is known as the Variables Tree because of the tree-like structure of the variable naming scheme. When each variable is created it is given characteristics selected from a range of properties which determine its behaviour. Some properties are mandatory and some are optional.
3.1 Mandatory properties The mandatory properties are: Type Name Source 3.1.1 Type PcVue supports three types of variables: Bit: Digital value Register: Analogue value Text: Text value 3.1.2 Name The variable's name is the identity by which it is known throughout PcVue. The name of a variable is a string composed of up to twelve fields delimited by the character “.”. All but the last part of the variable name is also known as its branch. Using branches you can group a set of variables together as they would be in the outside world. For example a Bit, two Registers and a Text variable could be grouped together to represent a simple temperature controller. For example: BUILDING.FLOOR_01.AC_01.INFO BUILDING.FLOOR_01.AC_01.ON BUILDING.FLOOR_01.AC_01.SETPOINT BUILDING.FLOOR_01.AC_01TEMP If the variables in the example above are represented in a (horizontal) tree format the grouping becomes more apparent. In the example that follows there are two temperature controllers plus two lights making a total of 14 variables.
Module 06 - Real time database Basics
Page 5/16
Figure 2
Arranging variables in hierarchical groups simplifies development and maintenance as tools in the Application Explorer allow you to cut, copy and paste entire branches with their variables. The main benefit however lies in how the variables tree is used in conjunction with graphical objects to accelerate the development of your project.
The main limits are: The name can contain a maximum of 12 fields. The maximum total size of a name is 255 characters including the delimiters “.”.
Module 06 - Real time database Basics
Page 6/16
3.1.3 Source To determine the source of a variable you ask yourself the following question: “Where is the value for this variable coming from?” The various sources are: Equipment: The value is collected from a device using one of the native drivers (i.e. Modbus TCP/IP), OPC: The value is collected from an OPC Server, Lonworks: The value is collected from a Lonworks network, DDE: The value is collected from a DDE Server, BACNet: The value is collected from a BACNet network, IEC: The value is collected from either an IEC 61850, or IEC 60870-104 network, Internal: The value is not collected from any outside source but the variable still belongs to the real-time database. (The value may be calculated using an expression or script.)
3.2 Main optional properties Here are the main optional properties. During the training we will discover several more. 3.2.1 Description A string describing a variable. You can display the description in the HMI instead of the variable’s name.
We recommend that you always use the Description property. 3.2.2 Command The Command property is used to determine whether a variable can be set by PcVue or not. 3.2.3 Properties related to variable type Some optional properties depend on the variable type. For example when a variable is a Register it has a Units property and a Minimum/Maximum range.
Module 06 - Real time database Basics
Page 7/16
3.3 Managing variables using Application Explorer There are two stages to creating a variable with the Application Explorer (AE). First you must create the branch to which it belongs. Then you can create the variable itself. Of course the same branch can have several variables and once you have created all the variables for a branch it is easy to create another similar branch using copypaste.
The term Branch can refer to the entire branch to which a variable belongs, or just part of it. The same as in a real tree where you can have a big branch made of several smaller branches. The term Variable Name is sometimes used to refer to just the last part of the name (for example SETPOINT or ON) or as an abbreviation for the Complete Variable Name – meaning the Branch plus the Variable Name. (for example BUILDING.FLOOR_01.AC_01.ON). The following steps all take place within the Application Explorer that is opened using the menu command Configure / Application Explorer.
Module 06 - Real time database Basics
Page 8/16
3.3.1 Creating a branch Expand the configuration tree and select the Variables Tree.
Step 1. From the task list select Add a branch. The Branch Creation dialog opens. Enter the Branch name and click OK. A new branch is created.
Figure 3
Step 2. Select the newly created branch and repeat the process to create its sub branch .
Step 3. Repeat this procedure until you have created the complete branch.
Module 06 - Real time database Basics
Page 9/16
3.3.2 Creating a variable
Step 1.
Select the branch that has just been created, and from the task list select Add bit. The Bit Creation dialog opens.
Figure 4
Step 2.
Enter the variable name and click the OK button to confirm the configuration. You should now have a Bit variable..
Step 3.
Save the configuration using the Application Explorer’s menu command File / Save.
Save makes a backup of the configuration on the hard drive.
You must have at least one variable on a branch otherwise the branch is not remembered when the Application Explorer is closed. The branch will disappear only if you restart PcVue, not the Application Explorer.
Module 06 - Real time database Basics
Page 10/16
Exercise 1.
Now we can start our project. Determine a variable naming scheme for our project. Create the variables for one Air Conditioner.
1. Determine the naming scheme Field 1: BUILDING Field 2: FLOOR_XX where XX is the Floor number Field 3: DeviceType_DeviceID where - DeviceType is AC for air conditioners and LT for lights. - DeviceID is the identifier of the device. Field 4: The information itself (Temp for temperature, etc.) Of course this naming scheme is not the only appropriate one. With some experience you will know what suits a particular project. 2. Create the following variables (with all other properties at their default settings): Name
Type
Source
Description
BUILDING.FLOOR_01.AC_01.TEMP
Register
Internal
Temperature
BUILDING.FLOOR_01.AC_01.SETPOINT
Register
Internal
Set point
BUILDING.FLOOR_01.AC_01.ON
Bit
Internal
Air cond. On
BUILDING.FLOOR_01.LT_01.LUM
Register
Internal
Luminosity
BUILDING.FLOOR_01.LT_01.ON
Bit
Internal
Light On
BUILDING.FLOOR_01.LT_01.CMD
Bit
Internal
Command
Note that the Complete Variable Name is given. Using the Application Explorer you will first have to add the branches and then the variables.
Module 06 - Real time database Basics
Page 11/16
3.4 Variable Selector The Variable Selector is the tool provided to browse the variables. It can be opened from the menu using the command Configure / Variables / Selector.
Figure 4
The Selector is useful to find a variable and to display and edit its properties.
Figure 5
Module 06 - Real time database Basics
Page 12/16
The Selector has four functional areas: [A]: Menu. [B]: Variables tool bar. (See below) [C]: Left pane. Displays the variables tree. [D]: Right pane. Displays branches and variables sub-ordinate to the branch that is currently selected in the variables tree. The display of a variable includes its main properties and real time value and status (See the section on Run-time properties). [E]: Associated behaviours toolbar. Tools to add modify and delete a variable’s associated behaviour. The tools that are available depend on the type of variable that is selected. [F]: Lower pane. Displays any associated behaviour for the selected variable.
You can change the properties that are displayed in the right pane by right clicking in the pane and selecting them from a context menu. 3.4.1 The variables tool bar The commands available in the tool bar change depending on what is currently selected. Here is a complete list. Add a new sub-branch to the branch selected in the variables tree. Add a new bit variable to the branch selected in the variables tree. Add a new register variable to the branch selected in the variables tree. Add a new text variable to the branch selected in the variables tree. *Display the selected variable’s properties. *Delete the selected variable or branch. Copy the selected variable or branch. Cut the selected variable or branch. Paste the selected variable or branch. * The icon that is displayed depends on the type of variable or branch selected. Module 06 - Real time database Basics
Page 13/16
Exercise 2.
Make the following modifications.
Name
Command /Control
Unit
Min/Max
BUILDING.FLOOR_01.AC_01.TEMP
No
Celsius
0/40
BUILDING.FLOOR_01.AC_01.SETPOINT
Yes
Celsius
0/40
BUILDING.FLOOR_01.AC_01.ON
Yes
BUILDING.FLOOR_01.LT_01.LUM
No
%
0/100
BUILDING.FLOOR_01.LT_01.ON
No
BUILDING.FLOOR_01.LT_01.CMD
Yes
Module 06 - Real time database Basics
Page 14/16
4 Run-time properties Each variable is represented at run-time by three properties:
Value: The possible values for each type are: o Bit: 1 (True), 0 (False) o Register: -3.37E+38 to +3.37E+38, o Text: 1 to 32,000 characters.
Timestamp: The timestamp usually gives the time when PcVue receives the variable value from a device. When PcVue is using a time stamped protocol (like OPC) the timestamp is provided by the device.
Status: There are 2 main statuses: o S (Set): The variable is valid. We can be sure that the value is usable. o NS (Not Set): The variable is not valid. We are not sure whether the value is usable. For example when a sensor is out of order, the value given by the device may be out of range. For PcVue the status is then NS.
A list of the statuses is available in the online Help in the topic: Application Explorer / Variables / Variables tree / Using the Variable Selector.
Module 06 - Real time database Basics
Page 15/16
5 Summing-up Real-time data is the engine of PcVue. The Variable Tree is made up of Branches and Variables. You must decide on a suitable naming scheme. A variable has many properties. The status of a variable indicates its validity.
Module 06 - Real time database Basics
Page 16/16
Variables
Module 06 Real time database Advanced
Contents
1
Introduction
3
1.1 In this module you will learn how to
3
1.2 Files used in this module
3
1.3 Third party software used in this module
3
2
This feature in PCVUE architecture
4
3
Advanced
5
4
3.1 Use the deadband
5
3.2 Opening the Variable Selector using a shortcut key
7
3.3 Edit variables using a third-party tool
8
Summing-up
Module 06 - Real time database Advanced
11
Page 2/11
1 Introduction 1.1 In this module you will learn how to Optimise your project using the deadband. Reduce design time by: Using a shortcut key, Editing the Variable Database file using Microsoft Excel.
1.2 Files used in this module Project started with the Basics module.
1.3 Third party software used in this module Windows Notepad, Microsoft Excel 2003 or later.
Module 06 - Real time database Advanced
Page 3/11
2 This feature in PCVUE architecture
Figure 1
Module 06 - Real time database Advanced
Page 4/11
3 Advanced 3.1 Use the deadband The deadband is the value by which the source of the variable must vary before the change is recognised by PcVue. It applies to Register variables only. The deadband property is very important and must be set for each Register variable that has a lot of activity. In practice, unless you have an unusually stable source, that applies to all Register variables where the value is generated externally to PcVue. Each time you create a Register variable, ask yourself: “Am I interested in all changes in value of this register – no matter how small?”. For example when a Temperature shifts from 15.15 degrees to 15.16 degrees, perhaps you don’t want to record this change. In this case you have to configure the deadband for this temperature. You will then optimise your application by decreasing the activity in PcVue. You configure the deadband of a Register variable from the Advanced tab of its Properties dialog.
Figure 2
There are three types of deadband: Absolute Range percent Value percent.
The deadband property does not appear if the variable has an Internal source.
Module 06 - Real time database Advanced
Page 5/11
The differences are explained in the following diagram. Here we assume that the current value is 15 and the deadband configured is 1.
Figure 3
Module 06 - Real time database Advanced
Page 6/11
3.2 Opening the Variable Selector using a shortcut key The Variable Selector is a tool that you will use frequently. By default there is no shortcut key to open it. To configure it: Use the menu Configure / Actions / Function Key...
Figure 4
Click Create... button Configure the dialog as shown below. Click the OK button.
Figure 5
Click the Save button and then the OK button. Module 06 - Real time database Advanced
Page 7/11
3.3 Edit variables using a third-party tool If you have a large number of variables, creating them using PcVue can be a long process. Fortunately you can use a third-party tool such as Microsoft Excel to create variables quickly.
The complete Variables Tree is in one ASCII file in CSV* format. It is located in the following path: \C\Varexp.dat *Comma Separated Variable Whatever tool is used for editing, the procedure is the same:
Step 1. Stop PcVue, Step 2. Make a copy of the Variables Tree file (just in case of any problems when editing),
Step 3. Open the Variables Tree file, Step 4. Make your modifications and save, Step 5. Re-start PcVue. Because the file Varexp.dat is an ASCII file you can use any text editor such as Notepad to edit the Variables Tree.
Module 06 - Real time database Advanced
Page 8/11
Exercise 1.
Add the following variables using Notepad.
Name
Type
Source
Description
BUILDING.FLOOR_01.AC_02.TEMP
Register
Internal
Temperature
BUILDING.FLOOR_01.AC_02.SETPOINT
Register
Internal
Set point
BUILDING.FLOOR_01.AC_02.ON
Bit
Internal
Air cond. On
The best way to do is to copy the existing variables and change their names.
Modify the file Varexp.dat while PcVue is running and then shut down PcVue. What happened?
Module 06 - Real time database Advanced
Page 9/11
Of course Notepad is not very useful for this and the best tool to modify the PcVue Variables Tree is Microsoft Excel.
The format to save the Varexp.dat in Excel is very specific. You must name the file “Varexp.dat” and select the CSV format (MS-DOS, *.csv).
Exercise 2.
Add the variables for the first floor using Excel.
Reminder of the specifications: This building has three floors. The first floor has three rooms. The second and third floors have five rooms and are identical. Most rooms have one air conditioner and one light. One room has two air conditioners and two lights. It is on the first floor. That means we will have: Floor
Air conditioners
Lights
Floor 1
4
4
Floor 2
5
5
Floor 3
5
5
The second line of the file Varexp.dat contains the title of each column. You can find the detailed format of the file Varexp.dat in “DVD\Sv\Documentation\Addenda\English\VAREXP_100_ENU.pdf”.
Module 06 - Real time database Advanced
Page 10/11
4 Summing-up You can dramatically improve your application’s performance using the deadband feature. With Microsoft Excel, you can accelerate creation of the Variables Tree.
Module 06 - Real time database Advanced
Page 11/11
Communication
Module 07 Usual drivers - Basics
Contents
1
Introduction
3
1.1 In this module you will learn
3
1.2 Files used in this module
3
1.3 Third party software used in this module
3
2
This feature in PcVue architecture
4
3
Basics
5
3.1 Communication concepts 3.1.1 Network, protocol and node
5
3.1.2 Master/Slave and Frame
6
3.1.3 Variable mapping
12
3.2 Configuration in PcVue
13
3.2.1 Communication configuration
13
3.2.2 Variable mapping
22
3.3 Optimisation and maintenance
4
5
26
3.3.1 PcVue Communication Manager
26
3.3.2 Maintenance and debugging
29
3.3.3 Start automatically after PcVue start-up
32
Summing-up
Module 07 - Usual drivers - Basics
33
Page 2/33
1 Introduction 1.1 In this module you will learn Some communication concepts, How to configure communication in PcVue, How to optimize and maintain it.
1.2 Files used in this module Copy the PcVue project located in My Documents\Pcvue Training\Module_07\Project in C:\Pcvue projects\Usr\.
1.3 Third party software used in this module We will use the Modbus Poll and Modbus Slave (Evaluation license). These files can be found here: My Documents\Pcvue Training\Module_07\Third party\.
Module 07 - Usual drivers - Basics
Page 3/33
2 This feature in PcVue architecture
Figure 1
Module 07 - Usual drivers - Basics
Page 4/33
3 Basics 3.1 Communication concepts 3.1.1 Network, protocol and node
PcVue uses a set of communication protocols to communicate with the process equipment across a network or several networks. There are three types of industrial networks: Serial link: RS232 or RS485 cables. PcVue uses the computer’s COM port or a dedicated communication board such as Applicom. For example Modbus RTU, Mitsubishi MELSEC-A Series etc. Ethernet: PcVue uses the computer’s Ethernet card. For example Modbus TCP/IP, Siemens S7 etc. Dedicated: A proprietary medium, for example Modicon Modbus+, Profibus etc. The following diagram describes the classic architecture.
Figure 2
When two systems are communicating they need to “speak” the same language. A protocol is a standard “language” used by two systems to communicate together. PcVue supports a wide and increasing range of industrial protocols. During this training course we will use Modbus TCP/IP as an example but what you will learn also applies to many other protocols. In PcVue vocabulary, the PLC is called a Node.
Module 07 - Usual drivers - Basics
Page 5/33
3.1.2 Master/Slave and Frame
Usually a protocol implements two types of “talkers”: The Master and the Slave(s). The Master is the one that makes the requests to the Slave(s) to read and/or write the data. The Slave “listens” on the network waiting for a request sent by the Master.
In the Ethernet environment the Master is sometimes called the Client and the Slave is called the Server. In most cases, PcVue is the Master and the PLC is the Slave. In PcVue vocabulary, the request is called a Frame. A frame is a message containing all the parameters needed to read or write data. For example a Modbus frame contains the Node address, the function code (read or write, bit or words, input or output etc.), the data address and quantity and a CRC (Cyclic Redundancy Check – used to check that the message hasn’t been corrupted). The process used by the master to collect the data is always the same: it periodically sends a frame to the slave, waits for the answer, sends another frame and so on. The following diagram represents the typical Master/Slave process.
Figure 3
The Master sends a frame to read some bits and waits for the reply. The Slave sends the reply. Then it waits for the next frame. 5 seconds later this process repeats and so on…
Module 07 - Usual drivers - Basics
Page 6/33
The period configured for one frame is called the polling period. Of course a Master can read different types of data in the same Slave. The following diagram represents this process.
Figure 4
The Master sends a frame to read some bits and waits for the reply. The Slave sends the reply. Then it waits for the next frame. 5 seconds later this process repeats and so on...
The Master sends a frame to read some words and waits for the reply. The Slave sends the reply. Then it waits for the next frame. 5 seconds later this process repeats and so on...
Module 07 - Usual drivers - Basics
Page 7/33
Exercise 1.
Create basic communication using the third party tools
1. Install Modbus tools package a. Run My Documents\Pcvue Training \Module_07\Third party\ModbusPollSetup.exe and follow the instructions. b. Run My Documents\Pcvue Training\Module_07\Third party\ ModbusSlaveSetup.exe and follow the instructions. 2. Start the Modbus TCP/IP Slave. a. Run the shortcut Modbus Slave located on the desktop. b. By default one Slave is configured. Close it by selecting File / Close. c. Load the Training slave configuration by selecting File / Open. In the dialog, select My Documents\Pcvue Training \Module_07\Third party\ Slave 1 - 10 Bits.mbs. d. Repeat the same operation by opening the file My Documents\Pcvue Training \Module_07\Third party\ Slave 1 10 Words.mbs. e. Select Connection/Connect…, the Register Later button, then the OK button. f. Select the TCP/IP option.
Module 07 - Usual drivers - Basics
Page 8/33
g. Finally you should have the Slave HMI with these settings:
Figure 5
h. You can change the data values by double-clicking on the corresponding cell.
Module 07 - Usual drivers - Basics
Page 9/33
3. Start the Modbus TCP/IP Master. a. Open the shortcut Modbus Poll located on the desktop. b. By default a frame is configured. It is set for reading 10 words from address 0 to Slave no.1. So you only have to select Connection / Connect… Now you are able to read and write the Words. c. We are going to create a frame to read the bits. Select File / New. Select Setup / Read/Write definitions… and configure the dialog as follows:
Figure 6
d. Select Connection / Connect... Select TCP/IP. Now you are able to read and write the bits. 4. Check the frames using Display / Communication.
Module 07 - Usual drivers - Basics
Page 10/33
Try to read data to an Illegal Address (i.e. address 11) and check the frame reply. Try to send an Illegal Function (i.e. Write Input Registers) and check the frame reply. What do you see?
Module 07 - Usual drivers - Basics
Page 11/33
3.1.3 Variable mapping
When the Communication Manager receives a reply it needs to dispatch the various values to the PcVue variables. This means that it needs to know which PcVue variable corresponds with each Slave address. This is the purpose of variable mapping. The following diagram shows a mapping example for a frame requesting 10 Words starting at address 0.
Figure 7
Module 07 - Usual drivers - Basics
Page 12/33
3.2 Configuration in PcVue There are two main steps: Configure the communication itself, Configure the variable mapping. 3.2.1 Communication configuration
Communication is defined in terms of these communication objects: Network, Node, Frame.
Each communication object has common parameters and sometimes specific ones also. You can find the specific parameters for a protocol in the Help here: F1/Configuration/Communication/Native communication drivers/Configuring a protocol. The configuration is done using the Communication Objects dialog. You can open it via Configure / Communication / Equipment.
Figure 8
Module 07 - Usual drivers - Basics
Page 13/33
Figure 9
[A]: Three columns displaying the configured communication objects: Network, Node and Frame. Of course by default it is empty. [B]: Status of the communication objects. Used for maintenance. [C]: On / Off buttons. Used to start and stop the entire communication manually. [D]: Validate / Cancel buttons.
Module 07 - Usual drivers - Basics
Page 14/33
3.2.1.1 Network
The Network object defines the protocol and the board used. You can have up to 16 different protocols on the same project. To create a network:
Step 1.
Open the Communication Objects dialog.
Step 2.
Double-click the Network / Creation field.
Step 3.
The dialog Network board and protocol selection appears.
Step 4.
In the left-hand column, select the appropriate protocol provider and the protocol in the right-hand column. Click OK button.
Figure 10
We advise you always to select the MULTI PROTOCOL board. Step 5.
The Network Parameters dialog appears.
Step 6.
Type the Network object name in the Network field.
Module 07 - Usual drivers - Basics
Page 15/33
Figure 11
Step 7.
Click the Validate button then Cancel to close the dialog.
Now a new Network has been added in the Network column. To edit a Network object, double-click on it.
Exercise 2.
Create a new Network with the following parameters:
Parameters
Value 1
Protocol
Modbus TCP/IP (XBUS-IP-MASTER)
Network name
XBUS_IP
Module 07 - Usual drivers - Basics
Page 16/33
3.2.1.2 Node
The node object of a Network defines a device communicating with the corresponding protocol. To create a Node:
Step 1.
Select the Network.
Step 2.
Double-click the Node / Creation field.
Step 3.
Type the Node object name in the Equipment field.
Step 4.
Enter any other parameters that are needed. The parameters depend on the protocol and the PLC type.
Figure 12
Step 5.
Click the Validate button then Cancel to close the dialog.
Now a new Node has been added in the Node column. To edit a Node object, double-click on it.
You must keep the message time-out parameter at the default value (0) except with some particular old devices.
Module 07 - Usual drivers - Basics
Page 17/33
Exercise 3.
Create a new Node with the following parameters:
Parameters
Value 1
Node name
PLC1
Equipment type
MODBUS DEC
TCP/IP address
127.0.0.1 (your computer’s address)
Slave address
1
Module 07 - Usual drivers - Basics
Page 18/33
3.2.1.3 Frame
The Frame object defines the request to be sent to the node. To create a Frame:
Step 1.
Select the Node.
Step 2.
Double-click the Frame / Creation field.
Step 3.
Type the Frame object’s name in the Frame field.
Step 4.
Select the Frame format and Access grant.
Figure 13
Module 07 - Usual drivers - Basics
Page 19/33
Step 5.
Select the address by clicking on this button: . The Address selection dialog appears. Each line displayed corresponds with an address zone in the Node, so it depends on the protocol and the node type. The address zone corresponds to the Function configured in the Modbus Poll tool as shown below.
Figure 14
Step 6.
Select the appropriate Address zone, the Starting address and Quantity of data then click the OK button.
Step 7.
Configure the scan rate (polling period).
Step 8.
Click the Validate button then Cancel to close the dialog.
Now a new Frame has been added in the Frame column. To edit a Frame object, double-click on it.
The parameter Priority mode is used in particular cases. Misuse can cause problems with performance.
Module 07 - Usual drivers - Basics
Page 20/33
Exercise 4.
Create two new Frames with the following parameters:
Parameters
Frame 1
Frame 2
Frame name
R_BITS
R_WORDS
Frame format
BIT
WORD
Access grant
Read
Read
Address zone
Bit I/O
Word I/O
Starting address
1
1
Quantity of data
10
10
Polling period
1 second
1 second
For one frame, select the starting address 0. What happened? Why?
Module 07 - Usual drivers - Basics
Page 21/33
3.2.2 Variable mapping
To configure the mapping for a variable:
Step 1.
Open the Properties dialog of a variable.
Step 2.
In the Source tab select the communication network name. The dialog changes appearance to display an Equipment sub-tab. Click the Link button.
Figure 15
Module 07 - Usual drivers - Basics
Page 22/33
Step 3.
The Equipment Mapping dialog appears.
Figure 16
[A] Communication objects, [B], Address.
Step 4.
Select the frame object [A] you want to map the variable.
Step 5.
Double click the address [B] to which you want to map the variable. The Equipment Mapping dialog closes and the mapping information appears in the Source tab of the Properties dialog.
Step 6.
Confirm the configuration and close the Properties dialog by clicking the OK button.
Module 07 - Usual drivers - Basics
Page 23/33
Exercise 5.
Communicate with PcVue and the Modbus Slave tool.
1. Create two equipment variables with the following properties: Name
Type
Source
FROM_PLC.BIT1
Bit
Equipment
FROM_PLC.WORD1
Register
Equipment
Min
Max
0
100
2. Map these 2 variables by selecting a valid address. 3. Start the Modbus Slave. 4. Start the communication and check the variables’ values.
Disconnect the Modbus Slave. What are the variables’ values?
Module 07 - Usual drivers - Basics
Page 24/33
In the Modbus Slave, set the Word value to 150. What is the value of the PcVue variable? Why?
When does the following Timestamp change?
Module 07 - Usual drivers - Basics
Page 25/33
3.3 Optimisation and maintenance Unfortunately it is unusual to implement communication successfully the first time! 3.3.1 PcVue Communication Manager
The Communication Manager is the module that manages the processing of frames as shown below.
Figure 17
Here we have two frames: Frame2 and Frame10 have polling periods of 2 and 10 seconds respectively. Each polling period, the frame is added to the communication stack. When at least one frame is in the stack it is sent to the Slave. When the slave reply is received the frame is removed from the stack. When you are configuring communication you must try to optimize it as much as possible. To do that you must tune these three parameters: The number of frames, The polling period, The write data.
Module 07 - Usual drivers - Basics
Page 26/33
3.3.1.1 Number of frames
It’s usual to suppose that a frame requesting 10 words is faster than a frame requesting 100 words. Actually this is wrong. The time used to read 10 or 100 word is the same. This is because during an exchange, most of the time consumed is used to build and transmit the frame. Therefore most of the time spent in the communication process is to manage the frames whatever their size. To understand that, try to solve this basic problem: 100 people want to travel from a point A to point B linked by a highway. This highway has a toll at the beginning and a toll at the end. The question is: Which is the faster? 100 cars transporting one person each or one bus transporting 100 persons (assuming the speed of the car and the bus is the same of course)?
Figure 18
Of course it’s faster using the bus as it is only processed once at the tolls, whereas each car must be processed individually. So using one frame “transporting” 100 data items is faster than 100 frames “transporting” 1 data item.
To have smooth traffic you must configure the communication to have the minimum number of frames. 3.3.1.2 Polling period
The polling period is also an important parameter to optimise the communication. If the Master is polling too fast it will increase the traffic on the network. For example we know that when you are using a Modbus serial link communication with 19,200 baud and one frame needs around 100ms to go and back to the Master. Module 07 - Usual drivers - Basics
Page 27/33
It means you can have up to 10 frames per second. What will happen if you configure 15 frames with a polling period of 1 second each? 3.3.1.3 Write data
Some projects need to write data to the PLC. In theory there is no problem with sending a frame to write data in the Slave. But a performance problem occurs when you send many controls at a fast rate. The following figure helps you to understand why:
Figure 19
You can see that PcVue is managing two stacks: the read frames stack and the write frames stack. The write frames stack is always in priority because a control can be very important. If you send a control every second then PcVue will add the write frame every second on the top of the write frames stack. Therefore the frames from the read frames stack will never be sent and the HMI never refreshed!! A classical mistake is to send a heartbeat to the PLC too frequently.
Don’t send controls that are too many and/or too fast. If you need to send many values in one shot to the PLC you must use the Recipe function. Check the Recipe module in this training course.
Module 07 - Usual drivers - Basics
Page 28/33
3.3.2 Maintenance and debugging
In case of failure, PcVue provides some status information to help you to find the problem. When a communication object is selected, the system supplies a set of states and counters. Two hexadecimal state codes and two error counters are associated with each network, equipment and frame. You can select them in real time by selecting the required network, equipment and frame. The figure below shows the State/Counter for the selected network.
Figure 20
Module 07 - Usual drivers - Basics
Page 29/33
It’s important to understand the difference between the Status and the Protocol Status. The Status is set by the Communication Manager and informs you of whether this object is communicating well or not. Here you can see various status values: Network
Node
Frame
Meaning
0700
0700
a000
The communication is fine!
0700
0700
e000
The communication is working but the “unstacking” is slower than the stacking (See Figure 17). Solution: Increase the scan period.
0413
Network error: PcVue cannot communicate with the selected COM channel. Solution: COM port problem, Ethernet card disabled etc.
0701
0701
xxxx
Communication out of order for this frame. Solution: Check the Protocol status and check the frame parameters.
The protocol status is a code sent by the equipment or by the protocol driver. For example if you try to read data which is outside of the PLC’s range it will send back a code. PcVue will display this code in the Protocol status.
This code depends on the driver’s implementation. Check the driver documentation (in PcVue’s online Help) or the PLC’s documentation. When a communication failure occurs, PcVue adds a new log in the Event Viewer. Then you can debug in Runtime mode as well. The following message is an example: Status a021 - 2 - 1658 - 562, (1.XBUS_IP.PLC1.R_WORDS) with Status a021: Frame status 2: protocol status 1658: State counter 1 562: State counter 2 (1.XBUS_IP.PLC1.R_WORDS): Frame name
Module 07 - Usual drivers - Basics
Page 30/33
Exercise 6.
Disconnect the Modbus Slave and check the different Communication status. Also check the Event viewer.
Module 07 - Usual drivers - Basics
Page 31/33
3.3.3 Start automatically after PcVue start-up
By default the native driver communication is off when PcVue starts up. To start the communication automatically:
Step 1.
In the Application Explorer configuration tree, select the node representing the project. From the task list select Settings.
Step 2.
In the left pane, select the Station start-up node.
Step 3.
Tick the Equipment option.
Figure 21
Module 07 - Usual drivers - Basics
Page 32/33
4 Summing-up PcVue is able to communicate with many protocols on a serial network, an Ethernet network or proprietary networks. The communication configuration uses three objects: network, node and frame. You can debug failed communication using the communication object’s status. The communication MUST be optimised.
Module 07 - Usual drivers - Basics
Page 33/33
Communication
Module 07 Usual drivers - Advanced
Contents
1
Introduction
3
1.1 In this module you will learn how to
3
1.2 Files used in this module
3
1.3 Third party software used in this module
3
2
This feature in PcVue architecture
4
3
Advanced
5
4
3.1 Communication System variables
5
3.2 Manage double words
7
3.3 Manage redundant PLCs with Ethernet protocols
10
3.4 How to map variables using MS Excel
13
Summing-up
Module 07 - Usual drivers - Advanced
14
Page 2/14
1 Introduction 1.1 In this module you will learn how to Use the communication system variables, Manage double words, Manage redundant PLCs with Ethernet protocols, Map variables using Microsoft Excel.
1.2 Files used in this module PcVue project developed in the Basics module.
1.3 Third party software used in this module We will use the Modbus Poll and Modbus Slave (Evaluation license). These files can be found here: My Documents\Pcvue Training\Module_07\Third party\.
Module 07 - Usual drivers - Advanced
Page 3/14
2 This feature in PcVue architecture
Figure 1
Module 07 - Usual drivers - Advanced
Page 4/14
3 Advanced 3.1 Communication System variables Normally, the end user requires a “System” view to display the state of all devices. PcVue automatically generates one system variable for each network object that is configured.
Figure 2
A list of the communication system variables is available in the online Help in: Application Explorer / Variables / System Variables / Communication Status Variables.
Module 07 - Usual drivers - Advanced
Page 5/14
Exercise 1.
Check the system variables generated by PcVue. Start the Modbus Slave and check the system variable values. Stop the Modbus Slave and check the system variable values.
Module 07 - Usual drivers - Advanced
Page 6/14
3.2 Manage double words A classic communication problem occurs when you are reading double words and you don’t know how the data is “coded”. A Double Word contains four bytes with the bytes at its ends known as the MSB (Most Significant Byte) and the LSB (Least Significant Byte). Unfortunately there is no standard for this and, according to the device, sometimes the LSB is transmitted first and the MSB last and sometimes it is the reverse. This coding is called LMsb:
LSB B31
B30
B29
MSB B24
B7
B2
B1
B0
Figure 3 MSB B0
B1
B2
LSB B7
B24
B29
B30
Figure 4
PcVue supports both formats. When you create a frame using the Double Word format, the address zones are as follows:
Figure 5
Module 07 - Usual drivers - Advanced
Page 7/14
B31
Exercise 2.
Check the difference between the MLsb address zone and the LMsb address zone.
1. Create a frame with the following parameters: Parameters
Frame 2
Frame name
R_DOUBLEWORDS
Frame format
DOUBLE WORD
Access grant
Read
Address zone
DWord I/O LMsb
Starting address
1
Quantity of data
5
Polling period
1 second
2. Create a variable having the following properties and map it on the R_DOUBLEWORDS frame Name FROM_PLC.DOUBLEWORD1
Type Register
Module 07 - Usual drivers - Advanced
Source
Min
Max
Equipment
0
4294967295
Page 8/14
3. Start the Modbus Slave and change the values as follows. For each step check the variable value.
Figure 6
4. Change the address zone for the frame R_DOUBLEWORDS to MLsb. 5. Redo step 3 and observe the difference.
Module 07 - Usual drivers - Advanced
Page 9/14
3.3 Manage redundant PLCs with Ethernet protocols Because some customers require exceptional reliability of their system, they will use redundant PLCs. PcVue is able to manage redundant PLCs but only using an Ethernet protocol. In this configuration, when PcVue detects a communication failure with the Slave On Duty it switches automatically to the Standby Slave.
Figure 7
To configure a redundant PLC:
Step 1.
Open the Node properties and click the Redundancy button.
Step 2.
Tick the Enable option for each Standby node needed (maximum 3). Then enter the parameters (TCP/IP address etc.).
Module 07 - Usual drivers - Advanced
Page 10/14
Figure 8
Module 07 - Usual drivers - Advanced
Page 11/14
Exercise 3.
Configure a Standby node and test it using the Modbus Slave.
1. The Standby node must have the following parameters: TCP/IP address
Port number
Slave address
127.0.0.1
502
2
2. Load the Slave 2 configuration file in Modbus Slave using File/Open. In the dialog select My Documents\Pcvue Training \Module_08\Third party\ Slave 2 10 Words.mbs. 3. Close down the On Duty slave to simulate a communication failure.
Module 07 - Usual drivers - Advanced
Page 12/14
3.4 How to map variables using MS Excel If you have a large number of equipment variables, mapping them using PcVue can be a long process. As PcVue’s variable configuration files are in CSV (comma separated value) format you can use a third party tool such as Microsoft Excel to map variables faster.
You can find the format of the Varexp.dat file in “DVD\Sv\Doc\English\VAREXP_100_ENU.pdf” in the chapter Equipment Variables.
Module 07 - Usual drivers - Advanced
Page 13/14
4 Summing-up You can display the communication status using the system variables. PcVue can manage redundant PLCs when using an Ethernet network for communication. You can configure the variable mapping using Microsoft Excel.
Module 07 - Usual drivers - Advanced
Page 14/14
Communication
Module 08 OPC - Basics
Contents
1
Introduction
3
1.1 In this module you will learn
3
1.2 Files used in this module
3
1.3 Third party software used in this module
3
2
This feature in PcVue architecture
4
3
Basics
5
3.1 Theory
5
3.2 How does it work?
6
3.3 Configure it in PcVue
4
14
3.3.1 OPC SERVER
14
3.3.2 OPC Client
14
Summing-up
Module 08 - OPC - Basics
21
Page 2/21
1 Introduction 1.1 In this module you will learn Overview of the OPC technology. Configure PcVue as an OPC Client. Configure PcVue as an OPC Server.
1.2 Files used in this module PcVue project developed in the previous module. If you don’t have it you can find it in My Documents\Pcvue Training\Module_08\Project.
1.3 Third party software used in this module We will use the Kepware OPC server and client (Evaluation license). The Kepware files can be found here: My Documents\Pcvue Training\Module_08\Third party\.
Module 08 - OPC - Basics
Page 3/21
2 This feature in PcVue architecture
Figure 1
Module 08 - OPC - Basics
Page 4/21
3 Basics 3.1 Theory OPC is an acronym for OLE for Process Control. OPC is a communication standard based on OLE/COM technology. OPC is a widely accepted industrial communication standard that enables the exchange of data between multi-vendor devices and control applications without any proprietary restrictions. An OPC server can communicate data continuously among PLCs on the shop floor, RTUs in the field, HMI stations, and software applications on desktop PCs. Even when the hardware and software are from different vendors, OPC compliance makes continuous real-time communication possible. OPC provides interoperability between applications for SCADA, command control and industrial equipment control (communication card, API, etc.). The OPC concept is based upon the COM model’s client/server architecture. A client application can call upon several OPC servers simultaneously. Those servers may be located either on the local station or on remote stations via DCOM (Distributed COM). The OPC Foundation is dedicated to ensuring interoperability in automation by creating and maintaining open specifications. The Foundation has many members some of which are main players in automation. Arc Informatique is an OPC Foundation member. The OPC Foundation has released many OPC specifications: OPC Data Access (OPC DA): Dedicated to real time data. OPC Alarms & Events (OPC AE): Dedicated to alarm management. OPC Historical Data Access (OPC HDA): Dedicated to managing archives. OPC XML Data Access (OPC XML-DA): Dedicated to real time data. It uses SOAP XML technology.
PcVue is an OPC DA Client and Server. PcVue is an OPC XML-DA Client.
PcVue does not implement OPC AE or OPC HDA. Module 08 - OPC - Basics
Page 5/21
3.2 How does it work? Here is a standard architecture:
Figure 2
Communication takes place via the following steps: 1. Connection. The Client connects to the Server. 2. Group creation. The Client creates an OPC group using particular parameters: a. Group Name, b. Polling Period, c. Deadband, d. Others…. 3. Item subscription. The Client subscribes OPC item(s) that are to be in the group. An OPC item corresponds to one data item in the PLC 4. Notification. The Server starts the communication (according the polling period) with the device and sends to the client the value of each subscribed item. Then each time an item’s value changes (according the deadband) the server will notify the client.
Module 08 - OPC - Basics
Page 6/21
When the Server notifies the Client it sends several pieces of information: Item name, Value (V) Timestamp (T): PcVue will display and archive the timestamp given by the server. Quality (Q): This property indicates the “validity” of the item. A quality is good or bad. For example if the server loses communication with the device, the quality of the item is bad. Item type: Boolean, integer, text…. etc.
Of course you can implement more complex architectures using OPC. A Server can notify many Clients.
Figure 3
Module 08 - OPC - Basics
Page 7/21
A Client can be connected to many Servers.
Figure 4
A Client can be located in a computer other than that of the Server.
Figure 5
Module 08 - OPC - Basics
Page 8/21
Exercise 1.
Create a basic architecture (see Figure 2) using Kepware OPC Server and Client.
1. Install the Kepware package: a. Launch My Documents\Modules\Module_08\Third party\KepServerEX.exe. b. In the “Select features” dialog box, collapse the Drivers item.
Figure 6
c. Select the “Simulation Suite” driver and click the Next buttons until the end of the Wizard.
Figure 7
Module 08 - OPC - Basics
Page 9/21
2. Load the Server configuration file: a. Select File / Open. b. Select: My Documents\Modules\Module_08\Third Party\Server_Configuration.opf You should have the following screen:
Figure 8
If you click on Channel_0_User_Defined / User you see in the right-hand panel that three items have been configured: Table 1
Name
Type
Simulated
Access mode
On_Off
Boolean
Yes
Read only
Setpoint
Word
No
Read / Write
Temperature
Float
Yes
Read only
We will configure the Client to read these items. 3. Start the Client: Windows Start button / All programs / Kepware Products / KepServerEx / OPC Quick Client.
Module 08 - OPC - Basics
Page 10/21
4. Connection: a. Edit / New Server connection. b. Select Kepware Server. OK.
Figure 9
5. Create a Group: a. Edit / New Group. b. Configure Name = Group 1 and Update rate = 1000.
Figure 10
Module 08 - OPC - Basics
Page 11/21
6. Item subscriptions: a. Edit / New item. b. Browse the Server and select Temperature.
Figure 11
c. Follow the same procedure for the On_Off and Setpoint items. You should then have the following configuration:
Figure 12
Module 08 - OPC - Basics
Page 12/21
What do you see when the values are refreshed?
What happens if you switch off the server?
Module 08 - OPC - Basics
Page 13/21
3.3 Configure it in PcVue 3.3.1 OPC SERVER
To use PcVue as an OPC Server the configuration is very easy. There is nothing to do! 3.3.2 OPC Client
PcVue is a standard OPC Client, so the configuration procedure is similar to that of the Kepware Quick OPC Client.
Step 1. Connection: a.
Figure 13
b.
Figure 14
Module 08 - OPC - Basics
Page 14/21
c.
Figure 15
d. A new server is added. The state must be “Connected”.
Figure 16
Step 2. Create a group: a.
Figure 17
Module 08 - OPC - Basics
Page 15/21
b.
Figure 18
c. A new group is added.
Figure 19
Step 3. Create variables: Now we must create some variables Name
Type
Control/Command
Source
Bit
No
SRV1
FROM_OPC.TEMP
Register
No
SRV1
FROM_OPC.SETPOINT
Register
Yes
SRV1
FROM_OPC.ON_OFF
Module 08 - OPC - Basics
Page 16/21
Step 3. Item subscription: a.
Figure 20
b.
Figure 21
c.
Figure 22
Module 08 - OPC - Basics
Page 17/21
d.
If you double-click in the Variable Selector, the variable is automatically added in the mapping window and the next item is selected. That is useful if you have many items to map in a row! You can find more details in the PcVue Help file: F1\Application Explorer\Communication\Data acquisition\OPC You should end up with the following configuration:
Figure 23
Module 08 - OPC - Basics
Page 18/21
Exercise 2. a. Connect PcVue to the Kepware Server. b. Create three PcVue variables as described in the following table: Name
Type
Control/Command
Source
Bit
No
SRV1
FROM_OPC.TEMP
Register
No
SRV1
FROM_OPC.SETPOINT
Register
Yes
SRV1
FROM_OPC.ON_OFF
c. Using the Variables Selector, check the value of each OPC variable.
Open the Variables Selector. What is the meaning of (PLC)?
Module 08 - OPC - Basics
Page 19/21
Switch off the Kepware Server. What happens in PcVue?
Exercise 3.
Create a text item in the Kepware Server then configure PcVue to see the text value.
Module 08 - OPC - Basics
Page 20/21
4 Summing-up OPC provides interoperability between applications. PcVue is a OPC DA Server and Client and also an OPC XML-DA Client. There are three steps to configuring any OPC Client: Connection, Group creation, Item subscription. All items subscribed in single group will be refreshed according the polling period and the deadband of the group. The OPC Server notifies the client(s) only when the item value changes according the deadband. An item notification includes three main properties: Value, Timestamp, Quality (VTQ).
Module 08 - OPC - Basics
Page 21/21
Communication
Module 08 OPC - Advanced
Contents
1
Introduction
3
1.1 In this module you will learn
3
1.2 Files used in this module
3
1.3 Third party software used in this module
3
2
This feature in PcVue architecture
4
3
Advanced
5
3.1 Optimize the communication with OPC
5
3.2 Display the Status of the OPC Communication
5
3.3 Advanced settings
7
3.3.1 Server Advanced parameters
7
3.3.2 Group Advanced parameters
8
3.4 Activate the OPC Traces 3.5 How to map variables using Microsoft Excel
4
Summing-up
Module 08 - OPC - Advanced
9 10
11
Page 2/11
1 Introduction 1.1 In this module you will learn How to optimize the OPC communication. How to display the status of the OPC communication. How to tune the OPC communication. How to add logs.
1.2 Files used in this module PcVue project developed in the Basic module.
1.3 Third party software used in this module We will use the Kepware OPC server and client (Evaluation license). Kepware files are located here: My Documents\Pcvue Training\Module_08\Third party\. Install the Kepware server if it is not already installed.
Module 08 - OPC - Advanced
Page 3/11
2 This feature in PcVue architecture
Figure 1
Module 08 - OPC - Advanced
Page 4/11
3 Advanced 3.1 Optimize the communication with OPC As you know a SCADA project must consume as little bandwidth as possible. You can optimize the communication by managing several OPC groups. A starting point is to create at least three groups. Fast: Here you subscribe the items you want to be refreshed as fast as possible. We usually configure critical alarms only. Medium: Here you subscribe the general items. Most items of the application will be in this group. Slow: Here you subscribe the items that you don’t need to refresh very often.
3.2 Display the Status of the OPC Communication A set of System variables is automatically created after the OPC Configuration.
You can find the complete list in the PcVue Help file: F1\Application Explorer\Variables\System Variables\OPC status variables or click here. Check the System variables created after your configuration.
Figure 2
Module 08 - OPC - Advanced
Page 5/11
Exercise 1.
Switch off Kepware Server. Check the value of the following variables:
3.3 Advanced settings There are many advanced options in OPC configuration dialog boxes. In this topic we will describe the most commonly used. 3.3.1 Server Advanced parameters
To open the Server Advanced Parameters, open the Server properties and display the Advanced Parameters tab.
Figure 3
Connection/Reconnection The parameter is used to change the time to detect a lost connection and to manage the reconnection. By default PcVue sends a “ping” to the server every 10 seconds. If there is a failure Pcvue tries to reconnect every 60 seconds. Of course you can change these parameters.
Exercise 2.
Change the reconnection period to 20 seconds and check the result by switching off the Kepware server.
Module 08 - OPC - Advanced
Page 7/11
3.3.2 Group Advanced parameters
Figure 4
Deadband Some OPC Servers have a global Deadband parameter that applies the same deadband value to all items. In this case you have nothing to do except if you want to change it for a particular group.
If the Server doesn’t manage a global Deadband you must configure it in each OPC group in Pcvue. Timestamp By default the timestamp used by PcVue is the one from the OPC Server. If you want you can keep the Local timestamp by clicking the Local option.
Exercise 3.
Change the Deadband of the OPC group to 30% and check the value of the variables in the Variables Selector.
Module 08 - OPC - Advanced
Page 8/11
3.4 Activate the OPC Traces If you have a problem it is always good to have some logs (traces). You can analyze the log and use it to help find the problem. PcVue can generate traces for the Server connection and for each group. Whatever the traces, the output is always shown in the Event Viewer (\Bin\Log Files\Trace.dat). To enable the traces for the Server / Group object:
Step 1.
Open its Properties and select the Traces tab.
Step 2.
Select each available option.
Step 3.
Click “Save” button.
Figure 5
Exercise 4.
Activate the traces and check the event viewer.
Module 08 - OPC - Advanced
Page 9/11
3.5 How to map variables using Microsoft Excel If you have a large number of OPC variables, mapping them using PcVue can be a long process. Fortunately you can use a third party tool such as Microsoft Excel to create variables faster.
You can find the format of the file Varexp.dat in “DVD\Sv\Doc\English\VAREXP_100_ENU.pdf” in the chapter OPC variables.
Module 08 - OPC - Advanced
Page 10/11
4 Summing-up Always try to optimize the communication. OPC System variables are automatically generated and can be used to create a “system” mimic. There are many advanced options in the OPC dialog boxes. If there is any problem the first action is to activate the OPC Traces.
Module 08 - OPC - Advanced
Page 11/11
HMI
Module 09 Mimics - Basics
Contents
1
Introduction
3
1.1 In this module you will learn how to
3
1.2 Files used in this module
3
1.3 Third party software used in this module
3
2
This feature in PcVue architecture
4
3
Basics
5
4
3.1 The Workspace
5
3.2 The mimic object
8
3.2.1 Create a mimic
9
3.2.2 Operational modes
11
3.2.3 Mimic properties
11
3.2.4 How to open a mimic automatically on start-up
13
Summing-up
Module 09 - Mimics - Basics
14
Page 2/14
1 Introduction 1.1 In this module you will learn how to Customize the workspace, Use the main properties of mimics, Make the Homepage mimic.
1.2 Files used in this module Copy the PcVue project located in My Documents\Pcvue Training\Module_09\Project to C:\Pcvue projects\Usr\.
1.3 Third party software used in this module None.
Module 09 - Mimics - Basics
Page 3/14
2 This feature in PcVue architecture
Figure 1
Module 09 - Mimics - Basics
Page 4/14
3 Basics 3.1 The Workspace The workspace is the name given to the area occupied by the Supervisor on the PC screen. The workspace contains all the tools necessary to develop Supervisor applications and is the container for the windows that form the User Interface at runtime. Within the workspace you will find the following features:
Figure 2
The Menu Bar: The Menu Bar provides access, using either the keyboard or the mouse, to all the development tools. By using the mouse, the menu bar can be dragged and docked to any outside edge of the workspace, or it can be left floating anywhere on the screen. The menu bar may be opened and closed from a pop-up menu displayed by clicking with the right mouse button anywhere within the workspace’s background. A tick indicates that the menu bar is visible.
Module 09 - Mimics - Basics
Page 5/14
The toolbars: The toolbars give you quick access to the most commonly used tools for window development and run-time operation. As with the menu bar, the toolbars may be floating or docked. You can select which toolbars are open from a pop-up menu displayed by right-clicking anywhere on the menu bar. A tick indicates that a toolbar is open. The Status bar: The status bar is located at the bottom of the workspace, above any toolbars you may have docked there. It provides information on the current state of the workspace including the current cursor position and zoom level of the active window.
You can show and hide these bars using the Function keys F6 and F8.
The workspace’s appearance and behaviour are changed using the Display/Workspace Properties command.
Figure 3
The following properties may be changed. The size of the workspace and its location on the screen. The workspace colour. The appearance of the title bar and its contents. The tools that are available from the title bar. The number of monitors used (in the Regions tab) Module 09 - Mimics - Basics
Page 6/14
Exercise 1.
Change some of the Workspace’s properties and check the effect. Then customize it as follows:
Figure 4
The # character is a special character in PcVue. It is used to substitute a string. You will use this character many times in your design.
A list of the various substitutions for the title bar is available in the online Help in: The configuration environments / The HMI / Changing the Workspace Properties.
Module 09 - Mimics - Basics
Page 7/14
3.2 The mimic object The User Interface for your Project is developed as a set of mimics. Mimics are easily and quickly developed to form Menus, Overviews, Process Diagrams, Trend Displays and so on. Mimics may be linked together to form a hierarchical display. Of course you can have several mimics opened in the same time. The list of the opened mimics is displayed using the Window menu.
Figure 5: In this figure one mimic is open. Its name is Mimic1 and its title is Mimic1.
Figure 6: In this figure two mimics are open.
Each PcVue mimic is saved in a file of the same name - the mimic and file are effectively one and the same. For this reason the main commands associated with mimics are found in the File menu.
Figure 7
Module 09 - Mimics - Basics
Page 8/14
3.2.1 Create a mimic
Step 1.
To create a new mimic, use the File / New command or Control + N keys. A dialog opens to request the template you want to use for this mimic. Templates will be covered in another module. Click the OK button.
Figure 8
Step 2.
To save this mimic, use the File / Save command or Control + S keys. The Save mimic dialog appears. Enter the name and click the OK button.
Figure 9
Module 09 - Mimics - Basics
Page 9/14
Exercise 2.
Create the Homepage mimic.
Where is the Homepage file physically located?
What happens if I copy the Homepage file to another project?
Module 09 - Mimics - Basics
Page 10/14
3.2.2 Operational modes
Mimics can be displayed in a number of modes selected from the Mode toolbar. Run: In Run mode the animated properties of drawing elements in the mimic are updated in real time. Design: In Design mode the properties of drawing elements do not update in real time. Drawing elements may be added, modified and deleted and the support window modified. This is the mode of operation used while you are developing a mimic. 3.2.3 Mimic properties
Each mimic (as with any object in PcVue) has a set of properties. You can display them using the command Window / Window properties.... Because there are many properties they are organised in a range of tabs.
Figure 10
Module 09 - Mimics - Basics
Page 11/14
Exercise 3.
Change the properties of the Homepage mimic as in the following screenshot.
Figure 11
Module 09 - Mimics - Basics
Page 12/14
3.2.4 How to open a mimic automatically on start-up
Step 1.
Open the Application Explorer and, in the configuration tree, select the node representing the project. (Top of the tree)
Step 2.
From the task list select Settings.
Step 3.
Select Station startup.
Step 4.
Tick the First window option.
Step 5.
Select the mimic name by clicking the button adjacent to the Mimic
field.
Figure 12
Exercise 4.
Configure the TRAINING project to open the Homepage mimic automatically. Restart PcVue to test it.
Module 09 - Mimics - Basics
Page 13/14
4 Summing-up The Workspace can be customized. One mimic is one file. A mimic has many properties which can be customized.
Module 09 - Mimics - Basics
Page 14/14
HMI
Module 09 Mimics - Advanced
Contents
1
Introduction
3
1.1 In this module you will learn
3
1.2 Files used in this module
3
1.3 Third party software used in this module
3
2
This feature in PcVue architecture
4
3
Advanced
5
3.1 Mimic and window
5
3.2 Managing a big mimic
6
3.2.1 Scaling the mimic
6
3.2.2 Using scroll bars
7
3.2.3 Using the Navigator
9
3.3 Managing screen resolutions
11
3.4 Useful options
13
3.4.1 Mimic opening mode
4
Summing-up
Module 09 - Mimics - Advanced
13
14
Page 2/14
1 Introduction 1.1 In this module you will learn The difference between a mimic and a window, How to manage big mimics, How to adapt a mimic to different screen resolutions, Other kinds of tuning.
1.2 Files used in this module PcVue project developed in the Basic module.
1.3 Third party software used in this module None.
Module 09 - Mimics - Advanced
Page 3/14
2 This feature in PcVue architecture
Figure 1
Module 09 - Mimics - Advanced
Page 4/14
3 Advanced 3.1 Mimic and window The terms window and mimic are used many times throughout this manual and are generally interchangeable. However there is a subtle difference between a window and a mimic that is important to understand, particularly if you are manipulating windows and mimics programmatically. For readers who are familiar with the classic Microsoft Document/View architecture, Mimic is equivalent to Document and Window equivalent to View. We can sum up the difference between a mimic and a window as follows: “The mimic is the content (the data) and the window is what you see on the screen”. In following diagram you can see a mimic and a window. The mimic contains many graphical objects. The window displays only a part of this mimic so the rest of it would not be visible in the HMI.
Figure 2
Module 09 - Mimics - Advanced
Page 5/14
3.2 Managing a big mimic A mimic can be larger than the screen (or the window). PcVue can manage it in three ways. 3.2.1 Scaling the mimic
To scale the mimic to the window size you must set the option Scale mimic to fit window in the tab Window properties / Display.
Figure 3
This option can produce some graphical side effects mainly with text and bitmaps. Use it only in specific cases.
Module 09 - Mimics - Advanced
Page 6/14
Exercise 1.
Open the mimic BigMimic_Scale. Check the properties and the effect.
3.2.2 Using scroll bars
To use the scroll bars you must set the option Allow mimic to be larger than window in the tab Window Properties / Display.
Figure 4
Module 09 - Mimics - Advanced
Page 7/14
Exercise 2.
Open the mimic BigMimic_Scroll. Check the properties and the effect.
You can navigate using the panning tool by pressing and holding down Shift + the mouse’s middle button.
Module 09 - Mimics - Advanced
Page 8/14
3.2.3 Using the Navigator
The Navigator is a useful tool that allows the user to navigate graphically in the mimic. To activate it you must set the option Enable Navigator in the tab Window Properties / Navigator.
Figure 5
In Design mode you can use the Navigator via the Display / Navigator command (Menu bar).
Figure 6
Module 09 - Mimics - Advanced
Page 9/14
In Run mode the Navigator is automatically embedded in the window.
Figure 7
Exercise 3.
Open the mimic BigMimic_Navigator. Check the properties and the effect.
Module 09 - Mimics - Advanced
Page 10/14
3.3 Managing screen resolutions Sometimes you design a project in one resolution but the target computer has another resolution. PcVue can manage this situation by adapting the mimic automatically to the new resolution. By default this option is not activated. To activate it you must set the option Screen Resolution / Adapt mimic size to screen resolution in the dialog Configure / HMI Options....
Figure 8
Module 09 - Mimics - Advanced
Page 11/14
You can check in which resolution a mimic has been created in the tab Windows Properties / Advanced.
Figure 9
Exercise 4.
Activate the option Adapt mimic size to screen resolution. Change the resolution of your screen. Open the Homepage mimic.
Module 09 - Mimics - Advanced
Page 12/14
3.4 Useful options 3.4.1 Mimic opening mode
By default, a mimic opens in Run mode. This is not convenient when you are developing your project. You can configure PcVue to open the mimic always in Design mode using the option Mimics open mode / in the dialog Configure / HMI Options.... Remember to change it back when you have completed your development!
Figure 10
Exercise 5.
Activate the option Mimics open mode / . Test it.
Module 09 - Mimics - Advanced
Page 13/14
4 Summing-up PcVue provides several features for handling large mimics. PcVue can manage different resolutions for the same project.
Module 09 - Mimics - Advanced
Page 14/14
HMI
Module 10 Basic graphical objects Basics
Contents
1
Introduction
3
1.1 In this module you will learn
3
1.2 Files used in this module
3
1.3 Third party software used in this module
3
2
This feature in PcVue architecture
4
3
Basics
5
3.1 The basic graphical objects
4
5
3.1.1 Insert a shape
5
3.1.2 Select multiple objects
6
3.1.3 Duplicate a graphical object
7
3.1.4 Properties of objects
9
3.2 The Arrange tools
11
3.2.1 Using groups
12
3.2.2 Lock objects
12
3.2.3 Managing the ordering objects
12
3.2.4 Moving and resizing objects
12
3.3 Create a button
13
3.4 Using images
15
3.4.1 Insert an image
15
3.4.2 Transparent color
16
3.4.3 Image from the PcVue Library
18
Summing-up
Module 10 - Basic graphical objects - Basics
19
Page 2/19
1 Introduction 1.1 In this module you will learn About the basic shapes, About the main properties of shapes, About the Arrange tools, How to create a button, How to insert an image in a mimic.
1.2 Files used in this module Copy the PcVue project located in My Documents\Pcvue Training\Module_10\Project to C:\Pcvue projects\Usr\..
1.3 Third party software used in this module None.
Module 10 - Basic graphical objects - Basics
Page 3/19
2 This feature in PcVue architecture
Figure 1
Module 10 - Basic graphical objects - Basics
Page 4/19
3 Basics 3.1 The basic graphical objects All graphical objects available in PcVue are located in the Drawing toolbar.
Figure 2
[A] Selection tools: also in the Draw Menu. [B] Properties tools: also in the Edit Menu. [C] Basic graphical objects (shapes): also in the Draw Menu. [D] Special objects: also in the Insert Menu. [E] Macro animation objects: also in the Insert Menu. This module covers only [A], [B] and [C]. 3.1.1 Insert a shape
