Whats there to play with, you want them to be up as long as possible. Get it hashing and then dont touch that mofo unless you have to!
I'm working on a small code change to enable the unit to log a small hashing data set to a database and set up alerts on it.
Without SSH access to it, I can't do that and test the wereabouts .. here's a sample output ..
{"CG_Uptime":5952,"MHS_Avg":4704506.04,"MHS_5s":4713962.81,"MHS_1m":4748876.82,"MHS_5m":4752360.92,"MHS_15m":4746689.88,"MHS_Now":"4562160",
"DegC_In":"27","DegC_TopOut":"77","DegC_BotOut":"73","UnitID":"SP3x","UnitSN":"FL14","UnitFW":"2.3.44","UnitMA":"D0:39:72:3D:1C:12","Unit_Uptime":593581,
"FreeMem":"368","PSUVolt_Top":"211","PSUVolt_Bot":"211","FAN":"80","VST":"670","VSB":"670","VMAX":"750","AC_TOP":"1295","AC_BOT":"1325","DC_AMP":"150",
"PSUWall_Top":"1440","PSUWatt_Top":"1296","PSUWall_Bot":"1488","PSUWatt_Bot":"1324","UnitCPULd_0":0.58,"UnitCPULd_1":0.72,"UnitCPULd_2":0.75}
I'm lnking the local hashrate value, with the detected pool hashrate and 1m-15m averages, with the line voltage, amperage at the wall for each PSU, intake and otput temperatures. The CPU load is there so that the script logging the data does not affect the computing capacity more than it should .. (I sanitized my serial number)
I hope that some hosting companies will use it to monitor all their SPT miners, they can even bill by the recorded KWh .. or as a logging tool to enforce Service Level Agreements
if not, I'll still make good use of this. There's a lot to play with .. especially if you want to process SP10, SP20 and SP30 data with the same code.