xgateway_interface
xgateway_interface
DeviceNet Scanner
Doc: HMSI-27-247, Rev: 2.00
Connecting DevicesTM
HALMSTAD • CHICAGO • KARLSRUHE • TOKYO • BEIJING • MILANO • MULHOUSE • COVENTRY • PUNE • COPENHAGEN
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
product. Failure to observe this may cause damage to the product.
Table of Contents
Revision List
• Input Buffer
This buffer holds data forwarded
from the other network, i.e. data
which can shall be sent to other Input
Buffer
(from Gateway)
DeviceNet nodes.
DeviceNet
• Output Buffer DeviceNet Scanner Interface
This buffer is forwarded to the
other network, i.e. data which is Output
(to Gateway)
Buffer
retrieved from other DeviceNet
nodes.
1.2 Features
• Galvanically isolated bus electronics
• 125kbit, 250kbit and 500kbit operation
• On-board configuration switches
• Up to 512 byte of I/O in each direction
• Explicit Messaging (up to 512 bytes in each direction)
• Polled I/O
• Bit-strobed I/O
• Change-of-state / Cyclic I/O
Top View
1.3.1 Connectors & Switches
DeviceNet Configuration Gateway Power
Connector switches
Connector
DeviceNet connector
See A-34 “DeviceNet Connector Pinout”.
Configuration Switches
See 2-9 “Configuration Switches”.
Switches 1 and 2 are used to set the baud rate of the Scanner interface.
Switch 1 Switch 2 Switch 3 Switch 4 Switch 5 Switch 6 Switch 7 Switch 8 Baud Rate
OFF OFF - - - - - - 125 k
OFF ON - - - - - - 250 k
ON OFF - - - - - - 500 k
ON ON - - - - - - (reserved)
Example:
OFF
ON
In this example, the baud rate will be 250 kbit/s.
Switches 3...8 are used to set the MacID of the Scanner interface in binary format.
Example:
OFF
OFF
OFF
ON
ON
ON
See also...
• The Anybus X-gateway User Manual, for full details on using ACM.
• The online help in ACM, for further help on the available settings.
• 3-14 “Control & Status Word Details”
• 3-15 “Live List Interpretation”
Anybus NetTool DN is an easy to use configuration tool suitable for the Anybus-X DeviceNet Scanner
interface. A fast learning curve and visual user interface allows complete network configurations to be
built without spending precious time learning a new program.
Anybus NetTool DN is ordered separately, however a free trial version (limited to 2 nodes) can be
downloaded from the HMS website www.anybus.com
For a configuration example, see 2-12 “Configuration Example”.
Configuration Drivers
To be able to configure the Scanner interface, a compatible configuration driver must be used. In the
case of Anybus NetTool, the following adapters are supported:
For further information, consult the application note “How to Configure DeviceNet with Anybus Net-
Tool for DeviceNet”, available at www.anybus.com, or contact HMS.
In this example, a network consisting of 5 nodes has been created using Anybus NetTool DN.
• Node 0 (Anybus-M)
This is the Scanner interface itself.
• Node 1 (Anybus-C)
10 words input
5 words output
• Node 2 (AB32)
1 word input
1 word output
• Node 3 (AB64)
2 words input
2 words output
Nodes 1 - 3 are mapped to the Scanner interface as illustrated below. (Note: Although DeviceNet allows
data to be mapped on a per-bit basis, this has been avoided in the example for simplicity reasons).
Offset Offset
Node (Input) (Output)
Word Bit Word Bit
1 0 0 0 0
2 10 0 5 0
3 11 0 6 0
The I/O map is reflected in the Input- and Output buffers as follows:
10 bytes (node 1)
20 bytes (node 1)
2 bytes (node 2)
4 bytes (node 3)
2 bytes (node 2)
4 bytes (node 3) (unused)
(unused)
3. Data Exchange
Status Word
Live List
DeviceNet Scanner Slave Interface
DeviceNet
Network DeviceNet
Image Network
DeviceNet Network
Image
Other Network
(Output)
(Input)
Control Word
DeviceNet
Network DeviceNet
Image Network
(Input) Image
(Output)
The structure of the DeviceNet Network I/O is determined by the configuration created in the Device-
Net configuration tool.
Note: The input/output data sizes of the Scanner Interface is determined by the size of the actual con-
figuration created using the DeviceNet configuration tool and cannot be set via the Gateway Config in-
terface.
See also...
• 2-10 “Gateway Config Interface”
• 2-11 “DeviceNet Scanlist Configuration”
The Control Word, if enabled, controls the communication towards the other nodes on the DeviceNet
network.
Control Word Contents:
(MSB) (LSB)
1b Reset gateway Setting this bit causes the gateway to perform a self-reset.
The Status Word holds general status information as described in the generic user manual. Bit 2 and 3
indicates the Master Mode, similar to the corresponding two bits in the Control Word, see above.
(Consult the generic user manual for further information about the remainding bits in the Status Word).
IMPORTANT: The Control- and Status Words can be disabled through the Gateway Configuration Interface. In
such case, the master interface will enter ‘Run’ mode automatically after having completed the start up initialisation se-
quence. If enabled, the scanner will start up in ‘Idle’ mode, and will not exchange data until the mode has been changed to
‘Run’.
Depending on fieldbus, it may be necessary to swap the bytes in the Control/Status word and in the Live list.
For more information regarding the Live List, consult the generic user manual.
Object Description
-
Implemented Services
Class services: Get Attribute Single
Instance services: Get Attribute All
Get Attribute Single
Set Attribute Single
Reset
Object Description
-
Supported Services
Class services: -
Instance services: -
Object Description
-
Supported Services
Class Get Attribute Single
Instance: Get Attribute Single
Set Attribute Single
Allocate Master/Slave Connection Set (4Bh)
Release Group 2 Identifier Set (4Ch)
Object Description
-
Supported Services
Class -
Instance: Get Attribute Single
Set Attribute Single
Get Member
Set Member
Note: This instance is only settable when no active Class 0 I/O connections are in use.
Object Description
-
Implemented Services
Class services: -
Instance services: Get Attribute Single
Set Attribute Single
Reset
Object Description
-
Implemented Services
Class services: -
Instance services: Get Attribute Single
Set Attribute Single
Instance numbers correlate to the Mac ID of the connected device + 1 (i.e. instance 10 = MAC ID 9).
Object Description
-
Supported Services
Class services: Get Attribute Single
Instance services: Get Attribute Single
Set Attribute Single
Get Member
Set Member
Instance numbers correlate to the Mac ID of the connected device + 1 (i.e. instance 10 = MAC ID 9).
Object Description
This object groups information about the configuration in the scanner, and can be changed using a De-
viceNet configuration tool or through the mailbox interface. Note that alterations in this object is only
permitted in Idle Mode.
Supported Services
Class services: Commit
Instance services: Get Attribute All
Set Attribute All
Get Attribute List
Get Attribute Single
Set Attribute Single
Object Description
Each instance within this object represents a node on the network. An instance groups all information
associated with the node, i.e. I/O sizes, Vendor ID, Product Code, Product Type etc.
The scanner keeps two copies of this information - a volatile working copy, and another copy stored in
non-volatile memory. All changes are carried out in the working copy, which can then be stored in non-
volatile memory by means of the ‘Commit’-service.
Supported Services
Class services: Commit (Saves the scanlist to non-volatile memory)
Reset (Clears the entire scanlist)
Instance services: Get Attribute All
Set Attribute All
Get Attribute Single
Set Attribute Single
Reset (Clears the corresponding node in the scanlist)
Instance numbers correlate to the Mac ID of the connected device + 1 (i.e. instance 10 = MAC ID 9).
The following attributes are treated differently if addressed using Set/Get Single.
A. Technical Specification
Interface Details
Note: The DeviceNet interface requires 24V bus power according to the DeviceNet standard in order
to function properly.