YASKAWA DX200 Feature Pack Complete Guide

Collection of common troubleshooting cases

Case 1: High Speed Ethernet Server connection frequently drops

Phenomenon: The upper computer reads the robot's position through UDP and updates it once per second, but there is no response after a few minutes.

Troubleshooting: Check if the network switch supports full duplex and try a direct connection test. Use Netstat - s to view UDP packet loss statistics. The packet loss rate was found to be as high as 5%.

Solution: Replace with an industrial grade switch, place the robot controller and upper computer in the same VLAN, and turn off unnecessary broadcast traffic. At the same time, add a heartbeat mechanism in the program to automatically resend the connection request if no response is received within 3 seconds.

Case 2: Occasional collision between two robots during independent control

Phenomenon: Robots A and B are running simultaneously, but occasionally collide in the common working area.

Troubleshooting: Check if the interference detection function is enabled. Although cube area interference was enabled, only TCP was checked and the upper arm was ignored.

Solution: Use the "Arm Interference Check" function to set cylindrical models for the upper and lower arms of two robots, and define the overlapping area as the interlock zone. Meanwhile, use the WAIT instruction in the homework to implement software interlocking based on shared registers.

Case 3: Arc tracking COMARC not corrected

Phenomenon: During the welding process, the robot swings but fails to correct the weld deviation.

Troubleshooting: Check if the welding power supply has constant voltage characteristics and if the current feedback signal is correctly connected to the controller input port. Confirm that the sensor parameters (such as swing amplitude, frequency, and correction gain) in the ARCSON instruction are set appropriately.

Solution: Adjust the "correction gain" from 0.5 to 1.2 and confirm that there is no fluctuation in the welding current baseline. If pulse welding is used, it may be necessary to reduce the pulse frequency to ensure stable current signal.

Case 4: Automatic backup files cannot be accessed through FTP

Phenomenon: The CMOS Save with FTP function is enabled, but the directory is empty after the FTP client connects.

Troubleshooting: Confirm that the Ethernet FTP function (164060) has been installed simultaneously and that the FTP server mode is activated (the controller can only be in either Client or Server mode). Check FTP user permissions.

Solution: Switch the FTP mode to Server in the controller settings and set the username and password (default is anonymous readable). Use FileZilla client to connect in active mode, with the path/CAMOSBACK UP.

Case 5: MotoLogix controls robot to remain stationary

Phenomenon: The PLC sends motion commands, but the robot does not respond, but the communication diagnosis shows normal.

Troubleshooting: Check if DX200 is in "remote mode" (with the teaching pendant key in the REMOTE position). Confirm that the MotoLogix Runtime has started (can be viewed in the system information). Monitor the Enable and Busy signals in the PLC function block.

Solution: The usual reason is that the robot is not in servo mode. In the PLC program, first call the MC-Power function block to enable the servo, and then send MC_SoveAbsolute. In addition, ensure that the fieldbus (ProfiNet/DeviceNet) mapping is correct and the I/O data length is consistent with the MotoLogix definition.

Performance optimization and programming best practices

Use System Job (163901) to handle background loop tasks. For example, continuously monitoring the collision detection status, and immediately alerting when in PLAY mode and collision detection is unexpectedly turned off. The system job runs automatically after the controller is started, independent of the operating mode and servo state.

Utilize Interrupt Job (163908) to quickly respond to external events. For example, when the safety light barrier is triggered, the current movement is interrupted and the evacuation procedure is immediately executed. Interrupting tasks can occur during motion and timer commands, minimizing response latency. Each robot can define up to 8 interrupt tasks.

Combining relative homework with user coordinate system: Write the welding trajectory as a relative homework and attach the origin of the user coordinate system to the reference point of the workpiece. When changing the workpiece type, only the new reference point is measured and the user coordinate system is redefined, and the original trajectory does not need to be re taught.

TCP function (163910) reduces duplicate teaching: If multiple tools (such as primer gun and topcoat gun) need to follow the same trajectory, first use tool A to teach the trajectory, and then insert the TCPON command in the job to switch to tool B. The trajectory will automatically switch without the need for re teaching.

Regular backup and version management: Use the automatic backup function to backup the entire system data to the FTP server every morning. At the same time, manually save a dated. cmos file after each major modification. It is recommended to keep a backup history of at least 30 days.