Difference between revisions of "Building monitoring"

From Earlham CS Department
Jump to navigation Jump to search
(Displaying Energy Scripts Outline)
(Building IP)
Line 10: Line 10:
  
 
==Building IP==
 
==Building IP==
*159.28.165.<strong>100</strong> - Bundy*
+
*159.28.165.<strong>100</strong> - Bundy**
 
*159.28.165.<strong>101</strong> - Barrett
 
*159.28.165.<strong>101</strong> - Barrett
 
*159.28.165.<strong>102</strong> - Wilson
 
*159.28.165.<strong>102</strong> - Wilson
 
*159.28.165.<strong>103</strong> - Warren
 
*159.28.165.<strong>103</strong> - Warren
*159.28.165.<strong>104</strong> - Unknown
+
*159.28.165.<strong>104</strong> - Mills**
*159.28.165.<strong>105</strong> - Unknown
+
*159.28.165.<strong>105</strong> - Olvey Andis*
: * - not yet set up
+
: * - box in place, EGX is not
 +
: ** - no box or egx in place

Revision as of 13:15, 25 March 2012

Displaying Energy Scripts Outline

  1. Java scripts harvest data directly from Modbus
  2. Perl scripts collect this data and put it in the Postgress database "energy" under the table "electrical_energy"
    electrical_energy attributes:
    area - what building.
    preal - kW hours for that instant.
    date - date of harvest.
  3. A final perl script accesses this data and generates a .png graph using the Google graph API
  4. 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 - Mills**
  • 159.28.165.105 - Olvey Andis*
* - box in place, EGX is not
** - no box or egx in place