Hello everyone. We have the Talons working on our drive base with the new framework, and I spent our snow day taking a look at the new sample code before getting a smidge confused.
It looks like all of the samples that include closed loop control bypass the labview motor control (4 or 2 motor.vi) and access the Talons directly (which makes sense).
If we want to add closed loop control to teleop that allows the driver to press a button to go straight (the pigeon example), how do we wire the xy axes so the driver can control the robot with arcade drive when not pressing the button?
I hope the question makes sense. We are at the point where we understand closed loop control intellectually, and are beginning to implement it.
When you talk about the new framework you mean Command and Control? Or do you mean the new CTRE Phoenix Framework? I am assuming Phoenix.
For the record we are just talking about your drivetrain here not any of the other motors right?
You said “It looks like all of the samples that include closed loop control bypass the LabVIEW motor control (4 or 2 motor.vi) and access the Talons directly (which makes sense).” But this isn’t true for either of the drive examples you can see they are using existing motor option.
The pigeon example is for the drivetrain and uses closed loop control in software. The other closed loop examples (position and velocity) are designed around a non-drivetrain motor. I think this is where your confusion is coming from.
Thank you for your reply. That was indeed the issue. I knew most of the other closed loop examples were for non-drivetrain motors, but got confused when motion magic did not have the arcade or tank drive. Then, I must have assumed they were all like that.