RU2809537C2 - Method for obtaining data about rotation speed deviation - Google Patents

Abstract

FIELD: gas turbine engines.

SUBSTANCE: due to data storage limitations, electronic turbine engine data acquisition systems may not be able to continuously record high speed compressor rotor speed data over the life of the gas turbine engine (100). However, high-speed compressor rotor speed data may be useful for collecting short-term rotation speed variations that may occur during operating events of the gas turbine engine (100), such as idle periods. A control system (600) for a gas turbine engine (100) is disclosed. In embodiments, the control system (600) includes a controller (610) and a high-speed logging device (660). The controller (610) receives the sensor value from the sensor (22) coupled to the gas turbine engine (100) and publishes a label that contains the event type, the sensor value, and a timestamp. The high speed logging device (660) checks the tag for an overspeed event.

EFFECT: if an overspeed event is detected, the high speed logging device (660) logs the values provided by the tag.

7 cl, 3 dwg

Description

Technical field

The present invention relates generally to gas turbine engines and relates to a method for obtaining rotation speed deviation data for gas turbine engines.

State of the art

Gas turbine engines contain the following sections: compressor, combustion section and turbine. Gas turbine engines also contain a control system that, among other things, controls the gas turbine engine systems.

US Patent No. 10151215 to Raimondo et al. describes a control system for a gas turbine engine. In embodiments, the control system includes a controller and a high-speed recording device. The controller receives sensor values from sensors connected to the gas turbine engine and publishes a map of actuation thresholds. The high-speed logging device reads the sensor values from the controller. The high-speed registration device checks the card header to see if the card header has changed at a predetermined card read interval, sets a flag when the card header has been changed, and reads the card during the next card read interval cycle. The control system stores timestamps assigned to sensor values and trip thresholds on the same time axis.

The present invention is directed to overcome one or more problems identified by the inventors or known from the prior art.

The essence of the invention

This document discloses methods for monitoring a gas turbine engine. In embodiments, the method includes recording a turbocharger rotor speed obtained from the sensor and a time stamp associated with the turbocharger rotor speed. The method further includes detecting the start of an overspeed event if the rotational speed of the turbocharger rotor exceeds a trigger threshold value. The method further includes, in response to detecting the start of an overspeed event, detecting the end of an overspeed event if the turbocharger rotor speed falls below a threshold set point value. The method further includes, in response to detecting an overspeed event, generating a tag that contains an overspeed event value, a turbocharger rotor speed, and a timestamp. The method further includes reading the tag to detect an overspeed event. The method further includes, in response to detecting an overspeed event, recording a plurality of marks containing an overspeed event value, a rotation speed of the turbocharger rotor, a time stamp, from the start of the overspeed event to the end of the overspeed event.

Brief description of the figures

In fig. 1 is a schematic illustration of an exemplary gas turbine engine;

in fig. 2 shows a functional block diagram of the control system according to FIG. 1; And

in fig. 3 is a block diagram of a method for recording information related to the event of exceeding the permissible rotation speed of a turbocharger rotor of a gas turbine engine with the control system of FIG. 1 and 2.

Detailed description

The system and methods described herein include a control system for performing control and monitoring of a high speed machine such as a gas turbine engine. Although embodiments of the system and methods describe a gas turbine engine, the system and methods may be used with other high speed machines, such as diesel or gas engines. In embodiments, the control system includes a controller and a high-speed recording device. The controller interrogates the sensor connected to the gas turbine engine and monitors the gas turbine engine for events. The high-speed logging device receives sensor and event related data from the controller and stores timestamps corresponding to the sensor and event related data.

In fig. 1 is a schematic illustration of an exemplary high speed machine. In the illustrated embodiment, the high speed machine is a gas turbine engine 100. Some surfaces have been omitted or exaggerated (in this and other figures) for clarity and ease of explanation. Also, the present invention may refer to the front and back directions. In general, all references to "front" and "rear" are related to the direction of flow of the primary air (i.e., the air used in the combustion process), unless otherwise noted. For example, the front is “upstream” with respect to the primary air flow direction and the rear is “downstream” with respect to the primary air flow direction.

In addition, the description may generally refer to the central axis of rotation 95 of the gas turbine engine, which may be generally defined by the longitudinal axis of its compressor shaft 120 and power turbine shaft 130 (supported by a plurality of bearing assemblies 150). The central axis 95 may be common or shared with various other concentric engine components. All references to radial, axial and circumferential directions and measurements are to the 95 center axis unless otherwise noted, and terms such as "inner" and "outer" generally indicate less or more distance in the radial direction, with the radius 96 may extend in any direction perpendicular to and extending outward from the central axis 95.

