Data burning method, device and equipment and medium

Abstract

The invention discloses a data burning method and device, equipment and a medium. The method comprises the steps of obtaining to-be-burnt production data corresponding to a to-be-burnt instrument, and determining a target instrument type and an instrument version in the to-be-burnt production data; determining a first file identifier based on the target instrument type and an instrument record file; determining to-be-burnt function data based on the first file identifier, the instrument version and the at least one function parameter file; and burning the to-be-burnt production data and the to-be-burnt function data into a memory of the to-be-burnt instrument. The problems that in the prior art, the effect is low and the accuracy is poor due to the fact that instrument information is manually input are solved, the instrument parameter management effect is improved, and meanwhile the effect of improving the instrument information burning accuracy and efficiency is achieved.

Description

Technical Field

[0001] The present invention relates to the field of computer processing technology, and in particular to a data burning method, device, equipment and medium. Background Art

[0002] As the requirements for the safety, stability, and functionality of surgical robots become higher and higher, different types of surgical instruments are usually attached to surgical robots and used as execution tools. Before using the surgical instruments, the relevant information of the instruments needs to be burned into the surgical instruments so that after the surgical robots are attached to the surgical instruments, they can accurately operate the surgical instruments through the relevant information of the instruments.

[0003] Currently, the method of burning instrument information into surgical instruments usually relies on manual input of the instrument information. This burning method requires manual input of the information of each instrument, which not only has the problem of low burning efficiency, but also is prone to information entry errors. Summary of the invention

[0004] The present invention provides a data burning method, device, equipment and medium, so as to improve the accuracy and efficiency of device information burning while improving the device parameter management effect.

[0005] According to one aspect of the present invention, a data burning method is provided, the method comprising:

[0006] Acquire the production data to be burned corresponding to the device to be burned, and determine the target device type and device version in the production data to be burned;

[0007] Determine a first file identifier based on the target device type and the device record file; wherein the device record file includes at least one device type record; the device type record is determined based on the device type and its corresponding file identifier;

[0008] Determining the function data to be burned based on the first file identifier, the device version and at least one function parameter file;

[0009] The production data to be burned and the functional data to be burned are burned into the memory of the device to be burned.

[0010] According to another aspect of the present invention, there is provided a data burning device, the device comprising:

[0011] A data acquisition module, used to acquire production data to be burned corresponding to the device to be burned, and determine the target device type and device version in the production data to be burned;

[0012] A first file identification determination module, configured to determine a first file identification based on the target device type and the device record file; wherein the device record file includes at least one device type record; and the device type record is determined based on the device type and its corresponding file identification;

[0013] A function data determination module, used for determining the function data to be burned based on the first file identifier, the device version and at least one function parameter file;

[0014] The burning module is used to burn the production data to be burned and the functional data to be burned into the memory of the device to be burned.

[0015] According to another aspect of the present invention, there is provided an electronic device, the electronic device comprising:

[0016] at least one processor; and a memory in communication with the at least one processor; wherein,

[0017] The memory stores a computer program executable by the at least one processor, and the computer program is executed by the at least one processor so that the at least one processor can execute the data burning method described in any embodiment of the present invention.

[0018] According to another aspect of the present invention, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a processor to implement the data burning method described in any embodiment of the present invention when executed.

[0019] According to another aspect of the present invention, a computer program product is provided, comprising a computer program, wherein when the computer program is executed by a processor, the data burning method according to any embodiment of the present invention is implemented.

[0020] The technical solution of the embodiment of the present invention obtains the production data to be burned corresponding to the device to be burned, and determines the target device type and device version in the production data to be burned; determines the first file identifier based on the target device type and the device record file; determines the functional data to be burned based on the first file identifier, the device version and at least one functional parameter file; burns the production data to be burned and the functional data to be burned into the memory of the device to be burned, thereby solving the problem of low effect and poor accuracy of manually entering device information in the prior art, and achieving the determination of the target device type and device version in the production data to be burned by using the production data to be burned corresponding to the device to be burned generated in the device production, and then locates the first file identifier from the device record file through the target device type, and then determines the functional data to be burned that is compatible with the first file identifier and the device version from at least one functional parameter file, and finally, burns the production data to be burned and the functional data to be burned into the memory of the device to be burned, thereby achieving effective management of the device functional data, improving the accuracy of device information burning, and improving the burning efficiency.

[0021] It should be understood that the contents described in this section are not intended to identify the key or important features of the embodiments of the present invention, nor are they intended to limit the scope of the present invention. Other features of the present invention will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0023] Figure 1 is a flow chart of a data burning method provided according to the first embodiment of the present invention;

[0024] Figure 2 is a schematic diagram of a data burning method provided in Embodiment 1 of the present invention;

[0025] Figure 3 is a schematic diagram for characterizing the document format in an instrument record file provided in Embodiment 1 of the present invention;

[0026] Figure 4 is a schematic diagram of a file identifier for characterizing a function parameter file provided according to the first embodiment of the present invention;

[0027] Figure 5 is a schematic diagram for characterizing a document format in a function parameter file provided in Embodiment 1 of the present invention;

[0028] Figure 6 is a structural schematic diagram of a data burning device provided according to Embodiment 2 of the present invention;

[0029] Figure 7 It is a structural schematic diagram of an electronic device for implementing the data burning method of an embodiment of the present invention. DETAILED DESCRIPTION

[0030] In order to enable those skilled in the art to better understand the scheme of the present invention, the technical scheme in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present invention.

[0031] It should be noted that the terms "first", "second", etc. in the specification and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present invention described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0032] Embodiment 1

[0033] Figure 1 This is a flow chart of a data burning method provided according to the first embodiment of the present invention. This embodiment is applicable to the case of burning device information into the memory of the device. The method can be executed by a data burning device. The data burning device can be implemented in the form of hardware and / or software. The data burning device can be configured in a computing device. Figure 1 As shown, the method includes:

[0034] S110, obtaining production data to be burned corresponding to the device to be burned, and determining the target device type and device version in the production data to be burned.

[0035] Among them, the instrument to be burned can refer to an instrument whose relevant information needs to be burned into its memory. The instrument can be a surgical instrument, such as a laparoscopic instrument, a hysteroscopic instrument, etc. The technical solution provided in this embodiment does not specifically limit the instrument. The production data to be burned can be data related to the instrument itself. The instrument type can be used to characterize the type of instrument gripper, such as, the instrument type includes but is not limited to a lens, a puncture device, a separation forceps, a titanium clamp, an aspirator head, an electrocoagulation forceps, and a disposable ultrasonic soft tissue surgical knife head, a needle holding forceps, an electrode electric hook, a bipolar Maryland forceps, a monopolar curved scissors, a monopolar straight scissors, a straight double-window non-invasive grasping forceps, a curved double-window non-invasive grasping forceps, a straight single-window invasive grasping forceps, a straight single-window non-invasive grasping forceps, a flat-head window bipolar forceps, a micro-non-invasive flat-head window bipolar forceps, etc. The instrument version can be used to characterize the update of the instrument or the historical modification record throughout the life cycle of the instrument. For example, the version of a certain instrument is "V02", which means that this is the second design update of the instrument.

[0036] In this embodiment, when data burning is required for a certain device, the device can be used as the device to be burned. At this time, the production data to be burned related to the device to be burned is obtained, and the target device type and device version of the device to be burned are extracted therefrom, so as to determine which functional parameters need to be burned based on the target device type and device version.

[0037] It should be noted that the production data to be burned corresponding to the devices to be burned of different device types or different device versions may be different. In other words, the production data to be burned corresponding to each device to be burned is different and not universal. In order to improve the convenience of device data burning, these production data to be burned related to the device to be burned itself can be placed together so that they can be directly obtained during burning. In this embodiment, obtaining the production data to be burned corresponding to the device to be burned includes: scanning the production identification information corresponding to the device to be burned, and reading the production data to be burned in the production identification information.

[0038] Among them, the production identification information may refer to the coding information used to store data. For example, the production identification information may be represented in the form of a QR code, a barcode, an image, etc. The production data to be burned also includes the project code, production code, life information, usage type, coating information and production date of the project to which the instrument to be burned belongs. The project code can be used to characterize the uniqueness of the project and to identify the project corresponding to the surgical instrument (for example, the project may be a surgical system of different versions). The production code can be used to identify the uniqueness of the surgical instrument to ensure that each instrument can be accurately tracked and managed. Life information can be used to characterize the duration for which the instrument can maintain its function or the number of times it can be used normally. The usage type can be used to characterize whether the instrument is a conventional surgical instrument (for normal surgical use) or a training surgical instrument (for training use). Coating information can be used to characterize whether the instrument is coated.

