Device connection state self-diagnosis system and method and non-transient storage medium

Abstract

The invention provides an equipment connection state self-diagnosis system, a self-diagnosis method and a non-transient storage media, and the equipment connection state self-diagnosis system comprises a communication diagnosis model, an equipment communication state recognition model, a communication line recognition model and a graphical representation refreshing model. And the communication diagnosis model judges whether the equipment data of the peripheral equipment is received. The device communication state recognition model recognizes that the communication line of the peripheral device is normal when receiving the device data of the peripheral device, and judges whether the connection state is a first type or a second type according to the standard data of the peripheral device. The communication line identification model identifies that the peripheral device is disconnected when the device data of the peripheral device is not received, and checks the communication line of the peripheral device to judge whether the connection state is a second type or a third type. And the graphical representation refreshing model refreshes the display drawings of the peripheral devices in the graphic control page according to the connection states of the peripheral devices.

Description

Technical Field

[0001] The present application relates to the field of smart grids, and in particular to a system, a self-diagnosis method, and a non-transitory storage medium for diagnosing the connection status of peripheral devices in a smart grid. Background Art

[0002] In recent years, the use of smart grids has gradually become popular. Generally speaking, smart grids design power systems in layers according to functionality and have multiple functions, such as real-time information monitoring, data analysis, and forecasting management.

[0003] With the expansion of smart grids, the market needs to gradually add new functions to assist, making the grid more intelligent to meet the ever-increasing needs of users. However, at this stage, there is still a lack of effective methods and systems that can determine the connection status of each peripheral device of the system through real-time communication data and display it in a real-time visual manner. Therefore, it is still difficult for users to know the connection status of peripheral devices in the first place, and it is difficult to reduce the difficulty of maintenance processing. Summary of the invention

[0004] The main purpose of the present application is to provide a device connection status self-diagnosis system, self-diagnosis method and non-transitory storage medium, which can automatically diagnose the connection status of currently connected peripheral devices and display it in real time in a visual manner.

[0005] In one embodiment, the connection status self-diagnosis system of the device of the present application is communicatively connected to multiple peripheral devices in the environment, and includes:

[0006] One picture control page;

[0007] a communication diagnosis model configured to determine whether a device data of each peripheral device is received;

[0008] a device communication status identification model, configured to identify that a communication line of a first device among the plurality of peripheral devices is normal when the communication diagnosis model receives the device data of the first device, and to determine that a connection state of the first device is a first category or a second category according to a characteristic data related to the connection in the first device, wherein the first category indicates that the communication line of the first device is normal and the device connection is normal, and the second category indicates that the communication line of the first device is normal but the device connection is abnormal;

[0009] a communication line identification model configured to identify that a second device among the plurality of peripheral devices is disconnected when the communication diagnosis model does not receive the device data of the second device, and to determine that the connection status of the second device is the second category or a third category by checking the communication line of the second device, wherein the third category indicates that the communication line of the second device is abnormal and the device connection is abnormal; and

[0010] A graphic refresh model is configured to refresh a displayed graphic of each peripheral device in the graphic control page according to the connection status of each peripheral device.

[0011] In one embodiment, the connection status self-diagnosis method of the device of the present application is applied to a connection status self-diagnosis system that is communicatively connected to multiple peripheral devices in an environment, and includes:

[0012] Step a) the self-diagnosis system determines whether a device data of each peripheral device is received;

[0013] Step b) upon receiving device data of a first device among the plurality of peripheral devices, the self-diagnosis system identifies that a communication line of the first device is normal;

[0014] Step b1) after step b), judging a connection status of the first device as a first category or a second category according to a characteristic data related to the connection in the first device, wherein the first category indicates that the communication line of the first device is normal and the device connection is normal, and the second category indicates that the communication line of the first device is normal but the device connection is abnormal;

[0015] Step c) when the device data of a second device among the plurality of peripheral devices is not received, the self-diagnosis system identifies that the second device is disconnected;

[0016] Step c1) after step c), by checking the communication line of the second device, determining whether the connection status of the second device is the second category or a third category, wherein the third category indicates that the communication line of the second device is abnormal and the device connection is abnormal; and

[0017] Step d) The self-diagnosis system refreshes a display diagram of each peripheral device in a graphic control page according to the connection status of each peripheral device.

[0018] In one embodiment, the non-volatile storage medium of the present application stores an application having a plurality of computer executable program codes, which, when executed, can implement the various specific steps of the connection status self-diagnosis method of the device of the present application.

[0019] Compared with the related art, the present application can immediately diagnose the cause of the abnormality when the connection is abnormal, whether it is a problem with the peripheral device itself or a problem with the communication line, which is helpful for users to troubleshoot and maintain the equipment. In addition, the present application displays the diagnosis results in a visual way, which helps users to detect the existence of the fault at the first time and know exactly whether to check the peripheral device itself or the communication line used for connection. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] Figure 1 This is a schematic diagram of the system connection for this application;

[0021] Figure 2 A block diagram of the diagnostic system of the present application;

[0022] Figure 3A This is the first schematic diagram of the graphic control page of this application;

[0023] Figure 3B This is a second schematic diagram of the graphic control page of this application;

[0024] Figure 4 This is a schematic diagram of the diagnostic results of this application;

[0025] Figure 5A and Figure 5B Diagnostic flowchart for this application;

[0026] Figure 6 Refresh the flowchart for the illustration of this application;

[0027] Figure 7 The third schematic diagram of the graphic control page of this application;

[0028] Figure 8 This is the fourth schematic diagram of the graphic control page of this application.

[0029] Description of Figure Numbers

[0030] 1: Server

[0031] 11: Image control page

[0032] 111: Connection architecture display area

[0033] 112: Communication protocol display area

[0034] 113: Data card display area

[0035] 12: Device communication receiving model

[0036] 13: Communication Diagnosis Model

[0037] 14: Device communication status identification model

[0038] 15: Communication line identification model

[0039] 16: Graphic refresh model

[0040] 17: Device click model

[0041] 18: Data register

[0042] 2: Network switch

[0043] 3: Peripheral equipment

[0044] 31: First peripheral device

[0045] 32: Second peripheral device

[0046] 33: Third peripheral equipment

[0047] 34: The fourth peripheral device

[0048] S51~S68: Diagnostic steps

[0049] S71~S75: Refresh Steps DETAILED DESCRIPTION

[0050] The present application discloses a device connection status self-diagnosis system (hereinafter referred to as the diagnostic system in the specification), which is connected to one or more peripheral devices by wired or wireless means, and receives data from these devices to execute a self-diagnosis program, thereby determining whether these devices themselves are abnormal, or whether the connection between these devices and the diagnostic system is abnormal.

[0051] See also Figure 1 , is a schematic diagram of the system connection of the present application. The diagnostic system of the present application is implemented in the server 1 in the form of software combined with hardware. Figure 1 As shown, the server 1 is communicatively connected to the network switch 2, and the network switch 2 is connected to a plurality of peripheral devices 3 in the field. Thus, the server 1 is connected to the plurality of peripheral devices 3 in the field through the network switch 2 to receive device data of the peripheral devices 3 and execute a self-diagnosis program.

[0052] In one embodiment, the plurality of peripheral devices 3 include various electronic devices in a smart grid, such as digital meters, digital protection relays, phasor measurement units, solar inverters, energy storage bidirectional inverters, battery management systems, uninterruptible power systems, charging piles, generators, and load devices. The network switch 2 communicates with different peripheral devices 3 through different communication protocols, such as Modbus, IEC61850, Ethernet, controller area network (CAN bus), etc., but is not limited thereto. In the present application, the diagnostic system provides at least one graphic control page (e.g. Figure 2 , Figure 3A and Figure 3B The technical feature of the present application is that after the diagnostic system completes the self-diagnosis procedure, the diagnostic result can be displayed in a visual manner in real time through the graphic control page 11, so that the user can quickly detect the abnormality of the peripheral equipment and start maintenance or replacement.

[0053] Please also refer to Figure 2 , is a block diagram of the diagnostic system of the present application. Figure 2 As shown, the diagnostic system of the present application is implemented by a server 1, and includes a graphic control page 11, a device communication receiving model 12, a communication diagnostic model 13, a device communication status identification model 14, a communication line identification model 15, a graphic refresh model 16, a device click model 17, and a data register 18. Specifically, the server 1 of the present application has a non-transient storage medium (such as a memory, a hard disk, or an optical disk, etc.), and the non-transient storage medium is used to store an application, and the application has a plurality of computer executable program codes. When the server 1 executes the plurality of computer executable program codes, the graphic control page 11 and the plurality of models 12-17 can be virtually created in the server 1, so that the server 1 can implement the connection status self-diagnosis method of the present application (hereinafter referred to as the diagnostic method) through the graphic control page 11, the plurality of models 12-17, and the data register 18 (implemented in software or hardware).

[0054] The graphic control page 11 is used to display the connection architecture of all devices in the field where the diagnostic system is located (for example, including a network switch 2 and multiple peripheral devices 3). The device communication receiving model 12 is used to receive the device data of each peripheral device 3 in the field. The communication diagnosis model 13 determines how to start the communication diagnosis program based on the device data of each peripheral device 3. The device communication status identification model 14 is used to identify whether each peripheral device 3 itself is abnormal. The communication line identification model 15 is used to identify whether the communication line between each peripheral device 3 and the server 1 or the network switch 2 is abnormal. The graphic refresh model 16 is used to update the display content of the graphic control page 11 according to the status of each peripheral device 3 itself and the status of the communication line. The device click model 17 is used to detect whether the graphic control element of each peripheral device 3 displayed on the graphic control page 11 is clicked. The data register 18 is used to temporarily store the diagnostic results of the diagnostic system.

[0055] Please also refer to Figure 3A and Figure 3B , respectively, are the first schematic diagram and the second schematic diagram of the graphic control page of this application. Figure 3AAs shown, the graphic control page 11 of the present application includes at least a connection architecture display area 111 and a communication protocol display area 112, wherein the connection architecture display area 111 displays the connection architecture of multiple peripheral devices in the current field, and the communication protocol display area 112 displays the communication protocol used for communication between each peripheral device and the network switch.

[0056] The graphics control page 11 may also include a data card display area 113. Figure 3B As shown, the graphic control page 11 displays multiple graphic control elements representing multiple peripheral devices in the current field, and as described above, the device click model 17 of the diagnostic system detects whether the graphic control elements of these peripheral devices are clicked (for example, the user clicks a specific graphic control element through the human-machine interface of the server 1). When the device click model 17 detects that the graphic control element of one of the peripheral devices is clicked, it triggers the graphic control page 11 to display the data card display area 113. In the present application, the graphic control page 11 obtains the device data corresponding to the clicked peripheral device and displays the device data on the data card display area 113. In one embodiment, the data card display area 113 can display the communication status light of the clicked peripheral device (for example, a green light to display the communication status as connected or a red light to display the communication status as disconnected), basic data (for example, device name, device model and device location, etc.), connection status (for example, connected or disconnected), and communication interruption time and other information. However, the above is only one specific implementation example of the present application, but is not limited thereto.

[0057] The technical feature of the present application is that the graphic control page 11 displays all peripheral devices in the field and the communication protocols used by these peripheral devices through the connection architecture display area 111 and the communication protocol display area 112, and when any peripheral device or communication line is diagnosed to be abnormal, the abnormal information is displayed on the graphic control page 11. Accordingly, it is helpful for users of the smart grid to detect abnormalities in real time and perform maintenance.

[0058] See also Figure 4 , is a schematic diagram of the diagnostic results of this application. In this application, Figure 3A or Figure 3B The graphic control page 11 can represent different states of the communication line by displaying drawings in different colors or in different forms, and the display results are as follows: Figure 4 In addition, the graphic control page 11 can indicate the abnormality of the peripheral device itself (i.e., the device connection abnormality) by marking with special symbols. Figure 4In the embodiment, the graphic control page 11 indicates through specific display drawings and special symbols (i.e., X symbols) that the communication line of the first peripheral device 31 is normal and the device connection is normal, the communication line of the second peripheral device 32 is normal but the device connection is abnormal, the communication line of the third peripheral device 33 is abnormal and the device connection is also abnormal, and the communication line of the fourth peripheral device 34 is normal and the device connection is normal.

[0059] When the user Figure 3A On the control page 11, you can see Figure 4 When the display result is shown, the user can click the graphic control element of the peripheral device (such as the third peripheral device 33) to be viewed through the human-machine interface of the server 1. Figure 3B As shown, the graphic control page 11 can trigger the display data card display area 113 to display the device data of the third peripheral device 33 in detail, so as to facilitate the user to perform maintenance.

[0060] See also Figure 5A and Figure 5B , which is a diagnostic flowchart of this application. Figure 5A and Figure 5B The specific execution steps of the diagnostic method of the present application are disclosed, and the diagnostic method is based on Figure 1 and Figure 2 The diagnostic system shown in FIG. 1 is implemented. First, the diagnostic system starts the communication diagnostic program (step S51). In the first embodiment, the diagnostic system can automatically start the communication diagnostic program after the server 1 is started. In the second embodiment, the diagnostic system can start the communication diagnostic program after receiving an external trigger (for example, executing the application installed in the server 1). In the third embodiment, the diagnostic system can start the communication diagnostic program when the server 1 starts to receive device data from one or more peripheral devices 3 through the network switch 2.

[0061] Next, the diagnostic system traverses all currently connected peripheral devices 3 (step S52), and determines whether the device data of each peripheral device 3 is received (step S53). In one embodiment, the diagnostic system sends an inquiry command to all currently connected peripheral devices 3 through the device communication receiving model 12, and receives a reply packet sent by each peripheral device 3 in response to the inquiry command, wherein the reply packet may include device data. In addition, the diagnostic system determines whether the reply of each peripheral device 3 is received respectively through the communication diagnostic model 13, that is, determines whether the device data of each peripheral device 3 is received respectively.

[0062] The technical feature of the present application is that if the diagnostic system successfully receives the device data of one of the peripheral devices 3, it means that the communication line between the diagnostic system and the peripheral device 3 is normal, so it is necessary to further check the connection status of the peripheral device 3. If the diagnostic system continues to fail to receive the device data of one of the peripheral devices 3, it means that the connection status of the peripheral device 3 is abnormal, so it is necessary to further check the communication line between the diagnostic system and the peripheral device 3.

[0063] Specifically, if the diagnostic system successfully receives the device data replied by one of the peripheral devices (e.g., the first peripheral device 31), it will be determined that the communication line between the first peripheral device 31 (and the network switch 2) is normal, and then the connection status of the first peripheral device 31 itself is diagnosed to be normal. If the diagnostic system cannot receive the device data replied by one of the peripheral devices (e.g., the second peripheral device 32), it will be determined that the second peripheral device 32 itself is abnormal (i.e., in a disconnected state), and then the communication line between the second peripheral device 32 (and the network switch 2) is diagnosed to be normal.

[0064] like Figure 5A and Figure 5B As shown, if the communication diagnosis model 13 determines in step S53 that the device data of the first peripheral device 31 is successfully received, the diagnosis system will directly identify that the communication line of the first peripheral device 31 is normal through the device communication status identification model 14 (step S54). Next, the communication status identification model 14 obtains the target data related to the connection from the device data of the first peripheral device 31, and determines the connection status of the first peripheral device 31 based on the target data. In one embodiment, the connection status of the peripheral device 3 includes a first category indicating that the communication line of the peripheral device 3 is normal and the device connection is normal, a second category indicating that the communication line of the peripheral device 3 is normal but the device connection is abnormal, and a third category indicating that the communication line of the peripheral device 3 is abnormal and the device connection is abnormal. The present application displays at least three different categories of diagnostic results in a visual manner, instantly and directly, so that the user can quickly and clearly know the current connection status of each peripheral device 3, and when any peripheral device 3 is abnormal, it is helpful for the user to better understand the location and cause of the fault.

[0065] Specifically, after identifying that the communication line of the first peripheral device 31 is normal in step S54, the device communication status recognition model 14 further parses the device data of the first peripheral device 31 according to the communication protocol of the first peripheral device 31 to determine whether the device data of the first peripheral device 31 has target data related to the connection (step S55). In one embodiment, if it is determined that the device data of the first peripheral device 31 does not have target data related to the connection according to the communication protocol, the device communication status recognition model 14 directly identifies that the device connection of the first peripheral device 31 is normal (step S56), and sets the connection status of the first peripheral device 31 to the first category (step S57).

[0066] In one embodiment, if it is determined according to the communication protocol that the device data of the first peripheral device 31 has target data related to the connection, the device communication state recognition model 14 further determines whether the target data has changed (step S58). Specifically, the target data may be, for example, the heartbeat of the first peripheral device 31 or a designated bit in a designated point, but is not limited thereto. If the target data has changed (for example, a regular change generated over time), it means that the first peripheral device 31 continues to operate and the diagnostic system can continue to receive device data. At this time, the device communication state recognition model 14 can recognize that the device connection of the first peripheral device 31 is normal (step S56), and set the connection state of the first peripheral device 31 to the first category (step S57). If it is determined in step S58 that the target data has not changed, the device communication state recognition model 14 recognizes that the device connection of the first peripheral device 31 is abnormal (step S59), and sets the connection state of the first peripheral device 31 to the second category (step S60).

[0067] If the communication diagnosis model 13 determines in step S53 that the device data of the second peripheral device 32 cannot be received, the diagnosis system will directly identify the disconnection of the second peripheral device 32 through the communication line identification model 15 (step S61), that is, identify the abnormal connection of the second peripheral device 32. Then, the communication line identification model 15 will further check the communication line between the second peripheral device 32 and the network switch 2 (step S62) when it is determined that the second peripheral device 32 is abnormal, and determine the connection status of the second peripheral device 32 based on the inspection result.

[0068] Specifically, after identifying that the second peripheral device 32 is disconnected in step S61, the communication line identification model 15 further detects the pin of the second peripheral device 32 through the communication protocol of the second peripheral device 32, or reads the communication port status of the second peripheral device 32 through the network switch 2 connected to the second peripheral device 32, thereby checking whether the communication line of the second peripheral device 32 is abnormal (step S63). In one embodiment, if the inspection result is normal (i.e., it is judged as no in step S63), the communication line identification model 15 identifies that the communication line of the second peripheral device 32 is normal (step S64), and sets the connection status of the second peripheral device 32 to the second category (step S65). If the inspection result is abnormal (i.e., it is judged as yes in step S63), the communication line identification model 15 identifies that the communication line of the second peripheral device 32 is abnormal (step S66), and sets the connection status of the second peripheral device 32 to the third category (step S67).

[0069] In this application, the diagnostic system will be based on Figure 5A and Figure 5B All the steps shown in FIG. 1 are for diagnosing all the peripheral devices 3 currently connected (for example, all the peripheral devices 3 displayed on the graphic control page 11). In other words, the diagnostic system will perform the following steps on all the peripheral devices 3 currently connected: Figure 5A and Figure 5B The steps shown in the figure are performed, and the corresponding connection status (belonging to the first category, the second category or the third category) is set for each peripheral device 3. In one embodiment, the user can set a refresh frequency (for example, every 100 milliseconds, every 500 milliseconds or every 1 second, etc.) for the diagnostic system. Thus, the diagnostic system can send the query command to each peripheral device 3 according to the refresh frequency, diagnose each peripheral device 3, set or update the corresponding connection status for each peripheral device 3 according to the diagnosis result, and record or update the connection status in the data register 18 (step S68).

[0070] In the present application, after the device communication status recognition model 14 recognizes that the connection status of a peripheral device 3 is the first category or the second category, it immediately writes the connection status into the data register 18. Similarly, after the communication line recognition model 15 recognizes that the connection status of a peripheral device 3 is the second category or the third category, it immediately writes the connection status into the data register 18. In the present application, the graphic refresh model 16 reads the latest connection status of each peripheral device 3 from the data register 18 according to the refresh frequency, and refreshes the display drawings of each peripheral device 3 in the graphic control page 11 according to these connection statuses. In one embodiment, the update frequency of the device communication status recognition model 14 and the communication line recognition model 15 for the data register 18 is synchronized with the update frequency of the graphic refresh model 16 for the graphic control page 11 (for example, the data register 18 and the graphic control page 11 are updated simultaneously through pipeline technology). In another embodiment, the updating frequency of the device communication state identification model 14 and the communication line identification model 15 for the data register 18 is not synchronized with the updating frequency of the icon refresh model 16 for the icon control page 11 .

[0071] Please also see Figure 6 , is a flowchart of the refresh diagram of this application. Figure 6 As shown, the diagnostic system starts the icon refresh program (step S71) according to the preset update frequency through the icon refresh model 16. In the icon refresh program, the icon refresh model 16 reads the storage data of one of all the peripheral devices 3 currently connected to the diagnostic system from the data register 18 (step S72), and obtains and determines the connection status of this peripheral device 3 based on the storage data (step S73). The connection status is, for example, the first category, the second category, and the third category described above. After step S73, the icon refresh model 16 refreshes the display drawings in the graphic control page 11 according to the connection status of the peripheral device 3 (step S74).

[0072] For example, if the connection status of the first peripheral device is the first category (i.e., the communication line of the first peripheral device is normal and the device connection is normal), the graphic refresh model 16 refreshes the display diagram of the first peripheral device on the graphic control page 11, so that the graphic control page 11 displays the communication line between the first peripheral device and the network switch 2 as normal in the first color (e.g., blue) or the first line (e.g., solid line), and does not display the special symbol representing the abnormal device connection on the graphic control element of the first peripheral device. If the connection status of the second peripheral device is the second category (i.e., the communication line of the second peripheral device is normal but the device connection is abnormal), the graphic refresh model 16 refreshes the display diagram of the second peripheral device on the graphic control page 11, so that the graphic control page 11 displays the communication line between the second peripheral device and the network switch 2 as normal in the first color (e.g., blue) or the first line (e.g., solid line), and displays the special symbol representing the abnormal device connection (e.g., X symbol) on the graphic control element of the second peripheral device. For another example, if the connection status of the third peripheral device is the third category (i.e., the communication line of the third peripheral device is abnormal and the device connection is abnormal), the graphic refresh model 16 refreshes the display diagram of the third peripheral device on the graphic control page 11, so that the graphic control page 11 displays the communication line abnormality between the third peripheral device and the network switch 2 in a second color (e.g., gray) or a second line (e.g., a dotted line), and displays a special symbol representing the device connection abnormality on the graphic control element of the third peripheral device.

[0073] Through the above technical means, the graphic refresh model 16 can update the graphic control page 11 in real time according to the data in the data register 18 , so that the user can instantly perceive the current connection status of each peripheral device 3 .

[0074] After step S74, the graphic refresh model 16 determines whether all peripheral devices 3 currently connected to the diagnostic system have been traversed (step S75). If all peripheral devices 3 have not been traversed, the graphic refresh model 16 executes steps S72 to S74 again to obtain the data of the next peripheral device 3 from the data register 18 and update the display diagram of the next peripheral device 3 on the graphic control page 11. Moreover, after traversing all peripheral devices 3, the graphic refresh model 16 temporarily ends the current graphic refresh procedure and starts the next graphic refresh procedure according to the update frequency.

[0075] See also Figure 7 and Figure 8 , which are respectively the third schematic diagram and the fourth schematic diagram of the graphic control page of this application. Figure 7A schematic diagram of the connection architecture display area 111 and the communication protocol display area 112 on the graphic control page 11 of the present application is shown, wherein the graphic control page 11 uses different colors or different lines to display the communication protocols used for communication between each peripheral device (such as Server, Controller, Relay, PMU and UPS, etc.) and the network switch (Switch) and their connection status, such as Ethernet RJ45, Ethernet Fiber, No Monitoring and RS485, etc.

[0076] Figure 8 The schematic diagram of the connection architecture display area 111, the communication protocol display area 112 and the data card display area 113 on the graphic control page 11 of the present application is shown. Figure 8 As shown, the control page 11 displays the communication protocols used by each peripheral device to communicate with the network switch and their connection status with different colors or lines, including the color or line representing the abnormal communication line (Connection Lost). In addition, the control page 11 also uses special symbols (such as X symbol) to represent the abnormal device connection of the peripheral device ( Figure 8 PMU is taken as an example).

[0077] At this time, if the user clicks on the graphic control element represented by the PMU through the human-machine interface, the device click model 17 of the diagnostic system will trigger the data card display area 113 of the graphic control page 11, so that the graphic control page 11 will display the connection status, basic data, device location and disconnection time of the PMU in the data card display area 113.

[0078] The diagnostic system and method of the present application can perform instant diagnosis when an abnormality occurs, and display the diagnostic results in a visual manner, so as to help users detect the cause of the fault and perform troubleshooting.

Claims

1. A device connection status self-diagnosis system, which is communicatively connected with a plurality of peripheral devices in an environment, and comprises: Picture control page; a communication diagnosis model configured to determine whether a device data of each peripheral device is received; a device communication status identification model configured to, upon receiving the device data of a first device among the plurality of peripheral devices, identify that a communication line of the first device is normal, and determine, based on the target data related to the connection in the first device, that the connection state of the first device is a first category or a second category, wherein the first category indicates that the communication line of the first device is normal and the device connection is normal, and the second category indicates that the communication line of the first device is normal but the device connection is abnormal; a communication line identification model configured to identify that a second device among the plurality of peripheral devices is disconnected when the device data of the second device is not received, and to determine that the connection state of the second device is the second category or the third category by checking the communication line of the second device, wherein the third category indicates that the communication line of the second device is abnormal and the device connection is abnormal; and The icon refresh model is configured to refresh the displayed illustrations of each peripheral device in the icon control page according to the connection status of each peripheral device.

2. The device connection status self-diagnosis system according to claim 1, wherein the graphic control page comprises: A connection structure display area configured to display the connection structure of the plurality of peripheral devices; a communication protocol display area configured to display the communication protocol used between each of the peripheral devices and the network switch; and A data card display area configured to display basic data of the third peripheral device clicked in the connection architecture display area, the connection status and the communication interruption time; Wherein, the connection status self-diagnosis system further includes a device click model, which is configured to trigger the data card display area when detecting that the third peripheral device is clicked.

3. The device connection status self-diagnosis system according to claim 1, further comprising a device communication receiving model configured to traverse the plurality of peripheral devices and respectively receive the device data of each of the peripheral devices. 4 . The device connection status self-diagnosis system according to claim 1 , wherein the target data is a heartbeat of the first device or a specified bit in a specified point.

5. A connection status self-diagnosis system for a device according to claim 4, wherein the device communication status identification model is configured to parse the device data of the first device according to the communication protocol of the first device to confirm the target data of the first device, and when the first device does not have the target data, directly identify the connection status of the first device as the first category.

6. A connection status self-diagnosis system for a device according to claim 1, wherein the communication line identification model is configured to detect the pin of the second device through the communication protocol of the second device, or to read the communication port status of the second device through a network switch connected to the second device to check whether the communication line of the second device is normal or abnormal.

7. The connection status self-diagnosis system of the device according to claim 1, further comprising a data register, wherein the device communication status identification model and the communication line identification model are configured to write the connection status of each of the peripheral devices into the data register, and the graphic refresh model is configured to read the connection status of each of the peripheral devices from the data register.

8. The device connection status self-diagnosis system according to claim 1, wherein the display diagram represents different connection statuses with different colors, and represents device connection abnormalities of each peripheral device with special symbols.

9. A method for self-diagnosis of the connection status of a device, applied to a connection status self-diagnosis system that is communicatively connected to a plurality of peripheral devices in an environment, and comprising: Step a) the self-diagnosis system determines whether the device data of each peripheral device is received; Step b) upon receiving the device data of a first device among the plurality of peripheral devices, the self-diagnosis system identifies that a communication line of the first device is normal; Step b1) after step b), judging the connection status of the first device as a first category or a second category according to the target data related to the connection in the first device, wherein the first category indicates that the communication line of the first device is normal and the device connection is normal, and the second category indicates that the communication line of the first device is normal but the device connection is abnormal; Step c) when the device data of a second device among the plurality of peripheral devices is not received, the self-diagnosis system identifies that the second device is disconnected; Step c1) after step c), by checking the communication line of the second device, determining whether the connection status of the second device is the second category or the third category, wherein the third category indicates that the communication line of the second device is abnormal and the device connection is abnormal; and Step d) The self-diagnosis system refreshes the display drawings of each peripheral device in the graphic control page according to the connection status of each peripheral device.

10. The method for self-diagnosis of the connection status of a device according to claim 9, wherein the target data is a heartbeat of the first device or a specified bit in a specified point.

11. The method for self-diagnosis of the connection status of a device according to claim 9, wherein the step b1) comprises: Step b11) parsing the device data of the first device according to the communication protocol of the first device to confirm the target data of the first device; as well as Step b12) directly identifying the connection status of the first device as the first category when the first device does not have the target data.

12. The method for self-diagnosis of the connection status of a device according to claim 9, wherein the step c1) includes detecting the pin of the second device through the communication protocol of the second device, or reading the communication port status of the second device through a network switch connected to the second device, so as to check whether the communication line of the second device is normal or abnormal.

13. The method for self-diagnosis of the connection status of a device according to claim 9, wherein the self-diagnosis system comprises a data register, and the method for self-diagnosis of the connection status further comprises: Step e) after step b1), writing the connection status of the first device into the data register; and Step f) after step c1), writing the connection status of the second device into the data register; Wherein, the step d) includes reading the connection status of each of the peripheral devices from the data register.

14. The device connection status self-diagnosis method according to claim 9, wherein the display diagram uses different colors to represent different connection states, and uses special symbols to represent device connection abnormalities of each peripheral device.

15. A non-transitory storage medium storing an application program, wherein the application program has a plurality of computer executable program codes, and when the plurality of computer executable program codes are executed, the connection status self-diagnosis method of the device as claimed in claim 9 can be implemented.

Images