User Manual

Anybus® Communicator™ for PROFIBUS
Rev. 2.53

HMS Industrial Networks AB  Germany + 49 - 721 - 96472 - 0 Japan + 81 - 45 - 478 -5340 Sweden + 46 - 35 - 17 29 20 U.S.A. + 1 - 312 - 829 - 0601 France + 33 - 3 89 32 76 76 Italy + 39 - 347 - 00894 - 70 China + 86 - 10 - 8532 - 3183

 ge-sales@hms-networks.com jp-sales@hms-networks.com sales@hms-networks.com us-sales@hms-networks.com fr-sales@hms-networks.com it-sales@hms-networks.com cn-sales@hms-networks.com

Table of Contents

Table of Contents
Preface About This Document
How To Use This Document ............................................................................................................ P-1 Important User Information .............................................................................................................. P-1 Related Documents.............................................................................................................................. P-2 Document History ............................................................................................................................... P-2 Conventions & Terminology.............................................................................................................. P-3 Glossary ................................................................................................................................................. P-3 Support .................................................................................................................................................. P-4

Chapter 1

About the Anybus Communicator for PROFIBUS
External View ........................................................................................................................................1-2 Status LEDs ...........................................................................................................................................1-3 Configuration Switches ........................................................................................................................1-3 Hardware Installation ...........................................................................................................................1-4 Software Installation .............................................................................................................................1-5 ABC Config Tool.........................................................................................................................1-5

Chapter 2

Basic Operation
General....................................................................................................................................................2-1 Data Exchange Model ..........................................................................................................................2-2 Memory Map................................................................................................................................2-2 Data Exchange Example.............................................................................................................2-3 Sub-Network Protocol .........................................................................................................................2-4 Protocol Modes..............................................................................................................................2-4 Protocol Building Blocks ...............................................................................................................2-4 Master Mode ................................................................................................................................2-5 Generic Data Mode ......................................................................................................................2-5 Data Representation on PROFIBUS .................................................................................................2-6 General.........................................................................................................................................2-6 Data Representation .....................................................................................................................2-6 Memory Layout (Internal Memory Buffer).....................................................................................2-6

Chapter 3

Navigating the ABC Config Tool
Main Window ........................................................................................................................................3-1 Pull-down Menu ...........................................................................................................................3-2 Toolbar Icons ................................................................................................................................3-5

Chapter 4

Basic Settings
Fieldbus Settings....................................................................................................................................4-1 ABC Parameters ....................................................................................................................................4-2 Sub-Network Parameters .....................................................................................................................4-3

............................................................................................................................................................................................................................................................................................10-4 Toolbar Icons ....7-1 Adding and Editing Frame Objects ......................................................................8-5 Example: Specifying a Modbus-RTU Command in Master Mode ...................................7-1 Constant Objects (Byte...............................................6-3 Transaction Parameters (Generic Data Mode)..................................................................................................................................................................................................................................................................................................................................................................................6-4 Transaction Editor ....................................................................7-4 Variable Data Object ..............................................................................................................................................................................................................................................8-1 Adding & Managing Commands ....................................7-3 Data Object ..................................................................................................................................................6-1 Transaction Parameters (Master Mode)......................................................................................................................................Table of Contents 3 Chapter 5 Nodes General.................................6-5 Chapter 7 Frame Objects General......................................................................................................................................................................................................................................5-1 Chapter 6 Transactions General...................................................................................................5-1 Node Parameters......................................8-2 Toolbar Icons ....................................................................................................................................................................................................................................................................................................................................................................10-4 .............................................7-2 Limit Objects (Byte..................................................................................................... Dword) ...........................................................................................6-2 Parameters (Query & Broadcast)..........6-1 Adding & Managing Transactions .....................................................................................................................................................6-3 Consume-Transactions ..............................................................8-3 General..................................................................................................................................................................................................................................................................................................................................7-6 Chapter 8 Commands General...................................................................................................................................................10-1 Navigating the Node Monitor.......................................................................8-3 Basic Navigation ..................10-3 ............................................................ Dword). Word........... Word.......................................................................................................................8-3 Pull-down Menu ......................10-2 Pull-Down Menu.......................................................7-4 Checksum Object ....................................................................6-2 Parameters (Response)........................................6-3 Produce-Transactions .........................................................................8-2 The Command Editor .................8-6 Chapter 9 Chapter 10 Sub Network Monitor Node Monitor General....................8-4 Editing a Command ............5-1 Adding & Managing Nodes....................................................................................................................................................................................................................................................................8-1 Pull-Down Menu..............................................................................

................. B-1 Electrical Characteristics .................................................................................13-2 Status Register Contents (Gateway to Control System)............................13-5 Chapter 14 Advanced Fieldbus Configuration General............................................................................................................................ B-1 ..................................................................................................Table of Contents 4 Chapter 11 Data Logger General...................................................................................A-5 Typical Connection (RS232)....................................................................................................................... B-1 Environmental Characteristics ........................................................13-5 Control Codes in Master Mode .........................................................................................................................................A-5 Typical Connection (RS422 & 4-Wire RS485) ...............................................................................................................................................................................................14-1 Mailbox Editor...............................................................................................Modbus RTU Master ....................................................................................................13-1 Data Consistency .....................................................................................................................................................................................12-1 Selecting a Wizard Profile ...................................................................................................... A-4 Typical Connection (RS485)...........................................................................................................................................................................................................................................................................................................13-3 General Information.....................................................................13-3 Status Codes in Master Mode .............................................................................13-5 Control Codes in Generic Data Mode ...........................A-3 General Information........................................................................................... A-3 Termination (RS485 & RS422 Only) ........12-2 Chapter 13 Control and Status Registers General.............A-1 Power Connector ....................................................................................................................................................................................................................................................11-1 Operation.............................13-3 Control Register Contents (Control System to Gateway)...............11-1 Configuration ................................................................................................................................................................................................11-2 Chapter 12 Configuration Wizards General....................13-1 Handshaking Procedure ................................A-3 Bias Resistors (RS485 Only)...................................................................................13-5 General Information..............................................................................................................................................A-5 .............................. A-3 Connector Pinout (DB9F) .....................................................14-1 Appendix A Connector Pin Assignments PROFIBUS Connector ........................................................................................12-1 Wizard ..................................................................................................................................................... A-1 PC Connector ..............................................................13-3 Status Code in Generic Data Mode ................................................................................................................................................................................................ A-6 Appendix B Technical Specification Mechanical Properties.........................................................................................................................................................................................................................................................................................................A-2 Sub-network Interface .........................................................................................................................................................................................................................................................................

.............Table of Contents 5 Regulatory Compliance ....................................... B-2 Appendix C Troubleshooting Appendix D ASCII Table ....................................................................

Anybus® is a registered trademark of HMS Industrial Networks AB.Preface About This Document How To Use This Document This document contains a general introduction as well as a description of the technical features provided by the Anybus Communicator. We. ESD Note: . The reader is also expected to be familiar with the Microsoft Windows operating system. and standards. The reader of this document is expected to be familiar with PLC and software design. Warning: This is a class A product. Static control precautions are required when handling the product. This product contains ESD (Electrostatic Discharge) sensitive parts that may be damaged if ESD control procedures are not followed. The examples and illustrations in this document are included solely for illustrative purposes. All other trademarks are the property of their respective holders. regulations. Those responsible for the use of this device must ensure that all the necessary steps have been taken to verify that the application meets all performance and safety requirements including any applicable laws. The information in this document is subject to change without notice and should not be considered as a commitment by HMS Industrial Networks AB. Failure to observe this may cause damage to the product. HMS Industrial Networks AB. codes. as well communication systems in general. HMS Industrial Networks AB assumes no responsibility for any errors that may appear in this document. In a domestic environment this product may cause radio interference in which case the user may be required to take adequate measures. Important User Information The data and illustrations found in this document are not binding. reserve the right to modify our products in line with our policy of continuous product development. There are many applications of this product. HMS cannot assume responsibility or liability for actual use based on these examples and illustrations. including the PC-based configuration software. Because of the many variables and requirements associated with any particular implementation.

About This Document P-2 Related Documents Document name ABC-PDP Installation Leaflet Author HMS Document History Summary of Recent Changes (2.01 2.50 2..53) Change Minor corrections & updates Updated status led indications Updated behavior of parameter “On data change” Page(s) 1-3 6-2 .52. minor corrections & updates Corrected Control..6-4 Revision List Revision 2.00 2.53 Date 2003-06-24 2004-03-08 2005-02-04 2006-03-27 2006-12-22 2007-06-01 2009-04-23 Author PeP PeP PaL PeP PeP PeP KeL Chapter All 10 A All 13 All Description 2nd major release Corrected Control Codes Added recomended PROFBUS connectors Major rewrite Misc. 2. minor corrections and updates .and Status Word definitions Misc.02 2.51 2.52 2.

