Local Slave Parameters
Original instructions
About us
Accessing the Configuration
Open the EtherNet/IP Local Slaves configuration page:
Step
Action
1
Open the Control Expert project that includes a BMENOC0301 module.
2
Open the DTM Browser (Tools → DTM Browser).
3
In the DTM Browser, double-click the name that you assigned to the BMENOC0301 to open the configuration window.
NOTE: You can also right-click on the module and scroll to Open to open the configuration window.
4
Expand (+) Device List in the navigation tree to see the local slave instances.
5
Select the local slave instance BMENOC0301_from_EDS_LS4 <EIP:192.168.20.10> 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: 112
  • local slave 2: 113
  • local slave 3: 114
  • ...
  • local slave 16: 127
Active Configuration
Enabled
Enable the local slave with the configuration information in the Assembly fields when the BMENOC0301 module 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 auto-generated value in this field represents the association to the local slave in the Request/Connection Summary table.
NOTE: This setting is auto-generated after the local slave settings are edited and the network configuration is saved.
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:
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
112
101
Outputs (T->O)
102
Inputs (O->T)
103
Configuration Size
199
Heartbeat
2
113
111
Outputs (T->O)
112
Inputs (O->T)
113
Configuration Size
200
Heartbeat
3
114
121
Outputs (T->O)
122
Inputs (O->T)
123
Configuration Size
201
Heartbeat
4
115
131
Outputs (T->O)
132
Inputs (O->T)
133
Configuration Size
202
Heartbeat
5
116
136
Outputs (T->O)
137
Inputs (O->T)
138
Configuration Size
202
Heartbeat
6
117
141
Outputs (T->O)
142
Inputs (O->T)
143
Configuration Size
202
Heartbeat
7
118
146
Outputs (T->O)
147
Inputs (O->T)
148
Configuration Size
202
Heartbeat
8
119
151
Outputs (T->O)
152
Inputs (O->T)
153
Configuration Size
202
Heartbeat
9
120
156
Outputs (T->O)
157
Inputs (O->T)
158
Configuration Size
202
Heartbeat
10
121
161
Outputs (T->O)
162
Inputs (O->T)
163
Configuration Size
202
Heartbeat
11
122
166
Outputs (T->O)
167
Inputs (O->T)
168
Configuration Size
202
Heartbeat
12
123
171
Outputs (T->O)
172
Inputs (O->T)
173
Configuration Size
202
Heartbeat
13
124
176
Outputs (T->O)
177
Inputs (O->T)
178
Configuration Size
202
Heartbeat
14
125
181
Outputs (T->O)
182
Inputs (O->T)
183
Configuration Size
202
Heartbeat
15
126
186
Outputs (T->O)
187
Inputs (O->T)
188
Configuration Size
202
Heartbeat
16
127
191
Outputs (T->O)
192
Inputs (O->T)
193
Configuration Size
202
Heartbeat
NOTE: When using explicit messaging to read the BMENOC0301 module’s assembly instance, you need to 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):