![]() Please note that the contact before the ADD instruction is generally unnecessary if you want it to execute all the time: While the EN input is true, the instruction executes: Here is a disabled ADD instruction (the EN input is FALSE), and you can see that the ADD instruction isn’t being executed because the Result is still 0: The instruction is only executed if the EN input is true. Notice that the editor added the EN input and the ENO output automatically. Here is what it looks like in the ladder logic editor: Here is what the ADD function looks like in the function block diagram editor: ![]() Ladder logic, however, requires the concept of a “rung”, which is just power (represented as a BOOL signal) entering from the left, and connecting all of the language elements together within the rung (a.k.a “network” in TwinCAT 3). All of the function blocks available in the function block diagram editor are also available in the ladder logic editor, so I consider the ladder logic language to be a super-set of the function block diagram language. ![]() In some ways, the function block editor is just the ladder logic editor without contacts and coils. In TwinCAT 3, the ladder logic editor shares a lot of functionality with the function block diagram editor. This chapter is part of the TwinCAT 3 Tutorial.
0 Comments
Leave a Reply. |