I don’t know if this is possible or not but here is my idea.
What if there was a way to “code” your autonomous on the fly using your controller right before the match starts just like how you can use sendable chooser.
An example could be this:
Suppose your robot was made to go through the low bar and you have multiple bots on your team that want want to go through it during autonomous. Using this method all the members can go through the low bar without crashing into each other. By “coding” their autonomous on the fly based on the position they placed their bot when setting up.
It’s almostttt what I was looking for. If I were to use that I need the ability to assign different .csv recordings to different joystick buttons and use sendablechooser or something to select one and go with it. You think that would be possible?
Very doable. Especially with smartdashboard. Just have the autonomous read the wait time from smartdashboard, then drive under. The first time has 0, second have 5, and the third team 10 seconds.
The link posted and the topic of this thread are two different issues. If you’d like to be able to select SmartDashboard options through your controller, than you would have to make your own widget that interacts with JInput in order to get the behavior desired.
(I’d recommend creating a custom dashboard using Swing and networktables.jar but that would be decently difficult. Not as difficult as creating a custom widget, though).
If you change to python you can use a package called pynetworktables2js which allows you to create a GUI in javascript that works with networktables(smartdashboard). You can take a look at our old UI at our UI github page
This seems very nice in theory, but I don’t believe the input had to be via controller. The idea of recreating the motion on a controller during autonomous is great, but I feel like it’s too susceptible to human error (this is referencing the other thread linked: http://www.chiefdelphi.com/forums/sh...d.php?t=136151)
In your scenario, coding it with a small and specific amount of lefts or rights and one up seems so easy to code that you wouldn’t need to set it up with a joystick/controller; you could simply have an electronic interface in which you specify the defense number you’re crossing and your initial position. A complex path is difficult to maneuver perfectly with a joystick, and the simple choice of a defense is easy enough to not need a controller.