US20140201109A1 - Energy distribution system and related methods, devices, and systems - Google Patents
Energy distribution system and related methods, devices, and systems Download PDFInfo
- Publication number
- US20140201109A1 US20140201109A1 US13/815,898 US201313815898A US2014201109A1 US 20140201109 A1 US20140201109 A1 US 20140201109A1 US 201313815898 A US201313815898 A US 201313815898A US 2014201109 A1 US2014201109 A1 US 2014201109A1
- Authority
- US
- United States
- Prior art keywords
- power
- node
- solar
- node manager
- energy
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000009826 distribution Methods 0.000 title claims abstract description 35
- 238000000034 method Methods 0.000 title description 29
- 238000004891 communication Methods 0.000 claims description 15
- 230000001413 cellular effect Effects 0.000 claims description 3
- 238000005516 engineering process Methods 0.000 description 30
- 238000009434 installation Methods 0.000 description 29
- 238000003860 storage Methods 0.000 description 25
- 238000012360 testing method Methods 0.000 description 16
- 238000010586 diagram Methods 0.000 description 13
- 238000007726 management method Methods 0.000 description 11
- 230000004044 response Effects 0.000 description 11
- 238000004590 computer program Methods 0.000 description 10
- 238000012423 maintenance Methods 0.000 description 9
- 230000008569 process Effects 0.000 description 9
- 238000012545 processing Methods 0.000 description 9
- 230000006870 function Effects 0.000 description 8
- 238000010248 power generation Methods 0.000 description 8
- 230000008901 benefit Effects 0.000 description 7
- 241000714197 Avian myeloblastosis-associated virus Species 0.000 description 6
- 101150037717 Mavs gene Proteins 0.000 description 6
- 230000009471 action Effects 0.000 description 6
- 230000033001 locomotion Effects 0.000 description 6
- 238000012937 correction Methods 0.000 description 5
- 230000005611 electricity Effects 0.000 description 5
- 238000004519 manufacturing process Methods 0.000 description 5
- 239000002184 metal Substances 0.000 description 5
- 230000010076 replication Effects 0.000 description 5
- 241000196324 Embryophyta Species 0.000 description 4
- 230000005540 biological transmission Effects 0.000 description 4
- 238000003306 harvesting Methods 0.000 description 4
- 230000002776 aggregation Effects 0.000 description 3
- 238000004220 aggregation Methods 0.000 description 3
- 230000006399 behavior Effects 0.000 description 3
- 239000003245 coal Substances 0.000 description 3
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 230000007774 longterm Effects 0.000 description 3
- 238000005259 measurement Methods 0.000 description 3
- 238000012546 transfer Methods 0.000 description 3
- 238000004458 analytical method Methods 0.000 description 2
- 230000033228 biological regulation Effects 0.000 description 2
- 230000001276 controlling effect Effects 0.000 description 2
- 230000000875 corresponding effect Effects 0.000 description 2
- 238000001514 detection method Methods 0.000 description 2
- 239000000446 fuel Substances 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000006855 networking Effects 0.000 description 2
- 230000035515 penetration Effects 0.000 description 2
- 238000001556 precipitation Methods 0.000 description 2
- 230000000644 propagated effect Effects 0.000 description 2
- 238000013515 script Methods 0.000 description 2
- 238000006424 Flood reaction Methods 0.000 description 1
- 241001494496 Leersia Species 0.000 description 1
- 229920006362 Teflon® Polymers 0.000 description 1
- 241000509228 Thalasseus maximus Species 0.000 description 1
- 238000009825 accumulation Methods 0.000 description 1
- 238000004378 air conditioning Methods 0.000 description 1
- 230000003190 augmentative effect Effects 0.000 description 1
- 238000004422 calculation algorithm Methods 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 230000010267 cellular communication Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000006243 chemical reaction Methods 0.000 description 1
- 238000000576 coating method Methods 0.000 description 1
- 238000005094 computer simulation Methods 0.000 description 1
- 230000003750 conditioning effect Effects 0.000 description 1
- 230000002596 correlated effect Effects 0.000 description 1
- 238000013480 data collection Methods 0.000 description 1
- 239000000428 dust Substances 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000005265 energy consumption Methods 0.000 description 1
- 230000004907 flux Effects 0.000 description 1
- 239000002803 fossil fuel Substances 0.000 description 1
- 230000036541 health Effects 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 238000011900 installation process Methods 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 230000007257 malfunction Effects 0.000 description 1
- 239000000463 material Substances 0.000 description 1
- 239000000203 mixture Substances 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 238000010606 normalization Methods 0.000 description 1
- 238000011022 operating instruction Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000005457 optimization Methods 0.000 description 1
- 230000000704 physical effect Effects 0.000 description 1
- 238000013439 planning Methods 0.000 description 1
- 230000000135 prohibitive effect Effects 0.000 description 1
- 238000000275 quality assurance Methods 0.000 description 1
- 230000008439 repair process Effects 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 230000001953 sensory effect Effects 0.000 description 1
- 238000009987 spinning Methods 0.000 description 1
- 239000000758 substrate Substances 0.000 description 1
- 230000008685 targeting Effects 0.000 description 1
- 230000002123 temporal effect Effects 0.000 description 1
- 238000013024 troubleshooting Methods 0.000 description 1
- 239000013598 vector Substances 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
- G05B15/00—Systems controlled by a computer
- G05B15/02—Systems controlled by a computer electric
-
- F—MECHANICAL ENGINEERING; LIGHTING; HEATING; WEAPONS; BLASTING
- F24—HEATING; RANGES; VENTILATING
- F24S—SOLAR HEAT COLLECTORS; SOLAR HEAT SYSTEMS
- F24S30/00—Arrangements for moving or orienting solar heat collector modules
- F24S30/40—Arrangements for moving or orienting solar heat collector modules for rotary movement
- F24S30/45—Arrangements for moving or orienting solar heat collector modules for rotary movement with two rotation axes
- F24S30/452—Vertical primary axis
-
- F—MECHANICAL ENGINEERING; LIGHTING; HEATING; WEAPONS; BLASTING
- F24—HEATING; RANGES; VENTILATING
- F24S—SOLAR HEAT COLLECTORS; SOLAR HEAT SYSTEMS
- F24S50/00—Arrangements for controlling solar heat collectors
- F24S50/20—Arrangements for controlling solar heat collectors for tracking
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05F—SYSTEMS FOR REGULATING ELECTRIC OR MAGNETIC VARIABLES
- G05F1/00—Automatic systems in which deviations of an electric quantity from one or more predetermined values are detected at the output of the system and fed back to a device within the system to restore the detected quantity to its predetermined value or values, i.e. retroactive systems
- G05F1/66—Regulating electric power
- G05F1/67—Regulating electric power to the maximum power available from a generator, e.g. from solar cell
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/02—Marketing; Price estimation or determination; Fundraising
- G06Q30/0283—Price estimation or determination
-
- H—ELECTRICITY
- H02—GENERATION; CONVERSION OR DISTRIBUTION OF ELECTRIC POWER
- H02S—GENERATION OF ELECTRIC POWER BY CONVERSION OF INFRARED RADIATION, VISIBLE LIGHT OR ULTRAVIOLET LIGHT, e.g. USING PHOTOVOLTAIC [PV] MODULES
- H02S20/00—Supporting structures for PV modules
- H02S20/10—Supporting structures directly fixed to the ground
-
- H—ELECTRICITY
- H02—GENERATION; CONVERSION OR DISTRIBUTION OF ELECTRIC POWER
- H02S—GENERATION OF ELECTRIC POWER BY CONVERSION OF INFRARED RADIATION, VISIBLE LIGHT OR ULTRAVIOLET LIGHT, e.g. USING PHOTOVOLTAIC [PV] MODULES
- H02S20/00—Supporting structures for PV modules
- H02S20/30—Supporting structures being movable or adjustable, e.g. for angle adjustment
- H02S20/32—Supporting structures being movable or adjustable, e.g. for angle adjustment specially adapted for solar tracking
-
- F—MECHANICAL ENGINEERING; LIGHTING; HEATING; WEAPONS; BLASTING
- F24—HEATING; RANGES; VENTILATING
- F24S—SOLAR HEAT COLLECTORS; SOLAR HEAT SYSTEMS
- F24S30/00—Arrangements for moving or orienting solar heat collector modules
- F24S2030/10—Special components
- F24S2030/14—Movement guiding means
- F24S2030/145—Tracks
-
- F—MECHANICAL ENGINEERING; LIGHTING; HEATING; WEAPONS; BLASTING
- F24—HEATING; RANGES; VENTILATING
- F24S—SOLAR HEAT COLLECTORS; SOLAR HEAT SYSTEMS
- F24S2201/00—Prediction; Simulation
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02E—REDUCTION OF GREENHOUSE GAS [GHG] EMISSIONS, RELATED TO ENERGY GENERATION, TRANSMISSION OR DISTRIBUTION
- Y02E10/00—Energy generation through renewable energy sources
- Y02E10/40—Solar thermal energy, e.g. solar towers
- Y02E10/47—Mountings or tracking
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02E—REDUCTION OF GREENHOUSE GAS [GHG] EMISSIONS, RELATED TO ENERGY GENERATION, TRANSMISSION OR DISTRIBUTION
- Y02E10/00—Energy generation through renewable energy sources
- Y02E10/50—Photovoltaic [PV] energy
- Y02E10/56—Power conversion systems, e.g. maximum power point trackers
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
- Y10T—TECHNICAL SUBJECTS COVERED BY FORMER US CLASSIFICATION
- Y10T29/00—Metal working
- Y10T29/49—Method of mechanical manufacture
- Y10T29/4935—Heat exchanger or boiler making
- Y10T29/49355—Solar energy device making
Definitions
- the following disclosure relates generally to energy distribution systems.
- Some embodiments are directed to methods for managing information and/or operation of power or communication nodes connected to end-users, distribution grids, and/or power generators.
- a power plant produces energy with a power generator, such as a coal or gas fired generator, a hydro-powered generator, or a nuclear-powered generator. Power is then transmitted to an end user over a transmission grid.
- the transmission grid supplies this power to a local distribution grid which supplies the power to end users via low-voltage transmission lines, substations, distribution circuits, etc.
- a utility company can meter the power at the end-user's premises to determine how much power has been consumed.
- FIG. 1 is a block diagram of a system that includes a node manager configured in accordance with an embodiment of the present technology.
- FIG. 2A is an isometric view of a solar tracker system configured in accordance with an embodiment of the present technology.
- FIG. 2B is a side view of a tracker and a tracker assembly configured in accordance with embodiments of the present technology.
- FIG. 2C is a top plan view of a base configured in accordance with embodiments of the present technology.
- FIG. 2D is a partial backside view of a tracker assembly configured in accordance with an embodiment of the present technology.
- FIG. 2E illustrates a method of assembling the tracker assembly configured in accordance with an embodiment of the present technology.
- FIG. 3A is a block diagram illustrating tracker electronics configured in accordance with an embodiment of the present technology.
- FIG. 3B is a flow diagram illustrating a routine performed by a node manager in accordance with an embodiment of the present technology.
- FIG. 3C is a flow diagram illustrating a routine of a learning process employed by a node manager in accordance with an embodiment of the present technology.
- FIG. 4A is a diagram of an energy network configured in accordance with an embodiment of the present technology.
- FIG. 4B is a network diagram illustrating a cloud-based networked arrangement of node managers configured in accordance with an embodiment of the present technology.
- FIG. 4C is an diagram of a controller center arranged to operate various aspects of a microgrid in accordance with an embodiment of the present technology.
- FIG. 4D is a diagram of a microgrid licensing/investing/purchasing scheme configured in accordance with an embodiment of the present technology.
- FIGS. 5A-E illustrate various example user interfaces that can be used with a node manager in accordance with an embodiment of the present technology.
- FIG. 6 is a flow diagram illustrating an internodal bidding scheme in accordance with an embodiment of the present technology.
- FIG. 7 show various system logs than can be generated by a node manager during a single day of operation of a solar tracker in accordance with an embodiment of the present technology.
- the technology disclosed herein relates to energy systems and, in particular. to a node manager configured to manage information and/or operation of various aspects of an energy distribution system.
- FIG. 1 is an overview block diagram showing the operational relationships of a node manager 10 in accordance with an embodiment of the present technology.
- the node manager 10 is configured to manage information and/or operation at one or more nodes in a power distribution system, such as power distribution nodes (e.g., a substation), end-user user nodes (e.g., a residential, commercial, governmental, or other suitable users), and/or communication nodes (e.g., a server, database, etc.).
- power distribution nodes e.g., a substation
- end-user user nodes e.g., a residential, commercial, governmental, or other suitable users
- communication nodes e.g., a server, database, etc.
- the node manager 10 communicates with or is integrated with one or more nodal equipment 12 (e.g., nodal devices) at or in the vicinity of a node.
- the nodal equipment 12 can include, for example, energy equipment (e.g., a solar array), auxiliary equipment (e.g., a load balancer), and/or network equipment (e.g., a database).
- the node manager 10 operates to receive nodal information 14 .
- the nodal information 14 can include information relevant to a particular node or a number of nodes.
- the resource information can relate to power demand, weather forecasts, and/or the ambient environment in the vicinity of the nodal devices.
- the node manager 10 operates to derive nodal analytics 16 based on the nodal information 14 .
- the node manager 10 can derive the nodal analytics 16 based on various correlations in the nodal information 14 .
- the node manager 10 can correlate power demand with the weather forecast and/or the ambient environment.
- the node manager 10 generates nodal analytics 16 based on various rules. The node manager 10 can use these rules to develop new or modified correlations, rules, and/or other analytics.
- the node manager 10 operates to generate nodal knowledge 18 based on the nodal information 12 and the nodal analytics 16 .
- the nodal knowledge 18 can allow a power utility to predict power demand based on a weather forecast.
- the nodal knowledge 18 can be bought, sold, or licensed according to a variety of transaction models. In other embodiments, the nodal knowledge 18 can be used for auditing purposes.
- the nodal equipment includes devices, apparatuses, systems, etc. that incorporate a node manager.
- Nodal equipment 12 can be located, for example, at a power distribution node (e.g., a substation), an end-user user node (with e.g., a residential, commercial, governmental, etc.), and/or a communication node (e.g., a server, database, etc.).
- the nodal equipment 12 operates independently of a node manager.
- the nodal equipment 12 allows a node manager to handle nodal information, analytics, and/or knowledge.
- the nodal equipment 12 can include energy equipment, auxiliary equipment, and/or network equipment.
- nodal equipment 12 can include other types of equipment, devices, apparatus, etc.
- the nodal equipment 12 can include a mobile phone, a personal computer, and/or a remote controller device that incorporate a node manager.
- Nodal energy equipment generally includes equipment that is configured to supply and/or store energy (e.g., with a bank of batteries, fuel cells, compressed air, etc.).
- Nodal energy equipment can include, for example, conventional generators (e.g., coal, gas-fired, hydro-powered, nuclear, etc.) and/or renewable energy generators (solar, wind, geothermal, hydro-powered, etc.).
- nodal energy equipment can both deliver and store energy.
- an electric or hybrid car can receive and store energy from the grid and provide energy back to the grid to meet peak demand, load balance, etc.
- nodal energy equipment is described in the context of a solar tracker system or equipment 200 (“tracker 200 ”; FIG. 2A ). In other embodiments, however, other types of nodal energy equipment are possible. Further, some aspects of the tracker 200 can be configured to provide other advantages. For example, the mechanical, operational, as well as the other aspects of the tracker 200 can provide certain advantages relevant to equipment for harvesting solar energy generally.
- FIG. 2A is an isometric view of a tracker 200 configured in accordance with an embodiment of the present technology.
- the tracker 200 includes a tracker assembly 203 and tracker electronics 205 (shown schematically) operably coupled to the tracker assembly 203 .
- the tracker assembly 203 includes a base 210 , a rotatable frame 220 , and a pivoting frame 230 suitable to carry a solar panel array 206 (e.g., one or more solar panels of photovoltaic cells).
- a solar panel array 206 e.g., one or more solar panels of photovoltaic cells.
- FIG. 2B is a side view of a tracker 200 and tracker assembly 203 and FIG. 2C is a top plan view of the base 210 configured in accordance with embodiments of the present technology.
- the base 210 can include a track member 212 supported by a plurality of foot plates 214 .
- the track member 212 can be a frame (e.g., metal tubing frame) having a symmetrical (e.g., round, circular, etc.) shape with an outer circumference C 1 .
- the foot plates 214 can, for example, be metal footings configured to support the track member 212 above the ground or other surface and to anchor the tracker 200 to the ground or other surface.
- the foot plates 214 can be secured to the track member 212 around the circumference C 1 of the track member 212 .
- additional support members 216 e.g., angled support bars or straps
- the base 210 can also include a motor 240 (e.g., a slew motor; drawn in phantom) on which a base member 217 can be fixed.
- the motor 240 can be configured with support structures (not shown) and configured to rotationally turn the base member 217 around a Z-axis (e.g., azimuth, FIG. 2A ) with respect to the track member 212 .
- the motor 240 can include a slew motor from Kinematics Manufacturing, Inc., of 21410 N. 15 th Lane, 104, Phoenix, Ariz. 85027.
- the base member 217 includes radially extending arms 218 coupled thereto.
- the radially extending arms 218 can include wheels 219 (drawn in phantom) for engaging and moving along the track member 212 .
- the individual wheels can be attached at a distal end 215 of each arm 218 such that each individual arm 218 has an arm length L 1 that extends between the base member 217 and the track member 212 .
- the wheels can ride on a round tube to minimize friction and minimize dirt/dust accumulation on the track. Minimal surface contact between the wheels and the track allows wheels to cut grass or other plants that grow over the track, negating the need to significantly alter the landscape surrounding the tracker.
- the wheels can be made from a pipe surrounding low friction bearings to minimize the torque on the centralized slewing drive, allowing the use of a smaller, less expensive slewing drive.
- the wheels can also be made from a pipe long enough to still contact the track if any settling or anomalies occur that cause the track to be not perfectly circular.
- the motor 240 can drive rotation (e.g., in either direction around the Z-axis) of the base member 217 (e.g., using a drive shaft; not visible in FIG. 2C ) such that the wheels 219 fixed to the radially extending arms 218 move along the track member 212 .
- the motor 240 and/or drive shaft can include bearings or other friction-reducing members or coatings like Teflon®.
- FIG. 2D is a partial backside view of a tracker assembly 203 configured in accordance with an embodiment of the present technology.
- the tracker assembly 203 also includes a rotatable frame 220 having towers 222 a and 222 b (referred to together as 222 ) coupled to the base 210 (e.g., to the arms 218 ).
- Each tower 222 includes a plurality of frame members 224 interconnected by bars 226 (e.g., such as metal tubing).
- the frame members 224 can be coupled, at one end (e.g., a first end), to the arms 218 of the base 210 .
- the frame members 224 can culminate (e.g., at a second end) at a tower peak 225 a and 225 b where a hinge 228 is provided for pivotally attaching the pivoting frame 230 .
- the rotatable frame 220 can also include the actuator 250 (as best seen in FIG. 2B ), such as a linear actuator) for engaging and moving (e.g., pivoting) the pivoting frame 230 with respect to the rotatable frame 220 and around the X-Y axis ( FIG. 2A ).
- the actuator 250 can be coupled to the rotatable frame 220 and move with respect to the rotatable frame via pins 251 , 252 (only the pin 251 is visible in FIG. 2D ) around which the actuator 250 can pivot (e.g., pivot about 90°).
- the actuator 250 can include a linear actuator from Linak, Inc., of 2200 Stanley Gault Parkway, Louisville, Ky. 40223.
- the pivoting frame 230 can be configured to carry, orient, position, or otherwise hold a solar panel array 206 (e.g., via a unistrut attachment 253 ).
- the solar panel array 206 can comprise a plurality of photovoltaic cells suitable for converting solar energy into electrical energy.
- the solar panel array 206 can include one or more solar panels (e.g., 240 Watt) from SunPower Corporation, of 77 Rio Robles, San Jose, Calif. 95134.
- the pivoting frame 230 can be pivotally coupled to the rotatable frame 220 via the hinges 228 .
- the tracker assembly 203 is configured to utilize the solar panel array 206 to convert solar energy into electrical energy.
- the tracker assembly 203 can receive control signals ( FIG. 2A ) to move, adjust and position the solar panel array 206 in a desired location and orientation for collecting solar energy.
- the rotatable frame 220 is arranged with the base 210 such that actuation of the motor 240 turns or rotates the base member 217 and arms 218 in a manner that translates rotation of the rotatable frame 220 around the Z-axis to position azimuth.
- the actuator 250 receives control signals to position the pivoting frame 230 in a manner that the pivoting frame 230 and the rotatable frame 220 together position zenith.
- the tracker electronics 205 can communicate via the control signals the desired azimuth and zenith angles for positioning (e.g., via the motor 240 and the actuator 250 ) the solar panel array 206 .
- the tracker 200 is able to position the rotating, pivoting tracker assembly 203 and to generate electrical energy corresponding to the relative position of the solar panel array 206 .
- the tracker assembly 203 can transmit the converted electrical energy directly to the tracker electronics 205 . In other embodiments, the tracker assembly 203 may transmit at least a portion the electrical energy to other components of the tracker 200 or to remote components. For example, the tracker assembly 203 may transfer a portion of the electrical energy directly to a bank of batteries (not shown) for reserve power.
- the tracker assembly 203 is configured to receive control signals from the tracker electronics 205 .
- the tracker assembly 203 positions the solar panel array 206 by changing the orientation of the rotatable frame 220 and the pivoting frame 230 via the combination of associated motor(s) (e.g., motor 240 ) and actuator(s) (e.g., actuator 250 ).
- the tracker assembly 203 positions the solar panel array 206 by rotation about a Z-axis (e.g., azimuth) in combination with rotation about an X-Y axis (e.g., in the X-Y plane).
- the tracker assembly 203 sets operational parameters.
- the tracker assembly 203 can enable and/or disable the operation of certain cells in the solar panel array 206 in response to the control signals.
- the tracker assembly 203 is configured to provide status information to the tracker electronics 205 .
- the status information can include, for example, present orientation of the rotatable frame, the pivoting frame 230 , and/or the solar panel array 206 .
- the status information can also include information about the ambient (e.g., of the solar panel array 206 , the output voltage (or current) of the solar panel array 206 (or individual cells therein)), operational aspect of the motor and/or actuator (e.g., encoder position, overheat detection, speed sensors, etc.), and ambient information (e.g., humidity, sunlight, temperature, wind speed, etc.) in the vicinity of the tracker assembly 203 .
- Status information can also relate to the overall status of the tracker, such as whether maintenance is required (e.g., when a motor has malfunctioned, a circuit board needs to be replaced, etc.).
- the base 210 supports stable mounting of the solar panel array 206 in a fail safe manner.
- the tracker 200 can include instructions for detection of imbalances and/or other mechanical issues that would create tipping or other unstable scenarios in conventional trackers. These imbalances and other issues could be addressed rapidly by the tracker assembly 203 by moving the solar panel array (e.g., pivoting frame 230 ) into a stable position (e.g., horizontal position, vertical position, in-line with a wind direction, etc.) in real-time.
- many of the sensors 257 a - 257 e can be located at a sensor box 255 that can be attached at or near the pivoting frame 230 or, in other embodiments, near to the actuator 250 (e.g., linear actuator).
- the actuator 250 e.g., linear actuator
- the sensors 257 can be located at the interior and/or exterior of the sensor box 255 and can include, for example, a heat sensor 257 a (e.g., for detecting a temperature reading at the solar panel array 206 or elsewhere), a light sensor 257 b , an accelerometer 257 c , a compass sensor 257 d (e.g., for detecting tilt azimuth), and a position sensor 257 e (e.g., for detecting pivot zenith).
- Other sensors 257 are contemplated for including in the sensor box 255 . For example, vibration sensors, moisture sensors, clocks, timers, etc. can also be included.
- all of the sensors 257 can be mounted at the same time. Also by positioning the sensor box 255 at or near the solar panel array 206 or, alternatively, near the actuator 250 , the sensors 257 that detect position, velocity, etc. are appropriately positioned to measure the rotating and pivoting motion of the tracker assembly 203 . Similar to the sensor box 255 , the tracker electronics 205 can be located within a common housing or box 258 (e.g., a secure (lockable), weather proof box) that can be mounted at or near the tracker assembly 203 .
- a common housing or box 258 e.g., a secure (lockable), weather proof box
- FIG. 2E illustrates a method 260 of assembling the tracker assembly 203 in accordance with an embodiment of the present technology.
- the method 260 of assembling a tracker assembly 203 includes preparing a deployment site by digging footing holes in the ground, or in other embodiments (e.g., roof top assembly applications), preparing support structures to couple foot plates 214 thereto (block 262 ).
- the deployment site does not need to be level.
- the method 260 can also include assembling and leveling the base 210 at the deployment site (block 264 ).
- Assembly of the base 210 can include, for example, assembling the track member 212 .
- the track member 212 may be provided as 4 arcuate pieces that can be coupled to form a circular track member 212 .
- Assembly of the base 210 can also include attaching a plurality of foot plates 214 to the track member 212 and, in some embodiments, further securing the foot plates to the track member with support members 216 .
- Assembly of the base 210 may further include providing the base member 217 and attaching the plurality of radially extending arms 218 to the base member in a manner where the arms engage the track member with wheels 219 .
- the base 210 can be secured to the deployment site via attachment of the foot plates 214 via poured concrete or mechanical coupling (e.g., bolts, screws, pins, etc.) and leveled.
- the foot plates 214 can be set in the holes in the ground or attached via other retaining structures (bolts, screws, brackets, etc.) in a manner that levels the base 210 regardless of condition of the site.
- the method 260 can continue with assembling the rotatable frame 220 (e.g., assembling the towers 222 , mounting the towers on the base 210 via mechanical coupling (screws, bolts, etc.), attaching the hinges 228 to the towers, etc.) and connecting the motor 240 (e.g., slew motor) to the base 210 for rotating the rotatable frame 220 (block 266 ).
- the method can further include attaching the actuator 250 to the rotatable frame 220 with the pins 251 , 252 (block 268 ) and mounting the pivoting frame 230 to the hinges 228 of the rotatable frame (block 270 ).
- the actuator 250 e.g., a linear actuator
- the actuator 250 is positioned such that the actuator can engage a backside of the pivoting frame 230 to move the pivoting frame around the X-Y axis created by hinge points.
- solar panels can be attached to the pivoting frame 230 in an array.
- solar panels can be attached and carried by the pivoting frame in a 6 ⁇ 6 solar panel array 206 as shown in FIG. 2A .
- Other solar panel array configurations are contemplated.
- the method 260 can also include installing a lockable and/or weatherproof electronics box 258 (e.g., for housing an electronic control module or tracker electronics 205 ) (block 272 ).
- the method 260 can further provide at block 274 assembling one or more wiring harnesses (e.g., having quick connect/disconnect cables) to facilitate electrical connections with the motor 240 , actuator 250 , sensor box 255 , and solar panel array 206 as well as other components, such as an array of batteries (not shown).
- Further assembly and startup steps are also contemplated.
- the method 260 could include completing assembly and installation of the tracker assembly 203 (block 276 ) and initializing a startup calibration protocol (block 278 ).
- the components of the tracker assembly 203 can be sized to meet Occupational Safety and Health Act (OSHA) requirements such that a single person of average size can carry, manipulate and/or otherwise assemble the components of the tracker assembly 203 .
- OSHA Occupational Safety and Health Act
- the method 260 can be performed by one or two persons of average size without the use of a crane or other special equipment to assemble and deploy the tracker assembly 203 .
- Many of the components of the tracker assembly 203 can be off-the-shelf components (e.g., slew motor, linear actuator, fabricated metal components) and could be relatively light-weight to facilitate ease of assembly at a desired site.
- the tracker 200 , the tracker assembly 203 and/or portions thereof may be assembled and distributed as kits.
- the kits can include tracker and/or tracker assembly components and instructions for assembling, installing, and/or initiating use of the tracker assembly 203 .
- the kit may include all metal or other fabricated components for building and assembling the base 210 , the rotatable frame 220 , and pivoting frame 230 (e.g., frame structures, bolts and other coupling devices, motors, electronic components, wiring harness, sensor box, etc.).
- the components can be sized and of suitable materials to meet OSHA requirements so that an individual person of average size can use the kit to assemble the tracker assembly.
- the kit can include assembly instructions (written instructions, video explanations, computer simulations, etc), such as, for example, instructions on how to perform the method 260 described above.
- the kit may also include other instructions, for example, instructions on operation, maintenance and/or repair of the tracker 200 and/or tracker assembly 203 .
- the kit may also include one or more solar panels to mount in the pivoting frame 230 .
- FIG. 3A is a block diagram of the tracker electronics 205 .
- the tracker electronics 205 include a CPU 302 (central processing unit) including at least one programmed processor configured with memory to operate as a node manager 303 .
- the CPU 302 can also include interfaces and other components for communication over a network and/or with other devices (e.g., via a Mod Bus).
- the tracker electronics 205 further include a wireless communication component 305 , controllers 307 , and inverter circuits 308 .
- the wireless communication component 305 can be configured to provide a direct wireless link for the CPU in addition to or in lieu of standard networking capabilities.
- the controllers 307 are configured to communicate control signals to the tracker assembly 203 to control the motor 240 and the actuator 250 .
- the Inverters 308 are configured to receive solar generated electricity and convert the energy into AC form.
- the inverters 308 can supply the DC voltage to first and/or second power line interfaces 310 a , 310 b .
- the inverters 308 can also convert stored energy at a battery bank 312 into AC form.
- the inverters can convert AC power from the grid or microgrid into DC form suitable for charging the batteries at the battery bank 312 and/or for powering at least a portion of the tracker electronics 205 .
- the tracker electronics 205 can be powered by the solar energy collected by the solar panel array 206 .
- the battery bank 312 can be configured to provide power to the grid or the microgrid.
- the tracker electronics 205 are configured to control the tracker assembly 203 and to receive status from the tracker assembly.
- a user can directly control aspects of the tracker 200 .
- the user can directly connect with the CPU 302 (e.g., via a USB link, wireless link, and/or radio link) to, e.g., control the motor 240 and the actuator 250 and/or to receive status from the individual sensors at the sensor box.
- the node manager 303 can be incorporated into the CPU 302 to provide control signals and/or receive status signals. In one aspect of operation, the node manager 303 passively collects information but does not act on the information. That is, the node manager 303 does not operate (i.e., control) the nodal equipment. In another mode of operation, the node manager 303 can at least partially operate the nodal equipment.
- FIG. 3B is a flow diagram illustrating a routine 320 performed by the node manager 303 .
- the routine 320 is performed by a node manager 303 at the CPU 302 of the tracker electronics 205 .
- the node manager 303 can be incorporated at other portions of the tracker electronics 205 , such as at a logic controller.
- the routine 320 can be executed at other types of nodal equipment, including other types of energy′ equipment (auxiliary).
- the routine 320 applies one or more rules that dictate, at least in part, the operation of the node manager 303 .
- these rules can be based on nodal knowledge.
- the rules can give the node manager 303 certain control over the tracker electronics 205 .
- the node manager 303 can be given at least partial control over the motor 240 (to orient azimuth) and/or the actuator 250 (to orient zenith).
- the rule would dictate that the node manager 303 automatically decrease the span range of the pivoting frame in certain wind conditions.
- a first rule may dictate that the node manager 303 disconnect from the main grid when power generation at the grid is unstable (e.g., spikes) beyond a certain threshold of power stability.
- the first rule may be based on a series of test rules and nodal analytics that arrived at this particular threshold.
- a second rule may work in combination with the first rule to dictate when the tracker 200 should connect to the microgrid.
- the second rule could dictate to the node manager 303 to connect the battery bank 312 to the microgrid when the battery is holding a sufficient amount of charge, or to keep the battery bank disconnected until the battery bank has the appropriate amount of charge.
- the rule could be based on nodal knowledge (i.e., nodal knowledge 18 , FIG. 1 )) related to a weather model in response to a rule related to a predicted weather plan.
- the rules can be “birth certificate” rules that set the initial operating behavior of the node manager 303 .
- a birth certificate can be loaded when the tracker 200 is being assembled. When the tracker 200 is operational, the birth certificate can dictate that the node manager 303 self-calibrate the tracker assembly 203 .
- conventional tracker-type devices can be difficult to set up in the field because they can require complicated and time-intensive calibration procedures. For example, installers need to manually align these devices for compass heading and manually level the devices with, e.g., the ground.
- the birth certificate can provide rules that instruct the tracker 200 to find proper compass direction using a GPS sensor.
- the birth certificate can provide a rule that the node manager uses to auto-level the tracker assembly.
- a tracker can be off level if the foot plates are improperly installed or if the ground shifts.
- the birth certificate rule can provide tuning adjustments that compensate for any out of level alignment of the foot plates.
- the birth certificate rule can instruct the motor 240 or the actuator 250 to operate in a way that compensates for out of level alignment.
- the sensors 257 from the sensor box 255 can be used, for example, to detect the position of the sun, GPS location, etc., which could also be useful for initial calibration.
- the routine acquires nodal information 14 ( FIG. 1 ) by sensing, detecting, requesting, or otherwise acquiring nodal information.
- the routine 320 can sense ambient conditions, request information over a network, or be pushed information without a request.
- the nodal information 14 can relate to, for example, ambient conditions (e.g., barometric pressure, humidity, sunlight, wind speed, temperature, etc.), operating conditions (e.g., operational status of sensors, motors, grid signal quality, battery capacity etc.), and/or performance (e.g., array output power, conversion efficiency, etc.).
- the routine 320 can acquire nodal information 14 using, for example, the sensor box 255 , network communications, and/or the wireless or radio network 305 ( FIG. 3A ).
- the routine 320 can time/date stamp and GPS stamp the nodal information 14 .
- the tracker 200 or a remote device can use the nodal information 14 to derive spatial temporal analytics information.
- the nodal information 14 can be utilized in a variety of network configurations, such as cloud networks, local networks, network islanding, etc.
- the routine 320 determines whether to push (e.g., transmit) some or all of the nodal information 14 to at least one other nodal device (e.g., nodal equipment 12 , FIG. 1 ), such as a remote server, a local computer, a maintenance technicians' portable computing device, etc.
- the other nodal devices can use the nodal information 14 to develop analytics that are fed back to the routine 320 (see adjacent flow routine A to B).
- the other nodal devices can use the nodal information 14 to derive nodal analytics/knowledge 16 , 18 .
- the nodal analytics 16 and/or nodal knowledge 18 could be used by a tracker manufacturer to develop birth certificates (see above) for new tracker installations.
- newer trackers 200 could be as “smart” as existing trackers 200 (i.e., by passing on the same knowledge to new trackers).
- a “new” tracker 200 could learn from an “old” tracker that operating at certain motor speeds for a given amount of temperature, humidity, etc., could cause malfunction.
- the routine 320 further determines if it should apply at least a portion of the nodal analytics 16 .
- the routine 320 can delegate more computationally intensive tasks to another nodal device (e.g., to perform processor intensive correlations), but still perform less computationally intensive tasks (e.g., data comparison).
- the routine 320 can have all analytics delegated to another node manager 303 .
- routine 320 processes nodal information 14 according to various nodal analytics 16 .
- An example of such correlations is described below with reference to FIG. 3C .
- the routine 320 develops nodal knowledge 18 based at least in part on the nodal analytics 16 applied at block 327 .
- the routine 320 can decide in a rule making stage whether a particular rule should be tested (or further tested) before it is adopted, whether the rule should be discarded, or whether the rule should be deemed true (e.g., an expert opinion rule that is deemed to be fact or that is based on manual intervention from a user).
- certain nodal information 14 can cause nodal analytics 16 to substantially change a rule.
- the routine 320 determines whether it should grant nodal control to the nodal device.
- the nodal device is passive.
- the nodal device can be suited to gathering data but not controlling the position of the tracker 200 .
- the nodal device could be a consumer device used to gather data for analyzing a user power consumption behavior.
- a transaction could include incentives for users to provide information relating to their consumption behavior. A discounted price for such a unit could be offered in exchange for this information. This information could be useful for creating nodal knowledge 18 , such as consumer power consumption.
- Table 1 provides various other examples of nodal information 14 .
- Wind speed SCADA e.g., data from grid
- Ambient/Planar irradiance unsun Battery charge levels ambient
- Available discharge power Solar cell temperatures
- Signal conditioning Motor currents User demand
- Demand response Tilt/Azimuth User consumption Real time (time stamp)
- Consumer pricing GPS location
- a fundamental problem with incorporating solar energy into existing electrical grids is that the grids must have enough capacity to meet peak demands when aggregate demands are highest.
- a conventional solution is “pure peaker” power plants.
- Conventional solar generation is typically not suitable as a pure peaker because even though its availability is predicable, it cannot be guaranteed.
- Solar generation has low inertia; generation can be online/offline almost instantaneously.
- traditional power plants coal, nuclear
- the demand for ancillary services which is typically over multiple intervals on any given day, occurs when power must be added to or taken off grid in a matter of seconds to regulate voltage or power factor corrections.
- embodiments of energy distribution systems, or autonomous energy networks (AENs) configured in accordance with embodiments of the present technology can provide a complete solution from deployment to management of a fully autonomous distributed power plant.
- the successful realization of an efficient and reliable solar energy source can include:
- the AEN platform can provide an active intelligent “Expert System” presence at the edge of the grid through, e.g., an integrated cellular communications network.
- Each installation can include a computer, such as a Linux based computer, with SCADA (Supervisory Control And Data Acquisition) capabilities and an Expert Systems Inference Engine (ESIE).
- SCADA Supervisory Control And Data Acquisition
- ESIE Expert Systems Inference Engine
- This decision expertise manages the local installation and provides remote access through, e.g., a cellular network connection.
- the AEN's SCADA API Application Program Interface
- the ESIE enhanced supervisory capabilities manage the advanced power harvesting (Learned Energy Ray Normalization, LERN) algorithms for sun positioning for up to 20 solar trackers. Data is gathered, analyzed, and reported to the AEN network for near real-time and historical tracking.
- the ESIE management proactively monitors trending and exception events that are processed at the local site and reported to the AEN.
- Modified ESIE rules are downloaded when new “insight” is generated from the AEN master ESIE processing aggregate data sets of a large number of installations plus third party data bases (real time market pricing, DRM requests, national weather services, solar forecasts, etc.).
- third party data bases real time market pricing, DRM requests, national weather services, solar forecasts, etc.
- SCADA functions can include:
- ESIE functions can include:
- the AEN can include cloud based data and control network connects to each SCAN installation allowing the aggregation of information and services to be near real time, historical, proactive, and predictive.
- Each SCAN computer has the intelligence to perform the tasks demanded for complete autonomous operation if it never connects to the AEN cloud. This can allows for intermittent operations as standalone entities to optimize various network configurations and real world limitations of network performance.
- the cloud there can include a few replication nodes, a number of directory nodes, and a larger number of data nodes. In one implementation, one might run all of these nodes on virtual machines in, e.g., Amazon data centers.
- Directory nodes can manage information and topology about all other nodes and help nodes find one another. Data nodes store data, and replication nodes manage pulling data from less-accessible or slower data nodes (e.g. tracker nodes) and push data to bigger machines with more reliable network connectivity.
- a solar node collects data and then locates the local data node by consulting the directory node.
- the directory node also knows about other directory nodes in the cloud, and can consult them to find data nodes running in the cloud to push data to as well.
- Most of the intelligence about where data should go is handled by the replication nodes in the cloud; the solar node mostly pushes data to whichever is the closest data node according to the directory node.
- the solar nodes In disconnected mode, the solar nodes function as before. However, the directory nodes cannot find the authoritative directory nodes, so they coordinate among themselves and elect a gantry to start a local replication node. This node manages local storage space for the island by prioritizing data so that the remaining storage is balanced between data nodes, and, in the event one needs to discard data, the lowest-priority data is discarded first. Once the network is functioning again, the replicator node coordinates reconnection to the rest of the network, and the queued-up data drains out to the data nodes in the cloud.
- the AEN can also provide other features, such as:
- the knowledge base on the network cloud handles logistics, the installation process, the sales process, and even the permitting process to ensure that there is maximum efficiency, reliability, and minimum cost from sales lead generation to maintenance schedules. This is all exposed to employees and dealers through a graphic interface (see below) that runs on a computer, laptop, tablet or smartphone. Each employee has a certain level of security clearance that allows them to see or not to see certain information on their particular account.
- the SCAN installation can be a complete turnkey solution that provides the site customer an efficient and reliable power source that is remotely managed and is maintained as an evolving intelligent smart grid power generation asset.
- the customer need not have any expertise in power production equipment, networking, or operations and maintenance. All functions are managed by onsite intelligence supported by integrated, offsite management.
- Smart grid capability built into both the onsite SCAN and remote AEN offer the utility the ability to see what is happening at the customer end of the grid network. These features alleviate the problems of blind solar deployments (residential rooftops) that offer no visibility to the grid operator. With the addition of a SCADA API, integration to the utility management software platforms is enabled. This offers real value to the utility by providing and integrated and reliable power source where power is consumed. By solving the PV issues articulated above, the PV penetration problem is minimized allowing solar energy to be an asset rather than a problem to the grid.
- an AEN controller center can be arranged to operate various aspects of a microgrid.
- a microgrid licensing/investing/purchasing scheme can include technology licensees, exchange investors, independent generators, independent dealers/franchisers, power purchase agreement providers (PPA), and a microGrid Energy Independence Exchange. As shown in this scheme, various network fees, service residuals, licensing fees, investments, and dividends can be generated.
- node managers can gather sensor data from onsite sensors with time stamps and serial numbers.
- node managers can further gather third-party data based on the locations and time stamps of the sensor data.
- third-party data may include, but are not limited to, one or more of:
- the node manager can also determine minimum sample size for 99% confidence using:
- the node manager can also employ manual intervention for low correlation coefficient (greater than 0.05, less than 0.95 correlation coefficient based on sufficient sample size):
- TEST rules are then used by the expert systems to find positive correlations, negative correlations, or statistical insignificance.
- the utility grid is affected by a statistically infinite number of stimuli from macro level weather patterns that cause droughts or floods to micro level human activities like sporting events. This makes manual processing important in order to zero in on new rules by expanding the scope of testing when necessary instead of trying to correlate the statistically infinite number of data points caused by grid stimuli. For example, if the grid is experiencing under voltage every weeknight between 5:00 pm and 6:00 pm with a correlation coefficient of 0.80, a TEST rule could be implemented to test this correlation vs. different temperature ranges. This is because under voltage may only occur at high or low temperatures due to air conditioning or heater use.
- the 65 to 80 degrees Fahrenheit temperature range may not experience under voltage, which may be causing the correlation coefficient to be 0.80.
- the correlation coefficient of under voltage to time of day (5:00-6:00 pm) becomes 0.96.
- a new rule is made to charge batteries prior to 5:00 pm only when temperature ranges are lower than 65 or higher than 80 degrees Fahrenheit.
- TEST rules in some embodiments, can be predictions, observations, metrics, or desired outcomes that can be tested against events that occur. Correlations can be made between TEST rules and mined data from sensors and third-party databases. Correlation coefficients of less than 0.05 are determined statistically insignificant and can be ignored.
- FIGS. 5A-5E provide various example user interfaces that can be used with a node manager.
- Table 2, below, shows various examples of application interfaces for access with a node manager.
- Each node provides one or more services and/or products that vary in price based on the supply and demand of those services or products.
- an automated system In order to set an accurate market price for transactions that can happen frequently (e.g., every millisecond), there must be an automated system.
- node managers can be accessed through the nodal access interface where a minimum price can be set for the services or products offered by that particular node.
- Internodal Bidding occurs autonomously for each service or product based on the minimum acceptable value (MAV) for that service or product. For example, this could occur when a third party requests a particular service or product or when the energy network requires a certain service or product to maintain reliability.
- MAV minimum acceptable value
- Internodal Bidding can be similar to the way Google allows users to set a Maximum Cost Per Click (CPC) on certain advertising.
- CPC Maximum Cost Per Click
- users can set parameters for many different outcomes (e.g. maximum exposure of advertisement, lower cost per click, a mixture of exposure and cost considerations, etc.) Those willing to pay the highest CPC have the best chance of winning many bids and ensuring the most exposure. Those trying to save money, run the risk of limited or no advertising exposure.
- Internodal Bidding can occur in a similar fashion, with the exception that nodes are set to provide a service or product for a MINIMUM acceptable value. Suppliers of nodes that are willing to accept a smaller value for their service or product will likely sell more product or service. For example, if a node has a limited supply, suppliers will likely make their money in times of peak demand. If a node has a large supply, suppliers may choose to bid very low in order to sell the most services or products.
- Internodal Bidding has several parameters that can be altered or adapted to allow suppliers associated with nodes to maximize their revenue.
- certain MAV parameters may include setting different MAVs for different times of day, setting different MAVs for different times of year, establishing different MAVs for different services or products, establishing different MAVs for different levels of storage capacity, determining different MAVs for different weather patterns, and/or establishing different MAVs during certain predictable local events (e.g. sports events, festivals, etc.).
- Internodal Bidding can allow for energy products and services to maintain a reliable service while keeping the cost of energy and reliability as low as possible (e.g., much like Google has done for the advertising industry). Furthermore, it also allows the largest energy plants as well as the smallest single energy producer to participate in the energy market.
- Node 150 contains 64 kW of solar panel capacity and 128 kWh of storage.
- the Node's MAV for stored kilowatt hours is 60 cents/kWh. This is a very high price per kWh considering that the local retail price of electricity is 18 cents/kWh.
- the local utility sends out a “spinning reserve” peak demand request for 60 kW of capacity for the next 2 hours.
- Their bid price is 65 cents/kWh because the utility's only other option is to cut service at that particular substation.
- Node 150 rises to the top of the bidding with its 60 cents/kWh bid. Node 150 wins the bid and supplies 120 kWh of capacity for 60 cents/kWh. Node 150 would have received 8 cents per kWh if sold during off-peak times or $9.60. Node 150 would have received 18 cents per kWh if sold at retail or $21.60
- Internodal Bidding allows renewable energy and storage devices to provide the same services supplied today by fossil fuel powered generators and power plants in just milliseconds rather than several minutes, hours, or even days.
- FIG. 6 is flow diagram illustrating an Internodal Bidding scheme 600 in accordance with an embodiment of the present technology.
- the scheme 600 can include setting a MAV through a Nodal Access Interface (block 602 ).
- the scheme 600 can continue at decision block 604 where the scheme 600 can determine if the request is manual. If the request is manual, the scheme 600 can continue to block 606 where it is determined if the request is within bidding parameters (e.g., established parameters, pre-set parameters, etc.). If the request is not manual, the scheme 600 can determine if an automated service is necessary (decision block 605 ). If the automated service is necessary, the scheme 600 can then continue on to block 606 to determine if the request is within bidding parameters. If an automated service is not needed, the scheme 600 can return to block 602 where a MAV is set through the Nodal Access Interface.
- bidding parameters e.g., established parameters, pre-set parameters, etc.
- the scheme 600 can continue to decision block 608 where it is determined if the bid is low enough. If the bid is low enough, the scheme 600 can provide the product or service requested (block 610 ). If the bid exceeds a threshold (e.g., is not low enough), the scheme 600 can return to block 602 to set a MAV through the Nodal Access Interface.
- a threshold e.g., is not low enough
- FIG. 7 show various system logs than can be generated by a node manager during a single day of operation of a solar tracker in accordance with an embodiment of the present technology.
- Table 3, below, shows example setup parameters corresponding to the system logs of FIG. 7 .
- Embodiments of the subject matter and the operations described in this specification can be implemented in digital electronic circuitry, or in computer software, firmware, or hardware, including the structures disclosed in this specification and their structural equivalents, or in combinations of one or more of them.
- Embodiments of the subject matter described in this specification can be implemented as one or more computer programs, i.e., one or more modules of computer program instructions, encoded on computer storage medium for execution by, or to control the operation of, data processing apparatus.
- a computer storage medium can be, or can be included in, a computer-readable storage device, a computer-readable storage substrate, a random or serial access memory array or device, or a combination of one or more of them.
- a computer storage medium is not a propagated signal, a computer storage medium can be a source or destination of computer program instructions encoded in an artificially-generated propagated signal.
- the computer storage medium also can be, or can be included in, one or more separate physical components or media (e.g., multiple CDs, disks, or other storage devices).
- the operations described in this specification can be implemented as operations performed by a data processing apparatus on data stored on one or more computer-readable storage devices or received from other sources.
- the term “programmed processor” encompasses all kinds of apparatus, devices, and machines for processing data, including, by way of example, a computer, a system on a chip (or multiple ones or combinations of the foregoing).
- the apparatus can include special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application-specific integrated circuit).
- the apparatus also can include, in addition to hardware, code that creates an execution environment for the computer program in question, e.g., code that constitutes processor firmware, a protocol stack, a database management system, an operating system, a cross-platform runtime environment, a virtual machine, or a combination of one or more of them.
- the apparatus and execution environment can realize various different computing model infrastructures, such as web services, distributed computing and grid computing infrastructures.
- a computer program (also known as a program, software, software application, script, or code) can be written in any form of programming language, including compiled or interpreted languages, declarative or procedural languages, and it can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, object, or other unit suitable for use in a computing environment.
- a computer program may, but need not, correspond to a file in a file system.
- a program can be stored in a portion of a file that holds other programs or data (e.g., one or more scripts stored in a markup language document), in a single file dedicated to the program in question, or in multiple coordinated files (e.g., files that store one or more modules, sub-programs, or portions of code).
- a computer program can be deployed to be executed on one computer or on multiple computers that are located at one site or distributed across multiple sites and interconnected by a communication network.
- the processes and logic flows described in this specification can be performed by one or more programmable processors executing one or more computer programs to perform actions by operating on input data and generating output.
- tracker electronics, servers, mobile devices, etc. can be implemented as a controller in an auxiliary device.
- the processes and logic flows can also be performed by, and the apparatus can also be implemented as, special purpose logic circuitry, e.g., an FPGA or an ASIC.
- the node manager can be implemented as a controller in an auxiliary device.
- processors suitable for the execution of a computer program include, by way of example, both general and special purpose microprocessors, and any one or more processors of any kind of digital computer. In some embodiments, the processors can be selected according to the type of device.
- a processor will receive instructions and data from a read-only memory or a random access memory or both.
- the essential elements of a computer are a processor for performing actions in accordance with instructions and one or more memory devices for storing instructions and data.
- a computer will also include, or be operatively coupled to receive data from or transfer data to, or both, one or more mass storage devices for storing data, e.g., magnetic, magneto-optical disks, or optical disks.
- mass storage devices for storing data, e.g., magnetic, magneto-optical disks, or optical disks.
- a server can transfer nodal information, nodal analytics, and/or knowledge can be transferred to flash memory.
- a computer need not have such devices.
- a computer can be embedded in another device, e.g., a mobile telephone, a personal digital assistant (PDA), a mobile audio or video player, a game console, a Global Positioning System (GPS) receiver, or a portable storage device (e.g., a universal serial bus (USB) flash drive), to name just a few.
- Devices suitable for storing computer program instructions and data include all forms of non-volatile memory, media and memory devices, including by way of example semiconductor memory devices, e.g., EPROM, EEPROM, and flash memory devices; magnetic disks, e.g., internal hard disks or removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks.
- the processor and the memory can be supplemented by, or incorporated in, special purpose logic circuitry.
- embodiments of the subject matter described in this specification can be implemented on a computer having a display device, e.g., an LCD (liquid crystal display), LED (light emitting diode), or OLED (organic light emitting diode) monitor, for displaying information to the user and a keyboard and a pointing device, e.g., a mouse or a trackball, by which the user can provide input to the computer.
- a display device e.g., an LCD (liquid crystal display), LED (light emitting diode), or OLED (organic light emitting diode) monitor
- a keyboard and a pointing device e.g., a mouse or a trackball
- a touch screen can be used to display information and to receive input from a user.
- a computer can interact with a user by sending documents to and receiving documents from a device that is used by the user; for example, by sending web pages to a web browser on a user's client device in response to requests received from the web browser.
- Embodiments of the subject matter described in this specification can be implemented in a computing system that includes a back-end component, e.g., as a data server, or that includes a middleware component, e.g., an application server, or that includes a front-end component, e.g., a client computer having a graphical user interface or a Web browser through which a user can interact with an implementation of the subject matter described in this specification, or any combination of one or more such back-end, middleware, or front-end components.
- the components of the system can be interconnected by any form or medium of digital data communication, e.g., a communication network.
- Examples of communication networks include a local area network (“LAN”) and a wide area network (“WAN”), an inter-network (e.g., the Internet), and peer-to-peer networks (e.g., ad hoc peer-to-peer networks).
- LAN local area network
- WAN wide area network
- inter-network e.g., the Internet
- peer-to-peer networks e.g., ad hoc peer-to-peer networks.
Abstract
Description
- The present application claims priority to U.S. Provisional Application No. 61/752,922, filed Jan. 15, 2013, which is incorporated herein by reference in its entirety.
- The following disclosure relates generally to energy distribution systems. Some embodiments, for example, are directed to methods for managing information and/or operation of power or communication nodes connected to end-users, distribution grids, and/or power generators.
- In a typical energy distribution system, a power plant produces energy with a power generator, such as a coal or gas fired generator, a hydro-powered generator, or a nuclear-powered generator. Power is then transmitted to an end user over a transmission grid. The transmission grid, in turn, supplies this power to a local distribution grid which supplies the power to end users via low-voltage transmission lines, substations, distribution circuits, etc. A utility company can meter the power at the end-user's premises to determine how much power has been consumed.
- One problem with traditional energy distributions is they employ antiquated transmission and distribution grids. This makes it difficult and cost prohibitive for utility companies to bring new and alternative power generators online, such as wind, solar, geothermal, etc. Another problem with these systems is that they centralize power distribution, which gives utility companies a market monopoly. Thus, many utility companies are reluctant to improve their power distribution infrastructure.
-
FIG. 1 is a block diagram of a system that includes a node manager configured in accordance with an embodiment of the present technology. -
FIG. 2A is an isometric view of a solar tracker system configured in accordance with an embodiment of the present technology. -
FIG. 2B is a side view of a tracker and a tracker assembly configured in accordance with embodiments of the present technology. -
FIG. 2C is a top plan view of a base configured in accordance with embodiments of the present technology. -
FIG. 2D is a partial backside view of a tracker assembly configured in accordance with an embodiment of the present technology. -
FIG. 2E illustrates a method of assembling the tracker assembly configured in accordance with an embodiment of the present technology. -
FIG. 3A is a block diagram illustrating tracker electronics configured in accordance with an embodiment of the present technology. -
FIG. 3B is a flow diagram illustrating a routine performed by a node manager in accordance with an embodiment of the present technology. -
FIG. 3C is a flow diagram illustrating a routine of a learning process employed by a node manager in accordance with an embodiment of the present technology. -
FIG. 4A is a diagram of an energy network configured in accordance with an embodiment of the present technology. -
FIG. 4B is a network diagram illustrating a cloud-based networked arrangement of node managers configured in accordance with an embodiment of the present technology. -
FIG. 4C is an diagram of a controller center arranged to operate various aspects of a microgrid in accordance with an embodiment of the present technology. -
FIG. 4D is a diagram of a microgrid licensing/investing/purchasing scheme configured in accordance with an embodiment of the present technology. -
FIGS. 5A-E illustrate various example user interfaces that can be used with a node manager in accordance with an embodiment of the present technology. -
FIG. 6 is a flow diagram illustrating an internodal bidding scheme in accordance with an embodiment of the present technology. -
FIG. 7 show various system logs than can be generated by a node manager during a single day of operation of a solar tracker in accordance with an embodiment of the present technology. - As described in greater detail below, the technology disclosed herein relates to energy systems and, in particular. to a node manager configured to manage information and/or operation of various aspects of an energy distribution system.
-
FIG. 1 is an overview block diagram showing the operational relationships of anode manager 10 in accordance with an embodiment of the present technology. In general, thenode manager 10 is configured to manage information and/or operation at one or more nodes in a power distribution system, such as power distribution nodes (e.g., a substation), end-user user nodes (e.g., a residential, commercial, governmental, or other suitable users), and/or communication nodes (e.g., a server, database, etc.). - In one aspect, the
node manager 10 communicates with or is integrated with one or more nodal equipment 12 (e.g., nodal devices) at or in the vicinity of a node. As described in greater detail below, thenodal equipment 12 can include, for example, energy equipment (e.g., a solar array), auxiliary equipment (e.g., a load balancer), and/or network equipment (e.g., a database). - In another aspect, the
node manager 10 operates to receivenodal information 14. In one embodiment, thenodal information 14 can include information relevant to a particular node or a number of nodes. For example, the resource information can relate to power demand, weather forecasts, and/or the ambient environment in the vicinity of the nodal devices. - In yet another aspect, the
node manager 10 operates to derivenodal analytics 16 based on thenodal information 14. In one embodiment, thenode manager 10 can derive thenodal analytics 16 based on various correlations in thenodal information 14. For example, thenode manager 10 can correlate power demand with the weather forecast and/or the ambient environment. In some embodiments, thenode manager 10 generatesnodal analytics 16 based on various rules. Thenode manager 10 can use these rules to develop new or modified correlations, rules, and/or other analytics. - In still yet another aspect, the
node manager 10 operates to generatenodal knowledge 18 based on thenodal information 12 and thenodal analytics 16. Thenodal knowledge 18, for example, can allow a power utility to predict power demand based on a weather forecast. In some embodiments, thenodal knowledge 18 can be bought, sold, or licensed according to a variety of transaction models. In other embodiments, thenodal knowledge 18 can be used for auditing purposes. - In general, the nodal equipment includes devices, apparatuses, systems, etc. that incorporate a node manager. Nodal
equipment 12 can be located, for example, at a power distribution node (e.g., a substation), an end-user user node (with e.g., a residential, commercial, governmental, etc.), and/or a communication node (e.g., a server, database, etc.). In some embodiments thenodal equipment 12 operates independently of a node manager. In other embodiments, thenodal equipment 12 allows a node manager to handle nodal information, analytics, and/or knowledge. As described in greater detail below, thenodal equipment 12 can include energy equipment, auxiliary equipment, and/or network equipment. However,nodal equipment 12 can include other types of equipment, devices, apparatus, etc. For example, thenodal equipment 12 can include a mobile phone, a personal computer, and/or a remote controller device that incorporate a node manager. - Nodal energy equipment generally includes equipment that is configured to supply and/or store energy (e.g., with a bank of batteries, fuel cells, compressed air, etc.). Nodal energy equipment can include, for example, conventional generators (e.g., coal, gas-fired, hydro-powered, nuclear, etc.) and/or renewable energy generators (solar, wind, geothermal, hydro-powered, etc.). In some embodiments, nodal energy equipment can both deliver and store energy. For example, in a smart grid, an electric or hybrid car can receive and store energy from the grid and provide energy back to the grid to meet peak demand, load balance, etc.
- As described herein, nodal energy equipment is described in the context of a solar tracker system or equipment 200 (“
tracker 200”;FIG. 2A ). In other embodiments, however, other types of nodal energy equipment are possible. Further, some aspects of thetracker 200 can be configured to provide other advantages. For example, the mechanical, operational, as well as the other aspects of thetracker 200 can provide certain advantages relevant to equipment for harvesting solar energy generally. -
FIG. 2A is an isometric view of atracker 200 configured in accordance with an embodiment of the present technology. Thetracker 200 includes atracker assembly 203 and tracker electronics 205 (shown schematically) operably coupled to thetracker assembly 203. Thetracker assembly 203 includes abase 210, arotatable frame 220, and apivoting frame 230 suitable to carry a solar panel array 206 (e.g., one or more solar panels of photovoltaic cells). Various aspects of thebase 210, therotatable frame 220, the pivotingframe 230 and associated motor(s) and actuator(s) are described in greater detail with reference toFIGS. 2A-2E together. -
FIG. 2B is a side view of atracker 200 andtracker assembly 203 andFIG. 2C is a top plan view of the base 210 configured in accordance with embodiments of the present technology. In reference toFIGS. 2B and 2C together, the base 210 can include atrack member 212 supported by a plurality offoot plates 214. In one embodiment, thetrack member 212 can be a frame (e.g., metal tubing frame) having a symmetrical (e.g., round, circular, etc.) shape with an outer circumference C1. Thefoot plates 214 can, for example, be metal footings configured to support thetrack member 212 above the ground or other surface and to anchor thetracker 200 to the ground or other surface. Thefoot plates 214 can be secured to thetrack member 212 around the circumference C1 of thetrack member 212. In some embodiments, additional support members 216 (e.g., angled support bars or straps) can couple thetrack member 212 to thefoot plates 214. - Referring to
FIG. 2C , the base 210 can also include a motor 240 (e.g., a slew motor; drawn in phantom) on which abase member 217 can be fixed. Themotor 240 can be configured with support structures (not shown) and configured to rotationally turn thebase member 217 around a Z-axis (e.g., azimuth,FIG. 2A ) with respect to thetrack member 212. In one particular embodiment, themotor 240 can include a slew motor from Kinematics Manufacturing, Inc., of 21410 N. 15th Lane, 104, Phoenix, Ariz. 85027. Thebase member 217 includes radially extendingarms 218 coupled thereto. Theradially extending arms 218 can include wheels 219 (drawn in phantom) for engaging and moving along thetrack member 212. For example the individual wheels can be attached at adistal end 215 of eacharm 218 such that eachindividual arm 218 has an arm length L1 that extends between thebase member 217 and thetrack member 212. Also, the wheels can ride on a round tube to minimize friction and minimize dirt/dust accumulation on the track. Minimal surface contact between the wheels and the track allows wheels to cut grass or other plants that grow over the track, negating the need to significantly alter the landscape surrounding the tracker. The wheels can be made from a pipe surrounding low friction bearings to minimize the torque on the centralized slewing drive, allowing the use of a smaller, less expensive slewing drive. The wheels can also be made from a pipe long enough to still contact the track if any settling or anomalies occur that cause the track to be not perfectly circular. - The
motor 240 can drive rotation (e.g., in either direction around the Z-axis) of the base member 217 (e.g., using a drive shaft; not visible inFIG. 2C ) such that thewheels 219 fixed to theradially extending arms 218 move along thetrack member 212. In some embodiments, themotor 240 and/or drive shaft can include bearings or other friction-reducing members or coatings like Teflon®. -
FIG. 2D is a partial backside view of atracker assembly 203 configured in accordance with an embodiment of the present technology. Referring toFIGS. 2B and 2D together, thetracker assembly 203 also includes arotatable frame 220 havingtowers 222 a and 222 b (referred to together as 222) coupled to the base 210 (e.g., to the arms 218). Each tower 222 includes a plurality offrame members 224 interconnected by bars 226 (e.g., such as metal tubing). Theframe members 224 can be coupled, at one end (e.g., a first end), to thearms 218 of thebase 210. Theframe members 224 can culminate (e.g., at a second end) at atower peak hinge 228 is provided for pivotally attaching thepivoting frame 230. Therotatable frame 220 can also include the actuator 250 (as best seen inFIG. 2B ), such as a linear actuator) for engaging and moving (e.g., pivoting) thepivoting frame 230 with respect to therotatable frame 220 and around the X-Y axis (FIG. 2A ). Theactuator 250 can be coupled to therotatable frame 220 and move with respect to the rotatable frame viapins 251, 252 (only thepin 251 is visible inFIG. 2D ) around which theactuator 250 can pivot (e.g., pivot about 90°). In one particular embodiment, theactuator 250 can include a linear actuator from Linak, Inc., of 2200 Stanley Gault Parkway, Louisville, Ky. 40223. - The pivoting
frame 230 can be configured to carry, orient, position, or otherwise hold a solar panel array 206 (e.g., via a unistrut attachment 253). Thesolar panel array 206 can comprise a plurality of photovoltaic cells suitable for converting solar energy into electrical energy. In one particular embodiment, thesolar panel array 206 can include one or more solar panels (e.g., 240 Watt) from SunPower Corporation, of 77 Rio Robles, San Jose, Calif. 95134. As described above, the pivotingframe 230 can be pivotally coupled to therotatable frame 220 via thehinges 228. - In one aspect, the
tracker assembly 203 is configured to utilize thesolar panel array 206 to convert solar energy into electrical energy. During operation, thetracker assembly 203 can receive control signals (FIG. 2A ) to move, adjust and position thesolar panel array 206 in a desired location and orientation for collecting solar energy. For example, therotatable frame 220 is arranged with the base 210 such that actuation of themotor 240 turns or rotates thebase member 217 andarms 218 in a manner that translates rotation of therotatable frame 220 around the Z-axis to position azimuth. Additionally, theactuator 250 receives control signals to position the pivotingframe 230 in a manner that the pivotingframe 230 and therotatable frame 220 together position zenith. For example, thetracker electronics 205 can communicate via the control signals the desired azimuth and zenith angles for positioning (e.g., via themotor 240 and the actuator 250) thesolar panel array 206. As such, thetracker 200 is able to position the rotating, pivotingtracker assembly 203 and to generate electrical energy corresponding to the relative position of thesolar panel array 206. - In some embodiments, the
tracker assembly 203 can transmit the converted electrical energy directly to thetracker electronics 205. In other embodiments, thetracker assembly 203 may transmit at least a portion the electrical energy to other components of thetracker 200 or to remote components. For example, thetracker assembly 203 may transfer a portion of the electrical energy directly to a bank of batteries (not shown) for reserve power. - As described above, the
tracker assembly 203 is configured to receive control signals from thetracker electronics 205. In response to some commands, thetracker assembly 203 positions thesolar panel array 206 by changing the orientation of therotatable frame 220 and thepivoting frame 230 via the combination of associated motor(s) (e.g., motor 240) and actuator(s) (e.g., actuator 250). In the embodiment illustrated inFIGS. 2A-2D , for example, thetracker assembly 203 positions thesolar panel array 206 by rotation about a Z-axis (e.g., azimuth) in combination with rotation about an X-Y axis (e.g., in the X-Y plane). In response to other commands, thetracker assembly 203 sets operational parameters. For example, thetracker assembly 203 can enable and/or disable the operation of certain cells in thesolar panel array 206 in response to the control signals. - In another aspect, the
tracker assembly 203 is configured to provide status information to thetracker electronics 205. The status information can include, for example, present orientation of the rotatable frame, the pivotingframe 230, and/or thesolar panel array 206. The status information can also include information about the ambient (e.g., of thesolar panel array 206, the output voltage (or current) of the solar panel array 206 (or individual cells therein)), operational aspect of the motor and/or actuator (e.g., encoder position, overheat detection, speed sensors, etc.), and ambient information (e.g., humidity, sunlight, temperature, wind speed, etc.) in the vicinity of thetracker assembly 203. Status information can also relate to the overall status of the tracker, such as whether maintenance is required (e.g., when a motor has malfunctioned, a circuit board needs to be replaced, etc.). - Additionally the
base 210 supports stable mounting of thesolar panel array 206 in a fail safe manner. For example, thetracker 200 can include instructions for detection of imbalances and/or other mechanical issues that would create tipping or other unstable scenarios in conventional trackers. These imbalances and other issues could be addressed rapidly by thetracker assembly 203 by moving the solar panel array (e.g., pivoting frame 230) into a stable position (e.g., horizontal position, vertical position, in-line with a wind direction, etc.) in real-time. - In one embodiment, many of the sensors 257 a-257 e (referred to together as 257) can be located at a
sensor box 255 that can be attached at or near the pivotingframe 230 or, in other embodiments, near to the actuator 250 (e.g., linear actuator). The sensors 257 can be located at the interior and/or exterior of thesensor box 255 and can include, for example, aheat sensor 257 a (e.g., for detecting a temperature reading at thesolar panel array 206 or elsewhere), alight sensor 257 b, anaccelerometer 257 c, acompass sensor 257 d (e.g., for detecting tilt azimuth), and aposition sensor 257 e (e.g., for detecting pivot zenith). Other sensors 257 are contemplated for including in thesensor box 255. For example, vibration sensors, moisture sensors, clocks, timers, etc. can also be included. By positioning all of the sensors 257 at a common location (e.g., within a common housing or box 255), all of the sensors 257 and/or other related data collection devices can be mounted at the same time. Also by positioning thesensor box 255 at or near thesolar panel array 206 or, alternatively, near theactuator 250, the sensors 257 that detect position, velocity, etc. are appropriately positioned to measure the rotating and pivoting motion of thetracker assembly 203. Similar to thesensor box 255, thetracker electronics 205 can be located within a common housing or box 258 (e.g., a secure (lockable), weather proof box) that can be mounted at or near thetracker assembly 203. - Other aspects of the present technology are directed to methods of assembling the
tracker assembly 203. In general, methods in accordance with an embodiment of the present technology are suited for quick assembly.FIG. 2E illustrates amethod 260 of assembling thetracker assembly 203 in accordance with an embodiment of the present technology. Themethod 260 of assembling atracker assembly 203 includes preparing a deployment site by digging footing holes in the ground, or in other embodiments (e.g., roof top assembly applications), preparing support structures to couplefoot plates 214 thereto (block 262). In some embodiments, the deployment site does not need to be level. Themethod 260 can also include assembling and leveling the base 210 at the deployment site (block 264). Assembly of the base 210 can include, for example, assembling thetrack member 212. In one embodiment, thetrack member 212 may be provided as 4 arcuate pieces that can be coupled to form acircular track member 212. Assembly of the base 210 can also include attaching a plurality offoot plates 214 to thetrack member 212 and, in some embodiments, further securing the foot plates to the track member withsupport members 216. Assembly of the base 210 may further include providing thebase member 217 and attaching the plurality of radially extendingarms 218 to the base member in a manner where the arms engage the track member withwheels 219. Once assembled, the base 210 can be secured to the deployment site via attachment of thefoot plates 214 via poured concrete or mechanical coupling (e.g., bolts, screws, pins, etc.) and leveled. For example, thefoot plates 214 can be set in the holes in the ground or attached via other retaining structures (bolts, screws, brackets, etc.) in a manner that levels the base 210 regardless of condition of the site. - The
method 260 can continue with assembling the rotatable frame 220 (e.g., assembling the towers 222, mounting the towers on thebase 210 via mechanical coupling (screws, bolts, etc.), attaching thehinges 228 to the towers, etc.) and connecting the motor 240 (e.g., slew motor) to thebase 210 for rotating the rotatable frame 220 (block 266). The method can further include attaching theactuator 250 to therotatable frame 220 with thepins 251, 252 (block 268) and mounting the pivotingframe 230 to thehinges 228 of the rotatable frame (block 270). In operation, the actuator 250 (e.g., a linear actuator) is positioned such that the actuator can engage a backside of the pivotingframe 230 to move the pivoting frame around the X-Y axis created by hinge points. - If not already completed, solar panels can be attached to the
pivoting frame 230 in an array. For example, solar panels can be attached and carried by the pivoting frame in a 6×6solar panel array 206 as shown inFIG. 2A . Other solar panel array configurations are contemplated. Themethod 260 can also include installing a lockable and/or weatherproof electronics box 258 (e.g., for housing an electronic control module or tracker electronics 205) (block 272). Themethod 260 can further provide atblock 274 assembling one or more wiring harnesses (e.g., having quick connect/disconnect cables) to facilitate electrical connections with themotor 240,actuator 250,sensor box 255, andsolar panel array 206 as well as other components, such as an array of batteries (not shown). Further assembly and startup steps are also contemplated. For example, themethod 260 could include completing assembly and installation of the tracker assembly 203 (block 276) and initializing a startup calibration protocol (block 278). - Accordingly, in contrast to conventional trackers that have to have a large center hole dug for deep post installation, installation of the
tracker assembly 203 can be done with minimal equipment (e.g., a wrench, stepladder, etc) and with minimal effort (e.g., an average sized person). In one embodiment the components of thetracker assembly 203 can be sized to meet Occupational Safety and Health Act (OSHA) requirements such that a single person of average size can carry, manipulate and/or otherwise assemble the components of thetracker assembly 203. For example, themethod 260 can be performed by one or two persons of average size without the use of a crane or other special equipment to assemble and deploy thetracker assembly 203. Many of the components of thetracker assembly 203 can be off-the-shelf components (e.g., slew motor, linear actuator, fabricated metal components) and could be relatively light-weight to facilitate ease of assembly at a desired site. - The
tracker 200, thetracker assembly 203 and/or portions thereof may be assembled and distributed as kits. The kits can include tracker and/or tracker assembly components and instructions for assembling, installing, and/or initiating use of thetracker assembly 203. For example, the kit may include all metal or other fabricated components for building and assembling thebase 210, therotatable frame 220, and pivoting frame 230 (e.g., frame structures, bolts and other coupling devices, motors, electronic components, wiring harness, sensor box, etc.). As described above, the components can be sized and of suitable materials to meet OSHA requirements so that an individual person of average size can use the kit to assemble the tracker assembly. Additionally, the kit can include assembly instructions (written instructions, video explanations, computer simulations, etc), such as, for example, instructions on how to perform themethod 260 described above. The kit may also include other instructions, for example, instructions on operation, maintenance and/or repair of thetracker 200 and/ortracker assembly 203. In some instances, the kit may also include one or more solar panels to mount in thepivoting frame 230. -
FIG. 3A is a block diagram of thetracker electronics 205. In the illustrated embodiment thetracker electronics 205 include a CPU 302 (central processing unit) including at least one programmed processor configured with memory to operate as anode manager 303. TheCPU 302 can also include interfaces and other components for communication over a network and/or with other devices (e.g., via a Mod Bus). Thetracker electronics 205 further include awireless communication component 305,controllers 307, andinverter circuits 308. Thewireless communication component 305 can be configured to provide a direct wireless link for the CPU in addition to or in lieu of standard networking capabilities. Thecontrollers 307 are configured to communicate control signals to thetracker assembly 203 to control themotor 240 and theactuator 250. TheInverters 308 are configured to receive solar generated electricity and convert the energy into AC form. Theinverters 308 can supply the DC voltage to first and/or second power line interfaces 310 a, 310 b. Theinverters 308 can also convert stored energy at abattery bank 312 into AC form. In some embodiments, the inverters can convert AC power from the grid or microgrid into DC form suitable for charging the batteries at thebattery bank 312 and/or for powering at least a portion of thetracker electronics 205. In some embodiments, thetracker electronics 205 can be powered by the solar energy collected by thesolar panel array 206. In still other embodiments thebattery bank 312 can be configured to provide power to the grid or the microgrid. - In operation, the
tracker electronics 205 are configured to control thetracker assembly 203 and to receive status from the tracker assembly. In one embodiment, a user can directly control aspects of thetracker 200. For example, the user can directly connect with the CPU 302 (e.g., via a USB link, wireless link, and/or radio link) to, e.g., control themotor 240 and theactuator 250 and/or to receive status from the individual sensors at the sensor box. - In other embodiments, the
node manager 303 can be incorporated into theCPU 302 to provide control signals and/or receive status signals. In one aspect of operation, thenode manager 303 passively collects information but does not act on the information. That is, thenode manager 303 does not operate (i.e., control) the nodal equipment. In another mode of operation, thenode manager 303 can at least partially operate the nodal equipment. -
FIG. 3B is a flow diagram illustrating a routine 320 performed by thenode manager 303. In the illustrated embodiment, the routine 320 is performed by anode manager 303 at theCPU 302 of thetracker electronics 205. In other embodiments, however, thenode manager 303 can be incorporated at other portions of thetracker electronics 205, such as at a logic controller. Further, in other embodiments, the routine 320 can be executed at other types of nodal equipment, including other types of energy′ equipment (auxiliary). - At
block 321, the routine 320 applies one or more rules that dictate, at least in part, the operation of thenode manager 303. As described in greater detail below, these rules can be based on nodal knowledge. In some embodiments, the rules can give thenode manager 303 certain control over thetracker electronics 205. For example, thenode manager 303 can be given at least partial control over the motor 240 (to orient azimuth) and/or the actuator 250 (to orient zenith). In one embodiment, the rule would dictate that thenode manager 303 automatically decrease the span range of the pivoting frame in certain wind conditions. - In another embodiment, a first rule may dictate that the
node manager 303 disconnect from the main grid when power generation at the grid is unstable (e.g., spikes) beyond a certain threshold of power stability. As described in greater detail below, the first rule may be based on a series of test rules and nodal analytics that arrived at this particular threshold. In some embodiments, a second rule may work in combination with the first rule to dictate when thetracker 200 should connect to the microgrid. For example, the second rule could dictate to thenode manager 303 to connect thebattery bank 312 to the microgrid when the battery is holding a sufficient amount of charge, or to keep the battery bank disconnected until the battery bank has the appropriate amount of charge. The rule could be based on nodal knowledge (i.e.,nodal knowledge 18,FIG. 1 )) related to a weather model in response to a rule related to a predicted weather plan. - In some embodiments, the rules can be “birth certificate” rules that set the initial operating behavior of the
node manager 303. In one embodiment, a birth certificate can be loaded when thetracker 200 is being assembled. When thetracker 200 is operational, the birth certificate can dictate that thenode manager 303 self-calibrate thetracker assembly 203. By contrast, conventional tracker-type devices can be difficult to set up in the field because they can require complicated and time-intensive calibration procedures. For example, installers need to manually align these devices for compass heading and manually level the devices with, e.g., the ground. - However, the birth certificate can provide rules that instruct the
tracker 200 to find proper compass direction using a GPS sensor. In another embodiment, the birth certificate can provide a rule that the node manager uses to auto-level the tracker assembly. A tracker can be off level if the foot plates are improperly installed or if the ground shifts. The birth certificate rule can provide tuning adjustments that compensate for any out of level alignment of the foot plates. In particular, the birth certificate rule can instruct themotor 240 or theactuator 250 to operate in a way that compensates for out of level alignment. In another embodiment, the sensors 257 from thesensor box 255 can be used, for example, to detect the position of the sun, GPS location, etc., which could also be useful for initial calibration. - At
block 322, the routine acquires nodal information 14 (FIG. 1 ) by sensing, detecting, requesting, or otherwise acquiring nodal information. For example, the routine 320 can sense ambient conditions, request information over a network, or be pushed information without a request. Thenodal information 14 can relate to, for example, ambient conditions (e.g., barometric pressure, humidity, sunlight, wind speed, temperature, etc.), operating conditions (e.g., operational status of sensors, motors, grid signal quality, battery capacity etc.), and/or performance (e.g., array output power, conversion efficiency, etc.). The routine 320 can acquirenodal information 14 using, for example, thesensor box 255, network communications, and/or the wireless or radio network 305 (FIG. 3A ). - In many embodiments, the routine 320 can time/date stamp and GPS stamp the
nodal information 14. In this way thetracker 200 or a remote device can use thenodal information 14 to derive spatial temporal analytics information. As described in greater detail below with reference toFIGS. 4A-4D , thenodal information 14 can be utilized in a variety of network configurations, such as cloud networks, local networks, network islanding, etc. - At
decision block 323, the routine 320 determines whether to push (e.g., transmit) some or all of thenodal information 14 to at least one other nodal device (e.g.,nodal equipment 12,FIG. 1 ), such as a remote server, a local computer, a maintenance technicians' portable computing device, etc. In some embodiments, the other nodal devices can use thenodal information 14 to develop analytics that are fed back to the routine 320 (see adjacent flow routine A to B). In one embodiment, the other nodal devices can use thenodal information 14 to derive nodal analytics/knowledge nodal analytics 16 and/ornodal knowledge 18 could be used by a tracker manufacturer to develop birth certificates (see above) for new tracker installations. In this way,newer trackers 200 could be as “smart” as existing trackers 200 (i.e., by passing on the same knowledge to new trackers). For example, a “new”tracker 200 could learn from an “old” tracker that operating at certain motor speeds for a given amount of temperature, humidity, etc., could cause malfunction. - At
decision block 325, and if the routine 320 determines that data is to be pushed (block 323), the routine 320 further determines if it should apply at least a portion of thenodal analytics 16. In some embodiments, the routine 320 can delegate more computationally intensive tasks to another nodal device (e.g., to perform processor intensive correlations), but still perform less computationally intensive tasks (e.g., data comparison). In other embodiments, the routine 320 can have all analytics delegated to anothernode manager 303. - At
block 327 the routine 320 processesnodal information 14 according to variousnodal analytics 16. An example of such correlations is described below with reference toFIG. 3C . - At
block 328 the routine 320 developsnodal knowledge 18 based at least in part on thenodal analytics 16 applied atblock 327. In particular, the routine 320 can decide in a rule making stage whether a particular rule should be tested (or further tested) before it is adopted, whether the rule should be discarded, or whether the rule should be deemed true (e.g., an expert opinion rule that is deemed to be fact or that is based on manual intervention from a user). In one embodiment, certainnodal information 14 can causenodal analytics 16 to substantially change a rule. - At
decision block 329 the routine 320 determines whether it should grant nodal control to the nodal device. In some embodiments the nodal device is passive. For example, the nodal device can be suited to gathering data but not controlling the position of thetracker 200. In another embodiment, the nodal device could be a consumer device used to gather data for analyzing a user power consumption behavior. For example, a transaction could include incentives for users to provide information relating to their consumption behavior. A discounted price for such a unit could be offered in exchange for this information. This information could be useful for creatingnodal knowledge 18, such as consumer power consumption. Table 1 provides various other examples ofnodal information 14. -
TABLE 1 Local Nodal Information Generic Nodal Information Wind speed SCADA (e.g., data from grid) Wind direction Grid Voltage Ambient temperature Grid power factor Barometric pressure Grid configuration Ambient/Planar irradiance (sun Battery charge levels ambient) Available discharge power Solar cell temperatures Signal conditioning Motor currents User demand Motor temperatures Demand response Tilt/Azimuth User consumption Real time (time stamp) Consumer pricing GPS location - A fundamental problem with incorporating solar energy into existing electrical grids is that the grids must have enough capacity to meet peak demands when aggregate demands are highest. A conventional solution is “pure peaker” power plants. Conventional solar generation is typically not suitable as a pure peaker because even though its availability is predicable, it cannot be guaranteed. Solar generation has low inertia; generation can be online/offline almost instantaneously. Conversely traditional power plants (coal, nuclear) require days to cycle. Load following gas plants require 30 to 90 minutes. The demand for ancillary services, which is typically over multiple intervals on any given day, occurs when power must be added to or taken off grid in a matter of seconds to regulate voltage or power factor corrections.
- For these and other reasons the inclusion of conventional solar systems at significant levels introduces problems that will increase with additional solar deployment (PV penetration). Due to both the intermittent and low inertia of conventional solar generation, significant disruption to the generation hierarchy of base load and “pure peaker” plants results in significant price volatility. Additionally, utilities must keep electricity in reserve to provide for supply disruptions or demand spikes, and they must regulate voltage and keep it steady. Both imperatives are difficult when solar resources come online/offline abruptly.
- Referring to
FIG. 4A , embodiments of energy distribution systems, or autonomous energy networks (AENs) configured in accordance with embodiments of the present technology can provide a complete solution from deployment to management of a fully autonomous distributed power plant. The successful realization of an efficient and reliable solar energy source can include: -
- Targeting “nonproductive,” sun-advantaged land close to power lines for the location of equipment. The ideal property is suburban/urban brown lots that are on the local substation feed to where the power will be used. Although, with the use of virtual net metering, these geographic limitations are bypassed allowing the generation site and energy consumption to spread across the utility service area. A low-profile, small footprint installation facilitates use of marginal nonproductive land and flat roofs.
- Solar trackers can enable any solar installation to harvest high concentrations of solar flux anywhere on the globe. This can realize, for example, up to a 50% increase over fixed angle installations for the same solar panels. This increased production for the same number of solar panels saves on land, labor, and components costs. Matching production with local consumption and grid conditions is possible with the addition of multiple solar trackers. For any solar panel, maximum energy harvest is guaranteed throughout the year.
- The
tracker electronics 205 can employ a Smart Controller and Analysis Node (SCAN) that includes an Expert Systems Inference Engine (ESIE) embedded into each installation to provide dynamic, rules-based decision response to real-time events on the grid and at the local installation. Decisions whether to store, consume power onsite, or net meter are events that need to take in a myriad of changing conditions. - These rules can be generated in the AEN data center to take advantage of an aggregation of many installations and events that are happening on the grid (DNR, supply interruptions, real time pricing, etc.) and then transferred to the local installation.
- To take advantage of high efficiency solar trackers and provide reliable generation sources, there can be guaranteed minimum down times and the ability to proactively operate and maintain (0 & M) a large number of installations remotely with a minimum of service truck rolls. Each local SCAN installation combined with the AEN can provide installation flexibly with the added sophistication of remote analytics and management. The AEN platform can provide an active intelligent “Expert System” presence at the edge of the grid through, e.g., an integrated cellular communications network.
- Each installation can include a computer, such as a Linux based computer, with SCADA (Supervisory Control And Data Acquisition) capabilities and an Expert Systems Inference Engine (ESIE). This decision expertise manages the local installation and provides remote access through, e.g., a cellular network connection. The AEN's SCADA API (Application Program Interface) allows QES, partners, and utilities access to local grid operational data and a platform for advanced smart grid applications. The ESIE enhanced supervisory capabilities manage the advanced power harvesting (Learned Energy Ray Normalization, LERN) algorithms for sun positioning for up to 20 solar trackers. Data is gathered, analyzed, and reported to the AEN network for near real-time and historical tracking. The ESIE management proactively monitors trending and exception events that are processed at the local site and reported to the AEN. Modified ESIE rules are downloaded when new “insight” is generated from the AEN master ESIE processing aggregate data sets of a large number of installations plus third party data bases (real time market pricing, DRM requests, national weather services, solar forecasts, etc.). Various related functions can include:
-
- Solar PV panels and micro-inverters provide power and data (inverters; continuous power output and grid voltages). This data is cached, analyzed, and compressed for upload to the AEN storage for analysis providing predictive maintenance, warranty, and billing functions.
- Voltage control at the point of power consumption. This function can monitor the voltage and power factor of the grid voltage. Problems can be rectified, for example, in one or more of the following ways:
- Low voltage
- Add capacitance to correct the power phase of the grid voltage. This action corrects under voltage conditions where there is distortion of grid power factor from large reactive loads (motors, A/C units, etc.).
- Discharge storage device.
- High voltage
- Slightly turning gantry away from sun to reduce generation.
- Diverting generation into charging of storage devices.
- Low voltage
- Sensor inputs from the physical actions of the solar tracker and the local environment can include:
- Weather station (wind speed, wind direction, temperature, humidity, solar irradiance, precipitation, barometer, reference solar irradiance).
- Spatial orientation sensors of the real world position of the gantry as opposed to where it is calculated to be. This sensor can also be used to detect unauthorized gantry manipulation or attempted theft.
- Absolute reference sensing of true south compass direction.
- Additional I/O for controlling local hardware, measuring local variables, and discrete inputs.
- SCADA functions can include:
-
- Control of each axis motor and correct operation throughout the controlled sun tracking moves.
- Measurement of grid voltage.
- Measurement of grid power factor.
- Monitor of local controller supply voltage (voltages delivered to each motor).
- Status of local network (Modbus, Ethernet, USB, Cellular radio).
- Monitor and control override switches for local maintenance operations.
- iOS (iPhone, iPad, etc.) control surface for local control of installation.
- Calculation of the position of the sun.
- Validate correct movement of the gantry, monitor long term mechanical drifts of motors and gantry movements, and apply correction.
- Logging of power generation and performance metrics, compress, analyze, and transmit to AEN remote secure server.
- Update software modules through secure network connection.
- Provide real-time secure access for troubleshooting.
- Provide local sun intensity information for cloud prediction services
- Interface to existing utility or installed generation and control equipment.
- Provide micro climate information, such as current solar insolation value, temperature, barometric pressure, wind speed, wind direction, and/or precipitation.
- ESIE functions can include:
-
- Update local ESIE current rule sets.
- Calculate long term drifts on power generation and apply corrections (LERN).
- Provide voltage control action decisions.
- DMR action decisions.
- Manage intelligent power storage and dispatch with various storage and generation options, such as batteries, fuel cells, and/or compressed Air.
- Provide intelligent islanding logic, such as automated islanding reconnection from grid when unstable grid conditions exist, demand response requests from utility to take site offline on low voltage (brown out) conditions, intermittent, or blackout conditions, and/or provide power to on-site customers during local blackouts.
- Real time load measurement and management of customer electricity consumption for energy use profile optimization. This function can be augmented by use of a local appliance control network such as ZigBee for granular onsite energy management.
- Secure site with motion (gantry) and video surveillance.
- In various embodiments, the AEN can include cloud based data and control network connects to each SCAN installation allowing the aggregation of information and services to be near real time, historical, proactive, and predictive. Each SCAN computer has the intelligence to perform the tasks demanded for complete autonomous operation if it never connects to the AEN cloud. This can allows for intermittent operations as standalone entities to optimize various network configurations and real world limitations of network performance. Referring to
FIG. 4B , in the cloud, there can include a few replication nodes, a number of directory nodes, and a larger number of data nodes. In one implementation, one might run all of these nodes on virtual machines in, e.g., Amazon data centers. Directory nodes can manage information and topology about all other nodes and help nodes find one another. Data nodes store data, and replication nodes manage pulling data from less-accessible or slower data nodes (e.g. tracker nodes) and push data to bigger machines with more reliable network connectivity. - In normal operation, a solar node collects data and then locates the local data node by consulting the directory node. The directory node also knows about other directory nodes in the cloud, and can consult them to find data nodes running in the cloud to push data to as well. Most of the intelligence about where data should go is handled by the replication nodes in the cloud; the solar node mostly pushes data to whichever is the closest data node according to the directory node.
- In disconnected mode, the solar nodes function as before. However, the directory nodes cannot find the authoritative directory nodes, so they coordinate among themselves and elect a gantry to start a local replication node. This node manages local storage space for the island by prioritizing data so that the remaining storage is balanced between data nodes, and, in the event one needs to discard data, the lowest-priority data is discarded first. Once the network is functioning again, the replicator node coordinates reconnection to the rest of the network, and the queued-up data drains out to the data nodes in the cloud.
- Note that there may be situations where some
trackers 200 in a group may be in a state of permanent disconnection while others in the same group have normal network access. In this case, the local replication node hangs around to replicate data from the partially-disconnected data nodes out to more available data nodes. - The AEN can also provide other features, such as:
-
- Aggregation and storage of information from all subscribing installations.
- Provide API interface to data set for both in-house use and subscribers:
- Micro environment weather data over a large geographic area, providing near real-time and historical information.
- Near real-time and historical local grid conditions.
- Voltage
- Power factor
- Outage information
- Near real-time power and historical power generation from any subscribing SCAN installation.
- Near real-time and historical power usage of local site consumption and energy use profiling.
- Individual SCAN and aggregate solar generation forecasting.
- DRM service requests.
- Voltage regulation services.
- Power factor correction services.
- Operations & Management of SCAN installations.
- SCAN ESIE rule sets generation and updating.
- SCAN program updating.
- Analyze long term drifts on power output of each PV panel.
- Expert systems scheduling of service and maintenance.
- Warranty monitoring for performance guarantees.
- Power generation metrics for billing of PPA installations.
- Large account corporate management of multiple sites
- Utility planning and provisioning
- In some embodiments, the knowledge base on the network cloud handles logistics, the installation process, the sales process, and even the permitting process to ensure that there is maximum efficiency, reliability, and minimum cost from sales lead generation to maintenance schedules. This is all exposed to employees and dealers through a graphic interface (see below) that runs on a computer, laptop, tablet or smartphone. Each employee has a certain level of security clearance that allows them to see or not to see certain information on their particular account.
- The SCAN installation can be a complete turnkey solution that provides the site customer an efficient and reliable power source that is remotely managed and is maintained as an evolving intelligent smart grid power generation asset. The customer need not have any expertise in power production equipment, networking, or operations and maintenance. All functions are managed by onsite intelligence supported by integrated, offsite management.
- Smart grid capability built into both the onsite SCAN and remote AEN offer the utility the ability to see what is happening at the customer end of the grid network. These features alleviate the problems of blind solar deployments (residential rooftops) that offer no visibility to the grid operator. With the addition of a SCADA API, integration to the utility management software platforms is enabled. This offers real value to the utility by providing and integrated and reliable power source where power is consumed. By solving the PV issues articulated above, the PV penetration problem is minimized allowing solar energy to be an asset rather than a problem to the grid.
- Referring to
FIG. 4C , an AEN controller center can be arranged to operate various aspects of a microgrid. Referring toFIG. 4D , a microgrid licensing/investing/purchasing scheme can include technology licensees, exchange investors, independent generators, independent dealers/franchisers, power purchase agreement providers (PPA), and a microGrid Energy Independence Exchange. As shown in this scheme, various network fees, service residuals, licensing fees, investments, and dividends can be generated. - Referring to
FIG. 3C , the following disclosure describes certain aspects of the learning process employed by node managers (e.g., via node nodal analytics and knowledge). In one embodiment, node managers can gather sensor data from onsite sensors with time stamps and serial numbers. Node managers can further gather third-party data based on the locations and time stamps of the sensor data. Some examples of possible third-party data may include, but are not limited to, one or more of: - a. Utility SCADA requests
- b. Weather data
- c. Real time energy pricing
- d. Grid Battery storage data
- The node manager can also determine minimum sample size for 99% confidence using:
-
- ii. n=sample size
- iii. Za/2=critical value=value of standard distribution at 97.5 percentile confidence level
- iv. E=margin of Error
- 1. Simple approximation of margin of error at 99% confidence is:
-
- v. σ=standard deviation of x number of time stamped events
-
- In one embodiment, if minimal sample size is met for 2 or more data points, there can be a test for correlation:
-
- a. If the absolute value of the correlation coefficient (determined by the dot product of two value vectors or by the Pearson product-moment correlation coefficient) is greater than 0.95 then a rule may be made automatically and sent to manual processing for quality assurance (since correlation does not always mean causation).
- i. A theoretical example of this process is as follows:
- 1. Sufficient sample size is met for correlation of 3 data points.
- 2. Correlation coefficient of 0.96 between over voltage and irradiance levels over 980 W/m2 when ambient temperature is below 84 degrees Fahrenheit.
- 3. A New Rule is made for over voltage correction based on irradiance levels when temp is below 84 degrees.
- 4. The software model would then test to find weather conditions that cause 84 degree temperatures and irradiance levels in excess of 980 W/m2 to determine if over voltage may be forecasted.
- ii. A theoretical counter example (local rule testing) is as follows:
- 1. Sufficient sample size is met for correlation of 3 data points.
- 2. Correlation coefficient of 0.74 between under voltage and battery bank discharge request for 500 kW+/−50 kW on Saturday between 1 and 3 pm PST in La Jolla, Calif.
- 3. A New Rule is not made.
- 4. Rule is sent for manual processing.
- 5. Manual processing makes a new TEST rule that states:
- a. Between 1 pm and 3 pm all units within a 20 mile radius of La Jolla, Calif. log voltage values and test against temperature range.
- iii. A second theoretical counter example (the case of statistical insignificance) is as follows:
- 1. Sufficient sample size is met for correlation of 2 data points.
- 2. Correlation coefficient of 0.04 is determined between demand response requests from utility SCADA on Monday at 5:50 pm local time.
- 3. Correlation is thrown out and determined statistically insignificant.
- i. A theoretical example of this process is as follows:
- a. If the absolute value of the correlation coefficient (determined by the dot product of two value vectors or by the Pearson product-moment correlation coefficient) is greater than 0.95 then a rule may be made automatically and sent to manual processing for quality assurance (since correlation does not always mean causation).
- The node manager can also employ manual intervention for low correlation coefficient (greater than 0.05, less than 0.95 correlation coefficient based on sufficient sample size):
-
- a. Statistically significant correlations can be manually examined to further test the correlation.
- b. Modifications in the rule set for both the network cloud and the distributed expert systems are used to reach a sufficiently high correlation coefficient.
- i. For example: If the correlation coefficient is 0.05, a manual TEST rule can be implemented to broaden the scope of correlation in order raise or lower the coefficient.
- 1. If the coefficient stays the same or goes below 0.05, the correlation is discarded.
- 2. If the coefficient goes up but is still below 0.95 a new TEST rule can be implemented to broaden the scope of correlation.
- i. For example: If the correlation coefficient is 0.05, a manual TEST rule can be implemented to broaden the scope of correlation in order raise or lower the coefficient.
- TEST rules are then used by the expert systems to find positive correlations, negative correlations, or statistical insignificance. The utility grid is affected by a statistically infinite number of stimuli from macro level weather patterns that cause droughts or floods to micro level human activities like sporting events. This makes manual processing important in order to zero in on new rules by expanding the scope of testing when necessary instead of trying to correlate the statistically infinite number of data points caused by grid stimuli. For example, if the grid is experiencing under voltage every weeknight between 5:00 pm and 6:00 pm with a correlation coefficient of 0.80, a TEST rule could be implemented to test this correlation vs. different temperature ranges. This is because under voltage may only occur at high or low temperatures due to air conditioning or heater use. The 65 to 80 degrees Fahrenheit temperature range may not experience under voltage, which may be causing the correlation coefficient to be 0.80. After the new TEST rule is implemented to check specific temperature ranges, the correlation coefficient of under voltage to time of day (5:00-6:00 pm) becomes 0.96. A new rule is made to charge batteries prior to 5:00 pm only when temperature ranges are lower than 65 or higher than 80 degrees Fahrenheit.
- TEST rules, in some embodiments, can be predictions, observations, metrics, or desired outcomes that can be tested against events that occur. Correlations can be made between TEST rules and mined data from sensors and third-party databases. Correlation coefficients of less than 0.05 are determined statistically insignificant and can be ignored.
- Rules can be made for:
-
- a. How to make rules,
- b. How to establish a value hierarchy of a set of rules,
- c. When to log data,
- d. What data to log,
- e. How to log, analyze, and correlate data,
- f. Taking action to solve problems on the grid, the network cloud management system, or the local sites,
- g. When to buy electricity from the grid and when to sell power back to the grid,
- h. When to charge batteries and when to discharge batteries,
- i. When to pull off the grid when things become unstable (islanding),
- j. How to respond to automated utility requests (i.e. demand response, microgrid, islanding, etc.),
- k. When to respond to anomalies (based on standard deviation), and
- l. Which predictions, observations, metrics, or desired outcomes should be cross correlated with mined data.
-
FIGS. 5A-5E provide various example user interfaces that can be used with a node manager. Table 2, below, shows various examples of application interfaces for access with a node manager. -
TABLE 2 Tracker control: automatic/manual mode toggle manual positioning device calibration device configuration - birth certificates, re-provisioning, latitude/longitude, tracking interval, various other things we discover to be useful, knobs for maintenance techs device security management Access to current/historical tracker log data: panel orientation motor motion statistics (movement errors, exceptional conditions, etc.) motor amperage computed sun position (later) LERN information - how far the sun is from where we computed it to be, and other data collected to refine our solar positioning model power generation metrics and other power-related data Access to node/network event logs (for diagnostics): related/neighbor nodes local software configuration (which nodes are running where, node status) data pushed (which data, and to where) rules available for decision-making rules applied startup/shutdown/sleep events Real-time and historical smart grid data access: aggregate grid statistics: power generation, changes throughout the day, seasons local and aggregate grid performance statistics “post-mortem” data on how well our tracking and rules performed compared to the “ideal model” aggregate statistics by location, kind of installation, size of installation, or age of installation - The following description describes certain aspects of Internodal Bidding. Each node provides one or more services and/or products that vary in price based on the supply and demand of those services or products. In order to set an accurate market price for transactions that can happen frequently (e.g., every millisecond), there must be an automated system.
- In some embodiments, node managers can be accessed through the nodal access interface where a minimum price can be set for the services or products offered by that particular node. Throughout each day, Internodal Bidding occurs autonomously for each service or product based on the minimum acceptable value (MAV) for that service or product. For example, this could occur when a third party requests a particular service or product or when the energy network requires a certain service or product to maintain reliability.
- In some instances, Internodal Bidding can be similar to the way Google allows users to set a Maximum Cost Per Click (CPC) on certain advertising. In the Google scenario, users can set parameters for many different outcomes (e.g. maximum exposure of advertisement, lower cost per click, a mixture of exposure and cost considerations, etc.) Those willing to pay the highest CPC have the best chance of winning many bids and ensuring the most exposure. Those trying to save money, run the risk of limited or no advertising exposure. Internodal Bidding can occur in a similar fashion, with the exception that nodes are set to provide a service or product for a MINIMUM acceptable value. Suppliers of nodes that are willing to accept a smaller value for their service or product will likely sell more product or service. For example, if a node has a limited supply, suppliers will likely make their money in times of peak demand. If a node has a large supply, suppliers may choose to bid very low in order to sell the most services or products.
- One of ordinary skill in the art will recognize that many parameters associated with cost and demand as well as micro- and macro-transactions can apply to the concept of Internodal Bidding. In particular examples, Internodal Bidding has several parameters that can be altered or adapted to allow suppliers associated with nodes to maximize their revenue. For example, certain MAV parameters may include setting different MAVs for different times of day, setting different MAVs for different times of year, establishing different MAVs for different services or products, establishing different MAVs for different levels of storage capacity, determining different MAVs for different weather patterns, and/or establishing different MAVs during certain predictable local events (e.g. sports events, festivals, etc.).
- In many embodiments, Internodal Bidding can allow for energy products and services to maintain a reliable service while keeping the cost of energy and reliability as low as possible (e.g., much like Google has done for the advertising industry). Furthermore, it also allows the largest energy plants as well as the smallest single energy producer to participate in the energy market.
- Node 150 contains 64 kW of solar panel capacity and 128 kWh of storage. The Node's MAV for stored kilowatt hours is 60 cents/kWh. This is a very high price per kWh considering that the local retail price of electricity is 18 cents/kWh.
- The local utility sends out a “spinning reserve” peak demand request for 60 kW of capacity for the next 2 hours. Their bid price is 65 cents/kWh because the utility's only other option is to cut service at that particular substation.
- In this example, Node 150 rises to the top of the bidding with its 60 cents/kWh bid. Node 150 wins the bid and supplies 120 kWh of capacity for 60 cents/kWh. Node 150 would have received 8 cents per kWh if sold during off-peak times or $9.60. Node 150 would have received 18 cents per kWh if sold at retail or $21.60
- Because of Automated Internodal Bidding, Node 150 was able to receive $72.00 for just one battery charge cycle. Accordingly, Internodal Bidding allows renewable energy and storage devices to provide the same services supplied today by fossil fuel powered generators and power plants in just milliseconds rather than several minutes, hours, or even days. In particular instances of application, the larger the network of nodes becomes, the more reliable the products and services can become.
-
FIG. 6 is flow diagram illustrating anInternodal Bidding scheme 600 in accordance with an embodiment of the present technology. Thescheme 600 can include setting a MAV through a Nodal Access Interface (block 602). Thescheme 600 can continue atdecision block 604 where thescheme 600 can determine if the request is manual. If the request is manual, thescheme 600 can continue to block 606 where it is determined if the request is within bidding parameters (e.g., established parameters, pre-set parameters, etc.). If the request is not manual, thescheme 600 can determine if an automated service is necessary (decision block 605). If the automated service is necessary, thescheme 600 can then continue on to block 606 to determine if the request is within bidding parameters. If an automated service is not needed, thescheme 600 can return to block 602 where a MAV is set through the Nodal Access Interface. - If the request is within bidding parameters, the
scheme 600 can continue to decision block 608 where it is determined if the bid is low enough. If the bid is low enough, thescheme 600 can provide the product or service requested (block 610). If the bid exceeds a threshold (e.g., is not low enough), thescheme 600 can return to block 602 to set a MAV through the Nodal Access Interface. -
FIG. 7 show various system logs than can be generated by a node manager during a single day of operation of a solar tracker in accordance with an embodiment of the present technology. Table 3, below, shows example setup parameters corresponding to the system logs ofFIG. 7 . -
TABLE 3 A day in the life of a distributed solar power plant deployed into the Southwest United States. Assumptions: Installed SCAN installations 3000 Gantries installed 10,800 (average 3.6 gantries per SCAN) Installed Capacity 87.48 MWatt Yearly average capacity factor 31.25% (7.5 sun hours, yearly average) Total battery storage capacity 45,589 kWh Island enabled SCAN 758 installations Voltage regulation of installed 55% capacity 15 MW (load shedding) Demand/Response capability Utility Dispatch Services SCADA Utility API Island demand requests Voltage control requests Storage discharge requests Load shedding requests Utility Data Services: SCAN SCADA Analytic API Solar forecasting data Local grid conditions data (voltage, power factor, outage) Micro climate data sets - Embodiments of the subject matter and the operations described in this specification can be implemented in digital electronic circuitry, or in computer software, firmware, or hardware, including the structures disclosed in this specification and their structural equivalents, or in combinations of one or more of them. Embodiments of the subject matter described in this specification can be implemented as one or more computer programs, i.e., one or more modules of computer program instructions, encoded on computer storage medium for execution by, or to control the operation of, data processing apparatus.
- A computer storage medium can be, or can be included in, a computer-readable storage device, a computer-readable storage substrate, a random or serial access memory array or device, or a combination of one or more of them. Moreover, while a computer storage medium is not a propagated signal, a computer storage medium can be a source or destination of computer program instructions encoded in an artificially-generated propagated signal. The computer storage medium also can be, or can be included in, one or more separate physical components or media (e.g., multiple CDs, disks, or other storage devices). The operations described in this specification can be implemented as operations performed by a data processing apparatus on data stored on one or more computer-readable storage devices or received from other sources.
- The term “programmed processor” encompasses all kinds of apparatus, devices, and machines for processing data, including, by way of example, a computer, a system on a chip (or multiple ones or combinations of the foregoing). The apparatus can include special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application-specific integrated circuit). The apparatus also can include, in addition to hardware, code that creates an execution environment for the computer program in question, e.g., code that constitutes processor firmware, a protocol stack, a database management system, an operating system, a cross-platform runtime environment, a virtual machine, or a combination of one or more of them. The apparatus and execution environment can realize various different computing model infrastructures, such as web services, distributed computing and grid computing infrastructures.
- A computer program (also known as a program, software, software application, script, or code) can be written in any form of programming language, including compiled or interpreted languages, declarative or procedural languages, and it can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, object, or other unit suitable for use in a computing environment. A computer program may, but need not, correspond to a file in a file system. A program can be stored in a portion of a file that holds other programs or data (e.g., one or more scripts stored in a markup language document), in a single file dedicated to the program in question, or in multiple coordinated files (e.g., files that store one or more modules, sub-programs, or portions of code). A computer program can be deployed to be executed on one computer or on multiple computers that are located at one site or distributed across multiple sites and interconnected by a communication network.
- The processes and logic flows described in this specification can be performed by one or more programmable processors executing one or more computer programs to perform actions by operating on input data and generating output. For example, tracker electronics, servers, mobile devices, etc., can be implemented as a controller in an auxiliary device. The processes and logic flows can also be performed by, and the apparatus can also be implemented as, special purpose logic circuitry, e.g., an FPGA or an ASIC. For example, the node manager can be implemented as a controller in an auxiliary device.
- Processors suitable for the execution of a computer program include, by way of example, both general and special purpose microprocessors, and any one or more processors of any kind of digital computer. In some embodiments, the processors can be selected according to the type of device.
- Generally, a processor will receive instructions and data from a read-only memory or a random access memory or both. The essential elements of a computer are a processor for performing actions in accordance with instructions and one or more memory devices for storing instructions and data. Generally, a computer will also include, or be operatively coupled to receive data from or transfer data to, or both, one or more mass storage devices for storing data, e.g., magnetic, magneto-optical disks, or optical disks. For example, a server can transfer nodal information, nodal analytics, and/or knowledge can be transferred to flash memory. However, a computer need not have such devices. Moreover, a computer can be embedded in another device, e.g., a mobile telephone, a personal digital assistant (PDA), a mobile audio or video player, a game console, a Global Positioning System (GPS) receiver, or a portable storage device (e.g., a universal serial bus (USB) flash drive), to name just a few. Devices suitable for storing computer program instructions and data include all forms of non-volatile memory, media and memory devices, including by way of example semiconductor memory devices, e.g., EPROM, EEPROM, and flash memory devices; magnetic disks, e.g., internal hard disks or removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks. The processor and the memory can be supplemented by, or incorporated in, special purpose logic circuitry.
- To provide for interaction with a user, embodiments of the subject matter described in this specification can be implemented on a computer having a display device, e.g., an LCD (liquid crystal display), LED (light emitting diode), or OLED (organic light emitting diode) monitor, for displaying information to the user and a keyboard and a pointing device, e.g., a mouse or a trackball, by which the user can provide input to the computer. In some implementations, a touch screen can be used to display information and to receive input from a user. Other kinds of devices can be used to provide for interaction with a user as well; for example, feedback provided to the user can be any form of sensory feedback, e.g., visual feedback, auditory feedback, or tactile feedback; and input from the user can be received in any form, including acoustic, speech, or tactile input. In addition, a computer can interact with a user by sending documents to and receiving documents from a device that is used by the user; for example, by sending web pages to a web browser on a user's client device in response to requests received from the web browser.
- Embodiments of the subject matter described in this specification can be implemented in a computing system that includes a back-end component, e.g., as a data server, or that includes a middleware component, e.g., an application server, or that includes a front-end component, e.g., a client computer having a graphical user interface or a Web browser through which a user can interact with an implementation of the subject matter described in this specification, or any combination of one or more such back-end, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication, e.g., a communication network. Examples of communication networks include a local area network (“LAN”) and a wide area network (“WAN”), an inter-network (e.g., the Internet), and peer-to-peer networks (e.g., ad hoc peer-to-peer networks).
- From the foregoing, it will be appreciated that specific embodiments have been described herein for purposes of illustration, but that various modifications may be made without deviating from the disclosed technology. The methods disclosed herein include and encompass, in addition to methods of making and using the disclosed devices and systems, methods of instructing others to make and use the disclosed devices and systems. For example, the operating instructions can instruct the user how to provide any of the operational aspects of the Figures discussed herein. In some embodiments, methods of instructing such use and manufacture may take the form of computer-readable-medium-based executable programs or processes. Moreover, aspects described in the context of particular embodiments may be combined or eliminated in other embodiments. Further, although advantages associated with certain embodiments have been described in the context of those embodiments, other embodiments may also exhibit such advantages, and not all embodiments need necessarily exhibit such advantages to fall within the scope of the presently disclosed technology.
Claims (18)
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/815,898 US9488968B2 (en) | 2013-01-15 | 2013-03-15 | Energy distribution system and related methods, devices, and systems |
US15/295,787 US10437209B2 (en) | 2013-01-15 | 2016-10-17 | Solar tracker and related methods, devices, and systems |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US201361752922P | 2013-01-15 | 2013-01-15 | |
US13/815,898 US9488968B2 (en) | 2013-01-15 | 2013-03-15 | Energy distribution system and related methods, devices, and systems |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/815,913 Continuation US9471050B2 (en) | 2013-01-15 | 2013-03-15 | Solar tracker and related methods, devices, and systems |
Publications (2)
Publication Number | Publication Date |
---|---|
US20140201109A1 true US20140201109A1 (en) | 2014-07-17 |
US9488968B2 US9488968B2 (en) | 2016-11-08 |
Family
ID=51164251
Family Applications (4)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/815,898 Expired - Fee Related US9488968B2 (en) | 2013-01-15 | 2013-03-15 | Energy distribution system and related methods, devices, and systems |
US13/815,913 Expired - Fee Related US9471050B2 (en) | 2013-01-15 | 2013-03-15 | Solar tracker and related methods, devices, and systems |
US13/815,922 Abandoned US20140200717A1 (en) | 2013-01-15 | 2013-03-15 | Node manager in an energy distribution system and related methods, devices, and systems |
US15/295,787 Expired - Fee Related US10437209B2 (en) | 2013-01-15 | 2016-10-17 | Solar tracker and related methods, devices, and systems |
Family Applications After (3)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/815,913 Expired - Fee Related US9471050B2 (en) | 2013-01-15 | 2013-03-15 | Solar tracker and related methods, devices, and systems |
US13/815,922 Abandoned US20140200717A1 (en) | 2013-01-15 | 2013-03-15 | Node manager in an energy distribution system and related methods, devices, and systems |
US15/295,787 Expired - Fee Related US10437209B2 (en) | 2013-01-15 | 2016-10-17 | Solar tracker and related methods, devices, and systems |
Country Status (2)
Country | Link |
---|---|
US (4) | US9488968B2 (en) |
WO (1) | WO2014113481A1 (en) |
Cited By (13)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20150039460A1 (en) * | 2013-08-01 | 2015-02-05 | Shilpa Parekh | Bi-directional project information updates in multi-party bidding |
US20160154082A1 (en) * | 2014-12-01 | 2016-06-02 | Wts Llc | Dual axis tracking device |
US20160169560A1 (en) * | 2013-07-10 | 2016-06-16 | Innovative Motion Gmbh | Solar collector assembly |
US20160238189A1 (en) * | 2013-10-22 | 2016-08-18 | The Arizona Board Of Regents On Behalf Of The University Of Arizona | Octohedral frame and tripod for rotating equipment |
US10495720B2 (en) | 2014-12-01 | 2019-12-03 | Wts Llc | Control valve assembly for a fluid heating system |
US10505059B2 (en) | 2015-01-16 | 2019-12-10 | The Arizona Board Of Regents On Behalf Of The University Of Arizona | Micro-scale concentrated photovoltaic module |
US10538451B2 (en) | 2015-03-02 | 2020-01-21 | The Arizona Board Of Regents On Behalf Of The University Of Arizona | Glass or metal forming mold of adjustable shape |
US10551089B2 (en) | 2015-08-03 | 2020-02-04 | The Arizona Board Of Regents On Behalf Of The University Of Arizona | Solar concentrator for a tower-mounted central receiver |
US10686400B2 (en) | 2015-06-12 | 2020-06-16 | THE ARIZONA BOARD OR REGENTS on behalf of THE UNIVERSITY OF ARIZONA | Tandem photovoltaic module with diffractive spectral separation |
US20200202351A1 (en) * | 2018-12-19 | 2020-06-25 | Francotyp-Postalia Gmbh | Service payment system and method |
US10989420B2 (en) | 2016-11-18 | 2021-04-27 | Wts Llc | Digital fluid heating system |
US11803500B1 (en) * | 2018-07-31 | 2023-10-31 | Faith Technologies, Inc. | Peer-to-peer DC or AC distribution network |
US11946886B2 (en) | 2014-12-01 | 2024-04-02 | Wts Llc | Fluid heating system |
Families Citing this family (23)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
KR101492528B1 (en) * | 2013-06-10 | 2015-02-12 | 주식회사 하이메틱스 | Method for monitoring photovoltaic power generation by using rtu and wireless rtu device therefor |
CA2945270A1 (en) * | 2014-04-09 | 2015-10-15 | Claudio Ornella | Supporting structure for solar panels |
US10255393B2 (en) | 2014-06-20 | 2019-04-09 | Board Of Regents, The University Of Texas System | Optimally placing photovoltaic arrays to maximize value of energy production based on peak power production, local solar radiation, weather, electricity market prices and rate structures |
US20160118799A1 (en) * | 2014-10-22 | 2016-04-28 | SEWW Energy Inc. | Apparatuses, Methods, and Systems for Sustainable Energy Microgrid Mobile Medical Solutions |
US9718334B2 (en) | 2015-04-09 | 2017-08-01 | Kevin Paul Means | Assembly and method for supporting and locking movable solar panels |
US20180241210A1 (en) * | 2015-08-12 | 2018-08-23 | Kyocera Corporation | Management server, management method and management system |
US10557646B1 (en) * | 2016-07-11 | 2020-02-11 | Nextracker Inc. | Sensing and feedback for row on sun tracking method and system |
US20180054156A1 (en) * | 2016-08-16 | 2018-02-22 | Roger F. Lokey | Solar Tracker System for Large Utility Scale Solar Capacity |
US20180175666A1 (en) * | 2016-12-20 | 2018-06-21 | Ecojiva, LLC | Electrical load management system |
WO2019014148A2 (en) * | 2017-07-10 | 2019-01-17 | Nuance Energy Group, Inc. | Transportable and multi configurable, modular power platforms |
US20190105991A1 (en) * | 2017-10-11 | 2019-04-11 | Divergent Technologies, Inc. | Solar extended range electric vehicle |
US10552082B2 (en) | 2018-04-03 | 2020-02-04 | International Business Machines Corporation | Optimized data replication in multi-tier storage environment |
WO2020047167A1 (en) * | 2018-08-28 | 2020-03-05 | Nextracker Inc. | Systems for and methods of positioning solar panels in an array of solar panels with spectrally adjusted irradiance tracking |
US11251746B2 (en) | 2018-11-20 | 2022-02-15 | Nextracker Inc. | Staged stowage of solar trackers and method thereof |
US20230353087A1 (en) * | 2019-09-18 | 2023-11-02 | Clean Energy Factory Co., Ltd. | Solar module |
US11466900B2 (en) | 2019-09-20 | 2022-10-11 | King Fahd University Of Petroleum And Minerals | Dual-axis hydraulic system for solar tracking |
US10958211B1 (en) * | 2019-10-04 | 2021-03-23 | The Florida International University Board Of Trustees | Systems and methods for power management |
RU2723786C1 (en) * | 2019-11-29 | 2020-06-17 | Федеральное государственное бюджетное образовательное учреждение высшего образования "Забайкальский государственный университет" (ФГБОУ ВО "ЗабГУ") | Device for orientation of solar battery |
CN111245007B (en) * | 2020-01-08 | 2022-06-14 | 华为数字能源技术有限公司 | Position information acquisition method and device of controller |
US11444570B2 (en) | 2020-02-28 | 2022-09-13 | OffGrid Power Solutions, LLC | Modular solar skid with enclosures |
RU2746561C1 (en) * | 2020-07-03 | 2021-04-15 | Федеральное государственное бюджетное образовательное учреждение высшего образования "Московский государственный технологический университет "СТАНКИН" (ФГБОУ ВО "МГТУ "СТАНКИН") | Tracker |
WO2022266242A1 (en) * | 2021-06-16 | 2022-12-22 | Conti SPE, LLC. | Intelligent solar racking system |
ES1286556Y (en) * | 2022-01-24 | 2022-05-09 | Souto Daniel Bermudez | SOLAR TRACKER |
Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20050033707A1 (en) * | 2002-03-28 | 2005-02-10 | Ehlers Gregory A. | Configurable architecture for controlling delivery and/or usage of a commodity |
US20090188488A1 (en) * | 2008-01-28 | 2009-07-30 | Tilt Solar Llc | Wireless mesh networking of solar tracking devices |
US20100082171A1 (en) * | 2008-10-01 | 2010-04-01 | Toru Takehara | Network topology for monitoring and controlling a solar panel array |
US20110066297A1 (en) * | 2008-05-20 | 2011-03-17 | LiveMeters, Inc. | Remote monitoring and control system comprising mesh and time synchronization technology |
US20110106328A1 (en) * | 2009-11-05 | 2011-05-05 | General Electric Company | Energy optimization system |
US8528541B2 (en) * | 2005-01-31 | 2013-09-10 | Seesean, Inc. | Solar collection apparatus and methods |
Family Cites Families (43)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US603317A (en) | 1898-05-03 | calver | ||
US4146785A (en) | 1978-02-13 | 1979-03-27 | Sunpower Systems Corporation | Sun-tracking control system for solar collector |
US4408595A (en) | 1978-09-05 | 1983-10-11 | Broyles Howard F | Turret mounted solar concentrator with boom mounted secondary mirror or collector |
US4215410A (en) | 1979-02-09 | 1980-07-29 | Jerome H. Weslow | Solar tracker |
US4440155A (en) | 1981-07-17 | 1984-04-03 | Reynolds & Taylor, Inc. | Solar concentrating lens and receiver |
US4794909A (en) | 1987-04-16 | 1989-01-03 | Eiden Glenn E | Solar tracking control system |
FR2643510B1 (en) | 1989-02-23 | 1994-02-25 | Gallois Montbrun Roger | PERFECTED SOLAR COLLECTOR |
US5586218A (en) | 1991-03-04 | 1996-12-17 | Inference Corporation | Autonomous learning and reasoning agent |
US6485152B2 (en) * | 2000-05-05 | 2002-11-26 | Doug Wood | Matrix solar dish |
US6498290B1 (en) * | 2001-05-29 | 2002-12-24 | The Sun Trust, L.L.C. | Conversion of solar energy |
US20050197991A1 (en) | 2003-06-25 | 2005-09-08 | Wray Robert E. | Method and apparatus for providing rule-based, autonomous software agent with ontological information |
US7500178B1 (en) | 2003-09-11 | 2009-03-03 | Agis Network, Inc. | Techniques for processing electronic forms |
US8019445B2 (en) | 2004-06-15 | 2011-09-13 | Intelligent Generation Llc | Method and apparatus for optimization of distributed generation |
US7786059B2 (en) | 2004-12-21 | 2010-08-31 | Chevron Oronite Company Llc | Anti-wear additive composition and lubricating oil composition containing the same |
US7274975B2 (en) | 2005-06-06 | 2007-09-25 | Gridpoint, Inc. | Optimized energy management system |
US7884279B2 (en) | 2006-03-16 | 2011-02-08 | United Technologies Corporation | Solar tracker |
JP5137820B2 (en) | 2006-04-24 | 2013-02-06 | シャープ株式会社 | Solar power generation system and solar power generation system control method |
US20070290651A1 (en) | 2006-06-14 | 2007-12-20 | Worldwater & Power Corp. | Solar power control using irradiance |
ES2288418B1 (en) | 2006-06-19 | 2008-10-16 | Wattpic Energia Intel.Ligent, S.L. | AUTONOMOUS AND INTERACTIVE MODULAR SYSTEM OF SOLAR ENERGY PRODUCTION. |
US20110030672A1 (en) | 2006-07-14 | 2011-02-10 | Olsson Mark S | Solar Collection Apparatus and Methods Using Accelerometers and Magnetics Sensors |
US20080011288A1 (en) | 2006-07-14 | 2008-01-17 | Olsson Mark S | Solar Collection Apparatus and Methods Using Accelerometers and Magnetic Sensors |
KR20090077772A (en) | 2006-10-09 | 2009-07-15 | 카바닐라스 인제니에로스, 에스.엘. | Two-axle solar tracker |
US7890436B2 (en) | 2006-10-17 | 2011-02-15 | Clean Power Finance, Inc. | Billing and payment methods and systems enabling consumer premises equipment |
KR100819861B1 (en) | 2007-04-19 | 2008-04-08 | 다울이엔씨(주) | Solar tracker |
ITMI20071222A1 (en) | 2007-06-19 | 2008-12-20 | Enermill En Rinnovabili S R L | PANEL FOR ADJUSTABLE SOLAR MODULES |
US20090032089A1 (en) * | 2007-08-03 | 2009-02-05 | Atomic Energy Council - Institute Of Nuclear Energy Research | Solar tracker having louver frames |
EP3324505B1 (en) | 2007-10-15 | 2023-06-07 | Ampt, Llc | Systems for highly efficient solar power |
WO2009105291A1 (en) | 2008-02-18 | 2009-08-27 | Skyfuel, Inc. | Sun-tracking controller for multiple solar collectors |
US20090260619A1 (en) | 2008-04-20 | 2009-10-22 | The Boeing Company | Autonomous heliostat for solar power plant |
ES2366505B1 (en) | 2008-07-16 | 2012-09-14 | Benito Martín Barbero | DOUBLE AXLE SOLAR FOLLOWER. |
US20100191489A1 (en) | 2009-01-28 | 2010-07-29 | Uqm Technologies, Inc. | Distributed Generation Power System |
ES2378730B1 (en) | 2009-03-04 | 2013-03-19 | Mecanizados Solares, S.L. | PERFECTION IN THE SUBSTANCE OF A SOLAR FOLLOWER. |
KR20100102402A (en) | 2009-03-11 | 2010-09-24 | 윤정식 | Sunlight-tracking apparatus for solar cell module panel |
US20110233157A1 (en) * | 2010-03-22 | 2011-09-29 | JAC-Rack, Inc. | Solar panel mounting system and method |
US8071930B2 (en) * | 2010-07-08 | 2011-12-06 | SkylineSolar, Inc. | Solar collector having a spaced frame support structure with a multiplicity of linear struts |
US9300141B2 (en) | 2010-11-18 | 2016-03-29 | John J. Marhoefer | Virtual power plant system and method incorporating renewal energy, storage and scalable value-based optimization |
US8367995B2 (en) | 2011-02-23 | 2013-02-05 | King Fahd University Of Petroleum And Minerals | System and method for automatic positioning of a solar array |
US20120266938A1 (en) | 2011-04-25 | 2012-10-25 | Aspect Solar Pte Ltd | Solar tracking system and method for concentrated photovoltaic (cpv) systems |
WO2013108245A1 (en) * | 2012-01-22 | 2013-07-25 | Heliofocus Ltd. | Solar concentrating systems |
US20140352757A1 (en) * | 2013-03-15 | 2014-12-04 | Johnny Ramirez | Smart modular automated multi axis case for solar modules, panels, electronic displays, sensors, and the like |
CA2945270A1 (en) * | 2014-04-09 | 2015-10-15 | Claudio Ornella | Supporting structure for solar panels |
US10006665B2 (en) * | 2014-06-27 | 2018-06-26 | Sunpower Corporation | Solar tracker drive |
US9954089B2 (en) * | 2016-06-20 | 2018-04-24 | Infineon Technologies Americas Corp. | Low dislocation density III-nitride semiconductor component |
-
2013
- 2013-03-15 US US13/815,898 patent/US9488968B2/en not_active Expired - Fee Related
- 2013-03-15 US US13/815,913 patent/US9471050B2/en not_active Expired - Fee Related
- 2013-03-15 US US13/815,922 patent/US20140200717A1/en not_active Abandoned
-
2014
- 2014-01-15 WO PCT/US2014/011700 patent/WO2014113481A1/en active Application Filing
-
2016
- 2016-10-17 US US15/295,787 patent/US10437209B2/en not_active Expired - Fee Related
Patent Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20050033707A1 (en) * | 2002-03-28 | 2005-02-10 | Ehlers Gregory A. | Configurable architecture for controlling delivery and/or usage of a commodity |
US8528541B2 (en) * | 2005-01-31 | 2013-09-10 | Seesean, Inc. | Solar collection apparatus and methods |
US20090188488A1 (en) * | 2008-01-28 | 2009-07-30 | Tilt Solar Llc | Wireless mesh networking of solar tracking devices |
US20110066297A1 (en) * | 2008-05-20 | 2011-03-17 | LiveMeters, Inc. | Remote monitoring and control system comprising mesh and time synchronization technology |
US20100082171A1 (en) * | 2008-10-01 | 2010-04-01 | Toru Takehara | Network topology for monitoring and controlling a solar panel array |
US20110106328A1 (en) * | 2009-11-05 | 2011-05-05 | General Electric Company | Energy optimization system |
Cited By (23)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20160169560A1 (en) * | 2013-07-10 | 2016-06-16 | Innovative Motion Gmbh | Solar collector assembly |
US10514186B2 (en) * | 2013-07-10 | 2019-12-24 | Innovative Motion Gmbh | Solar collector assembly |
US10296970B2 (en) * | 2013-08-01 | 2019-05-21 | Ebay Inc. | Bi-directional project information updates in multi-party bidding |
US11704723B2 (en) | 2013-08-01 | 2023-07-18 | Ebay Inc. | Bi-directional project information updates in multi-party bidding |
US20150039460A1 (en) * | 2013-08-01 | 2015-02-05 | Shilpa Parekh | Bi-directional project information updates in multi-party bidding |
US9746127B2 (en) * | 2013-10-22 | 2017-08-29 | The Arizona Board Of Regents On Behalf Of The University Of Arizona | Frame with compression and tension members to rotate equipment about an axis |
US20160238189A1 (en) * | 2013-10-22 | 2016-08-18 | The Arizona Board Of Regents On Behalf Of The University Of Arizona | Octohedral frame and tripod for rotating equipment |
US10168412B2 (en) * | 2014-12-01 | 2019-01-01 | Wts Llc | Dual axis tracking device |
US10495720B2 (en) | 2014-12-01 | 2019-12-03 | Wts Llc | Control valve assembly for a fluid heating system |
US11946886B2 (en) | 2014-12-01 | 2024-04-02 | Wts Llc | Fluid heating system |
US20160154082A1 (en) * | 2014-12-01 | 2016-06-02 | Wts Llc | Dual axis tracking device |
US10890645B2 (en) | 2014-12-01 | 2021-01-12 | Wts Llc | Dual axis tracking method |
US11255804B2 (en) | 2014-12-01 | 2022-02-22 | Wts Llc | Method of calculating pathogen inactivation for a fluid heating system |
US10505059B2 (en) | 2015-01-16 | 2019-12-10 | The Arizona Board Of Regents On Behalf Of The University Of Arizona | Micro-scale concentrated photovoltaic module |
US11056599B2 (en) | 2015-01-16 | 2021-07-06 | The Arizona Board Of Regents On Behalf Of The University Of Arizona | Micro-scale concentrated photovoltaic module |
US11456394B2 (en) | 2015-01-16 | 2022-09-27 | The Arizona Board Of Regents On Behalf Of The University Of Arizona | Micro-scale concentrated photovoltaic module |
US10538451B2 (en) | 2015-03-02 | 2020-01-21 | The Arizona Board Of Regents On Behalf Of The University Of Arizona | Glass or metal forming mold of adjustable shape |
US10686400B2 (en) | 2015-06-12 | 2020-06-16 | THE ARIZONA BOARD OR REGENTS on behalf of THE UNIVERSITY OF ARIZONA | Tandem photovoltaic module with diffractive spectral separation |
US10551089B2 (en) | 2015-08-03 | 2020-02-04 | The Arizona Board Of Regents On Behalf Of The University Of Arizona | Solar concentrator for a tower-mounted central receiver |
US10989420B2 (en) | 2016-11-18 | 2021-04-27 | Wts Llc | Digital fluid heating system |
US11920801B2 (en) | 2016-11-18 | 2024-03-05 | Wts Llc | Digital fluid heating system |
US11803500B1 (en) * | 2018-07-31 | 2023-10-31 | Faith Technologies, Inc. | Peer-to-peer DC or AC distribution network |
US20200202351A1 (en) * | 2018-12-19 | 2020-06-25 | Francotyp-Postalia Gmbh | Service payment system and method |
Also Published As
Publication number | Publication date |
---|---|
WO2014113481A1 (en) | 2014-07-24 |
US20140200717A1 (en) | 2014-07-17 |
US10437209B2 (en) | 2019-10-08 |
US9488968B2 (en) | 2016-11-08 |
US20170255172A1 (en) | 2017-09-07 |
US20140196761A1 (en) | 2014-07-17 |
US9471050B2 (en) | 2016-10-18 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US10437209B2 (en) | Solar tracker and related methods, devices, and systems | |
US10261536B2 (en) | Systems and methods for optimizing microgrid power generation and management with predictive modeling | |
US9979198B2 (en) | Systems and methods for microgrid power generation and management | |
EP2599183B1 (en) | Dynamic distributed power grid control system | |
US8825218B2 (en) | Dynamic distributed power grid control system | |
US7962247B2 (en) | Computer implemented systems and methods for start-up, calibration and troubleshooting of an installed renewable energy system | |
US20170147025A1 (en) | Systems and methods for microgrid power generation management with selective disconnect | |
US20120029720A1 (en) | Dynamic distributed power grid control system | |
Dykes et al. | Opportunities for research and development of hybrid power plants | |
Sakib et al. | A qualitative study on the United States internet of energy: a step towards computational sustainability | |
Kowli et al. | Supporting wind generation deployment with demand response | |
Nixon et al. | Analysis of standalone solar streetlights for improved energy access in displaced settlements | |
Liu et al. | Bi-level fuzzy stochastic expectation modelling and optimization for energy storage systems planning in virtual power plants | |
Nasserddine et al. | Internet of things integration in renewable energy systems | |
Wang et al. | Grid-aware placement of datacenters and wind farms | |
Njoka et al. | Evaluation of IoT-based remote monitoring systems for stand-alone solar PV installations in Kenya | |
Shaver | Implementation of a DC Microgrid | |
Parsons et al. | Variability of power from large-scale solar photovoltaic scenarios in the state of Gujarat | |
Kabouris et al. | Computational environment to investigate wind integration into small autonomous systems | |
Vijayalakshmi et al. | AI and IoT in Improving Resilience of Smart Energy Infrastructure | |
Kroposki et al. | Grid Integration Science | |
Meagher et al. | Secure Automated Microgrid Energy System | |
Meagher et al. | Secure Automated Microgrid Energy System (SAMES) W912HQ-13-C-0064 DEMONSTRATION PLAN |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: QUESTAR ENERGY SYSTEMS, INC., WASHINGTON Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:TILLEY, HERBERT ALAN;ROBINSON, GREGORY WILLIAM;MCKENZIE, EDWIN EUGENE;SIGNING DATES FROM 20130710 TO 20130711;REEL/FRAME:030884/0488 |
|
AS | Assignment |
Owner name: WOVN, INC., WASHINGTON Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:QUESTAR ENERGY SYSTEMS, INC.;REEL/FRAME:034725/0053 Effective date: 20140811 |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
AS | Assignment |
Owner name: DRIFT MARKETPLACE, INC., WASHINGTON Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:WOVN, INC.;REEL/FRAME:043523/0898 Effective date: 20170517 |
|
FEPP | Fee payment procedure |
Free format text: MAINTENANCE FEE REMINDER MAILED (ORIGINAL EVENT CODE: REM.); ENTITY STATUS OF PATENT OWNER: SMALL ENTITY |
|
LAPS | Lapse for failure to pay maintenance fees |
Free format text: PATENT EXPIRED FOR FAILURE TO PAY MAINTENANCE FEES (ORIGINAL EVENT CODE: EXP.); ENTITY STATUS OF PATENT OWNER: SMALL ENTITY |
|
STCH | Information on status: patent discontinuation |
Free format text: PATENT EXPIRED DUE TO NONPAYMENT OF MAINTENANCE FEES UNDER 37 CFR 1.362 |
|
FP | Lapsed due to failure to pay maintenance fee |
Effective date: 20201108 |