EP1682954A2 - Systeme d'automatisation comprenant des composants communiquant entre eux - Google Patents

Systeme d'automatisation comprenant des composants communiquant entre eux

Info

Publication number
EP1682954A2
EP1682954A2 EP04803111A EP04803111A EP1682954A2 EP 1682954 A2 EP1682954 A2 EP 1682954A2 EP 04803111 A EP04803111 A EP 04803111A EP 04803111 A EP04803111 A EP 04803111A EP 1682954 A2 EP1682954 A2 EP 1682954A2
Authority
EP
European Patent Office
Prior art keywords
program
components
management system
version
automation system
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
EP04803111A
Other languages
German (de)
English (en)
Inventor
Peter Wiedenberg
Rene Wolf
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Siemens AG
Original Assignee
Siemens AG
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 AG filed Critical Siemens AG
Publication of EP1682954A2 publication Critical patent/EP1682954A2/fr
Ceased legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/70—Software maintenance or management
    • G06F8/71—Version control; Configuration management
    • 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
    • G05B19/0423—Input/output
    • G05B19/0425—Safety, monitoring
    • 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/418—Total factory control, i.e. centrally controlling a plurality of machines, e.g. direct or distributed numerical control [DNC], flexible manufacturing systems [FMS], integrated manufacturing systems [IMS] or computer integrated manufacturing [CIM]
    • G05B19/41845—Total factory control, i.e. centrally controlling a plurality of machines, e.g. direct or distributed numerical control [DNC], flexible manufacturing systems [FMS], integrated manufacturing systems [IMS] or computer integrated manufacturing [CIM] characterised by system universality, reconfigurability, modularity
    • 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/31405—EDM electronic data management
    • 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/31418—NC program management, support, storage, distribution, version, update
    • 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

  • the invention relates to an automation system with mutually communicating components and a central administration system.
  • Automation systems generally have many different individual components, such as Drives, programmable logic controllers (PLC) and communication devices (HMI, operator control and monitoring device) that serve the system operator to exchange information with the automation system.
  • PLC programmable logic controllers
  • HMI operator control and monitoring device
  • Many of these automation components have a software or firmware component, that is to say they are program-controlled, the program being loadable into these components, that is to say interchangeable.
  • the components of the automation system are connected via a network, e.g. connected to each other via a fieldbus or a LAN (Ethernet, Token-Ring, etc.) in order to exchange data with each other, i.e. to be able to communicate.
  • a network e.g. connected to each other via a fieldbus or a LAN (Ethernet, Token-Ring, etc.) in order to exchange data with each other, i.e. to be able to communicate.
  • program versions for program-controlled components, e.g. distinguish between program errors that have become known through their range of functions or through corrections.
  • the programs have version numbers that reflect the versions.
  • Automation systems often already contain a central system that is also connected to the network as a management system.
  • central configuration station i.e. a so-called engineering PC, which is used for the central management of the automation system. From this, programs can possibly also be transferred to a specific system component and loaded into it.
  • An update to a component is usually initiated, activated and then activated. This is done e.g. at the weekend or when the system is down. It is essential that the update knowingly, e.g. does not occur while the process is running, which could lead to malfunctions in the entire automation system.
  • the implementation and responsibility of the program management on all system components lies with the project engineer or maintenance engineer of the system. This decides whether and which versions of the programs are installed on the components, i.e. on the assignment of programs and components. He is also responsible for the compatibility of the programs of the various components in the system, i.e. for the smooth interaction of the individual program versions.
  • a compatibility matrix is often used for this purpose, which is recorded, for example, in writing on paper. It contains an overview of the compatibility of the various software versions of the individual component programs. So for an automation system Often company standards are laid down, which determine which assignments between programs and automation components are permitted for the system. The project engineer or maintenance engineer must also always observe this information.
  • the aim of the present invention is therefore to reduce the susceptibility to errors when assigning components and programs.
  • the task is solved by an automation system with components communicating with each other, each of which is controlled by a program assigned to them.
  • a central management system communicating with the components is also provided in the automation system.
  • the assignments of components and programs are stored in the management system.
  • the assignment of component and program can be determined by the management system. This is done e.g. in that the management system sends a request to a specific component via the system bus, which reports back to the management system the name, version, version number, etc. of the program on it.
  • the assignment saved in the management system can thus always be kept up-to-date, i.e. consistent. An entry of a change after a program update on a component cannot be forgotten, which eliminates another source of errors.
  • the program can be transferred from the administration system to the component. There it can be activated and thus activated at a suitable time.
  • the project engineer or maintenance engineer of the automation system therefore no longer has to leave his or her workplace in the administration system to carry out a program change on a component, which results in a considerable reduction in time and effort.
  • a necessary program update can be carried out automatically on a component, for example, even in the absence of an operator, for example on weekends. This saves labor and time. The next day of operation of the system, for example, only needs to be checked whether the program update has been completed correctly.
  • permissible assignments are stored in the management system for a component and a program.
  • the program is only transferred to the component if its assignment to the component is permitted.
  • a manual check of a compatibility matrix in written form by the maintenance engineer or project engineer is therefore no longer necessary and a further source of error due to an inadvertent incorrect installation of a program that is not compatible with the system or the component is avoided.
  • the compatibility matrix or corresponding company standards can be integrated in the form of the permissible assignments as a logic function in the management system. Changes e.g. In the company standard of permissible program assignments, they are stored in a single central location in the management system and cannot be overlooked in future software updates.
  • the management system is connected to the Internet.
  • the management system is e.g. at any time the possibility to obtain the latest version of a program or information about it from the program or component manufacturer.
  • the manufacturer has the option of immediately informing the operator of an automation system about detected errors or security gaps in one of his programs and notifying them of necessary program updates.
  • the necessary updates e.g. to eliminate security-related errors in a program can be automatically determined and announced.
  • a further degree of automation can be achieved if a new program version is automatically available from the management system when a new program version is available from the manufacturer the Internet is obtained and installed in the automation system at the earliest possible time.
  • Knowingly activation i.e. the final approval for implementation, i.e. triggering a program update, can in principle be reserved for the project engineer or maintenance engineer of the system in all embodiments.
  • FIG. 1 shows an automation system with an administration system with an Internet connection in a schematic diagram
  • FIG. 2 shows an exemplary configuration dialog on the screen of the management system.
  • FIG. 1 shows an automation system 2.
  • This contains several PLCs 4 (programmable logic controller), several HMI 6 (human machine interface, communication device) and drives 8 as components.
  • a central management system 10 is included, which itself counts as a component of the automation system.
  • the management system 10 is connected to the PLC 4, the HMI 6 via a network 12, the drives 8 are also networked via a fieldbus 48.
  • a mass storage device 14 is also connected to the management system 10.
  • the management system 10 is connected to manufacturers 18 via the Internet 16.
  • All components of the automation system 2 that is to say PLC 4, HMI 6, drive 8, management system 10 and network 12, operate under program control, ie a computer program 20, 22, 24, 26, 28 is assigned to each of them.
  • Each of these computer programs 20 to 28 has a version number which characterizes the version.
  • a further developed program, which was later offered by the manufacturer 18 and in which, for example, errors were corrected, has a higher version number.
  • the management system 10 can send a request via the network 12 to all components of the system 2 and to itself in order to query the current version of the programs 20 to 28. All versions of all programs 20 to 28 are stored in the management system 10 in the form of an electronic list (not shown).
  • a manufacturer 18 of the PLC 4 sends a data carrier 32, e.g. a CD-Rom with a program 20 to the operator of the automation system 2.
  • the version of the program 20 on the data carrier 32 is 4.0 higher than the version 3.2 of the programs 20 currently present in the PLC 4.
  • the maintenance worker (not shown) working on the management system 10 The automation system 2 places the data carrier 32 in the mass storage 14 of the management system 10, for example whose CD-Rom drive, a. On the basis of the information in the management system 10, it is known that the version of the program 20 currently used in the automation system 2 is lower than that on the data carrier 32.
  • the maintenance engineer therefore transmits the new version 4.0 of the program 20 to all the PLCs 4 via the administration system 20 and the network 12 and thus initiates the update.
  • all PLC 4 Upon acceptance, i.e. activation and activation of the update in the PLC 4, all PLC 4 are equipped with programs of the latest version 4.0.
  • the version number of the program 28 of the network 12 currently present in the automation system 2 is 2.1.
  • a manufacturer 18 of the network 12 has new versions 2.2 to 2.4 of the program 28 on its website. Since the manufacturer 18 informed the maintenance engineer of the automation system 2 in writing, for example via the Internet 16 by email, about the new available versions of the program 28, the latter checks the admissibility with the help of the company standard list shown in FIG. 2 in the management system this update.
  • the management system 10 has the highest permissible version for the program 28, the sion 2.2 saved. The maintenance engineer therefore loads the new program 22 with version 2.2 from the manufacturer 18 via the internet 16 into the HMI 6 via the administration system 10 and the network 12 and activates this version there.
  • FIG. 2 shows the screen 40 of the management system 10, which is not shown in FIG. 1.
  • An assignment list 42 is shown in tabular form on the screen 40, which provides information about the relevant data for the software versions of the programs of the components used in the automation system 2.
  • the top row of the table shows the respective column heading, the following five rows each represent a component 4 to 12 of the automation system 2.
  • the system components are named.
  • the second table column indicates for each component the current version number of the programs stored in the automation system 2, which are the same throughout the system for each component, that is, the version status of the program of the component.
  • the third column shows for each component the mass storage device 14 or the Internet 16 or a LAN (local area network) or intranet or the like. available highest possible, i.e. most recent version of the programs assigned to the components.
  • Column four shows the permitted revision level for each component according to the company standard. In automation length 2, the number recorded there in each line is the highest permitted version for programs of the respective components. For the management system 10, it can be seen in the second line that there is no maximum restriction for the program 26 of the management system 10, that is, the most current version may always be installed.
  • the fifth and last one within the management system 10 Column in table 42 is automatically determined and displayed, namely whether or not it is necessary to update its programs plant-wide for the components corresponding to the row.
  • This line hides a logic function in the management system 10 for determining the fifth column on the basis of the information from columns two to four.
  • the installation is e.g. to be answered in the negative since the installed, i.e. current, version 4.0 in the automation system 2 is already the maximum permissible version, namely 4.0.
  • the currently available version 4.2 is therefore not installed.
  • the maintenance engineer of the automation system 2 checks the table 42 and, by pressing or clicking the button 44, grants the administration system 10 permission to transmit the corresponding programs to the administration system 10, the network 12 and, via the network 12, to the drives 8. If the maintenance engineer does not agree with the automatically generated assignment list, or if he only wants to start the installation at a later time, he can cancel the installation by pressing the button 46.

Landscapes

  • Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Automation & Control Theory (AREA)
  • Software Systems (AREA)
  • Quality & Reliability (AREA)
  • Computer Security & Cryptography (AREA)
  • Manufacturing & Machinery (AREA)
  • Stored Programmes (AREA)
  • Interconnected Communication Systems, Intercoms, And Interphones (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

L'invention concerne un système d'automatisation (2) comprenant des composants qui communiquent entre eux (4, 6, 8, 10, 12) et qui sont respectivement commandés par un programme (20, 22, 24, 26, 28) leur étant associé. Ce système d'automatisation (2) comprend en outre un système de gestion central (10) qui communique avec lesdits composants (4, 6, 8, 10, 12) et dans lequel sont stockées les associations entre les composants (4, 6, 8, 10, 12) et les programmes (20, 22, 24, 26, 28).
EP04803111A 2003-11-13 2004-11-08 Systeme d'automatisation comprenant des composants communiquant entre eux Ceased EP1682954A2 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
DE10353052A DE10353052A1 (de) 2003-11-13 2003-11-13 Automatisierungsanlage mit untereinander kommunizierenden Komponenten
PCT/EP2004/012624 WO2005047992A2 (fr) 2003-11-13 2004-11-08 Systeme d'automatisation comprenant des composants communiquant entre eux

Publications (1)

Publication Number Publication Date
EP1682954A2 true EP1682954A2 (fr) 2006-07-26

Family

ID=34585056

Family Applications (1)

Application Number Title Priority Date Filing Date
EP04803111A Ceased EP1682954A2 (fr) 2003-11-13 2004-11-08 Systeme d'automatisation comprenant des composants communiquant entre eux

Country Status (3)

Country Link
EP (1) EP1682954A2 (fr)
DE (1) DE10353052A1 (fr)
WO (1) WO2005047992A2 (fr)

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE102004055814A1 (de) * 2004-11-18 2006-05-24 Endress + Hauser Process Solutions Ag Verfahren zur Inbetriebnahme eines Feldgerätes der Prozessautomatisierungstechnik
DE102006028797A1 (de) * 2006-06-23 2007-12-27 Khs Ag Austauschbares Antriebssystem
WO2010060976A1 (fr) * 2008-11-27 2010-06-03 Siemens Aktiengesellschaft Procédé pour concevoir un dispositif de contrôle-commande pour une installation industrielle
WO2010060977A1 (fr) * 2008-11-27 2010-06-03 Siemens Aktiengesellschaft Procédé pour concevoir un dispositif de contrôle-commande pour une installation industrielle
US8489210B2 (en) * 2009-03-24 2013-07-16 Rockwell Automation Technologies, Inc. Electronic operator interface based controller and device automatic downloads
EP2237123A1 (fr) * 2009-03-30 2010-10-06 Siemens Aktiengesellschaft Procédé, dispositif et programme de commande pour vérifications décentralisée de compatibilité des composants d' un système d' automatisation
DE102012001456A1 (de) 2012-01-25 2013-07-25 Dräger Medical GmbH Versionskontrolle für medizinische Anästhesiegeräte
JP6608889B2 (ja) 2017-09-12 2019-11-20 ファナック株式会社 数値制御装置、産業機械に含まれる装置及び数値制御システム
DE102018123613A1 (de) * 2018-09-25 2020-03-26 Innogy Se Firmwareupdate durch zentrales Steuermodul einer Ladestation

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP3329841B2 (ja) * 1991-10-18 2002-09-30 株式会社日立製作所 ネットワークシステム及びそのソフトウエア管理方法
BR9402027A (pt) * 1993-05-28 1994-12-13 Xerox Corp Processo para gerenciar uma configuração e assegurar compatibilidade entre componentes num sistema de computação, e, processo para eliminar incompatibilidades entre software residente e software de migração num sistema de computador automatizado
DE19845764A1 (de) * 1998-10-05 2000-04-13 Siemens Ag Speicherprogrammierbare Steuerung mittels Datenverwaltung über Netzrechner und Verfahren zum Betrieb einer speicherprogrammierbaren Steuerung
US6467088B1 (en) * 1999-06-30 2002-10-15 Koninklijke Philips Electronics N.V. Reconfiguration manager for controlling upgrades of electronic devices
US7130701B1 (en) * 2000-05-24 2006-10-31 Schneider Automation Inc. System for remote configuration monitoring of an industrial control system
TWI244603B (en) * 2001-07-05 2005-12-01 Dainippon Screen Mfg Substrate processing system for managing device information of substrate processing device
EP1283455A1 (fr) * 2001-08-03 2003-02-12 Siemens Aktiengesellschaft Dispositif pour la maintenance d'une installation technique comprenant un certain nombre de composants et/ou d'elements de logiciel

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See references of WO2005047992A2 *

Also Published As

Publication number Publication date
WO2005047992A3 (fr) 2005-07-14
DE10353052A1 (de) 2005-06-16
WO2005047992A2 (fr) 2005-05-26

Similar Documents

Publication Publication Date Title
EP0906596B1 (fr) Systeme d'automatisation de processus industriels
DE102007026678A1 (de) Verfahren zum Austausch eines defekten Feldgerätes gegen ein neues Feldgerät in einem über digitalen Feldbus kommunizierenden System, insbesondere Automatisierungssystem
EP3876046B1 (fr) Annotation de retour des sélections opérateur
WO2004106211A1 (fr) Procede et dispositif pour assurer la maintenance d'un systeme d'ascenseur ou d'escalier mecanique
DE10210280B4 (de) Steuerungen, Tools und diese umfassende Systeme
DE112004001775T5 (de) Verfahren und Vorrichtung zur Bereitstellung von automatischen Software-Updates
DE102005014941B4 (de) Verfahren zum Bereitstellen von Dokumentationsinformationen von komplexen Maschinen und Anlagen, insbesondere einer Spritzgussmaschine
WO2007090486A1 (fr) Systeme de determination de l'état d'usure d'une machine-outil
EP1779205A1 (fr) Procede pour faire fonctionner un appareil de champ d'automatisation
DE102011052384A1 (de) Automatische Annahme, Inspektion, Bestandsverwaltung und Berichterstellung mit Hilfe drahtloser Kommunikation
DE102004041469B4 (de) CNC-Fertigungsanordnung mit zentraler Datenbank
EP1638028A2 (fr) Génération assistée par ordinateur et gestion de changement pour interfaces utilisateur
DE102008060005A1 (de) Sicherheitssteuerung und Verfahren zum Steuern einer automatisierten Anlage mit einer Vielzahl von Anlagenhardwarekomponenten
EP3001310B1 (fr) Procédé et dispositif d'actualisation de micrologiciels pour des composants d'un système d'automatisation industriel
DE102017123090A1 (de) Robotersystem und Wartungsverfahren zum Verfolgen von Informationen eines Moduls
EP1682954A2 (fr) Systeme d'automatisation comprenant des composants communiquant entre eux
EP2808749B1 (fr) Procédé d'échange d'informations de commande entre des appareils de commande et d'observation d'un système d'automatisation industriel et système d'automatisation industriel
WO2011000367A1 (fr) Procédé et dispositif de traitement d'erreurs simplifié sur une machine-outil
WO2022028827A1 (fr) Procédé pour faire fonctionner un système et système couplé à un certain nombre de postes de production pour produire un produit
DE10131944A1 (de) Verfahren zur Verarbeitung von Daten
EP1331534B1 (fr) Système d'automatisation et procédé de génération de documentation
EP1454201B1 (fr) Systeme d'ingenierie et systeme d'automatisation
EP1019808B1 (fr) Systeme et procede sensible pour traitement de signaux numeriques et procede de fonctionnement d'un systeme sensible
EP0770946A1 (fr) Procédé pour l'interprétation redondante automatique et optimale de mesures pour des systèmes de bus dans des centrales électriques
DE202010017583U1 (de) System zur Planung der Wartung einer automatisierungstechnischen Anlage

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20060509

AK Designated contracting states

Kind code of ref document: A2

Designated state(s): DE FR GB IT

DAX Request for extension of the european patent (deleted)
RBV Designated contracting states (corrected)

Designated state(s): DE FR GB IT

17Q First examination report despatched

Effective date: 20070924

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION HAS BEEN REFUSED

18R Application refused

Effective date: 20080609