problems with using switches for autonomous

[Alan Anderson]

Originally Posted by ssica_jj

Attached is a screen shot of our code.

You still haven't said how you are determining that the value isn't being read. Are you probing any of the wires to find out whether the data from the Driver Station digital inputs is making it out of the Get Dig In?

I don't know why you're storing a string of text "1" and "0" characters in something called "Program Num", I am having a hard time understanding why you are doing a Concatenate instead of using the Append T/F String vi to do the appending it is designed for, and I have no idea why you put a Get Dig In there three times. Can you describe what that code is supposed to be doing?

[ssica_jj]

Originally Posted by Alan Anderson

You still haven't said how you are determining that the value isn't being read. Are you probing any of the wires to find out whether the data from the Driver Station digital inputs is making it out of the Get Dig In?

When we ran the code, to check the values, we turned on the 'highlight execution' and saw that the only value being read is 0.

Originally Posted by Alan Anderson

I dont know why you're storing a string of text "1" and "0" characters in something called "Program Num", I am having a hard time understanding why you are doing a Concatenate instead of using the Append T/F String vi to do the appending it is designed for, and I have no idea why you put a Get Dig In there three times. Can you describe what that code is supposed to be doing?

There are 3 Get Dig In because we are using 3 switches. We are converting the value into string then concatenating them in order to create different combination for the case selector in autonomous. That way, we can have multiple autonomous modes and switch between them between matches without re-downloading the code each time. We are using the Append T/F String.vi to convert the digital input value into string.

[Alan Anderson]

Originally Posted by ssica_jj

When we ran the code, to check the values, we turned on the 'highlight execution' and saw that the only value being read is 0.

Try putting an indicator or a probe on the output of Get Dig In and running the code at speed.

There are 3 Get Dig In because we are using 3 switches.

Get Dig In returns all eight switches at the same time. You only need to use it once, and you can get multiple elements from its output with a single Index Array. See the attached code fragment. [edit]...which apparently didn't get attached properly, and which I do not have a copy of at the moment. I'll try to correct that later today.[/edit]

We are using the Append T/F String.vi to convert the digital input value into string.

I understand that, but you're ignoring the "Append" part of it. You can build the string as you go instead of keeping the characters separate and combining them in a separate step.

[Joe Ross]

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

Alan, you forgot the code fragment.

[Alan Anderson]

Originally Posted by Joe Ross

Alan, you forgot the code fragment.

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

[ssica_jj]

Originally Posted by Alan Anderson

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

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

[fkm300]

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

[Alan Anderson]

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.