|
|
|
![]() |
|
|||||||
|
||||||||
| View Poll Results: Favorite Motor Controller | |||
| Talon SRX |
|
58 | 49.57% |
| Victor SP |
|
29 | 24.79% |
| Jaguar |
|
4 | 3.42% |
| Spark |
|
13 | 11.11% |
| SD540 |
|
13 | 11.11% |
| Voters: 117. You may not vote on this poll | |||
![]() |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
|||
|
|||
|
Re: Motor Controllers
Quote:
http://hansenhobbies.com/products/co...nlpconnectors/ http://hansenhobbies.com/products/co.../pt1in_lp_1x2/ |
|
#2
|
|||||
|
|||||
|
Re: Motor Controllers
Quote:
So many fun things to consider.... |
|
#3
|
||||
|
||||
|
Re: Motor Controllers
The 2015 rules has a specific exception for wiring terminations to COTs devices. I would think the 2016 rules would have the same exception. We will see. As a robot inspector, this is not an area I would focus on unless told to anyway.
|
|
#4
|
|||
|
|||
|
Re: Motor Controllers
It is always a risk when "future proofing" something. What you may have done one year may not be legal the next. At the very least, one can use these motor controllers on a practice robot with very little effort.
|
|
#5
|
||||
|
||||
|
Re: Motor Controllers
Talon SRX are my favorite. Unless you need the advanced features of the Talon the Victor SP makes more economic sense. I will wait to pass judgement on the new 2016 controllers when they prove their durability.
Other than size the jaguars don't deserve their bad reputation. We found them reliable when connected correct and not filled with metal shavings. ![]() |
|
#6
|
|||||
|
|||||
|
Re: Motor Controllers
Quote:
Quote:
Quote:
|
|
#7
|
|||
|
|||
|
Re: Motor Controllers
Quote:
I could see the first task for a student in the pit being to crimp some connectors onto a set of spare motors and controllers, ready to go. In fact... *writes that down* As for the poll, I voted for Talon SRX since it seems to offer quite a lot of potential advantages for the fairly minimal extra cost. Virtually every one of our robot failures last year, both on our practice field and unfortunately during our first regional, was some combination of our software addressing the incorrect PWM or DIO, the encoder wired incorrectly, read incorrectly, software values set/reset incorrectly, motors trying to run the forklift past the edge (e.g. we didn't have time to wire in a hard limit switch), etc. If we thought to use the limit switch and encoder functionality in the Talon SRX, and communicate over CAN instead of PWMs and DIOs, our code (and failure modes) could have been much simpler. Last edited by GreyingJay : 23-12-2015 at 11:29. |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|