MP2600iec

One common cause of the CPU load being higher than expected is caused by using a custom Function Block that uses a large structure connected as a VAR_INPUT instead of a VAR_IN_OUT.

When a variable is declared as a VAR_INPUT, the MPiec Controller copies the entire contents of the structure into the Function Block every scan. Other programming languages refer to this technique as “Passing by Value.”  In this situation, the Function Block does not have the ability to alter the contents of the original data. When declaring a variable as VAR_IN_OUT, the MPiec Controller passes a pointer to the original location of the variable rather than a copy of the data. Other programming languages refer to this technique as “Passing by Reference.” The pointer is an internal 32 bit value, which is significantly more efficient than copying the entire contents every scan. This method also gives the Function Block the ability to alter the contents of the structure variable.

To show this example in practice, the attached document shows two scenarios. The first scenario scans a Function Block with a large structure as a VAR_INPUT and results in a high CPU load. The other scenario shows the same structure as a VAR_IN_OUT and has no impact on the CPU load.

The large structure is an array of an array creating 500,000 LREAL’s. There is nothing else in the program, the custom Function Blocks have no code.

Yaskawa motion systems use lithium batteries for mainly two different functions: maintaining Absolute encoder data and preserving CPU non-volatile memory.

The encoder battery used with the ServoPacks (JZSP-BA01) is required if a multi-turn absolute encoder is needed because it holds the multi-turn encoder data when the drive power is down. Therefore, when setting the drive to use the absolute encoder as an incremental encoder or a single-turn absolute encoder, the encoder battery is not needed.  The encoder battery power can be applied via the battery case on the ABS encoder cable (CN2), or through the I/O connector (CN1, for example Sigma7 ML-III ServoPack, pins 14[+] & 15[-]).

Figure1

When using an absolute encoder without the encoder battery case, the battery can be connected to through CN1 connector on the ServoPack:

Figure2

Figure3

The Absolute Encoder Current Draw specification is:

• 20 μA when ServoPack is powered off
• 3 μA when ServoPack is powered on (w/o diode in place)

To determine the worst case battery life, divide the A-hour rating of the battery by the Sum of the current of all encoders when powered off.

For example, assume 16.5 A-hr battery and 16 Encoders are connected: 16.5 A-hr / (.000020 A * 16) = 51500 hours or 5.8 years

For installing and replacing the battery in the ServoPack, refer to:

• YASKAWA SIGMA-7 AC Servo Drives and Motors Technical Supplement (YAI-KAEPS80000123F)
• YASKAWA AC Servo Drives Sigma-V Series Product Catalog (YEA-KAEPS80000042)

The other type of batteries is used for the MP controllers. These batteries (JEPMC-BA3001) provide a backup power for the CPU non-volatile memory, preserving the SRAM data when CPU power is down. This data includes the retained variables, the alarm history, the absolute encoder offset and the real-time clock data. The SRAM can last for one hour without the battery connected. This battery must be replaced while power is supplied, within 2 weeks of when the BAT indicator first lights. For the MP2600, the SRAM battery power can be applied through the battery connector (CN14), or through the I/O connector (CN13 pins 7[+] & 32[-]).

Figure4 

For installing and replacing the battery in the CPU, refer to:

• YASKAWA MP3200iec Machine Controller Hardware Manual (YAI-SIA-IEC-5)
• YASKAWA MP2600iec Hardware Manual (YEA-SIA-IEC-6)

More references on the encoder usage in Yaskawa motion systems:

• The absolute encoder battery back-up techniques
• Material Safety Data Sheet (MSDS) for Toshiba ER3V and ER6V batteries
• A.810 Absolute Encoder Battery Life and Replacement
• MP940 Dip switch settings, battery and PC cable

If the Vipa Ethernet coupler was previously configured and then modules are added or changed, you must perform an online save through its web page before they will function correctly.  If the new configuration is not saved, the Vipa Ethernet coupler will flash the SF and MS red LED’s when the controller connects.  The I/O status variable in the MotionWorks IEC project will show a status of 0x1000 (connected) or 0x320 (deleted configuration) but the I/O will not update.

To save the configuration on the Vipa Ethernet coupler:

Open the Vipa web page by typing the IP address into the browser’s address bar.

Note:  Disconnect or stop any MPiec controller Ethernet connection to the Vipa bus coupler.

Navigate to the Configuration tab and press the Save button.

After saving the configuration, the Vipa Ethernet coupler must be powered down for at least 20 seconds, and then powered back up.  If the power is short cycled, the Vipa Ethernet coupler will not power up.

See attached document for a screen shot of the web page’s Configuration tab

Invalid Segment Type Error 06#315 may result if configuration instances of the adapter (SigmaLogic EIP Node) are swapped.

Valid configuration instances of the adapter should be as follows.

Input :
Assembly Instance  : 102 ;
Size : 64 (32-bit);

Output :
Assembly Instance  : 112 ;
Size : 64 (32-bit)

