So i have another problem >.<

[Joe Ross]

One thing to keep in mind is that telop.vi is called 50 times a second by robot main. Thus, 50 times a second you are opening robot drive. If it works at all, I'd expect a lot of error messages in the diagnostics window of the driver station.

If Robot Drive VIs are only going to be used in telop, you could open robot drive in the init case of telop.vi and use feedback to save the device reference. However, this becomes cumbersome if you have a lot of devices, or if you want to access them other places (such as autonomous).

The better thing to do is put your open in begin.vi, and then set the device reference. In telop.vi, you can get the device reference and then use it.

[Green2]

I am going to guess that the enums for the joystick are both on USB 1 (can't tell from the posted pictures). Make make sure they are pointing to the proper USB ports...

[JohnFogarty]

they are on USB 1 and USB 2 still only one of them works, i tried the + wheel - and it did nothing, i tried changing the axis in the code...nothing changed, and i reversed the motor inverses and...still nothing

[Mark McLeod]

You might try downloading code that has no joysticks just to be sure you aren't executing old code for some reason.

[JohnFogarty]

Ok, i'll try that. Does anyone have a Tank Drive program i could use?

[jhersh]

Try changing the controls for selecting the PWM channels and the USB channels to constants. That way we don't need to worry about them getting reset to default values.

[Tanner]

From my experience, Joe's answer explains the problem. Otherwise, I don't see anything else that is wrong.

Originally Posted by Joe Ross

One thing to keep in mind is that telop.vi is called 50 times a second by robot main. Thus, 50 times a second you are opening robot drive. If it works at all, I'd expect a lot of error messages in the diagnostics window of the driver station.

If Robot Drive VIs are only going to be used in telop, you could open robot drive in the init case of telop.vi and use feedback to save the device reference. However, this becomes cumbersome if you have a lot of devices, or if you want to access them other places (such as autonomous).

The better thing to do is put your open in begin.vi, and then set the device reference. In telop.vi, you can get the device reference and then use it.

You could open all your motors/joysticks in Teleop.vi, but it gets complicated in just setting that up.

-Tanner

[JohnFogarty]

I put that into my code last night, i'm going to try it today. It seemed the 2nd joystick was not in the Begin.vi that might have been the problem. and i set the open jaguar reference in the begin.vi as well.

[Matt95]

Originally Posted by Tanner

From my experience, Joe's answer explains the problem. Otherwise, I don't see anything else that is wrong.



You could open all your motors/joysticks in Teleop.vi, but it gets complicated in just setting that up.

-Tanner

While Im not exactly sure about your problem, but i recommend removing all connection with the right control and seeing if the left motor works (by doing what it originally was suspost to do.) if the left control still isn't working, then the left control probably has a malfunction of some sort. In that case, you should get a new left control.

[JohnFogarty]

ok so i've definatly got a problem, i took the right motor out of the code and set it to the y axis of joystick 1. AND it's doing the same thing and it's running both motors, i tried Joe's idea NOTHING IS WORKING. O.o ....

[TheOtherGuy]

Could you explain in detail how you are deploying the program?

[bladetech932]

I would try separating out those constants on the axis it shouldn't change anything i know but thats what caused ours to do that.

[jhersh]

Have you looked at the Diagnostics tab of the driver station? There is a window that will show all your errors there. Please tell us what errors you see. It's best to clear the error list, then run it, so you can get a clear picture of what errors happen in a single run.

[JohnFogarty]

I had so many errors it wasn't funny when i replaced Arcade Drive with tank drive. I tried Arcade and it still screwed up but the errors were gone. What i do is start a new Robot Project I build it and set it as the startup. I edited the tele-op File to use jostick, watchdog and Open motor references from the begin.vi, I changed the Arcade drive to Tank Drive and i set the 2 get axis's to Axis 2 and axis 5 because i'm using the Daul Action Gamepad. then i took axis 5 off and so nothing was to supposed to run the right motor. When i ran the program to see if the left motor worked on the left stick. Both motors ran they were not supposed to, when i took axis 2 off and tried axis 5 right y axis stick nothing happened. To run my code i save my teleop changes and Deploy it from the boot time thing at the bottom by right clicking and selecting deploy (I DO GET A MESSAGE BOX SAYING THAT CERTAIN VI's are real time vi's and that if i choose to continue all vi's on the device will close the vi's it lists are mostly camera realted though it sometimes shows the main vi as well). then i reboot and open the drivers station.

[TheOtherGuy]

Originally Posted by John_1102

I had so many errors it wasn't funny when i replaced Arcade Drive with tank drive. I tried Arcade and it still screwed up but the errors were gone. What i do is start a new Robot Project I build it and set it as the startup. I edited the tele-op File to use jostick, watchdog and Open motor references from the begin.vi, I changed the Arcade drive to Tank Drive and i set the 2 get axis's to Axis 2 and axis 5 because i'm using the Daul Action Gamepad. then i took axis 5 off and so nothing was to supposed to run the right motor. When i ran the program to see if the left motor worked on the left stick. Both motors ran they were not supposed to, when i took axis 2 off and tried axis 5 right y axis stick nothing happened. To run my code i save my teleop changes and Deploy it from the boot time thing at the bottom by right clicking and selecting deploy (I DO GET A MESSAGE BOX SAYING THAT CERTAIN VI's are real time vi's and that if i choose to continue all vi's on the device will close the vi's it lists are mostly camera realted though it sometimes shows the main vi as well). then i reboot and open the drivers station.

So you select deploy rather than 'Run as Startup' and then reboot the cRio once it's finished downloading? When you deploy, it just loads and runs your program on the cRio while the LabVIEW program is running, and if you turn off the cRio it will lose that code. The last program set as startup will then load when you reboot. Seems like you're loading the same arcade drive program each time you turn it off and back on. Right click on Build Dependencies in the project tree and select Build, then Run as Startup once that's done. Then you should be able to reboot without losing the program.