211–220 of 221 posts
Why are they crediting Scott Manley instead of just grabbing the images from the reports themselves? It sounds to me as if they wrote an article based on the video, and not based on the report. Very lazy journalism.
Earlier quoted context omitted.
Only if you happen to have the relevant skill set. Speaking as someone capable of designing the mechanical hardware and who is broadly electrically savvy but who is most definitely not an embedded engineer: I could bang out a few hundred hacked together dev boards in week, but doing a custom board would take me a few months. Starting with reading 'Prototyping PCBs for Dummies'.
or just hire a guy that knows how to do their job.
Watch a few YT videos, copy-paste the reference schematics for all those boards, delete what you don't use and you are almost done :)
Earlier quoted context omitted.
Which means air space that can get crushed. Either the phone is solid or it isn't.
> Which means air space that can get crushed Would note that air isn't the only substance in a phone that compresses under 38 MPa. (Batteries come to mind.)
Note that I would expect water to seep into a battery at this pressure and that will cause all kinds of issues - including chemical fires underwater. Just not crushed batteries.
Earlier quoted context omitted.
That’s my entire experience in embedded. Everything I get from other companies basically looks like an internship project right down to the pointer arguments with unspecified bounds on the function calls. One of the companies we bought hardware from keeps representing things are working when they only work on devices in the lab. Almost nobody in the space produces anything professional and everything uses Yocto even…
> Almost nobody in the space produces anything professional and everything uses Yocto even for two person projects where Multistrap would be more productive. While I agree with your sentiment that there's a lot of poor software engineering in embedded space (especially in consumer-oriented novelty products, less so in established fields like industrial or telco), I can't but wonder what's wrong with Yocto? In my expe…
If you don’t already know anything about how to do these things in Linux Yocto is good for it. But if you try to swim against the current of the way the layer authors want you to do any of those things you will find it very challenging.
Take read-only root, for example. Usually it’s a one-line change in a config file plus an additional mount should you want an overlay in volatile memory. I don’t see how pulling in layers and config files does anything other than obscure how that works.
For a good example of what I hate about it, try building from Meta-Intel without graphics drivers.
Earlier quoted context omitted.
> 1. The Camera+Card was encased in a separate enclosure made of titanium+sapphire, and did not seem to be exposed to extreme pressures. I wonder what the price of the enclosure was then. Feels a bit like click bait...
It might have been filled with mineral oil, those external enclosures often setup that way so that the enclosure is less extreme to manufacture. Not sure if that would work for camera lenses though unless those were also filled.
Earlier quoted context omitted.
> 1. The Camera+Card was encased in a separate enclosure made of titanium+sapphire, and did not seem to be exposed to extreme pressures. I wonder what the price of the enclosure was then. Feels a bit like click bait...
Clickbait? Where? How? It's literally in the NTSB report, and it's not like, a crazy concept?
Earlier quoted context omitted.
> Encrypted filesystems typically encrypt contents of each file separately - that way you don't need to read / write the whole disk to read it write any individual file contents. Ah, that's not true of "full disk encryption". It usually encrypts the disk blocks. File-based encryption is stronger; you can use different protection classes on different files, you can use authenticated encryption, etc. iOS does it this w…
File-based encryption leaks metadata (which in some cases is bad enough to render it unusable).
Earlier quoted context omitted.
It might have been filled with mineral oil, those external enclosures often setup that way so that the enclosure is less extreme to manufacture. Not sure if that would work for camera lenses though unless those were also filled.
As someone who was on the product team for a 6000msw video camera, it's probably not filled with mineral oil. I doubt anyone makes subsea camera bodies/optics completely from scratch, and off-the-shelf units are not designed for pressure. In ours we used Sony camera internals, the enclosure was atmospheric, filled with dry nitrogen to reduce condensation, and the sapphire lens was designed to resist 12500psi and redu…
Earlier quoted context omitted.
It wasn't in the crushed part, it was in the camera's shell, and the camera was mounted outside, if I understood properly.
And: > This still and video camera is rated to withstand depths up to 6,000m (19,685 feet, 3,281 fathoms) Unlike the Titan sub...
Earlier quoted context omitted.
Here; the title focusing on the price is implying that the cheap SD card survived ocean floor environment alone. A surprising amount of stress for its price. Instead, a pressure-proof deep sea camera module was found at the wreckage site. It’s less interesting that an expensive thing rated for ocean depths was intact at ocean depths. Its like “missing child found after 4 days in Alaska temperatures!” gasp! How did th…
> Here; the title focusing on the price is implying that the cheap SD card survived ocean floor environment alone. A surprising amount of stress for its price. I certainly did not read that implication into the title, so it's entirely possible that the author didn't mean it.
- thing survived ocean depths, unexpectedly.
Without either of those, what did you read into the title? "Part of wreckage found at wreckage site"? And you still clicked?