Coriolis mass flowmeters, hart communication protocol (206 pages)
Summary of Contents for FMC Technologies Smith Meter microFlow.net Liquid
Page 1
Electronic Preset Delivery System Smith Meter ® microFlow.net Liquid Modbus and Modbus/TCP Communications Bulletin MNFL003 ║ Issue/Rev 0.1 (9/13)
Page 2
FMC Technologies Measurement Solutions, Inc. FMC Technologies Measurement Solutions, Inc. will not be held responsible for loss of liquid or for damage of any kind or from any cause to the person or property of others, or for loss or profit, or loss of use, or any other special, incidental, or consequential damages caused by the use or misapplication of the contents stated herein.
microFlow.net Liquid Modbus Communications Manual Table of Contents Table of Contents 1 – Introduction ................................... 5 1.1 – Modbus/TCP ..................................5 1.2 – Floating Point Endian Control .............................. 6 1.3 – Communications Control Selections............................ 6 1.4 – Configuring the microFlow.net Liquid for Modbus Communications via Serial Port ............6 1.5 –...
microFlow.net Liquid Modbus Communications Manual Introduction 1 – Introduction The Modbus protocol was developed by Modicon, Inc. to be a concise method of transferring data to/from programmable logic controllers (PLCs). It has become a de-facto standard in many areas of industrial automation where supervisry control or remote data collection is required.
microFlow.net Liquid Modbus Communications Manual Introduction Floating Point Endian Control Floating-point numbers are not defined in the Modbus specification; there are nearly as many variations of how it is supported as there are vendors. Most often, Modbus registers are combined sequentially to make up an IEEE single precision or double precision floating point number;...
microFlow.net Liquid Modbus Communications Manual Introduction Mode – dependent on EIA 232/EIA 485 wiring configuration. Must match the master device. • Return to the Main Menu by pressing the <Clear> key. Configuring the microFlow.net Liquid for Modbus Communications via TCP/IP (Ethernet or SLIP) •...
microFlow.net Liquid Modbus Communications Manual Implementing Remote Host Functionality 2 – Implementing Remote Host Functionality Implementing Host Status Polling To implement routine polling loops, the following coils should be periodically read. These coils represent the critical states that a host should monitor. Coil State In Program Mode –...
microFlow.net Liquid Modbus Communications Manual Implementing Remote Host Functionality 09 Alarm Condition 10 Storage Full 11 Operation Out Of Sequence 12 Power Failed During Transaction 13 Already Authorized 14 Program Code Not Used 15 Display/Keypad In Remote Mode 16 Ticket Not In Printer 17 No Keypad Data Pending 18 No Transaction In Progress 19 Option Not Installed/Enabled...
microFlow.net Liquid Modbus Communications Manual Implementing Remote Host Functionality 2.25 Set Time/Date To set the date and time via Modbus, write the following holding registers (Function 3): 7688 (30344) Time Set - Year, 4 digit 7689 (30345) Time Set - Month 768A (30346) Time Set - Day 768B (30347) Time Set - Hour 768C (30348) Time Set - Minute...
microFlow.net Liquid Modbus Communications Manual Implementing Remote Host Functionality Bit# Bit 31 . . . Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 Value Recipe Example: If recipes 3 and 5 are the only valid recipes for this load, the value to write to this register prior to authorization would be: (5-1) (3-1)
microFlow.net Liquid Modbus Communications Manual Implementing Remote Host Functionality 2.32 Read Event Log To read historical events from the event log, the following steps are used. The most recent event log entry’s sequence number is available via Function 4, registers 1792- 1793 (unsigned long integer).
Page 18
microFlow.net Liquid Modbus Communications Manual Modbus Register Reference 30350 (768E) Time Set - 0=MIL,1=AM,2=PM Number Back (0=current) 40588 (9E8C) Recipe Index to Read/Write (1-4) Directory: SYSTEM_CMDS ------------------------------------------------------------------------ Data Type: UNSIGNED_LONG Start Address: 30464 ******Start of Function 4***** - STATUS REGISTERS - Function 4 table: 30464 (7700) Request Event Log Entry ------------------------------------------------------------------------...
Page 20
microFlow.net Liquid Modbus Communications Manual Modbus Register Reference 3852 (0F0C) Current Prompt Response Data 1 Directory: BATCH_RUN_DATA 3854 (0F0E) Current Prompt Response Data 2 Data Type: UNSIGNED_CHAR 3856 (0F10) Current Prompt Response Data 3 3858 (0F12) Current Prompt Response Data 4 Start Address: 5632 3860 (0F14) Current Prompt Response Data 5...
Page 21
microFlow.net Liquid Modbus Communications Manual Modbus Register Reference 11264 (2C00) Additive 1 Non-resettable Total Start Address: 15104 11268 (2C04) Additive 2 Non-resettable Total 15104 (3B00) Analog Analog Counts 11272 (2C08) Additive 3 Non-resettable Total 15106 (3B02) Analog Raw Value (mA or volts) 11276 (2C0C) Additive 4 Non-resettable Total 15108 (3B04) Analog Engineering Value 15136 (3B20) Analog I/O #2 Analog Counts...
microFlow.net Liquid Modbus Communications Manual Appendix 4 – Appendix Modbus Communications Primer The microFlow.net Liquid Modbus interface is designed to conform to a subset of the “Modicon Modbus Protocol Reference Guide” PI-MBUS-300 Rev. D (Modicon, Inc., Industrial Automation Systems). Modbus can be implemented on various transmission mediums (such as RS-232 or RS-485 communication ports).
microFlow.net Liquid Modbus Communications Manual Appendix master to delay twice between messages as long as the duration exceeds the speci- fied delay). 4.12 How Characters are Transmitted Serially When messages are transmitted on standard Modbus serial networks, each character or byte is sent in this order (left to right): With Parity Checking (8 bit word, 1 stop) Start Stop...
microFlow.net Liquid Modbus Communications Manual Appendix Master/Slave Communications The master communicates with the microFlow.net Liquid by sending messages con- taining function codes. Function codes indicate the actions the microFlow.net Liquid is to perform. The microFlow.net Liquid’s response to the master uses the function code field to report on the status of the task it was assigned.
microFlow.net Liquid Modbus Communications Manual Appendix Assuming that no error in communication interferes, the data field of a response from a slave to a master contains the requested data. If an error does occur, the field contains an exception code that the application controlling the master can use to determine the next action to be taken.
microFlow.net Liquid Modbus Communications Manual Appendix 4.51 Field Contents In Modbus Messages Examples of a Modbus query message and normal response are shown in the tables on the following page. The field contents in both examples are displayed in hexadecimal. In this example, the master sends a Read Holding Registers request to microFlow.net Liquid address 06.
microFlow.net Liquid Modbus Communications Manual Appendix 4.52 Address The address is the first field in the frame and consists of one byte (eight bits) of informa- tion. The address is the unique identification of the microFlow.net Liquid (slave) that is to receive the message that is sent via the supervisory system (master).
microFlow.net Liquid Modbus Communications Manual Appendix 01 Read Relay Status Description Reads the ON/OFF status of discrete variables in the microFlow.net Liquid. The maxi- mum number of “coils” per response is 256 in the microFlow.net Liquid. Query The query message specifies the starting register and quantity of registers to be read. There are now no variables to read from this group.
microFlow.net Liquid Modbus Communications Manual Appendix are contained in the next byte, again from left to right. As the bits are transmitted serially, they flow from LSB to MSB (i.e., 20 through 27, 28 through 35, and so on). In the last data byte, the status of relays 56 through 52 is shown as the byte value 1B hex, or binary 0001 1011.
microFlow.net Liquid Modbus Communications Manual Appendix The status of inputs 1031 through 1024 is shown as the byte value AC hex, or binary 1010 1100. Input 1031 is the MSB of this byte and input 1024 is the LSB. The status of inputs 1031 through 1024 is expressed as ON-OFF-ON-OFF-ON-ON-OFF-OFF, from left to right.
microFlow.net Liquid Modbus Communications Manual Appendix 04 Read Input Registers Description This function reads the binary contents of “input registers” in the microFlow.net Liquid. These are “read-only” values; they cannot be written. Query The query message specifies the starting register and quantity of registers to be read. Registers are addressed starting at zero.
microFlow.net Liquid Modbus Communications Manual Appendix An example of a request to force relay 150 ON in microFlow.net Liquid 17 appears below: (Reset User Alarm #9) Query Field Name Example (Hex) microFlow.net Liquid Address Function Relay Address Hi Relay Address Lo Force Data Hi Force Data Lo Error Check (CRC)
microFlow.net Liquid Modbus Communications Manual Appendix Response An echo of the query, returned after the register con-tents have been preset, is a normal response. An example of a response to the preceding query appears below: Response Field Name Example (Hex) microFlow.net Liquid Address Function Register Address Hi...
microFlow.net Liquid Modbus Communications Manual Appendix Query Field Name Example (Hex) microFlow.net Liquid Address Function Relay Address Hi Relay Address Lo Quantity of Relays Hi Quantity of Relays Lo Byte Count Force Data Hi (Relays 27-20) Force Data Hi (Relays 29-28) Error Check (CRC) Response The normal response consists of the slave address, function code, starting address,...
microFlow.net Liquid Modbus Communications Manual Appendix Query Field Name Example (Hex) microFlow.net Liquid Address Function Starting Address Hi Starting Address Lo No. of Registers Hi No. of Registers Lo Byte Count Data Hi Data Lo Data Hi Data Lo Error Check (CRC) Response A normal response consists of the slave address, function code, starting address, and quantity of registerspreset.
microFlow.net Liquid Modbus Communications Manual Appendix Accordingly, the application program controlling the master can quickly recognize the exception response and derive the exception code from the data field. Data Field: A normal response consists of any data or statistics in the data field re- quested by the query.
microFlow.net Liquid Modbus Communications Manual Related Publications 6 – Related Publications The following literature can be obtained from FMC Measurement Solutions Literature Fulfillment at measurement.fulfillment@fmcti.com or online at www.fmctechnologies.com/measurementsolutions When requesting literature from Literature Fulfillment, please reference the appropriate bulletin number and title. microFlow.net Liquid Specification ............................