Skip to main content

Command: EtherNet/IP – Scan for Devices

Dialog: Scan Devices

Table 18. Scanned Devices

Device name, Device type, Address, Station name, etc.

Data about the scanned device depending on network type.

When you change a value in the list of scanned devices, the value is displayed in italics. This indicates that the new value has been changed in the editor in CODESYS, but not in the device. When you download the value to the device, it is displayed normally.

Values which indicate differences between the project and the scanned device are displayed in orange.

If multiple device descriptions are available for the scanned device, then the name is displayed in bold. The selection of the matching device description is resolved differently for different fieldbuses. For more detailed information, see the corresponding fieldbus chapters.

If a device description cannot be found, then the following message is shown: "Attention! The device was not found in the repository." Depending on the bus system, additional information is displayed, such as vendor number and product number. The device cannot be inserted into the project without the installed device description.

Show differences to project

standard icon: The table in the dialog also shows additional configured devices (in the device tree of the project).

_cds_icon_option_deactivated.png: The table shows all scanned devices. The configured devices are not shown.

Scan for Devices

Starts a new search.

Copy All Devices to Project

The device which is selected in the table is inserted into the device tree in the project. If nothing is selected, then all scanned devices are shown.



Important

If you use Copy All Devices to Project to insert devices, which are available in the device tree, to the device tree, then the following should be noted: The data of the Process Data and <...> I/O Mapping tabs of the existing devices may be overwritten with the data of the recently inserted devices.

Table 19. Configured Devices

This part of the dialog is visible only when you select the Show differences to project option.

Differences between the scanned and configured devices are color-coded. Devices displayed in green are identical on both sides. Devices displayed in red are available only in the view of the scanned or configured devices.

_cds_icon_scan_copy_before.png

If you have selected a device in both views, then the scanned devices are inserted above the selected configured device.

_cds_icon_scan_copy_below.png

If you have selected a device in both views, then the scanned devices are inserted below the selected configured device.

_cds_icon_scan_change_device.png

If you have selected a device in both views, then the configured devices are replaced by the selected scanned device.

_cds_icon_scan_copy_all.png

All scanned devices are copied to the project.

_cds_icon_scan_delete.png

Deletes the selected configured device.



Tip

Scanning an adapter can fail if the PLC is in RUN mode and a connection already exists from the scanning controller to the adapter. Then the scanning causes another connection to be established to the adapter, which interrupts the existing connection in the case of some adapters. Then the scanner restarts the connection to the adapter, which causes the adapter to interrupt the connection to the scanning controller.

For this reason, it makes sense to perform a network scan in STOP mode after a "Reset". If RUN mode cannot be interrupted, then scanning is possible without an projected remote adapter (EtherNet/IP Scanners in the device tree only).

For experts

When accepting the remote adapter by means of the Copy to Project command, the I/O dimensions with which the adapter responded are set for the first "exclusive owner" connection. In order to log all of the detected assembly instances after scanning, the definition IODRVETHERNETIP_PRINT_SCAN_RESULT must be set. By default, it is scanned by the instance ID 100–199. This can be modified by means of the ParamScanStartOfInstanceAssem and ParamScanLastOfInstanceAssem library parameters from the IoDrvEtherNetIP Library library. This may be necessary, for example to scan in another manufacturer-specific range (assembly instance ID ranges).