Isagraf 5 user manual_handson

Hands on ISaGRAF

Software release 5.2

June 2009

Hands on ISaGRAF

Printing History1st printing — October, 2007

2nd printing — March, 2008

3rd printing — January, 2009

4th printing — June, 2009

? Copyright 1999-2009: ICS Triplex ISaGRAF Inc

All rights reserved. No portion of this work may be reproduced in any form or by any means, without the prior written permission of ICS Triplex ISaGRAF Inc.

Table of Contents

Hands on ISaGRAF_________________________________ 1 Getting Started with ISaGRAF (4)

Exploring an Existing Project (5)

Open the Project (5)

Project Description (7)

View the Declared Variables (11)

Open the SFC Program (12)

Open the LD Program (14)

Open the I/O Wiring Tool (15)

Build the Project Code (16)

Simulate the Project (17)

Starting with a Simple Project (19)

Create the Project (19)

Create a POU in the Resource (22)

Define the Program (24)

Modify the Variables in the Dictionary (26)

Set Up the I/O Wiring (27)

Simulate the project (30)

Creating a Distributed Project with Bindings (33)

Create the Project (33)

Create POUs in the Resources (36)

Create a Group of Variables in your Resources (37)

Declare Variables in the Dictionary (39)

Define the Programs (41)

Define the Bindings (44)

Simulate the Project (45)

Distributing an IEC 61499 Program across two Resources (47)

Create a typical IEC 61499 project (47)

Create IEC 61499 user-defined function blocks (51)

Declare IEC 61499 Function Block Instances (58)

Create an IEC 61499 program (60)

Simulate the Project (66)

Creating an ISaGRAF 3 Project (69)

ISaGRAF5.2 - Workbench i

Create an ISaGRAF 3 project (69)

Create the program (73)

Simulate the Project (77)

Importing an ISaGRAF 3 Project (81)

Import the ISaGRAF 3 Project (82)

Replace TSTART and TSTOP statements for use with ISaGRAF 5 targets 85

Simulate the project (87)

ii ISaGRAF5.2 - Table of Contents

Hands on ISaGRAF

ISaGRAF is the leading IEC 61131 automation software technology. It is used by automation system vendors and OEMs ( original equipment manufacturers ) to create products to address the embedded, stand alone, or distributed control systems needs. ISaGRAF also complies with the international standard defining the methods to use function blocks to distribute a control algorithm across multiple resources (as defined into the IEC 61131-3 standard). Developed by the International Electrotechnical Commission (IEC), IEC 61499 presents guidelines for the use of function blocks in distributed industrial process, measurement, and control systems.

An IEC 61499 diagram supersedes the implementation of individual applications. While an application would traditionally be implemented on individual controllers in traditional automation, interacting with each other through manually implemented data transfers or interlocks, the IEC 61499 function block diagrams span over multiple devices (previously referred to as configs or controllers) and regulates the interaction between the various devices. When using ISaGRAF5.2, it is now possible to create control systems that define interactions between multiple devices that could be PLCs, field controllers, field instruments (flowmeter, valves, pumps, etc), with variable footprints, but all interacting in a well defined and coherent fashion.

ISaGRAF5.2 - Workbench1

2ISaGRAF 5.2 - Hands On ISaGRAF 5.2 offers unparalleled functionality and benefits by incorporating both the IEC 61131-3 and IEC 61499 standards. With ISaGRAF 5.2, users will have the ability to build traditional control systems where the interactions between devices will be automatically regulated and synchronized by the IEC 61499 function block diagrams rather than through the use of manually implemented algorithms.

In creating the automation system, one would traditionally start by looking at individual control applications and then determine how to have these interact with the other ones. Under ISaGRAF 5.2, although the same methodology may be used in defining the local behavior of the control devices, one would define global diagrams using the IEC 61499 environment and would drop in function blocks to regulate the behavior of the cooperating devices.Each IEC 61499 function block is made of two parts:

the top part holds the ECC ( Execution control chart ). The IEC 61499 specifies that this

part should be programmed using a state machine. Under ISaGRAF 5.2, it is conveniently programmed using SFC which happens to be an ideal state machine.

the bottom part defines the actual control function. Is can be programmed using any of

the IEC 61131-3 languages.

Each IEC 61499 function block is assigned to a specific resource. These resources will eventually be assigned to a given device (called config under IEC 61131-3) and one device can hold more than one resource. An IEC 61499 diagram then spans over multiple resources which can also mean over multiple devices.

The ISaGRAF application Workbench is a 32-bit environment ...

522090608FM72WWP70HW13

