Re: [Nut-upsuser] Air Media
tisdag 28 juni 2016 kl. 13:40:30 CEST skrev Ove Airmedia: > Hej Kjell, Hej Ove > Jag hade tappat bort dig bland dokumenten. > Vill du fortfarande ha produkterna du beställt? > Jo det vill jag. De behövs till min Multiplex Heron. Har pengarna kommit in på ditt konto? Jag var inte säker så jag kollade med min bank, så de skulle se om det kommit rätt. När kommer den nya sändaren ut till försäljning? Funkar ditt paypal nu? Med vänliga hälsningar Kjell Claesson ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Not getting nut to work with Eaton 5115
On Friday 22 January 2016 21.35.16 Magnus Karlsson wrote:
Hi Magnus,
> Following the instructions a following site I can not get nut to work with
> my UPS.
>
OK.
> http://bernaerts.dyndns.org/linux/75-debian/335-debian-wheezy-install-monito
> r-eaton-ups
>
> Hope that you can find out what is wrong by the provided info in the email
>
8<snip-
> # lsusb -s 001:005 -v
>
> Bus 001 Device 005: ID 06da:0002 Phoenixtec Power Co., Ltd UPS
> Device Descriptor:
> bLength18
> bDescriptorType 1
> bcdUSB 1.10
> bDeviceClass0 (Defined at Interface level)
> bDeviceSubClass 0
> bDeviceProtocol 0
> bMaxPacketSize0 8
> idVendor 0x06da Phoenixtec Power Co., Ltd
> idProduct 0x0002 UPS
> bcdDevice1.00
> iManufacturer 4 Powerware
> iProduct 24 Powerware UPS
> iSerial 0
> bNumConfigurations 1
> Configuration Descriptor:
8<snip-
Yes this is the first 5115 model that uses a type of serial over usb.
You need to use the bcmxcp_usb driver for this one.
Add bcmxcp_usb to your ups.conf and test.
>
> /etc/udev/rules.d/90-nut-ups.rules
>
> # Eaton 5115
> ACTION=="add", SUBSYSTEM=="usb", ATTR{idVendor}=="06da",
> ATTR{idProduct}=="0002", MODE="0660", GROUP="nut"
>
>
>
>
> Issuing command
> root@laptux:~# upsdrvctl start
> Network UPS Tools - UPS driver controller 2.6.4
> Network UPS Tools - Generic HID driver 0.37 (2.6.4)
> USB communication driver 0.32
> This Liebert device (06da:0002) is not (or perhaps not yet) supported
> by usbhid-ups. Please make sure you have an up-to-date version of NUT. If
> this does not fix the problem, try running the driver with the
> '-x productid=0002' option. Please report your results to the NUT user's
> mailing list <nut-upsuser@lists.alioth.debian.org>.
>
So it's not a hid ups.
Regards
Kjell Claesson
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] interrupt pipe disabled
tisdagen den 16 december 2014 15.36.29 skrev Frantz de Germain: Hello, Hi Frantz, I'm testing an APC SMT3000RMI2U connected to an USB port with Nut 2.7.2. I've got the message : interrupt pipe disabled (add 'pollonly' flag to 'ups.conf' to get rid of this message) I've been looking for pollonly in the usbhid-ups man page, but it didn't help me. Only add pollonly to your ups.conf ex: [APC] driver = usbhid-ups port = auto pollonly vendorid = Could someone explain me what does this means exactly ? What are these interrupts ? What exactly may not work ? It depends on the implementation of the usb driver used. And it would not listen to the interrupt pipe. So actualy nothing works like it should. /Kjell ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] upsrw doesn't set variable
lördagen den 29 juni 2013 11.28.14 skrev Mike.: 8--snip- Hi Mike, Thanks for the quick reply. I checked the log file (which, admittedly, I should have done before I posted about the problem :) ). Here's the command and the corresponding log message: # upsrw -u au -p ap -s outlet.1.delay.shutdown=12 PW5125@localhost OK bcmxcp[90004]: Set [outlet.1.delay.shutdown 12] failed due to invalid parameter Yep the ups is telling that the command has an invalid parameter. Have to check if there is any difference between the 5125 and others. Curious that the command gives an OK response, even though it logs a failure. The OK kome from upsrw, as the driver is accepting the command. I'll try the -D flags when I have some time, maybe this evening. btw, how many is a few -D flags? fwiw, I don't have a USB port on the UPS, just serial. Thanks. //Kjell ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] upsrw doesn't set variable
lördagen den 29 juni 2013 15.22.44 skrev Mike.: 8-snip- Sorry for the delay. Here is the console output of bcmxcp with -DDD specified: [snip] 13.721204 Auto delay on: 2 13.721243 send_command: (4 bytes) = ab 01 35 1f 13.821127 send_command: (4 bytes) = ab 01 33 21 13.920982 send_command: (4 bytes) = ab 01 3b 19 14.033202 Battery Status: (21 bytes) = 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 14.033249 00 00 00 00 01 03 14.033275 Battery Status = No test initiated (0) Up to this point it is only asking for status and outlets etc. 14.261271 entering setvar(outlet.1.delay.shutdown, 12) 14.261318 send_command: (7 bytes) = ab 04 cf 69 e8 d5 5c This is a authorization block that enable us to send a command. 16.261647 send_command: (8 bytes) = ab 05 97 01 01 0c 00 ab This is the command. ab = start of block 05 = length of data 97 = Set Outlet Parameter 01 = Set Automatic Off Delay of outlet xx 01 = this is the outlet xx 0c = LSB of seconds = 12 00 = MSB of seconds = 00 so it reads 0012 sec. ab = Checksum 16.318194 Set [outlet.1.delay.shutdown 12] failed due to invalid parameter Now the ups is telling you that the command is accepted, but parameter 01 is not valid for this command. Try setting the ON DELAY 2 then it is OK. I have the same ups here, and it looks like the possibility to set off delay is not implemented on this type. 16.318245 send_command: (4 bytes) = ab 01 34 20 16.574540 send_command: (4 bytes) = ab 01 41 13 This is command to read outlet blocks. 16.658312 init_outlet(14), res=14 16.658346 Number of outlets: 2 16.658358 Number of bytes: 6 16.658369 Outlet number: 1 8---snip The problem is that I had a crash on my backup ;-( so I lost the paper on the specific commands for 5125. So if someone have the command specifications on pw5125, can you check if this is the case for the 5125 that it is impossible to set auto off delay. Regards Kjell Claesson Co author of the bcmxcp driver. ___ 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 with Powerware 5125.
torsdagen den 21 februari 2013 14.39.10 skrev Daniel Lopes de Carvalho: Hi, Hi Daniel Does anyone know how to make NUT works with Powerware 5125? I already tried serial communication (genericups and bcmxcp) and USB (usbhid-ups and bcmxcp_usb), but without success. Do you have serial or usb connection on the ups? I run a 5125 on serial with bcmxcp driver. Short start of output. #upsc pw5125 ambient.temperature: 28 ambient.temperature.high: 70 battery.charge: 99 battery.runtime: 2060 battery.voltage: 27.07 device.mfr: Eaton device.model: PW5125 1000i device.serial: GB device.type: ups driver.name: bcmxcp driver.parameter.baud_rate: 9600 driver.parameter.pollinterval: 2 driver.parameter.port: /dev/ttyS1 driver.parameter.shutdown_delay: 10 driver.version: 2.6.5-Unversioned directory driver.version.internal: 0.26 input.frequency: 49.65 and so on. Regards Kjell ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Powerware 5125 (USB) under Debian Squeeze.
On Wednesday 21 November 2012 13.49.35 Daniel Lopes de Carvalho wrote: Hi Kjell, thanks for your answer. OK We bought this UPS in the end of 2011. The model is: Powerware 5125 Rack-Mount UPS 5000/6000 VA. That is new. I tried setting the usbhid-ups, but without success. OK [Ups01] driver = usbhid-ups port = / dev/bus/usb/002/003 desc = Powerware 5125 Try the bcmxcp_usb and change the ups.conf to: [Ups01] driver = bcmxcp_usb port = auto desc = Powerware 5125 Run it as: /usr/lib/bcmxcp_usb -DD -a Ups01 2.295039 Checking device (0592/0002) (002/004) 2.306139 - VendorID: 0592 2.306150 - ProductID: 0002 2.306155 - Manufacturer: Powerware 2.306160 - Product: USB UPS 2.306164 - Serial Number: unknown 2.306169 - Bus: 002 Trying to match device 2.306173 2.306180 Device does not match - skipping 2.306189 Checking device (0592/0002) (002/003) 2.685186 - VendorID: 0592 2.685199 - ProductID: 0002 2.685204 - Manufacturer: Powerware 2.685208 - Product: USB UPS 2.685213 - Serial Number: GE143A0741 2.685218 - Bus: 002 The vendor/product id is the same for the bcmxcp_usb capable ups. Looks like it reconnected on the bus as you have two instants of it. /Kjell ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Powerware 5125 (USB) under Debian Squeeze.
On Wednesday 21 November 2012 12.31.41 Daniel Lopes de Carvalho wrote: Hi. Hi Daniel, I'm looking for a way to configure an Eaton Powerware 5125 under Debian Squeeze (amd64) with USB port. How old is the ups? I use a 5125 but it has only serial (or snmp). If this usb card is new, it may talk 'usbhid-ups'. Can someone help me? So you can try the usbhid-ups driver. You should also upgrade to a more resent version of nut. (Can not remember if the usbhid-ups existed in 2.4.3, think it was called newhidups then and did not support all ups'es. Regards /Kjell ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] bcmxcp_usb can not communicate with Eaton Powerware 5110
söndagen den 15 juli 2012 16.59.56 skrev Greg Vickers: Hi Greg, On 13/07/12 22:24, Charles Lepple wrote: On Jul 13, 2012, at 12:41 AM, Greg Vickers wrote: 0.238682get_answer: (128 bytes) = ab 01 79 01 02 50 00 50 01 00 0e 00 01 00 10 50 0.239445 4f 57 45 52 57 41 52 45 20 55 50 53 20 20 20 5c 00 00 00 00 00 00 00 00 00 0.240107 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 51 51 00 00 00 00 51 0.240351 00 00 00 00 00 00 00 f0 00 f0 00 00 00 f0 00 00 00 00 00 00 00 00 f0 00 00 0.240558 00 00 00 00 00 00 51 00 00 51 00 00 00 00 00 00 00 00 00 f0 00 00 00 00 00 0.241334 00 00 00 00 00 00 00 f0 18 3b ab 01 0.241969get_answer: block_number = 1 0.242121get_answer: sequence number (1) is ok 0.242254get_answer: checksum is ok 0.242891get_answer: block_number = 1 0.243072Communications with UPS lost: get_answer: not the right sequence received 0!!! Well, that's odd. Yep that's odd. If it would be the last sequence the sequence-number should read 82. The sequence is numbered in ascending order and on the last sequence the msb is set to 1. (1010 = 82 Hex) I'm not an expert on this driver, but a quick read of that portion of the code implies that this shouldn't happen. The last line says the received sequence number is 0. I think the sequence number is the 4th byte (my_buf[3]), which is 1 in the hex dump you posted: 8-snip Yep Charles is right. The problem with the 5110 is that it was one of the first that was equipped with usb. This implementation is not following the usb criteria. That is why there is difference between this and later ups'es. Look at: http://trac.networkupstools.org/projects/nut/browser/trunk/drivers/bcmxcp_usb.c#L49 And the difference in line 59 for the phonitextec interface that the 5110 use. I have backed off a bit from the development, and I don't have any early Powerware to test the driver. But I know that Arnaud made some changes around the problem with the 5110. Regards Kjell Claesson ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Debian Squeeze / Powerware 9135 450KVA UPS
torsdagen den 12 januari 2012 15.30.02 skrev Gregory Skelton: Hi, Hi Gregory, I have more information, I did some more digging and found a debugging mode for the driver.. So this what I'm seeing. Any ideas how I get around the PW_COMMAND_START_BYTE? Thanks for any help. Greg Have made the mail a little shorter. By the way you should get the same output with only 2 D. ./bcmxcp -a powerware -DD -i 5 -x baud_rate=9600 But now to the problem 8--snip 1.156360 Length of Config_block: 48 1.156366 Length of statistics map: 62 1.156371 Length of command list: 4047 1.156375 Length of outlet_block: 33650 This is not normal every output should have length 8, so you should have 33650/8 = 4206.25 outlets. 1.156380 Length of alarm_block: 34179 And this make the error. Because the driver set up the outlets now. Do you have a firmware before Rev: AE ? 2.157495 Receive error (PW_COMMAND_START_BYTE): 0!!! 3.158599 Receive error (PW_COMMAND_START_BYTE): 0!!! 4.159701 Receive error (PW_COMMAND_START_BYTE): 0!!! 4.159712 Communications with UPS lost: Error executing command 4.159717 Could not communicate with the ups /snip This may be fixable by reading the firmware revision and skip this setup of outlet blocks. Regards Kjell ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] beginner questions about AEC Star T4110
On Thursday 11 August 2011 10.55.39 Gémes Géza wrote: Hi, Hi Géza. I've got an AEC Star T4110 connected with an RS232 port by a megatec cable. On the list of supported devices (http://www.networkupstools.org/stable-hcl.html) there is only one AEC device, so I tried genericups with upstype=21. The problem is, that the UPS (while being on-line) reports constantly being on battery. # upsc aec ups.status OB The only thing I could found on AEC T4(110), that it is a RS232 and have 'dry contact' and 'SNMP' as option. And as it is a online ups and at least 10KVA, I think it has some intelligent communication. So I don't think it is a working on the generic driver. If you don't have the 'dry contact' option installed. My question is: What is the recommended procedure to debug this (what parameters try to change in what order)? About the system: Ubuntu 10.04 (kernel 2.6.32-33-generic) NUT: 2.4.3-1ubuntu3.1 I think it talks some megatec protocol. So if you can upgrade to a new NUT and test the 'blazer_ser' driver. Or the megatec driver in 2.4. Run it in debug mode. Locate where you have the ups driver. Then do /path/to/megatec -DD -a myups Where myups is the tag in the ups.conf [myups] driver=megatec port= /dev/ttyS0 (end by CTRL+c) Cheers /Kjell ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] beginner questions about AEC Star T4110
On Thursday 11 August 2011 15.37.09 Gémes Géza wrote: Thank you for your help. Unfortunately it isn't working. OK. I have nut version 2.4.3-1ubuntu3.1 , so have tried the megatec driver: [aec] driver=megatec port= /dev/ttyS0 The output of # /lib/nut/megatec -DD -a aec is: Network UPS Tools - Megatec protocol driver 1.6 (2.4.3) 0.00send_to_all: SETINFO driver.parameter.port /dev/ttyS0 0.000111debug level is '14' 0.001356DTR=1, RTS=0 0.001404send_to_all: SETINFO device.type ups 0.001424send_to_all: SETINFO driver.version 2.4.3 0.001450send_to_all: SETINFO driver.version.internal 1.6 0.001470send_to_all: SETINFO driver.name megatec 0.001485Starting UPS detection process... 0.001505Asking for UPS information [I]... 2.503689I = FAILED [timeout] Well you could try out some of the other drivers like belkin and blazer. Se if you get any answer from the ups. /Kjell ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Is eaton 5115 UPS compatible with NUT
Hi. Hi Daniel, I'm using ubuntu 10.04 and I'm in the process of buying a ups. This is it (eaton 5115 ups) with usb interface http://powerquality.eaton.com/05146561-5591.aspx?CX=3 I had a look at the ups compatibility chart here: http://www.networkupstools.org/stable-hcl.html But I can't find this particular ups listed. You have to look at Powerware for that one. This is a model before Eaton marked there series. And yes it is compatible with the bcmxcp_usb driver. I plan to use NUT v. 2.4.3 that I can get from the repositories. Try to get a new version. I think Ubuntu have the latest. I had a look at the manpage for the bcmxcp_usb and usbhid-ups driver http://www.networkupstools.org/docs/man/bcmxcp_usb.html http://www.networkupstools.org/docs/man/usbhid-ups.html According to the manpage, usbhid-ups should support the newer Eaton USB models Yes but not this one. So my question is, will this driver work with this ups? No, you will need to use the bcmxcp-usb driver. I have to know before purchasing. Thanks. Lycka till med ups'en. Regards Kjell ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Can't get iDowell to work
Hi, PS. What is the meaning of: battery.capacity: 0.03 ? This is a mapping problem. The UPS is reporting 100% battery capacity is available and I mistakenly mapped this to the battery capacity (Ah) value. I will remove this later on. Kewl! This is already done in the trunk by Arnaud. So 'emerge nut-svn' and it would be fixed. Kjell ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Can't get iDowell to work
OK On Monday 03 January 2011 20:40:17 Arjen de Korte wrote: Citeren Kjell Claesson kjell.claes...@epost.tidanet.se: So start to send the output of: lsusb -v Cut out the part about the ups, and we have a look on it. Make that lsusb -v -d 075d:0300 to save yourself the trouble of weeding out the interesting stuff from the other USB devices (we already know the VID:PID combination from the udev rule you created). Make sure to run this as root, so that we have a chance of capturing the report descriptor of this device. Best regards, Arjen Thanks Arjen :-) Here you go guys: # lsusb -v -d 075d:0300 The device class is not HID, but you can try this. Do a ups.conf like this. [iDowell] driver = usbhid-ups port = auto vendorid = 075d productid = 0300 desc = iBox by iDowell Now run it like this: /lib/nut/usbhisd-ups -DD -a iDowell -u root Kjell ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] help with CyberPower 425HG
Hi James, $ sudo upsdrvctl start Network UPS Tools - UPS driver controller 2.4.3 Network UPS Tools - Generic HID driver 0.34 (2.4.3) USB communication driver 0.31 Using subdriver: CyberPower HID 0.3 OK, the driver seems to start. But have you started the daemon (upsd)? $ sudo upsc my...@localhost Error: Driver not connected Then you have to start the upsmon to monitor the ups. - Check with: ps xau |grep nut nut 5324 0.0 0.0 12428 508 ?Ss 09:41 0:00 /lib/nut/bcmxcp -a pw5115 nut 5348 0.0 0.0 40528 864 ?Ss 09:41 0:00 /usr/sbin/upsd nut 5367 0.0 0.0 40496 1148 ?S09:41 0:00 /usr/sbin/upsmon - You may also do: ps xau |grep ups Then you see that upsmon have two instants. One as nut and one as root. Regards Kjell ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Again me :)
Hi Vladimir, Dears, I finally resolve my problem, I just make symbolic link: [t...@box var/run/]# ln -s -T /var/state/ups/ nut Now I finally got services online: # /sbin/service ups start Starting UPS driver controller:[ OK ] Starting upsd: [ OK ] Starting UPS monitor (master): [ OK ] 8snip- ups.mfr: unknown ups.model: unknown ups.serial: unknown ups.status: OL ups.temperature: 25.0 This may due to that it is not responding to the info comand (I/cr). You can test it like this. /path/to/blazer_usb -DD -a mustek -u root If you get any 'short reply' or 'invalid start character'. The mfr model and serial is from the same function. I use megatec_usb driver and try with blazer_usb and same situation, I don`t got ups.model/serial/mfr. On shutdown (when battery is low), my ups shutdown strange, got off all led and when I put power again, I must press power button to turn off ups and press it again, to get the power. What do you think what is the problem?! What happens if you wait. Some ups'es need to have a serten charge level to start. This to manage a power-out after power on. If it starts direct, and the battery is empty, it would shut off before a safe powerdown. Regards Kjell ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Again me :)
OK, This is out from blazer_usb -DD -a mustek -u root : http://pastebin.com/63QHfdU0 1.606976 blazer_vendor: short reply 1.607091 Vendor information read 1 failed 2.612971 blazer_vendor: short reply 2.613078 Vendor information read 2 failed 3.618972 blazer_vendor: short reply 3.619077 Vendor information read 3 failed 3.619168 Vendor information unavailable Yep this tell me that it don't support that command. Maybe your ups is using another command for this. Maybe Arjen have something on this. The funny thing is when I eject power cord from ups and back in, my fuse from electricity goes down! :) and same UPS with same connection when I put on pc which is on windows, everything is ok. Battery level is low, pc go down and on power back, ups start again and pc (because I put in bios on power back, to turn on). It may be the same here. The command to shut down the ups is 'shutdown power off' instead of 'shutdown return on power' Do you have any ondelay=1 in your ups.conf? Because the command is the same for power off stay off and power off return. The difference is that return need a power on delay. It looks like this. S1R0 (off delay 1 and ondelay 0. Then it stay off.) S1R1(off delay 1 and ondelay 1. It return in one minute.) Check the man page for the blazer ups. Regards Kjell ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] HP R3000 XR (BCMXCP) serial connection problem: e7!!! and e2!!!
Hi Robert, UPS: HP R3000 XR with HP UPS Management Module What I Want: I just want the UPS to shut down the client called tor before the UPS power drains out, I'd prefer to use a direct serial cable instead of network, in case the network doesn't work. I'll manage the UPS trough the ethernet using the built-in HTTP webinterface in the HP UPS Management Module. I've created a DB9-RJ45 cable according to the spec (called -RJ-45 Serial 1-5 (5-Port)) released by Brian Vo in this forumthread: http://forums11.itrc.hp.com/service/forums/questionanswer.do?admit=10944762 6+1277983799644+28353475threadId=1320596 So this is how my cable look like now: DB9-3 --- RJ45-4 DB9-2 --- RJ45-5 DB9-5 --- RJ45-6 This does not look right. The pin 4 on the RJ45 is output ( o/p ) and should be connected to the rx pin on the DB9 that is number 2. So it looks like you have to switch rx tx data. This cable is connected between port2 on the HP UPS Management Module, and the onboard DB9 connector on a server running Ubuntu 10.04 and NUT 2.4.3 In the HP UPS Management Module, I've set up a client called tor in load1, and assigned serial port2 to it with a shutdown time of 2 minutes. This is my nut configuration in /etc/nut/ups.conf : [aasgaard] driver = bcmxcp port = /dev/ttyS0 This is OK. But when it has given you the speed it connect with, you can add the baud_rate to the config also for a quicker startup. This is what happens when i try to start the driver: ---START--- rob...@tor:~$ sudo upsdrvctl start Attempting to autodect baudrate This you get because of the missing baud_rate Communications with UPS lost: Receive error (Requested only mode command): e7!!! In the init it sends a 'Requested only mode' command to the ups. This is not handled by the ups. No respons from the ups. The command is 0xA0 so this is not communicating at all. Communications with UPS lost: Receive error (Requested only mode command): e2!!! Same as before. Can't connect to the UPS on port /dev/ttyS0! After it has checked all the baudrates it can not connect. Driver failed to start (exit status=1) ---STOP--- I've also tried replacing this cable with a regular ethernet cable, and the original HP 432734-001 (AF401A) RJ45-DB9 adapter, this is the result I get: ---START--- rob...@tor:~$ sudo upsdrvctl start Network UPS Tools - UPS driver controller 2.4.3 Network UPS Tools - BCMXCP UPS driver 0.23 (2.4.3) RS-232 communication subdriver 0.17 Attempting to autodect baudrate Can't connect to the UPS on port /dev/ttyS0! Driver failed to start (exit status=1) ---STOP--- Can anyone in any way help me toward making this work? Try to switch the rx/tx line. Or messure the signal with a voltmeter. Regards Kjell Claesson ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] amacrox ap1000 problems
Ok guys I get this errors: Hi, Network UPS Tools – UPS driver controller 2.4.1 Network UPS Tools – Generic HID driver 0.34 (2.4.1) USB communication driver 0.31 No matching HID UPS found my ups.conf is: [ap1000] driver = usbhid-ups port = auto I’ve also tried to set a specific usb port and change driver. My ups is a AMACROX 1000 http://www.amacrox.com//english/01_product/02_01detail.aspx?pdid=46 and it should be the following usb device lsusb -D /dev/bus/usb/008/003 Device: ID 0665:5161 Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass 0 (Defined at Interface level) This line tell us that it's not a HID device. bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0×0665 idProduct 0×5161 bcdDevice 0.02 iManufacturer 1 Cypress Semiconductor iProduct 2 USB to Serial iSerial 0 And this that it have a serial to usb converter. bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 34 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 3 bmAttributes 0×80 (Bus Powered) MaxPower 100mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 3 Human Interface Device This is not true. Almost all say this but is it there proprietary protocol. It does not follow the hid protocol. bInterfaceSubClass 0 No Subclass bInterfaceProtocol 0 None iInterface 4 Sample HID ** UNRECOGNIZED: 09 21 00 01 00 01 22 1b 00 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0×81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0×0008 1x 8 bytes bInterval 32 Device Status: 0× (Bus Powered) I would go for megatec_usb driver Regards /Kjell . ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Old fashion UPS monitoring
Hello! Hello, I have a box that monitors the surrounding environment and sends a signal to a debian machine when it is time to shut down, according to the developers of the box it uses and old standard of UPS signaling. It is super simple, it just changes the DCD status to high when it is time to shut down. Has anybody heard of this kind of signaling, i have googled without success. But maybe someone on this list can help me sort thit out? Yes, this is sometimes called contact-closure. NUT have a driver named 'genericups' for this. Many ups'es use this. The may have a 'smart' protocol that gives some info like load and voltage, but also a contact-closure setup. If you read the man page for the genericups you get a hint how to set this up. /Kjell ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] communications lost/established
Hi ricman, 8snip send: D read: timeout blazer_status: short reply Status read 3 failed No supported UPS detected Network UPS Tools - Megatec/Q1 protocol serial driver 1.51 (2.4.1) where am i wrong? 1. Your ups.conf ? 2. What command did you use for debug ? ex: /path/to/driver -a ups -u root 3. The user and group of the serial port ? ex: crw-rw 1 root uucp 4, 64 18 mar 22.37 /dev/ttyS0 4. Is the user you run NUT as, a member of the group for the port? /Kjell ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] HP R1500 G2 UPS
Hi, Citeren Jon Bendtsen jbendt...@laerdal.dk: I have a R3000XR, and i use bcmxcp using a seriel port out, since i can not find a USB port on the UPS. I do have a USB2serial on the host. I still experience that NUT upsstats.cgi says the UPS battery is at 97%, and some days later at 100%. It happens regularly. The bcmxcp driver reports directly what the UPS is telling us. If the algorithm used for battery charge calculation is voltage based (not entirely unlikely), small variations in the battery voltage may make it jump between two fixed values all the time. I have a very strong opinion about 'correcting' such behavior, since it can also be an indication of imminent battery failure. Totally agree with Arjen. When on line it is more of a voltage reading. And set the cell voltage to about 2.26 when on 100%. But it is not a direct voltage reading. It depends on where it land, when it change to floating. For example: If I do a battery test, it drop to about 80% before end. Then it start charging. But the % don't follow the voltage. I have 24 volt nominal so it is on 95% from about 26.5 to 27.3. Then when it goes to floating it drop to about 27.07 and say 99%. If it drop much when floating you get a low % reading, and as Arjen say it may indicate a bad cell. ( I know as I experienced that). BUT when it change to battery, the meter indicate remaining runtime in %. So start fixing this would make more damage than help. This is calculated during battery test. So if you have strange or large run-time numbers, do a battery test. (see page 115 of XCP Rev C.doc) /Kjell ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] XPCC XVRT-1000 driver
To Arjen.
Hi, do we have any active developer on the powercom driver.
It seems to support the XPCC ups. The problem seems to be
the calculation of the voltage and ups.load.
This thread should give some info needed to make it work.
Anything to move to dev list?
/Kjell
OK Jeff,
Jeffrey B. Green wrote:
I'll go
ahead and build a version of 2.4.1 for lenny (backports doesn't seem to
have nut in it) to see what happens...
Okay. Built it (nut 2.4.1) and put it on the server. The only type that
works for that ups is BNT-other. When nut starts up it sees the ups on
battery, but fairly quickly changes that to online. For example, initially:
That was fast :-)
Now see what it gives.
The startup on battery is OK. The driver is doing a battery test at start.
Don't know why they do it, but there must be a reason for that.
If type is BNT, KIN or IMP they run this.
if (ser_send_char (upsfd, BATTERY_TEST) != 1) {
upslogx(LOG_NOTICE, writing error);
dstate_datastale();
return;
So it is type of detection of the right type.
% upsc xtreme
battery.charge: 85.0
driver.name: powercom
driver.parameter.linevoltage: 120
driver.parameter.manufacturer: XPCC
driver.parameter.modelname: XVRT-1000
driver.parameter.pollinterval: 2
driver.parameter.port: /dev/ttyS0
driver.parameter.type: BNT-other
driver.version: 2.4.1
driver.version.internal: 0.12
input.frequency: 60.09
input.voltage: 105.2
input.voltage.nominal: 120
output.frequency: 60.09
output.voltage: 18.2
ups.load: 14.5
ups.mfr: XPCC
ups.model: BNT-other-0AP
ups.model.type: BNT-other
ups.serial: Unknown
ups.status: OB TEST
Looks OK on frequency, but input and output voltage and load seems wrong.
Then within 5-10 seconds or so,
% upsc xtreme
battery.charge: 100.0
driver.name: powercom
driver.parameter.linevoltage: 120
driver.parameter.manufacturer: XPCC
driver.parameter.modelname: XVRT-1000
driver.parameter.pollinterval: 2
driver.parameter.port: /dev/ttyS0
driver.parameter.type: BNT-other
driver.version: 2.4.1
driver.version.internal: 0.12
input.frequency: 60.09
input.voltage: 103.6
input.voltage.nominal: 120
output.frequency: 60.09
output.voltage: 103.6
ups.load: 7.7
ups.mfr: XPCC
ups.model: BNT-other-0AP
ups.model.type: BNT-other
ups.serial: Unknown
ups.status: OL
The same here.
But the signaling seems OK, so it is usable for protection. But not for
reading any values from.
/Kjell
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] XPCC XVRT-1000 driver
OK Jeff, Kjell Claesson wrote: Then if you can check the speed on the port. The powercom driver is using 1200 b/s. % stty -F /dev/ttyS0 speed 1200 baud; line = 0; min = 0; time = 0; ignbrk -brkint -icrnl -imaxbel -opost -onlcr -isig -icanon -echo -echoe -echok -echoctl -echoke Disregard my string in the latest mail. This is not the powercom ups answer. I was on the wrong track. But the answer your ups is giving, looks like you have a powercom protocol. But it is not recognized by the driver. The default for the driver is Trust ups and it sends 11 bytes. Yours is sending 16. So check the manual page for the powercom driver, and check if you can make it talk to it. Problem is that it may use some odd calculations for the voltage and load and frequency. /Kjell ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] XPCC XVRT-1000 driver
Great Jeff, Jeffrey B. Green wrote: I'll experiment with the driver variable options, however, if you know the correct (or almost correct) settings, then that info would be greatly appreciated. No my baby is the bcmxcp driver, so my knowledge in the calculations done in the powercom driver is not so god. But I think you got close. Setting the line voltage variable to 120 produces: Yes the line voltage is used in calculation. % upsc xtreme battery.charge: 98.1 driver.name: powercom driver.parameter.linevoltage: 120 driver.parameter.pollinterval: 2 driver.parameter.port: /dev/ttyS0 driver.parameter.type: KIN1500AP driver.version: 2.2.2 driver.version.internal: $ Revision: 0.5 $ input.frequency: 59.53 input.voltage: 105.2 input.voltage.nominal: 120 output.frequency: 59.53 output.voltage: 105.2 ups.load: 9.9 ups.mfr: PowerCom ups.model: Unknown ups.model.type: KIN1500AP ups.serial: Unknown ups.status: OL This look close to the upsmon program. The only thing is the voltage that is low. Better have the dev's looking at this, as it have to be a new setting in the driver. But the most important part is the ups.status. Check if it go from OL (On Line) to OB (On Battery) when you remove the main's. The best way of doing this is by a circuit breaker on the line. So the ground connection would stay uninterrupted. Then you have to make a real test. Best is to load it with some light-bulbs as it is going to shut off. Have the communication to the computer and load it with the bulbs until it signals LB (Low Battery). Now check if it shutting down properly. /Kjell ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] XPCC XVRT-1000 driver
Jeff, The previous values were under load, which I forgot to mention. It has a ~500W server and 10W switch on it. Then the ups.load is low also. But you should not do the LB shutdown test with the server attached. It may power off without a warning. /Kjell ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] XPCC XVRT-1000 driver
OK. The readings just before the nut initiated server shutdown due to LB was: % upsc xtreme battery.charge: 47.9 driver.name: powercom driver.parameter.linevoltage: 120 driver.parameter.manufacturer: XPCC driver.parameter.modelname: XVRT-1000 driver.parameter.pollinterval: 2 driver.parameter.port: /dev/ttyS0 driver.parameter.type: KIN1500AP driver.version: 2.2.2 driver.version.internal: $ Revision: 0.5 $ input.frequency: 0.00 input.voltage: 0.0 input.voltage.nominal: 120 output.frequency: 59.53 output.voltage: 13.3 ups.load: 85.5 ups.mfr: XPCC ups.model: XVRT-1000 ups.model.type: KIN1500AP ups.serial: Unknown ups.status: FSD OB LB BOOST The battery.charge dropped in increments of 5.0. It started at: % upsc xtreme battery.charge: 146.9 driver.name: powercom driver.parameter.linevoltage: 120 driver.parameter.manufacturer: XPCC driver.parameter.modelname: XVRT-1000 driver.parameter.pollinterval: 2 driver.parameter.port: /dev/ttyS0 driver.parameter.type: KIN1500AP driver.version: 2.2.2 driver.version.internal: $ Revision: 0.5 $ input.frequency: 0.00 input.voltage: 0.0 input.voltage.nominal: 120 output.frequency: 59.53 output.voltage: 14.1 ups.load: 67.1 ups.mfr: XPCC ups.model: XVRT-1000 ups.model.type: KIN1500AP ups.serial: Unknown ups.status: OB This looks god. Status signaling is working, so now it is only the calculation of the values returned from the ups. The tricky thing is that you use an 'old' driver. The version of nut is up to 2.4.1 stable. And is soon going to 2.6.x. Your internal revision is 0.5 of the powercom driver, and it is 0.11 in 2.4.1 as I can see. In svn trunk it is up to 0.12. And there have been changes around KIN models in 0.8, so the new driver may give you better readings. This need to be tested before talking to the developer list about adding support for the XPCC. Checked the svn and the changes to 0.12 is only structural so it would not add any functional changes. Is it possible for you to upgrade to nut-2.4.1 ? /Kjell ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] XPCC XVRT-1000 driver
Hi Jeff, Jeffrey B. Green wrote: However, they are fairly simple tools and not configurable beyond the command line arguments specifying the serial line and polling times. Sorry, small correction. Not polling times, rather the breakout delay time and the UPS shutdown delay time. This sounds like the powercom program. So I think you need the powercom driver. Problem is that I don't think we have the papers on the protocol. What you can do is starting the UPSMON program, then cat the port. Ex: cat /dev/ttyS0 If it returns something like this it is powercom. (199.0 199.0 235.0 019 50.0 27.8 37.8 00101000 Then if you can check the speed on the port. The powercom driver is using 1200 b/s. /Kjell ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Powerware 5110 UPS with nut in Ubuntu
2009/8/28 Thomas Zulliger thomas.zulli...@quiksilver.com.au Hi Arnaud and Thomas. Can not reproduce it. upsdrvctl -DD start Network UPS Tools - UPS driver controller 2.4.1 Starting UPS: pw3105 exec: /lib/nut/bcmxcp_usb -a pw3105 Network UPS Tools - BCMXCP UPS driver 0.21 (2.4.1) USB communication subdriver 0.17 No errors. The only thing that come to my mind is that the driver is already running. Check by: ps xau |grep bcmxcp If you try to start it and it is running you get: Starting UPS: pw3105 exec: /lib/nut/bcmxcp_usb -a pw3105 Network UPS Tools - BCMXCP UPS driver 0.21 (2.4.1) USB communication subdriver 0.17 Can't set POWERWARE USB configuration Unable to find POWERWARE UPS device on USB bus Regards Kjell I'm experiencing exactly the same problem DNS-323 fun_plug Fonz nut 2.4.1-1.tgz powerware 3105 using BCMXCP_usb /mnt/HD_a2/packages # lsusb Bus 002 Device 001: ID : Bus 001 Device 002: ID 0592:0002 Powerware Corp. Bus 001 Device 001: ID : /mnt/HD_a2/packages # upsdrvctl -DD start Network UPS Tools - UPS driver controller 2.4.1 Starting UPS: pw3105 exec: /ffp/bin/bcmxcp_usb -a pw3105 Network UPS Tools - BCMXCP UPS driver 0.21 (2.4.1) USB communication subdriver 0.17 Can't claim POWERWARE USB interface Unable to find POWERWARE UPS device on USB bus Things to try: - Connect UPS device to USB bus - Run this driver as another user (upsdrvctl -u or 'user=...' in ups.conf). See upsdrvctl(8) and ups.conf(5). Fatal error: unusable configuration Driver failed to start (exit status=1) /mnt/HD_a2/packages # upsdrvctl -DD -u root start Network UPS Tools - UPS driver controller 2.4.1 Starting UPS: pw3105 exec: /ffp/bin/bcmxcp_usb -a pw3105 -u root Network UPS Tools - BCMXCP UPS driver 0.21 (2.4.1) USB communication subdriver 0.17 Can't claim POWERWARE USB interface Unable to find POWERWARE UPS device on USB bus Things to try: - Connect UPS device to USB bus - Run this driver as another user (upsdrvctl -u or 'user=...' in ups.conf). See upsdrvctl(8) and ups.conf(5). Fatal error: unusable configuration Driver failed to start (exit status=1) /mnt/HD_a2/packages # I rebooted, unplugged, reinstalled etc etc..issue still persists! Can you please point me in the right direction? [pw3105] driver = bcmxcp_usb port = auto desc = PowerWare UPS I'm still puzzled by this issue: I can't reproduce it with the units I have here :( would you be able to test a patch or the development branch (subversion trunk)? cheers, Arnaud ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Serial comm errors with bcmxcp on HP R3000 XR
OK, Should I try changing the polling frequency just to see if it helps? Don't think it would help. If it would be a problem with poll frequency, the error should be continuous and constant. The same is if there was any problem with the driver to the specific model of ups you are running. The driver polls the same data every time, so the error should happen on every poll. Can you relate the errors in the log to any activity? Is the time random or is it spread evenly over time ? I am not getting any other errors or events or significance or that correspond with the UPS errors. The comm errors are not continuous, but there doesn't seem to be a strict pattern. They seem to cluster one every minute or two for between two and ten minutes at a time, with periods of between a half hour to an hour of quiet between the clusters. This sound like a kind of EMI. Do you have the beer fridge beside the computer :-) Check your vicinity for any source of EMI. Fan motors for ventilation, old dimmers, fridges, air-condition. I cc this to Arjen also, one of the guy's in the NUT team that have great knowledge about this tings. Regards Kjell ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Serial comm errors with bcmxcp on HP R3000 XR
OK David, Kjell, Thanks for your time in replying. The cable is a regular commercial shielded cable and is only six feet long. Grounding should not be an issue, everything is on a single circuit with a single ground and is powered through the UPS itself, all in one cabinet, so all grounds should be at the same potential. That is good. Should not be any problems. Then the problem may be the polling frequency. The ups is sending a lot of data for each request. But as you are running it at 19200 it should be OK. I have my PW5125 on 9600 bps and have no problem. What is your system spec ? Linux freebsd ? Kernel version ? I think there was some glitch around version 2.6.25 of the kernel that make the serial port behave strange. Can you relate the errors in the log to any activity? Is the time random or is it spread evenly over time ? Attached is the debug information you requested. Thank you for the info. It looks OK. No errors that info is missing. Older firmware may have some problems, but it look fine on yours. Regards Kjell ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Accurate battery reports? (HP R3000 XR)
OK Jon, just a comment. is bcmxcp a eaton driver? For some years ago Eaton purchased Powerware, but the driver was developed before that. On the nut 1.4 series it was Martin Schroeder that made the driver. But it was dropped, so i was sitting with some Powerware ups'es that I have to monitor. Tore Ørpetveit was getting some info from Powerware Norway, so in 2004 I and Tore started to rewrite the driver. Then Wolfgang Ocker added usb support. Oliver Wilcock sent me some patches for load segments (This code is rewritten, but he was pushing it in :-) ) HP and Compaq re-branded some Powerware equipment like the HP3000XR. sorry, the UPS is already in production usage. As for 2.4.1, i will get it eventually once it is in debian stable. I did try to upgrade to 2.4.1-3 from debian testing, but i had to change a lot to get it working, so i gave up and reverted to debian stable. OK, I fully understand that. Regards Kjell ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Powerware 5110 UPS with nut in Ubuntu
Hi all, Hi Greg, I've got a Powerware 5110 UPS that I'm trying to set up with nut in Ubuntu. I've installed nut and configured the first two files: $ cat /etc/nut/nut.conf MODE=standalone $ cat /etc/nut/ups.conf [pw5110] driver = bcmxcp_usb port = auto # port = /dev/bus/usb/002/002 Yes the port should be auto. And if you use the latest libusb you should have a device at /dev/bus/usb/002/002 that you have found. When I try to test this configuration with the following command: $ sudo upsdrvctl start pw5110 Network UPS Tools - UPS driver controller 2.4.1 Network UPS Tools - BCMXCP UPS driver 0.21 (2.4.1) USB communication subdriver 0.17 Can't set POWERWARE USB configuration Unable to find POWERWARE UPS device on USB bus To make a real test that it read the usb you can do the following. Set libusb debug to 3. sudo export LIBUSB_DEBUG=3 Then run the driver in debug (not by upsdrvctl). sudo /path/to/bcmxcp_usb -DD -u -a pw5110 Now it should spit out some info. You end it by ctrl-c. Report back and we can have a look. We may have a bug here, but it is not confirmed as our tests does not reveal it. /Kjell ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] upsmon says ONBATT when status: TRIM
Hi, Hi Lionel, I've been getting emails from upsmon saying: Subject: UPS pw5...@localhost notification: ONBATT UPS pw5...@localhost on battery But then the machines on the UPS stay on for hours; we haven't got that kind of runtime, more like 10-20 minutes. After a few occurrences, it now happened at a time where I could log in to see in real time what is happening and: $ upsc PW5125 | grep status ups.status: TRIM This is fixed in a later release of the driver. From change log: Wed Jan 14 21:45:10 UTC 2009 / Kjell Claesson kjell.claes...@epost.tidanet.se - drivers/bcmxcp.c: Changed status info to include OL with BYPASS, BOOST, TRIM. Add some more meters like power and current.nominal (max). And also if you upgrade to a later release you have load segment control and some more info from the PW5125 you run. Like this: ~ $ upsc pw5115 ambient.temperature: 28 ambient.temperature.high: 70 battery.charge: 98 battery.runtime: 2060 battery.voltage: 26.95 driver.name: bcmxcp driver.parameter.baud_rate: 9600 driver.parameter.pollinterval: 2 driver.parameter.port: /dev/ttyS0 driver.parameter.shutdown_delay: 10 driver.version: 2.4.1 driver.version.internal: 0.21 input.frequency: 49.65 input.frequency.high: 54 input.frequency.low: 46 input.frequency.nominal: 50 input.transfer.boost.high: 207 input.transfer.high: 266 input.transfer.low: 171 input.transfer.trim.low: 243 input.voltage: 234 input.voltage.nominal: 230 outlet.1.delay.shutdown: -1 outlet.1.delay.start: 1 outlet.1.id: 1 outlet.1.status: On outlet.2.delay.shutdown: -1 outlet.2.delay.start: 2 outlet.2.id: 2 outlet.2.status: On output.current: 0.0 output.current.nominal: 4.5 output.frequency: 49.65 output.phases: 1 output.voltage: 234 output.voltage.nominal: 230 ups.beeper.status: enabled ups.firmware: Cont:02.03 Inve:02.03 ups.load: 0.0 ups.model: PW5125 1000VA ups.power: 0 ups.power.nominal: 1000 ups.serial: GB282A0427 ups.status: OL Regards Kjell ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] HP R3000XR battery charge levels?
Hi again, Just a couple of values are bothering me here... hoping anyone else with an R3000XR can advise. Nice to see that you got it running. battery.charge: 33.1 battery.runtime: 442 battery.voltage: 129.2 This may indicate a faulty battery in the pack. You have 10x12volt, and it should go up to about 137 volt at 100% charge. Also the runtime estimated by the ups is only about 7 min (443 sec). And that is low as it is only loaded to 37,5%. That should be a runtime at about 13 min. ups.load: 37.5 ups.power: 1080.5 ups.power.nominal: 2900 This look OK. 1080.5 is about 37,5 % of 2900. 129.2V battery voltage? Does the R3000 series use a line-voltage battery pack to avoid the need for step-up/step-down transformers? No, it is the same battery-pack in the European 230 volt unit. But one thing is bothering me: input.frequency.nominal: 60 input.transfer.boost.high: 12 input.voltage: 119.8 input.voltage.nominal: 120 The value for input.transfer.boost.high: is way out of range. The value is not reported in the meter map And you don't have any trim, high or low point. It should look like this. input.frequency.nominal: 50 input.transfer.boost.high: 207 input.transfer.high: 276 input.transfer.low: 184 input.transfer.trim.low: 243 input.voltage: 229 input.voltage.nominal: 230 (this is from a PW5115) Also the serial number look strange. So I need to take look on the driver. More to the point, though, is that battery charge level 33.1%? And if so, if the UPS is only at 37.5% load, why is the charge just sitting at 33.1%? Is that the expected output value, or a sign of a dying battery pack? Think you have a dying battery pack. /Kjell ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] New NUT user with HP R3000XR problem
On Tue, May 26, 2009 at 09:51:31PM -0400, Brother Railgun of Reason wrote: Hi, ups.conf looks like this: [tokamak] driver = bcmxcp port= /dev/tty00 baud_rate = 19200 desc= HP R3000XR (main rack) (Oops. That's *after* changing to the 19200 rate the driver claims to autodetect.) That sound strange. It should hit 19200 direct if it is in the config. And the HP R3000XR is communicating at 19200 default. That type is the reason the baud changing got into the driver. Am I using the correct cable here? If not, what's the correct cable to use? If it say it connect it is talking to the ups. But to be sure about that, you may run it in debug mode, like this. /path/to/bcmxcp -DD -a tokamak (stop it by hitting ctrl-c) Now it would spit out some info. I'm interested in the output. There may be some problems how the HP is counting the load-segments. It depends on the version of the firmware in the ups. The other detail I forgot to add was that, just out of sheer constructive paranoia, I tried using an APC 940-0024C cable instead of the HP cable, which as far as I can tell with a DVM is just a dumb serial cable wired all nine pins straight through. With the HP cable, the driver thinks it has comm sync at 19200, but upsdrvctl can't talk to it; with the APC cable, the driver can't even establish communication at all. /Kjell ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Nut and PowerWare 5115
Greg and Arnaud I missed to add that I'm also interested in this one: unset USB_DEBUG lsusb -d06da:0002 -v on your 9.04. I can't find it back in the thread. @Kjell: do you see anything that could lead to that kind of regression? I'm not sure that it's on our side though. I can not set the finger on what it is. My PW3105 is running fine on nut-2.4.1. I know that there have been changes to the nut_usb.c file, and I made a comment to Arjen about it. Because it was breaking the switch between Powerware and Phoenixtec. But that is fixed. And the problem on my side is that I don't have any ups with the Phoenixtec Power Co usb interface. If I get some time I can put ubuntu on a computer and test if the nut package is working on the pw3105. Arnaud, do you have any problems running PW5115 with nut-2.4.1 ? /Kjell ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Nut and PowerWare 5115
tisdag 21 april 2009 14:43:28 skrev Greg: Hi Kjell, Hi Greg, Sorry for the late reply been doing a lot of testing. No problem. I got the package from http://ipkg.nslu2-linux.org/feeds/optware/cs05q3armel/cross/stable/nut_2.4. 1-1_arm.ipk It pretty much pre-compiled which are then extracted to the device on installation. OK. I tested nut and the 5115 under Ubuntu 8.10. Ubuntu comes with nut 2.2.2 by default which works fine. I installed 2.4.1 which does not work either. This is not so good. Then we may have a bug introduced to the nut_usb. I cc this mail to Arnaud. Arnaud can you run some tests on the PW5115 with NUT 2.4.1 ? We may have broken something from version 2.2.2. But it may be the package also but I think Arnaud is working on that to. The error: USB error: could not set config 1: Device or resource busy Can't set POWERWARE USB configuration Unable to find POWERWARE UPS device on USB bus Is indicating that something is already running. Did you check that the debug run was the only thing running at the moment. So I compiled and installed 2.2.2 on my QNAP device and it still doesn't work. 2.2.2 was compiled on my QNAP without HAL support just USB support. Yes, and I see that you get the same error as you get on 2.4.1 on the QNAP. The problem is that I don't have any 5115 to test this on. So I hope that Arnaud can test this. My PW3105 is running fine on usb on 2.4.1. Regards Kjell ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Nut and PowerWare 5115
fredag 17 april 2009 15:36:24 skrev Greg: Hi Kjell, Hi. Sorry for the delay. Thanks for the follow up. Answers below... OK Greg, I can not locate the package you used for installing NUT, but the device should be capable of running NUT. I was thinking if HAL is enabled in the package so the 'hotplug' find the ups on the bus and start the hal driver. Then it gives a conflict. But I got a nice advise from our master Arnaud to enable debug for the libusb. If you do 'export USB_DEBUG=3' you get some debugging info from the libusb in your log. This may help to track down what happens. One thing that is bothering me is that we may have a bug that I can't test. The PW5115 is using a different way of handling the usb endpoint. This is fixed a while back. But there may have been changes to the nut_usb.c that have broken this. I can not see any wrong in the code, but as I don't have a PW5115 with usb, I can not test this. But I know that we have some users running the 5115 on usb, and I have not seen any bug report yet. If you can test it on the Ubuntu installation we can rule out any buggs. Regards /Kjell ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Nut and PowerWare 5115
torsdag 16 april 2009 02:25:58 skrev Greg: Hi everyone, Hi Greg, Been searching like crazy to find an answer to this. I have even read some of the source code but cannot figure this one out. I have installed nut 2.4.1 on my QNAP 409 Pro. (command: ipkg install nut) I have configured the ups.conf, upsd.conf and upsd.users. When i run upsdrvctl start I get the following error messages and output. Network UPS Tools - UPS driver controller 2.4.1 Network UPS Tools - BCMXCP UPS driver 0.21 (2.4.1) USB communication subdriver 0.17 Communications with UPS lost: Receive error (data): got 33 bytes instead of 116!!! Communications with UPS lost: Receive error (Request command): COMMAND: 31 RECONNECT USB DEVICE Can't set POWERWARE USB configuration Unable to find POWERWARE UPS device on USB bus This looks like a access rights problem. Can you try the following. Start the driver in debug mode like this. /path/to/bcmxcp_usb -DD -a PowerWare -u root Normal the path is /lib/nut but check where the bcmxcp_usb is located. This should spit out some debug info. Stop it by hitting ctrl-c. Send me (and the list) the output. 8-snip My ups.conf looks like this user=admin [PowerWare] driver = bcmxcp_usb port = auto desc = PowerWare 5115 UPS #pollinterval=1 baud_rate = 9600 You can remove the baud_rate. It is only for the serial part of the driver. Regards Kjell (Driver author) ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Driver for UPS Eaton 9130
fredag 20 mars 2009 15:03:25 skrev Attila Csontos: Hi Attila, I was trying build new driver from svn, I think, that driver is now OK. There is output from PW9130.br debug level is '2' Connected to UPS on /dev/cua/a with baudrate 9600br Length of meter map: 92 8-snip--- Thank you for the feedback, now the debug output looks OK. If you have any problems or questions not answered in the doc's, don't hesitate to drop us a mail. To Arnaud: Should we put this under Eaton or Powerware in the driver.list ? /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 UPS Eaton 9130
måndag 16 mars 2009 14:32:44 skrev Arnaud Quette: OK all, 8--snip-- It happens only when I start driver with -DD (or more 'D'). When I run only with -D, it working normally. all the debug outputs there are at level 2. so nothing but normal. from your feedback, my guess is that it crashes at the Config_block (line 1108) the gdb trace just before the crash should confirm this (last one should be: Length of alarm map...) Kjell will (or not) confirm since I'm not an XCP expert... This is a type of bugg. Your ups is overshooting the alarm map in the driver. The alarm map length is 29 so 29x8=232. And in the driver it is only set 226, and 232 declared as max. So I have to extend the alarm map by 8 to 240. My ups'es have not so long maps, and the original xcp document was only showing the first 226. But Arnaud have sent me the later alarm map, so I try to get some time later this evening to fix this. Tnx for reporting. 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 UPS Eaton 9130
söndag 15 mars 2009 23:57:18 skrev Attila Csontos: Hi Kjel, I was trying both, but I got message unknow UPS (or similar like this). Maybe nut does not support this model UPS till now. This sounds strange. Maybe Arnaud can answer this. B.t.w. Have you checked that the nut driver have right to the com port? If you have a ups.conf like this: [pw9130] driver = bcmxcp port = /dev/ttyS0 baud_rate = 9600 shutdown_delay = 10 desc = Web server you may try to run the driver like this: /path/to/bcmxcp -DD -a pw9130 -u root (Stop by ctrl-c) Then we know if there is a right's problem. And you also get some debug info. Regards Kjell ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] APC SMART-UPS 1500 always reporting LB
lördag 28 februari 2009 20:37:44 skrev waa-...@revpol.com: Hi Bill, 8--snip- Here is a current upsc output: (on batteries for about 50 mins now) --[snip]-- # upsc smart...@localhost battery.alarm.threshold: 0 battery.charge: 000.0 battery.charge.restart: 00 battery.date: 09/20/00 battery.packs: 000 battery.runtime: 0 battery.runtime.low: 120 battery.voltage: 23.15 battery.voltage.nominal: 024 Yep, it seems like you have a broken ups. As the battery runtime and battery charge is dropping to zero. You still have 23.15 volt on the battery (If we can trust this measurement). Regards Kjell ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Followup: APC SMART-UPS 1500 always reporting LB
Hi Again Bill, Checked up the manual for the APC. It looks like you have to do some configuration with the POWERCHUTE SOFTWARE. Reset the battery date and make a runtime calibration test. If this is not done it may as it say in the Problem and/possible cause THE LEDS IN THE BATTERY BAR GRAPH ARE BLINKING TOGETHER Problem While online or on battery, the expected remaining runtime is lower than the configured low battery warning interval. Note: The number of blinking LEDs still indicates the rela- tive state of charge of the connected batteries. It may be: The battery runtime meter has fallen out of calibration and needs to be recalibrated. This is worth testing before calling the APC support. 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 ?
lördag 28 februari 2009 16:36:54 skrev Charles Lepple: There's a subtle difference here - adding '-D' to the upsdrvctl command line increases the verbosity of upsdrvctl, not the driver that it starts. For testing, you would want something like: /lib/nut/usbhid-ups -D -a compaq-ups As Kjell mentioned, the nut-upsdev list is a better place for usbsnoop logs and whatnot, if we can't figure it out with the basic debug output. You are right Charles, I must have been sleeping. The only thing I was thinking that it was strange debug output :-) So KP you should run the driver only, not through the upsdrvctl. By running it like Charles say, you should get some more debug info out. /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: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
Re: [Nut-upsuser] Recommended UPS brand (OffTopic sort of)
lördag 14 februari 2009 14:40:07 skrev Doug Parsons: OK Doug, I saw those as well but need the online model as I have had some issues with offline models and rapid power cycles. When you have an automatic transfer switch between two ups units and your equipment, the rapid cycles can cause you to loose power or in my case corrupt the power to the point my router locked up. I have several ESX servers and the more critical units need to have clean power on at least one power supply. Just a little bit of insurance there. I also have some SAN storage that needs the online unit. One other catch is that I am limited to a 120V 20 Amp feed to the units and want to maximize it. The 2200 does this. If I go any bigger I need a 30 amp circuit and any smaller waste capacity on that circuit. Thanks for the input. Then you could step up to a PW9130L2000R-XL2U. True online, double-conversion and a circuit breaker rating 20A. But the MGE equipment is also a great choice. /Kjell ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Recommended UPS brand (OffTopic sort of)
fredag 13 februari 2009 20:52:41 skrev Arnaud Quette: Hi Doug, 8---snip Really hate that MGE drop those models as I really like the quality and design. not that easy! This part of MGE has not been droped, but sold to Eaton. All the good things, including the NUT and more generally FLOSS support has so gone to Eaton. Check my sig for the new link, and rejoice: what you like is still alive, and more than even ;-) And if you extend Arnaud's sig link to: http://www.eaton.com/EatonCom/ProductsServices/Powerware/index.htm You find another brand that is good. And I think you would like a PW5130L2500-XL2U. http://www.powerware.com/UPS/5130_UPS.asp Regards Kjell ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] HP/Compaq T700H UPS cable pinout
Den Tuesday 13 January 2009 23.27.02 skrev Arjen de Korte: Hi Arjen, It would be nice if the driver would also report 'battery.voltage.nominal', so that clients don't have to guess it. We need this for instance when drawing bar graphs in the CGI programs. That take some more time, This is in the config block. And was planned to be included when I rewrite some more. Have to check the command list block and parse it an do something like in the upscode2 driver. The 'can_upda' and so on. So I know what the ups can respond to. But it is a binary answer and I have not find any nice way to do that. input.frequency: 50.34 input.voltage: 245 Same here. The input.voltage nominal is fixed. But I have to sleep. Se if I have time to enter the input/output.frequency.nominal A.S.A.P. This probably needs to be multiplied by 100. Note that this value is reported in percentage, not a factor. Either this, or the load can't be right. Now it show ups.power. But that is the output power in va. Have also input power in va and out/input.power in watt that I can read. Although the OL status is implied when the UPS is in TRIM state, it would be nice if the driver would report this too. Not all clients will pick this up, if they want to know if the UPS is running on mains or on battery (would require checking for OL|TRIM|BOOST). It helps to be verbose here and add the OL status too. Should be fixed. I know that you have much to do, but if you have any idea about the comand- list-block, and how to parse and use it I would be glad :-) Regards Kjell ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] HP/Compaq T700H UPS cable pinout
Den Tuesday 13 January 2009 03.40.58 skrev Mathew McBride: Hi Mathew, I managed to obtain the original cable for this UPS, and it turns out, according to some poking with a multimeter, that it is a simple straight through. I managed to connect the UPS and setup NUT ok. One thing I would like though: The HP software can display the output/load wattage. Is it possible to somehow add this to the variables list? What driver do you use , upscode2 or bcmxcp ? Can you send the outupt of upsc ups Regards Kjell ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Unknown product ID for Tripp-Lite UPS (SU1500RTXL2UA)
Den Wednesday 31 December 2008 06.31.05 skrev Herman C Lau: To all, Hi Herman, I attempted to configure the UPS tools for the Tripp-Lite SmartOnline 1500VA 2U rackmount UPS. I followed the instructions from the 'upsdrvctl start' output and posted the diagnostic information below. Is my UPS using an unknown product ID as reported? From the mailing list archive, I have found another posting for the same UPS with device model '09AE/4003', whereas mine is '09AE/4001'. The output from the debug run looks OK. so you can try to add the productid to the ups.conf [su1500] driver = usbhid-ups port = /dev/usb/hiddev0 productid = 4001 desc = Tripp Lite SmartOnline 1500VA And I think it ignore the port value. so you can set that to auto. Se the : man usbhid-ups Now run it as normal and se if the driver starts and the upsd so you can get some values back with: upsc su1500 Regards Kjell ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] HP/Compaq T700H UPS cable pinout
Den Saturday 20 December 2008 16.39.55 skrev Mathew McBride: Hello all, Hi Mathew I have obtained a Compaq T700 H UPS sans-cable. My research indicates it would've come with a HP #201092-001 cable, and from previous posts on this list, it speaks upscode2, possibly being a rebadged Eaton unit. Yep it is an Eaton unit that speaks upscode2. Any suggestions for cable pinouts I can try? Attache a pdf with info from Compaq. Se if it helps. (attachment removed from posting to list) Regards /Kjell ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] HP/Compaq T700H UPS cable pinout
Den Saturday 20 December 2008 20.29.43 skrev Charles Lepple: Hi Charles, On Sat, Dec 20, 2008 at 11:40 AM, Kjell Claesson kjell.claes...@epost.tidanet.se wrote: Attache a pdf with info from Compaq. Se if it helps. (attachment removed from posting to list) If we're allowed to distribute that file, would you mind posting it to the wiki? I think we can upload attachments. Email Arnaud if you have trouble logging in. What wiki ? Can not find anything on alioth. But I send you the file and you can place it in the right place. /Kjell ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Mustek drivers
Den Thursday 18 December 2008 17.05.59 skrev du: Hi Kjell, Hi Mohanjith, The UPS is from one of the local manufacturers IE Tec. They no longer produce this UPS. I tried all drivers with no luck, namely apcsmart, belkin, belkinunv, bestuferrups, bestups, cpsups, cyberpower, energizerups, etapro, everups, genericups, isbmex, liebert, masterguard, mge‐shut, mge‐utalk, oneac, powercom, safenet, snmp-ups, tripplite, tripplitesu, victronups. If you look in the nut source docs/megatec.txt you find. quote The following drivers are targeted for assimilation: * blazer (1) * fentonups (1) * mustek (1) * esupssmart (1) * ippon (1) * sms (1) * masterguard (3) (1) megatec already supercedes this driver in functionality. (2) megatec partially supercedes this driver in functionality, but some small features are missing (non-critical for normal operation). (3) megatec partially supercedes this driver in functionality, but some important features are missing, which means some hardware may not be supported. unquote So the driver should support the mustek protocol. With genericups I tried all UPS types with no luck. I have hit a brick wall. The generic is only for contact closure and if the ups support this you may have to use a differnet cable for this. Any ideas? Any help is appreciated. Looking at your second mail you run the upsdrvctl with debug. This would not run the driver with debug. You need to run it like. /path/to/driver/megatec -DD -a patriot You have to kill this with ctrl-c but you get debug info from the driver. Check the manual for megatec, there is some flags you may alter, like DTR and RTS in the ups.conf. Also the sendpace can be altered, this is the wait between characters. (default 100mS) Run the driver in debug mode. Alter the DTR RTS value in the config and run it again. Se if you have any responce from the Q1 command. If you get response alter the sendpace for relyable respons. As it is a text protocol you may try minicom or any terminal program and send Q1/r (Q1 followed by return) and check if you get any responce. ref: http://eu1.networkupstools.org/protocols/megatec.html Regards /Kjell ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Mustek drivers
Den Tuesday 16 December 2008 15.48.48 skrev Sudirikku Mohanjith: Hi, Hi Mohanjith, I cannot find Mustek drivers or PowerMust drivers that support Mustek UPSes in the NUT source. Looking at the source I see that mustek is added to svn:ignore. Could I know where I can get either driver or know why they were removed form the source? The source was full of drivers for the megatec protocol, so the mustek and powermust is dropped. Now it is supported by the megatec driver. Please help me, I have a Mustek UPS that used to work on Fedora but no longer on Debian for the obvious reason of not having any of the mustek drivers. Test the megatec driver. /Kjell ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Mustek drivers
Den Tuesday 16 December 2008 20.39.17 skrev Sudirikku Mohanjith: Hi Kjell, OK Mohanjith, Thanks for the quick reply, much appreciated. I tried the megatec driver with no luck. Bellow you will find part of the ups.conf and the output from upsdrvctl. From /etc/nut/ups.conf [patriot] driver = megatec port = /dev/ttyS0 desc = Patriot UPS powering moha-gateway 8-snip--- Maybe we should start from the begining. What is the brand and type of UPS? They have cleaned up the driver code in NUT, and made some driver handle more types. Because you could find drivers with almost the same code, and was not maintaind. So to fix this, the support was added into one driver. You have 'Patriot...' in the description, so if it is a 'Best Power Patriot' you should try the bestups driver. But tell us what ups you have and we can go from there. Regards /Kjell Den Tuesday 16 December 2008 15.48.48 skrev Sudirikku Mohanjith: Hi, Hi Mohanjith, I cannot find Mustek drivers or PowerMust drivers that support Mustek UPSes in the NUT source. Looking at the source I see that mustek is added to svn:ignore. Could I know where I can get either driver or know why they were removed form the source? The source was full of drivers for the megatec protocol, so the mustek and powermust is dropped. Now it is supported by the megatec driver. Please help me, I have a Mustek UPS that used to work on Fedora but no longer on Debian for the obvious reason of not having any of the mustek drivers. Test the megatec driver. /Kjell ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Driver not found for Powerware 5110
Den Tuesday 09 December 2008 18.39.58 skrev Aldo Caruso: Hi, Hi Aldo, I have an UPS Powerware 5110 ( usb connection ), on Linux OS is Debian 4.0 Good info, but it would be better to know the nut version. And the driver version number also. The /etc/ups.conf file setting is: [myups] driver = bcmxcp_usb port = auto desc = UPS Powerware 5110 1500 VA That is OK. When the daemon starts it displays the following message: Starting Network UPS Tools: (upsdrvctl failed). Looking at /var/log/syslog I found the following line Can't connect to UPS [myups] (bcmxcp_usb-auto): No such file or directory This should be located in /var/lib/nut and that directory should belong to the user nut is running as. Normaly nut. But it depends on the packages. Think we have some debian users that could help you with this. Does any body know why it appends -auto to the driver name ? This indicate an older verion of the nut. Now it appands the tag name ( for you 'myups') to the socket, like bcmxcp_usb-myups. This is my /var/lib/nut ls -l /var/lib/nut/ totalt 8 srw-rw 1 nut nut 0 9 dec 21.51 bcmxcp_usb-pw3105 -rw-r--r-- 1 nut nut 5 9 dec 21.51 bcmxcp_usb-pw3105.pid -rw-r--r-- 1 nut nut 5 9 dec 21.51 upsd.pid Regards /Kjell ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Cyberpower/powerpanel error: Data stale
Den Tuesday 28 October 2008 17.39.25 skrev Seann Clark: Hi Seann and Arjen, Could not keep me from looking at this. The driver looks OK, and changing the timing (delays) in it is not going to help. Then I turned to google. Looks like there is a regression in the kernel. https://bugzilla.redhat.com/show_bug.cgi?id=451326 Is it possible for you to change back to a 2.6.24 kernel? It have been a lots of changes in the serial port code referring to the kernel change-log and patches. Also 2.6.26 seems to have the problem. 2.6.27 could work. But I don't think you have any RPM for that yet. I run a 2.6.27 kernel, but I had no time digging into the bcmxcp driver yet, so I have not run any serial driver on this machine. Regards Kjell ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Cyberpower/powerpanel error: Data stale
Den Monday 27 October 2008 17.59.44 skrev Seann Clark: All, Hi Seann, 8snip- What I am seeing that is the problem now is that the driver starts correctly, and initially displays information back from the UPS, but on any subsequent reads of the UPS, I get the error: Mon Oct 27-11:55:[EMAIL PROTECTED]:ups upsc cyberpower-ups Error: Data stale I'm not so familiar with the cyberpower driver. But I looked in the svn and it seems that the powerpanel driver is on it's way to replace it. Think Arjen is the one that know all about this. I have just started seeing this error as the ups was moved to a newer system on a newer version of Fedora. the differences between the version was it was working on 2.1.x and not on 2.2.x. I would fall back to the old system but that was replaced due to catastrophic hardware failure, that wasn't power related. If you can try out the powerpanel driver and report back what it say and if you get the same data stale. Or, is it possible that new setup inject noice into the communication cable? I hade this on one ups, where I got a ground-loop with the cable. Any help would be appreciated though, and I can provide even more information if it is needed. Regards Kjell ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Delta UPS boxes
Den Wednesday 03 September 2008 15.56.11 skrev Jerome BENOIT: OK Jerome, Here is the full list: battery.charge: 100 battery.temperature: 000 battery.voltage: 274.0 driver.name: belkin driver.parameter.pollinterval: 2 driver.parameter.port: /dev/ttyS0 driver.version: 2.2.2 driver.version.internal: 0.21 input.frequency: 60.1 input.transfer.high: 0.0 input.transfer.low: 0.0 input.voltage: 211.0 output.frequency: 60.0 output.voltage: 220.0 ups.firmware: 5015307704 ups.load: 054 ups.mfr: BELKIN ups.model: GES602N ups.status: OL ups.temperature: 000 Thank you for the info. I have not yet made such a test. I have one new cluster, one old cluster, and a new workstation. So far, I have played with the upssched features on the new computers. Now I must play with the old computer: this may take some time. Once the all computers are ready, I will make such a test. Yes I understand that. You need a testsetup so you don't mess up your cluster. We recomend to power some other load (light's) for testing and supply the computer directly. In that case if the UPS missbehave the computer is uneffected. What I can say right now is that when I do /sbin/upsmon -c fsd everything shutdown as expect, except the UPS box. Right now, my guess is that /sbin/upsmon -K does not work as expected. I have not yet modified the /etc/init.d/nut script provided by the Debian (Lenny) package: at the very end, I get the message: Power down flag is not set (UPS shutdown not needed) 8--snip-- What is the expected magic string ? is this string come somehow from the UPS box ? Does I miss something here ? If you read the 'shutdown.txt' in the doc, you find that this is a file 'creates the POWERDOWNFLAG file - usually /etc/killpower' And this is created by upsmon master. http://eu1.networkupstools.org/doc/2.2.0/shutdown.html This is the file that the shutdown script look for to power of the ups. quote if (test -f /etc/killpower) then echo Killing the power, bye! /usr/local/ups/bin/upsdrvctl shutdown sleep 120 # uh oh... the UPS poweroff failed! # you probably should reboot here to avoid getting stuck # *** see the section on power races below *** fi unquote Meanwhile I got a feed from a Delta user: he suggest to use belkinunv. I let it a try, but it did not work. It would be fine if he could give us the info from his setup. We need to enter this into the compatibility list. So people know what driver to use. Regards Kjell ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Delta UPS boxes
Den Tuesday 02 September 2008 20.11.28 skrev Jerome BENOIT: Hello ! Hi Jerome On the manual and the box, I read: Delta GES N-Series 6kva (on line series) On the other hand, upsc gives ups.mfr: BELKIN This depends on the driver. If the request for manufacturer fails to return anything, it set's it to BELKIN. ups.model: GES602N This is OK. ups.firmware: 5015307704 Strange firmware number. Is the rest of the upsc command OK ? Like voltages, runtime, current, status e.t.c.. Also make sure that the shutdown is working. upsdrvctl shutdown shutdowns the UPS box. Yep, Sorry but I was referring to when you pull the mains, and check if it goes to OB and if it signalling OB LB and start a shutdown on your system. We need to know that the ups is giving the right status to the driver. Nevertheless, it seems that I can not set the UPS fsd, so the Debian init NUT script does not poweroff the UPS box. Hmm, this is the way it should work. And this is what happens when you do and FSD. If the main's is failing it would go to battery. When the battery goes to LB (Low Battery) it start to shutdown the system. Then it power of the ups. It set the ups in something called shutdown.return. It power off the ups to save the battery, then power it on when the main's return (after delay or charge level) So the computer should be set to 'last state' in the bios for 'state after power loss'. Don't hesitate to ask any questions on the list, we are here to help you get things going the way you whant. We run many different dist's, think Arnaud is best on the Debian side. I run Gentoo. Regards Kjell ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Delta UPS boxes
Den Monday 01 September 2008 18.04.22 skrev Jerome BENOIT: Hi again Jerome, Not 100% sure but it looks like it is tha same as belkin use. So for start, try the belkin driver's and then the megatec driver. the driver belkin is the good one ! OK, can you send some info to the list. Product (Manufacturer) and type (type number). The output of the upsc command. Also make sure that the shutdown is working. Then we can put it in the compatibility list. Regards Kjell ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Delta UPS boxes
Den Saturday 30 August 2008 21.31.44 skrev Jerome BENOIT: Hello List, Hi Jerome, I would like to control the big Delta box that protect the cluster of my group: I am not familiar with those kind of machine, but quite familiar with (Debian) Linux. That is good. Does anyone know which NUT driver to use ? Not 100% sure but it looks like it is tha same as belkin use. So for start, try the belkin driver's and then the megatec driver. The UPS have 3 different communication interfaces: RS-232 AS-400 Dry-contact Which one is the more appropriate for NUT ? You should try RS-232 first. If no go on belkin or megatec you can try to setup the dry-contact with the generic driver. Any other information is welcome :-) If you install NUT, try the driver in debug mode first. Setup the ups.conf (se manual) then run the driver in debug. /path/to/belkin -DD -u root -a ups The -u root is to handle any problems with access to the comport. If you know this is OK you can take out the -u root in the command. The -a ups is pointing to what you set for tag name in ups.conf. Regards Kjell ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] New addition to compatibility list
Den Sunday 02 March 2008 04.53.29 skrev Greg: Hi Greg, I'm not sure if this is the right list to send this to but anyway heres a new entry for your UPS hardware compatibility list (stable) Think most of the devs is also monitoring this list. Manufacturer - UPSonic Model - PC POWER UPS PCP600 NUT driver - megatec This is not enough info to get it into the compatibility list. Can you support us with info from 'upsc ups' to check that the values is OK ? Is the shutdown function working OK ? Is listed instant commands doing what is expected ? So if you can supply us with this info it goes into the list. Thank you for helping us extending the comp. list. Best regards Kjell ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Powerware 5115 on Debian Etch
Den Monday 18 February 2008 15.25.26 skrev Daniel Nyström: OK, There have been some updates to the configure script and some other things. You may have to do a 'autoreconf' first so you have a fresh configure script. Kjell I just updated my svn checkout (now revision 1308), but it wasn't even able to compile at all; [EMAIL PROTECTED]:~/nut-trunk$ ./configure --with-usb --without-ssl --without-snmp --without-serial --without-ipv6 --prefix=/opt/nut [..snip...] [EMAIL PROTECTED]:~/nut-trunk$ make [..snip...] gcc -DHAVE_CONFIG_H -I. -I../include-I../include -O -Wall -Wsign-compare -MT sstate.o -MD -MP -MF .deps/sstate.Tpo -c -o sstate.o sstate.c mv -f .deps/sstate.Tpo .deps/sstate.Po make[1]: *** No rule to make target `access.o', needed by `upsd'. Stop. make[1]: Leaving directory `/home/daniel/nut-trunk/server' make: *** [all-recursive] Error 1 [EMAIL PROTECTED]:~/nut-trunk$ Ideas? Kjell Claesson wrote: Den Monday 18 February 2008 10.51.35 skrev Daniel Nyström: Hi Daniel, This is fixed in tha latest trunk and also in the testing branch that is going to be the next release. You can grab a tarball from http://buildbot.ghz.cc/public/nut/ for Debian Etch. If you want to try this out. Regards Kjell P.S. Driver version should be 0.14 to have the fix. Bumping this one, as there seems to be others having similar problems. Any ideas? Daniel Nyström wrote: I've got some strange problem with NUT on my 5115 on Debian Etch: ---snip--- $ sudo ./bcmxcp_usb -DDD -a 5115 -u root Network UPS Tools - BCMXCP UPS driver 0.13 (2.3.0-1181) Warning: This is an experimental driver. Some features may not function correctly. debug level is '7' Communications with UPS lost: Receive error (Request command): COMMAND: 31 RECONNECT USB DEVICE Communications with UPS lost: Receive error (Request command): COMMAND: 31 RECONNECT USB DEVICE Communications with UPS lost: Receive error (Request command): COMMAND: 31 RECONNECT USB DEVICE Communications with UPS lost: Receive error (Request command): COMMAND: 31 RECONNECT USB DEVICE Communications with UPS lost: Receive error (Request command): COMMAND: 31 RECONNECT USB DEVICE Communications with UPS lost: Error executing command Could not communicate with the ups: Inappropriate ioctl for device ---snip--- Saw a similar issue earlier on this list, but it was never solved. Any ideas? ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Powerware 5115 on Debian Etch
Den Monday 18 February 2008 16.03.23 skrev Daniel Nyström: OK, Thanks! Forgot it didn't come with the repo. :) Now it do compile, but configure didn't find my missing dbus/dbus-glib.h. Maybe something to add to autoconf? But doing make install still halts: Yep there have been some issues with the install path. But as I think you are going to run nut as standard and not with hal, you may add --whitout-hal to the configure. As it looks like it stop on that. Kjell /bin/sh ../libtool --mode=install /usr/bin/install -c 'mge-xml' '/opt/nut/bin/mge-xml' /usr/bin/install -c mge-xml /opt/nut/bin/mge-xml /bin/sh ../libtool --mode=install /usr/bin/install -c 'upsdrvctl' '/opt/nut/bin/upsdrvctl' /usr/bin/install -c upsdrvctl /opt/nut/bin/upsdrvctl test -z || /bin/mkdir -p /bin/sh ../libtool --mode=install /usr/bin/install -c 'hald-addon-usbhid-ups' '/hald-addon-usbhid-ups' libtool: install: `' must be an absolute directory name Try `libtool --help --mode=install' for more information. make[2]: *** [install-halexecPROGRAMS] Error 1 make[2]: Leaving directory `/home/daniel/nut-trunk/drivers' make[1]: *** [install-am] Error 2 make[1]: Leaving directory `/home/daniel/nut-trunk/drivers' make: *** [install-recursive] Error 1 [EMAIL PROTECTED]:~/nut-trunk$ I guess it's pretty simple, since all other files works. Kjell Claesson wrote: Den Monday 18 February 2008 15.25.26 skrev Daniel Nyström: OK, There have been some updates to the configure script and some other things. You may have to do a 'autoreconf' first so you have a fresh configure script. Kjell I just updated my svn checkout (now revision 1308), but it wasn't even able to compile at all; [EMAIL PROTECTED]:~/nut-trunk$ ./configure --with-usb --without-ssl --without-snmp --without-serial --without-ipv6 --prefix=/opt/nut [..snip...] [EMAIL PROTECTED]:~/nut-trunk$ make [..snip...] gcc -DHAVE_CONFIG_H -I. -I../include-I../include -O -Wall -Wsign-compare -MT sstate.o -MD -MP -MF .deps/sstate.Tpo -c -o sstate.o sstate.c mv -f .deps/sstate.Tpo .deps/sstate.Po make[1]: *** No rule to make target `access.o', needed by `upsd'. Stop. make[1]: Leaving directory `/home/daniel/nut-trunk/server' make: *** [all-recursive] Error 1 [EMAIL PROTECTED]:~/nut-trunk$ Ideas? Kjell Claesson wrote: Den Monday 18 February 2008 10.51.35 skrev Daniel Nyström: Hi Daniel, This is fixed in tha latest trunk and also in the testing branch that is going to be the next release. You can grab a tarball from http://buildbot.ghz.cc/public/nut/ for Debian Etch. If you want to try this out. Regards Kjell P.S. Driver version should be 0.14 to have the fix. Bumping this one, as there seems to be others having similar problems. Any ideas? Daniel Nyström wrote: I've got some strange problem with NUT on my 5115 on Debian Etch: ---snip--- $ sudo ./bcmxcp_usb -DDD -a 5115 -u root Network UPS Tools - BCMXCP UPS driver 0.13 (2.3.0-1181) Warning: This is an experimental driver. Some features may not function correctly. debug level is '7' Communications with UPS lost: Receive error (Request command): COMMAND: 31 RECONNECT USB DEVICE Communications with UPS lost: Receive error (Request command): COMMAND: 31 RECONNECT USB DEVICE Communications with UPS lost: Receive error (Request command): COMMAND: 31 RECONNECT USB DEVICE Communications with UPS lost: Receive error (Request command): COMMAND: 31 RECONNECT USB DEVICE Communications with UPS lost: Receive error (Request command): COMMAND: 31 RECONNECT USB DEVICE Communications with UPS lost: Error executing command Could not communicate with the ups: Inappropriate ioctl for device ---snip--- Saw a similar issue earlier on this list, but it was never solved. Any ideas? ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Installation and config; not found driver
Den Wednesday 30 January 2008 16.11.15 skrev Chencho Pc-cito: Hi all. Hi Chencho, I'm under Ubuntu 7.10 server I use a SALICRU UPS Advance I install nut and nut-usb, write some config files, but i cannot connect to UPS. At ups.conf i wrote: [salicru] driver = newhidups port = auto desc = Desc Try the megatec_usb driver instead. But if try to make sudo upsdrvctl start it said: No matchin HID UPS found If i write lsusb appears: Bus 001: Device 007: Id 06da:0003 Phoenixtec Power Co. Ltd I had a rule at /etc/udev/rules.d/60-local.rules like: http://www.theefrit.com/blog/2006/10/17/sai-mge-ellipse-premium-y-linux/ but changing Device to mine (06da:0003) But i cannot make it work. Regards Kjell ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] powerware 3110 USB
Hi Patrick, Den Wednesday 09 January 2008 05.11.57 skrev Patrick Ohearn: Hello, I am attempting to monitor my two Powerware 3110 UPS from Gentoo Linux using nut-2.2.0, kernel-2.6.22.1 via USB. From what I can gather around the net (circa 2005) things with USB on this UPS just didn't work. Has this changed and is there anything I can do to help? There is a fix (committed today) in the trunk. So if you can grab the code from svn (trunk) and build it. I can not garanti that it works. But as you say quote is there anything I can do to help? unquote You can test this out for us. The ups.conf should look like this. [ups-router] driver = bcmxcp_usb port = auto desc = Powerware 3110 - Router I use Gentoo also. I have a patched nut-2.2.1.tar.gz so I copied the /usr/portage/sys-power/nut to overlay, and copied the nut-2.2.0.ebuild to nut-2.2.1.ebuild. This is fare more simple than building from svn as you need to set all the config parameters to get it installed in the right place. Regards Kjell ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Powerware 5115 on Debian Etch
Hi Daniel, (Eller hejsan.) Den Monday 07 January 2008 09.28.41 skrev Daniel Nyström: I've got some strange problem with NUT on my 5115 on Debian Etch: ---snip--- $ sudo ./bcmxcp_usb -DDD -a 5115 Network UPS Tools - BCMXCP UPS driver 0.13 (2.3.0-1181) Warning: This is an experimental driver. Some features may not function correctly. debug level is '7' Can't set POWERWARE USB configuration Unable to find POWERWARE UPS device on USB bus Things to try: - Connect UPS device to USB bus - Run this driver as another user (upsdrvctl -u or 'user=...' in ups.conf). See upsdrvctl(8) and ups.conf(5). Fatal error: unusable configuration [EMAIL PROTECTED]:/opt/nut/bin$ sudo ./bcmxcp_usb -DDD -a 5115 -u root Network UPS Tools - BCMXCP UPS driver 0.13 (2.3.0-1181) Warning: This is an experimental driver. Some features may not function correctly. debug level is '7' Communications with UPS lost: Receive error (Request command): COMMAND: 31 RECONNECT USB DEVICE Communications with UPS lost: Receive error (Request command): COMMAND: 31 RECONNECT USB DEVICE Communications with UPS lost: Receive error (Request command): COMMAND: 31 RECONNECT USB DEVICE Communications with UPS lost: Receive error (Request command): COMMAND: 31 RECONNECT USB DEVICE Communications with UPS lost: Receive error (Request command): COMMAND: 31 RECONNECT USB DEVICE Communications with UPS lost: Error executing command Could not communicate with the ups: Inappropriate ioctl for device ---snip--- Saw a similar issue earlier on this list, but it was never solved. Any ideas? Yes this depend on the endpoint used by the implementation from Phoenixtec Power Co., Ltd. It is used on the 5115 and 3110 that was equiped with usb (1.1) in an early stage. If you what you may patch your source with the patch presented by Max E. Kuznecov on the developer list on 2007-11-07. Have not had the time to check this out (and I don't have the equipment to test it on) so nothing have been done in the driver to fix this. Se if I can get this fixed. Regards Kjell Gott nytt 2008. ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] powerware 5125 and bcmxcp driver
Den Saturday 01 December 2007 00.11.21 skrev Radu: Hi Radu, I'm trying to get a Powerware 5125 UPS running using the bcmxcp driver, but I get the following errors: video2:~# /sbin/upsdrvctl start Network UPS Tools - UPS driver controller 2.0.4 Network UPS Tools - BCMXCP UPS driver 0.10 (2.0.4) Don't hurt to get some newer release as 2.0.4 is out of date. But I don't think it solves the problem. Communications with UPS lost: Error executing command Communications with UPS lost: Error executing command Communications with UPS lost: Error executing command Communications with UPS lost: Error executing command Communications with UPS lost: Error executing command Communications with UPS lost: Error executing command Can't find the UPS on port /dev/ttyS0! Driver failed to start (exit status=1) This error come from that it don't answer. The first error is the test on 9600 baud (as you have it in the ups.conf) then it test on 1200, 2400, 4800, 9600, 19200 and then fail. Here are my /etc/nut/ups.conf: [ups] driver = bcmxcp port = /dev/ttyS0 desc = PowerWare 5125 baud_rate = 9600 That look's OK. With the generic driver it works, sort of. I mean it signals I'm running on battery (which is not true) and the battery is low and then shut downs. Also, I can connect with the minicom to the UPS. How does it look when you connect with minicom ? The bcmxcp protocol is a binary protocol with no handshake. But if it looks like text strings you may try to send UPDA cr to the ups. If it spit out some data, try the upscode2 driver. Any ideas how to get the bcmxcp driver up? Try upscode2 and check that the cable for the ups is the one to use for serial communication. (May be another for generic (contact closure)) Regards Kjell ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] PW9120 - Shutdown condition?
Den Friday 09 November 2007 13.09.32 skrev Arjen de Korte: I have a PW9120 hooked up via a serial cable running NUT 2.0.4. When running upsc I cant see any parameter that looks like it would trigger a shutdown. Theres is nothing like battery.charge.low: 30 or battery.charge.warning: 30. The UPS may not support reporting and/or changing this value. Arjen is right about that. It uses the default settings in the ups. The config change is on the todo list. Also reading of config block. I get: ambient.temperature battery.(charge|runtime|voltage) driver.(misc) input.(misc) output.(misc) ups.(firmware|load|model|power.nominal|serial|status|voltage.nominal) running upscmd -l gives me: shutdown.return shutdown.stayoff test.battery.start What triggers the shutdown of a PW9120 and how do I change the value ? In general, shutdown will be triggered when the UPS is both on battery *and* reporting low battery. The latter may or may not be user configurable. In your case, it looks like the driver has no way of changing this level, so when this actually happens depends on the UPS. Yes it trigg on OnBattery (OB) LowBattery (LB) and do a shutdown_return. See 'docs/shutdown.txt' if the time remaining after a shutdown is initiated isn't sufficient for an orderly shutdown of your UPS. The 2.0.4 version have a bug in the shutdown_return, it is not reading the shutdown delay from ups.conf in this function. This is fixed in the latest releas. But as you have no varning about delay longer than runtime on battery low you should get at least 120 seconds runtime after OB LB. Regards Kjell ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] PowerWare 9120 via USB?
Den Thursday 08 November 2007 16.11.11 skrev Tobias Balle-Petersen: Tobias Balle-Petersen wrote: Hello Arjen. Arjen de Korte wrote: Adding 'baudrate = 9600' to the 'ups.conf' entry for this UPS should fix this. Strange, it tells me this is not supported. I'm on 2.0.4. Ahh... It goes in the global section. Sorry. Hello all, You have been busy i see. OK it is possible to set the 9120 to requsted mode only, and this is done by the serial driver part. And it should remain so after power cycling. One thing that bothers me is that it state. Quote: I can se the UPS with lsusb: Bus 002 Device 004: ID 06da:0002 Phoenixtec Power Co., Ltd Bus 002 Device 001: ID : Bus 001 Device 001: ID : Unquote Phoenixtec did the communication bord for the 3110 and 5115 so we may have some problems that discussed on the developer list regarding 5115. A new 3105 is reporting Bus 002 Device 002: ID 0592:0002 Powerware Corp. I also found during debug of the 3110 that is not following the standard for the bcmxcp. So try to run it with a serial dongle, and we look into this. (dam that my work take so mutch time from this) Regards Kjell ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] PowerWare 9120 via USB?
Den Wednesday 07 November 2007 12.06.11 skrev Tobias Balle-Petersen: OK Tobias, I have tried two different USB-cables. The one that came with the UPS and another one I had lying around. I have tried both ports on the computer (Apple mac G4). Was there any difference in the communication ? It is not a compatibility error, as it should hang on the same command. And it was developed on a 9120 but serial connected. If the PW9120 is supported by both drivers (bcmxcp_usb and bcmxcp) should it not be listed in both sections on the chart? Both yes and no. It should work but as no one have give a positive feedback on this we can not enter it into the chart. Use hi class usb cables, if You is unable to use the serial version of the driver. Use a short sheelded cable. Don't twist it around the powerlines. Does communicating with the UPS demand more of the USB-cables than any other USB-setup (printers etc.)? If so why? No not realy, but the printer driver is not so verbose as this ups driver. So if there is some problems with the printer it would resend without sending communication error. I can do the same with the ups driver and let it silently ignore any communication errror and hope that the retry is handling it. But as the ups is more critical than a printer, (I think that you can stand to resend a printout, but I don't think that you would like the ups to shutdown without issuing a nice shutdown to the Computer.) we need to know that the communication is OK. Then you should get new version of nut as 2.0.4 is past date. I'm running Debian Stable. 2.0.4 is the latest version. My UPS should be usable with this version right? Yes it would be usable, but there have been some changes around the error handling in the drivers. And some more fixes. Think Arnaud have made some packages for debian. If ther is someone on the list that can point you to this as i'm not into this package handling systems as i'm running Gentoo. Regards Kjell ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] PowerWare 9120 via USB?
Den Friday 02 November 2007 13.00.46 skrev Tobias Balle-Petersen: Hello... Hi Tobias. I have a PowerWare 9120 attached via USB to my Debian system. My ups.conf looks like this: [ups1] driver = bcmxcp_usb port = auto desc = PowerWare 9120 When testing the driver with upsdrvctl -u root start I get: Network UPS Tools - UPS driver controller 2.0.4 Network UPS Tools - BCMXCP UPS driver 0.10 (2.0.4) Communications with UPS lost: Receive error (Request command): BLOCK: 0, COMMAND: 31! Communications with UPS lost: checksum error! Communications with UPS lost: Receive error (Request command): BLOCK: cb, COMMAND: 31! Model = PW9120 3000VA Firmware = 02.60 Shutdown delay = 120 seconds Communications with UPS lost: Receive error (Request command): BLOCK: fa, COMMAND: 3c! Communications with UPS lost: Receive error (Request command): BLOCK: 81, COMMAND: 33! It looks like you have a problem with the usb connection. Check the cabling. The driver is using a binary protocol with checksum, and is hard on bit errors. The command 31 is asking for the identification block. Command 3c is extended limit block and 33 is tha status block. And as it answer with Modell and seems to start, it reads the Identification block after som errors. When looking at the combatability chart at http://www.networkupstools.org/compat/stable.html it seems the PW9120 is supported by the bcmxcp driver and not bcmxcp_usb. I have however found suggestions that bcmxcp_usb supports the 9120: http://osdir.com/ml/monitoring.nut.user/2006-04/msg00054.html It is not a compatibility error, as it should hang on the same command. And it was developed on a 9120 but serial connected. I have a SNMP card in the 9120, but my understanding is that the NUT SNMP-driver does not allow the UPS to be shut down. This is why I am now turning to USB. Any ideas as to how I can get my setup running? Use hi class usb cables, if You is unable to use the serial version of the driver. Use a short sheelded cable. Don't twist it around the powerlines. Then you should get new version of nut as 2.0.4 is past date. Regards Kjell ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Powerware 9155 with SNMP card
Hi Niels, Den Friday 10 August 2007 13.26.56 skrev Niels Baggesen: On Thu, Aug 09, 2007 at 04:59:13PM +0200, Bernd Markgraf wrote: that's indeed not so good... the ietf mib reports them OL but misses some values. like the 3 input phases, temperature etc and gives me battery.runtime.low of 1 which i think is not that good either... Ooops, I really must bem in here. Long long time ago I have reworked the snmp-ups to handle 3-phase for both IETF and PowerWare mibs, but I never gor around to committing them. Actually I have used them in production for more than a year now :-( (on a PW 9390 with SNMP card) On the other hand, I am off for three weeks of vacation starting sunday so even it I could commit them to the trunk, I will not be around to handle any horrors this may result in. So I see two options: either I commit it, and leave the rest of you with sorting any problems out, or I just mail my patch to relevant persons on this list ... I think you should commit to the trunk. In that way Bernd may test it and hopfully be tested on some other ups'es. And as you have used it in production for more than a year I think it's time for a commit. Regards Kjell ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Nut fsd command ignored: bcmxcp_usb driver, Powerware 5105 UPS
Den Thursday 26 July 2007 01.19.00 skrev Stuart Rackham: Hi Hi Stuart, I'm having a problem with the bcmxcp_usb driver FSD command: everything seems to work apart from: upsmon -c fsd 8snip This part have been answered. One peculiarity -- even though the test.battery.start instant command is listed it puts this in the log: Jul 24 23:08:11 kea bcmxcp_usb[5221]: [test.battery.start] not supported Any help would be appreciated. Yes this is OK, the 3105 is not supporting this command. The plan is to parse the command block and only enable commands supported by the ups. Larger ups'es have many more commands then the driver include. Regards Kjell (bcmxcp developer) ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Microdowell (cpsups) driver segfault
Den Tuesday 19 June 2007 13.12.48 skrev [EMAIL PROTECTED]: Hello All Hi Varain, I have a MicroDowell ups (BBox BP 1000) connected to a Gentoo box by serial cable. If I try to start the driver , I see the following : Network UPS Tools - CyberPower text protocol UPS driver .05 (2.0.5) Warning: This is an experimental driver. Some features may not function correctly. debug level is '13' ups_sync: send [\rP4\r] ups_sync: got ret 46 [#1000VA,2.107,,CYBER POWER] ups_sync: got line beginning with #, looks usable, returning get_ident: got [#1000VA,2.107,,CYBER POWER] Detected MicroDowell B.Box BP 1000 2.107 on /dev/ttyS0 Segmentation fault It segfaults no matter what compilation options I select, or if I use upsdrvctl or launch the driver directly. Anyone have any ideea what I'm doing wrong ? (If this belongs to the -dev list, just say so ... ) Are you running a 64bit computer ? This is what i found on the mailing list http://lists.alioth.debian.org/pipermail/nut-upsuser/2006-July/001363.html Don't know if this is resolved yet. But the problem is if you take it to the developer list, they want you to run 2.2.0-pre1 and there is no official ebuild for this yet. I have a modified ebuild in overlay that i may send to you, if you would like to test the 2.2.0-pre1. Regards Kjell (developer bcmxcp driver) ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Microdowell (cpsups) driver segfault
Den Wednesday 20 June 2007 07.21.57 skrev [EMAIL PROTECTED]: 8snip--- Thank you, but for now I'll try the powerpanel driver (as Arjen advised). I'll let you know if things work out. Yes there have been some changes to the drivers. Some have merged into new and some have support for other ups'es. So I think that Arjen's advise is the right one. As an experiment, if I compile just the driver from 2.2.0-pre1 (with the required options), can I expect it to work ? (assuming the problem was solved in this version) Don't think this would work as the codebase have changed from 2.0 to 2.2. Regards Kjell ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] [Nut-upsdev] Belkin USB UPSes
OK Eric, Den Tuesday 22 May 2007 08.56.08 skrev Eric S. Raymond: Kjell Claesson [EMAIL PROTECTED]: Or install the udev rules and replug the ups. Did that. Manual startup of the driver now works without -u root, indicating (I think) that the udev rools are doing their job. This 8---Snip /proc/bus/usb/002: total 0 crw-rw-r-- 1 root root 189, 128 2007-05-18 01:47 001 crw-rw-r-- 1 root nut 189, 130 2007-05-22 02:46 003 /proc/bus/usb/003: total 0 crw-rw-r-- 1 root root 189, 256 2007-05-22 02:44 001 also indicates that permissions look OK. However, starting with upsdrvctrl still reports driver startup failing with exit 1. What other things besides permissions errors can cause this? Normaly it should say something more than 'exit 1'. Did You install from svn ? And if so, did You set the state_path during configure. You may be missing or having the wrong rights on that directory. Default it should be /var/state/nut/. This directory holds the driver socket, and if it don't exist it would make the upsdrvctrl exit with a error. (I plan to submit a patch for the installation instructions if we can figure this out, so your advice will benefit the next person to trip over this, too.) Take care that there is difference depending on udev version and libusb. As ther was changes around the access to /proc in the kernel, this is changed in the udev. So now it makes devices under /dev/bus/usb/xxx And for libusb, Quote: * Fri Jan 27 2006 Jindrich Novy [EMAIL PROTECTED] 0.1.11-2 - change device search order, /dev/bus/usb is tried first, then /proc/bus/usb, and never try /sys/bus/usb (#178994) Unquote This was released in libusb 0.1.12 so now the device is /dev/bus/usb/00x/00x The /proc/bus/usb/xxx/xxx is setup to belong to root:usb now. Regards Kjell P.S. Peter Selinger made me change mail client. Didn't notice that it was not cc'd to the list. ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Powerware Prestige 1000VA
Hi Steve, Just updated the trunk, so do an 'svn up' to update the trunk. Follow the advise from Peter. Was not thinking about the configure flags. So run 'configure --help' and set the paths. Regards Kjell sön 2007-05-20 klockan 09:14 +0100 skrev [EMAIL PROTECTED]: Hi Kjell, Kjell Claesson wrote: You don't have the Battery_low alarm. Ah yes, I see what you mean - never spotted that. 0015 BATTERY_TOTALLY_DISCHARGED Yes It does have this alarm though, which is probably not half as useful! Thanks very much for the patch - I'll try it as soon as I get the source to compile on my system. -Steve ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Powerware Prestige 1000VA
Hi, lör 2007-05-19 klockan 14:24 +0100 skrev [EMAIL PROTECTED]: Hi all, I've more-or-less got NUT 2.0.4 working with my Powerware Prestige 1000VA UPS (serial), but unfortunately NUT is flagging LOW_BATTERY continuously, which is a tad embarrassing when power fails ;-) Can you upgrade to 2.0.5, or any better if you can use the svn trunk. There is a bug in 2.0.4 in the shutdown, so the shutdown delay would not work as expected. And in 2.0.5 I use the topologi block that is not present in older ups'es using the bcmxcp protocol. But this is fixed in the svn trunk. But the error you get come from another thing. Some powerware ups'es signaling the OB an LB via the alarm block. So the driver is made to check if the alarm is present, then it use this to set the LB status. There may be a different alarm-map in your ups. Start up the driver like this. /pat/to/bcmxcp -DD -a blah And sen me the output then i can see what alarms you have. The numbers from upsc [EMAIL PROTECTED] seem reasonable: ambient.temperature: 24.5 battery.charge: 99 battery.runtime: 3999 battery.voltage: 69.2 driver.name: bcmxcp driver.parameter.port: /dev/ttyS0 driver.version: 2.0.4 driver.version.internal: 0.10 input.frequency: 50.0 input.voltage: 239.0 output.frequency: 50.0 ups.firmware: 02.07 ups.load: 0.2 ups.model: Powerware Prestige 1000VA ups.power.nominal: 1000 ups.serial: ** ups.status: OL LB ups.voltage.nominal: 240 but I suspect the 'LB' in ups.status is the clue. Does this indicate low battery? I'm curious as the battery charge is shown as 99% and the battery voltage is OK (for the 5x 12V batteries is has). Could it be the battery pack has failed self-test? Any clues gratefully received! Regards Kjell ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] writing variables
Hi Russ fre 2007-05-18 klockan 11:16 -0400 skrev Russ Romano: Can anyone give me insight into upsrw? I have a cyberpower PR2200 UPS (running an experimental version of the powerpanel driver hot off the presses by Arjen (thanks Arjen!!)). When I try to run upsrw -s xyz=abc to set any available variable, I get Set variable failed: Access denied. What user name and password is it looking for here? My upsd.users file has 2 users configured, one for local master use, and one for remote slave use. I tried the master username/password and the result is the same. I've tried system username/password with no luck. There doesn't seem to be much documentation on upsrw, and even the man page just refers to username and password without giving a scope as to what kind of username/password is expected and how to define it in upsd.users. It look's like this. [monuser] password = pass allowfrom = localhost actions = set instcmds = all upsmon master The line 'instcmds = ALL' tell the daemon that user 'monuser' with password 'pass' can run all commands. The line 'actions = set' gives the monuser rights to set variables. Try 'man upsd.users' for more info. Regards Kjell ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Tripp Lite SMART2200RMXL2U and Fedora Core 6 (NUT 2.0.3)?
Hi Andreas. Sorry to say but this is just brought to our attention on the development list (2 hours ago). This ups seems to have a different product id. It means that it maybe using different protocols. So switch to development list and follow up on the discussion. Regards Kjell fre 2007-05-11 klockan 13:56 -0400 skrev Andreas Meyer: Hi, I'm running Fedora Core 6 and need to monitor a Tripp Lite SMART2200RMXL2U. I've loaded the nut-2.0.3-2.1 RPM. The UPS is connected via the provided USB cable, and that much appears to work: # dmesg | grep -i tripp hiddev96: USB HID v1.10 Device [Tripp Lite TRIPP LITE SMART2200RMXL2U ] on usb-:00:1f.4-2 # lspci | grep -i usb 00:1f.4 USB Controller: Intel Corporation 82801BA/BAM USB (Hub #2) (rev 01) # lsusb Bus 001 Device 003: ID 09ae:3012 Tripp Lite Bus 001 Device 001: ID : However, the tripplite_usb driver doesn't seem to find the UPS: # tripplite_usb -u root -DD auto Network UPS Tools - Tripp Lite OMNIVS and SMARTPRO driver 0.6 (2.0.3) Warning: This is an experimental driver. Some features may not function correctly. debug level is '6' Checking device (09AE/3012) (001/003) - VendorID: 09ae - ProductID: 3012 - Manufacturer: Tripp Lite - Product: TRIPP LITE SMART2200RMXL2U - Serial Number: 9550ALCSM538900465 - Bus: 001 Trying to match device Device does not match - skipping Checking device (/) (001/001) - VendorID: - ProductID: - Manufacturer: Linux 2.6.18-1.2798.fc6 uhci_hcd - Product: UHCI Host Controller - Serial Number: :00:1f.4 - Bus: 001 Trying to match device Device does not match - skipping No appropriate HID device found No matching USB/HID UPS found I've also tried various combinations of -x product=3012 and -x vendor=09ae to no avail. Suggestions? Thanks, Andy ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] HP R3000 XR, warning or perhaps error
Hi ons 2007-04-18 klockan 15:51 +0800 skrev Gregory Orange: Arnaud Quette wrote: 2007/4/17, Kjell Claesson [EMAIL PROTECTED]: It all seems to work but the initial errors or warnings concern me. I'm running stable 2.05 built from source. This come from the baudhunting function in the driver. If you set the baud_rate in the ups.conf to 9600 You don't get this errors. ... can't this be filtered to avoid user confusion? Yes. I take this up of list with Arjen. The error is due to the fact that is use the 'normal' communication function during baudhunting. And it test to communicate 3 times before it say that it lost the communication. And because it try on the wrong speed it fails all attempt and cast an error. (Oops, sending to list this time) Or for another suggestion, the message could be changed to something like: No baud rate specified in UPS configuration file ups.conf, attempting baud rate auto detection... Attempting communication at 2400 baud... failed Attempting communication at 4800 baud... failed Attempting communication at 9600 baud... success That would make it look less like debug info and more like useful output for a user like me who is somewhere in between naive and proficient. This could be done. Regards Kjell ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Compaq T2400H UPS model 242688-006
ons 2007-04-04 klockan 16:23 +1200 skrev Douglas Pearless: Hi, Hi Douglas, I have a Comapq T2400H model 242688-003 and do not have the special cable to connect it to my serial port. I have tried all sorts of cable wirings that I found on the net, including ones for the powerware 5119 which appears to be the same model. OK, I think you have seen this :-) - Part# 295245-003 (PowerRite Pro) Software: FailSafe-III UPS DB-9M DB-9F RS-232 Receive 1 --- 3 TxD Transmit 2 --- 2 RxD Common 4 --- 5 SG PnP_En 6 --- 7 RTS + 4 DTR + 6 DSR -- And this should be the cable. And it is for smart mode, so you can not use it with the generic driver. I have read the documentation that comes with NUT, tried to read the source code and looked at the genericups code too. I have hit a bit of a wall, does anyone have the pinout for a working cable for this unit that works in the dumb or smart mode, and the ups.conf they used?? This type of ups is talking upscodeII, so you need to test the upscode2 driver. If it acts like a T1500h you may need to add 'use_pre lf' into the 'ups.conf'. ups.conf should look something like this. [compaq] driver = upscode2 port = /dev/ttyS0 desc = Compaq T2400h manufacturer = Compaq input_timeout = 5 use_pre_lf = yes Regards Kjell P.S. Send you a pdf of list. ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Compaq T2400H UPS model 242688-006
Hi Douglas, tor 2007-04-05 klockan 08:08 +1200 skrev Douglas Pearless: Debian, latest stable, upsdrvctl --version gives 2.0.1 Cheers Douglas. That's not so good. The upscode2 driver was entered into the 2.0.2 release. And nut is now on 2.0.5 in stable (Minus a bug in the bcmxcp driver :-) ) And what i know, Arnaud have made some packages for Debian. http://packages.debian.org/cgi-bin/search_packages.pl?searchon=namesversion=allexact=1keywords=nut Regards Kjell P.S. Hope you can 'aptget' a unstable or testing package. Charles Lepple wrote: On 4/4/07, Douglas Pearless [EMAIL PROTECTED] wrote: Well, I have made the cable. I had a fresh install of debian and I had used synaptic to install the latest version of NUT and created a ups.conf per earlier instructions. Any time you're tempted to say the latest version, please mention the version number as well. In Debian, it also helps to know which distribution you are tracking (stable, testing, unstable; or sarge, etch, etc.) and also the revision of the package (e.g. the -1 on 2.0.5-1). thanks, ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Re: Nut-upsuser Digest, Vol 21, Issue 29
OK Arjen, I think i need more time in my bed. tor 2007-03-29 klockan 08:42 +0200 skrev Arjen de Korte: THANKS, but the 'megatec' driver only works whith windows OS via USB, and i need it for red hat OS with USB-serial connection... No need to be upset, what Arjen de Korte was referring to was that the ups use the megatec protocol. Yes. And since you appear to be using a USB-to-serial converter, you should use the 'megatec' driver from nut-2.0.5. But as the megatec_usb driver is new in the NetworkUpsTools he say that you need to build it from source. No. Apparently, the UPS has a serial connection and is connected through an USB-to-serial converter, so the megatec_usb driver can't be used. You need the 'megatec' driver from nut-2.0.5. Yes you are right. Was missing the point that the interface acted like a usb-to-serial converter. So it would work with the megatec driver. So it would be possible to test with nut-2.0.4 if you get hold of an rpm for RH9. There is no new RPM's for RH9 that include this driver. There may be RPM's for RH9 for nut-2.0.5. I don't know, I only have RPM's for openSUSE. Anyone? Best regards, Arjen Regards Kjell ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] snmp ups Status: Not supported
Hi, tor 2007-03-29 klockan 18:24 +0200 skrev Massimo Martinelli: Alle 20:22, mercoledì 28 marzo 2007, Kjell Claesson ha scritto: Yes the status is used for shutting down the system. So it would be needed to make a correct shutdown . I noticed that you are running version 2.0.4. I think there have been some changes made to the snmp in 2.0.5 so if you could upgrade and test if it reports status. Good call, Kjell I upgraded to nut-snmp 2.0.5 and now status is displayed correctly. Thanks ! now i just need to figure how to install that version on my ubuntu dapper production server ... ;) Can you use this ? http://packages.ubuntulinux.org/feisty/admin/nut-cgi /Kjell ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] snmp ups Status: Not supported
Hi Massimo, ons 2007-03-28 klockan 16:36 +0200 skrev Massimo Martinelli: Hi I set up my ups with driver snmp-ups, and it get recognized as a AEC T2003. In the nut-cgi upstats page input/output/load are displayed corectly, but the Status field is marked as Not supported. Is Status important to initiate shutdown in case of low battery ? Will my server shut down correctly ? Yes the status is used for shutting down the system. So it would be needed to make a correct shutdown . I noticed that you are running version 2.0.4. I think there have been some changes made to the snmp in 2.0.5 so if you could upgrade and test if it reports status. I'm not familiar to the snmp driver but i noticed that there have been some changes made to the ietf mib for 2.0.5. But i can't find anything in the changelog. But Niels Baggesen have made many changes in the trunk. So if the 2.0.5 does not work, You may try the development trunk from svn. Regards Kjell thanks Massimo I include upsc [EMAIL PROTECTED] output: battery.charge: 100.0 battery.runtime: 000.0 battery.runtime.low: 2 battery.voltage: 013.6 driver.name: snmp-ups driver.parameter.mibs: ietf driver.parameter.pollfreq: 15 driver.parameter.port: ups.printertrento.it driver.parameter.snmp_version: v1 driver.version: 2.0.4 driver.version.internal: 0.41 input.frequency: 050.0 input.voltage: 400.0 output.voltage: 4000.0 ups.firmware.aux: 2.38.DK520 ups.load: 047.0 ups.mfr: AEC T2003 ups.model: T2003 ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Re: Nut-upsuser Digest, Vol 21, Issue 29
Hi Gonzalo, ons 2007-03-28 klockan 16:22 -0300 skrev gonzalo campuris: THANKS, but the 'megatec' driver only works whith windows OS via USB, and i need it for red hat OS with USB-serial connection... No need to be upset, what Arjen de Korte was referring to was that the ups use the megatec protocol. But as the megatec_usb driver is new in the NetworkUpsTools he say that you need to build it from source. There is no new RPM's for RH9 that include this driver. So grab the svn and the development trunk. You would need the usblib and som development packages installed to build it. Regards Kjell Please, anybody can help me [EMAIL PROTECTED] escribió: Send Nut-upsuser mailing list submissions to nut-upsuser@lists.alioth.debian.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser or, via email, send a message with subject or body 'help' to [EMAIL PROTECTED] You can reach the person managing the list at [EMAIL PROTECTED] When replying, please edit your Subject line so it is more specific than Re: Contents of Nut-upsuser digest... Today's Topics: 1. Re: UPSilon 2000 via USB linux (Arjen de Korte) -- Message: 1 Date: Wed, 28 Mar 2007 12:34:24 +0200 (CEST) From: Arjen de Korte Subject: Re: [Nut-upsuser] UPSilon 2000 via USB linux To: gonzalo campuris Cc: nut-upsuser@lists.alioth.debian.org Message-ID: [EMAIL PROTECTED] Content-Type: text/plain;charset=iso-8859-1 This list is for the Network UPS Tools (NUT) software, but this log looks like it is from something else entirely. The RPMs listed on rpmfind.net for RH9 seem very old, so you will probably need to compile from source: http://www.networkupstools.org/source.html Then, since your UPS is not listed in the compatibility list, you probably need to try a few drivers, such as megatec. UPSilon 2000 is mentioned on http://www.megatec.com.tw/Download.htm which suggests that the 'megatec' driver is indeed the right one. Best regards, Arjen -- Eindhoven - The Netherlands Key fingerprint - 66 4E 03 2C 9D B5 CB 9B 7A FE 7E C1 EE 88 BC 57 -- ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser End of Nut-upsuser Digest, Vol 21, Issue 29 *** __ Preguntá. Respondé. Descubrí. Todo lo que querías saber, y lo que ni imaginabas, está en Yahoo! Respuestas (Beta). Probalo ya! ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Starting Network UPS Tools: (upsdrvctl failed) upsd upsmon ?
Hi Theo, You can try to run the driver only with the ups.conf. Locate the bcmxcp_usb driver. then run this command. /path/to/bcmxcp_usb -DD -a powerware (exchange the /path/to with the right path) Now it should spit out som debug info if the communication is ok. You should also upgrade to the 2.0.5 version as (think it was) Arjen found one bad typo in the shutdown functions. Also you should set the shutdown_delay to 60 in the ups.conf as it warns that it could not run more than 60 sec after it signaling low battery. This time is used to power off the ups after a low battery warning. So it should give a shutdown -h now on battery low, then run for 60 sec and power off. Normal a machine should manage to go down to halt in this time. But with 2.0.4 it would not power off (se above). Regards Kjell lör 2007-03-24 klockan 10:35 +0100 skrev Theo G. Kanter: Using the HOWTO in http://keystoneit.wordpress.com/2006/09/25/network-ups-tools-nut-on-ubuntu/ I installed nut on an Ubuntu Edgy LAMP Server with an Eaton Powerware 5110 attached to it via usb. But nut fails to start properly (see the error message Starting Network UPS Tools: (upsdrvctl failed) upsd upsmon below). It then complains about communication with the UPS being lost (UPS [EMAIL PROTECTED] is unavailable). I wonder whether this communication error message may be related to the howto assuming that a user 'upsl' exists, while 'nut' only configures a user 'nut'. I am new to 'nut' so any hints are welcome. I have no clue why upsdrvctl fails when I start nut when it first starts properly by itself. Below I included the configuration files (found in /etc/nut/*) Please advise me on how to deal with both these issues. # upsdrvctl start Network UPS Tools - UPS driver controller 2.0.4 Network UPS Tools - BCMXCP UPS driver 0.10 (2.0.4) Model = POWERWARE UPS1000VA Firmware = 00.50 Shutdown delay = 120 seconds Shutdown delay longer than battery capacity when Low Battery warning is given. (max 60 seconds) # /etc/init.d/nut start Starting Network UPS Tools: (upsdrvctl failed) upsd upsmon. Broadcast Message from [EMAIL PROTECTED] (somewhere) at 9:48 ... Communications with UPS [EMAIL PROTECTED] lost --- /etc/nut/ups.conf --- [powerware] driver = bcmxcp_usb port = auto desc = PowerWare 5110, USB --- /etc/nut/upsd.conf --- ACL all 0.0.0.0/0 ACL remote 192.168.0.0/24 ACL localhost 127.0.0.1 ACCEPT localhost ACCEPT remote REJECT all --- /etc/nut/upsd.users [monuser] password = PASSWORD allowfrom = localhost actions = SET instcmds = ALL upsmon master --- /etc/nut/upsmon.conf MONITOR [EMAIL PROTECTED] 1 monuser PASSWORD master SHUTDOWNCMD /sbin/shutdown -h +0 Thanks in advance. --theo ([EMAIL PROTECTED]) ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Problem with HP R3000 XR
Hi Paul. Yes this is a bugg entered into the stable release. It was noticed after the 2.0.5 release by Henning Brauer. If you would apply the attached patch it would fix this. Just gunzip it and place it in the nut source directory and do a patch -p1 bcmxcp.patch Now build and try it out. Regards Kjell Claesson tor 2007-03-01 klockan 09:37 +1100 skrev Paul Battaglia: Hi All, I'm trying to communication with the HP r3000 XR UP using the latest stable build and I'm getting the following errors. Can anyone enlighten me with the errors below and what other course of action I can take. Thanks in advance. Paul. [EMAIL PROTECTED] etc]# /usr/local/ups/bin/upsdrvctl start Network UPS Tools - UPS driver controller 2.0.5 Network UPS Tools - BCMXCP UPS driver 0.11 (2.0.5) Communications with UPS lost: Error executing command Communications with UPS lost: Error executing command Communications with UPS lost: Error executing command Communications with UPS lost: Error executing command Communications with UPS re-established Connected to UPS on /dev/ttyS0 baudrate: 19200 Communications with UPS lost: Receive error (Request command): 9!!! Communications with UPS lost: Receive error (Request command): 9!!! Communications with UPS lost: Receive error (Request command): 9!!! Communications with UPS lost: Error executing command Could not communicate with the ups Driver failed to start (exit status=1) -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.412 / Virus Database: 268.18.5/706 - Release Date: 28/02/2007 ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser bcmxcp.patch.gz Description: GNU Zip compressed data ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Powerware 5110
Hi Steve. sön 2007-02-04 klockan 03:30 +1100 skrev Steve Simeonidis: I have an FC5 system with a powerware 5110 usb ups. The system seems to find the UPS -- [EMAIL PROTECTED] src]# lsusb Bus 004 Device 001: ID : Bus 003 Device 002: ID 0592:0002 Powerware Corp. Bus 003 Device 001: ID : Bus 002 Device 001: ID : Bus 005 Device 001: ID : Bus 001 Device 001: ID : --- [EMAIL PROTECTED] src]# cat /proc/bus/usb/devices .. T: Bus=03 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=1.5 MxCh= 0 D: Ver= 2.00 Cls=00(ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=0592 ProdID=0002 Rev= 0.50 S: Manufacturer=Powerware S: Product=Powerware UPS C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=100mA I: If#= 0 Alt= 0 #EPs= 1 Cls=ff(vend.) Sub=00 Prot=00 Driver=(none) E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=20ms - Yep that looks OK. I have set the port to auto but I can not make it work What do I need to set the port to? The ups.conf should look something like this. [pw5110] driver = bcmxcp_usb port = auto shutdown_delay = 60 desc = USB ups Now try to start the driver like this. /sbin/bcmxcp_usb -a pw5110 If it spit out something like this Network UPS Tools - BCMXCP UPS driver 0.11 (2.0.5) Model = POWERWARE UPS500VA Firmware = Cont:00.80 Inve:00.60 Shutdown delay = 60 seconds Then it is ok. If not then check the you have the right udev rules installed. Kjell ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] initial configuration assistance
Hi Gregory, tis 2007-01-30 klockan 14:43 +0900 skrev Gregory Orange: Hi, I've browsed the archives back for a few months and nothing has jumped out at me as being helpful, but since there doesn't seem to be a search facility it's certainly possible I've missed what I'm looking for. Anyway, I wonder if someone can help me. I've very recently installed nut 2.0.4-r1 on a gentoo box and am in the initial stages of configuration and testing. Our APC Smart-UPS 3000 is connected with a 940-0024C serial cable, which seems to be a good one to use - I firstly removed the 940-1524C cable which happened to be dangling from the UPS. I've configured upsd.conf with [rack1ups] driver = apcsmart cable = 940-0024C port = auto desc = Rack 1 UPS and left most other files as default, except for following some parts of doco on initial setup. The port should be set to /dev/ttyS0 if you use the first com port. Then depending on the udev version the tty is owned by the tty group or the uucp group. Check by ls -al /dev/ttyS0. Add the nut user to the right group in /etc/group. This is more easy then trying to fix the udev rule. The problem: When I /etc/init.d/upsd start, I get this: Network UPS Tools upsd 2.0.4 Can't connect to UPS [rack1ups] (apcsmart-auto): No such file or directory Synchronizing giving up Try to start the driver first. /etc/init.d/upsdrv start Check that it is running and that it don't fail. Then start the deamon if it is ok. /etc/init.d/upsd start I'm running Gentoo ~X86 and use a homemade ebuild for nut-2.0.5 with some patches that i entered into the development trunk. Regards Kjell ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Fwd: Re: [Nut-upsuser] Recommendation for big UPS (was CyberPower PR2200)]
Hi Doug, ons 2006-11-15 klockan 22:22 -0500 skrev Doug Reynolds: 8snip I haven't figured out what the F060 or the 0S is. they always stayed the same. when the UPS went dead and turned off, it would still reply with the same reply, but all the numbers were zeros.€€ 8snip I think the F is line frequency 60Hz. Regards Kjell ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
