similar to: Hope for APC Smart UPS 1500

Hi, we bought two Smart-UPS X 1500 FW:UPS 09.1 / ID=20 lsusb -v: Bus 002 Device 002: ID 051d:0003 American Power Conversion UPS Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 idVendor

On Jul 9, 2013, at 9:04 AM, Gregor Burck wrote: > we bought two Smart-UPS X 1500 FW:UPS 09.1 / ID=20 [...] > I see there should be problems to get it work with a free daemon like nut, but are there some hints using it? > In my ups.conf I tried: > > [apc001] > driver = apcsmart > port = auto > desc = "Smart APC" Only the USB drivers should

At one time I had my Back-UPS ES-750 working with nut and the usbhid-ups driver. Not sure what has changed, but I can't get the driver to load now. It exits with this error: Network UPS Tools - UPS driver controller 2.2.2 Network UPS Tools: 0.29 USB communication driver - core 0.33 (2.2.2) No matching HID UPS found Driver failed to start (exit status=1) lsusb -v gives me: Bus 003 Device

Hi! I'm trying to setup a small mobile server rack with key switch to power on/off the whole system. Used USP is an APC Smart-UPS 1500 SMT1500RMI2U with extra AP9613 IO card [1] to get the key switch "connected" to the UPS. The IO card has several inputs which can trigger actions like power on and "gracefully" shutdown. On key switch OFF this SMT ups model changes ups

Hi All, I bought a USB Bluetooth dongle. However, it's not working for me. Please help, how to debug and get more information as I can not see any error or warning message from system log message. I checked http://thread.gmane.org/gmane.linux.bluez.kernel/22183/focus=22211, however, also find another page

Hello list, ? ?Cannot make Evolution 850 to be recognized, maybe the problem is "Warning: incomplete endpoint descriptor" in lsusb? Details are as follows. NUT installed by download of debian package. Any ideas/suggestions are highly welcome, thanks in advance! --ValenteM = ? ?= ? ? = ? ? = Ubuntu server 12.04.1 LTS (GNU/Linux 3.2.0-35-generic x86_64) sudo dpkg -i

Hi, just try the Unitek Self Protek Mistral 1000ipF with nut and I doesn't work. How can I correctly configure it (if the driver support it). Best regards, In my dmesg: [42953293.620000] usb 1-2: new low speed USB device using uhci_hcd and address 7 [42953293.760000] usb 1-2: no configurations [42953293.760000] usb 1-2: can't read configurations, error -22 [42953293.880000] usb 1-2: new

Hi there... nut 2.4.3 kicks an error at me when I try to talk to my UPS. machine is linux 2.4.21-32.ELsmp with libusb-0.1.8-3 package update. # /usr/local/ups/bin/upsdrvctl start Network UPS Tools - UPS driver controller 2.4.3 Network UPS Tools - Generic HID driver 0.34 (2.4.3) USB communication driver 0.31 Using subdriver: APC HID 0.95 libusb_get_interrupt: error submitting URB: Invalid

Hi, I have a powermust with a usb connector. I searched the archive and found this post: http://lists.alioth.debian.org/pipermail/nut-upsdev/2006-April/000816.html Must I abandon hope of controlling this UPS via USB with NUT? Added this line to /etc/udev/rules.d/70-nut-usbups.rules: # OMRON - usbhid-ups SYSFS{idVendor}=="06da", SYSFS{idProduct}=="0003",

Hello I have two completely different UPS that turn out to use the same driver. Both work with blazer_usb my LSUSB says: Bus 001 Device 005: ID 0665:5161 Cypress Semiconductor USB to Serial Bus 001 Device 004: ID 0665:5161 Cypress Semiconductor USB to Serial my lsusb -vd 0665: says: pi at elektra:~ $ lsusb -vd 0665: Bus 001 Device 005: ID 0665:5161 Cypress Semiconductor USB to Serial

Hello In case anyone is interested and for the sake of updating the documentation from http://networkupstools.org/stable-hcl.html , I would like to report that nut v2.7.4 talks successfully ( at least partially ) with the UPS from $topic, which is part of the product line from http://www.informups.com/guardian_guardian_lcd600va_2000va.html ( Inform is a Turkish manufacturer that was

folks, the following is lsusb -v for my 250gb usb hard drive. I note the Protocol line mentions zip: ie bInterfaceProtocol 80 Bulk (Zip) does that mean its one of those USB-ZIP devices ? If so, to the parameters below say anything about the CHS settings needed ? tia, PS - HPA, you were correct wrt what I missed :-} Bus 001 Device 002: ID 1058:0401 Western Digital Technologies,

Hi all! FYI, after some research in your list I think that blazer_usb is the best driver for my Soyntec Sekury A600 UPS (which is not in the hardware supported lists). I connected it with my system using USB port (it also has serial RS-232) This is the report I have: battery.voltage: 13.60 battery.voltage.nominal: 12.0 beeper.status: enabled device.type: ups driver.name: blazer_usb

Hi everybody, In a christmas sequel I've been offered one of the units mentioned above. I've tried to connect it to my Fedora 8 workstation but rapidly concluded it's not yet supported by NUT. So far, I've decompiled the Java classes of the manufacturer's application and noticed that it's most probably yet another kind of serial protocol through the USB. Since

Hello, I (now) own an Emerson Liebert GXT3 6000VA conected via USB. I've searched the web trying to configure nut (nut-2.6.5-1.el6.x86_64 epel rpm on CentOS 6.3) to monitor the UPS, but couldn't find a successful configuration. I'm running kernel 2.6.32-279.14.1.el6.x86_64. The UPS is connected with an USB cable: Bus 004 Device 002: ID 10af:0008 Liebert Corp. PowerSure Interactive

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

rtd at linux-5048:~> lsusb -vvv -d 2a37: Bus 001 Device 005: ID 2a37:5110 Couldn't open device, some information will be missing Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor

Some of my messages never went through since I hit a message size limit. I'm resending them in the hopes they are under the limit. Charles, The lsusb command did not trigger a disconnect. The output of that command is below. I ran "usbhid-ups -a upsunit -DDD &> output.log" and I have attached the /var/log/messages and output.log to this email. Before running this test

Hi, I have a Sitecom NL-031 USB 3.0 NIC which I'd like to use under centos 6.5, but unfortunately I see no support. Or, I am doing something wrong. According to LKDDb (Linux Kernel Driver DataBase), the correct driver is "CONFIG_USB_NET_AX8817X: ASIX AX88xxx Based USB 2.0 Ethernet Adapters" but obviously, I've grabbed a non matching "iProduct", because mine is

Hi Charles, I'll try the blazer_ser and the nutdrv_qx with version 2.7.1 later. Below, the result of 'lsusb -vvv' requested: Bus 004 Device 002: ID 04b4:5500 Cypress Semiconductor Corp. HID->COM RS232 Adapter Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.00 bDeviceClass 0 (Defined at Interface level)