General
This "Basic Module Information" (BMI) provides quick access to a list of the main module functions, some attributes, and the location of more detailed module information.
NOTE
: When developing an application, or troubleshooting a significant problem, it is
IMPORTANT
to read and follow more detailed module information, including safety recommendations.
The primary source of detailed module information is the SLP85xD User Manual available from www.mt.com/SLP85xD. This is referred to as the "manual" in this BMI.NOTE: In this BMI, the word "tag" refers to data tags in the Logix controller.
Function
The SLP85xD EtherNet/IP interface enables the SLP85xD to communicate to EtherNet/IP Programmable Logic Controllers (PLCs) through a direct connection to the EtherNet/IP network at 100 MBPS speed. SLP85xD modules with their slim, compact design, and with a built-in Ethernet/IP interface, are tailored for multi-line automation networks which are directly connected to control systems. Various types of data exchange to allow reading and writing of different weighing and control parameters for the SLP85xD are available. Configuration to setup the type of data exchange resides in the SLP85xD, and is also available by using the APW-Link PC Tool-based setup.
Features
- User programmable IP address, Subnet Mask and Gateway address.
- Unicast I/O for EtherNet/IP allows for direct point-to-point communication between two devices on a network. This communication format is more efficient when I/O data does not need to be shared between multiple target devices.
- Capability for bi-directional discrete mode communications (Class 1 Cyclic Messaging) of weight, status, and control data between the PLC and the SLP85xD.
- Support for Explicit Messaging to access SLP85xD internal variables.
- Offers specific Data Okay and Heartbeat bits to allow the PLC to confirm that data exchange is valid and working.
- Status LEDs to indicate communication, network and module status.
Network, Power, Serial Configuration, and I/O Connectors
Refer to manual for pinouts and Rockwell Automation part numbers of mating Ethernet/IP connector.
- A range of cables are available from Mettler Toledo that provide a shared connection for Ethernet/IP communications, 10 to 30 VDC power (12 VDC Nominal), and an RS232 configuration port. Refer to the SLP85xD Installation Manual available from www.mt.com/SLP85xD for communications and power wiring. A seperate cable is available to provide I/O from the module.
- The cable installation procedures and specification including distance and termination requirements are the same as recommended by Allen-Bradley for the EtherNet/IP connection.
Module Identity
The module Identity includes the following Device attributes:
- Vendor ID '666', and Vendor Name string 'METTLER TOLEDO'
- Product Type '43', and Product Type Name string 'Generic Device'
- Product Code '8705', and Product Name string 'SLP85xD EtherNet/IP'
- Catalog Name string 'MT-302193xx'
Communications
The SLP85xD EtherNet/IP Interface uses EtherNet/IP Implicit communication for transferring I/O data to a controller. Certain data can also be accessed using EtherNet/IP explicit messaging. CIP messages are supported from a host device over the EtherNet/IP network.
Note
: Refer to the manual for full details of these communication protocols.Input and Output Tag Data
The SLP85xD's PLC I/O Interface is based on the Mettler Toledo Standard Automation Interface (SAI). This interface provides a standard protocol for all Mettler Toledo devices so that the user can access them in the same way, and expect that they respond to the same basic set of commands.
The SLP85xD implements ONLY 2-Block Mode communications. However, since 1-Block mode is included in the 2-Block mode format definition, we will describe both modes here

1-Block
Format (shown above) is the most basic method of communicating using the SAI protocal. It returns a Single Precision Floating Point value from the device, along with command and scale status words, for a total of four words (8 bytes). Four words (8 bytes) of output data from the PLC are also accepted by the device so that a Single Precision Floating Point command value can be sent to the device, along with a 16-bit command word.In devices that have more than one channel, the 16 bit Channel Mask can be used to send the same commands to more than one channel at the same time. Since the SLP85xD is a single channel device, the Channel Mask is usually ignored. However, there are some special commands (such as the Test Command) that require this value to be populated. Because the Channel Mask can still sometimes take on a function and impact how the device responds,
it is recommended that the value always be set to zero
when not using one of the special commands.
2-Block
Format (default - shown above) provides a total of 8 words (16 bytes) of I/O in both directions by using the basic 1-Block format, and adding another 4 words (8 bytes) of status information.From a functional standpoint, only a Command Word is added to the Controller Outputs in 2-Block format. The Command Word is used to tell the device which combinations of status words should be returned to the Controller. The remaining Output words are currently reserved for future use.
The SLP85xD is only capable of communicating with the 2-Block format (16 bytes in each direction). As such, the Fieldbus format shown below cannot be changed.

Note
: Logix IO tags are updated by the controller asynchronous to its ladder-logic program scan. When "block integrity" of this data is important, the CPS ladder instruction should be used to synchronously copy the data to other Logix tags for use by the application logic. Also Note:
Default RPI
for the IO connection is 10ms
. It is important to set the Requested Packet Interval for an update time suitable for the application. The update time chosen determines how often the host will receive Input Image updates from the SLP85xD EtherNet/IP Interface. A very long RPI will result in events taking place at the SLP85xD EtherNet/IP Interface module that may never be seen by the host logic.1 Block Format Tags
Below is the view of an SLP85xD device
1-Block Input tags.
Note that the Floating Point value returned from the device can be accessed with the MB1_Measuring_Value
tag. The Scale Status bits can be accessed as a word with the MB1_Device_Status
tag, or by accessing the individual bit tags expanded below it. The MB1_Response
tag will echo back the last command sent to the device after the command has been accepted. 1 Block Input Tags

Below is the view of an SLP85xD device 1-Block Output tags. Note that the Floating Point value written to the device can be accessed with the
MB1_Command_Value
tag. The actual command sent to the device is written in the tag MB1_Command
. The MB1_Channel_Mask
(and the corresponding bit tags below it) are not used on the SLP85xD since it is a single channel device - except for some special commands such as the Test Mode.1 Block Output Tags

2 Block Format Tags
2 Block format takes the 1 Block tags and adds the Status Command on the PLC/DCS Output, and the Status Group words with Response Word on the PLC/DCS Input.
Below is a view of the SLP85xD Status Block tags added onto the
1 Block
tags to make up the 2-Block Input format. The bits in the individual status groups will change meaning depending on what Status Block Command is being sent by the PLC/DCS system in the Outputs. The PLC programmer will need to use care when looking at these bits to ensure that the bit interpretations take the command response (SB1_Response
) value into account to understand the proper meaning.2 Block Input Tags

Below is the view of an SLP85xD device
2-Block Output
tags. Note that the Status Block is appended after the 1-Block
tags, so that both structures are now present. The first three words of the Status Block are reserved for future use. The last word is a Command value from the Controller to the SLP85xD to select predefined combinations of Status Words to be returned to the Controller's Inputs. Please refer to the manual for details the definitions for the commands and the status bits returned in each Status Word.2 Block Output Tags

Provide Feedback