Anybus® Communicator™ PROFINET to Modbus RTU/Serial USER MANUAL SCM-1202-176 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.
Table of Contents 1 2 3 4 5 6 Page Preface ................................................................................................................................. 5 1.1 About This Document .......................................................................................................5 1.2 Document Conventions .....................................................................................................5 1.3 Trademarks......................................................
7 8 9 Communicator Configuration ........................................................................................... 31 7.1 Connecting the Communicator ......................................................................................... 31 7.2 Access the Built-In Web Interface From HMS IPconfig........................................................... 32 7.3 Access the Built-In Web Interface From a Web Browser ........................................................ 34 7.
13 Technical Data ................................................................................................................. 119 13.1 A Technical Specifications................................................................................................. 119 Reference Guides ............................................................................................................ 121 A.1 About Input Registers and Holding Registers .............................................................
This page intentionally left blank
Preface 5 (124) 1 Preface 1.1 About This Document This manual describes the installation and configuration of the Anybus Communicator. For additional documentation and software downloads, FAQs, troubleshooting guides and technical support, please visit www.anybus.com/support. 1.2 Document Conventions Numbered lists indicate tasks that should be carried out in sequence: 1. First do this 2.
Safety 6 (124) 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.
Preparation 7 (124) 3 Preparation 3.1 Cabling Have the following cables available: • Ethernet cable for configuration • Ethernet cable for connecting to the high level network • Power cable 3.2 System Requirements 3.2.1 Supported Operating Systems 3.2.
Preparation 3.5 8 (124) 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. As an alternative, you can set a static IP address within the same IP address range as the Communicator IP address on the computer accessing the Communicator built-in web interface.
About Anybus Communicator 4 About Anybus Communicator 4.1 Serial Protocol Communication 4.1.1 Serial Protocol Types 9 (124) The gateway features three distinct modes of operation for the subnetwork communication, called Modbus RTU, Custom Request/Response and Custom Produce/Consume. Modbus RTU By default the Communicator uses the Modbus RTU serial protocol. The Communicator uses Modbus transactions defined by the Modbus standard.
About Anybus Communicator 4.1.2 10 (124) Serial Protocol Building Blocks The following building blocks are used to describe the subnetwork communication. Node A node represents a single device on the subnetwork. Each node can be associated with a number of transactions.
About Anybus Communicator 11 (124) Frame fields are low level entities used to compose transactions. A frame field can represent a: • fixed value, a constant • range of values, limit objects • block of data or a calculated checksum Transaction Templates The Transaction templates are available when either the Custom Request/Response or Custom Produce/Consume serial protocol is enabled. A transaction represents a complete serial telegram, and consists of a number of frame fields.
About Anybus Communicator 12 (124) Examples: If you have a common read transaction. Then you can create one single transaction template for the read transaction and reuse it multiple times times on your node(s). If you have a function code in your protocol similar to a standard Modbus RTU transaction. Then you can create a transaction template based on the Modbus RTU transaction for the read operation.
About Anybus Communicator 4.2 13 (124) 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. 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.
About Anybus Communicator 14 (124) Request process data Request process data from the serial subnetwork nodes, specified in the Communicator configuration, and make the process data available on the server interface and for the high level network client device. Transfer process data 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.
About Anybus Communicator 4.3 15 (124) How the Data Exchange Works 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. The same memory locations are exchanged on the serial subnetwork.
Installation 16 (124) 5 Installation 5.1 External Parts A. Power connector E. 7-pin connector I. Security switch B. Label with LED designation F. Ethernet port x 2 J. Factory reset button C. Status LEDs G. Cable tie mount K. D. Configuration port H. Laser engraved connectors designation Laser engraved label with product information L. DIN rail locking mechanism Anybus® Communicator™ User Manual SCM-1202-176 1.
Installation 5.2 17 (124) DIN Rail Mounting 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. 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. Anybus® Communicator™ User Manual SCM-1202-176 1.
Installation 5.3 18 (124) Connecting to PROFINET Network 1. Connect the Communicator to your PROFINET network. PROFINET Connector Pin Description 1 TD+ 2 TD- 3 RD+ 4 5 6 RD- 7 8 To Do Next Connect the Communicator to the serial subnetwork and to power. Check LED status, refer to Communicator LED Indicators, p. 86. Anybus® Communicator™ User Manual SCM-1202-176 1.
Installation 5.4 19 (124) Connecting to Serial RS232/RS485 Subnetwork Use minimum 90 oC copper (Cu) wire only. 1. Insert the cable wires into the 7-pin connector and tighten the wire clamp screws. 7-pin connector Pin Signal 1 +5 V OUT 2 RS485- A 3 RS485+ B 4 Signal GND 5 Functional Earth (FE) 6 RS232 Tx Output 7 RS232 Rx Input 2. Connect the 7-pin connector to the Communicator. 3. Connect the Communicator to your serial subnetwork.
Installation 5.5 20 (124) Connecting to Power Caution Ensure that the power supply is turned off before connecting it to the equipment. Using the wrong type of power supply can damage the equipment. Ensure that the power supply is connected properly and of the recommended type. 1. Insert the cable wires to the terminal block and tighten the wire clamp screws. Power port Pin Description 1 Functional Earth (FE) 2 Ground (GND) 3 12-30 VDC Power Connector 2.
Installation 5.6 21 (124) Security Switch 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. Network specific parameters, configured via the PLC is still available.
Installation 5.7 22 (124) Locking the Cables To strain relieve the cables, place a cable tie in the holder and lock the cables. Anybus® Communicator™ User Manual SCM-1202-176 1.
Installation 5.8 23 (124) DIN Rail Demount Before You Begin 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. To unlock the Communicator DIN rail locking mechanism, turn the screwdriver clockwise. 3.
Configuration Quick Guide 6 24 (124) 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, p. 31. 6.1 Prepare Configuration 1. Connecting to the high level network Connect the Communicator to the PROFINET high level network. 2. Connecting the Communicator to the subnetwork Connect the Communicator to the serial RS232/RS485 subnetwork. 3.
Configuration Quick Guide 25 (124) 4. Finding 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. Use the software application HMS IPconfig to find the Communicator default IP address on your PC.
Configuration Quick Guide 6.2 26 (124) 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 – Custom Produce/Consume For information about the serial protocol types, refer to Serial Protocol Types, p. 9. b. Configure the basic settings Physical standard, Baud rate, Data bits, Parity and Stop bits. 2.
Configuration Quick Guide 27 (124) 4. High level network configuration On the PROFINET page: a. Use Automatic I/O sizes provided by the subnetwork or choose to set them manually. Max I/O size is 1024 bytes. b. Enable DHCP server or choose to set a specific IP address. c. Apply the IP settings. d. To be able to identify the Communicator on the PROFINET network, give the Communicator a Station name. 5.
Configuration Quick Guide 6.3 28 (124) 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 transactions match. On the I/O data map page: You can download the I/O data mapping in a spreadsheet to your PC. 2. Download GSDML File Option if the PLC program requires a GSDML (Generic Station Description Markup Language) file.
Configuration Quick Guide 29 (124) In the PLC program: 3. Import product file Option if the PLC program requires a GSDML (Generic Station Description Markup Language) file. Import the GSDML file into your PLC project. 4. Configure the communication Configure the PLC to communicate with the Communicator according to the I/O data map created in the Communicator. Anybus® Communicator™ User Manual SCM-1202-176 1.
Configuration Quick Guide 6.4 30 (124) Verify Operation 1. Apply the configuration When you have completed and verified the configuration, click Apply for the settings to take effect. 2. 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. 3.
Communicator Configuration 7 31 (124) 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 Configuration Quick Guide, p. 24. 7.1 Connecting the Communicator Procedure 1. Connect the Communicator to the high level network. 2. Connect the Communicator to the subnetwork. 3.
Communicator Configuration 7.2 32 (124) 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. The Communicator default IP address is 192.168.0.10. 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.
Communicator Configuration 5. 33 (124) To open the Communicator built-in web interface, click Open web page. Result → You are redirected to the Communicator built-in web interface Home page. Anybus® Communicator™ User Manual SCM-1202-176 1.
Communicator Configuration 7.3 34 (124) Access the Built-In Web Interface From a Web Browser Before You Begin The Communicator default IP address is 192.168.0.10. 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. When you change to a static IP address on your computer, internet access may be lost. Procedure 1.
Communicator Configuration 7.4 35 (124) Communicator Built-In Web Interface Overview Use the Communicator built-in web interface to configure, maintain and troubleshoot the Communicator. Home View the Communicator, network and node status. Apply After configuration changes are made and verified, press Apply to make the settings take effect. Serial RS-232/485 Serial Subnetwork with Nodes. Select a Serial protocol, use Modbus RTU standard transactions or create your own transaction templates.
Communicator Configuration 7.5 General Subnetwork Settings 7.5.1 Communication Serial Protocol 36 (124) 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. The transactions can be based on the Modbus communication specification or fully customized.
Communicator Configuration 7.5.2 37 (124) Communication Basic Settings Physical standard Specify the physical interface type for the device connected to the Communicator. 1. 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. RS-485 Use RS-485 when multiple nodes are connected to the subnetwork.
Communicator Configuration 38 (124) Setting Value 57600 baud 115200 baud 128000 baud 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 8 data bits and can not be changed. Parity Specify if parity should be used to detect errors in the data. 3. Select parity value from the Parity drop-down menu.
Communicator Configuration 39 (124) You can use Custom settings to set the desired Inter-telegram timeout and Inter-telegram delay. The following must be applied on all nodes: • The time between two adjacent characters in the same telegram must be less than Intertelegram timeout. • The time between two characters in two different telegrams the same or more than Intertelegram delay. Anybus® Communicator™ User Manual SCM-1202-176 1.
Communicator Configuration 7.6 40 (124) About Transaction Templates This section applies when the Custom Request/Response or Custom Produce/Consume serial protocol is applied, refer to Communication Serial Protocol, p. 36 7.6.1 Transaction Template Example Custom Request/Response Request/Response transaction template example: The transaction named Read parameter (0x01) consists of a number of frame fields. In the Request field there are three Constants, a Node address and a Checksum field.
Communicator Configuration 41 (124) Custom Produce/Consume 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. Anybus® Communicator™ User Manual SCM-1202-176 1.
Communicator Configuration 7.6.2 42 (124) Transaction Template Types There are two types of transaction templates, Empty template and Modbus template. Empty template When using the Empty template, you start with an empty transaction and build a desired structure by adding and arranging frame fields. For the produce/consume transactions you select; Empty produce template or Empty consume template. Anybus® Communicator™ User Manual SCM-1202-176 1.
Communicator Configuration 43 (124) Modbus templates Modbus templates are available for request/response and transactions. When using the Modbus template, you first select the Modbus template from which you want to start. You can then restructure the transaction by rearranging, adding or removing frame fields. Example, new transaction template based on the Modbus template Read Discrete Inputs: Anybus® Communicator™ User Manual SCM-1202-176 1.
Communicator Configuration 7.6.3 44 (124) 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. The following frame fields are available: Node address Frame field representing the Node address of the Node. A constant byte that holds a copy of the nodes address when the transaction is used by a node.
Communicator Configuration 45 (124) Checksum Most serial protocols features some way of verifying that the data has not been corrupted during transfer. The checksum frame field calculates and includes a checksum in a transaction. Anybus® Communicator™ User Manual SCM-1202-176 1.
Communicator Configuration 7.7 46 (124) Build Transaction Templates Before You Begin Ensure that you have applied the Custom Request/Response or Custom Produce/Consume serial protocol, refer to Communication Serial Protocol, p. 36. 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. Anybus® Communicator™ User Manual SCM-1202-176 1.
Communicator Configuration 47 (124) Options for the Custom Request/Response Protocol: ► To add a new empty template without any frame fields, select Empty template. Example, a new empty request/response template is added to the transaction template list: Anybus® Communicator™ User Manual SCM-1202-176 1.
Communicator Configuration ► 48 (124) To add a new template based on a standard Modbus transaction, select Modbus templates and then the desired Modbus transaction. Example, a new request/response template based on “Read Coils (1)” is added to the transaction template list: Anybus® Communicator™ User Manual SCM-1202-176 1.
Communicator Configuration 49 (124) Option for the Custom Produce/Consume Protocol: ► Select Empty produce template or Empty consume template. You can change the Transaction type after the transaction template is added. Example, 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. To Do Next ► Add frame fields to the transaction template, refer to Add Frame Fields, p. 50.
Communicator Configuration 7.7.2 50 (124) Add Frame Fields Procedure 1. In the transaction template list, select a transaction template to add frame fields to. 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. ► To duplicate a frame field: On the frame field that you want to delete, click the three dots icon and then click Duplicate. Anybus® Communicator™ User Manual SCM-1202-176 1.
Communicator Configuration 51 (124) ► To change the order of the frame fields: Drag and drop the frame fields in the list to change the 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. 3. To apply the settings, click Apply in the web-interface header, and follow the instructions. To Do Next ► Configure the frame field settings, refer to Configure Frame Field Settings, p. 52.
Communicator Configuration 7.7.3 52 (124) Configure Frame Field Settings Procedure 1. In the Transaction templates list, select a transaction template to configure. 2. In the Transaction template settings select a Field to configure. → 3. The Field sidebar opens, on the right side of the screen. Configure the Field settings. Limit can only be added as a Response frame field. Node address Frame field representing the Node address of the node.
Communicator Configuration 53 (124) Limit • 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. • Base number system: Select Decimal Dec (Default) or Hexadecimal Hex.
Communicator Configuration 54 (124) Checksum • Name: You can name the Frame Field to make it easier to identify. • Checksum type: Specify the algorithm used to calculate the checksum. Select CRC (CRC-16IBM) (Default), LRC (ISO 1155:1978), XOR or ADD. • Start offset: Specify the offset from where to start the checksum calculation. Enter a value between 0 (Default) and 511. • Error check type: Specify how the checksum is converted.
Communicator Configuration 7.7.4 55 (124) Data Delimiter and Subnet Delimiter Options In a variable data object, the length of the data field may vary depending on the type of data being read in a specific case. In order to present the variable data correctly on the corresponding network, the length of the data field must be identified. In a Variable data object, there are three ways to identify the data length; by length character, end character or length of message.
Communicator Configuration 2. 56 (124) In the Data delimiter and/or Subnet delimiter drop down menu, select one of the following options: – Byte counter The data packet consists of a length character, indicating the length of the data section, followed by the variable data object itself. In order to copy the exact data size from the transaction message, the length of the variable data object is first identified. In this example we have added a length character with 4 bytes of data.
Communicator Configuration 7.7.5 57 (124) Store Transaction Templates The transaction templates are stored on the Transaction templates page. The transaction templates are available for use on the Nodes & transaction page, when you add transactions to a node. For information on how to add the transaction templates to the nodes, refer to Transaction Settings, p. 64. Anybus® Communicator™ User Manual SCM-1202-176 1.
Communicator Configuration 7.8 58 (124) 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. Broadcast node • You can add one single Broadcast node.
Communicator Configuration 7.8.2 59 (124) Add Node You can add one single Broadcast node. The maximum number of Nodes that can be added is 31. Procedure 1. In the web-interface left sidebar menu, click Nodes & transactions. 2. Click Add node . 3. Select Add broadcast node or Add node. → A new node/brodcats node is added to the nodes list. To Do Next Configure the Node Settings, Node Settings, p. 60. Anybus® Communicator™ User Manual SCM-1202-176 1.
Communicator Configuration 7.8.3 60 (124) 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 1. In the nodes list, select a node to configure. Anybus® Communicator™ User Manual SCM-1202-176 1.
Communicator Configuration 2. 61 (124) Configure the Node settings. Setting Value Description Node address 1 to 247 Node ID, also called node address, is the node’s identity on the subnetwork. The node id is a number between 1 and 247. By default, the node is assigned the next available number. The same node id cannot be used on multiple nodes. Name N/A By default, the node is assigned the name New node and the corresponding Server address. The node name can be changed.
Communicator Configuration 7.8.4 62 (124) Add Transactions The maximum number of transactions that can be added to a node is 150. 1. In the nodes list, select a node to configure. 2. In the transactions list, click Add. 3. Choose one of the following alternative: When using the Modbus RTU Serial Protocol ► Click Add and select a transaction from the list of standard Modbus RTU transactions.
Communicator Configuration ► 63 (124) 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. You need to build the transactions before you can use the template, refer to Build Transaction Templates, p. 46. ► 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.
Communicator Configuration 7.8.5 64 (124) Transaction Settings Before You Begin When a custom transaction is selected, the custom transaction template is locked for editing. For Modbus transaction reference guide, refer to Modbus Transactions, p. 121. Procedure Modbus RTU Protocol: Custom Request/Response Protocol: 1. In the nodes list, select a node to configure. 2. In the transactions list, select a transaction to configure. → 3. The transaction sidebar opens, on the right side of the screen.
Communicator Configuration 5. 65 (124) Configure the Transaction 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 in the read data field. Appear when Modbus transaction Read Write Multiple Registers (23) is selected. Address 0 to 65 535 Specify the start address for the read/write transaction.
Communicator Configuration 7.8.6 66 (124) 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. To duplicate: 7.8.8 • One transaction, select the transaction and click Duplicate. • Multiple transactions, select the checkbox in front of each transaction you want to duplicate and click Duplicate.
Communicator Configuration 7.9 67 (124) High Level Network Settings Configure the PROFINET network settings. 7.9.1 To Use Automatic I/O Sizes By default, the Communicator is set to use automatic I/O sizes. The size of the input data, Data Size to PROFINET, and the output data, Data Size from PROFINET, is determined by the subnetwork configuration. The Data sizes can be between 0-1024 bytes. In the Communicator built-in web interface, the Use Automatic I/O Sizes checkbox is selected. 7.9.
Communicator Configuration 7.9.3 68 (124) To Use DHCP Server By default, the IP settings are provided by the high level network DHCP server. The DHCP enabled checkbox is selected. Default Communicator IP Settings The Communicator comes with the following factory default IP settings: Setting Default value Web configuration IP address 192.168.0.10 Subnet mask 255.255.255.0 Gateway address There is no default Gateway address. Primary DNS server There is no default Primary DNS server.
Communicator Configuration 7.9.4 69 (124) To Configure IP Settings Manually 1. Deselect the DHCP enabled checkbox. 2. Configure the IP settings. Setting Description IP address The PROFINET network IP address in IPv4 dot-decimal notation Subnet mask The PROFINET network Subnet mask in IPv4 dot-decimal notation. Gateway address ThePROFINET network Gateway address in IPv4 dot-decimal notation. If there is no gateway available, set the Gateway address to: 0.0.0.
Communicator Configuration 7.11 70 (124) Station Name A PROFINET device is identified by its Station name in the PROFINET network. Enter a Station name for the Communicator. 7.12 • The maximum allowed length of the Station name is 240 characters. • No symbol characters, punctuation characters, or whitespace are permitted. • Write the Station name as one single word.
Communicator Configuration 7.12.1 71 (124) Optimize the I/O Data Map The optimize function is used to automatically remove gaps between the mapping. 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. If you optimize the I/O data map, the current I/O data map will be overwritten. To optimize the map: 1. Click Optimize. 2. To confirm, click OK. Anybus® Communicator™ User Manual SCM-1202-176 1.
Communicator Configuration 7.12.2 72 (124) 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. Transactions can not share the same I/O are. If multiple transactions are placed in the same I/O area, the area is highlighted. Anybus® Communicator™ User Manual SCM-1202-176 1.
Communicator Configuration 7.12.3 73 (124) Map Area 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. When General is selected, the transaction data cannot be accessed from the high level network.
Communicator Configuration 7.12.4 74 (124) Trigger Byte Trigger byte is used to enable/disable the trigger functionality for the response. When Trigger byte is enabled, the Communicator increases the trigger byte by one when the Communicator receives new data from the subnetwork. The Trigger byte is stored in the Data from PROFINET area or the General area. The location of the trigger byte is specified by the address. How to Enable Trigger Byte on a Node Procedure 1.
Communicator Configuration 7.12.5 75 (124) Endian Swap In most PLCs, PROFINET can be configured to use either Little-endian format or Big-endian format. Big-endian The big-endian format places the most significant byte of the data at the byte with the lowest memory address. Little-endian The little-endian format places the least significant byte of the data at the byte with the lowest memory address. To convert between big-endian and little-endian you must reverse the byte order.
Communicator Configuration 7.12.6 76 (124) Offline Option Offline mode is used to define what data to send if the network connection or connection with a specific node is lost. You must specify the offline mode to use for each transaction on the I/O data map. Select one of the following Offline options: • Clear (Default): The data is cleared and the value 0 is sent. • Freeze: The Communicator holds the value until the connection is restored.
Communicator Configuration 7.12.7 77 (124) Live List By default Live list is disabled. When Live list is enabled, the first four bytes of process data on the PROFINET 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. For example, this occurs when the number of configured nodes is less than 32.
Communicator Configuration 7.12.8 78 (124) Data Exchange Control By default Data exchange control is disabled. When Data exchange control is enabled, the first four bytes of process data on the PROFINET 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.
Communicator Configuration 7.13 79 (124) Apply Configuration Before You Begin When you apply the configuration, any existing configuration is overwritten. Disconnect the Communicator from the PROFINET network Before you can apply the configuration, ensure that there is no active communication on the PROFINET network where the Communicator is connected. Procedure To make the settings take effect, download the configuration to the Communicator: 1. In the web-interface header, click Apply 2.
Communicator Configuration 80 (124) If you have made changes to the IP settings you are prompted to apply these settings. 3. To apply the IP settings, click Apply IP settings. Anybus® Communicator™ User Manual SCM-1202-176 1.
Communicator Configuration 7.14 81 (124) Use an Existing Configuration When you have configured a Communicator and want to use the same settings to configure additional Communicators, do the following. Procedure 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. In the built-in web-interface of the new Communicator to be configured: 2.
PLC Configuration 82 (124) 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. In the Communicator built-in web-interface: On the I/O data map page you can exported 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. → 8.
PLC Configuration 8.3 83 (124) Configure the PROFINET Connection Before You Begin • Configure the Communicator, refer to Communicator Configuration, p. 31. • Download the PROFINET GSDML file from the Communicator built-in web interface, refer to Export Product GSDML File, p. 82. Procedure To configure the PROFINET connection: 1. Import the PROFINET GSDML file into your PLC configuration tool. 2. Select the input module and output module.
Verify Operation 9 84 (124) Verify Operation Before You Begin Ensure that the Communicator is connected to your PC, to a power supply and to the OT network. Refer to Installation, p. 16. 9.1 Communicator Status Monitor On the Home page, you can get a quick overview of the network and the Communicator operating status. Gateway status Overview the Communicator LED indications remotely. Refer to Communicator LED Indicators, p. 86. Node Status Overview the status for each node added to the subnetwork.
Verify Operation 85 (124) 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. Anybus® Communicator™ User Manual SCM-1202-176 1.
Verify Operation 9.2 86 (124) Communicator LED Indicators Before you can verify operation you must configure the Communicator.
Verify Operation 9.3 87 (124) Ethernet LED Indicators LED A Off Function No link (or no power) Green Link (100 Mbit/s) established Green, flashing Activity (100 Mbit/s) Yellow Link (10 Mbit/s) established Yellow, flashing Activity (10 Mbit/s) LED B Off Function Not used Anybus® Communicator™ User Manual SCM-1202-176 1.
Use Cases 88 (124) 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. The Temperature Regulator is connected to the serial subnetwork via a custom RS-232 protocol.
Use Cases 10.1.3 89 (124) Choose Serial Protocol Type The Temperature Regulator is using a request/response protocol to access parameters addressed with index and sub index. ► 10.1.4 On the Serial RS232/485 page, select Modbus RTU. Set Up Serial Communication Set up the communication between the Communicator and the Temperature Regulator. In the Serial RS232/485 page, configure the Communication settings.
Use Cases 10.1.5 90 (124) Set Up the 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 Anybus® Communicator™ User Manual SCM-1202-176 1.
Use Cases 10.1.6 91 (124) Set Up 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. Procedure 1. Select the Temp Regulator node. Configure the temperature setpoint transaction: 2. To add a transaction, click Add. 3.
Use Cases 92 (124) Configure the actual temperature transaction: 5. To add a second transaction, click Add. 6. Select the transaction to configure. 7. In the transaction sidebar, on the right side of the screen. Enter values for the transaction settings. Actual temperature transaction settings: Setting Value Description Transactio name Actual Temp Give the transaction a name.
Use Cases 10.1.7 93 (124) 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. Address Data to PROFINET 0–1 Setpoint temperature from PROFINET to the Temperature Regulator. Address Data from PROFINET 0–1 Actual temperature speed from the Temperature Regulator to PROFINET. Anybus® Communicator™ User Manual SCM-1202-176 1.
Use Cases 94 (124) 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. In this use case we use the Communicator to enable data exchange between an AC motor, of the type My Drive, and a PLC. The use case describes how to map the communication in the Communicator. My Drive is connected to the serial subnetwork via a custom RS-485 protocol.
Use Cases 10.2.3 95 (124) Choose Serial Protocol Type My Drive is using a request/response protocol to access parameters addressed with index and sub index. ► 10.2.4 On the Serial RS232/485 page, select Custom Request/Response. Set Up Serial Communication Set up the communication between the Communicator and My Drive. In the Serial RS232/485 page, configure the Communication settings.
Use Cases 10.2.5 96 (124) 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 PROFINET to My Drive and status word and actual speed from the drive to PROFINET. Create Read parameter (0x01) The Communicator reads values delivered from to the My Drive node on to the PLC. 1. Add an Empty template and select it. 2.
Use Cases 97 (124) 4.
Use Cases 98 (124) Create Write Parameter (0x02) The Communicator writes values delivered from the PLC to the My Drive node. 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 fields with the following settings: Request frame fields 4.
Use Cases 10.2.6 99 (124) Set Up Node and Transactions 1. Add a node and select it. 2. In Node settings configure the node with the following settings: 3. Node settings Value Node address 1 My Drive is set up as a node with Node address 1.
Use Cases 10.2.7 100 (124) Check the I/O Data Map The control word, speed from PROFINET to My Drive and status word and actual speed from My Drive to PROFINET are mapped as follows in the I/O data map page. Control word and speed from PROFINET to My Drive Address Data to PROFINET 0-1 Control Word 2-3 Speed Status word and actual speed from My Drive to PROFINET Address Data from PROFINET 0-1 Control Word 2-3 Speed Anybus® Communicator™ User Manual SCM-1202-176 1.
Use Cases 101 (124) 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. The Barcode Scanner is connected to the serial subnetwork via a custom RS-232 protocol.
Use Cases 10.3.3 102 (124) Choose Serial Protocol Type The Barcode Scanner is using a produce/consume protocol to access parameters addressed with index and sub index. ► 10.3.4 On the Serial RS232/485 page, select Custom Produce/Consume. Set Up Serial Communication Set up the communication between the Communicator and the Barcode Scanner. In the Serial RS232/485 page, configure the Communication settings.
Use Cases 10.3.5 103 (124) 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. In this example we have added three frame fields for the barcode data transaction: • One Variable data frame for the length of the barcode. We use a fixed value.
Use Cases 104 (124) Procedure 1. Add an Empty consume template and select it. 2. Name the template Read Barcode Data. 3.
Use Cases 105 (124) Set Up Node and Transactions 1. Add a node and select it. 2. In Node settings configure the node with the following settings: 3. Node settings Value Node address The Barcode Scanner is set up as a node with Node address 1.
Maintenance 106 (124) 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 Communicators. To export a configuration file: 1. In Files & firmware, click Export. → The configuration settings are stored in a .conf file and downloaded to your PC. Anybus® Communicator™ User Manual SCM-1202-176 1.
Maintenance 11.1.2 107 (124) Import Configuration To easily configure multiple Communicators with the same settings, you can import a configuration file. Before You Begin Importing a configuration replaces the current applied configuration. Supported file format is .conf. Procedure Import configuration file: 1. On the Files & firmware page, click Import. 2. In the Import configuration window, click Select file (.conf). 3.
Maintenance 11.2 108 (124) Clear and Revert Configuration You can restore all settings in a configuration to the default settings. Procedure To clear the configuration: 1. On the Files & firmware page, click Clear. 2. In the Confirm clear window, click Clear. 3. To apply the change, click Apply in the web-interface header, and follow the instructions. You can revert all changes done to the settings in the current configuration. To Revert the configuration: 1.
Maintenance 11.3.2 109 (124) Firmware and Configuration Compatibility Compatibility after firmware upgrade Current configuration is still compatible after upgrading the firmware. Compatibility after firmware downgrade Compatibility after a firmware downgrade can not be guaranteed. The current configuration may use features not available in the older firmware version. Anybus® Communicator™ User Manual SCM-1202-176 1.
Maintenance 11.3.
Troubleshooting 111 (124) 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. The table can contain at most 10000 messages. When the limit is reached, the oldest messages are discarded when new messages are added. Choose how data is displayed To choose if the data should be displayed in Hexadecimal, Decimal or ASCII, click Hex, Dec or Ascii.
Troubleshooting 12.1.2 112 (124) Event Log 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, refer to Communicator Status Monitor, p. 84.
Troubleshooting 12.1.3 113 (124) LED Status On the Home page, you can remotely monitor the Communicator LED status. For information about the LED indication, refer to Communicator LED Indicators, p. 86. Anybus® Communicator™ User Manual SCM-1202-176 1.
Troubleshooting 12.2 114 (124) 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. 2. Use a pointed object, such as a ballpoint pen to press and hold the reset button.
Troubleshooting 115 (124) 3. While holding the reset button, reconnect the Communicator to power. 4. Release the reset button. → 5. The Communicator enters Exception state. 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. Anybus® Communicator™ User Manual SCM-1202-176 1.
Troubleshooting 12.3 116 (124) 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. To complete the interrupted firmware update: 1. Disconnect the Communicator from power. 2. Reconnect the Communicator to power. Anybus® Communicator™ User Manual SCM-1202-176 1.
Troubleshooting 3. 117 (124) Leave the Communicator for 10 minutes. The Gateway status led indicator flashes red and green until the firmware upgrade is completed. Result → The Communicator recover and return to normal operation. To check LED status, refer to Communicator LED Indicators, p. 86. Anybus® Communicator™ User Manual SCM-1202-176 1.
Troubleshooting 118 (124) 12.4 Support 12.4.1 Support Package Before you create a ticket for technical support, generate a support package. The support package contain information about what has occurred and will help the Anybus technical support team resolve the support case as quickly and efficiently as possible. Support Package Content The information in the support package are available to open and read, the files are not locked or encrypted. Generate Support Package 1.
Technical Data 119 (124) 13 Technical Data 13.
This page intentionally left blank
Appendix A: Reference Guides 121 (124) A Reference Guides A.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. These registers can be used for a variety of things such as inputs, outputs, configuration data, or other requirement for holding data.
Appendix A: Reference Guides A.4 122 (124) 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.
Appendix A: Reference Guides A.6.2 123 (124) RS232 Typical Connection Anybus® Communicator™ User Manual SCM-1202-176 1.
last page © 2021 HMS Industrial Networks Box 4126 300 04 Halmstad, Sweden info@hms.se SCM-1202-176 1.