[0039] In this embodiment, the production data to be burned corresponding to each device to be burned can be stored in the production identification information in advance. After activating the device parameter burning software, the production identification information can be scanned with a scanning device scanner to read the device type, project code, production code, life information, usage type, coating information, device version, production date, device type, etc. in the production identification information, and the read information is used as the production data to be burned. For example, see Figure 2 The production identification information can be a surgical instrument production information QR code, and the production data to be burned can be obtained through the QR code.

[0040] The advantage of this setting is that you only need to enter information by scanning the QR code, without having to manually enter information or call in parameter files. You only need to check whether the device name, type, and version in the production data to be burned corresponds to the produced device, and you can burn it with one click, which improves the burning efficiency.

[0041] S120: Determine a first file identifier based on the target device type and the device record file.

[0042] Among them, the instrument record file can be a text document. The instrument record file includes at least one instrument type record. The instrument type record is determined based on the instrument type and its corresponding file identifier. The instrument type and its corresponding file identifier can be connected with an assignment operator, such as an equal sign. Different instrument type records can be separated by a separator, such as a comma. The file identifier can be based on a material code, a project code, and an instrument name. While the uniqueness of the instrument type is represented by a file identifier determined by a variety of information, it is convenient to manage information such as the material code, project code, and instrument name corresponding to the instrument type.

[0043] In this embodiment, the target device type can be used to search the device record file for a device type that matches the target device type. If so, the file identifier corresponding to the device type being searched can be used as the first file identifier to facilitate continued search for other device parameters of the device under the corresponding version through the first file identifier.

[0044] In order to improve the accuracy of the burned data, the production data to be burned can also be verified to obtain a verification result in the process of determining the first file identifier based on the target device type and the device record file; when the verification result is consistent with the preset result, the device record file is read based on the preset file path, and the first file identifier corresponding to the target device type is determined from at least one device type record in the device record file.

[0045] The first file identifier includes a material code, a project code, and a device name. The preset file path may refer to a storage location of a device record file, which may be composed of a drive letter and a file name. The preset result may be verification passed.

[0046] In this embodiment, the format, range, uniqueness, integrity, etc. of the production data to be burned can be verified to verify the correctness and legality of the data and obtain a verification result. If the verification result is that the verification is passed, the device record file stored in the preset file path can be retrieved and read. Further, it is possible to find out whether there is a device type record containing the target device type from at least one device type record in the read device record file. If so, the file identifier located after the assignment symbol in the searched device type record can be used as the first file identifier.

[0047] For example, see Figure 2 , you can create a text document with the suffix .txt in a specified location in the computer storage medium in advance, and use the text document to store the device type and the corresponding file identifier. The format of the file identifier can be material code_item code_device name to generate a device record file. Figure 3 As shown, the device type record in the device record file can be composed of the device type, the assignment symbol '=', the material code_item code_device name and the separator ','.

[0048] The advantage of this setting is that when the production data to be burned meets the preset format requirements, the first file identifier can be automatically queried from the pre-configured device record file through the target device type, so as to quickly locate the corresponding device function parameter file. At the same time, it is convenient to add or delete device types in the file to meet the burning needs of more types of devices.

[0049] S130: Determine the function data to be burned based on the first file identifier, the device version, and at least one function parameter file.

[0050] The function parameter file is used to store the function name of the device and the corresponding parameter value. It should be noted that the function parameters used by devices of different device types and versions are different.

[0051] Continue to see Figure 2 , all function parameter files can be collected in a folder. In this way, the first file identifier and the device version can be used to find out whether there is a function parameter file that matches the first file identifier and the device version in the folder. If so, the data stored in the found function parameter file can be read and the read data can be used as the function data to be burned.

[0052] In order to improve the accuracy and convenience of file positioning, in the process of determining the functional data to be burned based on the first file identifier, the device version and at least one functional parameter file: the first file identifier and the device version can be spliced ​​to obtain the target file identifier; based on the target file identifier and at least one functional parameter file, the target functional parameter file is determined; based on the target functional parameter file, the functional data to be burned is obtained.

[0053] Specifically, the device version can be spliced ​​to the back of the first file identifier to generate a target file identifier, so that the target file identifier is compatible with the naming format of the file name in the device function parameter folder. Then, find out whether there is a file consistent with the target file identifier from at least one function parameter file. If it exists, the consistent function parameter file can be used as the target function parameter file. Retrieve the function name and corresponding parameter value in the target function parameter file to obtain the function data to be burned. If the data is retrieved successfully, a successful retrieval prompt message is given in the form of a pop-up window; if the data fails to be retrieved, a retrieval failure prompt message is generated, and the reason for the failure is prompted.

[0054] For example, see Figure 4 , you can pre-collect the function parameter files of each device type and different versions of the device, and store them in the specified folder in the form of txt documents. The file name of the stored function parameter file can be composed of material code_item code_device name_version. The parameter record in the function parameter file consists of multiple function fields. The document format can be found in Figure 5 Each function field consists of a function name, an assignment symbol “=”, and a parameter value corresponding to the function name.

[0055] In other words, the collected folder is a collection of function parameter files of each device type and version. The material code, project code, device name and version number are used as file names to distinguish the function parameters of different types of devices, so as to facilitate the review and replacement of parameter files. There will be different versions of function parameters for the same device type, and the version number is used as a distinction to meet the needs of burning different versions of parameters in production and improve the effectiveness of device data management.

[0056] S140, burning the production data to be burned and the functional data to be burned into the memory of the device to be burned.

[0057] The memory may be a non-volatile medium, such as a ROM (read-only memory), a hard disk, and the like.

[0058] Continue to see Figure 2 , the parsing function can be called to parse the production data to be burned and the function data to be burned, and the function name and the corresponding parameter value in the production data to be burned, as well as the production data to be burned, can be burned into the memory of the device to be burned.

[0059] In order to ensure the correctness of data writing, the production data to be burned and the functional data to be burned can also be stored in a buffer storage address during the process of burning the production data to be burned and the functional data to be burned into the memory of the device to be burned; the buffer storage address includes at least two fields; the field includes multiple bytes; the byte includes device data and check byte bits; for each field, the multiple bytes in the field are checked in turn to obtain a check value, and the check value is stored in the check byte bit in the field; the stored data in the field in the buffer storage address is burned to the field in the memory of the device to be burned.

[0060] Among them, the buffer storage address can be a certain storage space reserved in the memory space. The check value is used to detect whether an error occurs during data transmission or storage. The device data includes production data to be burned and / or functional data to be burned. It should be noted that the device data can be production data to be burned and / or functional data to be burned, or it can be data after processing the production data to be burned and / or functional data to be burned. The check byte position can be the last few byte positions in the field, such as the last two or the last four bytes. The stored data includes device data and check values.

[0061] In this embodiment, the production data to be burned and the functional data to be burned can be arranged and compressed, and allocated and stored in the buffer storage address. The data in the buffer storage address is stored in multiple fields, and a verification method can be used to verify each byte in the field to obtain a verification value, and then the verification value can be stored in the verification byte position in the field. For example, the verification method can be a cyclic redundancy check (CRC) or other verification methods. It should be noted that the fields in the buffer storage address correspond to the fields in the memory of the device to be burned one by one. The stored data in the field in the buffer storage address can be stored in the field corresponding to the field in the memory of the device to be burned. For example, if the field in the buffer storage address is the first field, the stored data in the first field can be stored in the first field in the memory.

[0062] Exemplarily, the memory in the device is an EEPROM, in which internal data is stored in multiple fields. According to the fields in the buffer storage address, CRC check can be performed byte by byte by field, and the check value is stored in the last 2 bytes of the field.

[0063] In order to further improve the accuracy of data writing, the stored data in the field in the buffer storage address can be obtained during the process of burning the stored data in the field in the buffer storage address to the field in the memory of the device to be burned; the check value in the stored data is checked, and if the check passes, the stored data is burned to the field in the memory.

