I am facing a issue with OCR400 controller.
i am using Run Time algorithm in Drop1, for calculating some cycle time. I observed that, the minutes value of run time, is completing one minute in around 61 sec(So, the cycle time of 140 min has increased to around 142 mins). This cycle time is not constant now, unlike it used to be earlier. This has started recently. Earlier there was no such issue. Actually, all the accumulating algorithms like Run Time, Reset Sum has started functioning slower than it used to. In case of reset sum, I was integrating one analog value over a period of time. I also used report manager for the same integration. The output from both reset sum algorithm and Report manager were equal earlier. But, now, i have observed that the reset sum output lags behind the result that i get from Report Manager. I have not rebooted the controller from a while now. There were no Drop Alarms.
I have used system time algorithm also, and that is also lagging behind the actual UTC time by 5 secs. When i use the same algorithm (reset sum, run time, system time etc.) in some other controller(Drop 2). the results are okay. I could nt find anything on the error log. We have been making regular changes in the logic, and Drop Load is also successful (without any alarms and failures).
Has anybody faced such issues?
Hi Nandan - your post does not match any known issues that I am familiar with. If you send us some details about your plant and release level (to: ovation-wdpf@emersonprocess.com) we can have one of our local experts contact you to debug the problem.
In reply to Greg Schirm:
Hi Greg, It is Ovation 3.3.1, i have mailed you other details, which might be helpful, though as i said i could not find any controller alarms from error log.
Thanks.