search for: 700i

...ut 18308 0.0 0.0 2620 708 ? Ss 15:14 0:00 /sbin/upsd nut 18326 0.0 0.0 2592 764 ? S 15:14 0:00 /sbin/upsmon $ sudo upsc Powerware5110 battery.charge.low: 11 battery.voltage: 13.5 battery.voltage.low: 10 device.mfr: Eaton device.model: POWERWARE UPS 700i device.part: 103004267-5591 device.serial: device.type: ups driver.name: bcmxcp_usb driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.version: 2.7.1 driver.version.internal: 0.28 input.frequency: 49.9 input.frequency.high: 55 input.frequency.low: 45 input.frequency.nominal: 50 in...

On Feb 12, 2014, at 7:50 PM, Tim Dawson wrote: > Run the driver with -DDDDD and see what variables it picks up. I have noted that with the Prestige 9 in bcmxcp, some variables are not consistent within models, and had to do some gentle remapping to get things to work correctly. Tim, is this the issue you mentioned on 2014-02-02 with blocks 0x9 and 0x13? I'll reply to that email. > On

...m avoiding Eaton/Powerware because the lack of usbhid support, the > bcmxcp driver doesn't report much bootc at tarquin ~ $ upsc pw9120 ambient.temperature: 10 ambient.temperature.high: 40 battery.charge: 100 battery.runtime: 720 battery.voltage: 26.0 device.mfr: Eaton device.model: PW9120 700i device.serial: RY346A0036 device.type: ups driver.name: bcmxcp_usb driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.parameter.shutdown_delay: 60 driver.version: 2.6.5 driver.version.internal: 0.26 input.frequency: 50.0 input.frequency.high: 52 input.frequency.low: 48 input.freque...

Luke-Jr wrote, On 9/18/2013 1:02 PM: > I wanted to suggest some rating for functionality. I got the UPS available > that seemed to have the best possible rating from NUT's list (Eaton Powerware > UPS 1500), and found out it doesn't support telling me battery level or > runtime! :/ I'm avoiding Eaton/Powerware because the lack of usbhid support, the bcmxcp driver

I wanted to suggest some rating for functionality. I got the UPS available that seemed to have the best possible rating from NUT's list (Eaton Powerware UPS 1500), and found out it doesn't support telling me battery level or runtime! :/ Luke

Hi all, I just acquired a new UPS and have been trying to get it to work with NUT. It's an Eaton/Powerware 9120 700i with both USB and RS-232 interfaces. I first tried the USB interface (using bcmxcp_usb) and found that the UPS worked fine for a few minutes but then NUT lost communication and didn't get it back. In addition the UPS itself seemed to lock up at one point such that the inverter shut off and the...

...Ss 15:14 0:00 >/sbin/upsd >nut 18326 0.0 0.0 2592 764 ? S 15:14 0:00 >/sbin/upsmon > >$ sudo upsc Powerware5110 >battery.charge.low: 11 >battery.voltage: 13.5 >battery.voltage.low: 10 >device.mfr: Eaton >device.model: POWERWARE UPS 700i >device.part: 103004267-5591 >device.serial: >device.type: ups >driver.name: bcmxcp_usb >driver.parameter.pollinterval: 2 >driver.parameter.port: auto >driver.version: 2.7.1 >driver.version.internal: 0.28 >input.frequency: 49.9 >input.frequency.high: 55 >input.freq...

...conf MONITOR eaton5s at localhost "Eaton 5S 700" --------------------------------------------------- nut.conf MODE=netserver --------------------------------------------------- ups.conf maxretry = 3 [eaton5s] driver = usbhid-ups port = auto desc = "Eaton 5S 700i UPS" vendorid = "0463" productid = "FFFF" pollinterval = 15 [heartbeat] driver = dummy-ups mode=dummy-loop port = heartbeat.conf desc = "Watch over NUT" --------------------------------------------------- ups...

On Feb 15, 2014, at 6:46 PM, Greg Vickers wrote: > Thanks! I've attached the file to this email (bcmxcp_usb.output2014160926.gz), it ran for 12 seconds, and looks like it's looping by that time. I'm not sure what to look for, does grepping for 'Yes' show the variables that the driver can pull off this UPS? The boolean variables seem to be indicated by "Yes". I

...R eaton5s at localhost "Eaton 5S 700" --------------------------------------------------- nut.conf MODE=netserver --------------------------------------------------- ups.conf maxretry = 3 [eaton5s] driver = usbhid-ups port = auto desc = "Eaton 5S 700i UPS" vendorid = "0463" productid = "FFFF" pollinterval = 15 [heartbeat] driver = dummy-ups mode=dummy-loop port = heartbeat.conf desc = "Watch over NUT" ----------------------------------------------...

...R eaton5s at localhost "Eaton 5S 700" --------------------------------------------------- nut.conf MODE=netserver --------------------------------------------------- ups.conf maxretry = 3 [eaton5s] driver = usbhid-ups port = auto desc = "Eaton 5S 700i UPS" vendorid = "0463" productid = "FFFF" pollinterval = 15 [heartbeat] driver = dummy-ups mode=dummy-loop port = heartbeat.conf desc = "Watch over NUT" ----------------------------------------------...

On 16/02/14 00:38, Charles Lepple wrote: > On Feb 15, 2014, at 2:57 AM, Tim Dawson wrote: >> The driver will poll the UPS for what variables it supports when it starts, and then go into a polling loop. Look for a section defining the meter map, and you should see the result, as well as the raw data. > Tim: spot on. > > Greg, > > If you want, you can capture the -DDDD output