Functional Spec / Test Documentation of Interlocks

moistcat

Member
Join Date
Jun 2020
Location
Melbourne
Posts
54
Hi all,

I was wondering if anyone had any good methods for developing functional spec / test sheets for equipment interlocks.
I find the best method to describe a particular process / equipment interlock is the ladder logic itself.

I have also seen the method with defining signals: A = Tank High Level, B = Mains Phase Failure
Then expressing as: PMP005_INTERLOCK = A | B

Any ideas /comments would be awesome!
 
I always used a cause and effect matrix via a spread sheet as a programming/documentation tool. However, it would not be a good function test document. Test plans take a lot more effort, and a lot of process knowledge.
 
I've seen similar in Excel, but it gets very clunky very quickly when you have chained conditions like A OR (B and (D AND NOT C)) OR (F AND C).

Because of this we moved from Excel into a Word document with a portrait format and revert to text. However in some instances where the person specifying the interlocks actually understands the whole process, he may define them as the output of an interlocked block, which will split the complexity of the interlock logic in different process elements.
 
You could use Structured Text.
Even if the ST program is dormant and not actually used, you can enjoy the benefit of accessing the symbols of the PLC program.
And you can embed the ST program in the same PLC project as the 'normal' PLC program, so you automatically syncronize the versioning of both.

edit: If you can get the spec in text pseudocode, you can add that to the ST program as a comment header.

I have also seen the method with defining signals: A = Tank High Level, B = Mains Phase Failure
Then expressing as: PMP005_INTERLOCK = A | B
Technically not wrong, but people that are not used to notation of logics will be confused.
Write the logic in plain text is better.
In the above I am also missing what state both the incoming and outgoing signals must be for TRUE or FALSE states.
I am guessing that the signals are to be fail-safe, so Tank High Level is an N.C. signal, i.e. it must be TRUE to release the other part of the process.
 
Last edited:

Similar Topics

Hi there, i like to know if some of you experienced plc gurus have particular method/s on simplying a plc program written by somone else. whether...
Replies
2
Views
1,707
I've been trying to solve an issue that I've had for several days now and it has now made me give up, which in turn led me to this forum in hope...
Replies
7
Views
2,590
Hi, I'd like to understand the difference between the following 'functional safety' wiring methods and how they relate to the EN13849-1 'input -...
Replies
5
Views
2,529
We have a legacy winch system that was built back in 1975, we are looking to replace all the controls (electrical) on this and bring it up to...
Replies
8
Views
1,914
Hi Guys, Please Pardon me if this sound odd. I'm to provide PLC functional Design Specification and PLC Logic Desig to a Client. I need to be...
Replies
16
Views
9,920
Back
Top Bottom