[Nut-upsuser] 06da:0002 Phoenixtec Power Co., Ltd UPS
Hi! all. I have been reading every mail and news about nut and 06da:0002 Phoenixtec but not found a solution. I have a very nice working ups from: CENER ref: Active 1000VA 230V 12 CENER and front logo LA 900 It has COM3 and USB plugs, I don't know if it needs a standar RS232 I have test with varius drivers in ups.conf [MyUPS] driver = bcmxcp_usb | usbhid-ups | blazer_usb (one of then each time) port = auto # lsusb Bus 006 Device 004: ID 06da:0002 Phoenixtec Power Co., Ltd UPS # dmesg [ 1208.332585] usb 6-1: new low-speed USB device number 4 using uhci_hcd [ 1208.510146] usb 6-1: New USB device found, idVendor=06da, idProduct=0002 [ 1208.510151] usb 6-1: New USB device strings: Mfr=4, Product=38, SerialNumber=0 [ 1208.510155] usb 6-1: Product: USB Cable (V2.00) [ 1208.510157] usb 6-1: Manufacturer: Phoenixtec Power # lsusb -v Bus 006 Device 004: ID 06da:0002 Phoenixtec Power Co., Ltd UPS Couldn't open device, some information will be missing Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 1.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x06da Phoenixtec Power Co., Ltd idProduct 0x0002 UPS bcdDevice0.06 iManufacturer 4 iProduct 38 iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 34 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x60 (Missing must-be-set bit!) Self Powered Remote Wakeup MaxPower 20mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 ** UNRECOGNIZED: 09 21 00 01 21 01 22 51 00 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 5 In the list, I found: https://www.mail-archive.com/nut-upsdev@lists.alioth.debian.org/msg00191.html Hm, bad idea. The Phoenixtec make the interface card to early Powerware ups'es with just the Vendor/product id 06da:0002. And it speaks the bcmxcp protocol. B.t.w an bad usb implementation that need a dirty fix to make it work. I can't find that dirty fix to make it work -- Output with driver bcmxcp_usb 0.000361 Starting UPS: Phoenixtec 0.000445 exec: /lib/nut/bcmxcp_usb -a Phoenixtec -u root Network UPS Tools - BCMXCP UPS driver 0.26 (2.6.4) USB communication subdriver 0.21 usb_set_debug: Setting debugging level to 3 (on) usb_os_init: Found USB VFS at /dev/bus/usb usb_os_find_busses: Found 008 usb_os_find_busses: Found 007 usb_os_find_busses: Found 006 usb_os_find_busses: Found 005 usb_os_find_busses: Found 004 usb_os_find_busses: Found 003 usb_os_find_busses: Found 002 usb_os_find_busses: Found 001 usb_os_find_devices: Found 005 on 008 skipped 1 class/vendor specific interface descriptors usb_os_find_devices: Found 003 on 008 skipped 1 class/vendor specific interface descriptors skipped 1 class/vendor specific interface descriptors usb_os_find_devices: Found 001 on 008 error obtaining child information: Inappropriate ioctl for device error obtaining child information: Inappropriate ioctl for device usb_os_find_devices: Found 001 on 007 usb_os_find_devices: Found 003 on 006 skipped 1 class/vendor specific interface descriptors skipped 1 class/vendor specific interface descriptors usb_os_find_devices: Found 002 on 006 usb_os_find_devices: Found 001 on 006 error obtaining child information: Inappropriate ioctl for device usb_os_find_devices: Found 001 on 005 usb_os_find_devices: Found 001 on 004 usb_os_find_devices: Found 001 on 003 usb_os_find_devices: Found 001 on 002 usb_os_find_devices: Found 002 on 001 usb_os_find_devices: Found 001 on 001 Communications with UPS lost: Error executing command Could not communicate with the ups: Resource temporarily unavailable CLOSING - After replace with new batteries, it keeps beeping every minute, I need to reset batteries counter or timer ? Anyone can help me about this CENER como Active 1000VA 230V 12 CENER Bus 006 Device 004: ID 06da:0002 Phoenixtec Power Co., Ltd UPS Thanks in advanced. Best regards. -- Jose Angel Navarro Cortes email: j...@telefonica.net web: http://janc.es/ Usuario Linux: #49178
Re: [Nut-upsuser] Do I need to configure times and percents?
01.12.2014, 06:18, Charles Lepple clep...@gmail.com: On Nov 29, 2014, at 7:32 AM, Victor Porton por...@narod.ru wrote: On Debian Linux jessie: After buying an UPS and installation of nut-server and nut-client at my PC and configuring the ports and the protocol, do I need to adjust time and/or percentage parameters, to be sure my computer will be turned off automatically after a reasonable time after failing electricity? I would recommend testing with a dummy load to see if the UPS operates as you expect it to. In particular, there is no standard for a reasonable time for shutdown. In the default configuration, NUT's upsmon program shuts the system down after the UPS reports a low battery. Your UPS may or may not allow that threshold to be configured, so there are several other options if you want to shut down after a specific time on battery, or when other conditions are reached. My UPS is Advice PRS850. You may want to check the list archives to see if anyone else has additional information on other UPS models from this manufacturer: http://www.networkupstools.org/support.html#_mailing_lists It actually isn't on our hardware compatibility list: http://buildbot.networkupstools.org/~buildbot/cayman/docs/latest/stable-hcl.html If you post additional details (output of upsc and upsrw) someone may be able to offer more specific suggestions. $ upsc advice Init SSL without certificate database battery.charge: 100 battery.voltage: 13.70 battery.voltage.high: 13.00 battery.voltage.low: 10.40 battery.voltage.nominal: 12.0 device.type: ups driver.name: blazer_usb driver.parameter.pollinterval: 2 driver.parameter.port: /dev/ttyS0 driver.parameter.productid: 5161 driver.parameter.vendorid: 0665 driver.version: 2.7.2 driver.version.internal: 0.11 input.current.nominal: 3.0 input.frequency: 50.0 input.frequency.nominal: 50 input.voltage: 234.9 input.voltage.fault: 234.9 input.voltage.nominal: 230 output.voltage: 234.9 ups.beeper.status: enabled ups.delay.shutdown: 30 ups.delay.start: 180 ups.load: 18 ups.productid: 5161 ups.status: OL ups.type: offline / line interactive ups.vendorid: 0665 -- Victor Porton - http://portonvictor.org ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Do I need to configure times and percents?
On Dec 1, 2014, at 4:11 AM, Victor Porton por...@narod.ru wrote: battery.voltage: 13.70 battery.voltage.high: 13.00 battery.voltage.low: 10.40 These are the voltage thresholds for the UPS, so theoretically the UPS will send the LB signal when the battery voltage goes lower than 10.40 Volts. Also, if battery.charge works, you can use ignorelb if you want to shut down at another level of charge: http://www.networkupstools.org/docs/man/ups.conf.html#_ups_fields ups.delay.shutdown: 30 ups.delay.start: 180 These timers are in seconds. You will want to verify this, but according to those values, the UPS will shut off its output 30 seconds after the shutdown signal (so you need to make sure that your OS shutdown takes less time than that). Does upsrw -l advice show anything? -- Charles Lepple clepple@gmail ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] 06da:0002 Phoenixtec Power Co., Ltd UPS
On Dec 1, 2014, at 3:00 AM, j...@telefonica.net wrote: I have a very nice working ups from: CENER ref: Active 1000VA 230V 12 CENER and front logo LA 900 Do you know what software was originally recommended for the UPS? Unfortunately, Phoenixtec seems to have made a lot of different USB-to-serial adapters. The most likely driver is blazer_usb (or nutdrv_qx, which is newer). You may need to shut down the UPS completely (turn power off, and unplug) if the other drivers have sent commands that put the UPS into a bad state. -- Charles Lepple clepple@gmail ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Do I need to configure times and percents?
01.12.2014, 14:50, Charles Lepple clep...@gmail.com: On Dec 1, 2014, at 4:11 AM, Victor Porton por...@narod.ru wrote: battery.voltage: 13.70 battery.voltage.high: 13.00 battery.voltage.low: 10.40 These are the voltage thresholds for the UPS, so theoretically the UPS will send the LB signal when the battery voltage goes lower than 10.40 Volts. Also, if battery.charge works, you can use ignorelb if you want to shut down at another level of charge: http://www.networkupstools.org/docs/man/ups.conf.html#_ups_fields ups.delay.shutdown: 30 ups.delay.start: 180 These timers are in seconds. You will want to verify this, but according to those values, the UPS will shut off its output 30 seconds after the shutdown signal (so you need to make sure that your OS shutdown takes less time than that). Does upsrw -l advice show anything? $ upsrw -l advice upsrw: invalid option -- 'l' Network UPS Tools upsrw 2.7.2 usage: upsrw [-h] upsrw [-s variable] [-u username] [-p password] ups Demo program to set variables within UPS hardware. -hdisplay this help text -s variable specify variable to be changed use -s VAR=VALUE to avoid prompting for value -u username set username for command authentication -p password set password for command authentication ups UPS identifier - upsname[@hostname[:port]] Call without -s to show all possible read/write variables. -- Victor Porton - http://portonvictor.org ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Do I need to configure times and percents?
On Dec 1, 2014, at 9:19 AM, Victor Porton por...@narod.ru wrote: 01.12.2014, 14:50, Charles Lepple clep...@gmail.com: Does upsrw -l advice show anything? $ upsrw -l advice upsrw: invalid option -- 'l' I suppose I should read the documentation every once in a while :-) upsrw advice I was thinking of upscmd -l advice. -- Charles Lepple clepple@gmail ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Do I need to configure times and percents?
01.12.2014, 16:27, Charles Lepple clep...@gmail.com: On Dec 1, 2014, at 9:19 AM, Victor Porton por...@narod.ru wrote: 01.12.2014, 14:50, Charles Lepple clep...@gmail.com: Does upsrw -l advice show anything? $ upsrw -l advice upsrw: invalid option -- 'l' I suppose I should read the documentation every once in a while :-) upsrw advice upsrw advice outputs nothing. I was thinking of upscmd -l advice. -- Victor Porton - http://portonvictor.org ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
[Nut-upsuser] puzzle, need magic incantation
Hi Charles; I had nut working from before, but managed to lock up something and had to reboot. Nut is in the stuff to start at boot time, but is not now capable to being restarted with the nut script in /etc/init.d, claiming it is disabled: gene@coyote:/usr/src/nut-2.7.2/docs/man$ sudo service nut start * nut disabled, please adjust the configuration to your needs * Then set MODE to a suitable value in /usr/local/ups/etc/nut/nut.conf to enable it gene@coyote:/usr/src/nut-2.7.2/docs/man$ service nut start * nut disabled, please adjust the configuration to your needs * Then set MODE to a suitable value in /usr/local/ups/etc/nut/nut.conf to enable it So I look at that file and see it has only one active line: mode=standalone So where do I go from here? Minor rant: FWIW, before I asked, I redid the nut ./configure --with-doc=auto, then a make. Then I step into the docs directory and do a sudo make install, which it appears to do. But no manpages were install despite the command line echo showing that they were when I did the sudo make install, but I am forced to go into the docs directory and a man ./name-of-man-page to read it, and mode is only mentioned briefly in the example line which shows mode=none. That is a 10-33 torr suckage. This I think can be alleviated by setting up the env variable MANPATH, which is not apparently configured. Export that and it works. So put it in my .bashrc But since every other manpage on the system works without that env setting of $MANPATH, showing /usr/local/ups/share/man:/usr/share/man when queried now, why should i have to do it for nuts man pages? Boggles the mind. End minor rant. And I still cannot start it, see above. The error msg says its disabled, but not why, so I've exactly no clue what is really wrong. Cheers, Gene Heskett -- There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order. -Ed Howdershelt (Author) Genes Web page http://geneslinuxbox.net:6309/gene US V Castleman, SCOTUS, Mar 2014 is grounds for Impeaching SCOTUS ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] 06da:0002 Phoenixtec Power Co., Ltd UPS
Hi Charles. Thanks for your reply. I have no idea about the original software, this UPS has never been working and nobody knows about it. I test with blazer_usb with no success, but I will try to get that nutdrv_qx, it is not in my Debian Wheezy distribution of Nut. I will take in acount to reset with power off in case commands goes wrong. Regards. -- Jose Angel Navarro Cortes email: j...@telefonica.net web: http://janc.es/ Usuario Linux: #49178 El 14.12.01 08:04:05 Charles Lepple dijo: On Dec 1, 2014, at 3:00 AM, j...@telefonica.net wrote: I have a very nice working ups from: CENER ref: Active 1000VA 230V 12 CENER and front logo LA 900 Do you know what software was originally recommended for the UPS? Unfortunately, Phoenixtec seems to have made a lot of different USB-to-serial adapters. The most likely driver is blazer_usb (or nutdrv_qx, which is newer). You may need to shut down the UPS completely (turn power off, and unplug) if the other drivers have sent commands that put the UPS into a bad state. -- Charles Lepple clepple@gmail ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] puzzle, need magic incantation (nut.conf)
On Dec 1, 2014, at 9:43 AM, Gene Heskett ghesk...@wdtv.com wrote: Hi Charles; I had nut working from before, but managed to lock up something and had to reboot. Nut is in the stuff to start at boot time, but is not now capable to being restarted with the nut script in /etc/init.d, claiming it is disabled: gene@coyote:/usr/src/nut-2.7.2/docs/man$ sudo service nut start * nut disabled, please adjust the configuration to your needs * Then set MODE to a suitable value in /usr/local/ups/etc/nut/nut.conf to enable it gene@coyote:/usr/src/nut-2.7.2/docs/man$ service nut start * nut disabled, please adjust the configuration to your needs * Then set MODE to a suitable value in /usr/local/ups/etc/nut/nut.conf to enable it So I look at that file and see it has only one active line: mode=standalone Hi Gene, Is the MODE token capitalized? (The nut.conf file is included in the startup shell script, which is case-sensitive.) Here is the original nut.conf with its comments: https://github.com/networkupstools/nut/blob/587d5f828c03d961f0cbeb11c6a19a7944ec6ccd/conf/nut.conf.sample -- Charles Lepple clepple@gmail ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] puzzle, need magic incantation (man pages)
On Dec 1, 2014, at 9:43 AM, Gene Heskett ghesk...@wdtv.com wrote: FWIW, before I asked, I redid the nut ./configure --with-doc=auto, then a make. Then I step into the docs directory and do a sudo make install, which it appears to do. But no manpages were install despite the command line echo showing that they were when I did the sudo make install, but I am forced to go into the docs directory and a man ./name-of-man-page to read it, and mode is only mentioned briefly in the example line which shows mode=none. That is a 10-33 torr suckage. I think that other link I sent to the sample nut.conf has all of the possible values there - not sure what happened to those comments in your original file. This I think can be alleviated by setting up the env variable MANPATH, which is not apparently configured. Export that and it works. So put it in my .bashrc But since every other manpage on the system works without that env setting of $MANPATH, showing /usr/local/ups/share/man:/usr/share/man when queried now, why should i have to do it for nuts man pages? Boggles the mind. If you run ./configure without passing, say, --prefix=/usr/local, it will default to --prefix=/usr/local/ups which has the advantage of putting everything in one directory. To clean up, you just delete /usr/local/ups. Cleaning up after a botched install to /usr/local is painful, either involving backups, or surgically removing files from bin/, sbin/, etc/, man/man?/, etc. -- Charles Lepple clepple@gmail ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] nut and Tripp Lite smart500rt1u on Scientific Linux 7
On Nov 29, 2014, at 5:01 PM, Matthew Sund matts...@yahoo.com wrote: I installed nut from the epel repository on Scientific Linux 7. I would like to get my smart500rt1u working, but # upsc smart500@localhost gives the following output: battery.voltage.nominal: 0 device.mfr: Tripp Lite device.model: SMART500RT1U device.type: ups driver.name: tripplite_usb ... ups.firmware.aux: protocol 3005 Support for protocol 3005 was not added until this summer, and we have not yet released a version of NUT which includes this. However, depending on how easy it is to rebuild packages in Scientific Linux, you may be able to download a snapshot of NUT (labeled 2.7.2.5, but that is just a placeholder version number for the autobuilder) and rebuild. When you say epel repository, is it the same as for RHEL/Fedora? Theoretically, you should be able to download the SRPM from here: https://dl.fedoraproject.org/pub/epel/7/SRPMS/n/ install to /usr/src (or something) and rebuild with a NUT snapshot: http://buildbot.networkupstools.org/snapshots If you have questions, let us know - I'm sure there are other users of RPM-based distributions on the list. -- Charles Lepple clepple@gmail ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] puzzle, need magic incantation (nut.conf)
On Monday 01 December 2014 20:35:15 Charles Lepple did opine And Gene did reply: On Dec 1, 2014, at 9:43 AM, Gene Heskett ghesk...@wdtv.com wrote: Hi Charles; I had nut working from before, but managed to lock up something and had to reboot. Nut is in the stuff to start at boot time, but is not now capable to being restarted with the nut script in /etc/init.d, claiming it is disabled: gene@coyote:/usr/src/nut-2.7.2/docs/man$ sudo service nut start * nut disabled, please adjust the configuration to your needs * Then set MODE to a suitable value in /usr/local/ups/etc/nut/nut.conf to enable it gene@coyote:/usr/src/nut-2.7.2/docs/man$ service nut start * nut disabled, please adjust the configuration to your needs * Then set MODE to a suitable value in /usr/local/ups/etc/nut/nut.conf to enable it So I look at that file and see it has only one active line: mode=standalone Hi Gene, Is the MODE token capitalized? Yes. The one in /usr/local/ups/etc is the only one it can find Copy/paste: MODE=standalone Aha! The paths in the /etc/init.d/nut script were wrong. Fixed that up and a sudo service nut restart seems to have fired it right up. Except that /usr/local/ups/bin/upsc myups is connection refused. And it is not visible in htop. Next? Thank you Charles (The nut.conf file is included in the startup shell script, which is case-sensitive.) Here is the original nut.conf with its comments: https://github.com/networkupstools/nut/blob/587d5f828c03d961f0cbeb11c6a 19a7944ec6ccd/conf/nut.conf.sample Cheers, Gene Heskett -- There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order. -Ed Howdershelt (Author) Genes Web page http://geneslinuxbox.net:6309/gene US V Castleman, SCOTUS, Mar 2014 is grounds for Impeaching SCOTUS ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] puzzle, need magic incantation (man pages)
On Monday 01 December 2014 20:43:37 Charles Lepple did opine And Gene did reply: On Dec 1, 2014, at 9:43 AM, Gene Heskett ghesk...@wdtv.com wrote: FWIW, before I asked, I redid the nut ./configure --with-doc=auto, then a make. Then I step into the docs directory and do a sudo make install, which it appears to do. But no manpages were install despite the command line echo showing that they were when I did the sudo make install, but I am forced to go into the docs directory and a man ./name-of-man-page to read it, and mode is only mentioned briefly in the example line which shows mode=none. That is a 10-33 torr suckage. I think that other link I sent to the sample nut.conf has all of the possible values there - not sure what happened to those comments in your original file. This I think can be alleviated by setting up the env variable MANPATH, which is not apparently configured. Export that and it works. So put it in my .bashrc But since every other manpage on the system works without that env setting of $MANPATH, showing /usr/local/ups/share/man:/usr/share/man when queried now, why should i have to do it for nuts man pages? Boggles the mind. If you run ./configure without passing, say, --prefix=/usr/local, it will default to --prefix=/usr/local/ups which has the advantage of putting everything in one directory. To clean up, you just delete /usr/local/ups. Cleaning up after a botched install to /usr/local is painful, either involving backups, or surgically removing files from bin/, sbin/, etc/, man/man?/, etc. BTDT, not fun. Thanks Charles Cheers, Gene Heskett -- There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order. -Ed Howdershelt (Author) Genes Web page http://geneslinuxbox.net:6309/gene US V Castleman, SCOTUS, Mar 2014 is grounds for Impeaching SCOTUS ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
