7.4 Fault Diagnosis Section
7.4.1 Overview
The robot is equipped with built-in capabilities for basic fault diagnosis and health monitoring. It can track fundamental anomalies and faults, such as joint overheating, sensor failures, persistently high system resource usage, and low battery levels. If you need to continuously monitor the robot's status, we recommend querying the current alarm list at regular intervals. Please keep the frequency low to avoid performance impact; a frequency of 0.2 Hz or lower is recommended. The full list of faults and alarms can be found in the exception_info.yaml file located at /agibot/software/v0/config/hds/database/exception_info.yaml on the MDU.
7.4.2 Get Current Alert List RPC Interface
| Interface Name | pb:/aimdk.protocol.HDSService/GetAlertList |
|---|---|
| Function Overview | Get Current Alert List |
| Interface Type | HTTP JSON RPC |
| URL | http://10.42.10.12:50587/rpc/aimdk.protocol.HDSService/GetAlertList |
| Input Parameters | |
| Output Parameters |
|
| Example Script | examples/hds/get_alert_list.sh |
| Remarks |
7.4.3 Other Health Diagnostic Interfaces
In addition to the above GetAlertList interface, the following interfaces are also available
GetTotalAlertList: Get all alerts in the system, including historical informationGetAlertCount: Get the number of all current alerts in the systemGetExceptionEvent: Get fault events in the system
However, the information obtained from the above interfaces is too redundant or inconvenient to use. It is recommended to only use the GetAlertList interface for basic alert information retrieval operations. Examples for each of the above open interfaces are located in the examples/hds directory, and their input and output parameters are not detailed here.