800xA - Control Builder - Application
In Control Builder, After Creating Application, When i select Application, right click new.....
I get 4 options:
1) Control Module
2) Single Control Module
I know Programming is possible through all..but what is the difference.
Which has to be used where?
Voted best answer
>"Which has to be used where?"
It Depends ......
You could write a very long book on which is the "best" programming language to use, but it really comes down to understanding the strengths and weaknesses of each language. I would suggest that you try programming the same simple application in each of the three (not 4) techniques you list ...
1) and 2) Are the same thing.
Control Modules have some strengths. They are very efficient and very resusable. You can write a very large amount of repeated code very quickly. They are particularly good in applications where you have a lot of identical simple IO and control types - for example power plants where you are basically monitoring and alarming several hundred or thousand digital IO but dont do much logic. Control Modules are also extensively used for Food and Beverage applications and Batch applications.
Control Modules can be written using any language ( IL, SFC, LD, ST and FBD ) but most applications use ST.
To get the best out of Control Modules you have to understand the concept of Code Sorting and why it works ( and why sometimes it doesnt ). Again, code sorting is a very long topic.
Control Modules are great for programmers, but programming in Control Modules is not always very intuitive. They can be hard to explain to plant support personell who are more used to traditional type PLCs. The graphical programming interface (CMD Editor) is very old and not really usable, so control connections are done using variables and without much graphical representation.
These are the standard IEC programming languages of ST, IL, LD, SFC and FBD. These languages are very familiar to anyone used to programming regular PLC's. However the code is less efficient - the compiler does not optimize memory very well so your program tends to be bigger unless you do more work to reduce memory consuption.
These languages are used quite extensively in Pulp & Paper for example. There is less re-use of code and much of the application is complicated and unique to the process. Programming in FBD is an easy and fast way to write logic like this and IMO easier for plant maintenance to troubleshoot complicated logic.
You can also combine Control Modules with Program Units by inserting Control Modules to a Program and then using the "ExecuteControlModules" function to call them.
In a perfect world, this is a great combination of Control Modules AND Program units, and it does certainly work very well. However, there are still some limits that prevent using Diagrams in every industry ...
- There is no support for embedding Diagrams into Control Modules and Programs, so if you are going to use Diagrams you need to make this decision at the start of your project and write everything in Diagrams.
- Diagrams dont work with the Batch Manager properly yet. Things just break horribly when you try it.
You can also program in Function Diagrams, but thats a whole other story.
Its depends on user how to build a application to suite & for understanding purpose.
Here all 4 languages you can use at a single application it depends.
ex:Control modules are very efficient programmming language which uses code sorting so that logic/program will be executed faster since its runs based on data flow instead of program flow as like in normal programming language(IEC61131-3 SFC,ST,LD,FBD,IL)
here in single control module we can create many control modules & you can use the normal programming language as well.
single Control module uses CMD editor to make the logics/applicaitons.
Diagrams: After 5.1 FP4 this new language came, to make the logics graphically looks best by using all kinds of control modules/programming blocks so that you can hide the unwanted ports of the control modules/function blocks, here you can launch the hardware editor directly by using the parameter reference on right click,view total program flow.