EP2730988A2 - Systeme und Verfahren zur Segmentsynchronisation - Google Patents

Systeme und Verfahren zur Segmentsynchronisation Download PDF

Info

Publication number
EP2730988A2
EP2730988A2 EP13191970.6A EP13191970A EP2730988A2 EP 2730988 A2 EP2730988 A2 EP 2730988A2 EP 13191970 A EP13191970 A EP 13191970A EP 2730988 A2 EP2730988 A2 EP 2730988A2
Authority
EP
European Patent Office
Prior art keywords
communications
macrocycle
time
segments
control system
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Withdrawn
Application number
EP13191970.6A
Other languages
English (en)
French (fr)
Other versions
EP2730988A3 (de
Inventor
John Petzen
William Pettigrew
William Galt
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
General Electric Co
Original Assignee
General Electric Co
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by General Electric Co filed Critical General Electric Co
Publication of EP2730988A2 publication Critical patent/EP2730988A2/de
Publication of EP2730988A3 publication Critical patent/EP2730988A3/de
Withdrawn legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/40—Bus networks
    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B19/00—Programme-control systems
    • G05B19/02—Programme-control systems electric
    • G05B19/04—Programme control other than numerical control, i.e. in sequence controllers or logic controllers
    • G05B19/042—Programme control other than numerical control, i.e. in sequence controllers or logic controllers using digital processors
    • G05B19/0421—Multiprocessor system
    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B19/00—Programme-control systems
    • G05B19/02—Programme-control systems electric
    • G05B19/418—Total factory control, i.e. centrally controlling a plurality of machines, e.g. direct or distributed numerical control [DNC], flexible manufacturing systems [FMS], integrated manufacturing systems [IMS] or computer integrated manufacturing [CIM]
    • G05B19/4185—Total factory control, i.e. centrally controlling a plurality of machines, e.g. direct or distributed numerical control [DNC], flexible manufacturing systems [FMS], integrated manufacturing systems [IMS] or computer integrated manufacturing [CIM] characterised by the network communication
    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B2219/00—Program-control systems
    • G05B2219/20—Pc systems
    • G05B2219/25—Pc structure of the system
    • G05B2219/25228—Scheduling communication on bus
    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B2219/00—Program-control systems
    • G05B2219/20—Pc systems
    • G05B2219/25—Pc structure of the system
    • G05B2219/25274—Communication processor, link interface
    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B2219/00—Program-control systems
    • G05B2219/30—Nc systems
    • G05B2219/31—From computer integrated manufacturing till monitoring
    • G05B2219/31121—Fielddevice, field controller, interface connected to fieldbus
    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B2219/00—Program-control systems
    • G05B2219/30—Nc systems
    • G05B2219/31—From computer integrated manufacturing till monitoring
    • G05B2219/31124—Interface between communication network and process control, store, exchange data
    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B2219/00—Program-control systems
    • G05B2219/30—Nc systems
    • G05B2219/31—From computer integrated manufacturing till monitoring
    • G05B2219/31375—LAS link active scheduler, distribute bandwidth between processing nodes
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
    • Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
    • Y02P90/02—Total factory control, e.g. smart factories, flexible manufacturing systems [FMS] or integrated manufacturing systems [IMS]

Definitions

  • the subject matter disclosed herein relates to control systems, and more specifically, to synchronizing execution of control across segments of the control system.
  • Certain systems may provide for control capabilities that enable the execution of computer instructions in various types of devices, such as sensors, pumps, valves, and the like.
  • a communications bus may be used to send and receive signals to the various devices.
  • Each device may issue inputs and/or outputs related to the device conditions and/or control logic and transmit them over the communications bus.
  • the input and/or output information may be received by a number of interested entities, including components on alternative segments of the communications bus.
  • such communications across the alternative segments may be unsynchronized, thus presenting unpredictability as to the timing relationship between the sending and/or receiving of signals across alternative segments.
  • the control system response time may include increased latency, resulting in less stable control in the control system.
  • an industrial process control system includes a first link active scheduler configured to operate on a first communications segment while a second link active schedule operates on a second communications segment.
  • the first link active scheduler is configured to schedule a first access time on the first communications segment approximately the same as a second access time on the second communications segment.
  • the first access time relates to a first field device on the first communications segment of the industrial process control system and the second access time relates to a second field device on the second communications segment of the industrial process control system.
  • a method in a second embodiment, includes obtaining, via a processor of a device on a first communications segment of an industrial control system, a reference time. The method further includes determining, via the processor, a first macrocycle duration of the first communications segment and scheduling, via the processor, a first macrocycle execution time for a first macrocycle on the first communications segment.
  • the first macrocycle execution time is approximately the same as other macrocycle execution times on other communications segments of the industrial control system when macrocycle durations of the other communications segments are approximately equal to the first macrocycle duration.
  • a non-transitory tangible computer-readable medium includes executable code.
  • the executable code includes instructions for synchronizing macrocycle execution times across multiple communications segments of an industrial process control system based upon common macrocycle durations of each of the multiple communications segments.
  • Industrial control systems may include controller systems suitable for interfacing with a variety of field devices, such as sensors, pumps, valves, and the like.
  • sensors may provide inputs to the controller system, and the controller system may then derive certain actions in response to the inputs, such as actuating the valves, driving the pumps, and so on.
  • controller systems such as the MarkTM VIe controller system, available from General Electric Co., of Schenectady, New York
  • multiple field devices may be communicatively coupled to and controlled by a controller. Indeed, multiple controllers may be controlling multiple field devices, as described in more detail with respect to FIG. 1 below.
  • the devices communicatively connected to the controller may include field devices, such as Fieldbus Foundation devices, that include support for the Foundation H1 bi-directional communications protocol. Accordingly, the devices may be communicatively connected with the controller in various communication segments, such as H1 segments, attached to linking devices, to enable a plant-wide network of devices.
  • Each field device may include computer instructions or control logic encapsulated in function blocks.
  • a proportional-integral-derivative (PID) function block may include PID instructions suitable for implementing a closed-loop control of certain processes, such as industrial processes.
  • an Analog Input (AI) function block and an Analog Output (AO) function block may be used to retrieve input data and to submit output data, respectively.
  • AI Analog Input
  • AO Analog Output
  • various types of function blocks may be provided that can include a variety of computer instructions or control logic, as described in more detail below with respect to FIG. 1 .
  • the field device may then execute the computer instructions or control logic in the function block. For example, in one implementation cycle, the AI function block's execution may occur first.
  • a "macrocycle,” as discussed herein, may refer to a cycle of scheduled function block execution, scheduled communication time, and a portion of time reserved for asynchronous communications (e.g., alerts and/or downloads) by devices on a communications segment (e.g., an H1 segment).
  • the field devices may provide a variety of information (e.g., status, alarm, and event information) to interested entities. For example, alarm viewers, redundant (i.e., backup) controllers, and others may receive alert information or other information regarding the field devices. Based upon this information, the control system may cause changes (e.g., may control) various settings or conditions of the control system.
  • these field devices may be connected to the communications bus via alternative communications segments, these macrocycle execution timings may be unsynchronized, causing an unpredictability as to when each macrocycle will execute with respect to executions on other communications segments. Thus, the control system response time may be greatly reduced, causing less stability in control of the control system.
  • Embodiments described herein enable synchronization of macrocycle execution across the multitude of segments of the control system. That is, timing signals from a controller of the control system are provided to a link active scheduler (LAS). Each LAS will start corresponding macrocycles at the same time as every other LAS with corresponding macrocycles that have the same configured macrocycle duration in the control system. Such a synchronized execution enables more predictability in relative timing of execution, enabling faster response times and more stable control of the control system.
  • LAS link active scheduler
  • FIG. 1 depicts an embodiment of an industrial process control system 10.
  • the control system 10 may include a computer 12 suitable for executing a variety of field device configuration and monitoring applications, and for providing an operator interface through which an engineer or technician may monitor the components of the control system 10.
  • the computer 12 may be any type of computing device suitable for running software applications, such as a laptop, a workstation, a tablet computer, or a handheld portable device (e.g., personal digital assistant or cell phone).
  • the computer 12 may include any of a variety of hardware and/or operating system platforms.
  • the computer 12 may host an industrial control software, such as a human-machine interface (HMI) software 14, a manufacturing execution system (MES) 16, a distributed control system (DCS) 18, and/or a supervisor control and data acquisition (SCADA) system 20.
  • HMI human-machine interface
  • MES manufacturing execution system
  • DCS distributed control system
  • SCADA supervisor control and data acquisition
  • the computer 12 may host the ControlSTTM software, available from General Electric Co., of Schenectday, New York.
  • the computer 12 is communicatively connected to a plant data highway 22 suitable for enabling communication between the depicted computer 12 and other computers 12 in the plant.
  • the industrial control system 10 may include multiple computers 12 interconnected through the plant data highway 22.
  • the computer 12 may be further communicatively connected to a unit data highway 24, suitable for communicatively coupling the computer 12 to industrial controllers 26 and 27, which may act in tandem and/or provide controller redundancy for one another.
  • the system 10 may include other computers coupled to the plant data highway 22 and/or the unit data highway 24.
  • embodiments of the system 10 may include a computer 28 that executes a virtual controller, a computer 30 that hosts an Ethernet Global Data (EGD) configuration server, an Object Linking and Embedding for Process Control (OPC) Data Access (DA) server, an alarm server, or a combination thereof, a computer 32 hosting a General Electric Device System Standard Message (GSM) server, a computer 34 hosting an OPC Alarm and Events (AE) server, and a computer 36 hosting an alarm viewer.
  • Other computers coupled to the plant data highway 22 and/or the unit data highway 24 may include computers hosting Cimplicity®, ControlSTTM, and ToolboxSTTM, available from General Electric Co., of Schenectady, New York.
  • the system 10 may include any number and suitable configuration of industrial controllers 26 and 27.
  • the system 10 may include one industrial controller 26, or two (e.g., 26 and 27), three, or more industrial controllers 26 for redundancy.
  • the industrial controllers 26 and 27 may enable control logic useful in automating a variety of plant equipment, such as a turbine system 38, a valve 40, and a pump 42.
  • the industrial controllers 26 and 27 may communicate with a variety of devices, including but not limited to temperature sensors 44, flow meters, pH sensors, temperature sensors, vibration sensors, clearance sensors (e.g., measuring distances between a rotating component and a stationary component), and pressure sensors.
  • the industrial controller may further communicate with electric actuators, switches (e.g., Hall switches, solenoid switches, relay switches, limit switches), gasifiers, gas treatment units (e.g., acid gas removal units), air separation units, compressors, steam turbines, gas turbines, heat recovery steam generators, and so forth.
  • switches e.g., Hall switches, solenoid switches, relay switches, limit switches
  • gasifiers e.g., gas treatment units
  • gas treatment units e.g., acid gas removal units
  • air separation units e.g., compressors, steam turbines, gas turbines, heat recovery steam generators, and so forth.
  • the turbine system 38, the valve 40, the pump 42, and the temperature sensor 44 are communicatively interlinked to the automation controller 26 and 27 by using linking devices 46 and 48 suitable for interfacing between an I/O NET 50 and a H1 network 52.
  • the linking devices 46 and 48 may include the FG-100 linking device, available from Softing AG, of Haar, Germany.
  • a linking device, such as the linking device 48 may be coupled to the I/O NET through a switch 54.
  • other components coupled to the I/O NET 50, such as the industrial controllers 26 and 27, may also be coupled to the switch 54.
  • data transmitted and received through the I/O NET 50 may in turn be transmitted and received by the H1 network 52, such as a 31.25 kilobit/sec network.
  • the linking devices 46 and 48 may act as bridges between the I/O Net 50 and the H1 network 52.
  • a variety of devices may be linked to the industrial controllers 26, 27 and to the computer 12.
  • the devices such as the turbine system 38, the valve 40, the pump 42, and the temperature sensor 44, may include industrial devices, such as Fieldbus Foundation devices that include support for the Foundation H1 bi-directional communications protocol.
  • a Fieldbus Foundation power supply 53 such as a Phoenix Contact Fieldbus Power Supply available from Phoenix Contact of Middletown, PA, may also be coupled to the H1 network 52 and may be coupled to a power source, such as AC or DC power.
  • the power supply 53 may be suitable for providing power to the devices 38, 40, 42, and 44, as well as for enabling communications between the devices 38, 40, 42, and 44.
  • the H1 network 52 may carry both power and communications signals (e.g., alert signals) over the same wiring, with minimal communicative interference.
  • the devices 38, 40, 42, and 44 may also include support for other communication protocols, such as those included in the HART® Communications Foundation (HCF) protocol, and the Profibus National Organization e.V. (PNO) protocol.
  • HCF HART® Communications Foundation
  • PNO Profibus National Organization e.V.
  • Each of the linking devices 46 and 48 may include one or more segment ports 56 and 58 useful in segmenting the H1 network 52.
  • the linking device 46 may use the segment port 56 to communicatively couple with the devices 38 and 44
  • the linking device 48 may use the segment port 58 to communicatively couple with the devices 40 and 42.
  • Distributing the input/output between the devices 38, 44, 40, and 42 by using, for example, the segment ports 56 and 58, may enable a physical separation useful in maintaining fault tolerance, redundancy, and improving communications time.
  • additional devices may be coupled to the I/O NET 50.
  • an I/O pack 60 may be coupled to the I/O NET 50.
  • the I/O pack 60 may provide for the attachment of additional sensors and actuators to the system 10.
  • the linking devices 46 and 48 may also provide additional functionality, such as maintaining a link active scheduler (LAS) 61 and a live list 63 of field devices 38, 40, 42, and 44, as described in more detail below with respect to FIG. 2 .
  • the live list 63 may be stored on a memory of the linking devices 46 and 48.
  • the live list 63 includes the list of all devices currently communicatively coupled to the system 10.
  • the embodiments described herein may provide for such synchronization.
  • Such synchronization may be useful, for example, because with unsynchronized H1 segments, it may be impossible to predict when each segment will execute with respect to the other segments within the system.
  • the total system response to a signal from the field by the controller may include unnecessary latency.
  • the response may take up to approximately 2.5 macrocycles of elapsed time. Such latency may result in an increased system response time that is slower and provides less-stable control than a control system with time synchronization across segments.
  • the devices 38, 40, 42, and 44 may provide data, such as alerts, status, or condition data, to the system 10. Timing synchronization of the provision of this data by the devices 38, 40, 42, and 44 on separate segments may be handled in accordance with the embodiments described below.
  • FIG. 2 depicts a block diagram of an embodiment of the industrial process control system 10 depicting various components in further detail. Multiple controllers, such as the controllers 26 and 27, may be set up for redundant operations. That is, should the controllers 26 become inoperative, the controller 27 may take over and continue operations.
  • the controllers 26 and 27 are coupled to the unit data highway 24.
  • the controllers 26 and 27 may each include a memory 86 and a processor 88 for executing the functions of the controllers 26 and 27.
  • the controllers 26 and 27 may execute a Fieldbus process 90 and an alarm process 91.
  • the Fieldbus process 90 may be used to interface with the field devices 38, 40, 42, and 44.
  • the controllers 26 and 27 may be coupled to the I/O pack 60 over the I/O NET 50.
  • the I/O pack 60 may communicate with the controllers 26 and 27 using the advanced digital logic (ADL) protocol.
  • ADL advanced digital logic
  • the controllers 26 and 27 may be coupled to linking devices 46 and 48 through an I/O NET 50.
  • the linking devices 46 and 48 may communicate with the controllers 26 and 27 over the I/O NET 50.
  • the linking devices 46 and 48 may be coupled to the H1 network 52, and one linking device 46 may be coupled to devices 38 and 44 and another linking device 48 may be coupled to device 40 and 42.
  • the linking device 46 may include a memory 92, such as volatile and non-volatile memory, and the processor 94, and the linking device 48 may include a memory 96, such as volatile and non-volatile memory, and a processor 98.
  • the linking devices 46 and 48 may communicate with the controllers 26 and 27 using the Fieldbus Foundation protocol.
  • a master linking device such as the linking device 46, other linking devices (e.g., linking device 48), or any other fieldbus devices may include a LAS 61.
  • the LASs 61 found on these devices may schedule the execution of function blocks (e.g., the AI function blocks, PID, and AO function blocks discussed above) as part of the management of the macrocycle. Additionally, the LASs 61 may periodically issue a token, such as a pass token, to each of the field devices 38, 40, 42, and 44.
  • the field devices 38, 40, 42, and 44 that properly respond to the pass token may be kept in the live list 63. Any field device 38, 40, 42, and 44 not responding to the pass token may be removed from the live list 63.
  • the live list 63 is kept updated by maintaining a list of communicatively responsive field devices 38, 40, 42, and 44.
  • the live list 63 may be advantageously used to maintain consistency of status and alert information, even in circumstances where one or more of the field devices 38, 40, 42, and 44 may have been disconnected, as described in more detail below with respect to FIG. 5 .
  • the LAS 61 may grant permission for each communication occurring over the H1 segments.
  • only one device e.g., 38 or 40 and 42 or 44
  • the LASs 61 may ensure that each field device 38, 40, 42, and 44 is given time to communicate control data, alarms, etc. through the H1 segments to the controllers 26 and 27.
  • FIG. 3 illustrates a process for synchronizing macrocycle execution over multiple segments of the control system 10.
  • FIG. 4 illustrates a simplified representation of the control system 10 of FIGS. 1 and 2 to provide a more clear picture of the process 200. For clarity, FIGS. 3 and 4 will be discussed together.
  • the process 200 may be implemented as non-transitory computer readable instructions that instruct one or more processors of the LASs 61.
  • Execution synchronization may enable the synchronous and asynchronous portions of the macrocycles from different H1 segments 52 to occur at the same time. By providing more precision in macrocycle execution start times, the end times are more predictable. For example, in control systems where the execution is not synchronized across H1 segments 52, the total system response time (e.g., the sum of the control response time, field device sensing time, and control actuation time) may take up to approximately 2.5 macrocycles of elapsed time to occur. On the other hand, when the synchronization techniques described herein are implemented, the worst-case system response time may be 1 macrocycle, resulting in greater stability for the loops controlled by Foundation Fieldbus devices.
  • the total system response time e.g., the sum of the control response time, field device sensing time, and control actuation time
  • the worst-case system response time may be 1 macrocycle, resulting in greater stability for the loops controlled by Foundation Fieldbus devices.
  • a synchronized time may be obtained from the control system 10 (block 202 of FIG. 3 ).
  • the controllers 26 and 27 of FIG. 2 may provide a synchronized time to the LASs 61 on each H1 segment 52.
  • the synchronized timings may be implemented according to standard timing protocols.
  • the precision time protocol PTP
  • the timing may be within 20-40 milliseconds of precision amongst the clocks (e.g., the LASs 61) of the control system 10.
  • a controller e.g., 26 or 27
  • the grandmaster is responsible for providing a timing reference 204 ( FIG. 4 ) to clocks in the control system.
  • each H1 segment 52 may include an LAS 61.
  • Each of the LASs 61 may obtain a timing reference 204, which helps ensure that each of the LASs 61 are working off of the same reference time.
  • the LASs 61 may take into account and compensate for network latency.
  • the synchronized time may remain consistent between clocks in these H1 segments.
  • the LASs 61 may determine the macrocycle execution duration for each of the H1 segments 52 (block 206 of FIG. 3 ). Each H1 segment executes on a deterministic length of time from the start of the segment.
  • the macrocycle duration may determined based upon function block execution times, transmission times of cyclic messages, gaps between messages determined by network parameter, time reserved for acyclic messages, etc.
  • the LASs 61 may work together to schedule synchronized execution of macrocycles on H1 segments 52 with similar macrocycle durations (block 208 of FIG. 3 ).
  • each LAS 61 may maintain a link active schedule, which may provide a schedule of times in the macrocycle for devices (e.g., 38, 40, 42, and/or 44) to publish their output values on the Fieldbus.
  • the link active schedules may be coordinated amongst the LASs 61, such that each macrocycle with a common duration will begin execution at the same time, according to the reference timing.
  • the LASs 61 would create a link active schedule that executes these macrocycle executions at approximately the same time (e.g., within 20-40 milliseconds) based upon the synchronization time. If the control system 10 included additional H1 segments with other macrocycle durations (e.g., 640 milliseconds) then the 320 millisecond segments would be scheduled to start at approximately the same time as one another and the 640 millisecond segments would be scheduled to start approximately the same time as one another.
  • additional H1 segments with other macrocycle durations e.g., 640 milliseconds
  • the LASs 61 may begin granting bus utilization permission in the control system 10 according to the link active schedule (block 210 of FIG. 3 ).
  • the LASs 61 determine whether there may be sufficient time to carry out unscheduled or lower priority items before the next scheduled data execution (decision block 212). When there is not enough time to carry out these items, the LASs 61 may wait or idle until the next schedule execution time occurs (block 214). In some scenarios, one or more idle messages may be provided by the LASs 61, to indicate that the bus has been idled until the proper execution time occurs. This may help to ensure that other devices of control system 10 do not assume that the LASs 61 have failed (e.g., is no longer properly scheduling communications) merely because the LASs 61 are waiting for the proper execution time.
  • the scheduled communication is implemented (block 216 of FIG. 3 ).
  • the LASs 61 may provide a compel data (CD) token 220 ( FIG. 4 ) to the device (e.g., 38, 40, 42, and/or 44) that is scheduled to have access to the bus at the execution time.
  • the publishing device Upon receiving the CD token 220, the publishing device immediately sends its data to one or more subscribing devices. From there, the LASs 61 repeat the bus grant process (block 210 of FIG. 3 ).
  • lower priority or unscheduled communications may be enabled by the LASs 61 (block 218).
  • the LASs 61 may provide a Pass Token (PT) 222 between devices (e.g., 38, 40, 42, and/or 44) of the control system 10, may provide a Time Distribution (TD) 224, and/or may provide a Probe Node (PN) 226.
  • the PT 222 may be provided in a round-robin fashion (e.g., equal sharing in a defined sharing order) between devices on segments 52, to authorized unscheduled activities by these devices.
  • devices 38 and 40 may receive one PT 222 that is shared in a round-robin fashion, while devices 42 and 44 may receive another PT 222 shared in a similar round-robin fashion.
  • the TD 224 may provide a control command to synchronize all clocks of devices (e.g., 38, 40, 42, and/or 44) on an H1 segment 52.
  • the PN 226 may be provided by the LASs 61 on an H1 segment 52 to identify any new devices on the bus. Once the unscheduled or low priority commands are complete, the LASs 61 repeat the bus grant process (block 210 of FIG. 3 ).
  • the active link schedule may change or the clock time of the LASs 61, over time, may diverge from the reference time. Accordingly, the synchronization time may be obtained periodically (e.g., time interval), to ensure that the LASs 61 retain the proper reference time. Further, the macrocycle durations may be determined (block 206) as new devices come online and the scheduling (block 208) may be altered as devices come online or go offline.
  • an LAS 61 may fail, creating a need for a new LAS 61 to permit access of the bus to devices of the control system 10.
  • a link master or non-transitory computer implemented instructions, may instruct a device of the control system 10 to maintain a copy of the link active schedule.
  • the link master may monitor communications on the bus and determine when an LAS 61 fails (e.g., by determining that an LAS 61 has not granted bus access rights to a device for a certain period of time). As discussed above, the LAS 61 may provide an idle notification to the link master, to ensure that there are no false positives regarding the failure determination.
  • the link master may assume the scheduling role, activating its copy of the link active schedule for future access grants.
  • the link master becomes the new LAS 61, it synchronizes its clock with the grandmaster, ensuring that the new LAS 61 executes segments with like macrocycle durations at approximately the same time.
  • FIG. 5 illustrates a macrocycle 250 where execution of controller code relating to fieldbus devices is executed after the scheduled portion of the macrocycle.
  • the macrocycle 250 may include all of the scheduled function block execution in the H1 devices on a segment (portion 252 of the macroblock 250).
  • the macroblock 250 may include an allotment of time for scheduled communications or other functional block executions (portion 254 of the macroblock 250).
  • a reserved portion 256 may be used for asynchronous communications, such as alerts and/or downloads).
  • Controller code relating to the fieldbus devices may be synchronized to occur after the scheduled portion of the macrocycle 250 (e.g., portions 252 and 254). Accordingly, this code may be executed during the reserved portion 256 of the macrocycle 250, as illustrated by block 258.
  • inputs from the multiple segments of the system may be collected. This collected input data may enable execution of sometimes complicated control algorithms in the controller, with the ability to update outputs at the start of a succeeding macrocycle, as illustrated by the virtual communications resources (VCRs) 260.
  • VCRs virtual communications resources
  • extended macrocycle durations may be reduced. For example, in traditional systems, scheduled macrocycle time is used for executing function blocks in the devices. Control strategies that include multiple function blocks in the same device, with VCRs to other devices, may result in longer macrocycle times than the current embodiments that execute controller logic after the schedule portions of the macrocycle 250. Additionally, in contrast to traditional systems that promote control in the field, which are limited by the set of function blocks described in the Fieldbus standard; complicated and/or higher-order control is possible using the restricted function block capability described in the Fieldbus standards.

Landscapes

  • Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Automation & Control Theory (AREA)
  • General Engineering & Computer Science (AREA)
  • Manufacturing & Machinery (AREA)
  • Quality & Reliability (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Programmable Controllers (AREA)
  • Small-Scale Networks (AREA)
  • Synchronisation In Digital Transmission Systems (AREA)
EP13191970.6A 2012-11-08 2013-11-07 Systeme und Verfahren zur Segmentsynchronisation Withdrawn EP2730988A3 (de)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
US13/672,618 US20140126583A1 (en) 2012-11-08 2012-11-08 Systems and Methods for Segment Synchronization

Publications (2)

Publication Number Publication Date
EP2730988A2 true EP2730988A2 (de) 2014-05-14
EP2730988A3 EP2730988A3 (de) 2017-10-25

Family

ID=49554064

Family Applications (1)

Application Number Title Priority Date Filing Date
EP13191970.6A Withdrawn EP2730988A3 (de) 2012-11-08 2013-11-07 Systeme und Verfahren zur Segmentsynchronisation

Country Status (2)

Country Link
US (1) US20140126583A1 (de)
EP (1) EP2730988A3 (de)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105179215A (zh) * 2015-07-02 2015-12-23 合肥轩明信息科技有限公司 一种基于modbus通信的现代水泵控制系统
EP3148904A4 (de) * 2014-06-02 2018-03-07 ATS Automation Tooling Systems Inc. System und verfahren zur verfolgung eines beweglichen elements in einem linearen motorfördersystem

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10142199B2 (en) * 2014-12-19 2018-11-27 Emerson Process Management Lllp Automatic process data transmission and monitoring for an industrial process network
US10571880B2 (en) 2017-09-20 2020-02-25 General Electric Company System and method for synchronization of device communication
CN112558505A (zh) * 2019-09-10 2021-03-26 阿里巴巴集团控股有限公司 工控系统的控制处理方法、装置、工控系统及电子设备

Family Cites Families (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6285966B1 (en) * 1998-06-25 2001-09-04 Fisher Controls International, Inc. Function block apparatus for viewing data in a process control system
US6742136B2 (en) * 2000-12-05 2004-05-25 Fisher-Rosemount Systems Inc. Redundant devices in a process control system
DE10113261C2 (de) * 2001-03-16 2003-07-10 Siemens Ag Synchrones, getaktetes Kommunikationssystem mit dezentralen Ein-/Ausgabe-Baugruppen und Verfahren zur Einbindung dezentraler Ein-/Ausgabe-Baugruppen in ein solches System
DE10120558A1 (de) * 2001-04-26 2002-10-31 Siemens Ag Verfahren und Vorrichtung zum Steuern und/oder Regeln von über ein gemeinsames Feldbussystem an eine Steuer- und/oder Regelungsvorrichtung angekoppelten Einrichtungen
US7904184B2 (en) * 2004-11-23 2011-03-08 Rockwell Automation Technologies, Inc. Motion control timing models
US8005553B2 (en) * 2006-09-29 2011-08-23 Fisher-Rosemount Systems, Inc. Automatic configuration of synchronous block execution for control modules run in fieldbus networks
US7616565B2 (en) * 2007-02-26 2009-11-10 Raytheon Company Network communication scheduling
US7831411B2 (en) * 2007-05-25 2010-11-09 Rockwell Automation Technologies, Inc. Diagnostic tool for retroactive assessment of industrial process performance
US7590511B2 (en) * 2007-09-25 2009-09-15 Rosemount Inc. Field device for digital process control loop diagnostics
WO2010107441A1 (en) * 2009-03-20 2010-09-23 Innovative Wireless Technologies, Inc. Distributed ad hoc mesh network protocol for underground mine and hazardous area communications
US8340790B2 (en) * 2009-08-31 2012-12-25 Fisher-Rosemount Systems, Inc. Methods and apparatus to adjust control loop timing in a process control system
US8229578B2 (en) * 2009-09-21 2012-07-24 Fisher-Rosemount Systems, Inc. Methods and apparatus to manage module run sequences in a process control environment
US8510463B2 (en) * 2010-04-21 2013-08-13 General Electric Company Systems and methods for facilitating communication with a fieldbus device
US8352641B2 (en) * 2010-04-21 2013-01-08 General Electric Company Systems and methods for identifying fieldbus devices in a control system
US9197576B2 (en) * 2010-11-15 2015-11-24 Rockwell Automation Technologies, Inc. Method and apparatus for allocating and prioritizing data transmission
US8977372B2 (en) * 2011-05-12 2015-03-10 General Electric Company System and method for cycle time visualization
US8797884B2 (en) * 2012-06-27 2014-08-05 Nxp B.V. Network communication apparatus, system and method

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
None

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3148904A4 (de) * 2014-06-02 2018-03-07 ATS Automation Tooling Systems Inc. System und verfahren zur verfolgung eines beweglichen elements in einem linearen motorfördersystem
CN105179215A (zh) * 2015-07-02 2015-12-23 合肥轩明信息科技有限公司 一种基于modbus通信的现代水泵控制系统

Also Published As

Publication number Publication date
US20140126583A1 (en) 2014-05-08
EP2730988A3 (de) 2017-10-25

Similar Documents

Publication Publication Date Title
EP3462257B1 (de) Steuerungssystem und steuerungsvorrichtung
EP2730988A2 (de) Systeme und Verfahren zur Segmentsynchronisation
Sehr et al. Programmable logic controllers in the context of industry 4.0
CN111034128B (zh) 控制系统以及控制装置
US10761884B2 (en) Control device for operating multiple types of programs in different execution formats
EP3026515B1 (de) Programmierbares steuerungssystem
US11977362B2 (en) Control device and distributed control system
US9405644B2 (en) Redundant automation system
US20220147022A1 (en) Control system
US8375237B2 (en) Systems and methods for synchronization of an external control system with fieldbus devices
EP3851925A1 (de) Steuerungssystem und steuerungsvorrichtung
JP2020021341A (ja) 冗長化システム
CN102621897B (zh) 用于无冲突地将设备从待机模式转换到运行模式的方法
CN111052012B (zh) 控制装置以及控制系统
US10571880B2 (en) System and method for synchronization of device communication
CN116490829A (zh) 用于控制具有控制冗余的自动化系统的方法以及自动化系统
CN111052683B (zh) 网络系统
JP2013033374A (ja) 分散型監視制御システム
JP7231073B2 (ja) 制御装置および制御システム
Witte et al. Opportunities for Industrial Control
KR102123941B1 (ko) Profinet 시스템 및 profinet 시스템에 대해 보조적인 제2 시스템을 특징으로하는 자동화 시스템 및 그 통신 방법
CN115199472A (zh) 一种风力发电机组双冗余电控系统及其控制方法
EP2929646A1 (de) Bewegungssteuerungssystem mit asynchroner kommunikation und steuerung und verfahren dafür

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20131107

AK Designated contracting states

Kind code of ref document: A2

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

AX Request for extension of the european patent

Extension state: BA ME

PUAL Search report despatched

Free format text: ORIGINAL CODE: 0009013

AK Designated contracting states

Kind code of ref document: A3

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

AX Request for extension of the european patent

Extension state: BA ME

RIC1 Information provided on ipc code assigned before grant

Ipc: G05B 19/042 20060101ALI20170919BHEP

Ipc: G05B 19/418 20060101AFI20170919BHEP

Ipc: H04L 12/40 20060101ALI20170919BHEP

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

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

18D Application deemed to be withdrawn

Effective date: 20180426