In the drawings:
For purposes of clarity, the initial discussion will include a basic description of the exemplary device. This will be followed by a presentation of an exemplary embodiment of the device. Finally, how a device would operate in accordance with the principles of the invention will be discussed.
Turning to
PDA 14 may include a universal serial bus (USB) port for connecting to a dongle which enables PDA 14 to monitor and control ZigBeee devices. Although other devices are available, an example of such a dongle is Integration's IA OEM-DAUB1 2400. More specifically, this will allow an operator to send command signals from PDA 14 to control power control switch device 12.
Although PDA 14 and base station 16 are shown, any wireless capable device can be used to control device 12 in cable 10. The term “control unit” will be used to generally refer to these types of devices since they are exemplary platforms for delivering desired functionality and any similar functional platform is also envisioned by the invention. In addition to the above and by no means limiting, a control unit can also be any wireless capable personal computer or a simple Ethernet wireless to wired bridge. Any standard protocol such as intelligent platform management interface (IPMI) or a command line interface (CLI) running on top of transmission control protocol/internet protocol (TCP/IP) is suitable for the purposes of the invention. Moreover, since the connection transport protocol is TCP/IP, access can be done over a standard TCP/IP socket connection running an application with a graphical user interface (GUI). The type of interaction between a control unit and an inventive cable is a client server system.
Power cord or power cable 10 is exemplified by International Electrotechnical Commission (IEC) IEC32 and may have two connectors, male and female, so that it can be used as an extender cable for existing cables and thus enable power management of existing systems. Power cord or cable 10 can come in any length and can have peripheral functions, such as receptacles for connecting light bulbs.
Referring now to
Specifically, MCU 24 can be any off the shelf MCU, e.g., a PIC 8 bit or a 8051 compliant 16 bit processor. As shown in
MCU 24 further includes an analog-to-digital converter (ADC) that has two inputs ADC1 34 and ADC2 36. As illustrated in
One data channel of MCU 24 (not pictured), which can be implemented as a I2C, serial or any other similar architecture, is connected to wireless unit 20.
Wireless unit 20 uses Bluetooth®, ZigBee® or any other standard protocol for wireless communications. Specifically, wireless unit 20 implements the transmission control protocol/internet protocol (TCP/IP) stack and connectivity setup, including address, gateway, access port ID, and other functions. Consequently, MCU 24 only needs to handle the reading of the analog inputs and the switching of the digital output. This results in a minimal requirements set for MCU 24. There are wireless transceiver modules available in the market having the desired wireless access functionality that can be molded into power cable 10. These include, but are not limited to, for example, the Lantronix® WIPort and Chipcon® CC2431.
As shown in
In general, device 12 is initialized with a certain set of requirements and in response to certain events, specific actions are carried out. In both instances, most of these requirement settings and actions are carried out by establishing a wireless connection between the control unit and device 12 and then using a graphical user interface (GUI) on the control unit to set the appropriate requirements or take the appropriate actions. As evidenced by the list below, some actions are triggered automatically and require no further control unit interaction.
With respect to general setup information, the following need to be designated: setting user rights, designating device name and address, and designating recipients for alerts.
With respect to actions, the following actions may be initiated: turning on/off the switch (connect/disconnect), setting voltage/current threshold for automated turn off (soft circuit breaker), setting alert threshold for voltage and current, setting alert target, setting status on default (on or off), setting soft circuit breaker and alert behavior (to act immediately or to act after a time period has elapsed or to be inactive), measuring current (amps), measuring voltage (volts), and measuring power consumption (watts).
As evident from the above, device 12 has the following functions: switch on or off, provide actual current, provide actual voltage, provide actual power consumption, realize a soft circuit breaker and provide root mean square power consumption.
There are three basic processes operating that enable power monitoring and management.
The first process runs essentially on MCU 24. MCU 24 has control over all the in/out signals connected to the circuit shown in
The second process is an interactive process running between MCU 24 and the control unit. The second process includes a process running on the control unit that offers a network server IP interface in the listening mode. In addition, wireless unit 20 acts as network interface hardware for encapsulating the IP packets exchanged between the control unit and MCU 24 into wireless packets for communication over standard wireless protocols such as ZigBee® or Bluetooth®.
The control unit owns client software that triggers certain actions. User interaction on the GUI on the control unit is needed to start one of these actions. Actions may include but are not limited to, “read sensor data”, set switch status”, set MCU internal value (e.g. IP address, . . . ).
Specifically the software on the control unit will start an IP connection to the IP server process of MCU 24 using the wireless OSI layer 1 and layer 2 functionality. Once the TCP/IP connection is established, a command is sent to MCU 24 and a response is created according to the data in the database (in case of a read command) or an action of MCU 24 is triggered (MCU 24 is switching switch 28). A successful action creates a notification back to the control unit which triggers the termination of the connection.
A third process runs in MCU 24 and monitors thresholds set by set commands from the control unit, such as PDA 14. In the event a voltage/current threshold is reached, a pre-defined action is performed. For example, a possible action is switching switch 28 to on or off.
While the foregoing description and drawings represent the preferred embodiments of the present invention, it will be understood that various changes and modifications may be made without departing from the spirit and scope of the present invention.