Took a detailed look at autobalnce before our competition tomorrow.
One finding is that we need to change the drive forward instantcommand to a runcommand as instant commands always end immediately therefore the timeout won’t be relevant. We want there to be some time between the arm raises so needs to be a runcommand. This is a must change before we run our match
Another idea for us to try us to add a wait command after the balance target that waits until we are in our balance tolerance of 3 degrees. At which point it could null the balance target and do a very short duration translation in y at a low speed to “lock” the wheels. This is the suggestion from the 1714 team member earlier this morning. I think we could code this up and have it commented out and if we arnt able to balance we have it ready to go.
Took a detailed look at autobalnce before our competition tomorrow.
One finding is that we need to change the drive forward instantcommand to a runcommand as instant commands always end immediately therefore the timeout won’t be relevant. We want there to be some time between the arm raises so needs to be a runcommand. This is a must change before we run our match
Another idea for us to try us to add a wait command after the balance target that waits until we are in our balance tolerance of 3 degrees. At which point it could null the balance target and do a very short duration translation in y at a low speed to “lock” the wheels. This is the suggestion from the 1714 team member earlier this morning. I think we could code this up and have it commented out and if we arnt able to balance we have it ready to go.