Re: [Nut-upsuser] Selftest intervall, APC Smart-UPS 750 RM
2009/9/3 Arjen de Korte Citeren Arnaud Quette strange indeed. the data is there, and now know. I've made a minor fix (r1955). please test it and tell me back if input.transfer.reason appears now. No, it won't. The 'input.transfer.reason' value is set through the VRANGE and FRANGE status bits. In the absence of either, it will be cleared. Therefor, you can't treat this as an ordinary variable. There are HID PDC fields that use these, so we'll have to be careful to change this in order not to break other subdrivers in the process. ooch, right! I completely missed that. thanks for pointing it Arjen ;-) I just commited a fix (r1956): it only reports voltage or frequency out of range, and not over/under voltage / ripple / force / selftest as it was in the previous version. Is it fine like that Markus? 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://www.debian.org 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] UPS::Nut PERL module is rewritten
Hi Gabor, 2009/9/3 Kiss Gabor (Bitman) can you please send me the source? Do you mean the unpacked Perl module? Sure. See attachment. great, thanks. everything seems fine, though I've very roughly tested... anything against embedding it in the NUT source tree? Why not? :-) Meanwhile I modified function Set() a bit in order to handle spaces in values a more intelligent way. See attachment. ok, I've just commited the last version to the development tree (r1957). Later if I have time I'll try to implement STARTTLS command too. don't hesitate to send update patches (on the upsdev list). thanks a lot for your contribution, Arnaud -- Linux / Unix Expert RD - Eaton - http://www.eaton.com/mgeops Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://www.debian.org 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] UPS::Nut PERL module is rewritten
Hi Phil, 2009/9/3 Brother Railgun of Reason On Thu, Sep 03, 2009 at 02:33:36PM +0200, Arnaud Quette wrote: 2009/9/1 Kiss Gabor (Bitman) can you please send me the source? Do you mean the unpacked Perl module? Sure. See attachment. great, thanks. everything seems fine, though I've very roughly tested... anything against embedding it in the NUT source tree? I'm thinking about writing an alternate NUT monitor CGI in Perl using this module, since I've been unable to get the currently-included CGI to work or even get enough diagnostic information out of it to enable me to figure out why it's not working. don't hesitate to post your work (on the upsdev list), so that we can consider it for a possible inclusion or at least for referencing it on the Projects page. 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://www.debian.org 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] MGE Evolution mge-utalk Driver Not Connected error
2009/8/23 Phil Harrison Hi Arnaud, Hi Phil, sorry for the lag, I was sure this mail was already gone... Thanks for your suggestion. I had to wait for a moment to take the UPS offline to test your suggestion. I shut down attached system, turned off the UPS and unplugged mains power for 5-10 seconds. I think replugged mains power, turned on the UPS and all attached equiptment started turning on. sudo /lib/nut/mge-shut -DDD -a ups1 gives me same as before. using mge-utalk same as before as well. I'm now doubting: reading back the thread, you mention an esv14+ but the msg title is about an evolution. if it's the former, stay with mge-utalk. if it's the latter, go with mge-shut. Is there anyway I can test whether the problem is to do with the USB to serial adaptor? according to dmesg it should be working correctly. [0.01] console [tty0] enabled [9.241586] usb 8-2: pl2303 converter now attached to ttyUSB0 it's quite possible, since I've seen iirc some issue when the converter is attached to a hub that is not a root one. so, is the converter attached to a root hub (ie directly on the PC)? 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://www.debian.org 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] UPS::Nut PERL module is rewritten
On Fri, Sep 04, 2009 at 11:06:32AM +0200, Arnaud Quette wrote: Hi Phil, 2009/9/3 Brother Railgun of Reason On Thu, Sep 03, 2009 at 02:33:36PM +0200, Arnaud Quette wrote: 2009/9/1 Kiss Gabor (Bitman) can you please send me the source? Do you mean the unpacked Perl module? Sure. See attachment. great, thanks. everything seems fine, though I've very roughly tested... anything against embedding it in the NUT source tree? I'm thinking about writing an alternate NUT monitor CGI in Perl using this module, since I've been unable to get the currently-included CGI to work or even get enough diagnostic information out of it to enable me to figure out why it's not working. don't hesitate to post your work (on the upsdev list), so that we can consider it for a possible inclusion or at least for referencing it on the Projects page. Sure, will do. I won't be able to get to it immediately, as I'm in the middle of a bunch of major house maintenance right now, but once I get something put together I'll post it. (footnote: upsdev list? Don't think I'm on it.) -- Phil Stracchino, CDK#2 DoD#299792458 ICBM: 43.5607, -71.355 ala...@caerllewys.net ala...@metrocast.net p...@co.ordinate.org Renaissance Man, Unix ronin, Perl hacker, Free Stater It's not the years, it's the mileage. ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Selftest intervall, APC Smart-UPS 750 RM
Hello I'm now at r1957 and I find no input.transfer.reason in the output of upsc. usbhid-ups -D -a apcsmart shows no UPS.BatterySystem.Battery.TestPeriod ups.test.interval Hope that helps, bye wildi On Friday 04 September 2009 10:28:48 you wrote: 2009/9/3 Arjen de Korte Citeren Arnaud Quette strange indeed. the data is there, and now know. I've made a minor fix (r1955). please test it and tell me back if input.transfer.reason appears now. No, it won't. The 'input.transfer.reason' value is set through the VRANGE and FRANGE status bits. In the absence of either, it will be cleared. Therefor, you can't treat this as an ordinary variable. There are HID PDC fields that use these, so we'll have to be careful to change this in order not to break other subdrivers in the process. ooch, right! I completely missed that. thanks for pointing it Arjen ;-) I just commited a fix (r1956): it only reports voltage or frequency out of range, and not over/under voltage / ripple / force / selftest as it was in the previous version. Is it fine like that Markus? cheers, Arnaud ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Tripplite_usb Driver fail on OMNIVS1500
Yes, This is my config summary: enable SSL development code: yes enable libwrap (tcp-wrappers) support: no enable IPv6 support: yes build CGI programs: no build and install the development files: no build serial drivers: yes build SNMP drivers: yes build USB drivers: yes enable HAL support: no build neon based XML driver: no build Powerman PDU client driver: no Is there another way to update to 2.4 other than building from source? I can't seem to get this to work and it is probably because I am relatively new to linux. After configuring it with those tags I still do not have upsdrvctl. When doing this upsdrvctl start I get this bash: /sbin/upsdrvctl: No such file or directory. There is now nothing in /usr/local/ups/bin or /usr/local/ups/sbin. Arnaud Quette aquette@gmail.com writes: have you done the make uninstall, then used the configure directives above, then make ; make install? ___ Chris Abel Systems and Network Administrator Wildwood Programs 2995 Curry Road Extension Schenectady, NY 12303 518-836-2341 ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Selftest intervall, APC Smart-UPS 750 RM
2009/9/4 Markus Wildi Hello Hi I'm now at r1957 and I find no input.transfer.reason ah, blind development... please send me the debug output (level 5) of the driver. in the output of upsc. usbhid-ups -D -a apcsmart shows no UPS.BatterySystem.Battery.TestPeriod ups.test.interval you might have misunderstood me: I've not found anything (in the HID dump nor in apcupsd) that shows that this variable exist. it may be in the remaining unknown/unmapped data (prefixed by ff86). do you have access to this settings in powerchute or apcupsd? 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://www.debian.org 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] Tripplite_usb Driver fail on OMNIVS1500
2009/9/4 Chris Abel ca...@wildwood.edu Yes, This is my config summary: enable SSL development code: yes enable libwrap (tcp-wrappers) support: no enable IPv6 support: yes build CGI programs: no build and install the development files: no build serial drivers: yes build SNMP drivers: yes build USB drivers: yes enable HAL support: no build neon based XML driver: no build Powerman PDU client driver: no Is there another way to update to 2.4 other than building from source? I can't seem to get this to work and it is probably because I am relatively new to linux. ok, before going to deep on this and wasting too much time on compilation, I'd like to have: - the output of lsusb -vv -d09ae:0001. - your USB topology (ie is the UPS plugged on a root hub, are there other devices on the same bus, ...) - the result of ls -l /dev/bus/usb/XXX/YYY where XXX is the Bus number and YYY the Device number as shown by lsubs) once this part is ok, we'll check again to test 2.4.1 from the source 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://www.debian.org 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] Tripplite_usb Driver fail on OMNIVS1500
Arnaud Quette aquette@gmail.com writes: ok, before going to deep on this and wasting too much time on compilation, I'd like to have: - the output of lsusb -vv -d09ae:0001. Bus 001 Device 002: ID 09ae:0001 Tripp Lite Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x09ae Tripp Lite idProduct 0x0001 bcdDevice0.01 iManufacturer 1 TRIPP LITE iProduct2 TRIPP LITE UPS iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 34 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x80 (Bus Powered) MaxPower 60mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 3 Human Interface Device bInterfaceSubClass 1 Boot Interface Subclass bInterfaceProtocol 0 None iInterface 0 HID Device Descriptor: bLength 9 bDescriptorType33 bcdHID 1.00 bCountryCode0 Not supported bNumDescriptors 1 bDescriptorType34 Report wDescriptorLength 52 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 10 Device Status: 0x (Bus Powered) - your USB topology (ie is the UPS plugged on a root hub, are there other devices on the same bus, ...) Bus 002 Device 001: ID : Bus 001 Device 005: ID 05ac:0302 Apple Computer, Inc. Apple Optical Mouse [Fujitsu] Bus 001 Device 004: ID 05ac:0204 Apple Computer, Inc. Bus 001 Device 003: ID 05ac:1002 Apple Computer, Inc. Apple Extended Keyboard Hub [Mitsumi] Bus 001 Device 002: ID 09ae:0001 Tripp Lite Bus 001 Device 001: ID : Yes there are other devices on the same bus. - the result of ls -l /dev/bus/usb/XXX/YYY where XXX is the Bus number and YYY the Device number as shown by lsubs) crw-rw-r-- 1 root nut 189, 1 2009-09-04 12:50 /dev/bus/usb/001/002 once this part is ok, we'll check again to test 2.4.1 from the source tree. Hope that helps. ___ Chris Abel Systems and Network Administrator Wildwood Programs 2995 Curry Road Extension Schenectady, NY 12303 518-836-2341 ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Tripplite_usb Driver fail on OMNIVS1500
2009/9/4 Chris Abel ca...@wildwood.edu Arnaud Quette aquette@gmail.com writes: ok, before going to deep on this and wasting too much time on compilation, I'd like to have: - the output of lsusb -vv -d09ae:0001. Bus 001 Device 002: ID 09ae:0001 Tripp Lite Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x09ae Tripp Lite idProduct 0x0001 bcdDevice0.01 iManufacturer 1 TRIPP LITE iProduct2 TRIPP LITE UPS iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 34 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x80 (Bus Powered) MaxPower 60mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 3 Human Interface Device bInterfaceSubClass 1 Boot Interface Subclass bInterfaceProtocol 0 None iInterface 0 HID Device Descriptor: bLength 9 bDescriptorType33 bcdHID 1.00 bCountryCode0 Not supported bNumDescriptors 1 bDescriptorType34 Report wDescriptorLength 52 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 10 Device Status: 0x (Bus Powered) - your USB topology (ie is the UPS plugged on a root hub, are there other devices on the same bus, ...) Bus 002 Device 001: ID : Bus 001 Device 005: ID 05ac:0302 Apple Computer, Inc. Apple Optical Mouse [Fujitsu] Bus 001 Device 004: ID 05ac:0204 Apple Computer, Inc. Bus 001 Device 003: ID 05ac:1002 Apple Computer, Inc. Apple Extended Keyboard Hub [Mitsumi] Bus 001 Device 002: ID 09ae:0001 Tripp Lite Bus 001 Device 001: ID : Yes there are other devices on the same bus. - the result of ls -l /dev/bus/usb/XXX/YYY where XXX is the Bus number and YYY the Device number as shown by lsubs) crw-rw-r-- 1 root nut 189, 1 2009-09-04 12:50 /dev/bus/usb/001/002 once this part is ok, we'll check again to test 2.4.1 from the source tree. Hope that helps. ok, now you can recompile 2.4.1 with the flags mentioned before, and do only a make (not install) then fire drivers/tripplite_usb -D -a upsname defined in /etc/nut/ups.conf and send us back the output. last question: have you bought this unit recently? 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://www.debian.org 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
