PC-based System

ELOP II

First Steps

HIMA Paul Hildebrandt GmbH + Co KG

Industrial Automation

HI 800 001 AVA

All HIMA products mentioned in this manual are protected by the HIMA
trademark. This also applies to other manufacturers and their products,
unless otherwise stated.

It is forbidden to pass on or copy this document or to exploit and reveal its

contents without our express permission. Contravention’s shall be liable to
damage claims.

All technical information and instructions in this manual were created with
great care and with the incorporation of effective control measures.
However, the possibility of errors can never be completely excluded.
HIMA must therefore point out that neither a guarantee nor legal
responsibility nor any liability can be accepted for consequences arising
from incorrect details. HIMA will always be grateful to readers who point out
any errors.

We reserve the right to make technical modifications.

Further information can be found in the documentation on the CD-ROM

and on our web site under www.hima.de.

Information enquiries must be directed to:

HIMA Paul Hildebrandt GmbH + Co KG

Post-box 12 61
68777 Brühl

Tel: +49 (6202) 709 0

Fax: +49 (6202) 709 107

Email: [email protected]
Contents

1 BRIEF OVERVIEW................................................................................1
1.1 SCOPE OF DELIVERY .........................................................................1
1.2 INFORMATION ABOUT THIS MANUAL ....................................................1
1.3 SUPPORT .........................................................................................2
2 INSTALLATION.....................................................................................3
2.1 HARD- AND SOFTWARE REQUIREMENTS.............................................4
2.2 W HERE TO INSTALL ...........................................................................4
2.3 HOW TO START THE INSTALLATION .....................................................5
2.4 NETWORK INSTALLATION ...................................................................6
2.5 DE-INSTALLATION..............................................................................6
3 INTRODUCTION TO ELOP II ...............................................................7
3.1 STARTING ELOP II ...........................................................................7
3.2 STANDARD SCREEN ELEMENTS .........................................................8
3.3 TITLE BAR ........................................................................................9
3.4 MENU BAR........................................................................................9
3.5 SYMBOLS BAR ................................................................................10
3.6 STATUS BAR ...................................................................................10
3.7 STRUCTURE W INDOW .....................................................................11
3.7.1 Context Menu for Objects......................................................12
3.8 W ORKING AREA ..............................................................................13
3.8.1 Function Block Diagram Editor (FBD Editor).........................13
3.8.2 Document Editor....................................................................14
3.9 ERROR STATE VIEWER....................................................................15
3.10 ONLINE HELP ..................................................................................15
4 OBJECTS IN THE STRUCTURE WINDOW .......................................17
4.1 PROJECT ........................................................................................17
4.2 LIBRARY .........................................................................................17
4.2.1 Program Type........................................................................17
4.2.2 Function Block Type ..............................................................18
4.2.3 Function.................................................................................18
4.3 CONFIGURATION .............................................................................19
4.3.1 Resource ...............................................................................19
4.4 DOCUMENTATION ............................................................................20

I
5 BASIC FEATURES OF ELOP II .........................................................21
5.1 PROJECT MANAGEMENT ..................................................................21
5.2 BUILDING BLOCK LIBRARIES ............................................................22
5.3 FUNCTION BLOCK DIAGRAM EDITOR .................................................23
5.3.1 Maximizing the Working Area................................................24
5.3.2 Maximizing and Restoring Panes..........................................25
5.4 FUNCTION DIAGRAMS WITH CENTERED STARTING POINT ..................26
5.4.1 Zoom .....................................................................................27
5.5 CREATE LOGIC ...............................................................................28
5.5.1 Organization of Variables ......................................................28
5.5.2 Drag & Drop of Variables ......................................................30
5.5.3 Drag & Drop Function Blocks ................................................31
5.5.4 Connecting Elements ............................................................32
5.6 CREATING AND MANAGING DOCUMENTATION ...................................33
5.6.1 Templates for Printing Documents ........................................34
5.7 OFFLINE SIMULATION OF THE LOGIC ................................................36
6 WORKING WITH RESOURCE TYPES...............................................37
6.1 DEFINING A RESOURCE ...................................................................38
6.2 ASSIGNING A PROGRAM TYPE TO A RESOURCE ................................39
6.3 IO ASSIGNMENT .............................................................................40
6.4 ASSIGNING SYSTEM VARIABLES .......................................................42
6.5 CODE GENERATOR .........................................................................43
6.5.1 Code Comparator ..................................................................43
6.6 CONTROL PANEL ............................................................................44
6.6.1 Download...............................................................................45
6.7 ONLINE TEST ..................................................................................47
6.8 HARDWARE DOCUMENTATION..........................................................48
7 EXERCISES ........................................................................................49
7.1 CREATING A PROJECT .....................................................................49
7.2 CREATING A FUNCTION BLOCK ........................................................54
7.2.1 Variable Declaration ..............................................................54
7.2.2 Function Block Layout ...........................................................57
7.2.3 Develop Logic in the Drawing Area .......................................61
7.3 CREATING A PROGRAM ...................................................................66
7.3.1 Variable Declaration ..............................................................66
7.3.2 Develop Logic in the Drawing Area .......................................66
7.4 CREATING CONFIGURATION AND RESOURCE ....................................67
7.5 OFFLINE SIMULATION OF A LOGIC ....................................................72
7.6 PLC CABINET LAYOUT AND VARIABLE ASSIGNMENT .........................80
7.7 RUNNING A PROGRAM ON A PLC .....................................................86
II
 7.7.1 Compile Program...................................................................86
7.7.2 Communication between PC and Controller .........................88
7.7.3 Download and Start ...............................................................95
7.8 ONLINE TEST ..................................................................................99
7.9 FORCING INPUTS AND OUTPUTS ....................................................102
7.10 DOCUMENTATION ..........................................................................108
7.11 BACKUP A PROJECT ......................................................................114
7.11.1 Archiving..............................................................................114
7.11.2 Restore a Project.................................................................116
8 APPENDIX.........................................................................................119
8.1 INDEX ...........................................................................................119
8.2 LIST OF ABBREVIATIONS ................................................................125

III
IV
1 Brief overview

1.1 Scope of Delivery

The ELOP II scope of delivery includes:

• This manual
The manual “First Steps” enables you to obtain a speedy and simple
introduction to the operation of ELOP II. For this purpose, in addition
to an overview of the functions, it provides step-by-step instructions
to create a project.
• A CD-ROM
Besides the ELOP II software, the CD-ROM also contains a few help
programs and the documentation for the current HIMA automation
systems.
• A hardlock (Dongle)
The hardlock is for license administration (protection against
unauthorized use) of the protected ELOP II software.

1.2 Information about this Manual

In this manual, the user will find things worth knowing to familiarize himself
with the most important functions of ELOP II in the context of a training
course or auto-didactically.

The installation of ELOP II is explained in Chapter 2. Chapters 3 to 6

describe in general terms how to use and operate ELOP II. Users without
any prior knowledge should read through this section carefully.

Chapter 7 contains exercise lessons, on the basis of which users who

already have some basic knowledge of ELOP II can familiarize themselves
with how to create projects or increase their knowledge.

The Appendix in Chapter 8 contains explanations on the specialist terms

used, the index register and the list of abbreviations.

1
1.3 Support
You have a choice of various possibilities if you have any questions on
operation or reporting program errors, or if you wish to make suggestions
about improvements.

Frequent Chapter in this manual Questions and answers

questions on basic subjects

News, FAQ’s, Our Web page News, frequently asked

Download www.hima.com questions, functional
objects

Questions and Per email:

ideas
[email protected]

Phone: Between 9:00 and 17:00

Central European Time
+49-(0)6202-709 259 (on working days)
+49-(0)6202-709 261

