You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 19 Next »

 

 Set-up of cpu and ioc boot directories:

  1. Create  the $IOC_DATA directory for your cpu and iocs  as follows:
    1. cd $IOC_DATA
    2. mkdir cpu-<area>-<subsystem-prefix><2-digit#>
    3. mkdir  sioc-<area>-<subsystem-prefix><2-digit#>
      1. cd sioc-<area>-<subsystem-prefix><2-digit#>
      2. mkdir autossave autosave-req iocInfor archive restore
  2.  Create the $EPICS_IOCS cpu and ioc boot directories
    1. cd $EPICS_IOCS
    2. mkdir cpu-<area>-<subsystem-prefix><2-digit#>  
      1. cd cpu-<area>-<subsystem-prefix><2-digit#>
      2. Setup relative symbolic links to the common startup script and EPICS version:.
        1. ln -s ../common/st.cmd.linuxRT.cpu startup.cmd
        2. ln -s ../common/bin/<epics base version> epicsSpecificRelease
      3. Generate a kernel-modules.cmd file
        1. for examples click  here.
    3. mkdir  sioc-<area>-<subsystem-prefix><2-digit#>
      1. cd sioc-<area>-<subsystem-prefix><2-digit#>
      2. cp ../template/st.cmd.linuxRT startup.cmd
      3. edit startup.cmd and replace <ioc> with your ioc name.
      4. cp ../template/screenrc and replace <ioc> with your ioc name.
      5. edit screenrc and replace <ioc> with your ioc name.
      6. Please note that if the location of your IOC Application st.cmd file is non-standard then change EPICS_IOC_APP path in startup.cmd
      7. Setup a relative symbolic link to the TOP of the IOC Application release
        1. ln -s ../../iocTop/<app>/<version> iocSpecificRelease
    4. Add cpu and IOC to $EPICS_IOCS/screeniocs   
      1. Please note that the  $EPICS file is a symbolic link, so cd to the appropriate directory and edit this file
      2. add line for cpu
        format:  cpu-<area>-<subsystem-prefix><2-digit #>      <ts>   <ts port #t>   <screen  host>   [ # comment]
      3. add line for each ioc
        format:  sioc-<area>-<subsystem prefix><2-digit #>  cpu-<area>-<subsystem-prefix><2-digit #>    <account>   [ # comment]
      4. The "comment" field in screeeniocsis optional and must be precede but  "#".

  3. IOC Applications with RT constraints:

    1. Create script <app>/iocBoot/<ioc>/rtPriortiesSetup.cmd  to set real-time priorities for threads
    2. Load rtPriortiesSetup.cmd from <app>/iocBoot/<ioc>/st.cmd 

LinuxRT Upgrade IOC Application release:

How-to start your linuxRT EPICS Application:

  • Start ioc from the Linux:
    • viocRestart -v <ioc>
       
  • Start ioc from Linux manually in foreground:
    • ssh laci@<cpu>   -or-  iocConsole <cpu>       (from facet server use flaci)
    • check if ioc is running : screen -ls
    • If it's not running then manually start ioc.
       
    • cd <app>/iocBoot/<ioc>
    • ./st.cmd   

How-to boot a linuxRT ioc from the <cpu>:  

The following scripts are located under the directory $IOC/common and should be in PATH

  1.  In the foreground w/screens 
    • linuxRT_viocConsole.sh  <ioc>
  2. In the background w/screens
    •  linuxRT_startup_vioc.sh <ioc>
  3. In the foreground without screens
    • linuxRT_startupConsole.sh <ioc>

How-to use screen program:

  • ctrl a d : detach from the screen session
  • ctrl a [ : scroll up through the start-up messages.
  • View all vioc's on host  cpu:
    • logged in as laci  or flaci for FACET iocs
    • screen -ls  
  • Attach to vioc: screen -r <ioc>
  • Attaching to a linuxRT screen session multiple times with  "laci"concurrently:  (Note: from FACET use flaci)
    screen  -x <ioc>

  • Note: The "screen" program supports multi-display mode. When you attach an existing screen session, you can use "-x". It allows an user to attach to "a not detached screen session." The -r option allows a user to attach to a "detached screen session".


Additional References:


  • No labels