An electronic detonator compatible method and system, electronic device and storage medium

Abstract

This application provides a compatible method, system, electronic device, and storage medium for electronic detonators, belonging to the field of electronic detonators. The method includes: determining a target identification code for the electronic detonator, wherein the target identification code is used to uniquely identify the electronic detonator, and the target identification code includes a segment code of the electronic detonator; obtaining the delay time of the electronic detonator according to the segment code and a preset relationship mapping table, wherein the relationship mapping table indicates the correspondence between the segment code and the delay time; and adjusting the detonation of the electronic detonator according to the delay time. This application enables compatible design of both preset and field-set electronic detonators.

Description

Technical Field

[0001] This application relates to the field of electronic detonators, and more particularly to an electronic detonator compatible method and system, electronic device and storage medium. Background Technology

[0002] According to the definition of relevant standards, digital electronic detonators are divided into two types: pre-set electronic detonators with the delay time written at the detonation factory and field-set electronic detonators with the delay time set at the detonation site.

[0003] Generally, pre-set blasting is used in repetitive tunnel blasting operations, where there is no need to set a delay time, and the requirements for on-site blasting personnel are relatively low. On-site set blasting is generally used in open-air operations where the blasting effect needs to be improved, or in special application environments where vibration reduction and noise reduction are required. It is necessary to adjust the blasting parameters according to the borehole network parameters and rock structure at the blasting site, and the requirements for personnel are relatively high.

[0004] Therefore, how to flexibly adjust the delay time of electronic detonators to achieve compatibility design for both preset and field-mounted electronic detonators has become an urgent problem to be solved. Summary of the Invention

[0005] The main objective of this application is to propose an electronic detonator compatible method and system, electronic device and storage medium, which aims to achieve compatible design of pre-set and field-set electronic detonators.

[0006] To achieve the above objectives, a first aspect of this application proposes an electronic detonator-compatible method, the method comprising:

[0007] Determine the target identification code of the electronic detonator, wherein the target identification code is used to uniquely identify the electronic detonator, and the target identification code of the electronic detonator includes the segment code of the electronic detonator;

[0008] The delay time of the electronic detonator is obtained according to the segment code and the preset relationship mapping table, wherein the relationship mapping table is used to indicate the correspondence between the segment code and the delay time;

[0009] The detonation of the electronic detonator is adjusted according to the aforementioned delay time.

[0010] In some embodiments, the target identifier is obtained by updating an initial identifier, which is written into the electronic delay module of the electronic detonator in the following manner:

[0011] Obtain preliminary data for the electronic delay module;

[0012] The electronic delay module was subjected to performance testing, and the first test result was obtained.

[0013] If the first detection result indicates that the electronic delay module is qualified, then the module serial number of the electronic delay module is added to 1 to obtain the target module serial number;

[0014] The initial identification code is generated based on the preliminary data of the electronic delay module and the serial number of the target module;

[0015] Write the initial identification code into the electronic extension module;

[0016] After writing the initial identifier code into the electronic delay module, the written identifier code is read from the electronic delay module.

[0017] The initial identifier code after writing is compared with the initial identifier code to obtain the comparison result;

[0018] If the comparison result indicates that the initial identifier code after writing is consistent with the initial identifier code, then the electronic delay module is determined to be qualified and the writing of the initial identifier code is determined to be completed.

[0019] In some embodiments, prior to adjusting the detonation of the electronic detonator according to the delay time, the method further includes registering the detonator in the following manner:

[0020] The detonator is subjected to a first initialization operation, wherein the first initialization operation includes at least one of initializing registration hole information, initializing the barcode scanning module, initializing registration voltage detection, and initializing current detection;

[0021] The registration key's status is monitored, and the monitoring results are obtained.

[0022] If the monitoring result indicates that the registration key has not been pressed, then the current surge is detected to obtain a second detection result;

[0023] If the second detection result indicates that a current surge has been detected, then the target identification code is read.

[0024] After successfully reading the target identifier code, the target identifier code is verified.

[0025] After the target identification code is successfully verified, the electronic detonator is subjected to performance testing to obtain a third test result;

[0026] If the third test result indicates that the performance of the electronic detonator is qualified, then the target identification code is parsed to obtain the tube code and segment code of the electronic detonator;

[0027] The system displays a successful registration message.

[0028] In some embodiments, adjusting the detonation of the electronic detonator according to the delay time includes:

[0029] A second initialization operation is performed on the detonator, wherein the second initialization operation includes at least one of initializing the communication voltage, initializing the detonation voltage, initializing the correspondence between the segment code and the delay time;

[0030] Send a data retrieval request;

[0031] If the target identifier and detonation code are received according to the data acquisition request, it is determined whether the delay time needs to be adjusted, and a first determination result is obtained;

[0032] If the first judgment result indicates that the delay time needs to be adjusted, then it is determined whether the electronic detonator is used in a segmented manner, and a second judgment result is obtained.

[0033] If the second judgment result indicates that the electronic detonator is used in a segmented manner, then the correspondence between the segment code and the delay time of the electronic detonator is modified.

[0034] The delay time of the electronic detonator is calculated based on the segment code;

[0035] Test the electronic detonator network;

[0036] The delay time is calibrated, and the calibration result is written into the detonator;

[0037] The electronic detonator is decoded according to the detonation code, and detonation is authorized.

[0038] In some embodiments, determining whether the delay time needs to be adjusted includes:

[0039] Obtain index data for adjusting the delay time, wherein the index data includes at least one of the following: the insertion condition of the electronic detonator, rock hardness, drilling spacing, and charge amount;

[0040] Based on the aforementioned indicator data, a determination is made as to whether the delay time needs to be adjusted.

[0041] In some embodiments, determining the target identifier code of the electronic detonator includes:

[0042] Based on the pre-acquired chip code, working capacitor code, detonating capacitor code, capacitor withstand voltage code, ignition component code, design version number, and PCB version number, generate key material codes;

[0043] Based on the pre-obtained pipe factory code, machine number high digit, year high digit, year low digit and month splicing result, production date, machine number low digit, box number code, and box serial number, generate the pipe code code;

[0044] Obtain the module type, segment code, and check byte of the electronic detonator;

[0045] The target identification code of the electronic detonator is determined based on the key material code, the module type, the segment code, the tube code, and the check byte.

[0046] In some embodiments, obtaining the delay time of the electronic detonator based on the segment code and a preset relational mapping table includes:

[0047] Obtain the relationship mapping table;

[0048] Obtain the segment code from the target identifier code;

[0049] Based on the segment code, traverse the relation mapping table to find the delay time corresponding to the segment code.

[0050] To achieve the above objectives, a second aspect of this application provides an electronic detonator-compatible system, the system comprising:

[0051] The target identification code determination module is used to determine the target identification code of the electronic detonator, wherein the target identification code is used to uniquely identify the electronic detonator, and the target identification code of the electronic detonator includes the segment code of the electronic detonator;

[0052] The delay time acquisition module is used to obtain the delay time of the electronic detonator according to the segment code and the preset relationship mapping table, wherein the relationship mapping table is used to indicate the correspondence between the segment code and the delay time;

[0053] The detonation adjustment module is used to adjust the detonation of the electronic detonator according to the delay time.

[0054] To achieve the above objectives, a third aspect of this application provides an electronic device, which includes a memory and a processor. The memory stores a computer program, and the processor executes the computer program to implement the method described in the first aspect.

[0055] To achieve the above objectives, a fourth aspect of the present application provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the method described in the first aspect.

[0056] The electronic detonator compatible method, system, electronic device, and storage medium proposed in this application determine the target identification code of the electronic detonator. This target identification code uniquely identifies the electronic detonator and includes its segment code, enabling differentiation between different electronic detonators. Furthermore, the delay time of the electronic detonator is obtained based on the segment code and a preset mapping table. This mapping table indicates the correspondence between the segment code and the delay time, allowing for convenient determination of the corresponding delay time based on the segment code. This method, which sets the detonator based on the delay time, achieves the function of a preset electronic detonator. Furthermore, adjusting the detonation of the electronic detonator based on the delay time allows for flexible adjustment of the delay time in the detonator according to actual needs, achieving compatibility between preset and field-set electronic detonators. Attached Figure Description

[0057] Figure 1 This is a flowchart of the electronic detonator compatibility method provided in the embodiments of this application;

[0058] Figure 2 yes Figure 1 The flowchart of step S101 in the text;

[0059] Figure 3 This is a flowchart illustrating the process of writing an initial identification code into the electronic delay module of an electronic detonator using an electronic detonator compatibility method provided in this application embodiment;

[0060] Figure 4 This is a schematic diagram illustrating the specific implementation process of writing the initial identification code into the electronic delay module of the electronic detonator in the electronic detonator compatible method provided in this application embodiment;

[0061] Figure 5 This is a schematic diagram illustrating the specific implementation process of writing the target identifier code into the electronic detonator in the electronic detonator compatibility method provided in this application embodiment;

[0062] Figure 6 yes Figure 1 The flowchart of step S102 in the document;

[0063] Figure 7 This is a flowchart of the registered detonator of the electronic detonator compatible method provided in the embodiments of this application;

[0064] Figure 8 This is a schematic diagram illustrating the specific implementation process of the registered detonator of the electronic detonator compatibility method provided in this application embodiment;

[0065] Figure 9 yes Figure 1 The flowchart of step S103 in the process;

[0066] Figure 10This is a flowchart illustrating the determination of whether the delay time needs to be adjusted in the electronic detonator compatibility method provided in this application embodiment;

[0067] Figure 11 This is a schematic diagram illustrating the specific implementation process of the compatible initiation method of the electronic detonator compatible method provided in this application embodiment;

[0068] Figure 12 This is a schematic diagram of the structure of the electronic detonator compatible system provided in the embodiments of this application;

[0069] Figure 13 This is a schematic diagram of the hardware structure of the electronic device provided in the embodiments of this application. Detailed Implementation

[0070] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0071] It should be noted that although functional modules are divided in the system diagram and the logical order is shown in the flowchart, in some cases, the steps shown or described may be performed in a different order than the module division in the system or the order in the flowchart. The terms "first," "second," etc., in the specification, claims, and the aforementioned drawings are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence.

[0072] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used herein is for the purpose of describing embodiments of this application only and is not intended to limit this application.

[0073] According to the definition of relevant standards, digital electronic detonators are divided into two types: pre-set electronic detonators with the delay time written at the detonation factory and field-set electronic detonators with the delay time set at the detonation site.

[0074] Generally, pre-set blasting is used in repetitive tunnel blasting operations, where there is no need to set a delay time, and the requirements for on-site blasting personnel are relatively low. On-site set blasting is generally used in open-air operations where the blasting effect needs to be improved, or in special application environments where vibration reduction and noise reduction are required. It is necessary to adjust the blasting parameters according to the borehole network parameters and rock structure at the blasting site, and the requirements for personnel are relatively high.

[0075] Therefore, how to flexibly adjust the delay time of electronic detonators to achieve compatibility design for both preset and field-mounted electronic detonators has become an urgent problem to be solved.

[0076] Therefore, embodiments of this application propose an electronic detonator compatible method and system, electronic device and storage medium, aiming to achieve compatible design of pre-set and field-set electronic detonators.

[0077] The electronic detonator compatibility method, system, electronic device, and storage medium provided in this application are specifically described through the following embodiments. First, the electronic detonator compatibility method in this application embodiment is described.

[0078] The electronic detonator compatibility method provided in this application relates to the field of electronic detonators. This method can be applied to a terminal, a server, or software running on either a terminal or a server. In some embodiments, the terminal can be a smartphone, tablet, laptop, desktop computer, etc.; the server can be configured as an independent physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDN, and big data and artificial intelligence platforms; the software can be an application implementing the electronic detonator compatibility method, but is not limited to the above forms.

[0079] This application can be used in a wide variety of general-purpose or special-purpose computer system environments or configurations. Examples include: personal computers, server computers, handheld or portable devices, tablet devices, multiprocessor systems, microprocessor-based systems, set-top boxes, programmable consumer electronics, network PCs, minicomputers, mainframe computers, and distributed computing environments including any of the above systems or devices. This application can be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc., that perform specific tasks or implement specific abstract data types. This application can also be practiced in distributed computing environments where tasks are performed by remote processing devices connected via a communication network. In distributed computing environments, program modules can reside in local and remote computer storage media, including storage devices.

[0080] It should be noted that in various specific embodiments of this application, when processing data related to the identity or characteristics of an object, such as object information, object behavior data, object historical data, and object location information, the object's permission or consent is obtained first. Furthermore, the collection, use, and processing of this data comply with relevant laws, regulations, and standards. In addition, when embodiments of this application require obtaining sensitive personal information of an object, separate permission or consent from the object is obtained through pop-ups or redirection to a confirmation page. Only after obtaining the object's separate permission or consent is the necessary object-related data required for the proper functioning of the embodiments of this application obtained.

[0081] Figure 1 This is an optional flowchart of the electronic detonator compatibility method provided in the embodiments of this application. Figure 1 The method may include, but is not limited to, steps S101 to S103.

[0082] Step S101: Determine the target identification code of the electronic detonator, wherein the target identification code is used to uniquely identify the electronic detonator, and the target identification code of the electronic detonator includes the segment code of the electronic detonator;

[0083] Step S102: Obtain the delay time of the electronic detonator according to the segment code and the preset relationship mapping table, wherein the relationship mapping table is used to indicate the correspondence between the segment code and the delay time;

[0084] Step S103: Adjust the detonation of the electronic detonator according to the delay time.

[0085] Steps S101 to S103 of this embodiment involve determining the target identification code of the electronic detonator. The target identification code uniquely identifies the electronic detonator and includes its segment code, allowing for differentiation between different electronic detonators. Further, the delay time of the electronic detonator is obtained based on the segment code and a preset mapping table. This mapping table indicates the correspondence between the segment code and the delay time, facilitating the determination of the corresponding delay time based on the segment code. This allows for the setting of the detonator based on the delay time, thus achieving the function of a preset electronic detonator. Furthermore, adjusting the detonation of the electronic detonator based on the delay time allows for flexible adjustment of the delay time in the detonator according to actual needs, achieving a compatible design for both preset and field-set electronic detonators.

[0086] First, step S101 will be described.

[0087] Please see Figure 2In some embodiments, step S101 of the electronic detonator compatible method may also include, but is not limited to, steps S201 to S204:

[0088] Step S201: Based on the pre-acquired chip code, working capacitor code, detonating capacitor code, capacitor withstand voltage code, ignition component code, design version number, and PCB version number, generate key material codes;

[0089] Step S202: Generate a pipe code based on the pre-obtained pipe factory code, high digit of machine number, high digit of year, low digit of year and month concatenation result, production date, low digit of machine number, box number code, and box serial number;

[0090] Step S203: Obtain the module type, segment code, and check byte of the electronic detonator;

[0091] Step S204: Determine the target identification code of the electronic detonator based on the key material code, module type, segment code, tube code, and check byte.

[0092] Steps S201 to S204 are described in detail below.

[0093] In step S201 of some embodiments, the chip code is the version number of the core MCU used by the module manufacturer, reflecting chip upgrades. The working capacitor code uses encoding to express information about the working capacitor, for example, using 0, 1, and 2 to represent the working capacitor code. 0 indicates no working capacitor, i.e., 0 represents a single-capacitor module; 1 indicates a ceramic capacitor, i.e., 1 represents a pseudo-dual-capacitor module; 2 indicates a tantalum capacitor, i.e., 2 represents an independent dual-capacitor module. The capacitance and model of the ceramic and tantalum capacitors are set according to actual conditions. The detonating capacitor code uses encoding to express information about the detonating capacitor, which is usually a tantalum or aluminum electrolytic capacitor. The capacitor voltage rating code, commonly used for electronic detonators, has voltage ratings of 10V, 16V, 20V, and 25V. This can be represented by encoding 00 for 10V, 01 for 16V, 10 for 20V, and 11 for 25V. The ignition component code reflects the form and parameters such as diameter or width of the ignition component. Ignition components typically come in three types: bowl-shaped bridge wire, surface-mount bridge wire, and detonating resistor. The design version number reflects the module's principle design. The PCB version number reflects the version of the PCB used in the module. The critical material code reflects information about the critical materials used in the electronic detonator module and is written during the module manufacturing process. The critical material code is at least 5 bytes in size. Specifically, all the above information can be obtained manually or by machine; there are no restrictions.

[0094] Because the key materials used in the module can only be seen by dissecting the electronic detonator after assembly, and dissecting the detonator carries certain safety risks, writing the key material information into the target identification code facilitates quality control for the detonator manufacturer. By reading the key material information, the manufacturer can understand whether there have been any changes in the key materials used in the module, which facilitates quality control before production and allows for quality traceability without dissection in case of abnormalities.

[0095] In step S202 of some embodiments, the tube code of the electronic detonator is written according to relevant rules. Based on the assumption that the high-order bits of the tube manufacturer code and year remain largely unchanged, and the machine number code remains largely unchanged, the tube code is redistributed and integrated, dividing it into two parts. Specifically, one part consists of non-communication bytes, which have a relatively fixed size of 2 bytes; the other part consists of communication bytes, which have a size of 4 bytes.

[0096] It should be noted that non-communication bytes are not used for electronic detonator network communication, but only for the management target identification code. Non-communication bytes generally include the detonator manufacturer code, the high-order byte of the machine number, and the high-order byte of the year. The detonator manufacturer code is 8 bits long, the high-order byte of the machine number is 4 bits long, and the high-order byte of the year is 4 bits long.

[0097] The communication byte is a data bit in the detonator code that changes during the detonator's validity period. In electronic detonator networking, it is used as an identification byte for network communication. The communication byte generally includes: the concatenation result of the lower digit of the year and the month, the production date, the lower digit of the machine number, the box number code, and the box serial number. The concatenation result of the lower digit of the year and the month is 5 bits in size.

[0098] Furthermore, to conserve communication bytes, the concatenation result of the year's lower digit and the month is encoded in base 12. This is achieved by dividing the concatenation result by 12, with the quotient representing the year and the remainder representing the month code (where 0 represents December). This method uses 5 bits to ensure that communication bytes do not repeat within 32 months. The production date is 5 bits, the lower digit of the machine number is 5 bits, the box number is 7 bits, and the box serial number is 10 bits.

[0099] Specifically, when obtaining the pipe factory code, the high digit of the machine number, the high digit of the year, the low digit of the year and the concatenation result with the month, the production date, the low digit of the machine number, the box number code, and the box serial number, this series of information can generally be obtained manually or by machine, without any restrictions.

[0100] In step S203 of some embodiments, the module type is used to define the maximum allowable delay of the module, such as 8 seconds, 16 seconds, etc. The module type is generally written by the module manufacturer during production, and its size is 1 byte. The segment code is the segment identification number of the electronic detonator, and it is generally written by the detonator manufacturer during production. The electronic detonator initiator allocates the delay time of the detonator according to the preset segment number, and the segment code is 1 byte in size. The check byte is used to verify whether the data stored in the memory is accurate, usually using an accumulation check method. The check byte needs to be written by both the module manufacturer and the detonator manufacturer during production, and its size is 1 byte.

[0101] Specifically, when obtaining the module type, segment code, and check byte of an electronic detonator, this information can be obtained manually or by machine, without any restrictions.

[0102] In step S204 of some embodiments, the key material code, module type, segment code, tube code, and check byte are sequentially concatenated to obtain the target identification code of the electronic detonator. In other embodiments, the positions of the key material code, module type, segment code, tube code, and check byte in the target identification code are not limited.

[0103] Steps S201 to S204 above allow for the decomposition and definition of the identification code's encoding method. By sequentially concatenating the key material code, module type, segment code, pipe code, and check byte, the number of bytes required for communication in the identification code is reduced, thereby improving communication efficiency. Furthermore, by utilizing bits in the target identification code to correspond to different delay segments, compared to directly storing the delay time, it achieves the effect of occupying less storage space.

[0104] The following is a detailed description of the electronic delay module for writing the initial identification code into the electronic detonator.

[0105] Please see Figure 3 In some embodiments, the target identifier is obtained by updating the initial identifier, which is written into the electronic delay module of the electronic detonator in the following manner:

[0106] Step S301: Obtain preliminary data for the electronic delay module;

[0107] Step S302: Perform performance testing on the electronic delay module to obtain the first test result;

[0108] Step S303: If the first detection result indicates that the electronic delay module is qualified, then add the module serial number of the electronic delay module to 1 to obtain the target module serial number.

[0109] Step S304: Generate an initial identification code based on the preliminary data of the electronic delay module and the serial number of the target module;

[0110] Step S305: Write the initial identification code into the electronic delay module;

[0111] Step S306: After writing the initial identifier code into the electronic delay module, read the initial identifier code after writing from the electronic delay module;

[0112] Step S307: Compare the written initial identifier with the initial identifier to obtain the comparison result;

[0113] Step S308: If the comparison result indicates that the initial identifier code after writing is consistent with the initial identifier code, then the electronic delay module is deemed to have passed the test, and the writing of the initial identifier code is deemed to have been completed.

[0114] Steps S301 to S308 are described in detail below.

[0115] In step S301 of some embodiments, the preliminary data of the electronic delay module includes key material information generated by the module, module type, segment code, production date, pipe manufacturer code, and machine number. The production date is used to obtain the concatenation result of the high and low digits of the year with the month, and the machine number is used to obtain the high and low digits of the machine number. The segment code defaults to 00000000, indicating an online setting type; the pipe manufacturer code defaults to 00000000, indicating it was written by the module manufacturer.

[0116] In step S302 of some embodiments, the performance test includes testing of electrical performance and functionality. The first test result includes whether the electronic delay module is qualified or unqualified. The electronic delay module undergoes performance testing to obtain the first test result. Specifically, the electrical performance and functionality of the electronic delay module are tested. The first test result is that the electronic delay module is qualified only if both electrical performance and functionality tests are qualified; conversely, the first test result is that the electronic delay module is unqualified if either electrical performance or functionality fails, or if both fail.

[0117] In step S303 of some embodiments, the module serial number is the concatenation of the box number code and the box internal serial number. The module serial number of the electronic delay module refers to the serial number of the previous module of the current electronic delay module, and the target module serial number refers to the serial number of the current electronic delay module on the production line. Specifically, if the first detection result indicates that the electronic delay module is qualified, the module serial number is added to 1 to obtain the target module serial number.

[0118] In step S304 of some embodiments, an initial identification code is generated based on the preliminary data of the electronic delay module and the target module serial number. Specifically, firstly, the key material information of the module is written into the position of the key material code in the initial identification code; the module type is written into the position of the module type in the initial identification code; and the default segment code is written into the position of the segment code in the initial identification code. Next, a pipe code is generated based on the default pipe factory code, production date, machine number, and target module serial number. Further, the generated pipe code is written into the position of the pipe code code in the initial identification code. Further, a check byte is generated based on the key material code, module type, segment code, and pipe code, and the generated check byte is written into the position of the check byte in the initial identification code. Finally, the initial identification code is generated.

[0119] In step S305 of some embodiments, the initial identification code is written to the electronic delay module. Specifically, the initial identification code is written to the memory of the electronic delay module.

[0120] In step S306 of some embodiments, after the identification code is written to the electronic delay module, the initial identification code after writing is read from the electronic delay module.

[0121] In step S307 of some embodiments, the comparison result includes whether the written initial identifier code matches the original identifier code or whether the written initial identifier code does not match the original identifier code. Specifically, when comparing the written initial identifier code with the original identifier code to obtain the comparison result, the data of the initial identifier code read from the electronic delay module and the generated initial identifier code are first compared. If the data of the read initial identifier code and the generated initial identifier code match, the comparison result is that the written initial identifier code matches the original identifier code. Correspondingly, if the data of the read initial identifier code and the generated initial identifier code do not match, the comparison result is that the written initial identifier code does not match the original identifier code. In this case, the target module serial number is subtracted from 1.

[0122] In step S308 of some embodiments, if the comparison result indicates that the initial identifier code after writing is consistent with the initial identifier code, then the electronic delay module is determined to be qualified and the writing of the initial identifier code is determined to be completed.

[0123] The following is combined with Figure 4 A detailed description is provided of the electronic delay module that writes the initial identification code into the electronic detonator.

[0124] Please see Figure 4 , Figure 4 This is a schematic diagram illustrating the specific implementation process of writing the initial identification code into the electronic delay module of the electronic detonator in the electronic detonator compatible method provided in this application embodiment.

[0125] First, preliminary data of the electronic delay module is obtained, and the specific implementation process is similar to that of step S301 above.

[0126] Next, the electronic delay module undergoes performance testing, the specific implementation process of which is similar to that of step S302 above. If the performance is found to be qualified, the module serial number is added to 1, that is, the concatenation result of the box number code and the box internal serial number is added to 1 to obtain the target module serial number, the specific implementation process of which is similar to that of step S303 above.

[0127] Next, an initial identifier code is generated and written into the electronic delay module. The specific implementation process is similar to that of steps S304-S305 above.

[0128] Further, the initial identifier code after writing is read, and the specific implementation process is similar to that of step S306 above. Then, the data of the initial identifier code after writing is compared with that of the initial identifier code, and the specific implementation process is similar to that of step S307 above. If the data of the initial identifier code after writing is consistent with that of the initial identifier code, it indicates that the electronic delay module has passed the test, and the specific implementation process is similar to that of step S308 above.

[0129] Finally, the initial identifier writing process ends.

[0130] Furthermore, if a performance failure is detected, it indicates a performance failure and then proceeds to the initial identifier code writing process termination step. If the initial identifier code is inconsistent with the data after writing, it indicates that the initial identifier code writing failed, the target module serial number is subtracted from 1, and then it proceeds to the initial identifier code writing process termination step. To save space, further details are omitted.

[0131] Through steps S301 to S308, the conformity of the electronic delay module can be detected using a dual detection method (i.e., a combination of performance testing and identification code testing), thereby improving the accuracy of the detection. Simultaneously, the above process generates an initial identification code. Furthermore, by modifying the module serial number under different conditions, the rationality of the production line can be improved.

[0132] The following describes how to write the target identification code into the electronic detonator.

[0133] In some embodiments, the target identification code is written into the electronic detonator in the following manner:

[0134] Obtain preliminary data for the electronic detonator;

[0135] The electronic detonator was subjected to performance testing, and the fourth test result was obtained;

[0136] If the fourth test result indicates that the electronic detonator's performance is qualified, then the initial identification code is read from the electronic delay module;

[0137] Based on the preliminary data and initial identification code of the electronic detonator, generate the target identification code;

[0138] Write the target identification code into the electronic detonator;

[0139] After writing the target identification code into the electronic detonator, the written target identification code is read from the electronic detonator;

[0140] The written target identifier code is compared with the target identifier code to obtain the comparison result;

[0141] If the comparison result indicates that the target identification code is consistent with the target identification code after writing, then the detonation code is written into the electronic detonator and decryption detection is performed;

[0142] If the decryption test result indicates successful decryption, then the electronic detonator is deemed to have passed the test, and the writing of the target identifier code is confirmed to be complete.

[0143] The following is combined with Figure 5 The process of writing the target identification code into the electronic detonator is described in detail.

[0144] Please see Figure 5 , Figure 5 This is a schematic diagram illustrating the specific implementation process of writing the target identifier code into the electronic detonator in the electronic detonator compatibility method provided in this application embodiment.

[0145] First, the preliminary data of the electronic detonator is obtained. This preliminary data includes the segment code, manufacturer code, and detonation code. The preliminary data of the electronic detonator is obtained through initialization.

[0146] Then, the electronic detonator undergoes performance testing to obtain a fourth test result. This performance testing includes both electrical performance and functional testing. The fourth test result indicates whether the electronic detonator is qualified or unqualified. Specifically, the electronic detonator's electrical and functional performance are tested. Only if both electrical performance and functional tests are qualified is the fourth test result considered qualified; conversely, if either electrical performance or functional test is unqualified, or if both are unqualified, the fourth test result is considered unqualified.

[0147] If the fourth test result indicates that the electronic detonator is of qualified performance, the initial identification code is read from the electronic delay module configured in the electronic detonator.

[0148] Further, based on the preliminary data and preliminary identification code of the electronic detonator, a target identification code is generated. The encoding rules for the initial and target identification codes are consistent; that is, the location of the encoding for each piece of information with the same meaning in both codes is the same. For example, the position of the key material code in the initial and target identification codes is the same. The initial identification code is generated by the module manufacturer, and the target identification code is generated by the tube manufacturer. Specifically, the tube manufacturer code and segment code in the initial identification code are defaulted to 0. After reading the initial identification code, the tube manufacturer code and segment code are updated. Then, based on the updated tube manufacturer code, the updated segment code, and all information from the preliminary identification code (excluding tube manufacturer codes, segment codes, and check bytes), an updated check byte is obtained. The updated tube manufacturer code, the updated segment code, and the updated check byte are used to obtain the target identification code.

[0149] Next, the target identification code is written into the electronic detonator. Specifically, the target identification code is printed onto the surface of the electronic detonator. In other embodiments, the target identification code is written into the control module of the electronic detonator.

[0150] After the target identification code is written into the electronic detonator, the written target identification code is read from the electronic detonator.

[0151] Subsequently, the written target identifier code is compared with the target identifier code to obtain a comparison result. This comparison result includes whether the written target identifier code matches the target identifier code, or whether they do not match. Specifically, the target identifier code read from the electronic detonator is compared with the generated target identifier code. If the read and generated target identifier codes match, the comparison result is that the written target identifier code matches the target identifier code.

[0152] If the comparison result indicates that the target identifier code is consistent with the target identifier code after writing, then the detonation code is written into the electronic detonator and decryption detection is performed.

[0153] If the decryption test result indicates successful decryption, then the electronic detonator is deemed to have passed the test, and the writing of the target identifier code is confirmed to be complete.

[0154] In the above steps, if the fourth test result indicates that the electronic detonator's performance is unqualified, it indicates that the electronic detonator's performance is unqualified, and then proceeds to the target identifier code writing process end step. If the data of the read target identifier code and the generated target identifier code are inconsistent, it indicates that the target identifier code writing has failed, and then proceeds to the target identifier code writing process end step. If the decryption test result indicates that decryption has failed, it indicates that the password writing has failed, and then proceeds to the target identifier code writing process end step.

[0155] Through the above steps, this embodiment of the application can perform qualification testing on electronic detonators through a triple detection method (i.e., a combination of performance testing, identification code detection, and detonation decryption detection), thereby improving the accuracy of the detection. Simultaneously, by modifying the initial identification code, the target identification code can be obtained, improving the accuracy of the target identification code.

[0156] Next, step S102 will be described.

[0157] Please see Figure 6 In some embodiments, step S102 may include, but is not limited to, steps S601 to S603:

[0158] Step S601: Obtain the relationship mapping table;

[0159] Step S602: Obtain the segment code from the target identifier code;

[0160] Step S603: Based on the segment code, traverse the relation mapping table to find the delay time corresponding to the segment code.

[0161] Steps S601 to S603 are described in detail below.

[0162] In step S601 of some embodiments, the relationship mapping table can be pre-set, and the relationship mapping table represents the correspondence between segment codes and delay times. Specifically, the segment code consists of 1 byte, therefore, binary 00000000 to 11111111 can store a total of 256 segment codes, where 00000000 represents the default segment code written by the module manufacturer. When the segment code is 00000000, the electronic detonator is an online setting type; while 00000001 to 11111111 are written by the detonator manufacturer. The delay time can be 10ms, 15ms, 20ms, 25ms, etc. Based on this, the relational mapping table can be configured to correspond one-to-one between segment codes and delay times according to the ascending order of segment codes and delay times. For example, segment code 00000001 corresponds to a delay time of 10ms, segment code 00000010 corresponds to a delay time of 15ms, segment code 00000011 corresponds to a delay time of 20ms, and so on. Converting the segment code to decimal will give the segment corresponding to the segment code. Segment code 00000001 can be called segment 1, segment code 00000010 can be called segment 2.

[0163] In step S602 of some embodiments, a segment code can be obtained from the target identification code in the electronic detonator. Specifically, the segment code is obtained from the target identification code according to a preset storage location of the segment code.

[0164] In step S603 of some embodiments, the relation mapping table is traversed based on the segment code to find the delay time corresponding to the segment code. Specifically, if the segment code read from the electronic detonator is 00000001, the relation mapping table is traversed. If there is a correspondence between the segment code 00000001 and the delay time of 10ms, then the delay time corresponding to the segment code is found to be 10ms.

[0165] By using steps S601 to S603 above, the delay time corresponding to the segment code can be obtained by querying the relational mapping table. That is, the effect of a preset electronic detonator can be achieved without setting the delay time.

[0166] Next, the registration detonator will be described in detail.

[0167] Please refer to Figure 7 Prior to step S103, the electronic detonator compatibility method further includes registering the detonator, which is registered in the following manner:

[0168] Step S701: Perform a first initialization operation on the detonator, wherein the first initialization operation includes at least one of initializing registration hole information, initializing the barcode scanning module, initializing registration voltage detection, and initializing current detection.

[0169] Step S702: Monitor the status of the registration key and obtain the monitoring results;

[0170] Step S703: If the monitoring result indicates that the registration key has not been pressed, the current surge is detected to obtain a second detection result;

[0171] Step S704: If the second detection result indicates that a current surge has been detected, then the target identification code is read.

[0172] Step S705: After successfully reading the target identifier code, verify the target identifier code;

[0173] Step S706: After the target identification code is successfully verified, the electronic detonator is subjected to performance testing to obtain the third test result;

[0174] Step S707: If the third test result indicates that the performance of the electronic detonator is qualified, then the target identification code is parsed to obtain the tube code and segment code of the electronic detonator.

[0175] Step S708: Display registration success information.

[0176] Steps S701 to S708 are described in detail below.

[0177] In step S701 of some embodiments, the first initialization operation includes at least one of initializing registration hole information, initializing the barcode scanning module, initializing registration voltage detection, and initializing current detection. The detonator is initialized according to the first initialization operation.

