Fieldbus equipment software integration method and device and storage medium thereof

Abstract

The invention discloses a fieldbus equipment software integration method and device and a storage medium thereof, and relates to the technical field of fieldbuses, the modularization method is realized by splitting fieldbus slave station equipment software into a plurality of module units, each module unit has clear responsibilities and interfaces, and the integration of fieldbus slave station equipment software is realized. Wherein the controller unit comprises a CPU (Central Processing Unit), a memory, a slave station chip interface and an external Ethernet interface, the software is realized by adopting a layered architecture, an operating system abstraction layer and a field bus slave station protocol stack abstraction layer are added, and the modularization method provides a plurality of functions such as slave station remote IO (Input / Output), a slave station coupler, slave station equipment and the like. Moreover, the functions can be enabled through configuration information, and effective execution and management can be achieved through tools such as a protocol analysis device and a computer readable storage medium.

Description

Technical Field

[0001] The present invention relates to the field of field bus technology, and in particular to a method and device for integrating field bus equipment software and a storage medium thereof. Background Art

[0002] Software changes occur all the time throughout its life cycle. On the one hand, these are updates caused by new technologies, and on the other hand, they are updates caused by changes in user needs.

[0003] In industrial automation systems, fieldbus devices are used to transmit field control data and measurement values ​​to programmable logic controllers (PLCs). Fieldbus devices are required to be scalable and configurable. On the one hand, the functional requirements are becoming more and more complex, and on the other hand, the communication methods also need to be different with the fieldbus. Therefore, higher requirements are placed on the software development speed, flexibility and stability of fieldbus devices.

[0004] At present, each automation manufacturer designs different software for different fieldbus devices. The software reuse rate is extremely low. Each part of the system needs to be developed from scratch. There is a lot of duplication of work in the system development process, the openness is very poor, and there are many obstacles to updating. In addition, the products of various manufacturers are incompatible and it is difficult to meet the needs of modern industrial production. The reason for this problem is that the software of fieldbus devices is designed separately according to the hardware, and there is a lack of a method for integrating the software of different devices. Therefore, it is particularly important to invent a method, device and storage medium for integrating fieldbus device software.

[0005] Existing technologies such as announcement number: CN201910207833.8 disclose a human-machine interaction system architecture in the field of industrial robots, which realizes the independence of display input, data acquisition, and data transmission through layered design, and improves the modifiability of software through modular ideas. However, these studies focus on the research of human-machine interaction system architecture in the field of industrial robots, and do not involve the internal component design of the software architecture of fieldbus devices.

[0006] The prior art also has the following shortcomings, which are specifically reflected in: 1. The prior art protocol has low compatibility, there are many different field bus protocol standards, and there are differences between the protocols, which makes it difficult to directly integrate and interoperate devices with different protocols, increases the complexity and cost of system integration, reduces communication efficiency, increases the probability of data errors or losses, and increases the difficulty of data transmission and exchange.

[0007] 2. Existing integration methods may be difficult to meet the needs of system expansion. When the system needs to be expanded, if the existing integration methods cannot effectively support it, a large number of hardware devices need to be replaced. Existing integration methods have limitations, and the software cannot flexibly adapt to the access of new devices. The entire system needs to be redesigned and reconfigured, which increases the cost of system upgrades and maintenance. Summary of the invention

[0008] The purpose of the present invention is to provide a method and device for integrating fieldbus device software and a storage medium thereof, which solve the problems existing in the background technology.

[0009] To solve the above technical problems, the present invention adopts the following technical solution: The present invention provides a method, device and storage medium for integrating fieldbus device software, including step 1, configuring a fieldbus slave device.

[0010] Step 2: Modularize the fieldbus slave device software.

[0011] Step 3: Fieldbus slave protocol abstraction.

[0012] Step 4: Information storage.

[0013] Preferably, the fieldbus slave device configuration includes a controller unit, at least one expansion module unit and a server. The controller unit of the fieldbus slave device includes a CPU, a memory, a slave chip interface and an external Ethernet interface. The software of the fieldbus slave device is implemented using a layered architecture.

[0014] Preferably, the fieldbus slave device software is modularized, including a logic function layer and a user function layer. The logic function layer is located at the top layer of the human-computer interaction system architecture, and organizes and coordinates specific program operations, parameter reading and writing, device diagnosis, and expansion module management. The user function layer is located at the top of the software architecture, and presents the functions of the fieldbus device in a modular form. The function layer implements specific device functions, such as code processing, operation status diagnosis, alarm, data acquisition, expansion module management, etc.; and ultimately realizes the operation management, data transmission, file storage and other operations of the actual fieldbus device.

[0015] Preferably, the fieldbus slave station protocol abstraction, the specific process is: the fieldbus slave station device software will add a fieldbus abstraction layer in the hierarchical structure, including a protocol stack abstraction layer, which is used to abstract the common interface of the slave station protocol stack software, and use a unified interface form to the application layer, which will abstract the common parts of different fieldbus communication protocols, or abstract the interface part containing the fieldbus protocol chip.

[0016] Preferably, the fieldbus slave device software will add a fieldbus abstraction layer in the layered structure, including an operating system abstraction layer, provide a calling interface to the fieldbus layer through an interface, and adapt to the underlying operating system layer.

[0017] Preferably, the fieldbus slave device software can realize slave remote IO, slave coupler, and slave device through a set of methods; the fieldbus slave device software enables corresponding slave functions through configuration information.

[0018] A second aspect of the present invention provides a server for running a fieldbus slave device, characterized in that, for information storage, configuration information required by the fieldbus slave device is stored in a local storage medium.

[0019] The third aspect of the present invention provides a parsing device for the modularization method of field bus slave device software, characterized in that the protocol parsing device includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, and when the computer program is executed by the processor, the steps of any one of the modularization methods for field bus slave device software are implemented.

[0020] A fourth aspect of the present invention provides a computer-readable storage medium for a modular method for fieldbus slave device software, characterized in that a fieldbus device integration software program is stored on the computer-readable storage medium, and when the program of the fieldbus device integration method is executed by a processor, it will implement any step of the modular method for fieldbus slave device software described in any one of the above.

[0021] The beneficial effects of the present invention are: 1. The technical protocols in the present invention are highly compatible, and devices with different protocols can be directly integrated and interoperable, which reduces the complexity and cost of system integration. At the same time, it reduces the software development and debugging work caused by protocol conversion, shortens the system integration cycle, increases communication efficiency, reduces the probability of data errors or losses, and reduces the difficulty of data transmission and exchange.

[0022] 2. In the present invention, the system has high scalability. When the system has high scalability, there is no need to replace existing hardware equipment on a large scale during the upgrade. During the update process, the high scalability system can quickly integrate new components or functions due to its good architectural design, thereby improving the system's update efficiency and reducing the cost of system upgrades and maintenance. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0024] Figure 1 It is a schematic diagram of the steps of the method of the present invention.

[0025] Figure 2 The operating environment diagram of a fieldbus device software integration method is shown in FIG.

[0026] Figure 3 This is a layered architecture diagram of modular software for fieldbus devices.

[0027] Figure 4 This is a schematic diagram of configuration information stored in a storage medium according to the present invention.

[0028] Figure 5 It is a schematic diagram of the process of reading and acquiring the configuration information of the field bus of the present invention.

[0029] Figure 6 This is an example diagram of a configuration file of the present invention. DETAILED DESCRIPTION

[0030] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0031] Reference Figure 1 As shown, the present invention provides a method, device and storage medium for integrating fieldbus device software, step 1, fieldbus slave station device configuration.

[0032] In a specific embodiment, the fieldbus slave device configuration includes a controller unit, at least one expansion module unit and a server. The controller unit of the fieldbus slave device includes a CPU, a memory, a slave chip interface and an external Ethernet interface. The software of the fieldbus slave device is implemented using a layered architecture.

[0033] In the present invention, the technical protocols are highly compatible, and devices with different protocols can be directly integrated and interoperable, which reduces the complexity and cost of system integration. At the same time, it reduces the software development and debugging work caused by protocol conversion, shortens the system integration cycle, increases communication efficiency, reduces the probability of data error or loss, and reduces the difficulty of data transmission and exchange.

[0034] Step 2: Modularize the fieldbus slave device software.

[0035] In a specific embodiment, the fieldbus slave device software is modularized, including a logic function layer and a user function layer. The logic function layer is located at the top layer of the human-computer interaction system architecture, and organizes and coordinates specific program operations, parameter reading and writing, device diagnosis, and expansion module management. The user function layer is located at the top of the software architecture, and presents the functions of the fieldbus device in a modular form. The function layer implements specific device functions, such as code processing, operation status diagnosis, alarm, data acquisition, expansion module management, etc.; ultimately, it realizes the operation management, data transmission, file storage and other operations of the actual fieldbus device.

[0036] Step 3: Fieldbus slave protocol abstraction.

[0037] In a specific embodiment, the fieldbus slave station protocol abstraction, the specific process is: the fieldbus slave station device software will add a fieldbus abstraction layer in the hierarchical structure, including a protocol stack abstraction layer, which is used to abstract the common interface of the slave station protocol stack software, and use a unified interface form to the application layer, which will abstract the common parts of different fieldbus communication protocols, or abstract the interface part containing the fieldbus protocol chip.

[0038] In a specific embodiment, the fieldbus slave device software will add a fieldbus abstraction layer to the hierarchical structure, including an operating system abstraction layer, which provides a calling interface to the fieldbus layer through an interface and adapts to the lower operating system layer; according to the function, it can be divided into two components: the operating system abstraction component is responsible for the multi-task interface abstraction, and the hardware driver is responsible for the abstraction of the driver program of the fieldbus communication interface.

[0039] In the present invention, the system has high scalability. When the system has high scalability, there is no need to replace existing hardware equipment on a large scale during the upgrade. During the update process, the highly scalable system can quickly integrate new components or functions due to its good architectural design, thereby improving the system's update efficiency and reducing the cost of system upgrades and maintenance.

[0040] In a specific embodiment, the fieldbus slave device software can implement slave remote IO, slave coupler, and slave device through a set of methods; the fieldbus slave device software enables corresponding slave functions through configuration information.

[0041] Step 4: Information storage.

[0042] In a specific embodiment, the information storage, the configuration information required by the fieldbus slave device will be stored in a local storage medium.

[0043] In a specific embodiment, the protocol parsing device includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program, when executed by the processor, implements the steps of any one of the modularization methods for field bus slave device software.

[0044] In a specific embodiment, the computer-readable storage medium stores a fieldbus device integration software program, and when the fieldbus device integration method program is executed by a processor, the steps of any one of the fieldbus slave device software modularization methods are implemented.

[0045] Reference Figure 2 The hardware environment of the device for running the fieldbus slave device software involved in the implementation scheme of this application includes: a processor 1001, an internal bus 1002, a fieldbus communication interface 1003, a network interface 1004 and a memory 1005. Specifically:

[0046] 1) Processor 1001 is running an embedded operating system and application programs.

[0047] 2) The internal bus 1002 is used to realize the connection between these hardware and internal data interaction.

[0048] 3) The field bus communication interface 1003 is used to implement the field bus communication function, including but not limited to RJ45, RS485, RS232, CAN, M12 interface, wireless and other hardware communication interface forms required by various industrial field buses.

[0049] 4) Network interface 1004 is used for debugging, program downloading and other TCP / IP-based communication functions, using a standard Ethernet interface.

[0050] 5) The memory 1005 is used to store the operating system, terminal applications and configuration information, and can be a high-speed RAM memory or a stable memory (non-volatile memory), such as a disk memory.

[0051] It should be noted that the processor 1001 may be a CPU.

[0052] Reference Figure 3The modular method of fieldbus slave device software involved in the implementation scheme of this application is divided into a logic function layer, a fieldbus protocol abstraction layer, a fieldbus protocol stack layer, an operating system abstraction layer, and an operating system layer. The logic function layer is the highest, the fieldbus abstraction layer is located between the logic function layer and the fieldbus communication layer, the fieldbus communication layer is located between the fieldbus abstraction layer and the operating system layer, the operating system layer is located between the fieldbus layer and the operating system layer, and the operating system layer is located at the bottom.

[0053] Reference Figure 3 The logical function layer includes but is not limited to the following functional components: module operation component, module management component, log component, diagnostic component, digital quantity component, analog quantity component, and protocol adapter component. The above functional components are described in detail as follows:

[0054] 1) The module running component is responsible for reading the component description file, obtaining the configuration information of each component, and loading other functional components to run according to the configuration information.

[0055] 2) The module management component is responsible for managing all connected expansion modules and is the main functional component for implementing remote IO devices and coupler devices.

[0056] 3) The diagnostic component is responsible for diagnosing the device's own operating status and managing the operation of each component.

[0057] 4) The digital input component is responsible for realizing the digital signal acquisition function.

[0058] 5) The digital output component is responsible for realizing the output function of digital signals.

[0059] 6) The analog input component is responsible for realizing the analog signal acquisition function.

[0060] 7) The analog output component is responsible for realizing the output function of the analog signal.

[0061] 8) The communication component is responsible for realizing data interaction with field bus devices.

