I have a Gamatronic Smart Compact 750.
I have it connected to my linux machine via serial cable and am running nut
2.0.3. There is no interruption in power, but the ups is reporting OB (on
battery). Is there a configuration option I am missing?
The relevant ups.conf entry is:
[Gamatronic]
port = /dev/ttyS1
desc = "Home Gamatronic UPS"
driver = genericups
upstype = 22
Does anyone know why, or how to check why, it is showing OB, when it should
be showing OL?
Thanx.
Shlomo
--
-----------------------------------------------------------------------
,-~~-.___. ._.
/ | ' \ | |"""""""""|
Shlomo Dubrowin
( ) 0 | | | (Sheldon)
\_/-, ,----' | | |
==== !_!--v---v--"
/ \-'~; |""""""""|
shlomo@dubrowin.org
/ __/~| ._-""|| | http://www.dubrowin.org
=( _____|_|____||________|
-----------------------------------------------------------------------
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20060501/31239374/attachment.htm
On 5/1/06, Shlomo Dubrowin <shlomo@dubrowin.org> wrote:> Does anyone know why, or how to check why, it is showing OB, when it should > be showing OL?I am not familiar with the various genericups types, but you can use statserial to show the status of the various serial port lines. -- - Charles Lepple
On 5/1/06, Shlomo Dubrowin <shlomo@dubrowin.org> wrote:> I am using the serial cable that was supplied with the UPS. But based on > what I'm seeing in statserial, are you suggeting that perhaps, some of the > pin-outs are wrong? Would that indicate the wrong status?It is definitely possible that the cable is meant for a different operating mode. You may want to check the list archive for updates on Gamatronic support - I do not know much about that particular manufacturer. You can also check the CREDITS or drivers.list files in the NUT distribution to see what else is supported. http://boxster.ghz.cc/projects/nut has the latest source code, in case you haven't checked the development branch yet (in trunk/). -- - Charles Lepple
Charles Lepple wrote:> On 5/1/06, Shlomo Dubrowin <shlomo@dubrowin.org> wrote: >> Does anyone know why, or how to check why, it is showing OB, when it >> should be showing OL? > > I am not familiar with the various genericups types, but you can use > statserial to show the status of the various serial port lines.Hi Charles - what does it suggest if statserial shows no change when the UPS switches to battery? Serial plugged in.... statserial /dev/ttyS0 -d 16742 Unplugged returns 16390 Which shows I have the right serial port because unplugging the serial cable shows changes. -- Criggie
Criggie wrote:> > > Charles Lepple wrote: > > On 5/1/06, Shlomo Dubrowin <shlomo@dubrowin.org> wrote: > >> Does anyone know why, or how to check why, it is showing OB, when it > >> should be showing OL? > > > > I am not familiar with the various genericups types, but you can use > > statserial to show the status of the various serial port lines. > > > Hi Charles - what does it suggest if statserial shows no change when the > UPS switches to battery? > > Serial plugged in.... statserial /dev/ttyS0 -d > 16742 > > Unplugged returns 16390 Which shows I have the right serial port because > unplugging the serial cable shows changes.This could mean several things. * perhaps your UPS does not report "on battery". Does it report "low battery"? The latter is all that is technically needed to shut down the computer. * perhaps your UPS or cable is broken, or partially broken * perhaps your UPS is not contact-closure. Maybe it expects proper serial port communications, instead of setting individual pins? In this case, you should use one of the serial drivers. -- Peter
On 5/1/06, Criggie <criggie@criggie.dyndns.org> wrote:> Serial plugged in.... statserial /dev/ttyS0 -d > 16742If you figure out that it is indeed a contact-closure UPS, and you have a working contact-closure cable, then running statserial without "-d" will show you the appropriate signal names needed to construct a custom genericups configuration. -- - Charles Lepple