The gas turbine engine 100 includes an intake 110, a compressor shaft 120, a turbocharger or compressor 200, a combustion compartment 300, a fuel system 80, a turbine 400, an exhaust gas outlet 500, and a clutch 50 for transmitting power output. The gas turbine engine 100 may be in a dual-shaft configuration, where the power turbine shaft 130 is separate from the compressor shaft 120, or may be in a single-shaft configuration, where the power turbine shaft 130 and the compressor shaft 120 form parts of a single shaft.

The compressor 200 may include a compressor rotor assembly 210, compressor stationary vanes ("stators") 250, and inlet guide vanes 255. The compressor rotor assembly 210 (also referred to as a compressor rotor) is mechanically coupled to a compressor shaft 120. As shown, compressor rotor assembly 210 is an axial flow rotor assembly. Compressor rotor assembly 210 includes one or more compressor disk assemblies 220. Each compressor disk assembly 220 includes a compressor rotor disk that is circumferentially filled with compressor rotor blades. Stators 250 axially follow each of the disks of the compressor assembly 220. Each disk of the compressor assembly 220 paired with adjacent stators 250 that follow the disk of the compressor assembly 220 is considered a compressor stage. Compressor 200 includes a plurality of compressor stages. The inlet guide vanes 255 axially precede the first compressor stage.

Combustion compartment 300 includes one or more fuel injectors 310 and combustion chamber 320.

Turbine 400 includes a turbine rotor assembly 410 and turbine nozzles 450. Turbine rotor assembly 410 may be mechanically coupled to compressor shaft 120 and turbine shaft 130. As shown, turbine rotor assembly 410 is an axial flow rotor assembly. Turbine rotor assembly 410 includes one or more turbine disk assemblies 420. Each turbine disk assembly 420 includes a turbine disk that is circumferentially filled with turbine blades. Turbine nozzles 450, such as a nozzle ring, axially precede each of the turbine disks in the turbine assembly 420. Each turbine nozzle 450 is grouped with the others in different ways to form a ring. Each turbine disk assembly 420 paired with an adjacent turbine nozzle 450 that precedes the turbine disk assembly 420 is considered a turbine stage. Turbine 400 contains multiple turbine stages.

The exhaust gas outlet 500 includes an exhaust gas diffuser 510 and an exhaust gas manifold 520.

One or more of the above components (or components thereof) may be made of stainless steel and/or durable high temperature materials known as "superalloys". A super alloy or high strength alloy is an alloy which is characterized by very high mechanical strength and creep resistance at high temperatures, adequate surface stability and resistance to corrosion and oxidation. Superalloys may include materials such as HASTELLOY, INCONEL, WASPALOY, RENE alloys, HAYNES alloys, INCOLOY, MP98T, TMS alloys and CMSX single crystal alloys.

The gas turbine engine 100 also includes a sensor that may be used to monitor and control the gas turbine engine 100. The sensor may include a shaft speed sensor 22. The shaft speed sensor 22 may be used to measure the rotor speed of the compressor assembly 210, which is also referred to as the turbocharger rotor speed (NGP). In a dual-shaft configuration, a separate sensor can be used to measure the rotor speed of the power turbine (NPT).

Gas turbine engine 100 also includes a control system 600. The control system 600 includes a controller 610 and a human-machine interface (HMI) 650. The controller 610 may be configured to receive values from a sensor coupled to the gas turbine engine 100 to monitor and control the gas turbine engine 100. The controller 610 may monitor the gas turbine engine 100 for events such as a sudden increase or decrease in the rotor speed of the compressor assembly 210.

In one embodiment, the control system 600 is implemented using one or more processors, memory, and software. The controller 610 may use the shaft speed sensor 22 to determine the type of event occurring, such as a normal operation event or an overspeed event, or may be alerted to an overspeed event by another process of the gas turbine engine 100.

The onset of an overspeed event can be defined as starting when the trip threshold is exceeded and ending when the setpoint threshold is reached. The actuation threshold and the setpoint threshold may be determined in relation to the NGP measured by the shaft speed sensor 22. In one example, the actuation threshold may be exceeded if the NGP measured by the shaft speed sensor 22 exceeds 100% of the predetermined maximum design rotation speed of the turbocharger rotor, which is sometimes referred to as the maximum design rotation speed.

When the NGP becomes less than the setpoint threshold, it can be considered the end of the overspeed event. In one example, the set point threshold may be passed if there is an active overspeed event at that time and if the NGP is less than 100% of the predetermined maximum design turbocharger rotor speed.

In one embodiment, there may be multiple overspeed event levels defined to represent different overspeed event levels/values. For example, there may be a first level overspeed event, a second level overspeed event, and a third level overspeed event. In one example, the third level overspeed event starts at a higher NGP than the first level and second level overspeed events. This means that the first level and second level overspeed events occur during the third level overspeed event.

Each overspeed event level can have a corresponding trigger level. For example, there may be a first level trigger threshold, a second level trigger threshold, and a third level trigger threshold. In one example, the first level trip threshold may occur at an NGP of 101.5% of the maximum design rotation speed, the second level trip threshold may occur at an NGP of 103.75% of the maximum design rotation speed, and the third level trip threshold may occur at an NGP of 105% of the maximum design rotation speed. In other examples, the trip threshold levels may be set to occur at a wide variety of NGPs and percentages of NGPs relative to the maximum design rotation speed. Although three trigger threshold levels have been described herein, there may be four, five, six, seven, eight, nine or more trigger threshold levels. During operation of the gas turbine engine 100, there may be multiple exceedances of the first level, second level, and third level actuation thresholds. For example, the first trigger threshold of the first level, the second trigger threshold of the first level, the third trigger threshold of the first level, and so on.

Each trip threshold may represent the start of an overspeed event, which may be accompanied by a setpoint threshold representing the end of an overspeed event.

In one embodiment, there are multiple levels of setpoint threshold, such as a first level setpoint threshold, a second level setpoint threshold, and a third level setpoint threshold. In one example, the first level setpoint threshold may occur at an NGP of 101% of the maximum design rotation speed, the second level setpoint threshold may occur at an NGP of 103.25% of the maximum design rotation speed, and the third level setpoint threshold may occur at NGP equal to 104.5% of the maximum design rotation speed. In one example, the set point threshold is generally 0.5% less than the corresponding operation threshold. In one example, the set point threshold is generally 1.0% less than the corresponding operation threshold.

Although three levels of set point thresholds have been described here, there may be four, five, six, seven, eight, nine or more levels of set point thresholds. During operation of gas turbine engine 100, there may be multiple exceedances of the first level, second level, and third level set point thresholds. For example, the first setpoint threshold of the first level, the second setpoint threshold of the first level, the third setpoint threshold of the first level, and so on.

In one embodiment, the normal operation event occurs during normal operation of the gas turbine engine, for example, when the NGP is between 94% and 100% of the maximum design compressor rotor speed. In other examples, the NGP is generally 100% of the maximum design rotation speed during normal operation of the gas turbine engine. In one example, the upper limit of the normal operating mode of the gas turbine engine 100 passes to the operating threshold and the gas turbine engine 100 returns to the normal operating state when the NGP falls below the threshold set value.

In some embodiments, the HMI 650 includes a high speed recording (HSR) device 660 configured to receive and record NGP values (also sometimes referred to as values) of the shaft speed sensor 22 and events recorded by the controller 610, including overspeed events, standard operating mode and other events, such as events related to the gas turbine engine operating cycle (start-up, shutdown, load change, etc.). In other embodiments, the HSR 660 may be contained in a device coupled to the controller 610. The HMI 650 may be coupled to the monitoring system 700. An operator may temporarily attach the monitoring system 700 to the HMI 650 to obtain information recorded by the HSR 660 and to analyze and diagnose any problems with the gas turbine engine 100. In some embodiments, the HMI 650 is coupled to the monitoring system 700 over a network to provide remote monitoring and diagnostic information recorded by the HSR 660. Remote monitoring can be performed on-site or off-site for the gas turbine engine 100.

In fig. 2 is a functional block diagram of the control system 600 of FIG. 1. The controller 610 may include a work controller 620 and a publisher 630. The work controller 620 is configured to control the gas turbine engine 100 while the gas turbine engine 100 is operating. The work controller 620 may use values received from various sensors to control the gas turbine engine 100.

The publisher 630 is configured to record an array that relates to, among other things, each event type and NGP values received from the shaft speed sensor 22 . The event type can characterize normal operating conditions and overspeed conditions, such as at the start of an overspeed event, the end of an overspeed event, during an overspeed event, and at different levels of overspeed events.

