Timed sequence with individual​ity for case structures

Hello All
The attached vi is one that I found by trolling on the forum, and made some slight modifications to it.
If you look at the BD, you can see that the timing between the action of each case structure is the same.
I would like to modify it even further and have each case structure have its' own individual time control.
I can do this by using a sequence and place a wait in each frame.
Would this method be both suitable and the simplest ( I have been giving some thought to using one case structure, but this solution eludes me at the moment)
Regards
Ray
Attachments:
TabAutoScroll.vi ‏16 KB

Single case, single property node, single wait.
Attachments:
TabAutoScroll_mod.vi ‏9 KB

Similar Messages

  • Property node for case structure

    Is there any way to programatically pull out the list of cases (strings) from a case structure at run time?

    Thank you tbob and tst.  I do use the enum "trick" in other places (I once saw it used in an example somewhere) and I am nervous about the Selector Strings property available through scripting after reading about it on the LAVA forums site (I am a novice LabView user and I mostly didn't know what they were talking about).
    I have a VI that processes "tags" embedded in various text fields that many of my collegues use.  As an example we have a custom front end to the LabView simple error handler that processes our custom error codes and handles timed popups, writing to the device error log, etc.  The default behavior can be modified by inserting tags (<popup 60> for a dialog box with a 60 second timeout or <no device log> to supress writing an entry to our device error log) into the "source" string of a standard error cluster -- just like the <append> tag used by the Simple Error Handler.
    In most instances there are only a few tags so I just use a case structure in the "tag processing VI" to select the desired action indicated by each tag.  When people are parsing their strings for tags, they like to have a qick and easy way to test if a string is a vaild tag.  I provide a separate "validator VI" to do this.  I frequently add and remove tags from the case structure as things evolve, but I often forget to update the list of valid tags used by the validator VI or some one runs into an older version on another machine.  I wanted to have the vaildator VI access the case structure on the tag processing VI to get the current list of vaild tags.

  • Shortcuts for case structure manipulation?

    Hello all.  I'm curious if there are keyboard shortcuts for duplicating cases or deleting cases in a case structure.  I'm also interested if any of you have any tips or secrets to working with large case structures - LabVIEW mods that enable a storyboard-style case structure reorganizer, for example.
    Thanks!

    JLS wrote:
    Another useful feature of case structures is that if you use an enumerated type for the selector, you have the option to "Add Case for Every Value.
    Yes that is handy for enums with a handful of values.
    The other feature I like about enumerated cases is the ability to NOT have a default case.
    When this is the situation, LV will remind me that I have not coded up all of the cases in the event I missed one.
    This is very handy in applications where you have a bunch ( 100 or more) of enum values.
    If at a later date I decide that I need to add enum value #101 then I edit the typedef and then LV reminds of all the places I have to go and fix.
    Just a different approach for a different challenge.
    Ben
    That reminds of a related trick I have not heard anyone mention lately.
    Bonus Q:
    Given a list of all of the enum states (array of strings), what is the easiest way to create an enum with all of those values?
    Correct answers are worth 5-stars!
    Ben Rayner
    I am currently active on.. MainStream Preppers
    Rayner's Ridge is under construction

  • Wiring inputs n outputs for case structure

    Hi everyone...
    I have a simple basic question...How to wired the correct tunnel for output in case structure.Because when I try to wire the build array to the case structure, It shown as white terminal....How how to make solid color terminal for output tunnel...Actually I forgot how to wire it correctly..so...I hope u guys can remind me again...thank u very much...
    Attachments:
    Cepat21.vi ‏43 KB

    Hi Altenbach...
    Thank u very much for ur
    help.I'm always make a careless mistake.thanks to u guys.Now,I'm be able to display my
    data into table something like attachment below.Actually I'm using IIOA
    to parse the value into string...something like that...
    V = 238.25 I = 23.82 P = 5676.12
    V = 237.79 I = 23.78 P = 5654.28
    V = 237.35 I = 23.74 P = 5633.54
    V = 236.94 I = 23.69 P = 5614.09
    V = 236.56 I = 23.66 P = 5596.12
    V = 236.22 I = 23.62 P = 5579.80
    V = 235.91 I = 23.59 P = 5565.29
    V = 235.64 I = 23.56 P = 5552.72
    V = 235.42 I = 23.54 P = 5542.22
    V = 235.24 I = 23.52 P = 5533.88
    V = 235.11 I = 23.51 P = 5527.78
    V = 235.03 I = 23.50 P = 5523.98
    V = 235.00 I = 23.50 P = 5522.52
    V = 235.02 I = 23.50 P = 5523.40
    V = 235.09 I = 23.51 P = 5526.62
    V = 235.21 I = 23.52 P = 5532.16
    V = 235.37 I = 23.54 P = 5539.95
    V = 235.58 I = 23.56 P = 5549.92
    V = 235.84 I = 23.58 P = 5561.99
    Then I try to convert this string into numeric or dbl coz I want to
    merge it with signal.So, it looks like complicated like u imagine.
    Now,I have one other question.refer to my vi, I have used elapsed time
    so that it will run from the start time until target time.But its only
    can be determined in seconds.So, how can I modify it with using elapsed
    time for day.I mean this prog will start on Monday for example n stop
    at wednesday.It means it will run for 3 days...thank u very much...
    Attachments:
    build table1.PNG ‏36 KB
    Cepat2122.vi ‏165 KB

  • How can i use a string as a control for case structure?

    my vi is reading data. the output is a string,how can a string can control the case structure? because the there's a constructed vi in that case structure that wll perform a tast after the main vi read.
    Thank You
    (Can you please give me a simple example how can do this)

    Try this vi. You shouldn't have any problems just connecting a string to the case selector.
    BJD1613
    Lead Test Tools Development Engineer
    Philips Respironics
    Certified LV Architect / Instructor
    Attachments:
    string_to_control_case_structure.vi ‏10 KB

  • Fill internal table with mutliple entries for nested structure

    Dear ABAP Experts,
    I have a question related to fill internal tables with nested structures.
    I have a structure like this:
    BEGIN OF proto,
              sicht TYPE ysicht,
              version TYPE FAGLFLEXA-RVERS,
              BEGIN OF kons,
    kon TYPE YKONSEINHEIT,
              END OF kons,
              jahr TYPE CHAR04,
    END OF proto.
    Now I need to fill this structure with values (over an internal table), but how can I achieve that I save multiple datas für element "kon" für one single entry of structure "proto"?
    An example could be:
    sicht = '01'
    version = '100'
    kon = 1001 (first entry)
    kon = 1002 (second entry)
    usw... (n entry)
    jahr = '2008'
    Thanks in advance for every helpful answer.
    Regards
    Thomas

    BEGIN OF proto,
               sicht TYPE ysicht,
               version TYPE FAGLFLEXA-RVERS,
               kons TYPE STANDARD TABLE OF YKONSEINHEIT WITH NON-UNIQUE KEY TABLE_LINE,
               jahr TYPE CHAR04,
    END OF proto.
    DATA: ls_proto TYPE proto,
          lt_proto TYPE STANDARD TABLE OF proto,
          ls_kon
    ls_proto-sicht = '01'.
    ls_proto-version = '100'
    INSERT '1001' INTO TABLE ls_proto-kons.
    INSERT '1002' INTO TABLE ls_proto-kons.
    ls_proto-jahr = '2008'.
    INSERT ls_proto INTO TABLE lt_proto
    If you're going to use a more complicated inner table with several components, then you need to define a type for those components. 
    matt

  • 720 480 sequence with square pixels for web delivery only

    i'm on fcp 5.0.4. i've done some text qt exports and all seems to be fine, just want to double-check here. i am editing a sequence of stills. i want my seq settings to be 720x480 square pixels (you can choose 'custom' for this but it will change back to ntsc dv 3:2) because i like the 1.5 (720x480) pixel aspect ratio.
    usually when i do 720x480 projects i'm working with dv/non-square footage and when i export for web use i'll choose the 640x480 setting so that it displays correctly on computers.
    so the question is: any foreseeable trouble with my using 720x480 with square pixels seq settings if i want to export a qt at those same specs, and it's NOT going to broadcast, just web delivery?
    i'm also using compressor - jpeg as part of seq settings unless someone can tell me there's a better compressor to use. (yes i know tiffs would be better but am using jpegs here.)
    thanks.

    Yes, there are foreseeable problems of applications assuming that your 720x480 video should have D1-sized pixels, as you've already experienced.
    But once you finally end up with a 720x480 square pixel QuickTime movie that you are going to embed into a web page it should play properly.
    Just make sure you host the video yourself so you can control its presentation. I bet if you upload it to Vimeo or YouTube those services would also reasonably assume that your video had non-square pixels.

  • How to implement Case Structure for multiple inputs to Pic Ring?

    So I have a reasonably simple program which I am almost completeed with. Basically the data of an array is read and then is indexed and a new array is created from the indexed data. And then I use Match Pattern to see if elements in the new array match certain words. And if they do then a number value is allocated to a Pic Ring at the end. And depending on the final number value the Pic Ring changes from one pic to another.
    However, I have the problem that I will be using multiple Match Pattern functions to compare elements in the final array, but I can't attach multiple Match Patterns and their subsequent logic statements to a single Pic Ring, only one. I've been trying to work this out by implementing a Case Structure or Event Structure. But the Event Structure isn't working and with the Case Structure, it is very messy with multiple True/False Case Structures inside of each other. Anyway, hopefully this all makes some sense. I'm attaching the VI program to this post. Thanks.
    Attachments:
    ArrayTest2.vi ‏495 KB
    ArrayTest2.vi ‏495 KB

    Obviously, you can only display one picture.  So then the question becomes which picture to show.  Therefore, you will have to create some sort of preference of one pattern over another.
    I would use a FOR loop so that you can loop through your available patters and their possible results.  Use the Conditional Terminal on the FOR loop so that you can stop the loop on the first match.  Then you just wire up the selected value for the ring outside of the loop.
    There are only two ways to tell somebody thanks: Kudos and Marked Solutions
    Unofficial Forum Rules and Guidelines

  • Combine 4 stops for 4 case structure

    Hello everyone!!
    I meet a problem in my project, I knwo it's not difficult but we are all beginners for labview.
    We need to control 4 batteries, each battery needs a life cycle calculator. I try to connect 4 life cycle calculator(case structure) in my while loop, but there are 4 stops for 4 case structure and 1 stop button for the whole while loop....I don't know how to handle with these four extra case structure stop buttons....
    As the battery charging and discharging, the life cycle part keep working so actually it's no need for stop button for each case structure , can we just get rid off the stop button for each case structure?? Is there any problem with the life cycle calculator if we do not use the stop button???
    Really Thank you for help !!!!
    here I attach our vi, you can configure it directly !!
    Attachments:
    PR2.vi ‏78 KB

    The main problem is code architecture. Once you fix this, your current problem will vanish automatically.
    You seem to be spending way too much time rewriting basically the same code over and over. You need to modularize the code and make it scalable. You have four instances of basically the same code. Are you planning to later scale this up for a few hiundred batteries? Would you then simply make it a diagram that is millions of pixels hight? Once you combine all the functionality for one battery into scalable code, you can scale it up for an arbitrary number of instances.
    Same for the front panel. Make the controls for one battery into a cluster and then make a 2D array of such cluster (2x2 in your case). Suddenly, the entire code will be the size of a postage stamp and easy to maintain. If you currently want to change an error in the algorithm, you need to make identical changes in four different places. If you forget one place, bugs will be very had to find.
    LabVIEW Champion . Do more with less code and in less time .

  • Event structure vs case structure?

    I am developing an application that is fairly user input based... lots of boolean control buttons to do different things.
    In the past, I have avoided "value change" event structures, and instead went with a while loop, stacked sequence, and series of case structures. After having done it, I decided this was a terrible idea. This time, I intend to build an array from the booleans, convert it to a number, and feed it in to a single case structure. This will give me the option to add cases for different combinations of the booleans being pressed.
    I guess the question is: What is the best method for doing something like this?  Does one have advantages over the other?
    Edit: I wasn't that clear.  I would like a comparison between the "value change" event structure method, and just feeding everything in to an array -> case structure.  I also am worried that with the bool array -> case structure that I will run in to problems where I end up with too many control variables, and the value of the resulting number gets ugly very quickly. The application has several buttons... next, last, save, load, several different configure setup buttons etc.
    Thanks!
    Solved!
    Go to Solution.

    Aalenox wrote:
    I am developing an application that is fairly user input based... lots of boolean control buttons to do different things.
    In the past, I have avoided "value change" event structures, and instead went with a while loop, stacked sequence, and series of case structures. After having done it, I decided this was a terrible idea. This time, I intend to build an array from the booleans, convert it to a number, and feed it in to a single case structure. This will give me the option to add cases for different combinations of the booleans being pressed.
    I guess the question is: What is the best method for doing something like this?  Does one have advantages over the other?
    Edit: I wasn't that clear.  I would like a comparison between the "value change" event structure method, and just feeding everything in to an array -> case structure.  I also am worried that with the bool array -> case structure that I will run in to problems where I end up with too many control variables, and the value of the resulting number gets ugly very quickly. The application has several buttons... next, last, save, load, several different configure setup buttons etc.
    Thanks!
    Event structure. Among other things, it will allow your loop to "sleep." then wake up when an event happens. With a case structure it's going to be constantly polling. Event structure is pretty much always the right way to go in newer versions of LabVIEW that have it available. I assure you, your first solution was aboslutely wrong and you noticed that, your second is better and was common the way before event structures existed, now that event structures exist, you should go with those.
    CLA, LabVIEW Versions 2010-2013

  • Can a case structure execute multiple cases?

    So I have a VI set up with a mutiple option case structure to select which input a voltage is read from (there are 32 options). Now that I have it made, I realize that sometimes I may want to read from multiple inputs at once.. Is there an easy way to change my setup so that it executes multiple cases at a time? Right now my control is a slider to choose the case. What would be a good front panel control choice to be able to select multiple options? Thanks
    Solved!
    Go to Solution.

    You can build an array of your options and loop through the required cases. As mentioned, a case can only perform 1 case per loop.
    A good front panel control would be a cluster or an array of booleans (e.g. a tick box per option), easy to loop through.
    /Y
    LabVIEW 8.2 - 2014
    "Only dead fish swim downstream" - "My life for Kudos!" - "Dumb people repeat old mistakes - smart ones create new ones."
    G# - Free award winning reference based OOP for LV

  • Boolean in empty case structure

    Hello Everybody,
    I am a bit stuck with one of my case structures. I am trying to set "True" for Boolean constant in order to enable "write to file" of the data once the number in one of the  dynamic data flows reaches threshold value 79. I want to make sure that all numbers will be written after that, and not only numbers >=79.
    My idea was to put Boolean "True" in the true part of the case structure, and leave nothing in the false part of the case structure. That unfortunately did not work  
    Does anybody know if there is a way to set Boolean to "True" after I reach desired number and keep it at "True" afterwards for continuous recording?
    I would really appreciate any help
    Oleks
    Solved!
    Go to Solution.
    Attachments:
    loadcell_final_trig_qsw_3_08_2009.vi ‏416 KB

    Just use a gobally initialized feedback node, less code.
    Message Edited by altenbach on 08-03-2009 07:44 PM
    LabVIEW Champion . Do more with less code and in less time .
    Attachments:
    Loadcell.png ‏1 KB
    LoadCell.vi ‏15 KB

  • Once I have sent an email I cant switch my case structure back to false

    This may be a stupid question because nobody else seems to have had a problem with it, so sorry if this is the case.
    Using the email Vi example provided with Labview, in a case structure, when the case structure goes true, it stays true as soon as the email vi is running, even after it has sent the email.
    Is there any way to stop it or does it need a specific timeout period?
    My very simple example is provided.
    Thanks for any help
    Alexi
    Attachments:
    mailtest[1].vi ‏28 KB

    alexi wrote:
    > This may be a stupid question because nobody else seems to have had a
    > problem with it, so sorry if this is the case.
    >
    > Using the email Vi example provided with Labview, in a case structure,
    > when the case structure goes true, it stays true as soon as the email
    > vi is running, even after it has sent the email.
    >
    > Is there any way to stop it or does it need a specific timeout period?
    > My very simple example is provided.
    Are you sure hotmail.com has an SMTP server running? I really doubt
    that. Or even if it does you may not be able to contact it, as most ISP
    block outgoing port 25 on their network to reduce problems with virus
    hyjacked boxens spamming the internet. Don't blame him, it is a very
    sensitive thing to do.
    If one of these p
    roblems occurs the Open TCP Connection function will
    timeout after 60 seconds and return with an error 56, network timeout.
    You will probably have to use the SMTP server of your ISP to send the
    messages to and this server will further send it to the correct receiver
    even if that one is on hotmail.
    Rolf Kalbermatter
    Rolf Kalbermatter
    CIT Engineering Netherlands
    a division of Test & Measurement Solutions

  • Programatically get the states of case structure

    Dear all,
    Is there a way we can programatically get all the states of a case structure in my VI.
    I know that there is no property node for case structure, but I am sure there must be some way that labview ppl must have thought about it.
    Awaiting....
    cheers
    Sree
    Solved!
    Go to Solution.

    With scripting, there is a property node for the case structure and you can query the names of the cases.  You will need LabVIEW 8.6 or greater for scripting.  Get started here.  Note that scripting is unsupported, except through the scripting message board.
    This account is no longer active. Contact ShadesOfGray for current posts and information.

  • Case Structures

    Can a case be created for Case Structures of a decimal value or range? That is say 0.001..0.5?
    I can create case structure for say 1..5
    can I create it for 0.001..0.5?
    Solved!
    Go to Solution.

    No you can't, the case structure terminal doesn't support decimals. but if you have a hand full of range like [.001;.01[, [.01;.1[ and [.1;.5[ then you could multiply and round the value by 1000 and set your range to 1..10, 10..100 and 100 to 500.
    Just a quick idea, other solutions would be possible.
    When my feet touch the ground each morning the devil thinks "bloody hell... He's up again!"

Maybe you are looking for