We think you have liked this presentation. If you wish to download it, please recommend it to your friends in any social system. Share buttons are a little bit lower. Thank you!
Presentation is loading. Please wait.
Published byVirginia Finkley
Modified over 2 years ago
© 2013 SPiiPlus Training Class Safety and Faults 1
© 2013 Faults Mechanism 2 All fault responses can be customized by the user Fault: An abnormal situation detected by the controller related to safety of motion, hardware damage, faulty wiring, EtherCAT errors, limit switch tripped, etc. Faults and errors are monitored every controller cycle. The controller has a predefined set of faults and default responses.
© 2013 Faults Mechanism Example faults: o Encoder error due to bad wiring o Drive alarm caused by problem with the power amplifier o Axis limit switch tripped o E-Stop activation o Critical position error caused by a driving axis into a hard stop 3
© 2013 Some Predefined Axis and System Faults 4 Axis Faults Right Limit Left Limit Soft Right Limit Soft Left Limit Encoder not connected Encoder error Drive Alarm Position Error Critical Position Error Velocity Limit Overcurrent System Faults Program error Memory overuse Runtime overload Servo Processor alarm Servo Interrupt Emergency stop
© 2013 Axis Fault Variables FAULT o Encodes all faults for a certain axis. For example, ON FAULT(1).#ENCNC will activate an autoroutine when axis 1 encoder is disconnected. FMASK o Masks a defined axis fault. For example, FMASK(0).#RL=0 will mask axis 0 hardware right limit fault. FDEF o Activates/deactivates default response to axis fault. For example, FDEF(3).#SLL=0 will disable the default response to axis 3 software left limit fault. 5
© 2013 System Fault Variables S_FAULT o Aggregates one specific fault for all axes. For example, ON S_FAULT.#LL will activate an autoroutine when any axis passes the left limit. S_FMASK o Masks a defined system fault. For example, S_FMASK.#ES=0 will mask the Emergency Stop fault. S_FDEF o Activates/deactivates default response to system fault. For example, S_FDEF.#ES=0 will disable the default response to the Emergency Stop fault. 6
© 2013 Customized Fault Responses The user can define a customized fault response that can override/supplement the default fault response by: o Activating the fault FMASK variable o Writing an autoroutine, for example: ! Axis 0 critical position error is being checked FMASK(0).#CPE = 1 FDEF(0).#CPE = 0 STOP ON FAULT(0).#CPE; BLOCK ! Run on critical position error KILL (0,4) ! Kill axis 0 and 4 START 3, User_PE ! Run buffer 3 starting at label User_PE DISP "Critical position error Axis 0" END; RET 7
© 2013 Safety and Faults Configurator 8 MMI component used for configuration of controller responses to faults Red LED indicates a fault Allow default fault response Allow detection of fault Invert fault signal (if necessary)
© 2013 Safety and Faults Monitor 9 Provides immediate monitoring of axis and system faults
© 2013 Default Responses The controller provides default responses for most faults A default response can be one of the following: o No response – for indication only. o Kill motion – when the axis is under control o Disable motor – when the controller can’t control the axis o Kill Disable – Kill motion followed by disable 10
© 2013 Default Responses To view default responses: o In the System Information Viewer, look under “Safety & Fault Response” heading to view predefined fault responses per axis o Alternatively, the terminal command #SC prints the same information to the Communication Terminal 11
© 2013 Fault Mechanism 12
© 2013 Fault Mechanism 13 Example 1 – Axis 0 left limit fault
© 2013 Fault Mechanism 14 Example 2 – Axis 0 left limit fault
© 2013 Encoder Faults Encoder Not Connected o Quadrature encoders: Checked by HW to verify continuity between A/A’ and B/B’ on quadrature encoders o Analog Sin-Cos encoders: Checked by SW using Sin^2 + Cos^2 Encoder Error o Checks encoder logic by the SW (Firmware) to verify legal transfers between A and B signals ( ) 15 FaultQuad EncoderSin-cos Encoder Encoder not connected Encoder Error
© 2013 Hardware Limit Faults During operation, when the left limit switch is on, the controller detects a left (negative) limit fault. During operation when the right limit switch is on, the controller detects a right (positive) limit fault. As a default response, the controller kills the violating motor. As long as the fault is active, the controller kills any motion toward the limit while motion away from the limit is allowed. 16
© 2013 Software Limit Faults The user can define left and right software limits in the Adjuster Wizard: Unlike hardware limits, the software limit causes the fault before the trajectory passes the software limit position The controller provides processing so the termination point is very close to software limit – using the KDEC deceleration variable 17
© 2013 As long as the fault is active, the controller kills any motion toward the limit while motion away from the limit is allowed Software Limit Faults 18
© 2013 Velocity and Acceleration Limits Maximum reference (not feedback) velocity (XVEL) and acceleration (XACC) can be specified for each axis. Calculated automatically by the Adjuster Wizard based on motor data entered earlier in the Adjuster process Can be specified by user if necessary 19
© 2013 Important – the velocity limit (XVEL) parameter affects the servo control loops because it scales velocity feedback. Make sure XVEL is set properly before tuning. Velocity and Acceleration Limits When the commanded motion exceeds the maximum velocity value, a FAULT.#VL fault is generated. When the commanded motion exceeds the maximum acceleration value, a FAULT.#AL fault is generated. 20
© 2013 Current/Torque Protection There are three current/torque protection variables defined in terms of percentage of peak drive current: o XRMS – defines maximum allowable RMS current. If violated, an overcurrent fault occurs. o XCURI – defines absolute maximum current when axis is idle. This sets a physical limit on drive output. o XCURV – defines absolute maximum current when axis is in motion. This sets a physical limit on drive output. 21
© 2013 Current/Torque Protection Overcurrent protection o The controller provides over-current protection by calculating RMS current o The protection relates to continuous current rating of drive and motor o The Adjuster Wizard automatically calculates current protection parameters based on motor and drive data entered earlier in the Adjuster process o Current protection parameters can be modified by users if necessary 22
© 2013 Current/Torque Protection 23
© 2013 Position Error Faults There are six variables for position error faults As a default response, the critical position error fault disables the drive The position error fault has no default response (indication only). The user can define a customized response. 24
© 2013 Error Mechanism A four-digit error code is generated after any malfunction during operation. The controller returns error codes which belong to the following categories: o ACSPL+ Syntax Errors: numbers 1000 to 1999 o ASCPL+ Compilation Errors: 2000 to 2999 o ACSPL+ Runtime Errors: 3000 to 3999 o Motion Termination Errors: 5000 to 5150 o System Errors: 5151 to 5999 o EtherCAT Errors: 6000 to 6999 o Reserved for user-defined error codes: 9000 and above 25
© 2013 The meaning of an error code can be determined by o Looking up the error code in section 5 of the ACSPL+ Command and Variable Reference Guide o Querying the error code in the Communication Terminal using double question mark syntax For example; ??5167 returns “Initialization problem: Number of drive modules does not meet the configuration” If an error occurs when using the MMI, a pop up window displays the error code along with its meaning. Error Mechanism 26
© 2013 Error Mechanism MERR is an ACSPL+ standard variable that stores motion termination cause per axis If axis motion terminates without error, MERR returns 0 If axis motion terminates with error, MERR returns the corresponding 4-digit error code in the range of
© 2013 Error Mechanism PERR is an ACSPL+ standard variable that stores ACSPL+ error code (progam error) per program buffer If an ACSPL+ error occurs during program execution, the controller stores the error code in the corresponding element of the PERR array 28
© 2013 Error Mechanism In addition to the SPiiPlus error codes, the user can add their own codes in the range of 9000 and above. For example: ON (RPOS(axis) > 10000) ! Condition for error KILL (axis), 9123 ! Kill motion citing error code 9123 DISP "Cause of motion termination", MERR(axis); FCLEAR(axis)! Reset MERR flag of the axis RET 29
© 2013 EtherCAT Diagnostics EtherCAT diagnostic commands allow you to view connected EtherCAT network nodes, operational state, network offsets (variables), errors, etc. o There are three diagnostic commands: o #ETHERCAT – A terminal command showing connected EtherCAT nodes, corresponding states, and variable offsets o ECST – Shows the status of the EtherCAT network. All bits should be on with the possible exception of bit 4 (synchronization bit) if using 3rd party IO. o ECERR – Gives an error code that can be sent to ACS Support for troubleshooting purposes. If zero, no errors exist 30
© 2013 Example 1 A vision system moves a scanner head along a single linear axis Safety and faults need to be configured for the axis If the scanner head moves into the limit, it is important not to remain there due to hazards Turn off the default response to limits for the axis and define new response so the scanner head does not stay in the limit 31
© 2013 Example 1 Load Safety and Faults example 1 to an empty buffer, review code, and execute. o If using trainer unit, command motion and manually toggle limit switches o If using simulator, command motion and simulate limit switches by toggling. SAFINI(X).#LL, or SAFINI(X).#RL 32
© 2013 Example 2 The vision system needs to wait for a signal from the user before it is allowed to continue operation Modify example 1 so that after moving out of a limit, code execution halts until user sends a signal from the terminal (i.e. user changes the state of a global variable from the terminal) Use the terminal to notify the user of any safety issues (use DISP to display messages to the Terminal), and prompt for user input when necessary 33
© 2013 Example 3 For safety purposes it is desired to disable all axes and stop the program if the user does not send a signal for an extended amount of time Modify example 2 accordingly, define an appropriate user-response timeout length 34
© 2013 SPiiPlus Training Class MC4U Trainer Setup 1.
© 2013 SPiiPlus Training Class Motion Profile Generation 1.
© 2013 SPiiPlus Training Class Single-Axis Motion 1.
© 2013 SPiiPlus Training Class Homing. © 2013 Homing Homing is a very important aspect for almost any motion system. With a wide variety of mechanical.
VMware vCenter Server High Availability Product Support Engineering VMware Confidential.
1 BACKGROUND ALARM SYSTEM OF ZXJ10 Training Center Zhongxing Telecom Pakistan (Pvt.) Ltd.
SK-NET™ 4.0 Tutorial SK-NET™ is a Windows® based software program designed to monitor and control a network of Secura Key SK-ACP 2-door control panels.
SK-NET Tutorial SK-NET is a Windows® based software program designed to monitor and control a network of up to 100 Secura Key SK-ACP 2-door control panels.
© 2010 InHand Electronics, Inc. – Troubleshooting Linux Performance and Battery Consumption Issues Dave Stewart Director of Software Engineering.
1July 2007 Uniflair UG40 / MP40. 2 General features The graphic user interface is composed of: Back-lit LCD Display : 132 x 64 pixel screen with acoustic.
SpiderAlert Software Training June This list covers the basic steps to follow when designing a new project: Install Software Install new DLLs.
WINDOWS XP. Startup and Shutdown Boot Process Start with the installation of Windows XP and proceed through the execution of Ntldr and Ntdetect. Device.
The I 2 C Bus. 2 of 40 The I 2 C Bus What is the I 2 C Bus and what is it used for? Bus characteristics I 2 C Bus Protocol Data Format Typical I 2 C devices.
Lenel Command Keypad LNL-CK Hardware and Software Configuration Slide 1 of.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 13Slide 1 Chapter 13 Real-time Software Design.
Dive into WebRatio 6 BPM Milano, 09/11/2013 WebRatio Customer Services.
Computing Higher - SD Process – Topic 2 St Andrew’s High School Unit 2 Software Development Process.
1 Process Description and Control Chapter 2. 2 Process A program in execution An instance of a program running on a computer The entity that can be assigned.
2 Welcome To Defect Management Training Objective: The objective of this course is to learn about standards that emphasize a best practice approach for.
Silberschatz, Galvin and Gagne ©2010 Operating System Concepts Essentials – 8 th Edition Chapter 16: Windows 7.
PCI Bus CENG Spring Dr. Yuriy ALYEKSYEYENKOV 2 The PCI (Peripheral Component Interconnect) bus was developed as a low-cost, processor-independent.
Chapter 20- Embedded Systems Lecture 1. Topics covered Embedded systems design Architectural patterns Timing analysis Real-time operating systems.
© 2007 – 2010, Cisco Systems, Inc. All rights reserved. Cisco Public ROUTE v6 Chapter 5 1 Chapter 5: Implement Path Control CCNP ROUTE: Implementing IP.
1 Chapter 11 I/O Management and Disk Scheduling Patricia Roy Manatee Community College, Venice, FL ©2008, Prentice Hall Operating Systems: Internals and.
Routers and Routing Basics CCNA 2 Chapter 7.
The ESC-QuickBooks Integration For Use with ESC Version 12.
1 Basis: HESHBON update: RR HESHBON HA-710 Wheel Alignment System Fahrwerksvermessungs-System Service Manual Service-Handbuch (Ver.1.0.
Robonova-1 Instruction Manual v1.5 Written by Meena Seralathan.
SG 4: FIT1001 Computer Systems S Important Notice for Lecturers This file is provided as an example only Lecturers are expected to modify / enhance.
Fundamentals of Bus Bar Protection GE Multilin. 2 GE Consumer & Industrial Multilin 2-Jun-14 Outline Bus arrangements Bus components Bus protection techniques.
© 2016 SlidePlayer.com Inc. All rights reserved.