Petr Kubánek
2011-Apr-25 09:20 UTC
[Nut-upsuser] [HCL] Numeric 3000 SW supported by blazer_ser
Hi, Numeric 3000 SW seems to be supported. Please find entries below. I did not go through complete shut-down sequence while on site (Bloemfontein, RSA), but recent power failure (while I was already at Europe) confirms it works as expected. - Numeric Digital 3000 SW, seems to be some India based manufacturer upsc watcher-ups battery.voltage: 81.70 battery.voltage.nominal: 72.0 beeper.status: enabled device.mfr: NUMERIC device.model: 3000 SW device.type: ups driver.name: blazer_ser driver.parameter.pollinterval: 2 driver.parameter.port: /dev/ttyUSB0 driver.version: 2.4.3 driver.version.internal: 1.51 input.current.nominal: 13.0 input.frequency: 50.0 input.frequency.nominal: 50 input.voltage: 221.3 input.voltage.fault: 221.3 input.voltage.nominal: 230 output.voltage: 219.6 ups.delay.shutdown: 30 ups.delay.start: 180 ups.firmware: VER 3.02 ups.load: 11 ups.mfr: NUMERIC ups.model: 3000 SW ups.status: OL ups.temperature: 18.0 ups.type: offline / line interactive upsrw watcher-ups (nothing show up) upscmd -l watcher-ups Instant commands supported on UPS [watcher-ups]: beeper.toggle - Toggle the UPS beeper load.off - Turn off the load immediately load.on - Turn on the load immediately shutdown.return - Turn off the load and return when power is back shutdown.stayoff - Turn off the load and remain off shutdown.stop - Stop a shutdown in progress test.battery.start - Start a battery test test.battery.start.deep - Start a deep battery test test.battery.start.quick - Start a quick battery test test.battery.stop - Stop the battery test Shutdown test (Ubuntu server 10.04.2 LTS): Apr 24 18:10:29 watcher1 upsmon[1684]: UPS watcher-ups at localhost on battery Apr 24 18:17:01 watcher1 CRON[20146]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 24 18:34:49 watcher1 upsmon[1684]: UPS watcher-ups at localhost battery is low Apr 24 18:35:09 watcher1 upsmon[1684]: Giving up on the master for UPS [watcher-ups at localhost] Apr 24 18:35:09 watcher1 upsmon[1684]: Executing automatic power-fail shutdown Apr 24 18:35:09 watcher1 upsmon[1684]: Auto logout and shutdown proceeding Apr 24 18:35:14 watcher1 init: idmapd main process (643) killed by TERM signal Apr 24 18:35:14 watcher1 init: tty4 main process (949) killed by TERM signal Apr 24 18:35:14 watcher1 init: tty5 main process (955) killed by TERM signal Apr 24 18:35:14 watcher1 init: tty2 main process (968) killed by TERM signal Apr 24 18:35:14 watcher1 init: tty3 main process (969) killed by TERM signal Apr 24 18:35:14 watcher1 init: tty6 main process (972) killed by TERM signal Apr 24 18:35:14 watcher1 init: cron main process (975) killed by TERM signal Apr 24 18:35:14 watcher1 init: tty1 main process (1932) killed by TERM signal Apr 24 18:35:14 watcher1 acpid: exiting Apr 24 18:35:15 watcher1 kernel: Kernel logging (proc) stopped. Apr 24 20:19:22 watcher1 kernel: imklog 4.2.0, log source = /proc/kmsg started. Apr 24 20:19:22 watcher1 rsyslogd: [origin software="rsyslogd" swVersion="4.2.0" x-pid="670" x-info="http://www.rsyslog.com"] (re)start http://www.numericups.com/default.aspx?pageid=c58749e9-aac7-468e-9743-9f56df899646 Thanks a lot. Petr Kub?nek http://rts2.org
Arnaud Quette
2011-Apr-27 09:52 UTC
[Nut-upsuser] [HCL] Numeric 3000 SW supported by blazer_ser
Hi Petr, 2011/4/25 Petr Kub?nek <petr at kubanek.net>> Hi, > > Numeric 3000 SW seems to be supported. Please find entries below. I did > not go through complete shut-down sequence while on site (Bloemfontein, > RSA), but recent power failure (while I was already at Europe) confirms > it works as expected. > > - Numeric Digital 3000 SW, seems to be some India based manufacturer > > upsc watcher-ups > > battery.voltage: 81.70 > battery.voltage.nominal: 72.0 > beeper.status: enabled > device.mfr: NUMERIC > device.model: 3000 SW > device.type: ups > driver.name: blazer_ser > driver.parameter.pollinterval: 2 > driver.parameter.port: /dev/ttyUSB0 > driver.version: 2.4.3 > driver.version.internal: 1.51 > input.current.nominal: 13.0 > input.frequency: 50.0 > input.frequency.nominal: 50 > input.voltage: 221.3 > input.voltage.fault: 221.3 > input.voltage.nominal: 230 > output.voltage: 219.6 > ups.delay.shutdown: 30 > ups.delay.start: 180 > ups.firmware: VER 3.02 > ups.load: 11 > ups.mfr: NUMERIC > ups.model: 3000 SW > ups.status: OL > ups.temperature: 18.0 > ups.type: offline / line interactive > > upsrw watcher-ups > > (nothing show up) > > upscmd -l watcher-ups > > Instant commands supported on UPS [watcher-ups]: > > beeper.toggle - Toggle the UPS beeper > load.off - Turn off the load immediately > load.on - Turn on the load immediately > shutdown.return - Turn off the load and return when power is back > shutdown.stayoff - Turn off the load and remain off > shutdown.stop - Stop a shutdown in progress > test.battery.start - Start a battery test > test.battery.start.deep - Start a deep battery test > test.battery.start.quick - Start a quick battery test > test.battery.stop - Stop the battery test > > Shutdown test (Ubuntu server 10.04.2 LTS): > > Apr 24 18:10:29 watcher1 upsmon[1684]: UPS watcher-ups at localhost on > battery > Apr 24 18:17:01 watcher1 CRON[20146]: (root) CMD ( cd / && run-parts > --report /etc/cron.hourly) > Apr 24 18:34:49 watcher1 upsmon[1684]: UPS watcher-ups at localhost battery > is low > Apr 24 18:35:09 watcher1 upsmon[1684]: Giving up on the master for UPS > [watcher-ups at localhost] > Apr 24 18:35:09 watcher1 upsmon[1684]: Executing automatic power-fail > shutdown > Apr 24 18:35:09 watcher1 upsmon[1684]: Auto logout and shutdown proceeding > Apr 24 18:35:14 watcher1 init: idmapd main process (643) killed by TERM > signal > Apr 24 18:35:14 watcher1 init: tty4 main process (949) killed by TERM > signal > Apr 24 18:35:14 watcher1 init: tty5 main process (955) killed by TERM > signal > Apr 24 18:35:14 watcher1 init: tty2 main process (968) killed by TERM > signal > Apr 24 18:35:14 watcher1 init: tty3 main process (969) killed by TERM > signal > Apr 24 18:35:14 watcher1 init: tty6 main process (972) killed by TERM > signal > Apr 24 18:35:14 watcher1 init: cron main process (975) killed by TERM > signal > Apr 24 18:35:14 watcher1 init: tty1 main process (1932) killed by TERM > signal > Apr 24 18:35:14 watcher1 acpid: exiting > Apr 24 18:35:15 watcher1 kernel: Kernel logging (proc) stopped. > Apr 24 20:19:22 watcher1 kernel: imklog 4.2.0, log source = /proc/kmsg > started. > Apr 24 20:19:22 watcher1 rsyslogd: [origin software="rsyslogd" > swVersion="4.2.0" x-pid="670" x-info="http://www.rsyslog.com"] (re)start > > > http://www.numericups.com/default.aspx?pageid=c58749e9-aac7-468e-9743-9f56df899646 > > Thanks a lot. >thanks a lot for your *perfect* report, commited as r2976 into the development trunk. cheers Arnaud -- Linux / Unix Expert R&D - Eaton - http://powerquality.eaton.com Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://www.debian.org Free Software Developer - http://arnaud.quette.free.fr/ -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20110427/b6a0ba48/attachment.htm>