Satec Expertmeter PM180 User manual

expertmeter™
High Performance Analyzer
PM180
SATEC PM180 PLC Configurator
Reference Guide
BG0611 REV.A1

2
Every effort has been made to ensure that the material herein is complete and accurate.
However, the manufacturer is not responsible for any mistakes in printing or faulty
instructions contained in this book. Notification of any errors or misprints will be received
with appreciation.
For further information regarding a particular installation, operation or maintenance of
equipment, contact the manufacturer or your local representative or distributor.
REVISION HISTORY
A1
Jan 2018
Initial release
All trademarks are property of their respective owners
February 2018
Copyright 2017-2018 SATEC Ltd.

3
Table of Contents
1GENERAL...........................................................................................................5
2IEC61131 IMPLEMENTATION...........................................................................6
2.1 Limitations..............................................................................................................................6
2.2 Data types..............................................................................................................................6
2.3 Built-in functions ....................................................................................................................7
2.3.1 AND ...................................................................................................................7
2.3.2 OR .....................................................................................................................7
2.3.3 NOT ...................................................................................................................7
2.3.4 GE......................................................................................................................8
2.3.5 EQ......................................................................................................................8
2.3.6 LE8
2.3.7 GE_THRESHOLD ..................................................................................................8
2.3.8 LE_THRESHOLD ...................................................................................................8
2.3.9 TON ...................................................................................................................9
2.3.10 TOF .............................................................................................................9
2.4 Function block .......................................................................................................................9
2.5 Implemented languages........................................................................................................9
2.5.1 Functional block diagram .................................................................................... 10
2.5.2 Ladder diagram.................................................................................................. 10
3PROGRAMMING GUIDE..................................................................................13
3.1 Getting started.....................................................................................................................13
3.2 Creating project ...................................................................................................................13
3.3 Adding devices ....................................................................................................................15
3.4 Device properties.................................................................................................................16
3.5 Main function block..............................................................................................................17
3.6 Adding function blocks.........................................................................................................17
3.7 Setting function blocks.........................................................................................................18
3.7.1 Rename FB........................................................................................................ 18
3.7.2 Add variables..................................................................................................... 19
3.7.3 Variable properties ............................................................................................. 19
3.7.4 Add work area ................................................................................................... 23
3.7.5 Debug FB .......................................................................................................... 23
3.7.6 Delete FB .......................................................................................................... 24
3.8 Communication with the device...........................................................................................24
3.8.1 Interfaces ......................................................................................................... 24
3.8.2 Upload configuration to the device ....................................................................... 26
3.8.3 Download configuration from the device................................................................ 29
3.9 Functional block diagrams...................................................................................................32
3.9.1 Open workspace ................................................................................................ 32
3.9.2 Add or delete variables ....................................................................................... 33
3.9.3 Variable properties ............................................................................................. 34
3.9.4 Add built-in components ..................................................................................... 34
3.9.5 Making connections ............................................................................................ 35
3.9.6 Making time delays ............................................................................................ 37
3.9.7 Programming limits for set point variables............................................................. 38
3.10 Ladder diagrams..................................................................................................................41
3.10.1 Add ladder diagram ..................................................................................... 41
3.10.2 Rails .......................................................................................................... 42
3.10.3 Contact ...................................................................................................... 42
3.10.4 Negated contact .......................................................................................... 42
3.10.5 Coil............................................................................................................ 43
3.10.6 Negated coil................................................................................................ 43

4
3.10.7 Creating LD ................................................................................................ 43
3.10.8 Transformation LD into setpoints ................................................................... 47
3.11 Using PLC Configurator with PAS.......................................................................................47
4TROUBLESHOOTING......................................................................................49
4.1 Address in not set................................................................................................................49
4.2 Connection error..................................................................................................................49
4.3 No MAIN module .................................................................................................................50
4.4 Unconnected inputs.............................................................................................................51

5
1General
This document specifies a subset of the IEC 61131 standard,
particularly part 3 that deals with the languages used to program
controllers. The document provides complete information necessary to
use SATEC PM180 PLC Configurator (hereinafter referred to as PLC
Configurator) in order to program the PM180 device using Functional
block diagrams (FBD) and Ladder diagrams (LD) and to communicate
with the device. Refer to the PM180 Installation Manual and PM180
Operation Manual for more information on communication connections
and configuring communication parameters in your device.

