Download PLC Checker User Guide

PLC Checker User Guide
7.3.2
Properties
Name (name)
See Concepts - Rules - Rule name
Identifier (id)
See Concepts - Rules - Rule identifier
Code filter (treatments)
See Concepts - Rules - Code filter
Data filter (variables)
See Concepts - Rules - Data filter
S
A
I
Type of checking (checkType)
Written from one task only (writtenFromOneTaskOnly) This rule check that all writtings of each variable
of the variable sub-set, found in the code sub-set, can be executed from only one task. Example : a PL7-Pro
application mays contain the MAST task, a FAST task and one task per events. This rule is useful to identify
critical variables due to concurrents accesses.
Written only once (writtenOnce) This rule checks that each variable of the variables sub-set (variables properties) is written only once in the code filter (treatments properties). This is useful for example to check that the
outputs are written from only one equation.
Set only once (SetOnce) This rule checks that each variable of the variables sub-set (variables properties) is set
only once in the code filter (treatments properties).
Reset only once (ResetOnce) This rule checks that each variable of the variables sub-set (variables properties)
is reset only once in the code filter (treatments properties).
Written from one code block only (writtenFromOneBlockOnly) This rule check that all writings of each
variable of the variable sub-set (variables properties), found in the code sub-set (treatments properties), are in the
same block of codes. Example : In a PL7-Pro application the blocks of codes are the sections, the SR and the
events. This rule is useful to check application modularity.
Written before read (writtenBeforeRead) This rule check that each variable of the variable sub-set (variables
properties) is written before read in the code sub-set (treatments properties). This rule can check application
reactivity.
Written in block (writtenInBlock) This rule check that each variable of the variable sub-set (variables properties) is written at least once in the code sub-set (treatments properties). This rule allows to check that all application
variables are used.
Not written in block (notWrittenInBlock) This rule check that each variable of the variable sub-set (variables
properties) is NOT written in the code sub-set (treatments properties). This rule is useful to check application
modularity.
68/77
January 2011