laserswald / camden-robotics Goto Github PK

After messing with the vector classes errors I've noticed something.....coordinate vector is a mess with the interface system. With the interface you are forcing the sub-class CartesianVector to "set the direction" but it can't unless it has a magnitude as well (i'm assuming the set direction is to set the x and y coordinates to contain the setting direction? ). Is there a way you want to fix this? I'm starting to think it would have been easier to have kept to treating vectors with one class and not two.

For some reason the robot code will not use the most updated version of java's Math lib. instead use this import for trig and other stuff : import com.sun.squawk.util.*; and then use the regular java.util.Math for the rest....if you tried to do stuff in Netbeans you should have already ran into this problem. Also, in the code create packages for each class so the compiler knows where to find them. use these for the packages : edu.wpi.first.wpilibj.templates.
and the class name is MathUtils instead of Math (note this is for what's not in the Math class. If the function can be found in the java 1.3 Math class then use it from their, if not use MathUtils.)

Two Joysticks

Chris has requested that we use two joysticks for the driving. I think that we should detect how many joysticks we have connected and shape up accordingly.

Had an idea. Why don't we create a "buffer/interface like" class that acts as the init for the robot. I will manage setting up the devices for the bot based on the read from the config files on boot. I can start working on this write now if you can just pass me what you have so far on the config files

I'd like Vector2 to be an interface. Perhaps made into CoordinateVector, with PolarVector and CartesianVector as subclasses. Sound good to you?

It needs to get gone, we don't need the documentation for other projects in our project.

The code that we worked on needs to be in src/edu/team3329, not deep in the bowels of src/edu/wpi/ blah blah. WE wrote this code, it's in OUR project, not WPI's.

Have all the current netbeans stuff placed into the new project root folder, with it set up so that we can just replace the project on the mini computer, open netbeans, and run that sucker.

Add Eclipse compatible build stuff.

OK so here is off the top of my head what we need to do.
TEST:

• the robot drive with two sticks.
• readings by digital encoders
• basic PID loops and tunings (best for the elevator system we are working on)
• customized robot drive that uses Motion Profiling

I have been having a problem pushing the code to the robot. Can you investigate that for me?