similar to: the 2nd generation of NUT developers (was: tripp lite smart2200RMXL2U error reading protocol)

Hi James, thanks for the feedback. The output you get seems generally fine, except for battery.voltage: 0.0 and output.voltage: 164.0; these values are consistent with what Phil DeBoest reported. Upsmon normally executes the shutdown command when you reach the "low battery" threshold, as decided by the UPS and/or driver. It does so by looking at ups.status, not battery.charge. --

Hi, I'm running Fedora Core 6 and need to monitor a Tripp Lite SMART2200RMXL2U. I've loaded the nut-2.0.3-2.1 RPM. The UPS is connected via the provided USB cable, and that much appears to work: # dmesg | grep -i tripp hiddev96: USB HID v1.10 Device [Tripp Lite TRIPP LITE SMART2200RMXL2U ] on usb-0000:00:1f.4-2 # lspci | grep -i usb 00:1f.4 USB Controller: Intel Corporation 82801BA/BAM

Hello. I'm new to nut and don't know if I've missed something in setting it up or if my ups isn't quite supported. I'm using these: - svn version of nut (downloaded on 9/13/06) - a tripp lite SMART2200RMXL2U - debian sarge with 2.6.8 kernel - the tripplite_usb driver (newhidups says my ups is not supported) I figured out how to get the device perms correct.

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

2006/10/2, Peter Selinger <selinger@mathstat.dal.ca>: > Arnaud Quette wrote: > > > > 2006/9/29, Peter Selinger <selinger@mathstat.dal.ca>: > > > > > I don't really understand the purpose of the "Testing" branch. It has > > > not been touched since July, as far as I can see. I also don't > > > understand NUT's release

Fellows, back for 4 days, the baby and the mother are now at home, and the father is... hem, well not so fresh ;-) For those interested in some pictures: http://benjamin.quette.free.fr/ 2006/11/16, Peter Selinger <selinger@mathstat.dal.ca>: > ... > Arnaud: could you please amend the instructions on the NUT download > website http://www.networkupstools.org/source.html (Development

This is a USB only ups. I could not make it work with nut. So I put this daemon together. Get it from http://www.vsys.org/sventura/dev/ at the bottom of the page. Init scripts are gentoo based but I think it should be easy to adjust them to any distro. I am planning to integrate it with nut if I can find the time and there is enough interest on it to justify the project. This is a very entry

Philipp Leusmann wrote: > > Ok, I tried this and my results seem to bet he same as reported. Then I > think I=B4ll have to stick with the windows-driver at least on my main > machine.=20 > Or is there anything I can help to fix this driver? I don't know why we can't read anything from this device. There are many ways in which one could make a buggy device that works with

Hello all; I am new to this list. Recently we have been getting these cheap new Tripp-Lite "LCD" style UPS'es around here, and I was surprised to find the lack of Linux support. The model name is OMNI650LCD. Anyway, I tried the tripplite_usb driver and got a message instructing me to contact this mailing list. I might try to fix the problem myself, if I was more familiar with the

2006/1/27, Peter Selinger <selinger@mathstat.dal.ca>: > > ... > battery.mfr.date, which is probably the more accurate interpretation. > > I think the naming should be changed to propose both: - battery.date.mfr: Battery manufacturing date - battery.date.change: Battery change date Any comments? Arnaud -------------- next part -------------- An HTML attachment was scrubbed...

Hi Patrick, I didn't get further bug reports from you, so I have now listed your device as "supported" by newhidups. Last I saw as of your below message, the driver was working as expected. If there are any future problems, let me know! -- Peter Patrick Nolan wrote: > > Remember me? Back in May we exchanged some messages about my Tripp-Lite > UPS. My boss has gone on

I have a Tripp Lite OMNI900LCD. It has a usb connector and claims to be USB/HID. I haven't been able to get it to work with newusbhid or tripplite_usb. Here's lsusb -v output: Bus 001 Device 013: ID 09ae:2005 Tripp Lite Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass 0 (Defined at Interface level)

Oh oops, I see you already did. -- Peter selinger wrote: > > You could send it without "submitting" it. That's the advantage of > patches - they can be discussed. There are lots of eyeballs here that > might see what's wrong. Thanks, -- Peter > > Eric S. Raymond wrote: > > > > Peter Selinger <selinger at mathstat.dal.ca>: > > > I

On 1/13/07, Peter Selinger <selinger@mathstat.dal.ca> wrote: > > The question is when exactly this should be converted to a number. > > Should this be done in upscli_splitname() or in upscli_connect()? The > > latter would require a change in the prototypes of upscli_splitname() > > and upscli_connect(), and an attendant change in all the existing > > clients.

On 10/15/06, Peter Selinger <selinger@mathstat.dal.ca> wrote: > I have converted NUT's build system to Automake/Libtool. Right now, > the new build system is contained in the "automake" branch, at: Wow... this is really nice. Thanks for taking the time to do the conversion. > drivers/Doxyfile - this seems to belong to Charles. Perhaps >

Hi Patrick, Patrick Nolan wrote: > > Remember me? Back in May we exchanged some messages about my Tripp-Lite > UPS. My boss has gone on vacation, so I finally got a chance to take a > look at this. > > Peter Selinger wrote: > ... > > In case you feel like experimenting with this, I am attaching a patch > > that *might* enable this device to be supported by the

On 2/10/06, Charles Lepple <clepple@gmail.com> wrote: > On 2/10/06, Peter Selinger <selinger@mathstat.dal.ca> wrote: > > Charles Lepple wrote: > > > > > > > [...] The only thing I had to correct manually is > > > > that a few of my binary files were inaccurately classified as text > > > > files (and thus subject to the \r\n

[moving to upsdev as it's now off topic for upsusers] 2006/8/30, Peter Selinger <selinger@mathstat.dal.ca>: [snip] > > the threaded method would allow, with some sub-drv config, to launch > > the polling thread and/or the interrupt thread. Either feeding the > > core is not important since the core wouldn't care about that. > > I think is may make sense to

I think someone tried this recently, although I cannot find the post any more. It may be helpful, but it is not guaranteed that we will find anything. Could you please keep the discussion on the mailing list? Thanks, -- Peter Philipp Leusmann wrote: > > Wouldn't it help to sniff usb-communication with the windows driver? > > Philipp > > > -----Urspr=FCngliche

2005/9/25, Peter Selinger <selinger@mathstat.dal.ca>: > > Arnaud Quette wrote: > > > > Some more points while you're at it: > > - newhidups will have to be renamed. My aimed was to let the name until > we > > can superceed hidups. Then remove hidups, and rename newhidups to > usbhid-ups > > (name proposition welcomed, but should match the fact