Scribd
Upload
35 views2 pages

General: Figure 1: The Triangle With User Options

PLC

Uploaded by

nantha74
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
35 views2 pages

General: Figure 1: The Triangle With User Options

PLC

Uploaded by

nantha74
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

1.

General
The motion control market displays a wide variety of incompatible systems and solutions. In businesses where
different
systems are used, this incompatibility induces considerable costs for the end-users, learning is confusing,
engineering
becomes difficult, and the process of market growth slows down.
Standardization would certainly reduce these negative factors. Standardization means not only the programming
languages
themselves, (as standardization is achieved using the worldwide IEC 61131-3 standard) but also standardizing
the interface towards different motion control solutions. In this way the programming of these motion control
solutions
is less hardware dependent. The reusability of the application software is increased, and the costs involved in
training
and support are reduced.
Users have requested that PLCopen helps to solve this problem, which initiated the Motion Control Task Force. This
Task Force has defined the programmers interface by standardizing the Function Blocks for Motion Control.
Figure 1: The triangle with user options
For the positioning of this activity, please check figure 1. This triangle has the following user options at its corners:
Performance
Functionality
Standardization.
In practice, users write their programs very closely coupled to the hardware with dedicated functions, in order to get
the
highest performance possible as dictated by their environment. This limits the user in his options with respect to the
target hardware and the reusability of the control software and raises the training investment.
The second user option enables a very broad range of software functionality to be offered. This can be very helpful
to
the user, but will seldom lead to high performance. Also the training costs are increased.
The third corner, standardization, is primarily focused on reusability across different systems from different
suppliers,
including integrated, distributed and networked systems, as well as reduction in training investments. Due to the
general
character of this definition, the performance on different architectures can be less optimal than hard coding. Due to
this,
standardization should not be expected to offer maximum performance but can closely approach maximum
functionality,
meaning that the bottom of the triangle is very short.
The first specification was released as an independent library of function blocks for motion control. It included
motion
functionality for single axes and multiple axes, several administrative tasks, as well as a state diagram. This
specification
provides the user with a standard command set and structure independent of the underlying architecture.
This structure can be used on many platforms and architectures. In this way one can decide which architecture will
be
used at a later stage of the development cycle. Advantages for the machine builder are, amongst others, lower costs
for
supporting the different platforms and the freedom to develop application software in a more independent way,
without
limiting the productivity of the machine. In addition to those benefits, system maintenance is easier and the
education
period is shorter. This is a major step forward, and is more and more accepted by users as well as suppliers.
With the release of part 1, it was understood that additional functionality was needed. Part 1 provides the basis for a
set

PLCopen
for efficiency in automation
TC2 Task Force Motion Control March 17, 2011 1999 - 2011 copyright by PLCopen
Function Blocks for Motion Control Version 2.0, Published page 9/ 141
of inter-related specifications:
Part 1 - PLCopen Function Blocks for Motion Control
Part 2 - PLCopen Motion Control - Extensions, which in the new release 2.0 is merged with Part 1
Part 3 - PLCopen Motion Control - User Guidelines
Part 4 - PLCopen Motion Control Coordinated Motion
Part 5 - PLCopen Motion Control - Homing Extensions
Part 6 - PLCopen Motion Control Fluid Power Extensions
With the release of the underlying document, Part 1 PLCopen Function Blocks for Motion Control version 2.0,
Part 2
PLCopen Motion Control Extensions has been integrated into the Basic document
The PLCopen Motion Control User Guidelines, Part 3, is an addition to the PLCopen Function Blocks for Motion
Control,
and should not be seen as stand alone document.

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy