similar to: Trouble connecting to apc smart 1500 via serial cable

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

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 >

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

I've got it ! Actually, it was obvious. A question of rights on the USB port. As soon as the process has the right rights (?) on the port, it runs smoothly. Sorry for the useless post... Regards, Pierre Boullier ----- Original Message ----- From: Pierre Boullier To: nut-upsuser at lists.alioth.debian.org Sent: Friday, November 12, 2010 3:18 PM Subject: usbhid-ups and 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

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

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,

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

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

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

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

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

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

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 >

On Dec 7, 2013, at 2:38 PM, Christian wrote: > Dear list, > > I have an APC Smart-UPS 1500 hooked up via the USB port. Recently, when > we had a power outage, the only entry in the logs was: > > Dec 3 14:43:43 afs1 upsmon[3035]: UPS apc at localhost on battery > > and then the machine seems to have run until the battery was empty. It > only notices the "battery

Dear list, I have an APC Smart-UPS 1500 hooked up via the USB port. Recently, when we had a power outage, the only entry in the logs was: Dec 3 14:43:43 afs1 upsmon[3035]: UPS apc at localhost on battery and then the machine seems to have run until the battery was empty. It only notices the "battery low" after I turn the system back on: Dec 3 16:01:39 afs1 usbhid-ups[21973]:

APC Smart-UPS X 1500 Restart Issue. Hi All, I have installed nut-2.4.3. I have manually modified the files apc-hid.c and udev-rules to support 5G APC UPS. I took sample code from the 2.5 development tree. Shutdown process is working very well -- upsmon creates the file /etc/killpower - shutdown script checks for the file and issues /sbin/upsdrvctl shutdown - UPS cuts the power off. All

APC Smart-UPS X 1500 Restart Issue. Hi All, I have installed nut-2.4.3. I have manually modified the files apc-hid.c and udev-rules to support 5G APC UPS. I took sample code from the 2.5 development tree. Shutdown process is working very well -- upsmon creates the file /etc/killpower - shutdown script checks for the file and issues /sbin/upsdrvctl shutdown - UPS cuts the power off. All

Hi. I guess the world is full of these, one more won't hurt: "The ogg-cdparanoia script is a wrapper of the programs cdparanoia (http://www.xiph.org/paranoia/), sox (http://sox.sourceforge.net/) and oggenc (http://www.vorbis.com/). The process is simple: for each track, cdparanoia is called to extract the audio to a temporary wav file. Sox is used on it to see if it is normalized.

Hi. I've seen that there are a few python bindings for the libraries. I am planning to write a relationed python module and before doing things wrong I wanted to know if this list can be used to talk about those bindings, if the authors of those bindings are on this list, or if I should join a python mailing list or something like that. IOW, I wouldn't like to write something to discover