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
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 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. ============ 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.
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 5cThis is a authorization block that enable us to send a command.> 16.261647 send_command: (8 bytes) => ab 05 97 01 01 0c 00 abThis 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 > parameterNow 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 13This 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.