Presentation on theme: "Studio 5000 Engineering and Design Environment"— Presentation transcript:
1 Studio 5000 Engineering and Design Environment V21 Highlights
2 Introducing Studio 5000 Engineering and Design Environment -PRESENT-Logix Designer (V21)Programming and configuration for Logix controllers.Existing RSLogix 5000 user interface retained with new shared components.-FUTURE-View Designer (V22)Graphical design environment for View 5000 HMIs.New User Interface.Studio 5000 is the first evolution of our Engineering and Design EnvironmentStudio 5000 is a modular framework for engineering collaboration with plug-ins for specific engineering tasks such as Logix Designer for control code development, and looking forward to View Designer for HMI development and additional plug-ins like Library Manager, Motion AnalyzerStudio 5000 creates the Automation Environment for Standard, Premier and Optimal experiences.
3 Logix Extended Tag Properties Decreased Troubleshooting Time & Faster Time to MarketT101.LevelSingle tag reference can obtain the all exposed and referenced instruction dataVisible Parameters as members of the instruction tagExtended Tag data associated with membersAbility to add additional data around a specific tag, without having to create a UDT – add info to actual properties of the tagCan write code against the min and max values; controller does not enforce the values directlySimplify your Logix applicationNo need to create custom data structures for commonly used tag informationDevelop your application faster and reduce errorsUse Min/Max tag limits programmatically, or propagate to third party HMI after moving to a local tag.
4 Extended Tag Properties: Value for Machine/Equipment Builders Faster time to market with more efficient developmentCreate tagEnable choicesTank_LevelAuto-Generated=DevelopmentTimeProfitabilitySingle tag reference can obtain the all exposed and referenced instruction dataVisible Parameters as members of the instruction tagExtended Tag data associated with members
5 Extended Tag Properties: Value for End Users Faster Troubleshooting with Standard Naming ConventionsTroubleshooting withExtended Tag PropertiesFaulted 3:00 amNon-Standard NamingMaintenance Costs.LevelExtended Tag Properties (Standard Naming)Less CostMore UptimeMore CostMore DowntimeThe Example above illustrates that using non-standard or disparate naming convention can lead to extended downtime when data is hard to find. Using Extended Tag Properties helps to standardize naming conventions allowing for less confusion and less downtime.Single tag reference can obtain the all exposed and referenced instruction dataVisible Parameters as members of the instruction tagExtended Tag data associated with members
6 Pre-V21 Project Documentation Storage Comments/Descriptions Stored on PCL6 ControllerUser Memory (Volatile/RAM)CPUEngineering PC “.ACD”Comments/DescriptionsRungTagUDTAOITaskProgramRoutineThis slide shows the current state of documentation and comments residing on the PC.Rung comments, descriptions, all project documentation lives inside the controllerDo not have to take .acd file everywhere –Only thing not in the controller program right now is the trendCommentsDescriptions
7 New V21 Project Documentation Storage Reduce File Management EffortsL7ControllerCPUUser Memory (Volatile/RAM)New Memory(Non-Volatile)L6 ControllerCPUUser Memory (Volatile/RAM)Engineering PC “.ACD”Significant improvement in revision management with controllersSimplified Multi User Project DevelopmentEasier Project MaintenanceRung Comments. All descriptions (Routines Programs/Task/Tag/UDT/etc)Exception to this is trends and trend comments.**Reminder** As with V21, this is in L7x, L1ER, L2ER and L3ER controllers.CommentsDescriptionsAlarm Log 10K AlarmsExtended Tag Properties
8 New Non-Volatile Extended Memory ControllerCPUNew Memory(Non-Volatile)User Memory (Volatile/ RAM)Storage is completely independent of user memory spaceNew non-volatile memory storage space is independent of the user memory.Note- If min/max data is accessed programmatically, user memory will be consumed.Extended tag properties, rung comments, descriptions, etc live in a new nvs memory area – extended memory space that does not take away from your user memoryNot added to project storage - 8 meg program still uses 8 meg of controller space
9 User Memory (Volatile/RAM) Project Documentation Storage: Value for Machine Builders and End UsersL7ControllerCPUUser Memory (Volatile/RAM)New Memory(Non-Volatile)Improved Maintenance Response Time (End User)Improved Revision ManagementEasier project maintenanceComments/Descriptions are Always AvailableFaster Time to Market (OEM)Multi-user DevelopmentNo Risk to Losing Project DocumentationSignificant improvement in revision management with controllersSimplified Multi User Project DevelopmentEasier Project MaintenanceRung Comments. All descriptions (Routines Programs/Task/Tag/UDT/etc)Exception to this is trends and trend comments.**Reminder** As with V21, this is in L7x, L1ER, L2ER and L3ER controllers.
10 Updated FT A&E Alarm State Model Simplifies application creation to easily follow ISA 18.2 recommendationsISA S18.2 Alarm State Transition DiagramFT A&E vs. ISA 18.2 terminology:Shelve = ShelvedSuppress = Suppressed By DesignDisable = Out Of ServiceSlide take away is Following ISA 18.2 alarming standard.Put alarms and events in the controller – HMI points to the controller and gets all the alarming infrastructure, etcDon’t have to do anything at the HMI level except point to the controllerOnly works with our controllers and HMI, so won’t get it if using someone else’s HMIISA state modelSource: International Society of Automation. (2009). ANSI/ISA Management of Alarm Systems for the Process Industries. Research Triangle Park: ISA
11 Shelving Function for Alarms Reduce Costly Mistakes by Assuring Alarms are NoticedIN ALARMShelvedThis slide shows how the shelving function is analogous to a snooze function.Click to Shelve
12 Selectively Apply Duration to ALMA Increase Productivity by Eliminating Nuisance AlarmsHigh LimitHigh High LimitTimeTemperatureMin Duration To TriggerIn V21, minimum duration can be applied to all or selected limits in the ALMA instruction. Minimum duration is the time that the limit must be held for the event to be realized.In a V20 if user wants to use the Minimum Duration function, the function applies to all limits. This is a concern if the user wants this function applied to less critical alarm limits such as High and Low, but requires instant notification on more critical alarm limits such as HighHigh and LowLow.
13 New Controller Based Alarm Log High Availability of Alarming Data Reduces Material LossesAlarmLog=Communications LossFactoryTalk View 6.x and 7.xCircular File Stores Alarm TransitionsThis function utilizes the non-volatile space on the controller.It is circular file which stores up to 10K alarms in L7x, 5K in L3, 5K in L2 and 2.5K in L1 CMX.Historical log embedded on the controller
14 Expanded FT A&E System Limits Scale to Larger ApplicationsExpanded FTA&E Limits in FactoryTalk View 7.0ServersCurrent Tested LimitsFactoryTalk View 7.0 TargetFT A&E Servers (Non-Redundant)2 Servers10 ServersFT A&E Servers (Redundant)2 Server Pairs10 Server PairsFT View Servers (Non-Redundant)FT View Servers (Redundant)5 Server PairsEliminates barrier that may have led to use of HMI Classic AlarmingMore servers enable logical segregation of FT A&E servers by processing areaClientsCurrent Tested LimitsFactoryTalk View 7.0 TargetFT A&E Clients20 Clients50 ClientsFT View Clients
15 Controller Support Roadmap V20 is in extended maintenance mode V20 will be in Extended Maintenance Mode for some time.V20 is the last version to allow selection of and creation of these controllers. No V21 firmware is available for these controllers.V20 is in extended maintenance mode
16 Operating System Support Operating Systems Supported in V21:Windows 7 Professional SP1 32 bitWindows 7 Professional SP1 64-bitWindows 7 Home Premium SP1 32 bitWindows 7 Home Premium SP1 64-bitWin2K8 Server Standard R2 SP1 (64-bit)Knowledgebase Answer ID 67020“RSLogix 5/500/5000 on Windows Vista and Windows 7“
18 EtherNet/IP CIP Motion Encoder Eliminate Extra Wiring and ComplexityEtherNet/IP DLR support18 bit resolutionSingle-turn and multi-turn absolute842EM-S842EM-MIP67 Packaging, M12 connectorsSolid and Hollow shaft optionsCIP Motion Feedback Only axis supportUse as master axis for gear, PCAM, MDSCProvides a master axis solution when using the Kinetix 350 drive or Kinetix 5500 driveProvides CIP Motion feedback only axis solution for the Kinetix 350 and Kinetix 5500 servo drives for ControlLogix and 5370 CompactLogix controllersFeedback only axis is required in many applications where non-controller master axis feedback is required for Gear, PCAM, and Master Driven Speed Control motion move support
19 High Performance Position Driven Outputs (PLS) More points per Output Cam from 8 to 16Position based output controlMAOC motion instruction with RSLogix graphical profile editorMap to any output - boolean or physicalAdvanced PLS featuresOutput Cam Function in CompactLogixBenefitsAny axis can control outputs using position & velocityPhysical or virtual axesMultiple output module optionsStandard outputsOutputs with CIP Sync for high performance1756-OB16IS - 8 outputs/module1756-OB16IFS - 16 outputs/module1732E-OB8M8SR – 8 outputs /moduleEtherNet/IP DLRUse with ControlLogix or CompactLogixHigh performance PLS support with local (ControlLogix) and distributed (ControlLogix, 5370 CompactLogix) outputs – up to 50us resolutionMaximum flexibility…..any virtual axis or CIP Motion drive can be mapped to any output for PLS functionality1732E-OB8M8SR is the only option for PLS support with 5370 CompactLogix
20 Kinetix 5500 CIP Motion Servo Drive Lower Installation Costs50% less cabinet space70% fewer wiring terminations60% less cable runs requiredVPL Servo motor single cable connectionFlexible Machine ArchitectureSingle or Multiple Axis configurationsShared AC/DC Bus configurationsServo or V/Hz – Induction and PM motorsEmbedded switch DLR supportMeets Global Machine StandardsVAC Input VoltageHardwired Safe Torque Off1A to 23A continuous
21 Kinetix VPL Servo Motor Single cable27% lower cable cost 60% less wiringWindings options matched to drive ratings allow for optimized system sizing and costsNM Continuous Torque RangeFlat speed/torque curves deliver twice as much power at high speeds delivering 20% savingsIntegrated Mechatronic functions simplify commissioning and reduce operational costsEnergy efficient drive/motor match and green shunt50% less energy15% lower costsBased on proven magnetic core MP technology for market leading reliability and performance
23 Introducing ControlLogix Peer-to-Peer I/O Expanded Application Capabilities1756-OB16IEF1756-LSC8xIB8I1756-IB16IFThe latest additions to the ControlLogix family of I/O offer significantly improved performance, increasing production capacity and minimizing system response time.A total of 3 new modules offer individual benefits but, when used in combination, provide peer-to-peer I/O control with nominal screw-to-screw speed < 100µS, independent of the controller.Increase speeds to capture new eventsIncreased scan timePattern matching event tasks – reduce code space
24 What is Peer-to-Peer I/O Control? Peer-to-Peer I/O Control is output actuation based on input data, independent of the programmable automation controller (PAC).Throughput speeds are drastically reduced as outputs are turned on and off without intervention from the PAC. Here’s how it works:The input module is configured to “produce” dataThe output module establishes a connection to the input moduleThe output module “listens” for the data the input module is producingThe output module energizes outputs when it “hears” the required parametersHow it works:the input module is configured to “produce” datathe output module establishes a connection to the input modulethe output module “listens” for the data the input module is producingthe output module energizes outputs when it “hears” the required parametersALL COMPLETELY INDEPENDENT OF THE PROGRAM.SO, P2P I/O Control will alleviate the controller’s responsibility of that execution of code.It is handed over to the IO Modules for faster throughput as well as eliminating transport lags for transfer into the PAC.ConfigurationInput Module produces dataController InfoOutput
25 * Example Use Cases: Peer-to-Peer I/O Control Peer control allows outputs on the 1756-OB16IEF module to energize within 50µS of input peer pre-conditions being met.Max # of PulsesPer Cycle LimitGlueApply Glue NowSensorGlue Gun ControlTrigger an Event Based TaskSingle Input OR a Combination of InputsVariable Pulse train to HeatingElement from PID CalculationTemp Feedback to Analog InputHeated VesselTime-Proportioned Control Applications*SSimple Flowmeter / Solenoid Valve ControlWhy would we need this and What applications could benefit from this advancement?Examples:Filling Lines where counting and execution is critical (Very speed)Glue Gun applications where edge detection is critical at high speeds and very quick decisions need to be madeConfigurable Cycle Limit feature that helps prevent “Globbing” in the event of line stoppage.Time Proportioned Control ApplicationsProvides a PWM On Time and Cycle TimeHigh Speed Parts Reject or Select applicationsMust Detect then React at a high speedTake AwayAlleviate the Processor lag time for executing logic and hand it over to the IO.All of these can be solved at the I/O Module Level utilizing P2P control.
27 New CompactLogix Controllers Scalable Controllers to Best Meet Application NeedsL3L2New ER controllers are better scaled to provide a clear and simple product selection5 simple criteria; Memory, Embedded IO, # of local IO expansions, and two new limits # of Ethernet nodes on RSLogix5000 I/O Tree and Motion Axis supported (Position loop only)Memory ranges from 384KB to 3MBEmbedded IO, selection of brick style or modular controller, purely digital or combination of analog and High speed counterNumber of Local IO Expansions.Number of EtherNet/IP Nodes on RSlogix5000 IO tree. What these means will be discuss in the new few slidesLastly Motion axis supported for position loop only ranging from 2 axis to 16 axis. We will have detail explanation of what this is later.Clear & Simple Product SelectionL1Integrated Motion with L1,L2,L3
28 Simple and Consistent Scaling CatalogMemoryEmbedded I/O# of local IO Expansions# of EtherNet/IP Nodes on I/O TreeMotion Axis supported (Position)1769-L16ER-BB1B1769-L18ER-BB1B1769-L18ERM-BB1B1769-L24ER-QB1B1769-L24ER-QBFC1B1769-L27ERM-QBFC1B1769-L30ER1769-L30ER-NSE1769-L30ERM1769-L33ER1769-L33ERM1769-L36ERM384KB512KB750KB1MB2MB3MB16 IN/16 OUT16 IN/16 OUT/4 AI/2 AO/4 HSC-684163048163248-24816New ER controllers are better scaled to provide a clear and simple product selection5 simple criteria; Memory, Embedded IO, # of local IO expansions, and two new limits # of Ethernet nodes on RSLogix5000 I/O Tree and Motion Axis supported (Position loop only)Memory ranges from 384KB to 3MBEmbedded IO, selection of brick style or modular controller, purely digital or combination of analog and High speed counterNumber of Local IO Expansions.Number of EtherNet/IP Nodes on RSlogix5000 IO tree. What these means will be discuss in the new few slidesLastly Motion axis supported for position loop only ranging from 2 axis to 16 axis. We will have detail explanation of what this is later.
31 ControlLogix 557xS Integrated Safety Safety FeaturesExisting GuardLogix functionalitySafety Task 1756-L6xS functionalityAll safety and safety application instructionsAll existing GuardLogix safety certificationsIEC 61508, IEC 62061, ISO 13849, etc.Controller Options1756-L72S = 4MB standard / 2M Safety1756-L73S = 8MB standard / 4M Safety
32 New Redundancy Module 1756-RM2F More Application Options & Faster Machine ThroughputFeatures and BenefitsHigher Data Throughput Rates – Less Cross Loading time means less scan time impact1 GB fiber speeds – Faster Cross Load SpeedsRedundant Fiber Channels – No single point of FailureEnhanced Diagnostic Display (Used with RM Configuration tool) – Less time spent troubleshooting in the event of an issue
33 ControlLogix XT & ControlLogix SXT 1756-A7XTNew higher density XT chassis (7-Slots)Same physical size as 1756-A10 and 1756-A5XTUse with existing Logix-XTNo software update required1756-L73XT / -L73SXT (8MB) Logix-XT controllerShares all characteristics of existing Logix-XT modulesNo software update required - Standard L7x firmware
34 Performing a System Upgrade or Creating a New System Customer upgrades a system component (e.g., moving from V16 to V17)What other devices must be upgraded?Controller moving from V16 to V17Graphical representation of why the following tool may be required.What other devices in the system are affected?Are other softwareupgrades needed ?Will this break any part of the system?
35 New Compatibility Management Web Site Reduce Time to Market and Mitigate RiskIdentifies compatibility of firmware versionsEasier to locate downloadsEasier to locate release notes or other companion documents.New tool with solid infrastructure, data is continuing to be updated and added.
36 Logix Connector Enhancements – VantagePoint Reduced engineering timeSimplified connectivity to Logix platformsIncreased ease of useLive Data Import wizard brings in structures from Logix platformsIf a matching type definition does not already exist, a type definition is created to match the UDT definition in the controllerTag instances are then created for each tag in the controller that uses that definitionDynamic Object Creation – When using the Live Data Import wizard bring in structures from the Logix platform, you now have another dialog to select which UDT structures to bring in. When the wizard is executed, if a matching type definition does not already exist, a type definition is created to match the UDT definition in the controller. Tag instances are then created for each tag in the controller that uses that definition. Thus you no longer need to define the type package in advance and set the Import rules to bring structures into the model. Quite an improvement! Now for the caveat. This feature works one on one with a controller. If two controllers use the same UDT definition, they will each have their own type definition.