Controller mapping issues

[Hamiltonian]

We’re using Logitech F310 controllers. The buttons all map correctly into the FRC Driver Station (current, v24.0.1), but about half fail to map into the FRC PC Dashboard (current). We’re using JAVA and have created a simple tank drive program for testing purposes, but the controller fails to properly control the drive (no specifics - I will ask one of students to post more if needed).

Our workspace is offsite, so I’m asking with incomplete information. Double-checking the CANbus addresses is at the top of my list, but I do think that mapping was done correctly.

We’re short on mentors and lack a software mentor, so this could be something simple/obvious we’ve overlooked.

[four]

Have you checked that the switch on the back of the controller is set to the correct mode for what your code is?

[Hamiltonian]

Thanks for the reply. The mapping is correct in Driver Station but remains incomplete in the FRC PC Dashboard, regardless of the setting of the backside switch. I hadn’t noticed that button before - thanks for the tip.

[NewtonCrosby]

What do you mean “FRC PC Dashboard”?

Is it the simulator that you mean FRC PC Dashboard?

[Hamiltonian]

This^ It was called LabVIEW Dashboard, apparently? Do we even need this? Last year we built an Everybot as a warm-up to joining FRC and I don’t recall using this.

[NewtonCrosby]

You do not need that for your robot to function correctly.

Other Dashboard alternatives exist, SmartDashboard, Glass, Shuffleboard to name a few. Those are all provided with WPILib’s installer. There are other 3rd party dashboards that exist as well.

The main thing to know is that the axis values and button numbers MUST be correct in Driverstation because the axis and button polling will be sent to the robot as the Driverstation sees it. If Driverstation is good, and the robot is still not working, then we can help troubleshoot the code.

Best thing to get help with Code is provide a Github (or similar) link to the entire code repository. I don’t know Labview, but if you’re using Java, Python, or C++ I’m happy to take a look and help your team get things driving.

[Hamiltonian]

Thanks @NewtonCrosby. If that Dashboard is unrelated, we’ll get the CANbus enumeration checked. The test code we’re using is a slightly amended version of: SPARK-MAX-Examples/Java/Tank Drive With CAN/src/main/java/frc/robot/Robot.java at master · REVrobotics/SPARK-MAX-Examples · GitHub

I will ask a student to create a team Github account so we can post our full test code.

[NewtonCrosby]

Good luck, I would recommend looking at some of the WPILib examples as well.

For example, the Command-Based framework does a great job organizing code and making it work. The most up-to-date example of this paradigm in FRC is the Rapid React command-based bot.

If you need an intro to commands, I like this resource.

[Hamiltonian]

Thanks. I’ve seen lots of recommendations for the Command-based. Our Software Team (of one) followed the KitBot code which appears to be Command-based but were unable to get the robot to respond to the code.

As we lack a programming mentor at the moment, I think we’re stuck with kludgy Timed code this year.

[NewtonCrosby]

I was talking to another mentor that’s been doing this for 15+ years.

The general consensus was that we both agree that even though documentation is a million times better than it was when we both started, there’s just so much to learn to the point where it’s hard to imagine getting started.

If you need any help on the software side, feel free and ping me.