MP940 Machine Controller

MP940 Machine Controller - YAI

Single-axis; 115, 240, 480 Volts

The MP940 Machine Controller is a legacy product and no longer promoted in the Americas. (The retrofit/upgrade to the MP940 is the MP2000iec product family, specifically the MP2600iec is a machine controller module fully integrated in to Yaskawa's latest Sigma-5 Series Amplifier. The MP940 Machine Controller series was a single-axis controller and a member of Yaskawa's MotionSuite family of electronic machine controllers. The modular packaging of the MP940 provides integral mounting with Sigma II drives from 30 watt to 55kW, with voltages of 115, 240 and 480 volts.

TemplateWeb

Support & Training

Documents

Manuals

Support & Training

Documents

FAQs

Sort by :

Expand All

Didn't find what you were looking for? Try solutioncenter.yaskawa.com

Showing 21 to 30 of 79 entries.

Previous Page
Page1
Page2
Page3
Page4
Intermediate Pages
- Page5
- Page6
- Page7
Page8
Next Page

Question	Posted Date
What is a "DWG" (drawing)? Posted Date: 05/02/2001 Answer: "DWG" is an abbreviation of "drawing", which is a thread of ladder logic. Drawings form the ladder program for an MP9xx controller. Each drawing can contain a maximum of 500 steps. There are 3 different types of drawings: 1. DWG.A- Executed only once at power up 2. DWG.H- Executed once every High-Speed scan cycle (this cycle time is set by High-Speed scan time) 3. DWG.L- Executed once every Low-Speed scan cycle (this cycle time is set by Low-Speed scan time) They are organized like a family of three generations. A parent drawing (i.e. 'H') is automatically executed by the CPU. Child generations (i.e. 'H01') are executed by being called by the parent drawing with a 'SEE' instruction. Grandchild generations (i.e. 'H01.01') are called by child drawings in the same way. Only a direct descendant of the same family can be called. A parent drawing can not call a grandchild drawing directly, and a drawing can not call drawings of another family (i.e. DWG.H01 can not call DWG.H02.01). Each drawing family will be executed every scan cycle. If there are too many steps in the family of drawings to execute in the allotted time, an error will occur. Increasing the appropriate scan time will prevent this situation. The attached file shows the structure for calling drawings Attachments: 11KB Product Group/Line: Controllers, MotionWorks Software, MP920 Machine Controller, MP930 Machine Controller, MP940 Machine Controller Topic/Sub Topic: Ask a Technical Question, Document Clarification, Programming, Specifications Document Number: MNEN-5CJMMG Published Date: 05/02/2001 Share \| Rate Rate this article :	05/02/2001
What I/O cable options are there for the MP940? Posted Date: 11/29/2004 Answer: There are three options. Option #3 is NEW in 2001: Use pigtail (flying lead) cables. Part number for this option is JZSP-CKI01-XX(A), where XX is cable length in meters: Lengths available are 01, 02, or 03 meters. This option requires two cables to configure a system; one cable for the 1CN on the SGDH and another for the I/O port on MP940. Use terminal block + connector cable assembly. Part number for this option is JUSP-TA50P. Cable length is 0.5 meters. This option requires two JUSP-TA50P's to configure a system. The terminal blocks make wiring to the host controller quick and easy. Use cable assembly with D-SUB output for 3rd party. Part number for this option is CKI-MP940D-XX (rev 2). Lengths available are 0.5, 01, 02, or 03 meters. This is a NEW option introduced in Sept. of 2001. This cable is configured as a "Y" or "two headed" cable. One leg of the "Y" plugs into the amp's 1CN and the other into the I/O port on the MP940. Both terminate on the other end into a single 50 pin D-SUB connector. All 50 pins of the D-SUB are used when combining the I/O (many conductors are not used when the traditional two cable route is chosen). This D-SUB connector allows the customer to specify a 3rd party terminal block of their choice while cutting wiring time in half vs. the pigtail arrangement. For customers who have access to terminal blocks at a volume discount, this option offers substantial cost savings over the JUSP-TA50P. Specify 500 mm, 1m, 2m, or 3m length. For further information on this cable, refer to the CAD DWG or PDF file below. A partial list of suitable terminal blocks is also provided. Explanation of Attached Files: CKI-MP940D-XX (rev 2).dwg Autocad Drawing of the "Y split cable" CKI-MP940D-XX Fixed.pdf Autocad file in pdf format Suitable 50 pin D-Sub MALE terminal blocks.xls Alternative terminal block part numbers from Wago, Phoenix, Weidmuller, Amphenol MP940_SGDH_IO.xls List of pin/wire descriptions for "Y split cable" from SGDH and MP940 to terminal See additional CAD files by searching the following file names: Ys-15.dwg (Programming cable for MP940) CKI-MP940D-XX (rev 2).dwg (I/O and CN1 Cable) Ys14.dwg (Port 2 interface cable with flying leads). Attachments: 30KB 884KB 447KB Product Group/Line: Controllers, MP940 Machine Controller Topic/Sub Topic: Ask a Technical Question, Hardware, Applications, Wiring Document Number: MNEN-5CJMPJ Published Date: 11/29/2004 Related Files: What I/O cable options are there for the MP940? CAD Drawing: CKI-MP940D-XX: MP940 I/O Cable, D-Sub Output Share \| Rate Rate this article :	11/29/2004
What are the steps to set up a Mechatrolink or DeviceNet Network on an MP940 with MotionWorks+? Posted Date: 07/13/2004 Answer: The attached technical note outlines the details in assigning and the setup of Master and Slaves in a MP940 Network System using MotionWorks+. Two different network protocols are available for use with the MP940: Yaskawa's deterministic high-speed network called Mechatrolink, and ODVAs open device network called DeviceNet. Mechatrolink is used as the primary example. However, the setup from MW+ is virtually identical when applying DeviceNet. All nodes that are connected in the network must use the same protocol with only one Master (MP940 has the ability to be setup as a Mechatrolink or DeviceNet Network Master). In both cases, the MP940 only supports network I/O in a Polled I/O fashion. Attachments: 380KB Product Group/Line: Controllers, MotionWorks Plus Software, MP940 Machine Controller Topic/Sub Topic: Ask a Technical Question, Network Communications, Procedure - Policy, Start Up - Installation Document Number: MNEN-5CJMFW Published Date: 07/13/2004 Share \| Rate Rate this article :	07/13/2004
What are the recommended programming practices when using function blocks? Posted Date: 09/06/2004 Answer: The following are some recommended programming tips when using function blocks: 1. Function Blocks causing motion must be used in the 'H' drawings. 2. When creating 'H' drawings, allocate enough D registers before inserting the function blocks. (Drawing properties) 3. Ensure that function blocks within the same drawing are not sharing D registers. 4. Include RADinit1 and RDAinit2 in the 'A' drawings for every axis commanded by function blocks. 5. Cycle control power after compiling 'A' drawings. 6. In Multi-axis applications, use the AXISEND function block. All axes related function blocks must be inserted between the SVON and AXISEND function blocks. 7. Take into account the function block dependencies, i.e. function blocks that work together: SVON & AXISEND, CHNG_DYN & MOVE blocks, MOD_ENG & CAM, JOG & STOP, etc. 8. Use the ALARMRST function block to reset SVON errors (after eliminating the cause) and to clear the Error ID register (MW**81). Product Group/Line: Controllers, MotionWorks Software, MP920 Machine Controller, MP930 Machine Controller, MP940 Machine Controller Topic/Sub Topic: Ask a Technical Question, Software Document Number: MTN-5WKP9C Published Date: 09/06/2004 Share \| Rate Rate this article :	09/06/2004
What are the possible causes of communication failure between an HMI and a MP9xx controller? Posted Date: 05/03/2001 Answer: Yaskawa has prepared start-up guides for many of the popular HMI products on the market today. These start-up guides are very helpful during startup. The MP products have port communication lights that blink rapidly when the MP product and the HMI are communicating properly. If HMI communications cannot be established, investigate the following possibilities: 1) Ensure that the Memobus driver is installed in the proper directory and selected in the HMI Programming software. 2) Check the cable wiring, testing it pin for pin according to the wiring recommended in the Yaskawa start-up guide. With RS-422/485 communication, terminating resistors may be needed. Try removing the termination resistors if they are part of the circuit, or adding them if they were not. The success of terminating resistors sometimes depends on the characteristics of the cables used. 3) Check the digital ground and field ground (shield) connections. Make sure that the digital and field ground are separated. Follow the grounding/shielding recommendations in the start-up guide. 4) Check the communications protocol setting in both the HMI and the MP product (typically port 2). Select 19.2kBaud, Even Parity, 8 data bits, 2 stop bit, Memobus RTU transmission mode. 5) Make certain that the slave address is set properly. 6) Make sure the right MP series controller is selected. Some HMI products require this selection. 7) Verify that the active page on the HMI actually monitors/sets a valid MP register (any register MW/MB/MF/ML register within MW00000 thru MW32767). For more information regarding specific startup and setup information, please click on this FAQ link FAQ. Product Group/Line: Controllers, MP920 Machine Controller, MP930 Machine Controller, MP940 Machine Controller Topic/Sub Topic: Ask a Technical Question, Troubleshooting, Wiring Document Number: MNEN-5CJMML Published Date: 05/03/2001 Share \| Rate Rate this article :	05/03/2001
What are the differences between single-axis and multi-axis function blocks? Posted Date: 09/21/2004 Answer: To see the main differences between single-axis and multi-axis function blocks, please download the attached .PDF file with further information and illustrations. Attachments: 31KB Product Group/Line: Controllers, MotionWorks Software, MP920 Machine Controller, MP930 Machine Controller, MP940 Machine Controller Topic/Sub Topic: Ask a Technical Question, Programming Document Number: MTN-5WKPTA Published Date: 09/21/2004 Share \| Rate Rate this article :	09/21/2004
What are some potential causes of an A.E2 alarm? Posted Date: 06/24/2013 Answer: An A.E2 alarm is a watchdog timer alarm, caused by either an MP940 processor time-out or an MP940-SGDH communications synchronization error. Below are some remedies. 1. Excessive system noise - Be sure that the MP940 is grounded to the SGDH (MP940 FG connection on power connector to the SGDH screw terminal on the front side of heat sink with a 16awg short ground wire), and the SGDH is connected directly to the field ground ground bar in the cabinet. Verify that the SGDH is properly grounded. Verify that the subpanel / ground terminal is properly grounded. Make sure that the machine is properly grounded to a sufficient building ground. 2. SGDH Comm Synch Error (Insufficient 24VDC power or bad wire connection) 1) Control power on SGDH and MP940 must power ON within 3 sec of each other 2) Check Dual Port Ram connection between SGDH and MP940 3) Check the 24VDC power supply capacity (if it dips below 21VDC for the unit will automatically watchdog trip as a safety precaution and generate an A.E2 alarm to indicate to user that there is a power supply issue). If the error occurs at the same point in the program all the time, chances are that the program is controlling an output point that draws more current than the power supply is capable of. 4) Verify that all terminal screws that bond wires are securly tightened, sometimes an intermittent connection in the power supply can be caused by loose wires after shipping or moving a machine (vibration of the machine may also cause screws to loosen). 3. MP940 Processor Time-Out - Typically caused when actual H or L scan 'time' exceeds H or L scan 'setting' respectively. The H scan will deterministically execute the entire H program/drawing and sub programs/drawings every H scan setting time cycle. Higher priority background tasks will interrupt the execution, but the H execution must occur in its entirety within the H scan setting. Otherwise, an error will occur. Any remaining time is left over to perform lower priority tasks. Likewise, the L scan will also deterministically execute the entire L program/drawing and sub programs/drawings every L scan setting time cycle. Higher priority tasks will interrupt its execution (such as the H scan), but the L execution must occur within the L scan setting. Otherwise, an error will occur. Hence, if too much time is spent in the H scan, the L scan will be starved of time! As a program grows in size during development, and if this error occurs, most commonly the H scan time will need to be increased. In MW+, it will be necessary to perform a full compile/download for the new values to take effect and maintain after a power cycle. Troubleshooting a Processor time-out - Verify that mProgram_HighScan_Current (SW00005, units of ms/100) and mProgram_HighScan_Maximum (SW00006, units of ms/100) does not exceed the High Scan setting (an MP940 Property attribute in MW+). Note that due to programming differences, various sections of code may not be run under certain conditions. Therefore, it will be necessary to test all conditions so that the maximum scan value can be determined. Example: If mProgram_HighScan_Maximum starts to exceed 70 (0.7 ms) when the high scan setting is 1msec, it would be advisable to increase the high scan setting to 2msec or more as needed. 1) If that does not work, verify that mProgram_LowScan_Current (SW00011, units of ms/100) and mProgram_LowScan_Maximum (SW00012, units of ms/100) do not exceeded the Low scan setting). 2) Another method is prevention. Place critical tasks under high scan setting programs or drawings, and non-critical tasks under low scan programs or drawings. This logical separation also lends itself to good programming practices. View our MP940/MW+ Program Template for an example by viewing FAQ # MMIR-5CM5LM Product Group/Line: Controllers, Servo Products, MP940 Machine Controller, SGDH Sigma II Topic/Sub Topic: Ask a Technical Question, Alarm, Troubleshooting Document Number: MNEN-5CJMG6 Published Date: 06/24/2013 Share \| Rate Rate this article :	06/24/2013
What are some issues that would cause a web application to drift when using camming with registration, and what are some remedies to this condition? Posted Date: 07/13/2004 Answer: The slave (SGDH motor) on a web handling or similar system may drift for the following reasons: 1) Slave has a non-integer based machine cycle. 2) Master has a non-integer based machine cycle. 3) Cam calculations are flawed. Please see the attached Word file for detailed information about these conditions. Attachments: 16KB 105KB Product Group/Line: Controllers, MotionWorks Plus Software, MP940 Machine Controller Topic/Sub Topic: Ask a Technical Question, Application Example, Programming, Software, Troubleshooting Document Number: KHUL-5DUSAN Published Date: 07/13/2004 Share \| Rate Rate this article :	07/13/2004
Product Demo Documentation: MP940 Posted Date: 06/26/2013 Answer: This FAQ contains links to the supporting files for the MP940 demo. Search the document numbers below to locate your files. Vital Statistics* General: Demo Vital Statistics - Product and Tradeshow (Doc # GG.MCD.07.008) Demo Program Example Code: MP940 - MW+ Template Program (Doc # EC.MCD.03.514) Example Code Manual: MP940 - MW+ Template Program (Doc # EM.MCD.03.514) Schematics None available at this time. *Requires partner login Product Group/Line: Controllers, MotionWorks Plus Software, MP940 Machine Controller Topic/Sub Topic: Ask a Technical Question, Product Demo Document Number: MTN-6VYLY9 Published Date: 06/26/2013 Related Files: Example Code Manual: MP940 - MW+ Template Program Share \| Rate Rate this article :	06/26/2013
Many new computers do not offer serial communication ports. How is communication possible to Yaskawa products if no serial port is available? Posted Date: 06/25/2013 Answer: Currently most Yaskawa products require serial communication; some do offer Ethernet as an alternative. However, if neither method of communication is available, most computers offer USB (Universal Serial Bus). A USB to serial adaptor device may be used to establish communication. These adaptors are widely available on the Internet and at electronics stores. All current Yaskawa software will work with a USB to serial port adaptor (provided the operating system supports it). Yaskawa has used the following inexpensive model successfully with current generation products and software (SGDH, SMC-2000, SMC-3010, SMC-4000, MP-940, MP-930, MP-920, NS-600, NS-500, NS-300, SigmaWin100, SigmaWin+, YTerm, MotionWorks, MotionWorks+, IndexWorks, NS-XXX): http://www.cablestogo.com/product.asp?cat%5Fid=101&sku=26886 USB to serial adaptors can be purchased from many different vendors, including many PC vendors. The results from google search yielded a cost effective unit available, the link is listed below: Some sources for USB-to-Serial adapters: - CBW: manufactured by Zonet and is their Model # ZUC3100. SKU# 830762001706 - Cable America: http://www.cablestogo.com/product.asp?cat%5Fid=101&sku=26886 See attached. JPG file for photo example of cable. Attachments: 8KB Product Group/Line: Servo Products, Controllers, CACR-HR, IndexWorks Software, MotionWorks Software, MotionWorks Plus Software, MP920 Machine Controller, MP930 Machine Controller, MP940 Machine Controller, NS600 Indexer, NSxxx Software, SGDA, SGDB, SGDC, SGDH Sigma II, SigmaWin100-200 Software, SMC-2000, SMC-3010 LEGEND-MC, YTerm Software Topic/Sub Topic: Ask a Technical Question, Environment, Maintenance, Programming Document Number: MTN-5VDNR9 Published Date: 06/25/2013 Share \| Rate Rate this article :	06/25/2013

Showing 21 to 30 of 79 entries.

Previous Page
Page1
Page2
Page3
Page4
Intermediate Pages
- Page5
- Page6
- Page7
Page8
Next Page

SAFETY PRECAUTIONS AND INSTRUCTIONS FOR USE OF FAQ INFORMATION!

Please read and understand the product instruction manual before installing, servicing or operating Yaskawa products. FAQ content and illustrations are provided as technical advice to augment the information in manual, not supersede it. It is not possible to give detailed instructions for all types of installation or support activities. The information described in the FAQs are subject to change without notice to improve the product or FAQ. Yaskawa assumes no responsibility for errors or omissions or damages resulting from the use of the information contained in any FAQ. All warnings, cautions and product instruction for product use must be followed. Installation, operation and maintenance should be carried out by qualified personnel. Failure to observe these and other precautions highlighted in the product manuals will expose the user to high voltages resulting in, serious injury or death. Qualified personnel are defined as individuals who are familiar with the installation, starting, operation and maintenance of Yaskawa products of the type described and have proper qualifications to perform the work.

Node: dxpprd01:8080

Rating

Rate

SiteSearch

Yaskawa Main Navigation