similar to: Tripplite OMNI1000LCD Watchdog

Dean K. Gibson wrote: > > My Belkin UPS 1000 failed about a month ago; all of a sudden it > reported a battery failure. Since the Belkin logs showed this as in > instant transition from 99% to 22%, I assume a circuit board failure, > not a battery failure. Similarly, one Belkin UPS 500 circuit board > failed after I used my 100W amateur radio transmitter (not connected to

Hi all: I am trying to get a TrippLito OMNI1000LCD working with nut. Even with the development branch, I get the following.... upsdrvctl start Network UPS Tools - UPS driver controller 2.1.0 Network UPS Tools: HID UPS driver 0.13 (2.1.0) Warning: This is an experimental driver. Some features may not function correctly. Detected Tripp Lite TRIPP LITE UPS on port /dev/usb/hiddev0

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 > +++

I'm working on a gentoo server with Nut 2.0.5-r1 and libusb-0.1.12. I originally tried the hidups driver which seemed to work, but produced a large amount of unhandled events. Then I tried the newhidups which told me my ups wasn't supported. When I try using tripplite_usb -u root -DDDD /proc/bus/usb/002/002 I get that there isn't a match. But when I try using tripplite_usb -DDDD

Hello NUT-UPSUSERS, I would just like to try and help other and indicate that I was able to use the development trunk and get the Tripp Lite OMNI1000LCD UPS (USB) working with the newhidups drivers on Gentoo Linux. The one that is currently available at many local Costco stores and online. In case others need to replicate, I've attempted to document my steps over here.

Thanks again for your help, Charles. I was able to install the Tripp Lite software on my Ubuntu machine, and it sort of works. It does something which continually changes the USB device ID of the UPS, and prints voluminous error messages in the log. However, one of the things that it can do is to schedule a UPS shutdown, which Nut does not know how to do. So I monitored the USB port with

I have a TrippLite AVR550U that my company uses several individual Linux boxes in one large system, all running Ubuntu 18.04LTS, and all will be using the package version of nut - 2.7.4. In my scenario, our usage case is for the PCs to all shut down, followed by the individual UPSes, when mains power is removed from the whole system. (This isn't a typical setup for UPS, but it's what

Can anyone help getting a Tripplite SU2200XL to work with nut 2.0.3 using the supplied serial cable? Starting the ups service yields: Starting tripplitesu: Network UPS Tools - Tripp Lite SmartOnline driver 0.02 (2.0.3) Unable to detect Tripp Lite SmartOnline UPS on port /dev/ttyS0 I also have Tripplite's PowerAlert 12 software installed and when run it finds the UPS without a problem. So

Hi everybody, If we let the feature running, it appears that the driver gets unbound after a while ( variable from quarter of hour to 6 hours ) and cannot reconnect. This behavior appear with both MGE Ellipse ASR and non-ASR models with connection to an UHCI and OHCI controllers. The USB core is from 2.4.28 kernel. We use nut-2.0.3. Start, powerfail and recovery detections, UPS shutdown work

I am using NUT 2.0.2 on SuSE Linux 9.2 which is attached to a Tripplite SmartPro Net 2200 UPS. I have Nut using the included tripplite driver, and it is communicating with the UPS correctly. The battery voltage of theTripplite reported by the NUT server is 13.5VDC. If I attach the UPS to a Windows 2000 server running Tripplite's PowerAlert software, the battery voltage is being reported as

[please use reply-all to include the list] On May 20, 2019, at 5:30 PM, Steven Bixby wrote: > > I have a TrippLite AVR550U that my company uses several individual Linux boxes in one large system, all running Ubuntu 18.04LTS, and all will be using the package version of nut - 2.7.4. In my scenario, our usage case is for the PCs to all shut down, followed by the individual UPSes, when

Greetings, Any suggestions? I think I'm close but I can't quite get tripplite_usb to talk to my OMNI1000LCD. I'm new to NUT and couldn't find an answer using Google. With any luck, I've simply missed the obvious. The system I'm using, kaylee, is a debian stable system with some debian testing installed and a 2.6.15.4 kernel. I downloaded NUT 2.0.3 and built it from

Hello, I am hoping someone can point me in the right direction. I am setting up a new UPS, most things seem to be working except the UPS turns off immediately during a test shutdown using///"//upsmon -c fsd".//No delay before the UPS turns itself off leaving no time for the server to shutdown properly. I have attempted to set the delay higher using "upsrw -s

Good morning! On a CentOS 6.4 / 64 bit server I have installed the watchdog 5.5 package. The rpm -qi watchdog states: The watchdog program can be used as a powerful software watchdog daemon or may be alternately used with a hardware watchdog device such as the IPMI hardware watchdog driver interface to a resident Baseboard Management Controller (BMC). ... This configuration file is also used to

I am trying to get a TrippLite SU1500RTXL2Ua working with nut on Mandriva 2007.1, is there a particular version of nut needed to get this to work? At first I tried nut 2.0.5 (which came with 2007.1) but it wouldn't work, and then research showed it was an older version of nut. So nut-2.2.1-2 src rpm was pulled from Mandriva 2008.1, the binary rpm built, and nut and nut-server installed from

Dear Developers, I've released a patch against openssh-2.5.2p2. The patch adds heartbeat (keepalive) function to ssh(1), and watchdog timeout function to sshd(8). The watchdog timeout is intended to terminate user's processes as soon as possible after the link has been lost. http://www.ecip.tohoku.ac.jp/~hgot/sources/openssh-watchdog.html The combination of the heartbeat and the

Hi! I''m trying to run w83627hf_wdt.ko watchdog driver in domain 0 (xenlinux 2.6.10-xen0), but the driver doesn''t seem to work (the machine reboots all the time after the watchdog-timeout set in BIOS). Is there something that could prevent the driver from accessing the watchdog-hardware (io-ports/registers) ? The watchdog-driver is very simple, and you can find it in

This patch is based on one which has been in XenServer for a very long. To keep the trend of documentation going, it also corrects the new command line document. -- Andrew Cooper - Dom0 Kernel Engineer, Citrix XenServer T: +44 (0)1223 225 900, http://www.citrix.com _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel

I am having an issue running NUT and using an TrippLite OMNI900LCD. When I run ./upsdrvctl start I get : [player@V0002-S002 bin]$./upsdrvctl start Network UPS Tools - UPS driver controller 2.1.0 Network UPS Tools: 0.28 USB communication driver 0.28 - core 0.30 (2.1.0) Detected a UPS: Tripp Lite /TRIPP LITE UPS Using subdriver: TrippLite HID 0.1 (experimental) dstate_setflags: base variable

Jeremy, while originally I had hoped this patch, sitting in xen/next, would get pushed for .37, that didn''t happen and now the .38 merge window was missed too. Trying to get this to Linux on my own seems inappropriate, so can I hope that you will include this with whatever other changes you intend to push for .39? Thanks, Jan _______________________________________________ Xen-devel