Automated production method for dual-machine hot standby of panel products

Abstract

The present invention discloses a dual-machine hot standby automated production technology for panel products. The AP1 and AP2 boards are connected and form a CC Link loop with the PLCs of other devices. BC board 1 and BC board 2 back up each other. When one board goes down or initiates a switch operation, the Active signal of the other board automatically turns on. The BC system executes the logic for starting the service based on the board signal changes. The boards of the primary and backup systems use heartbeats to determine whether the other BC is alive. The BC monitors the board error signal and determines the board status to decide whether to perform the switch operation. The BC dual-machine hot standby technology of this application is a first in the panel industry. To perform a version change operation, the backup BC system can be deployed and started first, and then the primary BC system can be deployed and started. The new version of the BC can then be used to provide services, greatly shortening the version change time and thus achieving rapid tape-out production.

Description

Technical Field

[0001] The present application relates to the field of automated production technology, and specifically to a dual-machine hot standby automated production technology for panel products. Background Art

[0002] During panel production, the system monitors status changes such as system downtime, board power outages, and system power outages in the production BC system, enabling rapid switching of the BC system to production. This shortens troubleshooting time and the time it takes to bring new system versions online, improving production capacity. Technological innovations include support for simultaneous dual-system releases without downtime, regular data writes to boards, and a heartbeat mechanism to detect abnormal status in the backup system or server. This allows the backup service to automatically initiate a master-slave switch when the primary service experiences a downtime or anomaly. The backup server automatically replaces the primary server for production, synchronizing data resources and ensuring data consistency between the primary and backup services.

[0003] Currently, BC systems in the panel industry are deployed in a single-point deployment model. If a server cabinet experiences a power outage, overload, or other issues, causing system downtime, the equipment will cease to function properly. Troubleshooting and system board replacements require significant downtime, impacting production line capacity. Summary of the Invention

[0004] The present invention provides a dual-machine hot standby automated production technology for panel products, the purpose of which is to quickly realize system replacement and production, thereby achieving rapid wafer production.

[0005] This application is achieved through the following technical solutions:

[0006] Panel product dual-machine hot standby automated production technology connects AP1 and AP2 boards and forms a CC Link loop with the PLC of other equipment. BC board 1 and BC board 2 back up each other. When one board fails or initiates a switch operation, the Active signal of the other board automatically turns on. The BC system executes the service startup logic based on the board signal changes. The boards in the active and standby systems use heartbeats to determine whether the other BC is alive. The BC monitors the board error signals and determines the board status to decide whether to switch.

[0007] As a preferred embodiment, the heartbeat is to first write data into SW0018, then monitor the on / off event of the board SB0118, and locally write the board SB0018 to turn on / off.

[0008] As a preferred embodiment, BC bundles are divided into two types: Normal bundle and Switch bundle.

[0009] As a preferred embodiment, the Normal bundle is a bundle that does not require development control when the BC is started, and the SwitchbundleBC is a bundle that is started through the startSwitchBundle() method program: the bc-client-bundle and the sesc connection / rv connection bundle.

[0010] As a preferred embodiment, during the active / standby switching process, the active / standby client service client-service-bundle is load balanced through nginx.

[0011] As a preferred embodiment, the posting method between the main and standby systems BC is processed using public reids, and the data is interoperable, realizing fast switching of the dual-machine hot standby system and consistency of the account data after switching, so that it can be put into production quickly.

[0012] As a preferred embodiment, the situations in which active / standby switching is initiated include the server actively initiating active / standby switching, system switching due to user program errors, server shutdown or power outage, and data link abnormality.

