How to verify compliance with PLCopen® codingguidelines with PLC Checker？ @

20

08

-20

17

Itri

s A

uto

mat

ion

Sq

uar

e SA

S

Team introduction

Karoline BeskeExport Director

karoline.beske@itris-automation.com

Marwen Saafi Technical Support

marwen.saafi@automationsquare.com

Robyn Buckland Marketing Director

robyn.buckland@automationsquare.com

Zhihang WangSales & Marketing Assistant

zhihang.wang@automationsquare.com

@2

00

8-2

01

7 It

ris

Au

tom

atio

n S

qu

are

SAS

Table of content

PLCopen®

coding guidelines

PLC Checker

@2

00

8-2

01

7 It

ris

Au

tom

atio

n S

qu

are

SAS

Itris Automation

PLCopen®

PLCopen®

Welcome

Mr. van der Wal

PLCopen® Managing Director

evdwal@plcopen.org

PLCopen® Association

@2

00

8-2

01

7 It

ris

Au

tom

atio

n S

qu

are

SAS

Business

Vendor and product independent worldwide association

Location

Headquarter: The Netherlands

Branches: China, Japan, USA and Korea

Mission

Be the leading association resolving

topics related to control programming

and to support the use of international

standards in this field.

PLCopen® Association

@2

00

8-2

01

7 It

ris

Au

tom

atio

n S

qu

are

SAS

Table of content

Itris Automation

PLCopen®

PLC Checker

@2

00

8-2

01

7 It

ris

Au

tom

atio

n S

qu

are

SAS

PLCopen®

coding guidelines

PLCopen® coding guidelines

@2

00

8-2

01

7 It

ris

Au

tom

atio

n S

qu

are

SAS

5 Categories

• Naming• Comment• Coding Practices• Languages• Vendor-Specific

3 levels of importance

• High• Medium• Low

23 team members from 12 companies

64 Rules

Good practice programming rules

5 References

• IEC 61131.3• IEC 61131.8• JSF++ coding standard• MISRA-C • Codesys On-line help

PLCopen® coding guidelines

@2

00

8-2

01

7 It

ris

Au

tom

atio

n S

qu

are

SAS

Purpose

• To introduce a coding standard for the Industrial Control Market

• To deal with the complexity of larger programs

• To increase efficiency in coding

• To support the program life cycle

Benefits

• Higher quality and efficiency

• Better maintainability

• Lower costs, especially over the life-cycle

PLCopen® coding guidelines

@2

00

8-2

01

7 It

ris

Au

tom

atio

n S

qu

are

SAS

Rules description format

Required

Identifier: reference number of the rule

Importance: the level of effect on the quality of the

application software (high, medium or low)

Targeted language: Language or languages the rule can be

applied.

References: when rules was found or inspired by a third

party document, the reference is given in this field

Description: a detailed description of the rule

Guidelines: explanation of how to deal with the rule

violation.

Reasoning: reasons why this rule is valuable

Optional

Exceptions: good reasons not to follow the rule in

certain cases

Example: an explanatory example to help

understanding of the rule

Don’t：example in red color to highlight bad coding

practice

Do：example in green color to highlight good coding

practice

Comments: extension of the rule description. To link

with other rules or subjects which may be out of the

scope of this document.

PLCopen® coding guidelines

@2

00

8-2

01

7 It

ris

Au

tom

atio

n S

qu

are

SAS

PLCopen® coding guidelines

@2

00

8-2

01

7 It

ris

Au

tom

atio

n S

qu

are

SAS

Why should we use PLCopen coding guidelines?

• The first general coding guidelines proposed for industrial control

• Help to enhance programming methods within automation industry

• Improve readability, efficiency, maintainability, reliability and security (IEC 25010)

• Ensure the consistency of the verification process

• A good starting point for companies to define their company-internal guidelines

• And it is open to the community - download from www.PLCopen.org

Table of content

PLCopen®

PLCopen®

coding guidelines

@2

00

8-2

01

7 It

ris

Au

tom

atio

n S

qu

are

SAS

PLC Checker

Itris Automation

Itris Automation

Business

Software engineering company

Provides PLC development tools

Location

Grenoble,

France

Our Mission

Optimizing development processes of PLC programs by

- Increasing productivity

- Improving program quality

- Reducing testing & commissioning time

@2

00

8-2

01

7 It

ris

Au

tom

atio

n S

qu

are

SAS

Table of content

Itris Automation

PLCopen®

PLCopen®

coding guidelines

@2

00

8-2

01

7 It

ris

Au

tom

atio

n S

qu

are

SAS

PLC Checker

@2

00

8-2

01

7 It

ris

Au

tom

atio

n S

qu

are

SAS

PLC Checker

Support of all 5 languages of

the IEC 61131

Support of major brands

and formats

Itris Technology

PLC

Checker

Rules

Verification

PLC Checker

PLC

Checker

Checker Ruleset

PLCprogramexport

Upload ResultsStatic analysis

@2

00

8-2

01

7 It

ris

Au

tom

atio

n S

qu

are

SAS

PLC Checker

Adaptation

@2

00

8-2

01

7 It

ris

Au

tom

atio

n S

qu

are

SAS

PLCopen

Ruleset

How are the PLCopen®

coding guidelines mapped

to the Checker ruleset?

PLC Checker

@2

00

8-2

01

7 It

ris

Au

tom

atio

n S

qu

are

SAS

Rules

Classification

In short term

In long term

Already Available

Automatable with

configuration

Cannot be

supported by PLC

Checker

Cannot be

supported by

automatic tools

Total Feasibility

Feasible Not feasible

88%

12%

Automatable

rules

Rules Automatable

with development

Not automatable

rules

PLC Checker

@2

00

8-2

01

7 It

ris

Au

tom

atio

n S

qu

are

SAS

Codes which violate the rules

Errors are made intentionally in the code and are manually tested

New automate tests are ran periodically and results are compared with the reference

Each rule is tested on PLC programs from different development environments

Keep the test results and the tested PLC program as references

Testing

PLC Checker

PLC

Checker

PLCprogramexport

Upload

ResultsFor PlCopen

Static analysis

@2

00

8-2

01

7 It

ris

Au

tom

atio

n S

qu

are

SAS

PLCopen

Ruleset

PLC Checker

@2

00

8-2

01

7 It

ris

Au

tom

atio

n S

qu

are

SAS

PLCopen

Ruleset

Checker Ruleset

How the PLCopen® coding guidelines are mapped to the Checker ruleset？

Examples

PLC Checker

How the PLCopen® coding guidelines are mapped to the Checker ruleset？

Examples

@2

00

8-2

01

7 It

ris

Au

tom

atio

n S

qu

are

SAS

PLC Checker

@2

00

8-2

01

7 It

ris

Au

tom

atio

n S

qu

are

SAS

PLC Checker – Demo

@2

00

8-2

01

7 It

ris

Au

tom

atio

n S

qu

are

SAS

Contact information

For further questions or information

www.itris-automation.com

+33 476 236 756

karoline.beske@itris-automation.com (Export Director)

Remaining questions will be addressed after the Webinar

@2

00

8-2

01

7 It

ris

Au

tom

atio

n S

qu

are

SAS

Thank you

Have a nice day!

www.itris-automation.com

@2

00

8-2

01

7 It

ris

Au

tom

atio

n S

qu

are

SAS