WO2021005530A1

WO2021005530A1 - Method and system for updating firmware of drives and associated modules

Info

Publication number: WO2021005530A1
Application number: PCT/IB2020/056424
Authority: WO
Inventors: Denson OUSEPH; Abhijit NIKAM
Original assignee: Abb Schweiz Ag
Priority date: 2019-07-09
Filing date: 2020-07-08
Publication date: 2021-01-14

Abstract

The present invention relates to a method and a system for updating firmware of industrial drives and associated modules. The system selects an industrial drive from a plurality of industrial drives, and a first firmware. Accordingly, a second firmware from a plurality of second firmware is selected. Further, the system determines a compatibility between the selected first firmware and the second firmware based on a mapping between the plurality of first firmware and the plurality of second firmware that exists in a database associated with the system. Thereafter, the first firmware and the second firmware are loaded into the industrial drive commissioned in the industrial plant and installs the first firmware into the industrial drive for updating industrial drive firmware and installs the second firmware in the one or more modules for updating firmware of the one or more modules.

Description

METHOD AND SYSTEM FOR UPDATING FIRMWARE OF DRIVES AND

ASSOCIATED MODULES

Technical Field

[001] The current invention relates in general to industrial equipment, and more particularly to update firmware of industrial drives and associated modules.

Background

[002] Industrial drives are generally used for controlling equipment like motors. Specifically, industrial drives are used to control motor speed, motor torque and motor power usage. Motors may in turn control a load.

[003] A typical industrial drive in addition to drive firmware, can also comprise various modules such as a fieldbus, an Input/ Output (I/O) module (or feedback modules) and so forth. These modules provide certain added functionality as desired by end-user or for the application. For instance, a fieldbus module enables the industrial drive to connect to a distributed control system and may be standardized according to IEC61158. Taking another example, feedback modules enable the industrial drive to connect to various components such as an encoder for receiving data related to motor and components thereof.

[004] The industrial drives and modules operate based on the firmware they are configured with. The firmware needs to be timely updated/ upgraded to resolve existing issues and to update the industrial drives and modules according to state of the art. Also, due to specific conditions in the site, the operations of the industrial drives and the modules may need to be reconfigured by updating the firmware.

[005] Often when drive firmware is updated, the firmware of other modules may remain unchanged, i.e. the firmware of the other modules may not be updated. Many a times updating the industrial drive leaves the drives incompatible with corresponding modules. This incompatibility is due to the updated drive firmware needing the firmware of other modules to also be updated to next version. Alternately, the updated drive firmware might need hardware changes for some modules. Lack of such knowledge dining the firmware update leads to incompatibility which can affect drive and module operation. [006] To overcome the issues, the firmware of the other modules may need to be independently updated, or the existing modules may have to be replaced with new modules having updated hardware / firmware, and which are compatible with the updated firmware of the industrial drive. For example, a drive connected to a motor and an encoder placed in the motor provides rotor position data to the drive. Updating firmware of the drive can lead to compatibility issues for the drive to communicate with the encoder. Hence, the encoder module firmware has to be updated manually by a site engineer, or the encoder module has to be replaced with a new encoder module having an updated firmware such that the drive and the encoder module are compatible.

[007] Thus, there exists a need to provide new and improved systems and methods that will automatically update firmware of industrial drives and associated modules. Summary of the Invention

[008] The present invention relates to a method and a system for updating firmware of an industrial drive and one or more modules. Each module is one of, but not limited to, a fieldbus module, a I/O module, and a feedback module. These modules are typically installed in slots provided on the industrial drive for such purposes, as would be apparent to those of ordinary skill in the art.

[009] The method and system are used to configure one or more industrial drives as well as one or more modules of each industrial drive. Thus, the method and system are used to update the drive and module firmware for one industrial drive, or the method and system is used to update the drive and module firmware for different industrial drives and modules of the various drives.

