Quote:
Originally Posted by gpetilli
Since this is a real time system, the value of the joystick may change between the two reads and then you will be writing different speeds to the front and back wheels. Probably not a huge issue, but may cause excess wear on the drive train.
|
Legitimate concern, but probably not a very big one. Your concern is about as critical as me worrying about having to allocate a 8 byte memory block for storing the double.
The loop will run through much much faster than you can humanly move the joystick, and possibly faster than the amount of time it takes to query the value from the joystick. Also, if they built the robot right, moving the two wheels at different speeds shouldn't be a big issue.
So no, no direct disadvantages of doing this manually. It's also a lot easier to fine tune as somebody said. It is kind of like re-inventing the wheel if you're not using any lower level jaguar functions that are inaccessible with the RobotDrive class, but that said, it's always a good idea to be familiar with your code, so whatever you think looks better will probably end up being better for you.
If you wanted arcade drive / meccanum drive, you can do some math and figure it out. Or you can go into the RobotDrive class and copy the math over.