Nut upsuser - Dec 2010 - nut 2.4 et MGE CometEXtrem 6

Hello

 

My server with another UPS (MGE Pulsar Evolution2200 USB) is OK.

All scripts work

Is it possible to work with a UPS MGE CometExtrem 6 on serial port

 

Which driver can I use ?

I tried with mge-shut ou mge-utalk without any success


when I start driver with upsdrvctl with mge-utalk

I have (after a long time)

Can't connect to UPS [MGE_cometEX] (mge-utalk-MGE_cometEX): No such file or
directory

or

 

Network UPS Tools - UPS driver controller 2.4.3
Network UPS Tools - MGE UPS SYSTEMS/U-Talk driver 0.89 (2.4.3)
/dev/ttyS0 is locked by another process
Driver failed to start (exit status=1)
 

Thanks for your help

 

 

 
-- 

Sabine GOUDARD - Informatique et Multim?dia

Ecole Nationale Sup?rieure d?Architecture de Saint-?tienne

1, rue Buisson BP 94 42003 Saint-?tienne Cedex 1

T?l. : 04 77 42 37 20 - Fax : 04 77 42 35 40

sabine.goudard at st-etienne.archi.fr

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20101207/e810ea38/attachment.htm>

Hello

2010/12/7 sabine GOUDARD <sabine.goudard at st-etienne.archi.fr>
>  Hello
>
>
>
> My server with another UPS (MGE Pulsar Evolution2200 USB) is OK.
>
> All scripts work
>
> Is it possible to work with a UPS MGE CometExtrem 6 on serial port
>
>
> Which driver can I use ?
>
> I tried with mge-shut ou mge-utalk without any success
>
as per NUT HCL, Comet Extreme use the UTalk protocol.
so mge-utalk is the driver you're looking for.

> when I start driver with upsdrvctl with mge-utalk
>
> I have (after a long time)
>
> Can't connect to UPS [MGE_cometEX] (mge-utalk-MGE_cometEX): No such
file or
> directory
>
> or
>
>
>
> Network UPS Tools - UPS driver controller 2.4.3
> Network UPS Tools - MGE UPS SYSTEMS/U-Talk driver 0.89 (2.4.3)
> /dev/ttyS0 is locked by another process
> Driver failed to start (exit status=1)
>
the above message shows that the mge-utalk driver can't start since there is
another driver locking the port.
so, first, stop everything, and issue a "killall mge-shut mge-utalk"
then start NUT as usual.
if something really goes wrong, stop everything and then try starting
mge-utalk in debug mode, to see if there is actually a problem, using:
$ /path/to/mge-utalk -DDD -a MGE_cometEX

Let it run for 30 seconds, and send us the output.

brg,
Arnaud
-- 
Linux / Unix Expert R&D - Eaton - http://powerquality.eaton.com
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://www.debian.org
Free Software Developer - http://arnaud.quette.free.fr/
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20101208/1f86de44/attachment.htm>