Case Structure Sub Label bug ?

Searching the forum I could not find a post related to this.
Whenever something changes in the diagram LV marks the VI as not saved (yet).
However, when the Sub diagram label of a Case Structure is changed, text and/or visibility, LV does not mark the VI as not saved.
I think this is a bug.
Kees
Solved!
Go to Solution.

CAR 438528 discussed in this thread was fixed in LabVIEW 2014. For a more complete list of bugs fixed in LabVIEW 2014, check the LabVIEW 2014 Bug Fixes. You can download an evaluation copy of LabVIEW 2014 at http://www.ni.com/trylabview/ or if you have an earlier version of LabVIEW installed and an active SSP subscription, you will be able to download the latest version of LabVIEW through NI Update Service.
Regards,
Jeff Peacock
Product Support Engineer | LabVIEW R&D | National Instruments | Certified LabVIEW Architect

Similar Messages

Problem with multiple sub-panels through Enum case structure: "The VI is not in a state compatible with this operation"

Hello,
I am using LabVIEW 8.0 and I am attempting to create a sub-panel that displays the front panel of a sub-vi depending on the selection made by the user via the Enum dropdown menu. I have wired the Enum to a case structure and applied identical coding to each individual case structure except for obviously changing the sub-vi source. However, I receive an error "The VI is not in a state compatible with this operation." I was able to successfully make a single sub-vi work within a sub-panel using a true/false case structure and the exact same coding. However, now that I am using an Enum box wired to a case structure, I receive this error. I have attached my block diagram as well. Could anyone assist me as to where it is that I am going wrong?
Thanks in advance!
Solved!
Go to Solution.
Attachments:
enum subpanels.JPG ‏22 KB

torm wrote:
I have attached my block diagram as well
I only see a picture. Can you attach the VI instead? At what point do you close the reference?
torm wrote:
I have wired the Enum to a case structure and applied identical coding to each individual case structure except for obviously changing the sub-vi source.
Well, if the code is identical except for the source, only the source should be inside the case, right? Why duplicate code?
LabVIEW Champion . Do more with less code and in less time .

Editor bug if you drag a case structure over an index/replace elements node on a in place structure

To reproduce:
Drag a case structure over a index/replace array node
You'll end up with this train wreck. Autocleanup no longer works
Interestingly, you can still get it to compile but setting the boolean to true doesn't run the true case. Warning: dragging the below snippet onto your block diagram will probably crash LabVIEW
Select all that and drag it into a new VI. Run autocleanup and the development environment will crash: Exception: Noncontinuable exception (0xC0000025) at EIP=0x00000000
Running LabVIEW 2014 SP1 with nothing special.

To quote Obi-Wan
This is not the bug you are looking for..........
Now search for "Clear as mud"
Having a Wired treminal inside an IPE driving conditional code should break the snot out of that code and cause the compiler to puke all over! The lack of check for that insanity is causing the crash! Don't do it! Just think of how you are abusing the poor IPE. What if you had a breakpoint on the Inplace Boundary and changed the boolean? That would necessatate a copy inside an inplace structure....... NO!!!!
Or, more to the point as best I understand: (Add duct tape adound head as needed)
An IPE must exist in one "Clump" Terminal Reads exisist in their own "Clump" (although you can read many terminals in one clump) So you require a clump to read the boolean terminal inside another clump. Clumps cannot reside in clumps since clumps are clumps that stand apart from each other by definition. The run arrow should be broken but is not- hence LabVIEW crashes. Makes sence to me except the clumping algorythm didn't catch the insanity and the run arrow wasn't broken. so the next edit caused all hell to break loose.
(If I missed domething here I am going to learn something today)
Jeff

Can I use a formula node to start the execution of a case structure?

Hi,
I am working on editing a VI to make it much easier to understand (for colleagues and non LV users). For one reason or another, the VI's creators did not fully make use of the power of case structures and other structure types. In the application we need it for, the instrument cycles and repeats measurements on several objects. We are interested in measuring the motor currents for several motors in the system. As it stands now, for each sample object's run, there is a separate sub-vi diagram which displays its waveform trace and several indicators such as max current, time at max, etc. That code was contained within a T/F case structure and copied and pasted 20 plus times.... Obviously the vi became extrememly cluttered and needed a huge screen to see. The trigger for the current case structures is an EQUALS comparison between one input (which is the sample object counter; and this part I will likely leave unchanged since it makes a lot of sense already) and a constant which was defined 1 through 20+ for case.
I have since made one case structure and 20+ instances of that case and have labeled them (at the top selection box near the detent arrows) "1", "2", 3, etc. I am wondering if I can use a formula node to act as the "trigger" which sets each case structure running? I believe that a simple IF statement should work. Please see a snippet of my attempt at making this in C below.
For the node, I defined X as the input and Y as the output. The input to the node, X, is connected to the sample object counter. The output, Y, is connected to the case selector of the case structure. My attempt at the code is below:
int32 y
For(x == 1)
y = "1";
For(x == 2)
y = "2";
etc, etc.
Is that above code snippet correct? Do i need something like "ENDIF" or "end if" at the end? Does "y" have to be defined as "int32" or can it be something else?
Thanks for the help!

Is your formula node doing anything else besides what is shown?
Why don't you just wire the value that is going into it at X directly into the selector of the case structure?
Attachments:
Example_VI_BD.png ‏2 KB

How can I have multiple inputs into the selector terminal of a case structure

Hi everyone
I have a question on how to wire multiple inputs in to the selector terminal of a case structure.
Currently, I have three switches, each switch determines different case. So if I switch the switch 1 is on, the numeric indicator will show 1. If the switch 2 is on, the numeric indicator will show 2, so on and so forth. However, the selector terminal will not allow me to wire multiply inputs into the case structure, I tried Bundle by Name, Bundle and Array to Cluster, but they did not work. I set the case structure with 3 cases, they are 1, 2 and 3.
Could someone help me please. I have attach an image and the VI of the work I did so far.
I have another question, is there a function which can toggle other switches to off when there is a switch has been toggled on.
Thank you very much
Tommy
Attachments:
Trial - Case Structure.vi ‏7 KB

Tommy, attached find a cheeseball way of doing this that has given me a LOT of mileage over the years. IT lends itself nicely to a couple of really good practices that NI recommend, but I have given you the bare-bones to "see under the hood".
The recommended practices:
1. You can make this a nice tight sub-vi where you can put it into a core library of routines that you'll use over the years, even extending the logic to look only for changes, etc.
2. If you are thinking about Front Panel design considerations, you'll want to use arrays of controls where possible, as that's a nice neat way of containerizing your switch for both the FP and Block Diagram.
Have fun. I have TONS of these types of things, so feel free to PM me if you have any other needs.
Wes
Wes Ramm, Cyth UK
CLD, CPLI
Attachments:
Boolean Switch Logic.vi ‏11 KB

How can I append some data to an array via a case structure?

Basically i want to do the following thing:
do
if control=0
else
Data=Data append data1
end if
}while(run=1)
We try to avoid local variable since the size of Data is pretty big. I am pretty sure i can add a shift register in a loop structure.But is it possible to add a shift register in a case structure?
Thank you!

The best you will be able to do is going to be a variation on what CC suggested regarding replacing array sub-sets.
If you do not know how big it will end up then over-allocate but still use the replace array subset.
The delays you are seeing are due to the memory buffers groing and additional memory need allocated as the array grows. The Replace array subset function operates inplace and re-uses the buffer it is passed. There is no clear KB regarding which array operations operate inplace and which do not.
http://forums.ni.com/ni/board/message?board.id=170&message.id=74847&requireLogin=False
Under Tools >>> Advanced >>> Show buffer allocations will show you where buffers are being allocated (LV 7.1).
If you post a zip or llb of you code I am sure someone will have more to add.
Ben
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction

Case Structure timing/ writing data to a excel

Hi all,
I have written a program that has the main functions of allowing the user to generate a random number between either 0-10 or 5-15 by using the labelled switch. I also have a control which can switch this function on or off. When this switch is true it will display the random number and also write this number to an excel spreadsheet every 1 second (I hope). When false this will stop displaying the number and hence not write the number to a file.
However, I am having the following issues:
1. Excel file is corrupt once I begin to write the generated numbers to the spreadsheet. (I am trying to write to a .xlsx file)
2. Once I begin to try write the numbers to file, the elapsed timer only displays the time is 1second intervals rather than the full time.
I changed the .xlsx file to a .csv file and this solved issue 1. but it only recorded one random number rather than the numbers that were generated in that time since switched on/off.
Should I have the write to spreadsheet function in the timed case structure?
Should the file path control be outside this case structure?
Have I set up the write to spreadsheet VI correctly?
If anyone could help with these issues that would be a big help.
Thanks!
Attachments:
Random Number tester.vi ‏30 KB

lneill65 wrote:
There is still an issue with the elapsed time. Once I begin I turn the top boolean control to true, the elapsed time begins changing at the set time increment inside the case structure. Is there anyway to stop this from happening?
Your elapsed time display is independent of the boolean switches because it is on the toplevel loop diagram. I am not sure why you place a five second wait inside the case structure if you want to write once per second.
I am not sure why you have two sequential case structures since the calculations of the first structure is not needed unless the other case is also true. Why not place it inside the true case?
You should also adhere to some basic coding styles. Avoid overlapping and floating objects, hidden wires, right-to-left wiring.
If it is sufficient if the code reacts once per second, just run the loop with a 1 second wait. If you don't want to display a stale random number if the switch is off, place the indicator after the case structure.
Here's a quick draft. Modify as needed. I probably would use an event structure, but let's keep it simple at this stage. You should also modify it so it does not try to write with an illegal path and also retain the selected path once selected. I propably would use a file dialog instead of a FP Path control.
LabVIEW Champion . Do more with less code and in less time .
Attachments:
Random Number testerMOD.vi ‏9 KB

Please Clarify the Errors (Case Structure)

I am using numeric case structure but I don't understand the errors, can anyone clarify what they are mean and what I have to do to change it. Thank you in advance.

(This is a new problem, so you should have started a new thread.)
The solution is simple: Things are case sensitive!
A case labeled "Divide" is different to a case "divide"! Correct the first characer for each case and you're all set.
In scenarios such as this, easiest is to hook up an empty case structure to the radio control, then right-click the case structure and select "Add case for every value". Voila! No chance for mispellings!
Message Edited by altenbach on 08-07-2006 09:49 AM
LabVIEW Champion . Do more with less code and in less time .

CASE STRUCTURES WITH TAB CONTROL

Hi,
I have created tab controlled case structures for three different cases,
Tablet type
Machine Input
Output
It seems that data is not interlinked while switching betweeen the cases.
I have to select the start buttun for each tab to get results.And also if I skip the second tab and jump to third tab, it doesnot give results. SOmehow the data is not acquired.
Can anyone help me out for the same.
Attached is the main VI (PAR_LAB_ATT_00_01)followed by a sub VI(gen time array)
Thanks
Sumit
Attachments:
PAR_LAB_ATT_00_01.vi ‏200 KB
Generate Time Array.vi ‏15 KB

Please don't use all CAPS when posting your message subject.
How are you running your VI? I don't see any while loop in it, so it only runs once. Which means only the case structure associated with the tab that is currently highlighted before you press the run button will actually run.
The vast majority of the time, a tab control is only used to control what is displayed in the front panel and is not used to actually control the execution order of the program.
I would recommend looking at the online LabVIEW tutorials
LabVIEW Introduction Course - Three Hours
LabVIEW Introduction Course - Six Hours

Case structure not going through all cases before restarting

I have a case structure and it is not going throught the entire list of cases, I cannot figure out the problem. Any help would be greatly appreciated. I have attached my VI:
Attachments:
42sampleWorkingCodeNI.vi ‏974 KB

In your case labeled "exhauset 24", you reset the state back to "valve 2 open".
Your program is way (way!!) too convoluted to do any serious code maintenance. Properly written, the same functionality can be achieved wich much less code. 90% of your code is duplicate. Why don't you use arrays?
LabVIEW Champion . Do more with less code and in less time .

Case Structure - multiple selectors, single exit

I tried searching for an anwser to my question but I could not find one.
I'm creating an interface for my graduation project (using LabVIEW 7.1) and I will be using several subpanel's, at this point I'm trying to create a selection method. During the design of the interface the users gave preference to buttons for switching between the different subpanels (there is a total of 4 buttons). And a subpanel is chosen based on a numeric value (I have taken the code from the viewer.vi example).
Now I'm trying to work out some sort of case structure starting from the 4 buttons and resulting in a single numeric value. The idea being that when button 1 is pressed, subpanel 1 is active and every other panel is not. So far I haven't found a working one, especially because of the single numeric value I want to have.
If the anwser is somewhere on this board then you have my apologies and I would appreciate a link to it.
If something is not clear: feel free to ask questions.

That's why a radio button control is better. It automatically allows only one button to be active. Clicking a new one will turn the others off.
Try it! Just place any number of booleans (any style) inside the radio button control. The output will be a single number. If you wire it to a case structure, you'll get the control label for each as case name.
(you can also allow or disallow "no selection", etc.)
LabVIEW Champion . Do more with less code and in less time .
Attachments:
RadioButtons.vi ‏10 KB

Case structure & event structure

1.What are the disadvantages of case strucure?
2.What are the advantages of event structure?

