Power station arc discharge data acquisition control method and system

Abstract

The invention discloses a power station arc discharge data acquisition control method, which comprises the following steps of: after equipment is electrified, carrying out equipment self-inspection to ensure that each piece of equipment in a system can operate normally and the equipment is accurately positioned when the equipment is abnormal, and ensuring that the abnormal equipment is quickly positioned and repaired; by automatically matching an actual data acquisition scene according to the current environment, the data acquisition efficiency and accuracy are improved, meanwhile, in order to protect equipment, a time interval is increased when an impedance network is set, and due to the increase of the time, secondary scene information checking is added for the accuracy of an arc discharge data scene label, so that the accuracy of the arc discharge data scene label is improved. Data is matched with scene information as much as possible; scene configuration information is obtained in real time before execution each time, and the scene configuration information is synchronously updated to a scene configuration file after data acquisition is completed; it is ensured that data cannot be collected repeatedly when execution is started next time if the data collection is abnormal midway or manually interrupted, errors possibly caused by manual intervention are reduced, and the use threshold of a control system is lowered.

Description

Technical Field

[0001] This invention belongs to the technical field of arc data acquisition, and particularly relates to a power plant arc data acquisition and control method and system. Background Technology

[0002] Existing arc-shaped data collection methods typically rely on manual methods, which require significant manpower, are complex to operate, and raise numerous safety concerns. Real-world data collection scenarios are diverse, making manual collection inefficient. Long-term collection also struggles to acquire large amounts of data, and the coverage is limited. Furthermore, the real-world environment is constantly changing (e.g., weather, cloud cover, etc.), and the time required for manual data collection can be excessive, leading to potentially significant discrepancies in the labels of manually collected data. Summary of the Invention

[0003] The purpose of this invention is to provide a power plant arcing data acquisition and control method and system that can automatically acquire data based on the current actual environment and the matching scenarios in the configuration, thereby improving acquisition efficiency and data accuracy.

[0004] To solve the above problems, the technical solution of the present invention is as follows: A method for acquiring and controlling arcing data in a power plant includes the following steps: The equipment performs a self-test to ensure that it is powered on and operating normally. Obtain system configuration and initialize the device to a reset state; Obtain scene configuration information to confirm whether there are any scene configurations that need to be processed; Acquire current environmental information, including power, current, voltage, illumination, line length, signal quality, temperature, and humidity, to match the scene. Construct a feature vector X composed of power, current, voltage, illumination, line length, signal quality, temperature, and humidity, and calculate the Mahalanobis distance D between X and the pre-stored scene feature vector. 2 If D 2 <χ 2 The match is successful if (0.95, 7). Based on the successfully matched scenario ID, switch to the corresponding impedance network and verify the scenario matching again. If the verification is successful, start arc data acquisition. After successfully collecting arc data, the scene configuration file is updated.

[0005] According to one embodiment of the present invention, the device self-test includes: performing zero drift and gain calibration on the current transformer and voltage divider network, and writing the calibration coefficients into the EEPROM for use during arcing data acquisition, ensuring that the ADC sampling error is <0.5%; The di / dt detection channel is delayed and verified. Only after confirming the preset delay time is the 5 A / μs trigger threshold written to the FPGA comparator register. Otherwise, arc data acquisition triggering is prohibited. Perform a loopback test on the RS-485 / CAN-FD link. If the test fails, mark COMM_FAIL and suspend the arcing data acquisition task until communication is restored. Test the high-voltage interlock HVIL and relay contact resistance. If HVIL is open or the contact resistance is >50 mΩ, then the high-voltage relay is locked out, preventing the arcing data acquisition from being powered on. After all the above self-test items pass, release the high-speed sampling clock and DMA channel to allow entry into the arc data acquisition state.

[0006] According to one embodiment of the present invention, when obtaining system configuration, the system uses three sources of configuration as input: local SD card, host computer TCP command, and cloud MQTT, and verifies consistency using CRC32. If they are inconsistent, the system enters configuration conflict mode.

[0007] According to one embodiment of the present invention, when obtaining scene configuration information, the power level + line length + temperature and humidity range triplet is mapped to a 32-bit MurmurHash3 value, and a binary search is used to retrieve it in the scene configuration table.

