similar to: Belkin w/ Cypress Semi. interface probs

I recently bought a Belkin F6H375 UPS. It connects to the computer via USB. Searching the Internet led me to believe that the megatec_usb driver in nut supports this UPS, however I've been unable to get it to work. I have this in ups.conf: [belkinusb] driver = megatec_usb port = auto desc = "Belkin USB" Here's what happens when I try to use it: ~ #

[moving this thread to nut-upsdev] On Jan 12, 2008 5:54 PM, Alexander I. Gordeev <lasaine at lvk.cs.msu.su> wrote: > On Sun, 13 Jan 2008 01:30:37 +0300, Charles Lepple <clepple at gmail.com> > wrote: > > when you figure this out, can we make sure that we know which > > changesets would need to be back-ported to branches/Testing (since > > that is where we would

[moving this thread to nut-upsdev] On Jan 12, 2008 5:54 PM, Alexander I. Gordeev <lasaine at lvk.cs.msu.su> wrote: > On Sun, 13 Jan 2008 01:30:37 +0300, Charles Lepple <clepple at gmail.com> > wrote: > > when you figure this out, can we make sure that we know which > > changesets would need to be back-ported to branches/Testing (since > > that is where we would

I have upgraded to CentOS5 on our computers. I had been using Mandriva 2006. The problem I am having is that the networkupstools (nut-2.0.4.tar.gz) does not find the UPS device. However, when I had Mandriva 2006 on the same hardware it worked. The device manager on CentOS does show the UPS device. The settings I used in the ups.conf file are: driver = newhidups port = auto Using the same

I have changed over to CentOS5 on some of our computers. I had been using Mandriva 2006 and the nut software worked using: driver = newhidups port = auto Using the same version of nut with the same config files on CentOS5, I get the following error output from 'upsdrvctl': Network UPS Tools - UPS driver controller 2.0.4 Network UPS Tools: New USB/HID UPS driver 0.28 (2.0.4) No

I have changed over to CentOS5 on some of our computers. I had been using Mandriva 2006 and the nut software worked using: driver = newhidups port = auto Using the same version of nut with the same config files on CentOS5, I get the following error output from 'upsdrvctl': Network UPS Tools - UPS driver controller 2.0.4 Network UPS Tools: New USB/HID UPS driver 0.28 (2.0.4) No

Browsing through the newhidups.c code, I stumbled across the following: /* master list of avaiable subdrivers */ static subdriver_t *subdriver_list[] = { #ifndef SHUT_MODE &generic_subdriver, #endif &mge_subdriver, #ifndef SHUT_MODE &apc_subdriver, &belkin_subdriver, &tripplite_subdriver, NULL #endif }; Shouldn't the 'NULL' terminator be outside 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()

Hi, I bought a Belkin Active Battery Backup UPS (http://www.belkin.com/uk/activebattery/) yesterday with a USB port and hoped it would work with nut. The device will show up in /proc/bus/usb/devices as a Cypress Semiconductor USB to Serial. It creates /dev/hiddev0 (and this disappears when the UPS is unplugged). I've tried using belkin, belkinunv, usbhid-ups and megatec_usb. I've tried

Ok, I tried this from scratch on a fresh 2.7.2 directory. I followed the web instructions, specifically: + I generated the new subdriver for my UPS (rtd-hid.*) based on PATH info. + I put them in the drivers subdir + I added the include line (#include rtd-hid.h) in usbhid-ups.c (specifically in the #ifndef SHUT_MODE section) + I added &rtd_subdriver, to the subdriver_list in usbhid-ups.c

Hi, (please let me know if there is a better place to submit bugs) I run a FreeBSD box with stack-protector enabled, which raises a problem in the upsdrv_initups() function of the newhidups.c module; the regex_array variable is sized one item too small. Regards, Herve Masson <<<< void upsdrv_initups(void) { int i; #ifndef SHUT_MODE /*! * SHUT is only supported by

Sorry for the bad formatting of the previous message...I tried to use plus signs as bullet points, and that caused a problem somehow. Ok...I discovered that if I do the autoreconf after the first failed make (and the autoreconf still gives that error message), and then do make again...it builds. Conclusions: 1) Autoreconf *must* be run, and not ./configure? I had thought that putting in my *.c

Some UPSes contain HID report descriptors that fail to correctly describe the contents of reports. For example, the OpenUPS descriptor fails to set the units, logical maximum and logical minimum before the corresponding `main item' as required by the HID specification. This commit allows an override HID report descriptor to be given to usbhid-ups which replaces the one produced by the UPS,

Hi Patrick, I didn't get further bug reports from you, so I have now listed your device as "supported" by newhidups. Last I saw as of your below message, the driver was working as expected. If there are any future problems, let me know! -- Peter Patrick Nolan wrote: > > Remember me? Back in May we exchanged some messages about my Tripp-Lite > UPS. My boss has gone on

Hi Patrick, Patrick Nolan wrote: > > Remember me? Back in May we exchanged some messages about my Tripp-Lite > UPS. My boss has gone on vacation, so I finally got a chance to take a > look at this. > > Peter Selinger wrote: > ... > > In case you feel like experimenting with this, I am attaching a patch > > that *might* enable this device to be supported by the

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

Gentlemen, I have a new HID USB device, that seems to be quite similar to the currently supported APC HID UPS. I append the dump-tree output, and would much appreciate advice on how to proceed. Certain entries for the current device are not available, but maybe there are some replacements that could be used. This may of course require a new table in apc-hid.h, and I would prefer not to do this

Gentlemen, Please note that what follows pre-dates the latest changes from Arnaud (just thought someone might want to look at these before I can test the latest!). When running newhidups with -D -D -D I saw messages that looked like errors, and it took me a while to understand that they were not really errors. I therefore added two new entries in apc-hid.h, and I modified a couple of diagnistic

So, I have this Mustek Powermust 600USB (no serial port) here temporarily. It seems to be a hid device. The output from "lsusb -v" and "newhidups -DDDDD" (with "generic" and "vendorid=06da") are (respectively): ----------------------------------------------------------------------------------------------- Bus 001 Device 002: ID 06da:0003 Phoenixtec Power

Hi, I'm attempting to port an application which uses the Cypress CyAPI, which is Windows only, though I don't know if wine can handle device drivers or such low-level stuff. Anyway, I tried to develop a little prototype to run under wine, hoping it would provide with some insight. But this is the output I get: fixme:setupapi:SetupDiGetClassDevsW : returning empty list