WO2008077358A1 - Appareillage doté d'un appareil d'automatisation et d'un appareil de commande, et procédé d'exploitation d'un tel appareillage - Google Patents

Appareillage doté d'un appareil d'automatisation et d'un appareil de commande, et procédé d'exploitation d'un tel appareillage Download PDF

Info

Publication number
WO2008077358A1
WO2008077358A1 PCT/DE2006/002302 DE2006002302W WO2008077358A1 WO 2008077358 A1 WO2008077358 A1 WO 2008077358A1 DE 2006002302 W DE2006002302 W DE 2006002302W WO 2008077358 A1 WO2008077358 A1 WO 2008077358A1
Authority
WO
WIPO (PCT)
Prior art keywords
description
operating
automation
device description
network according
Prior art date
Application number
PCT/DE2006/002302
Other languages
German (de)
English (en)
Inventor
Bruno Kiesel
Original Assignee
Siemens Aktiengesellschaft
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Siemens Aktiengesellschaft filed Critical Siemens Aktiengesellschaft
Priority to DE112006004210T priority Critical patent/DE112006004210A5/de
Priority to PCT/DE2006/002302 priority patent/WO2008077358A1/fr
Publication of WO2008077358A1 publication Critical patent/WO2008077358A1/fr

Links

Classifications

    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B19/00—Programme-control systems
    • G05B19/02—Programme-control systems electric
    • G05B19/04—Programme control other than numerical control, i.e. in sequence controllers or logic controllers
    • G05B19/042—Programme control other than numerical control, i.e. in sequence controllers or logic controllers using digital processors
    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B2219/00—Program-control systems
    • G05B2219/20—Pc systems
    • G05B2219/25—Pc structure of the system
    • G05B2219/25057—Configuration stored in distributed database for real time use
    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B2219/00—Program-control systems
    • G05B2219/20—Pc systems
    • G05B2219/25—Pc structure of the system
    • G05B2219/25061—Configuration stored in central database
    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B2219/00—Program-control systems
    • G05B2219/30—Nc systems
    • G05B2219/31—From computer integrated manufacturing till monitoring
    • G05B2219/31334—Database with devices, configuration, of plant
    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B2219/00—Program-control systems
    • G05B2219/30—Nc systems
    • G05B2219/32—Operator till task planning
    • G05B2219/32122—Documentation of programmable electronic system
    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B2219/00—Program-control systems
    • G05B2219/30—Nc systems
    • G05B2219/32—Operator till task planning
    • G05B2219/32142—Define device, module description using xml format file
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
    • Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
    • Y02P90/02—Total factory control, e.g. smart factories, flexible manufacturing systems [FMS] or integrated manufacturing systems [IMS]

