similar to: Power Shield Defender 1200 - The Story Continues

> Hello everyone. I try to connect four PowerMust 2000 ups's via usb to one > computer using megatec_usb driver. But megatec_usb completly ignores port > directive in ups.conf, I even try port = /dev/null and megatec_usb founds > ups and it works. The 'port' is not used for USB connected devices, it's only needed for compatibility reasons. > Problem is that

Hello, i try to setup NUT service to read/control my UPS but without success. Problem is when i try to start "/usr/local/ups/bin/upsdrvctl -DDDD -u root start" i got: /Network UPS Tools - UPS driver controller 2.6.2/ / 0.000000/ /If you're not a NUT core developer, chances are that you're told to enable debugging/ /to see why a driver

Hi All, I get very strange UPS problem from RspberryPI mode B (both version 2 and 3). Here is our environment: OS: Raspbian 8.0, Ubuntu 16.04 and Ubuntu 14.04 Platform: RaspberryPi Mode B version 2 and version 3 NUT: tested version 2.6.3, 2.7.1 and 2.7.2 (from

Hi nut-upsdev, I have just got OMRON BX35F. Only object files and usage information is included. Where should I start to help you to get it supported? Any interest in supporting it at all?

Is that with both UPSes on same machine? A quick guess would be that insufficient data points to identify the device are configured (vendorid, productid, serial...) in ups.conf, so both drivers connect to the first match. I'd expect them to conflict and one would die or both loop reconnecting, if both are running at once, though. Also, which NUT version? Custom build from GitHub or an

Hi, I'm new in the list and I'm having a little bit trouble to put the megatec_usb to work. I've been using NUT for a while with the apc and megatec driver (serial), with no problem. The server is a Ubuntu 8.04.2 with NUT version 2.2.1-2.1ubuntu7.2, the default package version in this ubuntu release. I've configured the ups.conf as follows: [sms] driver = megatec_usb

Hi, I'm new in the list and I'm having a little bit trouble to put the megatec_usb to work. I've been using NUT for a while with the apc and megatec driver (serial), with no problem. The server is a Ubuntu 8.04.2 with NUT version 2.2.1-2.1ubuntu7.2, the default package version in this ubuntu release. I've configured the ups.conf as follows: [sms] driver = megatec_usb

Bonjour, Je souheterais utilis? la version qui permet le '-x generic',mais je ne sais pas ou la recuperer car ca devrait solutionner mon probleme (cf mail ci-dessous) DaneZ _____ From: DaneZ [mailto:david.guillotte@danez.no-ip.org] To: arnaud.quette@mgeups.com Sent: Sat, 08 Jul 2006 23:24:06 +0200 Subject: Fw: INFOSEC 500 XP en USB _____ Bonjour Arnaud, Je me

Roman, I don't think I already asked, but could you post the output of lsusb -v -d 06da:0003 Just to be sure that we're not exceeding some buffer limitations of the device. Best regards, Arjen -- Please keep list traffic on the list

Hi, Has anyone had success with the Dynamix 650VA, that uses the USB cable? I can't get megatec_usb to recognize it, I have tried both stable and development versions. Regards Glen Ogilvie

On Feb 18, 2014, at 10:15 PM, Charles Lepple wrote: > On Feb 18, 2014, at 5:55 PM, Thiago Tiedtke dos Reis wrote: > >> Hi, >> >> Recently I got three units of this nobreak [0]: > ... >> [0] http://www.sms.com.br/produtos/Nobreak-SMS/Manager-III-Senoidal > > According to the HCL, for the Manager III, you might want to try the blazer_ser (or in 2.7.1,

I looked through the faq, but couldn't find an answer to this. I'm trying to configure nut-2.0.4-26 on SuSE linux 10.2. In ups.conf, I have [myups] driver = belkinunv port = /dev/undefined desc = "Local UPS" I'm trying to find out what the port should be set to. lsusb shows: Bus 001 Device 005: ID 050d:0980 Belkin Components Device Descriptor: bLength

I was getting: "Can't claim USB device [0764:0501]: could not detach kernel driver from interface 0: Operation not permitted" so I manually installed the udev rules the source (I installed the Gentoo ebuild). I am now getting: # 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

Hi Arjen My apologies fro drifting off topic in the other mailing list...:-) On the bottom of the Belkin UPS unit - is the model number: F6C120auUNV The "au" is for Australia I think. "man belkinunv" states that F6C120-UNV is supported - and I assumed that the "au" would not prevent this. I plugged in the USB to gather the information you requested. My intention

Hi all, I?ve a UPS Liebert GXT3 500-3000VA with USB port. I?ve install NUT version 2.2.2 from repository packages for Debian Lenny. Linux kernel 2.6.26 I?ve try to use usbhid-ups driver in ups.conf [liebert] driver=usbhid-ups port=/dev/usb/hiddev0 Debian get the usb: # lsusb -v Bus 001 Device 002: ID 10af:0008 Liebert Corp. PowerSure Interactive UPS Device Descriptor: bLength

Hi, I have an UPS with only the marking D1000 on it and it came with Junda-Tech's UpsMate. Its USB id is 3344:0025, which is apparently a microprocessor. I've could get some of the HID interactions as described on the website, but there are some outstanding. Junda-Tech does not respond to any queries. Does anybody else have the same or a similar UPS with more information? What is the

So, I have this Mustek Powermust 600USB (no serial port) here temporarily. It seems to be a hid device. The output from "lsusb -v" and "newhidups -DDDDD" (with "generic" and "vendorid=06da") are (respectively): ----------------------------------------------------------------------------------------------- Bus 001 Device 002: ID 06da:0003 Phoenixtec Power

On Sep 10, 2015, at 8:49 AM, Rob Groner <rgroner at RTD.com> wrote: > > Charles, > > 3.16.6.-2-desktop I think that corresponds to this file: http://lxr.free-electrons.com/source/drivers/usb/core/devio.c?v=3.16 (but I don't see anything obvious there) What does "lsusb -vvv -d 2a37:" return? Usually I'd say run that as root when the driver isn't running,

Installed a new Tripplite Smart1500LCD on a CentOS 7 host using the usb connector. Nut does connect: $upsc ups battery.charge: 100 battery.runtime: 1407 battery.type: PbAC ... But after a half hour or so the connection is lost. Restarting nut re-establishes the connection. Any idea what might be causing the dissconnection?

On 06/19/2017 11:02 AM, Manuel Wolfshant wrote: > Thank a lot ! > Now, conclusions after attempting builds ( with no docs included since > attempting to enable them triggers the errors related to missing or > too old tools mentioned by me in an earlier message ) > - building against libsub 1.0 triggers the following 2 errors : > nutdrv_qx-nutdrv_qx.o: In function