3 ms·
> Robots work really well for manufacturing. What they don't work well for is repairs. Robots work well in cases of rigidly prescribed actions. While we are no
by ptero 10y ago
> Robots work really well for manufacturing. What they don't work well for is repairs.
Robots work well in cases of rigidly prescribed actions. While we are not yet there with repairs, we are moving in that direction: for most things, from cars to TVs humans at repair shops will now test large modules and swap out the failing ones (not trying, as they would 30+ years ago, to find and replace a dead resistor or weld a patch / joint, etc.).
This "test and replace modules" strategy means it is easy to design many devices to be robotically repairable; it is just not (yet?) profitable to do so.
- Pica_soO 10y agoThe reason for this is that the whole robotic industry is stuck in lots of small walled in gardens of the past. No templates, no object orientation, no functional programming, its 1984.0 in the factories. There are pushes by some companies (ABB, Stäubli, Kuka, Denso) but they meet resistance by the customer companies themselves, who view code as some sort of throw away part tailored to a machine, not as something of value that could migrate and grow more powerful, and the same for "similar" lines, where only positions and sizes changed. Just get your hand on some big manufacturers "coding standards" for robots- and you know what im talking about. They usually dont have standard libs for you to use and no static analysers (unless you count the ranting guy, who oversees standard upholding).