Closed ErikBoesen closed 6 years ago
I imagine this has to do with a value stored in networktables?
Yes, it does.
This will happen in competition if you don't restart the dashboard as well. Has to do with the way nt stores things. Where in the code does it use it, cause theoretically you should be setting this value at the beginning of auto anyway
@twinters007 Do you have an idea for handling this a better way? We can't afford to let the robot spin the other direction and cross out of the null zone into the other team's territory; that would be a gigantic penalty.
Should we just repeat the same code from the other part of the scale autonomous rather than switching, at least until we come up with a better idea? A little repetition imo is not as bad as non-functionality.
@JosephCarpenter My PR fixed this.
We're just using target_direction
to get the direction relative to the actual target now.
In opposite side scale auto, we switch between
left
andright
positions. This change persists across runs, though. Won't really matter in competition as we always reboot the robot, but it's annoying for testing and generally a messy way to do things.