[0008] According to one embodiment of the present invention, based on the successfully matched scene ID, the system switches to the corresponding π-type or T-type impedance network via a relay matrix. After the impedance network is switched, a 100 kHz sinusoidal excitation is injected into the line under test and the reflection coefficient Γ is detected. If |Γ| < 0.1, the secondary verification is passed. After the secondary verification is passed, arcing data is collected at a preset ADC sampling rate. The trigger condition is di / dt > 5 A / μs and the duration is > 200 ns. The collected data is then directly written to DDR via DMA.

[0009] According to one embodiment of the present invention, when updating the scene configuration file, only the changed fields are updated, and Protocol Buffers are used for serialization and BCH(63,56) ECC verification is performed. If multiple consecutive matching failures occur after the update, the system will automatically roll back to the previous version.

[0010] According to one embodiment of the present invention, the updated scenario configuration hash value is written into the Hyperledger Fabric private chain to prevent tampering.

[0011] According to one embodiment of the present invention, during the arc data acquisition process, the waveform kurtosis coefficient K is calculated in real time. If K < 3, a suspected anomaly is marked, and the sampling rate is reduced and the data is reacquired to improve the accuracy of data labeling.

[0012] A power plant arcing data acquisition and control system, comprising: The device self-test module is used to ensure that the device is turned on and operating normally; The initialization module is used to obtain system configuration and initialize the device to a reset state. The information acquisition module is used to acquire scene configuration information to confirm whether there are any scene configurations that need to be processed. The scene matching module is used to acquire current environmental information to match scenes, construct a feature vector X composed of power, current, voltage, illumination, line length, signal quality, temperature and humidity, and calculate the Mahalanobis distance D between X and the pre-stored scene feature vectors. 2 If D 2 <χ 2 The match is successful if (0.95, 7). The secondary matching module is used to switch to the corresponding impedance network based on the successfully matched scenario ID, and verify the scenario matching again. If the verification is successful, arc data acquisition will begin. The configuration update module is used to update the scene configuration file after successfully collecting arc data.

[0013] Because the present invention adopts the above technical solution, it has the following advantages and positive effects compared with the prior art: In one embodiment of the present invention, the power plant arcing data acquisition and control method performs a self-test after the equipment is powered on to ensure that each device in the system can operate normally and accurately locate any abnormal devices, thus ensuring rapid location and repair of faulty devices. By automatically matching the actual data acquisition scenario according to the current environment, the efficiency and accuracy of data acquisition are improved. To protect the equipment, a time interval is added when setting the impedance network. This increased time also necessitates a secondary scenario information check to ensure the accuracy of the arcing data scenario label, guaranteeing that the data matches the scenario information as closely as possible. Scenario configuration information is acquired in real time before each execution, and the scenario configuration file is updated synchronously after data acquisition is completed. This ensures that if data acquisition is interrupted due to an abnormality or human intervention, data will not be collected repeatedly when execution resumes, reducing errors that may result from manual intervention and lowering the barrier to entry for the control system. Attached Figure Description

[0014] Figure 1 This is a flowchart of a power plant arcing data acquisition and control method according to an embodiment of the present invention; Figure 2 This is a block diagram of a power plant arcing data acquisition and control system according to an embodiment of the present invention. Detailed Implementation

[0015] The following detailed description, in conjunction with the accompanying drawings and specific embodiments, provides a power plant arcing data acquisition and control method and system based on the present invention. The advantages and features of the present invention will become clearer from the following description and claims.

[0016] Please refer to Figure 1 This embodiment provides a method for acquiring and controlling arcing data in a power plant, including the following steps: The equipment performs a self-test to ensure that it is powered on and operating normally. Obtain system configuration and initialize the device to a reset state; Obtain scene configuration information to confirm whether there are any scene configurations that need to be processed; Acquire current environmental information, including power, current, voltage, illumination, line length, signal quality, temperature, and humidity, to match the scene. Construct a feature vector X composed of power, current, voltage, illumination, line length, signal quality, temperature, and humidity, and calculate the Mahalanobis distance D between X and the pre-stored scene feature vector. 2 If D 2 <χ 2 The match is successful if (0.95, 7). Based on the successfully matched scenario ID, switch to the corresponding impedance network and verify the scenario matching again. If the verification is successful, start arc data acquisition. After successfully collecting arc data, the scene configuration file is updated.

