Management system and sub board

The management system with a sub-board stabilizes computer operation by monitoring communication states and performing various restart processes, addressing the reboot challenges in routers with high CPU load, ensuring stable device communication.

JP2024167715AActive Publication Date: 2024-12-04KINDEN CORP

Patent Information

Application Number
JP2023083972
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Filing Date
2023-05-22
Publication Date
2024-12-04
Estimated Expiration
2043-05-22

AI Technical Summary

Technical Problem

Existing routers face challenges in rebooting themselves when the CPU load becomes high, leading to instability in connected devices due to the computer's inability to stabilize its operation, affecting communication methods like LAN, USB, and LTE.

Method used

A management system comprising a computer and a sub-board that communicates using multiple methods (USB, LAN, RS485) to monitor communication states and autonomously perform restart processes (software, hardware, power cycling, and self-reboot) to stabilize the computer's operation.

Benefits of technology

The system effectively stabilizes the computer's operation by autonomously restarting and managing power supply to connected devices, reducing instability and potential damage.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2024167715000001_ABST
    Figure 2024167715000001_ABST
Patent Text Reader

Abstract

To provide a management system capable of stabilizing operation of a computer at least.SOLUTION: A management system 10 includes a computer (PC) 1 and a sub board 2. The sub board 2 has a function of communicating with the PC 1. The sub board 2 has a function of communicating with a first device 101 in a first method, and a function of communicating with a second device 102 in a second method which is different from the first method. The sub board 2 executes first communication monitoring processing, second communication monitoring processing, and reboot processing. The first communication monitoring processing monitors a state of the communication in the first method. The second communication monitoring processing monitors a state of the communication in the second method. The reboot processing includes processing to reboot the PC 1 at least when a result of at least one communication monitoring processing of the first communication monitoring processing and the second communication monitoring processing satisfies a predetermined condition.SELECTED DRAWING: Figure 1
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present disclosure relates to management systems and sub-boards, and more particularly to management systems including a computer and a sub-board in communication with the computer. [Background technology]

[0002] Patent Document 1 describes a router that implements a function for rebooting itself when the load on the CPU becomes high, thereby initializing internal information and continuing normal operation. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2009-232358 A Summary of the Invention [Problem to be solved by the invention]

[0004] In the router described in Patent Document 1, if the operation of the CPU (computer) stops, it is difficult for the router to reboot itself.

[0005] In addition, a computer generally has multiple devices connected thereto via various methods such as LAN or USB so that they can communicate with each other, and even if the computer is not unstable enough to reboot itself, the operation of the devices may become unstable. In such a case, restarting the computer may stabilize the operation of the devices, and thus the operation of the computer may also become more stable.

[0006] An object of the present disclosure is to provide a management system and a sub-board that can at least stabilize the operation of a computer. [Means for solving the problem]

[0007] A management system according to an embodiment of the present disclosure includes a computer and a sub-board. The sub-board has a function of communicating with the computer. The sub-board has a function of communicating with a first device in a first method and a function of communicating with a second device in a second method. The second method is different from the first method. The sub-board executes a first communication monitoring process, a second communication monitoring process, and a restart process. The first communication monitoring process is a process of monitoring a state of communication in the first method. The second communication monitoring process is a process of monitoring a state of communication in the second method. The restart process includes a process of at least restarting the computer when a result of at least one of the first communication monitoring process and the second communication monitoring process satisfies a predetermined condition.

[0008] A sub-board according to one embodiment of the present disclosure has a function of communicating with a computer. The sub-board has a function of communicating with a first device in a first method and a function of communicating with a second device in a second method. The second method is different from the first method. The sub-board executes a first communication monitoring process, a second communication monitoring process, and a restart process. The first communication monitoring process is a process of monitoring a state of communication in the first method. The second communication monitoring process is a process of monitoring a state of communication in the second method. The restart process includes at least a process of restarting the computer when a result of at least one of the first communication monitoring process and the second communication monitoring process satisfies a predetermined condition. Effect of the Invention

[0009] The management system and sub-board disclosed herein have the effect of at least stabilizing the operation of a computer. [Brief description of the drawings]

[0010] [Figure 1] FIG. 1 is a block diagram of a computer system including a terminal (management system) according to a first embodiment of the present disclosure. [Diagram 2]FIG. 2 is a block diagram of a PC (computer) and a sub-board that constitute the terminal. [Diagram 3] FIG. 3 is a flow chart for explaining the processing of the sub-board according to the embodiment. [Figure 4] FIG. 4 is a flowchart illustrating the restart process included in the above process. [Diagram 5] FIG. 5 is a flowchart for explaining the process of the PC in the above embodiment. [Figure 6] FIG. 6 is a flowchart illustrating a part of the processing of a sub-board constituting a terminal according to the second embodiment of the present disclosure. [Figure 7] FIG. 7 is a flowchart illustrating another part of the above process. [Figure 8] FIG. 8 is a flowchart for explaining the process of the PC in the above embodiment. [Figure 9] FIG. 9 is a block diagram of a modified example of the terminal according to the above embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0011] (1) First embodiment The specific communication methods, specific processing procedures, and specific numerical values ​​of various thresholds given in the following description are merely examples and may be changed as appropriate.

[0012] (1-1) Computer System A terminal 10 according to the first embodiment of the present disclosure is used in, for example, a computer system 100 as shown in Fig. 1. The computer system 100 includes the terminal 10, an LTE (Long Term Evolution) router 20, a server 30, a first device 101, a second device 102, and a third device 103. The first device 101 has an RS485 connector, the second device 102 has a LAN (Local Area Network) connector, and the third device 103 has a USB (Universal Serial Bus) connector.

[0013] (1-2) Terminal The terminal 10 includes a computer 1 and a sub-board 2. The computer 1 is, for example, a personal computer (PC), and may be referred to as "PC 1" below. However, the computer 1 is not limited to being for personal use.

[0014] The sub-board 2 has a function of communicating with the computer 1 in both the USB and LAN systems. The sub-board 2 also has a function of communicating with the first device in the RS485 system, with the second device in the LAN system, and with the third device 103 in the USB system.

[0015] In addition, although LAN usually means a wiring system, in this disclosure, it is used to mean a communication system used in wiring of the LAN system. The LAN system is usually a wired LAN system (for example, Ethernet (registered trademark) system), but it may be a wireless LAN system.

[0016] In this embodiment, the sub-board 2 is connected to the computer 1 so as to be able to communicate with each other via the USB method and the LAN method. Therefore, the PC 1 can communicate with the sub-board 2 at all times. In addition, the first device 101 is connected to the sub-board 2 so as to be able to communicate with each other via the RS485 method, the second device 102 is connected to the sub-board 2 so as to be able to communicate with each other via the USB method. Therefore, the PC 1 can communicate with each of the first device 101, the second device 102, and the third device 103 at all times via the sub-board 2.

[0017] Furthermore, the sub-board 2 is communicatively connected to the LTE router 20 in a LAN manner. The LTE router 20 can be communicatively connected to the server 30 in a VPN manner. Therefore, when the LTE router 20 is communicatively connected to the server 30 in a VPN manner, the PC 1 can communicate with the server 30 via the sub-board 2 and the LTE router 20.

[0018] (1-2-1) Computer 2, the PC 1 includes a first CPU 11, a memory 12, an SSD 13, a LAN connector 14, two or more USB connectors 15, a chipset 17, and a DC power supply 18. The PC 1 is provided with a power switch SW1.

[0019] The first CPU 11 is capable of communicating with the memory 12, the SSD 13, the LAN connector 14, and each of the two or more USB connectors 15 via a chipset 17.

[0020] The DC power supply 18 is connected to the commercial power supply 40 via the AC adapter 3 and the sub-board 2, and supplies DC power for operating each of the first CPU 11, the memory 12, the SSD 13, and the chipset 17. The DC power supply 18 also supplies bus power to each of the two or more USB connectors 15, thereby achieving USB power supply to the third device 103 via the sub-board 2.

[0021] The first CPU 11 performs a monitoring process (hereinafter sometimes referred to as "USB communication monitoring process") to monitor whether or not there is USB communication (hereinafter sometimes referred to as "USB communication") between the PC 1 and the sub-board 2, and ultimately the third device 103, via the chipset 17.

[0022] Monitoring the presence or absence of communication includes judging the presence or absence of communication. The judgment of the presence or absence of USB communication performed by the first CPU 11 is, for example, judging whether or not a no-communication state (described later) is detected by the chipset 17. For example, first timing information regarding the timing to execute a USB communication monitoring process is stored in the memory 12 (or the SSD 13). The first CPU 11 judges whether the current time is the monitoring timing based on a comparison between current time information acquired from a built-in clock of the first CPU 11 and the first timing information stored in the memory 12, and executes the USB communication monitoring process and other processes in parallel (for example, multiple cores constituting the first CPU 11 in parallel, or a single core in time sharing).

[0023] The power switch SW1 starts and stops the supply of DC power from the DC power supply 18 to each of the first CPU 11, the memory 12, the SSD 13, the chipset 17, and the two or more USB connectors 15 (hereinafter, may be referred to as "power supply to the PC 1") in response to a manual operation. The power switch SW1 also has a function of stopping and restarting the power supply to the PC 1 in response to a signal from the sub-board 2.

[0024] That is, PC1 starts up when the power switch SW1 is turned on while the outlet of the terminal 10 is connected to the commercial power supply 40, and stops operation when the power switch SW1 is turned off. PC1 also receives a command from the sub-board 2 while in operation and is restarted. The restart here is a series of operations that terminates the operating system (OS) of PC1, performs a normal shutdown in which the power of PC1 is turned off, and then turns the power of PC1 on.

[0025] In addition to such normal restart, which will be described in detail later, the PC 1 can be forcibly shut down and restarted during operation via the power switch SW1 from the sub-board 2. Furthermore, the PC 1 can be stopped and restarted in response to the power supply from the sub-board 2 to the AC adapter 3 being stopped and restarted during operation.

[0026] (1-2-2) Sub-board As shown in FIG. 2, the sub-board 2 includes a second CPU 21, an AC / DC converter 22, a relay 23, a communication unit 24, two or more RS485 connectors 25, a LAN connector 26, a LAN hub 27, two or more LAN connectors 271, a USB hub 28, two or more USB connectors 281, a restart button BT1 and a shutdown button BT2.

[0027] The second CPU 21 is communicatively connected to each of the AC / DC converter 22, the relay 23, the communication unit 24, the LAN hub 27, the USB hub 28, the restart button BT1, and the shutdown button BT2.

[0028] The AC / DC converter 22 is connected to a commercial power source 40, converts a portion of the AC power from the commercial power source 40 into DC power, and supplies the converted DC power to each of the second CPU 21 and the LTE router 20. Another portion of the AC power from the commercial power source 40 is supplied to the AC adapter 3 via a relay 23. The AC adapter 3 converts the AC power supplied via the relay 23 into DC power, and supplies the converted DC power to the DC power source 18.

[0029] The relay 23, under the control of the second CPU 21, stops and resumes the supply of AC power to the AC adapter 3. Accordingly, the supply of DC power from the AC adapter 3 to the PC 1 (hereinafter, sometimes referred to as "power supply to the PC 1") is also stopped and resumed.

[0030] Each of the two or more LAN connectors 271 is connected to the LAN connector 14 on the PC1 side via the LAN hub 27. A second device 102 is connected to at least one of the two or more LAN connectors 271 via a LAN cable. The USB hub 28, under the control of the second CPU 21, connects the third device 103 connected to the USB connector 281 to the PC1 so as to be able to communicate with each other.

[0031] Each of the two or more USB connectors 281 is connected to one (USB connector 151) of the two or more USB connectors 15 on the PC1 side via a USB hub 28. A second device 102 can be connected to each of the two or more USB connectors 281 via a LAN cable. The USB hub 28 connects, under the control of the second CPU 21, a third device 103 connected to each of the two or more USB connectors 281 so as to be communicable with the PC1.

[0032] Each of the two or more RS485 connectors 25 is connected to another one (USB connector 152) of the two or more USB connectors 15 on the PC1 side via the communication unit 24. The first device 101 can be connected to each of the two or more RS485 connectors 25. The communication unit 24 receives a signal transmitted in the RS485 format from the first device 101 connected to each of the two or more RS485 connectors 25, converts the received signal into a USB format signal, and transmits the converted signal to the PC1. The communication unit 24 also receives a signal transmitted from the PC1 to the first device 101 in the USB format, and converts the received signal into a RS485 format signal. Then, the communication unit 24 outputs the converted signal to the RS485 connector 25 corresponding to the first device 101, which is the destination of the signal from the PC1, among the two or more RS485 connectors 25, under the control of the second CPU 21. In this way, the communication unit 24 performs conversion between the USB system and the RS485 system, so that the first device 101 connected to each of the two or more RS485 connectors 25 can communicate with the PC 1.

[0033] The second CPU21 performs a monitoring process (hereinafter, sometimes referred to as "RS485 communication monitoring process") to monitor the presence or absence of communication in the RS485 system (hereinafter, sometimes referred to as "RS485 communication") between the sub-board 2 and the first device 101 via the communication unit 24. The monitoring of the presence or absence of RS485 communication (determination of whether or not there is a no-communication state) performed by the second CPU21 is, for example, a determination of whether or not the no-communication state has been detected by the communication unit 24.

[0034] The second CPU 21 also performs a monitoring process (hereinafter, sometimes referred to as a "LAN communication monitoring process") to monitor the presence or absence of communication in a LAN system (hereinafter, sometimes referred to as "LAN communication") between the PC 1 and the sub-board 2, and further the second device 102, via the LAN hub 27. The monitoring of the presence or absence of LAN communication (determination of whether or not there is a no-communication state) performed by the second CPU 21 is, for example, a determination of whether or not a no-communication state has been detected by the LAN hub 27.

[0035] Then, the second CPU21 executes the restart process when at least one of the monitoring results of the RS485 communication monitoring process and the LAN communication monitoring process satisfies a predetermined condition.

[0036] For example, second timing information regarding the timing for executing each of the RS485 communication monitoring process and the LAN communication monitoring process is stored in the built-in memory of the second CPU 21. The second CPU 21 judges whether the current time is the timing for monitoring the RS485 method and the LAN method based on a comparison between the current time information acquired from the built-in clock of the second CPU 21 and the second timing information stored in the built-in memory, and executes the RS485 communication monitoring process and the LAN communication monitoring process in parallel.

[0037] (1-2-3) Specified condition: No communication condition In this embodiment, the predetermined condition is a no-communication condition, for example, a condition in which no communication continues for a predetermined period of time or more.

[0038] (1-2-4) No communication state A no-communication state is a state in which there is no communication for a predetermined period of time or more. A no-communication state is, for example, a state in which the amount of communication (communication speed) per unit time is zero, but may also include a state in which the communication speed is so slow that it can be considered to be zero.

[0039] (1-2-5) Restart process In this embodiment, the restart process includes a first restart process, a second restart process, a third restart process, and a fourth restart process.

[0040] The first restart process is a process equivalent to a software reboot, but is performed automatically by the sub-board 2, not by manual operation. In a software reboot of a general computer, a restart command is sent to the PC1 in response to a manual operation, such as selecting restart from the OS shutdown menu or pressing the software restart button BT1. In addition, although details will be described later, in this embodiment, the restart command can be sent in response to pressing the hardware restart button BT1 provided on the sub-board 2.

[0041] The second restart process is equivalent to a hardware reboot, but is performed automatically by the sub-board 2, not by manual operation. In a typical computer hardware reboot, for example, a forced shutdown is performed by pressing and holding the power button, and then the power is turned on by pressing the power button briefly. In addition, although details will be described later, in this embodiment, the shutdown can be performed in response to pressing a shutdown button BT2 by hardware provided on the sub-board 2.

[0042] The third restart process is equivalent to plugging and unplugging the power cord, but is not performed manually but is automatically performed via the power switch SW1 on the sub-board 2. In a typical computer, the AC side of the AC adapter 3 is connected to the power outlet of the commercial power source 40 and the DC side of the AC adapter 3 is connected to the computer, and power supply to the computer is stopped and restarted by plugging and unplugging the power cord from the commercial power source 40.

[0043] The fourth restart process is equivalent to a self-reboot of a computer, but the subject and target of the reboot is the second CPU 21 of the sub-board 2, and is automatically performed by the second CPU 21 itself. Note that in the fourth restart process, in addition to the self-reboot of the second CPU 21, it is preferable that devices other than the second CPU 21 (such as the communication unit 24, the LAN hub 27, and the USB hub 28) are also restarted.

[0044] In the sub-substrate 2, the second CPU 21 repeatedly judges whether the no-signal condition is satisfied. Then, when it is judged that the no-signal condition is satisfied, if the first restart process has not been executed, the first restart process is executed. Also, when it is judged that the no-signal condition is satisfied, if the first restart process has been executed and the second restart process has not been executed, the second restart process is executed. Furthermore, when it is judged that the no-signal condition is satisfied, if the second restart process has been executed and the third restart process has not been executed, the third restart process is executed. Then, when it is judged that the no-signal condition is satisfied, if the third restart process has been executed and the fourth restart process has not been executed, the fourth restart process is executed.

[0045] In this embodiment, the timing (order) of execution of the first restart process to the fourth restart process as described above is managed by the first flag to the fourth flag. More specifically, when it is determined that the no-communication condition is satisfied, if the first flag is in a reset state, the first restart process is executed. Also, when it is determined that the no-communication condition is satisfied, if the first flag is in a set state and the second flag is in a reset state, the second restart process is executed. Furthermore, when it is determined that the no-communication condition is satisfied, if the second flag is in a set state and the third flag is in a reset state, the third restart process is executed. And when it is determined that the no-communication condition is satisfied, if the third flag is in a set state and the fourth flag is in a reset state, the fourth restart process is executed.

[0046] (1-2-6) Alert transmission If the determination result remains that the non-communication condition is satisfied even after the third restart process is performed, the second CPU 21 transmits an alert to the server 30. The alert includes warning information that the operation of the PC 1 may be unstable, notification information that the restart process by the sub-board 2 has been performed, and identification information for identifying the terminal 10.

[0047] The server 30 receives the alert and outputs the received alert. The administrator of the computer system 100 recognizes from the alert output from the server 30 that the operation of the PC 1 in the terminal 10 has become unstable, and that the PC 1 has not stabilized even after being rebooted by the sub-board 2. This enables the administrator to take measures such as maintenance of the terminal 10 as soon as possible.

[0048] The second CPU21 is electrically connected to a signal line (USB cable) between the communication unit 24 and the USB connector 152 on the PC1 side, and monitors the power supplied from the USB connector 152 (hereinafter, sometimes referred to as "USB bus power"), and detects a shutdown of PC1 based on a change in the USB bus power (e.g., detecting a shutdown of PC1).

[0049] In detail, when PC1 is shut down, the power supply from the USB connector 152 stops and the voltage of the USB bus power drops, for example, from 5 V to 0 V. Therefore, the second CPU21 can detect the shutdown of PC1 based on the change in the voltage of the USB bus power from 5 V to 0 V.

[0050] When the restart button BT1 is pressed, the second CPU21 transmits a restart command to the PC1 via the LAN hub 27 or the USB hub 28. The PC1 receives the restart command and performs a restart. In other words, the PC1 can also be restarted by a manual operation via the restart button BT1 on the sub-board 2 side. Therefore, the terminal 10 can perform both the first restart process that is automatically executed by the sub-board 2 and the normal restart by the restart button BT1 on the PC1.

[0051] When the shutdown button BT2 is pressed, the second CPU 21 transmits a shutdown command to the PC 1 via the LAN hub 27 or the USB hub 28. That is, the PC 1 can also be shut down by manual operation via the shutdown button BT2 on the sub-board 2. Therefore, the terminal 10 can perform both the second restart process automatically executed by the sub-board 2, the normal shutdown by the shutdown button BT2, and the power on by the power switch SW1 on the PC 1.

[0052] (1-3) Example of operation (1-3-1) Example of sub-board operation The sub-board 2 (second CPU 21) operates, for example, according to the flowcharts shown in Figures 3 and 4. The processes in Figures 3 and 4 are started in response to the start-up of the sub-board 2 and are ended in response to the stop of operation. The sub-board 2 is started, for example, when the outlet of the terminal 10 is connected to the commercial power supply 40.

[0053] 3, first, the sub-board 2 (second CPU 21) resets each flag (step S1). The flags are the first flag to the fourth flag.

[0054] The first flag is a flag indicating that PC1 has been restarted. The second flag is a flag indicating that PC1 has been forced to shut down. The third flag is a flag indicating that power supply to PC1 has been stopped and restarted. The fourth flag is a flag indicating that the sub-board 2 itself has been restarted.

[0055] Next, the sub-board 2 (second CPU 21) judges whether it is time to monitor the RS485 communication based on the second timing information stored in the built-in memory (step S2). If it is judged that it is not time to monitor the RS485 communication (No in step S2), the process proceeds to step S4.

[0056] If it is determined in step S2 that it is time to monitor the RS485 communication (Yes), the sub-board 2 (second CPU 21) executes the RS485 communication monitoring process (step S3), after which the process proceeds to step S6.

[0057] If it is determined in step S2 that it is not the timing to monitor RS485 communication (No), the sub-board 2 (second CPU 21) determines whether it is the timing to monitor LAN communication based on the second timing information (step S4). If it is determined that it is the timing to monitor LAN communication (Yes in step S4), the sub-board 2 (second CPU 21) executes LAN communication monitoring processing (step S5). Then, the processing proceeds to step S6.

[0058] In step S6, the sub-board 2 (second CPU 21) judges whether or not a no-communication state has been detected by at least one of the RS485 communication monitoring process in step S3 and the LAN communication monitoring process in step S5 (step S6). If it is judged that a no-communication state has not been detected by either the RS485 communication monitoring process or the LAN communication monitoring process (No in step S6), the process returns to step S1.

[0059] If it is determined in step S6 that a non-communication state has been detected by at least one of the RS485 communication monitoring process and the LAN communication monitoring process (Yes), the sub-board 2 (second CPU 21) determines whether the fourth flag is set (step S7). If it is determined that the fourth flag is set (Yes in step S7), the process ends.

[0060] If it is determined in step S7 that the fourth flag is not set (No: that is, the fourth flag is reset), the sub-substrate 2 (second CPU 21) executes a restart process (step S8). After that, the process returns to step S2.

[0061] If it is determined in step S4 that it is not the timing to monitor LAN communication (No), the sub-board 2 (second CPU 21) determines whether or not a USB reset command has been received from PC 1 (step S9). If it is determined that a USB reset command has not been received from PC 1 (No in step S9), the process returns to step S2.

[0062] If it is determined in step S9 that the USB reset command has been received (Yes), the sub-board 2 (second CPU 21) stops and resumes the USB power supply to the third device 103 via the USB hub 28 (processing equivalent to plugging in and unplugging the third device 103 from the USB connector 281) (step S10). This restarts the third device 103 connected to the USB connector 281. After that, the process returns to step S2.

[0063] The restart process in step S8 is executed, for example, according to the flowchart in FIG.

[0064] In the restart process, first, the sub-substrate 2 (second CPU 21) judges whether the first flag is set (step S801). If it is judged that the first flag is set (Yes in step S801), the process proceeds to step S804.

[0065] If it is determined in step S801 that the first flag is not set (No: that is, the first flag is reset), the sub-substrate 2 (second CPU 21) restarts the PC1 (processing equivalent to a software reboot) (step S802). Next, the sub-substrate 2 (second CPU 21) sets the first flag (step S803). After that, the process returns to the upper flowchart (see FIG. 3).

[0066] If it is determined in step S801 that the first flag is set (Yes), the sub-board 2 (second CPU 21) determines whether the second flag is set (step S804). If it is determined that the second flag is set (Yes in step S804), the process proceeds to step S807.

[0067] If it is determined in step S804 that the second flag is not set (No: that is, the second flag is reset), the sub-board 2 (second CPU 21) performs a forced shutdown and startup of PC1 (processing equivalent to a hardware reboot) (step S805). Next, the sub-board 2 (second CPU 21) sets the second flag (step S806). After that, the process returns to the upper flowchart (see FIG. 3).

[0068] If it is determined in step S804 that the second flag is set (Yes), the sub-board 2 (second CPU 21) determines whether the third flag is set (step S807). If it is determined that the third flag is set (Yes in step S807), the process proceeds to step S810.

[0069] If it is determined in step S807 that the third flag is not set (No: that is, the third flag is reset), the sub-board 2 (second CPU 21) stops and restarts the power supply to PC 1 (processing equivalent to plugging and unplugging the power cord) (step S808). Next, the sub-board 2 (second CPU 21) sets the third flag (step S809). After that, the process returns to the upper flowchart (see FIG. 3).

[0070] If it is determined in step S807 that the third flag is set (Yes), the sub-substrate 2 (second CPU 21) sends an alert to the server 30 (step S810). Next, the sub-substrate 2 (second CPU 21) restarts (self-reboots) the sub-substrate 2 itself (step S811) and sets the fourth flag (step S812). After that, the process returns to the upper flowchart (see FIG. 3).

[0071] (1-3-2) PC operation example The PC1 (first CPU 11) operates, for example, according to the flowchart shown in Fig. 5. The process in Fig. 5 is started in response to the start-up of the PC1, and is ended in response to the stop of the operation.

[0072] First, the PC1 (first CPU 11) judges whether or not it is time to monitor USB communication based on the first timing information stored in the memory 12 (step S11). If it is judged that it is not time to monitor USB communication (No in step S11), the process proceeds to step S15.

[0073] If it is determined in step S11 that it is time to monitor USB communication (Yes), the PC1 (first CPU11) executes a USB communication monitoring process (step S12). Next, the PC1 (first CPU11) determines whether or not a no-communication state has been detected by the USB communication monitoring process in step S11 (step S13). If it is determined that a no-communication state has not been detected by the USB communication monitoring process (No in step S13), the process returns to step S11.

[0074] If it is determined in step S13 that a non-communication state has been detected (Yes), the PC1 (first CPU11) transmits a USB reset command to the sub-board 2 (step S14). After that, the process returns to step S11.

[0075] If it is determined in step S11 that it is not the timing to monitor the USB communication (No), the PC1 (first CPU11) executes other processes (processes other than the USB communication monitoring process) (step S15), and then the process returns to step S11.

[0076] (1-3-3) Modification of the first embodiment In the following, the description of the already mentioned items will be omitted or simplified, and only the differences from the first embodiment will be described in detail.

[0077] In this modified example, the second CPU 21 monitors the presence or absence of RS485 communication via the communication unit 24, monitors the presence or absence of LAN communication via the LAN hub 27, and further monitors the presence or absence of USB communication via the USB hub 28. Note that the monitoring of the presence or absence of USB communication (determination of whether or not there is a no-communication state) performed by the second CPU 21 is, for example, a determination of whether or not a no-communication state has been detected by the USB hub 28.

[0078] Then, the second CPU21 executes the restart process when the monitoring result regarding the communication in at least one of the RS485 method, the LAN method, and the USB method satisfies a predetermined condition (a non-communication condition).

[0079] 4, the alert in step S810 may be sent, for example, after the fourth flag is set in step S812, rather than when it is determined in step S807 that the third flag is set. In this case, the notification information included in the alert may be supplemented with a statement that the sub-board 2 has also performed a self-reboot. This allows the administrator of the computer system 100 to recognize that the operation of PC1 in the terminal 10 has become unstable, and that PC1 has not stabilized even after undergoing a reboot process by the sub-board 2 and then rebooting (self-rebooting) itself. This eliminates the need for the administrator to perform maintenance on the terminal 10 when PC1 stabilizes due to the self-reboot of the sub-board 2.

[0080] In this modified example, the RS485 system may be replaced with other serial communication systems, such as the RS422 system or the RS232C system.

[0081] In this modified example, instead of or in addition to monitoring the presence or absence of communication (determining whether or not there is a no-communication state), the presence or absence of a communication error may be monitored. The sub-substrate 2 (second CPU 21) may perform a restart process, for example, when the number of communication errors occurring per unit time is equal to or greater than a threshold value. Alternatively, the sub-substrate 2 (second CPU 21) may perform a restart process, for example, when there is no communication and when the number of communication errors occurring per unit time is equal to or greater than a threshold value.

[0082] In this modification, commercial power supply 40 may be replaced with a non-commercial AC power supply. Also, AC / DC converter 22 built into sub-board 2 may be replaced with a power supply block externally attached to sub-board 2.

[0083] In this modification, the LTE router 20 may be replaced with a router other than LTE (for example, a router compatible with 5G). The communication between the server 30 and the LTE router 20 may be performed by a method other than VPN (for example, a method compatible with the general Internet).

[0084] (1-4) Advantages of the First Embodiment According to this embodiment, by restarting PC1 based on the communication status in the RS485 system and the LAN system corresponding to the first device 101 and the second device 102, it is possible to effectively stabilize the operation of at least PC1 in the terminal 10 equipped with PC1.

[0085] In this embodiment, the sub-board 2 monitors the communications in the RS485 system and the LAN system (determines whether the RS485 communication and the LAN communication are in a no-communication state), and the PC 1 monitors the communications in the USB system (determines whether the USB communication is in a no-communication state). When the USB communication becomes a no-communication state, the PC 1 stops and restarts the power supply to the third device 103 in the USB system, thereby restarting the third device 103 and stabilizing the PC 1.

[0086] In addition, by sending a restart command (an operation equivalent to a software reboot) before turning the power of PC1 off and on (an operation equivalent to a hardware reboot), it is possible to stabilize the operation of PC1 while minimizing damage to PC1.

[0087] In addition, if the operation of PC1 does not stabilize even after turning the power of PC1 off and on, the operation of PC1 can be stabilized by stopping and resuming the power supply to PC1 (an operation equivalent to unplugging and plugging the power supply back in).

[0088] In addition, even if the communication state is lost via either the RS485 system or the LAN system, the PC 1 can be rebooted.

[0089] (2) Second embodiment In the following, the description of the points in common with the first embodiment will be omitted or simplified, and the points of difference will be described in detail.

[0090] One difference is that the sub-board 2 monitors USB communication in addition to RS485 communication and LAN communication, and executes a restart process if at least one of RS485 communication, LAN communication, and USB communication becomes non-communicative.

[0091] Another difference is that the sub-board 2 manages the timing and number of times that the four types of processes included in the restart process (four types of processes corresponding to software reboot for PC1, hardware reboot for PC1, unplugging and plugging PC1 into the power outlet, and self-reboot of the sub-board 2: see Figure 4) are executed based on the number of times PC1 is shut down.

[0092] The number of shutdowns is the number of times PC1 is shut down during the period in which the no-communication condition is continuously satisfied (i.e., the period in which the no-communication state continues). The initial value of the number of shutdowns is 0, and it is incremented every time PC1 is shut down while the no-communication state continues, and is reset to 0 when the no-communication state is released.

[0093] Another difference is that PC1 performs alive monitoring of the second CPU21 on the sub-board 2 (processing of FIG. 8) instead of performing USB communication monitoring processing and sending a USB reset command if a no-communication state is detected as a result of this (processing of FIG. 5).

[0094] (2-1) Sub-board The second CPU 21 monitors whether or not there is RS485 communication via the communication unit 24, and whether or not there is LAN communication via the LAN hub 27, and further monitors whether or not there is USB communication (hereinafter sometimes referred to as "USB communication") between the PC 1 and the sub-board 2 and ultimately the third device 103 via the USB hub 28.

[0095] Then, the second CPU21 executes the restart process when the monitoring result regarding the communication in at least one of the RS485 method, the LAN method, and the USB method satisfies a predetermined condition (a non-communication condition).

[0096] The second CPU21 detects the shutdown of the PC1 based on the change in the USB bus power, and also counts the number of times (n number of shutdowns) that the PC1 has shut down during a period in which the no-signal condition is continuously satisfied. Then, the second CPU21 controls the timing (sequence) and number of times of execution of each of the first restart process, the second restart process, the third restart process, and the fourth restart process based on the number of shutdowns n.

[0097] In detail, when the second CPU21 determines that the no-signal condition is satisfied, if the number of shutdowns n is, for example, 1 or less (i.e., 0 or 1), it executes a first restart process; if the number of shutdowns is 2, it executes a second restart process; if the number of shutdowns is 3, it executes a third restart process; and if the number of shutdowns is 4, it executes a fourth restart process.

[0098] As a result, the first restart process is executed in response to the change in the determination result regarding the no-signal condition from a determination result that the no-signal condition is not satisfied to a determination result that the no-signal condition is satisfied. If the determination result that the no-signal condition is satisfied remains even after the first first restart process is executed in this way, the second first restart process is executed. If the determination result that the no-signal condition is satisfied remains even after the second restart process is executed, the third restart process is executed. Then, if the determination result that the no-signal condition is satisfied remains even after the third restart process is executed, the fourth restart process is executed.

[0099] In this way, in the sub-board 2, whether or not the no-signal condition is satisfied is repeatedly determined by the second CPU 21. Then, if the number of shutdowns n when it is determined that the no-signal condition is satisfied is 1 or less (n=0 or 1n=1), the second CPU 21 executes the first restart process, if n=2, the second restart process, if n=3, the third restart process, and if n=4, the fourth restart process.

[0100] Therefore, if there is no change in the state in which the no-signal condition is satisfied, the first restart process will be executed twice, the second restart process once, the third restart process once, and the fourth restart process once, in that order.

[0101] (2-2) PC The first CPU 11 performs USB communication monitoring processing, and transmits a USB reset command when a no-communication state is detected by the USB communication monitoring processing, and instead performs alive monitoring of the second CPU 21 on the sub-board 2 side. For example, the memory 12 further stores third timing information regarding the timing of alive monitoring of the second CPU 21.

[0102] (2-3) Example of operation (2-3-1) Example of sub-board operation The sub-board 2 (second CPU 21) executes the processes shown in the flowcharts of FIG. 6 and FIG. 7 with respect to RS485 communication (that is, RS485 communication monitoring and restart process).

[0103] 6, first, the sub-substrate 2 (second CPU 21) sets the number of shutdowns n to an initial value of 0 (step S21). Next, the sub-substrate 2 (second CPU 21) determines whether or not RS485 communication is present (step S22), and if it is determined that RS485 communication is present (Yes in step S22), the process returns to step S22.

[0104] If it is determined in step S22 that there is no RS485 communication (No), the sub-board 2 (second CPU 21) measures a no-communication time t1 related to RS485 communication. The no-communication time t1 can be measured, for example, by resetting and starting a timer in response to the end of detection of RS485 communication. Next, the sub-board 2 (second CPU 21) determines whether the no-communication time t1 is equal to or longer than a predetermined time (e.g., 5 minutes) (step S24). If it is determined that the no-communication time t1 is not equal to or longer than 5 minutes (No in step S24: i.e., less than 5 minutes), the process returns to step S22.

[0105] If it is determined in step S24 that the time is 5 minutes or more (Yes), the sub-board 2 (second CPU 21) determines whether the number of shutdowns n is a predetermined number or less (e.g., 2 times or less: n≦2) (step S25), as shown in Fig. 7. If it is determined that the number of shutdowns n is not 2 times or less (No in step S25: that is, n≧3), the process proceeds to step S33.

[0106] If it is determined in step S25 that the number of shutdowns n is 2 or less (Yes), the sub-board 2 (second CPU 21) shuts down PC 1 (step S26). In addition to shutting down PC 1, it is preferable to turn off and on the power (for example, stop and resume USB power supply) of devices other than the sub-board 2 (for example, the third device 103 connected to the USB connector 281 of the sub-board 2) in step S26.

[0107] Next, the sub-board 2 (second CPU 21) determines whether the voltage V of the USB bus is equal to or lower than a predetermined value (the predetermined value is, for example, 0 V or a value small enough to be regarded as 0 V) ​​(step S27). If it is determined that the voltage V is equal to or lower than the predetermined value (Yes in step S27), the process proceeds to step S31.

[0108] If it is determined in step S27 that the voltage V is not equal to or less than the predetermined value (No: that is, the voltage V exceeds the predetermined value), the sub-board 2 (second CPU 21) determines whether the no-communication time t1 exceeds a predetermined value (for example, t1>10 minutes) (step S28). If it is determined that the no-communication time t1 does not exceed the predetermined value (No in step S28: that is, t1≦10 minutes), the process returns to step S27.

[0109] If it is determined in step S28 that the non-communication time t1 exceeds the predetermined value (Yes), the sub-board 2 (second CPU 21) determines whether the number of shutdowns n is 1 or less (n≦1) (step S29). If it is determined that the number of shutdowns n is not 1 or less (No in step S29: that is, n=2), the process proceeds to step S32.

[0110] If it is determined in step S29 that the number of shutdowns n is 1 or less (Yes), the sub-board 2 (second CPU 21) forcibly shuts down PC1 (step S30). In this process, the detection target for the non-communication state is RS485 communication, and since both USB communication and LAN communication can be performed between PC1 and the sub-board 2, the forced shutdown in step S30 is performed in at least one of USB communication and LAN communication (for example, USB communication). Then, the process proceeds to step S31.

[0111] In step S31, the sub-board 2 (second CPU 21) turns on the power supply of the PC 1 via the switch SW1. After that, the process proceeds to step S35.

[0112] If it is determined in step S29 that the number of shutdowns n is not 1 or less (No: that is, n=2), the sub-substrate 2 (second CPU 21) stops and restarts the power supply to the PC 1 via the relay 23 (step S32). After that, the process proceeds to step S35.

[0113] If it is determined in step S25 that the number of shutdowns n is not 2 or less (No: that is, n≧3), the sub-board 2 (second CPU 21) determines whether the number of shutdowns n is 3 (n=3) (step S33). If it is determined that the number of shutdowns n is not 3 (No in step S33: that is, n≧4), the process proceeds to step S36.

[0114] In step S35, the sub-board 2 (second CPU 21) increments the number of shutdowns n. After that, the process returns to step S22 (see FIG. 6).

[0115] In step S36, the sub-board 2 (second CPU 21) issues an alert to the server 30. After that, the process ends.

[0116] Furthermore, the sub-board 2 (second CPU 21) further executes the same process as above for LAN communication, that is, a process in which "RS485" is replaced with "LAN" in the flowcharts shown in Figures 6 and 7 (LAN communication monitoring and restart process). However, in the LAN communication monitoring and restart process, the detection target for a non-communication state is LAN communication, and since there is a possibility that only USB communication can be performed between PC1 and the sub-board 2, the forced shutdown in step S30 is performed via USB communication.

[0117] Furthermore, the sub-board 2 (second CPU 21) further executes the same process as above with respect to USB communication, that is, a process (USB communication monitoring and restart process) in which "RS485" is replaced with "USB" in the flowcharts shown in Figs. 6 and 7. However, in the USB communication monitoring and restart process, the detection target for the non-communication state is USB communication, and since there is a possibility that only LAN communication can be performed between PC1 and the sub-board 2, the forced shutdown in step S30 is performed via LAN communication.

[0118] It should be noted that the RS485 communication monitoring and restart processing, the LAN communication monitoring and restart processing, and the USB communication monitoring and restart processing are executed in parallel by, for example, a single core or a plurality of cores of the second CPU 21.

[0119] (2-3-2) Example of sub-board operation The PC1 (first CPU 11) operates, for example, according to the flowchart shown in Fig. 8. The process in Fig. 8 starts when the PC1 is started, and ends when the operation is stopped.

[0120] First, the PC1 (first CPU 11) judges whether it is time to perform alive monitoring of the second CPU 21 based on the third timing information stored in the memory 12 (step S41). If it is judged that it is not time to perform alive monitoring of the second CPU 21 (No in step S41), the process proceeds to step S46.

[0121] If it is determined in step S41 that it is time to perform alive monitoring of the second CPU21 (Yes), the PC1 (first CPU11) performs alive monitoring of the second CPU21 through the alive monitoring process of the following steps S42 to S44. That is, the PC1 (first CPU11) determines whether or not there is a signal from the second CPU21 (step S42). If it is determined that there is a signal from the second CPU21 (Yes in step S42), the process proceeds to step S46.

[0122] If it is determined in step S42 that there is no signal from the second CPU21 (No), the PC1 (first CPU11) measures the no-signal time t2 (step S43). The no-signal time t2 can be measured, for example, by resetting and starting a timer in response to the end of detection of a signal from the second CPU21. Next, the PC1 (first CPU11) determines whether the no-signal time t2 is equal to or longer than a predetermined time (for example, t2≧6 minutes 30 seconds) (step S44). If it is determined that the no-signal time t2 is not equal to or longer than the predetermined time (No in step S44: that is, t2<6 minutes 30 seconds), the process returns to step S42.

[0123] If it is determined in step S44 that the no-signal time t2 is equal to or longer than the predetermined time (Yes), the PC1 (first CPU 11) restarts the second CPU 21 (step S45). Note that the restart of the second CPU 21 is performed, for example, by transmitting a restart command from the first CPU 11 to the second CPU 21 through at least one of LAN communication and USB communication. After that, the process returns to step S41.

[0124] If it is determined in step S41 that it is not the timing to perform alive monitoring of the second CPU 21 (No), the PC 1 (first CPU 11) executes other processing (processing other than alive monitoring processing: for example, processing related to energy management, which will be described later) (step S46). After that, the processing returns to step S41.

[0125] (2-4) Modification of the second embodiment In the following, the description of the already mentioned items will be omitted or simplified, and only the differences from the second embodiment will be described in detail.

[0126] In this modification, as shown in Fig. 9, the sub-board 2 further includes a self-reboot chip 29, and the process of Fig. 8 is executed by the self-reboot chip 29. In this case, in the process of Fig. 8, the "other process" of step S46 is an internal process of the sub-board 2 (no process may be executed). This makes it possible for the sub-board 2 to self-reboot even if both the USB communication and the LAN communication between the PC 1 and the sub-board 2 are in a non-communication state.

[0127] The self-reboot chip 29 may be, for example, a watchdog timer (hereinafter, referred to as "watchdog timer 29"). In this case, the second CPU 21 transmits a signal (for example, a signal indicating the survival of the second CPU 21 itself) to the watchdog timer 29 at a predetermined cycle (for example, once every three minutes). The watchdog timer 29 executes, for example, the process of FIG. 8 except for steps S41 and S46.

[0128] In detail, the watchdog timer 29 first determines in step S42 whether or not there is a signal from the second CPU 21. If the determination result in step S42 is that there is a signal (Yes), the process returns to step S42. If the determination result in step S42 is that there is no signal (No), steps S43 to S45 are executed. Then, after execution of step S45, the process returns to step S42. As a result, when the no-signal time t2 during which there is no signal from the second CPU 21 reaches a time (e.g., 6 minutes 30 seconds) obtained by adding a predetermined time (e.g., 30 seconds) to a time (6 minutes) equivalent to twice the period in which a signal is transmitted from the second CPU 21.

[0129] In this modification, the PC1 (first CPU11) may further transmit a USB reset command (processing equivalent to the processing of FIG. 5 performed in the first embodiment) when the result of the USB communication monitoring processing indicates a no-communication state. The sub-board 2 (second CPU21) may further stop and resume the USB power supply in response to the USB reset command.

[0130] Also, in this modified example, the sub-board 2 (second CPU 21) may perform RS485 communication monitoring and restart processing and LAN communication monitoring and restart processing, but not USB communication monitoring and restart processing. Or, the sub-board 2 (second CPU 21) may only perform RS485 communication monitoring and restart processing, but not LAN communication monitoring and restart processing and USB communication monitoring and restart processing. In general, the sub-board 2 (second CPU 21) may perform only one or any two of the RS485 communication monitoring and restart processing, LAN communication monitoring and restart processing, and USB communication monitoring and restart processing.

[0131] Furthermore, the terminal 10 in this modified example may be configured so that the PC 1 (first CPU 11) can not only transmit a restart command to the sub-substrate 2 (second CPU 21), but also forcefully shut down the sub-substrate 2 (second CPU 21) and further stop and resume power supply to the sub-substrate 2. In that case, in step S45, the restart of the second CPU 21 may be performed stepwise, for example, by transmitting a restart command, forcefully shutting down, and stopping and resuming power supply to the sub-substrate 2.

[0132] (2-5) Advantages of the Second Embodiment According to this embodiment, by restarting PC1 based on the communication status of each of the RS485 method, LAN method, and USB method corresponding to the first device 101, the second device 102, and the third device 103, it is possible to more effectively stabilize the operation of at least PC1 in the terminal 10 equipped with PC1.

[0133] In addition, by sending a restart command (an operation equivalent to a software reboot) before turning the power of PC1 off and on (an operation equivalent to a hardware reboot), it is possible to stabilize the operation of PC1 while minimizing damage to PC1.

[0134] In addition, if the operation of PC1 does not stabilize even after turning the power of PC1 off and on, the operation of PC1 can be stabilized by stopping and resuming the power supply to PC1 (an operation equivalent to unplugging and plugging the power supply back in).

[0135] In addition, if the operation of PC1 does not stabilize even after stopping and resuming power supply to PC1, an attempt can be made to stabilize the operation of the sub-board 2 and therefore PC1 by restarting the sub-board 2 itself (an operation equivalent to a self-reboot).

[0136] In addition, even if any of the RS485 method, LAN method, and USB method becomes non-communicative, the PC 1 can be rebooted.

[0137] Furthermore, it is possible to manage the execution order and the number of executions for the first to fourth four types of restart processing (S26 and S31, S30 and S31, S32, and S34) based on the number of shutdowns n.

[0138] In addition, by monitoring the USB bus power from PC1, it is possible to easily detect the shutdown of PC1.

[0139] (3) Specific examples (3-1) First concrete example The computer system 100 of the first or second embodiment is, for example, a system (energy management system) that performs energy management in a small store such as a convenience store.

[0140] The server 30 is installed, for example, in a headquarters that manages a plurality of stores. The terminal 10 is installed in each of the plurality of stores together with the LTE router 20 and the first device 101 to the third device 103. The first device 101 is, for example, an air conditioner, the second device 102 is, for example, a cooling device, and the third device is, for example, an office device. The PC 1 constituting the terminal 10 is, for example, an AI controller (hereinafter, referred to as "AI controller 1"). The AI ​​controller 1 performs energy management of the store in which the terminal 10 is installed (for example, reducing power consumption while improving the in-store environment, etc.) in cooperation with the server 30 or independently. When the AI ​​controller 1 becomes unstable, the sub-board 2 constituting the terminal 10 executes three types of reboot processing corresponding to software reboot, hardware reboot, and plugging / unplugging the AI ​​controller 1 in stages. This allows the AI ​​controller 1 to be stabilized while suppressing damage to the AI ​​controller 1 in the terminal 10.

[0141] Furthermore, if the AI ​​controller 1 does not stabilize even after the above-mentioned restart process has been performed on the AI ​​controller 1, the sub-board 2 can be further rebooted to further increase the possibility of stabilizing the AI ​​controller 1. Additionally, by sending an alert to the server 30, it is possible to support manual measures, such as having an administrator visit the store and perform maintenance on the terminal 10.

[0142] The target of energy management is not limited to small stores, but may be large stores or even places other than stores (for example, offices, etc.).

[0143] (3-2) Second Specific Example The computer system 100 of the first or second embodiment may be, for example, a control system that controls digital signage.

[0144] The server 30 is installed, for example, in an advertising agency that advertises using digital signage. The terminal 10 is installed, for example, in an advertiser's store together with the LTE router 20, and the first device 101 to the third device 103 are installed inside and outside the store. The first device 101 is, for example, a large outdoor electronic signboard, the second device 102 is, for example, a small indoor electronic signboard, and the third device is, for example, a tablet terminal. The PC 1 constituting the terminal 10 is, for example, an AI controller 1, and the AI ​​controller 1 controls the digital signage connected to the terminal 10 in cooperation with the server 30 or independently. When the AI ​​controller 1 becomes unstable, the sub-board 2 of the terminal 10 performs three types of restart processing for the AI ​​controller 1 and self-reboots the sub-board 2 in stages as necessary, and also transmits an alert to the server 30 at an appropriate timing. This makes it possible to automatically deal with malfunctions in the digital signage and further to support manual dealing with them. As a result, for example, the burden on advertisers regarding the management of digital signage can be reduced.

[0145] (4) Other modifications In the above description, the terminal 10 may be a management system (hereinafter, referred to as "management system 10") that includes a PC1 and a sub-board 2. In the management system 10, the PC1 and the sub-board 2 may be separate entities. In other words, the PC1 and the sub-board 2 do not have to be housed in a single housing. The sub-board 2 may be, for example, externally attached to the PC1, or may be installed in a location away from the PC1. [Explanation of symbols]

[0146] 10 Terminal (Management System) 1. Computer 2 Sub-board 101 1st device 102 2nd device 103 Third equipment

Claims

1. A computer, a sub-board having a function of communicating with the computer; The sub-substrate is A function of communicating with a first device in a first manner; and a function of communicating with a second device in a second method different from the first method; The sub-substrate is a first communication monitoring process for monitoring a state of communication in the first method; a second communication monitoring process for monitoring a state of communication in the second method; a restart process including at least a process of restarting the computer when a result of at least one of the first communication monitoring process and the second communication monitoring process satisfies a predetermined condition. Management system.

2. the sub-board further has a function of communicating with the computer in a USB system and a LAN system, The first system is an RS485 system, the second method is the LAN method, The first communication monitoring process is an RS485 communication monitoring process that monitors whether or not communication is occurring in the RS485 system, The second communication monitoring process is a LAN communication monitoring process that monitors whether or not communication is occurring in the LAN system, The predetermined condition is a no-communication condition that a no-communication state in which no communication has occurred for a predetermined period of time or more has been detected, the restart process includes a process of restarting the computer when a result of at least one of the RS485 communication monitoring process and the LAN communication monitoring process satisfies the non-communication condition. The management system according to claim 1 .

3. The sub-board further has a function of communicating with a third device in the USB system, The sub-board further executes a USB communication monitoring process for monitoring a state of communication in the USB system, the restart process includes a process of restarting the computer when a result of at least one of the RS485 communication monitoring process, the LAN communication monitoring process, and the USB communication monitoring process satisfies the non-communication condition. The management system according to claim 2.

4. The restart process is When the result of the RS485 communication monitoring process satisfies the non-communication condition, restarting the computer by communication in at least one of the LAN method and the USB method; When the result of the LAN communication monitoring process satisfies the non-communication state, restarting the computer by communication in the USB system; and when the result of the USB communication monitoring process satisfies the non-communication condition, restarting the computer by communication using the LAN system. The management system according to claim 3.

5. the restart process is a process of restarting the computer when a result of at least one of the RS485 communication monitoring process and the LAN communication monitoring process satisfies the non-communication condition, The sub-board further has a function of communicating with a third device in the USB system, The computer includes: Executing a USB communication monitoring process for monitoring the state of communication in the USB system; When a result of the USB communication monitoring process satisfies the non-communication condition, the power supply from the sub-board to the third device by the USB method is stopped and then resumed. The management system according to claim 2.

6. The restart process is a first restart process for sending a restart command to the computer when the predetermined condition is satisfied; a second restart process for turning off and on the power of the computer if the predetermined condition remains satisfied after the restart command is sent by the first restart process; The management system according to any one of claims 1 to 5.

7. the restart process further includes a third restart process for stopping and restarting power supply to the computer when the predetermined condition remains satisfied after the power supply to the computer is turned off and on by the second restart process; The management system according to claim 6.

8. The restart process further includes a fourth restart process for restarting the sub-board when the predetermined condition remains satisfied even after the power supply to the computer is stopped and then resumed by the third restart process. The management system according to claim 7.

9. the restart process counts the number of times the computer is shut down during a period in which the predetermined condition is satisfied, and sequentially executes the first restart process, the second restart process, the third restart process, and the fourth restart process based on the counting result; The management system according to claim 8.

10. the sub-board has a function of communicating with the computer at least in a USB format; the restart process further includes a process of detecting that the computer has been shut down based on a change in bus power supplied from the computer in the USB system; The management system according to claim 9.

11. A sub-board having a function of communicating with a computer, The sub-substrate is A function of communicating with a first device in a first manner; and a function of communicating with a second device in a second method different from the first method; The sub-substrate is a first communication monitoring process for monitoring a state of communication in the first method; a second communication monitoring process for monitoring a state of communication in the second method; a restart process including at least a process of restarting the computer when a result of at least one of the first communication monitoring process and the second communication monitoring process satisfies a predetermined condition. Sub-board.

Citation Information

Patent Citations

  • USB connection system, USB device, and host

    JP2006048496A

  • Relay device, circuit switching system, and circuit switching method

    JP2015226141A

  • Electronic apparatus

    JP2018094720A

  • Communication system, relay transmission apparatus, router device and communication method

    JP2009232358A

Cited By

  • Processing circuit, processing method, and program

    JP2026153253A

  • Processing circuit, processing method, and program

    JP7935193B2

  • Braking system for a rail-mounted traveling unit of a transfer vehicle

    US20240383456A1