Circuit breaker with notification and reporting capabilities

Abstract

A method of monitoring electrical faults includes processing features of signals output by sensors of a circuit breaker regarding electrical properties of a circuit coupled with a load, and transitioning between operating states based on the processed features. The states include a normal state, a fault state, and a tripped state, where the state remains in the normal state until the processed features no longer satisfy normal criteria, after which the state transitions to the fault state, where the state transitions back to the normal state when a trip condition is not satisfied, and the state transitions from the fault state to the tripped state when the trip condition is satisfied. The method further includes detecting a warning event when the state transitions from the normal state to the fault state and back to the normal state, and outputting a warning event notification when the warning event is detected.

Description

[0001] Cross-references to related applications

[0002] This application claims priority to U.S. Patent Application Serial No. 62 / 979,864, filed February 21, 2020, the entire contents of which are incorporated herein by reference. Technical Field

[0003] This disclosure relates to circuit breakers, and more specifically, to circuit breakers with notification capabilities. Background Technology

[0004] Circuit breakers protect circuits from damage caused by overcurrent or overvoltage (such as overload or short circuit). When a fault is detected, the circuit breaker may trip, interrupting the current. These trips can be harmful. As technology advances, the sensitivity of circuit breakers may increase, potentially increasing the occurrence of harmful trips.

[0005] Technological advancements in arc-fault circuit interruption (AFCI) devices that improve arc detection sensitivity can mask fault conditions in the load, such as those caused by wear or aging. For example, new available hardware can improve arc detection sensitivity, particularly in the 1MHz to 40MHz bandpass region. While many household appliances do not generate RF noise in this region, there are exceptions where actual arcing currents occur (such as in motor brushes, high-frequency switching of certain power supplies, and fluorescent lamp ignition). These arcing events may have a filterable, desirable pattern. However, pattern variations (e.g., those due to aging or wear) may not be detected until a trip occurs.

[0006] When a trip does occur, the user may not know whether it is merely an inconvenience to be ignored or an indication of degradation of the load, socket, or cable coupled to a branch monitored by the tripped circuit breaker. The user may not know whether resetting the circuit breaker and resuming operation is safe. In some cases, operation may be unrecoverable due to the conditions that caused the trip. Operation is then interrupted until the faulty component can be repaired or replaced. Unexpected interruptions to circuit operation can be inconvenient, costly, and / or dangerous.

[0007] While conventional methods and systems are generally considered to fulfill their intended purpose, there remains a need in the art for a circuit breaker that reduces harmful tripping and provides indications of when a load, receptacle, or cable indicates performance degradation before operation is halted. This disclosure provides a solution. Summary of the Invention

[0008] The objects and advantages of the illustrated embodiments described below will be set forth in the following description and will become apparent therefrom. Further advantages of the illustrated embodiments will be realized and obtained by means of the devices, systems, and methods particularly pointed out in the written description and its claims, as well as the accompanying drawings. To achieve these and other advantages, and in accordance with the objects of the illustrated embodiments, in one aspect, a method for monitoring electrical faults is disclosed. The method includes determining characteristics of a signal output by at least one sensor of a circuit breaker, the characteristics representing electrical properties of a circuit coupled to a load. The method also includes transitioning between operating states based on processed characteristics. Operating states include a normal state, a fault state, and a trip state, wherein the operating state remains in the normal state until the processed characteristics no longer meet normal criteria, thereafter transitioning to the fault state, wherein the operating state transitions back to the normal state when a trip condition is not met, and transitions to the trip state when a trip condition is met. The method also includes detecting a warning event when the operating state transitions from the normal state to the fault state and back to the normal state, and outputting a warning event notification when a warning event is determined.

[0009] In one or more embodiments, the method may further include processed features of a buffered signal and the contents of an output buffer associated with a warning event notification.

[0010] In one or more embodiments, the electrical fault may be an arc fault, a ground fault, and / or a ground neutral fault.

[0011] In one or more embodiments, the contents of the buffer may correspond to the time from when the circuit breaker leaves its normal state until it returns to its normal state.

[0012] In one or more embodiments, the method may further include: transitioning to a warning notification state to buffer processed features of a signal when a normal criterion is not met, then transitioning to a fault state, transitioning from the fault state to a warning notification state when a tripping condition is not met, thereby indicating that a warning event has been detected, transitioning from the warning notification state to a communication state to output a warning event notification and the contents of the buffer, and transitioning from the warning notification state to a normal state.

[0013] In another aspect of this disclosure, a method for monitoring electrical faults is disclosed. The method includes receiving one or more warning event notifications from a circuit breaker, wherein each warning event notification is based on the detection of transition patterns between operating states of the circuit breaker. Operating states include a normal state and a fault state; in the normal state, processed characteristics meet normal criteria, and in the fault state, normal criteria are not met. The pattern includes a series of transitions, including transitioning from the normal state to the fault state and back to the normal state. The method also includes determining a probability of impending tripping based on the one or more warning event notifications and outputting an impending trip notification according to the determined probability.

[0014] In one or more embodiments, a warning event notification may include a warning duration indicating the duration during which the circuit breaker is not operating in a normal state, wherein the probability of an impending trip may be determined based on a parameter and / or a variation of one or more parameters, including at least one of the number of warning event notifications, the warning duration, and the duration between warning event notifications.

[0015] In one or more embodiments, the method may further include receiving warning data with a warning event notification, the warning data including any processed features that are functions of the electrical characteristics of a circuit branch connecting the circuit breaker to one or more loads sensed after the circuit breaker transitions from a normal state. The electrical characteristics may be sensed by the circuit breaker, and the probability of an impending trip may be determined based on changes in the processed features.

[0016] In one or more embodiments, the method may further include decomposing warning data to identify which of one or more loads is energized or operating when the corresponding electrical property is sensed, wherein the probability of an impending trip may also be a function of the operation of the identified one or more loads.

[0017] In one or more embodiments, the method may further include applying at least one model to determine when to output an impending trip notification, and applying machine learning, statistical and / or numerical techniques to train and / or apply at least one model.

[0018] In one or more embodiments, the trip notification may be output wirelessly to a user equipment and / or via a network to a remote device.

[0019] In another aspect of this disclosure, a circuit breaker coupled to at least one load is disclosed. The circuit breaker includes a memory configured to store a plurality of programmable instructions and at least one processing device communicating with the memory. Upon execution of the plurality of programmable instructions, the at least one processing device is configured to process characteristics of signals output by at least one sensor of the circuit breaker regarding electrical properties of the circuit coupled to the load, and to transition between operating states based on the processed characteristics. The operating states include a normal state, a fault state, and a trip state. The operating state remains in the normal state until the processed characteristics no longer meet the normal criteria, after which the operating state transitions to the fault state. When the trip condition is not met, the operating state transitions from the fault state back to the normal state, and when the trip condition is met, the operating state transitions to the trip state. Upon execution of the plurality of programmable instructions, the at least one processing device is also configured to detect a warning event when the operating state transitions from the normal state to the fault state and back to the normal state, and to output a warning event notification when a warning event is detected.

[0020] In one or more embodiments, when executing multiple programmable instructions, at least one processing device may also be configured to buffer the processed features of a signal and output the contents of the buffer in association with a warning event notification.

[0021] In one or more embodiments, the contents of the buffer may correspond to the operation of the circuit breaker from its exit from the normal state until it returns to the normal state.

[0022] In one or more embodiments, the circuit breaker may include at least one sensor for sensing electrical properties and at least one signal conditioning and conversion unit for regulating the signal output by the at least one sensor and converting the signal from analog to digital. When executing multiple programmable instructions, at least one processing device may also be configured to detect and output processed characteristics of the signal.

