Difference between revisions of "Building monitoring"
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
| + | ==Scripts== | ||
| + | #Java scripts harvest data directly from Modbus | ||
| + | #Perl scripts collect this data and put it in the Postgress database "energy" under the table 'electrical_energy' | ||
| + | **electrical energy | ||
| + | ***area - what building. | ||
| + | ***preal - kW hours for that instant. | ||
| + | ***date - date of harvest. | ||
| + | #A final perl script accesses this data and generates a .png graph using the Google graph API | ||
| + | #The images generated (day, week, month, year) are put in a html frame on a [http://proto.cs.earlham.edu/~energy/production/eDisplay/ page] to display the data. | ||
| + | |||
==Building IP== | ==Building IP== | ||
*159.28.165.<strong>100</strong> - Bundy* | *159.28.165.<strong>100</strong> - Bundy* | ||
Revision as of 13:49, 25 March 2012
Scripts
- Java scripts harvest data directly from Modbus
- Perl scripts collect this data and put it in the Postgress database "energy" under the table 'electrical_energy'
- electrical energy
- area - what building.
- preal - kW hours for that instant.
- date - date of harvest.
- electrical energy
- A final perl script accesses this data and generates a .png graph using the Google graph API
- The images generated (day, week, month, year) are put in a html frame on a page to display the data.
Building IP
- 159.28.165.100 - Bundy*
- 159.28.165.101 - Barrett
- 159.28.165.102 - Wilson
- 159.28.165.103 - Warren
- 159.28.165.104 - Unknown
- 159.28.165.105 - Unknown
- * - not yet set up
