EP2132627A1 - Procédé de fonctionnement de composants de technologie d'automatisation et composants de technologie d'automatisation - Google Patents

Procédé de fonctionnement de composants de technologie d'automatisation et composants de technologie d'automatisation

Info

Publication number
EP2132627A1
EP2132627A1 EP07722036A EP07722036A EP2132627A1 EP 2132627 A1 EP2132627 A1 EP 2132627A1 EP 07722036 A EP07722036 A EP 07722036A EP 07722036 A EP07722036 A EP 07722036A EP 2132627 A1 EP2132627 A1 EP 2132627A1
Authority
EP
European Patent Office
Prior art keywords
program
component
central unit
unit
system program
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.)
Withdrawn
Application number
EP07722036A
Other languages
German (de)
English (en)
Inventor
Frank Springer
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 EP2132627A1 publication Critical patent/EP2132627A1/fr
Withdrawn legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/4401—Bootstrapping
    • G06F9/4416—Network booting; Remote initial program loading [RIPL]
    • 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/05—Programmable logic controllers, e.g. simulating logic interconnections of signals according to ladder diagrams or function charts
    • 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/10—Plc systems
    • G05B2219/13—Plc programming
    • G05B2219/13062—Booting

Definitions

  • the present invention relates to an operating method for a component of automation technology.
  • the present invention further relates to such a component itself.
  • Control systems of control systems for example the central units of programmable logic controllers (PLCs), the control units of numerical control (CNCs) and motion control units (MCU), sensor modules, distribution nodes of modular control systems, etc.
  • PLCs programmable logic controllers
  • CNCs numerical control
  • MCU motion control units
  • sensor modules for example the sensors, sensors, etc.
  • CPU central control device of a modular control system
  • central unit is always used for the element of the component of the automation technology which contains the various programs which are required for the proper operation of the component. If the component of the automation technology includes both CPU functionality and has peripheral units, is spoken by a compact device.
  • the CPU has a system memory in the prior art.
  • the system memory is designed as a remanent memory.
  • a system program is stored in the system memory. Due to the execution of the system program, the central unit in operation of the CPU with (at least) one peripheral unit connected to the central unit.
  • the (at least one) peripheral unit is in operative connection with a technical process.
  • the system program can cause the central unit first to detect a degree of expansion of the control system, ie how many peripheral units are connected to the central unit. Next, for example, the central processing unit can recognize which peripheral units it is.
  • the system program causes the central unit to cyclically receive at least one status signal of the industrial technical process from the at least one peripheral unit and to transmit at least one control signal intended for the industrial technical process to the at least one peripheral unit.
  • the system program (at least in the rule) neither effects the processing of the received status signal nor the determination of the control signals to be transmitted.
  • this processing and determination usually takes place in that the central unit executes an application program which determines the processing and determination.
  • the user program can be created by a user. It can be supplied to the CPU by the user. It can also be deleted or changed.
  • the system program can not usually be changed by the user.
  • the object of the present invention is to provide possibilities by means of which the system program can be changed flexibly, in particular as a function of application and / or configuration or other criteria, in a simple manner adaptable.
  • a central unit of the component executes a boot program stored in a boot memory of the component. Due to the execution of the boot program, the central unit is able to communicate with a server, accept a system program from the server, and store the received system program in the system memory, possibly overwriting a system program already stored in a system memory of the component. The central unit continues to execute the system program. Due to the execution of the system program, the central unit communicates at least once with at least one peripheral unit connected to the central unit, which is connected to an industrial unit. technical process is in operative connection.
  • the boot program is thus configured in such a way that communication between the central unit and the at least one peripheral unit is not possible due to the execution of only the boot program.
  • the start condition may occur when a start command is given to the central unit by the server or via a man-machine interface of the component by a user.
  • the start condition may occur when the central unit has communicated with the at least one peripheral unit a predetermined number of times or during a predetermined time period. It is also possible for the central unit to execute a user program quasi-simultaneously with the system program, and the start condition to occur when a new user program is supplied to the component.
  • the central unit accepts at least one status signal of the industrial-technical process from the at least one peripheral unit and transmits at least one control signal intended for the industrial technical process to the at least one peripheral unit ,
  • the central processing unit determines the at least one control signal based on at least the at least one status signal based on the execution of the user program.
  • the component can be designed as a central control device of a modular control system.
  • the component has a control bus interface parts via which the at least one peripheral unit can be connected to the central unit.
  • the component is designed as a distributor node of a modular control system.
  • the central unit receives at least one status signal of the industrial technical process from the at least one peripheral unit and forwards it to a higher-level control device.
  • the central unit receives from the higher-level control device at least one control signal intended for the industrial technical process and forwards it to the at least one peripheral unit.
  • FIG. 1 shows schematically a system of automation technology, a server and an industrial technical process
  • FIGS. 2 to 4 flow charts
  • a component 1 of the automation technology is designed as a central control device (CPU) of a modular control system, for example as a CPU of a PLC.
  • CPU central control device
  • the embodiment of the component 1 as a central control device is purely exemplary.
  • the component 1 of the automation technology could alternatively be designed differently, for example as a distribution node of a modular Control system (see the following explanations to FIG 5) or as a sensor device '(see subsequent comments on FIG 7). Other embodiments are possible.
  • the component 1 of the automation technology has a central unit 2, a boat memory 3 and a system memory 4.
  • the central unit 2 may be, for example, a microprocessor.
  • a boot program 5 is stored in the boat memory 3.
  • a system program 6 can be stored in the system memory 4.
  • the system memory 4 may be empty or otherwise populated.
  • the component 1 (at least) has a communication interface 7, via which the central unit 2 can communicate with a server 8.
  • a user memory 9 is furthermore provided, in which a user program 10 can be stored.
  • the user memory 9 may be empty or otherwise populated.
  • the component 1 executes an operating method, which is explained in more detail below in conjunction with FIG.
  • designs are concerned with regard to the component 1 of the automation technology, they are generally valid.
  • embodiments are concerned with respect to the central controller, they are specific to the central controller.
  • the central unit 2 checks in a step S1 whether a start condition is fulfilled. On possible starting conditions will be discussed later in more detail.
  • a step S2 the central unit 2 executes the boot program 5. Due to the execution of the boot program 5, the CPU 2 is able to communicate with the server 8 in particular. Under what circumstances and in what form the central unit 2 communicates with the server 8, will be explained later in more detail.
  • the central unit 2 When the central unit 2 communicates with the server 8, due to the execution of the boot program 5, the central unit 2 is still able to receive from the server 8 a (new) system program 6 and to store the newly accepted system program 6 in the system memory 4. If necessary, a system program 6 which has already been stored in the system memory 4 can be overwritten. Under what conditions the central unit 2 receives the system program 6 from the server 8 and stores it in the system memory 4 will also be explained below.
  • the CPU 2 executes the system program 6 stored in the system memory 4. Due to the execution of the system program 6, the central unit 2 communicates at least once with at least one peripheral unit 11, which is connected to the central unit 2 - according to FIG. 1 via a control bus interface 12 of the central control unit. The type of communication will also be discussed in more detail below. It is important that the communication of the central unit 2 with the peripheral units 11 takes place in the context of the execution of the system program 6.
  • the boot program 5 is designed in such a way that communication between the central unit 2 and the peripheral units 11 is not possible due to the execution of only the boot program 5.
  • the peripheral units 11 are in operative connection with an industrial technical process 13.
  • the peripheral units 11 are therefore capable of detecting at least one state signal E of the industrial technical process 13 and forwarding it to the component 1 of the automation technology. Alternatively or additionally, the peripheral units 11 are able to output at least one control signal A to the industrial technical process 13 and to influence the industrial technical process 13 in this way.
  • step S3 is divided into three steps Sil, S12 and S13.
  • the central processing unit 2 executes a first part of the system program 6.
  • the central unit 2 receives from the peripheral units 11 the status signals E of the industrial technical process 13.
  • the central unit 2 executes the user program 10 stored in the user memory 9.
  • the user program 10 contains instructions by means of which the central unit 2 evaluates the status signals E received in step S11.
  • the central unit 2 determines the control signals A for the industrial technical process 13 on the basis of the state signals E-optionally with the additional use of internal state signals of the component 1 (examples of such state signals are the values of timers, counters and markers) the central unit 2 from a second part of the system program 6 from.
  • the central unit 2 transmits the control signals A intended for the industrial technical process 13 to the peripheral units 11.
  • the local stagingdiagra ⁇ un is performed cyclically.
  • a cycle time ie the time required for a single pass through the flowchart of FIG. 3 is generally a few milliseconds, in some cases less than a millisecond, eg. At 125 microseconds.
  • the central unit 2 must therefore continuously between the execution of the system program 6 (keyword "Acceptance of the state signals E and transmitting the control signals A") on the one hand and the execution of the user program 10 (keyword "evaluation of the status signals E and determining the control signals A") back and forth turn.
  • the central unit 2 thus executes the system program 6 and the user program 10 quasi-simultaneously.
  • the component 1 of the automation technology can thus be one of the following units:
  • a central control device of a modular control system for example a CPU of a PLC such as, purely by way of example, a CPU of the SIMATIC S7-300 series from Siemens AG, or
  • control device in which peripheral units 11 are already integrated into the control device.
  • An example of such a control device is a compact PLC of the earlier series SIMATIC S5-90 or SIMATIC S5-95 from Siemens AG.
  • peripheral units 11 are already integrated in the control device, it is even possible for the respective compact device (definition see above) to be expanded by means of further peripheral units 11.
  • the SIMATIC S5-95 module from Siemens AG already has peripheral units 11 on the compact device (onboard). additionally however, peripheral units 11 of the SIMATIC S5-100 modular control system can be connected to this compact device.
  • a step S14 the central unit 2 checks whether a new user program 10 is being supplied to it. If no new user program 10 is supplied to the CPU 2, a suitable response is taken. Which reaction is appropriate may depend on the circumstances of the case. For example, when the user program 10 executed by the CPU 2 is a user program of a programmable logic controller, it is possible to go back to the step S11 directly. On the other hand, if the user program 10 is a manufacturing specification for a single workpiece to be manufactured (not multiple), it is possible to go back to step S14.
  • a procedure is explained in conjunction with FIG 3, which is always applicable.
  • step S1 is returned.
  • the step Sl of FIG. 3 is identical to the step S1 of FIG. 2 and therefore does not need to be explained again.
  • step S15 the central unit 2 takes over the new user program 10.
  • the step S15 may in particular comprise a storage of the new user program 10 in the user memory 9.
  • step S16 the CPU 2 sets the start condition to "satisfied.” After the execution of step S16, the CPU 2 proceeds to step S1.
  • the step S2 of FIG. 2 is also contained in FIG. 3 in terms of content. However, it is divided in steps S17 to S21.
  • step S17 the controller 2 sets the start condition to "not satisfied.” The step S17 is required so that the steps S17 to S21 are executed only once after supplying a new user program 10.
  • step S18 the CPU 2 checks whether the current system program 6 for the newly supplied user program 10 is optimal. If so, it goes directly to step S22. Otherwise, steps S19 to S21 are executed. Step S18 is only optional. If it is omitted, steps S19 to S21 are always executed.
  • step S19 the CPU 2 makes contact with the server 8. It transmits to the server 8 at least one identification, from which the type of the component 1 emerges. Furthermore, it transmits - at least as a rule - information based on which the server 8 can determine the optimal system program 6. For example, the central processing unit 2 can transmit to the server 8 the user program 10, a typing of the user program 10 or an identification for the optimal system program 6 ("I need system program no. 7").
  • the central unit 2 can also transmit further information to the server 8 as part of the step S19. For example, it may additionally transmit an identification, by means of which the component 1 can be clearly differentiated from other components, ie in particular also of identical components 1. Other information can also be transmitted, for example an update status of the system program 6 currently stored in the system memory 6.
  • step S20 the central processing unit 2 receives from the server 8 the new, optimal system program 6.
  • step S21 the central unit 2 stores the received system program 6 in the system memory 4.
  • step S22 the central unit 2 checks whether the user program 10 is to be executed.
  • the CPU 2 proceeds to step Sil. Otherwise, the CPU 2 proceeds to step S14.
  • Step S22 is optional only. However, due to step S22, how often the user program 10 is executed may be limited. For, depending on the situation of the individual case, a one-time execution, a repeated execution or a continuous execution (that is to say until the occurrence of a termination condition, eg the specification of a stop command by a user 14) may alternatively be expedient.
  • a step S31 the central unit 2 checks whether the user 14 has given it a start command via a human-machine interface 15. Furthermore, in a step S32, the central unit 2 checks whether a start command has been specified by the server 8 (ie a communication request has been transmitted). Furthermore, the central unit 2 checks in a step S33 whether it has executed the user program 10 sufficiently often. In the context of step S33, it therefore compares the number of times it has executed the user program 10 with a predetermined number. This check corresponds to the number of times that the central unit 2 has communicated with the peripheral units 11 due to the cyclical execution of the steps S1 to S3 (see FIG. 2). So she checks in the frame of step S34, whether it has communicated with the peripheral units 11, for example, for at least four hours or three days, or whether a certain time has been reached, an absolutely predetermined period of time is thus completed.
  • step S35 sets the start condition to "satisfied."
  • step S35 of FIG. 4 corresponds to step S16 of FIG S35 is followed by step S1, which has already been explained in conjunction with FIG.
  • the present invention has been explained above in connection with a control device of a control system.
  • the control system could be modular or non-modular.
  • the present invention is not limited to controllers. It is for example - in particular as far as the embodiments according to FIG 2, according to FIG 3, steps S17 to S21 and according to FIG 4 applies - applicable to other components 1 of automation technology. An example of such a component is explained in more detail below in conjunction with FIGS. 5 and 6.
  • the component 1 is designed as a distributor node of a .nodular control system.
  • the distribution node 1 is connected to the peripheral units 11 via a peripheral interface 16.
  • the peripheral units 11 can detect status signals E of the industrial technical process 13 and / or output control signals A to the industrial technical process 13.
  • the distribution node 1 is furthermore connected via a control bus interface 17 to a higher-level control device 18.
  • the control device 18 of FIG. 5 may be, for example, the central control device of FIG. However, it may alternatively also be another control device.
  • the distribution node 1 executes an application program 10. Alternatively, it is possible that the distribution node 10 does not process a user program. Communication with the Server 8 can be done directly. Alternatively, the communication can take place via the higher-level control device 18. Furthermore, it is possible that the higher-level control device 18 is identical to the server 8.
  • the distribution node 1 of FIG. 5 executes the operating method described above in connection with FIG.
  • the step S3 is hereby divided in FIG. 6 in steps S41 to S44.
  • step S41 the CPU 2 receives from the peripheral units 11 state signals E of the industrial technical process 13.
  • step S42 the central unit 2 forwards the status signals E to the higher-order control device 18.
  • step S43 the central unit 2 receives from the higher-level control device 18 the control signals A for the industrial technical process 13.
  • step S44 the CPU 2 forwards the control signals A to the peripheral units 11.
  • the component 1 of the automation technology is designed as a sensor device.
  • a plurality of sensors 19 are connected to the sensor device 1.
  • the sensors 19 may be part of the sensor device 1. Alternatively, they can be independent elements.
  • the sensors 19 correspond to the peripheral units 11.
  • the sensor device 11 of FIG. 7 is connected to an evaluation device 21 via a communication interface 20.
  • the communication with the server 8 takes place either via the evaluation device 21 or directly to the server 8.
  • the evaluation device 21 can be identical to the server 8. According to FIG. 8, the steps S1 to S3 of FIG. 2 are implemented as follows:
  • a step S51 the CPU 2 checks whether the quantity to be detected is to be changed. A change of the quantity to be detected corresponds to the occurrence of the start condition.
  • a step S52 (corresponding to the step S1 of FIG. 2), the CPU 2 checks whether the start condition is satisfied.
  • the CPU 2 makes contact with the server 8 in a step S53. It transmits at least one type identification as part of step S53. In general, it also transmits an identification for the required system program 6 or for the size to be detected.
  • the step S53 of FIG. 8 substantially corresponds to the step S19 of FIG. 3.
  • a step S54 the central unit 2 receives from the server 8 the required system program 6.
  • the CPU 2 stores the received system program 6 in the system memory 4. Steps S54 and S55 of FIG. 5 correspond to steps S20 and S21 of FIG. 3.
  • a step S56 the CPU 2 detects the quantity to be detected. If necessary, it carries out further measures. Further measures may be, for example, saving or pre-value of the detected quantity. Alternatively or additionally, it is possible for the detected variable-at least from time to time-to be transmitted to the evaluation device 21.
  • the step S56 corresponds to an implementation of the step S3 of FIG. 2.
  • the component 1 of the automation technology periodically -. B. once a day, once a week or once a month - the server 8 asks if an update of the system program 6 is present.
  • component 1 Furthermore, it is possible during startup of component 1 to first execute a first system program 6, with which tests and initialization operations of component 1 are carried out, and then to reload a second system program 6 and optionally also further system programs 6, which successively during operation of component 1 needed.
  • a user program 10 in which only two or three axes need to be controlled, can be executed faster than a user program 10 in which, for example, five or six or even more axes are activated Need to become.
  • the system memory 4 is a Remanentspeieher, that is, the contents of the system memory 4 is maintained even when the power supply of the system memory 4 is turned off.
  • An example of such a remanent memory is a flash EPROM.
  • the system memory 5 is a volatile memory, e.g. B. a simple RAM. As a rule, either no system program 6 or only a single system program 6 is stored in the system memory 4. Alternatively, however, it is possible to dimension and operate the system memory 4 in such a way that two system programs 6 are simultaneously stored in the system memory 4.
  • System memory 4 an executable system program 6 available.
  • system program 6 generally does not process any status signals E of the process 13 and also does not determine any control signals A of the process 13. In individual cases, however, this is possible.
  • the boat memory 3 is always a remanent memory.
  • the boot program 5 stored in the retentive memory 3 can be unchangeable. Alternatively, it is possible that the boot profile 5 can also be updated. Analogous to the possibility of simultaneously storing two system programs 6 in the system memory 4, but only one of the system programs 6 is activated, such a procedure is also possible with respect to the boot memory 3 and the boot programs 5.
  • connection of component 1 to the server 8 is in principle of any nature. It can be direct or indirect. It can be wired or conduction-free. It can be a network connection or a point-to-point connection. Preferably, the communication between the component 1 and the server 8 via the Internet.
  • An update of the system program 6 is possible in a simple manner by means of the present invention. Furthermore, adaptations of the system program 6 to special circumstances (for example, to a user program 10 to be executed) are possible in a simple manner. A complicated interaction with the user 14 is not required.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Automation & Control Theory (AREA)
  • Computer Security & Cryptography (AREA)
  • General Engineering & Computer Science (AREA)
  • Programmable Controllers (AREA)

Abstract

Composant (1) de technologie d'automatisation comprenant une unité centrale (2), une mémoire de chargement (3) et une mémoire système (4). L'unité centrale (2) exécute un programme de chargement (5) enregistré dans la mémoire de chargement en présence d'une condition de démarrage. L'unité centrale (2) est en mesure, suite à l'exécution du programme amorce (5) de communiquer avec un serveur (8), de recevoir du serveur (8) un programme système (6) et d'enregistrer le programme système (6) reçu dans la mémoire système (4) avec réécriture éventuelle d'un programme système (6) qui est déjà enregistré dans une mémoire système (4). L'unité centrale (2) continue d'exécuter le programme système (6). L'unité centrale (2) communique, suite à l'exécution du programme système (6), au moins une fois avec au moins une unité périphérique (11) qui est reliée à l'unité centrale (2) et qui est en liaison active avec un processus technique industriel (13). En revanche, le programme de chargement (5) est conçu de telle façon que suite à l'exécution exclusivement du programme de chargement (5), il est impossible pour l'unité centrale (2) de communiquer avec ladite au moins une unité périphérique (11).
EP07722036A 2007-03-14 2007-03-14 Procédé de fonctionnement de composants de technologie d'automatisation et composants de technologie d'automatisation Withdrawn EP2132627A1 (fr)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/DE2007/000463 WO2008110128A1 (fr) 2007-03-14 2007-03-14 Procédé de fonctionnement de composants de technologie d'automatisation et composants de technologie d'automatisation

