similar to: apc-hid.c: watts_to_av_conversion

Gentlemen, I have now had a chance to run some initial tests of my changes to apc-hid.c of the current development tree. Running newhipups and inspecting the -DDDD output seems to indicate that with the fix below everything seems to work as expected. However, I have not yet shut my system in order to take the UPS out of action so that I can do my various tests with a lightbulb load. I still hope

Hello Charles! As promised, I just checked out the CVS and recompiled everything. In the attached .txt is what is coming out from my UPS. I am wondering about all those zeroes. Also, this morning I plan to connect the UPS to a Win box running the monitoring program supplied with the UPS (UPSilon2000) and a USB sniffer program. If you have any suggestions on what to look for in the data,

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

Gentlemen, I have determined that on my UPS (APC Back-UPS ES 650 FW:818.w1.D USB FW:w1), the variable UPS.PowerSummary.RemainingCapacityLimit is writeable. I am setting this variable to start shutdown a little earlier. Appended is an unconditional patch for apc-hid.h. If, as indicated by the original code, there are APC UPS devices that don't allow setting of this variable, it becomes

Gentlemen, I just had time to start looking at the latest version of the development tree. I have built the apc-hid part of newhidups from the development tree and I am in the process of testing it with my "Back-UPS ES 650". As of right now I have incorporated the attached changes to apc-hid.c. I have been using the corresponding changes together with some changes from Arnaud with the

I got sick & tired of constant power outages with no warning, so when I saw various UPSes at the store, I decided to get one, and the one I got was a model 200897 from Newpoint (a.k.a. Power Sentry). A couple of days later the power went out and I decided to use the opportunity to hook up the UPS. I added up the wattages of the equipment I would be connecting, and found that the only way I

*********************** Your mail has been scanned by InterScan MSS. *********************** Has anyone managed to get this UPS to work? I am using the laster development nuts. My /proc/bus/usb/devices content: ==== cut ==== T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 2 Spd=1.5 MxCh= 0 D: Ver= 1.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=ffff ProdID=0000 Rev= 1.00 S:

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

Hello everybody! I am trying to get an Atlantis-Land OnePower Line Interactive S1501 UPS (actually it is made by Ablerex) to talt to my Linux box through its USB port (no more RS-232...), either using the supplied program (UPSilon2000, works under Win and Linux) or whatever else. The UPSilon2000 program apparently works OK *if* it can talk to the UPS via a serial port; since my UPS has

Hello everybody! I am trying to get an Atlantis-Land OnePower Line Interactive S1501 UPS (actually it is made by Ablerex) to talt to my Linux box through its USB port (no more RS-232...), either using the supplied program (UPSilon2000, works under Win and Linux) or whatever else. The UPSilon2000 program apparently works OK *if* it can talk to the UPS via a serial port; since my UPS has

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

I have a Belkin F6H500ukUNV ups that I am attempting to get working under nut, however it does not appear to be detected by nut, I'm assuming that I need to feed some information back to you guys to get it included in the database somwhere. I've included (what I can think might be) the relivant outputs. Please let me know if you require anything else. dmesg output /sbin/newhidsups

Dear Daniele, nice to meet you, I'm a collegue of Gabriele. The problem with "blazer_usb" driver ("blazer_ser" works correctly) is related to the following commands: - "F" and "I": when the KRAULER subdriver check these UPS answers it uses wrong constants to check the lenght of the received packets, so these commands are considered as "not

It's been a while since I tried to use NUT, so I thought I would give it another try. Big trouble. The UPS is a Tripp-Lite AVR 550U. It has only a USB connector. The computer is running Red Hat Enterprise Linux 4. I just installed NUT version 2.2.0. I'm going through the steps in the INSTALL document. # cat ups.conf [igor] driver = usbhid-ups port = auto

[snip hex dump analysis] > > It is possible that the blazer_usb driver initialization has put the UPS > into a bad state. If you can schedule some downtime, you might want to try > usbhid-ups again after powering the UPS down completely and unplugging it > for a little while. (Often, a few seconds after the output is off and the > AC has been removed, you will hear relays

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 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 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! Info OS: TinyCore Linux 4.5.6 NUT version: 2.6.4 NUT innstallation method: source tarball Device name: Eaton Ellipse ups eco 1600 usb din (EL1600USBDIN) /usr/local/ups/etc/ups.conf file: [eaton] driver = usbhid-ups port = auto When I run: root at Dalen:/usr/local/ups/bin/upsdrvctl start eaton I get this error message: Network UPS Tools - UPS driver controller 2.6.4

Hello! We have two upses: MGE Pulsar M 3000 and MGE Pulsar EXtreme 3200C. They connect to server by USB. EXtreme works good with usbhid-ups (nut 2.2.1) and newhidups (nut 2.0.5). But Pulsar M doesn't want to work with usbhid-ups. - my ups.conf: [extreme] driver = usbhid-ups port = auto product = "EXtreme" [pulsar] driver = usbhid-ups port =