08-27-2008 01:49 PM
The maximum number I use in my code is 1. The usual number is 0. It is used to force data dependency.
The one exception is when I running a timing test on pieces of code to see which is faster. Those programs use flat sequences with n+2 frames where n is the number of pieces of test code.
Lynn
08-27-2008 05:49 PM
tst,
Please tell me you made this VI using scripting, and not by manually adding 10000 cases!
If you did the former, did you try and see how many you could add before LV gave up completely?
As a glutton for punishment I tried clicking on the case structure, it listed all the cases nearly instantaneously on my PC, so then I decided to convert it to a flat sequence and that did the trick: LabVIEW thought for a while then just terminated
08-28-2008 02:19 AM
nrp wrote:
Please tell me you made this VI using scripting, and not by manually adding 10000 cases!
What's "scripting"?
Adding it is simple - you just add a few cases every hour during breaks and in a few months you have your structure. 😄
I initially let it run to ~20,000 but then tried to look at it and crashed LV (hence the warning). The property itself is an I32, so it should be able to get to ~2 billion frames, but there are probably other limitations which will prevent you from getting that high.
08-28-2008 02:52 AM
I tried to get that many cases with LV 7.1.
Having accomplished to create a enum with 10000 enties (named from 0 to 9999 so I'm sure I don't miss one). I wired the enum to a case structure and tried 'add case for every value'.
All I got was one new case with the name "".
Are state machines limited to <10000 states in LV 7.1.?
Felix
08-28-2008 03:29 AM
tst wrote:
Will 10,000 frames be enough for what you want?
10000 stars for making 10000 sequences, tst!
BTW, how did you make it, scripting... ?!
08-28-2008 05:33 AM
nrp wrote:tst,
..., so then I decided to convert it to a flat sequence and that did the trick: LabVIEW thought for a while then just terminated
I think I read that the LV block diagram is limited to about 65,000 pixels wide. If the stacked seq was wider than 65 pixels (about two sub-VIs in width) then the conversion would have run into the diagram size limit.
Ben
08-28-2008 07:41 AM
Scripting is where you train a monkey to use a mouse and repeatedly do right click-->add case after
These modern monkeys are really smart, after only a few bananas they get the idea and can produce some LabVIEW. Trouble is when senior management gets wind of these code writing monkeys they try and steal them away from me to produce test applications!
08-28-2008 08:21 AM
Hey,
@Ben: I think the limit of the block diagram width is 65.498 pixels. However if you test it with a flat sequence it becomes invisible over a width of 32600 pixels (LV8.2.1)
Christian
08-28-2008 09:59 AM
08-28-2008 12:40 PM
nrp wrote:Scripting is where you train a monkey to use a mouse and repeatedly do right click-->add case after
These modern monkeys are really smart, after only a few bananas they get the idea and can produce some LabVIEW. Trouble is when senior management gets wind of these code writing monkeys they try and steal them away from me to produce test applications!
![]()
Yair helped me find this thread on LAVA
Ben