Setting Timer to Sequence Structure

Hi,
I'm currently designing a VI that perform analog data acquistion. How do I actually set a timer to each sequence so that they can run within stipulated time??

One of the easiest ways is to use the "Wait until Next millisecond" VI. Just place it in one of your sequences and program control will wait that long to execute the next sequence.
J.R. Allen

Similar Messages

Feature Film Editing in Premiere CC - Sequence Structure

I am looking to set up my sequence structure so that each scene has it's own sequence and then next each scene into a Master Sequence. My question is this:
Is there a way for Premiere to update the Master Sequence if the length of the Scene Sequence changes. As of now, I am not having much luck.
I know there will be small tweaks to the scene once I get feedback (Delete a line of dialogue, etc.) and would hope I wouldn't have to touch the Master Sequence for the continues outputs until the picture is locked.
And while we are at it, can some of you suggest how you set up your sequence structure for narrative features. Perhaps I am not approaching it in the best manner.

Perhaps you are not understanding the role of an editor. It is our job to create the sequence of material that tells a story. (Please excuse my snarky attitude)
As a scene lengthens or shortens, simply ripple edit the in or out points as necessary. The best method is the checker or a variation to the checker method; I often assign scenes with similar characteristics to a particular track, for example, all scenes that take place in the garden will live on track 3, all the kitchen scenes live on track 4. Or for story line 'A' you can designate tracks 1-3, then you can put the supportive / alternate story 'B' on tracks 4-6 also using the checker method. Again, excuse my attitude: don't be lazy.

How to execute a frame of a flat sequence structure for a specified amount of time?

Hello,
I have a timed loop measuring a resistance value every 2 seconds. I would like to have this timed loop execute for a specified amount of time (e.g. 5 minutes). The timed loop itself is placed within a flat sequence structure so I am concerned that the measurement will be taken once and the next frame will begin to execute, without waiting 2 seconds for a successive reading (and not looping for, say, 5 minutes).
In other words, is it possible to have a frame of a flat sequence structure execute for a specified amount of time before moving onto the next frame?
Thanks for your assistance!
JFK_Aero
Solved!
Go to Solution.

All code in one sequence frame must complete before the next frame can execute. So as long as your timed loop is setup correctly, the next frame cannot run until your 5 minutes is up (N = 5 minutes/2 seconds/measurement = 150 measurements).
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines

How should I set up my VI so that I can use the linear fit coefficient data analysis program, when my values are coming from while loops within a sequence structure?

I'm attempting to create a calibration program, using the printer port, and a Vernier Serial Box by modifying a calibration program designed for the serial box.
There are six calibration points, and to collect them, I have it controlled by while loops so that the numbers are taken when a button is pushed, and this is inside a sequence structure so that I can get the six different points. I feed these numbers into two different arrays (for x and y values) and then try to use the linear coefficient analysis on these points, but the values for the slope and intercepts it returns are not correc
t.
If I cut out the array and coefficient analysis, and feed the same numbers in directly without the while loop and sequence structures, it produces the proper values... I don't know why the numbers it is producing are different, and I'd really like to know.
Thanks,
Karinne.

I would use a data manager sub-vi that would be called by each from of the sequence structure that produced a data point. The data manager sub-vi could auto append new items or could place items in a specific entry of an array. Later on when you want to calculate the linear fit, call the sub-vi to return the array of values.
Stu

Elapse vi in sequence structure

Hi Guys
I know there a thousand way to implement a time elapse funciton, but i am curious the reason it does not work
I set first elapse vi tartget time 5 seconds, second 2 seconds and third 3 seconds in a for loop
It works in first and second iteraion. after a few iteration, the second and third elapse vi do not count time any more( I seems that the elapsed time is overwritten by first one. If you probe the three time elapsed output, it is always 5.
Attachments:
sequence timer.vi ‏104 KB

Well, if there are a thousand ways to do it, there are probably about 995 better ways to do it.
That being said, I believe you have to put a condition for each elapsed time that resets the timer on the first iteration of the while loop. And get rid of the elapsed times with nothing happenning. And learn how to use dataflow instead of sequence structures.
One FYI, too. Leave everything at the defaults except for the stuff you are changing - i.e., the reset and the time target. BIG HINT: i can = 0 only once.
Dataflow basics here.
Another BIG HINT:
Error in and Error out are inputs and outputs that could be used to enforce dataflow.
Bill
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.

Control references and sequence structures

My supervisor and I were discussing one of his programs, and he asked
me if I knew why he kept getting "Object reference is invalid" on a
property node that was using a reference. I couldn't figure it
out either, and eventually I said to try moving the actual control
itself (on the block diagram), into the first pane of the sequence
structure, and just feed the wire through.
This solved all of our problems... however both of us were
stumped with why what I suggested actually made it work. Anyone
know why this is?
Oops... I just realized that I made this on the breakpoint board
instead of the LabVIEW board...sorry. Although I suppose that the
people who frequent this might be the best to answer this...
Message Edited by Novatron on 07-14-2005 05:24 PM

There should be no difference between the two code versions IF you adhere to proper dataflow.
(Of course it is conceivable that the program is a mess and there is a race condition, e.g. if the reference is initially invalid and you set it elsewhere in the code via e.g. a local variable of the reference. In this case, a subtle change (e.g. the sequence structure) can rearrange the execution order for it to suddenly work by accident.)
I would be very curious to see a working example that demonstrates your described behavior.
LabVIEW Champion . Do more with less code and in less time .

How to set values to the structure containing a node with cardinality 0..n

Hello.
I 'm trying to set values for the node with cardinality 0..n. The node type is "Fields".
<xsd:complexType name="Field">
   <xsd:sequence>
      <xsd:element name="fieldCode" type="xsd:string"></xsd:element>
      <xsd:element name="displayValue" type="xsd:string" minOccurs="0"></xsd:element>
   </xsd:sequence>
</xsd:complexType>
<xsd:complexType name="Fields">
   <xsd:sequence>
      <xsd:element name="field" type="tns:Field" minOccurs="0" maxOccurs="unbounded"></xsd:element>
   </xsd:sequence>
</xsd:complexType>
I need to set several values for the element "fieldCode" but it has cardinality 0..1 and BPM does not allow it but I did not find any option about how to set values for the structure of type "Fields". Could you help me?
Best regards,
Timur Semenchuk

Hi Marcus,
If there is no way you could change the cardinality of the node, and thus it can contain 0..n items, I think you should create-and-add a new element programmatically.
Since the collection can contain zero elements, I would add a 'new' button, which upon clicking adds one new element via:
IYourNodeElement yourNodeElem = wdContext.nodeYourNode().createYourNodeElement();
wdContext.nodeYourNode().addElement(yourNodeElem);
Hope this explains a bit!
Best,
Robin van het Hof

In/out markers being set in the sequence instead of source clip

Here's what's happening:
1) I open a clip in the source monitor
2) I set the in/out points of a subclip and drag it to the timeline, no problem
3) I scroll around in the source monitor, finding a new clip
4) I hit in/out and try to drag the clip from the source monitor
5) The original clip is dragged over and I notice that the in/out points were set on my sequence instead of my source monitor.
The issue seems to be that focus doesn't follow the mouse intuitively? The focused/highlighted window remains the sequence even if I'm actively scrolling around in the source monitor and even if I hit in/out keys while the cursor is in the source monitor window -- the only way I can get the source monitor to be the focus is if I explicitly click on it.
I've only recently upgraded after some time over in FCP-land, but I feel as though this didn't seem to happen to me in previous versions of Premiere. Is there a preference or anything I can do to enable this to work? Many thanks in advance if anyone has ideas.
I'm on OS X Mountain Lion.

the only way I can get the source monitor to be the focus is if I explicitly click on it.
That's normal. If you want to keep focus on the Source Monitor, use the Insert or Overlay Edit commands instead of dragging.

Question about stacked sequence structure

Hi,
I made a numeric control outside a stacked sequence structure, and connect the control both to frame 1 and frame 2. In frame 2 there is a while loop structure. And now I start the labview program with the control A. Then, after frame 1 finished, frame 2 started, now I want to change the control to B and deliver B into frame 2. But the indicator in frame 2 shows that the control is still A. So I wonder how can I change the control and deliver it to the frame after the frame has started? Thank you!
NI Software : LabVIEW version 7.1
OS : Windows XP
Regards,
jackauden

Dataflow dictates what you are seeing. The control does not get read once the sequence starts. This is as expected.
Some possible solutions:
Just don't use stacked sequence! I don't and never feel limited by this choice.
Create local variable of the control and read from it inside frame 2.
Do you REALLY need a stacked sequence? Why???
LabVIEW Champion . Do more with less code and in less time .

Why does a sequence structure execute if a while loop is to the left of it?

I have a while loop in a case structure whose boolean is wired to a sub vi. To the right of this structure I have a sequence that executes regardless of the while loops condition. I assumed that the program would not continue to the case structure until the while loop stopped. Then it would proceed to the case structure.
Thank You

jemengineering wrote:
I have a while loop in a case structure whose boolean is wired to a sub vi. To the right of this structure I have a sequence that executes regardless of the while loops condition. I assumed that the program would not continue to the case structure until the while loop stopped. Then it would proceed to the case structure.
As others have mentioned, you have to familiarize yourself with the core idea of dataflow programming. One of the great powers of LabVIEW is the fact that things can occur in paralell unless there is data dependency.
A good start would be the LabVIEW beginners online tutorial:
http://www.ni.com/swf/presentation/us/labview/aap/default.htm
The quiz #1 on slide 11 deals with the above issues. Try to answer it.
In your particular case, you need to force execution order. This can be done by creating a data dependency (preferred) or by the use of a sequence structure. You could e.g. create a 2-frame flat sequence and place the loop in the first frame and the case structure in the second frame.
The picture shows a few scenarios for comparison. Can you spot the differences? Understanding dataflow is crucial for writing any LabVIEW program.
Message Edited by altenbach on 07-31-2006 06:49 AM
LabVIEW Champion . Do more with less code and in less time .
Attachments:
ExecutionOrder.png ‏19 KB

Question about the sequence structure

Hi,
If we want to get best performance when programming a sequence of functions or calculations, we should choose 'Stacked sequence structure' or 'Flat sequence structure'? or they have the same performance?
Thanks.

To the best of my knowlege there is no performance hit, the "Flat sequence structure" was a fairly recent addition to try and overcome one (of many) complaints about sequence structures in general, that stacked sequences obscure what is happening in the code. If the various sections of your calculation or functions have data dependency, i.e. the output of a calculation is fed into the subsequent calculation or function, then a sequence structure is probably not needed as, with data flow, the calculation that is "dependent" won't executed until all its inputs requirements are satified. If the "functions" are in the form of sub-vi's the method that is more "proper" is to inforce a dependency between subsequent vi's. This can be as simple as adding error in and out controls to the sub-vi's, even if they are only passed through the vi without actually performing an error function. This allows you to wire them together in the execution order that is required. Doing this on some of the early "built-in" functions that have remained in LabVIEW (the original timer functions) sometime requires putting a wrapper around them to make them sub-vi's with error passing, but in the latest versions of LabVIEW the compiler seems to do a good job of minimizing any performance hits this might appear to cause.
Putnam Monroe
LabVIEW Evangelist since 1992
Putnam
Certified LabVIEW Developer
Senior Test Engineer
Currently using LV 6.1-LabVIEW 2012, RT8.5
LabVIEW Champion

How to break a flat sequence structure ...??

How to break a flat sequence structure into two flat sequences structures......i am a student learning labview....help me..

To accomplish what you want you need to basically write some really ugly code. This is a side effect of using the flat sequence structure in the first place. This is exactly why they are not recommended.
First and foremost you will need to place your frame structure inside a loop. This will control how many times you execute the code.
Now you have a few alternatives to skip the first three steps which are kludging but time is of the essence.
1. Place a case structure around the code within the first three frames. Each frame will have a case structure. You can use the loop count to control only executing the code the first time through the loop.
2. You could combone the code of the first three frames into a single subVI and then use the same approach described above to skip executing that subVI.
Mark Yedinak
"Does anyone know where the love of God goes when the waves turn the minutes to hours?"
Wreck of the Edmund Fitzgerald - Gordon Lightfoot

Time dependent Hirarchy Structure

Hi,
I need to create Hirarchy, i did not create before,
Please some one explaine me how to create     Time dependent Hirarchy Structure in CostCenter InfoObject.
Please, please help me.
Thanks