6
2IEC61131 Implementation
IEC61131 is the standard relating to programmable controllers. Part 3
of this standard deals with the languages used for programming these
devices and is commonly referred as IEC61131-3. SATEC PM180 PLC
Configurator implements IEC61131-3 in order to create logic for PM180
devices.
IEC 61131-3 support is limited so that programmable controller system
configuration could be compiled to PM180 Setpoints.
2.1 Limitations
Limitations of IEC 61131-3 support are the following:
Programmable controller system configuration is limited to one task
executed at 20ms interval (PM180 hardware limitation). Any
program organization unit could be attached to this task.
Special (nonstandard) *_THRESHOLD functions are used to model
analogue values comparison functions of PM180 Setpoints.
2.2 Data types
Data types implemented in PLC Configurator are listed in the table
below.
Data type
Description
BOOL
Bit string of 1 bit. Logical state, values are FALSE and TRUE.
LREAL
Long real value (64 bit) ±10±308,
values are from +/-4.19E-307 to +/-1.67E+308.
TIME
Time duration in milliseconds,
values are from -T#24d20h31m23s648ms to
+T#24d20h31m23s647ms
DATE
Date format, values are from D#1-1-1 to D#65000-12-31,
Gregorian
For the PM180 device refers to the Packed date data type.
TOD
Time of Day format, values are from TOD#00:00:00.000 to
TOD#23:59:59.999
For the PM180 device refers to the Packed time data type.
DT
Date Time format combines DATE and TOD.
For the PM180 device refers to the Timestamp data type.
DP
Double point value. There are four possible values:
intermediate state (IS)
off state (OFF)
on state (ON)
bad state (BS)

7
2.3 Built-in functions
Functions are a type of Program Organization Unit. They are small
reusable units that form the fundamental building blocks of complex
industrial control programs. The implementation contains several built-
in functions that are supported by PM180 devices. They are listed in the
table below.
Function
abbreviation
Function name
Inputs
data
type
Outputs
data type
Logical operations
AND
AND
ANY_BIT
ANY_BIT
OR
OR
ANY_BIT
ANY_BIT
NOT
NOT
ANY_BIT
ANY_BIT
GE_THRESHOLD
Greater or equal with threshold
LREAL
BOOL
LE_THRESHOLD
Less or equal with threshold
LREAL
BOOL
GE
Greater or equal
ANY
BOOL
EQ
Equal
ANY
BOOL
LE
Less or equal
ANY
BOOL
Time delays
TON
Timer ON
BOOL,
Time
BOOL
TOF
Timer OFF
BOOL,
Time
BOOL
2.3.1 AND
AND function returns result of all inputs using logical conjunction.
Number of inputs is not limited.
AND function is shown in the figure below.
Figure 1 - AND
2.3.2 OR
OR function returns result of all inputs using logical disjunction. Number
of inputs is not limited.
OR function is shown in the figure below.
Figure 2 - OR
2.3.3 NOT
NOT function returns result of one input using logical inversion.
NOT function is shown in the figure below.

8
Figure 3 - NOT
2.3.4 GE
GE function returns TRUE if input IN1 greater or equal to IN2.
GE function is shown in the figure below.
Figure 4 - GE
2.3.5 EQ
EQ function returns TRUE if input IN1 equal to IN2.
EQ function is shown in the figure below.
Figure 5 - EQ
2.3.6 LE
LE function returns TRUE if input IN1 less or equal to IN2.
LE function is shown in the figure below.
Figure 6 - LE
2.3.7 GE_THRESHOLD
GE_THRESHOLD function returns TRUE if input IN greater or equal to
OPERATE and returns FALSE if input IN less or equal to RELEASE.
In this function IN is a value input, OPERATE and RELEASE are inputs to
set threshold. Usually to set threshold locale variables are used.
GE_THRESHOLD function is shown in the figure below.
Figure 7 - GE_THRESHOLD
2.3.8 LE_THRESHOLD
LE_THRESHOLD function returns TRUE if input IN less or equal to
OPERATE and returns FALSE if input IN greater or equal to RELEASE.
In this function IN is a value input, OPERATE and RELEASE are inputs to
set threshold. Usually to set threshold locale variables are used.

9
LE_THRESHOLD function is shown in the figure below.
Figure 8 - LE_THRESHOLD
2.3.9 TON
TON function is used for making time delays.
TON function returns TRUE if input IN changes from FALSE to TRUE with
the delay set via input PT.
In this function IN is control input (BOOL), input PT is used for setting
time delay in milliseconds.
TON function is shown in the figure below.
Figure 9 - TON
2.3.10 TOF
TOF function is used for making time delays.
TOF function returns FALSE if input IN changes from TRUE to FALSE
with the delay set via input PT.
In this function IN is control input (BOOL), input PT is used for setting
time delay in milliseconds.
TOF function is shown in the figure below.
Figure 10 - TOF
2.4 Function block
Function Block (FB) is a type of Program Organization Unit. It has set of
input variables and output variables. Each block has an algorithm,
which enables evaluation of all its inputs and produces set of output
values. Unlike functions, function blocks also have temporary variables,
which store intermediate values during its evaluation. The execution of
a function block can also depend on its own output in a previous
instance of execution.
Function block can include build-in functions.
2.5 Implemented languages
There are two graphical languages implemented in PLC Configurator:
Function Block Diagram (FBD).
Ladder Diagram (LD).

10
2.5.1 Functional block diagram
Function Block Diagram (FBD) is a programming language defined in
IEC61131-3. FBD is a graphical representation of an Industrial
programmed control system and adopts a set of symbols and
conventions defined in IEC-1131-3. It represents a control system in
terms of signal flow between processing elements similar to the
methodology adopted for signal flow in electronic circuits. By using
interconnected graphical blocks, it expresses the behavior of functions,
function blocks and a composite program.
An example of FBD is shown in the figure below.
Figure 11 –FBD
You can find detailed information about creating FBD in PLC
Configurator in chapter 3.9.
2.5.2 Ladder diagram
Ladder Diagram (LD) is a programming language defined in IEC61131-
3. Ladder diagrams are derived from electrical circuit diagrams, which
have been conventionally used to represent relay logic operations. Many
of the symbols and terminology have also been adopted from the circuit
diagrams. In other words, Ladder Diagrams are graphical
representations of Boolean expressions, but they can also include other
information normally not possible with Boolean expressions.
A ladder diagram has two vertical power rails, one on the left and
another on the right side of the diagram. The left vertical rail carries the
power to the coil (notionally) through the contacts. The contacts are
arranged along horizontal 'rungs' and the power flows through these
rungs to energize the coil, which is on the right hand side of the logic
diagram, when the logic condition represented by the contacts is TRUE

11
(AND logic). Alternative paths can be present with other contacts in
them (in parallel), which can be used to build OR logic.
An example of ladder diagram is shown in the figure below.
Figure 12 - LD
Basic concepts of LD implemented in PLC Configurator are the following:
There are two rails: left rail (so called “+” rail) and right rail (so
called “-” rail).
Between rails can be contacts and one coil. They are situated along
horizontal so called “rung”.
Contacts represent BOOL input variables, whereas coils represent
BOOL output variables.
There are two types of contacts and coils: normally closed and
normally opened.
Serial connection of contacts is used to create AND logic.
Parallel connection of contacts is used to create OR logic.
If all the contacts on the way from the left rail to a coil are closed,
the coil is energized and its state is TRUE.
Coils can have their own contacts like shown in the figure below.

12
Figure 13 –Coil’s contact
To create more complex logic it is possible to add built-in functions
and variables of other from BOOL data types.
Figure 14 - Using TON function in LD
You can find detailed information about creating LD in PLC Configurator
in chapter 3.10.