A label may be assigned to, among other things, each event type to identify the logged NGP value, the associated timestamp, and the type of event occurring. The tag may contain accumulated count values associated with the total number of times each overspeed event level has occurred in the gas turbine engine. Each label can be associated with a unique identifier to identify the label associated with it. Each unique identifier can be associated with an event type, a timestamp, and a registered NGP value in the array. The unique identifier may be a number used to identify the tag. The tags may be unique to a given gas turbine engine 100.

A timestamp represents a temporary value, such as the date and time of day, when the event occurred and when the NGP value was received. In some embodiments, publisher 630 logs timestamps based on controller clock 640 for events rather than values received from shaft speed sensor 22. In some embodiments, controller 610 reads timestamps based on controller clock 640 for NGP values received from shaft speed sensor 22. These NGP values and corresponding timestamps may be temporarily stored in the controller data store 615 of the management system 600 for a predetermined period of time. For example, NGP values and corresponding timestamps during a normal operation event may be temporarily stored for one hour in controller data store 615 before being gradually replaced by new values. The time period for temporarily stored values can be increased or decreased.

The HSR 660 may begin reading tags from the publisher 630 upon detecting an overspeed event. The HSR 660 can log a published tag when an overspeed event value is present in the tag. If an overspeed event occurs, temporary values stored in controller data store 615 can be logged by the HSR 660. For example, if an overspeed event occurs, the HSR 660 may record all previously temporarily stored values and data tags starting from 1 minute before the time mark of the start of the event of exceeding the permissible rotation speed, when the triggering threshold value was exceeded. When the NGP falls below the setpoint threshold and the overspeed event ends, the HSR 660 can continue to record all values and data tags starting 15 minutes after the setpoint threshold.

For NGP values obtained from the shaft speed sensor 22, the recorded value may be a floating point value obtained from the shaft speed sensor 22. In embodiments, these values are analog values obtained from the shaft speed sensor 22.

When an event occurs, the unique identifier, the offset to uniquely define the timestamp, and the logged NGP value can be packed into 32-bit words, which can then be packed into an array. When polling the shaft speed sensor 22, the recorded value can be stored into a 32-bit word, which can then be packed into an array.

In some embodiments, the array may be divided into an event array and an analog value array. Unique identifiers, timestamps and event types are packed into an event array, and recorded values for shaft speed sensor 22 are packed into an analog value array.

Publisher 630 may be configured to publish a label of an event that occurred within the last time range of a predetermined interval. The label includes a timestamp of the label. The timestamp of the tag is the time according to the controller clock 640 when the tag is published. This label can also contain unique identifiers, event type, and offset for each event. The offset for each event may be the amount of time the event was recorded relative to the timestamp of the tag. In some embodiments, the offset is expressed in milliseconds.

HSR 660 includes an event logging device 662, an analog logging device 664, a frequency regulator 666, an indirect timing unit 667, and a direct time shifting unit 668. In a homogeneous polling system, all timestamps must refer to the same time axis. The various processes of the HSR 660 are configured to create a virtual time axis that simulates the clock 640 of the controller 610 in order to keep all timestamps on the same time axis. The HSR 660 can limit the number of events logged. For example, after 20 overspeed events have occurred, each subsequent overspeed event logged may displace the oldest overspeed event.

Event logging device 662 may be configured to read the tag as soon as it is published by publisher 630. Event logging device 662 checks the tag at a predetermined interval and looks for an overspeed event type. The predetermined interval may have a relatively high frequency, such as once every 100 milliseconds, compared to the interval at which the publisher 630 publishes the label. If the tag event type changes from a normal operation event value to an overspeed event value, the event logging device 662 sets a flag to allow the entire tag to be logged.

Event logging device 662 may record the duration of an overspeed event and the number of overspeed events. Event logging device 662 may continuously record overspeed events and provide a total event count that is incremented incrementally each time an event occurs. For example, if the first level 1 overspeed event, the second level 1 overspeed event, and the third level 1 overspeed event occur, the total event count would be three. If a fourth level 1 overspeed event occurs, the total event count increases to four. Event logging device 662 may continuously record overspeed events of each overspeed event level. For example, if the first level one overspeed event and the second level overspeed event occur, the total event count will be one and the second level event count will be one and, for this example, the third level event count will be zero.

The duration of the overspeed event may be the time between the start of the overspeed event and the end of the overspeed event. Event logging device 662 may record the duration of multiple overspeed events.

For example, the duration of the overspeed event for the first level overspeed event, the second overspeed event of the first level, and the third overspeed event of the first level. Event logging device 662 may store the total cumulative duration of events for trip thresholds and setpoint thresholds. For example, the total cumulative duration for all first level trigger thresholds and first level setpoint thresholds.

