User Manual Anybus® Communicator™ for PROFINET Doc. Id. HMSI-27-309 Rev. 3.11 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..................................................................................................................... 8 Document History ...................................................................................................................... 8 Conventions & Terminology ..................................................................................................... 9 Glossary................................
IV Chapter 4 Basic Network Configuration General Information................................................................................................................. 26 Ethernet Configuration File (“ethcfg.cfg”) ........................................................................... 27 General............................................................................................................................. 27 PROFINET Settings .........................................................
V Chapter 11 Nodes General........................................................................................................................................ 57 Adding & Managing Nodes ..................................................................................................... 57 Node Parameters ....................................................................................................................... 57 Master Mode and Generic Data Mode...........................................
VI Chapter 15 DF1 Protocol Mode General........................................................................................................................................ 76 Communicator Parameters ...................................................................................................... 77 Sub-network Parameters .......................................................................................................... 78 Node Parameters ....................................................
VII Chapter 21 Advanced Fieldbus Configuration General........................................................................................................................................ 97 Mailbox Editor........................................................................................................................... 97 Appendix A Connector Pin Assignments PROFINET Connector (Ethernet)........................................................................................
Preface P. About This Document For more information, documentation etc., please visit the HMS website www.anybus.com. P.1 Related Documents Document name Anybus Communicator - PRT Installation Sheet DF1 Protocol and Command Set - Reference Manual, 1770-6.5.16, October 1996 Author HMS Allen-Bradley P.2 Document History Summary of Recent Changes (3.01... 3.
About This Document 9 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 PROFINET 1.1 General The Anybus Communicator module for PROFINET acts as a gateway between virtually any serial application protocol and a PROFINET IO-based network. Integration of industrial devices is enabled without loss of functionality, control and reliability, both when retro-fitting to existing equipment as well as when setting up new installations. PROFINET IO Controller (e.g a PLC) PROFINET IO Controller (e.
About the Anybus Communicator for PROFINET 11 1.2 External View For wiring and pin assignments, see “Connector Pin Assignments” on page 98. A: PROFINET Connector (Ethernet) This connector is used to connect the module to the network. B See also... - “PROFINET Connector (Ethernet)” on page 98 A B: Status LEDs See also... - “Status LEDs” on page 12 C: PC-connector This connector is used to connect the module to a PC for configuration and monitoring purposes. C D F See also...
About the Anybus Communicator for PROFINET 12 1.3 Status LEDs # 1 - Comm.
About the Anybus Communicator for PROFINET 13 1.4 Hardware Installation Perform the following steps when physically installing the Anybus Communicator module: 1. Snap the module on to the DIN-rail.
About the Anybus Communicator for PROFINET 14 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 gateway is designed to exchange data between a serial sub-network and a higher level network. Unlike most other gateway devices of similar kind, it does not have a fixed protocol for the sub-network, and 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 of the higher level network (i.e.
Basic Operation 16 2.2 Data Exchange Model Internally, the data exchanged on the subnetwork, and the data exchanged on the higher level network, reside 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 memory locations specified using the Anybus Configuration Manager. The very same memory locations can then be exchanged on the subnetwork.
Basic Operation 17 2.2.2 Data Exchange Example In the following example, a temperature regulator on the subnetwork exchanges information with a PLC on the higher level network, via the internal memory buffers in the module.
Basic Operation 18 2.3 Subnetwork Protocol 2.3.1 Protocol Modes The Anybus Communicator features three distinct modes of operation regarding the subnetwork communication, called “Master Mode”, “Generic Data Mode” and “DF1 Master Mode”. Note that the protocol mode only specifies the basic communication model, not the actual subnetwork protocol. • Master Mode In this mode, the module acts as a master on the subnetwork, and the serial communication takes place in a query-response fashion.
Basic Operation 19 2.3.3 Master Mode In this mode, the communication is based on a query-response scheme; when the Anybus Communicator issues a query on the subnetwork, the addressed node is expected to issue a response to that query. Nodes are not permitted to issue responses spontaneously, i.e. without first receiving a query. There is one exception to this rule; the broadcaster.
Basic Operation 20 2.3.4 Generic Data Mode In this mode, there is no master-slave relationship between the nodes on the subnetwork and the Anybus Communicator. Any node, including the module, may spontaneously produce or consume a message. Nodes do not have to respond to messages, nor do they have to wait for a query in order to send one. Control System Gateway Subnetwork Devices In the figure above, the Anybus Communicator “consumes” data that is “produced” by a node on the subnetwork.
Basic Operation 21 2.4 PROFINET IO 2.4.1 General The PROFINET IO interface provides PROFINET IO Soft Real-Time Communication. PROFINET is the open Industrial Ethernet standard for Automation from PROFIBUS International.
Basic Operation 22 2.4.4 Data Representation (IO Data & Record Data) As mentioned previously, the actual I/O configuration is determined by the IO Controller. The modules are mapped to the input and output data areas in the order of their slot number.
Basic Operation 23 2.5 Modbus-TCP (Read-Only) 2.5.1 General The Modbus-TCP protocol is an implementation of the standard Modbus protocol running on top of TCP/IP. The same function codes and addressing model are used. The built in Modbus-TCP server provides read-only access to the input and output data areas via a subset of the functions defined in the Modbus-TCP specification. All Modbus-TCP messages are received/transmitted on TCP port no. 502.
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. 2 Mb) This section is intended for static files such as web files, configuration files etc. • Volatile area (approx.
File System 25 3.2 File System Overview (admin root) (user root) user ip_accs.cfg ssi_str.cfg http.cfg pswd (protected) ethcfg.cfg sys_pswd.cfg pniocfg.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. These files, known as “system files”, are regular ASCII files which can be altered using a standard text editor.
Chapter 4 4. Basic Network Configuration 4.1 General Information The Anybus Communicator offers two modes of operation regarding the network settings (see below). Which mode to use is determined by the “TCP/IP Settings” parameter in Anybus Configuration Manager, see “Fieldbus Settings” on page 54. • TCP/IP Settings: Enabled When operating in this mode, the contents of the system file “ethcfg.
Basic Network Configuration 27 4.2 Ethernet Configuration File (“ethcfg.cfg”) 4.2.1 General To be able to participate on the network, the Anybus Communicator needs a valid TCP/IP configuration. These settings are stored in the system file “\ethcfg.cfg”. File Format: [IP address] xxx.xxx.xxx.xxx [Subnet mask] xxx.xxx.xxx.xxx [Gateway address} xxx.xxx.xxx.xxx [DHCP/BOOTP] ON or OFF • IP address • Subnet mask • Gateway address • DHCP/BootP ON - Enabled OFF - Disabled [SMTP address] xxx.xxx.xxx.
Basic Network Configuration 28 4.3 PROFINET Settings The file “\pnio.cfg” holds various PROFINET-related settings. The file is read once during startup, i.e. the Anybus Communicator must be restarted in order for any changes to have effect (unless its contents has been changed by an IO Controller/Supervisor via the DCP protocol. In such case, the settings will have effect immediately). Example: • [Station Name] Nice Device Station Name Station name as ASCII string, maximum 64 characters.
Basic Network Configuration 29 4.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 5 5. FTP Server 5.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 5.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 6 6. Web Server 6.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 35 • “IP Access Control” on page 28 Protected Files For security reasons, the following files are protected from web access: • Files located in “\user\pswdcfg\pswd” •
Web Server 33 6.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 • List of approved users. • Optionally, a login message can be specified by including the key [AuthName].
Web Server 34 6.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 7 7. Server Side Include (SSI) 7.1 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 Communicator encounters such a command, it will execute it, and replace it with the result (when applicable). Syntax XXX... below represents a command opcode and parameters associated with the command.
Server Side Include (SSI) 36 7.2 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 network interface. Syntax: DisplayFWVersion This function returns the main firmware revision of the network interface.
Server Side Include (SSI) 37 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) 38 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) 39 StoreEtnIPConfig Note: This function cannot be used in e-mail messages. This 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) 40 printf This function includes a formatted string, which may contain data from the input and output data areas, on a web page. The formatting of the string is similar to the C-language function printf(). Syntax:
Server Side Include (SSI) 41 The arguments that can be passed to the SSI function printf are: Argument InReadSByte(offset) InReadUByte(offset) InReadSWord(offset) InReadUWord(offset) InReadSLong(offset) InReadULong(offset) InReadString(offset) InReadFloat(offset) OutReadSByte(offset) OutReadUByte(offset) OutReadSWord(offset) OutReadUWord(offset) OutReadSLong(offset) OutReadULong(offset) OutReadString(offset) OutReadFloat(offset) CipReadSByte(class, inst, attr) CipReadUByte(class, inst, attr) CipReadSWord(c
Server Side Include (SSI) 42 scanf Note: This function cannot be used in e-mail messages. This function reads a string passed from an object in a HTML form, interprets the string according to the specification in format, and stores the result in the Output Data area according to the passed arguments. The formatting of the string is equal to the standard C function call scanf() Syntax:
Server Side Include (SSI) 43 IncludeFile This function includes the contents of a file on a web page. Syntax: Default output: Success Failure - - Failed to open SaveToFile Note: This function cannot be used in e-mail messages. This function saves the contents of a passed form to a file. The passed name/value pair will be written to the file “File name” separated by the “Separator” string.
Server Side Include (SSI) 44 DisplayScannerMode This function returns the current scanner mode (run or idle state). Syntax: SetScannerMode Note: This function cannot be used in email messages. This function is used to set the EtherNet/IP Scanner to Run or Idle. A variable called “scanner_state” shall be sent to the page with the value “run” or “idle” (other values will be ignored).
Server Side Include (SSI) 45 7.3 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. Temporarily changing the SSI output by calling the SSI function “SsiOutput()”. 7.3.1 SSI Output String File If the file “\ssi_str.
Server Side Include (SSI) 46 7.3.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 8 8. E-mail Client 8.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 email messages (specified separately for each SSI function). See also... • “Server Side Include (SSI)” on page 35 Server Settings The Anybus Communicator needs a valid SMTP server configuration in order to be able to send e-mail messages.
E-mail Client 48 8.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 module.
Chapter 3 3. Navigating ACM 3.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 20 3.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 21 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 58). Note that when the Data Logger is active, this menu entry is changed to “Stop Logging”.
Navigating ACM 22 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 58. Download firmware to the embedded fieldbus interface.
Navigating ACM 23 3.1.2 Toolbar Icons The toolbar features icons for the most commonly used functions. • New, Open & Save See “File” on page 20. • New Open Save Upload from ABC & Download to ABC See “Tools” on page 21. 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 10 10. Basic Settings 10.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 module.
25 4.2 Communicator Parameters Interface Only serial communication is currently supported. Control/Status Word See “Control and Status Registers” on page 62. 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.
26 4.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 5 5. Nodes 5.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. 5.2 Adding & Managing Nodes Function Paste Subnetwork Monitor Add Node Add Broadcastera Load Node Subnetwork Status...
Chapter 6 6. Transactions 6.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 29 6.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 54) 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 30 6.3 Transaction Parameters (Master Mode) 6.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 31 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 32 6.4 Transaction Parameters (Generic Data Mode) 6.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 33 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 34 6.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 7 7. Frame Objects 7.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 36 7.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 37 7.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 38 7.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 39 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 40 7.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 8 8. Commands This information is only valid for the Master and Generic Data modes. For DF1 master mode, please refer to “Services” on page 49. 8.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 42 8.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 43. • Edit Command Edit the currently selected command using the Command Editor.
Commands 43 8.3 The Command Editor 8.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 44 8.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. 8.3.
Commands 45 8.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 9 9. DF1 Protocol Mode This mode makes the Anybus Communicator act as a DF1 protocol master on the sub-network. 9.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 47 9.2 Communicator Parameters Interface Currently, only serial communication is supported. Control/Status Word (See “Control and Status Registers” on page 62). 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 48 9.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 49 9.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 27. 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 9.5 Services Services are commands that can be stored and reused.
DF1 Protocol Mode 50 9.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 51 9.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. 9.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 52 9.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 10 10. Sub-network Monitor 10.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 11 11. Node Monitor 11.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 55 11.2 Navigating the Node Monitor A B C D A: Drop-down Menu & Toolbar Icons See “Drop-down Menu” on page 56 and “Toolbar Icons” on page 57. 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 56 11.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 57 11.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 56. • 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 56.
Chapter 12 12. Data Logger 12.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. 12.
Data Logger 59 12.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 PROFINET User Manual Doc: HMSI-27-309, Rev. 3.
Chapter 19 19. Configuration Wizards 19.1 General When creating a new subnetwork 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 subnetwork configuration based on information supplied by the user, i.e the user simply has to “fill in the blanks”.
Configuration Wizards 91 19.3 Wizard - Modbus RTU Master This wizard can be used to create a Modbus-RTU-based network configuration based on certain information about the subnetwork. 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 14 14. Control and Status Registers 14.1 General The Control and Status Registers are disabled by default, but can be enabled using ACM (see “Control/ Status Word” on page 25). 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 63 14.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 64 14.2 Status Register Contents (Gateway to Control System) 14.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 65 14.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 66 14.3 Control Register Contents (Control System to Gateway) 14.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 15 15. Advanced Fieldbus Configuration 15.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. Connector Pin Assignments A.1 PROFINET Connector (Ethernet) Pin Housing 1 2 3 4 5 6 7 Signal Cable Shield TD+ TDRD+ Termination Termination RDTermination 8 Termination 1 8 A.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 PROFINET User Manual Doc: HMSI-27-309, Rev. 3.
Connector Pin Assignments 99 A.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 100 A.4 Subnetwork Interface A.4.1 General Information The subnetwork interface provides for RS232, RS422 and RS485 communication. Depending on the configuration specified in the Anybus Configuration Manager, different signals are activated in the subnetwork connector. A.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 101 A.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 A.4.
Appendix B B. Technical Specification B.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”) B.2 Electrical Characteristics Power Supply Power: 24 VDC ± 10% Power Consumption Maximum power consumption is 280 mA on 24 VDC. Typically around 100 mA. B.3 Environmental Characteristics Relative Humidity The product is designed for a relative humidity of 0 to 95 % non-condensing.
Technical Specification 73 B.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 74 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 C C. 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 PROFINET 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 D D. 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.
