Chief Delphi

Chief Delphi (http://www.chiefdelphi.com/forums/index.php)
-   General Forum (http://www.chiefdelphi.com/forums/forumdisplay.php?f=16)
-   -   Joystick in Autonomous (http://www.chiefdelphi.com/forums/showthread.php?t=126930)

jvriezen 20-02-2014 14:07

Joystick in Autonomous
 
Ignoring the fact that this is against the rules, if one were to program autonomous to take joystick input and the driver touched the joystick during autonomous, would the input be seen by the robot code? Or is that somehow locked out automatically?

Mark McLeod 20-02-2014 14:17

Re: Joystick in Autonomous
 
Nope.
The code only sees the last values sent in the last packet before Autonomous started.
That packet info is ignored by the communications task during Autonomous.

jvriezen 20-02-2014 14:21

Re: Joystick in Autonomous
 
Quote:

Originally Posted by Mark McLeod (Post 1346955)
Nope.
The code only sees the last values sent in the last packet before Autonomous started.
That packet info is ignored by the communications task during Autonomous.

So it behaves differently than the Kinect, which is not ignored during Auto. Ok.

Mark McLeod 20-02-2014 14:31

Re: Joystick in Autonomous
 
Yes, the Kinect gets through because it was originally setup to be used to direct the robot during Autonomous.

JohnGilb 20-02-2014 14:42

Re: Joystick in Autonomous
 
But we have the code for the communications task, right? So if you wanted to, you could let the joystick value through.

jvriezen 20-02-2014 16:17

Re: Joystick in Autonomous
 
Quote:

Originally Posted by JohnGilb (Post 1346983)
But we have the code for the communications task, right? So if you wanted to, you could let the joystick value through.

Would modifying that code in that way be permitted? (even if touching the joystick is still illegal during Auto) I don't know if that is part of the code you are not supposed to touch.

Joe Ross 20-02-2014 16:50

Re: Joystick in Autonomous
 
Quote:

Originally Posted by JohnGilb (Post 1346983)
But we have the code for the communications task, right? So if you wanted to, you could let the joystick value through.

You don't have the driver station code. I don't know enough about Windows DirectX programming to know whether you could read a joystick that is also being read by the drivers station and then send the data through an alternate communications method.

matthewdenny 21-02-2014 10:10

Re: Joystick in Autonomous
 
If joystick commands aren't sent during auto, is there a reason that the drivers have to stand back from the controls?

Mark McLeod 21-02-2014 10:12

Re: Joystick in Autonomous
 
During Autonomous commands from the Driver Station can be sent other ways than the joysticks.
So keep back :)

Then there's that Kinect thingy...

Christopher149 21-02-2014 10:26

Re: Joystick in Autonomous
 
@Mark, or anyone

If you set one of the axes before the match (say the "throttle" which doesn't have a centering spring), would autonomous be able to read that value?

geomapguy 21-02-2014 10:28

Re: Joystick in Autonomous
 
Quote:

Originally Posted by Christopher149 (Post 1347458)
@Mark, or anyone

If you set one of the axes before the match (say the "throttle" which doesn't have a centering spring), would autonomous be able to read that value?

Yes....I believe the defaults LabVIEW Auto Code already has the code needed to read it. But honestly, it's just easier to create a custom dashboard for setting certain boolean tasks for auto mode.

Jeanne Boyarsky 21-02-2014 10:28

Re: Joystick in Autonomous
 
I don't know, but I suspect there isn't code to prevent the joystick from being read. SmartDashBoard definitely is read and it seems unlikely they would introduce code to prevent other devices from being read.

You could try it as an experiment. There is a "practice" mode on the driver station that simulates a match of autonomous followed by regular. You could touch the joystick during the first 10 seconds of "practice" mode and see what happens.

If you do try it, post back here so we all know!


All times are GMT -5. The time now is 07:08.

Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi