Toggle Bit - S7
From ControlWiki
(Difference between revisions)
| (2 intermediate revisions not shown) | |||
| Line 1: | Line 1: | ||
{{PLC Archive | {{PLC Archive | ||
| - | | page_title=S7 | + | | page_title=S7 - Toggle function with Set/Reset override. |
| author_name=Helge Slettvoll | | author_name=Helge Slettvoll | ||
| program_filename=HSLE_FB108.pdf | | program_filename=HSLE_FB108.pdf | ||
| - | | abstract=Function Block with three input bits: Toggle, Set and Reset. Status output bit changes accordingly - from 0 to 1 or from 1 to 0 on rising edge | + | | abstract=Function Block with three input bits: Toggle, Set and Reset. Status output bit changes accordingly - from 0 to 1 or from 1 to 0 on rising edge of Toggle input. |
| - | Set and Reset input overrides Toggle input. | + | |
| - | If Set and Reset are both 1, then Status is 0 (Reset dominant) | + | Set and Reset input overrides Toggle input. If Set and Reset are both 1, then Status is 0 (Reset dominant). |
| + | |||
Helper bits are kept in instance data blocks, thus reducing the risk of typical copy/paste errors and simplifying memory allocation. | Helper bits are kept in instance data blocks, thus reducing the risk of typical copy/paste errors and simplifying memory allocation. | ||
[[File:FB108DB171.jpg]] | [[File:FB108DB171.jpg]] | ||
}} | }} | ||
Current revision as of 08:53, 17 August 2010
S7 - Toggle function with Set/Reset override.
contributed by: Helge Slettvoll
Link to File
Click here to view program file.
Abstract
Function Block with three input bits: Toggle, Set and Reset. Status output bit changes accordingly - from 0 to 1 or from 1 to 0 on rising edge of Toggle input.
Set and Reset input overrides Toggle input. If Set and Reset are both 1, then Status is 0 (Reset dominant).
Helper bits are kept in instance data blocks, thus reducing the risk of typical copy/paste errors and simplifying memory allocation.
Disclaimer
For all material in the PLC Archive, our site disclaimer applies. You take full responsibility for the application of any code appearing on this site, as we have made no engineering evaluation of the code nor are we, or the author, familiar with the details and risks inherent in your application.
