advertisement
User Manual
Anybus
®
Communicator
™ for EtherCAT
®
Doc: HMSI-168-95
Rev: 3.20
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. All other trademarks are the property of their respective holders.
EtherCAT® is a registered trademark and patented technology, licensed by Beckhoff Automation
GmbH, Germany
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 for Netbiter EasyConnect Gateway User Manual User Manual
Copyright© HMS Industrial Networks AB
Doc HMSI-168-92
Anybus Communicator Netbiter EasyConnect Gateway User Manual Doc: HMSI-168-92, Rev. 3.20
Table of Contents
Table of Contents
Preface About This Document
Chapter 1 About the Anybus Communicator for EtherCAT
Chapter 2 Basic Operation
Chapter 3 CANopen Object Dictionary Implementation
Anybus Communicator Netbiter EasyConnect Gateway User Manual Doc: HMSI-168-92, Rev. 3.20
Chapter 4
Chapter 5
Chapter 6
Chapter 7
Chapter 8
Navigating ACM
Basic Settings
Nodes
Transactions
Frame Objects
IV
Anybus Communicator Netbiter EasyConnect Gateway User Manual Doc: HMSI-168-92, Rev. 3.20
Chapter 9
Chapter 10
Chapter 11
Chapter 12
Chapter 13
Chapter 14
Commands
Example: Specifying a Modbus-RTU Command in Master Mode .................................... 51
DF1 Protocol Mode
Sub-network Monitor
Node Monitor
Data Logger
Configuration Wizards
V
Anybus Communicator Netbiter EasyConnect Gateway User Manual Doc: HMSI-168-92, Rev. 3.20
Chapter 15
Chapter 16
Appendix A
Appendix B
Appendix C
Appendix D
Control and Status Registers
Advanced Fieldbus Configuration
Connector Pin Assignments
Technical Specification
Troubleshooting
ASCII Table
VI
Anybus Communicator Netbiter EasyConnect Gateway User Manual Doc: HMSI-168-92, Rev. 3.20
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 - EtherCAT 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.11... 3.20)
Revision Change
3.20
Updated LED description
Page(s)
Revision List
Revision Date
2.00
Author
2007-05-07 PeP
2.01
2.03
2007-08-13 PeP
2009-04-24 KeL
3.00
3.01
2011-02-09 KaD
2011-09-30 KaD
3.02
3.10
3.11
3.20
2012-11-20 KeL
2015-02-11 ThN
2015-03-20 ThN
2016-09-07 ThN
I
All
B
1
Chapter Description
All 1st official release
-
All
Minor update
Misc. minor corrections and updates
All
All
Misc. minor updates, new template and DF1 functionality
Misc corrections and updates, new Anybus Configuration Manager name
Added information on EtherCAT trademark
Misc. corrections and updates
Added compliance/conformance info
Updated LED description
Anybus Communicator Netbiter EasyConnect Gateway User Manual Doc: HMSI-168-92, Rev. 3.20
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 “gateway” 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.4 Glossary
Term
ABC
ACM
Broadcaster
ECT
Command
Configuration
Meaning
Anybus Communicator
Anybus Configuration Manager
A protocol-specific node in the configuration that handles transactions destined to all nodes.
EtherCAT
A predefined transaction.
List of configured nodes with transactions on the subnetwork.
Fieldbus
Control System
Frame Object
Monitor
Node
The higher level network to which the communicator is connected.
Device which controls the communication on the higher level network, i.e. a fieldbus master
Low level entities which are used to describe the different parts of a transaction.
A tool for debugging the gateway and the network connections.
A device in the configuration which defines the communication with a node on the subnetwork
Subnetwork
Transaction
The network that is logically located on a subsidiary level with respect to the fieldbus, and to which this product 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 User
Higher Level Network In this case, EtherCAT
Network
Fieldbus
P.5 Support
For general contact information and support, please refer to the contact and support pages at www.anybus.com
Anybus Communicator Netbiter EasyConnect Gateway User Manual Doc: HMSI-168-92, Rev. 3.20
Chapter 1
1. About the Anybus Communicator for EtherCAT
The Anybus Communicator for EtherCAT acts as a gateway between virtually any serial application protocol and an EtherCAT-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.
EtherCAT Master
(e.g a PLC)
EtherCAT Master
(e.g a PLC)
PC configuration and monitoring
Multi-drop up to 31 nodes
PC configuration and monitoring
Serial communication device
Single-Node Serial Sub Network
Serial communication devices
Multi-Node Serial Sub Network
Subnetwork
The gateway can address up to 31 nodes, and supports the following physical standards:
• RS-232
• RS-422
• RS-485
EtherCAT Interface
EtherCAT 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.
• CANopen over EtherCAT
• DS301 v4.02 compliant
• Galvanically isolated network electronics
• Supports segmented SDO access
• Exchanges up to 512 bytes of data in each direction
Anybus Communicator Netbiter EasyConnect Gateway User Manual Doc: HMSI-168-92, Rev. 3.20
About the Anybus Communicator for EtherCAT 10
1.1 External View
For wiring and pin assignments, see “Connector Pin Assignments” on page 74.
A: EtherCAT Port 1 (In)
See also...
- “EtherCAT Connectors” on page 74
B: EtherCAT Port 2 (Out)
See also...
- “EtherCAT Connectors” on page 74
A
B
C: Status LEDs
See also...
D: PC-connector
This connector is used to connect the gateway to a PC for configuration and monitoring purposes.
See also...
D
E
F
E: Subnetwork Connector
This connector is used to connect the gateway to the serial subnetwork.
See also...
- “Subnetwork Interface” on page 76
F: Power Connector
This connector is used to apply power to the gateway.
See also...
- “Power Connector” on page 74
- “Troubleshooting” on page 131
G: DIN-rail Connector
The DIN-rail mechanism connects the gateway to PE (Protective Earth).
See also...
- “Hardware Installation” on page 12
C
G
Anybus Communicator Netbiter EasyConnect Gateway User Manual Doc: HMSI-168-92, Rev. 3.20
About the Anybus Communicator for EtherCAT 11
1.2 Status LEDs
EtherCAT Interface Indications
#
1 - RUN
2 - ERR
State
Off
Green
Green, blinking
Status
Device in INIT state
Device in OPERATIONAL state
Device in PREOPERATIONAL state
Green, single flash Device in SAFE-OPERATIONAL state
Off
Red
Red, blinking
Red, single flash
Normal operation (no errors)
Application watchdog timeout
General configuration error
Slave device application has changed the Ether-
CAT status autonomously: Parameter “Change” in the AL status register is set to 01 (change/error)
Red, double flash
3 - Link/Activity 1 Off
Green
Green, flickering
4 - Link/Activity 2 Off
Green
Green, flickering
Sync manager watchdog timeout
No link sensed on EtherCAT port 1
Link sensed on EtherCAT port 1
Activity on EtherCAT port 1
No link sensed on EtherCAT port 2
Link sensed on EtherCAT port 2
Activity on EtherCAT port 2
General Gateway/Subnet Indications
#
5 - Subnet Status a
State
Off
Green, flashing
Green
Red
6 - Device Status Off
Status
Power off
Running correctly, but one or more transaction error(s) have occurred
Running
Transaction error/timeout or subnet stopped
Power off
Alternating Red/Green Invalid or missing configuration
Green Initializing
Green, flashing Running
Red
Red, flashing
Bootloader mode b
If 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 Commu-
nicator. Choose Tools/Options/Module. Click “Factory Restore” to restore firmware. See
1
3
5
2
4
6
Anybus Communicator Netbiter EasyConnect Gateway User Manual Doc: HMSI-168-92, Rev. 3.20
About the Anybus Communicator for EtherCAT 12
1.3 Hardware Installation
Perform the following steps when physically installing the gateway:
1.
Snap the gateway on to the DIN-rail (See “DIN-rail Connector” on page 10)
The DIN-rail mechanism works as follows:
2
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)
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 EtherCAT network
3.
Connect the gateway to the serial subnetwork
4.
Connect the gateway to the PC via the Configuration Cable
5.
Connect the power cable and apply power
6.
Start the Anybus Configuration Manager on the PC
(The Anybus Configuration Manager software attempts to detect the serial port automatically. If not successful, select the correct port manually in the “Port”-menu)
7.
Configure the gateway using the Anybus Configuration Manager and download the configuration
Anybus Communicator Netbiter EasyConnect Gateway User Manual Doc: HMSI-168-92, Rev. 3.20
About the Anybus Communicator for EtherCAT 13
1.4 Software Installation
1.4.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.
Anybus Communicator Netbiter EasyConnect Gateway User Manual Doc: HMSI-168-92, Rev. 3.20
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 Netbiter EasyConnect Gateway User Manual Doc: HMSI-168-92, Rev. 3.20
Basic Operation 15
2.2 Data Exchange Model
Internally, the data exchanged on the subnetwork, and the data exchanged on the higher level network (i.e.
EtherCAT), resides in the same 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.
The internal memory buffer is divided into three areas based on their function:
• Input Data (Up to 512 bytes)
This area can be read from the higher level network (i.e. by the EtherCAT master).
• Output Data (Up to 512 bytes)
This area can be written to by the higher level network (i.e. by the EtherCAT master)
• General Data (Up to 1024 bytes)
This area cannot be accessed from the higher level network, but can be used for transfers between individual nodes on the subnetwork, or as a general “scratch pad” for data. The actual size of this area depends on the amount of data that is exchanged on the subnetwork.
Internal Memory
Input Data
(512 bytes)
Output Data
(512 bytes)
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 Output Data
0x000 0x200 0x400
General Data
Subnetwork:
EtherCAT:
Read/Write
Read Only
Subnetwork:
EtherCAT:
Read Only
Read/Write
Subnetwork:
EtherCAT: -
Read/Write
0x1FF 0x3FF 0x???
Anybus Communicator Netbiter EasyConnect Gateway User Manual Doc: HMSI-168-92, Rev. 3.20
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 gateway.
PLC (EtherCAT Master)
PLC Memory (Inputs) PLC Memory (Outputs)
Actual Temperature Temperature Setpoint
The PLC exchanges data between the internal
PLC memory and the EtherCAT slaves (in this case the Anybus Communicator gateway).
The PLC memory associated with the gateway is exchanged;
Data from the Input Data area is copied to
PLC Input Memory, and PLC Output
Memory is copied to the Output Data area.
Input Data
Actual Temperature
Anybus Communicator Gateway
Output Data General Data
0x000 0x200 0x400
Temperature Setpoint
(not used in this example)
0x1FF 0x3FF 0x???
The gateway copies the Output Register of the Temperature Regulator to the
Input Data area.
The gateway copies the Temperature-
Setpoint from the Output Data area to the Input Register in the Temperature-
Regulator.
Output Register
Actual Temperature
Input Register
Temperature Setpoint
Serial Device - Temperature Regulator
The Temperature Regulator has two registers, holding the Setpoint Temperature and the Actual Temperature respectively.
Anybus Communicator Netbiter EasyConnect Gateway User Manual Doc: HMSI-168-92, Rev. 3.20
Basic Operation 17
2.3 Subnetwork Protocol
2.3.1 Protocol Modes
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 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.
See also “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.
See also “DF1 Protocol Mode” on page 52.
• 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.
See also “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 Netbiter EasyConnect Gateway User Manual Doc: HMSI-168-92, Rev. 3.20
Basic Operation 18
2.3.3 Master Mode
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 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 Netbiter EasyConnect Gateway User Manual Doc: HMSI-168-92, Rev. 3.20
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 itself, 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 52.
Anybus Communicator Netbiter EasyConnect Gateway User Manual Doc: HMSI-168-92, Rev. 3.20
Basic Operation 20
2.4 EtherCAT Communication Properties
2.4.1 General
The EtherCAT interface acts as a full EtherCAT slave device with the following properties:
General Properties
• Full EtherCAT slave device
• 4 FMMU channels (can be used freely by the EtherCAT master for any purpose.)
• 4 SM channels
• 4kByte RAM
• Bit-oriented FMMU operation
• Position addressing, node addressing and logical addressing
• PDI Watchdog
• Output I/O Sync Manager Watchdog
Supported Features
• CANopen over EtherCAT
• DS301 v4.02 compliant
• Supports segmented SDO access
• Up to 512 bytes of cyclic data in each direction
2.4.2 Sync Managers
The gateway features four Sync Managers:
• Sync Manager 0
Used for mailbox write transfers (Master to Slave).
The gateway supports mailbox sizes of 50... 256 bytes (default = 192).
• Sync Manager 1
Used for mailbox read transfers (Slave to Master).
The gateway supports mailbox sizes of 50... 256 bytes (default = 192).
• Sync Manager 2
Contains the RxPDOs specified by the PDO assignment.
In practice, Sync Manager 2 holds the unmodified Output I/O data.
• Sync Manager 3
Contains the TxPDOs specified by the PDO assignment.
In practice, Sync Manager 3 holds the unmodified Input I/O data.
Anybus Communicator Netbiter EasyConnect Gateway User Manual Doc: HMSI-168-92, Rev. 3.20
Basic Operation 21
2.4.3 Data Representation
As mentioned previously, the gateway implements CANopen over EtherCAT. The object implementation is based on the DS301 communication profile.
Input and output data is mapped to dedicated objects in the manufacturer-specific range. Data declared as I/O data is exchanged by means of Process Data Objects (PDOs), while the remainder is exchanged through Service Data Objects (SDOs).
The PDO mapping is static and looks as follows:
PDO Corresponding Object
TxPDO 1A00h Index 2000h, sub-index 1...128
TxPDO 1A01h Index 2001h, sub-index 1...128
TxPDO 1A02h Index 2002h, sub-index 1...128
TxPDO 1A03h Index 2003h, sub-index 1...128
RxPDO 1600h Index 2100h, sub-index 1...128
RxPDO 1601h Index 2101h, sub-index 1...128
RxPDO 1602h Index 2102h, sub-index 1...128
RxPDO 1603h Index 2103h, sub-index 1...128
Internal Memory
Input Data, bytes 0... 127
Input Data, bytes 128... 255
Input Data, bytes 256... 383
Input Data, bytes 384... 511
Output Data, bytes 0... 127
Output Data, bytes 128... 255
Output Data, bytes 256... 383
Output Data, bytes 384... 511
Note: The gateway will only map as many PDOs as required to hold the specified amount of I/O data.
Example:
The following example illustrates how the internal memory buffers are represented on the EtherCAT network.
The I/O Sizes are set as follows:
IO Size In= 256 bytes (0x0100)
IO Size Out= 384 bytes (0x0180)
Resulting memory layout:
Input Data
0x000 0x200
Output Data
Object Index 2000h... 2001h
(TxPDO 1A00h... 1A01h)
IO Size In
(256 bytes)
Object Index 2100h... 2102h
(RxPDO 1600h... 1602h)
IO Size Out
(384 bytes)
0x0FF
0x100
0x1FF
Object Index 2002h... 2003h
0x37F
0x380
0x3FF
Object Index 2100h... 2103h
Anybus Communicator Netbiter EasyConnect Gateway User Manual Doc: HMSI-168-92, Rev. 3.20
Chapter 3
3. CANopen Object Dictionary Implementation
3.1 Standard Objects
3.1.1 General
The standard object dictionary is implemented in accordance with the DS301 specification (v4.02).
3.1.2 Object Entries
Index Object Name Sub-Index Description
1000h Device Type 00h Device Type
1008h Manufacturer device name
00h Manufacturer device name
1018h Identity object 00h
01h
02h
03h
Number of entries
Vendor ID
Product Code
Revision Number
04h
00h
01h... n
Serial Number
Number of entries
Mapped object #n
1600h
...
1603h
Receive PDO mapping
1A00h
...
1A03h
Transmit PDO mapping
1C00h Sync Manager
Communication Type
1C12h Sync Manager
Rx PDO Assign
1C13h Sync Manager
Tx PDO Assign
00h
01h... Nn
00h
01h
02h
03h
04h
00h
01h
02h
03h
04h
00h
01h
02h
03h
04h
Number of entries
Mapped object #n
Number of entries
Mailbox wr
Mailbox rd
Process Data out
Process Data in
Number of entries
Assigned RxPDO
Assigned RxPDO
Assigned RxPDO
Assigned RxPDO
Assigned TxPDO
Assigned TxPDO
Assigned TxPDO
Assigned TxPDO a
U8
U8
U8
U8
Type Access Notes
U32 RO 0000 0000h (No profile)
Visible string
RO -
U8
U32
U8
U32
U8
U8
U8
U8
U8
U8
U8
U8
U8
U8
U8
RO
RO
U32 RO
U32 RO
U32 RO
U8 R
U32 R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
-
04h
See 2-21 “Data Representation”
See 2-21 “Data Representation”
04h
01h
02h
03h
04h
No. of assigned RxPDOs (0... 4)
Assigned to RxPDO 1600h
Assigned to RxPDO 1601h
Assigned to RxPDO 1602h
Assigned to RxPDO 1603h
No. of assigned TxPDOs (0... 4)
Assigned to TxPDO 1A00h
Assigned to TxPDO 1A01h
Assigned to TxPDO 1A02h
Assigned to TxPDO 1A03h
a. The number of entries equals the number of mapped PDOs, see “Data Representation” on page 21.
Anybus Communicator Netbiter EasyConnect Gateway User Manual Doc: HMSI-168-92, Rev. 3.20
CANopen Object Dictionary Implementation 23
3.2 Manufacturer Specific Objects
3.2.1 Input Buffer
Index Object Name Sub-Index Description
2000h Inputs 00h No. of entries
01h
02h
...
Input byte 0000
Input byte 0001
...
2001h Inputs
80h
00h
01h
Input byte 0127
No. of entries
Input byte 0128
2002h Inputs
02h
...
80h
00h
01h
02h
Input byte 0129
...
Input byte 0255
No. of entries
Input byte 0256
Input byte 0257
2003h Inputs
...
80h
00h
01h
02h
...
80h
...
Input byte 0383
No. of entries
Input byte 0384
Input byte 0385
...
Input byte 0511
Type Access Notes
U8 RO -
U8 RO -
U8
U8
U8
U8
U8
U8
RO
RO
RO
RO
RO
RO -
-
-
-
-
-
Note: The gateway will only create the number of objects needed to hold the subnetwork configuration.
See also...
• “Data Representation” on page 21
Anybus Communicator Netbiter EasyConnect Gateway User Manual Doc: HMSI-168-92, Rev. 3.20
CANopen Object Dictionary Implementation 24
3.2.2 Output Buffer
Index Object Name Sub-Index Description
2100h Outputs 00h No. of entries
01h
02h
...
Output byte 0000
Output byte 0001
...
2101h Outputs
80h
00h
01h
02h
...
80h
Output byte 0127
No. of entries
Output byte 0128
Output byte 0129
...
Output byte 0255
2102h Outputs
2103h Outputs
00h
01h
02h
...
80h
00h
01h
02h
...
80h
No. of entries
Output byte 0256
Output byte 0257
...
Output byte 0383
No. of entries
Output byte 0384
Output byte 0385
...
Output byte 0511
Type Access Notes
U8 RO -
U8 R(W) -
U8
U8
U8
U8
U8
U8
RO
R(W)
RO
R(W)
RO
R(W) -
-
-
-
-
-
Note 1: For consistency reasons, data declared as I/O data will be read-only.
Note 2: The gateway will only create the number of objects needed to hold the subnetwork configura-
tion.
See also...
• “Data Representation” on page 21
Anybus Communicator Netbiter EasyConnect Gateway User Manual Doc: HMSI-168-92, Rev. 3.20
Chapter 10
10. Navigating ACM
10.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 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 “+”.
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.
This menu entry is expanded
Sub-entries
This menu entry holds additional sub-entries / parameters
Anybus Communicator Netbiter EasyConnect Gateway User Manual Doc: HMSI-168-92, Rev. 3.20
10.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
Description
Enter a descriptive name for the new configuration
Enables password protection
Download Password(6) Set passwords for downloading
Upload Password(6) 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.
Navigating ACM 60
Anybus Communicator Netbiter EasyConnect Gateway User Manual Doc: HMSI-168-92, Rev. 3.20
Navigating ACM 61
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 98).
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
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.
Anybus Communicator Netbiter EasyConnect Gateway User Manual Doc: HMSI-168-92, Rev. 3.20
Selecting the “Module” tab will reveal additional properties:
Navigating ACM 62
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 98.
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 Netbiter EasyConnect Gateway User Manual Doc: HMSI-168-92, Rev. 3.20
Navigating ACM 63
10.1.2 Toolbar Icons
The toolbar features icons for the most commonly used functions.
• New, Open & Save
New Open Save
• Upload from ABC & Download to ABC
Upload Download
• Up one Level
Clicking on this icon will move the selection in the navigation section.
Up one Level
• Cut, Copy, Paste, Delete, Insert
These icons are used for common editing functions in the navigation section.
Cut Copy Paste
• Connect
Clicking on this icon will cause
ACM
to attempt to connect to the gateway.
Delete Insert
Connect
• Disconnect
Clicking on this icon will cause
ACM
to disconnect from the gateway.
Disconnect
• Start Logging & Stop Logging
See “Tools” on page 61 & “Data Logger” on page 98.
Start Log.
Stop Log.
• Sub-network Monitor
Clicking on this icon will launch the sub-network Monitor
(see “Sub-network Monitor” on page 93).
• Add Command
This icon is used to add commands to the currently selected node.
Sub-Network
Monitor
Add Command
• Add Mailbox
(Advanced functionality, see “Mailbox Editor” on page 118)
Add Mailbox
• Add Node & Add Broadcaster
These icons are used to add nodes to the configuration.
• Node Monitor
Clicking on this icon will launch the Node Monitor (see “Node Monitor” on page 94)
Node Broadcaster
Node Monitor
• Add Transaction(s)
These icons are used to add transactions to the currently selected node.
Add
Transactions
Add
Transaction
Anybus Communicator Netbiter EasyConnect Gateway User Manual Doc: HMSI-168-92, Rev. 3.20
Chapter 5
5. Basic Settings
5.1 Fieldbus Settings
(Select “Fieldbus” in the Navigation Section to gain access to the parameters described in this section).
Fieldbus Type
Since the Anybus Configuration Manager supports a wide range of networking systems, make sure that this parameter is set to
“EtherCAT”.
IO Sizes
These parameters specify how data from the internal memory buffer shall be exchanged on EtherCAT. This can either be handled automatically by the gateway, or specified manually.
• Automatic
All data will be treated as cyclical I/O, i.e. it will be exchanged through Process Data Objects (PDO).
(see also “Data Representation” on page 21)
• 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, will be exchanged as cyclical I/O, i.e. through Process Data Objects
(PDO). The memory area can be read but not written by
Service Data Objects (SDO).
The remainder will be exchanged as acyclical I/O through
Service Data Objects (SDO).
(see also “Data Representation” on page 21)
Fieldbus Type
IO Sizes
Anybus Communicator Netbiter EasyConnect Gateway User Manual Doc: HMSI-168-92, Rev. 3.20
65
11.2 Communicator Parameters
Interface
Only serial communication is currently supported.
Control/Status Word
See “Control and Status Registers” on page 102.
Value
Enabled
Description
Enable the Control and Status Registers. The “Data Valid”-bit in the Control Register must be set to start the sub-network 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 sub-network 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
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 Netbiter EasyConnect Gateway User Manual Doc: HMSI-168-92, Rev. 3.20
66
11.3 Sub-network Parameters
Communication
These parameters specify the actual communication settings used for the sub-network.
Parameter
Bitrate (bits/s)
Data bits
Parity
Physical standard
Stop bits
Description
Selects the bit rate
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 Netbiter EasyConnect Gateway User Manual Doc: HMSI-168-92, Rev. 3.20
Chapter 12
12. Nodes
12.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.
12.2 Adding & Managing Nodes
Function
Paste
Subnetwork Monitor
Add Node
Add Broadcaster a
Load Node
Subnetwork Status...
Description
Paste a node from the clipboard
Launch the subnet monitor (see “Sub-network Monitor” on page 93)
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.
12.3 Node Parameters
12.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 83.
Anybus Communicator Netbiter EasyConnect Gateway User Manual Doc: HMSI-168-92, Rev. 3.20
Chapter 13
13. Transactions
13.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 86.
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 Netbiter EasyConnect Gateway User Manual Doc: HMSI-168-92, Rev. 3.20
13.2 Adding & Managing Transactions
Transactions 69
Function
Copy
Delete a
Node Monitor
Add Transaction(s) b
Add Transaction Consume c
Add transaction Produce c
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 94)
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 Netbiter EasyConnect Gateway User Manual Doc: HMSI-168-92, Rev. 3.20
13.3 Transaction Parameters (Master Mode)
13.3.1 Parameters (Query & Broadcast)
Transactions 70
Parameter
Minimum time between broadcasts (10 ms)
Reconnect time (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
• NoScanning -The updating of the sub-network is stopped
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 reported to the control system.
• Clear - Data is cleared (0) on the higher level network if the sub-network goes offline
• 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 Netbiter EasyConnect Gateway User Manual Doc: HMSI-168-92, Rev. 3.20
Transactions 71
Parameter
Update mode
Update time (10 ms)
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”).
The entered value is multiplied by 10. An entered value of 5 will result in 50 ms.
13.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 Netbiter EasyConnect Gateway User Manual Doc: HMSI-168-92, Rev. 3.20
Transactions 72
13.4 Transaction Parameters (Generic Data Mode)
13.4.1 Produce Transactions
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 sub-network.
• Clear
Data is cleared (0) on the sub-network if the higher level network goes offline
Update mode
• Freeze
Data is frozen on the sub-network if the higher level network goes offline
• NoScanning
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”.
Update time (10 ms)
• 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. 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 Netbiter EasyConnect Gateway User Manual Doc: HMSI-168-92, Rev. 3.20
Transactions 73
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
13.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.
Offline timeout time (10 ms)
Trigger byte
Trigger byte address
• Clear
Data is cleared (0) on the higher level network if the sub-network goes offline
• Freeze
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
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 Netbiter EasyConnect Gateway User Manual Doc: HMSI-168-92, Rev. 3.20
Transactions 74
13.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 Netbiter EasyConnect Gateway User Manual Doc: HMSI-168-92, Rev. 3.20
Chapter 14
14. Frame Objects
14.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
14.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 74.
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 74.
Anybus Communicator Netbiter EasyConnect Gateway User Manual Doc: HMSI-168-92, Rev. 3.20
Frame Objects 76
14.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 Netbiter EasyConnect Gateway User Manual Doc: HMSI-168-92, Rev. 3.20
Frame Objects 77
14.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 Netbiter EasyConnect Gateway User Manual Doc: HMSI-168-92, Rev. 3.20
Frame Objects 78
14.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
Data Length
Data Location
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.
14.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) (Variable Data Object)
Data 0x00 0x04 Data
Data of arbitrary length End Character Length Character 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 Netbiter EasyConnect Gateway User Manual Doc: HMSI-168-92, Rev. 3.20
Frame Objects 79
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
Fill unused bytes
Filler byte
Data Location
Object Delimiter
(Produce/Query)
Object Delimiter
(Consume/Response)
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
• Enabled a
Fill unused data with the value specified in “Filler byte”.
• Disabled
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
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
End Character Value
No end or length characters included in the received string or generated in the internal memory buffer
End Character value b
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 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 Netbiter EasyConnect Gateway User Manual Doc: HMSI-168-92, Rev. 3.20
Frame Objects 80
14.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.
Error check type combined with
Representation
• ADD (1 byte)
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 Netbiter EasyConnect Gateway User Manual Doc: HMSI-168-92, Rev. 3.20
Chapter 15
15. Commands
This information is only valid for the Master and Generic Data modes. For DF1 master mode, please
refer to “Services” on page 89.
15.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”-pa-
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 83). For DF1 Master Mode, see “Services” on page 89. In Generic Data Mode, no predefined com-
mands exist, but custom ones may be implemented as desired.
15.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 Netbiter EasyConnect Gateway User Manual Doc: HMSI-168-92, Rev. 3.20
Commands 82
15.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 83.
• Edit Command
Edit the currently selected command using the Command Editor.
See also “The Command Editor” on page 83.
• Delete Command
Delete the currently selected command from the list. Note that some commands are fixed and cannot be deleted.
15.2.2 Toolbar Icons
The toolbar features icons for the Add, Edit and Delete Command functions.
Add Command Edit Command
Delete Command
Anybus Communicator Netbiter EasyConnect Gateway User Manual Doc: HMSI-168-92, Rev. 3.20
Commands 83
15.3 The Command Editor
15.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.
15.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 84.
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 Description
Allow Broadcasting Specifies if it is allowed to broadcast the command (only relevant in Master Mode)
Produce
Consume
The command is producing data (Generic Data Mode only)
The command is consuming data (Generic Data Mode only)
Anybus Communicator Netbiter EasyConnect Gateway User Manual Doc: HMSI-168-92, Rev. 3.20
Commands 84
15.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.
15.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
Id
User
This setting is only relevant for Responses in Master Mode.
The value will be retrieved from the corresponding part of the “Query”-transaction.
Value will be retrieved from the “Command ID”-setting (see “Basic Navigation” on page 83).
Settings associated with the object can be edited by the user.
(other settings) Other settings are no longer supported.
Anybus Communicator Netbiter EasyConnect Gateway User Manual Doc: HMSI-168-92, Rev. 3.20
Commands 85
15.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 1
DisplayName Slave Address
Object Type Byte Object
Value [SlaveAddress]
The value of this byte constant will be set using the “SlaveAd-
“Node Parameters” on page 67).
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.
• Example Response
Response 1
DisplayName Slave Address
Object Type Byte Object
Value [SlaveAddress]
This value is linked to the “SlaveAddress” parameter in the parameter window.
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.
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 Netbiter EasyConnect Gateway User Manual Doc: HMSI-168-92, Rev. 3.20
Chapter 16
16. DF1 Protocol Mode
This mode makes the Anybus Communicator act as a DF1 protocol master on the sub-network.
16.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 Netbiter EasyConnect Gateway User Manual Doc: HMSI-168-92, Rev. 3.20
DF1 Protocol Mode 87
16.2 Communicator Parameters
Interface
Currently, only serial communication is supported.
Control/Status Word
(See “Control and Status Registers” on page 102).
Value
Enabled
Description
Enable the Control and Status Registers. The “Data Valid”-bit in the Control Register must be set to start the sub-network 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 sub-network 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
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 Netbiter EasyConnect Gateway User Manual Doc: HMSI-168-92, Rev. 3.20
DF1 Protocol Mode 88
16.3 Sub-network Parameters
Communication
These parameters specify the actual communication settings used for the sub-network.
Parameter
Bitrate (bits/s)
Data bits
Parity
Physical standard
Stop bits
Description
Selects the bit rate
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
Description
Node address of the master, valid values: 0–254
Poll time, active slaves (10 ms) 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 ms a
1000 ms b 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 Netbiter EasyConnect Gateway User Manual Doc: HMSI-168-92, Rev. 3.20
DF1 Protocol Mode 89
16.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 67.
Parameter
Checksum
Slave Address
Type
Description
Selects the type of checksum on the network.
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
16.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 Netbiter EasyConnect Gateway User Manual Doc: HMSI-168-92, Rev. 3.20
DF1 Protocol Mode 90
16.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 Valid settings
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.
Clear
Freeze
Noscanning
Clear
Freeze
The update mode for this service Cyclically
On data change
Single shot
Change of state on trigger
Timing:
Parameter
Retries
Timeout time (10 ms)
Update 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
The minimum time between two services of this kind (in steps of 10 ms) a
Default
3
1000 ms
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
Description
The memory location of the trigger byte this service uses for updates on trigger byte changes
Response Trigger byte Enables/disables the trigger byte
Response Trigger byte address
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
Default
0x05FF
Disabled
0x05FF
Anybus Communicator Netbiter EasyConnect Gateway User Manual Doc: HMSI-168-92, Rev. 3.20
DF1 Protocol Mode 91
16.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.
16.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:
PLC-5
Size range (in bytes)
1–26
SLC500
1–28
MicroLogix
1–26
Data options:
Parameter
Byte swap
Data length
Offset
Description
Determines if the data shall be swapped
The number of bytes, read from the DF1 network, to write to the area determined by the Offset parameter
The offset in the internal memory buffer in the module, where the data shall be read.
Valid settings
No byte swap
Swap words
Swap double words
Size
Anybus Communicator Netbiter EasyConnect Gateway User Manual Doc: HMSI-168-92, Rev. 3.20
16.8 Read Data
This service is used to read data from the nodes in the sub-network.
DF1 Protocol Mode 92
Command Parameters
Parameter Description Valid settings
Element Number The element number of the data file to be accessed within the slave.
PLC-5: 0–999
SLC500: 0–255
MicroLogix: 0–255
File number The file number of the data file to be accessed.
File type The file type of the data to be accessed.
PLC-5: 3, 7, 8, 10–999
SLC500: 3, 7, 8, 10–255
MicroLogix: 3, 7, 8, 10–255
Integer
Bit
Float
Size The number of bytes to read from the slave. One bit/integer element is
2 bytes and one float element is 4 bytes. The parameter must have an even value as only whole elements can be read from the slave.
PLC-5: 2–240
SLC500: 2–236
MicroLogix: 2–242
Data Options
Parameter Description
Byte swap Determines if the data shall be swapped.
Data length The number of bytes, read from the DF1 network, to write to the area determined 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.
-
Valid settings
No byte swap
Swap words
Swap double words
Size
16.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 Netbiter EasyConnect Gateway User Manual Doc: HMSI-168-92, Rev. 3.20
Chapter 17
17. Sub-network Monitor
17.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.
17.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 Netbiter EasyConnect Gateway User Manual Doc: HMSI-168-92, Rev. 3.20
Chapter 18
18. Node Monitor
18.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)
Response Section
Subnetwork
• 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.
Subnetwork
Command Section (Produce)
(Not used)
Anybus Communicator Netbiter EasyConnect Gateway User Manual Doc: HMSI-168-92, Rev. 3.20
Node Monitor 95
18.2 Navigating the Node Monitor
A
B
C
D
A: Drop-down Menu & Toolbar Icons
See “Drop-down Menu” on page 96 and “Toolbar Icons” on page 97.
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 97.
Anybus Communicator Netbiter EasyConnect Gateway User Manual Doc: HMSI-168-92, Rev. 3.20
Node Monitor 96
18.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 Netbiter EasyConnect Gateway User Manual Doc: HMSI-168-92, Rev. 3.20
18.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.
• Select Command & Send Command
These icons corresponds to the functions in the “Command” menu.
See also “Command” on page 96.
Start
Select
• 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.
Stop
Node Monitor 97
Stop
Send
Resume
Refresh
Anybus Communicator Netbiter EasyConnect Gateway User Manual Doc: HMSI-168-92, Rev. 3.20
Chapter 19
19. Data Logger
19.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.
19.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 AS-
CII 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 Netbiter EasyConnect Gateway User Manual Doc: HMSI-168-92, Rev. 3.20
19.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.
Data Logger 99
Anybus Communicator Netbiter EasyConnect Gateway User Manual Doc: HMSI-168-92, Rev. 3.20
Chapter 14
14. Configuration Wizards
14.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.
14.2 Selecting a Wizard Profile
The following window appears each time the Anybus Configuration Manager is started, or upon select-
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 67.
• Blank Configuration
This option creates an empty configuration.
Highlight the desired wizard and click “OK” to continue.
Anybus Communicator Netbiter EasyConnect Gateway User Manual Doc: HMSI-168-92, Rev. 3.20
Configuration Wizards 67
14.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 “EtherCAT”.
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
Specify the sizes of the input and output
data areas. For more information, see
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 Netbiter EasyConnect Gateway User Manual Doc: HMSI-168-92, Rev. 3.20
Chapter 21
21. Control and Status Registers
21.1 General
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 net-
work uses a different byte order, the upper and lower bytes will appear swapped.
21.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
Start
Write to Control Register
Start
CR_HS_CONFIRM=
SR_HS_SEND?
Yes
No
Read Status Register
Set CR_HS_CONFIRM to SR_HS_SEND
Done
SR_HS_CONFIRM=
CR_HS_SEND?
Yes
No
Write to Control Register
Toggle CR_HS_SEND
Done
Anybus Communicator Netbiter EasyConnect Gateway User Manual Doc: HMSI-168-92, Rev. 3.20
Control and Status Registers 103
21.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.
3. Wait until the fieldbus control system and the gateway are online on the fieldbus network, and shift to state B.
A
Offline
(no data exchange)
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.
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)
C: Online (Exchanging data)
Exchanging valid data in both directions.
If the gateway goes offline on the fieldbus, shift to state A.
Start
B
Online
(not yet exchanging data)
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 Netbiter EasyConnect Gateway User Manual Doc: HMSI-168-92, Rev. 3.20
Control and Status Registers 104
21.2 Status Register Contents (Gateway to Control
System)
21.2.1 General Information
The Status Register is (if enabled) located at 0x000–0x001 and constitutes a bit-field as follows:
bit(s) Name
15 Send
(SR_HS_SEND)
14
13
Confirm
(SR_HS_CONFIRM)
Data Valid
(Master Mode and DF1
Master Mode Only)
12... 8 Status Code
Description
These bits control the handshaking towards the fieldbus control system.
See also...
- “Handshaking Procedure” on page 102
- “Control Register Contents (Control System to Gateway)” on page 106
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.
7... 0 Data
See also...
- “Status Codes in Master Mode and DF1 Master Mode” on page 104
- “Status Code in Generic Data Mode” on page 105
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.
21.2.2 Status Codes in Master Mode and DF1 Master Mode
(This table is valid only in Master Mode and DF1 Master Mode).
Code Condition
0x00 Retransmission
Counter Updated
Type
Warning
0x01 Single Node Missing Error
0x02 Multiple Nodes Missing Error
0x03 Buffer Overrun Warning
0x04 Other Error
0x1F No Error
Error
Warning
Data Description
Counter 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
-
Slave address
A node returned more data than expected.
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 Netbiter EasyConnect Gateway User Manual Doc: HMSI-168-92, Rev. 3.20
Control and Status Registers 105
21.2.3 Status Code in Generic Data Mode
(This table is valid only in Generic Data Mode).
Code Condition
0x00 Invalid Transaction
Counter Updated
0x01 Frame Error
0x02 Offline Timeout
Counter Updated
0x03 Buffer Overrun
0x04 Other Error
0x1F No Error
Type
Error
Warning -
Error Counter
Warning -
Error
Warning -
-
Data
Counter
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 73 (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 Netbiter EasyConnect Gateway User Manual Doc: HMSI-168-92, Rev. 3.20
Control and Status Registers 106
21.3 Control Register Contents (Control System to
Gateway)
21.3.1 General Information
The Control Register is (if enabled) located at 0x200–0x201 and constitutes a bit-field as follows:
bit(s) Name
15 Confirm
(CR_HS_CONFIRM)
14 Send
(CR_HS_SEND)
Description
These bits control the handshaking towards the gateway.
13 Data Valid
12 Execute Command
11... 8 Control Code
See also...
- “Handshaking Procedure” on page 102
- “Status Register Contents (Gateway to Control System)” on page 104
This bit controls data consistency (see “Data Consistency” on page 103).
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).
7... 0 Data
See also...
- “Control Codes in Master Mode and DF1 Master Mode” on page 106
- “Control Codes in Generic Data Mode” on page 106
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.
21.3.2 Control Codes in Master Mode and DF1 Master Mode
(This table is valid only in Master Mode and DF1 Master Mode).
Code Instruction
0x00 Disable Node
0x01 Enable Node
0x02 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.
21.3.3 Control Codes in Generic Data Mode
(No Control Codes are currently supported in this mode).
Anybus Communicator Netbiter EasyConnect Gateway User Manual Doc: HMSI-168-92, Rev. 3.20
Chapter 23
23. Advanced Fieldbus Configuration
23.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.)
23.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.
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).
A
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 Netbiter EasyConnect Gateway User Manual Doc: HMSI-168-92, Rev. 3.20
Appendix A
A. Connector Pin Assignments
A.1 EtherCAT Connectors
4
5
2
3
6
7
Pin Signal
Housing Cable Shield
1 TD+
TD-
RD+
Termination
Termination
RD-
Termination
8 Termination
A.2 Power Connector
Pin
1
2
Description
+24 VDC
GND
Notes:
• Use 60/75 or 75 °C copper (Cu) wire only.
• Minimum terminal tightening torque: 5–7 lb-in (0.5–0.8 Nm).
1 8
1 2
Anybus Communicator Netbiter EasyConnect Gateway User Manual Doc: HMSI-168-92, Rev. 3.20
Connector Pin Assignments 75
A.3 PC Connector
Configuration Cable Wiring
RS232 Rx
DP9F (PC)
1
2
RS232 Tx 3
4
Ground
7
8
5
6
9
2
3
Pin
1
4
RJ11 (4P4C modular)
1
: ABC
Description
Signal ground
RS232 Rx (Input)
RS232 Tx (Output)
DB9F : PC
Pin
1
2
3
4
5
6 - 9
Description
-
RS232 Rx (Input)
-
RS232 Tx (Output)
-
Signal Ground
RJ11 (ABC)
Ground 1
2 Ground
3
4
Rx
Tx
4
3
2
1
5 (female) 1
9 6
1. The RJ11 (4P4C modular) is sometimes referred to as an RJ9.
Anybus Communicator Netbiter EasyConnect Gateway User Manual Doc: HMSI-168-92, Rev. 3.20
Connector Pin Assignments 76
A.4 Subnetwork Interface
A.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.
A.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.
A.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 Ω.
A.4.4 Connector Pinout (DB9F)
2
3
Pin
1
4
5
Description
+5 V Output (100 mA max)
RS232 Rx
RS232 Tx
(reserved)
Signal Ground a
8
9
6
7
RS422 Rx +
RS422 Rx -
RS485 + / RS422 Tx+
RS485 - / RS422 Tx-
(housing) Cable Shield
RS232
RS422
RS485
5 (female) 1
9
RS485
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 Netbiter EasyConnect Gateway User Manual Doc: HMSI-168-92, Rev. 3.20
Connector Pin Assignments 77
A.4.5 Typical Connection (RS485)
+5V
470R
RS485 +
120R
RS485 -
470R
Signal
Ground
Cable
Shield
Anybus Communicator Node Node
RS485 +
120R
RS485 -
Signal
Ground
A.4.6 Typical Connection (RS422 & 4-Wire RS485)
+5V
470R
RS422 Rx+
120R
RS422 Rx-
470R 470R
RS422 Tx+
RS422 Tx+
RS422 Tx-
RS422 Rx+
120R
RS422 RxRS422 Tx-
470R
Signal
Ground
Cable
Shield
Anybus Communicator
Signal
Ground
Device
Note: Bias resistors are normally not needed on RS422, but may be required when using 4-wire RS485.
A.4.7 Typical Connection (RS232)
RS232 Tx RS232 Rx
RS232 Rx
Signal
Ground
Cable
Shield
Anybus Communicator
Node Node End Node
RS232 Tx
Signal
Ground
Device
Anybus Communicator Netbiter EasyConnect Gateway User Manual Doc: HMSI-168-92, Rev. 3.20
B. Technical Specification
B.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”)
B.2 Electrical Characteristics
Power Supply
Power: 24 VDC ± 10%
Power Consumption
Maximum power consumption is 280 mA on 24 VDC. Typically around 100 mA.
B.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
Appendix B
Anybus Communicator Netbiter EasyConnect Gateway User Manual Doc: HMSI-168-92, Rev. 3.20
Technical Specification 76
B.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 Netbiter EasyConnect Gateway User Manual Doc: HMSI-168-92, Rev. 3.20
Technical Specification 77
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:
20
18
16
Control circuit wire size
AWG mm²
22 0.32
14
12
0.52
0.82
1.3
2.1
3.3
5
7
10
Maximum protective device rating
Amperes
3
20
25
Galvanic isolation on sub-network interface
• EN 60950-1 (2001)
Pollution Degree 2
Material Group IIIb
250 V
RMS
or 250 VDC working voltage
500 V secondary circuit transient rating
Anybus Communicator Netbiter EasyConnect Gateway User Manual Doc: HMSI-168-92, Rev. 3.20
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
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.
Anybus Communicator Netbiter EasyConnect Gateway User Manual Doc: HMSI-168-92, Rev. 3.20
Appendix E
E. ASCII Table
0x
1x
2x
3x
4x
5x
6x
7x x0 x1 x2 x3 x4 x5 x6 x7 x8 x9 xA xB xC xD xE xF
a
97 q
113
A
65
Q
81
!
33
1
49
SOH
1
DC1
17
`
96 p
112
@
64
P
80
(sp)
32
0
48
NUL
0
DLE
16 b
98 r
114
B
66
R
82
"
34
2
50
STX
2
DC2
18
ETX
3
DC3
19
#
35
3
51
C
67
S
83 c
99 s
115
EOT
100 t
4
DC4
20
$
36
4
52
D
68
T
84 d
116
ENQ
5
NAK
21
%
37
5
53
E
69
U
85 e
101 u
117
ACK f
6
SYN
22
&
38
6
54
F
70
V
86
102 v
118
BEL
7
ETB
23
'
39
7
55
G
71
W
87 g
103 w
119
BS
8
CAN
24
(
40
8
56
H
72
X
88 h
104 x
120 i
105 y
121
I
73
Y
89
)
41
9
57
HT
9
EM
25
LF
10
SUB
26
*
42
:
58
74
90 j
J
Z
106 z
122
VT
11
ESC
27
;
+
43
59
K
75
[
91 k
107
{
123
FF
12
FS
28
44
60
\
,
<
L
76
92 l
108
|
124 m
109
}
125
M
77
]
93
-
45
=
61
CR
13
GS
29 n
110
~
126
N
78
^
94
.
46
>
62
SO
14
RS
30 o
111
DEL
127
O
79
_
95
/
47
?
63
SI
15
US
31
Anybus Communicator Netbiter EasyConnect Gateway User Manual Doc: HMSI-168-92, Rev. 3.20
advertisement
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project