A lot of this is in the Talon SRX Software Reference Manual...
http://www.ctr-electronics.com/talon...ical_resources
Quote:
|
The only con I have comes from having to manage your code in two different places. Your PID tuning/etc comes from the Talon web interface, and the logic code comes from the robot code.
|
You can also set your gains using robot API(section 10 Talon SRX software ref manual). Also check out all of our examples on our github/software reference manual. Your post suggests that web-interface is the only way.
Quote:
|
We have a filter for "maximum speed" on each mechanism as a safety when new kids are learning PID, and that filter is the last line of defense when things go awry.
|
Talon SRX allows you to cap the maximal outputs during closed-loop (section 10.5). So that means you can do this with SRX Closed-Loop as well.
Quote:
|
Your robot code has to perform all boundary and logic checking prior to sending the desired position value to the SRX.
|
You mean you have to tell the Talon what position to servo to, which is correct. How else could that work?
Quote:
|
we can read these sensors using can talon class and use the values in our robot code. Even if we don't want to use any close loop control on the talon. To me it looks like a no brainer method to avoid running out of ports.
|
Section 16.9 talks about that a bit, but yep that's the point. Talons can be used to extend the number of inputs in your control system: limit switches, analog inputs, Pulse-width, and quadrature signals, and more to come. Checkout section 20.5 to tune how often signals get updated.
But I think you'll find the closed-loop examples available for Talon SRX will help quite a bit if you go that route.