similar to: Some newhidups questions

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

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, I think this question is mainly for Arnaud again: When I run my UPS directly with newhidups -D -D -D, with no data changes, and I then observe the interaction with my UPS (still Back-UPS ES 650 FW:818.w1.D USB FW:w1), I see the updateinfo cycle through 3 different forms: (1) a (2 bytes) => 06 08 notification that provides one item: UPS.PowerSummary.APCStatusFlag Note that

This took a long time because I had problems with my system. After I reloaded my operating system several times I found I had a bad memory module. Here is the output from newhidups for my Geek Squad GS1285U. It just kept repeating until I hit ctl-z. I think that this means nut will work for this ups. My computer is not powered by the ups yet. I did not want it to be powered down by accident.

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 Peter, I got all your patches and applied them, and I wanted to say kudos for a great job done. This is the output of upsc that I'm getting right now. I had the same issue when using any cvs version (from two weeks ago) that made my UPS go into a state where it wasn't functioning normally (checking the kernel log shows that it cannot be connected and I had around a page of DEVFS_USB

Charles Lepple wrote: > > would you mind forwarding (to either me, or the list) the .txt file > showing the hidparser bug? I am trying to revamp libhid's hidparser, > and it would be helpful to have the descriptor. The text file is contained in the tarball on the patch tracker, at

I tested your fix (newhidups -DDD /dev/null) using both and APC Back-UPS 350 an APC Smart-UPS RT 2000 XL. No more segmentation fault due to the fixed-size array. ~Jacob -----Original Message----- From: nut-upsdev-bounces@lists.alioth.debian.org [mailto:nut-upsdev-bounces@lists.alioth.debian.org] On Behalf Of Peter Selinger Sent: Monday, October 16, 2006 12:12 PM To: Schmier, Jacob Cc: NUT

2005/9/25, Peter Selinger <selinger@mathstat.dal.ca>: > > Arnaud Quette wrote: > > > > Some more points while you're at it: > > - newhidups will have to be renamed. My aimed was to let the name until > we > > can superceed hidups. Then remove hidups, and rename newhidups to > usbhid-ups > > (name proposition welcomed, but should match the fact

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

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

Has anyone gotten the newhidups driver to work w/ the Powerware 9120 series? Here's what I get for debug info (It's the Phoenixtec device): $ sudo lsusb Bus 002 Device 002: ID 0846:1040 NetGear, Inc. Bus 002 Device 001: ID 0000:0000 Bus 001 Device 002: ID 06da:0002 Phoenixtec Power Co., Ltd Bus 001 Device 001: ID 0000:0000 $sudo /lib/nut/newhidups -DDDDD auto Network UPS Tools: New

Paolo, Try sudo /lib/nut/newhidups -DDD -u root -a SmartUps1500 newhidups would only run on my computer if I ran it using sudo and as root user. I know this indicates a problem with the USB permissions, but I could not, for the life of me, get the permissions to change when I plugged the UPS in. I know this isn't a true fix, but it worked for me. -- ~Brian Foster

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):

Dear List, I have an MGE Ellipse 1500. I run openSUSE 10.2, kernel 2.6.18, libusb 0.1.12, nut 2.0.5. ps shows that the following processes are running: /usr/lib/ups/driver/newhidups -a mgeups /usr/sbin/upsd -u root /usr/sbin/upsmon /usr/sbin/upsmon NUT operates correctly, shutting down the server after 4 minutes without power. However I'm seeing 25 to 50 messages logged each day in

Here is a summary of the changes I made to newhidups today (between the tags after_PSE_6 and after_PSE_9, roughly). * all the vendor-specific code that was in various "switch" statements has now been moved to the individual subdriver (apc-hid, mge-hid, belkin-hid) files. This also includes the vendor-specific Usage tables. In future, it should be quite easy to add new

2006/1/13, Paul Mogren <fkamogee@yahoo.com>: > > This thread is FYI. I don't need any help here. > no, but some details for those who will read it, maybe ;-) I have SUSE 10.0 and an MGE Ellipse. I installed the NUT package from MGE. > > 1) The generated ups.conf pointed to a bad location: > /dev//dev/input/event0 > who generated that ? it seems like an old hiddev

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

Whenever I try to use the newhidups driver with my new UPS I get the following message: #/lib/nut/newhidups -DDD -a SmartUps1500 Network UPS Tools: New USB/HID UPS driver 0.28 (2.0.4) debug level is '3' [...skip unrelevant device...] Checking device (051D/0002) (001/005) - VendorID: 051d - ProductID: 0002 - Manufacturer: American Power Conversion - Product: Smart-UPS 1500 FW:601.3.I USB

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. >