A firmware update method, system, and control and interaction module for injection molding machines.

Abstract

This invention discloses a firmware update method, system, and control and interaction module for injection molding machines, relating to the field of injection molding machine control. The solution includes: when a mobile storage device is connected, determining whether the mobile storage device is properly connected based on a preset connection detection strategy; if properly connected, copying the file to be updated from the mobile storage device to memory, and determining whether there is a transmission anomaly based on a first verification strategy and the file to be updated in memory; if no transmission anomaly is found, writing the file to be updated from memory to non-volatile memory, and determining whether there is a write anomaly based on a second verification strategy and the file to be updated in non-volatile memory, thus confirming the update is complete. This solution improves the reliability of firmware updates in the high-temperature environment of injection molding machine operation through a multi-verification mechanism of correct connection, correct transmission, and correct writing, and relies on a mobile storage device to store the file to be updated, providing high update flexibility.

Description

Technical Field

[0001] This invention relates to the field of injection molding machine control technology, and in particular to a firmware update method, system, and control and interaction module for injection molding machines. Background Technology

[0002] Injection molding machines are typical industrial manufacturing equipment, mainly used for plastic melting and processing, or for the reuse of recycled plastics. They integrate a control and interaction module and multiple drives. The control and interaction module relies on internally stored firmware—software programs and operational data—to achieve precise control of each drive. In practical applications, the built-in firmware needs to be updated and upgraded according to engineering requirements. Currently, there are two main methods for firmware updates in injection molding machines: The first method is direct replacement, which involves removing the pluggable control and interaction module, reprogramming it via computer, and then replacing it. Alternatively, a control and interaction module with newly programmed firmware can be used to replace the original module. After power-off and power-on, it can be used. However, this method has the following drawbacks: First, the control and interaction module in the injection molding machine is installed in a metal frame, requiring the removal of structural components to access the hardware circuit board. Furthermore, the control and interaction module is relatively fragile, and improper handling can lead to damage, making this solution inflexible and risky. Second, when handling remotely, the updated control and interaction module needs to be shipped to the industrial site, which is difficult to maintain and costly.

[0003] The second method is to update the firmware using USB. This involves connecting the control and interaction module to a USB flash drive containing the firmware to be updated, then directly reading the data from the USB flash drive and overwriting the existing firmware in the Flash memory. However, this method has a drawback: because the production process requires melting the plastic, the working environment of the injection molding machine is usually at a high temperature. High temperatures can reduce hardware reliability, and various errors may occur during the update process, leading to firmware update failure.

[0004] Therefore, how to provide a more effective firmware update solution for injection molding machines is an urgent problem to be solved. Summary of the Invention

[0005] The problem solved by this invention is to provide a firmware update method, system and control and interaction module for injection molding machines. By relying on a multi-verification mechanism, the reliability of firmware updates is improved in the high-temperature environment of injection molding machine operation. Furthermore, by relying on a mobile storage device to store the files to be updated, the update is highly flexible.

[0006] To address the aforementioned technical problems, this application provides a firmware update method for injection molding machines, comprising: When it is determined that a mobile storage device is connected, the system determines whether the mobile storage device is connected normally based on a preset connection detection strategy; the mobile storage device stores files to be updated, and the files to be updated include firmware for this update and a first verification code; If the connection is successful, the file to be updated in the mobile storage device is copied to the memory, and the presence of any transmission abnormality is determined based on the first verification strategy and the file to be updated in the memory. If there is no transmission error, the file to be updated in the memory is written to the non-volatile memory. Based on the second verification strategy and the determination that there is no write error in the file to be updated in the non-volatile memory, the update is considered complete.

[0007] The beneficial effects of this invention are as follows: This solution improves the reliability of firmware updates in the high-temperature environment of injection molding machines through a multi-verification mechanism of correct connection, correct transmission, and correct writing. Furthermore, relying on mobile storage devices to store the files to be updated enhances update flexibility and facilitates practical industrial applications.

[0008] Furthermore, determining that the mobile storage device is normally connected based on a preset connection detection strategy includes: If the removable storage device is successfully identified, the directory of the removable storage device is read. If it is determined that the file to be updated exists in the directory, a first file is created in the mobile storage device, and the stored preset content is written into the first file; The first file is read, and if the preset content stored is consistent with the content recorded in the first file, the mobile storage device is determined to be normally connected.

[0009] Furthermore, the first verification code is a verification code determined by calculating the firmware using a first verification algorithm; Based on the first verification strategy, the file to be updated in memory is determined to have no transmission anomalies, including: The first verification algorithm is used to calculate the firmware under the file to be updated in the memory to determine the second verification code; If the second check code is found to be consistent with the first check code in the file to be updated in memory, it is determined that there is no transmission abnormality.

[0010] Furthermore, based on the second verification strategy, the determination that there is no write anomaly in the file to be updated in the non-volatile memory includes: Read the file to be updated from non-volatile memory; The first verification algorithm is used to calculate the firmware in the read file to be updated in order to determine the third verification code; If the third checksum matches the first checksum read from the file to be updated, it is determined that there is no write error.

[0011] Furthermore, when the mobile storage device is determined to be not properly connected based on a preset connection detection strategy, the alarm module outputs the corresponding first alarm information. And / or, when a transmission anomaly is determined based on the first verification strategy and the file to be updated in memory, the alarm module is controlled to output the corresponding second alarm information; And / or, when a write anomaly is determined in the file to be updated in the non-volatile memory based on the second verification strategy, the alarm module is controlled to output the corresponding third alarm information.

[0012] Furthermore, the firmware under the file to be updated in the memory is written to the storage location, which is the storage location of the original firmware in the non-volatile memory; Before copying the file to be updated from the removable storage device to memory, the process also includes: Back up the target critical files in the original firmware to obtain backup files; The backup file is stored in a backup storage location under the non-volatile memory, and the backup storage location is different from the storage location. Based on the third verification strategy, if the backup file in the backup storage location is determined to have no backup anomalies, the process proceeds to the step of copying the file to be updated from the removable storage device to memory.

[0013] Furthermore, the target critical files in the original firmware are backed up to obtain backup files, including: The fourth check code is determined by calculating the target key file in the original firmware using the second verification algorithm. The fourth verification code and the target key file are used as backup files; Based on the third verification strategy, the backup files at the backup storage location are determined to have no backup anomalies, including: Read the backup file from the backup storage location in the non-volatile memory; The second verification algorithm is used to calculate the target critical file in the read backup file to determine the fifth verification code; If the fifth check code matches the fourth check code in the read backup file, it is determined that there is no backup anomaly.

[0014] Furthermore, when a write anomaly is determined in the file to be updated in the non-volatile memory based on the second verification strategy, the following steps are taken: Delete the files that have been written to the non-volatile memory and are yet to be updated; The original firmware is restored using the backup file.

[0015] To address the aforementioned technical problems, the present invention also provides a firmware update system for injection molding machines, comprising: An access detection unit is used to determine whether a mobile storage device is properly connected based on a preset connection detection strategy when it is determined that a mobile storage device is connected. If the connection is properly connected, a copy and detection unit is triggered. The mobile storage device stores files to be updated, and the files to be updated include firmware for this update and a first verification code. The copy and detection unit is used to copy the file to be updated from the mobile storage device to the memory, and determine whether there is a transmission abnormality based on the first verification strategy and the file to be updated in the memory; if there is no transmission abnormality, the first write and detection unit is triggered. The first write and detection unit is used to write the file to be updated in the memory to a non-volatile memory, and determine that the update is complete when the file to be updated in the non-volatile memory is determined to have no write anomaly based on the second verification strategy.

[0016] To address the aforementioned technical problems, the present invention also provides a control and interaction module for an injection molding machine, including a memory, a non-volatile memory, and a controller; The controller is connected to the memory and the non-volatile memory respectively, and is used to perform the steps of the firmware update method for injection molding machines as described above. Attached Figure Description

