Differences

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

--- namespace:cameras [2026/04/20 16:04] – admin
+++ namespace:cameras [2026/07/28 16:58] (current) – [Allied Vision Camera] 12.144.223.107
@@ Line 28: / Line 28: @@
 ==== Baslers====
-Basler_4
+Basler_4/Frodo
-{{https://docs.baslerweb.com/a2a3840-45umbas|Basler_4 Manual}}
+{{https://docs.baslerweb.com/a2a3840-45umbas|Basler_4/Frodo Manual}}
+{{https://docs.baslerweb.com/aca1300-200um|Basler_1/EnergyCam}}
+====Streak Camera====
+Here are the steps to continuously triggering the streak camera and allowing the python script to archive the images.
+  - Turn on the camera and the HV
+  - Click on ''File'', then Click ''Algorithms\AcquireLoop.ini''
+  - the click to ''Algorithms Tab'', then navigate the directory from ''Algorithms to Loop: N=1''
+  - Click the "PLAY" button to run.
+  - Move to a terminal, Go to Directory:
+  - Run
+  - If you do a test, while Gen Archiving, from your laptop, the Shot_Numbers should match
+{{:namespace:img_1116.jpeg?400|}}\\
+{{:namespace:img_1114.jpeg?400|}}\\
+{{:namespace:img_1117.jpeg?400|}}\\
+====Allied Vision Camera====
+With the majority of Austin help, we got the Chris M. Allied Vision Camera working. The Main issue it was having was the Streaming, which relates to the time it takes to look for a Voltage trigger.
+This, coupled with arming the camera, there were differences between it and the Balser. We couldn't pull the frame willing we were streaming, but we needing to be stream long enough for the trigger to go through.
+plus, the switching between Internal(BG and live view) and External(Experiment) modes cause this to be a bigger issue.
+We did get this working seamlessly.
+Allied_0
+Allied_1: Chris M's : [[https://www.alliedvision.com/assets/support/Camera-Documentation/Allied-Vision/User-guides/Prosilica_GT_TechMan.pdf|GT 2000NIR]]