Digital Camera System

Overview

• GigE cameras work on the dedicated camera network, which is one of local networks under CDS network. The main software is managed on pylon-camera-server on LIGO Git and the binary package is available on LIGO's Debian repository via the apt-get command. A few camera servers belonging to both CDS and camera networks serves all camera images in the camera network to the client workstations in the CDS network. Old camera system called as camlan or camera-server is no longer updated for a long time. So it will be expired also in KAGRA, though the old one is still remaining.

Software Structure

Server side

• pylon-camera-server

  file	note
  /usr/bin/pylon-camera-server	Server application of pylon-camera-server (installed by apt)
  /kagra/camera/pylon-camera-config/K1-CAM_*.ini	Configuration files for pylon-camera-server
  /kagra/camera/pylon-camera-service	User interface for pylon-camera-server services on camera servers
  /kagra/camera/pylon-camera-status.sh	Status checker of pylon-camera-server
  ~controls/.config/systemd/user/pylon-camera-server@.service	Service template for pylon-camera-server
  ~controls/.config/systemd/user/pylon-camera-status.service	Service file for status checker of pylon-camera-server
  ~controls/.config/systemd/user/pylon-camera-status.timer	Service scheduler for status checker of pylon-camera-server

• camlan camera-server

  file	note
  /kagra/apps/camera/bin/camera_server.py	Server application of camlan camera-server
  /kagra/apps/camera/bin/camera_pcas.py	Pcas Server application
  /kagra/camera/camlan-camera-config/K1-CAM_*.ini	Configuration files for old camlan camera-server
  /kagra/camera/camera-service	User interface for old camlan camera-server services on camera servers
  /kagra/bin/CAM/camera_status.sh	Status checker (1) of camlan camera-server
  /kagra/bin/CAM/camera_ping.sh	Status checker (2) of camlan camera-server
  /etc/systemd/system/camera@.service	Service template for camlan camera-server
  /etc/systemd/system/camera_pcas@.service	Service template for Pcas process
  /etc/systemd/system/camera_status.service	Service file for status checker (1) of camlan camera-server
  /etc/systemd/system/camera_ping.service	Service file for status checker (2) of camlan camera-server

• common

  file	note
  /etc/systemd/system/cpupower-performance.service	Service file to ensure max performance behavior of CPU
  /kagra/camera/find_cameras.py	A tool for showing all camera list in the CAM network

Client side

• file	note
  /kagra/apps/camera/bin/camera_client.py	Camera client application to display an image on X11 and to save an image/video to a file
  /kagra/apps/camera/bin/camera_client_movie.py	Camera client application to save a video to a file (Deprecated)
  /kagra/apps/camera/bin/camera-service-client.sh	User interface for camera services on CDS workstations
  /kagra/apps/camera/bin/revert_default_expgain.sh	Revert to default values in config file

EPICS IOC@k1script1

• file	note
  /opt/rtcds/kamioka/k1/target/k1cam/db/GigE.substitutions	Record definition for each camera
  /opt/rtcds/kamioka/k1/target/k1cam/db/Cam.db	Record definition for each server
  /etc/supervisor/conf.d/k1cam.conf	Service file to launch IOC

How to Use

• To show the display, open sitemap on any workstations (click medm icon on the desktop), and choose CAMERA.

• You can/opt/rtcds/kamioka/k1/target/k1cam/db record the movies from MEDM screen.

• End-user Manual

How to add new cameras

1. Setup camera IP address and Name

   • using GUI (blog)

   • using script after physically connecting a camera to the CAM network

     k1cam0> /kagra/camera/find_cameras.py --key $(serial) --addr $(ip_address)
     k1cam0> /kagra/camera/find_cameras.py --key $(serial) --name $(camera_name)

2. Install GigE camera
3. Assign configuration file
4. Start camera service
5. Update medm screens

Configuration files

