Method and related device for recording the trend of the coke pushing and charging schedule time of a coke oven

Abstract

The embodiment of the application provides a coke pushing and coal charging plan time trend recording method and related device, and relates to the technical field of coking production. The method acquires each plan timestamp in a shift plan label set; periodically acquires a local system timestamp, and compares the local system timestamp with each plan timestamp in each period; in the case where the local system timestamp is equal to any plan timestamp, a preset update operation is performed on a coke pushing and coal charging plan record digital quantity, trend recording is performed based on the updated coke pushing and coal charging plan record digital quantity, thereby avoiding inherent defects such as logical complexity, timing error and poor fault tolerance caused by field-by-field comparison of year, month, day, hour, minute and second strings in the traditional scheme, and making the plan time have the same properties of collectability, triggerability and recordability as conventional industrial process signals.

Description

Technical Field

[0001] This invention relates to the field of coking production technology, and more specifically, to a method and related apparatus for recording the trend of coke oven pushing and coal charging schedules. Background Technology

[0002] The coke oven is the core equipment in coking production. Its coke pushing and coal charging operations must be strictly executed according to the planned schedule to ensure production continuity, equipment safety, and environmental compliance. Currently, the coke oven locomotive automatic travel and positioning system generates and manages the coke oven coke pushing and coal charging plans through a host computer human-machine interface. The relevant planned times are stored in a date-time format (e.g., 2026-05-11 08:00:00) in an SQL Server database, forming a structured planned data table. This planned data is an important basis for coke oven production scheduling, safety control, and environmental dust removal linkage.

[0003] To meet environmental regulatory requirements, the coking plant has deployed an environmental dust removal DCS control system. This system has a historical trend recording function, which can continuously collect and plot real-time process data such as switch signals (e.g., start / stop signals) and analog signals (e.g., air pressure, temperature). However, the coke oven pushing and coal charging schedule is itself a set of pre-set static time point data in string date and time format, which cannot be recognized by the DCS system and cannot be trend-recorded. Summary of the Invention

[0004] In view of this, the purpose of the present invention is to provide a method and related apparatus for recording the trend of coke oven pushing and coal charging schedule.

[0005] To achieve the above objectives, the technical solutions adopted in the embodiments of the present invention are as follows: In a first aspect, the present invention provides a method for recording the trend of coke oven pushing and coal charging schedules, the method comprising: Retrieve the timestamp of each plan in the current shift plan tag set; The local system timestamp is periodically acquired, and within each period, the local system timestamp is compared with each of the planned timestamps; If the local system timestamp is equal to any of the planned timestamps, a preset update operation is performed on the digital quantity of the coking coal charging plan record to record trends based on the updated digital quantity of the coking coal charging plan record.

[0006] Optionally, the step of pre-setting and updating the digital quantity of the coking coal charging plan record includes: Update the value of the recorded digital quantity of the coking coal charging plan from the first preset value to the second preset value, and start a countdown for the first preset duration; When the countdown ends, the value of the recorded digital quantity of the coking and coal loading plan is reset to the first preset value.

[0007] Optionally, the method further includes: For each preset shift handover time, when the preset shift handover time arrives, the set of plans for the current shift is cleared, and each timestamp of the new plan tag set is copied to the set of plans for the current shift.

[0008] Optionally, the method further includes: For each preset shift handover time, at a time point where the time remaining until the preset shift handover time is a second preset time, the set of plans for the current shift is cleared, and each timestamp of the new set of plans is copied to the set of plans for the current shift.

[0009] The method further includes: For each preset transfer time, when the preset transfer time is reached, the set of on-duty plan tags is cleared, and each plan timestamp in the new plan tag set is copied to the set of on-duty plan tags.

[0010] Optionally, the method further includes: Upon receiving a new planned time series, each planned time in the new planned time series is converted into a planned timestamp and written into the new planned tag set.

[0011] Optionally, the step of converting each planned time in the new planned time series into a planned timestamp includes: For each planned time, the number of seconds elapsed from the preset base time to the planned time is used as the planned timestamp corresponding to the planned time.

[0012] Secondly, the present invention provides a trend recording device for the planned time of coke oven pushing and coal charging, the device comprising: The acquisition module is used to retrieve the timestamp of each plan from the set of plan tags for the current shift. The processing module is used to periodically acquire the local system timestamp and compare the local system timestamp with each of the planned timestamps in each period; if the local system timestamp is equal to any of the planned timestamps, a preset update operation is performed on the digital quantity of the coking coal charging plan record to record trends based on the updated digital quantity of the coking coal charging plan record.

[0013] Thirdly, the present invention provides an electronic device including a processor and a memory, the memory storing machine-executable instructions that can be executed by the processor, the processor executing the machine-executable instructions to implement the trend recording method for coke oven pushing and coal charging schedules described in the first aspect above.

[0014] Fourthly, 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 trend recording method for coke oven pushing and coal charging schedules as described in the first aspect above.

[0015] The method and related apparatus for trend recording of coke oven pushing and coal charging plan time provided in this invention embodiment acquire each plan timestamp in the shift plan tag set; periodically acquire the local system timestamp, and compare the local system timestamp with each plan timestamp in each period; when the local system timestamp is equal to any plan timestamp, perform a preset update operation on the digital quantity of the coke pushing and coal charging plan record, so as to perform trend recording based on the updated digital quantity of the coke pushing and coal charging plan record. Because this invention embodiment converts the coke oven pushing and coal charging plan time into a unified timestamp integer variable and directly compares it with the local system timestamp, it transforms the originally non-real-time, non-analog / switching discrete plan time data into a deterministic trigger signal that can be identified and driven by the event mechanism in the DCS or HMI system, thereby generating a square wave pulse for trend recording. This avoids the inherent defects of traditional solutions, such as logical complexity, timing error susceptibility, and poor fault tolerance caused by relying on field-by-field comparison of year, month, day, hour, minute, and second strings, making the plan time have the same collectable, triggerable, and recordable attributes as conventional industrial process signals.

[0016] To make the above-mentioned objects, features and advantages of the present invention more apparent and understandable, preferred embodiments are described below in detail with reference to the accompanying drawings. Attached Figure Description

[0017] To more clearly illustrate the technical solutions of the embodiments of the present invention, the accompanying drawings used in the embodiments will be briefly introduced below. It should be understood that the following drawings only show some embodiments of the present invention and should not be regarded as a limitation on the scope. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0018] Figure 1 This figure shows a schematic block diagram of an electronic device provided by an embodiment of the present invention; Figure 2 This invention provides a flowchart illustrating a method for recording the trend of coke oven pushing and coal charging schedules according to an embodiment of the present invention. Figure 1 ; Figure 3 This invention provides a flowchart illustrating a method for recording the trend of coke oven pushing and coal charging schedules according to an embodiment of the present invention. Figure 2 ; Figure 4 This invention provides a flowchart illustrating a method for recording the trend of coke oven pushing and coal charging schedules according to an embodiment of the present invention. Figure 3 ; Figure 5 This invention provides a flowchart illustrating a method for recording the trend of coke oven pushing and coal charging schedules according to an embodiment of the present invention. Figure 4 ; Figure 6 The diagram shows a functional block diagram of a coke oven pushing and coal charging plan time trend recording device provided in an embodiment of the present invention.

[0019] Icons: 100 - Electronic device; 110 - Memory; 120 - Processor; 130 - Communication module; 200 - Trend recording device for coke oven pushing and coal charging schedule; 201 - Acquisition module; 202 - Processing module. Detailed Implementation

[0020] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. The components of the embodiments of the present invention described and shown in the accompanying drawings can generally be arranged and designed in various different configurations.

[0021] Therefore, the following detailed description of the embodiments of the invention provided in the accompanying drawings is not intended to limit the scope of the claimed invention, but merely to illustrate selected embodiments of the invention. All other embodiments obtained by those skilled in the art based on the embodiments of the invention without inventive effort are within the scope of protection of the invention.

[0022] It should be noted that relational terms such as "first" and "second" are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0023] The planned coke oven pushing and coal charging time is a crucial parameter in coke oven production and a key factor in the safety and environmental management of coking operations. Operators in the coke oven central control system generate a table of planned coke oven pushing and coal charging times and store it in a database by creating, modifying, and publishing plans on the host computer screen. However, this table only supports static viewing and lacks historical trend curve recording functionality. Therefore, it cannot be compared and analyzed with actual pushing and coal charging times on trend charts, nor can it be used for comprehensive analysis of historical data on coking production safety, environmental protection, and dust control. Due to the continuous improvement of environmental control indicators in coking, coking plants have deployed a Distributed Control System (DCS) for dust control, and there is an urgent need to introduce a trend recording function for the planned coke oven pushing and coal charging time to support the aforementioned comprehensive analysis requirements.

[0024] Traditional PLC (Programmable Logic Controller) or DCS control systems generate historical trend records by relying on real-time data signals with continuous sampling characteristics, such as analog quantities (e.g., temperature, pressure) or digital quantities (e.g., start / stop status). However, the coke oven pushing and coal charging schedule is essentially a set of discrete time points that are manually compiled, periodically updated, and not continuously occurring. It is not a real-time analog or digital data signal, and therefore cannot be directly integrated into existing trend recording mechanisms. Previous attempts involved downloading the coke oven locomotive automatic travel alignment system-generated coke pushing and coal charging schedule to the PLC, programming the PLC to trigger a 60-second square wave pulse (digital quantity) based on the schedule time, and then sending it via communication to the environmental protection and dust removal DCS control system server to complete trend recording. This solution, due to the need for an intermediate PLC step, suffers from problems such as extremely complex PLC programming, high implementation difficulty, and long communication paths. Furthermore, it frequently experiences trend record loss and interruptions caused by schedule modifications, adjustments, or early or delayed schedule releases, failing to meet the requirements of coke oven production control and coking safety and environmental protection management.

[0025] To overcome the shortcomings of the prior art, embodiments of the present invention provide a method and related apparatus for recording the trend of coke oven pushing and coal charging planning time, which will be described in detail below.

[0026] Please refer to Figure 1 This is a block diagram of an electronic device 100. The electronic device 100 includes a memory 110, a processor 120, and a communication module 130. The memory 110, processor 120, and communication module 130 are electrically connected to each other directly or indirectly to realize data transmission or interaction. For example, these components can be electrically connected to each other through one or more communication buses or signal lines.

[0027] The memory 110 is used to store programs or data. The memory 110 may be, but is not limited to, random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), etc.

[0028] The processor 120 is used to read / write data or programs stored in the memory 110 and to perform corresponding functions.

[0029] The communication module 130 is used to establish a communication connection between the electronic device 100 and other communication terminals through the network, and to send and receive data through the network.

[0030] It should be understood that, Figure 1 The structure shown is only a schematic diagram of the electronic device 100. The electronic device 100 may also include components that are larger than... Figure 1 The more or fewer components shown, or having the same Figure 1 The different configurations shown. Figure 1 The components shown can be implemented using hardware, software, or a combination thereof.

[0031] Please refer to Figure 2 The method for recording the trend of coke oven pushing and coal charging plan time provided in this embodiment of the invention includes steps S101 to S103.

[0032] S101, retrieve the timestamp of each plan in the set of plan tags for the current shift.

[0033] S102, periodically obtain the local system timestamp, and compare the local system timestamp with each planned timestamp in each period.

[0034] S103, when the local system timestamp is equal to any planned timestamp, performs a preset update operation on the digital quantity of the coking coal charging plan record, so as to record the trend based on the updated digital quantity of the coking coal charging plan record.

[0035] It should be understood that the traditional programming methods relied upon by the existing solutions generally use date and time strings in the form of year, month, day, hour, minute, and second for multi-field comparison, and then generate square wave pulse signals for the coking and coal loading plan. Whether implemented in the host computer or in the PLC, it is necessary to handle a large number of redundant calculations such as string parsing, time zone conversion, leap year judgment, and cross-day logic. The program structure is loose, debugging is difficult, and robustness is poor.