[0062] 9) The protocol adapter component is responsible for defining standardized functional interfaces and data formats.

[0063] 10) The log management component manages the internal log data generated when the above components are running.

[0064] Abstract the underlying devices, shield the heterogeneity of the underlying fieldbus device hardware platforms, provide calling interfaces in the form of components, and improve software reusability and development efficiency; the protocol adaptation module solves the differences in fieldbus communication protocols and meets the various real-time requirements of different tasks; a node control station container design scheme with strong ease of use, high reliability, and high scalability is proposed to unify the support interfaces of the underlying devices and components. The system is highly open and convenient for the development of new business scenarios and system maintenance.

[0065] Reference Figure 3 The fieldbus protocol stack abstraction layer is responsible for abstractly describing the bus protocol stack based on object-oriented thinking according to the fieldbus communication protocol type. Figure 4 As shown, the fieldbus slave protocol stack abstraction layer extracts the common parts of different fieldbus slave protocol stacks, defines a unified form of function pointer variables, and defines a unified functional interface and data type for the next layer of fieldbus protocol stack. The fieldbus abstraction layer is responsible for providing standardized functional interface definitions and standardized data format definitions for the protocol adapter components in the logical function layer described in 2.

[0066] It allows software designers to avoid having to worry about the heterogeneity of underlying devices and networks, while increasing software reuse and enabling rapid implementation of specific services.

[0067] Reference Figure 3 The fieldbus layer will include but not limited to the protocol stacks of different fieldbuses such as PROFINET, EtherCAT, EtherNetIP, MODBUS, CANopen, etc., and will be integrated in the form of components, specifically including:

[0068] 1)PROFINET master and slave.

[0069] 2) EtherCAT slave.

[0070] 3)ETHerNetIP protocol stack.

[0071] 4)MODBUS communication protocol includes RTU and TCP protocols.

[0072] 5)CANopen master and slave.

[0073] Traditional fieldbus slave device software requires different software to be developed for different protocols, and different interfaces to be developed for different slave protocol stack software. The slave protocol stack configuration information involved in the implementation scheme of the present application improves the adaptability of the expansion system and reduces the cost of development, debugging, and maintenance through the slave configuration information in the device memory.

[0074] Reference Figure 3The operating system abstraction layer provides an abstract interface for the fieldbus layer, which is specifically divided into an operating system abstraction component and a hardware driver abstraction component, which are described in detail as follows:

[0075] 1) The operating system abstraction component is responsible for abstracting the multitasking interface and time interface of the operating system.

[0076] 2) The hardware driver abstraction component is responsible for abstracting the communication interface used by the field bus.

[0077] 3) Hardware driver abstract components include but are not limited to RS485 communication, CAN communication and Ethernet communication.

[0078] There are many kinds of fieldbuses currently used in industrial fields. The operating system abstraction layer involved in the implementation scheme of the present application can integrate multiple fieldbus communication interfaces to improve adaptability and flexibility.

[0079] Reference Figure 4 , the contents in the device memory of the modular method for running the fieldbus slave device software involved in the implementation scheme of the present application include:

[0080] 1)Embedded operating system.

[0081] 2) Functional component configuration information.

[0082] 3) Fieldbus protocol stack configuration information.

[0083] Reference Figure 5 , the modular approach of the fieldbus slave device software will perform the following steps when reading and parsing the functional component configuration information:

[0084] 1) Read the functional components included in the fieldbus slave device.

[0085] 2) If the reading is successful as described in step 1, the configuration information in the functional component is parsed.

[0086] 3) The functional component configuration information described in step 2 is passed to the operation component for loading and operation.

[0087] Reference Figure 6 , the modular approach to fieldbus slave device software will perform the following steps:

[0088] 1) According to the ModSystem item in item 8 above, determine the information of the running component.

[0089] 2) According to the ModRuntime item in the above item 8, determine the information of the management component.

[0090] 3) According to the DevUartDrv item in item 8 above, determine the serial communication interface information.

[0091] 4) According to the DevCanDrv item in item 8 above, determine the CAN communication interface information.

[0092] 5) According to the DevEthernetDrv item in item 8 above, determine the Ethernet communication interface information.

[0093] Reference Figure 6 The modular method of the fieldbus slave device software will read the fieldbus information in the memory of the controller and parse the fieldbus information. The specific information is as follows:

[0094] 1) Determine whether the fieldbus slave module is a PROFINET IO device through [PROFINET] and follow the PROFINET information in the above step 2.

[0095] 2) Determine whether the fieldbus slave module is an EtherCAT slave device through [EtherCAT] and follow the EtherCAT information in step 2 above.

[0096] 3) Determine whether the fieldbus slave module is an EtherNetIP slave device through [EtherNetIP] and follow the EtherNetIP information in the above step 2.

[0097] 4) Determine whether the fieldbus slave module is a MODBUS device through [MODBUS], and based on the MODBUS information in the above step 2.

[0098] 5) Determine whether the fieldbus slave module is a CANopen device through [CANopen] and follow the CANopen information in the above step 2.

[0099] The present invention also provides a server device, which may include at least one processor, a memory, an input / output device, and a communication bus, wherein the input / output device may include a display screen (Display) and a keyboard (Keyboard), and the optional communication interface may also include a standard wired interface and a wireless interface. The memory may be a high-speed RAM expansion module (Random Access Memory) or a non-volatile memory expansion module (non-volatile memory), such as at least one disk expansion module. The communication bus may be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus, etc. The communication bus may be divided into an address bus, a data bus, a control bus, etc.

[0100] The processor may further include a hardware chip. The hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD) or a combination thereof. The PLD may be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL) or any combination thereof.

[0101] The above contents are merely examples and explanations of the concept of the present invention. Those skilled in the art may make various modifications or additions to the specific embodiments described or replace them in a similar manner. As long as they do not deviate from the concept of the invention or exceed the scope defined by the present invention, they shall all fall within the protection scope of the present invention.

Claims

1. A modular method for fieldbus slave device software, characterized in that: include: Step 1: Fieldbus slave device configuration; Step 2: Modularization of fieldbus slave device software; Step 3: Fieldbus slave protocol abstraction; Step 4: Information storage.

2. A modular method for fieldbus slave device software according to claim 1, characterized in that: The fieldbus slave device configuration includes a controller unit, at least one expansion module unit and a server. The controller unit of the fieldbus slave device includes a CPU, a memory, a slave chip interface and an external Ethernet interface. The software of the fieldbus slave device is implemented using a layered architecture.

3. A modular method for fieldbus slave device software according to claim 1, characterized in that: The fieldbus slave device software is modularized, including a logic function layer and a user function layer. The logic function layer is located at the top of the human-computer interaction system architecture, organizing and coordinating specific program operations, parameter reading and writing, device diagnosis, and expansion module management. The user function layer is located at the top of the software architecture, presenting the functions of the fieldbus device in a modular form. The function layer realizes specific device functions, such as code processing, operation status diagnosis, alarm, data acquisition, and expansion module management. Ultimately, the operation management, data transmission, file storage and other operations of the actual fieldbus equipment are realized.

4. A modular method for fieldbus slave device software according to claim 1, characterized in that: The fieldbus slave protocol is abstracted, and the specific process is as follows: The fieldbus slave device software will add a fieldbus abstraction layer to the layered structure, including a protocol stack abstraction layer, which is used to abstract the common interface of the slave protocol stack software and use a unified interface form to the application layer. It will abstract the common parts of different fieldbus communication protocols, or abstract the interface part of the fieldbus protocol chip.

5. A modular method for fieldbus slave device software according to claim 4, characterized in that: The fieldbus slave device software will add a fieldbus abstraction layer in the layered structure, including an operating system abstraction layer, provide a calling interface to the fieldbus layer through an interface, and adapt to the lower operating system layer.

6. A modular method for fieldbus slave device software according to claim 5, characterized in that: The fieldbus slave device software can realize slave remote IO, slave coupler, and slave device through a set of methods; the fieldbus slave device software enables corresponding slave functions through configuration information.

7. A server for running a fieldbus slave device according to claim 1, characterized in that: The information storage, the configuration information required by the fieldbus slave device will be stored in the local storage medium.

8. An analysis device for executing the modularization method of fieldbus slave device software according to any one of claims 1 to 7, characterized in that: The protocol parsing device includes: a memory, a processor, and a computer program stored in the memory and executable on the processor. When the computer program is executed by the processor, the steps of the modular method of field bus slave device software described in any one of claims 1 to 7 are implemented.

9. A computer-readable storage medium for executing the modularization method of fieldbus slave device software according to any one of claims 1 to 7, characterized in that: The computer-readable storage medium stores a fieldbus device integration software program, and when the fieldbus device integration method program is executed by a processor, the steps of the modularization method of fieldbus slave device software according to any one of claims 1 to 7 are implemented.

Images