We ran our auto gear placement in our first two quals matches, and had no issues. In our third, fourth, and fifth matches, our auto didn’t run. Like, not at all. It didn’t even enter the auto mode. We have a custom Preferences-based chooser system set up currently, and it’s running fine on the practice field and pit. It is also seeing the preferences value change on the robot, we tested this by having it print what auto mode it’s in at the field, and the robot is seeing the value. I know it is not an issue with the auto mode being created from the chosen auto value, because it is working on the practice field and pit, just not in matches. When we hard coded in our auto to bypass the chooser, it worked fine. Our DS logs also show the robot transferring to autonomous successfully. Has anyone else had this issue?
Yes we had this problem last year when using the Smartdashboard. The solution we used was to set the auto mode with a custom dial that acts as buttons to the Drive Station. Haven’t had a problem with auto not starting since. I think the Drive Station network is more robust than the Networking Tables.
One thing that might make a difference is the network connection. Windows classifies networks differently, and the application of firewall rules is not easy to predict in advance. If your Driver Station computer has one of the three firewall settings on, it might keep the Network Tables connection from getting through properly.
Check the Windows Firewall with Advanced Security settings to make sure that the firewall is off in all three of the Domain, Private, and Public profiles.
Thanks for the comments guys. We know the chosen auto value is getting through to the robot, because we are printing it back (what the robot sees). It seems to me almost like autonomousPeriodic isn’t running, but it works when we hard code the auto it works.
Add a connection indicator to your SmartDashboard (View>Add>Connection Indicator) and hold a thumbs down until it turns green.
We know the smartdashboard has connection, as all of our displays are updating.
Hmm…try updating your WPILib plugins to the latest version, I know there were some autochooser bugs that were fixed in 2017.3.1
We aren’t using the actual autochooser, we wrote a custom system using preferences.
You told us it was working in the pit and on the practice field. Does it print the proper value when on the competition field, but not run the associated autonomous routine?
When (and how) does your code print the mode selection value?
When (and how) does your code use the value to decide what autonomous to run?
Do you have any instrumentation/debug code that can help you determine whether any autonomous routine is being run?
Might your autonomous function have an accidental dependency on having the robot run teleoperated first? If you power up the robot and have it do a “practice” mode sequence before ever enabling it in teleop or autonomous, does it still work when tethered?
Basically we have the robot read the number we typed in and feeds it back into a number field. This worked on the competition field. This number is plugged into a switch statement and assigns the auto mode. This worked in our first two matches. I know the auto mode isn’t even being run because our gyro didn’t zero. When we do what you said with practice mode on the practice field, it works fine.
A previous poster was asking when you pull the data from your chooser. For instance, do you do it in autonomousinit or in robotinit?
Autonomous Init.