Device Id Mapping To Ip Address/Port/Slave Device Ids - Pepperl+Fuchs ICDM-RX/MOD Manual

Modbus router user
Table of Contents

Advertisement

ICDM-RX/MOD User Manual
Overview

1.10.4. Device ID Mapping to IP Address/Port/Slave Device IDs

Combining the Alias and Remote Modbus/TCP configurations can provide connectivity between Modbus
master(s) that address slave(s) based on device ID(s) to Modbus/TCP slave(s) which require specific IP
addresses, port numbers and/or alternate device ID(s). This is especially useful when:
There are multiple Modbus/TCP slaves with the same device ID.
A Modbus/TCP slave has multiple internal applications that are addressable through:
-
Different IP addresses, same port, same device ID
-
Different IP addresses, different ports, same device ID
-
Same IP address, different ports, same device ID
The following example depicts a typical installation requiring Device ID mapping:
Modbus Master Device ID to Slave Modbus/TCP Device Mapping Example
28

Advertisement

Table of Contents
loading

Table of Contents