[Nut-upsdev] anybody familiar with these init(?) sequences?
Carlos Rodrigues
carlos.efr at mail.telepac.pt
Tue Mar 4 09:45:22 UTC 2008
On Mon, Mar 3, 2008 at 11:03 PM, AE sysadmin <ae.tech.i at gmail.com> wrote:
> Thank you for the previous help. Here is the rather useless feedback.
>
[snip]
>
> # megatec -a test -DDDDD
>
> [root at localhost ~]# megatec -a test -DDDDD
> Network UPS Tools 2.2.0- - Megatec protocol driver 1.5.4 [megatec]
> Carlos Rodrigues (c) 2003-2007
>
> debug level is '5'
> Starting UPS detection process...
> Attempting to detect the UPS...
> Sending "Q1" command...
> "Q1" command successful.
> Attempting to detect the UPS...
> Sending "Q1" command...
> "Q1" command successful.
> Attempting to detect the UPS...
> Sending "Q1" command...
> "Q1" command successful.
> Attempting to detect the UPS...
> Sending "Q1" command...
> "Q1" command successful.
> Attempting to detect the UPS...
> Sending "Q1" command...
> "Q1" command successful.
> 0 out of 5 detection attempts failed (minimum failures: 2).
> Asking for UPS information ("I" command)...
> UPS doesn't return any information about itself.
> Megatec protocol UPS detected.
> Asking for UPS power ratings ("F" command)...
> UPS doesn't return any information about its power ratings.
> Cannot calculate charge percentage for this UPS.
> Done setting up the UPS.
> Asking for UPS status ("Q1" command)...
> UPS doesn't return any information about its status.
> dstate_init: sock /var/run/nut/megatec-test open on fd 5
> Asking for UPS status ("Q1" command)...
> UPS doesn't return any information about its status.
[snip]
Hmmm, the UPS seems to be detected but then it goes away. Can you try
the latest development version (trunk) to see if that works?
--
Carlos Rodrigues
More information about the Nut-upsdev
mailing list