|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
|||||
|
|||||
|
Re: FRC Blog - 2016 Motor Controllers
Quote:
|
|
#2
|
|||||
|
|||||
|
Re: FRC Blog - 2016 Motor Controllers
Quote:
I'd love this for FRC, and a few non-FRC applications I use Talons for. |
|
#3
|
|||||
|
|||||
|
Re: FRC Blog - 2016 Motor Controllers
A continuous sensor option would be nice too. Similar to the continuous sensor option in the WPILib PID Controllers.
|
|
#4
|
||||
|
||||
|
Re: FRC Blog - 2016 Motor Controllers
Even if its not built in, since we can access all the current and speed data, wouldn't we be able to do this on the RoboRIO? It wouldn't be anywhere close to as fast of a loop, but it should be good enough, right?
|
|
#5
|
|||||
|
|||||
|
Re: FRC Blog - 2016 Motor Controllers
I haven't spent nearly enough time trying to track down the correct way to do this, but I would love to know what it is.
|
|
#6
|
|||||
|
|||||
|
Re: FRC Blog - 2016 Motor Controllers
Quote:
If you're just running 4 Talon SRXs on the CANbus, nothing else and you're in a separate thread running your drive, what's the fastest you can run that loop and still get a fresh current measurement over CAN for each one? Same question, but w/ PWM speed controllers and reading current over PDP? |
|
#7
|
||||
|
||||
|
Re: FRC Blog - 2016 Motor Controllers
Quote:
The default status update period for Talons is 10ms. However I know that you can set it even faster. I bet you could do 5ms easily, and could probably push about every 2ms if you are careful with your CAN usage. I would bet that is plenty fast enough, as your mechanical system probably won't react much quicker then that. |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|