Tab: Sercos Slave – General

Object: Sercos Slave

The tab in the configurator of the Sercos Slave contains the basic settings for network communication.

In the initialization phase, the slave detects the connected modules and provides them as a list to the master. The master assigns device channels in the MDT (master data telegram) and AT (answer telegram) to each slave where the master can read and write data.

Table 2. Identification

Optional device	: If the device is missing in the network, then no error message is issued. : If the device is missing in the network, then the bus is not started and an error message is issued.
Sercos address	The field is activated when you select the classic addressing mode in the master. You must set the same address that is defined with the selector on the device.
Device number	Only part of the device editor when the device description file includes a corresponding entry. In this case, you can also designate a device number for the topological address. This number can then be used in function blocks for switching the device.
Topological Sercos address	The field cannot be edited. The topological address is determined by the order in the project.
Vendor ID	This is taken from the device description file and cannot be edited.
Vendor
Vendor device ID
Device name
FSP Type	Function-specific profile: This is taken from the device description file and cannot be edited.

Table 3. Check Labels

Check vendor code	: When starting the device, the corresponding properties are checked for agreement with the entry in the device description file. The started is aborted if there is a deviation.
Check Device ID

Table 4. Settings

Sercos cycle time factor

This field is visible only if the slave supports SCP_Sync or SCP_WD. This is where you can set the cycle time of the slave individually. Use this parameter when you want to adjust the cycle time of the slave in proportion to the cycle time of the master.

Connection type

Depending on the device description, the following options are available:

Acyclic: The connection is established asynchronously without a watchdog.
Acyclic with Watchdog: The connection is established asynchronously with a watchdog timer.
Cycle Synchronous: The connection is established synchronously to the cycle of the master. This setting is required in the case of oversampling.

Note: If you have selected Oversampling and deselect the connection type as Clock Synchronous, then a message dialog opens where you have to confirm the change. All oversampling settings are then deactivated.

Table 5. Module Diagnostic

This field is visible only if the slave supports the module diagnostic.
Release Diagnostic	: A status bit is provided for each module below the slave in the Sercos I/O Mapping dialog. The bit is TRUE when there are no errors.