[0064] Specifically, in response to a data burning event, the stored data stored in the field in the buffer storage address can be retrieved, and the data format of the received stored data and the format of the stored data in the buffer storage address can be compared. If the formats are the same, it is possible to analyze whether the check value in the stored data is correct. If correct, it is considered that the check has passed, and the stored data can be burned into the field in the memory.

[0065] For example, see Figure 2 When the one-key burning button is pressed on the system interface, it is considered that the data burning event has been responded to. When it is determined that the received data format is the same as the data message format in the buffer storage address, the CRC check code (i.e., check value) of each stored data is analyzed to see if it is correct. If it is correct, the stored data is burned into the EEPROM chip (i.e., memory) of the device to be burned through the burning module. If it is incorrect or timed out, it will prompt that the serial communication has failed. It should be noted that the data can be transmitted through the RS232 serial port.

[0066] In this embodiment, after the production data to be burned and the functional data to be burned are burned into the memory of the device to be burned, the burned data burned into the memory can also be read; the burned data and the stored data in the buffer storage address are compared, and when the comparison result meets the preset conditions, a successful burning prompt message is generated and displayed.

[0067] Specifically, the burned data burned into the memory can be automatically read, and then the burned data and the stored data in the buffer storage address are compared. If the comparison is consistent, it is considered that the comparison result meets the preset conditions, and a burning success prompt message is generated and displayed. If the comparison is inconsistent, an abnormal prompt message is generated. The advantage of this setting is that the accuracy of the burning data can be ensured while the user is convenient to know the burning result.

[0068] For example, see Figure 2 , read the programmed data, and compare the read data with the stored data in the buffer storage address. If they are the same, it indicates that the programming is successful; if they are not the same, it indicates that the programming has failed.

[0069] In this embodiment, a new text box can be created on the target page to display the production data to be burned and the function data to be burned in the text box. The target page can be a display page for monitoring the data burning situation.

[0070] Specifically, a new text box can be created on the target page. When the production data and function data to be burned are obtained, these data can be stored in the text box for cache and displayed in the text box so that the user can know the data to be burned. For example, the device type, device life, and device version can be displayed on the display page.

[0071] It should be noted that during the burning process, the device type, project code, production code, life, version, training, coating, production date, burning date, burning data and other information are collected. In order to improve the management of device information, the burned production data and burned functional data can also be stored in the database. For example, the production code, life, version, device parameters and other information of each device can be stored in a database in a target file format (such as *.CSV) in a fixed format and row by row. *.CSV is set to read-only, which only allows the burning software to perform write operations and does not allow manual modification.

[0072] It should also be noted that before the device is burned, the device to be burned can also be hooked up to the burning device to detect whether the device to be burned has been hooked up and determine the hooking status. If the hooking status is that there is no device hooked up, there is no voltage output to the device power supply output terminal. When it is detected that the device is hooked up, the burning device will supply power to the device to be burned, and automatically turn off the power supply output after burning is completed to ensure the safety of the device plugging and unplugging.

[0073] The technical solution provided in this embodiment obtains the production data to be burned corresponding to the device to be burned, and determines the target device type and device version in the production data to be burned; determines the first file identifier based on the target device type and the device record file; determines the functional data to be burned based on the first file identifier, the device version and at least one functional parameter file; burns the production data to be burned and the functional data to be burned into the memory of the device to be burned, thereby solving the problem of low effect and poor accuracy in manually entering device information in the prior art, and achieving the determination of the target device type and device version in the production data to be burned by using the production data to be burned corresponding to the device to be burned generated in the device production, and then locates the first file identifier from the device record file through the target device type, and then determines the functional data to be burned that is compatible with the first file identifier and the device version from at least one functional parameter file, and finally, burns the production data to be burned and the functional data to be burned into the memory of the device to be burned, thereby achieving effective management of the device functional data, improving the accuracy of device information burning, and improving the burning efficiency.

[0074] Embodiment 2

[0075] Figure 6 1 is a schematic diagram of the structure of a data burning device provided according to the second embodiment of the present invention. Figure 6 As shown, the device includes: a data acquisition module 210, a first file identification determination module 220, a function data determination module 230 and a burning module 240.

[0076] Among them, the data acquisition module 210 is used to obtain the production data to be burned corresponding to the device to be burned, and determine the target device type and device version in the production data to be burned; the first file identification determination module 220 is used to determine the first file identification based on the target device type and the device record file; wherein the device record file includes at least one device type record; the device type record is determined based on the device type and its corresponding file identification; the function data determination module 230 is used to determine the function data to be burned based on the first file identification, the device version and at least one function parameter file; the burning module 240 is used to burn the production data to be burned and the function data to be burned into the memory of the device to be burned.

[0077] The technical solution of this embodiment obtains the production data to be burned corresponding to the device to be burned, and determines the target device type and device version in the production data to be burned; determines the first file identifier based on the target device type and the device record file; determines the functional data to be burned based on the first file identifier, the device version and at least one functional parameter file; burns the production data to be burned and the functional data to be burned into the memory of the device to be burned, thereby solving the problem of low effect and poor accuracy in the manual entry of device information in the prior art, and achieving the determination of the target device type and device version in the production data to be burned by using the production data to be burned corresponding to the device to be burned generated in the device production, and then locates the first file identifier from the device record file through the target device type, and then determines the functional data to be burned that matches the first file identifier and the device version from at least one functional parameter file, and finally, burns the production data to be burned and the functional data to be burned into the memory of the device to be burned, thereby achieving effective management of the device functional data, improving the accuracy of device information burning, and improving the burning efficiency.

[0078] Based on the above device, optionally, the data acquisition module 210 is used to scan the production identification information corresponding to the device to be burned, and read the production data to be burned in the production identification information; wherein, the production data to be burned also includes the project code, production code, life information, usage type, coating information and production date of the project to which the device to be burned belongs.

[0079] Based on the above device, optionally, the first file identification determination module 220 includes:

[0080] A verification result determination unit, used for verifying the production data to be burned and obtaining a verification result;

[0081] A first file identification determination unit is used to read the instrument record file based on a preset file path when the verification result is consistent with the preset result, and determine the first file identification corresponding to the target instrument type from at least one instrument type record in the instrument record file; wherein the first file identification includes a material code, a project code and an instrument name.

[0082] Based on the above device, optionally, the function data determination module 230 includes:

[0083] A target file identification determination unit, configured to concatenate the first file identification and the device version to obtain a target file identification;

[0084] a target function parameter file determining unit, configured to determine a target function parameter file based on the target file identifier and at least one function parameter file;

[0085] The function data to be burned determining unit is used to obtain the function data to be burned based on the target function parameter file.

[0086] Based on the above device, optionally, the burning module 240 includes:

[0087] A first cache unit is used to store the production data to be burned and the functional data to be burned in a buffer storage address; the buffer storage address includes at least two fields; the field includes a plurality of bytes; the bytes include device data and check bytes, and the device data includes the production data to be burned and / or the functional data to be burned;

[0088] A check value determination unit, for each of the fields, sequentially checking the device data in a plurality of bytes in the field to obtain a check value, and storing the check value in a check byte position in the field;

[0089] The burning unit is used for burning the stored data in the field in the buffer storage address into the field in the memory of the device to be burned.

[0090] Based on the above device, optionally, the burning unit includes:

[0091] a stored data determining unit, configured to obtain stored data in the field in the buffer storage address;

[0092] The verification unit is used to verify the verification value in the stored data, and when the verification passes, burn the stored data into the field in the memory.

[0093] On the basis of the above device, optionally, the device further includes:

[0094] A recorded data determination unit, used for reading the recorded data recorded in the memory;

[0095] The comparison unit is used to compare the burned data with the stored data in the buffer storage address, and when the comparison result meets the preset conditions, generate and display the burning success prompt information.

[0096] The data burning device provided in the embodiment of the present invention can execute the data burning method provided in any embodiment of the present invention, and has the corresponding functional modules and beneficial effects of the execution method.

[0097] Embodiment 3

[0098] Figure 7 1 is a schematic diagram of the structure of an electronic device for implementing the data burning method of an embodiment of the present invention. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workbenches, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices (such as helmets, glasses, watches, etc.) and other similar computing devices. The components shown herein, their connections and relationships, and their functions are only examples and are not intended to limit the implementation of the present invention described and / or required herein.