[0036] The embodiments of this invention abandon this path and instead use a WinCC (Windows Control Center) timed global script to uniformly convert the "latest planned time" stored in the database into the total number of seconds calculated from a preset base time (e.g., January 1, 1970, 08:00:00, i.e., the beginning of the Unix epoch in the East Eight Zone), obtaining a planned timestamp in integer format. This planned timestamp is then sent directly to the FactoryTalk View SE (FactoryTalk ViewSupervisory Edition) software environment via the ODBC (Open Database Connectivity) and OPC (OLE for Process Control) communication links. In this software, the system local time is also synchronously converted into an integer timestamp under the same base and used as a tag in event programming. An event is an expression that triggers an operation. It consists of an equation containing tag values, mathematical operations, if-then-else logic, and other built-in functions. When the system timestamp tag is equal to the value of any planned timestamp tag, the event is triggered and a preset update operation is immediately performed on the digital data recorded in the coking coal loading plan (such as TJJHJL, ZMJHJL).

[0037] In this embodiment of the invention, the process of "preset update operation on the digital quantity of the coking and coal charging plan record" can be as follows: update the value of the digital quantity of the coking and coal charging plan record from a first preset value to a second preset value, and start a countdown for a duration of a first preset duration; when the countdown ends, reset the value of the digital quantity of the coking and coal charging plan record to the first preset value. The first preset value is, for example, a logic low level (0), the second preset value is, for example, a logic high level (1), and the first preset duration is, for example, 60 seconds. This operation ensures that the digital quantity of the coking and coal loading plan record remains at a high level for the first preset duration after being precisely triggered at the planned time point, forming a standard square wave pulse signal. This signal can be continuously collected and archived by the DataLog function of FactoryTalk View SE at a fixed sampling period (e.g., 1 second), and finally presented in the trend chart as a horizontal high-level line segment with a width of 60 seconds, which intuitively corresponds to a planned coking or coal loading process. This design avoids the problems of pulse distortion, missed sampling, or incorrect sampling caused by sampling timing offset, signal jitter, or trigger delay in traditional solutions, ensuring that the trend record is strictly aligned with the planned time, has a standardized form, and clear semantics.

[0038] Understandably, this embodiment of the invention converts the planned coke oven pushing and coal charging time into a unified timestamp integer variable and directly compares it with the local system timestamp. This transforms the originally non-real-time, non-analog / switching discrete planned time data into a deterministic trigger signal that can be identified and driven by the event mechanism in a DCS or HMI system, thereby generating a square wave pulse for trend recording. This fundamentally avoids the inherent defects of traditional solutions, such as logical complexity, timing errors, and poor fault tolerance, caused by relying on field-by-field comparison of year, month, day, hour, minute, and second strings. It gives the planned time the same technical attributes of being collectable, triggerable, and recordable as conventional industrial process signals.

[0039] Because the coke oven control operators work in four shifts, with shift handover taking place at two key times each day: 8:00 AM and 8:00 PM, each shift must prepare and publish the coke pushing and coal charging plan for the next shift on the computer before the handover. For example, the night shift operator prepares the day shift plan (8:00 AM to 8:00 PM) before leaving get off work at 8:00 AM, and the day shift operator prepares the night shift plan (8:00 PM to 8:00 AM) before leaving get off work at 8:00 PM. Since the coke oven has a 2×55-well structure, a single shift plan typically includes approximately 30 heats, resulting in a significant increase in the number of heats per shift within 24 hours. Two plans may be prepared within the same time period, resulting in overlapping plans. More importantly, if the next plan is released in advance before the current plan has been fully executed, the current plan time is easily overwritten or lost, leading to the loss of trend records for the corresponding period. Traditional solutions lack structured management of the plan lifecycle, relying only on single-table storage in the database or static writing to PLC registers, which cannot distinguish between "plans to be effective" and "plans currently being executed", thus failing to guarantee the integrity and timing correctness of plan data during the handover process.

