A solenoid valve multi-plate distributed control system

Abstract

The present application belongs to the technical field of program control and distributed control, and particularly relates to a solenoid valve multi-plate distributed control system. The system comprises collector plates, controller plates, executor plates and communicator plates which communicate through inter-plate networks. The collector plates encapsulate multi-channel temperature, pressure and flow data into control semantic data frames carrying collector channel identification, sampling time point identification, data stability flag and control object identification. The controller plates align states according to solenoid valve control periods and generate control state frames, and then generate control instructions carrying state frame number, parameter version number and instruction valid time window. The executor plates check and drive solenoid valves according to the control instructions. The communicator plates versionize and synchronize user set parameters. The system forms a closed loop corresponding relationship of collected data, control decision, execution feedback and parameter synchronization, and reduces control state inconsistency caused by distributed transmission delay, disorder and parameter cross-period switching.

Description

Technical Field

[0001] This invention belongs to the field of program control and distributed control technology, specifically relating to a multi-plate distributed control system for solenoid valves. Background Technology

[0002] Solenoid valve control systems are commonly used in laboratory fluid control, experimental pipeline switching, pressure release, flow distribution, and temperature-linked regulation. They typically consist of multiple sensors, solenoid valve drive circuits, a controller, and a human-machine interface. A common existing solution is a centralized control structure, where temperature, pressure, and flow sensor signals are uniformly connected to a main control board or control cabinet. The main control board handles sampling conversion, logic judgment, output control, and status display. Multi-core cables are then used to connect the individual solenoid valve coils, feedback contacts, and display interfaces. In this solution, the control logic is centralized in a single control node. Sensor data and valve status are typically processed according to a fixed scan cycle. After obtaining the sensor values, the main control board directly executes threshold judgments, interlock judgments, or sequential control, and drives relays, transistors, or dedicated drive circuits through the output ports to control the solenoid valves to engage, release, or hold. While this centralized deployment simplifies control logic in early scenarios with a small number of valves, it complicates the cabling, port usage, field wiring, and troubleshooting as the number of sensor and execution channels increases.

[0003] To reduce the wiring density of centralized control systems, some existing solutions are beginning to adopt a functional board-based approach, separating data acquisition, control, execution, and communication / display functions, and using inter-board communication for data forwarding. For example, the acquisition board connects to multiple temperature, pressure, and flow sensors, uploading the sampled data to the control board; the control board generates valve opening and closing commands based on preset logic; the execution board receives the control commands, drives multiple solenoid valves, and sends back the switch status; the communication board connects to the monitoring interface for parameter display and user settings. This approach reduces long-distance multi-core cables at the hardware connection level and allows each functional board to be expanded according to the number of channels. However, existing board-based systems still largely use ordinary message forwarding and sequential execution modes for control data processing. Sensor data directly participates in the current cycle judgment after reaching the control board, control commands directly enter the drive process after reaching the execution board, and user parameters directly overwrite control parameters after being sent via the communication board. This approach distributes functions across different boards but does not establish a unified control semantic association for sampling time, control cycle, parameter version, and execution feedback.

[0004] In a multi-board distributed control environment, temperature, pressure, and flow data come from different acquisition channels and arrive at different times after being transmitted through the inter-board network. Control commands transmitted from the controller board to the actuator board also experience queuing, retransmission, or delayed execution feedback. If the controller board directly combines multiple sensor values ​​according to the data arrival order, it may treat data from different control cycles as the same fluid state. If the actuator board does not verify the state frame, parameter version, and valid time window corresponding to the command, expired commands may continue to drive the solenoid valve under new fluid states. If user-set parameters take effect midway through a control cycle, the same round of acquired data may correspond to different control rules. The main technical problem arising from this is that existing multi-board distributed control systems for solenoid valves lack a timing consistency control mechanism that runs through the acquisition, decision-making, execution, and parameter synchronization processes, making it difficult for the control decisions formed by the controller and the actual solenoid valve actions executed by the actuator to correspond to the same fluid state section. Summary of the Invention

[0005] The purpose of this invention is to provide a multi-plate distributed control system for solenoid valves, which can solve the problems mentioned in the background art.

[0006] To achieve the above objectives, the technical solution adopted by the present invention is as follows: A multi-board distributed control system for solenoid valves includes a data acquisition board, a controller board, an actuator board, and a communication board that communicate in a distributed manner through an inter-board network. The data acquisition board is used to encapsulate multiple temperature, pressure and flow acquisition data into control semantic data frames carrying acquisition channel identifiers, sampling time identifiers, data stability flags and control object identifiers; The controller board is used to perform state alignment on the control semantic data frame according to the solenoid valve control cycle, generate a control state frame, and generate a solenoid valve control command carrying a state frame number, parameter version number, and instruction validity time window based on the control state frame. The actuator board is used to verify the solenoid valve control command based on the status frame number, parameter version number and command validity time window, and associate the solenoid valve execution feedback with the corresponding control command and send it back. The communicator board is used to synchronize user-set parameters in a versioned manner.

[0007] Preferably, when generating the control semantic data frame, the data acquisition board establishes a sampling time identifier, a data acquisition batch identifier, and an edge preprocessing identifier for the temperature, pressure, and flow data corresponding to the same controlled object, respectively. The edge preprocessing identifiers include data smoothing status, data mutation status, and data missing status; The control object identifier is bound to the solenoid valve number, sensor channel number, and control cycle number. The data acquisition board caches unuploaded data frames according to the control cycle number, and only uploads data frames that are still within the available cycle range after the inter-board network is restored.

[0008] Preferably, the controller board is provided with a state alignment window for the control cycle of the solenoid valve, and the state alignment window receives control semantic data frames from different acquisition channels according to the control object identifier; The controller board synthesizes temperature, pressure and flow data that fall within the same state alignment window into a control state frame, and configures the control state frame with any of the following validity levels: complete state, compensated state, pending confirmation state and failure state. The controller board generates solenoid valve control commands only based on control state frames that meet the access conditions of the control rules.

[0009] Preferably, when the controller board generates the solenoid valve control command, it writes the status frame number, parameter version number, command validity time window, target solenoid valve number, expected execution status and abnormal rollback identifier into the same control command frame; After receiving the control command frame, the actuator board performs a consistency check based on the locally recorded current state of the solenoid valve, the most recently executed command number, and the queue of incomplete commands. The actuator board executes the drive for control command frames that pass verification, and generates a feedback frame containing the rejection type and the original command number for control command frames that fail verification.

[0010] Preferably, the collector board sets a frame sequence continuity identifier and an adjacent frame trend identifier for the control semantic data frame; The frame sequence continuity identifier is generated by the upload order of the same acquisition channel in adjacent control cycles, and the adjacent frame trend identifier is formed by the change direction of temperature, pressure and flow data in a preset sampling period. The controller board identifies out-of-order data frames based on the continuous frame sequence identifier, identifies data frames whose change direction is inconsistent with the same controlled object based on the adjacent frame trend identifier, and writes the identification results into the validity level record of the corresponding control status frame.

[0011] Preferably, the state alignment window includes a main window and a delay compensation window; The main window receives control semantic data frames that fall within the current solenoid valve control cycle, and the delay compensation window receives control semantic data frames whose sampling time identifier is within the current solenoid valve control cycle and whose arrival time is delayed. The controller board generates a complete control status frame when the main window data is complete, generates a compensation status control status frame when the main window data is missing but the delay compensation window has matching data, and generates a pending confirmation status or failure status control status frame when both windows lack the necessary acquisition channel data.

[0012] Preferably, the controller board configures a data source table for each control state frame, and the data source table records the acquisition channel identifier, sampling time identifier, edge preprocessing identifier, and state alignment window type corresponding to the temperature, pressure, and flow data; Before generating solenoid valve control commands, the controller board matches and verifies the data source table with the current parameter version number. When the sampling time corresponding to any necessary data acquisition is later than the effective time of the parameter version number, the control status frame is included in the new parameter version control sequence. When the sampling time corresponding to any necessary data acquisition is earlier than the effective time of the parameter version number, the control status frame is retained in the original parameter version control sequence.

[0013] Preferably, the actuator board establishes a local execution registration table for the control command frame, and the local execution registration table records the original command number, status frame number, parameter version number, target solenoid valve number, drive start flag, action completion flag and status stability flag; When the actuator board receives a new control command frame, it compares the new control command frame with the incomplete records in the local execution registration table. Execution is refused when the target solenoid valve number is the same and the status frame number is earlier than the incomplete record. When the target solenoid valve number is the same and the parameter version number is inconsistent, the controller board is requested to reconfirm the control command frame.

[0014] Preferably, the controller board sets cross-cycle reference tags for the control semantic data frames in the main window and the delay compensation window; The cross-cycle reference marker records the original control cycle number to which the compensated data frame belongs, the target control cycle number into which the compensation is entered, and the corresponding control object identifier. When the controller board receives a data frame with the same original control cycle number as the cross-cycle reference mark in a subsequent control cycle, it performs a duplicate check on the data source table of the subsequently arriving data frames and the generated control status frames, and excludes the duplicate data frames from the solenoid valve control command generation process.

[0015] Preferably, when the actuator board sends back feedback on the execution of the solenoid valve, it combines the original instruction number, status frame number, parameter version number, action completion identifier, and status stability identifier in the local execution registration table into an execution receipt frame. After receiving the execution receipt frame, the controller board writes the execution receipt frame into the closed-loop record of the corresponding control status frame, and restricts the generation of subsequent control commands for the same target solenoid valve under the same parameter version number according to the closed-loop record. When the communicator board receives user-set parameters, it determines the synchronization boundary for the new parameter version number to enter the next control cycle based on the closed-loop record.

[0016] Compared with the prior art, the beneficial effects of the present invention are as follows: 1. The data acquisition board generates control semantic data frames carrying acquisition channel identifiers, sampling time identifiers, data stability flags, and controlled object identifiers. The controller board constructs a state alignment window according to the solenoid valve control cycle and generates control state frames. The actuator board verifies control commands based on the state frame number, parameter version number, and command validity time window, ensuring that temperature, pressure, and flow data, control decisions, and valve actions are confined within the same control cycle. Therefore, the controller board no longer simply forms control judgments based on the order of data arrival, but generates control state frames based on data within the same state alignment window; the actuator board no longer unconditionally executes received commands, but determines whether they still belong to the current control process based on the timing and version information carried by the command. The data semantic encapsulation at the acquisition end, the state frame generation at the control end, the command verification at the execution end, and the parameter versioning synchronization at the communication end together form a closed-loop constraint, making it difficult for expired data, out-of-order data, cross-cycle commands, and unsynchronized parameters to enter the same control judgment chain, thus solving the problem of inconsistent correspondence between control decisions and solenoid valve actions under distributed inter-board transmission conditions.

[0017] 2. Through frame sequence continuity identification, adjacent frame trend identification, main window, delay compensation window, data source table, local execution registration table, and execution receipt frame, abnormal data, delayed data, duplicate instructions, and incomplete instructions in the distributed control process are processed in a hierarchical manner. The data acquisition board establishes continuity and trend records for data frames within adjacent control cycles. The controller board can identify out-of-order frames and data frames with inconsistent change directions before generating control status frames. The main window, in conjunction with the delay compensation window, ensures that data sampled at the current control cycle but arriving late can be included in the controlled compensation process, rather than being directly discarded or misused in the next cycle. The actuator board records the original instruction number, status frame number, parameter version number, action completion identifier, and status stability identifier through the local execution registration table, providing a verifiable execution boundary between incomplete actions of the same target solenoid valve and subsequent instructions. The communicator board determines the synchronization boundary for new parameter versions to enter the next control cycle based on closed-loop records, avoiding user-set parameters switching in the middle of the same control cycle, and providing clear data sources and execution records for system maintenance, status tracing, and anomaly location. Attached Figure Description

[0018] Figure 1 This is a flowchart of the full-link closed-loop control of a multi-plate distributed control system for solenoid valves. Figure 2 Flowchart for controlling semantic data frame generation and cache upload of the data acquisition board; Figure 3 Flowchart for state alignment window, delay compensation, and parameter version matching; Figure 4 Flowchart for local execution registration, execution receipt, and parameter synchronization boundary confirmation for actuator board. Detailed Implementation

[0019] In one embodiment, a multi-board distributed control system for a solenoid valve includes a data acquisition board, a controller board, an actuator board, and a communicator board for distributed control communication via an inter-board network. The data acquisition board encapsulates multiple channels of temperature, pressure, and flow data into control semantic data frames carrying acquisition channel identifiers, sampling time identifiers, data stability flags, and controlled object identifiers. The controller board aligns the control semantic data frames according to the solenoid valve control cycle, generates control state frames, and generates solenoid valve control commands carrying state frame numbers, parameter version numbers, and command validity time windows based on the control state frames. The actuator board verifies the solenoid valve control commands based on the state frame number, parameter version number, and command validity time window, and associates and transmits the solenoid valve execution feedback with the corresponding control commands. The communicator board synchronizes user-set parameters using versioning.

[0020] In this embodiment, reference Figure 1 Instead of using ordinary data pass-through for distributed control, the data acquisition board, controller board, actuator board, and communicator board use control semantic data frames, control status frames, control command frames, and execution feedback frames as continuous data carriers within the same control cycle. The data acquisition board assigns temperature, pressure, and flow data according to the controlled object identifier. The controller board combines data uploaded from different channels into the same state alignment range. The actuator board verifies the status frame number and parameter version number referenced by the control command before driving the solenoid valve. The communicator board establishes version boundaries for user-set parameters. This process ensures that the acquired data, control logic, valve actions, and parameter settings are continuously recorded and verified within the same distributed control chain.

[0021] Specifically, after receiving multiple temperature, pressure, and flow sensor data, the data acquisition board performs data integrity checks and instantaneous anomaly marking on the raw acquired values. Then, it maps each acquired data to a corresponding control object. The control object can be a single solenoid valve or a group of solenoid valve control objects constrained by multiple sensor data. The acquisition channel identifier is used to indicate the data source, the sampling time identifier is used to indicate the sampling position of the data, the data stability flag is used to indicate whether the data can participate in the control judgment within the current control cycle, and the control object identifier is used to group different types of sensor data into the same fluid state section, so that the controller board can still identify which data should be combined into the same control state even when the arrival order of distributed communication is inconsistent.

