Re: [micro-manager-general] Andor iXon+, iXon3 bug?, need help
Status: Beta
Brought to you by:
nicost
|
From: Pedro A. <pa...@gm...> - 2020-03-12 09:07:54
|
Hi Lukas, Just as a sanity check, have you set the circular memory buffer to an appropriate size? https://micro-manager.org/wiki/Micro-Manager_Configuration_Guide#Memory_Settings Kind regards, Pedro Almada On Wed, 11 Mar 2020 at 18:04, Lukas Hille <Luk...@im...> wrote: > Hi, > > I need help with two Andor cameras. > > Two Andor cameras are used in dual view (Multi Camera adapter with > Andor: iXon+ and Andor: iXon3). > Acquisition is done by a burstAcquisition macro (equal to the script), > but the described behavior applies also to MDA. > With Frame transfer enabled and at higher Acquisition speeds (binning 2, > 0.9us vertical clock, 20ms exposure, full ROI) i get an buffer overflow. > > It appears that the device adapter before 14.April2019 "old" returns > very quick from mmc.popNextTaggedImage() and therefore produces no > buffer overflow, while the adapter after 14.April2019 "new" takes a very > long time to return from this function. > This also occurs with only one Camera in use, but with two cameras the > return time is to long to handle the data flow. > > A second issue is, that with Multi Camera adapter, the camera referring > to channel 0 (independent which one) stops acquiring after some time > (~60.000 images in Trigger: software). > This applies to the "old" and the "new" Andor device adapter. > > With Multi Camera adapter and external trigger (one source for both > cameras, Trigger set to External on both cameras), the camera referring > to channel 0 stops acquiring within 0 to some thousand images) > > I don't get any debugging error message with the new adapter. > With the old adapter i get for example: "GetNumberNewImages error: > first: 3473 last: 3473" for the camera on channel 0 before it stops > working. > > The goal would be to acquire about 200,000 time points with external > trigger at 20ms exposure time. > > I tried to understand the differences in the code from commits on > 14.April, but I didn't figure out why this makes a difference for the > popNextTaggedImage() function. > Also: the error message "GetNumberNewImages error:" doesn't make any > sense to me, referring to the situation that no new images are acquired. > > I would be very happy to get assistance on this one. > > Software: > AndorDriverPack2 - 2.103.30031.0 > Micro-Manager 2.0.0-gamma1 20200222 > mmgr_dal_Andor.dll from 1.04.2019, 16.04.2019 and 22.02.2019 (tried many > many more) > > best > Lukas > > -- > ____________________________________________ > Lukas Hille, M.Sc. > microscopy engineer > Luk...@im... > M +43 660 349 169 3 > > Department of Neurobiology, University of Vienna > Campus-Vienna-Biocenter 1 > 1030 Vienna > AUSTRIA > > https://neuro.univie.ac.at/ > https://www.imp.ac.at/groups/manuel-zimmer/ > Part of Vienna BioCenter > www.viennabiocenter.org > ____________________________________________ > > > > _______________________________________________ > micro-manager-general mailing list > mic...@li... > https://lists.sourceforge.net/lists/listinfo/micro-manager-general > |