[0099] like Figure 7 As shown, the electronic device 10 includes at least one processor 11, and a memory connected to the at least one processor 11, such as a read-only memory (ROM) 12, a random access memory (RAM) 13, etc., wherein the memory stores a computer program that can be executed by at least one processor, and the processor 11 can perform various appropriate actions and processes according to the computer program stored in the read-only memory (ROM) 12 or the computer program loaded from the storage unit 18 to the random access memory (RAM) 13. In the RAM 13, various programs and data required for the operation of the electronic device 10 can also be stored. The processor 11, the ROM 12, and the RAM 13 are connected to each other through a bus 14. An input / output (I / O) interface 15 is also connected to the bus 14.

[0100] A number of components in the electronic device 10 are connected to the I / O interface 15, including: an input unit 16, such as a keyboard, a mouse, etc.; an output unit 17, such as various types of displays, speakers, etc.; a storage unit 18, such as a disk, an optical disk, etc.; and a communication unit 19, such as a network card, a modem, a wireless communication transceiver, etc. The communication unit 19 allows the electronic device 10 to exchange information / data with other devices through a computer network such as the Internet and / or various telecommunication networks.

[0101] The processor 11 may be a variety of general and / or special processing components with processing and computing capabilities. Some examples of the processor 11 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various dedicated artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, a digital signal processor (DSP), and any appropriate processor, controller, microcontroller, etc. The processor 11 executes the various methods and processes described above, such as a data burning method.

[0102] In some embodiments, the data burning method can be implemented as a computer program, which is tangibly contained in a computer-readable storage medium, such as a storage unit 18. In some embodiments, part or all of the computer program can be loaded and / or installed on the electronic device 10 via the ROM 12 and / or the communication unit 19. When the computer program is loaded into the RAM 13 and executed by the processor 11, one or more steps of the data burning method described above can be performed. Alternatively, in other embodiments, the processor 11 can be configured to perform the data burning method in any other appropriate manner (for example, by means of firmware).

[0103] Various implementations of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various implementations can include: being implemented in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which can be a special purpose or general purpose programmable processor that can receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device.

[0104] Computer programs for implementing the methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, so that when the computer program is executed by the processor, the functions / operations specified in the flow chart and / or block diagram are implemented. The computer program may be executed entirely on the machine, partially on the machine, partially on the machine and partially on a remote machine as a stand-alone software package, or entirely on a remote machine or server.

[0105] In the context of the present invention, a computer-readable storage medium may be a tangible medium that may contain or store a computer program for use by or in combination with an instruction execution system, device or equipment. A computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices or equipment, or any suitable combination of the foregoing. Alternatively, a computer-readable storage medium may be a machine-readable signal medium. A more specific example of a machine-readable storage medium may include an electrical connection based on one or more lines, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0106] To provide interaction with a user, the systems and techniques described herein may be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and a pointing device (e.g., a mouse or trackball) through which the user can provide input to the electronic device. Other types of devices may also be used to provide interaction with the user; for example, the feedback provided to the user may be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form (including acoustic input, voice input, or tactile input).

[0107] The systems and techniques described herein may be implemented in a computing system that includes backend components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes frontend components (e.g., a user computer with a graphical user interface or a web browser through which a user can interact with implementations of the systems and techniques described herein), or a computing system that includes any combination of such backend components, middleware components, or frontend components. The components of the system may be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: a local area network (LAN), a wide area network (WAN), a blockchain network, and the Internet.

[0108] A computing system may include a client and a server. The client and the server are generally remote from each other and usually interact through a communication network. The client and server relationship is generated by computer programs running on the corresponding computers and having a client-server relationship with each other. The server may be a cloud server, also known as a cloud computing server or cloud host, which is a host product in the cloud computing service system to solve the defects of difficult management and weak business scalability in traditional physical hosts and VPS services.

[0109] An embodiment of the present invention further provides a computer program product, including a computer program. When the computer program is executed by a processor, the data burning method provided by any embodiment of the present invention is implemented.

[0110] In the process of implementation, the computer program product can be written in one or more programming languages ​​or a combination thereof to perform the computer program code of the present invention, including object-oriented programming languages, such as Java, Smalltalk, C++, and conventional procedural programming languages, such as "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer can be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or can be connected to an external computer (for example, using an Internet service provider to connect through the Internet).

