A microfiche appendix, Appendix A, is incorporated by reference above of a computer program listing. The total number of microfiche is 6. The total number of frames is 186. A second microfiche appendix, Appendix B, is also incorporated by reference above of schematic diagrams. The total number of microfiche is 1 and the total number of frames is 23.
A compact disk appendix is included containing computer program code listings pursuant to 37 C.F.R. 1.52(e) and is hereby incorporated by reference. The compact disk contains program code files in ASCII format. The total number of compact disks is 1 and the files included on the compact disk are as follows:
A portion of the disclosure of this patent document contains material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent file or records, but otherwise reserves all copyright rights whatsoever.
Generally, this invention relates to revenue meters of the type used by energy suppliers to accurately measure electrical energy delivered to consumers. More particularly, this invention relates to improved interfacing of the revenue meters.
In a typical electrical distribution system, an electrical supplier or utility company generates electrical energy and distributes the electrical energy to consumers via a power distribution network. The power distribution network is the network of electrical distribution wires which link the electrical supplier to its consumers. At the consumer's facility, there will typically be an electrical energy meter (revenue meter) connected between the consumer and the power distribution network to measure the consumer's electrical demand. The revenue meter is an electrical energy measurement device which accurately measures the amount of electrical energy flowing to the consumer from the supplier. The amount of electrical energy measured by the meter is then used to determine the amount required to compensate the energy supplier.
Typically, the electrical energy is delivered to the customers as an alternating current (“AC”) voltage that approximates a sine wave over a time period. The term “alternating waveform” generally describes any symmetrical waveform, including square, sawtooth, triangular, and sinusoidal waves, whose polarity varies regularly with time. The term “AC” (i.e., alternating current), however, almost always means that the current is produced from the application of a sinusoidal voltage, i.e., AC voltage. The expected frequency of the AC voltage, e.g., 50 Hertz (“Hz”), 60 Hz, or 400 Hz, is usually referred to as the “fundamental” frequency. Integer multiples of this fundamental frequency are usually referred to as harmonic frequencies.
While the fundamental frequency is the frequency that the electrical energy is expected to arrive with, various distribution system and environmental factors can distort the fundamental frequency, i.e., harmonic distortion, can cause spikes, surges, or sags, and can cause blackouts, brownouts, or other distribution system problems. These problems can greatly affect the quality of power received by the power customer at its facility or residence as well as make accurate determination of the actual energy delivered to the customer very difficult.
In order to solve these problems, socket based revenue meters have been developed to provide improved techniques for accurately measuring the amount of power used by the customer so that the customer is charged an appropriate amount and so that the utility company receives appropriate compensation for the power delivered and used by the customer.
To provide user input to the revenue meter, known meters typically utilize cumbersome keys or buttons located within a sealed cover of the revenue meter, or keys which are accessible from the outside but are sealed and cannot be activated without removing the seal. In both cases, at least one security seal is installed to prevent or indicate unauthorized access. Thus, the seal must be replaced every time the meter is accessed via the keys or buttons.
In addition, a problem exists when keys are added to the meter cover to mechanically actuate the interface of the revenue meter since tolerances in both the manufactured parts and the assembly process can cause an internal structure of the assembled revenue meter to misalign with the cover, for example, lean and twist with relation to the cover, resulting in misalignment of the mechanical actuators with the actual interface of the meter. Therefore, it is important to line up the keys/mechanical actuators on the cover with the appropriate buttons on the revenue meter.
Also, with the increasing complexity of revenue meters, usability has often been restricted by the user interface. Available systems permit the user to customize the data which can be viewed from the meter only with auxiliary devices. In available meters, a user can program the viewed data with an auxiliary device, such as a computer or calibration equipment. Such modifications often cannot be done easily in the field.
Accordingly, there is a need to provide a device with a user interface that allows the user to easily program various desired features for the device and provides a means to display various selected calculations and results generated by the meter.
In addition there is a need for an improved revenue meter that provides easily accessible and easy to use interfaces.
The present invention is defined by the following claims, and nothing in this section should be taken as a limitation on those claims. By way of introduction, one embodiment described below relate to a revenue meter for measuring the delivery of electrical energy from an energy supplier to a consumer through an electric circuit. The revenue meter includes bayonet terminals disposed on the meter, the terminals being mateable with matching jaws of a detachable meter mounting device. The revenue meter further includes a base coupled with the bayonet terminals and a cover coupled with the base, thereby preventing physical access to the meter. The revenue meter further includes at least one sensor operative to be coupled with the electric circuit and operative to sense at least current in the electric circuit and generate at least one analog signal indicative thereof. The revenue meter further includes a microprocessor coupled with the current sensor and operative to receive the at least one digital sample and compute at least one value therefrom. The revenue meter further includes a fiber optic communications link, coupled to the microprocessor.
Further aspects and advantages of the invention are discussed below in conjunction with the preferred embodiments.
a shows the revenue meter of
b shows the revenue meter of
c shows the revenue meter of
d shows the revenue meter of
e shows the revenue meter of
f shows the revenue meter of
g shows the revenue meter of
The disclosed embodiments provide easily accessible and easy to use interfaces that include a front panel keypad, and I/O and communications connections. The keypad allows a user to interact with the meter without requiring a breach to a security seal. For example, the user may need to access a central processing unit (CPU) of the revenue meter to program the meter, to retrieve revenue data, and to retrieve power quality data. In addition, the interface provides an external I/O and communication interface that is expandable and not limited to the number of conductors leaving the revenue meter. Moreover, connection to, and detachment from, the interface is simplified through the use of a single cable protruding from the revenue meter to create the connection.
The disclosed embodiments relate to revenue accurate electrical meters, including revenue meters with highly accurate and detailed power quality event detection, monitoring and quantification. It will be recognized by those skilled in the art that, although preferred, the highly accurate and detailed power quality event detection, monitoring and quantification are not necessary for the disclosed embodiments. Herein, the phrase “coupled with” is defined to mean directly coupled with or indirectly coupled with through one or more intermediate components.
Revenue meters must comply with American National Standards Institute's (ANSI) Standards for electric meters which include, but are not limited to, the following:
ANSI C12.1 (1995): American National Standard for Electric Meters-Code for Electricity Metering
ANSI C12.10 (1987): American National Standard for Electromechanical Watthour Meters
ANSI C12.13 (1991): American National Standard for Electronic Time of Use Registers for Electricity Meters
ANSI C12.16 (1991): American National Standard for Solid-State Electricity Meters
ANSI C12.20 (1998): American National Standard for Electricity Meters 0.2 and 0.5 Accuracy Classes
All of which are known in the art and are herein incorporated by reference.
Other specification/standards which apply to revenue meters include ISO Specification MTR1-96, “Engineering Specification for Polyphase Solid State Electricity Meters for Use on the ISO Grid,” herein incorporated by reference.
Referring to the drawings, and particularly
Referring to
S-base meters include a cover 24 which encloses the meter's electronics 26 and display 28. A sealing mechanism 30 secures the cover 24 to prevent unauthorized access to the meter electronics 26. Removal of the meter necessitates disengaging a t-seal (not shown) that seals the cover 24 and the revenue meter 20, which would indicate unauthorized tampering. A context adaptable input device, such as a keypad 32, is provided on a top portion 33 of the cover to allow access to the meter's electronics without requiring removal of the cover 24, described below. Artisans will appreciate that the keypad 32 can be replaced with other input devices, such as a touch screen, a mouse, a track ball, a light pen, a membrane switch, or other similar devices.
Referring now to
Referring to
The transparent meter cover 24 permits the viewing of the meter display 28 without having to remove the meter cover 24. Further, the meter cover 24 may also provide mechanisms for interacting with the meter 20 with the meter cover 24 in place. Such mechanisms include scroll buttons, reset switches or other input devices, and optical couplers, infrared emitters or other output devices as described in more detail below. All of these mechanisms are able to function with the meter cover 24 in place as specified in the ANSI standards. The meter cover 24 is held in place by the sealing mechanism 30 which locks the cover 24 to the meter and indicates when there has been unauthorized tampering with the cover. Typically, the sealing mechanism 30 also serves to lock the meter to the electrical circuit connection. As shown in
As shown in
Preferably, the meter also includes a demand reset switch seal for the demand reset button 99 located on the front panel of the meter 20. This seal may comprise, for example, a wire seal or lock inserted through the side of the button 99. The demand reset button 99 clears all the basic maximum demand measurement accumulators, such as kW, kVAR, and kVA measurements or may reset peak demand measurements or other functions as defined by the operator. Additional measurements can also be configured to be reset by activation of the reset button 99.
Referring to
Referring to
Referring also to
The keypad 32 presents information (i.e., the state of the input hardware such as buttons) or messages to a microprocessor, microcontroller or other central control device via the GUI, which in turn performs actions depending on the type of input and the current operating mode of the revenue meter 20, 34, 42. The GUI and a description of the operating modes is discussed below.
As used herein, the term A/D converter refers not only to a traditional A/D converter but also to a Time Division Multiplexing (“TDM”) based converter, or other converter which converts analog signals to digital signals. TDM is a method of measuring instantaneous power over a wide range of input voltages. TDM is accomplished by taking a snapshot of the waveform of the incoming electrical signal and converting it to a square wave over time using a known algorithm. The area of this square wave is then proportional to the power at the time the snapshot was acquired. The snapshot or sample time is dependent on processor speed. An exemplary implementation of TDM is the Quad4-Plus Electric Meter manufactured by Process Systems, A division of Siemens Power and Transmission & Distribution, LLC, located in Raleigh, N.C. which is described in the CD ROM specification for this product.
The digital output of the analog to digital converter 256 is connected to a digital signal processor 258. The digital signal processor (DSP) 258 is connected to memory 260 and to a microprocessor or CPU 262. The DSP 258 in conjunction with the CPU 262 executes the power quality event detection and reporting algorithms. The CPU 262 is also connected to a user interface 32 which allows users to program the meter or retrieve revenue or power quality data and generally interact with the meter as described in more detail below. It will be appreciated by those skilled in the art that the power quality detection and reporting algorithms can be executed by a variety of hardware configurations, all of which are known in the art.
Graphical User Interface
Referring now to
Referring now to
In a preferred embodiment the keypad 32 includes an up arrow button 32a, a down arrow button 32b and an enter button 32c. It will be recognized by those skilled in the art that other suitable buttons may be used. For example, the disclosed embodiments may be implemented using left and right arrow keys, other key arrangements as well as programmable soft keys. The meter 20 is configured to normally scroll through predefined parameters on the screen 28. In one embodiment, to temporarily freeze the automatic scrolling of the display, the user presses either of the arrow buttons 32a, 32b. The user may then manually scroll through the display by using the buttons 32a and 32b. The enter button 32c may be used to toggle between various available modes of the meter 20. The modes may include, for example two display modes—a Norm mode and an Alt mode. The enter button 32c may also be used to view a setup menu.
The Norm and Alt modes show various real-time measurements and meter properties. In the Norm and Alt modes the meter 20 is in a regular state of operation and is accumulating billable quantities. Generally, the meter 20 cannot be configured in these two modes. The only quantities that may be configured in the Norm or Alt modes are the meter communications parameters, such as the communications port, baud rate, protocol, etc. Both the Norm and Alt modes continuously scroll through various display screens.
In the Norm mode the meter 20 displays on display 28 the values of the kWh delivered and the kWh received; the values of kVARh delivered and kVARh received; the values of kVAh delivered and received; the maximum delivered kW and a time stamp of when the peak occurred; the maximum received kW and a timestamp of when the peak occurred; a count of the number of Demand Resets executed as well as a timestamp of the latest Peak Demand Reset; and a test screen where a black screen showing all segments (all pixels on) indicates a properly functioning display.
In the Alt mode the meter 20 displays nameplate information; demand nameplate information; an event log; phasor diagrams; instantaneous voltages' instantaneous current, instantaneous power; instantaneous demand; voltage harmonics; and current harmonics.
The meter 20 also is programmed with a Test mode. The meter 20 may only be configured and calibrated when it is in the Test mode. To enter the Test mode, the user must press a Test mode button 98 that is hidden beneath a plastic outer cover 24 of the meter 20. In order to enter into the Test mode, the user must remove existing anti-tamper sealing (revenue sealing). In the Test mode, all billable qualities cease to accumulate (as long as the meter in Test mode). All configuration changes made in Test mode remain when the meter 20 is put back in either Norm or Alt modes. The Test mode operates in a similar fashion to the other meter modes (Alt and Norm modes) except that in the Test mode the user is allowed to modify the configuration that affects billable quantities. For example, the CT or PT calibration constants can be modified. Also, in Test mode, the meter is programmed to use separate energy accumulation registers. This makes it possible to calibrate the meter without affecting billable quantities.
Alternatively, user input can also be received by the unit via the communications ports: a front panel optical port or various other communications ports including ethernet, RS232, RS485 or other suitable ports. The communication ports or optical port may be used to input time/date communications parameters, such as ethernet IP members, calibration parameters and setup parameters. The input information can be used to show various display screens to the user, presenting the user with the appropriate information on the dot addressable display 28.
User input, measurement parameters from the data acquisition module and internal meter parameters are fed to the operating system running on the central processing unit.
Preferably, the GUI of the revenue meter 20 is programmable. The programmable GUI allows a meter 20 to be customized to a particular application, presenting the user only with information required by the user. The GUI can be programmed using the keypad 32, or other suitable input device, or through one of the communication ports. If a user requires information through the GUI that is presently not available in the revenue meter 20, the GUI can be reprogrammed to provide this information. Preferably, any parameter can be part of any number of display screens and can be shown in different formats, be it numerical, as a bar, through a point on a chart or as an angle or length of a vector. Such a vector diagram is illustrated in
The graphical nature of the user interface allows sophisticated information to be presented to the user. This can include vector diagrams, bar graphs, graphical progress indicators, trend graphs, waveform graphs and histograms.
Referring now to
Another type of graphical display which may be displayed on the screen 28 is illustrated in
Numerical information which may be provided on the screen includes, for example, event log and nameplate displays. These displays may show, for example, textual information organized in a tabular format. The nameplate display shows owner, meter, and power system details. The event log display provides alert of recent, high priority events logged on the meter's data recorder.
Various screens may be provided as preprogrammed screens which include alphanumeric information. For example a screen may provide real-time information that shows various real-time parameters of the power system. This screen may be configured by defining a link to a minimum/maximum (min/max) parameter. Thus, the display would show the min/max values for line-to-line and line-to-neutral voltages, voltage unbalance, phase currents, power values (kVA, kVAR, and kW), frequency and power factor. The screen may also be configured by defining links to the meter's event log and various historical data logs.
Another screen may include energy and demand information showing the real-time sliding window demand for kW, kVA, and kVAR, and the real-time energy values kWh net, kVARh net and kVAh. Peak demand may be displayed on this screen for kW, kVAR and kVA. The screen may also be configured to define a link to a demand profile trend.
Yet another screen may include power quality information showing voltage disturbance and harmonics details. The voltage disturbance display may provide information regarding sag/swell and transient events. The display may show a sequence-of-events log and a set of curves representing the withstand capabilities of computers in terms of the magnitude and duration of the voltage disturbance, known as a CBEMA plot. Preferably in this display a trigger is included for manual waveform recording and control objects are provided for enabling/disabling power quality event recording. The screen preferably also shows harmonics measurement information which provides information regarding total harmonic distortion for each phase of voltage and current. The display may also show harmonics min/max and harmonics trending graphs.
Preferably, a set points display provides set points to monitor kW demand, over current and voltage unbalance levels. The meter preferably announces warnings if any of the values exceed specified upper limits.
Since the meter 20 is completely self contained, this information can be shown without the use of an external display device such as a laptop computer. Preferably, information, which can be accessed through the front panel display screen 28, is also accessible through the meter's communications ports, and therefore may also be displayed on a terminal/computer connected to one of the communication ports.
Preferably, the GUI is programmed using screen templates to provide scaleable fonts and scaleable graphical display objects such as lines, vectors, circles, pie charts, graphs or bar-graphs. This allows for customization of display screens with various numbers of lines, font sizes and graphical objects.
Preferably, a graphical progress indicator 299 is used to show the current time of an interval graphically and in text form on the dot addressable display. The time can be either time to completion or time elapsed. In addition, the graphical progress indicator can also indicate the end of a time interval. This gives the user instant graphical feedback about the status of various processes or completion of time intervals such as demand progress. One implementation of the graphical progress indicator presents the user with a bar that fills up as time goes on and the end of the interval approaches. Once the interval is complete, the bar is completely full and a graphical symbol (for example the text “EOI”) can be superimposed on the bar. At the same time as the bar is shown on the screen, a numeric value for the time remaining or the time elapsed can also be shown on the screen.
Voltage and current phase relationship can be presented to the user as vector diagrams on the dot addressable display 28. A vector is a graphical object that consists of a line whose length is somehow related to the value of a parameter (usually the length is proportional to the value) and is drawn on the dot-addressable display at an angle given by another parameter. The same screen that shows the vector can, if the user so desires, also show the actual text based numeric values corresponding the length and angle of the vector. By showing the vector of the currents and voltages present on the inputs of the revenue meter, the user gets immediate, easy to comprehend, feedback about voltage and current magnitude, and relative phase angles, which in turn provide instant system diagnosis information showing missing phases or phases connected improperly.
The user may also use the keypad 32 or other suitable input devices to navigate through a hierarchic menu system for meter configuration or GUI customization. In the preferred embodiment, the meter 20 is provided with a default set of display screens and hierarchic interface menus, which can be re-programmed through the user interface itself or through the communications ports.
The information to be displayed on the display screen, consists of graphical objects such as scalable text, lines, circles rectangles, charts, etc. For each screen, a template is provided which in turn provides information on how the screen is laid out. Preferably, the template provides information on the appearance and location of the graphical objects.
The hierarchic menu system is activated by some input key combination, for example by holding the enter key for an extended period of time.
The hierarchic menu system can be implemented using a scrollable menu system with a simple up key 32a, down key 32b and enter key 32c, i.e. the three-key interface used to navigate a set of menu choices. The up/down buttons 32a, 32b select the previous/next items in a list. The list is shown as a text list with the current item in the list highlighted in some fashion, either by inverting or changing the colors in some way or surrounding the highlighted item using a rectangle. When the enter input is activated using the enter button 32c, the highlighted input is selected and the appropriate function is performed: either a new menu list is selected, a single item is selected (such as yes/no) or the user is presented with a changeable parameter. If the parameter is numeric, the up and down keys 32a, 32b will increment or decrement it. If the parameter has numerous numeric fields, holding the up or down arrow buttons 32a, 32b will activate the next/previous numeric field. Just pressing the up/down buttons 32a, 32b will then once again increment/decrement the numeric entry. Hitting the enter button 32c will accept the input value and perform the appropriate action, such as checking/asking for the password and/or confirmation.
Preferably, when the meter 20 is in display mode, the up/down buttons 32a, 32b select either the next or previous display screen in a programmable list of display screens. If no direct user input is provided, the meter will automatically proceed to the next display screen after a preset programmable interval.
Other user interface functions can be implemented using various different combinations of the inputs. For example, the contrast change mode can be activated by simultaneously activating the up/down arrow keys 32a, 32b.
The revenue meter 20 of the disclosed embodiments provides several key advantages over prior art revenue meters. The GUI of the disclosed embodiments provides a method to present the user with information not available on traditional meters. The user interface is self-contained in the socket based revenue meter.
In a preferred embodiment the keypad 32 includes an up arrow button 52a a down arrow button 52b and the enter button 53. It will be recognized by those skilled in the art that other suitable buttons may be used. For example, the disclosed embodiments may be implemented using left and right arrow keys, other key arrangements as well as programmable soft keys. The revenue meter 20, 34, 42 is configured to normally scroll through predefined parameters on the screen 28. In one embodiment, to temporarily freeze the automatic scrolling of the display, the user presses either of the arrow buttons 52a, 52b. The user may then manually scroll through the display by using the buttons 52a and 52b. The enter button 53 may be used to toggle between various available modes of the revenue meter 20, 34, 42. The modes may include, for example, two display modes—a Norm mode and an Alt mode. The enter button 53 may also be used to view a setup menu.
In addition, the GUI is programmable to allow the revenue meter 20, 34, 42 to be customized via the keypad 32 to a particular application, presenting the user only with information required by the user. The GUI can be programmed using the keypad 32, or other suitable input device, or through one of the communication ports, described below.
In addition, the user may also use the keypad 32 or other suitable input device to navigate through a hierarchic menu system for meter configuration or GUI 199 customization. In the preferred embodiment, the meter 20, 34, 42 is provided with a default set of display screens and hierarchic interface menus, which can be re-programmed through the user interface itself or through the communications ports. The information to be displayed on the display screen, consists of graphical objects such as scalable text 198, lines 197, circles 196, rectangles 195, charts 194, etc. For each screen, a template is provided which in turn provides information on how the screen is laid out. Preferably, the template provides information on the appearance and location of the graphical objects.
The hierarchic menu system is activated by some input key combination, for example by holding the enter button 53 for an extended period of time. The hierarchic menu system can be implemented using a scrollable menu system with a simple up key 52a, down key 52b and enter button 53, i.e. the three-key interface used to navigate a set of menu choices. The up/down buttons 52a, 52b select the previous/next items in a list. The list is shown as a text list with the current item in the list highlighted in some fashion, either by inverting or changing the colors in some way or surrounding the highlighted item using a rectangle. When the enter input is activated using the enter button 53, the highlighted input is selected and the appropriate function is performed: either a new menu list is selected, a single item is selected (such as yes/no) or the user is presented with a changeable parameter. If the parameter is numeric, the up and down keys 52a, 52b will increment it. If the parameter has numerous numeric fields, holding the up or down arrow buttons 52a, 52b will activate the next/previous numeric field. Just pressing the up/down buttons 52a, 52b will then once again increment/decrement the numeric entry. Hitting the enter button 53 will accept the input value and perform the appropriate action, such as checking/asking for the password and/or confirmation.
Preferably, when the revenue meter 20, 34, 42 is in display mode, the up/down buttons 52a, 52b select either the next or previous display screen in a programmable list of display screens. If no direct user input is provided, the meter will automatically proceed to the next display screen after a preset programmable interval.
Other user interface functions can be implemented using various different combinations of the inputs. For example, the contrast change mode can be activated by simultaneously activating the up/down arrow keys 52a, 52b.
Referring to FIGS. 4B and 5A–5C, to provide a watertight interface between the keypad 32 and the cover 24, a backside of the top portion 33 of the cover 24 includes sealing walls 58. Infrared light pipes 59 are also included on the backside of the top portion 33 of the cover 24. As described, the keypad 32 of the revenue meter 20, 34, 42 utilizes an elastomer keypad. The sealing walls 58 sealingly engage the elastomer keypad 32. The keypad 32 includes at least one button, e.g., scroll buttons 52, with a plunger 64, and a web 66 portion which allows the plunger to move in a direction generally perpendicular to the keypad 32.
To protectively seal the revenue meter 20, 34, 42 from outside elements, such as rain, a compression plate 68 compresses the elastomer keypad 32 to the sealing walls 58. The compression plate 68 preferably is screwed to the cover 24 via bosses 70. It can be appreciated, however, that other fasteners, such as rivets and snap features within the plastic, can be used to attach the compression plate 68 to the cover 24. The sealing walls 58 and the compression plate 68 compress the keypad 32 to form a seal around each key 52 on the keypad 32. The sealing bosses 70 pass through corresponding holes 71 in the keypad 32 (seen best in
Referring to
When the user depresses keys 52, the web 66 (shown best in
For the keypad 32 to properly function, the keys 52 and the demand reset button 99 must properly align to the intermediate actuators 72 of the bezel 78. In addition, infrared emitters (not shown) located within the infrared locating member 54 must align to the infrared light pipes 59. Referring to
Referring to
Referring to
Referring to
In a preferred embodiment, analog and digital signals are transported via a serial link bus terminating in a twenty-four pin connector. Artisans will appreciate that the cable 93 can include a copper or fiber optic interface, or the equivalent, and that pin connectors of differing sizes can be used. Moreover, the I/O and communications device 88 includes alternate connectors 94 to accommodate other connection to the revenue meter, such as a modem and ethernet connections, e.g., RS 232 and RS 485 connections.
The interface link 92 allows for simplified connection of the revenue meter 20, 34, 42 to the I/O and communications device 88. Labeled connectors 90, 94 on the I/O and communications device allow for easy wiring. Plugability of the I/O and communications device to the socket based revenue meter 20, 34, 42 greatly simplifies servicing and replacing of the meter. The meter is removed without having to unscrew or unclamp any communications and I/O connections. In addition, the I/O and communication device 88 eliminates the necessity of locating individual conductors out of a bundle of wires. Connector 90 on the I/O and communication device 88 allows the installer to plug the interface link 92 into the I/O communication device 88 to hook up all wires to the desired I/O and communications ports at once.
In a preferred embodiment, a dedicated microprocessor 95 located inside the I/O and communication device 88 processes I/O and communication data and passes the data to and from the revenue meter 20, 34, 42 via the interface link 92. The interface link 92 connects to the microprocessor via known circuitry. The microprocessor 95 helps to reduce the load on the meter's processor. In addition, the microprocessor 95 allows for I/O and communications that are expandable and not limited to the number of conductors leaving the revenue meter. An exemplary microprocessor is model number PIC16C67 which is manufactured by Microchip Technology, located in Chandler, Ariz. Of course, other microprocessors can be used.
Data flow between the revenue meter 20, 34, 42 and the I/O and communications device 88 is controlled with data packets. Known techniques, such as RS 422, are used to serially send and receive the data packets to the revenue meter 20, 34, 42. In a preferred embodiment, the speed of the interface is 625 kilobits per second (kbps), but other rates are possible. The following description shows exemplary packets that are utilized to transmit between the revenue meter 20, 34, 42 and the external I/O and communications device 88. For the sake of simplicity, the packet transmission is described with reference to only one external I/O and communications device 88. It should be appreciated, however, that the protocol described herein supports one or more external I/O and communications devices 88.
Packets
The first external I/O and communications device 88 is the master on the bus, and thus initiates all data transfers. In a preferred embodiment, the interface is full-duplex, therefore data flows in both directions at once. The I/O and communications device 88 reports its input states while the revenue meter 20 transmits output states. Preferably, all data packets are error checked using a cyclic redundancy check. If a transmission error is detected, no retry is attempted, the packet is ignored and the states are updated on the next transaction.
Preferably, all packets are fixed length, therefore, the processor receiving the packet always knows where the end of the packet should be. In the following packet descriptions, an ‘x’ indicates four bits, for example, that are set to indicate a value in the corresponding packet. Artisans will appreciate that the number of bits per packet can be increased to produce a nearly infinite combination of packet values.
Input Packet Structure
In a preferred embodiment, an input packet is transmitted from the I/O and communications device 88 to the revenue meter 20. The packet indicates the state of the various inputs within the I/O and communications device 88.
Output Packet Structure
In a preferred embodiment, an output packet is transmitted from the revenue meter 20. The output packet contains the output state that the meter wants to appear on the revenue meter's outputs.
Config Packet Structure
The revenue meter 20 is able to power cycle the master external I/O device. When the master I/O and communications device 88 first powers up, it is responsible for transmitting the CONFIG packet for the master and any attached slave I/O and communications devices. The master I/O and communications device must continue transmitting the CONFIG packet(s) until each CONFIG packet is acknowledged.
Module#—The external I/O and communications device number that contains the configuration (XX). Based on the packet structure, up to 256 devices are possible. ‘y’ indicates whether the I/O and communications device is present. For example, present=1 and absent=0. Absent packets are only transmitted when the I/O and communications device is removed from a powered system. Since the I/O and communications device 88 cannot initiate the transmission of a CONFIG packet when power is removed, the revenue meter is responsible for detecting that the master I/O and communications device is removed.
Type X—16 bits indicating the type of input or output of a particular port on the I/O and communications device 88. For example:
CRC—The packet CRC.
ConfigAck Packet Structure
A CONFIGACK packet is used by the revenue meter to acknowledge that the CONFIG packet has been received. The master I/O and communications device transmits the CONFIG packet at least twice for each I/O and communications device present in order to receive an acknowledgement since the revenue meter cannot initiate a transfer and data is received from the meter while it is being transmitted by the I/O and communications device.
Flow Diagram
Referring to
Referring also to
Referring to
Moreover, the routine initializes a free running counter (block 104) and a periodic interrupt (block 106). In a preferred embodiment, an interrupt interrupts the microprocessor 95 every 819.2 microseconds, although other rates are possible. When the periodic interrupt occurs, a main routine is interrupted and execution continues in a periodic interrupt subroutine (block 108). After the occurrence of a periodic interrupt, the microprocessor 95 reads all digital input ports (block 110) and checks the input ports against the their state during the previous execution of the periodic interrupt subroutine (block 112). Each input is checked, and if an input has changed, a timestamp is recorded, e.g., a current value of a free running counter is stored in a corresponding location in the transmit buffer for that input (block 114).
It is desirable to timestamp the transition time of an input on the external I/O device 88 based on the time in the revenue meter 20, 34, 42 since the microprocessors in the revenue meter and external I/O and communications device are not time synchronized. The external I/O and communications device 88 preferably scans inputs every 819.2 microseconds. When the I/O and communications device 88 sees a transition on an input, it stores the free running counter in the input packet. This free running counter ideally increments every 3.2 microseconds. When the external I/O device is transmitting the input packet to the meter, just before transmitting the last four bytes of the packet, for example, it inserts the current free running counter into the 3rd and 4th last bytes. This ensures that the free running counter value inserted into the packet is as close as possible to the value it would be at the end of packet transmission. When the revenue meter 20, 34, 42 receives the packet, it calculates the time of transition of any of the inputs with the following formula:
tt=tn−(fpck−ftr+finh)*FT
where:
tt=the time of transition.
tn=the time on the meter at the time the packet is received.
fpck=the free running counter at the time the packet is transmitted.
ftr=the free running counter value when the input was scanned and seen to have transitioned.
finh=the inherent typical number of free running counts from the time that the fpck is recorded on the I/O and communications device and the packet is received on the revenue meter.
FT=the conversion factor between free running counts and normal time, e.g., 3.2 microseconds/count.
Therefore, the only variability left in the calculation of transition time is the variability of finh and the accuracy that the revenue meter can timestamp the communications bus receive interrupt.
After the timestamp information is recorded, an appropriate mask bit is set in the transmit buffer indicating that the input has changed (block 116). These values are transferred for processing by the revenue meter 20, 34, 42. Thereafter, or if the input had not changed, execution of the periodic interrupt service routine terminates (block 118).
Referring to
The I/O and communications device 88 waits approximately 10 milliseconds (block 130). This delay, coupled with the time to execute the remaining blocks in the main routine, ensures that the I/O and communications device 88 transmits and receives a packet to and from the revenue meter 20, 34, 42 approximately every 13 milliseconds. While other rates are possible, this rate ensures quick update without overloading the meter. The use of the 13 millisecond delay may be varied depending on a processing power of the revenue meter 20, 34, 42, and how often input states are likely to change. The delay is utilized to reduce the flow of data packets that the revenue meter 20, 34, 42 is required to process.
A first input data packet buffer and a second input data packet buffer are swapped to ensure that the main routine is transmitting input states from the first buffer while the periodic interrupt routine stores input states in the second buffer (block 132). When the revenue meter's microprocessor receives a packet, it executes a bus interrupt service subroutine (block 132a). This bus interrupt service subroutine swaps the input packet buffers (block 132b) so that the next data received does not overwrite the current data before being processed. The bus interrupt service routine then notifies the main routine (block 146) that a packet has been received (block 132c) and prepares to receive the next packet (block 132d). Thereafter, the bus interrupt service routine terminates (block 132e).
Referring to
While the input data packet is being transmitted, an output data packet is being received since the bus is full duplex (block 138). The output data packet's CRC is checked (block 140). If the CRC is valid (block 142), the output ports on the microprocessor 95 are updated (block 144), and another 10 milliseconds elapse before the main routine continues (block 130). Referring also to
Referring to
If no valid CONFIG packet is received within one second, the external I/O and communications device 88 is turned off for a predetermined turn off period (block 152) and then turned back on (block 148). In a preferred embodiment, the predetermined turn off period is five seconds. Of course, the one and five second predetermined times may be modified to suit the situation. The I/O and communication device 88 is power cycled to ensure that the I/O and communications device 88 starts code execution from a known state. Turing the I/O and communications device 88 off for five seconds ensures that the I/O and communications device 88 is in communication with the revenue meter 20, 34, 42 fairly quickly after a user plugs in the I/O and communications device 88.
Once a valid CONFIG packet has been received, the revenue meter 20, 34, 42 fills the outgoing bus transmit buffer with a CONFIGACK packet (block 154). The CONFIGACK packet is transmitted to the external I/O and communications device 88 when the next packet is received from the external I/O and communications device 88. Thereafter, the revenue meter 20, 34, 48 waits for a valid receive/transmit packet operation to complete or for timeout to occur (block 156). In a preferred embodiment, the a duration of the timeout is 50 milliseconds. If a 50 millisecond timeout occurs, the I/O and communications device 88 is either faulty or has been removed since the I/O and communications device 88 transmits packets approximately every 13 milliseconds.
If the timeout occurs, execution continues as though the I/O and communications device 88 is absent (block 152). If a packet is received, the output states are copied from the revenue meter 20, 34, 42 into the bus transmit buffer for transmission the next time the I/O and communications device 88 initiates a packet transaction (block 158). An output state changes when, for example, a user uses the keypad 32 described above to change a fan state from on to off, and off to on, and a set point module overrange can be triggered within the revenue meter 20, 34, 42 to shut down a load. As the microprocessor 95 receives data packets containing the output states, the data packets are processed to acquire the output state information, and the output states are set (block 144). The output state is utilized by relay hardware, for example, to turn a load on or off.
Thereafter, the revenue meter 20, 34, 48 checks the received packet mask for inputs that have changed since the last transaction (block 160). For each input that has changed state, the meter calculates the transition time (block 162), as described above. In either case, the revenue meter 20, 34, 42 reports the input states and transition times to an upper layer of the code responsible for reporting input states to structures which are internally utilized or reported to the user (block 164), and waits for the next packet (block 156).
From the foregoing description, it should be understood that improved revenue meter interfaces have been shown and described which have many desirable attributes and advantages. The revenue meter of the disclosed embodiments provides easily accessible and easy to use interfaces that include a front panel keypad, interactive display, and I/O and communications connections. The keypad allows a user to interact with the meter without requiring a breach to a security seal. In addition, the interface provides an external I/O and communications interface that is expandable and not limited to the number of conductors leaving the revenue meter.
It is to be understood that changes and modifications to the embodiments described above will be apparent to those skilled in the art, and are contemplated. It is therefore intended that the foregoing detailed description be regarded as illustrative rather than limiting, and that it be understood that it is the following claims, including all equivalents, that are intended to define the spirit and scope of this invention.
This application is a continuation of U.S. patent application Ser. No. 09/370,696 filed Aug. 9, 1999, now U.S. Pat. No. 6,825,776 entitled “External I/O and Communications Interface for a Revenue Meter” the entire disclosure of which including the appendices is hereby incorporated by reference. U.S. patent application Ser. No. 09/370,696 incorporated by reference the following U.S. patent applications which were filed on same date as that Application, and which are also hereby incorporated by reference: U.S. patent application Ser. No. 09/370,317, “REVENUE METER WITH POWER QUALITY FEATURES”, filed Aug. 9, 1999, now U.S. Pat. No. 6,615,147. U.S. patent application Ser. No. 09/371,883, “A-BASE REVENUE METER WITH POWER QUALITY FEATURES”, filed Aug. 9, 1999, now U.S. Pat. No. 6,493,644. U.S. patent application Ser. No. 09/370,695, “REVENUE METER WITH GRAPHIC USER INTERFACE”, filed Aug. 9, 1999 (abandoned). U.S. patent application Ser. No. 09/370,686, “REVENUE METER BLADE ASSEMBLY AND METHOD OF ATTACHMENT”, filed Aug. 9, 1999, now U.S. Pat. No. 6,186,842. U.S. patent application Ser. No. 09/370,863, “A POWER SYSTEM TIME SYNCHRONIZATION DEVICE AND METHOD FOR SEQUENCE OF EVENT RECORDING”, filed Aug. 9, 1999, now U.S. Pat. No. 6,611,922. U.S. patent application Ser. No. 09/369,870, “METHOD AND APPARATUS FOR AUTOMATICALLY CONTROLLED GAIN SWITCHING OF POWER MONITORS”, filed Aug. 9, 1999, now U.S. Pat. No. 6,397,155. U.S. patent application Ser. No. 09/370,757, “A KEYPAD FOR A REVENUE METER”, filed Aug. 9, 1999 (pending).
Number | Name | Date | Kind |
---|---|---|---|
4077061 | Johnston et al. | Feb 1978 | A |
4156280 | Griess | May 1979 | A |
4240149 | Fletcher et al. | Dec 1980 | A |
4259746 | Sandstedt | Mar 1981 | A |
4298839 | Johnston | Nov 1981 | A |
4345311 | Fielden | Aug 1982 | A |
4365302 | Elms | Dec 1982 | A |
4388611 | Haferd | Jun 1983 | A |
4455612 | Girgis et al. | Jun 1984 | A |
4459546 | Arrington et al. | Jul 1984 | A |
4463311 | Kobayashi | Jul 1984 | A |
RE31774 | Fletcher et al. | Dec 1984 | E |
4542469 | Brandyberry et al. | Sep 1985 | A |
4568934 | Allgood | Feb 1986 | A |
4612617 | Laplace, Jr. et al. | Sep 1986 | A |
4642564 | Hurley | Feb 1987 | A |
4663587 | Mackenzie | May 1987 | A |
4672555 | Hart et al. | Jun 1987 | A |
4715000 | Premerlani | Dec 1987 | A |
4783748 | Swarztrauber et al. | Nov 1988 | A |
4794369 | Haferd | Dec 1988 | A |
4837504 | Baer et al. | Jun 1989 | A |
4839819 | Begin et al. | Jun 1989 | A |
4843311 | Rozman et al. | Jun 1989 | A |
4878142 | Bergman et al. | Oct 1989 | A |
4878185 | Brand et al. | Oct 1989 | A |
4884021 | Hammond et al. | Nov 1989 | A |
4901221 | Kodosky et al. | Feb 1990 | A |
4914568 | Kodosky et al. | Apr 1990 | A |
4959607 | Coryea et al. | Sep 1990 | A |
4979122 | Davis et al. | Dec 1990 | A |
5017860 | Germer et al. | May 1991 | A |
5059896 | Germer et al. | Oct 1991 | A |
5061890 | Langini | Oct 1991 | A |
5081413 | Yamada et al. | Jan 1992 | A |
5122735 | Porter et al. | Jun 1992 | A |
5132610 | Ying-Chang | Jul 1992 | A |
5151866 | Glaser et al. | Sep 1992 | A |
5155836 | Jordan et al. | Oct 1992 | A |
5207595 | Learmont et al. | May 1993 | A |
5212441 | McEachern et al. | May 1993 | A |
5224011 | Yalla et al. | Jun 1993 | A |
5224054 | Wallis | Jun 1993 | A |
5233538 | Wallis | Aug 1993 | A |
5243536 | Bradford | Sep 1993 | A |
5243537 | Neumann | Sep 1993 | A |
5245275 | Germer et al. | Sep 1993 | A |
5247454 | Farrington et al. | Sep 1993 | A |
5258704 | Germer et al. | Nov 1993 | A |
5262715 | King et al. | Nov 1993 | A |
5270640 | Kohler et al. | Dec 1993 | A |
5301121 | Garverich et al. | Apr 1994 | A |
5391983 | Lusigman et al. | Feb 1995 | A |
5414812 | Filip et al. | May 1995 | A |
5426780 | Gerull et al. | Jun 1995 | A |
5481700 | Thuraisingham | Jan 1996 | A |
5498956 | Kinney et al. | Mar 1996 | A |
5514959 | Horan et al. | May 1996 | A |
5537029 | Hemminger et al. | Jul 1996 | A |
5548527 | Hemminger et al. | Aug 1996 | A |
5549089 | Snell et al. | Aug 1996 | A |
5555508 | Munday et al. | Sep 1996 | A |
5627759 | Bearden et al. | May 1997 | A |
5631843 | Munday et al. | May 1997 | A |
5650936 | Loucks et al. | Jul 1997 | A |
5736847 | Van Doorn et al. | Apr 1998 | A |
5745114 | King et al. | Apr 1998 | A |
5828576 | Loucks et al. | Oct 1998 | A |
6000034 | Lightbody et al. | Dec 1999 | A |
6018700 | Edel | Jan 2000 | A |
6124806 | Cunningham et al. | Sep 2000 | A |
6271523 | Weaver et al. | Aug 2001 | B1 |
6429785 | Griffin | Aug 2002 | B1 |
Number | Date | Country |
---|---|---|
WO 0101079 | Jan 2001 | WO |
Number | Date | Country | |
---|---|---|---|
20050017874 A1 | Jan 2005 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 09370696 | Aug 1999 | US |
Child | 10860227 | US |