The first concern comes here, as some of our realtime programmers opinion is that methods are not done for this, that in this cases we should implement FB_INIT which is called from the FB_CONVEYOR and it contains its own variables, so both have a REF to FB_MOTOR. MEthod will contain its won state machine and will not be ready until it´s output returns TRUE value. For example, if I have a FB_Conveyor which has its own state machine inside I could select to create and internal METHOD (M_INIT) for the conveyor which will inspect the conveyor in order to check if there is any products when conveyor it is in INIT state, checking the Method output value. One very good example that is pretty much taking our attention at the moment is the new Methods and the overall differences with the Actions.įrom my own point of view Methods are created not just in order to define and implement interfaces but also as a way to simplify the FunctionBlocks and their internal state machine.
#TWINCAT 3 DATABASE HOW TO#
At the moment, we are suffering a transformation of our PLC architectures due to the new functionality that are bring by TwinCAT 3 (Object Oriented)Īt the moment we are developing our new PLC architecture and we are having several concerns about how to go forward. I´m old users of Beckhoff technologies, especially TwinCAT.
0 kommentar(er)
