szczys

Yeah, I know the modern era machines have in-the-field updates, but I assume that wasn't a feature on the Lunar Module. You need a device capable of self-programming and with the state and cost of memory at the time I would think that an impossibility at the time.

There's something amazing about carrying around your dot-matrix printed source code in a roller suitcase. The only thing that says "stable release" more than printing it out on hundreds of pages of paper is launching the computer running the code into space with no hope of doing an update.

I had to read parts of this out loud to my wife and visiting inlaws. You've described my workshop hording practices to a T.

This helps solve our looming automation crisis.

On the other hand, patient handoff is the most dangerous part of the average hospital stay. Shorter shifts for nursing staff equates to more frequent handoffs.

That should be the goal of these "po public utilities". The public pays the upfront cost and assumes the risk of I stalling and maintaining these new systems. The should be able to relish in the benefits when those costs are overcome.

If you haven't seen it, you should watch "Print the Legend", a documentary about a few 3D printer startups like MakerBot, FormLabs, etc. It's on Netflix streaming: https://www.netflix.com/watch/80005444

I had no idea that USB type-c had analog audio support. I thought it was about speed, higher current for charging, and reversible connector.

I must say, I've had the Nexus 5X for about a month now and that reversible connector is a huge improvement over USB micro-B.

Latency looks like a real issue in this demo. If it can be improved this could be important, but think about how impatient you are if your smartphone doesn't respond to your touch immediately. Users have been trained to be irritated by laggy interfaces.

I always think you should start out learning 8-bit micros like PIC or AVR. The datasheets are short enough you can conceivably read the whole thing. This gets you some instinct on what peripherals a micro should have, how to look up their functionality, how to troubleshoot when they don't work, etc.

There's a much higher bar for getting everything working on an ARM controller (ie: did you turn on the peripheral clock before trying to drive that pin?). But I agree, once you're initiated you should prototype everything on a 32-bit micro and then port to smaller or more cost effective chips once all the functionality is established.

Good point, I edited the title. Thanks!

Ah, thanks. I've changed the title.

Sure, as long as it's right in the focus of the beam. If that means putting it in one particular spot, is there any benefit over inductive chargers? That method would be faster and more efficient.

Big win for Open Hardware on this one. You have Tindie with a huge network of small-run (and sometimes not so small) hardware manufacturing and the Hackaday community always looking for unique and interesting stuff to get their hands on.

Bonus: two incredible logos

Several of our writers have been selling on Tindie for years. Leading up to this I talked to as many people with Tindie stores as I could and everyone had great thing to say. This is huge for getting more people into Open Hardware!

Personally I would have thought that the RAM was somewhat similar at each power up. But Voja's research definitely proves me wrong.

I wonder how this would stand up to liquid nitrogen cooling to hold the bits in RAM between resets? How much do you think one bit flipping affect the randomness?

I think it's pretty awesome the group of mech engineers still came in 11th despite the requirement to design your own controller. Cross-discipline challenges like this are great way to build skills.

I think it's two different tools. "Underpowered" chips have their use and their place. Why deal with embedded Linux when I only need to twiddle some IO on a simple protocol?

For me the issue isn't the brand dying out, its decentralized uniformity. If the main organization spins into oblivion (when talented people give up because of this turmoil) who will make sure the unified IDE keeps with the times?

Yeah, I found Chris' mention of having to deal with different regulations from state to state (which only allowed an MD to administer shocks to a patient) an interesting tidbit that went along with bringing this to market. I understand why those were in place and am glad that the tech has become reliable enough to loosen those restrictions.

I'm glad that this has become obvious. From my own experience, it is a wonderful fit. SupplyFrame doesn't shy away from Hacking (we're taking back that term to have a positive connotation). And they align with Hackaday's values of Open Hardware and Open Source Software.

Haven't the carriers already been selling tickets for years? I would image you won't be the first to sit that seat. But you will still be considered an early adopter of civilian space travel!