Question:
How to troubleshoot GV_AI Accelerator Module related error (e.g. the hardware cannot be detected) on the AIS or Center V2 side log?
Answer:
Currently, AIS and CV2 have defined the following events.
Suppose a single M.2 card experiences an abnormal condition, causing the engine to fail to operate normally.
In that case, a blue frame will first appear around the CV2 pop up video, and the relevant log (IDS_PVD_ERROR06) will be recorded.
However, if multiple cards fail, or if one card fails, AIS may only see a performance degradation ( IDS_PVD_ERROR04 AIS busy).
At that moment, it may not be possible to immediately determine if there is a hardware anomaly on the AIS side.
Errors reported from the AIS side (will be recorded in the CenterV2 system log):
- IDS_PVD_ERROR02 \\ Incorrect AIS account/password
- IDS_PVD_ERROR04 \\ AIS busy
- IDS_PVD_ERROR05 \\ AIS connection timeout
- IDS_PVD_ERROR06 \\ AIS engine not recognized
- IDS_PVD_ERROR13 \\ Invalid image size
- IDS_PVD_ERROR14 \\ Invalid image type
- IDS_PVD_ERROR15 \\ AIS initializing
For IDS_PVD_ERROR04 where it might suggest AIS loading, the user should check the number of channels connected.
For IDS_PVD_ERROR05 where it might suggest network network-related issue, the user should check the network between Center V2 and AIS.
For IDS_PVD_ERROR06 where it might suggest hardware hardware-related issue, it is recommended to check and troubleshoot the AIS PC hardware.