Methods for batch upgrading remote I / O modules and remote I / O system

By acquiring device information and adding header information to data packets in a remote I/O system, automated batch upgrades of functional expansion modules are achieved, solving the problem of low firmware upgrade efficiency in existing technologies and improving upgrade efficiency.

CN123074928APending Publication Date: 2026-11-10SHANGHAI AIFUKEXIN ELECTRONICS CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202611426695.9
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2026-09-15
Publication Date
2026-11-10

AI Technical Summary

Technical Problem

The firmware upgrade efficiency of existing functional expansion modules is insufficient, and automated batch upgrades of similar modules cannot be achieved.

Method used

By acquiring device information from remote I/O couplers and function expansion modules, adding header information to data packets, and broadcasting them to the corresponding modules, automated firmware data distribution and assembly are achieved.

Benefits of technology

It enables automated batch upgrades of similar functional expansion modules without manual intervention, improving firmware upgrade efficiency.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123074928A_ABST
    Figure CN123074928A_ABST
Patent Text Reader

Abstract

This invention discloses a method and system for batch upgrading remote I / O modules. The method includes: acquiring device information sent by a remote I / O coupler; displaying the device information and receiving upgrade parameters selected by the user, including the target device type and target firmware version number; acquiring corresponding firmware data based on the target device type and target firmware version number; dividing the firmware data into multiple data packets, adding header information to each data packet, and sending them to the remote I / O coupler, so that the remote I / O coupler broadcasts the data packets to each functional expansion module. Through this method, the user only needs to select the target device type and target firmware version on a PC to trigger the PC to automatically complete firmware data acquisition, packetization, header information addition, and distribution, and the coupler automatically completes the broadcast distribution, realizing automated batch upgrading of similar functional expansion modules and improving the efficiency of firmware upgrades.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This invention belongs to the field of industrial automation control technology, specifically relating to a method for batch upgrading of remote I / O modules and a remote I / O system. Background Technology

[0002] In industrial automation control systems, remote I / O (Remote Input / Output) systems are a crucial component connecting field devices to the main control system. A typical remote I / O system consists of three main parts: a PC host computer (or PLC / DCS master station), a remote I / O coupler (also known as a bus coupler or gateway module), and multiple functional expansion modules (also known as I / O sub-modules). The remote I / O coupler communicates with the PC host computer via upper-level fieldbus protocols (such as PROFINET, EtherCAT, EtherNet / IP, Modbus TCP, CANopen, etc.) and exchanges data with downstream functional expansion modules via an internal bus (often including RS-485 and UART serial communication links). Functional expansion modules can be categorized by function into digital input modules (DI), digital output modules (DO), analog input modules (AI), analog output modules (AO), temperature control modules, high-speed counting modules, etc., and these modules are typically arranged sequentially in a plug-in or DIN rail configuration.

[0003] In practical engineering applications, the firmware of functional expansion modules needs to be upgraded periodically due to changes in on-site process requirements or the need to fix product firmware defects. Currently, there are several technical solutions for firmware upgrades of remote I / O functional expansion modules. The first method involves operators selecting individual functional expansion modules one by one through host computer software. The remote I / O coupler uses the internal bus to unicast address the functional expansion module, sending firmware data packet by packet to the specific module. After the module completes the upgrade and restarts, the same operation is repeated for the next module. The second method involves broadcasting firmware data. However, this often lacks a type matching and filtering mechanism on the functional expansion module side, making it difficult for it to independently determine whether to receive the broadcast data based on its own type. Therefore, manual intervention is still required for type identification and selection.

[0004] In summary, existing firmware upgrade technologies for functional expansion modules are significantly inefficient in terms of upgrade efficiency, and there is an urgent need for a solution that can automatically upgrade similar functional expansion modules in batches. Summary of the Invention

[0005] This invention application provides a method and system for batch upgrading remote I / O modules, aiming to at least partially solve the problem of insufficient firmware upgrade efficiency in existing functional expansion modules. To achieve the objectives of this invention application, the following technical solution is adopted: Firstly, a method for batch upgrading remote I / O modules is provided, the method being applied to a PC host computer, the method comprising: Obtain device information sent by the remote I / O coupler. The device information includes the coupler type of the remote I / O coupler and the device attribute information of each functional expansion module attached to the remote I / O coupler. Display the device information and receive upgrade parameters selected by the user, including the target device type and the target firmware version number; Based on the target device type and the target firmware version number, obtain the corresponding firmware data; The firmware data is divided into multiple data packets, and header information is added to each data packet before being sent to the remote I / O coupler, so that the remote I / O coupler broadcasts the data packets to each functional extension module, wherein the header information at least includes the target device type.

[0006] Secondly, a method for batch upgrading of remote I / O modules is provided, the method being applied to remote I / O couplers, the method comprising: Send device information to the PC host computer. The device information includes the coupler type of the remote I / O coupler and the device attribute information of each functional expansion module attached to the remote I / O coupler. Receive multiple data packets sent by the PC host computer, wherein the multiple data packets are obtained by the PC host computer after dividing the firmware data, and each data packet contains header information, the header information at least containing the target device type; Parse the header information to extract the target device type; Distribution discrimination is performed based on the target device type. If the target device type matches the coupler type, the multiple data packets are assembled into firmware data and written to the local storage area of ​​the remote I / O coupler. If the target device type does not match the coupler type, each data packet is broadcast to each functional extension module.

[0007] Thirdly, a method for batch upgrading remote I / O modules is provided, the method being applied to a function expansion module, the method comprising: Report the device attribute information of this function extension module to the remote I / O coupler; Receive multiple data packets broadcast by the remote I / O coupler. The multiple data packets are obtained by the PC host computer after dividing the firmware data. Each of the data packets contains header information, and the header information contains at least the target device type. Parse the header information to extract the target device type; Compare the target device type with the device type of this functional expansion module; If the comparison matches, the multiple data packets are assembled into the firmware data and written to the local storage area of ​​this function extension module; If the comparison does not match, each data packet is discarded.

[0008] Fourthly, a remote I / O system is provided, including a PC host computer, a remote I / O coupler, and multiple functional expansion modules, wherein: The PC host computer is used to acquire device information sent by the remote I / O coupler. The device information includes the coupler type of the remote I / O coupler and the device attribute information of each functional expansion module attached to the remote I / O coupler. It displays the device information and receives upgrade parameters selected by the user. The upgrade parameters include the target device type and the target firmware version number. Based on the target device type and the target firmware version number, it acquires the corresponding firmware data. The firmware data is divided into multiple data packets, and header information is added to each data packet before being sent to the remote I / O coupler, so that the remote I / O coupler broadcasts the data packets to each functional expansion module. The header information at least includes the target device type. The remote I / O coupler is used to send device information to a PC host computer; receive multiple data packets sent by the PC host computer; parse the header information and extract the target device type; perform distribution discrimination based on the target device type, wherein if the target device type matches the coupler type, the multiple data packets are assembled into firmware data and written to the local storage area of ​​the remote I / O coupler; if the target device type does not match the coupler type, the data packets are broadcast to each functional extension module. The functional extension module is used to report its device attribute information to the remote I / O coupler; receive multiple data packets broadcast by the remote I / O coupler; parse the header information and extract the target device type; compare the target device type with the device type of the functional extension module; if the comparison is consistent, assemble the multiple data packets into firmware data and write it to the local storage area of ​​the functional extension module; if the comparison is inconsistent, discard each data packet.

[0009] Compared with the prior art, the beneficial technical effects of this invention application are as follows: The remote I / O module batch upgrade method provided in this application includes: obtaining device information sent by a remote I / O coupler, the device information including the coupler type of the remote I / O coupler and the device attribute information of each functional expansion module attached to the remote I / O coupler; displaying the device information and receiving upgrade parameters selected by the user, the upgrade parameters including the target device type and the target firmware version number; obtaining the corresponding firmware data according to the target device type and the target firmware version number; dividing the firmware data into multiple data packets, adding header information to each data packet, and sending them to the remote I / O coupler, so that the remote I / O coupler broadcasts the data packets to each functional expansion module, wherein the header information at least includes the target device type. This method allows users to simply select the target device type and target firmware version on a PC host computer to trigger the PC host computer to automatically complete firmware data acquisition, packetization, header information addition, and distribution. The coupler then automatically completes the broadcast distribution. The entire process does not require initiating an upgrade process for each module individually, does not require manual tracking of upgraded and non-upgraded modules, and does not require manual intervention in type identification and filtering. It achieves automated batch upgrades of similar functional extension modules, thus improving the efficiency of firmware upgrades and solving the problems of existing technologies. Attached Figure Description

[0010] To more clearly illustrate the technical solutions in the embodiments of this invention, the drawings used in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this invention. For those skilled in the art, other drawings can be obtained from these drawings without creative effort.

[0011] Figure 1 This is a schematic diagram of the structure of a remote I / O system according to an embodiment of this invention. Figure 2 This is a schematic diagram illustrating the specific process of a remote I / O module batch upgrade method according to an embodiment of this invention. Figure 3 This is a schematic diagram illustrating the specific process of a remote I / O module batch upgrade method according to another embodiment of the present invention. Figure 4 This is a schematic diagram illustrating the specific process of a remote I / O module batch upgrade method according to another embodiment of the present invention. Figure 5 This is a schematic diagram illustrating the specific process of a remote I / O module batch upgrade method according to another embodiment of the present invention.

[0012] The accompanying drawings are provided to further understand the present invention and form part of the specification. They are used together with the embodiments of the present invention to explain the present invention and do not constitute a limitation thereof. Detailed Implementation

[0013] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without creative effort are within the scope of protection of the present invention.

[0014] As shown in the present invention application and claims, unless the context clearly indicates otherwise, the words "a," "an," "an," and / or "the" do not specifically refer to the singular and may also include the plural. Generally speaking, the terms "comprising" and "including" only indicate that explicitly identified steps and elements are included, and "multiple" includes one, two, or more, and these steps and elements do not constitute an exclusive list; the method or apparatus may also include other steps or elements.

[0015] While this application makes various references to certain modules of the system according to embodiments of the present invention, any number of different modules can be used and run on user terminals and / or servers. The modules are merely illustrative, and different aspects of the system and method may use different modules.

[0016] This application uses flowcharts to illustrate the operations performed by the system according to embodiments of the present invention. It should be understood that the preceding or following operations are not necessarily performed in exact order. Instead, various steps can be processed in reverse order or simultaneously, as needed. Furthermore, other operations can be added to these processes, or one or more steps can be removed from them.

[0017] Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings. Obviously, the described embodiments are merely a part of the embodiments of the present invention, and not all of the embodiments of the present invention. It should be understood that the present invention is not limited to the exemplary embodiments described herein.

[0018] It is worth noting that in this invention application, all data acquisition actions are carried out in compliance with the relevant data protection laws and policies of the country where the location is located, and with the authorization granted by the owner of the relevant device.

[0019] In view of the above-mentioned technical problems, embodiments of this application provide a method for batch upgrading remote I / O modules and a remote I / O system, which can be used to solve the problems of the prior art. The structure of the remote I / O system can be described first, such as... Figure 1The diagram shows the specific structure of the remote I / O system, which includes a PC host computer 1, a remote I / O coupler 2, and multiple functional expansion modules 3. The remote I / O coupler 2 can communicate with the PC host computer 1 via an upper-layer fieldbus protocol and communicate with the downstream functional expansion modules 3 via an internal bus.

[0020] The PC host computer 1 is used to obtain device information sent by the remote I / O coupler 2. The device information includes the coupler type of the remote I / O coupler 2 and the device attribute information of each functional expansion module 3 attached to the remote I / O coupler 2. It displays the device information and receives the upgrade parameters selected by the user. The upgrade parameters include the target device type and the target firmware version number. Based on the target device type and the target firmware version number, it obtains the corresponding firmware data. It divides the firmware data into multiple data packets, adds header information to each data packet, and sends them to the remote I / O coupler 2 so that the remote I / O coupler 2 broadcasts the data packets to each functional expansion module 3. The header information includes at least the target device type. The remote I / O coupler 2 is used to send device information to the PC host computer 1; receive multiple data packets sent by the PC host computer 1; parse the header information and extract the target device type; perform distribution discrimination according to the target device type, wherein if the target device type matches the coupler type, the multiple data packets are assembled into firmware data and written to the local storage area of ​​the remote I / O coupler 2; if the target device type does not match the coupler type, the data packets are broadcast to each functional expansion module 3. The function extension module 3 is used to report the device attribute information of this function extension module to the remote I / O coupler 2; receive multiple data packets broadcast by the remote I / O coupler 2; parse the header information and extract the target device type; compare the target device type with the device type of this function extension module; if the comparison is consistent, assemble the multiple data packets into firmware data and write it to the local storage area of ​​this function extension module 3; if the comparison is inconsistent, discard each data packet.

[0021] like Figure 2 The diagram shown is a detailed flowchart of the remote I / O module batch upgrade method provided in this application embodiment. This method can be applied to... Figure 1 The PC host computer in the remote I / O system shown in the diagram, the method includes the following steps: Step S41: Obtain the device information sent by the remote I / O coupler. The device information includes the coupler type of the remote I / O coupler and the device attribute information of each functional expansion module attached to the remote I / O coupler.

[0022] In practical applications, not only do functional expansion modules require firmware upgrades, but in some cases, remote I / O couplers also need firmware upgrades. Therefore, this device information can include not only the coupler type of the remote I / O coupler, but also the device attribute information of each functional expansion module connected to the remote I / O coupler. The coupler type can include support for multiple protocols: Ethernet / IP, CAN, EtherCAT, PROFINET, etc. The device attribute information of the functional expansion modules can at least include module type information to identify the module's functional category, version information to identify the current firmware version of the module (i.e., the functional expansion module), and address identification information to uniquely identify each module on the bus. The module type information can include, for example, digital input modules, digital output modules, analog input modules, analog output modules, temperature control modules, high-speed counting modules, etc., and the address identification information can be, for example, a station number.

[0023] In practical applications, step S41 can be implemented by pre-setting an operating cycle, which allows the PC host computer to periodically execute step S41 according to the operating cycle to obtain device information sent by the remote I / O coupler. Alternatively, the PC host computer can first send a device information synchronization request to the remote I / O coupler through an interface. In this way, the remote I / O coupler can report the device information to the PC host computer based on the device information synchronization request, thereby enabling the PC host computer to obtain the device information.

[0024] Step S42: Display the device information and receive the upgrade parameters selected by the user, including the target device type and the target firmware version number.

[0025] After obtaining device information, the PC host computer can directly display this information. For example, it can display the device information through its own device management interface, such as in a tree-like list format, making it easy for users to view. In practical applications, after viewing the device information, users can operate it using touch buttons on the device management interface or by selecting with the mouse. This allows them to specify firmware upgrades for various functional extension modules of the target device type, and upgrade the firmware version to the version indicated by the target firmware version number.

[0026] In this way, after the user selects the target device type and target firmware version number through operation, the PC host computer can further receive the upgrade parameters selected by the user, that is, the target device type and target firmware version number.

[0027] It should be further explained that after displaying the device information, considering the potentially large number and versions of firmware extension modules, direct searching from a vast amount of information would be inefficient for users. Therefore, a filtering module can be set up in the device management interface. Users can input filtering criteria in the filter input box, which can include at least one of the following: device type and firmware version number. The PC host computer can then receive the user's input filtering criteria, filter out matching extension modules from the device information based on these criteria, and display the filtering results. This allows users to view the filtering results and further select the target device type and target firmware version number from the filtered results.

[0028] Step S43: Obtain the corresponding firmware data based on the target device type and target firmware version number.

[0029] After obtaining the upgrade parameters through step S42, in step S43, the PC host computer can further retrieve the corresponding firmware data based on the target device type and target firmware version number in the upgrade parameters. In practical applications, firmware data is usually stored in the PC host computer's database, and for ease of retrieval, this firmware data is often categorized according to device type and version number. Furthermore, considering data security, this firmware data is usually encrypted into encrypted firmware files.

[0030] Therefore, in step S43, the corresponding encrypted firmware file can be obtained by searching or other means based on the target device type and the target firmware version number. Then, the encrypted firmware file can be decrypted to obtain the corresponding firmware data in step S43.

[0031] Step S44: Divide the firmware data into multiple data packets, add header information to each data packet, and send them to the remote I / O coupler so that the remote I / O coupler can broadcast the data packets to each functional extension module.

[0032] In practical applications, considering that firmware data is usually quite large, sending it all at once could easily lead to communication congestion. Therefore, in step S44, the firmware data can be divided into multiple data packets. For example, it can be divided into multiple data packets evenly, or other division methods can be used to divide the firmware data into multiple data packets. Header information is added to each data packet, and this header information at least includes the target device type, thereby instructing the functional extension module of that target device type to perform a firmware upgrade. These data packets can then be sent to a remote I / O coupler, enabling the remote I / O coupler to broadcast the data packets to each functional extension module.

[0033] Furthermore, considering that these data packets are derived from firmware data, and firmware upgrades require complete firmware data (i.e., the firmware data for the target firmware version number mentioned above), these data packets also need to be reassembled to generate the final firmware data. To facilitate this reassembly, the header information can also include the total number of packets and the sequence number of each packet, allowing for reassembly based on this total number and the sequence number of each packet. The total number of packets indicates the total number of data packets from which the firmware data is derived.

[0034] It should be noted that since functional expansion modules are typically installed in control cabinets in industrial settings, and production lines are often in continuous operation, firmware upgrades for these modules may cause production interruptions. In practice, firmware upgrades are usually performed during production breaks, such as holidays. Therefore, to control the timing of firmware upgrades, this application embodiment also provides two firmware upgrade modes (also known as update timeliness modes): real-time mode and delayed mode. The real-time mode indicates that firmware activation is performed immediately upon receiving the firmware data; the delayed mode indicates that firmware activation is performed after a preset delay period. This means that firmware activation is not performed immediately after receiving the firmware data, but only after the preset delay period has elapsed. This delayed mode allows for firmware upgrades on continuously operating production lines, avoiding production interruptions.

[0035] The preset delay duration can be set by the user according to actual needs, such as 3 hours, 4 hours, 5 hours or other durations. A countdown timer is set inside the remote I / O coupler or in other unit modules of the remote I / O system of this application to count down the preset delay duration, thereby determining whether the preset delay duration has been reached.

[0036] Therefore, in this embodiment, in step S42 above, the user can further select an update timeliness mode in the device management interface, such as specifying a real-time mode or a delayed mode. Thus, the upgrade parameters can also include the update timeliness mode. Furthermore, the update timeliness mode can be added to the header information, facilitating subsequent functional expansion modules to parse the update timeliness mode from the header information and select the firmware upgrade time based on the update timeliness mode.

[0037] Of course, the update timeliness mode can also be omitted from this header information, and the update timeliness can be directly controlled by the PC host computer. For example, if it is real-time mode, when sending these data packets, the firmware upgrade command is directly issued to control the direct activation of firmware data and perform firmware upgrade; if it is delayed mode, the update mode start command can be issued after the preset delay time is reached, and then these data packets are sent and the firmware data is activated to perform firmware upgrade.

[0038] In addition, after the PC host computer sends each data packet to the remote I / O coupler, it can further statistically analyze the upgrade results. Therefore, the method can further include receiving the upgrade result information reported by the remote I / O coupler and displaying this information, making it convenient for users to view the upgrade result information. This upgrade result information can include a list of successfully upgraded modules and / or information on modules that failed to upgrade. The information on modules that failed to upgrade includes at least the station number of the failed modules (i.e., the various functional expansion modules that failed to upgrade). The list of successfully upgraded modules can be displayed as a list of the successfully upgraded functional expansion modules.

[0039] The remote I / O module batch upgrade method provided in this application includes: obtaining device information sent by a remote I / O coupler, the device information including the coupler type of the remote I / O coupler and the device attribute information of each functional expansion module attached to the remote I / O coupler; displaying the device information and receiving upgrade parameters selected by the user, the upgrade parameters including the target device type and the target firmware version number; obtaining the corresponding firmware data according to the target device type and the target firmware version number; dividing the firmware data into multiple data packets, adding header information to each data packet, and sending them to the remote I / O coupler, so that the remote I / O coupler broadcasts the data packets to each functional expansion module, wherein the header information at least includes the target device type. This method allows users to simply select the target device type and target firmware version on a PC host computer to trigger the PC host computer to automatically complete firmware data acquisition, packetization, header information addition, and distribution. The coupler then automatically completes the broadcast distribution. The entire process does not require initiating an upgrade process for each module individually, does not require manual tracking of upgraded and non-upgraded modules, and does not require manual intervention in type identification and filtering. It achieves automated batch upgrades of similar functional extension modules, thus improving the efficiency of firmware upgrades and solving the problems of existing technologies.

[0040] Based on the above Figure 2 The present application also provides a method for batch upgrading remote I / O modules, which shares the same inventive concept as the method shown in the example. Figure 3 The diagram shown illustrates the specific process of this method, which can be applied to... Figure 1The remote I / O coupler in the remote I / O system shown herein, the method includes the following steps: Step S51: Send device information to the PC host computer.

[0041] Please refer to step S41 above; it will not be repeated here.

[0042] Step S52: Receive multiple data packets sent by the PC host computer.

[0043] Each data packet is obtained by the PC host computer after dividing the firmware data, and each data packet contains header information, which at least includes the target device type.

[0044] Referring to step S44 above, the PC host computer can divide the firmware data into multiple data packets, add header information to each data packet, and send them to the remote I / O coupler. In this way, the remote I / O coupler can receive each data packet sent by the PC host computer.

[0045] Step S53: Parse the header information and extract the target device type.

[0046] In step S53, after receiving each data packet, the remote I / O coupler can parse the header of these data packets and then extract the target device type.

[0047] Step S54: Perform distribution discrimination based on the target device type. If the target device type matches the coupler type, assemble each data packet into firmware data and write it to the local storage area of ​​the remote I / O coupler. If the target device type does not match the coupler type, broadcast each data packet to each functional extension module.

[0048] After obtaining the target device type through step S53, in step S54, the remote I / O coupler can first match the target device type with its own coupler type. If the target device type matches its own coupler type, it indicates that a firmware upgrade is needed. Therefore, the various data packets can be assembled into firmware data and written to the local storage area of ​​the remote I / O coupler. For example, the total number of packets and the sequence number of each data packet in the header information can be used to reassemble these data packets to obtain the firmware data, which can then be written to the local storage area.

[0049] In practical applications, to facilitate data management in the local storage area of ​​the remote I / O coupler, the local storage area is typically divided into an update parameter area, a first firmware area, and a second firmware area. The update parameter area stores update flags, the first firmware area stores currently running firmware data, and the second firmware area stores firmware data to be activated. Therefore, writing firmware data to the local storage area of ​​the remote I / O coupler can be done by writing the firmware data to the second firmware area, thus awaiting activation. The update flag is used to indicate whether the second firmware area stores firmware data to be activated. Alternatively, the header information of each data packet can also be stored in the update parameter area.

[0050] For example, after assembling the firmware data, the firmware data can be written to the second firmware area, and the storage update flag of the update parameter area can be updated to indicate that the second firmware area stores firmware data to be activated, and the header information can also be written to the update parameter area.

[0051] For example, as mentioned above, this header information also includes an update timeliness flag. In this case, if the target device type matches the coupler type, after receiving and assembling all data packets, the activation operation can be performed based on the update timeliness flag. For instance, if the update timeliness flag indicates real-time mode, the firmware activation process is executed immediately; if the update timeliness flag indicates delayed mode, the firmware activation process is executed after the preset delay duration is reached. The firmware activation process may include restarting this module (in this case, the remote I / O coupler) and entering the Bootload program; then, the Bootload program checks the update flag in the update parameter area; if the update flag is valid, the firmware data to be activated in the second firmware area of ​​the local storage area is copied to the first firmware area, thereby overwriting the currently running firmware data; then the update flag is deleted, and the firmware data in the first firmware area is started.

[0052] Of course, if the target device type does not match its own coupler type, it means that it does not need to upgrade its own firmware, but the function expansion module needs to be upgraded. Therefore, these data packets can be broadcast to each function expansion module. For example, each data packet can be sent to each function expansion module in a broadcast manner through the internal bus.

[0053] As mentioned above, in order to control the firmware upgrade time, one approach is to place the update time mode in the header information of the data packet, so that the update time mode can be extracted from the header information of the data packet to determine the firmware upgrade time. Another approach is not to place the update time mode in the header information of the data packet, but to have the PC host computer issue a start update mode command after a preset delay time. Therefore, the method can also include receiving the start update mode command sent by the PC host computer, and then responding to the start update mode command to start the update mode. In this update mode, I / O data polling with the upper-layer master station is suspended to avoid data loss, and the firmware activation process is executed to upgrade the firmware.

[0054] The method provided in this application embodiment, after broadcasting these data packets to each functional expansion module, may further include receiving update completion packets reported by each functional expansion module, wherein the update completion packet contains the station number of the corresponding functional expansion module, and then generating a list of modules that have been successfully upgraded based on these update completion packets.

[0055] Of course, in practical applications, some functional expansion modules may fail to upgrade. In this case, if no update completion package is received from the functional expansion module within the preset timeout window, it indicates that the upgrade of that functional expansion module has failed. Within this timeout window, for functional expansion modules of the target device type that have not received the update completion package, corresponding upgrade failure information can be generated. Then, the list of successfully upgraded modules and the information of the failed modules can be further combined to generate upgrade result information, which is then sent to the PC host computer.

[0056] Obviously Figure 3 The method shown can also solve the problems in the prior art, which will not be elaborated here.

[0057] Based on the above Figure 1 and Figure 2 The present application also provides a method for batch upgrading remote I / O modules, which shares the same inventive concept as the method shown in the example. Figure 4 The diagram shown illustrates the specific process of this method, which can be applied to... Figure 1 The method for a remote I / O system, which includes a functional expansion module (e.g., any functional expansion module), comprises the following steps: Step S61: Report the device attribute information of this function extension module to the remote I / O coupler.

[0058] This step can refer to steps S41 and S51 above, and will not be repeated here.

[0059] Step S62: Receive multiple data packets broadcast by the remote I / O coupler.

[0060] These data packets are obtained by the PC host computer after dividing the firmware data, and each data packet contains header information, which at least includes the target device type.

[0061] For step S62, please refer to step S52 above, and it will not be repeated here.

[0062] Step S63: Parse the header information and extract the target device type.

[0063] For step S63, please refer to step S53 above, and it will not be repeated here.

[0064] Step S64: Compare the target device type with the device type of this function extension module. If the two match, proceed to step S65. If the two do not match, proceed to step S66.

[0065] Step S65: Assemble the individual data packets into firmware data and write them to the local storage area of ​​this function extension module.

[0066] Step S66: Discard each data packet.

[0067] Here we can give a unified explanation of steps S64 to S66. In step S64, the target device type can be compared with the device type of this function extension module. If the two do not match, it means that the device type of this function extension module is not the target device type, so each data packet can be discarded directly.

[0068] Of course, if the two match, it means that the device type of this function extension module is the target device type, and the firmware of this function extension module needs to be upgraded. Therefore, step S65 can be executed to assemble each data packet into firmware data and write it to the local storage area of ​​this function extension module.

[0069] Based on the same technical principle as the local storage area of ​​the aforementioned remote I / O coupler, the local storage area of ​​this functional expansion module can also be divided into an update parameter area, a first firmware area, and a second firmware area. The update parameter area is used to store update flags, the first firmware area is used to store currently running firmware data (i.e., the firmware data of the currently running firmware), and the second firmware area is used to store firmware data to be activated. Therefore, the way to write the firmware data to the local storage area of ​​this functional expansion module is to write the firmware data to the second firmware area and wait for activation.

[0070] For example, as mentioned above, the header information can also include an update timeliness flag. In this case, if the target device type matches the coupler type, after receiving and assembling all data packets, the activation operation can be performed based on the update timeliness flag. For instance, if the update timeliness flag indicates real-time mode, the firmware activation process is executed immediately; if the update timeliness flag indicates delayed mode, the firmware activation process is executed after the preset delay period. The firmware activation process can include restarting this module (in this case, this extended function module) and entering the Bootload program; then, the Bootload program checks the update flag in the update parameter area; if the update flag is valid, the firmware data to be activated in the second firmware area of ​​the local storage area is copied to the first firmware area; then the update flag is deleted, and the firmware data in the first firmware area is started. Of course, after upgrading the firmware using this firmware activation process, this extended function module can also report an update completion packet to the remote I / O coupler. This update completion packet can contain the station number of this extended function module.

[0071] Obviously Figure 4 The method shown can also solve the problems in the prior art, which will not be elaborated here.

[0072] The above is a detailed description of the remote I / O module batch upgrade method provided in the embodiments of this application. For ease of understanding, a specific example can be used to further illustrate the method. In this example, it is necessary to upgrade the firmware of the temperature control module in the remote I / O system, such as... Figure 5 The flowchart shown below illustrates this example, which includes the following steps: S71: The PC host computer sends a device information synchronization request to the remote I / O coupler through the interface.

[0073] S72: The PC host computer receives device information returned by the remote I / O coupler.

[0074] The device information includes the coupler type of the remote I / O coupler, as well as the device attribute information of each functional expansion module attached to the remote I / O coupler. The device attribute information includes module type information, current firmware version information, station number, etc.

[0075] S73: The PC host computer displays device information on its own device management interface.

[0076] S74: The PC host computer receives the upgrade parameters selected by the user. The upgrade parameters include the target device type and the target firmware version number.

[0077] Specifically, the target device type refers to a temperature control module.

[0078] S75: The PC host computer obtains the corresponding firmware data based on the target device type and target firmware version number.

[0079] S76: The PC host computer divides the firmware data into multiple data packets and adds header information to each data packet.

[0080] This header information should include at least the target device type.

[0081] S77: The PC host computer sends each data packet to the remote I / O coupler.

[0082] S78: The remote I / O coupler receives multiple data packets sent by the PC host computer.

[0083] S79: The remote I / O coupler parses the header information of the data packet and extracts the target device type.

[0084] S710: The remote I / O coupler performs distribution discrimination based on the target device type and broadcasts each data packet to each functional extension module.

[0085] S711: The temperature control module receives multiple data packets broadcast by the remote I / O coupler.

[0086] S712: The temperature control module parses the header information of the data packet and extracts the target device type.

[0087] S713: The temperature control module compares the target device type with the device type of this function extension module.

[0088] S714: The temperature control module assembles the various data packets into firmware data and writes it to the local storage area of ​​this functional extension module.

[0089] It should be noted that the system embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. Furthermore, in the accompanying drawings of the device embodiments provided by this invention, the connection relationships between modules indicate that they have communication connections, which can be specifically implemented as one or more communication buses or signal lines. Those skilled in the art can understand and implement this without creative effort.

[0090] The above description represents the preferred embodiments of the present invention. It should be noted that those skilled in the art can make various improvements and modifications without departing from the principles of the present invention, and these improvements and modifications are also considered to be within the scope of protection of the present invention.

Claims

1. A method for batch upgrading remote I / O modules, characterized in that, The method is applied to a PC host computer, and the method includes: Obtain device information sent by the remote I / O coupler. The device information includes the coupler type of the remote I / O coupler and the device attribute information of each functional expansion module attached to the remote I / O coupler. Display the device information and receive upgrade parameters selected by the user, including the target device type and the target firmware version number; Based on the target device type and the target firmware version number, obtain the corresponding firmware data; The firmware data is divided into multiple data packets, and header information is added to each data packet before being sent to the remote I / O coupler, so that the remote I / O coupler broadcasts the data packets to each functional extension module, wherein the header information at least includes the target device type.

2. The method according to claim 1, characterized in that, Based on the target device type and the target firmware version number, obtain the corresponding firmware data, specifically including: Based on the target device type and the target firmware version number, obtain the corresponding encrypted firmware file; The encrypted firmware file is decrypted to obtain the firmware data; The header information also includes the total number of packets and the sequence number of the corresponding data packets, wherein the total number of packets is used to indicate the total number of data packets obtained by dividing the firmware data; The upgrade parameters also include an update timeliness mode, which includes a real-time mode and a delayed mode. The delayed mode is used to indicate that firmware activation will be performed after a preset delay period has elapsed.

3. The method according to claim 1, characterized in that, The device attribute information includes module type information for identifying the functional category of the module, version information for identifying the current firmware version of the module, and address identification information for uniquely identifying each module on the bus. Before receiving the upgrade parameters selected by the user, the method further includes: The system receives user-input filtering criteria, which include at least one of device type and firmware version number. Based on the filtering criteria, matching functional extension modules are filtered from the device information, and the filtering results are displayed. The method further includes: Receive upgrade result information reported by the remote I / O coupler; The upgrade result information is displayed, which includes a list of modules that were successfully upgraded and / or information on modules that failed to be upgraded. The information on modules that failed to be upgraded includes at least the station number of the failed module.

4. A method for batch upgrading remote I / O modules, characterized in that, The method is applied to a remote I / O coupler, and the method includes: Send device information to the PC host computer. The device information includes the coupler type of the remote I / O coupler and the device attribute information of each functional expansion module attached to the remote I / O coupler. Receive multiple data packets sent by the PC host computer, wherein the multiple data packets are obtained by the PC host computer after dividing the firmware data, and each data packet contains header information, the header information at least containing the target device type; Parse the header information to extract the target device type; Distribution discrimination is performed based on the target device type. If the target device type matches the coupler type, the multiple data packets are assembled into firmware data and written to the local storage area of ​​the remote I / O coupler. If the target device type does not match the coupler type, each data packet is broadcast to each functional extension module.

5. The method according to claim 4, characterized in that, Broadcasting each data packet to each functional expansion module specifically includes: sending each data packet to each functional expansion module via the internal bus in a broadcast manner; The method further includes: receiving a start update mode command sent by the PC host computer; and starting an update mode in response to the start update mode command, wherein I / O data polling with the upper-layer master station is suspended in the update mode; The header information also includes an update timeliness flag; the method further includes: after completing the reception and assembly of all data packets, performing an activation operation according to the update timeliness flag, wherein if the update timeliness flag indicates a real-time mode, the firmware activation process is executed immediately; if the update timeliness flag indicates a delayed mode, the firmware activation process is executed after waiting for a preset delay period to arrive.

6. The method according to claim 4, characterized in that, The header information also includes the total number of packets and the sequence number of the corresponding data packets, wherein the total number of packets indicates the total number of data packets into which the firmware data is divided; assembling the multiple data packets into the firmware data and writing it into the local storage area of ​​the remote I / O coupler specifically includes: assembling the multiple data packets into the firmware data using the total number of packets and the sequence number of the corresponding data packets; and writing the firmware data into the local storage area of ​​the remote I / O coupler; The local storage area includes: an update parameter area for storing update flags; a first firmware area for storing currently running firmware data; and a second firmware area for storing firmware data to be activated. After broadcasting each data packet to each functional expansion module, the method further includes: receiving update completion packets reported by each functional expansion module, wherein the update completion packets contain the station number of the corresponding functional expansion module; and generating a list of modules that have been successfully upgraded based on the update completion packets. The method further includes: within a preset timeout window, generating corresponding upgrade failure module information for the functional extension modules of the target device type that have not received the update completion package; generating upgrade result information by combining the list of successfully upgraded modules and the information of the failed upgrade modules, and sending it to the PC host computer.

7. A method for batch upgrading remote I / O modules, characterized in that, The method is applied to a functional extension module, and the method includes: Report the device attribute information of this function extension module to the remote I / O coupler; Receive multiple data packets broadcast by the remote I / O coupler. The multiple data packets are obtained by the PC host computer after dividing the firmware data. Each of the data packets contains header information, and the header information contains at least the target device type. Parse the header information to extract the target device type; Compare the target device type with the device type of this functional expansion module; If the comparison matches, the multiple data packets are assembled into the firmware data and written to the local storage area of ​​this function extension module; If the comparison does not match, each data packet is discarded.

8. The method according to claim 7, characterized in that, The header information also includes an update timeliness flag; the method further includes: after completing the reception and assembly of all data packets, performing an activation operation according to the update timeliness flag, wherein if the update timeliness flag indicates a real-time mode, the firmware activation process is executed immediately; if the update timeliness flag indicates a delayed mode, the firmware activation process is executed after waiting for a preset delay period to arrive. The local storage area includes an update parameter area for storing update flag bits, a first firmware area for storing currently running firmware data, and a second firmware area for storing firmware data to be activated. Assembling the multiple data packets into the firmware data and writing it into the local storage area of ​​this functional extension module specifically includes: assembling the multiple data packets into the firmware data, and writing the firmware data as firmware data to be activated into the second firmware area.

9. The method according to claim 8, characterized in that, The firmware activation process includes: Restart this module to enter the Bootload program; The Bootload program detects and updates the flag bit. If the update flag is valid, the firmware data to be activated in the second firmware area of ​​the local storage area is copied to the first firmware area. Delete the update flag bit; Start the firmware data in the first firmware area.

10. A remote I / O system, characterized in that, It includes a PC host computer, a remote I / O coupler, and multiple functional expansion modules, among which: The PC host computer is used to acquire device information sent by the remote I / O coupler. The device information includes the coupler type of the remote I / O coupler and the device attribute information of each functional expansion module attached to the remote I / O coupler. It displays the device information and receives upgrade parameters selected by the user. The upgrade parameters include the target device type and the target firmware version number. Based on the target device type and the target firmware version number, it acquires the corresponding firmware data. The firmware data is divided into multiple data packets, and header information is added to each data packet before being sent to the remote I / O coupler, so that the remote I / O coupler broadcasts the data packets to each functional expansion module. The header information at least includes the target device type. The remote I / O coupler is used to send device information to a PC host computer; receive multiple data packets sent by the PC host computer; parse the header information and extract the target device type; perform distribution discrimination based on the target device type, wherein if the target device type matches the coupler type, the multiple data packets are assembled into firmware data and written to the local storage area of ​​the remote I / O coupler; if the target device type does not match the coupler type, the data packets are broadcast to each functional extension module. The functional extension module is used to report its device attribute information to the remote I / O coupler; receive multiple data packets broadcast by the remote I / O coupler; parse the header information and extract the target device type; compare the target device type with the device type of the functional extension module; if the comparison is consistent, assemble the multiple data packets into firmware data and write it to the local storage area of ​​the functional extension module; if the comparison is inconsistent, discard each data packet.