• Configuration files are stored as K1-CAM-*.ini in /kagra/camera/pylon-camera-config/ (/kagra/camera/ instead for the old camlan system). A format of the configuration files are as follows. What we must edit are serial_number, overlay_text, multicast_addresses, channel_prefix and archive_file_name_prefix. Serial number can be checked on the camera body and camera name and multicast address must be decided as a unique value.

  • serial_number=00000000
    packet_size=8192
    inter_packet_delay=50000
    exposure_auto=0
    exposure_time_raw=1000
    gain_auto=0
    gain_raw=100
    timeout_ms=5000
    width=640
    height=480
    framerate_numerator=25
    framerate_denominator=1
    format=GRAY8
    overlay_text=OMC_TRANS
    overlay_silent=false
    multicast_address=239.192.0.x
    multicast_port=65000
    ttl_mc=64
    channel_prefix=K1:CAM-OMC_TRANS_
    calc_noise_floor=25
    archive_interval_minutes=0
    archive_folder_path_prefix=/kagra/camera/images/
    archive_file_name_prefix=OMC_TRANS

Start (and manage) camera service

• First, you need to decide which camera server (k1cam0, k1mca1, or k1cam2) to register the new camera with. Initial registration is done by logging into the camera server and executing the /kagra/camera/pylon-camera-service command (/kagra/camera/camera-service instead for the old camlan system). Following example is to register the OMC_TRANS camera on k1cam0.

  • k1ctr> ssh k1cam0
    k1cam0> /kagra/camera/pylon-camera-service enable OMC_TRANS

  pylon-camera-service command has following sub-commands.

  • list                 : show registered cameras
    enable <camera_name> : register cameras on the camera server
    disable <camera_name>: unregister cameras on the camera server
    start <camera_name>  : start camera process
    stop <camera_name>   : stop camera process
    restart <camera_name>: restart camera process
    status <camera_name> : show the status of camera process
    log <camera_name>    : show the log of camera process

  enable/disable can be executed only on the camera server and another sub-commands can be executed also on the CDS client workstations via /kagra/apps/camera/bin/camera-service-client.sh or the Shell Command block on the MEDM screens.

Update MEDM screens

• MEDM screens are stored in /opt/rtcds/userapps/release/cds/common/medm. When the new cameras are added, K1IFO_CAM.adl and K1CAM_STATUS.adl must be updated. Camera interface screen is served as CUST_CAMERA_PYLON.adl (CUST_CAMERA.adl instead for the old camlan system) with MEDM macros e.g. CAMERA=K1:CAM-OMC_TRANS and CONFIG=K1-CAM-OMC_TRANS.

How to recover

If GStreamer isn't started

1. Disconnect the LAN cable once or Switch ON/OFF power supply from network switch
2. Restart camera process

   k1cam?> /kagra/camera/pylon-camera-service restart $(camera_name)

How to ON/OFF power supply from camera switch

1. SSH connect with dynamic forward

   ssh -D 10000 k1cam0

2. Open web browser on workstation with setting SOCKS proxy

   Preferences -> Network Settings -> "Manual proxy configuration" SOCKS Host:localhost, Port:10000

3. Input IP address of network switch

4. System -> PoE -> PoE Port Configuration

5. Select the port and "disable" -> APPLY -> "Enable" -> APPLY

Hardware Assignments

Viewport Status

Status after iKAGRA

Cameras

Cameras

在庫

場所：PSL-S-A 3(2023/11/27)

Network Switches

There is the main switch in the main digital room. All the other switches are connected to the main switch with cat 6 LAN cables. Switches in EX and EY are connected to the main switch via optical fibers.

Camera Network Plan

Camera Machines

TEST for 10G network

Test of 10G switch has been done. We confirmed the following switch works. Three of them are bought, but not installed. They are to be installed for bKAGRA.

Network Switch

物品のありか

• 雲台：倉庫（Y側）、段ボール箱
• カメラ、レンズの在庫、カメラと雲台のアダプタ、ネジ、ペデスタル、NDフィルタ等（あれば）：PSL-S-A 3
• ビューポートに取り付けるための台座：MC近くの棚、MCE寄り（上とは別の箱）

Camera related information

• Camera document tree (JGW doc)

• Plan

• Basler GigE camera acA640-120gm

• Camera platform (MH1301-665 Professional Head System)

• Network Configuration

• GigE Camera Network

• Consideration to use a2A series (a2A5328-4gmPRO)

Requested