[0040] For this, please refer to Figure 3 The embodiments of the present invention also include step S201, which is executed in parallel with steps S101 to S103.

[0041] S201, for each preset shift handover time, when the preset shift handover time arrives, clear the current shift plan tag set, and copy each plan timestamp in the new plan tag set to the current shift plan tag set.

[0042] In this embodiment of the invention, for each preset shift handover time, when the preset shift handover time arrives, the current shift plan tag set can be cleared, and each plan timestamp in the new plan tag set can be copied to the current shift plan tag set; wherein, the "preset shift handover time" can be 8:00 and 20:00 daily; both the "current shift plan tag set" and the "new plan tag set" are FactoryTalk View. The SE software pre-configured structured tag groups, each containing 220 independent tags (corresponding to all furnace runs in a single shift of 2×55-hole coke ovens), are used to store the timestamp values ​​of the current execution plan and the plans to be implemented. This ensures that the system executes processes S101 to S103 based solely on the timestamps in the current shift's plan tag set at any given time, while the new plan tag set is continuously updated in real time by a WinCC timed global script (VBS). The two are logically isolated and do not interfere with each other. When the preset shift handover time arrives, the system triggers an atomic copy operation through a macro command (JHZC). First, it clears all contents of the current shift's plan tag set, and then writes all non-empty timestamps in the new plan tag set one by one, ensuring that the copy process is uninterrupted and cannot be rolled back. In this way, even if some furnace runs in the new plan have not been filled in or have failed verification, it will not affect the normal participation of the copied valid timestamps in pulse generation, thus balancing the timeliness of plan updates and the robustness of execution.

[0043] Understandably, this embodiment of the invention clears the current shift plan tag set when each preset shift handover time arrives, and copies each plan timestamp in the new plan tag set to the current shift plan tag set, thereby achieving orderly switching and seamless connection of plan data. That is, the plan version is atomically updated with time point as the trigger condition, tag set as the carrier unit, and integer timestamp as the unified data format, thereby avoiding plan data overwriting errors, pulse trigger misalignment, or trend record interruption caused by manual operation timing deviation, overlapping plan release, or delayed execution progress, ensuring that the coking and coal loading plan timestamp sequence always points to the currently valid and logically consistent execution plan at the shift handover time.

[0044] Because the coke oven control room operators work a four-shift, two-rotation system, shift handover operations are concentrated at two key points: 8:00 AM and 8:00 PM each day. In actual operation, situations often arise where the release time of new plans is significantly delayed compared to the shift handover time. For example, the day shift operator should complete and release the night shift plan before 8:00 PM, but due to production anomalies, scheduled maintenance adjustments, or temporary repairs, the actual release time is delayed until 8:05 PM or even later. If the plan switch is still strictly performed at 8:00 PM according to step S201, the system will face "current shift plan" errors because the new plan tag set has not yet been written with a valid timestamp. The dual empty state of "the tag set has been cleared and the new plan tag set is still empty" causes the S101 to S103 processes to be unable to obtain any available plan timestamps in subsequent cycles, resulting in a complete loss of trend records for 4 hours from 20:00 to the next hour (0:00). This problem is significantly harmful in the environmental dust removal DCS control system, because it requires that the coking and coal charging plan pulses must be strictly synchronized with real-time control signals such as the start and stop of the dust removal fan, the action of the smoke guide car, and the adjustment of the gas collection pipe pressure. Once the trend is interrupted, it will directly lead to the failure of environmental data attribution, the inability to trace the excessive events, and the distortion of compliance reports.

[0045] For this, please refer to Figure 4 The embodiments of the present invention also include step S301, which is executed in parallel with steps S101 to S103.

[0046] S301, for each preset shift handover time, at a time point where the time remaining until the preset shift handover time is the second preset time, clear the current shift plan tag set and copy each plan timestamp in the new plan tag set to the current shift plan tag set.

