HMS Anybus Communicator CAN PROFINET IRT 2.32 User Manual
AAnnyybbuuss®®CCoommmmuunniiccaattoorr™™CCAANN
PPRROOFFIINNEETT®®IIRRTT ((22..3322))
USER MANUAL
SCM-1202-035 1.2 en-US ENGLISH
Important User Information
Disclaimer
The information in this document is for informational purposes only. Please inform HMS Industrial Networks of any
inaccuracies or omissions found in this document. HMS Industrial Networks disclaims any responsibility or liability
for any errors that may appear in this document.
HMS Industrial Networks reserves the right to modify its products in line with its policy of continuous product
development. The information in this document shall therefore not be construed as a commitment on the part of
HMS Industrial Networks and is subject to change without notice. HMS Industrial Networks makes no commitment
to update or keep current the information in this document.
The data, examples and illustrations found in this document are included for illustrative purposes and are only
intended to help improve understanding of the functionality and handling of the product. In view of the wide range
of possible applications of the product, and because of the many variables and requirements associated with any
particular implementation, HMS Industrial Networks cannot assume responsibility or liability for actual use based on
the data, examples or illustrations included in this document nor for any damages incurred during installation of the
product. Those responsible for the use of the product must acquire sufficient knowledge in order to ensure that the
product is used correctly in their specific application and that the application meets all performance and safety
requirements including any applicable laws, regulations, codes and standards. Further, HMS Industrial Networks will
under no circumstances assume liability or responsibility for any problems that may arise as a result from the use of
undocumented features or functional side effects found outside the documented scope of the 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.
®
Anybus
are the property of their respective holders.
is a registered trademark of HMS Industrial Networks AB. All other trademarks mentioned in this document
Anybus®Communicator™CAN PROFINET®IRT (2.32) User Manual
SCM-1202-035 1.2 en-US
Table of Contents
Page
1 Preface ................................................................................................................................. 3
1.1 About This Document .................. .. ................................. ................................. .. ............... 3
1.2 Document history ....................... ..................................................................................... 3
1.3 Document Conventions ............................... .. ....................................................................4
2 Description .......................................................................................................................... 5
2.1 Introduction................ ................................. .. ................................. ................................ 5
2.2 Data Exchange Model ................................................................................. ......................6
2.3 PROFINET IRT Protocol ........................... ................................. .. ................................. ....... 7
2.4 CAN Network Protocol ...... ................................................................................................8
3 Installation......................................................................................................................... 13
3.1 Installation Overview ............... ................................. ...................................................... 13
3.2 Connectors and Indicators ....................... .. ................................. ................................. .. .. 14
3.3 DIN Rail Mounting.. .. ................................. ................................. .. ................................. . 14
3.4 CAN Interface.... .. .......................................................................................................... 16
3.5 PROFINET Interface ........... .. ........................................................................................... 16
3.6 Power Connector ............................... .. ............................... .. ................................. .. ...... 16
3.7 USB Connector ............ ................................. ................................................................. 16
3.8 LED Indicators ....................... ................................. ................................. .. .................... 17
4 Configuration..................................................................................................................... 18
4.1 Configuration Overview.. .. ................................. ................................. .. ........................... 18
4.2 Network Configuration............. ................................. .. ................................. ................... 19
4.3 Web Pages.................................... ................................. .. ................................. ............ 23
5 Anybus Configuration Manager ....................................................................................... 24
5.1 Main Window......................... ................................. .. ................................. ................... 24
5.2 Basic Settings ....................................................................... ................................. .. ...... 25
6 PROFINET Asset Management.......................................................................................... 27
6.1 Asset Management Record ........ .. ................................. .. ............................... .. ................ 27
6.2 Recording and Reading Data .. .......................................................................................... 27
6.3 Supported File Formats ...... .. ................................. .. ................................. ....................... 28
6.4 Supported Asset Management Records.............................. ................................. .. ............. 28
6.5 XML Based Asset Management. ................................. ................................. .. .................... 29
6.6 Binary Based Asset Management .. ................................. .. ............................... .. ................ 32
6.7 Uploading the Asset Management File to the FTP Server.............................................. ......... 36
Anybus®Communicator™CAN PROFINET®IRT (2.32) User Manual
SCM-1202-035 1.2 en-US
A Technical Data ................................................................................................................... 39
A.1 General Specifications............... .. ................................. .. ............................... .. ................ 39
A.2 CAN Interface.... .. .......................................................................................................... 39
A.3 PROFINET IRT Interface ............................................................................................. ...... 39
B Licenses .............................................................................................................................. 40
Anybus®Communicator™CAN PROFINET®IRT (2.32) User Manual
SCM-1202-035 1.2 en-US
Preface 3 (42)
1 Preface
1.1 About This Document
This document describes how to install and configure the Anybus Communicator CAN PROFINET
IRT (2.32) gateway.
For additional related documentation and file downloads, please visit www.anybus.com/support.
1.2 Document history
Version
1.0 2017-02-23
1.1 2017-11-22
1.2 2019-04-11
Date
Description
First release
Updated for new firmware
Added section about PROFINET Asset Management
®
Anybus
Communicator™CAN PROFINET®IRT (2.32) User Manual
SCM-1202-035 1.2 en-US
Preface 4 (42)
1.3 Document Conventions
Ordered lists are used for instructions that must be carried out in sequence:
1. First do this
2. Then do this
Unordered (bulleted) lists are used for:
• Itemized information
• Instructions that can be carried out in any order
...and for action-result type instructions:
► This action...
→ leads to this result
Bold typeface indicates interactive parts such as connectors and switches on the hardware, or
menus and buttons in a graphical user interface.
Monospaced text is used to indicate program code and other
kinds of data input/output such as configuration scripts.
This is a cross-reference within this document: Document Conventions, p. 4
This is an external link (URL): www.hms-networks.com
This is additional information which may facilitate installation and/or operation.
This instruction must be followed to avoid a risk of reduced functionality and/or damage
to the equipment, or to avoid a network security risk.
Caution
This instruction must be followed to avoid a risk of personal injury.
WARNING
This instruction must be followed to avoid a risk of death or serious injury.
Anybus®Communicator™CAN PROFINET®IRT (2.32) User Manual
SCM-1202-035 1.2 en-US
Description
2 Description
2.1 Introduction
Anybus Communicator CAN PROFINET IRT (2.32) is designed to exchange data between a CAN
subnetwork and a higher level network. The CAN protocol uses individually configurable frames,
offering great flexibility. Through the configuration of CAN frames, the Anybus Communicator
CAN will adapt to a predefined CAN subnetwork. It will be possible to send data to and receive
data from the CAN subnetwork, but also to act as a relay for data on the subnetwork.
The gateway can issue frames cyclically, on change of data, or based on trigger events issued by
the control system of the higher level network. It can also monitor communication on the
subnetwork and notify the higher level network when data has changed.
Anybus Communicator gateways are configured using Anybus Configuration Manager, a family of
configuration tools that have an easy to use graphical interface and that do not require
programming skills.
Anybus Configuration Manager and additional related software and documentation are available
at www.anybus.com/support.
5 (42)
Fig. 1 Anybus Configuration Manager
®
Anybus
Communicator™CAN PROFINET®IRT (2.32) User Manual
SCM-1202-035 1.2 en-US
Description
Internal Memory
Input Data
(220 bytes)
CAN Subnetwork
Output Data
(220 bytes)
General Data
Higher Level Network
CAN Network:
Fieldbus:
CAN Network:
Fieldbus:
CAN Network:
Fieldbus:
Write Only
Read Only
Read Only
Write Only
Read/Write
-
Input Data Output Data General Data
0x000 0x200
0x0DB 0x2DB
0x400
0x7FF
2.2 Data Exchange Model
2.2.1 Overview
The data exchanged on the CAN subnetwork and the data exchanged on the higher level
network reside in the same internal memory in the Anybus Communicator CAN. In order to
exchange data with the CAN subnetwork, the higher level network simply reads and writes data
to memory locations that have been specified in Anybus Configuration Manager. The same
memory locations can then be exchanged on the CAN subnetwork.
6 (42)
Fig. 2 Memory buffer structure
The internal memory buffer is divided into three areas based on their function:
Input Data (220 bytes) This area can be read from by the higher level network.
Output Data (220 bytes) This area can be written to by the higher level network.
General Data
(up to 1024 bytes)
2.2.2 Memory Map
When building the CAN subnetwork configuration in Anybus Configuration Manager the areas in
the memory buffer will be mapped to the following memory locations:
This area cannot be accessed by the higher level network but can be used for
transfers between individual nodes on the subnetwork, or as a general “scratch
pad” for data.
The size of the General Data area is 1024 bytes. How much of that area that will
be used for communication depends on the configuration.
Fig. 3 Memory Map
Anybus®Communicator™CAN PROFINET®IRT (2.32) User Manual
The illustration shows the maximum available data areas in Anybus Communicator CAN. The actual
amount of memory that can be allocated depends on the fieldbus network used.
SCM-1202-035 1.2 en-US
Description
2.3 PROFINET IRT Protocol
PROFINET is the open Industrial Ethernet standard for automation from PROFIBUS and PROFINET
International. The PROFINET IRT device provides PROFINET IO Isochronous Real Time
Communication.
PROFINET makes a clear distinction between fast cyclical data, IO Data, and acyclical data,
Record Data. PROFINET IO Data corresponds to what is generally referred to as I/O Data in
Anybus Communicator CAN PROFINET IRT (2.32). PROFINET Record Data is not supported.
Anybus Communicator CAN PROFINET IRT (2.32) acts as a PROFINET device (slave), which means
it can be accessed by a PROFINET controller (master), but will not initiate communication by
itself.
PROFINET IO Data (I/O Data)
PROFINET IO Data is exchanged cyclically and is built up by I/O modules. The actual I/O
configuration is determined by the PROFINET IO Controller. The modules are mapped to the
Input and Output Buffers in the order of their slot number.
The first two bytes of the I/O data area are reserved for the Control Word and the Status Word,
which are used by the IO Controller to control and report status on the nodes on the CAN
subnetwork. The remainder is available for real-time data transfer using PDOs.
7 (42)
GSD File
All PROFINET devices are associated with an XML-based GSD file. This file contains information
about the basic capabilities and configuration options of the device.
The latest version of the GSD file for Anybus Communicator CAN PROFINET IRT (2.32) can be
downloaded from www.anybus.com/support.
Anybus®Communicator™CAN PROFINET®IRT (2.32) User Manual
SCM-1202-035 1.2 en-US
Description
2.4 CAN Network Protocol
2.4.1 General
The CAN protocol is message-based and can exchange up to 8 bytes of data in each message.
The protocol only acts as a data carrier, it is up to each application to define and interpret the
data content of the messages.
Data is exchanged using frames. Each frame has a unique identifier for the data it exchanges,
which also represents the message priority. Anybus Communicator CAN supports both 11-bit
(CAN 2.0A) and 29-bit (CAN 2.0B) identifiers, selected in the configuration.
CAN is essentially a produce-consume protocol, where all nodes listen to all messages. The
devices recognize what data to collect by the identifier in the CAN frame. Anybus Communicator
CAN is also able to act as a network master and issue queries that demand responses. Both
methods can be used within the same configuration.
2.4.2 Message Types
Anybus Communicator CAN features three CAN message types: Query-Response, Produce, and
Consume. These message types only specify the basic communication model, not the actual CAN
protocol. All three message types can be used in the same configuration.
8 (42)
Query-Response
The Anybus Communicator CAN here acts as a master on the CAN subnetwork, and
communication takes place in a query-response fashion. The gateway sends a query and expects
a response within a specified timeout.
Fig. 4 Query-Response messaging
Produce and Consume
Here there is no master-slave relationship between the Anybus Communicator CAN and the
subnetwork nodes. Any node, including the gateway, may both produce and consume messages.
Nodes do not have to respond to messages, or wait for a query in order to send one. The
consumed data can be accessed from the higher level network, and vice versa.
Anybus®Communicator™CAN PROFINET®IRT (2.32) User Manual
SCM-1202-035 1.2 en-US
Description
9 (42)
Fig. 5 Produce and Consume messages
®
Anybus
Communicator™CAN PROFINET®IRT (2.32) User Manual
SCM-1202-035 1.2 en-US
Description
2.4.3 Protocol Building Blocks
The following building blocks are used in Anybus Configuration Manager to describe the
subnetwork communication.
10 (42)
Group
Transaction
Dynamic Transaction
CAN Frames
A group does not represent any specific device on the CAN subnetwork, it is only a
means to structure the transactions that have been defined for the gateway in Anybus
Configuration Manager.
Each group can be associated with any number of transactions, however the total
number of transactions in a configuration is limited to 128.
A transaction consists of one or more CAN frames. Each transaction is associated with a
set of parameters controlling how and when to use it on the subnetwork. There are 5
transaction types: produce, consume, query-response, dynamic produce and dynamic
consume. A group can contain transactions of all three types simultaneously.
A total of 128 transactions can be configured.
A dynamic transaction makes it possible for a network master to change selected
parameters during runtime. The parameters are mapped to the Output or General Data
areas and cannot be changed using Anybus Configuration Manager.
A dynamic transaction can only consist of a single CAN frame which in turn can only hold
one data object.
Only one dynamic produce transaction and one dynamic consume transaction can be
configured.
CAN frames are low level entities used to compose transactions. Each frame carries an
11-bit or 29-bit identifier and can hold up to 8 bytes of data.
A total of 256 CAN frames can be configured.
®
Anybus
Communicator™CAN PROFINET®IRT (2.32) User Manual
SCM-1202-035 1.2 en-US
Description
2.4.4 Control and Status Words
The optional Control and Status Words can be used to control the startup mode of the Anybus
Communicator CAN and to read the status of the CAN subnetwork. The Control Word is always
mapped to the first two bytes of the output data area, and the Status Word to the first two bytes
of the input data area, with the Least Significant Byte in the first byte (byte 0).
Fig. 6 Memory buffers
The illustration shows the maximum available data areas in Anybus Communicator CAN. The actual
amount of memory that can be allocated depends on the fieldbus network used.
Control Word
The Control Word can be used to reset the CAN controller and to select the startup mode and/or
reboot the Anybus Communicator CAN.
11 (42)
Bit Name
15 - 3
2 Reset CAN
1
0
(reserved)
Reboot module 1 - Reboots the Anybus Communicator CAN (software reset)
Operation mode Sets the start-up operation mode of the Anybus Communicator CAN:
Description
1 - Resets the CAN controller (used when CAN interface is bus off)
0 - Idle (no new data is issued to the CAN subnetwork. Data received from the CAN
subnetwork is sent on to the higher level network.)
1 - Run (data is exchanged between CAN subnetwork and higher level network.)
Status Word
The Status Word holds information from the CAN subnetwork.
Bit Name
15 - 6
5 CAN overrun 0 - OK
4 Error passive
3
2 Reset CAN
1
0
(reserved)
Bus off
complete
(reserved)
Operation mode 0 - Idle
Description
1 - CAN reception overrun
0 - CAN interface is NOT in error passive state
1 - CAN interface is in error passive state
0 - Bus runnning
1 - Bus off
If set, the CAN controller has been reset (used when CAN interface is bus off)
1 - Run
®
Anybus
Communicator™CAN PROFINET®IRT (2.32) User Manual
SCM-1202-035 1.2 en-US
Description
2.4.5 Transaction Live List
The optional Transaction Live List consists of a bit array where each bit corresponds to a
transaction on the CAN subnetwork (bit 0 corresponds to transaction 1 etc.). A set bit indicates
normal functionality. The bit is not set if the transaction is non-working or non-existent.
The live list is mapped in the Input data area of the memory, either at the start of the area or
directly after the Status word. From 8 transactions up to 128 transactions in steps of 8 can be
monitored using the live list. This means that up to 16 bytes of the input data area of the
memory can be occupied by the live list.
The latest live list can always be accessed in Anybus Configuration Manager, regardless of
whether the live list is mapped in the input data area or not.
12 (42)
Anybus®Communicator™CAN PROFINET®IRT (2.32) User Manual
SCM-1202-035 1.2 en-US
Loading...