Any team using NEOs, CANcoders, and labview?

I’ve genuinely spent so many hours trying to get it to work and I just can’t. When I use the built in encoders it accumulates drift, and when I try manual PID with the cancoders it just spins rapidly. Does anyone have code using cancoders, NEOs, and labview? I’d settle for falcon 500 code as well, but we use the rev ecosystem. I currently have some basic swerve where the modules never turn past 360 degrees, but that’s very basic. I tried watching the videos on labview swerve, but they are for a completely different way of coding the robot than what we do. Any help would be appreciated.

Can you post your code and can you describe what you are trying to do with the neo and cancoders?

What do you mean when you say the built in NEO encoder ‘drifts’?

we had the same problem 2 years ago with the at home I do not know what we did to fix it but here is our code GitHub - cavineers/RobotCode2021: Robot Code for the 2021 at home challenge.

we aren’t using swerve anymore :frowning:

Our github code for thrifty swerve actually uses the cancoders to PID the steering motors instead of using the internal motor counts. We knew it was the absolute WRONG way to do it if you have internal encoders, but at the time we weren’t sure what motors we were going to use for steering so it was a quick and easy way to make the steering code motor-agnostic.

I want to add to this that we worked for 2 months prior to the season start last year programming the swerve and getting manual and auto modes working semi-acceptably. Even then, it was a long discussion between swerve and tank. In fact, our decision matrix pointed toward tank, but we decided to make a leap of faith / emotion and do swerve anyway.

Even if you don’t run it this year - don’t give up. It’s a great learning experience.

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.