WO2018010801A1 - Procédé et outil d'ingénierie d'une installation de la technique des procédés ou des processus industriels - Google Patents

Procédé et outil d'ingénierie d'une installation de la technique des procédés ou des processus industriels Download PDF

Info

Publication number
WO2018010801A1
WO2018010801A1 PCT/EP2016/066799 EP2016066799W WO2018010801A1 WO 2018010801 A1 WO2018010801 A1 WO 2018010801A1 EP 2016066799 W EP2016066799 W EP 2016066799W WO 2018010801 A1 WO2018010801 A1 WO 2018010801A1
Authority
WO
WIPO (PCT)
Prior art keywords
plc
module
interface
engineering
interfaces
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
PCT/EP2016/066799
Other languages
German (de)
English (en)
Inventor
Mathias Maurmaier
Andreas Stutz
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
Siemens Corp
Original Assignee
Siemens AG
Siemens Corp
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, Siemens Corp filed Critical Siemens AG
Priority to PCT/EP2016/066799 priority Critical patent/WO2018010801A1/fr
Publication of WO2018010801A1 publication Critical patent/WO2018010801A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

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—Program-control systems
    • G05B19/02—Program-control systems electric
    • G05B19/04—Program control other than numerical control, i.e. in sequence controllers or logic controllers
    • G05B19/042—Program control other than numerical control, i.e. in sequence controllers or logic controllers using digital processors
    • G05B19/0423—Input/output
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; 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/46—Multiprogramming arrangements
    • G06F9/54—Interprogram communication

Definitions

  • the invention relates to a method for engineering a process or process plant with at least ei ⁇ nem function module, wherein the function module comprises a memory ⁇ programmable controller (module PLC). Furthermore, the invention relates to a tool for assisting in carrying out such a method.
  • the structure of the plant is usually recorded in a first step and an R & I flow chart by means of the tool the plant or parts of the system by link ⁇ tion of graphic process objects created.
  • the graphic process objects represent those for the operation of the
  • Plant components required such as sensors, motors, pumps, valves, piping, tanks, reactors, etc., or they represent functional modules that are increasingly used in the course of increasing modularization of plants.
  • the trend in process and process technology is actually towards modules with defined basic operations and their provision as functional units, the so-called function modules.
  • the functional modules with its own intelli ⁇ gence come in the form of a modular PLC.
  • the useable for this purpose controls often called Program Logic Controller (PLC), can originate from various manufacturers learning, that is, different in a plant is put ⁇
  • Function modules can be equipped with differing controllers from different manufacturers.
  • top-level PLC master programmable logic controller
  • the invention is therefore based on the object to find a method for engineering a process or process plant with at least one functional module, which is characterized by less effort. Another object is to provide a suitable tool for assisting in the implementation of the engineering process. To solve this problem, the new engineering method in claim 1, the new engineering tool on the features mentioned in claim 4. Advantageous developments of the invention are described in the dependent claims.
  • the invention has the advantage that a process or process plant with several functional modules, which can be equipped with controls from different manufacturers, can be engineered without the respective manufacturer-specific engineering tools of the control manufacturer.
  • the user of the plant no longer has to deal with the various engineering tools of the control manufacturers when engineering his plant and no longer has to acquire the specialized knowledge required to operate these tools.
  • the user can now advantageously manage with a single plant engineering tool.
  • the engineering of a functional module which is provided for a one ⁇ set in a facility can be performed from the module manufacturer.
  • the manufacturer of the functional module can in turn to specialized engineering tools USAGE ⁇ that are specific to the manufacturer of the module PLC used in the module.
  • the module manufacturer is thus given full access to the configuration of the controller during the automation of the function module.
  • connection settings in the top-level PLC and in particular in the module PLC for setting up the communication interfaces omitted, the associated with the plant engineering effort for the user is significantly reduced.
  • This reduced cost means that no longer has to function modules are only connected communi ⁇ kativ via a communication interface with a top-level plc but via several interfaces that can take advantage of different communication mechanisms. Different mechanisms usually have different advantages and disadvantages.
  • a template for the various communication interfaces of the modules is created at the manufacturer of the plant control system, which serves as a template for a later Proxyerstel ⁇ ment in plant engineering.
  • the engineering method thus uses a proxy pattern as the software architecture, with a template provided for plant engineering serving as a template for the proxy, which is implemented in the user program of the top-level PLC.
  • the Templa ⁇ te is specifically configured for the particular type of communication interface, and by means of a semantic description of the interface.
  • the manufacturer of the plant control system or, alternatively, the manufacturers of the functional modules used in the plant provide suitable templates for use in plant engineering for all interface types occurring in the plant.
  • the plant engineering tool therefore has a template for each interface type of the function modules that appears in the plant, on the basis of which a proxy is created, integrated in the user program of the top-level PLC and configured accordingly.
  • the template for the communica tion ⁇ interface can be translated into an implementation linkage with the Informatio ⁇ nen from a description file by the plant engineering tool, which can be considered part of the control system. Therefore, the template is preferably generated using the Anla ⁇ gen engineering tool and supplied by the Leitsystemherstel ⁇ ler.
  • the information necessary for the configuration of the proxy derived from the semantic Thomasstellenbe ⁇ scription of the connected respectively by means of the communication interface of the ⁇ le function module.
  • the file with the semantic See description can be generated from the information budget of Mo ⁇ dul-engineering tool, with which the manufacturer of the functional module develops the user program of the Mo- dul PLC. This may for example be made by the program's creator, the data highlighted in the user program the module PLC, which needed in the top-level PLC ⁇ to, and still indicates over which communication interface ⁇ put this data between module PLC and Top Level PLC should be ⁇ over.
  • the interface in the user program is created on the side of the module PLC and the information about the interface to be transferred data, which usually hun ⁇ derte of records include, for example, communication ⁇ channel, address, Information about the cycle time etc. is exported to a file with the semantic interface description of the function module.
  • Interface between functional module and control system, and the file with the semantic description of the respective interface which can be generated by means of a module engineering tool, as described above, or in some other way, and which is used by the plant engineering tool. be prepared, this creates a proxy, which can be included ⁇ example as a function block in the user program of the top-level PLC.
  • the template for the creation of the proxy is provided with its provision in the plant engineering tool and in plant engineering by means of the information from the semantic
  • Interface description of the respective function module is instantiated and configured.
  • a proxy which is implemented in the user program of the top-level PLC, a functional integration of functional modules is achieved in a modular system, wel ⁇ cher accesses to functions and / or data of thejansmo- module in the operation of the system as proxy accesses allows the ⁇ who.
  • a proxy is created in the user program of the top-level PLC with comparatively little effort for each of the interfaces. This makes it possible, for example, to realize a combination of cyclic and acyclic communication mechanisms in a functional module.
  • a cyclical communication mechanism ensures the advantages of real-time communication. Larger amounts of data can be transported by means of the acyclic communication mechanism, so that the real-time communication remains unaffected.
  • the realization of a respective proxy for the various communication interfaces as function blocks of the user program in the top-level PLC has the advantage that the proven function block concept according to IEC 61131 can be used for their integration into the user program.
  • a common facade in the top-level PLC is created for several proxies.
  • This combination of a proxy and façade pattern-based software architecture makes it much easier for the user to access a function implemented by a functional module that is implemented with multiple proxies. access if the function can be accessed via the façade at a defined interface.
  • a façade pattern is a design pattern in the field of software development and the façade created according to this pattern in the user program of the top-level PLC provides a uniform and advantageously simplified interface to the various communication interfaces and to the functions and / or data a functional module.
  • FIG. 1 shows in a simplified schematic representation as an example a plant 1 in which a process 2 is controlled by means of an automation system.
  • the automation ⁇ system includes a tool 3 for the engineering of the system 1, an operating and monitoring device 4, a top-level PLC 5 and a PLC 6, which are connected to each other via a bus system 7 for data communication.
  • a facade 8 is implemented, which handles To ⁇ to functions and / or data of a functional module 9 allows the module PLC 10 with two communication ⁇ interfaces 11 and 12 is connected to the top-level PLC 5.
  • a multiplicity of functional modules can, of course, be connected to the facade 8 or to a large number of facades realized in the top-level SPS 5.
  • the top-level PLC 5, the PLC 6 and the module PLC 10 control the process 2 in accordance with configurable user programs.
  • a variety of field devices 13 and 14 continue to be used.
  • RadioGunowkei ⁇ th field devices 14 are connected by means of a field bus 16 for commu ⁇ nication with the PLC 6.
  • the field devices 13, 14 can be, for example, transducers which serve to detect process variables, such as, for example, temperature, pressure, flow rate, fill level, density or gas concentration of a medium.
  • the field devices 13, 14 may likewise be actuators, by means of which the process sequence is influenced in accordance with detected process variables according to the specifications of the user programs.
  • actuators may be mentioned a control valve, a heater or a pump.
  • Figure 2 shows the implementation of the communication interface ⁇ filters 11 and 12 in a more detailed representation.
  • An interface 19 in the module SPS 10 is controlled by the herstel ⁇ ler of the function module in which the module-SPS is turned ⁇ sets 10, by means of a module-engineering tool, ches WEL specific to each controller used is re ⁇ alinstrument.
  • Prinzipi ⁇ ell, the interfaces 11 and 12 can be implemented in any way; it is of course possible to realize the interfaces 19 and 20 of the module PLC 10 using a proxy pattern as a reusable template in each case by a proxy in the user program of the module PLC 10.
  • the communication interfaces 11 and 12 which serve for the exchange of data between the top-level PLC 5 and the module PLC 10, to ⁇ next on physical interfaces 21 and 22 respectively led, which in each case a proxy 23 or 24 is connected downstream.
  • the physical interfaces 21 and 22 can be addressed by a user program in the form of the proxies 23 and 24, respectively.
  • the complexity of this automatically applied implementation is hidden by the facade 8, and thus the user-friendliness for the user is increased, as this by accessing the common facade 8 on the functions realized with the function module (9 in FIG. 1)
  • the communication interface 11 to the communica ⁇ tion function I device of PROFINET, that is, a communication system with cyclic data transmission, and the communication interface 12 to OPC UA, so a Kommunikati ⁇ onssystem with acyclic data transmission.
  • the combination of a cyclic and an acyclic data transmission advantageously avoids that the real time capability, which is a feature of the cyclic data transmission ⁇ , not by the large amounts of data, ge ⁇ is at risk for having a non-cyclic data transfer is often sufficient.
  • Alarm is transmitted while an identifier of the alarm and an associated high-precision timestamp are not transmitted in real time.
  • a module engineering tool 25 is used by the manufacturer, as shown in FIG.
  • Engineering by the module engineering tool 25 also specifies which variables in the late ⁇ ren operation of a plant with the function module 9 are seen to exchange.
  • These files 18 serve as the basis for the automated integration of the functional module 9 in the system 1, as previously explained with reference to FIG.
  • the files 18 can also be combined into one file. be prepared, ie it is not always necessary to have a separate file for each interface.
  • the templates 17, which serve as the basis for the proxy creation in addition to the files of the semantic interface description, are created, for example, with the aid of the plant engineering tool 3 and maintained for the later engineering of the plant.
  • TheVaccinel ⁇ development of the templates 17 may be effected for example by the manufacturer of the control system 1 series, which delivers the template 17 together with the plant engineering tool 3 to the Anlagenbetrei ⁇ over for carrying out the engineering.

Landscapes

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

Abstract

L'invention concerne un procédé et un outil pour l'ingénierie d'une installation de la technique des procédés ou des processus industriels (1) ayant au moins un module fonctionnel (9) comportant un automate programmable industriel (10, API-module), qui comprend plusieurs interfaces (11, 12) par le biais desquelles il est relié de manière communicative avec un automate de niveau supérieur (5, API de niveau supérieur). Un modèle (17) est disponible pour chaque type d'interface (11, 12) et un fichier (18) contenant la description sémantique respective de l'interface est disponible pour chaque interface (11, 12) et/ou sont écrits dans un outil d'ingénierie d'installation (3). Sur la base de ces données, un mandataire (23, 24) est créé au moyen de l'outil (3) pour chacune des interfaces (11, 12) pour permettre des accès à des fonctions et/ou à des données du module fonctionnel (9) au cours du fonctionnement de l'installation. Facultativement, une interface utilisateur commune (8), qui augmente la convivialité d'utilisation, est prévue les mandataires (23, 24).
PCT/EP2016/066799 2016-07-14 2016-07-14 Procédé et outil d'ingénierie d'une installation de la technique des procédés ou des processus industriels Ceased WO2018010801A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/EP2016/066799 WO2018010801A1 (fr) 2016-07-14 2016-07-14 Procédé et outil d'ingénierie d'une installation de la technique des procédés ou des processus industriels

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/EP2016/066799 WO2018010801A1 (fr) 2016-07-14 2016-07-14 Procédé et outil d'ingénierie d'une installation de la technique des procédés ou des processus industriels

Publications (1)

Publication Number Publication Date
WO2018010801A1 true WO2018010801A1 (fr) 2018-01-18

Family

ID=56411651

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2016/066799 Ceased WO2018010801A1 (fr) 2016-07-14 2016-07-14 Procédé et outil d'ingénierie d'une installation de la technique des procédés ou des processus industriels

Country Status (1)

Country Link
WO (1) WO2018010801A1 (fr)

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070067458A1 (en) * 2005-09-20 2007-03-22 Rockwell Software, Inc. Proxy server for integration of industrial automation data over multiple networks

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070067458A1 (en) * 2005-09-20 2007-03-22 Rockwell Software, Inc. Proxy server for integration of industrial automation data over multiple networks

Similar Documents

Publication Publication Date Title
DE102008014153B4 (de) Verfahren, Steuergerät und Steuerungssystem zur Steuerung eines Automatisierungssystems
DE102010029952A1 (de) Verfahren zum Integrieren von zumindest einem Feldgerät in ein Netzwerk der Automatisierungstechnik
DE102016201077A1 (de) Modul für eine technische Anlage und Verfahren zur Steuerung einer technischen Anlage
DE102011115809A1 (de) Verfahren zur Konfigurierung einer Steuereinrichtung
DE102008019053A1 (de) Verfahren zum Betreiben einer Anlage der Prozessautomatisierungstechnik
EP1658538B1 (fr) Procede pour generer des modules logiciels pour des appareils de terrain de la technique d'automatisation de processus
EP3246773B1 (fr) Procede de paramétrage d'une installation technique de processus ou de procede
DE102015200568A1 (de) Verfahren zum Austausch von Daten in einer automatisierungstechnischen Anlage
DE102013105097A1 (de) Steuerungseinrichtung und Verfahren zum Umschalten von Ein-/Ausgabeeinheiten einer Steuerungseinrichtung
EP3554050A1 (fr) Procédé de sécurisation d'un composants d'automatisation
WO1993003429A1 (fr) Installation industrielle automatisee a exploitation commerciale comprenant plusieurs parties
EP3616011B1 (fr) Dispositif et procédé de surveillance d'un système d'automatisation
EP2018603A1 (fr) Procede pour le parametrage d'un appareil de terrain de la technique d'automatisation de processus par reproduction de services acycliques
DE102008038501A1 (de) Verfahren zum Bestimmen einer statischen Datenstruktur eines Feldgerätes
DE10208530A1 (de) Betriebseinheit, Peripheriegerät und Verfahren zum Betrieb eines Peripheriegeräts
EP2985663A1 (fr) Procédé de simulation d'une installation industrielle automatisée
DE102007052031B4 (de) Verfahren zum Betreiben eines Parametrier-Gerätes
DE102007035159B4 (de) Verfahren zum Parametrieren von mehreren Feldgeräten der Automatisierungstechnik
DE102008042919A1 (de) Feldgerät der Prozessautomatisierungstechnik
EP2247989B1 (fr) Dispositif et procédé pour planifier l'intégration d'appareils de terrain d'une installation technique
LU500646B1 (de) Technik zur Bereitstellung einer Diagnosefunktionalität für eine auf einer speicherprogrammierbaren Steuerung basierenden Anwendung
EP2486459B1 (fr) Interface de bus de terrain et procédé de fonctionnement correspondant
DE102008023873A1 (de) Verfahren zum Betrieb eines Antriebssystems
WO2016079091A1 (fr) Procédé de fonctionnement d'un premier et d'au moins un deuxième appareil de terrain
EP2965157A1 (fr) Procédé et dispositif permettant de faire fonctionner une installation de traitement et/ou 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: 16738796

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16738796

Country of ref document: EP

Kind code of ref document: A1