EasyManua.ls Logo

YASKAWA MP2000 User Manual

YASKAWA MP2000
55 pages
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Page #27 background imageLoading...
Page #27 background image
TECHNICAL NOTE
MOTION APPLICATION ENGINEERING GROUP
Yaskawa Electric America - 2121 Norman Drive South – Waukegan IL 60085
(800) YASKAWA - Fax (847) 887-7280
11/23/2005 27 of 27 eng/05.055/MCD
DEVELOPING CODE
With the memory allocated and symbol naming conventions completed, code is ready to be
developed as decided by the user’s evaluation of the programming methods.
The application is ready to be translated to executable code using Ladder, Motion Programs or
Function Blocks. When translating the application to executable code, there are many key
techniques used in developing a reliable, efficient application program. Key techniques for the
three programming methods are examined in this section.
Ladder Techniques
When programming in ladder, the user must consider the scan based I/O and Parameter update.
This is a key difference to understand for programmers familiar with structured text based
languages where the application directly controls the flow of instruction execution. In addition,
high and low speed scan drawings require special consideration when developing logic to assure
intended results.
Low Scan Interlocks
The MP Controllers have two user settable scan rates: high and low. As discussed in the
program architecture section, this allows the application to be optimized. Low speed drawings
typically contain non-speed critical machine sequences, such as I/O interfacing sequences and
HMI interface logic.
Axis Specific Low Scan Interlocks
Enabling an axis is typically performed in a low scan drawing as described in the drawing
architecture section. The goal here in Axis Interlocking is to check status of critical axis and
system alarms, and to create an ‘axis normal’ signal. The axis normal signal will be used to allow
the ‘servo enable’ signal to turn on, and remain on. If an error occurs during any mode of
operation (such as manual mode or automatic production mode) then the servo on signal will turn
off, and the axis will stop motion.
In DWG L20.01, the first rung of code checks the entire status register IL8004 loads its status into
the Axis001_NoAlarms catch all bit for axis #1. Even though the IL8004 register catches all
alarms, it is helpful to summarize all the alarms with one bit to aid in visually troubleshooting if an
alarm occurs (see user manual for bit breakout). IL8004 catches alarms such as
IL8004 (Alarm Status for Axis #1)
- Servo Driver Errors
- POT/NOT (positive and negative over travels)
- Positioning Timeout, Excessive Error, excessive speed
- Servopack Parameter setting error, comm. error, encoder disconnect, etc
Question and Answer IconNeed help?

Do you have a question about the YASKAWA MP2000 and is the answer not in the manual?

YASKAWA MP2000 Specifications

General IconGeneral
BrandYASKAWA
ModelMP2000
CategoryController
LanguageEnglish

Summary

MP Machine Controller Programming Best Practices Overview

Why Use a Yaskawa Machine Controller?

Explains the benefits and advantages of using Yaskawa machine controllers for automation.

What's in MP Programming Best Practices Guideline?

Outlines the content and purpose of the MP Programming Best Practices Guideline document.

Benefits of Using MP Best Practices

Summarizes advantages across design, implementation, and support levels.

Design Level Benefits

Details advantages for programming method selection and model standardization.

Implementation Level Benefits

Covers benefits like pre-defined code, scalability, and optimized performance.

Support Level Benefits

Highlights advantages in training, skill transfer, and commonality for support.

Getting Started with MP Best Practices Guideline

Machine Information Gathering

Selecting Programming Method

Overview of Motion: MP Controller to Amplifier

All Layers in a System

Register Interface

Program Architecture

Drawings Definition

Defines "drawings" as modular ladder logic sections and their families (A, I, H, L).

Drawing Family Execution

Explains the priority and execution timing of different drawing families within the program scan.

Drawing Execution Chart

Graphically illustrates the execution flow of drawing families based on scan times.

Drawing Family Hierarchy and Program Flow

Describes the hierarchical calling structure and execution flow between parent, child, and grandchild drawings.

Best Practice Drawing Usage

A-Drawings

Used for initial system setup and executed once upon power-up.

I-Drawings

Used for time-critical operations, though often avoidable with modern processors.

H-Drawings

Best for time-critical processing, including motion control code.

L-drawings

Used for non-time-critical processing and general machine control.

MP2000 Best Practice Drawing Architecture

General Architecture Outline

Highlights advantages like organization, debug simplification, and code efficiency.

Drawing Architecture for A, H, and L

Details specific drawing types and their recommended usage within families A, H, and L.

Low Speed Scan Drawings (L)

Lists specific low-speed drawings and their functions for sequencing and auxiliary devices.

Memory Allocation

What is Memory Mapping?

Defines memory mapping as the recommended layout for MP2000 registers for organization.

Why is Memory Mapping Important?

Explains importance for program flexibility, reduced development time, and easier troubleshooting.

Memory Mapping with Function Blocks

Discusses register reservation for function blocks and allowable user address ranges.

D Registers for Working Memory

Explains the use of local D registers for drawing-specific data to minimize global memory usage.

Automatic Address Allocation

Advantages of Automatic Address Allocation

Highlights programming in symbols, organization, and preventing register overwrites.

Disadvantages of Automatic Address Allocation

Notes potential issues with even/odd addresses for certain data types.

Symbol Naming & Commenting Conventions

Purpose of Naming Convention

Explains the goal of increasing ease-of-use and program robustness.

Recommendations for Symbol & Tag Naming

Provides guidelines for clear, sortable symbol names and practical tag naming.

Developing Code

Ladder Techniques

Discusses scan-based I/O and parameter updates in ladder programming.

Low Scan Interlocks

Covers the use of low-speed drawings for non-speed critical sequences and interlocks.

Axis Specific Low Scan Interlocks

Explains interlocking for axis enabling and checking status.

Non-Axis Specific Low Scan Interlocks

Details common machine sequences and mode switching logic in L10 drawings.

Machine Interlocks

Axis Enable Interlocks

Verifies safety circuits and amplifier power before enabling an axis.

Automatic Mode Interlocks

Ensures all axes are normal, enabled, and no faults exist before enabling automatic mode.

Motion Programming Techniques

Gearing

Technique for creating gear applications by scaling master pulses with a B/A ratio for slave commanded position.

Waterfall Technique

Method using local registers as accumulators to simplify monitoring and debugging by writing to registers in one place.

Modulus Technique

Technique to modulate axis operations for repeating cycles like cam profiles by calculating position differences.

Delta Scan

Method to calculate position or value changes at scan rate, useful for modulus functions or speed compensation.

Handling Rollover

Uses math functions (ADDX, SUBX) to prevent miscalculations due to long register rollover.

Sequencing Techniques

State Machine Programming vs. Step Sequencing

Compares two methods for programming sequences: state-based and step-based.

Step Sequencing Technique

Describes using individual bits or toggles to initiate and monitor sequence steps.

Rules for Motion Programming

Starting a Motion Program

Ensures ladder code includes interlocks for servo enablement and 'NOP' mode before starting a motion program.

Active Interlocks During Motion Program Execution

Discusses interlocks for global registers and handling motion program execution state changes.

Stopping a Motion Program

Covers expected alarms when halting programs and using ladder logic to flag program status.

Bit Handshaking between Motion Programs and Ladder Code

Explains using SET/RESET coils for communication between motion programs and ladder logic.

Using WHILE Loops in Motion Programs

Guidelines for WHILE-WEND loops, including using EOX to avoid watchdog alarms.

Using PFORK, JOINTO, and PJOINT

Rules for parallel processing, coordinating multiple axes, and using global registers for handshaking.

Using Subroutines in Motion Programs

Recommends subroutines for repeatable processes like writing to Servopack parameters.

Related product manuals