ISaGRAF5.2 - Workbench3

Getting Started with ISaGRAF

The ISaGRAF workbench is designed to build process control applications. These applications can be distributed across several platforms, communicating with each other through networks. An ISaGRAF project shows the distribution and links between each PLC loop. The PLC loop is executed by the ISaGRAF virtual machine on each platform.

To familiarize yourself with the views, buttons and vocabulary of ISaGRAF, you can work through an existing project with comments.

indicates supplementary information regarding an aspect of ISaGRAF

Many actions you perform in ISaGRAF are done with the mouse. The mouse cursor is a diagonal arrow. It is important to understand the terms used in the documentation set with respect to the mouse.

You can use a two-button mouse in ISaGRAF. The left mouse button is the primary button, unless you configured it differently. The secondary button is referred to as the right mouse button.

Click means to press and immediately release the primary mouse button without moving the mouse.

Right-click means to click the right mouse button.

Double-click means to click the left mouse button twice.

Select means to click an item to indicate that it will be the object of the next operation. In

a scrolling list, a selected item is highlighted; in a graphical editor, handles appear on the

outer edges of a selected element.

Point means to position the tip of the cursor at the location you want to point to on the screen.

Drag means to point and hold down the primary mouse button as you move the mouse.

4ISaGRAF5.2 - Hands On

ISaGRAF 5.2 - Workbench 5Exploring an Existing Project

This section describes a demo project that is included with the default installation.Open the Project

https://www.360docs.net/doc/fe9181341.html,unch the workbench by clicking on the ISaGRAF icon.

.2.To open the

Demo project, click on the Standard toolbar.

3.In the Open dialog, in the Prj directory, locate the Demo directory:

4.In this directory, double-click the PRJLIBRARY .MDB file.

5.When prompted to specify a repository path, click OK .

The Demo project is opened in the Workbench.

Database

The PRJLIBRARY.MDB file is a Microsoft Access database where the project definitions are stored: architecture, names, descriptions, variables… The only items that are not stored in the database are the program source files. These source files are stored as text files in sub-directories for the project.

6ISaGRAF5.2 - Hands On

ISaGRAF 5.2 - Workbench 7Project Description

The purpose of the "Demo" project is to make an output blink at a certain period. The sequence to start or stop the blinking comes from a distant platform. This project is composed of two resources: one called "MASTER" and the other "SLAVE".

Resource A resource corresponds to a PLC loop. It is composed of programs. A resource is compiled and its code is downloaded onto a configuration to be executed by the ISaGRAF

virtual machine (or kernel).

Hardware Architecture Configuration

Each of these resources is located on a separate hardware platform, or configuration, linked by an Ethernet network. The following shows the "Hardware architecture" view of the "Demo"project.

Configurations

Resources

Driver

Network

Configurations

8ISaGRAF 5.2 - Hands On

"

To switch to the Hardware architecture view, click

on the Window buttons toolbar. Target

A configuration is attached to a target. A target contains definitions about the hardware platform and the virtual machine running on it. To observe that the target is attached to the NT-Target, double-click the configuration's title bar to view its hardware properties.NT-Target is the Windows NT target delivered by ICS Triplex ISaGRAF.

When you select a target, it affects:

The possible code types that you can generate for the resources of this configuration The list of "C" functions and "C"function blocks that you can call in your programs The list of I/O devices that you can use

The list of networks that you can connect to your configuration

Resources

Driver Network Instance

ISaGRAF 5.2 - Workbench 9

Network Instance In the hardware architecture view, you can also observe that both resources communicate via the ETCP network. ETCP is the standard driver developed by ICS Triplex ISaGRAF to

communicate over Ethernet using the TCP/IP protocol. ETCP means Enhanced TCP/IP protocol because it emulates, in this case, the behavior of a fieldbus. ETCP can be viewed as a virtual fieldbus. The Workbench debugger also uses ETCP to communicate with the resources running on the configurations.

Note: Any network driver can be implemented.

To view the list of available networks, double-click on the network item in the hardware architecture view (only ETCP is available for the standard installation ). To view the contents of each resource, switch to the link architecture view.

Link Architecture

The following shows the Link architecture view of the Demo project.

"To switch to the "Link architecture" view, click on the Window buttons toolbar.Resources

SFC Program Binding link LD Program

The first resource is composed of one SFC (Sequential Function Chart) program that sends commands to the other resource. The SFC program sequences the time during which the Run variable is set to TRUE. This Run variable is produced to the second resource via a binding link. In the second resource, the Run variable makes the Blink block run, or not run, in the BlinkOut LD program (Ladder Diagram). In the BlinkOut program, the BLINK standard function block sets / resets an output variable.