Are these test questions? I could name 10 for each, but why are you asking?
While there are often many ways to accomplish the same thing, Case structures and Event structures serve different purposes. Straight from the Help file:
Case Structure
Has one or more subdiagrams, or cases, exactly one of which
executes when the structure executes. The value wired to the selector terminal
determines which case to execute and can be Boolean, string, integer, or
enumerated type. Right-click the structure border to add or delete cases. Use
the Labeling tool to enter value(s) in the case selector label and configure the
value(s) handled by each case.
Event Structure (Not in Base Package)
Has one or more
subdiagrams, or event cases, exactly one of which executes when the structure
executes. The Event structure waits until an event happens, then executes the
appropriate case to handle that event.
Right-click the structure border to add new event cases and configure which
events to handle. Wire a value to the Timeout
terminal at the top left of the Event structure to specify the number of
milliseconds the Event structure should wait for an event to occur. The default
is –1, indicating never to time out.

Is it possible to add enable control to a case structure.

i have to find add/subtract the data only if need it.Not all the time when the vi runs. I have added the difft operations-add,sub.div and mul in a case struct and executed it.But this part of the prg is running all the time when the prg is running. Can i give a control or enable option to the case structure ? I have tried to write this part as a subvi.But again i dont want to run this always.

In subvi choose the above options and run the attached vi.
Attachments:
Mainvi.vi ‏10 KB
arithmetic case.vi ‏236 KB

Why does Labview insert quotations in the case structure selector box?

I was building a case structure with an array of strings. So, I copied the strings from the array on the FRONT PANEL directly into the SELECTOR LABEL. My 3 strings have the form; to me, these are 5- character strings with spaces, or 7 characters if you count the spaces as string characters
A, B, C
A, B, D
A, B, E
So, when I copied and pasted them directly into the selector box A, B, C appeared as "A", "B", "C" and A, B, D appeared as "A", "B", "C" and then I got an error for selector values not unique. Why didn't it appear as "A, B, C"?
Why did it transform the string I pasted and insert the quotation marks? I used no quotation marks in my array. Does the selector label interpret commas as functional characters that require quotation marks??
Thanks,
Dave

dav2010 wrote:
I was building a case structure with an array of strings. So, I copied the strings from the array on the FRONT PANEL directly into the SELECTOR LABEL. My 3 strings have the form; to me, these are 5- character strings with spaces, or 7 characters if you count the spaces as string characters
A, B, C
A, B, D
A, B, E
So, when I copied and pasted them directly into the selector box A, B, C appeared as "A", "B", "C" and A, B, D appeared as "A", "B", "C" and then I got an error for selector values not unique. Why didn't it appear as "A, B, C"?
Why did it transform the string I pasted and insert the quotation marks? I used no quotation marks in my array. Does the selector label interpret commas as functional characters that require quotation marks??
Thanks,
Dave
Actually in CASE STRUCTURE, any frame can have multiple values as 'Case Selector value' and these are separated by a comma. Also if you choose to operate a CASE STRUCTURE using string, it will automatically prefixs & suffixs quotes (") to that string.
But you can enter "A, B, C" manually and it will remain as it is. But if you copy and paste A, B, C, the CASE STRUCTURE will automatically change it to "A", "B", "C".
I am not allergic to Kudos, in fact I love Kudos.
Make your LabVIEW experience more CONVENIENT.

Case structure no false output

Hey guys,
To start off, I am very new at Labview. I have posted about this project before but my professor has changed the assignment slightly.
- Generate a random set of N points (x,y) between 0 and 100
- Find the closest point to each point
- Calculate the number of points with a closest point of less than D
- Graph the points with the points with a closest point of less than D clearly marked
So far I have manged to get everything done except for the last part, at least completley. My approach was to create a case structure with < D as the requirement, if true build array if false I wanted it to do nothing, but I can't seem to do that. I tried using a number ourside of the array size but that doesn't seem to work either. Then I tried using a a shift register to do the same thing but had the same problem. I could use some help if at all possible. I have posted both codes below. 1_9 is the case structure alone and 1_10 is the shift register approach.
Attachments:
Assignment 1_10.vi ‏27 KB
Assignment 1_9.vi ‏31 KB

Not bad- monor tweaks set off with some color attached.
NOTE use BD comments. Watch your data types (point closest should be an Integer type not a double) use increment rather than adding 1. kill the iteration indicators you are outo indexing off of an array generated with the Number of Points(N) control- there is no need to write N number of times to each indicator. why you CHOSE to cross the wires into and out of the fourth loop baffles the mind
EDIT: the SR should be initialized with an EMPTY array I just noticed that it has 1 element. that is a bug
Jeff
Attachments:
Assignment 1_10_MOD.vi ‏26 KB

Case Structure Sub Label bug ?

Similar Messages

Maybe you are looking for