Publications (1)

Publication Number Publication Date
EP2132627A1 true EP2132627A1 (fr) 2009-12-16

Family

ID=38294146

Family Applications (1)

Application Number Title Priority Date Filing Date
EP07722036A Withdrawn EP2132627A1 (fr) 2007-03-14 2007-03-14 Procédé de fonctionnement de composants de technologie d'automatisation et composants de technologie d'automatisation

Country Status (4)

Country Link
US (1) US20100162228A1 (fr)
EP (1) EP2132627A1 (fr)
DE (1) DE112007003496A5 (fr)
WO (1) WO2008110128A1 (fr)

Family Cites Families (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH03241448A (ja) * 1990-02-20 1991-10-28 Fujitsu Ltd Ｉｐｌ方式
US6223284B1 (en) * 1998-04-30 2001-04-24 Compaq Computer Corporation Method and apparatus for remote ROM flashing and security management for a computer system
US6609127B1 (en) * 1999-06-09 2003-08-19 Amx Corporation Method for dynamically updating master controllers in a control system
US20010034567A1 (en) * 2000-01-20 2001-10-25 Allen Marc L. Remote management of retail petroleum equipment
US6748457B2 (en) * 2000-02-03 2004-06-08 Realtime Data, Llc Data storewidth accelerator
US7072950B2 (en) * 2001-01-23 2006-07-04 Sony Corporation Method and apparatus for operating system and application selection
US8677117B2 (en) * 2003-12-31 2014-03-18 International Business Machines Corporation Remote management of boot application
KR100622671B1 (ko) * 2004-12-21 2006-09-19 한국전자통신연구원 홈게이트웨이 플랫폼에 독립적인 댁내장치 원격제어시스템 및 방법
KR100690877B1 (ko) * 2005-08-11 2007-03-09 엘지전자 주식회사 이동통신 시스템에서의 주기적인 위치추적 방법
US8010965B2 (en) * 2006-08-31 2011-08-30 Intel Corporation Automatic task performance as scheduled using embedded secondary processor
US8332869B2 (en) * 2007-11-21 2012-12-11 Dell Products L.P. Systems and methods for providing wake on LAN (WoL) support

Non-Patent Citations (1)

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

Also Published As

Publication number Publication date
DE112007003496A5 (de) 2010-02-11
US20100162228A1 (en) 2010-06-24
WO2008110128A1 (fr) 2008-09-18

Similar Documents

Publication Publication Date Title
DE102006047026B4 (de) Verfahren und System zum redundanten Ansteuern einer Slaveeinrichtung
EP2067081B1 (fr) Procédé destiné à la synchronisation de deux dispositifs de commande et dispositif d'automatisation monté de manière redondante
EP2817682B1 (fr) Procédé permettant un fonctionnement à sécurité intégrée d'un système de commande de processus à l'aide de dispositifs de commande redondants
WO2010121797A1 (fr) Système de commande de sécurité pour le pilotage d'un atelier automatisé, et procédé de réalisation d'un programme utilisateur pour un système de commande de sécutité
DE102007026678A1 (de) Verfahren zum Austausch eines defekten Feldgerätes gegen ein neues Feldgerät in einem über digitalen Feldbus kommunizierenden System, insbesondere Automatisierungssystem
EP1779205A1 (fr) Procede pour faire fonctionner un appareil de champ d'automatisation
WO2015007297A1 (fr) Unité de détection de données et système d'automatisation
EP0791874B1 (fr) Méthode et dispositif de commande de capteurs et/ou actionneurs binaires
EP1238318A1 (fr) Automate programmable et procede d'actualisation
DE10326542B4 (de) Betriebsverfahren und Steuerungsprogramm für eine Zentraleinheit eines Automatisierungssystems sowie Zentraleinheit eines Automatisierungssystems und Automatisierungssystem selbst
DE102006059708B4 (de) Antriebssteuerung für zumindest einen elektrischen Motor
WO2010121798A1 (fr) Système et procédé de répartition de données de projets d'une commande de sécurité d'une installation automatisée aux composants de commande
EP2002316B1 (fr) Dispositif de commande a modele de machine integre
EP1903530B1 (fr) Agencement doté d'un appareil sous vide et son procédé de fonctionnement
WO2014184276A1 (fr) Système de commande et procédé de commutation de modules d'entrée/sortie d'un système de commande
EP1881385A1 (fr) Système pour un échange d'informations entre une machine de traitement et un dispositif de transmission
EP2216696B1 (fr) Procédé et système de communication pour la configuration d'un module de communication intégré dans un module logique
EP0647890A1 (fr) Module de calcul pour un système d'automatisation modulaire
EP2132627A1 (fr) Procédé de fonctionnement de composants de technologie d'automatisation et composants de technologie d'automatisation
DE102011122516A1 (de) Verfahren zum Reduzieren des Ressourcenverbrauchs von Automatisierungsanlagen
EP3582032B1 (fr) Dispositif de terrain à temps d'arrêt réduit lors de la mise à jour du micrologiciel
DE4210844C2 (de) Programmierbare Steuerung und Verfahren zur Überwachung eines Ablaufprogrammes für eine programmierbare Steuerung
DE102011122515A1 (de) Ereignisschnittstelle für Energiemanagementsystem
DE102012025228A1 (de) Steuerungsübergreifende Energieverwaltung in einer Anlage
EP2420908A1 (fr) Dispositif d'automatisation et procédé de fonctionnement et d'estimation du temps de fonctionnement

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: 20090617

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LI LT LU LV MC MT NL PL PT RO SE SI SK TR

DAX Request for extension of the european patent (deleted)
17Q First examination report despatched

Effective date: 20100610

RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: SIEMENS AKTIENGESELLSCHAFT

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

Free format text: STATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWN

18D Application deemed to be withdrawn

Effective date: 20151001