[0047] The "second preset duration" can be set to 5 seconds, corresponding to the preset shift handover times of 8:00 and 20:00 daily. The actual execution times of S301 are 7:59:55 and 19:59:55, respectively. This design enables the system to start the plan switching process 5 seconds before the shift handover: First, it checks whether all 220 valid timestamps (corresponding to all furnace times of a single shift of 2×55-hole coke ovens) already exist in the new plan tag set. If any tag is found to be empty or has an abnormal format, copying is paused and an alarm is triggered. If all verifications pass, the clear and copy operations are immediately executed, and the new plan timestamps are loaded into the current shift plan tag set in batches. During the 5-second window between then and the shift handover time (8:00 or 20:00), the system has complete and valid new shift plan data and can respond to the calls of S101 to S103 processes at any time. Even if the shift handover time is delayed for some reason, or the operator does not click to confirm in time, the loaded new plan can still drive the trend record, completely eliminating the record gaps caused by the delay in the release time.

[0048] Understandably, in this embodiment of the invention, at a time point a second preset time interval away from each preset shift handover time, the current shift plan tag set is cleared, and each plan timestamp in the new plan tag set is copied to the current shift plan tag set. This advances the plan version update operation from "instantaneous triggering at the top of the hour" to "execution within a reserved window period before shift handover," enabling the system to complete data readiness and logical verification before the physical handover occurs. This avoids gaps in plan effectiveness caused by delays in manual operation, network communication jitter, or software response lag, ensuring that the coking and coal loading plan timestamp sequence is always continuous, without gaps, and traceable on the timeline.

[0049] Although coke oven central control operators are scheduled in four shifts with two rotations, dynamic factors such as production control, coke oven scheduled maintenance, and temporary fault repairs often require real-time adjustments to plans during shifts. If only steps S201 (hourly handover switching) or S401 (pre-handover buffer switching) are relied upon, plan changes occurring outside of handover periods will not take effect in a timely manner. For example, if the day shift operator temporarily adjusts the coking time of the next five heats at 12:00 noon based on the equipment status, and this change does not trigger hourly switching, the new timestamp will remain in the new plan tag set, while the plan tag set for the current shift will still use the old value. This causes the S101-S103 processes to continuously generate pulses based on outdated plans, resulting in a serious disconnect between trend records and actual production actions. More seriously, frequent manual triggering of switching will significantly increase the operational burden and the risk of misoperation, while completely eliminating manual intervention will lead to delays in plan updates. Neither of these can meet the stringent requirements of the environmental dust removal DCS control system for data timeliness and accuracy.

[0050] For this, please refer to Figure 5 The embodiments of the present invention also include step S401, which is executed in parallel with steps S101 to S103.

[0051] S401: For each preset transfer time, when the preset transfer time is reached, clear the current shift plan tag set and copy each plan timestamp in the new plan tag set to the current shift plan tag set.

[0052] The "preset transfer time" can be set to six fixed times daily: 0:00, 4:00, 8:00, 12:00, 16:00, and 20:00, covering all major production periods throughout the day. This allows the system to automatically complete the plan version upgrade at the predetermined time without waiting for manual instructions. First, it verifies whether all 220 tags in the new plan tag set (corresponding to all furnace cycles of the 2×55-hole coke ovens per shift) have been written with valid timestamps. If there are null or abnormal values, the transfer is skipped and logged. If all verifications pass, the cleanup is atomically executed. The empty and copy operations ensure that the entire set of plan tags for the shift is refreshed within milliseconds. From then until the next preset transfer time, the S101 to S103 processes always run based on the latest version of the plan. Regardless of whether manual fine-tuning or batch revisions occur in between, the trend records are strictly synchronized with the latest plan. At the same time, this method of transferring every 4 hours takes into account both the timeliness of updates and the balance of system load. Compared with transferring every minute or hour, it can avoid communication congestion and CPU overload caused by high-frequency IO operations, which meets the requirements of industrial sites for both stability and real-time performance.

