Accessing Local Slaves with a Scanner
Original instructions
About us
Introduction
Use these instructions to map local slave instances in a network scanner to the enabled local slaves in the BMENOC0301 (Local Slave 4, Local Slave 5).
NOTE: This example uses a BMENOC0301 module. Use the same instructions for other M580 communications modules (like the BMENOC0311 or BMENOC0321).
In this example, the BMX NOC 0401 Ethernet communication module is a network scanner (originator, O) that scans the BMENOC0301 module when it is enabled as a local slave (target, T).
Configure the BMX NOC 0401 module in an M340 Control Expert project.
Adding the Device DTM
Create a local slave instance that corresponds to an enabled local slave by name:
Step
Action
1
Open an M340 Control Expert project that includes a BMX NOC 0401 Ethernet communication module.
2
Right-click the BMX NOC 0401 module in the DTM Browser (Tools → DTM Browser) and scroll to Add.
3
Open the Add dialog box.
4
Select the DTM that corresponds to the BMENOC0301 module (BMENOC0301 (from EDS)).
NOTE:
  • The DTM used in this example (BMENOC0301 (from EDS)) corresponds to the BMENOC0301 module. For other target devices, use the DTM from the manufacturer that corresponds to your scanner device.
  • The corresponding input I/O vision and output I/O vision variables are automatically created with the respective suffixes _IN and _OUT.
5
Press the Add DTM button to open the Properties of device dialog window.
6
Assign a context-sensitive Alias name that corresponds to Local Slave 4 for the M580 BMENOC0301 module. (For this example, enter BMENOC0301_from_EDS_LS4.)
7
Press OK to see the local slave instance in the DTM Browser.
Mapping Local Slave Numbers
In the M340 Control Expert project, associate the local slave instances in the BMX NOC 0401 scanner with specific local slaves that are enabled for the BMENOC0301 module:
Step
Action
1
In the DTM Browser, double-click the local slave instance that corresponds to Local Slave 4 in the BMENOC0301 target device (BMENOC0301_from_EDS_LS4).
NOTE: The default connection is Local Slave 1 - Exclusive Owner, which is most applicable to Local Slave 1 in the target device. It is not appropriate for the local slave instance BMENOC0301_from_EDS_LS4, which is associated with Local Slave 4 by the assigned context-sensitive name (... _LS4).
2
Select Local Slave 1 - Exclusive Owner.
3
Press Remove Connection to delete the connection to Local Slave 1.
4
Press Add Connection to open the dialog box (Select connection to add).
5
Scroll to Local Slave 4 - Exclusive Owner.
6
Press the Apply button.
The local slave (Local Slave 4) is now the target of a local slave instance with a context-sensitive connection name (Local Slave 4 - Exclusive Owner).
Mapping IP Addresses
Associate the IP address of the local slave (target, T) with the local slave instances in the scanner (originator, O) configuration:
Step
Action
1
Double-click the BMX NOC 0401 module in the DTM Browser.
2
In the navigation pane, expand the Device List.
3
Select a local slave instance (BMENOC0301_from_EDS_LS4).
4
Select the Address Setting tab.
5
In the IP Address field, enter the IP address of the local slave device (192.168.20.10).
6
Click in the navigation pane to make the Apply button active.
NOTE: You may have to select Disabled in the drop-down menu (DHCP for this device) to activate the OK and Apply buttons.
7
Configure the data size.
NOTE: Refer to the instructions for configuring input and output items.
8
Press Apply.
Configuring an Additional Connection
You have created one local slave instance that corresponds by name and IP address to an enabled local slave. That is, the local slave instance BMENOC0301_from_EDS_LS4 in the M340 Control Expert project corresponds to Local Slave 4 in the M580 Control Expert project.
Because this example uses two local slave connections, you will make another connection (for Local Slave 5):
Step
Action
1
Repeat the above steps to create a second local slave instance that corresponds to Local Slave 5.
2
Build the Control Expert project.
Accessing the Device DDT Variables
Step
Action
1
In the Project Browser (Tools → Project Browser) expand Variables & FB instances.
2
Double-click Device DDT Variables to see the device DDTs that correspond to the BMENOC0301 module in slot 3.