Why it is not done is unfortunately down to economics.Elfen wrote:I'll admit that the R-Pi is a sturdy little beast but I have pushed them to their limits. I bought dead ones from ebay to study them. On many of them I can say after checking out the PSU section and that is working, the only thing left that is at fault is the SoC Chip. Replace that and chances are the R-Pi will come back to life. On 2 of the dead R-Pi's I have, the SoC Chip is actually cracked or bulging from the center. It does not take much to replace the chip. With modification to one of the assembly robots, you can have it remove the SoC chip and replace it, bringing it back to life, and that is not hard to do. I'm just asking "Why is it not being done?"
Instead I get the answer of "It's a $30 computer. If it breaks, throw it out and get a new one!" Well, that is not an option to certain communities out there. If one can do repairs with a SoC Chip swap and charge a low price for the service, then this fulfills another part of what Open Source Hardware is about: being able to maintain, repair and upgrade the system; in this case a R-Pi.
On the contrary I imagine it's very hard to do. I can't imagine how one would modify a pick and place machine to remove a SoC and reflow a new into into place.With modification to one of the assembly robots, you can have it remove the SoC chip and replace it, bringing it back to life, and that is not hard to do. I'm just asking "Why is it not being done?
MTBF doesn't really make sense for a device that mostly gets broken by having wires hooked up with wrong voltages or shorts. Depending on the current the resulting failures can and do happen in less than a second.
Can you cite any examples of robots repairing things easily?Robots can repair electronics devices with ease technically ...
What I meant by ''normalized & typical' is a Pi that is used for it's original purpose: to teach coding.ejolson wrote:MTBF doesn't really make sense for a device that mostly gets broken by having wires hooked up with wrong voltages or shorts.
I thought the whole point of the Raspberry Pi is hooking up things to it and then make it work: sensors, relays, motors and what have you. And coding is part of the making it work, some electronics and mechanics the other part. Of course, there is a bit of risk involved, all part of the learning curve.CaptSunset wrote:
No wires hooked up wrong, no overclocking; keyboards, mice & screens separate standardized components.
I was going to make that point but you obviously already made it.Heater wrote:masa-aud,Robots can repair electronics devices with ease technically ...
Of course, there are a lot of things that robots could do but they currently aren't. The entire fast food industry, for example, is ripe for a take over by machines. But like you said and I'll just repeat here, repair, especially board level repair, is hard for a machine to do certainly when the faults are random. This isn't a bad thing, though, because fixing an electronic device is something that people often find more interesting than making a raspberry float.cracked screens on their phones. There is
no robot in that shop performing even this repetitive repair.
On this topic, there is unimaginable irrationality and even insanity. From government sanctioned operations that supposedly properly deal with e-waste but refuse to allow any of it to be reused, which should be the higher purpose. To the people who rant that we need 100% renewable energy, but no nuclear power, and that tax incentives should drive a build out equally everywhere, even solar power in cloudy first world areas while ignoring that the place where most of the devices are made, China, is making them using the dirtiest power available, coal.As for e-waste and global warming, I would imagine that the contribution to that problem by the existence of the Raspberry Pi is a vanishingly small percentage of the total. We have more urgent places to start on that issue.
Let's call it 'mission creep'; if we get in the WayBack Machine and return to 2012, here is Eben Upton discussing the Foundation mission statement with Wired:buja wrote: I thought the whole point of the Raspberry Pi is hooking up things to it and then make it work: sensors, relays, motors and what have you. And coding is part of the making it work, some electronics and mechanics the other part. Of course, there is a bit of risk involved, all part of the learning curve.
Otherwise you could just install Python on a Mac or Windows machine and code the next boring keyboard-mouse-screen program.
I still refute the idea that getting a robot to repair dead Pi is "technically easy". I think it's hard to impossible with the current state of robotic and AI technology.Then repairing each device is costly difficult ( so no robots seem to be cited on the line) although technically "easy".
...especially if the robot itself were Pi powered.Heater wrote:If you build a robot that can fault find and repair a Pi, like replacing the SoC as suggested I'm sure we'd all love to see it.