Method for controlling an automated I / O device system
The method of generating application-specific description files through a support tool automates the integration of IODD parameters into gsdml files, addressing inefficiencies and errors in existing I/O device system configurations, enhancing convenience and reliability.
Patent Information
- Authority / Receiving Office
- DE · DE
- Patent Type
- Patents
- Current Assignee / Owner
- IFM ELECTRONIC GMBH
- Filing Date
- 2021-01-15
- Publication Date
- 2026-06-25
AI Technical Summary
Existing methods for configuring and integrating field devices in I/O device systems are cumbersome, error-prone, and require manual searching for correct IODDs, leading to inefficiencies and potential mismatches.
A method involving the use of application-specific description files, generated by a support tool, which automatically retrieves and integrates IODD parameters into a gsdml file, eliminating the need for manual IODD location and ensuring compatibility with the production process.
Facilitates convenient, reliable, and efficient configuration of field devices by automating the integration process, reducing time and error risks, and enabling flexible handling of field devices within I/O systems.
Smart Images

Figure 00000000_0000_ABST
Abstract
Description
The invention relates to a method for controlling an automated IO device system for executing a production process. It is known from the prior art to supplement an existing I / O device system with new devices, typically sensors or actuators, and to connect and configure or reconfigure these devices accordingly on the fieldbus of the I / O device system. For this purpose, description files (e.g., gsdml files) are provided for the respective fieldbus device. The description file can be loaded into the programming environment of a PLC (programmable logic controller) so that the user can perform the actual configuration, which ultimately enables the device to operate in conjunction with the I / O device system. This configuration, in turn, requires a number of fieldbus device-specific parameters, which the user can read from the I / O Device Description (IODD). German patent DE 10 2011 005 062 A1 discloses a method for providing data from a field device for which an automation platform is available that identifies the field device and assigns it data enabling standard operation of the field device. Customer-specific registration is offered as an extension option. Against this background, the object of the invention is to provide a method for controlling an automated IO device system that allows for more convenient and less error-prone device implementation and control. The problem is solved, starting from control methods of the type mentioned at the outset, by the characterizing features of claim 1. The measures mentioned in the dependent claims make advantageous embodiments and further developments of the invention possible. Accordingly, the invention is characterized in that the parameters from the IODD (IO-Device Description) including the article number of the device are transferred into the application-specific description file, typically a gsdml file. An I / O (Input / Output) device system is, for example, a system or machine used to execute a production process with specific production parameters. Sensors and other devices are used to monitor the production process. The individual devices are interconnected via a network or bus. Often, the devices are configured as slave input / output link devices in the bus hierarchy, while a part of the existing I / O system acts as the I / O master, such as the I / O controller, which runs control software. One possibility is the use of fieldbus systems connected via an industrial Ethernet standard like PROFINET, which uses TCP / IP and IT standards. For a field device (IO device), a description file (e.g., in gsdml format) is generally provided to make it readable, evaluable, and configurable. According to the invention, a description file is used for a field device that is connected to the PROFINET network of the device system. Traditionally, according to the state of the art, another form of description file, the so-called IODD, has been used, which contains further parameters of the field device as well as information such as the article number of the field device, the software / hardware version, etc. The IODDs are provided in a configuration database. According to the invention, the implementation of a field device can initially be simplified by eliminating the need to locate the IODDs belonging to a field device. According to the invention, configuration software, in particular MES (Manufacturing Execution Software) or an engineering tool (e.g., the so-called "TIA Portal" (Totally Integrated Automation) from Siemens), is executed. This software scans the network for additional field devices connected to the fieldbus and detects them. The configuration software also accesses the configuration database and selects the appropriate IODD for the detected field device. The configuration database can be an internal database of the support tool, and / or the support tool can access an external configuration database. It is also conceivable that the support tool has an internal configuration database and, additionally, accesses an external configuration database for specific IODDs in specific applications. The invention is characterized by the creation of an application-specific description file into which the parameters stored in the IODD corresponding to the field device currently being configured, which is usually newly connected to the network, are additionally inserted. The application-specific description file can typically be in or generated in the gsdml format. For this purpose, the configuration software uses a support tool, in particular a PCT tool (e.g. on an LR device), which generates the application-specific description file, in which this description file for the field device is supplemented by the parameters of the IODD from the configuration database. Depending on the specific implementation, an IODD can initially be uniquely assigned to a field device via an identification number such as the article number. The assignment of the IODD from the configuration database to the corresponding, identified field device can also be performed taking into account production parameters, particularly critical production parameters, of the respective production process. The support tool accesses the connected field devices via the gateway, which provides access to the network or fieldbus. Simultaneously, it is connected to the configuration database to locate the IODD, for example, via an Ethernet connection. The configuration database can be in the form of an external database (External Description Files database), which must be accessed, for example, via the internet. The configuration database can, for example, be stored in a cloud. To execute the control process, the generated application-specific description file is then loaded onto the I / O controller and / or the control software. The support tool transfers the application-specific description file to the configuration software (e.g., the engineering tool), so that the I / O controller or the control software loads the configuration via the configuration software (e.g., the engineering tool). This makes the configuration of a newly connected or newly configured field device significantly more convenient and reliable, especially since: - configuration does not have to be done using external tools, - the entire device implementation can be carried out using the existing configuration software (e.g., the engineering tool), - no more time has to be spent finding the correct IODD, - there is no longer a risk of using the wrong IODD, which does not fit the field device, when searching manually, and - the configuration and implementation of a field device can therefore be carried out much more conveniently overall. Depending on the specific implementation, the configuration software (engineering tool) allows for particularly easy and quick graphical programming. In one embodiment of the invention, a newly connected field device, such as an additional sensor or actuator, can be assigned to a group of existing sensors or actuators that are used to execute a specific application (e.g., monitoring the fill level or filling of a tank). The IODD and the parameters stored therein are then also adapted to this application, so that the IODD is advantageously tailored to the production process. In particular, the I / O controller or the control software can be designed as part of a programmable logic controller (PLC) for control, i.e., for controlling and / or regulating the production process, since this allows for more flexible handling and configuration, especially when replacing or adding field devices, unlike a hardwired controller. Especially when a production process application comprises multiple IO-Link master gateways and, consequently, multiple field devices, such as sensors or actuators, these can be grouped together in an application-specific manner. In this embodiment of the invention, the application-specific description files (e.g., gsdml files) are adapted to this application and thus to the production process. This may require not only adding parameters from the IODD, but also adapting parameters to the production process depending on the field device, or assigning and using an IODD specific to the production process. For this purpose, processing via a further configuration and optimization tool can be interposed between the configuration software (engineering tool) and the support tool, e.g., via file export to an AML format and processing using software such as that sold under the trade name "EPLAN".Files in AML format can be transferred to the configuration software, even without further modifications. In a further development of the invention, the already modified or adapted application-specific description file can be transferred to the configuration and optimization tool. Conversion from XML to AML format is possible in this process. In such a further development, the configuration software can also include the interposition of another configuration and optimization tool, such as the integration of software like "EPLAN" described above. Advantageously, the entire application can thus be transferred to the PLC and the IO-Link master gateways without further intervention. In an advantageous embodiment of the invention, the support tool can include a configuration model for accessing and configuring the field device. Furthermore, the support tool can use a data buffer as temporary storage during communication with the I / O field device and / or as temporary storage for parameters used to generate the application-specific description file. In these embodiments of the invention, the support tool constitutes a self-contained, computer-implemented form of a tool used to generate the application-specific description file. In this context, the term parameter can include both field device parameters and production parameters. In one embodiment of the invention, the application-specific description file generated using the generation function integrated into the support tool can have the following structure: The support tool accesses its data buffer and extracts the parameters read from the corresponding field device. Using this data, the support tool searches for the IODD (Integrated Data Distribution) of the corresponding field device in the internal or external database. This is done, for example, by using the field device's article number, which was read from the field device by the support tool and temporarily stored in the data buffer, and thus searching for the matching IODD in the internal or external configuration database. An existing description file (e.g., a gsdml file) of the field device can then be supplemented with the parameters of the cache and / or the IODD, according to the following structure for the application-specific description file template: - Header: The header requires data or parameters from the cache and / or the internal or external configuration database. - Parameter section: This also requires data or parameters from the cache and / or the internal or external configuration database. - Specification of further optional components - Other sections with specifications or definitions: e.g., the definition of constants. Example of implementation An embodiment of the invention is illustrated in the drawing and explained in more detail with further details and advantages. Specifically, Fig. 1 shows a schematic representation of the control method according to the invention. Fig. 1 shows individual field devices 1 that communicate via a gateway 2 within the I / O device system, in particular with the I / O controller 3, here a programmable logic controller (PLC), which also communicates via the gateway 2. Data is exchanged during this communication. For configuration, parameters P (e.g. article number, production-specific data, field device-specific information) are usually exchanged between the field devices 1 and the controller 3 via the gateway 2. For the configuration of, for example, a newly added field device 1, configuration software, here an engineering tool 4, is used. The configuration generated with this engineering tool 4 can be loaded and used by the I / O controller 3. According to the invention, the configuration software 4 utilizes the support tool 5, which has a configuration function 6, a data buffer 7 for temporarily storing the field device-specific or production process-specific parameters, and optionally further functions 8. The IO controller 3 can detect a new field device 1 via gateway 2. The support tool 5, used by the configuration software 4, also accesses the field devices 1 via gateway 2. Parameters P are transmitted from the field device 1, which is to be configured or integrated, to the support tool 5. The support tool 5 assigns an IODD to the field device 1 and accesses an internal configuration database 9 or, optionally, an external configuration database 10 via an Ethernet connection 11 for this purpose. The support tool 5 also has a generation function 12 to supplement the field device-specific description file (the gsdml file) with the IODD parameters P and generate an application-specific description file that is available to the configuration software 4. The entire configuration package can then be transferred to the controller 3. The configuration software 4 can also provide an intermediate configuration and optimization tool 13. The description file is converted from XML format to AML format by the support tool 5 after its generation and loaded by the configuration and optimization tool 13. The description file, also in AML format, can then be transferred to the controller 3 via the engineering tool 4. The newly connected field device 1 is integrated into the I / O device system conveniently, without significant time expenditure or increased susceptibility to errors, thanks to the automation according to the invention. All embodiments and further developments of the invention have in common that the parameters from the IODD, in particular including the device's article number, are transferred to the application-specific description file, typically a gsdml file. Reference symbol list 1 Field device 2 Gateway 3 Controller / programmable logic controller 4 Configuration software / engineering tool 5 Support tool 6 Configuration function 7 Data buffer as intermediate storage 8 Optional functions 9 Internal configuration database 10 External configuration database 11 Ethernet connection 12 Generation function 13 Configuration and optimization tool P Parameters
Claims
Method for controlling an automated I / O device system for executing a production process with at least one production parameter (P), wherein the I / O device system comprises an I / O controller (3) with control software and at least one I / O field device (1), which are interconnected via a PROFINET network with a gateway (2) as a software and / or hardware interface for communication over the network, wherein the gateway (2) is an IO-Link master gateway, wherein the method for integrating the field device (1) into the I / O device system comprises: • providing a description file in gsdml format • executing configuration software (4), in particular an engineering tool, and scanning for further I / O field devices (1) via the network • recognizing the I / O field device (1) by the configuration software • providing a configuration database (9, 10) which includes at least one IODD of the field device (1).• Providing a support tool (5) for generating an application-specific description file, which forms the interface between configuration software (4) and the gateway (2), • wherein the support tool (5) includes a configuration module for accessing and configuring the I / O field device (1), • wherein the support tool (5) uses a data buffer (7) as temporary storage during communication with the I / O field device (1) and / or as temporary storage for parameters (P) for generating the application-specific description file, • Generating an application-specific description file in gsdml format via the support tool (5), wherein the support tool (5) is a standalone, computer-implemented form of a tool with which the description file to be used application-specifically by the support tool (5) is generated by supplementing the description file in gsdml format,i. Assigning an IODD according to parameter (P) of the IO field device (1) and according to production parameter (P); ii. Adding at least one parameter (P) and the article number from the IODD to the application-specific description file; iii. wherein the support tool (5) assigns the IODD to the field device (1) and accesses an internal configuration database (9) or an external configuration database (10) via an Ethernet connection (11) for this purpose; • Transferring the application-specific description file as a gsdml file to the IO controller (3) and the control software via the configuration software (4); • Executing the control software to control the IO field device (1); • Using a configuration and optimization tool, exporting the application-specific description file as an AML file. Method for control according to one of the aforementioned claims, characterized in that the configuration database is provided as: • an external database (10) on a computer connected to the network or to a communication network separate from the network, in particular to an Ethernet communication (11), and / or • an internal database (9) that is integrated in the support tool (5). Method for control according to one of the aforementioned claims, characterized in that the IO controller (3) and / or the control software is used as part of a programmable logic controller for controlling the production process. Method for control according to one of the preceding claims, characterized in that the control software is exported and executed as an AML file after the application-specific description file transmitted to it has been integrated. Method for control according to one of the aforementioned claims, characterized in that the configuration software (4) and / or the support tool (5) recognizes the IO field device (1) on the basis of an identification number stored on the IO field device (1), in particular the article number. Method for control according to one of the aforementioned claims, characterized in that the configuration software (4) and / or the support tool (5) performs the assignment of the IODD based on at least one parameter (P) critical for the production process. Method for control according to one of the aforementioned claims, characterized in that the configuration software (4) is designed as MES software.