DE10208530A1 - Method for configuration and operation of peripheral devices connected to a host unit via a field bus in which the peripherals are supplied with a configuration file so that they can be directly configured by the host over the bus - Google Patents

Abstract

Method for operation of one or more peripheral devices (14a-14c) using a host unit (11) that recognizes, configures and or operates the peripheral devices. In order to configure a peripheral device, the host unit uses a device configuration file that is made available to the host unit by the peripheral device. The invention also relates to corresponding operating unit and peripheral device.

Description

The invention relates to a method for operating a peripheral device by means of a host Unit in which the peripheral device is recognized, configured and / or by the host unit is operated. The invention further relates to an operating unit, comprising a host unit and a peripheral device connected to it, in which the peripheral device from the host Unit is recognizable, configurable and / or operable. The invention also relates to a Peripheral device, having an interface unit for providing a Communication channel to a host unit, as well as a peripheral device by a host unit is recognizable, configurable and / or operable.

An operating unit typically has a peripheral device that is provided by a host unit is controlled via a bus. The peripheral device usually takes on the role of one Slave unit and works according to the instructions of the host unit which the Position of a master unit. With such an operating unit, peripheral devices and host unit can be connected to each other via a bus, which is the communication between master and slave.

For example, the bus can function as a fieldbus in a network environment be trained or as a direct connection between master and slave.

The host unit mentioned can be, for example, a master programmable memory. Control (master PLC) in the context of a control system or a common one Personal computer (PC) in the context of a computer network or a simple local PC unit. In the case of the master PLC, a peripheral device can, for example, use a fieldbus connected field device. In the case of the PC, for example, a peripheral device Printer, monitor or a modem.

In automation technology, for example, a control system is used Master PLC connected to a field device via a bus. For example, a is common Profibus as DP or FMS version. Such operating units are explained for example in "TAGUNGSBAND SPS / IPC / DRIVES, Electrical Automation Technology - Systems and components, trade fair & congress ", Günther Brandenburg et al., Nov. 23-25. 1999, Nuremberg, Hüthig. There is also a description of common operating units programmable logic controllers in "PROFIBUS-DP, basics, tips and tricks for User ", Manfred Popp, Hüthig, Heidelberg, 1998. Those in automation technology Common engineering tools usually require precise knowledge of variables and parameters of the fieldbus system and especially the connected fieldbus participants, so the peripheral devices. Engineering tools include tools such as Programming systems, fieldbus configurators, commissioning tools, B&B systems, So systems for operating and monitoring, as well as control systems, in particular also Control systems with which a visualization of processes is possible. Engineering tools also include tools that perform similar tasks as the examples mentioned. The knowledge mentioned is not part of an engineering tool, especially not part of a control program or control system. Appropriate Information is therefore not available on a host unit. For the description of device Properties represent the necessary information for field devices with variables, Parameters and partly also the functions are available in machine-readable form. The So-called device descriptions are published by the manufacturer of the device Example as part of the certification of the device. Such certification is for example known from "PROFIBUS Journal, PROFIBUS Open Solutions for the World of Automation July / August 01 "- Page 6ff:" Device engineering with GSD ", PROFIBUS user organization e. V. (PNO). It is explained that by reading the device description, the engineering Tools can be set to the device specifics. With all known Fieldbus systems have such description files separately on appropriate data carriers available. Examples of fieldbus systems are the Profibus-DP or the CAN-Bus or the HART- Bus. There is a device file for an operating unit working with the Profibus-DP for example as a device master file (GSD) or as an electronic device description (EDD) Available. In the case of the CAN bus, a device file is available, for example, as an electronic Data sheet (EDS) available. In the case of a HART bus, there is a device file Form of the Device Description Language (DDL).

The manufacturer of a device usually provides the appropriate description file, i. e. Device file, either on diskette for the device, publishes it in another way or makes it available for download on its own web server. In the case of Profibus-DP is such a download version, for example on the PNO web server above Profibus user organization available. The manufacturer must ensure that all published description files of a device are identical and at Further developments of the device for downward compatibility is considered. Furthermore, the Users get the device description files they need after getting them from the manufacturer in its engineering tool, for example a fieldbus configurator, install and can then work with the devices. However, usually delivers one Device file, for example the GSD file for a Profibus-DP, a fieldbus device only information about the number of bits / bytes of input / output data and the number and types of modules that can be arranged in a field device. However, it will does not define what the exchanged data represent, for example it does not represent which data types (analog, digital, floating point, integer value, etc.) the represent exchanged data.

A previously common handling of a device file is, for example, in the German Patent application DE 100 49 025 A1 described. Previous measures have been limited exclusively on the design of a GSD file, but do not extend to one Integration of a device file as part of an operating unit or a process for Operation of a peripheral device.

So far, the user has to have the required device description files Install engineering tool and can then work with the devices. In DE 100 49 025 A1 it is described that a fieldbus line consisting of fieldbus participants and the Fieldbus master must be configured independently of the rest of the control system. The system engineer must first set up the network. Then under Use of an available configuration tool, which usually runs on a PC and connected to the fieldbus master, data are entered that the fieldbus participants specify. The configuration tool then configures and specifies the fieldbus master thereby the memory locations in the fieldbus master for use for each of the signals that is received by or sent to a fieldbus node. In the next The PLC must be programmed to save data from the memory locations of the Fieldbus participants to receive and send there. Such a multi-step Configuration process is time consuming, must be separate and besides the configuration of the control system be carried out and requires the input of the data regarding the fieldbus participants in two or more systems at different times, resulting in errors or malpractice in configuration or documentation.

Regarding operating units that have a PC as a master, a so-called driver is usually provided for the integration of peripheral products, for example a printer, which is usually installed manually using an operating system, for example Microsoft Windows NT. In the example mentioned, before a peripheral product, for example the printer, can be used, it is installed and configured. This is done either when the operating system is installed or only later when a peripheral product is required. For this purpose, a special operating system program is usually called, from which the desired printer can be selected and configured in this example. The operating system usually has a number of predefined devices from which to choose. If the device is not found there, the necessary description files, ie drivers, must be read in and installed using a separate data medium, for example a floppy disk. These are usually included separately with the device, for example in the form of a floppy disk, or can be downloaded from a website of the respective manufacturer. The so-called "Plug &Play" technology can also be used with newer versions of MS Windows. This technique determines how a device can be identified in relation to the operating system and thereby tells which resources it needs and what a software driver must be such that Windows can locate and load it after the device has been identified. This method relieves the user of having to call up the installation programs for new devices. This measure is taken over automatically. However, in this case too, the device drivers are available separately on a separate data carrier medium and may have to be reloaded manually, as described above. A device file for a PC operating unit, i.e. a PC device driver, consists of descriptive files that describe the behavior of the peripheral device, in this example the printer, and the resources required by the device (e.g. I / O ports, interrupts, etc .) and general properties (e.g. input devices, mass storage devices, etc.) and software (drivers) that are installed in the operating system and access the device at a lower level. The installation of a device driver is known, for example, from "Peter Norton's Windows NT 4 Workstation", 1997, ISBN 3-87791-889-1, Chapter 14.1 - "Installing and Removing Devices".

The following is used for the terms "device description file" and "driver software" The term "device file" is used. For the terms "field device" (for example drives, Valve terminals or I / O fieldbus components, digital or analog counters etc.), "Fieldbus subscriber", "PC peripheral product", i.e. any type of slave device (e.g. printer, Monitor, monitor card, mouse or modem), the term "peripheral device" used. For the terms master PLC, control system, PC or similar, i.e. any type of one Master unit, the term "host unit" is used. Furthermore, refers to following the term "bus" to any type of data connection between the host unit and Peripheral device, for example a fieldbus, a direct data line or also a Radio link.

The described way of handling device files for field devices in the Automation technology as well as PC peripherals has a number of significant ones Disadvantages. So it is usually for the complete and correct use of a Peripheral device absolutely necessary that a device file clearly matches a device. Becomes the device cannot be operated or can only be operated partially become. However, unwanted misconduct can also occur, such as this is described for example in DE 100 49 025 A1. In particular, in the course of Further developments of the devices may be necessary for the user, one for each device version Keep the device file. Given the large number of fieldbus participants or PC Peripherals this easily leads to a significant and time consuming Administrative expenses. It may also be necessary in the course of maintenance work, a defective one or not replace the intact device. If a more current device is used in this case, and This is particularly common in the PC area, but for which the configuration does not fit, it can be in the problems in subsequent operations. Especially in the area of networkable PC Peripherals, such as printers, incur the effort to install Device files per workstation and not per device. This multiplies the one described above Problems. In particular, it is common in larger companies that end devices such as printers are not installed by the user, but by specialized personnel. With that, the individual users but no direct access to the required device files usually included with the device. It also means a significant amount for the manufacturers Logistics effort, identical stands for all devices and all versions on all delivery routes or to keep device files.

In particular, however, it means a considerable one for the user of peripheral devices Effort to keep all required device files consistently at all locations. This is for example, the case with LapTops used by service personnel. service personnel therefore usually does not have device files today. In the case of maintenance work, it can therefore to a procurement problem with subsequent downtimes of a machine or plant, which can mean a considerable cost. The biggest The main disadvantage, however, is the need for an installation procedure Device file justified by the user. In addition to the time involved in this procedure due to incorrect operation, error situations during installation and arise during operation.

This is where the invention comes in, the task of which is to provide a method for operating a Specify peripheral and a device so that a peripheral on particular can be put into operation in a simple manner.

The object is achieved by a method of the type mentioned at the outset, in which According to the invention for the configuration of the peripheral device, the peripheral device Descriptive device file of the host unit is provided by the peripheral device.

The essential finding of the invention is a device file in one To accommodate peripheral device, and to make available together with the peripheral device.

This has a number of advantages over previously common measures, one Make the device file available outside the peripheral device and on separate data carriers. This completely eliminates the need to procure device files. These are now available in the devices themselves. It is therefore always ensured that the content of the device file matches the device. Confusion is no longer possible. It all logistic provisions for storage, backup and Maintaining the consistency of device files, since these are present in the devices themselves. In addition, on Manual installation procedures for device files that were previously required are no longer required. On the one hand, this saves time and costs, on the other hand, incorrect operation and so that errors in the configuration and documentation no longer occur. At the Manufacturers in particular dispense with the precautions and thus the costs, device files either with the devices on separate data media, i.e. floppy disk or CD, or in Available on the Internet or at mailboxes. This essentially eliminates the im Connection with the listed prior art disadvantages in a method and the devices of the proposed type.

Advantageous developments of the invention can be found in the subclaims and specify advantageous options in detail, a device file in a peripheral device save, load a device file from a peripheral device and use it appropriately, for example in a configuration tool, as well as a device file advantageously on a Save host unit.