[0013] As a preferred embodiment, the situation of initiating the master-slave switch includes the situation where the server actively initiates the master-slave switch. Specifically, if the master-slave switch is initiated by system A, system A writes SB0000 of the hardware board to On and SW000D to 0x0001. The bottom layer of the main board communicates with the standby board and writes SW001D9 of the system B board. After system B finds that SW001D9 is On, it starts its own Switchbundle and writes SB000E and SW000E address bits to inform the board. During card establishment communication, the corresponding values ​​are written to the address bits SB01D8, SW01DA, and SW01DB of the main board. After system A reads the change in its own board address, it switches to the backup system, and system B switches to the primary system. If system B initiates the primary-backup switch, system A writes SB0000 to On and SW000D to 0x8001 on the hardware board. The bottom layer of the main board communicates with the backup board and writes SW001D9 on board B. After system B finds that SW001D9 is On, it starts its own switch bundle and writes the address bits SB000E and SW000E to inform the board. When the board establishes communication, the corresponding values ​​are written to the address bits SB01D8, SW01DA, and SW01DB of the main board. After system A reads the change in its own board address, it switches to the backup system, and system B switches to the primary system.

[0014] As a preferred embodiment, the server is shut down ( Figure 5 ) or a power outage occurs ( Figure 6 ), data link abnormality ( Figure 7), etc. Specifically, when system A is operating as the primary system and a system A board stops functioning, or the server where system A is located loses power or experiences an abnormality, system B detects the data link failure with system A through the CC-Link IE controller network. System B sets the cause and notification of the system switching notification (SB01D9, SW01D9). System B's application detects the system switching notification (SB01D9) and changes it from OFF to ON. If necessary, it checks the cause of the system switching notification (SW01D9). System B's application acquires control data from the control system to the backup system from the control system PC. System B transfers the acquired control data from the control system to the backup system. System B's application changes the user program's operation, and the user program sends data to the control system (starts updating and sending data). System B's application sets the system switching notification response details (SWO0OE). System B's application turns off the system switching notification response (SB000E) and turns ON the system switching notification response (SBO0OE). System B switches from the backup system to the control system. System B changes the system switching notification (SB01D9) from ON to OFF. System B's application changes the system switching notification response (SBO0OE) from ON to OFF.

[0015] As a preferred embodiment, the system switching in the event of a user program error specifically involves a switch bundle failure in the user program, i.e., the main system, resulting in malfunction. The application layer verifies functional functionality by periodically triggering test process tasks. If the program fails to execute the process properly due to an anomaly, the main system initiates a master-slave switchover. Based on these scenarios, the dual-machine hot standby automated production function allows for rapid system replacement and commissioning in extreme situations such as production system failures and power outages, enabling rapid tape-out.

[0016] Beneficial effects: The BC dual-machine hot standby of this application is the first of its kind in the panel industry. When the BC system is in dual-machine hot standby, when the active BC system goes down, the backup BC system will start to provide the corresponding bundle service; when performing a version change operation, you can first deploy and start the backup BC system, and then deploy and start the main BC system, or initiate a system service switching operation through the BC OPI client, so that the new version of BC can be used to provide services, greatly shortening the version change time, thereby achieving rapid tape-out production. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] Figure 1 This is a diagram showing the CC Link loop formed by connecting the AP1 and AP2 boards to the PLCs of other devices.

[0018] Figure 2 This is a diagram showing BC board 1 and BC board 2 backing up each other.

[0019] Figure 3 Schematic diagram of the server actively initiating active / standby switching.

[0020] Figure 4 Schematic diagram of initiating active / standby switchover for system B.

[0021] Figure 5 Schematic diagram of the scenario when the main service is down.

[0022] Figure 6 Schematic diagram of the scenario when the main service is powered off.

[0023] Figure 7 Diagram showing that the main service data link is abnormal and cannot be connected.

[0024] Figure 8 This is a diagram of system switching when a user program error occurs. DETAILED DESCRIPTION

[0025] The following is a detailed description of an embodiment of the present invention in conjunction with the accompanying drawings: This embodiment is implemented on the premise of the technical solution of the present invention, and a detailed implementation method and specific operation process are given, but the protection scope of the present invention is not limited to the following embodiment.

[0026] Panel product dual-machine hot standby automated production technology connects AP1 and AP2 boards and forms a CC Link loop with the PLC of other equipment. BC board 1 and BC board 2 back up each other. When one board fails or initiates a switch operation, the Active signal of the other board automatically turns on. The BC system executes the service startup logic based on the board signal changes. The boards in the active and standby systems use heartbeats to determine whether the other BC is alive. The BC monitors the board error signals and determines the board status to decide whether to switch.

[0027] The heartbeat is to first write data to SW0018, then monitor the on / off events of board SB0118, and locally write board SB0018 to turn on / off.

[0028] BC bundles are divided into two types: Normal bundle and Switch bundle.

[0029] Normal bundle is a bundle that does not require development control when BC is started. Switch bundleBC starts the bundle through the startSwitchBundle() method program: bc-client-bundle and sesc connection / rv connection bundle.

[0030] During the active / standby switchover process, the active / standby client service client-service-bundle is load balanced through nginx.

[0031] The posting method between the primary and standby systems BC is processed using public reids. The data is interoperable, realizing the rapid switching of the dual-machine hot standby system and the consistency of the account data after the switch, so that it can be put into production quickly.

[0032] The situations in which active / standby switching is initiated include the server actively initiating active / standby switching, system switching due to user program errors, server shutdown or power outage, and data link abnormality.

[0033] The situation of initiating the master-slave switch includes the situation where the server actively initiates the master-slave switch. Specifically, if system A initiates the master-slave switch, system A writes SB0000 of the hardware board to On and SW000D to 0x0001, the bottom layer of the main board communicates with the standby board, and writes SW001D9 of the B system board. After system B finds that SW001D9 is On, it starts its own Switch bundle and writes SB000E and SW000E address bits to inform the board. The board establishes communication and writes corresponding values ​​to the SB01D8, SW01DA, and SW01DB address bits of the main board. After system A reads the change in its own board address bit, it switches to the standby system, and system B switches to the main system. If system B initiates the master-slave switch, system A writes SB0000 of the hardware board to On and SW000D to 0x8001, the bottom layer of the main board communicates with the standby board, and writes SW001D9 of the B board. After system B finds that SW001D9 is On, it switches its own Switch The bundle starts and writes the SB000E and SW000E address bits to inform the board. When the board establishes communication, it writes the corresponding values ​​to the SB01D8, SW01DA, and SW01DB address bits of the main board. After system A reads the change in its own board address bits, it switches to the backup system, and system B switches to the main system.

[0034] The server is down ( Figure 5 ) or a power outage occurs ( Figure 6 ), data link abnormality ( Figure 7), etc. Specifically, when system A is operating as the primary system and a system A board stops functioning, or the server where system A is located loses power or experiences an abnormality, system B detects the data link failure with system A through the CC-Link IE controller network. System B sets the cause and notification of the system switching notification (SB01D9, SW01D9). System B's application detects the system switching notification (SB01D9) and changes it from OFF to ON. If necessary, it checks the cause of the system switching notification (SW01D9). System B's application acquires control data from the control system to the backup system from the control system PC. System B transfers the acquired control data from the control system to the backup system. System B's application changes the user program's operation, and the user program sends data to the control system (starts updating and sending data). System B's application sets the system switching notification response details (SWO0OE). System B's application turns off the system switching notification response (SB000E) and turns ON the system switching notification response (SBO0OE). System B switches from the backup system to the control system. System B changes the system switching notification (SB01D9) from ON to OFF. System B's application changes the system switching notification response (SBO0OE) from ON to OFF.

[0035] The system switching in the event of a user program error specifically involves a switchbundle failure in the user program (i.e., the main system), resulting in improper operation. The application layer verifies functionality by periodically triggering test process tasks. If the program fails to execute the process properly due to an anomaly, the main system initiates a master-slave switchover. Based on these scenarios, the dual-machine hot standby automated production function allows for rapid system replacement and commissioning in extreme situations where production cannot continue, such as a production system failure or power outage, thereby enabling rapid tape-out.

[0036] The basic principles, main features, and advantages of the present invention are shown and described above. Those skilled in the art should understand that the present invention is not limited to the above embodiments. The above embodiments and descriptions are merely illustrative of the principles of the present invention. Various changes and modifications may be made to the present invention without departing from the spirit and scope of the present invention. Such changes and modifications are intended to fall within the scope of the present invention. The scope of protection claimed in the present invention is defined by the appended claims and their equivalents.

Claims

1. A dual-machine hot standby automated production method for panel products, characterized in that: The AP1 and AP2 boards are connected and form a CCLink loop with the PLCs of other devices. AP1 and AP2 boards back up each other. When either board fails or initiates a switchover operation, the Active signal of the other board automatically turns on. The BC system executes the service startup logic based on the board signal changes. AP1 and AP2 boards use heartbeats to determine whether the other is alive. The BC system monitors the board error signals to determine the board status and decide whether to switch. The heartbeat is to first write data to SW0018, then monitor the on / off events of the board SB0118, and then write the board SB0018 locally to turn it on / off; BC bundles are divided into two types: Normal bundle and Switch bundle; Normal bundle is a bundle that does not require development control when BC is started. Switch bundle is a bundle that BC starts through the startSwitchBundle() method program: bc-client-bundle and sesc connection / rv connection bundle; During the active / standby switchover process, the active / standby client service bundle is load balanced through nginx. The posting method between the primary and standby systems uses a common ReIDs to process data. The data is interoperable, enabling fast switching of the dual-machine hot standby system and consistency of accounting data after switching. The situations in which active / standby switching is initiated include the server actively initiating active / standby switching, system switching due to user program errors, server shutdown or power outage, and data link abnormality. The situation of initiating active / standby switching includes the server actively initiating active / standby switching. Specifically, if system A initiates active / standby switching, system A writes SB0000 of board AP1 to On and SW000D to 0x0001. The main board AP1 communicates with the standby board AP2 at the bottom layer. AP1 writes SW001D9 and SB001D9 of board AP2 of system B. After the application of system B finds that SB001D9 is On, it switches itself to active / standby. The bundle starts and simultaneously changes SB000E and SW000E of board AP2 from Off to On. After board AP2 detects that SB000E is On, it writes the corresponding values ​​to the address bits SB01D8, SW01DA, and SW01DB of main board AP1 of system A. System A reads the address bit change of its own board AP1 and switches to the backup system, while system B switches to the primary system. If it is system B that initiates the primary-backup switchover, system B writes SB0000 and SW000D of board AP2. The main board bottom layer communicates with the backup board and writes SW001D9 of board AP1 of system A. After system A detects that SW001D9 is On, it starts its own switch bundle and writes the address bits SB000E and SW000E to inform board AP1. Board AP1 writes the corresponding values ​​to the address bits SB01D8, SW01DA, and SW01DB of board AP2. System B reads the address bit change of its own board AP2 and switches to the primary system. The server shuts down or has a power outage or data link abnormality. Specifically, when system A is running as the main control system, the A system board stops and cannot run, or the server where the A system is located has a power outage or an abnormality occurs, the B system board detects the stop of the A system data link through the CC-LinkIE controller network, and the B system board AP2 automatically changes the switching reason SW01D9 and the notification signal SB01D9 from OFF to ON. The B system application detects the notification from the board AP2, the B system application synchronizes the control data on the A system, and then sets the system switching notification response details SW000E, and changes the system switching notification response SB000E from OFF to ON. After the B system board AP2 receives the B application system notification response signal, it switches from the backup system to the main control system. The B system board AP2 changes the system switching notification SB01D9 from ON to OFF, and the B system application changes the system switching notification response SB000E from ON to OFF. After the above is completed, after the A system abnormality is resolved, the B system automatically switches from the backup system to the main control system.

2. The panel product dual-machine hot standby automated production method according to claim 1, characterized in that: The system switching when the user program is wrong is specifically when the user program, that is, the main system, has a switch bundle pseudo-death situation, resulting in abnormal operation. The application layer verifies whether the function is normal by regularly triggering the test process task. If the program has an abnormality and the process is not executed normally, the main system will initiate the master-slave switching process.

Images