ABC COP User Manual 3 01 SCM-1200-099
ABC COP User Manual 3 01 SCM-1200-099
ABC COP User Manual 3 01 SCM-1200-099
Connecting DevicesTM
+$/067$'&+,&$*2.$5/658+(72.<2%(,-,1*0,/$1208/+286(&29(175<381(&23(1+$*(1
Liability
Every care has been taken in the preparation of this manual. Please inform HMS Industrial Networks AB of any
inaccuracies or omissions. The data and illustrations found in this document are not binding. We, HMS Industrial
Networks AB, reserve the right to modify our products in line with our policy of continuous product development.
The information in this document is subject to change without notice and should not be considered as a commit-
ment by HMS Industrial Networks AB. HMS Industrial Networks AB assumes no responsibility for any errors that
may appear in this document.
There are many applications of this product. Those responsible for the use of this device must ensure that all the
necessary steps have been taken to verify that the applications meet all performance and safety requirements in-
cluding any applicable laws, regulations, codes, and standards.
HMS Industrial Networks AB will under no circumstances assume liability or responsibility for any problems that
may arise as a result from the use of undocumented features, timing, or functional side effects found outside the
documented scope of this product. The effects caused by any direct or indirect use of such aspects of the product
are undefined, and may include e.g. compatibility issues and stability issues.
The examples and illustrations in this document are included solely for illustrative purposes. Because of the many
variables and requirements associated with any particular implementation, HMS Industrial Networks AB cannot
assume responsibility for actual use based on these examples and illustrations.
HMS Industrial Networks AB has intellectual property rights relating to technology embodied in the product de-
scribed in this document. These intellectual property rights may include patents and pending patent applications
in the US and other countries.
Trademark Acknowledgements
Anybus ® is a registered trademark of HMS Industrial Networks AB. 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 prod-
uct. Failure to observe this may cause damage to the product.
Table of Contents
Chapter 5 Nodes
General..................................................................................................................................................... 33
Adding & Managing Nodes.................................................................................................................. 33
Node Parameters.................................................................................................................................... 33
Master Mode and Generic Data Mode........................................................................................... 33
Chapter 6 Transactions
General..................................................................................................................................................... 34
Adding & Managing Transactions ....................................................................................................... 35
Transaction Parameters (Master Mode).............................................................................................. 36
Parameters (Query & Broadcast)................................................................................................... 36
Parameters (Response).................................................................................................................... 38
Transaction Parameters (Generic Data Mode).................................................................................. 38
Produce-Transactions ..................................................................................................................... 38
Consume-Transactions ................................................................................................................... 39
Transaction Editor ................................................................................................................................. 40
Chapter 8 Commands
General..................................................................................................................................................... 47
Adding & Managing Commands ......................................................................................................... 47
Pull-Down Menu........................................................................................................................... 48
Toolbar Icons ................................................................................................................................. 48
The Command Editor ........................................................................................................................... 49
General.......................................................................................................................................... 49
Basic Navigation ........................................................................................................................... 49
Pull-down Menu ............................................................................................................................ 50
Editing a Command ...................................................................................................................... 51
Example: Specifying a Modbus-RTU Command in Master Mode ................................................. 52
Appendix C Troubleshooting
Related Documents
Document name Author
ABC-COP Installation Leaflet HMS
Anybus-S CANopen Fieldbus Appendix HMS
CiA Draft Standard 301 v4.02 CAN in Automation
DF1 Protocol and Command Set - Reference Manual, 1770-6.5.16, October 1996 Allen-Bradley
Document History
Change Page(s)
Updated software name “Anybus Config Tool” to “Anybus Configuration Manager” -
Changed the number of possible transactions 34
Updated information about the trigger byte 39
Updated information about the CRC-algorithm 46
Updated frontpage information -
Updated sales and support page -
Updated System Requirements for Anybus Configuration Manager 15
Revision List
Glossary
Term Meaning
ABC
Anybus Communicator™
Gateway
Broadcaster A protocol-specific node in the configuration that handles transactions destined to all nodes.
COP CANopen
Command A predefined transaction.
Configuration List of configured nodes with transactions on the subnetwork.
Fieldbus The higher level network to which the Anybus Communicator is connected.
Fieldbus Control System Fieldbus master
Frame Object Low level entities which are used to describe the different parts of a transaction.
Monitor A tool for debugging the Anybus Communicator and the network connections.
Node 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
Subnetwork
which the Anybus Communicator acts as a gateway.
Transaction A generic building block that is used in the subnetwork configuration and defines the data that
is sent and received on the subnetwork.
User Person or persons responsible for installing the Anybus Communicator
Higher Level Network In this case, CANopen
Network
Fieldbus
(CANopen Network)
HMI HMI
INVERTER INVERTER
PC configuration PC configuration
and monitoring and monitoring
Multi-drop up to 31 nodes
Subnetwork
The gateway can address up to 31 nodes, and supports the following physical standards:
• RS-232
• RS-422
• RS-485
CANopen Interface
CANopen connectivity is provided through patented Anybus technology; a proven industrial commu-
nication solution used all over the world by leading manufacturers of industrial automation products.
• Galvanically isolated bus electronics
• Supports all standard baudrates
• Customizable PDO mapping
• Up to 512+512 bytes of slow I/O
• Up to 80 RPDO’s and 80 TPDO’s
• Transmission types: PDO Sync, Change-of-state, Event based and RTR
• Network store/restore functionality
• Heartbeat & Node Guarding support
A: CANopen Connector
This connector is used to connect the gateway to the field-
bus.
See also...
- “CANopen Connector” on page 81 C
B
B: Configuration Switches
See also...
- “Configuration Switches” on page 13 A
C: Status LEDs
See also...
- “Status LEDs” on page 12 D
D: PC Connector
E G
This connector is used to connect the gateway to a PC for
configuration and monitoring purposes.
F
See also...
- “Hardware Installation” on page 14
- “PC Connector” on page 82
E: Subnetwork Connector
This connector is used to connect the gateway to the serial subnetwork.
See also...
- “Hardware Installation” on page 14
- “Subnetwork Interface” on page 83
F: Power Connector
This connector is used to apply power to the gateway.
See also...
- “Hardware Installation” on page 14
- “Power Connector” on page 81
- “Technical Specification” on page 85
G: DIN-rail Connector
The DIN-rail mechanism connects the gateway to PE (Protective Earth).
See also...
- “Hardware Installation” on page 14
B
The node address is configured using two rotary switches as follows: C
Example: To set node address 42, set switch A to ‘2’ and switch B to ‘4’.
The baudrate is set via switch C, and is interpreted as follows:
# Baudrate # Baudrate
0 (reserved) 5 250 kbit/s
1 10 kbit/s 6 500 kbit/s
2 20 kbit/s 7 800 kbit/s
3 50 kbit/s 8 1 Mbit/s
4 125 kbit/s 9 (reserved)
1. Snap the gateway on to the DIN-rail (See “External View” on page 11)
The DIN-rail mechanism works as follows:
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)
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
System requirements
• Pentium 133 MHz or higher
• 650 MB of free space on the hard drive
• 32 MB RAM
• Screen resolution of 800x600 (16 bit color) or higher
• Microsoft Windows™ 2000 / XP / Vista / 7 (32 bit)
• Internet Explorer 4.01 SP1 or newer
Installation
• From website
Download and execute the self-extracting .exe-file from the HMS website (www.anybus.com).
Each device on CANopen is associated with an Electronic Data Sheet (a.k.a .EDS-file), which holds a
description of the device and its functions. Most importantly, the file describes the object dictionary im-
plementation in the device.
The latest version of the .EDS-file for the Anybus Communicator for CANopen can be downloaded
from the HMS website, www.anybus.com.
2. Basic Operation
2.1 General
The Anybus Communicator is designed to exchange data between a serial subnetwork and a higher level
network. Unlike most other gateway devices of similar kind, it does not have a fixed protocol for the
subnetwork, 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 cer-
tain aspects of the subnetwork communication and notify the higher level network when data has
changed.
An essential part of the Anybus Communicator package is the Anybus Configuration Manager, a Win-
dows™ application which is used to supply the gateway with a description of the subnetwork protocol.
No programming skills are required; instead, a visual protocol description-system is used to specify the
different parts of the serial communication.
Subnetwork
• Input Data (512 bytes)
This area can be read by the higher level net-
work.
(how this data is represented on the higher level
network will be described later in this chapter). General Data
• 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 han-
dle up to 1024 bytes of general data.
When building the subnetwork configuration using the Anybus Configuration Manager, the different ar-
eas described above are mapped to the memory locations (addresses) specified below.
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 gateway.
CANopen
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.
ABC
Input Data Output Data General Data
0x000 0x200 0x400
The gateway 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 spec-
ifies 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 20.
The following building blocks are used in Anybus Configuration Manager to describe the subnetwork
communication. How these blocks apply to the three protocol modes will be described later in this doc-
ument.
• Node
A node represents a single device on the subnetwork. Each node can be associated with a
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 Man-
ager. This simplifies common operations by allowing transactions to be stored and reused.
• Frame Object
‘Frame objects’ are low level entities used to compose a transaction (see above). A frame object
can represent a fixed value (a constant), a range of values (limit objects), a block of data or a cal-
culated checksum.
In this mode, the communication is based on a query-response scheme; when the gateway issues a query
on the subnetwork, the addressed node is expected to issue a response to that query. Nodes are not per-
mitted to issue responses spontaneously, i.e. without first receiving a query.
There is one exception to this rule; the broadcaster. Most protocols offer some way of broadcasting mes-
sages to all nodes on the network, without expecting them to respond to the broadcasted message. This
is also reflected in the 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 Config-
uration Manager and selecting ‘Insert New Command’. Note however that this does not in any way pre-
vent other protocols based on the same query-response message-scheme to be implemented.
In this mode, there is no master-slave relationship between the nodes on the subnetwork and the gate-
way. 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.
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 subnet-
work to be ‘consumed’ by a node.
2.4.1 General
The Anybus Communicator acts as a slave on the CANopen network. As such, it does not initiate com-
munication towards other nodes by itself, but can be read from/written to by a CANopen master.
On CANopen, the input and output data areas are represented as object entries in the manufacturer spe-
cific range (2000h...5FFFh). Separate object ranges are used for byte, word, and double-word access.
A portion of these objects may be exchanged as Process Data Objects (PDO). The gateway supports up
to 80 RPDOs and 80 TPDOs, each capable of carrying up to 8 bytes of data.
Which objects that can be exchanged this way depend on two factors:
• PDO Mapping
The objects that shall be exchanged as PDOs on the bus are specified (i.e. mapped) by the net-
work configuration tool.
If no mapping has been specified, the gateway defaults to the following mapping scheme:
For more information about the object dictionary implementation, see “Object Dictionary Implemen-
tation” on page 74.
The I/O sizes specified in Anybus Configuration Manager correlate 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= 128 bytes(0x0080)
IO Size Out= 32 bytes(0x0020)
0x07F
0x080
See also...
• “Data Representation” on page 22
• “Object Dictionary Implementation” on page 74
• “Fieldbus Settings” on page 29
This section is the main tool for selecting and altering dif-
ferent levels of the subnetwork configuration.
Entries preceded by a ‘+’ holds further configuration pa- This menu entry holds additional
rameters or ‘sub menus’. To gain access to these parame- sub-entries / parameters
ters, the entry must be expanded by clicking ‘+’.
There are three main levels in the navigation window,
namely Fieldbus, ABC and subnetwork.
Right-clicking on entries in this section brings out addi-
tional 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 selec-
tion box or manually, depending on the parameter itself.
Values can be specified in decimal form (e.g. ‘42’), or in Parameter Section
hexadecimal format (e.g. ‘0x2A’).
• D: Information Section
This section holds information related to the currently se-
lected parameter.
Information Section
File
This menu features the following entries:
• New
Create a new configuration.
See also “Configuration Wizards” on page 67.
• 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...
This brings out the following window:
Item Description
Select a Name for the A name for the configuration
Configuration may be entered here
Download Password(6) These fields can be used to
Upload Password(6) password-protect the configu-
ration in the gateway.
• Exit
Close the Anybus Configuration Manager.
Tools
This menu features the following entries:
• Port
This entry selects the COM-port used
for the configuration of the gateway.
• Start Logging
Start the Data Logger (see “Data Logger” on page 65).
Note that when the Data Logger is active, this menu entry is changed to ‘Stop Logging’.
• Options
This will bring out the following window:
Item Description
Warning on Delete A confirmation dialog is displayed each
time something is deleted.
Warning on unsaved A confirmation dialog is displayed when
data closing the Anybus Configuration Man-
ager with unsaved data.
Show Wizard when The Wizard is displayed each time a new
“New” menu is selected configuration is created.
Language next time the Selects which language to use. The new
program is launched setting will be active the next time the pro-
gram is launched.
Item Description
Size of logbuffer 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
65.
Firmware Download Download firmware to the embedded field-
bus interface.
Warning: Use with caution.
Factory Restore Restores the gateway firmware to it’s orig-
inal state (does not affect the embedded
fieldbus interface).
Block Configuration When selected, the downloaded configu-
ration will not be executed by the gateway.
Warning: Use with caution.
Create Error log Creates an error log file
View
This menu features the following entries:
• Toolbar
This entry enables/disables the toolbar icons at the top of the
main window.
• Status Bar
This entry enables/disables the status bar at the bottom of the
main window.
Help
This menu features the following entries:
• Contents
Display the table of contents of the online help
system.
Note: At the time of writing, no online help sys-
tem exists.
• About...
Display general information about the gateway and the current build of Anybus Configuration
Manager.
The toolbar features icons for the most commonly used functions.
• Up one Level
Clicking on this icon will move the selection in the navigation section.
Up one Level
• Connect
Clicking on this icon will cause the Anybus Configuration Manager to attempt to
connect to the gateway. Connect
• Disconnect
Clicking on this icon will cause the Anybus Configuration Manager to disconnect
from the gateway. Disconnect
• Subnetwork Monitor
Clicking on this icon will launch the subnetwork Monitor
(see “Subnetwork Monitor” on page 60). 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 80)
Add Mailbox
• Node Monitor
Clicking on this icon will launch the Node Monitor (see “Node Monitor” on
page 61) Node Monitor
• Add Transaction(s)
These icons are used to add transactions to the currently selected node.
Add Add
Transactions Transaction
4. Basic Settings
General
During start-up the fieldbus interface of the gateway is initialized to fit the configuration created in the
Anybus Configuration Manager. Optionally, some initialization parameters can be set manually to pro-
vide better control over how the data shall be treated by the gateway.
Fieldbus Type
The Anybus Configuration Manager supports a wide range of net-
working systems. Make sure that this parameter is set to ‘CAN-
open’.
• Automatic
All data can be exchanged both cyclically and acyclically.
See also...
I/O Sizes
- “Data Representation on CANopen” on page 22
• User defined
Additional parameter properties appear; ‘IO Size In’ and ‘IO Size Out’. The specified amount,
starting at address 0x0000 of the respective memory buffers, can be exchanged both cyclically
and acyclically. The remainder will only be exchanged acyclically.
See also...
- “Data Representation on CANopen” on page 22
Note: Excessive I/O sizes may have a negative influence on the overall performance of the gateway. It
is therefore generally recommended to set the I/O sizes manually instead of using the ‘Automatic’-op-
tion.
Interface
Currently, only serial communication is supported.
Value Description
Enabled Enable the Control and Status Registers. The ‘Data Valid’-bit in the Control Register must
be set to start the subnetwork communication.
Enabled but no startup lock This setting is similar to ‘Enabled’, except that the control system is not required to set the
‘Data Valid’-bit to start the subnetwork communication.
Disabled 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 Description
Enabled The gateway will be restarted, and no error will be indicated to the user.
Disabled The gateway will halt and indicate an error.
Protocol Mode
This parameter specifies which protocol mode to use for the subnetwork.
Value Description
Generic Data Mode 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 subnetwork.
Master Mode This mode is intended for ‘Query & Response’-based protocols, where a single Master
exchanges data with a number of Slaves.
DF1 This mode is intended for the DF1 protocol. The Anybus Communicator can only be con-
figured 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 ex-
changed on the subnetwork. This feature is primarily intended for debugging purposes.
Communication
These parameters specify the actual communication settings used for the subnetwork.
• Master Mode
The Message Delimiter specifies the time that separates two messages in steps of 10ms. 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).
5. Nodes
5.1 General
In Anybus Configuration Manager, a node represents a single device on the network. While the gateway
doesn’t feature a scanlist in the traditional sense, all nodes, and their transactions, will be processed in
the order they have been defined in the Anybus Configuration Manager.
The maximum number of nodes that can be created in the Anybus Configuration Manager is 31.
Function Description
Paste Paste a node from the clipboard
Subnetwork Monitor Launch the subnet monitor ( “Subnetwork Monitor” on page
60)
Add Node Add a node to the configuration
Add Broadcastera Add a broadcaster node to the configuration
Load Node Add a previously saved node
Subnetwork Status... View diagnostic information about the subnetwork
a. This function is only available in Master Mode.
(To gain access to the parameters described in this section, select a node
in the Navigation Section).
Parameter Description
Slave Address The value entered here may be used to set the node address in
certain commands.
For more information, see “The Command Editor” on page 49.
6. Transactions
6.1 General
As mentioned previously, transactions are representations of the actual serial telegrams exchanged on
the serial subnetwork. While the gateway doesn’t feature a scanlist in the traditional sense, all nodes, and
their transactions, will be processed in the order they have been defined in the Anybus Configuration
Manager.
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 subnetwork. The Broadcaster can
only send transactions.
Function Description
Cut Cut a node to the clipboard
Copy Copy a node to the clipboard
Insert Insert a node from the clipboard
Delete Delete a node
Node Monitor Launch the node monitor ( “Node Monitor” on page 61)
Add Transaction(s) a 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 Transaction Consumeb Add a ‘Consume’-transaction
Add transaction Produceb Add a ‘Produce’-transaction
Add Command Add predefined transactions to the node
Insert New Node Insert a new node above the currently selected one
Save Node Save the selected node
Insert from File Insert a previously saved node above the currently
selected node
Rename To increase readability, each node can be given a
unique name using this function
a. Only available in Master Mode
b. Only available in Generic Data Mode
(To gain access to these parameters, select a Query- or Broadcast- transaction in the Navigation Section)
Parameter Description
Minimum time between This parameter specifies how long the gateway shall wait after transmitting a broadcast trans-
broadcasts (10 ms) action 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. For instance, an entered value of 5 results in 50 ms.
Note: This setting is only relevant for the Broadcaster node.
Offline options for field- This parameter specifies the action to take for this transaction if the higher level network goes
bus offline. This affects the data that is sent to the subnetwork.
• Clear - The data destined for the slave-devices is cleared (set to zero)
• Freeze - The data destined for the slave-device is frozen
• NoScanning -The updating of the subnetwork is stopped
Offline options for sub- This parameter specifies the action to take for this transaction if the subnetwork goes offline.
network This affects the data that is reported to the control system.
• Clear - Data is cleared (0) on the higher level network if the subnetwork goes offline
• Freeze - Data is frozen on the higher level network if the subnetwork goes offline
Reconnect time (10 ms) This parameter specifies how long the gateway shall wait before attempting to reconnect a dis-
connected node. A node will be disconnected in case the maximum number of retries (below)
has been reached.
The entered value is multiplied by 10. For instance, an entered value of 5 results in 50 ms.
Note: This setting is not relevant for the Broadcaster node.
Retries This parameter specifies how many times a timeout may occur in sequence before the node is
disconnected.
Timeout time (10 ms) 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. For instance, an entered value of 5 results in 50 ms.
Trigger byte address 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... 0x3FF and 0x400... 0xNNN
Update mode 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 transac-
tion 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 spec-
ified by the ‘Trigger byte address’ parameter.
Parameter Description
Update time (10 ms) This parameter specifies how often the transaction will be issued in steps of 10 ms (only rele-
vant when ‘Update mode’ is set to ‘Cyclically’).
The entered value is multiplied by 10. For instance, an entered value of 5 results in 50 ms.
(To gain access to these parameters, select a Response-transaction in the Navigation Section)
Parameter Description
Trigger byte 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 subnetwork. 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.
Trigger byte address This parameter specifies the location of the trigger byte in the internal memory buffer.
Valid settings range from 0x000... 0x1FF and 0x400... 0xNNN
6.4.1 Produce-Transactions
(To gain access to these parameters, select a Produce Transaction in the Navigation Section)
Parameter Description
Offline options for fieldbus 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 subnetwork.
• Clear
Data is cleared (0) on the subnetwork if the higher level network goes offline
• Freeze
Data is frozen on the subnetwork if the higher level network goes offline
• NoScanning
Stop subnet scanning for this transaction if the higher level network goes offline
Update mode The update mode for the transaction:
• Cyclically
The transaction is sent cyclically at the interval specified in the ‘Update Time’-param-
eter.
• 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
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.
Update time (10 ms) This parameter specifies how often the transaction will be issued in steps of 10ms (only
relevant when ‘Update mode’ is set to ‘Cyclically’).
The entered value is multiplied by 10. For instance, an entered value of 5 results in 50 ms.
Parameter Description
Trigger byte address 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 subnetwork.
This way, the control system can instruct the gateway to produce a specific transaction on
the subnetwork 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... 0x3FF and 0x400... 0xNNN
6.4.2 Consume-Transactions
(To gain access to these parameters, select a Consume Transaction in the Navigation Section)
Parameter Description
Offline options for subnet- This parameter specifies the action to take for this transaction if the subnetwork goes
work 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 subnetwork goes offline
• Freeze
Data is frozen on the higher level network if the subnetwork goes offline
Offline timeout time (10 ms) This parameter specifies the maximum allowed time between two incoming messages in
steps of 10ms. If this time is exceeded, the subnetwork is considered to be offline. A value
of 0 disables this feature, i.e. the subnetwork can never go offline.
The entered value is multiplied by 10. For instance, an entered value of 5 results in 50 ms.
Trigger byte • Enable
Enables the trigger byte. The location of the trigger byte must be specified in the ‘Trig-
ger byte address’ (below).
The trigger byte value will be increased each time a valid transaction has been con-
sumed 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 subnetwork.
• Disable
Disables the trigger byte functionality.
Trigger byte address This parameter specifies the location of the trigger byte in the internal memory buffer.
Valid settings range from 0x000... 0x1FF and 0x400... 0xNNN.
Please note that the trigger byte address must be unique to each transaction. It can not be
shared by two or more transactions.
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 ed-
itable.
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:
7. Frame Objects
7.1 General
Each transaction consists of Frame Objects which makes up the serial telegram frame. Each Frame Ob-
ject 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
• Byte
8 bits
• Word
16 bits
• Dword
32 bits
• 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 Pa-
rameter section.
Parameter Description
Value Constant value
• 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.
• 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 Pa-
rameter section as follows:
Parameter Description
Maximum Value This is the largest allowed value for the range.
Range:0x00... 0xFFh(byte)
0x0000... 0xFFFFh(word)
0x00000000... 0xFFFFFFFFh(dword)
Note: Value must be larger than the Minimum Value (below)
Minimum Value This is the smallest allowed value for the range.
Range:0x00... 0xFEh(byte)
0x0000... 0xFFFEh(word)
0x00000000... 0xFFFFFFFEh(dword)
Note: Value must be less than the Maximum Value (above)
• Produce/Query Transactions
The specified data block is forwarded from the higher level network to the subnetwork.
• Consume/Response Transactions
The specified data block is forwarded from the subnetwork 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 Description
Byte Swapping • 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
Data Length The length of the data block, in bytes. In case of a Response or Consume transaction, incom-
ing messages where the data size differs from the value specified here will be discarded. Max-
imum data length allowed for one frame is 300 bytes.
Data Location The location of the data block in the internal memory buffer
• Produce/Query Transactions
The specified data block will be forwarded from the higher level network to the subnetwork. 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 subnetwork or discarded.
• Consume/Response Transactions
The specified data block is forwarded from the subnetwork 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 dis-
carded.
To specify the properties of the object, select it in the Navigation Section enter the desired settings in
the Parameter section as follows:
Parameter Description
Byte Swapping • 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
Don’t fill
Filler byte Filler byte value. Only used if ‘Fill unused bytes’ has been enabled.
Data Location The offset in the internal memory buffer where the data shall be read from / written to
Object Delimiter • Length Character
Length character is visible in the internal memory buffer but not on the subnetwork
• Length Character Visible
The length character is visible both in the internal memory buffer and on the subnetwork.
• End Character
The end character is visible in the internal memory buffer but not on the subnetwork.
• End Character Visible
The end character is visible both in the internal memory buffer and on the subnetwork
• No Charactera
No End- or Length-character is generated in the internal memory buffer.
End Character Value End Character valueb
Maximum Data Length 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 300 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’
8. Commands
This information is only valid for master mode and generic mode. For DF1 master mode, please refer
to “Services” on page 56.
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 subnetwork.
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’-pa-
rameter (see “Node Parameters” on page 33). In such case, the parameters in the parameter section will
be greyed out and cannot be edited directly.
In Master Mode, Anybus Configuration Manager 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 49). For DF1 Master Mode, see “Services” on page 56. In Generic
Data Mode, no predefined commands exist, but custom ones may be implemented as desired.
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.
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 49.
• Edit Command
Edit the currently selected command using the
Command Editor.
See also “The Command Editor” on page 49.
• Delete Command
Delete the currently selected command from the list. Note that some commands are fixed and
cannot be deleted.
The toolbar features icons for the most commonly used functions.
• Add Command
(Same as ‘Add Command’ in the ‘Command’-menu).
Add Command
• Edit Command
(Same as ‘Edit Command’ in the ‘Command’-menu).
Edit Command
• Delete Command
(Same as ‘Delete Command’ in the ‘Command’-menu).
Delete Command
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.
Open the Command Editor by selecting ‘Edit Command’ or ‘Add Command’ from the ‘Command’-
menu.
A
B D E
A: Pull-down Menu
See “Pull-down Menu” on page 50.
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 que-
ry-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 Description
Allow Broadcasting Specifies if it is allowed to broadcast the command (only relevant in Master Mode)
Produce The command is producing data (Generic Data Mode only)
Consume The command is consuming data (Generic Data Mode only)
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 Command
Delete the column at the selected posi-
tion.
As mentioned previously, the transaction section in the Command Editor represents the actual transac-
tions 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
• Example Query
Query 1 2 3 4
DisplayName Slave Address Function Data Checksum
Object Type Byte Object Byte Object Data Object Checksum Object
Value [SlaveAddress] ID User User
The value of this byte The value of this byte The size and location The checksum type
constant will be set constant will be set of the data associated etc can be selected by
using the ‘SlaveAd- using the ‘Command with this object is the user. By default,
dress’ parameter (see ID’-field. determined by the this is set to match the
“Node Parameters” on user. Modbus-RTU stan-
page 33). dard.
• Example Response
Response 1 2 3 4
DisplayName Slave Address Function Data Checksum
Object Type Byte Object Byte Object Data Object Checksum Object
Value [SlaveAddress] ID User Depend
This value is linked to The value of this byte The size and location This object will
the ‘SlaveAddress’ constant will be set of the data associated retrieve its settings
parameter in the using the ‘Command with this object is from the correspond-
parameter window. ID’-field. determined by the ing object in the
user. Query.
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 pos-
sible 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 func-
tion code in the ‘Command ID’-field. If the command is allowed to be broadcasted, check the ‘Allow
Broadcasting’-checkbox.
9.1 General
In DF1 master mode, communication is based on ‘services’. A ‘service’ represents a set of commands
and operations on the subnetwork, that is predefined in the Anybus Communicator. Each service is as-
sociated with a set of parameters controlling how and when to use it on the subnetwork.
The communication is based on a query-response scheme, where the gateway issues a query on the sub-
network. The addressed node on the subnetwork 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, Anybus Configuration Manager 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-click-
ing on a node in the Anybus Configuration Manager and selecting ‘Add Command’.
Interface
Currently, only serial communication is supported.
Value Description
Enabled Enable the Control and Status Registers. The ‘Data Valid’-bit in the Control Register must
be set to start the subnetwork communication.
Enabled but no startup lock This setting is similar to ‘Enabled’, except that the control system is not required to set the
‘Data Valid’-bit to start the subnetwork communication.
Disabled 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 Description
Enabled The gateway will be restarted, and no error will be indicated to the user.
Disabled The gateway will halt and indicate an error.
Protocol Mode
This parameter specifies which protocol mode to use for the subnetwork.
Value Description
DF1 This mode is intended for the DF1 protocol. The Anybus Communicator can only be con-
figured 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 ex-
changed on the subnetwork. This feature is primarily intended for debugging purposes.
Communication
These parameters specify the actual communication settings used for the subnetwork.
DF1 Settings
Parameter Description
Master Node Address Node address of the master, valid values: 0 - 254, default 1
Poll time, active slaves (10 ms) Determines how often the slave shall be polled in steps of 10 ms, default 100 msa
Poll time, inactive slaves (10 ms) Determines how often the slave shall be polled in steps of 10 ms, default 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.
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 ex-
ecute a service, it automatically chooses the appropriate DF1 command(s) that are used to perform the
service on the selected DF1 node type.
Timing:
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:
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, de-
pending on node type:
Data options:
Command Parameters
Data Options
General
The Subnetwork Monitor is intended to simplify configuration and troubleshooting of the subnetwork.
Its main function is to display the data allocated for subnetwork 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 de-
selecting single transactions makes it possible to view any combination of allocated data.
Note: The subnetwork monitor has a negative influence on the overall performance of the gateway.
Therefore the monitor functionality should be used with care.
Operation
B: Nodes / Transactions
To view data blocks associated with a transaction, select the transaction in the list. The corre-
sponding 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 Meaning
White Not allocated.
Yellow Data allocated by a Response or Consume transaction.
Blue Data allocated by a Query or Produce transaction
Red Collision; area has been allocated more than once.
Grey Reserved (illustrates memory consumption, area can be allocated if necessary)
Green Data allocated by Trigger byte, Transmit/Receive Counter, or Control/Status Registers.
11.1 General
The Node Monitor can provide valuable information when setting up the communication with the sub-
network, by allowing individual commands to be issued manually, and monitoring the response (if ap-
plicable). 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:
(Not used)
B: Command Section
This section holds the currently selected command. The individual frame objects in the com-
mand can be edited in a similar way as in the Transaction and Command Editors.
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 64.
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 subnetwork.
• Send Command
Send the specified command to the subnetwork.
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.
The toolbar features icons for the most commonly used functions.
• Refresh
When clicking on this icon, the data displayed in the Monitor Section will be re-
freshed. Refresh
12.1 General
This feature allows the subnetwork traffic to be logged into a buffer for examination. This may provide
valuable information when debugging the lowest levels of the subnetwork communication.
Note that the logger function is part of the gateway itself and is separate from the Anybus Configuration
Manager. This means that logging can be performed even if the gateway is physically disconnected from
the PC running the Anybus Configuration Manager.
12.2 Operation
• Start logging
Select ‘Start Logging’ in the ‘Tools’-menu. Anybus Configuration Manager 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 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 AS-
CII format for both directions. The time between the log-en-
tries 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.
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 ‘ABC’-
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.
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.
• Blank Configuration
This option creates an empty configuration.
• Important Notes:
Many OEM devices do not fully comply with the Modbus standard. For example, they may im-
plement 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 informa-
tion about the serial communication protocol.
In the event that the wizard doesn’t 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.
Steps 3 - 6
Consult the online help system for fur-
ther information.
14.1 General
The Control and Status Registers are disabled by default, but can be enabled using the Anybus Config-
uration Manager (see “Status / Control Word” on page 30). These registers form an interface for ex-
changing status information between the subnetwork and the fieldbus control system.
The main purpose of these registers is to...
• Report subnetwork 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 sub-
network
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 net-
work uses a different byte order, the upper and lower bytes will appear swapped.
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.
Start Start
No Yes
Set CR_HS_CONFIRM
Toggle CR_HS_SEND
to SR_HS_SEND
Done Done
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 ‘Status / Control Word’-parameter in Anybus Configuration Manager is set to ‘Enabled’, the gate-
way will wait for the fieldbus control system to set the ‘Data Valid’-bit in the Control Register before it
starts exchanging data on the subnetwork.
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.
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 subnetwork devices; it should be considered as an aid for the fieldbus control system to know when
all data has been updated.
The Status Register is (if enabled) located at 0x000-0x001 and constitutes a bit-field as follows:
bit(s) Name Description
15 Send These bits control the handshaking towards the fieldbus control system.
(SR_HS_SEND)
14 Confirm See also...
(SR_HS_CONFIRM) - “Handshaking Procedure” on page 69
- “Control Register Contents (Control System to Gateway)” on page 73
13 Data Valid This bit is set when all transactions have been executed successfully at least once.
(Master Mode and DF1 Once set, it will not change.
Master Mode Only) 1:Data Valid
0:Data not Valid
Note: This bit is not used in Generic Data Mode.
12... 8 Status Code This field holds the last status report from the gateway.
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.
(This table is valid only in Master Mode and DF1 Master Mode).
Code Condition Type Data Description
0x00 Retransmission Warning Counter The number of retransmissions on the subnet-
Counter Updated work has increased. If this problem persists,
this may eventually trigger a Single- or Multi-
ple Node(s) Missing condition.
0x01 Single Node Missing Error Slave address A single node is missing.
0x02 Multiple Nodes Missing Error Number of nodes Multiple nodes are missing.
0x03 Buffer Overrun Warning Slave address A node returned more data than expected.
0x04 Other Error Error Slave address Undefined error
0x1F No Error Warning - 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 nec-
essarily be followed by a ‘No Error’ condition later on.
See also...
- “Consume-Transactions” on page 39 (Offline timeout
time)
0x03 Buffer Overrun Warning - A node returned more data than expected - or - the gate-
way was unable to finish processing a message prior to
receiving a new one.
0x04 Other Error Error - Undefined error
0x1F No Error Warning - 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.
The Control Register is (if enabled) located at 0x200-0x201 and constitutes a bit-field as follows:
bit(s) Name Description
15 Confirm These bits control the handshaking towards the gateway.
(CR_HS_CONFIRM)
14 Send See also...
(CR_HS_SEND) - “Handshaking Procedure” on page 69
- “Status Register Contents (Gateway to Control System)” on page 71
13 Data Valid This bit controls data consistency (see “Data Consistency” on page 70).
1:Output Area valid; exchange data on the subnetwork
0:Output Area not valid; do not exchange data on the subnetwork
Note: This bit is only relevant if the Control/Status Registers are set as ‘Enabled’
12 Execute Command If set, the specified command will be executed by the gateway (see below).
11... 8 Control Code This field holds commands which can be executed by the gateway (see below).
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.
(This table is valid only in Master Mode and DF1 Master Mode).
Code Instruction Data Description
0x00 Disable Node Actual node address Disables the specified node.
0x01 Enable Node Actual node address Enables a previously disabled node.
0x02 Enable Nodes Actual number of nodes to enable Enables the specified number of nodes, start-
ing from the first node in the configuration.
Remaining nodes will be disabled.
15.1.1 General
The standard object dictionary is implemented according to the DS301 specification (v4.02) from CiA
(CAN in Automation).
16.1 General
The fieldbus interface of the gateway consists of an embedded Anybus-S communication interface. Nor-
mally, 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 fa-
miliar with the Anybus-S and it’s application interface. For more information about the Anybus-S plat-
form, consult the Anybus-S Parallel Design Guide.
The standard initialization parameters are determined by the subnetwork configuration. Information
about the amount of input and output data used for subnetwork communication is used by Anybus Con-
figuration Manager 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 de-
sired fieldbus for further information.)
4 - -
5 CAN_SHLD Optional CAN shield
6 9
6 GND Optional ground
7 CAN_H CAN_H bus line (dominant high)
8 - -
9 (reserved) -
1 +24V DC
2 GND
Notes:
• Use 60/75 or 75×C copper (CU) wire only.
• The terminal tightening torque must be between 5... 7 lbs-in (0.5... 0.8 Nm)
A.3 PC Connector
1 1 Ground
RS232 Rx 2 2 Ground
RS232 Tx 3 3 Rx
4 4 Tx
Ground 5
Pin Description
1 Signal ground 4
2
3
3 RS232 Rx (Input)
2
4 RS232 Tx (Output) 1
DB9F : PC
Pin Description
1 -
2 RS232 Rx (Input) 5 (female) 1
3 RS232 Tx (Output)
4 -
9 6
5 Signal Ground
6-9 -
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 sub-
network connector.
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 >200mV.
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.
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... 120R.
5 a
Signal Ground
6 RS422 Rx + 9 6
7 RS422 Rx -
8 RS485 + /RS422 Tx+
9 RS485 - /RS422 Tx-
(housing) Cable Shield
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.
470R
RS485 + RS485 +
120R 120R
RS485 - RS485 -
470R
Signal Signal
Ground Ground
Ground
Signal
RS485 -
RS485 +
Ground
Signal
RS485 -
RS485 +
Ground
Signal
RS485 -
RS485 +
Ground
Signal
RS485 -
RS485 +
Cable
Shield
Anybus Communicator Node Node Node Node End Node
470R
120R
470R 470R
120R
470R
Signal Signal
Ground Ground
Cable
Shield
Note: Bias resistors are normally not needed on RS422, but may be required when using 4-wire RS485.
RS232 Tx RS232 Rx
RS232 Rx RS232 Tx
Signal Signal
Ground Ground
Cable
Shield
B. Technical Specification
Housing
Plastic housing with snap-on connection to DIN-rail, protection class IP20
Dimensions
120 mm x 75 mm x 27 mm, L x W x H (inches: 4.72” x 2.95” x 1.06”; L x W x H)
Power Supply
Power: 24V ± 10%
Power Consumption
Maximum power consumption is 280mA on 24V. Typically around 100mA
Relative Humidity
The product is designed for a relative humidity of 0 to 95% non-condensing
Temperature
Operating: ±0°C to +55°C
Non Operating: -25°C to +85°C
• EN 50082-2 (1993)
EN 55011 (1990)Class A
• EN 61000-6-2 (1999)
EN 61000-4-3 (1996)10V/m
EN 61000-4-6 (1996)10V/m(all ports)
EN 61000-4-2 (1995)±8kVAir Discharge
±4kVContact discharge
EN 61000-4-4 (1995)±2kVPower port
±1kVOther ports
EN 61000-4-5 (1995)±0.5kVPower ports (DM/CM)
±1kVSignal ports
UL/c-UL compliance
• EN 60950-1 (2001)
Pollution Degree 2
Material Group IIIb
250 VRMS or 250 VDCWorking voltage
500 VSecondary circuit transient rating
C. Troubleshooting
Problem Solution
Problem during configuration Upload / Download. • Serial communication failed. Try again
The Config Line “LED” turns red in the Anybus Configura-
tion Manager.
The serial port seems to be available, but it is not possible • The serial port may be in use by another application.
to connect to the gateway Exit the Anybus Configuration Manager and close all
other applications including the ones in the system
tray.
Try again
• Select another serial port
Try again
Poor performance • Right click ‘subnetwork’ in the Navigation window and
select ‘subnetwork Status’ to see status / diagnostic
information about the subnetwork.
If the gateway reports very many retransmissions,
check your cabling and/or try a lower baud rate setting
for the subnetwork (if possible).
• Is the Subnet Monitor in the Anybus Configuration
Manager active?
The subnetwork monitor has a negative influence on
the overall performance of the gateway, and should
only be used when necessary.
• Is the Node Monitor in the Anybus Configuration Man-
ager active?
The node monitor has a negative influence on the
overall performance of the gateway, and should only
be used when necessary.
No subnetwork functionality • Use the ‘Data logger’-functionality to record the serial
data communication on the subnetwork.
• If no data is being transmitted, check the configuration
in Anybus Configuration Manager.
• If no data is received, check the subnetwork cables.
Also verify that the transmitted data is correct.
D. ASCII Table
x0 x1 x2 x3 x4 x5 x6 x7 x8 x9 xA xB xC xD xE xF