Faults

Despite the considerable efforts made by DayStar Robotics engineers during the design and manufacturing process, unexpected issues may still inevitably arise during actual operation. When problems occur, they are communicated to operators, developers, and other equipment through fault alerts.

Faults can vary in type and origin. Current fault information can be accessed via the APP or SDK.

System Faults

System faults indicate hardware or software malfunctions. These include fault sources and fault codes, which can be communicated to users through the APP or SDK and are recorded by cloud services when Internet is availbale. To resolve these faults, please following the specific solutions corresponding to each fault code.

Behavioral Faults

Behavioral faults indicate that the robot is unable to execute a particular command. This typically means the robot's current state do not permit the execution of the command or the robot is currently occupied.

• Not placed in the specified posture

• Emergency stop button not illuminated

Application Faults

Application faults refer to issues with the App, such as the robot not being bound, connection failures, or network abnormalities.

Fault Recovery

Common warning will automatically clear once the conditions are resolved.

For special faults, such as motor protection or mainboard disconnection, a reboot is required to restore normal operation.