[0017] The arcing data acquisition and control method for this power station performs a self-check after power-on to ensure the normal operation of every device in the system and accurate location of equipment malfunctions, enabling rapid identification and repair of faulty devices. It improves data acquisition efficiency and accuracy by automatically matching the actual data acquisition scenario to the current environment. To protect the equipment, a time interval is added when setting the impedance network. This increased time also necessitates a secondary scenario information verification to ensure the accuracy of the arcing data scenario labels, guaranteeing that the data matches the scenario information as closely as possible. Scenario configuration information is acquired in real-time before each execution, and is synchronously updated to the scenario configuration file after data acquisition. This ensures that if data acquisition is interrupted due to an anomaly or human intervention, data will not be collected repeatedly upon restarting, reducing errors that may result from manual intervention and lowering the barrier to entry for the control system.

[0018] Specifically, the equipment self-test includes: performing a loopback test on the RS-485 link: the main control unit sends a 0x55 0xAA heartbeat frame, and the sub-device must return the same result within a preset time; performing a CRC15 check test on the CAN-FD link: sending an extended frame ID 0x12345678 and comparing the CRC15 check value; injecting a 1 ARMS 50 Hz calibration signal into the current transformer while the bus is de-energized, and recording the ADC zero drift value.

[0019] Once the device is powered on, within 50 ms of the power supply stabilizing, the main control MCU begins a "communication check." First, it sends a pre-defined 0x55 0xAA heartbeat frame to all daughterboards via RS-485, requiring a response within 2 ms. Then, it switches to CAN-FD, sending an extended frame and verifying the CRC15 checksum. Finally, it checks the link indicator bit of the Ethernet PHY. If any bus fails its self-test three times consecutively, the corresponding fault flag will be set, and the system will automatically enter a slowdown retry phase or switch to a backup channel.

[0020] Next is the simulation front-end's "zero drift and accuracy check." With the bus de-energized, the internal calibration source injects a 1 A, 50 Hz standard signal into the current transformer; the ADC calculates the DC offset using a 128-point FFT, and if the deviation exceeds 5 mA, the system writes the correction value back to the register and simultaneously saves it to the EEPROM. Similarly, the 1000 V precision source is switched to a voltage divider network, and an error greater than 0.5% is flagged. The temperature and humidity sensors are also compared with the factory calibration register; a temperature deviation exceeding 0.2 °C or a humidity deviation exceeding 2% RH will trigger an "environmental sensor drift" warning.

[0021] The following 50 ms is used for safety interlock self-test: a 10 mA current loop is injected into the high-voltage interlock circuit; if the return current is less than 8 mA, it is considered an open circuit; the relay contacts are tested for resistance using the four-wire method, and a resistance exceeding 50 mΩ is considered degraded. If either check fails, the system will immediately disconnect the high-voltage relay and enter a safe shutdown state.

[0022] Finally, the memory and firmware integrity are verified. The 512 kB AXI SRAM undergoes a 14-step read / write test using the March-C algorithm; any bit flip will trigger a RAM fault flag. The entire Flash memory is checked once using CRC32; if it does not match the pre-stored value, it is automatically restored from the backup partition, and a "Flash check error" is recorded.

[0023] All results are summarized into a 32-bit status word, coded in four levels: "Normal / Minor / Severe / Critical". If all passes, the green LED flashes three times quickly, and the system allows the next step; if a "critical" level fault occurs, the red LED stays on, the equipment is prohibited from continuing operation, and manual intervention is required.

[0024] During the equipment self-test phase, zero drift and gain calibration were performed on the current transformer and voltage divider network, and the calibration coefficients were written to the EEPROM. When arc acquisition is started, the ADC driver directly calls these coefficients to complete digital compensation, ensuring that the amplitude error at 2 MSPS high-speed sampling is <0.5%. Otherwise, the trigger threshold will drift and mask the true arc signal.

[0025] During the self-test, a 1 A RMS calibration source was used to verify the delay and bandwidth of the di / dt detection channel. Only when the detection delay was confirmed to be <50 ns did the FPGA write the 5 A / μs trigger threshold into the comparator register. If the self-test fails, this threshold will be forcibly set to "infinity" to prevent arcing triggering from the source and to prevent false alarms.

[0026] If the loopback test of RS-485 / CAN-FD fails, the system will mark "COMM_FAIL" and the arc acquisition module will be suspended. This is because waveform data needs to be uploaded in real time via CAN-FD. If the link is down, the monitoring is meaningless. The device would rather not collect data than leave a blind spot.

[0027] High voltage interlock (HVIL) and relay contact resistance tests are "veto" items for self-testing: when HVIL is open or contact resistance is >50 mΩ, the high voltage relay is locked and arcing acquisition cannot be powered on; only when the self-test passes and the optocoupler return current is >8 mA is it allowed to send high voltage to the impedance network to ensure the safety of personnel and equipment during the acquisition process.

[0028] The FPGA will only release the high-speed sampling clock after confirming that the 24 V → 3.3 V power rail timing is correct and the FPGA DONE pin is pulled high. If the power supply ripple is >1% or the clock jitter is >100 ps, ​​the FPGA will refuse to open the DMA channel to avoid inter-symbol interference during high-speed sampling and misjudgment of arcing.

[0029] The temperature, humidity, and light drift values ​​recorded during self-test are used as dynamic compensation benchmarks in the real-time kurtosis calculation of arc acquisition. If an abnormal K value is found during the acquisition phase, the system can compare it with the self-test benchmark to quickly locate whether it is a sudden change in the environment or sensor drift, thereby deciding whether to roll back the parameters or trigger a maintenance alarm.

[0030] Self-testing acts as a "safety calibration lock" and "accuracy benchmark package" for arc light data acquisition: if the self-test fails, acquisition is prohibited from starting; if the self-test passes, all calibration values, thresholds, and safety lock statuses are directly referenced by the acquisition task, ensuring that every arc light waveform is built on a reliable, controllable, and traceable hardware and parameter foundation.

[0031] When obtaining system configuration, the system uses three sources of configuration as input: local SD card, host computer TCP command, and cloud MQTT. The system checks for consistency using CRC32. If the consistency is inconsistent, the system enters configuration conflict mode.

[0032] Once the power-on self-test is complete, the device enters the "acquire system configuration" phase—it simultaneously faces three potentially conflicting "configuration lists": the SD card inserted by maintenance personnel in the field card reader, real-time commands issued by the host computer via TCP, and the latest parameters pushed by the cloud MQTT. The device first prioritizes these three sources: the SD card is always the most important, followed by TCP, and then MQTT. Next, the three data streams are brought in in parallel, and each stream is verified using CRC32 or SHA256 fingerprinting. The one with the latest version number and that passes verification is immediately written into a "temporary copy" in memory. If the three fingerprints are inconsistent, the system will prioritize the SD card version, while keeping the other two as "candidates" for manual confirmation.

[0033] When obtaining scene configuration information, the triplet of power level + line length + temperature and humidity range is mapped to a 32-bit MurmurHash3 value, and a binary search is used to retrieve it from the scene configuration table.

[0034] After the equipment completes system-level configuration, the next step is scenario configuration—determining the appropriate "power-line length-temperature and humidity" combination for the site and which impedance network should be used for arc detection. To this end, three possible scenarios are prioritized: the field card in the SD card slot is the most important, followed by the backup in the onboard QSPI Flash, and finally, the real-time push via cloud MQTT.

[0035] The device first scans the / scene / directory on the SD card, and sorts the bin files whose filenames contain a hash and version number in descending order of timestamp. If the card is not inserted or the directory is empty, it automatically searches for the same path in the QSPI Flash. If neither is found, it simply blocks for 30 seconds, waiting for the cloud to push the latest compressed package.

[0036] Upon receiving the file, the device doesn't rush to use it. Instead, it performs a "check-up": the file length must be a multiple of 64 bytes, and the entire packet is run using CRC32. Files that fail the check are immediately renamed to *.bad and moved on to the next candidate. Files that pass the check-up are decoded by nanopb into SceneCfg structures: power, wire length, upper and lower limits of temperature and humidity, the corresponding impedance network number, and 7-dimensional covariance diagonal elements, etc., all of which are put into a 128-record RAM table and sorted in ascending hash order for easy binary search later.