Monitor A tool for debugging the ABC and the network connections. User Person or persons responsible for installing the Anybus Communicator Higher Level Network In this case. because their meaning depend on which end of the link is being referenced. not procedural steps The term ‘user’ refers to the person or persons responsible for installing the Anybus Communicator in a network. the terms “input” and “output” can be ambiguous. Configuration List of configured nodes with transactions on the sub-network.About This Document P-3 Conventions & Terminology The following conventions are used throughout this document: • • • • • • • Numbered lists provide sequential steps Bulleted lists provide information. Fieldbus The higher level network to which the communicator is connected. The convention in this document is that “input” and “output” are always being referenced to the master/scanner end of the link. Node A device in the configuration which defines the communication with a node on the sub-network The network that is logically located on a subsidiary level with respect to the fieldbus. Hexadecimal values are written in the format 0xNNNN. Decimal values are represented as NNNN where NNNN is the decimal value As in all communication systems. PROFIBUS Network Fieldbus . Fieldbus Control System Fieldbus master Frame Object Low level entities which are used to describe the different parts of a Transaction. Transaction A generic building block that is used in the sub-network configuration and defines the data that is sent and received on the sub-network. and to Sub-network which the ABC acts as a gateway. PDP PROFIBUS-DP Command A pre-defined transaction. where NNNN is the hexadecimal value. Glossary Term ABC Meaning Anybus® Communicator™ Broadcaster A protocol-specific node in the configuration that handles transactions destined to all nodes. The term ‘ABC’ refers to the Anybus Communicator.

com .17 29 20 +46 (0) 35 .com +39 039 59662 27 +39 039 59662 31 www.com +1-312-829-0605 888-8-Anybus +1-312-738-5873 www.17 29 09 www. or contact the nearest support centre: HMS Sweden (Head Office) E-mail: Phone: Fax: Online: HMS North America E-mail: Phone: Toll Free: Fax: Online: HMS Germany E-mail: Phone: Fax: Online: HMS Japan E-mail: Phone: Fax: Online: HMS China E-mail: Phone: Online: HMS Italy E-mail: Phone: Fax: Online: HMS France E-mail: Phone: Fax: Online: mta@hms-networks.anybus.anybus.com +46 (0) 35 .anybus.com +81-45-478-5340 +81-45-476-0315 www.About This Document P-4 Support For technical support consult the online FAQ (www.com us-support@hms-networks.anybus.anybus.com jp-support@hms-networks.com it-support@hms-networks.anybus.com).com +86 10 8532 3023 www.anybus.com +49-721-96472-0 +49-721-964-7210 www.com cn-support@hms-networks.anybus.com support@hms-networks.com +33 (0) 3 89 32 76 41 +33 (0) 3 89 32 76 31 www.com ge-support@hms-networks.

About This Document P-5 .

control and reliability. Integration of industrial devices is enabled without loss of functionality. acts as a gateway between virtually any serial application protocol and a PROFIBUS DP-based network. both when retro-fitting to existing equipment as well as when setting up new installations. • • • • Complete PROFIBUS-DP slave functionality according to IEC 61158 Supports all common baudrates up to 12Mbit (detected automatically) Up to 244 bytes of I/O data in each direction (or 416 bytes in total) Galvanically isolated bus electronics . or ‘ABC’. and supports the following physical standards: • • • RS-232 RS-422 RS-485 PROFIBUS Interface PROFIBUS connectivity is provided through patented Anybus technology.g a PLC) HMI INVERTER HMI INVERTER PC configuration and monitoring PC configuration and monitoring Multi-drop up to 31 nodes Serial communication devices Serial communication device Single-Node Serial Sub Network Multi-Node Serial Sub Network Sub Network The ABC can address up to 31 nodes. PROFIBUS Master (e.g a PLC) (PROFIBUS Network) (PROFIBUS Network) PROFIBUS Master (e. a proven industrial communication solution used all over the world by leading manufacturers of industrial automation products.Chapter 1 About the Anybus Communicator for PROFIBUS The Anybus Communicator for PROFIBUS.

A-1 “PROFIBUS Connector” C B: Configuration Switches See also. See also..1-3 “Status LEDs” D D: PC-connector This connector is used to connect the ABC to a PC for configuration and monitoring purposes.A-1 “Power Connector” . .1-4 “Hardware Installation” E G F .A-2 “PC Connector” E: Sub-network Connector This connector is used to connect the ABC to the serial sub-network.B-1 “Technical Specification” G: DIN-rail Connector The DIN-rail mechanism connects the ABC to PE (Protective Earth)...1-4 “Hardware Installation” .. .. ...1-4 “Hardware Installation” .1-3 “Configuration Switches” A B C: Status LEDs See also. A: PROFIBUS Connector This connector is used to connect the ABC to the fieldbus.... . See also.A-3 “Sub-network Interface” F: Power Connector This connector is used to apply power to the ABC.... . . See also.1-4 “Hardware Installation” . .About the Anybus Communicator for PROFIBUS 1-2 External View For wiring and pin assignments. See also. see A-1 “Connector Pin Assignments”.. See also.

If a timeout occurs on a transaction. flashing Green Red 6 . If tools are used when opening the hatch. but one or more transaction error(s) have occurred Running Transaction error/timeout or subnet stopped Power off Invalid or missing configuration Initializing Running If the Device status LED is flashing in a sequence starting with one or more red flashes. flashing Status Not online Online Not offline Offline No diagnostics present Error in configuration Error in user parameter data Error in initialisation Power off Running correctly. the ABC requires a reset for any changes to have effect. flashing 1Hz Red. . flashing 2Hz Red. This led turns green when all transactions have been active at least once. i.Device Status Off Alternating Red/Green Green Green. Configuration Switches The configuration switches are used to set the PROFIBUS node address.(Not used) 4 . set switch A to ‘2’ and switch B to ‘4’.Fieldbus Diag Off Red.e. Note that the node address can not be changed during runtime. This includes any transactions using “change of state” or “change of state on trigger”. flashing 4Hz a Off 5 . this led will turn red. be cautious. please note the sequence pattern and contact the HMS support department 1 3 5 2 4 6 a.Fieldbus Online Off Green 2 . B A Example: If the node address should be 42. Normally.About the Anybus Communicator for PROFIBUS 1-3 Status LEDs # State 1 . these switches are covered by a plastic hatch. The configuration is done using two rotary switches as follows: Node Address = (Switch B x 10) + (Switch A x 1) Note: When removing the hatch. flashing Red. avoid touching the circuit boards and components.Subnet Status Green.Fieldbus Offline Off Red 3 .

Set up the PROFIBUS communication in accordance with the ABC configuration . Set the PROFIBUS node ID (see 1-3 “Configuration Switches”) 4. Connect the ABC to the PROFIBUS-DP network 3. select the correct port manually in the “Port”-menu). Snap the ABC on to the DIN-rail (See 1-2 “DIN-rail Connector”) The DIN-rail mechanism works as follows: 1 To snap the ABC on. then push it against the DIN-rail as to make it snap on (2) 2 1 To snap the ABC off. 2 2. as to make it snap off from the DIN-rail. 6. Connect the ABC to the PC via the Configuration Cable.About the Anybus Communicator for PROFIBUS 1-4 Hardware Installation Perform the following steps when physically installing the ABC: 1. push the it downwards (1) and pull it out from the DIN-rail (2). Start the ABC Config program on the PC (The ABC Config software attempts to detect the serial port automatically. If not successful. 8. Connect the power cable and apply power 7. first press the it downwards (1) to compress the spring in the DIN-rail mechanism. Connect the ABC to the serial sub-network 5. Configure the ABC using the ABC Config Tool and download the configuration 9.

right-click on the CD-drive icon and select Explore.anybus.exe’ and follow the onscreen instructions. . Execute ‘setup.com).About the Anybus Communicator for PROFIBUS 1-5 Software Installation ABC Config Tool System requirements • • • • • • Pentium 133 MHz or higher 10 MB of free space on the hard drive 8 MB RAM Screen resolution of 800x600 (16 bit colour) or higher Microsoft Windows™ NT4 / 2000 / XP Internet Explorer 4. • From website Download and execute the self-extracting . If the installation does not start automatically.01 SP1 or newer Installation • Anybus Communicator resource CD Insert the CD and follow the on-screen instructions.exe-file from the HMS website (www.

It can also monitor certain aspects of the sub-network communication and notify the higher level network when data has changed. Unlike most other gateway devices of similar kind. a Windows™ application which is used to supply the ABC with a description of the sub-network protocol. No programming skills are required. and can be configured to handle almost any form of serial communication. An essential part of the Anybus Communicator package is the ABC Config Tool. it does not have a fixed protocol for the sub-network.Chapter 2 Basic Operation General The ABC is designed to exchange data between a serial sub-network and a higher level network. or based on trigger events issued by the control system of the higher level network (i.e. the fieldbus master or PLC). on change of state. instead. a visual protocol description-system is used to specify the different parts of the serial communication. The ABC can issue serial telegrams cyclically. .

and can be used for transfers between individual nodes on the sub-network. (how this data is represented on the higher level network will be described later in this chapter). The ABC can handle up to 1024 bytes of General Data. the data exchanged on the sub-network. The very same memory locations can then be exchanged on the sub-network. the higher level network simply reads and writes data to memory locations specified using the ABC Config Tool. This means that in order to exchange data with the subnetwork. or as a general “scratch pad” for data.Basic Operation 2-2 Data Exchange Model Internally. resides in the same memory. the different areas described above are mapped to the memory locations (addresses) specified below. • General Data Output Data (244 bytes) General Data This area is not exchanged on the higher level network. Sub-Network ABC Internal Memory Input Data (244 bytes) The internal memory buffer is divided into three areas based on their function: • Input Data (Up to 244 bytes) This area can be read by the higher level network. (how this data is represented on the higher level network will be described later in this chapter). and the data exchanged on the higher level network. The actual size of this area depends on the amount of data that is exchanged on the sub-network. Memory Map When building the sub-network configuration using the ABC Config Tool. Input Data 0x000 0x200 Output Data 0x400 General Data Sub-Network: Read/Write Fieldbus: Read Only Sub-Network: Fieldbus: Read Only Read/Write Sub-Network: Fieldbus: Read/Write - 0x0F3 0x2F3 0x??? Higher Level Network . • Output Data (Up to 244 bytes) This area can be written to by the higher level network.

holding the Setpoint Temperature and the Actual Temperature respectively. via the internal memory buffers in the ABC. and PLC Output Memory is copied to the Output Data area.Basic Operation 2-3 Data Exchange Example In the following example. PROFIBUS ABC Input Data 0x000 Output Data 0x200 General Data 0x400 Actual Temperature Temperature Setpoint (not used in this example) 0x1FF 0x3FF 0x??? The ABC copies the TemperatureSetpoint from the Output Data area to the Input Register in the TemperatureRegulator. Sub-Network Serial Device . The PLC Memory associated with the ABC is exchanged. The ABC copies the Output Register of the Temperature Regulator to the InputData area. Data from the Input Data area is copied to PLC Input Memory. a temperature regulator on the sub-network exchanges information with a PLC on the higher level network. PLC (PROFIBUS Master) PLC Memory (Inputs) PLC Memory (Outputs) Actual Temperature Temperature Setpoint The PLC exchange data between the internal PLC memory and the slaves (in this case the ABC) on the PROFIBUS network.Temperature Regulator The Temperature Regulator has two registers. Output Register Actual Temperature Input Register Temperature Setpoint .

see 2-5 “Master Mode”. A Frame Object can represent a fixed value (a constant). • Transaction A ‘Transaction’ represents a complete serial telegram. any node on the sub-network. This simplifies common operations by allowing Transactions to be stored and re-used. including the ABC. see below. • Node A node represents a single device on the sub-network. the ABC acts as a master on the sub-network. • Frame Object ‘Frame Objects’ are low level entities used to compose a Transaction (see above). Each Transaction is associated with a set of parameters controlling how and when to use it on the sub-network. called ‘Master Mode’ and ‘Generic Data Mode’. Each node can be associated with a number of Transactions.Basic Operation 2-4 Sub-Network Protocol Protocol Modes The ABC features two distinct modes of operation regarding the sub-network communication. • Master Mode In this mode. a range of values (limit objects). and the serial communication takes place in a Query-Response fashion. not the actual sub-network protocol. Protocol Building Blocks The following building blocks are used in ABC Config Tool to describe the sub-network communication. see 2-5 “Generic Data Mode”. • Generic Data Mode In this mode. a block of data or a calculated checksum. Note that the protocol mode only specifies the basic communication model. . and consists of a number of Frame Objects (see below). may spontaneously produce or consume messages. • Commands A ‘Command’ is simply a pre-defined Transaction stored in a list in the ABC Config Tool. For more information about this mode. How these blocks apply to the two protocol modes will be described later in this document. there is no master-slave relationship between the sub-network nodes and the ABC. For more information about this mode. The nodes on the network are not permitted to issue messages unless they have been addressed by the ABC first.

the communication is based on a Query/Response scheme. may spontaneously produce or consume a message. In Master Mode.e. There is one exception to this rule.Basic Operation 2-5 Master Mode In this mode. when the ABC issues a Query on the sub-network. Nodes are not permitted issue Responses spontaneously. i. Any node. which can conveniently be reached by right-clicking on a node in the ABC Config Tool and selecting ‘Insert New Command’. without expecting them to respond to the broadcasted message. Most protocols offer some way of broadcasting messages to all nodes on the network. ABC Config Tool comes pre-loaded with most commonly used Modbus RTU commands. the data received from the higher level network is used to ‘Produce’ a message on the sub-network to be ‘Consumed’ by a node. This also works the other way around. This ‘Consumed’ data can then be accessed from the higher level network. the Broadcaster. the ABC ‘Consumes’ data that is ‘Produced’ by a node on the sub-network. Generic Data Mode In this mode. including the ABC. nor do they have to wait for a query in order to send one. Nodes do not have to respond to messages. the addressed node is expected to issue a Response to that Query. which features a dedicated Broadcaster node. . Note however that this does not in any way prevent other protocols based on the same Query-Response message-scheme to be implemented. In the figure above. without first receiving a Query. This is also reflected in the ABC. there is no master-slave relationship between the nodes on the sub-network and the ABC.

anybus.. it does not initiate communication towards other nodes on itself. see 9-1 “Sub Network Monitor”. The latest version of the GSD-file for the ABC can be downloaded from the HMS website. make sure that the I/O sizes in the PROFIBUS master match the actual sizes used by the ABC. The amount of data exchanged on the bus depends on the configuration in the ABC.0x21F 0x220 = 128 bytes = 32 bytes (0x0080) (0x0020) Output Data PROFIBUS Output Data 0x400 General Data (Not represented on PROFIBUS) (Not used) (Not used) 0x1FF 0x3FF 0x??? . www. Memory Layout (Internal Memory Buffer) The data in the Input..and Output Data areas is represented as continuous blocks of I/O data as follows: Example: In this example. As such. the I/O Sizes for the ABC has been set to the following values: IO Size In IO Size Out Resulting memory layout: Input Data 0x000 PROFIBUS Input Data 0x07F 0x080 0x200. but can be read from / written to by a PROFIBUS master. Data Representation The Input and Output Data areas in the internal memory buffer are represented as PROFIBUS I/O data.Basic Operation 2-6 Data Representation on PROFIBUS General The ABC acts as a slave on the PROFIBUS network. When setting up the PROFIBUS communication.com. The data sizes can be viewed at any time in the Sub-network Monitor.

namely Fieldbus. ABC and Sub-network. To gain access to these parameters. ‘0x2A’). Parameter Section • D: Information Section This section holds information related to the currently selected parameter. Sub-entries This menu entry holds additional sub-entries / parameters • C: Parameter Section This section holds a list of parameters or options related to the currently selected entry in the Navigation Section. or in hexadecimal format (e. depending on the parameter itself. The Tool Bar provides quick access to the most frequently used functions. the entry must be expanded by clicking ‘+’.g. This menu entry is expanded • B: Navigation Section This section is the main tool for selecting and altering different levels of the sub-network configuration. There are three main levels in the navigation window. Right-clicking on entries in this section brings out additional selections related to that particular entry. Entries preceded by a ‘+’ holds further configuration parameters or ‘sub menus’. ‘42’).g.Chapter 3 Navigating the ABC Config Tool Main Window The main window in the ABC Config Tool can be divided in 4 sections as follows: A C B D • A: Pull-down Menus & Tool Bar The second drop-down menu from the left will change depending on the current context. Information Section . The parameter value may be specified either using a selection box or manually. Values can be specified in decimal form (e.

CAUTION: Always keep a copy of the password in a safe place. • Print. A lost password cannot be retrieved! • Exit Close the ABC Config Tool. Save the current configuration under a new name. • Save Save the current configuration.. . This brings out the following window: Item Select a Name for the Configuration Download Password(6) Upload Password(6) Description A name for the configuration may be entered here These fields can be used to password-protect the configuration in the gateway.. See also 12-1 “Configuration Wizards”.. Send details about the current configuration to a printer.. • Save As. • Properties...Navigating the ABC Config Tool 3-2 Pull-down Menu File This menu features the following entries: • New Create a new configuration. • Open. Open a previously created configuration...

Cick ‘Apply’ to validate the new settings. Language next time the Selects which language to use. • Options This will bring out the following window: Item Warning on Delete Description A confirmation dialog is displayed each time something is deleted.Navigating the ABC Config Tool 3-3 Tools This menu features the following entries: • Port This entry selects the COM-port used for the configuration of the gateway. Warning: Use with caution. Selecting the ‘ABC’-tab will reveal additional properties: Item Size of logbuffer Description By default. Warning on unsaved A confirmation dialog is displayed when data closing the ABC Config Tool with unsaved data.. it is possible to specify a different number of entries (valid settings range from 1. • Download configuration to ABC Download the current configuration into the gateway. Download firmware to the embedded fieldbus interface. the Data Logger can log up to 512 entries in each direction. When selected. The new program is launched setting will be active the next time the program is launched. Creates an error log file Firmware Download Factory Restore Block Configuration Create Error log . Show Wizard when The Wizard is displayed each time a new “New” menu is selected configuration is created. • Start Logging Start the Data Logger (see 11-1 “Data Logger”).512).. See also 11-1 “Data Logger”. this menu-entry is changed to ‘Stop Logging’. If necessary. Restores the gateway firmware to it’s original state (does not affect the embedded fieldbus interface). the downloaded configuration will not be executed by the gateway. Warning: Use with caution. • Upload configuration from ABC Upload the configuration from the gateway to the ABC Config Tool. Note that when the Data Logger is active.

Note: At the time of writing. Help This menu features the following entries: • Contents Display the table of contents of the on-line help system.. • Status Bar This entry enables/disables the status bar at the bottom of the main window. Note: At the time of writing. • Search For Help On.Navigating the ABC Config Tool 3-4 View This menu features the following entries: • Toolbar This entry enables/disables the toolbar icons at the top of the main window... • About. no on-line help system exists. Search for a particular topic in the on-line help system. no on-line help system exists. Display general information about the gateway and the current build of ABC Config Tool.. .

Delete. Add Command • Add Mailbox (Advanced functionality. see 14-1 “Mailbox Editor”) Add Mailbox • Add Node & Add Broadcaster These icons are used to add nodes to the configuration. • New. Start Log. • Sub-Network Monitor Clicking on this icon will launch the Sub-network Monitor (see 9-1 “Sub Network Monitor”). Stop Log. Insert These icons are used for common editing functions in the navigation section.Navigating the ABC Config Tool 3-5 Toolbar Icons The toolbar features icons for the most commonly used functions. Add Transactions Add Transaction . Open & Save See 3-2 “File”. Node Broadcaster • Node Monitor Clicking on this icon will launch the Node Monitor (see 10-1 “Node Monitor”) Node Monitor • Add Transaction(s) These icons are used to add transactions to the currently selected node. Sub-Network Monitor • Add Command This icon is used to add commands to the currently selected node. Paste. Upload Download New Open Save • Up one Level Clicking on this icon will move the selection in the navigation section. Up one Level • Cut. Disconnect • Start Logging & Stop Logging See 3-3 “Tools” & 11-1 “Data Logger”. Connect • Disconnect Clicking on this icon will cause the ABC Config Tool to disconnect from the gateway. Cut Copy Paste Delete Insert • Connect Clicking on this icon will cause the ABC Config Tool to attempt to connect to the gateway. Copy. • Upload from ABC & Download to ABC See 3-3 “Tools”.

Fieldbus Type The ABC Config Tool supports a wide range of networking systems. General During start-up the fieldbus interface of the ABC is initialized to fit the configuration created in the ABC Config Tool. Optionally. Make sure that this parameter is set to ‘Profibus-DP’. IO Sizes (This setting is not applicable on this network and is therefore disabled in the ABC Config Tool) Fieldbus Type .Chapter 4 Basic Settings Fieldbus Settings (Select ‘Fieldbus’ in the Navigation Section to gain access to the parameters described in this section). some initialisation parameters can be set manually to provide better control over how the data shall be treated by the ABC.

The ‘Data Valid’-bit in the Control Register must be set to start the sub-network communication.and Status Registers. Module Reset This parameter specifies how the gateway will behave in the event of a fatal error. See also 2-4 “Protocol Modes”. Value Generic Data Mode Master Mode Description This mode is primarily intended for Produce & Consume-based protocols. The gateway will halt and indicate an error. Both counters are enabled by setting ‘Statistics’ to ‘Enabled’.and Receive Counters indicate how many transactions that have successfully been exchanged on the sub-network. where a single Master exchanges data with a number of Slaves. Status / Control Word (See 13-1 “Control and Status Registers”). and no error will be indicated to the user. Interface Currently. This setting is similar to ‘Enabled’. This setting completely disables the Control. This feature primarily intended for debugging purposes. • Transmit Counter Location Specifies the location of the Transmit Counter in the internal memory buffer. except that the control system is not required to set the ‘Data Valid’-bit to start the sub-network communication. Statistics The Transmit. Protocol Mode This parameter specifies which protocol mode to use for the sub-network. Value Enabled Enabled but no startup lock Disabled Description Enable the Control. This mode is intended for ‘Query & Response’-based protocols. • Receive Counter Location Specifies the location of the Receive Counter in the internal memory buffer. only serial communications is supported.Basic Settings 4-2 ABC Parameters (Select ‘ABC’ in the Navigation Section to gain access to the parameters described in this section).and Status Registers. where there are no Master-Slave relationship between the gateway and the nodes on the sub-network. Value Enabled Disabled Description The gateway will be restarted. .

If set to 0 (zero). RS422. select ‘Sub Network’ in the Navigation Section)..5 characters (the actual number of ms will be calculated automatically based on the currently used communication settings). Communication These parameters specify the actual communication settings used for the sub-network. ASCII Determines if the Start character shall be used or not Valid settings 0x00 . ASCII Determines if the End character shall be used or not Start character for the message. 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. Start and end characters are used to indicate the beginning and end of a serial message. Number of stop bits. • Master Mode The Message Delimiter specifies the time that separates two messages in steps of 10ms. Even RS232. In this case. a message may be initiated with <ESC> and terminated with <LF>.and End Character Note: These parameters are only available in Generic Data Mode. Odd. RS485 1 1. • Generic Data Mode The Message Delimiter specifies the time that separates two messages in steps of 10µs. 2 Start. the gateway will use the standard Modbus delimiter of 3. Valid Settings 1200. For example..57600 7. . Parameter Bit rate Data bits Parity Physical standard Start bits Stop bits Description Selects the bit rate Selects the number of data bits Selects the parity mode Selects the physical interface type Number of start bits.0xFF Enable / Disable Timing (Message Delimiter) The parameters in this category differs slightly between the different Protocol Modes.0xFF Enable / Disable 0x00 .Basic Settings 4-3 Sub-Network Parameters (To gain access to the parameters described in this section. 8 None.

Node Parameters (To gain access to the parameters described in this section.. Adding & Managing Nodes (Right-click on ‘Sub Network’ in the Navigation Section to gain access to these functions) Function Paste Sub Network Monitor Add Node Add Broadcastera Load Node Sub-Network Status. select a node in the Navigation Section). see 8-3 “The Command Editor”. The maximum number of nodes that can be created in the ABC Config Tool is 31. For more information. This function is only available in Master Mode. Parameter Slave Address Description The value entered here may be used to set the node address in certain commands.Chapter 5 Nodes General In ABC Config Tool. and their transactions. a node represents a single device on the network. all nodes. . will be processed in the order they have been defined in the ABC Config Tool.. While the gateway doesn’t feature a scanlist in the traditional sense. Description Paste a node from the clipboard Launch the subnet monitor (9-1 “Sub Network Monitor”) 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.

The two transactions will be grouped in order to increase readability. and transactions issued by other nodes are called ‘Transaction Consume’. Transactions sent to the sub-network are called ‘Transaction Produce’. Adding & Managing Transactions (Right-click on a node in the Navigation Section to gain access to these functions) Function Cut Copy Insert Delete Node Monitor Add Transaction(s) a Description Cut a node to the clipboard Copy a node to the clipboard Insert a node from the clipboard Delete a node Launch the node monitor (10-1 “Node Monitor”) On regular nodes. transactions are representations of the actual serial telegrams exchanged on the serial sub-network. this adds a Query and a Response. a single transaction will be added. The Query is issued by the gateway. transactions always come in pairs. Only available in Master Mode b. The actual number may however be less depending on the memory requirements of the defined transactions. a Query and a Response. Transactions are handled slightly differently in the two protocol modes: • Master Mode For regular nodes. all nodes. and their transactions. while Responses are issued by the slaves on the sub-network. will be processed in the order they have been defined in the ABC Config Tool. The Broadcaster can only send transactions. • Generic Data Mode Transactions can be added as desired for both directions.Chapter 6 Transactions General As mentioned previously. each node can be given a unique name using this function Add Transaction Consumeb Add transaction Produceb Add Command Insert New Node Save Node Insert from File Rename a. Theoretically. On the Broadcaster. Add a ‘Consume’-transaction Add a ‘Produce’-transaction Add pre-defined 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. Only available in Generic Data Mode . While the gateway doesn’t feature a scanlist in the traditional sense. the gateway supports up to 100 transactions.

To use this feature correctly.or Broadcast. This affects the data that is sent to the sub-network. Update time (10ms) This parameter specifies how often the transaction will be issued in steps of 10ms (only relevant when ‘Update mode’ is set to ‘Cyclically’). The location of the trigger byte is specified by the ‘Trigger byte address’ parameter. This feature enables the control system to notify the gateway when to issue a particular Query. This affects the data that is reported to the control system. • Clear . • Change of state on trigger The Query is issued when the trigger byte value has changed. This parameter specifies how long the gateway will wait for a response from a node. the control system must first update the data area associated with the Query/ transaction. select a Query. The unit is milliseconds (ms) and the entered value is multiplied by 10. The value should be set high enough to allow the slave devices time to finish the handling of the broadcast. The unit is milliseconds (ms) and the entered value is multiplied by 10.transaction in the Navigation Section) Parameter Minimum time between broadcasts (10ms) Description This parameter specifies how long the gateway shall wait after transmitting a broadcast transaction before processing the next entry in the scanlist. Retries Timeout time (10ms) This parameter specifies how many times a timeout may occur in sequence before the node is disconnected.The data destined for the slave-device is frozen • NoScanning -The updating of the sub-network is stopped Offline options for subnetwork This parameter specifies the action to take for this transaction if the sub-network goes off-line. Trigger byte address Update mode . which means that the shortest time is 10 ms. • On data change The data area is polled for changes at the time interval defined by Update time.Data is cleared (0) on the higher level network if the sub-network goes offline • Freeze . which means that the shortest time is 10 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’).Data is frozen on the higher level network if the sub-network goes offline Reconnect time (10ms) This parameter specifies how long the gateway shall wait before attempting to re-connect a disconnected node. Note: This setting is only relevant for the Broadcaster node. If this time is exceeded. Offline options for fieldbus This parameter specifies the action to take for this transaction if the higher level network goes off-line. • Clear . 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. then increase the trigger byte by one. A node will be disconnected in case the maximum number of retries (below) has been reached.The data destined for the slave-devices is cleared (set to zero) • Freeze . • Single shot The Query is issued once at start up. A transaction is issued when a change in data is detected. which means that the shortest time is 10 ms.Transactions 6-2 Transaction Parameters (Master Mode) Parameters (Query & Broadcast) (To gain access to these parameters. Note: This setting is not relevant for the Broadcaster node. the gateway will re-transmit the Query until the maximum number of retries (see above) has been reached. The unit is milliseconds (ms) and the entered value is multiplied by 10.

Transactions 6-3

Parameters (Response)
(To gain access to these parameters, select a Response-transaction in the Navigation Section)
Parameter Trigger byte 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. Trigger byte address This parameter specifies the location of the trigger byte in the internal memory buffer. Valid settings range from 0x000... 0x1FF and 0x400... 0xNNN

Transaction Parameters (Generic Data Mode)
Produce-Transactions
(To gain access to these parameters, select a Produce Transaction in the Navigation Section)
Parameter Offline options for fieldbus Description This parameter specifies the action to take for this transaction if the higher level network goes off-line. This affects the data that is sent to the sub-network. • Clear Data is cleared (0) on the sub-network if the higher level network goes offline • Freeze Data is frozen on the sub-network if the higher level network goes offline • NoScanning Stop sub-net scanning for this transaction if the higher level network goes offline Update mode The update mode for the transaction: • Cyclically The transaction is sent cyclically at the interval specified in the ‘Update Time’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 transaction is sent once at startup. • Change of state on trigger The transaction is sent when the trigger byte has changed. This feature enables the control system to notify the gateway when to issue a particular transaction. To use this feature correctly, the control system must first update the data area associated with the transaction, then increase the trigger byte by one. The location of the trigger byte is specified by the ‘Trigger byte address’ parameter. Update time (10ms) This parameter specifies how often the transaction will be issued in steps of 10ms (only relevant when ‘Update mode’ is set to ‘Cyclically’).

Transactions 6-4

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 affect unless the ‘Update mode’ parameter is set to ‘Change of state on trigger’.

Consume-Transactions
(To gain access to these parameters, select a Consume Transaction in the Navigation Section)
Parameter Offline options for sub-network Description This parameter specifies the action to take for this transaction if the sub-network goes off-line. This affects the data that is sent to the higher level network. • Clear Data is cleared (0) on the higher level network if the sub-network goes offline • Freeze Data is frozen on the higher level network if the sub-network goes offline Offline timeout time (10ms) 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. • Enable Enables the trigger byte. The location of the trigger byte must be specified in the ‘Trigger byte address’ (below). The trigger byte value will be increased each time a valid transaction has been consumed by the gateway. 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. Trigger byte address This parameter specifies the location of the trigger byte in the internal memory buffer. Valid settings range from 0x000... 0x1FF and 0x400... 0xNNN Please note that the trigger byte address must be unique to each transaction. It can not be shared by two or more transactions.

Trigger byte

Transactions 6-5

Transaction Editor
The Transaction Editor can be used to edit the individual Frame Objects of a Transaction. The same settings are also available in the Parameter Section of the Main Window, however the Transaction Editor presents the Frame Objects in a more visual manner.

Frame Objects

To edit the value of a parameter, click on it and enter a new value using the keyboard. When editing transactions which are based on pre-defined 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).

Parameters . see 6-5 “Transaction Editor”. a data object. which is used to edit transactions and frame objects in a more visual manner. For more information. The entry called ‘Transaction Editor’ will launch the Transaction Editor. To edit parameters associated with a particular frame object. It is also possible to edit the frame objects in a transaction in a more visual manner using the Transaction Editor. Each Frame Object specifies how the gateway shall interpret or generate a particular part of the telegram. three constants. 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. see 6-5 “Transaction Editor” Data Object. There are 5 types of frame objects. right-click on the Transaction in the Navigation Section and select one of the entries in the menu that appears.Chapter 7 Frame Objects General Each transaction consists of Frame Objects which makes up the serial telegram frame. and a checksum object. select the frame object in the Navigation Section. The settings for that frame object will be displayed in the Parameter Section. Transaction Constant Constant Variable Length Data Checksum Constant Adding and Editing Frame Objects To add a frame object to a Transaction.

Parameter Value Description Constant value . select it in the Navigation Section enter the desired value in the Parameter section. 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. If not. • Consume/Response Transactions The gateway will check if the received byte/word/dword matches the specified value. Word.Frame Objects 7-2 Constant Objects (Byte. To set the value of the object. the message will be discarded.

0xFEh 0x0000. 0xFFFFFFFFh (byte) (word) (dword) Note: Value must be larger than the Minimum Value (below) Minimum Value This is the smallest allowed value for the range. 0xFFFFh 0x00000000. 0xFFh 0x0000. Word. If not.. 0xFFFFFFFEh (byte) (word) (dword) Note: Value must be less than the Maximum Value (above) .. 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.. Range: 0x00. Range: 0x00. 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 enter the desired range in the Parameter section as follows: Parameter Maximum Value Description This is the largest allowed value for the range.Frame Objects 7-3 Limit Objects (Byte.. 0xFFFEh 0x00000000.......

The location of the data block in the internal memory buffer Data Location Variable Data Object Note: Only one Variable Data Object is permitted for each transaction. The End. A.or Length-character itself may either be forwarded to the sub-network or discarded. The End. B. This object is similar to the Data Object. D becomes B.or Length-character itself may either be forwarded to the higher level network or discarded. Maximum data length allowed for one frame is 300 bytes. B. except that it has no predefined length. Instead. In case of a Response or Consume transaction. C. an End or Length-character specifies the size of the data block as follows: (Variable Data Object) Data Data of arbitrary length 0x00 End Character 0x04 Length Character (Variable Data Object) Data 4 bytes of data • Produce/Query Transactions The specified data block will be forwarded from the higher level network to the sub-network. D becomes D. D. C. C. C • Swap 4 bytes A. select it in the Navigation Section enter the desired settings in the Parameter section as follows: Parameter Byte Swapping Description • No Swapping No swapping is performed on the data • Swap 2 bytes A. in bytes. • Consume/Response Transactions The specified data block is forwarded from the sub-network to the higher level network. A Data Length The length of the data block. . • Consume/Response Transactions The specified data block is forwarded from the sub-network to the higher level network. B.Frame Objects 7-4 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. incoming messages where the data size differs from the value specified here will be discarded. The control system must supply an End or Length-character in order for the gateway to know the size of the data block. To specify the properties of the object.or Length-character will be generated by the gateway automatically (if applicable) The End.

Frame Objects 7-5 To specify the properties of the object. Only relevant for Consume/Response transactions b. D becomes D. select it in the Navigation Section enter the desired settings in the Parameter section as follows: Parameter Byte Swapping Description • No Swapping No swapping will be performed on the data • Swap 2 bytes A. The offset in the internal memory buffer where the data shall be read from / written to • Length Character Length character is visible in the internal memory buffer but not on the sub-network • Length Character Visible The length character is visible both in the internal memory buffer and on the sub-network. A. Only used if ‘Object Delimiter’ is set to ‘End Character’ or ‘End Character Visible’ . The value must not exceed 300 bytes. a. • End Character Visible The end character is visible both in the internal memory buffer and on the sub-network • No Charactera No End. which is the maximum data length allowed for one frame. B. C. • Disabled Don’t fill Filler byte Data Location Object Delimiter Filler byte value.or Length-character is generated in the internal memory buffer. C • Swap 4 bytes A. C. D becomes B. End Character Value Maximum Data Length End Character valueb The maximum allowed length (in bytes) of the variable data object. the message will be discarded. B. Only used if ‘Fill unused bytes’ has been enabled. D. If the actual length of the data exceeds this value. B. C. A Fill unused bytes • Enableda Fill unused data with the value specified in ‘Filler byte’. • End Character The end character is visible in the internal memory buffer but not on the sub-network.

represented as hexadecimal ASCII (2 bytes). Error Check Start byte This parameter specifies the byte offset in the transaction to start checksum calculations on . The 2’s complement of the result will be used as a checksum. The resulting byte will be used as a checksum. Parameter Error Check Type Description This parameter specifies which type of algorithm to use: • CRC (2 bytes) CRC-16 with 0xFFFF polynome (Modbus RTU standard) • LRC (1 byte) All bytes are added together as unsigned 8-bit values. The Checksum Object calculates and includes a checksum in a transaction. • ADD (1 byte) All bytes are added together as unsigned 16-bit values. • XOR (1 byte) All bytes are logically XOR:ed together.Frame Objects 7-6 Checksum Object Most serial protocols features some way of verifying that the data has not been corrupted during transfer. The lowest 8 bits in the result are inversed and used as a checksum. • AddInvASCII (2 bytes) All bytes are added together as unsigned 8-bit values. The lowest 8 bits in the result will be used as a checksum.

ABC Config Tool comes pre-loaded with commands for most common Modbus RTU functions. In such case. the parameters in the parameter section will be greyed out and cannot be edited directly. and select ‘Add Command’ in the ‘Command’-menu. right-click on the node in the Navigation Section and select ‘Add Command’. Adding a command to a node actually results in (a) transaction(s) being added according to the directions specified in the command. but custom ones may be implemented as desired. The Frame Objects in such a transaction may retrieve their values not only from parameters in the parameter section. The specified command will be added to the node.Chapter 8 Commands General As mentioned previously. no pre-defined commands exist. the frame objects of added command may be edited in the Navigation/Parameter Section or using the Transaction Editor. . A list of commands will appear: Select the desired command in the list. Note however that certain frame objects may be locked for editing. Additional commands can easily be added using the Command Editor (see 8-3 “The Command Editor”). Adding & Managing Commands To add a command to a node. commands consist of frame objects and are representations of the actual serial telegrams exchanged on the serial sub-network. but also from other sources such as the ‘SlaveAddress’-parameter (see 5-1 “Node Parameters”). Commands are actually pre-defined transactions that can be stored and reused. In Master Mode. Just like other transactions. In Generic Data Mode. Just like regular transactions.

• Add Command (Same as ‘Add Command’ in the ‘Command’-menu). Add Command • Edit Command (Same as ‘Edit Command’ in the ‘Command’-menu). Note that some commands are fixed and cannot be deleted. and open the new command in the Command Editor. See also 8-3 “The Command Editor”. • Delete Command Delete the currently selected command from the list. Toolbar Icons The toolbar features icons for the most commonly used functions. • Exit Exit without adding a command to the node.Commands 8-2 Pull-Down Menu File This menu features the following entries: • Select Add the currently selected Command to the node. Delete Command . • Edit Command Edit the currently selected command using the Command Editor. See also 8-3 “The Command Editor”. Command This menu is used to manage the commands in the list: • Add Command Add a custom command to the list. Edit Command • Delete Command (Same as ‘Delete Command’ in the ‘Command’-menu).

g. Basic Navigation Open the Command Editor by selecting ‘Edit Command’ or ‘Add Command’ from the ‘Command’menu. C: Command Transactions This section holds the actual transactions associated with the command.Commands 8-3 The Command Editor General The Command Editor is used to define new commands and edit existing ones. or a single transaction. which can be stored and re-used at a later stage. The examples in this section uses Master Mode. Note that the Command Editor is somewhat protocol-dependent in the sense that certain frame objects may not be deleted or altered. B: Name of Command Actual name of the command. E: Other Settings Setting Allow Broadcasting Produce Consume Description Specifies if it is allowed to broadcast the command (only relevant in Master Mode) The command is producing data (Generic Data Mode only) The command is consuming data (Generic Data Mode only) . The procedures involved are similar in General Data Mode. to specify the function code. This makes it possible to build a library of commands. depending on the protocol mode etc. This can either be a Query-Response pair. in text form. e. D: Command ID This can be used as desired when building the command. but without the limitations imposed by the Modbus RTU protocol. A B D E C A: Pull-down Menu See 8-4 “Pull-down Menu”.

Column The functions in this menu alters the structure of the command.Commands 8-4 Pull-down Menu File This menu features the following entries: • Apply Changes Save changes and exit to the main window. • Delete Command Delete the column at the selected position. . • Exit Exit without saving. • Insert Column Insert a column at the selected position. • Append Column Add another column to the command.

User The settings associated with the object can be edited by the user. Id The value will be retrieved from the ‘Command ID’-setting (see 8-3 “Basic Navigation”). Each column features four rows with the following parameters: • Query/Response/Produce/Consume The upper right cell indicates the direction of the transaction. • ObjectType This row specifies the type of frame object that shall be used for the column. • 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. (other settings) Other settings are no longer supported. The value will be retrieved from the corresponding part of the ‘Query’-transaction. • Value This row specifies where the frame object shall retrieve its value/settings. Value Depend Description This setting is only relevant for Responses in Master Mode. [SlaveAddress] The value will be retrieved from the ‘SlaveAddress’-parameter (see 5-1 “Node Parameters”). Each column represents a frame object within the transaction. the transaction section in the Command Editor represents the actual transactions associated with the command. .Commands 8-5 Editing a Command As mentioned previously.

2 Function Byte Object ID The value of this byte constant will be set using the ‘Command ID’-field. Name the new command by entering it’s name in the ‘Command Name’-field.Commands 8-6 Example: Specifying a Modbus-RTU Command in Master Mode In the following example. check the ‘Allow Broadcasting’-checkbox. DisplayName Slave Address By default. a transaction always feature the following parts: • • • • Slave Address (1 byte) Function Code (1 bytes) A data field CRC (CRC-16) Furthermore. and a data object is inserted between the function code and the CRC. 2 Function Byte Object ID The value of this byte constant will be set using the ‘Command ID’-field. In Modbus-RTU. 3 Data Data Object User The size and location of the data associated with this object is determined by the user. each command always consists of a Query and a Response. . and enter a suitable function code in the ‘Command ID’-field. DisplayName Slave Address • Example Response Response Object Type Value 1 Byte Object [SlaveAddress] This value is linked to the ‘SlaveAddress’ parameter in the parameter window. however it is possible to add additional objects between the function code and the CRC as desired. These objects cannot be moved or deleted. 3 Data Data Object User The size and location of the data associated with this object is determined by the user. the Modbus-RTU-specific frame objects are already in place. this is set to match the Modbus-RTU standard. 4 Checksum Checksum Object User The checksum type etc can be selected by the user. • Example Query Query Object Type Value 1 Byte Object [SlaveAddress] The value of this byte constant will be set using the ‘SlaveAddress’ parameter (see 5-1 “Node Parameters”). 4 Checksum Checksum Object Depend This object will retrieve its settings from the corresponding object in the Query. a Modbus-RTU command is created in Master Mode. By default. If the command is allowed to be broadcasted.

or Control/Status Registers. are listed in the middle of the screen (B). Therefore the monitor functionality should be used with care. Data allocated by a Response or Consume transaction. Data allocated by a Query or Produce transaction Collision. click on the green light. area has been allocated more than once. All configured nodes. Selecting and deselecting single transactions makes it possible to view any combination of allocated data. Reserved (illustrates memory consumption. select the transaction in the list.Chapter 9 Sub Network Monitor General The Sub Network Monitor is intended to simplify configuration and troubleshooting of the sub network. Note: The sub-network monitor has a negative influence on the overall performance of the gateway. Start Stop . Output and General Data areas. C: Monitor Section This section visualises how data is allocated in the Input. click on the red light. B: Nodes / Transactions To view data blocks associated with a transaction. area can be allocated if necessary) Data allocated by Trigger byte. and their transactions. The corresponding data will then appear in the Monitor Section (C). Operation A B C A: Start Network & Stop Network Icons These icons controls the sub-network activity.e if a collision has occurred). To start the sub-network again. Transmit//Receive Counter. It’s main function is to display the data allocated for sub-network communication and detect if any area has been allocated twice (i. Colour White Yellow Blue Red Grey Green Meaning Not allocated. To stop all sub-network activity.

The response to the Query can be monitored in the Response Section. It is not possible to monitor any responses etc. Command Section (Produce) (Not used) Sub-network . by allowing individual commands to be issued manually.e. generated by other nodes. and monitoring the response (if applicable). it should be used only when necessary. Note: The node monitor has a negative influence on the overall performance of the gateway. It also provides an overview of the memory used by a particular node. Command Section (Query) Sub-network Response Section • Generic Data Mode The selected command (Transaction Produce) is sent to the sub-network. i. The Node Monitor behaves somewhat differently in the two protocol modes: • Master Mode The selected Command (Query Transaction) is sent to the sub-network.Chapter 10 Node Monitor General The Node Monitor can provide valuable information when setting up the communication with the subnetwork.

For more information.Node Monitor 10-2 Navigating the Node Monitor A B C D A: Pull-down Menu & Toolbar Icons See 10-3 “Pull-Down Menu” and 10-4 “Toolbar Icons” B: Command Section This section holds the currently selected command. C: Response Section (Master Mode only) This section holds the response to the selected Command.and Command Editors. see 10-4 “Toolbar Icons” . The data displayed in this section will be refreshed based on the refresh-icons in the toolbar. and areas displayed in light grey represents the data that is used by the node. The individual frame objects in the command can be edited in a similar way as in the Transaction. D: Monitor Section This section displays the data associated with the node. Areas in dark grey are reserved for the Status & Control Registers.

View This menu specifies the data representation in the Monitor Section. • Decimal Display the data in decimal format. • Stop Node Disable the transactions associated with the node. • Start Node Enable the transactions associated with the node. • Send Command Send the specified command to the sub-network. • Hex Display the data in hexadecimal format. . • 8 Multiple The number of columns will be fixed to 8. • Free The number of columns depends on the width of the window. Node This menu controls the data exchange for the node. This feature can help isolate problems associated with a particular node.Node Monitor 10-3 Pull-Down Menu File There is only one entry in this menu: • Exit This will close the Node Monitor. Command This menu is used to specify and issue a command manually. • Select Command Select a command to be sent on the sub-network. 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’. Columns This menu specifies the number of columns in the Monitor Section.

See also 10-3 “Command”. Stop Resume • Refresh When clicking on this icon.Node Monitor 10-4 Toolbar Icons The toolbar features icons for the most commonly used functions. • Start Node & Stop Node These icons corresponds to the functions in the ‘Node’-menu. See also 10-3 “Node”. i. the data will have to be refreshed manually using the ‘Refresh’-icon (see below).e. stopped. the data displayed in the Monitor Section will be refreshed cyclically. Select Send • Resume Refresh & Stop Refresh When enabled. Start Stop • Select Command & Send Command These icons corresponds to the functions in the ‘Command’-menu. the data displayed in the Monitor Section will be refreshed. Refresh . When disabled.

• Log until full Data will be logged until the log-buffer is full. Modes of Operation Select the desired mode of operation and click ‘OK’ to start logging data. The log-buffer will contain the most recent data. • Stop logging Select ‘Stop Logging’ in the ‘Tools’-menu. Log Window The logged data is displayed in Hexadecimal. This will open the log-window. This may provide valuable information when debugging the lowest levels of the sub-network communication. see below. .Chapter 11 Data Logger General This feature allows the sub-network traffic to be logged into a buffer for examination. • Log continuously Data will be logged continuously until logging is stopped by clicking ‘Stop Logging’. This means that logging can be performed even if the gateway is physically disconnected from the PC running the ABC Config Tool. see below. ABC Config Tool will then prompt for the desired mode of operation. The time between the logentries is displayed in a separate column. Click ‘Close’ to exit. The data may optionally be saved in ASCII text format by clicking ‘Create Text file’. Note that the logger function is part of the gateway itself and is separate from the ABC Config Tool. Decimal and ASCII format for both directions. Operation Start & Stop Logging • Start logging Select ‘Start Logging’ in the ‘Tools’-menu.

. A window with various settings will appear. To specify a different size for the buffer. Click ‘OK’ to exit. .Data Logger 11-2 Configuration By default. and enter the desired number of buffer entries under ‘Size of logbuffer’ (valid settings range from 1.512). select ‘Options’ in the ‘Tools’-menu. the log-buffer can hold 512 bytes of data in each direction. Select the ‘ABC’tab. Click ‘Apply’ to validate the new settings..

see 3-3 “Tools”). the ABC Config Tool provides a choice between starting out with a blank configuration.Modbus RTU Master”. the following wizards are available: • ABCC ExtLink Wizard This wizard is intended for use with the Anybus-CompactCom Modbus-RTU fieldbus communication module. The wizard automatically creates a sub-network configuration based on information supplied by the user.k. . or upon selecting the ‘New’ entry in the ‘File’-menu (unless it has been disabled in the ‘Options’-menu. or using a predefined template. Note however that this will only work when the subnetwork fits the wizard profile.a a wizard. Currently.Modbus RTU Master This option is suitable for Modbus RTU-based networks. • Wizard .Chapter 12 Configuration Wizards General When creating a new sub network configuration. • Blank Configuration This option creates an empty configuration. i. Selecting a Wizard Profile The following window appears each time the ABC Config Tool is started. See also 12-2 “Wizard . Highlight the desired wizard and click ‘OK’ to continue. in all other cases the ‘Blank Configuration’ option must be used.e the user simply has to “fill in the blanks”. a.

Click ‘Next’ to continue. Using this wizard involves the following steps: Step 1: Communicator Type Select ‘Profibus-DP’. and if necessary contact the manufacturer of the device to obtain further information about the serial communication protocol.Configuration Wizards 12-2 Wizard .6 Consult the on line help system for further information. it is possible to specify this command manually as a transaction in the ABC Config Tool. Click ‘Next’ to continue. For example. The on-line help system explains each configuration step in detail. • Important Notes: Many OEM devices do not fully comply with the Modbus standard.Modbus RTU Master This wizard can be used to create a Modbus-RTU-based network configuration based on certain information about the sub-network. In the event that the wizard doesn’t handle a particular Modbus command required by a device. the user should consult the documentation of the devices that shall be used on the sub-network for information about their serial communication requirements. Tip: It is possible to return to a previous menu at any time without losing any settings by clicking ‘Previous’ Step 2: Physical Settings Select the physical properties of the sub network. 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. Steps 3 .

which is illustrated in the two flowcharts below. These registers form an interface for exchanging status information between the sub-network and the fieldbus control system. MSB first).Chapter 13 Control and Status Registers General The Control. Handshaking Procedure A special handshaking procedure. which means they can be accessed from the fieldbus just like any other data in these areas.e. these registerse are stored in Motorola-format (i.. Note: Internally.and Output Data areas (0x000-0x001 and 0x200-0x201 respectively). but can be enabled using the ABC Config Tool (see 4-2 “Status / Control Word”). the upper and lower bytes will appear swapped.and Status Registers are disabled by default. If the higher level network uses a different byte order.. The main purpose of these registers is to. Read Status Register Start Write to Control Register Start CR_HS_CONFIRM= SR_HS_SEND? No Yes SR_HS_CONFIRM= CR_HS_SEND? Yes No Read Status Register Write to Control Register Set CR_HS_CONFIRM to SR_HS_SEND Toggle CR_HS_SEND Done Done . these registers occupy the first two bytes in the Input. must be followed when accessing these registers to ensure that both parts receive proper information. • • • 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.

If the same parameter is set to ‘Disabled’ or ‘Enabled but no startup lock’. shift to state A. 7. If the ‘Status / Control Word’-parameter in ABC Config Tool is set to ‘Enabled’. When the ‘Data Valid’-bit in the Status Register is set by the gateway. State Machine The fieldbus network participation can be described using a state machine as described below. 2. Write initial data to the Output Area according to the sub-network configuration. This latency can be caused by a missing node or a bad connection to a node with a long timeout value assigned to it. If the gateway goes offline on the fieldbus.and Status Registers are used to ensure data consistency during start-up and fieldbus off-line/on-line transitions. C Online (exchanging data) A Offline (no data exchange) Start B Online (not yet exchanging data) . 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. Set the ‘Data Valid’-bit in the Control Register. 3. and shift to state B. Note: The gateway cannot spontaneously clear the ‘Data Valid’-bit in the Status Register. A: Offline (No data exchange) 1. communication will start as soon as the fieldbus goes online. Wait until the ‘Data Valid’-bit in the Status Register is cleared by the gateway. the fieldbus control system should not wait for this bit to be set before communicating with the sub-network devices. B: Online (Not yet exchanging data) 4. Clear the ‘Data Valid’-bit in the Control Register. shift to state C. Therefore. 5. shift to state A.Control and Status Registers 13-2 Data Consistency The ‘Data Valid’-bits in the Control. If the gateway goes offline on the fieldbus. 6. it should be considered as an aid for the fieldbus control system to know when all data has been updated. Wait until the fieldbus control system and the gateway are online on the fieldbus network. Latency The ‘Data Valid’-bit in the Status Register may in some cases be delayed. C: Online (Exchanging data) Exchanging valid data in both directions.

Status Codes in Master Mode (This table is valid only in Master Mode). .13-5 “Control Register Contents (Control System to Gateway)” This bit is set when all transactions have been executed successfully at least once. this is treated as a Motorola-format word (i. .13-1 “Handshaking Procedure” .or Multiple Node(s) Missing condition. the upper and lower bytes will appear swapped. 0 Data Note: Internally. If the higher level network uses a different byte order. See also. Note: Conditions of type ‘Error’ will eventually be followed by a ‘No Error’ condition when the cause has been resolved... Once set..e. Code 0x00 Condition Invalid Transaction Counter Updated Type Error Data Counter Description The number of invalid transactions (i. Status Code in Generic Data Mode (This table is valid only in Generic Data Mode).. it will not change. . 1: Data Valid 0: Data not Valid Note: This bit is not used in Generic Data Mode.13-3 “Status Code in Generic Data Mode” 13 12. Code 0x00 Condition Re-transmission Counter Updated Type Warning Data Counter Description The number of re-transmissions on the subnetwork has increased. this may eventually trigger a Single... Conditions of type ‘Warning’ are however considered informational and may not necessarily be followed by a ‘No Error’ condition later on.e. See also. If this problem persists. Undefined error No errors 0x01 0x02 0x03 0x04 0x1F Single Node Missing Multiple Nodes Missing Buffer Overrun Other Error No Error Error Error Warning Error Warning Slave address Slave address Slave address - Number of nodes Multiple nodes are missing. MSB first). This field holds the last status report from the gateway.Control and Status Registers 13-3 Status Register Contents (Gateway to Control System) General Information The Status Register is (if enabled) located at 0x000-0x001 and constitues a bit-field as follows bit(s) 15 14 Name Send (SR_HS_SEND) Confirm (SR_HS_CONFIRM) Data Valid (Master Mode Only) Description These bits control the handshaking towards the fieldbus control system. A node returned more data than expected..13-3 “Status Codes in Master Mode” . received transactions which doesn’t match any of the Consume-transactions defined in the sub-network configuration) has increased. 8 Status Code 7.. A single node is missing.

Conditions of type ‘Warning’ are however considered informational and may not necessarily be followed by a ‘No Error’ condition later on. ..Control and Status Registers 13-4 Code 0x01 0x02 Condition Frame Error Offline Timeout Counter Updated Type Warning Error Data Counter Description End character is enabled. Undefined error No errors 0x04 0x1F Other Error No Error Error Warning - Note: Conditions of type ‘Error’ will eventually be followed by a ‘No Error’ condition when the cause no longer is detected.the gateway was unable to finish processing a message prior to receiving a new one.or . . The of number of timed out Consume-transactions has increased.6-4 “Consume-Transactions” (Offline timeout time) 0x03 Buffer Overrun Warning - A node returned more data than expected . but a message delimiter timeout occurs prior to receiving it. See also..

. exchange data on the sub-network 0: Output Area not valid. this is treated as a Motorola-format word (i. This field holds commands which can be executed by the gateway (see below). 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.... . Remaining nodes will be disabled. See also. the upper and lower bytes will appear to be swapped. Enables the specified number of nodes. Control Codes in Master Mode (This table is valid only in Master Mode).. Code 0x00 0x01 0x02 Instruction Disable Node Enable Node Enable Nodes Data Actual node address Actual node address Actual number of nodes to enable Description Disables the specified node. 1: Output Area valid.13-3 “Status Register Contents (Gateway to Control System)” This bit controls data consistency (see 13-2 “Data Consistency”). 8 Control Code 7.Control and Status Registers 13-5 Control Register Contents (Control System to Gateway) General Information The Control Register is (if enabled) located at 0x200-0x201 and constitues a bit-field as follows: bit(s) 15 14 Name Confirm (CR_HS_CONFIRM) Send (CR_HS_SEND) Data Valid Description These bits control the handshaking towards the gateway. See also. If the higher level network uses a different byte order.13-5 “Control Codes in Generic Data Mode” 13 12 Execute Command 11..e.. Control Codes in Generic Data Mode (No Control Codes are currently supported in this mode). Enables a previously disabled node. MSB first). starting from the first node in the configuration. the specified command will be executed by the gateway (see below). .13-1 “Handshaking Procedure” .. .13-5 “Control Codes in Master Mode” . 0 Data Note: Internally.

For general information about the Anybus-S platform. consult the Anybus-S Design Guide. For more information about the Anybus-S platform. consult the Anybus-S Parallel Design Guide. see below. (A mailbox message is a HMS specific command structure used for low-level communication with an Anybus-S interface. Information about the amount of input. Normally. However. It is possible to add fieldbus specific mailbox messages to customize the initialisation. consult the separate Anybus-S Fieldbus Appendix for the fieldbus you are using. A B For more information about fieldbus specific mailbox messages. 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).) Mailbox Editor To add a mailbox message to the configuration. right-click on ‘EndInit’ and select ‘Insert New Mailbox’. the other one contains the message data (B). the Anybus-S configuration settings are set up automatically by the gateway. This is done in the Mailbox Editor. 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). advanced users can configure the Anybus-S card for specific features. one contains header information (A).and output data areas in the Dual Port RAM of the embedded Anybus-S interface. To add message data.Chapter 14 Advanced Fieldbus Configuration General The fieldbus interface of the gateway consists of an embedded Anybus-S communication interface. All fields are editable except the Message information field that is fixed to 0x4002. The mailbox message is presented as two columns. This chapter assumes that the reader is familiar with the Anybus-S and it’s application interface. The standard initialisation parameters are determined by the sub-network configuration. Consult the Anybus-S Parallel Design Guide and the fieldbus appendix for the desired fieldbus for further information.and output data used for sub-network communication is used by ABC Config Tool to create the configuration message that sets the sizes of the input. which means that only fieldbus specific mailbox messages can be entered here.