[0017] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings: Figure 1 A flowchart of a firmware update method for an injection molding machine provided by the present invention; Figure 2 This is a schematic diagram of a firmware update system for an injection molding machine provided by the present invention. Detailed Implementation

[0018] The core of this invention is to provide a firmware update method, system, and control and interaction module for injection molding machines. Relying on a multi-verification mechanism, the reliability of firmware updates is improved in the high-temperature environment of injection molding machine operation. Furthermore, relying on a mobile storage device to store the files to be updated, the update is highly flexible.

[0019] To make the above-mentioned objects, features and advantages of the present invention more apparent and understandable, specific embodiments of the present invention will be described in detail below with reference to the accompanying drawings.

[0020] Please refer to Figure 1 , Figure 1 A flowchart of a firmware update method for an injection molding machine provided by the present invention.

[0021] The firmware update method for injection molding machines includes: S11: When it is determined that a mobile storage device is connected, determine whether the mobile storage device is connected normally based on the preset connection detection strategy; if it is connected normally, proceed to S12; wherein, the mobile storage device stores files to be updated, and the files to be updated include firmware used for this update and a first verification code; S12: Copy the file to be updated from the mobile storage device to memory, and determine whether there is a transmission error based on the first verification strategy and the file to be updated in memory; if there is no transmission error, proceed to S13; S13: Write the file to be updated in memory to non-volatile memory, and determine that the update is complete when there is no write error in the file to be updated in non-volatile memory based on the second verification strategy.

[0022] For injection molding machines, considering that they are mainly used for plastic melting and processing, or for the reuse of recycled plastics, the corresponding working environment temperature is usually high due to the production process of plastic melting. This makes the requirements for hardware reliability more stringent, especially when updating firmware. A more effective and reliable technical solution is needed to ensure that the firmware can be updated reliably, so that various processes such as plastic melting and processing can be completed by relying on the target firmware.

[0023] This embodiment provides a safe, economical, and reliable firmware update solution for injection molding machines. Specifically, this firmware update method can be applied to the control and interaction module in an injection molding machine. This control and interaction module can be understood as a human-machine interface module, which is equipped with a touch-screen display. The control and interaction module may also include a communication interface and function buttons. More specifically, the control and interaction module may also include a controller, memory, and non-volatile memory. An operating system is deployed under the controller; the specific type of operating system is not particularly limited here, but could be a Linux operating system. The non-volatile memory includes, but is not limited to, Flash memory, which is also not specifically limited here.

[0024] The firmware described in this application specifically includes software programs and related operational data. The software programs can be drive control programs corresponding to processes such as plastic melting and molding. To ensure secure firmware updates and upgrades, the aforementioned technical features are implemented. Furthermore, to accommodate flexible operation, the target firmware required for this update, along with the first verification code, is pre-stored as update files in a mobile storage device, allowing for flexible firmware updates as needed. Specifically, the mobile storage device includes, but is not limited to, a USB flash drive. The first verification code is determined by calculating the target firmware using a first verification algorithm, which includes, but is not limited to, the SHA256 algorithm.

[0025] Furthermore, step S11 aims to ensure that after the mobile storage device and the control and interaction module in the injection molding machine are connected, it confirms whether the hardware and software connections are normal. Only after ensuring a normal connection can step S12 be executed. Specifically, when the mobile storage device is plugged into the communication interface of the control and interaction module, it is determined that a mobile storage device is connected. Then, a preset connection detection strategy is used to determine whether the mobile storage device is properly connected. In some embodiments, when the preset connection detection strategy determines that the mobile storage device is not properly connected, the control alarm module outputs the corresponding first alarm information. This alarm module can be a display screen in the control and interaction module, displaying the corresponding first alarm information to remind technicians to replace the mobile storage device, check the physical link, etc. Of course, this alarm module can also be a voice broadcast module to issue alarms via voice. No particular limitation is made here; it is sufficient to flexibly output corresponding alarm information according to the actual application situation.

