The present invention relates to systems and methods for designing solar power equipment and, more particularly, to computerized systems for designing solar power equipment customized for a particular use and location.
Solar power equipment must be specified to meet certain load requirements and to operate within given parameters in a particular location. The need exists to automate the process of specifying or designing solar power equipment.
The present invention may be embodied as a design system for generating a power equipment proposal for a particular location, comprising an insolation database, a load database, and a processing system. The insolation database comprises insolation values associated with a plurality of geographic data points. The load database associates appropriate power equipment with load requirements. The processing system generates at least one power equipment proposal based on load requirements generated from the insolation database based on the insolation values associated with a geographic data point closest to the particular location and solar power equipment appropriately selected from the load database based on the load requirements generated from the insolation database.
The present invention may also be embodied as a method of generating a power equipment proposal for a particular location comprising the following steps. An insolation database is provided that comprises insolation values associated with a plurality of geographic data points. A load database is provided that associates appropriate solar power equipment with load requirements. A geographic data point closest to the particular location is selected. Load requirements are generated from the insolation database based on the insolation values associated with the selected geographic data point. A list of power equipment appropriate for the load requirements is generated from the load database. At least one power equipment proposal is generated based on the load requirements generated from the insolation database and the list of power equipment generated from the load database.
The present invention may further be embodied as a design system for generating a power equipment proposal for a particular location comprising a user interface, an insolation database, a load database, and a processing system. The user interface allows entry of system specifications. The insolation database comprises insolation values associated with a plurality of geographic data points. The load database associates appropriate power equipment with load requirements. The processing system for generating a plurality of power equipment proposals based on load requirements generated from the insolation database based on the insolation values associated with a geographic data point closest to the particular location, solar power equipment selected from the load database based on the load requirements generated from the insolation database, and the system specifications.
Referring initially to
The back-end system 30 and the front-end system 32 may be implemented entirely on a single computer or may be distributed across a plurality of computers connected by a network (not shown). If used, the network may be a local area network or may be a distributed network such as the Internet. The network may be wired or wireless.
The back-end system 30 may be implemented as a database server application capable of storing data and performing calculations based on stored data and data collected by the front-end system 32. In this case, the front-end system 32 will be typically be implemented as a remote computer running a standalone software application capable of generating the user interface 50 and transmitting data to the back-end system 30. Alternatively, the back-end system 30 may be implemented as a web server capable of storing data, generating the user interface 50, and performing calculations based on stored data and data collected through the user interface 50. In this case, the front-end system 32 will typically be implemented as what is commonly referred to as a “thin client” or browser capable of running the user interface 50 as generated by the back-end system 30. And as generally discussed above, both the back-end system 20 and the front-end system 20 may be implemented as a software application running on a single computing device.
One or more parts of the first example design system 20 will typically include or be embodied as one or more applications running an operating system such as Microsoft Windows, Unix, and/or Apple OS X. Such operating systems typically run on a computing system such as a workstation, a server, a personal computer, and/or a laptop computer. Alternatively, one or more parts of the first example design system may include or be embodied as an application running on a personal digital assistant (PDA), tablet, or cell-phone-based computing device running an operating system such as Apple iOS or Google Android.
The insolation data stored in the insolation database 42 is or may be calculated from publicly available databases such as data published by the NASA Langly Research Center Atmospheric Science Data Center POWER Project (the NASA SSE database). The NASA SSE database contains raw insolation data for geographic data points corresponding to each 1° of latitude and longitude in the United States (including Alaska and Hawaii). The example insolation database 42 was generated by calculating for each data point in the NASA SSE database minimum and average Insolation over a 22-year period. These minimum and average insolation values are stored for each data point in the example insolation database 42.
More specifically, the example insolation data stored in the insolation database was calculated as follows. First, data is obtained from the the NASA LARC data online website (http://eosweb.larc.nasa.gov/cgi-bin/sse/grid.cgi?email=) by navigating to the page where the latitude and longitude of a particular geographical site can be entered. This will require entry of an email address and password or, if you are new to the website, you may be required to create a new account. The correct lat/long (taken from Google Maps in the User Input portion) is then entered, and the website displays a page with many categories and their corresponding list boxes. Find the category “Parameters for Tilted Solar Panels” and select both “Radiation on equator-pointed tilted surfaces” and Minimum radiation for equator-pointed tilted surfaces” from the list box on the right. To highlight multiple selections from a list box, press and hold Ctrl while clicking on each selection. Press “Submit” at the bottom of the page. The website now displays a page containing two tables. The insolation data is derived from one row from each table. In particular, the insolation data is derived from the row that corresponds to the tilt angle of the entered latitude plus 15°. For example, if you enter “48” for latitude, you are interested in the row identified as “Tilt 63”. This row will always be the fourth from the bottom. An example of a representation of a raw data table containing insolation data collected for Seattle, Wash. (47N, 123W) is shown in
As will be described in further detail below, the average radiation value is used for Standard and Economy systems, while the minimum radiation value is used for Premium systems. The solar panel industry uses the term “insolation” to refer to substantially the same physical phenomena referred to in the tables as “radiation”.
The example load database 44 contains data associated with a plurality of configurations of battery banks, photo-voltaic (PV) panel array modules, and voltages. The load that a given battery bank could provide less certain predetermined system losses was calculated. The load that a given PV panel array could support less certain predetermined system losses was calculated for each solar resource. The smaller of these two load values corresponded to the minimum that a given system comprising a particular combination of battery bank and PV panel array could support. This process was repeated for each available voltage (e.g., 12V DC, 24V DC, 48V DC). The load data is calculated for a plurality of predetermined systems having different combinations of battery bank and PV panel array to provide an incremental increase in supportable loads.
An example of a Load Table containing load data calculated for a plurality of solar systems (e.g., combinations of battery banks and PV arrays) falling into Standard, Economy, and Premium categories is shown in
Referring now to
At step 126 in
At step 130 in
At step 140 in
Referring now to
Referring now to
The user enters a description of each load in the Description field 230a (e.g., “Camera”), a quantity in the load Quantity field 232a (e.g., “2”), a power value in Watts in the load Watts field 234a (e.g., “10”), the number of hours in the day the load is expected to operate in the load Hours/Day field 236a (e.g., “24”), and a watt-hour per day value in the load Wh/Day field 238a (e.g., “480”). The user then identifies a voltage associated with the load by selecting one value (e.g., “12 V DC”) from a plurality of voltages (e.g., “12 V DC”, “24 V DC”, and “48 V DC”) in the System Voltage dropdown box 240. As depicted in
The display fields 250-256 indicate running totals generated for each of defined values based on the load values input in using the input fields 230-238. The user cannot alter or enter data in the display fields 250-256.
Commonly, a given project requires that multiple loads be powered. In this case, the user may click the ADD button 242, and a second configuration of the load panel is generated as depicted in
At this point, the user is presented with a select solution panel as depicted in
The Premium, Standard, and Economy areas 262, 264, and 266 all contain the same information for each of three different solutions. Each of these areas 262, 264, and 266 contains a System display fields 280a, 280b, and 280c, a Days of Autonomy display field 282a, 282b, and 282c, a Voltage display field 284a, 284b, and 284c, a PV Array Size field 286a, 286b, and 286c, a Battery Bank Size display field 288a, 288b, and 288c, a PWM or MPPT display field 290a, 290b, and 290c, and a Warranty display field 292a, 292b, and 292c. The values and/or data displayed in these display fields is determined by the characteristics of the system defined in the System display fields and cannot be altered by the user. In the example depicted in
Referring now to
The interface then presents a questions/comments panel as depicted in
Referring now to
Like the first example method described above with respect to
Based on the location data entered at step 420, the processing system 40 determines at step 422 the nearest geographic data point associated with the location data. At step 424, the processing system 40 determines from the nearest geographic data point, the insolation data stored in the insolation database 42, and the facility data (e.g., image data, direction data, and/or angle data) one or more insolation values associated with a physical location associated with the location data. As described above, the example processing system 40 will typically determine at least average insolation and minimum insolation for the physical location associated with the location data. The insolation value(s) associated with the location data are temporarily stored for later use as will be described in further detail below.
At step 426 in
At step 430 in
At step 440 in
A first example of the operation of a system incorporating the principles of the present invention can be illustrated by representing the differences among the Premium, Standard, and Economy solutions at one location for two different loads. The average and minimum insolation values for Phoenix, Ariz. are 5.08 Peak Sun-hours and 4.01 Peak Sun-hours, respectively. For a first load of 10 Watts operating at 12 Volts DC for 24 hours/day and a second load of 40 Watts operating at 12 Volts DC for 24 hours/day, the following Premium, Standard, and Economy solutions are obtained:
A second example of the operation of a system incorporating the principles of the present invention can be illustrated by representing the differences among the Premium, Standard, and Economy solutions at two locations for the same load. The average and minimum insolation values for Phoenix, Ariz. are 5.08 Peak Sun-hours and 4.01 Peak Sun-hours, respectively, while the average and minimum insolation values for Bowdon, N. Dak. are 2.17 Peak Sun-hours and 1.73 Peak Sun-hours, respectively. For a load of 10 Watts operating at 12 Volts DC for 24 hours/day, the following Premium, Standard, and Economy solutions are obtained:
The present invention may be embodied as an automated design system tool for generating a power equipment proposal for a particular location, comprised of an insolation database with insolation values associated with a plurality of geographic data points, a load database associating appropriate power equipment with load requirements including duty cycles for the equipment, and a processing system which takes into account the periods of poor weather and corresponding low insolation to generate a power equipment proposal. The power equipment proposal will thus typically include three solutions based upon the required level of system reliability or up time as defined below.
The economy level design is for non-essential loads that can tolerate periodic outages based on seasonal weather changes which result in low levels of insolation.
The standard level design uses average insolation or weather patterns and is for loads that can tolerate occasional and/or rare outages based on extreme and unusual weather changes.
The premium level design uses worst case insolation or weather patterns over at least 20 years of data and is for critical loads that cannot tolerate any outages. The premium level design is thus designed for 24-7-365 operations.
The proposal is generated based on load requirements, the insolation database based on the insolation values associated with a geographic data point closest to the particular location, the periods of poor weather and corresponding low insolation, the level of system reliability required, and solar power equipment appropriate based on the load requirements generated from the insolation database.
The present invention may also be embodied as a design system for generating a power equipment proposal for a particular location comprising a user interface, an insolation database, a load database, and a processing system. The user interface allows entry of system specifications. The insolation database comprises insolation values associated with a plurality of geographic data points. The load database associates appropriate power equipment with load requirements. The processing system for generating a plurality of power equipment proposals based on load requirements generated from the insolation database based on the insolation values associated with a geographic data point closest to the particular location, and takes into account the periods of poor weather and corresponding low insolation and selects the solar power equipment from the load database based on the load requirements generated from the insolation database, and the system specifications.
This application claims benefit of U.S. Provisional Patent Application Ser. No. 61/547,727, filed Oct. 16, 2011. The contents of all applications listed above are incorporated herein by reference.
Number | Name | Date | Kind |
---|---|---|---|
3944837 | Meyers et al. | Mar 1976 | A |
4063963 | Bond, Jr. | Dec 1977 | A |
4262209 | Berner | Apr 1981 | A |
4731547 | Alenduff et al. | Mar 1988 | A |
4943763 | Bobry | Jul 1990 | A |
4975649 | Bobry | Dec 1990 | A |
5010469 | Bobry | Apr 1991 | A |
5029285 | Bobry | Jul 1991 | A |
5228924 | Barker et al. | Jul 1993 | A |
5302858 | Folts | Apr 1994 | A |
5400005 | Bobry | Mar 1995 | A |
5410720 | Osterman | Apr 1995 | A |
5457377 | Jonsson | Oct 1995 | A |
5532525 | Kaiser et al. | Jul 1996 | A |
5638244 | Mekanik et al. | Jun 1997 | A |
5642002 | Mekanik et al. | Jun 1997 | A |
5739595 | Mekanik et al. | Apr 1998 | A |
5760495 | Mekanik | Jun 1998 | A |
5856712 | Suzuki et al. | Jan 1999 | A |
5892431 | Osterman | Apr 1999 | A |
5949662 | Boldin et al. | Sep 1999 | A |
5961604 | Anderson et al. | Oct 1999 | A |
5982645 | Levran et al. | Nov 1999 | A |
5994793 | Bobry | Nov 1999 | A |
6014015 | Thorne et al. | Jan 2000 | A |
6093885 | Takehara et al. | Jul 2000 | A |
6198177 | Mao et al. | Mar 2001 | B1 |
6201371 | Kawabe et al. | Mar 2001 | B1 |
6288916 | Liu et al. | Sep 2001 | B1 |
6348782 | Oughton, Jr. et al. | Feb 2002 | B1 |
6483730 | Johnson, Jr. | Nov 2002 | B2 |
6486399 | Armstrong et al. | Nov 2002 | B1 |
6542791 | Perez | Apr 2003 | B1 |
6602627 | Liu et al. | Aug 2003 | B2 |
6605879 | Wade et al. | Aug 2003 | B2 |
6841971 | Spee et al. | Jan 2005 | B1 |
6933626 | Oughton, Jr. | Aug 2005 | B2 |
7040920 | Johnson, Jr. et al. | May 2006 | B2 |
7050312 | Tracy et al. | May 2006 | B2 |
7182632 | Johnson, Jr. et al. | Feb 2007 | B1 |
7449798 | Suzuki et al. | Nov 2008 | B2 |
7746669 | Falk | Jun 2010 | B2 |
RE43572 | West | Aug 2012 | E |
20030038610 | Munshi et al. | Feb 2003 | A1 |
20030047209 | Yanai et al. | Mar 2003 | A1 |
20030117822 | Stamenic et al. | Jun 2003 | A1 |
20070194759 | Shimizu et al. | Aug 2007 | A1 |
20070199336 | Tantot | Aug 2007 | A1 |
20080197122 | Gober | Aug 2008 | A1 |
20090194145 | Kribus et al. | Aug 2009 | A1 |
20100017045 | Nesler et al. | Jan 2010 | A1 |
20100109601 | Coyle et al. | May 2010 | A1 |
20100169008 | Niwa et al. | Jul 2010 | A1 |
20100279455 | Seemann | Nov 2010 | A1 |
20100318297 | Herzig et al. | Dec 2010 | A1 |
20110068624 | Dibachi et al. | Mar 2011 | A1 |
20110100004 | Al-Mazeedi | May 2011 | A1 |
20110114079 | Heckendorn | May 2011 | A1 |
20110198932 | Le et al. | Aug 2011 | A1 |
20110204720 | Ruiz et al. | Aug 2011 | A1 |
20110291608 | Shimura et al. | Dec 2011 | A1 |
20120158362 | Vandevelde et al. | Jun 2012 | A1 |
20120188806 | Tamura et al. | Jul 2012 | A1 |
20130081396 | Kuo | Apr 2013 | A1 |
Number | Date | Country |
---|---|---|
9520294 | Dec 1995 | AU |
1265231 | Jan 1990 | CA |
2033685 | Oct 1991 | CA |
2036296 | Nov 1991 | CA |
1297546 | Mar 1992 | CA |
2086897 | Jul 1993 | CA |
2028269 | Jan 2000 | CA |
2149845 | Feb 2000 | CA |
2403888 | Sep 2001 | CA |
2168520 | Apr 2003 | CA |
2504101 | Jun 2005 | CA |
2713017 | Jul 2009 | CA |
9302756.7 | Feb 1993 | DE |
0827254 | Nov 2005 | EP |
2355350 | Apr 2001 | GB |
61165051 | Oct 1986 | JP |
2000023365 | Jan 2000 | JP |
2001190035 | Jul 2001 | JP |
2004296547 | Oct 2004 | JP |
3142899 | Jul 2008 | JP |
2019990000402 | Jan 1999 | KR |
1020070004478 | Jan 2007 | KR |
1020070078524 | Aug 2007 | KR |
2007129808 | Nov 2007 | WO |
0931273 | Feb 1993 | ZA |
Entry |
---|
Boehringer, “Self-adapting dc Converter for Solar Spacecraft Power Supply,” IEEE Transactions on Aerospace and Electronic Systems, vol. AES-4, No. 1, Jan. 1968, pp. 102-111. |
Enslin, Wolf, Snyman, Swiegers, “Integrated Photovoltaic Maximum Power Point Tracking Converter”, IEEE Transactions on Industrial Electronics, vol. 44, No. 6, Dec. 1997, pp. 769-773. |
Enslin, “Maximum Power Point Tracking: A Cost Saving Necessity in Solar Energy Systems” Renewable Energy vol. 2, No. 6, 1992, pp. 543-549. |
Schoeman, Van Wyk, “A Simplified Maximal Power Controller for Terrestrial Photovoltaic Panel Arrays”, 13th Annual IEEE Power Electronics Specialists Conference (PESC '82 Record), Jun. 1982, pp. 361-367, Cambridge, MA. |
Snyman, Enslin, “An Experimental Evaluation of MPPT Converter Topologies for PV Installations”, Renewable Energy, vol. 3, No. 8, 1993, pp. 841-848. |
PCT International Search Report, International Application No. PCT/US2011/056597, Jan. 11, 2012, 12 pages. |
PCT International Search Report, International Application No. PCT/US2009/031836, Aug. 18, 2009, 12 pages. |
PCT International Search Report, International Application No. PCT/US2010/032832, Dec. 2, 2010, 10 pages. |
Number | Date | Country | |
---|---|---|---|
61547727 | Oct 2011 | US |