OmniScan feature ideas - NIDAQ multiple output scanners for AFM co-scanning

[michaelb1886]

What is affected by this bug?

For AFM scanning I have included a second set of analog outputs for driving an AFM stage at the same time as the confocal nanopositioner - total of 6 analog outs XYZ for the confocal and XYZ for the AFM. For my system I must move the two stages simultaneously.

When does this occur?

Scanning confocal images

Where on the platform does it happen?

How do we replicate the issue?

Expected behavior (i.e. solution)

It might be possible to create a second generic scanner that can generate analog outputs in response to scan line calls etc but that doesn't perform any actual photon counting? Or having a single scanner that generates 6 independent outputs - but can turn off certain axes when not required, leaving the AFM stationary and scanning only the confocal.

Other Comments

[Neverhorst]

Thank you again @michaelb1886 for your input. The plan for omniscan is to support an arbitrary number of virtual scanner axes in logic and GUI. If and how you implement scanning with different devices will probably be up to a hardware interfuse. I think this will solve this kind of issue in the future.