[0022] In this embodiment, after the control semantic data frame enters the controller board, the controller board establishes state alignment logic based on the solenoid valve control cycle. The state alignment logic does not use the message arrival time as the sole criterion for judgment, but simultaneously reads the sampling time identifier, the controlled object identifier, and the data stability flag. The controller board groups data of the same controlled object whose sampling time falls within the same control cycle into the same candidate set, and then generates a control state frame based on the completeness of the temperature, pressure, and flow data. The control state frame serves as the sole data basis for subsequent control commands, preventing the controller board from combining the pressure data of the previous control cycle with the flow data of the next control cycle into an incorrect fluid state.

[0023] In this embodiment, the alignment degree of the control state frames is calculated using timing consistency. Timing consistency characterizes the temporal proximity of different acquired data within the same control state frame. The timing consistency is denoted as... The calculation method is as follows: ; in, This represents the sampling time identifier corresponding to the i-th acquired data, n represents the number of acquired data participating in the synthesis of the same control state frame, T represents the logic length of the current solenoid valve control cycle, the minus sign indicates the difference between the sampling time span and the control cycle, and the division sign indicates converting the sampling time span into a relative quantity. For example, if the sampling times of temperature, pressure, and flow data within the same control state frame are taken as logic positions 2, 3, and 4 respectively, and the logic length of the current control cycle is 10, then... This indicates that the multi-source acquired data within the control state frame are highly similar to each other within the same fluid state section, and the controller board can use them as the basis for control in the same cycle.

[0024] When the controller board generates a solenoid valve control command based on the control status frame, it writes the status frame number, parameter version number, and command validity time window into the control command. The status frame number points to the control status frame on which the control command was generated, the parameter version number points to the user setting parameters that have been synchronized by the communicator board and confirmed by the controller board, and the command validity time window limits the control cycle boundary that the control command can be accepted by the actuator board. After receiving the control command, the actuator board first checks whether the status frame number belongs to the current executable queue, then checks whether the parameter version number is consistent with the local record, and then checks whether the command validity time window covers the current execution time. Only when all three conditions are met will the solenoid valve drive process begin.

[0025] After the actuator board completes the solenoid valve actuation, it establishes a correlation between the feedback data and the original control command. The feedback data includes the original command number, the target solenoid valve number, the action completion flag, and the state stability flag. The controller board receives the feedback data and writes it into the closed-loop record of the corresponding control state frame. If the feedback data fails to match any state frame number, the controller board retains the feedback data as a record to be checked and prohibits it from participating in the next round of control judgment. When the user modifies the setting parameters, the communicator board does not directly overwrite the control parameters currently being used by the controller board. Instead, it generates a new parameter version number and waits for the controller board to confirm the synchronization boundary. The new parameter version number enters the control operation in the next control cycle or at an idle boundary confirmed by the controller board. The control semantic data frame fields and their processing meanings are shown in Table 1 below.

[0026] Table 1. Control Semantic Data Frame Fields and Their Processing Meanings

[0027] In Table 1, each field is written into different data carriers in the order of acquisition, alignment, decision-making, execution, and feedback. The acquisition channel identifier and sampling time identifier are used to solve the problem of attribution of multi-source acquisition data. The data stability flag and control object identifier are used to limit the data range participating in the synthesis of control status frames. The status frame number, parameter version number, and instruction validity time window are used to limit the execution qualification of control instructions. Based on this, the actuator board can reject instructions that are cross-cycle, cross-version, or whose source cannot be traced in the distributed control communication. In this embodiment, the multi-board distributed control process has a unified timing reference basis and instruction closed-loop basis.

[0028] In a preferred embodiment, reference Figure 2When generating the control semantic data frame, the data acquisition board establishes a sampling time identifier, a data acquisition batch identifier, and an edge preprocessing identifier for the temperature, pressure, and flow data corresponding to the same controlled object, respectively. The edge preprocessing identifier includes data smoothing state, data mutation state, and data missing state. The control object identifier is bound to the solenoid valve number, sensor channel number, and control cycle number. The data acquisition board caches data frames that have not been uploaded according to the control cycle number, and only uploads data frames that are still within the available cycle range after the inter-board network is restored.

[0029] Specifically, the data acquisition board sets a unified control cycle number for the temperature, pressure, and flow data of the same controlled object, and sets a data acquisition batch identifier for data from different sensor channels within the same control cycle. The data acquisition batch identifier is used to reflect the order in which the data is generated. The edge preprocessing identifier is written by the data acquisition board after completing the basic discrimination locally. The data smooth state indicates that the changes of adjacent sampled data are continuous. The data abrupt state indicates that there is a discontinuous change in direction or amplitude between the current sampled data and the previous sampled data. The data missing state indicates that no usable data has been generated for the corresponding channel in the current control cycle. The data acquisition board does not delete the data of the entire controlled object due to the missing of a single channel, but writes the missing state into the control semantic data frame, so that the controller board can perform hierarchical processing during the state alignment stage.

[0030] The data acquisition board manages the cached data frames using control cycle numbers. The cache queues are established according to the control object identifiers. When the inter-board network communication is interrupted, the data acquisition board continues to form control semantic data frames locally and record their control cycle numbers. After the inter-board network is restored, the data acquisition board does not upload all cached data frames in the order they were cached. Instead, it compares the control cycle numbers of the cached data frames with the current available cycle range broadcast by the controller board. Only data frames that are still within the available cycle range are allowed to be uploaded. Data frames that have exceeded the available cycle range are retained as local trace records or marked as expired frames to prevent historical data from being centrally entered into the controller board after the network is restored and interfering with the current solenoid valve control status.

[0031] Furthermore, the data acquisition board performs combined verification of the sampling time identifier, the acquisition batch identifier, and the edge preprocessing identifier. If a certain acquisition channel generates multiple sampling values ​​within the same control cycle, the data acquisition board prioritizes retaining the sampling values ​​with continuous acquisition batch identifiers and edge preprocessing identifiers indicating a smooth data state. If a certain channel experiences a data mutation, the data acquisition board encapsulates the mutation data together with the adjacent data before and after it, enabling the controller board to determine whether the mutation is due to a change in fluid state or an acquisition anomaly. If a certain channel experiences a data missing state, the data acquisition board still uploads data from other channels of the same controlled object and writes the missing state into the corresponding field. In this embodiment, the out-of-order, missing, and mutation problems that the acquisition end cannot directly solve are handed over to the controller board for processing in a structured semantic form, avoiding the incomplete state profile caused by the acquisition end simply discarding data.

[0032] In a preferred embodiment, the controller board is provided with a state alignment window oriented towards the solenoid valve control cycle. The state alignment window receives control semantic data frames from different acquisition channels according to the controlled object identifier. The controller board synthesizes temperature, pressure, and flow data falling within the same state alignment window into a control state frame, and configures any one of the following validity levels for the control state frame: complete state, compensated state, pending confirmation state, and failed state. The controller board generates solenoid valve control commands only based on control state frames that meet the control rule admission conditions.

[0033] In this embodiment, the state alignment window uses the controlled object identifier as the entry point and the solenoid valve control cycle as the time boundary. Within the same window, the controller board waits for the arrival of temperature, pressure, and flow data, and reads the sampling time identifier, edge preprocessing identifier, and data stability flag of each data frame. If all three types of data are within the same control cycle and there are no missing states, the controller board synthesizes them into a complete control state frame. If there are gaps that can be filled by delayed data, the controller board synthesizes them into a compensated control state frame. If the missing data belongs to a necessary acquisition object but is still within the waiting range, the controller board sets it to a pending confirmation state. If the necessary acquisition object is missing and the waiting range has ended, the controller board sets it to a failed state.

[0034] The control rule admission criteria are determined by the controller board based on the type of the controlled object and the parameter version number. Control state frames in a complete state can directly enter the control rule calculation. Control state frames in a compensated state need to record the compensation source in the data source table before entering the control rule calculation. Control state frames in a pending state are only allowed to enter the hold judgment or wait judgment. Control state frames in a failed state are not allowed to generate new solenoid valve switching commands. Before generating control commands, the controller board verifies the validity level of the control state frame. If the validity level of the control state frame does not match the data completeness required by the control rule, the controller board does not generate a switching command, but keeps the current controlled object in a traceable waiting state. In this embodiment, through window alignment and hierarchical admission, the decisions formed by the controller board are only derived from state frames with clear data composition.

[0035] In a preferred embodiment, when the controller board generates the solenoid valve control command, it writes the status frame number, parameter version number, command validity time window, target solenoid valve number, expected execution status, and abnormal rollback identifier into the same control command frame. After receiving the control command frame, the actuator board performs a consistency check based on the locally recorded current solenoid valve status, the most recently executed command number, and the queue of incomplete commands. The actuator board executes the drive for control command frames that pass the check and generates a feedback frame containing the rejection type and the original command number for control command frames that fail the check.

[0036] Specifically, the status frame number of the control command frame is used to determine which control status frame the control command comes from, the parameter version number is used to determine which set of user-defined parameters the control logic uses, the command validity time window is used to limit the control cycle range that the command can be accepted by the actuator board, the target solenoid valve number is used to determine the driven object, the expected execution state is used to limit the target state of engagement, release or hold, and the abnormal rollback flag is used to determine the hold or rollback strategy of the solenoid valve when the verification fails or the execution feedback is abnormal. After receiving the control command frame, the actuator board does not directly enter the drive output, but compares the control command frame with the currently recorded solenoid valve state, the most recently executed command number and the queue of incomplete commands.

[0037] The consistency check of the actuator board includes source consistency, version consistency, time consistency, and state consistency. Source consistency is used to verify whether the state frame number is within the range of executable state frames received by the actuator board. Version consistency is used to verify whether the parameter version number is consistent with the local synchronized version. Time consistency is used to verify whether the current execution time is within the instruction valid time window. State consistency is used to verify whether the current state of the target solenoid valve allows it to enter the expected execution state. If any check item is not satisfied, the actuator board will not execute the drive and will generate a feedback frame containing the rejection type and the original instruction number and return it to the controller board. The controller board will write the rejection reason into the closed-loop record of the corresponding control state frame. In this embodiment, the actuator end becomes an active verification node in the distributed control closed loop, rather than an ordinary switch output node.

[0038] In a preferred embodiment, the data acquisition board sets a frame sequence continuity identifier and an adjacent frame trend identifier for the control semantic data frame; the frame sequence continuity identifier is generated by the upload order of the same acquisition channel in adjacent control cycles, and the adjacent frame trend identifier is formed by the change direction of temperature, pressure and flow data in a preset sampling period; the controller board identifies out-of-order data frames based on the frame sequence continuity identifier, identifies data frames whose change direction is inconsistent with the same controlled object based on the adjacent frame trend identifier, and writes the identification results into the validity level record of the corresponding control status frame.

[0039] In this embodiment, the frame sequence consecutive identifier is formed by incrementing the data frame order within adjacent control cycles of the same acquisition channel. When the controller board receives data frames from the same acquisition channel, it compares the current frame sequence consecutive identifier with the consecutive identifier of the previously received data frame. If the consecutive identifier of the current frame is earlier than the received frame, the controller board marks it as an out-of-order data frame. If the consecutive identifier of the current frame skips an intermediate sequence number, the controller board records the intermediate gap as a potential frame loss position. The adjacent frame trend identifier is formed by the acquisition board based on the changing direction of adjacent sampled data. The changing direction can be upward, downward, stable, or uncertain. The controller board combines the trend identifiers of temperature, pressure, and flow rate within the same controlled object. If the combination relationship is inconsistent with the preset fluid control logic, the trend conflict is recorded in the control status frame.

[0040] The frame sequence continuity identifier and the adjacent frame trend identifier jointly participate in the determination of the validity level of the control state frame. Out-of-order data frames are not directly deleted, but are judged whether they can enter the delay compensation window based on the sampling time identifier. Trend conflict data frames are not directly identified as errors, but are judged together with the data stability flag and the edge preprocessing flag. If the trend conflict comes from the data change state, the controller board sets the control state frame to the pending confirmation state. If the trend conflict comes from out-of-order data, the controller board excludes it from the current state frame synthesis process. In this embodiment, abnormal network transmission order and abnormal fluid state change are treated separately to reduce the number of erroneous control commands generated by the controller board due to a single abnormality flag.

[0041] In this embodiment, trend consistency can be calculated using a trend sign vector, and the trend consistency value is denoted as . The calculation method is as follows: ; in, This indicates the actual trend sign of the current controlled object on the i-th acquisition type. This represents the allowed reference trend symbol for the same controlled object under the current control rules. 'm' represents the number of data acquisition types participating in the trend comparison. The multiplication sign indicates the directional matching relationship between the actual trend and the reference trend on the same data acquisition type. The square root sign indicates normalization of the trend vector. For example, if the actual trend symbol for temperature, pressure, and flow is (1,1,0), and the reference trend symbol is (1,1,0), then... This indicates that the current trend combination is consistent with the allowed trend combination. If the actual trend sign is (1, -1, 0), then... This indicates that the pressure trend is opposite to the reference trend, and the controller board will include the corresponding control status frame in the pending confirmation or compensation judgment.

[0042] In a preferred embodiment, reference Figure 3 The state alignment window includes a main window and a delay compensation window. The main window receives control semantic data frames that fall within the current solenoid valve control cycle, and the delay compensation window receives control semantic data frames whose sampling time identifier is within the current solenoid valve control cycle and whose arrival time is delayed. The controller board generates a complete state control state frame when the main window data is complete, generates a compensated state control state frame when the main window data is missing but the delay compensation window has matching data, and generates a pending confirmation state or a failed state control state frame when both windows lack necessary acquisition channel data.

[0043] Specifically, the main window is used to receive data frames that arrive at the controller board according to the normal arrival order, while the delay compensation window is used to receive data frames whose sampling time belongs to the current control cycle but whose arrival time is delayed. When the controller board determines whether the data in the delay compensation window can be matched, it does not directly fill in the gaps according to the arrival order, but checks the control object identifier, sampling time identifier, acquisition batch identifier, and frame sequence continuity identifier. Only when all of the above fields can correspond to the gaps in the main window are the delayed data allowed to enter the control state frame of the compensation state. If the delayed data cannot correspond to the gaps in the main window, the controller board sets it as cross-cycle waiting verification data and does not use it for the generation of the current solenoid valve control command.

[0044] A window occupancy record is established between the main window and the delay compensation window. The controller board maintains a window reception table for each controlled object. The window reception table records the arrival status of each acquisition type in the main window, the candidate status in the delay compensation window, and the source of the data ultimately adopted. If the main window has formed a complete control state frame, the data arriving at the same sampling time in the delay compensation window will not replace the existing control state frame, but will enter the repeatability verification process. If there is a gap in the main window and the data in the delay compensation window can be filled in, the controller board writes a compensation source mark in the control state frame. In this embodiment, there is a clear reference boundary when processing network lag data to avoid the same sampled data being used repeatedly in different control cycles. The relationship between the state alignment window and the control state frame generation is shown in Table 2 below.

[0045] Table 2 Relationship between State Alignment Window and Control State Frame Generation

[0046] The window relationships shown in Table 2 are maintained independently by the controller board under each controlled object. The difference between the complete state and the compensated state is whether the data enters the control state frame through the delay compensation window. The difference between the pending confirmation state and the failed state is whether the necessary data acquisition is still at the waiting boundary. Repeated recording is used to prevent the same sampling source from participating in the generation of new control instructions again after the historical control state frame has been used. The window record is bound to the control state frame number, so that the controller board can trace the data source and data entry path of each control instruction.

[0047] In a preferred embodiment, the controller board configures a data source table for each control state frame. The data source table records the acquisition channel identifier, sampling time identifier, edge preprocessing identifier, and state alignment window type corresponding to temperature, pressure, and flow data. Before generating solenoid valve control commands, the controller board matches and verifies the data source table with the current parameter version number. When the sampling time corresponding to any necessary acquisition data is later than the effective time of the parameter version number, the control state frame is included in the new parameter version control sequence. When the sampling time corresponding to any necessary acquisition data is earlier than the effective time of the parameter version number, the control state frame is retained in the original parameter version control sequence.

[0048] In this embodiment, the data source table is generated along with the control status frame. The data source table is not an ordinary log, but a necessary verification basis before the generation of solenoid valve control commands. The controller board reads the sampling time identifier and status alignment window type in the data source table, and reads the current parameter version number and its effective time synchronized by the communicator board. When the sampling time of any necessary data in the control status frame is later than the effective time of the parameter version number, the controller board believes that the control status frame should be subject to the constraints of the new parameter version control sequence. When the sampling time of any necessary data is earlier than the effective time of the parameter version number, the controller board believes that the control status frame should be retained in the original parameter version control sequence to prevent data within the same status frame from crossing different parameter versions.

[0049] Furthermore, after receiving the user-set parameters, the communicator board sends the parameter content, parameter version number, and request effective boundary to the controller board. The controller board does not immediately replace the parameter version currently participating in the control state frame calculation. Instead, it determines whether the new parameter version can enter the next control cycle based on the data source table of the generated control state frames. If the data sources of the current control state frames are all earlier than the effective time of the new parameter version, the controller board continues to use the original parameter version to generate control commands. If the data sources of the new round of control state frames are all later than the effective time of the new parameter version, the controller board writes the new parameter version into the control command frame. In this embodiment, the synchronization process of the user-set parameters is incorporated into the data boundary of the control state frame to avoid parameter switching occurring within the same control state section.

[0050] In this embodiment, parameter version matching can be determined using a version attribution function, and the version attribution value is denoted as . The calculation method is as follows: ; in, This indicates the sampling time identifier of the i-th necessary data acquisition within the control state frame, where n represents the number of necessary data acquisitions. This indicates when the parameter version number takes effect. This indicates that the control status frame belongs to the original parameter version control sequence. This indicates that the control status frame belongs to the new parameter version control sequence. This indicates that there is cross-parameter version sampling data within the control state frame. For example, the sampling times for temperature, pressure, and flow are 2, 3, and 4 respectively, and the time when the parameter version takes effect is 5. The controller board uses the original parameter version; if the sampling times are 6, 7, and 8 respectively, and the parameter version takes effect at time 5, then... The controller board uses the new parameter version; if the sampling times are 4, 5, and 6 respectively, and the parameter version takes effect at time 5, then... The controller board does not use the state frame to generate switching instructions.

[0051] In a preferred embodiment, reference Figure 4 The actuator board establishes a local execution registration table for the control command frame. The local execution registration table records the original command number, status frame number, parameter version number, target solenoid valve number, drive start flag, action completion flag, and status stability flag. When the actuator board receives a new control command frame, it compares the new control command frame with the incomplete records in the local execution registration table. If the target solenoid valve number is the same and the status frame number is earlier than the incomplete record, execution is rejected. If the target solenoid valve number is the same but the parameter version number is different, the actuator board is requested to reconfirm the control command frame.

[0052] Specifically, the local execution registration form is generated by the actuator board after receiving a control command frame. The original command number is used to uniquely associate the command issued by the controller board, the status frame number is used to associate the data acquisition and decision-making source, the parameter version number is used to associate the user-set parameters, the target solenoid valve number is used to determine the execution object, the drive start identifier is used to record whether the drive process has started, the action completion identifier is used to record whether the solenoid valve action has reached the target state, and the state stability identifier is used to record whether the action is completed and the state is in a feedback-ready state. When the actuator board receives a new control command frame, it uses the target solenoid valve number as the main index to look up incomplete records and compares the new and old status frame numbers and parameter version numbers.

[0053] If a new control command frame has the same target solenoid valve number as an incomplete record and the new status frame number is earlier than the status frame number in the incomplete record, the actuator board considers the new control command frame to be an expired command and refuses to execute it. If a new control command frame has the same target solenoid valve number as an incomplete record but the parameter version numbers are inconsistent, the actuator board does not directly overwrite the execution status but sends a reconfirmation request to the controller board. If a new control command frame has the same target solenoid valve number as an incomplete record and the expected execution status is opposite to that of the incomplete record, the actuator board waits for the controller board to return confirmation information before processing it. This prevents the same solenoid valve from receiving conflicting drive commands when the action is incomplete. In this embodiment, the actuator provides a command boundary for the single valve action chain, reducing the interference of repeated commands and reverse commands on the solenoid valve status closed loop.

[0054] In a preferred embodiment, the controller board sets a cross-cycle reference mark for the control semantic data frames in the main window and the delay compensation window; the cross-cycle reference mark records the original control cycle number to which the compensated data frame belongs, the target control cycle number to which the compensation enters, and the corresponding control object identifier; when the controller board receives a data frame with the same original control cycle number as the cross-cycle reference mark in a subsequent control cycle, it performs a duplicate check on the data source table of the subsequently arriving data frames and the generated control status frames, and excludes the duplicate data frames from the solenoid valve control command generation process.

[0055] In this embodiment, the cross-cycle reference mark is generated along with the control state frame of the compensation state. The original control cycle number is used to indicate the cycle in which the compensated data frame is generated, the target control cycle number is used to indicate which control state frame the compensated data frame enters, and the control object identifier is used to limit the scope of the cross-cycle reference mark. When the controller board receives a data frame with the same original control cycle number in a subsequent control cycle, it does not directly participate in the synthesis of a new state frame because its arrival time is in a subsequent cycle. Instead, it searches the data source table of the generated control state frames. If the data source table already references the same acquisition channel identifier, the same sampling time identifier, and the same control object identifier, then the subsequent data frame is set as a duplicate data frame.

[0056] The repeatability check is also processed in conjunction with the frame sequence continuity identifier. If a subsequent data frame has the same sampling time as the referenced data frame but a different frame sequence continuity identifier, the controller board records it as a frame to be checked and prohibits it from participating in the generation of new control commands. If a subsequent data frame has the same frame sequence continuity identifier as the referenced data frame but a different sampling time, the controller board records it as an abnormal acquisition end number and notifies the acquisition board to check the cache record. The cross-cycle reference mark does not change the acquired data itself, but only limits whether it can enter the subsequent control state frame synthesis process. In this embodiment, the delay compensation data is prevented from being repeatedly referenced after the network is restored, so that the compensation mechanism and the duplicate exclusion mechanism form a continuous control chain.

[0057] In this embodiment, the duplicate reference determination can be performed using a data frame duplicate discrimination value. Perform calculations. The method for determining whether a newly arrived data frame has already been referenced by a control status frame is as follows: ; in, This indicates an instruction operation; the value is 1 if the condition within the parentheses is true, and 0 if the condition is false. 'c' represents the acquisition channel identifier for the newly arriving data frame. This indicates the acquisition channel identifier of the data frame already referenced in the data source table, and q indicates the sampling time identifier of the newly arrived data frame. This indicates the sampling time identifier of the referenced data frame, and 'o' indicates the control object identifier of the newly arrived data frame. This indicates the control object identifier that has referenced the data frame, and 'r' represents the original control cycle number of the newly arrived data frame. This indicates the original control period number of the cross-period reference marker record. For example, if all four identifiers are the same, then... The controller board will exclude newly arriving data frames from the instruction generation process; if any identifier is different, then... The controller board continues to verify window ownership and source.

[0058] In a preferred embodiment, when the actuator board sends back feedback on the execution of the solenoid valve, it combines the original instruction number, status frame number, parameter version number, action completion identifier, and status stability identifier from the local execution registration table into an execution receipt frame. After receiving the execution receipt frame, the controller board writes the execution receipt frame into the closed-loop record of the corresponding control status frame, and restricts the generation of subsequent control instructions for the same target solenoid valve under the same parameter version number based on the closed-loop record. When the communicator board receives user-set parameters, it determines the synchronization boundary for the new parameter version number to enter the next control cycle based on the closed-loop record.

[0059] Specifically, the execution receipt frame is generated by the actuator board after the solenoid valve completes its action or an abnormal action occurs. The original instruction number is used to correspond to the control instruction frame issued by the controller board, the status frame number is used to correspond to the control status frame, the parameter version number is used to correspond to the user-set parameter version, the action completion indicator is used to indicate whether the actuator board has completed the target drive action, and the status stability indicator is used to indicate whether the execution feedback can be used as the basis for closed-loop completion. After receiving the execution receipt frame, the controller board retrieves the corresponding control status frame by the status frame number and writes the execution receipt frame into the closed-loop record. If the closed-loop record shows that the same target solenoid valve still has incomplete actions under the same parameter version number, the controller board will not generate a new opposite status instruction.

[0060] When the communicator board receives new user-set parameters, it first forms a candidate parameter version number for the new parameters, and then requests a synchronization boundary from the controller board. The controller board searches the current closed-loop record. If the execution feedback frames corresponding to the relevant controlled objects all have action completion and state stability indicators, the controller board allows the candidate parameter version number to enter in the next control cycle. If any relevant solenoid valve still has an incomplete execution record, the controller board keeps the candidate parameter version number in a pending synchronization state until the closed-loop record forms a switchable boundary. Based on this, the communicator board avoids inserting new parameters into the ongoing control closed loop. In this embodiment, execution feedback and parameter version synchronization are directly associated, so that parameter updates do not disrupt the established cyclical relationship between acquisition, decision-making, and execution.

[0061] In this embodiment, the closed-loop state can be achieved through closed-loop completion values. express, The method for determining whether the same target solenoid valve is allowed to proceed to subsequent instruction generation under the same parameter version is as follows: ; Where u represents the target solenoid valve number corresponding to the instruction to be generated. This indicates the target solenoid valve number in the closed-loop record, and v indicates the parameter version number corresponding to the instruction to be generated. This represents the parameter version number in the closed-loop record. `f` represents the action completion flag, which can be either 0 or 1. `s` represents the state stability flag, which can also be either 0 or 1. For example, if the target solenoid valve number and parameter version number are the same, and both the action completion flag and the state stability flag are set to 1, then... The controller board allows subsequent control checks within the same version; if the action completion flag is 0 or the state stability flag is 0, then... The controller board maintains restrictions on the generation of subsequent instructions.

[0062] In this embodiment, the closed-loop record of the controller board and the parameter version of the communicator board are synchronized to form the control cycle boundary. The data acquisition board provides the data source for the same control state section. The controller board generates a control state frame based on the state alignment window and the data source table. The actuator board performs verification based on the local execution registration table and the control instruction frame. The communicator board determines the entry timing of the parameter version based on the closed-loop record. The acquisition end, control end, execution end, and communication end respectively process the data source, state synthesis, action boundary, and parameter boundary. The four types of processing refer to each other through the state frame number, parameter version number, and control object identifier. In this embodiment, the distributed control chain maintains traceable state association under the conditions of data delay, instruction queuing, feedback lag, and user parameter changes.

[0063] In one embodiment, the controller board also establishes an anomaly handling record when generating a control status frame. The anomaly handling record is not used as a new control route, but is instead used to uniformly archive the aforementioned status alignment, version matching, and execution receipt. If the data frame uploaded by the acquisition board is determined to be an out-of-order frame, the anomaly handling record saves its frame sequence continuity identifier and the original sampling time identifier. If the control status frame is determined to be a cross-parameter version status, the anomaly handling record saves the effective time of the parameter version number and the sampling time of each necessary acquisition data. If the actuator board rejects the control command frame, the anomaly handling record saves the rejection type and the original command number. When maintenance personnel read the anomaly handling record through the monitoring interface, they can locate the specific link in the acquisition, status synthesis, command execution, or parameter synchronization where the anomaly occurred.

[0064] Preferably, when displaying parameters, the communicator board does not directly show unverified single-channel acquisition values. Instead, it prioritizes displaying the data source table and closed-loop records that have entered the control state frame. After the user-set parameters are written into the candidate parameter version number, the communicator board simultaneously displays the synchronization status between the candidate parameter version number and the current parameter version number. If the controller board determines that there is an incomplete execution registration record, the communicator board retains the user-set parameters but does not trigger the controller board to switch versions. If the controller board returns a switchable boundary, the communicator board updates the candidate parameter version number to the current parameter version number. In this embodiment, the content displayed on the monitoring interface corresponds to the state frames, instruction frames, and acknowledgment frames within the distributed control system, avoiding the display parameters from being out of sync with the actual control parameters.

[0065] In a preferred embodiment, the inter-board network communication messages between the data acquisition board, controller board, actuator board, and communicator board all carry frame type identifiers. Control semantic data frames, control status frames, control instruction frames, execution receipt frames, parameter version frames, and exception feedback frames each use different frame type identifiers. The controller board determines whether the message enters the status alignment process, instruction generation process, closed-loop writing process, or parameter synchronization process based on the frame type identifier. The actuator board distinguishes between control instruction frames and reconfirmation requests based on the frame type identifier. The communicator board distinguishes between parameter candidate records and parameter synchronization confirmation records based on the frame type identifier. In this embodiment, different control semantic carriers are separated on the same inter-board network to prevent the mixing of ordinary messages from causing a break in the control chain.

[0066] In this embodiment, if a short-term interruption occurs in the inter-board network, the collector board continues to cache control semantic data frames according to the control cycle number, the controller board retains the generated control status frames and incomplete closed-loop records, the actuator board retains the incomplete records in the local execution registration table, and the communicator board retains the candidate parameter version number. After the interruption is restored, the collector board only uploads data frames that are still within the available cycle range, the controller board excludes referenced data using cross-cycle reference flags and duplicate discrimination values, the actuator board filters out expired instructions using status frame numbers and parameter version numbers, and the communicator board determines the parameter switching boundary using closed-loop records. In this embodiment, historical cached data after network recovery will not unconditionally enter the current control cycle.

[0067] In one embodiment, the controller board can form a sequential chain of control status frames for the same controlled object according to the status frame number. Each node in the sequential chain includes a data source table, validity level, parameter version number, control instruction frame reference, and execution receipt frame reference. If a control status frame does not generate a control instruction frame, the sequential chain records the reason type as pending confirmation, failure, cross version, or duplicate source. If a control status frame generates a control instruction frame but the actuator board refuses to execute it, the sequential chain records the rejection type and the original instruction number. Subsequent control status frames read the closed-loop status of the previous node before generating control instructions to avoid continuously generating control actions with unclear sources or inconsistent versions on the same target solenoid valve.

[0068] Preferably, when synthesizing control status frames, the controller board establishes necessity markers for temperature, pressure, and flow acquisition data. These necessity markers are jointly determined by the controlled object and user-set parameters. If the current control rule for a certain controlled object only requires pressure and flow data, temperature data can be written into the data source table as a reference source but not as an admission condition. If the current control rule for a certain controlled object requires temperature, pressure, and flow to participate in the judgment, the absence of any necessary acquisition data will cause the control status frame to enter a pending confirmation or invalidation state. The necessity markers are stored together with the parameter version number, so that the controller board can re-determine which acquisition data belongs to the necessary source after the parameter version changes. In this embodiment, the state alignment process is adapted to the data requirements of different controlled objects without expanding the hardware structure.

[0069] In this embodiment, the actuator board performs structured encoding on the rejection types of the feedback frames. The rejection types include at least the status frame number expired, parameter version inconsistency, instruction validity time window out of bounds, and the target solenoid valve having incomplete actions and conflicting with the expected execution state. After the actuator board generates a feedback frame containing the rejection type and the original instruction number, the controller board writes it into the closed-loop record of the corresponding control status frame. If the rejection type is status frame number expired, the controller board stops generating subsequent control instructions based on the status frame number. If the rejection type is parameter version inconsistency, the controller board triggers the communicator board to resynchronize the current parameter version. In this embodiment, feedback anomalies can be directly backfilled into the status frame that generated the instruction, rather than forming an isolated alarm record.

[0070] In a preferred embodiment, the controller board sets different control output permissions for the complete state, compensated state, pending confirmation state, and failed state. The complete state allows entry into the regular control rule judgment, the compensated state allows entry into the control rule judgment with compensation source records, the pending confirmation state only allows the generation of control instructions to maintain the original state or wait for confirmation, and the failed state does not allow the generation of new solenoid valve switching instructions. The actuator board also verifies the state frame number, parameter version number, and instruction validity time window for the instruction to maintain the original state. The communicator board displays the data source table corresponding to the pending confirmation state and the failed state. In this embodiment, different validity levels correspond to different instruction generation boundaries, so that the state frame classification results can actually constrain the solenoid valve control output.

[0071] In this embodiment, the controller board also sets a version continuity relationship for continuous control commands of the same target solenoid valve. The version continuity relationship is formed by the parameter version number, the status frame number, and the original command number. If the current control command and the previous control command have the same parameter version number and the status frame numbers are consecutive, the controller board allows the generation of subsequent commands after the execution of the acknowledgment frame loop closure. If the current control command and the previous control command have different parameter version numbers, the controller board reads the synchronization boundary given by the communicator board and checks the loop closure completion value. If the loop closure completion value is 0, the controller board retains the candidate command in the pending confirmation queue. In this embodiment, there is a clear sequential constraint between parameter updates and continuous solenoid valve actions.

[0072] In one embodiment, the data acquisition board writes data smoothing state, data mutation state, and data missing state by comparing adjacent sampled data. If the current sampled data changes in the same direction as the data in the previous control cycle of the same channel without forming a gap, the data acquisition board writes the data smoothing state. If the current sampled data changes in the opposite direction to the previous control cycle and other acquisition types of the same controlled object do not show the same trend, the data acquisition board writes the data mutation state. If the current control cycle does not obtain data of a certain necessary acquisition type, the data acquisition board writes the data missing state. After reading the edge preprocessing identifier, the controller board determines the validity level of the control state frame. In this embodiment, the preprocessing result of the acquisition end directly participates in the state frame admission and does not remain at the local filtering stage.

[0073] In this embodiment, the data source table, cross-cycle reference flag, local execution registration table, and closed-loop record of the controller board are associated through common fields. The common fields include the controlled object identifier, status frame number, parameter version number, and target solenoid valve number. The data source table is used to indicate which acquired data constitutes the control status frame, the cross-cycle reference flag is used to indicate which compensation data has been referenced, the local execution registration table is used to indicate the execution status of the control command on the actuator board, and the closed-loop record is used to indicate whether the execution feedback is returned to the controller board. The four types of records form a verifiable chain data structure. In this embodiment, anomaly location can be traced layer by layer along the acquisition source, status synthesis, command execution, and feedback closed loop.

[0074] In a preferred embodiment, after receiving a reconfirmation request from the actuator board, the controller board retrieves the original control instruction frame based on the original instruction number, and then retrieves the control status frame and data source table based on the status frame number. If the control status frame is still at the executable boundary and the parameter version number is still the current version, the controller board returns a confirmation execution frame to the actuator board. If the control status frame has crossed the instruction validity time window or the parameter version number has changed, the controller board returns a cancellation execution frame to the actuator board. The actuator board updates its local execution registration table based on the confirmation execution frame or the cancellation execution frame. In this embodiment, when the execution end discovers a parameter version conflict, the processing result comes from the controller board's review of the original data source and the current version boundary.

