[go: up one dir, main page]

WO2003036401A2 - Procede de detection de plusieurs appareils de champ dans une configuration d'appareils - Google Patents

Procede de detection de plusieurs appareils de champ dans une configuration d'appareils Download PDF

Info

Publication number
WO2003036401A2
WO2003036401A2 PCT/DE2002/003850 DE0203850W WO03036401A2 WO 2003036401 A2 WO2003036401 A2 WO 2003036401A2 DE 0203850 W DE0203850 W DE 0203850W WO 03036401 A2 WO03036401 A2 WO 03036401A2
Authority
WO
WIPO (PCT)
Prior art keywords
address
field devices
fgn
electronic
http
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/DE2002/003850
Other languages
German (de)
English (en)
Other versions
WO2003036401A3 (fr
Inventor
Andreas Jurisch
Stefan Walz
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
Publication of WO2003036401A2 publication Critical patent/WO2003036401A2/fr
Publication of WO2003036401A3 publication Critical patent/WO2003036401A3/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—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
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
    • Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
    • Y02P90/02—Total factory control, e.g. smart factories, flexible manufacturing systems [FMS] or integrated manufacturing systems [IMS]

Definitions

  • the invention lies in the field of remote-controlled operation of field devices, in particular for the purpose of observing and operating field devices.
  • Field devices are used in the automation of a wide variety of technical processes, for example for monitoring a production or manufacturing process or a processing process.
  • the field devices can be the production plants themselves or devices for monitoring, preferably for controlling and / or regulating, depending on the recorded field data, the technical means of production or plants used.
  • the field devices are often arranged in star coupler configurations in which transmission protocols based on a master-slave architecture are used.
  • the field devices that are connected as slave devices to a master device must be recognized so that the field devices can be controlled electronically by the master device via a respective address.
  • transmission protocols based on the master-slave architecture are used. Address collisions are prevented with these protocols.
  • the master or master device In accordance with the mode of operation of a master-slave protocol, the master or master device generates a request for a specific one of the slave devices. Only the specific slave device responds to the request. All other slave devices connected to the master device remain silent. As a rule at the star coupler In this way, only one master device is connected so that a serial transmission channel between the star coupler and the slave devices is only ever occupied by one of the slave devices. Additional circuit components for arbitrating the connection are not required.
  • the master device In order to enable the master device to address all slave devices to be managed by the master device, the master device needs a list of the connected slave devices. The master device must therefore be aware of all connected slave devices. The slave devices can only be addressed via their address if this requirement is met. Since the parameterization of the telecontrol or station control system master is time-consuming and complex, these activities result in considerable expenditure of time and costs.
  • the object of the invention is to provide an improved method for recognizing connected field devices, which also enables time and cost-effective work in connection with a large number of address query options.
  • An essential idea of the invention consists in sub-areas of an overall address area with a single request to query for the presence of field devices in the respective sub-area. It is not necessary to address the field devices with their respective addresses. Several field devices can also respond to an inquiry. This is consciously accepted. With the successive, targeted reduction of the queried sub-areas, the addresses of the connected field devices are then automatically recognized in the further course of the method.
  • the respective electronic address of the field devices is a binary address, so that half of the address query area and the remaining half of the address query area are formed by setting a measurement bit to a value of 0 or 1 be, whereby the division of the total address range is possible in a simple manner and with little expenditure of time.
  • the measurement bit and a bit mask are respectively transmitted to the field devices during electronic interrogation, the bit mask comprising bits that are not evaluated by the field devices, i.e. go unnoticed.
  • bit mask is always shortened by one bit when the electronic query is repeated n times in successive repetitions. Repeating n times is terminated when the bit mask no longer contains bits, i.e. the electronic query includes the exact address of the addressed field device.
  • An expedient development of the invention provides that the recorded electronic responses or the other electronic responses in the central device are processed electronically by means of an OR gate, as a result of which it can be recognized with little circuit complexity whether field devices are present in a query address area.
  • electronic and / or other electronic responses that collide in time are recorded such that they are received by the central device essentially simultaneously. A detection of the temporal collision of responses from the field devices is therefore not necessary, as a result of which the circuitry complexity can be kept as low as possible. It is sufficient to recognize whether there was an answer at all.
  • the method and / or the device can advantageously be used for monitoring energy technology systems.
  • Figure 1 is a schematic representation with a device network and a company intranet, which are connected via a proxy server;
  • FIG. 2 shows a user interface design of a browser device with graphic representations for several field devices
  • Figure 3 shows another surface design of the browser device with a graphical representation of a
  • Figure 4 is a schematic representation of a field device and a user personal computer
  • FIG. 5 shows a flow chart for downloading HTML pages as part of an observation and operating system
  • Figure 6 is a block diagram for explaining an RPC call
  • FIG. 7 shows the arrangement with the device network and the company intranet according to FIG. 1, individual elements of the proxy server being shown schematically;
  • Figure 8 is a schematic block diagram of the proxy server
  • FIG. 9 shows a schematic illustration to explain a client / server interaction
  • FIG. 10 shows a schematic illustration to explain device detection in a master / slave arrangement
  • FIG. 11 shows a Nassi-Sneider diagram
  • FIG. 12 shows a schematic tree representation of a method for device recognition
  • FIG. 13 shows a schematic illustration of a master / slave arrangement to explain a configuration query
  • FIG. 14 shows a schematic block diagram of a device management in the proxy server
  • FIG. 15 shows a schematic block diagram to explain the functional integration of an XSL parser in the proxy server (XSL - “Extended Stylesheet Language”);
  • FIG. 16 shows a schematic block diagram to explain an XSLT processor (XSLT - "Extended Stylesheet Language Transformations").
  • a monitoring and operating system (BuB system) that can be used in conjunction with field devices is described below.
  • FIG. 1 shows a schematic architecture of two networks, a device network with several field devices FG1 ... FGN and a company intranet with several user devices N1 ... NN, preferably a personal computer (PC).
  • the device network and the company intranet are connected via a proxy server 1.
  • the proxy server 1 is part of the observation and operating system and serves as a gateway between the device network and the company intranet.
  • information for example measurement and / or status data, is collected by the field devices FG1 ... FGN and transmitted to the user devices N1 ... NN in order to inform a user of the user devices N1 ... NN about the
  • the BuB system is used to record operating or control inputs of the user with the help of the user devices N1 ... NN and for converting the inputs of the user into the field devices FG1 ... FGN.
  • the field devices FG1 ... FGN can be any devices for observing, measuring, controlling and / or regulating a wide variety of physical quantities in different technical processes, for example for monitoring and / or controlling energy technology systems, for example a substation.
  • the device network comprises individual PPP connections 2 (PPP - “Point to Point Protocool”), which can be connected to the proxy server 1 via a star coupler 3, or a separate Ethernet segment.
  • PPP Point to Point Protocool
  • the proxy server 1 provides its own homepage Form of HTML data (HTML - "HyperText Markup Language") is available, which shows an overview of the field devices FG1 ... FGN that can be reached in the device network (cf. FIG. 2); the homepage can be displayed in the user devices N1 ... NN using a standard browser.
  • the field devices FG1 ... FGN are only equipped with the star coupler 3 and a modem 4 connected to it.
  • the field devices FG1 ... FGN are connected to the modem 4 via an asynchronous serial interface directly via the star coupler 3.
  • An IP protocol IP - "Internet Protocol"
  • PPP link layer is used as the protocol for access to the field devices FG1 ... FGN.
  • the Ethernet connections are connected to a switch or a hub. If this switch or hub has a PPP port in addition to Ethernet ports, then this is called a router. This PPP port can then also be connected directly to the modem 4.
  • the user devices N1 ... NN connected to the local network have access to a modem 5 which can be connected to the modem 4 of the device network via a telecommunications network 6, for example a telephone network based on an ISDN or a mobile radio network is. If a dial-up connection (remote data transmission) is set up in the user devices N1 ... NN, the user devices N1 ... NN can each access the field devices FG1 ...
  • Proxy server 1 If the proxy server 1 is now addressed by the user devices N1 ... NN, the field devices FG1 ... FGN can be accessed by each of the user devices N1 ... NN connected to the company intranet for observation and operation. Proxy server 1 "mirrors" all field devices FG1 ... FGN, ie information about field devices FG1 ... FGN, into the company intranet. Proxy server 1 processes the following protocols: HTTP protocol (HTTP - "Hypertext Transfer Protocol "and RPC protocol (RPC -" Remote Procedure Call "). The HTTP protocol is used for the transmission of static data.
  • the RPC protocol which is also an IP-based protocol, is used to transmit dynamic data, the dynamic data in particular being recorded in the field devices FG1 ... FGN Measured values and / or event lists relating to information about events in the field devices FG1 ... FGN.
  • the HTTP protocol allows the user devices N1 ... NN to access the field devices FG1 ... FGN.
  • the field device When accessing the BuB system, the field device first transmits HTML data to the user device used in this application by selecting the associated IP address of the field device to be operated / observed, the HTML data comprising data, with the help of which a display in the browser device of the retrieving user device Position of the field device can be generated, as shown by way of example in Figure 3.
  • the retrieval of the HTML data for generating the representation according to FIG. 3 can be triggered by the user using a selection of one of the field devices shown in the overview, for example by actuating a mouse or a keyboard of the user device.
  • the following information is shown on the surface 20 of the browser device (cf. left side in FIG. 3): field device family (for example SIPROTEC4), field device type and field device type 21, an operating tree 22, the version of the BuB tool 23 (version and date) and details of connection 24 to the field device (MLFB - "machine-readable manufacturing designation", BF number, connection status and
  • the HTML page 25 assigned to a link or branch in the operating tree 22 is also displayed on the surface. Depending on the link selected in the operating tree 22, the associated HTML page 25 is displayed on the surface 20 of the browser device.
  • the HTML pages stored in the field devices FG1 ... FGN can also include Java code which causes the browser device of the respective user device N1 ... NN to display the information from the parallel to the existing HTTP connection Field devices FG1 ... FGN loaded HTML page to establish another connection with the field devices FG1 ... FGN.
  • This second connection uses the RPC protocol to get dynamic data, such as event lists or measured values, from the field devices FG1 ... FGN particularly quickly and effectively for display in the user devices N1 ... NN within a selected HTML page, for example the HTML page 25 shown in Figure 3 to transmit.
  • FIG. 4 shows a schematic illustration for a more detailed explanation of the retrieval of the information in the context of the BuB system from the field devices FG1 ... FGN into the user devices N1 ... NN.
  • a browser device 31 is installed on a user personal computer 30, which represents an exemplary embodiment of the user devices N1 ... NN.
  • the user personal computer 30 is connected to a field device 33 via an IP network 32, which can include the proxy server 1, the star coupler 3, the modem 4, the modem 5 and the telecommunications network 6.
  • the field device 33 has an HTTP server 34.
  • HTML pages 35 are stored in the field device 33 and contain information specific to this field device 33.
  • the HTML pages 35 contain, for example, an HTML representation of the front view of the field device 33.
  • the HTML pages 35 are specially matched to the field device 33 and can be downloaded by the user personal computer 30 by means of an HTTP download from the HTTP server 34 of the field device 33 be called up.
  • Field device 33 can be triggered by entering a URL (URL - “Uniform Resource Locator”) in the browser device 31 or by means of the reference from another HTML page (“link”).
  • the field device 33 provides a series of raw data 36 (measured values, parameters, etc.) in the form of files.
  • the HTML pages 35 contain references to the raw data 36 available in the field device 33. If the raw data 36 are to be evaluated or otherwise changed, a program is required which can generate high-quality data formats according to certain algorithms. These data formats can then be used by the program, for example, to display the screen in connection with analysis options. The computing power required for this is generally not available in the field device 33. With the help of the browser device 31, the user has the option of using the IP network 32 via communication links.
  • the HTML page (s) 35 is (are) first requested from the user personal computer 30 with the aid of the browser device 31.
  • the HTTP server 34 of the field device 33 has provided the HTML page (s) 35, including the references to the raw data 36 contained therein
  • the HTML page 35 and the raw data 36 are transmitted to the user personal computer 30.
  • the HTML page 35 and the raw data 36 are transmitted by means of separate protocols between the field device 33 and the user personal computer 30, preferably HTTP or RPC protocol.
  • the raw data 36 can then be processed in the user personal computer 30 using suitable programs.
  • the field device 33 additionally comprises an RPC server 34a.
  • the referenced files of the raw data 36 can also be loaded automatically.
  • the file with the raw data 36 of the field device 33 is referenced with the parameter “SRC”.
  • the browser device 31 can start the correct program for further processing the raw data 36, the browser device 31 must be informed of the content type of the raw data 36.
  • the browser device 31 can have both the file extension (for example "* .ext") and the MIME type (MIME - "Multi-purpose Internet Mail Extension") supplied by the HTTP server 34 is evaluated.
  • the program for raw data processing started by the browser device 31 takes over the conversion of the downloaded raw data 36.
  • the program for raw data processing can be implemented as a browser plug-in, as an ActiveX component or as an external program.
  • the processing of sporadically generated raw data 36 is preferably carried out with the aid of a browser plug-in * or an Active X component.
  • the data is accessed using the TCP protocol. If continuously updated raw data 36 are to be processed in the form of an endless data stream, then it makes sense to use a more effective protocol for the transmission to the user personal computer 30 (the user devices N1..NN).
  • the additional RPC protocol is used to separate the information to be displayed in the user devices N1 ... NN (or the user personal computer 30) about the field device (s) FG1 ... FGN or 33 in allows static and dynamic information.
  • the static information is transmitted using the HTTP standard protocol, while the dynamic, ie changeable, data is transmitted via the more effective RPC protocol.
  • the effort that would be incurred when sending the dynamic data using the HTTP protocol by establishing / closing the connection and monitoring the connection would exceed the event-dependent, repeated transmission of the dynamic data using the RPC protocol. Since usually only a few data are to be transmitted quickly (measured values, message lists, ...), the use of a connectionless protocol, in particular the RPC protocol, is advantageous for the dynamic data.
  • RPC Remote Procedure Call
  • a local program calls a procedure on a remote system.
  • the concept of the remote procedure call ensures that the The entire network code remains hidden in the RPC interface and in the network routines.
  • UDP User Defined Protocol
  • UDP is located in the same layer as connection-oriented TCP, It is always a good idea to use the UDP protocol if only a little data is to be transferred quickly, so there is an exchange of short requests and answers in application programs between client and server that results from the establishment / termination of the connection and monitoring of the connection exceed that of the retransmission of the data, the separate transmission of static and dynamic Mixing data between the field devices FG1 ... FGN in the device network and the user devices N1 ... NN in the company intranet using different protocols is optimized by the provision and the specific design of the proxy server 1 described later in detail.
  • An RPC call runs as follows, for example:
  • a client process 100 running within browser 31 calls an RPC interface 101.
  • This client process 100 can be, for example, a Java applet embedded in an HTML page.
  • the RPC interface 101 has the task of specifying the subroutine entry.
  • the specification contains the name of the function and the number and types of parameters. This defines a logical entry.
  • the RPC interface 101 enables the remote procedure 102 to be started.
  • the parameters of the client process 100 are read from the RPC interface 101.
  • the purpose of the RPC interface 101 is to package and convert the parameters for the server program.
  • the network routines send the messages to a server process 103, which runs in the RPC server 34a.
  • An RPC interface 104 of the server process 103 rebuilds the parameters from the message packets.
  • server program In the next step the server program is called.
  • a server stub is defined for this. This stub is the actual entry into the procedure lying on the server process 103.
  • control is passed back to the RPC interface 104.
  • Interface 104 packs the return parameters and then transports the data to the network routines.
  • the network routines transport the data to the client process 100 via network-dependent calls.
  • the RPC interface 101 of the client process 100 unpacks the parameters and supplies the specified parameters with the new data.
  • Control is returned to the client process 100, which can process the received data further.
  • the concept of the remote procedure call ensures that the entire network code remains hidden in the RPC interface and in the network routines. This avoids that the application programs (client and server) focus on details such as conversion EBCDIC ⁇ > ASCII, number conversion. vertleiter, socket, session etc., must take care of.
  • An advantage of using the RPC protocol for dynamic data is that it simplifies the implementation of distributed applications.
  • the retrieval of information from the field device 33 which comprises the HTTP server 34, which is described in connection with FIG. 4, can also be used in connection with actions within the framework of the observation and operating system which are carried out for the purpose of operating the field device 33 become. This makes it possible to operate the field device 33 using the browser device 31. This is described in more detail below.
  • the field device 33 contains a storage device 35a, in which operating software is stored in the form of HTML pages 35, and a Java archive or data from which HTML pages can be generated.
  • the operating software is specially tailored to the field device 33.
  • an HTTP download starts, which leads to the downloading of the operating software from the HTTP server 34 of the field device 33 into the user personal computer 30.
  • the front view of the field device 33 is shown with all operating and display elements within the browser device (cf. FIG. 3 ). The user can then trigger certain operating functions of the field device 33 with the aid of a mouse click on the screen of the user personal computer 30.
  • the user action is transmitted to the field device 33 by means of a fast and effective protocol which, on the one hand, transmits the above-mentioned operating requirements from the user personal computer 30 to the field device 33 and, on the other hand, reads back reactions from the field device 33.
  • a fast and effective protocol which, on the one hand, transmits the above-mentioned operating requirements from the user personal computer 30 to the field device 33 and, on the other hand, reads back reactions from the field device 33.
  • the internal operating and display functions of the field device 33 to the interface of the browser device 31 published, for example keyboard buffer, display buffer, LED status.
  • TCP / IP and HTTP Internet protocols, such as TCP / IP and HTTP, do not offer any security mechanisms. Additional protocols are required to enable secure communication.
  • the mechanisms for protecting security-related actions on the field device 33 via TCP / IP communication are of particular importance. With regard to protection against unauthorized access, the operating actions on the field device 33 can be classified (cf. Table 1).
  • firewall e.g. proxy server
  • the internal network company intranet / LAN
  • another network e.g. Internet
  • the field device 33 is set in the delivery state in such a way that keys that enable the complete entry of customer passwords are blocked. This lock must be lifted by the customer on the field device 33 itself or with the operating program in the browser device 31 on the user personal computer 30 (password entry required). In the delivery state, only simple operating actions are possible via the browser device 31: navigation in the operating menu, display of measured values, parameters and message lists.
  • the parameterization of the field device 33 in the front view emulation is possible with knowledge of the passwords, as on the field device 33, when the necessary keys have been locked.
  • Actions relevant to security on the field device 33 are protected by authentication protocols, e.g. by means of a hash function and a key generated by the field device 33. This means that no conclusions can be drawn about entered passwords from the connection log.
  • 128-bit information the so-called “message digest”
  • the receiver compares the "message digest” with that from the field device 33 the information determined. As a result, field device passwords are not transmitted via the communication link.
  • the keys generated in the field device 33 expire after a short time and can only be used once for a transmission. This means that the recording of security-relevant logs and a later repetition of these recorded logs is ineffective.
  • An element for the optimized implementation of the described functional interaction of the elements of the observation and operating system for example the use of the RPC protocol, the retrieval of the raw data from the field devices FG1 ... FGN and the operation of the field devices by means of a browser on the user devices N1 ... NN, is the proxy server 1.
  • Known standard HTTP proxy servers only support the HTTP protocol and are therefore not able to serve as a gateway between the device network and the company intranet. For this reason, a specific proxy server 1 designed for the BuB system was created, which supports both protocols used by the field devices FG1 ... FGN (HTTP, RPC).
  • a client makes a request for an object to a server device, this request initially runs via a so-called proxy device.
  • the proxy device checks whether the object in question is already in a local memory (cache) of the proxy device, which is usually formed on a hard disk. If it is determined here that the object is not stored locally in the memory, the proxy device forwards the request to an actual target server device. From there, the proxy device receives the object and stores a copy of the object in the local memory for further requests for this object before the proxy device passes the object on to the requesting client. However, if the object is found in the local memory of the proxy device, the client's request is not put through to the target server device, but the client receives the desired object directly from the proxy device.
  • a prerequisite for optimal execution of the described method is a sufficiently large memory area in the proxy device, ie in the order of magnitude of several hundred MB to several ren GByte. Otherwise, the local memory in the proxy device overflows and a "garbage collector" (a so-called clean-up service) must be started, which filters outdated objects from the memory in order to make space for new objects there.
  • agarbage collector a so-called clean-up service
  • aching an improvement in performance (faster data transport than external); a saving in external bandwidth (more space for other services remains free); a reduction in response times
  • the proxy server 1 used to connect the device network and the company intranet (see FIG. 1) is based on the described basic principle and, due to the specific design, which will be described in detail later, also has the advantages mentioned below.
  • the proxy server 1 comprises a file memory or file cache which is optimized for use in the BuB system and buffers all the files called up from the field devices FG1 ... FGN with static data in the proxy server 1. If such a file is accessed for the first time, then this file must be fetched directly from one of the field devices FG1 ... FGN. If this file is accessed again, however, it can then be delivered directly from the file cache of the proxy server 1. Since the local company intranet is generally much faster than a modem connection to the field devices FG1 ... FGN, there are significant advantages in terms of speed when accessing the device network ongoing operation, only the dynamic data, which is significantly smaller than the HTML pages and the Java archives, can be transferred via the slow modem connection.
  • the proxy server 1 also increases security in the network.
  • the proxy server 1 seals off the two networks, device network and company intranet, from one another and only transmits the protocols processed in the proxy server 1. This means that only the requirements generated by a browser on the user devices N1 ... NN to the field devices FG1 ... FGN are transmitted from the company intranet. Only the responses generated by the field devices FG1 ... FGN are transmitted in the opposite direction. This means that all other data packets circulating on the company intranet are kept away from the device network and therefore do not influence the throughput in the device network. Furthermore, a high data volume occurring in the device network due to cross communication between the field devices FG1 ... FGN cannot increase the network load in the company intranet.
  • the use of the RPC protocol by means of the proxy server 1 has the advantage that it is ensured that the possibility of access to the field devices FG1 ... FGN remains restricted to the company intranet connected to the proxy server 1.
  • Today, a company intranet is usually via an HTTP
  • Gateway connected to the internet. This gateway assumes a firewall function (see FIG. 7) by blocking the transmission of the RPC protocol. As a result, the data of the field devices FG1 ... FGN can no longer be accessed outside the company intranet, since all dynamic data of the field devices FG1 ... FGN are transmitted via the RPC protocol.
  • the proxy server 1 enables a wide range of functions, which in the previous direct access to the field devices
  • a separate homepage is made available via which all connected field devices FG1 ... FGN can be reached.
  • the connected field devices FG1 ... FGN are automatically addressed and recognized; Representation of these field devices FG1 ... FGN on the homepage as the start page on the user devices N1 ... NN for direct device access. - There is access via device names of the field devices
  • the proxy server 1 can be configured using a browser on the user devices N1 ... NN (e-mail addresses, telephone numbers, device names, ...)
  • the proxy server 1 defines the possible access routes ("firewall function").
  • the proxy server 1 can cache data from the field devices FG1 ... FGN. This function is suitable for. B. for logging the accident information or the operational measured values. This data is stored internally in an XML database (XML - "Extended Markup Language").
  • the proxy server can make the data transmitted from the field devices FG1 ... FGN via the RPC protocol available in XML format For example, user-specific expansions of the representations available in proxy server 1 can be carried out.
  • an XSL parser XSL - "Extended Stylesheet Language" integrated in proxy server 1 is available. - Thanks to the filters on the XML database that can be implemented using the XSL parser, the proxy server 1 can also be used as a client for other applications.
  • the proxy server 1 provides its own e-mail mailboxes that can be accessed using a POP3 client (POP3 - "Post Office Protocol Stepping 3" ), such as Outlook, can be called up. Still is forwarding of e-mails to another mailbox is possible using an SMTP server (STMP - "Simple Message Transfer Protocol") integrated in the proxy server 1.
  • POP3 Post Office Protocol Stepping 3
  • SMTP server STMP - "Simple Message Transfer Protocol"
  • the design of the proxy server 1 is described in more detail below.
  • FIG. 7 shows an arrangement with the device network and the company intranet according to FIG. 1, elements of the proxy server 1 being shown schematically.
  • FIG. 8 shows function blocks of the proxy server 1 in a block diagram.
  • each of the field devices FG1 ... FGN has a respective HTTP server HS1 ... HSN, which correspond to the respective HTTP server 34 (see FIG. 4) and is connected to a star coupler 39.
  • the proxy server 1 also has an HTTP server 40. The operation of the proxy server 1 is described below with reference to FIG. 8.
  • Access to the proxy server 1 always takes place from the local network of the company intranet, in which the user devices N1 ... NN with the respective modem connection are located in the device network comprising the field devices, which can comprise a substation or several substations. If one of the user devices N1 ... NN is addressed as a server via the associated local IP address, this access is forwarded to the HTTP server 40 via a TCP / IP stack 41 (TCP - “Transfer Control Protocol”).
  • TCP / IP stack 41 TCP - “Transfer Control Protocol”.
  • the HTTP server 40 delivers the requested files to the company intranet.
  • the HTTP server 40 contacts a cache manager 43 via a file filter 42.
  • the file filter 42 normally forwards the request to the cache manager 43. Only certain requests are recognized based on the requested file type and sent to another processing path. These exceptions will be described later.
  • the cache manager 43 first tries to find the requested file in the local files 44 or in a file cache 45. If the requested file is neither a local file of proxy server 1 nor in the file cache
  • a modem connection with the PPP protocol is preferably used as the connection to the device network (cf. FIG. 1). Since the proxy server 1 can hold several connections to different field devices FG1 ... FGN at the same time via this modem connection, an arbiteration of this modem connection is necessary because the PPP protocol can only manage a point-to-point connection.
  • a block slot protocol 48 is used for this purpose. This protocol allocates time slices on the modem communication link to the individual PPP connections and thus prevents collisions between the individual connections.
  • the block slot protocol 48 is also responsible for recognizing all field devices FG1 ... FGN active in the device network. For this purpose, the device network is searched cyclically for active field devices. The detected active field devices are entered by a device manager 49 into an XML database 50 of the proxy server 1.
  • the XML database 50 is a data tree stored according to the standardized “Document Object Model”. Now contains a user device N1,... Or, respectively, via the HTTP server 40 in the browser of a user device connected to the proxy server 1. NN loaded HTML page Java code that establishes a parallel UDP connection (UDP - "User Defined Protocol") for the RPC protocol, then this way an RPC server 51 is addressed from the company intranet.
  • UDP User Defined Protocol
  • connection management 52 may be included since the UDP protocol does not operate in a connection-oriented manner.
  • the connection management 52 ensures that a separate communication port for an RPC client 53 of the proxy server 1 is reserved in the device network for each usage device N1... NN from the company intranet.
  • the RPC requests from the company intranet are then forwarded directly to the device network via the RPC client 53 of the proxy server 1.
  • the responses of the field devices FG1 ... FGN to RPC requests are forwarded to the RPC server 51. This forwards the response of the respective field device FG1, ... or FGN to the user devices via the company intranet.
  • the dynamic data currently transferred in the RPC protocol from the respective field device FG1,... Or FGN are stored in the XML database 50 in the proxy server 1.
  • the data stored in the XML database 50 can be converted into any other data formats using an XSL parser 54 integrated in the proxy server 1.
  • the transformation instructions required for this must be stored locally in proxy server 1 as an XSL script file.
  • an * .XML file must be requested from the HTTP server 40. Such a request is made by the one connected to the HTTP server 40
  • HTML files generated dynamically from an XSL template with the current data of the field devices FG1 ... FGN from the XML database 50 or simply a subtree of the database can be transferred as an XML file.
  • the file filter 42, the cache management 43, the local files 44, the file cache 45, the XSL parser 54 and the XML database 50 form a file system of the proxy server 1.
  • HTTP Hypertext Transfer Protocol
  • client computer of the Internet user
  • server server device
  • the port 80 is defined as the starting point, ie an HTTP server is listening on this port for new client connections, or the vast majority of HTTP server software via a corresponding configuration dialog, you can also be instructed to use a different port for establishing contact.
  • a connection between an HTTP client and an HTTP server is very short-lived.
  • the HTTP client establishes a TCP connection to the desired HTTP server via port 80 and sends a request for a desired document to the HTTP server.
  • the HTTP server receives the request, evaluates it and, if successful, sends the desired document back to the HTTP client.
  • the HTTP server closes the TCP connection automatically, after sending the requested document or an error message to the HTTP client in response to its request.
  • HTTP HyperText Transfer Protocol
  • HTTP server An important functionality of HTTP is that the HTTP client can tell the HTTP server what kind of data it can understand. With every request, there must be communication between the HTTP client and the HTTP server about how the data should be transmitted. This communication creates a so-called "overhead"; HTTP is therefore also referred to as a stateless protocol because the connection does not go through several phases, from logging in, through data exchange to logging out through the HTTP client. On the one hand, this facilitates the development of HTTP client / HTTP server software, but is with regard to
  • the HTTP protocol is used to access sources in URL format (URL - "Uniform Resource Locator").
  • the HTTP client usually a web browser on the computer of the Internet user. It requires an HTML And then generates a sequence of requests for file references in that HTML page, after which the user will likely click a link in the requested HTML page and the HTTP client will send a request for the HTML pages associated with that link , to the same or another HTTP server.
  • These additional communication connections no longer have information about a previous connection. This works in simple client / server environments. However, in the case of more extensive communications, this mode of operation can become a problem, because for everyone else If the amount of data to be transferred is so small, this "overhead" arises, which reduces efficiency.
  • Figure 9 shows a schematic representation of the syntax of a request in connection with an HTTP client / server interaction.
  • the HTTP client / server interaction consists of a single request / response communication. It includes a "request line", one or more optional "request header fields” and an optional "entity body”.
  • a TCP Connection to the HTTP server 61 opened 62.
  • the HTTP client 60 then sends a command string to the HTTP server 61.
  • the HTTP server 61 responds via the TCP connection opened by the HTTP client 60 with a header which is next to that of the HTTP server 61 supported HTTP version also contains the MIME type and the encoding of the requested file, the content of the requested file is added to this header in ASCII format by the HTTP server 61.
  • the HTTP server 61 the complete file sent, it closes the TCP connection opened by the HTTP client 60 63 again. This process can be repeated as often as desired.
  • the "request line” consists of three text fields, which are separated by spaces.
  • the first field specifies the method (or the command).
  • the second field specifies the name of the source (is the URL without specifying the protocol and the
  • the last field specifies the protocol version of the HTTP client 60 used, for example HTTP / 10.
  • the “request header fields” provide additional information about the request and the HTTP client 60.
  • the fields are used as a type of RPC parameter. Each field consists of a name, followed by a colon and the field value. The order of the "header fields” is not important here.
  • the "entity body” is sometimes used by HTTP clients 60 to send larger information packets to the HTTP server 61.
  • the file cache 45 does not work as usual with the URL, the date and the lifespan of the files to be managed, but uses other criteria for identifying a file. If only the three criteria mentioned were used to decide whether a file locally in the file cache is identical to the file available in the field device, then a comparison of the file characteristics mentioned would be necessary to carry out this test. To do this, the header from the field device would have to be requested for each file become. Since the file system of the field devices FG1 ... FGN can only be loaded as a unit in the form of a KON file (converted files - format of the files that can be loaded into the user devices N1 ...
  • the file "ver.txt” can have / display the following content:
  • the slot protocol 48 (cf. FIG. 8) serves to connect the proxy server 1 to the field devices FG1... FGN in an arrangement with a star coupler according to FIG. 7.
  • the slot protocol 48 is divided into the two areas (i) device detection and (ii) Arbiting the star coupler arrangement.
  • the device detection is used for the automatic detection of all field devices FG1 ... FGN connected to the star coupler 39.
  • the arbitration must prevent collisions between datagrams of different field devices FG1 ... FGN on the communication link between the proxy server 1 and the individual field devices FG1 ... FGN.
  • the device identification is a component of the slot protocol 48. This protocol part exclusively occupies the serial connection, i. H. no other communication may be active on the modem link during device detection. For this reason, device recognition is only activated when the modem connection is established. This part of the protocol is inactive during operation of the monitoring and operating system. However, device detection can be activated if necessary.
  • Figure 10 shows a master-slave arrangement with a star coupler to explain the device detection.
  • the slot protocol 48 works according to the master-slave principle.
  • a master 70 is located at the upper connection in FIG. 10.
  • the lower connections of a star coupler 71 which corresponds to the star coupler 3 in FIG. 1, are each occupied by a slave S1 ... SN, which the field devices FG1 ... FGN according to FIG 1 correspond.
  • the master 70 could query every possible address of the connected slaves S1 ... SN and, in response to this query, the found slave Sl, ... or add SN to the list of devices known to Master 70.
  • this procedure can no longer be carried out with an address range of 32 bits.
  • 2 ⁇ 32 queries would be required.
  • this number can no longer be carried out since the time required for this query would exceed the life of the system.
  • the problem is solved according to the invention in the following way:
  • an address range is always queried when a request is made. Only the slaves that are in the queried address range respond to this request. Since there can be several field devices (slaves) in the same queried address range, a collision inevitably results in a simultaneous response from several of the slaves S1 ... SN. This collision is deliberately accepted and is part of the proposed procedure. For this reason, the master 70 only checks whether an answer to its request has been received within a defined period of time.
  • the master 70 sends out a request with a fixed bit of the address and a mask for the other address bits. Two queries can be used to test whether there are slaves in the address range specified by the fixed bit. If a response to a request for an address area has been received, the mask is reduced by one bit and for the next fixed bit is tested with two inquiries as to whether there are slaves in the now smaller address area. If there is an answer to the request for the now smaller address area, the next bit of the address area in which slaves are located is found. This process is repeated until the mask for the address area has been reduced to 0 bits. Then one of the slaves S1 ... SN is clearly identified on the bus.
  • FIG. 12 explains the described method again using a simple addressing scheme with a 4-bit address, that is to say for an address space from 0 to 15. It is assumed that the devices with addresses 3, 4 and 7 are in the arrangement. The polling of the most significant bit is started. Address space 0 to 7 is tested on the one hand and address space 8 to 15 in a second query with one query.
  • the slaves Sl ... Sn or the field devices FG1 ... FGN are connected to the master 70 using an IP-based protocol.
  • IP protocol all bus users have a 32-bit address. The address is divided into octets and each octet is shown in decimal. The hexadecimal 32 bit number 0x8D8D8000 therefore corresponds to the IP address 141.141.128.0.
  • FIG. 11 shows the flow diagram of the method as a Nassi-Sneidermann diagram.
  • the test as to whether a field device (slave) can be addressed in the available address range is preferably initiated by the master 70 with the aid of a request datagram known as such.
  • a request datagram known as such.
  • the fact that all signals received by the slaves S1 ... SN in the star coupler 71 are linked via a logical OR gate and this sum signal is forwarded to the master 70, can ensure that a response from one of the slaves S1. ..SN is recognized in any case. If the response datagrams of several of the slaves S1 ... SN overlap in time, an incorrect datagram is received in master 70. This case is also recognized as the answer.
  • a monitoring time can be defined for master 70. If the master 70 receives a response within this monitoring time, there are slaves or field devices in the requested address area. Conversely, there are no field devices in the requested address area if the master 70 has not received a response to the request within the monitoring time.
  • the error protection of the received datagram can be used to rule out a line fault and thus a possible fault detection of a connected slave. If, during the monitoring time, a Interference that simulates a non-existent slave only leads to an extension of the polling process, but not to an incorrect detection of connected slaves, since this line fault is detected at the latest when the mask is completely resolved.
  • Test 141 141 .128.0 Mask: 255.255.128.0
  • Test 141 141 84 2 Mask: 255.255.255.254
  • Test 141 141 84 0
  • Mask 255.255.255.254
  • Test 141 141 82 .0 Mask 255 .255 254 .0
  • Test 141 141 80 .0 Mask 255 .255 254 .0
  • Test 141 141 81 .0 Mask 255 .255 255 .0
  • Test 141 141 80 162 Mask 255 255 255 254
  • Test 141 141 80 162 Mask 255 255 255 255 255 255 255
  • FIG. 12 illustrates the process shown in the form of a tree, the fields framed in bold indicating the queries that were answered by one or more slaves S1 ... SN or field devices.
  • an IP-based network can be used instead of the simple architecture with star coupler 39. In this case, it is not necessary to arbiter this network using a protocol, for example the slot protocol 48. This function is performed by the network itself. In this embodiment, functions of the network can also be used for device detection. With a network connection between the proxy server 1 and the field devices
  • FG1 ... FGN a broadcast service is used for self-configuration of the observation and operating system.
  • the broadcast service is used to identify the field devices connected to the IP-based network (e.g. LAN) that contain a server for their own operation.
  • the broadcast service is also used to collect spontaneous events that have occurred in the connected field devices.
  • the broadcast service is an IP application and is therefore based on the functions of the IP stack and is based on the UDP protocol. For this service server side z. B. a fixed port OxDOOO reserved. A free port is dynamically selected on the client side.
  • the standard UDP / IP protocol it can be used on the IP programming interfaces of common operating systems such as B. MS Windows or Linux. This enables the proxy server 1 to be easily ported to classic office servers.
  • the broadcast service is active both in proxy server 1 and in the individual field devices.
  • proxy server 1 is defined as the master.
  • a configuration query is a UDP telegram sent by the master. Depending on the configuration, this telegram is directed to a broadcast or a multicast IP address.
  • a description of broadcast or multicast IP addresses can be found, for example, in Karanjit S. Siyan: Inside TCP / IP Third Edition, New Riders Publishing, Indianapolis, 1997, ISBN 1-56205- 714-6, page 187ff.
  • the broadcast service also has the task of distributing an event occurring spontaneously in one of the field devices in the IP-based network to the subscribers of the broadcast service. Since the field devices on the one hand have no information about which master is responsible for this signal and, on the other hand, it may be possible for several masters with distributed tasks to exist in the IP-based network, the event telegram is sent as a broadcast to all network participants. Depending on the event type and the sender, the masters can ignore this signal or trigger an action which is carried out via another protocol, e.g. B. HTTP, retrieves additional information from the field device. This retrieval of additional information on the field device sending the event by the responsible master also serves as an acknowledgment of receipt by the master. If an event telegram is not confirmed, it is repeated at regular intervals (for example about 10 s or with a logarithmically increasing time) until confirmation is received from a master.
  • regular intervals for example about 10 s or with a logarithmically increasing time
  • FIG. 13 shows a schematic illustration to explain the method in the context of the configuration query.
  • proxy server 1 sends a configuration request 72 as a broadcast to all participants in the network. All field devices FG1 ... FGN respond with a UDP datagram to the IP address of the master that sent the configuration request. As already stated, this UDP datagram contains provides the most important information about the connected devices.
  • FIG. 14 shows a schematic block diagram of the connection of the device management 49 in the proxy server 1.
  • the device management 49 provides the cache management 43 and the XML database 50 with information about the field devices FG1... FGN recognized in the device network. For this purpose, the device management 49 obtains its information about the connected field devices FG1... FGN from the process that is carried out as part of the slot protocol 48. In this way, the IP addresses of the connected field devices FG1 ... FGN are provided.
  • the device management 49 is supplied by the slot protocol 48 with the information about the recognized field devices FG1 ... FGN.
  • the slot protocol 48 only provides the device management 49 with the IP addresses of the recognized field devices FG1 ... FGN. All further information about the field devices FG1 ...
  • FGN which are to be provided by the device management 49 in the proxy server 1, is obtained by downloading HTTP data in defined files from the field devices FG1 ... FGN.
  • Device management 49 uses the known IP addresses of all recognized field devices FG1 ... FGN to provide cache management 43 with the following information about field devices FG1 ... FGN: field device type, field device version and version of the file block for the observation - and operating system.
  • This information is also available in the file cache 45 (cf. FIG. 8) for the files already stored there. This means that when a file is requested by a the field devices FG1 ... FGN were decided on the basis of this information whether the file in file cache 45 is identical to the file available in the field device without reading the file header of the requested file from the specific field device. It is only necessary to compare the version information for the file in the file cache 45 with the information from the device management 49 for the IP address of the specific field device.
  • connection of the device management 49 to the XML database 50 is used to provide information from the field devices FG1 ... FGN.
  • This information is loaded in the form of an XML file from the field devices FG1 ... FGN.
  • the following table shows an overview of the contents of this file:
  • the file “DevData .xml” is transformed in the proxy server 1 after downloading using the XSL parser 54 into the internal format of the proxy server 1 and then entered in the XML database 50 of the proxy server 1.
  • the XSL parser 54 (cf. FIG. 8) is used to generate dynamically generated HTML files from the central XML database 50 of the proxy server 1. For this purpose, XSL scripts stored locally in the proxy server 1 are used. The XSL scripts can be imported into the proxy server 1 using an admin page.
  • FIG. 15 shows the integration of the XSL parser 54 in the proxy server 1.
  • this request is filtered out by the file filter 42 and forwarded to the XML front-end HTTP 55.
  • This front end searches for an XSL transformation script belonging to the requested XML file and starts the XSL parser 54 with these two files.
  • the content of this database must match the data in the Existing data can be compared. This matching process is necessary because a lot of data stored in the XML database 50, such as, for example, B. Measured values are time-varying.
  • the block XML front-end RPC cache 57 takes care of this comparison.
  • the XSL parser 54 accesses the XML database 50, the intermediate XML front-end 57 checks the validity period of the requested information. If the requested information has already become invalid, the connection manager 52 requests it again from the RPC client 53 from the device, updates it in the XML database 50 and forwards it to the XSL parser 54.
  • the device manager 49 continuously monitors the status of the devices connected to the device network and updates this information using the XML front-end device data 56 in the XML database 50.
  • the XSL parser 54 is the main link in the display of the current data received from the field devices FG1... FGN from the XML database 50.
  • Each XSL script specifies transformation rules which determine the manner in which certain data are output the XML database 50 are to be displayed in the form of HTML pages in the user devices N1 ... NN.
  • One of the basic principles of XML is the separation of content and presentation. An XML document only contains "content", its presentation must be defined separately in the form of a style sheet.
  • There are various ways of adding the display information to an XML document These are based on two basic processes: Either the document is brought into a displayable form according to a style sheet, or the style sheet guides the display mechanism in how the individual elements of the document are to be displayed. These two basic procedures can be varied in different ways: - CSS stylesheet + XML document ⁇ XML-capable browser The browser processes the document and the presentation information in the form of a CSS style sheet and creates a presentation.
  • a display program that can process XSL stylesheets receives the presentation information in the form of an XSL stylesheet in addition to the document.
  • the XML document is transformed from an XSL transformer into an (X) HTML document according to the transformation rules of an XSL stylesheet, which can then be displayed by a browser.
  • FIG. 16 shows a schematic block diagram of an XSLT processor (XSL - “Extended Stylesheet Language Transformation”).
  • the block diagram shown in FIG. 16 again illustrates the data flow when an XML file is requested.
  • the file Xview.XML requested by the client is forwarded from the HTTP server to the XSLT processor 54.
  • This searches for the file Xview.XSL belonging to the requested file Xview.XSL and starts the XSLT processor 54 with these two files.
  • If process data from the XML database 50 of the proxy server is to be used in the transformation process started via the requested file Xview.XML, then the transformation script Xview.XSL must contain a reference to this database.
  • this XML database 50 has the name Siprogate .XML.

Landscapes

  • Engineering & Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Manufacturing & Machinery (AREA)
  • Quality & Reliability (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Automation & Control Theory (AREA)
  • Computer And Data Communications (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Small-Scale Networks (AREA)

Abstract

L'invention concerne un procédé permettant de détecter plusieurs appareils de champ, reliés à un appareil central, en une configuration d'appareils, notamment une configuration de coupleurs en étoile. Les multiples appareils de champ de la configuration d'appareils peuvent être adressés électroniquement par l'appareil central, à l'aide, dans chaque cas d'une adresse électronique provenant d'une zone d'adresses globale. Selon ce procédé, une moitié et moitié restante d'une zone d'interrogation d'adresse peuvent être consultées par demande électronique individuelle de l'appareil central aux appareils de champ. Des réponses électroniques des appareils de champ de la moitié de la zone d'interrogation d'adresses et/ou de la moitié restante de la zone d'interrogation d'adresses sont détectées à l'aide de l'appareil central. L'interrogation électronique et la détection électronique de réponses sont répétées en fonction des réponses obtenues, jusqu'à ce que la zone d'interrogation d'adresses comprenne exactement une adresse électronique provenant de la zone d'adresses globale.
PCT/DE2002/003850 2001-10-15 2002-10-08 Procede de detection de plusieurs appareils de champ dans une configuration d'appareils Ceased WO2003036401A2 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
DE10151119A DE10151119C2 (de) 2001-10-15 2001-10-15 Verfahren zum Erfassen von mehreren Feldgeräten in einer Gerätekonfiguration
DE10151119.1 2001-10-15

Publications (2)

Publication Number Publication Date
WO2003036401A2 true WO2003036401A2 (fr) 2003-05-01
WO2003036401A3 WO2003036401A3 (fr) 2004-04-15

Family

ID=7702725

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/DE2002/003850 Ceased WO2003036401A2 (fr) 2001-10-15 2002-10-08 Procede de detection de plusieurs appareils de champ dans une configuration d'appareils

Country Status (2)

Country Link
DE (1) DE10151119C2 (fr)
WO (1) WO2003036401A2 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105511424A (zh) * 2015-11-19 2016-04-20 上海斐讯数据通信技术有限公司 一种基于移动终端的生产监控系统及方法

Families Citing this family (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE10344360A1 (de) * 2003-09-24 2005-05-12 Siemens Ag Verfahren und Einrichtung zur Kommunikation mit einer Anlage
DE102004002330A1 (de) 2004-01-16 2005-08-04 Abb Patent Gmbh System zur Datenübertragung in Schaltanlagen
DE102005014050A1 (de) * 2005-03-23 2006-09-28 Endress + Hauser Process Solutions Ag Verfahren zum sicheren Bedienen eines Feldgerätes der Automatisierungstechnik
DE102006005805A1 (de) * 2006-02-08 2007-08-09 Siemens Ag Verfahren zur automatischen Konfigurierung eines Feldgeräte enthaltenden Netzwerks
DE102007022006A1 (de) * 2007-05-08 2008-11-13 Endress + Hauser Flowtec Ag Verfahren zum Übertragen von Daten zu einem Feldgerät der Automatisierungstechnik insbesondere der Prozessautomatisierungstechnik
DE102007029136A1 (de) * 2007-06-25 2009-01-02 Vega Grieshaber Kg Vorrichtung und Verfahren zum Generieren einer Bedienoberflächenkonfiguration für ein Feldgerät
DE102007050708B4 (de) 2007-10-22 2009-08-06 Phoenix Contact Gmbh & Co. Kg System zum Betreiben wenigstens eines nicht-sicherheitskritischen und wenigstens eines sicherheitskritischen Prozesses
DE102008039696A1 (de) * 2008-08-26 2010-03-04 Endress + Hauser Wetzer Gmbh + Co. Kg Verfahren zum Betreiben eines Systems von Feldgeräten
DE102009042354C5 (de) * 2009-09-23 2017-07-13 Phoenix Contact Gmbh & Co. Kg Verfahren und Vorrichtung zur sicherheitsgerichteten Kommunikation im Kommunikations-Netzwerk einer Automatisierungs-Anlage
DE102010046480B4 (de) * 2010-09-24 2021-12-16 Efr Europäische Funk-Rundsteuerung Gmbh Verfahren und System zur Übertragung eines Schaltbefehls an Stromnetzeinheiten
EP2787405B1 (fr) * 2013-04-05 2017-07-19 Siemens Aktiengesellschaft Procédé de fonctionnement d'une installation électrique et installation électrique
DE102018125894B4 (de) * 2018-10-18 2021-01-28 Bender Gmbh & Co. Kg Verfahren zum Auflösen eines Adresskonflikts bei dem Modbus RTU-Standardprotokoll
CN109189030B (zh) * 2018-10-22 2021-08-17 国网电力科学研究院(武汉)能效测评有限公司 一种面向多能源供给系统的蓄热远程控制系统

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4797948A (en) * 1987-07-22 1989-01-10 Motorola, Inc. Vehicle identification technique for vehicle monitoring system employing RF communication
US5365551A (en) * 1992-12-15 1994-11-15 Micron Technology, Inc. Data communication transceiver using identification protocol
US5373288A (en) * 1992-10-23 1994-12-13 At&T Corp. Initializing terminals in a signal distribution system
JPH07231329A (ja) * 1994-02-18 1995-08-29 Csk Corp ネットワークアドレスの付番装置
DE19544027C2 (de) * 1995-11-25 1999-01-07 Bernward Dr Zimmermann Bussystem, insbesondere zur elektrischen Installation
US5835720A (en) * 1996-05-17 1998-11-10 Sun Microsystems, Inc. IP discovery apparatus and method
DE19733906C2 (de) * 1997-08-05 1999-09-30 Siemens Ag Verfahren zur automatischen Adreßvergabe, Bussystem zur automatischen Adreßvergabe und Kommunikationsteilnehmer, die im Bussystem bzw. im Rahmen des Verfahrens einsetzbar sind
FR2776097B1 (fr) * 1998-03-16 2000-08-11 Sgs Thomson Microelectronics Procede perfectionne d'identification de cartes electroniques

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105511424A (zh) * 2015-11-19 2016-04-20 上海斐讯数据通信技术有限公司 一种基于移动终端的生产监控系统及方法

Also Published As

Publication number Publication date
DE10151119A1 (de) 2003-04-24
WO2003036401A3 (fr) 2004-04-15
DE10151119C2 (de) 2003-11-20

Similar Documents

Publication Publication Date Title
EP1436676B1 (fr) Procede permettant de faire fonctionner et d'observer des appareils utilisables in situ
EP1436677B1 (fr) Procede de mise en service d'un systeme de commande et de surveillance d'appareils de terrain
DE60118487T2 (de) Kommunikationsystem auf Basis von WDSL Sprache
DE60023292T2 (de) Doppelter ethernet-stack für plc-zugang mit maximaler geschwindigkeit
DE60300432T2 (de) Vorrichtung und Verfahren zur Optimierung des Netzwerkverkehrs
DE60222640T2 (de) Verfahren und system zur adressierung von geräten in einem rechnernetzwerk
DE69805952T2 (de) Vorrichtung zur steuerung von verbindungen zwischen netzwerken
EP1527554B1 (fr) Reseau informatique comportant des noeuds informatiques de diagnostic
DE10151119C2 (de) Verfahren zum Erfassen von mehreren Feldgeräten in einer Gerätekonfiguration
EP1305930B1 (fr) Systeme et procede pour transmettre des donnees opc par l'intermediaire de reseaux de donnees, notamment par internet, au moyen d'une communication de donnees asynchrone
EP2724494A1 (fr) Procédé de fonctionnement d'un appareil de terrain, ainsi qu'appareil de terrain
DE10208146A1 (de) Verfahren zum rechnergestützten Erzeugen einer graphischen Benutzeroberfläche und Geräteüberwachungs-/Steuerungseinheit
EP3718265A1 (fr) Dispositif de raccordement pour un échange de données entre un réseau de bus de terrain et un nuage
EP1362304A2 (fr) Systeme et procede pour generer et memoriser des pages web tout en optimisant l'encombrement en memoire
WO2003036402A2 (fr) Procede de conception d'une fonction d'utilisation d'appareils de champ et appareil de champ correspondant
EP1338961A2 (fr) Procédé pour la génération d'un interface utilisateur assistée par ordinateur
DE10151118A1 (de) Verfahren zum Übertragen von Rohdaten und Feldgerät
EP1518386B1 (fr) Systeme et procede de communication directe entre des appareils d'automatisation
EP3537654B1 (fr) Procédé et système de détermination d'une configuration d'une interface
EP1435026B1 (fr) Systeme et procede d'emission de donnees d'un appareil, en particulier d'un appareil d'automatisation, par l'intermediaire d'une interface normalisee avec remplacement de variables par l'intermediaire d'un serveur echo
WO2002067532A1 (fr) Procede pour transmettre des donnees, serveur mandataire et systeme de transmission de donnees
EP1341082A2 (fr) Méthode pour la génération assistée par ordinateur d'une interface graphique d'utilisateur d'une unité de monitorisation ou de contrôle d'un appareil
DE102007039266B4 (de) System und Verfahren für den Zugriff auf Prozess- und/oder Anlageninformationen mittels einer Standardapplikation
EP3979011A1 (fr) Détermination d'un état de sécurité
EP2031509A1 (fr) Procédé et dispositif de production et/ou d'utilisation d'un service Web générique

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A2

Designated state(s): US

AL Designated countries for regional patents

Kind code of ref document: A2

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR IE IT LU MC NL PT SE SK TR

121 Ep: the epo has been informed by wipo that ep was designated in this application
DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
122 Ep: pct application non-entry in european phase