[0053] Understandably, this embodiment of the invention constructs a periodic, regular, and low-load plan data refresh mechanism by clearing the current shift plan tag set when the preset transfer time arrives, and copying each plan timestamp in the new plan tag set to the current shift plan tag set. This mechanism actively drives the orderly rotation of plan versions at fixed time intervals, avoiding discontinuous trend records, pulse misalignment, or data lag caused by the arbitrariness of manual operation, the suddenness of plan adjustments, or the uncertainty of system response. This ensures that the coking coal loading plan timestamp sequence is uniformly updated, logically consistent, predictable, and verifiable on the time axis.

[0054] The following is a detailed explanation of the update process for the "New Plan Tag Set".

[0055] In this embodiment of the invention, when a new planned time series is received, each planned time in the new planned time series can be converted into a planned timestamp and written into a new planned tag set.

[0056] The process of "converting each planned time in the new planned time series into a planned timestamp" can be as follows: for each planned time, the number of seconds elapsed from the preset base time to the planned time is used as the planned timestamp corresponding to the planned time.

[0057] In this embodiment of the invention, the "preset base time" can be set to 08:00:00 on January 1, 1970, UTC+8 (i.e., the equivalent starting point of the Unix epoch in the UTC+8 time zone). This choice ensures that all timestamp calculations are based on the same absolute zero point, completely avoiding time zone conversion errors. This conversion is completed by calling the SQL Server database built-in function DATEDIFF through a WinCC timed global script (VBS).

[0058] The DATEDIFF function returns a non-negative integer value representing the total number of seconds between the planned time and the baseline time. For example, if the planned time is "2026-05-12 08:15:30", the corresponding planned timestamp is 1778545530. This integer result is then written to the pre-configured "New Plan Tag Set" in the FactoryTalk View SE software. This set consists of 220 independent tags (corresponding to all furnace runs in a single shift of the 2×55-hole coke ovens). Each tag is defined as an integer variable (Integer Tag) to ensure zero loss of numerical accuracy, minimize storage space, and maximize reading speed. Since the entire conversion process is completed in a closed loop on the WinCC host computer side, without the need for PLC participation in the calculation or dependence on the time synchronization accuracy of the OPC server, it has high reliability and strong robustness.

[0059] Understandably, embodiments of the present invention, upon receiving a new planned time series, convert each planned time in the new planned time series into a planned timestamp and write it into a new planned tag set. This establishes a dynamic injection method for planned data, using timestamps as a unified data base, event-driven updates as a mechanism, and tag sets as storage carriers. This allows manually compiled, unstructured date and time strings, susceptible to format and time zone interference, to be mapped in real-time, losslessly, and comparablely to single integer values. This enables discrete planned times to possess the same data semantics and operational capabilities as native process variables in industrial control systems, fundamentally eliminating pulse triggering inaccuracies caused by string parsing errors, leap year misjudgments, cross-day logic confusion, or local time zone deviations.

[0060] To perform the corresponding steps in the above embodiments and various possible methods, an implementation of a trend recording device 200 for coke oven pushing and coal charging planning time is given below. Further, please refer to... Figure 6 , Figure 6This is a functional block diagram of a coke oven coking and coal charging schedule trend recording device 200 provided in this embodiment of the invention. It should be noted that the basic principle and technical effects of the coke oven coking and coal charging schedule trend recording device 200 provided in this embodiment are the same as those in the above embodiments. For the sake of brevity, any parts not mentioned in this embodiment can be referred to the corresponding content in the above embodiments. The coke oven coking and coal charging schedule trend recording device 200 includes: Module 201 is used to retrieve the timestamp of each plan in the set of plan tags for the current shift.

[0061] The processing module 202 is used to periodically acquire the local system timestamp and compare the local system timestamp with each planned timestamp in each period; when the local system timestamp is equal to any planned timestamp, a preset update operation is performed on the digital quantity of the coking coal charging plan record, so as to record the trend based on the updated digital quantity of the coking coal charging plan record.