Fax:

+49-(0)6202-709 199

In order to obtain all the relevant information in replies about ELOP II,
please use the PFR editor (Product Feedback Report), which you will find
on the CD-ROM.
Note: This manual is part of the documentation for the ELOP II
seminars at HIMA. Because of the powerful nature of ELOP II,
we can only show the most important functions of the program
here.

It is recommended that you participate in a seminar in order to

deepen your knowledge.

2
2 Installation

This chapter covers:

• What is required?
• Where is it installed?
• How is installation started?
• Installation in the network
• De-installation
ELOP II is a hardware-protected program. The hardlock module (dongle)
must be connected to the parallel port.

Fig. 1 Hardlock

To address the hardlock module, a driver must be installed on the

computer. To install the driver a user must be registered under Windows
NT® with administrator rights . If in doubt, consult the system supervisor.

3
2.1 Hard- and Software Requirements
Besides the personal computer, you need the hardlock and the installation
CD-ROM.

The computer hardware requirements are as follows :

Minimum Recommended
Processor Intel Pentium II® 133 MHz 400 MHz
RAM 64 MB 128 MB
Graphic card 2 MB 8 MB
XGA (1024x768) XGA (1024x768)
Operating system Windows NT® Workstation
(the latest service pack is
recommended)
Table 1: PC hardware requirements

If a printer is connected to the hardlock , the printer should be switched on.

Some printers have an insufficient load resistance when switched off.

2.2 Where to Install

You can perform installation onto the local hard disk or onto a network drive
(see Chapter 2.4).

If ELOP II should be accessible to different users (with different user

names) on one computer, ELOP II must be installed for each of the users
individually. The procedure for multiple installation can be found in the
online help of ELOP II or in the installation program.

4
2.3 How to start the installation
The installation of ELOP II and all additional components can be invoked
from the installation menu of the CD-ROM.

The CD-ROM also contains the complete documentation of the software

and of the system family H41q/H51q as PDF files. The reader required for
displaying these files, Adobe Acrobat Reader, is included.

How to start the installation:

1. Insert the CD-ROM into the CD drive. The installation menu is started
automatically.
If the installation menu does not start automatically, open the root
directory of the CD-ROM in the Windows Explorer and double click on
the file “START.EXE“.

Select the language to be installed by choosing for German or

for English.

2. Click on the button “ELOP II“.

3. Click on the button “Hardlock“.

4. After installation of the hardlock driver, click on the button “ELOP II“ for
installing ELOP II.

5. After successful installation, the ELOP II Control Center appears from

where you can start ELOP II and additional programs. The Control
Center and the project management can be called up from the
Windows Start menu in the ELOP II directory.

Fig. 2 Start menu ELOP II

5
2.4 Network Installation
1. Installation is performed as described in Chapter 2.3, whereby a
directory on a network server is selected as the destination.

2. Release the installation directory for the other users.

3. Perform the workstation installation for each workstation and user by

running the program WS_SETUP from the installation directory of the
server.

2.5 De-installation
To de-install ELOP II, start the Control Center and select "Uninstall".
Depending on the security settings of your browser, next choose the
selected program.

6
3 Introduction to ELOP II

This chapter covers:

• Starting the program

• Elements of the user shell of ELOP II
• Menu and title bar
• Symbol and status bar
• Screen panes, structure window and working area
• Error state viewer
ELOP II is a program with numerous functions, but access is simplified by
the intuitive user guidance.

3.1 Starting ELOP II

In the Start menu, select the register Programs and there:

Fig. 3 Start menu ELOP II

Alternatively, you can also start the project management in the ELOP II
Control Center.

7
3.2 Standard Screen Elements
After ELOP II is started, the standard screen appears as shown in Fig. 4.
The standard screen basically consists of the following elements:
1 Title bar
2 Structure window
3 Menu bar
4 Symbols bar for the project management
5 Working area
6 Symbols bar for the Function Block Diagram editor
(FBD editor)
7 Error state viewer
8 Status bar with coordinate information of the Function Block
Diagram editor

1 2 3 4 5 6 7 8

Fig. 4 ELOP II standard screen

8
3.3 Title Bar
In addition to the standard functions for maximizing, minimizing and closing
the window, the title bar contains information about the project and about
the object processed.

Project directory Object

Fig. 5 Title bar

3.4 Menu Bar

Most functions of ELOP II are available in the menu bar.

Fig. 6 The “Project“ menu

9
3.5 Symbols Bar
The symbols bar is shown under the menu bar and is split into the parts
“Project management“ and “Function Block Diagram editor”.

Fig. 7 Symbols bar for the project

Fig. 8 Symbols bar for the Function Block Diagram editor

Note: If the mouse pointer is positioned over a button for a short time,
a “Quick-Info“ (short Help text) appears.

3.6 Status Bar

Information texts and help texts of the project management and of the
Function Block Diagram editor, and also the present pointer position, are
displayed in the status bar on the bottom edge of the window.

Fig. 9 Status bar

10
3.7 Structure Window
In the structure window, the project is displayed in its hierarchical structure.
You can choose between three views with different degrees of detail.

Entire project

1)
All POUs All data types

Fig. 10 Structure window

1)
Program Organization Unit (object)

11
3.7.1 Context Menu for Objects
Open the context menu of an object by right-clicking on the object in the
structure window. The individual commands are selected as usual by
clicking on the command with the left mouse button.

Fig. 11 Context menu of the project

12
3.8 Working Area
In the working area (see Fig. 4), you process the data objects with the

• Function Block Diagram editor and the

• Document editor.

3.8.1 Function Block Diagram Editor (FBD Editor)

With the Function Block Diagram editor, you create the function diagrams
in the Function Block Diagram language (FBD) or in the Sequential
Function Chart language (SFC, sequences).
The Function Block Diagram editor (Fig. 12) comprises the panes
1 Drawing area
2 Variable declaration editor
3 Overview window
4 Interface declaration editor

1 2 3 4

Fig. 12 Function Block Diagram editor

13
3.8.2 Document Editor
With the document editor, you create the documentation for a project. A
common revision management can be used for all documents. Simply drag
the item to be documented to the open document editor and drop it.

Click on the button “1 2 3” to update the table of contents.

Fig. 13 Document editor

14
3.9 Error State Viewer
Error messages are displayed in the Error state viewer. The occurrence of
a new error message is reported by a flashing symbol in the Windows
task bar.

Fig. 14 Error state viewer

3.10 Online Help

In the online help you find detailed descriptions of all functions of ELOP II.
With the aid of the index you can quickly obtain help on key words.

Fig. 15 Online Help

15
16
4 Objects in the Structure Window

This chapter covers:

• The hierarchical structure of the objects in the structure window.

• The meaning of the objects.
All objects of a project are displayed in the structure window (also see Fig.
10) in their hierarchical order. The project management is carried in the
structure window.

4.1 Project
The project is the superordinated object. All other objects are created
under a project. Only one project may be opened in ELOP II at a time.

4.2 Library
The library contains functions, function blocks and programs. In the
terminology of IEC 61131-3 functions, function blocks and programs are
also referred to as Program Organization Units (POU). ELOP II contains
standard libraries with ready-made functions. You use these functions to
create your own more complex Program Organization Units.

4.2.1 Program Type

A program type contains all functions of an application. A program type

can be assigned to several controllers for execution. A controller is
executing a program instance of the program type created in the library.

17
4.2.2 Function Block Type

The Function block type contains partial functions of an application,

comparable with a sub-routine. The Function block type can also be used
for structuring the program according to the system structure. The Function
block type can temporarily store values in local variables. The output value
depends on the input values and the temporarily stored values (typical
example: Flip-Flop, Timer).

In addition, the Function block type can be used to access external

variables (global variables of a program).

4.2.3 Function

The function contains basic functions of an application. Contrary to the

Function block type a function cannot store any statuses. The output value
depends only on the input values (typical example: AND, OR).

18
4.3 Configuration
The configuration groups controllers into logic units, between which a
communication connection can exist.

4.3.1 Resource

The resource is the term defined in IEC 61131-3 for a target system that
executes the program, i.e. the HIMA controller.

4.3.1.1 Program instance

The program instance is a reference to a program type that already

exists in a library. The program is run on this resource (PES). Controller-
specific settings such as communication variables and system variables
must be defined in the program instance and not in the program type
!

4.3.1.2 Task

A task defines the execution of a program in a resource. ELOP II

supports multitasking, but HIMA controllers only allow the execution of a
single program (= a single program instance).

The task is required only for offline simulation to define the cycle time for
the execution of the assigned program instance on the PC.

19
4.3.1.3 Project Root

The Project Root is required for the internal search algorithm. This
object serves to influence the search order and may only be changed by
experienced users.

4.4 Documentation
The documentation allows the arrangement of the objects being
documented by way of Drag & Drop. Users can perform revision
management for all included documents.

20
5 Basic Features of ELOP II

This chapter covers:

• Project management
• Creating functions
• Documentation management
This chapter explains the basic features of ELOP II and helps to improve
your knowledge of the program. Practical examples can be found in
Chapter 7.

5.1 Project Management

The project management is the organization center for working with
ELOP II. At the top of the structure window the project folder is shown (see
Fig. 10, left side).

You can
- Open or close a project (use the menu bar or the buttons in the
symbol bar)
- Archive or restore a project (use the context menu)
In the project template, which also opens via the menu bar, you can make
numerous pre-settings for the layout.

An open project is displayed in the structure window.

21
5.2 Building Block Libraries
A project can consist of as many desired
libraries with numerous building blocks.
Libraries can be created in a project, a
configuration, a resource or another
library .
This allows to structure the libraries in
accordance with the logic.

The basic functions of IEC 61131-3 are

gathered in the library "StandardLibs",
which is automatically included when a
new project is created.

The library "ELOP-LIB" contains HIMA-

specific function blocks, mainly for
processing the safety IO level.

Fig. 16 Libraries in the structure

window

22
5.3 Function Block Diagram editor
The Function Block Diagram editor starts automatically, when a function,
function block or program (POU) is opened. The panes

• Drawing area
• Interface declaration editor
• Variable declaration editor
• Overview window
are shown in a window inside the working area of the project management
as saved in the last project.

Fig. 17 Function Block Diagram editor in the working area

Extra functions are provided to switch between the maximized working area
and the general overview.

23
5.3.1 Maximizing the Working Area
You can hide and show the structure window in Fig. 17 with the button
in the left group of buttons in the symbols bar. To hide and show the
Error state viewer , use the button .

This enables the working area for the Function Block Diagram editor to be
enlarged or reduced.

Fig. 18 FBD editor in the maximized working area

Note: The size of the working area can also be enlarged by dragging
the boundaries towards the variable declaration editor and
towards the interface declaration editor.

24
5.3.2 Maximizing and Restoring Panes
To activate a window in the working click inside the window (Fig. 18). The
active window can be maximized using the button in the right group of
buttons of the symbols bar.

Fig. 19 Maximized drawing area

Pressing the button again causes the panes of the Function Block Diagram
editor to be shown in its original size again.

25
5.4 Function Diagrams with Centered Starting Point
The concept of ELOP II eliminates the need to subsequently insert
individual pages. The centered starting page can be expanded in any
direction without page limitations.
The position of a page is marked with coordinates. Columns are named
with capital letters and lines with numbers.

The first page is the page with the coordinate A/0. As soon as an element
is placed on this page, the page is activated.

Fig. 20 Page numbering in the function diagram

Active pages are highlighted. As soon as you place an element on an

adjacent page, this page is also activated and thereby highlighted. In this
way, the function diagram can be extended in any desired direction.
Note: If you plan to insert a page between existing pages, you can
move a page. To do this, select “Move page” from the menu
"Plug-Ins" in the context menu of the page.

26
The overview window shows a top view of the function diagram. You can
navigate between pages by clicking on one of the pages in the overview
window.

Fig. 21 Overview window

Note: With the item "Page list" of the "Plug-Ins" in the context menu
you can jump to particular pages.

5.4.1 Zoom

By using the buttons in the symbols bar you can enlarge

and reduce the view in the drawing area and in the overview window.

27
5.5 Create Logic
With these basic functions, you create a logic in the function diagram.

5.5.1 Organization of Variables

Variables are created in the variable declaration editor. The following types
of variables do exist:

Local Variables (VAR) are defined in a program, in a function or in a

function block and are available only in this POU. Local variables in a
program can be connected to hardware (e.g. DI or AI, see VARxx).

Interface Variables (VAR_INPUT, VAR_OUTPUT) can only be defined in

a function or in a function block. Interface variables are the direct
connection between the surrounding logic and the internal logic of the
function or function block. Each time a function or function block is invoked,
external values are transferred to the internal logic using VAR_INPUTs.
The results of the internal logic are written back to the calling POU using
VAR_OUTPUTs (Fig. 22, FBX).

Global Variables (VAR_GLOBAL) can only be defined in a program and

can be used in every function block (FB), where they have to be defined as
VAR_EXTERNAL with exactly the same variable name.

Example:
In Fig. 22 variable GE2 is created in function block FB Y and is also used
in function block FB X. Therefore, this variable has to be defined in both
function blocks as VAR_EXTERNAL.
Additionally variable GE2 must be defined as VAR_GLOBAL in the
program and can also be used there.

Note:
Global Variables may be connected to the hardware (e.g. DI, AI, DO, AO).
Input of initial-values for VAR_GLOBAL is possible only in the Program.
A printout of the cross-reference list, showing all uses of the VAR_GLOBAL
/ VAR_EXTERNAL, can be executed in the context menu of the resource.

28
 Program

HW VAR1 VAR5 HW
& >=1
HW GE1 GE2

VAR_GLOBAL

FB X

HW VAR11 VI1 VO1 VAR14 HW

S
&
HW VAR12 VI2 GE2 R

VAR_INPUT VAR_EXTERNAL VAR_OUTPUT

FB X

HW VAR21 VI1 S VO1 VAR24 HW

&
HW VAR22 VI2 GE2 R

VAR_INPUT VAR_EXTERNAL VAR_OUTPUT

FB Y

VAR IN Q GE2 GE2 HW

& TON
GE1 PT ET
VAR_GLOBAL

VAR_EXTERNAL

Fig. 22 Organizing variables

29
5.5.2 Drag & Drop of Variables
Variables are created in the variable declaration editor, where different
types of variables (local variables, input variables, output variables,
external variables) can be chosen. To use a variable in the logic, click on
the variable in the variable declaration editor and drag it to the desired
position in the drawing area. A value field with the variable name is
created. In the variable declaration editor, an icon in front of the variable
shows the use of the variable in the drawing area.

Fig. 23 Drag & Drop of variables in the drawing area

Note: You can also import variables from an external data source. For
information, see the online help.

30
5.5.3 Drag & Drop Function Blocks
To use a function block in the logic, select the function block from a library
in the structure window and drag it to the desired position in the drawing
area.

Fig. 24 Drag & Drop a POU in the drawing area

31
5.5.4 Connecting Elements
The elements placed in the drawing area can be connected to each other
by drawing segments between their nodes. The type of the line connection
is determined by the type of the source node. The two nodes must also be
of the same type.