[0010] The system is hosted on a remote server such as a cloud server and can have a database (or server being connected to a database). Alternately, the system is hosted in a server local to an industrial plant comprising the plurality of industrial drives and the one or more modules. Yet another alternative is to provide the system on a computing unit such as a desktop or a laptop.

[0011] The database (at the server or computing unit) has various information that is accessed for updating the firmware. In particular, the database includes a plurality of firmware as well as information about compatibility between different firmware, drives and modules. The plurality of firmware is for a plurality of drives and a plurality of modules, i.e. each firmware is having one or multiple versions and is for a particular drive or a particular module. [0012] In some embodiments, the system is accessed with a computing device (or unit) such as desktop or a laptop, which is connected via a network (e.g. a plant network or internet). The computing device is also connected with an industrial drive (and modules) using a wired connection. Alternately, the computing device accesses the industrial drive through the system, i.e. server is connected in the industrial network with industrial drives and modules thereof, and the computing device is connected to the server.

[0013] The method is performed wife fee computing device, by communication wife fee system and fee industrial drive (and modules). Alternately, fee computing device is configured to perform fee method by communicating wife fee drive. [0014] Thus, when the system (e.g. hosted on server) is accessed, the computing device can render various interfaces on a display of the computing device. The interfeces are used to select firmware packages for a specific industrial drive and modules of that drive, or to select firmware packages for different drives. Also, the interfaces are used for configuring the drive and modules for the firmware packages. Eventually, these are used to check if the selected firmware package will work for the selected configurations, and if so, they are obtained and pushed to the industrial drive (and modules) for updating the drive and modules to the corresponding firmware versions.

[0015] Thus, in accordance wife an embodiment, fee method includes displaying a first interface wife a plurality' of firmware for a plurality' of drives and a plurality of modules. Here, one or more versions of each firmware of fee plurality of firmware are associated wife one of a predetermined drive, and a predetermined module.

[0016] The method further includes receiving selection of a first firmware from the plurality of firmware, and in response to the selection of the first firmware, displaying the first firmware and at least a second firmware associated with the first firmware. Here, the second firmware (and other firmware as applicable) is identified from a database according to the first firmware. For example, the first firmware is for one particular drive type, and the second firmware (and a third firmware) for one or more modules is identified and displayed. This is identified from the database feat comprises compatibility information associated wife fee plurality of firmware.

[0017] In accordance wife fee embodiment, fee method further includes receiving selection of fee second firmware (and fee other firmware as applicable) from fee plurality of firmware. [0018] Once the firmware is selected, the industrial drive and the modules is selected for configuration with the selected firmware.

[0019] Thus, in accordance with the embodiment, the method includes displaying a second interface for selecting configuration of the industrial drive and one or more slots for the first firmware and the second firmware. The selection of the configurations, i.e. the drive type and the slots for the modules, and inputs on whether to update firmware for the drive type, the modules etc. is received at this interface. Thus, the method includes receiving the selected configurations.

[0020] According to the selected firmware, the industrial drive and the modules, packaging of the firmware is performed to generate one of a packaged firmware, or an alert. Thus, according to the inputs received from the computing device, the system can check if the selected firmware can work on the selected drive and modules. If there are no concerns, the selected firmware are packaged together for configuring the industrial drive and the modules. Otherwise, an alert is generated to indicate the firmware mismatch. [0021] Accordingly, the method includes generating the packaged firmware or the alert. The packaged firmware generation is initiated with the computing device according to the inputs and is received from the system once generated.

[0022] The method additionally includes providing the packaged firmware (if available) to the industrial drive (and modules) for updating the industrial drive and modules. This is pushed through a communication port of the industrial drive. Depending on the industrial drive and the modules, data exchange between external devices (computing device, system), and the industrial drive and modules is in different ways. For example, the drive can interface the computing device with a first communication port, and internally the drive can push the update to the modules. Alternately, there is a common communication port for communication from the computing device to the drive and the various modules.

Brief Description of Drawings

