Technical Manual Addendum Fieldbus Interface Module for Ethernet

Technical Manual Addendum

Table of Contents

1 Introduction 3
1.1 How to Use This Document ................................................................................................ 3
1.2 Important User Information................................................................................................. 3
1.3 Conventions Used in this Document .................................................................................... 3
1.4 Terms.............................................................................................................................. 4

2 About the Fieldbus Interface Module for Ethernet 5

2.1 Hardware Topology........................................................................................................... 5
2.2 Ethernet Interface .............................................................................................................. 5
2.3 Connectors and Key Components ....................................................................................... 6
2.4 Status Indicators ............................................................................................................... 7
2.5 Installation ....................................................................................................................... 7
2.6 Electronic Data Sheet (.EDS file) ......................................................................................... 8

3 Data Exchange 9
3.1 Internal Memory Buffer Structure ......................................................................................... 9
3.2 I/O Data........................................................................................................................... 10
3.3 Memory Map.................................................................................................................... 10

4 Quick Start Guide - Adding to Your Network 11

4.1 Connect the Module to Your Network ................................................................................... 11
4.2 Default IP Settings............................................................................................................. 11
4.3 Configuring the IP Address Using DHCP............................................................................... 11
4.4 Configuring the IP Address Using Anybus IPconfig ................................................................ 11
4.5 Configuring the IP Address Using ARP ................................................................................. 12
4.6 Configuring the IP Address Using Web Browser .................................................................... 12

5 Filesystem 14
5.1 FLASH Memory ................................................................................................................. 14
5.2 Security Framework........................................................................................................... 14

6 System Files 15
6.1 Configuration Files 'IP_accs.cfg' ......................................................................................... 15
6.2 Password Files 'sys_pswd.cfg' ........................................................................................... 15

7 FTP Server 17

8 Telnet Server 18
8.1 General Commands .......................................................................................................... 18
8.2 Diagnostic Commands ...................................................................................................... 18
8.3 File System Operations ...................................................................................................... 19

9 Ethernet/IP Configuration 21

10 Ethernet/IP 23
10.1 Implemented Objects......................................................................................................... 23
10.2 Identity Object, Class 01h .................................................................................................. 23
10.3 Message Router Object, Class 02h ..................................................................................... 24
10.4 Assembly Object,Class 04h ............................................................................................... 24
10.5 Diagnostic Object, Class AAh ............................................................................................. 25
10.6 TCP/IP Interface Object, Class F5h ...................................................................................... 25
10.7 Ethernet Link Object, Class F6h .......................................................................................... 27

11 Appendix - TCP/IP Configuration Basics 28

11.1 IP address ....................................................................................................................... 28
11.2 Subnet Mask .................................................................................................................... 28
11.3 Special Case IP addresses ................................................................................................. 28

Fieldbus Interface Module for Ethernet Table of Contents 1

 12 Appendix- Connector Pin Assignments 29
12.1 Ethernet Connector ............................................................................................................ 29

13 Appendix - Technical Specifications 30

13.1 Mechanical ...................................................................................................................... 30
13.2 Electrical.......................................................................................................................... 30
13.3 Environment..................................................................................................................... 30
13.4 EMC Compliance .............................................................................................................. 30

14 Appendix - ASCII Table 31

2 Table of Contents Fieldbus Interface Module for Ethernet

 1 Introduction
In this chapter, you’ll learn how to use this document and general information about the Fieldbus Interface
Module (FIM) for Ethernet.

1.1 How to Use This Document

This document contains a general introduction as well as a description of the technical features provided by the
Hi-Speed Checkweigher FIM.
The reader of this document is expected to be familiar with PLC and software design, as well as communication
systems in general.

1.2 Important User Information

The data and illustrations found in the document are not binding. We, Mettler-Toledo Hi-Speed Inc., reserve the
right to modify our products in line with our policy of continuous product development. The information in this
document is subject to change without notice and should not be considered as a commitment by Mettler-Toledo
Hi-Speed Inc., who assumes no responsibility for any errors that may appear in this document. There are many
applications of this document. Those responsible for the use of this device must ensure that all the necessary
steps are taken to verify that the application meets all performance and safety requirements, including any
applicable laws, regulations, codes, and standards.

1.3 Conventions Used in this Document

The following conventions are used throughout this document:
• Numbered lists provide sequential steps
• Bulleted lists provide information, not procedural steps
• The term ‘user’ refers to the person or persons responsible for installing the Fieldbus Interface Module in a
network
• The terms ‘module’ and ‘FIM’ refers to the Fieldbus Interface Module
• Hexadecimal values are written in the format 0xNNNN, where NNNN is the hexadecimal value
• Decimal values are represented as NNNN where NNNN is the decimal value
• As in all communication systems, the terms “input” and “output” can be ambiguous, because their meaning
depend on which end of the link is being referenced.
The convention in this document is that “input” and “output” are always being referenced to the master/scanner
end of the link. (see illustration below)

Fieldbus Interface Module for Ethernet Introduction​​ 3

 Figure 1. Input and Output Definition

1.4 Terms
FIM – Fieldbus Interface Module
Fieldbus – The network to which the FIM is connected
Fieldbus Control System – Fieldbus master

4 Introduction​​ Fieldbus Interface Module for Ethernet

 2 About the Fieldbus Interface Module for Ethernet
The Fieldbus Interface for Ethernet or FIM provides connectivity between a Mettler-Toledo Hi-Speed X-Series®
checkweigher and an Ethernet network. Integration of industrial devices is enabled without loss of functionality,
control and reliability, both when retro-fitting to existing equipment as well as when setting up new installations.

2.1 Hardware Topology

Figure 2. Fieldbus Network

2.2 Ethernet Interface

Ethernet connectivity is provided through the HMS patented AnyBus technology; a proven industrial com-
munication solution used all over the world by leading manufacturers of industrial automation products.
• EtherNet/IP group 2 and 3 server
• Web server
• Easy file management via FTP & Telnet server
• 10/100 Mbit/s, twisted pair

Fieldbus Interface Module for Ethernet About the Fieldbus Interface Module for Ethernet​​ 5
 2.3 Connectors and Key Components
For wiring and pin assignments, see Appendix Connector Pin Assignments.
1. Anybus Application Connector
This connector is used to provide the hardware interface to the XRTC.
2. Ethernet Connector
This connector is used to connect the FIM to Ethernet.
3. Configuration Switch
The switch values should all be set to the off state.
4. Anybus Watchdog
No user function.
5. Status Indicators
These LEDs indicate run time status and errors to the user, see below.

Figure 3 Connectors

6 About the Fieldbus Interface Module for Ethernet​​ Fieldbus Interface Module for Ethernet
 2.4 Status Indicators
Table 1- Status Indicator Table
# State Status
1- Link This LED indicates that the module is connected to an Ethernet network
by indicating solid green
2- Module status Steady off No power
Steady green Device operational
Flashing green Standby
Flashing red Minor fault
Steady red Major fault
Flashing green/red Self test
3- Network status Steady off No power or no IP address
Steady green Connected
Flashing green No connections
Flashing red Connection timeout
Steady red Duplicate IP detected
Flashing green/red Self-test
4- Activity This LED flashes green each time a packet is received or transmitted

Figure 4 Status Indicators

2.5 Installation

1. Remove the Fieldbus Interface Access Cover from the XRTC by removing the 5 screws that retain the cover.
The FIM (or Anybus-S PCB) mounting will then be accessible.
2. Note the MAC address of the FIM located on a label on the bottom of the FIM.
3. Create a label indicating the same MAC address and mount the new lable on the outside of the access
cover.
4. Remove the screws mounted on the top of the 3 standoffs.
Note: if the 3 standoffs are not mounted, then retrofit kit, part number 66999559, should be used to install
them.
5. Being careful to properly align the connector at J25, press the FIM firmly into place.
6. Reinstall the 3 screws previously removed to secure the FIM into place.
7. Reinstall the Fieldbus Interface Access Cover.

Fieldbus Interface Module for Ethernet About the Fieldbus Interface Module for Ethernet​​ 7
 2.6 Electronic Data Sheet (.EDS file)
Each EtherNet/IP device is associated with an .EDS file, containing all necessary information about the device.
This file is used by the network configuration tool during configuration of the network. This file is included on
the documentation CD included in the equipment shipment.

8 About the Fieldbus Interface Module for Ethernet​​ Fieldbus Interface Module for Ethernet
 3 Data Exchange
All data from the fieldbus and the checkweigher is stored in an internal memory buffer. This is a very easy
method for data exchange where the fieldbus control system simply reads and writes data to pre-defined
memory locations, and the checkweigher also uses the same internal memory buffer to read and write data.

