Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

passive synchronization of camera acquisition and laser trigger (Follow mode) using u-FPGA through htSMLM #26

Open
smojiri opened this issue Mar 5, 2024 · 4 comments

Comments

@smojiri
Copy link

smojiri commented Mar 5, 2024

I tried doing passive synchronization between my sCMOS camera and laser triggering using u-FPGA (AU) device through htSMLM plugin. The '1-On' laser trigger works. However, the ''follow/camera mode'' for laser trigger does not. Further, no bug is apparent in my micro-manager Corelog ("enable debug logging": selected). Below is what I checked and tried:

  • compatibility of my u-manager version (nightly build 2.0.3 20240229) with htSMLM version (htsmlm-2.1.0)
  • installing both EMU and htSMLM from the source code
  • settings in my device property browser:
    'camera output trigger kind [0]': exposure (as I connect the corresponding timing port of the camera to the 'camera' port of FPGA box),
    'camera output trigger polarity [0]' :Negative/Positive both were tried,
    'laser trigger mode': 4 - Follow,
    'laser trigger duration0 (us)': 65535,
    'laser trigger-sequence0': 65535.
  • checking the camera output signal with oscilloscope: I get square signal with 3.4 V amplitude, ~10 ms pulse width and the frequency of 20 Hz for set exposure of 50 ms.
  • trying whether I get signal from trigger ports of FPGA box using a signal generator input to the 'camera port' of the FPGA box via the executable LabVIEW drive of u-FPGA. trigger set: 'follow' mode, sync: passive. I get the expected signal from the output trigger port of FPGA box: confirming my hardware works fine.

[uManagerConfiguration.txt]
(https://github.com/jdeschamps/htSMLM/files/14497953/uManagerConfiguration.txt)

[EMU_Configuartion.txt]
(https://github.com/jdeschamps/htSMLM/files/14497963/EMU_Configuartion.txt)

CoreLog20240304T192556_pid10756.txt

@jdeschamps
Copy link
Owner

Hi there,

That must be the most detailed problem report I have ever received! Thanks!

Are you using the full box that was built at EMBL? Things that come to mind:

  • Which voltage amplitude did you use when debugging the box with the signal generator? Is the camera signal still ~3.3 V when it reaches the FPGA? For instance in certain configurations, we had a 5V->3.3V voltage divider in between the "camera input" on the box and the FPGA, this would lower a 3.3 V signal to about 2 V and might not trigger the FPGA.
  • Can you try the same signal generator set-up to trigger the FPGA but this time in Micro-Manager? To exclude that the problem is not when setting up the property in Micro-Manager. I don't see any "set mode to Follow" in the CoreLog.
  • I would measure the camera signal right before the FPGA itself (inside the box).

Finally, are you at EMBL? (asking because most systems are there, and also because I'll be there next week)

@smojiri
Copy link
Author

smojiri commented Mar 5, 2024

Hi Joran,

I hope everything's going nicely for you. Thank you for your prompt reply!

. I tried a 5 V signal input and got the 5 V output from the trigger port but, I will try tomorrow with 3.3 V as well. Yes, the camera signal is 3.4 V when it reaches FPGA. I measure it both out of camera and also there inside the box just out of FPGA board. I'm using the old M3 FPGA box (figure attached). It's Au board. In terms of included electronics boards, I think it has the same boards as the last FPGA box version but I'll further verify tomorrow.

. That sounds like a quite useful try. Surely, I will do it. I just re-tried with u-manager 2.0.3-05012024 (the one you also last tested htSMLM 2.0.3 with). Attached, is the CoreLog where set to 'Follow' is in.

. will do

Yes, I'm at EMBL next week. Actually all the microscopes except mine is already in Vienna. Will be great to meet you!

Best, Soheil

CoreLog20240305T190757_pid1080.txt
FPGA_box

@jdeschamps
Copy link
Owner

Hi Soheil :)

Keep me posted. Otherwise let's try to find time next week in person.

On your picture, it seems the camera is indeed wired directly to the FPGA.

checking the camera output signal with oscilloscope: I get square signal with 3.4 V amplitude, ~10 ms pulse width and the frequency of 20 Hz for set exposure of 50 ms.

FYI, if the system would work, that would lead to 10 ms pulses from the lasers

@smojiri
Copy link
Author

smojiri commented Mar 6, 2024

Hi Joran,

Sorry that the image I posted is not clearly showing the wire connections. The connections is as following:
-the camera port of FPGA box is wired (the white wire) to the SCB board.

  • then from SCB to the FPGA board
  • lastly from FPGA board to the trigger ports

Regarding your points:

  • Which voltage amplitude did you use...? do you measure the camera signal right before the FPGA?
  • I tried inputting both 5 V and 3.3 V signal to the camera port of the FPGA box and measured it out of the SCB board (just before FPGA board) in both cases I measure 3.3 V.
  • trying with signal generator set-up to trigger the FPGA via u-manager (does setting property clicks drop/change signal? I did. It gives the same result: either set trigger mode '1 - On' or '4 - Follow' appear in the Corelog but only with set trigger mode '1 - On', I see 3.3 V shift in the amplitude of the output signal.

FYI: Yes, that was just for trying 'Negative' output trigger polarity. I also tried 'positive output polarity': all the same signal property but ~40 ms pulse width in 50 ms period.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants