Multi-connector cluster control method, system, main control computer and media
By centrally processing parameters through the main control computer and utilizing the distributed clock synchronization mechanism of the real-time communication bus network, the problem of poor synchronization accuracy caused by independent PLC control in multi-connector production lines is solved, realizing efficient multi-connector cluster control and improving the automation integration and collaboration of the production line.
Patent Information
- Application Number
- CN202611011552.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-07-07
- Publication Date
- 2026-11-17
AI Technical Summary
In existing technologies, the independent control of PLCs in multi-connector production lines results in poor synchronization accuracy of physical actions when linking across devices, making it difficult to meet the clustering and automation requirements of smart factories.
The system employs a main control computer to centrally process operation parameters, completes protocol conversion through a motion control card, and utilizes the distributed clock synchronization mechanism of a real-time communication bus network to achieve high-precision synchronous control of multiple docking stations.
It improved the changeover efficiency and automation integration level of the production line, eliminated information silos, and achieved highly collaborative and consistent operation of multiple docking stations.
Smart Images

Figure CN123113643A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of automation control technology, and in particular to a multi-connector cluster control method, system, master control computer and medium. Background Technology
[0002] In modern surface mount technology (SMT) and through-hole package (DIP) production lines, the feeder platform serves as a core node for material transfer between different process equipment. Its main functions are conveying materials such as PCB boards and adjusting track width. Current production lines generally employ an independent control architecture with a single programmable logic controller (PLC) and a local human-machine interface (HMI). When faced with scenarios involving multiple feeders working in tandem, such as product changeovers and width adjustments, this architecture suffers from extremely poor synchronization accuracy between the independent PLCs executing cross-equipment actions. This easily leads to lag or incoordination, resulting in low production efficiency and making it difficult to meet the clustering and automation requirements of smart factories. Summary of the Invention
[0003] This application relates to a multi-connector cluster control method, system, main control computer and medium, which is mainly used to solve the technical problem of extremely poor synchronization accuracy of physical actions when each independent PLC performs cross-device linkage actions in traditional solutions.
[0004] A multi-connector cluster control method, applied to a main control computer, the method comprising: Obtain the target operation parameters for multiple docking stations in the target production line; The validity of the target operation parameters is verified, and standardized bus instructions are generated after the verification is passed. The standardized bus commands are sent to the motion control card, which then converts them into a control data stream conforming to the real-time bus protocol format. Through a real-time communication bus network, the control data stream is synchronously sent to each of the connecting station slaves using a distributed clock synchronization mechanism, so as to control each of the connecting station slaves to synchronously execute physical actions using the synchronization signal generated by the distributed clock synchronization mechanism. Receive real-time operation data from each of the aforementioned connection station slave stations, and determine the cluster operation status of the multiple connection station slave stations based on the real-time operation data.
[0005] Furthermore, obtaining the target operating parameters for multiple feeder stations in the target production line includes: The application programming interface is built based on the built-in Hypertext Transfer Protocol service. Using the application programming interface, an asynchronous access request issued by an external system through a general network is received, and the target job parameters in the object spectrum protocol format are parsed from the asynchronous access request.
[0006] Furthermore, the validity verification of the target operation parameters includes: The asynchronous access request is sequentially subjected to instruction format verification, parameter value range verification, and operation permission verification for the external system. If any of the aforementioned checks fails, an error response message is returned to the external system via the general network.
[0007] Furthermore, the standardized bus commands include parameter configuration commands and action trigger commands; controlling each of the connected station slaves to synchronously execute physical actions includes: The control data stream corresponding to the parameter configuration command is issued to synchronously update the target track width value of the driver in each of the connecting station slave stations; The control data stream corresponding to the action trigger command is sent out to synchronously control the motors in each of the connecting stations to perform track width adjustment or material conveying actions.
[0008] Furthermore, receiving real-time operational data fed back by each of the connecting station slaves through the real-time communication bus network includes: Receive SMEMA signals, the mechanical interface standard for surface mount equipment, collected from each of the aforementioned docking stations; Determining the cluster operation status of the multiple connection station slave stations based on the real-time operation data includes: Based on the SMEMA signal of the surface mount equipment mechanical interface standard, it is determined whether the upstream docking station is in a material release state and whether the downstream docking station is in a material receiving request state. If all conditions are met, the conveyor motors of the upstream and downstream feeder stations are synchronously triggered through the real-time communication bus network to complete the material transfer across equipment.
[0009] Furthermore, determining the cluster operation status of the multiple connection station slave stations based on the real-time operation data includes: If all the received real-time operation data indicate that the physical action has been completed, then the cluster operation status is determined to be a synchronization completion status. Based on the synchronization completion status, a successful operation response message is sent to the external system through the application programming interface.
[0010] Furthermore, determining the cluster operation status of the multiple connection station slave stations based on the real-time operation data includes: If any of the received real-time operating data is an abnormal signal indicating a malfunction, an emergency stop command is broadcast to each of the connecting station slaves via the motion control card to control each of the connecting station slaves to stop its current physical action and remain in its current physical position.
[0011] A multi-connector cluster control system includes: The main control computer is used to execute the multi-connector cluster control method as described in any of the foregoing descriptions. The motion control card is plugged into the main control computer and serves as the master station of the real-time communication bus network. The real-time communication bus network uses a bus-type cascaded topology to connect the motion control card with multiple docking station slaves. A general network connects the main control computer to external systems; The main control computer is equipped with a first communication interface for connecting to the general network and a second communication interface for connecting to the real-time communication bus network, so as to separate the non-real-time command interaction link from the synchronous motion control link.
[0012] A master control computer, comprising: Processor and memory; The memory stores a computer program that, when executed by the processor, implements any of the methods described above.
[0013] A computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the method.
[0014] As can be seen, in this embodiment, by centrally processing and verifying the operation parameters on the main control computer, completing the protocol conversion via the motion control card, and using the distributed clock mechanism of the high real-time bus network to drive each slave station, a one-to-many centralized control path is constructed. This mode completely breaks the information silo phenomenon caused by traditional single-machine independent control, eliminates the tedious process of on-site personnel manually inputting parameters for each device, and ensures a high degree of coordination and consistency of the entire group of machines when performing physical actions such as width adjustment or material handover through synchronization signals, significantly improving the efficiency of production line changeover and the level of automation integration. Attached Figure Description
[0015] To more clearly illustrate the technical solutions of the embodiments of this application, the drawings used in the description of the embodiments of this application will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0016] Figure 1 This is a schematic diagram of a system architecture for a multi-connector cluster control system according to one embodiment of this application; Figure 2 This is a schematic diagram of an EtherCAT bus topology architecture according to one embodiment of this application; Figure 3 This is a flowchart illustrating a multi-connector cluster control method according to an embodiment of this application; Figure 4 This is a schematic diagram of the first-level connection relationship of a single-device slave station cascade topology structure (taking a dual-track dual-segment connection station as an example) in one embodiment of this application. Detailed Implementation
[0017] To make the technical problems, technical solutions, and beneficial effects solved by this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.
[0018] To facilitate understanding, before describing the embodiments of this application, the relevant terms / concepts involved in the embodiments of this application will be introduced, including: Surface Mount Technology (SMT) is the mainstream production technology in the electronics assembly industry. It is mainly used for processes such as chip mounting and soldering on PCB boards. Its production line includes multiple automated machines working together. Dual In-line Package (DIP): This technology is used in the assembly line of plug-in electronic components and complements the SMT production line. Both require a docking station to realize the material transfer between equipment. EtherCAT bus: A real-time industrial Ethernet communication bus with microsecond-level communication synchronization accuracy and multi-slave cascading capability, enabling high-speed and highly reliable distributed control. It is the core communication solution for high-precision motion control in industry. Ethernet network: General Ethernet (TCP / IP protocol suite), used for non-real-time remote command interaction, adapting to the remote communication needs of Web API; WebAPI Interface: An application programming interface based on the HTTP / HTTPS protocol, using POST+JSON data format, used by external systems such as MES to remotely send control commands and parameters to the main control PC; Connecting platform: Material transfer equipment used to connect different process equipment in SMT / DIP production line. Its core functions are conveying PCB boards / electronic components and adjusting track width. It is the core node of material flow in the production line. The Surface Mount Equipment Manufacturers Association (SMEMA) standard is used for material transfer and basic signal interaction between various devices in an SMT production line. Programmable Logic Controller (PLC): A digital computing and operating electronic system designed specifically for industrial environments. It stores programs in a programmable memory and performs operations such as logic operations, sequential control, timing, counting, and arithmetic operations to control the operation of industrial production equipment. Human-Machine Interface (HMI): Also known as a touch screen, it is a device in the field of industrial control that enables information interaction between operators and equipment. It provides functions such as parameter input, status display, and fault alarm through a graphical interface and is the core terminal for local operation in traditional industrial control.
[0019] In one specific implementation, a multi-connector cluster control method is provided, applied to a main control computer. Please refer to... Figure 1 and Figure 2 See attached Figure 3 The multi-connector cluster control method specifically includes the following steps: Step S101: Obtain the target operation parameters for multiple feeder stations in the target production line.
[0020] Specifically, the master control computer (such as a PC master control unit) serves as the core control node, equipped with cluster control software, capable of replacing the logic control functions of multiple PLCs and the local operation functions of HMIs in traditional solutions. The method of this application can be applied to automated production line cluster management systems in SMT / DIP production lines of the electronics manufacturing industry, requiring the linkage of multiple interconnecting stations and high synchronization accuracy. In local scenarios, operators can directly input target operation parameters through the PC master control software; in remote scenarios, external systems (such as MES, host computers) send POST requests (e.g., JSON request bodies in UTF-8 format) to the master control computer's WebAPI interface via the Ethernet general network. These requests contain instruction types and related parameters. The master control computer receives asynchronous access requests from external systems via the general network through this application programming interface (WebAPI interface) and parses the target operation parameters in the object simple spectrum protocol format (such as JSON format). The target operation parameters specifically include product parameters, operating parameters, or recipe instructions, such as target track width values and operating speeds.
[0021] Step S102: Verify the validity of the target operation parameters, and generate standardized bus instructions after the verification is passed.
[0022] Specifically, after acquiring the target operation parameters, the master control computer's internal WebAPI module or core control module performs legality and validity verification on the parameters. For example, during the verification process, the system sequentially performs instruction format verification, parameter value range verification (such as track width range and speed threshold), and operation permission verification for the external system. If any of these verifications fails, the master control computer returns an error response to the external system through the general network, thereby promptly intercepting illegal or abnormal instructions. If all verifications pass successfully, the parameters are considered valid, and the master control computer's core control module converts them into standardized bus instructions corresponding to each slave station using a cluster synchronization control algorithm. For example, the standardized bus instructions may specifically include parameter configuration instructions and action trigger instructions.
[0023] Step S103: Send the standardized bus command to the motion control card, and convert the standardized bus command into a control data stream that conforms to the real-time bus protocol format through the motion control card.
[0024] Specifically, a motion control card (such as an EtherCAT motion control card) is plugged into the PCIe / PCIe-x interface of the host computer, serving as the master station of the real-time communication bus network. The host computer sends the generated standardized bus commands to the motion control card. As the core hardware for interaction between the PC and the bus network, the motion control card is responsible for performing low-level protocol conversion on the standardized control commands issued by the computer, transforming them into a control data stream conforming to the real-time bus protocol format (such as the EtherCAT industrial Ethernet bus protocol format). This control data stream can flow in the bus network with extremely high real-time performance, providing hardware-level data support for subsequent high-precision synchronous motion control.
[0025] Step S104: Through the real-time communication bus network, the control data stream is synchronously sent to each of the connecting station slaves using a distributed clock synchronization mechanism, so as to control each of the connecting station slaves to synchronously perform physical actions using the synchronization signal generated by the distributed clock synchronization mechanism.
[0026] Specifically, the real-time communication bus network (such as EtherCAT, an Ethernet-based control automation technology bus) adopts a bus-type cascaded topology, connecting the motion control card with multiple slave stations (such as slave station 1 to slave station N). The communication cycle of the entire real-time bus network is extremely short (e.g., communication cycle ≤ 1ms), thus ensuring the synchronous control accuracy of multiple slave stations.
[0027] The motion control card sends the converted control data stream to each cascaded docking station slave station via the real-time communication bus network. During this process, the inherent distributed clock synchronization mechanism of the bus network provides a synchronous clock reference for each docking station slave station, ensuring the consistency of operation across multiple devices and eliminating timing deviations caused by network transmission delays. When each docking station slave station receives the control data stream corresponding to the parameter configuration command, it first uses the generated synchronization signal to synchronously update the target track width value of the driver in each docking station slave station. Then, when the control data stream corresponding to the action trigger command is sent, the synchronization signal generated by the distributed clock synchronously controls the motors in each docking station slave station to perform corresponding physical actions. For example, this includes synchronously controlling the motors in each docking station slave station (such as cascaded conveyor motor drivers and width adjustment motor drivers in internal functional components) to perform track width adjustment actions or material conveying actions, thereby achieving efficient linkage with a single command affecting the entire cluster.
[0028] Step S105: Receive real-time operation data fed back by each of the connecting station slaves, and determine the cluster operation status of the multiple connecting station slaves based on the real-time operation data.
[0029] Specifically, during or after each slave station performs a physical action, its internal components (such as position sensors, drivers, and signal interfaces) collect real-time operational status and data. This data, as real-time operational data, is fed back to the main control computer via the real-time communication bus network. After receiving the real-time operational data from each slave station, the main control computer performs deep logic judgments based on this data to determine the current cluster operational status of the entire network of slave stations.
[0030] As can be seen, in this embodiment, by centrally processing and verifying the operation parameters on the main control computer, completing the protocol conversion via the motion control card, and using the distributed clock mechanism of the high real-time bus network to drive each slave station, a one-to-many centralized control path is constructed. This mode completely breaks the information silo phenomenon caused by traditional single-machine independent control, eliminates the tedious process of on-site personnel manually inputting parameters for each device, and ensures a high degree of coordination and consistency of the entire group of machines when performing physical actions such as width adjustment or material handover through synchronization signals, significantly improving the efficiency of production line changeover and the level of automation integration.
[0031] In one embodiment, for the aforementioned multi-connector cluster control method, the step of obtaining the target operating parameters for multiple connection station slave stations in the target production line specifically includes the following steps: Step S201: Build an application programming interface based on the built-in Hypertext Transfer Protocol service; Step S202: Using the application programming interface, receive the asynchronous access request issued by the external system through the general network, and parse the target job parameters in the object spectrum protocol format from the asynchronous access request.
[0032] Specifically, in order to address the problems of traditional single-unit programmable logic controller (PLC) solutions relying on local human-machine interface (HMI) operation, lacking standardized remote control interfaces, and being unable to efficiently integrate with upper-level systems such as manufacturing execution systems (MES), this embodiment introduces a WebAPI remote control integration mechanism in the main control computer (i.e., the main control PC).
[0033] In step S201, the main control computer embeds a Hypertext Transfer Protocol service (i.e., HTTP / HTTPS service) and provides a standardized application programming interface (i.e., WebAPI interface) to the outside world based on this service. This approach establishes a standard communication bridge between external systems and underlying control devices.
[0034] In step S202, when an external system (such as MES or a host computer) needs to issue production instructions, it sends an asynchronous access request to the main control computer through a general network (i.e., Ethernet based on the TCP / IP protocol suite). This general network is specifically designed to adapt to non-real-time remote instruction interaction needs and is separate from the underlying real-time bus network. The request sent by the external system is usually a POST request, and the data in the request body adopts the Object Simplified Protocol format (i.e., JSON data format encoded in UTF-8). After receiving the asynchronous access request, the WebAPI communication module of the main control computer parses the JSON format message and extracts the target job parameters. These parameters may specifically include product parameters, operating parameters, and instructions such as recipes (e.g., setting adjustment parameters, issuing operating speed, etc.).
[0035] In this embodiment, a WebAPI interface is built into the main control computer using an HTTP service. This interface utilizes a general network to receive and parse asynchronous access requests in JSON format, breaking away from the traditional closed model that relies entirely on local HMIs for manual parameter input on a per-device basis. This solution not only effectively reduces parameter errors caused by manual input but also enables the upper-layer MES system to directly penetrate the underlying devices and remotely and automatically distribute production parameters in batches. Combined with the system's underlying cluster synchronous execution capabilities, it achieves the efficient control goal of "one-time distribution, full cluster effect," greatly enhancing the automation integration capabilities of the production line and perfectly adapting to the construction and automation upgrade needs of smart factories.
[0036] In one embodiment, for the aforementioned multi-connector cluster control method, the validity verification of the target operation parameters specifically includes the following steps: Step S301: Perform instruction format verification, parameter value range verification, and operation permission verification for the external system sequentially on the asynchronous access request; Step S302: If any of the above checks fail, an error response message is returned to the external system through the general network.
[0037] Specifically, after receiving a remote instruction from an external system (such as MES or a host computer), in order to ensure the operational safety of the underlying equipment on the production line and the reliability of network communication, the WebAPI module in the main control computer will perform a strict multi-dimensional validity check on the asynchronous access request.
[0038] In step S301, the system will sequentially perform the following three levels of review: Command format verification: First, confirm whether the field structure of the received request message is complete and whether the data type conforms to the pre-agreed interface definition specification.
[0039] Parameter value range verification: Secondly, physical threshold comparison is performed on the specific parameter values parsed. For example, strictly check whether the target track width is within the allowable range of the docking platform's mechanical structure, or whether the set operating speed exceeds the safe speed threshold limit.
[0040] Operation permission verification: Finally, verify whether the external system that initiated the asynchronous access request has legitimate control permissions to prevent unauthorized network nodes from issuing or tampering with malicious commands.
[0041] In step S302, if any step in the above verification process fails, the main control computer will immediately intercept the instruction, refuse to forward it to the core control module of the PC main control unit, and immediately return detailed error information directly to the external system that initiated the request via the general network. Conversely, only when all verifications pass successfully will the system consider the instruction valid and forward it to the downstream core control module to generate bus control instructions.
[0042] By providing error feedback to external systems immediately upon receiving an anomaly, this mechanism can accurately intercept illegal parameters caused by network transmission anomalies, upper computer scheduling logic errors, or unauthorized access. This effectively avoids mechanical overload, jamming, or collision damage caused by the docking station performing out-of-bounds actions, thus ensuring the operational safety and robustness of the entire multi-device cluster system.
[0043] In one embodiment, for the aforementioned multi-connector cluster control method, the standardized bus commands include parameter configuration commands and action trigger commands; controlling each of the connected station slaves to synchronously execute physical actions specifically includes the following steps: Step S401: Send the control data stream corresponding to the parameter configuration command to synchronously update the target track width value of the driver in each of the connecting station slave stations; Step S402: Send the control data stream corresponding to the action trigger command to synchronously control the motors in each of the connecting stations to perform track width adjustment or material conveying actions.
[0044] Specifically, in the real-time instruction generation and issuance stage, the standardized bus instructions generated by the main control computer (PC main control unit) through the motion control card (EtherCAT motion control card) are subdivided into two-dimensional logical control stages.
[0045] In step S401, the control data stream corresponding to the parameter configuration command is first sent through the real-time communication bus network. This command preloads data, precisely writing the digital-level operational parameters (such as the target track width value) into the registers of the drivers (such as bus-type stepper drivers) inside the slave execution units of each docking station. During this configuration phase, the mechanical transmission components of each docking station remain stationary; only the underlying hardware data is synchronized and updated.
[0046] In step S402, the main control computer then sends out the control data stream corresponding to the action trigger command. This action trigger command combines the distributed clock synchronization mechanism of the real-time bus, which is equivalent to sending a unified physical enable signal with a very high-precision timestamp to all equipment on the line. At the instant the global synchronization clock ticks, the execution units of each docking station simultaneously obtain power authorization for components such as the track width adjustment motor and the conveyor motor, and synchronously start and execute the track width adjustment action or the material conveying action according to the parameters already loaded in the driver.
[0047] In this embodiment, by decoupling the control issuance process into two independent stages—parameter configuration commands and action trigger commands—this solution implements a collaborative strategy in its control mechanism: first, parameters are written statically, and then actions are triggered uniformly. This two-stage operation strategy allows distributed slave stations to synchronize and update target data in advance, eliminating the time lag in equipment start-up caused by varying network transmission delays or the order of data packet parsing. This ensures that multiple devices within the production line (such as eight slave stations in a single line) can achieve true simultaneous start-stop and precise linkage when performing track width adjustment or conveying physical displacement, significantly improving the smoothness and collaborative efficiency of the operation.
[0048] In one embodiment, for the aforementioned multi-connector cluster control method, the step of receiving real-time operating data fed back by each of the connected station slaves through the real-time communication bus network, and determining the cluster operating status of the multiple connected station slaves based on the real-time operating data, specifically includes the following steps: Step S501: Receive the SMEMA signal (Surface Mount Equipment Mechanical Interface Standard) collected by each of the aforementioned docking stations from the slave station; Step S502: Based on the SMEMA signal of the surface mount equipment mechanical interface standard, determine whether the upstream docking station of the two adjacent docking stations is in a material release state, and determine whether the downstream docking station is in a material receiving request state. Step S503: If all conditions are met, the conveyor motors of the upstream and downstream connecting station slave stations are synchronously triggered through the real-time communication bus network to complete the material transfer across equipment.
[0049] In SMT production lines, the Mechanical Interface Standard (SMEMA) for surface mount equipment is typically used for material transfer and basic signal interaction between devices. In traditional single-unit control mode, SMEMA lines only support basic material transfer trigger signals (such as material arrival, permission release, etc.) and often rely on PLC hardwiring to achieve simple linkage, lacking a unified signal interaction standard.
[0050] In this embodiment, each docking station execution unit is equipped with an SMEMA signal interface. During system operation, the main control computer uniformly receives the SMEMA signals collected by each docking station slave station through the bus network and processes them centrally as real-time operation data. The main control computer performs a logical joint determination of the upstream and downstream relay status based on the aggregated status data: it determines whether the upstream docking station is ready to release materials (material release status) and whether the downstream docking station is idle and ready to receive materials (material receiving request status).
[0051] Only when both of these logical conditions are met simultaneously will the main control computer, acting as the central dispatch hub, issue commands via the real-time communication bus network to synchronously trigger the conveyor motors of the upstream and downstream docking stations. This enables the conveyor mechanisms of these two adjacent devices to complete the cross-device transfer of materials such as printed circuit boards with precisely matched movements.
[0052] In this embodiment, by centralizing the SMEMA interaction signals that were originally handled by hard-wiring single PLCs at each independent station to the main control network for judgment, and using real-time bus instructions to synchronously trigger the conveyor motors of adjacent devices, the communication response blind spots and timing errors between isolated devices are effectively reduced, significantly improving the continuity and transmission efficiency of material conveying actions between adjacent nodes, and ensuring a highly smooth flow of materials in the production line.
[0053] In one embodiment, for the aforementioned multi-connector cluster control method, determining the cluster operation status of the multiple connection station slave stations based on the real-time operation data specifically includes the following steps: Step S601: If all the received real-time operation data indicate that the physical action has been completed, then the cluster operation status is determined to be a synchronization completion status; Step S602: Based on the synchronization completion status, send a response message of job success to the external system through the application programming interface.
[0054] During the physical actions such as mechanical width adjustment or material handover performed by the docking station, the execution units (such as position sensors, motor encoders, etc.) inside each docking station will continuously use the current operating status as real-time operating data and synchronously feed it back to the PC main control unit through the EtherCAT real-time communication bus network.
[0055] In step S601, the main control computer will only determine that the entire production line equipment group has reached a consistent completion node and will set the cluster operation status to synchronous completion state when the data returned from each docking station on the bus link clearly indicates that the physical action of its internal motor (width adjustment completed or delivery in place) has been completely executed and stopped. As long as any docking station has not completed its action, this global state will not be triggered.
[0056] In step S602, since this embodiment is based on the aforementioned remote integration scenario (i.e., remote control based on WebAPI), after confirming the synchronization completion state, the WebAPI communication module inside the main control computer will immediately encapsulate this physical state into a response body in an Object Simplified Protocol format (JSON format) that is easy for the upper-layer network to parse. For example, a response message containing the execution result code (e.g., resultCode indicating success) and explanatory information (e.g., resultMsg) is generated and returned to the external system (e.g., MES or host computer) that initially initiated the asynchronous access request via the general network (Ethernet).
[0057] In this embodiment, by closely monitoring the real operating data of all hardware devices and adopting a global confirmation mechanism that only completes the process when all standards are met, the production status known by the external Manufacturing Execution System (MES) is ensured to be absolutely real and complete. This prevents the subsequent production scheduling instructions from being issued incorrectly and the material scheduling from being disordered due to the lag in the actions of individual devices, and greatly improves the collaborative stability of the fully automated production line.
[0058] In one embodiment, for the aforementioned multi-connector cluster control method, determining the cluster operation status of the multiple connection station slave stations based on the real-time operation data specifically includes the following steps: Step S701: If any of the received real-time operation data is an abnormal signal indicating a fault, an emergency stop command is broadcast to each of the connecting station slaves via the motion control card to control each of the connecting station slaves to stop the current physical action and remain in the current physical position.
[0059] In complex industrial production environments (such as SMT / DIP production lines), the conveyor belts are highly susceptible to external interference or mechanical problems when operating at high speeds. Examples include printed circuit boards jamming during track transport, motor stalling due to foreign objects in the width adjustment mechanism, or failure of internal photoelectric sensors. When a conveyor belt detects these conditions through its internal self-testing logic or servo driver, it will set a fault alarm flag (i.e., an abnormal signal) in its periodically reported real-time operating data.
[0060] Once the master computer detects an abnormal signal from any node on the bus, it will immediately determine that the current cluster operation is in an abnormal fault state. In order to prevent the fault from spreading and causing subsequent material accumulation or chain collisions between multiple devices, the master computer will bypass the normal queue operation priority and immediately generate an emergency stop message with extremely high control weight.
[0061] Specifically, the emergency stop message no longer uses the inefficient node-by-node addressing method, but is directly broadcast to all connected slave stations on the bus via the EtherCAT motion control card. Upon receiving the broadcast command, all slave stations on the bus (including those that are not malfunctioning and are in normal operation) will forcibly and synchronously cut off the power output of the conveyor motor and the pulse-width modulation motor (or apply braking torque), causing all transmission mechanisms to instantly stop at their current coordinates and enter protection mode until the operator troubleshoots and manually resets the system.
[0062] In this implementation, when an abnormal signal is detected at any local node, the motion control card is used to broadcast an emergency stop command to all equipment on the line and forcibly maintain the physical position lock. This not only greatly shortens the time delay between fault response and command issuance, but also effectively prevents material squeezing and chain collision accidents caused by the blind operation of other equipment due to the failure of individual connecting stations. This significantly improves the operational safety of the production line hardware facilities and expensive work-in-process.
[0063] Please continue reading Figure 1 as well as Figure 2 As shown, in one embodiment, a multi-connector cluster control system is proposed to implement the multi-connector cluster control method described in any of the preceding embodiments, from the perspective of system-level hardware architecture and physical link deployment. The system specifically includes: The main control computer is used to execute the above-mentioned multi-connector cluster control method; The motion control card is plugged into the main control computer and serves as the master station of the real-time communication bus network. The real-time communication bus network uses a bus-type cascaded topology to connect the motion control card with multiple docking station slaves. A general network connects the main control computer to external systems; wherein the main control computer is configured with a first communication interface for connecting to the general network and a second communication interface for connecting to the real-time communication bus network, so as to separate the non-real-time command interaction link from the synchronous motion control link.
[0064] This embodiment breaks away from the traditional isolated and decentralized architecture of each connecting station on a production line, which has its own independent PLC controller. Instead, it adopts a centralized architecture with a main control computer (i.e., a PC main control unit) as the core. The main control computer internally carries the cluster synchronous control algorithm for multiple devices across the entire line and the WebAPI communication module.
[0065] like Figure 1 As shown, a motion control card (e.g., a high-speed motion control card supporting the EtherCAT protocol) is configured in the downlink of the control system. This card is directly plugged into and fixed on the motherboard of the main control computer via a high-speed physical interface such as PCIe, serving as the core hardware engine and bus master for the entire industrial communication. The real-time communication bus network (EtherCAT bus) derived from this control card uses a one-in-one-out bus cascade topology to connect the slave stations 1 to N distributed in the workshop through cables, constructing a high-speed industrial control architecture with microsecond-level deterministic transmission.
[0066] In the upward link of the control system, a general network (such as the factory's existing Ethernet TCP / IP network) is connected to facilitate information data communication between the main control computer and upper-level external systems (such as the MES manufacturing execution system or the upper-level scheduling host).
[0067] Most importantly, this system adopts a dual-NIC physical isolation design on the main control computer. Specifically, the main control computer is equipped with a first communication interface (such as the standard gigabit Ethernet port on the motherboard) to connect to a general network and carry non-real-time command interaction links with large data packets and bursts of traffic but low real-time requirements (such as receiving target job parameters in JSON format and feedback operation logs). At the same time, the main control computer uses a dedicated Ethernet port on the motion control card as a second communication interface to connect to a real-time communication bus network and exclusively handle synchronous motion control links with short data frames and extremely strict timing periods (such as ≤1ms).
[0068] In this embodiment, an integrated solution using a motion control card on the main control computer separates the network ports via a first and a second communication interface. This embodiment completely decouples the high-level business information flow from the low-level mechanical motion control flow at the physical level of the system architecture. This isolation design between the non-real-time network and the hard real-time network not only resolves the network data congestion and timing pollution crises that are prone to occur under the traditional single-port multiplexing architecture, but also provides extremely smooth and interference-free network integration capabilities while ensuring microsecond-level high-precision physical synchronization of dozens of slave devices, perfectly meeting the information and automation integration needs of modern smart factories.
[0069] In one embodiment, for the aforementioned multi-connector cluster control system, in order to clarify the specific wiring and network hierarchy of the physical links, the global topology of the real-time communication bus network is specifically configured as follows: The global topology of the real-time communication bus network includes: the main control computer sequentially cascades through the motion control card, slave station 1 to slave station N via the bus.
[0070] In terms of physical cabling and hardware connections in the workshop, this system abandons the complex star topology of traditional networks (which requires the use of switches and hubs) and instead adopts a linear bus cascade topology with one input and one output.
[0071] The main control computer (PC main control unit) serves as the control source for the entire production line, with its internally connected EtherCAT motion control card acting as the sole bus master for the entire network. Data frames carrying centralized control messages are sent from the master interface of this motion control card, first directly connecting to the ingress port (IN) of the first device (i.e., slave station 1) via a single network cable. After slave station 1 reads the required message fragments and injects feedback data, it directly transmits the updated data frame to the ingress port of the next adjacent device (slave station 2) via its egress port (OUT). The data flow continues in this manner, sequentially connecting slave station 3 until the last device at the physical end of the link (slave station N). Finally, the data frame flows back to the main control computer, completing a very short-cycle real-time communication loop.
[0072] In this embodiment, by cascading the main control computer through the motion control card via a linear bus from slave stations 1 to N, the complexity of cabling for multi-machine interconnection is simplified, eliminating the need for expensive intermediate network equipment such as industrial switches. More importantly, this architecture provides the system with excellent versatility and flexible scalability: when the production line capacity needs to be upgraded later and new slave station nodes need to be added, engineers only need to connect a communication cable after the last slave station N to bring it under the control of the main control system. This process requires no cumbersome topology reconstruction or cabling modifications to the main control node hardware and core software, resulting in significant deployment cost savings and seamless scalability.
[0073] In one embodiment, for the aforementioned multi-connector cluster control system, the connecting station slave is a dual-track, dual-segment connecting station, and the functional components inside each connecting station slave are cascaded in the real-time communication bus network in the following order: the first cascade node to the fourth cascade node are respectively the conveyor motor drivers for the first track to the fourth track; the fifth cascade node to the seventh cascade node are respectively the width adjustment motor drivers for the second track to the fourth track; the eighth cascade node is a digital input module; and the ninth cascade node is a digital output module.
[0074] Specifically, taking a dual-track, dual-segment docking station as an example, the hardware entity of a dual-track, dual-segment docking station, which has a relatively complex structure in surface mount technology or through-hole packaging technology production lines, usually contains a large number of actuators and sensor endpoints. In order to ensure the absolute orderliness of microsecond-level command transmission and underlying device status feedback, this system sets the specific physical cascading order of the docking station's internal functional components accessing the bus.
[0075] After the data frame enters the slave station of the receiving station, the first data processing nodes are the first to fourth cascaded nodes. These nodes are sequentially connected to the conveyor motor drivers of the first to fourth tracks. As an example, in a specific physical mapping, these four nodes can respectively correspond to the bus-type stepper drivers driving the first section conveyor motors of the first and second tracks, the second section conveyor motors of the first and second tracks, and the first and second section conveyor motors of the third and fourth tracks. They are responsible for accurately intercepting start, stop, and speed commands directly related to the material conveyor belt traction, ensuring the smooth segmented transmission of materials such as printed circuit boards.
[0076] Subsequently, the control data flow sequentially enters the fifth to seventh cascade nodes, which are dedicated to the width adjustment motor drivers for the second to fourth tracks. In the actual track adjustment logic, the first track is usually kept stationary as the absolute physical reference, while the three width adjustment motor drivers receive bus commands to drive the width adjustment mechanisms (such as lead screw drives) of the second, third, and fourth tracks, thereby achieving independent and precise adjustment of the physical spacing of each track to flexibly adapt to the needs of products of different sizes and batches.
[0077] Next, the data frame traverses the eighth cascade node, which is configured as a digital input module (DI module). The digital input module is mainly used to aggregate and acquire various external input signals generated inside the docking station equipment, such as material arrival signals from various photoelectric switches or trigger signals from mechanical limit sensors.
[0078] Finally, the data stream reaches the ninth cascade node at the end of the link, namely the digital output module (DO module). This module is mainly responsible for transmitting output signals from the docking station equipment according to the master control instructions, such as driving the audible and visual alarm indicator lights on the top of the equipment or controlling the action of specific relays.
[0079] That is, the slave devices inside each docking station are connected to the EtherCAT bus in the following order to ensure the orderly transmission of commands and status feedback. The following is the connection sequence for a dual-rail, dual-segment docking station: ① 1_2 rail conveyor 1-section bus type stepper driver: drives the first section conveyor motor of the 1st and 2nd rail conveyor mechanism ②1_2 rail conveyor 2-section bus type stepper driver: drives the second section conveyor motor of the 1st and 2nd rail conveyor mechanisms. ③ 3-4 rail conveyor, 1-section bus-type stepper driver: drives the first section conveyor motor of the 3- and 4-rail conveyor mechanisms. ④ 3-4 rail conveyor 2-section bus-type stepper driver: drives the second section conveyor motor of the 3- and 4-rail conveyor mechanism. ⑤ 2-rail width-adjusting bus type stepper driver: drives the width-adjusting mechanism of 2 rails to achieve precise adjustment of the width of 2 rails; ⑥ 3-rail width-adjusting bus type stepper driver: drives the width-adjusting mechanism of 3 rails to achieve precise adjustment of the width of the 3 rails; ⑦ 4-rail width-adjusting bus type stepper driver: drives the width-adjusting mechanism of 4 rails to achieve precise adjustment of the width of the 4 rails; ⑧ Bus-type DI module: Connects to the input signals of the docking station equipment; ⑨ Bus-type DO module: Output signal of the docking station equipment.
[0080] like Figure 4 The diagram illustrates the physical cascaded topology of the functional components within the dual-track, dual-section docking station within the EtherCAT real-time communication bus network. The cascade starting point is connected to the master station: the PC motion control card connects to the bus network via a DB36 interface. Data frames pass through each functional unit sequentially in a daisy-chain configuration via the ECAT IN and ECAT OUT interfaces, thereby achieving real-time, high-speed communication and synchronous control from a single master station to multiple slave stations. Motor driver cascade (actuation components): Figure 4 Stepper motor drivers M01 to M07 (corresponding to unit numbers 00 to 06) are cascaded in sequence. These drivers are used to drive the conveyor motor (for material transfer) and the width adjustment motor (for precise adjustment of track width) in the dual-rail, dual-section connecting platform, respectively. I / O expansion integration (sensing and control components): At the end of the cascaded link, a digital input module (DI module, unit number 07, EM32DI-E4) and a digital output module (DO module, unit number 08, EM32DO-E4) are connected in sequence. The DI module is used to collect external input signals from photoelectric sensors, limit switches, and other devices inside the connecting platform; the DO module is used to control output actions such as audible and visual alarms and relays.
[0081] In this embodiment, by fixing the various functional drivers and the cascading order of digital input / output modules on the real-time communication bus network within each dual-track, dual-segment docking station, a highly standardized mapping protocol specification is established for the addressing and orchestration of the upper-layer software. This consistency in the internal hardware cascading structure significantly reduces the processor overhead of the main control computer when parsing and reassembling the offsets of complex communication data frames, ensuring that field maintenance personnel can quickly and accurately locate and replace damaged components directly using standardized network node numbers, thus significantly improving the maintainability of the equipment cluster and the stability of the underlying communication architecture.
[0082] In one embodiment, for the aforementioned multi-connector cluster control system, in order to further define the data interaction protocol of the underlying communication network and its core synchronization reference, the system is specifically configured as follows: The real-time communication bus network is an Ethernet control automation technology bus, which is configured to provide a synchronous clock reference for each of the connecting station slaves through a distributed clock synchronization mechanism.
[0083] In high-precision control scenarios within industrial automation, standard general-purpose Ethernet is limited by mechanisms such as CSMA / CD (Carrier Sense Multiple Access / Collision Detection), resulting in unpredictable network jitter and delays in packet transmission and arrival times. To address this issue, the real-time communication bus network in this embodiment preferably employs an industrial-grade Ethernet control automation technology bus (i.e., EtherCAT bus). As an example, this bus possesses multi-slave cascading capabilities and microsecond-level communication synchronization accuracy, enabling high-speed, highly reliable distributed control between the master control node and various connected slave devices. Its network communication cycle can typically be configured to extremely short levels (e.g., ≤1ms).
[0084] The underlying protocol of the Ethernet control automation technology bus deeply integrates a distributed clock synchronization mechanism (Distributed Clocks, DC). Since the slave stations are linearly distributed in the workshop space, there is inevitably a time difference in the propagation of data frames in the communication cables. During network initialization and operation, this distributed clock synchronization mechanism selects the local oscillator of a specific node (usually the first slave station) with this clock capability as the reference master clock, and continuously and periodically sends specific messages to accurately measure the physical propagation delay and offset between nodes on the bus line.
[0085] Based on these precise measurements, the main control computer uses these delay compensation parameters to dynamically fine-tune the clock offset register inside each slave station in the network within an extremely short communication cycle. This ensures that the time axis used to trigger physical electrical pulses within each slave station distributed throughout the network achieves strict microsecond-level or even nanosecond-level alignment calibration. In actual execution, after the action control command issued by the main control computer reaches each slave station driver, the driver does not act immediately but enters a latching waiting state until the moment the synchronized clock beat (i.e., the synchronization signal) arrives across the entire network. Only then do all drivers simultaneously enable the current release, thereby driving the conveyor motors or width-adjusting motors of all slave stations within the line to start operating at an absolutely consistent physical moment.
[0086] In this embodiment, by introducing an industrial-grade EtherCAT (EtherControl and Automation) bus and deeply activating its inherent distributed clock synchronization mechanism at the protocol's underlying layer, this solution provides a robust real-time foundation for the master-slave control architecture, resisting network jitter and latency. This mechanism, through precise transmission delay measurement and clock skew compensation, eliminates the timing errors of command arrival times in traditional communication architectures, ensuring that slave stations distributed in different physical locations have absolutely aligned local timelines. This deep integration of hardware and software at the microsecond level ensures a high degree of consistency in the start-up of actions when multiple device clusters perform track-linked width adjustment and cross-device material handover, greatly enhancing the overall coordination control accuracy and system reliability of complex production lines.
[0087] In one embodiment, for the aforementioned multi-connector cluster control system, the master control computer is configured to: parse the object spectrum protocol format instructions received through the general network, and convert them into standardized bus instructions corresponding to each of the connected station slaves based on the cluster synchronization control algorithm; monitor the status feedback of each of the connected station slaves in real time, and realize parameter configuration and status monitoring of all the connected station slaves in the production line through a single terminal interface.
[0088] Specifically, the master computer, as the core control node of the entire cluster control system, is not only responsible for the underlying bus communication scheduling, but also undertakes the comprehensive functions of instruction parsing, algorithm calculation and status monitoring, in order to completely replace the logic control functions of multiple PLCs and the local operation functions of each device HMI in the traditional solution.
[0089] In industrial automation remote integration scenarios, when external systems (such as Manufacturing Execution System (MES) or factory host computer systems) remotely issue control tasks via a common network (such as Ethernet), these access requests are typically encapsulated in Object Simplified Protocol format (i.e., JSON data format based on UTF-8 encoding). The WebAPI parsing module deployed inside the main control computer performs deep parsing of the received JSON format instructions, accurately extracting target operation parameters including product width, operating cycle time, or specific production formulas. Subsequently, the main control computer uses its internally mounted cluster synchronization control algorithm module to precisely convert the extracted abstract business instructions into standardized bus instructions (such as EtherCAT bus instructions) that match the underlying execution logic of each docking station slave hardware. This algorithmic conversion mechanism achieves a one-to-many precise mapping from the high-dimensional management instructions of the host computer to the synchronous action electrical signals of multiple underlying hardware slave stations.
[0090] Furthermore, to address the shortcomings of existing technologies where each feeder station requires an independent local human-machine interface (HMI), leading to cumbersome operation and susceptibility to errors in manual input, the main control computer is configured to manage the entire line through a centralized, single-terminal interface. During operation, the main control computer continuously and in real-time monitors the status feedback (such as width adjustment completion, delivery arrival, physical faults, etc.) transmitted from each feeder station via a real-time communication bus, and presents the status in a unified graphical format on this single-terminal interface. Simultaneously, on-site operators can also directly issue and configure parameters for all feeders across the entire production line directly on this interface. As an example, when facing a changeover and width adjustment task on a production line with multiple devices (e.g., a line with 8 feeders), operators do not need to manually adjust each device individually; they only need to perform a unified parameter configuration operation on this single-terminal interface, and the system will automatically issue the width adjustment command synchronously to all feeders along the entire line.
[0091] In this embodiment, the main control computer is configured as the core hub with the ability to parse object spectrum protocol format and process cluster synchronization control algorithms. A single terminal interface is used to realize the status overview and parameter configuration of all equipment on the entire line. At the system level, the isolation and distributed control and interaction redundancy of traditional single-machine docking stations are completely eliminated. This centralized processing mechanism not only realizes that network commands are issued once and take effect across the entire cluster, eliminating the tedious work and potential error risks of manually inputting data for each machine, but also significantly reduces the time required for changing and adjusting the width of multiple devices (for example, from 10 minutes for a single machine to only a few minutes for the entire line), greatly enhancing the data transparency and automated centralized scheduling efficiency of the smart factory production line.
[0092] In one embodiment, for the aforementioned multi-connector cluster control system, in order to further improve the sensing accuracy of the pose adjustment mechanism and form closed-loop control, the sensor configuration method of the connecting station slave stations is specifically defined as follows: Each of the aforementioned docking stations includes a position sensor connected to the eighth cascade node, which is used to feed back the real-time track width to the main control computer.
[0093] In the mechanical structure of the dual-track dual-section connecting platform, in order to accurately control the physical position of the track after the width adjustment action, a high-precision position sensor (such as a high-precision grating ruler, magnetostrictive displacement sensor or high-resolution absolute encoder) is installed on the screw drive side or slide rail side of the width adjustment mechanism.
[0094] These position sensors do not use scattered analog hardwired connections directly to the main controller. Instead, they follow the system's strict bus cascading specifications, uniformly connecting the electrical signal outputs of the sensors to the eighth cascade node (the aforementioned DI digital input module) within the slave station of the docking station. This DI module, as a standard slave node on the bus link, can convert the analog signals or high-speed pulse signals acquired by the sensors into digital arrays in real time, and then load them into high-frequency data frames on the EtherCAT real-time communication bus, transmitting them back to the PC main control unit at high speed via the network.
[0095] By adding position sensors inside the docking station and standardizing their acquisition channels to the eighth cascade node of the bus link, the calculation errors caused by simply relying on the number of motor stepping pulses to extrapolate the width are eliminated. This ensures that the main control computer can always grasp the precise absolute physical position of the guide rail. This not only guarantees the absolute stability and alignment accuracy of the physical spacing of the product guide rails after each automated width adjustment operation, but also provides the main control computer with direct evidence to immediately trigger emergency protection logic when abnormalities such as rail jamming cause the actual motor displacement to deviate from the theoretical command. This improves the operational safety of the production line hardware and expensive work-in-process.
[0096] In one embodiment, a master control computer is provided, which serves as the core computing and logic processing hub in the system architecture, and implements the aforementioned cluster control logic by executing a specific computer program. The master control computer includes a processor and a memory; the memory stores a computer program, which, when executed by the processor, implements the multi-connector cluster control method described in any of the foregoing embodiments.
[0097] The main control computer described in this embodiment can be an industrial control host with high-performance computing capabilities. Its internal physical architecture mainly consists of a processor (CPU / GPU) and memory (RAM / ROM / SSD). The processor, as the computing and control core of the entire control system, has high concurrency processing capabilities and can meet the computing power requirements of microsecond-level synchronous control algorithms. The memory serves as the program execution environment and persistent data storage area, internally burning and storing pre-installed computer programs. These program logics rigorously encapsulate the entire control process, including remote command parsing, cluster synchronous control algorithms, real-time status monitoring, and fault arbitration.
[0098] During execution, the processor retrieves and runs the computer program from memory via the system bus, enabling centralized scheduling of multiple docking stations within the production line. Specifically, this includes: the processor calling the WebAPI communication module in real time to parse asynchronous instructions received via the general network and converting business parameters into specific bus control logic; subsequently, the processor drives the motion control card connected to the system bus, converting logic instructions into high-frequency pulses and communication data streams; simultaneously, the processor continuously scans the real-time operational data fed back from the underlying layers. If an abnormality is detected, the processor can immediately trigger the internally configured fault handling interrupt logic, controlling all equipment on the line to perform emergency avoidance through a broadcast mechanism.
[0099] For more information about the aforementioned equipment, please refer to the relevant descriptions in the foregoing method embodiments or system embodiments, which will not be repeated here.
[0100] In one embodiment, this application also provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the multi-connector cluster control method described in any embodiment of this application.
[0101] The above-described embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application, and should all be included within the protection scope of this application.
Claims
1. A method for controlling a cluster of multiple docking stations, characterized in that, Applied to a main control computer, the method includes: Obtain the target operation parameters for multiple docking stations in the target production line; The validity of the target operation parameters is verified, and standardized bus instructions are generated after the verification is passed. The standardized bus commands are sent to the motion control card, which then converts them into a control data stream conforming to the real-time bus protocol format. Through a real-time communication bus network, the control data stream is synchronously sent to each of the connecting station slaves using a distributed clock synchronization mechanism, so as to control each of the connecting station slaves to synchronously execute physical actions using the synchronization signal generated by the distributed clock synchronization mechanism. Receive real-time operation data from each of the aforementioned connection station slave stations, and determine the cluster operation status of the multiple connection station slave stations based on the real-time operation data.
2. The multi-connector cluster control method according to claim 1, characterized in that, The acquisition of target operating parameters for multiple feeder stations in the target production line includes: The application programming interface is built based on the built-in Hypertext Transfer Protocol service. Using the application programming interface, an asynchronous access request issued by an external system through a general network is received, and the target job parameters in the object spectrum protocol format are parsed from the asynchronous access request.
3. The multi-connector cluster control method according to claim 2, characterized in that, The validity verification of the target operation parameters includes: The asynchronous access request is sequentially subjected to instruction format verification, parameter value range verification, and operation permission verification for the external system. If any of the aforementioned checks fails, an error response message is returned to the external system via the general network.
4. The multi-connector cluster control method according to claim 1, characterized in that, The standardized bus commands include parameter configuration commands and action trigger commands; controlling each of the connected station slaves to synchronously execute physical actions includes: The control data stream corresponding to the parameter configuration command is issued to synchronously update the target track width value of the driver in each of the connecting station slave stations; The control data stream corresponding to the action trigger command is sent out to synchronously control the motors in each of the connecting stations to perform track width adjustment or material conveying actions.
5. The multi-connector cluster control method according to claim 1, characterized in that, The receiving of real-time operation data fed back by each of the connecting station slaves through the real-time communication bus network includes: Receive SMEMA signals, the mechanical interface standard for surface mount equipment, collected from each of the aforementioned docking stations; Determining the cluster operation status of the multiple connection station slave stations based on the real-time operation data includes: Based on the SMEMA signal of the surface mount equipment mechanical interface standard, it is determined whether the upstream docking station is in a material release state and whether the downstream docking station is in a material receiving request state. If all conditions are met, the conveyor motors of the upstream and downstream feeder stations are synchronously triggered through the real-time communication bus network to complete the material transfer across equipment.
6. The multi-connector cluster control method according to claim 2, characterized in that, Determining the cluster operation status of the multiple connection station slave stations based on the real-time operation data includes: If all the received real-time operation data indicate that the physical action has been completed, then the cluster operation status is determined to be a synchronization completion status. Based on the synchronization completion status, a successful operation response message is sent to the external system through the application programming interface.
7. The multi-connector cluster control method according to claim 1, characterized in that, Determining the cluster operation status of the multiple connection station slave stations based on the real-time operation data includes: If any of the received real-time operating data is an abnormal signal indicating a malfunction, an emergency stop command is broadcast to each of the connecting station slaves via the motion control card to control each of the connecting station slaves to stop its current physical action and remain in its current physical position.
8. A multi-connector cluster control system, characterized in that, include: The main control computer is used to execute the multi-connector cluster control method as described in any one of claims 1-7; The motion control card is plugged into the main control computer and serves as the master station of the real-time communication bus network. The real-time communication bus network uses a bus-type cascaded topology to connect the motion control card with multiple docking station slaves. A general network connects the main control computer to external systems; The main control computer is equipped with a first communication interface for connecting to the general network and a second communication interface for connecting to the real-time communication bus network, so as to separate the non-real-time command interaction link from the synchronous motion control link.
9. A master control computer, characterized in that, include: Processor and memory; The memory stores a computer program that, when executed by the processor, implements the method as described in any one of claims 1-7.
10. A computer-readable storage medium, characterized in that, It stores a computer program that, when executed by a processor, implements the method as described in any one of claims 1-7.
