Page History

...

1. Create the $IOC_DATA directory for your cpu and iocs as follows:
1. cd $IOC_DATA
2.  Create the $EPICS_IOCS cpu and ioc boot directories
   1. cd $EPICS_IOCS
   2. mkdir cpu-<area>-<subsystem-prefix><2-digit#>  
   3. mkdir  sioc-<area>-<subsystem-prefix><2-digit#>
3. Setup cpu directory files
   1. cd cpu-<area>-<subsystem-prefix><2-digit#>
      Original Method: (steps 3b and 3c)
   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 the file kernel-module.cmd. This file load kernels modules and drivers: kernel-modules.cmd
      for examples click  here.
      New Method: (steps 3d and 3e)
   4. Setup relative symbolic like to the TOP of the IOC Application
      1. ln -s ../../iocTop/<app> iocSpecificRelease
      2.  
4. Setup ioc directory files
1. cd sioc-<area>-<subsystem-prefix><2-
digit#>
1. digit# 
2. copy the ioc startup.cmd script from  $EPICS_IOCS/
template
1. templat
 for
1. for linuxRT running iocsh:    cp ../template/startup.cmd.linuxRT          startup.cmd
2. for  linuxRT running cexp:     cp ../template/startup.cmd.linuxRT.cexp  startup.
cmdstartup
1. cm
edit 
1. edit startup.cmd
 replace
1. 1. replace <ioc>  with your ioc name and for cexp replace <facility>
 change
1. 1. change path of the EPICS_IOC_APP if your st.cmd file is in a non-standard location.
2. cp ../template/screenrc   screenrc
3. edit screenrc and replace <ioc> with your ioc name
.
2. Setup a relative symbolic link to the TOP of the IOC Application release.

1. 1. ln -s ../../iocTop/<app>/<version> iocSpecificRelease
2. Modify $EPICS_IOCS/screeniocs    – Please note that this is a symbolic link to a CVS file
1. verify that the file in use has not been modified without being committed.
   1. cd $EPICS_IOCS/All/<facility>   , where facility is Dev,Prod,facet,acctest
   2. cvs diff -r HEAD screeniocs
   3. if there are issues, then send email to whoever made the change or to controls-software that you are about to update this file and uncommitted edits will be lost, so please commit your changes to CVS.  If you don't get a response,  you can either add the changes to CVS in addition to yours or just add yours.
      
2. check out screeniocs from CVS into your work area
1. cd
2. cd <work>
   cvs co epics/iocCommon/All/<facility>   , where facility is Dev,Prod,facet,acctest
1. cd epics/iocCommon/All/<facility>/screeniocs
2. edit screeniocs
   
1. add line for cpu
   format:  cpu-<area>-<subsystem-prefix><2-digit #>      <ts>   <ts port #t>   <screen  host>   [ # comment]
2. add line for each ioc
   format:  sioc-<area>-<subsystem prefix><2-digit #>  cpu-<area>-<subsystem-prefix><2-digit #>    <account>   [ # comment]
3. The "comment" field in  screeeniocs  is optional and must be precede but  "#".
3. commit your changes of screeniocs to CVS  as follows:
   1.  cvs commit  -m "added cpu and ioc blah" screeniocs
4. update the screeniocs file in use
   1. cd $EPICS_IOCS/All/<facility>
   2.  rm -f screeniocs
   3. cvs update screeniocs
       

...