Synchronous Start-up Method and Apparatus for Multi-Station Systems
By establishing a global clock reference and parallel status acquisition mechanism in the multi-station testing system, the problem of inconsistent startup times of each execution unit was solved, achieving high-precision synchronous startup and ensuring the timing consistency and data comparability of multi-station testing.
Patent Information
- Application Number
- CN202611119000.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-07-27
- Publication Date
- 2026-11-10
AI Technical Summary
In multi-station testing systems, the lack of a unified clock synchronization mechanism among the execution units leads to inconsistent startup times, introducing timing deviations ranging from milliseconds to seconds, which affects the accuracy and consistency of the tests.
By establishing a global clock reference, the time base of multiple execution units participating in the same task in the system is unified to the global clock. In response to the start command, the status information of each execution unit is obtained in parallel, and a start signal is sent to all execution units simultaneously based on the global clock reference.
It eliminates time base deviation caused by independent clocks of each execution unit, ensuring that each execution unit starts executing tasks with unified state start parameters at the same time, significantly improving the consistency of start conditions and the comparability of test data in multi-station parallel testing.
Smart Images

Figure CN123067951A_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of synchronous startup of multi-station systems, and more particularly to a method and apparatus for synchronous startup of multi-station systems. Background Technology
[0002] As a core component of new energy vehicles, the performance and reliability of the on-board charger (OBC) directly affect the charging safety and user experience of the entire vehicle. With the continuous improvement of OBC power levels and the expansion of functions from unidirectional charging to bidirectional charging and discharging (V2G, V2L, etc.), its control logic is becoming increasingly complex, placing higher demands on the coverage, accuracy, and efficiency of testing and verification.
[0003] Currently, OBC test benches typically consist of bidirectional AC power supplies, bidirectional DC power supplies, electronic loads, water chillers, and high / low temperature environmental chambers. These are uniformly scheduled by host computer software to simulate various input / output conditions of the OBC in a real-world vehicle environment. With the diversification and increasing scale of testing requirements, multi-station parallel testing has become the mainstream approach to improving testing efficiency. Existing solutions, such as the "Design of an Automated Testing System for New Energy Vehicle On-Board Chargers," while achieving single-station automated testing based on LabVIEW, still primarily rely on independent human-machine interfaces or separate control software for each device to operate independently. During testing, parameters for the high-voltage power supply, AC power supply, electronic loads, and environmental chambers need to be sent out one by one, at different times.
[0004] The aforementioned "independent control, time-sharing distribution" control architecture suffers from inherent timing deviations that are further amplified in multi-station parallel testing scenarios. Due to the lack of a unified clock synchronization mechanism among the devices, parameter distribution occurs in a sequential order, and the internal response times of each device are inconsistent. This results in multiple physical quantities (voltage, current, temperature) failing to establish unified initial conditions simultaneously, introducing millisecond- to second-level timing errors. Furthermore, the OBC startup phase typically requires the reception and parsing of multiple critical CAN messages within a 200-600 millisecond time window. If the test system lacks high-precision timing control capabilities, it will be difficult to effectively verify such critical operating conditions, severely restricting the accuracy and consistency of multi-station OBC parallel testing. Therefore, a testing method capable of synchronous parameter distribution and unified startup control across multiple devices is urgently needed. Summary of the Invention
[0005] The purpose of this invention is to provide a synchronous startup method and apparatus for multi-station systems, in order to solve the problem that in existing multi-station testing systems, each execution unit is operated one by one and started in a time-division manner. Due to the lack of a unified clock synchronization mechanism, the execution units cannot establish a unified task start state at the same time, which leads to timing deviations in startup time.
[0006] To achieve the above objectives, the present invention is implemented as follows: In a first aspect, the present invention provides a method for synchronously starting a multi-station system, comprising: Establish a global clock reference to unify the time base of multiple execution units participating in the same task in the system to the global clock reference; In response to the start command, the status information of each execution unit is acquired in parallel before the start action is executed; When it is determined from the status information that all execution units meet the preset executable conditions, a start signal is simultaneously sent to all execution units at a preset time, based on the global clock reference.
[0007] Furthermore, the multi-station system is a multi-station parallel test bench for on-board chargers of new energy vehicles; The plurality of execution units include a power supply device that provides power to each workstation, an electronic load device that provides load to each workstation, and an environmental control device that provides environmental simulation for each workstation. The synchronous start-up method is used to enable the power supply equipment, electronic load equipment and environmental control equipment of each workstation to apply test conditions to the on-board charger under test at the corresponding workstation at the same time.
[0008] Secondly, a method for coordinated protection of a multi-station system is provided, including: Obtain the running parameters of multiple execution units participating in the same task in the system; Based on the operating parameters, determine whether each execution unit meets the preset alarm triggering conditions; When any execution unit is determined to meet the alarm triggering condition, a linkage protection action sequence corresponding to the alarm triggering condition is executed according to the level of the alarm triggering condition. The linkage protection action sequence includes multiple protection actions that are executed sequentially at predetermined time intervals.
[0009] Thirdly, a method for real-time correlation and storage of multi-source test data is provided, including: The system time of the main control device is used as the global time reference; During the execution of the test task, test data is collected from multiple data sources, including at least a first type of data from the device and a second type of data from the object under test. Each piece of data of the first type and each piece of data of the second type collected will be timestamped with the global time base as the source; The first and second types of data, after being timestamped, along with the working condition setting data of the current execution stage of the test task, are linked and stored in the same data storage file in real time, using the timestamp as the association key.
[0010] Fourthly, a synchronous start-up device for a multi-station system is provided, comprising: The time reference establishment module is used to establish a global clock reference and unify the time references of multiple execution units participating in the same task in the system to the global clock reference; The status acquisition module, in response to the start command, acquires the status information of each execution unit in parallel before executing the start action; and, The synchronous triggering module is used to send a start signal to all the execution units simultaneously at a preset time, based on the global clock reference, when it is determined from the status information that all execution units meet the preset executable conditions.
[0011] Fifthly, the present invention also provides a computer-readable storage medium on which a computer program is stored, wherein the computer program, when executed by a processor, implements the steps of the method described in the first aspect.
[0012] The beneficial effects of this invention are as follows: The synchronous startup method of the multi-station system of this invention establishes a global clock reference, unifying the time base of all execution units participating in the same task in the system to the same clock source, fundamentally eliminating the time base deviation caused by each device maintaining its own independent clock. Furthermore, in response to the startup command, the system does not start immediately, but first acquires the status information of each execution unit in parallel. Only after determining that all execution units meet the preset executable conditions is a startup signal sent to all execution units simultaneously at a preset time. Through this three-step mechanism of "unifying the clock reference first, confirming that all units are ready, and finally synchronously triggering," this invention transforms the millisecond-level or even second-level random timing deviations caused by the individual operation and time-sharing startup of devices in traditional solutions into controllable and predictable synchronous startup. This ensures that each execution unit starts executing the task with unified state starting parameters at the same time, thereby fundamentally eliminating timing errors at the startup level and significantly improving the consistency of starting conditions and the comparability of test data in multi-station parallel testing. Attached Figure Description
[0013] Figure 1 This is a schematic flowchart of a synchronous startup method for a multi-station system according to an embodiment of the present invention; Figure 2 This is a schematic flowchart of a synchronous startup method for a multi-station system according to another embodiment of the present invention; Figure 3 This is a schematic flowchart of a synchronous startup method for a multi-station system according to another embodiment of the present invention; Figure 4This is a schematic flowchart of a synchronous startup method for a multi-station system according to another embodiment of the present invention; Figure 5 This is a schematic flowchart of a synchronous startup method for a multi-station system according to another embodiment of the present invention; Figure 6 This is a schematic flowchart of a synchronous startup method for a multi-station system according to another embodiment of the present invention; Figure 7 This is a schematic flowchart of a synchronous startup method for a multi-station system according to another embodiment of the present invention; Figure 8 This is a complete timing diagram of the multi-station synchronous start-up method of the present invention; Figure 9 A timing simulation comparison diagram of traditional time-sharing startup and synchronous startup of the present invention; Figure 10 This is a schematic architecture diagram of a multi-station system according to an embodiment of the present invention; Figure 11 Schematic diagram of the OBC multi-station test bench system used in the synchronous startup method of the present invention; Figure 12 This is a topology diagram of the signal and energy connections for the OBC multi-station test bench. Figure 13 This is a topology diagram of a computer-readable storage medium disclosed in this invention. Detailed Implementation
[0014] The present invention will now be described in detail with reference to the embodiments shown in the accompanying drawings. However, it should be noted that these embodiments are not intended to limit the present invention. Equivalent changes or substitutions in function, method, or structure made by those skilled in the art based on these embodiments are all within the scope of protection of the present invention.
[0015] The technical solutions provided by the various embodiments of the present invention will be described in detail below with reference to the accompanying drawings.
[0016] Example 1: As Figure 1 As shown, this embodiment 1 provides a synchronous startup method for a multi-station system (hereinafter referred to as "synchronous startup method" or "startup method" or "method"), applied in a multi-station system and a synchronous startup device. The method includes: Step 102. Establish a global clock reference to unify the time base of multiple execution units participating in the same task in the system to the global clock reference.
[0017] The specific operations for establishing a global clock reference include: The system time maintained by the master control device in the system is used as the global clock reference, and all execution units are notified to synchronize their local time base with the system time of the master control device.
[0018] By using the master control device's system time as a global clock reference and notifying all execution units to synchronize, this embodiment establishes a unique and unified time base at the system level. This eliminates time base deviations caused by each execution unit maintaining its own independent clock, ensuring that all subsequent status acquisition, condition determination, and start signal transmission are performed under the same time reference system. This guarantees that the "preset time" is the same absolute physical time for all execution units. Simultaneously, this global clock reference also provides a unified timestamp source for the operational data of each execution unit after startup, enabling all data generated by multiple workstations during subsequent operation to be correlated and traced on the same timeline. This lays the foundation for timeline alignment and horizontal comparison of multi-workstation data.
[0019] In another preferred embodiment, the establishment of the global clock reference also includes a multi-level clock source redundancy backup mechanism: The system maintains a master clock source and at least one backup clock source (such as the master control device's system time as the master clock source, and an external GPS timing module or IEEE 1588 PTP clock source as the backup clock source); the master control device periodically monitors the operating status of the master clock source; when an anomaly is detected in the master clock source (such as clock signal loss, frequency drift exceeding limits, etc.), it automatically switches to the backup clock source and notifies all execution units to resynchronize to the new global clock reference.
[0020] like Figure 2 As shown, prior to the step of responding to the start command, the procedure further includes: Step 1031. In response to the user's input of the initial setting command or according to the preset configuration file, generate the initial execution parameters required by each execution unit for this task; Step 1032. Before sending the start signal to each execution unit, the initial execution parameters are sent to the corresponding execution units respectively, so that each execution unit uses the initial execution parameters as the starting state of this task when it receives the start signal.
[0021] It should be understood that this operation establishes a unified starting state for subsequent synchronous startups, ensuring that each execution unit uses the same pre-set set of parameters as the starting state for this task when it receives the startup signal, rather than using default values or residual values from the previous task. Based on this, each execution unit no longer needs additional time to receive and load parameters during subsequent synchronous startups, thus eliminating interference from the parameter distribution process on the startup timing. This allows "simultaneous sending of startup signals at preset times" to truly transform into each execution unit starting the task with unified parameters at the same time.
[0022] In other words, this embodiment 1, by generating and pre-issuing initial execution parameters before startup, transforms the random delays that may be introduced by the traditional "start first, then set parameters" or "start while setting parameters" approach into controllable preparatory actions completed before startup, thus eliminating the problem of inconsistent starting states of each execution unit due to inconsistent parameter issuance times. Simultaneously, each execution unit carries complete initial execution parameters upon receiving the startup signal, eliminating the need to wait for parameter loading at startup and ensuring the effectiveness of "synchronous startup"—each unit not only starts operating at the same time but also uses the exact same preset parameters as starting conditions, thus providing dual protection for the consistency of multi-station test starting conditions from both the parameter and timing perspectives.
[0023] Step 104. In response to the start command, before executing the start action, the status information of each execution unit is obtained in parallel.
[0024] like Figure 3 As shown, the specific steps for obtaining the status information of each execution unit include: Step 301. Obtain one or more of the following statuses for each execution unit: communication link connectivity, initial parameter loading completion, and the status of the controlled object corresponding to that execution unit. The communication link connectivity status confirms the physical connection and protocol layer communication between the host computer and each execution unit, preventing subsequent start signals from failing to arrive due to communication interruptions. The initial parameter loading completion status confirms that the initial execution parameters issued in steps 1031-1032 have been successfully received and loaded by each execution unit. The controlled object's status confirms that the tested object at each workstation has been correctly installed and positioned, preventing tests from starting under no-load or improper installation conditions. These three statuses correspond to the three startup prerequisites: communication reachability, parameter readiness, and object positioning. Any anomaly indicates that the condition is not met and the reason is recorded.
[0025] Step 302. When any of the obtained status indicators is abnormal, mark the corresponding execution unit as not meeting the executable conditions and record the reason for the abnormality.
[0026] By acquiring three types of status information—communication link, parameter loading, and object presence—in parallel before startup, this embodiment establishes a multi-stage health check mechanism before startup: communication link connectivity ensures command reachability, parameter loading ensures consistent status, and object presence ensures test validity. Only when all execution units meet the conditions in all three dimensions are subsequent synchronous triggering steps allowed, thus preventing startup failures or invalid tests at some workstations due to communication interruptions, unloaded parameters, or the object under test not being in place. Simultaneously, the anomaly cause recording mechanism provides precise location information for subsequent fault diagnosis, allowing operators to quickly locate abnormal workstations and anomaly types based on the records, significantly improving the maintainability of the multi-workstation system.
[0027] In step 104, the operation of "parallel acquisition of status information of each execution unit" is as follows: By allocating independent communication channels or independent threads to each execution unit, status query requests are sent concurrently to each execution unit within the same time period, and each unit independently receives the returned status response.
[0028] Specifically, each execution unit has an independent uplink communication link or independent software thread resources. There is no resource sharing or queuing relationship between query tasks. All query requests are issued in parallel within the same time window, and each response result is received independently without affecting others. This parallel acquisition method is fundamentally different from the traditional "sequential polling" method: under sequential polling, the total time for acquiring the status of N execution units is the sum of the response times of each unit; while under parallel acquisition, the total time depends only on the response time of the slowest unit, and the status information of each unit is closer in time, almost like a snapshot at the same moment.
[0029] Thus, by allocating independent communication channels or independent threads to each execution unit for concurrent execution of status queries, this embodiment compresses the total time for acquiring the status of multiple workstations from the sum of the response times of each unit to the maximum value of the response times of each unit, significantly shortening the preparation time before startup and improving the response efficiency of the test system. More importantly, parallel acquisition ensures the temporal proximity of the status information of each execution unit. All status information is collected within the same extremely short time window, avoiding the problem of incomparability of status information between units queried earlier and later due to time differences in the sequential polling method. This provides a temporally consistent basis for subsequent judgment that all execution units meet the executable conditions, fundamentally ensuring the accuracy and reliability of synchronous triggering decisions.
[0030] like Figure 4 As shown, after acquiring the status information of each execution unit in parallel, the process also includes: Step 401. Set the timeout threshold for status acquisition.
[0031] Step 402. If complete status information of any execution unit cannot be obtained within the timeout threshold (meaning that the communication link of the execution unit may be abnormal or the unit is busy and unable to respond to the query request normally), or if the obtained status information determines that any execution unit does not meet the preset executable conditions (e.g., communication link interruption, initial parameter loading failure, or the tested object is not in place), then the step of sending the start signal is prohibited, and feedback prompt information is generated. That is, the system does not perform subsequent synchronous triggering operations, and at the same time generates feedback prompt information (including but not limited to the exception type, the identifier of the exception source unit, and the occurrence time), and outputs a clear exception alarm to the operator through the interface display layer. This timeout threshold and the aforementioned status acquisition step complement each other in timing: status acquisition is responsible for collecting the status information of each unit, and the timeout threshold is responsible for limiting the time boundary of collection. The two together constitute a complete exception capture mechanism.
[0032] Thus, this embodiment 1 establishes a final safety barrier before startup: the system is only allowed to enter the synchronization triggering phase when all execution units are successfully queried within a predetermined time and all meet the executable conditions; otherwise, the system actively terminates the startup process and informs the operator of the reason for the abnormality through feedback. This mechanism can effectively avoid blindly performing synchronous startup when the communication link is unstable, some execution units are offline, or the tested object is not installed correctly, preventing test failures, invalid data, or even equipment damage caused by "starting with defects." It also provides operators with clear troubleshooting guidance, greatly improving the security and availability of the system.
[0033] Step 106. When it is determined from the status information that all execution units meet the preset executable conditions, a start signal is sent to all execution units simultaneously at a preset time, based on the global clock reference.
[0034] like Figure 5 As shown, a start signal is sent simultaneously to all execution units at a preset time, specifically including: Step 501. Using the current time indicated by the global clock reference as a reference, take the next integer multiple of the clock cycle boundary of the current time as the preset time.
[0035] The next integer multiple of the clock cycle boundary refers to treating the clock cycle of the master control device system time as a continuous and equally spaced time division. Starting from the current moment, the next time point aligned with an integer multiple of the clock cycle is selected as the unified trigger moment. This trigger moment is the same absolute time point for all execution units.
[0036] In another preferred embodiment, the preset time can also be determined in the following way: Before each synchronous startup, the main control device reads the round-trip delay records of the most recent N communications of each execution unit and calculates the average delay and delay variance of each execution unit. Based on this, an optimal preset time is determined. This time is not simply taken as the boundary of a clock cycle, but is a time point selected after comprehensively considering the delay characteristics of each execution unit, so that the actual time deviation of all execution units starting to execute tasks is minimized after deducting their respective communication delays.
[0037] Step 502. When the global clock reference reaches a preset time, a start signal with a timestamp of the preset time is sent in parallel to each execution unit. After receiving the start signal, each execution unit uses the preset time timestamp carried in the start signal as a reference and begins to execute the task at that preset time.
[0038] Thus, in this embodiment 1, by using the next integer multiple of the clock cycle boundary as the preset time, a deterministic and unique synchronous triggering time point is provided for all execution units, eliminating the triggering time drift that may occur due to the independent operation of the internal clocks of each execution unit. Simultaneously, by carrying a timestamp of the preset time in the start signal, even if there are slight time delay differences during communication transmission, each execution unit can start uniformly based on the preset time carried in the signal rather than the actual arrival time of the signal, thereby effectively offsetting the impact of network transmission delay on synchronization accuracy. Furthermore, by aligning the preset time with the clock cycle boundary referenced by the global clock, the timestamps of subsequent running data all fall on the known and determined clock cycle boundary, facilitating accurate timeline alignment and correlation analysis of the running data of multiple execution units.
[0039] like Figure 6 As shown, after the step of simultaneously sending a start signal to all execution units, the process also includes: Step 108. After receiving the start signal, each execution unit independently records the runtime of its current task, using a preset time as the starting reference point. That is, it starts timing from the preset time and records the cumulative runtime of the current time relative to the preset time.
[0040] Step 110. Periodically generate time-stamped data containing the current operating state of the execution unit (reflecting the unit's working mode at that moment, such as constant voltage output, constant current charging, temperature rise, standby, etc.), the current task execution progress (identifying completed operating steps or task stages, such as completing step 3 of the operating sequence out of 15 steps), and the current runtime (providing the execution unit's time-series coordinates relative to a unified starting point, such as running for 1250ms). This data is used for subsequent timeline alignment and correlation analysis of the running data of multiple execution units. This time-stamped data, together with the global clock reference established in step 102, forms a dual time stamping system of absolute timestamp (global clock reference) and relative timestamp (running time starting from a preset time).
[0041] Thus, in this embodiment 1, after synchronous startup, each execution unit independently records its runtime and periodically generates time-stamped data, using a preset time as the starting reference point. Each piece of runtime data from each execution unit is appended with an independently usable time stamp. Absolute timestamps ensure the alignment of data from each workstation on the same global timeline, while relative timestamps eliminate the impact of minor time deviations caused by factors such as the actual physical location of the execution unit, equipment model, or communication delays on the data analysis results. The combination of these two types of timestamps makes it possible to perform timeline alignment, horizontal comparison, and correlation analysis on multi-workstation runtime data laterally: data analysts can unify the data from all workstations onto the same timeline using absolute timestamps, and can also accurately compare the behavioral differences of each workstation in the same operational phase using relative timestamps. This extends the temporal consistency of synchronous startup to the data level, ensuring the traceability and comparability of test data from the starting point to the entire process.
[0042] like Figure 7 As shown, after sending the start signal to all execution units simultaneously, the process also includes: Step 701. Upon receiving the start signal, each execution unit returns a start confirmation response to the main control device. This response includes the execution unit's identification, reception status, and current readiness flag.
[0043] Step 702. The main control device determines whether it has received start confirmation responses from all execution units within the preset timeout threshold.
[0044] Step 703. If yes, confirm that the synchronous startup was successful (the system enters the normal task execution phase); if no (i.e., any execution unit fails to return a startup confirmation response within the timeout threshold, then mark that execution unit as a startup exception), mark the execution unit that did not return a startup confirmation response as a startup exception, and perform exception handling operations—including but not limited to sending a pause command to the successfully started execution units, recording the reason for the exception and the time of the exception, and feeding back to the interface display layer for operators to troubleshoot and handle. This mechanism adds a two-way handshake confirmation step between sending the startup signal and officially starting the task, upgrading the synchronous startup from a one-way downward sending to a closed-loop control of sending-confirmation-execution.
[0045] It should be understood that this embodiment 1, by adding a start confirmation response mechanism after synchronous triggering, effectively distinguishes between the concepts of a sent start signal and successful start, avoiding false synchronization caused by communication interruptions, incomplete initialization within the execution unit, or hardware response failures. That is, the main control device may believe that synchronous start has been achieved, while some execution units may not actually have started executing tasks. This confirmation feedback mechanism substantially improves the credibility and reliability of synchronous start. Simultaneously, for unconfirmed execution units, the system can promptly locate anomalies and perform targeted anomaly handling, avoiding the risk of incomplete test data or damage to the tested object caused by some workstations continuing to execute tasks while others have not actually started. Furthermore, the recording and feedback of anomaly causes provide operators with accurate fault location information, significantly improving the maintainability and troubleshooting efficiency of multi-workstation systems. Together with the aforementioned synchronous start signal transmission, this forms a complete "send-confirm-execute" closed loop, further enhancing the robustness and system security of the synchronous start method.
[0046] In another preferred embodiment, after the activation confirmation response step, a synchronization accuracy verification and compensation step is further included: Upon receiving the start signal, each execution unit records the precise timestamp of the signal arrival locally (based on a synchronized global clock reference) and records the timestamp of the actual action occurrence when performing the task for the first time. The difference between these two timestamps (i.e., the start response delay) is reported to the master control device. The master control device collects the start response delays of all execution units and calculates the difference between the maximum and minimum delays as a synchronization accuracy indicator. If this indicator exceeds a preset threshold (e.g., 1 millisecond), the synchronization start accuracy is deemed insufficient, triggering a compensation mechanism: a time compensation value (i.e., the delay of that unit relative to the fastest unit) is sent to the execution unit with the larger delay. This unit then eliminates the delay by appropriately increasing its execution rate in subsequent task executions.
[0047] Figure 8This diagram fully presents the entire timeline from system initialization to normal operation using the aforementioned method. It covers the parallel correspondence between the main control layer's action timeline (0ms issuance of global clock synchronization command → 50ms parallel issuance of initial parameters → 100ms multi-threaded concurrent query of device status → 250ms calculation of the predetermined time and issuance of a start signal with a 250ms timestamp → waiting for confirmation response → receiving data after 450ms) and the execution unit layer's unified action timeline (synchronizing the local clock → loading parameters and waiting → responding to status query → synchronous start based on timestamp → sending back confirmation message → reporting dual-timestamp data), clearly demonstrating the collaborative cooperation between the main control layer and the execution unit layer within each time period. The diagram also illustrates the dual-timestamp recording mechanism (absolute timestamps are used for multi-station timeline alignment, and relative runtime is used for test process analysis), extending the "timing consistency" advantage of synchronous start-up to the data level.
[0048] pass Figure 9 This paper compares the timing differences between the synchronous startup method of Embodiment 1 and the traditional time-sharing startup scheme in a six-station parallel testing scenario. Figure 9 In the traditional time-sharing startup waveform area on the left, due to the independent control and time-sharing parameter distribution of each device and the lack of a unified clock synchronization mechanism, the startup times of the six workstations are inconsistent, with the maximum timing deviation reaching hundreds of milliseconds. During the critical CAN message reception window of 200-600 milliseconds in the OBC startup phase, some workstations experience short-term CAN test failures due to startup asynchrony. Figure 9 In the right-hand synchronous startup waveform area, a three-step mechanism—establishing a global clock reference, confirming the parallel state before startup, and synchronously triggering at a preset time—ensures that the startup times of the six workstations are highly consistent, compressing timing deviations to within 10 milliseconds. This guarantees that all workstations begin executing test tasks with uniform initial parameters at the same time. As can be seen from the comparison, this embodiment can fundamentally eliminate timing errors caused by time-sharing device startup, significantly improving the consistency of starting conditions and the comparability of test data in multi-workstation parallel testing.
[0049] This invention provides a synchronous startup method for multi-station systems, addressing the timing deviations caused by inconsistent startup times among execution units during multi-station parallel testing or production. This embodiment uses a six-station OBC test bench as an example; however, those skilled in the art should understand that the method is not limited to six-station or OBC testing scenarios, but is applicable to any automated system requiring synchronous startup of multiple stations. The specific implementation process of this embodiment is as follows: 1. System initialization and establishment of global clock reference Before the system begins operation, a global clock reference is first established. In this embodiment, the execution units participating in the same test task include: six bidirectional DC power supplies in the DC power supply cabinet, six AC power supplies in the AC power supply cabinet, six electronic loads in the electronic load cabinet, a high and low temperature environment chamber, a water chiller, a PLC slave in the transfer cabinet, and six CAN communication cards in the PC cabinet. Each execution unit is connected to the master control device via an industrial Ethernet network, and the CAN communication cards are connected to the OBCs under test at each workstation via a CAN bus. The system uses the system time of the master control device (an industrial control computer based on the LabVIEW platform) as the global clock reference and sends time synchronization commands to all execution units via the industrial Ethernet network to unify the local clocks of each execution unit with this global clock reference.
[0050] 2. Initial execution parameter preset The main control equipment responds to the user-input initial setting command or preset configuration file, generating initial execution parameters for each execution unit. These parameters include the output voltage and current limits of the DC source at each workstation, the output voltage and frequency settings of the AC source, the load mode and settings of the electronic load, the target temperature of the environmental chamber, and the target outlet water temperature and flow rate settings of the water chiller. Before startup, these parameters are sent to the corresponding execution units via the Modbus-TCP protocol. After receiving and loading these parameters, each execution unit enters a "parameter ready, waiting for trigger" standby state.
[0051] Taking station 1 as an example: The main control device sends the DC voltage setpoint to the corresponding DC power supply slave unit in the DC power supply cabinet for station 1 via the Modbus-TCP protocol, sends the AC voltage setpoint to the corresponding AC power supply slave unit in the AC power supply cabinet for station 1, sends the load mode and setpoint to the corresponding electronic load slave unit in the electronic load cabinet for station 1, sends the temperature setpoint to the control PLC of the high and low temperature environment chamber, and sends the water temperature and flow rate setpoints to the control PLC of the water chiller. The parameter sending method for stations 2 to 6 is exactly the same as that for station 1. After each execution unit receives and loads the initial execution parameters, it keeps the parameter configuration in memory, but does not immediately execute the output action. Instead, it is in a "parameter ready, waiting for trigger" standby state until it receives a start signal and then starts execution with this set of parameters as the starting state.
[0052] 3. Parallel state acquisition and timeout handling After the user clicks "Start Test," the master control device initiates status query requests in parallel within the same time window through communication channels independently allocated to each execution unit. In this embodiment, the master control device simultaneously initiates status query requests to the six DC power supply slaves in the DC power supply cabinet, the six AC power supply slaves in the AC power supply cabinet, the six electronic load slaves in the electronic load cabinet, the PLC in the environmental enclosure, the PLC in the water chiller, the PLC in the transfer cabinet, and the six CAN cards. All requests are sent in parallel within the same time window. After receiving the query request, each execution unit returns a current status response, which the master control device independently receives and parses.
[0053] The acquired statuses include the communication link connectivity status (determined by whether a valid response is received within the timeout threshold), the initial parameter loading completion status (confirmed by specific positioning flags in the status words returned by each execution unit), and the on-site status of the object under test (acquired through sensor signals corresponding to each execution unit, such as the position feedback of the high-voltage switch in the transfer cabinet, the connection detection signal of the OBC under test at the workstation, etc.). When any acquired status indicates an abnormality, the corresponding execution unit is marked as not meeting the executable conditions and the reason for the abnormality is recorded. For example, if the main control device detects that the DC power supply slave at station 2 fails to return a communication response within the timeout threshold, it determines that the communication link of the execution unit is abnormal, marks station 2 as not meeting the executable conditions, and records the reason for the abnormality as "DC power supply communication timeout at station 2"; if the status word returned by the electronic load at station 4 indicates that the initial parameter loading has failed, it marks station 4 as not meeting the executable conditions and records the reason for the abnormality as "electronic load parameter loading failure at station 4"; if the presence sensor signal at station 6 indicates that the measured OBC is not connected, it marks station 6 as not meeting the executable conditions and records the reason for the abnormality as "measured object not present at station 6".
[0054] It should be noted that, in this embodiment, the timeout threshold for status acquisition is preferably set to 100ms. This value is determined based on the typical response time of industrial Ethernet communication, which can balance response timeliness and communication fault tolerance. This timeout threshold can be adaptively adjusted according to the actual communication load of the system and the response characteristics of the equipment, and is not limited to the specific value of 100ms. If complete status information of any execution unit is not obtained within the timeout threshold, or if the obtained status information determines that any execution unit does not meet the preset executable conditions (such as communication link interruption, initial parameter loading failure, or the tested object not being in place), the main control device will prohibit the step of sending the start signal. That is, the system will not perform subsequent synchronous triggering operations, and at the same time, it will generate feedback prompt information and output a clear abnormal alarm to the operator through the interface display layer.
[0055] 4. Synchronization triggering based on a global clock reference When all communication links of the execution units are normal, parameters are loaded, and the object under test is in place, the next whole millisecond of the global clock reference is used as the preset time. For example, if the current time is 10:30:25.123, then the preset time is 10:30:25.124. This preset time is locked immediately after it is determined and will not change with subsequent processing time. When the global clock reference reaches this preset time, the master control device sends a start signal with the timestamp of the preset time in parallel through the independent communication channels of each execution unit.
[0056] 5. Initiation confirmation response and exception handling After the start signal is sent, the main control device waits for start confirmation responses from all parties. The confirmation responses are of two types: First, after completing internal start preparations, the device-side execution units (DC power supplies, AC power supplies, electronic loads, environmental chambers, water chillers, etc.) directly return a start confirmation response to the main control device via the industrial Ethernet. This response includes the execution unit's identification, start signal reception status, and current readiness flag. Second, after completing internal start preparations, the tested OBC transmits confirmation information back to the main control device via the CAN bus through the CAN communication card of the corresponding workstation. After receiving all the above confirmation responses, the main control device determines whether it has received confirmation information from all execution units and all tested OBCs within a preset confirmation timeout threshold (preferably set to 200ms in this embodiment).
[0057] If all are received, the synchronous startup is confirmed to be successful, and the system enters the normal task execution phase. Each execution unit starts executing tasks with the pre-sent initial execution parameters at the preset time, and the OBC under test at each workstation starts running and reports status data. If any execution unit or any OBC under test at any workstation fails to return confirmation within the timeout threshold, the corresponding execution unit or workstation is marked as a startup anomaly, and an anomaly handling operation is performed.
[0058] 6. Runtime recording and time stamp data generation after startup After successful synchronization, the system enters the post-boot data recording phase, which includes: 6.1 Each execution unit independently records the runtime of its current task, using a preset time as the starting reference point. Specifically, each execution unit maintains a runtime counter locally, which increments based on the local clock starting from the preset time, recording the cumulative runtime (in milliseconds) of the current time relative to the preset time.
[0059] 6.2 Each execution unit periodically generates time-stamped data, which includes three core pieces of information: the current operating status of the execution unit (e.g., constant voltage output, constant current charging, temperature rise, standby, etc.), the current task execution progress (e.g., completed step 3 of the operating sequence, out of 15 steps), and the current running time (e.g., 1250ms). Each execution unit merges the above time-stamped data with the operating parameter data (voltage, current, temperature, etc.) collected in this period and reports it to the main control device at a preset sampling frequency (10Hz in this embodiment, i.e., generating a set of data every 100ms).
[0060] After receiving data reported by each execution unit, the main control device associates the absolute timestamp referenced by the global clock with the relative runtime reported by each execution unit, forming a structured data record of "absolute timestamp + relative timestamp + workstation identifier + operating parameters + operating status + task progress". This dual time stamping system makes it possible to perform timeline alignment, horizontal comparison, and correlation analysis on multi-workstation operating data in the later stages.
[0061] Therefore, this embodiment comprehensively ensures the timing consistency of the multi-station system at the start time and the time traceability of the data throughout the entire process, from the unification of time base, initial state synchronization, pre-start state confirmation, determination of synchronization trigger time, start confirmation feedback to the generation of runtime data time tags.
[0062] Example 2: As Figure 10 As shown, the multi-station system 900 of this embodiment 2 has a topology structure divided into four layers from top to bottom: main control layer 901, communication network layer 902, execution unit layer 903, and controlled object layer 904. Each layer realizes bidirectional interaction of command issuance and data feedback through industrial Ethernet and CAN communication network, forming a complete closed-loop control system of issuance-confirmation-execution-feedback. Figure 11 The static structure of the system is presented from the perspective of equipment composition and hierarchical relationship. It shows the software and functional modules included in the host computer control layer (i.e., the main control layer 901), the five types of communication media included in the communication network layer 902, the various test equipment included in the execution unit layer 903, and the test samples of the controlled object layer 904. Figure 12 The dynamic interaction logic of the system is presented from the perspective of connection relationship and signal flow. It shows the communication connection (communication line / CAN bus) between the main control layer 901 and the execution unit layer 903, and between the execution unit layer 903 and the controlled object layer 904, the high voltage power connection (high voltage line), the acquisition signal connection (acquisition line), and the cooling circuit connection (cooling circuit pipe). Figure 11 and Figure 12 Together, these constitute a complete description of the hardware platform on which the synchronous startup device 1000 of this embodiment relies.
[0063] Main control layer 901 (corresponding to) Figure 11 The upper computer control layer and Figure 12 The host computer control system (located at the top layer of the system) includes three virtual functional modules of the synchronous startup device 1000 and a data storage and processing unit 1011. The synchronous startup device 1000 is the core functional module of this embodiment. The three virtual functional modules are deployed in the main control device as software program modules, loaded into the memory of the main control device during runtime, and executed by the processor. The synchronous startup device 1000 includes: a time reference establishment module 1001, used to establish a global clock reference and unify the time reference of multiple execution units participating in the same task in the system to the global clock reference; a status acquisition module 1002, used to acquire the status information of each execution unit in parallel before executing the startup action in response to the startup command; and a synchronous trigger module 1003, used to send a startup signal to all execution units simultaneously at a preset time based on the global clock reference when it is determined that all execution units meet the preset executable conditions according to the status information. The data storage and processing unit 1011 includes a DBC parsing engine (used to parse CAN messages from the tested OBC) and a CSV data fusion storage module (used to associate and store the time stamp data reported by each execution unit with the absolute timestamp referenced by the global clock). The main control layer 901... Figure 12 The communication lines and CAN bus are connected to the communication network layer 902.
[0064] Execution unit layer 903 contains all execution units participating in the same test task. Figure 11 Specifically, this includes a bidirectional high-voltage DC power supply, a three-phase AC power supply, AC loads, DC loads, a programmable low-voltage DC power supply, an environmental chamber, a water chiller, voltage sensors, current sensors, a high-precision multimeter, and low-voltage loads. These devices are integrated into the power supply cabinet, load cabinet, environmental chamber, and water chiller cabinet, respectively. Figure 12 Specifically, this is manifested in execution units such as bidirectional high-voltage DC power supplies connected to the host computer control system via communication lines. Each device in the execution unit layer 903 participates in the synchronous startup process as an independent execution unit in the synchronous startup device 1000. Each execution unit communicates with the host computer control system via communication lines. Figure 12 The communication line shown receives synchronization commands, initial parameters, and start signals from the main control layer 901, and returns status responses and start confirmation responses; through Figure 12 The high-voltage line shown applies electrical energy to the controlled object layer 904; through Figure 12 The acquisition line shown transmits the operating parameters of the controlled object layer 904 back to the main control layer 901.
[0065] The controlled object layer 904 is located at the bottom of the system, namely the test sample (OBC - on-board charger) placed inside the environmental chamber. Figure 11Specifically, this manifests as the tested OBC connected to the host computer control layer via a CAN bus, to the device execution layer via a high-voltage line, to the water chiller via a cooling circuit, and to sensors via a data acquisition line. Specifically, it manifests as the test sample connected to the host computer control system via a CAN bus, to a bidirectional high-voltage DC power supply, a three-phase AC power supply, and AC / DC loads via a high-voltage line, to the water chiller via a cooling circuit, and to voltage and current sensors via data acquisition lines. The controlled object layer 904 serves as the core object for synchronous startup in the synchronous startup device 1000. It receives synchronization and shutdown commands from the main control layer 901 via the CAN bus, receives electrical energy applied by the execution unit layer 903 via the high-voltage line, feeds back operating parameters to the execution unit layer 903 via the data acquisition line, and receives coolant circulation from the water chiller via the cooling circuit.
[0066] After the system 900 starts, the time reference establishment module 1001 of the main control layer 901 is activated first. This module uses the host computer system time of the main control device as the global clock reference and sends time synchronization instructions to all execution units (including DC power source, AC power source, electronic load, environmental actuator and each CAN card) participating in the same test task in the system through industrial Ethernet and CAN communication network. This makes the local time reference of all execution units consistent with the global clock reference, and establishes a unified time reference system for all subsequent operations involving time stamping.
[0067] After the global clock reference is established, the system enters the initial parameter preset stage. The master control device responds to the user-inputted initial setting command or generates the initial execution parameters required for each execution unit's current task based on a preset configuration file, and then sends these parameters to the corresponding execution units via industrial Ethernet. After receiving and loading the initial execution parameters, each execution unit keeps the parameters configured in memory but does not immediately execute any output actions, remaining in a "parameter ready, waiting to be triggered" standby state, preparing for subsequent synchronous startup at the parameter level.
[0068] When the user clicks the "Start Test" button on the interface or triggers the start command via external hardware, the system's status acquisition module 1002 is activated. Before executing the start action, this module concurrently sends status query requests to each execution unit within the same time period through independently allocated communication channels or independent threads, and each unit independently receives the returned status response. The status information acquired by the status acquisition module 1002 includes the communication link connectivity status of each execution unit, the initial parameter loading completion status, and the presence status of the controlled object corresponding to each execution unit. When any acquired status indicates an anomaly, the status acquisition module 1002 marks the corresponding execution unit as not meeting the executable conditions and records the reason for the anomaly. At the same time, the status acquisition module 1002 also has a timeout handling mechanism. If the complete status information of any execution unit cannot be acquired within the preset timeout threshold, or if the acquired status information determines that any execution unit does not meet the executable conditions, the system is prohibited from entering the subsequent synchronous triggering steps, and feedback prompts are generated to output a clear anomaly alarm to the operator through the interface display layer.
[0069] When the status acquisition module 1002 determines, based on the acquired status information, that all execution units meet the preset executable conditions (i.e., all communication links of all execution units are normal, all initial execution parameters have been successfully loaded, and all controlled objects are in place), the synchronization trigger module 1003 is activated. This module first uses the current time indicated by the global clock reference as a benchmark, and takes the next integer multiple of the clock cycle boundary of the current time as the preset time—in this embodiment, the next whole millisecond. Once this preset time is determined, it is immediately locked and no longer changes with subsequent processing time. When the global clock reference reaches this preset time, the synchronization trigger module 1003 simultaneously and in parallel sends a start signal with a timestamp of the preset time to all execution units in the system through the independent communication channels corresponding to each execution unit. After receiving the start signal, each execution unit begins executing the task with the preset time carried in the start signal as a reference—rather than starting execution at the moment the start signal was received—thus effectively compensating for the impact of differences in network transmission delay.
[0070] After the start signal is sent, each execution unit returns a start confirmation response to the main control device upon receiving the start signal. The response includes the execution unit's identification and reception status. The synchronization trigger module 1003 determines whether it has received start confirmation responses from all execution units within a preset confirmation timeout threshold: if all are received, the synchronization start is confirmed as successful, and the system enters the normal task execution phase; if any execution unit fails to return a confirmation response within the timeout threshold, the execution unit is marked as having a start anomaly, and an anomaly handling operation is performed.
[0071] After successful synchronization, each execution unit independently records the runtime of its current task (i.e., the cumulative runtime relative to the preset time) using a preset time as the starting reference point. It also periodically generates timestamp data containing the current running status, current task execution progress, and current runtime of the execution unit, which is then uploaded to the main control layer via industrial Ethernet. The main control layer's CSV data fusion storage module receives the data reported by each execution unit and associates the absolute timestamp indicated by the global clock reference with the relative timestamps (runtime) reported by each execution unit, forming a structured data record of "absolute timestamp + relative timestamp + workstation identifier + running parameters + running status + task progress." This record is then used for subsequent timeline alignment and correlation analysis of the running data from multiple execution units.
[0072] Through the aforementioned working principles and inter-module coordination, at the timing level, the time reference establishment module 1001 unifies the time reference of all execution units through a global clock reference, and the synchronization trigger module 1003 ensures that all execution units start executing tasks at the same absolute moment through a "preset time + simultaneous delivery" mechanism, fundamentally eliminating the millisecond to second-level timing deviations caused by the individual control and time-sharing start-up of devices in traditional solutions. At the reliability level, the status acquisition module 1002 performs parallel status confirmation on all execution units before startup, ensuring that the communication link is normal, parameters are loaded, and the controlled object is in place before allowing startup, eliminating the possibility of "starting with defects." The startup confirmation response mechanism added by the synchronization trigger module 1003 further verifies the actual delivery and execution effect of the startup signal, upgrading synchronous startup from "one-way delivery" to a closed-loop control of "delivery-confirmation-execution," significantly improving the system's robustness. From the perspective of data availability, each execution unit independently records its runtime and generates time-stamped data with a preset time as the starting reference point. Together with the absolute timestamp referenced by the global clock, it forms a dual time stamping system, which makes it possible to perform time axis alignment, horizontal comparison and correlation analysis on multi-station operation data. This extends the "timing consistency" advantage of synchronous startup to the data level, ensuring the traceability and comparability of multi-station test data from the "starting point" to the "entire process".
[0073] It should be noted that for the same or similar technical solutions as in Embodiment 1, please refer to Embodiment 1, and will not be repeated here.
[0074] Example 3: Example 3 of the present invention also provides a terminal device, which may include a processor, a memory, and a computer program stored in the memory and executable on the processor, wherein the computer program, when executed by the processor, implements the above-described... Figure 1 The various processes shown in the embodiment of the synchronous startup method for a multi-station system can achieve the same technical effect, and will not be described again here to avoid repetition.
[0075] Example 4: Combination Figure 13 As shown in the illustration, this embodiment also discloses a specific implementation of a computer-readable storage medium 1300. This computer-readable storage medium 1300 can be configured wholly or partially within a physical computer, server, cluster server, or data center.
[0076] In this embodiment, the computer-readable storage medium 1300 stores computer program instructions 1301, which are read and executed by a processor 1302 to perform the steps in the synchronous startup method for a multi-station system disclosed in Embodiment 1.
[0077] Optionally, the computer-readable storage medium 1300 can be configured as a server, and the server runs on a physical device used to build a private cloud, hybrid cloud, or public cloud. The computer-readable storage medium 1300 can also be configured as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), etc.
[0078] The computer-readable storage medium 1300 is used to store a program, and the processor 1302, upon receiving an execution instruction, executes the synchronous startup method for a multi-station system disclosed in Embodiment 1.
[0079] Meanwhile, the processor 1302 disclosed in this embodiment may be an integrated circuit chip with signal processing capabilities. The processor 1302 can be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it can also be a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the various methods, steps, and logic block diagrams disclosed in the embodiments of this invention. The general-purpose processor can be a microprocessor or any conventional processor.
[0080] The technical solution of the same part in the computer-readable storage medium 1300 disclosed in this embodiment as in Embodiment 1 and / or Embodiment 2 is described in Embodiment 1 and / or Embodiment 2, and will not be repeated here.
[0081] The detailed descriptions listed above are merely specific descriptions of feasible embodiments of the present invention, and are not intended to limit the scope of protection of the present invention. All equivalent embodiments or modifications made without departing from the spirit of the present invention should be included within the scope of protection of the present invention.
[0082] It will be apparent to those skilled in the art that the present invention is not limited to the details of the exemplary embodiments described above, and that the invention can be implemented in other specific forms without departing from its spirit or essential characteristics. Therefore, the embodiments should be considered in all respects as exemplary and non-limiting, and the scope of the invention is defined by the appended claims rather than the foregoing description. Thus, all variations falling within the meaning and scope of equivalents of the claims are intended to be included within the present invention. No reference numerals in the claims should be construed as limiting the scope of the claims.
[0083] Furthermore, it should be understood that although this specification describes embodiments, not every embodiment contains only one independent technical solution. This narrative style is merely for clarity. Those skilled in the art should consider the specification as a whole, and the technical solutions in each embodiment can also be appropriately combined to form other embodiments that can be understood by those skilled in the art.
Claims
1. A synchronous startup method for a multi-station system, characterized in that, include: Establish a global clock reference to unify the time base of multiple execution units participating in the same task in the system to the global clock reference; In response to the start command, the status information of each execution unit is acquired in parallel before the start action is executed; When it is determined from the status information that all execution units meet the preset executable conditions, a start signal is simultaneously sent to all execution units at a preset time, based on the global clock reference.
2. The method according to claim 1, characterized in that, The steps for establishing a global clock reference specifically include: The system time maintained by the master control device in the system is used as the global clock reference, and all execution units are notified to synchronize their local time base with the system time of the master control device.
3. The method according to claim 2, characterized in that, The specific steps for obtaining the status information of each execution unit include: The communication link connectivity status, initial parameter loading completion status, and the in-situ status of the controlled object corresponding to each execution unit are obtained respectively. When any of the obtained status indicators is abnormal, the corresponding execution unit is marked as not meeting the executable conditions and the reason for the abnormality is recorded.
4. The method according to claim 3, characterized in that, The step of simultaneously sending a start signal to all the execution units at a preset time specifically includes: Based on the current time indicated by the global clock reference, the next integer multiple of the clock cycle boundary of the current time is taken as the preset time; When the global clock reference reaches the preset time, a start signal with the timestamp of the preset time is sent in parallel to each execution unit.
5. The method according to claim 3, characterized in that, In the step of acquiring the status information of each execution unit in parallel: By allocating independent communication channels or independent threads to each execution unit, status query requests are sent concurrently to each execution unit within the same time period, and each unit independently receives the returned status response.
6. The method according to claim 1, characterized in that, After acquiring the status information of each execution unit in parallel, the process further includes: Set the timeout threshold for status acquisition; If complete status information of any execution unit cannot be obtained within the timeout threshold, or if it is determined from the obtained status information that any execution unit does not meet the preset executable conditions, then the step of sending the start signal is prohibited, and feedback prompt information is generated.
7. The method according to claim 1, characterized in that, Prior to the step of responding to the start command, the method further includes: In response to user input of initial setting commands or according to preset configuration files, generate the initial execution parameters required by each execution unit for this task; Before sending the start signal to each execution unit, the initial execution parameters are sent to the corresponding execution units respectively, so that each execution unit uses the initial execution parameters as the starting state of this task when it receives the start signal.
8. The method according to claim 1, characterized in that, Following the step of simultaneously sending a start signal to all the execution units, the method further includes: After receiving the start signal, each execution unit independently records the runtime of this task, using the preset time as the starting reference point. Periodically generate time-stamped data containing the current running status, current task execution progress, and current running time of the execution unit, so as to facilitate subsequent time axis alignment and correlation analysis of the running data of multiple execution units.
9. The method according to claim 1, characterized in that, After simultaneously sending the start signal to all the execution units, the method further includes: Upon receiving the start signal, each execution unit returns a start confirmation response to the main control device; The main control device determines whether it has received the start confirmation response from all execution units within the preset timeout threshold; If yes, then the synchronous startup is confirmed to be successful; if not, the execution unit that did not return a startup confirmation response is marked as a startup exception, and exception handling operations are performed.
10. A synchronous start-up device for a multi-station system, characterized in that, include: The time reference establishment module is used to establish a global clock reference and unify the time references of multiple execution units participating in the same task in the system to the global clock reference; The status acquisition module is used to acquire the status information of each execution unit in parallel before executing the start action in response to the start command. as well as, The synchronous triggering module is used to send a start signal to all the execution units simultaneously at a preset time, based on the global clock reference, when it is determined from the status information that all execution units meet the preset executable conditions.
