--
From: Peter Selinger [EMAIL PROTECTED]
Sent: Wednesday, October 15, 2008 11:05 PM
To: nspag [EMAIL PROTECTED]
Cc: NUT user list nut-upsuser@lists.alioth.debian.org
Subject: Re: ups question from your web site
Dear Nick,
thanks for writing. I no longer
Dear Nick,
thanks for writing. I no longer work on development of UPS drivers;
you will probably get a more up-to-date answer from the nut-upsuser
mailing list (cc'd).
I don't know if the Back-UPS 550 has similar commands to the Back-UPS
ES 650. If it has a USB connection, then the answer is
Hi Shane,
please try the instructions at
http://www.mathstat.dal.ca/~selinger/ups/backups.html
(with appropriate modifications for FreeBSD).
If you can't get it to work, please get help from the nut-upsuser
mailing list (cc'd above), as I am no longer actively involved in NUT
development.
Hi Drew,
I no longer work on NUT, but the folks at the nut-upsuser mailing list
are extremely helpful. See
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
The 2.0.3 release is *way* out of date; the current stable NUT release
is 2.2.0. It contains many improvements, particularly to
Arjen de Korte wrote:
Justin Piszcz wrote:
Bus 003 Device 002: ID 050d:1100 Belkin Components
# /lib/nut/usbhid-ups -a belkin
Network UPS Tools: 0.28 USB communication driver 0.28 - core 0.30 (2.2.0-)
No matching HID UPS found
Hmm best to stick with 2.0.4.
No. Just run
Arjen de Korte wrote:
Bus 003 Device 002: ID 050d:1100 Belkin Components
# /lib/nut/usbhid-ups -a belkin
Network UPS Tools: 0.28 USB communication driver 0.28 - core 0.30
(2.2.0-)
No matching HID UPS found
Hmm best to stick with 2.0.4.
No. Just run the driver in
Alexander I. Gordeev wrote:
On Wed, May 23, 2007 at 01:18:26AM -0300, Peter Selinger wrote:
I'll defer to Alexander Gordeev; he has worked extensively on the
megatec_usb driver, which is solving a somewhat similar problem,
although the protocol is different.
The UPS shutdown 30
Alexander,
I think we are talking to two different Davids here. The previous
poster, David Mohr, was describing how some models of the Belkin -UNV
series will only work with the megatec(_usb) drivers. He just didn't
mention which models. This is starting to be confusing.
-- Peter
Alexander I.
Sorry guys, my message (and various replies) went off-list by mistake.
I am putting this back on the mailing list.
Eric S. Raymond wrote:
Peter Selinger [EMAIL PROTECTED]:
Alexander and Eric,
have you confirmed that the F6C1200-UNV works with the megatec_usb
driver? Looking back
Eric S. Raymond wrote:
Peter Selinger [EMAIL PROTECTED]:
One potential problem is that you are passing the parameters
vendorid=0665 and subdriver=agiler when you start the driver manually,
but you are passing no such parameters to upsdrvctl. You can put them
into your ups.conf
I am in favor of this. I have wanted this for some time, but was not
sure how best to do it.
We also have to have a way to suppress the revision-stamp mechanism in
an actual distribution. In other words, SVN builds should have a
version number such as 2.1.0-r910, whereas builds from released
David Mohr wrote:
Hi,
it'd be great if you could update the documentation on the website
that some models of the Belkin -UNV series will only work with the
megatec(_usb) drivers.
Which models, specifically? You mention the F6C1100-UNV in the subject
line, but we previously had reports that
[EMAIL PROTECTED] wrote:
I do have gdlib-config installed, and that made me ignore the config
option, because:
What is the output of the following on your system?
#gdlib-config --version --ldflags --includes
2.0.33
-L/usr/lib
-I/usr/include
It doesn't include support for libXpm.
Russ Romano wrote:
Can anyone give me insight into upsrw?
I have a cyberpower PR2200 UPS (running an experimental version of the
powerpanel driver hot off the presses by Arjen (thanks Arjen!!)).
When I try to run upsrw -s xyz=abc to set any available variable, I
get Set variable
Don't know. You could run the driver with -DD to see the raw data
reported by the UPS. -- Peter
Tom Laermans wrote:
'lo,
UPS model: APC Back-UPS BR 800 (supplied by Dell)
My USB connection:
Bus 001 Device 002: ID 051d:0002 American Power Conversion Back-UPS Pro
500/1000/1500
#
Arjan,
I am forwarding your email to the nut-upsuser mailing list. I am not
an expert on the Powermust driver; hopefully somebody on the mailing
list will be able to help you!
-- Peter
Arjan DJ wrote:
Dear Peter,
Some days ago I bought a Sweex UPS (500VA) and now I have set up NUT (using
Czuczy Gergely wrote:
On Sat, 21 Apr 2007 21:56:53 -0300 (ADT)
[EMAIL PROTECTED] (Peter Selinger) wrote:
In this case, I recommend that you do some testing and figure out
yourself what the problem is.
The debug output that you sent indicates that newhidups was unable to
find
Could it be a permissions problem? Perhaps the USB devices are not yet
owned by the correct user during boot? -- Peter
Jim Osborn wrote:
I can start the driver successfully manually, after the machine is up
and running, but at boot time, it can't find my UPS. My init script
makes sure that
A couple of suggestions.
First, please read the man page of newhidups, particularly the section
on how to configure multiple USB ups's. (IMPLEMENTATION). Newhidups
does not use /dev/usb/hiddev*, and the port values you have given
will be ignored in any case.
Second, please follow the
Udo van den Heuvel wrote:
Hello,
When my kernel oopses (not ups/nut related) nut is somewhat upset and
keeps complaining that power is gone, and restored, etc, etc, etc.
How can I fix this?
Please start by providing some information. What NUT version are you
using, what driver? What
How I love svn blame!
571 selinger-guest if ( test ${ac_cv_func_connect} = no ); then
2aquette AC_CHECK_LIB(nsl, printf, [
2aquette NETLIBS=-lnsl
2aquette ], [], [])
2aquette
2aquette AC_CHECK_LIB(socket, printf, [
A.Lizard wrote:
As I said earlier, I got it working using the -u root option.
I'm running on the Debian distribution.
Upon upsmon -c fsd , it shuts down the workstation, but NOT the UPS. In
order to shut down both, I first tried Peter Selinger's shutdown patch for
init.d halt :
That is great news! -- Peter
A.Lizard wrote:
At 12:41 PM 2/27/07, you wrote:
It now works - with minor issues.
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
A.Lizard wrote:
This is also expected, since it sounds like you still have the driver
running with -u root.
I haven't been able to get it to run any other way - newhidups outputs
(non-root and root) below.
Right. The fact that it works when both the driver and upsd are passed
-u root
Back to square one. Is there any other process running that might
already be attached to that device? -- Peter
A.Lizard wrote:
At 01:01 PM 2/23/07, you wrote:
I tried the procedure - no change.
terrarium:/usr/lib/hal# /lib/nut/newhidups -DDD -a belkin-ups
Network UPS Tools: 0.28 USB
This is perhaps a permissions problem.
You need to give newhidups the -u root option, or else it will drop
root privileges and probably not be able to open the device. Also,
the newhidups driver has no start argument.
Try this: kill all running drivers, and stop upsd and upsmon. Then:
Simpson, Kenneth wrote:
Hi - I have 5 Linux servers connected to 1 SmartUPS 2200 VA.
The software from APC for Linux requires a Windows machine be
present on the network as a server in order to manage the Linux
machines.
This is a show stopper for us since we don't have access to any
Hi Gary,
I am no good at reading kernel logs; these are Greek to me.
The normal sequence is that upsd, upsmon, and the driver are all
stopped. Then 'upsdrvctl shutdown' is called as a standalone program
at the very end to turn off the power. (Neither a daemon nor a monitor
are required at that
You are using upsd and upsdrvctl 2.0.4 together with tripplite_usb
2.0.5. These versions will not work together, since the socket format
has changed. Use everything from 2.0.5, and you should be fine
I hope.
-- Peter
Forest Bond - Logic Supply wrote:
On Fri, Feb 16, 2007 at 09:51:28PM
Herman J van der Merwe wrote:
Earlier, I wrote ..
3. What still remains a mystery to me is why no *.conf.sample files are
created in the /path/to/my/nutinstallation/etc directory.
OK, my fault ... trying to work at 1h00 is not the best time to find the
hidden make install-conf line !!
Upgrade to NUT 2.0.5?
-- Peter
Marc Collin wrote:
hi
my girldfriend have a belkin ups and get often this message
USBDEVFS_CONTROL failed cmd newhidups rqt 161 rq 1 len 8 ret -71
ups.conf
[myups]
driver = newhidups
port = /dev/hiddev0
desc = Local UPS
)
echo Error: argument '$1' not supported 2
exit 3
;;
stop)
do_stop
;;
*)
echo Usage: $0 start|stop 2
exit 3
;;
esac
:
[EMAIL PROTECTED]:~$
Peter Selinger wrote:
I am not sure why you created a file S89ups-shutdown. You
Vladimir,
as Charles already pointed out, you can do what you want by writing a
few lines of shell script and arranging for the script to be called
when the UPS goes on battery.
# shut down when battery charge goes below $minlevel
minlevel=30
# check every $interval seconds
interval=5
while
Charles Lepple wrote:
On 1/30/07, Gregory Orange [EMAIL PROTECTED] wrote:
I've browsed the archives back for a few months and nothing has jumped
out at me as being helpful, but since there doesn't seem to be a search
facility it's certainly possible I've missed what I'm looking for.
Hi Arjen,
yes, you are right. The calls to dstate_dataok() in
usbhid_ups.c:hid_ups_walk() are somewhat random. I am worried about
this:
if ( (retcode == -EPERM) || (retcode == -EPIPE)
|| (retcode == -ENODEV) || (retcode == -EACCES)
|| (retcode == -EIO) ||
If you are using newhidups/usbhid-ups, the option -x pollfreq=value
can be used to set the polling frequency (or put pollfreq=value
into ups.conf). The default is 30 seconds.
-- Peter
Justin Piszcz wrote:
When I disconnect my UPS from the wall, I have to wait 15-30 seconds
before the USB
If I understood Markus correctly, the problem is not that the data
goes stale (it should do that when disconnecting the UPS
communications line), but that it goes unstale immediately afterwards
(even when the UPS is still disconnected).
This shouldn't really happen. Maybe some debugging is
Yes, but he said 2.0.5 in the subject line. -- Peter
Arjen de Korte wrote:
Peter Selinger wrote:
If I understood Markus correctly, the problem is not that the data
goes stale (it should do that when disconnecting the UPS
communications line), but that it goes unstale immediately
Collection, data=none
Item(Main ): End Collection, data=none
@@@
At 15:06 26/01/2007, Peter Selinger wrote:
Jon,
there were some threads in December on the nut-upsdev list, with
subjects such as megatec over USB. Andrey Lelikov had written a
patch for a SVEN
something in the
system that expects these values?
Regards
Jon
At 17:20 28/01/2007, Peter Selinger wrote:
Hi Jon,
I can't figure out which version of NUT you are running, because you
have pruned that information from your output. Also, which patches, if
any, have you applied?
What you
Hi Gary,
yes, this looks good. Your device is apparently identical, or very
similar, to the Cyber Power AE550, which is supported by newhidups.
You should be able to run the driver without the -DD and follow the
rest of the installation instructions.
-- Peter
Gary Redden wrote:
This took a
the
project with special options to bulid USB drivers and have usbtools
installed already on my system, is this correct?
Dominik Goraczkowski
P.S. I've tried to set all options to sent this message encoded
correctly this time.
Peter Selinger napisa?(a):
Hi Dominik,
no, I don't
From the file INSTALL, step 1:
1. Configure the source tree for your system. Add the --with-user
switch to set the user name that you created above.
./configure --with-user=nut
If you need any other switches for configure, add them here. For
example:
* to build and
.
./configure --with-user=nut
If you alter paths with additional switches, be sure to use those
new paths while reading the rest of the steps.
*** Reference: docs/configure.txt
---
Peter Selinger
Hi Dominik,
no, I don't think I have seen this device before. What is its
USB manufacturer and product ID (lsusb or usbview should show this, as
does the newhidups driver).
If it is a HID device, then it should not be very difficult to support
it in NUT, if it isn't already compatible.
Try
If you run newhidups with -u root, then you have to run upsd -u
root as well.
If you run newhidups without -u root, then it runs as the user
specified by the ./configure --with-user option, or by the ups.conf
user option (i.e. upsd in your case).
It looks like
crw-r--r-- 1 upsd root 189, 520
Dear Gary,
NUT 2.0.3 is an ancient version. CPS support was added to newhidups
much later.
-- Peter
P.S. please keep list traffic on the mailing list. Thanks!
Gary Redden wrote:
You wrote the following on the NUT-upsuser mailing list
To check if your device's USB interface is supported,
Doug Reynolds wrote:
Peter Selinger wrote:
I wanted to mention that some of Cyberpower UPS use a USB to Serial
bridge; I am not sure that the GS upses implement this method or not.
If it has a serial port, try using the new 'powerpanel' driver (which I
believe is in the new 2.0.5-pre2
Michelle Dupuis wrote:
I changed the line to:
NOTIFYCMD logger 'upsmon: test running notify command'
I wouldn't assume that NUT's configuration file parser interprets
these quotes and spaces correctly. Have you checked that it is not
calling
logger ('upsmon:) (test) (running) (notify)
There is a FAQ entry on this. But the FAQ is so hard to find (and
lacks a table of contents or an index), so probably nobody ever looks
at it. I know I don't.
Does anyone feel like grouping the FAQ into easy-to-lookup categories?
-- Peter
[EMAIL PROTECTED] wrote:
Have you looked at
Hi Richard,
This is bizarre. Using -DD, you should get more output between debug
level is '2' and No appropriate HID device found. You should at
least get something like:
debug level is '2'
Checking device (/) (005/001)
- VendorID:
- ProductID:
- Manufacturer: Linux
This question has a clear answer: no. There is no such Make/Config
option.
However, why not just do the following?
./configure [options]
cd clients
make upsmon upsc
You can't use make install with this method. But if you have to, you
could install these two binaries by hand:
cp upsmon
Paul Cooley wrote:
Hello NUT-UPSUSERS,
I would just like to try and help other and indicate that I was able to use
the development trunk and get the Tripp Lite OMNI1000LCD UPS (USB) working
with the newhidups drivers on Gentoo Linux. The one that is currently
available at many local
Please upgrade to NUT 2.0.5-pre2. APC support was much improved since
2.0.4.
Also, try these instructions:
http://www.mathstat.dal.ca/~selinger/ups/backups.html
If it still doesn't work, please write to the list again with more
specific information.
-- Peter
Ernest Aigner wrote:
Hello,
Daniel Gimpelevich wrote:
On Sat, 30 Dec 2006 15:15:45 -0400, Peter Selinger wrote:
Hi Daniel,
we have seen device 0d9f/0001 before (possibly under a different name,
but this is common), and as far as I remember we could not get it to
work. See the thread named Gentoo Ultra USB UPS
Arjen de Korte wrote:
Miwa Forever wrote:
As for changing MAXAGE directive - with values 60 and greater ups become
available from pc, at least i can see it's state with upsc. But in
/var/log/messages we can see next:
Dec 29 17:13:37 zork3 upsd[14370]: UPS [MGE-Ellipse] data is no
Miwa Forever wrote:
2006/12/28, Peter Selinger [EMAIL PROTECTED]:
Miwa Forever wrote:
Hello.
So as my english is not so good, i'll try to write my story in bash
commands
:o)
[EMAIL PROTECTED] uname -mrs
FreeBSD 5.5-STABLE i386
[EMAIL PROTECTED] su
[EMAIL
Hi Marc,
the answer to your question is contained in the file INSTALL,
distributed with NUT, section 6 Set ownership data and permissions on
your serial or USB ports that go to your UPS hardware.
Quote:
The setup for USB ports is slightly more complicated. Device
files for USB devices,
Did you set correct permissions on /dev/tts/0? If that device is owned
by root, then your driver cannot write to or read from it. -- Peter
Vitaly Oborsky wrote:
Good afternoon. I try to put nut on gentoo. Has executed installation
by a standard command emerge nut. All has passed successfully.
HID v1.11 Device [Belkin Belkin UPS] on usb1:2.0
- jamie
On Dec 8, 2006, at 4:22 PM, Peter Selinger wrote:
Jamie Fiedler wrote:
is there a way to override the productid (like -x productid=3D1234)
when using newhidups?
Hi Jamie, I like simple yes/no questions! The answer is yes
CyberPower support was added to newhidups after release 2.0.3 (a very
old release). You should use NUT 2.0.4, or even better: the newest
development snapshot from SVN (http://www.networkupstools.org/source.html)
-- Peter
henri wrote:
i can't seem to get newhidups to detect my UPS..
i'm
Hi Marek,
you should use newhidups, not hidups. -- Peter
Marek Szuba wrote:
Hello,
I have encountered problems trying to set up nut to work with APC BackUps Pro
CS connected over USB to an AMD64 machine running Debian. While apcupsd works
fine with that device, whenever I start upsd I
Hi Tim,
if you are using NUT 2.0.4, then you should look at the instructions
in the file INSTALL. Step 2 is the following:
2. Build the programs.
make
Optionaly, you can also build the USB drivers (requires libusb) using:
make usb
The same goes for the SNMP driver
Arjen de Korte wrote:
I guess the problem is that Synchronizing... step.
Indeed. Either the driver needs more time to dump all the data than is
allowed for in upsd or it could also be that the first connection to the
driver always fails. Since we first declare a driver stale before
Eric Masson wrote:
Arjen de Korte a =E9crit :
Hello Arjen,
This is a different problem, your driver is not answering at all and it
looks like the dumpall command is not processed. Upgrading to the lates=
t
development version would be a good idea now, since a few things have
Your problem may be related to the way upsd and upsdrvctl interact.
There are several ways to start the driver:
(1) newhidups [options] auto
(2) newhidups [options] -a myprofile
(3) upsdrvctl start myprofile
where myprofile is the name of a profile defined in ups.conf.
Except for testing
upsd installed from an older version).
-- Peter
Eric Masson wrote:
Peter Selinger a =E9crit :
Hello Peter,
Your problem may be related to the way upsd and upsdrvctl interact.
There are several ways to start the driver:
=20
(1) newhidups [options] auto
(2) newhidups [options
Hi Bryan,
thanks for your report. I am not sure what issue you are referring to.
All the output you posted appears to be normal. Did the driver give
you any particular problems? -- Peter
Bryan Bond wrote:
I am having an issue running NUT and using an TrippLite OMNI900LCD.
When I run
=?ISO-8859-1?Q?Pedro_C=F4rte-Real?= wrote:
/etc/nut/upsd.conf is world readable
/etc/nut/upsd.users is world readable
That is probably a really bad idea, since /usr/etc/upsd.users contains
passwords that would allow any user to shut down your machine.
-- Peter
To answer that question, we would have to see the script. This is not
the Ubuntu/Debian mailing list, so what's standard to them may not be
standard to us. -- Peter
=?ISO-8859-1?Q?Pedro_C=F4rte-Real?= wrote:
On 11/13/06, Peter Selinger [EMAIL PROTECTED] wrote:
I can only guess. Perhaps you
for communication. In other words, it is intended to be
started as:
upsd
and not
upsd
If upsd is started in the latter way, then upsmon could be started too
soon. -- Peter
=?ISO-8859-1?Q?Pedro_C=F4rte-Real?= wrote:
On 11/13/06, Peter Selinger [EMAIL PROTECTED] wrote:
To answer that question
I can only guess. Perhaps you are starting the components in the wrong
order? You have to start:
First the driver (upsdrvctl).
Second upsd.
Third upsmon.
-- Peter
=?ISO-8859-1?Q?Pedro_C=F4rte-Real?= wrote:
On 11/12/06, Peter Selinger [EMAIL PROTECTED] wrote:
Try an analogous setting
Yes, this has been fixed some time ago in the SVN version. -- Peter
Magnus Johansson wrote:
Hi!
I'm running NUT 2.0.4 and occasionally I get a segfault when starting
newhidups and if I don't get a segfault when starting newhidups the
process starts eating away at my memory. I sat down
Philipp
-Urspr=FCngliche Nachricht-
Von: nut-upsuser-bounces+philipp.leusmann=3Drwth-
[EMAIL PROTECTED] [mailto:nut-upsuser-
[EMAIL PROTECTED] Im
Auftrag von Peter Selinger
Gesendet: Donnerstag, 2. November 2006 03:54
An: Carlos Rodrigues
Cc: [EMAIL PROTECTED]; nut-
[EMAIL
Hi Carlos,
as far as I know, there is a standard serial over USB interface. I
think the USB specification discourages such interfaces.
All the serial over USB devices that I have seen have used a
manufacturer-specific hack. So connecting to a USB device should not
usually be as simple as
don't know about. I am not very hopeful about
being able to guess it. -- Peter
-Urspr=FCngliche Nachricht-
Von: Peter Selinger [mailto:[EMAIL PROTECTED]
Gesendet: Donnerstag, 19. Oktober 2006 19:18
An: Philipp Leusmann
Cc: Nut-upsuser@lists.alioth.debian.org
Betreff: Re: AW: [Nut
Dear Gabriel,
we would need some information to be able to help you, for example:
* NUT version
* operating system type and version
* what driver were you using
* what did you do
* what error messages did you get?
-- Peter
Gabriel =?iso-8859-1?q?Fern=E1ndez?= wrote:
I have not been able to
You should first get a current version of NUT. Get release 2.0.4 or
later, and preferably the Development version (see
http://www.networkupstools.org/source.html - Develoment Tree).
The driver to use is newhidups. -- Peter
Philipp Leusmann wrote:
Hi,
is there a way to use my Belkin F6H650
: Peter Selinger [mailto:[EMAIL PROTECTED]
Gesendet: Donnerstag, 19. Oktober 2006 14:52
An: Philipp Leusmann
Cc: nut-upsuser@lists.alioth.debian.org
Betreff: Re: [Nut-upsuser] Belkin F6H650 on USB port
You should first get a current version of NUT. Get release 2.0.4 or
later
Strange. Is the problem reproducible? I have never seen it before.
You might try the Development version of NUT from SVN (see
http://www.networkupstools.org/source.html under Development tree).
There has been quite a lot of work on the newhidups driver since
2.0.4.
-- Peter
Jan Zuchhold
=?iso-8859-1?Q?Fr=E9d=E9ric_POTTER?= wrote:
Thanks jimmy for the hints, but I'm afraid the description of the
problem I have was not clear.
The problem I have is NOT a software configuration issue of NUT.
The problem I have is that the UPS, when reaching battey.charge.low
SHUTS DOWN
at least one of
the values would dropped to a negative value. What should I do next? Thanks.
On Sat, 23 Sep 2006 16:06:37 -0300 (ADT)
[EMAIL PROTECTED] (Peter Selinger) wrote:
The patch I just sent may not work; please try this one instead.
-- Peter
That device is not currently supported (we have never seen it before).
It looks like a HID device, so it should be possible to write a
subdriver for it, see docs/hid-subdrivers.txt.
However, the data returned by the device looks strange; all the values
are 0. I am not sure if this will work
Michael Helmling wrote:
Excellent, it works with megatec and /dev/ttyS0. Thank you very
much! Someone could add that to the hardware database.
Please let me know if I can provide you with any information that
might help to get the USB interface working, too.
To get the USB interface
Denis Hainsworth wrote:
holy crap. just rpm'd the hotplug stuff for fc3. added an appropriate
line to usb.usermap and a script that changes permissions and group
and it just worked.
Excellent. I have added your device F6C550-AVR (050d/0551) to our
standard hotplug scripts in SVN as well.
Denis Hainsworth wrote:
usb 1-1: usbfs: process 32652 (newhidups) did not claim interface 0
before use
so I found two places where supposedly you guys have added code to
address the above issue I am having.
Maybe you can tell us what two places you are talking about? -- Peter
As far
Denis Hainsworth wrote:
On Sun, Sep 17, 2006 at 11:54:32AM -0300, Peter Selinger wrote:
Denis Hainsworth wrote:
usb 1-1: usbfs: process 32652 (newhidups) did not claim interface 0
before use
so I found two places where supposedly you guys have added code to
address
After what's been said here, and the data that Rob sent, it seems that
the UPSs are faulty; I cannot think of any reason why they should yank
the power after 5 minutes, without any warning sign, and with brand
new batteries. Even stranger that it still does this when the power is
interrupted only
Hi Magnus,
I didn't understand your compiler's error message (they were not in
English).
However, it seems that you need to install libusb, version 0.1.8 or
later, before compiling nut. I wrote some instructions for setting up
NUT with the APC Back-UPS at:
Rob wrote:
I would try the following: plug your computer into a wall outlet, plug
a desk lamp into the UPS. First, start the driver and upsd (but not
upsmon). Monitor the ups variables with upsc. Pull the power, wait 5
minutes or more, see what happens. Are there changes to ups.status?
Rob wrote:
While plugged into the wall:
battery.charge: 100.0
battery.runtime: 64:41
driver.name: cpsups
driver.parameter.port: /dev/ttyS2
driver.version: 2.0.4
driver.version.internal: .04
input.frequency: 60
input.voltage: 122
output.voltage: 122
ups.load: 9
ups.mfr:
Charles Lepple wrote:
On 9/8/06, Hans Fugal [EMAIL PROTECTED] wrote:
I have a Tripp Lite OMNI900LCD.
...
I can't get newhidups to recognize it at all.
Support for newer Tripp-Lite USB/HID models is still in the
development tree (the trunk in SVN). Instructions for grabbing it via
OK, in any case, once Hans gets the development version of NUT, he can
then produce enough debugging output so that we can hopefully support
the model. -- Peter
Marc Collin wrote:
Le vendredi 8 septembre 2006 15:35, Peter Selinger a =E9crit=A0:
Charles Lepple wrote:
On 9/8/06, Hans Fugal
on the NUT site, but maybe not the
correct ones?
Rob
Peter Selinger wrote:
Rob wrote:
What would I be looking for that I didn't see in my testing with my
windows box? Should I be trying to sniff the serial connection to see
if the UPS is for some reason sending a weird signal
Arnaud Quette wrote:
Hi
2006/8/27, Peter Selinger [EMAIL PROTECTED]:
...
What's to do here for the NUT developers is: first, improve support
for interrupt transfers in newhidups.
right, as we still rely on the (very) early code I first wrote.
moreover, the big nested if in update
Arnaud Quette wrote:
2006/8/30, Peter Selinger [EMAIL PROTECTED]:
Arnaud Quette wrote:
Hi
2006/8/27, Peter Selinger [EMAIL PROTECTED]:
...
What's to do here for the NUT developers is: first, improve support
for interrupt transfers in newhidups.
right, as we still
Paolo Pedroni wrote:
Anyway, I have found something in the debug output that does not seem norma=
l,
and maybe you may want to check it. The relevant output
(/lib/nut/newhidups -DD -a SmartUps1500) is as follows:
(snip)
Waiting for notifications...
upsdrv_updateinfo...
Waiting for
. This
would yank the power from your UPS. In the above setup, you would see
the lamp go off as the computer is preparing to shut down.
-- Peter
Peter Selinger wrote:
That is very odd indeed. Why should the system shut off abruptly? If
the log shows nothing, then it seems that the UPS just
That is very odd indeed. Why should the system shut off abruptly? If
the log shows nothing, then it seems that the UPS just turned off the
power.
I recommend testing this while attaching, say, a lamp to the UPS,
instead of a computer. (You can still use your computer to monitor the
UPS, just
Marc Collin wrote:
linux64:/home/collinm/Download/trunk # /usr/local/ups/bin/upsc [EMAIL
PROTECTED]
driver.name: newhidups
driver.parameter.port: /dev/hiddev0
driver.version: 2.1.0
driver.version.data: PowerCom HID 0.1
driver.version.internal: 0.30
powercom.coll2.feature3: 1
1 - 100 of 150 matches
Mail list logo
