[Nut-upsdev] Maruson power net 1500 support?

David Mathog mathog at caltech.edu
Tue May 20 18:10:59 UTC 2008


As suggested, the megatec_usb driver was attempted.  ups.conf has:

	driver = megatec_usb
	port = auto
	desc = "Top Maruson UPS"


Unfortunately, both as ups (the account created when nut was
compiled/installed) and as root, this is what happens:


% /usr/local/src/nut-2.2.2/drivers/megatec_usb -a MarusonTop -DDDD
Network UPS Tools 2.2.2 - Megatec protocol driver 1.5.14 [megatec_usb]
Carlos Rodrigues (c) 2003-2008

Serial-over-USB transport layer for Megatec protocol driver [megatec_usb]
Andrey Lelikov (c) 2006, Alexander Gordeev (c) 2006-2007, Jon Gough (c) 2007

debug level is '4'
Checking device (06DA/0003) (003/014)
- VendorID: 06da
- ProductID: 0003
- Manufacturer: unknown
- Product: USB UPS
- Serial Number: unknown
- Bus: 003
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...
Asking for UPS status [Q1]...
Q1 => FAILED [short read]
Q1 detail: (14 bytes) => 28 31 31 33 2e 39 20 31 30 30 31 30 30 30
Asking for UPS status [Q1]...
Q1 => FAILED [short read]
Q1 detail: (14 bytes) => 28 31 31 33 2e 39 20 31 30 30 31 30 30 30
Asking for UPS status [Q1]...
Q1 => FAILED [short read]
Q1 detail: (14 bytes) => 28 31 31 33 2e 38 20 31 30 30 31 30 30 30
Asking for UPS status [Q1]...
Q1 => FAILED [short read]
Q1 detail: (14 bytes) => 28 31 31 33 2e 39 20 31 30 30 31 30 30 30
Asking for UPS status [Q1]...
Q1 => FAILED [short read]
Q1 detail: (14 bytes) => 28 31 31 33 2e 39 20 31 30 30 31 30 30 30
5 out of 5 detection attempts failed (minimum failures: 2).
Megatec protocol UPS not detected.

lsusb still shows the device, ie

% lsusb -vvv

Bus 003 Device 016: ID 06da:0003 Phoenixtec Power Co., Ltd 
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               1.10
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0         8
  idVendor           0x06da Phoenixtec Power Co., Ltd
  idProduct          0x0003 
  bcdDevice            2.00
  iManufacturer           3 OMRON
  iProduct                1 USB UPS
  iSerial                 0 
etc.

I think the udev stuff is working properly, as the nut script was
installed in there, and the action of the driver changed to the above
(from something even less useful) after the UPS was unplugged, and then
plugged back in, subsequent to nut installation.  It looks like it has
the ability to read/write to the USB device, but what's coming back is
not what it expected to see (only 14 bytes insetad of ???), hence the
short read messages.

Suggestions???

Thanks,

David Mathog
mathog at caltech.edu
Manager, Sequence Analysis Facility, Biology Division, Caltech



More information about the Nut-upsdev mailing list