With regard to the method, the device file is preferably imported from the peripheral device Configuration tool added. The configuration tool preferably instructs Software module into which the device file is loaded. In particular, it is in other words, a program that advantageously specifies or carries out all of the steps that a device file describing the peripheral device of the host unit from the To provide peripheral devices. This has the advantage that the user in the Usually no measures, or if so, only those requested by the configuration tool Action to take. The configuration tool is preferably part of a initially explained engineering tool. The configuration tool could also be part the host unit, in particular a processor unit and / or one Have memory. In such a memory, for example, a corresponding one Configuration routine stored or executed from there.

It is preferably provided in the proposed method that the Configuration tool to get the host device device file describing the peripheral device from the To provide peripheral devices that access a bus over which the Peripheral is connected to the host unit. A bus could be a fieldbus or a direct one Data connection. A peripheral device is used with the configuration tool saved device file recognized, this from the initial state into a Data exchange status shifted, the device file from the peripheral device to the configuration tool transferred and the peripheral device returned to the initial state. Will be beneficial transfer the device file to the host unit. The aforementioned special process sequence for the operation of the peripheral device leads to the fact that the peripheral device is recognized and all necessary information about the peripheral device, the configuration tool, especially the host unit. This information is, it shouldn't already the host unit, for example in the form of standard device files or already on the Device files stored in the host unit are available in the according to the proposed method in a peripheral device stored device file. The The aforementioned further development of the process sequence enables an effective and with already on Location of existing specifications for host units, bus systems and peripheral devices compatible structure. After thus, in particular after the aforementioned training of proposed method, the host unit all information about connected Peripherals are available, they can be used in a suitable manner for operation configured and operated subsequently.

In the aforementioned development, an im is advantageously used for data exchange Configuration device provided for the peripheral device activated, the device file from Transfer peripheral device to the configuration tool and the peripheral device in the initial state offset, in particular by deactivating the configuration reporting unit of the peripheral device becomes. For the transfer of the device file describing the peripheral device is therefore in Peripheral device provided a specially provided configuration reporting unit, which communicates with the configuration tool in the proposed method and the Data exchange regulates.

The device file is advantageously transmitted in segments, that is to say in several parts. In part namely it is cheap or necessary to size the transferred part to the cycle of Adjust net data specified by one bus per participant. So could For example, an upper limit for Profibus-DP of a maximum of 246 bytes for one part be specified so that the device file is transferred in segments of a maximum of 246 bytes can.

The following are four preferred developments of the proposed method described, which offer the possibility of the proposed method on a special Application requirement according to, for example, a network environment, one Automation requirement or a PC operating unit.

For example, it may be advantageous in the context of further training, only one Peripheral device for which the host unit does not yet have a device file available recognize, and in particular only to put such in a data exchange state. This has the advantage that peripheral devices for which the host unit already has a device file is present, not recognized, addressed or put into a data exchange state have to. Such an approach leads to an effective, time-saving and therefore cost-saving execution of the proposed method.

According to a further preferred development of the proposed method a general device file can also be provided, which in particular is a peripheral device at least for the purpose of data exchange in the device file. It it is particularly preferred that the peripheral device through the general device file is pre-initialized to make the device file available from the peripheral device of the host unit put. This ensures that a peripheral device for data exchange Device file is recognized safely and correctly. A pre-initialization by a general device file has the advantage that the device file and thus the description of a peripheral device, regardless of a test for the special design of a peripheral device, accordingly a standard taken into account from the general device file. Such a blanket handling of all peripheral devices enables one Device file describing the peripheral device of the host unit from the peripheral device is very time-effective to provide.

According to yet another advantageous development of the proposed method the device file could also be sent from the peripheral device to a class 2 host device Will be provided. This could be a subordinate or subordinate to a class 1 host unit and as a largely self-sufficient host unit in a regional or local network section of an entire network. The proposed method can thus be advantageous can also be used in a decentralized network or automation environment. A class 1 host unit is a master unit in the usual sense understood how they are structured in a more or less hierarchical way Control systems, such as Suconet-K, Interbus-S, Control-Net or Device- Net. I.e. a class 1 host unit is assigned to a bus line in the usual sense which line then several peripheral devices can be connected. As part of a Such a hierarchical control system can then be one of the above Class 2 host unit can be provided, which is used in particular for parameterizing the class 1 host unit is provided, but also, similar to a conventional master unit, directly on a peripheral device of a line assigned to it can access it. In this sense it is Class 2 host unit is subordinate to a class 1 host unit. This is even more so the case with control systems that have little or none at all have a hierarchical structure, in particular similar to an Ether-Net. Because of one Such control systems per se have a rather decentralized structure host units with equal rights if there are multiple host units. For example the CAN bus is such a control system. Rather not hierarchical even for such constructed systems, the terminology of class 1 host unit and class Keep 2 host unit. The term class 2 host unit therefore denotes a host Unit which is a class 1 host unit as a more or less equal master Unit can be subordinate, but can also perform subordinate functions, that would otherwise go to a slave unit. The class 1, class 2 terminology is in the following regardless of a hierarchical or rather decentralized Control system used.

Either in an automation application or in a PC application Device file advantageously from the peripheral device of the host unit via a field bus Will be provided. According to a further preferred development of the However, the method also allows the device file to be downloaded from the peripheral device of the host To provide the unit directly bypassing the field bus. You can do this in the peripheral device separate interfaces and connectable corresponding direct Data connections, such as direct lines or radio connections, to a central or decentralized host unit can be provided.

