Quote:
Originally Posted by JVN
James,
This activity seems like it would be very "high effort, low reward" compared to other developments an FRC team could be doing.
I'm going to assume you're going to do some driver drills... if your team isn't the type of team that does driver drills, you're probably not capable of doing what you're describing anyways.
Training drivers isn't that hard. If you're going to run some driver drills you're going to quickly move past the part of the learning curve where this software would matter anyways.
Maybe I'm under-estimating the reward, and over-estimating the effort required for meaningful result.
-John
|
It was high effort, but now it is a well-defined solution... so it's really an inherited benefit... with no time invested here... but my time invested now is in learning about interfacing with the basics robotics drive itself... gears torque etc... stuff I need to learn no matter what solution we choose. I have gone over your spreadsheet with a fine tooth comb and use this as a simulation. (More on that in the other post on cof tomorrow).
We do driver drills... I listen to the driver's needs and I've talked with Jim Z as I'm very inspired by Team 33's method of drive control. I am not afraid of new innovation. We have to continuously challenge old paradigms and believe and continue to try new things.
For me the reward is that great feeling I saw when we continued to successfully balance the ramp for Rebound Rumble... to make the driver feel like he is at one with how the robot performs. I remember the moment I hesitated when I crashed my car because it was not intuitive to me (I did not know how to quickly react to slow down a standard stick drive). The reward is for a user to not need to worry about what to do when he panics because it is intuitive.