800xA Batch con PM891: Batch phase not IDLE
Hi all,
we are running 800xA 5.1 with Batch and PM891 as controllers (BatchAdvTemplatesLib). Now and then, not really reproducible, we get the following error message at procedure level:
"Phase xxx is NOT idle" (see attached screenshot).
This happens, when the same phase is called twice after each other, but strictly consecutively at procedure level. So in theory, I would assume that the batch is really in idle state, as the PFC also shows it, before calling the same phase again. However, at times, we get that error. Because of this, we usually introduce a small delay between the two calls. It seems to work, but sometimes we still encounter situations where a phase is reported not idle, which is very annoying. When trying to restart the phase after that error from the block status, it always works. I have done some research and only found documentation on that issue for other controller types: DCI and Melody.
Is this error known for batch and PM891? If yes, what does cause it, can we somehow prevent it from happening? Thank you for your support.
Stefan
we are running 800xA 5.1 with Batch and PM891 as controllers (BatchAdvTemplatesLib). Now and then, not really reproducible, we get the following error message at procedure level:
"Phase xxx is NOT idle" (see attached screenshot).
This happens, when the same phase is called twice after each other, but strictly consecutively at procedure level. So in theory, I would assume that the batch is really in idle state, as the PFC also shows it, before calling the same phase again. However, at times, we get that error. Because of this, we usually introduce a small delay between the two calls. It seems to work, but sometimes we still encounter situations where a phase is reported not idle, which is very annoying. When trying to restart the phase after that error from the block status, it always works. I have done some research and only found documentation on that issue for other controller types: DCI and Melody.
Is this error known for batch and PM891? If yes, what does cause it, can we somehow prevent it from happening? Thank you for your support.
Stefan
Asked 1 year ago
Answers
0
Hi all,
I have checked the OPC update rates on our connectivity server and the task execution rates in the controller and have found that they didn't comply to the recommendation given in the ABB Batch Management Configuration manual: "The update rate of the fastest OPC group should be at least double of the execution rate of the slowest task in the controller." Since we corrected this for the application which we had problems with, the above described error never appeared again (for several weeks now). That doesn't have to be the solution, but at least notably reduced the frequency of the described error. Let me know what you think.
Stefan
I have checked the OPC update rates on our connectivity server and the task execution rates in the controller and have found that they didn't comply to the recommendation given in the ABB Batch Management Configuration manual: "The update rate of the fastest OPC group should be at least double of the execution rate of the slowest task in the controller." Since we corrected this for the application which we had problems with, the above described error never appeared again (for several weeks now). That doesn't have to be the solution, but at least notably reduced the frequency of the described error. Let me know what you think.
Stefan
Answered 1 year ago
Add new comment