[0178] In step S702 of some embodiments, monitoring the state of the registration key refers to monitoring whether the registration key is pressed. The monitoring result includes whether the registration key is not pressed or whether the registration key is pressed. The monitoring result is obtained by monitoring the state of the registration key.

[0179] In step S703 of some embodiments, the second detection result includes whether a current surge was detected or not. If the monitoring result indicates that the registration key was not pressed, a current surge is detected to obtain the second detection result. If the monitoring result indicates that the registration key was pressed, the detonator registration process is exited.

[0180] In step S704 of some embodiments, if the second detection result indicates that a current surge has been detected, the target identification code of the electronic detonator is read. If the second detection result indicates that no current surge has been detected, the status of the scan button is monitored. If the scan button is detected, the target identification code of the electronic detonator is obtained by scanning the code; if the unscanned button is detected, the process returns to step S702.

[0181] In step S705 of some embodiments, after successfully reading the target identifier code, the target identifier code is verified. Specifically, the correctness of the target identifier code is verified by checking the identifier byte in the target identifier code.

[0182] In step S706 of some embodiments, the performance test includes electrical performance and functional testing. The third test result includes whether the electronic detonator's performance is qualified or unqualified. After successful verification of the target identification code, the electronic detonator undergoes performance testing to obtain the third test result. Specifically, when both the electrical performance and function of the electronic detonator are qualified, the obtained third test result indicates that the electronic detonator's performance is qualified. Correspondingly, when at least one of the electronic detonator's electrical performance and function is unqualified, the obtained third test result indicates that the electronic detonator's performance is unqualified.

[0183] In step S707 of some embodiments, if the third detection result indicates that the performance of the electronic detonator is qualified, the target identification code is parsed to obtain the tube code and segment code of the electronic detonator. Specifically, when parsing the target identification code, it can be parsed according to a pre-set encoding rule, and the parsing result is saved. The encoding rule is set according to actual business needs and can be flexibly changed without restriction.

[0184] In step S708 of some embodiments, the registration success message can be text or code indicating successful registration. After parsing and saving the tube code and segment code, the registration success message is displayed. Specifically, after displaying the registration success message, the system points to the next registration hole.

[0185] The following is combined Figure 8 The process of registering a detonator is described in detail.

[0186] Please see Figure 8 , Figure 8 This is a schematic diagram illustrating the specific implementation process of the registered detonator of the electronic detonator compatible method provided in this application embodiment.

[0187] First, the detonator undergoes an initial operation, similar to step S701 described above. Next, the status of the registration key is monitored, similar to step S702. If no registration key is detected, a current surge is detected, similar to step S703. If a current surge is detected, the target identification code is read, similar to step S704. If the target identification code is successfully read, it is verified, similar to step S705. If the target identification code verification is successful, the electronic detonator undergoes a performance test, similar to step S706. If the performance test is successful, the target identification code is parsed to obtain the tube code and segment code, similar to step S707. Finally, a registration success message is displayed, and the system points to the next hole to be registered, similar to step S708.

[0188] It should be noted that during the above process, if the registration button is detected to be pressed, the registration process exits; if no current surge is detected, the barcode scanning button is monitored. If the barcode scanning button is not detected, the process proceeds to the registration button monitoring step; if the barcode scanning button is detected, the target identification code is scanned, and the process proceeds directly to the step of parsing the target identification code to obtain the tube code and segment code. If reading the target identification code fails, or the target identification code verification fails, or the performance test fails, the information of an unqualified electronic detonator is displayed, and the process returns to the registration button monitoring step. If the registration success message is displayed and points to the next hole to be registered, the process returns to the registration button monitoring step. For the sake of brevity, further details are omitted.

[0189] Through the above steps S701 to S708, the detonator can be registered through multiple judgments, including key detection, current surge detection, target identification code reading detection, target identification code verification detection, and electronic detonator performance detection, thereby reducing the error rate of registering unqualified electronic detonators.

[0190] Please refer to Figure 9 In some embodiments, step S103 includes, but is not limited to, steps S901 to S909:

[0191] Step S901: Perform a second initialization operation on the detonator, wherein the second initialization operation includes at least one of initializing the communication voltage, initializing the detonation voltage, initializing the correspondence between the segment code and the delay time;

[0192] Step S902: Send a data acquisition request;

[0193] Step S903: If the target identifier code and detonation code are received according to the data acquisition request, determine whether the delay time needs to be adjusted and obtain the first judgment result.

[0194] Step S904: If the first judgment result indicates that the delay time needs to be adjusted, then determine whether the electronic detonator is used in a segmented manner to obtain the second judgment result.

[0195] Step S905: If the second judgment result indicates that the electronic detonator is used in a segmented manner, then modify the correspondence between the segment code and the delay time of the electronic detonator.

[0196] Step S906: Calculate the delay time of the electronic detonator based on the segment code;

[0197] Step S907: Test the electronic detonator network;

[0198] Step S908: Calibrate the delay time and write the calibration result into the detonator;

[0199] Step S909: Decode the electronic detonator according to the detonation code and authorize the detonation.

[0200] Steps S901 to S909 are described in detail below.

[0201] In step S901 of some embodiments, the second initialization operation includes at least one of initializing the communication voltage, initializing the detonation voltage, initializing the correspondence between the segment code and the delay time. The detonator is initialized according to the second initialization operation.

[0202] In step S902 of some embodiments, a data acquisition request is issued by an object, and the data acquisition request is used to request the acquisition of the target identification code and detonation code of the electronic detonator.

[0203] In step S903 of some embodiments, if a target identifier code and a detonation code are received according to a data acquisition request, a determination is made as to whether the delay time needs to be adjusted, resulting in a first determination result. The first determination result includes determining whether the delay time needs to be adjusted, or determining whether the delay time does not need to be adjusted.

[0204] The following section provides a detailed description of how to determine whether an adjustment to the extension period is necessary.

[0205] Please refer to Figure 10 In some embodiments, the process of determining whether the delay time needs to be adjusted includes, but is not limited to, steps S1001 to S1002:

[0206] Step S1001: Obtain index data for adjusting the delay time, wherein the index data includes at least one of the following: the insertion condition of the electronic detonator, rock hardness, drilling distance, and charge amount.

[0207] Step S1002: Based on the indicator data, determine whether the delay time needs to be adjusted.

[0208] In step S1001 of some embodiments, the index data used to adjust the delay time includes at least one of the following: the insertion condition of the electronic detonator, rock hardness, drilling distance, and charge amount. Specifically, the aforementioned index data can all be obtained from the blasting site.

[0209] In step S1002 of some embodiments, a determination is made as to whether the delay time needs to be adjusted based on the indicator data. Specifically, each indicator is compared with a reference range. If each indicator is within the reference range, the delay time is not adjusted; if at least one indicator is outside the reference range, the delay time is adjusted.

[0210] Through the above steps S1001 to S1002, the delay time can be flexibly adjusted and judged according to various indicators of the on-site environment, so that the delay time is more in line with the blasting requirements of the on-site environment, thereby achieving the effect of on-site set-up electronic detonators.

[0211] In step S904 of some embodiments, segmented application refers to the electronic detonator having the same delay time within the same segment, and the delay times between segments are usually at equal intervals. The second determination result includes whether the electronic detonator is used in a segmented manner or not. Specifically, if the first determination result indicates that the delay time needs to be adjusted, the differences in the delay times of the electronic detonators within the same segment and the differences in the delay times between segments are first determined. Then, if the delay times of the electronic detonators within the same segment are the same, and the delay times between segments are at equal intervals, the second determination result is determined to be that the electronic detonator is used in a segmented manner. If the delay times of the electronic detonators within the same segment are different, and / or the delay times between segments are not at equal intervals, the second determination result is determined to be that the electronic detonator is used in a non-segmented manner.

[0212] In step S905 of some embodiments, if the second determination result indicates that the electronic detonator is a segmented application, the correspondence between the segment code and the delay time is modified. Specifically, the relationship mapping table contains segment code 00000001, which corresponds to a delay time of 10ms. However, in actual practice, the delay time needs to be set to 25ms, so the delay time of segment code 00000001 can be directly changed to 25ms.

[0213] In step S906 of some embodiments, the delay time of the electronic detonator is calculated based on the segment code. Specifically, the segment code is converted into the corresponding delay time of the electronic detonator according to the correspondence between the segment code and the delay time.

[0214] In step S907 of some embodiments, the electronic detonator network is tested. Specifically, the reliability of the connections inside and outside the electronic detonator control chip is repeatedly tested online. This repeated online testing includes testing the charging control circuit, the safety discharge circuit, and the ignition control circuit.

[0215] In step S908 of some embodiments, the delay time is calibrated, and the calibration result is written to the detonator. Specifically, since electronic detonators typically use an on-chip RC oscillator as the counting clock, there is a problem of temperature drift. Therefore, during use, the delay time needs to be read out, calibrated, and then rewritten by the detonator into the delay counter with the corresponding delay time value.

[0216] In step S909 of some embodiments, authorization refers to the requirement that the detonator requires authorization from the safety officer, the blaster, and the gas detection personnel before detonation. In a specific implementation of this embodiment, the relevant personnel decode the electronic detonator according to the detonation code and authorize the detonation.

[0217] The following is combined with Figure 11 The detonation process of the embodiments of this application will be described in detail.

[0218] Please see Figure 11 , Figure 11 This is a schematic diagram illustrating the specific implementation process of the compatible detonation provided in the embodiments of this application.

[0219] First, the detonator undergoes a second initial operation, similar to step S901 described above. Next, a data acquisition request is sent, similar to step S902. Then, it is determined whether the target identifier code and detonation code have been received. If so, it is determined whether the delay time needs adjustment, similar to step S903. If adjustment is needed, it is determined whether the electronic detonator is a segmented application, similar to step S904. If the electronic detonator is segmented, the correspondence between the segment code and the delay time is modified, similar to step S905. Finally, the delay time of the electronic detonator is calculated based on the segment code, similar to step S906. Next, the electronic detonator network is tested. After the network passes the test, the delay time is calibrated and written to the initiator. Then, the electronic detonator is decoded and authorized for detonation. The specific implementation process is similar to steps S907-S909 above. If the target identifier code and detonation code are not received, the detonation process ends. If the delay time does not need adjustment, the process proceeds to the step of calculating the delay time of the electronic detonator based on the segment code. If the electronic detonator is a non-segmented application, the delay time of the electronic detonator is modified individually or in batches before proceeding to the step of testing the electronic detonator network. For brevity, this will not be elaborated further.

[0220] Through steps S901 to S909, the actual required delay time and the preset delay time of the electronic detonator can be obtained. By modifying the correspondence between the segment code and the delay time on the detonator, the preset delay time of the electronic detonator can be adjusted to the actual required delay time on site. This improves the detonation efficiency compared to directly modifying the time of the electronic detonator. Furthermore, it has the advantage of flexible delay time setting compared to existing preset electronic detonators.

[0221] Please see Figure 12 This application also provides an electronic detonator compatible system that can implement the above-described electronic detonator compatible method. The system includes:

[0222] The target identification code determination module 1201 is used to determine the target identification code of the electronic detonator. The target identification code is used to uniquely identify the electronic detonator and includes the segment code of the electronic detonator.

[0223] The delay time acquisition module 1202 is used to obtain the delay time of the electronic detonator according to the segment code and the preset relationship mapping table, wherein the relationship mapping table is used to indicate the correspondence between the segment code and the delay time;

[0224] The detonation adjustment module 1203 is used to adjust the detonation of the electronic detonator according to the delay time.

[0225] The specific implementation of this electronic detonator compatible system is basically the same as the specific implementation of the above-described electronic detonator compatible method, and will not be repeated here.

[0226] This application also provides an electronic device, which includes a memory and a processor. The memory stores a computer program, and the processor executes the computer program to implement the above-described electronic detonator compatible method. This electronic device can be any smart terminal, including tablet computers, in-vehicle computers, etc.

[0227] Please see Figure 13 , Figure 13 The hardware structure of an electronic device according to another embodiment is illustrated. The electronic device includes:

[0228] The processor 1301 can be implemented using a general-purpose CPU (Central Processing Unit), microprocessor, application-specific integrated circuit (ASIC), or one or more integrated circuits, and is used to execute relevant programs to implement the technical solutions provided in the embodiments of this application.

[0229] The memory 1302 can be implemented as a read-only memory (ROM), static storage device, dynamic storage device, or random access memory (RAM). The memory 1302 can store the operating system and other application programs. When the technical solutions provided in the embodiments of this specification are implemented through software or firmware, the relevant program code is stored in the memory 1302 and is called and executed by the processor 1301 to execute the electronic detonator compatible method of the embodiments of this application.

[0230] The input / output interface 1303 is used to implement information input and output;

[0231] The communication interface 1304 is used to enable communication and interaction between this device and other devices. Communication can be achieved through wired means (such as USB, Ethernet cable, etc.) or wireless means (such as mobile network, WIFI, Bluetooth, etc.).

[0232] Bus 1305 transmits information between various components of the device (e.g., processor 1301, memory 1302, input / output interface 1303, and communication interface 1304);

[0233] The processor 1301, memory 1302, input / output interface 1303 and communication interface 1304 are connected to each other within the device via bus 1305.

[0234] This application also provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the above-described electronic detonator compatible method.

[0235] Memory, as a non-transitory computer-readable storage medium, can be used to store non-transitory software programs and non-transitory computer-executable programs. Furthermore, memory may include high-speed random access memory, and may also include non-transitory memory, such as at least one disk storage device, flash memory device, or other non-transitory solid-state storage device. In some embodiments, memory may optionally include memory remotely located relative to the processor, and these remote memories can be connected to the processor via a network. Examples of such networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.

[0236] The electronic detonator compatibility method, system, electronic device, and storage medium provided in this application embodiment determine the target identification code of the electronic detonator. This target identification code uniquely identifies the electronic detonator and includes its segment code, enabling differentiation between different electronic detonators. Further, the delay time of the electronic detonator is obtained based on the segment code and a preset mapping table. This mapping table indicates the correspondence between the segment code and the delay time, allowing for convenient determination of the corresponding delay time based on the segment code. This enables the setting of the detonator based on the delay time, achieving the function of a preset electronic detonator. Furthermore, adjusting the detonation of the electronic detonator based on the delay time allows for flexible adjustment of the delay time in the detonator according to actual needs, achieving compatibility between preset and field-set electronic detonators.

[0237] The embodiments described in this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided by the embodiments of this application. As those skilled in the art will know, with the evolution of technology and the emergence of new application scenarios, the technical solutions provided by the embodiments of this application are also applicable to similar technical problems.

[0238] Those skilled in the art will understand that the technical solutions shown in the figures do not constitute a limitation on the embodiments of this application, and may include more or fewer steps than shown, or combine certain steps, or different steps.

[0239] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs.

[0240] Those skilled in the art will understand that all or some of the steps in the methods disclosed above, as well as the functional modules / units in the systems and devices, can be implemented as software, firmware, hardware, or suitable combinations thereof.

[0241] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of the units described above is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0242] The units described above as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0243] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0244] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part 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 multiple 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 of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing programs, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0245] The preferred embodiments of the present application have been described above with reference to the accompanying drawings, but this does not limit the scope of the claims of the present application. Any modifications, equivalent substitutions, and improvements made by those skilled in the art without departing from the scope and substance of the embodiments of the present application shall be within the scope of the claims of the present application.

Claims

1. A method for compatibility with electronic detonators, characterized in that, The method includes: Determine the target identification code of the electronic detonator, wherein the target identification code is used to uniquely identify the electronic detonator, and the target identification code of the electronic detonator includes the segment code of the electronic detonator; The delay time of the electronic detonator is obtained according to the segment code and the preset relationship mapping table, wherein the relationship mapping table is used to indicate the correspondence between the segment code and the delay time; The detonation of the electronic detonator is adjusted according to the aforementioned delay time; The step of adjusting the detonation of the electronic detonator according to the delay time includes: A second initialization operation is performed on the detonator, wherein the second initialization operation includes at least one of initializing the communication voltage, initializing the detonation voltage, initializing the correspondence between the segment code and the delay time; Send a data retrieval request; If the target identifier and detonation code are received according to the data acquisition request, it is determined whether the delay time needs to be adjusted, and a first determination result is obtained; If the first judgment result indicates that the delay time needs to be adjusted, then it is determined whether the electronic detonator is used in a segmented manner, and a second judgment result is obtained. If the second judgment result indicates that the electronic detonator is used in a segmented manner, then the correspondence between the segment code and the delay time of the electronic detonator is modified. The delay time of the electronic detonator is calculated based on the segment code; Test the electronic detonator network; The delay time is calibrated, and the calibration result is written into the detonator; The electronic detonator is decoded according to the detonation code, and detonation is authorized. The determination of whether the delay time needs to be adjusted includes: Obtain indicator data for adjusting the delay time, wherein the indicator data includes at least one of the following: the insertion condition of the electronic detonator, rock hardness, borehole spacing, and charge amount; Based on the aforementioned indicator data, determine whether the delay time needs to be adjusted; Prior to adjusting the detonation of the electronic detonator according to the delay time, the method further includes registering the detonator, which is registered in the following manner: The detonator is subjected to a first initialization operation, wherein the first initialization operation includes at least one of initializing registration hole information, initializing the barcode scanning module, initializing registration voltage detection, and initializing current detection; The registration key's status is monitored, and the monitoring results are obtained. If the monitoring result indicates that the registration key has not been pressed, then the current surge is detected to obtain a second detection result; If the second detection result indicates that a current surge has been detected, then the target identification code is read. After successfully reading the target identifier code, the target identifier code is verified. After the target identification code is successfully verified, the electronic detonator is subjected to performance testing to obtain a third test result; If the third test result indicates that the performance of the electronic detonator is qualified, then the target identification code is parsed to obtain the tube code and segment code of the electronic detonator; The system displays a successful registration message.

2. The electronic detonator compatible method according to claim 1, characterized in that, The target identifier is obtained by updating the initial identifier, which is written into the electronic delay module of the electronic detonator in the following manner: Obtain preliminary data for the electronic delay module; The electronic delay module was subjected to performance testing, and the first test result was obtained. If the first detection result indicates that the electronic delay module is qualified, then the module serial number of the electronic delay module is added to 1 to obtain the target module serial number; The initial identification code is generated based on the preliminary data of the electronic delay module and the serial number of the target module; Write the initial identification code into the electronic extension module; After writing the initial identifier code into the electronic delay module, the initial identifier code after writing is read from the electronic delay module; The initial identifier code after writing is compared with the initial identifier code to obtain the comparison result; If the comparison result indicates that the initial identifier code after writing is consistent with the initial identifier code, then the electronic delay module is determined to be qualified and the writing of the initial identifier code is determined to be completed.

3. A method for compatibility with electronic detonators according to any one of claims 1 to 2, characterized in that, The determination of the target identification code for the electronic detonator includes: Based on the pre-acquired chip code, working capacitor code, detonating capacitor code, capacitor withstand voltage code, ignition component code, design version number, and PCB version number, generate key material codes; Based on the pre-obtained pipe factory code, machine number high digit, year high digit, year low digit and month concatenation result, production date, machine number low digit, box number code, and box serial number, generate the pipe code code; Obtain the module type, segment code, and check byte of the electronic detonator; The target identification code of the electronic detonator is determined based on the key material code, the module type, the segment code, the tube code, and the check byte.

4. A method for compatibility with electronic detonators according to any one of claims 1 to 2, characterized in that, The step of obtaining the delay time of the electronic detonator based on the segment code and a preset relational mapping table includes: Obtain the relationship mapping table; Obtain the segment code from the target identifier code; Based on the segment code, traverse the relation mapping table to find the delay time corresponding to the segment code.

5. An electronic detonator compatible system, characterized in that, The system is used to perform an electronic detonator-compatible method as described in any one of claims 1 to 4, the system comprising: The target identification code determination module is used to determine the target identification code of the electronic detonator, wherein the target identification code is used to uniquely identify the electronic detonator, and the target identification code of the electronic detonator includes the segment code of the electronic detonator; The delay time acquisition module is used to obtain the delay time of the electronic detonator according to the segment code and the preset relationship mapping table, wherein the relationship mapping table is used to indicate the correspondence between the segment code and the delay time; The detonation adjustment module is used to adjust the detonation of the electronic detonator according to the delay time.

6. An electronic device, characterized in that, The electronic device includes a memory and a processor, the memory storing a computer program, and the processor executing the computer program to implement an electronic detonator compatible method according to any one of claims 1 to 4.

7. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by the processor, it implements an electronic detonator compatible method according to any one of claims 1 to 4.

Images