https://forge.codesys.com/forge/talk/Engineering/thread/2ea9b8a08b/2020-02-27T13:58:34.179000ZRecent posts to Common exception handling2020-02-27T13:58:34.179000Z2020-02-27T13:58:34.179000Ztimvhhttps://forge.codesys.com/u/timvh/https://forge.codesys.com173ec51f15fed859c5528f19aaec8309a670c44a

<div class="markdown_content"><p>You could use the Callback functionality, but in this case I would advise to add the "POU for implicit checks".<br/> Here you can select which kind of checks you want the runtime to do.<br/> This helps you find any problems in the code regarding division by zero or accessing an array out of bounds.</p></div>

2020-02-27T13:58:33.919000Z2020-02-27T13:58:33.919000Zchabhttps://forge.codesys.com/u/chab/https://forge.codesys.com14d6e99d480f6fcb265264741d01bc4d2cf4afe0

<div class="markdown_content"><p>What is the common handling for System Exception?</p> <p>For example when the exception DIVIDE BY ZERO is triggered.</p> <p>In my test setup, the device will halt. And I can see what happened in the CodeSys ControlDevice; Log. See figure.</p> <p>But in the factory, the CodeSys ControlDevice; Log is not available. A GUI is available, but that is not updated anymore (halted also).<br/> The users will have to do a device reset (power cycle) manually. Or can / should I do a device reset automatically (if possible at all).</p> <p>In this case, the application is not critical. But the users will notice an automatic reset. So my preference is a manual restart by the users. </p> <p>Any thoughts...</p> <p>Regards,<br/> Edwin.</p> <p><img alt="IMG: exception_log_02.JPG" rel="nofollow" src="https://forum.codesys.com//download/file.php?id=356"/></p></div>