A remote measurement and control method, system, device and medium

Abstract

The application discloses a remote measurement and control method, system, device and medium, and belongs to the technical field of distribution network measurement and control. The method comprises the following steps: determining a bus state and determining whether to start an occupation type scheduling strategy, making a slave station terminate sending through a physical layer conflict triggered interrupt, sending a control instruction message, and sending a query request to restore monitoring data uploading after receiving a slave station confirmation. The system comprises a measurement and control terminal and a slave station. The measurement and control terminal comprises an occupation type scheduling strategy selection module, a breaking signal injection module, a control instruction sending module and a recovery query sending module. The application actively injects a breaking signal which is incompatible with a data frame format protocol, so that the measurement and control terminal can recover the bus usage right and issue a control instruction without waiting for the current frame to end, the response delay of the control instruction is shortened to depend on the fixed length of the breaking signal, and the determinacy fast response of remote measurement and control of a distribution network magnetic control flexible interconnection device is realized.

Description

Technical Field

[0001] This invention relates to the field of power distribution network measurement and control technology, specifically to a remote measurement and control method, system, equipment, and medium. Background Technology

[0002] With the continuous integration of distributed power sources and diversified loads, the operation mode of distribution networks is undergoing profound changes. Flexible power exchange between distribution substations has become an important means to improve the operational flexibility of distribution networks and the capacity to absorb distributed energy. Magnetic control flexible interconnection devices are gradually being applied to flexible interconnection scenarios in low-voltage distribution substations due to their advantages such as low cost, small size, and ease of large-scale deployment.

[0003] The remote monitoring and control terminal of the magnetically controlled flexible interconnection device needs to simultaneously undertake two major tasks: uploading and displaying monitoring data and issuing and executing touch control commands. To achieve flexible power exchange between substations, the magnetically controlled flexible interconnection device adopts a three-phase half-bridge IGBT topology, with an LCL-type input filter circuit and an LC-type output filter circuit. The device's control strategy employs a dual-loop control structure with an outer voltage loop and an inner current loop. The outer voltage loop calculates a voltage reference value based on the grid voltage and load demand, while the inner current loop rapidly adjusts the output current to track the command value. The modulation method uses space vector pulse width modulation (SVPWM), which offers advantages over sinusoidal pulse width modulation (SPWM) in terms of higher DC voltage utilization and lower output harmonic content. The controller uses a proportional-integral (PI) control algorithm. This topology and control strategy impose higher response requirements on the real-time communication between the monitoring and control terminal and the device.

[0004] However, existing monitoring and control terminals mostly adopt RS485 (Recommended Standard 485) half-duplex bus communication based on the MODBUS (Modicon Communication Bus) protocol. In this communication mode, control commands must wait for the currently transmitted monitoring data frame to complete before gaining bus transmission rights. This results in a response delay for control commands that depends on the length of the monitoring data frame, making the delay time uncertain. When disturbances or faults occur in the distribution network, flexible interconnection devices need to quickly perform power dispatching or mode switching. The high latency response of control commands from the monitoring and control terminal directly affects the dynamic adjustment performance and operational safety of the system. Therefore, there is an urgent need for a remote monitoring and control method that can issue control commands instantly without waiting for the current data frame to end. Summary of the Invention

[0005] In view of the above-mentioned problems, the present invention provides a remote measurement and control method, system, device and medium.

[0006] Therefore, the technical problem solved by this invention is that in half-duplex bus communication, control commands must wait for the current data frame to finish transmitting before they can be sent, and the response delay is uncertain.

[0007] To solve the above-mentioned technical problems, the present invention provides the following technical solution: a remote monitoring and control method, comprising responding to the presence of a control command message to be sent: If the current bus is in the state of the measurement and control terminal receiving data frames, that is, the slave station is occupying the bus to send data, then it is further determined whether to enable the preemptive scheduling strategy. If the preemptive scheduling strategy is enabled, the priority preemption process is entered. If the measurement and control terminal is receiving data frames from the slave station, the measurement and control terminal actively injects an interrupt signal into the bus. The signal form of the interrupt signal is incompatible with the frame format protocol of the data frame, causing the slave station to trigger a hardware interrupt through a physical layer bus conflict, terminating the transmission of the current data frame. After the interrupt signal is sent, the control command message is sent to the bus. In response to the slave station receiving the control command message, it sends a monitoring data query request to the bus, prompting the slave station to resume uploading monitoring data.

[0008] As a preferred embodiment of the remote measurement and control method of the present invention, the method includes: before the measurement and control terminal actively injects an interruption signal into the bus, the method includes: The driver and receiver of the slave station's communication transceiver are both enabled during the transmission of the data frame; During the process of the slave station sending the data frame, the slave station continuously samples the actual level on the bus through the receiver and compares it with the driving level it is currently outputting.

[0009] The beneficial effects of this preferred technical solution are as follows: Before the interruption signal is injected by the measurement and control terminal, the driver and receiver of the slave station are both in an enabled state during the transmission of data frames, and the slave station continuously samples the bus level and compares it with its own output level. This solution provides the hardware foundation for the detection of physical layer bus conflicts in this invention, enabling the slave station to perceive changes in the bus level in real time during data frame transmission. Once the measurement and control terminal injects an interruption signal, the receiver of the slave station can immediately sample the difference between the bus level and its own drive level. There is no need to configure an additional dedicated conflict detection circuit; the real-time detection of physical layer conflicts can be achieved using only existing communication hardware, reducing system implementation costs and ensuring the real-time performance and reliability of conflict detection.

[0010] In a preferred embodiment of the remote measurement and control method described in this invention, the measurement and control terminal actively injects an interruption signal into the bus, comprising: When its own driver is enabled, the measurement and control terminal continuously outputs multiple levels to the bus. The levels of adjacent bits in the multiple levels are different, and the level of the stop bit of the multiple levels violates the provisions of the asynchronous serial communication protocol for stop bit levels followed by the data frame.

[0011] The advantages of this preferred technical solution are as follows: it limits the interrupt signal to a continuously output multi-bit mutually exclusive level sequence, and its stop bit level violates the stop bit level specification of the asynchronous serial communication protocol. This solution directly utilizes the inherent stop bit recognition mechanism of existing asynchronous serial communication hardware. The measurement and control terminal only needs to drive the bus according to a specific level sequence, and the slave station's communication hardware will automatically generate a frame error interrupt during bit-by-bit sampling because it cannot recognize a valid stop bit. This method does not require modification of the underlying logic of the slave station's communication hardware, requires no additional protocol stack processing time, and can trigger an interrupt response with a very short bit length. Compared with methods such as upper-layer protocol negotiation or software polling, it has the technical advantages of simple implementation and fast response speed.

[0012] As a preferred embodiment of the remote measurement and control method described in this invention, the step of the slave station terminating the transmission of the current data frame by triggering a hardware interrupt via a physical layer bus conflict includes: The slave station's communication hardware samples the bus level bit by bit according to the frame format of the asynchronous serial communication protocol to identify stop bits; The multi-bit level is superimposed on the current drive level of the slave station on the bus, causing the stop bit level sampled by the communication hardware to violate the stop bit level specification, thus failing to identify a valid stop bit and generating a frame error interrupt; After the frame error interruption occurs, the slave station reads the subsequent bits immediately following the stop bit from the multi-bit level as the interrupt feature code. After identifying the interrupt feature code as a preset feature code, it stops sending the current data frame and clears the transmission buffer.

[0013] The beneficial effects of this preferred technical solution are as follows: The slave station reads subsequent bits of the interrupt signal as an interrupt feature code after a frame error interruption occurs, and identifies priority preemption events by comparing the interrupt feature code with a preset feature code. This solution enables the slave station to accurately distinguish between priority preemption initiated by the telemetry and control terminal and occasional interference or bit errors on the communication line. The transmission of the current data frame is only stopped after the preset feature code is identified, avoiding invalid interruptions and data retransmissions caused by misjudgment of non-preemption trigger conditions. This improves the system's anti-interference capability and communication reliability, ensuring that the preemption mechanism is only triggered when the telemetry and control terminal actually issues a control command, and guaranteeing that the continuity of normal monitoring data upload is not affected by meaningless interruptions.

[0014] As a preferred embodiment of the remote measurement and control method described in this invention, the physical layer bus conflict includes: During the period when the measurement and control terminal outputs the multi-bit level to the bus, the bus simultaneously carries the driving level of the current data frame being output by the slave station and the multi-bit level output by the measurement and control terminal. The driving level of the slave station and the multi-bit level are superimposed on the bus to form a composite level. The receiver of the slave station samples a synthesized level that is inconsistent with the drive level currently output by the slave station, thereby determining that a bus conflict has occurred.

[0015] As a preferred embodiment of the remote measurement and control method of the present invention, the slave station reads the interrupt feature code after the frame error interruption occurs; After the preset feature code is identified, the slave station terminates the transmission of the current data frame and clears the transmission buffer, and the slave station's reception buffer is cleared after the interruption feature code is read. The slave station switches from the data transmission state to the control command reception state. The telemetry and control terminal sends the control command message to the slave station that is in the control command receiving state, and the control command message is fully received.

[0016] As a preferred embodiment of the remote measurement and control method described in this invention, the measurement and control terminal has the function of switching between preemptive working mode and normal working mode; In the normal operating mode, when there is a control command message to be sent and the telemetry and control terminal is receiving a data frame from the slave station, the telemetry and control terminal waits for the current data frame to be completely received before sending the control command message.

[0017] To solve the above-mentioned technical problems, the present invention also provides the following technical solution: a remote measurement and control system, comprising a measurement and control terminal and a slave station, wherein the measurement and control terminal and the slave station are connected via a bus communication connection; The measurement and control terminal includes: The preemptive scheduling strategy selection module is used to select whether to start executing the aforementioned priority control strategy. In response to the existence of control command messages to be sent, it performs a bus status determination. If the bus is currently in the state of the measurement and control terminal receiving data frames, i.e., the slave station is occupying the bus to send data, it further determines whether to enable the preemptive scheduling strategy. If the preemptive scheduling strategy is enabled, it enters the priority preemption process. An interrupt signal injection module is used to actively inject an interrupt signal into the bus when it is determined that the measurement and control terminal is receiving a data frame from the slave station; the signal form of the interrupt signal is incompatible with the frame format protocol of the data frame, causing the slave station to trigger a hardware interrupt through a physical layer bus conflict and terminate the transmission of the current data frame; The control command sending module is used to send the control command message to the bus after the interruption signal is sent. The recovery query sending module is used to respond to the slave station receiving the control command message, send a monitoring data query request to the bus, and prompt the slave station to resume uploading monitoring data.

[0018] The present invention provides a computer device, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the steps of the remote measurement and control method described above.

[0019] The present invention provides a computer-readable storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements the steps of the remote measurement and control method described above.

[0020] The beneficial effects of this invention are as follows: By actively injecting an interrupt signal incompatible with the data frame format protocol into the bus, this invention enables the slave station to immediately terminate the transmission of the current data frame upon detecting a bus signal conflict at the physical layer via hardware-triggered interruption. The control terminal can reclaim bus usage rights and issue control commands without waiting for the current frame to end. Compared to the traditional half-duplex communication method, which requires waiting for the complete data frame to end before sending control commands, this invention shortens the response delay of control commands from being determined by the data frame length to being determined solely by the length of the interrupt signal. This achieves deterministic and rapid response, effectively improving the dynamic response performance and system operational safety of the magnetically controlled flexible interconnect device in power scheduling and fault handling scenarios. At a baud rate of 115200bps, the control command response delay of this invention is approximately 200 microseconds, and is independent of the length of the monitored data frame; while the traditional half-duplex communication method requires waiting for the complete end of the current data frame before sending control commands, and at the same baud rate, the response delay is determined by the data frame length, typically more than 8 frames, approximately 800 microseconds or longer. The preemptive scheduling strategy of this invention reduces the response latency from 8 frames of data to about 2 frames, achieving deterministic microsecond-level real-time response. Attached Figure Description

[0021] To more clearly illustrate the technical solutions of the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0022] Figure 1 This is a flowchart of a remote measurement and control method provided in one embodiment of the present invention.

[0023] Figure 2 This is a schematic diagram of the structure of a magnetically controlled flexible interconnection device and a remote measurement and control terminal system provided in one embodiment of the present invention.

[0024] Figure 3 This is a schematic diagram of a magnetic control circuit topology provided in one embodiment of the present invention.

[0025] Figure 4 This is a schematic diagram of the architecture of a measurement and control terminal and storage medium provided in one embodiment of the present invention.

[0026] Figure 5 The timing diagram of a preemptive priority scheduling strategy provided in an embodiment of the present invention is shown.

[0027] Figure 6 A flowchart of a physical layer preemption mechanism provided in one embodiment of the present invention.

[0028] Figure 7 This is a schematic diagram of the physical layer preemption sequence frame structure provided in one embodiment of the present invention.

[0029] Figure 8 A flowchart illustrating a priority backup mechanism provided in one embodiment of the present invention.

[0030] Figure 9 A flowchart illustrating the priority release and task recovery mechanism provided in one embodiment of the present invention.

[0031] Figure 10 This is a schematic diagram of the human-machine interface of a measurement and control terminal provided in one embodiment of the present invention.

[0032] Figure 11 This is a schematic diagram of the measurement and control terminal provided in one embodiment of the present invention.

[0033] Figure 12 A schematic diagram comparing the response time of a preemptive priority scheduling strategy with that of a traditional half-duplex communication method, provided in an embodiment of the present invention. Detailed Implementation

[0034] To enable those skilled in the art to better understand the present invention, specific embodiments of the present invention are described in detail below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of the present invention, and not all of them. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without inventive effort should fall within the protection scope of the present invention.

[0035] Example 1, referring to Figure 1 As one embodiment of the present invention, a remote monitoring and control method is provided, comprising: S1 performs a bus status determination in response to the presence of an emergency control command message to be sent.

[0036] If the current bus is in the state of receiving data frames by the measurement and control terminal, that is, the slave station occupies the bus to send data, then it is further determined whether to enable the preemptive scheduling strategy. If the preemptive scheduling strategy is enabled, the priority preemption process is entered.

[0037] S2, if the telemetry and control terminal is receiving a data frame from the slave station, the telemetry and control terminal actively injects an interrupt signal into the bus. The signal form of the interrupt signal is incompatible with the frame format protocol of the data frame, causing the slave station to trigger a hardware interrupt through a physical layer bus conflict and terminate the transmission of the current data frame.

[0038] When the bus is occupied by a monitoring data frame uploaded by a slave station, the monitoring and control terminal does not wait for the data frame to finish transmitting. Instead, during the reception of the monitoring data frame, it actively injects an interrupt signal with a specific form into the bus. The signal form of this interrupt signal is incompatible with the frame format protocol followed by the data frame. When this signal appears on the bus, since the slave station is still in the transmitting state and its receiver is also in the enabled state, there is a conflict between the actual level sampled by the slave station on the bus and the driving level it is outputting. This difference is detected by the slave station's communication hardware at the physical layer and immediately triggers a hardware interrupt, causing the slave station to terminate the transmission of the current data frame. The core function of this step is to enable the monitoring and control terminal to reclaim the right to use the bus without waiting for the current frame to end, thereby overcoming the inherent limitation of traditional half-duplex communication where control commands must wait for the current frame to end before obtaining the right to transmit the bus.

[0039] S3, after the interrupt signal is sent, send the control command message to the bus.

[0040] After the interrupt signal is sent and the slave station has terminated the current data frame transmission due to a hardware interruption, the bus is released from the state occupied by the monitored data frame. Within this time window, the measurement and control terminal sends a control command message to the bus to ensure that the control command can obtain the right to send the bus in the shortest possible time and be received by the slave station in a timely manner, thereby realizing a rapid response to the control command.

[0041] S4, in response to the slave station receiving the control command message, sends a monitoring data query request to the bus, prompting the slave station to resume uploading monitoring data.

[0042] After the control command message has been successfully received and confirmed by the slave station, the high-priority control communication task on the bus has been completed. At this time, the measurement and control terminal actively sends a monitoring data query request to the bus, triggering the slave station to re-upload the latest monitoring data frame, so that the system can be restored from the control mode to the normal monitoring mode, thereby ensuring the continuity and timeliness of the monitoring data and realizing the orderly switching and coordinated operation of the two functions of monitoring and control on the same half-duplex bus.

[0043] It should be noted that existing monitoring and control terminals in half-duplex bus communication generally adopt a processing method that waits for the current data frame to be completely received before sending control commands. Under this method, the response delay of the control command depends on the length of the currently transmitted monitoring data frame, which is usually several milliseconds to tens of milliseconds, and the delay time is uncertain under different frame lengths. When the distribution network experiences disturbances or faults, the magnetically controlled flexible interconnection device needs to complete the issuance of power dispatch commands or the switching of operating modes within several milliseconds. The uncertain delay under the traditional method will directly affect the dynamic adjustment performance of the flexible interconnection device and the operational safety of the system.

[0044] Therefore, to address the aforementioned problems, the present invention, through steps S1 to S4, addresses the issue when the monitoring and control terminal has a control command message to be sent. First, it determines whether a preemptive scheduling strategy is enabled. If so, and the current bus is occupied by a monitored data frame, the priority preemption process is initiated directly. The control terminal proactively injects an interrupt signal incompatible with the frame format protocol into the bus without waiting for the current frame to end. This causes the slave station to detect a bus signal conflict at the physical layer and immediately terminate the transmission of the current data frame via a hardware-triggered interrupt. The control terminal then quickly reclaims bus access and sends a control command message. After receiving confirmation from the slave station, it sends a monitoring data query request to resume monitoring data uploading. These steps together constitute a complete preemptive remote control process, reducing the response delay of control commands from depending on the data frame length to depending only on a fixed-length interrupt signal. This achieves deterministic and rapid response of control commands in half-duplex bus communication, effectively improving the dynamic response performance and system operational safety of the magnetically controlled flexible interconnect device in power scheduling and fault handling scenarios.

[0045] Example 2, refer to Figures 2 to 12 This is one embodiment of the present invention. Based on the previous embodiment, a remote measurement and control method is provided.

