#10 PLC Best Practices – Assign Register Blocks by Function
Assign designated register blocks for specific PLC functions in order to validate data and block unauthorized access to controller data.
PLC Tutorials
Tutorials of Programmable Logic Controller – Learn PLC programs and ladder logic lectures of GE, ABB, Siemens, Allen Bradley, Omron PLC’s.
#9 PLC Best Practices – Validate indirections
PLC best practices – Validate indirections by poisoning array ends to catch fence-post errors.
#8 PLC Best Practices – Validate HMI Input Variables at PLC Level
HMI access to PLC variables can be restricted to a valid operational value range but further cross-checks in the PLC should be added.
#7 PLC Best Practices – Validate and Alert for Paired Inputs/Outputs
Alarm the operator when input/output states occur that are physically not feasible. Validate and alert for paired inputs/outputs in PLC.
#6 PLC Best Practices – Validate Timers and Counters
If timers and counters values are written to the PLC program, they should be validated by the programmable logic controller.
#5 PLC Best Practices – Cryptographic and Checksum Integrity Checks
Use cryptographic hashes, or checksums to check PLC program integrity and raise an alarm when they change.
#4 PLC Best Practices – Use PLC Flags as Integrity Checks
One of the best PLC best practices is to use PLC flags as integrity checks. Put counters on PLC error flags to capture any math problems.
#3 PLC Best Practices – Leave Operational Logic in the PLC wherever feasible
Leave as much operational logic e.g., totalizing or integrating, as possible directly in the PLC. The HMI does not get enough capacity.
#2 PLC Best Practices – Track Operating Modes
Track PLC operating modes – Keep the PLC in RUN mode. If PLCs are not in RUN mode, there should be an alarm to the operators.
#1 PLC Best Practices – Split PLC Code into Modules
#1 PLC Best Practices – Split PLC code into modules, using different function blocks (sub-routines). Test program modules independently.