similar to: PowerCom USB units...

Skipped content of type multipart/mixed-------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available Url : http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20070205/5ad69acc/attachment.pgp

Joel Peshkin wrote: > > I hacked in the following additonal changes... > > Index: newhidups.c > =================================================================== > RCS file: /cvsroot/nut/nut/drivers/newhidups.c,v > retrieving revision 1.1.1.1.8.6.2.21 > diff -u -r1.1.1.1.8.6.2.21 newhidups.c > --- newhidups.c 7 Nov 2005 22:14:20 -0000 1.1.1.1.8.6.2.21 > +++

Hi Peter, I've forwarded your mail to upsdev as it will be of interest for several people that are working on it. As I'm also on vacation (again) for a week and 1/2 as of this evening, I don't think I'll have the time for it before I get back.... I've not yet audited the patches, but these are queued on the Alioth tracker:

Hi! all. I have been reading every mail and news about nut and 06da:0002 Phoenixtec but not found a solution. I have a very nice working ups from: CENER ref: "Active 1000VA 230V 12 CENER" and front logo "LA 900" It has COM3 and USB plugs, I don't know if it needs a standar RS232 I have test with varius drivers in ups.conf [MyUPS] driver = bcmxcp_usb | usbhid-ups |

On Dec 3, 2014, at 2:02 PM, janc at telefonica.net wrote: > USB error: error sending control message: Invalid or incomplete > multibyte or wide character This is a wild guess, but what about using the option "langid_fix=0x0409"? -- Charles Lepple clepple at gmail

Hi again, Thanks for the prompt reply. Just for the record i am running debian unstable/sid with nut 2.7.4-3 # dpkg -l 'nut*' | grep ^ii ii nut 2.7.4-3 all network UPS tools - metapackage ii nut-client 2.7.4-3 amd64 network UPS tools - clients ii nut-server 2.7.4-3 amd64 network UPS tools - core

Hi, fellow NUT gurus; I am having a big issue with our new Powercom Imperial Digital UPS. The UPS is come with a serial over USB port and plug into the usb port on the computer. I am having problem to setup our fedora 7 linux machine talks to the ups. The kernel 2.6.22.1 seems to be able to detect the ups is plug into one of its usb port. But it just couldn't establish a connection with

Hi, fellow NUT gurus; I am having a big issue with our new Powercom Imperial Digital UPS. The UPS is come with a serial over USB port and plug into the usb port on the computer. I am having problem to setup our fedora 7 linux machine talks to the ups. The kernel 2.6.22.1 seems to be able to detect the ups is plug into one of its usb port. But it just couldn't establish a connection with

Hello, following up on myself, it was suggested on IRC that I better attach a dmesg output. Here's the output of a clean boot & echo 0f > /sys/.../pstate cycle. I can't spot a message that relates to the reclock action, and there's only one weird "nouveau 0000:04:00.0: clk: base: 7 MHz, boost: 7 MHz" message. On the other hand: # cat

On Dec 11, 2014, at 5:43 AM, janc at telefonica.net wrote: > 0.339329 Entering libusb_get_report > 0.342986 Report[get]: (2 bytes) => 01 00 > 0.343085 Path: 008c0001.008c0003, Type: Feature, ReportID: 0x01, Offset: 0, Size: 8, Value: 0 > 0.343120 Entering libusb_get_report > 0.346953 Report[get]: (2 bytes) => 02 00 > 0.346993 Path: 008c0001.008c0002,

Hello everyone, Charles suggested (about a week ago) that I repost to this list. I took a moment to run some additional tests ... The basics: -- UPS: Liebert PowerSure PSA 500 (from the 230 VAC / 50 Hz line) -- Kernel: 2.6.11.5 (from sources), USB support (down to and including CONFIG_USB_HIDDEV) compiled in statically (not as a module) -- Rest of OS: Basically still from the original SuSE

Hi Please could someone assist me? I?e got a 3g usb dongle - Huawei E1552. [root@]# lsusb Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 007 Device 002: ID 03f0:8407 Hewlett-Packard Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus

Hi! Charles. This is the output with 'explore' # ./usbhid-ups -DDDD -u root -x explore -x vendorid=06da -a CENER_LA900_usb Network UPS Tools - Generic HID driver 0.37 (2.6.4) USB communication driver 0.32 0.000000 debug level is '4' 0.000676 upsdrv_initups... 0.288980 Checking device (06DA/0002) (008/004) 0.316956 - VendorID: 06da 0.317057 - ProductID: 0002

Hi, I have two ups (Turbo-X 1000SD, Turbo-X 1500SD). The both report themselves as # lsusb Bus 008 Device 002: ID 0001:0000 Fry's Electronics The are produced by MEC and report MEC0002 as product (although the working one report it in dmesg but not in lsusb) The 1000 (bcdUSB 1.00) works with blazer_usb while the 1500 (bcdUSB 1.10) doesn't. I am attaching lsusb and blazer_urb output

please subscribe to the nut user mailing list ( http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser) and post the output of "/path/to/usbhid-ups -DDDDD -a <your_ups_name_in_ups.conf>" cheers, Arnaud -- Linux / Unix Expert R&D - Eaton - http://www.eaton.com/mgeops Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer -

Hi, I have been trying to figure out why the S100U is not performing very well on RH9.. Here is my thinking..( may be totally wide of the mark but here goes anyway) I remember reading somwhere that the sound system used by RH has changed... Does the S100U not depend on the sound subsystem?? So what I think is that the sound subsystem in RH9 and the S100U are not happy working together.. Does

Peter Selinger wrote: > Hm. I need more information, as NUT seems to garble the values even > before I can see them. I am not so worried about the date and > temperatures (although, strangely, the battery replacement date > appears to be Sept 25, 2001, which makes no sense). But the voltage is > definitely important. > > [...] > Thanks Peter - I'll send the new

Hi, I know it's been a topic many times here, but I've searched the archives, googled for days, and I simply don't believe, that there is still no solution to this. I'm using a PowerCom BNT-600AP ups with usb port. I've downloaded the latest version from svn, compiled it, and tried to use it: * megatec(_usb) - no luck, it did not find the UPS (I?ve read in this list, that

Hello, I’ve a problem with start driver for PowerCom KIN-600AP RM. The driver is “usbhid-ups”, see “No matching HID UPS found” when I trying to start driver. Ubuntu version is 18.04 LTS. My ups.conf: [powercom] driver = usbhid-ups port = auto vendorid = 0d9f productid = 0004 Start driver with: ./usbhid-ups -a powercom -DDDDD ... 0.032993 Unable to get HID descriptor (error sending

In a separate discussion, on 6/26/17 4:04 AM, Arnaud Quette wrote: > Hi > > If you're sure it's a HID device, add an entry in drivers/powercom-hid.c > { USB_DEVICE(POWERCOM_VENDORID, 0x0002), NULL }, > > Then autogen.sh + configure... > Please also report back so that I can update the code > > Cheers > Arno Thanks! I don't *know* whether or not