What's the origin and history of this code? Something about it looks strangely familiar -- I have a vague recollection of some prior thread based on code from an academic paper related to raster scanning.
My first advice is a quote I've heard in a couple variations: "a problem well-defined is a problem half-solved." So the first thing is to consider *carefully* what things do and don't need to change. And why.
For example, do the calculations you perform at certain positions help determine which future positions you visit? Or is your trip full of discrete positions known ahead of time?
Will you eventually visit all, or nearly all the same coordinates? Or will you only stop at a small subset? And if only a small subset, will an Intensity Graph still be an appropriate way to visualize your results?
As you take altenbach's advice (pro tip: you should pretty much *always* take altenbach's advice) to change the Scan subvi to go to a single target position instead of doing the whole scan, you're going to find that you have to rethink a bunch of the counter code. There's a strong interdependency among the tasks that's based on the present scheme of hardware clocking through an uninterrupted scanning period. Switching over to single point at a time behavior will make it harder to sync your AO positioning, your AI measurements, and your CTR measurements.
It's probably going to be non-trivial to get that kind of change working really well over a variety of paths through your field of view. Longer moves between positions will require correspondingly longer times to accomplish physically, but not necessarily in a linear relationship. Just one of many implications. All part of why I advise you to consider very carefully what you're trying to do and why.
-Kevin P
ALERT! LabVIEW's subscription-only policy came to an end (finally!). Unfortunately, pricing favors the captured and committed over new adopters -- so tread carefully.
