CoDeSys 2.3 PLC编程用户手册详解

版权申诉

184 浏览量更新于2024-06-13 1 收藏 2.32MB PDF 举报

CoDeSys 2.3 用户手册是一份详尽的指南，用于PLC（可编程逻辑控制器）编程，由3S-SmartSoftwareSolutions GmbH 出版。该手册版权属于该公司，自1994年至2010年，强调了其对文档准确性和完整性所做的努力。尽管如此，鉴于文本完全无误并非易事，作者鼓励用户在发现任何错误或改进意见时积极提供。手册内容分为多个部分，旨在帮助用户深入了解CoDeSys的核心概念和功能。首先，第1章"CoDeSys简介"概述了CoDeSys的基本概念，包括： 1.1 **CoDeSys介绍**：CoDeSys是一个集成的平台，它结合了多种硬件平台和编程语言，使开发者能够使用统一的界面进行跨平台的PLC编程，简化了开发过程。 1.2 **CoDeSys功能概览**：这部分详细阐述了CoDeSys的功能特性，如支持不同类型的硬件设备、提供了高级编程工具、以及其在自动化控制中的广泛应用。 1.3 **用户文档概述**：手册的目标读者被引导了解如何有效地利用这份文档，包括章节结构、术语解释和资源查找路径，以便于理解和操作。接着是第2章"CoDeSys中的构成与语言"，深入讲解了项目组件和编程语言： 2.1 **项目组件**：介绍了CoDeSys项目的基本组成部分，如程序模块、数据对象、配置文件等，这些元素共同构建起一个完整的自动化解决方案。 2.2 **编程语言支持**： - **Instruction List (IL)**：这是CoDeSys的核心编程语言，它基于IEC 61131-3标准，允许用户编写结构化的梯形图、顺序功能图（SFC）、指令表（Ladder Logic）、功能块图（FB）、和结构文本（ST）等。此外，手册还涵盖了其他重要的主题，如安装和配置、错误处理、性能优化，以及与Microsoft Windows和IntelliSense等第三方工具的集成。最后一章更新日期为2010年10月28日，表明这是一份早期版本，但其核心内容对于理解和使用CoDeSys 2.3编程仍然具有很高的参考价值。通过阅读此手册，用户可以系统地学习和掌握如何在CoDeSys环境中进行高效、标准化的PLC编程，实现自动化控制系统的高效设计和实施。

Project Components...

2-4 CoDeSys V2.3

The declaration parts of function blocks and programs can contain instance declarations. Instance

declarations are not permitted in functions.

Access to a function block instance is limited to the POU in which it was declared unless it was

declared globally.

The instance name of a function block instance can be used as the input for a function or a function

block.

Note: All values are retained after processing a function block until the next it is processed. Therefore,

function block calls with the same arguments do not always return the same output values!

Note: If there at least one of the function block variables is a retain variable, the total instance is stored in

the retain area.

Calling a function block

The input and output variables of a function block can be accessed from another POU by setting up

an instance of the function block and specifying the desired variable using the following syntax:

Assigning parameters at call:

If you would like to set input and/or output parameters when you call the function block, you can do

this in the text languages IL and ST by assigning values to the parameters after the instance name of

the function block in parentheses (for input parameters this assignment takes place using ":=" just as

with the initialization of variables at the declaration position, for output parameters "=>" is to be used).

If the instance is inserted via input assistant (<F2>) with option With arguments in the

implementation window of a ST or IL POU, it will be displayed automatically according to this syntax

with all of its parameters. But you not necessarily must assign these parameters.

Example:

FBINST is a local variable of type of a function block, which contains the input variable xx and the

output variable yy. When FBINST is inserted in a ST program via input assistant, the call will be

displayed as follows: FBINST1(xx:= , yy=> );

InOutVariables at call:

Please regard, that the InOutVariables (VAR_IN_OUT) of a function block are handed over as

pointers. For this reason in a call of a function block no constants can be assigned to VAR_IN_OUTs

and there is no read or write access from outside to them.

Example

Calling a VAR_IN_OUT variable iInOut1 of function block fubo in a ST module:

VAR

fuboinst:fubo;

iVar1:int;

END_VAR

iVar1:=2;

fuboinst(iInOut1:=iVar1);

not allowed in this case: “fuboinst(iInOut1:=2);” or “fuboinst.iInOut1:=2;”

Examples for calling function block FUB:

Function block FUB, see above, chapter 'Function Block'

The multiplication result is saved in the variable ERG, and the result of the comparison is saved in

QUAD. An instance of FUB with the name INSTANCE is declared.

This is how the instance of a function block is called in IL :

Project Components...

2-6 CoDeSys V2.3

These changes therefore play a role only when the same instance is called.

Example of a program

A program declaration begins with the keyword PROGRAM and ends with END_PROGRAM. Regard

Appendix J: Appendix J: Recommendations on the naming.

If you would l

ike to set input and/or output parameters when you call the program, you can do this in

the text languages IL and ST by assigning values to the parameters after the program name in

parentheses (for input parameters this assignment takes place using ":=" just as with the initialization

of variables at the declaration position, for output parameters "=>" is to be used).

If the program is inserted via input assistant (<F2>) with option With arguments in the

implementation window of a ST or IL POU, it will be displayed automatically according to this syntax

with all of its parameters. But you not necessarily must assign these parameters.

Examples for program calls:

In IL:

CAL PRGexample2

LD PRGexample2.out_var

ST ERG

or with assigning the parameters (input assistant "With arguments", see above):

CAL PRGexample2(in_var:=33, out_var=>erg )

In ST:

PRGexample2;

Erg := PRGexample2.out_var;

or with assigning the parameters (input assistant "With arguments", see above):

PRGexample2(in_var:=33, out_var=>erg );

In FBD:

Example for a possible call sequence for PLC_PRG:

See the program PRGexample shown in the picture at top of this chapter:

LD 0

ST PRGexample.PAR (*Default setting for PAR is 0*)

CAL IL call (*ERG in IL call results in 1*)

CAL ST call (*ERG in ST call results in 2*)

CAL FBD call (*ERG in FBD call results in 3*)

If the variable PAR from the program PRGexample is initialized by a main program with 0, and then one after

the other programs are called with above named program calls, then the ERG result in the programs will have

the values 1, 2, and 3. If one exchanges the sequence of the calls, then the values of the given result

parameters also change in a corresponding fashion.

2 - What is What in CoDeSys

CoDeSys V2.3 2-7

PLC_PRG

The PLC_PRG is a special predefined POU. Each project must contain this special program. This

POU is called exactly once per control cycle.

The first time the 'Project' 'Object Add' command is used after a new project has been created, the

default entry in the POU dialog box will be a POU named PLC_PRG of the program type. You should

not change this default setting!

If tasks have been defined, then the project may not contain any PLC_PRG, since in this case the

procedure sequence depends upon the task assignment.

Attention: Do not delete or rename the POU PLC_PRG (assuming you are not using a Task Configuration)!

PLC_PRG is generally the main program in a single task program.

Action

Actions can be defined and assigned to function blocks and programmes ('Project' 'Add action'). The

action represents a further implementation which can be entirely created in another language as the

"normal" implementation. Each action is given a name.

An action works with the data from the function block or programme which it belongs to. The action

uses the same input/output variables and local variables as the "normal" implementation uses.

Example for an action of a function block

In the example given, calling up the function block Counter increases or decreases the output variable

"out", depending on the value of the input variable "in". Calling up the action Reset of the function

block sets the output variable to zero. The same variable "out" is written in both cases.

Calling an action:

An action is called up with <Program_name>.<Action_name> or <Instance_name>.<Action_name>.

Regard the notation in FBD (see example below) ! If it is required to call up the action within its own

block, one just uses the name of the action in the text editors and in the graphic form the function

block call up without instance information.

Examples for calls of the above described action from another POU:

Declaration for all examples:

PROGRAM PLC_PRG

VAR

Inst : Counter;

END_VAR

Call of action 'Reset' in another POU, which is programmed in IL:

CAL Inst.Reset(In := FALSE)

LD Inst.out

ST ERG

Project Components...

2-8 CoDeSys V2.3

Call of action 'Reset' in another POU, which is programmed in ST:

Inst.Reset(In := FALSE);

Erg := Inst.out;

Call of action 'Reset' in another POU, which is programmed in FBD:

Note: Actions play an important role in blocks in sequential function charts, see Sequential Function Chart.

The IEC standard does not recognise actions other than actions of the sequential function chart.

Resources

You need the resources for configuring and organizing your project and for tracing variable values:

Global Variables which can be used throughout the project or network

Library manager for adding libraries to the project

Log for recording the actions during an online session

Alarm Configuration for the configuration of the alarm handling in the project

PLC Configuration for configuring your hardware

Task Configuration for guiding your program through tasks

Watch- and Recipe Manager for displaying variable values and setting default variable values

Target Settings for selection and if necessary final configuration of the target system

Workspace as an image of the project options

Depending on the target system and on the target settings made in CoDeSys the following resources

also might be available in your project:

Sampling Trace for graphic display of variable values

Parameter Manager for data exchange with other controllers in a network

PLC-Browser as controller monitor

Tools – availability depending on target – for calling external tool programs from within CoDeSys

SoftMotion functionality (due to license) with CNC-Editor (CNC program list) and CAM-Editor

Libraries

You ca

n include in your project a series of libraries whose POUs, data types, and global variables you

can use just like user-defined variables. The libraries standard.lib and util.lib are standard parts of the

program and are always at your disposal. See chapter 6.4 'Library Manager'.

Data types

Along with th

e standard data types the user can define his own data types. Structures, enumeration

types and references can be created.

See Appendix C: 'Data Types'.

Visualization

CoD

eSys provides visualizations so that you can display your project variables. You can plot

geometric elements off-line with the help of the visualization. In Online mode, these can then change

their form/color/text output in response to specified variable values.

A visualization can be used as a pure operating interface for a PLC with CoDeSys HMI or as a Web-

Visualization or Target-Visualization running via Internet resp. directly on the PLC.

See for more details in the user manual for the CoDeSys Visualization.

剩余468页未读，继续阅读

wwwarewow

粉丝: 4645
资源: 2470

CoDeSys 2.3 PLC编程用户手册详解

最新资源