Point to where the segment should start (output). Left-click on that position
and drag to the node the segment connects. When you release the mouse,
the auto-router draws the line segment.
You can also create segment nodes by connecting an existing segment to
another input or output.

Note: The segments are automatically routed by ELOP II, but can be
changed manually by dragging the segment with the SHIFT key
depressed.

Output

Inputs

Fig. 25 Dragging a line between nodes

32
5.6 Creating and Managing Documentation
ELOP II provides complete document management with revision service.

This enables you to create different revisions of documents.

In addition to a complete printout with an extensive revision service, the

document management also detects the changes made to individual pages
of your documents, so that you can only print out the changed pages.

Fig. 26 Document management

33
5.6.1 Templates for Printing Documents
DXF forms serve as the templates for printing documents. ELOP II contains
a standard set of forms for printing all objects.

Fig. 27 DXF form for the cover sheet

34
In the object properties, you can change the standard entries for the
templates and also for the individual fields in the DXF forms.

Fig. 28 Project definitions for printout

35
5.7 Offline Simulation of the Logic
The offline simulation gives you the possibly to examine function diagrams
for logical correctness on the PC, without using a Programmable Electronic
System (PES = PLC). To achieve this, the function diagrams of ELOP-II are
compiled and executed by the PC in a preselectable cycle time.

The offline simulation can only be started for program instances within a
resource. Therefore a task object has to be created and assigned to the
program instance in the resource.

The offline simulation animates the logic. With the help of online test fields
(OLT fields) you can display individual values anywhere in the function
diagram. In case of Boolean values, the lines are shown in red and blue
color.

Fig. 29 Offline simulation of a function diagram

36
6 Working with Resource Types

This chapter covers:

• Assignment of controller types and IO

• Code generation
• Program download to a controller
• Online test
• Hardware documentation
After the function diagram has been created and tested independent from
the hardware, assignment to a particular resource must be done.

According to IEC 61131-3, a resource is a system that runs a program and

serves the IO level.

You select the system type from a list of all available resources types.

37
6.1 Defining a Resource
In the context menu of a resource, select the controller type.

All controller types of the system families H11, H41/H51 and H41q/H51q
and also A1 are available. The assignment can be changed subsequently
with the menu item “Hardware change”.

Fig. 30 Selecting the resource type

Note: When entering a name for a resource, note that the maximum
length is eight characters with HIMA controllers!

38
6.2 Assigning a Program Type to a Resource
Before a resource can execute a program, a program type must be
assigned to the resource. In a dialog window select a program type from a
library.
For doing this, open the context menu of the resource and select the
program type in the “New” menu.

In the structure window the program type then appears as program

instance with the same name in the resource.

Fig. 31 Assign a program type to a resource

39
6.3 IO Assignment
To assign variables to IO modules, first the module types have to be
arranged in the cabinet assignment (context menu of the resource)
according to the hardware layout.

The modules and IO-racks are chosen from the lists on the bottom of the
dialog window (Fig. 32) and are dragged to the corresponding position in
the cabinet layout.

Fig. 32 Define IO assignment

40
After double clicking on a module icon in the cabinet layout, the dialog
window for assigning variables to IO channels opens.

Fig. 33 Assigning variables to IO channels

Only those variables can be selected, whose data type matches the
available IO channels.

The module F3236 shown in Fig. 33 is a 16-channel input module for

binary signals. The 16 input channels No. 01 … 16 with Data type “Digital”
are shown in the left list. The Boolean variables declared in the logic
(ANA_FM_IN1_E, ANA_FM_IN2_E etc.) appear in the right list.

Assignments are carried out by dragging variables from the right list into
the Tag name field of the left list.

41
6.4 Assigning System Variables
In addition to the variables assigned to IO modules, system variables with
status information such as “single channel operation” or “IO error” are
available in the central unit for evaluation in user-defined logic. The system
variables can also be transmitted to DCS systems (DCS = Data Control
System), alarm systems or other visualization systems.

The assignment of system variables to variables defined in the logic is

carried out with the variable declaration editor in the program instance.

Fig. 34 Assigning system variables

42
6.5 Code Generator
The code generator translates the graphical information of the logic into
code executable by the PES and generates an unambiguous code version.
The code generator is started from the context menu of a resource.

Fig. 35 Messages of the code generator

Code generator messages are displayed in a separate window and written

to the file RESOURCE.ERR, which is shown in the structure window below
the resource.

6.5.1 Code Comparator

The code comparator compares two compiled projects based on their code
versions, and displays the differences in form of a list. The result of the
code comparator passes a security check and allows later inspections for
software changes without carrying out complete functional tests.

43
6.6 Control Panel
Before the machine code compiled by the code generator can be
downloaded into the controller, the communication bus must be defined in
the configuration object of the structure window (also for point-to-point
connections). After that the communication bus between the PC and
resource must be assigned in the resource.

After the communication bus has

been assigned to the resource, the
control panel tab CP is added to the
registers in the structure window (Fig.
36).
Use the control panel to download
code into the controller and start
execution.
Additional tools such as “Status
display” and “Online change” allow for
requesting controller status
information or forcing inputs and
outputs.

Fig. 36 Control panel

44
6.6.1 Download/Reload
Use the button “Download/Reload” to download the compiled logic into the
controller.

A download has the following characteristics:

- A download has to be carried out to load program code into an
otherwise empty Central Unit.
- A download is necessary if major changes have been made to the
current application program.
- After initializing the download, a running controller will be stopped
and has to be cold started manually. All process data will be lost!

A reload has the following characteristics:

- A reload can be carried out if only minor changes to the loaded
application program are necessary.
- Changes to the application program can be made without stopping
the controller.
- The controller should be equipped with two Central Units. In this
case both Central Units will be loaded with the new program code
one after the other, which guarantees availability of the controller
during reload.
- The generation of reloadable code has to be permitted in the
properties of the resource under the tab Codegenerator.

45
In a dialog window you can specify additional settings for the download.

Fig. 37 Dialog window for download/reload

Fig. 38 Status of the data transfer during download

After the new program code has been downloaded successfully, the
controller – except of in case of a reload – must be restarted with the button
.
Attention: Contrary to a reload, a download results in a controller stop and
therefore a system stop! Downloads or reloads should only be
carried out by experienced and well-trained users.

46
6.7 Online Test
The online test (OLT) is an additional register in the structure window. In
contrast to the hardware-independent offline simulation (see chapter 5.7),
which only needs a Personal Computer for testing the logic, the online test
reads the actual values of the variables from the controller.

The online test uses the function diagram for displaying values and
statuses.

Fig. 39 Online test of a function

Note: An online test can only be performed if the code version of the
project loaded on the PC is identical with the code version in the
controller. If a project is lost on the PC due to a computer crash
etc. and no backup is available, online tests for this project are
no longer possible.
There is no way to upload a project from the PES back into the
PC!

47
6.8 Hardware Documentation
Select the documentation of the hardware from the respective resource.
You can export this documentation to a text file (ASCII format) and insert
this file into a document object.

Fig. 40 Documentation of the hardware

48
7 Exercises

7.1 Creating a Project

Step 1: Start ELOP II:

 Click on ELOP II in the Windows start menu and select

ELOP II.

Step 2: Create a new project:

 From the Project menu, select the option New or click on

the symbol in the symbols bar.

Step 3: Define the project path and name:

 In Fig. 41, left pane, select the directory where the new
project should be created, enter the name for the new
project in the Object name field and click OK.

Fig. 41 Create project

49
 The new project is displayed in the structure window. All
standard libraries are automatically included in the new
project.

 Click on the “+“ in front of the project name and open the
folder.

Step 4: Create a new library as the first element in the project. The
library will contain the function blocks created by the user:

 In the structure window, click on the project.

 Open the context menu with a right mouse click.

 Select New, Library.

Fig. 42 Create library

A new library with the name “NewLib“ is added to the project.

50
Step 5: Change the name of the library “NewLib“ to “Prog_Library“:

 In the structure window, click on “NewLib”.

 Open the context menu of the library “NewLib”.

 Select Rename and change the name to “Prog_Library“.

Fig. 43 Renaming a library

51
Step 6: Within the library “Prog_Library”, create your own function
blocks:

 Click on “Prog_Library”.

 Open the context menu.

 In the menu New, select Program Type.

Fig. 44 Create program type

 Click on the “+“ in front of the library.

A new function block Program Type is added to the

structure.
Note: The program type contains the logic to be executed
in the controller and can contain other function
blocks.

52
 Repeat Step 6 and create a Function Block Type.

 Rename the program type and the function block type as

described in Step 5.

The project structure looks like this after the

above six steps:

User library
Anwenderbibliothek

Function block objects

(POUs)

Fig. 45 Project structure after this exercise

53
7.2 Creating a Function Block
 Open the function block from Fig. 45 by double clicking on
the symbol:

The FBD editor opens.

7.2.1 Variable Declaration

Step 1: In the variable declaration editor select the variable type:

 Click on the register with the required variable type.

Select VAR_INPUT (see Fig. 46).

Fig. 46 Variable declaration editor

Note: For functions or function blocks, VAR_INPUT and
VAR_OUTPUT are used as input and output
variables for the parent POU.

54
Step 2: Enter a variable:

 Open the variable declaration dialog by double clicking in

a free area in the variables declaration editor.

 In the variable declaration overwrite the default “I1“ in the

Name field with “Variable1”.

 In the Declaration field, select the data type “BOOL“.

 Define the Position of the variable (“2” in Fig. 47) at the

building block.
In the example in Fig. 47 “Variable1“ is defined as
VAR_Input on the left hand side in the second position.

Fig. 47 Declaration of a variable

55
  In the field Long name enter a meaningful description for
“Variable1“. The long name helps to explain the use of the
variable.

 Add your input to the list of variables list by pressing the

Add button.

The dialog window remains open until you close it.

Note: VAR_INPUT and VAR_OUTPUT variable appear in the
position defined in the interface declaration.

Fig. 48 Interface declaration

56
7.2.2 Function Block Layout
Step 1: Define the properties of the function block using the interface
declaration:

 Open the context menu of the function block and select

Properties.

Fig. 49 Context menu of the POU

57
Step 2: Enter a POU name:

 In the Module text field enter a name for the POU. If

necessary, a new font can be specified with the Edit
font … button.

The module text appears in the center of the POU (see

Fig. 52).

Fig. 50 Entering the POU name

Note: The module text is used to describe the

functionality of the POU, e.g. “2-out-of-3”.

58
Step 3: Define an instance name:

 Select the register Instance name.

 In the Instance name field enter a name and activate the

Display checkbox.

 If necessary, specify a new font and correct the

Alignment.

The instance name appears on the upper left side of the

POU (see Fig. 52).

Fig. 51 Entering and formatting the instance name

Note: The instance name is used to define the use of a

POU in a project, e.g. “2-out-of-3 temperature
monitoring”.

59
Step 4: Change the POU size:

 Position the cursor over the bottom right corner of the

POU, press the left mouse button and change the size of
the POU according to your requirements.

Fig. 52 Changing POU size

60
7.2.3 Develop Logic in the Drawing Area
Step 1: Use drag & drop to place logic elements from the libraries in
the drawing area:

 In the structure window, click on the “+“ symbol to open

the library StandardLibs.

 In the StandardLibs, open the library IEC1131-3 and

there Functions, Bitstr.

 Click on the AND function and drag the object out of the
structure window into the drawing area.
A preview of the object is displayed while dragging.

 After you release the mouse button, the object is placed at

the cursor position.

Fig. 53 POU drag & drop

Note: The procedure for adding standard objects from
libraries to a logic also applies to user-defined
objects.

61
Step 2: Complete the page data:

Since placing the AND object is the first change to the

contents of this page, (also see Chapter 5.4 for details), the
dialog window “Edit Page Data“ opens automatically.

In the field Long Name enter a meaningful description for the

page.

Fig. 54 Editing page data

62
Step 3: Complete the logic with additional building blocks:

 Insert additional objects from the libraries into the drawing

area as described in Step 1.

 Duplicate identical objects by keeping the Ctrl key

pressed while dragging an already existing object to
another position in the drawing area.

Fig. 55 Copy object

Note: Objects cannot be positioned on top of each other.
In this case, ELOP II aborts copying followed by an
signal.

Step 4: Switch on the grid and zoom in:

 Switch on the grid with the right-most button in the

symbols bar.

 Zoom into the screen section you want to enlarge.

Fig. 56 Buttons for zoom and grid

Note: The buttons on the right side refer to the drawing
area of the open object.

63
Step 5: Add variables to your logic:
Note: Variables are moved into the drawing area with drag & drop.
 In the variables list, click on a variable name and drag the
variable into the value field area (light gray shaded
margins on the left and right side of a page) or to a
position in the drawing area. A preview of the value field is
shown while dragging.

After the variable has been dropped, the variable name

appears in the value field.

Fig. 57 Drag & drop variables

Note: You cannot drop variables on top of other objects

in the drawing area.

64
Step 6: Draw segments between the variables (value fields) and
function blocks.

 Position the cursor above the node where you want to

start the segment (variable output).

 Press the left mouse button and draw a segment to the

node where you want the segment to end. Release the
mouse button.

The result is an automatically routed connection between

the two nodes.

Fig. 58 Draw segments

Note: The color of a segment depends on the data type

(BOOL, Integer, Real etc.).
You cannot connect nodes of different data types!

65
7.3 Creating a Program
 Open the program object by double clicking on the icon.

The FBD editor opens.

7.3.1 Variable Declaration

The procedure for declaring variables is identical to the declaration of
function blocks (see Chapter 7.2.1).
Note: VAR and VAR_GLOBAL are used for POUs of the type
Program.

7.3.2 Develop Logic in the Drawing Area

The procedure for creating program type logic is identical to the
development of function block logic. Please see chapter 7.2.3 for details.

66
7.4 Creating Configuration and Resource
Step 1: Create a configuration. The configuration will incorporate the
resource(s):

 Click on the project in the structure window.

 Open the context.

 Select New, Configuration.

Fig. 59 Create a new configuration

Step 2: Rename the new configuration:

 In the structure window, click twice slowly on the

configuration name.

An input field opens and the name can be changed.

67
Step 3: Create a new resource within the configuration:

 In the structure window, click on the configuration.

 Open the context menu.

 Select New, Resource.

Fig. 60 Create a resource

Note: If you rename the resource, note that the resource

name must not be longer than eight characters!

68
Step 4: Assign a program to the resource:

 In the structure window, click on the resource.

 Open the context menu.

 Select New, Program instance...

Fig. 61 Create a new program instance

69
Step 5: Select the program type that is to be processed in the
resource:

 Choose your program.

Within the resource a program instance is created, which

is the reference to the program type in the Prog_Library.

Fig. 62 Assign a program type

70
The project structure looks like this after the five steps:

User library

Function object

Program type

Program instance

Fig. 63 Project structure

Note: The program instance in the resource is only a reference to

which program from the Prog_Library is run on the controller.
The program type in the user library contains only the logic and
the variables.
Hardware depending settings (resource type) must be made in
the program instance, for example IO addresses or bus
addresses.

71
7.5 Offline Simulation of a Logic
Step 1: Create a task for the simulation on the PC:

 In the structure window, click on the resource.

 Open the context menu of the resource.

 Select New, Task.

Fig. 64 Create a new task

72
Step 2: Assign a task to a program instance:

 In the structure window, click on the program instance.

 Open the context menu of the program instance.

 Select Properties.

Fig. 65 Invoking properties of the program instance

73
  In the window “Properties: Program“, click on the Browse
button of the Task Assignment.

Fig. 66 Task assignment

 Select the task created in Step 1.

Fig. 67 Select task

Note: The task controls the simulated execution of the
program instance on the PC. The task has no effect
on the program instance in the PLC.

74
Step 3: Enter the offline simulation:

 Click on the resource.

 Open the context menu of the resource.

 Select OFF-LINE-Simulation.

Fig. 68 Open the OFF-LINE-Simulation

Note: A new register OLS (Offline Simulation) opens in the

structure window.

75
Step 4: Start the OFF-LINE-Simulation:

 Click on the Cold boot button (with blue triangle).

The status changes from “Stopped” to “Running” after the

start.

Fig. 69 Start the offline simulation

76
Step 5: Open function blocks in the offline simulation:

 Open a function block by double clicking on an object in

the structure window.

Fig. 70 Offline simulation of a program

Note: You can open several function blocks at the same time and
trace the signals between the function blocks.
It is also possible to open function blocks by double-clicking on
a function block in the logic.

77
Step 6: Change the state of the signals and test the logic:

Change signal state with an online test field (OLT

field):
 Click inside a value field and keep the mouse button
pressed.

 Drag the cursor out of the value field and drop the OLT
field that follows the cursor at a free location.

 Relocate the OLT field if necessary.

 Change the signal state by double clicking in the OLT

field.

Fig. 71 Create an OLT field

Note: After having inserted OLT fields, the question

“Save change?” appears when closing the
function block in the drawing area.
If you click Yes, the OLT fields will be saved. In
case of No, the OLT fields you have created are
rejected.

78
 Change signal state directly in the value field:
 Position the cursor over the value field whose value you
want to change.

 Press and hold the ALT key. The signal state is displayed
in the value field instead of the signal name.

 Change the signal state by clicking in the value field.

 Release the ALT key. The signal name is displayed again.

Fig. 72 Change the value field with the ALT key

Note: You can only change values which are not created by the
logic.

Step 7: Close the offline simulation:

 Click on the Close OLS button in the symbols bar.

Fig. 73 Close the offline simulation

79
7.6 PLC Cabinet Layout and Variable Assignment
Step 1: Assign the resource type (RT):

 Click on the resource in the structure window.

 Open the context menu of the resource.

 Click on RT assignment , and select the type of HIMA

PLC you have.

Fig. 74 Assigning a resource type

80
Step 2: Open the cabinet layout:

 Open the context menu of the resource.

 Select Edit cabinet layout.

Fig. 75 Edit cabinet layout

In the window “Edit cabinet layout” an empty cabinet of the

selected HIMA PLC is shown (see Fig. 76).

81
Step 3: Define the racks of your cabinet (H51 in our example):

 Select the register Racks from the tabs on the bottom of

the window.

 Drag a rack from the list into the cabinet and drop it at
where you want the rack to be inserted.

Fig. 76 Defining racks

Note: The rack position must correspond with the rack
address set in the hardware.

82
Step 4: Furnish a rack with IO modules:

 “Insert” modules into the rack by dragging and dropping

components from the Module register on the bottom of the
page to the required positions in the rack.

Fig. 77 Insert modules

The module icons have the following meanings:

Yellow IO icon ⇒ safety-related

Grey IO icon ⇒ not safety-related
Blue IO icon ⇒ for explosion hazardous areas

Arrow to the icon ⇒ Input module

Arrow from the icon ⇒ Output module

Examples: ⇒ digital IO module

⇒ analog IO module

83
Step 5: Open the IO module assignment:

 Double-click on a module icon (F 3236 in our example) to

open the “Edit Tag name“ window.

Fig. 78 Module assignment

84
Step 6: Assign variables to the inputs and outputs of an IO module:
Note: Fig. 79, left, shows the 16 digital input channels of the F 3236
module. Fig. 79, right, lists all variables whose data type
(BOOL) matches the channels of the F 3236 module and
which have not been assigned to an IO channel yet.
 Click on a name in the variable list, drag the variable into
the IO channel list and drop it on an IO channel.

Assigned variables are displayed in the IO channel list at

their channel and are removed from the variable list.

Fig. 79 Assign variables to IO channels

Note: A variable can only be assigned to one IO channel

Step 7: Close the windows with OK.

85
7.7 Running a Program on a PLC

7.7.1 Compile Program

Before the logic, created by the user, can run on a controller, the
logic must be converted into code executable by the CPU:

Step 1: Start the Code generator.

 Click on the resource.
 Open the context menu of the resource.
 Select Codegenerator.

Fig. 80 Start the Codegenerator

Step 2: Confirm the start of the code generators:

Fig. 81 Confirm start

86
The code generator reports the progress of the compilation in its own
window.

Fig. 82 Messages of the code generator

After the code generation has been successfully accomplished, additional

elements appear in the structure window. These are:

• NAME.VGL File for the comparison

• NAME.COD Code file with compiled logic
• NAME.ERR File with error messages

Note: If errors occurred during code generation, more detailed

information can be called up via the Error state viewer .

87
7.7.2 Communication between PC and Controller
Note: Before communication can be established, a definition of the
bus connection and the bus settings between the PC and the
controller are necessary.

Step 1: Open the properties of the configuration:

 Click on the Configuration in the structure window.

 Open the context menu of the configuration.

 Select Properties.

Fig. 83 Open the configuration properties

88
Step 2: Add a new bus:

 In the window “Properties: Configuration“, select the

register Buses.

 Click on the Add button to define a new bus.

 In the dialog window, “Add communication system“ enter a

name for the new bus in the Name field.

 Ensure that the bus Type is set to HIBUS.

 Press OK to add your entry.

Fig. 84 Adding a bus

89
Step 3: Add a resource to the list of bus stations:

 In the list in Fig. 84, mark the newly created bus and click
on Edit.

 The window “Edit HIBUS – Bus name“ opens. Select the

register Station.

 Click on Add to define a new bus station.

 In the window “HIBUS station – Bus name“ (see Fig. 85),

select the resource (controller) with which you want to
communicate from the drop-down list Name.

Fig. 85 Add a resource to the list of bus stations

 Define the Bus Subscriber Number (BSN) in accordance

with the setting on the central module of the controller.

 Under Type select "Slave" for a resource.

90
Step 4: Add a PC to the list of bus stations:

 In the window “Edit HIBUS – Bus name“ click on Add to

define a new bus station.

 In the window “HIBUS station – Bus name“, enter the

name of the PC that is connected to the resource in the
Name field. The name can be chosen freely.

 Define the Bus Subscriber Number (BSN) for the PC. “31”
is normally used.
Important: The BSN of the PC must not collide with a BSN
of a controller.

 Under Type select "PADT (PC)" for the PC.

Fig. 86 Add a PC to the list of bus stations

Note: According to in IEC 61131-3 the PC with the user

software is generally called "Programming and
Debugging Tool", or PADT for short.

91
Step 5: Define the bus parameters:

 In the “Edit HIBUS – Bus name“ window, select the

register Parameter to define the Baud rate, the number of
Stop bits and the Parity of the serial bus.
Note: The settings must correspond with the settings
of the controller.
 Save all your bus settings with OK.

Fig. 87 Define the bus parameter

Note: The parameters set for the bus are used for communication by
the PC. The baud rate for the interface of the controller can
also be changed by switches on the central module.

92
Step 6: Open the properties of the resource:

 Click on the resource in the structure window.

 Open the context of the resource.

 Select Properties.

