I didn't want to distract from the OP but KrazyCarl92's post requires attention.
Quote:
Originally Posted by KrazyCarl92
I'll bite and share my experience:
I've been a part of a team that has used CAN in 4 seasons. In 3 of those seasons the CAN out right failed at some point and we switched to PWM on at least some of the motors (granted those were all with Jaguars...I have my own opinions on those too).
In 2012, I personally spent over 70 hours ...
And having not used CAN in 2013 and 2014, we were able to get much improved robot performance which I believe ...
|
Yes Jaguars had problems. That's why we created the Talon SRX (which is CAN and PWM). That's why we took the RJ11 out. That's why we integrated termination. That's why we re-wrote the CAN api on the RIO side [props to the NI team and WPILIB for making that happen].
Quote:
Originally Posted by KrazyCarl92
In 2015, Team 20 used CAN with Talons relatively successfully. However, there were still quirks with the code which definitely burned lots of time during build season. I wasn't personally coding, but I recall us taking over a week to iron out the code for switching between current setting and position setting modes of CAN motor controller operation.
|
This was no current-mode last season for Talon SRX. Talon 1.4.crf had duty cycle, closed-loop pos,and closed-loop velocity. Next season of course is a diff story.....
The examples in the Talon SRX Sofware reference manual are meant to save you time. Were they not helpful?
Quote:
Originally Posted by KrazyCarl92
There was also one practice match where a motor inexplicably drove the opposite direction it should have throughout a match. We were unable to reproduce the issue and it never happened again, but it was very puzzling. Not sure of the cause. Taking advantage of any of the elegance or benefits of CAN does involve added complexity.
|
You were having this level of trouble and didn't bother to ask for help from the community or email CTRE?
I haven't found any post from your team regarding this issue. And I know you haven't emailed
support@crosstheroadelectronics.com (since it goes to me).
Did the programmers look at the Talon SRX Software Reference Manual?
This feedback is so far-removed from literally ALL of the feedback I've gotten from last season I'm not sure where to start.
If ANY TEAM has questions/concerns/problems with ANY CTRE product please please PLEASE leverage our support email. Or look around CD for similar posts or post yourself. Or PM me. But email is best. But don't wait a full season and then post it when it's too late to be beneficial. We want to help you.
Carl, if you email us your team's 2015 code, we will figure it out. I have robots dedicated for exactly that purpose. Please PM me if there is more info that you think would be helpful.