IEC61131-3标准：工业控制系统编程语言详解

5星 · 超过95%的资源需积分: 32 92 浏览量更新于2024-07-26 收藏 2.7MB PDF 举报

IEC61131-3标准详解 IEC61131-3标准是国际电工委员会（IEC）制定的工业控制系统编程语言标准，于2003年发布。该标准提供了详细的工业控制系统编程语言规范，旨在统一工业控制系统的编程语言，提高工业控制系统的可靠性、安全性和可维护性。 IEC61131-3标准的主要内容包括： 1. 编程语言规范：IEC61131-3标准定义了工业控制系统的编程语言规范，包括变量、数据类型、运算符、控制结构、函数等方面的规范。 2. 编程语言的基本概念：该标准介绍了编程语言的基本概念，如变量、数据类型、数组、结构体等。 3. 编程语言的控制结构：IEC61131-3标准规定了编程语言的控制结构，如顺序结构、选择结构、循环结构等。 4. 编程语言的函数：该标准定义了编程语言的函数，包括函数的定义、函数的调用、函数的参数传递等。 5. 编程语言的错误处理：IEC61131-3标准规定了编程语言的错误处理机制，如错误类型、错误处理机制等。 IEC61131-3标准的应用： 1. 工业控制系统：IEC61131-3标准广泛应用于工业控制系统，包括PLC、DCS、SCADA等。 2. 自动化系统：该标准也应用于自动化系统，如机器人、自动化生产线等。 3. 工业自动化：IEC61131-3标准在工业自动化领域具有重要意义，能够提高工业自动化系统的可靠性、安全性和可维护性。 IEC61131-3标准的特点： 1. 统一性：IEC61131-3标准统一了工业控制系统的编程语言，提高了工业控制系统的可靠性和可维护性。 2. 可扩展性：该标准具有良好的可扩展性，能够满足不同工业控制系统的需求。 3. 互操作性：IEC61131-3标准保证了不同厂商的工业控制系统之间的互操作性。 IEC61131-3标准的版本历史： 1. 2003年版：该标准的首个版本，提供了详细的工业控制系统编程语言规范。 2. 2013年版：该标准的更新版本，新增了新的编程语言特性和功能。 IEC61131-3标准是工业控制系统编程语言的国际标准，提供了详细的工业控制系统编程语言规范，旨在统一工业控制系统的编程语言，提高工业控制系统的可靠性、安全性和可维护性。

– 14 – 61131-3  IEC:2003(E)

1.4 Overview and general requirements

This part of IEC 61131 specifies the syntax and semantics of a unified suite of programming

languages for programmable controllers (PCs). These consist of two textual languages, IL (Instruction

List) and ST (Structured Text), and two graphical languages, LD (Ladder Diagram) and FBD (Function

Block Diagram).

Sequential Function Chart (SFC) elements are defined for structuring the internal organization of

programmable controller programs and function blocks. Also, configuration elements are defined

which support the installation of programmable controller programs into programmable controller

systems.

In addition, features are defined which facilitate communication among programmable controllers and

other components of automated systems.

The programming language elements defined in this part may be used in an interactive programming

environment. The specification of such environments is beyond the scope of this standard; however,

such an environment shall be capable of producing textual or graphic program documentation in the

formats specified in this standard.

The material in this part is arranged in “bottom-up” fashion, that is, simpler language elements are

presented first, in order to minimize forward references in the text. The remainder of this subclause

provides an overview of the material presented in this part and incorporates some general

requirements.

1.4.1 Software model

The basic high-level language elements and their interrelationships are illustrated in figure 1. These

consist of elements which are programmed using the languages defined in this standard, that is,

programs and function blocks; and configuration elements, namely, configurations, resources, tasks,

global variables, access paths, and instance-specific initializations, which support the installation of

programmable controller programs into programmable controller systems.

Provided by IHS under license with IEC

Not for Resale

No reproduction or networking permitted without license from IHS

--``````-`-`,,`,,`,`,,`---

61131-3  IEC:2003(E) – 15 –

CONFIGURATION

RESOURCE

TASK TASK

PROGRAM

FB FB

RESOURCE

TASK TASK

PROGRAM

FB FB

GLOBAL and DIRECTLY REPRESENTED VARIABLES

and INSTANCE-SPECIFIC INITIALIZATIONS

ACCESS PATHS

Execution control path

Variable access paths

Function block

Variable

Communication function (See IEC 61131-5)

NOTE 1 This figure is illustrative only. The graphical representation is not normative.

NOTE 2 In a configuration with a single resource, the resource need not be explicitly

represented.

Figure 1 - Software model

A configuration is the language element which corresponds to a programmable controller system as

defined in IEC 61131-1. A resource corresponds to a “signal processing function” and its “man-

machine interface” and “sensor and actuator interface” functions (if any) as defined in IEC 61131-1. A

configuration contains one or more resources, each of which contains one or more programs executed

under the control of zero or more tasks. A program may contain zero or more function blocks or other

language elements as defined in this part.

Configurations and resources can be started and stopped via the “operator interface”, “programming,

testing, and monitoring”, or “operating system” functions defined in IEC 61131-1. The starting of a

configuration shall cause the initialization of its global variables according to the rules given in 2.4.2,

followed by the starting of all the resources in the configuration. The starting of a resource shall cause

the initialization of all the variables in the resource, followed by the enabling of all the tasks in the

resource. The stopping of a resource shall cause the disabling of all its tasks, while the stopping of a

configuration shall cause the stopping of all its resources. Mechanisms for the control of tasks are

defined in 2.7.2, while mechanisms for the starting and stopping of configurations and resources via

communication functions are defined in IEC 61131-5.

IEC 2468/02

Provided by IHS under license with IEC

Not for Resale

No reproduction or networking permitted without license from IHS

--``````-`-`,,`,,`,`,,`---

– 16 – 61131-3  IEC:2003(E)

Programs, resources, global variables, access paths (and their corresponding access privileges), and

configurations can be loaded or deleted by the “communication function” defined in IEC 61131-1. The

loading or deletion of a configuration or resource shall be equivalent to the loading or deletion of all the

elements it contains.

Access paths and their corresponding access privileges are defined in 2.7.1.

The mapping of the language elements defined in this subclause on to communication objects is

defined in IEC 61131-5.

1.4.2 Communication model

Figure 2 illustrates the ways that values of variables can be communicated among software elements.

As shown in figure 2 a), variable values within a program can be communicated directly by connection

of the output of one program element to the input of another. This connection is shown explicitly in

graphical languages and implicitly in textual languages.

Variable values can be communicated between programs in the same configuration via global

variables such as the variable x illustrated in figure 2 b). These variables shall be declared as GLOBAL

in the configuration, and as EXTERNAL in the programs, as specified in 2.4.3.

As illustrated in figure 2 c), the values of variables can be communicated between different parts of a

program, between programs in the same or different configurations, or between a programmable

controller program and a non-programmable controller system, using the communication function

blocks defined in IEC 61131-5 and described in 2.5.2.3.5. In addition, programmable controllers or

non-programmable controller systems can transfer data which is made available by access paths, as

illustrated in figure 2 d), using the mechanisms defined in IEC 61131-5.

PROGRAM A

FB_X

FB1

FB_Y

FB2

Figure 2 a) - Data flow connection within a program

PROGRAM A

FB_X

FB1

PROGRAM B

FB_Y

FB2

VAR_GLOBAL

x: BOOL;

END_VAR

VAR_EXTERNAL

x: BOOL;

END_VAR

VAR_EXTERNAL

x: BOOL;

END_VAR

CONFIGURATION C

Figure 2 b) - Communication via GLOBAL variables

IEC 2469/02

IEC 2470/02

Provided by IHS under license with IEC

Not for Resale

No reproduction or networking permitted without license from IHS

--``````-`-`,,`,,`,`,,`---

– 18 – 61131-3  IEC:2003(E)

1.4.3 Programming model

The elements of programmable controller programming languages, and the subclauses in which they

appear in this part, are classified as follows:

Data types (2.3)

Variables (2.4)

Program organization units (2.5)

Functions (2.5.1)

Function blocks (2.5.2)

Programs (2.5.3)

Sequential Function Chart (SFC) elements (2.6)

Configuration elements (2.7)

Global variables (2.7.1)

Resources (2.7.1)

Access paths (2.7.1)

Tasks (2.7.2)

As shown in figure 3, the combination of these elements shall obey the following rules:

1) Derived

data types shall be declared as specified in 2.3.3, using the standard data types specified

in 2.3.1 and 2.3.2 and any previously derived data types.

2) Derived

functions can be declared as specified in 2.5.1.3, using standard or derived data types,

the standard functions defined in 2.5.1.5, and any previously derived functions. This declaration

shall use the mechanisms defined for the IL, ST, LD or FBD language.

3) Derived

function blocks can be declared as specified in 2.5.2.2, using standard or derived data

types and functions, the standard function blocks defined in 2.5.2.3, and any previously derived

function blocks. This declaration shall use the mechanisms defined for the IL, ST, LD, or FBD

language, and can include Sequential Function Chart (SFC) elements as defined in 2.6.

4) A

program shall be declared as specified in 2.5.3, using standard or derived data types, functions,

and function blocks. This declaration shall use the mechanisms defined for the IL, ST, LD, or FBD

language, and can include Sequential Function Chart (SFC) elements as defined in 2.6.

Programs can be combined into configurations using the elements defined in 2.7, that is, global

variables, resources, tasks,

and access paths.

Reference to “previously derived” data types, functions, and function blocks in the above rules is

intended to imply that once such a derived element has been declared, its definition is available, for

example, in a “library” of derived elements, for use in further derivations. Therefore, the declaration of

a derived element type shall not be contained within the declaration of another derived element type.

A programming language other than one of those defined in this standard may be used in the

declaration of a

function or function block. The means by which a user program written in one of the

languages defined in this standard invokes the execution of, and accesses the data associated with,

such a derived function or function block shall be as defined in this standard.

Provided by IHS under license with IEC

Not for Resale

No reproduction or networking permitted without license from IHS

--``````-`-`,,`,,`,`,,`---

剩余225页未读，继续阅读

yz_wang2002

粉丝: 2
资源: 21

IEC61131-3标准：工业控制系统编程语言详解

可编程语言标准IEC61131-3中文版.pdf

IEC61131-3.pdf

中文IEC61131-3_Programming_Industrial_Automation_Systems

iec61131-3标准

基于IEC 61131-3标准的控制系统及应用

IEC 61131-3标准与ARM嵌入式控制系统.doc

探索IEC 61131-3标准的2013年版

IEC61131-3标准与PLC编程语言简介

IEC61131-3标准与PLC编程语言解析

西门子PLC编程语言解析：IEC61131-3标准

最新资源