Detects the POUs that violate the activated metrics at the lower or upper limits
Justification: Code that complies with certain metrics is easier to read, easier to maintain, and easier to test.
Importance: High
PLCopen rule: CP9
Example
Initial situation: The “Number of calls” metric is selected in “Project Settings Static Analysis Metrics”. Lower limit: 0; upper limit: 3. Prog_1 is called five times.
When running the static analysis, the “SA0150: Metric violation for Prog_1. Report for metric calls (5) > 2” error is issued in the message view, in the “Build” category.