[0026] Step S12 is designed to copy the file to be updated from the mobile storage device to the target memory of the control and interaction module and perform a correctness check. If the check passes and there is no transmission error, step S13 will continue. Specifically, the file to be updated from the mobile storage device can be copied to a temporary directory in the target memory, such as / temp. Then, a first verification strategy is used to determine whether there is a transmission error. In some embodiments, when a transmission error is determined based on the first verification strategy and the file to be updated in the target memory, the alarm module is controlled to output the corresponding second alarm information. Similarly, the alarm module here can be the aforementioned display screen to output the corresponding second alarm information to remind technicians to verify the target firmware and / or checksum. In addition, when a transmission error is determined, the file to be updated in the temporary directory in the target memory can also be deleted.

[0027] Step S13 aims to write the file to be updated in the temporary directory of the target memory to non-volatile memory and perform a correctness check. If the check passes and there is no write error, the update is considered complete. It can be understood that after the injection molding machine restarts, the newly written target firmware in the non-volatile memory can be read and used for subsequent control, such as using the target firmware to complete various process controls such as plastic melting and molding. In some embodiments, when a write error is detected in the file to be updated in the target non-volatile memory based on the second verification strategy, the alarm module is controlled to output the corresponding third alarm information. Similarly, the alarm module here can be the aforementioned display screen to output the corresponding third alarm information to remind technicians to update again or check other links. In addition, after a write error is detected, the original firmware can be restored according to the backup logic described in the following embodiments, which will not be repeated here.

[0028] In summary, this application provides a firmware update method for injection molding machines. This method improves the reliability of firmware updates under the high-temperature environment of injection molding machines through a multi-verification mechanism of correct connection, correct transmission, and correct writing. Furthermore, relying on a mobile storage device to store the update file facilitates remote transmission. Combined with the aforementioned multi-verification mechanism, off-site maintenance is convenient and does not require disassembling the injection molding machine, improving update flexibility. This allows for subsequent control of various processes such as plastic melting and processing using the latest target firmware, which is beneficial for practical industrial applications. In addition, the multi-verification mechanism provides strong software reliability, appropriately reducing the requirements for hardware reliability and thus lowering hardware costs.

[0029] In some embodiments, determining that a mobile storage device is properly connected based on a preset connection detection strategy includes: If the removable storage device is successfully identified, read the directory of the removable storage device; If it is confirmed that there is a file to be updated in the directory, create a first file on the removable storage device and write the preset content stored in the first file; Read the first file. If the preset content stored is consistent with the content recorded in the first file, the mobile storage device is confirmed to be connected normally.

[0030] Specifically, reading the directory of the mobile storage device includes: the operating system attempts to identify the accessed mobile storage device and register it in the device list, thereby identifying the directory of the mobile storage device; after identifying the directory, it checks whether there are any files to be updated. If there are files to be updated, a first file is created on the mobile storage device (specifically in its directory). Since preset content for connection detection has been pre-set, the preset content is written into the first file. After writing is completed, the first file is read back into the operating system, and the read content is compared with the pre-stored preset content. If they are consistent, it is determined that the mobile storage device is normally connected.

[0031] More specifically, the process of creating the first file, writing the preset content, reading back to the operating system, and comparing the content can be repeated N1 times. Only when the content comparison results are consistent for N1 consecutive times can the mobile storage device be determined to be properly connected. This setting helps to avoid misjudgment caused by occasional factors such as momentary signal interference and unstable contact during a single connection detection, thereby improving the accuracy and reliability of determining the access status of the mobile storage device. Here, N1 is an integer greater than 1. For example, N1=3. In addition, during the above repetition process, if any content comparison result is inconsistent, or the mobile storage device cannot be identified, or the mobile storage device directory under the operating system cannot be formed, it is determined that the mobile storage device is not properly connected and the firmware update cannot be completed. At this time, the first alarm information can be output as described in the above embodiment.

