Thread Content
After sequential cutting, as shown in the figure, click on a single interlock button; for example, click on SV6101. SV6101 is now in the green \"on\" state. Does it turn red and go into the \"off\" state after being clicked? Please share your thoughts, thank you. Bonus points
This is just a interlock schematic. It still depends on the interlock logic diagram provided by the design institute or the logic diagram in the configuration. Whether to close the valve depends on whether you are currently in an interlock activation state; if it isn’t activated, bypassing it has no impact on what comes later. If it’s triggered, it might be just as you said. Of course, this is all speculation; it still depends on your specific configuration logic diagram.
This post was last edited by jlshnlhj on 2017-11-29 09:54: OR gate, input 1 for action. With 4 inputs, interlocking action will occur as long as 1 of them is 1. The interlock button shown in the diagram is actually a manual interlock switch; when activated, it initiates the interlock action, while when deactivated, it shuts off the manual interlock. After clicking the “Cut” button, the OR gate output remains unchanged. After clicking the “Input” button, the OR gate’s output is 1. The color change depends on the configuration.
By clicking the cut-off button above, the entire interlock circuit is disconnected and does not participate; whether the process parameters have reached the interlock values has no impact on the operation of the cut-off valve below; Is the button near the cut-off valve a reset button? It is also possible to remove the valve interlock (to facilitate valve maintenance). From what I can see in this diagram, it seems that the \"1\" signal triggers the interlock, which does not meet the relevant safety requirements. Now, a “0” signal is required to trigger interlocking.
Interlocked resection will definitely not work; if it did, then why perform the resection at all? Removal still works, but how are the instruments and valves maintained?
Interlocked removal will definitely not work; if it does function, it can only mean that your configuration is incorrect
Interlocked resection is like cutting off your pipeline all the way to the branch line.
Removal is equivalent to bypassing it. So it doesn’t work anymore