EP1394643B1 - Méthode et dispositif pour surveiller activement une resource dans une commande numérique - Google Patents

Méthode et dispositif pour surveiller activement une resource dans une commande numérique Download PDF

Info

Publication number
EP1394643B1
EP1394643B1 EP03018251A EP03018251A EP1394643B1 EP 1394643 B1 EP1394643 B1 EP 1394643B1 EP 03018251 A EP03018251 A EP 03018251A EP 03018251 A EP03018251 A EP 03018251A EP 1394643 B1 EP1394643 B1 EP 1394643B1
Authority
EP
European Patent Office
Prior art keywords
resource
data
added functionality
functionality
numerical control
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.)
Expired - Lifetime
Application number
EP03018251A
Other languages
German (de)
English (en)
Other versions
EP1394643A2 (fr
EP1394643A3 (fr
Inventor
Rainer Dirnfeldner
Michael Kaever
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Siemens AG
Original Assignee
Siemens AG
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Siemens AG filed Critical Siemens AG
Priority to EP10009504.1A priority Critical patent/EP2254015B1/fr
Priority to EP10009503A priority patent/EP2254014A3/fr
Publication of EP1394643A2 publication Critical patent/EP1394643A2/fr
Publication of EP1394643A3 publication Critical patent/EP1394643A3/fr
Application granted granted Critical
Publication of EP1394643B1 publication Critical patent/EP1394643B1/fr
Anticipated expiration legal-status Critical
Expired - Lifetime legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B19/00—Programme-control systems
    • G05B19/02—Programme-control systems electric
    • G05B19/418—Total factory control, i.e. centrally controlling a plurality of machines, e.g. direct or distributed numerical control [DNC], flexible manufacturing systems [FMS], integrated manufacturing systems [IMS], computer integrated manufacturing [CIM]
    • G05B19/4184—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], computer integrated manufacturing [CIM] characterised by fault tolerance, reliability of production system
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
    • G06F11/0706—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment
    • G06F11/0736—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment in functional embedded systems, i.e. in a data processing system designed as a combination of hardware and software dedicated to performing a certain function
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
    • G06F11/0751—Error or fault detection not based on redundancy
    • G06F11/0754—Error or fault detection not based on redundancy by exceeding limits
    • G06F11/076—Error or fault detection not based on redundancy by exceeding limits by exceeding a count or rate limit, e.g. word- or bit count limit
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
    • G06F9/5011—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resources being hardware resources other than CPUs, Servers and Terminals
    • G06F9/5022—Mechanisms to release resources
    • 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/24—Pc safety
    • G05B2219/24109—Execute first diagnostic, service program before normal control program
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/34—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
    • G06F11/3442—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment for planning or managing the needed capacity
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/34—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
    • G06F11/3466—Performance evaluation by tracing or monitoring
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2201/00—Indexing scheme relating to error detection, to error correction, and to monitoring
    • G06F2201/805—Real-time
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2209/00—Indexing scheme relating to G06F9/00
    • G06F2209/50—Indexing scheme relating to G06F9/50
    • G06F2209/504—Resource capping
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2209/00—Indexing scheme relating to G06F9/00
    • G06F2209/50—Indexing scheme relating to G06F9/50
    • G06F2209/508—Monitor
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/48—Program initiating; Program switching, e.g. by interrupt
    • G06F9/4806—Task transfer initiation or dispatching
    • G06F9/4843—Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
    • G06F9/485—Task life-cycle, e.g. stopping, restarting, resuming execution
    • 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
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
    • Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
    • Y02P90/02—Total factory control, e.g. smart factories, flexible manufacturing systems [FMS] or integrated manufacturing systems [IMS]

Definitions

  • the present invention relates to Control of Automation Systems and, more particularly, to Active Resource Control of Automation Systems, particularly in a Run-Time Environment.
  • software modules or functions may overburden the System Resources and cause the System to abort. This is particularly problematic when the modules or functions are not previously accounted for, such as when functions or modules are activated, added or loaded in a Real Time System. It can occur, in this circumstance, that the module or function overburdens the System Resources because the Resources are previously allocated to other functions. For example, a Resource can be overburdened upon start-up based on some change in the configuration of the System. Or, perhaps, the System can reach its Resource limit during the run of a Real-Time system when, for example, a function is activated, such as when activating a Trace Function of a Motion Control Machine.
  • US 5,838,968 A proposes a system and method for dynamic resource management across tasks in real-time operating systems. Resources are allocated to task on the basis of predefined data provided for each task in a task resource utilization vector. During run-time, resource allocation can be varied in that tasks are allocated further resources (promotion) or previously allocated ressorces are removed or reduced (degradation).
  • US 5,844,795 A is concerned with a diagnostic aid for industrial controller using multi-tasking architecture, wherein at least one task runs a memory monitor program allowing input and output data to be viewed on an ad hoc basis. Each task is allocated processor time by a preemptive scheduler, allowing currently running tasks to be replaced by another task on account of specific criteria, e.g. a priority assigned to each task.
  • active resource control of added functionality in a numerical control process having at least one resource is provided. It can occur during run-time of the numerical control process, that an added functionality that uses at least a portion of the resource overburdens an existing limitation of the resource.
  • multiple layers for actively detecting and responding to resource limit errors can be combined or employed separately.
  • on-line checking of the added functionality detects during run time whether the added functionality causes the numerical control process to reach a resource limit.
  • Error handling that handles errors upon reaching a resource limit.
  • off-line checking detects off-line, before the run time of the numerical control process, whether the added functionality causes the numerical control process to reach a resource limit of the resource.
  • the invention further provides a flexible response to resource limit errors based on a degree of importance of the added functionality.
  • FIG 1 is a block diagram of an example system in which the present invention is employed.
  • an Automation Services Company 10 provides content comprising software, services and so forth, to a plurality of customers, represented by systems 1-N (reference numerals 14, 16, and 18, respectively).
  • a provider of manual engineering services 12 e.g., a Manufacturer
  • the customer systems 1-N (12, 14, 16) is in communication with the customer systems 1-N (12, 14, 16).
  • a Service provider 20 comprises a host 30 (referred to below simply as "host") in communication with a system/customer database 34 and an interactive user 32 that performs administrative or other functions. Any number of such databases 34 and interactive users 32 may interact with host 30.
  • An application programming interface (API) 36 makes possible for a Manufacturer partner 24 to deal with the content provided by the host 30.
  • one or more interactive users 40 interact with Manufacturer-partner host 38 for administration or other purposes.
  • Content is also provided over network 25 as between host 30 and client 26.
  • Client (or customer) 26 may comprise one or more controlled devices 42, such as a computer numerical controlled/ programmable logic controller (CNC/PLC) systems, peripheral devices and sensors, controllers 44, personal computers 45 and host computers 46, some or all of which are in communication over an internal network 47.
  • CNC/PLC computer numerical controlled/ programmable logic controller
  • controllers 44 personal computers 45 and host computers 46, some or all of which are in communication over an internal network 47.
  • the present invention is not limited to numerical controlled devices, but encompasses Active Resource Control of all types of controlled devices.
  • the present invention provides Active Resource Control of a controlled device 42.
  • the host 30 actively monitors and controls the resources of the controlled system 42.
  • Data regarding status of the Resource(s) is stored in the database 34 and used by the host 30 to determine whether a particular Resource is overburdened.
  • the steps for determining whether a resource is overloaded includes the step of measuring or estimating the free resources.
  • the resources can be determined from the operating system, which should know the time until the end of the cycle. This data can be passed from the O/S to the resource control. In such cases, the operating system should know the current amount of free memory / data storage and this is useful for executing the invention in every cycle.
  • the next step in the invention is to determine an estimated or a known future resource consumption resulting from the added functionality. It is preferred that, in the case of checking during the intervals of each cycle, the estimated or known resource consumption for the next step is determined. If, in some instances, the run-time of additional functionality is not known, but a worst-case estimation for sub-steps is known (e.g. each sub-step not more than 100 Microseconds) the worst-case limit may be used. The worst case estimation, in fact, may be used for some or all of the sub-steps instead of estimating resource usage individually for each sub-step (e.g. check at least each 100 us if more than 100us processing time are left in cycle).
  • an additional step may be introduced.
  • a user-defined/configurable safety margin may be determined that takes account of uncertainties in the estimations if any.
  • a user-specified limit may be employed. For example, if free resources can not be estimated, a user may specify an estimation of the free resources, that is, specify a limit for the resources an additional functionality may use. Rather, if resource usage of the additional functionality (or a step thereof) is not known, the user-estimation may be used instead. It could be, for example, that the minimum amount of resources remaining is a specified quantity for a particular operating system.
  • Figure 3 which is a schematic perspective of the invention, the resource allocation data is stored in the technical database 34B.
  • the technical database can be stored in any suitable storage device.
  • Figure 3 further illustrates the architecture shown in Figure 2 , particularly demonstrating the connectivity between host 30 and a customer operating client system 26, or Manufacturer 24, or others, who may arrange for and obtain access to the databases.
  • service provider 20 through its host 30, provides network-delivered automation-related content to a plurality of client systems, 261, 262, ..., 26N, each controlling a respective machine tool 701, 702, ...,70N.
  • Host 30 writes data into databases, for example, a first database 34A comprising commercial data and a second database, 34B, comprising technical data.
  • a data structure corresponding to each of the databases is shown below each of the databases 34A and 34B.
  • data structure 1012 comprises a plurality of data sets, one for each customer. Each customer data set within data structure 1012 may be recorded and accessed on the basis of the unique ID for that customer. Within the data for a given customer, there may be any number of sets of data corresponding to machines or client devices operated by the customer. Each such machine or client device is identified by a unique identifier or code, that is included in the data structure 1012.
  • data is first organized by customer. Given that a customer is likely to have any number of machines for which service provider 20 may be able to provide content, a plurality of fields, each corresponding to machines operated by that customer, may be present within a given customer's data, each such machine ID (or client ID) being unique to the particular machine tool or other controlled equipment. Data structure 1012, thus, can provide a historical view of behavior over time for the particular machine.
  • the present invention accesses, for example, real time trace data relating to a Trace Function initiated on a Machine coupled to the host through the network. Based on the Resource Allocation Data stored in the Database 34B, the Active Resource Control determines whether the available Resource(s) will be overloaded by the added functionality.
  • the Trace Function is but a single example of the various Functions that could overload System Resources that would trigger the Active Resource Control Mechanism of the present invention.
  • the present invention is not so limited to the particular arrangement or inclusion of data shown in Figure 3 . Certain information, for example, could be added or deleted, the data could be re-ordered, and other data structures could be used, consistent with this aspect of the present invention.
  • a System normally comprises Standard Functionality, including, for example, non-Real Time Standard Functionality 402 and / or Real Time Standard Functionality 404.
  • the Functionality sits on an operating system O/S 406 which controls the System.
  • Added Functionality including, for example, non-Real Time and Real Time Functionality 408, 410, respectively.
  • Pre-Activation Checking which provides the first layer of Active Resource Control. This process performs a resource limit check after completing the specification of a configuration that causes additional functionality to be activated but before actually activating this configuration. Specifically, Pre-Activation Checking compares available free resources with the expected additional resource requirements of the functionality/module to be added/activated.
  • the (a1) actual resource usage is measured from the System. Normally, this data is stored by the host 30 in the database 34B as Resource Allocation Data.
  • Another method within the present invention is to check (a2) an average or maximum resource usage measured for some period of time, for example, the previous minute, hour, or day. In practice, these two methods haven proven to be more precise, yet requiring less effort. However, these methods are dependant on circumstances which occur in the past, and real events may be more sporadic and unanticipated.
  • the present invention further provides a process that predicts resource overloads.
  • the invention provides for various predictions.
  • a first prediction is based on assumptions of the current system configuration. Another is based on statistical, theoretical, simulation or experimental knowledge about resource usage of individual control functions. Further, the predictive data maybe derived from combinations of control functions. This process requires more effort, but it is more deterministic. If the stored data regarding the availability of resources has integrity, the prediction itself provides a best / worst-case estimation.
  • the estimations regarding additional resources that are required are only based on the list of functions/modules to be activated.
  • the estimations could employ stored statistical, theoretical, simulation or experimental knowledge about resource usage of such control functions.
  • the data could be drawn as well from a combination with each other or with certain control functionality.
  • the required knowledge may be obtained in similar, or even the same, set of experiments, simulations, etc.
  • An example of such an experiment may be the measurement of the Run Time of Numerical Control Functionality for different Numerical Control setups in the course of automated software regression tests being done periodically.
  • Such timing measurement results are currently used only to identify and evaluate software development problems.
  • the timing results are stored in a database for resource control.
  • the data does not comprise a single number for each Function but, rather, a range of worst/typical/best cases, or other empirical data, such as statistical distribution.
  • the invention not only provides for monitoring and detection of overloading Resource Controls, but also provides responses, i.e., Control. Advance Checking is useful as a first estimation on possible resource problems. However, unanticipated events can, and do, occur even with Advanced Checking. Therefore, the invention provides a flexible response that is designed to react differently depending on the accuracy of the database and on the probability of resource problems that has been computed. With less accurate data, it is more likely that unanticipated results arise and vice versa.
  • responses i.e., Control.
  • Control i.e., Control.
  • Advance Checking is useful as a first estimation on possible resource problems. However, unanticipated events can, and do, occur even with Advanced Checking. Therefore, the invention provides a flexible response that is designed to react differently depending on the accuracy of the database and on the probability of resource problems that has been computed. With less accurate data, it is more likely that unanticipated results arise and vice versa.
  • responses provided by the present invention according to the degree of accuracy of the data.
  • the present invention provides, in one aspect, that the activation of the added functionality is blocked without override. However, and as will be explained, there is further provided Error Handling which aborts the added functionality, whilst leaving the critical Functions running. In another aspect, if available resources are sufficient under the best case estimation, yet not sufficient under the typical case estimation, the added functionality is blocked with a warning but allowing the user to override the blockage of the added Function.
  • the present invention was created to solve problems regarding overburdening Resources of a Numerical Control System, where a Trace Function was activated to trace the movement of a machine for diagnostics. It had been the case that the activated Trace Function caused the run time to reach the available cycle time of the cycle of interpolation task in a numerical control, for example an IPO cycle, and thus cause trouble in running the Numerical Control System.
  • the present invention is not so limited to Trace Functionality and is similarly to be applied to any "addable" functionality (e.g.
  • NCK numerical control kernel
  • FIG. 4 A second aspect, or step, of On-Line Checking 414 of the present invention is shown in Figure 4 which provides a second layer of Active Resource Control.
  • the machine tool here is On-Line, that is, coupled to the System and active.
  • On-Line Checking is advantageous because it monitors the events of the Machine in Real Time, events as they unfold, and access data of the Machine through the network during Run-Time.
  • Some of the techniques used to monitor the events of the Machine during the first step, i.e., Off-Line Checking may be employed as well in On-Line Checking. However, care must be taken with On-Line operations, because the Machine is running under a Cycle Time and it must be ensured that the Machine complete its task(s) within the cycle time.
  • the present invention presents possible various ways to optimize this checking to the needs of On-Line processing in real-time systems and to tailor it to the specific situation at hand.
  • the present invention performs run checking every cycle or, alternatively, only periodically depending on the load caused by resource checking and the dynamics of changes in resource usage.
  • the present invention performs a full check of available resources and expected usage or, alternatively, limit On-Line Checking to changes in available resources. Where On-Line Checking must be kept relatively simple, the checking might be done on a general level, disregarding a specific configuration of Control Functionality or additional modules/functions.
  • the present invention provides a synchronous checking methodology, whereby checking is executed during run-time allocation of each IPO cycle and causing a running trace to be stopped (and alarm to be issued) if a certain limit is reached (e.g. 95% of cycle time used).
  • the checking for available resources may be distributed within the activated additional functionality (e.g. Trace) in a way that checking is performed a plurality of times as illustrated by reference numeral 414a in Figure 4 . This is contrast to checking per cycle as shown by reference numeral 414b.
  • checking is executed along the course of functionality so that, in case of resource overload, the functionality until that time is completed and, only a part of the functionality is aborted.
  • the steps that have been executed before aborting the functionality still provide something useful for completing the task during the next cycle perhaps or for debugging or troubleshooting purposes.
  • the present invention provides flexible responses to on-line detection of resource problems that may, for example, depend on the criticality of the added Function.
  • a resource problem is persistent (e.g., long-term resource problems, or memory problems) the additional functionality is aborted (preferably with corresponding alarm) while the Standard Functionality is allowed to continue to run.
  • resource problem is intermittent (e.g., short-term resource problems, one cycle)
  • the additional functionality should be aborted only for the cycle (preferably by message or alarm) and continued in the next cycle. This could occur, for example, during run-time upon the occurrence of a load peak of some system function.
  • functionality falls into a number of sub-steps, only the sub-steps that not yet have been completed will be aborted.
  • the limits and estimations used for On-Line Checking are freely accessible, selectable and / or configurable by the user.
  • a third layer of Active Resource Control If for any reason, the On-Line Checking did not detect a resource problem so that a resource limit is finally reached, a suitable error handling exception 416 is provided by the present invention.
  • errors caused by some activated additional functionality are aborted / disabled only while keeping the standard functionality alive.
  • the present invention provides that this option is configurable, because, not all situations can operate without the additional functionality. When it is not possible, for example, for safety reasons, to run the system without the additional functionality, the whole system would have to be shut down in a safe way.
  • an operator such as user 32 ( Figure 2 ) interacts, via a Human Machine Interface (HMI) 50 and an Interface 60, with a Control System 66 that controls Machine Tool 70.
  • the Control System 66 includes a base system 68, a Manufacturer Application Interface 69, that permits downloaded program code to be plugged into the Control System 66 as compile cycle(s) 72.
  • base system 68 provides a Trace Functionality for Data Capture that can be extended through Manufacturer Application Interface 69.
  • the Trace Functionality locally gathers data and stores it into a buffer or queue associated with any of the levels 76-84, after which a non-cyclic task takes buffer data and stores it into a file in data storage 74, which may be, for example, static RAM, such that it can later be merged into the trace data.
  • the base system 68 is also in communication with various level control tasks, including pre-run control tasks 76, main (i.e., interpolator (IPO) level) control tasks 78, servo control and drive data control tasks 80, PLC data 82 and other information sources 84 within the machine control.
  • level control tasks including pre-run control tasks 76, main (i.e., interpolator (IPO) level) control tasks 78, servo control and drive data control tasks 80, PLC data 82 and other information sources 84 within the machine control.
  • Figure 6 provides a flow diagram that describes the steps associated with a method of performing Active Resource Control of a Data Capture System incorporating the additional Trace Functionality.
  • a client system HMI 50 receives program code associated with a selected service from host 30 over network 25 at step 802. Access by the real-time controller 66 is provided to the downloaded program code at step 804 and program code is executed. At step 806, data lists are identified and configured, which specify which data are to be captured. At step 808, respective events are configured, on the occurrence of which the specified data are to be captured. At 810, triggers are set, also according to the accessed, downloaded code.
  • a link is made to the respective data list.
  • Linking to a data list comprises storing a reference to which data list should be used. If the data collection capacity of the base system 68 has not been exhausted, as checked at step 816, then, based on the linked data list that contains a number of entries, each identifying one data to be recorded, all desired information is being accessed through base system 68 and, if required, through execution of the downloaded software. The specified data are written at step 818 to data storage 74, which may occur by way of an appropriate buffer.
  • step 820 As long as the capacity of data storage 74 is not exhausted, the trace continues until, at 820, occurrence of a respective trigger is detected. At the end of a post-trigger delay, assuming one had been specified, the link to the respective data list(s) are ended and writing to storage location 74 is terminated. If the data collection capacity had, at step 816, been exhausted, step 820 would also be invoked.
  • a system using the data capture functionality described should use no more than, say, approximately 60% of available cycle time, which may help to avoid interference with any running applications.
  • a Trace Functionality is in danger of exceeding this limit and even threatening overburdening resources.
  • a "Normal Trace” by itself is capable of overloading the resources. While the Normal Trace is begun and ended upon definite events, and a transfer of the Trace Date occurs only when the trace is stopped, there are numerous applications triggered by Trace Functionality that can cause Resources to be overloaded. Trace Functionality triggers machine commissioning support. It activates failure detection and debugging of system problems. There are applications problems especially for complex applications with multiple channels, synchronous actions, etc. There is routinely run-time situations that handle, for example, sporadic run-time problems. Often, Traces include crash-handling procedures, such as complete data gathering via Kernel dump. There may even be logic analysis involved in a Trace, such as oscilloscope, tachometer, etc.
  • Trace Function accesses local user program data, such as flags in the PLC program. Trace Functions are also known to copy Traced Local Data into a suitable global variable.
  • the present invention aims to respond to a resource overload to possibly avert a crash. If a crash is unavoidable, high robustness of gathering the data after a fault occurs is desirable and may be accomplished in the following ways. Data, to the extent possible, is made available after a resource overload. As previously mentioned, sudden errors during a Trace do not necessarily lead to a data overflow and there is provided in the invention suitable reactions in the event of resource scarcity. If an event or condition does occur, the data files are preserved according to the invention.
  • the present invention provides multiple layers of Active Resource Control. As shown in Figure 6 , these layers are overlayed on the System. Needless to say, these layers may be implemented in conjunction or separately. As shown, the step of Pre-Checking 811 is initiated before the start of the Function, i.e., Trace Function as shown, the detailed steps of which have been discussed above. It will be appreciated from the Figure that the Pre-Checking step 811 is executed Off-Line, that is, before the Function is running.
  • the On-Line Checking step 813 runs, on-line, that is concurrently with the Function as will be appreciated from Figure 6 .
  • step 813 performs Active Resource Control in Real Time.
  • the granularity of the On-Line Checking step 813 is configurable, that is, may either be initiated On-Line in the course of the Function or as many times as desired. This is illustrated in the Figure as steps 813 1..n . It shall be appreciated that increasing the granularity may improve the probability of detecting a Resource overload before the System crashes.
  • the invention further provides, as already described, a flexible response, which includes aborting the added Functionality without halting the entire system.
  • step 815 Another layer is the Error-Handling step 815, which has already been discussed. As will be appreciated from Figure 6 , step 815 also is activated during Run-Time. Indeed, the Error-Handling may be considered to run in the background, as it is triggered when a Resource limit is reached, which was not previously detected by, for example, the other Active Resource Control layers.
  • Host 30 queries the user for ID codes, that may include a customer ID code and a machine ID code, for example. Host 30, then, transmits to the user a set of options, which may include a list of Functions, at 906. The user transmits and the host 30 receives the user's selection of an option, at 908. Based upon the user's selection, host 30 retrieves from a database a set of properties for the client machine tool, at 910, and confirms, at 912, that the selected option is appropriate for the machine tool being operated by client 26. If not, host 30 notifies the user, at 914, that the selected option is inappropriate under the circumstances and that another option should be selected.
  • ID codes that may include a customer ID code and a machine ID code, for example.
  • Host 30, transmits to the user a set of options, which may include a list of Functions, at 906. The user transmits and the host 30 receives the user's selection of an option, at 908. Based upon the user's selection, host 30 retrieves from
  • the host 30 retrieves information for the selected option, at 916, and retrieves content, e.g., program code, associated with the selected option, at 918, that may be executed at the host 30 and/or at the client 26.
  • the information includes the specific Machine Tool Resource Allocation Data. In general, this data will be transferred to client 26, to be used, according to the description provided above, to assist in controlling the machine tool and gathering particular, resultant data. Following its retrieval, any content, such as program code, that has been retrieved by the host 30 is transmitted to client 26, at 920.
  • host 30 creates a database record for the transaction corresponding to the option selected by the user.
  • Host 30 associates the client and machine tool IDs with the database record, at 924, thereby identifying the specific machine tool that executes the selected Function.
  • host 30 associates the date and time the selected option is invoked with the database record established at 924.
  • host 30 may also associate the earlier-retrieved Resource Allocation Data with the database record, at 928.
  • host 30 awaits user initiation of client machine tool behavior corresponding to the selected option and the associated, downloaded program code and/or data.
  • the purpose of this waiting step, at 930, is to ensure user safety: particularly when moving machinery is involved, running the machinery should involve a manual step to help make sure the operator is aware of imminent machine activity before it begins and thereby avoid injury to personnel.
  • Host 30 receives a message, at 932, indicating that the user has initiated activity associated with the selected option. Host 30 also then awaits transmission, at 934, of data generated in connection with operating the machine tool and collected from the machine tool controller during the course of the selected option, including the Resource Allocation data gathered at the machine tool. Then, at 936, host 30 receives machine tool data collected from the client 26 machine tool and is stored in the database. In this manner, the Resource Allocation data is retrieved.
  • host 30, at step 938 processes data collected from client 26 according to code corresponding to the option selected by the user. Then, at step 940, the results of processing the data uploaded from client 26 (e.g., generated by numerical analysis module 512, of Figure 5 ) are transmitted to client 26, or, in some embodiments, to an entity that owns or controls it.
  • billing information is retrieved or generated, at 942, based on retrieved price information and is processed for transmission to the user or its owner or operator.
  • the database and selected option are made available for access by partner organizations. The order and the particulars of the above-steps may be varied. Moreover, other steps may be added without departing from the scope of this aspect of the present invention.

Claims (5)

  1. Procédé de commande d'une ressource active de fonctionnalité ( 410 ) ajoutée dans une opération de commande numérique ayant au moins une ressource,
    le procédé comprenant les stades dans lesquels :
    on fait débuter, pendant le déroulement de l'opération de commande numérique, une fonctionnalité ( 410 ) ajoutée, qui utilise au moins une partie de la ressource ; et
    on contrôle en ligne la fonctionnalité ( 410 ) ajoutée en détectant, pendant le déroulement de l'opération de commande numérique, si la fonctionnalité ( 410 ) ajoutée fait que l'opération de commande numérique atteint une limite de la ressource, caractérisé en ce que :
    l'opération de commande numérique est cyclique et le stade de contrôle en ligne de l'opération de commande numérique détermine si la ressource est surchargée dans un cycle,
    le procédé comprenant, en outre, en réaction à la détection que la fonctionnalité ( 410 ) ajoutée atteint la limite de la ressource, le stade dans lequel on prévoit au moins une réaction qui réagit en fonction d'un degré d'importance de la fonctionnalité ( 410 ) ajoutée, la réaction arrêtant seulement la fonctionnalité ( 410 ) ajoutée, dans lequel des résultats de la fonctionnalité ajoutée extraient dans un cycle avant d'interrompre la fonctionnalité ajoutée sont récupérés et dans lequel de l'information concernant l'interruption de la fonctionnalité ajoutée est indiquée dans un résultat de la fonctionnalité ajoutée.
  2. Procédé suivant la revendication 1, dans lequel la fonctionnalité ( 410 ) ajoutée est interrompue pendant un cycle présent.
  3. Procédé suivant la revendication 1, dans lequel l'information indique que les résultats de la fonctionnalité ajoutée ne sont pas complets.
  4. Procédé suivant la revendication 1, dans lequel l'interruption de la fonctionnalité ajoutée est indiquée par une alerte.
  5. Procédé suivant la revendication 1, comprenant, en outre, le stade de réglage d'une granularité du contrôle en ligne pour contrôler à une pluralité d'intervalles d'un cycle de l'opération de commande numérique.
EP03018251A 2002-08-23 2003-08-11 Méthode et dispositif pour surveiller activement une resource dans une commande numérique Expired - Lifetime EP1394643B1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP10009504.1A EP2254015B1 (fr) 2002-08-23 2003-08-11 Méthode et dispositif pour surveiller activement une resource dans une commande numérique
EP10009503A EP2254014A3 (fr) 2002-08-23 2003-08-11 Méthode et dispositif pour surveiller activement une resource dans une commande numérique

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US10/227,087 US7016759B2 (en) 2002-08-23 2002-08-23 Active resource control system method & apparatus
US227087 2002-08-23

Related Child Applications (3)

Application Number Title Priority Date Filing Date
EP10009504.1A Division EP2254015B1 (fr) 2002-08-23 2003-08-11 Méthode et dispositif pour surveiller activement une resource dans une commande numérique
EP10009503.3 Division-Into 2010-09-13
EP10009504.1 Division-Into 2010-09-13

Publications (3)

Publication Number Publication Date
EP1394643A2 EP1394643A2 (fr) 2004-03-03
EP1394643A3 EP1394643A3 (fr) 2007-10-03
EP1394643B1 true EP1394643B1 (fr) 2013-03-20

Family

ID=31495322

Family Applications (3)

Application Number Title Priority Date Filing Date
EP03018251A Expired - Lifetime EP1394643B1 (fr) 2002-08-23 2003-08-11 Méthode et dispositif pour surveiller activement une resource dans une commande numérique
EP10009503A Withdrawn EP2254014A3 (fr) 2002-08-23 2003-08-11 Méthode et dispositif pour surveiller activement une resource dans une commande numérique
EP10009504.1A Expired - Lifetime EP2254015B1 (fr) 2002-08-23 2003-08-11 Méthode et dispositif pour surveiller activement une resource dans une commande numérique

Family Applications After (2)

Application Number Title Priority Date Filing Date
EP10009503A Withdrawn EP2254014A3 (fr) 2002-08-23 2003-08-11 Méthode et dispositif pour surveiller activement une resource dans une commande numérique
EP10009504.1A Expired - Lifetime EP2254015B1 (fr) 2002-08-23 2003-08-11 Méthode et dispositif pour surveiller activement une resource dans une commande numérique

Country Status (2)

Country Link
US (1) US7016759B2 (fr)
EP (3) EP1394643B1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106383223A (zh) * 2016-08-31 2017-02-08 世纪亿康（天津）医疗科技发展有限公司 一种凝血和血小板功能分析仪

Families Citing this family (26)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7707359B2 (en) * 2005-12-09 2010-04-27 Oracle America, Inc. Method and apparatus for selectively prefetching based on resource availability
US8776092B2 (en) * 2006-09-29 2014-07-08 Rockwell Automation Technologies, Inc. Multiple interface support
US8818757B2 (en) * 2008-09-30 2014-08-26 Rockwell Automation Technologies, Inc. Modular object and host matching
US7912560B2 (en) * 2006-09-29 2011-03-22 Rockwell Automation Technologies, Inc. Module and controller operation for industrial control systems
US8732658B2 (en) * 2006-09-29 2014-05-20 Rockwell Automation Technologies, Inc. Layered interface in an industrial environment
US8265775B2 (en) * 2008-09-30 2012-09-11 Rockwell Automation Technologies, Inc. Modular object publication and discovery
US7676279B2 (en) * 2006-09-29 2010-03-09 Rockwell Automation Technologies, Inc. Services for industrial control systems
US7856279B2 (en) * 2006-09-29 2010-12-21 Rockwell Automation Technologies, Inc. Module structure and use for industrial control systems
US9217998B2 (en) * 2006-09-29 2015-12-22 Rockwell Automation Technologies, Inc. Management and development of an industrial environment
US9261877B2 (en) * 2006-09-29 2016-02-16 Rockwell Automation Technologies, Inc. Multiple machine interface
US20080082577A1 (en) * 2006-09-29 2008-04-03 Rockwell Automation Technologies, Inc. Module classification and searching for industrial control systems
US9058032B2 (en) * 2006-09-29 2015-06-16 Rockwell Automation Technologies, Inc. Hosting requirements for services
US8041435B2 (en) * 2008-09-30 2011-10-18 Rockwell Automation Technologies, Inc. Modular object dynamic hosting
US8078296B2 (en) * 2006-09-29 2011-12-13 Rockwell Automation Technologies, Inc. Dynamic procedure selection
US7835805B2 (en) * 2006-09-29 2010-11-16 Rockwell Automation Technologies, Inc. HMI views of modules for industrial control systems
US20090326697A1 (en) * 2006-11-17 2009-12-31 Hejian Technology (Suzhou) Co., Ltd. Semiconductor manufacturing automation system and method for using the same
US20090089325A1 (en) * 2007-09-28 2009-04-02 Rockwell Automation Technologies, Inc. Targeted resource allocation
EP2221694B1 (fr) * 2009-02-19 2013-03-27 Siemens Aktiengesellschaft Procédé de concession d'une justification d'utilisation d'une fonction dans un système d'automatisation industriel comprenant plusieurs unités de commande en réseau et système d'automatisation industriel
CN102004680A (zh) * 2010-11-23 2011-04-06 山东中创软件商用中间件股份有限公司 一种动态跟踪程序运行状态的方法及一种背板装置
TW201339777A (zh) * 2012-03-30 2013-10-01 Prec Machinery Res Dev Ct 可與數廠牌加工機控制器同時連線之方法
CN102929210B (zh) * 2012-11-22 2014-07-16 南京航空航天大学 基于特征的数控加工过程控制和优化系统及方法
CN103116313B (zh) * 2012-12-31 2018-07-31 深圳市配天智造装备股份有限公司 应用于数控机床对工件表面进行加工的方法及数控机床
CN103605318B (zh) * 2013-11-14 2017-02-15 北京铭隆世纪科技有限公司 Cnc控制器的功能定制方法、装置以及cnc控制器
CN106227108A (zh) * 2016-08-30 2016-12-14 成都福誉科技有限公司 一种运动控制器
JP7229884B2 (ja) * 2019-08-29 2023-02-28 株式会社日立ビルシステム 制御装置、及び装置制御方法
US11853282B2 (en) * 2021-12-09 2023-12-26 International Business Machines Corporation Gaining insights on database system table changes

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5726912A (en) * 1996-09-06 1998-03-10 Honeywell Iac Control system monitor
US5838968A (en) * 1996-03-01 1998-11-17 Chromatic Research, Inc. System and method for dynamic resource management across tasks in real-time operating systems

Family Cites Families (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2752514B2 (ja) 1990-11-22 1998-05-18 ファナック株式会社 Ｃｎｃ装置のプロブラム実行方式
US5452201A (en) * 1993-08-24 1995-09-19 Allen-Bradley Company, Inc. Industrial controller with highly distributed processing
US5408663A (en) * 1993-11-05 1995-04-18 Adrem Technologies, Inc. Resource allocation methods
JPH07129418A (ja) 1993-11-08 1995-05-19 Fanuc Ltd マルチタスク環境でのプログラム制御方式
US5636124A (en) * 1995-03-08 1997-06-03 Allen-Bradley Company, Inc. Multitasking industrial controller
US5844795A (en) 1995-11-01 1998-12-01 Allen Bradley Company, Llc Diagnostic aid for industrial controller using multi-tasking architecture
JPH09244728A (ja) * 1996-03-13 1997-09-19 Fanuc Ltd オンライン端末として利用されるｃｎｃ装置のデータ表示・入力方法
DE19624929C2 (de) * 1996-06-21 2001-08-02 Siemens Ag Prozeßautomatisierungssystem
US5978578A (en) * 1997-01-30 1999-11-02 Azarya; Arnon Openbus system for control automation networks
JP2001125797A (ja) * 1999-10-25 2001-05-11 Seiko Epson Corp マルチタスクシステム及びそのプログラムを記録した記録媒体並びに加工装置
GB2367913A (en) * 2000-09-16 2002-04-17 Motorola Inc Processor resource scheduler

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5838968A (en) * 1996-03-01 1998-11-17 Chromatic Research, Inc. System and method for dynamic resource management across tasks in real-time operating systems
US5726912A (en) * 1996-09-06 1998-03-10 Honeywell Iac Control system monitor

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106383223A (zh) * 2016-08-31 2017-02-08 世纪亿康（天津）医疗科技发展有限公司 一种凝血和血小板功能分析仪

Also Published As

Publication number Publication date
EP2254015A2 (fr) 2010-11-24
EP1394643A2 (fr) 2004-03-03
US7016759B2 (en) 2006-03-21
EP2254015A3 (fr) 2010-12-15
EP2254015B1 (fr) 2014-10-15
EP2254014A2 (fr) 2010-11-24
EP2254014A3 (fr) 2010-12-15
US20040039477A1 (en) 2004-02-26
EP1394643A3 (fr) 2007-10-03

Similar Documents

Publication Publication Date Title
EP1394643B1 (fr) Méthode et dispositif pour surveiller activement une resource dans une commande numérique
EP1410120B1 (fr) Capture de donnees destinee aux services d'automatisation a livraison electronique
EP1407412B1 (fr) Systeme de bases de donnees et procede permettant de fournir des services a distance pour des dispositifs d'automatisation industriels
EP1407333B1 (fr) Systeme et procede de diffusion electronique de contenu destines a des systemes d'automatisation industriels
RU2487388C2 (ru) Исполнительный механизм для систем hvac и способ его функционирования
US7292900B2 (en) Power distribution expert system
WO2003007090A2 (fr) Architecture d'un systeme et procede destine a un contenu automatise distribue par reseau
JP6724847B2 (ja) 制御装置、制御プログラム、制御システム、および制御方法
CN103403628A (zh) 安全控制装置以及安全控制方法
JP2018181315A (ja) 制御装置、制御方法および制御プログラム
EP3702858A1 (fr) Système de communication, procédé de communication et programme
EP3623952B1 (fr) Système de collecte de données de fonctionnement, procédé de collecte de données de fonctionnement et programme
US10890889B2 (en) Method of monitoring and assessing the operation of an industrial installation driven by a programmable controller and equipment implementing said method
CN113352316A (zh) 自动化设备和机器人的消息传递方法及动态消息传递系统
JPH09179754A (ja) タスク監視装置及びタスク監視方法
Albertos et al. Control kernel: A key concept in embedded control systems
KR100547625B1 (ko) 그리드 정보서비스를 위한 지능형 모니터링 시스템 및 방법
CN110837399A (zh) 一种管理流式计算应用程序的方法、装置及计算设备
Theiss et al. PLC-integrated process monitoring and prediction of the resulting real-time load
Cheng et al. Real-time computing in open systems for manufacturing
EP1274013A1 (fr) Module de surveillance de processus
CN110914842A (zh) 用于机器的自动维护的方法和系统
Magro et al. Measuring real time performances of PC-based industrial control systems
JP2003316424A (ja) 機器診断装置
Mathes et al. Time-constrained services: a framework for using real-time web services in industrial automation

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

AK Designated contracting states

Kind code of ref document: A2

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

AX Request for extension of the european patent

Extension state: AL LT LV MK

RTI1 Title (correction)

Free format text: METHOD AND APPARATUS FOR ACTIVE RESOURCE MONITORING IN A NUMERICAL CONTROL PROCESS

PUAL Search report despatched

Free format text: ORIGINAL CODE: 0009013

AK Designated contracting states

Kind code of ref document: A3

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

AX Request for extension of the european patent

Extension state: AL LT LV MK

17P Request for examination filed

Effective date: 20071022

AKX Designation fees paid

Designated state(s): DE FR GB

17Q First examination report despatched

Effective date: 20100528

REG Reference to a national code

Ref country code: DE

Ref legal event code: R079

Ref document number: 60343540

Country of ref document: DE

Free format text: PREVIOUS MAIN CLASS: G05B0019414000

Ipc: G05B0019418000

RIC1 Information provided on ipc code assigned before grant

Ipc: G05B 19/418 20060101AFI20120810BHEP

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

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

Owner name: SIEMENS AKTIENGESELLSCHAFT

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): DE FR GB

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 60343540

Country of ref document: DE

Effective date: 20130516

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

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

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

26N No opposition filed

Effective date: 20140102

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 60343540

Country of ref document: DE

Effective date: 20140102

GBPC Gb: european patent ceased through non-payment of renewal fee

Effective date: 20130811

REG Reference to a national code

Ref country code: FR

Ref legal event code: ST

Effective date: 20140430

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: GB

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20130811

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: FR

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20130902

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: DE

Payment date: 20211019

Year of fee payment: 19

REG Reference to a national code

Ref country code: DE

Ref legal event code: R119

Ref document number: 60343540

Country of ref document: DE

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: DE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20230301