. www.erni.Appendix A Connector Pin Assignments PROFIBUS Connector Pin Housing 1 2 3 4 5 6 7 8 9 Signal Shield B-Line RTSa Description Bus cable shield.erni. may also be used to power optical transceivers (RS485 to fibre optics) Recommended Connectors: • • • PROFIBUS Max standard (Part no. www. May be used by some devices to determine the direction of transmission b. 104577. The terminal tightening torque must be between 5.. 0. 134928.8 Nm) . connected to PE Positive RxD/TxD (RS485) Request To Send 5 1 GNDBUSb Isolated GND from RS-485 side +5V BUSb Isolated +5V output from RS-485 side (80mA max) A-Line Negative RxD/TxD (RS485) - 9 (female) 6 a.siemens.. 6GK1500-0FC00 or 6ES7 972-0BA50-0XA0.com) PROFIBUS reversed (Part no. Used for bus termination..com) Power Connector Pin 1 2 Description +24V DC GND 1 2 Notes: • • Use 60/75 or 75×C copper (CU) wire only. 7 lbs-in (0.5. www.com) Fast Connect Bus Connector (Part no.

Connector Pin Assignments A-2 PC Connector Configuration Cable Wiring DP9F (PC) 1 RS232 Rx RS232 Tx 2 3 4 Ground 5 6 7 8 9 RJ11 (ABC) 1 2 3 4 Ground Ground Rx Tx RJ9 (ABC) Pin 1 2 3 4 RS232 Rx (Input) RS232 Tx (Output) Description Signal ground 4 3 2 1 .

typically 100. the serial lines should be forced into a known state using pull-up and pull-down resistors. it is important to properly terminate the sub-network by placing termination resistors between the serial receivers near the end nodes. Termination (RS485 & RS422 Only) To avoid reflections on the serial lines. The bias resistors forms a voltage divider. The resistor value should ideally match the characteristic impedance of the cable. Bias Resistors (RS485 Only) When idle.. Depending on the configuration specified in the ABC Config Tool. 120R. To prevent this. installing bias resistors on several nodes may compromise the signal quality on the network and cause transmission problems. typically >200mV. RS422 and RS485 communications.Connector Pin Assignments A-3 DB9F (PC) Pin 1 2 3 4 5 6-9 Description RS232 Rx (Input) RS232 Tx (Output) Signal Ground 9 6 5 (female) 1 Sub-network Interface General Information The sub-network interface provides for RS232. different signals are activated in the sub-network connector. Note that bias resistors shall only be installed on one node. forcing the voltage between the differential pair to be higher then the threshold for the serial receivers. which may cause the serial receivers to pick up noise from the serial lines and interpret this as data. RS485 enters an indeterminate state. commonly known as bias resistors. ..

. It is therefore generally recommended to connect it only to Signal Ground (if available) of other nodes.. Connecting this signal directly Protective Earth (PE) of other nodes may./RS422 TxCable Shield             9 6 RS232    RS422  RS485  RS485 5 (female) 1 a. cause damage to the on-board serial transceivers.Connector Pin Assignments A-4 Connector Pinout (DB9F) Pin 1 2 3 4 5 6 7 8 9 (housing) Description +5V Output(100mA max) RS232 Rx RS232 Tx (reserved) Signal Grounda RS422 Rx + RS422 Rx RS485 + /RS422 Tx+ RS485 . in case of grounding loops etc.

but may be required when using 4-wire RS485.Connector Pin Assignments A-5 Typical Connection (RS485) +5V 470R RS485 + 120R RS485 470R Signal Ground Signal Ground RS485 RS485 + Signal Ground RS485 RS485 + Signal Ground RS485 RS485 + Signal Ground RS485 RS485 + Signal Ground 120R RS485 RS485 + Cable Shield Anybus Communicator Node Node Node Node End Node Typical Connection (RS422 & 4-Wire RS485) +5V 470R RS422 Rx+ 120R RS422 Rx470R RS422 Tx+ 120R RS422 Tx470R Signal Ground Signal Ground RS422 Rx470R RS422 Rx+ RS422 TxRS422 Tx+ Cable Shield Anybus Communicator Device Note: Bias resistors are normally not needed on RS422. Typical Connection (RS232) RS232 Tx RS232 Rx RS232 Rx RS232 Tx Signal Ground Signal Ground Cable Shield Anybus Communicator Device .

Connector Pin Assignments A-6 .

protection class IP20 Dimensions 120 mm x 75 mm x 27 mm.72” x 2. Typically around 100mA 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 Technical Specification Mechanical Properties Housing Plastic housing with snap-on connection to DIN-rail. L x W x H) Electrical Characteristics Power Supply Power: 24V ± 10% Power Consumption Maximum power consumption is 280mA on 24V.95” x 1.06”. L x W x H (inches: 4.

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) 10V/m EN 61000-4-6 (1996) 10V/m (all ports) EN 61000-4-2 (1995) ±8kV ±4kV EN 61000-4-4 (1995) ±2kV ±1kV Air Discharge Contact discharge Power port Other ports EN 61000-4-5 (1995) ±0.Technical Specification B-2 Regulatory Compliance EMC Compliance (CE) This product is in accordance with the EMC directive 89/336/EEC.5kV Power ports (DM/CM) ±1kV Signal ports UL/c-UL compliance The certification has been documented by UL in file E214107. Galvanic isolation on sub-network interface • EN 60950-1 (2001) Pollution Degree 2 Material Group IIIb 250 VRMS or 250 VDC Working voltage 500 V Secondary circuit transient rating .

If no data is received. If no data is being transmitted. No sub-network functionality • • • Use the ‘Data logger’-functionality to record the serial data communication on the sub-network. check your cabling and / or try a lower baud rate setting for the sub network (if possible). • Is the Node Monitor in the ABC Config Tool active? The node monitor has a negative influence on the overall performance of the gateway. Also verify that the transmitted data is correct. Exit the ABC Config Tool and close all other applications including the ones in the system tray. check the configuration in ABC Config Tool. Solution • Serial communication failed. The serial port seems to be available. and should only be used when necessary. Try again • Poor performance • 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. check the sub-network cables. Try again . The Config Line “led” turns red in the ABC Config Tool. If the gateway reports very many re-transmissions. but it is not possible to connect to the gateway • The serial port may be in use by another application.Appendix C Troubleshooting Problem Problem during configuration Upload / Download. and should only be used when necessary. • Is the Sub-Net Monitor in the ABC Config Tool active? The sub-network monitor has a negative influence on the overall performance of the gateway.

Appendix D ASCII Table x0 0x 1x 2x 3x 4x 5x 6x 7x x1 x2 x3 x4 x5 x6 x7 x8 BS 8 x9 HT 9 EM 25 ) 41 9 57 I 73 Y 89 i 105 y 121 xA LF 10 xB VT 11 xC FF 12 FS 28 . 59 K 75 [ 91 k 107 { 123 . 46 > 62 N 78 ^ 94 n 110 ~ 126 xF SI 15 US 31 / 47 ? 63 O 79 _ 95 o 111 DEL 127 NUL SOH STX ETX EOT ENQ ACK BEL 0 1 2 3 4 5 6 7 DLE DC1 DC2 DC3 DC4 NAK SYN ETB CAN 16 17 18 19 20 21 22 23 24 (sp) 32 0 48 @ 64 P 80 ` 96 p 112 ! 33 1 49 A 65 Q 81 a 97 q 113 " 34 2 50 B 66 R 82 b 98 r 114 # 35 3 51 C 67 S 83 c 99 s 115 $ 36 4 52 D 68 T 84 d 100 t 116 % 37 5 53 E 69 U 85 e 101 u 117 & 38 6 54 F 70 V 86 f 102 v 118 ' 39 7 55 G 71 W 87 g 103 w 119 ( 40 8 56 H 72 X 88 h 104 x 120 SUB ESC 26 27 * 42 : 58 J 74 Z 90 j 106 z 122 + 43 . 44 < 60 L 76 \ 92 l 108 | 124 xD CR 13 GS 29 45 = 61 M 77 ] 93 m 109 } 125 xE SO 14 RS 30 .

Sign up to vote on this title
UsefulNot useful