[0046] Reference Figure 2The remote monitoring and control system provided in this embodiment of the invention comprises two parts: a monitoring and control terminal and a magnetically controlled flexible interconnection device. The magnetically controlled flexible interconnection device is connected between transformer substation 1 and transformer substation 2, and consists of transformer 1, transformer 2, an auxiliary transformer, and a magnetic control circuit. The magnetic control circuit has data acquisition and action control functions, and works with the monitoring and control terminal for remote communication. The specific connection method of the magnetically controlled flexible interconnection device is as follows: the input end of transformer 1 is connected to transformer substation 1, and the output end of transformer 1 is connected to the auxiliary transformer and the magnetic control circuit; the magnetic control circuit is connected to both transformer 1 and the auxiliary transformer; and transformer 2 is connected to transformer substation 2. The magnetic control circuit performs data acquisition and action control on the magnetically controlled flexible interconnection device system. The auxiliary transformer performs secondary processing on the voltage after the main transformer's step-down voltage, and after active power flow regulation and reactive power compensation, transmits the voltage to the adjacent transformer substation through transformer 2. The monitoring and control terminal includes a CPU, a touch panel, a communication interface, and a memory. It has two operating modes: information display and touch control, and communicates bidirectionally with the magnetically controlled flexible interconnection device via an RS485 half-duplex bus.

[0047] Reference Figure 3 The magnetic control circuit uses an LCL-type input filter and an LC-type output filter, with a three-phase half-bridge IGBT (Insulated Gate Bipolar Transistor) topology in between. This topology uses fewer IGBT modules than the MMC (Modular Multilevel Converter), offering advantages in size and cost. After the main transformer performs initial voltage reduction on the distribution network, the magnetic control circuit detects the actual voltage and processes it again through an auxiliary transformer. Through active power flow regulation and reactive power compensation, it outputs a low-harmonic voltage that meets power quality requirements, which is then transmitted to adjacent distribution areas via transformer 2.

[0048] Reference Figure 4 The system architecture of the measurement and control terminal includes a CPU, a touch panel, a communication interface, and a memory, corresponding to the three main tasks of touch control, communication, and storage. The CPU, as the core processor, is responsible for allocating task processes and scheduling resources, coordinating the processing needs of touch control, communication, and storage tasks. For touch control tasks, the CPU recognizes touch instructions and converts them into executable code. For communication tasks, the CPU receives, parses, and packages data for transmission. For storage tasks, the CPU performs memory address addressing and switches between read and write operations. The touch panel is used to determine the operator's touch area, identify the corresponding register address, and respond to the operation by modifying the address variable value. The communication interface is the electrical interface for information transmission between the measurement and control terminal and the magnetically controlled flexible interconnection device, serving as the hardware foundation for bidirectional communication. The memory is used for temporary storage or data retention when power is off.

[0049] Reference Figure 5 During normal monitoring, the slave station periodically sends monitoring data frames to the bus. When the control terminal detects a touch command, it immediately sends a physical layer preemption sequence to the bus, actively driving a level conflict. When the slave station receiver samples a level difference between the synthesized bus level and its own driving level, a frame error interrupt is triggered, pausing the current frame transmission and clearing the transmission buffer. Bus usage rights are then transferred from the slave station to the control terminal. The conflict duration is less than 100 microseconds and has no impact on device performance. After successful preemption, the control terminal sends a control command message, and the slave station switches to control command receiving mode to respond, entering the normal control phase. After the control command is executed, the control terminal releases priority and sends a query request. The slave station resumes uploading monitoring data, and the system returns to the normal monitoring phase.

[0050] Reference Figure 10 The human-machine interface of the monitoring and control terminal is divided into a main interface, a parameter command interface, and a data curve interface. Page selection buttons are located at the bottom of the display page, and all buttons are visible to all pages, allowing for easy switching between any two pages. These buttons include labels such as "Main Interface," "Parameter Commands," and "Data Curves," and are visible to all pages, enabling operators to switch between pages without returning to the previous menu. When switching pages, the monitoring and control terminal automatically saves the current page's display state and restores it upon returning. The main interface displays an overview of the magnetically controlled flexible interconnect device, including system overview, system control, and hierarchy selection functions. The system overview displays the current circuit structure and key information, including the low-voltage side voltage and the magnitude of the magnetic control power. System control is used to manage the operation of the magnetically controlled flexible interconnect device, allowing for start-up or shutdown, and adjustment of active and reactive power. Hierarchical selection is used to switch the content displayed on the overview page, allowing users to view detailed operational information for specific modules. The parameter command interface enables control functions, including system start / stop control, operating mode switching, control parameter modification, program debugging and verification, and fault status clearing. The data curve interface enables monitoring functions, displaying real-time curves of the low-voltage side voltage and current of transformers 1 and 2, temperature information at each measurement node, input and output voltage and current of the magnetic control circuit, and fault information. The temperature information includes the real-time temperature of the transformer's magnetic body and the switching devices of the magnetic control circuit.

[0051] Reference Figure 11The measurement and control terminal has two main functions: monitoring and control. The monitoring function is used to monitor the status of the magnetically controlled flexible interconnection device, including: monitoring the low-voltage side voltage and current of transformer 1 and transformer 2; temperature monitoring of each measurement node in the system, covering the temperature of the transformer's magnetic body and the switching devices of the magnetic control circuit; monitoring the input and output voltage and current of the magnetic control circuit; and monitoring system fault information. The above monitoring data is uploaded from the slave station to the measurement and control terminal via a half-duplex bus, and after parsing, is displayed as a real-time curve on the data curve interface.

[0052] The control functions are used to control the operation of the magnetically controlled flexible interconnect device, including the following specific functions: system start / stop control; switching of operating modes; modification of control parameters; debugging and verification of programs; and clearing of fault states. These control functions are centrally displayed in the parameter command interface, and operators trigger the issuance of control commands by touching the corresponding buttons.

[0053] S1 performs a bus status determination in response to the presence of an emergency control command message to be sent.

[0054] The measurement and control terminal and the magnetically controlled flexible interconnection device are connected via an RS485 half-duplex bus. The measurement and control terminal acts as the master station, and the magnetically controlled flexible interconnection device acts as the slave station. Communication is initiated only by the measurement and control terminal, with the slave station passively responding to communication requests. The measurement and control terminal maintains a queue of commands to be sent. When the CPU receives a control task triggered by a touch operation from the touch panel, it generates a corresponding control command message and stores it in this queue. During any communication cycle, the measurement and control terminal first checks whether there is a control command message to be sent in this queue.

[0055] If the current bus is in the state of receiving data frames by the measurement and control terminal, that is, the slave station occupies the bus to send data, then it is further determined whether to enable the preemptive scheduling strategy. If the preemptive scheduling strategy is enabled, the priority preemption process is entered.

[0056] S1 includes S11 to S14.

[0057] S11, the telemetry and control terminal reads the status flag bit of its UART (Universal Asynchronous Receiver / Transmitter) receive buffer to determine whether it is currently receiving data frames from the slave station.

[0058] During normal monitoring, the magnetically controlled flexible interconnect device continuously uploads monitoring data frames to the monitoring and control terminal according to a predetermined upload cycle. The UART receiver of the monitoring and control terminal is enabled and continuously listens for differential signals on the bus. When the slave station starts sending a data frame, the UART hardware of the monitoring and control terminal detects the start bit and begins receiving data bit by bit, setting the receive status flag. The CPU of the monitoring and control terminal can determine whether it is currently receiving a data frame from the slave station by querying this receive status flag.

[0059] S12, if it is determined that no data frame is being received at present, that is, the bus is in an idle state, the measurement and control terminal executes the standard transmission procedure: directly encapsulates the control command message according to the predetermined communication request message format, enables the driver, and sends the message to the bus.

[0060] Reference Figure 8 When the bus is idle or the slave station is not in a receiving state, no preemption process is required. The control terminal encapsulates the control command into a control message according to the predetermined communication request message format and sends it directly; the slave station replies with a corresponding acknowledgment frame upon receiving it. If the control terminal sends a query message, the slave station responds with a data reply message. The priority backup mechanism ensures the normal operation of the communication process when the bus is idle.

[0061] S13, if a data frame is currently being received from a slave station, the telemetry and control terminal further obtains the frame length information of the current data frame in order to assess the time required to wait for the frame to end.

[0062] In one implementation, the telemetry and control terminal obtains the frame length information by parsing the length field in the frame header of the currently received data frame. The monitoring data frames uploaded by the magnetically controlled flexible interconnect device follow a predetermined message format, and the frame header contains a field indicating the length of subsequent data. The telemetry and control terminal can parse this field during reception to determine the total length of the current frame, thereby calculating the remaining time required from the current moment until the end of the frame transmission.

[0063] In another implementation, the telemetry and control terminal does not need to parse the frame length information; instead, it directly triggers the preemption process based on the bus status determination result. In this implementation, the telemetry and control terminal does not calculate the waiting time but directly uses the determination result as the basis for whether to execute preemption—as soon as it determines that a data frame is currently being received, it immediately enters the preemption transmission process. This method reduces the processing overhead of frame header parsing and further shortens the response delay from the occurrence of a touch to the triggering of preemption.

[0064] S14, the telemetry and control terminal decides whether to execute the preemptive transmission process based on the frame length information obtained in S13 or directly based on the bus status determination result.

[0065] In one implementation, the control terminal compares the remaining time calculated in S13 with a preset response delay threshold. If the remaining time is less than or equal to the threshold, the control command is sent after the current frame ends; if the remaining time is greater than the threshold, a preemptive transmission process is triggered. The value of the threshold can be set according to the actual requirements of the magnetically controlled flexible interconnect device for the response time of the control command, for example, it can be set to 2 milliseconds. This method avoids unnecessary bus preemption operations as much as possible without excessively affecting the real-time response of the control command, reduces data retransmission caused by frame error interruption, and thus improves the overall efficiency of bus communication.

[0066] In another implementation, the telemetry and control terminal does not perform threshold comparisons. It directly triggers the preemptive transmission process as soon as it determines that it is currently receiving data frames and that there are control command messages to be sent. This method minimizes the response delay of control commands, making it suitable for fault handling scenarios with extremely high real-time requirements.

[0067] The aforementioned bus status determination process is directly related to the user's operation. When an operator performs touch operations on the touch panel of the measurement and control terminal, the touch panel first determines the operator's touch area and identifies the corresponding internal register address. When the operator touches control function buttons such as "System Start / Stop Control," "Operating Mode Switching," "Control Parameter Modification," or "Clear Fault Status," the touch panel responds by modifying the corresponding address variable value. The CPU detects this change in address variable and generates a corresponding control command message, storing it in the pending queue. During this process, the touch panel simultaneously provides visual feedback—the touched button changes color or is highlighted to inform the operator that their touch operation has been recognized by the system. Meanwhile, the human-machine interface of the measurement and control terminal maintains normal page rendering and data display across the main interface, parameter command interface, and data curve interface, and the scheduling of underlying communication tasks remains transparent to the user. The operator does not need to understand the specific logic of the bus determination; they only need to operate on the touch panel, and the system automatically completes the bus status determination and decides whether to execute the preemption process.

[0068] Compared to the traditional half-duplex communication method of blindly waiting for the current frame to end before attempting to send, the preemptive scheduling strategy of this invention enables the telemetry and control terminal to actively interrupt the data frame being transmitted. Moreover, by obtaining the frame length information of the current data frame and comparing it with a preset threshold, the telemetry and control terminal can switch between real-time response and communication efficiency—in case of emergency control needs, preemption is triggered immediately, while in non-emergency scenarios, the complete transmission of monitoring data frames is prioritized, thus balancing the real-time performance of the system and data integrity.

[0069] S2, if the telemetry and control terminal is receiving a data frame from the slave station, the telemetry and control terminal actively injects an interrupt signal into the bus. The signal form of the interrupt signal is incompatible with the frame format protocol of the data frame, causing the slave station to trigger a hardware interrupt through a physical layer bus conflict and terminate the transmission of the current data frame.

[0070] After the telemetry and control terminal decides to execute the preemptive transmission process, it immediately initiates the physical layer interruption signal injection process without waiting for the current monitoring data frame to be transmitted completely. This process involves physical layer signaling interaction between the telemetry and control terminal and the slave station, namely the magnetically controlled flexible interconnect device, as well as the hardware interrupt response and state switching within the slave station.

[0071] S2 includes S21 to S27.

[0072] Reference Figure 6 The overall process of the physical layer preemption mechanism is as follows: After detecting a touch command, the monitoring and control terminal first determines whether a preemptive scheduling strategy is enabled. If the preemptive scheduling strategy is enabled, and the current bus is occupied by a monitored data frame, it directly enters the priority preemption process and immediately sends a physical layer preemption sequence (i.e., priority interrupt sequence + interrupt signature code) to the bus through the communication interface. Upon recognizing this sequence, the slave receiving end generates a frame error interrupt, suspends the transmission of the current monitored data frame, clears the transmission buffer, and releases the bus. The monitoring and control terminal then sends a control command message, and the slave responds to the command by executing the corresponding control function.

[0073] S21, the measurement and control terminal constructs and sends the physical layer preemption sequence to the bus.

[0074] The CPU of the measurement and control terminal, based on the control commands generated by the touch operation, calls the pre-set preemption sequence template in the memory and constructs the physical layer preemption sequence bit by bit. (Refer to...) Figure 6 As shown, the physical layer preemption sequence consists of two frames, comprising a 10-bit "priority interrupt sequence" in the front and an 8-bit "interrupt signature" in the back.

[0075] Reference Figure 7 The physical layer preemption sequence consists of two frames, comprising a 10-bit priority interrupt sequence and an 8-bit interrupt signature. The priority interrupt sequence is 0101010100 (high-low level), with the baud rate consistent with normal communication. However, its stop bit level violates the standard asynchronous serial communication protocol's requirement that the stop bit must be high. The interrupt signature is 0xAA (binary 10101010), used by the receiver to identify legitimate preemption events. In this embodiment, each frame of asynchronous serial communication has the following data format: 1 start bit (low level), 8 data bits (LSB priority), and 1 stop bit (high level), with a frame length of 10 bits. The receiver hardware identifies the start of the data frame by detecting the falling edge of the start bit (transitioning from high to low level) and recovers the data bytes bit by bit at the predetermined baud rate.

[0076] In one implementation, the monitoring and control terminal, with its UART driver enabled, continuously outputs the 18-bit level sequence to the RS485 differential bus via the TXD pin. The 10-bit priority interrupt sequence is output according to a set high-low level, with the baud rate consistent with normal communication, for example, 115200bps. The stop bit of this set level sequence is forcibly set to low, intentionally violating the asynchronous serial communication protocol's stop bit level requirement—in the standard UART protocol, the receiver expects a high-level stop bit. Because the end level of this sequence is low, and the subsequent levels jump continuously within a short time, the level change pattern and duration do not conform to the normal data frame start frame format, nor to the occasional random error frame format on the line.

[0077] In another implementation, if the slave station is not currently in a transmitting state (i.e., the bus is idle but the control terminal still needs to force confirmation of control), the control terminal can also output the two-frame preemption sequence. This sequence appears as a non-standard frame level signal on the idle bus. Although the slave station will not cause a bus conflict after detection, it can still enter the receive standby state by triggering a frame error and identifying the subsequent interrupt feature code. This implementation ensures a unified processing logic for the preemption sequence under different bus states.

[0078] S22, during the transmission of data frames by the slave station, its transceiver driver and receiver are simultaneously enabled to achieve real-time comparison between the transmitted level and the actual bus level.

[0079] Before and during step S21, the communication transceiver of the magnetically controlled flexible interconnect device is configured to a special operating mode: during data frame transmission, not only is the driver enabled to drive the bus to output its own data, but the receiver is also synchronously enabled. Therefore, while the slave station transmits the drive level of the monitoring data frame bit by bit, its receiver continuously samples the actual differential level on the RS485 differential bus and performs a real-time bit comparison between the sampled actual frame level and its own currently output drive level.

[0080] This configuration provides the hardware foundation for real-time detection of physical layer bus collisions in this invention. Slave stations do not require additional dedicated collision detection chips; they can perform level comparison using only the inherent receive channel of the RS485 transceiver, thus reducing system hardware costs.

[0081] S23, the level output by the measurement and control terminal and the level driven by the slave station are superimposed on the bus, causing a physical layer bus conflict.

[0082] When the monitoring and control terminal outputs two preemption sequences to the RS485 differential bus via its driver in S21, since the slave station has not yet detected the anomaly and continues to send the current monitoring data frame, the bus simultaneously carries two drive signals: one is the drive level of the current data frame being output by the slave station, and the other is the preemption sequence level output by the monitoring and control terminal. Because the RS485 bus is a differential half-duplex shared medium, when the output levels of multiple drivers are opposite, the actual differential signal on the bus is the electrical superposition of the two drive levels, forming a composite level.

[0083] For example, when the slave station outputs a logic high level while the control terminal simultaneously outputs a logic low level, the synthesized level on the bus no longer appears as a single standard differential high or low level, but rather as an intermediate state or an inverted level. After sampling this synthesized level, the slave station's receiver compares it with its own currently output drive level. Because there is a significant difference between the synthesized level and its own drive level, the slave station determines that a level conflict has occurred on the bus. This conflict determination occurs at the sampling time of the stop bit, therefore the detection delay is only one frame time, approximately 100 microseconds at a baud rate of 115200bps, exhibiting extremely high response speed.

[0084] S24, the slave communication hardware generates a frame error interrupt because it cannot recognize a valid stop bit.

[0085] After a bus collision occurs, the slave station's UART communication hardware continues to sample the bus level bit by bit according to the frame format of the standard asynchronous serial communication protocol in order to identify the valid start bit of the next frame. Because the stop bit level of the priority interrupt sequence injected by the telemetry and control terminal violates the standard UART protocol's requirement that the stop bit must be high, the slave station's UART hardware cannot identify a valid stop bit during the bit-by-bit sampling process, thus triggering a hardware-level frame error interrupt.

[0086] It should be noted that this frame error interrupt is generated directly at the UART hardware level, without relying on the slave station's software polling or protocol stack parsing, thus the interrupt response delay is extremely small. Furthermore, since this frame error interrupt is triggered by a specific signal actively injected by the telemetry and control terminal, rather than by line noise or interference, it is deterministic and repeatable.

[0087] S25: Read the interrupt signature code from the frame error interrupt service routine to identify a legitimate preemption event.

[0088] The slave station's CPU responds to the frame error interrupt triggered in S24 and enters the corresponding interrupt service routine. In this interrupt service routine, the slave station does not immediately terminate the transmission of the current data frame, but first reads the data buffered in the UART receive register. Since the telemetry and control terminal immediately sends an 8-bit interrupt signature after the 10-bit priority interrupt sequence, the slave station's receiver has already latched this 8-bit data into the receive buffer while sampling the collision level.

[0089] The slave station reads the 8-bit data as an interrupt signature and compares it with a preset signature. In this embodiment, the preset signature is the hexadecimal number 0xAA, i.e., the bit pattern is 10101010. If the read interrupt signature matches 0xAA, the slave station determines that the current frame error interruption is not caused by occasional line interference, but rather by a legitimate priority preemption event initiated by the telemetry and control terminal.

[0090] This feature code comparison mechanism enables the slave station to accurately distinguish between priority preemption initiated by the telemetry and control terminal and occasional interference or bit errors on the communication line. Only after recognizing the preset feature code will the slave station execute the subsequent termination transmission operation, avoiding invalid interruptions and data retransmissions caused by misjudgment of non-preemption triggering conditions such as lightning strike induced noise and electrostatic discharge, thereby improving the system's anti-interference capability and communication reliability.

[0091] If the interrupt signature read is inconsistent with 0xAA, the slave station handles the error according to the normal frame error handling procedure—discarding the current erroneous frame and recording the error count, but not terminating the transmission of data frames, and continuing to complete the transmission of the remaining bits and subsequent data frames. This mechanism ensures that the preemption mechanism is only triggered when the telemetry and control terminal actually issues a control command, guaranteeing that the continuity of normal monitoring data upload is not affected by meaningless interruptions.

[0092] S26, the slave station terminates the transmission of the current data frame, clears the transmission buffer, and switches to the control command receiving state.

[0093] After identifying the valid interrupt signature 0xAA in S25, the slave station immediately performs the following operations: S251: The slave station's CPU sends a stop instruction to the UART control register, terminating the continued transmission of the current monitoring data frame. After the transmission operation is terminated, the slave station's driver releases its occupancy of the RS485 bus, and the bus usage right is released.

[0094] S252: The slave station clears any remaining data in the transmit buffer of the current data frame that has not yet been fully transmitted, and discards the interrupted monitoring data frame. Because the interrupted data frame was not fully transmitted, it will be re-requested for upload by the telemetry and control terminal during the subsequent recovery phase.

[0095] S253, the slave station keeps the UART receiver enabled and switches its own communication status from "monitoring data transmission status" to "control command reception status" in preparation to receive the control command message that the telemetry and control terminal is about to send.

[0096] After the slave station completes the above state switch, the bus is released from the state occupied by the monitored data frame, and the measurement and control terminal can send control command messages to the bus within a very short time window.

[0097] S27, the telemetry and control terminal immediately sends a control command message after the interruption signal is sent.

[0098] After the telemetry and control terminal completes the transmission of the 18-bit preemption sequence in S21, it then passes through a 4-bit squelch window to ensure that the slave station has completed the interrupt response and state transition, and subsequently sends a complete control command message to the bus via the UART driver. This message follows... Figure 9 The communication message format of the control and measurement terminal shown includes fields such as slave address, function code, data field, and checksum. At this time, the slave station is in the control command receiving state, and its UART receiver is sampling the bus level normally, receiving the complete control command message, and parsing and executing the control operations contained therein.

[0099] It should be noted that the delay in the entire S2 process, from the occurrence of touch to the start of control command transmission, only includes the transmission time of the 18-bit priority interrupt sequence plus the 4-bit squelch window time, totaling 22 bits, or approximately 3 bytes of transmission time. This delay is independent of the length of the currently transmitted monitoring data frame. At a baud rate of 115200bps, each bit takes approximately 8.7 microseconds, for a total of approximately 190 microseconds. Considering the additional overhead of the UART start and stop bits, the actual delay is approximately 200 microseconds. Compared to existing half-duplex communication methods that require waiting for the current data frame to end (typically 8 bytes or more, requiring at least 800 microseconds at the same baud rate), this invention reduces the control command response delay to less than a quarter of the original method. Furthermore, the delay time is deterministic and does not change with the length of the monitoring data frame, thus ensuring the timely issuance of control commands by the magnetically controlled flexible interconnect device in power scheduling and fault handling scenarios.

[0100] When an operator clicks a function button such as "System Start" or "Working Mode Switch" on the touch panel of the control terminal, the terminal responds within microseconds, and the slave station immediately performs the corresponding power scheduling or mode switching action. The corresponding button on the touch panel displays a pressed animation upon touch triggering and updates its operating status after the slave station successfully executes the control command, providing the operator with intuitive closed-loop operational feedback. The operator does not need to know the details of underlying bus conflict detection and frame error interruption handling; what they perceive is the terminal's instantaneous response to touch operations and seamless switching of equipment status.

[0101] By actively injecting an interrupt signal incompatible with the data frame format protocol at the physical layer, and utilizing the hardware configuration of simultaneous driver and receiver enable during slave transceiver transmission, along with real-time comparison of bus level conflicts, the slave can respond to preemption events extremely quickly via hardware interrupts without relying on software protocol stack polling. Compared to the traditional half-duplex communication method where bus usage rights can only be acquired through software scheduling after the current frame ends, this invention directly triggers the transfer of bus usage rights at the physical layer. This shortens the control command waiting time from being determined by the data frame length to depending solely on a fixed-length preemption sequence, achieving deterministic microsecond-level real-time response. Simultaneously, the interrupt signature code feature comparison mechanism effectively eliminates false triggers caused by line interference, balancing response speed and communication reliability. Furthermore, step S2 utilizes the slave's operation of clearing the transmit buffer and switching to the control command receiving state, preparing a clean communication environment for the next stage of control command transmission and seamless transition.

[0102] Furthermore, as an alternative implementation of step S2, the telemetry and control terminal described in this invention also supports a "normal operating mode" configuration. In this normal operating mode, the physical layer preemption function of the telemetry and control terminal is disabled, and it reverts to the software priority scheduling method.

[0103] Specifically, the telemetry and control terminal has a function to switch between preemptive and normal operating modes. When there is a control command message to be sent and the telemetry and control terminal is receiving a data frame from a slave station, the telemetry and control terminal does not activate the physical layer preemption process, but waits for the current data frame to be completely received before sending the control command message to the bus. This normal mode is switched through the system configuration menu of the telemetry and control terminal. The operator can find the "Communication Scheduling Mode" option on the "Parameter Settings" page of the touch panel and switch modes by checking or unchecking the "Enable Priority Preemption" checkbox. When "Enable Priority Preemption" is checked, the telemetry and control terminal executes the physical layer preemption process in step S2 above; when this option is unchecked, the telemetry and control terminal reverts to the normal mode, does not inject an interrupt signal, and waits for the current data frame to be completely received before sending the control command. This implementation ensures that the measurement and control terminal of the present invention can interoperate with traditional standard equipment that does not support interrupt sequence recognition and frame error interrupt handling on the same bus. While maintaining compatibility with existing equipment, it provides high-performance preemptive scheduling capabilities for new systems or scenarios with high real-time requirements, thereby enhancing the applicability and deployment flexibility of the present invention.

[0104] S3, after the interrupt signal is sent, send the control command message to the bus.

[0105] In step S2, the slave station has completed the termination of the current monitoring data frame transmission and switched to the control command reception state, and the bus usage right has been released. After the preemption sequence is completed and the noise window has passed, the telemetry and control terminal immediately executes the transmission operation of the control command message. This step involves the construction and encapsulation of the message on the telemetry and control terminal side, the control of the physical layer transmission timing, and the complete reception and verification of the message on the slave station side.

[0106] S3 includes S31 to S35.

[0107] S31, the telemetry and control terminal encapsulates control command messages. Referring to Table 1, the telemetry and control terminal and the magnetically controlled flexible interconnection device follow a unified data transmission rate and verification method; the message format is transparent to both parties. The communication message frame format is shown in Table 1: Table 1: Schematic diagram of communication message format for telemetry and control terminals

[0108] The CPU of the monitoring and control terminal, based on the type of control task triggered by the operator's touch operation, ... Figure 9 The control command message format shown is used to construct the communication message format of the telemetry and control terminal. This message format includes the following fields: a 1-byte slave address field, used to identify the target slave—the magnetically controlled flexible interconnect device has a unique slave number, ensuring one-to-one communication between the telemetry and control terminal and the slave; a 1-byte function code field, used to distinguish different control operation types, such as system start, system stop, working mode switching, control parameter modification, debugging and verification program functions, clearing fault status, etc.; a variable-length data field, used to carry parameter information for specific control operations, such as the target mode number when switching working modes, the parameter address and modified value when modifying control parameters, and the verification command sequence when debugging and verifying; and a 2-byte checksum field, using CRC16 cyclic redundancy check, used to ensure the integrity of the message during transmission.

[0109] In one implementation, if the currently triggered control task is system start / stop control, the data field contains only a one-byte start / stop flag, where 0x01 indicates start and 0x00 indicates stop, and the function code field is set to 0x10 accordingly. If the currently triggered control task is working mode switching, the data field further contains a one-byte mode number subfield and a one-byte mode switching confirmation code subfield, and the function code field is set to 0x11 accordingly. If the currently triggered control task is control parameter modification, the data field contains a two-byte parameter address, a two-byte parameter value, and a one-byte parameter modification enable code, and the function code field is set to 0x12 accordingly. The function codes and data structures corresponding to different control tasks are pre-stored in the memory of the measurement and control terminal, and the CPU obtains the corresponding message format template by looking up the register address mapping table of the touch operation.

[0110] The measurement and control terminal combines the above fields in sequence into a complete control command message, and temporarily stores it in the UART transmit buffer, waiting for the bus to be in a transmittable state before outputting it.

[0111] S32, the measurement and control terminal enables the driver and sends control command messages byte by byte to the RS485 differential bus.

