|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
| Thread Tools | Rate Thread | Display Modes |
|
#16
|
|||
|
|||
|
Re: Problem with driving
In your driver station logs do you see a high trip time or a lot of missed packets?
In Q32 at SCH, we experienced bandwidth issues because too many people were pulling full or close-to-full quality camera feeds. The packet time skyrocketed, and the robot was hitting disable timeouts about every 3 seconds ( DS would blink No Robot Comms for 1/2 second then reconnect ). If you don't see any of these symptoms, it really really seems like your just don't have enough torque. EDIT: Ignore this, I just saw your post saying you had low trip time Last edited by Andrew Lobos : 18-03-2013 at 23:06. Reason: oops |
|
#17
|
|||||
|
|||||
|
Re: Problem with driving
Are you using Victors, Jaguars, or Talons on your drive motors? Jaguars will "brown out" at about 9 volts.
|
|
#18
|
|||
|
|||
|
Re: Problem with driving
Quote:
In 2011, we did the same thing with 8 inch wheels (traction in back, omni in front) but with a reduction between the gearbox and the wheels (chain). The robot barely had enough torque to turn. We ended up switching the CIMple boxes with Toughboxes since we were using a third CIM somewhere else that year. If you have 2 CIMs or MiniCIMs to spare, you should really put them in those CIMple gearboxes. Unless you have a need for the CIMple box speed, you might be better off switching to the kit toughboxes. Even then, I would still put two CIMs in, otherwise you'll just get pushed around by everyone else. |
|
#19
|
|||
|
|||
|
Re: Problem with driving
I think we are going to change the drive train if our weight permits it. I will get back to you guys within a day or three. Thanks for all your help though. By Lenepe, we are going to be awesome.
|
|
#20
|
|||
|
|||
|
Re: Problem with driving
During the regional, we had a similar issue where our robot would work in the pit area but would "lag" when we drove it on the field. At first we thought it was a cpu issue and then we made the wait loops a little longer (tenth of a second i believe). That did not get rid of the issue.
We started jerking the robot back and forth in the pit to see if we could reproduce the issue. The light on the jaguars were turning from solid yellow to flashing yellow. We traced the problem back to the cRIO. Specifically, our ethernet cable was zip tied really tight and it would lose communication everytime we jerked the robot. Simply creating some breathing room for the ethernet cable solved our issue. Hopefully your problem is easy to solve as ours. |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|