User Manual Anybus® Communicator™ for EtherNet/IP™ / Modbus-TCP Doc. Id. HMSI-27-314 Rev. 3.10 Connecting DevicesTM +$/067$' &+,&$*2 .$5/658+( 72.<2 %(,-,1* 0,/$12 08/+286( &29(175< 381( &23(1+$*(1 HMS Industrial Networks Mailing address: Box 4126, 300 04 Halmstad, Sweden Visiting address: Stationsgatan 37, Halmstad, Sweden E-mail: info@hms-networks.com Web: www.anybus.
Important User Information This document contains a general introduction as well as a description of the technical features provided by the Anybus Communicator, including the PC-based configuration software. The reader of this document is expected to be familiar with PLC and software design, as well as communication systems in general. The reader is also expected to be familiar with the Microsoft® Windows® operating system. Liability Every care has been taken in the preparation of this manual.
Table of Contents Table of Contents Preface About This Document Related Documents..................................................................................................................... 9 Document History ...................................................................................................................... 9 Conventions & Terminology ................................................................................................... 10 Glossary.................................
IV Chapter 3 File System General........................................................................................................................................ 28 File System Overview ............................................................................................................... 29 System Files................................................................................................................................ 29 Chapter 4 FTP Server General............................
V Chapter 11 Basic Settings Fieldbus Settings........................................................................................................................ 64 Communicator Parameters ...................................................................................................... 65 Sub-network Parameters .......................................................................................................... 66 Chapter 12 Nodes General....................................................
VI Chapter 16 DF1 Protocol Mode General........................................................................................................................................ 86 Communicator Parameters ...................................................................................................... 87 Sub-network Parameters .......................................................................................................... 88 Node Parameters ....................................................
VII Chapter 22 CIP Object Implementation General...................................................................................................................................... 107 Identity Object, Class 01h...................................................................................................... 108 General Information........................................................................................................ 108 Class Attributes..............................................
VIII Appendix A Parameter Data Initialization (Explicit Data) General...................................................................................................................................... 119 Add a Mailbox Message.......................................................................................................... 119 Mapping Input Parameter Data to EtherNet/IP ............................................................... 120 Mapping Output Parameter Data to EtherNet/IP..............
Preface P. About This Document For more information, documentation etc., please visit the HMS website www.anybus.com. P.1 Related Documents Document name ABC-EIP Installation Leaflet DF1 Protocol and Command Set - Reference Manual, 1770-6.5.16, October 1996 Open Modbus-TCP Specification, Release 1.0 RFC 821 RFC 1918 ENIP Specifications Author HMS Allen-Bradley Schneider Electric Network Working Group Network Working Group ODVA P.2 Document History Summary of Recent Changes (3.03... 3.
About This Document 10 P.3 Conventions & Terminology The following conventions are used throughout this document: • Numbered lists provide sequential steps • Bulleted lists provide information, not procedural steps • The term ‘user’ refers to the person or persons responsible for installing the Anybus Communicator in a network. • The term ‘ABC’ refers to the Anybus Communicator. • Hexadecimal values are written in the format 0xNNNN, where NNNN is the hexadecimal value.
Chapter 1 1. About the Anybus Communicator for EtherNet/IP The Anybus Communicator for EtherNet/IP acts as a gateway between virtually any serial application protocol and an EtherNet/IP-based network. Integration of industrial devices is enabled with no loss of functionality, control and reliability, both when retro-fitting to existing equipment as well as when setting up new installations. EtherNet/IP Scanner (e.g a PLC) EtherNet/IP Scanner (e.
About the Anybus Communicator for EtherNet/IP 12 1.1 External View For wiring and pin assignments, see “Connector Pin Assignments” on page 124. A: Ethernet Connectors These connectors are used to connect the Anybus Communicator to the network. C See also... B - “Ethernet Connector” on page 124 B: Configuration Switches A See also... - “Configuration Switches” on page 14 C: Status LEDs D See also...
About the Anybus Communicator for EtherNet/IP 13 1.
About the Anybus Communicator for EtherNet/IP 14 1.3 Configuration Switches If set to a nonzero value, the configuration switches forces the Anybus Communicator to use an IP address in the range 192.168.0.1 - 192.168.0.255. If set to zero, these settings are specified by the system file ‘ethcfg.cfg’, or by settings in Anybus Configuration Manager. Note that the switches are read once during startup; any changes require a reset in order to have effect. See also...
About the Anybus Communicator for EtherNet/IP 15 1.4 Hardware Installation Perform the following steps to install the Anybus Communicator module: 1. Snap the gateway on to the DIN-rail.
About the Anybus Communicator for EtherNet/IP 16 1.5 Software Installation 1.5.1 Anybus Configuration Manager System requirements • Pentium 133 MHz or higher • 650 MB of free space on the hard drive • 32 MB RAM • Screen resolution 800 x 600 (16 bit color) or higher • Microsoft Windows® 2000 / XP / Vista / 7 (32- or 64-bit) • Internet Explorer 4.01 SP1 or newer (or any equivalent browser) Installation • Anybus Communicator resource CD - Insert the CD and follow the on-screen instructions.
Chapter 2 2. Basic Operation 2.1 General The Anybus Communicator is designed to exchange data between a serial sub-network and a higher level network. Unlike most other similar devices, the Anybus Communicator has no fixed protocol for the sub-network, and consequently can be configured to handle almost any form of serial communication. The gateway can issue serial telegrams cyclically, on change of state, or based on trigger events issued by the control system in the higher level network (i.e.
Basic Operation 18 2.2 Data Exchange Model Internally, data exchanged on the sub-network and on the higher level network all resides in the same memory. ABC Internal Memory This means that in order to exchange data with the subnetwork, the higher level network simply reads and writes data to the memory locations specified using the Anybus Configuration Manager. The very same memory locations can then be exchanged on the sub-network.
Basic Operation 19 2.2.2 Data Exchange Example In the following example, a temperature regulator on the sub-network exchanges information with a PLC on the higher level network, via the internal memory buffers in the Anybus Communicator.
Basic Operation 20 2.3 Sub-network Protocol 2.3.1 Protocol Modes The Anybus Communicator features three distinct operating modes for sub-network communication: ‘Master Mode’, ‘DF1 Master Mode’ and ‘Generic Data Mode’. Note that the protocol mode only specifies the basic communication model, not the actual sub-network protocol. • Master Mode In this mode, the gateway acts as a master on the sub-network, and the serial communication is query-response based.
Basic Operation 21 2.3.3 Master Mode In this mode, the communication is based on a query-response scheme; when the gateway issues a query on the sub-network, the addressed node is expected to issue a response. Nodes are not permitted to issue responses/messages spontaneously, i.e. without first receiving a query. There is, however, one exception to this rule; the broadcaster.
Basic Operation 22 2.3.4 Generic Data Mode In this mode, there is no master-slave relationship between the nodes on the sub-network and the gateway. Any node (including the gateway) may spontaneously produce or consume a message. Nodes are not obliged to respond to messages, nor do they need to wait for a query in order to send a message. Control System Gateway Subnetwork Devices In the figure above, the Anybus Communicator ‘consumes’ data ‘produced’ by a node on the sub-network.
Basic Operation 23 2.4 EtherNet/IP 2.4.1 General EtherNet/IP is based on the Control and Information Protocol (CIP), which is also the application layer for DeviceNet and ControlNet. The Anybus Communicator acts as a Group 2 or 3 server on the EtherNet/IP network. Input and output data is accessed using I/O connections or explicit messages towards the assembly object and the parameter input/output mapping objects. See also... • “CIP Object Implementation” on page 107 2.4.
Basic Operation 24 2.4.
Basic Operation 25 2.5 Modbus-TCP 2.5.1 General The Modbus-TCP protocol is an implementation of the standard Modbus protocol running on top of TCP/IP. The built-in Modbus-TCP server provides access to the input and output data areas via a subset of the functions defined in the Modbus-TCP specification. The server supports up to 8 simultaneous connections and communicates over TCP port 502. For detailed information regarding the Modbus-TCP protocol, consult the Open Modbus Specification. 2.5.
Basic Operation 26 2.5.4 Modbus Addressing Mode Supported Function Codes The following function codes can be used in this mode: Modbus Function Function Code Associated with Area Read Holding Registers 3 Output Data area (0x200...0x3FF) Read Input Registers 4 Input Data area (0x000....0x1FF) Write Single Register 6 Output Data area (0x200...0x3FF) Force Multiple Registers 16 Mask Write Register Read/Write Registers 22 23 No.
Basic Operation 27 2.5.5 Anybus Addressing Mode Supported Function Codes The following function codes can be used in this mode: Modbus Function Read Coil Read Input Discretes Read Holding Registers Read Input Registers Write Coil Write Single Register Force Multiple Coils Force Multiple Registers Mask Write Register Read/Write Registers Function Code 1 2 3 4 5 6 15 16 22 23 Associated with Area(s) No. of I/Os or Data Points per Command Input and Output Data Area 1 - 2000 bits (0x000...
Chapter 3 3. File System 3.1 General General The Anybus Communicator features a built-in file system, which is used to store information such as web files, network communication settings, e-mail messages etc. Storage Areas The file system consists of the different storage areas: • Non-volatile area (approx. 1.4 Mb) This section is intended for static files such as web files, configurations files etc. • Volatile area (approx.
File System 29 3.2 File System Overview (admin root) (user root) user ip_accs.cfg ssi_str.cfg http.cfg pswd ethcfg.cfg onoffln.cfg (protected) sys_pswd.cfg email RAM (volatile, optional) email_1.cfg . . . email_10.cfg pswd (protected) ad_pswd.cfg email email_1.cfg . . . email_10.cfg 3.3 System Files The file system contains a set of files used for system configuration.
Chapter 4 4. FTP Server 4.1 General The built-in FTP server provides a way to access the file system using a standard FTP client. The following port numbers are used for FTP communication: • TCP, port 20 (FTP data port) • TCP, port 21 (FTP command port) Security Levels The FTP server features two security levels; admin and normal. • Normal level users The root directory will be ‘\user’. • Admin level users The root directory will be ‘\’, i.e. the user has unrestricted access to the file system.
FTP Server 31 4.2 FTP Connection Example (Windows Explorer) The built-in FTP client in Windows Explorer can easily be used to access the file system as follows: 1. Open the Windows Explorer by right-clicking on the ‘Start’ button and selecting ‘Explore’. 2. In the address field, type FTP://:@ - Substitute with the IP address of the Anybus Communicator - Substitute with the username - Substitute with the password 3. Press enter.
Chapter 5 5. Telnet Server 5.1 General The built-in Telnet server provides a way to access the file system using a standard Telnet client. The server communicates through TCP port 23. Security Levels Just like the FTP server, the Telnet server features two security levels; admin and normal. • Normal level users The root directory will be ‘\user’. • Admin level users The root directory will be ‘\’, i.e. the user has unrestricted access to the file system.
Telnet Server 33 5.2 General Commands admin • Syntax admin • Description Provided that the user can supply a valid admin username/password combination, this command provides admin access rights to normal level users. exit • Syntax exit • Description This command closes the Telnet session. help • Syntax help [general|diagnostic|filesystem] • Description If no argument is specified, the following menu will be displayed.
Telnet Server 34 5.3 Diagnostic Commands arps • Syntax arps • Description Display ARP stats and table iface • Syntax iface • Description Display net interface stats routes • Syntax routes • Description Display IP route table sockets • Syntax sockets • Description Display socket list 5.4 File System Operations For commands where filenames, directory names or paths shall be given as an argument the names can be written directly or within quotes.
Telnet Server 35 cd • Syntax cd [path] • Description Changes current directory. copy • Syntax copy [source] [destination] • Description This command creates a copy of the source file at a specified location. del • Syntax del [file] • Description Deletes a file. dir • Syntax dir [path] • Description Lists the contents of a directory. If no path is given, the contents of the current directory is listed. df • Syntax df • Description Displays filesystem info.
Telnet Server 36 md • Syntax md [directory] • Description Creates a directory. If no path is given, the directory is created in the current directory. mkfile • Syntax mkfile [filename] • Description Creates an empty file. move • Syntax move [source] [destination] • Description This command moves a file or directory from the source location to a specified destination. rd • Syntax rd [directory] • Description Removes a directory. The directory can only be removed if it is empty.
Chapter 6 6. Basic Network Configuration 6.1 General Information The Anybus Communicator offers two modes of operation regarding the network settings: • Settings specified by Configuration Switches If the on-board switches are set to a non-zero value, the ABC is locked to the following settings: IP Address:192.168.0.x(x = switch value) Gateway:255.255.255.0 Subnet:255.255.255.0 DHCP:OFF See also...
Basic Network Configuration 38 6.2 Ethernet Configuration File (‘ethcfg.cfg’) 6.2.1 General To exist on the network, the Anybus Communicator needs a valid TCP/IP configuration. These settings are stored in the system file ‘\ethcfg.cfg’. Note that if TCP/IP settings are enabled in Anybus Configuration Manager, then the IP address, gateway and subnet settings in ethcfg.cfg will be overwritten every time the module is restarted. All other settings are unaffected. File Format: [IP address] xxx.xxx.xxx.
Basic Network Configuration 39 6.3 IP Access Control It is possible to specify which IP addresses are permitted to connect to the Anybus Communicator. This information is stored in the system file ‘\ip_accs.cfg’. File Format: [Web] xxx.xxx.xxx.xxx • Nodes listed here may access the web server [FTP] xxx.xxx.xxx.xxx • Nodes listed here may access the FTP server [Modbus-TCP] xxx.xxx.xxx.xxx • Nodes listed here may access the gateway via Modbus-TCP [EtherNet/IP] xxx.xxx.xxx.
Basic Network Configuration 40 6.4 On/Offline Configuration By default, the On/Offline indication is triggered by the link status. Other triggering options can however be specified in the optional system file ‘\onoffln.cfg’, which should be placed in the module root and looks as follows: • File Format: [ON/OFF-line trigger] Modbus Values: ‘Link’ (default), ‘EIP’, ‘Modbus’ or a combination • [Timeout] 10 [Commands] 3, 16, 23 On/Offline trigger source Timeout Value Range: 1... 65535 (default = 1).
Basic Network Configuration 41 6.5 Anybus IPconfig (HICP) The Anybus Communicator supports the HICP protocol used by the Anybus IPconfig utility from HMS, which can be downloaded free of charge from the HMS website. This utility may be used to configure the network settings of any Anybus product connected to the network. Note that if successful, this will replace the settings currently stored in the configuration file (‘ethcfg.cfg’). Upon starting the program, the network is scanned for Anybus products.
Chapter 7 7. Web Server 7.1 General The Anybus Communicator features a flexible web server with SSI capabilities. The built-in web pages can be customized to fit a particular application and allow access to I/O data and configuration settings. The web server communicates through port 80. See also... • “Server Side Include (SSI)” on page 45 • “IP Access Control” on page 39 Protected Files For security reasons, the following files are protected from web access: • Files located in ‘\user\pswdcfg\pswd’ •
Web Server 43 7.2 Authorization Directories can be protected from web access by placing a file called ‘web_accs.cfg’ in the directory to protect. This file shall contain a list of users that are allowed to access the directory and its subdirectories. File Format: Username1:Password1 Username2:Password2 ... UsernameN:PasswordN [AuthName] (message goes here) • List of approved users. • Optionally, a login message can be specified by including the key [AuthName].
Web Server 44 7.3 Content Types By default, the following content types are recognized by their file extension: Content Type text/html image/gif image/jpeg image/x-png application/x-javascript text/plain application/x-zip-compressed application/octet-stream text/vnd.wap.wml application/vnd.wap.wmlc image/vnd.wap.wbmp text/vnd.wap.wmlscript application/vnd.wap.wmlscriptc text/xml application/pdf File Extension *.htm, *.html, *.shtm *.gif *.jpeg, *.jpg, *.jpe *.png *.js *.bat, *.txt, *.c, *.h, *.cpp, *.
Chapter 8 8. Server Side Include (SSI) General Server Side Include (from now on referred to as SSI) functionality enables dynamic content to be used on web pages and in e-mail messages. SSI are special commands embedded in the source document. When the Anybus module encounters such a command, it will execute it, and replace it with the result (when applicable). Syntax The ‘X’s below represents a command opcode and parameters associated with the command.
Server Side Include (SSI) 46 8.1 Functions DisplayMacID This function returns the MAC ID in format xx:xx:xx:xx:xx:xx. Syntax: DisplaySerial This function returns the serial number of the Anybus module. Syntax: DisplayFWVersion This function returns the main firmware revision of the Anybus module.
Server Side Include (SSI) 47 DisplayDNS1 This function returns the address of the primary DNS server. Syntax: DisplayDNS2 This function returns the address of the secondary DNS server. Syntax: DisplayHostName This function returns the hostname. Syntax: DisplayDomainName This function returns the default domain name.
Server Side Include (SSI) 48 DisplaySMTPUser This function returns the username used for SMTP authentication. Syntax: DisplaySMTPPswd This function returns the password used for SMTP authentication. Syntax: DisplayStationName This function returns the PROFINET Station Name. Syntax: DisplayStationType This function returns the PROFINET Station Type.
Server Side Include (SSI) 49 StoreEtnConfig Note: This function cannot be used in e-mail messages. This SSI function stores a passed IP configuration in the configuration file ‘ethcfgIP.cfg’. Syntax: Include this line in a HTML page and pass a form with new IP settings to it.
Server Side Include (SSI) 50 GetText Note: This function cannot be used in e-mail messages. This SSI function gets the text from an object and stores it in the OUT area. Syntax: ObjName- Name of object. offset - Specifies the offset from the beginning of the OUT area.
Server Side Include (SSI) 51 The conversion characters and their meanings are shown below. If the character after the % is not a conversion character, the behavior is undefined. Character d, i o x, X u c s f e, E g, G % Argument type, Converted to byte, short; decimal notation (For signed representation. Use signed argument) byte, short; octal notation (without a leading zero). byte, short; hexadecimal notation (without a leading 0x or 0X), using abcdef for 0x or ABCDEF for 0X.
Server Side Include (SSI) 52 Argument CipReadUWord(class, inst, attr) CipReadSLong(class, inst, attr) CipReadULong(class, inst, attr) CipReadFloat(class, inst, attr) CipReadShortString(class, inst, attr) CipReadString(class, inst, attr) CipReadUByteArray(class, inst, attr) CipReadUWordArray(class, inst, attr) CipReadULongArray(class, inst, attr) Description Read an unsigned word from a CIP-object Read a signed longword from a CIP-object Read an unsigned longword from a CIP-object Read a floating point val
Server Side Include (SSI) 53 The arguments that can be passed to the SSI function scanf are: Argument OutWriteByte(offset) OutWriteWord(offset) OutWriteLong(offset) OutWriteString(offset) OutWriteFloat(offset) MbWriteByte(id) MbWriteWord(id) MbWriteLong(id) MbWriteString(id) MbWriteFloat(id) CipWriteByte(class, inst, attr) CipWriteWord(class, inst, attr) CipWriteLong(class, inst, attr) CipWriteFloat(class, inst, attr) Description Write a byte to position offset in the OUT area Write a word to position off
Server Side Include (SSI) 54 SaveDataToFile Note: This function cannot be used in e-mail messages. This SSI function saves the data of a passed form to a file. The “Object name” parameter is optional, if specified, only the data from that object will be stored. If not, the data from all objects in the form will be stored. The [Append|Overwrite] parameter determines if the specified file shall be overwritten, or if the data in the file shall be appended.
Server Side Include (SSI) 55 8.2 Changing SSI output There are two methods of changing the output strings from SSI functions: 1. Changing SSI output defaults by creating a file called "\ssi_str.cfg" containing the output strings for all SSI functions in the system. 2. Temporary changing the SSI output by calling the SSI function "SsiOutput()". 8.2.1 SSI Output String File If the file "\ssi_str.
Server Side Include (SSI) 56 8.2.2 Temporary SSI Output change The SSI output for the next called SSI function can be changed with the SSI function “SsiOutput()”. The next called SSI function will use the output according to this call. Thereafter the SSI functions will use the default outputs or the outputs defined in the file ‘\ssi_str.cfg’. The maximum size of a string is 128 bytes.
Chapter 9 9. E-mail Client 9.1 General The built-in e-mail client can send predefined e-mail messages based on trigger-events in input and output data areas. The client supports SSI, however note that some SSI functions cannot be used in e-mail messages (specified separately for each SSI function). See also... • “Server Side Include (SSI)” on page 45 Server Settings The Anybus Communicator needs a valid SMTP server configuration in order to be able to send e-mail messages.
E-mail Client 58 9.2 E-mail Definitions The e-mail definitions are stored in the following two directories: • ‘\user\email’ This directory holds up to 10 messages which can be altered by normal level FTP users. • ‘\email’ This directory holds up to 10 messages which can be altered by admin level FTP users. E-mail definition files must be named ‘email_1.cfg’, ‘email_2.cfg’... ‘email_10.cfg’ in order to be properly recognized by the gateway.
Chapter 10 10. Navigating ACM 10.1 Main Window The main window in ACM can be divided into 4 sections as follows: A C B D • A: Drop-down Menus & Tool Bar The second drop-down menu from the left will change depending on the current context. The Tool Bar provides quick access to the most frequently used functions. • B: Navigation Section This menu entry is expanded Sub-entries This section is the main tool for selecting and altering different levels of the sub-network configuration.
Navigating ACM 60 10.1.1 Drop-down Menus File • New Create a new configuration. See also “Configuration Wizards” on page 64. • Open... Open a previously created configuration. • Save Save the current configuration. • Save As... Save the current configuration under a new name. • Print... Send details about the current configuration to a printer. • Properties... Set the name and (optional) passwords for the configuration.
Navigating ACM 61 Tools • Port Select the COM-port used for the configuration of the gateway. • Upload configuration from Communicator RS232/422/485 Upload the configuration from the gateway to ACM. • Download configuration to Communicator RS232/422/485 Download the current configuration to the gateway. • Start Logging Start the Data Logger (see “Data Logger” on page 98). Note that when the Data Logger is active, this menu entry is changed to “Stop Logging”.
Navigating ACM 62 Selecting the “Module” tab will reveal additional properties: Item Size of logbuffer Firmware Download Factory Restore Block Configuration Create Error log Description By default, the Data Logger can log up to 512 entries in each direction. If necessary, it is possible to specify a different number of entries (valid settings range from 1...512). Click “Apply” to validate the new settings. See also “Data Logger” on page 98. Download firmware to the embedded fieldbus interface.
Navigating ACM 63 10.1.2 Toolbar Icons The toolbar features icons for the most commonly used functions. • New, Open & Save See “File” on page 60. • New Open Save Upload from ABC & Download to ABC See “Tools” on page 61. Upload • Download Up one Level Clicking on this icon will move the selection in the navigation section. • Cut, Copy, Paste, Delete, Insert These icons are used for common editing functions in the navigation section.
Chapter 11 11. Basic Settings 11.1 Fieldbus Settings (Select ‘Fieldbus’ in the Navigation Section to gain access to the parameters described in this section). General During start-up the fieldbus interface of the Anybus Communicator is initialized to fit the configuration created in the Anybus Configuration Manager. Optionally, some initialization parameters can be set manually to provide better control over how the data shall be treated by the gateway.
11.2 Communicator Parameters Interface Only serial communication is currently supported. Control/Status Word See “Control and Status Registers” on page 102. Value Enabled Enabled but no startup lock Disabled Description Enable the Control and Status Registers. The “Data Valid”-bit in the Control Register must be set to start the sub-network communication.
11.3 Sub-network Parameters Communication These parameters specify the actual communication settings used for the sub-network. Parameter Bitrate (bits/s) Description Selects the bit rate Data bits Parity Physical standard Stop bits Selects the number of data bits Selects the parity mode Selects the physical interface type Number of stop bits.
Chapter 12 12. Nodes 12.1 General In ACM, a node represents a single device on the network. Although the gateway does not feature a scan list in the traditional sense, all nodes and their transactions will be processed in the order they were defined in ACM. The maximum number of nodes that can be created in ACM is 31. 12.2 Adding & Managing Nodes Function Paste Subnetwork Monitor Add Node Add Broadcastera Load Node Subnetwork Status...
Chapter 13 13. Transactions 13.1 General As mentioned previously, transactions are representations of the actual serial telegrams exchanged on the serial sub-network. Although the gateway does not feature a scan list in the traditional sense, all nodes and their transactions will be processed in the order they were defined in ACM. Transactions are handled slightly differently in the three protocol modes: • Master Mode For regular nodes, transactions always come in pairs; a query and a response.
Transactions 69 13.2 Adding & Managing Transactions Function Copy Deletea Node Monitor Add Transaction(s)b Add Transaction Consumec Add transaction Producec Add Command Insert New Node Save Node Insert from File Rename Description Copy a node to the clipboard Delete a node Launch the node monitor (see “Node Monitor” on page 94) On regular nodes, this adds a Query and a Response. The two transactions will be grouped in order to increase readability. On the Broadcaster, a single transaction will be added.
Transactions 70 13.3 Transaction Parameters (Master Mode) 13.3.1 Parameters (Query & Broadcast) Parameter Minimum time between broadcasts (10 ms) Description This parameter specifies how long the gateway shall wait after transmitting a broadcast transaction before processing the next entry in the scanlist. The value should be set high enough to allow the slave devices time to finish the handling of the broadcast. The entered value is multiplied by 10. An entered value of 5 will result in 50 ms.
Transactions 71 Parameter Update mode Description This parameter is used to specify when the transaction shall be sent to the slave: • Cyclically The transaction is issued cyclically at the interval specified in the “Update time” parameter. • On data change The data area is polled for changes at the time interval defined by Update time. A transaction is issued when a change in data is detected. • Single shot The Query is issued once at start up.
Transactions 72 13.4 Transaction Parameters (Generic Data Mode) 13.4.1 Produce Transactions Parameter Offline options for fieldbus Description This parameter specifies the action to take for this transaction if the higher level network goes offline. This affects the data that is sent to the sub-network.
Transactions 73 Parameter Trigger byte address Description This parameter specifies location of the trigger byte in the internal memory buffer. If “Update mode” is set to “Change of state on trigger”, the memory location specified by this parameter is monitored by the gateway. Whenever the trigger byte is updated, the gateway will produce the transaction on the sub-network.
Transactions 74 13.5 Transaction Editor The Transaction Editor can be used to edit the individual frame objects of a transaction. The same settings are also available in the parameter section of the main window, however the Transaction Editor presents the frame objects in a more visual manner. Frame Objects To edit the value of a parameter, click on it and enter a new value using the keyboard.
Chapter 14 14. Frame Objects 14.1 General Each transaction consists of Frame Objects which makes up the serial telegram frame. Each Frame Object specifies how the gateway shall interpret or generate a particular part of the telegram.
Frame Objects 76 14.3 Constant Objects (Byte, Word, Dword) Constant Objects have a fixed value and come in three sizes: • Byte 8 bits • Word 16 bits • Dword 32 bits Constants are handled differently depending on the direction of the transaction: • Produce/Query Transactions The gateway will send the value as it is without processing it. • Consume/Response Transactions The gateway will check if the received byte/word/dword matches the specified value. If not, the message will be discarded.
Frame Objects 77 14.4 Limit Objects (Byte, Word, Dword) Limit Objects have a fixed range and come in three sizes: • Byte 8 bits • Word 16 bits • Dword 32 bits Limit Objects are handled differently depending on the direction of the transaction: • Produce/Query Transactions This object shall not be used for such transactions (value will be undefined). • Consume/Response Transactions The gateway will check if the received byte/word/dword fits inside the specified boundaries.
Frame Objects 78 14.5 Data Object Data Objects are used to represent raw data as follows: • Produce/Query Transactions The specified data block is forwarded from the higher level network to the sub-network. • Consume/Response Transactions The specified data block is forwarded from the sub-network to the higher level network.
Frame Objects 79 To specify the properties of the object, select it in the Navigation Section enter the desired settings in the Parameter section as follows: Parameter Byte Swapping Description • No Swapping No swapping will be performed on the data • Swap 2 bytes A, B, C, D becomes B, A, D, C • Swap 4 bytes A, B, C, D becomes D, C, B, A Fill unused bytes • Enableda Fill unused data with the value specified in “Filler byte”.
Frame Objects 80 14.7 Checksum Object Most serial protocols features some way of verifying that the data has not been corrupted during transfer. The Checksum Object calculates and includes a checksum in a transaction. Parameter Error Check Start byte Error Check Type Description Specifies the byte offset in the transaction to start checksum calculations on.
Chapter 15 15. Commands This information is only valid for the Master and Generic Data modes. For DF1 master mode, please refer to “Services” on page 89. 15.1 General As mentioned previously, commands are actually predefined transactions that can be stored and reused. Just like regular transactions, commands consist of frame objects and are representations of the actual serial telegrams exchanged on the serial sub-network.
Commands 82 15.2.1 Drop-down Menu File This menu features the following entries: • Select Add the currently selected Command to the node. • Exit Exit without adding a command to the node. Command This menu is used to manage the commands in the list: • Add Command Add a custom command to the list, and open the new command in the Command Editor. See also “The Command Editor” on page 83. • Edit Command Edit the currently selected command using the Command Editor.
Commands 83 15.3 The Command Editor 15.3.1 General The Command Editor is used to define new commands and edit existing ones. This makes it possible to build a library of commands, which can be stored and reused at a later stage. Note that the Command Editor is somewhat protocol-dependent in the sense that certain frame objects may not be deleted or altered. The examples in this section use Master Mode.
Commands 84 15.3.3 Drop-down Menu File This menu features the following entries: • Apply Changes Save changes and exit to the main window. • Exit Exit without saving. Column The functions in this menu alters the structure of the command. • Append Column Add another column to the command. • Insert Column Insert a column at the selected position. • Delete Column Delete the column at the selected position. 15.3.
Commands 85 15.3.5 Example: Specifying a Modbus-RTU Command in Master Mode In the following example, a Modbus-RTU command is created in Master Mode. In Modbus-RTU, a transaction always feature the following parts: • Slave Address (1 byte) • Function Code (1 bytes) • A data field • CRC (CRC-16) Furthermore, each command always consists of a query and a response.
Chapter 16 16. DF1 Protocol Mode This mode makes the Anybus Communicator act as a DF1 protocol master on the sub-network. 16.1 General In DF1 master mode, communication is based on “services”. A “service” represents a set of commands and operations on the sub-network, that is predefined in the Anybus Communicator. Each service is associated with a set of parameters controlling how and when to use it on the sub-network.
DF1 Protocol Mode 87 16.2 Communicator Parameters Interface Currently, only serial communication is supported. Control/Status Word (See “Control and Status Registers” on page 102). Value Enabled Enabled but no startup lock Disabled Description Enable the Control and Status Registers. The “Data Valid”-bit in the Control Register must be set to start the sub-network communication.
DF1 Protocol Mode 88 16.3 Sub-network Parameters Communication These parameters specify the actual communication settings used for the sub-network. Parameter Bitrate (bits/s) Description Selects the bit rate Data bits Parity Physical standard Stop bits Selects the number of data bits Selects the parity mode Selects the physical interface type Number of stop bits.
DF1 Protocol Mode 89 16.4 Node Parameters To gain access to the parameters described in this section, select a node in the navigation section. For more information about nodes, see “Nodes” on page 67. Parameter Checksum Description Selects the type of checksum on the network. Slave Address Type The value entered here sets the node address. The PLC type of the slave Valid Settings BCC CRC (default) 0-254 PLC-5 SLC500 MicroLogix 16.5 Services Services are commands that can be stored and reused.
DF1 Protocol Mode 90 16.5.1 Available Services Right click on the node, and choose Add Command. A pop-up window will show the four different services that are available: • Integrity check • Read diagnostics • Read data • Write data A maximum of 50 services in total (for all nodes) can be selected. The predefined services can be configured to suit the application. Select a service to show the parameters.
DF1 Protocol Mode 91 16.6 Integrity Check This service checks that a node is up and running correctly. A telegram is sent to the node. The node mirrors and returns the telegram. No configuration is needed, apart from the general parameters, common to all services. 16.7 Read Diagnostics This service reads diagnostic information from the module. Command parameters The command parameter Size decides the amount of data that can be read.
DF1 Protocol Mode 92 16.8 Read Data This service is used to read data from the nodes in the sub-network. Command Parameters Parameter Description Element Number The element number of the data file to be accessed within the slave. File number File type Size Valid settings PLC-5: 0–999 SLC500: 0–255 MicroLogix: 0–255 The file number of the data file to be accessed. PLC-5: 3, 7, 8, 10–999 SLC500: 3, 7, 8, 10–255 MicroLogix: 3, 7, 8, 10–255 The file type of the data to be accessed.
Chapter 17 17. Sub-network Monitor 17.1 General The sub-network Monitor is intended to simplify configuration and troubleshooting of the sub-network. Its main function is to display the data allocated for sub-network communication and detect if any area has been allocated twice (i.e if a collision has occurred). All configured nodes, and their transactions, are listed in the middle of the screen (B). Selecting and deselecting single transactions makes it possible to view any combination of allocated data.
Chapter 18 18. Node Monitor 18.1 General The Node Monitor can provide valuable information when setting up the communication with the subnetwork, by allowing individual commands to be issued manually, and monitoring the response (if applicable). It also provides an overview of the memory used by a particular node. Note: The node monitor has a negative influence on the overall performance of the gateway, i.e. it should be used only when necessary.
Node Monitor 95 18.2 Navigating the Node Monitor A B C D A: Drop-down Menu & Toolbar Icons See “Drop-down Menu” on page 96 and “Toolbar Icons” on page 97. B: Command Section This section holds the currently selected command. The individual frame objects in the command can be edited in a similar way as in the Transaction and Command Editors. C: Response Section (Master Mode and DF1 Master Mode only) This section holds the response to the selected Command.
Node Monitor 96 18.2.1 Drop-down Menu File There is only one entry in this menu: • Exit This will close the Node Monitor. Note however that if the node has been disabled using “Stop Node” (see below), it will not resume data exchange until enabled again using “Start node”. Node This menu controls the data exchange for the node. This feature can help isolate problems associated with a particular node. • Start Node Enable the transactions associated with the node.
Node Monitor 97 18.2.2 Toolbar Icons The toolbar features icons for the most commonly used functions. • Start Node & Stop Node These icons corresponds to the functions in the “Node” menu. See also “Node” on page 96. • Start Stop Select Send Stop Resume Select Command & Send Command These icons corresponds to the functions in the “Command” menu. See also “Command” on page 96.
Chapter 19 19. Data Logger 19.1 General This feature allows the sub-network traffic to be logged into a buffer for examination. This may provide valuable information when debugging the lowest levels of the sub-network communication. Note that the logger function is part of the gateway itself and is separate from ACM. This means that logging can be performed even if the gateway is physically disconnected from the PC running ACM. 19.
Data Logger 99 19.3 Configuration By default, the log-buffer can hold 512 bytes of data in each direction. To specify a different size for the buffer, select “Options” in the “Tools”-menu. A window with various settings will appear. Select the “Module” tab, and enter the desired number of buffer entries under “Size of logbuffer” (valid settings range from 1–512). Click “Apply” to validate the new settings. Click “OK” to exit. Anybus Communicator EtherNet/IP / Modbus-TCP User Manual Doc: HMSI-27-314, Rev.
Chapter 20 20. Configuration Wizards 20.1 General When creating a new sub-network configuration, the Anybus Configuration Manager provides a choice between starting out with a blank configuration, or using a predefined template, a.k.a a wizard. The wizard automatically creates a sub-network configuration based on information supplied by the user, i.e the user simply has to “fill in the blanks”.
Configuration Wizards 101 20.3 Wizard - Modbus RTU Master This wizard can be used to create a Modbus-RTU-based network configuration based on certain information about the sub-network. The online help system explains each configuration step in detail. • Important Notes: Many OEM devices do not fully comply with the Modbus standard. For example, they may implement a variation of this standard or be limited to the use of specific Modbus commands other than the ones used by this wizard.
Chapter 21 21. Control and Status Registers 21.1 General The Control and Status Registers are disabled by default, but can be enabled using ACM (see “Control/ Status Word” on page 65). These registers form an interface for exchanging status information between the sub-network and the fieldbus control system. The main purpose of these registers is to...
Control and Status Registers 103 21.1.2 Data Consistency The “Data Valid”-bits in the Control and Status Registers are used to ensure data consistency during start-up and fieldbus offline/online transitions. If the “Control/Status Word”-parameter in ACM is set to “Enabled”, the gateway will wait for the fieldbus control system to set the “Data Valid”-bit in the Control Register before it starts exchanging data on the sub-network.
Control and Status Registers 104 21.2 Status Register Contents (Gateway to Control System) 21.2.1 General Information The Status Register is (if enabled) located at 0x000–0x001 and constitutes a bit-field as follows: bit(s) 15 14 13 Name Send (SR_HS_SEND) Confirm (SR_HS_CONFIRM) Data Valid (Master Mode and DF1 Master Mode Only) 12... 8 Status Code 7... 0 Data Description These bits control the handshaking towards the fieldbus control system. See also...
Control and Status Registers 105 21.2.3 Status Code in Generic Data Mode (This table is valid only in Generic Data Mode). Code 0x00 Condition Invalid Transaction Counter Updated Type Error Data Counter 0x01 Frame Error Warning - 0x02 Offline Timeout Counter Updated Error Counter 0x03 Buffer Overrun Warning - 0x04 0x1F Other Error No Error Error Warning - Description The number of invalid transactions (i.e.
Control and Status Registers 106 21.3 Control Register Contents (Control System to Gateway) 21.3.1 General Information The Control Register is (if enabled) located at 0x200–0x201 and constitutes a bit-field as follows: bit(s) 15 14 13 Name Confirm (CR_HS_CONFIRM) Send (CR_HS_SEND) Data Valid 12 Execute Command 11... 8 Control Code 7... 0 Data Description These bits control the handshaking towards the gateway. See also...
Chapter 22 22. CIP Object Implementation 22.
CIP Object Implementation 108 22.2 Identity Object, Class 01h 22.2.1 General Information Object Description Supported Services Class services: Get Attribute All Get Attribute Single Instance services: Get Attribute All Get Attribute Single Reset 22.2.
CIP Object Implementation 109 Device Status bit(s) 0 1 2 3 4... 7 8 9 10 11 12...
CIP Object Implementation 110 22.4 Assembly Object, Class 04h 22.4.1 General Information Object Description This object provides access to the I/O Data in the input and output data areas in the Anybus Communicator. See also... • “EtherNet/IP” on page 23 • “Fieldbus Settings” on page 64 Supported Services Class services: Get Attribute Single Instance services: Get Attribute Single Set Attribute Single 22.4.
CIP Object Implementation 111 22.4.5 Instance C6h (198) Attributes (Heartbeat Input-Only) This instance is used as heartbeat for input-only connections, and does not carry any data. 22.4.6 Instance C7h (199) Attributes (Heartbeat, Listen-Only) This instance is used as heartbeat for listen-only connections, and does not carry any data. 22.5 Diagnostic Object, Class AAh 22.5.1 General Information Object Description This object groups diagnostic information for the fieldbus interface.
CIP Object Implementation 112 22.6 Parameter Data Input Mapping Object, Class B0h 22.6.1 General Information Object Description This object can be used to access input data acyclically, and is set up dynamically based on the Parameter Data Mailbox initialization (see “Parameter Data Initialization (Explicit Data)” on page 119). See also...
CIP Object Implementation 113 22.7 Parameter Data Output Mapping Object, Class B1h 22.7.1 General Information Object Description This object can be used to access output data acyclically, and is set up dynamically based on the Parameter Data Mailbox initialization (see “Parameter Data Initialization (Explicit Data)” on page 119). See also...
CIP Object Implementation 114 22.8 Port Object, Class F4h 22.8.1 General Information Object Description Supported Services Class services: Get Attribute All Get Attribute Single Instance services: Get Attribute All Get Attribute Single 22.8.2 Class Attributes # 1 2 3 8 Access Get Get Get Get Name Revision Max Instance No.
CIP Object Implementation 115 22.9 TCP/IP Interface Object, Class F5h 22.9.1 General Information Object Description This object groups TCP/IP-related settings. See also... • “Basic Network Configuration” on page 37 • “Fieldbus Settings” on page 64 Supported Services Class services: Get Attribute All Get Attribute Single Instance services: Get Attribute All Get Attribute Single Set Attribute Single 22.9.2 Class Attributes # 1 2 3 Access Get Get Get Name Revision Max Instance No.
CIP Object Implementation 116 22.10 Ethernet Link Object, Class F6h 22.10.1 General Information Object Description This object groups diagnostic information for the Ethernet interface. See also... • “Basic Network Configuration” on page 37 Supported Services Class services: Get Attribute All Get Attribute Single Instance services: Get Attribute All Get Attribute Single 22.10.2 Class Attributes # 1 2 3 Access Get Get Get Name Revision Max Instance No.
CIP Object Implementation 117 22.10.
Chapter 23 23. Advanced Fieldbus Configuration 23.1 General The fieldbus interface of the gateway consists of an embedded Anybus-S communication interface. Normally, the Anybus-S configuration settings are set up automatically by the gateway. However, advanced users can configure the Anybus-S card for specific features. This chapter assumes that the reader is familiar with the Anybus-S and it’s application interface.
Appendix A A. Parameter Data Initialization (Explicit Data) A.1 General The portion of the input and output data that is declared as parameter data cannot be accessed from the network unless it has been properly initialized. The purpose of this procedure is to specify which data blocks in the input and output data areas to associate with the instance attributes in the Parameter Data Input Mapping Object and the Parameter Data Output Mapping Object.
Parameter Data Initialization (Explicit Data) 120 A.3 Mapping Input Parameter Data to EtherNet/IP Example In the following example, a total of 160 bytes of data will be mapped to the Parameter Data Input Mapping Object. The data is made up of 5 separate data blocks, each associated with a particular instance attribute. To achieve this, perform the following steps: 1. Add a new mailbox message to the configuration (see “Add a Mailbox Message” on page 119). 2.
Parameter Data Initialization (Explicit Data) 121 Resulting Attribute Mapping Input Data 0x000 Parameter Data Input Mapping Object I/O Data (Input) Attributes: IO Size In (256 bytes) #1 - Revision Instance #1 Attributes: #1 - Data #2 - Data #3 - Data #4 - Data #5 - Data 0x0FF 0x100 32 bytes Offset 0x0000h (not mapped) 64 bytes 16 bytes 32 bytes (not mapped) 0x1FF 16 bytes Offset 0x00FFh Mailbox Editor Screenshot Anybus Communicator EtherNet/IP / Modbus-TCP User Manual Doc: HMSI-27-314, Rev.
Parameter Data Initialization (Explicit Data) 122 A.4 Mapping Output Parameter Data to EtherNet/IP Example Mapping output data is similar to mapping input data; in the following example, a total of 144 bytes of data will be mapped to the Parameter Data Output Mapping Object. The data is made up of 4 separate blocks, each associated with a a particular instance attribute. To achieve this, perform the following steps: 1.
Parameter Data Initialization (Explicit Data) 123 Resulting Attribute Mapping Output Data 0x200 I/O Data (Output) Parameter Data Output Mapping Object 0x27F 0x280 Attributes: #1 - Revision (not mapped) IO Size Out (128 bytes) Offset 0x0000h 16 bytes Instance #1 (not mapped) Attributes: #1 - Data #2 - Data #3 - Data #4 - Data 32 bytes 32 bytes (not mapped) 64 bytes (not mapped) 0x3FF Offset 0x017Fh Mailbox Editor Screenshot Anybus Communicator EtherNet/IP / Modbus-TCP User Manual Doc: HMS
Appendix B B. Connector Pin Assignments B.1 Ethernet Connector Pin Housing 1 2 3 4 5 6 7 Signal Cable Shield TD+ TDRD+ Termination Termination RDTermination 8 Termination 1 8 B.2 Power Connector Pin 1 2 Description +24 VDC GND 1 2 Notes: • Use 60/75 or 75 °C copper (Cu) wire only. • Minimum terminal tightening torque: 5–7 lb-in (0.5–0.8 Nm). Anybus Communicator EtherNet/IP / Modbus-TCP User Manual Doc: HMSI-27-314, Rev. 3.
Connector Pin Assignments 125 B.3 PC Connector Configuration Cable Wiring DP9F (PC) RJ11 (ABC) 1 1 Ground RS232 Rx 2 2 Ground RS232 Tx 3 3 Rx 4 4 Tx Ground 5 6 7 8 9 RJ11 (4P4C modular)1 : ABC Pin 1 2 3 4 Description Signal ground 4 RS232 Rx (Input) RS232 Tx (Output) 3 2 1 DB9F : PC Pin 1 2 3 4 5 6-9 Description RS232 Rx (Input) RS232 Tx (Output) Signal Ground - 5 (female) 1 9 6 1. The RJ11 (4P4C modular) is sometimes referred to as an RJ9.
Connector Pin Assignments 126 B.4 Sub-network Interface B.4.1 General Information The sub-network interface provides for RS232, RS422 and RS485 communications. Depending on the configuration specified in the Anybus Configuration Manager, different signals are activated in the subnetwork connector. B.4.2 Bias Resistors (RS485 Only) When idle, RS485 enters an indeterminate state, which may cause the serial receivers to pick up noise from the serial lines and interpret this as data.
Connector Pin Assignments 127 B.4.5 Typical Connection (RS485) +5V 470R RS485 + RS485 + 120R 120R RS485 - RS485 470R Signal Ground Signal Ground Node RS485 + RS485 - Signal Ground Node RS485 + RS485 - Signal Ground Node RS485 + RS485 - Signal Ground Node RS485 + Anybus Communicator RS485 - Signal Ground Cable Shield End Node B.4.
Appendix C C. Technical Specification C.1 Mechanical Properties Housing Plastic housing with snap-on connection to DIN-rail, protection class IP20. Dimensions (L x W x H) 120 mm x 75 mm x 27 mm (4.72” x 2.95” x 1.06”) C.2 Electrical Characteristics Power Supply Power: 24 VDC ± 10% Power Consumption Maximum power consumption is 280 mA on 24 VDC. Typically around 100 mA. C.3 Environmental Characteristics Relative Humidity The product is designed for a relative humidity of 0 to 95 % non-condensing.
Technical Specification 129 C.4 Regulatory Compliance EMC Compliance (CE) This product is in accordance with the EMC directive 89/336/EEC, with amendments 92/31/EEC and 93/68/EEC through conformance with the following standards: • EN 50082-2 (1993) EN 55011 (1990) Class A • EN 61000-6-2 (1999) EN 61000-4-3 (1996) 10 V/m EN 61000-4-6 (1996) 10 V/m (all ports) EN 61000-4-2 (1995) ±8 kV air discharge, ±4 kV contact discharge EN 61000-4-4 (1995) ±2 kV power port, ±1 kV other ports EN 61000-4-5 (1995) ±0.
Technical Specification 130 Additional installation and operating instructions • Max Ambient Temperature: 55 °C (for Hazloc environments) • Field wiring terminal markings (wire type (Cu only, 14–30 AWG)). • Use 60/75 or 75 °C copper (Cu) wire only. • Terminal tightening torque must be 5–7 lb-in (0.5–0.8 Nm). • Use in overvoltage category 1 pollution degree 2 environment. • Installed in an enclosure considered representative of the intended use.
Appendix D D. Troubleshooting Problem Problem during configuration Upload / Download. The Config Line “LED” turns red in ACM. The serial port seems to be available, but it is not possible to connect to the gateway Poor performance No sub-network functionality Anybus Communicator EtherNet/IP / Modbus-TCP User Manual Solution • Serial communication failed. Try again • The serial port may be in use by another application. Exit ACM and close all other applications including the ones in the system tray.
Appendix E E. ASCII Table x0 x1 x2 x3 x4 x5 x6 x7 x8 x9 xA xB xC xD xE xF BS 8 HT 9 LF 10 VT 11 FF 12 CR 13 SO 14 SI 15 FS 28 GS 29 RS 30 US 31 0x NUL SOH STX ETX EOT ENQ ACK BEL 0 1 2 3 4 5 6 7 1x DLE DC1 DC2 DC3 DC4 NAK SYN ETB CAN 16 17 18 19 20 21 22 23 24 EM 25 2x (sp) 32 ! 33 " 34 # 35 $ 36 % 37 & 38 ' 39 ( 40 ) 41 * 42 + 43 , 44 45 .
Appendix F F. Copyright Notices This product includes software developed by Carnegie Mellon, the Massachusetts Institute of Technology, the University of California, and RSA Data Security: ***************************************************************************** Copyright 1986 by Carnegie Mellon.
