![]() ![]() ![]()
If you are using event based tasks, they will change the operation by interrupting the current task in a manner that depends on the relative priority of the current and event based task. ![]() Does reducing timeslice increase system speed series#Event based tasks (available in RSLogix 5000 v12 and higher – see our Mastering ControlLogix video series here) are beyond the scope of this article. We will consider three kinds of tasks: continuous, periodic and motion. It’s hard to describe the effects the System Overhead Time Slice will have on a given application, so some scenarios below illustrate the principles by example. Changing the time slice can have some complex effects on your system, depending on the overall makeup of the tasks in your processor. Does reducing timeslice increase system speed 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. Does reducing timeslice increase system speed 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.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |