View Single Post
  #359   Spotlight this post!  
Unread 09-02-2012, 14:31
EricVanWyk EricVanWyk is offline
Registered User
no team
 
Join Date: Jan 2007
Rookie Year: 2000
Location: Boston
Posts: 1,597
EricVanWyk has a reputation beyond reputeEricVanWyk has a reputation beyond reputeEricVanWyk has a reputation beyond reputeEricVanWyk has a reputation beyond reputeEricVanWyk has a reputation beyond reputeEricVanWyk has a reputation beyond reputeEricVanWyk has a reputation beyond reputeEricVanWyk has a reputation beyond reputeEricVanWyk has a reputation beyond reputeEricVanWyk has a reputation beyond reputeEricVanWyk has a reputation beyond repute
Send a message via AIM to EricVanWyk
Re: Banebots RS-775 Case Short

Quote:
Originally Posted by de_ View Post
re motors coming from factory shorted

Wow. Even after last years feedback, the manufacturer has still not solved the problem. Worst still they apparently are not even doing simple QA tests on them before shipping. We (or Banebots) need a new motor supplier. I have 6 of these on order and I can't see how I can risk using them.
This problem has been notoriously intermittent, and I don't know of a good way to know whether a particular motor doesn't have the issue. Detecting a case short is a certain way to know that there is a problem, but not detecting the short doesn't mean that there isn't a problem. Rotating or jostling the motor can hide or expose the defect.

I'm of the opinion that the "case-zap" method doesn't fix or clear anything, it just shakes things up hard enough to push the defect back into hiding for a bit. It can then pass bench testing until something else causes it to express again.

I'm willing to believe that Banebots is performing best faith QA, and that the defect is too finicky to be caught by their testing. My suggestion is to teams is to treat all of these motors as defective regardless of testing and isolate them appropriately or switch to a different motor.