CN205281229U - Control of process mill and/or controlgear - Google Patents

Abstract

The utility model relates to control of process mill and/or controlgear. In an embodiment, process control equipment has the control of a plurality of and preset mill and/or monitors relevant module. Provide program flow control routine in order to be used for monitoring multiple modules.

Description

Process plant monitoring and/or operating device

Point case application of the application to be the applying date be on July 31st, 2012, the application number patent application that to be 201220384091.X, practical New Name be " process plant is monitored and/or operating device ".

Technical field

It relates to apply the program flow control of (being called " module ") here for monitoring software, these software application are by performed by the plurality of devices used in modern process and manufacture factory. More specifically, it relates to program flow control monitoring routine, it with detection module mistake and takes the specific action of suitable factory for multiple module.

Background technology

Nowadays, process and all respects uses department of computer science that manufactures that factory runs in almost factory unify the monitoring based on microprocessor and Controlling System. Independent department of computer science unifies the monitoring based on microprocessor and Controlling System stores multiple module, and when it is operated, it realizes the operation of factory's many aspects. The scope of the concrete function of any given module is from monitoring and controls the on-the-spot equipment of independent factory to promotion operation and maintenance activity, provides data to for management report.

Comprise the on-the-spot equipment based on microprocessor-based control routine and become common. Many times, any given on-the-spot device processes device sequentially performs some modules. Independent on-the-spot equipment often comprises embedded system. Any given embedded system stores and performs multiple and that specific factory monitors and/or controlling functions is relevant module. Such as, the liquid level that a given digital device controller can be configured in control tank. Controller can have the input from tank level indicator and the output to Valve controlling device. Digital device controller performs one or more module, and the control of these modules exports, and exceedes with the level fluctuation in tank or correspondingly opens or closes valve lower than during the liquid level expected. Any given on-the-spot equipment, no matter be sensor (i.e. liquid level sensor) or performer (i.e. Valve controlling device) self can be a digital device, it is designed to perform one or more module, such as, simulated data is converted into the module of numerical data. Many times, any given on-the-spot device processes device performs the module relevant to function, and the scope of these functions is from the Communications routines between treater and I/O mouth to the routine of the numeral for the analogue value is converted into this value.

Factory's operation and maintenance computer system also often performs a lot of modules. When performing operation and maintenance routine on a corresponding treater, for factory personnel provides and independent shop equipment interaction capabilities. Additionally, factory management computer system often performs multiple module. When performing managing computer system routine on a corresponding treater, provide service data and associated report for factory personnel.

Known program flow control monitoring routine needs the storer of extra nearly 2MB to store all relevant data. Except the size of program flow control module self, required memory size depends on that the size of complete embedded firmware and needs control the quantity of the module monitored by program flow. Program flow control monitoring routine is that module is specific. Many times, storer is limited in embedded systems. Typically, before correspondingly starting to perform, program flow control module determines to need the quantity of monitored module. Once the quantity needing detected module determines, the distribution of corresponding storer has just set. It is thus desirable to provide a kind of program flow control monitoring routine, its need little storer and its can monitor multiple module.

Practical novel content

Known program flow control monitoring routine needs the storer of extra nearly 2MB to store all relevant data. Except the size of program flow control module self, required memory size depends on that the size of complete embedded firmware and needs control the quantity of the module monitored by program flow. Program flow control monitoring routine is that module is specific. Many times, storer is limited in embedded systems. Typically, before correspondingly starting to perform, program flow control module determines to need the quantity of monitored module. Once the quantity needing detected module determines, the distribution of corresponding storer has just set. It is thus desirable to provide a kind of program flow control monitoring routine, its need little storer and its can monitor multiple module.

In an embodiment, process plant monitoring and/or operating device comprise the controller being configured to receive at least one input and produce at least one output. The monitoring of this process plant and/or operating device also comprise the computer-readable medium for storing at least one module. Program flow of the present disclosure control monitoring routine operationally in dynamically determine to need the quantity of monitored module, and correspondingly increase or reduce the distribution of corresponding storer. Controller is configured to execution module further, to realize monitoring and/or controlling functions during the course. Process plant monitoring and/or operating device also comprise the program flow control monitoring routine stored on a computer-readable medium, when performing this program flow control monitoring routine, when its detection any mistake relevant with module and offer instruction detect the time stamp of any mistake. Program flow control monitoring routine comprises interface routine, performs this interface routine when any module mistake being detected, and this interface specific alarm of routine initializes factory and/or action.

Having the program flow control monitoring routine such as described modular design makes module monitors routine can reuse from module to module. Therefore, proportionally to the registered quantity that need to monitor module program flow control monitoring routine to upgrade. This is very useful for the embedded system with a large amount of module of limited storer and storage and execution.

Accompanying drawing explanation

Fig. 1 shows the block diagram of factory's supervision and control and data collecting system;

Fig. 2 shows the layout drawing in process plant piece region;

Fig. 3 A-3D shows the output of the on-the-spot equipment of multiple numeral;

Fig. 4 A-4C shows the input of the on-the-spot equipment of multiple numeral;

Fig. 5 shows the block diagram of a digital on-the-spot equipment;

Fig. 6 shows one for monitoring the OMD of management;

Fig. 7 comprises table 1, and table 1 explains the function relevant with given class variable;

Fig. 8 shows the order registering security function/thread/function in order to monitor;

Fig. 9 shows and nullifies the order of security function/thread for removing from monitoring;

Figure 10 shows security function/thread/functional order;

Figure 11 shows the monitoring of interpretive routine current control and the precedence diagram of initialize and use;

Figure 12 shows as given event sets up the schema of timing register;

Figure 13 shows for determining the whether schema in scope of given timing register cycle;

Figure 14 show watchdog routine current control monitoring routine whether undesirably run perform order; And

Figure 15 and 16 shows the routine of the module execution order for Adaptive change.

Embodiment

In an embodiment, the embedded system of a shop equipment stores and performs multiple module relevant with the specific function of various factory. Such as, program flow control monitoring routine is stored on the storer of shop equipment, any mistake when it performs on corresponding treater, in module that its detection dynamically (relevant with working time) is registered, that perform by shop equipment. This program flow control monitoring routine comprises Module registers routine, module monitors routine and interface routine. This Module registers routine is dynamically registered according to user's input in system operation time and is nullified the module of monitoring. Module monitors routine monitors any mistake of registered module and the execution of initialization interface routine when any module mistake being detected. Interface routine provides the specific alarm of factory and/or action. Therefore, monitor routine with public module and monitor all registered modules. Having the program flow control monitoring routine such as described modular design makes module monitors routine can reuse from module to module. Therefore, proportionally to the registered quantity that need to monitor module program flow control monitoring routine to upgrade. This is very useful for the embedded system with a large amount of module of limited storer and storage and execution.

When steering routine current control monitors routine, in fact execute any one in following functions: module performs monitoring, the interface of action when performing fault for module, sequence of modules is monitored, sequence of modules performs monitoring, the interface of action when performing fault for sequence of modules, monitoring is overflowed in buffer zone, the interface of action when overflowing for buffer zone, real time operating system (RTOS) (RealTimeOperatingSystem:RTOS) thread monitor, whether detection thread runs with the required time cycle, whether detection thread locks, whether detection thread runs too soon or too slow, undesirably whether detection module cycling service, motion interface during thread fault detected, above any sub-portfolio or combination.

For all modules performed in given factory system, module monitors routine can be shared. Because factory system fault actions depends on the given system that program flow control monitoring routine realizes wherein, so comprising the program flow control monitoring routine of interface routine once detect that any module mistake will the convenient factory's action shared.

Referring now to Fig. 1, factory SCADA (SupervisoryControlAndDataAcquisition: supervision and control and the data gathering) system 100 illustrated comprises some business and other computer systems, and these computer systems are controlled by one or more network of communication and some and/or monitoring equipment is interconnected. It is to be understood that this factory's SCADA system 100 has a lot of module, these modules are performed by the equipment being distributed in whole factory of as much quantity.

This factory's SCADA system 100 comprises one or more program control system 112 and 114. Program control system 112 can be a traditional program control system, such as PROVOX or RS3 system or any other DCS, this traditional program control system comprises and is coupled to controller 112B and I/O (Input/Output:I/O) blocks the operator interface 112A of 112C, controller 112B and I/O card 112C then be coupled to multiple on-the-spot equipment, that such as simulate with on-the-spot equipment 115 that is highway addressable remote transmitter (HighwayAddressableRemoteTransmitter:HART). Can being that the program control system 114 of distributed process control system comprises one or more operator interface 114A, this one or more operator interface 114A be coupled to one or more distributed AC servo system device 114B by the bus of such as industry ethernet. This controller 114B can be the DeltaV such as sold by the Fisher-Rosemount system house of Austin, Texas_TMThe controller of controller or any other type expected. This controller 114B such as, to one or more on-the-spot equipment 116, HART or Fieldbus field (FF) equipment or any other intelligence or non intelligent on-the-spot equipment, comprises such as those uses by I/O equipment connectionThe equipment of any agreement in AS interface and CAN protocol. Program flow control monitoring routine and HART, fieldbus, foundation fieldbus,It is compatible with Modbus. Known on-the-spot equipment 116 can give controller 114B provide with process variable and the information-related simulation of other equipment or the information of numeral. Operator interface 114A can store and perform process control operator that control process is run can module, it comprises control optimizer, diagnosis expert, neural network, tuner etc. Any given equipment in program control system 112,114 can comprise some modules that are that be stored on corresponding storer and that at least periodically perform by corresponding treater. Program flow control monitoring routine can be contained in any given program control system module.

The module or any other the monitoring that such as perform Asset Management Solutions (AssetManagementSolutions:AMS) can be connected to program control system 112 and 114 or single on-the-spot equipment wherein with the maintenance system of the computer 118 of the module that communicates, with putting maintenance into practice and monitor activities. Such as, maintenance calculations machine 118 can be connected to controller 112B by the communication link of any expectation or network (comprising wireless or handheld device network) and/or intercom mutually to on-the-spot equipment 115, and again arranges or implement other maintenance activity in some cases on on-the-spot equipment 115. Similarly, the maintenance module of such as AMS module can be arranged in distributed process control system 114 and perform by one or more user interface 114A relevant with distributed process control system 114, with putting maintenance into practice and monitoring function, comprise the data gathering relating to on-the-spot equipment 116 running status. Any given maintenance system can comprise program flow control monitoring routine.

Factory's SCADA system 100 also comprises multiple rotating machinery 120, such as turbine, motor etc., these are connected to maintenance calculations machine 122 by some permanent or interim communication links (such as bus, radio communication system or be connected to the handheld device that equipment 120 carrys out reading and remove subsequently). Maintenance calculations machine 122 can store and perform known monitoring and diagnosis module 123, the RBMwareTM such as sold by the CSI system house of Knoxville, Tennessee or any other is for diagnosing, monitor and optimize the known module of the running status of rotating machinery 120. Maintenance personnel often uses module 123 to go the performance safeguarding and supervising rotating machinery 120, determines the problem of rotating machinery 120, and determines whether and when rotating machinery 120 must keep in repair or change. Any one rotating machinery module can comprise program flow control monitoring routine.

Factory's SCADA system 100 also comprises generating and power distribution system 124, it has the generating relevant with factory and distribution equipment 125, this generating and distribution equipment 125 are connected to another computer 126 by such as bus, and it runs and supervises this generating and the operation of distribution equipment 125. Computer 126 can perform the known power control such as provided and diagnosis module 127 by such as Liebert and ASCO or other companies, to control and to safeguard this generating and distribution equipment 125. Generating and distribution equipment store and performs multiple module. Any one generating and distribution EM equipment module can comprise program flow control monitoring routine.

Computer system 130 is provided, it is connected to the computer relevant to the multiple functional system in process plant 100 or interface communicatedly, comprises process control function 112 and 114, such as those maintenance function realized in computer 118,114A, 122 and 126 and business functions. specifically, computer system 130 is connected to traditional program control system 112 and the maintenance interface 118 relevant to this Controlling System, the process control being connected to distributed process control system 114 and/or maintenance interface 114A communicatedly by bus 132, is connected to rotating machinery maintenance calculations machine 122 and generates electricity and distribution computer 126. local area network (LAN) that is that bus 132 can use any expectation or that be applicable to or Wide area network (WAN) agreement are to provide communication. as shown in Figure 1, computer 130 is also connected to business system computer by same or different network-bus 132 and safeguards planning computer 135 and 136, it can perform such as Enterprise Resources Planning (EnterpriseResourcePlanning:ERP) module, material resource planning (MaterialResourcePlanning:MRP) module, Computerized maintenance management system (ComputerMaintenanceManagementSystems:CMMS), adjust, produce and client's ordering system module, safeguard planning system module or any other business module expected, such as component, stock and starting material order module, production scheduling module etc. computer 130 can also be connected to the local area network 137 of whole factory, the Wide area network 138 of company and to computer system 140 by such as bus 132, and this computer system 140 makes factory to carry out from long-range position remote monitoring or communicates with factory becoming possibility. any one computer system module can comprise program flow control monitoring routine.

Further provide the example of the multiple equipment in process plant, these device storage and the multiple module of execution, Fig. 2 shows exemplary figure display 200, it can be provided by graphic user interface (GraphicalUserInterface:GUI), with to user report status information and enable running status and the performance of the system in user real-time analysis factory. As shown in Figure 2, given process can comprise motor, compressor, thermostatic regulator, valve, setter, equipment that wheel box is relevant to concrete process with other. The given factory system illustrated have one pair of tank 210,240, multiple temperature transmitter 221,251, pressure unit 222,252, flow transmitter 223,253 etc. and pipeline, all these can be interconnected as shown in Figure 2. Any given digital device controller module can comprise according to program flow of the present utility model control monitoring routine.

It is to be understood that, any given factory system can comprise on-the-spot equipment, these on-the-spot equipment relate to water spray, long-range pump, moving track car, rotary reactor, water source/heat exchanger, temperature analysis/tank liquid level, total production marks head, engine exhaust, benzene tank, turbine unit, pump vibrates, rotary lime kiln, filter stoppage detects, safety shower, water source is safeguarded, mobile/interim network, refinery manages, roll bearing, hot well tank, river (around), steam cracker, the use of the water after process, filtration condition, tubing system, source pressure, remote tank, cold-box, compressor air, mobile operator, compressor, steam line, steam distribution circuit, rotate aluminum oxide kiln, application in power industry, storage tank supervisory system, pipeline circuit, hand valve, fuel system, interim device, combustion chamber wall, long-range tank, temperature (criticized) by resin, NO_xThe Production Flow Chart of discharge, mobile water source test macro, strainer leak stopping/vapor stream, heat trnasfer, net control bridge joint, air compressor, coker, hair oil, blast furnace hearth, gaseous equilibrium/water source and Control for Kiln Temperature. Can comprise according to program flow described in the utility model control monitoring routine about any module of given monitoring and/or operating device. About the equipment about factory, other examples of storing and performing multiple module, Fig. 3 A-3D shows the on-the-spot equipment relevant to the control of factory. These equipment can be configured to activate by the output from the digital device controller such as illustrating with reference to Fig. 5 and describing.

Fig. 3 A shows on-the-spot equipment 300a, and it comprises linear valve 305a, digital valve controller 310a and linear valve actuator 315a. Fig. 3 B shows on-the-spot equipment 300b, and it comprises changeover valve 305b, digital valve controller 310b and changeover valve actuator 315b. Fig. 3 C shows on-the-spot equipment 300c, and it comprises pump 305c, digital motor/pump controller 310c and motor (tractor) 315c. Fig. 3 D shows on-the-spot equipment 300d, and it comprises the first tractor 305d, numeral tractor controller (not shown) and the 2nd tractor 315d. It is to be understood that any given on-the-spot equipment can be configured to the process control actuator relevant with factory real time execution. Any given factory monitoring EM equipment module can comprise program flow control monitoring routine.

Example that further relate to process plant, that store and perform multiple module equipment, Fig. 4 A-4C shows and monitors relevant on-the-spot equipment to factory. These equipment can be configured to by the input monitoring of the digital device controller such as illustrated with reference to Fig. 5 and describe. Fig. 4 A shows on-the-spot equipment 400a, and it comprises temperature sensor 405a and digital temperature monitor/controller 410a. Fig. 4 B shows on-the-spot equipment 400b, and it comprises liquid level sensor 405b and digital liquid level monitor/controller 410b. Fig. 4 C shows on-the-spot equipment 400c, and it comprises Ph sensor 405c and numeral Ph monitor/controller 410c. It is to be understood that any given on-the-spot equipment can be configured to the process monitoring/controller relevant with process plant real time execution. Any given factory monitoring EM equipment module can comprise program flow control monitoring routine.

Referring now to Fig. 5, show digital device controller 500. Digital device controller stores and performs the control to relevant on-the-spot equipment and/or monitors the main frame of relevant module. Digital device controller 500 comprises treater 510, discrete input 515, analog input 520, discrete output 525, modulating output 530, storer 535, short range field communications module 540, remote scene communication module 555 communicate with remote scene antenna 560. Short range field communications module 540 comprises digital circuit 545 and short range on-scene communication antenna 550. Usually, the main frame of treater 510, storer 535 and relevant module is embedded system timing. Program flow control monitoring routine described by the utility model is particularly suitable for expecting to have the embedded module of low storer and high performance. It is to be understood that any given on-the-spot equipment shown in Fig. 3 A-3D and 4A-4C can comprise the digital device controller comprising embedded system, this embedded system performs the module monitored by program flow control monitoring routine. It will be appreciated by those skilled in the art that, store in various shop equipment and perform there is multiple single module.

Program flow control monitoring routine can be designed as module execution working time monitoring routine, and it has the module error-detecting of the free stamp of band. When it is write with C++, program flow control monitoring routine can be used in any module, and especially useful for the module write with C++. Action when it is write with C++, when C encapsulation (C-wrapper) can be used for fault. Consequently, it is desirable to less memory spending, each monitors module 32 byte. Corresponding program flow control monitoring routine does not need to use outside storer (namely using storage inside device) to provide the time to stab.

The program flow control monitoring routine write with C++ can realize at module therein. Given module can be designed to detection module mistake and take action, and need not depend on peripheral equipment/interface. Corresponding program flow control monitoring routine can to design towards object programming (ObjectOrientedProgramming:OOP) concept. Therefore, the amendment of monitoring mechanism is completed by adding/remove the attribute of monitoring (Monitor) class. In at least one embodiment, program flow control monitoring routine is towards object programming design, can reuse N time so that it performs monitoring for different modules. For providing for performing making an immediate response of fault with the interface routine of other application communications.

Reference Fig. 6, program flow control monitoring routine 600 comprises module monitors management routine 605 and the module list 610 treating to monitor by module monitors management routine 605. As shown in Figure 6, routine CMonitorMgr uses routine CCirDLinkList class to create module list to be monitored. Routine CMonitorMgr is independent of real time operating system (RTOS) (RTOS) function. Routine CMonitorMgr does not use the application programming interfaces of any real time operating system (RTOS) to obtain the information of the thread about monitoring. Routine CMonitorMgr605 and routine CMonitor_TimeMinMax615 all uses routine CSisTime class 620 renewal time stamp in each execution of program flow control monitoring routine. The time stamp upgraded is relevant with any module mistake detected.

With further reference to Fig. 6 and additionally with reference in the figure 7 as the table 1 shown in element 700, it provides the explanation 710 of function 705, function 705 by routine CMonitorMgr605,720 and routine CMonitor_TimeMinMax class 615,715 provide. Variable m_bEnabledMonitoring625 remains vacation, until routine CMonitor_TimeMinMax receives first time renewal by routine TriggerTime () 719. After receiving first time renewal, variable m_ulLastTriggerTime will be updated and variable m_bEnabledMonitoring will be written as very, and routine CMonitorMgr will check threshold time limit. Also not activating if monitored when routine CMonitorMgr calls inspection, so will not implement threshold time inspection. Routine CMonitorMgr can be configured in interrupt level or thread-level with the periodic time to run. The module that any plan is monitored by routine CMonitorMgr will call Register () 721. This most at last module be added into the circulation bidirectional chain table variable m_LIST_monitor725 of routine CMonitorMgr. Program flow of the present disclosure control monitoring routine operationally in dynamically determine to need the quantity of monitored module, and correspondingly increase or reduce the distribution of corresponding storer.

Any given module, thread or function are about monitoring only to be registered once. If attempting to attempt second time Module registers, so routine CMonitorMgr can not register this module and return negative response for the request received. Fig. 8 and 9 respectively illustrates the orders registering 800 and cancellation 900 monitoring from routine CMonitorMgr. In order to remove module, thread or function from routine CMonitorMgr, routine CMonitor_TimeMinMax object reference routine Unregister () 722. For the received cancellation from monitoring, if having found this module, thread or function in routine CMonitorMgr, so routine CMonitorMgr removes this module from list and returns response certainly. If not finding this module, thread or function items when nullifying, so the request received will be sent negative response by routine CMonitorMgr.

Figure 10 shows precedence diagram 1000, and it has the details of the execution about routine CMonitorMgr class 1005. CMonitorMgr carrys out working procedure current control monitoring routine periodically to plan. This CMonitorMgr execution time interval according to system from a few microsecond by several seconds not etc., and can be configured on system operation time. Use wheel to ask and/or interrupt time-out and run the periodic inspection to each registered module under routine CMonitorMgr class. When receiving time-out event 1010, routine CMonitorMgr starts to monitor registered thread, function or module.

Figure 11 illustrates the execution 1100 of program flow control monitoring routine. If variable " Limit " is beyond the maximum restriction configured or falls under the minimum limit of configuration, so will call interface routine DevExecutionFailure () and take the specific alarm of factory and/or action. This alarm and/or action can be rewritten by equipment development person, to give equipment specific action. When not needing minimum limit to check, m_ulMimTimeLimit will be set to NO_LIMIT_CHECK, can not check lower limit to show. Similarly, this can be applied to maximum time restriction.

Figure 12 shows schema 1200, it illustrates when TriggerTime () class receives the routine performed when calling from just monitored module. The timing register based on interruption shown in schema 1200 can be used to examine whether CMonitorMgr self performs correctly. Routine starts from starting block 1205. Block 1210 is implemented the determination of the active program current control monitoring to whether. If have activated, block 1215 obtaining the snapshot (snapshot) of current time, in block 1215, calculates the time of disappearance subsequently. Block 1225 being determined, whether this is perform the first time after being reset from this routine. If it does, so obtain the minimum time value from triggering the time in block 1230 last time. If, so in block 1235, mark "true" is not distributed to reset after first time perform relevant variable. Block 1240 is implemented from once trigger the time the calculating of maximum time value, subsequently before this routine terminates in block 1250, by the upper set of time that once triggers for equaling current time in block 1245. If CMonitorMgr self in execution, so will not call security function to be set in a safe condition by corresponding plant processes.

Figure 13 shows schema 1300, it illustrates a routine, and when this routine performs, this routine is determined by whether the module of program flow control monitoring routine monitoring has, within the restriction expected, the execution number of times being associated. Routine starts from starting block 1305. In block 1310, check whether variable " WithinLimitStatus " equals "true", subsequently in block 1315, check whether monitoring activates. If monitoring is not activated, so routine continues to block 1355. If monitoring activates, so in block 1320, check whether variable " MinTimeLimit " equals variable " NO_TIME_LIMIT ". If equal, in block 1325, so implement test, to determine whether variable " MinTime " is less than variable " MinTimeLimit ". Block 1330 is implemented check, to determine whether variable " MaxTimeLimit " equals variable " NO_TIME_LIMIT ". Block 1335 obtains the snapshot of current time, and calculates variable " GetElapsedTime ", in block 1340, obtain variable " Maxtime " subsequently. Block 1345 being determined, whether variable " MaxTime " is greater than variable " MaxTimeLimit ". If be greater than, then it is determined that whether the state of variable " WithinLimit " equals "false". Block 1355 returns the state of monitored module. When the module execution time exceeds acceptable scope, return corresponding module error condition.

As shown in the order table 1400 in Figure 14, performing interface routine when module generation fault, DevExecutionFailure () is for monitoring function, and thread or CMonitorMgr self can produce alarm in default situations. Default-action can be rewritten by equipment development person, to have the specific action of factory, such as turns off certain part equipment specific.

Many times, it is desirable to security function is performed with predetermined order. As with reference to described by Figure 15 and 16 and monitor safety order as shown in order table 1500 and schema 1600 and perform. Manipulate variable " SSequenceExecution " 1505, " bExecutionStart ", " Ushort " of boolean's type and " SequenceFailed () " 1515 of " ushSeqNum " 1510 and void type as illustrated in fig. 15. Safe order routine starts from starting block 1605. In block 1610, variable " bExecutionStart " is set to "true", and in block 1615, variable " ushSeqNum " is set to zero. In block 1620, check variable " ushSeqNum ", to determine if the order equaling previously execution. If equaled, so it is set to equal variable " ExecutedSequence " by variable " ushSeqNum " in block 1625. If inequal, so by variable " SequenceExecutionFailure () " set in block 1630. Whether all orders complete to implement test in block 1635. If order does not complete, so routine returns block 1620. If order completes, so before this routine terminates in block 1645, in block 1640, variable " bExecutionStart " is set up and equals "false".

After reading the disclosure, it will be appreciated by those skilled in the art that the additional alternative structure of program flow control monitoring routine and functional design. Although thus, it is to be understood that illustrate and describe specific embodiment and application, but the disclosed embodiments are not limited to accurately structure disclosed herein and parts. When not deviateing spirit of the present utility model and appending claims limited range, it is possible to layout disclosed herein, operation and algorithm details, method and equipment are made multiple amendment, change and the change that it will be apparent to those skilled in the art that.

Claims (6)

1. process plant monitoring and/or an operating device, comprising:

Controller, is configured to receive at least one input and produce at least one export, and wherein said controller is further configured to and realizes described embedded system, to realize monitoring and/or controlling functions in process; And

Current control monitoring device in described embedded system, the time stamp that described current control monitor detects any mistake relevant with described embedded system and provides instruction any mistake when to be detected, described current control monitor comprises interface, when any embedded system mistake being detected, described interface initialize factory specifically reports to the police and/or action, and wherein said current control monitor realizes at least in part in firmware for action during fault.

2. process plant according to claim 1 monitoring and/or operating device, wherein, described current control monitor provides the error-detecting relevant with item at least one in the following: control routine performs monitoring, runtime operation system thread is monitored, control routine sequentially monitors, action when fault being detected, above-mentioned every sub-portfolio or combination.

3. process plant according to claim 1 monitoring and/or operating device, wherein said current control monitor comprises at least one item in the following: module autonomous design, runtime operation system autonomous design, microprocessor autonomous design, modular design, scalable design, reusable design, above-mentioned every sub-portfolio or combination.

4. process plant according to claim 1 monitoring and/or operating device, wherein said current control monitor provides based on the error-detecting interrupted and/or wheel is ask.

5. process plant according to claim 1 monitoring and/or operating device, wherein said current control monitor is configured to monitor multiple module.

6. process plant according to claim 1 monitoring and/or operating device, wherein said current control monitor is configured to registration and nullifies multiple module.