Have you ever hurt yourself from your own code?

Re:Have you ever hurt yourself from your own code? by Doxin on Friday May 28, 2021 @02:55AM (#27312474)

I don't work in robotics so I might be entirely off-base here, but surely the interlock process would consist of hitting an E-stop somewhere? What was this process that took long enough for said manager to get annoyed with?

[ Parent | on HN ]

Re:Have you ever hurt yourself from your own code? by jdiez17 on Friday May 28, 2021 @07:54AM (#27314277)

You usually only hit the E-stop when the robot is moving in a way that could be dangerous. Safety interlocks are intended to minimize the probability of such a dangerous situation. The robot won't move unless all of the interlocks are outputting a "go ahead" signal. The most common interlock is a (switch/laser/hall effect sensor/whatever) that detects the door to the robot cell is closed.

[ Parent | on HN ]

Re:Have you ever hurt yourself from your own code? by Doxin on Monday May 31, 2021 @03:14AM (#27341173)

Well yes I know that much, but surely having an e-stop pressed will stop the robot from moving, same as any of the other interlocks? And opening/closing a door or the like doesn't seem like something that takes a long time either...

[ Parent | on HN ]

Re:Have you ever hurt yourself from your own code? by monocasa on Friday May 28, 2021 @10:55AM (#27316078)

That cut power and the robot needed to fully recalibrate afterwards which took time while iterating trying to replicate a defect.

[ Parent | on HN ]

Re:Have you ever hurt yourself from your own code? by Aeolun on Friday May 28, 2021 @03:49AM (#27312758)

I assume you still need it to move, not be entirely turned off?

[ Parent | on HN ]