Cause:
The header node < RobotConfig…> of the robot configuration file RobotParameter.xml in the controller's ConfigureFiles directory is damaged or missing.
Troubleshooting:
Go to ftp://192.168.39.220/ConfigureFiles/ and check whether the header node of the robot configuration file RobotParameter.xml is normal.
Solution:
Contact after-sales support and copy the corresponding robot configuration file RobotParameter.xml to the controller.
Case sharing:
None.