[0032] In some embodiments, the first verification code is a verification code determined by calculating the firmware using a first verification algorithm; Based on the first verification strategy, it is determined that there are no transmission anomalies in the file to be updated in memory, including: The first verification algorithm is used to calculate the firmware under the file to be updated in memory to determine the second verification code; If the second checksum matches the first checksum in the file to be updated in memory, it is determined that there is no transmission anomaly.

[0033] Specifically, when it is determined that the second verification code is inconsistent with the first verification code under the file to be updated in the target memory, the process can return to the step of copying the file to be updated from the mobile storage device to the target memory, so as to reread and reuse the first verification strategy for verification. If the process is repeated N2 times without success, it is determined that there is a transmission abnormality, and then the file to be updated under the temporary directory in the target memory is deleted, and the corresponding second alarm information is output. Here, N2 is an integer greater than 1. For example, N2=3.

[0034] As can be seen, the above settings facilitate accurate and reliable detection of abnormal file transmission and fault-tolerant retry, ensuring reliable transmission of the file to be updated.

[0035] In some embodiments, based on a second verification strategy, determining that there is no write anomaly in the file to be updated in the non-volatile memory includes: Read the file to be updated from non-volatile memory; The third check code is determined by calculating the firmware in the read file to be updated using the first verification algorithm. If the third checksum matches the first checksum read from the file to be updated, it is determined that there is no write error.

[0036] Specifically, the target storage location in the non-volatile memory is a dedicated, fixed logical address allocated to the firmware, and the original firmware is stored in this target storage location; writing the file to be updated in the target memory into the target non-volatile memory means writing the target firmware under the file to be updated in the target memory into the aforementioned target storage location; in addition, the first check code can also be written into this target storage location, without any special limitation.

[0037] Subsequently, following the steps described above, the file to be updated is read and a third checksum is generated. If the third checksum matches the first checksum read, it is determined that there is no write anomaly. If the third checksum does not match the first checksum read from the file to be updated, the process can return to the step of writing the file to be updated in the target memory to the target non-volatile memory for rereading and reusing the second checksum strategy for verification. If the process is repeated N3 times without success, it is determined that there is a write anomaly. Subsequently, the original firmware can be restored according to the backup logic described in the following embodiments, which will not be repeated here. Here, N3 is an integer greater than 1. For example, N3 = 3.

[0038] In some embodiments, the firmware under the file to be updated in memory is written to a storage location, which is the storage location of the original firmware in non-volatile memory. Before copying the files to be updated from the removable storage device to memory, the process also includes: Back up the target critical files in the original firmware to obtain backup files; The backup file is stored in a backup storage location on non-volatile memory, and the backup storage location is different from the storage location; If the backup file in the backup storage location is determined to be without backup anomalies based on the third verification strategy, the process proceeds to copy the file to be updated from the removable storage device to memory.

[0039] In this embodiment, by backing up the target critical files in the original firmware, it is beneficial to restore the firmware when a write anomaly is detected. This enables the solution to implement a hierarchical, multi-verification mechanism of correct connection-correct backup-correct transmission-correct writing, forming a powerful error detection and recovery solution, and improving the reliability of firmware updates in the high-temperature environment of injection molding machine operation.

[0040] It should also be noted that the target key files mentioned here may include user data corresponding files, mold parameter corresponding files, custom files, key program files, etc., without any special limitations.

[0041] In some embodiments, target critical files in the original firmware are backed up to obtain backup files, including: The second verification algorithm is used to calculate the target key file in the original firmware to determine the fourth verification code; The fourth checksum and the target critical file are used as backup files; Based on the third verification strategy and the backup files at the backup storage location, it is determined that there are no backup anomalies, including: Read the backup file from the backup storage location in non-volatile memory; The second verification algorithm is used to calculate the target critical file in the read backup file to determine the fifth verification code; If the fifth checksum matches the fourth checksum in the read backup file, it is determined that there is no backup anomaly.

[0042] Specifically, the second verification algorithm here includes, but is not limited to, the MD5 algorithm; following the steps above, the backup file is read and the fifth verification code is calculated and generated. If the fifth verification code matches the read fourth verification code, it is determined that there is no backup anomaly; if the fifth verification code does not match the fourth verification code in the read backup file, the step of storing the backup file in the backup storage location under the target non-volatile memory can be returned to rewrite, reread, and reuse the third verification strategy for verification. If the verification fails after N4 repetitions, it is determined that there is a backup anomaly.

[0043] When a backup anomaly is detected, the backup file is deleted, and the alarm module is controlled to output the corresponding fourth alarm message to prompt the user to check the non-volatile memory or perform power-on / off initialization; the alarm module can be the display screen mentioned above.

[0044] In some embodiments, when a write anomaly is determined to exist in the file to be updated in non-volatile memory based on a second verification strategy, the following is included: Delete the files that have been written to non-volatile memory and are awaiting update; Restore the original firmware using the backup file.

[0045] Specifically, when a write anomaly is confirmed, on the one hand, the written files to be updated are deleted; on the other hand, the original firmware is restored using the backup file, that is, the backup file is written to the target storage location to restore the original firmware, so as to retain the original firmware to achieve various process controls such as plastic melting and molding. If it is still necessary to update the original firmware, after outputting the fourth alarm information and resolving the corresponding anomaly cause, the firmware update can be attempted again according to the method in this application. It should be noted that during this write process, the verification logic corresponding to the second verification strategy or the third verification strategy mentioned above can also be used to ensure that the write is correct, without any special limitations.

[0046] Please refer to Figure 2 , Figure 2 This is a schematic diagram of a firmware update system for an injection molding machine provided by the present invention.

[0047] The firmware update system for injection molding machines includes: Access detection unit 21 is used to determine whether a mobile storage device is properly connected based on a preset connection detection strategy when it is determined that a mobile storage device is connected; if it is properly connected, it triggers copy and detection unit 22; wherein, the mobile storage device stores files to be updated, and the files to be updated include firmware used for this update and a first verification code; The copy and detection unit 22 is used to copy the file to be updated from the mobile storage device to the memory, and determine whether there is a transmission abnormality based on the first verification strategy and the file to be updated in the memory; if there is no transmission abnormality, the first write and detection unit 23 is triggered. The first write and detection unit 23 is used to write the file to be updated in memory to non-volatile memory, and determine that the update is complete when the file to be updated in non-volatile memory does not have a write error based on the second verification strategy.

[0048] For the firmware update system for injection molding machines described in this application, please refer to the embodiments of the firmware update method for injection molding machines described above, which will not be repeated here.

[0049] In some embodiments, the access detection unit 21 includes: The first reading unit is used to read the directory of the mobile storage device when the mobile storage device is successfully identified; A creation unit is configured to create a first file in the removable storage device and write the stored preset content into the first file when it is determined that the file to be updated exists in the directory. The first comparison unit is used to read the first file, and when it is determined that the preset content stored is consistent with the content recorded in the first file, it determines that the mobile storage device is normally connected.

[0050] In some embodiments, the first verification code is a verification code determined by calculating the firmware using a first verification algorithm; the copying and detection unit 22 includes: The first calculation unit is used to calculate the firmware under the file to be updated in the memory using the first verification algorithm to determine the second verification code; The second comparison unit is used to determine that there is no transmission abnormality when it is determined that the second check code is consistent with the first check code under the file to be updated in the memory.

[0051] In some embodiments, the first write and detection unit 23 includes: The second read unit is used to read the file to be updated from non-volatile memory; The second calculation unit is used to calculate the firmware in the read file to be updated using the first verification algorithm to determine the third verification code. The third comparison unit is used to determine that there is no write anomaly when the third check code is consistent with the first check code read from the file to be updated.