13
3Programming guide
3.1 Getting started
Before starting PLC Configurator, be sure you have installed Java 8 64
bit on Windows 7 and above (64 bit versions only).
To start PLC Configurator:
1. Unzip the archive with the application in any folder.
2. Run file “bin/scadastudio.exe”.
3.2 Creating project
To create new project:
1. Start PLC Configurator application.
2. In the application, choose File -> New Project, like shown in the
figure below.
Figure 15 - File menu
3. In the New Project wizard, expand the SATEC category and select
SATEC PLC Project like shown in the figure below. Then click Next.

14
Figure 16 - Project choosing
4. In the Name and Location page of the wizard, do the following (like
shown in the figure below):
In the Project Name field type project name.
To setup project location click on Browse... button or type it in
the Project location field.
Figure 17 - Name and Location
5. Click Finish.
After that the project will be created and opened in PLC Configurator.
You should see the following components:

15
Figure 18 - Created project
3.3 Adding devices
To add new devices do following:
1. Click the right mouse button on the existing project.
Figure 19 - Add device menu
2. Select Device and Language in the “Add a new device” window and
click Ok.
Choose the type of diagram you want to use (Language):

16
FBD (Function Block Diagram).
LD (Ladder Diagram).
Figure 20 - Device properties
After that you will see a newly created device in the project tree.
Figure 21 - Created device in the project
3.4 Device properties
To open device properties double-click on a device in the project tree.
The properties will appear in the middle of the screen:
Figure 22 - Device properties
You can set the following settings:
1. “Release coefficient in comparison operations” –for details see
3.9.7.

17
2. “Settings range for the logic generator” – here you can set the
range of set points that will be used on the PM180 device, during
automatic logic generation. For detailed information see 3.11.
3.5 Main function block
A newly created device contains one function block named MAIN.
Figure 23 - Main function block
Main function block must be in every device. This block is sent to the
device when you use function “Send configuration to the device” (see
3.8.2). If you don’t have main function block in your device you will get
an error (see 4.3).
Note that if you add new function blocks to the device (see 3.6) you
have to use them in the Main function block otherwise that logic will be
ignored during uploading procedure.
3.6 Adding function blocks
To add additional function (FB) block do the following:
1. Click the right mouse button on the section “Programmable logic”
of the device and choose “New function block”.
Figure 24 - Add new function block
2. A new block named “POU” will appear in the project tree.

18
3.7 Setting function blocks
3.7.1 Rename FB
To rename FB click the right mouse button on FB in the project tree and
choose “Rename”.
Figure 25 - Rename FB
Type the new name in appeared window like shown in the figure below
and click OK.
Figure 26 - FB new name
In the following window confirm your action and click Ok.
The FB will be renamed.

19
3.7.2 Add variables
To add variables click the right mouse button on one of the following
sections depending on the type of variable you want to add:
1. Input variables.
2. Output variables.
3. Local variables.
Context menu will appear like shown in the figure below:
Figure 27 - Adding variables
In the menu choose the desired type of variable and click on it with the
left mouse button. A new variable will be added.
You can use the same input or local variable many times on the
same diagram. It can simplify visual perception of your project.
3.7.3 Variable properties
When you click on a variable in a FB tree its properties appear on the
right hand side of PLC Configurator (by default) like shown in the figure
below.

20
Figure 28 - Variable properties
You can set properties using Properties component.
There are following properties:
1. Name –name of a variable.
2. Type –type of a variable. Cannot be changed.
3. Initial value –a value that variable has before it is changed due to
signal flow.
4. Address –mapping variables to the PM180 internal variables such
as digital inputs, relay outputs, set points, etc. Local variables
don’t have such setting.
Please note that in order to operate on the PM180 device every
input and output variable of FB must be mapped to the device internal
variables otherwise you will get a message “Variable address is not set”
during uploading the configuration to the device.
Be advised that PLC Configurator automatically distributes set points
according to the device property “Settings range for the logic
generator”. To set this setting, see 3.4. We discourage you from
mapping output variables to set points, because PLC Configurator does
it automatically anyway. In case of manual mapping output variables to
set points you can get errors concerning execution sequence of function
blocks. In other words, logic that you made in PLC Configurator can be
executed in a different way on the device and the result that you get
will be different.
To set the address, click on icon in the Address setting. Depending
on the type of variable one of the following windows will appear: