40m QIL Cryo_Lab CTN SUS_Lab TCS_Lab OMC_Lab CRIME_Lab FEA ENG_Labs OptContFac Mariner WBEEShop
  40m Log  Not logged in ELOG logo
Entry  Mon Jun 3 21:03:54 2019, Milind, Update, Cameras, Steps to interact with GigE sitemap.pdf
    Reply  Tue Jun 4 22:24:45 2019, Milind, Update, Cameras, Steps to interact with GigE 
       Reply  Tue Jun 4 23:41:13 2019, gautam, Update, Cameras, Steps to interact with GigE 
          Reply  Wed Jun 5 22:30:13 2019, Milind, Update, Cameras, Steps to interact with GigE 
             Reply  Thu Jun 6 16:01:52 2019, Milind, Update, Cameras, Steps to interact with GigE terminal_medm_error.pdf
                Reply  Mon Jun 10 22:22:19 2019, Milind, Update, Cameras, Steps to interact with GigE 
                   Reply  Thu Jun 13 21:29:52 2019, Milind, Update, Cameras, Steps to interact with GigE terminal_error_server.pdf
Message ID: 14657     Entry time: Thu Jun 6 16:01:52 2019     In reply to: 14656     Reply to this: 14661
Author: Milind 
Type: Update 
Category: Cameras 
Subject: Steps to interact with GigE 

[Koji, Milind]

 

Today I ran into the following errors:

  1. Inability to access the EPICS channels using the commands caget and caput and thus the generation of a blank medm screen (error in Attachment #1) when simultaneously running the code in camera_server.py (/opt/rtcds/caltech/c1/scripts/GigE/SnapPy_pypylon/camera_server.py).
  2. Inability to run camera_server.py code with an active medm screen with a "... failed to read <EPICS channel>" error.

Therefore, Koji and I took a look at it and putting our faith in Gautam's hunch from elog 13023, we walked down to rack 1Y1 and keyed it. Following this, all the functionality previously described was restored! Koji then took a look at all the channels handled by this machine and bestowed upon me the permission to key the crate should I lose control of the GigE again.

Quote:

Thanks! It does indeed do the trick! With that I was able to

  1. Obtain current exposure value using the terminal command caget C1:CAM-ETMX_EXP
  2. Set exposure value using the terminal command caput C1:CAM-ETMX_EXP <desired_exposure_value>

Further, a quick look at the camera server code in /opt/rtcds/caltech/c1/scripts/GigE/SnapPy_pypylon/camera_server.py revealed that the script expects the details of "Number of Snapshots" in "Camera Settings" in the configuration file i.e in C1-CAM-ETMX.ini at ( /opt/rtcds/caltech/c1/scripts/GigE/SnapPy_pypylon/C1-CAM-ETMX.ini) which wasn't present before. Adding this parameter to the config file allows one to take a snapshot using the medm screen. Infact, unlike as described in this elog, I was able to start the server and client as described in elog 14649, and then obtain snapshots using the terminal command  caput C1:CAM-ETMX_SNAP 1.

Quote:

caget/caput probably does the job.

Quote:

Still not sure about how to modify the exposure time (other than using the pylon app, the only technique I know so far is to adjust the exposure manually on the medm screen and then run the scripts as described in the previous elog). 

 

 

Attachment 1: terminal_medm_error.pdf  59 kB  Uploaded Thu Jun 6 17:11:54 2019  | Hide | Hide all
terminal_medm_error.pdf
ELOG V3.1.3-