Figure 5. Fieldbus Interface Network

3.1 Internal Memory Buffer Structure

The internal memory buffer can be seen as a memory space with three different types of data; input data, output
data and general data.
Input Data
• Data sent to the fieldbus. The FIM can handle up to 512 bytes of Input Data.
Output Data
• Data received from the fieldbus. The FIM can handle up to 512 bytes of Output Data.
General Data
• This data cannot be accessed from the fieldbus.

Fieldbus Interface Module for Ethernet Data Exchange​​ 9

 Figure 6. Internal Memory Buffer Structure

3.2 I/O Data

Data is sent/received on change of value. By default (i.e., when using “Automatic” I/O sizes), all data is treated
as I/O data.

3.3 Memory Map

Memory Location Contents Access
0x0000-0x01FF Input data area R/W
0x0200-0x03FF Output data area RO
0x0400-0x07FB Genera data area R/W
Input data area – this area holds data that should be sent to the fieldbus
Output data area – this area holds data received from the fieldbus
General data area – this data cannot be accessed from the fieldbus

10 Data Exchange​​ Fieldbus Interface Module for Ethernet

 4 Quick Start Guide - Adding to Your Network
Before adding the FIM to your network, review this chapter and consult your network administrator. The module
is by default configured with DHCP enabled. If your network does not use DHCP, then the IP settings must be
set manually. The following manual setting procedures assume the availability of a Microsoft Windows PC on
the same network. Also, note that security features are also available to be customized for your installation (See
Security Framework).

4.1 Connect the Module to Your Network

Make sure that the checkweigher power is off, and connect the checkweigher to the Ethernet network. The
connection point is normally located near or at the bottom of the checkweigher control enclosure. An IP67
bulkhead RJ-45 type jack and mating connector (shipped loose) are normally provided.

4.2 Default IP Settings

The FGM is shipped from the factory with the following default settings:
IP Address 192.150.150.20
Subnet Mask 255.255.255.0
Gateway Address 0.0.0.0
DHCP/BOOTP On
Speed Auto
DNS 1 Address 0.0.0.0
DNS2 Address 0.0.0.0
Host Name <blank>
Domain Name <blank>
Log in User Name* MTPI
Log in Password* XSeries
*User account is used for HTTP, FTP, and Telnet servers only.

4.3 Configuring the IP Address Using DHCP

The module is set by default to send DHCP requests at power up. If your network uses a DHCP server, then all
that is needed is for the server to add the new node to its relation list. The MAC address of the FIM is printed on
the outside of the FIM access cover. The Anybus IPconfig tool may also be installed on a PC and then used to
read the IP and MAC addresses of all FIMs on the network (See Scanning the Network for all Fieldbus interface
Modules). If not using DHCP, then the module DHCP enable setting should be set to off to avoid startup delays
of the module while it attempts to access a DHCP server. There are several ways to change these settings.
Following are three methods for setting the IP Address.

4.4 Configuring the IP Address Using Anybus IPconfig

The HMS Anybus IPconfig tool is provided on the distribution CD. This program may be installed on a Windows
PC and used to scan the network for all Fieldbus Interface modules. Network settings are reported by the tool
including IP and MAC addresses. Please note that the tool will actually find and list all AnyBus-S devices that
are found on your network. Your network could have other applications of the HMS AnyBus-S cards.
1. If not already installed on a Windows PC, install the Anybus IPconfig tool software provided on the Fieldbus
Interface Module CD. The application is installed at Windows Programs/HMS/AnyBus IPconfig/AnyBus
IPconfig.
2. With the Windows PC connected to the same network as the FIM, run the AnyBus IPconfig application
(path is given in the previous step).
3. The program will at start, up and also upon clicking the Scan button, scan the network for all AnyBus
nodes including the FIM. The FIM network information will be displayed as a line in the list.

Fieldbus Interface Module for Ethernet Quick Start Guide - Adding to Your Network​​ 11
 4. Double click the line with the FIM network information. A dialog window will appear providing all the
current network settings.
5. Edit the IP settings on the page according to your network requirements. If you are not using DHCP,
remember to select the DHCP Off radio button.
6. Click the Set button to change the settings in the FIM.

4.5 Configuring the IP Address Using ARP

The IP address can be changed during runtime using the ARP command from a PC. The new IP address will be
stored in the FLASH.
(Note - the configuration switch must be set to 00000000 in order for the ARP command to function correctly)
Below is an example on how to change the IP address from a Windows™ command prompt:
arp -s <IP address> <MAC address>
ping <IP address>
arp -d <IP address>

The arp -s command will store the IP and MAC addresses in the PC’s ARP table. When the ping command is
executed, the PC sends this information to the module using the MAC address. The module detects that it was
addressed with the correct MAC address and adopts the IP address sent by the PC. (The arp -d command is
optional, but it removes the static route from the PC ARP table).
This method can be used to reconfigure modules that already have been configured, or even to reconfigure
modules outside the host’s subnet.
The MAC address is printed on a label on the bottom side of the module. The address should also be marked
on the XRTC Fieldbus Interface Access Cover.
As the Arp command automatically configures the subnet mask to 255.255.255.0, the first three bytes of the
IP address must be the same as for the PC executing the command.
Example:
PC- 10.10.12.67
Module- 10.10.12.x (Where x is a value between 1
and 254)

4.6 Configuring the IP Address Using Web Browser

1. Find the current IP address of the FIM. If this is a new installation, then the FIM IP address should be set to
the default settings listed in the above table. If the IP address is unknown, the HMS AnyBus IPconfig tool
may be used to scan the network and reveal the address (See Scanning the Network for all Fieldbus
Interface Modules).
2. Set your PC to a static IP address within the range of the FIM subnet. A successful ping to the FIM IP
address from a Windows Command Prompt will confirm the subnet settings.
3. Open an internet browser on your PC and enter the HTTP address of the FIM.
Example: http://192.150.150.20
4. Login to the web server using the account user name and password. A Configuration web page should
appear that includes the current FIM IP settings.
5. Edit the IP settings on the page according to your network requirements. If you are not using DHCP,
remember to set the DHCP enabled checkbox to not checked.
6. Cause the settings to be written to the FIM by clicking the STORE CONFIGURATION button. A message will
indicate successful storage.
7. Power cycle the checkweigher to cause new settings to be loaded.
8. Set your PC network settings appropriately for your network.

12 Quick Start Guide - Adding to Your Network​​ Fieldbus Interface Module for Ethernet
 9. To confirm network settings use a ping from a Windows Command Prompt, and/or repeat Step 3 using the
new IP address.

Fieldbus Interface Module for Ethernet Quick Start Guide - Adding to Your Network​​ 13
 5 Filesystem
The filesystem is a fixed-size storage area with a hierarchical directory structure. Files can be grouped in direc-
tories for increased readability.
The filesystem features user password security. The filesystem can be accessed via FTP, Telnet and HTTP.
Case Sensitivity
The file system is case sensitive. This means that the filename ‘AnyBus.txt’ is not identical to the file
‘AnyBus.TXT’.
Filename/Pathname Length
Filenames can be a maximum of 48 characters long. Pathnames can be 256 characters in total, filename
included.
File Size
File size is not restricted. However, the size cannot exceed the space available in the file system.
Free space
Approximately 1.4MB

5.1 FLASH Memory

The non volatile storage area of the filesystem is located in FLASH memory. Each FLASH segment can only be
erased approximately 1000000 times due to the nature of this type of memory.
The following operations will erase one or more FLASH segments:
• Deleting, moving or renaming a file or directory
• Writing or appending data to an existing file
• Formatting the filesystem

5.2 Security Framework

FIM settings may be protected from web, FTP, and Telnet access. The FIM is shipped with a default user name
and password. The user may choose to remove or modify this account. The user may also add user accounts.
The accounts for users are defined in the file ‘sys_pswd.cfg’ in the directory “\pswd\”. Files in this directory
cannot be accessed from a web browser.
The default user name and password are provided in Section 4.2 Default IP Settings. Note that these entries are
case sensitive.
It is also possible to configure which IP addresses and what protocols are allowed to connect to the module,
see ‘ip_accs.cfg’.

14 Filesystem​​ Fieldbus Interface Module for Ethernet

 6 System Files
The module uses these files for configuration purposes. The system files are ASCII files and can be edited with
any text editor. Generally, the module has to be restarted in order for any changes in these files to have effect.
Note: It is very important to follow the exact syntax specifications for each configuration file; otherwise the
module might have problems interpreting it, which can result in a faulty or non-expected behavior.

6.1 Configuration Files 'IP_accs.cfg'

It is possible to configure which IP addresses and what protocols that are allowed to connect to the module.
This information is stored in the file ‘\ip_accs.cfg’. The file contains one or several of the headers below.
[Web]
[FTP]
[Telnet]
[Ethernet/IP]
[All]

Under each header the allowed IP addresses are written. The wildcard ‘*’ can be used to allow series of IP
addresses. If a protocol header is not given, the system will use the configuration set below the header ‘All’. If
the ‘All’ header is not given, the protocol will not accept any connections.
Example:
[Web]
10.10.12.*
10.10.13.*
[FTP]
10.10.12.*
[Telnet]
10.10.12.*
[All]
*.*.*.*

The above example will allow all IP addresses beginning with 10.10.12 to access all protocols in the module.
Addresses beginning with 10.10.13 will be able to access the web server, but not the FTP and Telnet servers.
The Ethernet/IP server will accept connections from any IP address.
The contents of this file can be redirected by placing the line ‘[File path]’ on the first row, and a file path on the
second.
Example:
[File path]
\my_settings\ip_access_rights.cfg

In this example, the settings described above will be loaded from the file ‘\my_settings\ip_ access_rights.cfg’.

6.2 Password Files 'sys_pswd.cfg'

User/password information for web, FTP, and Telnet is stored in the file ‘sys_pswd.cfg’. This file must be placed
in ‘pswd\ directory. This directory is protected from web browser access.
The file format is the following:
User1:password1
User2:password2
...
User3:password3

Fieldbus Interface Module for Ethernet System Files​​ 15

 Example::
User:Password

In this example, the username is ‘User’, and the password is ‘Password’.

If no ‘:’ is present, the password will be equal to the username.
Example:
Username

In this example, both username and password will be ‘Username’.

16 System Files​​ Fieldbus Interface Module for Ethernet

 7 FTP Server
It is possible to upload/download files to/from the file system using a standard FTP client. By default, the FIM
requires user login for access by an FTP client. Upon successful login, the root user directory is accessed.
For more information about the security framework in the module, see “Security Framework.”

Fieldbus Interface Module for Ethernet FTP Server​​ 17

 8 Telnet Server
Through a Telnet client, the user can access the filesystem using a command line interface similar to MS-
DOS™. By default, the FIM requires user login for access by a Telnet client. Upon successful login, the root user
directory is accessed. For more information about the security framework in the module, see “Security
Framework.”

8.1 General Commands

help
Syntax
help [general | diagnostic | filesystem]

If no argument is specified, the following menu will be displayed.

General
commands:

help- Help with menus

version- Display version information
exit- Exit station program

Also try ‘help [general | diagnostic | filesystem]’

version
Syntax:
version

This command will display version information, serial number and MAC ID of the FIM.
exit
Syntax:
exit

This command closes the Telnet session.

8.2 Diagnostic Commands

The following commands can be viewed by the command ‘help diagnostic’
arps
Syntax:
arps

Display ARP stats and table

iface
Syntax:
iface

Display net interface stats

sockets
Syntax:
sockets

Display socket list

routes

18 Telnet Server​​ Fieldbus Interface Module for Ethernet

 Syntax:
routes

Display IP route table

8.3 File System Operations

For commands where filenames, directory names or paths shall be given as an argument the names can be
written directly or within quotes. For names including spaces the filenames must be surrounded by quotes. It is
also possible to use relative pathnames using ‘.’, ‘\’ and ’..’
dir
Syntax:
dir [path]

Lists the contents of a directory. If no path is given, the contents of the current directory is listed.
md
Syntax:
md [[path][directory name]]

Creates a directory. If no path is given, the directory is created in the current directory.
rd
Syntax:
rd [[path][directory name]]

Removes a directory. The directory can only be removed if it is empty.

cd
Syntax:
cd

Changes current directory.

del
Syntax:
del [[path][filename]]

Deletes a file.
ren
Syntax:
ren [[path][old name]] [[path][new name]]

Renames a file or directory.

move
Syntax:
move [[source path][source file]] [[destination path]]

This command moves a file or directory from the source location to a specified destination.
copy
Syntax:
copy [[source path][source file]] [[destination path][destination file]]

This command creates a copy of the source file at a specified location.

type
Syntax:
type [[path][filename]]

Fieldbus Interface Module for Ethernet Telnet Server​​ 19

 Types the contents of a file.
mkfile
Syntax:
mkfile [[path][filename]]

Creates an empty file.

