7/19/2016 4:51 PM | |
Posts: 91 Rating:
|
Hello, I'm sort of following a Siemens guide for putting diagnostics in the user program -- see here. However, I've found on a cold restart of the system, the Startup OB doesn't complete. There is some error handling that Siemens wrote to diagnose where in the process it got interrupted, however, no error code is ever spit out. The only thing I can think of is that the startup OB is being interrupted by a diagnostic OB (OB82 or 86). In the diagnostic OB, they have a copy function that copies an array to a DB for HMI display purposes. If the startup OB doesn't run, the array is not configured properly, and then you would get an access error as it tries to write to an array of 0 size. Is it possible for the startup OB to be interrupted? I thought that has to run first. The odd thing is if you put the PLC in stop, and then in run, it works fine. If it's warm it works fine. If it's cold, it doesn't run properly and the PLC goes to stop mode. Is it possible for a Startup OB to be interrupted? I'm using a ET200SP CPU (1512) and Tia Portal V13 SP1 update 5. |
Last edited by: Toombs at: 7/19/2016 4:52:43 PM |
|
7/19/2016 5:28 PM | |
Posts: 91 Rating:
|
For this one, it makes me think it can. Attached is the error I get. It says "Temporary CPU error: Area length error in FC 2081 affecting OB 83 execution." The only way that would happen is if the Startup OB doesn't process. The error happens immediately after the CPU changes from STOP to Startup Mode. Half the startup OB completes and then it seems OB83 interrupts it -- the array isn't setup yet so it faults out on programming error. AttachmentDiagnostic_Failure_OB83.zip (54 Downloads) |
Follow us on