Robot not driving and programmer is unavailable

[Dr. Poptart]

Team 3345 mentor here.

We're in a bit of a bind. We've managed to put together our drivetrain, using two motors per side, and tried to image the cRIO with our program from last year (time-constricted programmer). Whenever we try to drive, it seems like the gearbox motors fight against each other, but we're not sure at this point if the problem is that or if we've got an issue with the motor controllers. As I've said earlier, our programmer is a bit busy at the moment and can't seem to find the time to debug or even rewrite the program. We've tried switching motor inputs on the sidecar to match those from last year's robot (which the code we're using was made for).

We've tried asking him to just rewrite the code, but that doesn't seem to get through to him.

The two motors on the left side of the drivetrain are connected to sidecar ports 2 and 4, whereas the two on the right are connected to ports 1 and 3.

I don't have the code to put up at this moment but as soon as I can get it I'll edit this and put it up for you guys. As for now, I just want to know if any programmer in the area of my school (3200 McCullough Avenue, San Antonio, Texas, 78201) can perhaps come over and teach some of our more available members to program in any language (we're using Java at the moment, but any language is fine), we would really appreciate it.