ENGLISH Replacing Communicator Classic with New Communicator QUICK GUIDE SCM-1202-190 Version 1.
Important User Information Disclaimer The information in this document is for informational purposes only. Please inform HMS Networks of any inaccuracies or omissions found in this document. HMS Networks disclaims any responsibility or liability for any errors that may appear in this document. HMS Networks reserves the right to modify its products in line with its policy of continuous product development.
Overview Replacing Communicator Classic with New Communicator 1. Overview This guide describes how to replace the Communicator Classic with the new Communicator. Essentially, there are three main parts to take into consideration: 1. Physical differences: power and network connectors are not in the same place, and the configuration port is different. 2. Configuration conversion: locating your old configuration and importing it into the new communicator. 3.
Replacing Communicator Classic with New Communicator Physical Differences 2. Physical Differences Table 1.
Configuration Conversion Replacing Communicator Classic with New Communicator 3. Configuration Conversion The intended use of the configuration conversion is to: • convert custom protocols. • get a new Communicator unit up and running quickly and then complete the configuration in the Communicator's built-in web interface. NOTE If standard Modbus RTU commands are imported, they are converted to custom request/response transactions. The behavior of the standard Modbus RTU commands is preserved.
Replacing Communicator Classic with New Communicator Configuration Conversion Possible configuration parts that might look different or need correction • The fieldbus/network settings. These might need to be adjusted to the new network environment. • Timeouts were previously set per transaction. In the new Communicator, they are now set on node level. • Pure Modbus configurations are reinterpreted and imported as custom request/response transactions. Page 4 of 8 SCM-1202-190 1.
Network Configuration File Update Replacing Communicator Classic with New Communicator 4. Network Configuration File Update When replacing the Communicator Classic with the new Communicator, it is also mandatory to update the network configuration file (EDS, GSDML, GSD etc.) in the PLC software. To retrieve the network configuration file from the web interface of the new Communicator (the example is for EtherNet/IP™, but it is identical for all networks): 1. Select EtherNet/IP™ in the left menu. 2.
Replacing Communicator Classic with New Communicator Network Configuration File Update Example 2. How to import a GSDML file into TIA Portal 1. In the Options menu in TIA Portal, select Manage general station description files (GSD). 2. After the GSD file has been imported into the configuration tool the Communicator will be available in the hardware catalog. Page 6 of 8 SCM-1202-190 1.