append
Syntax:
append [[path][filename]] [“The line to append”]

Appends a line to a file.

df
Syntax:
df

Displays filesystem info.

20 Telnet Server​​ Fieldbus Interface Module for Ethernet

 9 Ethernet/IP Configuration
Depending on what EtherNet/IP Scanner is used the set up procedure may vary, but when using the Rockwell
ConrolLogix EtherNet/IP Scanner the following properties should be used:
Assembly Instance:
Input 100
Output 150
Configuration: 5; Size: 0
This example assumes that the EtherNet/IP Bridge module has been added to the configu¬ration in the Control
Logix PLC. To add the FIM-EIP to the configuration, right click the PLC in the RSLogix software, and select “New
Module”.
A dialogue window will appear. In this dialogue window, select “Generic Ethernet module” and press OK.

[NOTE: Graphic from "How to configure an EtherNet/IP adapter module with RSLogix 5000, by HMS Industrial
Networks AB, SCM-7032-029 Rev 2.03]
In the next dialogue window, RSLogix will ask for information regarding the communication to the FIM-EIP. First
enter a symbolic name for the FIM-EIP. In the example below the name “HSChecwkweigher_FIM_EIP” is used.

Fieldbus Interface Module for Ethernet Ethernet/IP Configuration​​ 21

 This name will create a tag in RSLogix, which can be used to access the memory location in the PLCs memory
where the data for the FIM-EIP module will be stored. A description can also be added, but that is optional.

Next step is to select the “Comm_Format”, which tells RSLogix the format of the data. In our example here, we
have selected Data-SINT, which will represent the data in the FIM-EIP as a field of 8-bit bytes.
I/O data is accessed in input instance 100 and output instance 150, so these values have to be entered as the
instance values for input and output. The size of the input connection and the output connection whould both
be set to 480 bytes.
The FIM-EIP does not support a configuration assembly, but RSLogix requires a value for this anyway. An
instance value of 0 is not a valid instance ID, but any non-zero value will work, here we have selected the
value 1. The data size of the configuration instance is then set to 0.
As a final step the IP address used for the FIM-EIP should be entered in RSLogix.
When finished, press next.
In the next dialogue window enter a value for the time between each scan of the module. In this example, we
are satisfied with the 10 ms, which is the default value. After this, press finish.
Now the FIM-EIP has been added to the configuration in RSLogix. Select Go Online in the communication
menu, and download the configuration. The configuration will now be downloaded to the PLC, and if no errors
are detected, the window shall look as below.
If there are any errors, a warning triangle will be present on the FIM-EIP in the I/ O configuration listing. Double
click the module to view any error that is reported.

Graphics copied from and is the property of Rockwell Automation

22 Ethernet/IP Configuration​​ Fieldbus Interface Module for Ethernet

 10 Ethernet/IP
EtherNet/IP is based on the Common Industrial Protocol (CIP) which is also the application layer used by
DeviceNet and ControlNet to exchange data between nodes.

10.1 Implemented Objects

EtherNet/IP requires some mandatory objects; these are implemented as well as some vendor specific objects.
The mandatory objects are the ones in the specification from ODVA.
The following vendor specific objects are implemented:
• Identity Object, Class 01h
• Message Router Object, Class 02h
• Assembly Object, Class 04h
• Connection Manager, Class 06h
• Diagnostic object, Class AAh
• TCP/IP Interface Object, Class F5h
• Ethernet Link Object, Class F6h

10.2 Identity Object, Class 01h

Services
Class services: Get Attribute All
Get Attribute Single
Instance services: Get Attribute All
Get Attribute Single
Reset

Class Attributes
# Access Name Type Value Description
1 Get Revision UINT 0001h Revision 2

Instance Attributes
# Access Name Type Value Description
1 Get Vendor ID UINT Default: 005Ah HMS Industrial Networks
AB
2 Get Device Type UINT Default: 000Ch Communication adaptor
3 Get Product Code UNIT Default: 0133h Anybus-C EtherNet/IP
4 Get Revision Struct of:
USINT Major revision of
EtherNet/IP interface
USINT Minor revision of
EtherNet/IP interface
5 Get Status WORD Device status, see table
below
6 Get Serial Number UDINT Module serial Serial number of the
number module
7 Get Product Name SHORT_STRING Anybus-C Name of product
EtherNet/IP

Fieldbus Interface Module for Ethernet Ethernet/IP​​ 23

 Status Attribute Extended Device Status
Bits Name Description Value Meaning
0 Module owned 0000b Unknown
1 Reserved 0010b Faulted I/O
connection
2 Configured 0011b No I/O connection
established
3 Reserved 0100b Non-volatile
configuration bad
4-7 Extended device See table on right 0110b Connection in
status Run mode
8 Minor recoverable 0111b Connection in Idle
fault mode
9 Minor Recov-
eralbe fault
10 Major recoverable
fault
11 Major unrecov-
erable fault
12-15 Reserved

10.3 Message Router Object, Class 02h

Services
Class services: -
Instance services: -

10.4 Assembly Object,Class 04h

Services
Class services: Get Attribute Single
Instance services: Get Attribute Single
Set Attribute Single

Description
The Assembly Object binds all mapped I/O data. This data is used for I/O connections
Class Attributes
# Access Name Type Value Description
1 Get Revision UINT 0002h Revision 2
2 Get Max Instance UINT The highest
initiated instance
no.

Instance Attributes – instance/connection point 64h (IN)

# Access Name Type Value Description
3 Set Data Array of BYTE Data consumed
by FGM

24 Ethernet/IP​​ Fieldbus Interface Module for Ethernet

 Note: if the I/O input data size is set to 0, this instance will not be initialized

10.5 Diagnostic Object, Class AAh

Services
Class services: Get Attribute All
Instance services: Get Attribute Single

Description
This vendor-specific object provides diagnostic information from the module.

Class Attributes
# Access Name Type Value Description
1 Get Revision UINT 0001h Revision 1
Instance Attributes -Instance 01h
# Access Name Type Description
01h Get Module and serial UDINT Serial number
number
03h Get Fieldbus type UINT Fieldbus type, in this
case TBD
04h Get Module software UINT Ethernet interface
version sofware version
0Fh Get Input I/O size UINT Size of I/O input area
(in bytes)
11h Get Input total size UINT TBD
12h Get Output I/O size UINT Size of I/O output
area (in bytes)
14h Get Output total size UINT Total number of
output bytes (I/O+
TBD)
1h118h Get MAC ID Array of USINT Ethernet MAC ID of
the module (6 bytes)
19h Get IP address UDINT Currently configured
IP address
1Ah Get Subnet mask UDINT Currently configured
subnet mask
1Bh Get Gateway address UDINT Currently configured
default gateway
address
1Ch Get SMTP server address UDINT SMTP server address
1Dh Get DHCP state UDINT 0=No DHCP,
1=DHCP available
1Eh Get Bootloader version UDINT Ethernet interface
Bootloader firmware
version

10.6 TCP/IP Interface Object, Class F5h

Services

Fieldbus Interface Module for Ethernet Ethernet/IP​​ 25

 Class services: Get Attribute All
Get Attribute Single
Instance services: Get Attribute All
Class services:
Get Attribute Single
Set Attribute Single

Description
This object provides a mechanism to configure the TCP/IP settings via EtherNet/IP.

Class Attributes
# Access Name Type Value Description
1 Get Revision UINT 0001h Revision
2 Get Max instance UINT 0001h 1 is the highest
instance number
3 Get No. of instances UINT 0001h 1 instance is
implemented

Instance Attributes
# Access Name Type Value Description
1 Get Status DWORD 00000001h 1= the interface
configuration
attribute contans a
valid configuration
2 Get Capability config- DWORD 000000014h Interface configu-
uration ration attribute is
settable. Capable
of obtaining
network configu-
ration via DHCP
3 Get/Set Configuration DWORD 0- configuration
control from non-volatile
memory
2- configuration
from DHCP
4 Get Port object Struct of: Physical linK - >
Ethernet object
Path size UINT 0002h 2 words
path Padded EPATH 20 F6 24 01h EtherNet class,
instance 1
5 Get/Set Interface configu- Struct of:
ration
IP address UDINT Currently used IP
address
Subnet mask UDINT Currently used
subnet mask
Gateway address UDINT Currently used
gateway address
Name server 1 UDINT Primary DNS
server

26 Ethernet/IP​​ Fieldbus Interface Module for Ethernet

 # Access Name Type Value Description
Name server 2 UDINT Secondary DNS
server
Domain name STRING Default domain
name
6 Get/Set Host name STRING Host name

10.7 Ethernet Link Object, Class F6h

Services

Class services: Get Attribute All

Get Attribute Single
Instance services: Get Attribute All
Get Attribute Single

Description
This object maintains link-specific counters and status information for the Ethernet communication interface.
Class Attributes
# Access Name Type Value Description
1 Get Revision UINT 0001h Revision 2 TBD
2 Get Max instance UINT 0001h 1 is the highest
instance number
3 Get No. of instances UINT 0001h 1 instance is
implemented

Instance Attributes
# Access Name Type Value Description
1 Get Interface speed UDINT 10 or 100 The actual speed
(MBPS) of the module
2 Get Interface flags DWORD
3 Get Physical address Array of 6 USINTS MAC Address Ethernet MAC
address of the
module
6 Get/Set Interface control Struct of: Configured
Control bits- interface auto-
WORD negotiation,
duplex and
Forces speed-
speed
UNIT

Fieldbus Interface Module for Ethernet Ethernet/IP​​ 27

 11 Appendix - TCP/IP Configuration Basics
11.1 IP address
The IP address is used to identify each node on the TCP/IP network. Therefore, each node on the network must
have a unique IP address. IP addresses are written as four decimal integers (0-255) separated by periods,
where each integer represents the binary value of one byte in the IP address. This is called dotted-decimal
notation.

Example: Address 10000000 00001010 00000010 00011110 is written as 128.10.2.30

11.2 Subnet Mask

The IP address is divided into three parts - net ID, subnet ID and host ID. To separate the net ID and the subnet
ID from the host ID, a subnet mask is used. The subnet mask is a 32-bit binary pattern, where a set bit
allocates a bit for network/subnet ID, and a cleared bit allocates a bit for the host ID. Like the IP address, the
subnet mask is commonly written in dotted-decimal notation.
Example:
To make the IP address 128.10.2.30 belong to subnet 128.10.2, the subnet mask shall be set to
255.255.255.0.

Note: To be able to establish communication between two devices both devices must belong to the same
subnet. If not, the communication must be done through a gateway. It is therefore recommended to configure
the module to the same subnet as your PC.

11.3 Special Case IP addresses

Devices on an Ethernet network are not allowed to be configured to the following IP addresses; therefore do not
configure the module to use any of them.

0.xx x- IP address where the first byte is zero

127.x.x.x - IP address where the fist byte is 127
x.x.x.0 - IP address where the last byte is zero
x.x.x.255 - IP addrss where the last byte is 255

28 Appendix - TCP/IP Configuration Basics​​ Fieldbus Interface Module for Ethernet

 12 Appendix- Connector Pin Assignments
12.1 Ethernet Connector

Pin Signal
Housing Cable Shield
1 TD+
2 TD-
3 RD+
4 Termination
5 Termination
6 RD-
7 Termination
8 Termination

Fieldbus Interface Module for Ethernet Appendix- Connector Pin Assignments ​ 29

 13 Appendix - Technical Specifications
13.1 Mechanical
Dimensions
86 mm x 54 mm x 15 mm, L x W x H
(inches: 3.38 x 2.13 x 0.59; L x W x H)

13.2 Electrical
Power Supply
Power: 24V ± 10%
Power Consumption
Maximum power consumption is 450 mA on 24V

13.3 Environment
Relative Humidity
The product is designed for a relative humidity of 0 to 95% non-condensing
Temperature

Operating: 0°C to +70°C

Non Operating: -25°C to +85°C

13.4 EMC Compliance

CE-mark
Certified according to European standards unless otherwise is stated
Emission
Tested per EN 55022 Class A: 1997

Immunity
According to EN 61000-6-2:1999

Tested per EN61000-4-2:1995

EN 61000-4-3:1996
EN 61000-4-4:1995
EN 61000-4-5:1995
EN 61000-4-6:1996

30 Appendix - Technical Specifications​​ Fieldbus Interface Module for Ethernet

 14 Appendix - ASCII Table

Fieldbus Interface Module for Ethernet Appendix - ASCII Table​​ 31

32 Appendix - ASCII Table​​ Fieldbus Interface Module for Ethernet
 www.mt.com
For more information

Mettler-Toledo Hi-Speed
1571 Northpointe Parkway
Lutz, FL 33558, USA
Tel. +1 813 889 9500
Fax +1 813 881 0840
www.mt.com/contact

Subject to technical changes.

© Mettler-Toledo Hi-Speed 03/2018
66100056
66100056C