On 08/02/2011 14:55, Arjen de Korte wrote:
{ shutdown.return, 0, 0, UPS.Output.APCDelayBeforeReboot, NULL,
1, HU_TYPE_CMD, NULL },
Yes, that does the trick!
# clients/upscmd -u apcmon -p pass123 apc1500 shutdown.return
has the desired effect.
Would you like me to provide any more output?
On 08/02/2011 16:09, Kevin wrote:
The bad news is that the # usbhid-ups -a apc1500 -k -DDD command
doesn't work
Cancel that. I was using the wrong path. It does work fine.
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http
On 08/02/2011 15:50, Arjen de Korte wrote:
Do you have any idea how long the delay is before the device actually
shuts down?
*Further testing:*
When the command is issued
On power:
Switches immediately to battery
Waits 60 seconds
Sleeps for 2 seconds, switches output power off
Restarts
On 08/02/2011 16:48, Arjen de Korte wrote:
That's good to know. It looks like we found the correct mapping. If
this doesn't conflict with known report descriptors, I'll add this to
the development version later today.
For info, I added this line:
{ shutdown.stop, 0, 0,
on 07/02/2011 18:46 Arjen de Korte wrote:
Citeren Kevin bakd...@gmail.com:
Of course not. When do you start listening to my advice? :-(
Arjen,
There is no call for language like that. I've spent a huge amount of
time in the last six weeks trying to sort this problem with your code.
I'll
on 07/02/2011 15:36 Arjen de Korte wrote:
Citeren Kevin bakd...@gmail.com:
Of course. Do as I asked you and it *will* make a difference.
You could have perhaps made a point of the sudden change to a different
command. Others also missed this subtlety.
I did this with the old working
on 07/02/2011 20:46 Arjen de Korte wrote:
Citeren Kevin bakd...@gmail.com:
This is not *my* code. I'm just trying to help here.
As am I.
I would be more
than happy to ditch the APC support from NUT entirely, but due to
popular demand this is just not an option.
Exactly. I am beginning
on 07/02/2011 20:58 Arjen de Korte wrote:
I posted the 'old' and 'new' lines. You might have missed this on the
first look, buy after I told you the difference, you could have looked
again at the original post.
Of course I saw it, after you made it so plain in such a blunt manner.
As I
on 07/02/2011 22:04 Arjen de Korte wrote:
The above is the only reason why we need multiple HID subdrivers in
usbhid-ups. If every UPS vendor would care to implement (and properly
test!) their firmware, we would need exactly one subdriver that would
fit all USB HID Power Device Class UPS'es.
on 06/02/2011 18:19 Arjen de Korte wrote:
Citeren Kevin bakd...@gmail.com:
Seems to have gone a bit quiet. Are we at a dead end now?
No, I just don't have a lot of spare time on my hand lately.
That's ok. I quite understand. Thank you for all your help so far.
You could
try if changing
on 06/02/2011 21:06 Charles Lepple wrote:
It looks like the only uncommented code which talks to the device is
the last line. (The results from the getval() calls do not seem to be
used.)
APCDelayBeforeReboot maps to 0xff86007c, so Arjen's suggestion to
change the 10 to 1 should be equivalent
on 23/01/2011 16:16 Arjen de Korte wrote:
Citeren Kevin bakd...@gmail.com:
I see my error now. The above line should be moved up to before the
first occurence of { ups.delay.shutdown, ... }. The first available
HID path that is found, will set the NUT mapping and there is one before
on 22/01/2011 15:35 Arjen de Korte wrote:
Sorry for the confusion. Yes the value hasn't changed, but I didn't
expect that to happen. It should however be modifiable through 'upsrw',
so that you might be able to set it to a lower value.
In the usbhid-ups driver, the
: No test initiated
ups.timer.reboot: -1
ups.timer.shutdown: 84
ups.timer.start: 244
ups.vendorid: 051d
Regards,
Kevin.
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
on the Smart-UPS 1000.
Ok, and thanks for your efforts. Actually, as I have a working solution on the
Smart-UPS 1000, and not on the CS 500, it is the latter that is more critical
(as I'm currently on standby all the time for when the power goes down!)
Regards,
Kevin
Kevin bakdong at gmail.com writes:
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.
APC Smart-UPS 1000
# clients
Kevin bakdong at gmail.com writes:
Sorry, this is the correct output for the Smart-UPS 1000
# clients/upsc apc1500
battery.charge: 100
battery.charge.low: 10
battery.charge.warning: 50
battery.mfr.date: 2007/07/07
battery.runtime: 6300
battery.runtime.low: 120
battery.temperature: 31.5
Arjen de Korte nut+users at de-korte.org writes:
Citeren Kevin bakdong at gmail.com:
return immediately switches to battery for a moment, sets both shutdown
and startup to 90 seconds, sleeps after 90 seconds
That is very odd. You could try what happens if you change
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
Arjen de Korte nut+users at de-korte.org writes:
Citeren Kevin bakdong at gmail.com:
Have you tried the latest version (nut-2.6.0) that was released only a
couple of days ago? Chances are that it might just work, since we have
seen reports about people running the CS 500 in recent
Arjen de Korte nut+users at de-korte.org writes:
Citeren Kevin bakdong at gmail.com:
0.686325 Initiating UPS shutdown
0.686340 upsdrv_shutdown...
0.686365 instcmd(shutdown.return, [NULL])
0.686382 find_nut_info: unknown info type: shutdown.return
Arjen de Korte nut+users at de-korte.org writes:
It's sad that you never submitted these changes back to NUT, so that
other people might benefit from them.
Yes indeed, although I don't by any means consider myself an expert, and the
changes that I made were just cludges to get the thing
. :-( Is it
any use to you to have the executables?
This has been driving me nuts for the last week, as I now have another CS 500
to
install, and only a 5 year old version of hidups to do it with!
Regards,
Kevin.
___
Nut-upsuser mailing list
Nut
Prior to test: OB LB RB
With mains off: OB LB RB VRANGE
With mains back on: OL CHRG
After a while: OB LB RB
Could anyone suggest a solution?
Thanks.
--
Kevin DeGraaf
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
Do you have a chance to switch off the mains to the UPS for a while
(without causing too much grief to the systems it is powering)
I'll be glad to test this (and post the upsc data) when I return to
work tomorrow.
Thanks.
--
Kevin DeGraaf
___
Nut
/fcntl.h:71: error: syntax error before 'l_pid'
[ ... Snipped; full output at http://kdegraaf.net/nut2.txt ... ]
Am I doing something wrong, or is this system (installed by a former
sysadmin) too old to compile nut-2.0.5?
Thanks.
--
Kevin DeGraaf
the full output of the command (available on
my website) to add support for this model into the development tree? I
could probably bribe someone with an item from an Amazon or Thinkgeek
wish list... :-)
Thanks.
--
Kevin DeGraaf
___
Nut-upsuser mailing
device found
No matching USB/HID UPS found
--
Kevin DeGraaf
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Back-UPS Pro
500/1000/1500
# ls -l /dev/bus/usb/005/009
crw-r--r-- 1 upsd root 189, 520 Jan 18 16:20 /dev/bus/usb/005/009
Any ideas? I'm not sure where in the filesystem upsd is attempting to
write the newhidups-auto socket. Thanks.
--
Kevin DeGraaf
29 matches
Mail list logo
