similar to: usbhid-ups pull request for consideration

Hi Stephen, It's been a little busy at home, so I haven't had a chance to go over the pull request in depth, but I didn't want you to think it hadn't been considered. On Apr 19, 2014, at 1:23 AM, Stephen J. Butler wrote: > I've added a pull request with changes to drivers/libusb and drivers/usbhid-ups mainly. They are to resolve issues I encountered when setting up a

I'm having trouble with the usbhid-ups driver and Windows. NUT won't connect to an APC SmartUPS 3000 via USB. I've had good success with NUT and Raspbian as well as NUT and Windows using the tripplitesu driver. The current system is: Windows 7 Enterprise 64 bit NUT 2.6.5-6 installed from MSI installer downloaded from networkupstools.org libusb-win32-bin-1.2.6.0 installed and

On 2015-10-23 5:42, Charles Lepple wrote: > So the interesting part is that I was testing the master branch yesterday (same commit) on an older Debian box (3.16 kernel). The driver had trouble starting, but once it got going, it has been running continuously. > > I'm not really sold on this approach (due to the testing needed on other hardware), but this pull request reworks the USB

Hi, I'm having a hard time configuring a Mustek Powermust 600VA ups to work via USB with nut. I read somewhere that nut works OK via the rs232 cable, but unfortunately I don't have a COM port in my computer. The kernel detects the ups as an Xbox pad :) and loads the xpad module. I tried running /lib/nut/megatec with different /dev/ttySx but it displays megatec protocol UPS was not

I'm attempting to get a HP R1500 G2 UPS working with Solaris 10 connected via USB. Thanks to Arnaud's patch to drivers/tripplite-hid.c found at http://lists.alioth.debian.org/pipermail/nut-upsuser/2010-February/005887.html things mostly work. upsc ups01 shows a couple of things that don't look quite right. [....] battery.temperature: -234.1 [....] ups.alarm: No battery installed!

See comments below. > -----Original Message----- > From: Charles Lepple [mailto:clepple at gmail.com] > Sent: Friday, August 29, 2014 5:35 AM > To: barry at skrypnyks.com > Cc: nut-upsuser at lists.alioth.debian.org > Subject: Re: [Nut-upsuser] Smart1500lcdt will not connect with usbhid-ups > > On Aug 28, 2014, at 6:49 PM, Barry Skrypnyk <barry at skrypnyks.com>

On Aug 29, 2014, at 2:02 PM, Barry Skrypnyk <barry at skrypnyks.com> wrote: > See comments below. > >> -----Original Message----- >> From: Charles Lepple [mailto:clepple at gmail.com] >> Sent: Friday, August 29, 2014 5:35 AM >> To: barry at skrypnyks.com >> Cc: nut-upsuser at lists.alioth.debian.org >> Subject: Re: [Nut-upsuser] Smart1500lcdt will

Hi List, I recently picked up a Tripp Lite SMART1500LCDT while they were on sale to pair with my home server, and have tried getting it set up with NUT, since it seems to be supported. I can get the whole NUT stack up and running, but the driver seems to only stay up for a couple minutes before crashing out. I've uploaded the level 6 debug output of the driver (with my serial number

I talked to Tripp Lite Technical support. Their policy is that they only support Fedora and SUSE. There is no one there that could help with Ubuntu or NUT issues. The only answer they could give me was to port the rpm files to Ubuntu and use them. This is way beyond my experience level. I will go to the local electronics store and buy a cheap USB 2 hub to see if that works. I will post the

Barry, I have had success with NUT on Debian and an EATON 5E2000IUSB-AU 5E 2000VA/1200W UPS With 3 x OUTLETS which I believe is good value. I would believe the the EATON ?5E 1500VA/900W UPS With 3 x OUTLETS would work just as well. The 1500VA also uses the same batteries as the 2000VA so I would believe it would run its raited load longer than 2000VA. My eight drive RAID driver uses less that

# ldd /lib64/nut/usbhid-ups linux-vdso.so.1 (0x00007ffdfe3e3000) libusb-0.1.so.4 => /lib64/libusb-0.1.so.4 (0x00007f98526e6000) <-- from libusbp-compat-0.1.5-r2 libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f98524ca000) libc.so.6 => /lib64/libc.so.6 (0x00007f985212f000) libusb-1.0.so.0 => /lib64/libusb-1.0.so.0 (0x00007f9851f17000) <--

I'm facing a looming deadline for getting this working, so I'm hoping someone experienced can weigh in on this. I'm getting errors in the Event Log when stopping the service: 1. Error stopping upsd (2) 2. Error stopping upsmon (2) Is there a detailed log somewhere? How can I track this down and find out what they mean? Or does someone know? Also, these three commands result in

Joel Peshkin wrote: > > I hacked in the following additonal changes... > > Index: newhidups.c > =================================================================== > RCS file: /cvsroot/nut/nut/drivers/newhidups.c,v > retrieving revision 1.1.1.1.8.6.2.21 > diff -u -r1.1.1.1.8.6.2.21 newhidups.c > --- newhidups.c 7 Nov 2005 22:14:20 -0000 1.1.1.1.8.6.2.21 > +++

On Aug 28, 2014, at 6:49 PM, Barry Skrypnyk <barry at skrypnyks.com> wrote: > I have searched the archives and googled this problem with usbhid-ups. I would really appreciate any help anyone could offer to solve the problem. > > System: Ubuntu 14.04.1 Trusty Tahr Which kernel version are you using? > Installed nut from Ubuntu repositories ? nut 2.7.1 > > Ups.conf file

I have searched the archives and googled this problem with usbhid-ups. I would really appreciate any help anyone could offer to solve the problem. System: Ubuntu 14.04.1 Trusty Tahr Installed nut from Ubuntu repositories - nut 2.7.1 Ups.conf file maxretry = 3 # user = nut [TrippLite] driver = usbhid-ups port = auto productid = 3016 desc = "Tripp Lite UPS,

Charles and Wolfy, Thanks for the replies. I added some responses below. I think I got the driver debugging right, but let me know if it is off. I should note: The CentOS 7.6 machine I have been testing with is a virtual machine (running on VMware ESXi 7.6). At least 1 customer and I have seen the same issue on VMs and physical boxes, so I don’t think that matters, but if it does let me know.

Ladies and Gentlemen, I have been playing around with Arnaud's new HAL stuff a bit, and have some questions and observations. First my configuration: my UPS (Peter may remember): ups.mfr: APC ups.model: Back-UPS ES 650 ups.productid: 0002 ups.firmware: 818.w1.D ups.firmware.aux: w1 kernel: 2.6.18-92.1.6.el5 hal-0.5.8.1-35.el5, nut based on nut-2.2.2.tar.gz, small changes to

This issue has been occurring for years on my setup. OS: Gentoo most recent kernel: 4.1.12 UPS: Eaton Powerware 9130 rackmount 2000kVA, connected via USB The upsdrv service dies and must be restarted several times a day. Zero output to dmesg or any other log other than failed reattempts reporting no such file or directory errors. "/lib64/nut/usbhid-ups -DDD -q -a powerware" exited 1

I was doing some testing with the 2.6.0-1 beta Windows installer and a Cyber Power CP1350PFCLCD UPS, and ran into an infinite loop in the usbhid-ups driver if the UPS is lost on the UPS bus. This is on a Windows XP SP3 system. USB device access is via libusb 1.2.4.0 (driver mode, not filter) in case that matters. Everything seems to work just fine so far while the UPS is connected (so kudos,

Hi, I've got a question about managing two UPSes under NUT. I have two similar model APC usb-connected UPSes to work with, but don't know how to manage them simultaneously from under Windows. Long story short, my ups.conf looks like this: --- ups.conf --- [ups1] driver= usbhid-ups port= auto serial=AS1054340323 [ups2] driver= usbhid-ups port= auto serial=AS1026662626 ---