Fig. 88 Open the resource properties

93
Step 7: Register PADT (PC)

 In the window “Properties: Resource”, open the register

PADT (PC).

 In the Bus field, select your bus from the list of the
configured buses.

 In the PADT (PC) field, select your PC from the list of

configured PADTs on the bus.

 Under PC interface select the serial port which connects

to the controller.

Fig. 89 Register PADT (PC) of the resource properties

94
7.7.3 Download and Start
When the communication bus has been defined, the controller can be
loaded and operated via the bus.

Step 1: Open the control panel:

 Click on the resource.

 Open the context menu of the resource.

 Select Control panel.

Fig. 90 Start the control panel

Note: You can leave the control panel open for further actions.
Simply select the register CP in the structure window.

95
Step 2: Start the download procedure:

 In the control panel, click on the button

Download/Reload.

 In the window “Download/Reload“, click on OK to start the

download.

The download progress is shown in the window “Data

transfer”.

Fig. 91 Start download

Note: A download must only be carried out by trained personnel and
with the permission of the person responsible for the facility,
because a download causes a shutdown.

96
Step 3: Start the controller:

 In the control panel, click on the Start button.

 For a new project select Cold start as start mode.

Fig. 92 Cold start of the controller

 After you pressed OK, a safety query makes sure that the
controller is not started inadvertently. The change in the
controller status (STOP -> RUN) is displayed in a separate
window.

Fig. 93 Start the controller

97
 The status of the controller is displayed in the control panel
and the icon of the start button revolves to show that the
controller is running.

Fig. 94 Control panel after controller start

98
7.8 Online Test
Note: Only if the code version of the user program in the controller is
identical to the code version of the project on the PC, the Online
Test can be started.

Step 1: Open the online test:

 Click on the resource.

 Open the context menu of the resource.

 Select ONLINE-Test.

Fig. 95 Invoke the Online Test

99
 Another register OLT (Online-Test) opens in the structure
window.

Below the button bar, all function blocks of the project are
listed.

 In the list, double-click on the function block you want to

test online.

Fig. 96 Online test in the structure window

100
Step 2: Open the function blocks in the OLT mode:

Fig. 97 Online Test of a program

Step 3: Close the online test:

 Click on the Close button.

Fig. 98 Close the online test

Note: The online test must be closed before modifications can be
made to the logic!

101
7.9 Forcing Inputs and Outputs
Step 1: Open the control panel:

 Click on the resource.

 Open the context menu of the resource.

 Select Control panel.

Fig. 99 Opening the control panel

102
Step 2: Check force switch settings:

 In the control panel, click on the Force switch button.

Fig. 100 Check force switch settings

103
 The “Force switch” window shows the status of the Master
force switch and the number of Activated force switches,
separately for inputs and outputs.

 Activate the Set checkboxes for both the inputs and

outputs (see figure below).

Fig. 101 Activate force switch

Step 3: Start the online as described in Chapter 7.8.

104
Step 4: Create an online test field:
Note: Also see Chapter 7.5, Step 6.
 Click inside the value.

 Drag and drop the OLT field at the position you want the
OLT field to reside.

Step 5: Change and activate the force value.

The OLT field is divided into three sections:

1. Display of the single switch and the state of the main

switch.

2. Display of the current signal state of the input or output.

3. Force value display.

1 2 3

Fig. 102 OLT field of a Boolean variable

 Change the force value and the force switch by double

clicking in the respective section of the OLT field.

The force switch and force value changes directly in the

controller. If the master force switch has not yet been set,
ELOP II asks whether the master force switch should be
set (see figure below).

105
 Fig. 103 Check back to set master force

Note: It is recommended not to set the master force switch via an OLT
field, otherwise an already set single switch could become
active inadvertently.

Possible states of the OLT field:

Single Master Force

force force Cur. value Output
value
switch switch
Not Not active FALSE TRUE Current
active value
Active Not active FALSE TRUE Current
value
Not Active FALSE TRUE Current
active value

Active Active FALSE TRUE Force

value

Active Active TRUE TRUE Force

value

Note: If OLT fields have been added to the logic and you close the
function block, you are asked whether you want to save the
changes for future use. Saving OLT fields does not affect the
code version of the project.

106
Note: If an input variable is forced, the forced value is used
everywhere in the logic.
If an output variable is forced, only the physical output is forced.
If the output variable is used in the logic, the value of the
variable is not changed by the forcing command, but still
contains the process value.

107
7.10 Documentation
A printout of the logic can be structured and organized in a document
object. All POUs are printed out with the documentation object. The
hardware is documented separately, but can be inserted into the document
object as a file.

Step 1: Create a new document object:

 Click on the project.

 Open the context menu of the project.

 Select New, Documents.

Fig. 104 Create a document object

108
Step 2: Rename the new document object:

 Slowly click twice on the name you want to change. An

input field opens and you can enter a new name.

Fig. 105 Rename document object

Step 3: Put all data of your project into the document object:

 Open the document object by double clicking on the

object.

 Click on your project name and hold down the mouse

button.

 Drag the project onto the document object.

The document object now shows all elements of your

project.
Note: You can also add single objects from your project to the
documentation by dragging and dropping only one object.

109
 Fig. 106 Add a project to the documentation

Step 4: Update the table of contents:

 Click on the Update TOC button.

Fig. 107 Update the table of contents

110
 After updating the table of contents, the pages are listed with
their pagination.

The sections in the document object correspond to the project

folder and the library folders with the indents reflecting the
hierarchy in the structure window.

Note: You can change the order of the elements or delete individual
elements. Don’t forget to update the table of contents!

Step 5: Print out the documentation:

 Start the printout for all, modified or selected pages via the
context menu or with the buttons in the symbol bar.

Fig. 108 Start printout

111
Step 6: Open the resource documentation:
Note: The resource documentation contains all hardware-related
data.
 Click on the resource.

 Open the context menu of the resource.

 Select Documentation, RES-DOCU (generated).

Fig. 109 Open the resource documentation

112
Step 7: Start the printout of the resource documentation:

 In the “RES docu generated …” window, select the

register Rack.

 Click on the Print button.

Fig. 110 Resource documentation

Note: You can also export the resource documentation to a file (in the
project path) and include it in the document object.
Attention: All folders will be exported or printed!

113
7.11 Backup a Project

7.11.1 Archiving
Step 1: Archive the project:

 Click on the project.

 Open the context menu of the project.

 Select Backup…

Fig. 111 Archiving a project

114
Step 2: Enter the path of the archive.

 In the “Backup“ window (Fig. 112) specify the path where

the project should be archived. In the field Target-file
enter the directory or press the Browse… button to select
a directory (Fig. 113).

 In the field Description enter a description for the project.

 Click on the Backup button.

The project is archived in the specified directory and now

carries the extension ".L3P“. The backup consists of three
files (Fig. 114).

Fig. 112 Define the archive name

Fig. 113 Browse for the target path

115
 Fig. 114 Archived project

7.11.2 Restore a Project

Note: To be able to restore a project from an archive, no other
project may be opened in ELOP II.

Step 1: Close open projects.

Fig. 115 Close project

Step 2: Start restoration of a project:

Fig. 116 Restore Project

116
Step 3: Select the project to be restored:

 In the “Restore” window (Fig. 117) specify the Target-

directory where you want to restore the project.
Use the Browse… button to select an already existing
directory.

Fig. 117 Restore archive

Fig. 118 Select Target-directory

117
  In the “Restore” window (Fig. 117) specify the Archive-
name and path of the project you want to restore.
Use the Browse… button to select an archive with the
mouse.

Fig. 119 Select archive

After the project has been successfully restored, it is

automatically opened and shown in the structure window.