[0111] It should be understood that the various forms of processes shown above can be used to reorder, add or delete steps. For example, the steps described in the present invention can be executed in parallel, sequentially or in different orders, as long as the desired results of the technical solution of the present invention can be achieved, and this document does not limit this.

[0112] The above specific implementations do not constitute a limitation on the protection scope of the present invention. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions can be made according to design requirements and other factors. Any modification, equivalent substitution and improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims

1. A data burning method, characterized in that: include: Acquire the production data to be burned corresponding to the device to be burned, and determine the target device type and device version in the production data to be burned; Determine a first file identifier based on the target device type and the device record file; wherein the device record file includes at least one device type record; the device type record is determined based on the device type and its corresponding file identifier; Determining the function data to be burned based on the first file identifier, the device version and at least one function parameter file; The production data to be burned and the functional data to be burned are burned into the memory of the device to be burned.

2. The data burning method according to claim 1, characterized in that: The step of obtaining the production data to be programmed corresponding to the device to be programmed comprises: Scanning the production identification information corresponding to the device to be burned, and reading the production data to be burned in the production identification information; The production data to be burned also includes the project code, production code, life information, usage type, coating information and production date of the project to which the device to be burned belongs.

3. The data burning method according to claim 1, characterized in that: The determining of the first file identifier based on the target device type and the device record file includes: Verifying the production data to be burned to obtain a verification result; When the verification result is consistent with the preset result, based on the preset file path, reading the instrument record file, and determining a first file identifier corresponding to the target instrument type from at least one instrument type record in the instrument record file; Wherein, the first file identifier includes a material code, a project code and a device name.

4. The data burning method according to claim 1, characterized in that: The step of determining the function data to be burned based on the first file identifier, the device version and at least one function parameter file includes: Concatenating the first file identifier and the device version to obtain a target file identifier; Determining a target functional parameter file based on the target file identifier and at least one functional parameter file; Based on the target function parameter file, the function data to be burned is obtained.

5. The data burning method according to claim 1, characterized in that: The step of burning the production data to be burned and the functional data to be burned into the memory of the device to be burned comprises: The production data to be burned and the functional data to be burned are stored in a buffer storage address; the buffer storage address includes at least two fields; the field includes a plurality of bytes; the bytes include device data and check bytes, and the device data includes the production data to be burned and / or the functional data to be burned; For each of the fields, sequentially verify the device data in a plurality of bytes in the field to obtain a verification value, and store the verification value in a verification byte position in the field; The stored data in the field in the buffer storage address is burned into the field in the memory of the device to be burned.

6. The data burning method according to claim 5, characterized in that: The step of burning the stored data in the field in the buffer storage address into the field in the memory of the device to be burned comprises: Obtaining the stored data in the field in the buffer storage address; The check value in the stored data is checked, and if the check value passes, the stored data is burned into the field in the memory.

7. The data burning method according to claim 5, characterized in that: After burning the production data to be burned and the functional data to be burned into the memory of the device to be burned, the method further includes: Reading the data burned into the memory; The programmed data is compared with the stored data in the buffer storage address, and when the comparison result meets the preset condition, a prompt message of successful programming is generated and displayed.

8. A data burning device, characterized in that: include: A data acquisition module, used to acquire production data to be burned corresponding to the device to be burned, and determine the target device type and device version in the production data to be burned; A first file identification determination module, configured to determine a first file identification based on the target device type and the device record file; wherein the device record file includes at least one device type record; and the device type record is determined based on the device type and its corresponding file identification; A function data determination module, used for determining the function data to be burned based on the first file identifier, the device version and at least one function parameter file; The burning module is used to burn the production data to be burned and the functional data to be burned into the memory of the device to be burned.

9. An electronic device, characterized in that: The electronic device comprises: at least one processor; and a memory communicatively connected to the at least one processor; wherein, The memory stores a computer program executable by the at least one processor, and the computer program is executed by the at least one processor so that the at least one processor can execute the data burning method according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a processor to implement the data burning method according to any one of claims 1 to 7 when executed.

Images