An example of platform independence in UNICOS

control systems

Koutli MariaCERN

EN-ICE-PLC

07/02/14

2

Aims: IEC 61131-3 programmingReusable, interchangeable codePlatform independencyStandardization..

UNICOS-CPC

Choice: Platforms based on Codesys V3PLCOpen XML

Schneider SoMachineBeckhoff Twincat

3

Codesys: An IEC61131-3 development tool with a flexible runtimeMany PLC manufacturers use it to extend their device

specific software.The product is license free.Compilation produces native code supported by many

CPU families(ARM, Intel 80x86,Pentium).The runtime is ready to use on many operating

systems(Windows(XP/7/CE),LINUX (OSADL),VxWorks).PC based devices can be used as the PLC unit

(SoftPLC). It supports OOP and high-level languages as C/C++.

4

PLCOpen XML: An independent schemeA standard file exchange format between

different manufacturers for textual and graphical information.

Provides an XML scheme for free.Provides interfaces to other software tools, like

modelling tools.(e.g. Simulink PLC Coder).

5

A look to the past..

1st attempt of porting UNICOS CPC5 within CODESYS V2 environment.1st Implementation of CODESYS V3 to UNICOS CPC6

Two UAB plug-ins and a CPC library based on XML Codesys files.With target the Schneider Somachine platform.

6

A 2nd implementation, why?

Use of PLC Open XML standard for the UAB output files

CODESYS V3, Twincat 3 and Somachine 3*, support it. More easy to read and edit comparing to CODESYS files. Other suppliers apart from Codesys support it.

Enhancements, completion of the previous implementation.

Improve communication with WinCC OA via Modbus driver.

Testing(Automated test and real application).Baseline 1st release.

*only for importation of ST language

7

What do we have now?

Two UAB plug-insA Resource Package(Templates, Baseline)

For creating a UNICOSCPC6 application for

SoMachine 3 and Twincat 3.

8

UAB Plug-insThe previous two UAB plug-ins for Codesys were modified in order to generate PLCOpen XML output files. A third plug-in for generation of the WinCC OA database is shared with Schneider.

Inputs: Spec file + User Logic Templates

Outputs:From Instance plug-in:

Instance and Communication fileFrom Logic plug-in:

Logic and Topology file

There is also possibility to choose thedevelopment platform(Somachine or Twincat) and the PLC type(M258, EPC, IPC)in UAB Wizard.

9

Resource PackageBaseline

CPC Objects library. Communication library

Templates Common templates for all CPC objects except

of I/O objects. Two different templates for the topology. PLCOpen XML files for SFC are not supported

by SoMachine 3 for the moment.

10

Interesting features

CODESYS/SoMachine offer a demo version of SoftPLC on Windows where the PLC code can be tested.

Twincat 3 is integrated into Visual Studio 2010 and it has a C++ module.

Beckhoff IPC can reach cycle time of some μs.

11

A real CPC application(1)

A UNICOS application is used in our lab to prove the reusability of the code between different platforms, in our case Schneider SoMachine and Beckhoff Twincat.

The same User Logic Templates are used for both systems. Spec file is also the same(with small adjustments in the I/O object ranges).

Use of WinCC OA as SCADA for remote control.Use of local touch panels Schneider Magelis for local

control.Tested on three different PLCs(Schneider M258 and

Beckhoff CX5020 EPC and C6920 IPC)

12

A real CPC application(2)

Local touch panel

SCADA screenshot

Controlled hardware

The Control system

13

Applications on a conventional Windows PC(1)..

Twincat can run locally on Windows PC with Modbus connection to WinCC OA. It can communicate with I/Os through OPC Server, C++

module or EtherCAT. Example: EcoSim Pro Simulation can be used instead of

real hardware connected via OPC Server(but only under Windows XP).

14

Applications on a conventional Windows PC(2)..

CODESYS/Somachine can use a demo SoftPLC on Windows PC. For all applications which do not have hard real-time

constraints. Alternatively a real-time SoftPLC is offered, but, it’s not

license free and it’s aimed on controller manufacturers..

15

ConclusionsOne instance and one logic plug-in for

automatic generation of CPC code is serving both systems.

The library of CPC objects is the same for SoMachine, Twincat and Codesys platforms.

Hardware can still influence the development procedure mainly in terms of communication but....this was taken into account during the development so that the user can focus on programming regardless of the hardware platform.

Thank you very much for your

attention!

Merci beaucoup pour votre

attention!