Definitions

  • Device network with an automation device and a HMI device and method for operating such a device network
  • the invention relates to a device network according to the preamble of claim 1, ie a device network with at least one automation device and at least one communicatively connected or connectable HMI device.
  • automated device encompasses all devices, devices or systems, ie in addition to e.g. Controllers, such as programmable logic controllers, process computers, (industrial) computers and the like, also drive controllers, frequency converters and the like, as used for the control, regulation and / or monitoring of technological processes, e.g. be used or be used for forming or transporting material, energy or information, etc., in particular by means of suitable technical devices, such. Sensors or actuators, energy is spent or converted.
  • Controllers such as programmable logic controllers, process computers, (industrial) computers and the like, also drive controllers, frequency converters and the like, as used for the control, regulation and / or monitoring of technological processes, e.g. be used or be used for forming or transporting material, energy or information, etc., in particular by means of suitable technical devices, such.
  • Sensors or actuators energy is spent or converted.
  • control device is in particular a mobile control device, such. a laptop computer, a so-called handheld, a PDA, a mobile phone and the like into consideration.
  • a mobile control device such. a laptop computer, a so-called handheld, a PDA, a mobile phone and the like into consideration.
  • any previously known in automation technology as an operating device device can be used as an operating device.
  • automation devices forming an automation system result in a wide range of different features, configurations, makes and the like.
  • access to individual automation devices is possible with
  • such programs generally allow only access to the devices of the respective manufacturer and are also often limited to certain types of automation devices.
  • the functionality of the respective automation device must be known to the operating device.
  • a device device description languages including an internationally standardized (IEC61804-3) device description language with the short name DDL (Device Description Language) or EDDL (Electronic Device Description Language) are known for device description.
  • IEC61804-3 device description language with the short name DDL (Device Description Language) or EDDL (Electronic Device Description Language) are known for device description.
  • DDL Device Description Language
  • EDDL Electronic Device Description Language
  • An object of the present invention is correspondingly to provide a device network of the aforementioned type or a method for operating such a device network, with which the above-mentioned disadvantages are avoided or at least reduced in terms of their effects.
  • this is achieved with a device network as defined in the independent device claim or a method for operating such a device network, as defined in the corresponding independent method claim.
  • a device network with at least one automation device and a communicatively connected or connectable control device, both the automation device and the operating device access to a respective memory with a stored there or leglegba- ren device description, provided that at a
  • the device description is available in parts, if it is not available on the HMI device.
  • the device description is loaded into the HMI device only, or at least at the latest at the time of operation by the automation device.
  • the retrieval of the device description in the automation device is also limited to each of the control unit specifically retrieved parts thereof.
  • EDDL is a text-based language that describes the digital communication characteristics of automation devices as well as parameters such as device status, diagnostic data, and Describe configuration information in a manner independent of the respective operating system and a respective man-machine interface.
  • Electronic device descriptions are often provided in the form of several description files on central systems and not locally, eg on an operator panel. Furthermore, due to the power of the electronic device description, a high complexity and thus a high expenditure for the interpretation with the result that only a few special applications exist that can interpret and process an electronic device description in its entirety. Apart from PC-based systems, there are only special products that prevent widespread use, especially because of their cost.
  • the communication between the automation device and the HMI device is limited to a wired communication, in particular according to the HART standard.
  • the invention addresses the problems associated with this by providing that in the case of an access by means of the operating device to the automation device, the complete device description is not always called up, but at least part of the device description can be called up and this only then, if these Device description or the respective part is not available on the HMI device.
  • the retrieval of the device description By limiting the retrieval of the device description to a respective part of interest, operating devices with limited storage resources can also be used. The fact that the retrieval from the automation device only takes place if the device description or the respective part on the
  • the HMI device is not already available, a check is necessary to determine whether the device description is already available on the HMI device. If no device description is stored on the HMI device, the condition for each automation device is always met and the relevant part of the device description is currently retrieved at the respective automation device. If there are device descriptions on the HMI device that do not suit the respective automation device, the condition is fulfilled and an inherently current part of a device description is called up for the respective automation device. If a device description that is basically suitable for the automation device is already available on the HMI device, the condition is nevertheless not fulfilled if the device description available on the HMI device does not correspond to the device description available on the HMI device, for example because the automation device has provided a device description with a current device description. includes more information. Also in this case, the respective relevant part of the device description is retrieved from the automation device and is thus available on the operating device.
  • the approach according to the invention therefore not only ensures that the device description is always up-to-date on the side of the operating device, but basically also makes any operating devices with limited resources, in particular with regard to the memory to which the operating device has access, in a device network of the above-mentioned. Type of operation, maintenance, troubleshooting, etc. usable.
  • an evaluation of the version identifier is advantageously provided in order to decide whether an apparatus description otherwise to be retrieved from the automation apparatus is available on the operator unit.
  • an evaluation comprises a comparison of the version identification of the device description available on the operating device with the version identification of the device description that can be called up on the automation device.
  • the device description is in the form of the Electronic Device Description (EDD)
  • EDD Electronic Device Description
  • the device description comprises a collection of block-like structures, addressable elements being usable in each block structure.
  • the retrieval of a part of the device description from the automation device can take place on the one hand according to the block structure and on the other hand according to actually addressed elements.
  • the device description so only individual blocks of the device description are retrieved and only those blocks in which actually addressed elements are used or occur in any other way.
  • identifiers such as "main menu”, “entry menu”, “maintenance menu” etc., of at least one selection menu by the operating device prior to retrieval of part of the device description as addressable elements
  • the respective part of the device description can be called up by the operating device on the basis of an operator-side analysis of the or each designator
  • a device description that exists in the form of the electronic device description proves to be of particular advantage because of these are already defined according to the underlying standard individual identifiers, which are specifically searched for in the user-side analysis can, for example, at the beginning of the interaction between the HMI device and the automation device to be presented as an entry-level menu, so for example a main menu or the like.
  • role information is available for the respective operating device or for a combination of the operating device and an identification of the user respectively using the operating device, which is also used in the analysis of the or each identifier. If the role information indicates that the HMI device is intended for maintenance purposes or if the user using the HMI device identifies itself as a member of the maintenance personnel, it may be provided that instead of an otherwise possibly preferred for presentation on the HMI selected main menus in the device description on the Automation device vortenes entry menu for maintenance tasks is displayed. Such an entry-level menu for maintenance tasks can be identified by means of a designated identifier as well as a main menu.
  • such a menu is more or less the "root" of the tree, and terms that are based on it are quite common in specialist terminology, so the menu-based analysis will find such a menu and can then be used as an introduction to the operation of the automation device.
  • the device description on the part of the automation device until the date of retrieval of the respective device description or part thereof does not even exist, but the generation is done only at the time of operation by the automation device.
  • the device description at no time is present in its entirety on the automation device, but the automation device accesses a device description stored in a remote memory and transfers these or parts of the same only to the operating device, without a local storage on the part of the automation device takes place.
  • the communication between the HMI device and the automation device ie the retrieval of each part of the device description of the automation device by the HMI device, so acts on the part of the automation device as
  • Trigger for providing the device description includes just not only the copying of the device description from an accessible to the programmable controller memory to the HMI device, but possibly also only in this context occurring generating the respective device description or the respective part of the device description. This is particularly advantageous in the case of configuration changes or when replacing devices or components of such devices.
  • Neutral loading formats can reduce any complexity of the actual device description by starting from an original
  • the neutral load format at least depicts the relationships that are actually required on the HMI device side. This can be connected in a particular case, a reduced load of the communication channel used in each case. In any case, the load on the communication channel can be reduced if a compression of the or each retrieved part of the device description is provided.
  • this loading formats such as XML or the like, are available, which can be easily interpreted by the respective operating device.
  • a device considered as an operating device can process the device description directly in the respective charging format, eg represent it, while such direct representability of a device description provided in a proprietary format can also be achieved a device description available in EDD, with standard applications is usually not guaranteed.
  • the application for receiving the device description to be provided on the side of the operating device can then be reduced to basic functionalities, while for operating device-specific functions, eg representations via an output device assigned to the operating device, such as a display device, on already brought by the respective operating device or for this already available functionality, eg in the manner of a so-called browser, can be used.
  • FIG. 1 shows an automation system with a number of automation devices and therein a device network with an automation device and an operating device
  • FIG. 2 shows a device network with an automation device and an operating device
  • FIG 3 shows a schematically simplified illustration of a device description comprising block-type structures, as described in the access to the automation device by means of the operating device, e.g. for operating procedures, may be used.
  • FIG. 1 shows, in a schematically simplified illustration, an automation system, denoted as a whole by 10, which is formed by a number of automation devices 14, 16, 18, 20 communicatively connected via a bus 12 or the like, and in total for the control and / or monitoring of a not shown technical process
  • an operating device 24 is provided which is communicatively connected or connectable to an automation device 14, 16, 18, 20 to which access is intended.
  • a connection of the operating device 24 to the bus 12 may be provided.
  • a wireless communication between the respective Weil automatic controller 14, 16, 18, 20 and the control unit 24 is carried out.
  • FIG. 2 the interaction of the operating device 24 with one of the automation devices 14, 16, 18, 20 is shown again using the example of the automation device 20, wherein the respective communicative connection, that is to say e.g. the communication between the operating device 24 and the automation device 20 via the bus 12 or such a communication on line-less ways, as a functional element in the form of a communication channel 26 is shown.
  • Both the respective automation device 20 and the operating device 24 have access to a respective memory 28, 30 with a device description 32, 34 stored or can be stored there.
  • the memory 28, 30 it does not have to be on the side of the automation device 20 or on pages of the operating device 24 to a local memory 28, 30 act in the sense that it is housed with the respective device 20, 24 in a common housing or the like, but the access to the respective memory 28, 30 can also be accessed as a remote Memory be formed.
  • the access to the respective memory 28, 30 can also be accessed as a remote Memory be formed.
  • the automation device-side device description 32 may in principle be a comprehensive device description, which takes into account the entire functionality of the respective automation device 20, it is provided that accesses by means of the operating device 24 to the automation device 20 can be limited to parts of the device description 32 stored there, so that only a respective interesting part of this device description 32 is retrievable or retrieved if this is not available on the operating device 24.
  • the retrieval of the respective part of the automation device-side device description 32 is performed corresponding transfer into the memory 30, to which the operating unit 24 has access, so that the user-device-side device description 34 normally represents only a section of the automation device-side device description 32 represents.
  • Each device description 32, 34 that is to say both the automation device-side device description 32 and the device-side device description 34, is assigned a version identification drawing 36, 38.
  • an evaluation of the version marking 36, 38 is provided. This is done in such a way that whenever there is a difference between the automation device-side version marking 36 and the operating-device-side version marking 38, it is assumed that the automation device-side device description 32 is not available on the side of the operating device 24.
  • the version identifier 36 is modified at each change of the device description 32 and thus defines the version of the respective programmable controller 20 and / or the respective device description 32 clearly.
  • the version designation 36 is used by the operating device 24 to determine whether the device description 32 has to be loaded by the respective automation device 20 or a part thereof. If the operating unit 24 is able to locally store a certain number of different device descriptions 34, a situation may arise in which a device description 34, which is fundamentally suitable for the respective automation device 20, already exists locally, but which does not reflect the actual version of the device respective automation device 20 is reflected, so that by comparison of the respective version markings 36, 38 always the consistency of the device description 34 used for the operation between the respective automation device 20 and the control unit 24 is ensured.
  • the automation device-side device description 32 is illustrated in FIG. 3 in a schematically simplified form, the aim of the representation being to clarify that the device description 32 comprises a collection of block-like structures 40, wherein selection menus are defined by the block structure 40 in the addressable elements 42 are usable.
  • the retrieval of part of the automation device-side device description 32 by the operating device 24 can then take place in accordance with the block structure 40 and based on actually addressed elements. If e.g. for displaying an entry menu for the operation of the automation device 20, for which e.g.
  • the term "MenüO" is agreed is provided, the retrieval of a part of the device description can be based on that at least that block structure 40 is called at the programmable controller, which includes an addressable element 42 in which the designation "MenüO" deposited is.
  • structures 40 in particular block structures of a certain category, eg block structures that define selection menus, are retrievable and on the side of the operating device 24 an analysis of the or each identifier, ie "MenuO", “Menu ll", ... “Menü2-3” , etc., and results from such an analysis, which of the selection menus is to be regarded as an entry-level menu.
  • the entry menu is usually characterized in that it has only successor but no predecessor, so that usually from the entry menu more menus are called, while none of the selection menus invoke the entry menu itself.
  • INS In particular, it is achieved by means of a skilful construction of the device description 32 that it is possible to determine automatically on the side of the operating device 24 which parts of the device description 32 are required for certain application scenarios (above exemplified only by way of example of the identification of an input menu). , After only relevant parts of the device description 32 are loaded, this not only shortens the charging process, but also enables the use of "scenario-oriented" operator devices 24 which do not have to master the complete functionality of a device description 32. For example, a mobile phone could be used as the operator device 24 be to read identification data or statistical information of an automation device 20 and display.
  • ' well-known 'menu IDs or the class affiliation of variables eg' DIAGNOSTIC '
  • the automation device 20 offers information functions with which the operating device 24 can determine the version of the respective device description 32, in particular its version identifier 36, as well as elements, structures 40 and the like included in the device description 32 of the automation device.
  • information functions e.g. the identifiers for a group of elements (e.g.
  • the transmitted information may also include information on the sizes of the individual elements that may be used on the operator panel 24 side to provide a skilful loading strategy, e.g. parallel loading of several elements.
  • the automation device 20 offers charging functions with which elements of the Description 32 can be transferred from the automation device 20 to the operating device 24. Such functions allow the loading of single elements as well as of several elements simultaneously. The requested elements are specified using identifiers.
  • the automation device 20 offers transfer functions with which variable contents can be exchanged between the automation device 20 and the operating device 24. However, such transfer functions are not required for the operation of the automation device 20 for loading the device description 32.
  • a toothing of the device description 32 with the respective automation device 20 is possible in different ways, with four essential variants in the foreground.
  • the device description 32 is generated completely externally, while in two other variants, the respective automation device 20 in different lines actively involved in the generation of the respective device description 32, as will be explained below.
  • Variant 1 In the process of creating the firmware for the respective automation device 20, a comparison of the data for the respective device description 32 with firmware data takes place. At runtime, the provision of the respective device description 32 takes place without interaction with the remaining firmware of the device. The adjustment of the data takes place outside of the device. The consistency of the firmware data with the device description 32 is ensured by the firmware creation process. The respective automation device 20 thus only has to be able to transfer the desired elements on request from an operator device 24. Individual elements of the device description can also be stored in a neutral charging format or compressed in the device or in a memory accessible to the device.
  • Variant 2 The data of the device description 32 are also used by the firmware during runtime. The device description 32 is thus used both by the device 20 itself and by the respective operating device 24. The firmware uses the data of the device description 32 and thus ensures the consistency. The respective automation device 20 can either work directly in the loading format in which the device description 32 is present, use an internal format or generate the loading format of the device description 32 if required.
  • Variant 3 Parts of the device description 32 are generated by the device 20 itself. This means that the complete device description 32 is present only in the device 20 itself and thus is always consistent with the respective firmware of the device 20. Use cases are e.g. Modular devices that present themselves to a user as a unit and in which the individual modules are described by associated device descriptions. A link of such modules and thus a link of the associated device descriptions can be done in the device 20 - without explicit engineering.
  • Variant 4 The device description 32 is generated completely by the respective automation device 20 itself. Consistency problems can not occur then. However, this also means that the device description 32 physically does not exist outside the respective automation device 20. Within the automation device 20, the device description 32 is either generated once or on request and provided in particular in the loading format available. Applications could be e.g. simple devices that can be described with few parameters and barely contain operating logic. An explicit engineering of the respective device description 32 can then be omitted.
  • the operating device 24 contains algorithms which make it possible, based on the dependencies between elements of the device description 32, to load a meaningful part (subset) of the device description 32 and thus to operate the respective device.
  • gen automation device 20 to enable.
  • a possible algorithm would then be able to determine all identifiers, starting directly from an initial menu identifiable as such, either directly (in the form of "MENU”, “VARIABLE”, ...) or indirectly (in the form of hidden dependencies) for the current role of the user (“ROLE”) are required and then selectively retrieve only the corresponding parts of the device description 32 from the respective automation device 20.
  • the operating device 24 is able to generate generic operating structures solely on the basis of identifiers, in particular variable descriptions (for example the class membership).
  • variable descriptions for example the class membership
  • an application on the operating device 24 is conceivable that can only display diagnostic information of the respective automation device 20.
  • variable descriptions of the "DIAGNOSTIC" class must be loaded as necessary structure information Menus for displaying such diagnostic information could be generated automatically in the application
  • Another simple application is simple automation devices that can be described with a few parameters respective device description 32 generated by a corresponding automation device 20 and the necessary menu structures for accessing the variables from the operating device 24 are generated automatically.
  • the approach according to the invention or outgoing embodiments is therefore characterized in that the device description 32 is generally retrieved by the operating device 24 only at an operating time and loaded onto the operating device 24.
  • the access to the device description 32 can be fine granular and also allows the loading of device description subsets.
  • the device description does not have to exist outside the respective automation device 20 and is only needed at the time of operation. Thus, the generation of the device description 32 at the time of operation is possible.
  • the operating device 24 is automatically the same Version level of the device description 32 on the automation device 20 with the present on the operating device 24 device descriptions 34 and retrieves the device description or a part thereof in the respective automation device 20 only if it is not available on the control unit 24.
  • a device network with at least one automation device 20 and a communicatively connected or connectable control device 24 and a method for operating such a device network is specified, wherein both the automation device 20 and the control device 24 Access to a respective memory 28, 30 with a stored there or can be stored device description 32, 34, in which at least one part of the automation device device description 32 is accessed when accessing the control unit 24 to the automation device 20, if this on the HMI device 24 is not available.

Landscapes

  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Engineering & Computer Science (AREA)
  • Automation & Control Theory (AREA)
  • Programmable Controllers (AREA)

Abstract

La présente invention concerne un appareillage mixte doté d'au moins un appareil d'automatisation (20) et d'un appareil de commande (24) relié ou pouvant être relié de manière à communiquer avec celui-ci, ainsi qu'un procédé pour faire fonctionner un tel appareillage mixte. L'appareil d'automatisation (20) ainsi que l'appareil de commande (24) ont respectivement accès à une mémoire (28, 30) où est enregistrée ou peut être enregistrée une description d'appareillage (28, 30). Lors d'un accès à l'appareil d'automatisation (20), au moyen de l'appareil de commande (24), au moins une partie de la description d'appareillage peut être extraite côté appareil d'automatisation (32), lorsque ladite description n'est pas disponible côté appareil de commande (24).
PCT/DE2006/002302 2006-12-22 2006-12-22 Appareillage doté d'un appareil d'automatisation et d'un appareil de commande, et procédé d'exploitation d'un tel appareillage WO2008077358A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
DE112006004210T DE112006004210A5 (de) 2006-12-22 2006-12-22 Geräteverbund mit einem Automatisierungsgerät und einem Bediengerät sowie Verfahren zum Betrieb eines solchen Geräteverbunds
PCT/DE2006/002302 WO2008077358A1 (fr) 2006-12-22 2006-12-22 Appareillage doté d'un appareil d'automatisation et d'un appareil de commande, et procédé d'exploitation d'un tel appareillage

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/DE2006/002302 WO2008077358A1 (fr) 2006-12-22 2006-12-22 Appareillage doté d'un appareil d'automatisation et d'un appareil de commande, et procédé d'exploitation d'un tel appareillage

Publications (1)

Publication Number Publication Date
WO2008077358A1 true WO2008077358A1 (fr) 2008-07-03

Family

ID=37915453

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/DE2006/002302 WO2008077358A1 (fr) 2006-12-22 2006-12-22 Appareillage doté d'un appareil d'automatisation et d'un appareil de commande, et procédé d'exploitation d'un tel appareillage

Country Status (2)

Country Link
DE (1) DE112006004210A5 (fr)
WO (1) WO2008077358A1 (fr)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2012016003A3 (fr) * 2010-07-28 2012-12-27 Fisher-Rosemount Systems, Inc. Dispositif d'entretien sur place portatif à interface utilisateur améliorée
EP2725437A1 (fr) * 2012-09-20 2014-04-30 Ferag AG Unité de commande dotée d'applications pour la commande d'installations de production
US9210581B2 (en) 2009-05-15 2015-12-08 Fisher-Rosemount Systems, Inc. Maintenance of wireless field devices
US9684296B2 (en) 2009-05-15 2017-06-20 Fisher-Rosemount Systems, Inc. Handheld field maintenance tool with improved functionality

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2001090829A2 (fr) * 2000-05-24 2001-11-29 Schneider Automation Inc. Procede de surveillance a distance de la configuration d'un systeme de commande industriel
WO2002077732A1 (fr) * 2001-03-22 2002-10-03 Metso Field Systems Oy Gestion de documents relatifs a des appareils de terrain dans un systeme d'automatisation
EP1401171A2 (fr) * 2002-09-20 2004-03-24 Sick AG Dispositif électronique pour un système bus
EP1515207A1 (fr) * 2003-09-15 2005-03-16 Siemens Aktiengesellschaft Objet d'automatisation et méthode pour la description d'un objet d'automatisation en utilisant une métalangage

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2001090829A2 (fr) * 2000-05-24 2001-11-29 Schneider Automation Inc. Procede de surveillance a distance de la configuration d'un systeme de commande industriel
WO2002077732A1 (fr) * 2001-03-22 2002-10-03 Metso Field Systems Oy Gestion de documents relatifs a des appareils de terrain dans un systeme d'automatisation
EP1401171A2 (fr) * 2002-09-20 2004-03-24 Sick AG Dispositif électronique pour un système bus
EP1515207A1 (fr) * 2003-09-15 2005-03-16 Siemens Aktiengesellschaft Objet d'automatisation et méthode pour la description d'un objet d'automatisation en utilisant une métalangage

Cited By (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9210581B2 (en) 2009-05-15 2015-12-08 Fisher-Rosemount Systems, Inc. Maintenance of wireless field devices
US9503906B2 (en) 2009-05-15 2016-11-22 Fisher-Rosemount System, Inc. Detection and location of wireless field devices
US9532232B2 (en) 2009-05-15 2016-12-27 Fisher-Rosemount Systems, Inc. Detection and location of wireless field devices
US9684296B2 (en) 2009-05-15 2017-06-20 Fisher-Rosemount Systems, Inc. Handheld field maintenance tool with improved functionality
WO2012016003A3 (fr) * 2010-07-28 2012-12-27 Fisher-Rosemount Systems, Inc. Dispositif d'entretien sur place portatif à interface utilisateur améliorée
US9201414B2 (en) 2010-07-28 2015-12-01 Fisher-Rosemount Systems, Inc. Intrinsically-safe handheld field maintenance tool with image and/or sound capture
US9703279B2 (en) 2010-07-28 2017-07-11 Fisher-Rosemount Systems, Inc. Handheld field maintenance device with improved user interface
US9709973B2 (en) 2010-07-28 2017-07-18 Fisher-Rosemount Systems, Inc. Handheld field maintenance tool with improved diagnostics
US9864357B2 (en) 2010-07-28 2018-01-09 Fisher-Rosemount Systems, Inc. Handheld field maintenance tool with integration to external software application
US10268180B2 (en) 2010-07-28 2019-04-23 Fisher-Rosemount Systems, Inc. Handheld field maintenance tool with simulation of field device for instruction or qualification
EP2725437A1 (fr) * 2012-09-20 2014-04-30 Ferag AG Unité de commande dotée d'applications pour la commande d'installations de production

Also Published As

Publication number Publication date
DE112006004210A5 (de) 2009-12-03

Similar Documents

Publication Publication Date Title
EP2051150B1 (fr) Procédé de modification automatique d'un programme
DE10152765B4 (de) Verfahren zur elektronischen Bereitstellung von Diensten für Maschinen über eine Datenkommunikationsverbindung
DE102007026678A1 (de) Verfahren zum Austausch eines defekten Feldgerätes gegen ein neues Feldgerät in einem über digitalen Feldbus kommunizierenden System, insbesondere Automatisierungssystem
EP2098925A1 (fr) Procédé et dispositif adaptés à la programmation et/ou la configuration d'un contrôleur de sécurité
EP2098926A1 (fr) Procédé et dispositif adaptés à la programmation et/ou la configuration d'un contrôleur de sécurité
EP2042956A2 (fr) Interface entre un système de gestion de la fabrication et un système d'automatisation
EP2407842B1 (fr) Procédé de mise en service de machines ou machines d'une série de machines et système de planification
EP1714197B1 (fr) Pilote pour appareils de champ de la technologie d'automatisation des processus
EP3637205A1 (fr) Déclenchement de l'image sur une station client de l'opérateur
EP2157536A2 (fr) Système de surveillance, commande et saisie de données de processus techniques
EP2422248B1 (fr) Système et procédé de répartition de données de projets d'un controlleur de sécurité d'une installation automatisée aux composants de commande
DE102008061721A1 (de) Administrationssystem
WO2008077358A1 (fr) Appareillage doté d'un appareil d'automatisation et d'un appareil de commande, et procédé d'exploitation d'un tel appareillage
EP2098928A1 (fr) Procédé et dispositif adaptés à la programmation et/ou la configuration d'un contrôleur de sécurité
EP3420426B1 (fr) Dispositif et procede d'adaptation d'une commande numerique sur une machine a commander
EP1653308B1 (fr) Procédé et dispositif pour enregistrer et mettre à disposition des informations
EP1643679A1 (fr) Configuration de modules dans des systèmes d'automatisation
EP1436697A2 (fr) Procede de traitement de donnees
EP1449040B1 (fr) Procede permettant d'acceder aux donnees d'un appareil d'automatisation, et appareil d'automatisation
DE102008023873A1 (de) Verfahren zum Betrieb eines Antriebssystems
DE10049021A1 (de) Verfahren und Vorrichtung zum Erfassen von Betriebsdaten einer Produktionsanlage
EP2085840B1 (fr) Procédé destiné à la programmation d'un dispositif de commande
EP2511777A1 (fr) Procédé de fonctionnement d'un dispositif de commande d'entraînement et dispositif de commande d'entraînement doté de moyens pour l'utilisation dans un tel procédé
DE69918829T2 (de) Steuerungssystem zur steuerung von prozessgeräten
EP1227379B1 (fr) Procédé et dispositif pour la commande d'une machine dans un système de fabrication

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 06840882

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 1120060042106

Country of ref document: DE

REF Corresponds to

Ref document number: 112006004210

Country of ref document: DE

Date of ref document: 20091203

Kind code of ref document: P

122 Ep: pct application non-entry in european phase

Ref document number: 06840882

Country of ref document: EP

Kind code of ref document: A1