Support

Yes, the HV600 will have Emergency Override functionality with several important enhancements as standard.

Yes, the FP605 will have 600V drive models. Development is ongoing and planned for future release.

Please see attached document for details.

Yes, I, J, K for circle mode is supported.

When Pn002.2 (Absolute Encoder Usage) = 0 (Use the absolute encoder as absolute encoder) the SERVOPACK is not ready to accept the /S-ON (Servo ON) signal until the SEN (Absolute Data Request) signal is ON. The SEN signal can be masked ON by setting Pn515.0 = 7 (The signal is always active). 

If the position error reported by your EtherCAT master is greater than what is reported in SigmaWin+ (for example through the Trace tool) this may be due to how the EtherCAT master is calculating position error. Position error reported in SigmaWin+ is calculated according to the motor's commanded position in a given servo cycle minus its actual position for the same servo cycle.

In some EtherCAT masters, the position error is calculated using the Target Position (0x607A) and Position Actual Value (0x6065) objects, where Position Error = Target Position - Position Actual Value. The drive's execution of the Target Position and reporting of the Position Actual Value occur at different network cycles, so the position error calculated by the EtherCAT master includes those cyclic delays. In short, if the EtherCAT master's position error is greater than the position error seen in SigmaWin+, it may be due to a position error calculation that is affected by network delays.

To avoid a position error calculation which is affected by network timing delays, the EtherCAT object Following Error Actual Value (0x60F4) is available in Sigma 7 and Sigma 5 and is mapped, by default, to TPDO1 (0x1A00). This object reports the same position error value as seen in SigmaWin and is the recommended means of obtaining position error in an EtherCAT system.

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 (JZSP-BA01) 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

See attached document

DriveWizard^® Mobile offers parameter or application backup in the Yaskawa Drive Cloud^TM so that data is available anytime and anywhere.

Parameter back-ups are connected to the drive serial number and your personal login, which can only be done with a user account.

Additionally, the account allows DriveWizard Mobile to gain access to the latest drive parameter data and manuals.

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

See attached document.

The controller counts all configured axes and any axes it discovers when the CNFG switch is on. To avoid adding discovered axes to this count, set the CNFG switch to off before the controller is powered on, or disconnect the additional axes.

Invalid Segment Type Error 16#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)

There is an error in older firmware versions that cause analog output channels with a negative offset to only output the maximum voltage. Use firmware version 3.1.1.1 for all MP2300 type controllers and firmware version 3.5.0 and higher for all other controllers to correct the issue. The 3.5.0 release will be available in April 2018.  Please contact customer support with help in resolving this issue before then.

The Yaskawa EtherCAT SERVOPACK controls the electronic gear parameters Pn20E and Pn210.  Changes made by the user have no effect. After a power cycle they are overwritten by the SERVOPACK.

For the SGDV EtherCAT SERVOPACK, Pn20E and Pn210 are always set to 1.

For the SGD7S EtherCAT SERVOPACK, Pn20E and Pn210 are set so that the resolution is 1,048,576 increments per rotation. When using motors with 24-bit encoders (SGM7J, SGM7A, or SGM7G) Pn20E will be set to 16 and Pn210 will be set to 1.

To adjust the reference units seen by the EtherCAT Master use objects 2701:01h and 2702:02h (PnB02 and PnB04).

In MotionWorks IEC versions 3.3.0 and lower, projects that had ladder rungs that were missing the right power rail compiled without any errors. This was not in compliance with the IEC 61131 standard. Starting with version 3.4.0, all ladder rungs must contain a right power rail for successful compilation.

1.  The feedback position is correct; however, for firmware version 8.03 and earlier, the low four bits of position data are not available.

2.  Future firmware versions will not allow writing to Pn20E and Pn210, but instead will enable a full-single-turn resolution mode via a new CoE object.