Slashdot Mirror
ESR's Newest Project: An Open Hardware/Open Source UPS (ibiblio.org)
An anonymous reader writes:
Last month Eric S. Raymond complained about his choices for a UPS (Uninterruptible Power Supply), adding that "This whole category begs to be disrupted by an open-hardware [and open-source] design that could be assembled cheaply in a makerspace from off-the-shelf components, an Arduino-class microcontroller, and a PROM...because it's possible, and otherwise the incentives on the vendors won't change." It could be designed to work with longer-lasting and more environmentally friendly batteries, using "EV-style intelligent battery-current sensors to enable accurate projection of battery performance" (along with a text-based alert system and a USB monitoring port).
Calling the response "astonishing," Raymond noted the emergence within a week of "the outlines of a coherent design," and in an update on GitLab reported that "The response on my blog and G+ was intense, almost overwhelming. It seems many UPS users are unhappy with what the vendors are pushing" -- and thus, the UPSide project was launched. "We welcome contributors: people with interest in UPSes who have expertise in battery technology, power-switching electronics, writing device-control firmware, relevant standards such as USB and the DMTF battery-management profile. We also welcome participation from established UPS and electronics vendors. We know that consumer electronics is a cutthroat low-margin business in which it's tough to support a real R&D team or make possibly-risky product bets. Help us, and then let us help you!"
There's already a Wiki with design documents -- plus a process document -- and Raymond says the project now even has a hardware lead with 30 years experience as a power and signals engineer, plus "a really sharp dev group. Half a dozen experts have shown up to help spec this thing, critique the design docs, and explain EE things to ignorant me." And he's already touting "industry participation! We have a friendly observer who's the lead software architect for one of the major UPS vendors." Earlier Raymond identified his role as "basically, product manager -- keeper of the requirements list and recruiter of talent" -- though he admits on his blog that he's already used a "cute hack" to create a state/action diagram for the system, "by writing a DSL to generate code in another DSL and provably correct equivalent C application logic."
He adds to readers of the blog that if that seems weird to you, "you must be new here."
Calling the response "astonishing," Raymond noted the emergence within a week of "the outlines of a coherent design," and in an update on GitLab reported that "The response on my blog and G+ was intense, almost overwhelming. It seems many UPS users are unhappy with what the vendors are pushing" -- and thus, the UPSide project was launched. "We welcome contributors: people with interest in UPSes who have expertise in battery technology, power-switching electronics, writing device-control firmware, relevant standards such as USB and the DMTF battery-management profile. We also welcome participation from established UPS and electronics vendors. We know that consumer electronics is a cutthroat low-margin business in which it's tough to support a real R&D team or make possibly-risky product bets. Help us, and then let us help you!"
There's already a Wiki with design documents -- plus a process document -- and Raymond says the project now even has a hardware lead with 30 years experience as a power and signals engineer, plus "a really sharp dev group. Half a dozen experts have shown up to help spec this thing, critique the design docs, and explain EE things to ignorant me." And he's already touting "industry participation! We have a friendly observer who's the lead software architect for one of the major UPS vendors." Earlier Raymond identified his role as "basically, product manager -- keeper of the requirements list and recruiter of talent" -- though he admits on his blog that he's already used a "cute hack" to create a state/action diagram for the system, "by writing a DSL to generate code in another DSL and provably correct equivalent C application logic."
He adds to readers of the blog that if that seems weird to you, "you must be new here."
If a UPS is going to burn down my house, I want it to be a UL listed device. The insurance company is not going to give a shit if I was super careful in putting it together. They're kinda pissy about homebuilt electrical stuff that burns down your house.
This is one of a plethora of currently closed-source products that could stand some competition! Ignore the nay-sayers, of which there plenty, and continue to push the boundaries. We need guys like you, whether we know it or not...
It's about time we moved past shitty lead-acid batteries for UPS systems.
Where are my Li-ion UPS systems? Where are my server/workstation 1800 watts sustained over 30 minute battery options? I want my damn server to have enough time to shut everything down. No more of this "suspend to ram/disk", I want it actually shut down, and if something hangs, not sit there at the screen waiting (I'm looking at you windows) for someone to close whatever is running/hung.
and god damn windows et al software updates that want to run when you shut down.
1) skip the fucking usb. Go with network. Or at least allow a usb/network adapter. 2) it is long past to have a direct dc line from battery to going past computer power supply. Converting from DC to AC and back is so inefficient. Instead have 48V connector and let power supply take it down. 3) ideally, rack mountable.
I prefer the "u" in honour as it seems to be missing these days.
That was uncalled for. You can add information to a topic without being rude.
"Lock and load, Brides of Christ!"
For most a lot of recreational marine use, the usual battery choice seems to be AGM batteries and these usually drive a mix of direct DC loads and an AC inverter.
There are some people that use flooded lead acid batteries, but these tend to be maintenance heavy and that can be a problem when batteries aren't always easily accessible.
I don't think the marine use is any less demanding than a UPS when you consider that driving an inverter is basically UPS use. Much of the time the batteries are under charging current in marine, either from propulsion alternators or due to generator running.
The newer larger vessels seem oriented towards running as much as possible off the inverter. I've seen some larger setups include DC inverter air conditioning due to its low start current requirements, allowing for (limited) air conditioning off the inverter. I think mostly this is for pilot house use when the vessel is under way and is getting power off the alternator.
Solar adoption on power vessels is less than you might expect, but I see setups close to 1500 kw on some new models. But they're still highly generator bound if you want stuff like large air conditioning, water makers, or large appliances like stoves or washer/dryers.
I'll start by pointing out some issues in ESR's current plan.
He is aiming to supply 230W for 15 minutes, which he says will power a "typical desktop system with 4k monitor." It won't, for that you need at least 500W and unless you want to play a careful balancing game more like 1000W. Sure, you system might average 230W, but peak load...
He also wants to use Upverter for electronics CAD. Upverter is a proprietary, web based (!) schematic capture and PCB layout system. It makes no sense at all considering that Kicad is both Free and better in pretty much every way. Kicad and git are a proven solution.
The other issue is lithium batteries. There is a reason SLAs are used, and it isn't just greed. They are cheap, easy to use and robust. You don't really get issues like one bad cell making your whole pack die, or needing to balance them and manage charging carefully. He complains that vehicle batteries last much longer, but they have complex battery management systems that are not at all trivial to design. Cheap lithium batteries like you find in toys and phones only last a couple of years, worse than SLAs.
const int one = 65536; (Silvermoon, Texture.cs)
SJW, n: "Someone I don't like, and by the way I'm a fuckwit" - AC
OpenUPS2 and NUC-UPS can only provide about 60W, maybe 100W peak for short periods. And they are DC only, so you can't run your workstation monitor from them making saving your work and shutting down a bit tricky. ESR specifically says he wants to run a 150W monitor from it.
Those little things are great for low power DC servers, but useless for workstations.
const int one = 65536; (Silvermoon, Texture.cs)
SJW, n: "Someone I don't like, and by the way I'm a fuckwit" - AC
Am I the only one with a $120 APC UPS with $50 replacement batteries every 2 years that does exactly what OP was looking for? And I get 35+ minutes of action time for my network gear, primary computer and one flat panel, complete with usb connectivity that shows up and is addressable in Linux.
Nevermind, just open source it. That solves the problem.