[0023] The subject matter of the invention will be explained in more detail in the following text with reference to preferred exemplary embodiments which are illustrated in the drawings, in which: [0024] Figure 1A illustrates a simplified block diagram of an environment for updating firmware of industrial drives and associated modules, in accordance with an embodiment of the present invention;

[0025] Figure IB illustrates a simplified block diagram of a system for updating firmware of industrial drives and associated modules, in accordance with an embodiment of the present invention;

[0026] Figure 2 is a flowchart of a method for updating firmware of industrial drives and associated modules, in accordance with an embodiment of the present invention;

[0027] Figure 3 illustrates exemplary User Interface (UI) for selecting first firmware and second firmware, in accordance with an embodiment of the present invention;

[0028] Figure 4 is an illustration of a UI showing a plurality of firmware, in accordance with an embodiment of the present invention;

[0029] Figure 5 is an illustration of generating a firmware package for updating the industrial drives and associated modules, in accordance with an embodiment of the present invention;

[0030] Figure 6 is an illustration of an exemplary UI showing the selected first firmware and the second firmware for updating the industrial drives and associated modules, in accordance with an embodiment of the present invention; and

[0031] Figure 7 is an illustration of installing the first and second firmware in an industrial drive and associated modules, in accordance with an embodiment of the present invention. Detailed Description:

[0032] The present invention discloses a method and a system for updating firmware of industrial drives and associated modules.

[0033] Figure 1 illustrates a simplified block diagram of an environment for updating firmware of an industrial drive and associated one or more modules. As shown in Figure 1, a site (100) or field (for example an industrial plant) comprises an industrial drive (102), one or more modules (103a & 103b) configured in the industrial drive (102), a motor (104). In an embodiment, the one or more modules (103a & 103b) is a fieldbus module, an Input/ Output (I/O) module or a feedback module. A fieldbus module enables the industrial drive to connect to distributed control systems and is standardized according to IEC61158. A plurality of protocols is defined for communication using fieldbus module. I/O modules enable the industrial drives to connect to various components such as an encoder for receiving data related to position of rotors in the motor. Likewise, various components are connected to the industrial drives. Similarly, the industrial drive is connected to various sensors for receiving data and measurements related to the motor and / or the environment of a site. [0034] An example is a sensor (109) integrated to the motor (104). In an embodiment, the sensor (109) is an encoder for measuring rotor position in the motor (104). In an embodiment, the sensor (109) can provide measurements as feedback to the industrial drive (102). The industrial drive (102) (also referred as drive) is electrically connected to the motor (104) for controlling speed and torque of the motor (104), which in turn may control a load (not shown). The drive (102) is connected to a power supply (101). The motor (104) can also be connected to the power supply (101), however, the electrical connection is not shown in Figure 1 and a person of ordinary skill should appreciate such connection exits. In one embodiment, the sensors (109) are mounted on the motor (104). In another embodiment, the sensor (109) is mounted on the drive (104). The sensor (109) is configured to measure various parameters such as vibrations, temperature, speed, current, voltage, and the like.

[0035] In Fig. 1, the drive module is shown to interact with an encoder. It should be apparent that the drive can have different modules, and each module is connected in the plant for different functions. Also, there may be connections with different types of industrial devices or equipment. For example, a drive may be connected with a motor, controller, sensors, communication devices etc. Accordingly, different modules (and corresponding ports) of the drive are pre -configured for such functions.

[0036] The drive (102) can be connected to a computing unit (106) for updating the drive and / or the modules of the drive. The computing unit (106) is an electronic device such as a desktop, a laptop, a tablet, and the like. The computing unit (106) is typically connected to the drive (102) using a cable (e.g. a USB or other cable), to access and alter the drive configuration

(i.e. via the connection). To perform such update, the computing unit is configured with the update / upgrade functions.

[0037] The computing unit can implement the update independently or in connection with a server (107). [0038] In one embodiment, the server is connected to the computing unit (106) via a network

(105). This connection is different from the cable connection and is typically an ethemet or other wired / wireless connection, which enables access to plant or cloud server at the computing device.

[0039] The server (107) (or computing device) implements an application (system) for configuring, engineering and monitoring the drive (102) and the one or more modules (103a & 103b). For example, during installation of the drive (102) and the one or more modules (103a

& 103b), the system can install the necessary' firmware into the drive (102) and the one or more modules (103a & 103b). Further, the system can configure parameter settings of the drive (102) and the one or more modules (103a &103b) for the drive (102) and the one or more module (103a & 103b) to perform respective functions. [0040] The firmware installed in the drive (102) is provided for drive functions. Likewise, the one or more modules (103a & 103b) also comprises firmware for performing respective functions. The drive (102) can have one or more slots (not shown) for the one or more modules. The one or more modules (103a & 103b) comprises adaptors to be associated with the one or more slots. For example, the I/O module is associated with slot 1 via an I/O adaptor, and the I/O adaptor is configured with a firmware that facilitates I/O devices (e.g., sensors (109)) to connect to the drive (102).

[0041] The system is used to update firmware of the drive and the one or more modules (103a & 103b), using a database.

[0042] In an embodiment the server (107) is associated with a database (108). The database (108) has a plurality of firmware. The plurality of firmware is associated with a plurality of drives and a plurality of modules. Further, each firmware can have various versions.

[0043] Figure IB shows the blocks present in the system for updating firmware of the drive (102) and the one or more module (103). In an embodiment, the system comprises various modules such as a rendering module, an input interface, a compatibility check module, a packaging module and a communication module. These modules can be implemented with a processor, an Application Specific Integrated Circuit (ASIC), Field-Programmable Gate Arrays (FPGA) or any other circuits that are capable of processing data. Accordingly, the modules are preconfigured to perform the various steps of the method. Thus, each module can be implemented in software and hardware, to perform the steps of the method. [0044] Figure 2 illustrates an exemplary flow chart for updating firmware of the industrial drive

(102) and the one or more modules (103a & 103b). [0045] At step 201, the rendering module (110) is configured in the server (107) to display a first interface with a plurality of firmware for a plurality of drives (102) and a plurality of modules (103).

[0046] Referring now to Figure 3, a UI is illustrated. In an embodiment, the UI is associated with the application (system) implemented in the computing unit (106). As shown, the UI can include fields for selecting drive and its modules for updating the firmware. As illustrated, the plurality of drives is provided for selection.

[0047] Referring back to Figure 2, at step 202, the method includes receiving by the user interface (111), a selection a type of drive (102) from a plurality of drive and the first firmware. A site engineer can access the UI on the computing unit (106) and can select the drive (102) for which the firmware needs update. For example, as shown in the Figure 3, the plurality of drives can include various models of drives such as ACS580, ACS850, ACS880 and so on. As shown, the drive (102) ACS880 is selected as an input by the site engineer. In one embodiment, a dropdown showing list of the plurality of drives is implemented. In one embodiment, a list comprising the plurality of drives is presented to the site engineer. The system selects the drive (102) based on an input received from the site engineer (or other operator or personnel). In an embodiment, once the drive (102) is selected, the UI provides an option for selecting the first firmware for the drive. As shown in Figure 4, different versions of the first firmware can be enlisted for the selected drive (102) by the system. [0048] At step 203, the method includes displaying by the user interface (111), in response to the selected first firmware, the selected first firmware, and at least a second firmware. Figure 3 illustrates the selected drive (first firmware not shown) and the second firmware according to the selection of the first firmware. As shown, for the selected drive (102) ACS880, the fieldbus modules shown are FENA-1, FENA-11 and FPBA-01. Likewise, for a different drive (e.g., ACS580) different fieldbus modules may be provided. Based on a model of the drive

