Why wont my probes read outside of the For Loop?

[relative0]

The problem seems that, for some reason the when I try to line a wait time function outside of a while loop after I have used a boolean function, (subtract). What I am trying to do is to reset the time axis on the graph because it wants to spiral into millions of numbers and to keep counting. I want to just take samples of like 100-1000 milliseconds and graph my data pixels against it. I have tried a while loop, that seems to work sometimes. The thing is really weird, it seems as if it wants to work sometimes and in some places but not in others. I have attached some expamples and the VI I am trying to get to work. Notice the problem places are in Red.

Thanks alot guys, (and girls), for any help that y
ou can give me.

Brian

[Mads]

Could you include the other VIs as well (save with options -> development distribution)? It's not possible to run your VI without the sub-VIs.

I haven't fully understood what you are trying to accomplish, but looking at what I've got there are two things that come to mind:

If you are generating data inside the loop, and only want to sample some of it and send that data to a graph then you must make sure that the data flow works. A loop will not output the data you wire out of it until the loop has terminated.

Thre little grey dot you mention in the code is a "coercion dot", it means that the data you wire into the function/VI does not have the same type as the function expects. LV will use the polymorphism functionality to coerce the data to the correct t
ype, an operation that is best avoided, at least if it's a lot of data involved (requires extra memory to do the coercion) or if it may cause an incorrect value to be passed. In your case the image cluster you have wired to the IMAQ function is not based on the type definition the function is using, just replace the cluster with the type defined one you'll get rid of the dot.