12-08-2010 10:10 AM
Reading the file at the beginning of the program only updates the numeric array. Once the loop starts, you overwrite the numeric array with new data that comes out of your A1 timer subVI. And that returns to zero because that is how you are initializing inside of it.
What you need to do is turn your subVI into an Action Engine that has the normal state of running, but also an initialization state where you feed it the data that you read in from the file and save that data into the uninitialized shift registers as your starting time.
12-08-2010 11:16 AM
The subVI does not use shift registers, rather "feedback nodes"
Is it still possible to feed the data that is read in from the file? From my understanding an AE is a Functional Global that stores information. I have already "initialized on compile or load" for the feedback node. What am I missing? How would I put file read/write into the SUBVI code otherwise? I have gone to the forums but to no avail
mhaque
12-08-2010 11:29 AM
From what I recall looking at your subVI (don't have it in front of me now), you can feed the values you read from the file into it and use them to initialize your FN.
12-08-2010 12:02 PM - edited 12-08-2010 12:03 PM
where would I place the data read into the feedback node?
mhaque
12-08-2010 12:04 PM
In place of the zero filled arrays that you are creating.
12-08-2010 02:05 PM
I have worked with probes, but I can't seem to figure out where the initialization takes place.
altenbach originally wrote the subVI.
mhaque
12-08-2010 10:13 PM
Do you mean in this thread? Can LabVIEW pickup from where it left off?.
Why did you go off and start a whole new thread about the same programming issue you were having?
Keep everything in one thread where you were already being helped 5 days before you started this thread. You've basically caused us to duplicate our efforts and wasted our time.
12-09-2010 07:40 AM
Actually the 2 issues merged. In one thread I was trying to save and the other dealt with the stop watch.
Either way I'm sorry about the inconvenience and thanks for all the help from the LabVIEW community.
mhaque