-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wormbot grinding in one corner #2
Comments
99% of the time if something like this is happening it's a problem with alimit switch. Turn limit switch debugging on and see if you can determine which switch is failing. also if the switches aren't physically secured properly they can shift their position and the robot can be hitting things before the limit switch physically gets pressed... While the robot is grinding away look at the limit switch that is supposed to be touched at that corner and press it using a screwdriver or something and see if that stops the behavior...if it does you may need to reposition or replace that switch |
also, we had a similar issues develop once and it was due to the RJ25 cable going to the camera head limit switches failing. |
Hi Jason, I ran the debugging twice and once it started grinding, but the other time it did not. Once it went through a full circle, it started printing repeatedly x negative y negative, but not x positive or y positive. However it did look as though the switch was physically compressed. I am not sure I know which cable you are talking about. |
Hi Jason!
We are having a slightly different issue with the wormbot. When we begin an experiment it will make several passes over the 12-well plates as expected, however, after a few passes the wormbot will go to the back corner and the motor will continue to spin and grind without stopping. If we readjust the robot toward the front, it will calibrate again and work fine for a while before this issue happens again. Any thoughts on where to start troubleshooting would be appreciated.
Thanks!
Kiley
The text was updated successfully, but these errors were encountered: