Re: [Nut-upsuser] upsrw doesn't set variable
It is similar to my question. I also can't set delay variables on outlet 1 or 2. And when I ask the ups to load off delay. It´s always 60s. Which I can't change. I use the usb-hid driver. Logmessage reports back: OK But nothing gets set when you refresh the variables. On the usb-bus the UPS continuously disconnects and reconnects again. Where the cause of this behaviour is the USB card in the UPS, I think/thought. Due to a bad connection in the soldering or something. When this occurs, also the 5v line on the UPS USB card dropped to 3V. But this also can be normal behaviour, I don't really know. I also gave it a try with the HP software on a XP machine. Only I used the RS232 cable. And I also couldn't set output variables. So, I presumed it has something to do with the UPS. Only I didn't disconnect the USB. Pascal. ___ 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
On 6/29/2013 at 9:14 AM Mike. wrote: |NUT 2.6.5 on FreeBSD 9.1 | | |Why isn't the variable outlet.1.delay.shutdown set with the following |command? | | | |# upsc PW5125@localhost | grep outlet.1.delay.shutdown |outlet.1.delay.shutdown: -1 | |# upsrw -u au -p ap -s outlet.1.delay.shutdown PW5125@localhost |Enter new value for outlet.1.delay.shutdown: 10 |OK | |# upsc PW5125@localhost | grep outlet.1.delay.shutdown |outlet.1.delay.shutdown: -1 | | | | |Am I missing something obvious? = Forgot to add ups.conf: [PW5125] driver = bcmxcp port = /dev/cuau0 baud_rate = 9600 desc = PW 5125 - 1500 ___ 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
On Jun 29, 2013, at 9:45 AM, Mike. wrote: On 6/29/2013 at 9:14 AM Mike. wrote: |NUT 2.6.5 on FreeBSD 9.1 | | |Why isn't the variable outlet.1.delay.shutdown set with the following |command? | | | |# upsc PW5125@localhost | grep outlet.1.delay.shutdown |outlet.1.delay.shutdown: -1 | |# upsrw -u au -p ap -s outlet.1.delay.shutdown PW5125@localhost |Enter new value for outlet.1.delay.shutdown: 10 |OK | |# upsc PW5125@localhost | grep outlet.1.delay.shutdown |outlet.1.delay.shutdown: -1 | | | | |Am I missing something obvious? = Forgot to add ups.conf: [PW5125] driver = bcmxcp port = /dev/cuau0 baud_rate = 9600 desc = PW 5125 - 1500 I was just going to gripe about the lack of driver information :-) Sounds similar to Pascal's question: http://lists.alioth.debian.org/pipermail/nut-upsuser/2013-June/008462.html Do you see anything from syslog at LOG_NOTICE? In theory, the bcmxcp driver should log a message if the parameter change is refused by the UPS. If not, you could try re-running the driver with a few -D flags. That will show some information on the commands and responses. We also have a bcmxcp branch that has a few fixes beyond v2.6.5, but none of them seem particularly relevant. Arnaud mentioned that some of the PowerWare devices have a USB HID interface that may be more fully mapped out. If you have a USB port on the UPS, you could try changing the parameter with usbhid-ups, then switching back to bcmxcp for long-term monitoring. -- Charles Lepple clepple@gmail ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] upsrw doesn't set variable
On 6/29/2013 at 9:59 AM Charles Lepple wrote: |On Jun 29, 2013, at 9:45 AM, Mike. wrote: | | On 6/29/2013 at 9:14 AM Mike. wrote: | | |NUT 2.6.5 on FreeBSD 9.1 | | | | | |Why isn't the variable outlet.1.delay.shutdown set with the following | |command? | | | | | | | |# upsc PW5125@localhost | grep outlet.1.delay.shutdown | |outlet.1.delay.shutdown: -1 | | | |# upsrw -u au -p ap -s outlet.1.delay.shutdown PW5125@localhost | |Enter new value for outlet.1.delay.shutdown: 10 | |OK | | | |# upsc PW5125@localhost | grep outlet.1.delay.shutdown | |outlet.1.delay.shutdown: -1 | | | | | | | | | |Am I missing something obvious? | = | | | Forgot to add ups.conf: | | | [PW5125] | driver = bcmxcp | port = /dev/cuau0 | baud_rate = 9600 | desc = PW 5125 - 1500 | | |[snip] | |Do you see anything from syslog at LOG_NOTICE? In theory, the bcmxcp |driver should log a message if the parameter change is refused by the UPS. | |If not, you could try re-running the driver with a few -D flags. That will |show some information on the commands and responses. | |We also have a bcmxcp branch that has a few fixes beyond v2.6.5, but none |of them seem particularly relevant. | |Arnaud mentioned that some of the PowerWare devices have a USB HID |interface that may be more fully mapped out. If you have a USB port on the |UPS, you could try changing the parameter with usbhid-ups, then switching |back to bcmxcp for long-term monitoring. | |-- |Charles Lepple |clepple@gmail = 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 Curious that the command gives an OK response, even though it logs a failure. 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. ___ 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
On 6/29/2013 at 6:16 PM Kjell Claesson wrote: |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. = 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) 14.261271 entering setvar(outlet.1.delay.shutdown, 12) 14.261318 send_command: (7 bytes) = ab 04 cf 69 e8 d5 5c 16.261647 send_command: (8 bytes) = ab 05 97 01 01 0c 00 ab 16.318194 Set [outlet.1.delay.shutdown 12] failed due to invalid parameter 16.318245 send_command: (4 bytes) = ab 01 34 20 16.574540 send_command: (4 bytes) = ab 01 41 13 16.658312 init_outlet(14), res=14 16.658346 Number of outlets: 2 16.658358 Number of bytes: 6 16.658369 Outlet number: 1 16.658388 Outlet state: 1 16.658406 Auto delay off: -1 16.658432 Auto delay on: 1 16.658461 Outlet number: 2 16.658477 Outlet state: 1 16.658496 Auto delay off: -1 16.658525 Auto delay on: 2 [snip] Let me know if there is anything else I should do. Thanks. ___ 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] upsrw doesn't set variable
On 6/29/2013 at 10:49 PM Kjell Claesson wrote: |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. command and log message: upsrw -u au -p ap -s outlet.1.delay.start=3 PW5125@localhost bcmxcp[94366]: Outlet 1 start delay set to 3 sec :) | |I have the same ups here, and it looks like the possibility to set off |delay is not implemented on this type. | :( | |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. | I checked my library, and I have only the user manuals. Thanks for your help. I am going to try loading up Powerware's LanSafe software, and see if that can change the shutdown delay settings, and whether the change will be persistent. But that is for another day... Thanks again. Mike. ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
