Micro Motion 5700 transmitter Integration Guide
The Micro Motion 5700 transmitter is a versatile device that can be used in a variety of applications, including flow measurement, batching, and process control. It features Ethernet connectivity for easy integration into your control system and provides a wide range of measurement capabilities, including mass flow, volume flow, density, and temperature. The transmitter is also compatible with Rockwell RSLogix 5000 software, making it easy to configure and use.
advertisement
Integration Guide
MMI-20029770, Rev AA
March 2016
Micro Motion
®
Model 5700 Transmitters
EtherNet/IP Rockwell RSLogix Integration Guide
Emerson Flow customer service
Email:
•
•
Worldwide:
Asia-Pacific:
Telephone:
North and South America
United States
Canada
Mexico
800-522-6277
+1 303-527-5200
Europe and Middle East
U.K.
The Netherlands
+41 (0) 41 7686 111 France
Asia Pacific
0870 240 1978 Australia
+31 (0) 704 136 666 New Zealand
0800 917 901 India
Argentina
Brazil
Venezuela
+54 11 4837 7000
+55 15 3413 8000
+58 26 1731 3446
Germany
Italy
Central & Eastern
Russia/CIS
Egypt
Oman
Qatar
Kuwait
South Africa
Saudi Arabia
UAE
0800 182 5347
8008 77334
800 70101
431 0044
663 299 01
800 991 390
800 844 9564
800 0444 0684
Pakistan
China
+41 (0) 41 7686 111 Japan
+7 495 981 9811 South Korea
0800 000 0015 Singapore
Thailand
Malaysia
800 158 727
099 128 804
800 440 1468
888 550 2682
+86 21 2892 9000
+81 3 5769 6803
+82 2 3438 4600
+65 6 777 8211
001 800 441 6426
800 814 008
Contents
Contents
Appendices and reference
Appendix A Assembly object (04
– 16 instances) .........................................................................18
– 1 instance) .............................................................................. 32
EtherNet/IP Rockwell RSLogix Integration Guide
i
Contents ii
Micro Motion ® Model 5700 EtherNet/IP transmitters
1
1.1
1.2
Before you begin
Before you begin
Topics covered in this chapter:
•
About this document
•
Related documentation
About this document
This document provides information about how to integrate a Micro Motion Model 5700
Ethernet EtherNet/IP transmitter with Rockwell RSLogix 5000.
The information in this document assumes that users understand:
• Transmitter programming concepts and procedures
• All corporate, local government, and national government safety standards and requirements that guard against data loss, equipment failure, injuries, or death
Related documentation
You can find all product documentation via the Micro Motion product documentation DVD shipped with the product or at
www.micromotion.com
.
Table 1-1: Additional documentation and resources
Topic
Transmitter installation
Hazardous area installation
Transmitter configuration and use
Product Data Sheet
Modbus configuration
Document
Micro Motion Model 5700 Transmitters Ethernet Installation Manual
See the approval documentation shipped with the transmitter, or download the appropriate documentation from the
Micro Motion web site at
www.micromotion.com
.
Micro Motion Model 5700 Transmitters Ethernet Configuration and
Use Manual
Micro Motion Model 5700 Product Data Sheet (PDS)
Modbus Interface Tool (MIT) — available at
www.micromotion.com
EtherNet/IP Rockwell RSLogix Integration Guide
1
Model 5700 transmitters in Ethernet networks
2
2.1
Model 5700 transmitters in Ethernet networks
Topics covered in this chapter:
•
Star topology
•
Ring topology
•
Daisy-chain topology
•
•
You can install the Model 5700 transmitter in star, ring, or daisy-chain networks using industrial-rated shielded Ethernet cables.
Make sure that each cable is no longer than 100 meters.
Connect the Model 5700 transmitter to the host system via a LAN (Local Area
Network) and not a WAN (Wide Area Network).
• Follow all network security best practices.
Star topology
Model 5700 transmitters can be installed in a star network.
Figure 2-1: Model 5700 star network
2
A.
B.
C.
Programmable Logic Controller (PLC)
Model 5700 with Ethernet output
External Ethernet switch
Micro Motion ® Model 5700 EtherNet/IP transmitters
2.2
Model 5700 transmitters in Ethernet networks
Ring topology
Model 5700 transmitters can be installed in a ring network.
Figure 2-2: Model 5700 ring network
2.3
A.
B.
Programmable Logic Controller (PLC)
Model 5700 with Ethernet output
Daisy-chain topology
Model 5700 transmitters can be installed in a daisy-chain network.
Figure 2-3: Model 5700 daisy-chain network
A.
B.
Programmable Logic Controller (PLC)
Model 5700 with Ethernet output
EtherNet/IP Rockwell RSLogix Integration Guide
3
Integrate with RSLogix 5000
3
3.1
Integrate with RSLogix 5000
Topics covered in this chapter:
•
Integrate with Rockwell RSLogix 5000 versions 20 and later
•
Integrate with Rockwell RSLogix 5000 versions 19 and earlier
Integrate with Rockwell RSLogix 5000 versions
20 and later
If you have Rockwell RSLogix 5000 version 20 or later firmware and programming software, use this section to load the Model 5700 Electronic Data Sheet (EDS) and commission the device using the RSLogix 5000 programming package.
Prerequisites
If you are upgrading the EDS from an older version, unregister the old EDS first using the
RSLogix 5000 EDS Hardware Installation Tool at Tools > EDS Hardware Installation Tool.
Procedure
1.
Download the EDS file using one of the following methods:
4
Micro Motion ® Model 5700 EtherNet/IP transmitters
Integrate with RSLogix 5000
Option
Use a USB memory drive
Description
a. Insert a USB memory drive into the Model 5700 Ethernet service port.
The service port connection is located under the transmitter cap.
Download the file
b. From the transmitter display, choose Menu > USB Options > Transmitter > USB
Drive > Download Support Files > EDS file.
c. Follow the menu to copy the EDS file to the memory drive.
d. Copy the zip file from the USB memory drive to the PC where RSLogix 5000 is installed.
e. Unzip the file to a chosen location.
f. In RSLogix 5000, choose Tools > EDS Hardware Installation Tool and register the
Model 5700 EDS file.
a. Download the EDS from the Micro Motion Model 5700 Ethernet product website.
b. Unzip the file to a chosen location.
c. In RSLogix 5000, choose Tools > EDS Hardware Installation Tool and register the
Model 5700 EDS file.
EtherNet/IP Rockwell RSLogix Integration Guide
5
Integrate with RSLogix 5000
Option
Use
RSLinx
Description
a. Using RSLinx, start RSLinx Classic.
Note
The Model 5700 transmitter must be active on the EtherNet/IP network.
b. Choose Communications > RSWho.
c. Expand the appropriate network card in the left panel tree.
d. From the device pane, right-click 5700 Transmitter.
e. Choose Upload EDS File from Device.
f. Follow the prompts from the Rockwell Automation's EDS Wizard to register the EDS.
2.
If you have an established RSLogix Ethernet network, skip this step. If not, follow these steps to create a network: a. From RSLogix 5000, right-click the controller/backplane in the tree view.
Example:
6 b. Select New Module….
c. Select the appropriate Ethernet card.
d. Select Create.
Micro Motion ® Model 5700 EtherNet/IP transmitters
Integrate with RSLogix 5000 e. Enter the Name.
f. Enter the IP Address.
g. Select the Slot where your Ethernet card is located.
h. Select OK.
i. On the Select Module Type window, select Close.
3.
To add the Model 5700 Ethernet device to the RSLogix 5000 Ethernet network, right-click the Ethernet network and select New Module…
Example: a. Select the Model 5700 from the Select Module Type window and press Create.
Example:
EtherNet/IP Rockwell RSLogix Integration Guide
7
Integrate with RSLogix 5000
The New Module properties dialog is displayed. The EDS generates an Add On
Profile (AOP) for the Model 5700 that loads all the variables into the controller's input and output image tables as named variables with the correct data types.
b. Enter the Name of the module.
c. Enter the IP Address.
4.
Change or keep the current connection type.
Option
To change the connection type
To keep the current connection type
5.
From the General tab, change the connection type: a. Select the Change… button.
Example:
Description
.
.
8 b. Click the current connection.
Default = Mass Flow In & Basic
A pull-down menu with all the available connection types is displayed. For
Micro Motion ® Model 5700 EtherNet/IP transmitters
Integrate with RSLogix 5000 c. Select your appropriate connection, and press OK.
CAUTION!
If you change the connection after the device goes online, you will need to take the controller offline in order for the change to take effect.
6.
On the New Module properties dialog, click OK.
7.
On the Select Module Type dialog, click Close.
8.
Open Controller Tags to verify the organization of data.
EtherNet/IP Rockwell RSLogix Integration Guide
9
Integrate with RSLogix 5000
3.2
Integrate with Rockwell RSLogix 5000 versions
19 and earlier
Use this section if you have Rockwell RSLogix 5000 version 19 or earlier firmware and programming software. These early versions do not support the Model 5700 Electronic
Data Sheet (EDS)-generated Add On Profile (AOP). Instead, you must use the generic module hardware tree.
1.
Download the EDS file using one of the following methods:
10
Micro Motion ® Model 5700 EtherNet/IP transmitters
Integrate with RSLogix 5000
Option
Use a USB memory drive
Description
a. Insert a USB memory drive into the Model 5700 Ethernet service port.
The service port connection is located under the transmitter cap.
Download the file
b. From the transmitter display, choose Menu > USB Options > Transmitter >
USB Drive > Download Support Files > EDS file.
c. Follow the menu to copy the EDS file to the memory drive.
d. Copy the zip file from the USB memory drive to the PC where RSLogix
5000 is installed.
e. Unzip the file to a chosen location.
a. Download the EDS from the Micro Motion Model 5700 Ethernet product website.
b. Unzip the file to a chosen location.
2.
In RSLogix 5000, choose Tools > EDS Hardware Installation Tool and register the Model
5700 EDS file.
3.
If you have an established RSLogix Ethernet network, skip this step. If not, follow these steps to create a network: a. From RSLogix 5000, right-click the controller/backplane in the tree view.
Example:
EtherNet/IP Rockwell RSLogix Integration Guide
11
Integrate with RSLogix 5000 b. Select New Module….
c. Select the appropriate Ethernet card.
d. Select Create.
e. Enter the Name.
f. Enter the IP Address.
g. Select the Slot where your Ethernet card is located.
h. Select OK.
i. On the Select Module Type window, select Close.
4.
From RSLogix 5000, choose File > New.
5.
Select your version from the Revision drop-down menu.
6.
Enter a Name for your application.
7.
Select the Slot where your Ethernet card is located.
8.
Press OK.
9.
From the By Vendor tab, select ETHERNET-MODULE Generic Ethernet Module.
Example:
12
10.
Select OK.
11.
Select Data-DINT as the module data type.
12.
Select the appropriate assembly instances for your application.
Enter the assembly numbers in the generic module setup, along with the data sizes
Example:
Micro Motion ® Model 5700 EtherNet/IP transmitters
Integrate with RSLogix 5000 a. Input = 101 b. Output = 150 c. Configuration = 1
Note
The Model 5700 does not use a Configuration instance. Enter 1 in the Assembly Instance column, and 0 length for the Size column.
13.
Enter the IP Address of the Model 5700.
14.
Press OK.
15.
Open Controller Tags to see the data organization.
EtherNet/IP Rockwell RSLogix Integration Guide
13
Integrate with RSLogix 5000
16.
Use your preferred programming techniques to convert the data from the input and output image tables to the correct data types.
• As the Model 5700 process variables are generally type REAL, use the COP command to convert them.
• The byte ordering is correct, so no byte swapping is needed.
Example:
14
Micro Motion ® Model 5700 EtherNet/IP transmitters
4
Explicit (messaging) variables
Explicit (messaging) variables
The programming for explicit variables is the same regardless of the controller firmware version. Explicit messaging differs from implicit messaging in that the service code and class refer to a Modbus data type rather than a specific data item. The message source element provides the location of the desired data in the Model 5700's database. The only difference is that the Common Industrial Protocol (CIP) message type refers to a type of data in the Model 5700's internal database rather than a specific data item. The desired data item is referenced as the Modbus address in the CIP message. The data item does not
have to be part of an assembly, so in the example in
, a batcher data item is requested to be read.
• For more information about CIP message codes, see
• For more information about Modbus addresses and their lengths, see the Modbus
Interface Tool (MIT) available at
www.micromotion.com
.
Note
After finding a Modbus address in the MIT, subtract 1 from that address when referencing it in the Msg in the following procedure.
Procedure
1.
Create the Msg and select it.
2.
Select the Source Element that was previously created as a controller scope tag.
Figure 4-1: Batch status message
Example:
The following example shows a message that writes data to the Model 5700 database.
The Automatic Overshoot Compensation (AOC) value is a floating point number that you will need to convert to integer format using a COP command prior to referencing it in the Source Element of the message.
EtherNet/IP Rockwell RSLogix Integration Guide
15
Explicit (messaging) variables
Combine the AOC value with the Model 5700 database (Modbus) address and length to form the message's source element. This can be an array as shown in the following graphic or a user-defined data type (UDT). The first element is the Modbus address (zero based), the second is the length, and finally the data in integer (INT) format.
16
The address and data length will be returned if the write is successful. For example,
Set_AOC_Rtn.
Micro Motion ® Model 5700 EtherNet/IP transmitters
Explicit (messaging) variables
EtherNet/IP Rockwell RSLogix Integration Guide
17
Assembly object (04
HEX
– 16 instances)
Appendix A
Assembly object (04
HEX
– 16 instances)
Topics covered in this appendix:
•
Class attributes
•
Input assemblies
•
Output assemblies
•
Output Only Heartbeat (instance 253)
•
Input Only Heartbeat (instance 254)
•
Listen Only Heartbeat (instance 255)
•
Usage notes
•
Common services
A.1
Class attributes
Class attributes (instance 0)
Attribute ID
1
2
Name
Revision
Max instance
Data type
UINT
UINT
Data value
2
255
Access rule
Get
Get
A.2
18
Input assemblies
Table A-1: Class attributes (Instances 100-107)
Attribute ID
3
Name
Input data
Data type
DWORD[varies]
Data value
0
Table A-2: Common input data
Assembly
Dword index
0
1
2
Name
Mass Flow
Temperature
Density
Access rule
Get
Data type
REAL
REAL
REAL
Micro Motion ® Model 5700 EtherNet/IP transmitters
Assembly object (04
HEX
– 16 instances)
Table A-2: Common input data
(continued)
Assembly
Dword index
3
4
5
6
7
8
Name
Drive Gain
Totalizer 1 (default = Mass Total)
Inventory 1 (default = Mass Inventory)
Status
Severity
Counter/Heartbeat (bits
16-32)
Alert detail
Communications error
• Bit #0 = Immediate Failure
• Bit #1 = Last Measure Value
Failure
• Bit #2 = Function Check
• Bit #3 = Out of Specification
• Bit #4 = Maintenance Required
The PLC will display the counter/heartbeat as a signed INT, therefore the counter can be negative.
• Bit #0 = Electronics Failure
• Bit #1 = Sensor Failed
• Bit #2 = Configuration Error
• Bit #3 = Core Low Power
• Bit #4 = Security Breach
• Bit #5 = Sensor-Transmitter
• Bit #6 = Tube Not Full
• Bit #7 = Extreme Primary
Purpose Variable
• Bit #8 = Reserved
• Bit #9 = Flowmeter Initializing
• Bit #10 = Function Check in
Progress
• Bit #11 = Sensor Being Simulated
• Bit #12 = Output Fixed
• Bit #13 = Drive Over Range
• Bit #14 = Process Aberration
• Bit #15 = Discrete Event X
Active
• Bit #16 = Output Saturated
• Bit #17 = Function Check
Failed
• Bit #18 = Data Loss Possible
Echo Output Data Discrete Actions
Data type
REAL
REAL
REAL
DWORD
DWORD
DWORD
EtherNet/IP Rockwell RSLogix Integration Guide
19
Assembly object (04
HEX
– 16 instances)
Table A-3: Liquid volume flow
Assembly
Dword index
0–8
9
10
11
Name
Mass Flow
Volume Flow
Totalizer 2 (default = Volume Total)
Inventory 2 (default = Volume Inventory)
Table A-4: Gas volume flow
Assembly
Dword index
0–8
9
10
11
Name
Mass Flow
Gas Volume Flow
Totalizer 4 (default = Gas Volume Total)
Inventory 4 (default = Gas Volume Inventory)
Table A-5: API Referral
15
16
17
18
12
13
14
Assembly
Dword index
0–8
9
10
11
Name
Mass Flow
Volume Flow
Totalizer 2 (default = Volume Total)
Inventory 2 (default = Volume Inventory)
Corrected Density
Corrected Vol Flow
Totalizer 3 (default = Corrected Vol Total)
Inventory 3 (default = Corrected Vol Inv)
Avg Density
Avg Temperature
CTL
Data type
See
REAL
REAL
REAL
Data type
REAL
REAL
REAL
Data type
REAL
REAL
REAL
REAL
REAL
REAL
REAL
REAL
REAL
REAL
20
Micro Motion ® Model 5700 EtherNet/IP transmitters
Table A-6: Concentration Measurement
19
20
21
16
17
18
22
23
24
Assembly
Dword index
0–8
9
10
11
12
13
14
15
Name
Mass Flow
Volume Flow
Totalizer 2 (default = Volume Total)
Inventory 2 (default = Volume Inventory)
Density at Reference
Std Vol Flow Rate
Totalizer 5 (default = Std Vol Total)
Inventory 5 (default = Std Vol Inv)
Net Mass Flow Rate
Totalizer 6 (default = Net Mass Total)
Inventory 6 (default = Net Mass Inv)
Net Vol Flow Rate
Totalizer 7 (default = Net Vol Flow Total)
Inventory 7 (default = Net Vol Flow Inv)
Concentration
Density - Fixed SG Units
Density - Fixed Baume Units
Table A-7: Batcher
Assembly
Dword index
0–8
9–11
12
13
14
Name
Mass Flow
Liquid Volume
Batch Total
Overshoot Compensation Value (Reg 1457)
Batch Fill Time
Assembly object (04
HEX
– 16 instances)
REAL
REAL
REAL
REAL
REAL
REAL
REAL
REAL
REAL
Data type
See
REAL
REAL
REAL
REAL
REAL
REAL
REAL
Data type
See
REAL
REAL
REAL
EtherNet/IP Rockwell RSLogix Integration Guide
21
Assembly object (04
HEX
– 16 instances)
Table A-7: Batcher
(continued)
Assembly
Dword index
15
Name
Fill status and diagnostics
• Bit #0 - Primary Fill in progress (reg 2495 bit 0)
• Bit #1 - Primary AOC training (reg 2495 bit 9)
• Bit #2 = Primary Valve (reg 2495 bit 5
• Bit #3 = Undefined
• Bit #4 = Undefined
• Bit #5 = Undefined
• Bit #6 - Fill Start Not Okay (reg 2496 bit 0)
• Bit #7 - AOC Flow Rate Too High (reg 2496 bit 1)
• Bit #8 - Maximum Fill Time Exceeded (reg 2496 bit
2)
• Bit #9 - Slug Flow (reg 2496 bit 3)
• Bit #10 - Tube Not Full (reg 2496 bit 4)
• Bit #11 - Drive Overrange (reg 2496 bit 5)
• Bit #12 - Critical Sensor Failure (reg 2496 bit 6)
• Bit #13 - Critical Transmitter Failure (reg 2496 bit 7)
• Bit #14 - Density Out of Limits (reg 2496 bit 8)
• Bit #15 - Temperature Out of Limits (reg 2496 bit 9)
• Bit #16 - Bit #31 for future expansion
Table A-8: Small input configurable data set
Assembly
Dword index
0–8
9–16
Name
Mass Flow
8 configurable slots
Data type
DWORD
Data type
See
REAL *8
Table A-9: Medium input configurable data set
Assembly
Dword index
0–8
9–24
Name
Mass Flow
16 configurable slots
Data type
See
REAL *16
22
Micro Motion ® Model 5700 EtherNet/IP transmitters
Assembly object (04
HEX
– 16 instances)
Table A-10: Large input configurable data set
Assembly
Dword index
0–8
9–40
Name
Mass Flow
32 configurable slots
Table A-11: Advanced Phase Measurement (APM) – liquid
15
16
17
12
13
14
18
19
Assembly
Dword index
0–8
9
10
11
23
24
25
20
21
22
26
27
Name
Mass Flow
Volume Flow
Volume Total
Volume Inventory
Gas Void Fraction
Contract Total 1
Contract Total 2
Contract Total 3
Contract Total 4
Net Oil Flow @ Line
Net Water Flow @ Line
Watercut @ Line
Net Oil Total @ Line
Net Water Total @ Line
Density Oil @ Line
Net Oil Flow @ Ref
Net Water Flow @ Ref
Watercut @ Ref
Net Oil Total @ Ref
Net Water Total @ Ref
Data type
See
REAL *32
Data type
REAL
REAL
REAL
REAL
REAL
REAL
REAL
REAL
REAL
REAL
REAL
REAL
REAL
REAL
REAL
REAL
REAL
REAL
REAL
Table A-12: Advanced Phase Measurement (APM) – gas volume
Assembly
Dword index
0–8
Name
Mass Flow
Data type
See
EtherNet/IP Rockwell RSLogix Integration Guide
23
Assembly object (04
HEX
– 16 instances)
Table A-12: Advanced Phase Measurement (APM) – gas volume
(continued)
15
16
17
12
13
14
Assembly
Dword index
9
10
11
Name
Gas Volume Flow
Gas Volume Total
Gas Volume Inventory
Contract Total 1
Contract Total 2
Contract Total 3
Contract Total 4
Total time mist detected
APM Status
•
Bit #0 – TMR Algorithm Active (reg 433 bit 12)
• Bit #1 – Bit #15 currently not defined
• Bit #16 – Bit #31 for future expansion
Data type
REAL
REAL
REAL
REAL
REAL
REAL
REAL
DWORD
DWORD
(1) Do not include the parenthesis in the label
A.3
Output assemblies
Table A-13: Common output data — Discrete actions only
Assembly
Dword index Name
0 • Bit #0 – Start Sensor Zero (trigger start with a 1, no abort)
• Bit #1 – Reset All Process Totals (same as setting bits
2-8)v
• Bit #2 – Reset Totalizer 1 (Mass Total by default)
• Bit #3 – Reset Totalizer 2 (Volume Total by default)
• Bit #4 – Reset Totalizer 3 (PM Ref Vol Total by default)
• Bit #5 – Reset Totalizer 4 (GSV Total by default)
• Bit #6 – Reset Totalizer 5 (CM Ref Vol Total by default)
• Bit #7 – Reset Totalizer 6 (CM Net Mass Total by default)
• Bit #8 – Reset Totalizer 7 (CM Net Vol Total by default)
• Bit #9 – Start All Totals (trigger start with a 1)
• Bit #10 – Stop All Totals (trigger stop with a 1)
If both start and stop =1, then totals are stopped
• Bit #11 – Start Smart Meter Verification (Continue Measuring Mode only)
Trigger start with a 1, no abort
Data type
DWORD
24
Micro Motion ® Model 5700 EtherNet/IP transmitters
Assembly object (04
HEX
– 16 instances)
Table A-13: Common output data — Discrete actions only
Assembly
Dword index Name
• Bit #12 – Not applicable
• Bit #13 – Reset all Inventory Totals
Table A-14: External process data
Assembly
Dword index Name
0
1
2
Common output data (instance 150 data)
External Pressure
External Temperature
Table A-15: Batcher
Assembly
Dword index Name
0
1
2
Common output data (instance 150 data)
Batch Target
Batcher Control – Discrete Actions
• Bit #0 – Reserved
• Bit #1 – Start Fill
• Bit #2 – End Fill
• Bit #2 – Pause Fill
• Bit #4 – Resume Fill
• Bit #5 – Reserved
• Bit #6 – Start Training
• Bit #7 – Save AOC Calibration
• Bit #8 – Bit #31 for future expansion
3 Maximum Batch Time (Reg 1305)
Table A-16: Batcher and external process data
Assembly
Dword index Name
0–2
3
External process data (instance 151 data)
Batch Target
Data type
Data type
See
REAL
REAL
Data type
See
REAL
DWORD
REAL
Data type
See
REAL
EtherNet/IP Rockwell RSLogix Integration Guide
25
Assembly object (04
HEX
– 16 instances)
26
Table A-16: Batcher and external process data
(continued)
Assembly
Dword index Name
4
5
Batcher Control – Discrete Actions
• Bit #0 – Reserved
• Bit #1 – Start Fill
• Bit #2 – End Fill
• Bit #2 – Pause Fill
• Bit #4 – Resume Fill
• Bit #5 – Reserved (for Clean in Place)
• Bit #6 – Start Training
• Bit #7 – Save AOC Calibration
• Bit #8 – Bit #31 for future expansion
Maximum Batch Time (Reg 1305)
Table A-17: Output configurable data
7
8
9
4
5
6
Assembly
Dword index Name
0
1
Common output data (instance 150 data)
Configurable Slot 1 (Register)
2
3
Configurable Slot 2 (Register)
Configurable Slot 3 (Register)
10
11
12
Configurable Slot 4 (Register)
Configurable Slot 5 (Register)
Configurable Slot 6 (Register)
Configurable Slot 7 (Register)
Configurable Slot 8 (Register)
Configurable Slot 9 (Coil)
Configurable Slot 10 (Coil)
Configurable Slot 11 (Coil)
Configurable Slot 12 (Coil)
Table A-18: Advanced Phase Measurement (APM)
Assembly
Dword index Name
0
1
Common output data (instance 150 data)
External Pressure
Data type
DWORD
REAL
Data type
See
REAL
REAL
REAL
REAL
WORD
WORD
WORD
WORD
BOOL
BOOL
BOOL
BOOL
Data type
See
REAL
Micro Motion ® Model 5700 EtherNet/IP transmitters
A.4
A.5
A.6
Assembly object (04
HEX
– 16 instances)
Table A-18: Advanced Phase Measurement (APM)
(continued)
Assembly
Dword index Name
2
3
External Temperature
External Water Cut
Data type
REAL
REAL
Output Only Heartbeat (instance 253)
Use of this instance number in place of an input assembly instance number allows I/O connections to only write data to the Model 5700 transmitter without any input data returned.
If not practical, remove this instance.
Input Only Heartbeat (instance 254)
Use of this instance number in place of an output assembly instance number allows I/O connections to monitor the input data from the Model 5700 transmitter without providing any output data, called an “input only” connection. Conceptually, input-only connections are used when HMIs or monitoring systems need to track input data, while still allowing a
Programmable Logic Controller (PLC) to provide the control side, or write the outputs.
This connection type is required per the Recommended Functionality for EtherNet/IP Devices document.
For more information about Input Only connections, see Volume 1 of the ODVA Specification
(Common Industrial Protocol).
Listen Only Heartbeat (instance 255)
Much like Input Only connections, Listen Only connections use this instance number in place of an output assembly instance number to open an I/O connection. The I/O connection monitors the input data from the Model 5700 transmitter. Existing I/O connections have dependencies for allocation and timeouts that are different than Input
Only connections.
EtherNet/IP Rockwell RSLogix Integration Guide
27
Assembly object (04
HEX
– 16 instances)
A.7
A.8
Usage notes
All output assemblies contain a common data as outlined in assembly instance 150. To maintain proper ownership of the output data (no toggling of outputs between multiple sources), only a single output assembly may be selected for use in I/O messaging. To achieve this, there is an output lock in place to mark all output assemblies as “owned” even though only a single assembly is actually in use.
All input instances can properly co-exist since no ownership is required. While not practical for most applications, multiple PLCs can theoretically open Input Only connections to any or all of the input assembly instances, up to the maximum number of I/O connections supported.
Common services
Service code
0E
HEX
10
HEX
Implemented for
Class level
Yes
No
Instance level
Yes
Yes
Service name
Get_Attribute_Single
Set_Attribute_Single
28
Micro Motion ® Model 5700 EtherNet/IP transmitters
Assembly connections
Appendix B
Assembly connections
Table B-1: Input and output assemblies
Size (32bit) Input assembly instance
100 – Basic Data
101 – Liquid Volume
102 – Gas Standard Volume
103 – API Referral
9
12
12
19
25
Output assembly instance
For definitions, see
150 – Basic Data
151 – External Process Data
152 – Batcher
153 – Batcher and External Process Data
154 – Configurable Data Set 104 – Concentration Management
105 – Batcher
106 – Small Configurable Data
Set
107 – Medium Configurable Data
Set
108 – Large Configurable Data
Set
109 – APM – Liquid Volume
110 – APM – Gas Volume
16
17
25
41
28
18
155 – APM External Process Data
253 – Output Only Heartbeat
254 – Input Only Heartbeat
255 – Listen Only Heartbeat
Size (32bit)
0
0
0
4
6
1
3
13
4
Table B-2: Connection types
Input assembly instance
ID
1
2
Name
Mass Flow In & No Out
Mass Flow In & Basic Out
For definitions, see
100 – Basic Data
100 – Basic Data
100 – Basic Data 3 Mass Flow In & External Data
Out
4
5
Mass Flow In (Listen Only)
Volume Flow In & No Out
100 – Basic Data
101 – Liquid Volume
6 Volume Flow In & Basic Out 101 – Liquid Volume
7 Vol Flow In & External Data
Out
101 – Liquid Volume
Output assembly instance
For definitions, see
254 – Input Only Heartbeat
150 – Basic Data
151 – External Process Data
255 – Listen Only Heartbeat
254 – Input Only Heartbeat
150 – Basic Data
151 – External Process Data
EtherNet/IP Rockwell RSLogix Integration Guide
29
Assembly connections
30
Table B-2: Connection types
(continued)
Input assembly instance Output assembly instance
ID Name
For definitions, see
For definitions, see
8 Volume Flow In (Listen Only) 101 – Liquid Volume
9 GSV In & No Out 102 – Gas Standard Volume
255 – Listen Only Heartbeat
254 – Input Only Heartbeat
10 GSV In & Basic Out 102 – Gas Standard Volume 150 – Basic Data
11 GSV In & External Data Out
12 GSV In (Listen Only)
102 – Gas Standard Volume 151 – External Process Data
102 – Gas Standard Volume 255 – Listen Only Heartbeat
13 API In & No Out
14 API In & Basic Out
15 API In & External Data Out
16 API In (Listen Only)
17 CM In & No Out
18 CM In & Basic Out
103 – API Referral
103 – API Referral
103 – API Referral
103 – API Referral
104 – Concentration Measurement
104 – Concentration Measurement
254 – Input Only Heartbeat
150 – Basic Data
151 – External Process Data
255 – Listen Only Heartbeat
254 – Input Only Heartbeat
150 – Basic Data
151 – External Process Data 19
20
CM In & External Data Out
CM In (Listen Only)
21 Batcher In & Batcher Out
22 Batcher In & External Data
Out
23 Batcher In (Listen Only)
104 – Concentration Measurement
104 – Concentration Measurement
105 – Batcher
105 – Batcher
105 – Batcher
24 Small Config In & No Out 106 – Small Configurable
Data Set
25 Small Config In & Config Out 106 – Small Configurable
Data Set
26 Medium Config In & No Out 107 – Medium Configurable
Data Set
27
28
Medium Config In & Config
Out
Large Config In & No Out
107 – Medium Configurable
Data Set
108 – Large Configurable
Data Set
29 Large Config In & Config Out 108 – Large Configurable
Data Set
30 Large Config In (Listen Only) 108 – Large Configurable
Data Set
31 APM Liquid In & No Out 109 - APM Liquid
32 APM Liquid In & Basic Out 109 - APM Liquid
255 – Listen Only Heartbeat
152 – Batcher
153 – Batcher and External
Data
255 – Listen Only Heartbeat
254 – Input Only Heartbeat
154 – Configurable Data Set
254 – Input Only Heartbeat
154 – Configurable Data Set
254 – Input Only Heartbeat
154 – Configurable Data Set
255 – Listen Only Heartbeat
254 – Input Only Heartbeat
150 – Basic Data
Micro Motion ® Model 5700 EtherNet/IP transmitters
Assembly connections
Table B-2: Connection types
(continued)
ID Name
33 APM Liquid In & APM Out
Input assembly instance
For definitions, see
109 - APM Liquid
34 APM Liquid In (Listen Only)
35 APM Gas In & No Out
36 APM Gas In & Basic Out
37 APM Gas In & APM Out
109 - APM Liquid
110 - APM Gas
110 - APM Gas
110 - APM Gas
38 APM Gas In (Listen Only) 110 - APM Gas
Output assembly instance
For definitions, see
155 – APM External Process
Data
255 – Listen Only Heartbeat
254 – Input Only Heartbeat
150 – Basic Data
155 – APM External Process
Data
255 – Listen Only Heartbeat
EtherNet/IP Rockwell RSLogix Integration Guide
31
Modbus object (44
HEX
– 1 instance)
Appendix C
Modbus object (44
HEX
– 1 instance)
Topics covered in this appendix:
•
Modbus class attributes
•
Instance attributes
•
Common services
The Modbus object provides a “pass through” to the internal Modbus representation of any data point. All validation related to addressing, length, or write validation is handled by the Modbus DLL.
C.1
Modbus class attributes
Attribute ID
1
Name
Revision
Data type
UINT
Data value
3
Access rule
Get
C.2
C.3
Instance attributes
No instance attributes are defined.
Common services
Service code
0E
HEX
4B
HEX
4C
HEX
4D
HEX
4E
HEX
4F
HEX
Implemented for
Class level
Yes
No
No
No
No
No
Instance level
Yes
Yes
Yes
Yes
Yes
Yes
Service name
Get_Attribute_Single
Read_Discrete_Inputs
Read_Coils
Read_Input_Registers
Read_Holding_Registers
Write_Coils
32
Micro Motion ® Model 5700 EtherNet/IP transmitters
Modbus object (44
HEX
– 1 instance)
Service code
50
HEX
Implemented for
Class level
No
Instance level
Yes
Service name
Write_Holding_Registers
4B
HEX
Read_Discrete_Inputs (Modbus FC 0x02)
Table C-1: Request format
Name
Starting address
Data type
UINT
Quantity of inputs UINT
Description
Offset in table to begin reading from
Number of inputs to read
Semantics
Zero-based
1-2000
Table C-2: Response format
Name
Input status
Data type
BYTE[n]
Description
Input values read
Semantics
8 inputs are packed into each byte
4C
HEX
Read_Coils (Modbus FC 0x01)
Table C-3: Request format
Name
Starting address
Data type
UINT
Quantity of inputs UINT
Description
Offset in table to begin reading from
Number of coils to read
Semantics
Zero-based
1-2000
Table C-4: Response format
Name
Coil status
Data type
BYTE[n]
Description
Input values read
Semantics
8 coils are packed into each byte
EtherNet/IP Rockwell RSLogix Integration Guide
33
Modbus object (44
HEX
– 1 instance)
4D
HEX
Read_Input_Registers (Modbus FC 0x04)
Table C-5: Request format
Name
Starting address
Data type
UINT
Quantity of input registers
UINT
Description
Offset in table to begin reading from
Number of input registers to read
Semantics
Zero-based
1-125
Table C-6: Response format
Name
Input register values
Data type
WORD[n]
Description
Input register values read
Semantics
Data swap to convert between little endian
(CIP) and big endian
(Modbus)
4E
HEX
Read_Holding_Registers (Modbus FC 0x03)
Table C-7: Request format
Name
Starting address
Data type
UINT
Quantity of input registers
UINT
Description
Offset in table to begin reading from
Number of input registers to read
Semantics
Zero-based
1-125
Table C-8: Response format
Name
Holding register values
Data type
WORD[n]
Description
Holding register values read
Semantics
Data swap to convert between little endian
(CIP) and big endian
(Modbus)
4F
HEX
Write_Coils (Modbus FC 0x0F)
Table C-9: Request format
Name
Starting address
Data type
UINT
Description
Offset in table to begin writing to
Semantics
Zero-based
34
Micro Motion ® Model 5700 EtherNet/IP transmitters
Modbus object (44
HEX
– 1 instance)
Table C-9: Request format
(continued)
Name
Quantity of outputs
Data type
UINT
Output values BYTE[n]
Description
Number of output coils to write
Output coils values
Semantics
1-2000
Table C-10: Response format
Name
Starting address
Quantity of outputs
Data type
UINT
UINT
Description
Offset in table where writing began
Number of output coils written
Semantics
Zero-based
50
HEX
Write_Holding_Registers (Modbus FC 0x10)
Table C-11: Request format
Name
Starting address
Data type
UINT
Quantity of outputs
Output values
UINT
WORD[n]
Description
Offset in table to begin writing to
Number of output coils to write
Output register values
Semantics
Zero-based
1-125
Table C-12: Response format
Name
Starting address
Data type
UINT
Quantity of outputs UINT
Description
Offset in table where writing began
Number of output resisters written
Semantics
Zero-based
EtherNet/IP Rockwell RSLogix Integration Guide
35
*MMI-20029770*
MMI-20029770
Rev AA
2016
Micro Motion Inc. USA
Worldwide Headquarters
7070 Winchester Circle
Boulder, Colorado 80301
T +1 303-527-5200
T +1 800-522-6277
F +1 303-530-8459
www.micromotion.com
Micro Motion Europe
Emerson Process Management
Neonstraat 1
6718 WX Ede
The Netherlands
T +31 (0) 70 413 6666
F +31 (0) 318 495 556
www.micromotion.nl
Micro Motion Asia
Emerson Process Management
1 Pandan Crescent
Singapore 128461
Republic of Singapore
T +65 6777-8211
F +65 6770-8003
Micro Motion United Kingdom
Emerson Process Management Limited
Horsfield Way
Bredbury Industrial Estate
Stockport SK6 2SU U.K.
T +44 0870 240 1978
F +44 0800 966 181
Micro Motion Japan
Emerson Process Management
1-2-5, Higashi Shinagawa
Shinagawa-ku
Tokyo 140-0002 Japan
T +81 3 5769-6803
F +81 3 5769-6844
©
2016 Micro Motion, Inc. All rights reserved.
The Emerson logo is a trademark and service mark of Emerson
Electric Co. Micro Motion, ELITE, ProLink, MVD and MVD Direct
Connect marks are marks of one of the Emerson Process
Management family of companies. All other marks are property of their respective owners.
advertisement
Key Features
- Ethernet connectivity
- Rockwell RSLogix 5000 compatibility
- Wide range of measurement capabilities
- Easy configuration and use
