Displaying 20 results from an estimated 2000 matches similar to: "Fw: usbhid-ups and APC Smart-UPS 1500"
2010 Nov 12
1
usbhid-ups and APC Smart-UPS 1500
Hello !
I'm totally new with Linux, just migrating from NetWare.
Our brand new server runs SuSE Linux Enterprise Server 11 Service Pack 1
SLED11 ships with NUT 2.2.2-69.11
I'm trying to setup NUT to communicate with our UPS over the USB cable.
First, I've tried with a "standard" ups.conf. Error message : device is (or not yet) supported.
Second attempt, including productid
2009 Jul 22
1
Cannot generare SSPI context
OS: SUSE Linux Enterprise Desktop(SLED) 11
wine version installed on SLED11:
samba-3.2.7-11.6.i586.rpm
samba-client-3.2.7-11.6.i586.rpm
samba-winbind-3.2.7-11.6.i586.rpm
wine is also installed on SLED11: wine-1.1.26-1.1.i586.rpm
MS SQL Server 2000 SP3 is a Member server.
SLED11 is also a MS Active Directory Domain member/client
Login as Administrator on the MS AD Domain from SLED11
run the
2014 Sep 23
2
upd and OpenBSD (was Nut 2.7.2 on OpenBSD 5.6 with APC USB UPS)
On Sep 23, 2014, at 3:55 AM, Henning Brauer <hb-nut at bsws.de> wrote:
> We have upd(4) attaching to these devices now. Either nut needs a
> driver getting status from upd (trivial, will show up in the
> hw.sensors sysctl tree) or we need some way for nut still being able
> to talk to the ups directly, without upd and nut interfering with each
> other.
While a upd(4) driver
2014 Sep 23
0
Nut 2.7.2 on OpenBSD 5.6 with APC USB UPS
* Henning Brauer <hb-nut at bsws.de> [2014-09-20 13:39]:
> * Charles Lepple <clepple at gmail.com> [2014-09-20 01:12]:
> > On Sep 19, 2014, at 5:18 PM, Stan Gammons <sg063015 at gmail.com> wrote:
> > > Looks like this patch fixed the problem. I see the status change now.
> > Good to hear.
> > I'm not familiar with the OpenBSD release process. Is
2007 Mar 06
1
APC SmartUPS 1500 not working for newhidups and usbhid-ups
Hi,
Can't get newhidups (2.0.5) or usbhid-ups (SVN trunk) to work
2.0.5 hidups seems to work, but I was hoping for more information...
like temperature, etc.
Tried newhidups and usbhid-ups, but they don't seem to detect my UPS...
should I switch back to serial? Will I get more information? (trying not
to move back to apcupsd, since i have a mixed environment)
Here is some debug
2006 Aug 25
1
Problems with APC Smart-UPS 1500 USB and, newhidups driver
Paolo,
Try
sudo /lib/nut/newhidups -DDD -u root -a SmartUps1500
newhidups would only run on my computer if I ran it using sudo and as
root user. I know this indicates a problem with the USB permissions,
but I could not, for the life of me, get the permissions to change when
I plugged the UPS in. I know this isn't a true fix, but it worked for me.
--
~Brian Foster
2006 Aug 25
1
Problems with APC Smart-UPS 1500 USB and, newhidups
Great! Please let the mailing list know if you run into any further
problems. -- Peter
Paolo Pedroni wrote:
>
> Alle 16:38, venerd=EC 25 agosto 2006, hai scritto:
> > Paolo,
> >
> > I recently fixed some bugs regarding the report descriptor retrieval.
> > Please try it with the newest development version from SVN. You can
> > follow the instructions at
>
2013 Jul 09
0
Hope for APC Smart UPS 1500
Hi,
we bought two Smart-UPS X 1500 FW:UPS 09.1 / ID=20
lsusb -v:
Bus 002 Device 002: ID 051d:0003 American Power Conversion UPS
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor
2013 Jul 10
0
Hope for APC Smart UPS 1500
On Jul 9, 2013, at 9:04 AM, Gregor Burck wrote:
> we bought two Smart-UPS X 1500 FW:UPS 09.1 / ID=20
[...]
> I see there should be problems to get it work with a free daemon like nut, but are there some hints using it?
> In my ups.conf I tried:
>
> [apc001]
> driver = apcsmart
> port = auto
> desc = "Smart APC"
Only the USB drivers should
2013 Dec 17
0
APC Smart-UPS 1500; system shutdown is not initiated.
On Dec 8, 2013, at 10:41 PM, Christian wrote:
> test.battery.start.deep - Start a deep battery test
> test.battery.start.quick - Start a quick battery test
Ideally, you would want to do a deep test with a dummy load, like a lamp, so as not to put your server in danger of getting cut off again. You can probably do the test.battery.start.quick test with the server still plugged into the UPS,
2013 Dec 17
1
APC Smart-UPS 1500; system shutdown is not initiated.
Charles,
the unit has two redundant power supplies, with only one hooked up to
the UPS. So I should be able to do a deep test with the machine itself,
right? I have tried it, but it aborts at some point...
For the quick test, it discharges the battery a bit, then recharges, but
once it is back to 100%, upsc still gives me:
ups.test.result: No test initiated
Is that expected?
Best,
Christian
2006 Aug 25
1
Problems with APC Smart-UPS 1500 USB and newhidups driver
Whenever I try to use the newhidups driver with my new UPS I get the following
message:
#/lib/nut/newhidups -DDD -a SmartUps1500
Network UPS Tools: New USB/HID UPS driver 0.28 (2.0.4)
debug level is '3'
[...skip unrelevant device...]
Checking device (051D/0002) (001/005)
- VendorID: 051d
- ProductID: 0002
- Manufacturer: American Power Conversion
- Product: Smart-UPS 1500 FW:601.3.I USB
2010 Apr 29
1
APC Smart-UPS Pro 1500 USB monitoring trouble
Hi there... nut 2.4.3 kicks an error at me when I try
to talk to my UPS. machine is linux 2.4.21-32.ELsmp
with libusb-0.1.8-3 package update.
# /usr/local/ups/bin/upsdrvctl start
Network UPS Tools - UPS driver controller 2.4.3
Network UPS Tools - Generic HID driver 0.34 (2.4.3)
USB communication driver 0.31
Using subdriver: APC HID 0.95
libusb_get_interrupt: error submitting URB: Invalid
2013 Jul 09
2
Hope for APC Smart UPS 1500
Hi,
we bought two Smart-UPS X 1500 FW:UPS 09.1 / ID=20
lsusb -v:
Bus 002 Device 002: ID 051d:0003 American Power Conversion UPS
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor
2007 Dec 18
2
Problem with APC SMART SC 1500
Hello,
I want to manage my SMART APC with nut 2.0.3 on Fedora Core 4. But i have this
output at start of my ups:
D?marrage de apcsmart :Network UPS Tools (version 2.0.3) - APC Smart protocol
driver
Driver version 1.99.7, command table version 2.0
Detected Smart-UPS SC1500 [5S0713T66466] on /dev/ttyS0
[ OK ]
D?marrage de upsd
2007 Jan 12
1
Trouble connecting to apc smart 1500 via serial cable
Hello.
I've been running a two machine setup with a mge-shut for some time
without problems, and now I'm configuring a three machine setup with an
APC Smart 1500.
The UPS has three machines connected to it, in a peculiar way: one
windows machine is connected via USB. The second windows machine is
using an agent to monitor messages from the first windows machine. Then,
I have a GNU/Linux
2009 Feb 28
2
APC SMART-UPS 1500 always reporting LB
Using nut v2.2.2, and the APC serial cable.
I have a client who's APC SMART-UPS 1500 (circa 2000) is always reporting LB. The batteries were old so they were replaced two weeks ago with brand new batteries. UPS still reported low batteries...
I ran a calibration and a test on the unit (using the nut upscmd utility)
During those tests, the battery charge on the unit goes to zero and slowly
2016 Apr 22
0
R - Understanding output of the Knoxtest (Package (surveillance))
The function knox of the "Surveillance" package performs Knox test for
space-time interaction. The output is supposed to give the numbers of
events that occur in a specific distance in space and time define by the
function arguments. This function also perform a Monte Carlo permutation
test, which give the estimated value (based on a random distribution) which
are supposed to be compared
2013 Dec 09
2
APC Smart-UPS 1500; system shutdown is not initiated.
Charles,
thanks for your detailed answer.
>> Occasionally, i get these in daemon.log: Dec 4 03:11:54 afs1
>> usbhid-ups[21973]: libusb_get_interrupt: could not claim interface
>> 0: Device or resource busy
>
> This isn't great, but I don't think it's related.
>
> It is normal to get a "could not claim interface 0" error once after
>
2007 Dec 01
1
APC smartups 1500 is broken with usbhid-ups
I'm trying to setup a server controlling 8 ups, 6 APC Smartups 1500
and two 1000. Because of the number of ups, i connected them using usb
cables.
I'm using Debian Etch AMD64 and nut 2.2.0 from testing (already tried
2.0 from stable, but had problems reading the ups serials and all the
following problems of 2.2).
This is my ups.conf:
[ups2]
driver = usbhid-ups
port =