similar to: USB HID - interrupt reports

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

Folks, I think the present megatec_usb.c deserves to be renamed to serial_usb.c. I think it potentially could serve many more UPS'es with built-in USB-to-serial converters, not limited to the megatec_usb driver (although that was the first one to use this). I also think a more layered approach would be nice, in the same fashion as the usbhid-ups driver with subdrivers. Which would mean that

Reporting current in milliAmps is not a good idea. This will lead to impractically large values, especially when we report them with two decimals resolution (10 microAmps). Even the laboratory measuring equipment that is standing right next to me now, doesn't offer this resolution in the range that is common for most UPS'es. I think you meant to write 'Ampere (A)' here

Peter, Apparently, some Belkin UPSes still have problems with this. When we receive this report through the interrupt pipeline it is ignored (the special case in usbhid-ups.c) and even after that it looks like there are still some problems with it: http://lists.alioth.debian.org/pipermail/nut-upsuser/2007-July/003014.html Wouldn't it be an option to just to ignore this completely and

Hi Recently i bought a MicroDoWell BP50, and with it followed a USB 2 serial converter. When i plug it into my 2.6.19 kernel, dmesg shows hiddev96: USB HID v1.10 Device [Cyber Power System CPS RS232 USB BRIDGE for UPS] on usb-0000:00:04.2-2 usbcore: registered new interface driver usbhid drivers/usb/input/hid-core.c: v2.6:USB HID core driver So, i figured i should use usbhid-ups,

I'm trying to see if we can make upsd autodetect the driver sockets from the STATEPATH. This works quite well and uses surprisingly little code (much less than parsing the 'ups.conf' file). However, since I can no longer read the name from the 'ups.conf' file, I need to extract this from the name of the socket. We might simply strip the drivername from the socket name again,

Dear Sirs, First of all I would like to thank you for support PCM product in your project. Kindly please be informed that POWERCOM launch new USB-controller with productID 0X04. Updated USB-controller compatible with previous version which supported by your usbhid-ups driver. There is added some command and changed idProduct. Vendor ID stay the same 0X0d9f without changes. Detailed information

Hi, Charles, On Wed, 2 May 2007 07:58:08 -0400, you wrote: > > Will that be enough to make it useable as a contribution? I believe > > the more sensible values for 36V UPS'es will be useful to other models > > than the one I have, too. > > Sounds good, but I don't think I saw it hit the list yet... I now have the following in megatec.c: static BatteryVolts

Thomas, The none (-22) message in your log is an errno from the libusb_get_interrupt() call in HIDGetEvents() in libhid.c. It indicates an invalid ioctl type. In HIDGetEvents() there is a comment with that call: /* needs libusb-0.1.8 to work => use ifdef and autoconf */ You may want to make sure your libusb is up-to-date. Hope this helps, AG --

Citeren Alexander Gordeev <lasaine op lvk.cs.msu.su>: > I've received the units. Are there any special things I should test or > just the standard NUT setup? They should be detected out of the box (with the latest version from the trunk) through the 'usbhid-ups' driver. Note that I just added some additional commands to enable|disable|mute the beeper of the UPS.

Hi, usualy, in the unix world, while processing command line options, unix programs keep the last option value, overriding config file options or previous command line ones, unfortunately, ssh only keep the first option processed. ex. : ssh -o BatchMode=no -o BatchMode=yes host cmd arg... the unix common expected behaviour is to have BatchMode = true, while ssh says BatchMode = false. how

Hi, I have to read in data which looks like this: SeriesA, 5, 5, 5, 5 SeriesB, 8, 5, 8, 8, 7, 10, 2, 7, 3 SeriesC, 5, 5, 8, 4, 7, 7, 4, 5 SeriesD, 5, 9, 5, 4, 2, 3, 10, 1 SeriesE, 7, 10, 9, 5, 8, 6, 10, 9, 5, 10, 4, 3, 2, 10, 8, 8, 10, 10, 10 SeriesF, 1, 2, 1, 5, 1, 7, 5, 7, 7, 3 There are actually much more data points in the data, each line contains between 300 and 500 values. If I use

Alexey, I posted this before, but never got a reply. So I'm reposting this again. In the present HID PDC implementation by PowerCOM, expect problems with the non-compliant implementation of the DelayBeforeShutdown and DelayBeforeStartup pages. Third party applications will expect that these follow the HID PDC specifications if you name them like this (and break terribly in the

Dear Sirs, We appreciate your support and cooperation. Can you please kindly add our new USB-controller with productID 0X04 to NUT compatible list. Updated USB-controller compatible with previous version which is supported by your usbhid-ups driver. Detailed information regarding new POWERCOM communication protocol you could download via link

Hi! Using (among others) the pretty old SuSE8.1, I cant get puppet to install packages. The rpm programms bahaviour was changed somewhen between versions 3 and 4 (sry, don´t know exactly when) and the old version does not support the "--nosignature" and "--nodigest" params and "--oldpackage" is purely an update parameter so when trying to install a package I

Hi, I have been using 'read.table' regularly to read tab-delimited text files with data. No problem, until now. Now I have a file that appeared to have read fine, and the data inside looks correct (structure etc), except I only had 15000+ rows out of the expected 24000. Using 'readLines' instead, and breaking up the data by tabs, gives me the expected result. I do not

Thanks, for the explanation. Still, I think this is surprising bahaviour which might be handled better. Best, Peter Am 20.10.2017 9:49 nachm. schrieb "I?aki ?car" <i.ucar86 at gmail.com>: > Hi Peter, > > 2017-10-20 21:33 GMT+02:00 Peter Meissner <retep.meissner at gmail.com>: > > Hey, > > > > I found this - for me - quite surprising and puzzling

Hello All, We have been successfully using PAM_LDAP authentication with OpenSSH-3.6 on our HP-UX 11.11. When OpenSSH-3.7.1p2 is installed [with Darrens' password expiry patch 26], and when Shadow password bundle is installed on the system, our ssh authentication failed. Even, when the source is compiled without Darren's patch, the same bahaviour is seen and there is no success. When

Well, seems like I hit every mudhole that could be on the way ... root at samba4:/# getent passwd | grep mgr mgr:*:10000:10000:Lars LH. Hanke:/home/AD/mgr:/bin/bash root at samba4:/# ldapsearch -LLL -D "CN=Administrator,CN=Users,DC=ad,DC=microsult,DC=de" -x -W '(uid=mgr)' uid uidNumber gidNumber sAMAccountName name gecos Enter LDAP Password: dn: CN=Lars LH.

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