[Nut-upsuser] Mustek Powermust 600VA

[Arjen de Korte]

> After following your advice, I got this:

Please state exactly how you started this driver (startup command line and
contents of 'ups.conf' so that people that find this thread, can easily
duplicate what you did.

> Serial-over-USB transport layer for Megatec protocol driver
> [megatec_usb]
>
> debug level is '3'
> Checking device (06DA/0003) (002/002)
> - VendorID: 06da
> - ProductID: 0003
> - Manufacturer: unknown
> - Product: USB UPS
> - Serial Number: unknown
> - Bus: 002
> Trying to match device
> Device matches
> failed to claim USB device, trying 2 more time(s)...
> detaching kernel driver from USB device...
> trying again to claim USB device...
> Starting UPS detection process...

Good. It looks like starting the driver as root at least temporarily fixes
the permissions problems.

> Attempting to detect the UPS...
> Sending "Q1" command...
> "Q1" command successful.
> Attempting to detect the UPS...
> Sending "Q1" command...
> Wrong answer to "Q1" command.
> Attempting to detect the UPS...
> Sending "Q1" command...
> "Q1" command successful.
> Attempting to detect the UPS...
> Sending "Q1" command...
> Wrong answer to "Q1" command.
> Attempting to detect the UPS...
> Sending "Q1" command...
> "Q1" command successful.
> 2 out of 5 detection attempts failed (minimum failures: 2).

That's more or less normal for this protocol. Some devices simply don't
answer for every request.

> Asking for UPS information ("I" command)...
> UPS doesn't return any information about itself.

Fine too.

> Megatec protocol UPS detected.
> Asking for UPS power ratings ("F" command)...
> UPS power ratings: #220.0 002 12.00 50.0

Looks promising. At least we have an indication that we communicate with
the UPS with one of the subdrivers.

> Asking for UPS status ("Q1" command)...
> UPS doesn't return any information about its status.
> Error reading status from UPS!

That is not good. :-(

As you've seen above, some UPS'es will have a lot of communication
failures. Unfortunately, the 'megatec' driver requires the UPS to answer
at the first try when starting up. If it fails to do so, it won't try any
of the above commands (with the exception of the Q1 command). It looks
like your UPS fails to every other attempt for the Q1 command, so it will
fail when we need it. This is something we need to fix in the Megatec
driver.

> Looks like the F command was accepted by the UPS. Is there anything
> else I can do to get full support for my device?

Please upgrade to the development version. This provides better debugging
facilities than the latest stable one.

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