Anybus ABC3013 Replacing Communicator Classic with New Communicator User Guide
- June 3, 2024
- Anybus
Table of Contents
Anybus ABC3013 Replacing Communicator Classic with New Communicator
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. The information in this document shall
therefore not be construed as a commitment on the part of HMS Networks and is
subject to change without notice. HMS Networks makes no commitment to update
or keep current the information in this document.
The data, examples and illustrations found in this document are included for
illustrative purposes and are only intended to help improve understanding of
the functionality and handling of the product. In view of the wide range of
possible applications of the product, and because of the many variables and
requirements associated with any particular implementation, HMS Networks
cannot assume responsibility or liability for actual use based on the data,
examples or illustrations included in this document nor for any damages
incurred during installation of the product. Those responsible for the use of
the product must acquire sufficient knowledge in order to ensure that the
product is used correctly in their specific application and that the
application meets all performance and safety requirements including any
applicable laws, regulations, codes and standards. Further, HMS Networks will
under no circumstances assume liability or responsibility for any problems
that may arise as a result from the use of undocumented features or functional
side effects found outside the documented scope of the product. The effects
caused by any direct or indirect use of such aspects of the product are
undefined and may include e.g. compatibility issues and stability issues.
Copyright © 2021 HMS Networks
Contact Information
Postal address:
Box 4126
300 04 Halmstad, Sweden
E-Mail: [email protected]
Overview
This guide describes how to replace the Communicator Classic with the new Communicator. Essentially, there are three main parts to take into consideration:
- Physical differences: power and network connectors are not in the same place, and the configuration port is different.
- Configuration conversion: locating your old configuration and importing it into the new communicator.
- Network configuration file update: how to locate the new GSD/GSDML/EDS file for your network and update the PLC (master).
The goal is to have the new Communicator up and running with a configuration originally from the old Communicator Classic. The screeshot below shows the desired view, where the new Communicator successfully is using the converted configuration.
Physical Differences
Table 1. Physical Comparison
NOTE The Communicator Classic requires more space at the bottom to
accommodate the DSUB connector, while the new Communicator is slightly taller.
Figure 1. The Communicator and the Communicator Classic in Action
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.
If you want to add additional commands you have to add them via the transaction templates in the user interface (all Modbus commands are available)
Locate the configuration file used with the Communicator Classic, that should
be converted to work with the new Communicator.
In the built-in web-interface of the new Communicator to be configured:
-
On the Files & Firmware page, click the Import Anybus Communicator Classic configuration button.
-
In the Import configuration window, click Select file (.cfg).
NOTE If there is an accompanying .cfx name file, it can also be selected and imported. -
In the Open dialog box, browse to and select the configuration file and click Open.
-
To import the configuration file, click Import.
The configuration is now imported in to the web interface of the new Communicator. A pop-up window will appear, saying The import succeeded with the following messages. This window will present things that might need tweaking or corrections.
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.
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):
- Select EtherNet/IP™ in the left menu.
- Select Files & Firmware.
- Click EDS File.
→ This will download the EDS File to the computer.
Below, see two example of how to import the network configuration file into Studio 5000 and TIA Portal. Example 1. How to import an EDS file into Studio 5000
- Make sure that Studio 5000 is in Offline mode.
- Open the Hardware Installation Tool wizard from the Start Menu or from the Tools menu in Studio 5000 and follow the on-screen instructions to install the EDS file.
Example 2. How to import a GSDML file into TIA Portal
- In the Options menu in TIA Portal, select Manage general station description files (GSD).
- After the GSD file has been imported into the configuration tool the Communicator will be available in the hardware catalog.