Download timeslice serial#
System Overhead Time Slice (SOTS) – A Closer LookĪs previously mentioned the System Overhead Time Slice (SOTS) is a setting that allows you to control the amount of processor CPU time allocated to background tasks, such as communications, Trends, MSG instruction traffic, serial port communications, Connection Manager operations, upload/download and online edits. Okay, so this turned out to be a network/CPU optimization type problem, however, I don’t think we’ve painted a detailed enough picture of what the SOTS actually is and does.
Download timeslice code#
Ultimately, by incrementing this setting to 35% I was able to eliminate the Module Connection and and Control Sync faults, however, there is a trade-off in that your Continuous Task scan will increase, which could in itself create a whole host of other problems.įortunately, this wasn’t the case in my circumstance, however, if increased scan were to create user program issues, my next step would have been to look closely at Continuous Task structure, i.e., removing non-critical pieces of code or programs that really don’t need to be in there (meaning they don’t need to be constantly scanned) and broken out into event-driven or periodic type tasks to reduce scan time. This setting can be found under Controller Properties –> Advanced tab as depicted below.īy increasing this time slice you can effectively increase the amount of time the CPU is allocated to services back-end system tasks such as communications. My thought here was to see how much of the overall CPU time was allocated to service some of the back-end system tasks such as communications. My next thought was to look at the System Overhead Time Slice (SOTS) setting. That said, a Skorpian IP Router was used to segregate the cell network from the rest of the plant network so I could be certain that the only network traffic in the cell was localized at the cell level. Of course, the time needed to procure the managed switch was not an immediate option and the complexity that is inherent when moving from an unmanaged to a managed switch was not something the internal engineering personnel nor machine builder was comfortable with. My first thought was the Unmanaged Ethernet Switch was going to have to be switched out for a Managed Ethernet Switch so that the network traffic could be efficiently optimized through the use of VLAN’s and VLAN routing.
Both faults were appearing on all axes so immediately I suspected a network management problem due to the volume of Ethernet/IP network traffic and the deployment of an Unmanaged Ethernet Switch. Upon further investigation into the axis fault logs I saw several “Module Connection Faults” followed immediately by a “Control Sync Fault”. The customer indicated that they were having intermittent servo motor issues stopping arbitrarily mid-cycle. Now that we have a general understanding of the complexity of the Ethernet/IP network in place let’s focus in on the problem that was presenting itself and then see how the System Overhead Time Slice setting corrected the problem. 12 x Allen Bradley 5700 Servo Drive units.1 x CompactLogix 5370 Safety Controller.A broad overview of the Ethernet/IP controls network is as follows: While both cells were symptomatic of the same CPU utilization type problems, I focused first on the larger of the two cells. I recently had a service call to a customer who had just launched a new program that required two integrated robotic cells to build out their product line. As the complexity and connectivity of modern automation systems get more complex requiring high-performance communications, I/O, and motion control, careful consideration must be taken to ensure that both user-defined and back-end system tasks are optimized to mitigate the likelihood of CPU starvation. I thought I would do a piece on the System Overhead Time Slice setting you will find in pre- L8 (5580) Allen Bradely ControlLogix and CompactLogix platform of controllers.
0 kommentar(er)