[0112] After the preemption sequence is sent in step S2, the driver of the telemetry and control terminal has been enabled during the preemption sequence transmission and remains so. The CPU of the telemetry and control terminal controls the UART controller to read the control command message byte by byte from the transmit buffer, and outputs it to the RS485 driver through the TXD pin according to the frame format of the standard asynchronous serial communication protocol (each byte contains a low-level start bit, 8 LSB-preferred data bits, and a high-level stop bit (at a predetermined baud rate)). The driver converts the TTL level to an RS485 differential level signal to drive the bus.

[0113] During transmission, the UART hardware of the telemetry and control terminal automatically handles the insertion of start, stop, and parity bits. The CPU only needs to write the original data bytes into the UART transmit holding register, and the UART controller automatically completes the serialized transmission. No additional frame interval or waiting time is set between adjacent bytes, and the complete control command message is sent in the form of a continuous byte stream to shorten the transmission time of control commands.

[0114] S33, the slave station fully receives the control command message in the control command receiving state.

[0115] In step S26, the slave station has switched to the control command receiving state, and its UART receiver remains enabled and continuously listens for level changes on the RS485 differential bus. When the telemetry and control terminal starts sending control command messages, the slave station's UART hardware detects the start bit and begins bit-by-bit sampling and reception.

[0116] The slave station's UART receiver samples each bit at the same baud rate and frame format as the transmitter, restores the serial level to parallel data bytes, and sequentially receives the slave address, function code, data field, and checksum fields in the message. The received data is then stored byte by byte in the slave station's UART receive buffer.

[0117] S34, the slave station performs integrity verification and address matching on the received control command message.

[0118] After receiving the entire control command message, the slave station performs the following verification operation: In step S341, the slave station reads the received slave address field and compares it with its own pre-defined unique slave number. If the addresses match, further processing continues; if the addresses do not match, the message is ignored and no operation is performed. This address matching mechanism ensures that in a multi-slave bus topology, control commands are only responded to by the target slave station, avoiding erroneous operations on other slave stations.

[0119] S342, the slave station recalculates the CRC checksum value for the received slave station address field, function code field, and data field according to the CRC16 checksum algorithm agreed upon with the telemetry and control terminal, and compares the calculated result with the received checksum field. If they match, it is determined that no bit errors occurred during the transmission of the message, and the integrity check passes; if they do not match, it is determined that a transmission error occurred in the message, the slave station discards the message, does not perform any control operations, and simultaneously returns an error response frame to the telemetry and control terminal via the bus. The error response frame contains an error code field indicating the type of checksum error.

[0120] In one implementation, after the slave station passes the integrity verification, it returns an acknowledgment frame to the telemetry and control terminal. This acknowledgment frame contains the same function code and slave address as the issued command, and sets the most significant bit of the data field to inform the telemetry and control terminal that the control command has been successfully received. Upon receiving this acknowledgment frame, the telemetry and control terminal determines that the preemptive control command issuance has been successfully completed.

[0121] In another implementation, to minimize the total delay from the issuance of a control command to its execution, the slave station does not return a separate acknowledgment frame. Instead, in the next monitoring data upload cycle after the control operation is completed, the execution result status word of the control command is uploaded to the monitoring and control terminal along with the monitoring data. This implementation eliminates the transmission time of the acknowledgment frame, further shortening the total time of the preemption process, and is suitable for scenarios requiring rapid fault isolation or emergency power scheduling with extremely strict real-time requirements. In this implementation, operators confirm whether the command has been executed by observing changes in relevant operating status parameters on the human-machine interface of the monitoring and control terminal—if the parameters change within the expected time, it means the control command was executed successfully; if the parameters do not change and the system does not return an abnormal alarm, operators can determine that the command execution failed and reissue it as appropriate.

[0122] S35. After receiving the confirmation response, the control terminal determines that the control command was successfully issued.

[0123] After sending the control command message, the telemetry and control terminal starts a short timer to wait for the slave station's acknowledgment. If the acknowledgment frame described in S34 is received before the timer expires, the control command is considered successfully issued, and the execution log, including the operation time, operation type, and operator identification, is recorded in the historical record area of ​​the memory for subsequent traceability and auditing. If no acknowledgment frame is received after the timer expires, the telemetry and control terminal determines that the control command issuance may have failed due to bus interference or slave station malfunction, records this failure event in the fault status register, and decides whether to automatically retry once depending on the strategy.

[0124] It should be noted that the above-mentioned confirmation and response mechanism is an optional, non-essential step in this invention. In the embodiment without confirmation and response, the telemetry and control terminal considers the control command to have been issued after sending the control command message and no longer waits for confirmation and response, thereby compressing the total time of the preemption process to the shortest possible duration—only the physical layer preemption sequence sending time plus the control command message sending time, with no additional waiting overhead.

[0125] After an operator performs a touch operation on the touch panel, the corresponding control button on the HMI (Human Machine Interface) of the control terminal immediately displays a pressed animation upon touch triggering. Subsequently, after the control command message is sent and the slave station successfully executes the control operation, the data display area related to the current control operation on the HMI is updated accordingly. For example, when an operator clicks the "Start" button on the main interface, the "Running Status" indicator on the main interface switches from the red "Stop" state to the green "Running" state. At the same time, the active power and reactive power values ​​in the system overview area begin to update in real time, reflecting that the magnetically controlled flexible interconnect device has entered normal operation. When an operator modifies the MHT voltage regulation range parameter on the parameter command interface and clicks "Confirm," the corresponding parameter display box on the parameter command interface updates to the modified value, and the voltage monitoring data on the main interface is adjusted according to the new voltage regulation range. All of the above interface feedback processes occur within a few hundred milliseconds, and the operator receives visual confirmation almost immediately after the touch operation, forming a complete closed-loop interactive experience of "touch triggering—bus preemption—command execution—interface feedback."

[0126] Step S3, building upon the successful reclaiming of bus usage rights and the switch from slave to receiving state in step S2, reliably delivers control commands through a clearly defined message format, function code mapping, and CRC integrity verification mechanism. Compared to traditional half-duplex communication where control commands must wait for the current data frame to end before being sent and still require a slave response to confirm the execution result after transmission, the control command message of this invention is sent within the first transmission window after bus release. The slave receives and verifies the message via UART hardware interrupt, further compressing the total delay from triggering to execution confirmation of the control command to a fixed value equal to the physical layer preemption sequence length plus the control command message length. This delay is unaffected by the monitored data frame length, exhibiting determinism and predictability. Simultaneously, through unique slave address matching and a dual-core CRC16 mechanism, instruction crosstalk and transmission errors in multi-slave topologies are effectively avoided, improving the reliability of control commands and the security of system operation. The confirmation response mechanism or status word transmission mechanism provides a positive confirmation channel for the measurement and control terminal to confirm the execution result, enabling the system to promptly detect and take remedial measures such as retry or alarm when the instruction execution fails, further enhancing the robustness of the system.

[0127] S4, in response to the slave station receiving the control command message, sends a monitoring data query request to the bus, prompting the slave station to resume uploading monitoring data.

[0128] After the control command message has been successfully received and executed by the slave station, the high-priority control communication task on the bus is complete. The system needs to return from control mode to normal monitoring mode to ensure the continuity and timeliness of monitoring data. This step involves the complete interactive process of the control terminal releasing priority, constructing and sending monitoring data query requests, and the slave station restarting monitoring data upload. This step also covers the exception handling mechanism in the event of a preemption failure.

[0129] S4 includes S41 to S46.

[0130] Reference Figure 9 After the preemptive interrupt control command is sent and confirmed by the slave station, the preemption of the current priority is successfully completed. The telemetry and control terminal then releases the priority and sends a query request message; upon receiving the query request, the slave station resumes uploading monitoring data. The interrupted monitoring data frame is discarded due to a frame error, and the slave station retransmits the latest data in the next upload cycle to ensure data consistency. If the telemetry and control terminal does not receive the expected response after sending the priority interrupt sequence, the system automatically retryes once and records the fault status to avoid malfunctions caused by interference.

[0131] S41, the telemetry and control terminal receives the confirmation response from the slave station and determines that the control command has been executed.

[0132] Based on S34 or S35, the telemetry and control terminal confirms that the slave station has successfully received and executed the control command. The method of obtaining this confirmation depends on the specific implementation method selected in S34: In the acknowledgment response mode, after sending the control command message, the telemetry and control terminal starts a short timer, waiting for an acknowledgment response frame from the slave station. Upon receiving the acknowledgment response frame, the telemetry and control terminal parses the function code response flag, confirming that the control command has been executed by the slave station. This method provides a clear two-phase handshake mechanism, enabling the telemetry and control terminal to accurately determine whether the slave station has entered the control command execution completion state, thereby accurately determining when it is safe to release priority and transition to the monitoring and recovery process.

[0133] In the status word follow-up mode, the telemetry and control terminal does not wait for a separate acknowledgment frame; instead, it directly enters the monitoring recovery process after sending the control command message. After the slave station completes the control operation, it embeds the execution result status word into the monitoring data frame and uploads it together in the next monitoring data upload cycle. This method eliminates the waiting time for the transmission of acknowledgment frames, sacrificing the accuracy of phased confirmations in exchange for a shorter overall preemption process time. After sending a query request, the telemetry and control terminal confirms whether the control command has been executed by parsing the status word carried in the monitoring data frame replied by the slave station. If the status word indicates that the command execution failed, the telemetry and control terminal records the fault event and prompts the staff on the human-machine interface.

[0134] S42, the monitoring and control terminal releases priority and switches to monitoring and query mode.

