[Nut-upsdev] Mustek PowerMust 848

[Marian Ciobanu]

>> information is provided by the UPS or if it is calculated based on
>> battery voltage. What do you think?

> I think you need to read 'man 8 blazer'.

Arjen, I did look at blazer's man before my first post, but my question
was not really answered there. Since this UPS got supported so recently,
and no Mustek appears in the man page, it seems possible to me that MAYBE
it would report the charge status, if asked nicely. Perhaps there's some
code that can be added to do this, some new commands. I wanted to look at
this, but before wasting my time getting familiar with the code only to
find out that reading the charge was not possible, I wanted to check if
you are quite confident that all the information that can be sent by
the UPS is actually passed on by uspc, and the only way to get some
idea about charge status is to look at the voltage. (As for setting
battery.voltage.high and battery.voltage.low to have the driver guess the
charge - I got that. I just wonder if the claim that "no UPSs compatible
with the blazer driver can ever possibly report charge or currents" is
really true. From your answer, it seems true; but I had to check.)


>> the variables that are displayed, upsd keeps my CPU 100% busy for 1

> I don't know. I can't see *what* it is doing at that time. You might
> want to run 'upsd' with debugging enabled to see if this reveals more
> information.

Well, I started upsd in debug mode and here's what I saw: when KNutClient
is not running the output is mostly "mainloop: polling 2 filedescriptors"
and "mainloop: no data available", with some Ping/Pong messages. When
KNutClient is running, there are "mainloop: polling 3 filedescriptors",
"mainloop: no data available" and Ping/Pong messages, and then
"write: [destfd=6] [len=35] [VAR mustek battery.voltage "13.70"]" and
similar messages. Once KNutClient is stopped, millions of
"mainloop: polling 3 filedescriptors" are generated and after a minute
there's a "Disconnect from 127.0.0.1", followed by messages like the ones
before starting KNutClient ("mainloop: polling 2 filedescriptors" +
"mainloop: no data available" + some Ping/Pong messages.)

It looks like KNutClient forgot to disconnect. Or maybe I messed up
something.

Thanks,
  Ciobi