The aforementioned four further developments of the proposed method are only one preferred selection of possible adaptations to the necessary circumstances of a Network environment or automation environment, in particular these can be in Combination or alternatively used. An application of the proposed A method or a further development of the same is possible with all electrical products, where to integrate or address the same as a peripheral device from a host computer as Host unit out driver software or description or configuration files as Device file is required. In the automation field, these are all types of electrical Peripheral devices such as drives, valve terminals, operating and monitoring devices (HMI), PLC as fieldbus device, I / O fieldbus components (digital, analog, counter, etc.), Temperature acquisition modules and other peripheral devices that are participants in one Fieldbus are suitable and / or are usually coupled as participants to a fieldbus. In the PC / IT environment, these are, for example, PC peripheral devices such as a printer Monitor, mouse or modem, which is integrated into a PC via driver software and / or addressed.

The proposed method is particularly suitable for use on a Operating unit and a peripheral device, in which a device file is provided.

The invention further leads to an operating unit of the type mentioned at the outset, by means of which the problem regarding the device is solved and in the solution to the problem According to the invention it is provided that the peripheral device for a configuration of the Peripheral device usable and having a device file describing the peripheral device, which is provided on the peripheral device of the host unit.

In particular, according to a preferred development, the operating unit can be a class 2 Have host unit that made the device file available on the peripheral device is.

The device file is advantageous on the peripheral device of the host unit via a Field bus provided. However, depending on the application, you could also have a additional interface bypassing the field bus of the host unit directly to the Be made available.

The operating unit advantageously provides instructions for recording the device file Configuration tool, which is designed in particular as a software module, but also as Hardware component can additionally or alternatively be present.

In the proposed operating unit, a peripheral device is advantageous Configuration reporting unit, in particular one designed as a software module Configuration reporting unit provided.

Finally, the invention introduces the task regarding the device Peripheral device of the type mentioned, in which to solve the task According to the invention, a device memory and a configuration message unit, which for a Data exchange with the host unit can be activated, is provided. It will be advantageous Configuration reporting unit deactivated after data exchange.

According to a preferred development of the proposed peripheral device is also a processor unit, a peripheral interface unit for providing a Communication channel to the periphery and another data memory provided.

According to a particularly advantageous and preferred development of the proposed Peripheral device, the device memory has a device file describing the peripheral device which is made available to the host unit by means of the configuration unit.

The invention with regard to the object relating to the device also introduces Peripheral device of the other type mentioned, in which to solve the task according to the invention a usable for a configuration of the peripheral device and a Device file describing the peripheral device is provided, which on the peripheral device Host unit is provided.

The proposed operating unit and / or the peripheral device is preferably corresponding the environment of a programmable logic controller designed and / or according to the environment of a PC system.

In the following, preferred embodiments of the invention are compared to the prior art described the technology. It should be noted that various modifications and Changes regarding the form and detail of an embodiment are made can without departing from the general idea of the invention. The one in the previous Description, features of the invention disclosed in the drawing and in the claims can be used individually as well as in any combination for the realization of the Invention to be essential. The general idea of the invention is not limited to the exact one Form or detail of the preferred shown and described below Embodiments or limited to an object that would be limited compared to the subject claimed in the claims.

Exemplary embodiments and embodiments of the invention are shown in the drawing described. This is not necessarily to show the embodiments to scale; rather, the drawing is only for explanation, in a schematic and / or light distorted shape. With regard to additions from the drawing immediately recognizable teachings, reference is made to the relevant prior art. In detail show the figures of the drawing in:

FIG. 1 is an operating unit in the form of a programmable logic controller with field bus and peripheral devices;

Fig. 2 is a schematic representation of a method of operating a peripheral device as part of a configuration system;

Fig. 3 is a flow diagram of a method of operating a peripheral device according to the prior art;

Fig. 4 shows a preferred embodiment of a method of operating a peripheral device, presented in the form of a flow diagram for a configuration method of a fieldbus;

Fig. 5 shows a preferred embodiment of a peripheral device for use in a preferred embodiment of an operating unit, with a schematically illustrated construction of the preferred embodiment of the peripheral device.

In Fig. 1 a programmable control system 10 is shown which comprises a programmable control unit 11. This has a programmable logic controller 11 a and several plug-in modules for application-specific organizational and functional modules 11 b, a CPU 11 d and other available slots 11 c. A plurality of peripheral devices, here field devices 14 a, 14 b and 14 c, are connected to the programmable logic control unit 11 via a field bus 13 .

For the commissioning and programming of the programmable logic control system 10 , an engineering system 12 is provided, which in particular has a PC which is connected to the programmable logic control unit 11 via a communication link 15 with the field devices 14 a, 14 b and 14 c and the field bus 13 ,

Before the field devices 14 a, 14 b and 14 c can be configured, the device files describing the field devices should be available. According to the prior art, these are provided separately and separately from the field devices 14 a, 14 b and 14 c. In the programmable logic control system 10 shown in FIG. 1, for the field devices 14 a, 14 b and 14 c corresponding device files on disks 16 a, 16 b and 16 c are used in the engineering system 12 and thus the programmable logic control unit 11 as host Unit provided.

In a preferred embodiment of the proposed operating unit, there is one Measure is also provided as a possible advantageous addition, since the Device files according to a preferred embodiment as an integral part of a field device Is made available.

