Difference between revisions of "PLCopen Model (IEC61131-3)"

From UaCapabilities
Jump to: navigation, search
(Created page with "==Introduction== {{uacap:PLCopen Intro}} == PLCopen Capabilities == __NOEDITSECTION__ {{uaCollapsible|PLCopen Information Model|{{uacap:PLCopen InfoModel}}|}} {{uaCollapsibl...")
 
(PLCopen Capabilities)
 
(4 intermediate revisions by the same user not shown)
Line 1: Line 1:
 
==Introduction==
 
==Introduction==
{{uacap:PLCopen Intro}}
+
IEC 61131 is a standard for programmable controllers. IEC 61131-3 focusses on programming languages for industrial automation. With its worldwide support, it is independent of any single company.
 +
The PLCopen OPC UA Information Model maps the IEC 61131-3 software model to an OPC UA information model. This mapping assures that an IEC 61131-3 control program on different control platforms from different control suppliers is represented the same way. A visualization program used for different controllers running the same control program must only be configured once.
 +
The PLCopen OPC UA Information Model is based on OPC UA for Devices (DI).
 +
PLCopen also defines Function Blocks to use OPC-UA client functionality in an IEC61131-3 controller. With these Function Blocks a controller can exchange complex data structures horizontally with other controllers independently from fieldbus system or vertically with OPC-UA interfaces in an MES/ERP system in order to collect data or write new production orders to the cloud. It allows a production line to be independently active in combination with integrated OPC UA Security features.
 +
OPC-UA client functionality in a controller does not provide hard deterministic real time and so it’s not a deterministic fieldbus – but UA provides fast, secured communication providing modelling mechanism for information models.
  
 
== PLCopen Capabilities ==
 
== PLCopen Capabilities ==
__NOEDITSECTION__
+
===PLC Information Model===
{{uaCollapsible|PLCopen Information Model|{{uacap:PLCopen InfoModel}}|}}
+
{{CapabilityUri|/PLCopen_Model_(IEC61131-3)#PLC_Information_Model}}
 +
{{Acronym|PLC}}
 +
'''Description'''
 +
<br>The controller supports the PLCopen OPC UA information model.
  
{{uaCollapsible|PLCopen Functionblocks|{{uacap:PLCopen FBs}}|}}
+
'''Usage Considerations'''
 +
<br>OPC UA servers which represent their underlying manufacturer specific controllers in a similar, IEC 61131-3 based manner provide a substantial advantage for client applications as e.g. visualizations or MES.
 +
 
 +
{{uaConformance|TBD <!-- Client -->|
 +
TBD <!-- Server -->
 +
<!-- Example
 +
* [http://opcfoundation.org/UA-Profile/Server/GlobalCertificateManagement '''Global Certificate Management Server Profile''']
 +
* [http://opcfoundation.org/UA-Profile/Client/GlobalCertificateManagement '''Global Certificate Management Client Profile''']
 +
-->
 +
}}
 +
 
 +
===Function Blocks===
 +
{{CapabilityUri|/PLCopen_Model_(IEC61131-3)#Function_Blocks}}
 +
{{Acronym|PLC}}
 +
'''Description'''
 +
<br>The controller supports the PLCopen OPC UA function blocks.
 +
 
 +
'''Usage Considerations'''
 +
<br>Fieldbus-independent communication between controllers or controllers and field devices that support OPC UA.
 +
<br>Vertical communication from controller with applications in MES or ERP level.
 +
 
 +
{{uaConformance|TBD <!-- Client -->|
 +
TBD <!-- Server -->
 +
<!-- Example
 +
* [http://opcfoundation.org/UA-Profile/Server/GlobalCertificateManagement '''Global Certificate Management Server Profile''']
 +
* [http://opcfoundation.org/UA-Profile/Client/GlobalCertificateManagement '''Global Certificate Management Client Profile''']
 +
-->
 +
}}

Latest revision as of 20:14, 30 March 2015

Introduction

IEC 61131 is a standard for programmable controllers. IEC 61131-3 focusses on programming languages for industrial automation. With its worldwide support, it is independent of any single company. The PLCopen OPC UA Information Model maps the IEC 61131-3 software model to an OPC UA information model. This mapping assures that an IEC 61131-3 control program on different control platforms from different control suppliers is represented the same way. A visualization program used for different controllers running the same control program must only be configured once. The PLCopen OPC UA Information Model is based on OPC UA for Devices (DI). PLCopen also defines Function Blocks to use OPC-UA client functionality in an IEC61131-3 controller. With these Function Blocks a controller can exchange complex data structures horizontally with other controllers independently from fieldbus system or vertically with OPC-UA interfaces in an MES/ERP system in order to collect data or write new production orders to the cloud. It allows a production line to be independently active in combination with integrated OPC UA Security features. OPC-UA client functionality in a controller does not provide hard deterministic real time and so it’s not a deterministic fieldbus – but UA provides fast, secured communication providing modelling mechanism for information models.

PLCopen Capabilities

PLC Information Model

URN:          https://opcfoundation.org/wiki/index.php/PLCopen_Model_(IEC61131-3)#PLC_Information_Model

Discovery ID: PLC


Description
The controller supports the PLCopen OPC UA information model.

Usage Considerations
OPC UA servers which represent their underlying manufacturer specific controllers in a similar, IEC 61131-3 based manner provide a substantial advantage for client applications as e.g. visualizations or MES.


Conformance Testing

Client Server

TBD

TBD

Function Blocks

URN:          https://opcfoundation.org/wiki/index.php/PLCopen_Model_(IEC61131-3)#Function_Blocks

Discovery ID: PLC


Description
The controller supports the PLCopen OPC UA function blocks.

Usage Considerations
Fieldbus-independent communication between controllers or controllers and field devices that support OPC UA.
Vertical communication from controller with applications in MES or ERP level.


Conformance Testing

Client Server

TBD

TBD