EP2486464A2 - Procédé pour faire fonctionner une interface de bus de terrain - Google Patents

Procédé pour faire fonctionner une interface de bus de terrain

Info

Publication number
EP2486464A2
EP2486464A2 EP10751607A EP10751607A EP2486464A2 EP 2486464 A2 EP2486464 A2 EP 2486464A2 EP 10751607 A EP10751607 A EP 10751607A EP 10751607 A EP10751607 A EP 10751607A EP 2486464 A2 EP2486464 A2 EP 2486464A2
Authority
EP
European Patent Office
Prior art keywords
fieldbus
information
interface
fieldbus interface
communication
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
EP10751607A
Other languages
German (de)
English (en)
Inventor
Robert Kölblin
Michael Maneval
Jörg REINKENSMEIER
Axel PÖSCHMANN
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.)
Endress and Hauser Process Solutions AG
Original Assignee
Endress and Hauser Process Solutions 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 Endress and Hauser Process Solutions AG filed Critical Endress and Hauser Process Solutions AG
Publication of EP2486464A2 publication Critical patent/EP2486464A2/fr
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—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/4185—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 the network communication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/40—Bus networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H04L12/4604—LAN interconnection over a backbone network, e.g. Internet, Frame Relay
    • H04L12/462—LAN interconnection over a bridge based backbone
    • H04L12/4625—Single bridge functionality, e.g. connection of two networks over a single bridge
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/12—Discovery or management of network topologies
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/34—Signalling channels for network management communication
    • 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/31121—Fielddevice, field controller, interface connected to fieldbus
    • 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/31211—Communicate diagnostic data from intelligent field device controller to central
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/34—Signalling channels for network management communication
    • H04L41/344—Out-of-band transfers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/02—Capturing of monitoring data
    • H04L43/022—Capturing of monitoring data by sampling
    • H04L43/024—Capturing of monitoring data by sampling by adaptive sampling
    • 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 present invention relates to a method of operating a fieldbus interface connected to a fieldbus of process automation technology.
  • field devices are often used to detect and / or influence process variables.
  • Sensors such as level gauges, flowmeters, pressure and temperature measuring devices, pH redox potential measuring devices, conductivity measuring devices, etc., which record the corresponding process variables level, flow, pressure, temperature, pH or conductivity, are used to record process variables .
  • actuators such as valves or pumps, via which the flow of a liquid in a pipe section or the level in a container can be changed.
  • field devices are all devices that are used close to the process and that provide or process process-relevant information. A variety of such field devices is manufactured and sold by the company Endress + Hauser.
  • the higher-level units are control systems or control units, such as PLC (Programmable Logic Controller) or PLC (Programmable Logic Controller).
  • PLC Programmable Logic Controller
  • PLC Programmable Logic Controller
  • PAM systems where PAM for Plant Asset Management
  • “Assets” are generally the parts of a plant that represent a value of the plant, such as the field devices used in a plant.
  • PAM systems typically manage information about a plant's assets in a database.
  • the assets used in a system in particular field devices, an exchange of devices, changes to devices, such as the exchange of sensors, the implementation of a new software version, etc., are recorded in a PAM system and the respective time sequence documented.
  • a PAM system is often set up in such a way that it regularly carries out a network verification in order to determine the devices connected to a fieldbus in information technology. Furthermore, maintenance work performed by a PAM system is usually documented. In this case, in a PAM system, as a rule, also corresponding information for device integration of the various field devices of a system, in particular a device description and / or a device driver of the field devices, implemented.
  • a PAM system is formed, for example, by Field CareO from Endress + Hauser.
  • PAM systems are usually managed by the plant operator. In this case, they are often prepared separately from a higher-level unit (for example a PLC), which is used for process control, and connected to a higher-level corporate network (for example, to an Ethernet network).
  • a higher-level unit for example a PLC
  • a higher-level corporate network for example, to an Ethernet network.
  • the detection of the assets of several fieldbus segments in a common PAM system is that the PAM system should be informed as soon as possible about changes to a fieldbus, in particular via a change in the information technology connected to the relevant fieldbus devices.
  • higher-level communication units which are connected, for example, on a parent network to the field bus, the need that they are informed as soon as possible about such information, which affect the network management of the fieldbus. This is the only way to detect changes in a system promptly and, if necessary, detect errors early.
  • MC2 class 2 master
  • MC2 fieldbus interface
  • a fieldbus which is designed in accordance with the PROFIBUSO standard
  • a communication connection for example via a higher-level corporate network
  • PAM system or generally a higher-level communication unit
  • the MC2 can determine the information required for the PAM system (or the higher-level communication unit) concerning the network management of the fieldbus and forward this information to the PAM system (or the higher-level communication unit) ,
  • the MC2 itself has to query all required information because it does not have access to information concerning the network management of the fieldbus and is regularly polled by a class 1 master (abbreviated to MC1) connected to the fieldbus as part of process control.
  • the MC2 has only a relatively short time interval between the cycles of the MC1 for the communication to be performed, so that due to the high amount of data to be determined by the MC2, a considerable amount of time is required to retrieve all the required information. This will affect the timeliness of the information provided by the MC2. In addition, the data traffic on the fieldbus is considerably increased by the MC2. A corresponding problem exists among other things also with a field bus, which is designed according to the Foundation ⁇ - Fieldbus standard and in which a corresponding fieldbus interface is provided.
  • the document WO 2007/074105 A2 discloses a method for system monitoring in a system in which several field devices communicate with a process control unit and a system monitoring unit, such as a gateway, via a fieldbus.
  • the system monitoring unit checks the regular data traffic for information that is on Indicate diagnostic event on one of the field devices. If a telegram with an indication of a diagnostic event is detected, the system monitoring unit requests further diagnostic information from the relevant field device.
  • the object of the present invention is to provide a fieldbus interface for connection to a fieldbus process automation technology and a method for operating such a fieldbus interface through which at least information related to the network management of the fieldbus, as current as possible can be detected and to a Higher-level communication unit, such as a PAM system, be prepared directly or in edited form. An unnecessary burden of bus traffic on the fieldbus through the fieldbus interface should be avoided.
  • a method of operating a fieldbus interface connected to a fieldbus of process automation technology has the following steps:
  • the fieldbus interface can already receive a great deal of information relating to the network management of the fieldbus without itself conducting an active communication.
  • an MC1 in a fieldbus which is designed in accordance with the ProfibusO standard, usually carries out a query of the fieldbus addresses as part of the process control, in order to check which devices are connected under information technology among the various fieldbus addresses.
  • the fieldbus interface can accordingly receive information on which addresses are connected in terms of information technology, whether it is a master or a slave, and in the case of a slave, it can also belong to a specific one Master (if several Master Class 1 (MC1) are provided).
  • the fieldbus interface can also detect further information by listening, as will be explained in particular below with reference to further developments. Because the fieldbus interface also carries out active communication as required, it can query additional information that it requires from individual devices connected to the fieldbus, in particular field devices.
  • the fieldbus interface can interrogate information that would not be available in the context of process control from a higher-level unit (for example, a PLC that forms an MC1 in a ProfibusO network). In this way, further information can be provided by the fieldbus interface of a higher-level communication unit, such as a PAM system, in a timely manner, for example, than would be possible by a higher-level unit for process control.
  • a higher-level communication unit such as a PAM system
  • the fieldbus interface can comprehensively and up-to-date provide information concerning the network management of the fieldbus, without the bus traffic on the fieldbus being heavily loaded.
  • a fieldbus interface is a module which is designed for connection to a fieldbus and through which information which is communicated via the fieldbus can be provided at least partially to a higher-level communication unit.
  • the higher-level communication unit can be connected directly to the fieldbus interface via a higher-level network (eg a company-internal Ethernet LAN (LAN: local area network) or via another communication connection (eg a USB interface) ,
  • a higher-level network eg a company-internal Ethernet LAN (LAN: local area network) or via another communication connection (eg a USB interface)
  • a higher-level network eg a company-internal Ethernet LAN (LAN: local area network) or via another communication connection (eg a USB interface)
  • this parallel functionality of such a fieldbus interface can be realized, for example, in that the mechanical connection of the fieldbus interface, via which it is connected to the fieldbus, branches off into two "channels" along which the incoming telegrams are routed
  • the one channel is designed in such a way that the incoming telegrams are all forwarded, irrespective of whether they are addressed to the fieldbus interface, and accordingly their contents can be further processed in the fieldbus interface
  • the other channel is designed in such a way that the incoming telegrams are forwarded only if they are addressed to the fieldbus interface Carrying out an active communication (for receiving the response telegrams to corresponding inquiries) is required.
  • this other channel can be turned off when the fieldbus interface is not actively communicating.
  • An “active” communication is understood to mean that a corresponding request can be actively made by the fieldbus interface
  • a request may, as explained below in relation to a further development, be made, for example, in the context of an acyclic communication through the fieldbus interface
  • Information listened to refers both to information exchanged between other communication participants via the fieldbus and to information whose telegrams are addressed to the fieldbus interface.
  • the monitored information is checked to see whether it concerns information that relates to the network management of the fieldbus, or otherwise, to be detected by the fieldbus interface information. Only when it is such information to be detected, they are detected in the fieldbus interface, in particular stored. If appropriate, the acquired information in the fieldbus interface is also further processed and provided in edited and / or summarized form to a higher-level communication unit. This is explained in particular below with reference to developments of the invention.
  • Information relating to network management at least includes information about which fieldbus addresses are connected to information technology devices. Compared to a purely mechanical connection, "information-technically connected" means that the device concerned answers at the relevant address to a corresponding request directed to this address Network management, including one or more of the following information:
  • the fieldbus interface can also provide documentation on the times or order so that the history of such changes can be tracked. This is particularly advantageous with regard to a subsequent error analysis.
  • the individual method steps of the method according to the invention as well as method steps of the further developments, insofar as this is technically expedient, are preferably carried out automatically by a suitably configured software and / or hardware of the fieldbus interface.
  • the fieldbus is designed in particular in accordance with the ProfibusO standard (see, for example, Profibus Profile Specification, Version 3.0) or according to the FoundationO Fieldbus standard (cf., for example, Foundation® Specification, Function Block Application Process, Revision FS 1.7).
  • the step of on-demand performance of an active communication comprises querying identification information for the driver and version management of at least one information technology connected to the fieldbus device, in particular field device, through the fieldbus interface.
  • the step of detecting comprises detecting requested identification information for the driver and version management by the fieldbus interface.
  • the fieldbus interface can provide further information about the individual devices, in particular field devices.
  • the requested identification information for the driver and version management of a field device comprises at least such information about the field device, which identifies the field device with regard to the device type, the manufacturer and the hardware and software version to the extent that it reveals which device integration information for that field device to be used.
  • the requested identification information can also have further identification information beyond this.
  • provision can be made, in particular, for the I & M parameters (l & M: Identification & Maintenancefunctions) defined in the ProfibusO standard to be completely or partially defined by the fieldbus interface as identification information (see Profibus® Profile Guidelines, Part 1, Identification & Maintenance Functions, Version 1.1, May 2003).
  • I & M parameters describe device-identifying parameters such as manufacturer code, serial number, order number, profile class, hardware and software version.
  • the format of the parameters as well as the communication services for reading these parameters is identical for all Profibus® devices.
  • I & M parameters facilitate access to device-specific online device information provided, for example, on a Vendor Asset Management System (Vendor) website.
  • Vendor Vendor Asset Management System
  • it can be checked on the basis of the identification information for the driver and version management, whether in the fieldbus interface and / or in a higher-level communication unit deposited information for device integration, such as a device description or a device driver, which are suitable for the actual information technology connected field device. This is particularly helpful after replacing a device to avoid compatibility issues.
  • the operating system eg a higher-level unit or an operator device
  • the operating program implemented thereon
  • the operating system must be made aware of the properties of this field device that are relevant in terms of operation.
  • device integration information of a field device (English name: means for device integration) are generally described the characteristics of the field device that are relevant for an operation of the same device information includes in particular the input and output signals supplied by the field device, Information regarding the communication of the field device via a fieldbus, parameters provided in the field device, status and diagnostic information supplied by the field device, data and rules for processing operations (eg configuration, calibration) and / or information about user dialogs, etc.
  • field devices from different manufacturers can be operated via the same operating program, standards have been created with regard to this device integration information.
  • Information about the device integration of a field device can be formed, for example, by a device description (DD) of the field device
  • the device description is usually created in text-based form (eg in ASCII text format) used according to fieldbus system different device description languages, such as the Foundation Fieldbus Device Description Language, GSD / Profibus (GSD: General Station Description), etc ..
  • the information provided in the device description are usually interpreted by an interpreter or translated and Such a frame application for the device description is formed for example by the operating program "Application Designer ⁇ " from Endress + Hauser.
  • information for device integration of a field device can also be formed by a device driver of the field device, in particular a "Device Type Manager” (DTM) Device-specific software that encapsulates data and functions of the field device and provides graphic controls.
  • DTM Device Type Manager
  • Such a device driver requires a corresponding frame application for execution, for example, a "Device Type Manager” requires an FDT frame application (FDT: Field Device Tool) for execution "from Endress + Hauser.
  • a parent communication unit in particular a PAM system, automatically accesses a database provided by a manufacturer (Vendor Asset Management System) in order to check through it let the device integration information used in each case be correct for the detected identification information for the driver and version management of the relevant field device. If necessary, if this is not the case, then the higher-level communication unit, in particular the PAM system, can automatically download the correct device integration information from the database. In this way, it is automatically ensured that in each case the correct information for device integration in the higher-level communication unit or possibly in the fieldbus interface are used.
  • a manufacturer Vendor Asset Management System
  • vendor asset management systems information about field devices is provided centrally in a database. Access to this is usually possible via corresponding portal pages with password-protected logins. There is the possibility that the plant operator accesses (or by an appropriate person or also automatically, for example by a PAM system) to the information provided by the manufacturer about the assets of his plant and / or updates this information.
  • current information about the field device such as, for example, information relating to calibration, maintenance and repair work, information regarding device integration to be used, procurement, installation, setup and operation, etc . are accessed.
  • a vendor asset management system is provided by Endress + Hauser through the "Web-enabled asset management system W @ M".
  • field device does not refer exclusively to sensors and / or actuators, but rather also refers to devices which are connected directly to the fieldbus and serve for communication with a higher-level unit (eg a PLC), such as Remote I / Os, Gateways, Linking Devices.
  • a higher-level unit eg a PLC
  • Remote I / Os Remote I / Os
  • Gateways Gateways
  • Linking Devices such as Remote I / Os, Gateways, Linking Devices.
  • the active communication of the fieldbus interface is formed by an acyclic communication.
  • a query of further information in particular in the case of a ProfibusO fieldbus, is made possible than is possible in the course of a cyclic communication.
  • acyclic communication may be performed as needed, so that when no information is needed, bus traffic will not be unnecessarily burdened.
  • a higher-level unit such as a PLC, which forms an MC1
  • the higher-level unit forms a master with respect to its associated field devices, which form slaves.
  • measured values are requested by the superordinate unit in accordance with predetermined rules by the individual sensors of the fieldbus allocated to it in a cycle, and control commands are output to the individual actuators assigned to them in dependence on the measured values obtained. If all field devices assigned to the higher-level unit have been processed, the cycle is ended.
  • the parent unit Upon completion of a cycle, the parent unit passes the token to an MC2, if one is attached to the fieldbus.
  • the token is consequently passed on to the fieldbus interface.
  • the fieldbus interface now has the possibility of communicating with individual field devices in the context of an acyclic communication, in particular of requesting information from them.
  • the fieldbus is designed in accordance with the FoundationO Fieldbus standard
  • one of the devices connected to it is usually designed as LAS (link active scheduler) in each fieldbus segment.
  • LAS also carries out tasks of network management, such as carrying out a regular polling of the fieldbus addresses, in order to check which devices are IT-connected under the various fieldbus addresses.
  • the LAS goes through the individual addresses of a fixed address range (devices are permanently connected under these addresses in terms of information technology) and gives the various function blocks of the field devices, according to its schedule, the possibility of carrying out a communication.
  • the LAS After performing this cyclic communication, the LAS gives devices, which temporarily register under an address of the temporary address range, the possibility to perform an (acyclic) communication. Accordingly, if the fieldbus interface wants to perform an acyclic communication, it must log in under an address of the temporary address range. After exchanging corresponding telegrams in which the fieldbus interface has sufficiently identified with respect to the LAS with regard to its properties, the fieldbus interface receives the token from the LAS and has the possibility of performing acyclic communication.
  • the step of detecting comprises the acquisition of further associated information by the fieldbus interface.
  • further information can be provided to a higher-level communication unit by the fieldbus interface.
  • the further information that has been listened to and recorded has at least one of the following information:
  • diagnostic information transmitted in the course of a cyclic communication can be of various types.
  • DATA EXCHANGE cyclic data exchange
  • the beginning of a diagnostic event is indicated by the fact that the field device sends back a response telegram (DATA_EXCH.res) with high priority to a request telegram (DATA_EXCH.req) of the MC1.
  • DATA_EXCH.res response telegram
  • DATA_EXCH.req request telegram
  • the MC1 Upon receipt of a high priority telegram, the MC1 sends a diagnostic request telegram (SLAVE_DIAG.req) to the field device. In response, the field device sends diagnostic information in a diagnostic response telegram (SLAVE_DIAG.res). Subsequently, the cyclic data exchange is continued. If the diagnostic event ends in the field device or if a change in the diagnostic data occurs, the field device in turn sends back a response telegram (DATA_EXCH.res) with high priority to a request telegram (DATA_EXCH.req) of the MC1. Subsequently, the MC1 again inquires of the field device diagnostic information by sending a diagnostic request telegram (SLAVE_DIAG.req).
  • diagnostic information and alarm messages are understood. Furthermore, in the case of a fieldbus in accordance with the ProfibusO standard and in accordance with the FoundationO Fieldbus standard, its status is transmitted together with a measured value. The status is formed by a basic quality, a quality substatus and information about the violation of limit values. Diagnostic information also refers to this status.
  • the "communication state” refers to the possible states of the ProfibusO state machine
  • DATA EXCHANGE short: DXCHG
  • the slave must receive and respond to a sequence of telegrams from the MC1 after switching on (Power_ON) or after a reset of the same
  • the status information relating to the communication state indicates in particular in which communication state the relevant field device is.
  • the respective information is preferably not only content, but at least partially also the times of the respective changes detected.
  • the fieldbus interface or, if appropriate, a higher-level communication nikationshim, such as a PAM system the timing of the changes (history) documented and / or trends are created.
  • the step of the demand-dependent execution of an active communication has the interrogation of diagnostic information from at least one information field connected to the fieldbus field device by the fieldbus interface and the step of detecting comprises the detection of queried diagnostic information through the fieldbus interface.
  • this interrogation can take place in particular in the context of acyclic communication, so that more extensive diagnostic information than can be obtained in the context of cyclic communication can be queried.
  • Such further diagnostic information can relate, for example, to a degree of wear of a probe, a buildup of a sensor, a number of operating hours, etc.
  • MC2 In the ProfibusO standard for Profibus® PA devices, further diagnostic information is specified which can be interrogated by an MC2.
  • manufacturer-specific diagnostic information can also be provided in a field device and made known to the respective MC2 by the associated information for device integration of the field device. According to the present invention, the fieldbus interface performs active communication only as needed.
  • Such "demand-dependent" execution can be initiated by the fieldbus interface itself, by a higher-level communication unit (eg a PAM system) which is in communication connection with the fieldbus interface, and / or by a user
  • a higher-level communication unit eg a PAM system
  • PAM system e.g. a PAM system
  • a user Dependent on the existence of certain conditions, such as that in the context of process control certain information (eg a telegram with high priority, a certain, transmitted value, an alarm or error message, a diagnostic request, etc.) is transmitted via the fieldbus and / or in that a rule or algorithm specifies a schedule for the execution of certain active communications.
  • the step of the demand-dependent performing an active communication by the fieldbus interface in response to listened information that is transmitted in the context of a cyclic communication via the fieldbus, initiated. Additionally or alternatively, it is provided according to an advantageous development that the step of performing an active communication through the fieldbus interface as required is initiated by a higher-order communication unit (for example a PAM system) which is in communication connection with the fieldbus interface.
  • a higher-order communication unit for example a PAM system
  • the fieldbus interface generates and updates a list based on acquired information relating to the network management of the fieldbus from on the fieldbus information technology connected devices.
  • a list or table which is also referred to as "LiveList”
  • information relating to the network management of the fieldbus can be clearly summarized, updated and, if necessary, collected, transmitted to a higher-level communication unit.
  • the fieldbus interface further collects information about the fieldbus information technology connected devices in the list and updates them.
  • an extended list or table which is also referred to as "extended live list”
  • Such further acquired information can in particular be identification information of the field devices for the driver and version management, diagnostic information of the respective field devices, the affiliation of the field devices a master and / or status information relating to the communication state, etc.
  • the bus status of the fieldbus is monitored by the fieldbus interface.
  • the information collected for this purpose can also be evaluated and / or trends created. This evaluation and generation of bus status trends can be performed by the fieldbus interface itself or even partially or completely by a higher level communication unit (e.g., a PAM system) in communication with the fieldbus interface.
  • a higher level communication unit e.g., a PAM system
  • the fieldbus interface can, in particular, show changes in the signal quality on the fieldbus, as evidenced, for example, by the increase in telegram repetitions, effects due to changing cable properties, for example due to aging of isolations, and / or changes of Cable laying, etc. are detected.
  • the fieldbus interface transmits on its own initiative or on request from a higher-level communication unit (eg a PAM system), which is in communication connection with the fieldbus interface, information acquired and possibly further processed and / or stored in the fieldbus interface the higher-level communication unit.
  • a higher-level communication unit eg a PAM system
  • the information in a higher-level communication unit can be utilized without this higher-level communication unit having to be connected to the fieldbus.
  • information from a plurality of fieldbus segments can be utilized in the higher-level communication unit.
  • the acquired information is already further processed in the fieldbus interface in a suitable manner and / or several pieces of information are combined (or collected). In this further processed and / or summarized form, they can then be transmitted to the higher-level communication unit.
  • the parent community receives already higher-quality information and the data traffic between the higher-level communication unit and the fieldbus interface can be reduced.
  • the list described above can be transmitted or combined diagnostic information can be transmitted to a plurality of field advisers of the fieldbus segment.
  • the collected transmission can take place in particular with the aid of a CommDTM (communication DTM) of the fieldbus interface.
  • a CommDTM communication DTM
  • Such a CommDTM is implemented in the respective higher-level communication unit and is responsible for the communication services with the fieldbus interface.
  • a CommDTM query the list described above or other further processed and / or summarized information directly from a corresponding memory (in particular from a buffer) of the fieldbus interface.
  • the CommDTM can already provide such a current list and provide it to a corresponding frame application of the higher-level communication unit as required.
  • the fieldbus interface transmits at least at
  • the fieldbus interface can inform the higher-level communication unit depending on the situation (for example when a change occurs and / or when a limit value is exceeded).
  • the higher-level communication unit is currently informed about important events, without this unnecessarily increasing the traffic on the communication connection.
  • a predetermined rule which is preferably stored in the fieldbus interface, it can be determined, for example, that the fieldbus interface at predetermined time intervals (ie regularly) and / or situation-dependent (eg when a change occurs and / or when exceeding a limit) performs a transmission to the higher-level communication unit.
  • the fieldbus interface has information for integrating the device with at least one field device connected in terms of information technology on the fieldbus, in particular a device description and / or a device driver of such a field device.
  • a further evaluation of the monitored information can already be carried out by the fieldbus interface.
  • the fieldbus interface itself more targeted and, taking into account the specific properties of each field device queries that are made in the context of active communication to the respective field device to generate.
  • the fieldbus interface can already further process associated information or prepare and transmit in this further processed form to the higher-level communication unit.
  • information for integrating the device with at least one field device connected by information technology to the fieldbus can also be provided in a higher-level communication unit, such as in a PAM system.
  • a higher-level communication unit such as in a PAM system.
  • the provision of device integration information only in the higher-level communication unit can then make sense if the fieldbus interface is not designed sufficiently for such comprehensive storage and data processing.
  • essential processing steps may be performed in the fieldbus interface that would otherwise be corrupted by the parent communication unit (eg PAM system) would have to be performed.
  • the fieldbus interface carries out at least one of the following steps using the information for device integration of a field device:
  • the method has the following steps:
  • the steps of comparing and determining can be carried out in particular by the fieldbus interface, provided that it has information for device integration. Additionally or alternatively, these steps can also be performed by a higher-level communication unit which is in communication connection with the fieldbus interface, such as a PAM system. In this case, the higher-level communication unit in particular Verify that the device integration information used by itself or another device, including (in relation to the network structure), such as the fieldbus interface, is correct. Furthermore, as explained above, a vendor asset management system can also be used to carry out these steps.
  • the higher-level communication unit is formed by a Plant Asset Management System (German: Asset Asset Management System), which communicates in particular via a higher-level network with the fieldbus interface in communication.
  • the present invention further relates to a fieldbus interface for connection to a fieldbus process automation technology, wherein the fieldbus interface is designed such that during operation of this, the data traffic on the field bus is listened to by this parallel to this interception function active communication is feasible and by this listened information concerning the network management of the fieldbus, are detected.
  • FIG. 1 shows a schematic representation of a fieldbus segment, which is connected via a fieldbus interface to a superordinate network, for explaining an embodiment of the invention
  • FIG. 2 shows an exemplary representation of an extended LiveList.
  • a field bus segment is shown schematically, in which four field devices FGO, FG1, FG2 and FG3 and a higher-level unit MC1 are connected to a fieldbus F.
  • Fieldbus F operates according to the ProfibusO standard.
  • the higher-level unit MC1 which in the present case is formed by a PLC, is configured as a master class 1 (MC1), while the field units FGO, FG1, FG2 and FG3 are slaves in each case.
  • the higher-level unit MC1 is connected to a computer 2, which serves as a visualization system (for example for displaying process parameters, etc.).
  • the communication between the higher-level unit PLC and the field devices FGO, FG1, FG2 and FG3 takes place in accordance with the ProfibusO standard.
  • the higher-level unit carries out a process control with respect to the field devices FGO, FG1, FG2 and FG3, as has been explained above by way of example in the general description part.
  • a field bus interface Fl is also connected, which establishes a connection to a higher-level network LAN.
  • the higher-level network LAN for example, a local corporate network, which is designed as Ethernet LAN.
  • the higher-level network LAN can also be connected to the worldwide Internet.
  • a PAM system 4 which forms a higher-level communication unit with respect to the network structure and relative to the fieldbus interface Fl, is connected.
  • Both the fieldbus F and the higher-level network LAN can also be connected to other devices and / or networks.
  • the fieldbus interface Fl continuously monitors the data traffic on the fieldbus F during operation. If necessary, it also performs active communication in parallel with eavesdropping on the traffic. Furthermore, it captures information that belongs to the network management of the fieldbus F.
  • the fieldbus interface Fl is configured as a class 2 master (MC2) in the illustrated embodiment.
  • the implementation of an active communication through the fieldbus interface Fl takes place in the context of an acyclic communication.
  • identification information for the driver and version management is interrogated and at least partially acquired by the field devices FGO, FG1, FG2 and FG3 connected to the fieldbus F in terms of information technology.
  • the fieldbus interface F1 can also be used to query further information and / or to collect further information that has been listened to.
  • the fieldbus interface Fl further performs a protocol conversion between the protocol of the parent network LAN and the ProfibusO protocol of the fieldbus F.
  • the fieldbus interface F1 performs further processing of the acquired information using the information for device integration and selectively generates further queries in response to the acquired information, which it makes in an acyclic communication to the individual field devices FGO, FG1, FG2 and FG3.
  • the fieldbus interface Fl generates and updates on the basis of acquired information relating to the network management of the fieldbus F, and on the basis of further acquired information, an extended LiveList to the field devices FGO, FG1, FG2, FG3 connected to the fieldbus F in information technology.
  • the extended LiveList transmits the fieldbus interface F1 on request from the PAM system 4 or, if a change in the information recorded in the LiveList occurs, to the PAM system 4 via the remote system. arranged network LAN.
  • the fieldbus interface F1 also transmits further information to the PAM system 4. Such a transmission can take place not only when a change of detected information occurs, but also when a predetermined limit value is exceeded and / or according to a predetermined rule (or algorithm) stored in the fieldbus interface F1.
  • the interrogations which are made as part of an active communication through the fieldbus interface Fl to one or more, connected to the field F field devices FGO, FG1, FG2 and FG3, inter alia, depending on mitxx information, possibly using Information about device integration of the relevant field device, created and provided.
  • certain queries are also regularly created and submitted according to a predetermined algorithm.
  • such queries can also be initiated by the PAM system 4, which makes a corresponding request to the fieldbus interface Fl.
  • the field bus interface F1 by a user or by the PAM system 4 can be set under what conditions a transmission of what information to the PAM system 4 (or to a other, higher-level communication unit) should take place.
  • the fieldbus interface Fl can be adjusted by a user or by the PAM system 4 (or by another, higher-level communication unit), under which conditions which queries are created and made by the fieldbus interface Fl.
  • the relevant fieldbus is in turn formed by a field bus according to the ProfibusO standard, to which the fieldbus interface according to the invention is connected and in which the process control of two higher-level units, each of which form a class 1 master (MC1), is executed.
  • the fieldbus interface in turn forms a master class 2 (MC2).
  • the higher-level unit MC1 of address # 1 regularly polls the fieldbus addresses to check which devices are IT-connected among the various fieldbus addresses.
  • the corresponding queries are referred to in the table as "FDL-ANFR.”
  • FDL-ANFR Fieldbus Data Link
  • the second column which is overwritten with "ANSWER”, shows under which fieldbus Addresses devices to respond to the appropriate request (in the second column by "FDL-ANFR.
  • the information given in the second column can only capture the fieldbus interface by listening to the data traffic on the fieldbus, as can be seen from the second column of the table, at addresses # 2 , # 3, # 4, # 5 and # 6 are each connected to the information technology devices, devices used to be IT-connected at addresses # 7 and # 8.
  • MC1 # 1 to a diagnostic request (indicated in the table as "DIAG-REFR.")
  • MC1 # 1 To both addresses # 7 and # 8.
  • the MC1 # 1 also did not receive any response to these diagnostic requests, which is indicated in the table by "DIAG-ANFR.
  • the fieldbus interface also contains identification information for the driver and version management of the individual devices connected in terms of information technology at the various fieldbus addresses
  • identification information is, for example, the manufacturer of the field devices (HERST.)
  • DEVICE TYPE respective device type
  • further identification information for the driver and version management, in particular further I & M parameters can be queried by the fieldbus interface and recorded in the table. There is no information for the addresses # 7 and # 8, which is indicated in the table by a "?" This also applies to the other, subsequent columns of the table.
  • the field devices with the addresses # 2, # 3 and # 6 are assigned to the MC1 # 1, while the field device with the address # 5 is assigned to the MC1 # 1 MC1 # 4 (MC1 is assigned the address # 4)
  • the fifth column with the heading "COMM. COND.” Indicates the respective communication status of the individual field devices. As can be seen from the information on the individual field devices, the field devices with the addresses # 3, # 5 and # 6 are each in the communication state "DATA EXCHANGE.” Accordingly, the respective MC1 performs normal process control with these field devices Only the field device with the address # 2 could not go into the "DATA EXCHANGE" state because an error has occurred during the communication state of the configuration.
  • the information given in the fourth and fifth column can capture the fieldbus interface only by listening to the data traffic on the fieldbus.
  • diagnostic information for the field devices connected to the fieldbus in each case are specified (ie the field devices of the addresses # 2, # 3, # 5 and # 6).
  • the sixth column entitled “DP SLAVE DIAGNOSIS” contains diagnostic information that is standardized for at least one DP slave No diagnostic event has occurred in the field devices of the addresses # 2, # 5 and # 6.
  • these field devices in the context of the cyclic data exchange with the respective MC1 each transmit low-priority messages, so that the respective MC1 is not ready for transmission of a diagnostic request telegram (SLAVE_DIAG.req), which is indicated by "NO DIAG” in the sixth column.
  • a diagnostic event has occurred with the field device of address # 3, which means that this field device returned a high-priority response telegram to the associated MC1 in the course of the cyclic data exchange.
  • This caused MC1 here: MC1 # 1 to send a diagnostic request telegram (SLAVE_DIAG.req) to the field device of address # 3.
  • the field device of address # 3 sent an alarm message to MC1 # 1. This is indicated in the sixth column by "DIAG / ALARM.”
  • the information given in the sixth column can only capture the fieldbus interface by listening to the traffic on the fieldbus.
  • the seventh column entitled “PA SLAVE DIAGNOSIS” shows that further standardized diagnostic information is available through the fieldbus interface for a PA slave As can be seen from the seventh column, this is OK with the field devices of addresses # 2 and # 6, which is indicated by "OK".
  • the basic quality of the field devices of the addresses # 3 and # 5 is poor, which is indicated by "BAD.”
  • the fieldbus interface is designed such that, in the case of poor basic quality, active diagnostic (acyclic) communication requests further diagnostic information
  • the further diagnostic information can in particular be diagnostic information that is standardized for PA slaves, but may alternatively or additionally be manufacturer-specific additional diagnostic information specified for the relevant field device Interface device-specific knowledge, which can be obtained, for example, by the fact that the fieldbus interface has information for device integration.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • General Engineering & Computer Science (AREA)
  • Manufacturing & Machinery (AREA)
  • Quality & Reliability (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Automation & Control Theory (AREA)
  • Testing And Monitoring For Control Systems (AREA)
  • Small-Scale Networks (AREA)

Abstract

L'invention concerne un procédé pour faire fonctionner une interface de bus de terrain (FI) reliée à un bus de terrain (F) d'automatisation des procédés. Le procédé comporte les opérations suivantes: écoute continue du trafic de données sur le bus de terrain (F) par l'interface de bus de terrain (FI); en fonction des besoins, établissement d'une communication active par l'interface de bus de terrain (FI), parallèlement à l'écoute du trafic de données; détection par l'interface de bus de terrain (FI) d'informations entendues concernant la gestion du réseau du bus de terrain (F).
EP10751607A 2009-10-06 2010-08-30 Procédé pour faire fonctionner une interface de bus de terrain Ceased EP2486464A2 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
DE102009045386A DE102009045386A1 (de) 2009-10-06 2009-10-06 Verfahren zum Betreiben eines Feldbus-Interface
PCT/EP2010/062611 WO2011042257A2 (fr) 2009-10-06 2010-08-30 Procédé pour faire fonctionner une interface de bus de terrain

Publications (1)

Publication Number Publication Date
EP2486464A2 true EP2486464A2 (fr) 2012-08-15

Family

ID=43662209

Family Applications (1)

Application Number Title Priority Date Filing Date
EP10751607A Ceased EP2486464A2 (fr) 2009-10-06 2010-08-30 Procédé pour faire fonctionner une interface de bus de terrain

Country Status (4)

Country Link
US (1) US20120246376A1 (fr)
EP (1) EP2486464A2 (fr)
DE (1) DE102009045386A1 (fr)
WO (1) WO2011042257A2 (fr)

Families Citing this family (27)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE102009046041A1 (de) 2009-10-27 2011-05-12 Endress + Hauser Process Solutions Ag Anordnung zur Bedienung von Feldgeräten in der Automatisierungstechnik mittels eines Konfigurier-/Managementsystems
DE102010029952B4 (de) 2010-06-10 2019-06-27 Endress + Hauser Process Solutions Ag Verfahren zum Integrieren von zumindest einem Feldgerät in ein Netzwerk der Automatisierungstechnik
DE102010042716A1 (de) 2010-10-20 2012-04-26 Endress + Hauser Process Solutions Ag System und Verfahren zum Betreiben einer Automatisierungsanlage
DE102011005062A1 (de) 2011-03-03 2012-09-06 Endress + Hauser Process Solutions Ag Verfahren zum Bereitstellen von Daten eines Feldgeräts
US20120310373A1 (en) * 2011-05-31 2012-12-06 General Electric Company Systems and methods for alert capture and transmission
US8994545B2 (en) * 2011-05-31 2015-03-31 General Electric Company Systems and methods for alert device removal
EP2538287A1 (fr) * 2011-06-22 2012-12-26 Siemens Aktiengesellschaft Etablissement automatique d'outils d'un dispositif automatisé
DE102011107323A1 (de) 2011-07-06 2013-01-10 Abb Ag Verfahren zur Übertragung eines Prozessabbildes über ein Gateway-Gerät
CN103104529A (zh) * 2011-11-15 2013-05-15 上海北玻玻璃技术工业有限公司 一种分子泵的总线控制装置和方法
CN103267023B (zh) * 2013-04-24 2016-12-28 深圳市生波尔机电设备有限公司 基于文本语言的真空分子泵控制方法及装置
DE102013107905A1 (de) * 2013-07-24 2015-01-29 Endress + Hauser Process Solutions Ag Feldbuszugriffseinheit und Verfahren zum Betreiben derselben
DE102014111350A1 (de) * 2014-08-08 2016-02-11 Endress + Hauser Gmbh + Co. Kg Automatisierte Erstellung von geeigneten Vorzugsmenüs für Feldgeräte
EP2996004B1 (fr) * 2014-09-09 2020-04-08 Siemens Aktiengesellschaft Procédé de mise à disposition d'informations concernant des noms de réseaux de communication au sein d'un système d'automatisation industriel et routeur
SG10201408352XA (en) * 2014-12-15 2016-07-28 Iia Technologies Pte Ltd A system of monitoring and controlling the operation of multiple machines for producing diamonds and a method thereof
CN105808407B (zh) * 2014-12-31 2019-09-13 华为技术有限公司 管理设备的方法、设备和设备管理控制器
CN104635608B (zh) * 2015-01-09 2017-07-04 攀钢集团攀枝花钢铁研究院有限公司 轧制设定信息传输滞后的检测方法
DE102015121947A1 (de) * 2015-12-16 2017-06-22 Endress+Hauser Process Solutions Ag Verfahren zum Überprüfen von Daten in einer Datenbank eines PAMs
DE102016124326A1 (de) 2016-12-14 2018-06-14 Endress+Hauser Conducta Gmbh+Co. Kg Verfahren zum Betreiben eines Messumformers und entsprechender Messumformer
EP3355139B1 (fr) * 2017-01-26 2020-11-04 Siemens Aktiengesellschaft Procédé de fonctionnement d'un système d'automatisation, système d'automatisation, appareil de terrain et contrôleur destinés à exécuter ledit procédé
CN107069961B (zh) * 2017-04-12 2019-04-26 国网福建省电力有限公司 一种变电站远动装置与调控主站遥信自动闭环联调的方法
AT520270B1 (de) 2017-07-28 2021-01-15 Wittmann Kunststoffgeraete Verfahren zum Verwalten und Steuern von Produktionsmitteln mit einer oder
TWI658712B (zh) * 2017-09-13 2019-05-01 財團法人資訊工業策進會 閘道器與在閘道器上判斷欲聯網機器的方法
DE102018123436A1 (de) 2018-09-24 2020-03-26 Endress+Hauser Conducta Gmbh+Co. Kg Verfahren zum Überwachen einer Anlage der Automatisierungstechnik
EP3722899B1 (fr) * 2019-04-11 2022-12-07 ETM professional control GmbH Procédé et dispositif de commande d'un appareil technique
DE102019217769A1 (de) * 2019-11-19 2021-05-20 Siemens Schweiz Ag Fernaktivierung der Wireless-Service-Schnittstelle eines Steuergerätes über ein Bussystem
EP4210283A1 (fr) * 2022-01-05 2023-07-12 Turck Holding GmbH Système de commande et/ou de surveillance pour les applications ethernet industrielles et procédé correspondant de commande et de surveillance d'un dispositif ethernet industriel
CN114884857B (zh) * 2022-07-13 2022-10-25 中车工业研究院(青岛)有限公司 一种信号质量的检测方法、装置及计算机可读存储介质

Family Cites Families (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5796721A (en) * 1996-06-21 1998-08-18 National Instruments Corporation Method and system for monitoring fieldbus network with dynamically alterable packet filter
US6076952A (en) * 1997-09-17 2000-06-20 National Instruments, Corp. Fieldbus network configuration utility with improved parameter control
AU2003250959A1 (en) * 2002-07-18 2004-02-09 Vega Grieshaber Kg Bus station with an integrated bus monitor function
DE10358270B4 (de) * 2003-12-11 2012-02-09 Endress + Hauser Process Solutions Ag Verfahren zur Inbetriebnahme eines Feldgerätes der Prozessautomatisierungstechnik
WO2006026749A2 (fr) * 2004-08-31 2006-03-09 Watlow Electric Manufacturing Company Systeme diagnostique de systeme d'exploitation reparti
DE102005023938B4 (de) * 2005-05-20 2009-01-15 Abb Ag Integration von Feldgeräten in ein Automatisierungssystem
DE102005063053A1 (de) 2005-12-29 2007-07-05 Endress + Hauser Process Solutions Ag Verfahren zur Anlagenüberwachung mit einem Feldbus der Prozessautomatisierungstechnik
DE102006051444C5 (de) * 2006-10-31 2011-12-08 Softing Ag Diagnoseverfahren und -vorrichtung für ein Feldbussystem
DE102007043328A1 (de) * 2007-09-12 2009-03-19 Endress + Hauser Process Solutions Ag Verfahren zur Überwachung einer Prozessanlage mit einem Feldbus der Prozessautomatisierungstechnik
DE102008019053B4 (de) * 2008-04-15 2016-01-07 Endress + Hauser Process Solutions Ag Verfahren zum Betreiben einer Anlage der Prozessautomatisierungstechnik
DE102009041781A1 (de) * 2009-09-15 2011-03-17 Siemens Aktiengesellschaft Bereitstellung anlagenbezogener Betriebsdaten unter Verwendung eines Diagnose-Datenservers als weiteren Feldbusmaster

Non-Patent Citations (1)

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

Also Published As

Publication number Publication date
WO2011042257A2 (fr) 2011-04-14
US20120246376A1 (en) 2012-09-27
DE102009045386A1 (de) 2011-04-07
WO2011042257A3 (fr) 2011-06-03

Similar Documents

Publication Publication Date Title
WO2011042257A2 (fr) Procédé pour faire fonctionner une interface de bus de terrain
DE102008019053B4 (de) Verfahren zum Betreiben einer Anlage der Prozessautomatisierungstechnik
DE102005063053A1 (de) Verfahren zur Anlagenüberwachung mit einem Feldbus der Prozessautomatisierungstechnik
DE102009046806A1 (de) Verfahren zum Bereitstellen von gerätespezifischen Informationen eines Feldgeräts der Automatisierungstechnik
EP2625869A1 (fr) Procédé permettant de diagnostiquer rapidement un appareil de terrain raccordé à un adaptateur sans fil
DE102007059671A1 (de) Verfahren zum Betreiben eines Systems aufweisend ein Feldgerät und ein Bediensystem
DE102012107673A1 (de) Verfahren zum Feldgerätetausch mit Hilfe eines mobilen Endgerätes
DE102017109030A1 (de) Verfahren zum Betreiben eines Feldgeräts
DE102009046041A1 (de) Anordnung zur Bedienung von Feldgeräten in der Automatisierungstechnik mittels eines Konfigurier-/Managementsystems
WO2012079946A1 (fr) Procédé pour intégrer au moins un appareil de terrain dans un réseau de la technique d'automatisation
DE102008038501A1 (de) Verfahren zum Bestimmen einer statischen Datenstruktur eines Feldgerätes
WO2012065807A1 (fr) Procédé de préparation d'un message de diagnostic général pour tous les types d'appareil de terrain
EP3652595B1 (fr) Procédé et système pour surveiller une installation de la technologie d'automatisation
EP2486459B1 (fr) Interface de bus de terrain et procédé de fonctionnement correspondant
EP3391158A1 (fr) Procédé de production d'un modèle de diagnostic générique
DE102010027963A1 (de) Verfahren zum Betreiben eines Feldgerätes der Prozessautomatisierungstechnik
WO2012028366A1 (fr) Procédé garantissant le mode de fonctionnement correct d'une installation d'automatisation
DE102008042919A1 (de) Feldgerät der Prozessautomatisierungstechnik
DE102010042199A1 (de) Verfahren zum Betreiben eines Feldbus-Interface sowie Computerprogrammprodukt
DE102008043683A1 (de) Feldgerät der Prozessautomatisierungstechnik
DE102009027168B4 (de) Verfahren zum Ermitteln einer übermittelten Telegramm-Datenlänge
DE102007035159A1 (de) Verfahren zum Parametrieren von mehreren Feldgeräten der Automatisierungstechnik
DE102016122051A1 (de) Verfahren und System zum Ermitteln von Diagnoseinformationen von zumindest einem Feldgerät der Prozessautomatisierung
EP1454201B1 (fr) Systeme d'ingenierie et systeme d'automatisation
WO2016102194A1 (fr) Dispositif et procédé de fonctionnement d'un appareil de terrain pourvu d'un serveur web

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

AK Designated contracting states

Kind code of ref document: A2

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

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

Effective date: 20140324

APBK Appeal reference recorded

Free format text: ORIGINAL CODE: EPIDOSNREFNE

APBN Date of receipt of notice of appeal recorded

Free format text: ORIGINAL CODE: EPIDOSNNOA2E

APBR Date of receipt of statement of grounds of appeal recorded

Free format text: ORIGINAL CODE: EPIDOSNNOA3E

APAF Appeal reference modified

Free format text: ORIGINAL CODE: EPIDOSCREFNE

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

Owner name: ENDRESS+HAUSER PROCESS SOLUTIONS AG

REG Reference to a national code

Ref country code: DE

Ref legal event code: R003

APBT Appeal procedure closed

Free format text: ORIGINAL CODE: EPIDOSNNOA9E

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