As industrialization continues to increase worldwide, the demand for steel is also growing, along with the variety of steel types required. This necessitates continuous improvement of steel production technology and precision in process control to produce more and better high-quality steel. The batching and feeding processes in steelmaking directly impact steel output and quality. Recording and analyzing these processes is beneficial for process improvement and analyzing the causes of defective products. Below, we will explain the methods and procedures for recording and analyzing the batching and feeding processes using the Zijingqiao real-time database. The overall process can be divided into two parts: coke feeding and ore feeding. Typically, coke and ore are each handled by two separate feeding systems. Before feeding, batching must be performed according to the type of steel being produced. One weighing hopper can correspond to one or two silos. When one weighing hopper corresponds to two silos, a selector is used for material selection. Coke is typically weighed directly in a coke weighing hopper and then fed directly to the ore container. Ore, on the other hand, is usually weighed and mixed in proportion by multiple weighing hoppers, and then weighed and fed together in a total ore weighing hopper. Recording Process Analysis For all weighing hoppers, a weighing cycle ends when the hopper opens. At this point, based on the material source of the weighing hopper (the selected state of the hopper selector), this value is recorded in the intermediate quantity corresponding to this feeding. A feeding record is generated when either the total ore weighing hopper or the coke weighing hopper opens. For coke feeding records, only the feeding quantity of the currently selected hopper is recorded; for ore feeding records, the feeding quantities of each group of components (obtained from the intermediate quantity) and the total ore feeding quantity are recorded. The records generated during the feeding process are published via web browsing. To ensure that all web clients see the same recording results, the data must be inserted into the history during recording. Web clients obtain consistent and complete recording results by querying feeding records within a specified time range. Recording Process Implementation. For ore feeding records, since they consist of a mixture of multiple components and the content of each component needs to be recorded, the weighing results of each component must be recorded using a set of intermediate variables before the feeding record is generated. Depending on whether the ore weighing hopper corresponds to one or two silos, the processing method for generating intermediate quantity records differs, but the triggering condition is always the opening of the discharge gate of the ore weighing hopper. In the database's "Value Change" script, define a processing script for each ore weighing hopper's on/off switch, as shown below: One ore weighing hopper corresponds to one silo. When the switch state changes, the script is: `if (580 Weighing Hopper 5 Open Signal.PV) then 580 Burner 5 Weighing E.PV = 580 Weighing Hopper 5 Weighing.PV; endif;` One ore weighing hopper corresponds to two silos. When the switch state changes, the script is: `if (580 Weighing Hopper 1 Open Signal.PV) then if (580 Ore 1 Burner 11 Selection Signal.PV == 0) then 580 Ore 1 Weighing E.PV = 580 Weighing Hopper 1 Weighing.PV; 580 Burner 11 Weighing E.PV = -99999; else 580 Ore 1 Weighing E.PV = -99999; 580 Burner 11 Weighing E.PV = 580 Weighing Hopper 1 Weighing.PV; endif; endif;` When the ore weighing hopper or coke weighing hopper is opened, a feeding record is generated. To facilitate the retrieval of records in time order, a "record time" database point has been added. The value stored in it does not have much practical significance, but the time it corresponds to is the retrieval condition for other quantities. For both ore weighing hoppers and coke weighing hoppers, a processing script should be defined in the "Value Change" script of the database for each weighing hopper's open/close switch, as shown below: Script for coke weighing hopper switch status change: int Millisecond = $SYSTEM.Millisec; int CurTime = $SYSTEM.LongTime; if (580 Coke Weighing Hopper Open.PV == 1) then InsertHisData2(580 Record Time.PV, $SYSTEM.LongTime, $SYSTEM.LongTime, Millisecond); InsertHisData2(580 Loading System.PV, -99999, CurTime, Millisecond); // Loading system 0 is represented as P InsertHisData2(580 Coke 3 Loading Amount.PV, -99999, CurTime, Millisecond); // Ore without loading InsertHisData2(580 Total Ore Loading Amount.PV, -99999, CurTime, Millisecond); //Here, it is assumed that when the value is 0, it is selected as Coke 1. if (580 Coke 1 Coke 2 Selection Signal.PV == 0) then InsertHisData2(580 Coke 1 Loading Amount.PV, 580 West Coke Weighing.PV, CurTime, Millisecond); InsertHisData2(580 Coke 2 Loading Amount.PV, -99999, CurTime, Millisecond); else InsertHisData2(580 Coke 1 Loading Amount.PV, -99999, CurTime, Millisecond); InsertHisData2(580 Coke 2 Loading Amount.PV, 580 West Coke Weighing.PV, CurTime, Millisecond); endif; endif; Script when the switch status of the mine weighing hopper changes: int Millisecond = $SYSTEM.Millisec; int CurTime = $SYSTEM.LongTime; if (580 West Mine Weighing Hopper Open.PV) then InsertHisData2(580 Recording Time.PV, CurTime, CurTime, Millisecond); InsertHisData2(580 Loading System.PV, 1, CurTime, Millisecond); // 1 indicates the loading system is K InsertHisData2(580 Coke 1 Loading Amount.PV, -99999, CurTime, Millisecond); // No ore or coke loaded InsertHisData2(580 Ball 10 Loading Amount.PV, -99999, CurTime, Millisecond); InsertHisData2(580 Ore 1 Loading Amount.PV, 580 Ore 1 Weighing E.PV, CurTime, Millisecond); // Loaded ore or coke InsertHisData2(580 Total Ore Loading Amount.PV, 580 West Ore Weighing.PV, CurTime, Millisecond); endif; Record query and display The display of records begins by retrieving all record times within a selected time range from a hidden "All Historical Data Table," and then retrieving other record values ​​based on these times and populating the display table with these values. This process is accomplished through the "Event Script" of the "All Historical Data Tables": The "Data Refresh" script in the "Event Script" is as follows: int RecordCount = #RecordTime.GetDataCount(); int RecordIndex = 1; int i,j; //The time of the first record may be less than the start time if ( #RecordTime.GetVal(1,1) < #StartDate.Time ) then RecordCount = RecordCount - 1; RecordIndex = RecordIndex+ 1; endif; if ( RecordCount > #List.RowCount() - 2) then #List.AddRow(RecordCount - (#List.RowCount() - 2)); else if ( RecordCount < 18 ) then //18 is the default number of records in this example, which can be adjusted according to the actual situation #List.DelTailRow(#List.RowCount() - 20); //20 is the default number of records plus the number of header rows. #List.ClearRowData(3,18); else #List.DelTailRow(#List.RowCourt() - 2 -RecordCourt); endif; endif; j=1; for i=1to RecordCourt+1step1 if ( #RecordTime.GetVal(1,RecordIndex+i) == #RecordTime.GetVal(3,RecordIndex+i)) then #list.SetVal(1, j+2, #RecordTime.GetVal(1,RecordIndex+i)); #list.SetVal(2, j+2, #RecordTime.GetVal(2,RecordIndex+i)); j=j+1; endif; next; Summary This article mainly takes the steel batching and feeding recording process as an example, and combines the process to realize data recording and query display. This example can serve not only as a prototype for steel batching, material feeding records, and data analysis display, but also, based on its application characteristics (data generation and storage are handled by server-side database scripts, while data querying and display are handled by client-side scripts), it can be extended to other industries. Hopefully, this will be helpful for learning and using the Zijinqiao Real-Time Database.