apcupsd-users Mailing List for Apcupsd UPS control software (Page 2)
Brought to you by:
adk0212
You can subscribe to this list here.
2003 |
Jan
|
Feb
(99) |
Mar
(81) |
Apr
(97) |
May
(53) |
Jun
(77) |
Jul
(156) |
Aug
(103) |
Sep
(124) |
Oct
(168) |
Nov
(74) |
Dec
(124) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2004 |
Jan
(178) |
Feb
(115) |
Mar
(161) |
Apr
(125) |
May
(70) |
Jun
(204) |
Jul
(91) |
Aug
(204) |
Sep
(109) |
Oct
(137) |
Nov
(81) |
Dec
(103) |
2005 |
Jan
(118) |
Feb
(82) |
Mar
(184) |
Apr
(146) |
May
(97) |
Jun
(151) |
Jul
(162) |
Aug
(163) |
Sep
(181) |
Oct
(121) |
Nov
(136) |
Dec
(132) |
2006 |
Jan
(162) |
Feb
(179) |
Mar
(158) |
Apr
(60) |
May
(155) |
Jun
(102) |
Jul
(172) |
Aug
(242) |
Sep
(102) |
Oct
(129) |
Nov
(92) |
Dec
(90) |
2007 |
Jan
(101) |
Feb
(71) |
Mar
(105) |
Apr
(58) |
May
(109) |
Jun
(100) |
Jul
(183) |
Aug
(158) |
Sep
(97) |
Oct
(113) |
Nov
(150) |
Dec
(71) |
2008 |
Jan
(216) |
Feb
(160) |
Mar
(47) |
Apr
(32) |
May
(53) |
Jun
(78) |
Jul
(72) |
Aug
(116) |
Sep
(55) |
Oct
(133) |
Nov
(105) |
Dec
(26) |
2009 |
Jan
(55) |
Feb
(43) |
Mar
(60) |
Apr
(29) |
May
(79) |
Jun
(37) |
Jul
(130) |
Aug
(96) |
Sep
(46) |
Oct
(109) |
Nov
(79) |
Dec
(60) |
2010 |
Jan
(121) |
Feb
(57) |
Mar
(62) |
Apr
(60) |
May
(51) |
Jun
(69) |
Jul
(44) |
Aug
(61) |
Sep
(87) |
Oct
(38) |
Nov
(74) |
Dec
(38) |
2011 |
Jan
(48) |
Feb
(49) |
Mar
(52) |
Apr
(86) |
May
(88) |
Jun
(49) |
Jul
(89) |
Aug
(55) |
Sep
(111) |
Oct
(89) |
Nov
(74) |
Dec
(82) |
2012 |
Jan
(72) |
Feb
(50) |
Mar
(34) |
Apr
(36) |
May
(15) |
Jun
(32) |
Jul
(34) |
Aug
(231) |
Sep
(35) |
Oct
(63) |
Nov
(34) |
Dec
(64) |
2013 |
Jan
(53) |
Feb
(39) |
Mar
(10) |
Apr
(49) |
May
(21) |
Jun
(20) |
Jul
(32) |
Aug
(37) |
Sep
(77) |
Oct
(42) |
Nov
(29) |
Dec
(26) |
2014 |
Jan
(33) |
Feb
(125) |
Mar
(119) |
Apr
(33) |
May
(21) |
Jun
(10) |
Jul
(32) |
Aug
(4) |
Sep
(14) |
Oct
(98) |
Nov
(96) |
Dec
(29) |
2015 |
Jan
(32) |
Feb
(106) |
Mar
(55) |
Apr
(25) |
May
(19) |
Jun
(61) |
Jul
(29) |
Aug
(54) |
Sep
(57) |
Oct
(36) |
Nov
(34) |
Dec
(24) |
2016 |
Jan
(48) |
Feb
(52) |
Mar
(31) |
Apr
(4) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2017 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(11) |
Jun
(8) |
Jul
(60) |
Aug
(9) |
Sep
(9) |
Oct
(10) |
Nov
(60) |
Dec
(17) |
2018 |
Jan
(6) |
Feb
(16) |
Mar
(28) |
Apr
(9) |
May
(2) |
Jun
(17) |
Jul
(74) |
Aug
(8) |
Sep
(6) |
Oct
(43) |
Nov
(22) |
Dec
(20) |
2019 |
Jan
(19) |
Feb
(13) |
Mar
(12) |
Apr
(18) |
May
(14) |
Jun
(28) |
Jul
(59) |
Aug
(11) |
Sep
(2) |
Oct
(58) |
Nov
(11) |
Dec
(9) |
2020 |
Jan
(21) |
Feb
(42) |
Mar
(22) |
Apr
(11) |
May
(4) |
Jun
(7) |
Jul
(8) |
Aug
(16) |
Sep
(15) |
Oct
(6) |
Nov
(5) |
Dec
(14) |
2021 |
Jan
(17) |
Feb
(27) |
Mar
(43) |
Apr
(16) |
May
(31) |
Jun
(16) |
Jul
(24) |
Aug
(31) |
Sep
(42) |
Oct
(2) |
Nov
(58) |
Dec
(42) |
2022 |
Jan
(23) |
Feb
(28) |
Mar
(36) |
Apr
(61) |
May
(1) |
Jun
(33) |
Jul
(4) |
Aug
(10) |
Sep
|
Oct
(17) |
Nov
(27) |
Dec
(8) |
2023 |
Jan
(1) |
Feb
(1) |
Mar
(3) |
Apr
(65) |
May
(7) |
Jun
(10) |
Jul
(23) |
Aug
(3) |
Sep
(5) |
Oct
(6) |
Nov
(7) |
Dec
(16) |
2024 |
Jan
(8) |
Feb
(23) |
Mar
(2) |
Apr
(2) |
May
(5) |
Jun
(2) |
Jul
(31) |
Aug
(3) |
Sep
|
Oct
|
Nov
|
Dec
|
From: Paul L. <pa...@pl...> - 2024-07-23 09:51:42
|
The Smart is substantially more expensive in my part of the world (50% more cost), and for my use didn’t seem justified. I can return this unit for another if it was really worthwhile, but for this particular situation probably isn’t worth it. My main machine is 11 years old, but has no serial port unfortunately. Would an adaptor like this be sufficient, or do I need something special? It says it has a PL2303 RA chipset – is that the genuine thing we’re looking for? https://www.pbtech.co.nz/product/ADPDNX0810/Unitek-BF-810Y-15M-USB-to-Serial-Adapter-DB9-RS232 Or do I need a genuine APC cable – I see some talk about those, but I don’t see a USB-serial cable. Is there any magic driver I need on linux, or should it just work? On the UPS itself, I’ve had it 2 days. I’m not filled with joy. It seems OK, but: 1. It doesn’t seem to go to 100% charged. It reports 100%, but when you cut the power it drops very fast to 66%, then sits around 66% - 50% for a long time (before I reconnected the power). 2. It doesn’t report load %, other than via the LCD on the front (and that only has 3 bars, so no real information). It’s hard to work out what the real load my equipment is putting on it 3. It makes a funny clicking noise sometimes, like a relay flicking in and out. I’m not sure whether that’s it clicking in because our voltage is sagging, or something wrong with it already Ultimately it looks like it’ll do what I need, and it wasn’t overly expensive. But I’d really like it to cut power. Thanks, Paul From: Pavel Boček <boc...@po...> Date: Tuesday, 23 July 2024 at 9:12 PM To: Apcupsd Discussion List <apc...@li...> Subject: Re: [Apcupsd-users] SMV1000CAI: killpower not working Hi, this model appears to be yet another version of ripped-off Smart, something like those Smart SC back in the day; do you actually know, like, you asked at APC *before* getting it, if it does support the full modbus/Smart protocol set of commands and that you are not trying to find something which may not be there AT ALL? (note: good that I'm in this list and there are ppl like you, otherwise I'd have no idea what corners is APC cutting all the time with all these "new" series :D) as with other models, I'd in any case suggest, if your master device does not have native RS232 interface, to get USB-to-serial adapter (with some genuine chipset, not counterfeit) and use serial connection of the UPS, that tends to work much better than USB itself -- S uctivým pozdravem/best regards, Pavel Boček Jabber: Be...@ja... +420 739 190 151 http://www.hwworld.cz (kurzy pájení, kondenzátory, aku/baterie aj./capacitors etc.) https://www.hardwareinsights.com (power supply reviews and more) stickers-cz.com (nekonformní samolepky, placky) ---------- Původní e-mail ---------- Od: Paul Lambert <pa...@pl...> Komu: apc...@li... <apc...@li...> Datum: 23. 7. 2024 10:37:50 Předmět: [Apcupsd-users] SMV1000CAI: killpower not working I have a new Easy UPS SMV1000CAI. I have it working, and it adequately powers my Debian server, apcupsd monitors it, and it shuts down my server when it hits the configured thresholds. I’m away from home a bit, and I’m keen that my setup keep working after a power outage – that is, I want the servers, routers, and raspberry pis that are powered from the UPS to restart when the power comes back. To do that, it looks like I need a hard power off – i.e. I need the killpower to work, and then for the UPS to resume when power comes back. With a test run with the UPS, I’m finding it shuts my server down, but doesn’t kill the power. It reports in the log that it is trying to kill the power, but I don’t see the actual power turning off on the UPS. In turn this means that my equipment doesn’t power down, and therefore doesn’t power up when the UPS is reconnected to mains power. To further test I have disconnected my server power from the UPS, connected the USB cable, then run apctest to test things, as you can see from the info below. However, there is no evidence of the UPS powering down, even after an extended period (10-15 minutes). Has anyone had a similar problem? Is there something obvious I’m missing? Does the Easy UPS range actually support the killpower command? I also notice basically all the other functions of apctest aren’t supported either – is this model perhaps unsupported? paul@server:~$ sudo apctest 2024-07-23 18:24:38 apctest 3.14.14 (31 May 2016) debian Checking configuration ... sharenet.type = Network & ShareUPS Disabled cable.type = USB Cable mode.type = USB UPS Driver Setting up the port ... Doing prep_device() ... You are using a USB cable type, so I'm entering USB test mode Hello, this is the apcupsd Cable Test program. This part of apctest is for testing USB UPSes. Getting UPS capabilities...SUCCESS Please select the function you want to perform. 1) Test kill UPS power 2) Perform self-test 3) Read last self-test result 4) View/Change battery date 5) View manufacturing date 6) View/Change alarm behavior 7) View/Change sensitivity 8) View/Change low transfer voltage 9) View/Change high transfer voltage 10) Perform battery calibration 11) Test alarm 12) View/Change self-test interval Q) Quit Select function number: 1 This test will attempt to power down the UPS. The USB cable should be plugged in to the UPS, but the AC power plug to the UPS should be DISCONNECTED. PLEASE DO NOT RUN THIS TEST WITH A COMPUTER CONNECTED TO YOUR UPS!!! Please enter any character when ready to continue: 2024-07-23 18:24:47 calling kill_power function. 9.085 apcupsd: usb.c:1007 UPS appears to support SmartUPS style hibernate. 2024-07-23 18:25:08 returned from kill_power function. 1) Test kill UPS power 2) Perform self-test 3) Read last self-test result Thanks, Paul +64 21 385 488 _______________________________________________ Apcupsd-users mailing list Apc...@li... https://lists.sourceforge.net/lists/listinfo/apcupsd-users |
From: Pavel B. <boc...@po...> - 2024-07-23 09:10:05
|
Hi, this model appears to be yet another version of ripped-off Smart, something like those Smart SC back in the day; do you actually know, like, you asked at APC *before* getting it, if it does support the full modbus/Smart protocol set of commands and that you are not trying to find something which may not be there AT ALL? (note: good that I'm in this list and there are ppl like you, otherwise I'd have no idea what corners is APC cutting all the time with all these "new" series :D) as with other models, I'd in any case suggest, if your master device does not have native RS232 interface, to get USB-to-serial adapter (with some genuine chipset, not counterfeit) and use serial connection of the UPS, that tends to work much better than USB itself -- S uctivým pozdravem/best regards, Pavel Boček Jabber: Be...@ja... +420 739 190 151 http://www.hwworld.cz (kurzy pájení, kondenzátory, aku/baterie aj./ capacitors etc.) https://www.hardwareinsights.com (power supply reviews and more) stickers-cz.com (nekonformní samolepky, placky) ---------- Původní e-mail ---------- Od: Paul Lambert <pa...@pl...> Komu: apc...@li... <apc...@li...urceforge. net> Datum: 23. 7. 2024 10:37:50 Předmět: [Apcupsd-users] SMV1000CAI: killpower not working " I have a new Easy UPS SMV1000CAI. I have it working, and it adequately powers my Debian server, apcupsd monitors it, and it shuts down my server when it hits the configured thresholds. I’m away from home a bit, and I’m keen that my setup keep working after a power outage – that is, I want the servers, routers, and raspberry pis that are powered from the UPS to restart when the power comes back. To do that, it looks like I need a hard power off – i.e. I need the killpower to work, and then for the UPS to resume when power comes back. With a test run with the UPS, I’m finding it shuts my server down, but doesn ’t kill the power. It reports in the log that it is trying to kill the power, but I don’t see the actual power turning off on the UPS. In turn this means that my equipment doesn’t power down, and therefore doesn’t power up when the UPS is reconnected to mains power. To further test I have disconnected my server power from the UPS, connected the USB cable, then run apctest to test things, as you can see from the info below. However, there is no evidence of the UPS powering down, even after an extended period (10-15 minutes). Has anyone had a similar problem? Is there something obvious I’m missing? Does the Easy UPS range actually support the killpower command? I also notice basically all the other functions of apctest aren’t supported either – is this model perhaps unsupported? paul@server:~$ sudo apctest 2024-07-23 18:24:38 apctest 3.14.14 (31 May 2016) debian Checking configuration ... sharenet.type = Network & ShareUPS Disabled cable.type = USB Cable mode.type = USB UPS Driver Setting up the port ... Doing prep_device() ... You are using a USB cable type, so I'm entering USB test mode Hello, this is the apcupsd Cable Test program. This part of apctest is for testing USB UPSes. Getting UPS capabilities...SUCCESS Please select the function you want to perform. 1) Test kill UPS power 2) Perform self-test 3) Read last self-test result 4) View/Change battery date 5) View manufacturing date 6) View/Change alarm behavior 7) View/Change sensitivity 8) View/Change low transfer voltage 9) View/Change high transfer voltage 10) Perform battery calibration 11) Test alarm 12) View/Change self-test interval Q) Quit Select function number: 1 This test will attempt to power down the UPS. The USB cable should be plugged in to the UPS, but the AC power plug to the UPS should be DISCONNECTED. PLEASE DO NOT RUN THIS TEST WITH A COMPUTER CONNECTED TO YOUR UPS!!! Please enter any character when ready to continue: 2024-07-23 18:24:47 calling kill_power function. 9.085 apcupsd: usb.c:1007 UPS appears to support SmartUPS style hibernate. 2024-07-23 18:25:08 returned from kill_power function. 1) Test kill UPS power 2) Perform self-test 3) Read last self-test result Thanks, Paul +64 21 385 488 _______________________________________________ Apcupsd-users mailing list Apc...@li... https://lists.sourceforge.net/lists/listinfo/apcupsd-users " |
From: Paul L. <pa...@pl...> - 2024-07-23 08:32:07
|
I have a new Easy UPS SMV1000CAI. I have it working, and it adequately powers my Debian server, apcupsd monitors it, and it shuts down my server when it hits the configured thresholds. I’m away from home a bit, and I’m keen that my setup keep working after a power outage – that is, I want the servers, routers, and raspberry pis that are powered from the UPS to restart when the power comes back. To do that, it looks like I need a hard power off – i.e. I need the killpower to work, and then for the UPS to resume when power comes back. With a test run with the UPS, I’m finding it shuts my server down, but doesn’t kill the power. It reports in the log that it is trying to kill the power, but I don’t see the actual power turning off on the UPS. In turn this means that my equipment doesn’t power down, and therefore doesn’t power up when the UPS is reconnected to mains power. To further test I have disconnected my server power from the UPS, connected the USB cable, then run apctest to test things, as you can see from the info below. However, there is no evidence of the UPS powering down, even after an extended period (10-15 minutes). Has anyone had a similar problem? Is there something obvious I’m missing? Does the Easy UPS range actually support the killpower command? I also notice basically all the other functions of apctest aren’t supported either – is this model perhaps unsupported? paul@server:~$ sudo apctest 2024-07-23 18:24:38 apctest 3.14.14 (31 May 2016) debian Checking configuration ... sharenet.type = Network & ShareUPS Disabled cable.type = USB Cable mode.type = USB UPS Driver Setting up the port ... Doing prep_device() ... You are using a USB cable type, so I'm entering USB test mode Hello, this is the apcupsd Cable Test program. This part of apctest is for testing USB UPSes. Getting UPS capabilities...SUCCESS Please select the function you want to perform. 1) Test kill UPS power 2) Perform self-test 3) Read last self-test result 4) View/Change battery date 5) View manufacturing date 6) View/Change alarm behavior 7) View/Change sensitivity 8) View/Change low transfer voltage 9) View/Change high transfer voltage 10) Perform battery calibration 11) Test alarm 12) View/Change self-test interval Q) Quit Select function number: 1 This test will attempt to power down the UPS. The USB cable should be plugged in to the UPS, but the AC power plug to the UPS should be DISCONNECTED. PLEASE DO NOT RUN THIS TEST WITH A COMPUTER CONNECTED TO YOUR UPS!!! Please enter any character when ready to continue: 2024-07-23 18:24:47 calling kill_power function. 9.085 apcupsd: usb.c:1007 UPS appears to support SmartUPS style hibernate. 2024-07-23 18:25:08 returned from kill_power function. 1) Test kill UPS power 2) Perform self-test 3) Read last self-test result Thanks, Paul +64 21 385 488 |
From: Jorge F. <jor...@gm...> - 2024-07-17 14:34:10
|
On 7/13/24 11:29 AM, Pavel Boček wrote: > Wanted to check da documentation, but site is down, dropping to > sourcecrap, looks like this started somewhen back in march-april > according to archive. What happened? Hi everyone, That's a great question! Fortunately, we can refer to the Internet Archive, where the most recent good snapshot is from March 15th: https://web.archive.org/web/20240000000000*/www.apcupsd.org I'm also CCing Adam (although I'm not sure if his email is still active or if he's available). Best regards, Jorge |
From: Pavel B. <boc...@po...> - 2024-07-17 10:05:28
|
did told ya in the first message its dropping to sourcecrap now, didn't I? -- S uctivým pozdravem/best regards, Pavel Boček Jabber: Be...@ja... +420 739 190 151 http://www.hwworld.cz (kurzy pájení, kondenzátory, aku/baterie aj./ capacitors etc.) https://www.hardwareinsights.com (power supply reviews and more) stickers-cz.com (nekonformní samolepky, placky) ---------- Původní e-mail ---------- Od: Ted Mittelstaedt <te...@mi...> Komu: apc...@li... Datum: 17. 7. 2024 6:25:56 Předmět: Re: [Apcupsd-users] apcupsd.org down " Fascinating! It appears now all apcupsd.org URLs are redirecting to Apcupsd UPS control software | Support for Apcupsd UPS control software at SourceForge.net(https://sourceforge.net/projects/apcupsd/support) I wonder if Adam decided to take the website down? The manual is still accessible from Apcupsd UPS control software / SVN / [r2381] /branches/Branch-3_14/doc/ manual (sourceforge.net) (https://sourceforge.net/p/apcupsd/svn/HEAD/tree/branches/Branch-3_14/doc/manual/) I suppose I will need to login to SF and see if I can modify the Support section of the project and setup a domain name for it. I think the old site is available on the Wayback machine and I can probably scrape the relevant data off that. Ted (https://sourceforge.net/projects/apcupsd/support) On 7/16/2024 5:49 AM, Pavel Boček wrote: " Hardly. Archive thors error since the given time, when I try to access documentation directly, get this: An error has been encountered in accessing this page. 1. Server: www.apcupsd.org(http://www.apcupsd.org) 2. URL path: /manual/manual.html 3. Error notes: NONE 4. Error type: 404 5. Request method: GET 6. Request query string: NONE 7. Time: 2024-07-16 12:47:42 UTC (1721134062) Reporting this problem: The problem you have encountered is with a project web site hosted by SourceForge.net. This issue should be reported to the SourceForge.net-hosted project (not to SourceForge.net). If this is a severe or recurring/persistent problem, please do one of the following, and provide the error text (numbered 1 through 7, above): 1. Contact the project via their designated support resources (https://sourceforge.net/support/prweb-lookup.php?host=www.apcupsd.org&support=1) . 2. Contact the project administrators of this project via email (see the upper right-hand corner of the Project Summary page (https://sourceforge.net/support/prweb-lookup.php?host=www.apcupsd.org) for their usernames) at use...@us... If you are a maintainer of this web content, please refer to the Site Documentation regarding web services (https://sourceforge.net/p/forge/documentation/Project%20Web%20Services/) for further assistance. NOTE: As of 2008-10-23 directory index display has been disabled by default. This option may be re-enabled by the project by placing a file with the name ".htaccess" with this line: Options +Indexes -- S uctivým pozdravem/best regards, Pavel Boček Jabber: Be...@ja...(mailto:Be...@ja...) +420 739 190 151 http://www.hwworld.cz(http://www.hwworld.cz) (kurzy pájení, kondenzátory, aku/baterie aj./capacitors etc.) https://www.hardwareinsights.com(https://www.hardwareinsights.com) (power supply reviews and more) stickers-cz.com (nekonformní samolepky, placky) ---------- Původní e-mail ---------- Od: Ted Mittelstaedt <te...@mi...>(mailto:te...@mi...) Komu: apc...@li... (mailto:apc...@li...) Datum: 16. 7. 2024 7:09:44 Předmět: Re: [Apcupsd-users] apcupsd.org down " It works fine from my POV. Adam K to my knowledge has the domain name and while Adam gave me committers rights in SF on the project a few years ago, without control of the name I really can't do anything. A year ago the NUT project pulled a copy of the core MODBUS code out of apcupsd and incorporated it as a driver for NUT. I still vastly prefer apcupsd however. The windows port of it is 32-bit however and when run on Windows Server Core it's necessary to install the WoW64 32-64 bit subsystem with the command DISM.EXE /online /enable-feature /featurename:ServerCore-WOW64 I am waiting to see what Microsoft does with the Desktop version of Windows Server 2025. I don't THINK they intend on removing the WoW64 subsystem but I've learned NOT to predict what they will do prior to a release. Unfortunately, porting it to 64 bit windows is non-trivial. Ted On 7/13/2024 8:29 AM, Pavel Boček wrote: " Wanted to check da documentation, but site is down, dropping to sourcecrap, looks like this started somewhen back in march-april according to archive. What happened? -- S uctivým pozdravem/best regards, Pavel Boček Jabber: Be...@ja...(mailto:Be...@ja...) +420 739 190 151 http://www.hwworld.cz(http://www.hwworld.cz) (kurzy pájení, kondenzátory, aku/baterie aj./capacitors etc.) https://www.hardwareinsights.com(https://www.hardwareinsights.com) (power supply reviews and more) stickers-cz.com (nekonformní samolepky, placky) _______________________________________________ Apcupsd-users mailing list <a href='mailto:Apc...@li...' class='-wm-moz-txt-link-abbreviated -wm-moz-txt-link-freetext'>Apc...@li...</a> <a href='https://lists.sourceforge.net/lists/listinfo/apcupsd-users' class='-wm-moz-txt-link-freetext -wm-moz-txt-link-freetext'>https://lists.sourceforge.net/lists/listinfo/apcupsd-users</a> " _______________________________________________ Apcupsd-users mailing list Apc...@li... (mailto:Apc...@li...) https://lists.sourceforge.net/lists/listinfo/apcupsd-users (https://lists.sourceforge.net/lists/listinfo/apcupsd-users) " _______________________________________________ Apcupsd-users mailing list <a href='mailto:Apc...@li...' class='-wm-moz-txt-link-abbreviated'>Apc...@li...</a> <a href='https://lists.sourceforge.net/lists/listinfo/apcupsd-users' class='-wm-moz-txt-link-freetext'>https://lists.sourceforge.net/lists/listinfo/apcupsd-users</a> " _______________________________________________ Apcupsd-users mailing list Apc...@li... https://lists.sourceforge.net/lists/listinfo/apcupsd-users " |
From: Ted M. <te...@mi...> - 2024-07-17 04:24:34
|
Fascinating! It appears now all apcupsd.org URLs are redirecting to Apcupsd UPS control software | Support for Apcupsd UPS control software at SourceForge.net <https://sourceforge.net/projects/apcupsd/support> I wonder if Adam decided to take the website down? The manual is still accessible from Apcupsd UPS control software / SVN / [r2381] /branches/Branch-3_14/doc/manual (sourceforge.net) <https://sourceforge.net/p/apcupsd/svn/HEAD/tree/branches/Branch-3_14/doc/manual/> I suppose I will need to login to SF and see if I can modify the Support section of the project and setup a domain name for it. I think the old site is available on the Wayback machine and I can probably scrape the relevant data off that. Ted <https://sourceforge.net/projects/apcupsd/support> On 7/16/2024 5:49 AM, Pavel Boček wrote: > Hardly. Archive thors error since the given time, when I try to access > documentation directly, get this: > > An error has been encountered in accessing this page. > > 1. *Server:* www.apcupsd.org > 2. *URL path:* /manual/manual.html > 3. *Error notes:* NONE > 4. *Error type:* 404 > 5. *Request method:* GET > 6. *Request query string:* NONE > 7. *Time:* 2024-07-16 12:47:42 UTC (1721134062) > > *Reporting this problem:* The problem you have encountered is with a > project web site hosted by SourceForge.net. This issue should be > reported to the SourceForge.net-hosted project (not to SourceForge.net). > > /If this is a severe or recurring/persistent problem,/ please do one > of the following, and provide the error text (numbered 1 through 7, > above): > > 1. Contact the project via their designated support resources > <https://sourceforge.net/support/prweb-lookup.php?host=www.apcupsd.org&support=1>. > > 2. Contact the project administrators of this project via email (see > the upper right-hand corner of the Project Summary page > <https://sourceforge.net/support/prweb-lookup.php?host=www.apcupsd.org> > for their usernames) at /user-name/@users.sourceforge.net > > If you are a maintainer of this web content, please refer to the Site > Documentation regarding web services > <https://sourceforge.net/p/forge/documentation/Project%20Web%20Services/> > for further assistance. > > NOTE: As of 2008-10-23 directory index display has been disabled by > default. This option may be re-enabled by the project by placing a > file with the name ".htaccess" with this line: > > Options +Indexes > > > -- > S uctivým pozdravem/best regards, > > Pavel Boček > Jabber: Be...@ja... > +420 739 190 151 > http://www.hwworld.cz (kurzy pájení, kondenzátory, aku/baterie > aj./capacitors etc.) > https://www.hardwareinsights.com (power supply reviews and more) > stickers-cz.com (nekonformní samolepky, placky) > > ---------- Původní e-mail ---------- > Od: Ted Mittelstaedt <te...@mi...> > Komu: apc...@li... > Datum: 16. 7. 2024 7:09:44 > Předmět: Re: [Apcupsd-users] apcupsd.org down > > > It works fine from my POV. > > Adam K to my knowledge has the domain name and while Adam gave me > committers rights in SF on the project a few years ago, without > control of the name I really can't do anything. > > A year ago the NUT project pulled a copy of the core MODBUS code > out of apcupsd and incorporated it as a driver for NUT. > > I still vastly prefer apcupsd however. The windows port of it is > 32-bit however and when run on Windows Server Core it's necessary > to install the WoW64 32-64 bit subsystem with the command > > DISM.EXE /online /enable-feature /featurename:ServerCore-WOW64 > > I am waiting to see what Microsoft does with the Desktop version > of Windows Server 2025. I don't THINK they intend on removing the > WoW64 subsystem but I've learned NOT to predict what they will do > prior to a release. > > Unfortunately, porting it to 64 bit windows is non-trivial. > > Ted > > On 7/13/2024 8:29 AM, Pavel Boček wrote: > > Wanted to check da documentation, but site is down, dropping > to sourcecrap, looks like this started somewhen back in > march-april according to archive. What happened? > > -- > S uctivým pozdravem/best regards, > > Pavel Boček > Jabber: Be...@ja... <mailto:Be...@ja...> > +420 739 190 151 > http://www.hwworld.cz <http://www.hwworld.cz> (kurzy pájení, > kondenzátory, aku/baterie aj./capacitors etc.) > https://www.hardwareinsights.com > <https://www.hardwareinsights.com> (power supply reviews and more) > stickers-cz.com (nekonformní samolepky, placky) > > > _______________________________________________ > Apcupsd-users mailing list > Apc...@li... <mailto:Apc...@li...> > https://lists.sourceforge.net/lists/listinfo/apcupsd-users <https://lists.sourceforge.net/lists/listinfo/apcupsd-users> > > _______________________________________________ > Apcupsd-users mailing list > Apc...@li... > https://lists.sourceforge.net/lists/listinfo/apcupsd-users > > > > _______________________________________________ > Apcupsd-users mailing list > Apc...@li... > https://lists.sourceforge.net/lists/listinfo/apcupsd-users |
From: Pavel B. <boc...@po...> - 2024-07-16 12:49:30
|
Hardly. Archive thors error since the given time, when I try to access documentation directly, get this: An error has been encountered in accessing this page. 1. Server: www.apcupsd.org 2. URL path: /manual/manual.html 3. Error notes: NONE 4. Error type: 404 5. Request method: GET 6. Request query string: NONE 7. Time: 2024-07-16 12:47:42 UTC (1721134062) Reporting this problem: The problem you have encountered is with a project web site hosted by SourceForge.net. This issue should be reported to the SourceForge.net-hosted project (not to SourceForge.net). If this is a severe or recurring/persistent problem, please do one of the following, and provide the error text (numbered 1 through 7, above): 1. Contact the project via their designated support resources (https://sourceforge.net/support/prweb-lookup.php?host=www.apcupsd.org&support=1) . 2. Contact the project administrators of this project via email (see the upper right-hand corner of the Project Summary page (https://sourceforge.net/support/prweb-lookup.php?host=www.apcupsd.org) for their usernames) at use...@us... If you are a maintainer of this web content, please refer to the Site Documentation regarding web services (https://sourceforge.net/p/forge/documentation/Project%20Web%20Services/) for further assistance. NOTE: As of 2008-10-23 directory index display has been disabled by default. This option may be re-enabled by the project by placing a file with the name ".htaccess" with this line: Options +Indexes -- S uctivým pozdravem/best regards, Pavel Boček Jabber: Be...@ja... +420 739 190 151 http://www.hwworld.cz (kurzy pájení, kondenzátory, aku/baterie aj./ capacitors etc.) https://www.hardwareinsights.com (power supply reviews and more) stickers-cz.com (nekonformní samolepky, placky) ---------- Původní e-mail ---------- Od: Ted Mittelstaedt <te...@mi...> Komu: apc...@li... Datum: 16. 7. 2024 7:09:44 Předmět: Re: [Apcupsd-users] apcupsd.org down " It works fine from my POV. Adam K to my knowledge has the domain name and while Adam gave me committers rights in SF on the project a few years ago, without control of the name I really can't do anything. A year ago the NUT project pulled a copy of the core MODBUS code out of apcupsd and incorporated it as a driver for NUT. I still vastly prefer apcupsd however. The windows port of it is 32-bit however and when run on Windows Server Core it's necessary to install the WoW64 32-64 bit subsystem with the command DISM.EXE /online /enable-feature /featurename:ServerCore-WOW64 I am waiting to see what Microsoft does with the Desktop version of Windows Server 2025. I don't THINK they intend on removing the WoW64 subsystem but I've learned NOT to predict what they will do prior to a release. Unfortunately, porting it to 64 bit windows is non-trivial. Ted On 7/13/2024 8:29 AM, Pavel Boček wrote: " Wanted to check da documentation, but site is down, dropping to sourcecrap, looks like this started somewhen back in march-april according to archive. What happened? -- S uctivým pozdravem/best regards, Pavel Boček Jabber: Be...@ja...(mailto:Be...@ja...) +420 739 190 151 http://www.hwworld.cz(http://www.hwworld.cz) (kurzy pájení, kondenzátory, aku/baterie aj./capacitors etc.) https://www.hardwareinsights.com(https://www.hardwareinsights.com) (power supply reviews and more) stickers-cz.com (nekonformní samolepky, placky) _______________________________________________ Apcupsd-users mailing list <a href='mailto:Apc...@li...' class='-wm-moz-txt-link-abbreviated'>Apc...@li...</a> <a href='https://lists.sourceforge.net/lists/listinfo/apcupsd-users' class='-wm-moz-txt-link-freetext'>https://lists.sourceforge.net/lists/listinfo/apcupsd-users</a> " _______________________________________________ Apcupsd-users mailing list Apc...@li... https://lists.sourceforge.net/lists/listinfo/apcupsd-users " |
From: Ted M. <te...@mi...> - 2024-07-16 05:03:35
|
It works fine from my POV. Adam K to my knowledge has the domain name and while Adam gave me committers rights in SF on the project a few years ago, without control of the name I really can't do anything. A year ago the NUT project pulled a copy of the core MODBUS code out of apcupsd and incorporated it as a driver for NUT. I still vastly prefer apcupsd however. The windows port of it is 32-bit however and when run on Windows Server Core it's necessary to install the WoW64 32-64 bit subsystem with the command DISM.EXE /online /enable-feature /featurename:ServerCore-WOW64 I am waiting to see what Microsoft does with the Desktop version of Windows Server 2025. I don't THINK they intend on removing the WoW64 subsystem but I've learned NOT to predict what they will do prior to a release. Unfortunately, porting it to 64 bit windows is non-trivial. Ted On 7/13/2024 8:29 AM, Pavel Boček wrote: > Wanted to check da documentation, but site is down, dropping to > sourcecrap, looks like this started somewhen back in march-april > according to archive. What happened? > > -- > S uctivým pozdravem/best regards, > > Pavel Boček > Jabber: Be...@ja... > +420 739 190 151 > http://www.hwworld.cz (kurzy pájení, kondenzátory, aku/baterie > aj./capacitors etc.) > https://www.hardwareinsights.com (power supply reviews and more) > stickers-cz.com (nekonformní samolepky, placky) > > > _______________________________________________ > Apcupsd-users mailing list > Apc...@li... > https://lists.sourceforge.net/lists/listinfo/apcupsd-users |
From: Pavel B. <boc...@po...> - 2024-07-13 15:41:46
|
Wanted to check da documentation, but site is down, dropping to sourcecrap, looks like this started somewhen back in march-april according to archive. What happened? -- S uctivým pozdravem/best regards, Pavel Boček Jabber: Be...@ja... +420 739 190 151 http://www.hwworld.cz (kurzy pájení, kondenzátory, aku/baterie aj./ capacitors etc.) https://www.hardwareinsights.com (power supply reviews and more) stickers-cz.com (nekonformní samolepky, placky) |
From: <ad...@wa...> - 2024-06-22 05:04:36
|
I found a manual online. The answer is doshutdown is triggered *after* those events. ========= failing apcupsd generates this event when the UPS is running on batteries and the UPS sets the low battery signal indicating that battery power is nearly exhausted. After this event, apcupsd will immediately generate a doshutdown event. Default action -- sends "UPS battery power exhausted. Doing shutdown." to wall and then exits. ------ Original Message ------ >From "ad...@wa..." <ad...@wa...> To "apc...@li..." <apc...@li...> Date 6/21/2024 7:23:09 PM Subject [Apcupsd-users] Sequence of Events >Hello, everyone. I just bought a new APC UPS, and I'm now setting up event scripts to notify me of whatever happens. I have a question about the sequence of events. > >For background, I had apcupsd running on a few instances for several years, but was renting a VPS for the past year and a half. I understand how to script events and I had everything working fine - including texting the utility to notify of power outage :-) . But now that I'm looking at things with fresh eyes, I realize I never scripted these events below before, and I would like to now. > >When I look at apccontrol.bat, there are a few of events that are confusing to me. It says: > >:failing > %POPUP% "UPS battery power exhausted. Doing shutdown." > GOTO :done > >:timeout > %POPUP% "UPS battery runtime limit exceeded. Doing shutdown." > GOTO :done > >:loadlimit > %POPUP% "UPS battery discharge limit reached. Doing shutdown." > GOTO :done > >:runlimit > %POPUP% "UPS battery runtime percent reached. Doing shutdown." > GOTO :done > >Does this mean that whenever one of these events is triggered, it will sequentially trigger "doshutdown" after? > >My "real" question is, do I need to script the PC shutdown within the above events, or only at "doshutdown" event? > >Thanks! > > > > > >_______________________________________________ >Apcupsd-users mailing list >Apc...@li... >https://lists.sourceforge.net/lists/listinfo/apcupsd-users |
From: <ad...@wa...> - 2024-06-21 17:46:55
|
Hello, everyone. I just bought a new APC UPS, and I'm now setting up event scripts to notify me of whatever happens. I have a question about the sequence of events. For background, I had apcupsd running on a few instances for several years, but was renting a VPS for the past year and a half. I understand how to script events and I had everything working fine - including texting the utility to notify of power outage :-) . But now that I'm looking at things with fresh eyes, I realize I never scripted these events below before, and I would like to now. When I look at apccontrol.bat, there are a few of events that are confusing to me. It says: :failing %POPUP% "UPS battery power exhausted. Doing shutdown." GOTO :done :timeout %POPUP% "UPS battery runtime limit exceeded. Doing shutdown." GOTO :done :loadlimit %POPUP% "UPS battery discharge limit reached. Doing shutdown." GOTO :done :runlimit %POPUP% "UPS battery runtime percent reached. Doing shutdown." GOTO :done Does this mean that whenever one of these events is triggered, it will sequentially trigger "doshutdown" after? My "real" question is, do I need to script the PC shutdown within the above events, or only at "doshutdown" event? Thanks! |
From: Ted M. <te...@mi...> - 2024-05-30 14:04:44
|
OK, Basic Windows PC troubleshooting: Windows has basically 4 components: 1) The OS and kernel which is the same on all PC's and has system privileges 2) Configuration settings in the OS and kernel that may be unique to your PC 3) The device driver package that gets system privileges (video drivers, printer drivers, etc) 4) Regular unprivileged add-in applications (word, excel, acrobat, etc) 5) Add-in applications that are given system privileges (antivirus scanners, etc.) 6) And then, there's the misbehaving application itself. Logically we know this: It's not #1 because apctray runs on a huge number of windows PC's and does not display this problem It's not #6 because of the same thing as above, it runs on lots of PCs and does not do this It's not #4 because those apps don't have permission to kill the tray icon So it's going to be #2, #3 or #5. So the way we figure this out is simple: 1) Remove the hard disk or storage media the OS resides on 2) Install a scratch disk, or m2 chip or whatever 3) Boot it off a windows 10 or 11 ISO downloaded from Microsoft and install Windows. Make NO configuration changes other than the minimal to get a running OS on it 4) do not load any add in programs. 5) Load apcupsd and observe behavior. If it keeps doing it, write this up as a bug with hardware versions, (including BIOS) and software versions of everything. Bugs must be repeatable to be a real bug and this matches the criteria. As a last ditch Hail Mary you can try firmware updates on everything (including the PC BIOS) 6) If it works normally then one at a time, start making OS configuration changes (#2) until they match your prior system. Observe tray behavior each change made. 7) If that works normally then load in device drivers one at a time observing tray behavior each time until they match your prior system 8) If that is OK then load in unprivileged application programs one at a time observing apctray behavior each time. If you finish and your new system matches your old system, and apctray behavior is normal, then you have a Potentially Unwanted Program you don't know about on your old system. AKA "virus" Normal procedure at that time is to add a dock to the PC, dock your hard disk or m.2 chip, and copy your data off your old media, then wipe it. Ted On 5/30/2024 4:43 AM, Jan Píša wrote: > - no event in event viewer > - it seems that apctray is killing itself, but don't know why (apcupsd > service is still running in background, only apctray will exit) > - Caffeine didn't help > - and as I already said, when apctray status window is opened (and can > be closed after couple of minutes also), this behavior does not > happen. Icon stays in tray and everything is working as expected. > > :-/ > > jimmy > > Dne 29.05.2024 v 6:21 Ted Mittelstaedt napsal(a): >> Look in your windows event viewer when the program terminates as >> windows should be logging an error there >> >> Your computer could also be going into some kind of low power mode >> and killing the process. This app will prevent that: >> >> https://www.zhornsoftware.co.uk/caffeine/ >> >> Ted >> >> On 5/26/2024 3:12 AM, JAN PÍŠA wrote: >>> Hello, >>> I have some strange problem with APCTray in Windows 11 Apcupsd >>> is working fine, service is running. But... >>> - when I run APCTray, it stays in tray for literally a few seconds >>> only and then terminates (missing APCtray in process list). I tried >>> to measure if the time is still same, but it is occuring randomly >>> something between 30 and 60 seconds after startup. >>> - I found that when I run APCTray and then open it so the status >>> window is visible, it will not terminate. >>> - also when I run APCTray, immediately open the status window, wait >>> couple minutes (I didn't measure how many, but I left status window >>> opened a while, doing another work) and then I close the status >>> window, APCTray will not terminate and stays in tray working. >>> No errors, no indication why, I am clueless :( >>> Thanks for your ideas. >>> jimmy >>> >>> >>> _______________________________________________ >>> Apcupsd-users mailing list >>> Apc...@li... >>> https://lists.sourceforge.net/lists/listinfo/apcupsd-users >> >> >> _______________________________________________ >> Apcupsd-users mailing list >> Apc...@li... >> https://lists.sourceforge.net/lists/listinfo/apcupsd-users > > > > > _______________________________________________ > Apcupsd-users mailing list > Apc...@li... > https://lists.sourceforge.net/lists/listinfo/apcupsd-users > |
From: Jan P. <ji...@wo...> - 2024-05-30 12:02:11
|
- no event in event viewer - it seems that apctray is killing itself, but don't know why (apcupsd service is still running in background, only apctray will exit) - Caffeine didn't help - and as I already said, when apctray status window is opened (and can be closed after couple of minutes also), this behavior does not happen. Icon stays in tray and everything is working as expected. :-/ jimmy Dne 29.05.2024 v 6:21 Ted Mittelstaedt napsal(a): > Look in your windows event viewer when the program terminates as > windows should be logging an error there > > Your computer could also be going into some kind of low power mode and > killing the process. This app will prevent that: > > https://www.zhornsoftware.co.uk/caffeine/ > > Ted > > On 5/26/2024 3:12 AM, JAN PÍŠA wrote: >> Hello, >> I have some strange problem with APCTray in Windows 11 Apcupsd is >> working fine, service is running. But... >> - when I run APCTray, it stays in tray for literally a few seconds >> only and then terminates (missing APCtray in process list). I tried >> to measure if the time is still same, but it is occuring randomly >> something between 30 and 60 seconds after startup. >> - I found that when I run APCTray and then open it so the status >> window is visible, it will not terminate. >> - also when I run APCTray, immediately open the status window, wait >> couple minutes (I didn't measure how many, but I left status window >> opened a while, doing another work) and then I close the status >> window, APCTray will not terminate and stays in tray working. >> No errors, no indication why, I am clueless :( >> Thanks for your ideas. >> jimmy >> >> >> _______________________________________________ >> Apcupsd-users mailing list >> Apc...@li... >> https://lists.sourceforge.net/lists/listinfo/apcupsd-users > > > _______________________________________________ > Apcupsd-users mailing list > Apc...@li... > https://lists.sourceforge.net/lists/listinfo/apcupsd-users |
From: Ted M. <te...@mi...> - 2024-05-29 04:54:13
|
Look in your windows event viewer when the program terminates as windows should be logging an error there Your computer could also be going into some kind of low power mode and killing the process. This app will prevent that: https://www.zhornsoftware.co.uk/caffeine/ Ted On 5/26/2024 3:12 AM, JAN PÍŠA wrote: > Hello, > I have some strange problem with APCTray in Windows 11 Apcupsd is > working fine, service is running. But... > - when I run APCTray, it stays in tray for literally a few seconds > only and then terminates (missing APCtray in process list). I tried to > measure if the time is still same, but it is occuring randomly > something between 30 and 60 seconds after startup. > - I found that when I run APCTray and then open it so the status > window is visible, it will not terminate. > - also when I run APCTray, immediately open the status window, wait > couple minutes (I didn't measure how many, but I left status window > opened a while, doing another work) and then I close the status > window, APCTray will not terminate and stays in tray working. > No errors, no indication why, I am clueless :( > Thanks for your ideas. > jimmy > > > _______________________________________________ > Apcupsd-users mailing list > Apc...@li... > https://lists.sourceforge.net/lists/listinfo/apcupsd-users |
From: <la...@wo...> - 2024-05-28 18:03:19
|
Hello, I have some strange problem with APCTray in Windows 11. Apcupsd is working fine, service is running. But... - when I run APCTray, it stays in tray for literally a few seconds only and then terminates (missing APCtray in process list). I tried to measure if the time is still same, but it is occuring randomly something between 30 and 60 seconds after startup. - I found that when I run APCTray and then open it so the status window is visible, it will not terminate. - also when I run APCTray, immediately open the status window, wait couple minutes (I didn't measure how many, but I left status window opened a while, doing another work) and then I close the status window, APCTray will not terminate and stays in tray working. No errors, no indication why, I am clueless :( Thanks for your ideas. jimmy |
From: <la...@wo...> - 2024-05-28 17:08:15
|
Hello, I have some strange problem with APCTray in Windows 11. Apcupsd is working fine, service is running. But... - when I run APCTray, it stays in tray for literally a few seconds only and then terminates (missing APCtray in process list). I tried to measure if the time is still same, but it is occuring randomly something between 30 and 60 seconds after startup. - I found that when I run APCTray and then open it so the status window is visible, it will not terminate. - also when I run APCTray, immediately open the status window, wait couple minutes (I didn't measure how many, but I left status window opened a while, doing another work) and then I close the status window, APCTray will not terminate and stays in tray working. No errors, no indication why, I am clueless :( Thanks for your ideas. jimmy |
From: Ted M. <te...@mi...> - 2024-04-04 13:22:28
|
You might try a exe to msi converter like WinINSTALL LE Ted On 4/4/2024 5:09 AM, Paul Schrader wrote: > > Hello, > > Are there any options to control the Windows Install from command line ? > > I would like to be able to do a Silent Install from command line and > Exclude the option to install the USB Driver. > > I can get a Silent install started by using /S but it attempts to > install the USB Driver and fails , as I do not need that > > Looking to see if it can be excluded when running a Silent Install. > > Thanks > > Paul > > > > _______________________________________________ > Apcupsd-users mailing list > Apc...@li... > https://lists.sourceforge.net/lists/listinfo/apcupsd-users |
From: Paul S. <sw...@ka...> - 2024-04-04 12:25:48
|
Hello, Are there any options to control the Windows Install from command line ? I would like to be able to do a Silent Install from command line and Exclude the option to install the USB Driver. I can get a Silent install started by using /S but it attempts to install the USB Driver and fails , as I do not need that Looking to see if it can be excluded when running a Silent Install. Thanks Paul |
From: Sarunas B. <sa...@ma...> - 2024-03-25 16:30:35
|
On 3/25/24 12:10, Phil Stracchino wrote: > I'm a bit out of touch with apcupsd and the state of support, having > been using NUT for a while because I unwisely bought a CyberPower UPS. > Can anyone tell me the state of support for SMT series APC UPSen? > Specifically a SMT3000RM2UC? It works very well for us (Ubuntu 22.04, apcupsd 3.14.14) with the following APC accessory cable + adapter: * APC UPS Communications Cable Smart Signalling DB9 to RJ45 (AP940-0625A) * SABRENT USB 2.0 to Serial (9 Pin) DB 9 RS 232 Converter Cable, Prolific Chipset (CB-DB9P) /etc/apcupsd/apcupsd.con settings: UPSCABLE 940-0625A UPSTYPE modbus DEVICE /dev/ttyUSB0 (USB port number of course may differ.) -- Sarunas Burdulis Dartmouth Mathematics math.dartmouth.edu/~sarunas · https://useplaintext.email · |
From: Phil S. <ph...@ca...> - 2024-03-25 16:10:32
|
I'm a bit out of touch with apcupsd and the state of support, having been using NUT for a while because I unwisely bought a CyberPower UPS. Can anyone tell me the state of support for SMT series APC UPSen? Specifically a SMT3000RM2UC? -- Phil Stracchino Babylon Communications ph...@ca... ph...@co... Landline: +1.603.293.8485 Mobile: +1.603.998.6958 |
From: Trev <tr...@se...> - 2024-02-28 05:15:08
|
Potuz via Apcupsd-users wrote on 28/2/24 4:50 am: > Hello, I am seeing old posts that say that apctest does not support > doing a callibration over USB. However I do see this option when running > apctest in my system: [...] > 10) Perform battery calibration [...] > I have simply 2 questions. > 1) is the calibration over USB supported? There are so many broken USB firmware versions and UPS combinations that it is not possible to definitively say one way or the other. If the option appears as above, which is vaguely encouraging, the only way to know for sure is to try it and observe the result. > 2) Do I need to unplug the power to run the calibration? > I put the system to a load of 15% and when running the test it reports > the battery constantly at 100% for over half an hour (but I didn't > unplug the power from the UPS). In which case you are using the mains and not the UPS battery -- the mains power obviously needs to fail before the battery can be used/tested/calibrated :) |
From: Sebastian A. <s....@op...> - 2024-02-27 22:52:41
|
As per title, I think this has been touched on a few weeks ago on this list. I have a number of cheapo APC units (mainly CS type) which will not allow me to change the schedule of self-tests using apctest. I don't even think they ever run an automatic self test - as units which have been in for years show for last test result as "none". However, all of them allow me to run a manual self-test through the apctest menu. Is there any way of passing the selftest as a command to either apctest or apcupsd, so that I can script it and run it from cron? It all seems tantalizingly close to what I need, as apcupsd can actually run the test through the apctest menu, and then I can see the test has passed - but I can't find anyway of triggering this automatically from cron. I understand APC has limited the features on these units on purpose, but that's usually the advantage of using good open source software - to make up for manufacturers' - erm - whims :-) Thank you for any suggestions. |
From: Potuz <po...@po...> - 2024-02-27 18:07:40
|
Hello, I am seeing old posts that say that apctest does not support doing a callibration over USB. However I do see this option when running apctest in my system: 1) Test kill UPS power 2) Perform self-test 3) Read last self-test result 4) View/Change battery date 5) View manufacturing date 6) View/Change alarm behavior 7) View/Change sensitivity 8) View/Change low transfer voltage 9) View/Change high transfer voltage 10) Perform battery calibration 11) Test alarm 12) View/Change self-test interval Q) Quit I have simply 2 questions. 1) is the calibration over USB supported? 2) Do I need to unplug the power to run the calibration? I put the system to a load of 15% and when running the test it reports the battery constantly at 100% for over half an hour (but I didn't unplug the power from the UPS). apcaccess reports 5 minutes with a new battery at 100% so that on a minimal power failure the UPS tries to turn off the server. Best, P. |
From: Yannick M. <yan...@ok...> - 2024-02-24 23:29:50
|
Hello The new BX1600MI is not close to me. I will try this. Mine I bought in 2023 does not show this behaviour. In apcaccess, the new BX1600MI does not show firmware version anymore. For now, I rebuilt my apcupsd debian package with the attached patch. Regards Le 24/02/2024 à 22:53, David Ranch a écrit : > > Wireshark for Windows offers a USB sniffer module upon installation. > It might be interesting to run that with Powerchute Serial Shutdown > and see if Ted is correct that the USB is throwing trash but the > Windows software just ignores it. > > --David > > On 02/24/2024 12:58 PM, Andy Smith wrote: >> Hi Yannick, >> >> On Sat, Feb 24, 2024 at 08:20:36PM +0100, Yannick Martin via Apcupsd-users wrote: >>> With apcupsd on debug, I found that "battery present" and "battery need >>> replacement" states are flapping: >> So similar to what I am seeing with my BX1600MI. I am mopstly seeing >> battery detach/reattach, as in 10+ times per hour. I also >> occasionally see power fail/restore and "changeme" but only quite >> rarely compared to detach/reattach. >> >>> I don't have any issue when I checked the unit with PowerChute on Windows. >> Same. It seemed to behave perfectly with POwerchute Serial Shutdown >> on Windows. >> >>> For now, I will patch apcupsd and 2 others counters: _bacnt (absent) and >>> _brcnt (replacement). I think the issue is similar to RS1500 glitch on those >>> new BX1600 ... >> Even though I am sending it back and getting a different brand, I >> would still be interested in seeing your patch! >> >> Thanks, >> Andy >> >> >> _______________________________________________ >> Apcupsd-users mailing list >> Apc...@li... >> https://lists.sourceforge.net/lists/listinfo/apcupsd-users > > > > _______________________________________________ > Apcupsd-users mailing list > Apc...@li... > https://lists.sourceforge.net/lists/listinfo/apcupsd-users |
From: David R. <ap...@tr...> - 2024-02-24 22:19:08
|
Wireshark for Windows offers a USB sniffer module upon installation. It might be interesting to run that with Powerchute Serial Shutdown and see if Ted is correct that the USB is throwing trash but the Windows software just ignores it. --David On 02/24/2024 12:58 PM, Andy Smith wrote: > Hi Yannick, > > On Sat, Feb 24, 2024 at 08:20:36PM +0100, Yannick Martin via Apcupsd-users wrote: >> With apcupsd on debug, I found that "battery present" and "battery need >> replacement" states are flapping: > So similar to what I am seeing with my BX1600MI. I am mopstly seeing > battery detach/reattach, as in 10+ times per hour. I also > occasionally see power fail/restore and "changeme" but only quite > rarely compared to detach/reattach. > >> I don't have any issue when I checked the unit with PowerChute on Windows. > Same. It seemed to behave perfectly with POwerchute Serial Shutdown > on Windows. > >> For now, I will patch apcupsd and 2 others counters: _bacnt (absent) and >> _brcnt (replacement). I think the issue is similar to RS1500 glitch on those >> new BX1600 ... > Even though I am sending it back and getting a different brand, I > would still be interested in seeing your patch! > > Thanks, > Andy > > > _______________________________________________ > Apcupsd-users mailing list > Apc...@li... > https://lists.sourceforge.net/lists/listinfo/apcupsd-users |