similar to: Nut-upsuser Digest, Vol 36, Issue 8

It is possible at least on linux to get the port associated with a device from userspace - I'd assume that on each platform it's possible, just that libusb is incomplete (on top of being undocumented). Here's a patch for matching portnum on linux, with a few pieces pulled from libusb. It lacks autoconf macros to isolate it -- but it does appear to work. Regards, Alex Peyser On

I'm setting up a cluster with multiple ups's using nut 2.2. The ups's are Belkin 1500 (ID 050d:0751) which don't appear to report a serial number. Is there any other way I can setup ups.conf with multiple of these ups over usb on Linux? If I just setup the vendor and product id's, every definition in ups.conf appears to match the first one, and therefore all of them but

Le 23/06/2011 14:00, nut-upsuser-request at lists.alioth.debian.org a ?crit : > Send Nut-upsuser mailing list submissions to > nut-upsuser at lists.alioth.debian.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser > or, via email, send a message with subject or body 'help' to >

THANKS, but the 'megatec' driver only works whith windows OS via USB, and i need it for red hat OS with USB-serial connection... Please, anybody can help me.... nut-upsuser-request@lists.alioth.debian.org escribi?: Send Nut-upsuser mailing list submissions to nut-upsuser@lists.alioth.debian.org To subscribe or unsubscribe via the World Wide Web, visit

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

---> On 15/03/2009 8:00 AM, nut-upsuser-request at lists.alioth.debian.org wrote: > Message: 1 > Date: Sat, 14 Mar 2009 21:47:08 +0100 > From: Arjen de Korte <nut+users at de-korte.org> > Subject: Re: [Nut-upsuser] Weird Load and Battery Temp Readings > To: nut-upsuser at lists.alioth.debian.org > Message-ID: <20090314214708.37122w00w79l6u9s at mail.de-korte.org>

> ---------- Forwarded message ---------- > From: Arjen de Korte > To: nut-commits at lists.alioth.debian.org > Date: Mon, 27 Aug 2007 18:33:00 +0000 > Subject: svn commit r1076 - in trunk: . drivers > Author: adkorte-guest > Date: Mon Aug 27 18:33:00 2007 > New Revision: 1076 > > Log: > * drivers/libhid.[ch],libshut.[ch],libusb.[ch]: > - Cut the libshut and

the USB access. That file is actually specifically for bcmxcp_usb.c, and applies only to Powerware devices. You should use the interface in libusb.c / libhid.c instead. See megatec_usb.c or tripplite_usb.c for how it is done. Thanks, -- Peter Peter van Valderen wrote: > > Hello Arjen, > > On 5/23/07, Arjen de Korte <nut+devel at de-korte.org> wrote: > > Never mind the

I think having this logic buried within libhid/libusb (libusb:libusb_open(), line 179 to 206) is ultimately a mistake, albeit one that I am probably responsible for. Would it make sense to confine libhid to low-level operations, and leave the decision of trying to reopen vs. retrying to open to the high-level driver, in this case usbhid-ups? I envision that the code in usbhid-ups:reconnect_ups()

On Dec 31, 2009, at 8:45 AM, Arjen de Korte wrote: > Author: adkorte-guest > Date: Thu Dec 31 13:45:16 2009 > New Revision: 2218 > > Log: > Add pkg-config as method to retrieve CFLAGS and LDFLAGS (but fall > back to libusb-config) > > Modified: > trunk/m4/nut_check_libusb.m4 Arjen, I'm not sure you want parentheses in the shell script fragments. Search for

Hi, Arjen; I am new to linux and not sure how to create the PowerCom-usb driver. So could you please compile powercom-usb file for me. I am happy to test it out with the USB PowerCom Ups. Thanks, Paul MCSE/MCSA/MCP ------------------------------ Message: 2 Date: Mon, 03 Sep 2007 11:13:32 +0200 From: Arjen de Korte <nut+users at de-korte.org> Subject: Re: [Nut-upsuser] Powercom USB UPS is

> Today's Topics: > > 1. Re: Possible support for Trust 1300VA LCD Management UPS? > (Charles Lepple) > Hmm, you have both libusb-compat and libusb-legacy. Unfortunately, > that alone doesn't tell us what NUT is linked against. > > What does "otool -L <path-to-drivers>/blazer_usb" show? Not sure what > that path would be for MacPorts, but

On Sun, Apr 20, 2008 at 10:46 AM, Arjen de Korte wrote: > We need a pre3 to fix this since this has been a long standing bug. This > path is hardcoded in the example configuration, where running > ./configure should set this path properly. In fact, Charles fixed this > in the trunk, but apparently we didn't backport the fix to Testing. Good > catch! I apologize for not

On 2/27/07, A.Lizard <alizard@ecis.com> wrote: > terrarium:/home/alizard# /usr/local/ups/bin/newhidups -DDD -a belkin-ups > Network UPS Tools: 0.28 USB communication driver 0.28 - core 0.30 (2.0.5-pre2) > > debug level is '3' > Checking device (050D/0551) (002/006) the '002/006' part is "bus->dirname, dev->filename" in libusb.c. Does

Hi Vladimir, I have got 2.0.3 working on netBSD 3.0. To get it operational I needed to do the following (most of this is from memory...). 1). Recompile kernel with uhid removed. If uhid ataches to the device then libusb is not able to. Have to allow generic usb driver ugen to claim port. >From dmesg usb0 at uhci0: USB revision 1.0 uhub0 at usb0 uhub0: VIA Technologies UHCI root hub, class

On Thu, Dec 4, 2008 at 4:51 PM, Arjen de Korte <adkorte-guest at alioth.debian.org> wrote: > Author: adkorte-guest > Date: Thu Dec 4 21:51:28 2008 > New Revision: 1596 > > Log: > Added new richcomm_usb driver based on the lakeview_usb driver (using libusb). Sorry if I wasn't clear - I was advocating *renaming* the lakeview_usb driver to richcomm_usb. Is there another

Hi Pengfei, Glad you tried the program and it works fine to you for the first place. Dr. Swarup and John from UIUC wrote most of the code, and released the original code to public. Dynamic slicing tool is really very useful. Giri is now far from perfect. For example, there are know bugs for multi-thread programs and I'm fixing it these weeks. I will take charge of this project for a while

On Mar 19, 2017, at 10:56 AM, Drew from Zhrodague <drewzhrodague at zhrodague.net> wrote: > > [] I've spoken with one of the developers, and he's offered to share some technical documentation with me. I'll report here with whatever I can. He's on vacation in China. Hopefully this documentation will lead to fewer surprises down the road. > [] I found this

[moved to nut-upsdev while we figure out the protocol] > On Mar 9, 2017, at 11:22 AM, Drew from Zhrodague <drewzhrodague at zhrodague.net> wrote: > > I'm able to cat /dev/usb/hiddev0 and /dev/hidraw0 - I pipe this through hexdump and I get different types of data from each: > > > hiddev: > > 0002420 00a7 ffa0 00ff 0000 00a7 ffa0 00ff 0000 > 0002430 00a7

Dear R list, I have a sequence of weekly observations of number of adults and larvae in various size classes from a butterfly population living in a subtropical area with pronounced wet and dry seasons. Wet and dry seasons are each defined 26 weeks long with fixed start and end dates. The data span 103 weeks (two seasons each of wet and dry) with some missing weeks. What I would like to do is