Differences

This shows you the differences between two versions of the page.

--- howto:antibunching_measurements [2019/07/26 07:12] – [Comments] buschmann
+++ howto:antibunching_measurements [2023/09/07 11:54] (current) – [Changing from Normal Acquisition (T3-mode) to Antibunching (T2-mode)] peter
@@ Line 7: / Line 7: @@
 ===== Emission Filters =====
-During Antibunching Measurements the [[Glossary:afterglow effect]] of the [[Glossary:SPADs]] may become visible as (un)expected additional peaks near the expected antibunching dip (see figure 2). These peaks might be useful to find the location of the dip, they are however artifacts caused by photons emitted (after the detection of a genuine photon) by one SPAD detected by the second SPAD. The distance of the expected dip and the afterglow peak is characteristic for the setup.
+During antibunching measurements, the avalanche breakdown flash of [[Glossary:SPADs]] may become visible as unexpected additional peaks near the expected antibunching dip (see figure 2). These peaks might be useful to find the location of the dip, they are however artifacts caused by photons emitted (after the detection of a genuine photon) by one of the SPADs, detected by the second SPAD. The distance of the expected dip and the afterflash peak is characteristic for the setup.
-To get rid of the afterglow peak it has been proven useful to introduce 2 identical bandpasses directly in front of each [[Glossary:SPAD]] and to use a 50:50 beamsplitter plate instead of a beamsplitter cube or to misalign the detectors slightly.(( The [[glossary:afterglow effect]] of [[products:MPD]] SPADs for Atto488 (485 nm excitation) could be eliminated by inserting one 536/40 bandpass in front of SPAD 2 (510LP in the filter wheel). For quantum dots the afterglow effect could be eliminated by using only one 593/40 bandpass in front of SPAD 2 (excitation @ 405 nm or 485 nm) ))
+To get rid of the afterflash peak, it has been proven useful to introduce 2 identical bandpass filters directly in front of each [[Glossary:SPAD]] E.g. the afterflash of MPD SPADs for Atto488 (485 nm excitation, emission around 520 nm) could be suppressed by inserting one 536/40 bandpass filters in front of SPADs.
-===== Antibunching using Symphotime =====
+We also recommend to use a 50:50 beam splitter plate instead of a beam splitter cube, or to intentionally misalign the detectors slightly.
+===== Antibunching using SymPhoTime =====
     *with [[Products:PicoHarp 300]] in [[glossary:T3-mode]]
-        *not possible with the [[software:SymPhoTime32]], because in [[software:SymPhoTime32]] the [[Glossary:Sync Divider]] is always active and set to 8
+        *not possible with SymPhoTime (32-bit version), because in SPT32 the Sync Divider is always active and set to 8
-        *data acquisition is possible with the [[Products:PicoHarp 300]]/[[Products:HydraHarp 400]] software as well as with [[software:SymPhoTime64]], where the sync divider can be disabled. With HH, don't use use SYNC channel as input for one detector, but e.g. Ch. 1+2. SYNC must be plugged in. Unfortunately, analysis of HH T3-antibunching data is not implemented in SPT.
+Instead, data acquisition is possible with native [[Products:PicoHarp 300]]/[[Products:HydraHarp 400]] softwares as well as with [[software:SymPhoTime64]], where the sync divider can be disabled.
+Using a PicoHarp300, connect one detector to Ch.0 (SYNC) and the other one to Ch.1
+With a HydraHarp400, don't use use SYNC channel as input for one detector. Use e.g. input channels 1 and 2. The SYNC should stay connected.
+Unfortunately, analysis of HydraHarp400 T3-mode antibunching data is not implemented in SPT.
     *with [[Products:PicoHarp 300]]/[[Products:HydraHarp 400]] in [[glossary:T2-mode]]
-        *measurements are possible with the [[software:SymPhoTime64]]
+        *measurements are possible with [[software:SymPhoTime64]]
 ==== Changing from Normal Acquisition (T3-mode) to Antibunching (T2-mode) ====
-=== Cabling: PicoHarp ===
+=== Cabling: PicoHarp 300 ===
-     -Disconnect Sync from [[Products:PicoHarp 300]] Ch0.
+     -Disconnect Sync from [[Products:PicoHarp 300]] Ch.0.
-     -Disconnect SPAD 1 Signal from Router ([[Products:PHR800]]).
+     -Disconnect SPAD 1 Signal from PHR800 Router.
-     -Connect SPAD 1 to [[Products:PicoHarp 300]] Ch0 (Do not use the attenuator).
+     -Connect SPAD 1 Signal to [[Products:PicoHarp 300]] Ch.0 only if it is NIM compatible. If the SPAD provides only TTL output pulses, you need to use the SIA400 adapter.
      -Adjustment of the CFD Level for Ch 0 (Sync Channel) might be necessary.
-    *It is also possible to connect both Detectors directly to the [[Products:PicoHarp 300]] without passing SPAD 2 through the router.    **In this case, however, the router cable (DVI-cable) needs to be disconnected from the PH300**
+It is also possible to connect both detectors directly to the [[Products:PicoHarp 300]] without passing SPAD 2 through the router. **In this case, however, the router cable (DVI-cable) needs to be disconnected from PicoHarp300**
-    *No special delay cables necessary
-=== Cabling: HydraHarp ===
+=== Cabling: HydraHarp 400 ===
-    *Disconnect Sync from [[Products:HydraHarp 400]] Ch0. (thats all)
+    *Disconnect the Sync signal from [[Products:HydraHarp 400]] SYNC IN. (That is all.)
-    *if Laser is attached via [[Products:SEPIA II]] driver, it's enough to disable the SYNC in the SEPIA software => no cable change necessary
+    *if the laser is an LDH-series heasd driven by [[Products:SEPIA II]] driver, it's enough to disable the SYNC in the SEPIA software => no cable change necessary.
 === Software Settings during Acquisition ===