similar to: Fw: [Nut-upsdev] POWERCOM-UPS-USB : UPS Shutdown

Good Day Roger Price AA. Hi, Normally one would expect the UPS to disconnect it's power outlets after the default ups.delay.shutdown = 20 seconds. ==> I got it. I tried to command "upsdrvctl shutdown" on both line-mode and battery-mode ==> But ups do not disconnect its outlets power ----------------------------------------------------------------------------------- BB.

Good Day Roger AA. notice that during the test, you have little or no load, since despite being in state OB DISCHRG the battery.charge is still 100. It's best to perform such tests with a dummy load such as a table lamp and an old fashioned incandescent 100 watt bulb. ==> Yes. I got it and try to ascend load as below results dinow-All-Series:~# upsc pcmups Init SSL without

Good Day Roger AA. notice that during the test, you have little or no load, since despite being in state OB DISCHRG the battery.charge is still 100. It's best to perform such tests with a dummy load such as a table lamp and an old fashioned incandescent 100 watt bulb. ==> Yes. I got it and try to ascend load as below results dinow-All-Series:~# upsc pcmups Init SSL without

Good Day nut Many thanks for your reading ==> AA. I confront an issue that can't shutdown the ups With the nut, I can get the ups status(upsc) and shutdown the linux-ubuntu when power failure occurs(upsmon) But don't know which configuration I ignore to setup for ups shutdown ==> BB. I want to check that with the command "upsdrvctl shutdown" and

On Tue, 16 May 2017, Dinow Hsieh wrote: > BB. Could you show us the output of command "upsc pcmups"? > > ==> Yes. Below 2 mode were the outputs of command "upsc pcmups" > > battery.charge: 100 > battery.charge.low: 10 > battery.charge.warning: 30 > battery.date: 2010/12/20 ... > ups.date: 2010/12/20 > ups.load: 4 ... > ups.status: OB

On May 17, 2017, at 4:53 AM, Dinow Hsieh <dinow at upspowercom.com.tw> wrote: > > ==> I tried below set-command but it react fail > > dinow-All-Series:~# upsrw -s "ups.delay.shutdown"="30" -u pcmups pcmups at localhost > Password: > Unexpected response from upsd: ERR ACCESS-DENIED > This error is not from the driver. Be sure to specify a NUT

Hi! Is there any user of nut having this type of UPS? ( http://www.pcmups.com.tw/product/iCute.html) It works nice under windows and also is detected under Linux and installed as USB HID device. There is problem however, as the software provided by its manufacturer (http://www.pcmups.com.tw/download/Download/UPSMON_USBV091.zip) doesn't seem to comunicate with the UPS at all. It shows messages

Hello All. I have PowerCOM ( http://pcmups.com.tw/ ) UPS management protocol specification at http://www.sovico.org/pcm.txt Current version of NUT contains any drivers include driver for Powercom, but not fully funcionality. This specification describe protocol for next series UPS: BLACK KNIGHT: All UPS AP series WARRIOR: WAR-1000AP WOW: All UPS U series IMPERIAL: All UPS KING: All UPS SMART

Well it is the season for storms and power outages here in the US PNW. I noticed that today when the power went out, NUT mostly did what I hoped/wanted. But it did not actually turn off the UPS at all. The UPS kept beeping and I had to turn it off manually. I thought that NUT would handle this. But perhaps it cannot for my unit? Or perhaps I have things improperly configured? Any suggestions?

Hi Guys, Am a Linux newbie and need some help setting up this UPS with NUT on Cent OS 5.6. So basically I have the following packages installed with yum: libusb-devel-0.1.12-5.1.x86_64 libusb-devel-0.1.12-5.1.i386 libusb-0.1.12-5.1.x86_64 libusb-0.1.12-5.1.i386 nut-2.2.2-1.el5.x86_64 When I run service ups start I get the following: Starting UPS driver controller:

I have only RS-232 on the box (meanwhile, it was manufactured on march of 2011) Here is my configs: nut.conf: * * MODE = netserver ups.conf: * * [KIN1500] driver = powercom port = notUsed desc = "Powercom KING PRO KIN-1500AP RM" upsd.conf: * * LISTEN 192.168.1.2 3493 upsd.users: * * [monuser] password = xxxxxxxx upsmon master

Dear Sirs, First of all I would like to thank you for support PCM product in your project. Kindly please be informed that POWERCOM launch new USB-controller with productID 0X04. Updated USB-controller compatible with previous version which supported by your usbhid-ups driver. There is added some command and changed idProduct. Vendor ID stay the same 0X0d9f without changes. Detailed information

Dear Sirs, We appreciate your support and cooperation. Can you please kindly add our new USB-controller with productID 0X04 to NUT compatible list. Updated USB-controller compatible with previous version which is supported by your usbhid-ups driver. Detailed information regarding new POWERCOM communication protocol you could download via link

OS name and version: pi at raspberrypi ~ $ cat /etc/*release PRETTY_NAME="Debian GNU/Linux 7.0 (wheezy)" uname -a Linux raspberrypi 3.6.11+ #393 PREEMPT Fri Mar 8 16:36:28 GMT 2013 armv6l GNU/Linux exact NUT version pi at raspberrypi ~ $ dpkg -s nut Package: nut ... Version: 2.6.4-2.3 NUT installation method: package exact device name and related information:

On Nov 11, 2014, at 3:30 PM, Maksym Bodaniuk <max.bodaniuk at gmail.com> wrote: > Dear Charles and Artem, > > I've recently bought a new PowerCom Imperial IMD825-AP LCD which identifies itself as 0x0d9f:0x0004. > At first glance it seems that usbhid-ups driver works fine. But when I tried to shutdown UPS via DelayBeforeShutdown it started double beeping every couple seconds

please subscribe to the nut user mailing list ( http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser) and post the output of "/path/to/usbhid-ups -DDDDD -a <your_ups_name_in_ups.conf>" cheers, Arnaud -- Linux / Unix Expert R&D - Eaton - http://www.eaton.com/mgeops Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer -

Hello all! Some days ago we received new UPS?Powercom BNT-2000AP with USB interface to replace an old staff and I've spent four last days trying to connect it with NUT. I have a FreeBSD 8.4 box with NUT 2.7.2. # dmesg|grep -i powercom ugen0.3: <POWERCOM Co.,LTD> at usbus0 uhid0: <POWERCOM Co.,LTD HID UPS Battery, class 0/0, rev 1.10/0.01, addr 3> on usbus0 uhid0: <POWERCOM

Hi, fellow NUT gurus; I am having a big issue with our new Powercom Imperial Digital UPS. The UPS is come with a serial over USB port and plug into the usb port on the computer. I am having problem to setup our fedora 7 linux machine talks to the ups. The kernel 2.6.22.1 seems to be able to detect the ups is plug into one of its usb port. But it just couldn't establish a connection with

Hi, fellow NUT gurus; I am having a big issue with our new Powercom Imperial Digital UPS. The UPS is come with a serial over USB port and plug into the usb port on the computer. I am having problem to setup our fedora 7 linux machine talks to the ups. The kernel 2.6.22.1 seems to be able to detect the ups is plug into one of its usb port. But it just couldn't establish a connection with