Re: [Nut-upsuser] Any ideas what protocol GE VH3000 UPS might talk?
On 6/24/24 12:50, gene heskett via Nut-upsuser wrote: On 6/24/24 11:30, Jim Klimov via Nut-upsuser wrote: Curiously, they identify as |067b:2303 Prolific Technology| like a common USB-Serial dongle brand. Experiments with blazer and nutdrv-qx got no reasonable response from the devices. Jim The cure Jim, is eliminate the prolific by replacing it with a FTDI dongle. Prolific has a bug in its wakeup, throwing away the first byte rx'd. I threw mine into the out bin 2 decades ago. Was trying to use it to talk to a cm11a for a heyu interface. Failed miserably. Encourage owners to toss it and get the FTDI-usb<->serial which Just Works. THAT would explain a LOT of past issues with trying to use a Microsoft DeLorme GPS receiver as a stratum-1 time source. Unfortunately since the Prolific chip was built into the device, replacing it with FTDI wasn't an option. (The worse problem, though, was that at the time, the Prolific driver in the Linux kernel had a bug in it which prevented it from ever being unloaded once loaded, which in turn made it impossible to cleanly reboot. I couldn't simply compile the driver inline because it didn't get initialized properly unless loaded as a module.) -- Phil Stracchino Fenian House Publishing ph...@caerllewys.net p...@co.ordinate.org Landline: +1.603.293.8485 Mobile: +1.603.998.6958 ___ Nut-upsuser mailing list Nut-upsuser@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] CyberPower PR3000LCDRTXL2U — battery date reset?
On 4/2/24 07:13, Jim Klimov via Nut-upsuser wrote: Well, for a bit of devil's advocate - if the battery swelled, it might hace leaked or fumed, contaminating the device and contacts. The safe approach (for their liability, and for end-users' fire hazard really) is to not claim the device is safe to use anymore. Not an invalid point, true. I'd discuss other shortcomings of Cyberpower's design, but I don't want to drift further off topic. -- Phil Stracchino Babylon Communications ph...@caerllewys.net p...@co.ordinate.org Landline: +1.603.293.8485 Mobile: +1.603.998.6958 ___ Nut-upsuser mailing list Nut-upsuser@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] CyberPower PR3000LCDRTXL2U — battery date reset?
So, I just rebuilt the battery packs in my PR3000LCDRTXL2U and its expansion unit. You don't want to KNOW. If the internal batteries have overheated and bulged, you CANNOT remove the battery pack intact even by partially disassembling the UPS, you have to pry the batteries out via the top of the chassis one by one. It's not pretty. Three and a half hours of work including repairing damaged wiring harnesses. ANYWAY . can anyone by chance tell me how to reset the battery DATE on a CyberPower UPS using upscmd? -- Phil Stracchino Babylon Communications ph...@caerllewys.net p...@co.ordinate.org Landline: +1.603.293.8485 Mobile: +1.603.998.6958 ___ Nut-upsuser mailing list Nut-upsuser@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] CyberPower PR3000LCDRTXL2U and NUT 2.8.0 - mute?
On 3/21/24 14:00, Greg Oliver via Nut-upsuser wrote: All I can say is definitely replace the batteries if you are going to keep using it. The CyberPower(s) I have had in the past all have the battery check that cannot be turned off and when the batteries are actually "dead" the unit will kill the load to everything every time it runs the check. Just FYI. Yeah, definitely planning on replacing the batteries. Just trying to mute the alarm in the meantime. And probably going to suck it up and buy new battery packs instead of buying new SLA batteries and rebuilding them, because Cyberpower's battery "trays" are ghastly. I've seen thicker plastic on notions-counter blister packs. -- Phil Stracchino Babylon Communications ph...@caerllewys.net p...@co.ordinate.org Landline: +1.603.293.8485 Mobile: +1.603.998.6958 ___ Nut-upsuser mailing list Nut-upsuser@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
[Nut-upsuser] CyberPower PR3000LCDRTXL2U and NUT 2.8.0 - mute?
I have a CyberPower PR3000LCDRTXL2U with a BP48V75ART2U expansion chassis, which I am monitoring using NUT 2.8.0 (on Gentoo Linux). TThe UPS appears to be telling me that the batteries need replacement due to age. CyberPower support has confirmed that for me and told me how i should be able to mute the alarm from the front panel until I can replace the batteries, but it doesn't appear to be working. I can send the PR3000LCDRTXL2U a beeper.disable or beeper.mute via upscmd, and upsc dutifully reports ups.beeper.status: disabled, but it keeps beeping. Anyone else with a PR3000LCDRTXL2U have any useful tips? -- Phil Stracchino Babylon Communications ph...@caerllewys.net p...@co.ordinate.org Landline: +1.603.293.8485 Mobile: +1.603.998.6958 ___ Nut-upsuser mailing list Nut-upsuser@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
[Nut-upsuser] upsset.conf : Restriction directives need updating
The good news: While gathering information for this post, I solved the ORIGINAL problem I was going to post about, which was figuring out how to change the low-battery limit on my CyberPower PR3000LCDRTXL2U UPS with expansion chassis. With three battery packs, the default 20% is absurd. However, during the course of finally getting around to getting upsdet.cgi working, I found the security advice in upsset.conf to be highly outdated. upsset.conf gives the following access restriction syntax ... # # deny from all # allow from your.network.addresses # This syntax is long obsolete, at least in Apache. It should currently be done in a fashion generally similar to this: ScriptAlias /upsstats.cgi /usr/share/nut/cgi/upsstats.cgi ScriptAlias /upsset.cgi /usr/share/nut/cgi/upsset.cgi Options +Includes +ExecCGI AllowOverride Limit Require local Require ip aa.bb.cc.dd/nn -- Phil Stracchino Babylon Communications ph...@caerllewys.net p...@co.ordinate.org Landline: +1.603.293.8485 Mobile: +1.603.998.6958 ___ Nut-upsuser mailing list Nut-upsuser@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] The name HOSTSYNC is confusing. Can we do better?
On 1/19/22 06:10, Roger Price wrote: The man page for upsmon.conf explains the HOSTSYNC directive: HOSTSYNC seconds upsmon will wait up to this many seconds in master mode for the slaves to disconnect during a shutdown situation. By default, this is 15 seconds. When a UPS goes critical (on battery + low battery, or "FSD": forced shutdown), the slaves are supposed to disconnect and shut down right away. The HOSTSYNC timer keeps the master upsmon from sitting there forever if one of the slaves gets stuck. The explanation is clear. but the name "HOSTSYNC" is not. It seems to me that if the directive is to provide a maximum time that the primary should wait for secondaries to shut down, then it would be better if it were called MAXWAITTIME. Good call IMO. -- Phil Stracchino Babylon Communications ph...@caerllewys.net p...@co.ordinate.org Landline: +1.603.293.8485 Mobile: +1.603.998.6958 ___ Nut-upsuser mailing list Nut-upsuser@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] On retiring some terminology
On 3/12/21 9:14 PM, Rusty Bower wrote: > Manager/subscriber seems most accurate > > Sent from my iPhone > >> On Mar 12, 2021, at 20:13, Douglas Parsons wrote: >> >> >> In place of secondary how about subscriber? It would be accurate to >> the role. I'd been going to suggest controller and ... something. Controller and subscriber? -- Phil Stracchino Babylon Communications ph...@caerllewys.net p...@co.ordinate.org Landline: +1.603.293.8485 Mobile: +1.603.998.6958 ___ Nut-upsuser mailing list Nut-upsuser@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