Configuration :
Assembly Instance  : 1 ;
Size : 1(8-bit)

When an MP2600iec drops the Ethernet connection to a PC due to a power cycle, some PC’s set their Ethernet connection to 10mbps. When the MP2600iec re-establishes the Ethernet connection, it detects the 10mbps connection and it creates an alarm because the MP2600iec does not support 10mbps connections. After this alarm occurs, the PC cannot communicate to the MP2600iec.

To avoid this alarm, always use an Ethernet switch or hub when connecting a PC to an MP2600iec.

If using an Ethernet switch or hub is not an option, the connection can be recovered by unplugging the Ethernet cable and then plugging it back in.

See attached document

See attached document.

There are two cases when this may occur. If the library cannot be found on the PC or if the library is marked as open.

See attached document for instructions.

The MPiec controllers have evolved over their lifespan. The first versions only supported Internet Explorer with the classic interface. A modern interface was added and fully supported in firmware release 3.2.0 to conform to more modern browsers. The classic interface is the only interface supported by Internet Explorer and is available in all firmware versions. The attached chart shows the supported interface - firmware version combinations.

See document MTN-97XRJ3 “Using Web Server Classic on the MPiec Controllers” for more information on using the classic interface.

There are two ways to reset the controller to factory defaults, one using the web browser and the other through Hardware Configuration.

See attached document for specific instructions.

Please open the pdf for a look at the Controller Memory for the MPiec Controllers.

The controller was unable to load a configured axes group is indicated by the error 440C 1003 with the description: Unable to add axes group to groupIODriver. Check the validity of the handle. The most likely cause is that the INIT switch of the controller is ON. The INIT switch disallows the loading of any saved configuration.

To fix this alarm, turn the INIT switch off and reboot the controller.

Please see attached document for details.

See attached file

See attached document

The INIT switch bypasses the loading of any saved configuration.  Use this switch if there are suspected configuration issues causing alarms on the controller that may prevent you from connecting to the MPiec controller.  If the INIT switch is ON and the CNFG switch is OFF, the controller will show no axes connected.

The CNFG switch automatically configures the MPiec controller with the supported devices attached to the Mechatrolink network and I/O cards.  When this switch is ON the MPiec controller can control any supported devices attached regardless if they are in a saved configuration or not.  Yaskawa recommends leaving this switch on.

The  SUP/MNT switch puts the MPiec controller in supervisor mode for firmware upgrades.  When this switch is ON, the controller will not “control” anything (The PLC will not run.)  Servos cannot be enabled and I/O cannot be read or written.

With MotionWorks IEC v2.x, it may have been necessary to include a file (as described below) to ensure that all SGDV drives were read correctly. In general, this problem has been fixed and should no be necessary when using newer version of MothinWorks IEC v3.x.

The following solution is applicable for MotionWorks IEC 2.x and SGDV drive ONLY.  MotionWorks IEC 3.0 and later, as well as Sigma-7 drive compatiblity, are NOT supported using this method. Please contact Yaskawa Technical Support Group in these situations.

If a file named "Compatibleparts.XML" is added to the following MotionWorks IEC working directory, the Hardware Configuration will treat an unknown part number as a part number in its database. A reference file which can be edited is included on this page.

This solution is only recommended if your version of MotionWorks IEC does not recognize the part number of a Sigma-5 servopack on the network, such as a single phase 1.5KW servopack, or the fanless servopacks that end in 002000. The XML file attached to this FAQ contains the information to allow the recognition of the following six amplifier models:

Exact part Compatible part
SGDV-****21*002000 SGDV-****21*
SGDV-****25*002000 SGDV-****25*
SGDV-****11*002000 SGDV-****11*
SGDV-****15*002000 SGDV-****15*
SGDV-****E1*002000 SGDV-****E1*
SGDV-****E5*002000 SGDV-****E5*

The first tag contains the unknown part number. Asterisks (*) indicate any character. The plus character (+) indicates that the remainder of the string is ignored.

The second tag is the compatible part number already in your MotionWorks IEC database.

SGDV-****E1*+
SGDV-****E1*

Windows XP Location:
C:\Documents and Settings\All Users\Application Data\Yaskawa\MotionWorks IEC ConfigTool
Windows 7 - Windows 10 Location:
C:\ProgramData\Yaskawa\MotionWorks IEC ConfigTool

Yes. Exporting Modbus variables for a Red Lion HMI can be done directly from MotionWorks. First, the HMI Tag Import/Export tool needs to be enabled in the Modbus section of the Hardware Configurator. Once enabled the tool allows the user to choose “Red Lion” as the Manufacturer and also select a location on their PC to store the exported tag file. Last, to export the tag variables, use the “Export MWiec variables to HMI tags” button in MotionWorks to create a tag file which can be imported into Red Lion’s Crimson software.

Please see the attached document for steps on importing POU's within MotionWorks IEC.

Please see attached application note for detailed steps on converting a MotionWorks IEC Version 2 Project into Version 3.