"johnnysweekends" testing Automotive 12v sodium-ion car starter battery.
I've been searching for information all over, and it's surprisingly hard to find the details.
I see that sodium is much better than lead but not as good as lithium, but cheaper and nontoxic, so I went looking for why Pb batteries aren't dead yet and replaced by Na everywhere.
Looks like the alternators will have to be replaced (or can they be reprogrammed?). Any mechanics or engineers here have additional insights?
Also should be applicable to UPS batteries. Anyone building those?
Pb car batteries are optimised for automotive use and the alternators are matched.
car batteries have many thin lead plates that will deliver, or take, a lot of current, even when very cold or hot
and the alternators can recharge the battery quickly for lots of quick starts and stops in.the coldest weather, taxi/mom, winter, chicago,christmas,school
as to reprograming, not so much, automotive "charge controllers" were/are designed around Pb batteries ,which are robust beasts with a high tollerance for momentary fluctuations, and as the primary goal is durability ,they are dumb devices
I live off grid, and use a variety of battery types, and voltages, so end uo reprograming regularly, and have even gone as far as to do an alternator deleet on a w250 3/4 4x4 cummins dodge ooerated at the 45'th parallel, and only the solar pannels installed on the hood for electrical power, worked with some limitations in winter, but not for the faint of heart.
As soon as sodium batteries are cheap enough to play with I will be experimenting, but do expect there tobe pecuiarities to there charging cycle, and perhaps limintations on high current discharge.
The test will be getting a DI diesel to start in the cold, after say forgetting to turn on the fuel for 10min, having to then boost from a Pb battery conected to a BIG regular alternator, no fires or bieng "dissabled" allowed.
So the real answer is that the whole automotive sector will have to be compatable for rescue and emergency services to function, not counting just
normal "hey,gimi a boost" calls costing $5000 in repairs or whatever
I assumed they were a poor fit for the starter-motor problem, the need to supply super-high current (load) to get static forces overcome, swing the engine into it's cycle. But, I see they are capable of that burst of high load. So, indeed it begs questions.
I suspect the engineer approach would still be to demand a brick of standard lead-acid battery size, to fit into the hole, and the least possible change to wiring harness and associated behaviour.
Building out cars which need a different box in the hole would be something you do with supreme confidence it isn't making you awkward in the marketplace. If you wind up at the petrol stop in death valley with a dead battery, and alas a good ol' lead acid unit can't fit, that isn't cool. Battery replacement happens in all kinds of places.
Fascinating. I intend to do some research on this, but if you're aware of any methods or protocols to retrain the system for increased motility in absence of fiber, drop a link. I'm pretty sure that an abrupt change would not work well for one adapted to fiber and observe such every time the situation arises. Probiotics and physical activity don't affect this for me.
Edit: I see that the report did pretty much exactly what I say doesn't work. This is confusing when considered through my own experience. Definitely interesting though.
I believe that the documentation is a huge reason why php became so dominant on the net. Human curated, many real-work examples and helpful comments to get things done.
Do you really need "infinite" energy? the universe is a giant clock, a perfect timekeeping device for itself; but then we have nothing to compare it to.
But humans don't hibernate between tasks. I continue living, using about the same amount of energy and oxygen. When one project is done, move on to the next (or have to come up with something else to do).
Sure, but look at the transportation costs alone for getting you to the office and back every day. I'd bet in the common cases where a dev is writing a web app that's not FAANG-scale, you could power the server for 20 years on the energy it takes for you to get to work that one year.
Let's put this in concrete terms: it's surprising how much work you can get out of a Raspberry Pi. An RPi 4 is almost certainly enough to host many small companies' websites until they hit a traffic inflection point. A loaded RPi4 takes about 8 W/h to operate. A gallon of gasoline has about 33 kWh of energy in it, or about 4,000 hours of RPi running time. In other words, a single gallon of gas could run an RPi 4 for about 6 months.
Suppose it takes you a month (or about 20 commuting days) to write your startup's website in Flask, and that it takes you about 1 gallon of gas round trip to work and back. Your car alone just spend about 10 years worth of server power, which is statistically much longer than that website is likely to live.
Now suppose you're a badass programmer who can convert that Flask app into assembler that runs twice as efficiently, and it only takes you 1 month to write it. Now you've spent 40 gallons of gas, and your app can run for 40 years on the amount of energy you spent writing it.
You can fiddle with the numbers a lot, but I think the general point stands: unless your code is very heavily used, it may not be possible to ever break even energy-wise by spending human effort to make it run more efficiently.
Getting to work or staying home has nothing to do with whether I'm writing C or ruby.
For the next 30 years I have to put effort into something, and the number of tasks that need to be done never ends, no matter how quickly I complete them.
My web server gets about 1000 to 1 hits of hacking attempts to valid requests (malformed headers, etc.) so I hope nginx and fcgi handle errors efficiently, because I pay for those cycles.
In those cases, a malformed request is common enough that discriminating between well-formed and malformed should be thought of like a first-class part of handling a request, not an error-handling situation. Errors are when things go wrong that you don't expect to usually go wrong*
*for varying values of usually, YMMV, use your own judgement, etc
You're not describing exceptional events. You're describing pretty much the happy path of any reverse proxy. In fact, in some applications these sort of events outnumber HTTP Status 200-worthy requests.
That assertion is obviously wrong. Think about it: you have a web server listening to the world. Do you really expect all requests to be neatly pointing to sanitized URLs? Of course not. Why on Earth should you assume that handling invalid requests is not one of the primary use cases?
When I want a parameter is an integer, I don't check all the ways in which it's NOT an integer; the happy path is when it _is_ an int and the program can continue, and anything else is an _Error_. If it overflows, that's an error too.
i.e., happy means it's basically the longest path (aside from diagnosing the error).
The question is: should the subroutine set an error number or throw an exception? Knowing the cost for each might help me decide for various situations.
Understanding is not the same as performing. I can "understand" or get the gist of what is being said in german (or lisp, or rust, etc), but it's difficult to read and I can't write it; also could be understanding the mechanics or basic principles.
Literacy is complicated but indispensable in the last century.
I've been searching for information all over, and it's surprisingly hard to find the details. I see that sodium is much better than lead but not as good as lithium, but cheaper and nontoxic, so I went looking for why Pb batteries aren't dead yet and replaced by Na everywhere.
Looks like the alternators will have to be replaced (or can they be reprogrammed?). Any mechanics or engineers here have additional insights?
Also should be applicable to UPS batteries. Anyone building those?