similar to: newhidups: today's changes

I have gone ahead and merged the regex_branch with the main Development branch. Reason: recent renaming of files and moving around of code leads to conflicts between the branches that will be increasingly difficult to resolve. It is easier to merge now while the two branches are still relatively similar and most edits non-overlapping. The merge is between tags before_PSE_6 and after_PSE_6 on

Zaid, I have a Belkin F6C800-UNV which has both a serial and USB connector. The serial connection is already working with the Belkinunv driver. I will connect via the USB and then compare both sets of variables. This should allow me to correlate and shed some light on the meaning of many of Belkin's non-standard "Usage" descriptors. With this information, it should be very easy

Hi, I got a Belkin F6C550-AVR UPS today and was trying to get it working with NUT, I used the "hidups" driver and got some data out of it, mainly the following: battery.charge: 100 battery.runtime: 120 driver.name: hidups driver.parameter.port: /dev/usb/hiddev0 driver.version: 2.0.0 ups.mfr: Unknown ups.model: Unknown ups.serial: Unknown ups.status: OL the versions of NUT that I tried

Hi, I got a Belkin F6C550-AVR UPS today and was trying to get it working with NUT, I used the "hidups" driver and got some data out of it, mainly the following: battery.charge: 100 battery.runtime: 120 driver.name: hidups driver.parameter.port: /dev/usb/hiddev0 driver.version: 2.0.0 ups.mfr: Unknown ups.model: Unknown ups.serial: Unknown ups.status: OL the versions of NUT that I tried

Hello everyone! If this message was posted twice, my apologies. I'm having issues with my webmail today... I am using the testing version of NUT from SVN at changeset 582. I have successfully created a stub for newhidups driver for my Dynex DX-800U UPS, but I am completely lost on the customization of it. I've followed the hid-subdrivers.txt instructions and I understand I need to

Hi Scott, Scott Alfter wrote: > I had a UPS go bad recently (shuts off all by itself for no good reason, >AFAICT), so I bought a CyberPower 685AVR this afternoon. The two CyberPower >drivers in NUT 2.0.2 don't know how to talk to it, but the hidups driver >appears to work properly. This means you have to use USB instead of RS-232 (it >supports both), but at least it works. >

Hi all, I've tried installing NUT from both the Debian packages and the 2.0.4-pre1 source but I'm unable to sort out the USB permissions when using the newhidups driver and an APC XS series UPS. In each case, I'm able to run newhidups as user root but running it as user nut fails: --- as 'nut' # /lib/nut/newhidups -u nut -a apc1 Network UPS Tools: New USB/HID UPS driver 0.28

Hello, I am having trouble getting upsd to start. I am using the Debian NUT packages version 2.0.3 (current in Debian/sid). I am using the newhidups driver with an APC Back-UPS BR 800. The init.d script wasn't functioning, so I backtracked to running upsd manually and I get: foxstar:/etc/nut# upsd -u root Network UPS Tools upsd 2.0.3 Can't connect to UPS [foxstarups] (newhidups-auto):

Hi I'd like to know what you guys think to the following idea. Please be aware, C/C++ are not exactly my strongpoint (couldn't be much further from it actually..!), so I'm not sure whether this is all legal code. -- SYNOPSIS: Allow a newhidups subdriver to register that it can handle settings in ups.conf (and via -x on the command line), as per the normal serial drivers.

I have checked in a cleaned-up version of patch #302111 (Belkin support) into CVS. See cvs diff -uN -r before_PSE_2 -r after_PSE_2 to check the difference. Here is the CHANGES entry: Tue Sep 13 20:50:14 UTC 2005 / Peter Selinger <selinger@users.sourceforge.net> - newhidups: added Belkin support. Also added some new variables and instant commands (some of these were already used by

I can start the driver successfully manually, after the machine is up and running, but at boot time, it can't find my UPS. My init script makes sure that the usbfs is up (by checking for the existence of /proc/bus/usb/devices), and I can't think of what else could be different with the boot-time failure versus the manual startup after logging in. I'll include my configuration at the

Hi. I'm having trouble with nut-2.0.3 on a linux kernel 2.4.32 machine and a MGE Evolution 3000. The problem is that I'm getting the following message, repeatidly, on dmesg: usbdevfs: usb_submit_urb returned -22 (-22 means -EINVAL) I traced the problem with newhidups -DDDDDD auto and found out that the -22 error appears in a line "none (-22)" of the output as: ----------

I'm trying to get nut to work with a Cyberpower 900AVR. There are many different products known by this name, but this one has the extra name 'BC900D'. I am told by a cyberpower tech that this one should talk exactly the same USB protocol as the 685AVR, which was recently made to work with newhidups. Unfortunately, when I run the SVN checkout (trunk) of nut-2.1, I get: sstreet

Hi, I'm running nut 2.0.3 on Gentoo connected to an MGE ProtectionCenter 675. newhidups intermittently crashes. Any ideas? N. # /usr/lib/nut/newhidups -a mgeups Network UPS Tools: New USB/HID UPS driver 0.28 (2.0.3) Detected a UPS: MGE UPS SYSTEMS/PROTECTIONCENTER Using subdriver: MGE HID 0.8 This is the error I'm getting *** glibc detected *** /usr/lib/nut/newhidups: double free or

Hi Arnaud, hi all I wish you all the best for 2006. Enjoying of some less stressed time, I follow your advice, Arnaud, to switch our UPS management on the newhidups driver. ( Enfin ! ;) Our goal is to support (soon) the new MGE ASR ELLIPSE ( and of course also the old ELLIPSE and EXTREME models ). I rebuild the libusb-0.1.10a packages to conform to our installation process. I perform the same

j T wrote: > >- allow the value to be NULL if a subdriver does not require > > initialization. > > Am I right in thinking that this is simply a case of doing: > > subdriver_t some_subdriver = { > /* ... */ > some_format_serial, > NULL, > } > > Rather than: > > subdriver_t belkin_subdriver = { > /* ... */ >

Hi there, been using NUT for ages and recently upgraded to a new server; while I'm waiting for a USB->Serial adapter for Solaris to arrive, I thought I'd play with the newhidups, as the APC UPS I have has a USB port and the new server doesn't have a serial port.... I've got Solaris 10 & newhidups working with the ugen driver up to a point, and that is a read

Hi Is there any way to have a newhidups subdriver register that is can handle settings from ups.conf, as per a "normal" nut driver? In, for example, belkinunv.c, there are various addvar() calls in the upsdrv_makevartable() function, but I can't work out where addvar() calls should be put in an HID subdriver. Thanks Jo Turner -)O(-

I ran into the following issue today and would like some feedback from the group. Setup: I am using a MGE Pulsar Evolution 2200 UPS connected through a Belkin (F5U218-MOB) 4-Port USB Hub. Scenario: The newhidups subdriver_matcher function calls belkin_subdriver->belkin_claim. The belkin_claim function in belkin-hid.c matches the VendorID of the hub to Belkin's VendorID (0x050d), causing

There is a memory leak in newhidups. After 23 days uptime it used 138M memory. Apart from the memory leak, the system works ok. Is there anything I can do to help fix this problem? Tor. [root@tophat init.d]# ps -unut v PID TTY STAT TIME MAJFL TRS DRS RSS %MEM COMMAND 21122 ? Ss 1:35 0 69 137934 136800 27.0 /sbin/newhidups auto 21125 ? Ss 0:37 0