Hi, I just got at work an MGE UPS Comet EX RT 7 and I can communicate fine with it through mge-shut, it detects correctly when on battery. I am using Nut 2.0.3 on Linux (RHEL 3). I am trying to simulate a low battery condition to test my shutdown procedure by setting lowbatt to 98%: driver.parameter.lowbatt: 98 but the ups reaches this value, goes to 97% and still no LB. I tried to change, in the ups firmware, the threshold for pre-alarm to 98% and the ups started its shutdown sequence however nut would still not get LB in ups.status so no shutdown. Any ideas I do not get the LB status ? I cannot wait for the batteries to reach 20% charge to see if it works that way as the load is very low, I would have to wait very long :) NB: to Arnaud, the model is not correctly detected, I get a "null" model name: Detected (null) [1C0F47062] on /dev/ttyS0 Philippe
salut Philippe, 2006/3/31, Philippe Marzouk:> Hi, > > I just got at work an MGE UPS Comet EX RT 7 and I can communicate fine > with it through mge-shut, it detects correctly when on battery. > > I am using Nut 2.0.3 on Linux (RHEL 3). > > I am trying to simulate a low battery condition to test my shutdown > procedure by setting lowbatt to 98%: > > driver.parameter.lowbatt: 98 > > but the ups reaches this value, goes to 97% and still no LB. > > I tried to change, in the ups firmware, the threshold for pre-alarm to > 98% and the ups started its shutdown sequence however nut would still > not get LB in ups.status so no shutdown. > > Any ideas I do not get the LB status ? > > I cannot wait for the batteries to reach 20% charge to see if it works > that way as the load is very low, I would have to wait very long :) > > NB: to Arnaud, the model is not correctly detected, I get a "null" model > name: > > Detected (null) [1C0F47062] on /dev/ttyS0thanks to send me a verbose startup trace (ie "mge-shut -DDDDD ..."), and 2 upsc outputs (one when OB and one when OL). I wonder if this issue isn't due to a low charge on output, but it's however strange. Note that you can meanwhile use the upssched mecanism to force the shutdown on a battery.charge or battery.runtime (or whatever) criteria. If you need, I can provide such a script... Arnaud -- Linux / Unix Expert - MGE UPS SYSTEMS - R&D Dpt Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://people.debian.org/~aquette/ OpenSource Developer - http://arnaud.quette.free.fr/
2006/3/31, Philippe Marzouk <phil@ozigo.org>:> Hi, > > I just got at work an MGE UPS Comet EX RT 7 and I can communicate fine > with it through mge-shut, it detects correctly when on battery. > > I am using Nut 2.0.3 on Linux (RHEL 3). > ... > driver.parameter.lowbatt: 98 > > but the ups reaches this value, goes to 97% and still no LB. > > I tried to change, in the ups firmware, the threshold for pre-alarm to > 98% and the ups started its shutdown sequence however nut would still > not get LB in ups.status so no shutdown. > > Any ideas I do not get the LB status ?this was a lack: LB can be detected through 2 HID paths, of which 1 was missing (in shut, not newhidups). Fixed and validated.> NB: to Arnaud, the model is not correctly detected, I get a "null" model > name: > > Detected (null) [1C0F47062] on /dev/ttyS0Fixed too. Added in trunk and Testing, so this will be available in 2.0.4. Thanks for the report. Arnaud -- Linux / Unix Expert - MGE UPS SYSTEMS - R&D Dpt Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://people.debian.org/~aquette/ OpenSource Developer - http://arnaud.quette.free.fr/