similar to: iDowell subdriver added

Hi all, first message to the list. :-) I've got an iBox made by iDowell: http://store.apple.com/uk/product/TR423ZM/A This seems to be similar to the smaller Microdowell UPS: http://idowell.eu/ I cannot get it recognised by the drivers. This is what I get when I plug in the USB connector: Jan 3 19:27:26 compaq kernel: usb 3-2: new low speed USB device using uhci_hcd and address 47

Citeren Arjen de Korte <adkorte-guest op alioth.debian.org>: > Log: > Use the 'nss_compat_ossl' compatibility layer to use the Mozilla NSS > library instead of OpenSSL (we might want to include native support > in the future, but this will at least allow a quick migration for > testing purposes) I don't recall that we ever discussed the possibility of

Looking for ioctl() calls in the drivers, I noticed that the energizerups.c code looks a lot like a megatec protocol over a USB connection. It uses 8 bytes per packet, which makes it look like the agiler subdriver in megatec_usb. Do we know if there are people that use this driver now and that might be able to verify this? Best regards, Arjen -- Eindhoven - The Netherlands Key fingerprint - 66

On Wed, Sep 24, 2008 at 2:27 PM, Arjen de Korte <adkorte-guest at alioth.debian.org> wrote: > - /* Server side variables */ > - { "driver.version.internal", ST_FLAG_STRING, sizeof(DRIVER_VERSION), NULL, NULL, DRIVER_VERSION, HU_FLAG_ABSENT, NULL }, > - { "driver.version.data", ST_FLAG_STRING, sizeof(APC_HID_VERSION), NULL, NULL, APC_HID_VERSION,

Hi all, I attached a driver for MiniBox openUPS device ( http://www.mini-box.com/OpenUPS) and a dump of the hid usages. I had the possibility to make a few adjustments to the device firmware for HID usages, and although I haven't managed to produce a good structure many issues from previous firmware were at least fixed and new information added. ATM the driver only shows pertaining

Citeren Arjen de Korte <adkorte-guest at alioth.debian.org>: > Author: adkorte-guest > Date: Thu Jan 15 11:54:05 2009 > New Revision: 1728 > > Log: > Another stab at this. > > Modified: > trunk/tools/Makefile.am And failing miserably... :-( Can someone more fluent in 'autotoolish' fix this problem? Currently the BuildBot is broken by update r1718

Citeren Arnaud Quette <aquette op alioth.debian.org>: > Author: aquette > Date: Sat Dec 11 12:31:21 2010 > New Revision: 2731 > URL: http://trac.networkupstools.org/projects/nut/changeset/2731 > > Log: > Complete the list of Subversion ignored files, with AsciiDoc > generated contents (no functional changes) Is there a particular reason for having both the man/

Citeren Arnaud Quette <aquette op alioth.debian.org>: > Modified: trunk/drivers/tripplite-hid.c > ============================================================================== > --- trunk/drivers/tripplite-hid.c (original) > +++ trunk/drivers/tripplite-hid.c Sun Mar 1 19:56:31 2009 > @@ -84,6 +84,8 @@ > > /* HP R/T 2200 INTL (like SMART2200RMXL2U) */ > {

I'm following advice from Arjen de Korte and Charles Lepple (see http://lists.alioth.debian.org/pipermail/nut-upsuser/2010-January/005829.html). I added a full update on the specifics of my situation: http://lists.alioth.debian.org/pipermail/nut-upsdev/2011-February/005255.html Would appreciate guidance on getting started generating a MIB-to-NUT mapping (tools, etc): OS: CentOS 5.5 NUT

Citeren Arnaud Quette <aquette op alioth.debian.org>: > Log: > Optionaly enable silent build rules, using AM_SILENT_RULES, only if > it's supported (requires automake 1.11) Why do we need a new branch for this? As far as I can see, only the below lines are really needed > +dnl Currently, we only (force) enable silent rules if available > +dnl Verbose mode can be

Hi All, I'm using an iDowell UPS with the usbhid-ups driver: $ upsc iDowell at localhost battery.charge: 100 battery.charge.low: 15 battery.runtime: 650 battery.type: Pb acc device.mfr: iDowell device.model: iBox device.serial: 00000001 device.type: ups driver.name: usbhid-ups driver.parameter.pollfreq: 30 driver.parameter.pollinterval: 2 driver.parameter.port: auto

I have the following UPS that I'm trying to get to work with NUT: SU3000RTXL3U I have it connected via USB. My ups.conf looks like: [test] driver = usbhid-ups vendorid = 09ae port = auto When I run upsdrvctl -DD start, I get: Network UPS Tools - UPS driver controller 2.4.1 Starting UPS: test exec: /lib/nut/usbhid-ups -a test Network UPS Tools - Generic HID driver 0.34 (2.4.1)

> Author: agordeev-guest > Date: Wed Oct 3 00:09:21 2007 > New Revision: 1136 > > Log: > - drivers/megatec_usb.c: added ability to do subdriver-specific > initialization, and moved some shared code to agiler init function > since krauler doesn't need it. [...] I'm not very thrilled about this patch: 1) Down at the subdriver level, one shouldn't use

Arnaud Quette <aquette.dev at gmail.com> va escriure (2011-02-28 14:48): > > 2011/2/14 Ernest Sales <ersaloz at gmail.com> > > > Arjen de Korte <nut+users at de-korte.org> va escriure: > > > This is a known problem in nut-2.4.3 and should be solved in > > > nut-2.6.0. We have also dropped the megatec and > megatec_usb drivers, > > >

In /var/log/syslog Dec 23 13:04:50 ************** upsmon[2010]: Poll UPS [rack1ups at localhost] failed - Write error: Broken pipe After this, there is no longer a upsd daemon running. Error messages follow: Dec 23 13:04:50 ************** upsmon[2010]: Communications with UPS rack1ups at localhost lost ... Dec 23 13:04:55 ************** upsmon[2010]: UPS [rack1ups at localhost]: connect

A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 188 bytes Desc: not available Url : http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20071124/3ceb35d2/attachment.pgp

Alexander Gordeev wrote: > Author: agordeev-guest > Date: Mon Aug 13 13:09:43 2007 > New Revision: 1049 > > Log: > drivers/megatec_usb.c: added credits to the banner message. Is this really needed/desirable? I think this kind of information needs to be put in the AUTHORS document. There are many more people on this list that put a lot of effort in NUT, without claiming credit

Hello, today I'm fighting with a Online Zinto 1000 (lsusb.txt) produced by Phoenixtec/Eaton ;-) http://www.eaton.com/EatonCom/OurCompany/NewsandEvents/NewsList/CT_141334 I have tested different drivers without success (please see attachments usbhid-ups.txt, bcmxcp_usb.txt, blazer_usb.txt) The help got unfortunately time outs (explore.txt)

Here are a series of my recent changes to NUT. The first few in the set are primarily little fixes and improvements. In among those are a few for .gitignore files which of course you can ignore for SVN, and there's one for a commit to a generated file which of course should not be tracked in any VCS. Then there are a couple or three to do with generating the header files used by

To people with APC, CyberPower, Belkin and TrippLite UPS'es and using the 'usbhid-ups' driver. There are some concerns that the usbhid-ups driver is not acting as it is supposed to do. Could you run the following command (as root and with the mains plugged) and check if the UPS powers back on automatically? upsmon -c fsd I think we should *not* release nut-2.2.1 if we're not