SW Version Information

Release Date: 2025.12.22

DOWNLOAD HERE

Important Notice

When using the robot in the V2.12.3 environment and switching the controller to use V3.4, a manual reboot is required after the initial boot.
This procedure is necessary for optimization following the restoration because the robot's unique parameters were changed to improve accuracy. If the reboot is not performed, the robot may malfunction.

Key Changes

Dart-Platform

Added Guide Text for Motion Power Control Instructional text regarding voltage settings has been added to the Motion Power Control section in the Settings menu to minimize confusion for users operating in high-voltage environments.

• Text: "Please set it to 220V, as the same output processing is performed even in voltage environments higher than 220V."

Motion Control

Improved Solution Space Criteria for movejx during Blending Motion Resolved an issue where the joint configuration (Solution Space) became unnaturally fixed when the subsequent motion in a blending operation was movejx (auto solution).

• The reference for calculating the Solution Space has been changed to the "target point of the preceding motion."

• The logic has been updated to ensure natural joint transitions as expected by the user during continuous motion sequences.

Hardware & Positioning

Improved Position Precision upon Reboot Improved minor positional errors caused by physical factors during a Power Cycle (reboot).

Bug Fixes

System Stability

Fixed Unexpected Error [5.7056] when Restarting Program Fixed an issue where Unexpected Error [5.7056] would intermittently occur, causing the robot to stop, when restarting a program after it had been stopped during execution.

Motion Control

Fixed movejx Target Reach Failure near Singularities Fixed an issue where the movejx command failed to reach the target position near a singularity and triggered a Joint Limit error when calibration parameters were applied.

Force Control

Fixed movel Absolute Position Movement Error in Compliance Mode Fixed an issue where executing a movel command in Compliance Mode caused the robot to move to a relative position based on the initial position, rather than the intended absolute position.

PREVIOUS RELEASE NOTES: