I am getting this following error what was the root cause behind this error . can you please explain me so i can me move forward to further action ?
This message means that the PI Scheduler service has taken longer than the allotted maximum time in order to stop.
Is the PE scheduler currently running right now? Was it recently restarted, or told to stop?
Thanks for your initial help,
As from project requiremnt ,
I have calcuated value on every 1 ms so in ICU i select pipeschd interface and add scan class 0.001 and restart the ICU .
At this time I checked PI-SMT message log I found above error.
Can we calulated value in millisecond by using perfomanace equation?
Please note that the message is being printed because the "maximum stop time" has been exceeded. This is, in fact, a UniInt parameter, meaning it is common to all UniInt interfaces (of which PI PE scheduler is one). By default, the value is 120 seconds (two minutes), which is the amount of time given to the interface to stop and clean up when the interface is told to stop (via service stop or when interactive session is stopped), before a force stop is done.
The fact that it is being printed here implies that somehow the PI PE scheduler received a stop command (seems like this is implied by your comment about adding a scan class and restarting ICU, assuming you meant restarting the interface), and took over 120 seconds to stop. With PI PE scheduler printing this message, I suspect that perhaps it was in the middle of performing an 'expensive' calculation when it was told to stop. How many PE equations do you have running on this scheduler? Are there any which are performing summary calculations like TagTot, TagAvg, TagMean, etc over a large period of time?
Regarding your question about milliseconds, please be advised that UniInt scan classes can only be scheduled down to hundreths of a second. Also please be advised on known issue 3215OSI8. Even though PI PE scheduler may run scans at sub-seconds, the timestamps will always be rounded to the nearest second for purposes of calculation and final results. What is the need for having such frequently scheduled calculations? I would suggest considering using event-triggered calculations then, rather than periodic scan-based calculations.
Retrieving data ...