Programs, functions, or function blocks, which may make up a resource, are also called POUs (Program Organization Unit). POUs located in the Programs section make up the PLC loop executed by the Virtual machine.

A binding link always starts from a producer resource and ends at a consumer resource.

To view existing bindings and to define new ones, double-click on a binding link to open the binding list window.

The definition of a new binding consists in selecting three items:

a variable in the producer resource

a variable in the consumer resource

a network driver

This driver sends or produces the value of the producer resource variable and assigns the corresponding variable in the consumer resource. The following shows the binding list window.

The left part of the window displays the resource-binding grid: bindings between resources. The right part of the window displays the variable-binding grid: bindings between variables. Clicking on the top-right button closes this window. The next step is the declaration of

variables.

10ISaGRAF5.2 - Hands On

ISaGRAF 5.2 - Workbench 11View the Declared Variables

Variables are declared in the dictionary view.

1.To access the dictionary view, click

on the Window buttons toolbar.2.In the tree on the left, double-click Variables, then MASTER, then Any group, then

All variables.

A grid is displayed on the right side of the screen. 3.Note that two TIME variables and one BOOL variable are declared. Declaration of

variables is performed within this grid. You can view the variables declared for the SLA VE resource by expanding its structure in the tree.

4.

To view the contents of each program, switch to the link architecture view by clicking

on the Window buttons toolbar.

12ISaGRAF 5.2 - Hands On Open the SFC Program

SFC programs are opened in the SFC editor.

1.In the MASTER resource window, double-click the DriveSlave program.

The DriveSlave program is displayed in the SFC editor.

2.To change the zoom level of the SFC chart, choose a setting from the list

on the options toolbar.The DriveSlave SFC chart is defined as follows:This SFC loops and sets the Run variable to TRUE during the TimeOn period.

Step S1 has no action (action block with

no name / no code is ignored)

Transition T1: waits for activity of S1 to

reach TimeOff (TimeOff initial value is 5

seconds – see dictionary section)

S1.T is the step duration

Step S2 is composed of one Boolean

Non-stored action. Run variable is set to

TRUE when S2 becomes active and reset

to FALSE when S2 is deactivated.

Transition T2: waits for activity of S2 to

reach passed TimeOn. (TimeOn initial

value is 10 seconds – see dictionary

section) S2.T is the step duration

ISaGRAF 5.2 - Workbench 133.To view the programming in the level 2 of a step or transition, double-click its symbol or

on the level 2 rectangle appearing to its right.

4.To close the SFC editor, from the File menu, choose Exit

.

Open the LD Program

LD programs are opened in the multi-language editor. The multi-language editor enables the edition of ST, FBD, LD, and IL programs.

1.In the SLA VE resource window, double-click the BlinkOut program.

The BlinkOut program is displayed in the multi-language editor.

The BLINK standard function block only runs when the Run variable is TRUE. The "OutValue" is set to TRUE according to the following time diagram:

2.To close the multi-language editor, from the File menu, choose Exit.

The next step is to look at the I/O wiring in the second resource to observe which I/O device the OutValue variable is wired to.

14ISaGRAF5.2 - Hands On

Open the I/O Wiring Tool

The I/O wiring tool enables the definition of links between the variables defined in a project and the channels of the devices existing on the target system. Wiring is performed at the resource level, therefore, I/O wiring is only available when a resource is selected and when a target has been attached to the current configuration.

1.

Select the Slave resource window, then click on the Window Buttons toolbar. The tree on the left shows the only device used for the resource: a device for Output Boolean variables. This device is for simulation purposes only.

2.To view the channels of the device, expand the device by clicking + in front of the device

name.

3.Note that the OutValue variable is wired to the only channel of the device.

4.To close the I/O Wiring tool, from the File menu, choose Close.

ISaGRAF5.2 - Workbench15

16ISaGRAF 5.2 - Hands On Build the Project Code

The Workbench generates, i.e., builds code for resources. This code is either run in simulation or downloaded onto a target.

1.To generate the code for the project, click

on the Standard toolbar.The database is checked, then the resource code and the project are built.2.

In the Output window, note the results of the build:Project DEMO: 0 error(s), 0 warning(s) Output Window

The Output window is a window that appears, by default, at the bottom of the current window.This window can be manipulated as a toolbar (it can be docked on one side of the workspace).The height of the output window can be changed using the slider at its top. The output window shows the result of the code generation and during testing it shows, the execution messages.Slider to change height of the output window