Quote:
Originally Posted by Mark McLeod
I'd need to see your code to help much, but I don't see anything.
Are you using imageshack or something like that?
Those sites get block by our school and there's not even an indication that there is a picture in any of your posts.
Someone else will have to help with this problem...
P.S. When I get home I'll be able to see what you posted. That is if they ever let me out of this shop...
|
I used tinypic. next time, ill just upload a zip file so everyone can access it.
Quote:
Originally Posted by Joe Ross
One thing I noticed is that you're opening and closing your robot drive in teleop, plus you still have references to the default robot drive in telop. You probably have conflicts in PWM assignments doing that. You also shouldn't be opening and closing hardware like that, as telop is called 50 times per second. You should open it and save the device reference in begin. In teleop you should get the device reference and do something with it. It should be closed in finish.
|
Thats what we
had. We had all that, and the only errors we were getting from the driver station were the watchdog errors. This was good,
except that tank drive was not functioning properly(meaning each joystick controls its own jaguar which moves the motor its connected to).
I guess we are just having errors somewhere when everything is being referenced. maybe some other code is screwing around the data for the references because when we use joystick references instead of just opening joysticks on a USB port, tank drive screws up(I am sure i wrote this before, but ill do it once again. When i say tank drive screws up, i mean that in light bulb mode, the joysticks are giving the correct values[joystick 1 turns left motor, joystick 2 turns right motor]. When we run the code on the robot, Joystick 1 controls both motors and joystick 2 looses control of motor 2(it regains control for half a second randomly)
It would be really helpful if you could post or PM me some sample code(we dont have any examples installed in labview for some reason) that we could work off of.