Robot hardware detection method and system

Abstract

The invention discloses a robot hardware detection method. The robot hardware detection method is applied to a robot controller comprising a programmable logic controller (PLC) layer and an embedded layer. The robot hardware detection method comprises the steps that the PLC layer acquires the states of slave units connected with ports of the robot controller and feeds back the states of the slaveunits to the embedded layer, wherein the states are normal states or abnormal states; and the embedded layer receives and displays the states of the slave units. Apparently, in the practical application, detection of the states of the slave units connected with the ports of the robot controller is achieved through the robot controller, and the states of the slave units are displayed, externally connected detection equipment is not needed, the cost is low, meanwhile the workload of a testing staff is reduced, and the testing efficiency is improved. The invention further discloses a robot hardware detection system which has the above beneficial effects.

Description

technical field [0001] The invention relates to the field of robots, in particular to a method and system for detecting robot hardware. Background technique [0002] With the continuous maturity of robot-related technologies and markets, it is very important to monitor the robot and determine whether the robot has hardware problems (that is, whether there is a problem with the slave device connected to the robot controller). In the prior art, to detect whether there is a problem with the slave devices connected to each interface of the robot controller (master device), it is generally necessary to rely on other detection tools, such as checking the device connected to the CAN (Controller Area Network, Controller Area Network) interface. The kvaser that checks whether there is a problem with the slave device, the Adam module that checks whether there is a problem with the slave device connected to the RS485 interface, etc., that is, the slave devices connected to different in...

AI Technical Summary

Problems solved by technology

In the prior art, to detect whether there is a problem with the slave devices connected to each interface of the robot controller (master device), it is generally necessary to rely on other detection tools, such as checking the device connected to the CAN (Controller Area Network, Controller Area Network) interface. The kvaser that checks whether there is a problem with the slave device, the Adam module that checks whether there is a problem with the slave device connected to the RS485 interface, etc., that is, the slave devices connected to different interfaces need to use different detection tools, which makes the detection steps complicated and increases the testing personnel. Work load and high detection cost

Images