search for: hiddev1

...ied searching the list archives before posting here (I'm sure I'm not the first one to try to get this going) but they seem to be offline... The UPS is unfortunately USB based but I thought I'd give it a try anyway. Here is what I was able to do so far... I see my UPS comming up on hiddev1: Jun 22 23:11:31 mypbx devlabel: devlabel service started/restarted Jun 22 23:11:35 mypbx kernel: hub.c: new USB device 00:1d.0-1, assigned address 4 Jun 22 23:11:35 mypbx kernel: hiddev1: USB HID v1.00 Pointer [TRIPP LITE TRIPP LITE INTERNET725U ] on usb1:4.0 Jun 22 23:11:38 mypbx /etc/ho...

...es eg usb 3-1: USB disconnect, address 3 usb 3-2: new low speed USB device using uhci_hcd and address 4 But I don't know how to progress from here. I have used the following commands: mkdir /dev/usb mkdir /dev/usb/hid mknod /dev/usb/hid/hiddev0 c 180 96 mknod /dev/usb/hid/hiddev1 c 180 97 mknod /dev/usb/hid/hiddev2 c 180 98 mknod /dev/usb/hid/hiddev3 c 180 99 However, I'm not sure how to check that there is a link between hiddev0 and the USB device that's registering above. - In a fit of woeful optimism I have configured ups.conf to connect to hiddev0 but I get th...

I am currently trying to use your NUT program to monitor a SMART3000RMOD2U TRIPP LITE device. I find that it connects with the in the device folder as hiddev0 and if I connect a second device it connects under hiddev1. I attempted to use your software with the driver=usbhid-ups and port=auto, but when I try to discover it it can't be found. Then when I run the command /sbin/usbhid-ups -a ups1 -D where ups1 described the driver and port combination, I get the following output: This Tripp Lite device (09ae/...

Hi Patrick, in February, you tried to post the below message to the nut-upsuser list, but the post was rejected because you were not subscribed to the list. Unfortunately, you did not subscribe and re-post it. Anyway, I have been working on Tripp-Lite support for newhidups recently, and I wonder if you have any feedback. Did you ever get this device to work? >From the information you sent,

...nd handle our 7 servers with it in the office. Technical details: NUT version: BSD box: Network UPS Tools upsd 2.0.5 Linux box: Network UPS Tools upsd 2.0.5 Driver config: [ups1] driver = newhidups port = /dev/usb/hiddev0 [ups2] driver = newhidups port = /dev/usb/hiddev1 (this is the linux one. on FreeBSD, it's /dev/ugen{0,1}) startup output on the BSD box: # /usr/local/etc/rc.d/nut start Network UPS Tools - UPS driver controller 2.0.5 Network UPS Tools: 0.28 USB communication driver 0.28 - core 0.30 (2.0.5) No matching HID UPS found Driver failed to start (...

...for newhidups > >>> recently, and I wonder if you have any feedback. Did you ever get this > >>> device to work? > >> It works ok under the old hidups driver. > >> The only annoyance is that when the machine is rebooted, the ownership > >> of /dev/hiddev1 reverts to root. I never got around to making an > >> automatic process to make sure which device it gets attached to > >> (although it always seems to be hiddev1). I could do that and put > >> it into the startup script, but so far I have been checking and > >&gt...

...'Bus 003 Device 063' and 'Bus 003 Device 064') Since there is no flag for manufacturer, I had to go with serial. This is my new ups.conf: [ups1] driver = usbhid-ups port = /dev/usb/hiddev0 serial=000000000 [ups2] driver = usbhid-ups port = /dev/usb/hiddev1 serial=1HCG4700J When I run upsdrvctl start ups1, it starts /lib/nut/usbhid-ups -a ups1 but no -x flag. Starting usbhid-ups manually with the -x serial=000000000 and -DD flag shows: Checking device (0463/FFFF) (003/064) - VendorID: 0463 - ProductID: ffff - Manufacturer: MGE UPS SYSTEMS - Pr...

...ise. > > Thanks! > Martin > > > ** Attachment added: "ups_problem.txt" > > https://bugs.launchpad.net/ubuntu/+source/nut/+bug/779512/+attachment/2636234/+files/ups_problem.txt > What is strange, as per your next mail, is that "ls /dev/usb" shows "hiddev1"! Can you please forward us an excerpt of your system log, using the "usb" pattern. cheers, Arnaud -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20111216/d9ca5ac1/attachment.html&g...

On Oct 12, 2014, at 8:28 PM, Gene Heskett <gheskett at wdtv.com> wrote: > Its unk because whats plugged in seems to be blocking the rear name plate. > About all I can recall is that its big, 3 battery unit, rated somewhere > north ob 1250 VA. > > Its an 050D:0751 Belkin. > > What driver should I use, and what file is that set in? Looks like it is in usbhid-ups. If

Greetings; Its unk because whats plugged in seems to be blocking the rear name plate. About all I can recall is that its big, 3 battery unit, rated somewhere north ob 1250 VA. Its an 050D:0751 Belkin. What driver should I use, and what file is that set in? The nut version presently and freshly installed is from the Ubuntu 10.04.4 LTS repo's. Probably old, but IIRC it also worked with

..., what file do I add that too? I also note that in the original bootup discovery it was hiddev0/hidraw6, the same as the latest plug in report, so that also appears stable. But ls -l /dev/usb: crw-rw---- 1 root root 180, 0 2014-10-12 18:51 hiddev0 crw-rw---- 1 root root 180, 1 2014-10-12 18:51 hiddev1 crw-rw---- 1 root root 180, 2 2014-10-12 18:51 hiddev2 crw-rw---- 1 root root 180, 3 2014-10-14 08:44 hiddev3 crw-rw---- 1 root lp 180, 4 2014-10-13 05:50 lp4 crw-rw---- 1 root lp 180, 5 2014-10-13 05:50 lp5 shows that hiddev3 is the one created by my cable unplug/replug. Call me confused at b...

> 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

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

...------- And, /dev/hidraw0 (and all associated) is owned by root:root despite 62_*.rules for udev stating it should be uucp. ------------------------ [root at coyote ups]# ls -l /dev/hid* crw-rw---- 1 root root 180, 0 2009-12-27 08:52 /dev/hiddev0 crw-rw---- 1 root root 180, 1 2009-12-26 11:17 /dev/hiddev1 crw-rw---- 1 root root 253, 0 2009-12-27 08:52 /dev/hidraw0 crw-rw---- 1 root root 253, 1 2009-12-26 11:17 /dev/hidraw1 crw-rw---- 1 root root 253, 2 2009-12-26 11:17 /dev/hidraw2 crw-rw---- 1 root root 253, 3 2009-12-26 11:17 /dev/hidraw3 crw-rw---- 1 root root 253, 4 2009-12-26 11:17 /dev/hidraw4...

...logic, too. > > Example of "bizzare" UPS configuration from > http://www.networkupstools.org/features/ > > This machine can run, if at least two two of these three UPSes has > enough power: "local UPS Smart UPS 1000 hiddev0", "local UPS Smart UPS > 1000 hiddev1", "remote UPS spare1 connected to machine upsfarm". Ignore > status of "local UPS Back UPS 500 hiddev2", which powers another machine > (but this UPS and machine connected to it must be shot down, before this > server will go down). > > ********************...