similar to: [UPS on Serial vs. USB] USB slow to update, serial instant.

Displaying 20 results from an estimated 10000 matches similar to: "[UPS on Serial vs. USB] USB slow to update, serial instant."

2009 Oct 13
6
USB/UPS connectivity issue on Intel DP55KG Motherboard
Hello, I use the following in my ups.conf: # USB: [apc] driver = usbhid-ups port = auto desc = "APC 1500VA" pollfreq = 5 On my new motherboard (an Intel DP55KG), every once and awhile I get this: Broadcast Message from nut at box.com (somewhere) at 17:48 ... Communications with UPS apc at localhost lost Broadcast Message from nut at box.com
2007 Jun 13
4
false alerts/shutdown
Hello, I've installed Nut (2.0.5) on RedHat a week ago, and upsmon seems to generate false alarms every hour: ... Jun 8 06:10:56 nutevalserver upsmon[2849]: UPS usb-mge-evolution at localhost on line power Jun 8 06:35:46 nutevalserver upsmon[2849]: UPS usb-mge-evolution at localhost on battery Jun 8 06:35:51 nutevalserver upsmon[2849]: UPS usb-mge-evolution at localhost on line power
2007 Jul 28
1
nut 2.0.5-3+b1 reports low battery, previous versions do not
Package: nut Version: 2.0.5-3+b1 Running: Debian Testing Arch: x86_64 BUG: (the battery is relatively new (6mos) and there have been no recent power outages) Jul 28 04:29:44 p34 upsmon[2402]: UPS belkin at localhost battery is low Jul 28 05:13:15 p34 upsmon[2402]: UPS belkin at localhost battery is low Jul 28 05:14:05 p34 upsmon[2402]: UPS belkin at localhost battery is low FIX: (go back to
2007 Feb 21
5
nut suddenly stopped working...
I almost had nut_2.0.5-3_i386.deb (from http://packages.debian.org/unstable/admin/nut - installed via dpkg, not via repository) working: * problems with getting it to come up during boot * monitoring via knutclient was OK * shutdown on low battery worked adequately, if not quite as described) and newhidups suddenly stopped talking to my Belkin F6C550-AVR . It's only been in use for a
2007 Dec 25
2
mge pc 675 does not work with usb-hidups
On opensuse 10.3, i installed nut and configured my ups.conf like i did it on opensuse 10.2 by putting (10.3 , nut 2.2.0): [MGEpc675] driver = usbhid-ups port = auto desc = "MGEpc675" instead of (10.2 , nut 2.0.4) : [MGEpc675] driver = newhidups port = auto desc = "MGEpc675" But it doesn't work. It appears that upsdrvctl
2007 Feb 16
5
MGE Nova AVR 600 USB on FreeBSD
Hi, I've seen a few emails in the archives about problems polling MGE UPSs via USB under FreeBSD, but unfortunately I didn't find a solution in them that works for me. A few details about my setup.. The UPS is a MGE Nova AVR 600 connected via USB to a FreeBSD 6.2 box. I have tried both the nut port (2.0.5) and the svn trunk but have had no success yet. I am running nut as root to
2007 Feb 16
5
MGE Nova AVR 600 USB on FreeBSD
Hi, I've seen a few emails in the archives about problems polling MGE UPSs via USB under FreeBSD, but unfortunately I didn't find a solution in them that works for me. A few details about my setup.. The UPS is a MGE Nova AVR 600 connected via USB to a FreeBSD 6.2 box. I have tried both the nut port (2.0.5) and the svn trunk but have had no success yet. I am running nut as root to
2005 Aug 19
1
MGE Ellipse 800 USBS doesn't shutdown under FreeBSD
Hi all, First of all thanks for the great work on nut ! (despite it's not fully functional yet overhere). Everything seemed to go fine until the final test : shutdown the UPS ! The system is running FreeBSD 5.3, the UPS is MGE Ellipse 800 USBS both linked with the MGE serial cable. The system is a remote server, only running some file services and large disks. The porting,
2006 Nov 16
6
FreeBSD 6.1, MGE Ellipse ASR600USBS, newhidups & upsd
Hello, I'm facing problems as I'm installing NUT to monitor a MGE Ellipse ASR600USBS on a FreeBSD 6.1 box. UPS is recognized as : ugen0: MGE UPS SYSTEMS ELLIPSE, rev 1.10/42.41, addr 2 I'm temporarily using root profile (devfs/devd scripts not modified atm). newhidups starts & runs fine (unplugging mains makes newhidups outputs lots of data when started with -DDDD flags)
2015 Aug 14
2
occassional problem wtih upslog and apc ups units via snmp ... [NA] status
I see this in syslog: Aug 12 03:57:22 orion upsd[18274]: Data for UPS [a102-apc-10] is stale - check driver (one for each UPS). Then I see a bunch of messages like this: Aug 12 03:58:02 orion upsd[18274]: write() failed for ::1: Broken pipe Aug 12 03:58:02 orion snmpd[2872]: Connection from UDP: [127.0.0.1]:50940 And then it returns to normal like this: Aug 12 03:58:04 orion upsd[18274]: UPS
2009 Jan 20
4
Mustek PowerMust 848
An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20090120/ffb91e55/attachment.htm
2008 Mar 06
3
problem with output voltage on a mustek ups
Hi there I have a Mustek PowerMust 1000 USB using serial port /dev/ttyS0. I use nut 2.2.1 with the megatec driver on Debian Lenny (testing), running on an AMD64 X2. (I was using a Debian Etch as slave, but to keep it simple I turned it off) My problem is that sometimes the UPS is running OK, but when the message "UPS is trimming incoming voltage" appears on knutclient (i.e. OL TRIM in
2008 Oct 04
3
Bug#501087: nut: support for a tripplite avr750u
Hi Raphael, btw, are you 2 bugs today a simple coincidence with my linkedIn invitation yesterday? ;-) 2008/10/4 Raphael Geissert <atomo64 at gmail.com>: > Package: nut > Version: 2.2.2-8 > Severity: wishlist > Tags: patch > > Attached is a patch adding "support" for tripplite's avr750u UPS. > Issues: > * productid still needs to be specified in
2007 Nov 08
1
Upsonic PrOffice 650 usb/serial
Hi, I recently installed a Upsonic PrOffice 650 UPS, which is a cheap model[1] available in Australia. It has a serial and USB port, and comes with a note saying WinPower software can be downloaded from [2]. Investigation of the software shows it to be Java with native libraries for serial and USB. Disassembling various classes reveals it talks at 2400 baud, and has a protocol similar to
2007 Jan 27
2
"no longer stale" when disconnected with 2.0.5 newhidups
Hello, I'm using driver newhidups with APC Back-UPS CS 500. Most things works fine except the following: After I disconnect the UPS the upsd write "Data for UPS [apc] is stale - check driver" in /var/log/messages. In the same second it tells "UPS [apc] data is no longer stale". This repeats all the time the ups is disconnected: Jan 25 14:45:03 degpn026w226 kernel: usb
2007 Aug 25
1
nut-2.2.0+linux kernel usb/hiddev bug
-> ups at p34 POWER ALERT on Sat Aug 25 07:40:01 EDT 2007 -> UPS belkin at localhost battery is low The last good version is 2.0.4, someone e-mailed me from this list before exactly why this happened it was about ignoring bad events from the usb-dev subsystem/kernel but I guess my question is this going to get fixed or should I stick with 2.0.4 as long as I can? Thanks. # ./usbhid-ups
2010 Jan 05
2
Conditional named_scope chaining with params (Need help)
Hello there, I have a model that has more then one named_scope. In my action Index of the controller that handle this model I want to do this in a drier way: if params[:ownership] == "mine" @posts = Post.tagged_with(params[:tags], :on => :tags).owner(current_user.id).paginate :all, :page => params[:page], :order => ''created_at DESC'' else
2005 Oct 30
2
GUI client?
It's very nice to see that NUT now supports my Belkin Universal UPS. Great work! Now I'm wondering if there's a GUI client that will build/run on a modern distribution. KNutClient requires an outdated version of Qt, and the "UPS Monitor" link leads to a Spanish error page. Thanks! -- ======================================================================== Ian Pilcher
2009 May 20
1
Windows Nut Client supporting hibernate.
I am aware of 2 windows nut clients both interestingly called winnut. One (winnut 2.0.0b) is a service based client based on a port of the but client code (I think). The other is a GUI client based on (I think again) on knutclient . I have corresponded with both authors about a feature request - to allow the shut-down action to be (optionally) a windows hibernate. This seems a very
2005 Nov 06
1
telling apart USB devices
I just noticed the following curious behavior when using newhidups with upsdrvctl and two different USB devices: My ups.conf contains two devices, both using newhidups: [belkinusb] driver = newhidups port = auto desc = "Belkin UPS, USB interface" vendorid=050d [mgeusb] driver = newhidups port = auto desc = "MGE UPS, USB