Configuration

The EL6740-0010 acts as an Interbus slave for linking process data with an Interbus strand or reading process data from the Interbus telegrams. The EL6740-0010 first has to be configured via EtherCAT so that the Interbus master can detect it.

Proceed as follows to configure the EL6740-0010:

Insert the terminal manually into the configuration tree or scan the EtherCAT strand with the EL6740-0010. EL6740-0010 appears without process data, see Fig. EL6740-0010. In this state the EL6740-0010 remains in SAFE-OP.

Manually add the required number of process data for this Interbus slave by right-clicking on inputs and outputs (Fig. Appending process data + Appending process data, number).

Configuration 3: — Adding process data, number

Note regarding process data

The process data of the EL6740-0010 must have the following characteristics:

Only WORD variables (16 bit) are permitted
Up to 32 words input variables and 32 words output variables can be created

After reloading the EtherCAT device the EL6740-0010 is ready for operation as an Interbus slave and reaches the OP state.

Configuration 5: — Configured EL6740-0010

The Interbus master can now detect it as slave with the configured process data.

EL6740-0010 "INIT" status

SUPI reset with each EL6740-0010 init; an error occurs at the IB, which must be acknowledged there. While the EL6740-0010 is in init state the SUPI remains in reset.

IBS status

As long as the EL6740-0010 is not in OP status, the terminal signals /STATERR on the Interbus. In this case, no valid process data inputs are available for the IBS.
/STATERR is also reported if the SyncManager watchdog of the EL6740-0010 drops, e.g. due to a fault in the EtherCAT communication.

Status word of the EL6740-0010

Error messages with the following values are reported to the status input of the EL6740-0010:

0x2000: SUPI station Error,
No data have been sent to the Interbus

0x4000: SUPI invalid data received from Interbus
Invalid data receives from the Interbus