Hi Sergey, 2011/7/15 Sergey Talchuk <tals1975 at gmail.com>> Hi Arnaud, > > both configurations are ok :). Please find the file attached. >logic since the 2nd is automatically guessed from the first using USB Vendor and Product ID ;-) can you please send in upsc, upscmd and upsrw output. and also report the shutdown testing as described here: http://www.networkupstools.org/docs/user-manual.chunked/ar01s06.html#Shutdown_design I'll then add this model to the HCL. cheers, Arnaud> thanks, > Sergey > > P.S. Have nice weekend > > > On Wed, Jul 13, 2011 at 6:20 PM, Arnaud Quette <aquette.dev at gmail.com>wrote: > >> >> 2011/7/13 Sergey Talchuk <tals1975 at gmail.com> >> >>> Hi Arnaud, >>> >> >> Hi Sergey, >> >> >>> A friend of mine bought an UPS: ?POWEREX VI 1000 LED?. >>> http://www.powerexups.aiptek.de/products.html >>> As far as I know he doesn?t want to use NUT for windows, since he is >>> quite happy with the software delivered on the CD :) >>> http://www.power-software-download.com/viewpower.html >>> >>> But I was wondering if NUT can work with the UPS. >>> And it seems ?POWEREX VI 1000 LED? can work with ?blazer_usb? driver (see >>> below) >>> >>> # lsusb -d 0665:5161 >>> Bus 002 Device 005: ID 0665:5161 Cypress Semiconductor USB to Serial >>> >> >> well, though it won't be as good as an Eaton (standard disclaimer ;-), >> this one should indeed be supported by the blazer drivers. >> >> Not fully sure if it's with blazer_usb (cypress subdriver) and port "auto" >> or with blazer and port "/dev/ttyUSB0" though. Try the former first... >> >> please report back on the list so that we can add it to the compat list. >> >> 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/20110717/987f3200/attachment.html> -------------- next part -------------- ==CONFIGURATION Nr.1 ------------------ # driver = blazer_usb # port = auto $ upsc powerex battery.voltage: 27.80 battery.voltage.nominal: 24.0 beeper.status: enabled device.type: ups driver.name: blazer_usb driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.version: 2.6.0 driver.version.internal: 0.03 input.current.nominal: 5.0 input.frequency: 49.9 input.frequency.nominal: 50 input.voltage: 233.6 input.voltage.fault: 233.1 input.voltage.nominal: 220 output.voltage: 233.1 ups.delay.shutdown: 30 ups.delay.start: 180 ups.load: 10.0 ups.productid: 5161 ups.status: OL ups.type: offline / line interactive ups.vendorid: 0665 ==CONFIGURATION Nr.2 ------------------ # driver = blazer_usb # subdriver = cypress # vendorid = 0665 # productid = 5161 # port = auto $upsc powerex battery.voltage: 27.80 battery.voltage.nominal: 24.0 beeper.status: enabled device.type: ups driver.name: blazer_usb driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.parameter.productid: 5161 driver.parameter.subdriver: cypress driver.parameter.vendorid: 0665 driver.version: 2.6.0 driver.version.internal: 0.03 input.current.nominal: 5.0 input.frequency: 49.9 input.frequency.nominal: 50 input.voltage: 233.1 input.voltage.fault: 233.6 input.voltage.nominal: 220 output.voltage: 233.6 ups.delay.shutdown: 30 ups.delay.start: 180 ups.load: 10.0 ups.productid: 5161 ups.status: OL ups.type: offline / line interactive ups.vendorid: 0665 $ upscmd -l powerex Instant commands supported on UPS [powerex]: 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
2011/7/18 Sergey Talchuk <tals1975 at gmail.com>> Hi Arnaud, >Hi Sergey, first, please keep the traffic on the list. Even if you're not subscribed, there may be people interested in the below information...> The UPS had successful shutdown on COMMUNICATION LOST and on TIMER with 60 > seconds delay. >I guess from the above that the TIMER was related to "on battery" condition. I would like to ensure that OB and LB ups.status conditions are handled. could you please check for these and send back upsc outputs? note that there should be no load apart from dumb things (like light bulbs) attached to the UPS... just in case. 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/ Please find the output from other commands in the attached file.> > thanks, > Sergey > > On Sun, Jul 17, 2011 at 11:44 AM, Arnaud Quette <aquette.dev at gmail.com>wrote: > >> Hi Sergey, >> >> 2011/7/15 Sergey Talchuk <tals1975 at gmail.com> >> >>> Hi Arnaud, >>> >>> both configurations are ok :). Please find the file attached. >>> >> >> logic since the 2nd is automatically guessed from the first using USB >> Vendor and Product ID ;-) >> >> can you please send in upsc, upscmd and upsrw output. >> and also report the shutdown testing as described here: >> >> http://www.networkupstools.org/docs/user-manual.chunked/ar01s06.html#Shutdown_design >> >> I'll then add this model to the HCL. >> >> cheers, >> Arnaud >> >> >>> thanks, >>> Sergey >>> >>> P.S. Have nice weekend >>> >>> >>> On Wed, Jul 13, 2011 at 6:20 PM, Arnaud Quette <aquette.dev at gmail.com>wrote: >>> >>>> >>>> 2011/7/13 Sergey Talchuk <tals1975 at gmail.com> >>>> >>>>> Hi Arnaud, >>>>> >>>> >>>> Hi Sergey, >>>> >>>> >>>>> A friend of mine bought an UPS: ?POWEREX VI 1000 LED?. >>>>> http://www.powerexups.aiptek.de/products.html >>>>> As far as I know he doesn?t want to use NUT for windows, since he is >>>>> quite happy with the software delivered on the CD :) >>>>> http://www.power-software-download.com/viewpower.html >>>>> >>>>> But I was wondering if NUT can work with the UPS. >>>>> And it seems ?POWEREX VI 1000 LED? can work with ?blazer_usb? driver >>>>> (see below) >>>>> >>>>> # lsusb -d 0665:5161 >>>>> Bus 002 Device 005: ID 0665:5161 Cypress Semiconductor USB to Serial >>>>> >>>> >>>> well, though it won't be as good as an Eaton (standard disclaimer ;-), >>>> this one should indeed be supported by the blazer drivers. >>>> >>>> Not fully sure if it's with blazer_usb (cypress subdriver) and port >>>> "auto" or with blazer and port "/dev/ttyUSB0" though. Try the former >>>> first... >>>> >>>> please report back on the list so that we can add it to the compat list. >>>> >>>> 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/20110718/646bd000/attachment.html> -------------- next part -------------- $ upsc powerex battery.voltage: 27.80 battery.voltage.nominal: 24.0 beeper.status: enabled device.type: ups driver.name: blazer_usb driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.parameter.productid: 5161 driver.parameter.subdriver: cypress driver.parameter.vendorid: 0665 driver.version: 2.6.0 driver.version.internal: 0.03 input.current.nominal: 5.0 input.frequency: 49.9 input.frequency.nominal: 50 input.voltage: 229.7 input.voltage.fault: 229.2 input.voltage.nominal: 220 output.voltage: 229.7 ups.delay.shutdown: 30 ups.delay.start: 180 ups.load: 10.0 ups.productid: 5161 ups.status: OL ups.type: offline / line interactive ups.vendorid: 0665 ===$upscmd -l powerex Instant commands supported on UPS [powerex]: 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 ==$ upsrw powerex ====
Hi Sergey, *** first, please keep the traffic on the list *** ie, keep nut-upsuser copied of our discussion! 2011/7/19 Sergey Talchuk <tals1975 at gmail.com>> Hi Arnaud, > > Sorry. My mistake. > > OB ups.status condition is handled correct (see attachment) >excellent, thanks. I still see that you're using timers. Have you also tried reaching the low battery (ups.status = OB LB) to trigger shutdown? Otherwise, please also test this: http://www.networkupstools.org/docs/user-manual.chunked/ar01s06.html#Shutdown_design finally, I've just added an entry in the development version of the HCL (r3140). It will show up in the next release. But I'm not sure about OL ups.status, since 'upsc powerex' output didn't> give me anything like 'battery.charge=?' >check the blazer manpage for the solution: http://www.networkupstools.org/docs/man/blazer.html and more specially the "BATTERY CHARGE" section. 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/20110719/4cddf949/attachment.html> -------------- next part -------------- ==ON BATTERY $ upsc powerex battery.voltage: 26.50 battery.voltage.nominal: 24.0 beeper.status: enabled device.type: ups driver.name: blazer_usb driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.parameter.productid: 5161 driver.parameter.subdriver: cypress driver.parameter.vendorid: 0665 driver.version: 2.6.0 driver.version.internal: 0.03 input.current.nominal: 5.0 input.frequency: 50.1 input.frequency.nominal: 50 input.voltage: 7.4 input.voltage.fault: 7.4 input.voltage.nominal: 220 output.voltage: 220.4 ups.delay.shutdown: 30 ups.delay.start: 180 ups.load: 12.0 ups.productid: 5161 ups.status: OB ups.type: offline / line interactive ups.vendorid: 0665 --- Jul 19 20:36:24 openSuSE blazer_usb[1444]: Startup successful Jul 19 20:36:24 openSuSE upsd[1447]: listening on 127.0.0.1 port 3493 Jul 19 20:36:24 openSuSE upsd[1447]: Connected to UPS [powerex]: blazer_usb-powerex Jul 19 20:36:24 openSuSE upsd[1448]: Startup successful Jul 19 20:36:24 openSuSE upsmon[1451]: Startup successful Jul 19 20:36:24 openSuSE upsd[1448]: User test at 127.0.0.1 logged into UPS [powerex] Jul 19 20:37:24 openSuSE upsmon[1452]: UPS powerex at localhost on battery Jul 19 20:37:24 openSuSE upssched[1458]: Timer daemon started Jul 19 20:37:24 openSuSE upssched[1458]: New timer: onbatt1 (10 seconds) Jul 19 20:37:24 openSuSE upssched[1458]: New timer: earlyshutdown (120 seconds) Jul 19 20:37:34 openSuSE upssched[1458]: Event: onbatt1 Jul 19 20:37:34 openSuSE upssched-cmd: on battery. The UPS has been on battery for a while, logout right now! Jul 19 20:39:24 openSuSE upssched[1458]: Event: earlyshutdown Jul 19 20:39:24 openSuSE upssched-cmd: forced shutdown. UPS on battery too long, forced shutdown! Jul 19 20:39:24 openSuSE upsmon[1452]: Signal 10: User requested FSD Jul 19 20:39:24 openSuSE upsd[1448]: Client test at 127.0.0.1 set FSD on UPS [powerex] Jul 19 20:39:24 openSuSE upsmon[1452]: Executing automatic power-fail shutdown Jul 19 20:39:24 openSuSE upsmon[1452]: Auto logout and shutdown proceeding Jul 19 20:39:29 openSuSE shutdown[1470]: shutting down for system halt Jul 19 20:39:29 openSuSE init: Switching to runlevel: 0