Hello,
It looks like the nut-upsuser list is momentarily down. That's why I
send it to nut-upsdev list too.
I have recently bought a mustek Powermust 1000VA USB (sadly not the USB
P version). I have done some tests with the latest nut 2.2.0 megatec and
megatec_usb drivers. Here are my feedbacks.
It works quite well but is extremely noisy in battery mode (and that
is not the noise of the beeper for sure, it is more like a big voltage
transformer -
we don't really need the beeper ;). It is shipped with a java WinPower
monitoring tool for linux. I did not try it yet (i'm not really fan with
bundled tools). The ups has two 12V 7ah battery packs. It is a
line-interactive. The fan is regulated (+40db) and does not stop even if
the ups is powered off. To stop it, unplug the wall socket ;)
I proceed 3 tests,
- with the serial interface and the megatec driver
- with the usb interface and the megatec_usb driver
- a forced shutdown with upsmon
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 ?
For instance, I did not see the 'battery.charge.low' or
'battery.runtime' (very useful) like with the MGE device i have. Also, i
noticed that the ups.temperature never changed (25?C looks very low for
me especially in summer :)
In debug mode i get,
# /lib/nut/megatec -a mustekups -DDD
Network UPS Tools 2.2.0-export? - Megatec protocol driver 1.5.4 [megatec]
Carlos Rodrigues (c) 2003-2007
debug level is '3'
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 power ratings: #220.0 004 24.00 50.0
Asking for UPS status ("Q1" command)...
UPS status: (224.3 225.2 219.7 014 50.0 27.6 25.0 00001001
24.0V battery, interval [19.4V, 27.4V].
Done setting up the UPS.
Asking for UPS status ("Q1" command)...
UPS status: (224.8 224.8 219.7 014 50.0 27.6 25.0 00001001
Charge: 100.0%
dstate_init: sock /var/lib/nut/megatec-mustekups open on fd 6
Asking for UPS status ("Q1" command)...
UPS status: (224.8 224.8 219.7 014 50.0 27.6 25.0 00001001
Charge: 100.0%
Asking for UPS status ("Q1" command)...
UPS status: (226.2 226.2 220.1 015 50.0 27.6 25.0 00001001
Charge: 100.0%
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% :( )
# /lib/nut/megatec -a mustekups -DDD
Network UPS Tools 2.2.0-export? - Megatec protocol driver 1.5.4 [megatec]
Carlos Rodrigues (c) 2003-2007
debug level is '3'
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 power ratings: #220.0 004 24.00 50.0
Asking for UPS status ("Q1" command)...
UPS status: (224.8 224.8 220.1 014 50.1 27.6 25.0 00001001
24.0V battery, interval [19.4V, 27.4V].
Done setting up the UPS.
Asking for UPS status ("Q1" command)...
UPS status: (224.8 224.8 220.1 014 50.0 27.6 25.0 00001001
Charge: 100.0%
dstate_init: sock /var/lib/nut/megatec-mustekups open on fd 6
Asking for UPS status ("Q1" command)...
UPS status: (224.8 224.8 219.7 014 50.1 27.6 25.0 00001001
Charge: 100.0%
Asking for UPS status ("Q1" command)...
UPS status: (224.8 224.8 220.1 015 50.1 27.6 25.0 00001001
Charge: 100.0%
Asking for UPS status ("Q1" command)...
UPS status: (226.2 226.7 220.1 014 50.1 27.6 25.0 00001001
Charge: 100.0%
Asking for UPS status ("Q1" command)...
UPS status: (224.8 224.8 219.7 014 50.1 27.6 25.0 00001001
Charge: 100.0%
Asking for UPS status ("Q1" command)...
UPS status: (226.2 226.7 220.1 014 50.0 27.6 25.0 00001001
Charge: 100.0%
Asking for UPS status ("Q1" command)...
UPS status: (015.3 226.2 223.3 014 50.0 25.2 25.0 10001001
Charge: 72.5%
Asking for UPS status ("Q1" command)...
UPS status: (015.3 015.3 223.4 014 50.0 24.8 25.0 10001001
Charge: 67.5%
Asking for UPS status ("Q1" command)...
UPS status: (015.3 015.3 223.1 015 50.0 24.4 25.0 10001001
Charge: 62.5%
Asking for UPS status ("Q1" command)...
UPS status: (015.3 015.3 222.3 014 50.0 24.3 25.0 10001001
Charge: 61.2%
Asking for UPS status ("Q1" command)...
UPS status: (015.3 015.3 222.7 015 50.0 24.3 25.0 10001001
Charge: 61.2%
Asking for UPS status ("Q1" command)...
UPS status: (015.3 015.3 222.7 015 50.0 24.3 25.0 10001001
Charge: 61.2%
Asking for UPS status ("Q1" command)...
UPS status: (015.3 015.3 223.1 015 50.0 24.3 25.0 10001001
Charge: 61.2%
Asking for UPS status ("Q1" command)...
UPS status: (015.3 015.3 222.3 015 50.0 24.3 25.0 10001001
Charge: 61.2%
Asking for UPS status ("Q1" command)...
UPS status: (015.3 015.3 221.5 015 50.0 24.3 25.0 10001001
Charge: 61.2%
Asking for UPS status ("Q1" command)...
UPS status: (015.3 015.3 222.3 015 50.0 24.3 25.0 10001001
Charge: 61.2%
Asking for UPS status ("Q1" command)...
UPS status: (015.3 015.3 222.7 014 50.0 24.3 25.0 10001001
Charge: 61.2%
Asking for UPS status ("Q1" command)...
UPS status: (222.8 222.8 223.1 014 50.0 24.3 25.0 00001001
Charge: 61.2%
Asking for UPS status ("Q1" command)...
UPS status: (225.7 225.7 220.0 014 50.1 25.2 25.0 00001001
Charge: 72.5%
Asking for UPS status ("Q1" command)...
UPS status: (224.8 224.3 219.6 014 50.0 25.4 25.0 00001001
Charge: 75.0%
Asking for UPS status ("Q1" command)...
UPS status: (226.2 226.2 220.0 014 50.0 25.4 25.0 00001001
Charge: 75.0%
Asking for UPS status ("Q1" command)...
UPS status: (224.8 224.8 219.6 014 50.1 25.5 25.0 00001001
Charge: 76.3%
Asking for UPS status ("Q1" command)...
UPS status: (227.2 227.2 221.5 014 50.1 25.6 25.0 00001001
Charge: 77.5%
Asking for UPS status ("Q1" command)...
UPS status: (226.7 226.7 221.5 014 50.0 25.7 25.0 00001001
Charge: 78.8%
Asking for UPS status ("Q1" command)...
UPS status: (226.7 226.7 221.5 014 50.0 25.7 25.0 00001001
Charge: 78.8%
Asking for UPS status ("Q1" command)...
UPS status: (227.2 227.2 221.9 014 50.1 25.7 25.0 00001001
Charge: 78.8%
Asking for UPS status ("Q1" command)...
UPS status: (228.1 228.1 221.9 014 50.1 25.8 25.0 00001001
Charge: 80.0%
Asking for UPS status ("Q1" command)...
UPS status: (228.1 228.1 221.5 014 50.1 25.8 25.0 00001001
Charge: 80.0%
Asking for UPS status ("Q1" command)...
UPS status: (228.1 228.1 221.9 014 50.1 25.8 25.0 00001001
Charge: 80.0%
Asking for UPS status ("Q1" command)...
UPS status: (228.6 228.1 222.3 014 50.1 26.0 25.0 00001001
Charge: 82.5%
Asking for UPS status ("Q1" command)...
UPS status: (228.1 228.1 221.5 014 50.1 26.0 25.0 00001001
Charge: 82.5%
Asking for UPS status ("Q1" command)...
UPS status: (228.1 228.6 221.5 014 50.1 26.0 25.0 00001001
Charge: 82.5%
Asking for UPS status ("Q1" command)...
UPS status: (227.2 227.2 221.9 014 50.1 26.0 25.0 00001001
Charge: 82.5%
Asking for UPS status ("Q1" command)...
UPS status: (227.2 227.2 221.5 014 50.1 26.1 25.0 00001001
Charge: 83.8%
Asking for UPS status ("Q1" command)...
UPS status: (227.2 227.2 221.5 014 50.1 26.1 25.0 00001001
Charge: 83.8%
Asking for UPS status ("Q1" command)...
UPS status: (227.6 227.6 221.9 014 50.0 26.1 25.0 00001001
Charge: 83.8%
Asking for UPS status ("Q1" command)...
UPS status: (227.6 227.6 221.9 014 50.0 26.2 25.0 00001001
Charge: 85.0%
Asking for UPS status ("Q1" command)...
UPS status: (228.1 228.6 221.5 015 50.0 26.2 25.0 00001001
Charge: 85.0%
Asking for UPS status ("Q1" command)...
UPS status: (228.1 228.1 221.5 014 50.0 26.2 25.0 00001001
Charge: 85.0%
Asking for UPS status ("Q1" command)...
UPS status: (227.6 227.6 221.5 015 50.1 26.2 25.0 00001001
Charge: 85.0%
Asking for UPS status ("Q1" command)...
UPS status: (228.1 228.1 221.9 014 50.1 26.2 25.0 00001001
Charge: 85.0%
Asking for UPS status ("Q1" command)...
UPS status: (228.1 228.1 221.9 015 50.1 26.2 25.0 00001001
Charge: 85.0%
Asking for UPS status ("Q1" command)...
UPS status: (227.6 227.6 221.5 014 50.1 26.3 25.0 00001001
Charge: 86.2%
Asking for UPS status ("Q1" command)...
UPS status: (226.7 226.2 221.1 015 50.1 26.3 25.0 00001001
Charge: 86.2%
Asking for UPS status ("Q1" command)...
UPS status: (226.7 226.7 221.5 014 50.1 26.3 25.0 00001001
Charge: 86.2%
Asking for UPS status ("Q1" command)...
UPS status: (226.2 226.7 220.7 015 50.1 26.4 25.0 00001001
Charge: 87.5%
Asking for UPS status ("Q1" command)...
UPS status: (224.8 224.3 218.0 014 50.1 26.4 25.0 00001001
Charge: 87.5%
Asking for UPS status ("Q1" command)...
UPS status: (226.2 226.2 220.0 015 50.1 26.4 25.0 00001001
Charge: 87.5%
Asking for UPS status ("Q1" command)...
UPS status: (226.2 226.2 220.0 014 50.0 26.4 25.0 00001001
Charge: 87.5%
Asking for UPS status ("Q1" command)...
UPS status: (225.7 225.7 220.0 015 50.1 26.4 25.0 00001001
Charge: 87.5%
Asking for UPS status ("Q1" command)...
UPS status: (225.7 225.7 220.3 014 50.0 26.4 25.0 00001001
Charge: 87.5%
Signal 2: exiting
2. Monitoring with the USB interface
I was really disappointed to read in the mustek documentation that the
usb interface was "reserved" for Windows. Despite mustek restriction,
I
tried megatec_usb and nut was able to recognize the megatec protocol
(what a relief, heartbeats 100 ;).
usb 2-1: new low speed USB device using ohci_hcd and address 4
usb 2-1: configuration #1 chosen from 1 choice
hiddev96: USB HID v1.00 Device [Cypress Semiconductor USB to Serial] on
usb-0000:00:02.0-1
# lsusb
Bus 001 Device 001: ID 0000:0000
Bus 002 Device 004: ID 0665:5161 <-------------------- Mustek device
Bus 002 Device 003: ID 05a9:4519 OmniVision Technologies, Inc.
Bus 002 Device 002: ID 1532:0002
Bus 002 Device 001: ID 0000:0000
lsusb identifies an ID 0665:5161 interface like the Belkin device
defined in the megatec_usbs KnownDevices().
# /lib/nut/megatec_usb -a mustekups-usb -DDD
Network UPS Tools 2.2.0-export? - Megatec protocol driver 1.5.4
[megatec_usb]
Carlos Rodrigues (c) 2003-2007
Serial-over-USB transport layer for Megatec protocol driver [megatec_usb]
debug level is '3'
Checking device (0000/0000) (001/001)
- VendorID: 0000
- ProductID: 0000
- Manufacturer: Linux 2.6.23-rc1-git3 ehci_hcd
- Product: EHCI Host Controller
- Serial Number: 0000:00:02.1
- Bus: 001
Trying to match device
Device does not match - skipping
Checking device (0665/5161) (002/005)
- VendorID: 0665
- ProductID: 5161
- Manufacturer: Cypress Semiconductor
- Product: USB to Serial
- 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...
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...
"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.
1 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 power ratings: #220.0 004 24.00 50.0
Asking for UPS status ("Q1" command)...
UPS status: (228.1 228.1 221.5 014 50.1 27.5 25.0 00001001
24.0V battery, interval [19.4V, 27.4V].
Done setting up the UPS.
Asking for UPS status ("Q1" command)...
UPS doesn't return any information about its status.
dstate_init: sock /var/lib/nut/megatec_usb-mustekups-usb open on fd 6
Asking for UPS status ("Q1" command)...
UPS status: (228.1 228.6 221.9 014 50.1 27.5 25.0 00001001
Charge: 100.0%
Asking for UPS status ("Q1" command)...
UPS status: (228.6 228.1 221.5 015 50.1 27.5 25.0 00001001
Charge: 100.0%
Asking for UPS status ("Q1" command)...
UPS status: (228.6 228.1 221.9 014 50.1 27.5 25.0 00001001
Charge: 100.0%
Asking for UPS status ("Q1" command)...
UPS status: (229.1 229.1 221.9 014 50.0 27.5 25.0 00001001
Charge: 100.0%
Asking for UPS status ("Q1" command)...
UPS status: (228.1 228.1 221.9 014 50.1 27.5 25.0 00001001
Charge: 100.0%
Signal 2: exiting
and the upcs output gives,
# 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
3. Shutdown process
I have tested the forced shutdown process with upsmon and ended with an
weird error messsage.
It is like if the upsmon will not set the FSD flag on the Mustek
PowerMust 1000va USB ups.
I'm using the megatec_usb driver for the test.
Here are the last messages sent to the syslog daemon,
Aug 7 21:06:21 seal upsmon[9421]: Signal 10: User requested FSD
Aug 7 21:06:21 seal upsd[9365]: Client upsmon at 127.0.0.1 set FSD on UPS
[PowerMust]
Aug 7 21:06:21 seal upsmon[9421]: Executing automatic power-fail shutdown
Aug 7 21:06:21 seal wall[9828]: wall: user nut broadcasted 2 lines (43
chars)
Aug 7 21:06:21 seal upsmon[9421]: Auto logout and shutdown proceeding
Aug 7 21:06:26 seal upsd[9365]: Host 127.0.0.1 disconnected (read failure)
Aug 7 21:06:26 seal shutdown[9834]: shutting down for system halt
Aug 7 21:06:26 seal init: Switching to runlevel: 0
Aug 7 21:06:31 seal upsd[9365]: Signal 15: exiting
Aug 7 21:06:32 seal sshd[8446]: Received signal 15; terminating.
Aug 7 21:06:33 seal smartd[8327]: smartd received signal 15: Terminated
Aug 7 21:06:33 seal smartd[8327]: smartd is exiting (exit status 0)
[...]
On the console we can read the following error message:
shutting down UPS immediately
set_data_agiler: output string too large
also the UPS never succeed in killing the power.
It looks like a bug for me or have i just missed something ?
Many thanks to the nut team and especially to Carlos Rodrigues for his
work on the megatec_usb driver (i hope i have forgotten no one) :)
Jj