mastodon - @astrsk
lemmy - @astrsk

  • 0 Posts
  • 40 Comments
Joined 2 years ago
cake
Cake day: June 17th, 2023

help-circle





  • Right. In 2017 I had to buy a car and decided to go new. For $20k I got a hatchback that serves all my needs, even as a fwd vehicle. There isn’t a single EV on the market that comes close to that price, let alone in that form factor.

    Edit: I should mention that this sub-compact vehicle has 150hp, 4 doors, and seatbelts for 5 (including driver). It’s an excellent family vehicle that’s very safe and would be a great learner’s car in the future. It’s even mechanically simple and easy to repair. If I could just have this exact car in an EV form that didn’t cost 2.5x as much, I would be happy to upgrade.





  • And not to mention the discharge efficiency curve. For LiPo batteries you will see a sort of “coasting” when the battery is at about 3.7v if your load is sufficiently small. But when it’s at 4.0v it will seem to drain quicker.

    I have a 10000mAh battery powering a device that uses 10uA every 30 minutes for about 10 seconds. On one charge it should last about 1 year maybe a little more. The first 2 months it seemed like it lost a lot more juice than was expected but since then it settled in and is now ahead of its estimate. Which means it will speed back up as it goes down below 3.7v.





  • I gave it a try on my bare Debian 12 (kernel 6.1) install last week and a 3090.

    KDE Plasma, on Wayland, worked out of the box but with poor performance. After following the official guide to installing the proprietary drivers, the Wayland session no longer works. After entering my password in SDDM I get a blank screen with a solid text cursor in the upper corner until I forcefully power cycle the machine.

    I’ll stick to x11 for now, which works flawlessly with great performance in games (~200fps in Baldur’s Gate 3, max settings 1440p @ 240hz).


  • I would reasonably expect an increase in expected life / flights of a future model for sure but it will be highly dependent on what’s being tested. NASA aren’t making tools, they’re making instruments, if that makes sense. They aren’t producing a rugged tool for accomplishing a mission that someone buys to use, they’re making scientific equipment that carry out experiments and collect specific data. Even the instruments themselves are experiments, such as the durability of joint designs on the collection arms, or the roter materials selected all have a purpose and associated datapoint.

    All that to say, the expected lifespan / flights on the next model will reflect the mission goals and budget / cost of the project and not necessarily an accurate expectation of the system. More or less “we designed this instrument to deliver x amount of data” not “we designed this tool to survive y number of uses”.





  • Having not watched this yet, I’m going to guess that this failure state basically results in the processor simply incrementing its address pointer indefinitely which will inevitably just loop across the whole contents of the rom, along with current state ram data? Outputting audio might be a bug in this case, a hardware bug that is. Unless it was an esoteric way for the system designers to debug using oscilloscopes? Maybe it was meant to just dump ram contents but ended up hitting all rom addresses? Either way, I’m excited to watch this when I get some more time and just wanted to speculate based on the short description of the video I read.