[0075] Preferably, when user-set parameters are modified, the communicator board binds the parameter change record to the control object identifier, instead of switching all control objects to the new parameter version. The controller board queries the corresponding closed-loop record based on the control object identifier and calculates the parameter version synchronization boundary only for the relevant control objects. For unrelated control objects, the controller board continues to generate instructions according to the original control state frame and the original parameter version number, and the actuator board still performs local registration table verification according to the target solenoid valve number. In this embodiment, parameter version synchronization can be limited to the corresponding control object range, reducing the impact of parameter updates on unrelated solenoid valve control chains.

[0076] In this embodiment, the operation of the multi-board distributed control system for solenoid valves can be understood as a continuous control process consisting of semantic data acquisition, state framing, instruction versioning, execution registration, and feedback closed-loop. The data acquisition board transforms dispersed temperature, pressure, and flow data into control semantic data frames with the controlled object and sampling time. The controller board transforms data from the same state section into control state frames. The actuator board transforms control commands into solenoid valve actions with registration boundaries. The communicator board transforms user parameters into synchronizeable parameter versions. The data carriers reference each other through common fields. In this embodiment, without changing the basic division of labor among the data acquisition board, controller board, actuator board, and communicator board, the timing consistency of distributed control is extended from single-point control logic to data constraints throughout the entire link.

Claims

1. A multi-plate distributed control system for solenoid valves, characterized in that, This includes data acquisition boards, controller boards, actuator boards, and communicator boards that communicate in a distributed manner via an inter-board network; The data acquisition board is used to encapsulate multiple temperature, pressure and flow acquisition data into control semantic data frames carrying acquisition channel identifiers, sampling time identifiers, data stability flags and control object identifiers; The controller board is used to perform state alignment on the control semantic data frame according to the solenoid valve control cycle, generate a control state frame, and generate a solenoid valve control command carrying a state frame number, parameter version number, and instruction validity time window based on the control state frame. The actuator board is used to verify the solenoid valve control command based on the status frame number, parameter version number and command validity time window, and associate the solenoid valve execution feedback with the corresponding control command and send it back. The communicator board is used to synchronize user-set parameters in a versioned manner.

2. The multi-plate distributed control system for solenoid valves according to claim 1, characterized in that, When generating the control semantic data frame, the data acquisition board establishes a sampling time identifier, a data acquisition batch identifier, and an edge preprocessing identifier for the temperature, pressure, and flow data corresponding to the same controlled object, respectively. The edge preprocessing identifiers include data smoothing status, data mutation status, and data missing status; The control object identifier is bound to the solenoid valve number, sensor channel number, and control cycle number. The data acquisition board caches unuploaded data frames according to the control cycle number, and only uploads data frames that are still within the available cycle range after the inter-board network is restored.

3. The multi-plate distributed control system for solenoid valves according to claim 1, characterized in that, The controller board is provided with a status alignment window for the control cycle of the solenoid valve. The status alignment window receives control semantic data frames from different acquisition channels according to the control object identifier. The controller board synthesizes temperature, pressure and flow data that fall within the same state alignment window into a control state frame, and configures the control state frame with any of the following validity levels: complete state, compensated state, pending confirmation state and failure state. The controller board generates solenoid valve control commands only based on control state frames that meet the access conditions of the control rules.

4. The multi-plate distributed control system for solenoid valves according to claim 1, characterized in that, When the controller board generates the solenoid valve control command, it writes the status frame number, parameter version number, command validity time window, target solenoid valve number, expected execution status and abnormal rollback flag into the same control command frame. After receiving the control command frame, the actuator board performs a consistency check based on the locally recorded current state of the solenoid valve, the most recently executed command number, and the queue of incomplete commands. The actuator board executes the drive for control command frames that pass verification, and generates a feedback frame containing the rejection type and the original command number for control command frames that fail verification.

5. A multi-plate distributed control system for solenoid valves according to claim 2, characterized in that, The data acquisition board sets a continuous frame sequence identifier and an adjacent frame trend identifier for the control semantic data frame; The frame sequence continuity identifier is generated by the upload order of the same acquisition channel in adjacent control cycles, and the adjacent frame trend identifier is formed by the change direction of temperature, pressure and flow data in a preset sampling period. The controller board identifies out-of-order data frames based on the continuous frame sequence identifier, identifies data frames whose change direction is inconsistent with the same controlled object based on the adjacent frame trend identifier, and writes the identification results into the validity level record of the corresponding control status frame.

6. A multi-plate distributed control system for solenoid valves according to claim 3, characterized in that, The state alignment window includes a main window and a delay compensation window; The main window receives control semantic data frames that fall within the current solenoid valve control cycle, and the delay compensation window receives control semantic data frames whose sampling time identifier is within the current solenoid valve control cycle and whose arrival time is delayed. The controller board generates a complete control status frame when the main window data is complete, generates a compensation status control status frame when the main window data is missing but the delay compensation window has matching data, and generates a pending confirmation status or failure status control status frame when both windows lack the necessary acquisition channel data.

7. A multi-plate distributed control system for solenoid valves according to claim 3, characterized in that, The controller board configures a data source table for each control state frame. The data source table records the acquisition channel identifier, sampling time identifier, edge preprocessing identifier, and state alignment window type corresponding to temperature, pressure, and flow data. Before generating solenoid valve control commands, the controller board matches and verifies the data source table with the current parameter version number. When the sampling time corresponding to any necessary data acquisition is later than the effective time of the parameter version number, the control status frame is included in the new parameter version control sequence. When the sampling time corresponding to any necessary data acquisition is earlier than the effective time of the parameter version number, the control status frame is retained in the original parameter version control sequence.

8. A multi-plate distributed control system for solenoid valves according to claim 4, characterized in that, The actuator board establishes a local execution registration table for the control command frame. The local execution registration table records the original command number, status frame number, parameter version number, target solenoid valve number, drive start flag, action completion flag, and status stability flag. When the actuator board receives a new control command frame, it compares the new control command frame with the incomplete records in the local execution registration table. Execution is refused when the target solenoid valve number is the same and the status frame number is earlier than the incomplete record. When the target solenoid valve number is the same and the parameter version number is inconsistent, the controller board is requested to reconfirm the control command frame.

9. A multi-plate distributed control system for solenoid valves according to claim 6, characterized in that, The controller board sets cross-cycle reference markers for the control semantic data frames in the main window and the delay compensation window; The cross-cycle reference marker records the original control cycle number to which the compensated data frame belongs, the target control cycle number into which the compensation is entered, and the corresponding control object identifier. When the controller board receives a data frame with the same original control cycle number as the cross-cycle reference mark in a subsequent control cycle, it performs a duplicate check on the data source table of the subsequently arriving data frames and the generated control status frames, and excludes the duplicate data frames from the solenoid valve control command generation process.

10. A multi-plate distributed control system for solenoid valves according to claim 8, characterized in that, When the actuator board sends back feedback on the execution of the solenoid valve, it combines the original instruction number, status frame number, parameter version number, action completion identifier, and status stability identifier in the local execution registration table into an execution receipt frame. After receiving the execution receipt frame, the controller board writes the execution receipt frame into the closed-loop record of the corresponding control status frame, and restricts the generation of subsequent control commands for the same target solenoid valve under the same parameter version number according to the closed-loop record. When the communicator board receives user-set parameters, it determines the synchronization boundary for the new parameter version number to enter the next control cycle based on the closed-loop record.

Images