06-23-2008 12:25 PM
06-23-2008 12:51 PM
06-23-2008 01:47 PM
06-24-2008 10:27 AM
Altenbach,
Looked at your post on how to clear a shift register and came up with this. It works, but I don't understand why the 0 isn't added into my array. Thanks for your suggestion. To answer your question on adding the data to the bottom of the array: I'm entering concentrations in ascending order. I could add the data to the top, but then I would have to rearrange my array when complete.
Thanks,
Eric
06-24-2008 11:07 AM - edited 06-24-2008 11:13 AM
I'm not sure what you want to do, but did you intend NOT to wire the array through the FALSE case? The blue wire between the shift registers.
Oops... there's more.. you are adding one single element of 0 to the array.. so now I'm even more confused..
What is the TRUE case supposed to do? Why the ENTER button to stop the loop? Are you trying to initialize an array?
As I continue to look at the code, I get even more confused. It starts by comparing iteration 0 equal to 0 so it goes ito the True statement, runs a while loop that does nothing but wait for the ENTER button to be pressed. Returns zero to an uninitialized array. Offers the value 1 to the outer loop which stops because it is equal to 1. So why do you have a FALSE case? It will never go there.. So your array will always be 1 element 0.
RayR
06-24-2008 11:37 AM
06-24-2008 11:52 AM
Knoebel wrote:
The first program I wrote "enter concentration" didn't update the array unless I ran the vi again.
06-24-2008 12:03 PM
06-24-2008 12:08 PM
06-24-2008 12:48 PM
Joel and Altenbach,
Thanks for helping me out with this. It seems my solution is a combination of both your solutions. I'm building an array by running this vi multiple times. Each time a concentration is entered I leave this vi and start a calibration. Joel gives me the option to stop, but in my case that is accomplished by just entering the concentration and pressing enter or done. Altenbach's solution does this, but appending to the array isn't working. The data is overwritten and sometimes not written until the next time I run the vi. Probably a simple fix. I would not have come up with either of these solutions on my own so thank-you.
Eric