HI
Find the below link
http://help.sap.com/saphelp_nw2004s/helpdata/EN/0e/fd4e3c97f6bb3ee10000000a114084/frameset.htm
Time-Dependent Hierarchies
Use
In a hierarchy that is not time dependent, the characteristic values are always the same.
If you want to create views of a hierarchy that are valid for a specific time period, you need to create the entire hierarchy as time dependent.
If you want to model relationships that change time-dependently, you need to create the hierarchy structure time-dependently.
Functions
In InfoObject maintenance, you can set whether and in which ways a hierarchy is time dependent. You can choose from the following:
·         whether the hierarchy is not time dependent (Hierarchy Not Time-Dependent). This is set by default.
·         whether the entire hierarchy is time dependent (Entire Hierarchy Time-Dependent).
·         whether individual node relationships are time dependent (Hierarchy Structure Time-Dependent)
·         whether a temporal hierarchy join is used with time-dependent hierarchy structures (Use Temporal Hierarchy Join)
Entire Hierarchy is Time-Dependent
You can either load time-dependent hierarchies (see Loading Time-Dependent Hierarchies) or create them in the BI system (see Creating a Hierarchy). When you create a time-dependent hierarchy, you have to enter a validity interval (valid to and valid from fields).
If an entire hierarchy is time dependent, the system creates hierarchy versions that are valid for separate intervals. The system automatically uses the current valid version in this case. The hierarchy valid in each case can be uniquely identified by its technical name and the From-To Date.
In the InfoObject tree of the Data Warehousing Workbench, all time-dependent hierarchies under the associated InfoObject are displayed with the corresponding To Date, for example Time-Dependent Hierarchy 05/31/2000.
In reporting, the system returns the valid hierarchy when a query is executed using the query key date.
Within a restructuring company areas, you can create time-dependent versions of a hierarchy for the Main Area InfoObject. This enables you to compare the restructuring over different time periods in a query.
Time-dependent hierarchy 01/01/1999 - 05/31/1999
Time-Dependent Hierarchy 06/01/1999 - 12/31/1999
Main Area NORTH
Main Area NORTH
Area 1
Area 2
Area 2
Main Area SOUTH
Main Area SOUTH
Area 1
Area 3
Area 3
Area 4
Area 4
In reporting, you can work in the individual columns of the report structure with fixed date values. You may want to do this to compare Main Area North in the Time-Dependent Hierarchy 05/31/2000 with Main Area North in the Time-Dependent Hierarchy 06/01/2000 (simulation).
Time-Dependent Hierarchy Structures
You can either load time-dependent hierarchies (see Loading Time-Dependent Hierarchies) or create them in the BI system (see Creating a Hierarchy).
In hierarchy maintenance, you can determine a valid time interval for each hierarchy node (Valid to and Valid from fields).
In reporting, a hierarchy with time-dependent hierarchy structures is created either for the current key date or for the key date defined for the query. In addition, you can evaluate a hierarchy historically using the temporal hierarchy join.
You can assign an employee to different cost centers at different times within the context of a restructuring.
In the context menu of a hierarchy, choose Display Hierarchy to access the hierarchy display: Each node and leaf has been given a date symbol. Hierarchy nodes that are assigned to different places in the hierarchy structure, depending on the time, are displayed more than once. By double clicking on a hierarchy node, you can display the associated validity period for the node relation.
In the following example, you can double click on the Jones leaf to see that the worker Jones was assigned to region USA between 01/01/1999 and 05/31/1999 and Puerto Rico from 06/01/1999 to 12/31/1999.
In order to use a hierarchy with a time-dependent hierarchy structure in reporting, you require the following settings in the BEx Query Designer:
                            a.      If you want to evaluate a hierarchy with a time-dependent hierarchy structure for a fixed key date, enter the key date in query definition.
                            b.      If you want to evaluate a hierarchy with a time-dependent hierarchy structure historically, for a key date that is to be derived from the data, choose the temporal hierarchy join option and specify the derivation type for the key date.
For a more detailed description of the functions and differences between the two evaluation views, see Time-Dependent Hierarchy Structures in the Query.
In maintenance of the key date derivation type (RSTHJTMAINT) determine the rule you want to use to determine the key date from the data. In this way you determine the time characteristic and way in which the key date is to be derived.
       1.      First determine the time characteristic.
If you choose a Basic Time Characteristic as a time characteristic (for example, 0CALDAY, 0CALMONTH, 0FISCPER), you can use a key date derivation type of this kind for all InfoProviders that contain exactly one time characteristic that references the selected basic time characteristic. If there are several time characteristics in an InfoProvider that reference the basic time characteristic, you have to either determine the time characteristic more specifically or select a particular time characteristic from a particular InfoSet (Time Characteristic from InfoSet).
       2.      Determine how you want the key date to be derived from the time characteristic.
The following derivation types are available:
¡        First day of the period
¡        Last day of the period
¡        Delay by number of days (you specify this in the Delay by Days field). In this case, the key date is calculated from the first day in the period plus the number of days specified minus 1. If the key date does not fall within the period, the last day of the period is used.
Key date derivation type with (basic characteristic = 0CALMONTH, derivation type = u201Cfirst day of periodu201C):
·         For January 2005 the key date is calculated as 1/1/2005.
·         For February 2005 the key date is calculated as 2/1/2005.
Key date derivation with (basic characteristic = 0FISCPER, derivation type = u201Cdelay by number of daysu201C and u201Ddelay u201C = 29):
·         For K4/01.2005 the key date is calculated as 1/29/2005.
·         For K4/02.2005 the key date is calculated as 2/28/2005.
·         For K4/03.2005 the key date is calculated as 3/29/2005.
Note that the way in which you determine the key date derivation type affects performance. The number of data records that the OLAP processor reads corresponds to the level of detail on which the time characteristic and the leaf level lie. For this reason, choose the time characteristic as approximately as possible in order to keep the hierarchy small.
A small hierarchy has 100 leaves. For a period of 12 months, the OLAP Processor reads 1200 data records at month level. At day level, it reads 36500 data records.
Regards,
kumar reddy.k
Edited by: kumar reddy on Nov 18, 2008 10:50 AM

Incrementing sequence structures

I am sure there is an easy way to do this, but I can't quite get it to work properly. Any help would be appreciated:
I have a while loop that runs for 40 seconds. When those 40 seconds are up, it triggers a dialog box to pop up. That dialog box is in a sequence loop that contains 30 different frames. Each frame has a different dialog box message. This entire portion is surrounded by a for loop.
What I am trying to do is have:
1. the while loop run for 40 seconds
2. the first frame of the sequence with dialog box #1 to pop up
3. the original while loop to run again for another 40 seconds
4. the second frame of the sequence with dialog box #2 to pop up
5. the original while loop to run again for ano
ther 40 seconds
6. the third frame of the sequence with dialog box #3 to pop up
and so on....
I have a for loop around the entire thing so that it can repeat the same while loop structure multiple times. I have a 30 wired into the N input of the for loop so that it will run the entire portion 30 times (corresponding to the 30 different dialog box messages that have to pop up).
How can I get one and only one frame of the sequence structure to pop up after the while loop finishes its 40 second period of running?
I would gladly email you this portion of the code for you to take a look at if it will help. Just let me know where to send it.
Thanks.

This does seem to be a good application for a case statement. If you do
need to keep the sequence format for some reason, could you put the while
loop in vi that you can drop into each of the sequence frames?
Dan.
"Koen" wrote in message
news:[email protected]..
> It seems to me that it would be much easier to use a case instead of a
> sequence and wire the increment (i) of the while loop to the selector
> of the case. In this way loop 0 will execute case 0 ,1 executes 1 and
> so on each after the 40 sec wait.
> Is there any particular reason for using the sequence?

Are sequence structures the right approach here?

Hi everyone,
The attached VI shows the endmembers in case structure form of a relatively simple task I need to perform. It takes a bank of 6 digital outputs and toggles between true and false logic. Between the endmembers, I need to change the logic on some ports sequentially and after time delays. For instance, changing the case from true false, I need to change line 2 from false to true 2 seconds before I change lines 4 and 5 to true. I want the user to see only one button to toggle between states, and I want the states to be discrete and not continuously changing.
Are sequence structures the best way to do this? If I put those into the case structure, won't it re-iterate the sequence over and over? Or do I need a case structure initialized with shift registers so that it stops after one interation until the next time the user toggles the control?
Thanks for any help on this,
Brad
Attachments:
ValveBankEndMembers.vi ‏56 KB

I have a couple suggestions. Most important, have two cases in your case structure. One for the toggle, one for the quit. Otherwise you will have to wait for a toggle in order to process the quit. I also lumped the controls into a cluster. You are converting from array to cluster anyway, this saves you the unbundle. Finally, since you are toggling each boolean, you can just apply a NOT to the entire array and use a shift register to pass the array from one loop iteration to the other. This last will save a lot of debugging headaches if you ever need to add/remove bolleans.
Message Edited by jasonhill on 06-14-2006 09:05 AM
Attachments:
Toggle Trap 2.PNG ‏14 KB
ValveBankEndMembersEvent2.vi ‏16 KB

Setting Timer to Sequence Structure

Similar Messages

Maybe you are looking for