105 4635 hms hmsi 27 305

105 4635 hms hmsi 27 305
User Manual
Anybus® Communicator™
for DeviceNet™
Doc. Id. HMSI-27-305
Rev. 3.12
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: [email protected]
Web: www.anybus.com
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 commitment 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 including 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 described 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. DeviceNet™ and ODVA™ are trademarks of ODVA, 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
which case the user may be required to take adequate measures.
ESD Note: This product contains ESD (Electrostatic Discharge) sensitive parts that may be damaged if ESD
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 DeviceNet User Manual
Copyright© HMS Industrial Networks AB
Doc: HMSI-27-305
Anybus Communicator DeviceNet User Manual
Doc: HMSI-27-305, Rev. 3.12
Table of Contents
Table of Contents
Preface
About This Document
Related Documents..................................................................................................................... 7
Document History ...................................................................................................................... 7
Conventions & Terminology ..................................................................................................... 8
Glossary.............................................................................................................................. 8
Support.......................................................................................................................................... 8
Chapter 1
About the Anybus Communicator for DeviceNet
External View............................................................................................................................. 10
Status LEDs ............................................................................................................................... 11
Configuration Switches............................................................................................................. 11
Hardware Installation................................................................................................................ 12
Software Installation ................................................................................................................. 13
Anybus Configuration Manager ........................................................................................ 13
Electronic Datasheet (EDS-file)........................................................................................ 13
Chapter 2
Basic Operation
General........................................................................................................................................ 14
Data Exchange Model .............................................................................................................. 15
Memory Map.................................................................................................................... 15
Data Exchange Example ................................................................................................. 16
Subnetwork Protocol ................................................................................................................ 17
Protocol Modes.................................................................................................................. 17
Protocol Building Blocks.................................................................................................... 17
Master Mode..................................................................................................................... 18
Generic Data Mode .......................................................................................................... 19
DF1 Master Mode ........................................................................................................... 19
Data Representation on DeviceNet........................................................................................ 20
General............................................................................................................................. 20
Data Types ....................................................................................................................... 20
Memory Layout ................................................................................................................ 21
Chapter 3
Navigating ACM
Main Window............................................................................................................................. 22
Drop-down Menus ............................................................................................................ 23
Toolbar Icons .................................................................................................................... 26
Anybus Communicator DeviceNet User Manual
Doc: HMSI-27-305, Rev. 3.12
3
Chapter 4
Basic Settings
Fieldbus Settings........................................................................................................................ 27
Communicator Parameters ...................................................................................................... 28
Sub-network Parameters .......................................................................................................... 29
Chapter 5
Nodes
General........................................................................................................................................ 30
Adding & Managing Nodes ..................................................................................................... 30
Node Parameters ....................................................................................................................... 30
Master Mode and Generic Data Mode.............................................................................. 30
Chapter 6
Transactions
General........................................................................................................................................ 31
Adding & Managing Transactions .......................................................................................... 32
Transaction Parameters (Master Mode)................................................................................. 33
Parameters (Query & Broadcast)...................................................................................... 33
Parameters (Response)....................................................................................................... 34
Transaction Parameters (Generic Data Mode) ..................................................................... 35
Produce Transactions......................................................................................................... 35
Consume Transactions ...................................................................................................... 36
Transaction Editor .................................................................................................................... 37
Chapter 7
Frame Objects
General........................................................................................................................................ 38
Adding and Editing Frame Objects ....................................................................................... 38
Constant Objects (Byte, Word, Dword)................................................................................ 39
Limit Objects (Byte, Word, Dword) ...................................................................................... 40
Data Object ................................................................................................................................ 41
Variable Data Object ................................................................................................................ 41
Checksum Object ...................................................................................................................... 43
Chapter 8
Commands
General........................................................................................................................................ 44
Adding & Managing Commands ............................................................................................ 44
Drop-down Menu ............................................................................................................ 45
Toolbar Icons .................................................................................................................... 45
The Command Editor .............................................................................................................. 46
General............................................................................................................................. 46
Basic Navigation............................................................................................................... 46
Drop-down Menu ............................................................................................................ 47
Editing a Command ......................................................................................................... 47
Example: Specifying a Modbus-RTU Command in Master Mode .................................... 48
Anybus Communicator DeviceNet User Manual
Doc: HMSI-27-305, Rev. 3.12
4
Chapter 9
DF1 Protocol Mode
General........................................................................................................................................ 49
Communicator Parameters ...................................................................................................... 50
Sub-network Parameters .......................................................................................................... 51
Node Parameters ....................................................................................................................... 52
Services........................................................................................................................................ 52
Available Services ............................................................................................................. 53
Integrity Check .......................................................................................................................... 54
Read Diagnostics ....................................................................................................................... 54
Read Data ................................................................................................................................... 55
Write Data .................................................................................................................................. 55
Chapter 10
Sub-network Monitor
General........................................................................................................................................ 56
Operation.................................................................................................................................... 56
Chapter 11
Node Monitor
General........................................................................................................................................ 57
Navigating the Node Monitor................................................................................................. 58
Drop-down Menu ............................................................................................................ 59
Toolbar Icons .................................................................................................................... 60
Chapter 12
Data Logger
General........................................................................................................................................ 61
Operation.................................................................................................................................... 61
Configuration ............................................................................................................................. 62
Chapter 13
Configuration Wizards
General........................................................................................................................................ 63
Selecting a Wizard Profile ........................................................................................................ 63
Wizard - Modbus RTU Master ............................................................................................... 64
Chapter 14
Control and Status Registers
General........................................................................................................................................ 65
Handshaking Procedure .................................................................................................... 65
Data Consistency .............................................................................................................. 66
Status Register Contents (Gateway to Control System)...................................................... 67
General Information.......................................................................................................... 67
Status Codes in Master Mode and DF1 Master Mode...................................................... 67
Status Code in Generic Data Mode................................................................................... 68
Control Register Contents (Control System to Gateway)................................................... 69
General Information.......................................................................................................... 69
Control Codes in Master Mode and DF1 Master Mode.................................................... 69
Control Codes in Generic Data Mode ............................................................................... 69
Anybus Communicator DeviceNet User Manual
Doc: HMSI-27-305, Rev. 3.12
5
Chapter 15
CIP Object Implementation
Identity Object, Class 01h........................................................................................................ 71
General Information.......................................................................................................... 71
Class Attributes................................................................................................................ 71
Instance Attributes............................................................................................................ 71
Message Router, Class 02h....................................................................................................... 72
General Information.......................................................................................................... 72
Class Attributes................................................................................................................ 72
Instance Attributes............................................................................................................ 72
DeviceNet Object, Class 03h .................................................................................................. 73
General Information.......................................................................................................... 73
Class Attributes................................................................................................................ 73
Instance Attributes............................................................................................................ 73
Assembly Object, Class 04h .................................................................................................... 74
General Information.......................................................................................................... 74
Class Attributes................................................................................................................ 74
Instance Attributes - Instance/Connection Point 64h ........................................................ 74
Instance Attributes - Instance/Connection Point 96h ........................................................ 74
Connection Object, Class 05h................................................................................................. 75
General Information.......................................................................................................... 75
Class Attributes................................................................................................................ 75
Instance 1 & 10...14 (Explicit Messaging Connection) Attributes ................................... 75
Instance 2 (Polled Connection) Attributes.......................................................................... 75
Instance 3 (Bit-strobe connection) Attributes...................................................................... 76
Instance 4 (COS/Cyclic connection) Attributes ................................................................. 76
Acknowledge Handler Object, Class 2Bh ............................................................................. 77
General Information.......................................................................................................... 77
Class Attributes................................................................................................................ 77
Instance Attributes............................................................................................................ 77
Diagnostic Object, Class AAh................................................................................................. 78
General Information.......................................................................................................... 78
Class Attributes................................................................................................................ 78
Instance Attributes, Instance 01h...................................................................................... 78
Parameter Data Input Mapping Object, Class B0h ............................................................. 79
General Information.......................................................................................................... 79
Class Attributes................................................................................................................ 79
Instance Attributes, Instance 01h...................................................................................... 79
Parameter Data Output Mapping Object, Class B1h .......................................................... 80
General Information.......................................................................................................... 80
Class Attributes................................................................................................................ 80
Instance Attributes, Instance 01h...................................................................................... 80
Chapter 16
Advanced Fieldbus Configuration
General........................................................................................................................................ 81
Mailbox Editor........................................................................................................................... 81
Anybus Communicator DeviceNet User Manual
Doc: HMSI-27-305, Rev. 3.12
6
Appendix A
Parameter Data Initialization (Explicit Data)
General........................................................................................................................................ 82
Add a Mailbox Message............................................................................................................ 82
Mapping Input Parameter Data to DeviceNet ..................................................................... 83
Mapping Output Parameter Data to DeviceNet .................................................................. 85
Appendix B
Connector Pin Assignments
DeviceNet Connector............................................................................................................... 87
Power Connector ...................................................................................................................... 87
PC Connector ............................................................................................................................ 88
Subnetwork Interface ............................................................................................................... 89
General Information.......................................................................................................... 89
Bias Resistors (RS485 Only)............................................................................................ 89
Termination (RS485 & RS422 Only) ............................................................................ 89
Connector Pinout (DB9F) ................................................................................................ 89
Typical Connection (RS485)............................................................................................. 90
Typical Connection (RS422 & 4-Wire RS485) .............................................................. 90
Typical Connection (RS232)............................................................................................. 90
Appendix C
Technical Specification
Mechanical Properties............................................................................................................... 91
Electrical Characteristics .......................................................................................................... 91
Environmental Characteristics ................................................................................................ 91
Regulatory Compliance ............................................................................................................ 92
Appendix D
Troubleshooting
Appendix E
ASCII Table
Anybus Communicator DeviceNet User Manual
Doc: HMSI-27-305, Rev. 3.12
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 - DeviceNet 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.00... 3.10)
Change
Device type changed from “Group two only server” to “Group two server”
Screenshots and descriptions of ABC Tool updated for Anybus Configuration Manager
Changed “ABC” to “Communicator RS232/422/485”
Amended description of “Update time” parameter
Added description for Consume/Response to “Object Delimiter” parameter
Changed “Maximum Data Length” limit
Removed obsolete “Start Bits” parameter
Removed obsolete “ABCC ExtLink Wizard” entry
Replaced “Sales and Support” info with link to website
Added parameters to checksum object description
Minor text edits, typo corrections
Page(s)
9
Multiple
Multiple
34, 35
42
42
51
64
8
43
Multiple
Summary of Recent Changes (3.10... 3.12)
Revision
3.11
3.12
Change
Added trademark symbol
Added compliance/conformance info
Page(s)
Front cover
92
Revision List
Revision
2.00
2.01
2.50
2.51
2.52
3.00
3.01
3.10
3.11
3.12
Date
2003-12-03
2004-03-08
2006-04-05
2006-12-22
2009-04-23
2011-02-09
2011-09-30
2015-02-20
2015-03-13
2015-03-20
Author
PeP
PeP
PeP
PeP
KeL
KaD
KaD
ThN
ThN
ThN
Anybus Communicator DeviceNet User Manual
Chapter
All
16
All
All
All
All
All
Cover
C
Description
Second major release
Corrected Control Codes
Major update
Misc. minor corrections & updates
Misc. minor corrections and updates
Misc. corrections, new template and DF1 functionality
Misc corrections and updates, new Anybus Configuration Manager
Misc. corrections and updates, new Doc ID
Added trademark synbol
Added compliance/conformance info
Doc: HMSI-27-305, Rev. 3.12
About This Document 8
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.
•
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 document is that “input” and “output” are always being referenced to the master/scanner end of the
link.
P.3.1 Glossary
Term
ABC
ACM
Broadcaster
DEV
Command
Configuration
Fieldbus
Fieldbus Control System
Frame Object
Monitor
Node
Sub-network
Transaction
User
Higher Level Network
Network
Fieldbus
Meaning
Anybus Communicator
Anybus Configuration Manager
A protocol-specific node in the configuration that handles transactions destined to all nodes.
DeviceNet
A predefined transaction
List of configured nodes with transactions on the subnetwork
The higher level network to which the communicator is connected
Fieldbus master
Low level entities which are used to describe the different parts of a transaction
A tool for debugging the Anybus Communicator and the network connections
A device in the configuration which defines the communication with a node on the subnetwork
The network that is logically located on a subsidiary level with respect to the fieldbus, and to
which the Anybus Communicator acts as a gateway
A generic building block that is used in the subnetwork configuration and defines the data that
is sent and received on the subnetwork
Person or persons responsible for installing the Anybus Communicator
In this case, DeviceNet
P.4 Support
For general contact information and support, please refer to the contact and support pages at
www.anybus.com
Anybus Communicator DeviceNet User Manual
Doc: HMSI-27-305, Rev. 3.12
Chapter 1
1. About the Anybus Communicator for DeviceNet
The Anybus Communicator for DeviceNet acts as a gateway between virtually any serial application protocol and a DeviceNet-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.
ControlNet Master
(e.g a PLC)
(ControlNet Network)
(ControlNet Network)
ControlNet Master
(e.g a PLC)
HMI
INVERTER
PC configuration
and monitoring
HMI
INVERTER
PC configuration
and monitoring
Multi-drop up to 31 nodes
Serial communication
device
Serial communication devices
Single-Node Serial Sub Network
Multi-Node Serial Sub Network
Subnetwork
The Anybus Communicator can address up to 31 nodes, and supports the following physical standards:
•
RS-232
•
RS-422
•
RS-485
DeviceNet Interface
DeviceNet connectivity is provided through the patented Anybus technology; a proven industrial communication solution used all over the world by leading manufacturers of industrial automation products.
•
•
•
•
Communications Adapter, profile no. 12
Group two server
MacID and baudrate configuration via on-board switches
Polled, Change-of-state and Bit strobed I/O
Anybus Communicator DeviceNet User Manual
Doc: HMSI-27-305, Rev. 3.12
About the Anybus Communicator for DeviceNet 10
1.1 External View
For wiring and pin assignments, see Appendix “Connector Pin Assignments” on page 87.
A: DeviceNet Connector
This connector is used to connect the Anybus Communicator to the fieldbus network.
C
See also...
B
- “DeviceNet Connector” on page 87
A
B: Configuration Switches
See also...
- “Configuration Switches” on page 11
C: Status LEDs
D
See also...
- “Status LEDs” on page 11
D: PC-connector
This connector is used to connect the gateway to a PC for
configuration and monitoring purposes.
E
G
F
See also...
- “PC Connector” on page 88
E: Subnetwork Connector
This connector is used to connect the gateway to the serial subnetwork.
See also...
- “Subnetwork Interface” on page 89
F: Power Connector
This connector is used to apply power to the gateway.
See also...
- “Power Connector” on page 87
- “Connector Pin Assignments” on page 87
G: DIN-rail Connector
The DIN-rail mechanism connects the gateway to PE (Protective Earth).
See also...
- “Connector Pin Assignments” on page 87
Anybus Communicator DeviceNet User Manual
Doc: HMSI-27-305, Rev. 3.12
About the Anybus Communicator for DeviceNet 11
1.2 Status LEDs
#
1 - Network Status
2 - Module Status
3 - (Not used)
4 - (Not used)
5 - Subnet Statusa
State
Off
Green
Green, flashing
Red
Red, flashing
Off
Green
Green, flashing
Red
Red, flashing
Off
Green, flashing
Green
Red
6 - Device Status
Off
Alternating Red/Green
Green
Green, flashing
Red
Red, flashing
Status
Not powered / not online
Link OK, On line, Connected
On line, Not connected
Critical Link Failure
Connection timeout
No power to device
Device Operational
Data size bigger than configured
Unrecoverable fault
Minor Fault
Power off
Running correctly, but one or more transaction error(s) have occurred
Running
Transaction error/timeout or subnet
stopped
Power off
Invalid or missing configuration
Initializing
Running
1
2
3
4
5
6
Bootloader modeb
IIf the Device Status LED is flashing in a
sequence starting with one or more red
flashes, please note the sequence pattern
and contact the HMS support department
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 Communicator. Choose Tools/Options/Module. Click “Factory Restore” to
restore firmware. See “Tools” on page 24.
1.3 Configuration Switches
The configuration switches are used to set the DeviceNet MacID and baudrate settings.
Note that the these settings cannot be changed during runtime, i.e. the Anybus Communicator requires
a reset for any changes to have effect.
The switches are interpreted as follows:
Baudrate
125k
250K
500K
(reserved)
sw. 1
OFF
OFF
ON
ON
sw. 2
OFF
ON
OFF
ON
Anybus Communicator DeviceNet User Manual
Mac ID
0
1
...
62
63
sw. 3
OFF
OFF
...
ON
ON
sw. 4
OFF
OFF
...
ON
ON
sw. 5
OFF
OFF
...
ON
ON
sw. 6
OFF
OFF
...
ON
ON
sw. 7
OFF
OFF
...
ON
ON
sw. 8
OFF
ON
...
OFF
ON
Doc: HMSI-27-305, Rev. 3.12
About the Anybus Communicator for DeviceNet 12
1.4 Hardware Installation
Perform the following steps when physically installing the Anybus Communicator:
1. Snap the gateway on to the DIN-rail (See “External View” on page 10)
The DIN-rail mechanism works as follows:
1
To snap the gateway 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)
2
1
To snap the gateway 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
2. Connect the gateway to the DeviceNet network
3. Connect the gateway to the serial subnetwork
4. Connect the gateway to a free COM-port on the PC via the PC-cable
5. Set the DeviceNet baudrate and Mac-ID using the on-board switches
6. Connect the power cable and apply power
7. Start the Anybus Configuration Manager program on the PC
(The Anybus Configuration Manager attempts to detect the serial port automatically. If not successful, select the correct port manually in the “Port”-menu)
8. Configure the ABC using the Anybus Configuration Manager and download the configuration
Anybus Communicator DeviceNet User Manual
Doc: HMSI-27-305, Rev. 3.12
About the Anybus Communicator for DeviceNet 13
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 doubleclick on it to start the installation, then follow the on-screen instructions.
•
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.
1.5.2 Electronic Datasheet (EDS-file)
On DeviceNet, the characteristics of a device is stored in an ASCII data file with the suffix EDS. This
file is used by DeviceNet configuration tools when setting up the network.
The latest version of this file can be obtained from the HMS website www.anybus.com.
Anybus Communicator DeviceNet User Manual
Doc: HMSI-27-305, Rev. 3.12
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. 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 protocol. No programming skills are required; instead, a visual protocol description-system is used to specify
the different parts of the serial communication.
Anybus Communicator DeviceNet User Manual
Doc: HMSI-27-305, Rev. 3.12
Basic Operation 15
2.2 Data Exchange Model
Internally, the data exchanged on the subnetwork, and
the data exchanged on the higher level network, resides
in the same memory.
ABC Internal Memory
This means that in order to exchange data with the subnetwork, the higher level network simply reads and
writes data to memory locations specified using the Anybus Configuration Manager. The very same memory
locations can then be exchanged on the subnetwork.
Input Data (512 bytes)
This area can be read by the higher level network.
(how this data is represented on the higher level
network will be described later in this chapter).
•
Higher Level Network
•
Output Data
(512 bytes)
Subnetwork
The internal memory buffer is divided into three areas
based on their function:
Input Data
(512 bytes)
General Data
Output Data (512 bytes)
This area can be written to by the higher level
network.
(how this data is represented on the higher level
network will be described later in this chapter).
•
General Data
This area is not exchanged on the higher level network, and can be used for transfers between
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 gateway 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 areas described above are mapped to the memory locations (addresses) specified below.
Input Data
0x000
Output Data
0x200
Subnetwork:
Fieldbus:
Read/Write
Read Only
0x1FF
Anybus Communicator DeviceNet User Manual
Subnetwork:
Fieldbus:
0x3FF
General Data
0x400
Read Only
Read/Write
Subnetwork:
Fieldbus:
Read/Write
-
0x???
Doc: HMSI-27-305, Rev. 3.12
Basic Operation 16
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 Anybus Communicator.
PLC (DeviceNet Scanner)
PLC Memory (Inputs)
PLC Memory (Outputs)
Actual Temperature
Temperature Setpoint
DeviceNet
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.
The PLC exchange data between the internal
PLC memory and the slaves (in this case the
ABC) on the DeviceNet network.
ABC
Input Data
Output Data
0x000
Actual Temperature
General Data
0x200
0x400
Temperature Setpoint
(not used in this example)
0x3FF
The ABC copies the Output Register of
the Temperature Regulator to the InputData area.
The ABC copies the TemperatureSetpoint from the Output Data area to
the Input Register in the TemperatureRegulator.
Output Register
Input Register
Actual Temperature
Temperature Setpoint
Anybus Communicator DeviceNet User Manual
0x???
Subnetwork
0x1FF
Serial Device - Temperature Regulator
The Temperature Regulator has two
registers, holding the Setpoint Temperature
and the Actual Temperature respectively.
Doc: HMSI-27-305, Rev. 3.12
Basic Operation 17
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”, “DF1 Master Mode” and “Generic Data Mode”. Note that the protocol mode only specifies the basic communication model, not the actual subnetwork protocol.
•
Master Mode
In this mode, the gateway 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 gateway first.
For more information about this mode, see “Master Mode” on page 18.
•
DF1 Master Mode
In this mode, the gateway acts as a master on the subnetwork, using the DF1 protocol. The serial
communication takes place in a query-response fashion. For more information about this mode,
see “DF1 Protocol Mode” on page 49.
•
Generic Data Mode
In this mode, there is no master-slave relationship between the subnetwork nodes and the gateway; any node on the subnetwork, including the gateway, may spontaneously produce or consume messages.
For more information about this mode, see “Generic Data Mode” on page 19.
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 two protocol modes will be described later in this document.
•
Node
A node represents a single device on the subnetwork. Each node can be associated with a number of transactions, see below.
•
Transaction
A “transaction” represents a complete serial telegram, and consists of a number of frame objects
(see 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 calculated checksum.
Anybus Communicator DeviceNet User Manual
Doc: HMSI-27-305, Rev. 3.12
Basic Operation 18
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 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 messages to all nodes on the network, without expecting them to respond to the broadcasted message. This
is also reflected in the gateway, which features a dedicated broadcaster node.
Control System
Gateway
Subnetwork Devices
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 Configuration 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.
Anybus Communicator DeviceNet User Manual
Doc: HMSI-27-305, Rev. 3.12
Basic Operation 19
2.3.4 Generic Data Mode
In this mode, there is no master-slave relationship between the nodes on the subnetwork and the gateway. Any node, including the gateway, 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 gateway “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 49.
Anybus Communicator DeviceNet User Manual
Doc: HMSI-27-305, Rev. 3.12
Basic Operation 20
2.4 Data Representation on DeviceNet
2.4.1 General
DeviceNet is based on the Control and Information protocol (CIP) which is also the application layer
for ControlNet and EtherNet/IP.
The input and output data is accessed using I/O connections or explicit messages towards the Assembly
Object and the Parameter Input/Output Mapping Objects.
See also...
•
“CIP Object Implementation” on page 70
2.4.2 Data Types
The input and output data holds two types of data; I/O Data and parameter data. I/O Data is exchanged
on change of value, and can be accessed using I/O connections towards the Assembly Object.
Parameter data can be accessed acyclically via the Parameter Input- and Output Mapping Objects. Note
however that each instance attribute within these objects must be created manually using the Anybus
Configuration Manager. For more information see “Parameter Data Initialization (Explicit Data)” on
page 82.
See also...
•
“Assembly Object, Class 04h” on page 74
•
“Parameter Data Input Mapping Object, Class B0h” on page 79
•
“Parameter Data Output Mapping Object, Class B1h” on page 80
•
“Fieldbus Settings” on page 27
Anybus Communicator DeviceNet User Manual
Doc: HMSI-27-305, Rev. 3.12
Basic Operation 21
2.4.3 Memory Layout
The I/O sizes are specified using the Anybus Configuration Manager and correlates to gateway memory
as follows:
Example:
In this example, the I/O Sizes for the gateway have been set to the following values:
IO Size In= 256 bytes(0x0100)
IO Size Out= 128 bytes(0x0080)
Resulting memory layout:
Input Data
0x000
Output Data
0x200
General Data
0x400
I/O Data (Output)
I/O Data (Input)
0x27F
0x280
(Cannot be accessed
from DeviceNet)
0x0FF
0x100
Parameter Data (Output)
Parameter Data (Input)
0x1FF
Anybus Communicator DeviceNet User Manual
0x3FF
0x???
Doc: HMSI-27-305, Rev. 3.12
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.
Entries preceded by a “+” holds further configuration parameters or “sub menus”. To gain access to these parameters, the entry must be expanded by clicking “+”.
This menu entry holds additional
sub-entries / parameters
There are three main levels in the navigation window,
namely Fieldbus, Communicator RS232/422/485, and
Subnetwork.
Right-clicking on entries in this section brings out additional selections related to that particular entry.
•
C: Parameter Section
This section holds a list of parameters or options related to
the currently selected entry in the Navigation Section.
The parameter value may be specified either using a selection box or manually, depending on the parameter itself.
Values can be specified in decimal form (e.g. “42”), or in
hexadecimal format (e.g. “0x2A”).
•
D: Information Section
This section holds information related to the currently selected parameter.
Anybus Communicator DeviceNet User Manual
Doc: HMSI-27-305, Rev. 3.12
Navigating ACM 23
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.
Item
Select a Name for the
Configuration
Enable Password
Download Password(6)
Upload Password(6)
Description
Enter a descriptive name for
the new configuration
Enables password protection
Set passwords for downloading
and uploading the configuration
(max. 6 characters)
CAUTION: Always keep a copy of the password
in a safe place. A lost password cannot be retrieved!
•
Exit
Close ACM.
Anybus Communicator DeviceNet User Manual
Doc: HMSI-27-305, Rev. 3.12
Navigating ACM 24
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 61).
Note that when the Data Logger is active, this menu entry is changed to “Stop Logging”.
•
Options
This will open the following window:
Item
Warning on Delete
Warning on Unsaved
Configuration
Show Wizard when
“New” menu is selected
Select language
Anybus Communicator DeviceNet User Manual
Description
A confirmation dialog is displayed each time something is deleted.
A confirmation dialog is displayed when closing ACM with unsaved data.
The Wizard is displayed each time a new configuration is created.
Selects which language to use. The new setting will be active the next time the program is launched.
Doc: HMSI-27-305, Rev. 3.12
Navigating ACM 25
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 61.
Download firmware to the embedded fieldbus interface.
Warning: Use with caution.
Restores the gateway firmware to the
original state (does not affect the embedded fieldbus interface).
When selected, the downloaded configuration will not be executed by the gateway.
Warning: Use with caution.
Creates an error log file
View
•
Toolbar
Enables/disables the toolbar icons at the top of the main window.
•
Status Bar
Enables/disables the status bar at the bottom of the main window.
Help
•
Contents/Search For Help On...
Opens a built-in browser window with a link to the Anybus
support website.
•
About...
Displays general information about the gateway and the current
version of ACM.
Anybus Communicator DeviceNet User Manual
Doc: HMSI-27-305, Rev. 3.12
Navigating ACM 26
3.1.2 Toolbar Icons
The toolbar features icons for the most commonly used functions.
•
New, Open & Save
See “File” on page 23.
•
New
Open
Save
Upload from ABC & Download to ABC
See “Tools” on page 24.
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.
•
Up one Level
Cut
Copy
Paste
Delete
Insert
Connect
Clicking on this icon will cause ACM to attempt to connect to the gateway.
Connect
•
Disconnect
Clicking on this icon will cause ACM to disconnect from the gateway.
Disconnect
•
Start Logging & Stop Logging
See “Tools” on page 24 & “Data Logger” on page 61.
Start Log.
•
Stop Log.
Sub-network Monitor
Clicking on this icon will launch the sub-network Monitor
(see “Sub-network Monitor” on page 56).
•
Sub-Network
Monitor
Add Command
This icon is used to add commands to the currently selected node.
•
Add Command
Add Mailbox
(Advanced functionality, see “Mailbox Editor” on page 81)
Add Mailbox
•
Add Node & Add Broadcaster
These icons are used to add nodes to the configuration.
Node
•
Node Monitor
Clicking on this icon will launch the Node Monitor (see “Node Monitor” on
page 57)
•
Broadcaster
Node Monitor
Add Transaction(s)
These icons are used to add transactions to the currently selected node.
Anybus Communicator DeviceNet User Manual
Add
Transactions
Add
Transaction
Doc: HMSI-27-305, Rev. 3.12
Chapter 4
4. Basic Settings
4.1 Fieldbus Settings
(Select “Fieldbus” in the Navigation Section to gain access to the
parameters described in this section).
General
During start-up the fieldbus interface of the Anybus Communicator is initialized to fit the configuration
created in the Anybus Configuration Manager. Optionally, some initialization parameters can be set
manually to provide better control over how the data shall be treated by the gateway.
Fieldbus Type
The Anybus Configuration Manager supports a wide range of networking systems. Make sure that this parameter is set to “DeviceNet”.
IO Sizes
Fieldbus Type
These parameters specify how data from the internal memory
buffer shall be exchanged on DeviceNet. This can either be handled automatically based on the subnetwork configuration, or
specified manually.
•
Automatic
All data will be represented as I/O Data on DeviceNet.
•
User defined
Additional parameter properties appear; “IO Size In” and
IO Sizes
“IO Size Out”. The specified amount, starting at address
0x0000 of the respective memory buffers, will be reserved
for and represented as I/O Data. The remainder will be reserved for parameter data.
See also...
•
“Data Representation on DeviceNet” on page 20
•
“Assembly Object, Class 04h” on page 74
•
“Parameter Data Input Mapping Object, Class B0h” on page 79
•
“Parameter Data Output Mapping Object, Class B1h” on page 80
Anybus Communicator DeviceNet User Manual
Doc: HMSI-27-305, Rev. 3.12
28
4.2 Communicator Parameters
Interface
Only serial communication is currently supported.
Control/Status Word
See “Control and Status Registers” on page 65.
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.
This setting is similar to “Enabled”, except that the control system is not required to set the
“Data Valid”-bit to start the sub-network communication.
This setting completely disables the Control and Status Registers.
Module Reset
This parameter specifies how the gateway will behave in the event of a fatal error.
Value
Enabled
Disabled
Description
The gateway will be restarted, and no error will be indicated to the user.
The gateway will halt and indicate an error.
Protocol Mode
This parameter specifies which protocol mode to use for the sub-network. See “Protocol Modes” on
page 17.
Value
Generic Data Mode
Master Mode
DF1
Description
This mode is primarily intended for Produce & Consume-based protocols, where there are
no Master-Slave relationship between the gateway and the nodes on the sub-network.
This mode is intended for “Query & Response”-based protocols, where a single Master
exchanges data with a number of Slaves.
This mode is intended for the DF1 protocol. The Anybus Communicator can only be configured as a Master with half-duplex communication.
Note: This is the only mode available if you intend to configure an ABC module for DF1.
Statistics
The Transmit- and Receive Counters indicate how many transactions that have successfully been exchanged on the sub-network. This feature is primarily intended for debugging purposes.
•
Receive Counter Location
Specifies the location of the Receive Counter in the internal memory buffer.
•
Transmit Counter Location
Specifies the location of the Transmit Counter in the internal memory buffer.
•
Statistics
Enables/disables the Receive and Transmit Counters.
Anybus Communicator DeviceNet User Manual
Doc: HMSI-27-305, Rev. 3.12
29
4.1 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.
Master Mode and Generic Mode
1200
2400
4800
9600
19200
35700
38400
57600
7, 8
None, Odd, Even
RS232, RS422, RS485
1, 2
Start- and End Character
Note: These parameters are only available in Generic Data Mode.
Start and end characters are used to indicate the beginning and end of a serial message. For example, a
message may be initiated with <ESC> and terminated with <LF>. In this case, the Start character would
be 0x1B (ASCII code for <ESC>) and the End character 0x0A (ASCII code for <LF>)
Parameter
End character value
Use End character
Start character value
Use Start character
Description
End character for the message, ASCII
Determines if the End character shall be used or not
Start character for the message, ASCII
Determines if the Start character shall be used or not
Valid settings
0x00–0xFF
Enable / Disable
0x00–0xFF
Enable / Disable
Timing (Message Delimiter)
The parameters in this category differs slightly between the different protocol modes.
•
Master Mode
The Message Delimiter specifies the time that separates two messages in steps of 10 ms. If set to
0 (zero), the gateway will use the standard Modbus delimiter of 3.5 characters (the actual number
of ms will be calculated automatically based on the currently used communication settings).
•
Generic Data Mode
The Message Delimiter specifies the time that separates two messages in steps of 10 µs.
Anybus Communicator DeviceNet User Manual
Doc: HMSI-27-305, Rev. 3.12
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...
Description
Paste a node from the clipboard
Launch the subnet monitor (see “Sub-network Monitor” on page 56)
Add a node to the configuration
Add a broadcaster node to the configuration
Add a previously saved node
View diagnostic information about the sub-network
a. This function is only available in Master Mode.
5.3 Node Parameters
5.3.1 Master Mode and Generic Data Mode
To gain access to the parameters described in this section, select a node in the Navigation Section.
Parameter
Slave Address
Description
The value entered here may be used to set the node address in certain commands.
For more information, see “The Command Editor” on page 46.
Anybus Communicator DeviceNet User Manual
Doc: HMSI-27-305, Rev. 3.12
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. The query is issued
by the gateway, while responses are issued by the slaves on the sub-network. The Broadcaster
can only send transactions.
•
Generic Data Mode
Transactions can be added as desired for both directions. Transactions sent to the sub-network
are called “Transaction Produce”, and transactions issued by other nodes are called “Transaction
Consume”.
•
DF1 Master Mode
Please refer to “DF1 Protocol Mode” on page 49.
Theoretically, the gateway supports up to 150 transactions. The actual number may however be less depending on the memory requirements of the defined transactions.
Anybus Communicator DeviceNet User Manual
Doc: HMSI-27-305, Rev. 3.12
Transactions 32
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 57)
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.
Add a “Consume”-transaction
Add a “Produce”-transaction
Add predefined transactions to the node
Insert a new node above the currently selected one
Save the selected node
Insert a previously saved node above the currently selected node
To increase readability, each node can be given a unique name using this function
a. Only available if more than one node exists
b. Only available in Master Mode
c. Only available in Generic Data Mode
Anybus Communicator DeviceNet User Manual
Doc: HMSI-27-305, Rev. 3.12
Transactions 33
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.
Offline options for fieldbus
Note: This setting is only relevant for the Broadcaster node.
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.
• Clear - The data destined for the slave-devices is cleared (set to zero)
• Freeze - The data destined for the slave-device is frozen
Offline options for sub-network
• NoScanning -The updating of the sub-network is stopped
This parameter specifies the action to take for this transaction if the sub-network goes
offline. This affects the data that is reported to the control system.
• Clear - Data is cleared (0) on the higher level network if the sub-network goes
offline
Reconnect time (10 ms)
• Freeze - Data is frozen on the higher level network if the sub-network goes offline
This parameter specifies how long the gateway shall wait before attempting to reconnect a disconnected node. A node will be disconnected in case the maximum number
of retries (below) has been reached.
The entered value is multiplied by 10. An entered value of 5 will result in 50 ms.
Retries
Timeout time (10 ms)
Trigger byte address
Note: This setting is not relevant for the Broadcaster node.
This parameter specifies how many times a timeout may occur in sequence before the
node is disconnected.
This parameter specifies how long the gateway will wait for a response from a node. If
this time is exceeded, the gateway will retransmit the Query until the maximum number of retries (see above) has been reached.
The entered value is multiplied by 10. An entered value of 5 will result in 50 ms.
This parameter specifies the location of the trigger byte in internal memory (only relevant when “Update mode” is set to “Change of state on trigger”).
Valid settings range from 0x200 to 0x3FF and 0x400 to 0xFFF
Anybus Communicator DeviceNet User Manual
Doc: HMSI-27-305, Rev. 3.12
Transactions 34
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.
• Change of state on trigger
The Query is issued when the trigger byte value has changed. This feature enables the control system to notify the gateway when to issue a particular Query. To
use this feature correctly, the control system must first update the data area associated with the Query/transaction, then increase the trigger byte by one. The location of the trigger byte is specified by the “Trigger byte address” parameter. The
trigger byte is checked at the interval specified in the “Update time” parameter.
This parameter specifies how often the transaction will be issued in steps of 10 ms
(relevant only when “Update mode” is set to “Cyclically”, “On data change” or “Change
of state on trigger”).
Update time (10 ms)
The entered value is multiplied by 10. An entered value of 5 will result in 50 ms.
6.3.2 Parameters (Response)
Parameter
Trigger byte
Trigger byte address
Description
This parameter is used to enable/disable the trigger functionality for the response. If
enabled, the gateway will increase the trigger byte by one when the gateway receives new
data from the sub-network. This can be used to notify the control system of the updated
data.
The location of the trigger byte is specified by the “Trigger byte address” parameter below.
This parameter specifies the location of the trigger byte in the internal memory buffer.
Valid settings range from 0x000 to 0x1FF and 0x400 to 0xFFF
Anybus Communicator DeviceNet User Manual
Doc: HMSI-27-305, Rev. 3.12
Transactions 35
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.
• Clear
Data is cleared (0) on the sub-network if the higher level network goes offline
• Freeze
Data is frozen on the sub-network if the higher level network goes offline
• NoScanning
Update mode
Stop subnet scanning for this transaction if the higher level network goes offline
The update mode for the transaction:
• Cyclically
The transaction is sent cyclically at the interval specified in “Update Time”.
• 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 transaction is sent once at startup.
• Change of state on trigger
Update time (10 ms)
The transaction is sent when the trigger byte has changed. This feature enables the
control system to notify the gateway when to issue a particular transaction. To use this
feature correctly, the control system must first update the data area associated with
the transaction, then increase the trigger byte by one. The location of the trigger byte
is specified by the “Trigger byte address” parameter. The trigger byte is checked at the
interval specified in the “Update time” parameter.
This parameter specifies how often the transaction will be issued in steps of 10ms
(relevant only when “Update mode” is set to “Cyclically”, “On data change” or “Change of
state on trigger”).
The entered value is multiplied by 10. An entered value of 5 will result in 50 ms.
Anybus Communicator DeviceNet User Manual
Doc: HMSI-27-305, Rev. 3.12
Transactions 36
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.
This way, the control system can instruct the gateway to produce a specific transaction on
the sub-network by updating the corresponding trigger byte.
The trigger byte should be incremented by one for each activation. Please note that the
trigger byte address must be unique to each transaction. It can not be shared by two or
more transactions.
Note: This parameter has no effect unless the “Update mode” parameter is set to “Change
of state on trigger”.
Valid settings range from 0x200 to 0x3FF and 0x400 to 0xFFF
6.4.2 Consume Transactions
Parameter
Description
Offline options for sub-network This parameter specifies the action to take for this transaction if the sub-network goes
offline. This affects the data that is sent to the higher level network.
• Clear
Data is cleared (0) on the higher level network if the sub-network goes offline
• Freeze
Offline timeout time (10 ms)
Trigger byte
Data is frozen on the higher level network if the sub-network goes offline
This parameter specifies the maximum allowed time between two incoming messages
in steps of 10ms. If this time is exceeded, the sub-network is considered to be offline. A
value of 0 disables this feature, i.e. the sub-network can never go offline.
The entered value is multiplied by 10. An entered value of 5 will result in 50 ms.
• Enable
Enables the trigger byte. The location of the trigger byte must be specified in “Trigger byte address”.
The trigger byte value will be increased each time a valid transaction has been consumed by the gateway.
The trigger byte will also be increased if the offline option is set to “Clear” and the
offline timeout time value is reached.
This feature enables the control system to be notified each time new data has been
consumed on the sub-network.
• Disable
Trigger byte address
Disables the trigger byte functionality.
This parameter specifies the location of the trigger byte in the internal memory buffer.
Valid settings range from 0x000 to 0x1FF and 0x400 to 0xFFF.
Please note that the trigger byte address must be unique to each transaction. It can not
be shared by two or more transactions.
Anybus Communicator DeviceNet User Manual
Doc: HMSI-27-305, Rev. 3.12
Transactions 37
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. When editing
transactions which are based on predefined commands, certain parts of the transaction may not be editable.
The File menu features the following entries:
•
Apply Changes
This will save any changes and exit to the main
window.
•
Exit
Exit without saving.
Example:
The transaction created in this example are built up as follows:
The first byte holds the STX (0x02) followed by two bytes specifying the length of the data field
(in this case 8). The next 8 bytes are data and since this is a “query”-transaction, the data is to be
fetched from the Output Area which starts at address location 0x202. No swapping will be performed on the data. This is followed by a two-byte checksum. The checksum calculation starts
with the second byte in the transaction.
The transaction ends with a byte constant, the ETX (0x03).
Anybus Communicator DeviceNet User Manual
Doc: HMSI-27-305, Rev. 3.12
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.
There are 5 types of frame objects, which are described in detail later in this chapter:
•
Constant Objects
•
Limit Objects
•
Data Objects
•
Variable Data Objects
•
Checksum Objects
Example:
The following Transaction consists of several frame objects; three constants, a data object, and
a checksum object.
Transaction
Constant
Constant
Variable Length Data
Checksum
Constant
7.2 Adding and Editing Frame Objects
To add a frame object to a Transaction, right-click on
the Transaction in the Navigation Section and select
one of the entries in the menu that appears.
The entry called “Transaction Editor” will launch the
Transaction Editor, which is used to edit transactions
and frame objects in a more visual manner. For more
information, see “Transaction Editor” on page 37.
To edit parameters associated with a particular frame
object, select the frame object in the Navigation Section. The settings for that frame object will be displayed in the Parameter Section.
It is also possible to edit the frame objects in a transaction in a more visual manner using the Transaction
Editor, see “Transaction Editor” on page 37.
Anybus Communicator DeviceNet User Manual
Doc: HMSI-27-305, Rev. 3.12
Frame Objects 39
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.
To set the value of the object, select it in the Navigation Section and enter the desired value in the Parameter section.
Parameter
Value
Description
Constant value
Anybus Communicator DeviceNet User Manual
Doc: HMSI-27-305, Rev. 3.12
Frame Objects 40
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. If
not, the message will be discarded.
There are 3 types of interval objects:
•
Byte
8 bit interval
•
Word
16 bit interval
•
Dword
32 bit interval
To set the range of the object, select it in the Navigation Section and enter the desired range in the Parameter section as follows:
Parameter
Maximum Value
Minimum Value
Description
This is the largest allowed value for the range.
Range:0x00 to 0xFFh(byte)
0x0000 to 0xFFFFh(word)
0x00000000 to 0xFFFFFFFFh(dword)
Note: The value must be larger than the Minimum Value.
This is the smallest allowed value for the range.
Range:0x00 to 0xFEh(byte)
0x0000 to 0xFFFEh(word)
0x00000000 to 0xFFFFFFFEh(dword)
Note: The value must be less than the Maximum Value.
Anybus Communicator DeviceNet User Manual
Doc: HMSI-27-305, Rev. 3.12
Frame Objects 41
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.
To specify the properties of the object, select it in the Navigation Section and enter the desired settings
in the Parameter section as follows:
Parameter
Byte Swapping
Description
• No Swapping
No swapping is 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
The length of the data block, in bytes. In case of a Response or Consume transaction, incoming messages where the data size differs from the value specified here will be discarded. Maximum data length allowed for one frame is 300 bytes.
The location of the data block in the internal memory buffer.
Data Length
Data Location
7.6 Variable Data Object
Note: Only one Variable Data Object is permitted for each transaction.
This object is similar to the Data Object, except that it has no predefined length. Instead, an End or
Length-character specifies the size of the data block as follows:
(Variable Data Object)
Data
Data of arbitrary length
•
(Variable Data Object)
0x00
End Character
0x04
Length Character
Data
4 bytes of data
Produce/Query Transactions
The specified data block will be forwarded from the higher level network to the sub-network.
The control system must supply an End or Length character in order for the gateway to know
the size of the data block.
The End- or Length-character itself may either be forwarded to the sub-network or discarded.
•
Consume/Response Transactions
The specified data block is forwarded from the sub-network to the higher level network. The
End- or Length-character will be generated by the gateway automatically (if applicable).
The End- or Length-character itself may either be forwarded to the higher level network or discarded.
Anybus Communicator DeviceNet User Manual
Doc: HMSI-27-305, Rev. 3.12
Frame Objects 42
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”.
• Disabled
Filler byte
Data Location
Object Delimiter
(Produce/Query)
Don’t fill
Filler byte value. Only used if “Fill unused bytes” has been enabled.
The offset in the internal memory buffer where the data shall be read from / written to
• Length Character
Length character visible in internal memory buffer but not sent out on the sub-network
• Length Character Visible
Length character visible in internal memory buffer and sent out on the sub-network
• End Character
End character visible in internal memory buffer but not sent out on the sub-network
• End Character Visible
End character visible in the internal memory buffer and sent out on the sub-network
• No Character
Object Delimiter
(Consume/Response)
No end- or length-character generated in the internal memory buffer
• Length Character
Length character visible in internal memory buffer but not received from the sub-network
• Length Character Visible
Length character visible in internal memory buffer and received from the sub-network
• End Character
End character visible in internal memory buffer but not received from the sub-network
• End Character Visible
End character visible in the internal memory buffer and received from the sub-network
• No Character
No end or length characters included in the received string or generated in the internal
memory buffer
End Character Value
Maximum Data Length
End Character valueb
The maximum allowed length (in bytes) of the variable data object. If the actual length of the
data exceeds this value, the message will be discarded. The value must not exceed 256 bytes,
which is the maximum data length allowed for one frame.
a. Only relevant for Consume/Response transactions
b. Only used if “Object Delimiter” is set to “End Character” or “End Character Visible”
Anybus Communicator DeviceNet User Manual
Doc: HMSI-27-305, Rev. 3.12
Frame Objects 43
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.a
This parameter specifies which type of algorithm to use:
• CRC (2 bytes)
CRC-16 with 0xA001 polynome (Modbus RTU standard)
• LRC (1 byte)
All bytes are added together as unsigned 8-bit values. The two’s complement of the result
will be used as a checksum.
(Modbus ASCII standard with Error Check Start Byte = 0x01 and Representation = ASCII)
• XOR (1 byte)
All bytes are logically XOR:ed together. The resulting byte will be used as a checksum.
• ADD (1 byte)
Error check type
combined with
Representation
All bytes are added together as unsigned 16-bit values. The lowest 8 bits in the result will
be used as a checksum.
The binary value can be converted to its one’s or two’s complement. This conversion is carried
out before ASCII formatting (see next parameter).
• None
The checksum binary value is transmitted without conversion.
• One’s complement
The checksum value will be converted to its one’s complement (inverse code).
Example: 00001100 will be transmitted as 11110011
• Two’s complement
The checksum value will be converted to its two’s complement (complement code).
Example: 00001100 will be transmitted as 11110100
• Binary
The checksum is transmitted in binary format.
• ASCII
All characters in the checksum are converted to ASCII values.
a. In Generic Data Mode the Start character (if used) will not be included in the checksum calculation.
Anybus Communicator DeviceNet User Manual
Doc: HMSI-27-305, Rev. 3.12
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 52.
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.
Adding a command to a node actually results in (a) transaction(s) being added according to the directions
specified in the command. The frame objects in such a transaction may retrieve their values not only
from parameters in the parameter section, but also from other sources such as the “SlaveAddress”-parameter (see “Node Parameters” on page 30). In such case, the parameters in the parameter section will
be greyed out and cannot be edited directly.
In Master Mode, ACM comes preloaded with commands for most common Modbus RTU functions.
Additional commands can easily be added using the Command Editor (see “The Command Editor” on
page 46). For DF1 Master Mode, see “Services” on page 52. In Generic Data Mode, no predefined commands exist, but custom ones may be implemented as desired.
8.2 Adding & Managing Commands
To add a command to a node, right-click on the node in the Navigation Section and select “Add Command”.
A list of commands will appear:
Select the desired command in the list, and select “Add Command” in the “Command”-menu. The specified command will be
added to the node.
Just like other transactions, the frame objects of added command
may be edited in the Navigation/Parameter Section or using the
Transaction Editor. Note however that certain frame objects may
be locked for editing.
Anybus Communicator DeviceNet User Manual
Doc: HMSI-27-305, Rev. 3.12
Commands 45
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 46.
•
Edit Command
Edit the currently selected command using the Command Editor.
See also “The Command Editor” on page 46.
•
Delete Command
Delete the currently selected command from the list. Note that some commands are fixed and
cannot be deleted.
8.2.2 Toolbar Icons
The toolbar features icons for the Add, Edit and Delete Command functions.
Add Command
Anybus Communicator DeviceNet User Manual
Edit Command
Delete Command
Doc: HMSI-27-305, Rev. 3.12
Commands 46
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. The procedures involved are similar in Generic Data
Mode, but without the limitations imposed by the Modbus RTU protocol.
8.3.2 Basic Navigation
Open the Command Editor by selecting “Edit Command” or “Add Command” from the “Command”menu.
A
B
D
E
C
A: Drop-down Menu
See “Drop-down Menu” on page 47.
B: Name of Command
Actual name of the command, in text form.
C: Command Transactions
This section holds the actual transactions associated with the command. This can either be a query-response pair, or a single transaction, depending on the protocol mode etc.
D: Command ID
This can be used as desired when building the command, e.g. to specify the function code.
E: Other Settings
Setting
Allow Broadcasting
Produce
Consume
Description
Specifies if it is allowed to broadcast the command (only relevant in Master Mode)
The command is producing data (Generic Data Mode only)
The command is consuming data (Generic Data Mode only)
Anybus Communicator DeviceNet User Manual
Doc: HMSI-27-305, Rev. 3.12
Commands 47
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.4 Editing a Command
As mentioned previously, the transaction section in the Command Editor represents the actual transactions associated with the command. Each column represents a frame object within the transaction.
Each column features four rows with the following parameters:
•
Query/Response/Produce/Consume
The upper right cell indicates the direction of the transaction.
•
DisplayName
Each column can be named so that the different parts of the command appears in a more user
friendly manner when editing its settings in the Transaction Editor or in the Parameter Section
of the Main Window.
•
ObjectType
This row specifies the type of frame object that shall be used for the column.
•
Value
This row specifies where the frame object shall retrieve its value/settings.
Value
Description
Depend
This setting is only relevant for Responses in Master Mode.
The value will be retrieved from the corresponding part of the “Query”-transaction.
Id
Value will be retrieved from the “Command ID”-setting (see “Basic Navigation” on page 46).
User
Settings associated with the object can be edited by the user.
[SlaveAddress] Value will be retrieved from the “SlaveAddress”-parameter (see “Node Parameters” on page 30).
(other settings) Other settings are no longer supported.
Anybus Communicator DeviceNet User Manual
Doc: HMSI-27-305, Rev. 3.12
Commands 48
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.
•
Example Query
Query
DisplayName
Object Type
Value
•
1
Slave Address
Byte Object
[SlaveAddress]
The value of this byte
constant will be set
using the “SlaveAddress” parameter (see
“Node Parameters” on
page 30).
2
Function
Byte Object
ID
The value of this byte
constant will be set
using the “Command
ID”-field.
3
Data
Data Object
User
The size and location
of the data associated
with this object is
determined by the
user.
4
Checksum
Checksum Object
User
The checksum type etc
can be selected by the
user. By default, this is
set to match the Modbus-RTU standard.
2
Function
Byte Object
ID
The value of this byte
constant will be set
using the “Command
ID”-field.
3
Data
Data Object
User
The size and location
of the data associated
with this object is
determined by the
user.
4
Checksum
Checksum Object
Depend
This object will retrieve
its settings from the
corresponding object
in the Query.
Example Response
Response
DisplayName
Object Type
Value
1
Slave Address
Byte Object
[SlaveAddress]
This value is linked to
the “SlaveAddress”
parameter in the
parameter window.
By default, the Modbus-RTU-specific frame objects are already in place, and a data object is inserted
between the function code and the CRC. These objects cannot be moved or deleted, however it is possible to add additional objects between the function code and the CRC as desired.
Name the new command by entering its name in the “Command Name” field, and enter a suitable function code in the “Command ID”-field. If the command is allowed to be broadcasted, check the “Allow
Broadcasting” checkbox.
Anybus Communicator DeviceNet User Manual
Doc: HMSI-27-305, Rev. 3.12
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.
The communication is based on a query-response scheme, where the gateway issues a query on the subnetwork. The addressed node on the sub-network is expected to issue a response to that query. Nodes
are not permitted to issue responses spontaneously, i. e. without first receiving a query.
Control System
Gateway
Subnetwork Devices
In DF1 Master Mode, ACM comes preloaded with a number of services, that can be selected by the user.
The actual DF1 commands, that perform the services during runtime, are predefined in the Anybus
Communicator. The configuration of the services is performed by right-clicking on a node in the ACM
and selecting “Add Command”.
Anybus Communicator DeviceNet User Manual
Doc: HMSI-27-305, Rev. 3.12
DF1 Protocol Mode 50
9.2 Communicator Parameters
Interface
Currently, only serial communication is supported.
Control/Status Word
(See “Control and Status Registers” on page 65).
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.
This setting is similar to “Enabled”, except that the control system is not required to set the
“Data Valid”-bit to start the sub-network communication.
This setting completely disables the Control and Status Registers.
Module Reset
This parameter specifies how the gateway will behave in the event of a fatal error.
Value
Enabled
Disabled
Description
The gateway will be restarted, and no error will be indicated to the user.
The gateway will halt and indicate an error.
Protocol Mode
This parameter specifies which protocol mode to use for the sub-network.
Value
DF1
Description
This mode is intended for the DF1 protocol. The Anybus Communicator can only be configured as a Master with half-duplex communication.
Note: This is the only mode available if you intend to configure an ABC module for DF1.
See also “Protocol Modes” on page 17.
Statistics
The Transmit- and Receive Counters indicate how many transactions that have successfully been exchanged on the sub-network. This feature is primarily intended for debugging purposes.
•
Receive Counter Location
Specifies the location of the Receive Counter in the internal memory buffer.
•
Transmit Counter Location
Specifies the location of the Transmit Counter in the internal memory buffer.
•
Statistics
Enables/disables the Receive and Transmit Counters.
Anybus Communicator DeviceNet User Manual
Doc: HMSI-27-305, Rev. 3.12
DF1 Protocol Mode 51
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.
Valid Settings
2400
4800
9600
19200
38400 (Default)
8
None, Odd, Even
RS232, RS422, RS485
1
DF1 Settings
Parameter
Master Node Address
Poll time, active slaves (10 ms)
Description
Node address of the master, valid values: 0–254
Determines how often the slave shall be polled in steps of 10 ms
Poll time, inactive slaves (10 ms) Determines how often the slave shall be polled in steps of 10 ms
Default
1
100 msa
1000 msb
a. The default value is given as 10 in the parameter window. Each change of 10 ms either increases or decreases
this value by 1, i.e. 9 represents a poll time of 90 ms and 11 represents a poll time of 110 ms.
b. The default value is given as 100 in the parameter window. Each change of 10 ms either increases or decreases
this value by 1, i.e. 99 represents a poll time of 990 ms and 101 represents a poll time of 1010 ms.
Anybus Communicator DeviceNet User Manual
Doc: HMSI-27-305, Rev. 3.12
DF1 Protocol Mode 52
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 30.
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. The user configures each slave with services that
can be issued from the master. A total of 50 services are allowed.
The Anybus Communicator supports a selection of DF1 commands. When the gateway is going to execute a service, it automatically chooses the appropriate DF1 command(s) that are used to perform the
service on the selected DF1 node type.
Anybus Communicator DeviceNet User Manual
Doc: HMSI-27-305, Rev. 3.12
DF1 Protocol Mode 53
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.
General Configuration Parameters
These parameters are common to all services, but the settings
are individual to each instance of a service.
General:
Parameter
Offline options for
fieldbus
Offline options for
sub-network
Update mode
Description
The action to take for this service
if the fieldbus goes offline. This
option affects the data that is sent
out to the sub-network.
The action to take for this service
if the sub-network goes offline.
This option affects the data that is
reported to the fieldbus master.
The update mode for this service
Valid settings
Clear
Freeze
Noscanning
Clear
Freeze
Cyclically
On data change
Single shot
Change of state
on trigger
Timing:
Parameter
Retries
Timeout time (10 ms)
Description
The number of times to resend this service before the node is disconnected
The time to wait before resending this service (in steps of 10 ms)a
Default
3
1000 ms
Update time (10 ms)
The minimum time between two services of this kind (in steps of 10 ms)a
1000 ms
a. The default value is given as 100 in the parameter window. Each change of 10 ms either increases or decreases
this value by 1, i.e. 99 represents a poll time of 990 ms and 101 represents a poll time of 1010 ms.
Trigger:
Parameter
Request Trigger byte
address
Response Trigger byte
Response Trigger byte
address
Description
The memory location of the trigger byte this service uses for updates on trigger
byte changes
Enables/disables the trigger byte
The memory location of the trigger byte this service uses for updates on trigger
byte changes
Valid settings range from 0x200 to 0x3FF and 0x400 to 0xFFF
Anybus Communicator DeviceNet User Manual
Default
0x05FF
Disabled
0x05FF
Doc: HMSI-27-305, Rev. 3.12
DF1 Protocol Mode 54
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. The size is given in bytes
which means that it always has to be an even number as only whole elements can be read from the slave.
One bit/integer element is 2 bytes and one float element is 4 bytes. The range of the size differs, depending on node type:
Size range (in bytes)
PLC-5
1–26
SLC500
1–28
MicroLogix
1–26
Data options:
Parameter
Byte swap
Data length
Offset
Description
Determines if the data shall be swapped
Valid settings
No byte swap
Swap words
Swap double words
The number of bytes, read from the DF1 network, to write to the area determined Size
by the Offset parameter
The offset in the internal memory buffer in the module, where the data shall be
read.
Anybus Communicator DeviceNet User Manual
Doc: HMSI-27-305, Rev. 3.12
DF1 Protocol Mode 55
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.
Integer
Bit
Float
The number of bytes to read from the slave. One bit/integer element is PLC-5: 2–240
2 bytes and one float element is 4 bytes. The parameter must have an SLC500: 2–236
even value as only whole elements can be read from the slave.
MicroLogix: 2–242
Data Options
Parameter Description
Byte swap Determines if the data shall be swapped.
Valid settings
No byte swap
Swap words
Swap double words
Data length The number of bytes, read from the DF1 network, to write to the area determined Size
by the Offset parameter
Offset
The offset in the internal memory buffer in the module, where the data shall be
read. See “Memory Map” on page 15.
Note: If the control and status registers are enabled (default), first available data
location will be: Input area 0x002, Output area 0x202.
9.9 Write Data
This service is used to write data to the nodes in the sub-network. The parameters to be configured are
the same as for the service Read Data. The only difference is that data is read from the internal memory
buffer in the Anybus Communicator and written to the sub-network bus, instead of being written to the
internal memory buffer.
Anybus Communicator DeviceNet User Manual
Doc: HMSI-27-305, Rev. 3.12
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.
Note: The sub-network monitor has a negative influence on the overall performance of the gateway.
Therefore the monitor functionality should be used with care.
10.2 Operation
A
B
C
A: Start Network & Stop Network Icons
These icons controls the sub-network activity. To stop all activity, click
on the red light. To start the sub-network again, click on the green light.
Start
Stop
B: Nodes / Transactions
To view data blocks associated with a transaction, select the transaction in the list. The corresponding data will then appear in the Monitor Section (C).
C: Monitor Section
This section visualizes how data is allocated in the Input, Output and General Data areas.
Color
White
Yellow
Blue
Red
Grey
Green
Meaning
Not allocated
Data allocated by a Response or Consume transaction
Data allocated by a Query or Produce transaction
Collision; area has been allocated more than once
Reserved (illustrates memory consumption, area can be allocated if necessary)
Data allocated by Trigger byte, Transmit/Receive Counter, or Control/Status Registers
Anybus Communicator DeviceNet User Manual
Doc: HMSI-27-305, Rev. 3.12
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.
The Node Monitor behaves somewhat differently in the three protocol modes:
•
Master Mode and DF1 Master Mode
The selected Command (Query Transaction) or Service is sent to the sub-network. The response
to the Query can be monitored in the Response Section.
Command Section (Query)
Subnetwork
Response Section
•
Generic Data Mode
The selected command (Transaction Produce) is sent to the sub-network. It is not possible to
monitor any responses etc. generated by other nodes.
Command Section (Produce)
Subnetwork
(Not used)
Anybus Communicator DeviceNet User Manual
Doc: HMSI-27-305, Rev. 3.12
Node Monitor 58
11.2 Navigating the Node Monitor
A
B
C
D
A: Drop-down Menu & Toolbar Icons
See “Drop-down Menu” on page 59 and “Toolbar Icons” on page 60.
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.
D: Monitor Section
This section displays the data associated with the node. Areas in dark grey are reserved for the
Status & Control Registers, and areas displayed in light grey represent the data that is used by the
node.
The data displayed in this section will be refreshed based on the refresh-icons in the toolbar. For
more information, see “Toolbar Icons” on page 60.
Anybus Communicator DeviceNet User Manual
Doc: HMSI-27-305, Rev. 3.12
Node Monitor 59
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.
•
Stop Node
Disable the transactions associated with the node.
Command
This menu is used to specify and issue a command manually.
•
Select Command
Select a command to be sent to the sub-network.
•
Send Command
Send the specified command to the sub-network.
Columns
This menu specifies the number of columns in the Monitor Section.
•
Free
The number of columns depends on the width of the window.
•
8 Multiple
The number of columns will be fixed to 8.
View
This menu specifies the data representation in the Monitor Section.
•
Hex
Display the data in hexadecimal format.
•
Decimal
Display the data in decimal format.
Anybus Communicator DeviceNet User Manual
Doc: HMSI-27-305, Rev. 3.12
Node Monitor 60
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 59.
•
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 59.
•
Resume Refresh & Stop Refresh
The data displayed in the Monitor Section will normally be refreshed automatically (cyclically).
Click on “Stop” to stop automatic data refresh. Data will now only be
refreshed if you click “Refresh” (see below).
Press “Resume” to resume automatic refreshing of data.
•
Refresh
Refreshes the data displayed in the Monitor Section.
Refresh
Anybus Communicator DeviceNet User Manual
Doc: HMSI-27-305, Rev. 3.12
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.2 Operation
Start & Stop Logging
•
Start logging
Select “Start Logging” in the “Tools”-menu. ACM will then prompt for the desired mode of operation, see below.
•
Stop logging
Select “Stop Logging” in the “Tools”-menu. This will open the log-window, see below.
Modes of Operation
Select the desired mode of operation and click “OK” to start logging data.
•
Log until full
Data will be logged until the log-buffer is full.
•
Log continuously
Data will be logged continuously until logging is
stopped by clicking “Stop Logging”. The log-buffer
will contain the most recent data.
Log Window
The logged data is displayed in hexadecimal, decimal and ASCII format for both directions. The time between the log-entries is displayed in a separate column.
The data may optionally be saved in ASCII text format by
clicking “Create Text file”.
Click “Close” to exit.
Anybus Communicator DeviceNet User Manual
Doc: HMSI-27-305, Rev. 3.12
Data Logger 62
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 DeviceNet User Manual
Doc: HMSI-27-305, Rev. 3.12
Chapter 13
13. Configuration Wizards
13.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”. Note however that this will only work when the subnetwork
fits the wizard profile; in all other cases the “Blank Configuration” option must be used.
13.2 Selecting a Wizard Profile
The following window appears each time the Anybus Configuration Manager is started, or upon selecting the “New” entry in the “File” menu (unless it has been disabled in the “Options” menu, see “Tools”
on page 24). does not
Currently, the following wizards are available:
•
Wizard - Modbus RTU Master
This option is suitable for Modbus RTU-based networks.
See also “Wizard - Modbus RTU Master” on page 64.
•
Blank Configuration
This option creates an empty configuration.
Highlight the desired wizard and click “OK” to continue.
Anybus Communicator DeviceNet User Manual
Doc: HMSI-27-305, Rev. 3.12
Configuration Wizards 64
13.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. In all cases, the user should consult the documentation of the
devices that shall be used on the subnetwork for information about their serial communication
requirements, and if necessary contact the manufacturer of the device to obtain further information about the serial communication protocol.
In the event that the wizard does not handle a particular Modbus command required by a device,
it is possible to specify this command manually as a transaction in the Anybus Configuration
Manager.
Using this wizard involves the following steps:
Step 1: Communicator Type
Select “DeviceNet”.
Click “Next” to continue.
Tip: It is possible to return to a previous
menu at any time without losing any settings by clicking “Previous”.
Step 1a: I/O Sizes
This parameter is used to set the sizes of
the in/out data areas. For more information, see “IO Sizes” on page 27.
Click “Next” to continue.
Step 2: Physical Settings
Select the physical properties of the subnetwork.
Click “Next” to continue.
Steps 3 - 6
Consult the online help system for further information.
Anybus Communicator DeviceNet User Manual
Doc: HMSI-27-305, Rev. 3.12
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 28). 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...
•
Report sub-network related problems to the fieldbus control system
•
Ensure that only valid data is exchanged in both directions
•
Enable the fieldbus control system to start/stop data exchange with selected nodes on the subnetwork
If enabled, these registers occupy the first two bytes in the input and output data areas (0x000–0x001
and 0x200–0x201 respectively), which means they can be accessed from the fieldbus just like any other
data in these areas.
Note: Internally, these registers are stored in Motorola-format (i.e. MSB first). If the higher level network uses a different byte order, the upper and lower bytes will appear swapped.
14.1.1 Handshaking Procedure
A special handshaking procedure, which is illustrated in the two flowcharts below, must be followed
when accessing these registers to ensure that both parts receive proper information.
Read Status Register
Write to Control Register
Start
Start
CR_HS_CONFIRM=
SR_HS_SEND?
No
Yes
SR_HS_CONFIRM=
CR_HS_SEND?
Yes
Read Status Register
Write to Control Register
Set CR_HS_CONFIRM
to SR_HS_SEND
Toggle CR_HS_SEND
Done
Done
Anybus Communicator DeviceNet User Manual
No
Doc: HMSI-27-305, Rev. 3.12
Control and Status Registers 66
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.
If the same parameter is set to “Disabled” or “Enabled but no startup lock”, communication will start
as soon as the fieldbus goes online.
State Machine
The fieldbus network participation can be described using a state machine as described below.
A: Offline (No data exchange)
1. Clear the “Data Valid”-bit in the Control Register.
2. Write initial data to the Output Area
according to the sub-network configuration.
A
Start
Offline
(no data exchange)
3. Wait until the fieldbus control system
and the gateway are online on the fieldbus network, and shift to state B.
B
Online
(not yet exchanging data)
B: Online (Not yet exchanging data)
4. Wait until the “Data Valid”-bit in the
Status Register is cleared by the gateway.
5. Set the “Data Valid”-bit in the Control
Register.
C
Online
(exchanging data)
6. When the “Data Valid”-bit in the Status Register is set by the gateway, shift
to state C.
7. If the gateway goes offline on the fieldbus, shift to state A.
C: Online (Exchanging data)
Exchanging valid data in both directions.
If the gateway goes offline on the fieldbus, shift to state A.
Note: The gateway cannot spontaneously clear the “Data Valid”-bit in the Status Register.
Latency
The “Data Valid”-bit in the Status Register may in some cases be delayed. This latency can be caused by
a missing node or a bad connection to a node with a long timeout value assigned to it.
Therefore, the fieldbus control system should not wait for this bit to be set before communicating with
the sub-network devices; it should be considered as an aid for the fieldbus control system to know when
all data has been updated.
Anybus Communicator DeviceNet User Manual
Doc: HMSI-27-305, Rev. 3.12
Control and Status Registers 67
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...
- “Handshaking Procedure” on page 65
- “Control Register Contents (Control System to Gateway)” on page 69
This bit is set when all transactions have been executed successfully at least once.
Once set, it will not change.
1:Data Valid
0:Data not Valid
Note: This bit is not used in Generic Data Mode.
This field holds the last status report from the gateway.
See also...
- “Status Codes in Master Mode and DF1 Master Mode” on page 67
- “Status Code in Generic Data Mode” on page 68
Note: Internally, this is treated as a Motorola-format word (i.e. MSB first). If the higher level network
uses a different byte order, the upper and lower bytes will appear swapped.
14.2.2 Status Codes in Master Mode and DF1 Master Mode
(This table is valid only in Master Mode and DF1 Master Mode).
Code
0x00
Condition
Retransmission
Counter Updated
Type
Warning
0x01
0x02
0x03
0x04
0x1F
Single Node Missing
Multiple Nodes Missing
Buffer Overrun
Other Error
No Error
Error
Error
Warning
Error
Warning
Data
Counter
Description
The number of retransmissions on the subnetwork has increased. If this problem persists, this may eventually trigger a Single- or
Multiple Node(s) Missing condition.
Slave address
A single node is missing.
Number of nodes Multiple nodes are missing.
Slave address
A node returned more data than expected.
Slave address
Undefined error
No errors
Note: Conditions of type “Error” will eventually be followed by a “No Error” condition when the cause
has been resolved. Conditions of type “Warning” are however considered informational and may not
necessarily be followed by a “No Error” condition later on.
Anybus Communicator DeviceNet User Manual
Doc: HMSI-27-305, Rev. 3.12
Control and Status Registers 68
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. received transactions which does not match any of the consume-transactions defined in the sub-network configuration) has
increased.
End character is enabled, but a message delimiter timeout
occurs prior to receiving it.
The of number of timed out consume-transactions has
increased.
See also...
- “Consume Transactions” on page 36 (Offline timeout
time)
A node returned more data than expected - or - the gateway
was unable to finish processing a message prior to receiving a new one.
Undefined error
No errors
Note: Conditions of type “Error” will eventually be followed by a “No Error” condition when the cause
no longer is detected. Conditions of type “Warning” are however considered informational and may not
necessarily be followed by a “No Error” condition later on.
Anybus Communicator DeviceNet User Manual
Doc: HMSI-27-305, Rev. 3.12
Control and Status Registers 69
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...
- “Handshaking Procedure” on page 65
- “Status Register Contents (Gateway to Control System)” on page 67
This bit controls data consistency (see “Data Consistency” on page 66).
1:Output Area valid; exchange data on the sub-network
0:Output Area not valid; do not exchange data on the sub-network
Note: This bit is only relevant if the Control/Status Registers are set as “Enabled”
If set, the specified command will be executed by the gateway (see below).
This field holds commands which can be executed by the gateway (see below).
See also...
- “Control Codes in Master Mode and DF1 Master Mode” on page 69
- “Control Codes in Generic Data Mode” on page 69
Note: Internally, this is treated as a Motorola-format word (i.e. MSB first). If the higher level network
uses a different byte order, the upper and lower bytes will appear to be swapped.
14.3.2 Control Codes in Master Mode and DF1 Master Mode
(This table is valid only in Master Mode and DF1 Master Mode).
Code
0x00
0x01
0x02
Instruction
Disable Node
Enable Node
Enable Nodes
Data
Actual node address
Actual node address
Actual number of nodes to enable
Description
Disables the specified node.
Enables a previously disabled node.
Enables the specified number of nodes, starting from the first node in the configuration.
Remaining nodes will be disabled.
14.3.3 Control Codes in Generic Data Mode
(No Control Codes are currently supported in this mode).
Anybus Communicator DeviceNet User Manual
Doc: HMSI-27-305, Rev. 3.12
Chapter 15
15. CIP Object Implementation
DeviceNet is based on the Control and Information protocol (CIP) which is also the application layer
for ControlNet and EtherNet/IP.
The following CIP-objects are implemented in this product:
Mandatory Objects
Object
Identity Object, Class 01h
Message Router, Class 02h
DeviceNet Object, Class 03h
Assembly Object, Class 04h
Connection Object, Class 05h
Acknowledge Handler Object, Class 2Bh
Page
71
72
73
74
75
77
Vendor Specific Objects
Object
Diagnostic Object, Class AAh
Parameter Data Input Mapping Object, Class B0h
Parameter Data Output Mapping Object, Class B1h
Anybus Communicator DeviceNet User Manual
Page
78
79
80
Doc: HMSI-27-305, Rev. 3.12
CIP Object Implementation 71
15.1 Identity Object, Class 01h
15.1.1 General Information
Object Description
Implemented Services
Class services:
Get Attribute All
Get Attribute Single
Instance services:
Get Attribute All
Get Attribute Single
Reset
15.1.2 Class Attributes
#
1
Access
Get
Name
Revision
Type
UINT
Value
0001h
Description
Revision 1
Value
Default: 005Ah
Default: 000Ch
Default: 003Ch
Description
HMS Industrial Networks AB
Communication Adapter
Anybus Communicator for DeviceNet
Major fieldbus version
Minor fieldbus version
Device status, see table below
Serial number of the module
Product name
-
15.1.3 Instance Attributes
#
1
2
3
Access
Get
Get
Get
Name
Vendor ID
Device Type
Product Code
4
Get
Revision
5
6
7
8
Get
Get
Get
Get
Type
UINT
UINT
UINT
Struct of:
USINT
USINT
Status
WORD
Serial Number UDINT
Product Name SHORT_STRING
Config Consist UINT
Value
Module serial number
“AnyBus-C”
N/A
Device Status
bit(s)
0
1
2
3... 7
8
9
10
11
12... 15
Name
Module Owned
(reserved)
Configured
(reserved)
Set for minor recoverable faults
Set for minor unrecoverable faults
Set for major recoverable faults
Set for major unrecoverable faults
(reserved)
Anybus Communicator DeviceNet User Manual
Doc: HMSI-27-305, Rev. 3.12
CIP Object Implementation 72
15.2 Message Router, Class 02h
15.2.1 General Information
Object Description
Supported Services
Class services:
Get Attribute Single
Instance services:
-
15.2.2 Class Attributes
#
1
Access
Get
Name
Revision
Type
UINT
Value
0001h
Description
Revision 1
15.2.3 Instance Attributes
-
Anybus Communicator DeviceNet User Manual
Doc: HMSI-27-305, Rev. 3.12
CIP Object Implementation 73
15.3 DeviceNet Object, Class 03h
15.3.1 General Information
Object Description
Implemented Services
Class services:
Get Attribute Single
Instance services:
Get Attribute Single
15.3.2 Class Attributes
#
1
Access
Get
Name
Revision
Type
UINT
Value
0002h
Description
Revision 2
15.3.3 Instance Attributes
#
1
2
Access
Get
Get
Name
MAC ID
Baud Rate
Type Value
USINT N/A
USINT N/A
5
Get
Allocation Information
Struct of:
BYTE N/A
USINT N/A
Anybus Communicator DeviceNet User Manual
Description
Currently used MacID
Currently used baudrate:
1 = 125 kbps
2 = 250 kbps
3 = 500 kbps
Allocation choice byte
Master’s MAC ID
Doc: HMSI-27-305, Rev. 3.12
CIP Object Implementation 74
15.4 Assembly Object, Class 04h
15.4.1 General Information
Object Description
This object provides access to the I/O Data in the Input- and Output Data areas in the Anybus Communicator.
See also...
•
“Data Representation on DeviceNet” on page 20
•
“Fieldbus Settings” on page 27
Services
Class services:
Get Attribute Single
Instance services:
Get Attribute Single
Set Attribute Single
15.4.2 Class Attributes
#
1
Access
Get
Name
Revision
Type
UINT
Value
0001h
Description
Revision 1
15.4.3 Instance Attributes - Instance/Connection Point 64h
This instance is used to access I/O Data (Input) in gateway memory.
#
3
Access
Get
Name
Data
Type
Array of BYTE
Value
-
Description
Data produced by the ABC
15.4.4 Instance Attributes - Instance/Connection Point 96h
This instance is used to access I/O Data (Output) in gateway memory.
#
3
Access
Set
Name
Data
Type
Array of BYTE
Anybus Communicator DeviceNet User Manual
Value
-
Description
Data consumed by the ABC
Doc: HMSI-27-305, Rev. 3.12
CIP Object Implementation 75
15.5 Connection Object, Class 05h
15.5.1 General Information
Object Description
Implemented Services
Class services:
Get Attribute Single
Instance services:
Get Attribute Single
Set Attribute Single
15.5.2 Class Attributes
#
1
Access
Get
Name
Revision
Type
UINT
Value
0002h
Description
Revision 2
Instance 1 = Explicit messaging connection (Predefined in DeviceNet object)
Instance 2 = Polled connection / COS / Cyclic consuming connection
Instance 3 = Bit strobe connection
Instance 4 = COS / Cyclic producing connection
Instance 10 - 14 = Explicit connection (UCMM allocated)
15.5.3 Instance 1 & 10...14 (Explicit Messaging Connection) Attributes
#
1
Access
Get
Name
State
Type Value
USINT N/A
2
Get
Instance type
USINT 0
Description
0 = Non existent
1 = Configuring
3 = Established
4 = Timeout
5 = Deferred delete
Explicit messaging connection
15.5.4 Instance 2 (Polled Connection) Attributes
#
1
Access
Get
Name
State
Type Value
USINT N/A
2
Get
Instance type
USINT 1
Anybus Communicator DeviceNet User Manual
Description
0 = Non existent
1 = Configuring
3 = Established
4 = Timeout
I/O Connection
Doc: HMSI-27-305, Rev. 3.12
CIP Object Implementation 76
15.5.5 Instance 3 (Bit-strobe connection) Attributes
#
1
Access
Get
Name
State
Type Value
USINT N/A
2
Get
Instance type
USINT 1
Description
0 = Non existent
1 = Configuring
3 = Established
4 = Timeout
I/O Connection
15.5.6 Instance 4 (COS/Cyclic connection) Attributes
#
1
Access
Get
Name
State
Type Value
USINT N/A
2
3
Get
Get
Instance type
Transport Class trigger
USINT 1
BYTE N/A
4
5
6
Get
Get
Get
Produced Connection ID
UINT
Consumed Connection ID
UINT
Initial Comm Characteristics BYTE
N/A
N/A
0Fh (No ACK)
01h (ACK)
7
Get
Produced Connection Size
8
Get
Consumed Connection Size UINT
0
9
Get/Set
Expected Packet Rate
UINT
0
12 Get
Watchdog timeout action
USINT N/A
13 Get
Produced Connection path
length
Produced Connection Path
UINT
14 Get
15 Get
16 Get
UINT
N/A
0006h
EPATH 20 04 24 66 30 03h
Consumed Connection path UINT 0004h
length
Consumed Connection Path EPATH 20 2B 24 01h
Anybus Communicator DeviceNet User Manual
Description
0 = Non existent
1 = Configuring
3 = Established
4 = Timeout
I/O Connection
Defines the behaviour of the connection
CAN ID for transmission
CAN ID for reception
Produces over message group 1
Does not consume.
Produces over message group 1
Consumes over message group 2
Number of bytes transmitted across
this connection
Number of bytes received across
this connection
Timing associated with this connection
0 = Transition to the timed out state
1 = Auto Delete
2 = Auto Reset
3 = Deferred Delete
Number of bytes in the produced
connection path attribute
Application object producing data
on this connection
Number of bytes in the consumed
connection path length attribute
Specifies the application object(s)
that are to receive the data consumed by this connection object
Doc: HMSI-27-305, Rev. 3.12
CIP Object Implementation 77
15.6 Acknowledge Handler Object, Class 2Bh
15.6.1 General Information
Object Description
Implemented Services
Class services:
Get Attribute Single
Instance services:
Get Attribute Single
Set Attribute Single
15.6.2 Class Attributes
#
1
2
Access
Get
Get
Name
Revision
Max Instance
Type
UINT
UINT
Value
0001h
0001h
Description
Revision 1
Max instance number
15.6.3 Instance Attributes
#
1
Access
Get/Set
Name
Acknowledge Timer
Type
UINT
Value
16
2
Get/Set
Retry Limit
USINT
1
3
Get/Set
Producing connection Instance
UINT
4
4
Get
Ack List Size
Byte
-
5
Get
Ack List
Array of USINT N/A
6
Get
Data with Ack Path List Size
Byte
7
Get
Data with Ack Path List
Array of USINT N/A
-
Description
Time (in ms) to wait for acknowledge before re-sending
Number of ACK timeouts before
retry limit reached event
Connection instance, which contains the path of the producing I/O
application object, which will be
notified of Ack Handler events.
Max. no. of members in Ack list.
0 = Dynamic
List of active connection instance
which are receiving Acks.
Max. no. of members in Data with
Ack Path List. 0 = Dynamic
List of connection instance/consuming application object pairs.
Note: Instance 1 is created when using an ACK:ed COS/Cyclic connection.
Anybus Communicator DeviceNet User Manual
Doc: HMSI-27-305, Rev. 3.12
CIP Object Implementation 78
15.7 Diagnostic Object, Class AAh
15.7.1 General Information
Object Description
This vendor specific object provides diagnostic information from the module.
Implemented Services
Class services:
Get Attribute All
Instance services:
Get Attribute Single
15.7.2 Class Attributes
#
1
Access
Get
Name
Revision
Type
UINT
Value
0001h
Description
Revision 1
15.7.3 Instance Attributes, Instance 01h
#
01h
04h
0Fh
Access
Get
Get
Get
Name
Module serial number
Module Software version
Input I/O Sizea
Input Total Size
Type
UDINT
UINT
UINT
Description
Serial number
DeviceNet Interface software version
IO Size In
11h Get
12h Get
Output I/O Sizea
UINT
UINT
Total size of Input Data area (I/O + Parameter Data)
IO Size Out
14h Get
Output Total Size
UINT
Total size of Output Data area (I/O + Parameter Data)
a. See “IO Sizes” on page 27.
Anybus Communicator DeviceNet User Manual
Doc: HMSI-27-305, Rev. 3.12
CIP Object Implementation 79
15.8 Parameter Data Input Mapping Object, Class B0h
15.8.1 General Information
Object Description
This object can be used to access input data acyclically, and is set up dynamically based on the Parameter
Data Mailbox initialization (see “Parameter Data Initialization (Explicit Data)” on page 82).
See also...
•
“Data Representation on DeviceNet” on page 20
•
“Parameter Data Output Mapping Object, Class B1h” on page 80
•
“Fieldbus Settings” on page 27
•
“Parameter Data Initialization (Explicit Data)” on page 82
Supported Services
Class services:
Get Attribute All
Instance services:
Get Attribute Single
15.8.2 Class Attributes
#
1
Access
Get
Name
Revision
Type
UINT
Value
0001h
Description
Revision 1
15.8.3 Instance Attributes, Instance 01h
Each attribute corresponds to a block of Input Data. Note that the size and location of each block must
be specified using the Anybus Configuration Manager.
For more information, see “Mapping Input Parameter Data to DeviceNet” on page 83.
#
01h
02h
02h
02h
02h
02h
...
32h
Access
Get
Get
Get
Get
Get
Get
...
Get
Name
Data
Data
Data
Data
Data
Data
...
Data
Anybus Communicator DeviceNet User Manual
Type
Array of USINT
Array of USINT
Array of USINT
Array of USINT
Array of USINT
Array of USINT
...
Array of USINT
Description
Mapped block if Input Data
Mapped block if Input Data
Mapped block if Input Data
Mapped block if Input Data
Mapped block if Input Data
Mapped block if Input Data
...
Mapped block if Input Data
Doc: HMSI-27-305, Rev. 3.12
CIP Object Implementation 80
15.9 Parameter Data Output Mapping Object, Class B1h
15.9.1 General Information
Object Description
This object can be used to access output data acyclically, and is set up dynamically based on the Parameter Data Mailbox initialization (see “Parameter Data Initialization (Explicit Data)” on page 82).
See also...
•
“Data Representation on DeviceNet” on page 20”
•
“Parameter Data Input Mapping Object, Class B0h” on page 79
•
“Fieldbus Settings” on page 27
•
“Parameter Data Initialization (Explicit Data)” on page 82
Supported Services
Class services:
Get Attribute All
Instance services:
Get Attribute Single
Set Attribute Single
15.9.2 Class Attributes
#
1
Access
Get
Name
Revision
Type
UINT
Value
0001h
Description
Revision 1
15.9.3 Instance Attributes, Instance 01h
Each attribute corresponds to a block of output data. Note that the size and location of each block must
be specified using the Anybus Configuration Manager.
For more information, see “Mapping Output Parameter Data to DeviceNet” on page 85.
#
01h
02h
03h
04h
05h
06h
...
32h
Access
Get/Set
Get/Set
Get/Set
Get/Set
Get/Set
Get/Set
...
Get/Set
Name
Data
Data
Data
Data
Data
Data
...
Data
Anybus Communicator DeviceNet User Manual
Type
Array of USINT
Array of USINT
Array of USINT
Array of USINT
Array of USINT
Array of USINT
...
Array of USINT
Description
Mapped block of Output Data
Mapped block of Output Data
Mapped block of Output Data
Mapped block of Output Data
Mapped block of Output Data
Mapped block of Output Data
...
Mapped block of Output Data
Doc: HMSI-27-305, Rev. 3.12
Chapter 16
16. Advanced Fieldbus Configuration
16.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. For more information about the Anybus-S platform, consult the Anybus-S Parallel Design Guide.
The standard initialization parameters are determined by the sub-network configuration. Information
about the amount of input and output data used for sub-network communication is used by ACM to
create the configuration message that sets the sizes of the input and output data areas in the Dual Port
RAM of the embedded Anybus-S interface. It is possible to add fieldbus specific mailbox messages to
customize the initialization. This is done in the Mailbox Editor, see below.
(A mailbox message is a HMS specific command structure used for low-level communication with an
Anybus-S interface. Consult the Anybus-S Parallel Design Guide and the fieldbus appendix for the desired fieldbus for further information.)
16.2 Mailbox Editor
To add a mailbox message to the configuration, right-click on
“EndInit” and select “Insert New Mailbox”.
A mailbox message consists of a Header section and a data section where the Header consists of 16 words (32 bytes) and the data
section consists of up to 128 words (256
bytes). All fields are editable except the Message information field that is fixed to 0x4002,
which means that only fieldbus specific mailbox messages can be entered here.
A
B
The mailbox message is presented as two columns; one contains header information (A),
the other one contains the message data (B).
To add message data, simply change the Data
size parameter in the header column (A), and
the corresponding number of bytes will appear in the message data column (B).
For more information about fieldbus specific mailbox messages, consult the separate Anybus-S Fieldbus
Appendix for the fieldbus you are using. For general information about the Anybus-S platform, consult
the Anybus-S Design Guide.
Anybus Communicator DeviceNet User Manual
Doc: HMSI-27-305, Rev. 3.12
Appendix A
A. Parameter Data Initialization (Explicit Data)
A.1 General
The portion of the Input and Output Data declared as Parameter Data cannot be accessed from the network unless it has been properly initialized.
The purpose of this procedure is to specify which data blocks in the Input and Output Data areas to
associate with the instance attributes in the Parameter Data Input Mapping Object and the Parameter
Data Output Mapping Object.
To achieve this, it is required to set up two mailbox messages in the Mailbox Editor of the Anybus Configuration Manager.
For more information about the Mailbox Editor, see “Mailbox Editor” on page 81.
A.2 Add a Mailbox Message
To add a mailbox message to the configuration, rightclick on “EndInit” and select “Insert New Mailbox”.
This causes the following window to appear:
This window, a.k.a. the Mailbox Editor, will be used in the
examples later in this chapter.
Anybus Communicator DeviceNet User Manual
Doc: HMSI-27-305, Rev. 3.12
Parameter Data Initialization (Explicit Data) 83
A.3 Mapping Input Parameter Data to DeviceNet
Example
In the following example, a total of 160 bytes of data will be mapped to the Parameter Data Input Mapping Object. The data is made up of 5 separate data blocks, each associated with a particular instance
attribute.
To achieve this, perform the following steps:
1. Add a new mailbox message to the configuration (see “Add a Mailbox Message” on page 82).
2. Change the “Command”-value in the mailbox header to 0004h.
3. Adjust the “Data Size”-value in the mailbox header (left column). In this example, the size shall
be set to 20 (0014h), since each mapped attribute occupies 4 bytes of mailbox data.
4. Specify the mapping locations for the attributes in the mailbox data section. As mentioned above,
each mapping entry needs 4 bytes; two bytes specifying the offset1 of the data block, followed by
two bytes which specify the length of the data block. Note that these values must be entered in big
endian (Motorola) format.
In this example, this gives us the following mailbox data:
Mailbox Data
Location
0x00
0x01
0x02
0x03
0x04
0x05
0x06
0x07
0x08
0x09
0x0A
0x0B
0x0C
0x0D
0x0E
0x0F
0x10
0x11
0x12
0x13
Data
0x00
0x00
0x00
0x20
0x00
0x40
0x00
0x40
0x00
0x80
0x00
0x10
0x00
0x90
0x00
0x20
0x00
0xF0
0x00
0x10
Attribute no.
Comments
1
Offset = 0000h
Size = 32 bytes
2
Offset = 0040h
Size = 64 bytes
3
Offset = 0080h
Size = 16 bytes
4
Offset = 0090h
Size = 32 bytes
5
Offset = 00F0h
Size = 16 bytes
As shown in the table above, the attributes are numbered in the order they are mapped, i.e. it is
possible to rearrange the attribute numbering by physically changing the mapping order in the
mailbox data.
5. To save the new mailbox, select “Apply changes” in the “File”-menu.
1. The offset is specified from the start of the parameter data, not from the physical memory location in the
Anybus Communicator.
Anybus Communicator DeviceNet User Manual
Doc: HMSI-27-305, Rev. 3.12
Parameter Data Initialization (Explicit Data) 84
Resulting Attribute Mapping
Input Data
0x000
Parameter Data
Input Mapping Object
I/O Data (Input)
Attributes:
IO Size In
(256 bytes)
#1 - Revision
Instance #1
Attributes:
#1 - Data
#2 - Data
#3 - Data
#4 - Data
#5 - Data
0x0FF
0x100
32 bytes
Offset 0x0000h
(not mapped)
64 bytes
16 bytes
32 bytes
(not mapped)
0x1FF
16 bytes
Offset 0x00FFh
Mailbox Editor Screenshot
Anybus Communicator DeviceNet User Manual
Doc: HMSI-27-305, Rev. 3.12
Parameter Data Initialization (Explicit Data) 85
A.4 Mapping Output Parameter Data to DeviceNet
Example
Mapping output data is similar to mapping input data; in the following example, a total of 144 bytes of
data will be mapped to the Parameter Data Output Mapping Object. The data is made up of 4 separate
blocks, each associated with a a particular instance attribute.
To achieve this, perform the following steps:
1. Add a new mailbox message to the configuration (see “Add a Mailbox Message” on page 82).
2. Change the “Command”-value in the mailbox header to 0005h.
3. Adjust the “Data Size”-value in the mailbox header (left column). In this example, the size shall
be set to 16 (0010h), since each mapped attribute occupies 4 bytes of mailbox data.
4. Specify the mapping locations for the attributes in the mailbox data section. As mentioned above,
each mapping entry needs 4 bytes; two bytes specifying the offset1 of the data block, followed by
two bytes which specify the length of the data block. Note that these values must be entered in big
endian (Motorola) format.
In this example, this gives us the following mailbox data:
Mailbox Data
Location
0x00
0x01
0x02
0x03
0x04
0x05
0x06
0x07
0x08
0x09
0x0A
0x0B
0x0C
0x0D
0x0E
0x0F
Data
0x00
0x20
0x00
0x10
0x00
0x50
0x00
0x20
0x00
0x70
0x00
0x20
0x00
0xD0
0x00
0x40
Attribute no.
Comments
1
Offset = 0020h
Size = 16 bytes
2
Offset = 0050h
Size = 32 bytes
3
Offset = 0070h
Size = 32 bytes
4
Offset = 00D0h
Size = 64 bytes
As shown in the table above, the attributes are numbered in the order they are mapped, i.e. it is
possible to rearrange the attribute numbering by physically changing the mapping order in the
mailbox data.
5. To save the new mailbox, select “Apply changes” in the “File”-menu.
1. The offset is specified from the start of the Parameter Data, not from the physical memory location in the
Anybus Communicator.
Anybus Communicator DeviceNet User Manual
Doc: HMSI-27-305, Rev. 3.12
Parameter Data Initialization (Explicit Data) 86
Resulting Attribute Mapping
Output Data
0x200
I/O Data (Output)
Parameter Data
Output Mapping Object
0x27F
0x280
Attributes:
#1 - Revision
(not mapped)
IO Size Out
(128 bytes)
Offset 0x0000h
16 bytes
Instance #1
(not mapped)
Attributes:
#1 - Data
#2 - Data
#3 - Data
#4 - Data
32 bytes
32 bytes
(not mapped)
64 bytes
(not mapped)
0x3FF
Offset 0x017Fh
Mailbox Editor Screenshot
Anybus Communicator DeviceNet User Manual
Doc: HMSI-27-305, Rev. 3.12
Appendix B
B. Connector Pin Assignments
B.1 DeviceNet Connector
Pin
1
2
3
4
Signal
VCAN L
Shield
CAN H
Description
DeviceNet bus power, negative supply voltage
Can L bus line
Cable shield
CAN H bus line
5
V+
DeviceNet bus power, positive supply voltage
1
5
B.2 Power Connector
Pin
1
2
Description
+24 VDC
GND
1
2
Notes:
•
Use 60/75 or 75 °C copper (Cu) wire only.
•
Minimum terminal tightening torque: 5–7 lb-in (0.5–0.8 Nm).
Anybus Communicator DeviceNet User Manual
Doc: HMSI-27-305, Rev. 3.12
Connector Pin Assignments 88
B.3 PC Connector
Configuration Cable Wiring
DP9F (PC)
RJ11 (ABC)
1
1
Ground
RS232 Rx
2
2
Ground
RS232 Tx
3
3
Rx
4
4
Tx
Ground
5
6
7
8
9
RJ11 (4P4C modular)1 : ABC
Pin
1
2
3
4
Description
Signal ground
4
RS232 Rx (Input)
RS232 Tx (Output)
3
2
1
DB9F : PC
Pin
1
2
3
4
5
6-9
Description
RS232 Rx (Input)
RS232 Tx (Output)
Signal Ground
-
5 (female) 1
9
6
1. The RJ11 (4P4C modular) is sometimes referred to as an RJ9.
Anybus Communicator DeviceNet User Manual
Doc: HMSI-27-305, Rev. 3.12
Connector Pin Assignments 89
B.4 Subnetwork Interface
B.4.1 General Information
The subnetwork interface provides for RS232, RS422 and RS485 communications. Depending on the
configuration specified in the Anybus Configuration Manager, different signals are activated in the subnetwork connector.
B.4.2 Bias Resistors (RS485 Only)
When idle, RS485 enters an indeterminate state, which may cause the serial receivers to pick up noise
from the serial lines and interpret this as data. To prevent this, the serial lines should be forced into a
known state using pull-up and pull-down resistors, commonly known as bias resistors.
The bias resistors form a voltage divider, forcing the voltage between the differential pair to be higher
than the threshold for the serial receivers, typically >200 mV.
Note that bias resistors shall only be installed on one node; installing bias resistors on several nodes may
compromise the signal quality on the network and cause transmission problems.
B.4.3 Termination (RS485 & RS422 Only)
To avoid reflections on the serial lines, it is important to properly terminate the subnetwork by placing
termination resistors between the serial receivers near the end nodes.
The resistor value should ideally match the characteristic impedance of the cable, typically 100–120 Ω.
B.4.4 Connector Pinout (DB9F)
Pin
1
2
3
4
Description
+5 V Output (100 mA max)
RS232 Rx
RS232 Tx
(reserved)
5
Signal Grounda
RS422 Rx +
RS422 Rx RS485 + / RS422 Tx+
RS485 - / RS422 TxCable Shield
6
7
8
9
(housing)
RS232



RS422

RS485

RS485
5 (female) 1









9
6



a. Connecting this signal directly to Protective Earth (PE) of other nodes may, in case of grounding loops etc., cause
damage to the on-board serial transceivers. It is therefore generally recommended to connect it only to Signal
Ground (if available) of other nodes.
Anybus Communicator DeviceNet User Manual
Doc: HMSI-27-305, Rev. 3.12
Connector Pin Assignments 90
B.4.5 Typical Connection (RS485)
+5V
470R
RS485 +
RS485 +
120R
120R
RS485 -
RS485 470R
Signal
Ground
Signal
Ground
Node
RS485 +
RS485 -
Signal
Ground
Node
RS485 +
RS485 -
Signal
Ground
Node
RS485 +
RS485 -
Signal
Ground
Node
RS485 +
Anybus Communicator
RS485 -
Signal
Ground
Cable
Shield
End Node
B.4.6 Typical Connection (RS422 & 4-Wire RS485)
+5V
470R
RS422 Rx+
RS422 Tx+
120R
RS422 Rx-
RS422 Tx470R
470R
RS422 Tx+
RS422 Rx+
120R
RS422 Tx-
RS422 Rx470R
Signal
Ground
Signal
Ground
Cable
Shield
Anybus Communicator
Device
Note: Bias resistors are normally not needed on RS422, but may be required when using 4-wire RS485.
B.4.7 Typical Connection (RS232)
RS232 Tx
RS232 Rx
RS232 Rx
RS232 Tx
Signal
Ground
Signal
Ground
Cable
Shield
Anybus Communicator
Anybus Communicator DeviceNet User Manual
Device
Doc: HMSI-27-305, Rev. 3.12
Appendix C
C. Technical Specification
C.1 Mechanical Properties
Housing
Plastic housing with snap-on connection to DIN-rail, protection class IP20.
Dimensions (L x W x H)
120 mm x 75 mm x 27 mm (4.72” x 2.95” x 1.06”)
C.2 Electrical Characteristics
Power Supply
Power: 24 VDC ± 10%
Power Consumption
Maximum power consumption is 280 mA on 24 VDC. Typically around 100 mA.
C.3 Environmental Characteristics
Relative Humidity
The product is designed for a relative humidity of 0 to 95 % non-condensing.
Temperature
Operating:
Non-operating:
0 °C to +55 °C
-25 °C to +85 °C
Anybus Communicator DeviceNet User Manual
Doc: HMSI-27-305, Rev. 3.12
Technical Specification 92
C.4 Regulatory Compliance
EMC Compliance (CE)
This product is in accordance with the EMC directive 89/336/EEC, with amendments 92/31/EEC and
93/68/EEC through conformance with the following standards:
•
EN 50082-2 (1993)
EN 55011 (1990) Class A
•
EN 61000-6-2 (1999)
EN 61000-4-3 (1996) 10 V/m
EN 61000-4-6 (1996) 10 V/m (all ports)
EN 61000-4-2 (1995) ±8 kV air discharge, ±4 kV contact discharge
EN 61000-4-4 (1995) ±2 kV power port, ±1 kV other ports
EN 61000-4-5 (1995) ±0.5 kV power ports (DM/CM), ±1 kV signal ports
UL/c-UL Compliance
IND: CONT. EQ.
FOR HAZ LOC.
CL I, DIV 2
GP A,B,C,D
TEMP
CODE
E203225
WARNING - EXPLOSION HAZARD - SUBSTITUTION OF ANY COMPONENTS
MAY IMPAIR SUITABILITY FOR CLASS I, DIVISION 2.
WARNING - EXPLOSION HAZARD - WHEN IN HAZARDOUS LOCATIONS,
TURN OFF POWER BEFORE REPLACING OR WIRING MODULES.
WARNING - EXPLOSION HAZARD - DO NOT DISCONNECT EQUIPMENT
UNLESS POWER HAS BEEN SWITCHED OFF OR THE AREA IS KNOWN TO
BE NON-HAZARDOUS.
ATTENTION – RISQUE D’EXPLOSION – LE REMPLACEMENT DE TOUT
COMPOSANTS INVALIDE LA CERTIFICATION CLASS I, DIVISION 2.
ATTENTION – RISQUE D’EXPLOSION – EN ZONE EXPLOSIVE, VEUILLEZ
COUPER L’ALIMENTATION ÉLECTRIQUE AVANT LE REMPLACEMENT OU LE
RACCORDEMENT DES MODULES.
ATTENTION – RISQUE D’EXPLOSION – NE PAS DÉCONNECTER
L’ÉQUIPEMENT TANT QUE L’ALIMENTATION EST TOUJOURS PRÉSENTE OU
QUE LE PRODUIT EST TOUJOURS EN ZONE EXPLOSIVE ACTIVE.
Anybus Communicator DeviceNet User Manual
Doc: HMSI-27-305, Rev. 3.12
Technical Specification 93
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.
•
Secondary circuit intended to be supplied from an isolating source and protected by overcurrent
protective devices installed in the field sized per the following:
Control circuit wire size
AWG
mm²
22
0.32
20
0.52
18
0.82
16
1.3
14
2.1
12
3.3
Maximum protective device rating
Amperes
3
5
7
10
20
25
Galvanic isolation on sub-network interface
•
EN 60950-1 (2001)
Pollution Degree 2
Material Group IIIb
250 VRMS or 250 VDC working voltage
500 V secondary circuit transient rating
CIP Product Compliance
Anybus Communicator DeviceNet User Manual
Doc: HMSI-27-305, Rev. 3.12
Appendix D
D. Troubleshooting
Problem
Problem during configuration Upload / Download.
The Config Line “LED” turns red in ACM.
The serial port seems to be available, but it is not possible
to connect to the gateway
Poor performance
No sub-network functionality
Anybus Communicator DeviceNet 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.
Try again
• Select another serial port
Try again
• Right click “sub-network” in the Navigation window and
select “sub-network Status” to see status / diagnostic
information about the sub-network.
If the gateway reports very many retransmissions, check
your cabling and/or try a lower baud rate setting for the
sub-network (if possible).
• Is the Subnet Monitor in ACM active?
The sub-network monitor has a negative influence on the
overall performance of the gateway, and should only be
used when necessary.
• Is the Node Monitor in ACM active?
The node monitor has a negative influence on the overall
performance of the gateway, and should only be used
when necessary.
• Use the “Data logger”-functionality to record the serial
data communication on the sub-network.
• If no data is being transmitted, check the configuration in
ACM.
• If no data is received, check the sub-network cables. Also
verify that the transmitted data is correct.
Doc: HMSI-27-305, Rev. 3.12
Appendix E
E. ASCII Table
x0
x1
x2
x3
x4
x5
x6
x7
x8
x9
xA
xB
xC
xD
xE
xF
BS
8
HT
9
LF
10
VT
11
FF
12
CR
13
SO
14
SI
15
FS
28
GS
29
RS
30
US
31
0x
NUL SOH STX ETX EOT ENQ ACK BEL
0
1
2
3
4
5
6
7
1x
DLE DC1 DC2 DC3 DC4 NAK SYN ETB CAN
16
17
18
19
20
21
22
23
24
EM
25
2x
(sp)
32
!
33
"
34
#
35
$
36
%
37
&
38
'
39
(
40
)
41
*
42
+
43
,
44
45
.
46
/
47
3x
0
48
1
49
2
50
3
51
4
52
5
53
6
54
7
55
8
56
9
57
:
58
;
59
<
60
=
61
>
62
?
63
4x
@
64
A
65
B
66
C
67
D
68
E
69
F
70
G
71
H
72
I
73
J
74
K
75
L
76
M
77
N
78
O
79
5x
P
80
Q
81
R
82
S
83
T
84
U
85
V
86
W
87
X
88
Y
89
Z
90
[
91
\
92
]
93
^
94
_
95
6x
`
96
a
97
b
98
c
99
d
100
e
101
f
102
g
103
h
104
i
105
j
106
k
107
l
108
m
109
n
110
o
111
7x
p
112
q
113
r
114
s
115
t
116
u
117
v
118
w
119
x
120
y
121
z
122
{
123
|
124
}
125
~
126
DEL
127
Anybus Communicator DeviceNet User Manual
SUB ESC
26
27
Doc: HMSI-27-305, Rev. 3.12
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertisement