the 2nd update!!!
Rack monitor for monitoring Rack controller hearbeat, and relays rack controller <update> publish mqqt topics. relaying is important when rack controller ethernet got disconnected with any reason, The subscriber (high leve apps) needs to get updated (fans, temps, humids, controller status) to know Controller is dead or just cripple. . I put extra precaution due on my last experience with dead PSU on my first rack controller model( no MQTT, just web based and UDP update).
the other important is rack controller is monitored by rack monitor, and get published to let know the apps subscriber status of rack controller (including monitor
using wireless to link between rack controller and monitor. ideally.. monitor can be put every corner in wireless coverage.
I am using fake NRF24L+ (SR24 actually with more power consumption and less sensitivity), this will be replaced when needed more wireless coverage with real RFF24L+
Populated with 1500XL APC UPS
lower intake filter with frame
overal coding is 98% done, need tweaking to handle humidity to no let buzzer go off with false alarm
I am populating the closed rack now...
the life-saver, pyhton rules...:
I create simple python-mqtt to monitor all health status with updated information , better than doing in bash and C/C++ when needed to create something quick.
the output:
Updated time: 2015-08-12 10:50:52.370450
TEMPERATURE
REAR LOWER : 33.88 C
REAR UPPER : 33.50 C
EXHAUST : 34.00 C
FRONT LOWER: 28.44 C
FRONT UPPER: 28.44 C
AMBIENT : 28.31 C
HUMIDITY
FRONT : 47.80 Percents
REAT : 39.50 Percents
FAN RPMS
UPPER LEFT : 1470 RPM
UPPER MID : 1530 RPM
UPPER RIGHT: 1680 RPM
LOWER LEFT : 1922 RPM
LOWER MID : 1890 RPM
LOWER RIGHT: 2139 RPM
enjoy and to be continued...
Rack monitor for monitoring Rack controller hearbeat, and relays rack controller <update> publish mqqt topics. relaying is important when rack controller ethernet got disconnected with any reason, The subscriber (high leve apps) needs to get updated (fans, temps, humids, controller status) to know Controller is dead or just cripple. . I put extra precaution due on my last experience with dead PSU on my first rack controller model( no MQTT, just web based and UDP update).
the other important is rack controller is monitored by rack monitor, and get published to let know the apps subscriber status of rack controller (including monitor
using wireless to link between rack controller and monitor. ideally.. monitor can be put every corner in wireless coverage.
I am using fake NRF24L+ (SR24 actually with more power consumption and less sensitivity), this will be replaced when needed more wireless coverage with real RFF24L+
Populated with 1500XL APC UPS
lower intake filter with frame
overal coding is 98% done, need tweaking to handle humidity to no let buzzer go off with false alarm
I am populating the closed rack now...
the life-saver, pyhton rules...:
I create simple python-mqtt to monitor all health status with updated information , better than doing in bash and C/C++ when needed to create something quick.
the output:
Updated time: 2015-08-12 10:50:52.370450
TEMPERATURE
REAR LOWER : 33.88 C
REAR UPPER : 33.50 C
EXHAUST : 34.00 C
FRONT LOWER: 28.44 C
FRONT UPPER: 28.44 C
AMBIENT : 28.31 C
HUMIDITY
FRONT : 47.80 Percents
REAT : 39.50 Percents
FAN RPMS
UPPER LEFT : 1470 RPM
UPPER MID : 1530 RPM
UPPER RIGHT: 1680 RPM
LOWER LEFT : 1922 RPM
LOWER MID : 1890 RPM
LOWER RIGHT: 2139 RPM
enjoy and to be continued...