similar to: newhidups: selecting device by BUS

I have gone ahead and merged the regex_branch with the main Development branch. Reason: recent renaming of files and moving around of code leads to conflicts between the branches that will be increasingly difficult to resolve. It is easier to merge now while the two branches are still relatively similar and most edits non-overlapping. The merge is between tags before_PSE_6 and after_PSE_6 on

* I committed into CVS the gendb patch that I sent to the mailing list on September 12. Arnaud, I hope you approve of this patch; it is more reliable than the previous method in tracking the correct dependencies. * This, together with some other minor recent changes on the Development branch, is between the "before_PSE_3" and "after_PSE_3" tags. Arnaud: if you

I have checked in a cleaned-up version of patch #302111 (Belkin support) into CVS. See cvs diff -uN -r before_PSE_2 -r after_PSE_2 to check the difference. Here is the CHANGES entry: Tue Sep 13 20:50:14 UTC 2005 / Peter Selinger <selinger@users.sourceforge.net> - newhidups: added Belkin support. Also added some new variables and instant commands (some of these were already used by

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

Okay, now that I've got NUT up and running with the newhidups driver, I can give it a quick shakedown. Most of the values look good, but are few are off. Here's what I get: elrond@foxstar:~$ upsc foxstarups@localhost battery.charge: 100 battery.charge.low: 10 battery.charge.warning: 50 battery.date: 3150/08/01 battery.mfr.date: 2005/03/22 battery.runtime: 1935 battery.runtime.low: 120

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

[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

Hi Shane, please try the instructions at http://www.mathstat.dal.ca/~selinger/ups/backups.html (with appropriate modifications for FreeBSD). If you can't get it to work, please get help from the nut-upsuser mailing list (cc'd above), as I am no longer actively involved in NUT development. Good luck, -- Peter Shane Roberts wrote: > > Hi Peter, > > I am running the NUT

Peter, You may want to have a look at the comments to Bug 164524 at bugzilla@redhat.com: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=164524 I filed this a long while ago, because of the mess we get into when shutting down Linux via /etc/rc.d/init.d/halt, and the UPS device no longer being reachable when we want shut it down. There seem to be some changes to libusb on the way, that

Hello everyone! If this message was posted twice, my apologies. I'm having issues with my webmail today... I am using the testing version of NUT from SVN at changeset 582. I have successfully created a stub for newhidups driver for my Dynex DX-800U UPS, but I am completely lost on the customization of it. I've followed the hid-subdrivers.txt instructions and I understand I need to

Thought I would write some notes about how I got an APC BackUPS XS 1500 working with newhidups under Gentoo 2006.0. The specific issue here is the permissions on the device files used that libusb uses to access the USB hardware. I followed Peter Selinger's instructions at http://www.mscs.dal.ca/~selinger/ups/backups.html on getting newhidups going with an APC device. The sticking point for

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

Hi there, I'm one of the maintainers of the SME Server distro (www.contribs.org) and we've been chasing this one for some time: http://www.contribs.org/bugzilla/show_bug.cgi?id=352 http://lists.alioth.debian.org/pipermail/nut-upsdev/2006-January/000543.html Many thanks to Peter Selinger and everyone else who helped with the debugging and patches. Thanks, Gordon

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

Here is a summary of the changes I made to newhidups today (between the tags after_PSE_6 and after_PSE_9, roughly). * all the vendor-specific code that was in various "switch" statements has now been moved to the individual subdriver (apc-hid, mge-hid, belkin-hid) files. This also includes the vendor-specific Usage tables. In future, it should be quite easy to add new

Zaid, I have a Belkin F6C800-UNV which has both a serial and USB connector. The serial connection is already working with the Belkinunv driver. I will connect via the USB and then compare both sets of variables. This should allow me to correlate and shed some light on the meaning of many of Belkin's non-standard "Usage" descriptors. With this information, it should be very easy

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

Hi Arnaud, hi all I wish you all the best for 2006. Enjoying of some less stressed time, I follow your advice, Arnaud, to switch our UPS management on the newhidups driver. ( Enfin ! ;) Our goal is to support (soon) the new MGE ASR ELLIPSE ( and of course also the old ELLIPSE and EXTREME models ). I rebuild the libusb-0.1.10a packages to conform to our installation process. I perform the same

Hi developers, I would like to propose making a release soon from the current NUT trunk. There have been a lot of important changes since 2.0.5: new drivers added/refined (e.g. megatec_usb); the switch to Automake; the renaming of newhidups to usbhid-ups; automatic installation of hotplugging files; IPv6 support; improvements to the tripplite_usb driver; improvements to the gamatronic driver;

I'm using an APC Back-UPS XS with nut 2.0.3. I've recompiled/reinstalled the source, and switched over to the newhidups driver (instead of the old hidups driver). I modified by ups.conf to use newhidups. The hotplug files were not automatically installed, I had to copy those from the scripts directory to my hotplug/usb directory. The newhidups driver loads find and then works for a