similar to: New powercom device?

On 8/15/2017 6:13 AM, Charles Lepple wrote: > On Aug 10, 2017, at 12:19 AM, Harlan Stenn wrote: >> >> 0.447497 HID descriptor length 37 >> 0.450449 Report Descriptor size = 37 >> 0.451062 Using subdriver: PowerCOM HID 0.5 >> 0.451996 3 HID objects found >> 0.453502 Path: ffa00001.ffa00001, Type: Input, ReportID: 0x00, >> Offset: 0, Size: 8,

On Aug 10, 2017, at 12:19 AM, Harlan Stenn wrote: > > 0.447497 HID descriptor length 37 > 0.450449 Report Descriptor size = 37 > 0.451062 Using subdriver: PowerCOM HID 0.5 > 0.451996 3 HID objects found > 0.453502 Path: ffa00001.ffa00001, Type: Input, ReportID: 0x00, > Offset: 0, Size: 8, Value: 0 > 0.453677 Path: ffa00001.ffa00002, Type: Output, ReportID:

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

I've got a Powercom Imperial UPS, with an internal USB<=>serial converter. It implements the same protocol as other powercom devices implements, but only when talking over serial port (there's no such port on the device). Someone wrote a draft version of usbserial driver for it, and the UPS works with this kernel-level driver and with powercom driver from nut (using /dev/ttyUSBx

Hi I Bought a cheap Plexus 800VA UPS from ebuyer : http://www.ebuyer.com/product/240319 to use with my Netgear ReadyNAS duo. Initial version of NUT was very old and NAS didn't detect it although in the NAS log it said "UPS Disconnected". Syslog did send the following : Jan 25 12:46:36 nas-27lfc kernel: usb 1-1: new low speed USB device using uhci_hcd and address 2 Jan 25 12:46:37

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)

Skipped content of type multipart/mixed-------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available Url : http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20070205/5ad69acc/attachment.pgp

First off, my apologies for bringing back this thread from the dead (September 2005, http://lists.alioth.debian.org/pipermail/nut-upsdev/2005-September/000150.html), however my problem seems relevant enough that I wondered what happened to this thread as it seems to have died after the message I quote below. Despite the fact that I am having trouble getting my Sweex 1000VA UPS (USB) to work, and

First off, my apologies for bringing back this thread from the dead (September 2005, http://lists.alioth.debian.org/pipermail/nut-upsdev/2005-September/000150.html), however my problem seems relevant enough that I wondered what happened to this thread as it seems to have died after the message I quote below. Despite the fact that I am having trouble getting my Sweex 1000VA UPS (USB) to work, and

Hi Rok, I retired from working on NUT a few months ago, so I don't have the most up-to-date info. But the guys on the nut-upsdev mailing list (cc'd above) are very helpful. Both of your devices (or nearly identical ones) have been seen on the mailing lists before. The Sweex was first mentioned in a message by Eli Wapniarski on 14 Jun 2006 on nut-upsuser, and was most recently discussed

Is anyone besides me using gcc 4.*.*? I noticed that NUT generates an enormous amount of warning noise with that compiler, mostly due to implicit casts between signed/unsigned pointer types. Any volunteers to de-noise the code a bit? The easy way is to insert typecasts; the better way is to actually take care about signedness. -- Peter gcc -I../include -O -Wall -Wsign-compare -c -o everups.o

On Sat, May 28, 2016 at 11:05 AM, abi <abi at abinet.ru> wrote: > However I was unable to shutdown.return it. Maybe protocol is not fully > compatible? > > 0.145757 Initiating UPS shutdown > 0.145760 upsdrv_shutdown... > 0.145763 instcmd(shutdown.return, [NULL]) > 0.145767 powercom_shutdown_nuf: value = (null), command = 5400 > 0.145770

Hi. Sorry for the English. Use online translator. Trying to configure Powercom Smart KING Pro 1250A and Debian Jessie. OS name and version: Debian Jessie 8.8, kernel 4.9.25-1~bpo8+1 exact NUT version: 2.7.2-4 NUT installation method: package exact device name and related information: Powercom Smart KING Pro 1250A (connect via usb; leads changed) complete problem description, with any relevant

Hi. Sorry for the English. Use online translator. Trying to configure Powercom Smart KING Pro 1250A and Debian Jessie. OS name and version: Debian Jessie 8.8, kernel 4.9.25-1~bpo8+1 exact NUT version: 2.7.2-4 NUT installation method: package exact device name and related information: Powercom Smart KING Pro 1250A (connect via usb; leads changed) complete problem description, with any relevant

Hi again, Thanks for the prompt reply. Just for the record i am running debian unstable/sid with nut 2.7.4-3 # dpkg -l 'nut*' | grep ^ii ii nut 2.7.4-3 all network UPS tools - metapackage ii nut-client 2.7.4-3 amd64 network UPS tools - clients ii nut-server 2.7.4-3 amd64 network UPS tools - core

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 =

Howdy, I've been trying for a while now to get this running. Can anybody please tell me what the proper configuration is for this unit ??? This is what I've got/tried so far: # cat ups.conf # Start with # # # upsdrvctl -u nut -D start MEGATEC MODE=netserver user=nut # Ultra ULT33046 2000 VA 1200 W

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:

Hi, Arjen; I am new to linux and not sure how to create the PowerCom-usb driver. So could you please compile powercom-usb file for me. I am happy to test it out with the USB PowerCom Ups. Thanks, Paul MCSE/MCSA/MCP ------------------------------ Message: 2 Date: Mon, 03 Sep 2007 11:13:32 +0200 From: Arjen de Korte <nut+users at de-korte.org> Subject: Re: [Nut-upsuser] Powercom USB UPS is