• drvAsynI2C (only tags with `-sbc`)
• devGpio (only tags with `-sbc`)

#!/epics/ioc/bin/linux-<ARCH>/epicsIoc

epicsEnvSet( "STREAM_PROTOCOL_PATH", "/epics/ioc/protocols/" )

## Register all support components
dbLoadDatabase( "/epics/ioc/dbd/epicsIoc.dbd", 0, 0 )

• Add a host device to the container:

  --device <DEVICENAME>[:<NAME_INSIDE_CONTAINER>]
  # e.g. --device /dev/ttyS0      ## add serial port0 to container
  # e.g. --device /dev/gpiochip0  ## add gpio interface to container (this is mandatory for the `-sbc` tagged images)

• Add user inside container to a group:

  --group-add $(getent group | grep <GROUPNAME> | cut -d ":" -f 3)
  # e.g. --group-add $(getent group | grep gpio | cut -d ":" -f 3)  ## add the user inside the container to the host's gpio group

• 2.0.0, 2, latest
  based on epics-base 7.0.6.1, asyn 4.42 with FTDI support, autosave 5.10.2, calc 3.7.4, modbus 3.2, devSnmp 1.1.0.2, StreamDevice 2.8.22, iocStats 3.1.16, devThmpLedPulser 1.0.0
• 2.0.0-sbc, 1-sbc, latest-sbc
  based on epics-base 7.0.6.1, asyn 4.42 with FTDI support, autosave 5.10.2, calc 3.7.4, modbus 3.2, devSnmp 1.1.0.2, StreamDevice 2.8.22, drvAsynI2C 1.0.3, devGpio 2.0.0, iocStats 3.1.16, devThmpLedPulser 1.0.0
  

  ---

docker run -d --network host -v <LOCAL_DIR>:/config paluma.ruhr-uni-bochum.de/epics/ca-gateway -cip <CLIENT IP> -sip <SERVER IP> -pvlist <PVLIST_FILE> -access <ACCESS_FILE>

• 2.1.3.0, 2, latest

  ---

• 4.6.9, 4, latest

  ---

• 4.6.9, 4, latest

  ---

1. Create a directory, where you will store the needed configuration files for our IOC (e.g. `${HOME}/hameg_demo`)
2. Now create a file called "hameg_demo.sub" inside this newly created directory with the following content to get access to all for channels of this device

   file "/epics/ioc/databases/hmp4040.db"

1. 1. 1. Now we need a startup script for our EPICS IOC, which opens the serial interface and configures it so we can talk to the HMP4040. The default settings of the HMP4040 is 8N1 at 9600baud.
         Create a file "hameg_demo.cmd" within the directory we created at the beginning:

         #!/epics/ioc/bin/linux-x86_64/epicsIoc
         
         epicsEnvSet( "STREAM_PROTOCOL_PATH", "/epics/ioc/protocols/" )
         
         ## Register all support components
         dbLoadDatabase( "/epics/ioc/dbd/epicsIoc.dbd", 0, 0 )

1. 1. 1. Now start the docker container to run your IOC:
         

         docker run -dit --name hamer-demo -v ${HOME}/hameg_demo:/config --device /dev/ttyS0 paluma.ruhr-uni-bochum.de/epics/ioc:latest /config/hameg_demo.cmd

1. 1. 1. Now we need a startup script for our EPICS IOC, which opens a TCP/IP port to the HMP4040.
         Create a file "hameg_demo.cmd" within the directory we created at the beginning:

         #!/epics/ioc/bin/linux-x86_64/epicsIoc
         
         epicsEnvSet( "STREAM_PROTOCOL_PATH", "/epics/ioc/protocols/" )
         
         ## Register all support components
         dbLoadDatabase( "/epics/ioc/dbd/epicsIoc.dbd", 0, 0 )

1. 1. 1. Now start the docker container to run your IOC:

         docker run -dit --name hamer-demo -v ${HOME}/hameg_demo:/config paluma.ruhr-uni-bochum.de/epics/ioc:latest /config/hameg_demo.cmd

         ---

1. Now create a file called "wiener_demo.sub" inside this newly created directory with the following content to get access to channels 'u0' and 'u1' of this device. The macro CRATE is either the hostname or the IP address of the MPOD crate.

   file "/epics/ioc/databases/WienerPL500.db"
   {
     pattern { H, N, CRATE, CH }
       { LMD, MUPIX:LV:P0:H1, 192.168.0.5, u0 }
       { LMD, MUPIX:LV:P0:H1, 192.168.0.5, u1 }
   }

2. Now create the startup script for the IOC

   #!/epics/ioc/bin/linux-x86_64/epicsIoc
   
   epicsEnvSet( "STREAM_PROTOCOL_PATH", "/epics/ioc/protocols/" )

1. Now start the docker container to run your IOC:

   docker run -dit -v ${HOME}/wiener_demo:/config --name snmp-demo paluma.ruhr-uni-bochum.de/epics/ioc:latest /config/wiener_demo.cmd

docker run --network host -e DISPLAY=$DISPLAY --device /dev/dri -v <LOCAL_DIR>:/config -v /tmp/.X11-unix:/tmp/.X11-unix paluma.ruhr-uni-bochum.de/epics/phoebus -settings <CONFIG_FILE>

• 4.6.9, 4, latest

docker run -d -v <LOCAL_DIR>:/config -p 4812 paluma.ruhr-uni-bochum.de/epics/archive-engine -engine <ENGINE> -settings <CONFIG_FILE>

• 4.6.9, 4, latest

Examples of using the epics-ioc

1. Create a directory, where you will store the needed configuration files for our IOC
2. Now create a file called "hameg_demo.sub" inside this newly created directory with the following content to get access to all for channels of this device

   file "/databases/hmp4040.db"

1. The HMP4040 has two interfaces for remote control: USB and Ethernet. I will discuss both
   
   1. USB:

1. 1. 1. Now we need a startup script for our EPICS IOC, which opens the serial interface and configures it so we can talk to the HMP4040. The default settings of the HMP4040 is 8N1 at 9600baud.
         Create a file "hameg_demo.cmd" within the directory we created at the beginning:

         #!/epicsIoc
         epicsEnvSet( "STREAM_PROTOCOL_PATH", "/epics/protocols" )
         dbLoadDatabase( "/epics/dbd/epicsIoc.dbd", 0, 0 )
         epicsIoc_registerRecordDeviceDriver( pdbbase )

1. 1. 1. Note in the file above: the first parameter of `drvAsynSerialPortConfigure` is an internal name for the newly created device handle. This has to be the same name we used in our "hameg_demo.sub" as value for the PORT macro.
         This startup script now creates a handle for the serial port at "/dev/ttyAMA0", configures this port and afterwards loads all needed records via the substitution file we created in the beginning.
      2. Now start the docker container to run your IOC:
         

         docker run -dit -v ${HOME}/hameg_demo:/config --device /dev/ttyAMA0 paluma.ruhr-uni-bochum.de/epics/ioc /config/hameg_demo.cmd

   2. Ethernet:

1. 1. 1. Now we need a startup script for our EPICS IOC, which opens a TCP/IP port to the HMP4040.
         Create a file "hameg_demo.cmd" within the directory we created at the beginning:

         #!/epicsIoc
         epicsEnvSet( "STREAM_PROTOCOL_PATH", "/epics/protocols" )
         dbLoadDatabase( "/epics/dbd/epicsIoc.dbd", 0, 0 )
         epicsIoc_registerRecordDeviceDriver( pdbbase )

1. 1. 1. Note in the file above: the first parameter of `drvAsynIPPortConfigure` is an internal name for the newly created device handle. This has to be the same name we used in our "hameg_demo.sub" as value for the PORT macro.
      2. This startup script now creates a TCP/IP connection to the HMP4040 and loads all needed records via the substitution file we created in the beginning.
      3. Now start the docker container to run your IOC:

         docker run -dit -v ${HOME}/hameg_demo:/config paluma.ruhr-uni-bochum.de/epics/ioc /config/hameg_demo.cmd

docker run -dit -v <LOCAL_DIR>:/config --name <NAME_OF_CONTAINER> [OPTIONS] paluma.ruhr-uni-bochum.de/epics/ioc <IOC_STARTUP_SCRIPT>

docker run -dit -v /home/florian/epics-docker/test/ioc-config:/config --name hameg-demo --device /dev/ttyS0:/dev/ttyHameg paluma.ruhr-uni-bochum.de/epics/ioc /config/hameg_demo.cmd

#!/epicsIoc

epicsEnvSet( "STREAM_PROTOCOL_PATH", "/epics/protocols" )
dbLoadDatabase( "/epics/dbd/epicsIoc.dbd", 0, 0 )

docker attach <CONTAINER_ID/NAME>

• Connect to serial devices:

  --device /dev/<DEVICENAME>[:<NAME_INSIDE_CONTAINER>]

• Connect being a member of e.g. group dialout:

  --group-add $(getent group | grep dialout | cut -d ":" -f 3)

• Connect to I2C (arm only):

  --device /dev/i2c-<NUM>

• Connect to CAN bus devices:

  --network host

• • -p 5064-5065:5064-5065 -p 5064-5065:5064-5065/udp # for CA

  • --network host # for PVaccess

• • -e EPICS_CA_AUTO_ADDR_LIST=no -e EPICS_CA_ADDR_LIST=<LIST OF IP ADDRESSES> # for CA

    UDP broadcasts are not forwarded by Docker's default network (bridge). Setting `EPICS_CA_ADDR_LIST` to the broadcast address (e.g. `192.168.0.255`) does not work.
    Alternatively use `--network host`

  • --network host # for PVaccess

• 1.2.1, 1, latest
  based on epics-base 7.0.6.1, asyn 4.42 with FTDI support, autosave 5.10.2, calc 3.7.4, modbus 3.2, devSnmp 1.1.0.2, StreamDevice 2.8.22, drvAsynI2C 1.0.3, devGpio 2.0.0, iocStats 3.1.16, devThmpLedPulser 1.0.0
  This image is based on Debian Bullseye, timezone is set to Europe/Berlin
• 1.2.1-slim, 1-slim, latest-slim
  Same as above, but the image only contains the ioc, db files, and protocol files.

docker run -d --network host -v <LOCAL_DIR>:/config paluma.ruhr-uni-bochum.de/epics/ca-gateway -cip <CLIENT IP> -sip <SERVER IP> -server -pvlist -access

• 2.1.2.0, 2, latest

epics-ioc

• iocStats
• execute

• 1.2.0, 1, latest
  based on epics-base 7.0.4, asyn 4.40.1 with FTDI support, autosave 5.10.1, calc 3.7.4, modbus 3.1, devSnmp 1.0.0.1, StreamDevice 2.8.15, drvAsynI2C 1.0.2, devGpio 1.0.6, iocStats 3.1.16, execute 1.0.0
  This images uses "FROM scratsh", this means the image contains only the IOC (no /bin/bash or anything else)
• 1.2.0-alpine, 1-alpine, latest-alpine
  based on epics-base 7.0.4, asyn 4.40.1 with FTDI support, autosave 5.10.1, calc 3.7.4, modbus 3.1, devSnmp 1.0.0.1, StreamDevice 2.8.15, drvAsynI2C 1.0.2, devGpio 1.0.6, iocStats 3.1.16, execute 1.0.0
  This images uses "FROM alpine", which means in addition to the IOC it provides the alpine linux system

• 2.1.2.0, 2, latest

• 4.6.3, 4, latest

• 4.6.3, 4, latest

4. The HMP4040 has two interfaces for remote control: USB and Ethernet. I will discuss both

3. Note in the file above: the first parameter of `drvAsynSerialPortConfigure` is an internal name for the newly created device handle. This has to be the same name we used in our "hameg_demo.sub" as value for the PORT macro.
   This startup script now creates a handle for the serial port at "/dev/ttyAMA0", configures this port and afterwards loads all needed records via the substitution file we created in the beginning.

4. Now start the docker container to run your IOC:
   

   docker run -dit -v ${HOME}/hameg_demo:/config --device /dev/ttyAMA0 paluma.rub.de/panda-ioc ./hameg_demo.cmd

6. Ethernet:

3. Now create a file called "hameg_demo.sub"

4. The HMP4040 has two interfaces for remote control: USB and Ethernet. I will discuss both
5. USB:

1. Now we need a startup script for our EPICS IOC, which opens the serial interface and configures it so we can talk to the HMP4040. The default settings of the HMP4040 is 8N1 at 9600baud.
   Create a file "hameg_demo.cmd" within the directory we created at the beginning:

3. Note in the file above: the first parameter of `drvAsynSerialPortConfigure` is an internal name for the newly created device handle. This has to be the same name we used in our "hameg_demo.sub" as value for the PORT macro.
   This startup script now creates a handle for the serial port at "/dev/ttyAMA0", configures this port and afterwards loads all needed records via the substitution file we created in the beginning.

4. Now start the docker container to run your IOC:
   

   docker run -dit -v ${HOME}/hameg_demo:/config --device /dev/ttyAMA0 paluma.rub.de/panda-ioc ./hameg_demo.cmd

6. Ethernet:

1. Now we need a startup script for our EPICS IOC, which opens a TCP/IP port to the HMP4040
   Create a file "hameg_demo.cmd" within the directory we created at the beginning:

1. Create a directory, where you will store the needed configuration files for our IOC

1. Now create the startup script for the IOC

1. Now start the docker container to run your IOC:

• Connect with same credentials as (current) user:
  `--user $(id -u):$(id -g)
• Connect being a member of e.g. group dialout:
  `--group-add: $(getent group | grep dialout | cut -d ":" -f 3)

4. Now start the docker container to run your IOC:
   

   docker run -dit -v ${HOME}/hameg_demo:/config --device /dev/ttyAMA0 paluma.rub.de/panda-ioc ./hameg_demo.cmd

6. Ethernet:

1. 1. 1. Now start the docker container to run your IOC:
         

mkdir ${HOME}/wiener_demo

1. Now create a file called "wiener_demo.sub" inside this newly created directory with the following content to get access to channels 'u0' and 'u1' of this device. The macro CRATE is either the hostname or the IP address of the MPOD crate.
   

1. Create a directory, where you will store the needed configuration files for our IOC
   

mkdir ${HOME}/hameg_demo

3. Now create a file called "hameg_demo.sub" inside this newly created directory with the following content to get access to all for channels of this device
   %CODE{"bash"}%

4. The HMP4040 has two interfaces for remote control: USB and Ethernet. I will discuss both
5. USB:

3. Note in the file above: the first parameter of `drvAsynSerialPortConfigure` is an internal name for the newly created device handle. This has to be the same name we used in our "hameg_demo.sub" as value for the PORT macro.
   This startup script now creates a handle for the serial port at "/dev/ttyAMA0", configures this port and afterwards loads all needed records via the substitution file we created in the beginning.

4. Now start the docker container to run your IOC:
   
   <

   docker run -dit -v ${HOME}/hameg_demo:/config --device /dev/ttyAMA0 paluma.rub.de/panda-ioc ./hameg_demo.cmd

5. Ethernet:

• Get Docker CE for Windows (chose "Linux Containers" when aksed which kind of containers you want to use on your system.)

1. Install Docker (refer to the links at the top of this page!)
2. Create a directory, where you will store the needed configuration files for our IOC
   

mkdir ${HOME}/hameg_demo

1. Now create a file called "hameg_demo.sub" inside this newly created directory with the following content to get access to all for channels of this device
   %CODE% file "/databases/hmp4040.db"

1. 1. 1. Now we need a startup script for our EPICS IOC, which opens the serial interface and configures it so we can talk to the HMP4040. The default settings of the HMP4040 is 8N1 at 9600baud.
         Create a file "hameg_demo.cmd" within the directory we created at the beginning:
         %CODE% #!/pandaIoc

1. 1. 1. Now start the docker container to run your IOC:
         

docker run -dit -v ${HOME}/hameg_demo:/config --device /dev/ttyAMA0 paluma.rub.de/panda-ioc ./hameg_demo.cmd

1. 1. 1. Now we need a startup script for our EPICS IOC, which opens a TCP/IP port to the HMP4040
         Create a file "hameg_demo.cmd" within the directory we created at the beginning:
         %CODE% #!/pandaIoc

1. 1. 1. Now start the docker container to run your IOC:
         

docker run -dit -v ${HOME}/hameg_demo:/config paluma.rub.de/panda-ioc ./hameg_demo.cmd

1. Install Docker (refer to the links at the top of this page!)
2. Create a directory, where you will store the needed configuration files for our IOC
   

mkdir ${HOME}/wiener_demo

1. Now create a file called "wiener_demo.sub" inside this newly created directory with the following content to get access to channels 'u0' and 'u1' of this device. The macro CRATE is either the hostname or the IP address of the MPOD crate.
   

file "/databases/WienerPL500.db"
{
        pattern { subsys, dev, sector, CRATE, CH }
        { LMD, MUPIX, P0:H1:D3:S2, 192.168.0.5, u0 }
        { LMD, MUPIX, P0:H1:D3:S2, 192.168.0.5, u1 }
}

1. Now create the startup script for the IOC
   %CODE% #!/pandaIoc

1. Now start the docker container to run your IOC:
   

docker run -dit -v ${HOME}/wiener_demo:/config paluma.rub.de/panda-ioc ./wiener_demo.cmd

Images

• asyn
• autosave
• calc
• modbus
• devSnmp
• StreamDevice
• drvAsynI2C
• devGpio

Usage

docker run -dit -v <PATH_ON_YOUR_HOST>:/config [OPTIONS] paluma.rub.de/panda-ioc ./<YOUR_ST.CMD>

#!/pandaIoc
epicsEnvSet( "STREAM_PROTOCOL_PATH", "/protocols" )
dbLoadDatabase( "/dbd/pandaIoc.dbd", 0, 0 )
pandaIoc_registerRecordDeviceDriver( pdbbase )

## Load device drivers and records at this point
## Load record instances
dbLoadRecords( "/config/dbExample2.db", "user=Test, no=1, scan='1 second'" )

OPTIONS:

• Connect to GPIOs (arm only):
  `-v /sys/class/gpio`
• Connect to I2C (arm only):
  `--device /dev/i2c-<NUM>`

• • CA: `-p 5064-5065:5064-5065 -p 5064-5065:5064-5065/udp`

Tags

• 1.0.0, 1, latest
  based on epics-base:7.0.3, asyn 4.36, autosave 5.10, calc 3.7.3, modbus 3.0, devSnmp 1.0.0.1, StreamDevice 2.8.9, drvAsynI2C 1.0.2, devGpio 1.0.6

Usage

docker run -d --network host -v <PATH_ON_HOST>:/config paluma.rub.de/ca-gateway -cip <CLIENT IP> -sip <SERVER IP> -server -pvlist <PVLIST_FILE> -access <ACCESS_FILE>

Tags

• 2.1.1.0, 2, latest

phoebus

Usage

docker run --network host -e DISPLAY=$DISPLAY --device /dev/dri -v <PATH_ON_HOST>:/home/panda-dcs/config -v /tmp/.X11-unix:/tmp/.X11-unix paluma.rub.de/phoebus -settings <SETTINGS_FILE>

Tags

• 4.6.0-SNAPSHOT, 4, latest

archive-engine

Usage

docker run -d -v <PATH_ON_HOST>:/home/panda-dcs/config -p 4812 paluma.rub.de/archive-engine -engine <ENGINE> -settings <SETTINGS_FILE>

Tags

• 4.6.0-SNAPSHOT, 4, latest

sncseq base image

Examples of using the panda-ioc

1. Now create a file called "hameg_demo.sub" inside this newly created directory with the following content to get access to all for channels of this device
   

   file "/databases/hmp4040.db"

1. 1. 1. Connect the HMP4040 to our PC via USB. Under linux, the device will show up under `/dev/ttyAMA0` or similar.
      2. Now we need a startup script for our EPICS IOC, which opens the serial interface and configures it so we can talk to the HMP4040. The default settings of the HMP4040 is 8N1 at 9600baud.
         Create a file "hameg_demo.cmd" within the directory we created at the beginning:
         

         #!/pandaIoc
         epicsEnvSet( "STREAM_PROTOCOL_PATH", "/protocols" )
         dbLoadDatabase( "/dbd/pandaIoc.dbd", 0, 0 )

1. 1. 1. Note in the file above: the first parameter of `drvAsynSerialPortConfigure` is an internal name for the newly created device handle. This has to be the same name we used in our "hameg_demo.sub" as value for the PORT macro.
         This startup script now creates a handle for the serial port at "/dev/ttyAMA0", configures this port and afterwards loads all needed records via the substitution file we created in the beginning.
      2. Now start the docker container to run your IOC:
         

         docker run -dit -v ${HOME}/hameg_demo:/config --device /dev/ttyAMA0 paluma.rub.de/panda-ioc ./hameg_demo.cmd

1. 1. 1. Now we need a startup script for our EPICS IOC, which opens a TCP/IP port to the HMP4040
         Create a file "hameg_demo.cmd" within the directory we created at the beginning:
         

         #!/pandaIoc
         epicsEnvSet( "STREAM_PROTOCOL_PATH", "/protocols" )
         dbLoadDatabase( "/dbd/pandaIoc.dbd", 0, 0 )

1. 1. 1. Note in the file above: the first parameter of `drvAsynIPPortConfigure` is an internal name for the newly created device handle. This has to be the same name we used in our "hameg_demo.sub" as value for the PORT macro.
         This startup script now creates a TCP/IP connection to the HMP4040 and loads all needed records via the substitution file we created in the beginning.
      2. Now start the docker container to run your IOC:
         

         docker run -dit -v ${HOME}/hameg_demo:/config paluma.rub.de/panda-ioc ./hameg_demo.cmd

1. Now create a file called "wiener_demo.sub" inside this newly created directory with the following content to get access to channels 'u0' and 'u1' of this device. The macro CRATE is either the hostname or the IP address of the MPOD crate.
   

   file "/databases/WienerPL500.db"
   {
    pattern { subsys, dev, sector, CRATE, CH }
    { LMD, MUPIX, P0:H1:D3:S2, 192.168.0.5, u0 }
    { LMD, MUPIX, P0:H1:D3:S2, 192.168.0.5, u1 }
   }

2. Now create the startup script for the IOC
   

   #!/pandaIoc

1. Now start the docker container to run your IOC:
   

   docker run -dit -v ${HOME}/wiener_demo:/config paluma.rub.de/panda-ioc ./wiener_demo.cmd

   ---

• Docker Volumes

docker run -dit [VOLUMES] [OPTIONS] paluma.rub.de/panda-ioc ./[ST.CMD]

Volumes:

• /home/panda-dcs/protocols: This directory contains the protocol files for StreamDevice (if this directory is empty, all protocol files from our git repo are copied here)
• /home/panda-dcs/databases: This directory contains the database files for the IOC (if this directory is empty, all database files from our git repo are copied here)

OPTIONS can be:

• Connect to serial devices:
  `--device /dev/<DEVICENAME>`

