Accessing the Configuration

Open the EtherNet/IP Local Slaves configuration page:

Step

Action

1

Open the Control Expert project.

2

Open the DTM Browser (Tools > DTM Browser).

3

In the DTM Browser, double-click the CPU DTM to open the configuration window.

NOTE: You can also right-click the CPU DTM and select Open.

4

Expand (+) Device List in the navigation tree to see the local slave instances.

5

Select the local slave instance to view the Properties and Assembly configuration tabs.

Properties

Identify and enable (or disable) the local slave on the Properties tab:

Parameter

Description

Number

The Control Expert DTM assigns a unique identifier (number) to the device. These are the default values:

  • local slave 1: 129

  • local slave 2: 130

  • local slave 3: 131

Active Configuration

Enabled

Enable the local slave with the configuration information in the Assembly fields when the CPU scanner service is an adapter for the local slave node.

Disabled

Disable and deactivate the local slave. Retain the current local slave settings.

Comment

Enter an optional comment (maximum: 80 characters).

Connection Bit

The connection bit is represented by an integer (769 ... 896).

NOTE:

  • This setting is auto-generated after the local slave settings are input and the network configuration is saved.

  • The connection bit is represented by an integer:

    • 385...387 (firmware v1.0)

    • 769...896 (firmware v.2.10)

Assembly

Use the Assembly area of the Local Slave page to configure the size of the local slave inputs and outputs. Each device is associated with these assembly instances:

  • Outputs

  • Inputs

  • Configuration

  • Heartbeat (The heartbeat assembly instance is for listen-only connections only.)

The Control Expert assembly numbers are fixed according to this table, where O indicates the originator (scanner) device and T indicates the target device:

Local Slave

Number

Connection

Device

Assembly

1

129

101

Outputs (T->O)

102

Inputs (O->T)

103

Configuration

199

Heartbeat

2

130

111

Outputs (T->O)

112

Inputs (O->T)

113

Configuration

200

Heartbeat

3

131

121

Outputs (T->O)

122

Inputs (O->T)

123

Configuration

201

Heartbeat
NOTE: When using explicit messaging to read the CPU’s scanner service assembly instance, allocate sufficient room for the response. The size of the response equals the sum of: assembly size + 1 byte (Reply service) + 1 byte (General Status).

Limitations (from the perspective of the local slave):

  • maximum RPI value: 65535 ms

  • maximum timeout value: 512 * RPI

  • outputs (T->O): 509 bytes maximum

  • inputs (O->T): 505 bytes maximum

  • configuration for the CPU scanner service: 0 (fixed)