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

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

On Mon, 15 May 2017, Dinow Hsieh wrote: > ==> I have tried this command "upsdrvctl shutdown" as below results (However the UPS still sustain the power) > > ??? Network UPS Tools - UPS driver controller 2.7.1 > ??? Network UPS Tools - Generic HID driver 0.38 (2.7.1) > ??? USB communication driver 0.32 > ??? Using subdriver : PowerCOM HID 0.4 > ??? Initiating UPS

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

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

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

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

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

Hi ALL, Powercom Imperial IMP-525AP seems to be fully compatible with NUT. Unfortunately, I can not disable beeper. upscmd -u {NUT_USER} -p {NUT_PASSWORD} powercom beeper.toggle returns *OK*, however, ups.beeper.status=enabled Thank you, Sergey ========== Additional info: 1) $ upsc powercom battery.charge: 100 battery.charge.low: 10 battery.charge.warning: 30 battery.date: 2010/01/01

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

Hi Charles, > Sigh, I wish the vendors wouldn't change operation without changing identifiers. > > Do you have any recommendations on how the driver should decide whether it is an old 0x0004 or new 0x0004 device? No-no, there is no an old 0x0004 or new 0x0004 device, I guess that we have to handle general case for all 0d9f:0x0004 devices. From PCM_USB_LIST_device2014.pdf attached

On Nov 12, 2014, at 3:53 AM, Maksym Bodaniuk <max.bodaniuk at gmail.com> wrote: > Hi Charles, > >> Sigh, I wish the vendors wouldn't change operation without changing identifiers. >> >> Do you have any recommendations on how the driver should decide whether it is an old 0x0004 or new 0x0004 device? > > No-no, there is no an old 0x0004 or new 0x0004

Hello all, Last week I rescued and UPS from the trash (it's really amazing the kind of things you can find in the trash of the university research labs). No manual, no cd, no cables, just the unit. It's name is "Blizzo 500", and blizzo was just the rebranding of a spanish reseller which has been out of the scene for nearly two years now, at least according to the wayback

Hello, Got PowerCOM BNT-1000AP, usb id 0d9f:00a6, firmware FW4.A6 nut 2.4.3 on debian stable shows only two instant commands: beeper.toggle - Toggle the UPS beeper -- not working test.battery.start.quick - Start a quick battery test -- works ok. No load and shutdown commands. Trying svn trunk version, with the same results. Debug output shows the problem: 0.035558

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

Hi Arnaud, I received several replies from technical support. It turned out that according to the UPS serial number it had been manufactured in 2012. So, the device should support the ability to disable the beeper. But still I can not disable the beeper using the latest version of UPSMON Plus in Windows: http://www.pcm.ru/data/download/public/soft/setup_upsmon_v2.9.rar (don't know why; the

Hello. Not listed as supported, so here is some info, [root at vhost ~]# /usr/sbin/usbhid-ups -DD -a powercom Network UPS Tools - Generic HID driver 0.38 (2.7.2) USB communication driver 0.32 0.000000 debug level is '2' 0.001318 upsdrv_initups... 0.074753 Checking device (0529/0001) (003/002) 0.074835 Failed to open device, skipping. (Permission denied)

Hi Have been trying to get nut and Powercom Vanguard 2000 ups communicating ? in the /lib/udev/rules.d/52-nut-usbups.rules file we have this entry #? PowerCOM VGD - Vanguard? - usbhid-ups ATTR{idVendor}=="0d9f", ATTR{idProduct}=="0004", MODE="664", GROUP="nut" ? In the /etc/ups/ups.conf [UPS] ??????? driver = usbhid-ups ??????? port =

On April 28, 2017 9:11:59 AM GMT+03:00, "????????? ?????????" <vtk-alexb at mail.ru> wrote: >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: