similar to: HP T1500 INTL

Displaying 20 results from an estimated 400 matches similar to: "HP T1500 INTL"

2009 Mar 01
1
[nut-commits] svn commit r1800 - in trunk: . data drivers
Citeren Arnaud Quette <aquette op alioth.debian.org>: > Modified: trunk/drivers/tripplite-hid.c > ============================================================================== > --- trunk/drivers/tripplite-hid.c (original) > +++ trunk/drivers/tripplite-hid.c Sun Mar 1 19:56:31 2009 > @@ -84,6 +84,8 @@ > > /* HP R/T 2200 INTL (like SMART2200RMXL2U) */ > {
2010 Mar 09
1
Tripp-Lite SU2200XLA problem
Hi, I kludged support for the TrippLite SU2200XLA into nut-2.4.3 as follows: --- ./drivers/tripplite-hid.c.0 2010-03-03 15:53:20.000000000 -0500 +++ ./drivers/tripplite-hid.c 2010-03-03 15:53:40.000000000 -0500 @@ -81,6 +81,8 @@ { USB_DEVICE(TRIPPLITE_VENDORID, 0x4002), battery_scale_1dot0 }, /* e.g. TrippLite SmartOnline SU1500RTXL2ua */ {
2010 Feb 18
2
HP R1500 G2 UPS
Hi, I have a HP R1500 G2 UPS and want to get it working under Debian Lenny - as this OS is not supported by HP I'm trying to use nut for it - but I can't get it working. Do I have any chance to get the UPS running with nut. I also tried different drivers but had no luck either. Or does anyone has experience with HP UPS under debian ? Any help would be nice ! I tried /lib/nut/usbhid-ups
2009 Feb 25
3
driver for HP/Compaq T750 ?
Hi, I own a UPS HP T750. Is there a driver for this UPS (either serial or USB)? thx kp
2010 Sep 11
1
TrippLite SMART1000LCD
These patches allow this device to function in nut.. diff --git a/trunk/drivers/tripplite-hid.c b/new/drivers/tripplite-hid.c index c36da98..dddd13c 100644 --- a/trunk/drivers/tripplite-hid.c +++ b/new/drivers/tripplite-hid.c @@ -71,6 +71,8 @@ static usb_device_id_t tripplite_usb_device_table[] = { { USB_DEVICE(TRIPPLITE_VENDORID, 0x2005), battery_scale_0dot1 }, /* e.g. TrippLite
2005 Dec 05
3
Powerware 5125 works ?
Hi there. At the moment I'm trying to get my HP T1500 XR (Powerware 5125) UPS to work with NUT. NUT registers that the UPS is on battery/online, but I just cant get the program to shut down the computer I'm using the original cable (thus I didn't enter anything in the ups.conf file) If I remove the cable and run the daemon/program the computer will shutdown after x minutes defined in
2019 Feb 12
4
Monitor Eaton 93PS UPS
I also operate an HP T1500 G3 which it's an Eaton made UPS. Connected on usb i get frequent communication errors and data aquisition stopped. Mine has a serial connection, also. Operating via serial has no trouble. Maybe it's something related to usb setting in bios, i.e. Legacy mode, speed setting, etc. However on serial mode looks like the eaton or hoe power protector software does not
2017 Dec 04
2
SNMPv3 fails when more than one UPS is configured in ups.conf
Hi Charles, Running upsdrvctl -D start on the host with all three configured to SNMPv3 kicks out 56 different "unhandled ASN 0x81 from ..." lines on all three but importantly they all start up and keep running. I'm starting to suspect the startup is taking so long that systemd is timing out and killing it. time -p reports real time of 133.27. I'm not a fan of systemd but
2009 Aug 02
1
MGE Evolution mge-utalk Driver Not Connected error
Hi All, I have an mge pulsar esv 14+ rackmount UPS connected via straight through serial cable to a USB to serial adaptor (My motherboard does not have a native RS232 port). I am running Ubuntu Server 9.04 x64, and nut 2.4.1-2ubuntu4 installed via APT. I am getting the error: Poll UPS [ups1 at localhost] failed - Driver not connected My conf files: (ups.conf) [ups1] driver=mge-utalk
2009 May 05
5
upsd flapping in the breeze
Hi, I have had a long standing problem with NUT talking to 110V MGE UPSs on FreeBSD, I was recently investigating again and noticed that upsd seems overly noisy, eg.. May 5 03:50:36 egbert upsd[96662]: UPS [ups1] data is no longer stale May 5 03:50:36 egbert upsd[96662]: Data for UPS [ups1] is stale - check driver May 5 03:50:36 egbert upsd[96662]: UPS [ups1] data is no longer stale May 5
2013 Oct 09
2
Updated to 2.6.5, previously-working APC SmartUPS now fails completely
(Note that I mentioned this *was* previously working with an older version of Nut). [irs2-ups1] driver = snmp-ups port = irs2-ups1.sum.naoj.org mibs = auto community = private irs2-ups1.sum.naoj.org responds to pings. On Tue, Oct 8, 2013 at 3:55 PM, Tim Rice <tim at multitalents.net> wrote: > On Tue, 8 Oct 2013, Philip Tait wrote: > > > Here is the upsc
2008 Jul 22
1
MGE Pulsar EX1500 RT comms problem
Hi, I have the above UPS connected to a FreeBSD 6.2 box and it shows 'data stale' very frequently (every few minutes). I have tried the usual trick of setting maxage, poll interval, etc etc but to no avail. When I wind up logging I see (on mge-shut) entering shut_get_report(id: 0d, len: 1800) shut_wait_ack(): ACK received entering shut_get_report(id: 16, len: 1800) shut_wait_ack():
2007 Apr 20
2
Multiple UPS monitoring, relaying
Hello, I've got a setup with NUT, where we've got two UPSes, ups1 and ups2. UPS1 supports our servers, while UPS2 supports our desktop boxes. We monitor both of them via USB on a box now called "upsmon". The interesting point comes here. We monitor both UPSes on the upsmon box, but if UPS2 fails, which supports our desktop boxes, NUT shouldn't initiate a shutdown in
2007 Apr 20
1
USB problem as user
Hello I'm having a bit of a trouble to set up a Back-UPS on a production box. We're using the newhidups driver for this module here, in the office, and I'd like to monitor the one, out in our server farm. The situation is the following: # /lib/nut/newhidups -u root -DD -a ups1 2> ups1.out Network UPS Tools: 0.28 USB communication driver 0.28 - core 0.30 (2.0.5) this one worked
2011 Mar 14
1
UPS Support
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
2011 Jul 26
0
[RFC] PowerChain: add LIST POWERCHAIN and GET POWERCHAIN to the client (network) protocol
Hi, this is the 2nd part of the PowerChain RFC. 2011/6/13 Arnaud Quette <aquette.dev at gmail.com> > As already presented, the links below will describe in details the > PowerChain notion: > > https://wiki.ubuntu.com/ServerOneiricInfraPower > https://wiki.ubuntu.com/ServerOneiricInfraPower#PowerChain%20design >
2006 Feb 25
3
Compaq R1500 UPS and Linux
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 - -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi! Has anyone gotten it working at all with Linux :) I picked one up for thiry bucks and would love to monitor it! Liz - -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Darwin) iD8DBQFD/5fEIACpLcG4dhwRAmeCAJ9+8FGXqKoOlZdkw/KFXb9n0PEemwCdHaoD NVnv7JjmBAjNsExK6WzAdnA= =pcPX - -----END PGP
2013 Oct 09
0
Updated to 2.6.5, previously-working APC SmartUPS now fails completely
On Tue, 8 Oct 2013, Philip Tait wrote: > Here is the upsc output: > > # /usr/local/ups/bin/snmp-ups -DD -a irs2-ups1 > Network UPS Tools - Generic SNMP UPS driver 0.68 (2.6.5) > 0.000000 debug level is '2' > 0.000327 SNMP UPS driver : entering upsdrv_initups() [snip] > 4.457750 No supported device detected I'm using a APC smart ups with a
2012 Mar 04
2
NUT Two Apc UPSes on Windows
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 ---
2009 Nov 15
3
two MGE Ellipse 1500 ups via usb
Hi, I've got two MGE Ellipse 1500 UPS connected via usb to an ubuntu jaunty system with nut and libupsclient1 2.4.1-2ubuntu4. As soon as I start the driver for the second one, they start fighting each other and I get no data. I found an older post to this list that said: If you want to monitor multiple UPSes through usbhid-ups, you *must* make sure that each one can be uniquely identified