-
It can't do scans as fast als FluoView (which scans rectangles
up to ca. 250kHz pixel frequency),
FluoLab only can do it at ca. 2kHz. But the fast X-Line
scan might be implemented in the
future to give the fast scans also to FluoLab.
-
As the AD-Card and the FluoLab XY-Scan-vi are triggered from
independend counters,
they the unsynchronized at scans bigger than some 256x256
pixels. This could be solved
with a line-based XY-Scan as done in FluoView, where the time span is not
so long.
-
The X-Mirror and the Y-Mirror can't be controlled simultaneously
in the kHz-domain.
(by the way... did you ever see a computer doing something
simultaneously?..). The underlying
dll-calls need some 3.8kHz and can only handle either
X or Y movements. The Line-Scan
for example consists of sequences of X and Y movements.
-
You need a AD-Card which is supported from NIDAQ. Typically,
this is a card from National
Instruments itself. The PM-Signal can't be get through
the FluoView-Hardware. But in this way
you get pure voltage-signal from the primary PM amplifier.
(has its roll-off at about 500kHz)