[0135] After confirming that the control command has been received and executed by the slave station, the telemetry and control terminal performs a priority release operation. This operation includes: the CPU clearing the flag of the currently executing high-priority control task, switching the task scheduler from the "control priority" state back to the "normal monitoring" state, and switching the bus communication mode from control command issuance mode to monitoring data query mode.

[0136] At the task scheduling level, after the CPU of the monitoring and control terminal records the completion event of the current control command message transmission to the task log, it clears the completed control task entries in the command queue to be sent and resets the monitoring data reception and parsing task as the current default task. At the same time, the CPU resets the internal bus preemption status flag, so that the subsequent communication process returns to the normal monitoring data frame reception and processing state.

[0137] S43, the monitoring and control terminal constructs and sends a monitoring data query request message.

[0138] The CPU of the measurement and control terminal is according to Figure 9The communication message format of the control and measurement terminal shown is used to construct a monitoring data query request message. This query request message shares the same frame structure as the control command message in S31, the difference being the setting of the function code field—the function code of the query request message is set to the encoded value corresponding to the query function, and the data field is empty or only contains the data type indicator bit of the query, indicating that the slave station uploads complete monitoring data, including the low-voltage side voltage and current of transformer 1 and transformer 2, the temperature information of each measuring node in the system, the input and output voltage and current of the magnetic control circuit, and fault information, etc.

[0139] The measurement and control terminal writes the constructed query request message into the UART transmit buffer. After the bus is idle, it enables the driver and sends the query request message to the RS485 differential bus.

[0140] It should be noted that the priority release operation in S42 and the query request sending operation in S43 are closely linked in timing. The monitoring and control terminal releases the priority and sends the query request immediately after confirming that the control command has been executed, without setting any additional time delay in between, so as to minimize the time required to recover from the control mode to the monitoring mode and reduce the interruption window of monitoring data.

[0141] S44, the slave station receives the query request message and restarts the monitoring data upload.

[0142] After the slave station is in the control command receiving state and has completed the execution of the control command, its UART receiver remains enabled and continues to listen for subsequent communication messages on the bus. When a query request message sent by the telemetry and control terminal arrives, the slave station's UART hardware receives the message completely according to the same receiving procedure as S33.

[0143] After receiving the query request message, the slave station performs the following operations: S441, the slave station parses the function code field in the message and identifies it as a monitoring data query request, rather than a new control command. Based on this, the slave station switches its communication state from "control command receiving state" back to "monitoring data sending state".

[0144] S442, read the latest monitoring data from the slave station—including the low-voltage side voltage and current sampling values ​​of transformer 1 and transformer 2, the latest temperature readings at each temperature node, the electrical parameters of the input and output terminals of the magnetic control circuit, and the current fault status word—according to Figure 9 The message format shown encapsulates this data into monitoring data frames.

[0145] In step S443, after the slave station's UART driver is enabled, it sends the monitoring data frame to the RS485 differential bus. During transmission, the slave station's transceiver continues to maintain the configuration described in step S22, where both the driver and receiver are enabled simultaneously, to maintain the ability to detect potential subsequent bus collisions in real time.

[0146] In one implementation, the slave station initiates data upload immediately upon receiving a query request message, without waiting for a predetermined upload period. This method enables the immediate resumption of monitoring data uploads, further shortening the monitoring data interruption window caused by preemption processes, and allowing staff to see the latest system operating status more quickly on the human-machine interface of the monitoring and control terminal.

[0147] In another implementation, the slave station does not immediately upload data. Instead, it treats the query request message as a reset signal for the periodic upload timer. The slave station resets its internal upload period timer and sends monitoring data frames periodically according to the predetermined upload cycle. This method maintains the periodic rhythm of monitoring data uploads, avoids fluctuations in the data frame transmission frequency caused by phase misalignment between the query request and the original upload cycle, and facilitates stable parsing and display refresh of the monitoring data by the monitoring and control terminal.

[0148] S45, the monitoring and control terminal receives the monitoring data frame uploaded by the slave station and restores normal monitoring display.

[0149] After sending a query request message, the telemetry and control terminal's UART receiver is enabled, continuously receiving monitoring data frames from the slave station. Upon receiving a monitoring data frame, the telemetry and control terminal performs the following operations: In step S451, the monitoring and control terminal performs integrity verification on the received monitoring data frame according to the same integrity verification process as in step S34, including CRC check and slave address matching. After the verification is successful, the monitoring and control terminal parses each field in the data frame and extracts monitoring data such as transformer electrical parameters, temperature information, magnetic control circuit parameters, and fault status words.

[0150] In S452, the CPU of the monitoring and control terminal writes the parsed monitoring data into the display buffer, driving the display controller of the touch panel to update the various data display areas in the human-machine interface. Specifically, the voltage, current, power, and other parameter values ​​in the main interface are refreshed to the latest sampled values, new data points are added to the original curves in the data curve interface, and the fault status indicator lights are updated to be on or off or have different colors according to the fault status text.

[0151] S453: The monitoring and control terminal simultaneously writes the received monitoring data into the historical database in the memory to form a continuous time series data record for subsequent data playback, trend analysis and fault tracing.

[0152] At this point, the entire preemption process is complete. The telemetry and control terminal has returned from the "control priority state" of responding to the touch operation and executing control commands in step S2 to the normal continuous monitoring state. The interrupted monitoring data frames have been discarded because the slave station cleared the transmission buffer in step S26. The slave station retransmitted the latest monitoring data in step S44, thus ensuring data consistency—that is, the data displayed on the telemetry and control terminal's human-machine interface is the latest state after the system has resumed stable operation after the control command was executed, rather than the outdated data from the time of interruption.

[0153] S46, Exception handling: Retry and fault recording mechanism in the case of preemption failure.

[0154] If the telemetry and control terminal does not receive the expected response from the slave station after sending the priority interrupt sequence in step S2, the telemetry and control terminal will execute the following exception handling procedure: S461, the monitoring and control terminal determined that this preemption attempt failed. Possible reasons for the failure include: strong electromagnetic interference on the communication line causing the slave station to fail to correctly identify the interrupt signature code; the slave station being in an uninterruptible hardware self-test or fault protection state; abnormal physical connection of the bus, etc.

[0155] In step S462, the telemetry and control terminal automatically performs a retry operation: re-executes the physical layer preemption process and control command issuance process from S21 to S26. During the retry, the telemetry and control terminal maintains the same control command content and priority interrupt sequence.

[0156] S463 If ​​the retry is successful, continue with the monitoring and recovery process from S41 to S45, and record this retry event in the fault log, marking it as "preemption retry successful".

[0157] S464: If the expected response is not received after a retry, the control terminal will not attempt a third attempt and will instead determine that the slave station is in an abnormal state. The control terminal will record this preemption failure event in the fault status register and display a fault prompt dialog box on the touch panel's human-machine interface, showing alarm messages such as "Control command issuance failed, please check communication connection." Simultaneously, it will trigger an audible and visual alarm, such as a buzzer or indicator light, to prompt manual intervention. At the interface level, the touched buttons will return to their original state after the press animation, accompanied by a flashing red border to indicate that the operation was unsuccessful, preventing staff from repeating invalid operations due to a lack of feedback.

[0158] This anomaly handling mechanism avoids misoperation or silent failure caused by single communication interference, and improves the reliability of the preemption process through a limited number of automatic retries. Meanwhile, fault logging and alarm notifications enable staff to promptly detect system communication anomalies and take manual troubleshooting measures, preventing potential security risks caused by the system blindly switching to normal operation without actual execution of control commands.

[0159] After staff complete the touch operation on the touch panel and observe the immediate feedback from the control buttons, the human-machine interface resumes normal monitoring data refresh within tens of milliseconds after the control command is executed. The system overview parameters on the main interface, which had been briefly paused due to the preemption process, resume periodic updates, and the previously paused curve plotting in the data curve interface resumes. The entire human-machine interface of the monitoring and control terminal returns to a smooth real-time display state. If the control command involves system start / stop or working mode switching, staff can observe a clear switch in the operating status indicators on the interface—for example, the "Running" status indicator lights up, the active and reactive power values ​​jump from zero or low values ​​to normal operating values, and the direction of the arrow animation representing power flow in the system overview changes. If preemption fails due to communication anomalies, staff will see clear fault prompts and visual feedback of operation failure on the interface, rather than vague changes in equipment status or silent failure.

[0160] Reference Figure 12 Taking a baud rate of 115200bps as an example, traditional half-duplex communication requires waiting for the current monitoring data frame to complete before sending control commands, and the response latency depends on the data frame length. With a frame length of 8 bytes, the latency is approximately 800 microseconds, and the latency increases linearly with the frame length. The preemptive scheduling strategy proposed in this invention has a response latency consisting only of an 18-bit priority interrupt sequence plus a 4-bit squelch window, totaling 22 bits of time, approximately 200 microseconds, and is independent of the data frame length. This invention reduces the control command response latency to less than a quarter of that of the traditional method and is deterministic.

[0161] The above-mentioned interface feedback process together constitutes a complete closed-loop experience from touch operation triggering to system status update confirmation, enabling staff to intuitively and definitively know that their control intentions have been faithfully executed by the system.

[0162] By immediately releasing priority and sending a monitoring data query request after the control command is executed, the slave station can recover from the control command receiving state to the monitoring data sending state in the shortest possible time. This compresses the monitoring data interruption window caused by the preemption process to only the transmission time of the query request message and the slave station's data encapsulation response time. Compared to the traditional half-duplex communication method where the control command needs to wait for the next protocol cycle or timeout retries to resume normal monitoring data reception, the priority release and task recovery mechanism of this invention has a clear triggering time and a deterministic recovery path, avoiding the problems of long-term monitoring data interruption or inconsistent status. At the same time, by discarding interrupted old data frames and retransmitting the latest monitoring data, this invention ensures that the data displayed on the human-machine interface of the monitoring and control terminal always reflects the latest operating status of the system, avoiding data incompleteness or status disorder caused by partial data frame transmission. The automatic retry and fault logging in the exception handling mechanism further improve the robustness and maintainability of the system, ensuring the reliability of preemptive scheduling in various actual operating environments. The configuration options of the conventional working mode and the complete implementation of the preemption process described above together constitute the complete technical solution of the present invention, enabling the measurement and control terminal to flexibly select appropriate communication scheduling strategies in different application scenarios, taking into account both the real-time requirements in high-performance scenarios and the interoperability requirements in compatibility scenarios.

[0163] This embodiment employs a preemptive scheduling strategy, enabling the control terminal to immediately preempt the bus upon receiving an emergency command, balancing real-time performance and communication efficiency. The core lies in injecting an interrupt signal incompatible with the frame format at the physical layer. This triggers a slave hardware interrupt using level conflicts, reducing the control command response delay from the traditional uncertain value of several milliseconds to tens of milliseconds to a fixed value at the hundred-microsecond level, independent of frame length, achieving deterministic and rapid response. An interrupt signature comparison mechanism distinguishes between legitimate preemption and interference, while the conventional mode ensures interoperability with traditional devices. CRC checksums and address matching ensure reliable command delivery, and acknowledgments or status words provide execution feedback. Upon completion, priority is immediately released and a query request is sent. The interrupt window is monitored for minimization, old frames are discarded, and the latest data is retransmitted to ensure display consistency. In case of anomalies, automatic retries and fault recording enhance robustness.

[0164] Example 3, referring to Figure 2 The above is an illustrative scheme of a remote measurement and control method. It should be noted that the technical solution of this remote measurement and control system and the technical solution of the aforementioned remote measurement and control method belong to the same concept. Details not described in detail in this embodiment of the remote measurement and control system can be found in the description of the aforementioned remote measurement and control method.

[0165] This embodiment also provides a remote monitoring and control system, including: The preemptive scheduling strategy selection module is used to perform bus status determination in response to the existence of control command messages to be sent. If the current bus is in the state of receiving data frames by the measurement and control terminal, that is, the slave station occupies the bus to send data, it further determines whether to enable the preemptive scheduling strategy. If the preemptive scheduling strategy is enabled, the priority preemption process is entered. An interrupt signal injection module is used to actively inject an interrupt signal into the bus when it is determined that the measurement and control terminal is receiving a data frame from the slave station; the signal form of the interrupt signal is incompatible with the frame format protocol of the data frame, causing the slave station to trigger a hardware interrupt through a physical layer bus conflict and terminate the transmission of the current data frame; The control command sending module is used to send the control command message to the bus after the interruption signal is sent. The recovery query sending module is used to respond to the slave station receiving the control command message, send a monitoring data query request to the bus, and prompt the slave station to resume uploading monitoring data.

[0166] This embodiment also provides an electronic device applicable to a remote measurement and control method, comprising: a memory and a processor; the memory is used to store computer-executable instructions, and the processor is used to execute the computer-executable instructions to implement a remote measurement and control method as proposed in the above embodiment.

[0167] This embodiment also provides a storage medium on which a computer program is stored. When the program is executed by a processor, it implements a remote measurement and control method as proposed in the above embodiments.

[0168] The storage medium proposed in this embodiment belongs to the same inventive concept as the remote measurement and control method proposed in the above embodiments. Technical details not described in detail in this embodiment can be found in the above embodiments, and this embodiment has the same beneficial effects as the above embodiments.

[0169] Based on the above description of the implementation methods, those skilled in the art can clearly understand that the present invention can be implemented using software and necessary general-purpose hardware, and of course, it can also be implemented using hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, such as a computer floppy disk, read-only memory (ROM), random access memory (RAM), flash memory, hard disk, or optical disk, etc., including several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods of the various embodiments of the present invention.

[0170] It should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention and are not intended to limit it. Although the present invention has been described in detail with reference to preferred embodiments, those skilled in the art should understand that the technical solutions of the present invention can be modified or equivalently replaced without departing from the spirit and scope of the technical solutions of the present invention, and all such modifications or substitutions should be covered within the scope of the claims of the present invention.

Claims

1. A remote monitoring and control method, characterized in that, include: In response to the presence of a control command message to be sent, perform a bus status determination: If the current bus is in the state of receiving data frames by the measurement and control terminal, that is, the slave station occupies the bus to send data, then it is further determined whether to enable the preemptive scheduling strategy. If the preemptive scheduling strategy is enabled, the priority preemption process is executed: the measurement and control terminal actively injects an interrupt signal into the bus. The signal form of the interrupt signal is incompatible with the frame format protocol of the data frame, causing the slave station to trigger a hardware interrupt through a physical layer bus conflict, terminating the transmission of the current data frame. After the interrupt signal is sent, the control command message is sent to the bus. In response to the slave station receiving the control command message, it sends a monitoring data query request to the bus, prompting the slave station to resume uploading monitoring data.

2. The remote monitoring and control method as described in claim 1, characterized in that: Before the measurement and control terminal actively injects an interruption signal into the bus, the following steps are included: The driver and receiver of the slave station's communication transceiver are both enabled during the transmission of the data frame; During the process of the slave station sending the data frame, the slave station continuously samples the actual level on the bus through the receiver and compares it with the driving level it is currently outputting.

3. The remote monitoring and control method as described in claim 2, characterized in that: The measurement and control terminal actively injects an interruption signal into the bus, including: When its own driver is enabled, the measurement and control terminal continuously outputs multiple levels to the bus. The levels of adjacent bits in the multiple levels are different, and the level of the stop bit of the multiple levels violates the provisions of the asynchronous serial communication protocol for stop bit levels followed by the data frame.

4. The remote monitoring and control method as described in claim 3, characterized in that: The termination of the current data frame transmission by the slave station due to a hardware interrupt triggered by a physical layer bus conflict includes: The slave station's communication hardware samples the bus level bit by bit according to the frame format of the asynchronous serial communication protocol to identify the start bit; The multi-bit level is superimposed on the current drive level of the slave station on the bus, causing the stop bit level sampled by the communication hardware to violate the stop bit level specification, thus failing to identify a valid stop bit and generating a frame error interrupt; After the frame error interruption occurs, the slave station reads the subsequent bits immediately following the stop bit from the multi-bit level as the interrupt feature code. After identifying the interrupt feature code as a preset feature code, it stops sending the current data frame and clears the transmission buffer.

5. The remote monitoring and control method as described in claim 4, characterized in that: The physical layer bus conflicts include: During the period when the measurement and control terminal outputs the multi-bit level to the bus, the bus simultaneously carries the driving level of the current data frame being output by the slave station and the multi-bit level output by the measurement and control terminal. The driving level of the slave station and the multi-bit level are superimposed on the bus to form a composite level. The receiver of the slave station samples a synthesized level that is inconsistent with the drive level currently output by the slave station, thereby determining that a bus conflict has occurred.

6. The remote monitoring and control method as described in claim 4, characterized in that: The slave station reads the interrupt signature code after the frame error interruption occurs; After the preset feature code is identified, the slave station terminates the transmission of the current data frame and clears the transmission buffer, and the slave station's reception buffer is cleared after the interruption feature code is read. The slave station switches from the data transmission state to the control command reception state. The telemetry and control terminal sends the control command message to the slave station that is in the control command receiving state, and the control command message is fully received.

7. The remote monitoring and control method as described in claim 1, characterized in that: The measurement and control terminal has the function of switching between preemptive working mode and normal working mode; In the normal operating mode, when there is a control command message to be sent and the telemetry and control terminal is receiving a data frame from the slave station, the telemetry and control terminal does not perform the step of actively injecting an interrupt signal into the bus, but waits for the current data frame to be completely received before sending the control command message to the bus.

8. A remote monitoring and control system, employing a remote monitoring and control method as described in any one of claims 1 to 7, characterized in that, include: The measurement and control terminal and the slave station are connected via a bus communication connection. The measurement and control terminal includes: The preemptive scheduling strategy selection module is used to perform bus status determination in response to the existence of control command messages to be sent. If the current bus is in the state of receiving data frames by the measurement and control terminal, that is, the slave station occupies the bus to send data, then it is further determined whether to enable the preemptive scheduling strategy. If the preemptive scheduling strategy is enabled, the priority preemption process is executed. An interrupt signal injection module is used to actively inject an interrupt signal into the bus when it is determined that the measurement and control terminal is receiving a data frame from the slave station; the signal form of the interrupt signal is incompatible with the frame format protocol of the data frame, causing the slave station to trigger a hardware interrupt through a physical layer bus conflict and terminate the transmission of the current data frame; The control command sending module is used to send the control command message to the bus after the interruption signal is sent. The recovery query sending module is used to respond to the slave station receiving the control command message, send a monitoring data query request to the bus, and prompt the slave station to resume uploading monitoring data.

9. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the remote measurement and control method according to any one of claims 1 to 7.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the steps of a remote measurement and control method according to any one of claims 1 to 7.

Images