-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
default sample time is too fast? #56
Comments
Thanks for posting this Raj, it's one of those things that is "known" vaguely but never got properly documented. This is a consequence of us having crazy numbers of PVs in our IOCs. I suspect we want to be smarter about the sample time we choose in these "many PVs" cases rather than always bumping to 1Hz. |
Ok cool. Is there any way to know or test if the sample time is too small, so it can step it up until it reaches a minimally satisfactory sample time? |
The IOC can tell if the current sampling time is "too fast" by seeing if it has enough time to process all the PVs before the next scheduled update. I do not know if it is possible to continually change the parameter and optimize it, or if it needs to be set once at the start of the program as the module is currently written. The consequence of not increasing the sampling time from 50ms is that you'll get your PVs back at arbitrary intervals, e.g. it will go "as fast as it can" and finish whenever it does. Having the sampling time too low can also theoretically impact PLC performance, but I'm not sure if this is a leading-order concern compared to the IOC process getting overloaded. |
This line seems to suggest the default sample time being set by the template is too small so it samples it 20 times slower.
The text was updated successfully, but these errors were encountered: