The present disclosure relates generally to intelligent electronic devices (IEDs) for electrical power systems, and more particularly, to an IED including a removable device for storing data relating to electrical power distribution systems.
Electric utility companies (“utilities”) track electric usage by customers by using power meters. These meters track the amount of power consumed at a particular location. These locations range from power substations, to commercial businesses, to residential homes. The electric utility companies use information obtained from the power meter to charge their customers for their power consumption, i.e., revenue metering.
A popular type of power meter is the socket-type power meter, i.e., S-base or Type S meter. As its name implies, the meter itself plugs into a socket for easy installation, removal and replacement. Other meter installations include panel mounted, switchboard mounted, and circuit breaker mounted. Typically, the power meter connects between utility power lines supplying electricity and a usage point, namely, a residence or commercial place of business.
A power meter may also be placed at a point within the utility's power grid to monitor power flowing through that point for distribution, power loss, or capacity monitoring, e.g., at a substation. These power and energy meters are installed in substations to provide a visual display of real-time data and to alarm when problems occur. These problems include limit alarms, breaker control, outages and many other types of events.
In today's times, users are interested in capturing data in an intelligent electronic device (IED) and taking that data back to an office and analyzing or databasing the data at a later time. The common way to gather data in the art now is to download stored data via a communication port to a laptop or a stationary computing device utilizing a serial or Ethernet protocol. The disadvantage of this technology is that the user doesn't always have a laptop available and there is a latency time to gathering the data due to the protocol communication. For instance, to download 2 megabytes of data using traditional serial download schemes could take as long as 10 minutes.
Therefore, a need exists for devices, systems and methods for storing data sensed and generated by an intelligent electronic device (IED), e.g., a power meter, and for managing the stored data to extend the useful life of the meter.
An intelligent electronic device (IED), e.g., an electrical power meter, having at least one removable memory device for storing data sensed and generated by the intelligent electronic device is provided. Utilizing the techniques of the present disclosure, a user will be able to just remove the portable or removable memory device and replace it with a fresh one and then download the data from the removable memory device to a computing device at a later period. In one embodiment, the IED will utilize a USB (Universal Serial Bus) architecture for communicating generated data to the removable memory device.
In one aspect of the present disclosure, an IED is configured to operate as a USB master and/or USB slave device. The USB master configuration for the IED can be implemented using both hardware and software both internally to the host IED processor or by an additional processor or processors or other type of silicon coupled to the IED processor either directly or indirectly. Moreover, the USB interface may also be allowed to be used as a USB slave wherein under user control or wherein the IED itself via its processor or other components stored internally can determine whether it chooses to be a USB master or USB slave device.
It is to be appreciated that the IED can be configured to have the interface act as a Ethernet or RS-232 device or any other type of communication architecture.
According to one aspect of the present disclosure, an intelligent electronic device (IED) is provided including a housing; at least one sensor configured for sensing at least one electrical parameter distributed to a load; at least one analog-to-digital converter coupled to the at least one sensor and configured for converting an analog signal output from the at least one sensor to a digital data; at least one processing unit coupled to the at least one analog-to-digital converter configured to receive the digital data and store the digital data in a removable memory; and at least one device controller coupled to the at least one processing unit, the at least one device controller including at least one interface disposed on the housing for interfacing with the removable memory, wherein the at least one device controller is operative as a master or slave device controller.
In one aspect, the at least one device controller operates in accordance with a Universal Serial Bus (USB) specification.
The above and other aspects, features, and advantages of the present disclosure will become more apparent in light of the following detailed description when taken in conjunction with the accompanying drawings in which:
It should be understood that the elements shown in the figures may be implemented in various forms of hardware, software or combinations thereof. Preferably, these elements are implemented in a combination of hardware and software on one or more appropriately programmed general-purpose devices, which may include a processor, memory and input/output interfaces.
The present description illustrates the principles of the present disclosure. It will thus be appreciated that those skilled in the art will be able to devise various arrangements that, although not explicitly described or shown herein, embody the principles of the disclosure and are included within its spirit and scope.
All examples and conditional language recited herein are intended for pedagogical purposes to aid the reader in understanding the principles of the disclosure and the concepts contributed by the inventor to furthering the art, and are to be construed as being without limitation to such specifically recited examples and conditions.
Moreover, all statements herein reciting principles, aspects, and embodiments of the disclosure, as well as specific examples thereof, are intended to encompass both structural and functional equivalents thereof. Additionally, it is intended that such equivalents include both currently known equivalents as well as equivalents developed in the future, i.e., any elements developed that perform the same function, regardless of structure.
Thus, for example, it will be appreciated by those skilled in the art that the block diagrams presented herein represent conceptual views of illustrative circuitry embodying the principles of the disclosure. Similarly, it will be appreciated that any flow charts, flow diagrams, state transition diagrams, pseudo-code, and the like represent various processes which may be substantially represented in computer readable media and so executed by a computer or processor, whether or not such computer or processor is explicitly shown.
The functions of the various elements shown in the figures may be provided through the use of dedicated hardware as well as hardware capable of executing software in association with appropriate software. When provided by a processor, the functions may be provided by a single dedicated processor, by a single shared processor, or by a plurality of individual processors, some of which may be shared. Moreover, explicit use of the term “processor” or “controller” should not be construed to refer exclusively to hardware capable of executing software, and may implicitly include, without limitation, digital signal processor (“DSP”) hardware, read only memory (“ROM”) for storing software, random access memory (“RAM”), and nonvolatile storage.
Other hardware, conventional and/or custom, may also be included. Similarly, any switches shown in the figures are conceptual only. Their function may be carried out through the operation of program logic, through dedicated logic, through the interaction of program control and dedicated logic, or even manually, the particular technique being selectable by the implementer as more specifically understood from the context.
The word “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any configuration or design described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other configurations or designs. Herein, the phrase “coupled with” is defined to mean directly connected to or indirectly connected with through one or more intermediate components. Such intermediate components may include both hardware and software based components.
As used herein, intelligent electronic devices (“IED's”) include Programmable Logic Controllers (“PLC's”), Remote Terminal Units (“RTU's”), electric power meters, protective relays, fault recorders and other devices which are coupled with power distribution networks to manage and control the distribution and consumption of electrical power. A meter is a device that records and measures power events, power quality, current, voltage waveforms, harmonics, transients and other power disturbances. Revenue accurate meters (“revenue meter”) relate to revenue accuracy electrical power metering devices with the ability to detect, monitor, report, quantify and communicate power quality information about the power which they are metering.
An intelligent electronic device (IED) 10 for monitoring and determining an amount of electrical power usage by a consumer and for providing audible and visual indications to a user is illustrated in
The CPU 18 is configured for receiving the digital signals from the A/D converters 14 to perform the necessary calculations to determine the power usage and controlling the overall operations of the IED 10. In a preferred embodiment, the DSP 16 will receive the digital signals from the A/D converters 14 and perform the necessary calculations to determine the power usage to free the resources of the CPU 18. The CPU 18 will include a microprocessor 20 executing instructions and performing various calculations, flash memory 22 for storing executable instructions and permanent data tables for controlling the overall operation of the microprocessor and random access memory (RAM) 24 for holding data during computations by the microprocessor 20.
A first memory 26 is coupled to CPU 18 and stores calibration and setup parameters of the IED 10, e.g., meter configuration, serial number of the device, etc. Memory 26 may be an integrated circuit in the form of a FLASH or EEPROM, or any other known or to be developed type of memory which is nonvolatile, capable of being changed in the IED, and amenable to making such changes difficult for an end user.
The IED 10 further includes a second memory 28 for storing sensed and generated data for further processing and for retrieval, e.g., data logs. Memory 28 may be flash memory and may be removable or non-removable. In one embodiment, data stored on memory 28 may be retrieved by an external device or computer via a communication device 30. In another embodiment, where memory 28 is removable, memory 28 will be in the form of a memory card such as a CompactFlash card, a Memory Stick, a SmartMedia card, etc., and data stored therein will be retrieved from an appropriate memory card reader.
A power supply 32 is also provided for providing power to each component of the IED 10. In one embodiment, the power supply 32 is a transformer with its primary windings coupled to the incoming power distribution lines and having an appropriate number of windings to provide a nominal voltage, e.g., 5 VDC, at its secondary windings. In other embodiments, power is supplied from an independent source to the power supply 32, e.g., from a different electrical circuit, an uninterruptible power supply (UPS), etc.
The IED 10 of the present disclosure will have a user interface for interacting with a user and for communicating events, alarms and instructions to the user. The user interface will include a display 34 for providing visual indications to the user. The display 34 may include a touch screen, a liquid crystal display (LCD), a plurality of LED number segments, individual light bulbs or any combination of these. The display 34 may provide the information to the user in the form of alpha-numeric lines, computer-generated graphics, videos, etc. The user interface will include an input device 35 for entering data, e.g., parameters, limits, etc. The input device may include pushbuttons, a keypad, a touch screen, at least one dial, etc. The user interface may also include a speaker or audible output means 36 for audibly producing instructions, alarms, data, etc. The speaker 36 will be coupled to the CPU 18 via a digital-to-analog converter (D/A) for converting digital audio files stored in memory to analog signals playable by the speaker 36.
The IED 10 will include the communication device 30 for enabling data communications between the IED 10 and other computing devices, e.g., a desktop computer, laptop computer, other IEDs, etc. The communication device 30 may be a modem, network interface card (NIC), wireless transceiver, etc. As described above, the IED 10 may be coupled to a personal computer over a network, e.g., a LAN, WAN, the Internet, etc., via the communication device 30, where the personal computer will retrieve data, e.g., logs, from the IED 10. The communication device 30 will perform its functionality by hardwired and/or wireless connectivity. The hardwire connection may include but is not limited to hard wire cabling e.g., parallel or serial cables, USB cable, Firewire (1394 connectivity) cables, and the appropriate port. The wireless connection will operate under any of the various known wireless protocols including but not limited to Bluetooth™ interconnectivity, infrared connectivity, radio transmission connectivity including computer digital signal broadcasting and reception commonly referred to as Wi-Fi or 802.11.X (where x denotes the type of transmission), satellite transmission or any other type of communication protocols or systems currently existing or to be developed for wirelessly transmitting data. It is to be appreciated that the network may be a local area network (LAN), wide area network (WAN), the Internet or any known network that couples a plurality of computers to enable various modes of communication via network messages. Furthermore, the IED 10 will communicate using the various known protocols such as Transmission Control Protocol/Internet Protocol (TCP/IP), File Transfer Protocol (FTP), Hypertext Transfer Protocol (HTTP), etc. and secure protocols such as Internet Protocol Security Protocol (IPSec), Point-to-Point Tunneling Protocol (PPTP), Secure Sockets Layer (SSL) Protocol, etc.
It is to be understood that the present disclosure may be implemented in various forms of hardware, software, firmware, special purpose processors, or a combination thereof. The IED may also include an operating system and micro instruction code. The various processes and functions described herein may either be part of the micro instruction code or part of an application program (or a combination thereof) which is executed via the operating system.
It is to be further understood that because some of the constituent system components and method steps depicted in the accompanying figures may be implemented in software, the actual connections between the system components (or the process steps) may differ depending upon the manner in which the present disclosure is programmed. Given the teachings of the present disclosure provided herein, one of ordinary skill in the related art will be able to contemplate these and similar implementations or configurations of the present disclosure.
As the IED 10 collects data and processes the collected data, the data will be stored on, for example, flash memory 28. The data may be stored in various types of logs, e.g., a historical trend log which is a collection of time-stamped records used to track any parameter over time. Other exemplary logs may include limit logs, event-triggered waveforms logs (e.g., records a waveform when a user-programmable value goes out of limit and when the value returns to normal), power quality logs (e.g., records magnitude and duration of voltage and current surges and sags for every power quality event), status change (input) logs, control output (relay) logs, system event logs, flicker logs and reset logs. However, flash devices “wear out” after a large but finite number of erases. Furthermore, the IED 10 may determine and store meter diagnostic data. This can become an issue if the same place in the flash memory is used over and over again.
Flash devices are partitioned into sectors and impose the rule that all bytes in a sector must be erased at the same time. Thus, for managing the number of erases, the sector is the basic unit. The IED 10 of the present disclosure manages sector wear by placing data in the flash memory 28 so that the number of erases in all sectors is equalized over time. The IED 10 uses the flash memory for its logs. This technique is appropriate for any similar application in which memory contents change over time and in which there is slightly more capacity in the flash memory than is actually needed. The extra capacity is used to ensure that free sectors are always available when needed.
In one embodiment, the memory for storing the data and/or logs is configured as removable memory. The IED of this embodiment facilitates replacing or swapping out the memory if the memory is “worn” or about to go bad. In one embodiment, the IED will utilize a USB (Universal Serial Bus) architecture for communicating generated data to the removable memory.
Referring to
One of the common issues with USB design is that since the connections are electrical and not optical connections, they run a danger to the user when connected to a high power source, e.g., an electrical power distribution system. Because of this danger, there will need to be a large amount of isolation between the USB connector and the electrical voltage input. One elegant and innovative way of providing isolation is to connect the USB connector port to the front panel of the housing and then utilize the power coming from the USB reading device, i.e., master device, and not from the meter or IED to power the connector and the USB electronics.
Referring to
At least one optoisolator 152 is then coupled from the secondary of the USB chip 150 to the at least one host or intermediary processor 18 of the IED. This allows for very high electrical isolation and very low cost eliminating the needs of isolation transformers, a multiple tap power supply or DC to DC isolating power supplies. When a master device is coupled to the USB master port 142, the master device such as a lap top computer, smart phone or other intelligent device is providing power to the USB master device controller 150.
USB slave port 144 is coupled to a slave device controller 154. The slave device controller 154 may be any known programmable device operating in accordance with one of the various known USB specifications and may include one or more drivers for various slave devices. The slave device controller 154 is coupled to the at least one host or intermediary processor 18 of the IED without the use of an optoisolator. Since the slave device, e.g., a memory stick, in most cases will not have a power source, a power source internal to the IED will be utilized to power the slave device controller 154 and the slave device coupled to USB slave port 144. In one embodiment, power supply 32 will be coupled to the slave device controller 154. It is to be appreciated that at least one intermediary device may be used to coupled power supply 32 to the slave device controller 154 to step down or condition the power being provided. It is envisioned that the slave device controller 154 could also be separate hardware or a separate processing module or could be embedded into the host CPU 18 as hardware, software or a combination thereof.
It is envisioned by the teachings of the present disclosure that the USB master and USB slave connections depicted in
In another embodiment, the IED 210 includes a USB interface 240 that has only one port 241 as shown in
Referring to
The mode of the device controller 251 will be determined based on the type of device coupled to port 241. If a master device, e.g., PC 146, is coupled to the port 241, the device controller 251 will need to operate in a master mode. In one embodiment, switch 256 will transmit a control signal to the device controller 251 to change its mode. The switch 256 will operate either based on a manual input via a button or the like 243 mounted on the IED adjacent to the port 241 or the switch will receive a signal from the CPU 18 in the case where an operator changes the mode via a touch screen 235. When the device controller 251 is placed in the master mode, that is, a USB master device is coupled to port 241 and the IED 210 is operating as a USB slave, switch 256 sends a master control signal to the device controller 251 and removes the power supply from the circuit. In the master mode of the device controller 251, the device controller 251 will receive power via the port 241 from the master device, e.g., a laptop computer. When the device controller 251 is placed in the slave mode, that is, a USB slave device is coupled to port 241 and the IED 210 is operating as a USB master, switch 256 sends a slave control signal to the device controller 251 and switches in the power supply 232 to the circuit. In the slave mode of the device controller 251, the device controller 251 will receive power via the power supply 232 and provide power to the slave device, e.g., a removable memory device.
It is to be appreciated that the mode of the device controller 251 could be switched automatically without a manual input from an operator. For example, the device controller 251 will auto-detect if the connected device is a master or slave device. For example, once the device controller 251 determines that something is connected to port 241, the device controller will wait a predetermined period of time to see if a command or message is received. If no command or message is received, the connected device is most likely a slave device since slave device do not send commands or messages and the device controller 251 will send an appropriate control signal to switch 256. Alternatively, if the device controller 251 receives a command or message from the connected device, the device controller 251 will send the appropriate signal to the switch 256 to remove power.
In utilizing the hardware device(s) described herein, the user will be able to accomplish the various applications of the disclosure which are described below.
Utilizing a USB memory stick, the IED of the present disclosure will be a USB master. As a USB master, the IED uses the USB memory stick as a storage medium. The USB master could treat the stick as a USB hard drive or a form of IDE interface. This being the case, the IED will be programmed to control the USB memory stick for placing data and/or files on to the memory stick. The IED will perform this function by sensing the electrical parameters of the electrical power distribution system, processing the data collected from the sensors 12 and analog-to-digital converters 14 and then storing the raw or modified or computed results from such sensing to the USB “drive”. The IED will also utilize a real time clock or other type of time sensing algorithm to store with data a time stamp. This will allow a user to have timed analysis of events on the line of the electrical power distribution system.
Utilizing this technique, the user will be able to ascertain historical profiling such as by non-limiting example 15 minute watt and VARs distribution, energy over a month and many other applications. Additionally, the IED can be configured to sense or received data from sensors or be coupled to external sensors whether directly or indirectly to sense non-electrical parameters such as ambient temperature, gas pressure, greenhouse emissions or other such parameters. This data can be stored with the time stamp in the USB drive for additional later analysis.
In one embodiment, the IED stores the data in a comma separated value (CSV) format, as shown in
Other non-limiting embodiments include that data can be stored in a binary or ASCII format so that either a computer could read or process the data in a recognizable format. Such storage of data could include the Electric Power Research Institute PQDIF format, Comtrade format and/or ANSI C12.19 protocol data. Other protocols and file formats are contemplated by the present disclosure. The above are only for illustrative examples.
Furthermore, the USB memory stick, i.e., USB slave device, could also be used to store a shadow copy of the internal system memory or be used as a debug device for the IED to ascertain if it is working properly. This USB memory stick or device could be used by the IED to store debug codes, failures codes or provide a log of executable information that the internal IED processor is using.
When the IED is operating as a USB slave, the IED to be able to download stored data from internal meter storage and is treated like a “serial” port wherein a computing device can establish a communication stream with the meter by serial master/slave communication such as but not limited to Modbus and DNP 3.0 type protocols or PPP, TCP/IP or other such communication protocols. The USB “slave” could also allow data to be sent to and from the IED utilizing file transferring methods such as FTP or other such file transferring protocol.
Other forms of data retrieval anticipated by the present disclosure would be to use removable serial flash such as SD flash manufactured by SanDisk Corporation of Milpitas, Calif. (an exemplary flash is commercially available as model number SDSDRH-032G-A11) or parallel flash such as but not limited to NOR flash and Compact Flash, an example of which is manufactured by SanDisk Corporation as model number SDCFX-032G-A61. This technology will enable use similar to the USB type device and as such is contemplated by the present disclosure.
Different mounting forms are envisioned by the present disclosure. One preferable form would be to mount the USB port in the front panel of the device. This allows a user to access either the USB port to remove and install new USB media, e.g., a storage device. The USB media can be mounted on the front panel of the device anywhere accessible to a meter once install in an electrical switchgear panel. Other mounting options would include mounting the USB storage device in the rear of the instrument behind the electrical switchgear providing some security from unauthorized removal.
In one embodiment, the USB interface 542 is disposed in a recess 545 of the housing of the IED 510 as illustrated in
It is also envisioned that mounting could be within a door 570 on the instrument or IED 510 providing an enclosed structure for the USB or similar type memory as illustrated in
It is to be appreciated that the IED may communicate to devices other than a storage device. For example, when the IED is in a master mode, the IED may be coupled to a USB slave device(s) such as: a printer for printing data measured or calculated by the IED; an input device, e.g., a mouse, joystick, keyboard, etc., for navigating the display 34; a image capture device, e.g., a webcam, to capture images of the environment surrounding the IED; and a communication device (e.g., a modem, a wireless transceiver, a network interface card, etc.) for enabling the IED to transmit or forward its data to other IEDs, computing devices, servers, etc. It is to be appreciated this listing of USB slave devices is merely illustrative and not exhaustive of the possible devices that could be coupled to the IED.
In one embodiment, the IED is configured or selected to be the USB master device and can connect up to 127 slaves devices via at least one USB hub. In this embodiment, the USB master device, will go through an enumeration process, either on power up or when devices are connected via a USB bus, and assign each connected slave device an address. The IED as the USB master device will query each device to find out what type of data transfer the specific device wants to perform, for example, interrupt mode, bulk transfer mode or isochronous mode. The IED as the USB master device can also send commands or query parameters with control packets. The Universal Serial Bus divides the available bandwidth into frames with the USB master IED device keeping track of the total bandwidth that the slave devices are requesting and controls the frames to ensure the slaves devices get the bandwidth they need.
It is to be appreciated that the teachings, and devices, of the present disclosure are compatible with any known or to be developed USB standard, for example, USB 1.0, 2.0 and 3.0 (also known as SuperSpeed USB) including any preceding and intermediate versions. Furthermore, the architectures disclosed herein support the following signaling or transmission rates: a low speed rate of 1.5 Mbits/s as defined by USB 1.0; a full speed rate of 12 Mbits/s as defined by USB 1.1; a hi-speed rate of 480 Mbits/s as defined by USB 2.0; and a SuperSpeed rate of 5.0 Gbits/s as defined by USB 3.0. Other signaling or transmission rates are also contemplated. Regardless of the specific standard employed, the IED of the present disclosure is forward and backward compatible to communicate to any existing or to be developed external device.
Furthermore, it is to be appreciated that the disclosed interfaces or ports, e.g., interfaces 140, 240 and ports 142, 144, 241, include any known or to be developed USB connector, e.g., a plug or receptacle, such as a type A connector, a type B connector, Mini-A connector, Mini-B connector, Micro-A connector, Micro-B connector, Micro-AB connector, etc. Additionally, the interfaces and ports may include proprietary connectors such as the UltraPort employed by IBM, 10P10C connectors employed by American Power Conversion, HTC ExtUSB employed by HTC Corporation, the Port-Port connector employed by Nokia, among others.
Referring to
Additionally, the face plate 613 includes a plurality of indicators 708 which, when illuminated, indicate to the user the “type of reading”, the “% of load bar”, the “parameter designation” which indicates the reading which is being displayed on displays 706, a “scale selector” (e.g., Kilo or Mega multiplier of Displayed Readings), etc. Face plate 613 includes a plurality of buttons 710 (e.g., a “menu” button, an “enter” button, a “down” button, a “right” button, etc.) for performing a plurality of functions, including and not limited to: viewing of meter information; enter display modes; configuring parameters; performing re-sets; performing LED checks; changing settings; viewing parameter values; scrolling parameter values; and viewing limit states. The housing 611 includes voltage connections or inputs 712 provided on rear surface 702b thereof, and current inputs 714 provided along right side surface 702e thereof. The IED 610 may include a first interface or communication port 716 for connection to a master and/or slave device. Desirably, first communication port 716 is situated in rear surface 702b of housing 611.
The face plate 613 further includes a communication interface 640. The interface 640 is protected by a plug 644 which when removed reveals a communication port opening 642, as shown in
Referring to
Referring to
Referring to
When sealing the interface 640 with the plug 644, the cover 646 is aligned with the channel 647 and pressed toward the face of the IED 610. The seal 652 mates with the channel 647 until the lip portion 650 makes contact with the channel 647, sealing the interface from the elements of the environment. It is to be appreciated that the plug may be configured from a variety of materials including, but not limited to, plastic, rubber, nylon, etc. In certain embodiments, the plug 644 will make a water-tight seal with the channel 647. The water-tight seal created could block out water, moisture, alternate liquids, dust, alternate solids, etc., and possibly keep the port, e.g., a USB port free of particles that could potentially damage the electronics described above.
Removal of the plug 644 involves lifting the cover 646 until the seal 652 disengages the channel 647. The cover 646 may now be rotated about the longitudinal axis of the leg portion 648 to exposed the port opening 642. It is to be appreciated that the step 654 of the leg portion 648 will retain the plug 644 to the bezel 649 thus preventing loss of the plug 644.
It is further to be appreciated that any of the ports described above may be arranged with the port opening 642 of the interface 640. Additionally, other ports may be employed, for example, an Ethernet port, a RS-232 port, a RS485 port, etc.
Furthermore, it is to be appreciated that the plug may be used to protect a port, a switch, a reset button, a demand reset or any other user accessible item on the face or around the body or housing of the IED. The plug may also have a mechanism to be locked as sealed using a meter seal, wire lock, pad lock or other type of lock that would enter through an opening and seal the plug to the instrument blocking removal. For example, referring to
Although the disclosure herein has been described with reference to particular illustrative embodiments, it is to be understood that these embodiments are merely illustrative of the principles and applications of the present disclosure. Therefore numerous modifications may be made to the illustrative embodiments and other arrangements may be devised without departing from the spirit and scope of the present disclosure, which is defined by the appended claims.
Furthermore, although the foregoing text sets forth a detailed description of numerous embodiments, it should be understood that the legal scope of the present disclosure is defined by the words of the claims set forth at the end of this patent. The detailed description is to be construed as exemplary only and does not describe every possible embodiment, as describing every possible embodiment would be impractical, if not impossible. One could implement numerous alternate embodiments, using either current technology or technology developed after the filing date of this patent, which would still fall within the scope of the claims.
It should also be understood that, unless a term is expressly defined in this patent using the sentence “As used herein, the term ‘——————’ is hereby defined to mean . . . ” or a similar sentence, there is no intent to limit the meaning of that term, either expressly or by implication, beyond its plain or ordinary meaning, and such term should not be interpreted to be limited in scope based on any statement made in any section of this patent (other than the language of the claims). To the extent that any term recited in the claims at the end of this patent is referred to in this patent in a manner consistent with a single meaning, that is done for sake of clarity only so as to not confuse the reader, and it is not intended that such claim term be limited, by implication or otherwise, to that single meaning. Finally, unless a claim element is defined by reciting the word “means” and a function without the recital of any structure, it is not intended that the scope of any claim element be interpreted based on the application of 35 U.S.C. § 112, sixth paragraph.
This application is a continuation application of U.S. application Ser. No. 13/834,737, filed on Mar. 15, 2016, which is a continuation-in-part application of U.S. application Ser. No. 12/628,636 filed on Dec. 1, 2009, now U.S. Pat. No. 9,885,739, the contents of which are hereby incorporated by reference in their entireties.
Number | Name | Date | Kind |
---|---|---|---|
D56045 | White | Aug 1920 | S |
D76149 | Olsen | Feb 1924 | S |
1705301 | Miller | Mar 1929 | A |
D187740 | Littlejohn | Apr 1960 | S |
D199808 | Gazzman, III | Dec 1964 | S |
D201100 | Little et al. | May 1965 | S |
D241006 | Wallace | Aug 1976 | S |
3989334 | Fortino | Nov 1976 | A |
D273574 | Overs | Apr 1984 | S |
4609247 | Annoot | Sep 1986 | A |
5014213 | Edwards et al. | May 1991 | A |
D332923 | Polydoris et al. | Feb 1993 | S |
D343786 | Hines et al. | Feb 1994 | S |
D348019 | Kocol et al. | Jun 1994 | S |
5459850 | Clay et al. | Oct 1995 | A |
5475693 | Christopherson et al. | Dec 1995 | A |
D366434 | Brown et al. | Jan 1996 | S |
5485595 | Assar et al. | Jan 1996 | A |
5581470 | Pawloski | Dec 1996 | A |
5598370 | Niijima et al. | Jan 1997 | A |
5634050 | Krueger et al. | May 1997 | A |
5640529 | Hasbun | Jun 1997 | A |
5650936 | Loucks et al. | Jul 1997 | A |
5736847 | Doorn et al. | Apr 1998 | A |
5787445 | Daberko | Jul 1998 | A |
5828576 | Loucks et al. | Oct 1998 | A |
5841269 | Schoonmaker et al. | Nov 1998 | A |
5897661 | Baranovsky et al. | Apr 1999 | A |
5995911 | Hart | Nov 1999 | A |
6000034 | Lightbody et al. | Dec 1999 | A |
6007353 | Webster | Dec 1999 | A |
D427533 | Cowan et al. | Jul 2000 | S |
D429655 | Cowan et al. | Aug 2000 | S |
D435471 | Simbeck et al. | Dec 2000 | S |
6183274 | Allum | Feb 2001 | B1 |
6185508 | Van Doom et al. | Feb 2001 | B1 |
6186842 | Hirschbold et al. | Feb 2001 | B1 |
D439535 | Cowan et al. | Mar 2001 | S |
6236949 | Hart | May 2001 | B1 |
D443541 | Hancock et al. | Jun 2001 | S |
6256762 | Beppu | Jul 2001 | B1 |
D455066 | Kolinen | Apr 2002 | S |
6384946 | Pitsch et al. | May 2002 | B1 |
6397155 | Przydatek et al. | May 2002 | B1 |
D458863 | Harding et al. | Jun 2002 | S |
D459259 | Harding et al. | Jun 2002 | S |
6466434 | Tsai | Oct 2002 | B1 |
6476595 | Heuell et al. | Nov 2002 | B1 |
6476729 | Liu | Nov 2002 | B1 |
6493644 | Jonker et al. | Dec 2002 | B1 |
6513091 | Blackmon et al. | Jan 2003 | B1 |
6563697 | Simbeck et al. | May 2003 | B1 |
6611773 | Przydatek et al. | Aug 2003 | B2 |
6611922 | Ozcetin et al. | Aug 2003 | B2 |
6615147 | Jonker et al. | Sep 2003 | B1 |
6636030 | Rose et al. | Oct 2003 | B1 |
6654842 | Park | Nov 2003 | B1 |
6671635 | Forth et al. | Dec 2003 | B1 |
6671654 | Forth et al. | Dec 2003 | B1 |
6687627 | Gunn et al. | Feb 2004 | B1 |
6694270 | Hart | Feb 2004 | B2 |
6735535 | Kagan et al. | May 2004 | B1 |
6737855 | Huber et al. | May 2004 | B2 |
6745138 | Przydatek et al. | Jun 2004 | B2 |
6751562 | Blackett et al. | Jun 2004 | B1 |
6751563 | Spanier et al. | Jun 2004 | B2 |
6792337 | Blackett et al. | Sep 2004 | B2 |
6792364 | Jonker et al. | Sep 2004 | B2 |
6798190 | Harding et al. | Sep 2004 | B2 |
6798191 | Macfarlane et al. | Sep 2004 | B1 |
6813571 | Lightbody et al. | Nov 2004 | B2 |
6825776 | Lightbody et al. | Nov 2004 | B2 |
6853978 | Forth et al. | Feb 2005 | B2 |
6871150 | Huber et al. | Mar 2005 | B2 |
D505087 | Ricci et al. | May 2005 | S |
6944555 | Blackett et al. | Sep 2005 | B2 |
6957158 | Hancock et al. | Oct 2005 | B1 |
6961641 | Forth et al. | Nov 2005 | B1 |
6983211 | Cowan et al. | Jan 2006 | B2 |
6988025 | Ransom et al. | Jan 2006 | B2 |
6988182 | Teachman et al. | Jan 2006 | B2 |
6990395 | Ransom et al. | Jan 2006 | B2 |
7006934 | Jonker et al. | Feb 2006 | B2 |
7010438 | Hancock et al. | Mar 2006 | B2 |
7072779 | Hancock et al. | Jul 2006 | B2 |
D525893 | Kagan et al. | Aug 2006 | S |
D526920 | Kagan et al. | Aug 2006 | S |
7085824 | Forth et al. | Aug 2006 | B2 |
7089089 | Cumming et al. | Aug 2006 | B2 |
7096316 | Karr et al. | Aug 2006 | B1 |
7127328 | Ransom | Oct 2006 | B2 |
D532747 | Ricci et al. | Nov 2006 | S |
7136384 | Wang | Nov 2006 | B1 |
D534120 | Ricci et al. | Dec 2006 | S |
7155350 | Kagan | Dec 2006 | B2 |
7158050 | Lightbody et al. | Jan 2007 | B2 |
7174258 | Hart | Feb 2007 | B2 |
7174261 | Gunn et al. | Feb 2007 | B2 |
7184904 | Kagan | Feb 2007 | B2 |
7188003 | Ransom et al. | Mar 2007 | B2 |
7191076 | Huber et al. | Mar 2007 | B2 |
7216043 | Ransom et al. | May 2007 | B2 |
D545181 | Kagan et al. | Jun 2007 | S |
7246014 | Forth et al. | Jul 2007 | B2 |
7248977 | Hart | Jul 2007 | B2 |
7248978 | Ransom | Jul 2007 | B2 |
7249265 | Carolsfeld et al. | Jul 2007 | B2 |
7256709 | Kagan | Aug 2007 | B2 |
7271996 | Kagan et al. | Sep 2007 | B2 |
7294997 | Kagan | Nov 2007 | B2 |
7304586 | Wang et al. | Dec 2007 | B2 |
7305310 | Slota et al. | Dec 2007 | B2 |
7337081 | Kagan | Feb 2008 | B1 |
7417419 | Tate | Aug 2008 | B2 |
7472138 | Adkins et al. | Dec 2008 | B2 |
D615895 | Beattie | May 2010 | S |
7868782 | Ehrke et al. | Jan 2011 | B2 |
D642083 | Blanc et al. | Jul 2011 | S |
D653572 | Ohtani et al. | Feb 2012 | S |
8176174 | Kagan | May 2012 | B2 |
D666933 | Hoffman et al. | Sep 2012 | S |
8310403 | Nahar | Nov 2012 | B2 |
8325057 | Salter | Dec 2012 | B2 |
8365960 | Kalaouze | Feb 2013 | B1 |
D682720 | Kagan et al. | May 2013 | S |
D682721 | Kagan et al. | May 2013 | S |
8587949 | Banhegyesi et al. | Nov 2013 | B2 |
D712289 | Kagan et al. | Sep 2014 | S |
D712290 | Kagan et al. | Sep 2014 | S |
D712291 | Kagan et al. | Sep 2014 | S |
8947246 | Aiken | Feb 2015 | B2 |
9063181 | Banker | Jun 2015 | B2 |
D739283 | Kagan | Sep 2015 | S |
9885739 | Kagan | Feb 2018 | B2 |
20010027500 | Matsunaga | Oct 2001 | A1 |
20020051466 | Bruckman | May 2002 | A1 |
20020114326 | Mahalingaiah | Aug 2002 | A1 |
20020162014 | Przydatek | Oct 2002 | A1 |
20020165677 | Lightbody et al. | Nov 2002 | A1 |
20020166022 | Suzuki | Nov 2002 | A1 |
20020188814 | Saito et al. | Dec 2002 | A1 |
20030003908 | McGrew et al. | Jan 2003 | A1 |
20030014200 | Jonker et al. | Jan 2003 | A1 |
20030065459 | Huber et al. | Apr 2003 | A1 |
20030066311 | Li et al. | Apr 2003 | A1 |
20030101008 | Hart | May 2003 | A1 |
20030105608 | Hart | Jun 2003 | A1 |
20030132742 | Harding et al. | Jul 2003 | A1 |
20030154471 | Teachman et al. | Aug 2003 | A1 |
20030175025 | Watanabe et al. | Sep 2003 | A1 |
20030210699 | Holt et al. | Nov 2003 | A1 |
20030212512 | Hart | Nov 2003 | A1 |
20030220752 | Hart | Nov 2003 | A1 |
20040028041 | Yasue | Feb 2004 | A1 |
20040066311 | Giles et al. | Apr 2004 | A1 |
20040138786 | Blackett et al. | Jul 2004 | A1 |
20040138787 | Ransom et al. | Jul 2004 | A1 |
20040138835 | Ransom et al. | Jul 2004 | A1 |
20040172207 | Hancock et al. | Sep 2004 | A1 |
20040183522 | Gunn et al. | Sep 2004 | A1 |
20040193329 | Ransom et al. | Sep 2004 | A1 |
20040229578 | Lightbody et al. | Nov 2004 | A1 |
20050017874 | Lightbody et al. | Jan 2005 | A1 |
20050027464 | Jonker et al. | Feb 2005 | A1 |
20050071106 | Huber et al. | Mar 2005 | A1 |
20050273281 | Wall et al. | Dec 2005 | A1 |
20050275397 | Lightbody et al. | Dec 2005 | A1 |
20050281105 | Oshima | Dec 2005 | A1 |
20050288876 | Doig et al. | Dec 2005 | A1 |
20050288877 | Doig et al. | Dec 2005 | A1 |
20060039196 | Gorobets et al. | Feb 2006 | A1 |
20060052958 | Hancock et al. | Mar 2006 | A1 |
20060070416 | Teratani | Apr 2006 | A1 |
20060071813 | Kagan | Apr 2006 | A1 |
20060076944 | Weikel | Apr 2006 | A1 |
20060077999 | Kagan et al. | Apr 2006 | A1 |
20060086893 | Spanier et al. | Apr 2006 | A1 |
20060106972 | Gorobets et al. | May 2006 | A1 |
20060133454 | Beckwith | Jun 2006 | A1 |
20060161400 | Kagan | Jul 2006 | A1 |
20060170409 | Kagan et al. | Aug 2006 | A1 |
20060230394 | Forth et al. | Oct 2006 | A1 |
20060271244 | Cumming et al. | Nov 2006 | A1 |
20070033151 | Lee, Jr. | Feb 2007 | A1 |
20070055889 | Henneberry et al. | Mar 2007 | A1 |
20070067119 | Loewen | Mar 2007 | A1 |
20070067121 | Przydatek et al. | Mar 2007 | A1 |
20070114054 | Mon | May 2007 | A1 |
20070136010 | Gunn et al. | Jun 2007 | A1 |
20070150214 | Qin et al. | Jun 2007 | A1 |
20070165365 | Kamiya | Jul 2007 | A1 |
20080046205 | Gilbert et al. | Feb 2008 | A1 |
20080065335 | Doig et al. | Mar 2008 | A1 |
20080263245 | Hsieh | Oct 2008 | A1 |
20090011738 | Sasakura | Jan 2009 | A1 |
20090140880 | Flen | Jun 2009 | A1 |
20090182921 | Lin et al. | Jul 2009 | A1 |
20100289457 | Onnerud et al. | Nov 2010 | A1 |
20120314354 | Rayner | Dec 2012 | A1 |
20130297840 | Kagan et al. | Nov 2013 | A1 |
Number | Date | Country |
---|---|---|
07235881 | May 1995 | JP |
Entry |
---|
Anderson, D., USB System Architecture, Nov. 2000, Addison-Wesley Professional, 9th Printing, pp. 22-23. |
BE1-951 Multifunction Protection System, Basler Electric, Sep. 2012 pp. 1-12. |
IEEE Standard Common Format for Transient Data Exchange, Oct. 15, 1999, IEEE. |
Jemstar High Accuracy Revenue Meter for Generation, Transmission, and Industrial Power Measurement, Ametek Power Instruments, 2012, pp. 1-2. |
Jemstar Retrofit for Generation, Transmission, and Industrial Power Measurement, Ametek Power Instruments, 2007, pp. 1-2. |
Mark-V EMS60 Intelligent Energy Meter, Advanced High-Accuracy Meter With Integrated Data Telemetry Solutions and Power Quality Monitoring, Transdata Energy Metering and Automation, 2010, pp. 1-2. |
Nexus 1262/1272 High Performance Utility Billing Meters With Communication & Advanced Power Quality, Electro Industries/Gaugetech, 062112 pp. 1-12. |
Nexus 1262/1272 Switchboard Meter Quick Start, Electro Industries-Gaugetech, 083112, pp. 1-4. |
Power Quality Standards Coordinating Committee, IEEE P1159.3/D9 Draft: Recommended Practice for the Transfer of Power Quality Data, Aug. 1, 2002, IEEE Standards Activities Department. |
Powerlogic ION8650, Schneider Electric, 2011, pp. 1-12. |
The Authoritative Dictionary of IEEE Standards Terms, Seventh Edition, IEEE Std 100-2000 , Published 2000, p. 574. |
Xu Hong, Wang Jianhua, “An Extendable Data Engine based on OPC Specification”; Computer Standards & Interfaces 26 (2004) 515-525; Dec. 5, 2003. |
Number | Date | Country | |
---|---|---|---|
20180225231 A1 | Aug 2018 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 13834737 | Mar 2013 | US |
Child | 15921308 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 12628636 | Dec 2009 | US |
Child | 13834737 | US |