The analog logging device 664 may operate in parallel with the event logging device 662. The analog logging device 664 may read the values received for the shaft speed sensor 22 from the controller 610 or the published tag at a predetermined interval, such as once every 100 milliseconds. Analog logging device 664 assigns a timestamp to each value received from controller 610 based on the following formula:

Where is the assigned timestamp, is the time on the virtual time axis when the HMI 650 receives the values, and is the time on the virtual time axis when the request to read the values was sent.

Analog recording device 664 may record the maximum NGP that occurs in the gas turbine engine when the first level actuation threshold is detected.

Delays in the HMI 650 operating system may affect the exact rate at which the forward time offset unit 668 reads values received from the shaft speed sensor 22 from the controller 610 or a published tag. The frequency controller 666 is configured to estimate the exact time during which the analog logging device 664 reads these values. The frequency controller 666 maintains the average cycle time between readings of the values received for the shaft speed sensor 22 from the controller 610 for a predetermined number of cycles. In one embodiment, the frequency controller 666 maintains the average cycle time between readings of the values received for the shaft speed sensor 22 from the controller 610 or publisher over the last twenty cycles.

If the average value is shifted by a predefined amount relative to the predefined interval, then an adjustment is applied. For example, if the average value is greater than the predetermined interval plus the predetermined value, then the frequency controller 666 accelerates by the adjustment amount the next scheduled time for reading the values by the analog device 664 for recording; if the average value is less than the predetermined interval minus the predetermined value, then the frequency controller 666 delays by the adjustment amount the next scheduled time for the analog device 664 to read the values for recording.

In one embodiment, the predetermined interval is 100 milliseconds, the predetermined value is 5 milliseconds, and the adjustment amount is 1 millisecond. In this embodiment, if the average value is greater than 105 milliseconds, the analog logger 664 accelerates the reading of the values by 1 millisecond, and if the average value is less than 95 milliseconds, the analog logger 664 delays the reading of the values by 1 millisecond. In embodiments, the acceleration and latency of reading values by analog logging device 664 is limited to a range of 80 milliseconds to 120 milliseconds.

Depending on the configuration of the control system 600, the HSR 660 uses an indirect time block 667 or a direct time offset block 668 to maintain a virtual time axis. If date and time values are available for controller 610, forward time offset block 668 may be used. If date and time values are not available for controller 610, indirect time determination block 667 may be used.

The indirect timing block 667 relies on a predetermined interval that the publisher 630 uses to update the timestamp of the tag. The indirect time determination unit 667 performs a synchronization loop when HSR 660 starts and then at regular intervals, such as every hour. The synchronization cycle of the indirect timing unit 667 includes reading the timestamp of the tag at a relatively high frequency, for example every 20 milliseconds. If the timestamp of the notch has changed, the indirect time determination block 667 sets a flag that allows the timestamp of the notch to be read and assigned the current time to the virtual time axis HSR 660 within a subsequent regular interval cycle. When the timestamp of a mark is assigned to the current time of the virtual time axis, the indirect timing block compensates for the delay caused by waiting for the next cycle to read the timestamp of the mark and assign it to the current time of the virtual time axis.

The immediate time offset block 668 assigns the current value of the virtual time axis as the controller time plus the time interval. In some embodiments, this controller time is stored in the same analog array with the sensor values. The complete reading of sensor values from the controller 610 by the analog logging device 664 may be split into multiple sub-packets due to the size limitations of the data transfer packets between the controller 610 and the HMI 650. The time interval can be determined by:

Where is a time interval (which can have a negative value), is the response time to read from the last packet, is the read request time from the first packet, n denotes the index of the auxiliary packet that contains the controller date and time, and N denotes the number of auxiliary packets that make up the complete array. In some embodiments, when the absolute value of a time interval is less than a predetermined threshold, it will not be added to the controller time. In some embodiments, this predetermined threshold is 10 ms.

The control system 600 may also include an HMI data store 655. HMI data store 655 may be used by HMI 650 and its various processes to store, among other things, data read from controller 610 and to store a virtual time axis.

Industrial applicability

Gas turbine engines can be suitable for a variety of industrial applications, such as various aspects of the oil and gas industry (including transmission, gathering, storage, extraction and lifting of oil and natural gas), power generation, power generation, aerospace and other transportation industries.

Due to data storage limitations, electronic turbine engine data acquisition systems may not be able to continuously record high speed compressor rotor speed data over the life of the gas turbine engine 100. However, high speed compressor rotor speed data may be useful. to collect short-term variations in rotational speed that may occur during operating events of the gas turbine engine 100, such as idle periods. Typically, the NGP of gas turbine engine 100 is controlled to remain above 94% of the maximum design rotation speed to limit emissions and below 100% of the maximum design rotation speed to prevent structural failure of the compressor rotor. The ability to log data to identify the characteristics of an overspeed event can provide useful information to eliminate factors that could lead to structural failure of a gas turbine component. For example, to eliminate destruction caused by modal impact. Structural damage and failure can occur due to the maximum NGP being reached, due to operating for extended periods at rotational speeds above a specific NGP, and due to the number of times the NGP exceeds a particular NGP threshold.

In fig. 3 is a block diagram of a method for recording information related to the event of exceeding the permissible rotation speed of a turbocharger rotor of a gas turbine engine with the control system of FIG. 1 and 2. The method begins at block 810 and includes the controller 610 recording the turbocharger rotor speed received from the sensor and a time stamp associated with the turbocharger rotor speed based on the controller clock 640. Block 810 may include controller 610 querying sensor 22 coupled to gas turbine engine 100 for turbocharger rotor speed at a predetermined sensor polling interval.

Block 820 enables the controller to detect a normal operation event if the turbocharger rotor speed is below the actuation threshold, and the start of an overspeed event if the turbocharger rotor speed is above the actuation threshold. In one embodiment, there are multiple levels of overspeed events and the controller may detect the onset of each overspeed event level. For example, the controller may detect a normal operation event if the turbocharger rotor speed is below the trigger threshold, the start of a first level overspeed event if the turbocharger rotor speed exceeds the first level trigger threshold, the start of a second level overspeed event, if the rotation speed of the turbocharger rotor exceeds the threshold value of the second level, and the beginning of the event of exceeding the permissible speed of rotation of the third level, if the speed of rotation of the turbocharger exceeds the threshold value of the third level.

Block 820 may include the publisher 630 of the controller 610 recording an array of NGP values received from the shaft speed sensor 22 and the occurrence of each event. Block 820 may include writing shaft speed sensor 22 values to an analog array. Block 820 may also include recording each event to an event array, which may include recording a unique identifier and timestamp of the event. The event timestamp may represent the time according to the controller clock 640 when the event occurred.

Block 830 enables controller 610 to detect, in response to detecting the start of an overspeed event, the end of an overspeed event, and the start of a normal operation event if the turbocharger rotor speed falls below a threshold set point. In one embodiment, there are multiple overspeed event levels, and controller 610 may detect the end of each overspeed event level. For example, controller 610, in response to detecting the start of a first level overspeed event, detects the end of a first level overspeed event if the turbocharger rotor speed is less than the first level setpoint threshold; controller 610, in response to detecting the start of a second level overspeed event, detects the end of a second level overspeed event if the rotation speed of the turbocharger rotor is less than a second level setpoint threshold; and the controller 610, in response to detecting the start of the third level overspeed event, detects the end of the third level overspeed event if the rotation speed of the turbocharger rotor is less than the third level setpoint threshold.

Block 840 includes controller 610 generating, in response to detection of a normal operation event, a tag containing the value of the normal operation event, the rotation speed of the turbocharger rotor, and a timestamp; and generating, by the controller 610, in response to detection of an overspeed event, a tag comprising an overspeed event value, a rotation speed of the turbocharger rotor, and a time stamp.

In one embodiment, there are multiple overspeed event levels, and controller 610 may generate tags based on each overspeed event level. For example, controller 610, in response to detecting a first level overspeed event, generates a tag comprising a first level overspeed event value, a turbocharger rotor speed, and a timestamp. The controller 610, in response to detecting a second level overspeed event, generates a tag containing a first level overspeed event value, a second level overspeed event value, a turbocharger rotor speed, and a time stamp. The controller 610, in response to detecting a third level overspeed event, generates a label containing a first level overspeed value, a second level overspeed value, a third level overspeed event value, a turbocharger rotor speed, and a temporary mark.

Block 840 may include publishing by the label publisher 630 an event that occurred within the last time range of the predetermined label publication interval. Publishing an event label may involve updating the registry to add an event that occurred within the last time range of the label's publishing interval. The published tag may contain a timestamp of the tag, that is, the time on the controller clock 640 when the tag was published, and recorded information, such as a unique identifier, sensor value, and offset, for an event that occurred within the last time range. The offset can be the difference in time between the event timestamp and the label timestamp.

Block 850 includes high speed device 660 reading a tag to detect a transition between a normal operation event and an overspeed event. In one embodiment, there are multiple levels of an overspeed event, and the high speed logging device 660 may read the tag to detect a transition between a normal operation event, a first level overspeed event, a second level overspeed event, and an overspeed event. rotation of the third level.

Block 850 may include HSR 660 reading the tag after it is published and reading shaft speed sensor values from controller 610. Block 850 may include checking the tag by event logging device 662 at a predetermined tag reading interval to detect whether the tag contains a value. events of exceeding the permissible rotation speed. In this case, the predetermined tag reading interval has a higher frequency than the predetermined tag publishing interval. Block 850 may also include setting a flag by device 662 to log events when the tag contains an overspeed event value and logging the entire tag. Block 850 may also include analog device 664 reading to record values received for each sensor from controller 610 or tag at a predetermined sensor read interval or tag read interval, respectively. The sensor reading interval can be equal to the tag reading interval.

When HSR 660 reads data from controller 610, data corruption may occur. By checking the tag at a relatively high frequency compared to the tag publication interval and reading the tag only when the tag header has been changed, the event logger 662 ensures that the tag is read only after it has been fully updated, but well before the next tag change, which can prevent data corruption.

Block 860 includes, in response to detection of an overspeed event, recording by high speed device 660 to record multiple marks containing the overspeed event value, the turbocharger rotor speed, a time stamp, from the start of the overspeed event to the end of the overspeed event. permissible rotation speed. In one embodiment, there are multiple levels of an overspeed event, and the high speed recording device may, in response to detecting a first level overspeed event, log multiple tags containing the first level overspeed event value, the overspeed event value rotation of the second level, the value of the event of exceeding the permissible rotation speed of the third level, the rotation speed of the turbocharger rotor and the time stamp.

The method may also include the control system 600 storing all timestamps on a single time axis. The method may include assigning, by the analog logging device 664, a sensor time stamp relative to a virtual time axis to each sensor value received from the controller 610. The sensor timestamp may be assigned by subtracting from the time on the virtual axis the time at which the values were received by the analog logging device 664. half the difference between the time on the virtual time axis when the values were received by the analog device 664 for logging and the time on the virtual time axis when the request to read the values was sent by the analog device 664 for logging.

The method may include adjusting the predetermined sensor reading interval by frequency controller 666 to account for delays of the HMI operating system 650. Adjusting the predetermined sensor reading interval may include maintaining the average cycle time between reading sensor values over a predetermined number of cycles, increasing the actual predetermined sensor reading interval by the amount of the adjustment if the average value is below the required sensor reading interval by a predetermined amount, and reducing the actual predefined sensor reading interval by the adjustment amount if the average value is above the required sensor reading interval.

The method may also include assigning, by block 668, a direct time offset to the current value of the virtual time axis as the time on controller clock 640 plus a packet read interval when date and time values for controller clock 640 are available. The packet read interval may be the difference between the last packet read response time and the first packet read request time, multiplied by the difference of half the result of dividing the auxiliary packet index, which contains the date and time of the controller clock 640, by the number of auxiliary packets that make up the complete array. . This interval can be negative. In some embodiments, when the absolute value of this interval is less than a predetermined threshold, it will not add up to the controller time. In some embodiments, this threshold is equal to half the cycle time of the controller 610.

The method may further include executing a synchronization loop by the indirect timing unit 667 upon startup of the HSR 660 and thereafter at a synchronization interval with the publisher 630 to create a virtual time axis, and assigning a time stamp by the publisher 630 to the current time on the virtual time axis by compensating for the delay caused by waiting for the next loop to read the timestamp of the tag when the date and time of the controller clock 640 are not available.

The method may also include obtaining time-stamped data associated with the sensor and events of the monitoring system 700 to monitor the gas turbine engine 100, to perform diagnostics of the gas turbine engine 100, to alert technicians and customers when certain events occur, and to recommend maintenance of the gas turbine engine. Diagnostics may be performed by a technician who analyzes the data to determine what maintenance, if any, needs to be performed on gas turbine engine 100. Performing monitoring and diagnostics of the gas turbine engine 100 may include providing raw data, various statistics, and alerts to technicians or consumers over a network. Diagnostics may also be performed by monitoring system 700 or corresponding remote systems that may use analytics to perform monitoring and diagnostics on gas turbine engine 100. In some embodiments, data received by controller 610 is read by HSR 660 and written as sets. These sets can be obtained by the monitoring system 700. As in some other embodiments, the HSR 660 may operate in other devices attached to the controller. Other control systems may also receive these sets.

As described above, the HSR 660 may maintain a virtual time axis that stores all data received by the HSR 660 on a time axis relative to the clock 640 of the controller 610 and on a synchronized virtual time axis when the clock 640 of the controller 610 is unavailable. Maintaining a virtual time axis can prevent inconsistencies when creating timestamps and can eliminate the need for a technician to perform time-consuming analysis of digital state changes and review of events in various event registries.

It will be apparent to those skilled in the art that the various illustrative logical blocks and algorithm steps described in conjunction with the embodiments disclosed herein may be implemented as electronic hardware, computer software, program modules, or combinations thereof. To explicitly reflect such interchangeability of hardware and software, various illustrative components, blocks, and steps have been described above in general terms with respect to their functionality. The implementation of such functionality as hardware or software depends on the design constraints imposed on the system as a whole. Those skilled in the art may implement the described functionality in different ways for each particular application, but such implementation decisions should not be construed as causing a departure from the scope of the present invention. In addition, grouping functions within one block or step is intended for ease of description. Specific functions or steps can be moved from one block without departing from the scope of the present invention.

The various illustrative logic blocks described in conjunction with the embodiments disclosed herein may be implemented or executed by a general purpose processor, digital signal processor (DSP), application specific integrated circuit (ASIC), field programmable gate array (FPGA), or other programmable logic devices, discrete or transistor logic gates, discrete hardware components, or any combination thereof designed to perform the functions described in this document. The general purpose processor may be a microprocessor, but in the alternative, the processor may be any processor, controller, or microcontroller. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in combination with a DSP core, or any other similar configuration.

The steps of the method or algorithm described in combination with the embodiments disclosed herein may be implemented directly in hardware, in software executed by a processor (eg, a computer processor), or a combination of the two. Software may be stored in random access memory (RAM), flash memory, read-only memory (ROM), electrically programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), registers, hard disk, removable disk , CD-ROM or any other form of storage medium. An exemplary storage medium may be coupled to a processor such that the processor can read information from and write information to the storage medium. Alternatively, the storage medium may be an integral part of the processor. The processor and storage medium may be located in an ASIC.

The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present invention. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles described herein may be applied to other embodiments without departing from the spirit or scope of the invention. Thus, it should be understood that the description and drawings presented herein depict the presently preferred embodiment of the invention and, therefore, represent the subject matter broadly contemplated by the present invention. It should also be understood that the scope of the present invention fully includes other embodiments that may become apparent to those skilled in the art.

Claims (13)

1. A method for monitoring a gas turbine engine (100), the method comprising: recording the rotation speed of the turbocharger rotor received from the sensor (22) and a time stamp associated with the rotation speed of the turbocharger rotor; detecting the start of an overspeed event if the turbocharger rotor speed exceeds the triggering threshold; detecting, in response to detecting the start of an overspeed event, the end of an overspeed event if the rotation speed of the turbocharger rotor falls below a threshold set point; generating, in response to detection of an overspeed event, a tag that contains the value of the overspeed event, the rotation speed of the turbocharger rotor, and a time stamp; reading the tag to detect an event of exceeding the permissible rotation speed; And registering, in response to detection of an overspeed event, a plurality of marks containing the value of the overspeed event, the rotation speed of the turbocharger rotor, a time stamp, from the beginning of the overspeed event to the end of the overspeed event. 2. The method of claim 1, wherein the method further includes, in response to detecting the end of the overspeed event, recording a plurality of marks containing the turbocharger rotor speed and a time stamp for a total of fifteen minutes after the overspeed event rotation speed. 3. The method of claim 2, wherein the method further comprises temporarily storing a plurality of marks comprising a turbocharger rotor speed and a time stamp of the mark, and, in response to the onset of an overspeed event, recording the turbocharger rotor speed and time stamp generally from one minute before the start of the overspeed event. 4. The method according to claim 1, characterized in that the method further includes incrementally increasing the count by one for each overspeed event recorded during operation of the gas turbine engine (100). 5. The method according to claim 1, characterized in that the method additionally includes determining the total duration of the overspeed events by summing the difference between the start time stamp of the overspeed event and the end time stamp of the overspeed event of each overspeed event , recorded during operation of the gas turbine engine (100). 6. The method according to claim 1, characterized in that the method further includes recording the maximum rotation speed of the turbocharger rotor between the start of the overspeed event and the end of the overspeed event. 7. The method according to claim 1, characterized in that the threshold value of the setting is generally 0.5% less than the threshold response value.