• Connect to GPIOs (arm only):
  `-v /sys/class/gpio --group-add $(grep gpio /etc/group | awk -F':' '{ print $3 }')`
  (add panda-dcs user to host's gpio group, does not work in compose files!)
• Connect to I2C (arm only):
  `--device /dev/i2c-<NUM> --group-add $(grep i2c /etc/group | awk -F':' '{ print $3 }')`
  (add panda-dcs user to host's i2c group, does not work in compose files!)
• Connect to CAN bus devices:
  `--network host`

• • CA: `-p 5064-5065:5064-5065 -p 5064-5065:5064-5065/udp` (might be sufficient to publish CAS ports)
  • PVaccess: `--network host`

• • CA: `-e EPICS_CA_AUTO_ADDR_LIST=no -e EPICS_CA_ADDR_LIST=<LIST OF IP ADDRESSES>`
    UDP broadcasts are not forwarded by Docker's default network (bridge). Setting `EPICS_CA_ADDR_LIST` to the broadcast address (e.g. `192.168.0.255`) does not work
    Alternatively use `--network host`
  • PVaccess: `--network host`

docker run -d --network host -v <PATH_ON_HOST>:/home/panda-dcs/config paluma.rub.de/ca-gateway -cip <CLIENT IP> -sip <SERVER IP> -server -pvlist <PVLIST_FILE> -access <ACCESS_FILE>

epics-base

panda-ioc

• 7.0.3, 7, latest
  Based on "epics-base:7.0.3", asyn 4.36, autosave 5.10, calc 3.7.3 modbus 3.0, snmp 1.0.0.1, stream 2.8.9
• 7.0.2
  Based on "epics-base:7.0.2", asyn 4.36, autosave 5.10, calc 3.7.3 modbus 3.0, snmp 1.0.0.1, stream 2.8.9
• 7.0.2-raspi, 7-raspi, raspi-latest
  Based on "epics-base:7.0.2-raspi", asyn 4.36, autosave 5.10, calc 3.7.3 modbus 3.0, snmp 1.0.0.1, stream 2.8.9, drvasyni2c 1.0.2, devgpio 1.0.6
• 7.0.2-beagleboneblack, 7-bbb, bbb-latest
  Based on "epics-base:7.0.2-beagleboneblack", asyn 4.36, autosave 5.10, calc 3.7.3 modbus 3.0, snmp 1.0.0.1, stream 2.8.9, drvasyni2c 1.0.2, devgpio 1.0.6

ca-gateway

• 7.0.3, 7, latest
  Based on "epics-base:7.0.3", CA-Gateway R2.1.1.0
• 7.0.2
  Based on "epics-base:7.0.2", CA-Gateway R2.1.1.0

Phoebus

Archive-Engine

• Get Docker CE for Windows

docker pull paluma.rub.de/<IMAGENAME>

Usage

panda-ioc

• /home/panda-dcs/protocols: This directory contains the protocol files for StreamDevice (if this directory is empty, all protocol files from git repo are copied here)

ca-gateway

Phoebus

Archive-Engine

1. Now start the docker container to run your IOC:
   

   docker run -dit -v ${HOME}/wiener_demo:/home/panda-dcs/config paluma.rub.de/panda-ioc ./wiener_demo.cmd

   ---

List of Images and Tags

epics-base

• 7.0.3
  EPICS base 7.0.3, based on Debian-Buster
• 7.0.2
  EPICS base 7.0.2, based on Debian-Stretch
• 7.0.2-raspi
  EPICS base 7.0.2, based on Debian-Stretch, cross-build for usage on the Raspberry pi
• 7.0.2-beagleboneblack
  EPICS base 7.0.2, based on Debian-Stretch, cross-build for usage on the BeagleBone Black

panda-ioc

• 7.0.3, 7, latest
  Based on "epics-base:7.0.3"
• 7.0.2
  Based on "epics-base:7.0.2"
• 7.0.2-raspi, 7-raspi, raspi-latest
  Based on "epics-base:7.0.2-raspi"
• 7.0.2-beagleboneblack, 7-bbb, bbb-latest
  Based on "epics-base:7.0.2-beagleboneblack"

ca-gateway

• 7.0.3, 7, latest
  Based on "epics-base:7.0.3"
• 7.0.2
  Based on "epics-base:7.0.2"

Phoebus

• openjdk11, latest

Archive-Engine

• openjdk11, latest

  ---

Wiener PL5xx and Wiener MPOD LV power supplies (SNMP)

1. First we need to install Docker CE (refer to the links at the top of this page!)
2. Create a directory, where we will store some files needed for our IOC

   mkdir ${HOME}/wiener_demo

3. Connect the Wiener MPOD (or PL5xx) via ethernet to your PC and look up the IP address of the device (e.g. 192.168.0.5)
4. Now create a file called "wiener_demo.sub" inside this newly created directory with the following content to get access to channels 'u0' and 'u1' of this device. The macro CRATE is either the hostname or the IP address of the MPOD crate.
   

   file "/epics/databases/WienerPL500.db"
   {
    pattern { subsys, dev, sector, CRATE, CH }
    { LMD, MUPIX, P0:H1:D3:S2, 192.168.0.5, u0 }
    { LMD, MUPIX, P0:H1:D3:S2, 192.168.0.5, u1 }
   }

5. Now create the startup script for the IOC
   

   #!/epics/ioc/bin/linux-x86_64/pandaIoc
   
   epicsEnvSet( "ARCH", "linux-x86_64" )
   epicsEnvSet( "TOP",  "/epics/ioc" )
   epicsEnvSet( "WCR",  "guru WIENER-CRATE-MIB::" )

1. Now start the docker container to run your IOC:
   

   docker run -dit -v ${HOME}/wiener_demo:/home/panda-dcs/config paluma.rub.de/panda-ioc ./wiener_demo.cmd

Examples

Hameg HMP4040 LV Power Supply

1. First we need to install Docker CE (refer to the links at the top of this page!)
2. Create a directory, where we will store some files needed for our IOC

   mkdir ${HOME}/hameg_demo

3. Now create a file called "hameg_demo.sub" inside this newly created directory with the following content to get access to all for channels of this device
   

   file "/epics/databases/hmp4040.db"
   {
    pattern { CHAN, PORT }
      { 0, hmp_1 }
      { 1, hmp_1 }
      { 2, hmp_1 }
      { 3, hmp_1 }
   }

4. The HMP4040 has two interfaces for remote control: USB and Ethernet. I will discuss both
   1. USB:
      1. Connect the HMP4040 to our PC via USB. Under linux, the device will show up under `/dev/ttyAMA0` or similar.
      2. Now we need a startup script for our EPICS IOC, which opens the serial interface and configures it so we can talk to the HMP4040. The default settings of the HMP4040 is 8N1 at 9600baud.
         Create a file "hameg_demo.cmd" within the directory we created at the beginning:
         

         #!/epics/ioc/bin/linux-x86_64/pandaIoc
         
         epicsEnvSet( "ARCH",                 "linux-x86_64" )
         epicsEnvSet( "TOP",                  "/epics/ioc" )
         epicsEnvSet( "STREAM_PROTOCOL_PATH", "/home/panda-dcs/protocols" )
         
         ## Register all support components
         dbLoadDatabase( "$(TOP)/dbd/pandaIoc.dbd", 0, 0 )
         pandaIoc_registerRecordDeviceDriver( pdbbase )
         
         ## Load drivers
         ## Connect to R&S HMP4040 with HO732 via usb-serial interface
         drvAsynSerialPortConfigure( "hmp_1", "/dev/ttyAMA0", 0, 0, 0 )
         asynSetOption( "hmp_1", 0, "baud", "9600" )
         asynSetOption( "hmp_1", 0, "bits", "8" )
         asynSetOption( "hmp_1", 0, "parity", "none" )
         asynSetOption( "hmp_1", 0, "stop", "1" )
         asynSetOption( "hmp_1", 0, "clocal", "Y" )
         asynSetOption( "hmp_1", 0, "crtscts", "N" )
         asynSetOption( "hmp_1", 0, "ixon", "N" )
         asynSetOption( "hmp_1", 0, "ixoff", "N" )
         asynSetOption( "hmp_1", 0, "ixany", "N" )
         
         ## Load record instances
         dbLoadTemplate ("/home/panda-dcs/config/hameg_demo.sub" )
         
         iocInit()

      3. Note in the file above: the first parameter of `drvAsynSerialPortConfigure` is an internal name for the newly created device handle. This has to be the same name we used in our "hameg_demo.sub" as value for the PORT macro.
         This startup script now creates a handle for the serial port at "/dev/ttyAMA0", configures this port and afterwards loads all needed records via the substitution file we created in the beginning.
      4. Now start the docker container to run your IOC:
         

         docker run -dit -v ${HOME}/hameg_demo:/home/panda-dcs/config --device /dev/ttyAMA0 paluma.rub.de/panda-ioc ./hameg_demo.cmd

   2. Ethernet:
      1. Connect the HMP4040 to our PC via Ethernet cable. You need a DHCP server and need to get the IP address assigned to the HMP4040 (e.g. 192.168.0.5)
      2. Now we need a startup script for our EPICS IOC, which opens a TCP/IP port to the HMP4040
         Create a file "hameg_demo.cmd" within the directory we created at the beginning:
         

         #!/epics/ioc/bin/linux-x86_64/pandaIoc
         
         epicsEnvSet( "ARCH",                 "linux-x86_64" )
         epicsEnvSet( "TOP",                  "/epics/ioc" )
         epicsEnvSet( "STREAM_PROTOCOL_PATH", "/home/panda-dcs/protocols" )
         
         ## Register all support components
         dbLoadDatabase( "$(TOP)/dbd/pandaIoc.dbd", 0, 0 )
         pandaIoc_registerRecordDeviceDriver( pdbbase )
         
         ## Load drivers
         ## Connect to R&S HMP4040 with HO732 via usb-serial interface
         drvAsynIPPortConfigure( "hmp_1", "192.168.0.5:5025 TCP", 0, 0, 0 )
         
         ## Load record instances
         dbLoadTemplate ("/home/panda-dcs/config/hameg_demo.sub" )
         
         iocInit()

      3. Note in the file above: the first parameter of `drvAsynIPPortConfigure` is an internal name for the newly created device handle. This has to be the same name we used in our "hameg_demo.sub" as value for the PORT macro.
         This startup script now creates a TCP/IP connection to the HMP4040 and loads all needed records via the substitution file we created in the beginning.
      4. Now start the docker container to run your IOC:
         

         docker run -dit -v ${HOME}/hameg_demo:/home/panda-dcs/config paluma.rub.de/panda-ioc ./hameg_demo.cmd

• Get Docker CE for Wondows

• openjdk11, latest

  ---

docker run -dit -v ${PWD}/ioc-config:/home/panda-dcs/config [OPTIONS] paluma.rub.de/panda-ioc ./[ST.CMD]

• /home/panda-dcs/config: This directory should contain the substitution files and start up scripts for your IOC.
• /home/panda-dcs/protocols: This directory contains the protocol files for StreamDevice (if this directory is empty, all protocol files from git repo are copied here)
• /home/panda-dcs/databases: This directory contains the database files for the IOC (if this directory is empty, all database files from git repo are copied here)

docker run -d --network host -v ${PWD}/ioc-config:/home/panda-dcs/config paluma.rub.de/ca-gateway -cip <CLIENT IP> -sip <SERVER IP> -server -pvlist <PVLIST_FILE> -access <ACCESS_FILE>

docker run --network host -e DISPLAY=$DISPLAY --device /dev/dri -v ${PWD}/phoebus-config:/home/panda-dcs/config -v /tmp/.X11-unix:/tmp/.X11-unix paluma.rub.de/phoebus -settings <SETTINGS_FILE>

docker run -d -v ${PWD}/phoebus-config:/home/panda-dcs/config -p 4812:4812 paluma.rub.de/archive-engine -engine Test -settings <SETTINGS_FILE>

• 7.0.3
  EPICS base 7.0.3, based on Debian-Buster
• 7.0.2
  EPICS base 7.0.2, based on Debian-Stretch
• 7.0.2-raspi
  EPICS base 7.0.2, based on Debian-Stretch, cross-build for usage on the Raspberry pi
• 7.0.2-beagleboneblack
  EPICS base 7.0.2, based on Debian-Stretch, cross-build for usage on the BeagleBone Black

• 7.0.3, 7, latest
  Based on "epics-base:7.0.3"
• 7.0.2
  Based on "epics-base:7.0.2"
• 7.0.2-raspi, 7-raspi, raspi-latest
  Based on "epics-base:7.0.2-raspi"
• 7.0.2-beagleboneblack, 7-bbb, bbb-latest
  Based on "epics-base:7.0.2-beagleboneblack"

• 7.0.3, 7, latest
  Based on "epics-base:7.0.3"
• 7.0.2
  Based on "epics-base:7.0.2"

• openjdk11, latest

• openjdk11, latest

• 7.0.3
  Container with EPICS base 7.0.3 installed, based on Debian-Buster

• 7.0.2-raspi
  Container with EPICS base 7.0.2 installed, based on Debian-Stretch, cross-build for usage on the Raspberry pi
• 7.0.2-beagleboneblack
  Container with EPICS base 7.0.2 installed, based on Debian-Stretch, cross-build for usage on the BeagleBone Black

docker run -dit -v ${TOP}/ioc-config:/home/panda-dcs/config [OPTIONS] paluma.rub.de/panda-ioc ./hameg_demo.cmd

docker run -d --network host -v ${TOP}/ioc-config:/home/panda-dcs/config paluma.rub.de/ca-gateway -cip <CLIENT IP> -sip <SERVER IP> -server -pvlist gw_pvlist -access gw_access

docker run --network host -e DISPLAY=$DISPLAY --device /dev/dri -v ${TOP}/phoebus-config:/home/panda-dcs/config -v /tmp/.X11-unix:/tmp/.X11-unix paluma.rub.de/phoebus -settings phoebus-settings.ini

docker run -d -v ${TOP}/phoebus-config:/home/panda-dcs/config -p 4812:4812 paluma.rub.de/archive-engine -engine Test -settings archiver-settings.ini