A configuration system 20 is shown schematically in FIG. 2, which has a configuration tool 22 . The configuration tool 22 can be designed as a software module or also as a hardware module. Via the configuration module 22 , using device files 26 a, 26 b and 26 c, a corresponding field device documentation 25 is created, on the basis of which field devices, such as the field devices 14 a, 14 b, 14 c in FIG. 1, can be configured. The documentation and / or the device files 26 a, 26 b and 26 c can be stored in a configuration database 24 . Corresponding interfaces, data connections and data exchange routines 23 are provided between the configuration tool 22 and the units 24 , 25 and 26 a-c, and corresponding interfaces, data connections and data exchange routines 27 between the units 24 , 25 and 26 a-c. In addition, a communication link 28 is provided between the configuration tool 22 and the user as an input / output unit. A peripheral device interface 29 is also provided. A communication channel 21 , for example a direct data connection or a field bus to a field device 14 a, 14 b, 14 c, can be connected to this. In the configuration system 20 shown in FIG. 2, the device files 26 a, 26 b and 26 c are made available to the configuration tool 22 on floppy disks or another data carrier medium, but in any case separately from a field device. In a preferred embodiment of a proposed operating unit or a peripheral device, this is no longer necessary, since a device file describing a peripheral device is provided with the peripheral device itself as an integral part of the same.

In Fig. 3 in flow chart form, a configuration method of a field bus is shown according to the prior art. Only if a device file already exists in a host unit can the fieldbus be configured, the configuration can be loaded into the PLC and fieldbus operation can be started. If this is not the case, a device file must first be obtained, since this is usually not made available in the system or a field device. The procurement of a device file includes either reading from a corresponding data carrier or downloading from a dedicated website. The device file must then be read into a PC, for example an engineering system, and installed in a configuration system. A method described with reference to FIG. 2 would be used, for example. Only then could the configuration of a fieldbus be created.

Such a complex process is no longer necessary according to the proposed method. A preferred embodiment of the method is shown schematically in FIG. 4 using a flow chart for a configuration method of a fieldbus. If a device file already exists, a fieldbus configuration can be created, it can be loaded into the PLC and fieldbus operation can be started. However, if a device file is not available, the procedure is very simple. If a configuration tool used does not yet have a device file, for example from an earlier configuration, available at the time the configuration was created via the peripheral device, the configuration tool simply reads this information from the corresponding field device. For example, a configuration tool from the Profeller DP from Moeller, for example a CFG-DP device, or a configuration tool for a COM Profibus from Siemens can be used. However, the peripheral device is designed in accordance with the proposed features. A preferred embodiment of the peripheral device will be described below with reference to FIG. 5.

In particular, for the configuration and commissioning of a Profibus-DP fieldbus, For example, by a system engineer, first the fieldbus is set up in such a way that all desired field devices and the Profibus-DP master, i.e. an available host unit, be connected to each other. After that, using an available Configuration tools that are compatible with the CFG-DP Profibus or, for example, also in individual cases to the COM Profibus, which usually runs on a PC and with the Fieldbus master is connected, data entered that specify the master or the network. To For example, an available baud rate is specified. After that, the individual Field devices can be selected and appropriately parameterized. Offer to select a participant the configuration tools menus that represent known participants and from a internal database. New, previously unknown participants can join the Database can be added by the GSD file according to the proposed Procedure is loaded from the peripheral device itself. Of course it is also possible to use a GSD file as usual via a data medium To have available.

• 1. Diagnoseanforderung
• 2. Stationsadresse ändern (optional)
• 3. Parametrieren des Teilnehmers
• 4. Konfigurieren des Teilnehmers
• 5. Zyklischer Datenaustausch

In order to be able to exchange data with a Profibus-DP peripheral device, the Profibus-DP master is usually prepared according to standard EN50170, which standard provides the following telegram sequence when starting up the slave, i.e. the peripheral device:

• 1. Diagnostic request
• 2. Change station address (optional)
• 3. Parameterize the participant
• 4. Configure the subscriber
• 5. Cyclic data exchange

A device file according to the proposed method is between steps 3 with regard to the above telegram sequence, in particular in the present embodiment. and 4. executed. Depending on the design of the peripheral device and the network or automation environment, there are various options available for loading the device file into the configuration tool. In particular, one of the four options explained below is particularly suitable for a specific network or automation environment. A combination of the same or other options are of course also possible.

As a particularly preferred embodiment of the proposed peripheral device, a peripheral device 50 according to FIG. 5, which will first be described, is suitable for each of the possibilities to be explained below. The peripheral device 50 has a processor unit 56 which determines the mode of operation of the peripheral device. The processor unit 56 comprises a controller 56 a, a memory 56 b and a control program 56 c. Due to the commands of the control program 56 c reads the controller 56 a on the peripheral input / output unit 57 from the process data or the periphery and are on the peripheral input / output unit 57 data to the process or from the periphery. The data storage 59 is used for the temporary storage of data. Communication between the internal units of the peripheral device 50 takes place via a corresponding data bus 51 . The peripheral device has a configuration reporting unit 58 , which is provided for communication with a configuration tool, for example a configuration tool 22 , as described in FIG. 2. The configuration message unit 58 is not addressed in normal operation. It therefore remains deactivated in normal operation. When the peripheral device is switched on, such a device usually expects parameterization and configuration data with which information such as address, watchdog times, number of input / output bytes, baud rate etc. are determined by a host unit. This is done using the device file. After this phase, the peripheral device can switch to regular operation and exchange data with the host unit, for example in accordance with 4th and 5th of the list above.

The peripheral device 50 also has a device file memory 55 . This can be designed as a non-volatile memory, for example as EEPROM, flash or as buffered RAM. As a result, the contents of the device file memory 55 are retained even in the event of a power failure. In addition, the user / system engineer can read out the device file memory 55 but cannot delete it and thus cannot manipulate it, which is advantageous for security reasons. The device file memory 55 can be read out at any time since it is not clear from the perspective of the peripheral device 50 when a configuration tool needs the stored information. The configuration message unit 58 can of course be designed as a hardware module, as already described above, but it could also be implemented as a software module.

• 1. Das Konfigurationswerkzeug scannt zunächst den angeschlossenen Bus ab und erkennt über ein Bit im obligatorischen Diagnosetelegramm die DP-Peripheriegeräte, die eine Gerätedatei im Sinne des vorgeschlagenen Verfahrens speichern. Das Konfigurationswerkzeug geht nur mit dem bzw. den in Frage kommenden Peripheriegeräten in den Zustand "zyklischer Datenaustausch". Vorteilhaft werden bei dieser Ausführungsform des vorgeschlagenen Verfahrens Peripheriegeräte für die bereits eine GSD-Datei vorliegt, nicht angesprochen. Im Peripheriegerät wird nun die Konfigurationsmeldeeinheit 58 aktiviert. In diesem Zustand liefert das Peripheriegerät dann statt der wirklichen E/A- Daten den Inhalt der gespeicherten Gerätedatei, welche vorteilhaft in einem Gerätedateispeicher 55 abgelegt ist. Dabei ist es vorteilhaft möglich, die Gerätedatei in mehreren Teilen segmentiert zu übertragen, da beispielsweise ein Profibus-DP pro Teilnehmer und Zyklus maximal 246 Bytes Nettodaten spezifiziert. Nach der vollständigen und korrekten Übertragung wird die Konfigurationsmeldeeinheit 58 wieder deaktiviert und das Peripheriegerät 50 wechselt wieder in den Anfangszustand zurück. Hat das Konfigurationswerkzeug alle Gerätedateien aller angeschlossenen Peripheriegeräte wie beschrieben empfangen, kann die reguläre Konfiguration wie in der obigen Telegrammreihenfolge aufgeführt mit Punkt 4 fortgeführt werden. Für die hier erläuterte bevorzugte Ausführungsform des vorgeschlagenen Verfahrens ist es notwendig, daß das Konfigurationswerkzeug Zugriff auf den DP-Master, also eine Host-Einheit, hat, um die empfangenen Daten vom Master abzugreifen, als GSD-Datei zusammenzusetzen und geeignet abzuspeichern.
• 2. Für alle Peripheriegeräte im Sinne der Erfindung führt der Systemingenieur eine spezielle allgemeingültige GSD-Datei aus. Diese Datei beschreibt das DP-Peripheriegerät normgerecht als DP-Teilnehmer, jedoch speziell nur für den Zweck des Ladens der Gerätedatei. Insbesondere ist für solche Peripheriegeräte eine solche Identifikationsnummer vorgesehen. Auf Basis dieser speziellen GSD-Datei erstellt der Systemingenieur eine Konfiguration, die nur solche Teilnehmer enthält, von denen die "regulären" GSD- Dateien fehlen. Das Peripheriegerät erkennt in der Diagnoseanforderung die Identifikationsnummer. Dadurch wird im Peripheriegerät nun die Konfigurationsmeldeeinheit 58 aktiviert. In diesem Zustand liefert das Peripheriegerät dann statt der wirklichen E/A- Daten den Inhalt der gespeicherten Gerätedatei. Diese ist in dem Gerätedateispeicher 55 abgelegt und wird über den internen Bus 51 des Peripheriegerätes an eine Schnittstelle 52 und von da an den Kommunikationskanal 53 zur Host-Einheit, in diesem Fall einem Feldbus, übermittelt. Auch in diesem Fall ist es wie unter 1. bereits beschrieben möglich, die Gerätedatei in mehreren Teilen segmentiert zu übertragen. Die weiteren Konfigurationsschritte folgen wiederum wie bereits unter 1. erläutert, das heißt nach der vollständigen korrekten Übertragung wird die Konfigurationsmeldeeinheit 58 deaktiviert, das Peripheriegerät wechselt in den Anfangszustand und das Konfigurationswerkzeug kann für eine folgende reguläre Konfiguration eingesetzt werden.
• 3. Es ist auch möglich, daß das Konfigurationswerkzeug über einen Klasse-2-Master, also einem Klasse-1-Master neben oder untergeordnete Host-Einheit, direkt auf den Profibus-DP-Strang zugreift. Dabei wird die Möglichkeit der Kommunikation zwischen einem Klasse-2-Master und einem DP-Peripheriegerät genutzt. Mit den Klasse-2- Funktionen sind Schreibe- und Lesezugriffe auf DP-Peripheriegeräte auch bei gleichzeitigem Betrieb des DP-Busses mit einem Klasse-1-Master möglich. Damit kann eine Gerätedatei wie unter 1. oder 2, mittels Klasse-2-Funktionen aus einem Peripheriegerät geladen werden. Eine entsprechende Kommunikation kann entweder über die bereits erwähnte Schnittstelle 52 und einen daran angeschlossenen Kommunikationskanal zu einem Klasse-1-Master über einen Feldbus 53 erfolgen. Es könnte jedoch auch eine Kommunikation über eine Peripherie Ein/Ausgabeinheit 57 und einen daran angeschlossenen weiteren Bus 57a mit einem Klasse-2-Master erfolgen.
• 4. Weiterhin kann es notwendig sein, ein Peripheriegerät direkt mit einer Host-Einheit zu verbinden. Dies kann über eine zusätzliche Verbindung an der Schnittstelle 52, welche beispielsweise als serielle Schnittstellenverbindung ausgelegt sein kann, am Peripheriegerät erfolgen. Über eine solche serielle Schnittstellenverbindung 54 würde die Gerätedatei unmittelbar an eine Host-Einheit übertragen werden können. Ein Betrieb am eigentlichen Profibus-DP-Bus 53 ist dazu nicht notwendig. Durch Ansprache der zusätzlichen Schnittstellenverbindung 54 wird die Konfigurationsmeldeeinheit 58 aktiviert. Damit kann das Konfigurationswerkzeug die Gerätedatei auslesen und lokal zur weiteren Nutzung speichern. Nach der vollständigen und korrekten Übertragung wird die Konfigurationsmeldeeinheit 58 deaktiviert. Hat das Konfigurationswerkzeug alle Gerätedateien aller angeschlossenen Peripheriegeräte wie beschrieben empfangen, kann wiederum die reguläre Profibus-DP-Konfiguration entsprechend Punkt 4 der oben angegebenen Telegrammreihenfolge durchgeführt werden.

The four different options mentioned above for loading a device file into the configuration tool, for example a configuration tool corresponding to the configuration tool 22 of FIG. 2, are now as follows, for example applied to a system according to FIG. 1:

• 1. The configuration tool first scans the connected bus and recognizes, via a bit in the mandatory diagnostic telegram, the DP peripheral devices that save a device file in accordance with the proposed method. The configuration tool only goes into the "cyclic data exchange" state with the peripheral device or devices in question. In this embodiment of the proposed method, peripheral devices for which a GSD file already exists are advantageously not addressed. The configuration message unit 58 is now activated in the peripheral device. In this state, the peripheral device then supplies the content of the stored device file, which is advantageously stored in a device file memory 55 , instead of the actual I / O data. It is advantageously possible to transfer the device file in segments in several parts, since, for example, a Profibus-DP specifies a maximum of 246 bytes of net data per participant and cycle. After the complete and correct transmission, the configuration message unit 58 is deactivated again and the peripheral device 50 changes back to the initial state. If the configuration tool has received all device files of all connected peripheral devices as described, the regular configuration can be continued as described in the above telegram order with point 4 . For the preferred embodiment of the proposed method explained here, it is necessary for the configuration tool to have access to the DP master, that is to say a host unit, in order to tap the received data from the master, to compile it as a GSD file and to store it in a suitable manner.
• 2. For all peripheral devices in the sense of the invention, the system engineer executes a special, general GSD file. This file describes the DP peripheral device as a DP device in accordance with the standards, but specifically only for the purpose of loading the device file. In particular, such an identification number is provided for such peripheral devices. Based on this special GSD file, the system engineer creates a configuration that contains only those participants from whom the "regular" GSD files are missing. The peripheral device recognizes the identification number in the diagnostic request. As a result, the configuration message unit 58 is now activated in the peripheral device. In this state, the peripheral device then supplies the content of the stored device file instead of the actual I / O data. This is stored in the device file memory 55 and is transmitted via the internal bus 51 of the peripheral device to an interface 52 and from there to the communication channel 53 to the host unit, in this case a field bus. In this case too, it is possible, as already described under 1., to transfer the device file in segments in several parts. The further configuration steps in turn follow as already explained under 1., that is to say after the complete correct transmission, the configuration message unit 58 is deactivated, the peripheral device changes to the initial state and the configuration tool can be used for a subsequent regular configuration.
• 3. It is also possible for the configuration tool to access the Profibus-DP line directly via a class 2 master, that is to say a class 1 master next to or a subordinate host unit. The possibility of communication between a class 2 master and a DP peripheral device is used. With the class 2 functions, write and read access to DP peripheral devices is possible even if the DP bus is operated simultaneously with a class 1 master. This means that a device file as under 1. or 2 can be loaded from a peripheral device using class 2 functions. Corresponding communication can take place either via the already mentioned interface 52 and a communication channel connected to it to a class 1 master via a field bus 53 . However, communication could also take place via a peripheral input / output unit 57 and a further bus 57 a connected to it with a class 2 master.
• 4. It may also be necessary to connect a peripheral device directly to a host unit. This can be done via an additional connection on the interface 52 , which can be designed, for example, as a serial interface connection, on the peripheral device. Via such a serial interface connection 54 , the device file could be transferred directly to a host unit. Operation on the actual Profibus-DP bus 53 is not necessary for this. The configuration message unit 58 is activated by addressing the additional interface connection 54 . This enables the configuration tool to read the device file and save it locally for further use. After the complete and correct transmission, the configuration reporting unit 58 is deactivated. Once the configuration tool has received all device files of all connected peripheral devices as described, the regular Profibus-DP configuration can be carried out in accordance with point 4 of the telegram sequence specified above.

The above four examples were explained using the DP bus, but could also be transferred to other bus systems. REFERENCE SIGNS LIST 11 host unit
13 field bus
14 a, 14 b, 14 c peripheral device
22 Configuration tool
50 peripheral device
53 field bus
54 interface
55 Device file
56 processor unit
58 Configuration reporting unit
59 data memories

Claims (26)

1. Method for operating a peripheral device ( 14 a, 14 b, 14 c, 50 ) by means of a host unit ( 11 ), in which the peripheral device ( 14 a, 14 b, 14 c, 50 ) from the host unit ( 11 ) is recognized, configured and / or operated, characterized in that for the configuration of the peripheral device ( 14 a, 14 b, 14 c, 50 ) a device file ( 14 a, 14 b, 14 c, 50 ) describing the peripheral device ( 55 ) of the host unit ( 11 ) from the peripheral device ( 14 a, 14 b, 14 c, 50 ) is made available. 2. The method according to claim 1, characterized in that the device file ( 55 ) from the peripheral device ( 14 a, 14 b, 14 c, 50 ) is recorded in a configuration tool ( 22 ). 3. The method of claim 2, wherein the configuration tool ( 22 ) has a software module into which the device file ( 55 ) is loaded. 4. The method according to claim 2, characterized in that the configuration tool ( 22 ) is part of the host unit ( 11 ), in particular has a processor unit and / or a memory. 5. The method according to claim 2, characterized in that the configuration tool ( 22 ) accesses a bus ( 13 ), the peripheral device ( 14 a, 14 b, 14 c, 50 ) with stored device file ( 55 ) is recognized, the peripheral device ( 14 a, 14 b, 14 c, 50 ) from the initial state to a data exchange state, the device file ( 55 ) from the peripheral device ( 14 a, 14 b, 14 c, 50 ) to the configuration tool ( 22 ), in particular to the host unit ( 11 ), is transferred and the peripheral device ( 14 a, 14 b, 14 c, 50 ) is set to the initial state. 6. The method according to claim 5, characterized in that the configuration tool ( 22 ) for data exchange in the peripheral device ( 14 a, 14 b, 14 c, 50 ) activates and / or deactivates a configuration reporting unit ( 58 ). 7. The method according to claim 5, characterized in that after the peripheral device ( 14 a, 14 b, 14 c, 50 ) is in the initial state, a configuration of the peripheral device ( 14 a, 14 b, 14 c, 50 ) takes place. 8. The method according to claim 5, characterized in that the device file ( 55 ) is transmitted in segments. 9. The method according to claim 5, characterized in that a peripheral device ( 14 a, 14 b, 14 c, 50 ), for which no device file of the host unit ( 11 ) is available, is recognized, in particular is placed in a data exchange state , 10. The method according to any one of the preceding claims, characterized in that the peripheral device ( 14 a, 14 b, 14 c, 50 ) is pre-initialized by a general device file to the device file ( 55 ) from the peripheral device ( 14 a, 14 b , 14 c, 50 ) of the host unit ( 11 ). 11. The method according to any one of the preceding claims, characterized in that the device file ( 55 ) from the peripheral device ( 14 a, 14 b, 14 c, 50 ) is made available to a class 2 host unit. 12. The method according to any one of the preceding claims, characterized in that the device file ( 55 ) from the peripheral device ( 14 a, 14 b, 14 c, 50 ) of the host unit ( 11 ) via a field bus ( 13 , 53 ) is made available. 13. The method according to claim 1 to 11, characterized in that the device file ( 55 ) from the peripheral device ( 14 a, 14 b, 14 c, 50 ) of the host unit ( 11 ) bypassing the field bus ( 53 ) directly ( 54 ) is made available. 14. Operating unit, comprising a host unit ( 11 ) and an attached peripheral device ( 14 a, 14 b, 14 c, 50 ), in which the peripheral device ( 14 a, 14 b, 14 c, 50 ) from the host Unit ( 11 ) is recognizable, configurable and / or operable, characterized in that the peripheral device ( 14 a, 14 b, 14 c, 50 ) can be used for a configuration of the peripheral device ( 14 a, 14 b, 14 c, 50 ) and a peripheral device (14 a, 14 b, 14 c, 50) descriptive device file (55) mounted on the peripheral device (14 a, 14 b, 14, 50 c) the host unit (11) is provided , 15. Operating unit according to claim 14, characterized by a class 2 host unit, the device file ( 55 ) on the peripheral device ( 14 a, 14 b, 14 c, 50 ) is provided. 16. Operating unit according to claim 14, characterized in that the device file ( 55 ) on the peripheral device ( 14 a, 14 b, 14 c, 50 ) of the host unit ( 11 ) via a field bus ( 13 , 53 ) available is posed. 17. Operating unit according to claim 14, characterized in that the device file ( 55 ) on the peripheral device ( 14 a, 14 b, 14 c, 50 ) of the host unit ( 11 ) via an additional interface ( 54 ) bypassing a field Busses ( 13 , 53 ) is provided directly. 18. Operating unit according to one of claims 14 to 17, characterized by a configuration tool ( 22 ) for receiving the device file ( 55 ). 19. Operating unit according to one of claims 14 to 18, characterized in that the peripheral device ( 14 a, 14 b, 14 c, 50 ) has a configuration message unit ( 58 ), in particular a software module designed as a configuration message unit ( 58 ). 20. Operating unit according to one of claims 14 to 19, characterized by Design features of a programmable logic controller. 21. Operating unit according to one of claims 14 to 19, characterized by Design features of a PC system. 22. Peripheral device ( 50 ), having an interface unit ( 54 ) for providing a communication channel to a host unit ( 11 ), characterized by a device memory ( 55 ) and a configuration message unit ( 58 ), which are used for data exchange with the host unit ( 11 ) can be activated. 23. Peripheral device ( 50 ) according to claim 22, characterized in that the configuration reporting unit ( 58 ) can be deactivated after the data exchange. 24. Peripheral device ( 50 ) according to claim 22 or 23, characterized by a processor unit ( 56 ), a peripheral interface unit ( 57 ) for providing a communication channel to the periphery and a further data memory ( 59 ). 25. Peripheral device ( 50 ) according to one of claims 22 to 24, characterized in that the device memory ( 55 ) has a device file describing the peripheral device, which is made available to the host unit ( 11 ) by means of the configuration unit ( 58 ). 26. Peripheral device ( 14 a, 14 b, 14 c, 50 ), in particular a peripheral device ( 50 ) according to one of claims 22 to 25, which can be recognized, configured and / or operated by a host unit ( 11 ), characterized by one for a configuration of the peripheral device ( 14 a, 14 b, 14 c, 50 ) and a device file describing the peripheral device ( 14 a, 14 b, 14 c, 50 ), which is stored on the peripheral device ( 14 a, 14 b, 14 c, 50 ) of the host unit ( 11 ) is made available.