[Nut-upsuser] support for APC Matrix 5000, vintage 12/00 (was: NUT apcsmart driver - firmware addition)
Hey Jarett,
2009/2/24 jarett.stev...@usermail.com
After upgrading to the 2.4.1 version, I wasn't able to read as many
variables from my UPS. After a bit of experimentation, I determined that
the firmware on my UPS was different than what is currently in the
apcsmart driver, though it had worked before. I located my firmware
version (5ZM), and added in with the other APC Matrix entries; now
everything works as expected!
$ diff -u apcsmart.c.orig apcsmart.c
--- apcsmart.c.orig Tue Feb 24 14:00:34 2009
+++ apcsmart.c Tue Feb 24 14:01:04 2009
@@ -564,6 +564,7 @@
!strcmp(buf, 8TI) || /* (SmartUPS 1250,
vintage 08/24/95.) */
!strcmp(buf, 6TI) || /* (APC600.) */
!strcmp(buf, 6QI) || /* (APC600.) */
+ !strcmp(buf, 5ZM) || /* (APC Matrix
5000, vintage 12/00.) */
!strcmp(buf, 0ZI) || /* (APC Matrix
3000, vintage 10/99.) */
!strcmp(buf, 5UI)) { /* (APC Matrix
5000, vintage 10/93.) */
upsdebugx(1, Found Smart-UPS);
$
$
$ diff -u apcsmart.h.orig apcsmart.h
--- apcsmart.h.orig Tue Feb 24 14:00:06 2009
+++ apcsmart.h Tue Feb 24 14:00:26 2009
@@ -267,6 +267,7 @@
/* APC Matrix */
{ 0ZI,79ABCDEFGKLMNOPQRSUVWXYZcefgjklmnopqrsuxz/, 0 },
{ 5UI,79ABCDEFGKLMNOPQRSUVWXYZcefgjklmnopqrsuxz/, 0 },
+ { 5ZM,79ABCDEFGKLMNOPQRSUVWXYZcefgjklmnopqrsuxz/, 0
},
{ NULL, NULL, 0 },
};
thanks, I've applied it to the development version.
cheers,
Arnaud
--
Linux / Unix Expert RD - Eaton - http://www.eaton.com/mgeops
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://people.debian.org/~aquette/
Free Software Developer - http://arnaud.quette.free.fr/
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
[Nut-upsuser] Mustek PowerMust 424 / 636 / 848 (USB) compatibility
Hi Vitaly, 2009/2/26 Vitaly Polyakov v...@fapu.ru Hello. You are the site administrator Project Network UPS Tools, are not you? I think? it is a good idea to add information about the compatibility the NUT with a Mustek PowerMust 424/636/848 USB. These UPS are using modified protocol, and therefore the old driver megatec_usb is not suitable and the new driver blazer was created. Details about this, I hardly found here: http://lists.alioth.debian.org/pipermail/nut-upsdev/2008-December/003555.html I think, if you post information about this driver the page Compatibility - this will save much time users of this equipment. Beforehand thank. P.S. Sorry for my English. thanks, I've just applied it to the development tree. cheers, Arnaud -- Linux / Unix Expert RD - Eaton - http://www.eaton.com/mgeops Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://people.debian.org/~aquette/ Free Software Developer - http://arnaud.quette.free.fr/ ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] driver for HP/Compaq T750 ?
Am Donnerstag, 26. Februar 2009 20:37:56 schrieben Sie: Citeren KP Kirchdoerfer kap...@bering-uclibc.de: [...] And the upshid-ups driver ends with: No matching HID UPS found Driver failed to start (exit status=1) Try this driver again, but make sure to add productid = 1f06 to the ups.conf entry for this device. Chances are that it is a re-branded Tripplite unit (we've seen other HP units that are actually this brand). Unfortunately the same result... (Driver failed to start...) any more hints? regards kp ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] driver for HP/Compaq T750 ?
2009/2/27 KP Kirchdoerfer kap...@bering-uclibc.de Am Donnerstag, 26. Februar 2009 20:37:56 schrieben Sie: Citeren KP Kirchdoerfer kap...@bering-uclibc.de: [...] And the upshid-ups driver ends with: No matching HID UPS found Driver failed to start (exit status=1) Try this driver again, but make sure to add productid = 1f06 to the ups.conf entry for this device. Chances are that it is a re-branded Tripplite unit (we've seen other HP units that are actually this brand). Unfortunately the same result... (Driver failed to start...) any more hints? lsusb -vv -d 03f0:1f06 also test bcmxcp or bcmxcp_usb Arnaud -- Linux / Unix Expert RD - Eaton - http://www.eaton.com/mgeops Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://people.debian.org/~aquette/ Free Software Developer - http://arnaud.quette.free.fr/ ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] driver for HP/Compaq T750 ?
Am Freitag, 27. Februar 2009 18:35:11 schrieb Arnaud Quette: 2009/2/27 KP Kirchdoerfer kap...@bering-uclibc.de Am Donnerstag, 26. Februar 2009 20:37:56 schrieben Sie: Citeren KP Kirchdoerfer kap...@bering-uclibc.de: [...] And the upshid-ups driver ends with: No matching HID UPS found Driver failed to start (exit status=1) Try this driver again, but make sure to add productid = 1f06 to the ups.conf entry for this device. Chances are that it is a re-branded Tripplite unit (we've seen other HP units that are actually this brand). Unfortunately the same result... (Driver failed to start...) any more hints? lsusb -vv -d 03f0:1f06 see below also test bcmxcp or bcmxcp_usb Also these does not work... kp Bus 001 Device 002: ID 03f0:1f06 Hewlett-Packard Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x03f0 Hewlett-Packard idProduct 0x1f06 bcdDevice0.00 iManufacturer 4 Hewlett-Packard iProduct 36 T750 INTL iSerial50 2CJ5380638 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 34 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower 50mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 3 Human Interface Device bInterfaceSubClass 0 No Subclass bInterfaceProtocol 0 None iInterface 0 HID Device Descriptor: bLength 9 bDescriptorType33 bcdHID 1.11 bCountryCode 33 US bNumDescriptors 1 bDescriptorType34 Report wDescriptorLength 900 Report Descriptors: ** UNAVAILABLE ** Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0008 1x 8 bytes bInterval 248 Device Status: 0x0003 Self Powered Remote Wakeup Enabled ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] driver for HP/Compaq T750 ?
fredag 27 februari 2009 18:35:11 skrev Arnaud Quette: 2009/2/27 KP Kirchdoerfer kap...@bering-uclibc.de 8---snip-- Try this driver again, but make sure to add productid = 1f06 to the ups.conf entry for this device. Chances are that it is a re-branded Tripplite unit (we've seen other HP units that are actually this brand). Unfortunately the same result... (Driver failed to start...) any more hints? lsusb -vv -d 03f0:1f06 also test bcmxcp or bcmxcp_usb This would not work as the vendor product id is hardcoded in the nut_usb.c I can not recognise the look of the ups. So I can not say if it is a re-branded version. Regards Kjell ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] driver for HP/Compaq T750 ?
fredag 27 februari 2009 18:48:58 skrev KP Kirchdoerfer: 8snip--- Bus 001 Device 002: ID 03f0:1f06 Hewlett-Packard Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x03f0 Hewlett-Packard idProduct 0x1f06 bcdDevice0.00 iManufacturer 4 Hewlett-Packard iProduct 36 T750 INTL iSerial50 2CJ5380638 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 34 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower 50mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 3 Human Interface Device bInterfaceSubClass 0 No Subclass bInterfaceProtocol 0 None iInterface 0 HID Device Descriptor: bLength 9 bDescriptorType33 bcdHID 1.11 bCountryCode 33 US bNumDescriptors 1 bDescriptorType34 Report wDescriptorLength 900 Report Descriptors: ** UNAVAILABLE ** Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0008 1x 8 bytes bInterval 248 Device Status: 0x0003 Self Powered Remote Wakeup Enabled This look like a hid device. Have you tested the usbhid_ups driver in debug mode. /Kjell ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] driver for HP/Compaq T750 ?
fredag 27 februari 2009 19:09:27 skrev KP Kirchdoerfer: Am Freitag, 27. Februar 2009 18:54:00 schrieben Sie: fredag 27 februari 2009 18:48:58 skrev KP Kirchdoerfer: 8snip--- If you ask me to run upsdrvctl with -D I'll don't geht more information than before: /sbin/upsdrvctl -D start compaq-ups Network UPS Tools - UPS driver controller 2.2.2 Starting UPS: compaq-ups Network UPS Tools: 0.29 USB communication driver - core 0.33 (2.2.2) No matching HID UPS found Driver failed to start (exit status=1) You can rise the debug level by adding D. So try -DDD . I have not worked with the usbups_hid driver but it should give some more info. /Kjell ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] driver for HP/Compaq T750 ?
fredag 27 februari 2009 19:37:42 skrev KP Kirchdoerfer: You can rise the debug level by adding D. So try -DDD . I have not worked with the usbups_hid driver but it should give some more info. Yep; I tried that also, but didn't got more output OK, then we have a bastard ;-( The only thing I can think of is to make a snoop of the traffic. This may be done by a windows machine running the original driver and the usbsnoop program. The SnoopyPro-0.22 on SF is one sniffer. This can be tricky sometimes to get a good log, but it can tell us if it is a known protocol or something HP have come up with. /Kjell P.S. If your up for this, take it to the nut-upsdev list. ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
