similar to: No USB/HID UPS found

Hi Vladimir, I have got 2.0.3 working on netBSD 3.0. To get it operational I needed to do the following (most of this is from memory...). 1). Recompile kernel with uhid removed. If uhid ataches to the device then libusb is not able to. Have to allow generic usb driver ugen to claim port. >From dmesg usb0 at uhci0: USB revision 1.0 uhub0 at usb0 uhub0: VIA Technologies UHCI root hub, class

Hello, I wanted to see if there's any chance that NUT will support a few new TrippLite UPSes that we just bought: Sep 9 01:42:25 miko /kernel: uhid0: TRIPP LITE TRIPP LITE OMNIVS1500XL, rev 1.1 I grabbed the devel sources via cvs, but am having trouble building it when I enable the "newhidups" driver: gmake[1]: Leaving directory `/usr/local/src/nut/common' drivers/

Hi, colleagues! Something strange happens with a server. I am attempting to connect management interface of UPS with server via USB. In console I see a lot of errors: Mar? 7 13:42:04 xxx kernel: ugen2.2: <POWERCOM Co.,LTD HID UPS Battery> at usbus2 Mar? 7 13:42:05 xxx kernel: uhid0 on uhub6 Mar? 7 13:42:05 xxx kernel: uhid0: <POWERCOM Co.,LTD HID UPS Battery, class 0/0, rev 1.10/0.02,

I wrote a small app that monitors a Back-UPS ES500 UPS via the uhid0 interface. I want to run the daemon with as little privs as possible. gastest# ls -l /dev/uhid0 crw-rw---- 1 root operator 122, 0 Nov 12 05:26 /dev/uhid0 gastest# Is it safe to chmod o+r /dev/uhid0 ? Or is there a better way to drop privs of the daemon yet still be able to read from the device ? All I am doing is

I am looking at the newhid driver for this Pulsar EXtreme here but it gives odd results, for example there is no status variable :) eg debug level is '2' Checking device (0463/FFFF) (/dev/usb0//dev/ugen0) - VendorID: 0463 - ProductID: ffff - Manufacturer: unknown - Product: unknown - Serial Number: unknown - Bus: /dev/usb0 Trying to match device Device matches HID descriptor retrieved

Hi list- I'm having problems with TrippLite SMX1500LCD not being detected by NUT under FreeBSD 6.3-RC2. NUT 2.2.1 was installed from ports with the following options: WITH_USB=true WITH_SNMP=true WITHOUT_IPV6=true WITH_LIBUPSCLIENT=true WITH_CGI=true I use USB cable shipped with TrippLite and 'usbdevs -v' shows the following: ... Controller /dev/usb2: addr 1: full speed, self

Hi, Have anybody tried Cyberpower Value 600E (USB) under FreeBSD? usbhid-ups from nut 2.4.1 does not recognize (find) the device on my machine. [root at substance /usr/local/libexec/nut]# uname -a FreeBSD substance.dyndns.org 7.2-RELEASE FreeBSD 7.2-RELEASE #0: Fri May 1 08:49:13 UTC 2009 root at walker.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 [root at substance

Hi all, I’m new to NUT and have some trouble getting my new UPS to work. Since the HCL listed Powercom UHID models as „green“ I thought buying a Roline (German rebranded Powercom) model would be a good idea. The OS is FreeBSD: FreeBSD freenas-pmh.local 11.2-STABLE FreeBSD 11.2-STABLE #0 r325575+6aad246318c(HEAD): Mon Jun 24 17:25:47 UTC 2019 root at

On 2/5/14, 9:55 PM, Charles Lepple wrote: > On Feb 5, 2014, at 9:03 PM, Chris Duffy wrote: > >>> Please run this: >>> >>> /usr/local/libexec/nut/blazer_usb -a UPSonic -u root -D >>> >>> and send the output back to the list. >>> >> Output from the above command: >> >> 0.000000 debug level is '1' >>

On Feb 6, 2014, at 8:41 AM, Chris Duffy wrote: > 0.016485 Trying megatec protocol... > 0.017411 send: Q1 > 0.252545 read: (244.4 244.4 229.9 028 50.0 2.19 23.1 00000001 > 0.252589 Status read in 1 tries > 0.252602 Supported UPS detected with megatec protocol > 1.288032 send: Unknown error > 1.288085 Permissions problem: Input/output error

Peter, attached is a proposed patch to fix compilation of generic-hid.c when libusb's usb.h is not in /usr/include (but the -I flag is provided by "libusb-config --cflags"). It fixes the build under OS X, where Fink installs libusb with --prefix=/sw. I changed "usb.h" to <usb.h> so that 'make depend' wouldn't generate a dependency on 'usb.h' with

Hi all. I'm trying to get a CyberPower OR700LCDRM1U UPS working with NUT (via USB). I assumed this would be compatible since the OR2200LCDRM2U is. Clearly I'm wrong or missing something vital. I'm on FreeBSD, using the version of NUT from the ports tree (2.6.1). FWIW, I tried compiling from source with similar results. Here's my UPS in ups.conf: [ssups] driver=usbhid-ups

Peter Selinger wrote, > Hi Joe, > > I read between the lines that (a) you are using the newhidups driver, > and (b) it is working. Is this correct? You might want to post the > output of "upsc" just for the record. Whups, I should've been more clear and less terse -- it's been a long weekend putting the machines these are supporting into production! This

Hello world; been using nut atop Debian GNU/Linux (sid) for about two years by now, my configuration broke as I upgraded the machine this morning (headin' for kernel 2.6 to have full support for the new GBE NIC included). I read through the UPGRADE.gz instructions provided with the Debian packages and tried to fix things according to the instructions pointed out there, but things still just

Hi I'd like to know what you guys think to the following idea. Please be aware, C/C++ are not exactly my strongpoint (couldn't be much further from it actually..!), so I'm not sure whether this is all legal code. -- SYNOPSIS: Allow a newhidups subdriver to register that it can handle settings in ups.conf (and via -x on the command line), as per the normal serial drivers.

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

j T wrote: > >- allow the value to be NULL if a subdriver does not require > > initialization. > > Am I right in thinking that this is simply a case of doing: > > subdriver_t some_subdriver = { > /* ... */ > some_format_serial, > NULL, > } > > Rather than: > > subdriver_t belkin_subdriver = { > /* ... */ >

Hello Charles! As promised, I just checked out the CVS and recompiled everything. In the attached .txt is what is coming out from my UPS. I am wondering about all those zeroes. Also, this morning I plan to connect the UPS to a Win box running the monitoring program supplied with the UPS (UPSilon2000) and a USB sniffer program. If you have any suggestions on what to look for in the data,

Hello, I installed NUT and configured it for 2 MGE UPS's connected via USB. Debian etch NUT package: # dpkg -l nut*|grep ^ii ii nut 2.0.4-3 The core system of the nut - Network UPS Tools ii nut-usb 2.0.4-4 USB Drivers subsystem for the nut - Network UP Separately, with only one UPS defined in ups.conf, each one works fine (I specified specific serial numbers for either, with

I'm sure I'm missing something, but I can't seem to get NUT working on FreeBSD. bryce at tahiti[/usr/local/etc/nut]>cat ups.conf [belkin] driver = usbhid-ups port = auto vendorid = 050d #productid = 0751 bryce at tahiti[/usr/local/etc/nut]>s /usr/local/libexec/nut/usbhid-ups -DDDDD -a belkin Network UPS Tools - Generic HID driver 0.34 (2.4.1) USB communication driver 0.31