(102), corresponding fieldbus modules are enlisted in the UI. In an embodiment, a list of all such modules (associated with the selected drive (102) are shown in the UI. For example, a field for slot 2 (for I/O module) can also be shown in the UI. For illustration, only one slot is shown in the Figure 3. A person skilled in the art should acknowledge that many such fields is shown, and corresponding modules is selected by the site engineer.

[0049] Referring now to Figure 4, an exemplary UI showing the plurality of firmware stored in the database (108) is shown. In an embodiment, the plurality of firmware comprises various versions of the first firmware and second firmware. For example, let the selected drive (102) is ACS880, different versions of firmware available for the selected drive (102) are shown in the UI. Likewise, for the selected one or more modules (103a & 103b) (e.g., FENA-l(fieldbus module) and encoder (feedback or I/O module)), various versions available for respective modules are shown in the UI. As shown, the available versions of first firmware are ACS880FW1.0, ACS880FW2.0 and ACS880FW2.1. Likewise, the versions of the firmware available for the FENA-1 are FMODFWl.O, FMODFW2.0 and FMODFW3.0 and the various versions of the firmware available for the encoder are EncModFW4.0, EncModFW4.1 and EncModFW4.5. In an exemplary embodiment, the first firmware refers to the drive firmware and the second firmware refers to the firmware of the fieldbus module and the I/O module.

[0050] At step 204, the method includes receiving by the user interface (111), a selection for the second firmware. In an embodiment, any slot in the drive (102) can be selected. The site engineer can select the second firmware from the displayed plurality of second firmware. Figure 4 shows the second interface showing the plurality of first and second firmware. Figure 5 further illustrates that for the selected first firmware (ACS880 FW2.1), the corresponding second firmware available are F Mod FW2.0 and the Enc Mod FW4.0.

[0051] In an embodiment, the compatibility check module (112) determines a compatibility between the first firmware and the second firmware. In an embodiment, the database (108) can have a mapping between the plurality of first firmware and the plurality of second firmware. The mapping can suggest the compatibility between different firmware associated with different equipment and modules. For example, a mapping between ACS880FW2.1, FMODFW2.0 and EncModFW4.0 indicates that the drive firmware ACS880FW2.1 is compatible with the fieldbus module FMODFW2.0 and the I/O module EncModFW4.0. Likewise, a plurality of such mapping exists in the database (108). [0052] Once the site engineer selects the first firmware and the second firmware, the compatibility check module (112) determines the compatibility' between the selected firmware based on the mapping between different firmware. In an embodiment, if the selected first firmware and the second firmware are not compatible, an alert is displayed in the UI. The site engineer can select an alterate firmware to meet tire requirement of compatibility. In case of compatibility, a suitable message is displayed, and user is provided to generate a firmware package. [0053] At step 205, the method includes displaying by the rendering module (110), a second interface for selecting configuration of the drive (102) and one or more slots in the drive (102). In an embodiment, the drive (102) comprises one or more slots for uploading the selected first firmware and the second firmware. Referring Fig. 6, once the firmware is selected, the UI provided enables the personnel select slots for installing the firmware and confirming whether to update or not. This may be automatically populated based on the firmware selection. As the system is aware of the drive and modules, it can recommend this.

[0054] As an example, the first firmware is to be installed in the drive slot and the second firmware in for the corresponding modules. [0055] The selected firmware can be packaged together for the installation.

[0056] At step 206, the method comprises generating by the packaging module (113) a firmware package. Reference is now made to Figure 5, illustrating generation of the firmware package. In one embodiment, the firmware package is an archived file comprising the first firmware and the second firmware. [0057] At step 207, the method comprises providing by the communication module (114), the firmware package for installing the first firmware and the second firmware. The system loads the firmware package into the drive (102) commissioned in the site (100). Loading the firmware package includes loading the firmware package file into the drive (102) via the computing unit (106), or via the server. In an embodiment, the drive (102) can comprises a memory (RAM and/or ROM) to store the first firmware. In an embodiment, the drive (102) may comprises additional storage to store the second firmware. Referring to Figure 7, an illustration of loading the firmware package into the drive is shown.

[0058] In an embodiment, the system installs tire first firmware in the drive (102) and the second firmware in the respective one or more modules (103a & 103b). In an embodiment, during installation of the firmware, the drive (102) is connected to the computing unit (106) such that the system has access to the drive (102) and its memory (RAM and/or ROM). In a further embodiment, the system can have read/write access to modify contents in the drive (102). In an embodiment, upon loading the firmware package into the drive (102), the system is configured to extract the first firmware and second firmware from the firmware package. The drive can have dedicated memory locations for storing the first firmware and second firmware. Upon extracting first and second firmware, the system can store the first firmware and the second firmware in the dedicated memory locations. Further, the system installs the first firmware in the drive ( 102) and the second firmware in the one or more modules (103a & 103b). In a further embodiment, the system provides installs the first firmware in a first communication port. The first communication port is configured for communication between the system and the drive (102). [0059] In one embodiment, the second firmware is installed by the drive (102) in the one or more modules (103a & 103b) via a second communication port configured for communication between the drive (102) and the one or more module (103). The drive (102) is capable of detecting the second firmware and install the second firmware in the one or more modules (103a & 103b). For example, if the drive (102) comprises three slots for three modules, the drive (102) updates firmware of a first module, second module and a third module. In one embodiment, only the second firmware of the one or more modules (103a & 103b) is updated without updating the first firmware of the drive (102). In another embodiment, only the first firmware of the drive (102) is updated without updating the second firmware of the one or more modules (103a & 103b). [0060] In one embodiment, the drive (102) comprises a provision such that the system can update the second firmware of the one or more modules (103a & 103b) without updating the first firmware of the drive (102) via a common communication port configured for communication between the drive (102) and the system and the one or more module (103) and the system. For example, a dedicated slot is provided in the drive (102) such that w'hen the second firmware is loaded in the slot, the drive (102) can push the second firmware into the one or more modules (103a & 103b) and provide access to the system to install the second firmware in the one or more modules (103a & 103b). In an embodiment, the system may selectively install the second firmware in the one or more modules (103a & 103b). The system may not update firmware of each of the one or more modules (103a & 103b). Instead, the system may install, for example only in the first module among three modules.

[0061] In an embodiment, the firmware update of the drive (102) and the one or more modules (103a & 103b) is initiated from the site (100) or is initiated remotely over the network (105).

[0062] In an embodiment, the proposed method and system helps in achieving efficiency as compatibility between firmware is determined. [0063] In an embodiment, updating firmware of the one or more modules ( 103a & 103b) along with firmware of the drive (102) reduces time in independently updating the firmware of the one or more modules (103a & 103b). [0064] Thus, the invention provides updating firmware of drive and modules of the drive using a computing device. The computing device is either configured individually to perform various steps for the update and is physically (e.g. through a cable) connected to the drive. The device is configured with an application, which allows the device to perform the various functions. In particular, the device renders available firmware for the drive and the modules of the drive. This can be fetched according to the drive type and the particular module, and the hardware version of the drive and modules. A database with the device provides which firmware is available for the drive and modules. According to selection of one firmware, other compatible firmware is shown for easy selection. This reduces the burden on the operator to identify which firmware will work together, while performing the update. Eventually, the selected firmware is packaged and sent for installation. This can be sent to the drive which performs the update for the drive and the modules, or to a common port (if that is available). As an alternative to providing the entire functionality with the computing device, the invention can be a distributed solution, where part of the method is performed by the device and part by the server.

Referral Numerals:

100 - Site

101 - Power supply

102 - Drive

103 - Modules

104 - Motor

105 - Network

106 - Computing unit

107 - Server

108 - Database

109 - Sensor

Claims

We claim:

1. A method for updating firmware of an industrial drive and one or more modules associated with the industrial drive, wherein each module of the one or more modules is one of, a fieldbus module, an Input/ Output (I/O) module, and a feedback module, the method comprising: displaying a first interface with a plurality of firmware for a plurality of drives and a plurality of modules, wherein one or more versions of each firmware of the plurality of firmware are associated with one of a predetermined drive, and a predetermined module; receiving selection of a first firmware from the plurality of firmware;

displaying, in response to the selection of the first firmware, the first firmware and at least a second firmware associated with the first firmware, wherein the second firmware is identified from a database according to the first firmware, wherein the database comprises compatibility information associated with the plurality of firmware;

receiving selection of the second firmware from the plurality' of firmware;

displaying a second interface for selecting configuration of the industrial drive and one or more slots for the first firmware and the second firmware;

generating one of a packaged firmware and an alert, according to a check for firmware mismatch based on the first firmware and the second firmware, wherein the check is performed according to the selected configuration of the industrial drive and the one or more slots, based on tire information associated with the plurality of firmware, wherein the packaged firmware is generated with the first firmware and the second firmware, and wherein the alert provides information of the firmware mismatch; and

providing the packaged firmware for installing the first firmware and the second firmware.

2. The method as claimed in claim 1, wherein the first firmware is associated with one of the plurality of drives, and the second firmware is associated with one of the plurality of modules.

3. The method as claimed in claim 1, wherein displaying at least the second firmware comprises displaying the second firmware and one or more third firmware, according to the first firmware.

4. The method as claimed in claim 1, wherein providing the packaged firmware comprises sending the packaged firmware to the industrial drive at a first communication port, wherein the first communication port is configured for data exchange between the computing device and the industrial drive, and wherein the industrial drive and the one or more modules communication via at least a second communication port.

5. The method as claimed in claim 1, wherein providing the packaged firmware comprises sending the packaged firmware to the industrial drive at a common communication port, wherein the common communication port is configured for data exchange between the computing device, the industrial drive, and the one or mote modules.

6. The method as claimed in claim 1, wherein the method is performed with a computing device that is connected with the industrial drive via a first communication channel, and wherein the computing device is connected with a server via a second communication channel.

7. A system for updating firmware of industrial drives and modules, the system comprising: a rendering module for rendering one or more interfeces, wherein a first interface displays a plurality of firmware for a plurality of drives and a plurality of modules, wherein one or more versions of each firmware of the plurality of firmware are associated with one of a predetermined drive, and a predetermined module (first, second interface), wherein in response to the selection of the first firmware, the first firmware and at least a second firmware associated with the first firmware is displayed, wherein the second firmware is identified from a database according to the first firmware, wherein the database comprises compatibility information associated with the plurality of firmware, wherein a second interface is displayed for selecting configuration of the industrial drive and one or more slots for the first firmware and the second firmware

an input interface for receiving selection via the first and second interfeces, wherein the selection from the first interface comprises receiving selection of a first and a second firmware from the plurality of firmware and wherein selection from the second interface comprises receiving selection of configuration and one or more slots in the industrial drive;

a compatibility check module for checking compatibility between the selected first firmware and the selected second firmware;

a packaging module for generating a firmware package comprising the selected first firmware and the selected second firmware; and

a communication module for sending the firmware package to the appropriate one or more slots in the industrial drive.

8. The system as claimed in claim 7, wherein the communication module is configured to provide the packaged firmware to the industrial drive at a first communication port, wherein the first communication port is configured for data exchange between the system and the industrial drive, and wherein the industrial drive and the one or more modules communication via at least a second communication port.

9. The system as claimed in claim 7, wherein the communication module provides the packaged firmware to the industrial drive at a common communication port, wherein the common communication port is configured for data exchange between the system, the industrial drive, and the one or more modules.

10. The system as claimed in claim 7, wherein the communication module communicates with the industrial drive and the one or more module via a computing device that is connected with the industrial drive via a first communication channel, and wherein the computing device is connected with a server via a second communication channel.