JP2011227902A - Systems and methods for synchronization of external control system with fieldbus devices - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide systems and methods for synchronization of an external control system with fieldbus devices.SOLUTION: A message including timing information for at least one fieldbus device in direct or indirect communication with a controller may be received by the controller. Based upon information included in the received message, the controller may determine a start time for a current operation cycle of the at least one fieldbus device. The controller may then utilize the start time and a duration of the current operation cycle to determine a specific time at which the controller will execute control functionality for the at least one fieldbus device such that a control message output by the controller will be received by the at least one fieldbus device within the current operation cycle.

Description

  Embodiments of the present invention generally relate to control systems, and more specifically to synchronization of external control systems and fieldbus devices.

  Control systems are used in a wide variety of applications. For example, the control system is utilized in the context of power generators, power plants, and / or process plants. The control system generally includes a central controller that communicates with other components of the control system, such as sensors, measuring devices, valves, and the like. The central controller generally communicates with these other components via appropriate network communications.

US Pat. No. 6,119,122

  With the development and adoption of foundation fieldbus standards, fieldbus devices are incorporated into control systems. Generally, fieldbus devices are configured to perform standard operations during a macro cycle or other operating cycle. The operating cycle of fieldbus devices is often much longer than the operating cycle of an external controller such as a central controller in a power plant. Considering this asynchronous operation, there may be a timing shift between the controller and the fieldbus device. Further, the communication and / or command output from the controller to the fieldbus device may be received as late as two macro cycles from the cycle in which the operation data is provided from the fieldbus device to the controller. Therefore, an improved system and method for synchronizing a fieldbus device with an external controller or external control system is desired.

  Some or all of the above needs and / or problems may be addressed by certain embodiments of the invention. Embodiments of the present invention can include systems and methods for synchronizing fieldbus devices with an external control system. According to one embodiment of the present invention, a method for synchronizing control of fieldbus devices is disclosed. A controller including one or more computers can receive a message that includes timing information for at least one fieldbus device that communicates directly or indirectly with the controller. The controller can determine the start time of the current operating cycle of the at least one fieldbus device based on the information included in the received message. Based on the start time and duration of the current operation cycle, the controller can cause the controller to receive at least one fieldbus so that control messages output from the controller are received by the at least one fieldbus device during the current operation cycle. A specific time for performing the control function on the device can be determined.

  According to another embodiment of the present invention, a control system is disclosed. The control system can comprise at least one memory and at least one processor. The at least one memory can be configured to store computer-executable instructions. At least one processor receives and receives a message including timing information about at least one fieldbus device that accesses at least one memory, executes computer-executable instructions, and communicates directly or indirectly with the processor A start time of a current operation cycle of at least one fieldbus device based on information contained in the received message, and a control output from at least one processor based on the start time and duration of the current operation cycle It may be configured to determine a specific time at which a control function for at least one fieldbus device is performed such that a message is received by the at least one fieldbus device during the current operating cycle.

  Additional systems, methods, devices, functions, and aspects are realized through the techniques of various embodiments of the invention. Other embodiments and aspects of the invention are described in detail herein and are considered a part of the claimed invention. Other embodiments and aspects can be understood with reference to the description and drawings.

  Having outlined the invention above, reference is now made to the accompanying drawings. The drawings are not necessarily drawn to scale.

1 is a schematic diagram of an exemplary control system that can be utilized in accordance with various embodiments of the invention. FIG. 4 is a flowchart of an exemplary method for synchronizing a fieldbus device and an external control system, according to an exemplary embodiment of the present invention. FIG. 6 illustrates an example of synchronization that can be achieved by various embodiments of the present invention. 3 is a flowchart of an exemplary method for communicating commands received from an external computer to a fieldbus device, according to an exemplary embodiment of the present invention. 4 is a flowchart of an exemplary method for facilitating writing of values to a fieldbus device by an external computer, according to an exemplary embodiment of the invention. 2 is a flowchart of an exemplary method for identifying a fieldbus device in a control system, according to an exemplary embodiment of the present invention. 4 is a flowchart of an exemplary method for updating a list of fieldbus devices in a control system, according to an exemplary embodiment of the present invention. FIG. 6 is an example of a presentation of a connected fieldbus device that can be generated according to various embodiments of the present invention. 1 is a schematic diagram of an exemplary control system that can be utilized in accordance with various embodiments of the invention. FIG. 4 is a flowchart of an example method that facilitates communication between one or more fieldbus devices and an external control system, according to an example embodiment of the invention.

  Exemplary embodiments of the present invention are described more fully hereinafter with reference to the accompanying drawings. The drawings illustrate some but not all embodiments of the invention. Indeed, the invention can be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; Rather, these embodiments are provided so that this disclosure will satisfy applicable legal requirements. Like reference numerals refer to like elements throughout the specification.

  Systems and methods for synchronizing control of fieldbus devices within a control system are disclosed. More specifically, systems and methods for synchronizing an external controller or control system with one or more fieldbus devices are disclosed. One controller and any number of fieldbus devices can be provided. The controller can communicate directly or indirectly with each fieldbus device. For example, the controller can communicate with one or more fieldbus devices via one or more suitable link devices. In operation, the controller can receive a message that includes timing information for at least one fieldbus device. For example, the controller can receive a message from the link device. Based on information contained in the received message, such as current timing information for one or more segments associated with the link device, the controller can determine the current operating cycle for the fieldbus device or group of fieldbus devices ( For example, the start time of the current macro cycle can be determined. The controller can also identify or determine the duration of the current operating cycle, for example by accessing the duration information of the appropriate memory device. Based on the start time and duration of the operating cycle, the controller can determine a specific time or point at which the controller performs a control function for the fieldbus device or group of devices. For example, the controller can determine an offset from the current time. When the determined specific time is reached, the controller may process the input received from the fieldbus device and / or perform other control processing for the fieldbus device. The controller can then output any number of control messages and / or data for communication to the fieldbus device. According to one aspect of the invention, the output message can be received at the device during the current operating cycle of the fieldbus device. In this respect, the controller and the fieldbus device can be synchronized.

  The controller may also facilitate communication with one or more fieldbus devices, as required by certain embodiments. For example, the controller can facilitate communication between an external computer, such as a human machine interface (HMI) computer, and a fieldbus device. In this regard, the controller receives a command formatted according to a protocol other than the fieldbus protocol from the HMI computer, generates a command formatted according to the fieldbus protocol, and transmits the generated command to one or more fieldbus devices. Can be output for communication. For example, the controller can function as a gateway device that facilitates reading and / or writing of fieldbus data values and / or variables by the HMI computer. As an example, to facilitate writing a value to the fieldbus device, the controller can receive a first command from the HMI computer instructing to write a value to the fieldbus device. The controller can identify the target fieldbus device and generate a second command formatted according to the fieldbus protocol based on the information included in the first command. A second command can then be communicated to the identified fieldbus device to complete the writing of the desired value.

  Also, in certain embodiments, the controller can dynamically identify fieldbus devices connected within the control system. For example, the controller may receive one or more messages, such as notification messages, from one or more individual fieldbus link devices. Each message received may include information related to multiple segments of the individual link device. Each of these segments can provide a communication channel that can connect the fieldbus device to the link device. The controller can parse or parse each received message to identify one or more of the active segments of each link device to which at least one fieldbus device is connected. The controller can then generate individual query messages for each identified active segment to request information related to one or more fieldbus devices connected to that segment. In response to communicating the inquiry message to the active segment, the controller can receive any number of responses including information related to the connected fieldbus device. If necessary, the controller can then generate and communicate individual device inquiry messages to any number of connected fieldbus devices to obtain more detailed information about the fieldbus devices. it can. As information is collected at the controller, the controller creates one or more lists of connected fieldbus devices in the control system and / or various graphic presentations associated with the connected fieldbus devices. Can do. The created list and / or presentation can then be sent to any number of suitable recipients, such as a workstation computer utilized by the operator of the control system.

  In certain embodiments, a plurality of redundant link devices can be provided to facilitate communication between the fieldbus device and the controller. For example, a primary link device and a secondary link device can be provided. The main link device can detect that the network connectivity with the controller has been lost, and can instruct switching or transition of communication control to the sub link device. In certain embodiments, the switching may be indicated based on additionally determining that network connectivity exists between the secondary link device and the external controller. As required by certain embodiments, the secondary link device can be set as the primary device after migration.

  Various embodiments of the present invention may include one or more dedicated computers, systems, and / or specific machines that facilitate synchronization of fieldbus devices and external controllers or control systems. In certain embodiments, one or more dedicated computers, systems, and / or specific machines that facilitate communication between an external computer and one or more fieldbus devices may also be provided. Also, in certain embodiments, one or more dedicated computers, systems, and / or facilitating dynamic identification of fieldbus devices connected within and / or active within the control system Or a specific machine can be provided. A dedicated computer or particular machine may include a wide variety of software modules as required in various embodiments. As described in more detail below, certain embodiments may utilize these various software components to process timing information associated with the fieldbus device and synchronize the external controller with the fieldbus device. it can.

  Certain embodiments of the present invention described herein may have the technical effect of facilitating the synchronization of fieldbus devices with external controllers or control systems. Also, certain embodiments of the present invention process data received from a fieldbus device, perform control functions for the fieldbus device, and control one or more during one operation cycle or one macrocycle of the fieldbus device. It is possible to have a technical effect of outputting a message to the fieldbus device. In this respect, the operations of the fieldbus device and the external controller can be synchronized. Also, certain embodiments of the present invention may have the technical effect of facilitating communication between an external computer such as an HMI computer associated with the control system and one or more fieldbus devices. . For example, commands received from an external computer can be processed to generate or create commands that can be communicated to one or more fieldbus devices. Indeed, certain embodiments have the technical effect of receiving commands formatted in a non-fieldbus protocol, generating commands formatted according to the fieldbus protocol, and outputting them to one or more fieldbus devices. Can do. As required, certain embodiments of the present invention described herein are technical effects that facilitate dynamic identification of fieldbus devices connected to and / or within a control system. Can also have.

  Furthermore, specific embodiments of the present invention can have the technical effect of facilitating communication between the fieldbus device and the external controller. The network connectivity between the external controller and the plurality of link devices can be monitored to facilitate switching of communication control from the first link device to the second link device. In this regard, maintaining network connectivity between the external controller and the fieldbus device even if the network connectivity with one or more link devices that facilitate communication between the controller and the fieldbus device is lost. Can do.

  Various embodiments of the present invention provide a foundation fieldbus type (hereinafter “fieldbus”) device, a control system, such as a power plant (eg, gas turbine, steam turbine, wind turbine, etc.), power plant, and / or process plant. Incorporate into the control system related to Various embodiments of the present invention can utilize a wide variety of fieldbus devices as needed. Examples of fieldbus devices include, but are not limited to, sensors, meters, measuring devices, valves, actuators, input / output subsystems, host systems, link devices, any suitable fieldbus H1 device, and / or any A suitable Fieldbus High Speed Ethernet ™ (HSE) device is included. In certain embodiments, the H1 device may operate and / or communicate at a different speed than the HSE device. As an example, an H1 device can operate at approximately 31.25 kilobits per second, and an HSE device can operate at approximately 100 megabits per second. If desired, various HSE devices such as link devices can be used to interconnect the H1 device with the central controller of the control system. Further, the term “HSE protocol” may be used to indicate a fieldbus protocol that facilitates communication with the HSE fieldbus device.

  Communication between fieldbus devices and / or between one or more controllers and / or between the control system and the processor of the fieldbus device can be facilitated by utilizing a fieldbus protocol. The fieldbus protocol is an all-digital serial, two-way communication protocol that provides a standardized physical interface to a bus or network that interconnects field devices or fieldbus devices. Fieldbus protocol is an open architecture protocol developed and managed by Foundation Fieldbus. The fieldbus protocol actually provides a local area network for field equipment or field equipment in a plant or facility, so that the field equipment performs control functions in distributed locations throughout the facility, The overall control policy can be implemented by communicating with each other before and after performing the control function. In the fieldbus protocol, control functions can be distributed throughout the process control network, reducing the workload on the central controller.

  FIG. 1 is a block diagram of one exemplary control system 100 that can be utilized in accordance with various embodiments of the invention. The control system 100 includes one or more controllers 105 (eg, a central controller) and / or control devices, one or more link devices 110a-n, and / or one or more fieldbus devices 115a-n. be able to. The controller 105 can communicate with the link devices 110a-n via one or more suitable networks 120 or communication buses. Link devices 110a-n can communicate with various fieldbus devices 115a-n via one or more suitable buses 125a-n or a network.

  Any number of link devices 110a-n can be utilized in connection with the control system 100 as needed. Link devices 110a-n may be devices capable of communicating via a fieldbus network or bus and one or more relatively high speed networks that facilitate communication with controller 105. For example, the link device (collectively referred to as link device 110) may be an HSE fieldbus device or an HSE / H1 combined device. Thus, the link device 110 can communicate with the controller 105 via a suitable Ethernet ™ network or other suitable network. Also, the link device 110 can communicate with the connected fieldbus devices 115a-n via one or more fieldbus networks and / or data buses. If necessary, link devices 110a-n can facilitate communication between controller 105 and fieldbus devices 115a-n. Alternatively, in other embodiments, the fieldbus device 115 may be in direct communication with the controller 105 via a suitable network 120 or bus 125.

  Link device 110 may comprise any number of segments and / or connections that can connect fieldbus data bus 125 or a local fieldbus network. For example, in certain embodiments, the link device 110 may comprise four segments, although other numbers of segments may be included as needed. Each segment can establish a separate communication channel and can be configured to facilitate communication between the link device 110 and a fieldbus device connected to that segment.

  In operation, the link device 110 can be configured to send or communicate a message including timing information to the controller 105. In certain embodiments, messages can be communicated periodically. The communication cycle may be a default period or a period set by one or more user preferences. Also, various suitable periods, such as a period of approximately 500 milliseconds, may be utilized as needed. In other embodiments, a message can be communicated to the controller 105 in response to a message request. In accordance with one aspect of the present invention, the communicated message may include timing information associated with a segment of link device 110 and / or a fieldbus device connected to the segment. For example, the message may include the current operating time of the segment and / or connected fieldbus device in the current macro cycle or other operating cycle. If desired, the message may include a wide variety of additional information, such as the duration of the operation cycle. Instead of receiving a message from the linking device 110, in certain embodiments of the present invention, a message may be received directly from the fieldbus device 115.

  With continued reference to FIG. 1, any number of fieldbus devices 115a-n may be utilized in connection with control system 100. In certain embodiments, each fieldbus device (collectively referred to as device 115) can communicate with link device 110 via a local fieldbus network or data bus 125. In this regard, communication between the fieldbus device 115 and the controller 105 can be facilitated by the link device 110. In other embodiments, the fieldbus device 115 can communicate directly with the controller 105. A variety of different types of fieldbus devices can be utilized, including any number of H1 fieldbus devices and / or other suitable devices, as required by various embodiments of the present invention. In certain embodiments, fieldbus devices 115a-n can be distributed or located at different points within a power plant or process plant. In this regard, fieldbus devices 115a-n can be utilized to monitor and / or control various aspects and / or operations of the plant.

  In certain embodiments, communication between link devices 110a-n and fieldbus devices 115a-n can be facilitated using a fieldbus protocol. Communication between the link devices 110a to 110n and the controller 105 can also be facilitated using a fieldbus protocol.

  According to an aspect of the present invention, the segment of the link device 110 and the fieldbus device connected to the segment can be configured to operate according to an operation cycle such as a fieldbus macrocycle. For example, a fieldbus macrocycle can define the total execution time of logic within a segment. In certain embodiments, the duration or length of the operational cycle can be configured or set by a user or technician. In other embodiments, the duration of the operating cycle can be determined and / or set dynamically. If desired, a minimum duration of an operating cycle can be defined based at least in part on the latency and / or operating speed of the slowest device connected to the target segment. Instead of setting an operation cycle for a segment of the link device 110, an operation cycle may be set in a similar manner for individual fieldbus devices or groups of fieldbus devices.

  Any number of operating cycles may be set as needed in various embodiments of the invention. For example, each operation cycle can be set for each segment of each link device 110a-n. In certain embodiments, once the set duration of the operating cycle is set or determined, the duration can be communicated to and / or stored at the controller 105.

  In certain embodiments, the fieldbus device 115 connected to the segment (or directly connected to the controller 105) is measured data, event data, and / or other suitable related to the operation of the fieldbus device 115. Data can be operable to communicate to the controller 105 or can be configured to communicate. According to one aspect of the present invention, the fieldbus device 115 can be configured to output data during a corresponding operation cycle so that the data is received and processed by the controller 105 during the same operation cycle. . Data can also be output so that control signals or other messages related to the processing of that data by the controller 105 can be received by the fieldbus device 115 during its operating cycle. In this respect, the operations of the fieldbus device 115 and the controller 105 can be synchronized.

  With continued reference to FIG. 1, the illustrated network or networks 120 may include any suitable network or combination of networks that facilitate communication between the link devices 110a-n and the controller 105. Similarly, the fieldbus data buses 125a-n or network may be any number of suitable data buses and / or local areas that facilitate communication between the link device 110 and a fieldbus device connected to the link device 110. A network can be included. Examples of suitable networks and / or data buses include, but are not limited to, a local area network, a wide area network, the Internet, a radio frequency (RF) network, a Bluetooth ™ enabled network, a suitable wired network, a suitable network Includes a wireless network, or an appropriate combination of wired and wireless networks. In certain embodiments of the invention, such as embodiments utilizing an Ethernet network, one or more Ethernet switches can be provided. The Ethernet ™ switch can route data within the network 120. Each Ethernet ™ switch may include hardware and / or software components that can operate to facilitate the routing of data within the network 120. Examples of suitable Ethernet ™ switches include, but are not limited to, network bridges, multilayer switches, and the like.

  In various embodiments of the present invention, redundant components may be included in the network 120 and / or system 100 as desired. For example, redundant wiring, switches, and / or routers can be provided. Also, in certain embodiments, redundant link devices 110a-n and / or segments may be provided. In this respect, sufficient operation can be maintained in the control system 100 when a network device failure occurs.

  With continued reference to FIG. 1, the control system 100 may include a controller 105, such as a central controller. Some examples of suitable controllers are the Mark ™ VI control system and Mark ™ Vie control system manufactured by General Electric Company. The controller 105 may be configured to communicate with and / or control other components of the control system 100 and / or plant or system components controlled by the control system 100. Controller 105 also receives data associated with fieldbus devices 115a-n and / or link devices 110a-n and processes at least a portion of the received data and / or any number of link devices 110a-110. n and / or one or more control signals or other messages can be configured to be received by the fieldbus devices 115a-n. In accordance with one aspect of the present invention, the controller 105 is one in which received data associated with the operation of the fieldbus devices 115a-n is processed to facilitate synchronization of the fieldbus devices 115a-n and the controller 105. Or a plurality of specific times can be determined.

  The controller 105 can include any number of processor-driven devices that control the operation of the control system 100. For example, the controller 105 can include any number of dedicated computers or specific machines, application specific circuits, programmable logic controllers (PLCs), microcontrollers, personal computers, minicomputers, mainframe computers, supercomputers, and the like. . In certain embodiments, the operation of controller 105 may be controlled by computer-executed or computer-implemented instructions that are executed by one or more processors associated with controller 105. The instructions may be implemented as one or more software components as desired in various embodiments of the invention. Execution of instructions forms a dedicated computer or other specific machine capable of controlling the operation of the control system 100 and / or operating to facilitate the synchronization of the controller 105 and the fieldbus devices 115a-n. can do. One or more processors that control the operation of the controller 105 may be internal to the controller 105 and / or in communication with the controller 105 via one or more suitable networks. In certain embodiments of the invention, the operation and / or control of controller 105 may be distributed over several processing components.

  The controller 105 can include one or more processors 140, one or more memory devices 141, and one or more network interface devices 142. The one or more memory devices 141 may be any suitable memory device, such as a cache, a read-only memory device, a random access memory device, a magnetic storage device, and the like. One or more memory devices 141 may include data, executable instructions, and / or various program modules utilized by controller 105, such as control systems, link devices 110a-n, and / or fieldbus devices 115a-n. Data 145 associated with the operation, operating system 146, control module 147, synchronization module 148, communication module 149, and / or live list module 152 may be stored. The memory 141 can also present information related to the operation of the control system to the operator and / or a control system such as one or more workstations 130 from which the operator can enter user commands. It may be operative to store a fieldbus protocol or HSE protocol 150 that facilitates communication with 100 other components, and / or a second control system protocol 151. The data 145 may include appropriate data related to operation of the control system 100 and / or operation of the plant or system monitored by the control system 100, for example, measurement data, operational data, one or more links Data associated with operation of devices 110a-n, data associated with operation of one or more fieldbus devices 115a-n, one or more operations of link devices 110a-n and / or fieldbus devices 115a-n Data related to a cycle or a macro cycle can be included. An operating system (OS) 146 may include executable instructions and / or program modules that facilitate and / or control the overall operation of the central controller 105. For example, the OS 146 can facilitate execution of other software programs and / or program modules by the processor 140.

  The control module 147 may operate to monitor and / or control the overall operation of the control system 100 and / or the plant or system monitored and / or controlled by the control system 100. In doing so, the control module 147 may utilize various measurements and / or other data related to the operation of the control system 100 and / or the monitored plant or system. At least a portion of the utilized data can be received directly from the fieldbus devices 115a-n or via the link devices 110a-n. The control module 147 further operates to generate command signals related to the operation of the control system 100 and to instruct the generated signals to be communicated to other components of the control system 100, such as fieldbus devices 115a-n. be able to. For example, the control module 147 processes data received from one or more fieldbus devices 115a-n and directs the generated control signal or other message to be communicated to the fieldbus devices 115a-n. Can operate or be configured as such.

  The synchronization module 148 is or can be configured to synchronize the operation and / or processing of the controller 105 and fieldbus devices 115a-n. In accordance with one aspect of the present invention, the synchronization module 148 allows the control signals and other messages generated and / or output by the controller 105 to be fielded during one or more applicable current operating cycles of the fieldbus device. Identify one or more specific times for the controller 105 to perform control functions and / or processes for one or more individual fieldbus devices and / or groups of fieldbus devices, as received by the bus device can do.

  In one exemplary embodiment, the synchronization module 148 may be in one fieldbus device 115 or a group of fieldbus devices, such as a group of fieldbus devices connected to the same segment of the link device 110 or the same data bus 125. Relevant timing information can be received. Various embodiments of the present invention can receive a wide variety of timing information as required. In one exemplary embodiment, information related to the current time in the current operating cycle or macrocycle may be received. In another exemplary embodiment, information related to the start time of the current operating cycle may be received. In a specific embodiment, the timing information can be received in a synchronization message or a timing message output from the link device 110 or the fieldbus device 115. For example, the link device 110 can output a timing message or a synchronization message including its own timing information for each segment of the link device 110. In certain embodiments, timing messages or synchronization messages can be output periodically to be received by the controller 105 as needed. That is, the link device 110 or the fieldbus device 115 can be configured to output timing data periodically at a predetermined interval or time. For example, the timing data can be output at or near the beginning of an operating cycle or macrocycle, as received by the controller 105.

  When timing information for a segment or fieldbus device 115 is received, the synchronization module 148 may utilize that timing information to determine the start time of the current operating cycle associated with the segment or device 115. it can. For example, the synchronization module 148 may determine from a current time (eg, clock time) associated with the controller 105 to a timing value included in the timing information (eg, a value representing the current time within an operating cycle), and as needed. By subtracting the estimated network delay time, the start time of the current operating cycle can be determined. The synchronization module 148 may also access or obtain information related to the operating cycle of the segment or device 115, such as the duration of the operating cycle. For example, the synchronization module 148 can access duration data in appropriate memory associated with the controller 105. As another example, the synchronization module 148 may identify received timing information or duration information included in another received message.

  Once the start time of the operating cycle is determined, the synchronization module 148 determines the determined start time for the segment or fieldbus device 115 to determine the specific time at which the control module 147 should perform the controller function. And the duration information of the operation cycle can be used. For example, a timing offset for executing the controller function or a specific clock value for executing the controller function can be determined. The specific time determined is such that a control signal or other message output from the controller 105 is received by the fieldbus device 115, segment, and / or device connected to the segment during the current operating cycle. It can be the time at which the control action of the segment or device 115 takes place. In this respect, the operation of the fieldbus devices 115a to 115n connected to the operation of the controller 105 can be synchronized. Further, a difference in operation speed between the controller 105 and the connected fieldbus devices 115a to 115n can be taken into consideration. When the determined specific time is reached, the control module 147 may perform controller functions on the fieldbus device 115, the segment, and / or devices connected to the segment. In doing so, the control module 147 processes the input (eg, measurement data, event data, etc.) received from the segment and / or fieldbus device 115 and / or to the fieldbus device 115, segment, and / or segment. Any number of suitable control signals and / or other messages can be generated for output to connected devices. The control module 147 can then instruct the generated signal and / or message to be sent to a designated recipient.

  Examples of operations that can be performed by the synchronization module 148 to synchronize the controller 105 and the fieldbus devices 115a-n will be described in more detail below with reference to FIG.

  The communication module 149 may operate to format and / or generate communications sent over the network 120 and / or communications sent to the workstation 130. The communication module also receives communications sent to the central controller 105, for example, communications received from the workstation 130, link devices 110a-n, and / or fieldbus devices 115a-n, and data from the received communications. Can be operable to extract and process. The communication module may utilize both a fieldbus protocol or HSE protocol 150 and / or one or more other protocols such as a control system protocol or second protocol 151 in formatting the communication. .

  According to one aspect of the present invention, the communication module 149 can be operable to facilitate communication between the workstation 130 and the fieldbus devices 115a-n. For example, the communication module 149 can be configured to receive commands associated with the fieldbus devices 115a-n from one or more workstations 130. In one exemplary embodiment, a user of workstation 130 enters and enters one or more commands related to the operation of fieldbus devices 115a-n, such as a command to change the operation mode of fieldbus device 115. The command may be communicated to the controller 105 for processing by the communication module 149 and / or the control module 147. The received command may be formatted according to a protocol other than the fieldbus protocol. When a command such as a command to read a value from the fieldbus device or write a value to the fieldbus device is received, the communication module 149 can identify the command as a command for the fieldbus device 115. For example, the communication module 149 is referenced in the variable associated with the received command or the received command by comparing the variable included in the command with the stored information associated with the variable for the fieldbus devices 115a-n. Can be identified as a variable associated with the fieldbus device 115. In one exemplary embodiment, a variable included in a received command may be used to access and / or search a variable data repository for fieldbus devices 115a-n, such as a variable lookup table or a variable database. it can. In this regard, the fieldbus device 115 associated with the received command can be identified.

  Once the fieldbus device 115 associated with the received command is identified, the communication module 149 can translate or translate the received command into a command formatted according to the fieldbus protocol. In certain embodiments, the communication module 149 can utilize at least a portion of the information included in the received command to generate a second command formatted according to the fieldbus protocol. If desired, the communication module 149 can additionally utilize a portion of the stored data 145, such as a storage memory address of a variable associated with the command, to generate a second command. For example, the generated second command may include the memory address information of the fieldbus device 115 in which the variable or parameter to be changed is stored. Once generated, the communication module 149 can instruct the second command to communicate to the identified fieldbus device 115. In this regard, the communication module 149 can function as a gateway module that facilitates communication between the non-fieldbus workstation 130 and the fieldbus devices 115a-n.

  In addition to processing commands received from workstation 130, communication module 149 and / or control module 147 receives information from fieldbus devices 115a-n and presents at least a portion of the received information to the user. It can operate to communicate to the workstation 130. For example, the fieldbus device 115 is associated with the operation of the fieldbus device 115, such as the value of one or more operating variables and / or parameters of the fieldbus device 115, measured data, calculated values, and / or other data. Information can be communicated to the controller 105. In certain embodiments, information can be communicated from the fieldbus device 115 to the controller 105 in real time or near real time. In other embodiments, information can be communicated from the fieldbus device 115 to the controller 105 periodically at appropriate predetermined time intervals. In other embodiments, information can be communicated from the fieldbus device 115 to the controller 105 in response to a request for information, such as a request or command to read the value of an operating variable associated with the fieldbus device 115. In still other embodiments, the field based on the trigger event being identified by the fieldbus device 115, such as a change in the identified operating variable or a determination that the measurement is outside a threshold or threshold range. Information can be communicated from the bus device 115 to the controller 105. Communication from the fieldbus device 115 to the controller 105 can be formatted according to a fieldbus protocol.

  Once received, at least a portion of the information can be utilized by the communication module 149 to generate a message formatted according to a protocol other than the fieldbus protocol (eg, EGD protocol). Then, the communication module 149 can instruct to output the generated message to communicate with the workstation 130. In this regard, information received from the fieldbus device 115 can be translated or translated into a protocol or language associated with the workstation 130 and communicated to the workstation 130 for display to the user. Then, the user of the workstation 130 can determine whether or not a change in the operation of the fieldbus device 115 is requested by looking at the displayed information. If a change is required, the user can utilize the workstation 130 to communicate commands to the controller 105 as described in more detail above.

  For examples of operations that can be performed by the communication module 149 to facilitate communication between the workstation 130 and one or more fieldbus devices 115a-n, see below with reference to FIGS. More in detail.

  The live list module 152 may operate to dynamically generate and / or maintain a list of link devices 110a-n, segments, and / or fieldbus devices 115a-n connected within the control system 100. . In certain embodiments, live list module 152 generates and / or updates a list of devices based on receipt of individual notification messages or status messages from various link devices 110a-n and evaluation of the received messages. Can be operable. For example, a newly connected and / or disconnected device can be identified by comparing a received notification message with a previously received notification message. In this regard, in certain embodiments of the invention, a list of connected devices is maintained in near real time. An example of operations that can be performed by the live list module 152 to generate a list of connected fieldbus devices 115a-n and dynamically maintain and / or update the list is described below with reference to FIGS. Will be described in more detail. In addition to generating and / or maintaining a list of connected devices, the live list module 152 can generate a wide variety of presentations associated with the connected devices, such as a graphical display and / or a graphical user interface. If necessary, the live list module instructs one or more receiving devices, such as workstation 130, to communicate the generated list and / or presentation for display to an operator of control system 100. be able to.

  With continued reference to FIG. 1, the network interface device 142 may facilitate connection of the controller 105 to the network 120 and / or workstation 130. Network interface device 142 may include any number of input / output cards (eg, Ethernet cards) and / or other devices that facilitate network communication.

  In certain embodiments of the invention, one or more workstations 130 may be provided. If desired, these workstations 130 can provide a human machine interface (HMI) between the control system 100 and one or more operators of the control system 100. For example, the workstation 130 can facilitate receiving user input and / or user commands related to the operation of the control system 100. The workstation 130 may also be configured to receive data from the controller 105, such as presentations and / or other information related to the connected fieldbus devices 115a-n. The workstation 130 can be further configured to display at least a portion of the received data to the user via a suitable display device such as a monitor. In this regard, various data values related to the operation of the fieldbus devices 115a-n can be communicated to the workstation 130 and displayed to the user.

  In certain embodiments, workstation 130 may facilitate receiving user input associated with commands communicating to fieldbus device 115. For example, a command to write a value to the memory of the fieldbus device 115 may be input to the workstation 130 and / or generated by the workstation 130. Commands entered or generated can be communicated from the workstation 130 to the controller 105. The controller 105 can process the received command and facilitate communication of the command to the fieldbus device 115. In a specific embodiment, the controller 105 receives a command formatted according to a non-fieldbus protocol, generates a command formatted according to the fieldbus protocol using the received command, and sends the generated command to the fieldbus device 115. Can be output as received. In this regard, the controller can facilitate communication between the workstation 130 and the fieldbus devices 115a-n. For example, the controller 105 may facilitate reading values from the fieldbus devices 115a-n and / or writing values to the fieldbus devices 115a-n by the workstation 130.

  The workstation 130 may include one or more suitable computers or computing devices, such as a personal computer, handheld computing device, minicomputer, etc. The workstation 130 may also include one or more suitable network connections, such as a direct link or direct connection, a local area network, a wide area network, the Internet, a radio frequency (RF) network, a Bluetooth ™ compatible network, any Can communicate with the controller 105 via any suitable wired network or any suitable wireless network. In this regard, user commands, instructions, and / or other inputs related to operation of the control system 100 can be received at the workstation 130 and communicated to the controller 105. Also, the controller 105 communicates to the workstation 130 for output and / or display to the user of control system 100 and / or output data related to the operation of the plant or other system monitored by the control system 100. Can do.

  If desired, embodiments of the present invention can include a control system 100 with more or fewer components than those shown in FIG. The control system 100 of FIG. 1 is provided as an example only.

Fieldbus Synchronization FIG. 2 is a flowchart of an exemplary method 200 for synchronizing a fieldbus device and an external control system, according to an exemplary embodiment of the present invention. The method 200 may be performed by a suitable controller associated with the control system, such as the controller 105 associated with the control system 100 of FIG. The method can begin at block 205.

  At block 205, any number of fieldbus devices and / or link devices may be initialized, such as fieldbus devices 115a-n and / or link devices 110a-n shown in FIG. Further, communication between the fieldbus device and / or the link devices 110a to 110n and the controller 105 can be established.

  At block 210, a timing message or a synchronization message may be received. For example, a timing message that includes timing information for one or more segments associated with the link device 110 may be received from the link device 110. As another example, a timing message can be received directly from the target fieldbus device 115. Although certain embodiments of the present invention may include one or more fieldbus devices that communicate directly with the controller 105, the remainder of the method 200 of FIG. 2 communicates with the controller 105 via the link device 110. A description will be given in relation to a fieldbus device for communication. Various embodiments of the present invention can receive a wide variety of timing information, such as the start time of the current operation cycle of the segment or fieldbus device 115 and the current time of the current operation cycle, as needed.

  At block 215, one or more target segments or links associated with the link device may be identified based on information included in the received timing message. For example, one or more segments of the linking device 110 that are in operation and / or one or more segments of the linking device 110 to which at least one fieldbus device is connected may be identified. The operation then proceeds to block 220 where the next segment can be identified for processing.

  At block 225, operational cycle information for the segment may be accessed or otherwise obtained. For example, operational cycle information can be obtained by accessing a memory or obtained from an external data source. As another example, the operating cycle information for a segment can be identified or analyzed from a received timing message and / or another received message. A wide variety of information related to the operating cycle of the segment can be accessed or obtained, such as the duration or length of the operating cycle of the segment.

  At block 230, the start time of the current operating cycle of the segment may be determined or identified based on information included in the received timing message. For example, the start time of the current operation cycle is determined from the current time (eg, clock time) associated with the controller 105, the timing value included in the timing message (eg, a value representing the current time within the operation cycle), and as needed. And subtracting the estimated network delay time. As another example, the start time of the current operating cycle can be determined by identifying start time information included in the timing message.

  At block 235, the determined start time and duration of operation cycle information to determine a specific time for the controller function to be performed by the controller 105 for the segment and / or a fieldbus device connected to the segment. Can be used. For example, a timing offset for executing the controller function or a specific clock value for executing the controller function can be determined. The specific time required is determined so that the control signal or other message output from the controller 105 is received by the segment and / or a device connected to the segment during the current operating cycle or the current macro cycle. And / or the time during which the control action on the device is performed. In this respect, the operation of the controller 105 and the operation of the segment can be synchronized.

  At block 240, a determination can be made as to whether the current segment is the last available segment. If block 240 determines that the current segment is not the last available segment of link device 110, operation proceeds to block 220 where the next segment can be identified for processing. On the other hand, if block 240 determines that the current segment is the last available segment, operation can proceed to block 245.

  At block 245, controller functions for the segment and / or connected fieldbus devices may be performed. For example, upon reaching a particular time required for a segment, the controller 105 can perform controller functions on that segment and / or devices connected to that segment. In doing so, the controller 105 processes inputs (eg, measurement data, event data, etc.) received from the segment and / or connected fieldbus device and / or to the segment and / or connected fieldbus device. Any number of suitable control signals and / or other messages can be generated for output. Controller 105 can then instruct the designated recipient to communicate the generated signal and / or message.

  Method 200 may end after block 245.

  The method 200 shown in FIG. 2 describes an iterative method for processing the segments associated with the linking device 110 and synchronizing the controller 105 with each segment, but in certain embodiments, one or more segments are described. Can be processed in parallel. Also, if desired, the method 200 can be utilized in connection with any number of link devices.

  The operations described in the method 200 of FIG. 2 are not necessarily performed in the order shown in FIG. 2, but may be performed in any suitable order instead. Also, certain embodiments of the invention may perform more or fewer elements or operations than all the elements or operations shown in FIG.

  FIG. 3 is an illustration 300 of an example of synchronization that can be achieved by various embodiments of the present invention. As shown in FIG. 3, the embodiment of the present invention facilitates synchronization between an external controller such as the controller 105 shown in FIG. 1 and a connected fieldbus device such as the fieldbus device 115 shown in FIG. it can. By synchronizing the fieldbus device 115 and the controller, the input can be received from the fieldbus device 115 and the output can be communicated from the controller 105 to the fieldbus device 115 to be received by the fieldbus device 115 during one operation cycle or one macro cycle. Thus, the input can be processed by the controller 105. In this regard, it is possible to provide an appropriate timing between the function of the controller 105 and the function of the fieldbus device 115.

  In contrast, in the asynchronous timing method (also shown in FIG. 3), the controller controls the fieldbus device at a time such that the output control message or signal is not received by the fieldbus device during the same operating cycle. May perform the function. As a result, the fieldbus device may not be able to receive the necessary input before performing its function, thereby causing a timing error and / or a data error between the fieldbus device and the controller. In some cases, the operation of the controller may be delayed up to two operation cycles or macrocycles relative to the connected fieldbus device. Such timing errors can be reduced or eliminated by synchronizing the controller and the fieldbus device according to various embodiments of the present invention.

Fieldbus Communication FIG. 4 is a flowchart of an exemplary method 400 for communicating commands received from an external computer to a fieldbus device, according to an exemplary embodiment of the invention. The method 400 may be performed by a suitable controller associated with the control system, such as the controller 105 associated with the control system 100 of FIG. The method may begin at block 405.

  At block 405, commands related to operation of the control system 100 may be received from a human machine interface (HMI) computer, such as one of the workstations 130 shown in FIG. The command may be received via any number of suitable networks and / or network connections, such as via a network similar to network 120 described above with reference to FIG. The received command may be formatted according to a protocol other than the fieldbus protocol. For example, in certain embodiments, the received command may be formatted according to the EGD protocol or another suitable protocol.

  At block 410, a determination may be made as to whether the command is for a fieldbus device, such as one of the fieldbus devices 115a-n shown in FIG. In certain embodiments, the information contained in the command can be analyzed to determine whether the command is a command for the fieldbus device 115. For example, a device identifier included in the command can be identified and it can be determined whether the device identifier is associated with the fieldbus device 115. As another example, a variable or parameter included in or identified by a command can be analyzed to determine whether the variable is associated with the fieldbus device 115. For example, a variable included in a command can be used to access or search a database or lookup table that includes variables associated with any number of fieldbus devices 115a-n. Based on the identification of the match, the fieldbus device 115 associated with the variable can be identified. If block 410 determines that the command is not a command for fieldbus device 115, method 400 may end. On the other hand, if it is determined at block 410 that the command is for the fieldbus device 115, the operation can proceed to block 415 and the fieldbus device 115 associated with the command can be identified. For example, the device identifier or variable included in the command can be used to identify the fieldbus device 115 associated with the command.

  At block 420, a fieldbus command for the identified fieldbus device 115 may be generated based on the command received from the HMI computer. For example, information included in the received command and / or storage information associated with a variable or parameter identified by the received command (for example, an identifier of the fieldbus device 115, a storage location of the fieldbus device 115 associated with the variable, etc. ) Can be used to generate fieldbus commands formatted according to the fieldbus protocol. In this regard, commands received from the HMI computer can be converted or translated into commands formatted according to the fieldbus protocol.

  At block 425, the generated fieldbus command can be output for communication to the fieldbus device 115. For example, fieldbus commands can be communicated directly to fieldbus device 115. As another example, fieldbus commands can be communicated to link device 110 for delivery to fieldbus device 115.

  The method may end after either block 410 or 425.

  A wide variety of commands can be received from the HMI computer and processed by the controller 105 and / or the communication module 149. An example of a suitable command that can be processed is a command that writes a value to the fieldbus device. FIG. 5 is a flowchart of an exemplary method 500 that facilitates an external computer to write a value to a fieldbus device, in accordance with an exemplary embodiment of the present invention. The method 500 may be performed by a suitable controller associated with the control system, such as the controller 105 associated with the control system 100 of FIG. The method may begin at block 505.

  At block 505, a command to write a value to a fieldbus device such as fieldbus device 115 shown in FIG. 1 may be received from a human machine interface (HMI) computer such as one of workstations 130 shown in FIG. The command may be received via any number of suitable networks and / or network connections, such as via a network similar to network 120 described above with reference to FIG. The received command may be formatted according to a protocol other than the fieldbus protocol. For example, in certain embodiments, the received command may be formatted according to the EGD protocol or another suitable protocol.

  At block 510, a variable or parameter associated with the received write command may be identified. For example, a variable or parameter for which a value is required to be written can be identified. At block 515, a determination can be made as to whether the fieldbus device 115 is identified based on the variable. For example, using a variable, a reference table or database of variables associated with the fieldbus devices 115a to 115n is searched or accessed, and if a match is found, it is determined that the variable is associated with the fieldbus device 115. can do. If block 515 determines that there is no fieldbus device identified by or associated with the variable, the operation can end. On the other hand, if it is determined at block 515 that the fieldbus device 115 is identified by the variable or the fieldbus device 115 is associated with the variable, the operation can proceed to block 520.

  At block 520, a determination can be made as to whether writing to the identified variable is allowed or permitted. In certain embodiments, it can be determined whether the HMI computer has permission or access to write a value to the identified variable. For example, stored information associated with write permissions and / or access rights can be examined to determine whether writing to the identified variable is possible or permitted. If it is determined that writing to the variable identified at block 520 is not permitted, the operation can end. On the other hand, if it is determined at block 520 that writing to the variable is permitted, the operation can proceed to block 525.

  At block 525, the fieldbus protocol may be used to generate a second write command for the variable. If desired, the generation of the second write command can be based on a command received from the HMI computer. For example, a fieldbus write command can be generated using information included in the received write command. If necessary, storage information associated with the identified variable or parameter, for example, an identifier of the fieldbus device 115, and / or a storage location or memory address of the fieldbus device 115 in which the value of the variable is stored. A fieldbus write command can be generated using this. In this regard, commands received from the HMI computer can be converted or translated into commands formatted according to the fieldbus protocol.

  At block 530, the generated fieldbus write command can be output for communication to the fieldbus device 115. For example, a fieldbus write command can be communicated directly to the fieldbus device 115. As another example, fieldbus commands may be communicated to link device 110 and delivered to fieldbus device 115.

  Embodiments of the present invention can facilitate the HMI computer writing values to a wide variety of variables or parameters associated with the fieldbus device 115. For example, embodiments of the present invention can facilitate writing a value in an operating mode or operational mode associated with the fieldbus device 115. In this respect, the operation mode of the fieldbus device 115 can be set using the HMI computer. For example, the operating mode can be set to one of a manual operating mode, a sleep operating mode, an automatic operating mode, or another suitable operating mode.

  At block 535, which may not be essential in certain embodiments of the invention, information related to the operation of the fieldbus device 115 may be received by the controller 105. For example, measurement data and / or data related to the value of one or more variables and / or parameters of the fieldbus device 115 can be received. The received information may be formatted according to the fieldbus protocol.

  At block 540, which may not be essential in certain embodiments of the invention, a message may be generated for output to the HMI computer utilizing at least a portion of the received information. For example, a message including the updated variable value that has been written can be generated. The generated message can be formatted according to a protocol other than the fieldbus protocol, such as the EGD protocol. Once generated, a message may be output for communication to the HMI computer at block 545 and / or for presentation to a user of the HMI computer. In this respect, the controller 105 can function as a gateway device that facilitates communication between the fieldbus device 115 and the HMI computer.

  Although communication from the fieldbus device 115 to the HMI computer is described in FIG. 5 as being performed after writing to the variable associated with the fieldbus device, in certain embodiments of the invention, instead, Alternatively or in addition, information and / or measurement data associated with the variable value may be communicated to the HMI computer prior to receiving a command to write the value to the fieldbus device 115.

  The method may end after any of blocks 515, 520, or 545.

  The operations described in the methods 400, 500 of FIGS. 4 and 5 need not necessarily be performed in the order shown in FIGS. 4 and 5, but may be performed in any suitable order instead. Also, certain embodiments of the present invention may perform more or fewer elements or operations than all of the elements or operations shown in FIGS.

  4 and 5 describe the reception of commands to fieldbus devices 115a-n, but perform similar operations as necessary to send commands to one or more link devices 110a-n. Can be received and processed.

Fieldbus Device Identification FIG. 6 is a flowchart of an exemplary method 600 for identifying a fieldbus device in a control system, according to an illustrative embodiment of the invention. The method 600 may be performed by a suitable controller associated with the control system, such as the controller 105 associated with the control system 100 of FIG. The method may begin at block 605.

  At block 605, connecting and / or initializing one or more link devices and / or fieldbus devices associated therewith, such as link devices 110a-n and fieldbus devices 115a-n, to control system 100. Can do. For example, any number of fieldbus devices 115a-n, such as H1 devices, may be connected to the link device 110 via a suitable fieldbus data bus and / or other suitable network connection. The link device 110 (which may be a suitable H1 / HSE device) can then be connected to the central controller 105 of the control system 100 via any number of suitable network connections. When the link devices 110a to 110n are connected to the controller 105, each link device 110a to 110n can periodically communicate a notification message or a status message to the controller 105. If necessary, the period for communicating the notification message can be set with various user parameters, and various timer periods can be used according to various embodiments of the present invention. The message can be used to generate and / or dynamically update the list of link devices 110a-n and fieldbus devices 115a-n connected to the controller 105.

  At block 610, the next link device 110 may be selected from a group of one or more link devices 110a-n connected to the controller 105. For example, the next link device 110 may be selected from a group of one or more link devices 110a-n that have communicated their notification message to the controller 105. At block 615, a notification message received from the selected link device 110 may be identified. In certain embodiments, the identified notification message is for later use in detecting changes in connected fieldbus devices 115a-n, as described in more detail below with reference to FIG. Can be remembered.

  The notification message received for the selected link device 110 may include a wide variety of information related to one or more segments of the link device 110. Each segment can be a branch of the link device 110 or a communication branch that facilitates communication between the link device 110 and any number of fieldbus devices 115a-n. For example, each segment can be connected to a fieldbus data bus or local network that facilitates communication between the link device 110 and the various fieldbus devices 115a-n. In certain embodiments, one link device 110 may include four segments, but a link device may comprise any number of segments. The notification message may include a wide variety of information related to the link device segment. For example, the notification message may include a version number or other identifier for each segment. In certain embodiments, the version number is the segment, an indication of whether the segment is in use, an indication of whether there are fieldbus devices connected to the segment, the number of connected fieldbus devices, and Other information can be identified as needed.

  At block 620, the received notification message may be parsed or otherwise parsed to identify active segments associated with the linking device 110. Each identified segment can then be analyzed to identify or determine individual fieldbus devices connected to the segment. At block 625, the next segment of the selected link device 110 may be identified and selected. Then, at block 630, a query message for the selected segment can be generated. With the generated inquiry message, information related to the fieldbus devices 115a to 115n connected to the segment can be requested. In various embodiments of the present invention, various information such as identifiers and / or version numbers of the fieldbus devices 115a to 115n can be requested as required. Alternatively, the inquiry message may request a standardized status message for the segment that includes information related to the fieldbus device connected to that segment. Once generated, an inquiry message can be communicated to the segment.

  At block 635, a response to the inquiry message may be received. The response can include a message identifying fieldbus devices 115a-n connected to the segment. In certain embodiments, the response may include segment identification information, an identifier for each connected fieldbus device 115, an indication of whether the fieldbus device 115 is active, and / or other associated with the fieldbus device 115. Appropriate information can be included. If desired, the received message can be parsed or otherwise parsed to identify one or more fieldbus devices 115a-n connected to the segment. Each identified fieldbus device 115 can then be analyzed to obtain additional information related to the fieldbus device 115.

  At block 640, the next fieldbus device 115 may be identified and / or selected. Then, at block 645, a device inquiry message for the selected fieldbus device 115 may be generated. The generated device inquiry message can request various types of information of the fieldbus device 115 as required in various embodiments. The information includes, but is not limited to, a device identifier and a user of the device 115. A tag, manufacturer identifier, device type, device revision identifier, device description revision, one or more functional block revisions, and / or other suitable information are included. Once generated, a device inquiry message can be sent to the fieldbus device 115 or otherwise communicated. For example, a device inquiry message can be communicated to the link device 110, and the link device 110 can communicate a device inquiry message to the fieldbus device 115.

  At block 650, a response to the device inquiry message may be received. The received response message can be generated by the fieldbus device 115 and includes a wide variety of information related to the fieldbus device 115, such as some or all of the information described above with reference to block 645. Can do. In this regard, accurate information related to the fieldbus device 115 and / or its operation can be collected by the controller 105.

  At block 655, a determination may be made as to whether the selected fieldbus device 115 is the last fieldbus device connected to the selected segment. If block 655 determines that fieldbus device 115 is not the last device connected to the segment, operation can proceed to block 640, where the next fieldbus device can be identified or selected for processing. it can. In this regard, information related to each fieldbus device connected to the segment can be collected or otherwise obtained by the controller 105. On the other hand, if it is determined that the fieldbus device 115 selected at block 655 is the last fieldbus device connected to the segment, operation can proceed to block 660.

  At block 660, a determination may be made as to whether the selected segment is the last active segment of the selected link device 110. If block 660 determines that the segment is not the last segment, operation proceeds to block 625 where the next segment can be identified or selected for processing. In this regard, information relating to each segment of the link device can be collected or otherwise obtained by the controller 105. On the other hand, if it is determined that the segment selected at block 660 is the last segment of the link device, operation can proceed to block 665.

  At block 665, a determination can be made as to whether the selected link device 110 is the last link device connected to the controller 105. If at block 665 it is determined that the linking device 110 is not the last linking device, the operation can proceed to block 610 and the next linking device can be identified or selected for processing. In this regard, information related to each connected link device 110a-n can be collected or otherwise obtained by the controller 105. On the other hand, if it is determined that the link device 110 selected in block 665 is the last link device, the operation can proceed to block 670.

  At block 670, a list of fieldbus devices 115a-n connected to and / or functioning within the control system 100 may be created or generated. The generated list can include a wide variety of information such as identification information and / or operational information for each link device 110a-n, segment, and / or fieldbus device 115a-n. In certain embodiments, one or more presentations associated with the generated list, such as one or more graphical user interfaces, can be created or generated. The presentation can provide a visual representation of the connected fieldbus devices 115a-n and / or their operation. If desired, the presentation can be formatted utilizing a variety of different techniques and / or layouts. An example presentation layout will be described in more detail below with reference to FIG.

  If necessary, the generated list and / or presentation may be transmitted or otherwise communicated from controller 105 to one or more recipients, such as one or more workstation computers 130 shown in FIG. Can do. In certain embodiments, the generated list and / or presentation can be communicated according to a protocol associated with control system 100. In this regard, the operator of the control system 100 can be provided with information related to the connected fieldbus devices 115a-n. Thus, the operator can assign one or more of the fieldbus devices 115a-n properly or accurately. Also, the operator can make any number of diagnoses on the fieldbus devices 115a-n and / or determine whether the fieldbus devices 115a-n are operating properly.

  Method 600 may end after block 670.

  The method 600 shown in FIG. 6 describes an iterative method for processing link devices and collecting information related to various link device segments and / or fieldbus devices connected to the segments. In embodiments, one or more link devices, segments, and / or fieldbus devices may be processed in parallel. For example, inquiry messages for multiple segments of a link device can be generated and / or communicated in parallel. As another example, device inquiry messages for multiple fieldbus devices connected to a segment may be generated and / or communicated in parallel.

  FIG. 7 is a flowchart of an exemplary method for updating a list of fieldbus devices in a control system, according to an exemplary embodiment of the present invention. The method 700 may be performed by a suitable controller associated with the control system, such as the controller 105 associated with the control system 100 of FIG. The method 700 may begin at block 705.

  At block 705, a point in time when a notification message or status message should be received from the linking device 110 may be identified. In a specific embodiment, a timing threshold for receiving a notification message periodically output from the link device can be specified. Based on the timing and timing threshold at which the last notification message is received from the linking device 110, the point in time when the subsequent notification message should be received can be determined. If desired, the identified time point may allow a certain amount of error in receiving the notification message, such as transmission delay, connectivity constraint error, and / or failure of the link device that outputs the message. In certain embodiments, the controller 105 may instead be configured to request a notification message from the link device 110 and determine whether a response is received.

  At block 710, a determination can be made as to whether an expected notification message has been received from the link device 110. If it is determined at block 710 that a notification message has not been received, operation can proceed to block 715 where it can be determined that the linking device 110 is no longer connected to the controller 105 and / or control system 100. The operation can then proceed to block 780, described in more detail below, and the list and / or presentation associated with the fieldbus devices 115a-n connected to the control system 100 can be updated.

  On the other hand, if it is determined at block 710 that a notification message has been received from the link device 110, the operation can proceed to block 720. At block 720, the information included in the received notification message may be compared to stored information about the notification message previously received from the link device 110. Based on the comparison, a determination can be made as to whether information related to the segment of the link device 110 has changed. For example, if there is a difference between the received notification message and the stored notification, it can be determined that the information about one or more segments of the link device 110 has changed. At block 725, it may be determined whether there is a difference between the received notification message and the information stored for the previously received notification message. If no difference is identified at block 725, operation can proceed to block 730 and it can be determined that no update is required in the list of fieldbus devices connected to the link device 110. The method may end after block 730.

  On the other hand, if a difference is identified at block 725, the operation can proceed to block 735. At block 735, the segment where the change occurred can be identified. For example, the version number of each segment can be compared to the respective version number of each stored segment. By identifying the difference between the version number received in the notification message and the stored individual version, the changed segment can be identified. Although block 735 describes identifying changes within a single segment, changes may be identified within two or more segments as well. Alternatively, the version number or other information included in the notification message may be used to identify the newly activated segment associated with the linking device 110.

  At block 740, an inquiry message may be generated and communicated to the identified segment in the same manner as described above with reference to block 630 of FIG. A determination may then be made at block 745 as to whether a response to the communicated inquiry message is received. For example, a determination can be made as to whether a response is received within a timing threshold or a predetermined time period. If it is determined at block 745 that no response is received, the operation can proceed to block 750 and determine that the segment is no longer active and / or is not connected to the controller 105 via the linking device 110. be able to. Operation can then proceed to block 780, described in more detail below, and the list and / or presentation associated with the fieldbus devices 115a-n connected to the control system 100 can be updated.

  On the other hand, if it is determined at block 745 that a response to the inquiry message has been received, operation can proceed to block 755. At block 755, the received response can be compared to stored information associated with a previously received response for the segment, such as a response stored after block 650 of FIG. Based on the comparison of block 755, the fieldbus device 115 where the change occurred can be identified. For example, the modified fieldbus device 115 can be identified by identifying the difference between the received inquiry response and the individual inquiry response stored for that segment. Although block 755 describes identifying changes within a single fieldbus device, changes may be identified within two or more fieldbus devices in a similar manner. Also, a newly activated or connected fieldbus device can be identified in a similar manner.

  At block 760, a device inquiry message for the identified fieldbus device 115 may be generated and communicated to the fieldbus device 115 in the same manner as described above with reference to block 645 of FIG. A determination can then be made at block 765 as to whether a response to the communicated device inquiry message is received. For example, a determination can be made as to whether a response is received within a timing threshold or a predetermined time period. If it is determined at block 765 that no response is received, operation can proceed to block 770 where the fieldbus device 115 is no longer active and / or is not connected to the controller 105 via the link device 110. Can be determined. Operation can then proceed to block 780, described in more detail below, and the list and / or presentation associated with the fieldbus devices 115a-n connected to the control system 100 can be updated.

  On the other hand, if it is determined at block 765 that a response to the device inquiry message has been received, operation can proceed to block 775. At block 775, the received response can be analyzed and / or otherwise utilized to identify information related to the fieldbus device 115. In this respect, a change in operation of the fieldbus device 115 can be identified. The operation can then proceed to block 780.

  At block 780, the list and / or presentation associated with the fieldbus devices 115a-n connected to the control system 100 may be updated. For example, a newly connected fieldbus device and / or a newly disconnected fieldbus device can be identified. If a link device or segment is identified as disconnected (and a redundant link device and / or segment is not available), determine that each fieldbus device connected to that link device or segment is no longer connected be able to. Also, changes in the operation of one or more fieldbus devices can be identified. Based on the identified changes, the list and / or presentation of the fieldbus device, such as the list originally generated at block 670 of FIG. 6, can be updated or revised. In this regard, a relatively accurate list of connected fieldbus devices can be dynamically maintained.

  If desired, the updated list and / or presentation can be communicated to one or more recipients, such as workstation computer 130 shown in FIG. In certain embodiments, updated information can be communicated to a recipient when a change is identified. In other embodiments, an indication that a change has occurred can be communicated to the recipient, and then the updated information can be communicated to the recipient based on receiving a request for updated information. In still other embodiments, the updated information can be communicated periodically to the recipient or can be communicated based on receiving a request for updated information.

  Method 700 may end after any of blocks 715, 730, 750, or 770.

  Although the method 700 of FIG. 7 describes the operation for a single link device 110, similar operations can be performed for other link devices 110a-n connected to the controller 105 as needed. At this point, the list of fieldbus devices 115a-n connected to the controller 105 can be dynamically determined and updated. Also, in certain embodiments, a notification message can be received from a new link device, and a list of segments and fieldbus devices associated with the link device can be determined and utilized to be connected within the control system 100. The previously generated list of linked devices 115a-n can be updated.

  The operations described in the methods 600 and 700 of FIGS. 6 and 7 are not necessarily performed in the order shown in FIGS. 6 and 7, but may be performed in any suitable order instead. Also, certain embodiments of the present invention may perform more or fewer elements or operations than all the elements or operations shown in FIGS.

  FIG. 8 is a diagram of an example of a connected fieldbus device presentation 800 that can be generated according to various embodiments of the present invention. As shown in FIG. 8, the generated presentation 800 represents link devices 110a-n, segments, and / or fieldbus devices 115a-n connected to the controller 105 and / or connected within the control system 100. A live list, or a dynamically generated list, or a graphic presentation.

  Referring to FIG. 8, an exemplary presentation 800 shows three linking devices connected to the controller 105. Two fieldbus devices are connected to the first link device, three fieldbus devices are connected to the second link device, and two fieldbus devices are connected to the third link device. By utilizing the exemplary presentation 800 of FIG. 8, a workstation user (eg, an operator of the control system 100) can identify the connected link devices 110a-n and / or fieldbus devices 115a-n. it can. In this regard, the user can assign various fieldbus devices 115a-n and / or perform various diagnostics related to the control system 100.

  The presentation 800 shown in FIG. 8 is provided as an example only. Various embodiments of the present invention can generate and / or provide a wide variety of presentations to a receiving system or device as needed. These presentations can utilize a wide variety of layouts and / or include a wide variety of information.

Redundant Link Device In certain embodiments of the present invention, a plurality of redundant link devices can be provided to facilitate communication between the fieldbus device and an external controller such as the controller 105 shown in FIG. For example, a primary link device and a secondary link device can be provided. The main link device can detect that the network connectivity with the controller 105 has been lost, and can instruct switching or transfer of communication control to the sub link device. In certain embodiments, switching may be instructed based on additionally determining that network connectivity exists between the secondary link device and the external controller. As required in certain embodiments, the secondary link device can be set as the primary device after migration.

  FIG. 9 is a block diagram of an exemplary control system 900 that can be utilized in accordance with various embodiments of the invention. The control system 900 may include one or more controllers 905 (eg, a central controller) and / or control devices, a first link device 910, a second link device 912, and / or one or more fieldbus devices 915a-. n can be included. The controller 905 can communicate with the link devices 910, 912 via one or more suitable networks 920 or communication buses. The link devices 910, 912 can also communicate with the fieldbus devices 915a-n via one or more suitable buses 925 or networks.

  Any number of link devices, including first link device 910 and second link device 912, may be utilized in connection with control system 900 as desired. Each link device may be similar to the link device 110 described above with reference to FIG. According to one aspect of the present invention, the link devices 910, 912 can provide redundant communication capabilities and / or connectivity between the controller 905 and the fieldbus devices 915a-n. For example, the first link device 910 or the main link device can control communication between the controller 905 and the fieldbus devices 915a-n connected to the main link device 910. Based on the primary link device 910 determining that network connectivity with the controller 905 has been lost, the primary link device 910 is configured to transfer communication control to the second link device 912 or the secondary link device. Can do. In certain embodiments, the transition of communication control may further be based on the primary link device 910 determining that there is still network connectivity between the secondary link device 910 and the controller 905.

  In operation, link devices, such as primary link device 910, can be configured to send or output messages such as timing messages, multicast messages, etc., to communicate to controller 905. For example, a timing message or a multicast message can be periodically output according to a predetermined or preset time interval. Various embodiments of the present invention can utilize a wide variety of time intervals, such as a time interval of approximately 500 milliseconds, if desired. In certain embodiments, the time interval can be set or established by the controller 905 or a user of the link device 910. As required in certain embodiments, the primary link device 910 may instruct the secondary link device 912 to output a second timing message. Alternatively, the sub link device 912 may be configured to periodically output the second timing message in the same manner as the main link device 910.

  After outputting the timing message, the primary link device 910 can determine whether a response to the message is received from the controller 905. For example, the link device 910 can determine whether a response is received within a certain timing threshold period or before a timer started by the link device 910 expires when the message is output. Various embodiments of the present invention can utilize a wide variety of timing thresholds and / or initial timer values as needed. If it is determined that a response has been received, the link device 910 can maintain its current operating state. On the other hand, when it is determined that a response is not received, the main link device 910 can instruct switching or transition of communication control to the sub link device 912. If necessary, the primary link device 910 can determine whether network connectivity exists between the secondary link device 912 and the controller 905 before initiating or directing the transition. For example, the primary link device 910 queries the secondary link device 912 to determine whether the secondary link device 912 has received a response to the second timing message output from the secondary link device 912 from the controller 905. Can do. Based on the response to the inquiry, the primary link device 910 may determine whether a second timing message has been output from the secondary link device 912 and / or whether a response to the second timing message has been received. it can. If it is determined that a response to the second timing message has not been received by the secondary link device 912, the primary link device 910 may not make a transition and generates an error message or network connection if necessary. Some other control action can be taken to signal that the sex has been lost. On the other hand, when it is determined that a response to the second timing message has been received by the secondary link device 912, the main link device 910 can instruct a transition of communication control to the secondary link device 912. For example, the secondary link device 912 can be designated as the new primary link device. In this regard, even when the network connectivity with the main link device 910 is lost, the network connectivity between the controller 905 and the fieldbus devices 915a-n can be maintained.

  With continued reference to FIG. 9, any number of fieldbus devices 115a-n may be utilized in connection with control system 900. In certain embodiments, each fieldbus device (collectively referred to as device 915) can communicate with one or more link devices 910, 912 via a local fieldbus network or data bus 925. In this regard, communication between the fieldbus device 915 and the controller 905 can be facilitated by one or more of the link devices 910, 912. In various embodiments of the present invention, a wide variety of types of fieldbus devices can be utilized as needed, including any number of H1 fieldbus devices and / or other suitable devices. In certain embodiments, fieldbus devices 915a-n can be distributed or located at different locations within a power plant or process plant. In this regard, the fieldbus devices 915a-n can be utilized to monitor and / or control various aspects and / or operations of the plant. In particular embodiments, communication between link devices 910, 912 and fieldbus devices 915a-n can be facilitated using a fieldbus protocol.

  With continued reference to FIG. 9, the network 920 of one or more diagrams may include any suitable network or combination of networks that facilitates communication between the link devices 910, 912 and the controller 905. Similarly, the fieldbus data bus 925 or network may be any number of suitable data that facilitates communication between the link devices 910, 912 and the fieldbus devices 915a-n connected to the link devices 910, 912. Buses and / or local area networks can be included. Examples of suitable networks and / or data buses include, but are not limited to, a local area network, a wide area network, the Internet, a radio frequency (RF) network, a Bluetooth ™ enabled network, any suitable wired network, Any suitable wireless network or any suitable combination of wired and wireless networks is included. In certain embodiments of the invention, such as embodiments utilizing an Ethernet network, one or more Ethernet switches may be provided. The Ethernet ™ switch can route data within the network 920. Each Ethernet ™ switch can include hardware and / or software components that can operate to facilitate routing of data within the network 920. Examples of suitable Ethernet ™ switches include, but are not limited to, network bridges, multilayer switches, and the like.

  With continued reference to FIG. 9, the control system 900 can include a controller 905, such as a central controller. Some examples of suitable controllers are the Mark ™ VI control system and Mark ™ Vie control system manufactured by General Electric Company. The controller 905 can be configured to communicate with and / or control other components of the control system 900 and / or plant or system components controlled by the control system 900. Controller 905 also receives data related to the operation of fieldbus devices 915a-n and / or link devices 910, 912 and processes at least a portion of the received data and / or link devices 910, 912. And / or may be configured to output one or more control signals or other messages to be received by the fieldbus devices 915a-n. The controller 905 can include components similar to those described above with reference to the controller 105 of FIG. As such, the controller 905 can include any number of processors 940, memory devices 941, and / or network interface devices 942. Memory device 941 can store a wide variety of data, such as data file 945, operating system 946, control module 947, fieldbus HSE protocol 950, and / or control system protocol 951. Each of these components can function in a manner similar to that described above with reference to FIG.

  With continued reference to FIG. 9, the primary link device 910 can include any number of processor-driven devices and / or processing components that facilitate operation of the link device 910 and / or switching or transition to the secondary link device 912. Can be included. For example, main link device 910 may include any number of dedicated processing components, computing devices, specific machines, application specific circuits, programmable logic controllers (PLCs), microcontrollers, minicomputers, and the like. In particular embodiments, the operation of main link device 910 may be controlled by computer-executed or computer-implemented instructions that are executed by one or more processors or processing components associated with main link device 910. The instructions may be implemented as one or more software components as desired in various embodiments of the invention. A dedicated computer or other specific machine capable of operating to control the operation of the primary link device 910 and / or to facilitate switching or transitioning to the secondary link device 912 with the execution of instructions. Can be formed. One or more processing components that control the operation of the main link device 910 may be incorporated into the main link device 910 and / or in communication with the main link device 910 via one or more appropriate networks. Can do. In particular embodiments of the present invention, the operation and / or control of the main link device 910 can be distributed over several processing components.

  The main link device 910 may include one or more processors 952, one or more memory devices 953, and one or more network interface devices 954 or communication interface devices. The one or more memory devices 953 can be any suitable memory device, such as a cache, a read-only memory device, a random access memory device, a magnetic storage device, and the like. One or more memory devices 953 are associated with data utilized by the main link device 910, eg, data 955 associated with the operation of the main link device 910, data associated with the controller 905, and fieldbus devices 915a-n. Data, data related to the output of timing messages, etc. can be stored. The one or more memory devices 953 can also store executable instructions and / or various program modules used by the main link device 910, such as the operating system 956 and the switching module 957. In addition, if necessary, the memory 953 is operable to store a fieldbus protocol or an HSE protocol that facilitates communication with other components of the control system 900 such as the controller 905 and fieldbus devices 915a-n. be able to. An operating system (OS) 956 may include executable instructions and / or program modules that facilitate and / or control the overall operation of the main link device 910, although not necessarily required in certain embodiments of the invention. Can be included. For example, the OS 956 can facilitate execution of other software programs and / or program modules by the processor 952.

  The switching module 957 can facilitate determining or identifying a specific time or point in time when a timing message or multicast message is output from the primary link device 910 and, if necessary, the secondary link device 112. For example, the switching module 957 can determine a predetermined time interval (eg, 500 milliseconds) at which a timing message is output, and the switching module 957 can determine that time interval to determine when the timing message is output. Can be used together with the clock signal of the link device. The switching module 957 can then instruct the controller 905 to output a timing message from the primary link device 910 and, if necessary, the secondary link device 912. The switching module 957 can then determine whether a response to the output timing message is received at the primary link device 910 and / or the secondary link device 912. These determinations will be described in more detail above, and will be described below with reference to FIG. 10, but based on these determinations, the switching module 957 should switch the communication control to the sub-link device 912. Whether it can be determined. If it is determined that the migration should be performed, the switching module 957 can instruct the switching or migration.

  Examples of operations that can be performed by the switching modules 957, 967 are described in more detail below with reference to FIG.

  With continued reference to main link device 910, network interface device 954 can facilitate connection of main link device 910 to network 920 and / or fieldbus bus 925. Network interface device 954 may include any number of input / output cards and / or other devices that facilitate network communication.

  With continued reference to FIG. 9, the secondary link device 912 may include components similar to the primary link device 910. For example, the secondary link device 912 can include one or more processors 960 or processing components, one or more memory devices 961, and / or one or more network interface devices 962 or communication interface devices. Each of these components can operate similarly to the corresponding component of the main link device 910. For example, the memory device 961 can be configured to store a data file 965, an operating system 966, and / or a switching module 967 similar to the corresponding elements of the main link device 910.

  In operation, secondary link device 912 can be configured or programmed to output timing messages or multicast messages received by controller 905. In certain embodiments, messages can be output periodically as described above with respect to main link device 910. In other embodiments, the message may be output with an instruction from the main link device 910. The secondary link device 912 can then determine whether a response to the timing message has been received from the controller 905, as described above with respect to the primary link device 910. Based on this determination, the secondary link device 912 can store an indication as to whether a response has been received. The secondary link device 912 can be further configured to receive an inquiry message from the primary link device 910 related to whether the secondary link device 912 has received a response to the timing message. An indication of whether a response has been received for the message can be communicated to the main link device 910. Alternatively, in certain embodiments, secondary link device 912 may output an indication of whether a response to the timing message has been received without receiving an inquiry message from primary link device 910. The main link device 910 can use the received instruction to determine whether to switch the communication control to the sub link device 912.

  In certain embodiments of the invention, one or more workstations 930 may be provided. If desired, those workstations 930 can provide a human machine interface (HMI) between the control system 900 and one or more operators of the control system 900. For example, the workstation 930 can facilitate receiving user input and / or user commands related to operation of the control system 900. That is, the workstation 930 can facilitate user interaction with the controller 905. In addition, the workstation 930 can be configured to receive from the controller 905 data such as presentations related to the connected fieldbus devices 915a-n. The workstation 930 can be further configured to display at least a portion of the received data to the user via a suitable display device such as a monitor. The workstation 930 can include components similar to those described above for the workstation 130 of FIG.

  If desired, embodiments of the present invention can include a control system 900 with more or fewer components than those shown in FIG. The control system 900 of FIG. 9 is provided as an example only.

  FIG. 10 is a flowchart of an exemplary method 100 that facilitates communication between at least one fieldbus device and an external controller or external control system, in accordance with an exemplary embodiment of the present invention. The method 1000 may be performed by a suitable link device such as the primary link device 910 or the secondary link device 912 shown in FIG. The method may begin at block 1005.

  At block 1005, the primary link device 910 or the first link device may be initialized. The main link device 910 can facilitate communication between any number of fieldbus devices such as fieldbus devices 915a-n shown in FIG. 9 and an external controller such as the controller 905 shown in FIG. The secondary linking device 912 or the second linking device may also be initialized at block 1005 as needed in certain embodiments. The secondary link device 912 can also facilitate communication between the fieldbus devices 915a-n and the controller 905. For example, the secondary link device 912 can provide redundant communication capability in addition to the communication capability provided by the main link device 910.

  At block 1010, the primary link device 910 can identify a specific time or point in time when a message, such as a timing message or a multicast message, is output from the primary link device 910 to communicate to the controller 905. In certain embodiments, the primary link device 910 may be configured or programmed to output timing messages periodically. For example, timing messages can be output periodically according to a predetermined time interval, such as an interval of approximately 500 milliseconds or other suitable interval. The main link device 910 can use a predetermined time interval to specify the next specific time or the next time point when the timing message is output.

  At block 1015, the primary link device 910 may output a timing message or a multicast message to communicate to the controller 905 or to be received by the controller 905. For example, the primary link device 910 can determine that the specified specific time or time point has been reached, and the primary link device 910 can output a timing message based on the determination. At block 1020, which may not be mandatory in certain embodiments of the invention, the primary link device 910 may additionally instruct the secondary link device 912 to output a timing message to be received by the controller 905. . For example, the primary link device 910 can communicate an instruction to output a timing message to the secondary link device 912. Alternatively, the sub link device 912 may be configured to periodically output a timing message in the same manner as that used for the main link device 910.

  At block 1025, the primary link device 910 may start a response timer. The response timer monitors the period during which a response to the output timing message should be received from the controller 905 to indicate that proper network connectivity has been established between the main link device 910 and the controller 905. Can be used for. In particular embodiments, the timer can be a timer that counts from approximately zero, and the value of the timer can be compared to a predetermined threshold. In other embodiments, the timer can have an initial value set to a predetermined threshold, and the timer can be configured to count down to zero. In either case, a timer can be utilized to determine whether a response to the timing message is received within a predetermined time interval or within a period associated with proper network connectivity. Various embodiments of the present invention can utilize a wide variety of time intervals or periods as needed.

  At block 1030, a determination may be made at the main link device 910 as to whether the timer has expired or whether the timer value has reached a threshold. If it is determined at block 1030 that the timer has not expired or the threshold has not been reached, operation can proceed to block 1035. At block 1035, a determination can be made as to whether a response to the output timing message has been received from the controller 905. If it is determined at block 1035 that a response has been received, operation can proceed to block 1010 above. On the other hand, if it is determined at block 1035 that no response has been received, operation proceeds to block 1030 where the main link device 910 can continue to monitor the timer.

  On the other hand, if it is determined at block 1030 that the timer has expired or the threshold has been reached, it may be determined that proper network connectivity has not been established between the main link device 910 and the controller 905. As needed, in certain embodiments, the primary link device 910 may have multiple consecutive timings, such as two messages or three messages, before determining that proper network connectivity is not available or has not been established. It can be determined that no response is received across the message. In either case, if it is determined that proper network connectivity is not available or established between the primary link device 910 and the controller 905, operation can proceed to block 1045.

  At block 1045, the primary link device 910 queries the secondary link device 912 to determine whether a response to the second timing message output from the secondary link device 912 has been received by the secondary link device 912 from the controller 905. can do. For example, the primary link device 910 may include data including an indication of whether a second timing message was output from the secondary link device 912 and / or whether a response to the second timing message was received at the secondary link device 912. An inquiry message can be generated that includes instructions for the main link device to provide. Once generated, an inquiry message can be output from the primary link device 910 for communication to the secondary link device 912. In particular embodiments, primary link device 910 may then receive a response to the inquiry message from secondary link device 910. Instead of querying the secondary link device 912, the primary link device 910 determines whether an indication has been received from the secondary link device 912 regarding whether a response to the second timing message was received at the secondary link device 910. Can do.

  At block 1050, a determination can be made as to whether the secondary link device 912 has received a response to the second timing message from the controller 905. For example, it is determined whether information related to the second timing message has been received from the secondary link device 912 and / or whether the received information indicates that a response to the second timing message has been received. can do. At this point, it can be determined whether network connectivity is established between the secondary link device 912 and the controller 905. If it is determined at block 1050 that the secondary link device 912 has not received a response to the second timing message, the operation can be terminated without switching the communication control to the secondary link device 912. Also, if necessary, the main link device 910 can take one or more control actions to signal that the network connectivity between the controller 905 and the fieldbus devices 915a-n has been lost. . For example, the primary link device 910 may be received by another device, such as a controller 905, a workstation 930, and / or a mobile device associated with a power plant or process plant operator or manager. Alternatively, multiple network connectivity error messages can be output.

  On the other hand, if it is determined at block 1050 that the secondary link device has received a response to the second timing message, the operation can proceed to block 1055. At block 1055, the primary link device 910 can instruct switching or transition of communication control to the secondary link device 912. For example, the primary link device 910 can communicate to the secondary link device 912 a control signal that instructs the secondary link device 912 to take over communication control. In this regard, continuous network connectivity and / or communication between the controller 905 and the fieldbus devices 915a-n can be maintained. If necessary, the sub-link device 912 can be set as a new main link device. Then, the secondary link device 912 can perform some or all of the operations shown in the method 1000 of FIG.

  Method 1000 may end after block 1050 or 1055.

  The method 1000 shown in FIG. 10 describes a method for switching between two link devices 910, 912 that facilitates communication between an external controller 905 and one or more fieldbus devices 915a-n. In the various embodiments, any number of redundant link devices (eg, three link devices, four link devices, etc.) may be used as needed. In a specific embodiment, a similar method can be used to switch redundant segments associated with the link device 910. For example, one or more fieldbus devices 915a-n can be connected to a plurality of segments associated with the link device 910. Based on the detection that the network communication between the main segment and the fieldbus devices 915a-n is lost, the communication control can be switched or transferred to the sub-segment. In this regard, communication between the link device 910 and the fieldbus devices 915a-n can be maintained when there is a loss of network connectivity between the main segment and the fieldbus devices 915a-n.

  The operations described in the method 1000 of FIG. 10 need not necessarily be performed in the order shown in FIG. 10, and may be performed in any suitable order. Also, certain embodiments of the invention may perform more or fewer elements or operations than all the elements or operations shown in FIG.

  The present invention has been described above with reference to block diagrams and flowchart illustrations of systems, methods, apparatuses, and / or computer program products according to exemplary embodiments of the invention. It will be understood that one or more blocks of the block diagrams and flowcharts, and combinations of blocks in the block diagrams and flowcharts, can each be implemented with computer-executable program instructions. Similarly, according to some embodiments of the invention, some blocks of the block diagrams and flowcharts need not be performed in the order presented, or may not be performed at all.

  These computer-executable program instructions can be loaded into a general purpose computer, special purpose computer, processor, or other programmable data processing device to generate a particular machine, computer, processor, or other programmable The instructions executed by the processing unit form the means for implementing one or more functions noted in the blocks of the flowchart. These computer program instructions may also be stored in a computer readable memory that directs the computer or other programmable data processing device to function in a particular manner and stored in the computer readable memory. The instructions form an article of manufacture that includes instruction means for implementing one or more functions noted in the blocks of the flowchart. By way of example, embodiments of the present invention may provide a computer program product comprising a computer usable medium having computer readable program code or program instructions implemented thereon, wherein the computer readable program code is executed into a block of a flowchart. It is intended to implement one or more of the functions described. Computer program instructions may be loaded into a computer or other programmable data processing device to cause a series of operating elements or steps to be performed on the computer or other programmable device to form a computer-implemented process, Instructions executed on other programmable devices provide elements or steps that implement the functionality described in the blocks of the flowchart.

  Accordingly, the blocks in the block diagrams and flowcharts support combinations of means for performing the functions described therein, combinations of elements or steps for performing the functions described, and program instruction means for performing the functions described. Each block of the block diagrams and flowcharts, and combinations of blocks in the block diagrams and flowcharts, are represented by dedicated, hardware-based computer systems or combinations of dedicated hardware and computer instructions that perform the functions, elements or steps described therein. It will also be understood that it can be implemented.

  Although the present invention has been described in relation to the most practical matters and various embodiments at the present time, the present invention is not limited to the disclosed embodiments, and conversely, the various embodiments included within the scope of the claims. It should be understood that modifications and equivalent arrangements are intended to be included.

  This written description uses examples to disclose the invention, including the best mode, and also to enable any person skilled in the art to make and use the invention, including making and using the device or system and performing the incorporated methods. To. The patentable scope of the invention is defined in the claims, and may include other examples that occur to those skilled in the art. If such other examples have structural elements that do not differ from the literal wording of the claims, or if they contain equivalent structural elements that are only slightly different from the literal wording of the claims, then the patent It is within the scope of the claims.

100 system 105 controller 110a-n link device 115a-n fieldbus device 120 network 125a-n bus 130 workstation 140 processor 141 memory 142 network interface device 145 data file 146 operating system 147 control module 148 live list module 150 fieldbus protocol or HSE protocol 151 Control system protocol 200 method 205 block 210 block 215 block 220 block 225 block 230 block 235 block 240 block 245 block 250 block 255 block 260 block 265 block 270 block 300 method 305 block 310 block Lock 315 block 320 block 325 block 330 block 335 block 340 block 345 block 350 block 355 block 360 block 365 block 370 block 375 block 380 block 405 block 410 block 415 block 420 block 425 block 500 method 505 block 510 block 515 block 525 block 525 Block 530 Block 535 Block 540 Block 545 Block 600 Method 605 Block 610 Block 615 Block 620 Block 625 Block 630 Block 635 Block 640 Block 645 Block 650 Block 655 Block 660 Block 665 Block 670 Block Lock 700 method 705 block 710 block 715 block 720 block 725 block 730 block 735 block 740 block 745 block 750 block 755 block 760 block 765 block 770 block 775 block 780 block 800 presentation 900 control system 905 controller 910 first link device 912 first Two link devices 915a-n Fieldbus device 920 Network 925 Bus 940 Processor 941 Memory 942 Network interface device 945 Data file 946 Operating system 947 Control module 950 Fieldbus HSE protocol 951 Control system protocol 1000 Method 1005 Block 1010 Block 1015 Block 1020 Block 1025 Block 1030 Block 1035 Block 1045 Block 1050 Block 1055 Block

Claims (10)

A method (200) for synchronizing control of fieldbus devices (115a-n), comprising:
A controller (105) comprising one or more computers receives a message (210) that includes timing information about at least one fieldbus device (115) that communicates directly or indirectly with the controller (105). Steps,
Determining (230) a start time of a current operation cycle of the at least one fieldbus device (115) by the controller (105) based on information included in the received message;
Based on the start time and duration of the current operation cycle by the controller (105), a control message output from the controller (105) is transmitted during the current operation cycle to the at least one fieldbus device ( 115) determining (235) a specific time for the controller (105) to perform a control function for the at least one fieldbus device (115) as received at 115). Determining (230) the start time of the current operating cycle;
Determining a current operating time of the at least one fieldbus device based on the information included in the received message;
The method (200) of claim 1, comprising determining the start time based on the current operating time. Performing (245) the control function on the at least one fieldbus device (115) by the controller (105);
The method (200) of claim 1, further comprising: outputting (245) at least one control message for communication to the at least one fieldbus device (115) by the controller (105). Receiving (405) a first command formatted according to a protocol other than the fieldbus protocol (150) from the external computer (130) by the controller (105);
(410) determining by the controller (105) that the received command is associated with the fieldbus device (115);
Generating (420) a second command formatted according to the fieldbus protocol (150) by the controller (105) based on the determination and information contained in the received first command;
The method (200) of claim 1, further comprising: outputting (425) the generated second command by the controller (105) for communication to the fieldbus device (115). Determining (410) that the received first command is associated with the fieldbus device (115);
Identifying (510) a variable included in the received first command;
The method (200) of claim 4, comprising determining (515) that the identified variable is associated with the fieldbus device (115). Receiving (405) a first command includes receiving (505) receiving a first command that causes a value associated with the fieldbus device (115) to be written;
The method (200) of claim 4, further comprising the step of determining (520) by the controller (105) whether the external computer (130) is allowed to write to the variable. Receiving (615) at the controller (105) one or more messages from one or more individual link devices (110a-n), wherein each of the one or more messages is the individual Information relating to a plurality of segments of each of the link devices (110a-n), each of the plurality of segments comprising a communication channel to which one or more fieldbus devices (115a-n) can be connected, Steps,
The controller (105) analyzes each of the one or more received messages (620) and each individual link device (110a-110) to which one or more fieldbus devices (115a-n) are connected. n) identifying one or more of the plurality of segments;
For each one or more of the identified segments, an individual inquiry message requesting information related to the one or more fieldbus devices (115a-n) connected to the segment is sent to the controller (105). ) To generate (630),
Communicating (630) the individual inquiry message to each of the identified one or more segments by the controller (105);
Receiving (635) by the controller (105) one or more individual responses to the one or more inquiry messages, each response being connected to the segment; Including information relating to one or more fieldbus devices (115a-n);
Based on the one or more individual responses, a list of one or more fieldbus devices (115a-n) included in the control system (100) including the at least one fieldbus device 115 is The method (200) of claim 1, further comprising: (670) creating by a controller (105). Storing information associated with the one or more messages received from the one or more individual link devices (110a-n) by the controller (105);
Receiving (710) a second message containing information related to the plurality of segments of the link devices (110a-n) from one of the one or more link devices (110a-n);
Comparing (720) at least a portion of the information included in the second message with at least a portion of the stored information;
Determining, based on the comparison, that the one or more fieldbus devices (115a-n) connected to the plurality of segments of the link devices (110a-n) have changed (725); The method (200) of claim 7, further comprising: One or more fieldbus devices based on a determination that the one or more fieldbus devices (115a-n) connected to the plurality of segments of the link devices (110a-n) have changed The method (200) of claim 8, further comprising the step of updating (780) the list of (115a-n). A link device (110) facilitates communication between the controller (105) and the at least one fieldbus device (115), wherein the link device (110)
Communicating a timing message to the controller (105) (1015);
Determining whether a response to the timing message is received from the controller (105) (1035);
Based on the determination, the second link device (112) that facilitates communication between the controller (105) and the at least one fieldbus device (115a-n) is instructed to switch communication control. (1055)
The method (200) of claim 1 configured as follows.

Images