View Single Post
  #14   Spotlight this post!  
Unread 20-01-2016, 01:51
cbale2000's Avatar
cbale2000 cbale2000 is offline
Registered User
AKA: Chris Bale
FRC #0703 (Phoenix)
Team Role: Leadership
 
Join Date: Apr 2006
Rookie Year: 2004
Location: Saginaw, MI
Posts: 929
cbale2000 has a reputation beyond reputecbale2000 has a reputation beyond reputecbale2000 has a reputation beyond reputecbale2000 has a reputation beyond reputecbale2000 has a reputation beyond reputecbale2000 has a reputation beyond reputecbale2000 has a reputation beyond reputecbale2000 has a reputation beyond reputecbale2000 has a reputation beyond reputecbale2000 has a reputation beyond reputecbale2000 has a reputation beyond repute
Re: Heat/Friction of 775 + Versaplanetary

This might be a dumb question, but what is the ambient temperature of your workspace? Just noticing OPs location, and given the hemisphere and time of year... Just a thought.

We hooked one of our new 775pro motors to a 36:1 two stage (plus encoder stage) VersaPlanetary last week and did not notice any excessive heat buildups during the time we ran it (which was, granted, only a few minutes).

Echoing what others have said, make sure to check your gearbox alignment and lubrication and make sure you're using the correct mounting plate for your motor. If you remove the motor and leave the rest of the gearbox assembled, you should be able to rotate it smoothly by hand at almost any reduction (assuming you're using a hex output shaft, it's a bit harder to grip the round ones).


In my experience, the only failure I've seen on a Versa Planetary was on my teams 2014 robot. The gearbox was at 100:1 reduction running a Bag motor (that stalled quite frequently) on our shooter. When switching out the Bag motor (which had fried) for the more powerful Banebots 775, the gearbox was still quite hot, and the brass(?) hub connecting the motor to the stage above it cracked in half just from trying to re-tighten the set screw. Beyond that, somewhat specific case, I've never had any issues with them that weren't quickly identified assembly user errors.