Re: problems with using switches for autonomous
 

Are you using compatibility i/o or extended i/o?

Alan, you forgot the code fragment.

Re: problems with using switches for autonomous
 

I thought it was there when I wrote the post this morning. Here it is (again).

Re: problems with using switches for autonomous
 

We tried what you suggested. It works! Thank you for your help! We really appreciate it. :D

Re: problems with using switches for autonomous
 

We are having similar problems with getting the PSoC inputs to be seen on the Dashboard. We have placed Get Dig In on the Dashboard.vi but don't see any states change. The states do change on the Driver Station. Does anyone have any suggestions on what we should do?

Thanks!
Komal

Re: problems with using switches for autonomous
 

The Get Digital In vi only works on the robot. If you want to show its output on the Dashboard, the robot program will have to send it in the Dashboard data and the Dashboard program will have to retrieve it from there.

Re: problems with using switches for autonomous
 

we have our auton. working in the same way you guys do except on ours we have the boolean output of the "get Dig. in" block going to a block that gets the ID of the switch and goes directly into a case structure. inside the case we have different "pages" that have different auton. programs. the DIG. In is what controls the program.

Re: problems with using switches for autonomous
 

What our team did was use 2 PWMs attached to a 3-way switch mounted on the robot, and made 2 case structures, one inside the other for autonomous. We wired digital IOs into the case strucures, and that's how we get our autonomous selection.