https://forge.codesys.com/forge/talk/CODESYS-V2/thread/7bfceb9c60/2020-02-27T22:19:25.140000ZRecent posts to HELP! Runtime Error #812020-02-27T22:19:25.140000Z2020-02-27T22:19:25.140000Zshooterhttps://forge.codesys.com/u/shooter/https://forge.codesys.comc49e49c7c8a1128c72dd0bb83b4530ce96bce6a9

<div class="markdown_content"><p>yes in the helpfile and in the docs.</p></div>

2020-02-27T22:19:23.587000Z2020-02-27T22:19:23.587000ZMrkTrussellhttps://forge.codesys.com/u/mrktrussell/https://forge.codesys.com97c81b6299ae32b7d0739e60e8c68c6a6c87b4d0

<div class="markdown_content"><blockquote> <p><strong>shooter hat geschrieben:</strong><br/> you have a critical something in the tasktime, on old PLc this has worked, but now the watchdog is a lot stricter.<br/> check for long loops, or if the program takes too much time while waiting <br/> any program in a PLC must be complete every watchdog time.<br/> the watchdog is reset when a program or function block ends.<br/> this is complete different from a basic or C program.</p> </blockquote> <p><span style="color: #BF0000;"><strong> Is there a database of these runtime errors somewhere? A lookup table perhaps with descriptions and common causes / remedies?</strong></span></p></div>

2020-02-27T22:19:19.279000Z2020-02-27T22:19:19.279000Zshooterhttps://forge.codesys.com/u/shooter/https://forge.codesys.com9c3c46326c16957f13bfc03e363463207691b59b

<div class="markdown_content"><p>you have a critical something in the tasktime, on old PLc this has worked, but now the watchdog is a lot stricter.<br/> check for long loops, or if the program takes too much time while waiting <br/> any program in a PLC must be complete every watchdog time.<br/> the watchdog is reset when a program or function block ends.<br/> this is complete different from a basic or C program.</p></div>

2020-02-27T22:19:17.744000Z2020-02-27T22:19:17.744000ZMrkTrussellhttps://forge.codesys.com/u/mrktrussell/https://forge.codesys.come846697579de8bd4b54b58d0c8ceb63b7c251297

<div class="markdown_content"><p>A little more research has lead me to believe that this access violation at address '0x00000000' indicates a null pointer. <br/> So, I am most likely using something before it's created. Still, I am puzzled as to why this does not create an error on the old PLC.</p></div>

2020-02-27T22:19:13.437000Z2020-02-27T22:19:13.437000ZMrkTrussellhttps://forge.codesys.com/u/mrktrussell/https://forge.codesys.comaa29a5315d78c788011157367da9d6d5b22cce68

<div class="markdown_content"><p>Well, I was able to get the PLC into RUN mode by disabling the MAIN task (the task causing the error). This was expected, but not acceptable.</p> <p>I can't seem to find anything in the code that would create a problem here. This program runs on the last generation of the PLC I'm using. It refuses to run on the latest generation.</p> <p>I do have more information stating:</p> <p>Instruction at 0x00226DE4 attempted to read data at 0x00000000.</p> <p>I think this refers to the access violation, but as I stated previously, this code RUNs on the last generation PLCs.</p></div>

2020-02-27T22:19:11.873000Z2020-02-27T22:19:11.873000ZMrkTrussellhttps://forge.codesys.com/u/mrktrussell/https://forge.codesys.com9e90d6ae993345a60d9baf696da8ea1c38346f9b

<div class="markdown_content"><p>Does anyone have any information on "Runtime error #81 (access violation Task = MAIN) ?? I can't find any documentation for this error.</p> <p>The task throwing the error is the task that runs my main PLC_PRG. I am working on an ABB AC500 PM590 CPU. The error is produced EVERY time I try to RUN the PLC. Therefore, I cannot RUN the PLC.</p> <p>The PLC is giving me the following error in conjunction with the above:<br/> E2: IEC Task 0. Cycle time of IEC task index x - 4 is greater than watchdog time (x = 31 -&gt; IEC task index &gt; 27)</p> <p>I have modified the task configuration multiple times now to no avail.</p> <p>Any thoughts? Any help is greatly appreciated.</p></div>