It all looks like it's coming together. I am beginning to be able to decipher all the messages.
It appears to be reading the correct values for online, nominal line voltage, and battery voltages, and load, which it did not do before. Time to run it down, and see what I get, perhaps it's time to vacuum again :) here is an excerpt of the type of messages I get from running the driver. 1.173305 send_to_all: SETINFO input.voltage.nominal "120" 1.173312 send_to_all: SETINFO battery.voltage.nominal "36" 1.173319 send_to_all: SETINFO ups.debug.load_banks "0" 1.173325 send_to_all: SETINFO ups.delay.shutdown "64" 1.173332 send_to_all: SETFLAGS ups.delay.shutdown RW STRING 1.173337 send_to_all: SETAUX ups.delay.shutdown 3 1.173344 send_to_all: ADDCMD shutdown.return On Mon, 2010-02-01 at 08:58 -0500, Charles Lepple wrote: > On Jan 31, 2010, at 11:29 PM, chance fulton wrote: > > > Load added at 60 > > > > I plugged a CRT TV in, and the load meter on the front spikes and > > drops, > > I really don't have anything else less noisy to plug into it for more > > load. > > > > I can test that more in the morning though when nobody cares about > > noise. > > > > Load removed at 98 > > > > Power fail at 120 > > Restored at 169 > > > > Built from the 3004 protocol branch. > > I will take another look at the load stuff tonight, but I just > committed r2301 which should try some more status decoding. > > If you can run the battery down to the point where PowerAlert would > start a shutdown sequence, that would also be a useful log (so we know > for sure what the "Low Battery" flag is). > > - Charles _______________________________________________ Nut-upsdev mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/nut-upsdev
