ENGLISH Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial USER MANUAL SCM-1202-177 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.
Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial Table of Contents 1. Preface .................................................................................................................................. 1.1. About This Document ........................................................................................................ 1.2. Document Conventions ..................................................................................................... 1.3. Trademarks .......................
Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial 7.5.1. Communication Serial Protocol ................................................................................... 45 7.5.2. Communication Basic Settings .................................................................................... 46 7.5.3. Communication Advanced Settings ............................................................................. 48 7.6. About Transaction Templates ........................................................
Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial 10.1.6. Setup the Transactions .......................................................................................... 10.1.7. Check the I/O Data Map ........................................................................................ 10.2. AC Motor Drive - Custom Request/Response Use Case ........................................................ 10.2.1. About the Use Case ...........................................................................
This page is intentionally left blank.
Preface Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial 1. Preface 1.1. About This Document This document describes how to install and configure Anybus® Communicator™. For additional documentation and software downloads, FAQs, troubleshooting guides and technical support, please visit www.anybus.com/support. 1.2. Document Conventions Lists Numbered lists indicate tasks that should be carried out in sequence: 1. First do this 2.
Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial Trademarks Safety Symbols DANGER Instructions that must be followed to avoid an imminently hazardous situation which, if not avoided, will result in death or serious injury. WARNING Instructions that must be followed to avoid a potential hazardous situation that, if not avoided, could result in death or serious injury.
Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial Safety 2. Safety 2.1. Intended Use The intended use of this equipment is as a communication interface and gateway. The equipment receives and transmits data on various physical layers and connection types. If this equipment is used in a manner not specified by the manufacturer, the protection provided by the equipment may be impaired. 2.2. General Safety CAUTION Ensure that the power supply is turned off before connecting it to the equipment.
Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial Preparation 3. Preparation 3.1. Cabling Have the following cables available: • Ethernet cable for configuration • PROFIBUS cable for connecting to the high level network • Power cable 3.2. System Requirements 3.2.1. Supported Operating Systems Operating System Description Windows 7 SP1, 32-bit Windows 7 32-bit with Service Pack 1 Windows 7 SP1, 64-bit Windows 7 64-bit with Service Pack 1 Windows 10 64-bit Windows 10 64-bit 3.2.2.
HMS Software Applications Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial 3.5. HMS Software Applications Download the software installation files and user documentation from www.anybus.com/support. IPconfig Use the HMS software application IPconfig and scan your network to discover and change the Communicator IP address and to access the Communicator built-in web interface.
Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial About Anybus Communicator 4. About Anybus Communicator 4.1. Serial Protocol Communication 4.1.1. Serial Protocol Types The gateway features three distinct modes of operation for the subnetwork communication, called Modbus RTU, Custom Request/Response and Custom Produce/Consume. Figure 1. Communication, Serial protocol Modbus RTU By default the Communicator uses the Modbus RTU serial protocol.
Serial Protocol Communication Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial 4.1.2. Serial Protocol Building Blocks The following building blocks are used to describe the subnetwork communication. Node Figure 2. Nodes on a subnetwork A node represents a single device on the subnetwork. Each node can be associated with a number of transactions. Nodes and Transactions Figure 3.
Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial Serial Protocol Communication Frame Fields The Frame editor is used to design custom transaction templates. The Frame editor with Frame fields is available when either the Custom Request/Response or Custom Produce/ Consume serial protocol is enabled. Figure 4. Frame editor Frame fields are low level entities used to compose transactions.
Serial Protocol Communication Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial Transaction Templates The Transaction templates are available when either the Custom Request/Response or Custom Produce/ Consume serial protocol is enabled. Figure 5. Frame editor, Request and Response A transaction represents a complete serial telegram, and consists of a number of frame fields. Each frame field is associated with a set of parameters controlling what is transmitted on the subnetwork.
Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial How the Communication Works 4.2. How the Communication Works The Communicator enables communication, data exchange, between one or more server devices connected to a serial subnetwork and a client device connected to a high level network. Figure 6. Process data traffic overview For example: • The client device can be a PLC controller or a PC. • A server devices can be a sensor, scanner, industrial robot or sniffer.
How the Communication Works Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial Transfer Process Data Figure 8. Process data traffic from client to nodes Transfer process data from the high level network client device and make it available on the server interface and for the serial subnetwork nodes included in the configuration. SCM-1202-177 1.
Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial How the Data Exchange Works 4.3. How the Data Exchange Works Figure 9. The Communicator internal memory areas The data exchanged between the Communicator and the serial subnetwork and the high level network resides in the Communicator internal memory buffer. To exchange data with the serial subnetwork, the high level network reads and writes data to the Communicator internal memory buffer.
Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial Installation 5. Installation 5.1. External Parts Figure 10. External parts A. Power connector F. B. Rotary Switch x 3 For PROFIBUS address G. PROFIBUS DSUB connector 7-pin connector H. Cable tie mount L. C. Label with LED designation I. M. DIN rail locking mechanism Laser engraved connectors designation J. Security switch K. Factory reset button Laser engraved label with product information D. Status LEDs E.
Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial DIN Rail Mounting 5.2. DIN Rail Mounting IMPORTANT The equipment must be electrically grounded through the DIN rail for EMC compliance. Make sure that the equipment is correctly mounted on the rail and that the rail is properly grounded. Figure 11. Attach the Communicator on the DIN rail To attach the Communicator on the DIN rail: 1. Insert the upper end of the DIN rail clip into the DIN rail. 2. Push the bottom of the DIN rail clip into the DIN rail.
Connect to PROFIBUS Network Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial 5.3. Connect to PROFIBUS Network Figure 12. Connect to PROFIBUS network 1. Connect the Communicator to your PROFIBUS network. PROFIBUS Connector Pin Description 1 Shield 2 Not used 3 Line B 4 RTS 5 GND Bus 6 +5 V Bus Out 7 Not used 8 Line A 9 Not used Housing PE To Do Next Connect the Communicator to the Serial RS-232/485 network, set the node address on the rotary switches and connect to power.
Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial Connect to Serial RS232/RS485 Subnetwork 5.4. Connect to Serial RS232/RS485 Subnetwork NOTE Use minimum 90 oC copper (Cu) wire only. Figure 13. Connect to serial RS232/RS485 subnetwork 1. Insert the cable wires into the 7-pin connector and tighten the wire clamp screws. 7-pin connector Pin Signal 1 RS232 Rx Input 2 RS232 Tx Output 3 Functional Earth (FE) 4 Signal GND 5 RS485+ B 6 RS485- A 7 +5 V OUT 2.
Rotary Switch Settings Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial 5.5. Rotary Switch Settings 5.5.1. Rotary Switches Default Setting By default, the value on the three rotary switches are set to 000. Figure 14. Rotary switches default setting 000. SCM-1202-177 1.
Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial Rotary Switch Settings 5.5.2. Set a Node Address with Rotary Switches About the Rotary Switch Settings To set a node address for the PROFIBUS server, use the rotary switches located on the top front of the Communicator . TIP Use Windows Calculator (or similar application) to convert between hexadecimal (hex) and decimal (dec). • The default node address setting is 000.
Rotary Switch Settings Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial Before You Begin Ensure that the Communicator is disconnected from power. Figure 15. Disconnect Communicator from power Procedure Use a screwdriver to change the rotary switch position. Ensure that the rotary switches engage correctly. SCM-1202-177 1.
Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial Rotary Switch Settings Example 2. To set the node address 12 hex = 18 dec 1. The rear rotary switch A is not used, ensure that it is set to 0. 2. Set the center rotary switch B to 1 hex. 3. Set the front rotary switch C to 2 hex. The center rotary switch B 1 hex = 1 dec and the front rotary switch C 2 hex = 2 dec. The node address expressed in decimal numbers is therefore 16 x 1 + 2 = 18. Example 3.
Rotary Switch Settings Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial To Do Next Connect the Communicator to power. See Connect to Power (page 22). Figure 16. Connect Communicator to power Result The set node address is active as soon as the Communicator is powered on. NOTE Changing the address settings on the rotary switches during operation is ignored. For a new address to take effect, power cycle the Communicator . SCM-1202-177 1.
Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial Connect to Power 5.6. Connect to Power CAUTION Ensure that the power supply is turned off before connecting it to the equipment. IMPORTANT Using the wrong type of power supply can damage the equipment. Ensure that the power supply is connected properly and of the recommended type. IMPORTANT Before you connect the Communicator to power, ensure that the PROFIBUS address is set on the rotary switches.
Connect to Power Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial Power port Pin Description 1 12-30 VDC Power Connector 2 Ground (GND) 3 Functional Earth (FE) 2. Connect the terminal block to the Communicator. 3. Connect the Communicator to a power supply. 4. Turn on the power supply. To Do Next Check LED status, refer to Communicator LED Indicators (page 96). SCM-1202-177 1.
Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial Security Switch 5.7. Security Switch NOTE After completing the configuration of the Communicator, lock the security switch to prevent unauthorized access to the Communicator built-in web interface. When the security switch is in its locked position, the Communicator built-in web interface can not be accessed and the Communicator can not be configured using the built-in web interface.
Security Switch Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial Security Switch Status LED Figure 19. Security switch locked status LED When the security switch is in its: • locked position, the security switch status LED turn solid green. • unlocked position, the security switch status LED is turned off. SCM-1202-177 1.
Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial Lock the Cables 5.8. Lock the Cables Figure 20. Lock the cables To strain relieve the cables, place a cable tie in the holder and lock the cables. Page 26 of 134 SCM-1202-177 1.
DIN Rail Demount Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial 5.9. DIN Rail Demount Before You Begin IMPORTANT Be careful when removing the Communicator from the DIN-rail. If not removed properly, the DIN rail locking mechanism and the product cover can break. Have a flat-blade screwdriver, size 5.5 mm, available. Procedure Remove the Communicator from the DIN Rail: 1. Insert the screwdriver into the Communicator DIN rail locking mechanism. 2.
Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial DIN Rail Demount 3. Hold the screwdriver in the DIN rail locking mechanism while you unhook the Communicator from the DIN rail. Figure 22. Unhook the Communicator Page 28 of 134 SCM-1202-177 1.
Configuration Quick Guide Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial 6. Configuration Quick Guide This section is intended to give you a short overview of the tasks you need to perform to configure the Communicator. For detailed information, please refer to Communicator Configuration (page 39) . 6.1. Prepare Configuration 1. Connect Communicator to the PROFIBUS network. 2. Set the desired PROFIBUS address on the Rotary Switches. The default setting is 0.
Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial 3. Connect the Communicator to the serial RS232/RS485 subnetwork 4. Connect to PC and power Prepare Configuration a. Connect an Ethernet cable between the Communicator configuration port and your PC. b. Connect the Communicator to a power supply. Page 30 of 134 SCM-1202-177 1.
Prepare Configuration 5. Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial Find the Communicator on your PC The Communicator default IP address is 192.168.0.10. Option 1 On the PC accessing the Communicator built-in web interface, set a static IP address within the same IP address range as the Communicator IP address. Option 2 Change the IP address on the Communicator configuration port to one within the same IP address range as your PC.
Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial Setup New Configuration 6.2. Setup New Configuration Follow these steps to setup a new Communicator configuration. 1. Subnetwork configuration On the Communication page: a. Select a serial protocol: Modbus RTU (default), Custom Request/Response or Custom Produce/ Consume. For information about the serial protocol types, see Serial Protocol Types (page 6). b.
Setup New Configuration 3. Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial Add Nodes and Commands On the Nodes & commands page: a. Add a node and configure the node settings. b. Add commands to the node and configure the command settings. c. Repeat until you have added and configured all your nodes. 4. High level network configuration On the PROFIBUS page: 1. Use Automatic I/O sizes provided by the subnetwork or choose to set them manually. 2.
Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial 5. Setup New Configuration I/O Data Mapping The commands you added to the nodes are automatically mapped to the Communicator internal memory area. View the added nodes and commands on the I/O data map page. Page 34 of 134 SCM-1202-177 1.
PLC Configuration Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial 6.3. PLC Configuration In the Communicator built-in web interface: 1. Export I/O data map When you configure the communication between the Communicator and the PLC, you can use the I/O data map as a specification to ensure that the commands match. On the I/O data map page: You can download the I/O data mapping in a spreadsheet to your PC. 2.
Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial PLC Configuration In the PLC program: 1. 2. Import product file Option if the PLC program requires a GSD (General Station Description) file. Import the GSD file into your PLC project. Configure the communication Configure the PLC to communicate with the Communicator according to the I/O data map created in the Communicator. Page 36 of 134 SCM-1202-177 1.
Verify Operation Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial 6.4. Verify Operation 1. Apply the configuration 2. When you have completed and verified the configuration, click Apply for the settings to take effect. Verify status and LED indications On the Home page: Monitor the Communicator, network and node status. You can also view the Communicator LED indications remotely. SCM-1202-177 1.
Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial 3. Verify Operation Verify and monitor communication In Diagnostics, use the: • Serial RS-232/485 page to verify that the serial commands are sent and received by the Communicator. • Event log page to detect failures and unexpected behavior over time. Page 38 of 134 SCM-1202-177 1.
Communicator Configuration Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial 7. Communicator Configuration This section is intended to give you detailed information about the tasks you need to perform to setup a new Communicator configure. For a more brief overview of the configuration steps, please refer to the Configuration Quick Guide (page 29). 7.1. Connect the Communicator Procedure Connect to High Level Network and Subnetwork • Connect the Communicator to the subnetwork.
Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial Access the Built-In Web Interface From HMS IPconfig 7.2. Access the Built-In Web Interface From HMS IPconfig Before You Begin Download the software application HMS IPconfig installation files and user documentation from www.anybus.com/support. NOTE The Communicator default IP address is 192.168.0.10. NOTE To access the Communicator built-in web interface, ensure that Port 80 TCP is open in your Firewall.
Access the Built-In Web Interface From HMS IPconfig Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial 4. Change the Communicator IP address to one within the same IP address range as your PC. 5. To open the Open web page built-in web interface, click Communicator. Result You are redirected to the Communicator built-in web interface Home page. SCM-1202-177 1.
Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial Access the Built-In Web Interface From a Web Browser 7.3. Access the Built-In Web Interface From a Web Browser Before You Begin NOTE The Communicator default IP address is 192.168.0.10. NOTE To access the Communicator built-in web interface, ensure that Port 80 TCP is open in your Firewall. This applies to any Firewall between the web browser and the gateway. NOTE When you change to a static IP address on your computer, internet access may be lost.
Access the Built-In Web Interface From a Web Browser 4. Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial To open the built-in web interface Home page, press Enter. SCM-1202-177 1.
Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial Communicator Built-In Web Interface Overview 7.4. Communicator Built-In Web Interface Overview Use the Communicator built-in web interface to configure, maintain and troubleshoot the Communicator. Figure 23. The Communicator built-in web interface Home page Home View the Communicator, network and node status. Apply After configuration changes are made and verified, press Apply to make the settings take effect.
General Subnetwork Settings Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial 7.5. General Subnetwork Settings 7.5.1. Communication Serial Protocol Before You Begin Before starting the configuration, select the Serial protocol you want to use: • Modbus RTU, Default setting: Use for serial devices that conform to the Modbus communication specification. • Custom Request/Response: Create your own custom request/response transactions.
Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial General Subnetwork Settings 7.5.2. Communication Basic Settings Figure 26. Communication, Basic settings Physical standard Specify the physical interface type for the device connected to the Communicator. • Select a physical standard from the Physical standard drop-down menu. Setting Value Description Physical standard RS-232, Default standard Use RS-232 when one single node is connected to the subnetwork.
Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial General Subnetwork Settings Data bits Data bits is the number of bits used in the data representation of characters in the telegrams. The rate for Modbus RTU is 7 data bits or 8 data bits. The default setting is 8 data bits. Setting Value Baud rate 1200 baud 1800 baud 2400 baud 4800 baud 9600 baud, Default value 19200 baud 35700 baud 38400 baud 57600 baud 115200 baud 128000 baud Parity Specify if parity should be used to detect errors in the data.
Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial General Subnetwork Settings 7.5.3. Communication Advanced Settings Inter-Telegram Timeout Mode Settings Figure 27. Advansed settings, Default (3.5 characters) By default, Inter-telegram timeout mode Default (3.5 characters) is used. This is according the Modbus RTU standard, which advocates the use of a silent period equivalent to 3.5 characters between each message. The silent period is used to find out where one message ends and the next begins.
About Transaction Templates Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial 7.6. About Transaction Templates This section applies when the Custom Request/Response or Custom Produce/Consume serial protocol is applied, refer to Communication Serial Protocol (page 45). 7.6.1. Transaction Template Example Custom Request/Response Figure 29. Request/Response transaction template example The transaction named Read parameter (0x01) consists of a number of frame fields.
Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial About Transaction Templates Custom Produce/Consume Figure 30. Produce transaction template example The transaction named Read Barcode Data Template consists of a number of frame fields. The Transaction type can be Produce or Consume. In this example the Transaction type Consume is selected. In the frame field we have added one Variable data field and two Constant fields. 7.6.2.
About Transaction Templates Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial For the produce/consume transactions you select; Empty produce template or Empty consume template. Figure 32. Transaction template, Empty Produce and Consume templates Modbus Templates Modbus templates are available for Custom Request/Response and Modbus RTU transactions. When using the Modbus template, you first select the Modbus template from which you want to start.
Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial About Transaction Templates Example 4. New transaction template based on the Modbus template Read Discrete Inputs 7.6.3. Frame Field Types Each transaction consists of frame fields which makes up the serial telegram frame. Each frame field specifies how the Communicator shall interpret or generate a particular part of the telegram. Figure 34. The following frame objects are available Node address Frame field representing the Node address of the Node.
About Transaction Templates Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial Data Data frame fields are used to represent raw data as follows. • Produce/Request Transactions: The specified data block is forwarded from the higher level network to the subnetwork. • Consume/Response Transactions: The specified data block is forwarded from the sub-network to the high level network.
Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial Build Transaction Template 7.7. Build Transaction Template Before You Begin Ensure that you have applied the Custom Request/Response or Custom Produce/Consume serial protocol, refer to Communication Serial Protocol (page 45). 7.7.1. Add Transaction Template Procedure Add a transaction template: 1. In the web-interface left sidebar menu, click Transaction templates. 2. To select the template you want to use, click the Add drop-down button.
Build Transaction Template Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial Example 5. A new empty request/response template is added to the transaction template list SCM-1202-177 1.
Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial Build Transaction Template • To add a new template based on a standard Modbus transaction, select Modbus templates and then the desired Modbus transaction. Example 6. A new request/response template based on “Read Coils (1)” is added to the transaction template list Page 56 of 134 SCM-1202-177 1.
Build Transaction Template Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial Option for the Custom Produce/Consume Protocol • Select Empty produce templates or Empty consume templates. You can change the Transaction type after the transaction template is added. Example 7. A new produce template is added to the transaction template list 3. To apply the settings, click Apply in the web-interface header, and follow the instructions.
Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial Build Transaction Template 7.7.2. Add Frame Fields Procedure 1. In the transaction template list, select a transaction template to add frame fields to. Figure 35. Select transaction template 2. Build the transactions. • To add frame fields: In the Frame editor frame fields menu, drag and drop the desired frame fields into the drag and drop fields. Figure 36.
Build Transaction Template Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial • To change the order of the frame fields: Drag and drop the frame fields in the list to change the order. Figure 38. Change frame fields order • To delete a frame field: On the frame field that you want to delete, click the three dots icon. Click Delete and then Yes to confirm. Figure 39. Delete frame field 3. To apply the settings, click Apply in the web-interface header, and follow the instructions.
Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial Build Transaction Template 7.7.3. Configure Frame Fields Settings Procedure Figure 40. Frame Fields Settings 1. In the Transaction templates list, select a transaction template to configure. 2. In the Transaction template settings select a Field to configure. The Field sidebar opens, on the right side of the screen. 3. Configure the Field settings. Node address • Frame field representing the Node address of the node.
Build Transaction Template Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial Limit NOTE Limit can only be added as a Response frame field. • Name: You can name the Frame Field to make it easier to identify. • Type: Specify the number of bytes in the frame. Select Byte (1 byte) (Default), Word (2 bytes), Double word (4 bytes). • Endianess: Select Big-endian (Default) or Little-endian. • Min value: The lowest value of the limit range. • Max value: The highest value of the limit range.
Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial Build Transaction Template • Error check type: Specify how the checksum is converted. Select None (Default), One’s complement or Select None, Two’s complement. • Representation: Specify how the checksum is represented. Select Binary (Default) or ASCII. About Fixed field* • Yes, set here: The Value set here is fixed and cannot be changed when the transaction is used on a node. The value must be updated in the transaction template.
Build Transaction Template Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial Transaction Template Variable Data Settings Figure 41. Transaction template variable data settings 1. Select a desired Variable data object. 2. In the Data delimiter and/or Subnet delimiter drop down menu, select one of the following options.
Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial Build Transaction Template • End pattern The package consists of a data section followed by an end character to indicate where the data section ends. End pattern is used to define whether the delimiter is an end character or an end pattern, which depends on whether the message is forwarded from the subnetwork or sent as process data. • None The package contains only the data section.
Build Transaction Template Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial 7.7.5. Store Transaction Templates The transaction templates are stored on the Transaction templates page. Figure 42. Transaction templates page The transaction templates are available for use on the Nodes & transaction page, when you add transactions to a node. Figure 43. Nodes & transaction page For information on how to add the transaction templates to the nodes, refer to Transaction Settings (page 72). SCM-1202-177 1.
Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial Nodes and Transactions 7.8. Nodes and Transactions A node represents a single device on the serial subnetwork. Add nodes and set up the communication between the nodes and the client. Before You Begin Obtain user documentation, from the manufacturers of the devices to communicate with, describing available registers and how to address them. 7.8.1. Node and Broadcast Node You can add two types of nodes, Node and Broadcast Node. Figure 44.
Nodes and Transactions Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial 7.8.2. Add Node NOTE You can add one single Broadcast node. The maximum number of Nodes that can be added is 31. 1. 2. 3. In the web-interface left sidebar menu, click Nodes & transactions. Click Add node. Select Add broadcast node or Add node. Figure 45. Add node A new node/brodcats node is added to the nodes list. Figure 46.
Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial Nodes and Transactions 7.8.3. Node Settings Before You Begin Ensure that the Communicator Basic settings, on the Communication page, match the Node settings. There are no Node settings for the Broadcast node, except Name. Procedure Figure 47. Nodes page, Node settings 1. In the node list, select a node to configure. 2. Configure the Node settings.
Nodes and Transactions Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial 3. To apply the settings, click Apply in the web-interface header, and follow the instructions. To Do Next Add Transactions, Add Transactions (page 69). 7.8.4. Add Transactions NOTE The maximum number of transactions that can be added to a node is 150. 1. In the node list, select a node to configure. 2. In the transaction list, click Add. 3.
Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial Nodes and Transactions When using the Request/Response or Produce/Consume Serial Protocol Figure 49. Add new empty template • Click Add and select Add from new transaction template. You are redirected to the Transaction template page. A new empty template is added to the Transaction templates list. NOTE You must build the transactions before you can use the template, refer to Build Transaction Template (page 54). Figure 50.
Nodes and Transactions Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial • If you already have created Transaction templates, click Add and select the desired template from the list. A new transaction is added to the transactions list. Figure 51. Add new transaction To Do Next Configure the Transactions settings, Transaction Settings (page 72). SCM-1202-177 1.
Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial Nodes and Transactions 7.8.5. Transaction Settings Before You Begin NOTE When a custom transaction is selected, the custom transaction template is locked for editing. For Modbus transaction reference guide, refer to Modbus Transactions (page 131). Procedure Figure 52. Modbus TCP Protocol Figure 53. Custom request/response Protocol 1. In the node list, select a node to configure. 2. In the transactions list, select a transaction to configure.
Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial Nodes and Transactions 4. Select a transaction type from the Modbus transaction/Custom transaction drop-down menu. The transaction type defines what the node should perform when the transaction is executed. 5. Configure the Command settings. Setting Value Description Transaction name N/A You can name the transaction to make it easier to identify. Read quantity 1 to 125 Specifies the number of registers to read to follow in the read data field.
Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial Nodes and Transactions 7.8.6. Activate/Deactivate Transaction Figure 54. Activate/Deactivate Transaction The transaction default status is Active. To deactivate/activate a transaction, select the transaction and click the slide toggle. 7.8.7. Duplicate Transaction When you duplicate a transaction, all settings are preserved. Figure 55. Duplicate transaction To duplicate: • One transaction, select the command and click Duplicate.
Nodes and Transactions Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial 7.8.8. Delete Transaction Figure 56. Delete transaction 1. To delete: • One transaction, select the transaction and click Delete. • Multiple transactions, select the checkbox in front of each transaction and click Delete. 2. To confirm, click Yes. SCM-1202-177 1.
Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial High Level Network Settings 7.9. High Level Network Settings Configure the PROFIBUS network settings. 7.9.1. To Use Automatic I/O Sizes Figure 57. PROFIBUS, I/O sizes By default, the Communicator is set to use automatic I/O sizes. The size of the input data, Data Size to PROFIBUS, and the output data, Data Size from PROFIBUS, is determined by the subnetwork configuration.
High Level Network Settings Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial 7.9.3. PROFIBUS Address Settings NOTE Ensure that the Communicator rotary switches are sett to 000. Figure 59. PROFIBUS address setting In the PROFIBUS address field, enter the Communicator node address. SCM-1202-177 1.
Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial I/O Data Map 7.10. I/O Data Map Figure 60. I/O data map page On the I/O data map page the data communication between the subnetwork (Node) and the high level network (PLC) is mapped. The allocated I/O area is auto-generated based on how the settings on the Serial communication page and the Nodes and transactions page are configured.
Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial I/O Data Map 7.10.1. Optimize the I/O Data Map The optimize function is used to automatically remove gaps between the mapping. IMPORTANT Optimize remove gaps between the data objects in the map and should be used with care on already commissioned systems. Expected mapping in the PLC may change. NOTE If you optimize the I/O data map, the current I/O data map will be overwritten. Figure 61. I/O data map page, Optimize To optimize the map: 1.
Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial I/O Data Map 7.10.2. Map Area Transactions Order To change the order of the transactions in a map area, drag and drop the desired transaction to a new location. Figure 62. I/O data map, change the order of transactions Transactions can not share the same I/O are. If multiple transactions are placed in the same I/O area, the area is highlighted. Figure 63. Highlighted I/O area Page 80 of 134 SCM-1202-177 1.
I/O Data Map Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial 7.10.3. Map Area Figure 64. I/O data map page, Map area options Map area options You must specify the map area to use for each transaction in the I/O data map. Select one of the following Map area options: • Input/Output: The transaction data is sent/recieved to/from the high level network. • General: This area is used for transferring transaction data between individual nodes on the subnetwork.
Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial I/O Data Map How to Enable Trigger Byte on a Node Procedure 1. Navigate to the Nodes & transactions page. 2. Select the decried node and transaction. 3. In the transaction sidebar Update mode menu, select Change of state on trigger. 4. Navigate to the I/O data map page. 5. The transaction with the trigger byte enabled is marked with a flash icon. To open the Map Area sidebar, click on the flash icon. 6.
Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial I/O Data Map 3. Select the swapping type from the Endian swap drop-down menu. Setting Description No swapping Default setting Byte swap Swap 2 bytes Word swap Swap 4 bytes No swapping is performed on the data. A B C D becomes B A D C A B C D becomes C D A B Byte and Word swap 4. A B C D becomes D C B A To apply the settings, click Apply in the web-interface header, and follow the instructions. 7.10.6. Offline Option Figure 67.
Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial I/O Data Map 7.10.7. Live List Figure 68. I/O data map page, Live list enabled By default Live list is disabled. When Live list is enabled, the first four bytes of process data on the PROFIBUS network contain the live list. The Live list holds 32 bits. Each bit in the Live list can hold the status for a total of 32 nodes connected to the Communicator. The bit is 0 when the bit does not correspond to the configured node.
I/O Data Map Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial When Data exchange control is enabled, the first four bytes of process data on the PROFIBUS network contain the data exchange control. The Data exchange control holds 32 bits. Each bit in the Data exchange control can be used to enable/disable data exchange for individual nodes on the subnetwork. If control bit does not correspond to a configured node, the control bit is ignored.
Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial Apply Configuration 7.11. Apply Configuration Before You Begin NOTE When you apply the configuration, any existing configuration is overwritten. Figure 70. Disconnect the Communicator from the PROFIBUS network Before you can apply the configuration, ensure that there is no active communication on the PROFIBUS network where the Communicator is connected. Procedure To make the settings take effect, download the configuration to the Communicator: 1.
Apply Configuration Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial 2. To confirm download, click Apply. • The configured settings are downloaded and applied to the system. SCM-1202-177 1.
Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial To Use an Existing Configuration 7.12. To Use an Existing Configuration When you have configured a Communicator and want to use the same settings to configure additional Communicator, do the following. Procedure Figure 71. Files & firmware page In the built-in web-interface of the Communicator with the configuration you want to use: 1. On the Files & firmware page, click Export The configuration is saved in an conf file and downloaded to your PC.
To Use an Communicator Classic Configuration Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial 7.13. To Use an Communicator Classic Configuration Before You Begin NOTE Only the Communicator Classic serial configuration settings can be imported. The I/O data map and high-level network settings are not supported and must be set manually in the Communicator built-in web interface.
Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial To Use an Communicator Classic Configuration 3. In the Open dialog box, browse to and select the configuration .cfg file and click Open. 4. If you want to import a name file, click Select name file (.cfx). 5. In the Open dialog box, browse to and select the configuration .cfx file and click Open. 6. To import the configuration, click Import. Figure 73. Example, selected .cfg and .
PLC Configuration Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial 8. PLC Configuration 8.1. Export I/O Data Map When configuring the communication between the PLC and the nodes on the subnetwork, use the I/O data map as a specification to ensure that the transactions match. Figure 75. I/O data map page On the I/O data map page you can export the I/O data map in an Excel XLS file, where all the nodes and transactions are listed. To export the I/O data map: 1. Click Export.
Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial How to Use GSD File Modules 8.3. How to Use GSD File Modules When configuring the PROFIBUS communication, ensure that the I/O sizes in the PROFIBUS master match the I/O sizes sett on the Communicator PROFIBUS page, see High Level Network Settings (page 76). Import the Communicator GSD file into TIA portal and combine the modules to get the correct I/O size. NOTE Fill unused module slots with the value Empty. Table 1.
How to Use GSD File Modules Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial Example 9. Fill unused module slots The gateway cannot move positions and it expects data of a certain size at each position between the combine modes. Therefore, unused module slots needs to be filled with the value Empty. In this example we use an I/O size of 35 bytes. Combine modes: 1 + 2 + 32 To fill the positions, we add Empty where the Combine modes 4, 8, 16, 64 and 128 are expected.
Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial Verify Operation 9. Verify Operation Before You Begin Ensure that the Communicator is connected to your PC, to a power supply and to the OT network. See Installation (page 13). 9.1. Communicator Status Monitor On the Home page, you can get a quick overview of the network and the Communicator operating status. Figure 78. Home page Gateway status Overview the Communicator LED indications remotely. Refer to Communicator LED Indicators (page 96).
Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial Communicator Status Monitor Status Symbols Symbol Description Internal error has occurred and operation cannot be guaranteed. Out of Specification. Check Function: • Initial state where non network components are started and configured. • Network startup in progress. • Invalid configuration detected. Normal operation. SCM-1202-177 1.
Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial Communicator LED Indicators 9.2. Communicator LED Indicators NOTE Before you can verify operation you must configure the Communicator. Figure 79.
Use Cases Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial 10. Use Cases 10.1. Temperature Regulator - Modbus RTU Use Case 10.1.1. About the Use Case The purpose of this use case is to explain how to use the Modbus RTU serial protocol. In this use case we use the Communicator to enable data exchange between an Temperature Regulator and a PLC. The use case describes how to map the communication in the Communicator.
Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial Temperature Regulator - Modbus RTU Use Case 10.1.3. Choose Serial Protocol Type The Temperature Regulator is using a request/response protocol to access parameters addressed with index and sub index. Figure 81. Communication page, Modbus RTU • On the Serial RS232/485 page, select Modbus RTU. 10.1.4. Setup Serial Communication Set up the communication between the Communicator and the Temperature Regulator.
Temperature Regulator - Modbus RTU Use Case Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial 10.1.5. Set Up the Node Figure 83. Add the Temperature Regulator node 1. Add a node and select it. 2. In Node settings, configure the node with the following settings: Node settings Value Slave address 240 Name Temp Regulator Timeout time 1000 ms Reconnection time 1000 ms Retries 1 Address format Register SCM-1202-177 1.
Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial Temperature Regulator - Modbus RTU Use Case 10.1.6. Setup the Transactions Set up the communication between the node and the master. In this example, the communication between the Temperature Regulator and the PLC. The Temperature Regulator has two Modbus transactions: • One registers holding the setpoint temperature. • One registers holding the actual temperature. Configure the temperature setpoint transaction Figure 84.
Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial Temperature Regulator - Modbus RTU Use Case Configure the actual temperature transaction Figure 85. Actual temperature transaction 1. 2. 3. To add a second transaction, click Add. Select the transaction to configure. In the transaction sidebar, on the right side of the screen. Enter values for the transaction settings. Table 4.
Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial Temperature Regulator - Modbus RTU Use Case 10.1.7. Check the I/O Data Map The transactions to and from the Temperature Regulator are mapped as follows in the I/O data map page. Figure 86. I/O data map Address Data to PROFIBUS 0-1 Setpoint temperature from PROFIBUS to the Temperature Regulator. Address Data from PROFIBUS 0-1 Actual temperature speed from the Temperature Regulator to PROFIBUS. Page 102 of 134 SCM-1202-177 1.
AC Motor Drive - Custom Request/Response Use Case Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial 10.2. AC Motor Drive - Custom Request/Response Use Case 10.2.1. About the Use Case The purpose of this use case is to explain how to use the Custom Request/Response serial protocol. Figure 87. AC Motor Drive - Custom Request/Response Use Case In this use case we use the Communicator to enable data exchange between an AC motor, of the type My Drive, and a PLC.
Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial AC Motor Drive - Custom Request/Response Use Case 10.2.3. Choose Serial Protocol Type My Drive is using a request/response protocol to access parameters addressed with index and sub index. Figure 88. Communication page, Custom Request/Response • On the Serial RS232/485 page, select Custom Request/Response. 10.2.4. Setup Serial Communication Set up the communication between the Communicator and My Drive.
AC Motor Drive - Custom Request/Response Use Case Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial 10.2.5. Create Transaction Templates All frames are verified using a CRC-16-IBM checksum. My Drive is using a request/response protocol to access parameters addressed with index and sub index. Map up control word, speed from PROFIBUS to My Drive and status word and actual speed from the drive to PROFIBUS.
Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial AC Motor Drive - Custom Request/Response Use Case 3. In the Frame editor Request area, add five frame objects with the following settings: Table 6.
Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial AC Motor Drive - Custom Request/Response Use Case Create Write Parameter (0x02) The Communicator writes values delivered from the PLC to the My Drive node. Figure 91. Write Parameter (0x02) 1. Add an Empty template and select it. 2. Name the template Write parameter (0x02). 3. In the Frame editor Request area, add six frame objects with the following settings: Table 8.
Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial AC Motor Drive - Custom Request/Response Use Case 4. In the Frame editor Response area, add five frame objects with the following settings: Table 9.
AC Motor Drive - Custom Request/Response Use Case Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial 10.2.6. Setup Node and Transactions Figure 92. My Drive node with transactions 1. Add a node and select it. 2. In Node settings configure the node with the following settings: Node settings Value Node address 1 My Drive is set up as a node with Node address 1. Name My Drive Timeout time 1000 ms (default) Reconnecting time 1000 ms (default) Retries 0 (default) 3.
Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial AC Motor Drive - Custom Request/Response Use Case 10.2.7. Check the I/O Data Map The control word, speed from PROFIBUS to My Drive and status word and actual speed from My Drive to PROFIBUS are mapped as follows in the I/O data map page. Figure 93. I/O data map Table 11. Control word and speed from PROFIBUS to My Drive Address Drive Parameter 0-1 Control Word 2-3 Speed Table 12.
Barcode Scanner - Custom Produce/Consume Use Case Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial 10.3. Barcode Scanner - Custom Produce/Consume Use Case 10.3.1. About the Use Case The purpose of this use case is to explain how to use the Custom Produce/Consume serial protocol. In this use case we use the Communicator to enable data exchange between an Barcode Scanner and a PLC. The use case describes how to map the communication in the Communicator.
Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial Barcode Scanner - Custom Produce/Consume Use Case 10.3.3. Choose Serial Protocol Type The purpose of this use case is to explain how to use the Custom Produce/Consume serial protocol. Figure 95. Communication page, Custom Produce/Consume • On the Serial RS232/485 page, select Custom Produce/Consume. 10.3.4. Setup Serial Communication Set up the communication between the Communicator and Barcode Scanner.
Barcode Scanner - Custom Produce/Consume Use Case Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial 10.3.5. Create Transaction Templates Create Read Barcode Data Parameter Before You Begin The Communicator reads values delivered from to the Barcode Scanner node on to the PLC. The Barcode Scanner sends data whenever it is available, without any request or handshake from the Communicator. Figure 97.
Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial Barcode Scanner - Custom Produce/Consume Use Case Procedure Figure 98. Read Barcode Data Parameter 1. 2. 3. Add an Empty consume template and select it. Name the template Read Barcode Data. In the Frame editor, add four frame field with the following settings: Table 14.
Barcode Scanner - Custom Produce/Consume Use Case Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial 10.3.6. Setup Node and Transactions Figure 99. Node settings 1. 2. Add a node and select it. In Node settings configure the node with the following settings: Node settings 3. Value Node address The Barcode Scanner is set up as a node with Node address 1.
Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial Barcode Scanner - Custom Produce/Consume Use Case 10.3.7. Check the I/O Data Map The transactions from the Barcode Scanner is mapped as follows in the I/O data map page. Figure 100. I/O data map Table 16. Status word and actual speed from My Drive to PROFIBUS Address Barcode Scanner Parameter 0-31 The variable data, 31 bytes, are forwarded from the Barcode Scanner to the PLC. Page 116 of 134 SCM-1202-177 1.
Maintenance Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial 11. Maintenance 11.1. Configuration File Handling 11.1.1. Export Configuration You can export the current configuration, in order to import and use the same settings to configure additional Communicator. Figure 101. Files & firmware page To export a configuration file: • In Files & firmware, click Export. The configuration settings are stored in a .conf file and downloaded to your PC. SCM-1202-177 1.
Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial Configuration File Handling 11.1.2. Import Configuration To easily configure multiple Communicator with the same settings, you can import a configuration file. Before You Begin NOTE Importing a configuration replaces the current applied configuration. The supported file format is .conf. Procedure Figure 102. Files & firmware page Import configuration file: 1. 2. 3. 4. 5. On the Files & firmware page, click Import.
Clear and Revert Configuration Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial 11.2. Clear and Revert Configuration You can restore all settings in a configuration to the default settings. Procedure Figure 103. Files & firmware page When you want to clear a configuration and return to the default settings. To clear the configuration: 1. 2. 3. On the Files & firmware page, click Clear. In the Confirm clear window, click Clear.
Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial Firmware Management 11.3. Firmware Management 11.3.1. View the Firmware Version On the Support page, you can view the current applied firmware version. Figure 104. Support page, Product information example 11.3.2. Firmware and Configuration Compatibility Compatibility after firmware upgrade Current configuration is still compatible after upgrading the firmware.
Firmware Management Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial 11.3.4. Update Firmware Before You Begin IMPORTANT To eliminate the risk of interference with plant operation, firmware update is only available when the Communicator is disconnected from the OT networks. Ensure that the Communicator is disconnected from the OT networks. Procedure Figure 105. Files & firmware page To update the firmware: 1. 2. 3. 4. On the Files & firmware page, click Upload.
Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial Troubleshooting 12. Troubleshooting 12.1. Diagnostics 12.1.1. Serial RS-232/485 Data Monitor On the Serial RS-232/485 page you can monitor how the data flow between the nodes and the gateway changes over time. Figure 106. Serial RS-232/485 page The table can contain at most 10000 messages. When the limit is reached, the oldest messages are discarded when new messages are added.
Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial Diagnostics 12.1.2. Event Log Figure 107. Event log page How To Analyze the Information The log follows the FIFO principle, first in and first out. The oldest (first) value is processed first. Time (d:hh:mm:ss.ms) The date and time when the event occurred. Message A brief description of the event. Severity The severity of the event occurred. For description of the symbols, see Communicator Status Monitor (page 94).
Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial Diagnostics 12.1.3. LED Status On the Home page, you can remotely monitor the Communicator LED status. Figure 108. Home page For information about the LED indication, see Communicator LED Indicators (page 96). Page 124 of 134 SCM-1202-177 1.
Reset to Factory Settings Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial 12.2. Reset to Factory Settings Before You Begin Factory reset will reset any on site made configuration changes and set the Communicator to the same state as leaving HMS production. If the Firmware has been updated, factory reset will revert the Communicator configuration to initial state after the update. Procedure To reset the Communicator: 1. Disconnect the Communicator from power. Figure 109. Disconnect power 2.
Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial 3. Reset to Factory Settings While holding the reset button, reconnect the Communicator to power. Figure 111. Hold Reset button and reconnect power 4. Release the reset button. The Communicator enters exception state. 5. Reboot the Communicator. Result • When the Communicator has successfully rebooted, the Communicator configuration is reset to the factory default configuration or the current configuration after firmware upgrade.
Firmware Upgrade Error Management Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial 12.3. Firmware Upgrade Error Management If the firmware update process is interrupted or if the power is lost during the update process, the Communicator goes into fallback mode. The last working firmware is still available on the flash, but it is not active. Procedure To complete the interrupted firmware update: 1. Disconnect the Communicator from power. Figure 113. Disconnect power 2.
Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial Firmware Upgrade Error Management 3. Leave the Communicator for 10 minutes. The Gateway status led indicator flashes red and green until the firmware upgrade is completed. Figure 115. Firmware upgrade LED indication Result The Communicator recover and return to normal operation. Figure 116. Recover and return to normal operation To Do Next To check LED status, refer to Communicator LED Indicators (page 96). Page 128 of 134 SCM-1202-177 1.
Support Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial 12.4. Support 12.4.1. Support Package Figure 117. Support page Before you create a ticket for technical support, generate a support package. The support package contains information about what has occurred and will help the Anybus technical support team resolve the support case as quickly and efficiently as possible.
Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial Technical Data 13. Technical Data For complete technical specifications and regulatory compliance information, please visit www.anybus.com/support. 13.1.
Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial Reference Guides 14. Reference Guides 14.1. About Input Registers and Holding Registers Modbus data is most often read and written as registers which are 16-bit pieces of data. Holding registers and Input registers are both 16-bit registers. Input registers Input registers can only be read. Holding registers Holding registers can be read or written.
Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial Modus Exception Codes 14.4. Modus Exception Codes Exception Code Name Description 01 Illegal Function The server does not recognize or permit the function code. 02 Illegal Data Address The data address (register, discrete input or coil number) is not an permitted address for the server. If multiple registers were requested, at least one was not permitted. Reference: MODBUS Application Protocol Specification V1.
RS485/RS232 Electrical Connection Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial 14.6. RS485/RS232 Electrical Connection 14.6.1. RS485 Typical Connection Figure 118. RS485 14.6.2. RS232 Typical Connection Figure 119. RS232 SCM-1202-177 1.
This page is intentionally left blank.
