The EL51xx series covers incremental encoder interfaces:
Normally, the incremental encoder interfaces do not require any SDO configuration. Therefore, ecmccomp/applyComponent.cmd, which is often needed after ecmccfg/addSlave.cmd, is in most cases not required.
Make sure you use the correct slave type when adding the slave. Some slaves have the same product ID but totally different process data, which can result in the slave not going into OP mode and ecmc failing to start with a timeout.
For example, EL5101-0010 and EL5101-0011 have the same product ID but very different process data. So if an EL5101-0011 is added to the configuration but the actual slave connected is an EL5101-0010, the initial product ID verification will not catch the mismatch. Later, the slave will not go online since the process data is wrong.
The issue can be diagnosed by checking the dmesg logs:
# first login to host (ecmc server)
sudo dmesg
Configuring the wrong process data will lead to an error message “* EtherCAT * Invalid input configuration”
The solution is to use the correct configuration script.
This is commonly used at PSI (even though the EL5112 should be the standard choice). For configuration, use the EL5101-0010 configuration script:
${SCRIPTEXEC} ${ecmccfg_DIR}addSlave.cmd, "SLAVE_ID=16, HW_DESC=EL5101-0010"
This is an oversampling slave. Use the EL5101-0011 configuration script with an optional NELM which defines the level of oversampling:
Example: Add an EL5101-0011, with 100 levels of oversampling:
${SCRIPTEXEC} ${ecmccfg_DIR}addSlave.cmd, "SLAVE_ID=16, HW_DESC=EL5101-0011, NELM=100"
In the above example, for each EtherCAT frame, an array of 100 elements will be transferred. If the EtherCAT rate is 1kHz, then the incremental data will be sampled at 100kHz (which is also the maximum rate for this terminal).
NELM cannot be freely defined; depending on the EtherCAT rate, different NELM values will be accepted. Consult the EL5101-0011 manual for more information.
Normally, NELM needs to be an integer value, like 10, 20, 50, 100.
This is the PSI standard incremental encoder interface. The terminal can be used as one channel if index pulse needs to be connected or two channel if only A and B pulse trains are needed.
For 1 channel operation with index pulse, use the EL5112_ABC configuration script and for two channel, the EL5112_AB script:
# One channel:
${SCRIPTEXEC} ${ecmccfg_DIR}addSlave.cmd, "SLAVE_ID=16, HW_DESC=EL5112_ABC"
# Two channel:
${SCRIPTEXEC} ${ecmccfg_DIR}addSlave.cmd, "SLAVE_ID=16, HW_DESC=EL5112_AB"
This terminal supports setting cam/trigger outputs at certain counter values (for predefined time and direction).
8 predefined threshold counter values can be entered and configured switch outputs on or off. These thresholds can also be accessed/updated during runtime.
Depending on how the terminal should be used, the following startup scripts exist:
# EL5131: Normal incremental encoder operation:
${SCRIPTEXEC} ${ecmccfg_DIR}addSlave.cmd, "SLAVE_ID=16, HW_DESC=EL5131"
# EL5131_DC: Normal incremental encoder and DC clock (access to timestamps)
${SCRIPTEXEC} ${ecmccfg_DIR}addSlave.cmd, "SLAVE_ID=16, HW_DESC=EL5131_DC"
# EL5131_DC_TRG: Incremental encoder, access to timestamps and configuration of thresholds for outputs/triggering.
${SCRIPTEXEC} ${ecmccfg_DIR}addSlave.cmd, "SLAVE_ID=16, HW_DESC=EL5131_DC"
See the hardware diagnostics page.