Versions Compared

Old Version 13

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

Saved on

compared with

New Version 14

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

Saved on

Key

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

...

  • Under <top>/configure/RELEASE, remove any modules you are not using for your application (the slac_ethercat is a motion control based example)

  • Under <top>/<app_name>/Db/Makefile, only include the templates to be installed that you are using (each slave device should have an associated template)
    Here is an example of using the slac_template for a non-motor application:

     ## Install Protocol File:

     #DB_INSTALLS += $(CAENN1470)/db/caenN1470.proto

     ## ====================================================

    DB_INSTALL INSTALLS += $(ECASYN)/db/EK1101.template

    DB_INSTALL S+= $(ECASYN)/db/EL3202-0010.template

    #DB_INSTALLS +=$(MOTOR)/db/basic_asyn_motor.db

    # 

    DB_INSTALLS += $(ASYN)/db/asynRecord.db

    NOTE: Should be using DB_INSTALLS to be using the common templates found in the epics modules (want to avoid unnecessary copy and paste of template files or database records)

  • <top>/iocBoot/vioc-<>-<>/st.cmd
    Update the st.cmd to only load the database records specific to your application. The st.cmd for all EtherCAT applications must include the following items.  (Please reference the st.cmd file after using the slac_ethercat template for additional motion control related steps.)

...