privatelypublic

Lets ignore the open source FUD in the diagram.

Apples to broccoli comparison. Besides what I mentioned being optional (I'm sure it has downsides, probably cost), comparing road legal cars with a supercar is... interesting.

I'll need evidence of "Top power at Top Voltage." Since so little capacity is at that part of the curve, It'd make sense to design around (as in avoid, not feature) it rather than use it.

I suspect theres inductance and capacitance enough that even if the motors can't handle the voltage, it can be "clipped" until the pack comes down. (Especially since fmu these are 3phase AC motors, the motor driver is already regulating voltage and current to produce whatever the optimal waveform is)

I'd be interested in if you can even use dry fire suppression on the 5th floor of a building.

Long winded admission that you might as well pay for google's email service.

Yea. Fun, but not optimal for a product. 1000Hz is already comically faster than any human muscle reaction.

I know the receivers are often in a vulnerable position. But, on my 2008 era car- the code I've seen for SDR decoding is a broadcast MAC, pressure and a temp value.

I'm interested in... why? What are you building that loading data from disk is so lopsided vs CPu load from compiling, or network load/latency(one 200ms of "is this the current git repo?" Is a heck of a lot of NVMe latency... and its going to be closer to 2s than 200ms)

That's routine. Windows generally ends up nuking the OEM partitions if you do golden installs.

Except, zero knowledge replication is why ZFE native encryption got funded. I believe it was Datto specifically.

I'm not sure if anybody is wrong or right. But this should be officially documented, a specific error provided- not "permission denied", and a workflow to fix it that doesn't involve patching the driver.

Try disabling C states in the bios. My 5950x developed that issue, as did a friends 5600x.

What are you thinking the crime would be? He bet his company on a literal toss of the dice instead of the routine figurative ones.

Outside of Bribery and ?SarBox? (Whichever regulation handles kickbacks, etc), I can't think of anything.

It doesn't matter if it's true. And those spec sheets aren't what you'll find on amazon products. I looked at them, didn't see any mention of temperature. Also, stupid things use XT60 connectors. Not remotely appropriate for 150v DC.

Haha, touché- forgot the Pi5 only has a single lane.

The comment came out of knowing if the cable's a little dodgy the timing could be off- scrambling the PCIe signals (easier to just tape it off than look up if its supposed to matter and then tape it off anyway), and the fact my first HBA had the "QC pass" sticker prevent some lanes from connecting and the whole card was unresponsive as a result.

Are they actually extra? Or does the other cable simply route them over coax? Answer here is to grab a couple SFF-???? Breakout boards, a scope, and a signal generator.

Another thing to consider is isolating all but the first PCIe lane.

Suspiciously so. I'd love to see somebody(or somebodies) with an established reputation reverse the controller software & hardware.

Likely a reference to the recent addition of sesame to the allergen disclosure legislation in the US, and the subsequent rampant over labeling.

Nobody seems to remember a bunch of companies receiving rather large fines for pulling known bull-crap "may contain sesame."

Open circuit voltage is _very much_ widely considered to be the maximum. If its not spec'd openly as " at temp X" then it's reasonable to expect it to be invariant.

"Voc 37v @ 25*C"

Vs

"Voc 37v"

Edit: Isc is the same- max current.

That's humanity in general. But yea- general guide says "add up your open circuit voltage and don't exceed that." If something fails because of the panel manages to get more than 1000W of solar flux, and is cold... it's the mfgr's problem.

I need to actually look up why the extra flux increases voltage. Maybe it really doesn't but just moves the MPP to a higher voltage by having more current.

MosFET's or IGBTs are likely what failed. And, capacitance is something you do not want on a string of PV.

DC starts getting really nasty to deal with somewhere between 36-52v, with 150v of panels not being something joe-blow should be able to buy on amazon. Designing these systems to be safe is difficult.

Everybody entering you mean.

Throw a corpse in the car first, and you have a reasonable comparison.

Thats a policy to have when buying things in general. Even more so when gram for gram it holds 1% the energy of gasoline... but doesn't need the help of oxygen, or any decernable trigger to make a hash of things.

Can't recommend charging cells that have fallen below their official stop voltage- the liability and risk is too high. However, numerous papers have shown that the serious risks happen if they're reverse charged.

I wouldn't use anything but a bench supply stuck outside though.

4.2v for 100% SoC (State of Charge, charging), settles down closer to 4v once charging stops (likely not exactly correct, just my rote memory). 80-90% of capacity/SoC is between 3.7-3.8v.

The remaining 10-20% is above 3.8 and below 3.70v. 4.2v is the max to ever intentionally apply to a cell, and 2.5v is the minimum anybody specs as end of discharge.

As such- the "nominal" voltage is 3.7v or 3.8v.

Possibilities for 3.3v cut off include: LEDs' combined forward Voltage, a BMS set to that voltage, high drain applications pulling the voltage below a lower (potentially much lower at 10C to 50C discharge) cutoff voltage.

These are, of course, for NMC lithium secondary/lithium ion cells. NOT LiFePO4/LFP/LTO/Na-ion.

Theres lots of FUD, but most lithium stories are Li-Po cells (cell phones, RAdio-Control, laptops). Of the Li-Po's- most of them are for RC usage without any inbuilt protection.

LiPo's are beat treated like they're ziplock baggies full of 100mL of gasoline. If you handle them, I suggest buying an Ash Pot- their double walls give you a chance of containing a flaming pack. Best to just do it outside though.

I don't think the debate will end until Hard AI's are common- and even then philosophers will keep going.

Firing projectiles to destroy cameras (it doesn't matter how the slug is thrown) is... oh why bother, people won't change.

spray-chalk on a stick.

Yea, .Net has massively improved. I just had an awful employer who burned me out- possibly for good.

I don't think I need to say more than: 98% of the code base was ASP.net backed by .Net FW 1.1, the rest was VB6.

Sounds like the VR headset problem in a nutshell to me.