2015 Softing Inc. All Rights Reserved. tmanager Performance Considerations

Transcription

1 tmanager Performance Considerations

2 Softing Softing is a leading global provider of products for Industrial Automation and for Automotive Electronics. For over 30 years, the core business of Softing Industrial Automation has been industrial data communication with products ranging from chips & stacks up to dedicated gateways and data transfer modules. Softing acquired Psiber Data GmbH and OLDI in Psiber Data sells cable testing products. OLDI is an Original Design Manufacturer (ODM) that designs and sells PAC/PLC modules under other company brands and a few with the OLDI brand. OLDI as a company will continue as an ODM. OLDI and Psiber Data products will transition to the Softing brand in Softing also acquired the industrial communications product line from Trebing and Himstedt (TH) in As of January 1, 2015, the official North America company name is Softing Inc.

3 Softing Inc. Sells Softing and OLDI branded products Global Encompass Product Partner Products for Rockwell Authorized Distributors: Data Exchange Modules Communication and Protocol Modules Network Monitoring and Cable Test Tools Headquartered in Knoxville, TN

4 Products sold through the Rockwell Automation Channel Move Data Run Custom Code Certify Cable Connect Networks Monitor Networks eatm Enterprise Appliance Transaction Modules catm Controller Appliance Transaction Modules SAM Special Application Modules WireXpert Advanced Cable Certifier for Ethernet copper or fiber PCI; PCI Express Network Cards for High Temp Environments TH Scope; TH Link Monitor; Diagnose EtherNet/IP and other networks ControlLogix

5 Topics Performance overview Rockwell Automation reference manuals RA Logix Design recommendations RA EtherNet/IP recommendations tmanager performance optimization recommendations tmanager EtherNet/IP Communication options Database communication

6 Typical Performance Landscape There are many factors that affect overall throughput of a tmanager system.. Controller Controller Model ControlLogix L63 vs L75, etc. Rockwell Design Tips Time Slice Continuous, Periodic & Eventbased tasks DINTS Optimized UDTs Single Dimension Arrays Network or ControlLogix Backplane Backplane vs Front Ethernet port Type of Ethernet Bridge ENBT vs EN2Tvs EN3T EtherNet/IP Design Guidelines Switch features tmanager Trigger Scan Times OLDI Best Practices Triggers/Endpoint s/maps Use of Transaction Logs Use of Store & Forward Use of Status Tags System Log configuration Handshaking Business Ethernet Network Configuration Transaction rates Firewalls Network Loading # of hops etc Database Database Maintenance & Design Table Design -- contains index/keys on the appropriate columns Stored Procedure design -- consider impact of locks on heavily used tables, views, etc.

7 Rockwell Automation Design Documents Referenced While Preparing this PPT ControlLogix and CompactLogix Design Documents Expand Performance and Capacity Guidelines Chapter 2 of the Logix5000 Controllers Design Considerations manual has information concerning task scheduling and time slice setup for optimum performance. Pub RM094F-EN-P Chapter 3 of the Logix5000 Controllers Design Considerations manual contains guidelines for using various Logix data types Integrated Architecture Top 50 Design Points EtherNet/IP Performance Guide

8 Logix Optimization: Logix Time Slice If you have a continuous task, RSLogix5000 allows you to allocate a System Overhead Time Slice (SOTS), which is a percentage of the CPU s time reserved for background CPU functions such as: Communicating with programming & HMI devices Responding to messages Sending messages Serial port message & instruction processing Alarm instruction processing The tmanager uses CIP Class 3 (unconnected) messaging, processed in the time slice The SOTS only affects messaging performance if a continuous task exists The default value is 20% Raising the SOTS increases the scan time of the continuous task, but should increase the number of messages per second that are sent between the tmanager and Logix processor The recommended SOTS setting for a data concentrator is 50% or greater. Suggest starting with 50%. If everything is working well, you can see if raising it higher improves performance further

9 Logix Optimization: Task Configuration When Motion, Periodic, and Event Based tasks are used, configure them carefully Eliminate task overlaps Allow enough time for the communications task - SOTS Don t configure multiple periodic tasks at the same priority and same rate Each task will task switch with the others, executing in 1 msec intervals until all are complete There is overhead associated with each task switch For more information on how Logix processors handle different types of tasks, and to see graphical examples of the effects of changing the SOTS and other task parameters, reference Chapter 2 in the RA Logix5000 Controllers Design Considerations manual The information on this slide is from the Rockwell Automation Optimizing Control System Performance presentation, presented at various Automation Fairs. The information is also contained in the Logix5000 Controllers Design Considerations manual.

10 Logix Optimization: Use DINTS Use the DINT data type whenever possible. Logix is optimized for 32 bit data types, and they are processed faster than other data types SINT INT DINT REAL Memory usage for a Tag 4 Bytes 4 Bytes 4 Bytes 4 Bytes Memory Reserved for data in a UDT 1 Byte (8 Bit aligned) 2 Bytes (16 Bit aligned) 4 Bytes (32 Bit aligned) 4 Bytes (32 Bit aligned) Memory used to access instruction in an ADD * 236 Bytes 260 Bytes 28 Bytes 44 Bytes Execution Time for an ADD instruction * L μsec L μsec L μsec L μsec * Assumes all parameters are same data type The information on this slide is from the Rockwell Automation Optimizing Control System Performance presentation, presented at various Automation Fairs. The information is also contained in Chapter 3 of the Logix5000 Controllers Design Considerations manual.

11 Logix Optimization: Data Structure Guidelines Use the following data structure guidelines whenever possible Use Single Dimensional Arrays and User Defined Structures when designing your application Create tag names that are as descriptive as possible while keeping them short to minimize the memory usage and the communication packet size Use single aliasing to prevent changes to documented logic on upload of project Create packed UDTs to optimize memory and performance Use DINT arrays for B3 File usage (avoid bool arrays) Use the LINT data type (64-bit integer value) to store date and time values The information on this slide is from the Rockwell Automation Optimizing Control System Performance presentation, presented at various Automation Fairs. The information is also contained in Chapter 3 of the Logix5000 Controllers Design Considerations manual.

12 Logix Optimization: Optimizing UDT Memory Usage DATATYPE Sample1 BOOL Bit1; SINT Tiny_Value BOOL Bit2; INT Small_Value DINT Big_Value REAL Float_Value END_TYPE DATATYPE Sample1 BOOL Bit1; BOOL Bit2; SINT Tiny_Value INT Small_Value DINT Big_Value REAL Float_Value END_TYPE User defined structures allow you to combine multiple data types (atomic, predefined or user defined) into a new data type All elements in a structure are located on a byte (8 bit) boundary You can optimize the layout for readability or memory usage. Optimized memory usually yields better performance Group all bits adjacent to each other when creating a user defined structure Reduces the amount of memory used and reduces communications time The information on this slide is from the Rockwell Automation Optimizing Control System Performance presentation, presented at various Automation Fairs. The information is also contained in Chapter 3 of the Logix5000 Controllers Design Considerations manual.

13 RA EtherNet/IP Switch Recommendations When using Ethernet/IP for control, use an industrial grade switch Required switch features: Full-duplex capability on all ports Recommended switch features: VLAN Auto-negotiation/manually configurable speed/duplex Wire-speed switching fabric SNMP IGMP snooping constrains multicast traffic to ports associated with a particular IP multicast group Port diagnostics Port-mirroring (required for troubleshooting) Allows traffic analyzer connection without affecting the run-time system STP for loop prevention QoS The information on this slide is from Chapter 6 of the Logix5000 Controllers Design Considerations manual. For additional control network guidelines, reference the RA Logix 5000 Controllers Design Considerations manual and the RA EtherNet/IP Performance Guide

14 tmanager Optimization: System Log & Status Tags When you configure the System log, do not keep the Log detail level setting at DEBUG longterm Only enable the DEBUG mode for System logging if you are instructed to use it by OLDI support, and then remember to change the setting back to INFO or one of the other options when you are done Logging DEBUG messages will have a negative impact on tmanager performance Status Tags Since they will add loading on the controller and could affect performance, only define Status Tags for the projects, triggers and endpoints where they are needed and will be used by the controller s application program

15 tmanager Optimization: Transaction Logging & Overrun Timers Only enable Trigger & Endpoint Transaction Logging as needed for regulatory purposes, or during troubleshooting & start-up Transaction logging reduces the number of transactions per second that the tmanager can process If you have a large transaction, logging the entire transaction has a greater detrimental effect than just logging a specific number of bytes Trigger and Endpoint Overrun Timers The overrun features should be enabled sparingly, mainly during troubleshooting, since they will slow down the overall throughput of all the triggers on the module. For more information on Overrun Timers, reference the tmanager Troubleshooting presentation. The values entered for the trigger overrun timers need to be greater than the Scan Period. If the values are too low, the system log will get filled with overrun errors, the module throughput will decrease, and other important events and/or errors may be missed

16 tmanager Optimization: Store & Forward If Store & Forward is enabled on an endpoint, once communications are interrupted & data is sent to the S&F queue the number of transactions processed per second may decrease There is an initial time-out period that depends on either the adapter s configured connection or the transaction time-out values before writing to the S&F queue is initiated Writing data to the queue, which is stored on the tmanager s compact flash, may take more time than sending the information to it s normal destination Once communication is restored, there may be a detrimental effect on overall tmanager performance while data from the S&F queue is sent to its intended destination

17 tmanager Optimization: Separate Triggers & Endpoints Handshake mode selection effects when the next trigger firing occurs: When combining transactions under one trigger, remember that the trigger cannot fire again until the completion of all the messages at their level of handshaking. Therefore, one slow message, or one message with a high level of Handshaking selected, would cause all messages to wait for its completion It s often best to have one trigger per message path For more information on Handshaking, reference the tmanager Details and Best Practices presentation Separate endpoints are recommended if you have a transaction message which you might expect to be more time-consuming (x-sec vs. <1-sec to complete). The use of a separate endpoint will allow faster transactions to continue while the slower transactions wait in the queue for their completion

18 tmanager Optimization: One Controller.One Map Although you can use tags from multiple controllers in a single map, it is not recommended If any of a map s input variables are not available when the trigger fires, the trigger is marked as faulted and will not retry for 60-seconds If multiple controllers are used in a map, loss of communications with any of these controllers will cause the trigger to stop firing until all of the controllers are once again available If you need tags from multiple controllers mapped into a single database table at the same time Recommend mapping all the tags into a data concentrator controller Map tags from the data collector PLC to the database table in a single map

19 tmanager EtherNet/IP Communications EtherNet/IP communication over the ControlLogix backplane is usually faster than out one of the front Ethernet ports Rockwell Automation designed the ControlLogix backplane for speed and ease of communications, so backplane communication to the tmanager is always as fast or faster EtherNet/IP out the front port is comparable to communication over EtherNet/IP via a 1756-ENBT A 1756-EN2T/3T is twice a fast as a 1756-ENBT Reference Rockwell Automation Knowledgebase document for a comparison of the different Logix EtherNet/IP Bridge modules

20 Database Communication Configuring several database adapters versus having everything go to/from the same database has no impact on performance The size of the transactions & speed of the database s response to the tmanager s transactions, which can be affected by the database s configuration and maintenance, do have an impact on throughput

21 Softing Sales Contacts Scott Sibenac Jim Ralston Pete Desmarais Christophe Renard Regional Sales Western & Mexico Regional Sales Eastern US & Canada WireXpert Business Manager Regional Sales EMEA & Asia Pacific

22 Resources Softing US Web Softing US main website: To place an order Product information Knowledge Base Service Request Phone & FAX In the US: International: FAX: Address Softing Inc Chapman Hwy Knoxville, TN Rockwell Web Softing s Encompass Listing Knowledge Base (Softing reposts many Knowledge Base articles in Rockwell s Knowledge Base)