Fig. 120 Restored project

Note: You may also archive individual objects of a project and

restore them in other projects.

118
8 Appendix
8.1 Index
.COD ...........................................................................................................88
.ERR............................................................................................................88
.L3P ...........................................................................................................116
.VGL ............................................................................................................88
Administrator
~ rights .......................................................................................................3
Adobe Acrobat Reader...............................................................................5
Archiving....................................................................................................115
Backup ......................................................................................................115
Baud rate.....................................................................................................93
Bitstr ............................................................................................................62
Boolean .......................................................................................................36
Bus
~ parameters ...........................................................................................93
~ station number......................................................................................91
~ type .......................................................................................................90
add ~........................................................................................................90
add ~ user................................................................................................91
Cabinet layout .............................................................................................82
Central unit ..................................................................................................42
Code comparator ........................................................................................43
Code generator .....................................................................................43, 87
~ messages .............................................................................................88
Code version .........................................................................43, 47, 100, 107
Cold start .....................................................................................................98
Communication ...........................................................................................89
~ bus ........................................................................................................44
Add ~ system...........................................................................................90
Computer hardware ......................................................................................4
Configuration .........................................................................................19, 22
new ~ .......................................................................................................68
Connecting elements ..................................................................................32
Context menu ..............................................................................................12
Control Center ...........................................................................................5, 7
Control panel .........................................................................................44, 96
Coordinates .................................................................................................26
columns ...................................................................................................26

119
 lines .........................................................................................................26
Copy object .................................................................................................64
Create logic ...........................................................................................28, 62
Data type ...............................................................................................41, 86
Document editor ..........................................................................................14
Document management..............................................................................33
Document object
Rename ~ ..............................................................................................110
Documentation ..............................................................................14, 20, 109
Add project ............................................................................................111
creating~..................................................................................................33
Hardware ~ ..............................................................................................48
new ~ object ..........................................................................................109
Resource ~ ............................................................................................113
Dongle ...........................................................................................................1
Download ........................................................................................45, 96, 97
Drag & Drop
~ Function Blocks ....................................................................................31
~ variables .........................................................................................30, 65
Draw segments ...........................................................................................66
Drawing area .........................................................................................23, 30
Duplicate .....................................................................................................64
DXF .............................................................................................................34
Edit page data .............................................................................................63
Error message.............................................................................................15
Error state viewer ..............................................................................8, 15, 24
Exercises.....................................................................................................50
Forcing ......................................................................................................103
Force switch settings .............................................................................104
Force value ............................................................................................106
Input variable .........................................................................................108
Master force...........................................................................................105
Output variable ......................................................................................108
Single switch..........................................................................................105
Function.......................................................................................................18
Function block .............................................................................................18
~ type .......................................................................................................54
create a ~.................................................................................................55
Function Block Diagram editor ..............................................8, 10, 13, 23, 24
Grid..............................................................................................................64
Hardlock ................................................................................................1, 3, 4
~ Driver ......................................................................................................3

120
Hardware change........................................................................................38
HIBUS .........................................................................................................90
Installation .................................................................................................3, 5
De~ ............................................................................................................6
multiple ~ ...................................................................................................4
Network ~ ..................................................................................................6
Instance name.............................................................................................60
Interface declaration....................................................................................58
~ editor...............................................................................................13, 23
IO assignment .............................................................................................40
Library .............................................................................................17, 22, 31
new ~ .......................................................................................................51
rename ~ .................................................................................................52
Long name ..................................................................................................57
Menu bar ...................................................................................................8, 9
Modules.......................................................................................................40
~ assignment ...........................................................................................85
analog IO ~ ..............................................................................................84
digital IO ~ ...............................................................................................84
insert ~.....................................................................................................84
Move page...................................................................................................26
Network drive ................................................................................................4
Object ............................................................................................................9
Offline simulation.............................................................................19, 36, 73
start ~.......................................................................................................77
Online Help............................................................................................15, 30
Online test
~ field ...............................................................................................79, 106
Online test (OLT).........................................................................47, 100, 101
Overview window ..................................................................................13, 23
PADT (PC) ............................................................................................92, 95
Page numbering..........................................................................................26
Parity ...........................................................................................................93
PFR ...............................................................................................................2
Plug-Ins .......................................................................................................26
POU
~ name.....................................................................................................59
~ size .......................................................................................................61
Printer............................................................................................................4
Program
~ instance ....................................................................... 17, 19, 36, 39, 72
new ~ ...................................................................................................70

121
 ~ type .................................................................................................17, 39
assign ~................................................................................................71
new ~ ...................................................................................................53
compile a ~ ..............................................................................................87
create a ~.................................................................................................67
Program Organization Unit (POU) ..............................................................17
Programming and Debugging Tool .............................................................92
Project .........................................................................................9, 11, 17, 22
~ folder.....................................................................................................21
~ management.............................................................................5, 7, 8, 21
~ path.......................................................................................................50
~ root .......................................................................................................20
~ template................................................................................................21
create a ~.................................................................................................50
Quick-Info ....................................................................................................10
Rack ............................................................................................................83
Reload ...................................................................................................45, 97
Resource ...............................................................................................19, 22
~ type .......................................................................................................37
assigning a ~........................................................................................81
defining a ~ ..............................................................................................38
new ~ .......................................................................................................69
rename ~ .................................................................................................69
Restore......................................................................................................117
Revision management ..........................................................................14, 20
Sequence Function Chart language ...........................................................13
Shutdown ....................................................................................................97
Slave ...........................................................................................................91
Standard screen............................................................................................8
StandardLibs .........................................................................................22, 62
Start menu.................................................................................................5, 7
Starting ELOP II ............................................................................................7
Status bar ................................................................................................8, 10
Stop bits ......................................................................................................93
Structure window...............................................................................8, 11, 22
Objects in the ~........................................................................................17
Symbols bar ............................................................................................8, 10
Target file ..................................................................................................116
Task.......................................................................................................19, 36
assign ~ ...................................................................................................75
new ~ .......................................................................................................73
Technical Support .........................................................................................2

122
Templates....................................................................................................35
Title bar .....................................................................................................8, 9
Value field..............................................................................................30, 80
~ area ......................................................................................................65
Variable
~ declaration ............................................................................................55
~ editor .....................................................................................13, 23, 55
~ list .........................................................................................................65
add ~........................................................................................................65
Assign System ~......................................................................................42
external ~.................................................................................................18
Local ........................................................................................................28
system ~ ..................................................................................................19
VAR_External ..........................................................................................28
VAR_Global .............................................................................................28
VAR_Input .........................................................................................28, 57
VAR_Output ......................................................................................28, 57
Working area ...............................................................................8, 13, 23, 24
Zoom ...........................................................................................................27

123
124
8.2 List of abbreviations
BSN Bus Subscriber Number

CB Coprocessor module

CFG Configuration (bus documentation)

CG Code Generator

CONST Constant

CRC Cyclic redundancy check

CRF Cross reference (Info on inputs and outputs)

CSV Data format for import / export function, ASCII format with
comma separated value

CU Central Unit
DXF Standard-AutoCAD graphic format for printing copy

IO Input / output

FB Function block

FBD Function Block Diagram

FUN Function type object

GV Global variable

HIPRO-N / S Hibus communication not safety-related / safety-related

HW Hardware

LgP Logic plan - controlled protocolling

OLS Offline simulation

OLT Online Test

125
PADT Programming and debugging Tool (PC)

PES Programmable Electronic System

PFR Product Feedback Report

POU Program Organization Unit (object)

RES Resource

RETAIN Retention performance

RT Resource Type

RWP Read / write parameter

126
HIMA Paul Hildebrandt GmbH + Co KG
Industrie-Automatisierung