[Nut-upsdev] Mustek PowerMust 1000AV USB feedbacks

[Arjen de Korte]

> It looks like the nut-upsuser list is momentarily down. That's why I
> send it to nut-upsdev list too.

As far as I know, it isn't down, but the traffic is low. This may be due
in part to the way how the listserver deals with new messages. It looks to
me that some sending systems may not be compatible with this, since I
sometimes receive messages from people directly that were also sent to the
mailinglist, but never show up there.

[...]

> 1. Monitoring with the serial interface
>
> The output gives me,
>
> # upsc mustekups
> battery.charge: 100.0
> battery.voltage: 27.60
> battery.voltage.nominal: 24.0
> driver.name: megatec
> driver.parameter.pollinterval: 2
> driver.parameter.port: /dev/ttyS0
> driver.version: 2.2.0-exporté
> driver.version.internal: 1.5.4
> input.frequency: 50.1
> input.voltage: 230.5
> input.voltage.fault: 230.5
> input.voltage.maximum: 232.5
> input.voltage.minimum: 217.1
> output.voltage: 224.0
> output.voltage.nominal: 220.0
> ups.beeper.status: enabled
> ups.delay.shutdown: 0
> ups.delay.start: 2
> ups.load: 14.0
> ups.mfr: unknown
> ups.model: unknown
> ups.serial: unknown
> ups.status: OL
> ups.temperature: 25.0
>
> Q: Are this the only variables that the device is able to return or is
> upcs just missing some of them ?

Those are all that are supported by your UPS. The megatec protocol (see
http://www.sovico.org/pcm.txt for an example) doesn't provide more
information.

> For instance, I did not see the 'battery.charge.low' or
> 'battery.runtime' (very useful) like with the MGE device i have.

MGE uses a completely different protocol.

> Also, i noticed that the ups.temperature never changed (25°C looks very
> low for me especially in summer :)

This value may be entirely bogus, maybe your UPS doesn't have an internal
temperature sensor (or it is broken). From the debug data, this is the
actual value read from the UPS, so there is nothing we can do about that.

[...]

> In battery mode, (i cannot say if it is alright when the power fell so
> fast and stabilized at 60% and also recover fast too when the power is
> back, the load average is only 16% :( )

The battery charge is calculated by the megatec driver based on the
battery voltage, it's not a value from the UPS. This is not a very
accurate way of determining the battery charge and will result in a highly
non-linear transfer function. Don't count on it to be accurate, it isn't.
If realistic values for battery charge and runtime are important to you,
you're better of with a more sophisticated UPS.

[...]

> # upsc mustekups-usb
> battery.charge: 100.0
> battery.voltage: 27.50
> battery.voltage.nominal: 24.0
> driver.name: megatec_usb
> driver.parameter.pollinterval: 2
> driver.parameter.port: auto
> driver.parameter.productid: 5161
> driver.parameter.subdriver: agiler
> driver.parameter.vendorid: 0665
> driver.version: 2.2.0-exporté
> driver.version.internal: 1.5.4
> input.frequency: 50.0
> input.voltage: 226.7
> input.voltage.fault: 226.7
> input.voltage.maximum: 229.6
> input.voltage.minimum: 226.7
> output.voltage: 221.5
> output.voltage.nominal: 220.0
> ups.beeper.status: enabled
> ups.delay.shutdown: 0
> ups.delay.start: 2
> ups.load: 14.0
> ups.mfr: unknown
> ups.model: unknown
> ups.serial: unknown
> ups.status: OL
> ups.temperature: 25.0

The UPS still uses the same megatec protocol, but now a serial-to-USB
converter is used to connect to the computer. No surprise that you're
seeing the same data.

With regards to the shutdown problems, try if this works through the
serial interface. The megatec_usb driver is very new, so this may indeed
be a bug. It could also be that your UPS simply doesn't respond to this
command. The best way to verify this, is by trying the same through the
serial interface and post the results here.

Best regards, Arjen
-- 
Eindhoven - The Netherlands
Key fingerprint - 66 4E 03 2C 9D B5 CB 9B  7A FE 7E C1 EE 88 BC 57