Versions Compared

Old Version 19

changes.mady.by.user Unknown User (ababbitt)

Saved on

compared with

New Version 20

changes.mady.by.user Unknown User (ababbitt)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • scannerStartup.sh (where should we put a "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)

...