[TotalChaos]

Ok,

So I finally got a chance to test out the Spikes on our practice base and here's what I've found.

In this other thread I first said you could wire a numerical constant as the input for the Set VI. Then I read that it needed an Enum constant. It turns out I was half right both times.

The input to the Set VI accepts two types of data, numerical constants and enum constants. If you right click on the input node and select Create > Constant it gives you an enum constant (the drop down menu thingy) that has 4 choices: Off, On, Forward and Reverse. My best guess for Off and On is that Off means it's completely off and that On means the brakes are applied. (Though this could be reversed) Forward and Backwards are self explanatory. Now if you're going to use an enum constant inside of a case statement I found out one crucial thing that I didn't know about before. If you make the enum constant from scratch it seems that you have to add all the possible selections and set it to the one you want. (To add options you can right click the enum constant and select "Add item before" or "Add item after") They may also have to be in the correct order. (I didn't test this but the order would be Off, On, Forward, Reverse from top to bottom).

As it turns out, you can also just use numerical constants for inputs as well. They match up pretty simply:
0 - "Off"
1 - "On"
2 - "Forward"
3 - "Reverse"
So if you hooked up a value of 2 to the input it would be the same as hooking up an enum constant with "Forward" Selected.

I hope this clears things up a bit more. If you have any more questions or something I said didn't make sense just let me know!

- Austin