Recent posts to use globals in multiple actions in SFChttps://forge.codesys.com/forge/talk/CODESYS-V2/thread/47b6f0c230/2020-02-27T22:04:35.179000ZRecent posts to use globals in multiple actions in SFCuse globals in multiple actions in SFC2020-02-27T22:04:35.179000Z2020-02-27T22:04:35.179000Zshooterhttps://forge.codesys.com/u/shooter/https://forge.codesys.com62a55fe27c5f88641dea74ade560222d654ea34b<div class="markdown_content"><p>why reuse globals, why not use locals?</p>
<p>it is bad practice as the references will go crazy.</p></div>use globals in multiple actions in SFC2020-02-27T22:04:33.622000Z2020-02-27T22:04:33.622000ZAnonymoushttps://forge.codesys.com/u/*anonymous/https://forge.codesys.com3c3cd48b597bc8e6b75d3bc38ccb9b4c58f92e5f<div class="markdown_content"><p><em>Originally created by:</em> mr_sargent</p>
<p>Typically in ladder logic you would want to have one place where a global is activated/deactivated to avoid any logic complications. But since in SFC you can only have 1 step active at a time (excluding the IEC actions that are SET and continuously running) would it be OK programming practice to reuse these globals in different steps as long as you know they won't conflict with the same variable in the steps above? </p>
<p>Hopefully I made this question clear.</p></div>