HMS Anybus Communicator for PROFINET User Manual
+$/067$'&+,&$*2.$5/658+(72.<2%(,-,1*0,/$1208/+286(&29(175<381(&23(1+$*(1
HMS Industrial Networks
Mailing address: Box 4126, 300 04 Halmstad, Sweden
Visiting address: Stationsgatan 37, Halmstad, Sweden
Connecting Devices
TM
E-mail: info@hms-networks.com
Web: www.anybus.com
User Manual
Anybus® Communicator™
for PROFINET
Doc. Id. HMSI-27-309
Rev. 3.11
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. Please inform HMS Industrial Networks AB of any
inaccuracies or omissions. The data and illustrations found in this document are not binding. We, HMS Industrial
Networks AB, reserve the right to modify our products in line with our policy of continuous product development.
The information in this document is subject to change without notice and should not be considered as a commit-
ment by HMS Industrial Networks AB. HMS Industrial Networks AB assumes no responsibility for any errors that
may appear in this document.
There are many applications of this product. Those responsible for the use of this device must ensure that all the
necessary steps have been taken to verify that the applications meet all performance and safety requirements in-
cluding any applicable laws, regulations, codes, and standards.
HMS Industrial Networks AB will under no circumstances assume liability or responsibility for any problems that
may arise as a result from the use of undocumented features, timing, or functional side effects found outside the
documented scope of this product. The effects caused by any direct or indirect use of such aspects of the product
are undefined, and may include e.g. compatibility issues and stability issues.
The examples and illustrations in this document are included solely for illustrative purposes. Because of the many
variables and requirements associated with any particular implementation, HMS Industrial Networks AB cannot
assume responsibility for actual use based on these examples and illustrations.
Intellectual Property Rights
HMS Industrial Networks AB has intellectual property rights relating to technology embodied in the product de-
scribed in this document. These intellectual property rights may include patents and pending patent applications
in the US and other countries.
Trademark Acknowledgements
Anybus® is a registered trademark of HMS Industrial Networks AB. Microsoft® and Windows® are registered
trademarks of Microsoft, Inc. All other trademarks are the property of their respective holders.
Warning: This is a class A product. in a domestic environment this product may cause radio interference in
ESD Note: This product contains ESD (Electrostatic Discharge) sensitive parts that may be damaged if ESD
which case the user may be required to take adequate measures.
control procedures are not followed. Static control precautions are required when handling the
product. Failure to observe this may cause damage to the product.
Anybus Communicator PROFINET User Manual
Copyright© HMS Industrial Networks AB
Doc: HMSI-27-309
Doc: HMSI-27-309, Rev. 3.11Anybus Communicator PROFINET User Manual
Table of Contents
Preface About This Document
Related Documents ..................................................................................................................... 8
Document History ...................................................................................................................... 8
Conventions & Terminology ..................................................................................................... 9
Glossary.............................................................................................................................. 9
Support.......................................................................................................................................... 9
Chapter 1 About the Anybus Communicator for PROFINET
General........................................................................................................................................ 10
External View............................................................................................................................. 11
Status LEDs ............................................................................................................................... 12
Hardware Installation................................................................................................................ 13
Table of Contents
Software Installation .................................................................................................................14
Anybus Configuration Manager ........................................................................................ 14
Chapter 2 Basic Operation
General........................................................................................................................................ 15
Data Exchange Model .............................................................................................................. 16
Memory Map.................................................................................................................... 16
Data Exchange Example................................................................................................. 17
Subnetwork Protocol ................................................................................................................ 18
Protocol Modes.................................................................................................................. 18
Protocol Building Blocks.................................................................................................... 18
Master Mode..................................................................................................................... 19
Generic Data Mode .......................................................................................................... 20
DF1 Master Mode ........................................................................................................... 20
PROFINET IO ......................................................................................................................... 21
General............................................................................................................................. 21
I/O Configuration ............................................................................................................ 21
GSDML File .................................................................................................................. 21
Data Representation (IO Data & Record Data).............................................................. 22
Modbus-TCP (Read-Only)....................................................................................................... 23
General............................................................................................................................. 23
Data Representation (Modbus-TCP Register Map)........................................................... 23
Supported Exception codes................................................................................................. 23
Chapter 3 File System
General........................................................................................................................................ 24
File System Overview ............................................................................................................... 25
System Files ................................................................................................................................ 25
Doc: HMSI-27-309, Rev. 3.11Anybus Communicator PROFINET User Manual
Chapter 4 Basic Network Configuration
General Information ................................................................................................................. 26
Ethernet Configuration File (“ethcfg.cfg”) ........................................................................... 27
General............................................................................................................................. 27
PROFINET Settings ................................................................................................................ 28
IP Access Control ..................................................................................................................... 28
Anybus IPconfig (HICP) ......................................................................................................... 29
Chapter 5 FTP Server
General........................................................................................................................................ 30
FTP Connection Example (Windows Explorer).................................................................. 31
Chapter 6 Web Server
General........................................................................................................................................ 32
Authorization .............................................................................................................................33
Content Types............................................................................................................................ 34
IV
Chapter 7 Server Side Include (SSI)
General........................................................................................................................................ 35
Functions .................................................................................................................................... 36
Changing SSI output................................................................................................................. 45
SSI Output String File..................................................................................................... 45
Temporary SSI Output Change ........................................................................................ 46
Chapter 8 E-mail Client
General........................................................................................................................................ 47
E-mail Definitions..................................................................................................................... 48
Chapter 9 Navigating ACM
Main Window............................................................................................................................. 49
Drop-down Menus ............................................................................................................ 50
Toolbar Icons .................................................................................................................... 53
Chapter 10 Basic Settings
Fieldbus Settings........................................................................................................................ 54
Communicator Parameters ...................................................................................................... 55
Sub-network Parameters ..........................................................................................................56
Doc: HMSI-27-309, Rev. 3.11Anybus Communicator PROFINET User Manual
Chapter 11 Nodes
General........................................................................................................................................ 57
Adding & Managing Nodes ..................................................................................................... 57
Node Parameters ....................................................................................................................... 57
Master Mode and Generic Data Mode.............................................................................. 57
Chapter 12 Transactions
General........................................................................................................................................ 58
Adding & Managing Transactions .......................................................................................... 59
Transaction Parameters (Master Mode)................................................................................. 60
Parameters (Query & Broadcast)...................................................................................... 60
Parameters (Response)....................................................................................................... 61
Transaction Parameters (Generic Data Mode) ..................................................................... 62
Produce Transactions......................................................................................................... 62
Consume Transactions ...................................................................................................... 63
Transaction Editor .................................................................................................................... 64
V
Chapter 13 Frame Objects
General........................................................................................................................................ 65
Adding and Editing Frame Objects ....................................................................................... 65
Constant Objects (Byte, Word, Dword) ................................................................................ 66
Limit Objects (Byte, Word, Dword) ...................................................................................... 67
Data Object ................................................................................................................................ 68
Variable Data Object ................................................................................................................ 68
Checksum Object ...................................................................................................................... 70
Chapter 14 Commands
General........................................................................................................................................ 71
Adding & Managing Commands ............................................................................................ 71
Drop-down Menu ............................................................................................................ 72
Toolbar Icons .................................................................................................................... 72
The Command Editor ..............................................................................................................73
General............................................................................................................................. 73
Basic Navigation............................................................................................................... 73
Drop-down Menu ............................................................................................................ 74
Editing a Command ......................................................................................................... 74
Example: Specifying a Modbus-RTU Command in Master Mode .................................... 75
Doc: HMSI-27-309, Rev. 3.11Anybus Communicator PROFINET User Manual
Chapter 15 DF1 Protocol Mode
General........................................................................................................................................ 76
Communicator Parameters ...................................................................................................... 77
Sub-network Parameters ..........................................................................................................78
Node Parameters ....................................................................................................................... 79
Services........................................................................................................................................ 79
Available Services ............................................................................................................. 80
Integrity Check .......................................................................................................................... 81
Read Diagnostics ....................................................................................................................... 81
Read Data ................................................................................................................................... 82
Write Data .................................................................................................................................. 82
Chapter 16 Sub-network Monitor
General........................................................................................................................................ 83
Operation.................................................................................................................................... 83
VI
Chapter 17 Node Monitor
General........................................................................................................................................ 84
Navigating the Node Monitor ................................................................................................. 85
Drop-down Menu ............................................................................................................ 86
Toolbar Icons .................................................................................................................... 87
Chapter 18 Data Logger
General........................................................................................................................................ 88
Operation.................................................................................................................................... 88
Configuration ............................................................................................................................. 89
Chapter 19 Configuration Wizards
General........................................................................................................................................ 90
Selecting a Wizard Profile ........................................................................................................ 90
Wizard - Modbus RTU Master ............................................................................................... 91
Chapter 20 Control and Status Registers
General........................................................................................................................................ 92
Handshaking Procedure .................................................................................................... 92
Data Consistency .............................................................................................................. 93
Status Register Contents (Gateway to Control System) ...................................................... 94
General Information.......................................................................................................... 94
Status Codes in Master Mode and DF1 Master Mode...................................................... 94
Status Code in Generic Data Mode................................................................................... 95
Control Register Contents (Control System to Gateway)................................................... 96
General Information.......................................................................................................... 96
Control Codes in Master Mode and DF1 Master Mode.................................................... 96
Control Codes in Generic Data Mode ............................................................................... 96
Doc: HMSI-27-309, Rev. 3.11Anybus Communicator PROFINET User Manual
Chapter 21 Advanced Fieldbus Configuration
General........................................................................................................................................ 97
Mailbox Editor........................................................................................................................... 97
Appendix A Connector Pin Assignments
PROFINET Connector (Ethernet)........................................................................................ 98
Power Connector ...................................................................................................................... 98
PC Connector ............................................................................................................................ 99
Subnetwork Interface ............................................................................................................. 100
General Information........................................................................................................ 100
Bias Resistors (RS485 Only).......................................................................................... 100
Termination (RS485 & RS422 Only) .......................................................................... 100
Connector Pinout (DB9F) .............................................................................................. 100
Typical Connection (RS485)........................................................................................... 101
Typical Connection (RS422 & 4-Wire RS485) ............................................................ 101
Typical Connection (RS232)........................................................................................... 101
Appendix B Technical Specification
VII
Mechanical Properties............................................................................................................. 102
Electrical Characteristics ........................................................................................................ 102
Environmental Characteristics .............................................................................................. 102
Regulatory Compliance .......................................................................................................... 103
Appendix C Troubleshooting
Appendix D ASCII Table
Appendix E Copyright Notices
Doc: HMSI-27-309, Rev. 3.11Anybus Communicator PROFINET User Manual
P. About This Document
For more information, documentation etc., please visit the HMS website www.anybus.com.
P.1 Related Documents
Document name Author
Anybus Communicator - PRT Installation Sheet HMS
DF1 Protocol and Command Set - Reference Manual, 1770-6.5.16, October 1996 Allen-Bradley
P.2 Document History
Summary of Recent Changes (3.01... 3.10)
Change Page(s)
Screenshots and descriptions of ABC Tool updated for Anybus Configuration Manager Multiple
Changed “ABC” to “Communicator RS232/422/485” Multiple
Amended description of “Update time” parameter 31, 32
Added description for Consume/Response to “Object Delimiter” parameter 39
Changed “Maximum Data Length” limit 39
Removed obsolete “Start Bits” parameter 48
Removed obsolete “ABCC ExtLink Wizard” entry 64
Replaced “Sales and Support” info with link to website 8
Added parameters to checksum object description 40
Added info about Modbus registers 23
Minor text edits, typo corrections Multiple
Preface
Summary of Recent Changes (3.10... 3.11)
Revision Change Page(s)
3.11 Added compliance info 79
Revision List
Revision Date Author Chapter Description
1.00 2005-06-07 PeP All 1st release
2.00 2006-03-27 PeP All 2nd major release
2.01 2006-12-22 PeP - Misc. minor corrections & updates
2.02 2008-10-14 HeS - Misc. minor corrections & updates
2.03 2009-04-24 KeL All Misc. minor corrections and updates
3.00 2011-01-19 KaD All Misc. minor corrections, new template and DF1 functionality
3.01 2011-09-30 KaD All Misc corrections and updates, new Anybus Configuration
Manager name
3.10 February 2015 ThN All Misc. corrections and updates, new Doc ID
3.11 March 2015 ThN B Added compliance info
Doc: HMSI-27-309, Rev. 3.11Anybus Communicator PROFINET User Manual
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 Commu-
nicator 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.
• Decimal values are represented as NNNN where NNNN is the decimal value
• As in all communication systems, the terms “input” and “output” can be ambiguous, because
their meaning depend on which end of the link is being referenced. The convention in this doc-
ument is that “input” and “output” are always being referenced to the master/scanner end of the
link.
P.3.1 Glossary
Term Meaning
ABC
PRT PROFINET-IO
ACM Anybus Configuration Manager
Broadcaster A protocol specific node in the subnetwork scan- that hold transactions destined to all nodes.
Command A protocol specific transaction.
Configuration List of configured nodes with transactions on the subnetwork.
Fieldbus The network to which the communicator is connected.
Fieldbus Control System Fieldbus master
Frame Higher level series of bytes forming a complete telegram on the subnetwork
Monitor A tool for debugging the ABC and the network connections.
Node A device in the configuration that defines the communication with a node on the subnetwork
Scan list List of configured slaves with transactions on the subnetwork.
Subnetwork
Transaction
IO Controller
IO Supervisor
IO Device Field device assigned to an IO Controller. In this case the ABC.
Module (or I/O module) Hardware or logical component of a PROFINET network device.
Higher Level Network In this case, PROFINET
Network
Fieldbus
®
Anybus
Communicator™
The network that logically is located on a subsidiary level with respect to the fieldbus and to
which the ABC acts as a gateway.
A generic building block that is used in the subnetwork scan-list and defines the data that is
sent and received on the subnetwork.
PROFINET device which acts as a client for several IO devices, usually a PLC. (Comparable to
a PROFIBUS-DP class 1 master).
PROFINET programming device with commissioning and diagnostic functions (Comparable to
a PROFIBUS-DP class 2 master).
About This Document 9
P.4 Support
For general contact information and support, please refer to the contact and support pages at
www.anybus.com
Doc: HMSI-27-309, Rev. 3.11Anybus Communicator PROFINET User Manual
1. About the Anybus Communicator for
PC configuration
and monitoring
Serial communication devices
Multi-drop up to 31 nodes
Multi-Node Serial Sub NetworkSingle-Node Serial Sub Network
PC configuration
and monitoring
PROFINET IO Controller
(e.g a PLC)
PROFINET IO Controller
(e.g a PLC)
Serial communication
device
INVERTER
HMI
(Ethernet)
(Ethernet)
PC / web / SCADA
C/ eb/SC
PC / web / SCADA
C/ eb/SC
PROFINET
1.1 General
The Anybus Communicator module for PROFINET acts as a gateway between virtually any serial ap-
plication 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.
Chapter 1
Subnetwork
The Anybus Communicator can address up to 31 nodes, and supports the following physical standards:
•RS-232
•RS-422
•RS-485
Ethernet Interface
Ethernet connectivity is provided through the patented Anybus technology; a proven industrial commu-
nication solution used all over the world by leading manufacturers of industrial automation products.
•PROFINET IO
• Modbus-TCP server (read only)
• Security framework with per user access rights and IP access control
• Server Side Include (SSI) functionality
• Web server and Email client capability
• Easy file management via FTP
• 10/100 Mbit/s, twisted pair
Doc: HMSI-27-309, Rev. 3.11Anybus Communicator PROFINET User Manual
About the Anybus Communicator for PROFINET 11
F
A
B
C
D
E
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 net-
work.
See also...
- “PROFINET Connector (Ethernet)” on page 98
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.
See also...
- “PC Connector” on page 99
D: Subnetwork Connector
This connector is used to connect the module to the serial
subnetwork.
See also...
- “Subnetwork Interface” on page 100
E: Power Connector
This connector is used to apply power to the module.
See also...
- “Power Connector” on page 98
- “Technical Specification” on page 128
F: DIN-rail Connector
The DIN-rail mechanism connects the module to PE (Protective Earth).
See also...
- “Hardware Installation” on page 13
Doc: HMSI-27-309, Rev. 3.11Anybus Communicator PROFINET User Manual
1.3 Status LEDs
1
3
5
2
4
6
# State Status
1 - Comm. Status Off Off line
Green On line, Run
Green, flashing On line, STOP
2 -Module Status Off No power or not initialized
Green Initialized, no error
Green, 1 flash Diagnostic data available
Green, 2 flashes Blink. Used by engineering tools for identification.
Red, 1 flash Configuration Error
Red, 3 flashes No Station Name or no IP address assigned
Red, 4 flashes Internal error
3 - Link/Activity Off No link or power off
Green Link established
Green, flashing Receiving/transmitting data
4 - (not used)
5 - Subnet Status
6 - Device Status Off Power off
a. This LED turns green when all transactions have been active at least once. This includes
any transactions using “change of state” or “change of state on trigger”. If a timeout
occurs on a transaction, this LED will turn red.
b. The gateway is in bootloader mode, and firmware must be restored in order for it to work
properly. Start up the Anybus Configuration Manager and connect to the Anybus Commu-
nicator. Choose Tools/Options/Module. Click “Factory Restore” to restore firmware. See
“Tools” on page 61.
- -
a
Off Power off
Green, flashing Running correctly, but one or more transaction
Green Running
Red Transaction error/timeout or subnet stopped
Alternating Red/Green Invalid or missing configuration
Green Initializing
Green, flashing Running
Red
Red, flashing If the Device Status LED is flashing in a sequence
About the Anybus Communicator for PROFINET 12
- No connection with IO Controller
- Connection with IO Controller established
- IO Controller is in RUN state
- Connection with IO Controller established
- IO Controller in STOP state
- Too many modules/submodules
- I/O size or Configuration mismatch
error(s) have occurred
Bootloader mode
b
starting with one or more red flashes, please note
the sequence pattern and contact the HMS support
department
Doc: HMSI-27-309, Rev. 3.11Anybus Communicator PROFINET User Manual
About the Anybus Communicator for PROFINET 13
1
2
1
2
1.4 Hardware Installation
Perform the following steps when physically installing the Anybus Communicator module:
1. Snap the module on to the DIN-rail.
The DIN-rail mechanism works as follows:
To snap the module on, first press it downwards (1) to compress the
spring in the DIN-rail mechanism, then push it against the DIN-rail as to
make it snap on (2)
To snap the module off, push it downwards (1) and pull it out from the
DIN-rail (2), as to make it snap off from the DIN-rail
2. Connect the module to the PROFINET (Ethernet) network
3. Connect the module to the serial subnetwork
4. Connect the module to the PC via the configuration cable
5. Connect the power cable and apply power
6. Start the Anybus Configuration Manager program on the PC
(The Anybus Configuration Manager software attempts to detect the serial port automatically. If
not successful, select the correct port manually in the “Port”-menu)
7. Configure the Anybus Communicator using the Anybus Configuration Manager and download
the configuration
8. Set up the PROFINET communication in accordance with the module configuration
Doc: HMSI-27-309, Rev. 3.11Anybus Communicator PROFINET User Manual
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.
- If the installation does not start automatically: right-click on the CD drive icon and select
“Explore” to show the contents of the CD. Locate the installation executable and double-
click on it to start the installation, then follow the on-screen instructions.
About the Anybus Communicator for PROFINET 14
• From HMS website
- Download the latest version of Anybus Configuration Manager from www.anybus.com.
- Unzip the archive on your computer and double-click on the installation executable.
Doc: HMSI-27-309, Rev. 3.11Anybus Communicator PROFINET User Manual
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. the fieldbus master or PLC). It can also monitor
certain aspects of the sub-network communication and notify the higher level network when data has
changed.
An essential part of the Anybus Communicator package is Anybus Configuration Manager (ACM), a
Windows®-based application used to supply the gateway with a description of the sub-network proto-
col. No programming skills are required; instead, a visual protocol description-system is used to specify
the different parts of the serial communication.
Chapter 2
Doc: HMSI-27-309, Rev. 3.11Anybus Communicator PROFINET User Manual
2.2 Data Exchange Model
General Data
ABC Internal Memory
Input Data
(512 bytes)
Subnetwork
Output Data
(512 bytes)
Higher Level Network
Input Data Output Data General Data
Subnetwork:
Fieldbus:
E-mail Client:
SSI:
Subnetwork:
Fieldbus:
E-mail Client:
SSI:
Subnetwork:
Fieldbus:
E-mail Client:
SSI:
Read/Write
Read Only
Read Only
Read Only
Read Only
Read/Write
Read Only
Read/Write
Read/Write
-
-
-
0x000 0x200
0x1FF 0x3FF
0x400
0x???
Internally, the data exchanged on the subnetwork, and
the data exchanged on the higher level network, reside
in the same memory.
This means that in order to exchange data with the sub-
network, the higher level network simply reads and
writes data to memory locations specified using the An-
ybus Configuration Manager. The very same memory
locations can then be exchanged on the subnetwork.
The internal memory buffer is divided into three areas
based on their function:
• Input Data (512 bytes)
This area can be read by the higher level net-
work, the web server and the e-mail client.
(How this data is represented on the higher level
network will be described later in this chapter).
• Output Data (512 bytes)
This area can be read from/written to by the
higher level network, the web server and the e-
mail client.
(How this data is represented on the higher level
network will be described later in this chapter).
Basic Operation 16
• General Data (Up to 1024 bytes)
This area cannot be accessed from the higher level network, but can be used for transfers be-
tween individual nodes on the subnetwork, or as a general “scratch pad” for data. The actual size
of this area depends on the amount of data that is exchanged on the subnetwork. The Anybus
Communicator can handle up to 1024 bytes of general data.
2.2.1 Memory Map
When building the subnetwork configuration using the Anybus Configuration Manager, the different ar-
eas described above are mapped to the memory locations (addresses) specified below.
Doc: HMSI-27-309, Rev. 3.11Anybus Communicator PROFINET User Manual
Basic Operation 17
The Temperature Regulator has two
registers, holding the Setpoint Temperature
and the Actual Temperature respectively.
The PLC exchange data between the internal
PLC memory and the slaves (in this case the
ABC) on the PROFINET network.
The ABC copies the Output Register of
the Temperature Regulator to the Input-
Data area.
The ABC copies the Temperature-
Setpoint from the Output Data area to
the Input Register in the Temperature-
Regulator.
The PLC Memory associated with
the ABC is exchanged;
Data from the Input Data area is copied to
PLC Input Memory, and PLC Output
Memory is copied to the Output Data
area.
Input Data
ABC
Serial Device - Temperature Regulator
PLC (PROFINET IO Controller)
Output Data General Data
0x000 0x200
0x1FF 0x3FF
0x400
0x???
Output Register Input Register
Temperature Setpoint
Temperature Setpoint
Actual Temperature
Actual Temperature
PLC Memory (Inputs) PLC Memory (Outputs)
Temperature Setpoint
Actual Temperature
(not used in this example)
PROFINETSubnetwork
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.
Doc: HMSI-27-309, Rev. 3.11Anybus Communicator PROFINET User Manual
Basic Operation 18
2.3 Subnetwork Protocol
2.3.1 Protocol Modes
The Anybus Communicator features three distinct modes of operation regarding the subnetwork com-
munication, called “Master Mode”, “Generic Data Mode” and “DF1 Master Mode”. Note that the pro-
tocol 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. The nodes on the network are not permitted to issue messages
unless they have been addressed by the module first.
See also “Master Mode” on page 19.
• Generic Data Mode
In this mode, there is no master-slave relationship between the subnetwork nodes and the mod-
ule; any node on the subnetwork, including the Anybus Communicator, may spontaneously pro-
duce or consume messages.
See also “Generic Data Mode” on page 20.
• DF1 Master Mode
In this mode, the module acts as a master on the subnetwork, using the DF1 protocol. The serial
communication takes place in a query-response fashion.
See also “DF1 Protocol Mode” on page 76.
2.3.2 Protocol Building Blocks
The following building blocks are used in Anybus Configuration Manager to describe the subnetwork
communication. How these blocks apply to the three protocol modes will be described later in this doc-
ument.
•Node
A node represents a single device on the subnetwork. Each node can be associated with a num-
ber of transactions, see below.
•Transaction
A “transaction” represents a complete serial telegram, and consists of a number of frame objects
(below). Each transaction is associated with a set of parameters controlling how and when to use
it on the subnetwork.
• Commands
A “command” is simply a predefined transaction stored in a list in the Anybus Configuration
Manager. This simplifies common operations by allowing transactions to be stored and reused.
• Frame Object
“Frame objects” are low level entities used to compose a transaction (see above). A frame object
can represent a fixed value (a constant), a range of values (limit objects), a block of data or a cal-
culated checksum.
Doc: HMSI-27-309, Rev. 3.11Anybus Communicator PROFINET User Manual
Basic Operation 19
Subnetwork Devices
Gateway
Control System
2.3.3 Master Mode
In this mode, the communication is based on a query-response scheme; when the Anybus Communica-
tor 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. Most protocols offer some way of broadcasting mes-
sages to all nodes on the network, without expecting them to respond to the broadcasted message. This
is also reflected in the Anybus Communicator, which features a dedicated broadcaster node.
In Master Mode, Anybus Configuration Manager comes preloaded with most commonly used Modbus
RTU commands, which can conveniently be reached by right-clicking on a node in the Anybus Config-
uration Manager and selecting “Insert New Command”. Note however that this does not in any way
prevent other protocols based on the same query-response message-scheme to be implemented.
Doc: HMSI-27-309, Rev. 3.11Anybus Communicator PROFINET User Manual
Basic Operation 20
Subnetwork Devices
Control System
Gateway
2.3.4 Generic Data Mode
In this mode, there is no master-slave relationship between the nodes on the subnetwork and the Any-
bus Communicator. Any node, including the module, may spontaneously produce or consume a mes-
sage. Nodes do not have to respond to messages, nor do they have to wait for a query in order to send
one.
In the figure above, the Anybus Communicator “consumes” data that is “produced” by a node on the
subnetwork. This “consumed” data can then be accessed from the higher level network. This also works
the other way around; the data received from the higher level network is used to “produce” a message
on the subnetwork to be “consumed” by a node.
2.3.5 DF1 Master Mode
Please refer to “DF1 Protocol Mode” on page 76.
Doc: HMSI-27-309, Rev. 3.11Anybus Communicator PROFINET User Manual
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.
Supported Features
• Soft Real-Time (RT) communication
• Cyclic data exchange (10 ms cycle time)
• Acyclic Data exchange (Record Data Requests)
• Up to 64 slots / 1 subslot
• Up to 512 bytes of I/O in each direction
• TCP/IP Configuration via DCP (Discovery and Configuration Protocol)
2.4.2 I/O Configuration
PROFINET makes a distinction between fast cyclical data, a.k.a. “IO data”, and acyclical data, called
“Record Data”. By default, all data in the input and output data areas are exchanged as IO data. It is
however possible to specify how much data to exchange as IO data, and how much data to exchange
using acyclic Record Data read/write requests.
On PROFIN ET, the IO data is built up by I/O mod ules. In the case of the ABC, the act ual I/O module
configuration is adopted from the I/O controller/supervisor, provided that the total I/O sizes specified
by the IO controller does not exceed the sizes specified in the Anybus Configuration Manager.
For information about how the IO and Record Data relates to the input and output data areas, see “Da-
ta Representation (IO Data & Record Data)” on page 22.
2.4.3 GSDML File
On PROFINET, all devices are associated with a GSDML file. The GSDML file is the equivalent of the
PROFIBUS GSD file, and is based on the EXtensible Markup Language (XML).
This file holds information about the device (in this case the Anybus Communicator), its features, and
possible I/O configurations. The latest version of the GSDML file for the Anybus Communicator can
be downloaded from the HMS website, “www.anybus.com
”.
Doc: HMSI-27-309, Rev. 3.11Anybus Communicator PROFINET User Manual
Basic Operation 22
Input Data Output Data
16 Input0x000 ... 0x00F
0x0A0
16 Input/Output0x010 ... 0x01F
0x09F
0x0DF
0x1FF
0x020
16 Input/Output0x200 ... 0x20F
128 Input
128 Output
(unused)
32 Input0x0E0 ... 0x0FF
64 Input/Output
64 Output
64 Input/Output
Record Data Index 1000h
Record Data Index 10FFh
Record Data Index 2000h
Record Data Index 206Fh
IO Size In
(256 bytes)
IO Size Out
(400 bytes)
0x30F
0x3FF
0x290
0x38F
0x310
0x210
0x24F
0x100
0x250
0x28F
0x390
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.
Example:
In this example, the I/O Sizes for the ABC has been set to the following values:
IO Size In= 256 bytes (0x0100)
IO Size Out= 400 bytes (0x0200)
The following modules are specified in the IO Controller:
Slot Module Size Direction Notes
0 0 - (Device Access Point, DAP)
1 16 bytes Input -
2 16 bytes Input/Output -
3 128 bytes Input -
4 64 bytes Input/Output -
5 32 bytes Input -
6 64 bytes Output -
7 128 bytes Output -
Resulting memory layout:
Note the “unused” part of the output data area.The reason for this is that only 272 bytes
(128+64+64+16) are actually used in the I/O module configuration, although IO Size Out is set
to 400 bytes.
Doc: HMSI-27-309, Rev. 3.11Anybus Communicator PROFINET User Manual
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 pro-
vides 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. For detailed information re-
garding the Modbus-TCP protocol, consult the Open Modbus Specification.
2.5.2 Data Representation (Modbus-TCP Register Map)
The following function codes are implemented:
Modbus Function Function Code Associated with No. of I/O:s or data points per command
Read Input Registers 4 Input Data area
(0x000....0x1FF)
Read Multiple Registers 3 Output Data area
(0x200...0x3FF)
1 - 125 registers
1 - 125 registers
The Input & Output Data areas are mapped to Modbus registers as follows:.
Register Type Register # Memory Location Area Comments
Input Registers
(3xxxx)
Output Registers
(4xxxx)
0x0000 0x000...0x001 Input Data area (Status Register)
0x0001 0x002...0x003 -
0x0002 0x004...0x005 -
0x0003 0x006...0x007 -
... ... -
0x00FF 0x1FE...0x1FF -
0x0000 0x200...0x201 Output Data area (Control Register)
0x0001 0x202...0x203 -
0x0002 0x204...0x205 -
0x0003 0x206...0x207 -
... ... -
0x00FF 0x3FE...0x3FF -
Note: If enabled, the control and status registers occupies input register 0x0000 and output register
0x0000.
2.5.3 Supported Exception codes
Code Name Description
0x01 Illegal function The function code in the query is not supported
0x02 Illegal data address The data address received in the query is outside the initialized memory area
0x03 Illegal data value The data in the request is illegal
Doc: HMSI-27-309, Rev. 3.11Anybus Communicator PROFINET User Manual
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. 1 Mb)
This area is intended for temporary storage; data placed here will be lost in case of power loss or
reset.
Chapter 3
Important Note:
The non-volatile storage is located in FLASH memory. Each FLASH segment can only be erased ap-
proximately 100000 times due to the nature of this type of memory.
The following operations will erase one or more FLASH segments:
• Deleting, moving or renaming a file or directory
• Writing or appending data to an existing file
• Formatting the file system
Conventions
• \ (backslash) is used as a path separator
• File paths originate from the system root, and as such must begin with \
• File paths must not end with \
• Names may contain spaces but must not begin or end with one
• Names must not contain one of the following characters: \ / : * ? “ < > |
• Names cannot be longer than 48 characters (plus null termination)
• File paths cannot be longer than 256 characters (filename included)
• The maximum number of simultaneously open files is 40
• The maximum number of simultaneously open directories is 40
Doc: HMSI-27-309, Rev. 3.11Anybus Communicator PROFINET User Manual
3.2 File System Overview
user
pswd
email
pswd
email
sys_pswd.cfg
ad_pswd.cfg
ethcfg.cfg
pniocfg.cfg
email_1.cfg
email_10.cfg
.
.
.
.
.
.
email_1.cfg
email_10.cfg
RAM
http.cfg
ssi_str.cfg
(admin root)
(user root)
(volatile, optional)
(protected)
(protected)
ip_accs.cfg
File System 25
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. Note that some of these files
may also be altered by the Anybus Communicator itself, e.g. when using SSI (see “Server Side Include
(SSI)” on page 35).
The format of the system files are based on the concept of “keys”, where each “key” can be assigned a
value, see example below.
Example:
The exact format of each system file is described later in this document.
The contents of the above files can be redirected:
[Key1]
value of key1
[Key2]
value of key2
Example:
In this example, the contents will be loaded from the file “here.cfg”.
[File path]
\i\put\it\over\here.cfg
Note: Any directory in the file system can be protected from web access by placing the file web_accs.cfg
in the directory, see “Authorization” on page 33.
Doc: HMSI-27-309, Rev. 3.11Anybus Communicator PROFINET User Manual
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 Man-
ager, see “Fieldbus Settings” on page 54.
• TCP/IP Settings: Enabled
When operating in this mode, the contents of the system file “ethcfg.cfg” will be ignored com-
pletely, causing the following behavior:
- DNS services will not be available
- Domain and Host name cannot be set
- E-mail services will not be available
- Settings received from the network (i.e. via HICP or DCP) will be lost in the event of a power
loss or reset.
• TCP/IP Settings: Disabled
When operating in this mode, the Anybus Communicator module will use the settings stored in
the system file “ethcfg.cfg”. If this file is missing, the module will attempt to retrieve its settings
via DHCP or HICP for 30 seconds. If no configuration has been received within this period, the
module will halt and indicate an error on its status LEDs.
Chapter 4
DCP (Discovery and Basic Configuration)
The Anybus Communicator fully supports the DCP protocol, which allows an IO Controller/Supervi-
sor to change the TCP/ IP settings during runtime.
DHCP/BootP
The Anybus Communicator can retrieve the TCP/IP settings from a DHCP or BootP server. If no
DHCP server is found, the module will fall back on its current settings (i.e. the settings currently stored
in “\ethcfg.cfg”).
If no current settings are available (i.e. “ethcfg.cfg” is missing, or contains invalid settings), the module
will halt and indicate an error on the onboard status LEDs. The network configuration may however
still be accessed via HICP, see “Anybus IPconfig (HICP)” on page 29.
Doc: HMSI-27-309, Rev. 3.11Anybus Communicator PROFINET User Manual
Basic Network Configuration 27
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
[SMTP address]
xxx.xxx.xxx.xxx
[SMTP username]
username
[SMTP password]
password
[DNS1 address]
xxx.xxx.xxx.xxx
[DNS2 address]
xxx.xxx.xxx.xxx
[Domain name]
domain
[Host name]
anybus
[HICP password]
password
• IP address
• Subnet mask
• Gateway address
• DHCP/BootP
ON - Enabled
OFF - Disabled
• SMTP server/login settings
Username and Password is only necessary if required by the
server.
• Primary and Secondary DNS
Needed to be able to resolve host names
• Default domain name for not fully qualified host names
•Host name
•HICP password
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 configura-
tion. These settings are stored in the system file “\ethcfg.cfg”.
The settings in this file may also be affected by...
See also...
• DCP (See “DCP (Discovery and Basic Configuration)” on page 26).
• HICP (See “Anybus IPconfig (HICP)” on page 29)
• SSI (See “Server Side Include (SSI)” on page 35)
• DHCP/BootP (See “DHCP/BootP” on page 26)
• Mailbox Commands (See “Mailbox Editor” on page 97)
• “FTP Server” on page 30
• “Fieldbus Settings” on page 54
Doc: HMSI-27-309, Rev. 3.11Anybus Communicator PROFINET User Manual
Basic Network Configuration 28
Example:
[Station Name]
Nice Device
[Station Type]
ABS-PRT
[Vendor ID]
0x010C
[Device ID]
0x0001
• Station Name
Station name as ASCII string, maximum 64 characters.
• Station Type
Station type as ASCII string, maximum 64 characters.
• Vendor ID
16 bit hexadecimal value, with the prefix 0x. Assigned
by the PNO.
• Device ID
16 bit hexadecimal value, with the prefix 0x. Assigned
by vendor.
File Format:
[Web]
xxx.xxx.xxx.xxx
[FTP]
xxx.xxx.xxx.xxx
[Modbus-TCP]
xxx.xxx.xxx.xxx
[All]
xxx.xxx.xxx.xxx
• Nodes listed here may access the web server
• Nodes listed here may access the FTP server
• Nodes listed here may access the module via Modbus-TCP
• Fallback setting, used by the module when one or several of the
keys above are omitted
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).
4.4 IP Access Control
It is possible to specify which IP addresses that are permitted to connect to the Anybus Communicator.
This information is stored in the system file “\ip_accs.cfg”.
Note: * (asterisk) may be used as a wildcard to select IP series.
Doc: HMSI-27-309, Rev. 3.11Anybus Communicator PROFINET User Manual
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 con-
figure 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. The net-
work can be rescanned at any time by
clicking “Scan”. In the list of detected de-
vices, the Anybus Communicator will ap-
pear as “ABC-PRT”. To alter its network
settings, double-click on its entry in the
list.
A window will appear, containing the IP
configuration and password settings.
Validate the new settings by clicking
“Set”, or click “Cancel” to abort.
Optionally, the configuration may be protected from unauthorized access by a password. To enter a
password, click on the “Change password” checkbox, and enter the password under “New password”.
When protected, any changes in the configuration requires that the user supplies a valid password.
When done, click “Set”. The new IP configuration will now be stored in the configuration file (“eth-
cfg.cfg”).
Note that if “TCP/IP Settings” has been enabled in the Anybus Configuration Manager, any settings
received via HICP will be lost in the event of a power loss or reset.
Doc: HMSI-27-309, Rev. 3.11Anybus Communicator PROFINET User Manual
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.
Chapter 5
User Accounts
The user accounts are stored in two files, which are protected from web access:
• “\user\pswd\sys_pswd.cfg”
This file holds the user accounts for normal-level users.
• “\pswd\ad_pswd.cfg”
This file holds the user accounts for admin-level users.
File Format:
The format of these files are as follows:
Username1:Password1
Username2:Password2
Username3:Password3
Note: If no valid user accounts have been defined, the Anybus Communicator will grant admin-level
access to all users. In such case, the FTP accepts any username/password combination, and the root
directory will be “\”.
Doc: HMSI-27-309, Rev. 3.11Anybus Communicator PROFINET User Manual
Loading...