On Tue, 5 Feb 2008, Luki wrote:
> Daniel, thanks a lot for your help, now it works perfect, I was able
> to connect to UPS via serial line and gather statistics, rest of
> configuration left but the most important point achieved ;)
> I have done exactly as you suggested to create /etc/devfs.rules f
Hi,
I bought a Belkin Active Battery Backup UPS
(http://www.belkin.com/uk/activebattery/) yesterday with a USB port and
hoped it would work with nut.
The device will show up in /proc/bus/usb/devices as a Cypress
Semiconductor USB to Serial. It creates /dev/hiddev0 (and this
disappears when the UP
On Mon, Feb 04, 2008 at 08:13:21PM +0200, George wrote:
> Hi,
>
> Well I was able to make it workwith a java application called
> MultiLink which I downloaded from the Liebert website.
>
> The bad part of this Java app is that it requires a XWindow system
> like KDE or Gnome.
Many people, includ
On Sat, Feb 02, 2008 at 04:02:01PM +0200, George wrote:
> Hi,
>
> I have a Liebert GXT2-1000RT230 UPS that is connected to my server
> using a serial cable.
>
> I have no idea to what port exactly it is connected so my first
> question is: how do I find out what /dev/tty** should I use?
>
> Do I
Hi,
Well I was able to make it workwith a java application called
MultiLink which I downloaded from the Liebert website.
The bad part of this Java app is that it requires a XWindow system
like KDE or Gnome.
Thanks
On 2/4/08, Alain Williams <[EMAIL PROTECTED]> wrote:
> On Sat, Feb 02, 2008 at 04
Daniel, thanks a lot for your help, now it works perfect, I was able to
connect to UPS via serial line and gather statistics, rest of
configuration left but the most important point achieved ;)
I have done exactly as you suggested to create /etc/devfs.rules file and
I have added "nut" user to di
> For USB I created /usr/local/etc/devd/nut.conf with entries like..
> attach 100 {
> device-name "ugen[0-9]+";
> match "vendor" "0x0463";
> match "product" "0x";
> action "chown uucp /dev/$device-name*; chmod 660 /dev/$device-name*";
> };
>
>
>
Ok first I w
Hi Jimmy,
Problem still occurs, I have removed serial connection, only usb left.
I use your configuration and that's what I receive :
[EMAIL PROTECTED] /]# /usr/local/ups/bin/upsdrvctl start mustekups-usb
Network UPS Tools - UPS driver controller
Network UPS Tools - Megatec protocol driver 1.5.4
On Mon, 4 Feb 2008, Jimmy Jazz wrote:
> for the serial output in your init.d nut file
>
> set_serial() {
> for n in $@; do
> [ -e /sys/class/tty/ttyS${n} ] || continue
> mknod /dev/ttyS${n} c 4 $(( 64 + n )) && chown
> nut:uucp /dev/ttyS${n}
> done
>
Hi,
i was using the same device. Just don't try to use the usb and serial
outputs at the same time.
/etc/nut/ups.conf
#[mustekups]
# driver = megatec
# port = /dev/ttyS0
# desc = "Mustek PowerMust 1000VA USB"
# mfr = "Mustek"
# model = "PowerMust 1000 USB"
#
#[must
I've logged a patch tracker for this:
https://alioth.debian.org/tracker/index.php?func=detail&aid=310561&group_id=30602&atid=411544
2008/2/4, Arnaud Quette <[EMAIL PROTECTED]>:
> 2008/2/3, Huge <[EMAIL PROTECTED]>:
> > Is anyone here running a USB UPS on Solaris? I'm looking to upgrade my
> > UPS
2008/2/3, Huge <[EMAIL PROTECTED]>:
> Is anyone here running a USB UPS on Solaris? I'm looking to upgrade my
> UPS (from a SmartUPS 620 with RS232 comms), and most of the modern UPSs
> use USB ...
though the maturity is not the one of Linux, this code is quite stable.
I've attached a small README
12 matches
Mail list logo