[0037] When actually performing scene matching, the device concatenates the currently measured power, current, voltage, illumination, line length, signal quality, temperature, and humidity into a 7-dimensional feature vector. This vector is first quantized and then a 32-bit MurmurHash3 value is calculated. A binary search is then performed in the RAM table—a maximum of 7 comparisons are needed to locate a candidate scene. Once found, the Mahalanobis distance is calculated again; if it is less than χ... 2 If the threshold is met, the scenario is confirmed.

[0038] The power, current, voltage, illumination, wire length, signal quality, and temperature and humidity information are derived from the sensors and communication modules already installed inside the equipment. Power: The product of voltage and current samples taken at the same time: P = Vrms × Irms, calculated by the 16-bit ADC (ADS8688) every 1 ms after sampling at 2 MSPS.

[0039] Current: It is fed by a high-precision current transformer (0.1% class) + sampling resistor, and enters ADC channel 0 through instrumentation amplifier INA240 to directly output Irms.

[0040] Voltage: Vrms is obtained by connecting the high voltage divider network (1000 V→1 V) + isolation operational amplifier AMC1100 to ADC channel 1 and synchronously sampling.

[0041] Lighting: Provided by the onboard digital ambient light sensor BH1750, I 2 It has a Type-C interface, a 0.5 lx resolution, and is mounted inside the transparent window of the chassis. It updates every 100 ms.

[0042] Cable length: The cable length is measured by the device during the initial start-up inspection via TDR (Time Domain Reflectometry) pulse: The FPGA emits a 1ns step pulse, and the echo time Δt is converted into L = v·Δt / 2 (v is the cable speed factor of 0.2 m / ns). The result is written to NVM and automatically remeasured after the cable is replaced in the field.

[0043] Signal quality: The received signal strength is indicated by the communication module (CAN-FD or RS-485); if it is CAN, the equivalent RSSI is calculated using the frame error rate FER, ranging from 0 to 100%.

[0044] Temperature and humidity: Utilizing the integrated temperature and humidity sensor SHT35,I 2 C interface, ±0.2 °C, ±2 %RH accuracy, refresh rate per second, probe extends 5 mm out of the housing to avoid internal heat interference.

[0045] Before each scene matching, these 7 data streams are sampled by the MCU with a unified timestamp (1 ms beat), packaged into a 7-dimensional vector X, and directly fed into the FPGA's Mahalanobis distance engine to achieve on-site feature input.

[0046] Based on the successfully matched scene ID, the system switches to the corresponding π-type or T-type impedance network via a relay matrix. After the impedance network switch, a 100 kHz sinusoidal excitation is injected into the line under test, and the reflection coefficient Γ is detected. If |Γ| < 0.1, the secondary verification is passed. After the secondary verification is passed, arcing data is acquired at a preset ADC sampling rate. The trigger condition is di / dt > 5 A / μs and the duration is > 200 ns. The acquired data is then directly written to DDR via DMA.

[0047] During the arc data acquisition process, the waveform kurtosis coefficient K is calculated in real time. If K < 3, it is marked as a suspected anomaly, and the sampling rate is reduced and the data is reacquired to improve the accuracy of data labeling.

[0048] Once the scene matching is successful, the device immediately enters the actual "arc data acquisition" stage. First, it locks the sampling clock to a high-speed ADC with 2 MSPS and 16-bit resolution, while maintaining a 200 µs "listening window" on the bus—this pre-trigger buffer acts like a "rewind" on a video recorder, ensuring that no arc light details that may precede the trigger point are missed.

[0049] Subsequently, the system employs a dual trigger condition: when the current change rate di / dt exceeds 5 A / µs and persists for more than 200ns, the FPGA immediately pulls the trigger line low, and the DMA controller moves the old data from the first 200 µs along with the real-time data from the following 800 µs into DDR3 in one go. The entire process is completed in hardware, with the CPU only responsible for post-processing confirmation, achieving true zero packet loss.

[0050] During sampling, a dedicated coprocessor calculates the kurtosis coefficient K in real time within a 256-point sliding window. If the K value is found to be lower than 3, the system immediately reduces the sampling rate to 500 kSPS and resamples 512 points for recalculation. If the waveform is still abnormal, it is labeled as "low confidence" and sent to an independent buffer, and reported in real time via CAN-FD. Three consecutive abnormalities will automatically freeze the current impedance network, awaiting manual confirmation.

[0051] When updating the scenario configuration file, only the changed fields are updated. Protocol Buffers are used for serialization, and BCH(63,56) ECC verification is performed. If multiple consecutive matches fail after the update, the system automatically rolls back to the previous version. Alternatively, the updated scenario configuration hash value can be written to the Hyperledger Fabric private chain to prevent tampering.

[0052] As soon as an arcing event ends, the device immediately initiates a scene configuration update, writing the new data brought by the arc back to the knowledge base.

[0053] First, the DSP completes "post-processing" in just 50 milliseconds: extracting the waveform from the previous 1 ms into 7 key numbers—peak power, arc current, minimum voltage, light drop, line length, signal quality, and ambient temperature—and then calculating an intensity exponent A and a duration τ, using these to construct a 32-bit event fingerprint. These numbers are then encapsulated into a 32-byte SceneDelta, pasted into RAM like a sticky note.

[0054] Next, the device uses the fingerprint on the note to locate the currently used "scene page". If found, it only updates the changed parts: the power limit is raised by the new peak value, the lower limit of the line length is lowered by the new cable length, and the covariance matrix is ​​quietly tightened using the Welford online algorithm; if not found, it opens a new page in the 128-record LRU table and pushes the old data out. All changes only modify the difference fields, avoiding full page erasure.

[0055] After the modifications, the system assigns a new version number to this scenario, writes the entire page content into a temporary .bin file, adds a CRC32 signature and a timestamp, and after confirming it's correct, removes the ".tmp" suffix and instantly replaces the file in the Flash main area. Simultaneously, the same page is copied to the mirror area as a safety net in case of power failure or accidental writes. To ensure the cloud is also aware, the device sends the SceneDelta via MQTT with QoS=2 and an HMAC signature. The blockchain also writes the file hash into an immutable private blockchain block.

[0056] If the new scenario fails to match three times in a row, the device will immediately roll back to the previous stable version, the yellow light will stay on to remind maintenance, and the reason for the rollback will be broadcast via CAN-FD.

[0057] The entire closed loop of "refinement - incremental - verification - synchronization - rollback" is completed within 100 milliseconds from the end of the waveform to the configuration taking effect, allowing the equipment to "understand the field better with each acquisition" and make the next matching faster, more accurate and safer.

[0058] Based on the same concept, this embodiment also provides a power station arcing data acquisition and control system, please refer to... Figure 2 The system includes: The device self-test module is used to ensure that the device is turned on and operating normally; The initialization module is used to obtain system configuration and initialize the device to a reset state. The information acquisition module is used to acquire scene configuration information to confirm whether there are any scene configurations that need to be processed. The scene matching module is used to acquire current environmental information to match scenes, construct a feature vector X composed of power, current, voltage, illumination, line length, signal quality, temperature and humidity, and calculate the Mahalanobis distance D between X and the pre-stored scene feature vectors. 2 If D 2 <χ 2 The match is successful if (0.95, 7). The secondary matching module is used to switch to the corresponding impedance network based on the successfully matched scenario ID, and verify the scenario matching again. If the verification is successful, arc data acquisition will begin. The configuration update module is used to update the scene configuration file after successfully collecting arc data.

[0059] This system is used to implement the above-mentioned power plant arcing data acquisition and control method. Its implementation method is similar and will not be described in detail here.

[0060] The embodiments of the present invention have been described in detail above with reference to the accompanying drawings, but the present invention is not limited to the above embodiments. Even if various changes are made to the present invention, if these changes fall within the scope of the claims of the present invention and their equivalents, they shall still fall within the protection scope of the present invention.

Claims

1. A method for acquiring and controlling arcing data in a power plant, characterized in that, Includes the following steps: The equipment performs a self-test to ensure that it is powered on and operating normally. Obtain system configuration and initialize the device to a reset state; Obtain scene configuration information to confirm whether there are any scene configurations that need to be processed; Acquire current environmental information, including power, current, voltage, illumination, line length, signal quality, temperature, and humidity, to match the scene. Construct a feature vector X composed of power, current, voltage, illumination, line length, signal quality, temperature, and humidity, and calculate the Mahalanobis distance D between X and the pre-stored scene feature vector. 2 If D 2 < χ 2 The match is successful if (0.95, 7). Based on the successfully matched scenario ID, switch to the corresponding impedance network and verify the scenario matching again. If the verification is successful, start arc data acquisition. After successfully collecting arc data, the scene configuration file is updated.

2. The power plant arcing data acquisition and control method as described in claim 1, characterized in that, The equipment self-test includes: zero drift and gain calibration of the current transformer and voltage divider network, and writing the calibration coefficients into the EEPROM for use during arcing data acquisition, ensuring that the ADC sampling error is < 0.5%; Delay verification is performed on the di / dt detection channel. After confirming the preset delay time, the trigger threshold is written into the FPGA comparator register. Otherwise, arc data acquisition triggering is prohibited. Perform a loopback test on the RS-485 / CAN-FD link. If the test fails, mark COMM_FAIL and suspend the arcing data acquisition task until communication is restored. Test the high-voltage interlock HVIL and relay contact resistance. If HVIL is open or the contact resistance is > 50 mΩ, then the high-voltage relay is locked out, preventing the arcing data acquisition from being powered on. After all the above self-test items pass, release the high-speed sampling clock and DMA channel to allow entry into the arc data acquisition state.

3. The power plant arcing data acquisition and control method as described in claim 1, characterized in that, When obtaining system configuration, the system uses three sources of configuration as input: local SD card, host computer TCP command, and cloud MQTT. The system checks for consistency using CRC32. If the consistency is inconsistent, the system enters configuration conflict mode.

4. The power plant arcing data acquisition and control method as described in claim 1, characterized in that, When obtaining scene configuration information, the triplet of power level + line length + temperature and humidity range is mapped to a 32-bit MurmurHash3 value, and a binary search is used to retrieve it from the scene configuration table.

5. The power plant arcing data acquisition and control method as described in claim 1, characterized in that, Based on the successfully matched scene ID, the system switches to the corresponding π-type or T-type impedance network via a relay matrix. After the impedance network switch, a sinusoidal excitation is injected into the line under test, and the reflection coefficient Γ is detected. If |Γ| < 0.1, the secondary verification is passed. After the secondary verification is passed, arcing data is collected at a preset ADC sampling rate. The trigger condition is di / dt > 5 A / μs and the duration > 200 ns. The collected data is then written directly to DDR via DMA.

6. The power plant arcing data acquisition and control method as described in claim 1, characterized in that, When updating the scene configuration file, only the changed fields are updated. Protocol Buffers are used for serialization and BCH(63,56) ECC verification is performed. If multiple consecutive matches fail after the update, the system will automatically roll back to the previous version.

7. The power plant arcing data acquisition and control method as described in claim 6, characterized in that, The updated scenario configuration hash value is written to the Hyperledger Fabric private chain to prevent tampering.

8. The power plant arcing data acquisition and control method as described in claim 1, characterized in that, During the arc data acquisition process, the waveform kurtosis coefficient K is calculated in real time. If K < 3, it is marked as a suspected anomaly, and the sampling rate is reduced and the data is reacquired to improve the accuracy of data labeling.

9. A power plant arcing data acquisition and control system, characterized in that, include: The device self-test module is used to ensure that the device is turned on and operating normally; The initialization module is used to obtain system configuration and initialize the device to a reset state. The information acquisition module is used to acquire scene configuration information to confirm whether there are any scene configurations that need to be processed. The scene matching module is used to acquire current environmental information, including power, current, voltage, illumination, line length, signal quality, temperature, and humidity, to match scenes. It constructs a feature vector X composed of power, current, voltage, illumination, line length, signal quality, temperature, and humidity, and calculates the Mahalanobis distance D between X and the pre-stored scene feature vectors. 2 If D 2 < χ 2 The match is successful if (0.95, 7). The secondary matching module is used to switch to the corresponding impedance network based on the successfully matched scenario ID, and verify the scenario matching again. If the verification is successful, arc data acquisition will begin. The configuration update module is used to update the scene configuration file after successfully collecting arc data.

Images