Introduction

Use these instructions to map local slave instances in a network scanner to the enabled local slaves in the CPU’s embedded scanner service (Local Slave 1, Local Slave 2, Local Slave 3).

This example uses a BMENOC0301 Ethernet communication module as a network scanner (originator, O) that scans the CPU scanner service when it is enabled as a local slave (target, T).

Configure the BMENOC0301 module in an M580 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 your M580 Control Expert project.

2

Right-click the BMENOC0301 module in the DTM Browser (Tools > DTM Browser) and select Add.

3

Select the DTM that corresponds to the CPU.

NOTE:

  • The DTM used in this example corresponds to the CPU’s scanner service. 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.

4

Press the Add DTM button to open the Properties of device dialog window.

5

Assign a context-sensitive Alias name that corresponds to Local Slave 1 for the CPU.

Example: BMEP58_ECPU_from_EDS_LS1

6

Click OK to see the local slave instance in the DTM Browser.

Mapping Local Slave Numbers

In the M580 Control Expert project, associate the local slave instances in the BMENOC0301 scanner with specific local slaves that are enabled for the CPU’s scanner service:

Step

Action

1

In the DTM Browser, double-click the local slave instance that corresponds to Local Slave 1 in the CPU target device (BMEP58_ECPU_from_EDS_LS1).

NOTE: The default connection is Local Slave 1 - Exclusive Owner, which is most applicable to Local Slave 1 in the target device.

2

Select Local Slave 1 - Exclusive Owner.

3

Click Remove Connection to delete the connection to Local Slave 1.

4

Click Add Connection to open the dialog box ( Select connection to add).

5

Select Local Slave 4 - Exclusive Owner.

6

Click Apply .

The local slave (Local Slave 1 ) is now the target of a local slave instance with a context-sensitive connection name (Local Slave 1 - 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 BMENOC0301 module in the DTM Browser .

2

In the navigation pane, expand the Device List.

3

Select a local slave instance (BMEP58_ECPU_from_EDS_LS1).

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 inside 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.

8

Click Apply .

Configuring an Additional Connection

You have created one local slave instance that corresponds by name and IP address to an enabled local slave. This example uses two local slave connections, so make another connection for Local Slave 2.

Step

Action

1

Repeat the preceeding steps to create a second local slave instance that corresponds to Local Slave 2.

2

Build the Control Expert project.

Accessing the Device DDT Variables

Step

Actiom

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 with the CPU’s scanner service.