Hello all, I am trying to have an Autonomous selector with more then just the Alt. 1 and Alt. 2 selections without having to manually type it in an risk user error at an event (Default code is an emergency zeroed out everything so as to help stop me destroying a field if I misstype my auto), but as the dashboard has no way of getting all of the strings from my auto case selector, this isn’t happening. That being said, how do I either create a list of strings that feed to the selector (Will need the code for the dashboard end as well, if you can help) or, a way to have the auto selector automatically populate with my cases (THe former obviously being the most probable, as I’m unsure if LabView has any implementation for taking the various strings as an array out of the Cases of a case selector)
In the Begin case there is the array of strings which populates the drop down list, you may add, remove, or change this array as you would like. I would suggest copying the names of your cases and pasting them into the array. (As a side note you may want to have the default be crossing the baseline for that free five points if you can manage it)
The auto selector that is in the template code was already described, but I’ll do it again just to make sure the whole thing is well understood. Then I’ll discuss variations that you may be interested in.
In Begin, the code writes to the NT variable called “Auto List”. This is an array of strings. It is written in begin and not in Auto so that it can be displayed on the DB before Auto is called.
The DB reads this variable and updates the combo box on the Drive tab. This is a combo, so the user can still type into it as well as pick from a list. That is obviously one easy change is to make it a ring and not a combo.
The default value of the combo box is set into the NT variable called “Auto Selector”. This is a string so it is meaningful to the drivers. Any change to the combo is also written to the variable.
The last step is that Auto reads this variable and wires it to a case selector to determine which diagram runs.
If you are seeing user error, I’m curious where they are generally occurring. It is string based, so there can obviously be programmer error between the Begin and Auto, and the drivers could type rather than pick from a list, but I suspect that is rare.
If you are looking for variation ideas, you use a to-lower function to get rid of case compare problems. You can do your own compare to the array of strings written in Auto to determine which to run. And I saw a post from someone the other day using an enumerated type to get rid of the strings. Each of these solutions complicates it just a bit, so I’m curious what problem you are seeing, or is this mostly cautionary coding?
Greg McKaskle