<This page is currently under reviewactive development/revision. Please contact Alisha Babbitt (ababbitt@slaccontact Jesus Vasquez <jvasquez@slac.stanford.edu) > for more information or questions.>
...
- EtherCAT Resources & Reference Material
- linuxRT PC Set-up
- Configuring the $IOC/vioc-<>-<> Directorysioc-<area>-<subsystem##> Directory where ## is a 2-digit number 01-99.
- EtherCAT linuxRT Configuration
- EtherCAT Template for Creating Epics Application
- Configuring EtherCAT Epics Application
- Debugging Tips
...
- For new users, please reference the following page: Diskless Boot of LinuxRT or Centos7 - Quick Start-up For New UsersHighly Highly recommend viewing this diagram: LinuxRT_Diagram
Verification checks on linuxRT machines:
Table 1
| Facility | LinuxRT Account | LinuxRT Group | Comment |
|---|
| Development | laci | lcls | |
| LCLS | laci | lcls | |
| LCLS-II | | | not yet available |
| FACET | flaci | facet | linuxRT is built with laci as the default account, users must add facet group, user and password |
| Test-Facility | acctf | ? | linuxRT is built with laci as the default account, users must add test-facility group, user and password |
Verification checks on linuxRT machines:
- Please see $IOC/Please see $IOC/cpu-<bld>-<name>/README on instructions on how to power cycle machines remotely through the use of ipmi commands
- Once you set-up your linuxRT machine and boot up on development for instance, log in as laci to into laci on your linuxRT system (ref: Table 1). ( ssh laci@cpu-<bld>-<name>)
- Test if your machine is running real-time linux using uname -a
...
# =============================================================== # Define kernel module driver location # === ============================================================ PACKAGE_TOP=/afs/slac/g/lcls/package === KERNEL_DRIVER_HOME=$PACKAGE_TOP/linuxKernel_Modules ETHERCAT_DRIVER=$KERNEL_DRIVER_HOME/ethercat/buildroot-2015.02-x86_64 |
|---|
...
- Another helpful ethercat command line took is ethercat master
Configuring the $IOC/viocsioc-<>-<> Directory
The $IOC/vioc-<>-<> directory created for this EtherCAT application needs the follow items:
- scannerStartup.sh (where should we put a "master" scannerStartup.sh for people to copy)"master" scannerStartup.sh for people to copy/point to)
- Proposal: put generic scannerStartup.sh under $IOC/common/ethercat. Script has been modified to pass in the vioc name from when the script is called from the kernel-modules.cmd
- so vioc specific information (for vioc-ltu0-mc01) was moved to the kernel-modules.cmd => have to think about use case where multiple subsystems share cpucpu (see above solution)
- OR do we keep it in kernel-modules.cmd (this should be apart of the linuxRT discussion)
- Create a bin directory (currently under discussion to rename this "bin" directory to avoid confusion)
- Proposal: rename "bin" to "scanner" and use symbolic links to point to scanner binary and scanner.xml in epics application
- In the bin directory, create a symbolic link "scanner" that points to your scanner binary in your epics application (<top>/bin/linuxRT_glibc-x68_64/scanner)
OH! scanner binary is NOT specific to your application. Should point to the package area.
- In the bin directory, create a symbolic link "scanner.xml" that points to your scanner.xml in your epics application (<top>/etc/scanner.xml)
...
