Tab 'EtherCAT Slave - Online'

Tab 'EtherCAT Slave - Online'

Object: EtherCAT Slave

The tab provides slave status information and functions for the file transfer to the slave via EtherCAT (FoE).

Requirement: The expert settings for the slave are selected and the application is logged in to the controller.

Table 363: “State machine”
“Init”	Use for debugging purposes
“Boot Strap”	The slave is switched to Bootstrap Mode. Required if firmware files should be transferred to or from the slave
“Pre-Op”	Use for debugging purposes
“Safe-Op”	Use for debugging purposes
“Op”	Use for debugging purposes
“Current status”
“Requested status”

Table 364: “DLL status”
“Port A” “Port B” “Port C” “Port D”	`‎No Carrier / Open‎`: No carrier signal exists at the port, but the port is open. `‎No Carrier / Closed‎`: No carrier signal exists at the port and the port is closed. `‎Carrier / Open‎`: A carrier signal exists at the port and the port is open. `‎Carrier / Closed‎`: A carrier signal exists at the port, but the port is closed. Note: If the function is not supported, then the status can be hidden.

Table 365: “File Access over EtherCAT”
“Download”	Download of firmware files A dialog opens to save the firmware file. In this dialog, the input of a string as well as a password is necessary in order to execute the file transfer. The information should be taken from the data sheet of the slave.
“Upload”	Upload of firmware files A dialog opens to open the firmware file. In this dialog, the input of a string as well as a password is necessary in order to execute the file transfer. The information should be taken from the data sheet of the slave.

Table 366: “E²PROM access”
“Write E²PROM”	Writes the configuration of the slave to the E²PROM. A dialog for storing the configuration opens in the same way as for “File access over EtherCAT”.
“Read E²PROM”	Reads the configuration of the slave from the E²PROM. Upload of firmware files A dialog for opening the configuration opens in the same way as for “File access over EtherCAT”.
“Write E²PROM XML”	Writes the slave configuration directly from the XML file into the device. Can be executed only when configuration data exists in the XML file (<ConfigData> section).