System and method for conductor sensor conductor drop detection
By installing sensor units on power conductors to monitor and respond to their position and motion data in real time, the rapid identification and response of power conductor drop or shift events is solved, reducing safety risks and improving the management efficiency of power systems.
Patent Information
- Application Number
- CN202380044535.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-05-02
- Filing Date
- 2023-04-28
- Publication Date
- 2025-01-10
AI Technical Summary
The prior art is difficult to quickly identify and respond to drop or shift events of power conductors, resulting in increased safety risks of power systems and extended recovery time.
By installing sensor units on the conductors, collecting position and motion data, using electronic processors to communicate with the local control station, analyzing and performing protection actions in real time, such as power outages, quickly responding to potential hazards.
It realizes rapid identification and response to conductor drop or shift events, reduces safety risks, reduces recovery time, and improves the management efficiency of the power system.
Smart Images

Figure CN119301465A_ABST
Abstract
Description
[0001] Related Applications
[0002] This application claims the benefit of U.S. Provisional Patent Application No. 63 / 337,555, filed on May 2, 2022, the entire contents of each of which are incorporated herein by reference. Technical Field
[0003] Embodiments of the present disclosure relate to monitoring power distribution systems, and more particularly, to detecting and mitigating events associated with distribution conductors, such as fallen conductors. Background Art
[0004] Conductors, such as power conductors, are widely used in many settings. Such power conductors form an important part of the distribution system by transporting electricity from a power generation facility to where it is used by customers (e.g., residential, commercial, and industrial). The distribution system may include many types of conductors, for example, high voltage conductors may be used closer to the power generation facility or for long distance transmission, and medium voltage and low voltage conductors may be used closer to where the electricity is used (such as homes and businesses).
[0005] Many power conductors, such as power cables, run aerially, meaning the conductors are attached to support structures that lift the conductors above the ground, at a safe distance from people on the ground. High-voltage power conductors are often routed through open space, but medium-voltage and low-voltage conductors (which are closer to where the power is used) are more likely to run over roads, trees, or other objects. In some cases, various factors can cause conductors or their support structures to become dislodged and potentially fall to the ground or other objects, which can pose a significant safety risk to the environment, people, or property where the conductors remain energized.
[0006] Typically, a utility company may not be aware that a conductor has been displaced in this manner until the event is reported by someone who observes the displaced conductor. While in some instances a displaced conductor may cause a ground fault or other overcurrent condition that is addressed by various protective devices in the system, the location and type of displaced conductor may not be easily identified by the utility company for some time, increasing the time required to restore service. Additionally, a smart utility grid system may not receive notification that an event (such as a fallen conductor event) has occurred for several minutes or longer. Once the information is received, a maintenance team may need to be dispatched to address any potential issues, such as a displaced live conductor, which requires additional time to address the displaced conductor. Summary of the invention
[0007] Conductor monitoring is facilitated by various sensor units that collect data associated with the position or movement of one or more conductors. The sensor units may use accelerometers to monitor mechanical movement to determine the position and / or movement of one or more conductors. The data may be sent to a local control station that may be configured to quickly analyze events detected by the sensor units and perform protective actions, such as de-energizing the conductors.
[0008] Thus, one embodiment provides a sensing device for detecting a broken conductor. The sensing device includes a first sensor for sensing a parameter of a conductor, a communication interface including a transceiver, and an electronic processor. The electronic processor is configured to receive the parameter of the conductor from the first sensor, determine a jerk of the conductor based on the parameter, compare the jerk to a first predetermined threshold, and send a first signal to a utility manager using the transceiver and send a second signal to at least one of a pole sensing device.
[0009] A further embodiment provides a method for detecting a broken conductor. The method includes receiving a monitoring parameter from a first sensor at an electronic processor, determining a jerk based on the monitoring parameter at the electronic processor, comparing the jerk to a first predetermined threshold at the electronic processor, and sending a first signal to a utility manager and a second signal to at least one of a pole sensing device using a communication interface coupled to the electronic processor.
[0010] A further embodiment provides a system for detecting a broken conductor. The system includes a conductor and a sensing device coupled to the conductor. The sensing device includes a first sensor for sensing a parameter of the conductor, a communication interface including a transceiver, and an electronic processor. The electronic processor is configured to receive the parameter of the conductor from the first sensor, a movement of the conductor based on the parameter, compare the movement of the conductor to a first predetermined threshold, and send a first signal to a utility manager using the transceiver and send a second signal to the pole sensing device based on the comparison.
[0011] Other aspects of the disclosure will become apparent by consideration of the detailed description and accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS
[0012] The accompanying drawings, in which like reference numerals refer to the same or functionally similar elements throughout the individual views, together with the following detailed description, are incorporated into and form a part of the specification and serve to further illustrate embodiments including the concepts of the claims and to explain various principles and advantages of these embodiments.
[0013] Figure 1 is a diagram of a conductor monitoring system according to some embodiments.
[0014] Figure 2is a block diagram of a conductor support sensing apparatus according to some embodiments.
[0015] Figure 3 is a block diagram of a line sensor device according to some embodiments.
[0016] Figure 4 is a block diagram of an insulator sensor device according to some embodiments.
[0017] Figure 5 is a block diagram of a local control station according to some embodiments.
[0018] Figure 6 is a flow chart illustrating a process for monitoring a conductor with a wire sensor according to some embodiments.
[0019] Figure 7 is a flow chart illustrating a process for monitoring a conductor with an insulator sensor according to some embodiments.
[0020] Figure 8 is a flow chart illustrating a process for determining an occurrence of an event associated with a component of a power distribution system, according to some embodiments.
[0021] Fig. 9 is a flow chart illustrating a process for performing a protective action in response to an event occurring within a power distribution system, according to some embodiments.
[0022] Fig.10 is a flow chart illustrating a process for detecting a broken conductor in accordance with some embodiments.
[0023] Fig.11 is a flow chart illustrating another process for detecting a broken conductor in accordance with some embodiments.
[0024] Fig.12 is a flow chart illustrating yet another process for detecting a broken conductor in accordance with some embodiments.
[0025] The skilled person will understand that the elements in the drawings are shown for simplicity and clarity and are not necessarily drawn to scale. For example, the size of some elements in the drawings may be exaggerated relative to other elements to help improve the understanding of the embodiments of the present disclosure.
[0026] Apparatus and method components are represented where appropriate by conventional symbols in the drawings, and only those specific details relevant to an understanding of the embodiments of the disclosure are shown so as not to obscure the disclosure, wherein the details will be apparent to one of ordinary skill in the art having the benefit of the description herein. DETAILED DESCRIPTION
[0027] Before explaining any embodiments of the present disclosure in detail, it should be understood that the present disclosure is not limited in its application to the details of construction and the arrangement of components set forth in the following description or shown in the accompanying drawings. The present disclosure is capable of other embodiments and can be practiced or carried out in various ways.
[0028] One or more embodiments are described and illustrated in the following description and accompanying drawings. These embodiments are not limited to the specific details provided herein and may be modified in various ways. In addition, there may be other embodiments not described herein. In addition, the functions described herein as being performed by one component may be performed by multiple components in a distributed manner. Similarly, the functions performed by multiple components may be merged and performed by a single component. Similarly, the components described as performing specific functions may also perform additional functions not described herein. For example, a device or structure "configured" in a certain way is configured at least in this way, but may also be configured in a manner not listed. In addition, some embodiments described herein may include one or more electronic processors configured to perform the described functions by executing instructions stored in a non-transitory computer-readable medium. Similarly, the embodiments described herein may be implemented as non-transitory computer-readable media storing instructions executable by one or more electronic processors to perform the functions. As used herein, "non-transitory computer-readable media" includes all computer-readable media, but does not include temporary, propagating signals. Thus, a non-transitory computer readable medium may include, for example, a hard disk, a CD-ROM, an optical storage device, a magnetic storage device, a ROM (read only memory), a RAM (random access memory), a register memory, a processor cache, or any combination thereof.
[0029] In addition, the wording and terminology used herein are for descriptive purposes only and should not be considered as limiting. For example, the use of "including", "containing", "comprising", "having" and its variants herein is intended to cover the items listed thereafter and their equivalents and additional items. The terms "connect" and "couple" are widely used and cover direct and indirect connections and couplings. In addition, "connect" and "couple" are not limited to physical or mechanical connections or couplings, and may include electrical connections or couplings, whether direct or indirect. In addition, electronic communications and notifications may be performed using wired connections, wireless connections, or a combination thereof, and may be transmitted directly or through one or more intermediate devices on various types of networks, communication channels, and connections. In addition, only relational terms such as first and second, top and bottom may be used herein to distinguish one entity or action from another entity and action, without necessarily requiring or implying any actual such relationship or order between such entities or actions.
[0030] Figure 1A local power distribution monitoring system 100 is shown according to some embodiments. In an exemplary embodiment, the monitoring system 100 is configured to monitor a plurality of support structures 105a-d (e.g., "poles") supporting overhead conductors 110 within the power distribution system. In some examples, the power distribution system is a low voltage power distribution system. However, embodiments of the following systems and methods are also contemplated for both medium voltage and high voltage systems. In addition, the distribution system can be a three-phase alternating current (AC) distribution system. However, single-phase AC distribution systems as well as other multi-phase AC distribution systems (e.g., 6-phase, 12-phase, etc.) are also contemplated.
[0031] In some embodiments, the conductor 110 is a power line, but other types of conductors, such as communication lines, may be supported by the conductor support structures 105a-d. In some embodiments, the monitoring system 100 monitors the position of the conductor support structures 105a-d to identify the need for maintenance or repair of selected conductor support structures 105a-d. For example, the affected conductor support structure 105a-d may be moved or damaged due to a vehicle accident, weather event, or fallen tree, etc., so that its orientation is changed. This orientation change may affect the physical and / or functional integrity of the conductor 110, may endanger adjacent conductor support structures 105a-d, or may expose the affected conductor or individuals near the conductor support structure 105a-d to danger, for example, from a fallen conductor 110 or a fallen conductor support structure 105. Similarly, the monitoring system 100 monitors the position of the conductor 110 (and other parameters). For example, various factors, such as environmental (wind, ice, fire, fallen trees, etc.), human (collision with conductor support structures 105a-d), and other factors, may cause conductor 110 to break away from conductor support structure 105a-d and fall to the ground, which may result in power loss to customers, as well as potential risks caused by energized conductors. Therefore, monitoring the position (or other parameters) of conductor 110 is very important for the effective management and operation of the power distribution system.
[0032] The monitoring system 100 is also configured to monitor a plurality of overhead conductors 110. The monitoring system 100 may include one or more pole sensor devices 115a-d. The pole sensor devices 115a-d are described in more detail below. In some examples, the pole sensor devices 115a-d may include one or more line sensors 120a-c and / or one or more insulator sensors 122a-c. The one or more line sensors 120a-c are attached to the overhead conductors 110 and communicate with the pole sensor devices 115a-d to provide additional information about the overhead conductors 110, as described in more detail below. The one or more insulator sensors 122 may be attached to, or integrated with, one or more conductor insulators, such as suspension insulators, pin top insulators, and / or post insulators. While Figure 1 Only a single phase or conductor in a multi-phase system is shown with line sensors 120a-c and / or 122a-c, but it is contemplated that each conductor coupled to a conductor support structure 105a-d may have a line sensor 120a-c and / or insulator sensor 122a-c associated therewith for monitoring one or more parameters of the associated conductor 110.
[0033] The monitoring system 100 may also include a local controller 125. The local controller may be used as an intermediary device to provide communication between the pole sensor devices 115a-d and one or more other devices, such as a local control station 130 and / or a central controller 135. In one embodiment, the local controller 125 may be a data collection unit (“data collection unit, DCU”), such as a DCU2+ device from Aclara Technologies, LLC. However, other local control devices are also contemplated. In one embodiment, the local controller 125 may be configured to support advanced metering infrastructure (“Advanced Metering Infrastructure, AMI”) applications for electricity, water, gas, load control, distribution automation, smart infrastructure solutions, and / or other advanced applications. The local controller 125 may communicate with one or more pole sensor devices 115a-d, such as Figure 1 The local controller 125 may also communicate with a local control station 130 .
[0034] In addition, if Figure 1As shown, one or more of the pole sensor devices 115a-d can communicate directly with the local control station 130. For example, in the event that the pole sensor device 115a-d is within the communication range of the local control station 130, the pole sensor device 115a-d communicates directly with the local control station 130, rather than through one or more local controllers. In some examples, one or more pole sensor devices 115a-d can communicate with both the local distribution control station 130 and the local controller 125. In one embodiment, the ability of one or more pole sensor devices to communicate with either the local controller 125 and / or the local control station 130 is based on the communication range of the given pole sensor device 115a-d. As described in more detail below, the pole sensor devices 115a-d communicate with other devices, such as the local controller 125 or the local control station 130, using one or more wireless communication protocols. Therefore, the communication range of a given pole sensor device 115a-d is based on various factors, such as terrain, weather conditions, communication protocol type, etc. Thus, the local controller 125 may be positioned to allow pole sensor devices 115a - d outside of the communication range of a local control station to relay communications from the applicable pole sensor devices 115a - d to one or more local control stations via the local controller 125 .
[0035] For example, Figure 1 As shown, pole sensor device 115a may only be able to communicate with local controller 125 based on the communication range of pole sensor device 115a. Local controller 125 may then communicate the data provided by pole sensor device 115a to local control station 130 because local controller 125 may have an increased communication range over pole sensor device 115a (e.g., due to a high-power transmitter, increased altitude, etc.). In contrast, pole sensor device 115b may be able to communicate with both local controller 125 and local control station 130. Additionally, as shown in FIG. Figure 1 As shown, the pole sensor device 115c may only be able to communicate with the local control station 130 based on the communication range of the pole sensor device 115c (e.g., the pole sensor device 115c is not within the communication range of the local controller 125). It should be understood that the examples provided above are for illustration purposes only, and then in a normal power distribution system, there may be multiple conductor support structures 105a-d, multiple pole sensor devices 115a-d, multiple local controllers 125, and multiple local control stations 130.
[0036] The local control station 130 may be configured to control one or more aspects of the power distribution system associated with the monitoring system 100, as described in more detail below. The local control station 130 and / or the local controller 125 may also be configured to communicate with a central controller 135. In some embodiments, the central controller 135 is a cloud-based and / or local control system configured to monitor various aspects of the utility distribution system. In some embodiments, the central controller 135 is configured to display information to one or more users based on data received from devices such as the local controller 125 and / or the local control station 130. The central controller 135 may also be configured to generate outputs, such as maintenance requests, based on data received from the local controller 125 and / or the local distribution control station. In some embodiments, the central controller 135 may execute one or more software packages related to the management and supervision of a utility distribution system, such as a power distribution system. For example, the software package may be a software package from Aclara Technologies, LLC. software.
[0037] Each pole sensor device 115a-d, line sensor 120a-c, and / or insulator sensor 122a-c may include one or more types of sensors and circuits for controlling the collection of data and the transmission of data for analysis. In some embodiments, each sensor unit may include circuits, such as an electronic processor, for processing the data prior to transmission. The time at which the sensor data is sent may be periodic, randomized, and / or may be dynamically determined based on the detection of changing conditions. For example, sensor data may be sent when a monitoring threshold configured for the sensor device 115a-d is violated. In some embodiments, the reporting frequency of the sensor device 115a-d increases in response to changes in environmental conditions (e.g., a snowstorm arrives, a tree falls, or it becomes windy, etc.).
[0038] Figure 2 2 is a block diagram of a rod sensing device 200 according to some embodiments. The rod sensing device 200 may be similar to the above-described Figure 1The pole sensor devices 115a-d are described herein and should be understood to be interchangeable herein. In some examples, the pole sensing device 200 may be referred to as a conductor support sensing device. Each pole sensing device 200 may include an environmentally sealed housing 202 (not shown). Such a housing 202 may be made of any suitable material, including materials for components used in external locations (such as power distribution systems and / or telephone systems). Sensors and control circuits may be enclosed within the housing 202. One or more types of sensors may be included in the pole sensing device 200, such as an accelerometer 204 (e.g., 2-axis, 3-axis, 4-axis, etc.), a magnetometer 206 (e.g., 2-axis, 3-axis, 4-axis, etc.), a temperature sensor 208 (e.g., a thermistor) and / or a position sensor 210 (e.g., GPS, Glonass).
[0039] like Figure 2 As shown, the exemplary pole sensing device 200 also includes an electronic processor 212, a memory 214, a power supply 216, and a communication interface 218. The accelerometer 204 and the magnetometer 206 may be referred to as orientation sensors. In some embodiments, the accelerometer 204 and the magnetometer 206 are three-axis devices. In some embodiments, data from the temperature sensor 208 is used to provide temperature compensation for the accelerometer 204 and the magnetometer 206. However, in other embodiments, the temperature sensor 208 may also provide temperature information to the electronic processor 212 for determining the temperature around the pole sensing device 200, such as sensing a freezing condition or a fire. It should be understood that the pole sensing device 200 may include any of many other types of sensors in addition to or in place of the above-mentioned sensors.
[0040] The memory 214 may include a read only memory (ROM), a random access memory (RAM), other non-transitory computer readable media, or a combination thereof. The electronic processor 212 is configured to communicate with the memory 214 to store data and retrieve stored data. The electronic processor 212 is configured to receive instructions and data from the memory 214 and execute instructions, among other things. In particular, the electronic processor 212 executes instructions stored in the memory 214 to perform one or more of the processes described herein.
[0041] In one embodiment, power source 216 is configured to provide power to various components of pole sensing device 200. In some embodiments, pole sensing device 200 receives external power, and power source 216 converts and distributes the external power to various components of pole sensing device 200. In some examples, power source 216 includes a battery. In some instances, the battery may be the sole power source, or may be configured to provide backup power when external power is unavailable.
[0042] The communication interface 218 (eg, a transceiver) allows the electronic processor 212 to communicate with one or more external devices (such as one or more external line sensors 220, local controller 125 ( Figure 1 ) and / or local control station 130 ( Figure 1 )) as described herein. The communication interface 218 may also provide communication with other external devices (such as the central controller 135 ( Figure 1 )). In some embodiments, communication interface 218 may include separate transmitting and receiving components. In some embodiments, communication interface 218 is a wireless transceiver that encodes information received from electronic processor 212 into a carrier wireless signal and transmits the encoded wireless signal to one or more external devices, as described above. Communication interface 218 also decodes information received from one or more external devices and provides the decoded information to electronic processor 212. Communication network 240 may include a power line network or a wireless network (e.g., The communication interface 218 may include wireless communication protocols such as Wi-Fi, Wi-Max, cellular (3G, 4G, 5G, LTE), RF, LoRa, Zigbee, and / or other wireless communication protocols applicable to a given system or installation). In one embodiment, the communication interface 218 may use a proprietary wireless communication protocol, such as Synergize RF from Aclara Technologies, LLC.
[0043] like Figure 2 As shown, the pole sensing device 200 may also communicate with one or more line sensors 250 and / or insulator sensors 280. The line sensors 250 may be configured to be coupled to the conductor support structure 105 ( Figure 1 ) is associated with one or more conductors 110 ( Figure 1 In some embodiments, a plurality of line sensors 250 may be in communication with the pole sensing device 200. Similarly, the insulator sensor 280 may be configured to be coupled to the conductor support structure 105 ( Figure 1 ) is associated with one or more conductors 110 ( Figure 1). For example, the insulator sensor 280 may be integrated or coupled with one or more insulators, as described above. An insulator is generally understood to provide insulation between the conductor 110 and the associated conductor support structure. Thus, each conductor 110 ( Figure 1 ) can be provided on each conductor support structure 105 ( Figure 1 ) has an associated insulator and insulator sensor 280.
[0044] Now go to Figure 3 , a block diagram illustrating an example line sensor 250 is shown, according to some embodiments. Similar to the rod sensing device 200 ( Figure 2 ), the line sensor 250 may include one or more sensors, such as one or more accelerometers 302 (e.g., 2-axis, 3-axis, 4-axis, etc.), a magnetometer 304 (e.g., 2-axis, 3-axis, 4-axis, etc.), a temperature sensor 306 (e.g., a thermistor), a current sensor 308 (e.g., a current transformer), etc. The sensors within the line sensor 250 may be configured to detect various parameters associated with the associated conductor. For example, one or more accelerometers 302 may be used to detect conductor conditions, such as a dropped line, line sag, gallop, sway, etc. In some embodiments, the line sensor 250 may collect data based on the accelerometer 302 using any amount of internal sampling frequency and any amount of output data rate. As an example, the internal sampling frequency may be 1600 Hertz (HZ), and the output data rate may be a first sampling rate, such as 25 Hertz (Hz) during operation, and may be a second sampling rate, such as 5 Hz, during wake-up. The one or more accelerometers 302 may monitor the one or more conductors 110 ( Figure 1 ) data related to the mechanical movement of the
[0045] In some embodiments, the line sensor 250 can be physically mounted to one or more conductors 110 and can monitor the movement of the conductors in the x-direction, y-direction, and z-direction. Based on the movement of the conductors, the line sensor 250 can determine that the conductor is broken, the conductor is swaying from side to side, dancing (e.g., oscillating in the vertical direction), and / or the conductor has experienced a sudden loss of tension. The surface on which the broken conductor rests is not conducive to detecting the broken conductor based on the mechanical / physical movement of one or more conductors 110. The line sensor 250 can detect a broken conductor based on the jerk of the conductor (e.g., the rate of change of the acceleration of the conductor with respect to time), the free fall or pendulum swing of the conductor detected by the accelerometer 302, or by integrating parameters monitored by the accelerometer 302 to determine the position and / or velocity of the line.
[0046] The line sensor 250 may determine that the conductor is swaying based on movement along a single axis in the horizontal plane.
[0047] The line sensor 250 can determine that the conductor is dancing based on movement along a single axis in a vertical plane. The detection axis for both sway and galloping depends on the mounting orientation of the line sensor 250. In some embodiments, the mounting orientation of the line sensor 250 is considered during the installation of the line sensor 250. The line sensor 250 can determine that the conductor has experienced a sudden loss of tension based on a distinguishable jerk experienced along a single axis. The mounting orientation of the line sensor 250 does not contribute to determining the jerk of the line sensor 250.
[0048] Other sensors, such as temperature sensor 306, can detect a temperature increase, which indicates a possible overload or high resistance condition. In addition, temperature sensor 306 can detect an associated conductor 110 ( Figure 1 ) potential icing conditions. Current sensor 308 may be configured to detect current within a given conductor 110 and determine whether one or more current-based faults (eg, overcurrent, ground fault, etc.) exist on the given conductor.
[0049] The line sensor 250 may also include an electronic processor 310, a memory 312, and a communication interface 314. The memory 312 may include a read-only memory (ROM), a random access memory (RAM), other non-transitory computer-readable media, or a combination thereof. The electronic processor 310 is configured to communicate with the memory 312 to store data and retrieve stored data. The electronic processor 310 is configured to receive instructions and data from the memory 312 and execute instructions, among other things. In particular, the electronic processor 310 executes instructions stored in the memory 312 to perform one or more of the processes described herein.
[0050] The line sensor 250 can communicate with the pole sensing device 200 via the communication interface 314. For example, the communication interface 314 can use Communicates with the pole sensing device 200. However, the communication interface 314 may communicate with the pole sensing device 200 using any of the communication protocols described above with respect to the communication interface 314.
[0051] Now go to Figure 4 , a block diagram illustrating an example insulator sensor 280 is shown, according to some embodiments. Similar to the pole sensing device 200 ( Figure 2 ) and / or line sensor 250 ( Figure 3), the insulator sensor 280 may include one or more sensors, such as one or more accelerometers 350 (e.g., 2-axis, 3-axis, 4-axis, etc.), voltage sensors 352 (e.g., electronic field sensors), tension sensors 354 (e.g., strain gauges, etc.), and / or other sensors as required for a particular application. The sensors within the insulator sensor 280 may be configured to detect various parameters associated with the associated conductor. For example, one or more accelerometers 350 may be used to detect conductor movement, such as a dropped wire, wire sagging, galloping, etc. The voltage sensor 352 may detect the presence and / or loss of voltage on the associated conductor, which may indicate an electrical fault or, in the case of a loss of voltage, a dropped wire. Other sensors, such as the tension sensor 354, may detect changes in force associated with a conductor coupled to an insulator associated with the insulator sensor 280. For example, a sudden increase in tension or force, followed by a substantial decrease in the sensed tension or force, may indicate that a dropped conductor condition is occurring.
[0052] The insulator sensor 280 may also include an electronic processor 360, a memory 362, and a communication interface 364. The memory 312 may include a read-only memory (ROM), a random access memory (RAM), other non-transitory computer-readable media, or a combination thereof. The electronic processor 360 is configured to communicate with the memory 362 to store data and retrieve stored data. The electronic processor 360 is configured to receive instructions and data from the memory 362 and execute instructions, among other things. In particular, the electronic processor 360 executes instructions stored in the memory 362 to perform one or more of the processes described herein.
[0053] The insulator sensor 280 can communicate with the pole sensing device 200 via the communication interface 364. For example, the communication interface 364 can be used Communicates with the pole sensing device 200. However, the communication interface 364 may communicate with the pole sensing device 200 using any of the communication protocols described above with respect to the communication interface 218. In other embodiments, the insulator sensor 280 may communicate with the pole sensing device 200 via one or more wire sensors 250. The wire sensor 250 may receive messages from the insulator sensor and subsequently send the received messages to the pole sensing device 200, as described herein.
[0054] Now go to Figure 5 , shows a block diagram of an exemplary local control station 400 according to some embodiments. In one embodiment, the local control station 400 may be the same as the local control station 130 described above and may be used interchangeably. The local control cabinet may be located near one or more conductor supports within the power distribution system.
[0055] like Figure 5As shown, the local control station 400 according to one or more exemplary embodiments may include one or more power control devices 402, a communication interface 404, a controller 406, and an analysis engine 408. The power control device 402 may include various devices for controlling the power provided to the conductor 110 on the load side 410 of the power control device 402. For example, the power control device 402 may include devices such as a recloser, a tap switch, a capacitor bank, etc. In one example, where the power control device 402 includes a recloser, the power control device 402 may be opened so that the line side power 412 is separated from the load side 410, thereby making the conductor 110 ( Figure 1 Other power control devices 402 , such as tap changers, may be configured to vary the voltage provided to the conductor 110 via the load side 410 of the power control device 402 .
[0056] The controller 406 may be configured to control one or more of the above-mentioned power control devices 402. In one embodiment, the controller 406 may be an M-7679R-Pac controller from Beckwith Electric Co., Inc. However, other controllers 406 may also be used as required for a given application. The analysis engine 408 may be configured to analyze data received from one or more pole sensing devices (such as the pole sensing device 200) and / or the local controller 125 via the communication interface 404. In one example, the analysis engine 715 may be configured to determine that one or more events, such as a line drop event, have occurred based on the received data. A line drop event may occur when one or more conductors (such as the above-mentioned conductor 110) fall or otherwise become disconnected from the conductor support structure 105. Data from sensors (such as the accelerometer 302 associated with the line sensor 250) may provide data to the power control device 402 indicating a dropped line event, as will be described in more detail below. Other events may include various conductor support events, such as those described above (e.g., dancing, catching fire, sagging, falling, etc.).
[0057] In some embodiments, the analysis engine 408 can be configured to control one or more power control devices 402 to shut down, disconnect, or modify the power provided to a portion of the power distribution system. In one embodiment, the analysis engine 408 can be an edge gateway device from Aclara Technologies, LLC. However, in other embodiments, various controllers and / or electronic processors can operate as the analysis engine 408. In some examples, the analysis engine 408 can be configured to provide an interface to the controller 406, thereby allowing other devices (e.g., pole sensing device 200, local controller 125, etc.) to communicate with the controller 406 using various communication protocols as described herein. In other embodiments, the analysis engine 408 can be integrated with the controller 406.
[0058] When the local control station 400 receives data directly from the local controller 125 and / or the pole sensing device 200, actions to resolve the detected event can be performed in a shorter time than requiring a central controller (such as the central controller 135) to analyze the data and instruct one or more local control stations 40 to perform the actions required to resolve the event. For example, by utilizing the local control station 400, various operations, such as detecting and event and controlling the power control device 402 to perform one or more actions in response to the event, can occur on the order of milliseconds ("ms"). For example, in some embodiments, an event can be detected and the power control device 402 operates in response to the event in less than 1 second. However, values greater than 1 second or less than 1 second are also contemplated. In contrast, existing systems, such as those that rely on communication with a central controller (such as the central controller 135), may even take several minutes to receive notification that an event has occurred, as well as additional time to take corrective action.
[0059] The communication interface 404 may be configured to wirelessly communicate with devices such as the local controller 125 and / or the pole sensing device 200 using one or more wireless communication protocols. In one embodiment, the wireless communication protocol may be a proprietary RF communication protocol, such as Synergize RF from Aclara Technologies, LLC. Other wireless communication protocols may include cellular (e.g., 3G, 4G, 5G, LTE, etc.), Bluetooth, LoRa, Zigbee, RF, Wi-Fi, Wi-Max, and / or other wireless communication protocols suitable for a given system or installation. The communication interface 404 may also be configured to communicate with other devices, such as the central controller 135. In some embodiments, the communication interface 404 may communicate with the central controller 135 using wireless communication protocols such as those described above. In other examples, a wired communication protocol (such as PLC, serial, Ethernet, etc.) may be used by the communication interface 404 to communicate with the central controller 135. For example, the local control station 400 may send data indicating event detection and subsequent actions taken to the central controller 135.
[0060] Now go to Figure 6 , a process 500 for detecting a wire drop event of a conductor 110 at the wire sensor 250 described above is shown, according to some embodiments. While the process 500 is generally described as being performed by the wire sensor 250 described above, it is contemplated that other wire sensors or devices may perform the various steps of the process 500. Additionally, the process 500 may also be performed by the insulator sensor 280, as described above. At process block 502, the wire sensor 250 monitors various parameters associated with the conductor 110 to which the wire sensor 250 is coupled. For example, as described above, various parameters may be monitored by the wire sensor 250, such as motion via the accelerometer 302, current via the current sensor 308, temperature via the temperature sensor 306, and the like.
[0061] At process block 504, processor 310 determines whether one or more of the monitored parameters indicate a dropped wire condition. For example, in the case where the accelerometer detects that the wire is falling at a rate exceeding a predetermined value (such as 10 ft / s), the data from accelerometer 302 can be determined to exceed a predetermined threshold associated with a dropped conductor 110. However, values greater than 10 ft / s or less than 10 ft / s can also be used as the predetermined threshold. In response to determining that the monitored parameters do not exceed the predetermined threshold indicating a dropped wire, at process block 506, the monitored parameters are sent to one or more pole sensing devices 200 via communication interface 314. In one embodiment, the monitored parameters are sent via communication interface 314 at predetermined intervals. For example, the predetermined interval can be 1 second. However, it is also contemplated that the predetermined interval is either greater than 1 second or less than 1 second. In one embodiment, the monitored parameters are sent to one or more pole sensing devices, such as pole sensing device 200 described above.
[0062] In response to determining that the monitored parameter exceeds a predetermined threshold value indicating a fallen conductor, at process block 508, an alarm is sent to one or more pole sensing devices 200 along with the monitored parameter via the communication interface 314. In one embodiment, the alarm includes an indication of a fallen conductor condition determined based on the monitored parameter. Although process 500 only describes sending an alarm based on a fallen conductor condition, it is contemplated that other conditions determined based on the monitored parameters may also generate an alarm, such as a dancing wire, a sagging wire, etc.
[0063] Now go to Figure 7 , a process 550 is shown for detecting a line drop event of a conductor 110 at the insulator sensor 280 described above, according to some embodiments. While the process 550 is generally described as being performed by the insulator sensor 280 described above, it is contemplated that other insulator sensors or devices may perform the various steps of the process 550. At process block 552, the insulator sensor 280 monitors various parameters associated with the conductor 110 to which the insulator sensor 280 is coupled or associated. For example, as described above, various parameters may be monitored by the insulator sensor 280, such as motion via the accelerometer 350, voltage via the voltage sensor 352, tension / strain via the tension sensor 354, and the like.
[0064] At process block 554, processor 360 determines whether one or more of the monitored parameters indicate a dropped line condition. For example, in the event that tension sensor 354 detects a sudden decrease in tension (e.g., static force) that exceeds a predetermined limit, such as a decrease of greater than 80% of the normalized tension value, data from tension sensor 354 may be determined to exceed a predetermined threshold associated with a dropped conductor 110. However, values greater than 80% or less than 80% may also be used as the predetermined threshold. In some instances, processor 360 may look at a combination of parameters. For example, in the event that tension decreases by a value that exceeds a predetermined threshold and voltage sensor 352 detects a loss of voltage, the combined data provided by tension sensor 354 and voltage sensor 352 may indicate a dropped conductor 110.
[0065] In response to determining that one or more monitored parameters do not exceed a predetermined threshold indicating a line of drop, at process block 556, the monitored parameters are sent to one or more pole sensing devices 200 via communication interface 364. In one embodiment, the monitored parameters are sent via communication interface 354 at predetermined intervals. For example, the predetermined interval may be 1 second. However, predetermined intervals greater than 1 second or less than 1 second are also contemplated. In one embodiment, the monitored parameters are sent to one or more pole sensing devices, such as pole sensing devices 200 described above.
[0066] In response to determining that the monitored parameter exceeds a predetermined threshold value indicating a fallen conductor, at process block 558, an alarm is sent to one or more pole sensing devices 200 along with the monitored parameter via the communication interface 354. In one embodiment, the alarm includes an indication of a fallen conductor condition determined based on the monitored parameter. Although process 550 only describes sending an alarm based on a fallen conductor condition, it is contemplated that other conditions determined based on the monitored parameters may also generate an alarm, such as a dancing wire, a sagging wire, etc.
[0067] Now go to Figure 8 , a process 600 for determining an event at a pole sensing device, such as pole sensing device 200 described above, is shown, according to some embodiments. At process block 602, pole sensing device 200 monitors various parameters via one or more sensors associated with pole sensing device 200. As described above, pole sensing device 200 may include accelerometer 204, magnetometer 206, temperature sensor 208, etc., for monitoring various parameters associated with conductor support structure 105. Pole sensing device 200 may also monitor data associated with conductor 110 received from wire sensor 250 and / or insulator sensor 280, such as described above.
[0068] At process block 604, the electronic processor 212 determines whether an alarm has been received from the wire sensor 250 and / or the insulator sensor 280. As described above, the wire sensor 250 and / or the insulator sensor 280 may send an alarm to the pole sensing device 200 in response to a determined event, such as a dropped conductor event. In response to determining that an alarm has been received from one or more of the wire sensors 250 and / or the insulator sensors, the alarm and associated monitoring parameters are sent via the communication interface 218 at process block 606. In some embodiments, the alarm and associated monitoring parameters are sent to one or more local control stations, such as the local control station 400 described above. The alarm and associated monitoring parameters may also be sent to one or more local controllers 125 for further transmission to other devices, such as the local control station 400 and / or the central controller 135. The alarm and associated monitoring parameters may also be sent to a central device, such as the central controller 135 described above. In addition to sending the alarm and associated monitoring parameters, additional data may be further sent at process block 606, such as an identifier of the wire sensor 250 and / or insulator sensor 280 that sent the alarm, an identifier of the pole sensing device 200 that received the alarm, the position of the pole sensor device 115a (e.g., via the position sensor 210), and / or other relevant data.
[0069] In response to determining at process block 604 that no alarm has been received, electronic processor 212 determines whether the monitored parameters exceed one or more predetermined thresholds indicating the occurrence of an event at process block 608. For example, the event may include a dropped conductor support structure 105, a misaligned conductor support structure 105, a galloping conductor 110, an overcurrent event, an overheat, a detected collision with a conductor support 110, and / or other events as described herein.
[0070] In response to determining that the monitored parameters do not exceed any predetermined thresholds, the rod sensing device 200 continues to monitor multiple parameters at process block 602. In response to determining that the monitored parameters exceed one or more predetermined thresholds, an event is generated based on the monitored data at process block 610. In some events, the event may include an event type, as well as identification information of the rod sensing device 200, wire sensor 250, and / or insulator sensor that detected the event. Then at process block 606, one or more determined events are sent, as described above.
[0071] Now go to Fig. 9, according to some embodiments, a process 700 for performing one or more protection actions on a portion of a power distribution system is shown. In one embodiment, the process 700 is performed by a local control station, such as the local control station 400 described above. At process block 702, the local control station 400 receives data from one or more sensing devices, such as the pole sensing device 200 described above. In other embodiments, the data may be received via one or more local controllers 125, as described above.
[0072] At process block 704, the local control station 400 analyzes the data. For example, the received data may be analyzed via the analysis engine 408 described above. In other examples, one or more controllers 406 and / or the analysis engine 408 may analyze the data. In one embodiment, the local control station 400 analyzes the data to determine whether an event has been detected, and / or whether the data indicates whether one or more protective actions may be required. At process block 706, the local control station 400 determines whether a protective action is required based on the analyzed data. For example, in the event that the analyzed data indicates that a dropped conductor event has been detected, a protective action may be required to prevent the conductor from being in an energized state before or shortly after contacting the ground or other object.
[0073] Other events, such as dancing wires, fallen conductor supports, etc., may also require protective action. In response to determining that protective action is not required based on the analyzed data and / or received events, at process block 708, the analyzed data is sent to a central controller, such as central controller 135. The analyzed data sent to central controller 135 may include the type of event determined, the identity of the sensor, sensing device, or local controller that sensed and / or sent the event data, and any protective action taken. Examples of events that may not require immediate protective action may include misplaced conductor supports, conductor sagging, frozen conductors, etc. By sending the data to central controller 135, various maintenance operations may be scheduled or initiated to address the event and / or analyzed data.
[0074] In response to determining that a protective action is required, the local control station 400 determines whether the event occurred downstream of the local control station 400 (e.g., on the load side 410). An event that occurred upstream of the local control station (e.g., on the line side 412) cannot be resolved by the downstream local control station 400. In response to determining that the event did not occur downstream, the analyzed data is sent at process block 708. In one embodiment, at process block 708, the analyzed data is sent to the central controller 135. It should be understood that while one local control station 400 may be downstream of a detected event, one or more other local control stations 400 may be located upstream of the detected event and will have received data from one or more pole sensing devices 200 so that they can perform appropriate protective actions. For example, as Figure 1 As shown, the conductors 110 from the conductor support structure 105a to the conductor support structure 105c may be downstream of the local control station 130, thereby allowing the local control station 130 to disconnect the power at the conductor support structure 105c, which continues to at least the conductor support structures 105a-b via their associated conductors 110. Figure 1 In the example shown, the conductor 110 between the conductor support structures 105c and 105d will remain energized.
[0075] In some embodiments, the local control station 400 may include information related to all pole sensing devices 200 within a network or within a given area. Thus, based on the pole sensing device identification information transmitted by the pole sensing device 200, as described above, the local control station 400, such as via the analysis engine 408, may be able to determine the location of the detected event, and therefore determine whether the event occurred downstream of the local control station 400. In other examples, the local control station 400 may utilize other data, such as location data evidenced by the location sensor 210 of the pole sensing device 200, to determine whether the event occurred downstream of the local control station 400.
[0076] In response to determining that the event occurred downstream of the local control station 400, the local control station performs one or more protective actions at process block 712. As described above, the protective action may include de-energizing the conductor downstream of the local control station 400 using the power control device 402 (such as a recloser or switch). In some embodiments, the protective action may be based on the type of event, such as a permanent or transient event. An example permanent event may be a dropped conductor event. For a permanent event, the protective action may include de-energizing the conductor downstream of the local control station and locking the power control device 402 so that once the event is resolved, the downstream conductor can only be re-energized by the affirmative action of my maintenance personnel. For example, in the case where the power control device 402 is a recloser device, the recloser is locked by the controller 406 to prevent subsequent reclosing operations, allowing the downstream conductor to be energized. However, in other examples, where the event may be transient, such as a dancing line or a current fault (e.g., caused by a transient event such as a tree branch temporarily causing a fault condition), an attempt to re-energize the downstream conductor may be determined after a period of time, or after it is determined that the event is no longer occurring (e.g., when the dancing ceases).
[0077] After the protection action is completed, at process block 708, the data (including the protection action performed) is sent to the central controller, as described above.
[0078] As described above, by utilizing the local control station 400 to perform protection actions, the time to respond to certain events is greatly reduced. For example, it is considered that processes 500, 600, and 700 can be completed in approximately 1000ms (1 second) or less. This can allow certain events, such as a dropped conductor event (e.g., de-energizing the dropped conductor), to be resolved before the conductor reaches the ground, which is estimated to be typically from 1 second to 1.5 seconds. Even in the case where the conductor cannot be de-energized before the conductor contacts the ground or other objects, the conductor can be de-energized almost immediately thereafter using the process described herein. This provides a substantial improvement over current event monitoring systems in power distribution, which may typically take several minutes or longer to even know that an event has occurred.
[0079] Now go to Fig.10, according to some embodiments, a process 800 for detecting a wire break of a conductor 110 at a wire sensor 250 based on the jerk detected above is shown. Although the process 800 is generally described as being performed by the wire sensor 250 described above, it is contemplated that other wire sensors or devices may perform the various steps of the process 800. Additionally, the process 800 may also be performed by the insulator sensor 280, as described above. At process block 802, the wire sensor 250 monitors various parameters associated with the conductor 110 to which the wire sensor 250 is coupled. For example, as described above, various parameters may be monitored by the wire sensor 250, such as motion via the accelerometer 302, current via the current sensor 308, temperature via the temperature sensor 306, and the like. In some embodiments, the motion monitored by the accelerometer 302 may be along a single axis. For example, the monitored motion may be along the x-axis. The accelerometer 302 may use a sampling rate of 25 Hz.
[0080] At process block 804, processor 310 determines the jerk experienced by conductor 110. For example, jerk is the change in acceleration along the x-axis of line sensor 250 with respect to time. The x-axis may be parallel to conductor 110 to which line sensor 250 is connected. In some embodiments, jerk is determined by processor 310 performing an integration of acceleration sensed by accelerometer 302. Accelerometer 302 may be set to a 2 gravity (g) maximum mode. When jerk is detected by processor 310 based on monitored parameters of accelerometer 302, conductor 110 may be braking, as evidenced by a sudden decrease in tension. At process block 806, processor 310 determines whether jerk exceeds a predetermined threshold. For example, the accelerometer may detect an instantaneous jerk of at least a predetermined threshold, such as 1.0 g. However, values between 0.1 g and 15.9 g may also be used as the predetermined threshold.
[0081] In response to determining that the jerk exceeds a predetermined threshold indicating a broken wire, at process block 808, an alarm and data along with the monitored parameters are sent to the one or more pole sensing devices 200 via the communication interface 314. In one embodiment, the alarm includes an indication of a conductor break determined based on the monitored parameters, and in particular based on the jerk of the wire.
[0082] In response to determining that the jerk does not exceed the predetermined threshold value indicating a break line, at process block 810, the monitored parameters are sent to one or more rod sensing devices 200 via the communication interface 314. In one embodiment, the monitored parameters are sent via the communication interface 314 at predetermined intervals. For example, the predetermined interval may be 1 second. However, it is also contemplated that the predetermined interval may be greater than 1 second or less than 1 second. In one embodiment, the monitored parameters are sent to one or more rod sensing devices, such as the rod sensing devices 200 described above.
[0083] Now go to Fig.11 , according to some embodiments, a process 900 for detecting a wire break of a conductor 110 at a wire sensor 250 based on the above-described detected velocity is shown. Although the process 900 is generally described as being performed by the above-described wire sensor 250, it is contemplated that other wire sensors or devices may perform the various steps of the process 900. Additionally, the process 900 may also be performed by the insulator sensor 280, as described above. At process block 902, the wire sensor 250 monitors various parameters associated with the conductor 110 to which the wire sensor 250 is coupled. For example, as described above, various parameters may be monitored by the wire sensor 250, such as motion via the accelerometer 302, current via the current sensor 308, temperature via the temperature sensor 306, and the like. In some embodiments, the motion monitored by the accelerometer 302 may be along a single axis. For example, the monitored motion may be along the x-axis. The accelerometer 302 may use a sampling rate of 25 Hz.
[0084] At process block 904, processor 310 determines the velocity experienced by conductor 110. For example, processor 310 may integrate the acceleration motion as monitored by an accelerometer to determine the velocity.
[0085] In some embodiments, the processor 310 may use a first-order Euler integral to determine the velocity vector. In some embodiments, the processor may determine the velocity as if the z-axis and the gravity vector are still aligned, even if this is not the case. At process block 906, the processor 310 determines whether the velocity exceeds a predetermined threshold. For example, based on the integration of the accelerometer 302 data, the processor 310 may detect a velocity of at least a predetermined threshold, such as 2 meters per second (m / s). However, a value between 0.1 m / s and 10 m / s may also be used as a predetermined threshold. In response to determining that the velocity exceeds a predetermined threshold indicating a broken line, at process block 908, an alarm and data are sent to one or more pole sensing devices 200 along with the monitored parameters via the communication interface 314. In one embodiment, the alarm includes an indication of a conductor break determined based on the monitored parameters, and in particular based on the speed of the line. Although process 900 only describes sending an alarm based on a dropped conductor condition, it is contemplated that other conditions determined based on the monitored parameters may also generate an alarm, such as a dancing line, a line droop, etc.
[0086] In response to determining that the speed does not exceed the predetermined threshold value indicating a break line, at process block 910, the monitored parameters are sent to one or more rod sensing devices 200 via the communication interface 314. In one embodiment, the monitored parameters are sent via the communication interface 314 at predetermined intervals. For example, the predetermined interval may be 1 second. However, it is also contemplated that the predetermined interval may be greater than 1 second or less than 1 second. In one embodiment, the monitored parameters are sent to one or more rod sensing devices, such as the rod sensing devices 200 described above.
[0087] Now go to Fig.12 , according to some embodiments, a process 1000 for detecting a wire break of a conductor 110 at a wire sensor 250 based on the detected position described above is shown. Although the process 1000 is generally described as being performed by the wire sensor 250 described above, it is contemplated that other wire sensors or devices may perform the various steps of the process 1000. In addition, the process 1000 may also be performed by the insulator sensor 280, as described above. At process block 1002, the wire sensor 250 monitors various parameters associated with the conductor 110 to which the wire sensor 250 is coupled. For example, as described above, various parameters may be monitored by the wire sensor 250, such as motion via the accelerometer 302, current via the current sensor 308, temperature via the temperature sensor 306, etc. In some embodiments, the motion monitored by the accelerometer 302 may be along a single axis. For example, the monitored motion may be along the x-axis. The accelerometer 302 may use a sampling rate of 25 Hz.
[0088] At process block 1004, the processor 310 determines a distance vector. For example, the processor may perform a double integration of the acceleration motion as monitored by the accelerometer 302 to determine the distance vector. In some embodiments, the processor 310 may use a second order Euler integral to determine the distance vector. In some embodiments, the processor may determine the distance as if the z-axis and the gravity vector are still aligned, even if this is not the case. In some embodiments, the processor 310 may first determine a distance value at a time before the break (e.g., before the conductor breaks). For example, the processor 310 may determine how long it takes for the line sensor 250 to fall 2 meters (m). The processor 310 may add another 25% of the determined time to the determined time, so that the determined time may be approximately 800 milliseconds (ms). Once the processor 310 determines the time before the break, the processor 310 may determine the acceleration in each of the x-direction, the y-direction, and the z-direction based on the monitoring parameters monitored by the accelerometer 302. Based on the time before the break and the acceleration in each direction, the processor 310 may determine the distance vector. In some embodiments, the distance traveled by the line sensor 250 can be in any of three directions. For example, based on the determined distance vector, the processor 310 can determine that the line sensor 250 is falling "upwards". The processor can ignore the direction of movement and only determine the magnitude of the distance, regardless of the angle vector.
[0089] At process block 1006, the processor 310 determines whether the distance exceeds a predetermined threshold. For example, based on the double integration of the accelerometer 302 data, the processor 310 can detect a distance of at least a predetermined threshold, such as 2 meters (m). However, a value between 0.5m and 5m can also be used as a predetermined threshold. In response to determining that the distance exceeds the predetermined threshold indicating a broken line, at process block 1008, an alarm and data are sent to one or more pole sensing devices 200 along with the monitored parameters via the communication interface 314. In one embodiment, the alarm includes an indication of a conductor break determined based on the monitored parameters, and in particular based on the speed of the line. Although process 1000 only describes sending an alarm based on a dropped conductor condition, it is contemplated that other conditions determined based on the monitored parameters may also generate an alarm, such as a dancing line, a line sag, etc.
[0090] In response to determining that the distance does not exceed a predetermined threshold value indicating a break line, at process block 1010, the monitored parameters are sent to one or more pole sensing devices 200 via the communication interface 314. In one embodiment, the monitored parameters are sent via the communication interface 314 at predetermined intervals. For example, the predetermined interval may be 1 second. However, it is also contemplated that the predetermined interval may be greater than 1 second or less than 1 second. In one embodiment, the monitored parameters are sent to one or more pole sensing devices, such as the pole sensing devices 200 described above. In some embodiments, when the distance does not exceed the predetermined threshold value, the conductor is experiencing wind-induced vibrations.
[0091] Now go to Fig.13 , according to some embodiments, a process 1100 for detecting a wire break of a conductor 110 at a wire sensor 250 based on the gravity vector determined above is shown. Although the process 1100 is generally described as being performed by the wire sensor 250 described above, it is contemplated that other wire sensors or devices may perform the various steps of the process 1100. Additionally, the process 1100 may also be performed by the insulator sensor 280, as described above. At process block 1102, the wire sensor 250 monitors various parameters associated with the conductor 110 to which the wire sensor 250 is coupled. For example, as described above, various parameters may be monitored by the wire sensor 250, such as motion via the accelerometer 302, current via the current sensor 308, temperature via the temperature sensor 306, and the like. In some embodiments, the motion monitored by the accelerometer 302 may be along a single axis. For example, the monitored motion may be along the x-axis. The accelerometer 302 may use a sampling rate of 25 Hz.
[0092] At process block 1104, processor 310 determines the gravity vector. When line sensor 250 is not experiencing any movement, the gravity vector is 9.8 meters per second (m / s 2 ). At process block 1106, processor 310 determines whether the conductor is experiencing movement. For example, based on the gravity vector, the movement of line sensor 250 may be determined. When line sensor 250 moves, the gravity vector may be other than 9.8 m / s 2 , and thus experiences a different acceleration, as detected by accelerometer 302. In some embodiments, the movement may be a free fall, a pendulum swing, or other definable movement of line sensor 250.
[0093] In response to determining that the conductor is experiencing movement and thus indicating a broken wire, at process block 1108, an alarm and data along with the monitored parameters are sent to one or more pole sensing devices 200 via the communication interface 314. In one embodiment, the alarm includes an indication of a conductor break determined based on the monitored parameters, and in particular based on the speed of the wire. Although process 1100 only describes sending an alarm based on a dropped conductor condition, it is contemplated that other conditions determined based on the monitored parameters may also generate an alarm, such as a dancing wire, a sagging wire, etc.
[0094] In response to determining that the conductor has not experienced movement and therefore indicates a break line, at process block 1110, the monitored parameters are sent to one or more pole sensing devices 200 via the communication interface 314. In one embodiment, the monitored parameters are sent via the communication interface 314 at predetermined intervals. For example, the predetermined interval may be 1 second. However, it is also contemplated that the predetermined interval may be greater than 1 second or less than 1 second. In one embodiment, the monitored parameters are sent to one or more pole sensing devices, such as the pole sensing devices 200 described above. In some embodiments, when the distance does not exceed a predetermined threshold, the conductor is experiencing wind-induced vibrations.
[0095] In the foregoing description, specific embodiments have been described. However, it will be appreciated by those skilled in the art that various modifications and changes may be made without departing from the scope of the disclosure as set forth in the following claims. Therefore, the description and drawings should be regarded as illustrative rather than restrictive, and all such modifications are intended to be included within the scope of the present teachings.
[0096] Various features and advantages of some embodiments are set forth in the following claims.
Claims
1. A sensing device for detecting a broken conductor, the sensing device comprising: a first sensor for sensing a parameter of the conductor, a communication interface comprising a transceiver, and An electronic processor configured to: receiving a parameter of the conductor from the first sensor, determining a jerk of the conductor based on the parameter, comparing the jerk to a first predetermined threshold, and At least one of transmitting a first signal to a utility manager and transmitting a second signal to a pole sensing device is accomplished using the transceiver.
2. The sensing device according to claim 1, wherein: The electronic processor is configured to send the first signal to the utility manager in response to the jerk being greater than the first predetermined threshold.
3. The sensing device according to claim 2, wherein: The first signal includes at least one of a broken conductor alarm and the parameter.
4. The sensing device according to claim 1, wherein: The electronic processor is configured to send the second signal to the rod sensing device in response to the jerk being less than the first predetermined threshold.
5. The sensing device according to claim 1, wherein: The first sensor is an accelerometer.
6. The sensing device according to claim 5, wherein: The parameter is the motion of the conductor along the x-axis.
7. The sensing device according to claim 5, wherein: The first predetermined threshold is within the range of 0.1 gravity (g) and 15.9 g.
8. The sensing device according to claim 1, wherein: The sensing device is mounted to the conductor.
9. A method for detecting a broken conductor, the method comprising: receiving, at an electronic processor, a monitored parameter from a first sensor; determining, at the electronic processor, a jerk based on the monitored parameter; comparing, at the electronic processor, the jerk to a first predetermined threshold; and At least one of sending a first signal to a utility manager and sending a second signal to a pole sensing device using a communication interface coupled to the electronic processor.
10. The method according to claim 9, wherein: The first sensor is an accelerometer.
11. The method according to claim 10, wherein: The monitored parameter is the motion of the conductor along the x-axis.
12. The method according to claim 9, wherein: The first sensor is mounted to a conductor.
13. The method according to claim 9, wherein: In response to the jerk being greater than the first predetermined threshold, the first signal is sent to the utility manager.
14. The method according to claim 9, wherein: In response to the jerk being less than the first predetermined threshold, the second signal is sent to the rod sensing device.
15. A system for detecting a broken conductor, the system comprising: conductor; as well as a sensing device coupled to the conductor, the sensing device comprising: A first sensor for sensing a parameter of the conductor, a communication interface comprising a transceiver, and An electronic processor configured to: receiving a parameter of the conductor from the first sensor, determining a movement of the conductor based on the parameter, comparing the movement of the conductor to a first predetermined threshold, and Based on the comparison, at least one of sending a first signal to a utility manager and sending a second signal to a pole sensing device using the transceiver.
16. The system of claim 15, wherein: The motion of the conductor is the velocity of the conductor.
17. The system of claim 16, wherein: The speed of the conductor is determined by the electronic processor integrating the parameter from the first sensor.
18. The system of claim 15, wherein: The movement of the conductor is the distance travelled by the sensing device.
19. The system of claim 18, wherein: The distance traveled by the sensing device is determined by the electronic processor double integrating the parameter from the first sensor.
20. The system of claim 15, wherein: The motion of the conductor is the gravity vector of the sensing device.