Re: [Nut-upsuser] Support of amp; amp; amp; quot; shutdown.returnamp; amp; amp; quot; on a APC Back-UPS CS 500

2011-01-19 Thread Arjen de Korte

Citeren Kevin Myers bakd...@gmail.com:

As far as I can tell from your previous message, it works (with  
nut-2.6.0) for the Smart-UPS 1000, right?
No, although it does go into sleep mode if the power is off at the  
right time, it doesn't cycle the power otherwise so the load will  
not reboot after the shutdown. I'll do some more testing today.


Please also post the output of 'upsc upsname' (see 'man 8 upsc') and  
'upscmd -l upsname' (see 'man 8 upscmd') for both devices, so that we  
can see which commands are detected.


It may be a log easier to do the testing with the upscmd  
'shutdown.return' (Smart-UPS 1000) and 'shutdown.reboot' (CS-500)  
while the upsd server is running. During testing, it allows you to run  
an instance of upslog (see 'man 8 upslog') so that you'll be able to  
see the 'ups.timer.*' variables counting down. I suspect that the  
current mapping might be wrong.


Also note that the (re)start delay set in the Smart-UPS 1000 is  
presently set to 180 seconds, so you may have to wait a little longer  
that expected for the output to be switched on after the power returns.


Best regards, Arjen
--
Please keep list traffic on the list (off-list replies will be rejected)


___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser


Re: [Nut-upsuser] Support of amp; amp; amp; quot; shutdown.returnamp; amp; amp; quot; on a APC Back-UPS CS 500

2011-01-19 Thread Kevin

on 19/01/2011 15:31 Arjen de Korte wrote:
Please also post the output of 'upsc upsname' (see 'man 8 upsc') and 
'upscmd -l upsname' (see 'man 8 upscmd') for both devices, so that we 
can see which commands are detected.


It may be a log easier to do the testing with the upscmd 
'shutdown.return' (Smart-UPS 1000) and 'shutdown.reboot' (CS-500) 
while the upsd server is running. During testing, it allows you to run 
an instance of upslog (see 'man 8 upslog') so that you'll be able to 
see the 'ups.timer.*' variables counting down. I suspect that the 
current mapping might be wrong.


Also note that the (re)start delay set in the Smart-UPS 1000 is 
presently set to 180 seconds, so you may have to wait a little longer 
that expected for the output to be switched on after the power returns.


Thanks Arjen. I've spent a little more time on it today and can confirm 
that shutdown.reboot works as expected with the Smart-UPS 1000. (I only 
tested this by commenting out the shutdown.return code in the usbhid-ups 
driver) I will try with the upscmd command tomorrow.


This matches and confirms the behaviour of the 2.4 versions.

It is easy to tell when this is working properly, as both of the units 
have a flashing light sequence that signifies they are going into sleep 
mode.


As an aside, I gather that all the APC units will now switch into sleep 
mode automatically at a specific low battery state, so actually 
switching off as a last resort may be counter productive.


I haven't been able to get the CS 500 into sleep mode at all, apart from 
by using the old hidups driver that I modified to setvalue(0x86007c, 1) 
The 2.6 version shutdown.reboot definitely does not work - it doesn't 
seem to have any effect at all.


I will post the further information you have asked for tomorrow and also 
experiment with the upslog. I haven't seen output matching 'ups.timer' 
from this before, there must be a verbose command I haven't found yet.


Regards,
Kevin.

___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser