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 at localhost | grep "outlet.1.delay.shutdown" > |outlet.1.delay.shutdown: -1 > | > |# upsrw -u au -p ap -s outlet.1.delay.shutdown PW5125 at localhost > |Enter new value for outlet.1.delay.shutdown: 10 > |OK > | > |# upsc PW5125 at 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 at gmail
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 at localhost | grep "outlet.1.delay.shutdown"
|> |outlet.1.delay.shutdown: -1
|> |
|> |# upsrw -u au -p ap -s outlet.1.delay.shutdown PW5125 at localhost
|> |Enter new value for outlet.1.delay.shutdown: 10
|> |OK
|> |
|> |# upsc PW5125 at 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 at 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 at 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.
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 at 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
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. ------------- volgend deel ------------ Een HTML-bijlage is gescrubt... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20130630/47c29280/attachment.html>