[0052] In some embodiments, the firmware update system for an injection molding machine further includes: The first alarm unit is used to control the alarm module to output the corresponding first alarm information when it is determined based on a preset connection detection strategy that the mobile storage device is not properly connected. The second alarm unit is used to control the alarm module to output corresponding second alarm information when the file to be updated in memory is determined to have a transmission abnormality based on the first verification strategy. The third alarm unit is used to control the alarm module to output corresponding third alarm information when the file to be updated in the non-volatile memory is determined to have a write abnormality based on the second verification strategy.

[0053] In some embodiments, the firmware under the file to be updated in memory is written to a storage location, which is the storage location of the original firmware in the non-volatile memory; The firmware update system for injection molding machines further includes: The backup unit is used to back up the target critical files in the original firmware before copying the files to be updated from the mobile storage device to the memory, so as to obtain backup files; A storage unit is used to store the backup file to a backup storage location under the non-volatile memory, wherein the backup storage location is different from the storage location; The verification unit is used to trigger the copy and detection unit 22 when the backup file in the backup storage location is determined to be without backup anomalies based on the third verification strategy.

[0054] In some embodiments, the backup unit includes: The third calculation unit is used to calculate the target key file in the original firmware using the second verification algorithm to determine the fourth verification code. A backup file generation unit is used to use the fourth verification code and the target key file as backup files; The verification unit includes: The third reading unit is used to read backup files from the backup storage location in the non-volatile memory; The fourth calculation unit is used to calculate the target key file in the read backup file using the second verification algorithm to determine the fifth verification code; The fourth comparison unit is used to determine that there is no backup anomaly when the fifth check code is consistent with the fourth check code in the read backup file.

[0055] In some embodiments, the firmware update method for an injection molding machine includes: The deletion unit is used to delete the file to be updated that has been written in the non-volatile memory when the file to be updated in the non-volatile memory is determined to have a write anomaly based on the second verification strategy. The restore unit is used to restore the original firmware using the backup file.

[0056] The present invention also provides a control and interaction module for an injection molding machine, including a memory, a non-volatile memory, and a controller; The controller is connected to both memory and non-volatile storage to perform the steps of the firmware update method for injection molding machines as described above.

[0057] For the control and interaction module used in this application for the injection molding machine, please refer to the above embodiment of the firmware update method for the injection molding machine, which will not be repeated here.

[0058] While the disclosure is as stated above, its scope of protection is not limited thereto. Those skilled in the art can make various changes and modifications without departing from the spirit and scope of this disclosure, and all such changes and modifications will fall within the protection scope of this invention.

[0059] Furthermore, the various embodiments in this specification are described in a progressive manner, with each embodiment focusing on its differences from other embodiments. Similar or identical parts between embodiments can be referred to interchangeably. Relational terms such as "first" and "second" are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. The terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one" does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0060] Furthermore, the present invention is not to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A firmware update method for an injection molding machine, characterized in that, include: When it is determined that a mobile storage device is connected, the system determines whether the mobile storage device is connected normally based on a preset connection detection strategy. The mobile storage device stores files to be updated, including firmware for this update and a first verification code. If the connection is successful, the file to be updated in the mobile storage device is copied to the memory, and the presence of any transmission abnormality is determined based on the first verification strategy and the file to be updated in the memory. If there is no transmission error, the file to be updated in the memory is written to the non-volatile memory. Based on the second verification strategy and the determination that there is no write error in the file to be updated in the non-volatile memory, the update is considered complete.

2. The firmware update method for an injection molding machine as described in claim 1, characterized in that, Determining that the mobile storage device is properly connected based on a preset connection detection strategy includes: If the removable storage device is successfully identified, the directory of the removable storage device is read. If it is determined that the file to be updated exists in the directory, a first file is created in the mobile storage device, and the stored preset content is written into the first file; The first file is read, and if the preset content stored is consistent with the content recorded in the first file, the mobile storage device is determined to be normally connected.

3. The firmware update method for an injection molding machine as described in claim 1, characterized in that, The first verification code is a verification code determined by calculating the firmware using a first verification algorithm; Based on the first verification strategy, the file to be updated in memory is determined to have no transmission anomalies, including: The first verification algorithm is used to calculate the firmware under the file to be updated in the memory to determine the second verification code; If the second check code is found to be consistent with the first check code in the file to be updated in memory, it is determined that there is no transmission abnormality.

4. The firmware update method for an injection molding machine as described in claim 3, characterized in that, Based on the second verification strategy, the file to be updated in the non-volatile memory is determined to have no write anomalies, including: Read the file to be updated from non-volatile memory; The first verification algorithm is used to calculate the firmware in the read file to be updated in order to determine the third verification code; If the third checksum matches the first checksum read from the file to be updated, it is determined that there is no write error.

5. The firmware update method for an injection molding machine as described in claim 1, characterized in that, When the mobile storage device is determined to be not properly connected based on a preset connection detection strategy, the control alarm module outputs the corresponding first alarm information; And / or, when a transmission anomaly is determined based on the first verification strategy and the file to be updated in memory, the alarm module is controlled to output the corresponding second alarm information; And / or, when a write anomaly is determined in the file to be updated in the non-volatile memory based on the second verification strategy, the alarm module is controlled to output the corresponding third alarm information.

6. The firmware update method for an injection molding machine as described in any one of claims 1 to 5, characterized in that, The firmware under the file to be updated in the memory is written to the storage location, which is the storage location of the original firmware in the non-volatile memory; Before copying the file to be updated from the removable storage device to memory, the process also includes: Back up the target critical files in the original firmware to obtain backup files; The backup file is stored in a backup storage location under the non-volatile memory, and the backup storage location is different from the storage location. Based on the third verification strategy, if the backup file in the backup storage location is determined to have no backup anomalies, the process proceeds to the step of copying the file to be updated from the removable storage device to memory.

7. The firmware update method for an injection molding machine as described in claim 6, characterized in that, Back up the target critical files in the original firmware to obtain backup files, including: The fourth check code is determined by calculating the target key file in the original firmware using the second verification algorithm. The fourth verification code and the target key file are used as backup files; Based on the third verification strategy, the backup files at the backup storage location are determined to have no backup anomalies, including: Read the backup file from the backup storage location in the non-volatile memory; The second verification algorithm is used to calculate the target critical file in the read backup file to determine the fifth verification code; If the fifth check code matches the fourth check code in the read backup file, it is determined that there is no backup anomaly.

8. The firmware update method for an injection molding machine as described in claim 6, characterized in that, When a write anomaly is determined in the file to be updated in the non-volatile memory based on the second verification strategy, the following applies: Delete the files that have been written to the non-volatile memory and are yet to be updated; The original firmware is restored using the backup file.

9. A firmware update system for an injection molding machine, characterized in that, include: An access detection unit is used to determine whether a mobile storage device is properly connected based on a preset connection detection strategy when it is determined that a mobile storage device is connected. If the connection is successful, the copy and detection unit is triggered; wherein, the mobile storage device stores a file to be updated, the file to be updated includes firmware for this update and a first verification code; The copy and detection unit is used to copy the file to be updated from the mobile storage device to the memory, and determine whether there is a transmission abnormality based on the first verification strategy and the file to be updated in the memory; if there is no transmission abnormality, the first write and detection unit is triggered. The first write and detection unit is used to write the file to be updated in the memory to a non-volatile memory, and determine that the update is complete when the file to be updated in the non-volatile memory is determined to have no write anomaly based on the second verification strategy.

10. A control and interaction module for an injection molding machine, characterized in that, This includes memory, non-volatile storage, and the controller; The controller is connected to the memory and the non-volatile memory respectively, and is used to perform the steps of the firmware update method for an injection molding machine as described in any one of claims 1 to 8.

Images