Talk:CyberPower UPS

From ArchWiki

Split "Network UPS Tools" into its own article

I am editing the "Network UPS Tools" section because it needs some serious work. Ultimately I would like to see most of the content of this section moved to its own article as NUT is not specific to CyberPower UPS. The CyberPower article can then focus on the specifics concerning this brand (namely, that the usbhid-ups will work if anything works at all). -- fsckd (talk) 21:31, 26 June 2017 (UTC)Reply[reply]

I created a new page for "Network UPS Tools" because was some difficult to find about NUT here. I'll improve the page later. I think we can mantain NUT as a alternative for CyberPower owners at the Power Panel. -- rickxyz (talk) 02:18, 01 Feb 2018 (UTC)
Thanks! I completely forgot about this. I'll help when I am able. The CyberPower UPS page should only describe the driver and it should link to the NUT page for the full configuration of NUT. -- fsckd (talk) 22:58, 1 February 2018 (UTC)Reply[reply]
Ok. I'll change the CyberPower page also. -- rickxyz (talk) 13:18, 02 Feb 2018 (UTC)

Changes & writes to all USB TTYs it discovers

I recently encountered some horrible behavior from pwrstatd that might be worth noting. It appears the default behavior of the software is for it to periodically scan through all USB TTYs, change their settings (e.g. baud rate), and write to them. I encountered this behavior when I was trying to develop on an embedded system through a USB-UART bridge, and kept getting interrupted transfers, hardware resets, and garbage output. To me this is atrociously horrible behavior, especially as a default. I have no idea if there's a way to turn the behavior off, as I immediately uninstalled the software and won't have it anywhere near my system again (if the developer did that, who knows what else the software is capable of).

This might be worth noting somewhere on the page, as it took me a while to figure out what was going on. Including buying a new PCIe USB controller as I thought I was having hardware issues.

Phemmer (talk) 19:38, 16 February 2024 (UTC)Reply[reply]