Building monitoring: Difference between revisions
Jump to navigation
Jump to search
| 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> - | *159.28.165.<strong>104</strong> - Mills** | ||
*159.28.165.<strong>105</strong> - | *159.28.165.<strong>105</strong> - Olvey Andis* | ||
: * - not | : * - box in place, EGX is not | ||
: ** - no box or egx in place | |||
Revision as of 18:15, 25 March 2012
Displaying Energy Scripts Outline
- 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 attributes:
- area - what building.
- preal - kW hours for that instant.
- date - date of harvest.
- electrical_energy attributes:
- 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 - Mills**
- 159.28.165.105 - Olvey Andis*
- * - box in place, EGX is not
- ** - no box or egx in place