[0023] In one or more embodiments, when executing multiple programmable instructions, at least one processing device may also be configured to transition to a warning notification state when a normal criterion is not met to buffer the processed characteristics of a signal, then transition to a fault state, transition from the fault state to a warning notification state when a tripping condition is not met to indicate that a warning event has been detected, transition from the warning notification state to a communication state to output a warning event notification and the contents of the buffer, and transition from the warning notification state to a normal state.

[0024] In another aspect of this disclosure, an edge device for monitoring electrical faults is disclosed. The edge device includes a memory configured to store a plurality of programmable instructions and at least one processing device communicating with the memory. Upon execution of the plurality of programmable instructions, the at least one processing device is configured to receive one or more warning event notifications from a circuit breaker, wherein each warning event notification is based on the detection of a transition mode between operating states of the circuit breaker. Operating states include a normal state and a fault state. In the normal state, processed characteristics of signals sensed by the circuit breaker meet normal criteria; in the fault state, normal criteria are not met. The mode includes a series of transitions, including transitioning from the normal state to the fault state and back to the normal state. Upon execution of the plurality of programmable instructions, the at least one processing device is configured to determine a probability of impending tripping based on the one or more warning notifications and output an impending trip notification according to the determined probability.

[0025] In one or more embodiments, a warning event notification may include a warning duration indicating the duration during which the circuit breaker is not operating in a normal state, wherein the probability of an impending trip may be determined based on a parameter and / or a variation of one or more parameters, including at least one of the number of warning event notifications, the warning duration, and the duration between warning event notifications.

[0026] In one or more embodiments, when executing multiple programmable instructions, at least one processing device may also be configured to receive warning data with a warning event notification, wherein the warning data may include any processed feature that is a function of the electrical characteristics of a circuit branch connecting the circuit breaker to one or more loads sensed after the circuit breaker transitions from a normal state. The electrical characteristics may be sensed by the circuit breaker, and the probability of an impending trip may be determined based on changes in the processed feature.

[0027] In one or more embodiments, when executing multiple programmable instructions, at least one processing device may also be configured to decompose warning data to identify which of one or more loads is energized or operating when the corresponding electrical characteristic is sensed, wherein the probability of an impending trip may also be a function of the operation of the identified one or more loads.

[0028] In one or more embodiments, when executing multiple programmable instructions, at least one processing device may also be configured to apply at least one model to determine when to output an impending trip notification, and / or apply machine learning, statistical and / or numerical techniques to train and / or apply at least one model.

[0029] In one or more embodiments, the trip notification may be output wirelessly to a user equipment and / or via a network to a remote device.

[0030] In an additional aspect of this disclosure, a non-transitory computer-readable storage medium having one or more computer programs embedded therein is disclosed. When executed by a computer system, the non-transitory computer-readable storage medium causes the computer system to receive one or more warning event notifications from a circuit breaker, wherein each warning event notification is based on the detection of a transition mode between operating states of the circuit breaker. Operating states include a normal state and a fault state; in the normal state, processed characteristics meet normal criteria, and in the fault state, normal criteria are not met. The mode includes a series of transitions, including transitioning from the normal state to the fault state and back to the normal state. When executed by the computer system, the non-transitory computer-readable storage medium also causes the computer system to determine the probability of an impending trip based on the one or more warning event notifications and output an impending trip notification according to the determined probability.

[0031] In an additional aspect of this disclosure, a non-transitory computer-readable storage medium having one or more computer programs embedded therein is disclosed. When executed by a computer system, the non-transitory computer-readable storage medium causes the computer system to process characteristics of signals output by at least one sensor of a circuit breaker regarding electrical properties of a circuit coupled to a load, and to transition between operating states based on the processed characteristics. The operating states include a normal state, a fault state, and a trip state. The operating state remains in the normal state until the processed characteristics no longer meet the normal criteria, after which the operating state transitions to the fault state. When the trip condition is not met, the operating state transitions from the fault state back to the normal state, and when the trip condition is met, the operating state transitions to the trip state. When executed by the computer system, the non-transitory computer-readable storage medium also causes the computer system to detect warning events when the operating state transitions from the normal state to the fault state and back to the normal state, and to output a warning event notification when a warning event is detected.

[0032] These and other features of the systems and methods disclosed herein will become more apparent to those skilled in the art from the following detailed description of preferred embodiments in conjunction with the accompanying drawings. Attached Figure Description

[0033] A more detailed description of the present disclosure, which has been briefly outlined above, can be obtained by referring to various embodiments, some of which are illustrated in the accompanying drawings. While the drawings show preferred embodiments of the present disclosure, they should not be considered as limiting its scope, as the present disclosure may allow for other equally effective embodiments.

[0034] Figure 1 This is a block diagram illustrating an example circuit management system according to an embodiment of the present disclosure;

[0035] Figure 2 According to embodiments of this disclosure Figure 1 Example flowchart of circuit breakers in a circuit management system;

[0036] Figure 3 According to embodiments of this disclosure Figure 2 The diagram shows an example state machine diagram of the circuit breaker.

[0037] Figure 4 According to embodiments of this disclosure Figure 1 A flowchart illustrating the example operation of a circuit management system;

[0038] Figures 5A-5D An embodiment according to this disclosure is shown in Figure 3 Flowcharts of example methods executed in different states of a state machine; and

[0039] Figure 6 This is an implementation of an embodiment based on the present disclosure. Figure 1 A block diagram of an exemplary computer system for any smart device shown.

[0040] Where possible, the same reference numerals are used to denote the same elements common in the figures. However, elements disclosed in one embodiment may be advantageously used in other embodiments without specific description. Detailed Implementation

[0041] Reference will now be made to the accompanying drawings, wherein like reference numerals denote similar structural features or aspects of the subject matter disclosed. For purposes of explanation and illustration, and not limitation, schematic diagrams of exemplary embodiments of the circuit management system according to this disclosure are shown in... Figure 1 As shown in the figures, and generally indicated by reference numeral 100. Other embodiments of the circuit management system according to this disclosure, or aspects thereof, are shown in... Figures 2-6 As will be described in the text.

[0042] The circuit management system 100 includes a load center 102, which includes one or more circuit breakers 104. The circuit breakers 104 are configured to communicate with an edge device 106. The communication between the circuit breakers 104 and the edge device 106 may have a fixed bandwidth. Each circuit breaker 104 is coupled to a circuit called a branch 108, which includes an interface to one or more loads 110 (e.g., appliances, motors, etc.). Each circuit breaker 104 senses the electrical characteristics of its corresponding branch 108 and may be configured to detect conditions associated with branch 108 that could lead to an unwanted trip (referred to as a harmful trip) (where the switch of the circuit breaker 104 is controlled to interrupt current) and provide a warning to the edge device 106. The edge device 106 receives data from the circuit breakers 104 (including, for example, a warning of a potential harmful trip) and processes it further. Edge device 106 can communicate with external user device 120 (such as mobile computing device, desktop computer, server, etc.) and / or cloud-based server 122, such as to provide received data and the results of processing the received data.

[0043] Communication between circuit breaker 104 and edge device 106, and communication between edge device 106 and user equipment, can use wireless communication, such as near-field communication or WiFi communication (e.g., using ZigBee). TM ,Bluetooth TM Low Energy (BLE), Bluetooth TM (BL)4.0, WiFi, and other protocols, but not limited to these). It should also be understood that communication between edge device 106 and user equipment 106 and / or server 122 may include wired communication and optional wireless communication via a network (such as a local area network (LAN) or a wide area network (WAN) (such as the Internet)).

[0044] Circuit breaker 104, edge device 106, user equipment 120, and server 122 include processing devices operatively connected to and / or integrated into memory and a communication interface for communicating with other components of the circuit monitoring system 100, as described. The processing device may include, for example, a microcontroller, microprocessor, programmable logic device (PLD), digital signal processor (DSP), field-programmable gate array (FPGA), application-specific integrated circuit (ASIC), and / or other discrete or integrated logic circuits with similar processing capabilities. In one or more embodiments, circuit breaker 104 and / or edge device 106 may be configured as embedded devices, respectively.

[0045] Harmful tripping can occur due to arcing faults, ground faults, or grounded neutral faults. For example, arcing faults can occur when a load wears out and no longer performs according to its specifications, a load emits high-frequency (HF) noise due to persistent internal damage or poor design, connections on wiring nuts and / or joints are intermittent, cables are damaged or crushed, and / or connections on sockets and / or switches are loose. Ground faults can occur when there is current leakage from load 110, rapid transients and / or spikes in the current or voltage causing high-frequency current leakage to the associated branch 108, and / or slow wear of load 110 and / or damage to the isolation of the associated cables. Grounded neutral faults occur when there is an error in the wiring between the neutral and ground wires, shared neutral wires, etc. This is usually detected before any load is energized and assists the electrician in checking the wiring by tripping. However, some loads can generate signals that interfere with the operation of ground fault detection in the circuit breaker, and the correct impedance between the neutral and ground wires is not measured correctly, resulting in a harmful trip.

[0046] Conventional circuit breakers with Arc-Fault Circuit Interruption (AFCI) and / or Ground-Fault Circuit Interruption (GFCI) circuits may trip due to harmful tripping, but are not configured to collect information about the cause of the harmful tripping or provide supplementary information. Users and manufacturers lack information about how the load is aging and / or wearing down. Newer circuit breakers may have increased sensitivity for detecting electrical faults, potentially increasing the occurrence of harmful tripping. However, harmful tripping without information about the cause is unhelpful.

[0047] Conversely, according to this disclosure, each circuit breaker 104 is equipped with a state machine and an electrical fault algorithm that generates a warning event when the state machine transitions from a normal state to a fault (arc, ground fault, or ground neutral fault) state and returns to the normal state. Furthermore, circuit breaker 104 stores queued data regarding low-frequency (LF) and high-frequency characteristics extracted from the electrical characteristics sensed by circuit breaker 104. Each time a warning event is detected, a warning event notification, along with HF and LF characteristic data (also referred to as warning data) including queued data associated with the warning event, is provided to edge device 106. Since circuit breaker 104 has transitioned back to the normal state, circuit breaker 104 continues to operate and queues the data. If another warning event occurs, edge device 106 receives an associated warning event notification with updated associated warning data.

[0048] Edge device 106 can provide server 122 with all or selected data received from circuit breaker 104 (e.g., metering data, warning data, and warning event notifications). In one or more embodiments, edge device 106 may serve solely as a conduit between circuit breakers 104 by transmitting data between circuit breaker 104 and server 122. In one or more embodiments, any analytics device 124, including edge device 106, user equipment 120, and server 122, can receive and process data output from circuit breaker 104 and / or exchange the results of such processing.

[0049] Any analysis device 124 (also referred to individually or collectively as analysis device 124) can process and / or (using associated storage devices) store data output from circuit breaker 104. The storage device may be provided by storage devices accessible to analysis device 124. Analysis device 124 can process the circuit breaker's output data by (e.g., based on loads identified as associated with a particular circuit breaker 104) using any known or undiscovered techniques to decompose warning data and pair the decomposed warning data with the identified loads.

[0050] The analysis device 124 can also build statistical models based on warning data and other parameters such as the frequency of warning events, the duration of warning events (typically measured in half-cycles, e.g., the duration of a fault state that is measured not to cause a trip (e.g., the start of a transition from a normal state to a fault state and back to a normal state)). In this way, the circuit breaker 104 with sensitive arc fault and / or ground fault detection hardware can apply electrical fault detection algorithms to provide multiple instances of queuing data to the edge device 106. The analysis device 124 can use the warning data to create historical data to infer or predict, for example, load wear or aging conditions and / or future tripping.

[0051] This prediction can be made using probabilistic learning methods. Probability can include multiple dimensions of the collected information space. The information space is any combination of HF and LF features, but is not limited to warning duration, warning frequency, etc.

[0052] In one or more embodiments, the analysis device 124 can generate a model for the load. The analysis device 124 can determine a timeline of load operation. The timeline can be implemented to determine the time of use and the frequency of warning events (e.g., based on the load's operation over time without triggering any warning events). Once the circuit breaker 104 triggers one or more warning events, the analysis device 124 can determine and update the probability of the warning events over time based on load operation and the occurrence of other warning events. Initially, the probability may be low, increasing as the frequency of warning events increases in association with load operation. For example, the probability of an impending trip may increase when there are isolated occurrences of warning events or incidental occurrences spaced sufficiently long apart. However, the probability of an impending trip may increase due to certain conditions, such as an increased frequency of warning events, a reduced number of instances of normal operation between warning events, or a threshold number of consecutive warning events (which may increase). The conditions shown are intended as examples only and are not an exhaustive list of conditions.

[0053] Once the probability of a warning event reaches a threshold probability (e.g., a 50% or 75% probability, but not limited to a specific threshold probability), the analysis device 124 can (e.g., via user equipment 120) output an impending trip notification to the user and / or a third party (e.g., the load manufacturer, a service company that repairs the load, an appliance rating agency, etc.) indicating a potential future trip. The notification to the manufacturer may include warning data and provide the manufacturer with information about the product's lifespan or maintenance requirements. The manufacturer can pass this information to users to help them use the appliance more effectively, and / or the appliance rating agency can use this information to rate the appliance to help consumers choose which appliance to purchase. For example, the manufacturer may automatically exchange recall information with customers based on receiving an impending trip notification or warning data.

[0054] The analysis device 124 can perform further analysis on the warning data to provide more insights. For example, when a specific load consistently triggers warning events from circuit breaker 104, the analysis device 124 can track parameters (such as the duration of the warning event or values ​​included in the associated warning data) to determine if the parameters increase over time. As the duration of the warning event increases, it is likely that the duration will eventually reach a predetermined tripping time limit, causing circuit breaker 104 to trip. A warning event duration threshold can be implemented so that once the warning event duration reaches the threshold, an impending tripping notification is sent to the user or a third party.

[0055] In one or more embodiments, the analysis device 124 may generate a second model based on values ​​of warning data received from the circuit breaker 104, in association with one or more warning events corresponding to a specific load. For example, changes in radio frequency (RF) energy and / or low-frequency current measurements relative to warning data associated with a previous warning event may indicate a stability deviation relative to previous operation of the load. This could be an indication that the load is worn down and may eventually experience abnormal operation that could trip the circuit breaker 104.

[0056] In one or more embodiments, the analysis device 124 may use multiple load-specific models and / or implement machine learning techniques to facilitate model building scenarios. A K-nearest neighbor (KNN) prediction algorithm based on a feature set and feature region space created according to a similarity metric can be used as a way to identify upcoming trips. In other embodiments, a Naive Bayes model may also be utilized, where feature data clustering and metadata allow for estimation of the classification to trigger an impending trip notification to the user. The analysis device 124 can thus understand the operation of various loads coupled to the load center 102 based on associated warning events and, for example, create statistical and / or numerical models for each load. For example, the mean time between warning events and the frequency of occurrence of warning events relative to load operation can be used and / or modeled to send notifications to users of impending trips.

[0057] Furthermore, in one or more embodiments, the analytics device 124 may participate in crowdsourcing, where multiple edge devices 106 report warning events and provide associated warning data to the server 122 to update and / or train the models(s) for each load over time. The models(s) may set criteria to trigger notifications of impending trips.

[0058] When the edge device 106 is not the analysis device 124 that determines an impending trip, it can respond to an external diagnostic request using diagnostic mode information output when the circuit breaker is operating in diagnostic mode. User equipment 120 or server 122 can operate as analysis device 124 to determine an impending trip and output an impending trip notification. When the edge device is the analysis device 124 that determines an impending trip, it can respond to an external diagnostic request using trip history information including the impending trip notification and associated timestamps.

[0059] Therefore, user equipment 120 or server 122 can receive notification of an impending trip or determine the likelihood of an impending trip. This can provide users or third parties with an early warning of a potential trip that may be associated with a specific load, or clarify that a harmful trip is an indication of an impending, actual (desired) trip. Notification of an impending trip can provide users and / or third parties with information for taking action (e.g., repairing or replacing the load). Early action can prevent load 110 from failing at an inconvenient time, such as a washing machine failing when full of water or an oven failing on holiday dinner day.

[0060] Given that conventional circuit breakers equipped with enhanced arc fault detection components are primarily sensitive to RF (radio frequency) signals in the 1MHz to 40MHz bandpass region, the potential advantages of circuit monitoring system 100 can be demonstrated. Many loads in a household do not generate RF noise in this bandpass region, except for some loads where actual arcing currents exist in motor brushes or where high-frequency switching of some power supplies occurs (e.g., fluorescent lamp ignition). When these loads are operating, the sensed RF signals may exhibit certain expected repetitive patterns, which the enhanced arc fault detection components can filter out. However, when these RF signals begin to change and their repetitive patterns alter, a conventional circuit breaker equipped with enhanced arc fault detection may experience a potentially non-hazardous arc fault, in which the circuit breaker's detection state machine transitions from a normal state to a fault state and back to a normal state without the user's knowledge.

[0061] Conversely, when enhanced arc detection is used by the circuit breaker 104 in the circuit monitoring system 100, a non-hazardous arc fault triggers a warning event. Analysis device 124 tracks these warning events and can detect changes in patterns. Analysis device 124 can apply one or more models to determine whether the change in pattern is an indication of an impending trip and notify the user accordingly. The models can be enhanced by collecting data from multiple edge devices 106 via server 122 using various techniques such as machine learning, statistical, and / or digital technologies.

[0062] refer to Figure 2 And continue to refer to Figure 1 A block diagram of an example configuration of circuit breaker 104 is shown. Circuit breaker 104 includes one or more arc fault sensors and analog front-ends (AFEs) 202A, one or more ground fault sensors and AFEs 202B, a processor 204, a trip unit 212, and an optional self-testing device 220. The processor 204 is shown as including a signal acquisition unit 206, a feature processing unit 208, a state machine 210, a metering and communication unit 214, and a warning notification unit 216.

[0063] Processor 204 may include one or more processing devices and may be implemented in hardware, software, and / or firmware (such as any of a microcontroller, microprocessor, ASIC, PLD, or FPGA). In one or more embodiments, any of the signal acquisition unit 206, feature processing unit 208, state machine 210, metering and communication unit 214, and warning notification unit 216 may be external to processor 204 and accessible by processor 204. One or more other components of circuit breaker 104, or a portion thereof, may be integrated with processor 204.

[0064] The sensors (one or more) of the arc fault sensor and AFE sensor 202A and (one or more) of the ground fault sensor and AFE 202B sense physical characteristics and output analog voltage or current signals. Examples of physical characteristics include real-time signals and associated electrical characteristics of the branch 108 to which the circuit breaker 104 is coupled. The sensors can sense, for example, line current, line voltage, RF signals, received signal strength indication (RSSI) of the sensed signal, and differential current, but are not limited to these specific electrical characteristics. The sensors can be configured to monitor one or more of the following: arc fault, ground fault, grounded neutral, power consumption, etc.

[0065] The AFE circuitry of one or more arc fault sensors and AFE 202A and one or more ground fault sensors and AFE 202B includes a set of analog signal conditioning circuitry for conditioning the sensed signal to interface with other components of the circuit breaker 104, such as antennas, analog-to-digital (A / D) converters, microcontrollers, etc.

[0066] The signal acquisition unit 206 includes an A / D converter configured to continuously convert analog sensor signals from one or more arc fault sensors and AFE 202A and one or more ground fault sensors and AFE 202B into digital sensor signals (e.g., signals with a network frequency of 50 Hz or 60 Hz) for each half-cycle signal along the corresponding branch 108. The digital sensor signals have a level corresponding to the analog voltage or current signals sensed by the one or more arc fault sensors and AFE 202A and one or more ground fault sensors and AFE 202B.

[0067] The feature processing unit 208 is configured (e.g., using signal processing techniques) to receive and process digital sensor signals, and to calculate and output feature data of characteristics determined based on the digital sensor signals. These features represent the electrical properties of the circuit that couples the circuit breaker 104 to one or more loads 110. The feature data includes values ​​such as peak current (Ipeak), root mean square (RMS) current (Irms), peak voltage (Vpeak), RSSI conversion, RSSI signal-to-noise ratio (SNR), current phase (Iphase), RSSI energy, etc. The feature processing unit 208 outputs metering data (meaning power and energy measurements) to the communication unit 214 independently of the state machine 210.

[0068] State machine 210 (SM) applies a fault detection algorithm that detects faults in associated branches 108 that can be used to trigger tripping (e.g., controlling interruption current switching) – namely, arcing (in series or parallel with the load), grounding faults, and ground neutral faults. Dangerous arcing and grounding faults can be detected based on the profile of certain arcing or grounding fault half-cycles, as described in standards such as Insurer Laboratories (UL) and the International Electrotechnical Commission (IEC). However, there are also non-dangerous arcing or grounding fault half-cycles. For example, some arcing half-cycles are caused by rapid transients of load switching or normal operation of the load, or occur within a very short timeframe and do not lead to potential fire.

[0069] The trip unit 212 includes components for disconnecting the circuit of the circuit breaker 104, such as a solenoid, pneumatic element, or equivalent.

[0070] Metering and communication unit 214 acquires information collected by warning notification unit 216 and stored in one or more queues, and creates packets for transmission to edge device 106 via antenna 222 [or wired connection]. When a trip is triggered or a notification of an impending trip is received, metering and communication unit 214 outputs packets containing messages about the triggered trip or the impending trip, and further outputs packets containing warning data including information collected by warning notification unit 216. Metering and communication unit 214 further outputs metering data. Metering data may include basic data such as the integral of power over 1 second, RMS voltage, RMS current, etc. Metering data is transmitted at a relatively low rate (such as 0.5 Hz or 1 Hz). The rate at which metering data is transmitted can be configured to enable all circuit breakers 104 to transmit metering data to edge device 106 when operating in normal mode.

[0071] Warning notification unit 216 collects feature data output by feature processing unit 208. For example, when state machine 210 transitions from a fault state to a normal state, HF feature data and LF feature data can be queued in HF queues and LF queues and prepared for output. HF queues and LF queues store feature data for high-frequency signals and low-frequency signals, respectively. When a warning event is triggered and HF feature data and LF feature data from HF queues and LF queues are output to edge computing device 106, warning notification unit 216 further sends an internal warning event notification to metering and communication unit 214. If included, system diagnostic unit 220 is configured to perform diagnostics on the internal circuitry of circuit breaker 204, such as self-tests. For example, system diagnostic unit 220 can perform diagnostics on one or more arc fault sensors and AFE 202A and one or more ground fault sensors and AFE 202B, the microcontroller (MCU) of processor 204, internal communication channels, the switch position of the circuit breaker, firmware and memory integrity, etc.

[0072] refer to Figure 3 And continue to refer to Figure 1 and Figure 2 An example diagram of state machine 210 is shown. State machine 210 can be implemented using software, hardware, and / or firmware. State machine 210 is configured to transition between multiple states, including normal state 302, warning notification state 304, fault state 306, trip state 308, and communication state 310. The fault state indicates that any potentially dangerous fault (e.g., arc fault, ground fault, or ground neutral fault) has been detected in order to protect the circuit, user, or customer.

[0073] Operation begins in normal state 302. During normal state 302, the feature data output by feature processing unit 208 is processed, and the fault accumulator variable is set to 0. The feature data may include HF feature data corresponding to the extracted HF feature and LF feature data corresponding to the extracted LF feature. In the provided example, the high frequency is above 1MHz, and the low frequency is between 10Hz and 10kHz. Operation continues in normal state 302 when the HF feature data and LF feature data meet normal criteria (such as no fault half-cycle detected). For example, an arc fault is identified when both the HF feature data and LF feature data indicate an arc fault half-cycle as defined in UL1699. A ground fault is identified when the differential current (leakage current) reaches a level defined by UL493. A ground neutral fault is identified when the impedance between the load-side ground and neutral is short-circuited or close to 0 ohms.

[0074] During normal operation, circuit breaker 104 continues as follows: Figure 2 The operation, as shown, includes acquiring, processing, and packaging the sensed data, and outputting the packaged data as metering data. The metering data is output via a communication unit and may include, for example, data used to monitor power consumption and energy usage. Operation remains in normal state 302 until it transitions to warning state 304.

[0075] Furthermore, when operating in normal state 302, the HF queue and LF queue are cleared. In normal state, state machine 210 does not output data to metering and communication unit 214 (although metering data can be output to communication unit 214 by feature processing unit 208).

[0076] Once the normal criteria are no longer met (e.g., due to the detection of a fault half-cycle), the operation departs from the normal state and eventually transitions to fault state 306. In fault state 306, tripping conditions are monitored. When the tripping conditions are met, the operation transitions to tripping state 308. When the tripping conditions are not met (e.g., within time constraints), the operation transitions back to normal state 302.

[0077] exist Figure 3 In the example shown, once the normal criteria are no longer met, the operation state transitions from normal state 302 to warning notification state 304, as indicated by arrow 311. In warning notification state 304, HF and LF characteristic data are started being stored in the HF and LF queues. Additionally, the fault accumulator is set to 1. Once the fault accumulator is greater than zero, the operation transitions to fault state 306, as indicated by arrow 313. This state can cycle between warning notification state 304 and fault state 306 until the warning event equals 1 due to an update of the warning event under fault state 306. When the warning event equals 1, the operation state transitions to communication state 310. In fault state 306, monitoring of tripping conditions is performed.

[0078] The trip time limit is determined based on the trip time standard defined in the standards for arc faults and / or ground faults. The trip time limit determines the duration for which state machine 210 can remain in fault state 306 before transitioning to trip state 308, causing the circuit breaker 104 to open one or more contacts to interrupt current flow. The trip time limit is typically determined in half-cycles or milliseconds (ms) based on the definition of the corresponding fault described in UL1699 or UL493 standards and the load rated current or leakage current. The fault accumulator increments for each half-cycle indicating a fault based on the LF characteristic data and HF characteristic data. A fault timer variable is started, which counts half-cycles while in fault state 306. In this way, fault state 306 can exit if the value of the trip limit has not reached the value of the fault accumulator. State machine 210 tracks the fault timer relative to the trip time limit and further tracks the fault accumulator relative to the trip time limit. Since the fault accumulator may not increment every half cycle, the value of the fault accumulator may remain below the trip limit, causing the operating state to change from fault state 306 to warning state 304, and may eventually change to normal state 302.

[0079] Each time a fault half-cycle is detected, the fault accumulator increments. When the fault accumulator reaches the trip time limit and the fault time equals the trip time limit, the trip condition is met, and the state of state machine 210 transitions to trip state 308, as shown by arrow 315.

[0080] Because the fault accumulator may not increment every half-cycle, its value may remain below the trip limit. If the fault accumulator does not reach the trip time limit, the trip condition is not met, and state machine 210 transitions back to warning notification state 304 (as shown by arrow 317), and then to normal state 302. When state machine 210 transitions back to warning notification state 304, the warning event variable is set to 1, and all HF and LF feature data in the HF and LF queues are output to communication state 310. Note that when state machine 210 transitions from fault state 306 to trip state 308, the warning event is not set to 1.

[0081] However, if the tripping time has reached the predetermined tripping time limit and the fault accumulator is less than the tripping time, the warning event is set to 1, indicating that the fault did not occur within the required tripping time defined by the corresponding standard, or that the fault was not serious enough to pose any danger to the circuit or the user. Because the tripping criteria are not met, operation returns to warning notification state 304, as shown by arrow 319. Once the warning event is set to 1, the state machine 210 transitions back to warning notification state 304, communication state 310, and then to normal state 302.

[0082] In trip state 308, the trip code identifying the detected fault type is output to the next state (communication state 310), and the switch is operated to disconnect the contacts and interrupt current flow. Furthermore, the operation proceeds to communication state 310.

[0083] In communication state 310, determine whether the trip code indicates a fault, such as an arc fault, ground fault, or grounded neutral fault. If any of these faults are indicated, the operation does not return to normal, and the operation of circuit breaker 102 ends.

[0084] If the operation returns from fault state 306 to warning notification state 304 via arrow 319, the warning event is set to 1. In warning notification state 304, if the warning event is equal to 1, the operation transitions to communication state 310 (as shown by arrow 321) and outputs the queued LF characteristic data and HF characteristic data.

[0085] In communication state 310, if the warning event equals 1 (true if it is determined that no fault exists but a warning event does exist), a warning event notification with the contents of the HF queue and the LF queue is output. Furthermore, when the warning event equals 1, this indicates that no fault has occurred. Accordingly, when it is determined that the warning event equals 1, thus indicating that no fault has occurred, the operation returns to normal state 302, as shown by arrow 323.

[0086] In this way, whenever state machine 210 transitions from normal state 302 (via warning notification state 304) to fault state 306 and returns to normal state 302 (via communication state 310), a warning event has occurred, resulting in a warning event notification being output to edge device 106. The contents of the HF queue and LF queue are also output to edge device 106 in association with each warning event notification. The HF and LF characteristics included in the HF and LF queues can provide information indicating the source of the warning event, which is broken down by load and / or monitored to determine an impending trip or the need for maintenance or removal of a load, outlet, or cable.

[0087] Note that HF ​​and LF data are only provided to communication state 310 when a warning event is detected, because HF and LF data require higher bandwidth than metering data. When state machine 210 transitions to fault state and thus to trip state, the trip code variable is sent to communication state (as shown by arrow 317), and the circuit is interrupted.

[0088] Edge device 106 is capable of breaking down metering data to determine the load operating at any given time and associating received warning event notifications or impending trip notifications to be output with specific circuit breakers 104 and / or specific loads. When edge device 106 receives a warning event notification, it can provide metadata identifying the specific circuit breaker 104 and / or load 110 associated with the warning event notification or impending trip notification. The metadata identifies the circuit breaker 104 and / or load 110 associated with each warning event notification and impending trip notification. In one or more embodiments, the metadata may include additional information such as the name and / or model (e.g., Kenmore) of the identified load 110. TM Vacuum cleaner or General Electric TM The washing machine (model #GTW465ASNWW) is an example. Additionally, HF and LF characteristic data associated with warning event notifications and / or impending trip notifications are analyzed. Analysis may include using metadata and the associated HF and LF characteristic data to build statistical models and / or compare against statistical models based on the HF and LF characteristic data associated with the warning event notifications. The results of the comparison can be used to take actions such as sending an impending trip notification or recommending replacement or repair.

[0089] In one or more embodiments, user equipment 108 may submit a monitoring request to edge device 106. In one or more embodiments, the monitoring request identifies one or more circuit breakers 104 for which metering data is requested. In one or more embodiments, the monitoring request may identify one or more, or all, circuit breakers 104 selected by user equipment 108 to receive metering data and / or metadata. In one or more embodiments, the monitoring request may identify one or more, or all, loads 110 selected by user equipment 108 to receive metering data and / or metadata. In one or more embodiments, edge device 106 may aggregate only the metering data and / or metadata of the circuit breaker(s) 104(s) or load(s) 110(s) identified by the monitoring request. Furthermore, in one or more embodiments, edge device 106 may only send the metering data or metadata requested by the circuit breaker(s) 104(s) or load(s) 110(s) identified by the user.

[0090] The load can be identified in the monitoring request (e.g., by brand name, load name, type, and / or model), such as Kenmore. TM Vacuum cleaner or General Electric TM Humidifiers, etc. Edge device 106 can respond to a monitoring request by providing user device 108 with, for example, a list of each load that is operating at the time the monitoring request is received. In one or more embodiments, the list can identify the circuit breaker 104 to which each identified load is connected. A user of user device 108 can select one or more loads from the list and send an updated monitoring request identifying the selected one or more loads. In response, edge device 106 can send metering data and / or metadata for the identified loads.

[0091] Figure 4 and Figures 5A-5D An exemplary and non-limiting flowchart is shown, illustrating a method for generating a software application according to some of the illustrated embodiments. (Progress to...) Figure 4 and Figures 5A-5D Before describing, please note that Figure 4 and Figures 5A-5D The flowchart illustrates an example in which operation boxes are executed in a specific order, as indicated by the lines showing the flow between operation boxes; however, the individual boxes shown in the flowchart may be executed in a different order or in different combinations or sub-combinations. It should be understood that in some embodiments, some of the boxes described below may be combined into a single box. In some embodiments, one or more additional boxes may be included. In some embodiments, one or more boxes may be omitted.

[0092] refer to Figure 4 And continue to refer to Figures 1-3 A process flow diagram 400 is shown based on one or more embodiments of an example flow between circuit breaker 104, edge device 106, and / or server 122 in load center 102 and user device 120. It should be understood that any of the processing, storage, transformation, and correlation tasks shown and described can be performed by another device (such as user device 120 or server 122) with appropriate authentication, authorization, and communication capabilities for analytics device 124.

[0093] The operations performed by circuit breaker 104 are shown in column 402, the operations performed by edge device 106 are shown in column 404, and the operations performed by user application 120 are shown in column 408.

[0094] In operation 404, circuit breaker 104 (e.g., by means of installation in load center 102) is enabled, which allows the AFE circuits of one or more arc fault sensors and AFE 202A and one or more ground fault sensors and AFE 202B of circuit breaker 104 to begin acquiring data. In process 401, communication is established between edge devices 106 (e.g., via appropriate handshake). In process 403, communication is established between edge devices 106 and / or server 122 and user equipment 108 (e.g., via appropriate handshake and authentication of user credentials). User equipment 108 executes a monitoring application that enables user equipment 108 to communicate with edge devices 106 and / or server 122 and perform associated operations. In process 405, a monitoring request is sent from user equipment 405 to edge device 106, such as a request for monitoring data that may include metering data and / or metadata. Monitoring requests can be generated based on user input via a user interface (e.g., a graphical user interface (GUI), a text interface, a switch panel, etc.) or based on decisions made by the processing device of user equipment 108. In one or more embodiments, the monitoring application executed by user equipment 120 presents a GUI on user equipment 120.

[0095] In response to receiving a monitoring request, edge device 106 sends a data request to circuit breaker 104 at process 407. In response to the data request from the edge device, circuit breaker 104 accesses the collected samples for processing at operation 408, processes the metering data at operation 410, and packages the processed metering data at 412. One or more packets are sent to edge device 106 at process 409. During normal operation, the outputs of operations 408, 410, 412, and process 409 can be repeated periodically. This corresponds to state machine 210 remaining in normal state 302, as... Figure 3 As indicated by the middle arrow 309.

[0096] After edge device 106 receives the packaged metering data, in operation 424, edge device 106 and / or server 122 process the packaged metering data and store the packaged metering data and / or processing results in an associated storage device. In operation 426, edge device 106 and / or server 122 convert the packaged metering data and / or processing results into metadata. In process 411, the metadata is output to the user equipment. The monitoring application executed by user equipment 122 uses the received metadata to update and refresh the stored and displayed data. If circuit breaker 104 is identified in the monitoring request and / or associated with a load identified in the monitoring request, the metadata sent in process 411 may be associated only with that circuit breaker 104. After receiving the metadata at process 409, operations 424, 426, and process 411 are repeated.

[0097] The deviation from normal operation is shown at operation 414, which processes the warning data. This occurs because circuit breaker 104 detects a fault, causing it to transition from normal state 302 to fault state 306 and then back to normal state 302. Figure 2 In the example state machine 210 shown, these transitions occur via warning notification state 304. These transitions also result in transmissions to and from communication states, via which warning event notifications and warning data are issued. After processing the warning data (and warning event notification), in operation 412, the warning data and warning event notification are packaged. Metering data may also be packaged in operation 412. The packet sent at process 409 includes the packaged warning data and warning event notification.

[0098] After edge device 106 receives the packaged metering data, warning data, and warning event notifications, edge device 106 and / or server 122 perform operations 424 and 426, followed by operation 430. In operation 430, the warning data is processed (e.g., by decomposing the warning data by load, associating the decomposed warning data with the load, comparing it with historical data, updating historical data, determining whether a specific load is about to trip, etc.). In block 430, it can be determined (e.g., based on one or more statistical models) whether the received warning event notification has reached a threshold, thereby determining an impending trip. If an impending trip is determined, then in process 411, the impending trip notification is included along with metadata sent to the user equipment. In one or more embodiments, the metadata may also include an identifier of the abnormal load and a possible cause of the impending trip, a predicted probability of the impending trip, recent characteristic data, information records output by one or more models, etc.

[0099] When user equipment 120 receives metadata containing notification of an impending trip, an application executed by the user equipment causes a warning to be displayed to notify the user of the impending trip.

[0100] refer to Figures 5A-5D The flowchart shows an example method executed in different states of state machine 210. Figure 5AA flowchart 500 illustrates an example method when state machine 210 is in the normal state. The method begins at block 502. In block 504, the LF feature is processed. In block 506, the HF feature is processed. In block 508, it is determined whether the LF and HF features indicate a fault half-cycle. If the determination at block 508 is "No," meaning the LF and HF features do not indicate a fault half-cycle, the method continues at block 510, where the fault accumulator is set to 0. If the determination at block 508 is "Yes," meaning the LF and HF features do indicate a fault half-cycle, the method continues at block 512. In block 512, state machine 210 transitions to the warning notification state.

[0101] Figure 5B A flowchart 520 illustrates an example method when state machine 210 is in the warning notification state. The method begins at block 522, where the fault accumulator is set to 1. At block 524, the LF characteristic value is collected. At block 526, the HF characteristic value is collected. At block 530, it is determined whether the warning event is equal to 1. If the determination at block 528 is "yes," meaning the warning event is equal to 1, the method continues at block 532. At block 532, the state of state machine 210 transitions to the communication state. If the determination at block 530 is "no," meaning the warning event is not equal to 1, the method continues at block 534. At block 534, the state of state machine 210 transitions to the fault state.

[0102] Figure 5C A flowchart 540 illustrates a simplified example method when state machine 210 is in a fault state. While flowchart 540 is not intended to be a specific method for determining when to transition to one of the next states, it illustrates that a transition to a trip state or a warning state can be determined.

[0103] The method begins at box 542, where the trip time limit value is determined. At box 544, a fault timer is started. At box 546, it is determined whether the LF and HF characteristics indicate a fault half-cycle. If the determination at box 544 is "yes," meaning the LF and HF characteristics do indeed indicate a fault half-cycle, the method continues at box 550, where the fault accumulator is incremented, and then the method continues at box 552. If the determination at box 548 is "no," meaning the LF and HF characteristics do not indicate a fault half-cycle, the method bypasses box 550 and continues at box 552. At box 552, it is determined whether the fault timer equals the trip time limit. If the determination at box 552 is "no," meaning the fault timer does not equal the trip time limit, the method continues at box 548, forming a loop. If the determination at box 552 is "yes," meaning the fault timer equals the trip time limit, the method continues at box 554.

[0104] In box 554, determine if the fault accumulator is less than the trip time limit. If the determination at box 554 is "yes," meaning the fault accumulator is less than the trip time limit, the method continues at box 556, where the warning event is set to 1. The method continues at box 558, where state machine 210 transitions to the warning notification state. If the determination at box 554 is "no," meaning the fault accumulator is not less than the trip time limit, the method continues at box 560, where the trip code is set to the fault type. The method continues at box 562, where state machine 210 transitions to the trip state.

[0105] Figure 5D A flowchart 570 illustrates an example method when state machine 210 is in the communication state. The method begins at block 572. In block 574, it is determined whether the trip code is set to any one of AF (indicating arc fault), GF (indicating ground fault), and GN (indicating ground neutral fault). If the determination at block 574 is "No," meaning the trip code is not set to any of AF, GF, or GN, the method continues at block 576. In block 576, LF features are dequeued (removed from their queue). In block 578, HF features are dequeued (removed from their queue). In block 580, a warning event notification is prepared, which includes LF and HF feature values ​​and a fault accumulator. In block 582, the warning event notification is output. In block 584, state machine 210 transitions to the normal state.

[0106] If the determination at box 574 is "Yes", meaning the trip code is set to any of AF, GF, or GN, then the method continues at box 576. At box 586, prepare the trip message. At box 588, output the trip message.

[0107] refer to Figure 6 A block diagram of an example computing system 600 is shown, providing an example configuration of device A1 implemented using an example processing system. Device A1 can be any intelligent element included in the circuit management system 100, such as circuit breaker 104, edge device 106, user equipment 120, and / or server 122. Furthermore, portions of device A can be configured as software, and computing system 600 can represent such portions. Computing system 600 is merely an example of a suitable system and is not intended to impose any limitation on the scope of use or functionality of the embodiments of this disclosure described herein. Computing system 600 can be implemented using hardware, software, and / or firmware. In any case, computing system 600 is capable of implementing and / or performing the functions set forth in this disclosure.

[0108] The computing system 600 is shown in the form of a general-purpose computing device. The computing system 600 includes a processing device 602, a memory 604, an input / output (I / O) interface (I / F) 606 capable of communicating with internal components (such as a user interface 610), and optional external components 608. The processing device 602 may include, for example, a programmable logic device (PLD), a microprocessor, a DSP, a microcontroller, an FPGA, an ASIC, and / or other discrete or integrated logic circuits with similar processing capabilities.

[0109] Processing device 602 and memory 604 may be included in components provided, such as FPGAs, ASICs, microcontrollers, or microprocessors. Memory 604 may include, for example, volatile and non-volatile memory for temporary or long-term data storage and for storing programmable instructions executable by processing device 602. Memory 604 may be a removable (e.g., portable) memory for storing program instructions. I / OI / F 606 may include interfaces and / or conductors for coupling to one or more internal components 610 and / or external components 608.

[0110] These computer program instructions may also be stored in a computer-readable medium that can instruct a computer, other programmable data processing apparatus or other device to operate in a particular manner, such that the instructions stored in the computer-readable medium produce an article of writing which includes instructions that implement the functions / actions specified in one or more boxes of a flowchart and / or block diagram.

[0111] Computer program instructions may also be loaded onto a computer, other programmable data processing apparatus or other device to cause a series of operations to be performed on the computer, other programmable apparatus or other device, thereby producing a computer-implemented process, such that the instructions, which execute on the computer or other programmable apparatus, provide a process for implementing the function / action specified in one or more blocks of a block diagram.

[0112] Embodiments of device A1 may be implemented or performed by one or more computer systems, such as microprocessors. Each computer system 600 may be included within device A1 or multiple instances thereof. In the example shown, the computer system is embedded within device A1. In various embodiments, computer system 600 may include one or more of a microprocessor, FPGA, application-specific integrated circuit (ASIC), or microcontroller. Computer system 600 may be provided as an embedded device. Parts of computer system 600 may be provided externally, such as via a centralized computer.

[0113] Computer system 600 is merely one example of a suitable system and is not intended to impose any limitation on the scope or functionality of the embodiments of this disclosure described herein. In any case, computer system 600 is capable of implementing and / or performing any of the functions set forth above.

[0114] Computer system 600 can be described in the general context of computer system executable instructions, such as program modules executed by the computer system. Typically, program modules may include routines, programs, objects, components, logic, data structures, etc., that perform specific tasks or implement specific abstract data types.

[0115] Various embodiments have been referenced above. However, the scope of this disclosure is not limited to the embodiments specifically described. Rather, any combination of features and elements described, whether or not associated with different embodiments, is considered to be an implementation and practice of the contemplated embodiments. Furthermore, while embodiments may achieve advantages over other possible solutions or prior art, whether a given embodiment achieves a particular advantage does not limit the scope of this disclosure. Therefore, the foregoing aspects, features, embodiments, and advantages are merely illustrative and should not be considered as elements or limitations of the appended claims unless expressly stated in the claims(s).

[0116] The various embodiments disclosed herein can be implemented as systems, methods, or computer program products. Accordingly, these aspects can take the form of entirely hardware embodiments, entirely software embodiments (including firmware, resident software, microcode, etc.), or embodiments combining software and hardware aspects (generally referred to herein as "circuit," "module," or "system"). Furthermore, these aspects can take the form of computer program products embodied in one or more computer-readable media on which computer-readable program code is contained.

[0117] Any combination of one or more computer-readable media may be used. The computer-readable medium may be a non-transitory computer-readable medium. A non-transitory computer-readable medium may be, for example, but not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatuses, or devices, or any suitable combination of the foregoing. More specific examples (not an exhaustive list) of non-transitory computer-readable media may include: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable optical disc read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing. Program code embodied on a computer-readable medium may be transmitted using any suitable medium, including but not limited to wireless, wired, fiber optic cable, RF, etc., or any suitable combination of the foregoing.

[0118] Computer program code used to perform the operations of various aspects of this disclosure can be written in any combination of one or more programming languages. Furthermore, such computer program code can be executed using a single computer system or multiple computer systems communicating with each other (e.g., using a local area network (LAN), wide area network (WAN), the Internet, etc.). While various features have been described for the foregoing with reference to flowchart illustrations and / or block diagrams, those skilled in the art will understand that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer logic (e.g., computer program instructions, hardware logic, combinations of both, etc.). Typically, computer program instructions can be provided to processor(s) of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus. Furthermore, executing such computer program instructions using processor(s) produces a machine capable of performing the functions or actions specified in one or more blocks of the flowchart and / or block diagram.

[0119] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and / or operation of various embodiments of this disclosure. In this regard, each block in a flowchart or block diagram may represent a module, code segment, or code portion comprising one or more executable instructions for implementing the specified logical function(s). It should also be noted that in some alternative embodiments, the functions marked in the blocks may not appear in the order indicated in the figures. For example, two blocks shown consecutively may actually be executed substantially simultaneously, or these blocks may sometimes be executed in reverse order, depending on the functions involved. It will also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, may be implemented by a system based on dedicated hardware or a combination of dedicated hardware and computer instructions that performs the specified function or action.

[0120] It should be understood that the above description is intended to be illustrative and not limiting. Many other implementing examples will become apparent upon reading and understanding the above description. Although specific examples are described herein, it should be recognized that the systems and methods of this disclosure are not limited to the examples described herein but can be practiced with modifications within the scope of the appended claims. Accordingly, the specification and drawings should be considered illustrative and not limiting. Therefore, the scope of this disclosure should be determined by reference to the appended claims and the full scope of their equivalents.

Claims

1. A method for monitoring electrical faults, the method comprising: The characteristics of processing signals output by at least one sensor of the circuit breaker regarding the electrical properties of a circuit coupled to a load; ‎ The system transitions between operating states based on processed characteristics, including normal state, warning notification state, communication state, fault state, and trip state. The operating state remains in the normal state until the processed characteristics no longer meet the normal criteria. In response to failure to meet the normal criteria, the system transitions to the warning notification state, including initiating the processing of buffering the signal in a queue, and then transitions to the fault state. In response to the failure to meet the tripping conditions, the system transitions from the fault state back to the warning notification state, which indicates that a warning event has been detected. In response to the fulfillment of the tripping condition, the system transitions from the fault state to the tripping state; In response to transitioning back to the warning notification state, the system transitions from the warning notification state to the communication state to output the warning event notification and the contents of the queue associated with the warning event notification; A warning event is detected when the operating state transitions from the normal state to one of the fault state and the warning notification state and then returns to the normal state; as well as When the warning event is determined, output the warning event notification.

2. The method according to claim 1, wherein, The electrical faults are arc faults, ground faults, and / or ground neutral faults.

3. The method according to claim 1, wherein, The queue contains processed features of the signal corresponding to the time from when the circuit breaker leaves its normal state until it returns to its normal state.

4. The method of claim 1, wherein the warning event notification includes a warning duration indicating the duration during which the circuit breaker is not operating in the normal state, wherein the probability of an impending trip is determined based on a parameter and / or a variation of one or more of the parameters, the parameters including at least one of the number of warning event notifications, the warning duration, and the duration between the warning event notifications.

5. The method of claim 1, further comprising receiving warning data having the warning event notification, the warning data including any processed features that are functions of electrical characteristics of a circuit branch connecting the circuit breaker to one or more loads sensed after the circuit breaker transitions from the normal state. The electrical characteristics are sensed by the circuit breaker, and The probability of an impending trip is determined based on changes in the processed characteristics.

6. The method of claim 5, further comprising decomposing the warning data to identify which of the one or more loads is energized or operating when the corresponding electrical characteristic is sensed. The probability of an impending trip is a function of the operation of the identified one or more loads.

7. The method according to claim 1, further comprising: Apply at least one model to determine when to output an impending trip notification; as well as Apply machine learning, statistical and / or numerical techniques to train and / or apply the at least one model.

8. The method of claim 1, wherein the trip notification is output to the user equipment via wireless communication and / or to the remote device via a network.

9. A method for monitoring electrical faults, the method comprising: Receive one or more warning event notifications from the circuit breaker, wherein each warning event notification is based on the detection of a transition mode between the operating states of the circuit breaker, wherein the operating states include a normal state, a warning notification state, a communication state, a fault state, and a trip state, wherein in the normal state, the processed characteristics of the signals sensed by the circuit breaker meet normal criteria, and in the fault state, the normal criteria are not met, and the mode includes a series of transitions, including transitioning from the normal state to the fault state and back to the normal state; The probability of an impending trip is determined based on the one or more warning event notifications; as well as Based on the determined probability, a trip notification will be output. The series of transformations includes: When the processed features no longer meet the normal criteria, the transition from the normal state to the warning notification state, and subsequently from the warning notification state to the fault state, wherein in the warning notification state, the processed features of the signal are buffered in the queue. When the tripping conditions are not met, the system transitions from the fault state to the warning notification state, wherein the warning notification state indicates that a warning event has been detected. When the tripping condition is met, the system transitions from the fault state to the tripping state; and When transitioning to the warning notification state, the system transitions from the warning notification state to the communication state, wherein in the communication state, the warning event notification and the contents of the queue associated with the warning event notification are output.

10. An edge device for monitoring electrical faults, the edge device comprising: The memory is configured to store multiple programmable instructions; as well as At least one processing device communicates with the memory, wherein, when executing the plurality of programmable instructions, the at least one processing device is configured to: One or more warning event notifications are received from the circuit breaker, wherein each warning event notification is based on the detection of a transition mode between the operating states of the circuit breaker, wherein the operating states include a normal state, a warning notification state, a communication state, a fault state, and a trip state, wherein in the normal state, processed characteristics of signals sensed by the circuit breaker meet normal criteria, and in the fault state, the normal criteria are not met, and the mode includes a series of transitions, including transitioning from the normal state to the fault state and back to the normal state; ‎ The probability of an impending power outage is determined based on the one or more warning notifications. as well as Based on the determined probability, a trip notification will be output. The series of transformations includes: When the processed features no longer meet the normal criteria, the system transitions from the normal state to the warning notification state, and subsequently from the warning notification state to the fault state, wherein in the warning notification state, the processed features of the signal are buffered in a queue. When the tripping conditions are not met, the system transitions from the fault state back to the warning notification state, wherein the warning notification state indicates that a warning event has been detected. When the tripping condition is met, the system transitions from the fault state to the tripping state; and When transitioning to the warning notification state, the system transitions from the warning notification state to the communication state, wherein in the communication state, the warning event notification and the contents of the queue associated with the warning event notification are output.

11. The edge device of claim 10, wherein the warning event notification includes a warning duration indicating the duration during which the circuit breaker is not operating in the normal state, wherein the probability of an impending trip is determined based on a parameter and / or a variation of one or more of the parameters, the parameters including at least one of the number of warning event notifications, the warning duration, and the duration between the warning event notifications.

12. The edge device of claim 10, wherein, when executing the plurality of programmable instructions, the at least one processing device is further configured to receive warning data having the warning event notification, the warning data including any processed features that are functions of electrical characteristics of circuit branches connecting the circuit breaker to one or more loads sensed after the circuit breaker transitions from the normal state; The electrical characteristics are sensed by the circuit breaker, and The probability of an impending trip is determined based on changes in the processed characteristics.

13. The edge device of claim 12, wherein, when executing the plurality of programmable instructions, the at least one processing device is further configured to decompose the warning data to identify which of the one or more loads is energized or operating when the corresponding electrical characteristic is sensed. The probability of an impending trip is a function of the operation of the identified one or more loads.

14. The edge device of claim 13, wherein, when executing the plurality of programmable instructions, the at least one processing device is further configured to apply at least one model to determine when to output the impending trip notification, and / or apply machine learning, statistical and / or numerical techniques to train and / or apply the at least one model.

15. The edge device of claim 10, wherein the impending trip notification is output to a user equipment via wireless communication and / or to a remote device via a network.

Images