...
- Send email to Ken Brobeck requesting:
- create controls infrastructure for a new linuxRT linuxRT CPU and / or IOC to a specific facility production server.
- includes $IOC_DATA/<cpu,ioc> directories
- includes $IOC_DATA/<ioc>/<autosave,autosave-req,restore,iocInfo,archive> directories
- add CPU boot information to the DHCP configuration file, and reboot the DHCP server. Ken will need the following details:
- Which facility the CPU will boot (e.g. facet, lcls, lcls2, testfac). Thins This indicates the path to the startup.cmd script and the DHCP server.
- MAC Address of the CPU
- The CPU EPICS target architecture (e.g. linuxRT-x86,linuxRT-x86_64,etc)
- Proceed to Development Step Development Step #3
Development: dev
- Create the $IOC_DATA directory for your cpu and iocs iocs as follows:
- cd $IOC_DATDATA
- Create the $EPICS_IOCS cpu and ioc boot directories
- cd $EPICS_IOCS
- mkdir cpu-<area>-<subsystem-prefix><2-digit#>
- mkdir sioc-<area>-<subsystem-prefix><2-digit#>
- Setup cpu directory files
- cd cpu-<area>-<subsystem-prefix><2-digit#>
- Setup relative symbolic links to the common startup script and EPICS version:.
- ln -s ../common/st.cmd.linuxRT.cpu startupcpu startup.cmd
- ln -s ../common/bin/<epics base version> epicsSpecificRelease epicsSpecificRelease
- Generate the file kernel-module.cmd. This file load kernels modules and drivers: kernel-modules.cmd
- for examples click here.
- Setup ioc directory files
- cd sioc-<area>-<subsystem-prefix><2-digit#>
- copy the ioc startup.cmd script from $EPICS_IOCS/template
- for linuxRT running iocsh: cp ../template/startup.cmd.linuxRT startup.cmd
- for linuxRT running cexp: cp ../template/startup.cmd.linuxRT.cexp startup.cmd
- edit startup.cmd
- replace <ioc> with your ioc name and for cexp replace <facility>
- change path of the EPICS_IOC_APP in if your st,.cmd file is in a non-standard location.
- cp ../template/screenrc screenrc
- edit screenrc and replace <ioc> with your ioc name.
- Setup a relative symbolic link to the TOP of the IOC Application release.
- ln -s ../../iocTop/<app>/<version> iocSpecificRelease
- Modify $EPICS_IOCS/screeniocs – Please note that this is a symbolic link to this CVSed a CVS file:
- verify that the file in use has not been modified without being committed.
- cd $EPICS_IOCS/facility
- cvs diff -r HEAD screeniocs
- if these is an 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.
- check out screeniocs from CVS into your work area
- cd
- cd <work>
cvs co epics/iocCommon/<facility> , where facility is Dev,Prod,facet,acctest - cd epics/iocCommon/<facility>/screeniocs
- edit screeniocs
- add line for cpu
format: cpu-<area>-<subsystem-prefix><2-digit #> <ts> <ts port #t> <screen host> [ # comment] - add line for each ioc
format: sioc-<area>-<subsystem prefix><2-digit #> cpu-<area>-<subsystem-prefix><2-digit #> <account> [ # comment] - The "comment" field in screeeniocs is optional and must be precede but "#".
- commit your changes of screeniocs to CVS as follows:
- cvs commit -m "added cpu and ioc blah" screeniocs
- update the screeniocs file in use
- cd $EPICS_IOCS/<facility>
- rm -f screeniocs
- cvs update screeniocs
...
{"serverDuration": 73, "requestCorrelationId": "58bb7d75a7ec9513"}