[0062] Optionally, the above modules can be stored in the form of software or firmware. Figure 1 The memory 110 shown can be used by Figure 1 The processor 120 executes the program. Meanwhile, the data and program code required to execute the above modules can be stored in the memory 110.

[0063] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can also be implemented in other ways. The apparatus embodiments described above are merely illustrative; for example, the flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of apparatus, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions marked in the blocks may occur in a different order than those marked in the drawings. For example, two consecutive blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram and / or flowchart, and combinations of blocks in block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or action, or using a combination of dedicated hardware and computer instructions.

[0064] In addition, the functional modules in the various embodiments of the present invention can be integrated together to form an independent part, or each module can exist independently, or two or more modules can be integrated to form an independent part.

[0065] If the aforementioned functions are implemented as software functional modules and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this invention, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0066] The above description is merely a preferred embodiment of the present invention and is not intended to limit the invention. Various modifications and variations can be made to the present invention by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the scope of protection of the present invention.

Claims

1. A method for recording the trend of coke oven pushing and coal charging schedules, characterized in that, The method includes: Retrieve the timestamp of each plan in the current shift plan tag set; The local system timestamp is periodically acquired, and within each period, the local system timestamp is compared with each of the planned timestamps; If the local system timestamp is equal to any of the planned timestamps, a preset update operation is performed on the digital quantity of the coking coal charging plan record to record trends based on the updated digital quantity of the coking coal charging plan record.

2. The method for recording the trend of coke oven pushing and coal charging schedule as described in claim 1, characterized in that, The steps for pre-setting and updating the digital quantity of the coking coal charging plan record include: Update the value of the recorded digital quantity of the coking coal charging plan from the first preset value to the second preset value, and start a countdown for the first preset duration; When the countdown ends, the value of the recorded digital quantity of the coking and coal loading plan is reset to the first preset value.

3. The method for recording the trend of coke oven pushing and coal charging schedule as described in claim 1, characterized in that, The method further includes: For each preset shift handover time, when the preset shift handover time arrives, the set of plans for the current shift is cleared, and each timestamp of the new plan tag set is copied to the set of plans for the current shift.

4. The method for recording the trend of coke oven pushing and coal charging schedule as described in claim 1, characterized in that, The method further includes: For each preset shift handover time, at a time point where the time remaining until the preset shift handover time is a second preset time, the set of plans for the current shift is cleared, and each timestamp of the new set of plans is copied to the set of plans for the current shift.

5. The method for recording the trend of coke oven pushing and coal charging schedule as described in claim 1, characterized in that, The method further includes: For each preset transfer time, when the preset transfer time is reached, the set of on-duty plan tags is cleared, and each plan timestamp in the new plan tag set is copied to the set of on-duty plan tags.

6. The method for recording the trend of coke oven pushing and coal charging schedule as described in any one of claims 3 to 5, characterized in that, The method further includes: Upon receiving a new planned time series, each planned time in the new planned time series is converted into a planned timestamp and written into the new planned tag set.

7. The method for recording the trend of coke oven pushing and coal charging schedule as described in claim 6, characterized in that, The step of converting each planned time in the new planned time series into a planned timestamp includes: For each planned time, the number of seconds elapsed from the preset base time to the planned time is used as the planned timestamp corresponding to the planned time.

8. A trend recording device for the planned time of coke oven pushing and coal charging, characterized in that, The device includes: The acquisition module is used to retrieve the timestamp of each plan from the set of plan tags for the current shift. The processing module is used to periodically acquire the local system timestamp and compare the local system timestamp with each of the planned timestamps in each period; if the local system timestamp is equal to any of the planned timestamps, a preset update operation is performed on the digital quantity of the coking coal charging plan record to record trends based on the updated digital quantity of the coking coal charging plan record.

9. An electronic device, characterized in that, The method includes a processor and a memory, the memory storing machine-executable instructions that can be executed by the processor to implement the trend recording method for coke oven pushing and coal charging schedules as described in any one of claims 1-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 trend recording method for the coke oven pushing and coal charging plan time as described in any one of claims 1-7.

Images