similar to: Bogus shutdown

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

Hello, I have encountered problems trying to set up nut to work with APC BackUps Pro CS connected over USB to an AMD64 machine running Debian. While apcupsd works fine with that device, whenever I start upsd I get the following messages in syslog: hidups[23159]: Startup successful upsd[23160]: Connected to UPS [apc1]: hidups-hiddev0 upsd[23161]: Startup successful hidups[23159]: Unhandled event:

Hi, I'm new to nut, just installed it. I configured it using the hidups driver to work with my APC BackUPS: # upsc apc350@localhost battery.charge: 100 battery.runtime: 885 battery.voltage: 13.5 driver.name: hidups driver.parameter.port: /dev/usb/hiddev0 driver.version: 2.0.0 ups.delay.shutdown: -1 ups.delay.start: 0 ups.load: 660 ups.mfr: American Power Conversion ups.model: Back-UPS CS 350

Hi! I've got a Mandrake 2006.0 machine and a APC Back-UPS Pro 500/1000/1500 (from lsusb). The Mandrake package version of nut is 2.0.1 and hidups actually detects the UPS, however I get loads of these: Sep 12 18:26:11 vader hidups[7658]: Ignoring x86 page event 0xff860080 (0) Sep 12 18:26:11 vader hidups[7658]: Unhandled event: 0x840058 (6) Sep 12 18:26:11 vader hidups[7658]: Unhandled

I'd like to submit a patch to the 'hidups' driver. I'm a bit new to open-source development model, so I hope I'm not committing a faux paus by just posting it here. I did verify that the problem still exists (by source code inspection) in the latest dev snapshot, which is nut-2.0.3-pre2. I'm using nut-2.0.2 myself. The problem is when I'm connecting to my APC

I Seem to have made some progress in getting nut-2.0.5 installed, but hidups still has a version number of 0.13. First is hidups 0.13 the correct version? if not how do I find the correct version. Second if my Geek Squad GS1285U UPS is not supported how do I proceed. I have been a programmer for 35 years(mostly high level computer aided design), written code in 20 some languages, am retired

2006/1/13, Paul Mogren <fkamogee@yahoo.com>: > > This thread is FYI. I don't need any help here. > no, but some details for those who will read it, maybe ;-) I have SUSE 10.0 and an MGE Ellipse. I installed the NUT package from MGE. > > 1) The generated ups.conf pointed to a bad location: > /dev//dev/input/event0 > who generated that ? it seems like an old hiddev

is there a way to override the productid (like -x productid=1234) when using newhidups? just thought i'd try it with the F6C1500-TW-RK over usb. i was able to get hidups to work using the below settings, but it provides limited information. my ups.conf entry: [belkin] driver = hidups port = /dev/usb/hiddev0 and the output of upsc: gateway:/etc/nut# upsc

I downloaded nut-2.0.5 and followed the install instructions down to step 6. Since I will be using a USB port to connect to the Geek Squad GS 1285U did not go any farther yet. I tried to run "/lib/nut/hidups -DD -u root auto" to see if it found my UPS. But it is still the old hidups 0.13 from nut-2.0.3. Do I need to do something additional to get the new hidups?

Another update! It works. The systems shuts down properly when power is lost. Almost. "upsdrvctl shutdown" disconnects my UPS from the mains. From everything I've read in the documentation this should turn off the output of the UPS, not the input. Am I right here? I'm still having the following problem. Any help is appreciated. >> Also - I get the following every 4

I just installed NUT and my UPS is an APC Back-UPS ES 500. I looked in the list of drivers and found APC Back-UPS ES 350 listed in "drivers.txt" -- that list said I should use either the newhidups or hidups driver. I looked in the installation and I found headers and c files to create these drivers (I think), but in /usr/local/ups/bin there is no driver named, "newhidups or

Hello Linas, > Just wanted to inform You (for the compatibility list), that HP R/T2200 works perfectly with the hidups driver. Thank You very much for NUT! :) > > # upsc hp at localhost > battery.charge: 100 > battery.chemistry: PbAC > battery.voltage: 22.7 > driver.name: hidups > driver.parameter.port: /dev/usb/hiddev0 > driver.version: 2.0.5 > ups.delay.shutdown:

Hi Patrick, in February, you tried to post the below message to the nut-upsuser list, but the post was rejected because you were not subscribed to the list. Unfortunately, you did not subscribe and re-post it. Anyway, I have been working on Tripp-Lite support for newhidups recently, and I wonder if you have any feedback. Did you ever get this device to work? >From the information you sent,

Hi, All! I've recently bought an UPS. It is Krauler UP-M500VA, it has USB port and is a HID device. But as I discovered the only HID application it supports is 0x860004, so it isn't claimed by both hidups and newhidups drivers, because it uses a vendor-specific values. I tried to discover values in that x86 page, but I failed. How can I do it? And after I get values how to understand

Hi, I got a Belkin F6C550-AVR UPS today and was trying to get it working with NUT, I used the "hidups" driver and got some data out of it, mainly the following: battery.charge: 100 battery.runtime: 120 driver.name: hidups driver.parameter.port: /dev/usb/hiddev0 driver.version: 2.0.0 ups.mfr: Unknown ups.model: Unknown ups.serial: Unknown ups.status: OL the versions of NUT that I tried

Hi, I got a Belkin F6C550-AVR UPS today and was trying to get it working with NUT, I used the "hidups" driver and got some data out of it, mainly the following: battery.charge: 100 battery.runtime: 120 driver.name: hidups driver.parameter.port: /dev/usb/hiddev0 driver.version: 2.0.0 ups.mfr: Unknown ups.model: Unknown ups.serial: Unknown ups.status: OL the versions of NUT that I tried

I am having problems building usb on mac os x. First, mac os x doesn't seem to have asm/types.h, just sys/types.h. I can't find hiddev.h on mac os x either. Also, it doesn't have usb.h but instead IOKIT/usb/USB.h. I am using mac os x (10.4), and the latest cvs of nut. Is the new usb support going to work on mac os x? Is anyone working on it? It seems that libusb is available

Hi all Arnaud, Some newly purchased Ellipse ASR-model UPS find their way to my office for a first evaluation test. It concerns the Ellipse 1500 and Ellipse 1000 models. As you know we are still working with hidups. Peripheral recognition, start of NUT, mains short interruptions management, all that work fine... as expected ;-) But changes occured on the delayed shutdown procedure after the

Hello all, Has anyone had any luck getting a CPS GS 1500U working with NUT via USB. Its branded Geek Squad (don't ask) but it shows up in the USB device list as the CPS 1500U. I'm running Kubuntu Dapper with all current updates installed, Kernel 2.6.15-26-686, NUT 2.0.3. I've tried hidups and newhidups. With hidups I used port=/dev/bus/usb/001/004 which I'm sure is the UPS

I have an older system which has a simple APC Back-UPS ES 500 connected via USB. I built nut 2.0.2 from source and am attempting to get it to work. I had to manually create the device links and I think it's ok because hidups is recognizing the UPS but any attempts to read data from it fail: [root@server bin]# ./hidups -D -D -D /dev/usb/hid/hiddev0 Network UPS Tools: HID UPS driver 0.13